# Frontline Communication That Reaches Whoever Is on Shift Now **Author:** MangoApps Team **Published:** 2026-10-18 **Category:** frontline-communication Frontline messages fail when they go to a stale list instead of the people actually working. This week's releases in Chat, Safety Hub, Livestreaming and HR start from each person's real shift, crew, language and inbox instead. # Frontline Communication That Reaches Whoever Is on Shift Now At 6:40 on a Tuesday morning, a receiving supervisor at a distribution center needs to tell the dock crew that a trailer is coming in early and the bay assignments have changed. She knows exactly who she means: the people standing on the dock right now. What she has is a group chat built eight months ago. It includes two people who transferred out and three who only work nights, and it leaves out the new hire who started Monday. She sends the message anyway. Then she walks the dock to tell people in person, because the message went to the list and the list isn't the crew. Every frontline leader knows this gap. The people you need to reach are defined by where they are and when they're working. The tools that reach them are defined by who was added to a list at some point. This week, several releases across MangoApps closed that gap from different directions. ## Address the shift, not the roster Most workplace messaging assumes a stable team: the same people, at the same desks, all week. Frontline teams don't work like that. The group that matters at 7 a.m. is not the group that matters at 3 p.m., and the store or plant floor changes with every hire, transfer and schedule swap. The new [shift-aware Chat](https://www.mangoapps.com/changelog/3420) starts from that reality. A channel can follow a group in the organization, and administrators can create a channel for every location, one for whoever is on shift at each location, and a team channel for every manager. Membership follows the org chart and the schedule, so nobody adds or removes people by hand. When the new hire is scheduled, they're in. When someone transfers, they're out. Inside a conversation, people can see who is on shift right now. That sounds small, but it answers the question every supervisor asks before sending anything: who will actually read this in the next ten minutes? People can @onshift the coworkers currently working, or message whoever is on shift by location and role. The supervisor on the dock no longer needs an accurate list. She needs to know which dock she's talking to. Two more details matter on the floor. An Important message can name a backup who is told when the message isn't confirmed in time, so a safety notice that goes unread doesn't quietly die. And approvals waiting on a person now arrive as cards in Chat and can be approved or rejected there. A shift lead who spends the day in Chat doesn't have to switch apps to clear a time-off request before the next schedule goes out. On the phone, conversations update live, can be translated into the reader's language, and support push-to-talk with a walkie-talkie mode for crews whose hands are busy. The same idea, that a message belongs to the people doing the work, showed up somewhere you might not expect. A [permit to work in Safety Hub](https://www.mangoapps.com/changelog/3394) can now list the crew working under it, not just the person who requested it and the person who authorized it. When a hot work permit is suspended because of a nearby gas reading, the safety officer used to rely on the supervisor to pass the word along. Now each welder on the crew gets the stop-work notice on their phone directly. They also hear when the permit is issued, cancelled, past its end time or expired. Being on the crew lets someone view the permit, not edit or close it, so the control stays where it belongs. In both cases, the useful change isn't a new channel. It's that the audience is defined by the work. ## A town hall that reaches the break room Company-wide meetings show the roster problem at its widest. The CEO speaks to a room at headquarters and a stream for everyone else. For most frontline employees, "everyone else" means a phone in a loud break room during a fifteen-minute window, or nothing at all. This week's Livestreaming releases treat the remote sites as part of the audience rather than an afterthought. [Live captions](https://www.mangoapps.com/changelog/3396) now appear while the host is on air, in English, French, German, Italian, Portuguese or Spanish. That makes a town hall accessible to deaf and hard-of-hearing employees. It also makes it usable on a shop floor where nobody can hear a phone speaker. A plant manager running a monthly safety meeting in Spanish can count on workers following along in Spanish captions. The broadcast can also reach screens people already walk past. While a session is live, it can [take over the Digital Signage screens](https://www.mangoapps.com/changelog/3420) at the sites the host picks, then hand them back to their usual playlist. The break-room TV at every warehouse becomes the town hall for an hour without anyone at those sites touching a remote. Afterwards, hosts can see how many of the intended audience joined at each site, district and region. That turns "we held an all-hands" into "here's which locations we actually reached." Questions get the same treatment. A stage wall behind the speaker shows the question being answered and the next ones by votes. A QR code on the wall, the host console and a printable sheet lets people in the room sign in on their phones and go straight to the Q&A. Each session decides whether askers' names are shown to everyone, to moderators only or to nobody. That matters if you want an associate to ask the question they'd never raise with their name attached. With [moderated Q&A](https://www.mangoapps.com/changelog/3396), hosts choose whether questions appear immediately, are filtered by a language screen, or wait for a moderator. Sessions open to the whole company start in the reviewed mode by default. A session also no longer needs to be streamed in MangoApps at all. It can link to video on another platform, or have no video for an in-person meeting, while the Q&A, polls and chat still run in the app. The point isn't production value. Every frontline employee should be able to hear the meeting, ask a question and be counted as reached, whether they're in the cafeteria or two states away. ## When there's no inbox to send to The quietest release of the week may matter most to HR and compliance teams. Much of HR's machinery assumes every employee and candidate has an email address. In frontline industries, many don't. FCRA adverse action notices are a clear example. They must be sent and documented whether or not a candidate has an email address on file. Recruiters can now [record a notice sent by post or delivered in person](https://www.mangoapps.com/changelog/3395), with the date, the method and a note. A recorded pre-adverse notice starts the required waiting period of business days from its date. When a final notice is due and can't be emailed, the hiring decision-makers are told. Every recorded notice goes into the audit log and the check's FCRA timeline. The candidate without an email is no longer the case that sits in someone's drafts folder until the timing is in question. The same week, two other releases made sure the record matches what actually happened to people who aren't sitting at a computer. The [scheduled form run report](https://www.mangoapps.com/changelog/3395) lists each person a recurring checklist or sign-off was sent to and whether they've submitted it in the current cycle. A district manager can check mid-morning which store leads haven't sent the opening checklist and follow up with them, instead of counting submissions by hand. And [missed-break premium pay](https://www.mangoapps.com/changelog/3393) now calculates the extra hour owed when an employee works through a required meal or rest break, as states such as California require. It updates whenever a punch closes or its breaks change, and the same amount appears on the timesheet, the payroll report and the payroll export. The employee who skipped lunch during a rush no longer depends on a manager remembering to add it before payroll. ## The bigger picture It's easy to treat frontline communication as a reach problem: get the app on more phones, send more notifications. This week points to something more specific. Reach fails when the audience is defined the wrong way. It fails when a chat goes to a stale list instead of the people on shift, when a permit notice goes to the requester instead of the crew, when a town hall goes to "everyone" but only works for people at desks, and when a compliance notice assumes an inbox that doesn't exist. The fix in each case was the same. Start from the person's real situation — their shift, their location, their crew, their language, whether they have an email address at all — and let the system work out who that is. Managers stop maintaining lists. Employees stop missing messages that were technically sent to them. And when someone later asks whether the dock crew got the word, whether the warehouse saw the town hall, or whether the candidate got their notice, the record answers. That supervisor on the dock will still walk the floor. She just won't have to do it to make up for a message that went to the wrong people. --- # Where frontline work gets stuck between steps **Author:** MangoApps Team **Published:** 2026-10-14 **Category:** mango-scoop Explore credential gaps and the path from work order request to payment, plus updates to Sites Export and Import and the Rich-Text Post Composer. Hand-picked stories from MangoApps this week. ## Designing for the Forgotten Step in Frontline Operations ![Designing for the Forgotten Step in Frontline Operations](https://mango-cdn.b-cdn.net/images/blog-thumbnails/blog_839_20261011_140156.png) Most frontline delays come from small steps that wait on someone to remember, be reachable, or redo work they already did. Here is how this week's releases remove those waits, from timesheets and purchase orders to policy sign-off for employees without email. [Read the full story →](https://www.mangoapps.com/articles/designing-for-the-forgotten-step-in-frontline-operations) --- ### More to read #### MangoApps named a 2026 WorkTech Award winner by Inspiring Workplaces MangoApps is a 2026 WorkTech Award winner, named by Inspiring Workplaces for the second year running. See the customer results behind the win. [Read more →](https://www.mangoapps.com/articles/2026-worktech-award-winner) #### Where frontline handoffs lose the thread Explore the credential gap between procedures and schedules, the work order path from request to payment, and the field service management guide. [Read more →](https://www.mangoapps.com/articles/mango-scoop-2026-10-06) --- ### What's New **General** — [Product Update - October 11, 2026](https://www.mangoapps.com/changelog/3392) * **[Sites Export and Import](https://www.mangoapps.com/directory/app/sites)** — Admins can package one, several or all Sites, with their pages, files, navigation and translatio... **General** — [Product Update - October 10, 2026](https://www.mangoapps.com/changelog/3391) * **[Rich-Text Post Composer](https://www.mangoapps.com/directory/app/communications)** — Authors now see bold text, links, lists, mentions and pictures exactly as readers will ... --- # MangoApps Recognized as a Visionary for the Fourth Consecutive Year in the 2026 Gartner® Magic Quadrant™ for Intranet Packaged Solutions **Author:** The MangoApps Team **Published:** 2026-10-14 **Category:** intranet MangoApps, The AI Platform for the Frontline Workforce, today announced that it has been named a Visionary for the fourth consecutive year in the 2026 Gartner® Magic Quadrant™ for Intranet Packaged Solutions. SEATTLE, Wash. — October 14, 2026 — MangoApps, The AI Platform for the Frontline Workforce, today announced that it has been named a Visionary for the fourth consecutive year in the 2026 Gartner® Magic Quadrant™ for Intranet Packaged Solutions. MangoApps credits this recognition to its continued innovation and its vision for bringing communication, knowledge, and daily work together for frontline and desk employees on a single AI platform. ### Scored Among Highest Four in Four of Five Critical Capabilities Use Cases In the accompanying 2026 Gartner® Critical Capabilities for Intranet Packaged Solutions report, MangoApps ranked third in the Work Management and Resource Portal use cases and fourth in the Employee Engagement and Employee and Workplace Services use cases, receiving the following scores: - Employee Engagement: 3.81 / 5 - Employee and Workplace Services: 3.75 / 5 - Knowledge Services: 3.80 / 5 - Work Management: 3.88 / 5 - Resource Portal: 3.84 / 5 ### One Platform for Every Employee “Our customers run some of the most complex frontline operations in the world, and they need one platform that brings communication, knowledge, and daily work together for every employee,” said Anup Kejriwal, CEO and Founder of MangoApps. “We feel being recognized as a Visionary for the fourth consecutive year reflects the work our team and our customers have put into building that platform together, and we’re grateful for it.” Over the past year, MangoApps has continued to expand its platform. It introduced a [refreshed brand](https://www.mangoapps.com/articles/mangoapps-unveils-refreshed-brand-and-logo) reflecting its evolution into a unified workforce platform; its [Winter Release](https://www.mangoapps.com/articles/native-workforce-management-and-next-gen-generative-ai), which added native shift scheduling, time and attendance, and AI that builds surveys, wikis, and workspaces from a prompt; its [Spring ’26 Release](https://www.mangoapps.com/articles/mangoapps-spring-26-release-ai-lms-ops-upgrades), which added AI course creation, AI agents that query live Power BI data, and LMS automation; and [Multi-Agent Answers](https://www.mangoapps.com/articles/introducing-multi-agent-answers-in-mangoapps-ask-ai) in Ask AI, which coordinates specialist agents to answer questions that span scheduling, leave, tasks, and service requests in a single reply. MangoApps has also received more independent validation in the last year, including the [Gold award for Excellence in Intranet & Communications Platforms](https://www.mangoapps.com/articles/mangoapps-gold-reworked-2026-impact-awards) in Reworked’s 2026 IMPACT Awards, inclusion in [The Forrester Wave™: Intranet Platforms, Q2 2026](https://www.mangoapps.com/articles/mangoapps-2026-forrester-wave-intranet-platforms), and [Workday Design Approved status](https://www.mangoapps.com/articles/workday-design-badge) for MangoApps Workday Widgets, now listed on the Workday Marketplace. MangoApps serves a global customer base across industries such as retail, healthcare, manufacturing, and logistics. Organizations including AutoZone, PetSmart, TeamHealth, and YMCA of the USA rely on MangoApps to connect their frontline workforce, streamline daily operations, and keep every employee informed. To learn more, visit [www.mangoapps.com](https://www.mangoapps.com/). Source: Gartner Research, Magic Quadrant for Intranet Packaged Solutions, By [Mike Gotta](https://www.gartner.com/analyst/bbce01b872), Helen Poitevin, Alexandra Earl, 29 September 2026. Gartner Research, Critical Capabilities for Intranet Packaged Solutions, By [Mike Gotta](https://www.gartner.com/analyst/bbce01b872), Alexandra Earl, Helen Poitevin, 29 September 2026. GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally, and MAGIC QUADRANT is a registered trademark of Gartner, Inc. and/or its affiliates and are used herein with permission. All rights reserved. Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner’s research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose. About MangoApps MangoApps is The AI Platform for the Frontline Workforce. Built for enterprises with large frontline and distributed workforces, MangoApps brings together Employee Experience, Frontline Operations, and People Operations on a single platform under one identity, one data model, and one AI foundation. Trusted by more than 2 million users at leading organizations around the world, MangoApps keeps business-critical work moving every day. Learn more at [www.mangoapps.com](https://www.mangoapps.com/).** --- # Designing for the Forgotten Step in Frontline Operations **Author:** MangoApps Team **Published:** 2026-10-11 **Category:** frontline-operations Most frontline delays come from small steps that wait on someone to remember, be reachable, or redo work they already did. Here is how this week's releases remove those waits, from timesheets and purchase orders to policy sign-off for employees without email. # Designing for the Forgotten Step in Frontline Operations It is Tuesday morning, and a payroll coordinator is going down a list of names. None of these people did anything wrong. They worked their shifts, clocked in and clocked out. They just didn't press "submit" on a timesheet that was due yesterday. So their manager can't approve it, payroll can't close, and the coordinator spends an hour sending reminders to people who are already back on the floor. Every operations leader knows some version of this. Most of the delay in frontline work isn't caused by hard decisions. It comes from small steps that depend on one person remembering, being reachable, or redoing something they've already done. The process stops and waits for them. Several of the releases we shipped across MangoApps this week deal with that kind of waiting. They don't add steps. They take away the ones where work used to stall. ## When the Next Step Shouldn't Need a Reminder The timesheet problem is a good place to start, because the fix is simple. With [Timesheet Auto-Submit](https://www.mangoapps.com/changelog/3388), an admin can have timesheets submitted automatically the day after they are due. The employee can still review and submit their own, and the manager still approves. The difference is that approval no longer depends on whether someone remembered to click a button after a twelve-hour shift. This matters more than it looks. A late timesheet rarely stays a timesheet problem. It turns into a late approval, then a payroll exception, then a correction on the next check, and eventually a frustrated employee who thinks the company can't pay them properly. The fix has to happen at the first step, because that is where the delay begins. Procurement has the same shape. An inventory item reaching its reorder point is a predictable event, yet in many warehouses it still depends on someone noticing the shelf is low and then filling out a purchase order from memory. [Automatic Draft Purchase Orders](https://www.mangoapps.com/changelog/3389) now prepare a draft PO as soon as an item hits its reorder point, with the supplier, price and quantity already filled in. A person still reviews and sends it. What goes away is the gap between "we're running low" and "someone started the order," which is usually where stockouts come from. The new [Warehouse Overview](https://www.mangoapps.com/changelog/3288) on the Procurement dashboard puts low and out-of-stock items, the pick queue and incoming deliveries on one screen, by location and on the phone, so whoever reviews those drafts can see the full picture. Forms got a smaller fix in the same spirit. Form owners can now turn on [Response Alerts for Public Forms](https://www.mangoapps.com/changelog/3389) and get an in-app notification and an email each time someone submits through a public link. A form that collects incident reports from contractors or requests from the public is only useful if someone sees the response while it can still be acted on. Before, that depended on someone remembering to check. The common principle: when the next step is predictable, the system should prepare it, and people should spend their attention on judgment, not on remembering. ## Stop Asking People to Redo What They Already Did The second kind of stall comes from repeated work. We ask people to prove, confirm or rebuild things that already exist, and the repetition costs more than time. It teaches people that the process doesn't know what they've done. Onboarding is where this is most obvious. Someone transfers from another location or comes back after a season away, and their onboarding checklist asks them to complete a safety course they finished four months ago. With [Carry Over Valid Completions](https://www.mangoapps.com/changelog/3390), onboarding tasks can be marked complete automatically when the person already holds a valid course, policy acknowledgment, SOP, certification or licence. Their checklist then shows only what is actually left. Training authors can now also set [Per-Course Certificate Validity](https://www.mangoapps.com/changelog/3387), so "valid" means what it should for each course: a forklift certification and a general orientation module don't need to expire on the same schedule. Content upkeep has its own version of the problem. Review cycles on SOPs, policies and knowledge-base articles exist for a good reason, but most overdue reviews end the same way: the owner reads the page, finds nothing wrong, and then has to make a trivial edit just to reset the clock. [Still Accurate Content Reviews](https://www.mangoapps.com/changelog/3354) let owners confirm in one tap that the content is still correct, which restarts its review cycle without an edit. That keeps the record honest. A page marked as reviewed has actually been reviewed, and no one has to fake a change to prove it. Page owners on the intranet now have a [Sites Care Dashboard](https://www.mangoapps.com/changelog/3388) that shows which pages need attention: pages with no owner, broken links, content going stale, required reading people haven't finished. Each item links straight to the affected pages. Instead of checking every page, owners see the short list that actually needs them. The same idea applies when people create something new. AI drafting for forms, inspections, review templates, onboarding plans, playbooks and job postings now [starts from your company's closest existing template](https://www.mangoapps.com/changelog/3392) before it turns to the general gallery. Your organization has already decided how an inspection should be structured or what a job posting should say about benefits. A new draft should start from those decisions, not from a blank page that someone then has to fix to match house style. ## Reaching the People the Process Forgot The third kind of stall is the least visible. The process works fine for people at a desk and quietly fails for everyone else. Policy acknowledgment is a clear example. Many campaigns still run on email, and a large share of frontline workers don't have a company email address. As a result, the people who most need to sign a safety or conduct policy are often the ones the campaign can't reach. Compliance reports show a gap, and someone ends up chasing signatures on paper. [Policy Sign-Off Without Email](https://www.mangoapps.com/changelog/3387) sends acknowledgment campaigns to employees without an email address, who review and sign from their in-app Inbox. The campaign reaches the whole workforce, not just the part with an inbox. Attendance has a similar gap. When an employee misses a shift, the follow-up often happens on the manager's screen while the employee never sees the record. With [Missed Shifts on Mobile](https://www.mangoapps.com/changelog/3387), employees can see their missed shifts on their phone, check whether each one was excused, and explain an absence to their manager. Disputes are easier to settle while the shift is still recent, and people don't find out about a problem for the first time at a performance conversation. [Work Assignments](https://www.mangoapps.com/changelog/3390) addresses another familiar case: someone is sent to cover another site for two weeks and learns where to go, and who to report to, from a text message passed along by their manager. HR can now record the posting with its dates, and the person gets a "My Assignments" view showing where they are going, when, and who to report to. Training coordinators also got a related improvement. They can [add people to instructor-led sessions directly](https://www.mangoapps.com/changelog/3390), and booked sessions appear on everyone's calendar, so a learner doesn't miss a session because the invite went to the wrong place. ## The Bigger Picture None of these changes is dramatic on its own. A timesheet submits itself. A purchase order starts as a draft. A policy reaches someone without an email address. But frontline operations usually don't fail through big mistakes. They slow down through many small waits, each depending on one person who was busy, off shift, or never included in the process. Those waits add up in places operations leaders track closely: payroll exceptions, stockouts, compliance gaps, and new hires whose first week is spent repeating training they've already done. They also add up in a place that is harder to measure, which is how people feel about the workplace. An employee who is asked to redo a valid certification, or who learns about a missed shift weeks later, concludes that the system doesn't know them. That impression affects whether they stay. A useful question for any frontline process is where it depends on someone remembering, and whether it needs to. Some steps need a human decision, and they should stay that way. Many others are predictable enough for the system to prepare them, so people can spend their time on the decisions that actually need them. --- # MangoApps named a 2026 WorkTech Award winner by Inspiring Workplaces **Author:** Andy Tolton **Published:** 2026-10-08 **Category:** news-and-updates MangoApps is a 2026 WorkTech Award winner, named by Inspiring Workplaces for the second year running. See the customer results behind the win. MangoApps has been named a **[2026 WorkTech Award winner](https://www.inspiring-workplaces.com/awards/work-tech-awards/)** by the Inspiring Workplaces Group, making this our second year in a row on the list. This year, 14 technology companies from around the world were recognized. But what stood out to us was something Inspiring Workplaces founder Matt Manners said in the announcement: "More technology does not automatically mean a better workplace." We agree. There's no shortage of new workplace technology, especially around AI. The harder question is whether any of it is actually making work better for the people using it. That's a big part of what the WorkTech Awards set out to recognize. ## At a glance | **Award** | 2026 WorkTech Award | | **Awarding body** | The Inspiring Workplaces Group | | **Announced** | October 8, 2026 | | **Winners named** | 14 technology companies worldwide | | **MangoApps status** | Winner for the second consecutive year | | **Judged on** | Purpose, investment, innovation, customer results, and the company's own employee experience | ## How the 2026 WorkTech Awards were judged The judging focused on five areas: why the company exists, how much it invests in improving its product, what it's doing differently, the results customers are seeing, and whether the company creates the kind of employee experience it promotes to others. That meant we needed to show real examples and real results, not simply talk about what MangoApps can do. ## The customer results we submitted ### TeamHealth: 200+ applications in one app for 23,000 clinicians [TeamHealth](https://www.mangoapps.com/resources/teamhealth-case-study), one of the largest physician practices in the U.S., uses MangoApps to power ZeniTH, its employee app for 23,000 clinicians working across hundreds of facilities. Before ZeniTH, employees had to navigate a long list of different systems and tools. Today, more than 200 applications are accessible through one mobile app. More than 90% of employees use ZeniTH every month, even though using it isn't required. They come back because it makes their work easier. We also shared the story of Petauri. ### Petauri: one platform across 5x growth and multiple acquisitions [Petauri](https://www.mangoapps.com/resources/petauri-case-study) launched MangoApps on January 1, 2024, when the company had about 100 employees. Since then, it has grown to more than 500 employees across the U.S. and UK, largely through acquisitions. As new companies join Petauri, their employees can immediately become part of the same workplace rather than waiting months for systems to be combined. Petauri has also built three AI assistants in MangoApps. When choosing its approach to AI, the company needed to keep a complete record of the questions employees asked and the answers they received. That requirement led Petauri to choose MangoApps over Microsoft Copilot, which couldn't provide that capability at the time. ## Where MangoApps invests: 40% of revenue and 300+ releases a year More than 40% of our revenue now goes back into research and product development, and that number continues to grow. Over the past 12 months, we've shipped more than 300 releases. We publish every one of them in our [changelog](https://www.mangoapps.com/changelog), with dates and details, so customers and anyone evaluating MangoApps can see exactly what we've been working on. Some of the work we're most excited about goes beyond simply giving employees an AI assistant they can ask questions. For example, a shift handoff can automatically create follow-up tasks. If an employee reports something blocking their work, MangoApps can check again when the related issue has been resolved. When someone returns to a procedure they've used before, they can see what changed instead of reading the entire document again. These may not make for the flashiest AI demos, but they solve real problems. That matters especially for frontline employees. A lot of workplace technology has been designed first for people sitting at desks. We think [AI needs to be useful](https://www.mangoapps.com/ai) for the person working in a store, hospital, warehouse, factory or out in the field too. ## How MangoApps uses its own platform MangoApps also runs on MangoApps. Our employees use the same platform we sell to our customers, including our own AI assistants. Today, those assistants handle about 40% of routine HR and IT questions internally. Our product roadmap is shaped by customers too. Most of what we build starts with a customer request, and because every release is public, anyone can look back and see what we shipped and when. We also run our customer community on MangoApps. It's where customers work directly with their Customer Success teams, share what they've built and learn from each other. Our monthly spotlight sessions follow the same idea. Instead of us showing customers what MangoApps can do, customers show each other how they're using it. ## Why this award matters alongside our analyst recognition We've been fortunate to receive a lot of recognition for MangoApps. Gartner has named us a Visionary in the Magic Quadrant for Intranet Packaged Solutions for four consecutive years. Forrester has named us a Strong Performer in the Intranet Platforms Wave three times in a row. IDC named MangoApps a Leader in its Worldwide Employee Experience MarketScape, and ClearBox recognized us as an AI Innovator, Leading Product and Community Builder in its 2026 review. Those evaluations look closely at the strength of the platform. The WorkTech Awards come at it from a slightly different angle: Is the technology actually helping people? That's a question we care a lot about. MangoApps has now been around for 18 years. We're bootstrapped and employee-owned, more than 2 million people use our platform, and we retain 98% of our customers. Through all of that, one problem has remained surprisingly consistent. Frontline employees have been left behind by wave after wave of workplace technology. As AI becomes a bigger part of how companies operate, there's a real risk of that happening again. We want to help make sure it doesn't. Thank you to Inspiring Workplaces and the judging panel for the recognition, and especially to the [customers](https://www.mangoapps.com/customers) who continue to trust us and allow us to share their stories. [Read the full 2026 WorkTech Awards announcement](https://www.inspiring-workplaces.com/awards/work-tech-awards/) ## Frequently asked questions ### What are the WorkTech Awards? The WorkTech Awards are run by the Inspiring Workplaces Group and recognize technology companies that help organizations create better experiences at work. Entries are scored by an independent judging panel across five areas, with a maximum of 100 points. ### Who won the 2026 WorkTech Awards? Fourteen technology companies were named 2026 WorkTech Award winners: ChartHop, DailyPay, Envoy, Fama Technologies, Fuel50, Harbinger Group, Hubstaff, Kudos, Logile, MangoApps, Neat, Selerix Systems, Surface and Warp. Winners were announced on October 8, 2026. ### How are the WorkTech Awards judged? An independent panel scores each entry across five areas: the purpose of the business, its investment in the field, its innovation, the measurable results delivered for two named customers, and whether the company practices internally what it sells. Each area carries its own point weighting, totaling 100. ### What awards and analyst recognition has MangoApps received? MangoApps is a 2026 WorkTech Award winner for the second consecutive year. It has been named a Visionary in the Gartner Magic Quadrant for Intranet Packaged Solutions for three years running, a Strong Performer in the Forrester Intranet Platforms Wave for three consecutive years, and a Leader in the IDC Worldwide Employee Experience MarketScape. ClearBox recognized MangoApps as an AI Innovator, Leading Product and Community Builder in its 2026 review. ### What is MangoApps? MangoApps is the AI platform for the frontline workforce. It brings communication, operations, knowledge and governed AI into one app that every employee can open on a phone, whether they work at a desk or on a shop floor, hospital ward, warehouse or job site. The company has been building for frontline teams since 2008 and is used by more than 2 million people. ### Which companies use MangoApps? Leading organizations across healthcare, retail, manufacturing, finance, and more use MangoApps to connect frontline and office teams, improve communication, and get work done. MangoApps customers include AS Watson, AutoZone, Alorica, Caliber Collision, First Student, PetSmart, OU Health, TeamHealth, The YMCA of the USA, among many others. Customer stories are published at [mangoapps.com/customers](https://www.mangoapps.com/customers). --- # Where frontline handoffs lose the thread **Author:** MangoApps Team **Published:** 2026-10-06 **Category:** mango-scoop Explore the credential gap between procedures and schedules, the work order path from request to payment, and the field service management guide. Hand-picked stories from MangoApps this week. ## From SOP to Shift: Closing the Credential Gap on Frontline Teams ![From SOP to Shift: Closing the Credential Gap on Frontline Teams](https://mango-cdn.b-cdn.net/images/blog-thumbnails/blog_804_20261004_140220.png) Frontline compliance rarely fails inside one system. It fails in the handoffs between the procedure, the course, the certification and the schedule, and this week's releases connect those links. [Read the full story →](https://www.mangoapps.com/articles/from-sop-to-shift-closing-the-credential-gap-on-frontline-teams) --- ### More to read #### Fire and Life Safety: The Cycle Is the Contract Mandated inspection cycles, deficiencies that must be quoted first and licensing per technician. What fire and life safety software has to do. [Read more →](https://www.mangoapps.com/articles/fire-life-safety-field-service-software) #### From Request to Paid: The Work Order Lifecycle on One Record A job can be done well and still lose money between the technician, the biller and the scheduler. Six steps from request to payment, and what happens between them. [Read more →](https://www.mangoapps.com/articles/work-order-lifecycle-request-to-paid) #### Utilities and Telecom: Coordinated Field Operations at Scale Multi-state territories, crews in the thousands and regulated trades. Why dispatch and workforce communication are one question at utility scale. [Read more →](https://www.mangoapps.com/articles/utilities-telecom-field-operations-platform) #### Proving a Message Landed: Must-Read, Acknowledgment, and Automatic Re-Sends Open rates only describe the people a message already reached. Message-level acknowledgment, targeted re-sends, and reach by site give communications a number executives can act on. [Read more →](https://www.mangoapps.com/articles/employee-acknowledgment-tracking) --- ### New Resources **Resource** — [Complete Guide to Field Service Management](https://www.mangoapps.com/resources/field-service-management-guide) Late invoices, lost billables, inconsistent quotes, and technicians sent to work they are no longer certified for all trace back to six information gaps. This 64-page book names... --- ### What's New **General** — [Product Update - October 05, 2026](https://www.mangoapps.com/changelog/3354) * **[Still Accurate Content Reviews](https://www.mangoapps.com/key-features/content-governance-engine)** — Owners of overdue SOPs, wiki pages, policies, library items and knowle... **General** — [Product Update - October 04, 2026](https://www.mangoapps.com/changelog/3321) * **[RFP Bid Win/Loss Tracking](https://www.mangoapps.com/directory/app/rfp-desk)** — Mark a submitted RFP bid as won or lost, and a win offers that bid's approved answers back ... --- # From SOP to Shift: Closing the Credential Gap on Frontline Teams **Author:** MangoApps Team **Published:** 2026-10-04 **Category:** safety-compliance Frontline compliance rarely fails inside one system. It fails in the handoffs between the procedure, the course, the certification and the schedule, and this week's releases connect those links. # From SOP to Shift: Closing the Credential Gap on Frontline Teams It is 6:40 on a Saturday morning, and the forklift on the receiving dock has an operator. The schedule says so. What the schedule does not say is that his forklift certification lapsed on Thursday. Nobody hid it. The expiry date was sitting in a spreadsheet the training coordinator updates monthly, the refresher course was in the learning system, and the procedure he was trained on lives in a binder in the break room. Each of those records was right. They just never met. Most compliance failures on frontline teams look like this. They are not cases of someone ignoring the rules. They happen in the handoffs: between the document that describes the work and the course that teaches it, between the course and the credential it earns, and between the credential and the shift that depends on it. Several of the things that shipped this week sit in exactly those handoffs. Taken together, they trace one thread: from the procedure on paper to the person on the floor. ## Start with the binder you already have Every operation has a stack of standard operating procedures, equipment manuals and safety sheets. They are usually accurate, and almost nobody reads them. Turning them into real training has always taken time a training team does not have: someone has to read the document, break it into lessons, write the course and then keep it current. So the binder stays a binder, and new hires learn the job from whoever happens to be working next to them. In MangoApps, Training can now [create a course from a document](https://www.mangoapps.com/changelog/3189). Upload a PDF, or even a photo of a page, and it becomes a draft course organized into lessons. The important word is *draft*. Nobody is enrolled until a person has reviewed it. The AI does the tedious structuring, and the person who knows the work decides whether it is right. That is the right split. A machine is good at turning forty pages into eight lessons. It is not the one who should decide what a new hire needs to know about lockout/tagout. The same idea showed up in Sites, where editors can now [build intranet pages from a document or web page](https://www.mangoapps.com/changelog/3152). They can also review updates when the original web page changes, which deals with the quieter problem of an intranet page that was accurate the day it was published. The other half of training is proving it happened. Most training coordinators know the Monday routine: open the report, set the filters, export it and email it to the site managers who asked for it. [Scheduled training reports](https://www.mangoapps.com/changelog/3189) now send any Training report as a CSV daily, weekly or monthly, with the filters already set. That does not sound dramatic. But a completion report that arrives on its own is one that gets read before an audit rather than built during one. ## The link nobody draws: course to credential to shift This is where the forklift story actually went wrong. In most organizations, completing a course and holding a certification are recorded in two different places, and a person has to connect them. Usually that is someone in HR with a spreadsheet and a good memory. When that person is on vacation, or leaves, the connection breaks without anyone noticing. Admins can now [link credentials to the courses that earn them](https://www.mangoapps.com/changelog/3156) directly from Skills & Certifications. They choose which training courses award a certification, and each credential then shows the course it came from. That second part matters more than it sounds. When an auditor asks how an employee came to hold a credential, the answer is right there on the credential instead of being pieced together from two systems. The other end of the chain is the schedule. The shift page now shows [credential gap warnings](https://www.mangoapps.com/changelog/3156) when a shift is staffed but one of the assigned people has a required license or certification that will have lapsed by the shift date. The key part is "by the shift date." A check that only asks whether someone is certified today misses the forklift operator entirely, because he was certified when the schedule was built. Looking at the expiry against the day of the shift is what turns a credential record into something a scheduler can act on two weeks out, while there is still time to book a refresher or move someone. Coverage itself got easier too. When a coworker needs to step in, they can now [trade shifts that overlap or fall on the same day](https://www.mangoapps.com/changelog/3222). The shift each person gives up is left out of the conflict, daily-hours and rest-time checks. Before this, two people who simply wanted to swap Saturday shifts could be blocked by rules meant to stop overwork, which pushed the swap into a text message and off the record. When the legitimate path works, people are less tempted to work around it. ## The last mile: what the person on shift actually knows Even with the training done and the credentials current, frontline compliance comes down to what an individual knows at the moment they need it. Two releases this week addressed that moment from different directions. The first is a simple question: what am I supposed to have read? A worker can be sent a new safety bulletin, a policy update, an SOP revision and a must-read announcement in the same week, each through a different channel. [Waiting on You](https://www.mangoapps.com/changelog/3152) puts every must-read post, broadcast, alert, policy, page and SOP that someone still needs to read or acknowledge into one Inbox view. For a manager chasing acknowledgments before an audit, that makes it a much shorter conversation. For the employee, it replaces the uneasy feeling of having probably missed something with a list that has an end. The second is getting the details right. Policies are full of specific numbers, such as how many leave days, which date payroll runs and how many hours of notice a schedule change needs. When someone asks an AI assistant about them, a confident wrong number does real damage. With [Policy Key Facts](https://www.mangoapps.com/changelog/3222), AI reads the key numbers and dates out of a policy, and Ask AI answers from them only after a policy manager approves them. The pattern matches the course builder: the machine extracts and a person signs off. The employee asking at 11 p.m. about bereavement leave gets the number the policy owner confirmed, not a guess. The same week, employees gained the ability to [call out sick through Ask AI](https://www.mangoapps.com/changelog/3152), reporting an absence for an upcoming shift in plain language. The open shift can then be offered to other workers. That brings the thread full circle, because the replacement is picked from a schedule that now knows whose credentials will still be valid that day. ## The chain is only as strong as its handoffs Frontline compliance is usually discussed one piece at a time: a learning system, a certification tracker, a scheduling tool, a policy library. Each can be excellent on its own and the operation can still put an uncertified person on a forklift, because the risk is not inside any one of those systems. It lives between them, in the export, the spreadsheet, the monthly reconciliation and the coordinator's memory. What stands out about this week's work is that most of it is about connections rather than new destinations. A document becomes a course. The course awards a credential. The credential is checked against the shift date. The policy's numbers are confirmed by the person who owns them before anyone relies on them. None of these steps is new as an idea, and every compliance manager already does them by hand. The difference is whether they happen on their own or depend on someone remembering on a busy Thursday. That is also why the AI pieces this week were designed the way they were. Each one drafts, extracts or structures, and then stops for a person to approve. Compliance is the one area where "mostly right" is not good enough, so the useful job for AI here is to take on the reading, sorting and drafting, and leave the judgment with the people who are accountable for it. The forklift operator in that opening scene did nothing wrong. The system around him simply was not connected. Fixing that rarely takes another tool. It takes fewer gaps between the tools you already have. --- # Fire and Life Safety: The Cycle Is the Contract **Author:** Andy Tolton **Published:** 2026-10-01 **Category:** field-services Mandated inspection cycles, deficiencies that must be quoted first and licensing per technician. What fire and life safety software has to do. The annual inspection at a mid-rise office building didn't happen on time, because nobody scheduled it. The contract was a PDF in a shared folder, and the person who used to check that folder had moved on. The year before, a technician found a failed device during another visit. It went on a form. The form went into a drawer. This year a competitor quoted the repair. In fire and life safety, the cycle is the contract. Everything the business sells rests on doing the right work on the right date and being able to prove it. ## What the trade demands Four things are true of this work at once: - Mandated inspection cycles at every site you cover. - Deficiency findings that have to become quoted work before somebody else quotes them. - Records that an authority having jurisdiction can ask for at any time. - State licensing per technician, where the wrong technician on a job is a violation. Three things follow for the software. The mandated cycle has to generate its own work. The finding has to become the quote before the technician leaves. And only a technician who can legally do the work should be sent. This article works through each. It isn't regulatory guidance: what applies to you depends on your jurisdiction and the codes your local authority enforces, and your compliance lead is the person to ask. ## Never miss a mandated cycle **How do fire protection contractors track mandated inspection cycles?** The dependable way is to stop tracking them by hand. Agreements hold the coverage, the cycle and the pricing for each site. Inspection work orders generate on that cycle and arrive in the queue ready to assign, so nobody has to remember a mandated date. Site records carry every prior inspection at that location, so the technician arriving knows what the last one found. And agreement billing runs on the same cadence, with each invoice queued for review before it goes out. The important change is who does the remembering. In a document-based process, it's a person, and people change jobs. In a system, the agreement does it. [Recurring revenue that schedules itself](/articles/service-agreements-inspection-work-recurring-revenue) describes the mechanism in full. ## Turn deficiencies into quoted work **How do you quote inspection deficiencies on site?** By making the quote a step in the inspection and not a task afterward. A technician captures a finding on the form on site, with photo evidence. An estimate is built from the price book before they leave the site. The customer approves digitally, on the technician's device or through the portal, and the approved estimate converts to a work order with one click. Open estimates are visible per site, so nothing sits unquoted. That last point is easy to underrate. In a portfolio of hundreds of sites, an unquoted deficiency is invisible unless someone can see all the open ones at once. Having them listed per site turns a memory exercise into a review. The price consistency behind those estimates comes from [one price book](/articles/price-book-on-site-estimates-field-service). ## Send only technicians who can do the work **How do you make sure only licensed technicians are dispatched for fire alarm work?** By having the dispatch board check. Licensing and manufacturer certification are tracked with expiry alerts. A technician whose credential has lapsed is blocked from work that requires it. Inspection records are retained with version history, per site. Code and safety training is delivered on mobile through Training Connect, so a technician can renew without a trip to an office. The reason to build it this way is that alerts alone don't stop a dispatch. The whole argument is in [why an expired certification should block dispatch automatically](/articles/expired-certification-blocks-dispatch). ## Records an AHJ can demand at any time **What records does an AHJ require from a fire protection contractor?** That's set by the jurisdiction and the codes it enforces, and we're not going to interpret them. What we can say is what the software should be able to produce when someone asks. A full service history per site, with photos, notes and parts. Inspection records that are version-controlled, so you can show what was recorded and when. And an audit trail on every work order. The goal is that a request for records is a search and not a project. When the record is the same one the work ran on, you're not reconstructing what happened from three systems and a filing cabinet. It's simply there. ## What the customer sees Your customers, usually facilities and property managers, are accountable for these systems at their own buildings, and they'd like to stop chasing you for paperwork. A portal on the same record lets them see their sites, the work orders and the estimates in one place, under your brand, without calling anyone. One customer account can hold as many sites as it needs, each with its own address, contacts and history. That changes the relationship. The conversation stops being "did the inspection happen?" and becomes "here's what it found, and here's the quote for the two items that need work." It's also the moment an unquoted deficiency stops being invisible to both sides. [When the customer's only status channel is the phone](/articles/field-service-customer-portal-multi-site) covers what that portal has to read. ## What a site record holds for an inspection contractor For a contractor with many sites, the site record is the working memory of the business. It holds every prior inspection at that location, with its photos, notes and parts. It holds the deficiencies found and whether they were quoted, approved or declined. It holds the access notes: gate codes, key locations, parking, where the panel is. And it holds the agreement that sets the cycle, so anyone opening the site can see what's due and when. The value shows up on the technician's phone before they leave the truck. They know what last year's inspector found, which items were replaced and which weren't, and how to get in. The technician who's never been to the building starts from the same place as the one who's been ten times. It matters more as the portfolio grows. At a few dozen sites, a person can carry it. At hundreds, they can't, and the record has to do it. ## Four demos to ask for If you're evaluating software for a contracting business like this, ask to see the following, and don't accept a slide in place of any of them. 1. **A mandated cycle producing its own work order.** Show me the inspection an agreement generated without anyone creating it. 2. **A finding becoming an estimate.** Capture a deficiency on the form with a photo, then price it from the price book before leaving the site. 3. **A lapsed credential refusing an assignment.** Expire a technician's license, then try to assign them to work that requires it. 4. **A site's full history on a phone.** Open a location and show me every prior inspection, its photos and its open estimates. If a vendor can run all four, the cycle really is the contract in their software. [The evaluation guide](/articles/how-to-evaluate-field-service-platform) has the wider set. ## The technician, the dispatcher and the office on one record Nothing above works if the people involved are on different systems. The technician needs an app that works on the site's worst day, which is the subject of [why technicians work around the tools](/articles/why-technicians-work-around-field-service-software). The dispatcher needs a board that knows about cycles and credentials, as [a day in dispatch](/articles/day-in-field-service-dispatch) shows. And the office needs invoices that come from the work, as in [from request to paid](/articles/work-order-lifecycle-request-to-paid). MangoApps Field Service Suite runs all three on one record, inside the same platform as training, HR and communications. For a contractor with hundreds of sites, that's the difference between a system that holds the contract and a person who does. ## The software is part of the compliance record In this trade, the software isn't only a tool. It's part of the compliance record, so evaluate it that way. Ask to see the cycle generate a work order, the finding become an estimate and a lapsed credential refuse an assignment. [The twelve questions](/articles/how-to-evaluate-field-service-platform) and [the six information gaps](/articles/six-information-gaps-field-service) give you the framework, and the demos are the proof. The [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide) includes a one-page breakdown of this trade alongside six others. You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### How do you schedule recurring fire and life safety inspections automatically? Put the coverage, cycle and pricing for each site on the service agreement, and have the agreement generate inspection work orders on that cycle. The work orders arrive in the dispatch queue ready to assign, so no one has to remember a mandated date. ### Can inspection deficiencies be quoted and approved on site? Yes. The technician captures the finding on the form with photo evidence, builds an estimate from the price book before leaving, and the customer approves on the device or in the portal. The approved estimate converts to a work order with one click, and open estimates are visible per site. ### How are inspection records retained for AHJ requests? Inspection records are kept with version history per site, alongside the full service history of photos, notes and parts and an audit trail on every work order. Which records you must keep, and for how long, depends on your jurisdiction, so confirm requirements with your compliance lead. ### Can dispatch block a technician whose fire alarm license has lapsed? It can when work types carry the credentials they require and licensing is tracked on the record the dispatch board reads. A technician whose credential has lapsed is blocked from work that requires it, and the board says so at assignment. In MangoApps, work types carry the certifications they require, and a technician whose credential has lapsed cannot be assigned. The board says so at assignment. --- # From Request to Paid: The Work Order Lifecycle on One Record **Author:** Andy Tolton **Published:** 2026-10-01 **Category:** field-services A job can be done well and still lose money between the technician, the biller and the scheduler. Six steps from request to payment, and what happens between them. A job can be done well and still lose money in the gaps between the person who did it, the person who bills it and the person who books it. The technician does the work properly. The estimate was reasonable. The customer is happy. And somewhere between the driveway and the ledger, an hour is missing, a part isn't on the invoice and the payment arrives three weeks after it could have. Most field service software does some of the lifecycle well. What matters is what happens *between* the steps, because that is where the work goes. This article walks through six steps from request to payment, and for each one, what happens when it lives on one record and what happens when it doesn't. ## The six steps A work order lifecycle is the sequence a job passes through from the moment a customer asks for service to the moment the money is in the books. Six steps cover it: the request arrives, the job is assigned, the work is captured on site, the estimate goes out and comes back, the invoice is ready, and accounting has it. Every gap named in [the six information gaps behind every field service problem](/articles/six-information-gaps-field-service) is a place where one of these hand-offs is done by a person. ### Step 1. The request arrives **On one record:** A customer submits a request through the portal and it lands in the queue as a work order. There is no voicemail to transcribe and no detail lost in someone's handwriting. **When it doesn't:** The request arrives by phone or voicemail, and someone types it up. Details get shortened. Access notes and the actual symptom don't always make it into the ticket. **Gap closed:** The customer's only channel being the phone. See [when the customer's only status channel is the phone](/articles/field-service-customer-portal-multi-site). ### Step 2. The job is assigned **On one record:** The dispatcher sees every technician's workload and their experience with similar work, and assigns from that. No spreadsheet is consulted and no one is asked over the radio. **When it doesn't:** Assignment happens from a mix of memory, a whiteboard and a text thread. The person best suited to the job may not be the one who was free when the dispatcher happened to look. A dispatcher makes more decisions per hour than nearly anyone else in the business, and this is the one that sets up every step after it. [A day in dispatch on one board](/articles/day-in-field-service-dispatch) follows one dispatcher through the whole shift. ### Step 3. The work is captured on site **On one record:** Photos, signatures, notes, parts, materials and time are logged against the work order on the phone, as the work happens. There is no end-of-day pile to type up. **When it doesn't:** The technician writes it down, or plans to, and the details get reconstructed at the end of the day or the end of the week. Time entries drift toward round numbers. Parts that were used but not logged simply disappear. **Gap closed:** What happened on site not being what reaches the bill. This is where most billable work is lost, and it's the least visible place to lose it. ### Step 4. The estimate goes out and comes back **On one record:** The estimate is built from the price book on site, approved on the device and converted to a work order with one click. Nothing is re-keyed, and nobody waits three days. **When it doesn't:** The diagnosis happens on Tuesday and the quote goes out on Friday, built from a price list that may not match what the office would have charged. By then someone else has been out. **Gaps closed:** Inconsistent pricing and slow estimates. The detail is in [the price depends on which technician showed up](/articles/price-book-on-site-estimates-field-service). ### Step 5. The invoice is ready **On one record:** Labor, parts, materials and travel populate at price book rates from what the technician logged, once the job is complete. There is no missing billable line, because the lines came from the work. **When it doesn't:** Someone re-keys the ticket, and each hop is another chance to drop something. Days to invoice depend on how busy the office is. **Gap closed:** The job being done before the invoice exists. Every day the invoice waits is a day your cash is funding work you've already done. ### Step 6. Accounting has it **On one record:** The invoice and its payments sync in both directions with QuickBooks, Sage, NetSuite or another accounting or ERP system. The back office reviews exceptions instead of retyping records. **When it doesn't:** The same invoice is entered twice, once in the field service tool and once in the books, and someone reconciles the two at month end. Ask any vendor which accounting systems they sync with in both directions, by name, and to show one round trip. It's question nine in [our evaluation guide](/articles/how-to-evaluate-field-service-platform). ## What "work order" has to mean for this to work The work order is the system of record for every job: what was done, who did it, when, for whom and at what cost. If it's a form that gets filled in after the fact, the rest of the lifecycle has nothing reliable to build on. If it's the live record the whole job runs through, the invoice, the cost report and the customer's view all come from it. For that to work, a few things have to be true of the work order itself: - It can be created and updated from mobile or desktop, with configurable multi-step workflows and real-time status. - It has templates for common jobs, with pre-filled checklists, standard labor estimates and required documentation for recurring service calls, planned maintenance and warranty work. - Photos, signatures, notes, parts and time attach to it on site and flow onward into invoicing and job costing. - Priority levels, SLA tracking and escalation rules keep urgent work visible. - Every change is in a full audit trail. We list this once and briefly because this article is about the hand-offs, and the Field Service Suite page covers the feature set. The point is that a work order that does all of the above is the thing the six steps hang from. ## Cost capture: where billable work goes missing A technician writes hours and parts on paper. Someone types them into an invoice. Someone else types them into accounting. Every hop is a chance to lose a billable part or an hour of labor, and what goes missing there never shows up as a line item anywhere. That last part is what makes cost capture different from the other gaps. A late invoice is on a report. A part that was fitted, never logged and never billed is on nothing. Nobody knows what they're missing, so nobody goes looking. The fix has three parts. Labor is logged where the work happens, as it's worked, not reconstructed on Friday. Parts and materials are recorded against the work order on site and priced from the price book, so what was fitted is what's billed. And the work order, the estimate and the invoice share one data model, so what the technician captured is what the customer sees on the bill. ## The truck is part of the record too A vehicle is one of the biggest assets in a service business and one of the least tracked. It belongs in the job record for a practical reason: you can't allocate the cost of a job without knowing what it cost to get there. Vehicles are tracked alongside their assigned technician and linked to the work orders they served, with mileage and fuel recorded at checkout. A vehicle marked out of service can't be checked out, so nobody is sent in a truck that isn't roadworthy. Registrations and insurance surface ahead of their expiry dates instead of being discovered at a roadside stop. The point isn't fleet software for its own sake. It's that fuel, mileage and vehicle cost can land on the job they belong to. ## What this looks like from the office For the person who runs the back office, the difference between one record and several is the difference between reviewing and retyping. The invoice is built from the work the technician logged. It's queued for review before it goes out, so nothing bills unreviewed and nothing that was captured gets left off. Exceptions surface before the run rather than after the customer calls. With two-way accounting sync, the back office looks at exceptions, and doesn't re-enter the day's jobs. ## One data layer Underneath all six steps is one data layer: the job, the money, the customer and any agreement covering them share a single set of records. It's the reason the six steps can hand off without a person in the middle. MangoApps Field Service Suite is built on that layer and delivered inside the same platform as communications, HR, learning and AI. A technician's certification, a customer's request and a price change are all facts on one record. If you want to see how that changes a dispatcher's day, read [the day-in-dispatch walkthrough](/articles/day-in-field-service-dispatch). Practically, it also means you don't have to bring everything over at once. Read [we just bought an FSM tool](/articles/replace-fsm-tool-or-consolidate) if you're wondering how to add this to what you already run. ## What to measure If you want to know whether the hand-offs are working, three numbers tell you. Days from job completion to invoice issued shows whether Step 5 is waiting on people. The share of completed jobs with a billing correction after the invoice goes out shows whether Step 3 is capturing what happened. And the number of times any fact is entered more than once between request and payment shows how many hand-offs still depend on someone retyping. You don't need a dashboard for any of them. A sample of twenty jobs and a pen will do for the first pass. ## A demo that settles it If a vendor can show a job marked complete and an invoice ready with nothing typed in between, the rest of the lifecycle is probably on one record too. If they can't, it isn't. That's question one in [how to evaluate a field service platform](/articles/how-to-evaluate-field-service-platform), and it's worth making them do it live. The six steps are part of a longer walk through work orders, dispatch, estimates, invoicing and the customer portal in the [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide). You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### What are the stages of a work order? A work order moves through six steps: the request arrives, the job is assigned, the work is captured on site, the estimate goes out and comes back, the invoice is ready, and accounting has it. On one record, each step hands off to the next without anyone retyping information. Gaps appear wherever a hand-off depends on a person to carry the fact. ### How does field service software generate invoices automatically? The invoice is built from what the technician logged against the work order (labor, parts, materials and travel) at the rates in the price book. Because those lines come from the job itself, nothing is retyped, and the invoice is queued for review before it goes out. The test is to complete a job and see whether an invoice is ready with nothing typed in between. In MangoApps, the invoice is ready at price book rates the moment the job is marked complete. ### What is job costing and why does it fail with paper work orders? Job costing means knowing what a job actually cost in labor, parts, materials and equipment, so you can see its margin. It fails with paper because the details are written down, typed into an invoice and typed again into accounting, and every hop is a chance to lose a part or an hour. What goes missing leaves no trace, so the costs look lower than they really were. ### Can a work order capture photos and signatures offline? Yes. The technician can keep working the work order in a dead zone, and photos, time entries and signatures upload as soon as service comes back. See [why technicians work around the tools](/articles/why-technicians-work-around-field-service-software) for what an app built for field conditions has to do. ### Does the work order sync with accounting software? It should sync both ways, so invoices, payments and completed jobs move between the field service platform and your accounting system with no double entry. Ask any vendor for the named systems that sync in both directions and to show an invoice posting and a payment returning. MangoApps syncs two ways with QuickBooks, Sage, NetSuite and other accounting and ERP systems. --- # Utilities and Telecom: Coordinated Field Operations at Scale **Author:** Andy Tolton **Published:** 2026-10-01 **Category:** field-services Multi-state territories, crews in the thousands and regulated trades. Why dispatch and workforce communication are one question at utility scale. The storm has passed through two states and the crews that will restore power come from three regions and a contractor pool. Before the first truck rolls, a safety bulletin about a downed-line hazard has to reach every one of them, and someone has to be able to say afterward who read it. That's the scale problem in utilities and telecom. The dispatch question and the communication question turn out to be the same question: can you send the right crew, confirm they're qualified, and reach all of them with the right information at once? Service territories span multiple states. Field crews number in the hundreds or thousands. Regulatory requirements are extensive, outages demand coordinated response across teams, and the equipment and documentation are complex enough that crews need real-time technical knowledge in the field. ## Dispatch and manage large field teams **How do utilities coordinate dispatch across multi-state territories?** With one board that covers every region and still lets each region run its own. Map-based dispatch works across multi-state service territories. Skill and certification matching pairs specialized equipment and infrastructure with the crews qualified to work on them. Priority-based scheduling separates outages from planned maintenance, so an emergency is always at the top of the queue. Multi-team coordination uses role-based access by region, so each region has autonomy while data stays shared. The shared data is the important part. A regional supervisor manages their crews, and an operations executive sees the whole territory, and both are looking at one record. [A day in dispatch on one board](/articles/day-in-field-service-dispatch) shows what a single dispatcher's shift looks like on it. ## The storm, step by step Follow one event through a platform where dispatch, credentials and communication share a record. An outage is declared. Priority-based scheduling puts restoration work at the top of the queue in the affected regions, and planned maintenance in those areas yields. The dispatcher, or a regional supervisor with access to that region, sees which crews are available and matches them to the work using skills and certifications for the equipment involved. A crew member whose credential doesn't cover the task doesn't appear as an option. A safety bulletin about the hazard goes out to the crews involved, targeted by region and role, on push, SMS, in-app and email at once. It's marked must-read, so the supervisors can see who has acknowledged it and remind those who haven't. On site, a crew member can ask an assistant trained on the equipment manuals and procedures a question, and get an answer from the documentation. Afterward, the records are there: who was dispatched, what they were qualified for, who acknowledged the bulletin, what was done. Nobody had to compile it from three systems. ## Compliance and safety for regulated industries **How do utilities track certification and licensing for regulated trades?** On the employee record, connected to dispatch. OSHA compliance tracking comes with automated training renewal alerts. Safety inspection forms, incident reporting and corrective actions run on mobile. Certification and licensing tracking covers all the regulated trades in the workforce and connects to dispatch, so eligibility follows credentials. Documentation and records are retained in an audit-ready form. At this scale, the risk in a spreadsheet is bigger, and the spreadsheet is harder to keep current, because there are more people and more credentials to keep track of. The case for putting credentials on the record the board reads is in [why an expired certification should block dispatch automatically](/articles/expired-certification-blocks-dispatch). ## Connect field crews to the rest of the organization **How do you get safety bulletins to thousands of field crews and confirm receipt?** By sending to the crews as a group and asking for acknowledgment. A branded employee app carries corporate communications and safety bulletins on the phone a crew member already has. Targeted communications go out by role, location, certification, region or team, through push, SMS, in-app and email at once. Must-read acknowledgments are tracked, with reminders, so a compliance-critical message has confirmed receipt. In a regulated trade, that's proof and not hope. The same app carries the knowledge crews need. **Can AI assistants be trained on equipment manuals and procedures?** Yes: AI assistants trained on your equipment manuals, procedures and regulations answer from that documentation, on the phone, at the site. Training and onboarding are delivered on mobile at scale, and knowledge management works for thousands of field workers, and reaches beyond the office. That's the same reach that lets the dispatch board work. If crew members don't open the app, the bulletin doesn't land and the work order doesn't arrive. [Why technicians work around the tools](/articles/why-technicians-work-around-field-service-software) covers what makes people open it, and [where AI actually changes a field service operation](/articles/ai-in-field-service-operations) covers the assistants. ## Knowledge that works for thousands of field workers In a workforce this size, the manual and the procedure are the most valuable and least reachable things the company owns. A lineworker in a truck can't scroll through a shared drive. A telecom technician at a cabinet doesn't want to phone the office to ask which revision applies. Searchable procedures, product manuals and safety protocols, reachable from the field through search that spans the company's sources, put the document in the technician's hand. An assistant trained on the same material can answer a specific question from it, and point to where the answer came from. The technician gets what the company has already decided is right, and the company gets one place to keep it current. For how those assistants are built and governed, see [where AI actually changes a field service operation](/articles/ai-in-field-service-operations). ## Security and deployment for a regulated buyer A utility or telecom operator will put a platform through a security review. The facts a reviewer usually wants are these. **Certifications.** HITRUST CSF, SOC 2 Type II and ISO 27001, held together on one system. **Public sector.** A FedRAMP ATO for U.S. public sector, which is relevant for municipal and public utilities. **Deployment.** SaaS, Private Cloud, Customer VPC or On-Premise. The controls that go with the AI are described in [whose permissions does the AI inherit?](/articles/ai-governance-whose-permissions-does-the-ai-inherit). If your organization has specific authorization requirements, confirm them directly with us before assuming they're met. ## Why one platform at this scale Every app added to the platform inherits identity, permissions and integrations, and it doesn't rebuild them. For a workforce in the thousands, that's the difference between a rollout and a program. It also changes who has to be in the room. Each additional vendor brings a contract, an integration and a security review, and each of those happens once per vendor. With one platform, they happen once. MangoApps is The AI Platform for the Frontline Workforce, and Field Service Suite runs on the same platform as communications, learning, HR and AI. That's what lets a certification recorded in one place decide an assignment made in another. ## Questions to ask at this scale Scale changes what a demo has to prove. Ask a vendor to show you the following with volumes that resemble yours, not a ten-person sample. 1. **Regional autonomy with shared data.** Show a regional supervisor seeing only their region, and an executive seeing all of them, from the same record. 2. **A bulletin with acknowledgment.** Send a must-read to a targeted group, then show the list of who has and hasn't confirmed. 3. **Credential matching.** Expire a certification and try to assign that crew member to work that needs it. 4. **An assistant answering from a manual.** Ask a question about a piece of equipment and show where in the documentation the answer came from. 5. **Deployment and security.** Which of SaaS, Private Cloud, Customer VPC and On-Premise fits your requirements, and what the certification scope covers. If any answer relies on a second system, ask how many of your people that second system reaches. ## How many of your crews does your stack reach? At utility scale the adoption question is the coverage question. How many of your crews does the current stack reach? Most organizations have never counted. It's worth counting. A dispatch board no crew opens and a bulletin no crew reads are the same failure. When you're ready to compare platforms on that basis, start with [twelve questions and a scorecard](/articles/how-to-evaluate-field-service-platform). The general version of the argument is in [the six information gaps](/articles/six-information-gaps-field-service), and you can see how this plays out for trades with inspection cycles in [fire and life safety](/articles/fire-life-safety-field-service-software). The [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide) includes a one-page breakdown of this trade alongside six others. You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### How does field service software handle multi-state service territories? With map-based dispatch across the whole territory, role-based access by region so each region can run itself while sharing data, and skill and certification matching for specialized equipment. Priority-based scheduling puts outages ahead of planned maintenance. ### How do you confirm that field crews received a safety bulletin? Send the bulletin as a must-read and track acknowledgments. Messages can be targeted by role, location, certification, region or team and delivered by push, SMS, in-app and email at once, and reminders go to anyone who hasn't confirmed. The tracking gives you a record of who read it. ### Can certification tracking cover multiple regulated trades? Yes. Certification and licensing are tracked for all regulated trades in the workforce, with automated renewal alerts, and connected to dispatch so eligibility follows the credential. ### Is the platform available for public-sector utilities? MangoApps holds a FedRAMP ATO for U.S. public sector and can be deployed as SaaS, Private Cloud, Customer VPC or On-Premise. If you have specific authorization requirements, confirm them with us directly. --- # Proving a Message Landed: Must-Read, Acknowledgment, and Automatic Re-Sends **Author:** Andy Tolton **Published:** 2026-09-30 **Category:** frontline-communication Open rates only describe the people a message already reached. Message-level acknowledgment, targeted re-sends, and reach by site give communications a number executives can act on. *Internal communication has always reported activity, because activity was all the tooling could see. A post went out, a page was viewed, a newsletter was sent. None of that shows the people who needed the message received it. Acknowledgment at the message level does: intensity set per message, confirmation written to the employee record compliance reads from, automatic re-sends to anyone who has not viewed, and reach reported by site and shift. Communication becomes a measured function with a number an executive can act on.* It's 6:45 in the morning and the night charge nurse is handing over to day shift. A protocol change went live overnight. She doesn't know whether the nurses coming on have seen it, and neither does anyone at the health system's headquarters, where the communications report already lists the update as published. Published is true. It is also the least useful fact about that message. ## Why a communications function cannot defend its budget A function that can only report what it sent cannot show what it is worth, so it stays a cost center defending its budget with activity. This is the fifth of the reach gaps, and it is the one that makes the other four hard to see. Without proof, nobody can tell a campaign that worked from one that was wasted. The quarterly review gets a slide of posts published and average open rate, and the executive across the table has no way to connect any of it to what happened on the floor. Look closely at what those metrics measure. Sent counts the act of publishing. Opened and viewed count behavior, but only among people the message could reach in the first place. An open rate is a percentage of recipients, and the question that matters is what fraction of the frontline was ever in that denominator. In Microsoft's frontline research, 63% of frontline workers said messages from leadership do not reach them (Microsoft Work Trend Index Special Report, 2022). A newsletter can post an excellent open rate among the people who were never the problem. That is why [adoption is the denominator](https://www.mangoapps.com/articles/frontline-employee-app-adoption) under every other number in this article. Acknowledgment data from a third of the workforce isn't evidence of reach. It is evidence of which third you reach. The broader argument, that [sending is not reaching](https://www.mangoapps.com/articles/why-frontline-communication-fails), starts there. Once the denominator is real, four mechanisms turn a message into something you can prove. ## Intensity as a setting, not a habit Messages that must be seen need different treatment from the ones that don't, and the way to keep that difference meaningful is to make intensity a setting on the message rather than a habit of whoever writes it. Every communications team has a version of the habit. Capital letters in the subject line. "IMPORTANT" in the headline. A red banner on anything a senior leader sent. Habits decay because nothing enforces them, and within a few months the workforce learns that urgent means "someone in head office felt strongly." MangoApps treats intensity as four levels set per message: Must Read, Acknowledgment Required, Highlight, and a domain-wide banner. Because intensity is a setting, you can write rules about what qualifies and hold people to them. That strictness is exactly what keeps Must Read meaning something. A workable set of rules looks like this. | Level | Use it when | Keep it off | |---|---|---| | Acknowledgment Required | You need each person's confirmation on record: a safety procedure, a clinical protocol, a policy with legal weight | Anything you would not produce in an audit | | Must Read | The message changes what someone does on their next shift, and the supervisor needs to see who has opened it | General news, however senior the sender | | Highlight | It deserves attention but asks for no action, like an enrollment deadline or a site milestone | Anything that needs proof afterwards | | Domain-wide banner | Everyone on the platform needs to see one thing at once, such as a company-wide system outage | Routine announcements, which will teach people to scroll past it | The failure mode is always the same. Mark everything urgent and the label stops working, so when a real stand-down arrives it reads as one more alert in a week of them. A simple discipline helps. Once a month, list the messages that carried the top two levels and ask whether each one changed what somebody did on shift. If it didn't, it should have been a Highlight. ## Acknowledgment as a record, not a report Acknowledgment proves something only when each confirmation is written to the same employee record the compliance view reads from, with no export in between. When an employee confirms a safety notice in MangoApps, the confirmation is captured against that person and lands on the record compliance already uses. There is no nightly file to reconcile, and no window during which the communications tool says one thing and the compliance report says another. This is an architecture point, not a feature point. A survey tool and a compliance tool that each hold their own copy of who the employees are can never answer "who has not confirmed?" without a sync, and a sync describes a moment that is already out of date by the next shift change. We've made the longer case for [what a platform actually means](https://www.mangoapps.com/articles/what-platform-means) elsewhere. Here the consequence is practical. One record means one answer. That answer is visible by site, role, and shift. The difference matters more than it sounds. A company-wide figure tells you acknowledgment is lower than you'd like. A segmented view tells you the second shift at three named distribution centers has not confirmed, and that is a problem someone can go and fix before noon. It also helps to be precise about what acknowledgment is. A read receipt records that a screen opened. Acknowledgment records that a person actively confirmed they have the message, which is a different claim and holds up differently in an audit. Where understanding matters as much as receipt, a short quiz embedded in the post itself adds a comprehension signal alongside the confirmation. ## Boost: going back to the people who did not see it Boost re-sends a message only to the people who have not viewed it, so the follow-up lands where the gap is instead of on everyone. It is set at publish, not remembered afterwards. The author picks the channel for the re-send and the timing, either relative (a set number of hours after publishing) or fixed (before the next shift starts). When the moment arrives, the platform checks who has not viewed the message and goes back to them alone. The "only" is the point. Re-sending to the whole audience punishes the people who did the right thing with a duplicate, and it trains the entire workforce to ignore the second message. After a few rounds, the second message is the one nobody opens, which defeats the purpose of sending it. The supervisor effect is where this pays off on the floor. Picture the store's shift lead ten minutes before the doors open. A policy change went out the night before, marked Must Read and boosted to non-viewers at 5 a.m. By the time the shift starts, the lead can see who has opened it and who has not, and spends two minutes with the four people who haven't instead of thirty minutes briefing everyone. That is what it looks like when [the supervisor stops being the entire channel](https://www.mangoapps.com/articles/frontline-manager-communication-overload) and goes back to supervising. **Download *Frontline Worker Communication & Engagement*.** It walks through intensity, acknowledgment, Boost, and alerts capability by capability, with the reporting that proves each one worked. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) ## Alerts that cannot wait for someone to open an app Emergency alerts need to be a separate class of message with their own channels, permissions, and proof, because a missed alert does not cost you an engagement metric. A site closure, a safety stand-down, an active incident. None of these can depend on a worker happening to open an app between tasks. They need a different delivery model, and the organizations that handle them well built that model before they needed it. ### Every channel, including voice An alert has to reach people wherever they are and whatever they are doing. That means push, SMS, email, in-app, and the screens in break rooms and on the floor, plus text-to-speech voice for the places where reading a phone mid-task is unrealistic: the line worker in gloves, the crew in a bucket truck. What makes this workable is that it is one notification system rather than six. Rules are set once per message type, and every channel writes to the same delivery record. After the alert, you are reading one list of who received it and who confirmed it, not stitching a text-message log to an email report. ### Segmentation under pressure Precision matters more in an emergency, not less. An incident at one facility should reach that facility and the sites connected to it in seconds, targeted by site, region, role, or shift. It should not reach a workforce that has nothing to do about it. Every alert sent to people who did not need to act makes the next alert easier to ignore, and the cost of that shows up at the worst possible moment. ### Prepared before the incident Nobody should be writing the stand-down notice while the stand-down is happening. Templates for the likely scenarios (weather closure, evacuation, a recall, a system outage) are written and approved in advance, each mapped to its audience, along with a clear answer to who has permission to send them. In the moment, the job is to pick the template and confirm the sites. ### Acknowledge, expire, follow up An alert without required acknowledgment is a broadcast. With it, anyone who has not acknowledged within the window is automatically re-sent the notice, and the sites still below target show on a dashboard instead of being discovered afterwards. Alerts also auto-expire, so a resolved emergency does not linger at the top of someone's screen three days later. Comments can stay open where two-way information helps, and a poll attached to the alert gathers status from the floor, which site is clear and which crew still needs help. ### Quiet hours that never block an emergency Frontline workers often reach company communication in shift-limited windows, sometimes on unpaid time, and expecting engagement off the clock is an ethical question as much as a practical one. So respect for time off shift should be configurable, and it should be the default. Non-urgent items batch into digests that wait for the next shift. Urgent classes are exempt. No emergency waits on a quiet-hours rule, which is what lets you be generous with quiet hours everywhere else. Santee Cooper shows what this looks like in practice. The public not-for-profit electric and water utility in South Carolina serves more than two million people, with a workforce spread across offices, generating stations, water plants, and field crew quarters. Its employees named the app The Coop in a naming contest, and communication came first on it: leadership announcements, safety notices, IT alerts, and storm communication. Field workers now receive leadership updates, safety alerts, and recognition posts directly. > "The Coop really gives us the ability to get messages out across the team, immediately. Whether it's a CEO update, a safety alert or just recognizing someone's work, it's all in one place. Employees can scroll through recognitions, see what's happening, and feel connected to the larger organization." > > Jeffrey Straight, Public Relations Specialist, Santee Cooper The app field crews check for everyday updates is the same one that carries the storm alert. That is the argument for running critical communication as part of [internal communications](https://www.mangoapps.com/solutions/internal-communications) rather than as a separate emergency tool nobody has installed. ## Reporting reach by segment, not by average Reach has to be reported by site, role, shift, and tenure, because a company average conceals exactly the variation you need to act on. A healthy-looking company average can be one region at 40% and another at 95%, and those are two completely different problems. The first needs a delivery fix. The second needs nothing. The average tells you neither. Four dimensions carry most of the useful signal. Site shows which locations are drifting while there's still time to address it. Role separates the clinical staff from the environmental services team. Shift catches the classic failure where day shift gets everything and nights get it secondhand. Tenure catches the people in their first weeks, and in a workforce where turnover runs high, that group is never small. Content performance belongs on the same page. For every message and alert, you want delivery, acknowledgment, and response, plus a view of which content is actually used and which is published into silence. The second list is often the more valuable one. A communications team that can see which regular updates nobody reads can stop producing them, and every retired update makes the ones that remain more likely to be read. ## The dashboard for the meeting where budget is decided The dashboard that matters is the one built for the budget meeting, and it reports what the organization received rather than what the team produced. Four numbers do most of the work in that room: - Acknowledgment on critical communication, by site, against target - Training and compliance completion, measured rather than self-reported - Listening follow-through, meaning how many issues employees raised got a visible response - Tool consolidation achieved, in contracts retired None of those is an activity metric. Each one describes something that happened to the workforce or to the budget, and each one can be defended when a CFO pushes on it. The conversation changes character when the communications lead walks in with them. It stops being about how many posts went out and starts being about which sites confirmed the safety procedure and which did not, and what it will take to close the rest. Communication has been funded on faith for a long time. The organizations that stop doing that will not be the ones with the best writers. They will be the ones that can name the four sites below target before anyone asks. Get the capability detail and the reporting model in [*Frontline Worker Communication & Engagement*](https://www.mangoapps.com/resources/frontline-communication-engagement-guide). Score yourself on Gap 5 with [the six-question communication diagnostic](https://www.mangoapps.com/articles/frontline-communication-audit), then [see it configured for your sites](https://www.mangoapps.com/schedule-a-call). *The AI Platform for the Frontline Workforce.* ## Frequently asked questions **How do you track whether employees read a policy update?** Mark the update Acknowledgment Required at the message level and report confirmations by site. Each employee's confirmation is written to their record, so you can see which sites and shifts are below target instead of a single company average. Pair it with an automatic re-send to anyone who has not viewed it, so the follow-up happens without anyone chasing it by hand. **What is message acknowledgment in internal communications?** Message acknowledgment is an employee actively confirming they have received a specific message, recorded against that employee. It differs from a read receipt, which only records that a screen opened. Acknowledgment is a statement by the person, which is why it holds up in an audit. Where understanding matters too, a short embedded quiz adds a comprehension signal. **What metrics should internal communications report to executives?** Report reach by segment, acknowledgment on critical messages, training and compliance completion, listening follow-through, and tools consolidated. Each describes what the organization received rather than what the team produced. Sent counts and average open rates describe activity, and activity is hard to defend when budgets are set. **What is the difference between open rate and reach?** The difference is the denominator. An open rate is the share of recipients who opened a message, while reach is the share of the whole workforce who received it. A newsletter can show a strong open rate among desk staff while most of the frontline never had an inbox to receive it in. **How do you send an emergency alert to employees who do not have company phones?** Send it to their personal phones by push and SMS, to screens on the floor and in break rooms, and by text-to-speech voice where reading a phone is unrealistic. That requires every worker to be provisioned in advance with no corporate email and no password needed. Every channel should write to the same delivery record so you can see who received it. **Should emergency alerts require acknowledgment?** Yes, emergency alerts should require acknowledgment, with auto-expire and an automatic re-send to anyone who has not confirmed. Required acknowledgment is what turns an alert into proof of who knows. Auto-expire keeps resolved emergencies from lingering, and the re-send closes the gap without someone calling down a list. **What is a must-read message?** A must-read message is one marked at a higher intensity level so the platform tracks who has opened it. It should be reserved for messages that change what someone does on their next shift. If everything is marked must-read, the label stops meaning anything, so review monthly what carried it. **How do you re-send a message only to people who have not seen it?** Set a Boost when you publish. The platform checks who has not viewed the message at the time you choose, relative or fixed, and re-sends through the channel you pick to those people only. Everyone who already read it is left alone, which keeps the second message worth opening. **Can quiet hours block an emergency notification?** Not if urgent message classes are exempt from quiet hours, which they should be. Non-urgent items batch into digests for the next shift, while emergency alerts go out immediately on every channel. That exemption is what makes generous quiet hours safe to set for everything else. --- # The Price Depends on Which Technician Showed Up **Author:** Andy Tolton **Published:** 2026-09-30 **Category:** field-services The quote depends on who is holding the phone. How one price book and an estimate approved before the truck leaves close the pricing and approval gaps. Nobody notices the job that was underpriced, because it closed and it got paid. The margin left at the curb never appears as a line item. It just makes the quarter a little thinner than it should have been. That's what makes inconsistent pricing one of the quietest ways a field service company loses money. It has two parts that look separate and share a cause. The price a technician quotes doesn't come from the same place as the price the office bills. And the estimate happens somewhere other than the job site, days after the diagnosis, when the moment has passed. One price book, applied everywhere, and an estimate that's built and approved before the truck leaves the driveway, closes both. ## Gap 3: two quotes for one job The third of [the six information gaps](/articles/six-information-gaps-field-service) is that the price depends on which technician turned up. It happens in three familiar ways. Two technicians quote the same job and give different numbers, because each is working from memory, habit or a rate sheet that was accurate two years ago. A new hire undercharges because they don't know what's normal and they'd rather lose margin than lose the customer. And the parts price in the field differs from the parts price the office bills, so the customer sees one number on Tuesday and another on the invoice. You can put a number on it. Take the highest and lowest quote for the same common job last year, take the difference, and multiply by how often the low one was used. It's one of the six formulas in [what disconnected field service systems actually cost](/articles/cost-of-disconnected-field-service-systems). ## Gap 4: the estimate that arrives days after the diagnosis The technician sees the problem on Tuesday. The quote reaches the customer on Friday. By then, someone else has been out. Why do estimates get sent late? Because the person who diagnosed the problem isn't the person who prices it. The technician takes notes, goes to the next call, and the office builds the quote from those notes when it gets to them. Each hand-off adds time, and a customer's sense of urgency fades faster than most offices assume. The gap is measurable: compare your close rate on estimates approved on site with your close rate on estimates sent later. The difference, multiplied by annual estimate volume and average estimate value, is what waiting costs. We're not going to put a figure on it because the reader's own numbers are the only ones that count. ## What a price book is, and what it is not A price book in field service is the one source that every estimate, invoice and job-cost calculation pulls from. It's not a PDF rate sheet, and it's not a spreadsheet that someone updates when they remember. A rate sheet is something a person looks at. A price book is something the software reads. A useful price book has four properties. **It's centralized.** Parts, labor and service packages live in one list, and every estimate, invoice and job cost calculation pulls from it. Pricing is the same regardless of which technician builds the quote. **It's tiered when it needs to be.** Different customers can have different pricing: preferred customers, residential and commercial, members of a maintenance contract. **Updates are one-touch.** Change a price once, and every technician's app reflects it on their next estimate. There's no re-issuing of a sheet and no waiting for people to install a new version of a file. **It has a history.** You can see what prices were in effect when. That matters for disputes ("what did we charge in March?"), for audits, and for looking at margin trends over time. The last property is easy to overlook and it's the one you'll wish you'd asked for. The first time a customer disputes a charge from six months ago, "what was the price then?" needs an answer that isn't a guess. ## Building the estimate on site With a price book in place, the estimate can move to where the diagnosis happens. A technician builds a full estimate from the job site in minutes, powered by the price book, so the pricing is consistent regardless of who builds it. Branded templates make the quote look like it came from a professional operation, and photos and diagnostic notes attach to support the recommendation. It helps a customer to see the corroded fitting rather than being told about it. Approval happens on the technician's device or in the customer portal. The estimate can offer the customer options to choose between, so the conversation is about which option and not whether. An approved estimate converts to a work order with one click, and nothing is re-keyed. For the office, there's a pipeline view. Estimate history, versioning and reporting by technician, service type and region show where the pipeline is, and win rate by technician and service type shows where the coaching goes. The numbers come from the same record the estimates were built on. The [work order lifecycle](/articles/work-order-lifecycle-request-to-paid) shows where this fits in the six steps, and [a day in dispatch](/articles/day-in-field-service-dispatch) shows what it does for the dispatcher's afternoon. ## What to put in a price book on day one A price book doesn't have to be complete to be useful, and trying to make it complete is the usual reason it stalls. Start with what you sell most. List your twenty most common jobs and price each one as a service package: labor, parts and any standard extras together. Add the parts you use on nearly every truck, with their cost and their price. Decide whether you need tiers on day one. If you have preferred customers or maintenance-contract members who get different rates, set those up early. If you don't, leave them for later. Then retire the old sheet. A price book that lives alongside the PDF quickly turns into two sources, and two sources is the problem you started with. Once every estimate reads from the same list, you'll start to see the things a rate sheet never showed you: which packages win, which lose, and which technician's estimates convert. ## What consistent quotes tell you Once everyone quotes from the same list, the variation that's left is real information. Win rate by technician and by service type tells you where coaching would help and where a package is priced out of the market. Margin trends by service line show which work is worth chasing. And the history of prices in effect means a customer's question about a charge from March has an answer that doesn't depend on anyone's memory. None of this needs a data project. It falls out of the fact that the estimates, the invoices and the price list are one record. ## Where AI fits Drafting an estimate is the kind of queue work that AI can do a first pass on. Describe the job, or name the service type, and the assistant drafts an estimate against your price book. The technician reviews it, adjusts it and sends it. That order matters. The technician stays in charge of what the customer sees, and the price book stays the source of every price. The AI saves the typing and doesn't invent numbers. We cover this, and the other places AI does real work, in [where AI actually changes a field service operation](/articles/ai-in-field-service-operations). ## Agreements price from the same book Service agreements should price from the same list. Agreement rates, estimates and invoices all draw on it, so the work an agreement covers and the extras that fall outside it are priced consistently, whichever technician is on the job. The way agreements generate their own visits and bill on schedule is the subject of [recurring revenue that schedules itself](/articles/service-agreements-inspection-work-recurring-revenue). ## A test for any vendor The demo request is short: change a price, then show me it on a technician's next estimate. A vendor that can't do it has a rate sheet, not a price book. And if the answer to "when does the technician's app show the new price?" involves a sync window, a re-download or a second list, you'll be quoting the old price for a while. This is question three in [how to evaluate a field service platform](/articles/how-to-evaluate-field-service-platform). The price book is one piece of a larger argument about putting every fact on one record, and the [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide) makes that argument end to end. You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### What is a field service price book? A price book is the single source of pricing that every estimate, invoice and job-cost calculation reads from. It holds parts, labor and service packages in one place, can carry different pricing for different customer types, and keeps a history of prices over time. It differs from a rate sheet, which a person consults, in that the software applies it automatically. ### How do you keep pricing consistent across technicians? Give every technician the same source for prices and remove the need to remember or look them up. When estimates are built in the technician's app from the price book, the same job gets the same price whoever quotes it. When a price changes, the change appears on every technician's next estimate without anyone reissuing a list. ### Can a technician create and get an estimate approved on site? Yes. The technician builds the estimate on their phone from the price book, with photos and notes attached, and the customer approves on the technician's device or in the customer portal. Approving on site removes the days of delay between diagnosis and quote that lose jobs to competitors. ### How does an approved estimate become a work order? With one click. The approved estimate is converted to a work order and the lines carry over, so no one re-enters what the customer approved. The job then enters the dispatch queue like any other. ### Does the price book keep a history of past prices? It should. A record of which prices were in effect and when is what lets you answer a customer dispute, support an audit and analyze margin trends. When evaluating a vendor, ask to see the history for a price that has changed. --- # Why Field Service Software Has Been Split Down the Middle for 20 Years **Author:** Andy Tolton **Published:** 2026-09-30 **Category:** field-services Field service tools stop at the job and enterprise platforms stop at the desk. How the space between them got filled by people, and the three changes that close it. For about twenty years, a field service company could buy software from two places, and the person doing the work lived in the space between them. One kind of product was built for the dispatcher's desk. The other was built for the enterprise: a workforce platform with a great deal of capability and a user experience designed for an administrator sitting at a computer. Neither was built for the whole problem, which is a technician on a customer's driveway with gloves on, a dispatcher juggling five tools, and a back office waiting on both. So the gaps got filled by people. That wasn't a failure of effort. Closing those gaps at a price a mid-sized company could justify wasn't possible, and now it is. ## Half one: tools built for the dispatcher's desk Field service management tools are good at what they were designed for. They handle work orders, dispatch and invoicing well. If you need to create a job, send someone, and bill for it, they do that, and it would be unfair to say otherwise. Where they stop is the edge of the job. When a technician's certification expires, the tool doesn't know. When a safety regulation changes, it has no way to reach the person in the field. The technician's training record, their schedule as an employee, the safety bulletin that landed this morning: those live in other systems, or nowhere. These gaps don't show up on a feature comparison chart. They show up in compliance audits, in turnover, and in callbacks. That's why they tend to be discovered late, and by the operations team, not the software committee. ## Half two: platforms built for the office Enterprise workforce platforms went the other way. They have enormous capability, and they usually come with implementations that run a year and consulting fees that can dwarf the license. The user experience is designed for an office administrator. The back office uses it reasonably well. The field team works around it. Desk-first collaboration tools belong in this half too, and it's easier to describe them by architecture than by brand. They assume a desktop, a VPN and a work email address. Those are reasonable assumptions for knowledge workers. They're poor ones for a technician who has none of the three. We won't claim these tools have nothing for the frontline, because that isn't true and it would be easy to refute. The narrower question is more useful: how many of your technicians do they actually reach? Count them. The number tends to settle the argument. ## So the gaps were filled by people Someone re-keyed the work order. Someone chased the parts list. Someone answered the status calls. Someone kept a spreadsheet of who was certified for what, and hoped. These people weren't slow. They were the integration layer. Most field service companies have never priced that layer, which is a large part of why it survived. Knowledge workers switch between 11+ apps a day and lose 4+ hours a week to system switching (McKinsey), and a dispatcher, who is also a supervisor and the first line of tech support, pays more than most. If you're curious what it comes to on your own numbers, we wrote [a guide to the six formulas](/articles/cost-of-disconnected-field-service-systems), and the pattern behind them is in [the six information gaps behind every field service problem](/articles/six-information-gaps-field-service). ## The three things that changed Three developments made it possible to close the gaps without either a year-long implementation or another point solution. Each one alone helps. Together they change what a field service platform can be. ### AI drafts the work that used to sit in a queue An estimate from a description. An invoice from a completed job. A recommendation for who to send. These were the tasks that waited in someone's inbox until they had a spare hour, and AI can do the first pass so that a person reviews rather than starts from scratch. This is also why the platform decision has become a strategic one, and not a feature to compare. An AI assistant is only as useful as what it can see. See [where AI actually changes a field service operation](/articles/ai-in-field-service-operations) for the specifics. ### Mobile puts the whole job on the phone in the technician's pocket For decades, the mobile part of field service software was an afterthought: a reduced version of the desk screen. What has changed is that the entire lifecycle of a job can now live on the phone a technician already carries, including for people who have never had a desk or a company email address. [Why technicians work around the tools](/articles/why-technicians-work-around-field-service-software) covers what that takes. ### A unified architecture lets a fact get entered once The work order, the estimate, the price list, the invoice and the customer's view of all four can share one data model. A fact is entered once and every screen reads it. That's the difference between closing a gap and building a bridge across it, and the next section is about what it does and doesn't mean. For the six steps of a job on one record, see [from request to paid](/articles/work-order-lifecycle-request-to-paid). ## What "built as one system" means, and what it doesn't There is a meaningful difference between a platform designed as a unified system and one assembled through acquisition or bolt-on integration. The first shares a data model. The second shares a login screen. You can usually tell which one you're looking at by asking what happens between two features. If an estimate is approved, does the work order already know? If a certification lapses, does the dispatch board? In a unified system, the answer is yes because both screens are reading the same record. In an assembled one, it's yes only if someone built and maintains a sync between the two. This matters most for AI. An assistant that reads your standard operating procedures but not your dispatch board can't tell a technician whether they're certified for the job in front of them. The knowledge is in one system and the credential is in another, and the assistant can see only the first. That single sentence is a decent test for any vendor's AI story: ask what the assistant can't see. ## How to tell which half a vendor was built in You can learn a lot in a single demo by watching where the vendor's screens end. A tool built in the first half will show you a polished dispatch board and invoice, and it will get vague when you ask about a technician's training record or how a safety bulletin reaches the field. A platform built in the second half will show you breadth, and the technician's screen will feel like the administrator's screen made smaller. Neither is a bad product. Each is an answer to a different half of the question. Ask three things. Where does an employee's certification live, and can the dispatch board see it? What does a technician with no company email see when they first pick up the phone? And when a price changes, how many places does someone have to change it? The answers say which half the product came from, and whether it has crossed over or just added a bridge. ## Why the platform decision is the strategic one Step back and the pattern is simple. Identity, employee data, permissions and integrations are configured once, and every app you add inherits them instead of rebuilding them. You can start with field service and expand when you're ready, with users, data and history carrying forward. There's no second implementation, no migration and no lost context. Every app you turn on is one fewer vendor to manage, one fewer contract, one fewer integration and one fewer security review. For the technician it's one fewer system to learn, which in a trade with a labor shortage is not a small thing. MangoApps was built as one platform, for the frontline, over more than 18 years, and it now serves 2M+ users. It's The AI Platform for the Frontline Workforce, and the Field Service Suite is one of the things you can turn on within it. On the security side, the platform carries HITRUST CSF, SOC 2 Type II and ISO 27001 together on one system, plus a FedRAMP ATO for U.S. public sector, HIPAA and GDPR. ## What to ask a vendor The split was a constraint of the technology that was available, not a law of the category. A buyer today can ask a different question: which half was this vendor built in, and has it crossed over or just bolted on? The best way to find out is to ask for the demos that expose the seams: an invoice with nothing typed between completion and billing, an expired certification that blocks an assignment, a price change that shows up on a technician's next estimate. We've put those, and nine more, in [how to evaluate a field service platform: 12 questions and a scorecard](/articles/how-to-evaluate-field-service-platform). If you already own a field service tool and are wondering what this means for it, [read this next](/articles/replace-fsm-tool-or-consolidate). The longer version of this story, from the two halves of the category to what it takes to close the gaps, is in the [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide), a free download. You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### What is field service management (FSM) software? Field service management software handles the work that happens between a customer's request and a paid invoice: creating and tracking work orders, dispatching and scheduling technicians, estimating, invoicing and recording what happened on the job. Traditional FSM tools were built for the dispatcher's desk. They cover the job well and usually stop at its edges, which is where credentials, training, communication and HR data live. ### What is the difference between an FSM tool and a workforce platform? An FSM tool manages the job. A workforce platform manages the person doing it: their records, credentials, training, schedule, communication and access to AI. The two have historically been separate products from separate vendors. A platform that includes field service on the same data model can connect the two, so that a credential on the employee record is visible to the dispatch board. ### Why do field technicians not use enterprise software? Most enterprise software assumes a desk, a laptop, a VPN and a work email address. Field technicians work from trucks, attics and customer living rooms, and many have no work email at all. When the tool requires what they don't have, they work around it and the business loses visibility into what happened on the job. ### What does "unified data model" mean in field service software? It means the job, the customer, the price list, the invoice and the employee record live in one place that every feature reads and writes, instead of in separate systems synchronized to each other. A fact is entered once. When something changes, such as a price or a certification, every screen that depends on it changes with it. ### Can a field service company start with one capability on a platform? Yes. You can close your biggest gap first, keep the systems you depend on, and add capabilities when you're ready. Because identity, employee data, permissions and integrations are configured once, expanding later is a matter of configuration rather than a new implementation. [Here's how the three paths work](/articles/replace-fsm-tool-or-consolidate). --- # Why an Expired Certification Should Block Dispatch Automatically **Author:** Andy Tolton **Published:** 2026-09-29 **Category:** field-services In a licensed trade, the HR record is an operational record. Why the dispatch board should read credentials and refuse an assignment a lapsed one can't support. It's 2:00 in the afternoon and a licensed job needs covering. The nearest technician is close, free, and no longer certified for that work. Nobody has to remember the expiry date, because the dispatch board won't let them be assigned. The dispatcher picks the next person and moves on. Here is the version most companies live with. Same job, same afternoon, and the board doesn't know. The technician's certification lapsed last month in a spreadsheet, or in the learning system, or in an HR record, and the dispatch tool has never heard of any of them. The technician goes. Nobody notices until an audit, or a customer, or a stop-work order. In a licensed trade, the HR record is an operational record. That's the whole argument of this article, and it has a practical corollary: a certification should be something the dispatch board can read. ## The compliance gap has a shape Credentials are tracked in one place: a spreadsheet, a learning management system or an HR system. Assignments are made in another, the field service tool. Neither reads the other. This is the sixth of [the six information gaps](/articles/six-information-gaps-field-service), and it's the one with the highest stakes and the lowest visibility. Its cost is binary. It costs nothing, for months or years, until there's an audit finding or a stop-work order. Then it costs a great deal at once. That's why it tends to stay off spreadsheets, and why it's the one gap where a company's honest confidence matters more than an average. We show how to think about that number in [what disconnected field service systems actually cost](/articles/cost-of-disconnected-field-service-systems). What the credential is depends on the trade. In HVAC, technicians who handle refrigerants need [EPA Section 608 certification](https://www.epa.gov/section608). In electrical work, state licensing and code training apply. In fire and life safety, licensing and manufacturer certification are tracked alongside the records an authority having jurisdiction may ask for. In utilities, safety training and licensing for regulated trades carry the same weight. We'll take up the trade-specific versions in the articles on [fire and life safety](/articles/fire-life-safety-field-service-software), [electrical contractors](/articles/electrical-contractor-field-service-software) and [utilities and telecom](/articles/utilities-telecom-field-operations-platform). To be clear about what this article isn't: it's not legal advice, and it doesn't tell you what any regulation requires. It describes an operational risk, and how software can help you avoid it. ## Why reminders do not solve it Most companies already have renewal alerts. They're necessary. They aren't enough. An alert informs a person. It doesn't stop a dispatch. The failure happens in the space between the alert and the board, and that space is filled by people who are busy. The dispatcher is also the supervisor, the customer service representative and the first call for tech support. The renewal email went to someone else, or to a shared inbox, or to a manager who was on leave. Nobody in that chain did anything wrong. The system just relied on a memory holding up under load, which memory doesn't do. ## What requirement-aware assignment means The alternative is straightforward to describe. Work types carry the certifications they require. A technician whose credential has lapsed can't be assigned to that kind of work, and the board says so at the moment of assignment, when the dispatcher can still do something about it. Two things follow from that. The rule applies to recommendations, too. When the board suggests a technician for a job, it shouldn't suggest one the credential doesn't support. Governance isn't only about what an AI can read. It's also about what it's allowed to propose. We cover that in [where AI actually changes a field service operation](/articles/ai-in-field-service-operations) and [whose permissions does the AI inherit](/articles/ai-governance-whose-permissions-does-the-ai-inherit). And it works in the other direction. A technician records an EPA recertification on Monday and is dispatch-eligible on Tuesday. There's no phone call to the office and no manual update to a second system. Nobody has to remember to tell the board that someone is qualified again. ## The record has to be one record A dispatch board can only read a credential if the credential lives where the board can see it. That's an architecture question, not a feature one. When HR, learning and recruiting all write to the record the dispatch board reads, compliance stops being a spreadsheet. A few pieces make this concrete: - Certification tracking with expiry alerts, so the people who need to know in advance do. - Training that closes the gap it found: courses assigned automatically by role or location and delivered on the phone, so a technician can renew without a trip to an office. - A role change in the HR system updating access and training assignments together, so a promotion or a transfer doesn't leave stale permissions behind. This is the difference between an FSM tool and a workforce platform, and it's why they're different purchases. A field service tool manages the job. A platform that also holds the employee record can connect the job to the person's qualifications. It's the argument in [why field service software has been split down the middle for 20 years](/articles/field-service-software-split-down-the-middle). MangoApps puts field service on the same platform as People Operations, learning and recruiting, so a certification recorded in one is visible to the other. ## Setting it up: one work type, three credentials The idea is easier to trust once you've seen it applied to one job. Take a single work type, say a refrigerant recovery call. List what a technician needs to be assigned to it: the certification for handling refrigerants, the company's own safety course, and whatever licensing your jurisdiction expects for the work. That list is the requirement. Now the board has something to check. When the dispatcher opens the job, every technician either meets all three or doesn't, and the ones who don't are visibly out of the running with the reason attached. A technician who is two weeks from a renewal is a different case from one whose credential lapsed in March, and the record can tell those two apart. You don't need to model every work type on day one. Start with the two or three that carry the most risk and the most licensing, and add others as you go. In a typical implementation, certification requirements per work type are set in weeks three and four, which is early enough that the pilot crew works against them from their first real job. ## Objections worth answering **"We already track certifications in our learning system."** Good. That's the record. The question is whether the board reads it. A learning system that knows about a lapse and a dispatch tool that doesn't are two systems, and the gap between them is the one this article is about. **"Our dispatchers know their technicians."** They do, and it's a real asset. It also doesn't scale past the next vacation, the next new hire or the next busy day. Knowing someone's history and remembering the exact date a credential lapses are different jobs, and only one of them belongs to software. **"We'd rather trust the technician to tell us."** Most will. The problem isn't honesty. A technician can be unaware their credential lapsed, or believe a renewal was filed that hasn't been processed. A system that checks doesn't accuse anyone. It removes a question nobody should have to answer under pressure. ## What to ask a vendor You don't have to take anyone's word for it. There's a demo that settles it in two minutes, and it's request four of the five we suggest sending before any vendor meeting: > "Expire a certification, then try to assign that technician." Watch what happens. Either the board declines the assignment, or it doesn't. If the answer involves an alert, a report or a manual step, the credential isn't on the record the board reads. Ask two more things while you're there. Whose record does the dispatch board read? And who else writes to it? If HR, learning and the field service tool each keep their own copy, the gap is still open, however good the sync is. This is question seven in [the twelve-question evaluation guide](/articles/how-to-evaluate-field-service-platform). ## The stop-work order you never get When dispatch works this way, audit-ready records with full version history aren't a separate project. They're a byproduct of the way work gets assigned. The order that never arrives is the return on all of it, and it's a hard one to put on a spreadsheet because it's an event that didn't happen. The practical starting point is small. Pick one licensed work type, list the credentials it requires and see whether your current board can tell who holds them today. If it can't, you've found your first gap. For people staffing a seasonal or growing workforce, [the staffing article](/articles/seasonal-licensed-field-workforce) picks up where this one stops, and [the implementation guide](/articles/field-service-implementation-first-90-days) shows how to set the requirements per work type in weeks three and four. The certification question is one of twelve in the evaluation section of the [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide), which also covers the other five gaps. You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### How do you track technician certifications and licenses? Keep certifications and licenses on the employee record with expiry dates and renewal alerts, and make the record readable by the system that assigns work. A spreadsheet works until someone forgets to open it. The stronger approach is a record that HR, training and dispatch all read, so a lapse or a renewal changes what the dispatcher sees without any manual update. ### What is requirement-aware or certification-based dispatch? It means work types carry the certifications they require, and the dispatch board checks the technician's credentials at assignment. A technician whose credential has lapsed can't be assigned to that type of work, and the board says why. When they recertify, they become eligible again without anyone updating a second system. ### Can scheduling software automatically block an uncertified technician? It can if the credential and the schedule live on the same record. If certifications sit in a separate spreadsheet or learning system, the scheduling tool has nothing to check. Ask a vendor to expire a certification in a demo and then try to assign that technician. The result shows whether blocking is automatic or depends on a person remembering. In MangoApps, work types carry the certifications they require, and a technician whose credential has lapsed cannot be assigned. The board says so at assignment. ### How quickly should a recertification update dispatch eligibility? Immediately, once it's recorded. A technician who records a recertification on Monday should be dispatch-eligible on Tuesday at the latest, with no phone call to the office and no second entry. Delays here usually come from a manual step between the training record and the dispatch tool. In MangoApps, a recertification recorded on Monday makes the technician dispatch-eligible on Tuesday. ### Which industries need certification-based dispatch most? Licensed and regulated trades: HVAC, electrical, plumbing, fire and life safety, and utilities and telecom. Any trade where the wrong technician on a job is a compliance problem has the same need. The specifics differ by trade and jurisdiction, so check with your compliance lead about what applies to you. --- # What gets lost between shifts? **Author:** MangoApps Team **Published:** 2026-09-29 **Category:** mango-scoop Explore shift handoffs, the frontline communication guide, and product updates on building Site Pages and delegated sending. Hand-picked stories from MangoApps this week. ## Where frontline context gets lost between shifts ![Where frontline context gets lost between shifts](https://mango-cdn.b-cdn.net/images/blog-thumbnails/blog_706_20260922_142532.png) Explore the hidden cost of lost context, shift handoffs, Recorder and AI Sheets, plus updates to mobile Workspaces and the Content Calendar. [Read the full story →](https://www.mangoapps.com/articles/mango-scoop-2026-09-22) --- ### New Resources **Resource** — [Guide to Frontline Worker Communication & Engagement](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) 63% of frontline workers say messages from leadership do not reach them. This book covers why, what closing the gap requires, and how to make communication a measured function i... --- ### What's New **General** — [Product Update - September 26, 2026](https://www.mangoapps.com/changelog/3152) * **[Build Site Pages from a Document or Web Page](https://www.mangoapps.com/directory/app/sites)** — Turn an uploaded file, a web page address, or pasted text into a finished d... **General** — [Product Update - September 25, 2026](https://www.mangoapps.com/changelog/3151) * **[Delegated Sending in Communications](https://www.mangoapps.com/directory/app/communications)** — Leaders can let an assistant or comms team member send messages on their be... --- # Why Technicians Work Around the Tools **Author:** Andy Tolton **Published:** 2026-09-29 **Category:** field-services Technicians route around software built for the office. What an app built for gloves, dead zones and no company email looks like, and why onboarding is the test. The photo is in a personal text thread. The parts list is on the back of a receipt in the cab. The timesheet, which was due Friday, gets reconstructed from memory on Friday at 4:40. Each of these is a technician solving a problem the software created. They aren't refusing to use the tool. The tool refused them first: it wanted a desk, a login they don't remember, a signal they don't have, and an email address they were never given. That's the thesis. Field technician adoption isn't a training problem. It's a design problem, and it starts with the onboarding flow, not the app. ## The deskless reality Field technicians are the definition of deskless workers. They work from trucks, job sites, attics, basements, rooftops and customer living rooms, and they're never in front of a company computer. According to the Boston Consulting Group's September 2024 report, *Facing Deskless Labor Shortage with Technology*, deskless workers make up 70 to 80% of the global workforce, an estimated 2.7 billion people. Four conditions follow from that, and most field service software ignores at least one: - **They have no desk.** The tool has to work in a truck cab or a crawl space. - **They rarely check company email.** Many have none. Software that assumes an address is asking for something they don't have. - **They can't juggle apps between jobs.** Every extra login and every separate tool is time the technician doesn't have. - **Mobile was an afterthought.** Most field service tools were designed for dispatchers and office staff, and the mobile version shows it. The stakes are real. In skilled trades, a fully productive technician represents a year or more of training and certification. Gallup's 2019 report, *This Fixable Problem Costs U.S. Businesses $1 Trillion*, puts the cost of replacing an individual employee at anywhere from one-half to two times their annual salary. A technician who leaves because the tools made the job harder takes a lot of that investment with them. Organizations with strong internal communications are 4.5x more likely to have engaged employees (Gallup), and in a trade where disengagement is how technicians leave, that matters. ## Where rollouts die Field service implementations fail in one predictable place. The technician doesn't use the app, so the office keeps the old process running in parallel. The new system gets the office's data. The old one, on paper, still has the truth. Nobody plans for that. It happens gradually, as each awkward moment in the field becomes an exception. The technician can't find the job, so they phone. The signal drops, so they write it down. The exception becomes the process. The usual response is training. It rarely works, because training assumes the app fits the work. If a technician has to take three steps to log a part with wet gloves in a dead zone, showing them the three steps again won't fix that. The problem is the steps. ## What "built for field conditions" requires Four things separate an app built for the field from a desk app that fits on a phone. **Built for gloves, dirt and rain.** Large-button interfaces, voice-to-text and one-tap actions. If an action needs a stylus-precise tap or a keyboard, it won't be used at the job site. Dictating a note beats typing it every time. **Offline.** The job doesn't stop for a dead zone. The technician keeps working the work order, and photos, time entries and signatures upload the moment service returns. A basement is not a special case in this work. It's the job. **Evidence capture.** Photos with annotation, signatures on glass, GPS-tagged time entries and audio notes, all attached to the right work order. Each attaches to the job as it happens, which keeps them from ending up in a text thread that only one person can see. **Respect for time.** Push notifications for what matters and not everything. Fields auto-filled from the price book and the work order history. One-tap actions where a form would otherwise be. Every field a technician doesn't have to type is a field they won't skip. ## One app for the entire workday The strongest reason a technician opens an app is that their day is in it. Here's what that looks like across a shift. **Morning.** Today's jobs, routes and supervisor notes are on the home screen. The technician clocks in with GPS. **On site.** The work order is open. Photos are captured, an estimate is built from the price book, signatures are taken, time is logged and notes are dictated. **Between jobs.** The updated schedule is visible, priority changes arrive as push notifications, and customer messages come through the portal. **End of day.** Completed work orders are already in invoicing, the timesheet is submitted and tomorrow is ready. The same app carries the rest of work, too: company news and safety bulletins with acknowledgment tracking, certification courses and short training, searchable procedures and manuals, HR self-service, time and attendance, pre-shift vehicle inspections and incident reporting, and company-trained AI assistants for procedures, troubleshooting, pricing and HR questions. For the technician, it's one tool. For the business, it's one data model across communication, work orders, HR, learning and AI. And because it doesn't depend on a company email address, no one gets left out for lacking one. ## The onboarding flow is the test The quickest way to evaluate any technician app is to look at how a technician gets into it. In a version built for the field, the branded app installs on the technician's own phone. Onboarding is an invite by text message or a QR code. There's no directory entry to create, no VPN and no company hardware. No password. No corporate email. The evaluation question is the one to ask in every demo: what does a technician with no company email see on their own phone? Ask for the onboarding flow and not the app. If the vendor's answer starts with "first, they'll need a company email address," you have your answer. This is question four in [how to evaluate a field service platform](/articles/how-to-evaluate-field-service-platform). ## Three tests you can run on any technician app in an hour You don't need a pilot to find out whether an app was built for the field. Borrow a phone and try these. **The glove test.** Put on the thickest work gloves your technicians wear and try to log a part. If you can't do it without taking them off, the app was designed for a fingertip, and the fingertip isn't in the truck. **The airplane-mode test.** Open a work order, turn on airplane mode, take a photo, add a note and capture a signature. Then turn service back on and watch what happens. The work should have stayed on the phone and then arrived on its own. **The no-email test.** Start from a phone that has never seen the app, with no company email address to enter. See how long it takes to get to a work order, and count the steps that needed something a technician might not have. Each takes minutes, and they cost nothing. They also tell you more than a feature checklist, because they test what happens in the conditions technicians actually work in. ## The office has to adopt it too Adoption isn't only a field problem. If dispatchers and back-office staff keep working from the old process, the technicians notice, and the app becomes a place they enter data for nobody's benefit. The reverse is what you want. When a technician sees that the photo they took is on the invoice, the signature they captured closed the estimate and the time they logged became the timesheet, the app starts to pay them back. People adopt tools that give something back quickly. The route to that feeling is one record: what the technician does on the phone is what the office sees, without a phone call in between. See [from request to paid](/articles/work-order-lifecycle-request-to-paid) for how the record follows the job. ## What adoption looks like when it works MangoApps customers typically see 90%+ adoption within 90 days, including workers with no company email. If employees don't adopt after launch, you don't pay. What drives a number like that isn't a training program. It's peer-led rollout. In a deskless workforce, the strongest predictor of adoption is the pilot crew's own technicians training the next crew, and it's why the pilot crew choice matters as much as it does. We argue that in [your first 90 days](/articles/field-service-implementation-first-90-days). It also depends on the app carrying something the technician wants. A tool that only reports upward is one people tolerate. A tool that carries tomorrow's dispatch, their pay stubs and this morning's safety alert is one they open on their own. MangoApps is The AI Platform for the Frontline Workforce, and the Field Service Suite runs on the same platform as the communications, learning and HR features technicians use every day. Adoption also depends on who's onboarding. A seasonal hire who has an app on their phone on day one is on the schedule days sooner, and [staffing a seasonal, licensed field workforce](/articles/seasonal-licensed-field-workforce) covers that side. ## The alert on the same screen as tomorrow's dispatch The infrastructure that reaches every technician is the same infrastructure that delivers work orders. A safety alert lands on the same home screen as tomorrow's dispatch. When the app that carries the work order also carries the schedule and the payslip, the technician opens it because their day is in it. That's adoption. Everything else in this article is a way of arranging for it. To see how a work order moves from the phone to the ledger, read [from request to paid](/articles/work-order-lifecycle-request-to-paid); to see the view from the dispatcher's chair, read [a day in dispatch](/articles/day-in-field-service-dispatch). And if your technicians already have a tool they barely use, [start here](/articles/replace-fsm-tool-or-consolidate). The technician's workday, from the morning clock-in to the end-of-day timesheet, is laid out in the [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide). You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### Why do field technicians resist new software? Usually because it wasn't designed for their work. Most field service software was built for dispatchers and office staff, with mobile added later. It assumes a desk, a company email address and a reliable signal, and technicians work without all three. When the tool makes a job harder, they route around it, and the business loses visibility. ### What features does a technician app need to work in the field? It needs large-button screens, voice-to-text and one-tap actions that work with gloves; offline access so work continues in dead zones and uploads later; evidence capture including photos, signatures on glass and GPS-tagged time; and fields that auto-fill from the price book and work order history. It also needs to carry the rest of the technician's workday, and not just the work order. ### Can technicians use field service software without a company email address? They should be able to. A well-built app installs on a personal phone and onboards by invite through text message or a QR code, with no directory entry, VPN or company hardware. Access without a password or corporate email is the test of whether a product was built for deskless workers. ### Does the app work offline? An app built for the field should. The technician keeps working the work order when service drops, and photos, time entries and signatures upload when it returns. Ask any vendor to demonstrate it with the phone in airplane mode. ### What adoption rate is realistic for a field workforce? MangoApps customers typically see 90%+ adoption within 90 days, including workers with no company email, and if employees don't adopt after launch, you don't pay. A peer-led rollout, where pilot-crew technicians train the next crew, is the strongest predictor. Ask any vendor for their 90-day number and what they put behind it. --- # The Six Information Gaps Behind Every Field Service Problem **Author:** Andy Tolton **Published:** 2026-09-29 **Category:** field-services Late invoices, missing parts, inconsistent quotes and lapsed credentials look like separate problems. They share one cause, and it starts in six places. Picture one job. A technician is sent on Tuesday to a customer whose heating has failed. She diagnoses it, but her certification for that equipment lapsed last month and nobody's board showed it. She writes the parts and hours on a paper ticket. The quote for the repair reaches the customer on Friday, priced by whoever in the office had a minute, and lower than it should have been. The invoice goes out the following week after someone re-types the ticket, and two parts that were fitted never make it onto it. Late invoice. Missing billable parts. Inconsistent quote. Slow estimate. An unqualified dispatch. It looks like five failures, and it is one. Every one of them is a fact that didn't travel: what the technician did, what it should cost, what the customer was told, who was allowed to do the work. That is what we mean by an information gap, and it is the thesis of this article. Pull on almost any operational failure in a field service business and you'll find one of six places where two systems that should share a fact don't. ## The stack most field service companies actually run The typical mid-sized field service company runs on five to eight systems that don't talk to each other. Work orders and dispatch live in a field service management tool. Scheduling is in another app, or on a whiteboard. Invoicing and financials sit in accounting software, fleet tracking in its own dashboard, and employee communication is a group text, a communication tool or nothing at all. HR and payroll are somewhere else, training and compliance somewhere else again, and spreadsheets fill whatever is left. Each system has its own login, its own data model and its own mobile experience, or none. Job completion data doesn't flow to accounting. Training completions don't flow to dispatch. Fleet location lives in a different screen from the schedule. The business has no single source of truth, so people become the integration layer. Knowledge workers switch between 11+ apps a day and lose 4+ hours a week to system switching (McKinsey). The person who pays the highest price is the dispatcher. They're the supervisor, the customer service rep and the first line of tech support, all in one chair, across most of those systems at once. Each of the six gaps below is a place where that stack breaks. They're numbered because they tend to show up in this order as a company grows, not because the first is the worst. ## Gap 1. The job is done before the invoice exists **Why do field service companies invoice late?** Most of the time it's because the invoice starts from a paper work order that someone has to re-key. The job is finished, and the money can't move until the office catches up. The delay is usually measured in days and often stretches into weeks. Every one of those days is your cash funding work you've already done. Payroll, fuel and parts have all been paid; the customer hasn't been asked to pay yet. What closes it is a work order that closes on site and an invoice that's ready at price book rates the moment the job is marked complete. The full sequence is in [From request to paid: the work order lifecycle on one record](/articles/work-order-lifecycle-request-to-paid). ## Gap 2. What happened on site is not what reaches the bill Hours, parts and materials get written on paper, then typed into an invoice, then typed again into accounting. Every hop is a chance to lose something, and what goes missing leaves no trace. There's no line item for the part that was fitted and never billed. That's what makes this gap hard to see. A late invoice is visible on a report. A missing part isn't on any report, because nobody knows it was supposed to be there. The fix is to capture cost against the work order on the phone, as it happens: labor logged where the work is done, parts and materials recorded on site and priced from the same list the office bills from. Then what the technician captured is what the customer is billed for. More in [the work order lifecycle](/articles/work-order-lifecycle-request-to-paid). ## Gap 3. The price depends on which technician turned up **Why do technicians quote the same job differently?** Because the price they're quoting from isn't the same one. One tech quotes from memory, a new hire undercharges to be safe, and the parts price in the field differs from the one the office bills. Ask two people on the same team what a common repair costs and you'll often get two answers. The gap doesn't announce itself. The job closes, the customer pays, and the margin that was left at the curb never shows up as a line item. What closes it is a single price book: change a price once, and it appears on every technician's next estimate. We go through what that requires in [the price depends on which technician showed up](/articles/price-book-on-site-estimates-field-service). ## Gap 4. The estimate arrives days after the diagnosis The technician sees the problem on Tuesday. The customer gets a quote on Friday. By then somebody else has already been out. This is a timing problem, and timing costs real money: a customer's urgency fades faster than most offices assume. An estimate that's built on site, approved on the technician's device and converted to a work order with one click closes the customer's decision while they're still standing in the room. [The same article on pricing](/articles/price-book-on-site-estimates-field-service) covers how that works in practice. ## Gap 5. The customer's only status channel is the phone The job record knows the technician is on the way. The customer doesn't, so they call, and the dispatcher spends the afternoon answering. Nobody involved is doing anything wrong. The customer wants to know when someone's arriving and the only way to find out is a person. A portal that reads the same record the dispatcher sees removes the reason to call. [When the customer's only status channel is the phone](/articles/field-service-customer-portal-multi-site) goes into what that portal has to read, and what changes for customers with dozens of sites. ## Gap 6. The dispatch board cannot see who is certified Credentials live in one system. Assignments are made in another. So a technician gets sent to work they're no longer licensed to do, and that is an audit finding waiting for a date. In a licensed trade, the HR record is an operational record. If work types carry the credentials they require, a lapsed technician stops being assignable, and a recertification recorded on Monday makes them eligible on Tuesday. This is the gap with the highest stakes, so it gets its own article: [why an expired certification should block dispatch automatically](/articles/expired-certification-blocks-dispatch). ## Why the gaps compound Go back to the Tuesday job. The late invoice, the missed parts, the low quote, the three-day delay and the expired credential aren't five separate events. They're the same failure told five ways. Any one of them alone is survivable. Together they stack on a single job, and there are dozens of jobs a week. None of this needs a catastrophe. It compounds through ordinary weeks, and because each gap is filled by someone quietly working around it (re-keying, chasing, answering the phone), it rarely shows up as a problem to solve. It shows up as "how we do things." That's why most companies have never added it up. If you'd like to, [what disconnected field service systems actually cost](/articles/cost-of-disconnected-field-service-systems) gives you six formulas to run on your own numbers. ## Which gap to find first You don't need a consultant to see which gap is costing you most. Look at where you feel it. If cash is tight even though the schedule is full, start with Gap 1, and pull the average number of days between job completion and invoice. If margins are thinner than the quotes suggest, look at Gaps 2 and 3, and audit twenty completed jobs against what was billed. If you're winning fewer estimates than your technicians expect, it's Gap 4. If your dispatcher can't get through a morning without a queue of status calls, it's Gap 5. And if your compliance lead has ever said "I think everyone's current," it's Gap 6. Most operators find that two or three of the six are live at once, and that they trace back to the same handful of systems. That's useful, because it tells you where a single change does the most work. A price book helps Gaps 3 and 4 together. A work order that captures cost on site helps Gaps 1 and 2 together. Ask the people who do the job as well as the person who owns the budget. The dispatcher knows how many status calls there are. The office manager knows how many tickets get retyped. The technician knows which fields they skip. The gap is usually on the shortlist of things they've already complained about. ## What actually closes a gap There's a difference that matters here. A platform designed as one system shares a data model. A platform assembled through acquisition or bolt-on integration shares a login screen. You can tell them apart by asking what's underneath. In a unified system there's one data layer: one job record and one customer record that every capability writes to and reads from. A gap is only ever a fact that failed to travel, so the way to close it is to stop having two places for the fact to live. The other way is to build an integration for each pair of systems, and then to maintain it. Here is what that looks like, one line per gap: - A work order closes on site, and the invoice is ready at price book rates. - Hours, parts and materials are logged against the job on the phone as they happen. - Change a price once and it shows up on every technician's next estimate. - An approved estimate becomes a work order with one click, and nothing is re-keyed. - A customer's portal request enters the work order queue, and they track the same record the dispatcher sees. - A credential lapses, and the technician stops being assignable. MangoApps Field Service Suite runs on the same platform as communications, HR, learning and AI, which is why those lines can be true at once: the technician's certification, the price list and the customer's request all live on the same record. MangoApps is The AI Platform for the Frontline Workforce, and it has been built for that workforce for 18+ years and has 2M+ users. You don't need all of it on day one. Close your biggest gap first. Skip what you don't need. The article on [whether you have to throw away the FSM tool you already own](/articles/replace-fsm-tool-or-consolidate) explains how that sequencing works. ## The gap that was never a staffing problem For twenty years these gaps have been filled by people, because the infrastructure to close them at a price a mid-sized company could justify didn't exist. That's a big part of why it's been accepted as normal, a story we tell in [why field service software has been split down the middle](/articles/field-service-software-split-down-the-middle). It exists now. The question left for most operators isn't whether the gaps are real. It's which one you close first. If you're in a licensed trade, the answer may already be obvious. See how the same six gaps show up in [fire and life safety](/articles/fire-life-safety-field-service-software), [electrical contracting](/articles/electrical-contractor-field-service-software) and [utilities and telecom](/articles/utilities-telecom-field-operations-platform). To pick a vendor, start with [12 questions and a scorecard](/articles/how-to-evaluate-field-service-platform). To see the platform, look at the [Field Service Suite](/apps/field-service-suite). Want the whole argument in one place? The [complete Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide) covers the six gaps, the cost formulas and the vendor scorecard, and it's a free download with no email required. ## Frequently asked questions ### What is an information gap in field service? An information gap is a place where two systems that should share a fact don't, so a person has to carry it between them. In field service there are six common ones: invoices that wait on paperwork, billable work that never reaches the bill, prices that depend on the technician, estimates that arrive days late, customers who can only get status by phone, and dispatch boards that can't see who is certified. They look like separate problems and usually share one cause. ### Why do field service invoices take so long to go out? The invoice usually starts from a paper work order that someone has to re-key, so it can't go out until the office catches up. Hours, parts and materials are written on paper, typed into an invoice and typed again into accounting, and each hop adds delay and a chance to lose a billable item. Invoicing from the work order at price book rates, the moment the job is marked complete, removes the re-keying. ### How can a technician be dispatched to a job they are not certified for? When credentials are tracked in one system (a spreadsheet, a learning system, an HR record) and assignments are made in another, nothing connects the two except someone's memory. A certification can expire without the dispatcher ever seeing it. If work types carry the credentials they require, the board can refuse the assignment at the moment it's made. ### What is the difference between a unified field service platform and integrated point solutions? A unified platform shares one data model, so a job, a customer and a credential each live in one place that every capability reads and writes. Integrated point solutions are separate products connected to each other, which usually means they share a login screen and a set of sync rules while each keeps its own copy of the data. The difference shows up in the gaps between the products, where copies drift apart. ### Do you have to replace every system to close these gaps? No. Start with the gap that costs you the most, keep the systems you depend on, and expand when you're ready. Accounting, payroll and identity systems can stay in place and connect to the platform. [Read how the three paths work](/articles/replace-fsm-tool-or-consolidate). --- # What Disconnected Field Service Systems Actually Cost **Author:** Andy Tolton **Published:** 2026-09-28 **Category:** field-services Six formulas to put a number on late invoices, lost billables, pricing drift and compliance risk, using your own figures and not a vendor's ROI claim. None of this needs a catastrophe. The costs of disconnected field service systems compound through ordinary weeks: a few days of float on every invoice, a part here and an hour there that never reached the bill, a discount nobody approved because the price was in someone's head. This isn't a vendor ROI claim. There's no percentage in this article for you to believe or dismiss. These are your figures, and the article shows you where to find them. ## Why vendor ROI numbers don't persuade anyone Every field service vendor publishes a percentage. Faster invoicing by so much, more revenue per technician by so much. Nobody inside your business believes those numbers, and they're right not to. The vendor's customers aren't your customers, their jobs aren't your jobs, and the average of a hundred operations tells you nothing about yours. What does persuade a controller or an owner is a number that came from their own books. So the alternative is six formulas, each needing inputs you already have or can pull in an afternoon. The numbers you produce will be smaller or larger than someone else's, and they'll be yours. One caution before you start. These six are the costs of *information gaps*, places where a fact didn't travel between two systems. If you want the explanation of where each one comes from, start with [the six information gaps behind every field service problem](/articles/six-information-gaps-field-service). This article assumes you've met them and want to size them. ## The six line items Each formula is written the way you'd put it in a spreadsheet cell. Use your own figures. ### 1. The invoicing gap **Average daily invoiced revenue × days between job completion and invoice issue = cash permanently in transit.** This is a float cost, not a one-time loss, and the difference matters. You don't lose that money. It's tied up, permanently, in the gap between finishing a job and asking to be paid for it. If you issue invoices nine days after completion, then on any given day about nine days of your revenue is sitting there, financed by you. Shorten the gap and you release that cash once, and it stays released. Where to find the inputs: daily invoiced revenue from your accounting system, and the average gap from the timestamps on completed jobs and issued invoices. ### 2. The capture gap **Take one month of jobs. Find the share where a part, a materials charge or an hour never reached the invoice, then multiply by the average value of what was missed.** This is the hardest one to measure because what goes missing leaves no trace. The way to find it is to audit a sample: pick a month, take twenty jobs, and compare what the technician wrote down, what the van's stock or the supplier invoices say was used, and what the customer was billed. Even a small sample usually finds something. Whatever share you find, apply it across the year's job volume and the average value of the missing item. ### 3. The pricing gap **Find your highest and lowest quote for the same common job last year. Take the difference and multiply it by how often the low one was used.** Pick the job you do most, maybe a standard repair or a maintenance visit, and pull every quote for it. The spread between highest and lowest is the price of not having one price list. Multiply by how often the low quote went out, and you have the margin given away at the curb. ### 4. The approval gap **Take your close rate on estimates approved on site versus estimates sent later. Multiply the difference by annual estimate volume and average estimate value.** If you don't track both rates, start tracking them; the first month's data will be interesting by itself. The difference is what waiting costs. It won't be the same in every trade, and this is one place where your number can differ a great deal from anyone else's, which is exactly why you should use yours. ### 5. The status gap **Status calls per week × minutes per call × the loaded hourly cost of whoever answers.** Have the person who answers the phone count calls for a week, and tag the ones asking where the technician is or what the status of a job is. Loaded cost means wages plus the overhead your finance team already uses. There's also a cost the formula doesn't capture, which is the dispatcher's attention: every call is an interruption in the middle of a decision. ### 6. The compliance gap **The cost of one audit finding or stop-work order in your trade × your honest confidence that every credential is current today.** Think of this one as a probability times a consequence. Ask yourself how sure you are, today, that every technician on the board holds every credential the work they're assigned requires. Not "we have a process," but how sure you are. If you'd put that at 90%, the other 10% times the cost of one bad day is the number. We don't put a figure on penalties here and you shouldn't take one from us; ask your compliance lead what a finding costs in your trade. What matters is that this is the only one of the six that has no cost until the moment it has an enormous one. ## The hidden line: administrative hours There's a seventh cost that doesn't need a formula, only arithmetic. Re-keying, chasing and reconciling take hours, and they belong to real people. Here's a worked example, with the assumptions visible. Suppose four people in your office each spend four hours a week moving information between systems: retyping tickets, matching parts lists, reconciling a schedule against a timesheet. That's 16 hours a week. Over a 50-week year it's 800 hours, or about 40% of a full-time role at 2,000 hours a year. That example is an illustration, not a benchmark. Your team size and your hours will differ, so substitute them. The point is that a small weekly task, repeated by several people, adds up to something you'd notice if it were a job title. Systems that don't talk to each other also cost time in a way that doesn't show up as labor: knowledge workers switch between 11+ apps a day and lose 4+ hours a week to system switching (McKinsey). Every additional tool means another login and another place to look, and a dispatcher who is already the supervisor, the customer service rep and the first line of tech support pays for each one. ## Where the costs hide on the P&L Finance readers should see where each gap lands, because it's rarely a line labeled "information." | Gap | Where it shows up | |---|---| | Invoicing gap | Days sales outstanding and working capital | | Capture gap | Gross margin | | Pricing gap | Gross margin | | Approval gap | Revenue | | Status gap | Selling, general and administrative expense | | Compliance gap | Risk, and not on the P&L until it is | The first four are visible once you know where to look. The last is the odd one out: it costs nothing for years and then costs a lot at once, which is why it tends to stay off spreadsheets. ## What closing the gaps looks like The pattern is always the same: one record instead of several. A job is requested, assigned, captured on site, estimated, invoiced and synced to accounting without anyone retyping it. [The work order lifecycle](/articles/work-order-lifecycle-request-to-paid) lays out the six steps. MangoApps Field Service Suite runs on one data layer shared with the rest of the platform, so the work order, the price list and the customer's view of both are the same record. That's what lets an invoice be ready when the job closes and a lapsed credential stop an assignment. Whether it's the right answer for you is what the [evaluation guide](/articles/how-to-evaluate-field-service-platform) is for. ## The worksheet Copy this into a spreadsheet and fill in your own figures. Every input is something you can pull from your own systems or a week of counting. | Gap | Your inputs | Formula | |---|---|---| | Invoicing | Average daily invoiced revenue; days from job completion to invoice | Revenue per day × days | | Capture | Jobs sampled; share with a missing part, material or hour; average value | Share × average value × annual jobs | | Pricing | Highest and lowest quote for one common job; how often the low one was used | (High − low) × frequency of the low quote | | Approval | Close rate on site; close rate when sent later; annual estimate volume; average value | (Rate on site − rate later) × volume × value | | Status | Calls per week; minutes per call; loaded hourly cost | Calls × minutes ÷ 60 × hourly cost × 50 | | Compliance | Cost of one finding in your trade; your confidence that every credential is current | Cost × (1 − confidence) | Use your own figures. They're the only ones that will persuade anyone in your business. The trade-specific versions matter, too. A fire and life safety contractor's compliance gap and an electrical contractor's differ, and so do their invoicing patterns; see [fire and life safety](/articles/fire-life-safety-field-service-software) and [electrical contractors](/articles/electrical-contractor-field-service-software) for how they see it. ## Once the number exists Once you've added up the six, the conversation inside the business changes. It stops being "should we?" and becomes "which gap first?" That second question has an answer you can defend, because the number is yours. From here, [the evaluation guide](/articles/how-to-evaluate-field-service-platform) gives you twelve questions to put to any platform, and [the six information gaps article](/articles/six-information-gaps-field-service) is the map of where each cost comes from. If the price gap looks largest, start with [one price book](/articles/price-book-on-site-estimates-field-service). If it's the status gap, see [the customer portal](/articles/field-service-customer-portal-multi-site). And if the compliance gap kept you up, [that one has its own article](/articles/expired-certification-blocks-dispatch). The six formulas are also in the [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide), alongside the gaps they measure and a scorecard for comparing vendors. It's a free download with no email required. You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### How do you calculate the cost of late invoicing? Multiply your average daily invoiced revenue by the number of days between job completion and invoice issue. The result is the cash permanently in transit, which is money you've earned and financed but haven't yet asked for. It's a float cost, so shortening the gap releases the cash once rather than saving the same amount every month. ### What is billing leakage and how do you measure it? Billing leakage is billable work that was done but never reached the invoice: a part fitted but not listed, a materials charge missed, an hour not logged. Measure it by sampling. Take a month of completed jobs, compare what the technician recorded and what the stock or supplier records show was used against what was billed, and note the share of jobs where they differ and the average value of the difference. ### What is a reasonable days-to-invoice target for a field service company? It depends on the trade, and any universal number would be invented. What matters is that the invoice is ready the moment the job closes, so the delay comes from your billing cycle and customer terms rather than from re-keying. Measure your own average gap from completion to issue and watch it fall as hand-offs disappear. ### How do you estimate the cost of a compliance gap? Estimate what one audit finding or stop-work order costs in your trade, then multiply by how uncertain you are that every credential on your board is current today. If you're 90% sure, use 10%. It's a risk figure, not a certainty, and it's worth asking your compliance lead for the cost of a finding rather than guessing. ### How do I use these formulas with my own numbers? Copy the worksheet table above into a spreadsheet and fill in the inputs from your accounting system, your job timestamps, your quote history and a week of counting calls. Each formula is written to use figures you either already have or can gather in an afternoon. Nothing here needs an account or an email address. --- # How to Evaluate a Field Service Platform: 12 Questions and a Scorecard **Author:** Andy Tolton **Published:** 2026-09-28 **Category:** field-services Twelve questions that show whether a field service platform will still serve you in three years, each paired with a demo request and a scorecard to keep score. Most field service evaluations end the same way. Three vendors show three demos, every feature list gets a check mark, and the shortlist comes down to price and who the sales rep was. The trouble is that every vendor checks every box. Work orders, dispatch, invoicing, a mobile app: they all have them. What separates the tool that still serves you in three years from the one you're replacing is what happens *between* the features. Whether the invoice builds itself from the job. Whether a price change reaches a technician's phone or waits for someone to update a second list. Below are twelve questions, and each one comes with something to ask the vendor to show you live. Ask the demo request before you score the answer. A vendor can say yes to any question. Showing it is harder. ## How to use this guide Score each vendor from 1 to 5 on every question. The weights are set for you (High for most, Medium for one) and you can change them to fit your operation. Score after the demo, not before. Use it on every platform you evaluate, including ours. The scorecard near the end has a column for MangoApps, and we suggest you leave it blank until you have watched us run the demos. ## One record The first two questions test whether the platform keeps one record of a job or several copies that have to be reconciled. Everything else in this guide gets easier or harder depending on the answer. ### Question 1. Does the invoice generate from the work order, or does someone re-key it? **Ask the vendor to show you:** a completed job and the invoice ready, with nothing typed in between. This is the most useful single question in field service software. If the invoice is built from what the technician logged (labor, parts, materials, travel, at the price list's rates), then days-to-invoice depends on when the job closes. If someone types it from a paper ticket or a photo of one, days-to-invoice depends on how busy the office is that week. Watch for the demo that "auto-creates" an invoice and then needs a person to add the parts. That's a draft, and the work of finishing it is the gap. It's also the first of the six places facts get lost that we describe in [the six information gaps behind every field service problem](/articles/six-information-gaps-field-service), and [the work order lifecycle](/articles/work-order-lifecycle-request-to-paid) walks through what should happen at each hand-off. ### Question 2. Does the customer portal read the same job record, or a copy of it? **Ask the vendor to show you:** change a status on the work order, then refresh the portal. A portal that reads a copy of the job is a second system with a lag. It works until the dispatcher reassigns a technician at 2:00 and the customer is still looking at the 8:00 schedule. Then the customer calls, and the portal has produced the exact phone call it was bought to prevent. The test takes ten seconds and settles it. For more on what the portal has to read, see [when the customer's only status channel is the phone](/articles/field-service-customer-portal-multi-site). ## Pricing ### Question 3. When you change a price, when does the technician's app show it? **Ask the vendor to show you:** change a price, then show it on a technician's next estimate. If pricing lives in a separate list, or in a PDF, or in a tech's memory, two technicians will quote the same job differently forever. The office bills one number and the field quotes another. The right answer is "on the next estimate, without anyone touching a second system." Ask, too, whether the price list keeps a history of what was in effect on what date. You'll want that the first time a customer disputes a charge. The full argument is in [the price depends on which technician showed up](/articles/price-book-on-site-estimates-field-service). ## Frontline access ### Question 4. What does a technician with no company email see on their own phone? **Ask the vendor to show you:** the onboarding flow, not the app. A lot of field technicians have no company email and would rather not use a personal one for work. Many don't carry company hardware either. If the sign-in flow starts with a corporate email address, a directory entry or a VPN, those technicians are locked out on day one, and the office ends up running the old process alongside the new one "just until everyone's on it." Look for an invite by text message or a QR code, an app that installs on a personal phone, and no password or corporate email to remember. Then ask to see it on a phone, not a slide. [Why technicians work around the tools](/articles/why-technicians-work-around-field-service-software) is the long version of this question. ### Question 5. Can a technician build, price and close an estimate on site, and does it convert to a work order without being retyped? **Ask the vendor to show you:** an estimate built on a phone, approved, and turned into a work order. Speed matters here because urgency fades. A customer who hears "we'll send you a quote" on Tuesday has often called someone else by Friday. Ask whether the customer can approve on the technician's device or in a portal, and count the number of times anyone has to re-enter something between "approved" and "scheduled." ## Recurring work ### Question 6. Does a maintenance agreement generate its own scheduled visits, or does someone remember to create them? **Ask the vendor to show you:** the work order an agreement created on its own. If the answer is a calendar reminder, the agreement is a document, not a system. Recurring revenue is the steadiest money in field service, and it's also the easiest to lose, because nothing fails loudly when a visit is missed or an invoice goes out late. The revenue just doesn't arrive. Ask whether the agreement also bills on its own cycle, whether renewals surface ahead of expiry, and whether the price on a covered visit comes from the same list as everything else. [Recurring revenue that schedules itself](/articles/service-agreements-inspection-work-recurring-revenue) goes through each of those. ## Compliance ### Question 7. Can an expired certification block a dispatch automatically? **Ask the vendor to show you:** expire a certification in the demo, then try to assign that technician. In licensed trades, the HR record is an operational record. A technician whose credential lapsed last Tuesday is, on Wednesday, a liability who happens to be nearest to the job. If credentials are tracked in one system and assignments made in another, nothing connects the two except a person's memory. The demo is decisive. Either the board refuses the assignment, or it doesn't. Watch for the answer that involves an alert email: an alert informs someone, and it doesn't stop a dispatch. We take the whole argument apart in [why an expired certification should block dispatch automatically](/articles/expired-certification-blocks-dispatch). ### Question 8. Whose permissions does the AI inherit? If the answer is anything other than the caller's own, the AI can surface data the person asking isn't allowed to see. A technician asks a pricing question and gets a margin they were never supposed to see, because the assistant had broad access to answer quickly. The right answer is that every request runs as the person who made it, returns nothing they couldn't already see, and is logged. Ask where a prompt goes, what is retained, and whether any of it trains a public model. See [whose permissions does the AI inherit](/articles/ai-governance-whose-permissions-does-the-ai-inherit) for the full set of questions. ## Integration ### Question 9. Which accounting and HR systems sync two ways, by name? **Ask the vendor to show you:** an invoice posting to your accounting system and a payment coming back. "We integrate with accounting" tells you nothing. Get the names of the systems that sync in both directions, ask what moves (customers, invoices, payments, completed jobs and their costs), and ask to see one round trip. Ask the same about payroll and your HR system if technician time and credentials matter to you, and they do. For reference, ours is two-way sync with QuickBooks, Sage, NetSuite and other accounting and ERP systems, and with Workday, UKG, ADP, Paylocity, BambooHR and Rippling on the HR and payroll side. Keep the systems you depend on. A good platform connects to them once instead of asking you to replace them mid-season. If the answer to "what happens to our accounting system" is a migration project, that's worth knowing before you sign. ## Security ### Question 10. Which security certifications does the vendor hold on one system, not across acquired products? Certifications only mean what they say if they cover the product you're buying. Ask whether the attestation covers the platform your technicians will use, or a parent company, or a different product in the family. For a platform that carries employee records, customer sites and AI, the bar we'd set is HITRUST CSF, SOC 2 Type II and ISO 27001 together, on one system. Ask about FedRAMP authorization if you sell to or operate in the U.S. public sector, HIPAA with a signed BAA if health data is involved, and GDPR if you have staff or customers in Europe. Then ask how the product deploys: SaaS, Private Cloud, Customer VPC or On-Premise are the four options worth knowing about, and a 99.9% uptime SLA is a reasonable thing to see in writing. ## Expansion and adoption ### Question 11. Can you start with one gap, or does the vendor require an all-at-once rollout? Field service companies don't replace accounting, payroll and identity in one project, and they certainly don't do it in peak season. A vendor that needs everything to go live on the same Monday is asking you to take a risk that has nothing to do with your business. The healthier answer is to close the gap that costs you the most first, keep what works, and add the rest when you're ready. If you're worried about the tool you just bought, [we just bought an FSM tool: are you asking us to throw it away?](/articles/replace-fsm-tool-or-consolidate) answers that directly. ### Question 12. What is your adoption rate at 90 days, and do you back it with anything? Adoption is the number that decides whether any of the other eleven answers matter. A platform that's perfect on paper and unused in the truck is a parallel process with a monthly bill. Here is ours, stated as a fact: 90%+ adoption within 90 days, including workers with no company email. And if employees don't adopt after launch, you don't pay. Ask every vendor the same thing and see what they put in the contract. The way to earn that number is in [your first 90 days](/articles/field-service-implementation-first-90-days). ## The scorecard Score each vendor from 1 to 5 on each row and tally at the bottom. The weights are a starting point. | # | Criterion | Weight | Vendor A | Vendor B | Vendor C | MangoApps | |---|---|---|---|---|---|---| | 1 | Work order to invoice with no re-keying | High | | | | | | 2 | On-site capture of parts, time, photos and signature | High | | | | | | 3 | One price list across estimates and invoices | High | | | | | | 4 | Estimate built and approved on site | High | | | | | | 5 | Two-way accounting sync, named systems | High | | | | | | 6 | Agreements generate their own scheduled visits | High | | | | | | 7 | Expired certification blocks assignment | High | | | | | | 8 | Works for techs with no company email | High | | | | | | 9 | AI governed by the caller's permissions | High | | | | | | 10 | HITRUST, SOC 2 Type II and ISO 27001 on one system | High | | | | | | 11 | Start with one capability, expand without re-doing | Medium | | | | | | 12 | Adoption rate documented and guaranteed | High | | | | | | | **Total (max 60 at equal weight)** | | | | | | A note on the rows: they run in a different order from the twelve questions above, because the scorecard groups by the decision a buyer has to make, and the questions group by what to ask. Copy the table into a spreadsheet and add your own columns. ## Five demo requests to send before the meeting If you only do one thing after reading this, send these five to every vendor on your shortlist a week before the demo. Copy and paste them as they are. > 1. "Show me a completed job and the invoice ready, with nothing typed in between." > 2. "Change a price, then show me it on a technician's next estimate." > 3. "Build an estimate on a phone, approve it, and turn it into a work order." > 4. "Expire a certification, then try to assign that technician." > 5. "Show me the work order an agreement created on its own." Sending them ahead does two things. It gives the vendor time to prepare a real answer, and it tells you a great deal about how they respond to being asked to show rather than tell. ## A vendor that runs these live has nothing to hide behind A vendor who will run all five demos live, on your data and your service lines, has nothing hiding behind the feature list. One who redirects, or shows a slide, or promises a follow-up, has told you something too. We'll run all five on your service lines. [Schedule a demo](/schedule-a-demo) and bring your hardest scenario, or start with the [Field Service Suite](/apps/field-service-suite) if you want to see what we're evaluating you against. If you'd like the twelve questions, the scorecard and the five demo requests in a form you can hand to a colleague, they're in the [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide), a free download with no email required. ## Frequently asked questions ### What is the most important question to ask a field service software vendor? Ask whether the invoice generates from the work order or whether someone re-keys it. Have the vendor show a completed job and the invoice ready, with nothing typed in between. It tests whether the platform keeps one record of the job or several copies, and every other capability (billing accuracy, pricing consistency, customer visibility) depends on the answer. ### How do you test whether field service software works for technicians without company email? Ask to see the onboarding flow on a phone, not the app on a slide. A technician with no company email should be able to install a branded app on a personal phone, get invited by text message or QR code, and get to their work orders without a corporate email address, a directory entry or a VPN. If any step needs one of those, the software wasn't built for that technician. ### Should field service software integrate with accounting? Which systems? Yes. Invoices, payments and completed jobs should move in both directions so the back office reviews exceptions instead of retyping records. Don't accept "we integrate with accounting" as an answer. Ask for the named systems that sync two ways, and ask to watch an invoice post and a payment come back. MangoApps syncs two ways with QuickBooks, Sage, NetSuite and other accounting and ERP systems. ### What security certifications should a field service platform have? For a platform that holds employee records, customer data and AI, look for HITRUST CSF, SOC 2 Type II and ISO 27001 together on one system. Depending on your customers, also ask about FedRAMP authorization for U.S. public sector work, HIPAA with a signed BAA for health data, and GDPR compliance. Ask which deployment options are offered: SaaS, Private Cloud, Customer VPC or On-Premise. ### What adoption rate should you expect from field service software? Ask each vendor for their adoption rate at 90 days and what they back it with. MangoApps customers typically see 90%+ adoption within 90 days, including workers with no company email, and if employees don't adopt after launch, you don't pay. Whatever a vendor tells you, get the number in the contract. --- # A Day in Dispatch on One Board **Author:** Andy Tolton **Published:** 2026-09-28 **Category:** field-services The dispatcher makes the most decisions per hour and gets the worst software. One shift, 6:30 AM to 4:30 PM, on one board instead of six tools. Look at the chair. The person in it answers the status call, covers the no-show, reassigns the no-heat emergency and settles a parts question, all before lunch, and does it across six systems. The dispatcher makes more decisions per hour than anyone else in a field service business and is usually the worst-served by its software. They're also the supervisor, the customer service rep and the first line of tech support, so a tool that costs them a minute costs it a hundred times a day. Knowledge workers switch between 11+ apps a day and lose 4+ hours a week to system switching (McKinsey), and the dispatcher's version of that is worse. Here's the same day on one board, from the 6:30 queue to the 4:30 schedule, in which the dispatcher makes decisions instead of retyping them. ## The timeline ### 6:30 AM: the queue is already built **On one board:** Overnight portal submissions are in the queue as work orders. This week's planned maintenance is there too, generated from the agreements that cover it, ready to assign. **In six tools:** The submissions are voicemails to transcribe, and the maintenance is a spreadsheet of contracts that someone has to check against the calendar. The first hour goes to building the list the software should have built. ### 8:00 AM: the trucks roll out **On one board:** Technicians clock in on their phones. Vehicles are checked out with mileage and fuel recorded, and a truck marked out of service can't be checked out. **In six tools:** The clock-in is a text or a call, the vehicle log is a clipboard, and someone discovers at 9:15 that the van with the bad brakes went out. ### 11:00 AM: the no-heat call **On one board:** A commercial no-heat call comes in. The board recommends a technician based on workload and experience with similar work. The jobs that will be affected are flagged for reassignment, and ETA updates go out to those customers. **In six tools:** The dispatcher scans a map in one system, checks a schedule in another, phones two technicians, then phones the customers whose appointments moved. The decision was quick. The logistics around it took the rest of the hour. ### 2:00 PM: the licensed job **On one board:** A licensed job needs covering, and the nearest technician is no longer certified for it. The board won't let them be assigned. Nobody had to remember the expiry date. The full argument is in [why an expired certification should block dispatch automatically](/articles/expired-certification-blocks-dispatch). **In six tools:** The nearest technician goes, because the board has no idea. The credential lives in a different system, and its expiry was an email that went to someone else. ### 4:30 PM: the exceptions **On one board:** Completed work orders are already in invoicing at price book rates. Tomorrow's schedule is published. Only the exceptions that need a human are left. **In six tools:** The dispatcher leaves at six, after checking that completed jobs have what invoicing needs and rebuilding tomorrow's schedule by hand. ## What the board has to show **What should a dispatch board show?** Enough to make a decision without opening another system. In practice that means five things. **A live map.** Every technician's location, job status and remaining capacity are visible in real time, so assignment decisions rest on current information and not last hour's. **A dispatch board.** Unassigned jobs sit in a queue and are assigned by drag-and-drop or with AI assistance. **Calendar views.** Daily, weekly, team and regional. SLA tracking with escalation alerts warns before deadlines slip, not after. **Customer communication.** ETA and on-the-way notifications trigger from technician status changes, so the dispatcher isn't the messenger. **Best-fit assignment.** The suite recommends a technician based on open workload and experience with similar work, weighing proximity, skills, certification and priority in real time, and sequences the day's stops to cut drive time. The dispatcher decides. The recommendation explains itself. And one more requirement that's easy to miss: requirement-aware assignment. Work types carry the certifications they require, and the board says so at assignment. It's a single paragraph here and a full article in its own right, [linked above](/articles/expired-certification-blocks-dispatch). ## The operations manager's view: the shape of the business, not today's fires If the dispatcher's day is about the next hour, the operations manager's is about the quarter. They need the shape of the business, and that has to come from the same records the dispatcher works from. **What reports should a field service operations manager track?** A useful starting set: - Open versus completed work by technician, team and service type - Revenue from completed jobs and payments received - Estimate pipeline by technician, service type and region - Days-to-invoice and days-to-payment by customer - Work order volume and completion time by service type - Estimate win rate by technician and service type Dashboards are configurable and role-based, and exports to Excel, Power BI and Tableau keep the data portable. Because the numbers come from the same platform the work runs on, month-end close gets faster and executive reporting gets more accurate. Nobody has to reconcile the operations report with the finance one, because they read from the same place. It also opens up natural-language questions. "Which service lines had the longest days-to-invoice last quarter?" is a request an operations manager can ask and get an answer to, with the underlying data. [Where AI actually changes a field service operation](/articles/ai-in-field-service-operations) covers this and the rest of what AI does around dispatch. If any of those measures looks bad, the causes often trace back to the [six information gaps](/articles/six-information-gaps-field-service), and the estimate pipeline in particular comes from [one price book](/articles/price-book-on-site-estimates-field-service). ## Scaling the operation As the operation grows, a few things have to hold up. - **Configurable workflows** for different service lines: installation, repair, maintenance and emergency dispatch don't run the same way. - **Multi-location and multi-team support**, with regional autonomy and shared data. - **Role-based access**, so technicians see their jobs, supervisors see their teams and executives see the business. - **Connected onboarding**, from recruiting through first dispatch. For the last of these, see [staffing a seasonal, licensed field workforce](/articles/seasonal-licensed-field-workforce). For the way the whole sequence hangs together from request to payment, see [from request to paid](/articles/work-order-lifecycle-request-to-paid), and for adding a new crew to a live board, [your first 90 days](/articles/field-service-implementation-first-90-days). ## One board, one data model The dispatcher's board can do all of this because it reads the same record that HR, the technician and accounting write to. A credential recorded in one place, a status changed in the field, a price updated by the office: each is one fact, written once and seen everywhere. MangoApps Field Service Suite is built that way, as part of a platform that also handles communications, learning and HR. That's the difference between a board that displays the schedule and a board that knows the business. ## What the dispatcher stops doing It helps to name the tasks that disappear, because they're the ones nobody logs. They stop retyping a voicemail into a work order. They stop opening a second system to see who's free, and a third to see who's qualified. They stop phoning customers to tell them a technician is running late, because the notification goes out when the status changes. They stop reconciling completed jobs against invoices at the end of the day. And they stop being the only person who knows why the schedule looks the way it does, because the board shows it. None of those is a decision. Each is a piece of transcription that a person does because two systems don't share a fact. When they go, what's left is the judgment the dispatcher was hired for: who to send, what to move, what can wait. ## Five things to ask on a dispatch demo Ask to see each of these live, with your own service lines if possible. 1. An emergency job entering the queue, and how the board proposes an assignment and shows its reasoning. 2. A job being reassigned, and what happens to the customer's ETA and to the technician's next stop. 3. A technician whose certification has lapsed, and an attempt to assign them to a job that needs it. 4. A vehicle marked out of service, and an attempt to check it out. 5. Yesterday's completed jobs, already in invoicing, and the exceptions that need a person. If a vendor can do all five without leaving the board, the dispatcher's day probably looks like the one above. If it takes a second system for any of them, count it as one of your six tools. ## What the afternoon of status calls is worth The dispatcher is the user whose time compounds most across the company. Every minute they don't spend retyping or answering a status call is a minute spent on the decision that's actually theirs. Software that gives them back the afternoon is worth more than any single feature on the technician side. If you're building a case for it, the evaluation guide has [twelve questions to put to any vendor](/articles/how-to-evaluate-field-service-platform). The dispatcher's day, the operations manager's reports and a role-by-role view of the same platform are in the [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide). You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### What is a dispatch board in field service? A dispatch board is the screen a dispatcher uses to see open jobs, technician locations and availability, and to assign work. A good one shows a live map, a queue of unassigned jobs, calendar views by day, week, team and region, and SLA warnings, and it triggers customer notifications as technician status changes. It's most useful when it reads the same record as accounting, HR and the technician's app. ### How does AI-assisted dispatch choose a technician? The suite recommends a technician based on open workload and experience with similar work, weighing proximity, skills, certification and priority in real time, and explains its reasoning so the dispatcher can decide. Requirement-aware assignment adds a check on credentials: a technician whose certification has lapsed shouldn't be assignable to work that requires it. ### What KPIs should a field service operations manager track? Start with open versus completed work by technician, team and service type; revenue from completed jobs and payments received; estimate pipeline and win rate by technician and service type; days-to-invoice and days-to-payment by customer; and work order volume and completion time by service type. ### Can dispatch software prevent assigning an uncertified technician? It can when work types carry the certifications they require and the technician's credentials live on the record the board reads. A technician whose credential has lapsed can't be assigned, and the board says why at the moment of assignment. Ask a vendor to expire a certification in a demo and then try to assign that technician. In MangoApps, work types carry the certifications they require, and a technician whose credential has lapsed cannot be assigned. The board says so at assignment. ### Can I export field service reports to Power BI or Tableau? Yes. Dashboards are configurable and role-based, and reports export to Excel, Power BI and Tableau, so the data stays portable and can be combined with the rest of your reporting. --- # When the Customer's Only Status Channel Is the Phone **Author:** Andy Tolton **Published:** 2026-09-27 **Category:** field-services Customers call because the job record can't reach them. What a portal has to read, and how one account holds forty sites, access notes and service history. Picture the dispatcher's afternoon. It's 2:30, and the queue of things waiting for a decision includes a reassignment, a parts delay, and eleven voicemails. Nine of the eleven are the same question in different words: *where's my technician?* The system knows. The job record says the technician is on the way, and roughly when they'll arrive. The customer doesn't have access to that record, so the only way to find out is to ask a person. That's the thesis of this article. The customer is calling because the record can't reach them. ## Gap 5, and what it costs The fifth of [the six information gaps](/articles/six-information-gaps-field-service) is that the customer's only status channel is the phone. A customer needs service and they call. They want a status update and they call. They want to pay an invoice and they call. The visible cost is easy to compute: status calls per week, times minutes per call, times the loaded hourly cost of whoever answers. It's one of the six formulas in [what disconnected field service systems actually cost](/articles/cost-of-disconnected-field-service-systems). The cost that doesn't appear in the formula is the dispatcher's attention. A call about a status check comes in the middle of deciding who covers a no-heat emergency. The interruption is small each time, and there are a lot of them. ## What a portal has to read **What is a customer portal in field service management?** It's a branded, self-service site where customers submit requests, follow jobs, review estimates and invoices, and see their service history without calling anyone. What matters most is what it's connected to. The question to ask is whether the portal reads the same job record the dispatcher sees, or a copy of it. A copy is a second system with a lag, and a lagging portal produces the calls it was meant to prevent. A portal that reads the live record means the customer sees what the dispatcher sees. A useful portal covers the whole service relationship: - **Service requests** go straight into the work order queue, with no voicemail to transcribe and no detail lost. - **Real-time job tracking** shows scheduled, on the way, on site and completed as it happens. - **Estimates and invoices** can be reviewed and approved, and invoices can be viewed and paid, with service history visible by property or location. - **Branding** is per customer account, so the customer sees your company and their own sites. Behind the portal, automated ETA and on-the-way notifications go out when a technician's status changes, so the customer hears about the change before they'd think to ask. ## Residential is one address. Commercial is forty. Residential work is one address and one decision-maker. Commercial work is a property group with forty sites, three people who can authorize a repair, and a facilities director who expects you to know the building. Software built around the single service call can't hold that shape, so the office holds it instead. Someone in the office knows that the north campus needs a different contact than the south, and that the loading dock on site twelve is the only door open after six. That knowledge lives in a person's head, which is fine until they're out. **How should field service software handle a customer with many locations?** With a customer account that holds as many sites as it needs. ### Many sites, one customer Each site has its own address, contacts and history. A chain and a single location use the same structure. The customer is one record for billing and relationship, and the sites are as many records as service requires. A quote can be for one, the dispatch goes to the right site, and the invoice goes to the parent. ### Full service history per site **What is a site record in field service?** It's everything that has happened at one location: every prior work order, with its photos, notes and parts. It's on the technician's phone before they get out of the truck, so the person arriving knows what the last visit found, what was replaced, and what was recommended and declined. ### Access notes that save the first twenty minutes This is the detail people underestimate and technicians remember. A gate code. Where the key is kept. Which parking area is for service vehicles. That there's a dog on site, and that it's friendly except at the back door. Access notes get worked out by whichever technician first ran into the problem, usually after twenty minutes of phone calls. The right way to keep them is to capture them once, on the site record, by the technician who worked it out, so they're available to whoever goes next. The second technician to visit doesn't spend the first twenty minutes calling the office to ask what the first one learned. It sounds small and it isn't. Multiply twenty minutes by every first visit to every new site and it's a large amount of paid time that nobody logs as lost. ## One portal per account, covering every site For a commercial customer, the portal is scoped to the account and not the visit. The facilities director sees their sites, work orders, estimates and invoices in one place, under your brand, without calling anyone. Property management is the clearest example. Tenants submit maintenance requests directly, with no phone call. Owners see reporting dashboards configured for their needs. Work orders are organized by property, unit and tenant, each with its full service history. The property manager gets fewer inbound calls, and the tenant gets a request that's tracked from submission to completion. The same structure fits a retail chain, a hospital campus or a school district: one relationship, many locations, and a single place for the customer to look. (Property management is a subject of its own and we'll leave it as a worked example here.) ## Three people who can authorize a repair Commercial customers have a habit that residential software rarely handles: several people can say yes, and they don't all have the same authority. A site manager can approve a small repair. A regional facilities director approves anything larger. Accounts payable wants the invoice, and doesn't want to hear about the work. A customer account that holds its own contacts for each site gives the office one place to record who is who. The map stops living in a spreadsheet or in someone's memory, and the technician standing in a lobby can see who to ask. It also changes the first call. When a customer with forty locations phones about site nineteen, whoever picks up sees the site's history and its contacts before they say hello. ## How to know it's working You can measure a portal the way you'd measure any process change. Count status calls per week before and after. Watch the days between an estimate being sent and approved, since a customer who can approve from a link doesn't have to call back. And ask technicians how often they lose the first part of a visit to a locked gate or a missing contact. If the number of each falls, the record is reaching the people who need it. ## Why this only works on one record The portal works because of what's underneath. A request enters the queue as a work order. The customer tracks the same record the dispatcher sees. The invoice they pay came from the work the technician logged on site. If any of those is a copy, the portal is a view of something that might be out of date, and the calls come back. On one record, there's no lag to explain. MangoApps Field Service Suite is built that way, on the same data layer as the rest of the platform. The [work order lifecycle article](/articles/work-order-lifecycle-request-to-paid) traces one job through all six steps, and [recurring revenue that schedules itself](/articles/service-agreements-inspection-work-recurring-revenue) shows how site-level agreements and inspections use the same site record. ## A portal is read access to the record you already keep A portal isn't a customer-experience feature. It's the customer's read access to the record you already keep. If the record is right, the calls stop. If it isn't, a portal will show the customer exactly how wrong it is. That's the test to put to any vendor: change a status on the work order, then refresh the portal. It's question two in [how to evaluate a field service platform](/articles/how-to-evaluate-field-service-platform). The portal and site records are covered alongside the rest of the suite in the [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide). You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### What can customers do in a field service portal? They can submit service requests that land directly in the work order queue, track a job as it moves from scheduled to on the way to on site to completed, review and approve estimates, view invoices, make payments, and see their service history by property or location. The portal can be branded per customer account, so a commercial customer sees all of its sites in one place. ### How does a portal reduce inbound calls? Most inbound calls in a service business ask for status, a quote or an invoice. When customers can see the live job status, review estimates and view invoices themselves, and when automated ETA notifications tell them a technician is on the way, the reasons to call go away. The portal only works if it reads the same record the dispatcher sees. ### How should software handle one customer with many service locations? With a customer account that can hold as many sites as needed. Each site has its own address, contacts and service history, while billing and the relationship sit with the customer. A chain and a single location use the same structure, and a customer's portal can show all of its sites and their work in one place. ### What are site access notes and why do they matter? Site access notes are details a technician needs to get in and work: gate codes, key locations, parking, hazards or a dog on the property. They matter because without them each new technician spends the first twenty minutes working out what the last one already knew. Capturing them once on the site record makes them available to whoever goes next. ### Can customers approve estimates and pay invoices online? Customers can review and approve estimates and view invoices and make payments through the portal, with the approved estimate converting into a work order. --- # Recurring Revenue That Schedules Itself **Author:** Andy Tolton **Published:** 2026-09-26 **Category:** field-services Agreements in spreadsheets bill late and lapse, and inspection findings go unquoted. How agreements that generate their own work fix both leaks. Ask how a maintenance agreement creates its scheduled visits, and listen for the answer. If it's a calendar reminder, the agreement is a document, not a system. That's a hard sentence for an owner to hear, because most agreements are documents. They live in a folder, or a spreadsheet, or a field in a CRM. Someone remembers to create the visit, someone else remembers to bill it, and the renewal date is a note that gets read the week it expires. Two leaks follow, and they're the subject of this article: the planned visit that everyone forgot, and the finding that nobody quoted. ## Where recurring revenue leaks Every owner knows the difference between a business that lives on inbound calls and one that knows what next quarter looks like. Service agreements are that difference. They're also the thing most likely to sit in a spreadsheet, bill late and quietly lapse. The leaks come in two kinds. Agreements in a spreadsheet lead to late billing, missed visits and lapses at renewal that nobody noticed until the customer stopped calling. Inspection findings on a form that nobody reopens lead to repair work that never gets quoted. They have one thing in common, and it's why they last: nothing fails loudly. A missed visit doesn't set off an alarm. An unquoted finding isn't on any report. The revenue simply doesn't arrive, and it isn't obvious why. ## Agreements that generate their own work **How do maintenance contracts generate work orders automatically?** The agreement holds the coverage, the cycle and the pricing for each site. On the service cycle, a scheduled maintenance work order is created and arrives in the dispatch queue ready to assign. That's the difference between a system and a document. Nobody has to remember. A planned visit is never the thing everyone forgot, because the visit is created by the agreement, not by a person looking at a calendar. For the dispatcher, it changes the start of the day. The week's planned maintenance is already in the queue by 6:30 in the morning, next to the overnight portal requests. [A day in dispatch on one board](/articles/day-in-field-service-dispatch) follows one dispatcher through that morning. ## Billing on the same cadence Agreement billing runs on your cycle. Each invoice is built from the work delivered, and it's queued for review before it goes out. Nothing bills unseen, and nothing gets missed. The review step matters. Recurring billing that goes out unreviewed sends the customer an error the first time something changes. Recurring billing that depends on someone remembering to run it is late. Generating the invoice on schedule and holding it for a person to look at avoids both. ## Renewal before expiry Renewal dates surface ahead of time, with the service history attached. The conversation with the customer is then about what was delivered and not what was promised. That's a better position to negotiate from. "Here are the fourteen visits we made, the two deficiencies we found and the work that came out of them" is a stronger renewal than "your contract is up next month." ## Priced from the same price book Agreement rates come from the same list as estimates and invoices, so covered work and billable extras price consistently, whichever technician is on the job. An extra that falls outside the agreement is priced as it would be for anyone else, not from whatever the technician remembers. The argument for one list is in [the price depends on which technician showed up](/articles/price-book-on-site-estimates-field-service). ## The finding becomes the quote becomes the job Inspection work is the most reliable revenue in field service and the most commonly leaked. A technician finds four things wrong and writes them on a form. Two get quoted. One gets quoted three weeks later. The fourth is found by the next inspector, a year on. **What is deficiency work in inspection services?** It's the repair or remedial work that an inspection finds is needed: the failed device, the missing component, the item that doesn't meet a standard. It's the work that follows the inspection, and it's often worth more than the inspection itself. **How do you stop inspection findings from going unquoted?** By making each step hand off to the next without a person in between. The sequence looks like this. **The inspection schedules itself.** Coverage and cycle sit on the agreement, and the inspection work order generates on that cycle, ready to assign. Nobody has to remember a mandated date. **Digital inspection forms run on mobile.** The checklist runs in the platform your operation is already on, with photo evidence and signatures captured on site. **Findings attach to the site record.** A deficiency is recorded against the location where it was found, so it sits with that site's history and not in a form nobody reopens. **It's quoted before the technician leaves.** The finding becomes an estimate from the price book, with the photo attached, and the customer approves on the device or in the portal. **Approved work becomes scheduled work.** An approved estimate converts to a work order with one click, so remedial work enters the queue and not a follow-up list. Each step of that chain is small. The value is in the chain: no step depends on someone's inbox. ## Where this matters most Fire and life safety is the clearest example. The cycle is the contract: mandated inspection cycles at every site, deficiencies that have to become quoted work before somebody else quotes them, and records an authority having jurisdiction can ask for at any time. An inspection that nobody scheduled because the contract lived in a PDF is a missed obligation. A deficiency found last year that a competitor quoted this year is a lost job. Both are what happens when the agreement is a document. We take the trade in detail in [fire and life safety: the cycle is the contract](/articles/fire-life-safety-field-service-software). The same pattern applies elsewhere. HVAC maintenance agreements drive recurring revenue and smooth out seasonal swings. Landscaping runs on recurring contracts on fixed cycles, where route density decides the margin. Property management has preventive maintenance cycles across a portfolio. In each case, the question is the same: does the schedule generate the work, or does a person? ## How to tell if you have an agreement problem Few operators think they have one. These are the signs. A customer tells you a scheduled visit didn't happen, and you find out from them and not from your own records. Someone asks "when did we last service that site?" and the answer takes a phone call. Renewals get noticed in the week they expire, or after. An invoice goes out late because the person who runs recurring billing was on leave. You can't say off the top of your head how many open findings you have across your inspection customers. Any one of these is ordinary. Two or three together mean the agreement is a document, and the business is relying on memory to turn it into work. ## What to load first When you set agreements up in a system, start where the revenue is most reliable and the cost of a miss is highest. Load the agreements with mandated cycles first, since a missed date there has consequences beyond revenue. Put the coverage, the cycle and the pricing for each site on the agreement, and check that the first generated work orders look the way your dispatcher expects. Then bring in the rest of your maintenance contracts, and finally the renewals calendar. Have your team review the first generated visits before any customer sees them. ## Why this needs one record The agreement, the visit it generated, the finding, the quote, the work order and the invoice all sit on one data layer. That's what lets a visit come from an agreement, a finding come from a visit and an invoice come from the work, without anyone carrying facts between systems. MangoApps Field Service Suite is built that way, on the same platform as communications, HR, learning and AI. For an operator with mandated cycles, the same platform also holds the technician's credentials that decide who can do the work, and [that's a separate argument](/articles/expired-certification-blocks-dispatch). It also means agreements and the customer's portal are connected: the customer can see the visits their agreement covers, and the site record they read is the one your technician reads. See [when the customer's only status channel is the phone](/articles/field-service-customer-portal-multi-site). ## The demo that shows it There's a short way to test any platform on this. Ask the vendor to show you the work order an agreement created on its own. Not a reminder. Not a task. The work order, in the queue, ready to assign, with nobody having created it. This is question six in [how to evaluate a field service platform](/articles/how-to-evaluate-field-service-platform), and it separates agreements that are systems from agreements that are files. If you work in a licensed trade, [the electrical](/articles/electrical-contractor-field-service-software) and [utilities](/articles/utilities-telecom-field-operations-platform) articles show how it plays out in those trades. Agreements, inspections and deficiency work each get their own section in the [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide), a free download. You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### What is a service agreement in field service software? A service agreement is a recurring contract that defines the coverage, service cycle and pricing for each customer site. In field service software it should do more than record terms: it should generate scheduled work orders on the cycle, bill on the agreed cadence, and flag renewals before they expire. If someone has to remember to create the visits, the agreement is a document and not a system. ### How do maintenance agreements create work orders automatically? The agreement holds the cycle for each site. On that cycle it generates a scheduled maintenance work order that lands in the dispatch queue ready to assign. To check it, ask a vendor to show you a work order that an agreement created without anyone touching it. ### What is deficiency work and how should it be quoted? Deficiency work is the repair or remedial work an inspection finds is needed. It should be quoted before the technician leaves the site: the finding becomes an estimate from the price book with the photo attached, and the customer approves on a device or in the portal. Approved work then converts to a work order with one click so it enters the schedule instead of a follow-up list. ### How do you manage service contract renewals? Surface the renewal date ahead of expiry and attach the service history, so the renewal conversation is about the visits delivered and the work found and completed. Tracking renewals in a spreadsheet leaves them dependent on someone opening it in time. ### Can inspection findings be quoted on site? Yes. When the inspection form, the site record, the price book and the estimate share one record, a technician can turn a finding into a priced estimate on the phone with the photo attached, before leaving the site. The customer approves on the device or in the portal. --- # Your First 90 Days: Pick the Pilot Crew for Influence, Not Convenience **Author:** Andy Tolton **Published:** 2026-09-25 **Category:** field-services Eight to twelve weeks from kickoff to a crew on the platform. The week-by-week sequence, who decides what, and why the pilot crew decides the project. The app is live and the crews have it. In the office, someone is still keeping the old spreadsheet up to date, "just until everyone's on it." That sentence is where field service software projects die. The spreadsheet never goes away because nobody set a date for it to go, and the parallel process becomes the real one. The sequence below exists to make the old process unnecessary on a date. It runs eight to twelve weeks from kickoff to a field crew running on it, and it turns on one decision that most companies make by default: which crew goes first. ## Why implementations fail **Why do field service software implementations fail?** Rarely for technical reasons. The two causes are unowned decisions and a technician who doesn't use the app. Unowned decisions are the quieter of the two. Someone has to decide which service line goes first, what the dispatch priority rules are, which certifications each work type needs, and when the old system gets switched off. If those aren't assigned to a named person before kickoff, they're made in week six by whoever happens to be in the room, or they aren't made and the project drifts. The second cause follows from the first. When a technician doesn't use the app, the office keeps the old process running to have something reliable, and now there are two records. We look at why that happens in [why technicians work around the tools](/articles/why-technicians-work-around-field-service-software). ## The sequence **How long does it take to implement field service management software?** Eight to twelve weeks from kickoff to a field crew running on it, with full cutover inside 90 days. Add four weeks for multi-site rollouts with heavy data migration or multiple accounting integrations. ### Weeks 1 to 2: Foundation A named customer success manager and a technical lead are assigned. Employee records, roles and permissions are configured. The integration design is confirmed, and data mapping is scoped with your team. ### Weeks 3 to 4: Configuration Work order types and workflows are set up for each service line. Certification requirements are set per work type, so the board knows which credentials each kind of job needs. Dispatch rules, SLA tiers and escalation paths are defined. The price book is loaded with your rates and parts, and agreements are loaded. ### Weeks 5 to 7: Data and integrations Customer and site records are migrated with their history. The accounting integration is built and tested in both directions in a non-production environment before anything touches production. ### Weeks 8 to 9: Pilot One crew, one service line, real jobs, with the old process still available. Every friction point gets fixed before anyone else sees the app. This phase is the whole implementation. You sign off on pilot exit before rollout starts. ### Weeks 10 to 12: Rollout Crew by crew, with the pilot technicians training the next group. Peer-led rollout is the strongest predictor of adoption in a deskless workforce. The old system gets switched off, on a date. ### Weeks 13 to 14: Hypercare Elevated monitoring, daily check-ins and fast issue turnaround through your first full billing cycle on the new system. ### After go-live The named customer success manager and technical lead stay assigned. There are four major releases a year without an upgrade project. Customers typically see 90%+ adoption within 90 days, including workers with no company email. ## What MangoApps does and what you decide **What does the vendor do versus the customer during implementation?** Implementation is a partnership with a clear division of labor. Most implementation failures are not technical. They're unowned decisions, and this list exists so both sides know, before kickoff, which is which. **What MangoApps does:** - Configures the platform to your service lines, dispatch rules and billing structure - Configures the certification requirements you define against your work types - Loads your agreements and your price book - Migrates customer and site records, contacts, notes and history - Builds and tests the accounting and HR integrations - Trains your dispatchers, office staff and pilot crew - Assigns a named customer success manager and technical account manager who stay after go-live **What you decide:** - Which gap you close first, and therefore what goes live first - Which crew and service line pilot it - Who your internal champion is, and whether they can decide in week three without a committee - What your dispatch priority rules and SLA tiers actually are - Which certifications each work type requires - When the old system gets switched off, and whether that date is real Read the second list twice. Nobody outside your company can write it for you, and every item on it can stall a project if it's left open. The one about the date is the one that holds the rest together. ## The decision that matters most Pick the pilot crew for influence, not convenience. A respected senior technician who becomes an advocate is worth more than any training plan. A crew chosen because they were available is the most expensive shortcut in the project. That's a hard call, because the tempting choice is the crew with the lightest schedule. They can spare the time for meetings and testing, and they'll say yes. But they're also the crew whose opinion the rest of the field doesn't ask for. **How do you run a pilot for a field service app?** Find the technician the others call for advice. Not the one with the lightest schedule, and not necessarily the most senior title. The one whose truck other technicians walk over to when they're stuck. If that person tries the app on real jobs and it holds up, they'll say so, and the crew will believe them. If it doesn't hold up, you'll find out in week eight and not week twenty, when there's still time to fix it. Then give the pilot crew a real job: one service line, real work, with the old process available as a fallback. The fallback is the point. It lets the crew be honest about what doesn't work, since it isn't holding up the day. Every friction point they find gets fixed before anyone else sees the app, and the pilot technicians then train the next crew themselves. For seasonal operations, the same crew is the one to lean on when new hires arrive; see [staffing a seasonal, licensed field workforce](/articles/seasonal-licensed-field-workforce). ## What "pilot exit" should mean The pilot sign-off is short, because it has one job: to prove the old process is no longer needed. Before you let rollout start, check that a full day of jobs ran on the app without a paper fallback. Confirm that invoices for pilot jobs were generated from the work orders and not retyped, and that the accounting integration posted them and brought payments back. Look for anywhere a technician still records something twice. And ask the pilot crew directly whether they'd go back. That last question is the most useful. If the crew you picked for influence says no, they'll carry the rollout. If they hesitate, find out why before crew two hears about it. ## How timelines slip Most delays trace back to a small set of causes, and all of them are visible early. The champion needs a committee to decide anything, and the week-three decisions wait for a meeting. The integration scope grows because a second accounting system turns out to matter. The pilot crew gets pulled onto an emergency and the pilot pauses without anyone saying so. Or the switch-off date stays soft, and each week the old system stays open makes the next week harder to close. The answer to all four is the same: an owner, a date and a short list of decisions that were made before kickoff. That's what the second list above is for. ## The adoption guarantee If employees don't adopt MangoApps after launch, you don't pay. That's the guarantee, stated as a fact, and it puts a cost on the thing this whole article is about. It's also a reasonable thing to ask of any vendor. Question twelve in [how to evaluate a field service platform](/articles/how-to-evaluate-field-service-platform) is: what is your adoption rate at 90 days, and do you back it with anything? MangoApps is The AI Platform for the Frontline Workforce, and the Field Service Suite runs on the same platform as the rest of it, which is why adoption includes technicians who have no company email. The reasons adoption holds are laid out in [the technician article](/articles/why-technicians-work-around-field-service-software). ## Deciding on the date "8 to 12 weeks, not a year" is only true if the switch-off date is real. Decide that date at kickoff and write it down, and treat it as a commitment the champion owns. If you already run a field service tool and you're weighing this against what you have, [read this next](/articles/replace-fsm-tool-or-consolidate). And when you're choosing between vendors, the [evaluation guide](/articles/how-to-evaluate-field-service-platform) is where to start. Licensed trades will want [the article on certification-based dispatch](/articles/expired-certification-blocks-dispatch) before week three. The week-by-week sequence and both lists are also in the [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide), which is a convenient thing to hand to your executive sponsor. You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### How long does field service software implementation take? Eight to twelve weeks from kickoff to a field crew running on the new system, with full cutover inside 90 days. Multi-site rollouts with heavy data migration or multiple accounting integrations add about four weeks. ### What should a pilot crew look like? One crew and one service line, running real jobs with the old process still available. Choose the crew for influence and not convenience: a respected senior technician whom others ask for advice will do more for adoption than any training plan. ### What does the customer have to decide before kickoff? Which gap to close first, which crew and service line will pilot, who the internal champion is, what your dispatch priority rules and SLA tiers are, which certifications each work type requires, and when the old system gets switched off. ### What happens after go-live? A named customer success manager and technical lead stay assigned, hypercare runs through your first full billing cycle, and you receive four major releases a year without an upgrade project. Customers typically see 90%+ adoption within 90 days. ### What is the adoption guarantee? If employees don't adopt MangoApps after launch, you don't pay. --- # The Manager Is Not a Channel: Fixing Frontline Manager Communication Overload **Author:** Andy Tolton **Published:** 2026-09-25 **Category:** frontline-communication Supervisors carry the most effective frontline channel and the heaviest load in the company. Take the relaying and chasing off their shift and the channel gets stronger. *When the direct channel to frontline workers fails, the supervisor becomes the channel. That is not all bad news, since Gartner (2025) found manager-led communication is the most effective and most preferred way to reach frontline employees. The problem is load. Gallup attributes 70% of the variance in team engagement to the manager, and manager engagement fell from 30% to 27% in a single year. The fix is not a better manager. It is infrastructure that does the relaying managers now do by hand.* Almost every frontline communication plan has a person in the middle of it, and nobody wrote that person's job description with the plan in mind. When [the direct channel to frontline workers fails](https://www.mangoapps.com/articles/why-frontline-communication-fails), the message reaches the floor through the supervisor or it doesn't reach it at all. ## What the cascade actually asks of one person The cascade asks a single supervisor, in the middle of a shift, to be the delivery system for everything headquarters decided that week. Picture the floor lead at a distribution center two hours into second shift. She is holding four things in her head that have nothing to do with the trailers in front of her: a pricing change that goes live tomorrow, a schedule adjustment for the weekend crew, a revised break-coverage policy, and a recognition nomination deadline that closes Friday. She will pass each one along in the gaps between a late inbound load and two people who called out. Some of it will reach some of her team. Most of it will reach them compressed into a sentence on her way past. That is the cascade, described plainly. Headquarters publishes to a channel the floor doesn't have, usually an inbox or an intranet page, and the manager is expected to bridge the distance with their own voice. The cascade has no delivery record and no fallback. Its only capacity limit is the person carrying it. We call this a communication strategy. Then we measure engagement as though the channel were working, and when the number disappoints, the standard response is to ask managers to cascade more carefully. ## Manager-led communication works. That is exactly the problem. Managers are the best channel to the frontline, which is why overloading them costs so much. Gartner (2025) found that manager-led communication is both the most effective and the most preferred channel for frontline employees. Nothing here argues with that. A message from the person who sets your schedule carries a weight a corporate post never will. The supervisor knows which parts of an update matter at this site and can answer the follow-up on the spot. She can also tell from someone's face whether it landed. Gallup's research shows why the stakes are so high. Gallup attributes 70% of the variance in team engagement to the manager ([Gallup, 2014](https://www.gallup.com/workplace/231593/why-great-managers-rare.aspx)). And manager engagement is falling faster than that of any other group, from 30% to 27% in one year ([Gallup, State of the Global Workplace, 2025](https://www.gallup.com/workplace/659279/global-engagement-falls-second-type-2009.aspx)). Taken together, the two findings are uncomfortable. The channel that matters most is carried by the role that is deteriorating fastest, and most organizations respond to weak frontline reach by adding to that role's load. Every message the company cannot deliver directly becomes one more thing the supervisor has to carry. The question isn't whether to rely on managers. It is what to rely on them for. ## Where the load comes from: three sources Supervisor communication load comes from three places, and none of them actually needs a supervisor's judgment. They are expensive. In an illustrative model for a multi-site employer, 250 frontline supervisors each spend three hours a week relaying information and answering routine questions that already have documented answers. That is 150 hours a year per supervisor. At a fully loaded $32 an hour, it comes to $1.2 million a year. Every input is an assumption you can change. And the model doesn't count chasing at all. ### Relaying Relaying is passing along information the worker could have received directly. The new holiday schedule, say, or the benefits enrollment window. None of it needs interpretation. It routes through the supervisor only because the company has no other way to put it in front of the floor, and the supervisor becomes a human distribution list with a shift to run. ### Answering Answering is fielding routine questions with documented answers. Where is my pay stub? How does holiday pay work for a shift that crosses midnight? How much PTO do I have left? Each one pulls the supervisor away to look something up in a system the worker cannot reach, or worse, to guess. The answer already exists in a policy somewhere. The worker simply has nowhere to ask except a person. [Answering frontline questions without a supervisor](https://www.mangoapps.com/articles/frontline-knowledge-answers-without-supervisor) is its own problem, with its own fix. ### Chasing Chasing is confirming who saw the safety notice and following up with the people who did not. A sign-off sheet taped up in the break room. It's slow and it depends on the supervisor being there. The record it produces can't be audited. For anything critical, [tracking acknowledgment at the message level](https://www.mangoapps.com/articles/employee-acknowledgment-tracking) replaces the clipboard with a record of who confirmed and who did not. ## Same supervisor, same shift, rebuilt Rebuild the shift around the right infrastructure and the supervisor keeps every conversation that needs her while losing the relaying that never did. The four moments below happen on the same shift, to the same person. ### The pre-shift briefing Before, a policy change meant thirty minutes of briefing at the start of the shift. Now the change goes out the night before, targeted to the sites it affects and translated into each worker's language at the moment of publishing. It is marked Must Read. By the start of the shift she can see who has opened it and who has not. She spends two minutes with the four people who haven't, instead of thirty minutes with everyone. ### The safety alert An incident at one location triggers a stand-down notice across the region. It goes out by push, by SMS, and to the screens in the break rooms, with voice delivery for sites where reading a phone mid-task is not realistic. Acknowledgment is required. Anyone who hasn't acknowledged within the window is sent the notice again automatically, and the sites still below target show up on a dashboard while the incident is live rather than in the review afterwards. Her job is to talk to the people the dashboard names. ### The question that never reached the supervisor An associate wants to know how holiday pay works for a shift that crosses midnight. That used to be a question asked twice, once to a colleague who guessed and once to the supervisor, who had to go and look it up. Now it is asked in plain language in the app and answered from the actual policy document, scoped to the employee's own site and employment type. The supervisor never hears the question, and nothing is lost. ### The end of shift A sixty-second check-in at shift end asks what worked and what did not. One response is minor. Aggregated across sites and weeks, the responses surface a pattern nobody would have reported formally, such as a procedure being worked around at four locations. The follow-up message references what employees actually said, which is the part that decides whether anyone answers next time. The supervisor didn't have to run the survey or write the recap. > None of these moments require a better supervisor. They require a channel that reaches the worker, a return path that closes, and a record that proves both. **Download *Frontline Worker Communication & Engagement*.** It lays out the full supervisor-time model, with inputs you can replace with your own. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) ## Which capabilities take load off, and which add to it Any tool meant to help frontline communication should pass one honest test: does it remove a task from the manager, or create one? The capabilities that remove load share a trait. The work happens without the manager in the loop. - **Targeting by site, role, and shift.** The message arrives on the worker's phone without anyone forwarding it. - **Self-service for routine requests.** Pay stubs and time-off balances are available from the app at any hour, rather than only when someone is at a desk. - **Plain-language answers drawn from policy.** A worker describes the problem in their own words and gets an answer from the current handbook, inside the permissions that already apply to them. - **Automatic re-send to non-viewers.** A critical post goes back out only to the people who have not opened it, on a schedule set at publish. - **Recognition prompts with a one-tap send.** The platform notices an anniversary or a milestone and prompts the manager in the moment, so recognition stops depending on anyone remembering. The capabilities that add load share the opposite trait. They look like help and quietly hand the manager a new job. A message sent "to managers for distribution" is still a cascade, just with a nicer editor. A survey tool that asks the site manager to share the link, then exports results to a spreadsheet someone has to summarize, has created three tasks. A recognition program that runs through a desktop nomination form will be used by the managers who have a desk. Any product that expects the manager to build the audience, forward the message, run the survey, or compile the report belongs in this column. What separates the two columns is usually architecture, not features. Targeting works without the manager only when the audience is defined once, on one employee record that stays current as people change sites or shifts. A survey follow-up reaches the right people only when the survey and the message share that audience. And an answer drawn from policy is trustworthy only when the assistant reads the same governed library compliance does, which is why AI belongs at the foundation of an Employee Platform rather than bolted on as a chatbot. It is also the design behind [internal communications built for a workforce without desks](https://www.mangoapps.com/solutions/internal-communications). ## Manager enablement first Launch any frontline platform with manager enablement first, because supervisors decide adoption on the floor regardless of what the launch plan says. A supervisor who calls the new app "another thing from corporate" in the pre-shift huddle has made the adoption decision for her team. One who opens it in that huddle, shows the must-read list, and tells people their schedule lives there now has made the opposite one. Neither decision appears in the rollout plan. Both show up in the numbers a month later. What moves supervisors is seeing, before launch, which of their current tasks come off their plate. The broader picture of [what drives frontline adoption](https://www.mangoapps.com/articles/frontline-employee-app-adoption) starts with that conversation. None of this demotes the manager. The manager stays the most important channel to the frontline, and the infrastructure is what makes that sustainable. In the same illustrative model, handling a third of relayed communication and routine questions through direct delivery and self-service returns roughly 12,500 supervisor hours a year. Those hours go back to supervising: coaching a new hire through a first week, noticing who is struggling, deciding what a policy change means for this particular site. That is the work that made the manager-led channel the most effective one in the first place. The cascade has been spending it on delivery. **Download *Frontline Worker Communication & Engagement*** for the full model. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) Want to know whether your supervisors are carrying the whole channel? [Run the frontline communication audit](https://www.mangoapps.com/articles/frontline-communication-audit), or [see it configured for your sites](https://www.mangoapps.com/schedule-a-call). *The AI Platform for the Frontline Workforce.* ## Frequently asked questions **Why do frontline managers struggle to communicate with their teams?** They are carrying delivery, answers, and follow-up that infrastructure should carry. When the company has no direct channel to the floor, every update routes through the supervisor, along with every routine question and every "did you see the notice" conversation. All of that sits on top of running the shift, so communication gets compressed or dropped. The problem is capacity, not skill. **What is a communication cascade and why does it fail?** A communication cascade is the practice of publishing to managers and relying on them to pass each message to their teams. It fails on load, because one supervisor can't reliably relay every update between everything else they own. It also fails on absence. When the supervisor is out sick or has just left the company, the channel goes with them, and there is no record of who heard what. **Is manager-led communication effective for frontline workers?** Yes, it is the most effective and most preferred frontline channel, according to Gartner (2025). The problem is load, not effectiveness. Supervisors add context and read the room in a way no post can. **How much time do supervisors spend relaying information?** In an illustrative model, about three hours a week each, which comes to roughly $1.2 million a year for an organization with 250 frontline supervisors. That is 150 hours a year per supervisor at a fully loaded $32 an hour. The hours go to relaying information and answering routine questions with documented answers. The model doesn't include time spent chasing acknowledgment. **Why is manager engagement falling?** [Gallup's State of the Global Workplace 2025 report](https://www.gallup.com/workplace/659279/global-engagement-falls-second-type-2009.aspx) shows manager engagement fell from 30% to 27% in a single year, faster than any other group. Whatever else sits behind that decline, communication load is one driver the company controls directly, because managers absorb the delivery work the company's own channels cannot do. **How do you reduce the communication burden on frontline supervisors?** Deliver directly to the worker, and let routine questions and follow-ups resolve without the supervisor. In practice that means targeting messages by site, role, and shift so they arrive without being relayed, plus self-service for pay stubs and time-off balances. Questions get answered in plain language from the actual policy, and anyone who has not viewed a critical notice gets it again automatically. **Should companies stop relying on managers to communicate?** No. They should stop relying on managers to relay. Managers remain the most effective channel for coaching and for the conversations that need a person. What they should not carry is the delivery of messages that could reach the worker directly, or the follow-up on who saw what. Taking that off the shift is what makes the manager-led channel sustainable. **What happens to team communication when a supervisor is out?** In most cascade-based organizations, it stops. That is why the [frontline communication audit](https://www.mangoapps.com/articles/frontline-communication-audit) uses one diagnostic question for the manager gap: if a supervisor is out sick, does their team still receive company communication that week? If the answer is no, the manager is the entire channel, and a single sick day or resignation is enough to cut a team off. --- # The Personal Group Chat Problem: Why Ungoverned Channels Fill the Frontline Communication Vacuum **Author:** Andy Tolton **Published:** 2026-09-25 **Category:** frontline-communication When the company channel never reaches the floor, shift coverage and safety concerns move somewhere nobody can search or produce. Bans fail. A better governed channel wins. *Frontline workers do not wait for a sanctioned channel that never reaches them. Shift coverage, safety questions, and schedule changes move to personal messaging groups the company does not own, cannot search, and cannot produce in an audit. US regulators have levied more than $2.5 billion in fines since 2021 for work conducted on unapproved channels (SEC and CFTC enforcement actions, 2021 to 2024). Banning the apps rarely works. Governance holds when the company channel is one workers would choose anyway.* Somewhere in your operation tonight, a shift lead is asking a group chat who can cover Saturday. Three people answer inside ten minutes. One of them adds a photo of the walk-in door that still won't latch. Another asks whether the new return policy starts Monday or next month, and gets two different answers from two people who both sound certain. The chat lives on personal phones, in an app the company doesn't own, in a group nobody at headquarters can see. And it works. The shift gets covered. That is the problem. Communications leaders usually meet this as a nuisance. Compliance and legal teams meet it later, as a record that should exist and doesn't. It is the sixth of the reach gaps described in [why frontline communication fails](https://www.mangoapps.com/articles/why-frontline-communication-fails), and it is the gap that turns a reach problem into a risk problem. ## What actually moves to the group chat Everything the shift needs to coordinate moves to the group chat, and every bit of it is company business. Look at what a typical frontline group carries in a week. Who is covering Saturday, and who agreed to swap Tuesday for it. The photo of the broken fixture, sent so somebody fixes it before open. The question about the new return policy that nobody could answer at the register. "Did anyone hear about the schedule change?" posted at 6 a.m. by the associate who was off when the supervisor mentioned it. And the safety concern nobody wanted to raise formally, which ends up in writing anyway, just somewhere the company cannot read it. None of it is on a company system. This isn't rebellion. Roughly 80% of the global workforce is deskless (Emergence Capital, 2018; share reconfirmed by BCG, 2024), and most of the channels companies built for employees assume an inbox and a laptop those workers were never given. When Microsoft surveyed frontline workers, 63% said messages from leadership do not reach them (Microsoft Work Trend Index Special Report, 2022). Workers are not waiting for that number to improve. When the sanctioned channel does not reach them, coordination moves to the one that does. ## What the company loses when it moves The company loses its own record of how the work got done, and it loses it long before any regulator asks. A conversation in a personal messaging group cannot be searched by the company. It cannot be retained on the company's schedule or moderated when it turns ugly. It cannot be produced when an audit or a lawsuit asks for it. The loss shows up well before any of those requests. The decision made in a chat three weeks ago about how to handle short-dated stock is gone the moment someone asks why two stores did it differently. A new supervisor inherits the team but not the conversation history that explains it. The safety concern is the sharpest case. Someone raised it. Several people saw it. Formally, it never happened. If the fixture fails next month, the organization will learn that its people knew and its systems did not. So treat this as institutional loss before regulatory loss. Knowledge an organization cannot find is knowledge it cannot act on, and that now includes the AI it is expected to put in front of employees. An assistant can only answer from content the company holds and governs, which is the principle behind [governing AI by design](https://www.mangoapps.com/articles/governing-ai-by-design). Coordination that happens in personal groups is invisible to people and machines alike. ## The enforcement record Regulators have already put a price on the record a company cannot produce, and it is more than $2.5 billion. That is the combined total of SEC and CFTC fines since 2021 for work conducted on unapproved personal messaging channels (SEC and CFTC enforcement actions, 2021 to 2024). The fines were not for bad advice or bad trades. They were for business conducted somewhere the firm could not keep or hand over. The number exists because communication moved to a place the company could not govern, which is exactly the move described above. Those two regulators oversee financial markets, so a hospital system or a grocery chain may never deal with either of them. The principle carries over anyway. Any employer can be asked what its people said and when, in litigation discovery, say, or in the review after a safety incident. The regulator changes by sector. The exposure stays the same, a record of company business the company cannot produce. Frontline-heavy employers carry more of this than most, for a plain reason. Their people are the least likely to have a company channel that reaches them, so they are the most likely to have built their own. ## Why the exposure belongs to the gap, not the employees The exposure is created by the gap, not by the employees. A worker coordinating shift coverage in a personal group is solving a problem the company left them. Nobody gave the overnight crew a way to reach each other, so they made one. Calling it a policy violation is accurate and beside the point. This is why bans rarely hold. A ban removes the tool and leaves the need, so the coordination either continues quietly or moves somewhere harder to see. Enforcement then lands on the people with the least power in the organization and the best reason for what they did: the associate who found cover for a sick colleague, the technician who sent the photo so the job got finished. The company ends up disciplining the behavior it most wants, which is people looking after the shift. A policy still matters. Workers should know what belongs on a company system. But a policy with no better alternative behind it is a statement of preference, and frontline workers will follow the channel that works. **Download *Frontline Worker Communication & Engagement*.** The book lays out all six reach gaps, the ten requirements they produce, and a scorecard for finding which ones are open in your operation. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) ## What a governed channel has to be to win A governed channel wins only when it is better than the group chat it competes with. > Governance is not achieved by policy. It is achieved by making the governed channel the one people would choose anyway. That is the requirement no feature list states plainly. The group chat is fast and it is already on the phone. To replace it, a company channel has to match it on everything workers use it for, then add what the company needs. In practice that comes down to four things, described here by capability rather than by product. - **Every shape of conversation.** Direct messages, group rooms for a site or a shift team, and long-form posts for anything that needs more than a line. Files, images, and voice notes attach anywhere, because the person sending them usually has their hands full. - **Findable later.** Search across conversations, files, and posts, so the decision made three weeks ago can be retrieved. Mentions pull in the right people without notifying everyone, so the channel doesn't turn into noise. - **Reachable by everyone on the shift.** That includes the new hire who started Monday and has no corporate email address. If a channel leaves anyone out, that person's shift keeps a group chat going, and the whole team ends up in it. - **Already open.** It sits in the same app as the schedule and the company news, so checking it isn't a separate decision. A channel people have to remember to visit loses to one already in their hand. These line up with the requirements set out in [what a frontline employee app actually requires](https://www.mangoapps.com/articles/frontline-employee-app-requirements). Miss one and the group chat survives. If the governed channel isn't better, it will lose, and the policy will keep being broken by the people trying hardest to do their jobs. ## Governance that applies once Governance holds when one model covers every place company business is conducted, instead of a separate rule for each tool. Retention, eDiscovery, moderation, and audit should apply to company chat the same way they apply to posts and comments. One model decides whether legal can answer a question in an afternoon or needs a month, because one model means one place to look. When chat sits in one tool and announcements in another, each with its own retention setting, the organization has two governance problems and no complete record. The private track is what makes workers accept the channel at all. Private messaging between coworkers should run as a separately governed track, so personal exchange and company business are not held to one policy. People will not move their conversations to a company system that treats every message as a corporate record. Separating the tracks lets the company govern what it needs to govern, and it tells workers plainly where the line is. Then there is the record of governance itself. Every content and moderation action should be recorded, so when someone asks who removed a post or how long a thread was kept, the answer already exists. An audit becomes a retrieval rather than an investigation. This is where an Employee Platform built as one system earns its place. When chat and posts share one employee record and one permission model, governance is configured once and every capability inherits it, including the AI layer that answers from the same content. That shared foundation is also what lets [internal communications](https://www.mangoapps.com/solutions/internal-communications) reach the frontline and still hold up when someone checks. ## The test The test is one question. Do you know which unapproved channels your teams coordinate work in today? It is the sixth question in the [frontline communication audit](https://www.mangoapps.com/articles/frontline-communication-audit), and it is the hardest one to answer from headquarters. A quick way to find out is to ask five frontline supervisors which group chats their teams use to cover shifts. If a name comes back without hesitation, that is your answer. If the supervisor is a member of the group, the channel problem reaches further up than the floor. If a group chat turns up at all, the gap is open, and it will stay open until the company offers something better. When you evaluate what that might be, press every vendor on two points: who administers the channel day to day, and what their retention and eDiscovery position is on employee conversations. Both sit in the [vendor evaluation questions](https://www.mangoapps.com/articles/evaluate-frontline-communication-vendors). The group chat isn't really the thing to fix. It is the most accurate map you have of where the company channel does not reach. **Download *Frontline Worker Communication & Engagement*** for the full six-gap diagnostic and the requirements behind a governed channel. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) Take the [governance and delegation questions](https://www.mangoapps.com/articles/evaluate-frontline-communication-vendors) into your next shortlist review, or [see it configured for your sites](https://www.mangoapps.com/schedule-a-call). *The AI Platform for the Frontline Workforce.* ## Frequently asked questions **Why do employees use personal messaging apps for work?** Employees use personal messaging apps for work because the company channel does not reach them or does not carry what they need. Most frontline workers have no corporate email address and no company device, so channels built around an inbox or a desktop never arrive. The coordination still has to happen, so it moves to the phone. When Microsoft surveyed frontline workers, 63% said leadership messages do not reach them (Microsoft Work Trend Index Special Report, 2022). **Is it a compliance risk when staff coordinate work in personal group chats?** Yes, because the company cannot search, retain, or produce those conversations when an audit, investigation, or lawsuit asks for them. SEC and CFTC fines for work conducted on unapproved personal messaging channels passed $2.5 billion over four years (SEC and CFTC enforcement actions, 2021 to 2024). Outside financial services the regulator differs, but the exposure is the same missing record. **Can a company ban personal messaging apps for work?** A company can ban them, and it rarely works, because the need the apps meet remains. A ban removes the tool without giving workers another way to cover a shift or flag a problem, so the coordination goes quiet rather than away. **How do you stop employees using unapproved messaging apps?** Give them a governed channel that is better than the group chat and already open on their phone. That means direct and group messaging, files and voice notes, search, and reach to every worker, including those with no corporate email address. When the company channel is the easier one, the group chat loses its reason to exist. **What is off-channel communication?** Off-channel communication is company business conducted on systems the company does not control. A shift swap arranged in a personal messaging group is off-channel, and so is a customer issue settled over personal text. The content may be entirely appropriate. The problem is that the organization cannot retain, search, or produce it. **What is the difference between company chat and personal messaging?** The difference is governance. Company chat carries retention, search, moderation, and eDiscovery, and its administrative actions are recorded. A well-designed company chat also runs private exchanges between coworkers as a separately governed track, so personal conversation and company business are not held to the same policy. **Does frontline chat need retention and eDiscovery?** Yes, if it carries company business, and frontline chat almost always does. Shift coverage, safety concerns, and customer issues are exactly what gets asked about in audits and investigations. Retention and eDiscovery should apply to chat under the same model as posts and comments, so there is one place to look. **Should private messages between coworkers be governed the same as company communication?** No. A separately governed private track is what makes a company channel acceptable to the people using it. Workers will not move their conversations to a system that treats every message as a corporate record. Separating the tracks keeps governance focused on company business and states plainly where the line sits. **What is a governed communication channel?** A governed communication channel is a company-owned channel where retention, search, moderation, and audit apply, and which workers actually prefer to use. In practice that comes down to six requirements. It handles every shape of conversation, including files and voice notes, and its search makes decisions findable later. It reaches everyone on the shift and lives in the app they already open. One governance model covers chat, posts, and comments, while private messages run on a separately governed track. --- # Sending Is Not Reaching: Why Frontline Communication Fails **Author:** Andy Tolton **Published:** 2026-09-25 **Category:** frontline-communication Most frontline messages fail before anyone reads them, because the channel assumes an inbox and a desk. Six gaps explain the failure and what it costs. *Most frontline communication does not fail because the message was unclear. It fails because the message was never delivered. Enterprise communication assumes an inbox, a company device, and a login, and for the roughly 80% of the global workforce that does not work at a desk (Emergence Capital, 2018, reconfirmed by BCG, 2024), those assumptions are false. Sixty-three percent of frontline workers say leadership messages do not reach them (Microsoft, 2022). That is an infrastructure problem, treated as a content problem for twenty years.* ## Somewhere in your company this week, an employee will hear about a change to their own job from a customer Somewhere in your company this week, an employee will learn about a change to their own job from someone who does not work there. A patient's family mentions the new visiting rule to the nurse at shift change. A customer at the counter asks the associate about a return policy that changed on Monday. A contractor on the loading dock tells the receiving lead that the delivery window moved. Nobody inside told them, and it was not for lack of trying. The newsletter went out on schedule, to an inbox the associate has never had. The policy page was approved and correct, and the nurse has never opened it and wouldn't know where to look for it. None of those channels failed in the way the word usually means. Somebody did the work. The message had nowhere to land. The job then falls to the supervisor. One person, halfway through a shift, is expected to hold every update in their head and pass it along between the dozen other things they answer for. At the end of the quarter the organization measures engagement as though the channel had worked all along. ## The frontline is the largest segment of the workforce and the least reached The frontline is the biggest group of employees most companies have, and the group their communication infrastructure reaches least. Roughly 80% of the global workforce does not work at a desk (Emergence Capital, 2018, reconfirmed by BCG, 2024), and in the United States that is close to 100 million people (McKinsey, 2026) who serve the customer, treat the patient, run the line and drive the route. Enterprise communication was built on three assumptions about the person receiving it. It assumes an inbox, which most frontline workers don't have. It assumes a company device, which most are never issued. And it assumes a website behind a sign-in screen, which presumes a desktop and ten spare minutes. For the majority of the workforce, all three are false. The executive version of this argument, including what it means for AI plans, is laid out in [the frontline AI blind spot](https://www.mangoapps.com/articles/frontline-ai-blind-spot). This piece stays with the communications function and the channel it depends on. ## "They do not arrive" is a different kind of problem When 63% of frontline workers say messages from leadership do not reach them (Microsoft, 2022), they are describing a delivery failure, and no amount of writing fixes a delivery failure. Read the finding closely. Respondents did not say the messages were unclear or badly timed. They said the messages don't arrive. That changes the problem type. If the channel does not reach people, better copy will not help, and neither will a more disciplined editorial calendar, a clearer tone of voice, or a larger content budget. Each of those improves a message on its way to a place it will not arrive. Most internal communications teams are staffed and measured as editorial functions, and most are good at editorial work. The trouble is that the work sits on top of a channel that stops at the edge of the office. > This is not a content problem. It is an infrastructure problem, misdiagnosed for twenty years. The misdiagnosis survives because the reporting can't see it. Open rates and page views are calculated on the people the channel reached. A newsletter can post a healthy open rate among the employees who have an inbox and say nothing about the ones who don't, and nothing on the dashboard marks the difference. ## The six gaps underneath every frontline communication failure Pull on any frontline communication failure, whether a missed policy change, a safety alert nobody acknowledged, or an engagement score nobody can explain, and one of six gaps is usually underneath it. They are not six separate problems. They are symptoms of a function asked to run without the infrastructure it needs. ### Gap 1: The message never arrives No corporate email address, no assigned device, no sign-in. The channel assumes an inbox the worker does not have, so delivery depends on somebody relaying the message in person. This is the gap behind the Microsoft finding, and everything downstream of it stays theoretical until it closes. Rendering the intranet on a phone rarely closes it, for reasons covered in [why a mobile intranet is not a frontline employee app](https://www.mangoapps.com/articles/mobile-intranet-vs-frontline-employee-app). ### Gap 2: The manager is the entire channel When the direct channel fails, the supervisor becomes the channel. Gallup attributes 70% of the variance in team engagement to the manager ([Gallup, 2014](https://www.gallup.com/workplace/231593/why-great-managers-rare.aspx)), and manager engagement fell to 27% in a single year, down from 30% ([Gallup, State of the Global Workplace, 2025](https://www.gallup.com/workplace/659279/global-engagement-falls-second-type-2009.aspx)). Companies are routing more through the most overloaded role they have and calling it a strategy. The load, and how to take it off, is the subject of [frontline manager communication overload](https://www.mangoapps.com/articles/frontline-manager-communication-overload). ### Gap 3: Nothing comes back Frontline communication runs one way. Headquarters publishes, the floor receives, and there is no return path. The organization learns what it said and never learns what the floor knows, until that knowledge arrives as turnover or a safety incident, often twelve months too late to act on. A return path that people actually use is described in [frontline listening that closes the loop](https://www.mangoapps.com/articles/frontline-listening-close-the-loop). ### Gap 4: Answers are scattered The schedule sits in one system, the policy in another, training in a third and pay in a fourth. A worker with a two-minute question has no single place to ask it, so the question goes to the supervisor and Gap 2 gets worse. Frontline employees used an average of 2.3 channels in 2025 (Gartner, 2025), a sign that no single channel holds enough to be worth checking. More on this in [getting frontline workers answers without a supervisor](https://www.mangoapps.com/articles/frontline-knowledge-answers-without-supervisor). ### Gap 5: You cannot prove it landed Publishing metrics stand in for reach. A post went out and a page was viewed, and neither fact shows that the people who needed the message received it, understood it, or acted on it. Without that, nobody can tell a campaign that worked from one that was wasted, and communication stays a cost center that can't defend its budget. What real proof looks like is in [employee acknowledgment tracking](https://www.mangoapps.com/articles/employee-acknowledgment-tracking). ### Gap 6: Ungoverned channels fill the vacuum Workers are not waiting for the company to fix this. When the sanctioned channel does not reach them, coordination moves to personal messaging groups the company does not own and cannot search or produce in an audit. SEC and CFTC fines for work done on unapproved messaging channels passed $2.5 billion between 2021 and 2024. The gap creates that exposure, not the employees, as [the personal group chat problem](https://www.mangoapps.com/articles/personal-messaging-apps-frontline-compliance) explains. Every operation has a different mix of these open. The quickest way to find yours is to [score your operation against all six](https://www.mangoapps.com/articles/frontline-communication-audit), one honest answer per gap. ## What the gaps cost, and whose budget it lands in The six gaps are already being paid for, just not out of the communications budget. Start with engagement. Global employee engagement stands at 20%, its lowest level since 2020, and Gallup puts the cost to the world economy at $10 trillion in lost productivity (Gallup, State of the Global Workplace, 2026). In the United States engagement sits at 31% (Gallup, State of the Global Workplace, 2026). That loss is booked as productivity, and nobody charges productivity to the intranet. Turnover lands somewhere else again. Retail frontline turnover runs above 60% a year (McKinsey, 2024). In hospitals, each percentage point of registered nurse turnover costs a typical hospital about $262,500 a year (NSI Nursing Solutions Report, 2024). Those numbers sit with HR and operations, where they read as a labor-market problem rather than a question of whether anyone told the new hire what they needed to know in their first week. Compliance lands in legal. The more than $2.5 billion in off-channel communication fines (SEC and CFTC enforcement actions, 2021 to 2024) exists because work moved to a place the company could not govern. None of these costs appears in the communications budget, and that is exactly why the problem has lasted. The function that could close the gaps doesn't carry their price, and the functions carrying the price don't own the channel. The full model, with inputs you can change for your own operation, is in [what frontline disengagement actually costs](https://www.mangoapps.com/articles/cost-of-frontline-disengagement). **Download *Frontline Worker Communication & Engagement*.** It gives communications and HR leaders the six-gap diagnostic, the cost model, and the requirements a frontline channel has to meet, in one place. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) ## What reaching the frontline looks like when it works Reaching the frontline works when the channel is built for the worker who was never at a desk, and PetSmart shows how large the unreached share can be. Roughly 80% of its 55,000-person workforce, the people in stores and distribution centers, had little or no access to the previous desktop-centric platform. The company's branded app now drives 4x the industry engagement rate. > "With MangoApps, we're really trying to solve for engagement across the business. Our old platform was very desktop-centric. About 80% of our 55,000 employees, those in stores and distribution centers, largely didn't have access. MangoApps gave us the ability to actually reach our entire associate base for the first time ever." > > Sheena Christensen, Corporate Communications Manager, PetSmart Three things changed, and none of them was a better newsletter. The channel changed first. It now reaches a worker with no inbox and no company device, on the phone already in their pocket, in the language they work in. The associate opening the store sees the price change on the morning it was decided, and the supervisor is no longer the only route it can take. The direction changed next. A return path lets the floor answer, through a sixty-second check-in at shift end or a question asked in the app, so the organization hears about a procedure being worked around at four locations before it turns into an incident. The third change is evidence. Communications can say which sites acknowledged the safety notice and which fell below target, in the meeting where budgets get set, rather than reporting how many posts went out. That is what [internal communications for the frontline](https://www.mangoapps.com/solutions/internal-communications) looks like when it runs on infrastructure built for the people receiving it. ## Why this is solvable now when it was not ten years ago This became solvable because three constraints that used to block it have fallen away. The hardware problem solved itself. Frontline workers already carry capable phones. The barrier left standing is whether the company has anything worth putting on that phone that doesn't require a corporate email address to open. Platform architecture caught up. It is now possible to run one employee record, one permission model and one content layer across communication, knowledge and engagement, instead of integrating four systems that each hold a partial copy of who an employee is. That is an architectural change rather than a feature release, which is why it took as long as it did. AI changed the stakes. Consolidating content used to be a hygiene argument, and hygiene arguments lose to urgent ones. Now it is the precondition for everything a company wants AI to do for employees, because an assistant can only answer from content that is current, governed, and in one place. The foundation that reaches the frontline is the same one AI needs, and [why fragmented tools break enterprise AI](https://www.mangoapps.com/articles/why-fragmented-tools-break-enterprise-ai) makes that case in full. ## The decision underneath all of it Organizations that reach their frontline don't have better communicators than everyone else. They have infrastructure that carries what their communicators produce. The instinct in most companies is to work harder inside the existing channel. More frequent updates, a tighter calendar, a warmer tone. It is sincere work and it keeps improving a message on its way to somewhere it won't arrive. What changes the outcome is smaller and harder than effort. It is the decision to stop treating the frontline as the part of the workforce that gets reached later, and to fund the channel on the same terms as every other piece of infrastructure the business runs on. Until that decision is made, the employee who hears about their own job from a customer is the system working exactly as it was built. Get the full diagnostic and cost model in [*Frontline Worker Communication & Engagement*](https://www.mangoapps.com/resources/frontline-communication-engagement-guide). [Score your gaps](https://www.mangoapps.com/articles/frontline-communication-audit), or [see it configured for your sites](https://www.mangoapps.com/schedule-a-call). *The AI Platform for the Frontline Workforce.* ## Frequently asked questions **What is frontline communication?** Frontline communication is communication with employees who don't work at a desk, in the store, on the floor, on the ward, on the route and at the plant. It differs from desk communication because it cannot assume an inbox, a company device, or a sign-in to a corporate website. Those workers are usually on shift, often on a personal phone, with a few minutes between tasks. A channel that works for them has to reach a person with no corporate identity at all. **Why do internal communications not reach frontline workers?** Internal communications miss frontline workers because the channel assumes infrastructure those workers don't have. Newsletters need an inbox, intranets need a desktop and a sign-in, and most frontline employees have neither. Sixty-three percent of frontline workers say messages from leadership do not reach them (Microsoft, 2022). The messages are not rejected. They never arrive. **What percentage of the workforce is frontline or deskless?** Roughly 80% of the global workforce does not work at a desk (Emergence Capital, 2018, reconfirmed by BCG, 2024). In the United States, the frontline is close to 100 million people (McKinsey, 2026), the largest single segment of the workforce. It includes retail associates, nurses, plant operators, drivers, field technicians and hospitality staff. **Is frontline communication a content problem or a technology problem?** It is an infrastructure problem first. If a message cannot reach the worker, the quality of the writing makes no difference to the outcome. Better copy, a stronger editorial calendar and a bigger content budget all improve a message that still doesn't arrive. Content quality matters once delivery works, and not before. **What is the difference between reach and engagement in internal communications?** Reach is whether the message arrived, and engagement is what people did with it. Most communication tools report engagement, such as opens and clicks, calculated only on the people the channel reached. That makes a channel that misses most of the frontline look healthy. Measuring reach by site, role and shift is what shows who was never in the denominator. **What are the six reach gaps?** The six reach gaps are the message never arrives, the manager is the entire channel, nothing comes back, answers are scattered, you cannot prove it landed, and ungoverned channels fill the vacuum. Most frontline communication failures trace back to one of them. The [frontline communication audit](https://www.mangoapps.com/articles/frontline-communication-audit) lets you score each gap for your own operation. **Why do frontline managers end up carrying company communication?** Frontline managers carry it because the direct channel fails, so the supervisor becomes the channel by default. Gallup attributes 70% of the variance in team engagement to the manager ([Gallup, 2014](https://www.gallup.com/workplace/231593/why-great-managers-rare.aspx)). Asking that same person to relay every update, answer every routine question and chase every acknowledgment adds load to the role that most shapes how a team feels about work. **What does poor frontline communication cost?** Poor frontline communication costs money in turnover, supervisor time and compliance exposure, though none of it shows up in the communications budget. Retail frontline turnover runs above 60% a year (McKinsey, 2024), and each point of hospital RN turnover costs about $262,500 a year (NSI Nursing Solutions Report, 2024). Regulators have levied more than $2.5 billion in off-channel communication fines (SEC and CFTC enforcement actions, 2021 to 2024). The full model is in [what frontline disengagement actually costs](https://www.mangoapps.com/articles/cost-of-frontline-disengagement). **How do companies reach employees who have no corporate email address?** Companies reach them through a branded employee app on the worker's own phone, provisioned without a corporate identity, with no password and no corporate email required. The app is published under the company's name, so it reads as the employer's app rather than a vendor's. New hires are set up from the HR record in minutes. [What a frontline employee app actually requires](https://www.mangoapps.com/articles/frontline-employee-app-requirements) lists the capabilities to check for. --- # How to Evaluate Frontline Communication Vendors: 20 Questions and a Scorecard **Author:** Andy Tolton **Published:** 2026-09-25 **Category:** frontline-communication Feature checklists can't tell one data model from a shared login screen. These questions and a scorecard find the difference in the demo, before year two does. *Twenty questions in five groups: architecture, frontline access, listening and measurement, governance and delegation, and AI grounding. Each is written to surface an architecture decision that determines whether a platform still serves you in three years or becomes the next system you rip out. After the questions comes a nineteen-row scorecard to run against every vendor on your shortlist. A platform built on one data model, for the frontline, with AI grounded in your own content, scores well across every row. A stack of point tools cannot.* ## Why architecture questions and not feature questions Feature questions don't separate vendors, because any vendor can match any single capability. What can't be assembled through integration is the shared record underneath those capabilities. Integration moves copies of data between systems on a schedule. It does not produce one employee record that every capability reads and writes in the moment. That difference is almost invisible in a demo, where a platform designed as one system and one assembled from acquisitions can look identical. The first shares a data model. The second shares a login screen. Under load they behave nothing alike. Put either one in front of a workforce with retail-level turnover, above 60% a year (McKinsey, 2024), and the difference shows up every week in provisioning, in acknowledgment reports that don't match the compliance view, and in surveys nobody can follow up on without an export. A feature checklist is where assembled products look their best, because every box can be ticked by something, somewhere. The twenty questions below find the seams while the vendor is still in the room. If the case for why frontline messages go missing is new to your team, start with [why frontline communication fails](https://www.mangoapps.com/articles/why-frontline-communication-fails) and come back. One rule for using them. Ask every vendor on your shortlist, and ask us. ## Architecture (questions 1 to 3) The architecture questions establish whether you are buying one system or several systems sharing a sign-in screen. Listen for answers about the record underneath, not the interface on top. **1. Is this one shared data model, or separate modules connected by integrations?** Every other row on the scorecard depends on this one. If acknowledgment, surveys, knowledge and the assistant each keep their own copy of who an employee is, every report you run is a reconciliation. A strong answer describes one employee record that every capability reads from and writes to, and the vendor can show it. Change an employee's site once and watch audience membership, content targeting and access follow. An evasive answer talks about the experience. "Fully integrated" and "one unified interface" describe the screen. Ask what happens underneath when the screen changes. **2. When an employee acknowledges a notice, does the compliance view update instantly, or does a sync have to run?** This is the fastest live test of question 1. When the confirmation writes to the same record compliance reads from, there's no export and no window during which the two views disagree. When a sync has to run, that window exists, and an auditor will eventually ask about it. A strong answer is a demonstration. Someone acknowledges a safety notice on a phone and the compliance view changes before anyone refreshes a report. An evasive answer explains the sync schedule and how configurable it is. **3. When we add a capability later, is it configuration on the platform we already own, or a new implementation? And what happens to users, data, and history when we expand?** Most buyers start with communication and add listening or knowledge later. If each addition is a new implementation, you pay for identity and migration again, and employees lose their history. A strong answer names what carries forward, which should be the same identity, the same record and the same permissions, with nothing migrated. An evasive answer points to a partner, or to the shared contract. A shared contract is not a shared record. ## Frontline access (questions 4 to 8) The frontline access questions show whether a product was built for people without a desk or adapted for them afterwards. Roughly 80% of the global workforce does not work at a desk (Emergence Capital, 2018, reconfirmed by BCG, 2024), so these five decide how much of your company the platform can reach at all. **4. Can you reach an employee with no corporate email address, no company device, and no VPN?** This question decides whether the other nineteen matter. A platform that needs a corporate identity reaches the office and a fraction of the floor. Listen for a sign-in path with no password and no corporate email, that still supports SSO, MFA and SCIM where you already run them without requiring them anywhere. **5. How long does provisioning a new frontline hire take, and who does it?** With turnover at frontline rates, provisioning isn't an edge case. It's a weekly operation. The strong answer is minutes, driven by the HR record, with nobody in IT touching it. Site, role, shift and language should all follow from that one record. **6. Does it work offline, and on a shared device?** Cold storage, basements, delivery vans and plant floors all have patchy connectivity, so content has to be readable without a live connection. Shared devices and kiosks matter wherever a personal phone is impractical or not allowed. Ask, too, what protects company content on a personal phone. **7. Is the app published under our brand in both app stores, or under yours?** The receiving associate searching the app store on a Sunday night should find your name, your logo and your icon. A branded app reads as the company's, and it keeps the relationship with your workforce yours rather than the vendor's. **8. Does translation happen at publish, on the content itself?** Mixed-language crews on a single shift are ordinary. When translation is a separate project it arrives late and drifts from the original. Ask what happens when the original is corrected. Every language version should correct with it, because they are the same message. For this group, make one demo request. Ask the vendor to provision a fictional new hire with no corporate email address and reach them on a phone within five minutes. Watch how many people have to be involved. ## Listening and measurement (questions 9 to 12) These questions separate a platform that reports activity from one that can prove a message landed and show that feedback led somewhere. **9. Can you show acknowledgment by site, role, and shift rather than a company-wide average?** A healthy company average can hide one region at 40% and another at 95%. The operational question after any critical message is which sites fell below target, and only a breakdown by site and shift answers it. What good proof looks like is covered in [employee acknowledgment tracking](https://www.mangoapps.com/articles/employee-acknowledgment-tracking). **10. What happens automatically to the people who did not view a critical message?** The answer should be a setting chosen at publish. The platform re-sends only to members who haven't viewed, through the channel you pick, on a relative or fixed timer. For emergency alerts, ask about voice delivery for sites where reading a phone mid-task isn't realistic. If the answer involves someone exporting a list, escalation depends on that someone remembering. **11. Can a survey and the communication that closes the loop share one audience definition without an export?** Closing the loop is the strongest predictor of whether anyone answers the next survey. When the survey tool and the communication tool hold separate audience definitions, closing the loop means an export, a manual match and a guess. The group you surveyed should be the group you follow up with, defined once. **12. Is anonymity structural, with minimum thresholds, or promised in the invitation?** Frontline employees answer honestly when they believe the anonymity. Structural anonymity means the system enforces minimum response thresholds before site or team results appear. A sentence in the invitation is a promise. Ask what the threshold is and who can lower it. ## Governance and delegation (questions 13 to 16) The governance questions decide what the platform is still worth on day four hundred, after the launch team has moved on to other work. **13. Who administers this day to day, and what requires IT?** The function that owns employee communication is almost never the function that owns IT. If every audience change, new site or permission adjustment needs a ticket and a sprint, the platform stops reflecting the organization within a quarter and the workarounds start. A strong answer is that communications and HR configure audiences, sites and approval routing themselves. **14. Can a site leader publish locally without being able to publish company-wide?** Delegated local publishing is the requirement buyers miss most, because it looks like an administrative detail. It is the difference between a channel that carries what is true at this store today and one that carries only corporate content, which employees learn to skip. [What a frontline employee app actually requires](https://www.mangoapps.com/articles/frontline-employee-app-requirements) explains where it sits among the other requirements. **15. How do we find content that has no owner?** A knowledge base becomes a liability the moment it is wrong, because people trust it. Every page and policy should carry a named owner and a review cadence, with unowned content surfaced on its own. That matters twice over once an assistant answers from the same library. **16. What is the retention and eDiscovery position on employee conversations?** The question is whether frontline chat happens where retention, eDiscovery, moderation and audit apply, or in personal messaging groups the company cannot search. Off-channel communication fines passed $2.5 billion (SEC and CFTC enforcement actions, 2021 to 2024). Ask how private messaging is governed separately from company business. ## AI grounding (questions 17 to 20) The AI questions test whether an assistant is grounded in your content and governed by your rules. The arguments behind them are in [AI grounded in work](https://www.mangoapps.com/articles/ai-grounded-in-work) and [governing AI by design](https://www.mangoapps.com/articles/governing-ai-by-design). **17. What content does the AI answer from, and does it cite its sources?** Answers should come from your handbooks, policies and SOPs, with the source attached so a worker can check it. An assistant pointed at four uncurated repositories will answer confidently from the wrong version. **18. Does it inherit our existing permission model, or does it need a new one?** A second access model is a second thing to audit. Employees should not be able to reach a restricted document by asking a question, and one region should not receive another region's policy. **19. Is our data used to train public models?** The answer should be a plain no, and it should be in the contract. **20. What runs in production today, and what is on a roadmap?** Ask the vendor to mark every AI capability in the demo as production or roadmap, then ask to see the production ones on a live tenant. **Download *Frontline Worker Communication & Engagement*.** It includes the full question set and the scorecard below in a format your evaluation team can print and fill in. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) ## Score your shortlist Score each platform from 1, meaning no, to 5, meaning yes and demonstrated in front of you. A slide is not a demonstration, so a capability you only heard about scores a 3 at most. | # | Evaluation criterion | Vendor A | Vendor B | Vendor C | Vendor D | |---|---|---|---|---|---| | 1 | One shared data model, not integrated modules | | | | | | 2 | Works with no corporate email, device, or VPN | | | | | | 3 | Native app under our brand in both app stores | | | | | | 4 | Offline access and shared-device support | | | | | | 5 | Targeting by site, role, shift, and language | | | | | | 6 | Must-read and acknowledgment at message level | | | | | | 7 | Automatic re-send to people who have not viewed | | | | | | 8 | Emergency alerts with voice delivery | | | | | | 9 | Surveys and follow-up on one audience model | | | | | | 10 | Translation at publish, not as a project | | | | | | 11 | Delegated local publishing inside guardrails | | | | | | 12 | Content ownership and stale-content detection | | | | | | 13 | Acknowledgment reporting by site and shift | | | | | | 14 | AI answers from our content, citing sources | | | | | | 15 | AI inherits our existing permission model | | | | | | 16 | Our data not used to train public models | | | | | | 17 | HITRUST, SOC 2 Type II, and ISO 27001 (plus FedRAMP ATO for public sector) | | | | | | 18 | Adoption commitment in the contract | | | | | | 19 | Expansion is configuration, not re-implementation | | | | | Every column is blank, including the one you might expect us to fill in. Score MangoApps the way you score everyone else. ## How to read the score The total matters less than where the low scores fall. Rows 1, 9, 15 and 19 are the architecture rows. A vendor that scores low on those four and high everywhere else has assembled a product, and those rows are where it will fail in year two, when you add a capability, a region or an assistant. Rows 2 through 5 are the frontline rows. A vendor that scores low there was built for desks, and no amount of strength elsewhere changes who the product can reach. Row 18 is the one vendors are least comfortable with. Adoption in this category typically lands between 30% and 40%, and acknowledgment data is meaningless if a third of the workforce never opened the app. A vendor confident in its adoption will write a number into the contract. One that won't is telling you what it expects. The cost of a wrong choice here rarely shows up in the first quarter. It shows up when the second capability needs a second implementation, and by then the frontline has already learned whether the app is worth opening. Download the book for the printable scorecard and the full requirements behind it: [*Frontline Worker Communication & Engagement*](https://www.mangoapps.com/resources/frontline-communication-engagement-guide). Bring the scored sheet to a demo and [see it configured for your sites](https://www.mangoapps.com/schedule-a-call). *The AI Platform for the Frontline Workforce.* ## Frequently asked questions **What questions should I ask an employee communication platform vendor?** Ask twenty questions in five groups: architecture, frontline access, listening and measurement, governance and delegation, and AI grounding. The architecture questions matter most, because they reveal whether the platform shares one data model or connects separate modules. Ask the same questions of every vendor so the answers compare directly. **How do you tell one data model from integrated modules in a demo?** Ask the vendor to acknowledge a notice on a phone and watch whether the compliance view updates without a sync. On one data model, the confirmation writes to the same employee record compliance reads from, so the change is immediate. With integrated modules, a sync has to run first. A second test is to change an employee's site once and see whether audience membership and access follow on their own. **What certifications should a frontline communication platform have?** Look for HITRUST, SOC 2 Type II and ISO 27001 in combination, and FedRAMP ATO if you are in the public sector. A frontline platform often becomes the only corporate identity a worker has, on a personal device they own. Ask for the reports themselves, not a logo slide. **Should AI in an employee platform cite its sources?** Yes, AI answers should cite the policy, handbook or SOP they came from so a worker can check them. The assistant should also inherit your existing permission model, so nobody can reach a restricted document by asking a question. And your data should never be used to train public models. Get that last commitment in writing. **What should an employee app RFP include?** An employee app RFP should include the nineteen scorecard criteria, covering architecture, frontline access, acknowledgment and escalation, listening, governance, AI grounding, certifications and an adoption commitment. Ask vendors to demonstrate each one rather than describe it. Weight the architecture and frontline rows most heavily, because weaknesses there are the hardest to fix after purchase. **Why does it matter whether the app is in the app stores under our brand?** It matters because employees adopt the company's app and ignore a vendor's. An app listed under your name, with your logo and icon, reads as part of the job rather than one more piece of software someone bought. Adoption is the precondition for every other number you will report. **What is delegated local publishing and why ask about it?** Delegated local publishing lets a site leader publish what is true at their location without being able to publish company-wide. Without it, the channel carries only corporate content and employees stop reading. It is the requirement buyers miss most often because it looks like an admin setting. [What a frontline employee app actually requires](https://www.mangoapps.com/articles/frontline-employee-app-requirements) covers it in detail. **Should an adoption commitment be in the contract?** Yes, ask every vendor to put an adoption commitment in the contract. Adoption in this category typically lands between 30% and 40%, and acknowledgment or sentiment data is only as good as the share of the workforce using the platform. A vendor that won't commit to a number in writing is telling you something about its expectations. **What is the difference between a platform and a stack of point tools?** A platform shares one employee record across every capability, while a stack of point tools shares, at best, a login screen. With one record, an acknowledgment is a record rather than a report, and a survey and its follow-up share one audience. With a stack, every connection is a sync that can fail or fall behind. The distinction is set out in [what a platform means](https://www.mangoapps.com/articles/what-platform-means). --- # Answering Without a Supervisor: SOPs, Knowledge, and AI Search for the Frontline **Author:** Andy Tolton **Published:** 2026-09-24 **Category:** knowledge-management When answers are scattered, every routine question lands on the supervisor. Build one governed library a phone can use, then let employees ask it in plain language. *When the schedule lives in one system, the policy in another, and training in a third, a routine question has nowhere to go except a person, so it lands on the supervisor. Gartner found frontline employees accessed an average of 2.3 channels in 2025, a sign no single channel holds enough to be worth checking. The fix is two moves: one governed place for procedures and documents that works on a phone, then plain-language answers drawn from the policy itself, scoped to each employee's site and permissions.* An associate on a shift that crosses midnight wants to know how holiday pay works for the hours on either side of it. It's a two-minute question with a written answer, in a policy somebody wrote and approved. She asks it twice anyway. Once to the colleague next to her, who guesses. Once to her supervisor, who stops what he's doing and goes to look it up. Nothing in that exchange shows up in a report. It happens hundreds of times a week across a multi-site operation, and every instance costs the same two things: a worker who heard a guess first, and a supervisor pulled off the floor for a question a document could have answered. ## The two-minute question with nowhere to go The question goes to a person because no single place holds enough to be worth checking. The schedule is in one system, the policy in another, training in a third, pay in a fourth. Gartner (2025) found frontline employees accessed an average of 2.3 material channels. That number can read like choice. It isn't. Each channel holds a fragment and none of them holds the answer, so a worker with three minutes before the line starts has no reason to think the next app will do better than the last one did. Of the [six reach gaps behind most frontline communication failures](https://www.mangoapps.com/articles/why-frontline-communication-fails), this is the fourth, and it has an unpleasant side effect. It makes the second one worse. Gap 2 is the supervisor as the entire channel, the person who relays every update in between everything else the shift demands. Gap 4 quietly adds a help desk to that job. Every routine question with a documented answer that still routes to a person is a small tax on the role already carrying the most, which is the core of the argument that [the manager is not a channel](https://www.mangoapps.com/articles/frontline-manager-communication-overload). Nobody designed it this way. It is simply what happens when the answers live in more places than a worker can check between tasks, and a person is the one index that covers all of them. ## Three different answers waiting to be given An SOP that lives in three versions is not documentation. It is three different answers waiting to be given. One copy sits on a shared drive, one in a binder in the back office, one in somebody's saved email from the last time it changed. Which version a worker gets depends on who they happen to ask and what that person last read. Procedures are the content most expensive to get wrong and the most likely to be out of date. A stale promotion post embarrasses someone at the register. A cleaning procedure that is one revision behind, or a lockout step that changed after an incident, can hurt someone. And the people who knew which binder was current don't stay forever. McKinsey's 2024 retail frontline research puts turnover in the sector above 60% a year, so a large share of any floor is new at any moment. New employees are exactly the ones who cannot tell a current procedure from a retired one, and exactly the ones most likely to ask. The fix is not a better filing convention. It is two moves, in order. ## Move one: one place worth checking The first move is to give every procedure and document one governed home that works on the phone a worker already carries. Asking people to check one place only works if that place is worth the check, and making it worth the check is the job of [knowledge management built for the frontline](https://www.mangoapps.com/solutions/knowledge-management). ### Sites without a ticket When creating a site requires a ticket, the content ends up somewhere ungoverned instead. A regional manager who needs a home for a new facility and hears that her request is in the queue does not wait. She starts a shared folder or a group chat, and that becomes the place her people check. Department, region, and site homes should be buildable by the people who need them, by describing what the site should hold or dragging components into place. No code and no release cycle. Each site shows to the audience it serves, by department, location, role, or shift. A worker opening the app sees their site, not a directory of eighty-four others. ### One current version of every procedure Collaborative authoring with edit-conflict prevention means two people improving the same procedure at once don't overwrite each other. Full version history keeps every change recoverable, so "what did this say before the spring update?" has an answer. Read and edit permissions follow role, site, and team. A regional procedure is visible where it applies and nowhere else, and a draft revision stays invisible until it's approved. That last detail matters more than it sounds. A half-edited procedure read by the night shift is worse than the old one. ### Written for a phone A procedure delivered as a long document becomes something to pinch and scroll with gloves on. Procedures have to render for a small screen, in sections a person can read standing up. Search has to work the way people think, too. Semantic search finds the right passage from a description of the problem, the label printer that keeps jamming, rather than from a document title nobody remembers. ### Libraries reachable from the floor Policies, forms, training materials, benefits documents, and safety data all end up somewhere, and usually in several somewheres. Structured libraries give each resource one governed home, with automatic versioning and previews so nothing has to be downloaded to be read. Global search runs across every library at once. Offline availability covers what matters in cold storage or in a van with one bar of signal. A safety data sheet that needs a desktop to open is not available. It's a file. Local ownership holds all of this together. Headquarters cannot maintain the procedures for every facility, and shouldn't try. Site and department owners publish and maintain their own content inside a structure set centrally, which is the difference between a library that reflects each location and one that carries only corporate content. **Download *Frontline Worker Communication & Engagement*.** Its Knowledge & Answers section walks through each capability and the gap it closes, and its scoring page shows how open Gap 4 is at your own sites. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) ## Move two: make it answer Documentation only closes the gap if a worker can get an answer without knowing where the answer lives. The associate on the overnight shift is not going to search for a file called Holiday Pay Policy v4. She's going to type the question she asked her colleague. ### Ask in plain language The employee describes the problem instead of guessing a file name or a folder path, and asks in the language she works in. The answer comes back with its sources attached. On the floor that matters for a practical reason. When the worker can open the passage the answer came from, she can check it herself, and if she still takes it to her supervisor, they are both looking at the same text rather than two memories of it. ### Your content, your permissions Retrieval runs on your own handbooks, policies, SOPs, and libraries, gated by the access rules already in place. One region does not receive another region's policy. An employee cannot reach a restricted document by asking about it conversationally. This is what makes the holiday-pay answer useful rather than generic. It is scoped to the employee's own site and employment type, so a part-time associate at one location and a full-time associate at another each get the rule that applies to them. A general answer about how holiday pay usually works would have been the colleague's guess again, only faster. ### Specialists where the subject deserves one Some subjects need an assistant of their own. Assistants can be stood up from a specific document set for benefits, safety, or onboarding, each branded and scoped to its material, with routing across them so a question about an enrollment window reaches the benefits assistant rather than a generalist. Assistants the organization already runs can be connected instead of rebuilt. ### Privacy Employee data and company knowledge are not used to train public models. That is usually the first question a CHRO or a CIO asks about any of this, and the answer should fit in one sentence. The broader case for AI [grounded in the work itself](https://www.mangoapps.com/articles/ai-grounded-in-work), and for [governance designed in from the start](https://www.mangoapps.com/articles/governing-ai-by-design), is made elsewhere. On the frontline the test is narrower and harder to fake. Does the associate get the right answer, for her site, before her break ends? ## The precondition nobody demos: the library has to be right A knowledge base becomes a liability the moment it's wrong, because people trust it. Content doesn't announce that it has expired. The policy is superseded, the owner leaves the company, and the page keeps being read. When a person is the index, stale content at least meets some skepticism. An assistant quotes it fluently, with a source link. Every page and document needs a named owner and a review cadence. Expiration alerts reach the owner before content goes stale, not after a worker has followed it. Unowned content, the pages whose author left two reorganizations ago, gets surfaced rather than left to drift. Freshness becomes a measurable state across the whole content estate, so "is our library current?" has a number behind it instead of a shrug. This is where AI stops being a feature and becomes a platform question. The governance engine that flags a stale policy page and the assistant that answers from that page have to read the same library. An assistant pointed at four uncurated repositories will answer confidently from the wrong version, and nobody finds out until someone acts on it. A governance agent that surfaces stale pages, duplicates, and unowned content, then nudges owners to update or retire them, is what keeps the rest of the AI worth trusting. It is also why the AI decision belongs to the Employee Platform decision rather than to a separate tool purchase. Nobody puts this in a demo. It decides whether the demo is still true a year later. ## What changes for the supervisor The supervisor stops being the help desk for questions that already have written answers. Much of what reaches a supervisor on a given shift is not a judgment call. It's a pay stub, a benefits question, a form, the right person to call at another site. Self-service and governed answers handle those, and the supervisor stays available for what needs a supervisor: the new hire on her second day, or the customer complaint that is starting to escalate. The time adds up. The illustrative business case model in the book uses a 5,000-employee multi-site employer with roughly 4,000 frontline workers and 250 supervisors, each spending three hours a week relaying information and answering routine questions. That comes to 150 hours a year per supervisor, about $1.2 million a year at a fully loaded $32 an hour. If direct delivery and self-service absorb one third of it, roughly 12,500 hours go back to supervising, worth about $400,000 a year. The model is a structure for running your own numbers rather than a forecast, and the full version sits inside [the business case for frontline communication](https://www.mangoapps.com/articles/frontline-communication-business-case). The dollar figure is the smaller half of it. Those hours were being spent in the aisle, at the station, in the middle of the shift, which is where a supervisor is worth the most. The holiday-pay question will still get asked. What changes is who answers it first, and what the supervisor gets to do instead. **Get the full Knowledge & Answers section** in *Frontline Worker Communication & Engagement*. [Download the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) Score yourself on the Gap 4 question from the [frontline communication audit](https://www.mangoapps.com/articles/frontline-communication-audit). Can an employee answer a policy, pay, schedule, or training question without asking a person? Or [see it configured for your sites](https://www.mangoapps.com/schedule-a-call). *The AI Platform for the Frontline Workforce.* ## Frequently asked questions **How do frontline workers find company policies?** They find them in one governed place on their phone, and they ask it in plain language instead of hunting for a file. When policies are spread across a shared drive, a binder, and an intranet built for a desk, the fastest route to an answer is a person. A single library that renders for mobile, with search that works from a description of the problem, changes that. Answers drawn from the policy itself, with the source attached, finish the job. **What is the best way to manage SOPs across multiple sites?** Keep one current version of each procedure, permissioned by site, rendered for a phone, with full version history. Collaborative authoring with edit-conflict prevention stops two editors overwriting each other. Site and role permissions make a regional procedure visible where it applies, and draft revisions stay hidden until approved. Version history means any change can be traced and recovered when an auditor or an incident review asks. **Can AI answer employee HR questions from the handbook?** Yes, provided it retrieves from your own content, inside your existing permissions, and cites its sources. An answer about holiday pay or leave should come from the current handbook and be scoped to the employee's site and employment type. The citation lets the worker verify the passage herself. An assistant that answers from general knowledge instead of your policy is guessing, however fluent it sounds. **How do you keep an employee knowledge base accurate?** Give every page and document a named owner and a review cadence, then let the system chase them. Expiration alerts reach owners before content goes stale. Content whose owner has left gets surfaced rather than quietly read for another year. Tracking freshness across the whole library turns accuracy into a number you can report and act on. **Why does AI need governed content?** Because an assistant answers confidently from whatever it's given, including the wrong version. Pointed at several uncurated repositories, it will find a superseded policy as easily as the current one and present both with the same assurance. When the governance engine and the assistant read the same library, the owner who fixes a flagged page is fixing the page the assistant answers from. That's why the AI decision sits downstream of the platform decision. **What is a mobile knowledge base for frontline employees?** It's a governed library of procedures, policies, forms, and training that renders properly on a phone and still works where connectivity doesn't. Content is structured for a small screen rather than delivered as documents to pinch and scroll. The material that matters in low-signal sites is available offline. Permissions by site and role mean each worker sees what applies to them, not every other location's material. **Should local sites be able to publish their own content?** Yes, inside guardrails set centrally. Headquarters cannot maintain every facility's procedures, and when local leaders have to file a ticket to publish, the content moves to a shared folder or a group chat nobody governs. Delegated publishing lets site owners maintain what is true at their location while the central team sets the structure and the permissions. **Is employee data used to train public AI models?** No. Employee data and company knowledge are not used to train public models. Retrieval runs on your content inside your existing permission model, and restricted documents stay restricted when someone asks about them conversationally. Ask every vendor the same question and expect a one-sentence answer. **How much supervisor time does self-service recover?** In an illustrative model, about 12,500 hours a year, worth roughly $400,000. The model assumes a 5,000-employee employer with 250 frontline supervisors, each spending three hours a week relaying information and answering routine questions, with a third of that absorbed by direct delivery and self-service. Your figure depends on your own headcount and supervisor ratio, and [the business case for frontline communication](https://www.mangoapps.com/articles/frontline-communication-business-case) shows how to run it. --- # Why a Mobile-Responsive Intranet Does Not Reach Frontline Workers **Author:** Andy Tolton **Published:** 2026-09-23 **Category:** employee-app The desk model assumes an inbox and an assigned device, plus five more things frontline work does not provide. A smaller screen fixes one of the seven. *Once the reach gap is visible, the instinct is to extend what already works: make the intranet responsive, add a mobile view to the communications platform. It does not transfer. The desk model rests on seven assumptions (an inbox, an assigned device, working-hours access, reliable connectivity, hours of attention, a shared language, stable tenure), and frontline work violates every one. A responsive intranet answers exactly one of the seven. The answer is a different product with a different center of gravity.* A line cook finishes prep at 5:50 with ten minutes before service and a phone in his apron. The company intranet works on that phone now. It looked great in the demo. He has never opened it, because signing in needs a corporate email address he was never given, and nothing on the homepage is about his kitchen. Making the intranet responsive fixed the one thing that was never stopping him. Roughly 80% of the global workforce is deskless (Emergence Capital, 2018; share reconfirmed by BCG, 2024), and once an organization sees [why frontline communication fails](https://www.mangoapps.com/articles/why-frontline-communication-fails), the first fix it reaches for is usually a mobile version of what headquarters already uses. It's a reasonable instinct. The reasons it fails have nothing to do with how good the mobile version is. ## Three categories of software, each solving a piece Frontline workers are hard to reach because three categories of software each solved one piece of the problem, and none was built to solve the whole of it. Communication platforms were built for the communications team. They are strong at authoring, campaigns, and brand control, and they assume the person on the other end has an inbox. Intranets were built for desk workers, as destination websites you visit from a computer during working hours. Frontline point tools were built for one slice of the job each, whether that slice is scheduling, tasks, or training. Each of those tools arrived with its own login, its own idea of who an employee is, and no knowledge of the rest of the worker's day. Each of those decisions was reasonable in isolation. Stacked together, they produced an organization where reaching a single frontline worker can take four systems. And when someone asks whether that worker actually received the message, none of the four can answer. Nobody designed this outcome. It accumulated one sensible purchase at a time. ## The instinct to extend, and why it is the wrong instinct Extending the desk model to the frontline feels like the responsible move, and it is the wrong one. The options look sensible on a slide. Make the intranet mobile-responsive. Add an app to the communications platform. Give the frontline a lighter version of what headquarters uses. The content already lives there and IT has already secured it. It does not transfer, and the reason is not effort or polish. A better mobile team would not fix it, and neither would a bigger launch campaign. The desk model rests on seven assumptions about the person using it. Frontline work violates all seven, and a smaller screen addresses only one. ## Seven assumptions, seven failures Every assumption the desk model makes is false for most frontline workers, and each false assumption breaks something specific. | The desk model assumes | Frontline reality | What breaks | |---|---|---| | An inbox | No corporate email address | Delivery. Nothing sent by email exists. | | An assigned device | A personal phone, or a shared device | Sign-in, security posture, and any persistent session | | Access during working hours | Shift-limited windows, often unpaid time | Timing, and the ethics of expecting engagement off the clock | | Reliable connectivity | Plant floors, cold storage, basements, vehicles, remote sites | Anything that needs a live connection to read | | Hours of attention | Two or three minutes between tasks | Long-form content, multi-step menus, anything that needs a second visit | | A shared working language | Mixed-language crews on a single shift | Comprehension, and every downstream measure of it | | Stable tenure | Turnover above 60% in some sectors | Institutional memory. The population is always partly new. | 1. **An inbox.** Most frontline workers have no corporate email address, so the newsletter and the policy update simply do not exist for them. The message isn't late or ignored. It is absent. In one survey, 63% of frontline workers said messages from leadership do not reach them (Microsoft Work Trend Index Special Report, 2022). 2. **An assigned device.** The frontline works on a personal phone or on a shared device at a station. That changes sign-in, because a desk login assumes a corporate identity the worker doesn't have, and it changes security, because company content now sits on a phone the company does not own. On a shared tablet there is no persistent session either. The next person on shift picks it up. A channel for this workforce needs sign-in with no password and no corporate email, plus protection for company content on a personal phone. 3. **Access during working hours.** A desk worker reads company news at ten in the morning with a coffee. A frontline worker's access comes in shift-limited windows, and time outside the shift is often unpaid. That raises a question the desk model never had to answer: is it fair to expect someone to read company updates off the clock? The honest design answer is quiet hours for anything non-urgent, with an exemption only for genuine emergencies. 4. **Reliable connectivity.** Plant floors, walk-in freezers, basements, delivery vehicles, and remote sites all have one thing in common. A page that needs a live connection to load is unreadable there, and these are often the places where the safety procedure matters most. Content has to be readable offline. 5. **Hours of attention.** The frontline has two or three minutes between tasks. Long-form content fails in that window, and so does anything that takes four taps to find or a second visit to finish. An intranet is organized for someone browsing. A worker on a break is checking what changed and what they need to do next. 6. **A shared working language.** One shift can run in three or four languages. When translation is a separate project, it arrives days late and drifts from the original, and comprehension goes with it. So does every downstream measure. An acknowledgment from someone who couldn't read the message proves nothing. Content has to be translated at the moment of publishing into the languages crews actually work in, and a correction to the original has to correct every version. 7. **Stable tenure.** Retail frontline turnover runs above 60% a year (McKinsey retail frontline research, 2024). Intranets quietly reward tenure, because you get good at them by learning which page holds the form and which site the policy lives on. A population that is always partly new never builds that memory. The two-week-old employee, who has the most questions, is the one least able to find the answers. > A mobile-responsive intranet answers one of these seven. **Download *Frontline Worker Communication & Engagement*.** It includes the full seven-assumption breakdown and the six-gap scorecard to run on your own operation. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) ## What responsive design actually changes, and what it does not Responsive design changes the size of the screen, and screen size was never the barrier. A responsive intranet is a website rendered on a smaller screen. It is still reached through a login built for a desk identity. It is still organized for someone browsing rather than someone checking. It still needs a connection to load and still publishes in the language headquarters writes in. Of the seven assumptions, it answers the device question in the narrowest possible sense. The page now fits the phone. What kept frontline workers out was identity, organization, and connectivity. A field technician with no company email can't sign in to a beautifully responsive site. A warehouse associate who can sign in still faces a homepage designed for the marketing team's news. Santee Cooper, a public electric and water utility in South Carolina with more than 1,600 employees, described the gap in terms that have nothing to do with screen size. > "People in the field can sometimes be disconnected with what's happening corporate-wide. That's just a natural result when your jobsite is a turbine floor or a bucket truck. That means a lot of our folks have limited access to a computer. The Coop gives us a way to close that gap." > > Jeffrey Straight, Public Relations Specialist, Santee Cooper None of this is a criticism of the intranet. It does the job it was designed for. The point is what it was designed for. When someone says "we already have an intranet," the fair reply is that you have solved this for the people with a desk. The useful follow-up question is what share of your workforce logged into it last week, and whether you can answer that by site. We've written separately about [how to answer "we already have an intranet"](https://www.mangoapps.com/articles/we-already-have-an-intranet), and the usage numbers are covered in [the frontline AI blind spot](https://www.mangoapps.com/articles/frontline-ai-blind-spot), so they aren't repeated here. ## What changed that makes a different product possible now Three things changed, and together they make a product built for the frontline possible in a way it was not a decade ago. The first is the device. Every frontline worker now carries a capable phone, so the hardware problem has largely solved itself. The remaining barrier is whether the company has anything worth putting on that phone that doesn't require a corporate email address to sign in. The second is architecture. It became possible to run one employee record, one permission model, and one content layer across communication, knowledge, and engagement, rather than integrating four systems that each hold a partial copy of the employee. That is an architectural change, not a feature release, which is why it took as long as it did. It is also the difference between [a platform and a bundle of tools sold together](https://www.mangoapps.com/articles/what-platform-means). The third is AI, and it moved the timeline. Consolidation used to be a hygiene argument that lost to more urgent priorities. Now it is the precondition for everything an organization wants AI to do for employees, because an assistant can only answer from content that is current, governed, and in one place. The fragmentation that kept the frontline in the dark is the same fragmentation that will keep an assistant from answering a frontline worker's question correctly. ## A different center of gravity The answer is an employee app for the whole workforce, designed first for the people without a desk, that also serves the desk. Not the reverse. Where you start decides what you get. Design for the associate with three minutes and no inbox, and the person at a laptop loses nothing, since they get the same content in the same app and a browser besides. Design for the laptop and shrink it, and the frontline gets a smaller version of something built for someone else. That center of gravity turns into concrete requirements: reach without corporate identity, offline content, translation at the moment of publishing, targeting by site, role, and shift, and acknowledgment at the level of the individual message. We've laid out [the ten requirements a frontline employee app has to meet](https://www.mangoapps.com/articles/frontline-employee-app-requirements) as a buyer's list, written to be used before any vendor demo. The order in which a product satisfies them tells you who it was originally built for. An Employee Platform that starts with the frontline can carry communication, answers, recognition, and the work of the shift in one app, on one employee record, because it never assumed the desk in the first place. That is what a [branded employee app built for the frontline](https://www.mangoapps.com/solutions/employee-app) is meant to be. The intranet can keep doing the job it was bought for. The decision in front of you is who the next system is built for, and whether the answer is the deskless majority your current channels were never designed to reach. **Download *Frontline Worker Communication & Engagement*** for the seven assumptions and the requirements that follow from them. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) Want to see what that looks like for your workforce? [See it configured for your sites](https://www.mangoapps.com/schedule-a-call). *The AI Platform for the Frontline Workforce.* ## Frequently asked questions **Can a mobile intranet work for frontline employees?** Only for the ones who already have a corporate login and a desk habit. A mobile intranet fixes screen size, not identity or how the content is organized. A worker with no corporate email still can't sign in, and one who can still finds a site built for browsing rather than a two-minute check between tasks. **What is the difference between an intranet and an employee app?** An intranet is a destination site built for browsing from a desk, while an employee app is a channel and workspace built for checking. The app is built for workers with no corporate email, working on personal or shared phones where the signal drops. It comes to the worker through targeted notifications instead of waiting to be visited. And it holds the work of the shift alongside the news, which gives people a reason to open it every day. **What is the difference between an employee communication platform and an intranet?** A communication platform is an authoring and campaign tool for the communications team, and an intranet is a destination site for desk workers. Both are useful at what they were built for. Neither assumes the recipient has no inbox. So neither reaches a frontline worker directly, and neither can prove the message landed. **Why do companies need several systems to reach frontline workers?** Because three categories of software each solved one piece of the problem. Communication platforms handle authoring, intranets handle destination content for desk workers, and frontline point tools each handle one slice of the job with their own login. Reaching a single worker can take four systems, and none of them can say whether the message arrived. **Do frontline workers use the company intranet?** Rarely during a shift. Most have no corporate login to reach it, and the few minutes between tasks aren't enough for a site organized for browsing. The [frontline AI blind spot](https://www.mangoapps.com/articles/frontline-ai-blind-spot) covers the usage data in detail. The fastest internal test is to check what share of your frontline logged in last week, broken out by site. **What assumptions does a desk-based intranet make?** It assumes seven things: an inbox, an assigned device, access during working hours, reliable connectivity, hours of attention, a shared working language, and stable tenure. Frontline work violates every one. Each broken assumption breaks something specific, whether that is delivery, sign-in, comprehension, or institutional memory. **Should we replace our intranet to reach the frontline?** Not necessarily. The intranet can keep serving the people at desks, which is the job it was built for. The real question is whether anything you run today reaches the employee with no inbox and proves the message landed. If nothing does, that is the gap to close first. **What is a frontline point tool?** A frontline point tool is a single-purpose app for one slice of frontline work, such as scheduling, tasks, or training. Each one comes with its own login and no knowledge of the rest of the worker's day. Individually they are reasonable purchases. Stacked together, they hand the worker several logins and give the company several partial copies of who each employee is. **What changed to make frontline communication solvable now?** Devices, architecture, and AI. Every frontline worker now carries a capable phone. Platform architecture matured enough to run one employee record, one permission model, and one content layer across communication, knowledge, and engagement. And AI turned that unified layer from tidy into necessary, because an assistant can only answer from content that is current, governed, and in one place. --- # Frontline Listening That Closes the Loop: Pulse Surveys, Sentiment, and Recognition That Reaches the Floor **Author:** Andy Tolton **Published:** 2026-09-23 **Category:** employee-engagement Surveying more often rarely moves frontline engagement. What moves it is a return path that reaches workers with no inbox, protects anonymity, and visibly acts on what they say. *Global engagement stands at 20%, the lowest since 2020 (Gallup State of the Global Workplace, 2026), with hourly retail and manufacturing workers at the bottom. Measuring more often rarely helps, because asking and acting sit in different systems and nothing visibly changes. A frontline listening loop has to reach people without an inbox, take two minutes, stay structurally anonymous, surface patterns across sites, and close the loop with the people who raised the issue. Recognition is the other half, the organization answering the floor.* Somewhere on a distribution center floor, a picker has worked out that the new putaway procedure doesn't fit how the dock actually runs. So has everyone else on her shift. They've built a workaround, it mostly works, and it will stay invisible until the day it doesn't. Nobody at headquarters knows. There was never anywhere to tell them. ## The organization learns what it said and never learns what the floor knows Most frontline communication runs in one direction, and that single design choice is why organizations are routinely surprised by their own workforce. Headquarters publishes and the floor receives. There is no return path. It is the third of the [six reach gaps](https://www.mangoapps.com/articles/why-frontline-communication-fails) that open when communication infrastructure assumes a desk, and it is the one that hides the others. Without a return path the organization still finds out what the floor knows. It just finds out late. The information arrives as a resignation, a safety incident, or a survey result twelve months after anyone could have acted on it. By then the picker's workaround has become the procedure at four sites, and the people who could have explained it have moved on. The engagement numbers give that silence a scale. Global employee engagement fell to 20% in 2025, its lowest level since 2020 (Gallup State of the Global Workplace, 2026). Break the figures down by who does the work and hourly workers in retail and manufacturing sit at the bottom of Mercer's range, tied at 65%, lower than any other group ([Mercer, Inside Employees' Minds, 2025](https://www.mercer.com/en-us/insights/talent-and-transformation/attracting-and-retaining-talent/rebuilding-trust-addressing-the-workforce-crisis-in-retail-and-hospitality/)). Those are the people who meet the customer. Chelsea Carbahal of The Raley's Companies put the connection plainly. > "Our frontline employees determine whether or not a customer is going to come back to the store. In order to provide a great customer experience, you've got to provide a great experience to your team members. If you're not engaging with them, it's less likely that they're going to deliver on this, simply because they haven't been enabled and supported to do it." > > Chelsea Carbahal, VP of Community Impact & Public Affairs, The Raley's Companies ## Why the annual survey cannot be the return path The annual engagement survey cannot close Gap 3, because it was built to describe the past rather than to change the present. It tells you about a year you can no longer change. The results land months after the questions were asked, and by the time a site's score has been analyzed and presented, the manager who caused the dip may have left and the people who reported it may have followed. It is also answered mostly by the people already engaged enough to answer. A result drawn from the most connected third of a workforce gets presented as data about all of it. Sentiment read from a self-selected minority is arguably worse than no data, because it looks like data. On the frontline there is a more basic failure. The survey usually arrives by email, to an inbox most frontline workers do not have. In Microsoft's research, 63% of frontline workers said messages from leadership do not reach them (Microsoft Work Trend Index Special Report, 2022). A survey invitation is a message from leadership. It shares the same fate. The instinct, once participation disappoints, is to survey more often. Quarterly instead of annually. Monthly pulses on top. But running the same instrument through the same channel more frequently produces more of the same result, faster. The response rate among the unreachable stays at zero however often you ask them. ## What a frontline survey has to be A frontline survey has to meet three conditions the annual instrument was never designed for. It has to reach everyone, it has to fit into the few minutes a shift allows, and it has to be anonymous in a way a worker can believe. ### Reaches everyone, then reminds Distribution comes first. A frontline survey goes out through the employee app, push notification, and SMS to the whole workforce, not to an email list that quietly excludes most of the floor. People who have not responded get reminded. And response rates are visible by site while the survey is still open, so the regional manager can see on day three that two stores are at single digits and do something about it before the window closes. That last point changes the job. A response rate you only see at the end is a report card. A response rate you can see while it's open is something you can still fix. ### Two minutes A cashier on a ten-minute break will answer three questions. She will not answer forty. Short recurring pulses and post-shift check-ins fit the time a frontline worker actually has, and they should draw on the same question library as the annual instrument, so the results stay comparable. Once reach is solved, frequency becomes a choice rather than a constraint the tool imposes. An organization might run a sixty-second check-in at the end of every shift at one site during a change program, and a monthly pulse everywhere else, with the full instrument once a year. The decision belongs to the people running the program, not to the software. ### Anonymous by design Anonymity has to be enforced structurally, not promised in the invitation. A line of reassuring text at the top of a survey means little to a warehouse associate who knows her team has six people in it. What earns trust is a platform that will not show site or team results until a minimum number of responses has come in, so no manager can trace a small group's answers back to a name. That structural guarantee is what makes answers honest. Without it, the people with the most useful criticism are the ones most likely to stay quiet or to answer the way they think is expected. ## Individual answers add up to a pattern nobody would have reported The value of frontline listening is in the aggregate, where small answers add up to something nobody would have raised on their own. Take a sixty-second check-in at the end of a shift that asks what worked and what didn't. Any single response is minor. One person mentions that a step in the returns procedure is slow. Another says the new form doesn't match the handheld. Aggregated across sites and weeks, those answers surface a pattern nobody would have reported formally, a procedure being worked around at four locations. Nobody at those sites thought it worth escalating. Surveys alone can't produce that picture, because surveys are periodic. A continuous read of workforce sentiment draws on real platform activity and explicit feedback together, so the picture keeps updating between surveys. It breaks out by site, role, shift, and tenure, which is where the real variation lives. A company average hides the one region sliding while the others hold steady. This is work AI does well when it sits on the right foundation. No analyst can read thousands of open-text comments by hand every week and spot the segments trending down. An AI layer can, provided it reads from the same employee record and the same audience definitions as everything else on the platform. Pointed at an export, it produces a report. Built into the platform, it can recommend the action and the audience while there is still time to act. What comes out is specific. The recurring theme is not "scheduling satisfaction is down two points." It is that three sites in the same region are raising the same scheduling issue, in their own words, and have been for a month. That difference is the whole argument for funding the program. Engagement programs lose funding because they produce a score rather than a decision. A pattern with a location and a named group of people attached to it produces a decision. **Download *Frontline Worker Communication & Engagement*.** It shows how listening, recognition, and communication share one audience model, and what that makes possible for an HR team that has to prove engagement is worth funding. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) ## Closing the loop is the whole point Closing the loop is the single strongest determinant of whether anyone answers the next survey. Everything else in a listening program depends on it. It is also where most programs break, and they break for a structural reason. Closing the loop is nearly impossible when the survey tool and the communication tool hold separate audience definitions. The survey platform knows that the second-shift team at three sites flagged a scheduling problem. The communication platform has its own lists, built differently, maintained by someone else, and out of date by a different amount. Getting a message to exactly the people who raised the issue means an export, a match, and a guess. The group you surveyed has to be the group you follow up with, defined once. That is only true when listening and communication sit on one shared data layer with one employee record, which is what separates [a platform from a set of tools sold together](https://www.mangoapps.com/articles/what-platform-means). The follow-up itself has to do something specific. It should reference what employees said, in terms they will recognize as theirs. "Second shift at three of our sites told us the new rota leaves no time for handover, and here is what changes next week" is a message a worker reads and remembers. "Thank you for your feedback, we are reviewing the results" is a message that teaches her not to bother next time. The part of the follow-up that references what people said is the part that determines whether anyone answers again. Then measure. Act, communicate, and check whether sentiment in that segment moved. If it did, the program has evidence that listening changes outcomes. If it didn't, the organization has learned that the fix missed, while there is still time to try another. This is the listening marker that matters most in the first months of any rollout. Among the [90-day markers for frontline platform adoption](https://www.mangoapps.com/articles/frontline-employee-app-adoption), the first listening cycle that produced a visible action, communicated back to the people who raised it, is the one most organizations skip. It is also the one that decides whether the return path stays open. Nothing comes back from the floor until something visibly changes. ## Recognition is the organization answering the floor Recognition is the other half of the listening loop. Surveys are the floor speaking to the organization. Recognition is the organization speaking back to the floor, one person at a time. It is also the program that most reliably fails to reach the frontline, and the reason is structural again. Recognition depends on a supervisor remembering, having a channel, and having time. Frontline supervisors are short on all three, and they are already carrying [more of the communication load than any other role](https://www.mangoapps.com/articles/frontline-manager-communication-overload). A recognition program that adds work to that supervisor's shift will not be delivered, however good the intentions. The stakes justify getting it right. [Gallup found](https://www.gallup.com/analytics/472658/workplace-recognition-research.aspx) that well-recognized employees are 45% less likely to have turned over two years later. On a workforce where replacing each person costs roughly a third of their salary, that is not a morale initiative. Four design choices decide whether recognition reaches the floor. ### From any device, in the same app Peer recognition, kudos, and shout-outs have to be sent from the phone, in the same app where the schedule and the news already live. No desk, and no nomination window that opens once a quarter. A picker who sees a colleague cover a gap on the line should be able to say so in the thirty seconds before the next pallet, and the colleague should see it before the shift ends. ### Prompted, not remembered The platform should watch for milestones such as work anniversaries, and for standout activity, then prompt a manager or peer at the moment with a one-tap send. That turns recognition from an intention into a habit. The supervisor who meant to mark someone's fifth anniversary and lost track of the date is not a bad manager. She's a busy one, and the system should be carrying the reminder so she doesn't have to. ### The report that matters shows who is not being recognized Structured award programs still matter, with approval routing and budget tracking against allocation. But the most useful view in any recognition program is the gap report, which shows who is being recognized and who is not. Recognition drifts toward whoever works closest to a manager. A report that shows a night shift or a remote site receiving almost nothing is a finding a CHRO can act on. ### Tangible for an hourly workforce Recognition that stays symbolic works for a while. For an hourly workforce, a program that converts to something tangible carries more weight. Points should accrue from recognition, awards, and completed activity, with the balance and history visible at all times. The catalog should be one the organization controls, varied by region so rewards are relevant and deliverable where people live. Two conditions keep it working. Employees have to trust the points, because a points system nobody trusts is worse than none. And finance has to get reporting and reconciliation rather than a spreadsheet, which is what keeps the program funded past its first budget cycle. Santee Cooper, a public not-for-profit electric and water utility in South Carolina serving more than two million people, shows what happens when recognition finally reaches the field. Its 1,600-plus employees work across offices, generating stations, water plants, and field crew quarters. After moving to The Coop, the app employees named themselves through a naming contest, recognition activity doubled. > "The Coop really gives us the ability to get messages out across the team, immediately. Whether it's a CEO update, a safety alert or just recognizing someone's work, it's all in one place. Employees can scroll through recognitions, see what's happening, and feel connected to the larger organization." > > Jeffrey Straight, Public Relations Specialist, Santee Cooper At Santee Cooper, recognition and surveys arrived after communication, on an app employees already had and already trusted. Neither required a second implementation, and neither became one more tool a field worker had to find. ## What changes for the CHRO For the CHRO, engagement stops being an annual retrospective and becomes a measured input. Sentiment reads from real activity, not just a questionnaire. Risk segments surface while there is still time to act on them. And the connection between feeling informed and staying becomes visible in the same system that holds the employee record, instead of being argued from two reports that never quite agree. This is what [employee engagement built for the frontline](https://www.mangoapps.com/solutions/employee-engagement) changes in the budget meeting. An engagement program that can show a site trending down in March, a follow-up sent to the people who raised the issue in April, and sentiment in that segment recovering by June has evidence. A program that shows an annual score has an opinion. There is one question that tells you where your own organization stands. It comes from [the frontline communication audit](https://www.mangoapps.com/articles/frontline-communication-audit), and it is the Gap 3 question. In the last 90 days, has anything a frontline employee told you visibly changed a decision? If the honest answer is no, the problem is not survey design or question wording. It is that the floor has learned nobody is listening, and it will keep behaving accordingly until something visibly changes. **Download *Frontline Worker Communication & Engagement*** to see how listening, recognition, and communication work on one employee record. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) Score your own return path with [the frontline communication audit](https://www.mangoapps.com/articles/frontline-communication-audit), or [see it configured for your sites](https://www.mangoapps.com/schedule-a-call). *The AI Platform for the Frontline Workforce.* ## Frequently asked questions **How often should you survey frontline employees?** Run short pulses frequently and a full instrument annually, drawing both from one question library. Frequency is a choice once reach is solved. A sixty-second post-shift check-in or a monthly pulse catches problems while they can still be fixed, and the annual survey gives a stable baseline. The mistake is surveying more often through a channel that doesn't reach the floor. **How do you keep frontline surveys anonymous?** Enforce anonymity structurally rather than promising it in the invitation. The platform should withhold site or team results until a minimum number of responses has come in, so nobody can trace a small group's answers back to an individual. Frontline teams are often small, which makes this matter more there than anywhere. **Why do employee survey response rates fall?** Response rates fall when nothing visibly changed after the last survey. Employees who took the time to raise an issue and heard nothing back learn that answering is pointless. On the frontline there is a second cause, which is that invitations sent by email never reach workers without a corporate inbox. Fixing reach and closing the loop both have to happen for rates to recover. **What does closing the loop mean in employee listening?** Closing the loop means following up with the people who raised an issue, referencing what they said, then measuring whether sentiment in that segment moved. The follow-up has to go to the same group that was surveyed. That is only practical when the survey and the communication share one audience definition. The reference to what employees said is what determines whether they answer next time. **What is workforce sentiment analysis?** Workforce sentiment analysis is a continuous read of engagement health drawn from platform activity and explicit feedback, broken out by segment. It shows which sites, roles, shifts, or tenure groups are trending down and which themes keep recurring in open feedback. Done well, it recommends an action and an audience, not just a number. **How do you survey employees who do not have email?** Send the survey to the worker's phone through the employee app, push notification, and SMS. None of those channels needs a corporate email address. Reminders should go automatically to people who haven't responded, and response rates should be visible by site while the survey is open, so gaps can be addressed before it closes. **Why does employee recognition not reach frontline workers?** Recognition depends on a supervisor remembering, having a channel, and having time, and frontline supervisors are short on all three. Desk-based nomination forms and quarterly windows miss the floor entirely. What works is recognition sent from the phone and prompted automatically at milestones, with reporting that shows who is being missed. **Does recognition reduce turnover?** [Gallup found](https://www.gallup.com/analytics/472658/workplace-recognition-research.aspx) that well-recognized employees are 45% less likely to have turned over two years later. On a frontline where each departure costs roughly a third of that person's salary to replace, recognition is a retention lever as much as a morale program. The condition is that it actually reaches the floor, which is exactly where recognition most often fails. **Should frontline recognition include tangible rewards?** For an hourly workforce, usually yes, because recognition that converts to something tangible carries more weight than symbolic praise alone. Two conditions decide whether it works. Employees must be able to see and trust their points balance and history. And finance needs reporting and reconciliation rather than a spreadsheet, which is what keeps the program funded. --- # Where frontline context gets lost between shifts **Author:** MangoApps Team **Published:** 2026-09-22 **Category:** mango-scoop Explore the hidden cost of lost context, shift handoffs, Recorder and AI Sheets, plus updates to mobile Workspaces and the Content Calendar. Hand-picked stories from MangoApps this week. ## The Hidden Tax of Lost Context in Frontline Operations ![The Hidden Tax of Lost Context in Frontline Operations](https://mango-cdn.b-cdn.net/images/blog-thumbnails/blog_705_20260920_140351.png) She's two weeks into the supervisor role and already asked the same question twice this week: "Did we ever figure out why the evening shift keeps running short?" Her manager can't remember. The... [Read the full story →](https://www.mangoapps.com/articles/the-hidden-tax-of-lost-context-in-frontline-operations) --- ### More to read #### Where frontline work breaks down between shifts Explore the shift handoff problem, compare frontline communication platforms, and see what's new in Recorder and AI Sheets workbooks. [Read more →](https://www.mangoapps.com/articles/mango-scoop-2026-09-15) --- ### What's New **General** — [Product Update - September 21, 2026](https://www.mangoapps.com/changelog/3147) * **[Communications Content Calendar](https://www.mangoapps.com/directory/app/communications)** — Planned content slots now appear directly on the Communications Calendar alongs... **General** — [Product Update - September 20, 2026](https://www.mangoapps.com/changelog/3146) * **[Workspaces on Mobile](https://www.mangoapps.com/directory/app/workspace)** — Workspaces now have dedicated mobile pages for the board, hill charts, progress updates, and pi... --- # Staffing a Seasonal, Licensed Field Workforce **Author:** Andy Tolton **Published:** 2026-09-22 **Category:** field-services Crews double in peak and halve after, and every hire needs a credential before dispatch. How connected recruiting, onboarding and records shorten the path. The season starts and the crews double. For the first two weeks, the work is paperwork: forms, credentials, accounts, orientation. Then the season ends, most of those people leave, and next spring it happens again, often with the same people. Field service companies with seasonal demand live inside that cycle. Heating and cooling swing with the weather. Landscaping crews double and halve with the calendar. And in every licensed trade, each of those hires needs a license, a certification or both before they can be dispatched. The thesis of this article is that in a licensed trade the HR record is an operational record, and it should survive the off-season. A record that stays in place is what gets a returning worker back on a truck in days. ## The seasonal hiring problem has three parts **How do field service companies handle seasonal hiring?** The ones that manage it well treat it as three separate problems. **Speed to first dispatch.** How long between an accepted offer and a technician on a real job? Every day of that gap is a day of demand you can't serve at the moment you most want to. **Credential readiness.** A hire isn't dispatchable until the credentials for the work they'll do are in place. If verification depends on someone chasing paperwork, it's the slowest step. **Reactivation.** Many seasonal workers come back. If returning means starting from zero every year, the company pays the same onboarding cost repeatedly for people it already knows. ## Recruiting into the first dispatch The path from job posting to first dispatch should be one path, not four handoffs. That means forecasting seasonal headcount before the surge, syndicating postings to trade boards, and scoring resumes against the certifications the work requires. Connected onboarding then carries the hire from recruiting through first dispatch, using the Talent Acquisition Suite and Training Connect. Predictive demand planning can help with the timing of a seasonal surge. It's a signal to plan against and not a promise: a forecast tells you when to start hiring, and you still have to hire. ## Onboarding on the phone they already carry **How do you onboard technicians quickly?** Take the computer out of the process. The branded app installs on the new hire's own phone, and onboarding is an invite by text message or a QR code. There's no company email to create, no company hardware to issue and no VPN. The onboarding flow is the same as for any technician, which we go into in [why technicians work around the tools](/articles/why-technicians-work-around-field-service-software). From there, training can assign itself. Auto-enrollment by role or location means a new technician's required courses are waiting when they sign in, and mobile delivery works for people who have never had a computer at work. For trades with apprenticeships, training paths run in the learning system from apprentice to journeyman, and a skills inventory connects each person's capabilities to the jobs they can be assigned. Someone who is two courses from a qualification should be visibly two courses away, not a mystery. ## Credentials that reach dispatch The credentials a seasonal hire brings or earns have to reach the board. Certification tracking has expiry alerts. Work types carry the credentials they require, so a technician is assignable when they qualify and not before. We make that argument at length in [why an expired certification should block dispatch automatically](/articles/expired-certification-blocks-dispatch), so we won't repeat it here. For a seasonal workforce, the relevant point is speed: the moment a credential is recorded, the technician is eligible. ## When the season ends This is the part most companies handle worst, and it's the reason to think of seasonal staffing as a platform question. When the season ends, records and certifications stay in place. Returning workers are reactivated and not re-onboarded. Picture a returning landscaping crew lead in March. Their license is already on the record. Their training history is there. The access notes for the sites they worked last year (which gate, which key, which client dislikes the blowers before nine) are still on the site records. Reactivation is a status change, and they're on the schedule. The alternative is a form, a background check, a training refresh for things they already know, and a week of relearning the sites. The fastest seasonal onboarding is the one you don't have to repeat. ## Retaining the ones you trained In a trade with a labor shortage, retention decides whether you can take the work. Gallup's 2019 report, *This Fixable Problem Costs U.S. Businesses $1 Trillion*, puts the cost of replacing an individual employee at anywhere from one-half to two times their annual salary. It's an expensive way to find out someone wasn't happy. Replacing a frontline or hourly worker costs about 40% of their salary (Gallup), and organizations with strong internal communications are 4.5x more likely to have engaged employees (Gallup). **How do you retain skilled technicians?** Give them a reason to stay that's in the tools they use every day. A few things in the same app help: - Peer recognition and career development where the technician already works, so recognition isn't a separate site to remember. - A shift marketplace for technicians who want to pick up extra work, which lets people choose their hours instead of being assigned them. - Engagement risk detection, which analyzes patterns across technician behavior and flags attrition risk before a resignation arrives. It's a signal for a manager to have a conversation. It isn't a scorecard, and it isn't a substitute for the conversation. That last one deserves care. A signal that prompts a manager to check in with someone is useful. A signal treated as a verdict on the person isn't. The purpose of every item in this list is to keep skilled people, and not to measure them. ## The second workforce Many field service companies have a second workforce: warehouse crews, parts runners and office teams working shift schedules with their own compliance needs. On a shared platform, the shift and the route stop being separate problems. A shift opens in the warehouse and a field technician who wants extra hours picks it up. A safety alert reaches the field crews and the shop at once. Coverage flexes across both groups, and it's a way to give people more options rather than fewer. ## What to set up before the season starts The companies that get a smooth peak usually did their work in the quiet months. A short list of what's worth doing before the first hire arrives: - Decide which credentials each work type needs, so verification is a check against a list and not a judgment call made under pressure. - Load the training paths that new hires need first, so they're assigned automatically by role or location the day someone joins. - Confirm that last season's people, records and site notes are still in the system and marked for reactivation, so returning workers start from what's there. - Pick the technicians who will train new hires in the field, and tell them early. A peer who's shown someone how to log a part on their first day does more than a manual. None of it is complicated. It just needs someone to own it before it becomes urgent. [Your first 90 days](/articles/field-service-implementation-first-90-days) covers who decides what when you're setting up the platform itself. ## Why this is a platform question Recruiting, learning and HR systems that each keep their own record can't do any of the above. When HR, learning and recruiting write to the record the dispatch board reads, seasonal staffing stops being a paperwork project. MangoApps puts field service on the same platform as people operations, learning and recruiting, so the record that a hire builds in March is the one the board reads in April and again the following March. [How the pieces fit together](/articles/field-service-implementation-first-90-days) is in the implementation guide, and [whether you have to give up what you already run](/articles/replace-fsm-tool-or-consolidate) is a separate question. ## Getting the pilot right Start with one crew and one service line, and pick the crew for influence. Peer-led rollout applies to seasonal onboarding as much as to the first go-live: the people who trained on the platform last year are the best trainers this year. Seasonal staffing is one of the objections the [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide) answers directly. You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### How fast can a seasonal technician be onboarded? With recruiting, onboarding and training on the phone, a seasonal hire can reach their first job in days. The branded app installs on their own phone, onboarding is an invite by text message or QR code, and required training is assigned automatically by role or location. Credential checks are the step most likely to slow it down, so they're worth setting up before the season starts. ### Do returning seasonal workers need to be re-onboarded? They shouldn't. When the season ends, records and certifications stay in place, so a returning worker is reactivated instead of starting over. Their license, training history and site notes are still on the record when they come back. ### How do you track apprentice progress toward journeyman? Run apprentice-to-journeyman training paths in the learning system, and use a skills inventory to connect each person's capabilities to the jobs they can be assigned. Progress is then visible on the employee record, not in a separate spreadsheet. ### Can technicians pick up extra shifts through the app? Yes. A shift marketplace lets technicians pick up extra work, and it can extend to shop and warehouse shifts so that a field technician can take an open shift in the warehouse. ### How does recruiting connect to dispatch eligibility? Through one record. Resumes are scored against the certifications the work requires, connected onboarding carries a hire from recruiting to first dispatch, and when their credentials are recorded they become eligible for the work that requires them. There's no second entry between recruiting, training and the dispatch board. --- # What Frontline Disengagement Actually Costs: Turnover, Supervisor Time, and Audit Exposure **Author:** Andy Tolton **Published:** 2026-09-22 **Category:** frontline-communication The price of frontline communication gaps is already being paid, just booked in HR, operations, and legal. Added up, the replacement line alone dwarfs what the software costs. *Every gap in frontline communication has a price, and the prices are already being paid. They are recorded in other departments' budgets: turnover in HR, supervisor hours in operations, unverified compliance in legal, duplicate tools in IT. For a 5,000-employee multi-site employer with 4,000 frontline workers, the turnover line alone runs to roughly $20 million a year on conservative assumptions. Communication and engagement are usually evaluated against the cost of the software. They should be evaluated against the cost of the workforce.* A frontline communication platform usually reaches the finance committee as a license line. Somebody asks whether the current tool can be stretched another year, somebody else notes the renewal date, and the meeting moves on. The numbers that would change that conversation are in the building. They just aren't on the same slide. ## Why the cost is invisible The cost of frontline disengagement is invisible because no single budget owns it. The communications team sees its software line. HR sees turnover and the recruiting spend that follows it. Operations sees supervisors who lose part of every shift repeating what headquarters already published. Legal sees exposure, usually after something has gone wrong. Each owner can explain their own number, and nobody is asked to explain the total. That split mirrors the problem itself. Frontline communication fails along [six reach gaps](https://www.mangoapps.com/articles/why-frontline-communication-fails) that open whenever communication infrastructure assumes a desk. Some are about delivery, where the message never arrives because the worker has no inbox and no company device. Others are about what happens afterwards, when nothing comes back from the floor and nobody can prove what landed. Each gap has a price. The prices land wherever the damage shows up, which is almost never the communications budget. Put them on one page and the stake becomes visible. Every input below is shown, so you can swap ours for yours. ## Engagement, and what it is worth Engagement is at its lowest point in years, and the frontline sits at the bottom of it. Global employee engagement fell to 20% in 2025, its lowest level since 2020, and Gallup estimates the cost to the world economy at $10 trillion in lost productivity (Gallup State of the Global Workplace, 2026). In the United States engagement sits at 31%, the lowest in roughly a decade (Gallup State of the Global Workplace, 2026). Break the numbers down by who does the work and the pattern sharpens. Hourly workers in retail and manufacturing sit at the bottom of Mercer's range, tied at 65%, lower than any other group ([Mercer, Inside Employees' Minds, 2025](https://www.mercer.com/en-us/insights/talent-and-transformation/attracting-and-retaining-talent/rebuilding-trust-addressing-the-workforce-crisis-in-retail-and-hospitality/)). The least engaged people in the company are the ones who meet the customer: the associate stocking shelves before open, the nurse handing over a ward at shift change. A customer judges the business by them. They are also the people least likely to have heard what the business decided this week, because nothing it uses to announce decisions was built to reach them. A $10 trillion figure is too large to act on. It becomes useful when it is translated into lines a single employer can find in its own accounts, and the largest of those lines is turnover. ## Turnover, and what it costs to replace someone Turnover is the most expensive consequence of a disengaged frontline, and in most frontline sectors it runs at rates a headquarters function would treat as an emergency. In retail, frontline turnover runs above 60% a year across the sector (McKinsey, 2024). A store with forty associates replaces more than half of them every year, so at any given moment a meaningful share of the floor is new. Healthcare turnover is lower as a rate and far heavier per person. Hospital registered nurse turnover was 18.4%, with an average replacement cost of roughly $56,300 per bedside nurse, which means each single percentage point of RN turnover costs a typical hospital about $262,500 a year (NSI Nursing Solutions Report, 2024). The pipeline of departures isn't shrinking either. Roughly 40% of registered nurses intend to leave within five years (NCSBN, 2024). Hospitality carries the heaviest churn of all. Accommodation and food services have the highest quit rate in federal labor data (BLS JOLTS, 2024), so the audience turns over faster than most communication programs can adapt. Communication does not cause all of that, and a model that claimed it did shouldn't be trusted. The mechanism is still easy to trace. Picture a worker who hears about a change to her own job from a customer, who can't get a routine pay question answered without tracking down a supervisor, and who filled in a survey last spring and never saw anything change. She has fewer reasons to stay each week. Multiply her across a workforce and the result shows up in HR's numbers, where nobody connects it to the channel that failed her. ## Compliance, and what the audit finds Compliance is where communication gaps turn into exposure, and the exposure is real even before it becomes a cost. The clearest evidence is off-channel communication. When the sanctioned channel doesn't reach people, work moves to personal messaging groups the company does not own and cannot produce in an audit. Regulators have levied more than $2.5 billion in combined SEC and CFTC fines for work conducted on unapproved personal messaging channels (SEC and CFTC enforcement actions, 2021 to 2024). That figure exists because communication moved somewhere the company could not govern it. The gap created the exposure. The employees just filled the gap. The quieter version sits inside training and acknowledgment records. Most organizations report a completion rate for mandatory training and policy sign-off. Fewer could evidence those completions person by person if an auditor asked. Where completion is recorded by a supervisor confirming that a briefing took place, rather than by each worker confirming it for themselves, the reported number and the real one drift apart. Every completion inside that gap is unverified. It costs nothing until the day someone tests it, and then it costs whatever the finding costs. So the model below treats compliance as exposure, not as a run-rate expense. A large dollar figure would be easy to invent. **Download *Frontline Worker Communication & Engagement*.** It carries the full cost and return model behind this article, along with the evaluation questions to take into any vendor conversation. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) ## The model for a 5,000-employee employer Here is the cost side of the model for an illustrative 5,000-employee multi-site employer with roughly 4,000 frontline workers. Every input comes from a benchmark cited above or is stated as an assumption you can change. | Cost line | How it is modeled | Annual | |---|---|---| | Frontline turnover | 4,000 frontline employees at 40% annual turnover is 1,600 separations. Replacement cost at roughly one third of an average frontline salary is about $12,500 each. | $20.0M | | Supervisor time spent relaying | 250 frontline supervisors spending three hours a week relaying information and answering routine questions that already have documented answers. That is 150 hours a year each, at a fully loaded $32 an hour. | $1.2M | | Compliance and training exposure | Two mandatory assignments a year across 5,000 employees. A 15-point gap between reported and actual completion leaves roughly 1,500 unverified completions carrying audit exposure. | Exposure, not a cost until it is one | | Duplicate software | Four point solutions covering communication, engagement, recognition, and knowledge, at an average $60,000 annual contract, plus the integration maintenance and security review each one requires. | $240K+ | | Off-channel communication | Work conducted in personal messaging groups the organization cannot search or produce. Not modelable as a run-rate. Regulators have levied more than $2.5 billion in fines since 2021. | Tail risk | Two of those inputs deserve a word. The 40% turnover assumption is deliberately conservative. Retail runs above 60% (McKinsey, 2024), so an employer with a large retail footprint will see a bigger first line, not a smaller one. The supervisor figure is conservative too. It counts only relaying and routine questions with documented answers, the part of [the communication load frontline managers carry](https://www.mangoapps.com/articles/frontline-manager-communication-overload) that a direct channel could take off them. It leaves out the judgment calls, which is the work supervisors are there to do. This is illustrative. It is not a forecast, and it won't tell you what your organization will save. It gives you a structure for calculating what the gaps cost you now, with every assumption visible and replaceable. ## What the model says The model says turnover dominates by an order of magnitude. At $20 million a year, the turnover line is more than sixteen times the supervisor line and more than eighty times the duplicate software. Supervisor hours and tool sprawl are real, and either one would justify attention on its own. Next to turnover they are secondary. That changes the question a finance team should be asking. The usual evaluation compares a new platform's license against the tools it replaces, or against doing nothing. On that basis communication looks like a discretionary software purchase, and discretionary software purchases get deferred. The software line is the wrong denominator. Run the same employer through a three-point reduction in turnover, 40% down to 37%. That is 120 fewer separations at $12,500 each, or $1.5 million a year. The entire cost of the four point tools in the model is $240,000. A modest movement in retention is worth more than six times the software line before a single supervisor hour is counted. None of this proves that a given Employee Platform will move your turnover by three points. It shows what is at stake if one does. The question worth testing is whether reaching every worker directly, with [engagement and listening built for the frontline](https://www.mangoapps.com/solutions/employee-engagement), changes the reasons people leave. The return side of the model, including recovered supervisor time and retired tools, is set out in [the business case for frontline communication](https://www.mangoapps.com/articles/frontline-communication-business-case), with a calculator you can run against your own numbers. ## What you need to run it yourself You need four numbers to run this model for your own organization, and most of them already exist somewhere in the business. 1. Frontline headcount and current annual turnover. HR holds both, usually by site. 2. The number of frontline supervisors, and a realistic estimate of the hours each spends passing information along. Ask the supervisors for the second. 3. Your current per-employee cost across the tools a single platform would replace. 4. The completion rate you currently report on mandatory training, alongside your honest estimate of the real one. The last number is the hardest to produce. It's also the one that tells you the most, because the distance between the reported figure and the honest one is your audit exposure, stated as a count of people. Before you gather any of it, it helps to know which gaps are open in your operation. [The frontline communication audit](https://www.mangoapps.com/articles/frontline-communication-audit) scores each of the six. The audit and the model each take under an hour, and they're useful whether or not you ever talk to a vendor. Once the four numbers sit on one page, the budget conversation shifts. The question stops being whether a communication tool is worth its license. It becomes how much of a $20 million line the organization is prepared to leave where it is. **Download *Frontline Worker Communication & Engagement*** for the full cost and return model. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) Run the return side against your own numbers in [the business case for frontline communication](https://www.mangoapps.com/articles/frontline-communication-business-case), or [see it configured for your sites](https://www.mangoapps.com/schedule-a-call). *The AI Platform for the Frontline Workforce.* ## Frequently asked questions **How much does frontline turnover cost?** Replacing a frontline employee costs roughly one third of their annual salary, which works out to about $12,500 per separation in the illustrative model in this article. In healthcare the figure is much higher. The average replacement cost of a bedside registered nurse is roughly $56,300 (NSI Nursing Solutions Report, 2024). Multiply either figure by a year's separations and turnover quickly becomes the largest cost tied to the frontline. **What does one point of nurse turnover cost a hospital?** Each percentage point of registered nurse turnover costs a typical hospital about $262,500 a year (NSI Nursing Solutions Report, 2024). That follows from an average hospital RN turnover rate of 18.4% and a replacement cost near $56,300 per bedside nurse, both from the same report. With roughly 40% of registered nurses intending to leave within five years (NCSBN, 2024), the exposure is more likely to grow than shrink. **What is the cost of employee disengagement?** Gallup estimates that disengagement costs the world economy $10 trillion in lost productivity (Gallup State of the Global Workplace, 2026). Global engagement fell to 20% in 2025, its lowest level since 2020. For a single employer the most useful translation is turnover, which in a 5,000-employee model with 4,000 frontline workers runs to about $20 million a year. **How much time do supervisors spend on communication?** The illustrative model assumes three hours a week per supervisor spent relaying information and answering routine questions that already have documented answers. Across 250 supervisors at a fully loaded $32 an hour, that comes to about $1.2 million a year. Your figure may differ, but it is time taken from supervising, and it can be measured. **Does poor internal communication increase turnover?** Poor communication contributes to turnover, but it is not the single cause, and no honest model assigns it a precise share. The mechanism is still clear. A worker who hears about changes to her own job from a customer, and never sees her feedback acted on, has fewer reasons to stay. That is why a modest turnover change is the right sensitivity test for a communication investment. **What is the retail employee turnover rate?** Frontline retail turnover runs above 60% a year across the sector (McKinsey, 2024). At that rate a meaningful share of every store's floor is new at any given moment. The cost model in this article deliberately uses 40%, so its result is conservative for a retail employer. **Why should communication be evaluated against workforce cost rather than software cost?** Because the turnover line exceeds the software line by an order of magnitude. In the illustrative model, turnover costs $20 million a year and four point tools cost $240,000. A three-point reduction in turnover is worth $1.5 million, more than six times the entire software line, so judging the decision on license cost alone misses most of what is at stake. **How do you build a business case for an employee communication platform?** Start with the cost side, which is the model in this article, then add the return side. The return side models reduced turnover, recovered supervisor time, verified compliance, and retired software, and it is set out with a calculator in [the business case for frontline communication](https://www.mangoapps.com/articles/frontline-communication-business-case). Build both from your own headcount, turnover, and tool spend rather than benchmarks wherever you can. --- # Frontline Platform Adoption: Why the Category Averages 30 to 40 Percent and What the First 90 Days Have to Do **Author:** Andy Tolton **Published:** 2026-09-22 **Category:** employee-app Every acknowledgment rate and sentiment score is a fraction with adoption underneath it. What moves that number is what lives in the app, who gets enabled first, and how the rollout is run. *Most frontline platform deployments don't fail because the product couldn't do the job. They fail because the workforce didn't open it, and MangoApps puts typical category adoption at 30% to 40%. That matters more than it sounds. Acknowledgment tracking on a third of the workforce measures a subset and calls it the company, and sentiment from a self-selected minority looks like data while being worse than none. Reaching 90% depends on what lives in the app, who is enabled first, and what the first 90 days are designed to prove.* A safety notice goes out on a Monday with acknowledgment required. By Friday the dashboard reads 90% acknowledged, green at every site, and the compliance lead reports it upward. What the dashboard doesn't say is that 35% of the workforce has the app. Roughly a third of the company confirmed the notice. Nobody in that meeting knows it. ## The number that decides whether anything else in the platform is true Adoption is the denominator under every other number a communication platform reports. Reach, acknowledgment, sentiment, training completion: each one is a fraction of the people who opened the app, presented as if it were a fraction of the workforce. When adoption is high the two are close enough not to matter. When it isn't, every report is quietly describing a different company. The acknowledgment example above is simple arithmetic. Sentiment is worse. The people who answer a pulse survey in a low-adoption deployment are the people engaged enough to have installed the app and opened it this week, which is exactly the group least likely to be at risk. Their answers look like a reading of the workforce. They are a reading of its most connected minority, and a confident number built on them is worse than no number, because it looks like data and gets acted on. This is the difference between [sending a message and reaching the people it was for](https://www.mangoapps.com/articles/why-frontline-communication-fails), expressed as a single percentage. > Reach has to be real before anything built on it can be trusted. ## Why 30% to 40% is normal Most deployments land around a third because they give a frontline worker no reason to open the app and several reasons not to. Across the deployments MangoApps sees replaced, adoption for this category typically lands between 30% and 40%. The causes are rarely about the product's features. They're about four decisions made before launch. The app carries only corporate news. A leadership update is not a reason to open anything on a ten-minute break, so opens peak in launch week and decline from there. Sign-in requires a corporate identity much of the frontline was never issued. If getting in means a company email address or a VPN, the people without those are excluded by default, and they are usually the majority of the people the platform was bought to reach. Launch is treated as a communications event rather than an operational change. There's an announcement and a flyer in the break room, and nothing about how the shift runs is different afterwards. Supervisors weren't enabled. The floor takes its cue from the person running the shift, and if that person still reads the pre-shift update off a sheet of paper, the team learns the app is optional. Then there's the objection every rollout team hears: our frontline won't want another app. They won't, and it's the right instinct. Another app that duplicates something they already use loses. An app that consolidates what they already need wins. ## What actually drives adoption People open an app when something they need is already in it, and everything else in this section follows from that. ### Something the worker needs already lives there The schedule is the single most reliable reason a frontline employee opens an app. Pay stubs, time-off balances, and answers to routine questions come next. News rides along with them. An associate checking whether her Saturday swap was approved sees the safety notice on the way, which is a far better delivery mechanism than hoping she remembers to look for it. ### Consolidation as an adoption strategy Every additional app means another login and another interface, and for a worker with three minutes between tasks, each one is a reason to give up. Consolidation is usually pitched as an IT saving. On a frontline it's an adoption decision first, because every point solution you retire is one fewer place a worker has to remember to check. An Employee Platform that carries the schedule, the pay stub, and the news in one app gives a worker one place to check instead of four. ### No corporate identity required Access has to work with no password to manage and no corporate email address, on a personal phone or a shared device, provisioned in minutes. That is the first item in [what a frontline employee app actually requires](https://www.mangoapps.com/articles/frontline-employee-app-requirements), and it is first for a reason. SSO, MFA, and SCIM should be supported where they already exist and required nowhere. ### The app is theirs A [branded employee app](https://www.mangoapps.com/solutions/employee-app) is listed in both app stores under the company's own name, with its logo and colors, so it reads as the company's app rather than software the company bought. Santee Cooper, the South Carolina public utility, took that a step further. Its employees named the app themselves, through a naming contest, and called it The Coop. People are far more willing to open something they had a hand in naming. ### Managers first Supervisors decide adoption on the floor regardless of what the launch plan says. If a supervisor checks who hasn't opened a Must Read and spends two minutes with those four people, the team learns the app matters. If she doesn't, the team learns that too. Enabling managers first is not a courtesy. It's the part of the rollout that determines whether the rest of it lands, and it is also the fastest way to take relaying work off a role that is [already carrying too much communication](https://www.mangoapps.com/articles/frontline-manager-communication-overload). ## Proof it can be done at scale Adoption at 90% is not a theory, and it isn't limited to one kind of workforce. Four organizations with very different frontlines show what it looks like. The Kansas City Chiefs reached 90% adoption of their branded app, Huddle, among more than 600 game-day event staff, up from a 40% average adoption rate organization-wide. This is a seasonal, part-time workforce that turns over with the season, which is about as hard an audience as a rollout can have. OU Health, an academic health system, had 87% of its 10,000-plus person workforce engaged on the platform within a few months of launch. Clinicians on shift don't open a corporate inbox, so an inbox-based channel was never going to reach them. Columbia Basin Health Association, a community health organization, set itself a goal of 75% engagement within two years. It now runs above 90% monthly employee engagement. A major windows and doors manufacturer has a 14,000-person workforce that is two-thirds frontline. Four years ago most of those employees had no email access. More than 90% now actively engage, through audience segmentation, multilingual access, local champions at each site, and an app designed for the phone and connected to their HR systems. Across its customers, MangoApps averages more than 90% adoption within 90 days, against the 30% to 40% range typical for the category, and it puts that commitment in writing as an Adoption Guarantee. Whoever you're evaluating, ask the same question. Will they put an adoption number in the contract? **Download *Frontline Worker Communication & Engagement*.** It lays out the full implementation plan, the 90-day markers, and the requirements list to take into any evaluation. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) ## What the first 90 days have to do The first 90 days have to put the platform in front of every worker and prove it's being used, without anything the business depends on stopping. Two questions get asked before any signature, and both are fair. How long until this is live, and what breaks while we switch? The honest answers are short. Typical implementation runs 8 to 12 weeks, with a dedicated cross-functional team and a named Customer Success Manager from day one. Nothing switches at once. Existing systems keep running while the platform comes online underneath them, and the HR and payroll systems stay the source of truth for the employee record. The work falls into four phases. ### Align and plan Kickoff and planning lock the use cases that matter: coverage targets, compliance rules, the systems in place today, and what a successful launch looks like. A named CSM and a technical account manager are on from day one. What this phase locks is the definition of success, written down before anyone is attached to a particular launch date. ### Build and connect Branding and the app store listing come first, then identity and provisioning through SSO and SCIM where they exist, and integration into the HR, workforce management, and payroll systems that hold the employee record. Content migration runs in parallel. It is the right moment to retire content rather than move it, because every stale page carried across is a stale page the new platform then has to govern. ### Pilot The pilot runs in one region, a single division, or a defined set of sites. It exists to find the difference between the audience model on paper and the audience model in practice, and there is always a difference. The HR record might say a distribution center has one night-shift supervisor, while the floor knows two leads split the shift between them. Finding that before a company-wide launch is much cheaper than finding it after. ### Launch and expand Company-wide rollout starts with manager enablement, for the reasons above. Additional capability areas turn on afterwards as configuration, without a second implementation, which is what it means for the platform to [cover the work rather than one slice of it](https://www.mangoapps.com/articles/seven-things-one-work-platform). ## Three markers at day 90 By day 90, three things should be true, and each one can be checked. The first targeted campaign has run with measured reach. That gives the organization a real baseline for the first time, instead of an estimate everyone quietly knows is generous. Adoption is at 90% or higher. It gets there because the platform lives in an app employees have a reason to open on every shift, not because anyone was persuaded. The first listening cycle has produced a visible action, communicated back to the people who raised the issue. This is the marker most organizations skip, and it's the one that decides whether employees bother answering the next survey. It is also the subject of [frontline listening that closes the loop](https://www.mangoapps.com/articles/frontline-listening-close-the-loop). The order is deliberate. Reach comes first, because nothing can be measured until it works. Then the loop, then the proof. ## Where to start if you cannot start everywhere Start with the capability area that closes your widest gap, because nothing downstream requires starting everywhere. If you have scored your operation with the [frontline communication audit](https://www.mangoapps.com/articles/frontline-communication-audit), the gap with the most open answers tells you which row you're in. | If this is true today | Start with | |---|---| | A meaningful share of the workforce cannot be reached directly | The Front Door | | Delivery broadly works, but you can't target precisely, escalate a critical message, or prove what landed | Communications | | You have reach and no return path, and engagement is discussed with no data underneath it | Engagement and Listening | | Supervisors are acting as the help desk for questions with documented answers | Knowledge and Answers | | The immediate risk is content nobody owns, or work happening in channels you can't produce in an audit | Governance, Security, and Proof | The Front Door is the most common starting point, and the one that is a prerequisite for the others. That's the adoption argument in one line. Every area after it is measured against the people who opened the app, so a rollout that skips the reach problem ends up reporting precise numbers about a workforce that isn't there. **Download *Frontline Worker Communication & Engagement*** for the implementation plan and the 90-day markers in full. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) Take [the vendor questions on adoption commitment](https://www.mangoapps.com/articles/evaluate-frontline-communication-vendors) into your next evaluation, or [see it configured for your sites](https://www.mangoapps.com/schedule-a-call). *The AI Platform for the Frontline Workforce.* ## Frequently asked questions **What is a good adoption rate for an employee app?** More than 90% within 90 days is achievable, against a category average of 30% to 40%. The difference comes from what lives in the app, whether workers can get in without a corporate identity, and whether supervisors were enabled first. MangoApps customers average more than 90% within 90 days. Anything much below that means acknowledgment and sentiment reports are describing a subset of the workforce. **Why do frontline communication platforms fail?** They usually fail on adoption, not capability. Four causes recur. The app carries only corporate news, sign-in requires a corporate email address much of the frontline doesn't have, the launch is a communications event rather than an operational change, and supervisors were never enabled. Each one gives workers a reason to leave the app closed. **How do you get frontline employees to use a company app?** Put what they already need in it, remove the identity barrier, brand it as theirs, and enable managers first. The schedule is the most reliable reason to open an app, followed by pay stubs, time-off balances, and answers to routine questions. Access should work with no password and no corporate email. Supervisors who use it visibly set the norm for their teams. **How long does it take to implement an employee communication platform?** Typical implementation runs 8 to 12 weeks. That assumes a dedicated cross-functional team and a named Customer Success Manager from day one, working through four phases: align and plan, build and connect, pilot, then launch and expand. Existing systems keep running throughout, so nothing has to switch over at once. **Do we have to replace our HR or workforce management system?** No. Those systems stay the source of truth for the employee record and feed it into the platform through integration. Nothing gets ripped out, and the investment is kept. What they don't do is reach a worker with no inbox and prove the message landed, which is a different job. **Should you pilot an employee app before company-wide launch?** Yes, because the pilot is where the audience model meets reality. Run it in one region or a handful of sites. The org chart and the floor rarely agree on who reports to whom or which sites share a manager. Finding those differences in a pilot costs far less than finding them after a company-wide launch. **What should happen in the first 90 days of an employee app rollout?** Three markers should be met by day 90. The first targeted campaign has run with measured reach, adoption is at 90% or higher, and the first listening cycle has produced a visible action communicated back to the people who raised it. The order matters, because nothing can be measured until reach works. **Should an adoption guarantee be in the contract?** Ask every vendor whether they will put an adoption number in the contract. A vendor confident in its adoption should be willing to commit to one. MangoApps puts its commitment in writing as an Adoption Guarantee, backed by an average of more than 90% adoption within 90 days. **Why is adoption the precondition for communication metrics?** Because every communication metric is a fraction with adoption in the denominator. At 35% adoption, a 90% acknowledgment rate means about a third of the workforce confirmed the notice. Sentiment drawn from a self-selected minority is worse than no data, because it looks like data. Until adoption is high, every other number describes a different company than the one you run. --- # What a Frontline Employee App Actually Requires: 10 Non-Negotiables **Author:** Andy Tolton **Published:** 2026-09-21 **Category:** employee-app Write the list before the demo. The order in which a vendor can satisfy these requirements shows whether its product was built for desks or for the floor. *Ten requirements follow from the six ways frontline communication fails: reach without corporate identity, phone-first and device-agnostic design, offline access, translation at publish, targeting by site, role, shift, and language, delegated local publishing, a built-in return path, answers alongside the work of the shift, message-level acknowledgment, and a governed channel workers prefer. Write them down before any demo. A desk-built product usually satisfies five. A frontline-built product starts with the first four, because nothing else matters until delivery works.* The demo always goes well. The feed looks clean, the composer is quick, and the analytics dashboard fills with tidy charts drawn from a sample tenant where every employee has a company email address and a laptop. Nobody in the room asks what happens to the stock associate hired on Tuesday, who has neither. That question is the evaluation. Everything else is presentation. ## Why requirements come before demos Requirements come first because a demo shows features and requirements test architecture. If frontline communication fails because [sending is not reaching](https://www.mangoapps.com/articles/why-frontline-communication-fails), then a better feature set on the same channel changes nothing, and the evaluation has to be about infrastructure. Hold onto one rule through every vendor meeting. The order in which a vendor can satisfy the ten requirements below tells you what the product was originally built for. Here they are, written as a buyer's list rather than a feature list. | # | Requirement | Why it is non-negotiable | Gap it closes | |---|---|---|---| | 1 | Reach without corporate identity | A worker with no company email must be provisioned and reachable in minutes, not excluded by default. | Gap 1, delivery | | 2 | Phone-first and device-agnostic | Personal phones, shared devices, kiosks, and screens on the floor. A responsive website is not the same capability. | Gap 1, delivery | | 3 | Offline capability | Plant floors, cold storage, basements, vehicles, remote sites. Content has to be readable without a live connection. | Gap 1, delivery | | 4 | Translation at the moment of publishing | Mixed-language crews share one shift. Translation as a separate project arrives late and drifts from the original. | Gap 1, delivery | | 5 | Targeting by site, role, shift, and language | Reaching the right subset directly takes load off the supervisor instead of adding to it. | Gap 2, the manager | | 6 | Delegated local publishing | Local leaders publish what is true at their site, inside guardrails set centrally. | Gap 2, the manager | | 7 | A return path built in | Surveys, pulses, and anonymous feedback on the same audience model, not a separate tool. | Gap 3, the return path | | 8 | Answers and the work of the shift together | Policy, pay, schedule, training, and tasks in one place, or the question goes to the supervisor. | Gap 4, answers | | 9 | Acknowledgment at the message level | Must-read tracking, confirmation, and escalation. Sent is not received. | Gap 5, proof | | 10 | A governed channel workers prefer | Governance only works if the sanctioned channel beats the group chat it competes with. | Gap 6, governance | ## 1. Reach without corporate identity A worker with no company email address has to be provisioned and reachable within minutes of being hired, not excluded by default. Every other requirement depends on this one. In practice, a new hire gets in with no password and no corporate email, and without a laptop or a VPN. Single sign-on, multifactor authentication, and SCIM provisioning are supported where they already exist and required nowhere. Provisioning follows from one employee record, so site, role, shift, language, and audience membership arrive together instead of being set up by hand in four places. The app should be published under your name in both app stores, with your branding on the login screen and every notification. That sounds cosmetic. It isn't, because an app carrying the company's name reads as the company's app rather than software the company bought. Santee Cooper, a public electric and water utility in South Carolina with more than 1,600 employees, ran a naming contest, and its employees called theirs The Coop. > "People in the field can sometimes be disconnected with what's happening corporate-wide. That's just a natural result when your jobsite is a turbine floor or a bucket truck. That means a lot of our folks have limited access to a computer. The Coop gives us a way to close that gap." > > Jeffrey Straight, Public Relations Specialist, Santee Cooper Most of this workforce will use a personal phone, so look for an app-level PIN, remote wipe, and containerized company data. Where phones are impractical, kiosk mode on a shared device covers the rest. Why is this non-negotiable? Retail frontline turnover runs above 60% a year (McKinsey, 2024). At that rate provisioning isn't an edge case IT handles once a quarter. It's a weekly operation. A.S. Watson's Kruidvat stores show what happens when it works: most store staff have no company email, employees onboarded themselves with no training materials needed, and active user adoption passed 80% across more than 16,000 Kruidvat employees. In the demo, ask the vendor to provision a fictional new hire with no email address and show what that person sees on a phone. Give them five minutes. ## 2. Phone-first and device-agnostic The app has to reach workers on whatever device is actually in front of them, whether that is a personal phone, a shared handheld at the station, a kiosk, or a screen on the floor. A responsive website is not the same capability. It is a desk experience rendered on a smaller screen, still reached through a sign-in built for a desk identity, which is why [a mobile intranet and a frontline employee app](https://www.mangoapps.com/articles/mobile-intranet-vs-frontline-employee-app) are different products even when they look alike on a phone. Screens matter more than buyers expect. Some workers will never open an app mid-shift, and some environments make a phone unsafe. A break-room display carrying the same post as the app reaches those people without anyone rebuilding the content. In the demo, ask to see one message, published once, on a personal phone, a shared device, and a break-room screen. ## 3. Offline capability Content has to be readable without a live connection, because much of frontline work happens where there isn't one. Plant floors, cold storage, basements, delivery vehicles, and remote sites all break any feature that assumes a signal. The test is practical. A safety data sheet that needs a desktop, or a live connection, is not available to the person standing next to the chemical. A field technician in a van at a customer site has no break room and no supervisor three aisles away. If the procedure won't open where they are, there is no second channel behind it. In the demo, put the phone in airplane mode and ask to open the current procedure and the last must-read post. ## 4. Translation at the moment of publishing Every language version of a message has to exist the moment the message goes out, because a single shift often runs in three or four languages and a translation project always arrives late. Delay is only half the problem. Someone fixes a date in the English post, the Spanish copy made as a separate job keeps the old one, and three weeks later half the crew is working from a version nobody meant to publish. The requirement is that translation happens to the content itself, at publish, rather than to a copy of it. Correct the original and every language corrects with it. The translation should also cover the whole platform, not just the posts. A worker who reads Spanish, Portuguese, Tagalog, or Polish should get the app in that language rather than an English shell around translated messages. MangoApps translates at publish in more than 100 languages. Machine translation needs guardrails. Safety language, internal terminology, and brand terms often must not be machine translated, so look for overrides that hold those phrases fixed, plus regional defaults so each site starts in the languages its crews actually work in. A major windows and doors manufacturer is a useful reference point. Two-thirds of its 14,000-person workforce is on the frontline, and four years ago most of those employees had no email access. More than 90% now actively engage, reached through audience segmentation, multilingual access, local champions at each site, and a design built around the phone and connected to its HR systems. Language was one of four levers, not a finishing touch. In the demo, ask the vendor to publish a post in English, correct one word, and show the correction in three languages without anyone republishing. ## 5. Targeting by site, role, shift, and language Precise targeting is what takes load off the supervisor rather than adding to it. When a message can only go to everyone, the supervisor becomes the filter, deciding what applies to their team and relaying it in person. When it can go straight to second-shift pickers at two warehouses who work in Spanish, the supervisor has nothing to filter or repeat. What separates real targeting from a list tool is where the audiences come from. They should be built from employee attributes, not static lists, so a campaign for second-shift warehouse staff stays correct as people join and leave. A static list is accurate on the day someone builds it and wrong by the next payroll run. In the demo, ask for an audience built from site, shift, and language, then add a matching new hire and show that they join it automatically. ## 6. Delegated local publishing Local leaders must be able to publish what is true at their site, inside guardrails set centrally. Buyers miss this requirement more than any other, because it looks like an administrative detail. It's the difference between a channel that carries relevant content and one that carries only corporate content, and workers can tell which one they're looking at within a week. A screen showing only headquarters content stops being read. In practice, departmental and site owners publish and maintain their own sites and content within a structure the central team sets. Regional and site administrators are scoped to what they own, so a distribution center manages its own audiences and posts without holding the keys to the whole platform. Behind this sits an ownership question most evaluations skip. The function that owns employee communication is almost never the function that owns IT. If every audience change, new site, or template needs a ticket and a sprint, the platform stops reflecting the organization within a quarter, and the workarounds start. Audiences, templates, sites, branding, approval routing, and permissions should all be configurable without code or a developer, from one admin surface. Adoption and usage should also be reported by site, so a location that is drifting away shows up while someone can still do something about it. In the demo, ask a site administrator, not the vendor's central admin, to create a local audience and publish to it without help. **Download *Frontline Worker Communication & Engagement*.** It sets these ten requirements against the six reach gaps they come from, with the capability detail behind each one. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) ## 7. A return path built in Surveys, pulses, and anonymous feedback have to be first-class capabilities on the same audience model as communication, not a separate tool. The reason is the follow-up. The group you surveyed should be the group you close the loop with, defined once. Closing the loop is the strongest single influence on whether anyone answers the next survey, and it is nearly impossible when the survey tool and the communication tool each keep their own audience definitions. Anonymity has to be structural as well, enforced by minimum response thresholds before site or team results appear. A sixty-second check-in at shift end only produces honest answers if the person giving them believes the promise. In the demo, ask to survey one site, then send the follow-up to exactly the people who were asked, with no export in between. ## 8. Answers and the work of the shift together Policy, pay, schedule, training, and tasks need to live in one place, or every question goes to the supervisor by default. A worker with a two-minute question and nowhere obvious to ask will ask the person already running the floor. The schedule deserves a closer look. It is the single most reliable reason a frontline employee opens an app, which makes it the strongest adoption driver for everything else in that app. A news feed people have to remember to check competes for attention. A feed beside next week's shifts doesn't have to. This is also where AI either works or doesn't. An assistant can only answer from content that is current, governed, and held in one place. Take an employee who wants to know how holiday pay works for a shift that crosses midnight. The right answer comes from the actual policy document, scoped to that person's site and employment type, with the source attached. Whether that answer is possible gets decided by the platform underneath, long before anyone picks a model. In the demo, ask a pay question in plain language from a frontline account and check that the answer cites the policy it came from. ## 9. Acknowledgment at the message level Critical messages need must-read tracking and confirmation from each employee, with automatic escalation for anyone who has not responded. Sent is not received, and received is not understood. Publishing metrics tell you a post went out. They cannot tell you whether the night-shift nurse saw the protocol change before the next patient. The architectural test is where the confirmation lands. Acknowledgment should be written to the same employee record the compliance view reads from, with no export and no reconciliation window during which the two disagree. That is what turns [acknowledgment tracking](https://www.mangoapps.com/articles/employee-acknowledgment-tracking) into evidence rather than a report someone assembles after the fact. In healthcare, documented acknowledgment is not a reporting nicety. It is the audit. In the demo, ask the vendor to name the sites below target on a recent critical message, then show the automatic re-send to everyone who has not viewed it. ## 10. A governed channel workers prefer Governance only works if the sanctioned channel is better than the group chat it competes with. Policy doesn't achieve it. Making the governed channel the one people would choose anyway does, and that is the requirement no feature list states plainly. Workers are not waiting for permission. When the company channel doesn't reach them, coordination moves to personal messaging groups the company does not own and cannot produce in an audit. Combined SEC and CFTC fines for work conducted on unapproved personal messaging channels passed $2.5 billion (SEC and CFTC enforcement actions, 2021 to 2024). The gap created that exposure, not the employees. So the governed channel has to do what the personal group already does well, including group rooms for a site or shift team and voice notes for when hands are busy. Retention and eDiscovery then apply to conversations people were going to have anyway. In the demo, ask to see a shift team's group chat, then the retention and eDiscovery settings that govern it. ## How the ten sort vendors A product built for desk workers can usually satisfy five of the ten. Typically those are targeting, the return path, and acknowledgment, with partial credit on devices and on governance. A product built for the frontline starts with requirements 1 through 4, because nothing downstream is measurable until delivery works. Acknowledgment data is meaningless if a third of the workforce never opened the app. The split is architectural. A platform designed as one system shares a data model. A platform assembled from acquisitions and integrations shares a login screen. On a demo they can look identical, but under load they behave nothing alike. Five tests show the difference: - Acknowledgment becomes a record, not a report. - A survey and its follow-up share one audience, defined once. - A new hire is provisioned once, from one record. - A translated message is the same message, so a correction reaches every language. - Governance and AI read from the same library, so the engine that flags a stale policy page and the assistant answering questions about that policy look at one source. Each of those is a sentence about architecture, and each shows up as something an employee can or cannot do on a Tuesday. That is why [the platform decision comes first](https://www.mangoapps.com/articles/what-platform-means). ## Where to start Start with the capability area that closes your widest gap. The five areas build on each other because they share one data layer, so nobody has to start everywhere. | Capability area | Gaps it closes | Start here if | |---|---|---| | The Front Door | Gaps 1 and 4 | A meaningful share of your workforce cannot be reached directly today | | Communications | Gaps 1, 2, and 5 | Delivery broadly works, but you cannot target precisely, escalate a critical message, or prove what landed | | Engagement and Listening | Gap 3 | You have reach and no return path | | Knowledge and Answers | Gap 4 | Supervisors are acting as the help desk for questions that have documented answers | | Governance, Security, and Proof | Gaps 5 and 6 | The immediate risk is content nobody owns, or work happening in channels you cannot produce in an audit | The Front Door is the most common starting point, and every other area depends on it. Bring your score from the six-gap audit, because the widest gap on your own scorecard is a better guide than any vendor's preferred sequence. A [frontline employee app](https://www.mangoapps.com/solutions/employee-app) that passes the first four requirements gives every later capability a whole workforce to measure, instead of the subset that happens to have a laptop. Take the ten requirements into the [vendor evaluation scorecard](https://www.mangoapps.com/articles/evaluate-frontline-communication-vendors) and score every vendor on your shortlist, including us. [Download the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) for the detail behind each requirement, or [see it configured for your sites](https://www.mangoapps.com/schedule-a-call). *The AI Platform for the Frontline Workforce.* ## Frequently asked questions **What features does a frontline employee app need?** A frontline employee app needs ten capabilities: reach without corporate identity, support for any device, offline access, translation at publish, precise targeting, delegated local publishing, a built-in return path, answers alongside the work of the shift, message-level acknowledgment, and a governed channel workers prefer. The first four decide whether a message arrives at all. The other six decide what happens after it does. **How do employees sign in to a company app without a corporate email address?** They are provisioned from the employee record, so a new hire gets in with no password and no corporate email. Site, role, shift, language, and audience membership follow from that one record. Single sign-on, multifactor authentication, and SCIM are supported where an organization already runs them, but none of them is required for a worker to be reached. **Does a frontline app need to work offline?** Yes, because a large share of frontline work happens where there is no reliable connection. Plant floors, cold storage, basements, delivery vehicles, and remote sites all qualify. Procedures and safety data have to open without a live signal, or they are not available when they are needed. **Why does translation need to happen at publish rather than afterwards?** Translation done afterwards arrives late and drifts from the original. When translation happens to the content itself at publish, every language exists the moment the message goes out, and a correction to the original reaches every version. Overrides keep safety language and brand terms fixed where machine translation is not appropriate. **What is delegated local publishing?** Delegated local publishing lets site and departmental leaders publish and maintain their own content inside a structure set centrally. It is the requirement buyers miss most often because it looks administrative. Without it, the channel carries only corporate content, and local teams stop reading it. **Who should administer an employee communication platform?** Communications and HR should run it day to day, while IT owns the identity perimeter. Audiences, templates, sites, and approval routing need to be configurable without a developer, or every change becomes a ticket. IT keeps control of sign-on and security policy. **Is a personal phone secure enough for company communication?** It can be, provided company content is protected separately from the rest of the phone. An app-level PIN and containerized company data keep content inside the app, and remote wipe means it does not leave with an employee who leaves. Kiosk mode on a shared device covers roles where a personal phone is impractical. **How is a frontline employee app different from a mobile intranet?** A mobile intranet is a desk experience rendered on a smaller screen, still reached through a sign-in built for a desk identity. A frontline employee app is designed first for the worker with no company email and a few minutes between tasks. The [comparison of the two](https://www.mangoapps.com/articles/mobile-intranet-vs-frontline-employee-app) walks through where each one fits. **What should I ask a vendor to demonstrate?** Ask for things that test architecture rather than features. Have the vendor provision a new hire with no email in under five minutes, then open content in airplane mode and correct a published word in three languages. Next, have a site administrator publish locally without central help, and ask for the sites below target on a recent critical message. --- # The Business Case for Frontline Communication: A Model You Can Run With Your Own Numbers **Author:** Andy Tolton **Published:** 2026-09-21 **Category:** frontline-communication Judge communication against the cost of the workforce, not the price of the software. A worked return model for a 5,000-person employer, with every assumption stated and editable. *Communication and engagement are usually judged against the cost of the software. They should be judged against the cost of the workforce. For a 5,000-employee multi-site employer with 4,000 frontline workers, a three-point cut in turnover returns about $1.5 million a year. Handling a third of relayed communication through direct delivery and self-service returns roughly $400,000 in supervisor time, and retiring four point solutions returns $240,000 or more. Every input is a cited benchmark or a changeable assumption. It is a structure for calculating results, not a forecast.* In most budget reviews, frontline communication is compared with the price of the software. A per-seat quote sits next to a renewal date, and the question in the room is whether the line can be trimmed. That comparison makes the function look small, because the number on the other side of the scale is small. Put the cost of the workforce there instead and the conversation changes. The six reach gaps described in [why frontline communication fails](https://www.mangoapps.com/articles/why-frontline-communication-fails) each carry a price, and those prices are already being paid. They just sit in other departments' budgets, where nobody adds them up. This model adds them up. It uses an illustrative employer with 5,000 employees across many sites, 4,000 of them on the frontline, and every figure is either a published benchmark or an assumption you can replace with your own. ## What the gaps cost, in one table On the cost side, one line outweighs the others by an order of magnitude, and it is turnover. The reasoning behind each line is set out in [what frontline disengagement actually costs](https://www.mangoapps.com/articles/cost-of-frontline-disengagement). Here is the summary the return model starts from. | Cost line | How it is modeled | Annual | |---|---|---| | Frontline turnover | 4,000 frontline employees at 40% annual turnover is 1,600 separations, at about $12,500 each to replace | $20.0M | | Supervisor time spent relaying | 250 frontline supervisors spending three hours a week relaying information and answering routine questions, 150 hours a year each, at a fully loaded $32 an hour | $1.2M | | Compliance and training exposure | Two mandatory assignments a year across 5,000 employees, with a 15-point gap between reported and actual completion, leaves about 1,500 unverified completions | Exposure, not a cost until it becomes one | | Duplicate software | Four point solutions for communication, engagement, recognition, and knowledge, at an average $60,000 contract each, plus the integration and security review each requires | $240K+ | | Off-channel communication | Work conducted in personal messaging groups the company cannot search or produce, with more than $2.5 billion in SEC and CFTC fines since 2021 (SEC and CFTC enforcement actions, 2021 to 2024) | Tail risk | The turnover line is roughly eighty times the software line. That ratio is the whole argument for judging communication against the workforce rather than the tool. ## What closing the gaps returns Close the gaps and the same numbers run the other way, on the same model and the same conservative assumptions. | Return | How it is modeled | Annual | |---|---|---| | Reduced turnover | Three points off frontline turnover, 40% down to 37%, is 120 fewer separations at $12,500 each | $1.5M | | Recovered supervisor time | One third of relayed communication and routine questions handled by direct delivery and self-service, about 12,500 hours | $400K | | Verified compliance | Acknowledgment and completion measured rather than reported, so the 15-point gap closes | Exposure removed | | Retired software | Four point solutions retired, with their integrations and security reviews | $240K+ | | Governed channels | Work returns to a channel that can be searched, retained, and produced | Tail risk removed | ### Reduced turnover A three-point reduction in turnover is worth about $1.5 million a year. At 4,000 frontline employees, each point is 40 separations, and three points is 120 people who did not have to be recruited and brought up to speed at $12,500 apiece. Three points is modest against what customers report after closing the delivery and listening gaps. The model doesn't borrow a customer figure, because it doesn't need one. The mechanism is plain enough. A new hire who can get answers in week two without hunting for a supervisor is more likely to reach week ten, and a worker who sees something change after they spoke up has one less reason to leave. ### Recovered supervisor time Handling a third of relayed communication through direct delivery and self-service returns roughly 12,500 supervisor hours, worth about $400,000. The arithmetic is 250 supervisors at 150 hours each, 37,500 hours in total, with a third of it taken off their plate. Picture the pre-shift briefing. When a policy change arrives on every phone the night before, marked Must Read, the supervisor can see who has opened it and spend two minutes with the four people who haven't, instead of thirty minutes briefing everyone. When the holiday-pay question gets answered from the actual policy in the app, it never reaches the supervisor at all. Those hours go back to supervising. They are the coaching and the floor time that the relay work was crowding out. ### Verified compliance Verified compliance removes exposure rather than adding a dollar line. Two mandatory assignments across 5,000 employees is 10,000 completions a year. A 15-point gap between what gets reported and what actually happened leaves about 1,500 completions nobody can stand behind. When acknowledgment and completion are measured at the message level and written to the same employee record the compliance view reads from, that gap closes and the exposure turns into evidence. The value is avoided cost, and it is realized only when someone tests it, in an audit or after an incident. ### Retired software Retiring four point solutions returns $240,000 or more a year, before counting the integrations and security reviews that go with them. Most MangoApps customers retire four to five point solutions within their first eighteen months. The model assumes four, at an average $60,000 contract each. The "or more" is the maintenance nobody invoices separately, such as the connector that breaks when the HR system upgrades and the security review each vendor needs every year. ### Governed channels Governed channels remove a tail risk the model can't price as a run-rate. When the sanctioned channel reaches everyone and is better than the personal group chat, coordination moves back to a place the company can search, retain, and produce. Any employer can be asked for a record of what its people said, and a governed channel is how that request gets answered. ## Why the assumptions are conservative, and where they could be wrong Most of the assumptions lean low, and two conditions could still make the model overstate the return. Start with the ones that lean low. The 40% turnover baseline sits well under retail, where frontline turnover runs above 60% a year (McKinsey retail frontline research, 2024). Hospitality is harder still, since accommodation and food services carry the highest quit rate in federal labor data (BLS JOLTS, 2024). Handling one third of relayed communication directly is a floor. It assumes two-thirds of the relay work survives a channel that reaches every worker. Replacement cost is the biggest lever. The model uses $12,500, about one third of an average frontline salary. Specialized roles cost far more. Hospital registered nurse turnover was 18.4%, and replacing a single bedside nurse costs roughly $56,300, so each point of RN turnover costs a typical hospital about $262,500 a year (NSI Nursing Solutions Report, 2024). A health system that runs this model with its own clinical replacement costs will find the turnover line several times larger. Now the two ways it could be wrong. The first is adoption. Every line in the return table assumes workers actually use the platform. If a third of the workforce never opens the app, acknowledgment data describes a subset and the turnover line barely moves. Adoption is the precondition for every other number here, which is why [frontline platform adoption](https://www.mangoapps.com/articles/frontline-employee-app-adoption) deserves its own scrutiny before any business case is signed. MangoApps averages more than 90% adoption within 90 days, and that is the number to ask any vendor to commit to. The second is consolidation that doesn't happen. If the new platform is added on top of the existing tools instead of retiring four of them, the software line turns negative. The case then rests on turnover and supervisor time, and the model should say so. **Download *Frontline Worker Communication & Engagement*.** The book sets out the full cost and return model alongside the six reach gaps behind each line, so you can see where every assumption comes from. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) ## The consolidation arithmetic Every capability turned on in one platform is one fewer vendor, contract, integration, security review, and system for an employee to learn. That is how IT usually reads consolidation, and it is real. TeamHealth reaches 23,000 clinicians on mobile regardless of location, with more than 200 applications integrated through single sign-on and one click away on the mobile dashboard. The employee-side arithmetic matters at least as much. Every additional app is another login and another interface, and for a worker with three minutes between tasks, another reason to give up. Consolidation is usually presented as an IT saving. On a frontline it is an adoption strategy. It is also the foundation the AI plan depends on. An assistant can only answer from content that is current and governed, and it can only act for an employee when there is one identity to act as. Four point tools hold four partial copies of both. That is why [the platform decision comes first](https://www.mangoapps.com/articles/platform-decision-first), before the AI decision and before the next point purchase. ## The return that does not have a dollar figure Three things become measurable that were not measurable before, and none of them has a line in the model. The first is what share of the workforce actually received a critical message, by site and by shift, rather than how many were sent. The second is which sites and shifts are drifting away while there is still time to act. The third is whether anything changed after employees told you something. > Communication is still routinely funded on faith. It does not have to be. All three are the reason the function gets taken seriously in the meeting where budgets are set. A communications leader who can name the stores where acknowledgment of a safety stand-down fell below target is having a different conversation from one reporting open rates. ## Run it on your workforce You need five numbers to run this model on your own workforce. 1. Frontline headcount. 2. Current annual frontline turnover. 3. Number of frontline supervisors. 4. Your current per-employee cost across the tools the platform would replace. 5. The completion rate you report on mandatory training, and your honest estimate of the real one. Each line of the return model is a short formula on those inputs. The defaults are the assumptions used above, and every one of them is meant to be overwritten. | Line | Formula | Default result | |---|---|---| | Reduced turnover | Frontline headcount × points of turnover reduction × replacement cost (default one third of average frontline salary) | 4,000 × 3% × $12,500 = $1.5M | | Recovered supervisor time | Supervisors × weekly hours spent relaying × 50 working weeks × one third × loaded hourly cost | 250 × 3 × 50 × ⅓ × $32 = $400K | | Verified compliance | Employees × mandatory assignments × (reported completion minus real completion) | 5,000 × 2 × 15% = 1,500 unverified completions | | Retired software | Per-employee cost of the replaced tools × employees covered | About $48 × 5,000 = $240K | | Governed channels | Not modeled as a run-rate | Tail risk | The fifth input is the uncomfortable one, because the distance between the reported number and the honest one is the exposure. Then there is the objection every business case meets, that there is no budget this year. Start with the gap that costs the most and run the model on it. Most organizations find the turnover line alone exceeds the software cost by an order of magnitude, and most retire four to five existing contracts within eighteen months, which changes what the net cost actually is. It is one of the conversations worked through in [what to say when you already have an intranet](https://www.mangoapps.com/articles/we-already-have-an-intranet), and it usually turns a budget question into a sequencing one. If you have not yet scored which gaps are open, do that first with the [frontline communication audit](https://www.mangoapps.com/articles/frontline-communication-audit). It tells you which line of this model to run before the others. The software line was never where the money was. The decision in front of most employers isn't whether they can afford to close the gaps. It's which gap they close first. **Download *Frontline Worker Communication & Engagement*** for the complete cost and return model and the evaluation questions that go with it. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) Score your gaps with the [frontline communication audit](https://www.mangoapps.com/articles/frontline-communication-audit), or [see it configured for your sites](https://www.mangoapps.com/schedule-a-call). *The AI Platform for the Frontline Workforce.* ## Frequently asked questions **How do you calculate ROI on an employee communication platform?** Model four lines, turnover, supervisor time, compliance exposure, and software, and expect turnover to dominate. For a 5,000-employee employer with 4,000 frontline workers, a three-point turnover reduction is worth about $1.5 million a year, against roughly $400,000 in recovered supervisor time and $240,000 or more in retired software. Compliance shows up as avoided exposure rather than a run-rate saving. State every assumption so finance can change it. **How much does replacing a frontline worker cost?** This model uses about one third of annual salary, roughly $12,500 for an average frontline role. Specialized roles cost far more. Replacing a bedside registered nurse averages about $56,300, which means each point of RN turnover costs a typical hospital roughly $262,500 a year (NSI Nursing Solutions Report, 2024). **How many tools does a communication platform typically replace?** Most MangoApps customers retire four to five point solutions within the first eighteen months. The model assumes four, covering communication, engagement, recognition, and knowledge, at an average $60,000 contract each. The saving counts only if the platform actually replaces those tools. Added on top of them, it makes the software line negative. **Is communication ROI mostly software savings or workforce savings?** Workforce savings, by an order of magnitude. In the model, frontline turnover costs $20.0 million a year against $240,000 or more in duplicate software. Judging a communication platform only against its license cost compares it with the smallest number in the case. **What inputs do I need to build the business case?** You need five: frontline headcount, current annual turnover, the number of frontline supervisors, your per-employee cost across the tools the platform would replace, and your reported mandatory-training completion rate alongside an honest estimate of the real one. With those, every line of the model can be recalculated for your workforce. The honest completion estimate is usually the hardest to give and the most revealing. **What if we do not have budget for a new platform this year?** Run the model anyway, starting with the gap that costs you most, and look at net cost after consolidation. Most organizations find the turnover line alone exceeds the software cost by an order of magnitude. Retiring four to five existing contracts within eighteen months also changes what the platform costs net. The budget question often becomes a question of sequence. **How conservative is a three-point turnover improvement?** It's modest against what customers report after closing the delivery and listening gaps, though the model deliberately relies on no specific customer figure. The 40% baseline is also below the more than 60% annual turnover that retail frontlines run (McKinsey retail frontline research, 2024). Both the starting point and the improvement lean low. **What returns cannot be put in dollars?** Three: the share of the workforce that actually received a critical message, which sites and shifts are drifting away, and whether anything changed after employees spoke up. None has a line in the model. All three become measurable once the channel reaches everyone, and they're what gets the function taken seriously when budgets are set. --- # The Six Reach Gaps: A Diagnostic for Frontline Communication **Author:** Andy Tolton **Published:** 2026-09-21 **Category:** frontline-communication Most frontline communication quietly runs on supervisors relaying messages by hand. Score where delivery, answers, proof, and governance break before you sit through a vendor demo. *Frontline communication fails in six specific places: the message never arrives, the manager carries the whole channel, nothing comes back from the floor, answers are scattered across systems, nobody can prove what landed, and ungoverned channels fill the vacuum. Each gap has one diagnostic question. Answer all six honestly and the total tells you how much of your communication runs on infrastructure and how much runs on the goodwill of your supervisors.* The policy change went out Monday night. On Wednesday a cashier hears about it from a customer at the register, and nobody at headquarters will ever know, because every report says the message was sent. That distance between sent and received is where most frontline communication actually operates. It's rarely one failure. It's six, stacked, and each can be named and scored. The case for why [sending is not reaching](https://www.mangoapps.com/articles/why-frontline-communication-fails) is made elsewhere. This is the working tool: six questions a communications team can answer in under an hour, with someone from operations in the room to keep the answers honest. ## Why a diagnostic, and why before the demo Score your own operation before you look at anyone's feature list, because the gaps you have open decide where to start and what to buy. Most evaluations run the other way round. A vendor shows what the product does well, and those strengths quietly become your requirements. A company whose problem is delivery needs a different first purchase from one whose problem is proof, and a demo will happily sell either of them the wrong thing. Mark each question Open, Partly closed, or Closed, and answer as things are this week, not as the rollout plan says they'll be. Two tests help. If the honest answer depends on one supervisor who happens to be excellent, the gap is Partly closed at best. If you'd need to go and check before answering, mark it Open. | Gap | The question | Open | Partly closed | Closed | |---|---|---|---|---| | 1. Delivery | Can you send a message directly to every employee without a corporate email address, a company device, or a VPN? | | | | | 2. The manager | If a supervisor is out sick, does their team still receive company communication that week? | | | | | 3. The return path | In the last 90 days, has anything a frontline employee told you visibly changed a decision? | | | | | 4. Answers | Can an employee find the answer to a policy, pay, schedule, or training question without asking a person? | | | | | 5. Proof | For your last critical message, can you name the sites where acknowledgment fell below target? | | | | | 6. Governance | Do you know which unapproved channels your teams currently coordinate work in? | | | | Count the rows marked Open. The bands at the end read from that number, and the Partly closed rows show where work has already started. ## Gap 1. Delivery Delivery decides whether the other five gaps can be measured at all, since a message that never arrives cannot be acknowledged or answered. ### Can you send a message directly to every employee without a corporate email address, a company device, or a VPN? Open looks like this on a Tuesday. The morning's update is taped beside the time clock. A shift lead reads the headline aloud at the huddle, and the three people who start at ten never hear it. The email version went to store managers, who were asked to cascade it. Closed means every employee is provisioned and reachable in minutes on the phone they already carry, with no corporate email and no password between them and the message. That includes the person hired on Friday. The cost shows up everywhere downstream. Until this closes, every number you report describes the subset you could reach and calls it the workforce. In Microsoft's frontline research, 63% of frontline workers said messages from leadership do not reach them (Microsoft Work Trend Index Special Report, 2022). Not unclear, not badly timed. Not arriving. ## Gap 2. The manager When the direct channel fails, the supervisor becomes the channel, and the test is what happens the week that supervisor is out. ### If a supervisor is out sick, does their team still receive company communication that week? If the answer is no, everyone on the floor already knows it. The covering lead has a crew of their own. Updates pile up until Monday, and the team that most needed the safety reminder gets it five days late and secondhand. Closed doesn't mean the supervisor leaves communication. It means direct delivery targeted by site, role, and shift, so the supervisor adds context and handles the hard questions instead of being the only copy of the message. The cost lands on supervisor hours, in the most overloaded role in the company. Gallup attributes 70% of the variance in team engagement to the manager ([Gallup, 2014](https://www.gallup.com/workplace/231593/why-great-managers-rare.aspx)), and manager engagement fell from 30% to 27% in a single year ([Gallup, State of the Global Workplace, 2025](https://www.gallup.com/workplace/659279/global-engagement-falls-second-type-2009.aspx)). Routing more through that role and calling it a strategy is how the gap stays open. ## Gap 3. The return path Frontline communication usually runs one way, so this question asks whether anything the floor says travels back far enough to change a decision. ### In the last 90 days, has anything a frontline employee told you visibly changed a decision? A night-shift picker has noticed the new pick path adds a walk across the building on every order. There is nowhere to say so except to a supervisor with no route to escalate it. The annual survey is the only formal return path, and its results arrive months after anyone could have acted. Closing this takes short pulses and anonymous feedback, followed by a message back to the people who raised an issue that tells them what changed. That follow-up is the piece most organizations skip, and it decides whether anyone answers next time. The cost is recorded in other departments' budgets, as turnover and as incidents that were reportable months earlier. Global engagement sits at 20%, its lowest level since 2020 (Gallup, State of the Global Workplace 2026). ## Gap 4. Answers Answers are scattered when the schedule, the policy, training, and pay each live in a different system, so every question that can't find its answer routes to a person. ### Can an employee find the answer to a policy, pay, schedule, or training question without asking a person? An associate wants to know how holiday pay works for a shift that crosses midnight. They ask a coworker, who guesses. Then they ask the supervisor, who looks it up in a system the associate cannot reach. Closed requires one place to ask in plain language, answering from the actual policy document and scoped to that employee's site and employment type. This is also where the AI question gets decided. An assistant can only answer from content that is current, governed, and in one place, so the consolidation this gap demands is the foundation any AI for employees will need. The cost compounds Gap 2, because every unanswered question lands on the supervisor. Frontline employees accessed an average of 2.3 material channels in 2025 (Gartner, 2025). That isn't choice. It means no single channel holds enough to be worth checking. ## Gap 5. Proof Proof is the gap most organizations don't know they have, because their reports look full. ### For your last critical message, can you name the sites where acknowledgment fell below target? Open is knowing the message was sent and roughly how many people opened it, without being able to say which three sites never confirmed. You find out during an audit or after an incident. A post went out, a page was viewed, a newsletter was sent. None of that establishes that the people who needed the message received it or acted on it. Closed requires acknowledgment captured per employee and reported by site and shift, with an automatic re-send to anyone who hasn't viewed it. Leave it open and the function cannot defend its budget, because nobody can tell a campaign that worked from one that was wasted. Compliance carries the rest of the cost. In a hospital, documented acknowledgment of a protocol change is not a reporting nicety. It is the audit. ## Gap 6. Governance Ungoverned channels fill whatever space the sanctioned channel leaves, and the exposure is created by the gap, not by the employees. ### Do you know which unapproved channels your teams currently coordinate work in? Open sounds like "probably." There's a personal messaging group for the night crew at one distribution center, and very likely one for every store. Shift swaps get agreed there, and so do workarounds to a safety procedure. If legal asked for last month's messages, you couldn't produce them. Policy alone doesn't close this. A sanctioned channel that workers actually prefer does, with retention and eDiscovery applied to it. The cost is tail risk, easy to dismiss until it arrives. Regulators have levied more than $2.5 billion in combined fines for work conducted on unapproved personal messaging channels (SEC and CFTC enforcement actions, 2021 to 2024). **Download *Frontline Worker Communication & Engagement*.** It carries the printable scorecard and a cost model you can run with your own numbers. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) ## Reading your score The number of rows marked Open says less about how good your communication is than about where the first fix belongs. ### Five or six open The channel is not the problem to fix first. The infrastructure underneath it is. At this score, better writing and a tighter editorial calendar only improve a message on its way to somewhere it will not arrive. Start with delivery, and write down what a platform has to do before you look at one. [What a frontline employee app actually requires](https://www.mangoapps.com/articles/frontline-employee-app-requirements) is the list we'd start from. ### Three or four open You have delivery working somewhere and proof working nowhere. This is the most common result. Desk staff and a handful of well-run sites are reachable, so the reports look healthy, and nobody can say which locations sit below target on a critical message. Start with [acknowledgment and reporting at the message level](https://www.mangoapps.com/articles/employee-acknowledgment-tracking), which turns the reach you already have into evidence. ### One or two open The remaining gaps are almost always measurement and governance, the two that cost you the most credibility with the executive team. Reach is good and the function is still reporting activity. Close proof first, then look hard at where coordination happens off the record. [The personal group chat problem](https://www.mangoapps.com/articles/personal-messaging-apps-frontline-compliance) sets out why banning those groups fails and what replaces them. ## What to do with the result Treat every row marked Open as a requirement you will insist on, in the business case and in vendor evaluation. In the business case, each open gap maps to a budget line someone already owns. Delivery and the manager show up as supervisor hours. The return path shows up as turnover. Proof and governance show up as compliance exposure and tail risk. Put on one page, those lines move the conversation off the price of software and onto the cost of the workforce. In evaluation, the gaps become the questions you ask every vendor, including us, and the order in which a product closes them tells you what it was built for. Our guide to [evaluating frontline communication vendors](https://www.mangoapps.com/articles/evaluate-frontline-communication-vendors) turns the six gaps into a scored shortlist. You can also see how [internal communications on MangoApps](https://www.mangoapps.com/solutions/internal-communications) approaches each one. Then keep the scorecard. Run it again six months after you close the first gap, and the difference will be the first number your function has produced that describes what the workforce received rather than what the team sent. Get the printable scorecard and the cost model in [*Frontline Worker Communication & Engagement*](https://www.mangoapps.com/resources/frontline-communication-engagement-guide). Bring your score to a demo and [see it configured for your sites](https://www.mangoapps.com/schedule-a-call). *The AI Platform for the Frontline Workforce.* ## Frequently asked questions **How do I audit frontline communication?** Answer six questions, one per reach gap, and mark each Open, Partly closed, or Closed. The gaps are delivery, the manager, the return path, answers, proof, and governance. Score the operation as it runs this week, not as the plan says it will, and bring someone from operations to keep the answers honest. **What are the biggest gaps in internal communication?** In most organizations the biggest gaps are delivery and proof. Delivery fails because the channel assumes an inbox or a company device frontline workers don't have. Proof fails because reporting counts what was sent and opened, not who confirmed it by site. **How do you know if employees actually received a message?** You know when acknowledgment is captured at the message level and reported by site. Open rates only describe the people the message reached. Acknowledgment records each employee who confirmed, so you can name the sites below target and re-send automatically to anyone who hasn't viewed it. **Why do supervisors become the communication channel?** Supervisors become the channel because the direct channel fails. When a message can't reach a worker without email or a company device, someone has to relay it, and that falls to the person already running the shift. Supervisors remain the most trusted voice on the floor. The problem is load. **What is a communication return path?** A return path is any mechanism by which information from the floor reaches decision makers and visibly changes something. Pulses and anonymous feedback do the collecting. The follow-up message telling employees what changed keeps the path open, because it decides whether anyone answers next time. **How often should you run a communication audit?** Run it at least once a year, before any platform purchase, and after any major rollout. The annual run tracks drift. The pre-purchase run turns open gaps into requirements, and the post-rollout run shows whether the gaps you paid to close actually closed. **What is the most common result on this diagnostic?** The most common result is three or four gaps open. It usually means delivery works for desk staff and some sites while proof works nowhere. Reports look healthy because they describe only the reachable part of the workforce. **What should you fix first?** Fix delivery first, because nothing else can be measured until it works. Acknowledgment and listening both describe a subset of the workforce while delivery is open. Once everyone is reachable on their own phone, close the return path, then prove it. --- # "We Already Have Something": Six Objections to a Frontline Communication Platform, Answered Honestly **Author:** Andy Tolton **Published:** 2026-09-21 **Category:** frontline-communication The tools most organizations already run can each work well and still leave the frontline unreached. The honest test is whether any of them proves a message landed. *Most organizations already run an intranet, a chat tool, a newsletter, and an HR suite, and each does the job it was bought to do. The question is not whether those tools work. It is whether any of them reaches an employee with no inbox and proves the message landed. Here are six versions of that conversation, and the honest answer to each.* Somewhere in the second meeting, someone says it. We already have something. They're usually right. Nobody is starting from nothing. The intranet was a real project with a real budget, the chat tool is open on every laptop at headquarters, and the newsletter goes out on schedule and gets read. The HR suite may have gone live last quarter after a year of work. None of those decisions was a mistake, and anyone who suggests otherwise has not been in the room when they were made. So the objection deserves a straight answer rather than a pitch. The test that runs through every answer below is the same, and it has nothing to do with whether your current tools work. It is whether any of them was built for the part of the workforce where [sending is not reaching](https://www.mangoapps.com/articles/why-frontline-communication-fails): the associate, the line worker, the nurse at shift change, the technician in the van. ## We just bought a workforce management or HR suite. Do we have to replace it? No. You integrate. Those systems remain the source of truth for the employee record, and they feed a frontline communication platform through native integration. Nothing gets ripped out, and you keep the investment. A platform with 200+ integrations should connect to the HR, workforce management, payroll, and learning systems you already run, so that a role change or a site transfer in HR updates the employee's audiences and access automatically. Nobody reconciles two lists by hand. That connection is also what makes provisioning work at frontline turnover rates. When a new hire appears in the HR system, they should appear in the right site, shift, language, and audience in the communication platform without a ticket. The HR suite does the hiring. The platform does the reaching. What those systems don't do is reach a worker with no inbox and prove the message landed. That is a different job. An HR suite is built to hold the record and run the transactions around it, and it does both well. It was never designed to put a safety notice on a warehouse picker's personal phone, in their own language, and then show you an hour before the shift which sites haven't opened it. The two sit side by side, and the integration between them is built during the connect phase of a rollout, before any employee sees anything. ## We already have an intranet. Isn't that enough? Then you have solved this for the people with a desk. The question worth asking is what share of your workforce logged into the intranet last week, and whether you can answer that by site. Most organizations can answer it for headquarters. Far fewer can answer it for the distribution centers, the stores, or the night shift, and the ones who can rarely like the number. An intranet is not the wrong tool. It is a tool built for a different user, as a destination website visited from a computer during working hours. Making it responsive puts that website on a smaller screen, but it is still reached through a sign-in built for a desk identity and still organized for someone browsing rather than someone checking between tasks. The differences between [a mobile intranet and a frontline employee app](https://www.mangoapps.com/articles/mobile-intranet-vs-frontline-employee-app) run deeper than screen size. None of this means switching the intranet off. It keeps serving the people it was built for. The frontline app carries what workers need on shift, the intranet carries what desk teams need at a desk, and the two can run side by side. The decision isn't which one to keep. It's whether the frontline has a front door at all. ## We already have a chat tool. Isn't chat enough? Chat is necessary and not sufficient. It carries conversation well. It carries governed, targeted, acknowledged communication poorly, because it was built for people talking to each other rather than for an organization making sure a specific message reached a specific group and can be proven to have done so. Two questions settle it quickly. Can you require acknowledgment on a safety notice, and then evidence it by site and shift? And can a worker with no corporate account be reached at all? A tool that requires a company identity cannot reach someone who was never given one. If the answer to the second question is no, the first one doesn't matter. There is a second risk hiding in the chat conversation. When the sanctioned channel does not reach frontline teams, they coordinate in [personal messaging groups](https://www.mangoapps.com/articles/personal-messaging-apps-frontline-compliance) the company does not own and cannot produce in an audit. Combined SEC and CFTC fines for work conducted on unapproved personal messaging channels passed $2.5 billion (SEC and CFTC enforcement actions, 2021 to 2024). The answer is not less chat. It is chat inside a governed platform, with retention and eDiscovery applied, and with broadcast and acknowledgment sitting beside it rather than improvised on top of it. ## Our newsletter gets good open rates. Doesn't that mean communication is working? Open rates measure the people who received it. The question is what fraction of the frontline is in that denominator. Roughly 80% of the global workforce is deskless (Emergence Capital, 2018; share reconfirmed by BCG, 2024), and most of those people have no corporate inbox for a newsletter to land in. When Microsoft asked frontline workers directly, 63% said messages from company leadership do not reach them (Microsoft Work Trend Index Special Report, 2022). Not that the messages were unclear or badly timed. That they did not arrive. So a strong open rate can be completely accurate and still describe the wrong population. In a frontline-heavy organization, the newsletter is often performing well among the desk-based minority who were never the problem, while the people on the floor sit outside the measurement entirely. A better measure starts with the whole workforce as the denominator. For your last critical message, can you name the sites where acknowledgment fell below target? If the reporting can only tell you who opened an email, it can't tell you who was never sent one. ## Won't our frontline resist another app? They will, and that is the right instinct. Every additional app is another login, another interface, and another reason for a worker with three minutes to give up. Consolidation is usually presented as an IT saving. On a frontline, it is an adoption strategy. It is also why a frontline Employee Platform should consolidate rather than add. The schedule, pay, training, and answers belong in the same app that carries the news. The schedule alone changes the math, because it is the single most reliable reason a frontline employee opens an app, and everything else in that app benefits from the visit. MangoApps customers average more than 90% adoption within 90 days, and the reason is not persuasion. The app is where something they need already lives. The Kansas City Chiefs show the pattern with a workforce that scales up and turns over every season. Their branded app, Huddle, reached 90% adoption among more than 600 game-day event staff, up from a 40% average adoption rate organization-wide. The [adoption playbook](https://www.mangoapps.com/articles/frontline-employee-app-adoption) behind numbers like that has more to do with what the app holds than how it is launched. **Download *Frontline Worker Communication & Engagement*.** It lays out the six reach gaps and the cost model behind each objection answered here. [Get the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide) ## There's no budget for a new platform this year. Where would we start? Start with the gap that costs the most, and run the model with your own numbers. Most organizations find the turnover line alone exceeds the software cost by an order of magnitude. Take an illustrative employer with 4,000 frontline workers at 40% annual turnover. That is 1,600 separations a year, and at a replacement cost of roughly $12,500 each, about $20 million. Retail frontline turnover runs above 60% a year (McKinsey, 2024), so 40% is deliberately conservative. Bringing turnover down three points, to 37%, returns about $1.5 million a year in the same model. The duplicate software in the same model costs closer to a quarter of a million a year. The second line changes what the net cost actually is. Most customers retire four to five existing point solutions within eighteen months, covering tools for communication, recognition, engagement, and knowledge that each carry their own contract and security review. The budget for a platform is often already being spent, just in several places. The [business case for frontline communication](https://www.mangoapps.com/articles/frontline-communication-business-case) walks through every line of the model, including supervisor time and compliance exposure. Bring your own headcount and turnover rate, and the conversation with finance changes shape. ## The one question underneath all six Every objection above comes back to one question. Does anything you run today reach an employee with no inbox and prove the message landed? If the answer is yes, you may not need this. If the answer is no, the tools you have are not wrong. They are incomplete, and the part they leave out is the part of the workforce that serves the customer, treats the patient, and runs the line. That gap doesn't close by working harder inside the existing channels. It closes when the frontline stops being the part of the workforce that gets reached later. [Score the six reach gaps](https://www.mangoapps.com/articles/frontline-communication-audit) in your own operation first. [Download the book](https://www.mangoapps.com/resources/frontline-communication-engagement-guide), or [talk to someone who knows your industry](https://www.mangoapps.com/schedule-a-call). *The AI Platform for the Frontline Workforce.* ## Frequently asked questions **Do we have to replace our HR or workforce management suite to add a frontline communication platform?** No, you integrate it. The HR and workforce management systems stay the source of truth for the employee record and feed the platform through native integration. Role and site changes then update audiences and access automatically, and nothing gets ripped out. **Is an intranet enough to reach frontline employees?** An intranet solves communication for employees with a desk, but rarely for the frontline. It was built as a destination website visited from a computer, reached through a sign-in that assumes a corporate identity. Check what share of your workforce logged in last week, by site, to see where it stops reaching. **Is a chat tool enough for internal communications?** Chat is necessary but not sufficient. It handles conversation well and handles governed, targeted, acknowledged communication poorly. A chat tool that requires a corporate account also cannot reach a worker who has never been given one. **Do good newsletter open rates mean frontline communication is working?** No, because open rates only measure the people who received the newsletter. Most frontline workers have no corporate inbox, so they sit outside the denominator entirely. Acknowledgment by site on critical messages is a more honest measure. **Will frontline employees use another app?** They will use one that holds something they need on every shift. A platform that brings the schedule, pay, training, and answers into the same app as company news consolidates tools rather than adding one. That is why MangoApps customers average more than 90% adoption within 90 days. **How can we fund a frontline communication platform without new budget?** Start with the gap that costs the most and model it with your own numbers. In most organizations the turnover line alone exceeds the software cost by an order of magnitude. Retiring existing point solutions then offsets much of the software cost itself. **Does an employee app replace the intranet?** Not necessarily. The intranet can keep serving employees at a desk, while the frontline app carries what workers need on shift. The two can run side by side, because the real decision is whether the frontline has a front door at all. **How long before existing tools can be retired?** Most customers retire four to five point solutions within the first eighteen months. The usual candidates are separate tools for communication, recognition, engagement, and knowledge. Each one retired also removes a contract, an integration to maintain, and a security review. --- # The Hidden Tax of Lost Context in Frontline Operations **Author:** MangoApps Team **Published:** 2026-09-20 **Category:** operational-efficiency She's two weeks into the supervisor role and already asked the same question twice this week: "Did we ever figure out why the evening shift keeps running short?" Her manager can't remember. The... # The Hidden Tax of Lost Context in Frontline Operations She's two weeks into the supervisor role and already asked the same question twice this week: "Did we ever figure out why the evening shift keeps running short?" Her manager can't remember. The team's chat from three months ago is buried. The workspace where that problem was documented got deleted by accident, and nobody thought to restore it. Somewhere, the answer exists. It just can't be found. This kind of context loss is so common in frontline operations that most teams don't name it. They call it "onboarding time" or "communication gaps" or just "how things go." But it adds up — every follow-up email asking for information that was already submitted, every project rebuilt from scratch because someone hit delete, every AI conversation that starts over from zero because the last session closed. The cost isn't dramatic. It's a slow, steady tax on organizational time and institutional knowledge. And this week, MangoApps closed several of the gaps where that context slips away. ## When Work Already Exists and Needs to Stay Connected The most frustrating kind of rework is rebuilding something that was never truly lost — just disconnected. Take tasks. In most project management tools, tasks belong to one place. If a task was created in a standing to-do list but now needs to live inside a project, the choices are unattractive: copy it and lose the history, or leave it in place and lose visibility. This week, [workspace owners can link existing tasks](https://www.mangoapps.com/changelog/3146) from the Tasks app directly into a workspace list — preserving the original comments, due dates, assignees, and status updates intact. The task doesn't duplicate. It connects. The same principle applies to recovery. When someone deletes a workspace — by accident, or as part of a cleanup that went too far — everything in it has typically been gone for good: conversations, pinned files, linked tasks, project history. [Deleted workspaces now land in a Trash view](https://www.mangoapps.com/changelog/3145) with a 30-day window before permanent removal. For teams running month-long projects or compliance reviews, that window is the difference between a brief scare and a real loss. For teams building internal sites and communications, a careless edit used to mean publishing something unfinished or reverting to a prior state that required reconstruction. [The Sites editor now auto-saves as you type](https://www.mangoapps.com/changelog/3143), creates a restore point each time you press Save, and lets you browse version history without leaving the editor. Whatever work you've done is always recoverable. None of these features are individually dramatic. But they share a common architecture: instead of making teams protect their own work against the platform, the platform protects it. ## When the Conversation Already Happened Context loss in communication is subtler — and often more expensive — than lost files. A customer submits a support ticket. The agent opens it and sees a name, a contact email, and a general description. The first message the agent sends is a follow-up asking for what should have been collected upfront: the specific system, the error message, the account type. That follow-up introduces delay, creates friction, and signals to the customer that the intake form didn't work. [Service Desk now surfaces custom questions in the external customer portal](https://www.mangoapps.com/changelog/3145) — the same structured questions your team configured for each request type, now visible to external customers filing tickets. Tickets arrive with the details agents need. The clarifying email becomes unnecessary before it's sent. A similar loop plays out with AI tools. A manager spends time building context in Ask AI around a recurring attendance issue — specific team dynamics, specific language preferences, specific constraints. The conversation produces something useful. It closes. Next week, same problem, new session: the context has to be rebuilt from scratch. [Any closed Ask AI conversation can now be continued in one click](https://www.mangoapps.com/changelog/3143), picking up exactly where it left off. And for work that involves documents, [Ask AI now reads attached files](https://www.mangoapps.com/changelog/3142) — text, CSV, Word, and Excel — so a manager can ask questions directly about a staffing report or a policy document without first summarizing its contents in chat. The assumption embedded in these releases is worth stating plainly: the conversation you had yesterday is still relevant today. Tools should act like it. ## When Knowledge Lives Only in Someone's Head The deepest form of context loss is institutional. A senior technician knows why a particular line runs differently after Tuesday maintenance. A veteran shift lead knows which customers require a specific accommodations workflow. A team trainer knows how to walk a new hire through a process that isn't documented anywhere. When that person leaves — or is simply unavailable — the knowledge doesn't transfer automatically. It usually doesn't transfer at all. This week, [Recorder became generally available](https://www.mangoapps.com/changelog/3141). Employees can capture their screen or camera in the desktop app, with transcription and captions generated automatically. But the more significant part is the handoff: recordings can go directly to Training, to the Library, or attached to a Service Desk ticket as supporting context — without leaving the platform, without extra steps between capture and distribution. That single path changes what knowledge capture actually costs. A five-minute screen recording of an end-of-shift reconciliation process becomes a training resource in the same session it was made. A walkthrough shared in a ticket becomes referenceable for the next agent who encounters a similar case. Frontline knowledge doesn't have to stay trapped in individual expertise. But capturing it has to be low-friction enough that people actually do it — which means recording, transcribing, and routing to the right place can't each require a separate tool and a separate decision. ## The Compounding Return on Work That Persists Taken individually, this week's releases look like product maintenance — quality improvements to surfaces that already existed. Viewed together, they reflect a more deliberate design position: work that exists should stay accessible, in the form it was created, without requiring ongoing effort to preserve it. That sounds like a baseline expectation. For most enterprise software, it isn't. Context slips through disconnected apps, closed sessions, deleted records, undocumented expertise, and intake forms that don't ask the right questions. Teams absorb the cost of reconstruction so gradually that it registers as background noise rather than a solvable problem. The compounding effect of reducing those losses is real, even when any single instance looks minor. A team that can find and build on what already exists makes fewer clarifying requests, runs fewer recovery operations, and holds onto more of the institutional knowledge that makes daily operations actually function. Over months, those recovered hours become material. The changes this week won't eliminate rework entirely. But they close specific gaps that have been real sources of friction: the deleted workspace nobody thought to restore, the ticket that needed a follow-up email, the AI session that had to start over, the expert walkthrough that never got recorded because the recording flow required too many steps. A smaller tax, more consistently, across more of the platform. --- # Where AI Actually Changes a Field Service Operation **Author:** Andy Tolton **Published:** 2026-09-18 **Category:** field-services Who to send, what to quote, what the manual says and what the numbers mean. Where AI does real work in field service, and why it must see the whole operation. Imagine an assistant that has read every standard operating procedure your company has ever written. A technician standing in front of an electrical panel asks it whether she's certified to open the panel. The assistant can quote the procedure for opening it. It can't answer the question, because the credential lives in a system it can't see. That gap is where most AI in field service gets stuck. The useful question isn't which AI features a vendor lists. It's what the AI can see, and what it can do about it. AI in field service isn't hypothetical. It's already changing dispatch decisions, technician troubleshooting, back-office work and customer communication. The question for operations leaders is whether the AI they deploy will be governed, accurate and connected to the work, or an unmanaged sprawl of standalone tools. ## Lead with outputs, not capabilities Capability lists are easy to write and hard to evaluate. A better test is to name the output. A recommended technician for an open job. A draft estimate that the technician reviews and sends. A diagnostic step pulled from your own service manual. An answer to "which service lines had the longest days-to-invoice last quarter?" Those four are concrete, and each one is a piece of work that used to wait for a person. The rest of this article follows them through the four groups of people who touch a field service operation. ## For the technician: a specialist on call at every job **What is a troubleshooting assistant for technicians?** It's an assistant a technician can ask from the phone, at the job, describing a symptom and getting diagnostic steps from your own service manuals and past resolved cases. That distinction matters: the answer comes from your documentation and not from generic results on the internet. A few kinds of assistant do that work. **Troubleshooting.** Describe the symptoms, get diagnostic steps sourced from your manuals and from cases your team has already resolved. **Safety protocol.** Lockout-tagout, arc flash and PPE requirements, surfaced instantly from the company's own safety documentation, from the field. **Role-specific.** Commercial HVAC, residential plumbing, foreman, apprentice. Each has its own knowledge set and guardrails tailored to the role, so an apprentice doesn't get the answer meant for a foreman. **Does field service AI use my company's data or the public internet?** It uses yours. The assistants are trained on your SOPs, product manuals, pricing, safety protocols and internal knowledge, and retrieval-augmented generation grounds each answer in your own documentation. The answers are grounded in your documentation, not public internet content. ## For dispatch: who to send, and in what order **How is AI used in field service dispatch?** Mainly to recommend an assignment and to explain why. Given an open job, the assistant suggests the best technician in real time, weighing proximity, workload, skills, certification and priority, along with experience with similar work. The dispatcher decides, and the assistant shows its reasoning so the decision stays a human one. Three more dispatch uses sit alongside it: - **Route sequencing.** Full-day optimization that minimizes drive time, respects customer windows and holds up when the day is disrupted midway. - **Predictive scheduling.** Anticipating workload from service contracts, historical demand patterns and seasonal trends before the queue fills up. - **Demand forecasting.** Capacity planning at the workforce level, surfacing the signals before they become dispatch emergencies. Treat it as a signal to plan against and not a promise. The governance point belongs here, too. Governance isn't only about what an AI can read. The platform should decline an assignment that the credential doesn't support. That works in two directions: the recommendation shouldn't propose a technician the credential doesn't cover, and the board shouldn't accept the assignment if a person tries it anyway. The full argument is in [why an expired certification should block dispatch automatically](/articles/expired-certification-blocks-dispatch). You can see where the recommendation fits into a shift in [a day in dispatch](/articles/day-in-field-service-dispatch). ## For the back office: the queue work **Can AI write an estimate or an invoice?** It can draft either one, and a person reviews it. The back office has a queue of work that's tedious and time-sensitive, and it's where AI does its most immediate work. - **Estimates.** Describe the job or name the service type, and the assistant drafts an estimate against your price book. The technician reviews it, adjusts it and sends it. See [the price depends on which technician showed up](/articles/price-book-on-site-estimates-field-service). - **Invoices.** Formatting, line-item categorization and customer-specific billing logic are handled automatically, with exceptions flagged for human review. - **Documentation.** Drafts of SOPs and procedures for new service lines or equipment in minutes rather than days. Teams review and refine, and the AI does the first pass. - **Customer communications.** Service confirmations, ETA updates, follow-ups and review requests, drafted in your brand voice. - **Analytics.** Ask a question in plain language and get an answer with the underlying data. One more, delivered through People Operations: engagement risk detection, which looks for patterns across technician behavior and flags attrition risk before a resignation arrives. It's a signal for a manager to start a conversation and not a verdict, and [the staffing article](/articles/seasonal-licensed-field-workforce) explains how to think about it. ## Ask AI: one front door Rather than a different assistant in every app, one front door on the phone the technician already carries. Ask AI can summarize a bulletin, build an inspection form from a description, recommend who to send, draft an estimate against the price book and read a work order before you commit a crew to it. Every action runs as the person who asked, and every one is logged. That's the subject of [whose permissions does the AI inherit?](/articles/ai-governance-whose-permissions-does-the-ai-inherit), which we'd read before signing anything. ## Why this only works on one platform An assistant that reads your SOPs but not your dispatch board can't answer the certification question. The data model, the permissions and the work all have to be in one place for the AI to see enough to help, and be governed enough to trust. That's why AI is the reason the platform decision is strategic and not a feature to compare. Standalone tools can each be good. None of them can see the whole operation, and none can enforce a rule that spans two systems. **What is the difference between AI built into a platform and a standalone AI tool?** A standalone tool works on what you give it. AI built into a platform works on what the platform already knows (the job, the technician, the credential, the price list) and operates inside the same permissions. MangoApps is The AI Platform for the Frontline Workforce, with AI embedded in every module and available to every employee, inside the same governance, security and data model as the rest of the platform. Field Service Suite is part of that platform, so the assistant that recommends a technician is reading the same record the dispatcher sees. Adoption comes into it as well. AI only works for someone who opens the app, and [the article on why technicians work around their tools](/articles/why-technicians-work-around-field-service-software) covers what gets them to. ## Keep a person in the loop Every output described above has a person at the decision point. The dispatcher decides among the recommendations. The technician reviews the estimate before it goes to the customer. The office reviews the exceptions on an invoice. The manager decides what to do with a retention signal. That isn't a limitation. It's the design. In field work, the cost of a wrong answer lands on a customer's home or a technician's safety, and a person who's been in the room is better placed to judge it. AI's job is the first pass, the lookup and the draft, and the person's job is the call. It's also why the work suits a field workforce: the assistant makes an experienced technician faster, and it gives a newer one something to check their thinking against. ## Start with one output You don't need a strategy for all of this at once. Pick one output that costs your team time every week, such as draft estimates or invoice exceptions, and run it for a month. Watch what the reviewers change. If they're changing very little, expand it. If they're rewriting most of it, look at what the AI can't see and fix that before adding anything else. Most of the time, what an assistant gets wrong is what it doesn't have: a price that isn't in the price book, a manual that was never uploaded, a credential that isn't on the record. Those are data problems, and they're the reason a platform matters more than a feature. ## The sentence to hold vendors to The sentence worth holding any vendor to is this one: everything described runs in production today. Ask which of their AI claims a customer is using this week. A demo of something in beta and a customer running it in production are different things, and the difference is easy to see if you ask. Put the question in your evaluation with [the twelve questions](/articles/how-to-evaluate-field-service-platform), and see [whose permissions the AI inherits](/articles/ai-governance-whose-permissions-does-the-ai-inherit) for the questions to ask about governance. If you're wondering how AI factors into the older story of why field service software looks the way it does, read [why field service software has been split down the middle](/articles/field-service-software-split-down-the-middle). And if you already run a tool and are asking whether AI means starting over, [it doesn't](/articles/replace-fsm-tool-or-consolidate). The AI sections of the [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide) cover assistants, dispatch, back-office work and governance in more detail. You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### How is AI used in field service dispatch? AI recommends which technician to send to an open job, weighing proximity, workload, skills, certification and priority in real time, and explains its reasoning so the dispatcher can decide. It can also sequence a day's stops to cut drive time, and forecast demand so capacity is planned before the queue fills. A governed platform also declines an assignment that a technician's credentials don't support. ### Can AI generate estimates and invoices for field service? AI can draft an estimate from a description or service type using the price book, which the technician reviews, adjusts and sends. It can also handle invoice formatting, line-item categorization and customer-specific billing logic, flagging exceptions for human review. ### What is a troubleshooting assistant for technicians and what is it trained on? It's an assistant a technician can ask from the field. They describe the symptoms and get diagnostic steps. It's trained on your company's own service manuals, procedures, safety protocols and past resolved cases, and each answer is grounded in that documentation and not in public internet content. ### Does field service AI use my company's data or the public internet? It should use your data, inside your permissions. Your company's information shouldn't be used to train public models, and the assistants should answer from your own documentation. Ask any vendor where a prompt goes, what is retained and whether anything trains a public model. ### Is AI in field service software a separate product or built in? It can be either, and the difference matters. A standalone AI product works only on what you feed it. AI built into the platform works on the same records, permissions and audit trail as the rest of the software, which is what lets it answer questions like whether a technician is certified for a job. --- # Electrical Contractors: Compliance Built Into Every Step of the Job **Author:** Andy Tolton **Published:** 2026-09-17 **Category:** field-services State licensing, code training and OSHA on one side, progress billing and change orders on the other. What software has to do for an electrical contractor. The change order was agreed on the site, on a Thursday, standing next to a panel. It never reached the invoice, because it was written on a ticket that stayed in the truck. Three weeks later the project closed and the extra work had been done, and paid for by nobody. Elsewhere on the same project, a journeyman's license had lapsed halfway through. Nobody noticed, because the renewal date lived in someone's calendar. Electrical contracting carries two kinds of complexity at once, and the two tend to fail at the same seam. ## Compliance and cash flow fail in the same place Electrical work carries strict requirements: state licensing, code training, OSHA regulations and arc flash safety. It also carries multi-phase projects with progress billing and change orders. Disconnected systems make that administrative load much heavier, because every rule and every billing event lives in a different place. Three things have to be true of the software. It has to manage licenses and certifications at scale and connect them to dispatch. It has to estimate and invoice multi-phase projects without re-keying. And it has to put safety checklists and protocols in the technician's hand on site. This article doesn't interpret codes or regulations. It covers how software keeps the records the rules generate. ## License and certification management at scale **How do electrical contractors track technician licensing across states?** Track it per technician, on the employee record, with renewal alerts that arrive before the date and not after it. State licensing is tracked per technician with renewal alerts. Code training and compliance are delivered in the learning system, so completion is recorded where the credential is. Certification status is connected directly to dispatch eligibility, and records are audit-ready with full version history. The connection to dispatch is the part that changes outcomes. A record that only reminds someone leaves the assignment up to that person's attention. A record the board reads takes the assignment out of their hands. [Why an expired certification should block dispatch automatically](/articles/expired-certification-blocks-dispatch) makes the case in detail. **How does certification status affect dispatch for electrical work?** It should determine who can be assigned. A technician whose license has lapsed for a type of work shouldn't be assignable to it. ## Estimate and invoice complex multi-phase projects **How do you handle progress billing and change orders in field service software?** Keep them on the work order. Multi-step work orders carry the milestones and progress billing for a project. A detailed price book holds materials and labor rate categories, so every phase prices from the same list. Change order management is tied to work order status. And project-level job costing tracks labor, materials and equipment across the whole job, not just each visit. Why do change orders leak when they live outside the work order? Because they're agreed in the field and recorded later. The person who approves the change is at the site, the person who bills it is at the office, and the only thing connecting them is a piece of paper or a text. If the change order is a record on the work order, it's billed with the work and can't quietly disappear. The related idea of pricing from one source is in [the price depends on which technician showed up](/articles/price-book-on-site-estimates-field-service), and the way work moves from request to payment is in [from request to paid](/articles/work-order-lifecycle-request-to-paid). ## Pricing electrical work from one book A commercial electrical estimate draws on a lot of line items: materials by the foot and the fixture, labor at different rates for different classifications of work, equipment, and the markup you apply to all of it. If each estimator keeps their own version of that list, two bids for similar work can differ by more than the work does. A detailed price book with materials and labor rate categories gives every estimate the same source. When the cost of copper or the rate for a classification changes, you change it once, and the next estimate reflects it. The full history of what prices were in effect when is there for the day someone asks why a job in March was priced the way it was. [The price book article](/articles/price-book-on-site-estimates-field-service) covers how that works. ## One project, from bid to final invoice Walk one commercial project through the system to see where the pieces meet. The estimate is built from the price book, with materials and labor priced by category, and approved by the customer. It converts to a multi-step work order, with the milestones that drive progress billing set on it. As phases complete, invoices are generated from the work logged against them, and the project's cost picture builds up in the background: labor, materials and equipment, phase by phase. Midway through, the customer asks for extra circuits. On site, the change is recorded against the work order and priced from the same list. It's approved on the device. The added work joins the queue, and the next progress invoice includes it. Nobody has to remember the conversation, because the record has it. At the end, the job's cost is visible against what was estimated, so the next bid can be sharper. Every step used the same record, which is why nothing had to be retyped. For how the work order carries a job from start to finish, see [from request to paid](/articles/work-order-lifecycle-request-to-paid). ## Safety-first operations Electrical work makes safety part of the process and not a separate program. Digital checklists cover pre-job hazard assessment. Incident reporting and corrective action workflows run on mobile. OSHA compliance tracking comes with automated training renewal alerts, so a lapsed safety training shows up before it matters. **Can technicians access arc flash and PPE protocols from the field?** Yes. Arc flash and PPE protocols are searchable from the field, and a safety protocol assistant answers from your own safety documentation. It brings up your documented lockout-tagout, arc flash and PPE requirements and doesn't produce a generic answer. That's the assistant described in [where AI actually changes a field service operation](/articles/ai-in-field-service-operations). ## One record from license to invoice The license record, the work order, the change order and the invoice share one data model. That's the reason a lapsed credential can affect an assignment, and the reason a change order agreed on site can be billed with the job. MangoApps Field Service Suite is built on that data model, inside the same platform as learning, HR and safety. For technicians, [the app they use](/articles/why-technicians-work-around-field-service-software) carries the work order, the checklist and the training in one place. ## Questions for any vendor Three demos are worth asking an electrical contractor's vendor to run live. 1. **Expire a license, then try to assign that technician** to work that requires it. 2. **Add a change order on a live work order** and show it on the next progress invoice with nothing retyped. 3. **Open a safety protocol from a technician's phone** and show that the answer comes from your documentation and not a generic source. A vendor that can't do the first has an alert system, not a compliance system. A vendor that can't do the second will leak change orders the way your paper process does. ## Where compliance and cash flow meet In a licensed trade, compliance and cash flow fail at the same seam: the hand-off between systems. A lapsed license and a lost change order are the same kind of error, a fact that didn't travel. Closing that seam is the point. [The six information gaps](/articles/six-information-gaps-field-service) is the general version of this argument, and [the twelve-question evaluation guide](/articles/how-to-evaluate-field-service-platform) is how to test any vendor against it. The [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide) includes a one-page breakdown of this trade alongside six others. You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### How do you track electrician licenses across multiple states? Track licensing per technician on the employee record, with renewal alerts ahead of each expiry, and connect that record to the dispatch board. Code training is delivered and recorded in the learning system, so the record reflects both the license and the training. Audit-ready version history shows what was recorded and when. ### Can field service software handle progress billing and change orders? Yes, when the work order can carry multiple steps. Milestone and progress billing sit on the work order, a price book supplies materials and labor rates, and change orders are tied to the work order's status. Project-level job costing then covers labor, materials and equipment across the whole project. ### How do technicians access safety protocols on site? Through the same app they use for the work order. Pre-job hazard checklists run on mobile, and arc flash and PPE protocols are searchable from the field. A safety protocol assistant can answer from your own safety documentation. ### Does an expired license block dispatch automatically? It should. When work types carry the credentials they require and licensing is tracked on the record the dispatch board reads, a technician with a lapsed license can't be assigned to work that requires it. When they renew, they become eligible again without a manual update. In MangoApps, work types carry the certifications they require, and a technician whose credential has lapsed cannot be assigned. The board says so at assignment. --- # We Just Bought an FSM Tool. Are You Asking Us to Throw It Away? **Author:** Andy Tolton **Published:** 2026-09-16 **Category:** field-services The FSM tool isn't the problem, the count of systems around it is. Three paths onto one platform, what stays, what migrates and what happens to your data. No. The fear behind the question is understandable. You've just finished implementing a field service management system, it took real effort, and the last thing you want is a vendor telling you to start over. The rip-and-replace fear is reasonable. It's also not what we're describing. A narrower question does more work: how many other systems are you also running? If the answer is five to eight, the field service tool isn't the problem. The count is. Below are the questions a skeptical buying group usually asks, in their own words, with direct answers. ## Frequently asked questions from teams that already own an FSM tool ### We just implemented a field service management system. Are you asking us to throw it away? No. The question to ask is how many other systems you run around it. If the answer is five to eight, you'd be replacing five tools with one, and dispatch is the part you'd notice least. The field service tool gets retired last, once everything around it already works. Nobody has to make that call at the start. It's a decision for month six, or year two, when you have evidence of how the rest of the platform performs. The context for why these tools are shaped the way they are is in [why field service software has been split down the middle for 20 years](/articles/field-service-software-split-down-the-middle). ### We only need work orders and invoicing today. Does this lock us into a platform? No. Start with one capability, in one population. Expanding later is a configuration and not a new implementation, because identity, employee data, permissions and integrations are already in place. The approach is to close your biggest gap first, skip what you don't need, and add the rest when you're ready. To choose which gap comes first, [the six information gaps](/articles/six-information-gaps-field-service) is the map. To see how a first phase is run, see [your first 90 days](/articles/field-service-implementation-first-90-days). ### Do we have to replace accounting, payroll and identity? No field service company replaces those in one project, in the middle of a season. There are three paths onto the platform, and every customer has taken one of them. #### Keep and connect Your accounting, payroll and identity systems stay put. Accounting and ERP systems (QuickBooks, Sage, NetSuite and others) sync in both directions, so invoices, payments and completed jobs move between them with no double entry. HR and payroll systems such as Workday, UKG, ADP, Paylocity, BambooHR and Rippling sync employee records, roles, time off and approved hours. Identity and access follow your existing directory through SSO and SAML, multi-factor authentication and role-based access. Over 200 other systems connect through connectors and an open API. #### Migrate when ready Not on day one, and not from zero. Customer and site records, contacts, access notes, open work orders, agreements and your price list can be migrated whenever you choose. #### Start net new For a company on paper, spreadsheets and a whiteboard, the platform is the system of record from day one, across the whole suite, without a second system to maintain. The principle underneath all three is the same: you connect each system once, to one platform, and not to every other tool you own. For an integration to be worth having, ask for the named systems that sync two ways and see one round trip. That's question nine in [our evaluation guide](/articles/how-to-evaluate-field-service-platform). ### Our technicians barely use the tools they have now. Why would this be different? Most field service software was designed for the office and shipped to the field as an afterthought. This was built the other way: large-button interfaces, voice-to-text, one-tap actions, no company email required, and the same app that carries the technician's schedule and payslip. MangoApps customers typically see 90%+ adoption within 90 days. If employees don't adopt after launch, you don't pay. The reasoning is in [why technicians work around the tools](/articles/why-technicians-work-around-field-service-software). ### Half our field workforce has no company email and no company device. Does that work? They need neither. The branded app installs on a personal phone, and onboarding is an invite by text message or a QR code. There's no directory entry, no VPN and no company hardware. It's the population the platform was built for. No password. No corporate email. ### How do we know the invoice reflects what actually happened on the job? There's only one record. Hours, parts, materials, photos and the signature are captured against the work order on site, and the invoice is generated from that record at price book rates and not retyped from paper. Nothing bills unreviewed, and nothing captured gets left off. [The work order lifecycle](/articles/work-order-lifecycle-request-to-paid) traces it step by step. ### Does our data, or our customers' data, train public AI models? No. Your data stays inside your boundaries and doesn't train public models. The platform works with OpenAI, Anthropic and Google Gemini, with automatic failover, and provider choice is a setting and not an architectural commitment. Every AI action is logged. Details are in [whose permissions does the AI inherit?](/articles/ai-governance-whose-permissions-does-the-ai-inherit). ### How does the AI know what it is not allowed to show someone? It inherits your permission model. A request runs as the person making it and can't return anything they couldn't already access. There's no separate AI permission structure to get wrong. The full explanation is in [the AI governance article](/articles/ai-governance-whose-permissions-does-the-ai-inherit), and [where AI actually changes a field service operation](/articles/ai-in-field-service-operations) covers what it's used for. ### Our work is seasonal. We double headcount in peak and halve it after. Recruiting, onboarding and training run on the phone, so a seasonal hire reaches their first job in days. When the season ends, records and certifications stay in place, so returning workers are reactivated and not re-onboarded. See [staffing a seasonal, licensed field workforce](/articles/seasonal-licensed-field-workforce). ### What happens to our data if we leave? Retention is configurable, GDPR data subject requests are supported, and records can be exported in an audit-ready, portable format whenever you ask. Your records are yours. ## How to count the systems around your FSM tool The whole argument turns on a number, so it's worth getting it right. List every system that touches a job or a technician. For most companies the list looks something like this: a work order and dispatch tool, a scheduling app or a whiteboard, invoicing and accounting software, a fleet tracking system, an employee communication tool or a group text, an HR and payroll system, a training or compliance system, and the spreadsheets that fill the gaps between them. Count each one, and note which of them a technician actually opens. The typical mid-sized company lands between five and eight, with each system carrying its own login, its own data model and its own mobile experience, or none. The point isn't that any one of them is wrong. It's that nothing connects them but people. ## What this looks like by role A platform decision is made by a group, and each person in that group is solving a different problem. It helps to say what each one gets. **Owner or general manager.** Cash arrives faster, because the invoice doesn't wait on paperwork. Recurring agreements schedule and bill themselves. **Operations manager.** Open versus completed work, days-to-invoice, estimate pipeline and completion time come from one data model, so the numbers agree with each other. **Dispatcher.** One board with every open job, every technician's workload and the maintenance that generated itself overnight. Lapsed credentials can't be assigned. **Field technician.** One app on the phone they already carry: work order, estimate, price book, signature, timesheet and company news in one place. No company email required. **Office and back office.** Invoices generate from completed work and sync with accounting, and exceptions surface before the run. **IT.** Fewer vendors, contracts, integrations and security reviews. One identity model, and HITRUST, SOC 2 Type II and ISO 27001 on one system. If your FSM tool already serves the dispatcher and the owner, that's the part you keep for now. The rest of the list is where the count comes from. ## A sequence for a company that just bought an FSM tool Here is how a team in that position would usually proceed. **First, count.** Use the list above and get to a real number. Include the systems nobody talks about. **Second, pick one gap.** Choose the one that costs the most, using [the six formulas](/articles/cost-of-disconnected-field-service-systems) if you can. If your dispatcher's biggest problem is a credential the board can't see, start there. If your technicians barely use the current tool, start with the phone. **Third, connect and don't replace.** Leave the FSM tool, accounting and payroll where they are. Let the platform read and write to them through connectors. **Fourth, expand when the first population is running.** Add the next capability, in the next population, because identity, employee data and permissions are already there. **Last, retire what's redundant.** When the FSM tool's work is being done around it, or in place of it, you decide whether to switch it off, on a date you pick. The FSM tool gets retired last, and nobody has to rush it. ## Why the platform decision is still the strategic one Identity, employee data, permissions and integrations are configured once, and every app you add inherits them instead of rebuilding them. You start with field service and expand whenever you're ready, with users, data and history carrying forward. There's no second implementation, no migration and no lost context. Every app you turn on is one fewer vendor to manage, one fewer contract, one fewer integration and one fewer security review. For a technician it's one fewer system to learn. MangoApps is The AI Platform for the Frontline Workforce. It's been built for that workforce for 18+ years, and Field Service Suite is one of the apps you can turn on within it. ## Start with one gap "You don't rip and replace" is a claim about sequencing, and the sequence is yours to set. Start with one gap. [The six information gaps](/articles/six-information-gaps-field-service) helps you pick it, and [the twelve-question guide](/articles/how-to-evaluate-field-service-platform) helps you evaluate what you're looking at, including us. These questions, plus the integration map, are also answered in the [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide). You can also see the [Field Service Suite](/apps/field-service-suite) itself. --- # Where frontline work breaks down between shifts **Author:** MangoApps Team **Published:** 2026-09-15 **Category:** mango-scoop Explore the shift handoff problem, compare frontline communication platforms, and see what's new in Recorder and AI Sheets workbooks. Hand-picked stories from MangoApps this week. ## Where Frontline Work Leaks: Fixing the Shift Handoff Problem ![Where Frontline Work Leaks: Fixing the Shift Handoff Problem](https://mango-cdn.b-cdn.net/images/blog-thumbnails/blog_689_20260913_140357.png) There is a moment at the end of every shift that most workforce software ignores. The outgoing supervisor knows three things: a ticket is still open on the machine in Bay 4, the storeroom order is... [Read the full story →](https://www.mangoapps.com/articles/where-frontline-work-leaks-fixing-the-shift-handoff-problem) --- ### More to read #### The Complete Guide to Frontline Communication Platforms in 2026 How enterprise buyers evaluate frontline communication platforms that also run scheduling, tasks, training, and HR self-service, and how ten leading platforms compare on HR and IT integration. [Read more →](https://www.mangoapps.com/articles/frontline-communication-platforms-guide) #### The Best Secure Communication Apps for Hospital and Frontline Healthcare Staff in 2026 How hospitals compare secure communication platforms for every employee on the floor, clinical and non-clinical, on HIPAA readiness, no-email access, acknowledgment, and fit with the EHR and HR systems in place. [Read more →](https://www.mangoapps.com/articles/best-healthcare-communication-apps-hospital-frontline-staff) #### The Complete Guide to Aligning Internal Communications, Training, and Operations Software in a Unified Digital Workplace Why communications, training, and operations tools drift apart, what the misalignment costs frontline enterprises, and how a unified digital workplace closes the gaps without another integration project. [Read more →](https://www.mangoapps.com/articles/aligning-communications-training-operations-software) #### The Complete Guide to Knowledge Base Software for SOP and Policy Management in Regulated Industries How compliance, operations, and L&D leaders give frontline employees instant access to the current SOP or policy on any device while keeping version control, acknowledgment, and audit evidence intact. [Read more →](https://www.mangoapps.com/articles/knowledge-base-software-sop-policy-management-regulated) --- ### What's New **General** — [Product Update - September 14, 2026](https://www.mangoapps.com/changelog/3141) * **[Recorder](https://www.mangoapps.com/key-features/mango-recorder)** — Capture your screen or camera in the desktop app, then share, transcribe, caption, and hand off recordi... **General** — [Product Update - September 13, 2026](https://www.mangoapps.com/changelog/3140) * **[AI Sheets: Workbook Tabs](https://www.mangoapps.com/directory/app/ai-sheets)** — Sheets are now workbooks: create, rename, reorder, and switch between multiple tabs, each w... --- # Whose Permissions Does the AI Inherit? **Author:** Andy Tolton **Published:** 2026-09-15 **Category:** field-services The AI should know your work orders and nothing the person asking can't see. Whose permissions it inherits decides whether it is governed or a liability. A technician asks the assistant a pricing question and gets back the margin on a job she was never supposed to see. Nobody meant for it to happen. The AI had broad access so that it could answer quickly, and it answered quickly. That's the failure this article is about, and it's more likely to happen by accident than through an attack. The AI in your field operation should know your price list, your work orders and your technicians. It should also know nothing the person asking isn't allowed to see. None of the uses of AI in [where AI actually changes a field service operation](/articles/ai-in-field-service-operations) is worth having if the AI is ungoverned, insecure or out of compliance. This is the article for the security reviewer, the CIO and the procurement team. ## The one question **How do you make sure AI doesn't show employees data they shouldn't see?** Ask one question of any vendor: whose permissions does the AI inherit? If the answer is anything other than the caller's own, the AI can surface data the person asking isn't allowed to see. That's the whole test. A separate permission model for AI is the wrong answer, even when it's built with the best intentions. It's a second set of rules, and a second set of rules drifts from the first. Someone changes a role in the HR system, and the AI's rules don't follow. Someone adds a new data source, and it's exposed before anyone thinks to restrict it. The right answer is plain. Every request runs as the person who made it. It can't return anything they couldn't already access. Every action is logged. There's no separate AI permission structure to get wrong. ## Governance is not only about reading Most talk about AI security is about what the AI can *read*. In an operation that dispatches licensed technicians, it's just as important what it can *do*. The platform should decline an assignment that a technician's credential doesn't support. That isn't a data-access rule. It's a constraint on the action. If the AI recommends a technician, it shouldn't recommend one whose credential doesn't cover the work. If a person tries to assign one manually, the board should say no. The detail is in [why an expired certification should block dispatch automatically](/articles/expired-certification-blocks-dispatch). Governance that only covers reading leaves the more consequential half open. ## The controls, plainly Here's what governed AI looks like in practice, without the jargon. **Rules for who sees what.** Role-based access, so the right assistants go to the right employees. Field technicians get field tools, dispatchers get operations tools and executives get analytics. No one sees what they shouldn't. **A record of what the AI was asked.** Sensitive customer and employee data is flagged automatically, prompts are logged and unusual activity is surfaced to administrators before it becomes a problem. **One place to see where AI is used.** Usage analytics show where AI is being adopted, which assistants produce value and where the gaps are, so AI ROI is measured and not assumed. **Your choice of model, with failover.** The platform uses OpenAI, Anthropic or Google Gemini, with automatic failover, so one vendor's outage doesn't take your AI offline. Which provider you use is a setting, not a re-platform. **Your data stays yours.** Your company's information never trains public models, and enterprise data stays inside your boundaries. Ask a vendor for each of those five, and ask them to show it. A control that can only be described is not the same as one that can be inspected. ## Certifications and deployment Security review teams look for the same things, and it's easiest to list them. **Certifications.** HITRUST CSF, SOC 2 Type II and ISO 27001, all on one unified system. FedRAMP ATO for U.S. public sector. HIPAA with a BAA. GDPR. **Deployment.** SaaS, Private Cloud, Customer VPC or On-Premise, with a 99.9% uptime SLA. **Tenancy.** Single-tenant architecture, so your data never co-mingles with another customer's. **Access and data controls.** SSO and SAML, multi-factor authentication, field-level role-based access, geo-fencing, data loss prevention, audit logs and eDiscovery. **What security certifications should an AI workforce platform have?** For a platform that holds employee records and customer data and puts AI in front of them, the three to look for together are HITRUST CSF, SOC 2 Type II and ISO 27001, held on the same system you'll be using and not across products acquired separately. Whether a vendor holds all three on one system is a factual question you can ask for evidence of. Confirm anything else your industry requires against your own compliance program. ## A test you can run in an afternoon Don't rely on a description. You can check the permission question yourself in a demo or a trial. Create two users with very different roles: a field technician and an executive, say. Ask the assistant the same question as each of them, one that touches data only the executive should see, such as margins or another team's records. The technician should get a refusal or an answer built only from what they could already open. Then ask for the log of both requests and confirm that both are in it, attributed to the person who asked. Next, ask what happens when the model provider is down. A vendor with failover can show you. Finally, ask for an assignment the technician's credentials don't support and see whether the platform declines it. Four checks, and none of them needs the vendor's help beyond a login. ## Who owns AI governance on your side A platform can enforce the rules, but someone has to decide them. In most field service companies, three people share the job. IT or security owns the permission model and the review of where data goes. The operations lead decides which assistants each role gets and what they're allowed to do. And a compliance or safety lead confirms that what the AI says about procedures matches what the company has approved. When those three agree on the rules up front, the platform just applies them. When they haven't met, the platform will apply whatever it was configured with on the first day, which is usually too permissive. It's worth a meeting before anything goes live. ## What happens to your data if you leave Procurement readers look for this and are often disappointed. It's worth asking a vendor early. Retention is configurable. Data subject requests under GDPR are supported. Records can be exported in an audit-ready format. Your records are yours, in a portable format, whenever you ask. ## Questions for any AI vendor A short list to bring to the next meeting: 1. Whose permissions does the AI inherit? 2. Where does a prompt go, and what is retained? 3. Does anything train a public model? 4. What happens when the model provider is down? 5. Can I see every action the AI took? 6. Can it decline an action, or only withhold information? The first is question eight, and certifications are question ten, in [the twelve-question evaluation guide](/articles/how-to-evaluate-field-service-platform). The rest are what to ask once a vendor has passed those. ## The AI you can audit is the AI you can expand Governance from day one is what lets the same platform put AI in front of the technician, the dispatcher and the controller without a separate review for each. The AI you can audit is the AI you can expand. MangoApps is The AI Platform for the Frontline Workforce. Field Service Suite runs on the same platform as the rest of it, so AI in the field inherits the permissions and the audit trail of the platform already in your security review. If you're in utilities or telecom, [this is the article to pair with the one on operations at scale](/articles/utilities-telecom-field-operations-platform). And if you're already running a field service tool, [the migration article](/articles/replace-fsm-tool-or-consolidate) explains how this fits with it. The [Field Service Management guide](https://www.mangoapps.com/resources/field-service-management-guide) also has the security and deployment summary in one place for your IT and procurement reviewers. You can also see the [Field Service Suite](/apps/field-service-suite) itself. ## Frequently asked questions ### How does the AI know what it is not allowed to show someone? It inherits your permission model. A request runs as the person making it and can't return anything they couldn't already access. There's no separate AI permission structure to keep in sync, so when a person's role changes, what the AI can show them changes too. ### Does MangoApps AI train on our data or our customers' data? No. Your company's information never trains public models, and enterprise data stays inside your boundaries. Every AI action is logged. ### Which AI models does the platform use, and what if one is down? The platform works with OpenAI, Anthropic and Google Gemini, with automatic failover, so one vendor's outage doesn't take your AI offline. Provider choice is a setting and not an architectural commitment. ### What certifications does the platform hold for AI and data security? HITRUST CSF, SOC 2 Type II and ISO 27001 on one unified system, plus a FedRAMP ATO for U.S. public sector, HIPAA with a BAA and GDPR. The platform can be deployed as SaaS, Private Cloud, Customer VPC or On-Premise. ### Can we export our data if we leave? Yes. Retention is configurable, GDPR data subject requests are supported, and records can be exported in an audit-ready, portable format whenever you ask. --- # Where Frontline Work Leaks: Fixing the Shift Handoff Problem **Author:** MangoApps Team **Published:** 2026-09-13 **Category:** operational-efficiency There is a moment at the end of every shift that most workforce software ignores. The outgoing supervisor knows three things: a ticket is still open on the machine in Bay 4, the storeroom order is... # Where Frontline Work Leaks: Fixing the Shift Handoff Problem There is a moment at the end of every shift that most workforce software ignores. The outgoing supervisor knows three things: a ticket is still open on the machine in Bay 4, the storeroom order is short two items, and the safety procedure the morning crew runs every day got updated last Tuesday. The incoming supervisor knows none of it — unless someone wrote it down, remembered to mention it, and the incoming person actually read it. Three conditions that all have to be true simultaneously. In a busy facility, at least one usually isn't. This is the handoff problem. It doesn't register on a dashboard as a red number. It shows up as a part that was never ordered, a check skipped because nobody knew the procedure had changed, a blocker re-reported three shifts later because no one tracked what happened to the original ticket. The cost is real. It just gets absorbed into "that's how operations work." Several of this week's releases address that assumption directly. --- ## The Shift-to-Shift Gap The most operationally significant release this week is [Frontline Passdown Follow-ups and Blocker Rechecks](https://www.mangoapps.com/changelog/3137). On the surface, it sounds incremental — shift passdowns already existed. What's new is what happens *after* a passdown is written. When a supervisor closes out their shift and logs a passdown, MangoApps now generates AI-drafted follow-up tasks tied to the open items in that note. The incoming manager doesn't receive a sentence that says "still working on this" — they receive a task, with context, ready to be reviewed and assigned. The manager approves the AI draft before anything gets assigned, which keeps humans in the decision seat while removing the friction of translating "note" into "action item" at the start of a busy shift. The blocker recheck piece is valuable in a different way. When an open issue is logged as a blocker with a linked service ticket, someone has to remember to follow up once that ticket closes. Usually, nobody does. The incoming crew inherits an item whose status has changed but whose resolution hasn't been acted on. Now, when the linked ticket closes, a recheck round fires automatically. The system holds the dependency so the shift supervisor doesn't have to. This matters because the end of a shift is the worst time to be generating paperwork. Supervisors are handing off a running facility to someone who needs to get up to speed in minutes. Every cognitive task that gets offloaded from that moment — drafting follow-ups, tracking open blockers — translates directly into fewer things that fall through. The AI-drafted task isn't just a convenience feature; it's a structural guarantee that the work a supervisor identified doesn't silently disappear when they clock out. --- ## When the Ticket Ends, the Work Is Just Beginning A parallel gap exists on the supply and maintenance side. A technician files a service ticket and requests a part. The request is logged. And then — in most systems — it sits in ambiguous territory. Did the warehouse see it? Was it pulled? Is the inventory count still accurate, or does it reflect a request that was never fulfilled? [Service Desk Parts Through Warehouse Fulfillment](https://www.mangoapps.com/changelog/3137) closes that loop structurally. When a technician adds a part to a service ticket, the request automatically routes to the warehouse pick queue. Inventory only moves in the system when a storekeeper physically picks the item — not when it's requested. For multi-site operations where stock accuracy drives purchasing decisions and downtime forecasts, this distinction matters considerably. Two related releases this week tighten adjacent seams. [Dynamic Option Lists in Service Desk forms](https://www.mangoapps.com/changelog/3138) let dropdown fields sync automatically from a spreadsheet, Google Sheet, CSV URL, or JSON API. When the source of truth for a vendor list, a location name, or a product code changes, the form updates automatically rather than presenting stale options or missing new ones. The data handoff between external systems and your intake forms stays current without anyone managing it. And with [Notify Others at Submission](https://www.mangoapps.com/changelog/3138), requesters can add colleagues directly to a ticket on the request form itself — so the right manager, teammate, or department head is looped in the moment the ticket is created, not after it has sat in someone's queue for two days. The follow-up email asking "did you see this?" is the symptom of a notification gap that now has a structural answer. --- ## The Knowledge That Doesn't Travel With the Work There is a third kind of handoff that is easier to miss: the knowledge handoff. It happens when an experienced employee returns to a procedure they have run dozens of times, confident they know how it works — unaware that it was updated three weeks ago. [SOP Version Change Summaries](https://www.mangoapps.com/changelog/3137) address this directly. When an employee returns to a procedure they previously completed, they now see a step-by-step diff showing exactly what changed since their last run. Not the whole document. Just the delta. The design choice here deserves attention. The alternative — requiring full recertification whenever a procedure changes — is common in regulated industries but costly at scale. Requiring employees to re-read the full document and identify changes on their own is unreliable, especially for long procedures with minor but safety-relevant updates. A version diff that appears automatically and surfaces only what is new threads the needle: the employee's time is respected, the change is visible, and nothing gets missed because the format made it easy to skim past. Finding the procedure in the first place is a separate problem. The [rebuilt Enterprise Search](https://www.mangoapps.com/changelog/3136) now returns ranked, semantic results across every MangoApps app alongside connections to Google Drive, Confluence, Jira, and ServiceNow. It includes an AI overview, expert surfacing for people search, and saved searches with email alerts. For organizations where institutional knowledge is scattered across a platform, a shared drive, and a legacy wiki, the ability to search once and retrieve from all of them changes how employees access what they need — particularly for the employee who needs to know whether the version they remember is still current. --- ## What Closed Loops Actually Give You Operations leaders frame reducing rework as a cost problem. It is a cost problem. But it is also a trust problem. When workers and managers learn that what they log actually travels forward — that a passdown generates a real task, that a parts request becomes a confirmed pick ticket, that an SOP change appears exactly where and when they need it — they trust the system enough to use it consistently. And consistent use is what creates the data quality that makes AI useful. AI-drafted passdown tasks work because the passdown data is reliable. Semantic search surfaces the right expert because the content is indexed consistently. Warehouse fulfillment closes correctly because the intake process captured the right information. None of these features deliver their full value in a fragmented environment where critical operational notes live in a group chat, parts requests disappear into an email thread, and the authoritative version of a procedure is anyone's guess. The releases this week are individually useful. But the pattern they trace is a platform systematically closing the gaps it had previously left open — not by adding more places to log things, but by ensuring what gets logged reaches the person who needs it, in the form they can act on, at the moment it matters. --- # The Best Secure Communication Apps for Hospital and Frontline Healthcare Staff in 2026 **Author:** MangoApps Team **Published:** 2026-09-08 **Category:** healthcare How hospitals compare secure communication platforms for every employee on the floor, clinical and non-clinical, on HIPAA readiness, no-email access, acknowledgment, and fit with the EHR and HR systems in place. > **Quick answer:** Hospitals use two kinds of secure communication apps. Clinical communication platforms such as TigerConnect, Vocera (Stryker), PerfectServe, Spok, Halo Health (symplr), and Epic Secure Chat carry protected health information between clinicians and tie into the EHR and paging. Workforce communication platforms such as MangoApps reach every hospital employee, including the majority who have no EHR login or corporate email, with targeted news, critical alerts with acknowledgment, schedules, policies, training, and two-way communication under HIPAA business associate terms. The best choice for frontline healthcare staff is usually one of each, evaluated on HIPAA and HITRUST posture, sign-in without corporate email, acknowledgment and audit records, shift handoff support, and integration with the EHR, HRIS, and scheduling systems already in place. A hospital with 6,000 employees issues 2,100 EHR logins. When the infusion-pump recall notice goes out through the clinical messaging platform on a Tuesday morning, the nurses and physicians see it within the hour. Environmental services, transport, food service, security, the float pool, and the clinic front desks do not see it at all, because they were never in the system that sent it. That is the shape of the hospital communication problem. It is not one problem but two, and buying one app for both is how most health systems end up with a gap they cannot see. The stakes are clinical and financial. The Joint Commission Center for Transforming Healthcare has estimated that [80% of serious medical errors involve miscommunication between caregivers during patient handoffs](https://www.hipaajournal.com/effects-of-poor-communication-in-healthcare/). Staff RN turnover averaged 16.4% in 2024 at an average cost of $61,110 per nurse, and each percentage point of RN turnover costs or saves the average hospital about $289,000 a year, according to the [NSI Nursing Solutions National Health Care Retention & RN Staffing Report](https://www.nsinursingsolutions.com/documents/library/nsi_national_health_care_retention_report.pdf). Only 23% of frontline workers believe they have access to the technology they need to be productive, according to [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html). This guide is for hospital IT, clinical operations, and communication leaders. It explains the two categories, what to evaluate, how ten platforms compare, how the categories work together in a hospital, the business case, and how to run the evaluation. ## What is a healthcare communication app, and why are there two kinds? A healthcare communication app is software that delivers secure, targeted communication to hospital and frontline healthcare staff on the devices they carry. There are two kinds because there are two audiences and two data types. Clinical communication and collaboration platforms carry protected health information (PHI) between clinicians about patients, and integrate with the electronic health record, nurse call, and paging. Workforce communication platforms carry organizational communication to every employee, clinical and non-clinical, and integrate with the HRIS, scheduling, learning, and policy systems. Clinicians need both. The other 60% or so of a hospital's workforce, in support, ancillary, and clinic roles, gets only the second, which is why its reach decides compliance for most of the building. | Dimension | Clinical communication platform | Workforce communication platform | Who needs which | |---|---|---|---| | Primary users | Physicians, nurses, allied clinicians | Every employee, clinical and non-clinical | Clinicians need both; support staff need the workforce platform | | Messages contain PHI | Yes, by design | Organizational communication; PHI handling governed by the BAA and policy | Clinical: PHI. Workforce: policy, safety, schedules, training | | EHR, nurse call, paging integration | Yes | Typically no | Clinical workflows | | Reach to staff without EHR login or corporate email | Limited | Yes | The majority of the workforce | | Targeted news and critical alerts with acknowledgment | Limited | Yes | Recalls, policy changes, code and weather events | | Schedules, tasks, training, HR self-service | No | Yes | Every employee, every shift | | Typical owner | CNIO, CMIO, clinical IT | Communications, HR, operations, IT | Both, jointly | Three definitions: **HIPAA** is the U.S. law that governs protected health information; a vendor complies with it through safeguards and a **business associate agreement (BAA)**, the contract that permits the vendor to handle PHI on the hospital's behalf. **HITRUST CSF** is a certification a vendor earns by having its controls assessed against a framework that incorporates HIPAA and other standards; it is evidence, not the law. ## What should hospitals evaluate in a secure communication app for frontline staff? | Criterion | Why it matters in a hospital | Verify in the demo | |---|---|---| | HIPAA readiness and a BAA | Any vendor that may touch PHI must sign one | Ask for the BAA and the vendor's PHI-handling statement | | Published certifications | HITRUST CSF, SOC 2 Type II, ISO 27001 are what your InfoSec team recognizes | Current certificates, not badges | | Sign-in without corporate email and shared-device support | Most support staff have neither an EHR login nor an inbox; units use shared devices | Sign in as an environmental services technician on a unit kiosk | | Critical alerts with mandatory acknowledgment and audit export | Recalls, code events, policy changes need proof of receipt by role and unit | Send a recall alert to a floor; show acknowledgment by role; export it | | Shift handoff and huddle support | Handoff miscommunication is the leading error pattern | Show a pre-shift huddle post and a handoff checklist | | Integrations | EHR and paging for clinical; HRIS, scheduling, LMS, Microsoft 365 for workforce | Name the systems; show identity provisioned from the HRIS | | Translation and accessibility | Multilingual support workforces | Read a policy in Spanish on a phone | | Analytics by unit, shift, and site | Averages hide the units that never saw the notice | Filter acknowledgment by unit and shift | For scheduling specifically, see [The Schedule a Charge Nurse Can Actually Trust](https://www.mangoapps.com/articles/the-schedule-a-charge-nurse-can-actually-trust). ## Best communication apps for hospital and frontline healthcare staff compared The ten platforms below are the ones hospitals shortlist most often, across both categories and the collaboration suites that sit between them. | Platform | Category | PHI messaging | Reaches staff without EHR login or corporate email | Critical alerts with acknowledgment and audit export | Schedules, tasks, training, HR on the same platform | HIPAA BAA | HITRUST published | Best for | |---|---|---|---|---|---|---|---|---| | [MangoApps](https://www.mangoapps.com/industries/healthcare) | Workforce communication platform | Governed by the BAA and policy (confirm scope with vendor) | Yes | Yes | Yes, native | Yes | Yes (HITRUST CSF) | Every hospital employee, clinical and non-clinical, on one app | | [TigerConnect](https://tigerconnect.com/) | Clinical communication and collaboration | Yes | Limited | Vendor-stated | No | Yes (vendor-stated) | Vendor-stated | Clinician messaging with EHR and nurse-call integration | | [Vocera (Stryker)](https://www.vocera.com/) | Clinical communication, hands-free devices | Yes | Limited | Vendor-stated | No | Yes (vendor-stated) | Vendor-stated | Hands-free clinical voice and alarms at the bedside | | [PerfectServe](https://www.perfectserve.com/) | Clinical communication and scheduling | Yes | Limited | Vendor-stated | Provider scheduling | Yes (vendor-stated) | Vendor-stated | Physician communication and on-call scheduling | | [Spok](https://www.spok.com/) | Clinical communication and paging | Yes | Limited | Vendor-stated | No | Yes (vendor-stated) | Vendor-stated | Enterprise paging and clinical alerting | | [Halo Health (symplr)](https://www.symplr.com/) | Clinical communication | Yes | Limited | Vendor-stated | No | Yes (vendor-stated) | Vendor-stated | Role-based clinical messaging | | Epic Secure Chat ([Epic](https://www.epic.com/)) | EHR-native messaging | Yes | No (EHR users only) | Not published | No | Covered by the Epic agreement | Not applicable | Clinicians already in Epic | | [Microsoft Teams](https://www.microsoft.com/en-us/microsoft-teams/healthcare) (healthcare) | Collaboration suite | Under Microsoft's BAA (vendor-stated) | Partial (licensing) | Partial | Teams Shifts | Yes (vendor-stated) | Not published as a HITRUST-certified product | Microsoft 365-standardized health systems | | [Beekeeper (LumApps)](https://www.beekeeper.io/) | Frontline workforce communication | Vendor-stated | Yes | Vendor-stated | Forms and workflows | Vendor-stated | Not published | Frontline-only communication | | [Staffbase](https://staffbase.com/) | Employee communications platform | Vendor-stated | Partial | Partial (vendor-stated) | Via integration | Vendor-stated | Not published (ISO 27001, SOC 2 Type II published) | Communications teams at large health systems | *Capability and certification statements for third-party vendors are taken from each vendor's public documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps. "Not published" means the pages reviewed did not disclose it. Clinical platforms are compared here because hospitals evaluate them alongside workforce platforms; they serve a different audience and data type.* ### MangoApps MangoApps is the AI Platform for the Frontline Workforce, and in a hospital it is the platform for every employee: physicians and nurses alongside environmental services, food service, transport, security, clinic staff, and the float pool. One branded app carries targeted news and Critical Alerts with mandatory read receipts and audit trails, schedules and shift swaps, tasks and rounding checklists, policies and SOPs with AI search, training and credential tracking, and HR self-service, with no corporate email or EHR login required. MangoApps holds HITRUST CSF (which incorporates HIPAA), SOC 2 Type II, ISO 27001, and FedRAMP ATO, offers HIPAA business associate agreements, and deploys as SaaS, Private Cloud, Customer VPC, or On-Premise, with audit logs, eDiscovery, legal hold, and retention, per [mangoapps.com/security](https://www.mangoapps.com/security). Healthcare customers include [TeamHealth](https://www.mangoapps.com/resources/teamhealth-case-study), [Benchmark Human Services](https://www.mangoapps.com/customers/benchmark-human-services) (4,000+ employees, caregivers in client homes without corporate email), OU Health (87% workforce engagement within months of launching an app that required neither corporate email nor VPN), and Columbia Basin Health Association (more than 90% monthly engagement). **Key consideration:** MangoApps is the workforce platform in the pair; where clinicians need PHI messaging integrated with the EHR and nurse call, hospitals run a clinical communication platform alongside it. **Pricing:** modular suites, quote-based. ### TigerConnect A clinical communication and collaboration platform for secure clinician messaging, with EHR, nurse-call, and scheduling integrations (vendor-stated). **Best for:** care-team messaging carrying PHI. **Key consideration:** built for clinicians; non-clinical staff and organizational communication need a workforce platform. **Pricing:** quote-based. ### Vocera (Stryker) Hands-free clinical communication badges and smartphone apps with alarm and alert routing at the bedside (vendor-stated). **Best for:** nursing units where hands-free voice matters. **Key consideration:** device-centric; reach to support staff and organizational communication is limited. **Pricing:** quote-based, hardware plus software. ### PerfectServe Clinical communication paired with provider scheduling and on-call management (vendor-stated). **Best for:** physician communication and on-call routing. **Key consideration:** provider-focused; workforce communication and non-clinical schedules need another platform. **Pricing:** quote-based. ### Spok Enterprise healthcare communications with paging, clinical alerting, and directory (vendor-stated). **Best for:** health systems standardizing paging and alert routing. **Key consideration:** clinical alerting rather than organizational communication. **Pricing:** quote-based. ### Halo Health (symplr) Role-based clinical communication within the symplr operations portfolio (vendor-stated). **Best for:** role-based clinical messaging with symplr provider data. **Key consideration:** clinical audience. **Pricing:** quote-based. ### Epic Secure Chat Messaging inside the Epic EHR for Epic users. **Best for:** clinicians already in Epic all shift. **Key consideration:** reaches only staff with EHR logins; no organizational communication, acknowledgment, or non-clinical reach. **Pricing:** part of the Epic relationship. ### Microsoft Teams for healthcare The Microsoft 365 collaboration suite with healthcare features and Teams Shifts, under Microsoft's BAA (vendor-stated). **Best for:** Microsoft 365-standardized health systems whose staff hold licenses. **Key consideration:** frontline reach depends on licensing; acknowledgment and signage are not native. **Pricing:** Microsoft 365 licensing. ### Beekeeper (LumApps) A frontline-first communication platform with streams, chat, translation, and no-code forms, reaching staff without corporate email (vendor-stated); [acquired by LumApps in July 2025](https://www.lumapps.com/insights/news/lumapps-and-beekeeper-to-join-forces-creating-the-leading-employee-experience-platform-for-the-future-of-work). **Best for:** frontline-only communication programs. **Key consideration:** schedules, training, and HR self-service via integration; verify healthcare certifications. **Pricing:** tiered, quote-based. ### Staffbase An enterprise communications platform with multichannel publishing and Microsoft 365 depth; ISO 27001 and SOC 2 Type II published on [staffbase.com/security](https://staffbase.com/security). **Best for:** communications teams at large health systems. **Key consideration:** frontline sign-in depends on configuration; acknowledgment and records lighter than a system of engagement built for regulated work; HITRUST not published. **Pricing:** enterprise, quote-based. ## How the two categories work together in a hospital | Moment | Who must receive it | Clinical communication platform | Workforce communication platform | Record that exists | |---|---|---|---|---| | Code or rapid response | The care team | Yes | No | Clinical log | | Infusion-pump recall | Every employee who touches the device, clinical and non-clinical | Clinicians only | Everyone, with acknowledgment by role and unit | Acknowledgment export | | Policy change (visitor policy, PPE) | Every employee | Clinicians only, informally | Everyone, with mandatory read and training assignment | Acknowledgment plus training completion | | Shift handoff | The oncoming and outgoing care team | Yes (PHI) | Huddle post and checklist (no PHI) | Both | | Schedule change | The affected staff | Provider scheduling in some platforms | All staff, with swaps and approvals | Schedule audit | | Onboarding a new aide | The new hire and manager | No | Day-one access, training, policies | Completion record | | Survey after a unit incident | The unit | No | Pulse survey by unit | Results by unit | The pattern is consistent: clinicians get both, and the majority of the workforce gets only the workforce platform. That is why the reach of the workforce platform decides compliance for most of the hospital, and why "communication app for hospital staff" is a two-part answer. ## The business case: turnover, safety, and reach | Outcome | Data | Source | |---|---|---| | Nurse turnover | Staff RN turnover 16.4% in 2024; $61,110 average cost per nurse; $289,000 per percentage point for the average hospital | [NSI Nursing Solutions](https://www.nsinursingsolutions.com/documents/library/nsi_national_health_care_retention_report.pdf) | | Handoff safety | An estimated 80% of serious medical errors involve miscommunication during patient handoffs | [Joint Commission Center for Transforming Healthcare](https://www.hipaajournal.com/effects-of-poor-communication-in-healthcare/) | | Frontline burnout and attrition | 53% of deskless workers feel burned out; 43% are actively looking | [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) | | Replacement cost, all roles | One-half to two times annual salary | [Gallup](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) | | Engagement | 20% of employees engaged globally; ≈$10 trillion cost of low engagement | [Gallup](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) | | Technology gap | 23% of frontline workers have the technology they need | [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html) | For the retention and burnout context, see [How to Reduce Nurse Turnover](https://www.mangoapps.com/articles/how-to-reduce-nurse-turnover), [Reducing Burnout in Healthcare](https://www.mangoapps.com/articles/reducing-burnout-in-healthcare), and [Signs of Physician Burnout and How to Measure Them](https://www.mangoapps.com/articles/signs-of-physician-burnout-how-to-measure-them). ## How to run the evaluation 1. **"Send a recall alert to every employee on the third floor, clinical and non-clinical, and show acknowledgment by role."** Strong: one send, acknowledgment by role and unit, exportable. Weak: "clinicians will see it in the EHR." 2. **"Sign in as an environmental services technician with no email on a unit kiosk."** Strong: two minutes, HRIS-provisioned. Weak: IT creates the account. 3. **"Show the BAA and the current HITRUST certificate."** Strong: both, dated. Weak: "we are HIPAA compliant." 4. **"Show the audit export for a policy acknowledgment."** Strong: per employee, per version. Weak: an opens count. 5. **"Show how the app coexists with our clinical messaging platform and Epic."** Strong: a clear division of PHI and organizational communication, with identity from the HRIS. Weak: "we replace them." 6. **"Show a pre-shift huddle post and a handoff checklist on a phone."** Strong: templated, by unit. Weak: a PDF. 7. **"Show a policy change that assigns training and records completion on the employee record."** Strong: same platform. Weak: a link to the LMS. 8. **"Which integrations are native: HRIS, scheduling, LMS, Microsoft 365?"** Strong: named systems, vendor-maintained. Weak: "we have an API." Run a 30-day pilot on two units including support staff, and measure acknowledgment rate by role and unit on one real notice. ## Where MangoApps fits MangoApps is the AI Platform for the Frontline Workforce, and for hospitals it is one app for every employee: clinical, allied, and support, with no corporate email or EHR login required. Critical Alerts deliver recalls, code and weather events, and policy changes with mandatory acknowledgment and audit trails by role and unit. Schedules, shift swaps, rounding checklists, policies and SOPs with AI search, training and credential tracking, and HR self-service run on the same platform, so a policy change, the training it requires, and the checklist it updates appear on one employee record. MangoApps holds HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO, signs HIPAA business associate agreements, and deploys as SaaS, Private Cloud, Customer VPC, or On-Premise. Healthcare customers include TeamHealth, Benchmark Human Services, OU Health, Columbia Basin Health Association, and Marion Health. Where clinicians need PHI messaging integrated with the EHR, MangoApps runs alongside the clinical communication platform and covers the rest of the hospital. Learn more on the [MangoApps healthcare page](https://www.mangoapps.com/industries/healthcare), and see [Build a HIPAA-Compliant Intranet for Healthcare](https://www.mangoapps.com/articles/how-to-build-a-hipaa-compliant-intranet-for-your-health-system) for the compliance foundation. ## Frequently asked questions **What are the best communication apps for hospital and frontline healthcare staff?** Hospitals use two kinds. Clinical communication platforms (TigerConnect, Vocera, PerfectServe, Spok, Halo Health, Epic Secure Chat) carry protected health information between clinicians. Workforce communication platforms (MangoApps, with Beekeeper and Staffbase as communication-first alternatives) reach every employee, including the majority without an EHR login or corporate email, with alerts, acknowledgment, schedules, policies, and training. Most hospitals run one of each. Third-party statements are vendor-stated. **What is the difference between a clinical communication platform and a workforce communication platform?** A clinical platform carries PHI between clinicians and integrates with the EHR, nurse call, and paging. A workforce platform carries organizational communication to every employee and integrates with the HRIS, scheduling, learning, and policy systems. Clinicians need both; support staff need the workforce platform. **Do hospital communication apps need to be HIPAA compliant, and what does HITRUST add?** Any vendor that may handle PHI must sign a business associate agreement and maintain HIPAA safeguards. HITRUST CSF is a certification that provides third-party evidence those controls exist. MangoApps holds HITRUST CSF and signs BAAs; verify certificates for every vendor. **Can hospital employees without an EHR login or corporate email use these apps?** On workforce platforms that provision identity from the HRIS and support sign-in by SMS, QR code, or employee ID on a personal phone or unit kiosk, yes. Clinical platforms and Epic Secure Chat are built for staff with clinical system logins. **How do communication apps support shift handoffs and huddles?** Clinical platforms carry patient-specific handoff communication with PHI. Workforce platforms carry pre-shift huddle posts, handoff checklists, and acknowledgment without PHI, and connect them to the schedule. **Which hospital communication apps integrate with Epic, Microsoft 365, and the HRIS?** Clinical platforms integrate with Epic and other EHRs (vendor-stated). MangoApps integrates with Microsoft 365 and HRIS systems including Workday, UKG, and ADP among 200+ integrations, and coexists with clinical messaging platforms. Ask each vendor which integrations are native. **How do you prove that a recall or policy notice reached every employee?** With critical alerts that require acknowledgment attributed to the employee's HRIS identity and the notice version, escalated to the manager when missing, reported by role and unit, and exportable for audit. ## Sources - Joint Commission Center for Transforming Healthcare, hand-off communications research, as summarized by [HIPAA Journal](https://www.hipaajournal.com/effects-of-poor-communication-in-healthcare/) - NSI Nursing Solutions, [National Health Care Retention & RN Staffing Report](https://www.nsinursingsolutions.com/documents/library/nsi_national_health_care_retention_report.pdf) (2025 edition figures; confirm against the current edition) - Deloitte, [Frontline Worker Productivity Enabled by Technology](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html) - BCG, [Facing the Deskless Labor Shortage with Technology](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) (2024) - Gallup, [State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx); [This Fixable Problem Costs U.S. Businesses $1 Trillion](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) (2019) - LumApps, [LumApps and Beekeeper to Join Forces](https://www.lumapps.com/insights/news/lumapps-and-beekeeper-to-join-forces-creating-the-leading-employee-experience-platform-for-the-future-of-work) (July 2025) - Vendor pages: [MangoApps security](https://www.mangoapps.com/security), [MangoApps healthcare](https://www.mangoapps.com/industries/healthcare), [Staffbase security](https://staffbase.com/security) --- # The Complete Guide to Aligning Internal Communications, Training, and Operations Software in a Unified Digital Workplace **Author:** Andy Tolton **Published:** 2026-09-08 **Category:** integrated-digital-workplace Why communications, training, and operations tools drift apart, what the misalignment costs frontline enterprises, and how a unified digital workplace closes the gaps without another integration project. > **Quick answer:** Communications, training, and operations software are hard to align because each was bought for a different owner, holds its own copy of the employee record, uses its own identity and permissions, and measures a different thing. The result is a policy announced in one tool, trained in a second, and executed in a third, with no single record that the same employee did all three. Integrations connect the tools but do not unify the record. A unified digital workplace fixes alignment by running communication, training, and operations on one identity, one employee record, one permission model, and one governance layer, so a message, the training it requires, and the task it triggers are visible as one timeline. A food-safety procedure changes on a Monday. Corporate announces it in the communications platform. The course goes live in the learning system on Wednesday. The daily checklist changes in the operations tool on Friday. On Saturday the district manager cannot tell which of her 14 stores did all three, because no system knows the other two exist. None of the three tools is broken. Each does its job. The gap is between them, and it is structural, not a training problem. The numbers describe the structure. The average company runs 101 applications, and companies with more than 5,000 employees average 131, according to [Okta's Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/). A [Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) study found workers toggling between applications and websites roughly 1,200 times a day, about four hours a week spent reorienting. Only 23% of frontline workers believe they have access to the technology they need to be productive, and the right mix of tools lifts their productivity about 22%, according to [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html). This guide is for IT, learning, and operations leaders who own three stacks that were supposed to be one. It explains why the tools drift apart, the seven causes of misalignment, what misalignment costs, why integrations alone do not fix it, what alignment looks like in a unified digital workplace, and how to get there without a rip-and-replace. ## What makes it hard to align communications, training, and operations software? Four structural reasons, each of which would be enough on its own. **Separate buyers.** Communications was bought by internal comms, the learning system by L&D, the operations tool by ops. Three budgets, three roadmaps, three vendors, none accountable for the seams. **Separate employee records and identity.** Each tool holds its own copy of who works where. When a store manager changes roles, three records change on three schedules, or do not. **Separate permission and governance models.** Who can publish, who can assign, who can see what: defined three times, enforced three ways, audited nowhere as a whole. This is also why AI cannot be turned on safely across the three; see [Why Fragmented Tools Break Enterprise AI](https://www.mangoapps.com/articles/why-fragmented-tools-break-enterprise-ai). **Separate metrics.** Comms measures opens, L&D measures completions, ops measures tasks closed. Nobody measures whether the change happened. | Dimension | Communications tool | Learning system | Operations tool | What alignment requires | |---|---|---|---|---| | Owner | Internal comms | L&D | Operations | One accountable owner for the employee experience | | Employee record | Its own | Its own | Its own | One record from the HRIS | | Identity | Corporate email, often | LMS login | Ops login | One identity, including employees with no email | | Permissions | Publisher roles | Course admin roles | Task admin roles | One permission model | | Frontline reach | Partial | Desktop-first | Varies | Every employee on the device they carry | | Metric | Opens | Completions | Tasks closed | The change completed, per employee, per site | ## Why do internal communications, training, and operations tools become disconnected at work? They drift apart because they were bought one urgent problem at a time. A safety incident buys a communication tool. An audit finding buys a learning system. A store-execution problem buys a task tool. Each vendor optimizes its own workflow and treats the others as integration targets. Nobody designs the stack; it accumulates. The frontline makes the drift permanent. Communications and operations tools may reach the floor; the learning system usually assumes a desktop. When PetSmart looked at its own numbers, it found that about 80% of its 55,000 employees largely did not have access to company communications. Integrations get added, but as links between tools, not as a shared record, so a completed course never appears beside the acknowledged policy or the closed task. [Why Enterprise Workforce Integration Fails](https://www.mangoapps.com/articles/why-enterprise-integration-fails-without-a-unified-app) describes this checkbox problem in detail. Then AI arrives and cannot act across the boundaries. An assistant that can read the policy cannot see whether the training was completed or the task closed, because those live behind different permissions in different systems. Fragmentation stops being a productivity tax and becomes a liability; that is the argument of [Why Fragmented Tools Break Enterprise AI](https://www.mangoapps.com/articles/why-fragmented-tools-break-enterprise-ai). ## Seven common causes of misalignment between communications, training, and operations software ### 1. Three identities for one employee **Spot it:** the same person is "j.rivera" in comms, employee 40231 in the LMS, and a phone number in the ops tool. **Fix:** identity driven from the HRIS across all three, so a role change or termination propagates once. ### 2. The frontline has an account in one tool, or none **Spot it:** the learning system has 2,000 licenses for a 9,000-person workforce. Deskless workers are 70 to 80% of the global workforce ([BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology)) and 58% of American workers are on the frontline ([JLL](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention)). **Fix:** sign-in without corporate email, on the employee's own phone or a shared device, for every layer. ### 3. A policy change does not trigger training or a task **Spot it:** the SOP changed in March; the course was updated in May; the checklist never changed. **Fix:** event-driven workflows in which a policy version change assigns the training and updates the task, automatically. ### 4. Completion lives in the LMS, acknowledgment in comms, execution in ops, and no one joins them **Spot it:** the audit request for "who read, trained, and executed the new procedure" takes three exports and a spreadsheet. **Fix:** one employee record that holds acknowledgment, completion, and execution. ### 5. Managers get three dashboards and act on none **Spot it:** the store manager has a comms analytics login she has never used, an LMS report she cannot filter to her store, and an ops dashboard she checks hourly. **Fix:** one manager view by site that shows who has not acknowledged, who has not completed, and what is not done. ### 6. Each tool has its own permission model, so AI cannot be turned on safely **Spot it:** the AI pilot was blocked because nobody could say which documents it would read. **Fix:** one permission model that AI inherits; see [AI Grounded in Work, Not Bolted On as a Chatbot](https://www.mangoapps.com/articles/ai-grounded-in-work). ### 7. Metrics measure the tool, not the outcome **Spot it:** the comms report says 71% opened; nobody knows how many stores completed the change. **Fix:** measure the completed change per employee and per site, and report the three layers together. ## What misalignment costs | Cost | Evidence | |---|---| | Time lost to switching and searching | Roughly 1,200 app toggles a day, about four hours a week reorienting ([Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications)) | | Application sprawl | 101 applications per company; 131 at 5,000+ employees ([Okta](https://www.okta.com/newsroom/articles/businesses-at-work-2025/)) | | Under-equipped frontline | 23% of frontline workers have the technology they need; the right mix lifts productivity ~22% ([Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html)) | | Disengagement and attrition | 20% of employees engaged globally; ≈$10 trillion cost ([Gallup](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx)); 53% of deskless workers burned out, 43% looking ([BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology)) | | Turnover | Replacing an employee costs one-half to two times annual salary ([Gallup](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx)) | | Compliance exposure | When acknowledgment, training, and execution cannot be shown as one record, the control cannot be evidenced ([Why Workforce Records Fail When Audits Actually Happen](https://www.mangoapps.com/articles/why-workforce-records-fail-when-audits-actually-happen)); regulators have fined firms $1.1 billion (2022) and $392.75 million (2024) for communications that escaped approved, retained channels ([SEC](https://www.sec.gov/news/press-release/2022-174), [SEC](https://www.sec.gov/news/press-release/2024-98)) | | Safety | In healthcare, an estimated 80% of serious medical errors involve miscommunication during handoffs ([Joint Commission Center for Transforming Healthcare](https://www.hipaajournal.com/effects-of-poor-communication-in-healthcare/)) | The coordination cost on the floor is described in [The Hidden Coordination Tax in Frontline Operations](https://www.mangoapps.com/articles/hidden-coordination-tax-frontline-operations). ## Why integrations alone do not fix it An integration moves data between two records. It does not make them one record. After the integration, the learning system still holds its own copy of the employee, the communications tool still holds its own, and the two disagree the day after a transfer. The integration tax is paid by IT forever: a native connector maintained by the vendor is the cheapest kind, an API mapping your team maintains is the common kind, and a partner build nobody maintains is the kind that breaks in year two. The frontline gap is the other reason. Integration layers are typically built on SharePoint, Workday, and ServiceNow, and they work for the employees who have accounts in those systems. The other 70 to 80% keep operating through text messages, printed schedules, and verbal instructions. [Why Enterprise Workforce Integration Fails](https://www.mangoapps.com/articles/why-enterprise-integration-fails-without-a-unified-app) makes this case, and the integration checklist in [The Complete Guide to Frontline Communication Platforms](https://www.mangoapps.com/articles/frontline-communication-platforms-guide) shows what to ask for. ## What alignment looks like in a unified digital workplace The test is simple to state: one identity, one employee record, one permission model, one governance layer, across communication, training, and operations. [What "Platform" Should Actually Mean](https://www.mangoapps.com/articles/what-platform-means) sets out the test in full. Run the food-safety change through it. | Moment | Fragmented stack | Unified digital workplace | |---|---|---| | Monday: procedure changes | Comms publishes; nobody else knows | The SOP version changes once; the announcement, the training assignment, and the checklist update are generated from it | | The associate with no email | Never sees the announcement | Sees it on her phone, in her language, and confirms she read it | | Wednesday: training | Assigned in the LMS to the 2,000 with licenses | Assigned by role to everyone the SOP applies to; completion writes to the same record | | Friday: checklist | Updated in the ops tool by hand | Already updated from the SOP change; photo proof required | | Saturday: the district manager | Three dashboards, no answer | One view: which stores acknowledged, trained, and executed | | The auditor | Three exports and a spreadsheet | One timeline per employee and per store | | The AI assistant | Blocked | Answers "which stores completed all three?" because it sees one record with one permission model | ## How to move from fragmented to aligned without a rip-and-replace 1. **Inventory the three stacks and the employee records they hold.** Count the identities per employee and the licenses per layer against headcount. The gap between LMS licenses and headcount is usually the frontline. 2. **Pick the identity anchor.** The HRIS stays the system of record. Everything else provisions from it. [We Already Have UKG. Do We Have to Replace It?](https://www.mangoapps.com/articles/we-already-have-ukg-do-we-have-to-replace-it) covers the keep-it case. 3. **Choose the platform that will hold the shared record and reach the frontline.** It must sign in employees without corporate email and carry communication, training, and operations on one permission model. [Why the Platform Decision Comes Before the App Decision](https://www.mangoapps.com/articles/platform-decision-first) explains the order. 4. **Migrate one workflow end to end as the pilot.** A policy change is ideal: announcement, acknowledgment, training, task, record. Measure time-to-complete across all three layers, by site. 5. **Retire tools as workflows move.** Count applications retired, and hold vendors to the number. Measure three things: applications retired, time to complete a change across all three layers, and frontline weekly active users by site. [Seven Things That Only Happen When Work Runs on One Platform](https://www.mangoapps.com/articles/seven-things-one-work-platform) describes what the end state looks like in practice. ## Where MangoApps fits MangoApps is the AI Platform for the Frontline Workforce. It runs communication, knowledge, training, scheduling, tasks, and HR self-service on one identity and one employee record, for frontline and desk employees, with no corporate email required. A policy change generates the announcement with acknowledgment, the training assignment by role, and the task update from one source, and the district manager sees all three on one view. MangoApps AI is grounded in that record and inherits its permissions. The HRIS stays the system of record through 200+ out-of-the-box integrations, including Workday, UKG, ADP, and SAP SuccessFactors. Every deployment is backed by the [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee): 90%+ active adoption within 90 days. ## Frequently asked questions **What makes it hard to align communications, training, and operations software?** Separate buyers, separate employee records and identities, separate permission models, and separate metrics. Each tool was bought for a different owner and holds its own copy of the employee, so a policy announced in one tool, trained in a second, and executed in a third leaves no single record that the same employee did all three. **Why do internal communications, training, and operations tools become disconnected at work?** Because they were bought one urgent problem at a time, each vendor optimizes its own workflow, the frontline never receives an account in two of the three, and integrations are added as links rather than a shared record. AI then cannot act across the boundaries. **What are the most common causes of software misalignment at work?** Three identities for one employee; frontline staff with an account in one tool or none; policy changes that do not trigger training or tasks; completion, acknowledgment, and execution stored apart; managers with three dashboards; permission models AI cannot safely inherit; and metrics that measure the tool rather than the outcome. **Can integrations fix misaligned communications, training, and operations tools?** Integrations move data between records; they do not unify the record or the permission model, and they carry a maintenance cost. They also tend to serve employees who already have accounts in the connected systems, leaving the frontline out. **What is a unified digital workplace?** A platform on which communication, training, operations, and HR workflows run on one identity, one employee record, one permission model, and one governance layer, reaching every employee including those without corporate email. **How do you align tools for frontline employees who have no corporate email?** Provision identity from the HRIS, let employees sign in by SMS or QR code on a personal phone or shared device, and put communication, training, and tasks in that one app so the change reaches them as one experience. **How long does it take to consolidate communications, training, and operations onto one platform?** Start with one workflow end to end, typically a policy change, as a 60 to 90 day pilot at a few sites, then expand by region and retire tools as workflows move. The HRIS does not need to be replaced. ## Sources - Okta, [Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/) - Harvard Business Review, [How Much Time and Energy Do We Waste Toggling Between Applications?](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) (2022) - Deloitte, [Frontline Worker Productivity Enabled by Technology](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html) - BCG, [Facing the Deskless Labor Shortage with Technology](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) (2024) - JLL, [Leading practices for frontline workforce engagement and retention](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention) (2025) - Gallup, [State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx); [This Fixable Problem Costs U.S. Businesses $1 Trillion](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) (2019) - U.S. Securities and Exchange Commission, press releases [2022-174](https://www.sec.gov/news/press-release/2022-174) and [2024-98](https://www.sec.gov/news/press-release/2024-98) - Joint Commission Center for Transforming Healthcare, hand-off communications research, as summarized by [HIPAA Journal](https://www.hipaajournal.com/effects-of-poor-communication-in-healthcare/) --- # The Complete Guide to Knowledge Base Software for SOP and Policy Management in Regulated Industries **Author:** Andy Tolton **Published:** 2026-09-08 **Category:** knowledge-management How compliance, operations, and L&D leaders give frontline employees instant access to the current SOP or policy on any device while keeping version control, acknowledgment, and audit evidence intact. > **Quick answer:** Knowledge base software for SOPs and policies in a regulated industry has to do two things at once: give a frontline employee the current procedure in seconds, on a phone or shared device, in their language, and prove to an auditor that the procedure was controlled, versioned, acknowledged, and read by the people it applied to. Evaluate platforms on findability (AI search that returns the answer and its source), control (owners, versions, effective dates, approval workflows), acknowledgment (a mandatory read tied to a version), audit evidence (exportable records and retention), and frontline access without corporate email. MangoApps runs knowledge, acknowledgment, training, and communication on one platform for frontline and desk employees; desk-first knowledge bases such as Confluence, Notion, Guru, and Document360 are strongest for knowledge workers and need a frontline layer to reach the floor. The SOP binder on the plant floor is version 6. The document control system says version 9 is current. The auditor asks which version the night shift followed on the date of the deviation, and who on that shift had read it. Nobody can answer, because the two systems were never the same system. Document control lived with quality on a desktop. The floor lived with a binder, a laminated card, and whatever the shift lead remembered. SOP compliance did not fail at authoring. It failed at the point of access. The scale of that gap is measurable. Deskless workers are 70 to 80% of the global workforce, about 2.7 billion people, according to [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology). Only 23% of frontline workers believe they have access to the technology they need to be productive, according to [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html). [Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) sets a 75% minimum search-success benchmark for the systems that hold company knowledge and finds only 13% of employees use their intranet daily, while [SWOOP Analytics](https://www.swoopanalytics.com/sharepoint-bm-25) finds employees spend under six minutes a day there. This guide is for compliance, operations, and learning leaders in regulated industries who own that gap. It covers what makes SOP and policy knowledge different from general knowledge management, what each industry requires, why controlled documents fail to reach the frontline, the seven capabilities to evaluate, a comparison of knowledge base software through the regulated lens, and how to run the evaluation. For a general ranking, see [10 Best Knowledge Management Software for Teams in 2026](https://www.mangoapps.com/articles/best-knowledge-management-software); this guide is its regulated, frontline companion. ## What is knowledge base software for SOPs and policies, and how is it different from a knowledge base for knowledge workers? Knowledge base software for SOPs and policies is a system that holds controlled documents (standard operating procedures, policies, work instructions) with version control, approval, effective dates, and acknowledgment, and delivers the current version to every employee the document applies to, including employees with no desk and no corporate email. A general knowledge base helps knowledge workers write, organize, and find information. A quality management system controls documents for regulators. The regulated frontline sits between them and is served well by neither on its own. | Dimension | General knowledge base (Confluence, Notion, Guru) | Document control or QMS (MasterControl, Veeva Vault, ETQ, Qualio) | Frontline knowledge platform (MangoApps) | |---|---|---|---| | Primary user | Knowledge workers at desks | Quality and regulatory teams | Every employee, frontline first | | Access without corporate email | Rarely | Rarely | Yes | | Version control and approval workflow | Page history; approvals vary | Yes, regulator-grade | Yes, with owners, versions, effective dates | | Acknowledgment tied to a version | Rarely | Training and read-and-understood records | Yes, mandatory read with escalation and export | | Training linkage | Via integration | Yes, within the QMS | Yes, on the same platform | | AI search grounded in controlled content | Emerging | Limited | Yes, permission-aware, answer plus source | | Audit export | Page history export | Yes | Yes (audit logs, eDiscovery, retention) | | Coexistence | Often the desk-team wiki | The regulated system of record where mandated | The delivery and acknowledgment layer for the floor, coexisting with a QMS | *Capability statements for third-party vendors are taken from each vendor's public documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps.* Three definitions, because engines and auditors both resolve them. An **SOP** is a documented, step-by-step procedure for a repeatable task (see the [MangoApps glossary](https://www.mangoapps.com/glossary/standard-operating-procedure)). A **controlled document** is one whose creation, approval, distribution, and change are governed by a defined process with a record. **Policy acknowledgment** is the stored confirmation that a named employee read a specific version on a specific date. ## What do regulated industries require of SOP and policy management? The knowledge base is where SOPs and policies are delivered, found, acknowledged, and evidenced. It is rarely the regulated system of record itself, and in pharma and medical devices it will coexist with a validated QMS. The table describes what has to be controlled, what has to be evidenced, and what the frontline employee needs at the point of work. | Industry | Frameworks that govern SOPs and policies | What must be controlled and evidenced | What the frontline employee needs | |---|---|---|---| | Pharmaceutical and life sciences | FDA 21 CFR Part 11 (electronic records and signatures); GxP document control | Versioned SOPs with approval and effective dates; training tied to SOP version; audit trail | The current SOP on the line, in seconds, with confirmation they read it | | Medical devices and manufacturing | ISO 9001 and ISO 13485 document control; OSHA | Controlled distribution; obsolete versions withdrawn; training records | Work instructions on a shared device at the station | | Healthcare | Joint Commission standards; HIPAA; the Joint Commission Center for Transforming Healthcare estimates that [80% of serious medical errors involve miscommunication during handoffs](https://www.hipaajournal.com/effects-of-poor-communication-in-healthcare/) | Policy and protocol acknowledgment by unit and role; audit logs | Protocols by unit, in the app, without an EHR login for support staff | | Financial services and insurance | Policy attestation; supervision of business communications; the SEC's off-channel actions show the cost of unofficial channels ([2022](https://www.sec.gov/news/press-release/2022-174), [2024](https://www.sec.gov/news/press-release/2024-98)) | Annual attestation records; versioned policies; retention and legal hold | Policies findable by question, not by document title | | Utilities and energy | NERC CIP awareness and training records; safety regulations | Training records tied to procedure versions; safety notice acknowledgment | Procedures offline in the field | | Food service and retail | Food safety SOPs; OSHA; wage-and-hour notices | Acknowledgment by location; multilingual delivery | The SOP in the language the crew speaks | Add the primary regulator pages as links at publication; each framework above has a public source. ## Why controlled documents never reach the floor The document is controlled and invisible. That is the frontline findability problem, and it has five causes. **Desk-only access.** The document control system requires a corporate account; the floor does not have one. Deskless workers are 70 to 80% of the workforce ([BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology)). **PDF-only formats.** A 40-page PDF on a phone is not a procedure anyone follows mid-task. **No search where the work is.** The shared device at the station has no search, or a keyword search that returns twelve documents. Social Edge Consulting's 75% search-success benchmark is rarely measured for SOPs at all. **English only.** A procedure the crew cannot read is not controlled; it is decorative. **The "current version" question.** When the floor cannot tell version 6 from version 9, it follows the one it can find. In a regulated setting, "findable" has a precise meaning: the search returns the current effective version and its owner; superseded versions are visible only to roles authorized to see them; and the answer cites the SOP section it came from. Anything less is a document library. ## The seven capabilities to evaluate ### 1. Permission-aware AI search that answers from controlled content and cites the section The test is a plain-language question on a phone ("how long can the vaccine sit at room temperature?") answered with the current SOP section and its version, and nothing the user is not permitted to open. Superseded versions must not be answered from. See the [enterprise search glossary entry](https://www.mangoapps.com/glossary/enterprise-search-rag) and [Your AI Agent Is Reading a Copy of Your Business](https://www.mangoapps.com/articles/ai-agents-native-data-vs-copies). **Verify in demo.** Ask a question whose answer changed between versions; confirm the current answer and the citation. ### 2. Version control with effective dates, approval workflow, and superseded-version handling Every SOP has an owner, an approval workflow scoped to its risk, an effective date, and a history. Superseded versions are withdrawn from general view but retained for audit. **Verify.** Publish version 9 with a future effective date; show what the floor sees today and on the effective date. ### 3. Policy acknowledgment tied to a specific version, with escalation and export Mandatory read confirmation attributed to the HRIS identity, tied to the version acknowledged, with manager escalation and an exportable record. Re-acknowledgment when the version changes. See [From Sent to Certain](https://www.mangoapps.com/articles/from-sent-to-certain-closing-the-frontline-accountability-loop) and [Building the Audit Trail](https://www.mangoapps.com/articles/frontline-workforce-compliance-building-the-audit-trail). **Verify.** Export acknowledgments for version 8 after version 9 goes live. ### 4. Training linkage: an SOP change triggers re-training, and completion is written back Training records are evidence that the procedure was understood, not just read. [The Proof Problem](https://www.mangoapps.com/articles/the-proof-problem-why-training-records-aren-t-enough) explains why records alone fall short; the linkage between SOP version, training assignment, and completion is what closes the loop. **Verify.** Change an SOP; show the automatic training assignment by role and the completion on the employee record. ### 5. Frontline access: no corporate email, shared device and kiosk, offline, translation Identity provisioned from the HRIS and activated by SMS or QR code; kiosk mode for stations; offline access for basements and fields; translation of the SOP and the search. **Verify.** Sign in as a line worker with no email on a shared kiosk and find the current SOP in Spanish. ### 6. Ownership and lifecycle: owners, review dates, expiry, content freshness reporting Every controlled document has a named owner and a review date; expiry is enforced; freshness is reported by department. **Verify.** Show the expiry queue and the percentage of SOPs past review. ### 7. Audit evidence: tamper-evident logs, retention, legal hold, exportable timeline For one employee: every SOP they acknowledged, every version, every training completion. For one document: every version, approval, distribution, acknowledgment. Retention by document type; legal hold that suspends deletion. See [Why Workforce Records Fail When Audits Actually Happen](https://www.mangoapps.com/articles/why-workforce-records-fail-when-audits-actually-happen). **Verify.** Produce both timelines in the demo without an engineering ticket. ## Best knowledge base software for SOPs and policies in regulated industries The best knowledge base software for SOPs and policies in regulated industries delivers the current controlled document to every employee it applies to, including employees with no corporate email, and evidences that they read it. On that test the field divides into three groups: a frontline knowledge platform that combines delivery, acknowledgment, training, and search (MangoApps); general knowledge bases that excel for knowledge workers (Confluence, Notion, Guru, Document360, Bloomfire); and quality management systems that control documents for regulators and rely on other tools to reach the floor (MasterControl, Veeva Vault QualityDocs, Qualio). Full profiles of the general knowledge bases are in [10 Best Knowledge Management Software for Teams in 2026](https://www.mangoapps.com/articles/best-knowledge-management-software). | Platform | Frontline access without corporate email | Version control and approvals | Acknowledgment tied to version | Training linkage | AI search grounded and permission-aware | Audit export | Certifications published | |---|---|---|---|---|---|---|---| | [MangoApps](https://www.mangoapps.com/solutions/knowledge-management) | Yes | Yes | Yes (Critical Alerts, mandatory read, export) | Yes (same platform) | Yes | Yes (audit logs, eDiscovery, retention) | HITRUST CSF, SOC 2 Type II, ISO 27001, FedRAMP ATO | | [Confluence](https://www.atlassian.com/software/confluence) (Atlassian) | Limited | Page history; approvals via apps (vendor-stated) | Via apps (vendor-stated) | Via integration | Atlassian Intelligence (vendor-stated) | Page history; audit via Atlassian Guard (vendor-stated) | Vendor-stated | | [Notion](https://www.notion.so/) | Limited | Page history | No native | Via integration | Notion AI (vendor-stated) | Limited | Vendor-stated | | [Guru](https://www.getguru.com/) | Partial (browser extension and app) | Verification workflow (vendor-stated) | Card verification, not per-employee acknowledgment (vendor-stated) | Via integration | Yes (vendor-stated) | Vendor-stated | Vendor-stated | | [Document360](https://document360.com/) | Limited | Versioning and workflow (vendor-stated) | Not published | Via integration | AI assistant (vendor-stated) | Vendor-stated | Vendor-stated | | [Bloomfire](https://bloomfire.com/) | Partial | Vendor-stated | Not published | Via integration | Yes (vendor-stated) | Vendor-stated | Vendor-stated | | SharePoint document libraries (Microsoft) | Partial (Teams and licensing) | Versioning and approval flows | Via Power Automate | Via Viva Learning | Microsoft 365 Copilot (licensed) | Microsoft Purview | Microsoft 365 portfolio | | QMS archetype ([MasterControl](https://www.mastercontrol.com/), [Veeva Vault QualityDocs](https://www.veeva.com/), [Qualio](https://www.qualio.com/)) | Limited | Yes, regulator-grade | Read-and-understood and training records | Yes, within the QMS | Limited | Yes | Vendor-stated; validated for regulated use | *Capability and certification statements for third-party vendors are taken from each vendor's public documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps. "Not published" means the pages reviewed did not disclose it; "Limited" means the product is not designed for the frontline access pattern.* **MangoApps** centralizes policies, SOPs, and training content in one searchable hub every employee can reach from any device without a corporate email; AI search surfaces the right answer with permissions enforced; Critical Alerts provide mandatory acknowledgment with audit trails; training is assigned by role and location on the same platform; and a content governance engine applies lifecycle policies, with audit logs, eDiscovery, and retention per [mangoapps.com/security](https://www.mangoapps.com/security). Holt of California, a CAT equipment dealer with 800 employees, reported a 50% reduction in the time employees spent finding information and 85% weekly engagement after implementing MangoApps. **Confluence, Notion, Guru, Document360, and Bloomfire** are strong knowledge bases for knowledge workers, and the KM ranking covers their strengths in depth. For regulated frontline SOPs they typically lack no-email frontline access and per-employee, per-version acknowledgment, and depend on integrations for training. **SharePoint document libraries** control versions and approvals well inside Microsoft 365 and carry Purview for records; frontline reach depends on Teams licensing, and acknowledgment requires Power Automate. **Quality management systems** are the regulated system of record where a validated system is mandated. They are built for the quality team, not the line, and pair naturally with a frontline platform that delivers and acknowledges the current version on the floor. ## How to run the evaluation 1. **"Publish version 9 of an SOP and show me what a night-shift employee sees on a shared kiosk."** Strong: the current version, in her language, with a read confirmation. Weak: a PDF link. 2. **"Show the acknowledgment export for version 8 after version 9 goes live."** Strong: both records, per employee, with timestamps. Weak: a single count. 3. **"Ask the AI a question answered in a superseded version."** Strong: the current answer with its section cited. Weak: the old answer. 4. **"Change the SOP and show the re-training assignment and completion on the record."** Strong: automatic, same record. Weak: a link to the LMS. 5. **"Sign in as a line worker with no corporate email."** Strong: two minutes from a QR code. Weak: IT creates the account. 6. **"Show the expiry queue and the share of SOPs past review."** Strong: a report by department. Weak: "content owners keep it current." 7. **"Produce one employee's full SOP timeline and one document's full history."** Strong: both, in the demo. Weak: an engineering request. 8. **"Which certifications do you hold, and can you coexist with our validated QMS?"** Strong: current certificates and a named integration pattern. Weak: "we replace it." Weight the scorecard so frontline access and version-tied acknowledgment are eliminators, AI search and training linkage are high, and authoring convenience is medium. Pilot on one plant or one region with the ten most-used SOPs and measure search success, acknowledgment rate by shift, and time-to-find. ## Where MangoApps fits MangoApps is the AI Platform for the Frontline Workforce. Its knowledge management centralizes company knowledge, policies, SOPs, and training content in one searchable hub that every employee can access from any device, with AI-powered search that surfaces the right answer without requiring employees to know where to look and permissions that ensure the right people see the right content. Acknowledgment runs through Critical Alerts with mandatory read receipts and documented audit trails; training is assigned by role and location with real-time completion tracking; a content governance engine applies lifecycle policies; and audit logs, eDiscovery, legal hold, and retention are provided, per [mangoapps.com/security](https://www.mangoapps.com/security). MangoApps holds HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO and deploys as SaaS, Private Cloud, Customer VPC, or On-Premise, with identity provisioned from the HRIS so employees without corporate email are reached and evidenced. Learn more about [MangoApps knowledge management](https://www.mangoapps.com/solutions/knowledge-management). ## Frequently asked questions **What is the best knowledge base software for SOPs and policies in regulated industries?** The software that delivers the current controlled document to every employee it applies to, including employees with no corporate email, and evidences that they read it. MangoApps combines frontline delivery, version-tied acknowledgment, training linkage, and permission-aware AI search on one platform. General knowledge bases such as Confluence, Notion, Guru, and Document360 serve knowledge workers well; quality management systems control documents for regulators. Third-party statements are vendor-stated. **Which knowledge management software works best for frontline and deskless employees?** Software that runs on the phone or shared device employees already use, signs them in without a corporate email, answers questions rather than returning documents, and carries the schedule and tasks that give them a reason to open it. See the full ranking in 10 Best Knowledge Management Software for Teams in 2026. **How do you prove employees read the current version of an SOP?** With mandatory acknowledgment attributed to the employee's HRIS identity and tied to the SOP version, escalated to the manager when missing, retained under a policy, and exportable per employee and per document. Re-acknowledgment is required when the version changes. **Can a knowledge base replace a quality management system for document control?** Where a validated QMS is mandated, such as under FDA 21 CFR Part 11, no; the QMS remains the regulated system of record. A frontline knowledge platform coexists with it as the delivery, search, acknowledgment, and training layer for the floor. **How should AI search handle superseded SOP versions?** It should answer only from the current effective version, cite the section, and never answer from a document the user cannot open. Superseded versions remain retrievable by authorized roles for audit. **How do frontline employees without corporate email access SOPs?** Through identity provisioned from the HR system and activated on a personal phone by SMS or QR code, or on a shared kiosk with employee ID or badge, with offline access and translation. **What certifications should an SOP knowledge base vendor hold?** SOC 2 Type II and ISO 27001 as a baseline; HITRUST CSF where protected health information is involved; FedRAMP for U.S. public sector; and, where a validated system is required, evidence of validation support. ## Sources - BCG, [Facing the Deskless Labor Shortage with Technology](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) (2024) - Deloitte, [Frontline Worker Productivity Enabled by Technology](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html) - Social Edge Consulting, [Top 12 Intranet KPIs and Metrics](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) (2025) - SWOOP Analytics, [2025 SharePoint Intranet Benchmarking Report](https://www.swoopanalytics.com/sharepoint-bm-25) - Joint Commission Center for Transforming Healthcare, hand-off communications research, as summarized by [HIPAA Journal](https://www.hipaajournal.com/effects-of-poor-communication-in-healthcare/) - U.S. Securities and Exchange Commission, press releases [2022-174](https://www.sec.gov/news/press-release/2022-174) and [2024-98](https://www.sec.gov/news/press-release/2024-98) - MangoApps, [security](https://www.mangoapps.com/security) and [knowledge management](https://www.mangoapps.com/solutions/knowledge-management) --- # 9 Things to Know About Performance Management Software for Frontline and Hourly Employees **Author:** Andy Tolton **Published:** 2026-09-08 **Category:** performance-management Why performance management built around annual reviews and desk workers fails on the frontline, and what to evaluate in software that embeds goals, check-ins, and reviews into the daily work of multi-location teams. > **Quick answer:** Performance management software works for frontline and hourly employees when goals, check-ins, and reviews live inside the app those employees already open every shift, not in an HR system they log into once a year. Look for mobile check-ins that take two minutes, goals tied to store or site metrics, feedback managers can give from the floor, a shared performance record connected to scheduling and training data, and multi-location reporting that shows which sites are behind. MangoApps embeds performance into daily frontline work on the same platform as schedules, tasks, and training; standalone performance suites such as Lattice, 15Five, Culture Amp, Betterworks, and Workday Performance are strongest for desk-based teams. A district manager with 14 stores and 400 hourly employees receives the same email every October: complete your annual reviews in the performance system by November 15. None of the 400 employees has ever logged into that system. Most have no corporate email to log in with. The manager writes 400 reviews from memory over three weekends, and every one of them is a rumor about a year nobody recorded. Only two in 10 employees strongly agree their performance is managed in a way that motivates them to do outstanding work, according to [Gallup](https://www.gallup.com/workplace/236135/give-performance-reviews-actually-inspire-employees.aspx). On the frontline the problem is worse, because the tools were never in the room where the work happened. Among deskless workers, 53% feel burned out and 43% are actively looking for a new job ([BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology)); global engagement sits at 20% ([Gallup](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx)); and replacing an employee costs one-half to two times annual salary ([Gallup](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx)). The failure is not the review form. It is that performance was never embedded in daily frontline work. This guide covers the nine things HR leaders at multi-location enterprises should know before choosing performance management software for frontline and hourly employees, starting with the question that matters most. ## Which performance management platforms embed goals and reviews into daily workflows? The platforms that embed goals and reviews into daily workflows are the ones that run performance on the same login and employee record as the schedule, the tasks, the communication, and the training. In that model a store associate sees her goals when she opens the app for her shift, her manager gives feedback from the floor in the same app, and the review at quarter end draws on a record that already exists. Standalone performance suites integrate with the HRIS but not with the shift; the frontline employee has to be sent to them. | Platform | Category | Goals visible in the daily work app | Manager check-ins from mobile | Review data tied to scheduling and training | Sign-in without corporate email | Best for | |---|---|---|---|---|---|---| | [MangoApps](https://www.mangoapps.com/solutions/performance-learning) | Unified employee platform | Yes | Yes | Yes (same platform) | Yes | Frontline and multi-location enterprises that want performance inside daily work | | [Lattice](https://lattice.com/) | Performance and engagement suite | Via integration | Yes (vendor-stated) | Via integration | Vendor-stated | Desk-based teams with continuous performance programs | | [15Five](https://www.15five.com/) | Performance and engagement suite | Via integration | Yes (vendor-stated) | Via integration | Vendor-stated | Manager-led check-ins for desk teams | | [Culture Amp](https://www.cultureamp.com/) | Listening and performance | Via integration | Vendor-stated | Via integration | Vendor-stated | Organizations pairing performance with survey science | | [Betterworks](https://www.betterworks.com/) | Goals and performance (OKR-led) | Via integration | Vendor-stated | Via integration | Vendor-stated | Enterprise goal alignment | | [Leapsome](https://www.leapsome.com/) | Performance, engagement, learning | Via integration | Vendor-stated | Partial (learning in suite) | Vendor-stated | Mid-market desk teams | | [Workday Performance](https://www.workday.com/) | HCM suite module | Via Workday | Via Workday mobile | Via Workday | Vendor-stated | Workday-standardized enterprises | *Capability statements for third-party vendors are taken from each vendor's public documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps.* ## The 9 things to know ### 1. Performance for hourly workers has to happen on a phone, in two minutes, mid-shift **What it means.** A check-in is a two-minute exchange between a shift lead and an associate, on the floor, on a phone or a shared device, not a form completed at a desk. **Why frontline is different.** There is no desk. The manager has ten minutes between shifts and the associate has a break. Only 23% of frontline workers believe they have the technology they need to be productive ([Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html)); a performance tool that needs a laptop is one more they do not have. **What to look for.** Mobile check-in templates, sign-in without corporate email, shared-device support, and offline entry that syncs later. **Verify in the demo.** A shift lead gives feedback to an associate from a phone during a shift; the associate sees it on hers. ### 2. Goals should come from the store or site, not the HR system **What it means.** Frontline goals are operational: shrink, safety incidents, service scores, order accuracy, attendance reliability. They should be set from site metrics and templates by role, not typed into a form. **Why frontline is different.** A cashier's goals are the store's goals. When they live in a separate HR system they are invisible during the shift that decides them. **What to look for.** Goal templates by role and site, goals visible on the daily home screen, progress that updates from operational data where it exists. **Verify.** Show a store's goals on an associate's phone and a district view of progress across 14 stores. ### 3. Check-ins beat annual reviews, and the manager needs a prompt, not a form **What it means.** Continuous performance is a cadence of short conversations with a record, not a quarterly essay. **Why frontline is different.** Managers span dozens of people. Without a nudge in the app they use every day, the cadence dies. See [How to Build a Culture of Continuous Performance Management](https://www.mangoapps.com/articles/how-to-build-a-culture-of-continuous-performance-management). **What to look for.** Manager prompts in the daily app, one-tap check-in templates, and a visible record of the conversation for both people. **Verify.** Show the prompt a manager receives and how long the check-in takes. ### 4. A shared record is the difference between a review and a rumor **What it means.** Schedule adherence, training completions, recognition received, incidents, check-ins, and goals on one employee record that both the manager and the employee can see. **Why frontline is different.** When those live in five systems, the review is assembled from memory. [Why Performance Reviews Fail Without a Shared Record](https://www.mangoapps.com/articles/why-performance-reviews-fail-without-a-shared-record) lays out the cost, and [The Four Information Gaps Behind Every Performance Failure](https://www.mangoapps.com/articles/four-information-gaps-behind-every-performance-failure) names the gaps. **What to look for.** One record per employee that draws from scheduling, training, recognition, and communication on the same platform, or through documented integrations. **Verify.** Open one employee's record and find schedule adherence, training completion, recognition, and the last check-in on one screen. ### 5. Frontline managers span dozens of reports and several sites; the software must be built for that ratio **What it means.** A district manager reviews across 14 stores; a store manager across 40 associates. Calibration has to work across sites, and the district view has to show who is behind. **Why frontline is different.** Desk-team tools assume a manager with eight reports in one office. **What to look for.** District and regional views, calibration across sites, review status by location. **Verify.** Show review completion and score distribution across 14 stores in one view. ### 6. Adoption is the data quality plan **What it means.** If associates and managers do not use the tool during the shift, the record is empty and the review is a rumor again. [Your Performance Data Is Only as Good as Your Adoption](https://www.mangoapps.com/articles/your-performance-data-is-only-as-good-as-your-adoption) makes the case. **Why frontline is different.** Adoption follows the schedule. A performance tool inside the app that holds the schedule inherits its daily habit; a standalone tool has to earn one. **What to look for.** Weekly active use by site for the platform the performance tool lives in. The intranet benchmarks from Social Edge Consulting are a useful analogue: 60% weekly active users is successful and 85% weekly login is best practice ([Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics)). **Verify.** Ask for customer weekly-active data by site for a frontline deployment. ### 7. Performance should connect to learning, skills, and pay, not sit beside them **What it means.** A check-in that surfaces a skills gap should assign the course; a completed certification should appear on the record; the record should feed compensation decisions with data rather than recollection. See [Why Automated Performance Data Is the Secret to Fair Pay](https://www.mangoapps.com/articles/why-automated-performance-data-is-the-secret-to-fair-pay). **What to look for.** Learning assignments from check-ins, completions written to the record, exports to compensation processes. **Verify.** Assign a course from a check-in and show the completion on the record. ### 8. Fairness across locations is measurable **What it means.** Score distributions by site and by manager, calibration sessions across sites, and checks for patterns that disadvantage a shift, a language group, or a location. **Why frontline is different.** Hundreds of managers rating thousands of hourly employees produce variance that a small desk team never sees. **What to look for.** Distribution reports by site and manager, calibration workflows, audit trail on changes. **Verify.** Show score distribution by manager across a district. ### 9. The platform decision comes first **What it means.** A performance tool bought as one more application joins a stack that already averages 101 applications per company and 131 at 5,000+ employees ([Okta, Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/)), in which workers toggle roughly 1,200 times a day ([Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications)). A performance capability on the platform that already runs the shift adds no login, no record, and no permission model. **What to look for.** One identity, one employee record, one permission model across performance, scheduling, training, and communication. See [What "Platform" Should Actually Mean](https://www.mangoapps.com/articles/what-platform-means) and [Why the Platform Decision Comes Before the App Decision](https://www.mangoapps.com/articles/platform-decision-first). **Verify.** Sign in once and move from the schedule to a check-in to a training assignment without a second login. ## What is the best performance management software for frontline and hourly employees? For frontline and hourly employees, the best performance management software is the software they will actually open during a shift. That points to two categories. A unified employee platform such as MangoApps runs goals, check-ins, and reviews inside the same app as the schedule, tasks, training, and communication, with no corporate email required, so performance happens where the work happens. Standalone performance suites such as Lattice, 15Five, Culture Amp, Betterworks, and Leapsome offer deep review and goal tooling designed for desk-based teams and reach hourly employees only through integrations and a separate login. Workday Performance serves Workday-standardized enterprises through the HCM. The comparison table above shows the differences. The decisive test is simple: can a shift lead give feedback from the floor, and can an associate with no corporate email see it? ## What are the best continuous performance management platforms for multi-location enterprises? For multi-location enterprises, continuous performance management depends on three things a single-office tool never had to solve: manager-to-employee ratios in the dozens, calibration across sites, and district-level visibility into who is behind. Look for site and district views of goal progress and review status, distribution reports by manager and location, and check-in prompts that reach managers in the app they use to run the site. The platforms in the table above that run on the same platform as scheduling and tasks have the advantage, because the site data that performance should draw on is already there. ## How to evaluate 1. **"Show a shift lead giving feedback to an associate from a phone during a shift."** Strong: two minutes, same app as the schedule. Weak: "managers use the web portal." 2. **"Show a district view of goal progress across 14 stores."** Strong: one screen, filterable. Weak: an export. 3. **"Open one employee's record with schedule adherence, training, recognition, and the last check-in."** Strong: one record. Weak: four systems. 4. **"Sign in as an hourly associate without a corporate email."** Strong: HRIS-provisioned, two minutes. Weak: IT creates the account. 5. **"Show score distribution by manager across a district."** Strong: a calibration view. Weak: "HR runs that in a spreadsheet." 6. **"Assign a course from a check-in and show the completion on the record."** Strong: same platform. Weak: a link to the LMS. 7. **"What weekly active use do your frontline customers reach, by site?"** Strong: numbers. Weak: a change-management slide. 8. **"Which HRIS do you sync with, and is the connector native?"** Strong: Workday, UKG, ADP, SAP SuccessFactors named; vendor-maintained. Weak: "we have an API." ## Where MangoApps fits MangoApps is the AI Platform for the Frontline Workforce. Its performance management embeds goal-setting, check-ins, and reviews into the platform employees and managers already use every shift for schedules, tasks, communication, and training, so performance is an ongoing practice rather than an annual event. It works for frontline and hourly employees as well as desk workers, with no corporate email required, and performance data connects to learning and skills development on the same platform, giving HR a complete picture beyond review scores. Multi-location enterprises get district and regional views and calibration across sites. MangoApps serves 2M+ users with 98% customer retention and an NPS of 78, and backs deployments with an [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee) of 90%+ active adoption within 90 days. See [Performance Reviews Finally Built for the Frontline Workforce](https://www.mangoapps.com/articles/performance-reviews-finally-built-for-the-frontline-workforce) and [MangoApps performance and learning](https://www.mangoapps.com/solutions/performance-learning). ## Frequently asked questions **Which performance management platforms embed goals and reviews into daily workflows?** Platforms that run performance on the same login and employee record as the schedule, tasks, and training. MangoApps does this natively for frontline and desk employees. Lattice, 15Five, Culture Amp, Betterworks, Leapsome, and Workday Performance integrate with the HRIS but reach frontline employees through a separate login. Third-party statements are vendor-stated. **What is the best performance management software for frontline and hourly employees?** The software those employees will open during a shift: mobile check-ins, goals visible in the daily app, no corporate email required, and a shared record. Unified platforms such as MangoApps fit that description; standalone performance suites are strongest for desk-based teams. **What are the best continuous performance management platforms for multi-location enterprises?** Platforms with district and regional views, calibration across sites, manager prompts in the daily app, and a record that draws on site data. Evaluate MangoApps and the standalone suites on those criteria using the table above. **How often should frontline employees have performance check-ins?** Short check-ins on a regular cadence, typically monthly or tied to operational milestones, in place of or alongside a quarterly or annual review. Two minutes on a phone, prompted in the app the manager already uses. **Can hourly employees complete reviews on a phone without a corporate email?** Yes, on platforms that provision identity from the HRIS and support mobile and shared-device access. MangoApps publishes this; verify the activation flow for any platform in the demo. **How does performance management connect to scheduling and training data?** On a unified platform, schedule adherence, training completions, and recognition write to the same employee record the review draws on. On standalone tools, the connection depends on integrations with the scheduler and the LMS. **How do multi-location enterprises keep reviews fair across sites?** Distribution reports by site and manager, calibration sessions across sites, an audit trail on score changes, and translation so the process is the same in every language the workforce speaks. ## Sources - Gallup, [Give Performance Reviews That Actually Inspire Employees](https://www.gallup.com/workplace/236135/give-performance-reviews-actually-inspire-employees.aspx); [State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx); [This Fixable Problem Costs U.S. Businesses $1 Trillion](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) (2019) - BCG, [Facing the Deskless Labor Shortage with Technology](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) (2024) - Deloitte, [Frontline Worker Productivity Enabled by Technology](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html) - Okta, [Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/) - Harvard Business Review, [How Much Time and Energy Do We Waste Toggling Between Applications?](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) (2022) - Social Edge Consulting, [Top 12 Intranet KPIs and Metrics](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) (2025) --- # The Complete Guide to Choosing Employee Engagement Platforms for Large Frontline Organizations **Author:** Andy Tolton **Published:** 2026-09-08 **Category:** employee-engagement Why engagement platforms built for desk workers fail with frontline staff, the seven adoption failures to design around, and how HR leaders at large frontline organizations choose a platform that works at scale. > **Quick answer:** Employee engagement platforms work for large frontline organizations only when they reach employees who have no corporate email, run on the phone or shared device those employees use every shift, and connect engagement (surveys, recognition, communities) to the work itself (schedules, tasks, training). Desk-first platforms fail on frontline adoption because they assume an inbox and a laptop. For large frontline organizations the shortlist usually includes MangoApps, Workvivo, Achievers, Qualtrics EmployeeXM, Culture Amp, Reward Gateway, Lattice, and 15Five; MangoApps is the platform that runs engagement on the same app as frontline operations. The annual engagement survey reports 71% participation. Leadership is pleased. Nobody mentions that the 3,000 store associates who never received it are counted as "not surveyed" rather than as disengaged, or that the recognition program launched last spring has 40 users at headquarters and none on the floor. This is digital exclusion: an engagement program that cannot see most of the workforce because the tools were built for the minority who sit at a desk. It is the reason engagement platforms fail in frontline organizations, and it has nothing to do with how good the survey questions are. The scale of the problem is in the data. Global employee engagement fell to 20% in 2025, and [Gallup](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) estimates low engagement cost the world economy roughly $10 trillion, or 9% of GDP. Deskless workers are 70 to 80% of the global workforce, about 2.7 billion people, according to [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology), and BCG's survey of deskless workers found 53% feel burned out and 43% are actively looking for a new job. Only 23% of frontline workers believe they have access to the technology they need to be productive, according to [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html). This guide is for HR leaders at large frontline organizations choosing an engagement platform. It covers why frontline engagement platforms fail to gain adoption, what a platform has to do for frontline workers, which platforms work best for large frontline organizations, the business case, how to run the evaluation, and why engagement inside the work beats engagement beside it. For vendor profiles, see [Best Employee Engagement Platforms for 2026](https://www.mangoapps.com/articles/best-employee-engagement-platforms); this guide is the how-to-choose companion. ## Why do frontline employee engagement platforms fail to achieve adoption in large organizations? Seven reasons account for most failures, and every one of them is a design decision, not a frontline attitude. ### 1. The platform assumes a corporate email and a laptop Most engagement platforms authenticate through a corporate account and deliver surveys by email. Deskless workers are 70 to 80% of the global workforce ([BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology)) and 58% of American workers are on the frontline ([JLL](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention)). Most of them were never issued an inbox. The platform excludes them before the first survey goes out. **Fix:** identity provisioned from the HRIS, activated on a personal phone by SMS or QR code, with shared-device access for units where phones are restricted. ### 2. Engagement is separated from work The survey lives in one app, the schedule in another, the recognition program in a third. A frontline worker has no reason to open the survey app, so participation depends on reminders. The average company runs 101 applications, and companies with more than 5,000 employees average 131 ([Okta, Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/)); workers toggle between them roughly 1,200 times a day ([Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications)). Another app loses. **Fix:** run engagement inside the app that holds the schedule, the checklist, and the training, so the pulse survey appears where the worker already is. ### 3. Surveys are annual and desk-designed A 60-question annual survey written for a laptop does not fit a ten-minute break on a plant floor. Frontline shifts need pulse cadence, two-minute forms on a phone, and anonymity that workers trust. **Fix:** short pulses by site and shift, in the worker's language, with anonymity thresholds published. ### 4. Recognition lives in a program nobody on the floor sees Recognition works when it is public and visible in the daily feed. A points program in a separate portal is invisible to the people it is meant to motivate. See [Why Employee Recognition Fails and What Actually Works](https://www.mangoapps.com/articles/why-employee-recognition-fails-and-what-actually-works) and [Employee Recognition Programs That Actually Stick](https://www.mangoapps.com/articles/employee-recognition-programs-that-actually-stick). **Fix:** recognition in the same feed as team news, from peers and managers, visible by site. ### 5. Managers are not equipped to act on results Frontline engagement runs through the shift manager. If results arrive as a corporate PDF three months later, nothing changes at the site that scored lowest. **Fix:** manager dashboards by location with action planning, and results within days. ### 6. Language, shared devices, and connectivity are ignored A survey in English at a site that speaks Spanish, on a device that requires connectivity in a basement, gets the participation it deserves. **Fix:** translation, offline completion, kiosk mode. ### 7. Results are read as a company average A 71% company participation rate hides sites at 10%. Averages are how digital exclusion stays invisible. **Fix:** measure participation and scores by site, shift, and role. The same discipline applies to intranet adoption, where Social Edge Consulting benchmarks 60% weekly active users as successful and 85% as best practice ([Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics)); no frontline engagement program should accept a company average as its metric. ## What does an employee engagement platform need to do for frontline workers? | Criterion | Why it matters for frontline workers | Verify in the demo | |---|---|---| | Reach without corporate email | Most frontline staff have no inbox | Sign in as an hourly associate with no email, from a QR code | | Mobile-first pulse surveys with anonymity | Two minutes on a phone during a break | Send a three-question pulse to one shift at one site | | Recognition visible in the daily feed | Recognition motivates when peers see it | Recognize a colleague from a phone; see it in the site feed | | Communities by site and shift | Belonging is local | Join a site community; post a question | | Manager dashboards and action planning by location | Frontline engagement runs through the manager | Show the lowest-scoring site's action plan | | Translation | Multilingual workforces | Answer a pulse in Spanish; see results aggregated | | HRIS integration for segments | Sites, roles, and tenure must come from the system of record | Create a worker in the HRIS sandbox; see them in the right segment | | Connection to operations (schedules, tasks, training on the same platform) | The daily reason to open the app | Show the schedule and the pulse survey on the same screen | | Analytics by site, shift, and role | Averages hide exclusion | Filter participation by site | | Security and compliance | Frontline industries are often regulated | Current SOC 2 Type II, ISO 27001; HITRUST where health data is involved | ## Which employee engagement platforms work best for large frontline organizations? The platforms that work best for large frontline organizations are the ones that reach employees without corporate email, put pulse surveys and recognition in the same app as the daily work, and report by site. All-in-one platforms (MangoApps, Workvivo) do this natively; listening specialists (Qualtrics EmployeeXM, Culture Amp), recognition specialists (Achievers, Reward Gateway), and performance-led platforms (Lattice, 15Five) are strongest for desk-based teams and reach the frontline through integrations or a mobile app added to a desk-first design. | Platform | Category | Reach without corporate email | Mobile pulse surveys | Recognition in daily feed | Runs schedules, tasks, and training on the same platform | Analytics by site | Best for | |---|---|---|---|---|---|---|---| | [MangoApps](https://www.mangoapps.com/solutions/employee-engagement) | All-in-one employee platform | Yes | Yes | Yes | Yes, native | Yes | Large frontline organizations that want engagement inside the work app | | [Workvivo](https://www.workvivo.com/) | Social intranet and engagement | Partial | Yes | Yes | Via integration | Yes (vendor-stated) | Culture-led organizations, especially Zoom-centric | | [Achievers](https://www.achievers.com/) | Recognition and rewards | Vendor-stated | Partial | Yes | Via integration | Vendor-stated | Enterprise recognition programs | | [Qualtrics EmployeeXM](https://www.qualtrics.com/) | Employee listening | Vendor-stated | Yes | No | Via integration | Yes (vendor-stated) | Enterprise listening and analytics | | [Culture Amp](https://www.cultureamp.com/) | Listening and performance | Vendor-stated | Yes | Partial | Via integration | Yes (vendor-stated) | People analytics and survey science | | [Reward Gateway](https://www.rewardgateway.com/) | Recognition, rewards, benefits | Vendor-stated | Partial | Yes | Via integration | Vendor-stated | Recognition and benefits programs | | [Lattice](https://lattice.com/) | Performance and engagement | Vendor-stated | Yes | Partial | Via integration | Vendor-stated | Desk-based performance-led engagement | | [15Five](https://www.15five.com/) | Performance and engagement | Vendor-stated | Yes | Partial | Via integration | Vendor-stated | Manager-led check-ins for desk teams | *Capability statements for third-party vendors are taken from each vendor's public documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps. "Partial" means the capability exists but depends on configuration or a licensed add-on.* **All-in-one platforms.** MangoApps runs pulse surveys, peer recognition and rewards, and communities by site and shift on the same app as schedules, tasks, training, and HR self-service, with no corporate email required and analytics by location. Workvivo leads with a social feed, livestreams, and recognition and extends to the frontline through its mobile app. **Listening specialists.** Qualtrics EmployeeXM and Culture Amp bring the deepest survey science and analytics; their frontline reach depends on how identity and mobile delivery are configured, and they do not carry the daily work. **Recognition specialists.** Achievers and Reward Gateway are built for recognition and rewards at enterprise scale; frontline visibility depends on where the recognition surfaces. **Performance-led platforms.** Lattice and 15Five pair engagement with performance for desk-based teams. Full profiles are in [Best Employee Engagement Platforms for 2026](https://www.mangoapps.com/articles/best-employee-engagement-platforms). ## How to build the business case | Outcome | Data | Source | |---|---|---| | Profitability, productivity, absenteeism, safety | Top-quartile engagement business units show 23% higher profitability, 18% higher productivity, 81% lower absenteeism, and 64% fewer safety incidents than bottom-quartile units | [Gallup Q12 Meta-Analysis, 2020](https://www.gallup.com/workplace/236927/employee-engagement-drives-growth.aspx) | | Turnover | 18% lower in high-turnover organizations and 43% lower in low-turnover organizations for top-quartile units | Gallup Q12 Meta-Analysis, 2020 | | Replacement cost | One-half to two times annual salary per employee replaced | [Gallup](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) | | Intent to leave | Employees with a positive employee experience are 68% less likely to consider leaving | [SHRM](https://www.shrm.org/about/press-room/employees-with-a-positive-employee-experience-are-68--less-likel) | | Frontline risk | 53% of deskless workers feel burned out; 43% are actively looking | [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) | | The engagement baseline | 20% of employees engaged globally; ≈$10 trillion cost of low engagement | [Gallup, State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) | The business case for a frontline engagement platform is the business case for measuring and acting on the 70 to 80% of the workforce the current program cannot see. ## How to run the evaluation Eight questions, with strong and weak answers. 1. **"Send a two-question pulse to the night shift at three sites and show participation by site an hour later."** Strong: done, by site. Weak: "we can schedule a survey." 2. **"Sign in as a store associate with no corporate email."** Strong: two minutes from a QR code. Weak: IT creates the account. 3. **"Show recognition from an associate appearing in the feed of a colleague who has no corporate email."** Strong: same feed, same app. Weak: a separate portal. 4. **"Show the action plan for the lowest-scoring site and who owns it."** Strong: a manager dashboard with owners and dates. Weak: a corporate PDF. 5. **"Answer a pulse in Spanish and show it aggregated with English responses."** Strong: translation built in. Weak: a separate survey. 6. **"Show the pulse survey and the schedule on the same screen."** Strong: one app. Weak: "we integrate." 7. **"Show participation and scores by site, shift, and role, not the company average."** Strong: filters exist. Weak: one number. 8. **"Which certifications do you hold?"** Strong: current SOC 2 Type II and ISO 27001, HITRUST where relevant. Weak: "best practices." Run a 30-day pilot at two sites with the frontline population that never answered the last survey. Measure participation by site, recognition sent per employee, and manager actions logged. Weight the scorecard so reach without corporate email and site-level analytics are eliminators. ## Engagement inside the work: the platform question Engagement tools that sit beside the operations stack compete for attention with the tools that run the shift. Engagement that lives inside the app where the schedule, the checklist, and the training already are gets opened because the shift requires it. That is the difference between a platform and an add-on, and it is why the platform decision comes before the engagement-tool decision. See [The Complete Guide to Frontline Communication Platforms](https://www.mangoapps.com/articles/frontline-communication-platforms-guide) for the five layers, and [Why the Platform Decision Comes Before the App Decision](https://www.mangoapps.com/articles/platform-decision-first) and [What "Platform" Should Actually Mean](https://www.mangoapps.com/articles/what-platform-means) for the argument. ## Where MangoApps fits MangoApps is the AI Platform for the Frontline Workforce. Its employee engagement suite runs pulse surveys across locations, shifts, and job functions, peer recognition and rewards, and social communities by site and interest, on the same app as schedules, tasks, training, and HR self-service, with no corporate email required and engagement signals reported by location and team. Columbia Basin Health Association, a federally qualified health center where frontline clinical staff make up more than two-thirds of the workforce, reports more than 90% monthly engagement on MangoApps. PetSmart chose MangoApps after finding that about 80% of its 55,000 employees largely did not have access to company communications. Every deployment is backed by the [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee): 90%+ active adoption within 90 days. Learn more about [MangoApps employee engagement](https://www.mangoapps.com/solutions/employee-engagement). ## Frequently asked questions **Which employee engagement platforms work best for large frontline organizations?** Platforms that reach employees without corporate email, deliver pulse surveys and recognition in the same app as the daily work, and report by site. MangoApps does this natively; Workvivo extends a social platform to the frontline; Qualtrics EmployeeXM, Culture Amp, Achievers, Reward Gateway, Lattice, and 15Five are strongest for desk-based teams and reach the frontline through integrations and mobile apps. Third-party statements are vendor-stated. **Why do employee engagement platforms fail with frontline workers?** Because they assume a corporate email and a laptop, separate engagement from the work, run annual desk-designed surveys, hide recognition in a separate portal, leave managers without site-level results, ignore language and shared devices, and report company averages that hide excluded sites. **What is digital exclusion in employee engagement?** The condition where an engagement program cannot see part of the workforce because its tools require credentials or devices those employees do not have. Deskless workers are 70 to 80% of the global workforce, so exclusion usually means the majority is missing. **How often should frontline employees be surveyed?** Short pulses on a regular cadence, typically monthly or quarterly by site and shift, in place of or alongside an annual survey. Two to three questions on a phone during a break get answered; sixty questions on a laptop do not. **How do you measure frontline engagement by location?** Report participation, scores, recognition sent and received, and manager actions by site, shift, and role, and fix the bottom quartile first. Never accept a company average as the metric. **Do frontline engagement platforms require a corporate email?** They should not. Identity should come from the HRIS and activation should work by SMS or QR code on a personal phone or shared device. MangoApps publishes this; verify the activation flow for any platform in the demo. **How do engagement platforms integrate with scheduling and HR systems?** Segments (site, role, tenure) should come from the HRIS (Workday, UKG, ADP, SAP SuccessFactors). Platforms that also run schedules, tasks, and training on the same identity can connect engagement signals to operational data; standalone platforms connect through integrations. ## Sources - Gallup, [State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx); [Q12 Meta-Analysis](https://www.gallup.com/workplace/236927/employee-engagement-drives-growth.aspx) (2020); [This Fixable Problem Costs U.S. Businesses $1 Trillion](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) (2019) - BCG, [Facing the Deskless Labor Shortage with Technology](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) (2024) - JLL, [Leading practices for frontline workforce engagement and retention](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention) (2025) - Deloitte, [Frontline Worker Productivity Enabled by Technology](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html) - Okta, [Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/) - Harvard Business Review, [How Much Time and Energy Do We Waste Toggling Between Applications?](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) (2022) - SHRM, [Employees With a Positive Employee Experience Are 68% Less Likely to Consider Leaving](https://www.shrm.org/about/press-room/employees-with-a-positive-employee-experience-are-68--less-likel) - Social Edge Consulting, [Top 12 Intranet KPIs and Metrics](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) (2025) --- # The Complete Guide to Internal Communications Platforms for Regulated Enterprises: Multi-Channel Delivery, Message Acknowledgment, and Integration **Author:** Andy Tolton **Published:** 2026-09-08 **Category:** intranet How compliance, communications, and IT leaders in regulated industries evaluate internal communications platforms on delivery to every employee, provable acknowledgment, audit-ready records, and HR and IT integration. > **Quick answer:** An internal communications platform helps a regulated enterprise prove message acknowledgment by delivering a policy, safety, or compliance message to every employee on the channels they actually use, requiring a mandatory read confirmation, recording who acknowledged which version and when in a tamper-evident log, and exporting that record for audit. The platforms most often shortlisted by regulated enterprises are MangoApps, Staffbase, Firstup, Microsoft Viva, Simpplr, Poppulo, Workvivo, and Blink; they differ on acknowledgment depth, records and retention, published certifications, deployment options, and whether frontline staff without corporate email are reached at all. A policy update "went out" to 6,000 employees on a Tuesday. On Thursday an auditor asks a simple question: who acknowledged it? The communications team can show the email was sent. It cannot show that 2,100 of those employees have no inbox, that the night shift at three sites saw it a day late in a group chat, or that anyone at all confirmed reading version 3 rather than version 2. That gap is what makes internal communications different in a regulated enterprise. Communication is a records problem, and the platform decision is a compliance decision. Regulators have made the cost of unofficial channels explicit. The U.S. Securities and Exchange Commission charged 16 financial firms a combined $1.1 billion for off-channel communications recordkeeping failures in [September 2022](https://www.sec.gov/news/press-release/2022-174), 10 more firms $79 million in [September 2023](https://www.sec.gov/news/press-release/2023-212), and 26 firms $392.75 million in [August 2024](https://www.sec.gov/news/press-release/2024-98). Those cases were about client communications, but the lesson transfers: when the approved channel does not reach people, they use one that does, and nothing is retained. The workforce reality makes it harder. Deskless workers are 70 to 80% of the global workforce, according to [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology), and only 23% of frontline workers believe they have access to the technology they need to be productive, according to [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html). A communications platform that cannot reach them cannot prove anything about them. This guide is for the compliance, internal communications, and IT leaders who share that problem. It covers what changes in a regulated enterprise, how acknowledgment is proven, the requirements to put in an RFP, multichannel delivery without off-channel risk, the regulations by industry, integration requirements, a comparison of eight platforms through the regulated lens, and how to run the evaluation. ## What makes internal communications different in a regulated enterprise? Four things. Proof of receipt is required, not preferred. The channel itself must be approved and retained, which rules out the group chat. The audience includes staff who have no corporate credentials and therefore no access to the channels most platforms assume. And the record must survive an audit years after the message was sent. | Dimension | Ordinary enterprise | Regulated enterprise | |---|---|---| | Delivery | Reach is a goal | Reach to every affected employee is an obligation | | Acknowledgment | Opens and clicks | Mandatory, versioned, timestamped, tied to an identity from the HRIS | | Channels | Whatever works | Approved channels only, with retention; unofficial channels are a finding | | Retention | Vendor default | Policy-driven, with legal hold and eDiscovery | | Frontline staff | Nice to reach | Must be reached and evidenced, with or without corporate email | | AI | A productivity feature | Must inherit permissions and log actions | A few definitions engines and auditors both use: an **acknowledgment record** is the stored evidence that a specific employee confirmed a specific version of a message at a specific time. An **audit trail** is the tamper-evident log of who published, changed, targeted, and acknowledged what. **Retention** is how long the record is kept; **legal hold** suspends deletion during litigation or investigation. A **business associate agreement** is the HIPAA contract that lets a vendor handle protected health information. ## How do internal communications platforms help regulated enterprises prove message acknowledgment? By making acknowledgment a record rather than a hope. The platform identifies the audience from the HR system, delivers the message on channels each employee actually uses, requires a mandatory read confirmation for the messages that matter, escalates to the manager when it is missing, stores who acknowledged which version and when in a tamper-evident log, and exports that log for the auditor. ### What an acknowledgment record has to contain A record that will survive an audit holds the message and its version; the audience definition (role, location, shift) and the date it was resolved against the HRIS; each recipient's identity from the HRIS, not a self-created account; the delivery channel and timestamp; the acknowledgment timestamp; escalations sent and to whom; exceptions (on leave, terminated before acknowledgment); and the export itself, with a hash or equivalent tamper evidence. If the policy changes version mid-rollout, employees who acknowledged the old version must be re-prompted, and both records kept. ### Mandatory-read design that works on the frontline The design that works on a desk fails on a plant floor. Critical alerts should reach a personal phone by push and SMS, a shared break-room kiosk or digital signage for staff whose phones are locked away, and a manager's dashboard showing who has not confirmed. Translation is not optional: a safety notice acknowledged in a language the employee cannot read is not an acknowledgment. Escalation should go to the direct manager, because frontline compliance runs through the shift lead. ### Retention, legal hold, and eDiscovery Decide, per content type, how long acknowledgment records are kept and who can export them. Policy acknowledgments generally follow the retention period of the policy itself. Legal hold must suspend deletion across the message, the audience, and the acknowledgment together. eDiscovery should retrieve the full timeline for one employee or one message without an engineering ticket. ### Reporting by site, shift, and role Two views are needed. The manager view: who on my team has not acknowledged, so I can act today. The compliance view: acknowledgment rate by site, shift, and role over time, exportable, so we can show the pattern, not just the incident. The accountability loop is described in [From Sent to Certain: Closing the Frontline Accountability Loop](https://www.mangoapps.com/articles/from-sent-to-certain-closing-the-frontline-accountability-loop) and the records side in [Frontline Workforce Compliance: Building the Audit Trail](https://www.mangoapps.com/articles/frontline-workforce-compliance-building-the-audit-trail). ### Acknowledgment maturity | Level | What the platform records | What the auditor sees | |---|---|---| | 0 | Email sent | A sent timestamp; no proof anyone with no inbox was reached | | 1 | Opens counted | Aggregate opens; no identity, no version | | 2 | Read receipts | Who opened, but not who confirmed | | 3 | Mandatory acknowledgment with escalation | Who confirmed, when, and who was chased | | 4 | Versioned, retained, exportable, tied to HRIS identity | A defensible record per employee and per message version, across channels including kiosk and signage | Most enterprise communications tools operate at level 2. Regulated enterprises need level 4, and the gap between them is the evaluation. ## Key compliance requirements for message acknowledgment tracking Put these in the RFP, grouped the way your reviewers will read them. **Identity.** Accounts created, updated, and deactivated from the HRIS; SSO for staff with corporate accounts; HRIS-provisioned credentials for staff without email; acknowledgment always attributed to the HRIS identity. **Record integrity.** Tamper-evident audit logs; message versioning with re-acknowledgment on change; audience resolution recorded at send time. **Retention and legal hold.** Retention policies by content type; legal hold that covers message, audience, and acknowledgment together; documented deletion. **Auditability.** Exportable acknowledgment records per message and per employee; API access for the compliance team's systems; a compliance view by site, shift, and role. **Reach.** Delivery to employees without corporate email; kiosk and digital signage acknowledgment; translation; escalation to managers. **Certifications and deployment.** SOC 2 Type II and ISO 27001 as a baseline; HITRUST CSF for healthcare; FedRAMP for U.S. public sector; a choice of SaaS, private cloud, VPC, or on-premise; a data processing agreement naming the regulations that apply. **AI.** Any AI drafting, translating, or answering questions inherits the user's permissions, acts on the platform's own data, and logs its actions. See [Same Platform, Same Governance: Deployment and Compliance Architecture for Regulated Buyers](https://www.mangoapps.com/articles/regulated-deployment-ai-governance). ## Multi-channel delivery without off-channel risk The off-channel problem is not that employees are careless. It is that the approved channel did not reach them, so they built one that did. Before A.S. Watson Benelux deployed MangoApps across 16,000 Kruidvat retail employees, store schedule changes circulated as WhatsApp photos, and managers spent their days answering questions from people who had missed or deleted them. Nothing was recorded. The fix is a single platform that publishes once to every approved channel and keeps one record. | Channel | Reaches staff without corporate email? | Acknowledgment possible? | Retained by the platform? | Typical use | |---|---|---|---|---| | Branded app push notification | Yes | Yes | Yes | Critical alerts, policy changes | | SMS from the platform | Yes | Yes (link to acknowledge) | Yes | Urgent reach when the app is closed | | Digital signage and kiosk | Yes | Yes (kiosk acknowledgment) | Yes | Shared spaces where phones are restricted | | Email | No | Partial | Depends on archiving | Desk staff | | Microsoft Teams | Only with a license | Partial | Via Microsoft 365 retention | Desk staff | | Personal messaging apps (WhatsApp, iMessage, group text) | Yes | No | No | The off-channel finding | ## Which regulations touch internal communications, by industry The communications platform is rarely the regulated system itself. It is where policies are published, acknowledged, and evidenced, where safety and compliance training is announced and assigned, and where communication about regulated processes takes place. That framing keeps the requirements honest. | Industry | What applies to internal communication and records | What the platform must evidence | |---|---|---| | Healthcare | HIPAA (a business associate agreement for any vendor that may handle protected health information); Joint Commission standards; the Joint Commission Center for Transforming Healthcare estimates that [80% of serious medical errors involve miscommunication during patient handoffs](https://www.hipaajournal.com/effects-of-poor-communication-in-healthcare/) | Policy and protocol acknowledgment by unit and role; audit logs; secure channels; HITRUST CSF | | Financial services and banking | Recordkeeping and supervision expectations for business communications; the SEC's off-channel actions ([2022](https://www.sec.gov/news/press-release/2022-174), [2023](https://www.sec.gov/news/press-release/2023-212), [2024](https://www.sec.gov/news/press-release/2024-98)) | Approved channels with retention; legal hold; policy attestation records | | Insurance | Policy attestation; state regulatory examinations | Versioned acknowledgment; retention; exports | | Utilities and energy | NERC CIP awareness and training records | Training announcements tied to completion records; acknowledgment by role | | Pharmaceutical and manufacturing | GxP and GMP document control; OSHA | SOP change communication tied to versions and re-training; safety notice acknowledgment | | Public sector and contractors | FedRAMP; accessibility requirements | FedRAMP-authorized deployment; accessible mobile and web delivery | ## What makes it hard to align communications, training, and operations software in a regulated enterprise? Three systems, three identity models, three audit trails. The policy change is announced in the communications platform, the retraining is assigned in the LMS, the corrective checklist is completed in the operations tool, and the auditor asks for one timeline showing that the same employee did all three. Nobody has it. The alignment problem is a compliance problem before it is an efficiency problem. When acknowledgment lives in one system, certification in another, and execution in a third, the evidence for a single control is spread across three vendors with three retention policies. The platforms that solve this run communication, training, and operations on one identity and one employee record, so a policy change, the training it requires, and the task it triggers are visible as one record. The full treatment is in the companion guide on [aligning communications, training, and operations software](https://www.mangoapps.com/articles/aligning-communications-training-operations-software), and the five-layer framework in [The Complete Guide to Frontline Communication Platforms](https://www.mangoapps.com/articles/frontline-communication-platforms-guide). ## Integration requirements: HRIS identity, LMS records, ITSM, and AI | Integration | Why compliance needs it | What to verify | |---|---|---| | HRIS (Workday, UKG, ADP, SAP SuccessFactors, Paylocity) | Audience and identity must come from the system of record; departed employees must lose access the same day | Create and terminate a worker in a sandbox; watch the audience and the acknowledgment attribution update | | Identity provider (Okta, Microsoft Entra ID, Active Directory) | SSO for desk staff; no-email credentials for frontline staff | Sign in as both kinds of employee | | LMS (Cornerstone, Workday Learning, native) | A policy change should assign training and record completion against the same identity | Change a policy version; see the training assignment and completion write-back | | ITSM (ServiceNow) and operations tools | Corrective actions and tasks triggered by communications | Trigger a task from an alert; see it close | | Microsoft 365 and Google Workspace | Desk-staff channels and document sources | Publish once to app and Teams; search a SharePoint policy from a phone | | BI export and APIs | The compliance team's own reporting | Pull acknowledgment data through the API | | AI connectors | Drafting, translation, and Q&A must respect permissions and log actions | Ask the AI a question answered only in a restricted document; confirm it declines. See [Your AI Agent Is Reading a Copy of Your Business](https://www.mangoapps.com/articles/ai-agents-native-data-vs-copies) | ## Top internal communications platforms for regulated enterprises compared The eight platforms below appear most often on regulated enterprises' shortlists. They are compared on the regulated lens only; full profiles are in [The Best Internal Communications Software of 2026](https://www.mangoapps.com/articles/best-internal-communications-software). | Platform | Mandatory acknowledgment with escalation | Acknowledgment export and audit log | Retention and legal hold | Certifications published | Deployment options | Frontline sign-in without corporate email | Multichannel incl. SMS and signage | Analytics by site and shift | |---|---|---|---|---|---|---|---|---| | [MangoApps](https://www.mangoapps.com/) | Yes (Critical Alerts) | Yes | Yes (retention policies, eDiscovery, legal hold) | HITRUST CSF, SOC 2 Type II, ISO 27001, FedRAMP ATO | SaaS, Private Cloud, Customer VPC, On-Premise | Yes | Yes | Yes | | [Staffbase](https://staffbase.com/) | Partial (read receipts; vendor-stated) | Vendor-stated | Vendor-stated | ISO 27001, SOC 2 Type II | SaaS; EU hosting | Partial | Yes | Yes (vendor-stated) | | [Firstup](https://firstup.io/) | Vendor-stated | Vendor-stated | Vendor-stated | ISO 27001, SOC 2 Type II | SaaS; U.S. and Ireland hosting | Partial | Yes | Yes (vendor-stated) | | [Microsoft Viva](https://www.microsoft.com/en-us/microsoft-viva) | Partial (via Viva Engage and Teams) | Via Microsoft Purview | Via Microsoft Purview | Microsoft 365 portfolio | Microsoft 365 cloud | Partial (licensing) | Partial (no native SMS or signage) | Via Viva Insights | | [Simpplr](https://www.simpplr.com/) | Vendor-stated | Vendor-stated | Vendor-stated | ISO 27001:2022 | SaaS | Partial | Vendor-stated | Vendor-stated | | [Poppulo](https://www.poppulo.com/) | Vendor-stated | Vendor-stated | Vendor-stated | Vendor-stated | SaaS | Not published | Yes (email, signage, Teams) | Vendor-stated | | [Workvivo](https://www.workvivo.com/) | Vendor-stated | Vendor-stated | Vendor-stated | Vendor-stated | SaaS | Partial | Yes (signage) | Vendor-stated | | [Blink](https://www.joinblink.com/) | Yes (mandatory-read with audit logs; vendor-stated) | Vendor-stated | Vendor-stated | Vendor-stated | SaaS | Yes (SMS, QR) | Partial | Yes (vendor-stated) | *Capability and certification statements for third-party vendors are taken from each vendor's public documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps. "Not published" means the pages reviewed did not disclose it. Verified sources: [MangoApps security](https://www.mangoapps.com/security), [Staffbase security](https://staffbase.com/security), [Firstup security](https://firstup.io/legal/security), [Simpplr security](https://www.simpplr.com/security-compliance/).* **MangoApps** runs Critical Alerts with mandatory read receipts, escalation rules, and documented audit trails on the same platform as schedules, tasks, and training, with HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO, four deployment models, and identity provisioned from the HRIS for employees without corporate email. It is the platform in this group built for the acknowledgment-plus-reach problem. **Staffbase** is the strongest multichannel publisher in the group, with ISO 27001, SOC 2 Type II, and published EU hosting; acknowledgment and records are lighter than a system of engagement built for regulated work, and frontline sign-in depends on configuration. **Firstup** brings AI-orchestrated journeys and enterprise analytics, with ISO 27001 and SOC 2 Type II; data hosting is limited to the U.S. and Ireland, which matters for data-sovereignty requirements. **Microsoft Viva** inherits the Microsoft 365 compliance portfolio and Purview retention, but acknowledgment, SMS, and signage are not native, and frontline reach depends on Teams licensing. **Simpplr** offers strong governance and publishing tools with ISO 27001:2022; verify acknowledgment depth and frontline sign-in. **Poppulo** is a campaign-based multichannel platform strong on email and signage; it is built for content delivery rather than records, and frontline sign-in without email is not published. **Workvivo** leads with engagement and culture; verify acknowledgment and retention for regulated use. **Blink** publishes mandatory-read acknowledgment with audit logs and SMS or QR sign-in for frontline staff; certifications and retention should be verified for regulated deployments. ## How to run the evaluation Ten questions, each with what a strong answer and a weak answer sound like. 1. **"Show me the acknowledgment export for a policy that changed version mid-rollout."** Strong: two records per employee, one per version, with timestamps. Weak: a single opens count. 2. **"Terminate a worker in the HRIS sandbox. Show me that their prior acknowledgments still attribute to them and their access is gone."** Strong: both, automatically. Weak: an administrator edits a list. 3. **"Deliver a mandatory read to an employee with no email on a shared kiosk and show the record."** Strong: kiosk acknowledgment attributed to the HRIS identity. Weak: "they can use their personal email." 4. **"Put a message under legal hold. What is suspended?"** Strong: message, audience, and acknowledgments together. Weak: "we don't delete anything anyway." 5. **"Show a district manager who on their team has not acknowledged today's alert."** Strong: a manager view with escalation. Weak: a corporate-only report. 6. **"Translate a safety notice into Spanish and show the acknowledgment tied to the Spanish version."** Strong: version-aware translation. Weak: a separate document. 7. **"Change a policy and show the training assignment and completion write-back."** Strong: one record. Weak: a link to the LMS. 8. **"Which certifications do you hold, and which deployment models do you offer?"** Strong: current certificates and named options. Weak: "we follow industry best practices." 9. **"Ask your AI to summarize a document I am not permitted to see."** Strong: it declines. Weak: it summarizes. 10. **"Which channels do you retain, and which of my employees does each channel reach?"** Strong: a channel-by-audience map. Weak: "we integrate with everything." Weight the scorecard for compliance: acknowledgment and records, certifications and deployment, and frontline reach as eliminators; multichannel breadth, analytics, and integrations as high; content tooling as medium. Run a 30-day pilot at two sites and one shift population, and measure acknowledgment rate by site on a real policy change. ## Where MangoApps fits MangoApps is the AI Platform for the Frontline Workforce. Its internal communications suite delivers targeted news and Critical Alerts with mandatory read receipts, escalation rules, and documented audit trails across mobile push, SMS, digital signage, and email, with automatic translation and engagement analytics by location, team, and shift. Because communication runs on the same platform as schedules, tasks, training, and HR self-service, a policy change, the retraining it requires, and the checklist it triggers appear on one employee record. MangoApps holds HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO, offers HIPAA business associate agreements and GDPR data processing agreements, deploys as SaaS, Private Cloud, Customer VPC, or On-Premise, and provides real-time audit logs, eDiscovery, legal hold, and retention policies, per [mangoapps.com/security](https://www.mangoapps.com/security). Identity is provisioned from the HRIS, so employees without corporate email are reached and evidenced. Regulated-industry customers include [TeamHealth](https://www.mangoapps.com/resources/teamhealth-case-study) in healthcare, [Merchants Bonding Company](https://www.mangoapps.com/resources/merchants-bonding-case-study) in insurance, and [Benchmark Human Services](https://www.mangoapps.com/customers/benchmark-human-services), whose 4,000+ caregivers work in client homes without corporate email. ## Frequently asked questions **How do internal communications platforms help regulated enterprises prove message acknowledgment?** By identifying the audience from the HRIS, delivering on channels every employee actually uses including kiosk and signage, requiring mandatory read confirmation with escalation, recording who acknowledged which version and when in a tamper-evident log, and exporting that record for audit. Opens and read receipts are not acknowledgment. **What should a message acknowledgment record contain?** The message and its version, the audience definition resolved at send time, each recipient's HRIS identity, delivery channel and timestamp, acknowledgment timestamp, escalations, exceptions, and tamper evidence on the export. A version change should create a new record without erasing the old one. **Are read receipts enough for compliance?** No. A read receipt shows a message was opened, not that the employee confirmed the specific version. Regulated enterprises need mandatory acknowledgment tied to identity and version, retained under a policy, and exportable. **Which internal communications platforms support mandatory acknowledgment and audit export?** MangoApps publishes Critical Alerts with mandatory read receipts, escalation, and documented audit trails, with eDiscovery and legal hold. Blink publishes mandatory-read acknowledgment with audit logs. Staffbase, Firstup, Simpplr, Poppulo, and Workvivo publish read receipts or analytics; verify acknowledgment depth and export. Microsoft Viva relies on Purview. Third-party statements are vendor-stated. **What makes it hard to align communications, training, and operations software?** Each system has its own identity, employee record, permission model, and audit trail, so the evidence for one control is spread across three vendors. Platforms that run communication, training, and operations on one identity and record produce one timeline per employee. **How long should acknowledgment records be retained?** Generally for the retention period of the policy or requirement they evidence, and longer under legal hold. Set retention per content type and confirm the platform can apply and prove it. **Which certifications should a regulated enterprise require from a communications vendor?** SOC 2 Type II and ISO 27001 as a baseline; HITRUST CSF where protected health information is involved; FedRAMP for U.S. public sector. Ask for current certificates and reports. **How do you reach employees without corporate email with compliance messages?** Provision identity from the HRIS, let employees activate on a personal phone by SMS or QR code, deliver by push and SMS, and provide kiosk and digital signage acknowledgment where phones are restricted. MangoApps and Blink publish these methods; most other platforms depend on configuration or licensing. ## Sources - U.S. Securities and Exchange Commission, press releases [2022-174](https://www.sec.gov/news/press-release/2022-174), [2023-212](https://www.sec.gov/news/press-release/2023-212), [2024-98](https://www.sec.gov/news/press-release/2024-98) - BCG, [Facing the Deskless Labor Shortage with Technology](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) (2024) - Deloitte, [Frontline Worker Productivity Enabled by Technology](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html) - Joint Commission Center for Transforming Healthcare, hand-off communications research, as summarized by [HIPAA Journal](https://www.hipaajournal.com/effects-of-poor-communication-in-healthcare/) - Vendor security pages: [MangoApps](https://www.mangoapps.com/security), [Staffbase](https://staffbase.com/security), [Firstup](https://firstup.io/legal/security), [Simpplr](https://www.simpplr.com/security-compliance/) --- # The 10 Best Employee Intranet Platforms for Governance, Compliance, and Global Workforce Communication (2026) **Author:** Andy Tolton **Published:** 2026-09-08 **Category:** intranet Ten mobile-friendly employee intranet platforms ranked on governance depth, compliance certifications, deployment options, multilingual reach, and frontline adoption for global enterprises. > **Quick answer:** The employee intranet platforms global enterprises shortlist for governance and compliance in 2026 are MangoApps, Microsoft SharePoint and Viva, Unily, Staffbase, LumApps (with Beekeeper), Akumina, Simpplr, Interact, Igloo Software, and Haiilo. Compare them on published certifications (SOC 2 Type II, ISO 27001, HITRUST, FedRAMP), deployment options, documented data residency, audit and eDiscovery depth, multilingual delivery with regional administration, and whether frontline employees can sign in without a corporate email. MangoApps is the platform in this group that publishes all four certifications together with private-cloud and on-premise deployment and no-email frontline access. A global intranet has two jobs that pull in opposite directions. Compliance wants control: one current version of every policy, a record of who acknowledged it, data that stays where the regulator says it stays. Reach wants openness: 27,000 employees in four countries, most of them on a shop floor with a personal phone and no company email, opening the app because it holds something they need today. Most intranet rankings pick a side. This one does not. The ten platforms below are ranked on how well they do both, because for a global enterprise the platform that cannot prove acknowledgment is a liability and the platform the frontline cannot open is a rounding error. The stakes are visible in the data. Deskless workers make up 70 to 80% of the global workforce, about 2.7 billion people, according to [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology). Intranet reach varies sharply by country: the intranet is the main source of company information for 61% of desk-based employees in Germany, 45% in the UK, and 39% in the United States, according to [Staffbase's 2025 International Employee Communication Impact Study](https://staffbase.com/blog/employee-communication-impact-study-2025). And regulators have shown what unofficial channels cost: the U.S. Securities and Exchange Commission charged 16 firms $1.1 billion in combined penalties for off-channel communications in [September 2022](https://www.sec.gov/news/press-release/2022-174) and another 26 firms $392.75 million in [August 2024](https://www.sec.gov/news/press-release/2024-98). This is the third intranet ranking on this site, and it is deliberately different from the other two. [25 Intranet Platforms Worth Evaluating in 2026](https://www.mangoapps.com/articles/top-25-intranet-platforms-frontline-desk-workers) is the broad, frontline-first survey, now with a UK section. [Best Employee Intranet Platforms for Frontline Teams in 2026](https://www.mangoapps.com/articles/best-employee-intranet-frontline-teams) ranks ten platforms on frontline readiness. This guide ranks ten on governance, compliance, and global reach, with a vendor mix chosen for that lens. ## Quick reference: 10 intranet platforms for governance and global communication | Platform | Best for | Certifications published | Deployment options | Data residency | Languages and regional admin | Sign-in without corporate email | Ideal size | |---|---|---|---|---|---|---|---| | [MangoApps](https://www.mangoapps.com/) | Frontline and desk employees on one governed platform | HITRUST CSF, SOC 2 Type II, ISO 27001, FedRAMP ATO | SaaS, Private Cloud, Customer VPC, On-Premise | Multi-region AWS; custom residency via enterprise contracting; DPA names GDPR, UK GDPR, DPA 2018 | 50+ languages; delegated admins by region | Yes | 1,000 to 100,000+ | | [Microsoft SharePoint and Viva](https://www.microsoft.com/en-us/microsoft-365/sharepoint/collaboration) | Microsoft 365-standardized enterprises | Microsoft 365 compliance portfolio (SOC 2, ISO 27001) | Microsoft 365 cloud | Regional tenancy | Microsoft translation; M365 admin roles | Partial (Teams and licensing) | Any, IT-resourced | | [Unily](https://www.unily.com/) | Complex global enterprises needing deep governance | ISO 27001, SOC 2 Type II | SaaS | Vendor-stated | Vendor-stated | Partial | 10,000+ | | [Staffbase](https://staffbase.com/) | Multichannel communications at global scale | ISO 27001, SOC 2 Type II | SaaS; EU hosting on Azure and AWS published | EU hosting published | 75+ languages (vendor-stated) | Partial | Medium to large | | [LumApps](https://www.lumapps.com/) (with Beekeeper) | Communication-first with broad integrations and a frontline app | Vendor-stated | SaaS | Vendor-stated | Vendor-stated | Partial (Beekeeper: Yes) | 2,000+ | | [Akumina](https://www.akumina.com/) | Complex Microsoft 365 enterprises with localization needs | Vendor-stated | SaaS on Microsoft 365 | Microsoft 365 regional tenancy | 228 languages (vendor-stated) | Partial | Large global | | [Simpplr](https://www.simpplr.com/) | Fast deployment with strong governance tools | ISO 27001:2022 | SaaS | Vendor-stated | Vendor-stated | Partial | Mid-sized | | [Interact](https://www.interactsoftware.com/) | Content governance and multichannel publishing | Vendor-stated | SaaS | Vendor-stated | Vendor-stated | Partial | 2,500+ | | [Igloo Software](https://www.igloosoftware.com/) | Mid-market needing single-tenant hosting options | Vendor-stated | Multi-tenant or single-tenant SaaS | North America and Europe data centers (vendor-stated) | Vendor-stated | Not published | 500 to 20,000+ | | [Haiilo](https://www.haiilo.com/) | European social intranet with communications focus | Vendor-stated | SaaS | Vendor-stated | Multilingual (vendor-stated) | Partial (MDM deployment) | 1,000 to 50,000 | *Certification, deployment, residency, and capability statements for third-party vendors are taken from each vendor's public documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps. "Vendor-stated" without detail means the vendor claims the capability but does not publish specifics on the pages reviewed; "Not published" means the pages reviewed did not disclose it. "Partial" means frontline access exists but depends on configuration or licensing. Verify current certificates directly with each vendor during procurement.* ## How we ranked: the governance and global-reach framework Eight criteria, weighted for a multi-country, regulated enterprise. They map to the ten evaluation criteria in [The Complete Guide to Intranet Best Practices and Evaluating Enterprise Intranet Platforms](https://www.mangoapps.com/articles/the-complete-guide-to-intranet-best-practices) and the evaluation process in [How to Evaluate Employee Intranet Platforms in 2026](https://www.mangoapps.com/articles/evaluate-employee-intranet-platforms-2026). | Criterion | What we looked for | Weight | |---|---|---| | Certifications and attestations | SOC 2 Type II and ISO 27001 as a baseline; HITRUST for health; FedRAMP for U.S. public sector; current certificates, not badges | Eliminator for regulated industries | | Deployment and residency | SaaS, private cloud, VPC, or on-premise; documented hosting regions; a DPA that names the regulations that apply and the transfer mechanisms | High | | Identity and permissions | HRIS-driven provisioning and deprovisioning; role, region, and brand permissions; delegated regional administrators | High | | Records | Tamper-evident audit logs; exportable acknowledgment records; retention policies; eDiscovery and legal hold | High | | Content governance | Owners, review dates, expiry, versioning; approval workflows scoped to content type | High | | Global communication | Translation of posts, comments, and policies; time-zone publishing; local policy variants; acknowledgment reporting by country and site | High | | Mobile and frontline access | Branded app, sign-in without corporate email, offline, shared-device support | Eliminator for frontline-heavy enterprises | | Adoption evidence | Customer weekly-active data by industry; contractual adoption commitment | Medium | ## Which employee intranet software supports governance and compliance for global enterprises? The platforms below all offer role-based permissions. What separates them is which certifications they publish, which deployment models they offer, whether data residency is documented rather than promised, how deep audit and eDiscovery go, and whether governance coexists with sign-in for employees who have no corporate email. | Platform | SOC 2 Type II | ISO 27001 | HITRUST | FedRAMP | Deployment options | Data residency | Audit and eDiscovery | Regional admin | |---|---|---|---|---|---|---|---|---| | MangoApps | Yes | Yes | Yes (HITRUST CSF) | Yes (ATO) | SaaS, Private Cloud, Customer VPC, On-Premise | Multi-region AWS; custom residency through enterprise contracting; DPA incorporates EU SCCs and the UK International Data Transfer Addendum | Real-time audit logs, eDiscovery, legal hold, retention | Yes | | Microsoft SharePoint and Viva | Yes | Yes | Not published as a HITRUST-certified product | Yes (government cloud offerings) | Microsoft 365 cloud | Regional tenancy | Microsoft Purview | Yes (M365 roles) | | Unily | Yes | Yes | Not published | Not published | SaaS | Vendor-stated | Vendor-stated | Vendor-stated | | Staffbase | Yes | Yes | Not published | Not published | SaaS | EU hosting published | Vendor-stated | Vendor-stated | | LumApps (with Beekeeper) | Vendor-stated | Vendor-stated | Not published | Not published | SaaS | Vendor-stated | Vendor-stated | Vendor-stated | | Akumina | Vendor-stated | Vendor-stated | Not published | Not published | SaaS on Microsoft 365 | Microsoft 365 regional tenancy | Via Microsoft 365 | Vendor-stated | | Simpplr | Not published on the page reviewed | Yes (ISO 27001:2022) | Not published | Not published | SaaS | Vendor-stated | Vendor-stated | Vendor-stated | | Interact | Vendor-stated | Vendor-stated | Not published | Not published | SaaS | Vendor-stated | Vendor-stated | Vendor-stated | | Igloo Software | Vendor-stated | Vendor-stated | Not published | Not published | Multi-tenant or single-tenant | North America and Europe (vendor-stated) | Vendor-stated | Vendor-stated | | Haiilo | Vendor-stated | Vendor-stated | Not published | Not published | SaaS | Vendor-stated | Vendor-stated | Vendor-stated | *Sources: [MangoApps security](https://www.mangoapps.com/security) and [DPA](https://www.mangoapps.com/legal/dpa); [Staffbase security](https://staffbase.com/security); [Unily security certifications](https://www.unily.com/policies/privacy-hub/security-certifications); [Simpplr security and compliance](https://www.simpplr.com/security-compliance/). Other cells are vendor-stated from public documentation as of September 2026 and not independently verified by MangoApps.* Two patterns matter for frontline-heavy global enterprises. Microsoft brings the deepest compliance portfolio in the category, but frontline access depends on Microsoft 365 licensing and Teams, which most hourly and shop-floor employees never receive. Communications-first platforms bring reach and multichannel publishing, but records, retention, and eDiscovery tend to be lighter than in platforms designed as systems of engagement for regulated work. MangoApps is the platform in this group that publishes HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO together with on-premise and VPC deployment and sign-in for employees without corporate email. For how governance and adoption reinforce each other, see [How to Increase Frontline Intranet Adoption Without Sacrificing Governance or Compliance](https://www.mangoapps.com/articles/frontline-intranet-adoption-governance-compliance). ## What are the leading mobile-friendly employee intranet solutions? A mobile-friendly intranet for a global workforce is not a responsive website. It is a branded app on personal phones and shared kiosks, with sign-in that does not depend on a corporate email, offline access, translation, and the schedules and tasks that give frontline employees a reason to open it every shift. | Platform | Branded app | Sign-in without corporate email | Offline | Translation | Kiosk or signage | Schedules and tasks in the app | Frontline adoption evidence | |---|---|---|---|---|---|---|---| | MangoApps | Yes | Yes (HRIS-provisioned; SMS or QR activation) | Yes | 50+ languages | Yes | Native | 90%+ within 90 days (MangoApps customer data); A.S. Watson 16,000+ Kruidvat employees at 80%+ active | | Microsoft SharePoint and Viva | Via Teams | Partial (licensing) | Partial | Yes | Via Teams shared device | Via Teams Shifts | Vendor-stated | | Unily | Yes | Partial | Vendor-stated | Yes | Vendor-stated | Via integration | Vendor-stated | | Staffbase | Yes | Partial | Vendor-stated | 75+ languages (vendor-stated) | Yes (signage) | Via integration | Vendor-stated | | LumApps (with Beekeeper) | Yes | Beekeeper: Yes | Beekeeper: offline forms | Beekeeper: 200+ languages (vendor-stated) | Vendor-stated | Beekeeper: forms and workflows | Vendor-stated | | Akumina | Yes | Partial | Vendor-stated | 228 languages (vendor-stated) | Vendor-stated | Via integration | Vendor-stated | | Simpplr | Yes | Partial | Vendor-stated | Yes | Vendor-stated | Via integration | Vendor-stated | | Interact | Yes | Partial | Vendor-stated | Yes | Yes (signage) | Via integration | Vendor-stated | | Igloo Software | Browser-based | Not published | Vendor-stated | Vendor-stated | Vendor-stated | Via integration | Vendor-stated | | Haiilo | Yes (MDM deployment) | Partial | Vendor-stated | Yes | Vendor-stated | Via integration | Vendor-stated | *Capability statements for third-party vendors are vendor-stated from public documentation as of September 2026 and not independently verified by MangoApps.* For the feature-level detail on no-email access, see [9 Modern Employee Intranet Features That Reach Frontline Staff Without Email](https://www.mangoapps.com/articles/intranet-features-that-reach-frontline-workers). For a ranking built on frontline readiness alone, see [Best Employee Intranet Platforms for Frontline Teams in 2026](https://www.mangoapps.com/articles/best-employee-intranet-frontline-teams). ## The 10 platforms ### 1. MangoApps MangoApps is the AI Platform for the Frontline Workforce: a unified platform that runs communication, knowledge, scheduling, tasks, training, and HR self-service for frontline and desk employees on one identity, one employee record, and one governance model. It has been built for organizations where most employees do not sit at a desk for 18+ years, which is why its governance model was designed around workers who never receive a corporate email. **Best for:** Global enterprises of 1,000 to 100,000+ employees that need one platform for every country, brand, and shift, with certifications and deployment options that clear regulated-industry procurement. **Governance and compliance:** HITRUST CSF (which includes HIPAA), SOC 2 Type II, ISO 27001, and FedRAMP ATO; HIPAA business associate agreements and GDPR data processing agreements; SaaS, Private Cloud, Customer VPC, and On-Premise deployment; real-time searchable audit logs, eDiscovery and legal hold, global retention policies, and a content governance engine with lifecycle policies; role-based access with custom admin roles and delegation at department and network level; AES-256 at rest and TLS in transit; 99.9% uptime SLA, per [mangoapps.com/security](https://www.mangoapps.com/security). The [data processing agreement](https://www.mangoapps.com/legal/dpa) names GDPR, UK GDPR, and the Data Protection Act 2018 and incorporates EU standard contractual clauses and the UK International Data Transfer Addendum; a [subprocessor list](https://www.mangoapps.com/gdpr-subprocessors) is published; custom data residency is available through enterprise contracting. **Global communication:** Translation across 50+ languages; targeting and delegated administration by role, location, region, and brand; acknowledgment reporting by country and site; Critical Alerts with mandatory read receipts and escalation. **Mobile and frontline access:** One branded app for every employee, with identity provisioned from the HRIS and activated on a personal phone or shared device; no corporate email, VPN, or managed hardware; offline access; kiosk and digital signage. **Integrations:** [200+ out-of-the-box integrations](https://www.mangoapps.com/integrations), including Workday, UKG, ADP, Paylocity, SAP SuccessFactors, Rippling, and BambooHR; Okta, Microsoft Entra ID, Active Directory, and LDAP; Microsoft 365 and Google Workspace; Cornerstone and Workday Learning. **Proof:** A.S. Watson Benelux runs MangoApps across 1,700 stores in four countries with 27,000 employees, most with no company email address; more than 80% of Kruidvat's 16,000+ employees became active users and 20,000+ retail employees receive weekly schedules in the app. MangoApps serves 2M+ users with 98% customer retention and an NPS of 78, and reports 90%+ adoption within 90 days backed by an [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee). Analyst recognition includes Gartner Magic Quadrant Visionary for Intranet Packaged Solutions (2025), IDC MarketScape Leader (2024), and Forrester Wave Strong Performer (Q2 2026). **Key considerations:** The platform delivers the most value adopted company-wide rather than by one department; plan configuration time to use its flexibility. **Pricing:** Modular suites, quote-based. [Schedule a demo](https://www.mangoapps.com/schedule-a-call). ### 2. Microsoft SharePoint and Viva SharePoint and Viva form Microsoft's intranet and employee experience offering, embedded in Microsoft 365. SharePoint provides content services and the page framework; Viva Connections and Viva Engage add communication and community; Microsoft Purview supplies records, retention, and eDiscovery across the tenant. **Best for:** Enterprises fully standardized on Microsoft 365 and Teams, with internal IT capacity to configure and govern the intranet over time. **Governance and compliance:** The Microsoft 365 compliance portfolio, regional tenancy, Entra ID identity, and Purview for retention and eDiscovery. Security is not the question with Microsoft. **Global communication:** Microsoft translation and multi-geo tenancy; regional administration through Microsoft 365 roles. **Mobile and frontline access:** Partial. Frontline access depends on Teams and Microsoft 365 frontline licensing, which most hourly and shop-floor employees do not hold. **Key considerations:** Deployment requires internal IT or an implementation partner; full Viva functionality requires add-on licenses; the frontline experience depends on implementation quality and licensing decisions. **Pricing:** SharePoint is included in most Microsoft 365 enterprise plans; Viva modules are licensed separately per user. ### 3. Unily Unily is an intranet and employee experience platform built for large, complex organizations, with a focus on personalization, campaign management, and enterprise governance across regions and business units. **Best for:** Enterprises with 10,000+ employees, distributed teams, and defined ownership for intranet management. **Governance and compliance:** ISO 27001 and SOC 2 Type II, per [Unily's security certifications page](https://www.unily.com/policies/privacy-hub/security-certifications); version control, accessibility checks, and timed publishing; dynamic audience groups. **Global communication:** Multi-region deployments with lifecycle campaigns and dynamic audiences (vendor-stated). **Mobile and frontline access:** Partial; a strong mobile experience that depends on simplification of the desktop configuration. **Key considerations:** Requires experienced administrators for a powerful but complex back end; AI, advanced integrations, and branding may add cost and effort. **Pricing:** Modular, user-based, quote-based. ### 4. Staffbase Staffbase is an enterprise employee communications and intranet platform, headquartered in Germany, with multichannel publishing to app, intranet, email, SMS, and digital signage, and deep Microsoft 365 integration. **Best for:** Medium to large organizations whose communications team needs to publish once and deliver everywhere, at global scale. **Governance and compliance:** ISO 27001 and SOC 2 Type II; HIPAA business-associate requirements met through ISO 27001; EU hosting on Microsoft Azure and Amazon Web Services, per [staffbase.com/security](https://staffbase.com/security). **Global communication:** AI translation across 75+ languages (vendor-stated); campaign analytics; multichannel including SMS and signage. **Mobile and frontline access:** Partial; mobile-first origins, with frontline sign-in dependent on configuration. **Key considerations:** Content governance and enterprise search are weaker than in dedicated intranet platforms; scheduling, tasks, and training require third-party tools. **Pricing:** Enterprise, quote-based; includes onboarding and customer success. ### 5. LumApps (with Beekeeper) LumApps is a communication-first intranet with 100+ productized integrations across Microsoft 365 and Google Workspace and a presence in North America, Europe, and Japan. [LumApps agreed to acquire Beekeeper](https://www.lumapps.com/insights/news/lumapps-and-beekeeper-to-join-forces-creating-the-leading-employee-experience-platform-for-the-future-of-work), the frontline-first mobile platform, on July 2, 2025. **Best for:** Large and mid-market enterprises that want communication-first governance for desk staff and a frontline app for deskless staff from one vendor. **Governance and compliance:** Vendor-stated; confirm certifications and residency for both products during procurement. **Global communication:** Multichannel publishing with campaign management; Beekeeper's inline translation across 200+ languages (vendor-stated). **Mobile and frontline access:** Partial for LumApps; Yes for Beekeeper. **Key considerations:** Some customers report higher-than-expected setup effort; confirm how the two products are licensed and administered together as the integration proceeds. **Pricing:** Tiered, quote-based. ### 6. Akumina Akumina positions itself as an employee experience platform for large, distributed enterprises with deep Microsoft 365 investment and strong IT involvement, with an API-first architecture and localization across 228 languages (vendor-stated). **Best for:** Global enterprises standardized on Microsoft infrastructure with internal development resources and a preference for hands-on customization. **Governance and compliance:** Runs on the Microsoft 365 tenant; certifications vendor-stated. **Global communication:** Localization at scale is the platform's distinguishing claim. **Mobile and frontline access:** Partial. **Key considerations:** Flexibility comes with a steeper learning curve and longer time-to-value; heavy reliance on partners can add cost and complexity. **Pricing:** Not publicly disclosed; quote through the vendor or a partner. ### 7. Simpplr Simpplr is a SaaS intranet emphasizing fast deployment, intuitive content management, self-service publishing, and governance tools, with AI features for personalization and analytics. **Best for:** Mid-sized organizations that want strong governance and communications with minimal IT overhead. **Governance and compliance:** ISO 27001:2022, per [Simpplr's security page](https://www.simpplr.com/security-compliance/); publishing and governance tools. **Global communication:** Vendor-stated; global support outside North America is still expanding. **Mobile and frontline access:** Partial. **Key considerations:** The packaged approach may limit flexibility in complex or heavily integrated environments; some users report integration gaps. **Pricing:** Tiered by user count, quote-based; implementation typically included. ### 8. Interact Interact is a standalone intranet platform used across North America and Europe, with strengths in content publishing, design flexibility, and structured multichannel communications to mobile, email, Teams, and signage. **Best for:** Enterprises of 2,500+ that prioritize content governance and multichannel delivery. **Governance and compliance:** Vendor-stated. **Global communication:** Multichannel publishing, structured communities, engagement analytics. **Mobile and frontline access:** Partial. **Key considerations:** The admin interface can be complex for global administrators; deeper integrations may require developer support. **Pricing:** Per-user subscription with optional modules. ### 9. Igloo Software Igloo Software is a SaaS intranet for mid-market organizations offering multi-tenant or single-tenant hosting, with data center support in North America and Europe (vendor-stated), and built-in governance and analytics. **Best for:** Mid-sized to large organizations, chiefly in North America, that want single-tenant hosting or a European data center option without a heavy IT lift. **Governance and compliance:** Vendor-stated; single-tenant option is the governance-relevant feature. **Global communication:** Vendor-stated; limited presence outside North America. **Mobile and frontline access:** Browser-based; frontline sign-in not published. **Key considerations:** The interface may feel dated compared with design-forward platforms; federated search is lacking. **Pricing:** Subscription by user tier, quote-based. ### 10. Haiilo Haiilo is a European social intranet formed from the merger of COYO, Smarp, and Jubiwee, with a Studio publishing interface, an AI assistant for content and targeting, and a strong mobile experience with MDM deployment. **Best for:** Medium to large enterprises of 1,000 to 50,000 with multiple business units or multilingual needs and a communications and engagement focus. **Governance and compliance:** Vendor-stated. **Global communication:** Multilingual, multi-business-unit publishing. **Mobile and frontline access:** Partial; biometric login and branded MDM deployment. **Key considerations:** Advanced features such as analytics and surveys are modular and may carry fees; third-party integrations rely largely on API access; the flat Pages-and-Communities structure may not suit every organization. **Pricing:** User-based subscription with add-on modules. ## Replacing an outdated intranet with a governed, mobile platform Most global intranet projects are replacements, and the platform being replaced usually failed for a governance reason and a reach reason at the same time. The policy library had three versions of the same document because nobody owned it. The frontline never logged in because they were never issued an account. The two problems have one fix. When a legacy portal is replaced by a governed mobile platform, four things change. Identity comes from the HRIS, so every employee has an account on day one and loses it on termination day. Every policy has one current version, an owner, and an expiry, so employees trust what they find. Acknowledgment becomes a record rather than a paper sheet at the time clock. And adoption moves from the 30 to 40% legacy intranets typically reach to the 60% Social Edge Consulting calls successful and the 85% it calls best practice ([Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics)); MangoApps customers average more than 90% within 90 days. The process is laid out in [How to Replace an Outdated Intranet in 2026](https://www.mangoapps.com/articles/how-to-replace-an-outdate-intranet-in-2026), and the consolidation math in [How to Centralize Tools and Documents with an Employee Intranet](https://www.mangoapps.com/articles/centralize-tools-documents-employee-intranet). One number frames the opportunity: the average company runs 101 applications and companies with more than 5,000 employees average 131 ([Okta, Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/)). A governed platform that also carries schedules, tasks, and training retires several of them. ## How to choose by situation | If you are | Prioritize | Shortlist | |---|---|---| | 10,000+ employees, regulated, multi-country | Certifications incl. HITRUST or FedRAMP where required; deployment options; audit and eDiscovery; no-email frontline access | MangoApps; Microsoft SharePoint and Viva for M365 shops | | Microsoft 365-standardized with a knowledge-worker majority | Entra ID, Purview, Teams depth | Microsoft SharePoint and Viva, Unily, Akumina, Staffbase | | European headquarters with EU or UK residency requirements | Published EU hosting or single-tenant options; UK GDPR documentation | Staffbase, Haiilo, Igloo, MangoApps (custom residency via enterprise contracting) | | Frontline-heavy multi-country retail, hospitality, or manufacturing | Sign-in without corporate email, translation, schedules and tasks in the app | MangoApps, LumApps with Beekeeper | | Mid-market wanting low IT overhead | Packaged governance, fast deployment | Simpplr, Igloo, MangoApps | ## Where MangoApps fits MangoApps publishes HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO; deploys as SaaS, Private Cloud, Customer VPC, or On-Premise; provides real-time audit logs, eDiscovery, legal hold, and retention; and signs a DPA that names GDPR, UK GDPR, and the Data Protection Act 2018 and incorporates EU standard contractual clauses and the UK International Data Transfer Addendum. It reaches every employee on one branded app with no corporate email, translates across 50+ languages, and runs communication, knowledge, schedules, tasks, training, and HR self-service on one identity and one employee record, so AI can be turned on for a global workforce without a new permission model. A.S. Watson Benelux, with 27,000 employees across four countries, is the proof that governance and frontline reach coexist. Every deployment is backed by the [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee): 90%+ active adoption within 90 days. ## Frequently asked questions **Which employee intranet software supports governance and compliance for global enterprises?** Global enterprises shortlist MangoApps, Microsoft SharePoint and Viva, Unily, Staffbase, LumApps, Akumina, Simpplr, Interact, Igloo, and Haiilo. Compare published certifications, deployment options, documented residency, audit and eDiscovery depth, regional administration, and frontline access without corporate email. MangoApps publishes HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO with private-cloud, VPC, and on-premise options. **What are the leading mobile-friendly employee intranet solutions?** MangoApps, Staffbase, Unily, LumApps with Beekeeper, Interact, Simpplr, Haiilo, and Akumina all offer branded mobile apps; Microsoft Viva reaches mobile through Teams. The differences are sign-in without corporate email, offline access, translation, kiosk and signage support, and whether schedules and tasks live in the same app. MangoApps and Beekeeper publish no-email sign-in; most others depend on configuration or licensing. **What certifications should a global enterprise intranet vendor hold?** SOC 2 Type II and ISO 27001 as a baseline; HITRUST CSF for healthcare and other organizations handling protected health information; FedRAMP for U.S. public sector. Ask for current certificates and reports, not logos. **Do intranet platforms offer EU or UK data residency?** Some publish it. Staffbase publishes EU hosting on Azure and AWS; Igloo states data center options in North America and Europe; Microsoft offers regional tenancy; MangoApps hosts on multi-region AWS and offers custom residency and private cloud through enterprise contracting, with a DPA that incorporates the UK International Data Transfer Addendum. Always request the hosting statement in writing. **How do global intranets handle multiple languages and regional administrators?** Through automatic translation of posts, comments, and policies, time-zone-aware publishing, and delegated administrators scoped to a region or brand. MangoApps supports 50+ languages; Staffbase states 75+; Akumina states 228; Beekeeper states 200+ (vendor-stated). **Can frontline employees without corporate email use these platforms?** MangoApps and Beekeeper publish sign-in methods that do not require a corporate email. Microsoft Viva depends on Teams licensing. Unily, Staffbase, Simpplr, Interact, Akumina, and Haiilo support frontline access with configuration or licensing dependencies. Verify the activation flow in the demo. **How is this list different from the best intranets for frontline teams?** That ranking scores platforms on frontline readiness alone. This one scores them on governance, compliance, and global reach, and the vendor mix reflects it: Akumina, Staffbase, Simpplr, Igloo, and Haiilo appear here for governance and residency reasons; Appspace, theEMPLOYEEapp, Haystack, and Sociabble appear there for frontline reasons. **Which intranet platforms replace an outdated portal with the least disruption?** Platforms with vendor-led migration from SharePoint, Workplace from Meta, and legacy portals, HRIS-driven identity so accounts exist on day one, and a phased rollout. MangoApps offers migration services; see How to Replace an Outdated Intranet in 2026 for the four-phase process. ## Sources - BCG, [Facing the Deskless Labor Shortage with Technology](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) (2024) - Staffbase, [2025 International Employee Communication Impact Study](https://staffbase.com/blog/employee-communication-impact-study-2025) - U.S. Securities and Exchange Commission, press releases [2022-174](https://www.sec.gov/news/press-release/2022-174) and [2024-98](https://www.sec.gov/news/press-release/2024-98) - Social Edge Consulting, [Top 12 Intranet KPIs and Metrics](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) (2025) - Okta, [Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/) - LumApps, [LumApps and Beekeeper to Join Forces](https://www.lumapps.com/insights/news/lumapps-and-beekeeper-to-join-forces-creating-the-leading-employee-experience-platform-for-the-future-of-work) (July 2025) - Vendor security pages: [MangoApps](https://www.mangoapps.com/security), [Staffbase](https://staffbase.com/security), [Unily](https://www.unily.com/policies/privacy-hub/security-certifications), [Simpplr](https://www.simpplr.com/security-compliance/) --- # Can your AI architecture pass these eight tests? **Author:** MangoApps Team **Published:** 2026-09-08 **Category:** mango-scoop Explore eight AI architecture tests, governance for Claude and ChatGPT agents, and new resources for AI-era employee platforms and recruiting. Hand-picked stories from MangoApps this week. ## The Business Spending Blind Spots Operations Can't Afford ![The Business Spending Blind Spots Operations Can't Afford](https://mango-cdn.b-cdn.net/images/blog-thumbnails/blog_645_20260830_140455.png) Ask an operations director to pull together a picture of current business spending, and watch the workflow that follows: reimbursement requests in one module, vendor invoices in another, corporate... [Read the full story →](https://www.mangoapps.com/articles/the-business-spending-blind-spots-operations-can-t-afford) --- ### More to read #### Your AI Agent Is Reading a Copy of Your Business AI pilots stall because agents read stale, permission-less copies of the business. Acting safely requires current state and binding permissions, which only native data provides. [Read more →](https://www.mangoapps.com/articles/ai-agents-native-data-vs-copies) #### Eight Tests That Separate an AI Architecture From an AI Slide Deck Every vendor claims governed, permission-aware AI. These eight reproducible proof-of-concept tests turn each claim into a pass or fail any evaluation team can run in a day. [Read more →](https://www.mangoapps.com/articles/ai-vendor-proof-of-concept-tests) #### Connecting Claude, ChatGPT, and MCP Agents to Workforce Data Without Losing Governance Saying no to external AI agents isn't a strategy. The workable yes binds every agent to a named user, enforces permissions below the model, and lands every call in one audit trail. [Read more →](https://www.mangoapps.com/articles/mcp-enterprise-workforce-agents) #### Same Platform, Same Governance: Deployment and Compliance Architecture for Regulated Buyers Private deployment means little if the AI arrives with different controls. How to verify that governance, certifications, and the audit trail carry across all four deployment models. [Read more →](https://www.mangoapps.com/articles/regulated-deployment-ai-governance) --- ### New Resources **Resource** — [The Employee Platform for the AI Era: Technology Leaders Book](https://www.mangoapps.com/resources/tech-leaders-platform-book) An assistant on top of disconnected tools can answer a question. It cannot safely act. This book is written for the person who owns the architecture, and it includes an eight-te... **Resource** — [End-to-End Talent Acquisition: The Modern Recruiting Playbook](https://www.mangoapps.com/resources/talent-acquisition-book) Recruiting breaks at the handoffs, not the process. This book traces the four transitions where hiring falls apart, then shows what closes them when eight capabilities run on a ... --- ### What's New **General** — [Product Update - August 31, 2026](https://www.mangoapps.com/changelog/3129) * **[Vendor Management in Procurement](https://www.mangoapps.com/directory/app/procurement)** — Procurement users can now create and manage vendor records directly inside the Pr... **General** — [Product Update - August 30, 2026](https://www.mangoapps.com/changelog/3128) * **[Livestreaming Mobile Chat & Q&A Controls](https://www.mangoapps.com/directory/app/livestreaming)** — Phone viewers can now delete their own chat messages and withdraw their... --- # How to Increase Frontline Intranet Adoption Without Sacrificing Governance or Compliance **Author:** Andy Tolton **Published:** 2026-09-08 **Category:** intranet Why frontline intranets fail to reach deskless workers, the mobile-first playbook that lifts adoption, and the governance and compliance controls that make it safe for global, regulated enterprises. > **Quick answer:** Frontline intranet adoption fails for five reasons: workers need a corporate email to log in, the intranet does nothing they need during a shift, search returns documents instead of answers, managers were never made responsible for it, and nobody measures usage by location. Raising adoption does not require loosening control. The platforms that work for global, regulated enterprises pair a mobile-first employee app with identity issued from the HR system, role-based permissions, content ownership and expiry, audit logs, acknowledgment records, and recognized certifications such as SOC 2 Type II, ISO 27001, and HITRUST. There is a paradox at the center of most frontline intranet projects. The more an organization locks the intranet down to satisfy compliance (corporate credentials only, VPN required, every post through an approval queue), the more the frontline routes around it. Schedules go out as photos in a WhatsApp group. Safety notices get taped to a break-room wall. Policy updates are read aloud at a pre-shift huddle and never acknowledged by anyone. That is the least compliant outcome available. Nothing is logged, nothing is retained, and nobody can prove who saw what. Only 23% of frontline workers believe they have access to the technology they need to be productive, according to [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html). When the official tool does not reach them, the unofficial tool does. A.S. Watson Benelux, before it deployed MangoApps across 16,000 Kruidvat retail employees, saw exactly this: store schedule changes circulated as WhatsApp photos, and store managers spent their days fielding questions from employees who had missed or deleted them. This guide is for the operations, HR, and internal communications leaders who own frontline adoption and the compliance, IT, and information security leaders who own the controls. It argues that the two groups want the same things, then shows how to get them: the root causes of low adoption, the mobile-first playbook that fixes them, the governance layer that makes the playbook safe, compliance requirements by industry, a comparison of platforms enterprises shortlist for governance-heavy deployments, benchmarks, and a 90-day plan. ## Why do companies struggle with frontline employee intranet adoption? Five causes account for most failed frontline intranet rollouts, and none of them is "employees don't like technology." Deskless workers are 70 to 80% of the global workforce, about 2.7 billion people, according to [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology), and most intranets were built for the other 20 to 30%. | Root cause | What it looks like | The data | The fix | |---|---|---|---| | **1. Access is gated on a corporate email or laptop** | Frontline staff were never issued an inbox, so the front door is locked before they try the handle | The intranet is the main source of company information for only 39% of desk-based employees in the U.S. and 45% in the UK, versus 61% in Germany ([Staffbase, 2025 International Employee Communication Impact Study](https://staffbase.com/blog/employee-communication-impact-study-2025)). Frontline reach is lower still because that study covers desk-based staff | Issue identity from the HRIS, not the email system; sign in by SMS, QR code, or employee ID | | **2. No daily utility** | Schedules, pay, and tasks live in other apps, so the intranet is "news only" | Only 13% of employees use their intranet daily and 31% never do ([Social Edge Consulting, 2025](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics)) | Put the schedule, pay stub, tasks, and PTO in the same app as the news | | **3. Search fails, so workers stop trying** | A question about a policy returns twelve PDFs or nothing | Social Edge Consulting sets a 75% minimum search-success benchmark; employees spend under six minutes a day on their intranet ([SWOOP Analytics, 2025](https://www.swoopanalytics.com/sharepoint-bm-25)) | AI search that returns a permission-correct answer and its source | | **4. Managers were never made responsible** | The site or shift manager was told the intranet exists, not that it is their channel | Frontline adoption runs through the direct manager; when they are not enabled, the team treats the app as optional | Manager training, team pages, manager dashboards of who has not seen what | | **5. The wrong metrics** | An aggregate login number hides sites with zero adoption | Benchmarks: 60% weekly active users marks a successful intranet; 85% weekly login is best practice ([Social Edge Consulting, 2025](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics)) | Measure weekly active users by location and shift, acknowledgment rates, and search success | The cost of leaving these unfixed is not abstract. BCG's survey of deskless workers found 53% feel burned out and 43% are actively looking for a new job. [Gallup](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) estimates the cost of replacing an employee at one-half to two times annual salary. For the full diagnostic, including trust, connectivity, and content staleness, read [12 Reasons Frontline Intranet Adoption Fails (And How to Fix Each One)](https://www.mangoapps.com/articles/frontline-intranet-adoption-failures). To decide whether the intranet can be fixed or has been outgrown, see [8 Signs Your Frontline Organization Has Outgrown Its Employee Intranet](https://www.mangoapps.com/articles/intranet-problems-hurting-frontline-teams). This guide focuses on the fix and the controls around it. ## Is there really a trade-off between intranet adoption and governance? No. The controls that satisfy compliance and the mechanisms that make an intranet relevant to frontline workers are, for the most part, the same mechanisms. Identity from the HRIS is both a security control and the reason a new hire has access on day one. Role-based content is both a permission model and the reason a warehouse operative in Ohio does not see a policy for a store in Oregon. Acknowledgment records are both audit evidence and the way a manager knows who still needs to read the recall notice. The trade-off appears only when governance is implemented as friction rather than structure. | Governance control | Implemented as friction (adoption falls) | Implemented as structure (adoption rises) | |---|---|---| | Identity and provisioning | Corporate email required; IT creates accounts by ticket | Accounts created automatically from the HRIS; activated on the floor by QR or SMS; removed on termination day | | Content approval | Every post through a central queue, including a team's shift note | Approval scoped to content type: formal for policy, light for team news; owners and expiry dates on everything | | Permissions | Everything locked; requests for access take days | Role, location, and business-unit permissions inherited from the HRIS; delegated admins per region | | Retention and expiry | Nothing expires; two versions of the same policy stay live | Owners, review dates, automatic expiry; one current version, versioned history | | Acknowledgment | A paper sign-off sheet at the time clock | Mandatory read receipts in the app, exportable for audit, visible to the manager | | Device policy | Personal phones banned; shared desktop in a back office | Branded app on personal phones with a clear privacy statement; kiosk mode for shared devices; remote wipe | | AI access | AI disabled because permissions are unclear | AI that inherits the same permissions as search and answers only from content the user can already open | Two definitions help keep the conversation precise. **Intranet governance** is the set of rules for who can publish what, to whom, for how long, and who is accountable for it. **Content lifecycle** is the path each item takes from creation through ownership, review, expiry, and retention. Neither requires an approval queue for a pre-shift note. There is also a retention argument for getting this right. [SHRM](https://www.shrm.org/about/press-room/employees-with-a-positive-employee-experience-are-68--less-likel) research found employees with a positive employee experience are 68% less likely to consider leaving. An intranet that treats frontline workers as first-class users, with clear rules about what the company can and cannot see on their personal phone, is part of that experience. The 12-reasons diagnostic notes that ambiguous data policies are a direct cause of app deletion; a plain-language privacy statement at sign-up is a governance artifact that raises adoption. ## The mobile-first playbook for raising frontline intranet adoption Each principle below has the same shape: what to do, how to measure it, and the governance control that makes it safe. That last line is the point of the article. None of these require loosening control. ### Meet workers on the device they already carry Deploy a branded app to personal phones, with sign-in by SMS one-time code, QR onboarding, or employee ID and PIN. Support shared-device and kiosk mode for environments where personal phones are not allowed. Make it work offline and on low-bandwidth networks. *Measure:* percentage of frontline headcount activated by site within 30 days. *Governance:* identity still issued and revoked by the HRIS; remote wipe; session timeouts; a privacy statement shown at first sign-in. ### Give the app a reason to be opened every shift Schedules and pay are why hourly workers open an app daily. Put the schedule, shift swaps, coverage requests, pay stubs, PTO, tasks, and checklists in the same app as the news. Communication rides along with utility. This is the "day-one utility loop," and it is the single biggest difference between an intranet with 35% adoption and one with 90%. *Measure:* weekly active users by location; ratio of operational actions (swaps, tasks, PTO) to content views. *Governance:* the HRIS and scheduling system remain the systems of record; the app reads and writes through governed integrations with a clear rule for which fields it may change. ### Make search answer questions Frontline workers do not browse. They ask. AI search grounded in the company's own policies and SOPs should return a short answer, the source document, and nothing the user is not permitted to see. Translate content so a question asked in Spanish gets an answer in Spanish. *Measure:* search success rate (target 75% or higher); zero-result queries per week. *Governance:* permission-aware AI. If the user cannot open the document, the AI cannot answer from it. This is not an optional setting for regulated enterprises; it is the condition for turning AI on at all. For the architecture argument, see [Your AI Agent Is Reading a Copy of Your Business](https://www.mangoapps.com/articles/ai-agents-native-data-vs-copies). ### Target by role, location, and shift, and retire "all company" as the default Relevance drives return visits. A message for the night shift at three distribution centers should reach the night shift at three distribution centers. Reserve mandatory acknowledgment for the messages that matter: safety, policy, compliance. *Measure:* acknowledgment rate on critical posts by site; content engagement by audience segment. *Governance:* acknowledgment records double as compliance evidence. Export them; keep them under the same retention policy as the policy they acknowledge. ### Make managers the channel Frontline adoption runs through the site and shift manager. Give them team pages, a one-minute pre-shift huddle post, and a dashboard showing who on their team has not seen the recall notice or completed the safety course. Train them before launch and make adoption a line in their review. *Measure:* manager posting cadence; manager response time to team questions; adoption at sites where the manager was trained versus not. *Governance:* delegated admin scopes so a store manager can publish to their store and nothing else. ### Design for languages and accessibility Automatic translation for posts, comments, and policies. Text-to-speech and captions. Plain-language versions of the policies that matter most. *Measure:* adoption by primary language; acknowledgment rates by language group. *Governance:* translated policy versions tracked as versions of the master, not as separate documents with separate owners. ### Launch like a product, not a memo Run a 90-day plan (below) with champions per site and floor-level sign-up on launch day. When A.S. Watson launched, Kruidvat employees created their accounts before store managers had even met with them, because the app was intuitive enough not to need formal training. *Measure:* activation on launch day by site; week-4 weekly active users. *Governance:* launch content pre-approved; owners assigned before go-live so nothing is orphaned on day one. ### Measure by location, not in aggregate An aggregate adoption number hides the sites that never started. Report weekly active users, acknowledgment rates, and search success by site, region, and shift, and fix the bottom quartile first. *Measure:* the distribution, not the mean. *Governance:* analytics access scoped by role so a regional manager sees their region. For the feature-level detail on reaching staff without corporate email, see [9 Modern Employee Intranet Features That Reach Frontline Staff Without Email](https://www.mangoapps.com/articles/intranet-features-that-reach-frontline-workers). ## The governance and compliance layer that enables adoption The layer below is what InfoSec, legal, and compliance will ask for. Each item is also an adoption enabler when implemented as structure. ### Identity and lifecycle Accounts created, updated, and deactivated by the HRIS. SSO through SAML or OIDC (Okta, Microsoft Entra ID, Active Directory, LDAP) for staff who have corporate accounts. No-email credentials for staff who do not. SCIM provisioning where supported. Day-one access, termination-day removal, automatically. ### Role-based access and delegated administration Permissions by role, location, and business unit, inherited from the HRIS so they stay current without manual upkeep. Regional and site administrators with scoped rights. Separation of duties between publishing and administration. ### Content governance Every item has an owner, a review date, and an expiry. Version control with one current version and a visible history. Publishing workflows scoped to content type: formal approval for policy and compliance content, light or none for team news. ### Records, audit, and legal Tamper-evident audit logs of administrative actions. Exportable acknowledgment records. Retention policies by content type. eDiscovery and legal hold. ### Security and deployment Encryption at rest (AES-256) and in transit (TLS). Multi-factor authentication. Device controls including remote wipe. A choice of deployment models: SaaS, private cloud, customer VPC, or on-premise. Regional hosting and data-residency options documented, with a subprocessor list and a data processing agreement that names the regulations that apply. ### Governed AI AI assistants and agents inherit the same permissions as the people using them, act on native data rather than copies, and log their actions like any other administrator. An AI that answers from documents the user cannot open is a data-leak path with a friendly interface. | Requirement | Who asks | Evidence to request from the vendor | Adoption benefit | |---|---|---|---| | HRIS-driven identity and deprovisioning | InfoSec, HR | Live demo: create and terminate a worker in a sandbox | Day-one access for every hire, including those with no email | | Role-based permissions and delegated admin | InfoSec, Comms | Permission model documentation; demo of a scoped regional admin | Relevant content per role and site; managers can publish locally | | Content ownership, review, expiry, versioning | Compliance, Comms | Demo of expiry queue and version history | Trust: one current version of every policy | | Audit logs, acknowledgment export, retention, legal hold | Legal, Compliance | Sample export; retention policy configuration | Managers see who has not acknowledged; nothing falls to a paper sheet | | Certifications and deployment options | InfoSec, Procurement | Current SOC 2 Type II report, ISO 27001 certificate, HITRUST or FedRAMP letter where required; deployment options in writing | Procurement clears the platform the frontline will actually use | | Data residency and DPA | Legal, Privacy | Hosting regions, subprocessor list, DPA, transfer mechanisms | Global rollout without a per-country exception process | | Permission-aware AI | InfoSec, Compliance | Demo: ask the AI a question the user is not permitted to see answered | AI search can be turned on for the frontline | ## What compliance requirements should a frontline intranet meet in your industry? The intranet is rarely the regulated system itself. It is where policies are published, acknowledged, and evidenced, where safety and compliance training is assigned and completed, and where communication about regulated processes takes place. That framing keeps the requirements list honest. | Industry | Regulations and frameworks that touch internal communication and records | Intranet capabilities that satisfy them | Certifications procurement will expect | |---|---|---|---| | Healthcare (hospitals, home care, senior living) | HIPAA; Joint Commission standards on hand-off communication; state privacy law | Business associate agreement; policy acknowledgment; audit logs; data-loss controls so protected health information stays out of chat by policy; secure care-team messaging | HITRUST CSF, SOC 2 Type II, HIPAA BAA | | Financial services and insurance | Recordkeeping and supervision expectations for business communications; SOX-related policy attestation | Retention; legal hold; acknowledgment records; audit trails; private cloud or VPC deployment options | SOC 2 Type II, ISO 27001 | | Utilities and energy | NERC CIP awareness training records; safety regulations | Training assignment and completion records; safety alert acknowledgment; on-premise or VPC options | ISO 27001, SOC 2 Type II | | Public sector and government contractors | FedRAMP; Section 508 and WCAG accessibility | FedRAMP-authorized deployment; accessible mobile and web experience | FedRAMP ATO, SOC 2 Type II | | Pharmaceutical and manufacturing | GxP and GMP training and SOP control; OSHA | SOP version control; controlled distribution; training records tied to SOP versions | ISO 27001, SOC 2 Type II | | Retail and hospitality | OSHA; wage-and-hour notice requirements; PCI awareness | Safety training acknowledgment; policy acknowledgment by location; multilingual delivery | SOC 2 Type II | | Global and UK/EU operations | GDPR and UK GDPR; works-council consultation; data residency | DPA and subprocessor list; transfer mechanisms (EU SCCs, UK International Data Transfer Addendum); regional hosting; consultation-friendly privacy statements | ISO 27001, SOC 2 Type II, Cyber Essentials Plus (UK) | ## Which employee intranet software supports governance and compliance for global enterprises? Enterprises with governance-heavy requirements most often shortlist MangoApps, Microsoft SharePoint and Viva, Unily, Staffbase, Simpplr, LumApps, Interact, and Akumina. What separates them is not whether they have permissions (they all do) but which certifications they publish, which deployment models they offer, whether data residency is documented, how deep audit and eDiscovery go, and, critically, whether governance coexists with sign-in for frontline workers who have no corporate email. | Platform | SOC 2 Type II | ISO 27001 | HITRUST | FedRAMP | Deployment options | Data residency | Frontline sign-in without corporate email | Native acknowledgment and audit export | |---|---|---|---|---|---|---|---|---| | [MangoApps](https://www.mangoapps.com/security) | Yes | Yes | Yes (HITRUST CSF) | Yes (ATO) | SaaS, Private Cloud, Customer VPC, On-Premise | Multi-region AWS; custom residency through enterprise contracting; DPA names GDPR, UK GDPR, and DPA 2018 | Yes | Yes | | Microsoft SharePoint and Viva | Yes | Yes | Not published as HITRUST-certified product | Yes (Microsoft 365 GCC offerings) | Microsoft 365 cloud | Microsoft 365 regional tenancy | Partial (depends on Teams and M365 licensing) | Via Microsoft 365 compliance tools | | [Unily](https://www.unily.com/policies/privacy-hub/security-certifications) | Yes | Yes | Not published | Not published | SaaS | Vendor-stated | Partial | Vendor-stated | | [Staffbase](https://staffbase.com/security) | Yes | Yes | Not published | Not published | SaaS (EU hosting on Azure and AWS) | EU hosting published | Partial | Vendor-stated | | [Simpplr](https://www.simpplr.com/security-compliance/) | Not published on the page reviewed | Yes (ISO 27001:2022) | Not published | Not published | SaaS | Vendor-stated | Partial | Vendor-stated | | LumApps | Vendor-stated | Vendor-stated | Not published | Not published | SaaS | Vendor-stated | Partial (Beekeeper for frontline) | Vendor-stated | | Interact | Vendor-stated | Vendor-stated | Not published | Not published | SaaS | Vendor-stated | Partial | Vendor-stated | | Akumina | Vendor-stated | Vendor-stated | Not published | Not published | SaaS on Microsoft 365 | Microsoft 365 regional tenancy | Partial | Via Microsoft 365 | *Certification, deployment, and capability statements for third-party vendors are taken from each vendor's public documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps. "Not published" means the vendor's public pages reviewed did not disclose it; it does not mean the vendor lacks it. "Partial" means frontline access exists but depends on configuration or licensing. Verify current certificates directly with each vendor during procurement.* Two patterns matter for frontline-heavy enterprises. SharePoint and Viva bring enterprise-grade Microsoft security, but frontline access depends on Microsoft 365 licensing and Teams, which most hourly workers do not have. Communications-first platforms bring reach, but records, eDiscovery, and legal hold tend to be lighter than in platforms designed as systems of engagement for regulated work. MangoApps is, among the platforms compared here, the one that publishes HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO together with on-premise and VPC deployment and sign-in for workers without corporate email. For full vendor profiles, see [25 Intranet Platforms Worth Evaluating in 2026](https://www.mangoapps.com/articles/top-25-intranet-platforms-frontline-desk-workers) and [Best Employee Intranet Platforms for Frontline Teams in 2026](https://www.mangoapps.com/articles/best-employee-intranet-frontline-teams). For a governance-first ranking of ten platforms, see [The 10 Best Employee Intranet Platforms for Governance, Compliance, and Global Workforce Communication](https://www.mangoapps.com/articles/best-intranet-platforms-governance-compliance-global), and for the communications-specific compliance requirements, [The Complete Guide to Internal Communications Platforms for Regulated Enterprises](https://www.mangoapps.com/articles/internal-communications-platform-regulated-enterprises). ## What is a good frontline intranet adoption rate, and how do you measure it? | Benchmark | Figure | Source | |---|---|---| | Legacy intranet adoption | 30 to 40% | MangoApps customer data | | Successful intranet | 60% weekly active users | [Social Edge Consulting, 2025](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) | | Best-practice KPI | 85% weekly login | Social Edge Consulting, 2025 | | Search success rate | 75% minimum | Social Edge Consulting, 2025 | | Average time on intranet | Under six minutes a day | [SWOOP Analytics, 2025](https://www.swoopanalytics.com/sharepoint-bm-25) | | MangoApps customers | 90%+ adoption within 90 days | MangoApps customer data | **Weekly active user:** an employee who opened the app and took at least one action in a seven-day window. **Acknowledgment rate:** the share of the targeted audience that confirmed a mandatory-read message. **Search success rate:** the share of searches that end in an opened result or an accepted answer rather than a repeat search or abandonment. Report on a cadence that matches the decision each metric supports: - **Weekly:** weekly active users by location and shift; acknowledgment rate on the week's critical posts. - **Monthly:** search success and zero-result queries; content freshness (share of content past its review date); manager response time. - **Quarterly:** applications retired; survey participation by location; turnover by adoption cohort. ## A 90-day frontline intranet adoption plan | Phase | Weeks | Actions | Governance checkpoint | Metric | |---|---|---|---|---| | Foundation | 0 to 2 | Connect the HRIS; configure SSO and no-email sign-in; assign content owners and review dates; define delegated admin scopes; choose two pilot sites | Identity model approved by InfoSec; retention and acknowledgment policies written; privacy statement approved | HRIS sync accuracy by site | | Seed utility | 3 to 4 | Publish schedules, pay access, and the 20 most-searched SOPs; train managers; recruit a champion per site | Policy content passes formal approval; team news set to light approval | Manager training completion | | Launch | 5 to 6 | Floor launch with QR sign-up at pilot sites; first critical alert with mandatory acknowledgment; translation on | Acknowledgment export tested and filed | Day-1 activation; acknowledgment rate | | Expand | 7 to 10 | Roll out by region; retire two legacy channels (the WhatsApp group, the paper sign-off sheet); review the content expiry queue | Audit log review; first retention run | Weekly active users by site | | Benchmark | 11 to 13 | Compare every site against the 60% and 85% benchmarks; fix the bottom quartile; report to leadership | Quarterly governance review: owners, expiries, permissions | Distribution of weekly active users; search success | The checklists behind this plan, along with the RFP template and benchmarks, are in the [2026 Intranet Buyer's Guide for a Frontline Workforce](https://www.mangoapps.com/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026). ## Where MangoApps fits MangoApps is the AI-Ready Employee Platform for the Frontline. It was built for organizations where most employees do not sit at a desk, and its adoption numbers come from that design: one branded app for communication, schedules, tasks, training, and HR self-service, with no corporate email required, and customers averaging more than 90% adoption within 90 days against the 30 to 40% legacy intranets typically reach. The governance layer is native rather than added on. Identity is provisioned from the HRIS. Permissions follow role, location, and business unit. Audit logs are real-time and exportable, with eDiscovery, legal hold, and retention policies. MangoApps holds HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO, offers HIPAA business associate agreements and GDPR data processing agreements, and deploys as SaaS, Private Cloud, Customer VPC, or On-Premise, per [mangoapps.com/security](https://www.mangoapps.com/security). MangoApps AI runs on the platform's own permissioned data, so it can be turned on for the frontline without creating a new leak path. The proof that adoption and governance coexist is the [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee): 90%+ active adoption within 90 days, or MangoApps works to make it right. MangoApps serves 2M+ users, with 98% customer retention and an NPS of 78. Customers include [TeamHealth](https://www.mangoapps.com/resources/teamhealth-case-study) in healthcare, [Merchants Bonding Company](https://www.mangoapps.com/resources/merchants-bonding-case-study) in insurance, and A.S. Watson and [Raley's](https://www.mangoapps.com/resources/raleys-case-study) in retail. ## Frequently asked questions **Why do companies struggle with frontline employee intranet adoption?** Five causes account for most failures: sign-in requires a corporate email most frontline workers do not have; the intranet has no daily utility because schedules, pay, and tasks live elsewhere; search returns documents instead of answers; managers were never enabled or made accountable; and adoption is measured in aggregate, which hides sites that never started. Only 13% of employees use their intranet daily and 31% never do, per Social Edge Consulting. **What is a good intranet adoption rate for frontline employees?** Social Edge Consulting benchmarks 60% weekly active users as a successful intranet and 85% weekly login as best practice. Legacy intranets typically reach 30 to 40%. MangoApps customers average more than 90% adoption within 90 days. Measure by location and shift, not in aggregate. **How do you increase intranet adoption among employees without corporate email?** Issue identity from the HR system rather than the email system, let workers sign in by SMS, QR code, or employee ID on a personal phone or shared kiosk, put schedules and pay in the same app as the news, make managers the channel, and measure weekly active users by site. Deskless workers are 70 to 80% of the global workforce, so email-gated access excludes most of the people the intranet was bought to reach. **Does stronger intranet governance reduce adoption?** Only when governance is implemented as friction: email-only login, VPN, and approval queues for every post. Implemented as structure, the same controls raise adoption: HRIS-driven identity gives every hire day-one access, role-based content makes the feed relevant, and acknowledgment records show managers who still needs to read a notice. **Which employee intranet software supports governance and compliance for global enterprises?** Enterprises shortlist MangoApps, Microsoft SharePoint and Viva, Unily, Staffbase, Simpplr, LumApps, Interact, and Akumina. Compare published certifications (SOC 2 Type II, ISO 27001, HITRUST, FedRAMP), deployment options, documented data residency, audit and eDiscovery depth, and whether frontline workers can sign in without a corporate email. MangoApps publishes HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO with SaaS, private cloud, VPC, and on-premise options. **What compliance certifications should an enterprise intranet vendor hold?** SOC 2 Type II and ISO 27001 as a baseline. HITRUST CSF for healthcare and other organizations handling protected health information. FedRAMP for U.S. public sector. In the UK, InfoSec teams also look for Cyber Essentials Plus. Ask for current certificates and reports rather than logos. **How do you measure frontline intranet adoption?** Track weekly active users by location and shift, acknowledgment rate on critical posts, search success rate (75% minimum), content freshness, and manager response time. Review weekly, monthly, and quarterly, and fix the bottom-quartile sites first. **How long should a frontline intranet rollout take?** A 90-day plan is realistic: two weeks for identity, permissions, and content ownership; two weeks to seed schedules, pay, and top SOPs and train managers; two weeks to launch at pilot sites; four weeks to expand by region and retire legacy channels; and three weeks to benchmark every site and fix the laggards. ## Sources - BCG, [Facing the Deskless Labor Shortage with Technology](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) (2024) - Deloitte, [Frontline Worker Productivity Enabled by Technology](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html) - Staffbase, [2025 International Employee Communication Impact Study](https://staffbase.com/blog/employee-communication-impact-study-2025) - Social Edge Consulting, [Top 12 Intranet KPIs and Metrics](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) (2025) - SWOOP Analytics, [2025 SharePoint Intranet Benchmarking Report](https://www.swoopanalytics.com/sharepoint-bm-25) - Gallup, [This Fixable Problem Costs U.S. Businesses $1 Trillion](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) (2019) - SHRM, [Employees With a Positive Employee Experience Are 68% Less Likely to Consider Leaving](https://www.shrm.org/about/press-room/employees-with-a-positive-employee-experience-are-68--less-likel) (2023 research) - Vendor security pages: [MangoApps](https://www.mangoapps.com/security), [Staffbase](https://staffbase.com/security), [Unily](https://www.unily.com/policies/privacy-hub/security-certifications), [Simpplr](https://www.simpplr.com/security-compliance/) --- # The Complete Guide to Frontline Communication Platforms in 2026 **Author:** Andy Tolton **Published:** 2026-09-08 **Category:** frontline-communication How enterprise buyers evaluate frontline communication platforms that also run scheduling, tasks, training, and HR self-service, and how ten leading platforms compare on HR and IT integration. > **Quick answer:** A frontline communication platform reaches employees who have no desk, corporate email, or laptop, on the phone they already carry. Unlike a standalone communication app, it also runs scheduling, tasks, training, and HR self-service on the same platform, and it syncs identity and employee data from the HR and IT systems you already own. For multi-location U.S. enterprises, the platforms most often shortlisted in 2026 are MangoApps, WorkJam, Beekeeper (LumApps), Staffbase, Blink, Connecteam, YOOBIC, Flip, Speakap, and Firstup. The deciding criteria are sign-in without corporate email, operations workflows that are native rather than bolted on, and live integration with the HRIS and identity provider. A store manager in Ohio photographs next week's schedule and posts it to a WhatsApp group. A safety notice about a recalled ladder goes out by email to a warehouse crew that has never been issued an inbox. A new hire in a hospital kitchen completes onboarding on a shared desktop in a back office, then never logs in again because the only way back in is a corporate credential she does not have. None of these are communication failures in the narrow sense. The message was written. It was sent. It went to a channel the frontline never opens. Deskless workers make up 70 to 80% of the global workforce, about 2.7 billion people, according to [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology). In the United States, [JLL](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention) puts the frontline share at 58% of all workers. Most enterprise software was designed for the other 42%. Frontline communication platforms exist to close that gap. But the category has changed. In 2026, the buying decision is less about whether a platform can push a news post to a phone (they all can) and more about what else happens in the same app once the worker opens it, and which systems the platform talks to behind the scenes. This guide covers the category definition, the five capability layers to evaluate, how these platforms integrate with HR and IT systems, a comparison of the ten platforms most often shortlisted by multi-location enterprises, and a practical evaluation process. ## What is a frontline communication platform? A frontline communication platform is software that delivers company information to deskless employees on their own mobile devices, without requiring a corporate email address, a laptop, or a VPN, and that connects that communication to the daily work those employees do: their shifts, their tasks, their training, and their HR records. The "platform" qualifier matters. A frontline communication *app* solves reach: it gets a message from headquarters to a retail floor. A frontline communication *platform* solves reach and then keeps the worker in the app because their schedule, their pay stub, their checklist, and their compliance training live there too. That distinction drives adoption, and adoption is the only metric that makes any of this worth buying. The people this category serves are the ones customers actually see: store associates, nurses and aides, warehouse and plant crews, drivers, field technicians, hotel housekeepers, restaurant staff, and the site and shift managers who lead them. Their device reality is a personal smartphone, a shared tablet or kiosk in a break room, and, increasingly, digital signage on a plant floor. ### How frontline communication platforms differ from adjacent tools Buyers regularly confuse five categories that overlap on features but differ on who they were built for. | Category | Built for | Requires corporate email? | Communication | Scheduling and time | Tasks | Training | HR self-service | Typical buyer | |---|---|---|---|---|---|---|---|---| | Internal communications software | Headquarters communicators reaching a mostly desk-based workforce | Usually | Deep | No | No | No | No | Internal comms | | Modern intranet | Knowledge and news for the whole company | Often | Yes | Rarely | Rarely | Sometimes | Sometimes | Comms, IT | | Frontline communication app | Deskless workers who need news, chat, and documents on a phone | No | Deep | Via integration | Light | Light | Via integration | Comms, HR | | Workforce management (WFM) suite | Labor planning, scheduling, and time for hourly staff | Varies | Light | Deep | Sometimes | No | Partial | Operations, HR | | Frontline communication platform | Every employee, with communication tied to schedules, tasks, training, and HR on one login | No | Deep | Native | Native | Native | Native | Comms, Ops, HR, IT together | For the headquarters-centric category, see our guide to [the best internal communications software](https://www.mangoapps.com/articles/best-internal-communications-software). For the app category ranked on communication alone, see [the best frontline communication software of 2026](https://www.mangoapps.com/articles/best-frontline-communication-software). This guide sits above both: it evaluates the platform question. ## Why is frontline communication an operations problem, not just a communications problem? Because the reach problem and the tool-sprawl problem are the same problem. When communication lives in one app and schedules, tasks, and training live in three others, the worker has no daily reason to open the communication app, so the message does not land no matter how well it was targeted. The numbers describe a workforce that is under-equipped and over-toggled at the same time. Only 23% of frontline workers believe they have access to the technology they need to be productive, according to [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html), and the same research estimates productivity rises about 22% when frontline workers get a thoughtful mix of tools rather than a pile of them. Meanwhile the average company now runs 101 applications, and companies with more than 5,000 employees average 131, according to [Okta's Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/). A [Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) study of three Fortune 500 companies found workers toggling between applications and websites roughly 1,200 times a day, about four hours a week spent reorienting. The human cost shows up in the turnover data. BCG's survey of deskless workers found 53% feel burned out and 43% are actively looking for a new job. [Gallup](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) puts the cost of replacing an employee at one-half to two times annual salary, and calls that a conservative estimate. In its [State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) report, Gallup found global engagement at 20% and estimated the cost of low engagement at roughly $10 trillion, or 9% of global GDP. The upside is just as measurable: Gallup's [Q12 meta-analysis](https://www.gallup.com/workplace/236927/employee-engagement-drives-growth.aspx) shows top-quartile engagement units deliver 23% higher profitability, 18% higher productivity, 81% lower absenteeism, and 64% fewer safety incidents than bottom-quartile units. In healthcare the stakes are clinical. The Joint Commission Center for Transforming Healthcare has estimated that [80% of serious medical errors](https://www.hipaajournal.com/effects-of-poor-communication-in-healthcare/) involve miscommunication between caregivers during patient handoffs. One phrase should govern every evaluation in this category: **sent is not received.** A platform that can show which locations, shifts, and roles acknowledged a critical message, and which did not, turns communication into an operational record. A platform that reports only opens is a newsletter tool with a mobile app. For a longer argument on why this category is consolidating, read [Why the Employee App Market Is Really a Consolidation Problem](https://www.mangoapps.com/articles/employee-app-market-consolidation-problem). ## What are the five capability layers to evaluate in a frontline communication platform? Evaluate the platform as five layers stacked on two foundations. The layers are communication, scheduling and time, tasks and execution, training and knowledge, and HR self-service. The foundations are identity without corporate email, and integration with the HR and IT systems of record. Most vendors are strong on one or two layers. Very few are native across all five. ### Layer 1: Communication and reach **What it covers.** Targeted news and announcements by role, location, shift, department, or any HRIS attribute. Critical alerts with mandatory read receipts and escalation. Delivery across mobile push, SMS, digital signage, and email. Two-way channels: comments, chat, pulse surveys, recognition. Automatic translation. Engagement analytics by location and team. **What to look for.** Targeting that reads from the HRIS rather than from manually maintained lists. Acknowledgment records that export for audit. Signage and kiosk delivery for shared spaces where personal phones are not allowed. **Ask the vendor.** "Show me which of my 400 locations had the lowest read rate on last week's safety alert, and how a regional manager would see that without asking corporate." **Red flag.** Analytics that stop at opens and clicks. ### Layer 2: Scheduling, availability, and time **What it covers.** Schedule publishing to the phone. Shift swaps and coverage requests. Availability management. AI-assisted schedule creation. Mobile clock-in with geofencing. Manager approvals for time and attendance. **What to look for.** The schedule is why hourly workers open an app every day. If it lives in the communication app, communication rides along with it. If it lives elsewhere, the communication app becomes optional. Evaluate whether scheduling is native, or whether the vendor embeds a link to your existing WFM tool (useful, but not the same thing). **Ask the vendor.** "Can an employee see their schedule, request coverage, and have the swap approved without leaving this app, and does the approved change flow back to payroll?" **Red flag.** Scheduling described as "available through our partner ecosystem" with no named integration and no demo. ### Layer 3: Tasks and store execution **What it covers.** Task assignment and daily checklists. Photo verification. Audits and inspections. Multi-location rollouts with live completion dashboards for regional and corporate managers. **What to look for.** Managers should see completion status across every site without chasing updates. Workers should complete tasks on the phone they already carry, in the same app where they read the announcement that created the task. **Ask the vendor.** "Assign a planogram reset to 120 stores, require a photo, and show me the completion view a district manager sees an hour later." **Red flag.** Task data that lives in a separate product with a separate login. ### Layer 4: Training and knowledge **What it covers.** Mobile microlearning. Compliance certifications assigned automatically by role and location. Completion tracking managers can see in real time. Searchable SOPs and policies, with AI search that returns an answer rather than a list of documents. **What to look for.** Training assigned from the same role and location data that drives communication targeting, so a new hire's day-one course arrives without an administrator touching it. Search that respects permissions. **Ask the vendor.** "A new hire in a Texas store starts Monday. Walk me through what training appears on her phone, who assigned it, and what her manager sees on Friday." **Red flag.** Training that requires a separate LMS login. ### Layer 5: HR self-service **What it covers.** Pay stubs, PTO requests, benefits information, policy acknowledgment, onboarding and offboarding tasks, employee data changes. The HRIS remains the system of record; the platform is the front door. **What to look for.** Read and write. Viewing a pay stub is table stakes. Submitting a PTO request that lands in Workday or UKG, with the approval flowing back, is the differentiator. **Ask the vendor.** "Which HR transactions can an hourly worker complete in the app, and which only display information from the HRIS?" **Red flag.** HR "integration" that means a web link to the HRIS login page. ### Native or bolted on: how to tell | Signal | Native platform | Bolted-on stack | |---|---|---| | Login | One login for every workflow | Separate credentials per tool, or SSO that still bounces between apps | | Employee record | One profile from the HRIS drives targeting, scheduling, training, and permissions | Profiles duplicated and reconciled per tool | | Notifications | One notification center | Separate push streams that compete for attention | | Analytics | Cross-workflow (who read the alert, completed the task, finished the training) | Siloed reports per product | | Administration | One admin console, one vendor accountable | Several consoles and vendors, and finger-pointing when something breaks | The layers map to MangoApps [internal communications](https://www.mangoapps.com/solutions/internal-communications), [workforce operations](https://www.mangoapps.com/solutions/workforce-operations), [learning management](https://www.mangoapps.com/solutions/learning-management), and [knowledge management](https://www.mangoapps.com/solutions/knowledge-management) suites, which is the shape a unified platform takes in practice. ## How do frontline employee platforms integrate with existing HR and IT systems? The HRIS is the source of truth for who works where. A frontline platform syncs identity, org structure, and attributes from it, authenticates staff through the company's identity provider where they have an account, issues no-email credentials to staff who do not, and pushes schedule, time, training, and acknowledgment data back to payroll, learning, and compliance systems. Integration depth, not integration count, is what determines whether the platform works on day 90. ### The HR and IT integration checklist | Integration | Systems to name in the RFP | Why it matters for frontline | What good looks like | Verify in the demo | |---|---|---|---|---| | HRIS / HCM sync | Workday, UKG, ADP, SAP SuccessFactors, Paylocity, Rippling, BambooHR, Oracle HCM | Audience lists, schedules, and permissions stay current without manual upkeep | Scheduled and event-driven sync of people, roles, locations, managers | Create a worker in the HRIS sandbox; watch them appear in the right location | | Identity and SSO | SAML 2.0, OIDC, Okta, Microsoft Entra ID, Active Directory, LDAP, SCIM | Desk staff use existing credentials; deprovisioning is automatic | SCIM provisioning and deprovisioning, MFA support | Terminate the sandbox worker; confirm access ends | | No-email identity | SMS one-time codes, QR onboarding, employee ID plus PIN, badge tap | Most frontline workers have no corporate email | HRIS-provisioned accounts activated on the floor in under two minutes | Sign in as a worker with no email address | | Payroll and time | Payroll provider, time clock | Clock-ins and approved swaps must reach payroll | Bidirectional time data | Approve a shift swap; trace it to payroll | | Scheduling / WFM coexistence | UKG, Kronos, Legion, existing scheduler | Many enterprises keep an incumbent scheduler | Schedules display and swaps route back, or native scheduling replaces it | Ask which model applies and see it | | Microsoft 365 and Google Workspace | Teams, SharePoint, OneDrive, Outlook; Drive, Calendar, Meet | Desk staff and documents already live here | Federated search and embedded files, no duplicate copies | Search a SharePoint policy from the phone | | ITSM and service desk | ServiceNow | Frontline IT and facilities tickets | Ticket creation and status from the app | Open a ticket for a broken register | | Learning | Cornerstone, Workday Learning, native LMS | Compliance records | Completions written back to the record | Complete a course; find it in the HRIS | | Recognition and rewards | Workhuman, WorkTango, Achievers | Engagement programs | Recognition in the feed | Send recognition; confirm it posts | | File storage | SharePoint, OneDrive, Google Drive, Box, Dropbox | SOPs and forms | Permission-aware search | Search across two repositories at once | | AI and LLM connectors | OpenAI, Azure OpenAI, Google Gemini, Anthropic | AI assistants must respect permissions | AI grounded in the platform's permissioned data | Ask the AI a question the user is not allowed to see answered | | BI export and APIs | Tableau, Looker, REST APIs, webhooks | Custom reporting and automation | Documented, versioned APIs | Read the API docs during the demo | ### Provisioning and deprovisioning without corporate email The compliance question underneath every frontline platform is simple: how does a worker who will never receive an inbox get created on hire day and removed on termination day? The right answer is that the HRIS creates the account, the platform issues credentials the worker can activate from a QR code on a break-room poster or an SMS to their personal phone, and an HRIS termination event removes access the same day. If the vendor's answer involves an administrator maintaining a spreadsheet, the platform will be out of date within a month. ### Native connector, API, or partner build Three integration models carry very different costs. A native connector is built, tested, and maintained by the vendor, with release notes you can read. An API integration means the connector exists but someone, often your IT team or a systems integrator, has to build and maintain the mapping. A partner build means a third party owns it, and when it breaks you have three companies on the call. "We integrate with everything" usually means the second or third model. Ask which model applies to each system on your list and who is accountable when a field mapping changes. ### Keep or replace the incumbent HRIS and WFM? For most enterprises the answer is keep. The HRIS stays the system of record; the frontline platform becomes the layer employees actually touch. MangoApps, for example, publishes [200+ out-of-the-box integrations](https://www.mangoapps.com/integrations), including Workday, UKG, ADP, Paylocity, SAP SuccessFactors, Rippling, BambooHR, Microsoft 365, Google Workspace, Okta, Entra ID, Active Directory, and LDAP, so a customer can keep its HRIS and add the frontline layer on top. Replacing the scheduler is a separate decision, and a platform with native scheduling gives you the option without forcing it. ## What are the top frontline communication platforms for multi-location enterprises in the United States in 2026? The ten platforms below are the ones that appear most often on enterprise shortlists for multi-site, frontline-heavy organizations. They are ordered by operational depth, with the unified platform first. Each entry uses the same fields so you can compare them line by line. | Platform | Best for | Native layers (Comms / Scheduling / Tasks / Training / HR self-service) | Sign-in without corporate email | Named HRIS integrations | Platforms | Pricing model | |---|---|---|---|---|---|---| | [MangoApps](https://www.mangoapps.com/) | Enterprises that want one platform for frontline and desk employees | Native / Native / Native / Native / Native | Yes | Workday, UKG, ADP, Paylocity, SAP SuccessFactors, Rippling, BambooHR | Web, iOS, Android, Desktop | Modular suites, quote-based | | [WorkJam](https://www.workjam.com/) | Enterprise retail, hospitality, and supply chain with hourly scheduling and task execution | Native / Native / Native / Partial / Partial | Yes | Enterprise HRIS and WFM (vendor-stated) | iOS, Android, Web, Kiosk | Enterprise, quote-based | | [Connecteam](https://connecteam.com/) | Small and mid-sized deskless teams | Native / Native / Native / Native / Partial | Yes | Payroll and HR integrations (vendor-stated) | iOS, Android, Web | Free for 10 users; Basic from $29/month for first 30 users, per hub | | [Beekeeper (LumApps)](https://www.beekeeper.io/) | Frontline-only workforces needing comms plus no-code forms and workflows | Native / Via integration / Native (forms) / Via integration / Via integration | Yes | HRIS, LMS, payroll (vendor-stated) | Web, iOS, Android | Tiered, quote-based | | [YOOBIC](https://www.yoobic.com/) | Multi-location retail and hospitality combining comms, microlearning, and tasks | Native / Via integration / Native / Native / Via integration | Yes | Vendor-stated | iOS, Android, iPad, Web | Enterprise, quote-based | | [Flip](https://www.getflip.com/) | Enterprises wanting a fully branded app with HRIS mini-apps | Native / Via HRIS / Partial / Via integration / Via HRIS | Yes | Workday, SAP SuccessFactors, UKG (vendor-stated) | iOS, Android, Web | Enterprise, quote-based; integrations priced separately (vendor-stated) | | [Staffbase](https://staffbase.com/) | Large mixed workforces needing multichannel publishing and Microsoft 365 depth | Native / No / No / Via integration / Via integration | Partial | Microsoft 365 depth; HRIS via integration | Web, iOS, Android, Desktop, Signage | Enterprise, quote-based | | [Blink](https://www.joinblink.com/) | Frontline-only organizations wanting a branded super-app with micro-apps | Native / Via micro-apps / Light / Via integration / Via micro-apps | Yes (SMS, QR) | Microsoft 365, Workday, SAP (vendor-stated) | Web, iOS, Android, Desktop | Business and Enterprise tiers, quote-based | | [Speakap](https://www.speakap.com/) | Mid-market frontline industries wanting a white-label app with low IT involvement | Native / Via integration / Light / Partial (journeys) / Via integration | Yes | HR, scheduling, POS via API marketplace (vendor-stated) | Web, iOS, Android | Tiered, quote-based | | [Firstup](https://firstup.io/) | Large enterprises needing AI-orchestrated communication at scale | Native / No / No / No / Via integration | Partial | Workday, UKG, Concur, Microsoft 365 (vendor-stated) | Web, iOS, Android, Signage | Enterprise, quote-based | *Capability, integration, pricing, and certification statements for third-party vendors are taken from each vendor's public documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps. "Partial" means the capability exists but depends on configuration or a licensed add-on. "Via integration" means the vendor relies on a third-party system.* MangoApps 4.6/5 Stars · Gartner Peer Insights 2M+ Users · Trusted Worldwide Gartner MQ Visionary · Intranet Packaged Solutions (2025) IDC MarketScape Leader · Employee Experiences (2024) Forrester Wave Strong Performer · Intranet Platforms (Q2 2026) Reworked IMPACT Award (Gold) · Intranet & Communications Platforms **Best for:** Multi-location enterprises with 1,000 to 100,000+ employees that want communication, scheduling, tasks, training, and HR self-service for frontline and desk staff on one platform, with no corporate email required. [MangoApps](https://www.mangoapps.com/) is the AI-Ready Employee Platform for the Frontline. It has been built for organizations where most employees do not sit at a desk for 18+ years, and that shows in the shape of the product: communication is one of five native layers rather than the whole product. A store associate opens one app to read the morning briefing, check the schedule, request a swap, complete the planogram checklist with a photo, finish a compliance course, and pull up a pay stub. A regional manager opens the same app to see which stores acknowledged the recall notice, which completed the reset, and which have open shifts tomorrow. **Native capabilities** - **[Internal Communications](https://www.mangoapps.com/solutions/internal-communications):** Targeted news, campaigns, and journeys by role, location, shift, or any HRIS attribute; delivery across mobile push, SMS, digital signage, and email; automatic translation; engagement analytics by location and team. - **[Critical Alerts](https://www.mangoapps.com/key-features/critical-alerts):** Mandatory read receipts, escalation rules, and exportable acknowledgment records for safety, compliance, and operational notices. - **[Shift Scheduling, Time and Attendance](https://www.mangoapps.com/solutions/workforce-operations):** AI-assisted schedule creation, coverage requests, swaps, availability, mobile clock-in with geofencing, and manager approvals, in the same app as communication. - **[Frontline Task Management and Store Execution](https://www.mangoapps.com/solutions/task-management):** Checklists, audits, photo verification, and multi-location rollouts with live completion dashboards. - **[Frontline Learning Management](https://www.mangoapps.com/solutions/learning-management):** Onboarding, certifications, and microlearning assigned automatically by role and location, with real-time completion tracking. - **[Knowledge Management](https://www.mangoapps.com/solutions/knowledge-management):** Policies and SOPs in one searchable hub, with AI search that returns permission-correct answers. - **[HR Operations](https://www.mangoapps.com/solutions/hr-operations):** Onboarding, offboarding, policy acknowledgment, and employee self-service connected to the HRIS. **HR and IT integrations:** [200+ out-of-the-box integrations](https://www.mangoapps.com/integrations), including Workday, UKG, ADP, Paylocity, Namely, BambooHR, SAP SuccessFactors, and Rippling for HRIS; Microsoft Teams, SharePoint, OneDrive, Outlook, and Entra ID; Google Drive, Calendar, and Meet; SAML 2.0 (Okta, OneLogin, Ping Identity), OIDC, Active Directory, and LDAP for identity; Cornerstone and Workday Learning; Workhuman, WorkTango, and Achievers; Box and Dropbox; and OpenAI, Google Gemini, Anthropic Claude, and Azure OpenAI for AI. **Frontline access:** No corporate email, VPN, or managed device required. Identity is provisioned from the HRIS. Offline access, translation, and kiosk and digital signage delivery are included. **Security and deployment:** HITRUST CSF, SOC 2 Type II, ISO 27001, FedRAMP ATO, HIPAA (BAA available), and GDPR (DPA available), with SaaS, Private Cloud, Customer VPC, and On-Premise deployment options, per [mangoapps.com/security](https://www.mangoapps.com/security). **What customers say:** A.S. Watson Benelux operates 1,700 stores across four countries with 27,000 employees, most in their early twenties and none with a company email address. Before MangoApps, schedule changes were posted as WhatsApp photos. After deploying MangoApps as a branded employee app, more than 80% of Kruidvat's 16,000+ employees became active users, and 20,000+ retail employees now receive weekly schedules in the app. "There are 16,000 employees in Kruidvat, and they all use the mobile app to access MangoApps," said Jan Kees Fokkens, Social Intranet Project Manager, A.S. Watson Benelux. In healthcare, [Benchmark Human Services](https://www.mangoapps.com/customers/benchmark-human-services), with more than 4,000 employees, deployed MangoApps to reach caregivers who have no corporate email and work in client homes across the country. **Key considerations:** The platform delivers the most value when adopted across the organization rather than by one department, and enterprises should plan configuration time upfront to take advantage of its flexibility. Organizations under 500 employees that want a free tier will find Connecteam a better starting point. **Pricing:** Modular suites, quote-based. Every deployment is backed by the [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee): 90%+ active adoption within 90 days, or MangoApps works to make it right. MangoApps reports 98% customer retention and an NPS of 78. **Platforms:** Web, iOS, Android, Desktop [Schedule a demo to see MangoApps in action](https://www.mangoapps.com/schedule-a-call) WorkJam **Best for:** Enterprise retail, hospitality, and supply chain organizations whose primary problem is coordinating open shifts, task completion, and time-sensitive announcements across large hourly workforces. WorkJam is a digital frontline workplace platform that combines communications, shift scheduling, task management, and earned wage access in one app. It is strongest where operations leads the buying decision: an open-shift marketplace, employee-driven swaps and availability, and task management with photo verification so managers can confirm store execution remotely. **Native capabilities:** Communications, scheduling and shift marketplace, task management with photo verification, ExpressPay earned wage access. Training and HR self-service are available but lighter than the scheduling and task core. **HR and IT integrations:** Enterprise HRIS and WFM integrations (vendor-stated); confirm named systems and the direction of data flow for your stack. **Frontline access:** Mobile app plus kiosk mode for shared devices. **Key considerations:** Communication depth is oriented to operational messaging rather than campaign-style internal communications. Enterprises that also need a desk-worker intranet will typically run WorkJam alongside another platform. **Pricing:** Enterprise, quote-based. **Platforms:** iOS, Android, Web, Kiosk [Explore WorkJam](https://www.workjam.com/) Connecteam **Best for:** Small and mid-sized deskless teams, and organizations evaluating the category for the first time, that want communications bundled with scheduling, time tracking, tasks, and basic HR in one affordable app. Connecteam is an all-in-one workforce management app for deskless teams organized into three hubs: Operations, Communications, and HR and Skills. Buyers can start with communications alone and add operations or HR without switching platforms. It is the most accessible entry point in the category because of its published pricing and free tier. **Native capabilities:** News feed, chat, surveys, and directory; scheduling and job dispatch; GPS time clock; forms, checklists, and documents; courses and training; basic HR tools. **HR and IT integrations:** Payroll and HR integrations (vendor-stated); enterprise HRIS depth is more limited than the enterprise platforms on this list. **Frontline access:** Mobile-first; no corporate email required. **Key considerations:** Built for the SMB and mid-market. Enterprises with 5,000+ employees, complex permissions, or regulated-industry requirements typically outgrow it. **Pricing:** Free for up to 10 users; Basic tier from $29/month for the first 30 users, priced per hub, with annual billing discounted 18% ([connecteam.com/pricing](https://connecteam.com/pricing/), September 2026). **Platforms:** iOS, Android, Web [Explore Connecteam](https://connecteam.com/) Beekeeper (LumApps) **Best for:** Frontline-only or frontline-heavy organizations whose workers need more than a news feed: forms, workflows, and translation across many languages, with communication as the anchor. Beekeeper is a frontline success platform built exclusively for deskless workers. Targeted news streams, secure 1:1 and group chat, voice messaging, inline AI translation across 200+ languages, and no-code, offline-capable forms and workflows make it a strong fit for hospitality, manufacturing, and logistics workforces. [LumApps agreed to acquire Beekeeper on July 2, 2025](https://www.lumapps.com/insights/news/lumapps-and-beekeeper-to-join-forces-creating-the-leading-employee-experience-platform-for-the-future-of-work), positioning the combined company as an AI-powered employee hub spanning frontline and desk workers. Buyers should ask about the integrated roadmap in procurement conversations. **Native capabilities:** Communication, chat, forms and workflows. Shift management, training, and HR self-service are delivered through HRIS, LMS, and payroll integrations (vendor-stated). **HR and IT integrations:** HRIS, LMS, and payroll integrations (vendor-stated). **Frontline access:** Mobile-first, no corporate email required, offline-capable forms. **Key considerations:** Desk-worker intranet capabilities come from LumApps rather than Beekeeper itself; confirm how the two products are licensed and administered together. **Pricing:** Tiered, quote-based. **Platforms:** Web, iOS, Android [Explore Beekeeper](https://www.beekeeper.io/) YOOBIC **Best for:** Multi-location retail, hospitality, and consumer goods organizations that want daily briefings, microlearning, and operational checklists in one app for store and site teams. YOOBIC is a frontline employee experience platform that brings communications, microlearning, and task management together. Photo and video task verification supports store compliance, visual merchandising, and audit workflows, and a gamified newsfeed with recognition is designed to drive daily engagement. **Native capabilities:** Communication, microlearning, task execution with photo and video verification. **HR and IT integrations:** Vendor-stated; scheduling and HR self-service depend on integration with existing systems. **Frontline access:** Mobile-first, no corporate email required. **Key considerations:** Scheduling and HR self-service are not core; organizations that want those in the same app will pair YOOBIC with a WFM or HRIS front end. **Pricing:** Enterprise, quote-based. **Platforms:** iOS, Android, iPad, Web [Explore YOOBIC](https://www.yoobic.com/) Flip **Best for:** Enterprises that want an app published under their own brand in the app stores, with HRIS data surfaced inside it and no corporate email requirement. Flip is an AI-native employee app for frontline teams. Its HR mini-apps connect Workday, SAP SuccessFactors, and UKG so payslips, leave requests, and shift information appear inside the branded app. It supports 30+ languages with automatic translation and offers chat, voice and video calling, livestreaming, and peer community spaces. **Native capabilities:** Communication, chat, community. Schedules, pay, and leave are surfaced from the HRIS rather than managed natively. **HR and IT integrations:** Workday, SAP SuccessFactors, UKG via HR mini-apps and API (vendor-stated). Integrations are priced separately and require implementation effort (vendor-stated). **Frontline access:** Branded app on iOS and Android, no corporate email required. **Key considerations:** Lacks a page-based information architecture, which limits structured content for desk staff. Native scheduling and task depth are lighter than operations-first platforms. **Pricing:** Enterprise, quote-based; per-user or banded tiers. **Platforms:** iOS, Android, Web [Explore Flip](https://www.getflip.com/) Staffbase **Best for:** Large enterprises with mixed desk and frontline workforces whose communications team needs to publish once and deliver across app, intranet, email, SMS, and signage, with deep Microsoft 365 integration. Staffbase is an enterprise employee communications and intranet platform. Its multichannel publishing, AI-assisted content and translation across 75+ languages, and "Smart Impact" measurement of comprehension and action make it a communications team's platform first. Staffbase publishes ISO 27001 and SOC 2 Type II certifications and EU hosting on Azure and AWS, per [staffbase.com/security](https://staffbase.com/security). **Native capabilities:** Communication and intranet. Scheduling and tasks are not part of the platform; training and HR self-service are via integration. **HR and IT integrations:** Deep Microsoft 365 integration including Teams, SharePoint, Copilot, and Power BI; HRIS via integration (vendor-stated). **Frontline access:** Mobile app; frontline sign-in options depend on configuration (Partial). **Key considerations:** Operations and HR buyers will need separate tools for scheduling, tasks, and training. Content governance and enterprise search are stronger in dedicated intranet platforms. **Pricing:** Enterprise, quote-based. **Platforms:** Web, iOS, Android, Desktop, Digital Signage [Explore Staffbase](https://staffbase.com/) Blink **Best for:** Frontline-only organizations in retail, hospitality, logistics, healthcare, and transit that want a branded super-app experience and a single front door to existing web tools. Blink is a mobile-first employee super-app. Employees sign in with a mobile number, and the platform combines a news feed with mandatory-read acknowledgment, secure chat, and a content hub that surfaces existing web tools such as payroll portals and rostering systems as micro-apps behind one sign-in. Blink IQ analytics report engagement by team, manager, and location. **Native capabilities:** Communication, chat, acknowledgment. Scheduling, pay, and training are surfaced from other systems through micro-apps. **HR and IT integrations:** Microsoft 365, Workday, SAP (vendor-stated); SharePoint content surfaced without additional Microsoft licenses (vendor-stated). **Frontline access:** SMS and QR login; no corporate email required. **Key considerations:** Limited web experience and content structuring compared with full intranet platforms; governance and admin delegation are lighter than enterprise-focused options. **Pricing:** Business and Enterprise tiers, quote-based. **Platforms:** Web, iOS, Android, Desktop [Explore Blink](https://www.joinblink.com/) Speakap **Best for:** Mid-market retail, hospitality, manufacturing, construction, and logistics organizations that want a fully white-labeled frontline app deployed quickly without heavy IT involvement, including across multiple countries. Speakap is a white-labeled employee experience app for frontline industries. Employee Journeys deliver guided onboarding, recurring training, and targeted news with read acknowledgments and polls. Multilingual support across 20+ languages and an API marketplace connect HR, scheduling, and POS systems behind a single sign-on. **Native capabilities:** Communication, journeys, polls. Scheduling and HR self-service via the API marketplace. **HR and IT integrations:** HR, scheduling, and POS integrations via API marketplace (vendor-stated). **Frontline access:** White-label app, no corporate email required. **Key considerations:** Positioned for the mid-market; large enterprises with complex governance requirements should verify admin delegation and audit depth. **Pricing:** Basic, Premium, and Premium+ tiers, quote-based. **Platforms:** Web, iOS, Android [Explore Speakap](https://www.speakap.com/) Firstup **Best for:** Large enterprises in retail, healthcare, and banking that need to reach complex, segmented audiences with automated, AI-timed communication journeys and prove impact with detailed analytics. Firstup is an intelligent communication platform built around workforce orchestration: automated journeys triggered by employee lifecycle events, with delivery timing optimized by machine learning. It delivers across a branded app, intranet, email, and digital signage and exports to BI tools including Tableau and Looker. Firstup publishes ISO 27001 and SOC 2 Type II on its [security page](https://firstup.io/legal/security). **Native capabilities:** Communication and orchestration. No native scheduling, tasks, or training. **HR and IT integrations:** Workday, UKG, Concur, Microsoft 365 (vendor-stated); BI export to Tableau and Looker. **Frontline access:** Mobile app; frontline sign-in options depend on configuration (Partial). **Key considerations:** Lacks the intranet structure for work management and content governance at scale; data hosting is limited to the U.S. and Ireland (vendor-stated), which matters for data-sovereignty requirements. **Pricing:** Enterprise, quote-based. **Platforms:** Web, iOS, Android, Digital Signage [Explore Firstup](https://firstup.io/) ## Which frontline communication software also handles scheduling, tasks, and training? Three platforms on this list run communication, scheduling, tasks, and training natively: MangoApps, WorkJam, and Connecteam. YOOBIC runs communication, tasks, and training natively but relies on integration for scheduling. Beekeeper runs communication and forms natively with scheduling and training via integration. Staffbase, Firstup, Blink, Speakap, and Flip are communication-first platforms that surface or link to scheduling, task, and training systems owned by other vendors. | Platform | Communication | Shift scheduling | Time and attendance | Tasks and checklists | Training / LMS | HR self-service | Knowledge / SOP search | |---|---|---|---|---|---|---|---| | MangoApps | Native | Native | Native | Native | Native | Native | Native | | WorkJam | Native | Native | Native | Native | Partial | Partial | Partial | | Connecteam | Native | Native | Native | Native | Native | Partial | Partial | | YOOBIC | Native | Via integration | Via integration | Native | Native | Via integration | Partial | | Beekeeper (LumApps) | Native | Via integration | Via integration | Native (forms) | Via integration | Via integration | Partial | | Flip | Native | Via HRIS | Via HRIS | Partial | Via integration | Via HRIS | Partial | | Blink | Native | Via micro-apps | Via micro-apps | Light | Via integration | Via micro-apps | Partial | | Speakap | Native | Via integration | Via integration | Light | Partial (journeys) | Via integration | Light | | Staffbase | Native | No | No | No | Via integration | Via integration | Partial | | Firstup | Native | No | No | No | No | Via integration | Light | *Cells reflect vendor documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps.* What "native" buys you is not a longer feature list. It is one login, one employee record driving targeting and permissions, analytics that connect a message to the task it triggered and the training it required, and one vendor accountable when something breaks. Enterprises that start with a communication-only tool and later add scheduling, tasks, and training from three other vendors end up rebuilding identity, permissions, and integrations three more times. That second and third migration is the cost the platform decision is meant to avoid. ## How do you evaluate and select a frontline communication platform? Start with your workforce, not the vendor's feature list. Decide whether you are buying communication or buying a platform. Then run a scored pilot at real sites rather than trusting a demo. ### Start with workforce composition Count the employees who do not have a corporate email address. Count the sites, the languages, the shared devices, and the union or works-council constraints on personal-device use. If the answer to the first question is "most of them," sign-in without corporate email is an eliminator, not a criterion. If you also have a large desk-based population, a platform that serves both without separate tools is worth the extra evaluation effort. ### Decide the platform question before the vendor question Is frontline communication your only near-term need, or the first step in consolidating scheduling, tasks, training, and HR self-service? Organizations that solve communication first frequently find themselves managing five separate tools two years later. If consolidation is on the roadmap at all, evaluate unified platforms from the start, even if the initial deployment is communication only. ### Twelve RFP questions that expose gaps 1. **"Show me a worker with no email address signing in for the first time."** A strong answer takes under two minutes from a QR code or SMS. A weak answer involves IT creating an account. 2. **"Which HRIS fields drive audience targeting, and how often do they sync?"** Strong: named fields, scheduled and event-driven sync. Weak: "you can upload a CSV." 3. **"Terminate an employee in the HRIS sandbox. When does their access end?"** Strong: same day, automatically. Weak: an administrator removes them manually. 4. **"Show me the acknowledgment report for a critical alert by location."** Strong: a manager view with percentages by site and an export. Weak: total opens. 5. **"Can an employee see and swap a shift here, and where does the approval go?"** Strong: native, with write-back to payroll. Weak: a link to another system. 6. **"Assign a task to 100 locations with a photo requirement and show me the completion dashboard."** Strong: live, by site. Weak: a separate product. 7. **"Assign a compliance course by role and location and show completion in the HRIS record."** Strong: automatic assignment and write-back. Weak: a separate LMS login. 8. **"Which HR transactions can a worker complete, not just view?"** Strong: PTO, availability, data changes with approval flows. Weak: read-only pay stubs. 9. **"For each integration on my list, is it a native connector, an API you expect us to build against, or a partner build? Who maintains it?"** Strong: a per-system answer with release notes. Weak: "we integrate with everything." 10. **"Ask your AI assistant a question whose answer lives in a document I am not permitted to see."** Strong: it declines. Weak: it answers. 11. **"Which certifications do you hold, and which deployment options do you offer?"** Strong: named certifications (SOC 2 Type II, ISO 27001, HITRUST for healthcare, FedRAMP for public sector) and deployment choices. Weak: "we follow best practices." 12. **"What adoption do your customers in my industry reach at 90 days, and what happens contractually if we do not?"** Strong: numbers and a guarantee. Weak: a slide about change management. ### Run a real pilot Pick two sites and one shift population for 30 days. Measure four things: weekly active users by location, acknowledgment rate on one critical alert, the number of schedule questions managers field before and after, and time-to-find for one SOP. These four numbers will tell you more than any demo. ### Score the finalists | Criterion | Weight guidance | What a strong answer looks like | |---|---|---| | Mobile-first reach without corporate email | Eliminator for frontline-heavy organizations | HRIS-provisioned identity, activation from the floor, offline access | | Communication depth | High | Targeting by HRIS attribute, acknowledgment records, multichannel including SMS and signage | | Operations depth (scheduling, time, tasks) | High for ops-led buyers | Native workflows with write-back to payroll | | Training and knowledge | High for regulated industries | Automatic assignment, completion write-back, permission-aware AI search | | HR and IT integration | High | Named native connectors, SCIM, documented APIs | | Security and compliance | Eliminator for regulated industries | SOC 2 Type II, ISO 27001, HITRUST or FedRAMP where required, deployment options | | Adoption support | High | Customer adoption data by industry, named customer success, contractual guarantee | | Total cost | Medium | Module pricing, frontline tiers, integration fees, exit terms, tools you can retire | An editable version of this scorecard, along with an RFP template and implementation checklist, is in the [2026 Intranet Buyer's Guide for a Frontline Workforce](https://www.mangoapps.com/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026). ## How should retail, healthcare, manufacturing, hospitality, and logistics organizations choose differently? The five layers matter everywhere, but the weight shifts by industry. | If you are | Prioritize | Watch out for | Compliance to verify | |---|---|---|---| | Retail and grocery (multi-location, hourly) | Scheduling and swaps, task execution with photo verification, no-email access, translation | Communication-only tools that leave scheduling in a spreadsheet | Wage-and-hour notice acknowledgment, OSHA, PCI awareness | | Healthcare (hospitals, home care, senior living) | Critical alerts with acknowledgment, shift handoff communication, compliance training, HIPAA-ready messaging | Consumer messaging apps carrying PHI | HIPAA (BAA), HITRUST, Joint Commission handoff standards | | Manufacturing | Safety alerts, SOP access on the floor, kiosk and signage delivery, certifications | Desktop-only training that never reaches the line | OSHA, ISO, GMP training records | | Hospitality and food service | Multilingual communication, schedules on personal phones, daily briefings, recognition | Apps that require managed devices | Food safety training records, wage-and-hour | | Logistics and field service | Offline access, dispatch and tasks, time and geofenced clock-in, driver-safe delivery | Platforms that assume constant connectivity | DOT, safety training | In retail, A.S. Watson reached 80%+ active use across 16,000 Kruidvat employees without formal training, and [Raley's](https://www.mangoapps.com/resources/raleys-case-study) connected 20,000 grocery employees on MangoApps. In healthcare, [Benchmark Human Services](https://www.mangoapps.com/customers/benchmark-human-services) and [TeamHealth](https://www.mangoapps.com/resources/teamhealth-case-study) show the platform reaching clinicians and caregivers who never had corporate email. ## What are the common mistakes when buying frontline communication software? 1. **Buying a communication app, then adding four more apps.** The consolidation cost arrives in year two as a second and third migration. Decide the platform question first. 2. **Requiring a corporate email to log in.** This excludes most of the people the platform was bought to reach. 3. **Measuring opens instead of acknowledgments and actions.** Opens describe the newsletter. Acknowledgments and completed tasks describe the business. 4. **Skipping manager enablement.** Frontline adoption runs through the site and shift manager. If they were not trained and not made accountable, the app becomes optional. 5. **Ignoring shared devices and low connectivity.** Break-room kiosks, shared tablets, and basements without signal are where frontline work happens. 6. **Accepting "we integrate with everything."** Ask for the model (native, API, partner) and the owner for each system on your list. 7. **Signing without an adoption clause.** If the vendor will not commit to an adoption outcome, price that risk into the contract. For the adoption failures specific to intranets, see [12 Reasons Frontline Intranet Adoption Fails (And How to Fix Each One)](https://www.mangoapps.com/articles/frontline-intranet-adoption-failures). ## Where MangoApps fits MangoApps is the AI-Ready Employee Platform for the Frontline. It runs all five layers natively: communication, scheduling and time, tasks and store execution, training and knowledge, and HR self-service, on one login for frontline and desk employees, with no corporate email required. It connects to the systems enterprises already own through 200+ out-of-the-box integrations, holds HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO, and offers SaaS, Private Cloud, Customer VPC, and On-Premise deployment. Because identity, permissions, and employee data are shared across every workflow, MangoApps AI can act safely inside those workflows rather than sitting on top of disconnected tools as a chatbot. It is not the right fit for everyone. Teams under 500 employees that want a free tier should start with Connecteam. Communications departments that only need multichannel publishing and already own scheduling and training elsewhere may be well served by Staffbase or Firstup. For enterprises that want to stop running separate tools for every function, MangoApps backs the decision with an [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee): 90%+ active adoption in 90 days. ## Frequently asked questions **What is a frontline communication platform?** A frontline communication platform delivers company information to deskless employees on their own mobile devices without requiring a corporate email address, laptop, or VPN, and connects that communication to the schedules, tasks, training, and HR records those employees use every shift. It differs from a frontline communication app by running those operational workflows natively rather than linking out to other systems. **Which frontline communication software also handles scheduling, tasks, and training?** MangoApps, WorkJam, and Connecteam run communication, scheduling, tasks, and training natively. YOOBIC covers communication, tasks, and training with scheduling via integration. Beekeeper, Flip, Blink, Speakap, Staffbase, and Firstup are communication-first and rely on integrations or linked systems for scheduling, tasks, and training. **What are the top frontline employee communication apps for multi-location enterprises in the United States?** The platforms most often shortlisted by multi-location U.S. enterprises in 2026 are MangoApps, WorkJam, Beekeeper (LumApps), Staffbase, Blink, Connecteam, YOOBIC, Flip, Speakap, and Firstup. MangoApps is the unified option for mixed frontline and desk workforces; WorkJam leads for operations-first retail and hospitality; Staffbase and Firstup lead for communications teams at large enterprises. **Which frontline employee platforms integrate with existing HR and IT systems like Workday, UKG, and Microsoft 365?** All ten platforms in this guide publish HRIS and identity integrations, but depth varies. MangoApps publishes 200+ out-of-the-box integrations including Workday, UKG, ADP, Paylocity, SAP SuccessFactors, Microsoft 365, Google Workspace, Okta, and Entra ID. Flip names Workday, SAP SuccessFactors, and UKG through HR mini-apps. Firstup names Workday, UKG, and Microsoft 365. Ask each vendor whether a given integration is a native connector, an API, or a partner build. **Can frontline workers use these platforms without a corporate email address?** Yes for MangoApps, WorkJam, Connecteam, Beekeeper, YOOBIC, Flip, Blink, and Speakap, which support sign-in by SMS, QR code, employee ID, or HRIS-provisioned credentials. Staffbase and Firstup support frontline access, but sign-in options depend on configuration. **What is the difference between a frontline communication app and an employee super app?** A frontline communication app delivers news, chat, and documents to deskless workers. An employee super app adds schedules, tasks, training, and HR self-service in the same app on one login. The platforms that qualify as super apps in this guide are MangoApps, WorkJam, and Connecteam. See our comparison of [the best employee app software](https://www.mangoapps.com/articles/best-employee-app-software). **How much does frontline communication software cost?** Most enterprise platforms are quote-based and priced per user or per location. Connecteam publishes pricing: free for up to 10 users and a Basic tier from $29 per month for the first 30 users, per hub. Factor in integration fees, onboarding, and the cost of the tools you will retire, not only the subscription. **How do you measure whether frontline communication is actually reaching employees?** Track weekly active users by location and shift, acknowledgment rate on critical alerts, task completion by site, and search success on SOPs. Social Edge Consulting benchmarks 60% weekly active users as a successful intranet and 85% as best practice, and MangoApps customers average more than 90% adoption within 90 days. **Do we have to replace our HRIS or scheduling system to adopt a frontline platform?** No. The HRIS stays the system of record. The frontline platform syncs people and schedules in and writes time, swaps, acknowledgments, and training completions back. Replacing the scheduler is a separate decision that a platform with native scheduling lets you make later. **Which frontline communication platforms are HIPAA, HITRUST, or SOC 2 compliant?** MangoApps publishes HITRUST CSF, SOC 2 Type II, ISO 27001, FedRAMP ATO, HIPAA (BAA), and GDPR on its security page. Staffbase and Firstup publish ISO 27001 and SOC 2 Type II. Verify each vendor's current trust page; certifications for third-party vendors in this guide are vendor-stated. ## Related guides - [The Complete Guide to Internal Communications Platforms for Regulated Enterprises](https://www.mangoapps.com/articles/internal-communications-platform-regulated-enterprises) - [The Complete Guide to Choosing Employee Engagement Platforms for Large Frontline Organizations](https://www.mangoapps.com/articles/employee-engagement-platforms-frontline-organizations) - [9 Things to Know About Performance Management Software for Frontline and Hourly Employees](https://www.mangoapps.com/articles/performance-management-software-frontline-hourly-employees) - [The Complete Guide to Knowledge Base Software for SOP and Policy Management in Regulated Industries](https://www.mangoapps.com/articles/knowledge-base-software-sop-policy-management-regulated) - [The Complete Guide to Aligning Internal Communications, Training, and Operations Software](https://www.mangoapps.com/articles/aligning-communications-training-operations-software) - [The Best Secure Communication Apps for Hospital and Frontline Healthcare Staff](https://www.mangoapps.com/articles/best-healthcare-communication-apps-hospital-frontline-staff) - [10 Things to Know About AI Shift Scheduling in Digital Workplace Platforms](https://www.mangoapps.com/articles/ai-shift-scheduling-what-to-know) - [The 10 Best Employee Intranet Platforms for Governance, Compliance, and Global Workforce Communication](https://www.mangoapps.com/articles/best-intranet-platforms-governance-compliance-global) ## Methodology and sources Platform capabilities in this guide reflect each vendor's public documentation, product pages, and published pricing as of September 2026, along with analyst research and customer reviews. Statements about third-party vendors are vendor-stated and have not been independently verified by MangoApps. Statistics are attributed to their original sources: - BCG, [Facing the Deskless Labor Shortage with Technology](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) (2024) - JLL, [Leading practices for frontline workforce engagement and retention](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention) (2025) - Deloitte, [Frontline Worker Productivity Enabled by Technology](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html) - Okta, [Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/) - Harvard Business Review, [How Much Time and Energy Do We Waste Toggling Between Applications?](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) (2022) - Gallup, [State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx); [This Fixable Problem Costs U.S. Businesses $1 Trillion](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) (2019); [Q12 Meta-Analysis](https://www.gallup.com/workplace/236927/employee-engagement-drives-growth.aspx) (2020) - Joint Commission Center for Transforming Healthcare, hand-off communications research, as summarized by [HIPAA Journal](https://www.hipaajournal.com/effects-of-poor-communication-in-healthcare/) - Social Edge Consulting, [Top 12 Intranet KPIs and Metrics](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) (2025) - LumApps, [LumApps and Beekeeper to Join Forces](https://www.lumapps.com/insights/news/lumapps-and-beekeeper-to-join-forces-creating-the-leading-employee-experience-platform-for-the-future-of-work) (July 2025) - MangoApps proof points from [mangoapps.com](https://www.mangoapps.com/), [mangoapps.com/integrations](https://www.mangoapps.com/integrations), and [mangoapps.com/security](https://www.mangoapps.com/security) --- # Why Frontline Managers Are Always the Last to Know **Author:** MangoApps Team **Published:** 2026-09-06 **Category:** workforce-management A warehouse floor manager gets an email on a Thursday: three team members are out of compliance on their annual safety certification. A regulatory audit is scheduled for next week. # Why Frontline Managers Are Always the Last to Know A warehouse floor manager gets an email on a Thursday: three team members are out of compliance on their annual safety certification. A regulatory audit is scheduled for next week. She doesn't need more accountability. She's had that since the day she started. What she didn't have was a way to see who was behind *before* it became a compliance problem — without asking HR, waiting for a report, and circling back through email. By the time the information reached her, the window to act had already narrowed. This scenario, in some variation, plays out constantly in frontline organizations. Managers are given responsibility for outcomes — onboarding completion, training compliance, schedule accuracy — but the tools to monitor and act on those outcomes often live somewhere else: in HR dashboards, in admin panels, in reports that require someone else to pull. The gap between accountability and visibility is one of the most reliable sources of friction in frontline operations. This week's releases across MangoApps took direct aim at it. --- ## When Managers Can Finally See What's Actually Happening The most significant release this week, for any organization managing training compliance, is the [Training My Team Dashboard](https://www.mangoapps.com/changelog/3130). Managers and HR admins can now view their team's training progress — broken down by person, overdue items, or completed work — from a dedicated "My Team" tab. And they can send a nudge to a learner with one tap. This sounds simple. But consider what it replaces: a manager who wants to know whether their team has completed required training currently has to either ask HR, dig through aggregate reports they don't have direct access to, or wait for a compliance flag to surface. By the time any of those paths produces an answer, the "ahead of the deadline" window has often already closed. What the new dashboard gives managers is agency — not just visibility into a problem, but visibility at a moment when they can still do something about it. The nudge feature is part of that: it's not just about knowing someone is behind. It's about being able to act on that knowledge without routing through an intermediary. The same pattern appeared two days later with the [Onboarding Manager Nudge](https://www.mangoapps.com/changelog/3133). New-hire onboarding plans often split responsibility between HR and the direct manager: HR handles the paperwork, the manager owns the cultural integration, the introductions, the day-one checklist. But until now, the ability to send a targeted reminder was limited to HR admins. Managers couldn't nudge their own new hires on items that only the manager could address. The new feature lets them do that directly — from the dashboard or the plan header — for precisely the tasks in their lane. Both features reflect the same underlying insight: the person most motivated to close an onboarding or compliance gap is usually the direct manager. They're the ones who feel the cost of that gap daily. Routing the action through HR is a workaround, not a design — and it reliably slows things down. --- ## Authority That Follows the Org Chart Beyond visibility, there's a second, quieter problem: in most platforms, administrative authority is granted manually, which means it lags reality. A manager gets promoted, takes on a new team, or picks up a cross-functional responsibility — and the configuration in the platform doesn't update until someone remembers to update it. The new [Sites org-chart–based create policy](https://www.mangoapps.com/changelog/3133) is a small but meaningful answer to this. Previously, granting someone the right to create site pages required an explicit admin role assignment. Under the new "People Managers" option, anyone who manages at least one direct report automatically qualifies — based on org structure, not a remembered admin task. As organizations grow and change, this kind of automatic rights propagation keeps the platform current without requiring a ticket to IT every time a reporting line shifts. There's a version of this logic in the [Payroll Reconciliation tab for Leave Compliance Reports](https://www.mangoapps.com/changelog/3135) as well, though it addresses a different role. Payroll managers doing period-end reconciliation previously had to cross-reference multiple reports to get a complete view of employee leave. The new tab shows every employee and every leave type side-by-side, with CSV export. It's the right view, for the right role, without requiring that role to build it themselves from raw data. That's authority in the original sense: the authorization to do your job without routing through someone else's workflow. [Customizable printed schedules](https://www.mangoapps.com/changelog/3133) are in a similar category. Shift planners and managers can now choose which fields appear on printed schedules — name, label, location, team, description — with preferences saved per user across both print views. It's not a dramatic feature. But saved preferences represent something worth noticing: the platform treating the manager as someone whose preferences matter, not a default-view consumer who takes what the system was configured to show years ago. --- ## When Insight Needs to Move Fast Visibility and authority only complete the picture if the tools for acting on them are low-friction. Several releases this week addressed the cost of action directly. [My Tasks bulk actions](https://www.mangoapps.com/changelog/3135) let users bulk-start tasks, set due dates across a selection, or delete a batch at once. For a manager reviewing 30 open items at the start of a week — or closing out a finished project — this changes the rhythm significantly. Doing the right thing shouldn't require thirty separate clicks. The same efficiency logic appears in [Procurement's bulk project billing](https://www.mangoapps.com/changelog/3132). Warehouse managers can now select a full cart of inventory items and bill them all to a project in a single action, rather than opening each item individually. The result isn't just saved time — it's a lower activation energy for doing things correctly, which tends to mean more people do them correctly. On the other side of access: the [Power Tables PHI controls](https://www.mangoapps.com/changelog/3131) this week let admins flag any table as containing Protected Health Information. Once flagged, AI assistants, webhooks, public widgets, and exports are blocked from accessing that data without explicit acknowledgment and a full audit trail. This is the complement to the manager-visibility story: making sure that access to sensitive data is explicit, gated, and auditable — not ambient. The same principle applies equally to access that should be expanded and access that should be restricted. Good platforms do both. --- ## The Real Cost of the Gap The accountability-without-visibility problem doesn't just create compliance risk. It drives turnover. Frontline manager attrition is disproportionately driven by a specific frustration: being responsible for outcomes you can't influence in real time. It's not the work itself — it's the lag. The lag between something going wrong and finding out about it. Between knowing what needs to happen and being able to make it happen without three handoffs. That lag is a tools problem, and it compounds over time into the kind of exhaustion that shows up in exit interviews. Platforms that treat the floor manager as a first-class user — not just a worker with a slightly bigger inbox — tend to see better retention at every level. The manager who can see their team's training gaps, send a nudge, pull a payroll reconciliation report, and log into the schedule print view with their preferences already saved isn't just more effective. They're more likely to stay, and more likely to stay engaged. The releases this week aren't a grand announcement. They're the kind of incremental, specific improvements that accumulate into a platform that reflects how frontline operations actually work — not how they're imagined to work from a conference room. --- *Full releases this week: [September 6](https://www.mangoapps.com/changelog/3135) · [September 5](https://www.mangoapps.com/changelog/3134) · [September 4](https://www.mangoapps.com/changelog/3133) · [September 3](https://www.mangoapps.com/changelog/3132) · [September 2](https://www.mangoapps.com/changelog/3131) · [September 1](https://www.mangoapps.com/changelog/3130) · [August 31](https://www.mangoapps.com/changelog/3129) · [August 30](https://www.mangoapps.com/changelog/3128) · [August 29](https://www.mangoapps.com/changelog/3127)* --- # The Business Spending Blind Spots Operations Can't Afford **Author:** MangoApps Team **Published:** 2026-08-30 **Category:** operational-efficiency Ask an operations director to pull together a picture of current business spending, and watch the workflow that follows: reimbursement requests in one module, vendor invoices in another, corporate... # The Business Spending Blind Spots Operations Can't Afford Ask an operations director to pull together a picture of current business spending, and watch the workflow that follows: reimbursement requests in one module, vendor invoices in another, corporate card receipts somewhere else, pre-approval requests in a queue that requires separate navigation. The numbers exist. Assembling them into a coherent view takes time that nobody budgeted. This is not a data problem. Organizations track their spending carefully. It is a visibility problem: when every category of business expenditure flows through a separate workflow, the complete picture only comes together at reporting time — which is usually too late to act on it. This week's releases in MangoApps address that gap from multiple angles: aggregation at the dashboard level, automation at the point of data entry, and accountability at the level of individual projects and requests. --- ## When the Dashboard Only Shows Part of the Picture The natural first response to a visibility problem is to build a dashboard. Most operations teams have one. The problem is that dashboards tend to track whatever the first team to request them needed — which in most organizations means expense reimbursements. Corporate card receipts end up in a different view. Vendor invoices may not be in the same system at all. Pre-approvals — the requests that haven't become expenses yet — often aren't tracked in real time. [The Mango Spend dashboard](https://www.mangoapps.com/changelog/3120) now surfaces all four spend categories — reimbursements, pre-approvals, corporate card receipts, and vendor bills — in a single activity view. This sounds like a small change. In practice, it means the first thing someone sees when they open the Spend module is a complete picture of activity rather than a partial one. A vendor invoice approaching its due date is visible alongside the reimbursement queue. A pre-approval request sits next to the card receipts it may eventually generate. [Spend Analytics](https://www.mangoapps.com/changelog/3123) extended this further, bringing full analytics coverage to every enabled spend record type — each category in its own tab, with a summary overview that pulls them together. This matters more than it sounds. Finance teams looking at spending patterns need to see across categories: when pre-approval volumes rise faster than reimbursements, it may signal a shift in how teams are managing budgets. When vendor invoice volume climbs independently of card spend, it may indicate that procurement processes are routing differently than expected. That kind of cross-category pattern is invisible when each category lives in a separate view. The approver experience is where fragmentation hurts most acutely day-to-day. Reviewing and approving pending expense requests requires navigating away from whatever a manager was doing, finding the queue, and working through it. The [Spend Approvals dashboard card](https://www.mangoapps.com/changelog/3124) surfaces pending approval requests directly on the home screen — with one-click approval without changing context. For managers who handle a steady volume of routine approvals, this removes a navigation step that, repeated dozens of times per week, adds up to meaningful time. --- ## Where the Data Integrity Problem Begins Visibility is only useful if the underlying data is accurate. In spend management, data quality problems usually start not at the reporting layer but at the entry layer — specifically, with vendor invoices. When a vendor bill arrives, someone needs to enter the relevant details: vendor name, invoice number, PO reference, amount, due date. This is not complicated work, but it is time-consuming and error-prone. A transposed invoice number creates a reconciliation problem downstream. A missed PO reference delays approval. A due date entered a month off means a late payment fee. [AI Invoice Reading in Mango Spend](https://www.mangoapps.com/changelog/3125) addresses this by letting the system extract the relevant information directly from an attached document. Staff attach the bill; the AI reads the vendor, invoice number, PO number, amount, and due date. The role of the person processing the invoice shifts from transcription to verification. In organizations processing dozens or hundreds of vendor bills per month, the accuracy improvement compounds quickly — fewer errors to chase down, fewer delays in the approval queue, fewer late payments. This is one of the cleaner examples of AI assistance in operations software: it does not change what gets tracked, it changes how the data gets there. The workflow is the same; the manual work in the middle of it is substantially reduced. --- ## Connecting Spending to the Work It Funds Perhaps the least visible blind spot in business spending is the connection between expenditures and the projects or activities they fund. An expense report tells you that money was spent. A vendor invoice tells you what was purchased. What neither typically tells you — without significant manual effort — is which project absorbed the cost. This gap matters because project-level financial accountability is how organizations understand whether they are deploying resources effectively. When materials are drawn from a warehouse and charged to a project, that cost should appear in the project's budget. When it doesn't — when inventory issues are tracked separately from project financials — project managers work from an incomplete cost picture, and finance teams reconcile at the end of the period rather than monitoring in real time. [Procurement's new project charging capability](https://www.mangoapps.com/changelog/3127) closes this loop. Warehouse staff can now withdraw inventory and charge it directly to a project budget — from a service ticket, the warehouse counter, or a contractor self-service request portal. This brings material costs into the same financial picture as labor and vendor expenses for a given project. The self-service portal piece is particularly useful in contractor-heavy environments: instead of warehouse staff needing to initiate every withdrawal on behalf of contractors, contractors can submit their own requests through a portal, with the same authorization and project-charging rules applied. The accountability layer doesn't change — requests still route through the right approvals — but the burden of initiating the transaction no longer falls entirely on staff. The result is not a new category of spending information. Organizations already track materials procurement. It is a connection that previously required manual bridging: materials consumed in the field, linked to the project that consumed them, visible in the same place as the rest of that project's costs. --- ## What Full Visibility Actually Changes The end state of the releases this week is not a more impressive dashboard. It is a different kind of conversation. When an operations leader or finance director can see total committed spend across all categories — reimbursements awaiting approval, pre-approvals in flight, invoices due this week, card receipts to reconcile — the question changes from "what did we spend last month?" to "where does spending stand today?" That shift from retrospective to current is not a technical achievement; it is an operational capability. Organizations that develop this capability tend to catch things earlier: an invoice from a vendor that has already hit its monthly ceiling, a pre-approval request for a project whose budget is nearly exhausted, a reimbursement queue backed up because an approver is traveling. These are not unusual events. They are the normal texture of operations. The difference is whether they surface in real time, when there is still room to act, or in the month-end reconciliation, when the action that was possible has closed. The releases this week — dashboard aggregation, analytics coverage, AI-assisted invoice entry, project-level procurement charging, and streamlined approvals — each address one point in the spend management chain. Individually, any one of them is a useful improvement. Together, they describe an organization that knows what is being spent, why, and by whom, without needing to assemble that picture from scattered sources after the fact. --- # Do You Need to Replace Your Applicant Tracking System? **Author:** Christos Schrader **Published:** 2026-08-28 **Category:** talent-acquisition You may not need to replace your ATS. Learn how connecting recruiting, HR, and onboarding systems can close the offer-to-onboarding gap. **Quick answer:** You may not need to replace your applicant tracking system, and that is not the useful question anyway. The question is not whether your ATS tracks candidates. It is whether a signed offer starts onboarding on its own. Most organizations start by connecting what they already run, closing the offer-to-onboarding break first, and migrating the rest only when it makes sense to them. ![SaaS migration diagram showing teams staying connected, migrating when ready, and starting fresh through a shared data layer.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_3-in-1-shared-data-layer.png) ## The objection is reasonable, so start by granting it Nobody wants a second recruiting implementation two years after the first one. The ATS was expensive, the configuration took months, recruiters finally know it, and the contract has time left. All of that is true, and none of it is the point. An ATS is built to track candidates through stages, and most of them do that adequately. The question that decides whether your stack is working is a different one, and it sits at the edges of what an ATS was designed to do. So here are the five objections that come up in this conversation, in the order they usually arrive. ## "We just implemented it. We are not doing that again." You are probably not being asked to. The most common starting point is to keep and connect: your ATS, HRIS, payroll, and identity systems stay where they are, and they come onto a shared data layer through pre-built connectors and an open API across Workday, SAP SuccessFactors, UKG, ADP, BambooHR, and 200+ other enterprise systems. Employee records sync in real time, and when a candidate is hired, the new employee record flows to your HRIS automatically. What changes is not the tracking. It is the handoff. The break that costs the most, offer to onboarding, gets closed first, while the systems you already depend on stay in place. There are two other paths, and it is worth knowing all three exist. Migrate when ready, for the point when a standalone tool no longer justifies its cost or complexity, which is a business area turned on rather than a project started over. And start net new, for organizations without a mature HRIS or replacing legacy infrastructure. Three paths, and every MangoApps customer has taken one of them. Nobody is required to take the third. ## "Our ATS already has an onboarding module." Many do, and the question to ask about it is not whether it exists but what triggers it. If a person marks an offer accepted and then launches onboarding, that is a second project with a shorter name. If a signature triggers a role-based workflow that collects documents, provisions system access and groups, auto-enrolls required training, and puts the new hire in the directory and their team channels before day one, that is a connected process. The difference shows up in the first week rather than in the feature comparison. The new hire either logs in to an environment already configured for who they are and where they work, or spends day one waiting for access while a manager who has been in meetings all week tries to find them something to do. Test it with one question in your own environment: if the person who normally kicks off onboarding is on vacation the week an offer is accepted, what happens? ## "Our reporting is fine." ![Laptop and smartphone displaying MangoApps Talent Hub recruitment pipeline analytics, including funnel metrics, conversion rates, and hiring data.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_full-funnel-pipeline-reporting.png) Top-of-funnel reporting is usually fine. That is not where the argument is. Ask your current stack for these three and see how long it takes. Ninety-day retention broken out by sourcing channel. Time-to-fill separated from time-to-hire, so you can tell whether the delay is the search or the process. Cost per hire that survived their first quarter, by job board. Those are not exotic requests. They are impossible for a standalone ATS to answer on its own, because each one requires recruiting data and onboarding, HR, or performance data to sit on the same record. Most ATS platforms report the top of the funnel because the top of the funnel is all they can see. That is the sharpest version of this whole argument, and it rests on architecture rather than features: a source-to-90-day-retention view cannot be built from a system that stops caring about the person on their start date. > ![Angled view of a green MangoApps guide titled “End-to-End Talent Acquisition” displayed on a warm peach gradient background.](https://mango-cdn.b-cdn.net/marketing/uploads/talent-acquisition_thumbnail.png) > **Get the complete playbook:** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) covers the three paths onto the platform, what a connected record reports on, and the six questions buyers ask most often. ## "Our hiring is too specialized for an off-the-shelf platform." This one is worth taking seriously, because it is true of more organizations than vendors like to admit. It is also the objection most often based on an experience with a rigid product rather than with platforms generally. The requirements teams assume are too unusual are usually these: internal versus external candidate pooling, priority funnels for certain populations, group interviews for high-volume and seasonal hiring, approval chains that vary by department and salary band, and screening packages that differ by role type across executive, clinical, financial, frontline, and field work. Every one of those should be a configuration option rather than an exception or a custom build. Forms, fields, screening rules, approval routing, and the workflow itself should adjust to how your organization already hires, without code. Ask the vendor to configure your single strangest hiring rule during the evaluation. Not describe it. Configure it. ## "We only need recruiting. We do not want a whole platform." ![Three-column infographic outlining MangoApps capabilities across employee experience, frontline operations, and people operations, unified by one shared Mango platform base.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_one-shared-mango-platform-base.png) Then buy recruiting. The Talent Acquisition Suite solves the recruiting problem on its own, and starting there is the normal case rather than a compromise. What is worth understanding is what the platform decision does to the second purchase. Identity, employee data, permissions, and integrations get configured once, and every workflow added later inherits them instead of rebuilding them. Adding scheduling, learning, or communications later is a business area turned on, not a new implementation, with users, data, and history carrying forward. The consolidation math is the part IT cares about and recruiting rarely presents: every app you turn on is one fewer vendor to manage, one fewer contract to renew, one fewer integration to maintain, one fewer security review to run, and for employees, one fewer system to learn. The integration tax goes down, not up, with every addition. That is a decision about optionality rather than about buying more software today. ## Where MangoApps fits ![Infographic showing that over 50% of the roadmap is driven by customer requests, with four free major releases per year, 80% engineering and customer success headcount, and a quarterly Q1–Q4 timeline.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_continuous-customer-driven-inoovation.png) MangoApps runs recruiting as one workflow on [one platform](https://www.mangoapps.com/platform) rather than as a standalone product. In practice that means three things for an organization with an incumbent ATS. It connects. Pre-built connectors and a full open [API](https://www.mangoapps.com/integrations) across 200+ enterprise systems, with real-time employee record sync, so nothing has to move before value shows up. It closes the expensive gap first. A signed offer starts [onboarding](https://www.mangoapps.com/solutions/hr-operations) on its own, provisions access, queues [required training](https://www.mangoapps.com/solutions/performance-learning), and adds the new hire to the [branded app](https://www.mangoapps.com/solutions/employee-app) that everyone else already opens, with no separate login and no company device required. It leaves the sequencing to you. Start with one capability, in one population, one department or a single high-volume role. Typical implementations run 8 to 12 weeks with a named Customer Success Manager, and the platform comes online alongside your existing systems rather than replacing them on a vendor's timeline. The supporting numbers: 15+ years building for the frontline, 2M+ users, 98% customer retention, NPS 78, 90%+ adoption within 90 days of launch, four included releases a year with over half the roadmap coming from customer requests, and the Adoption Guarantee, which means that if employees do not adopt after launch, you do not pay. ## Frequently asked questions **Do we have to replace our ATS to use MangoApps for talent acquisition?** No. MangoApps connects to your ATS and HRIS through pre-built connectors and an open API, closes your biggest gap first, usually the offer-to-onboarding break, and lets you migrate the rest when it makes sense. Most organizations start with keep and connect. **Does buying the Talent Acquisition Suite lock us into a full platform purchase?** No. Start with the suite alone; it solves the recruiting problem by itself. Every other business area, HR, learning, scheduling, and communications, is a configuration you turn on when you are ready, not a new project and not a new vendor. **What happens to our historical candidate data?** ATS data migration is part of the standard implementation scope, handled by the Technical Account Manager assigned to your deployment in conjunction with your team. What migrates and what stays in the incumbent system is a decision made during the planning weeks rather than at contract signature. **How is this different from integrating our ATS with an onboarding tool?** An integration moves data between two systems on a schedule and depends on both vendors keeping their end stable. A shared data model means there is one record, so a signature does not need to be copied anywhere to start work. The visible difference is who is accountable when the handoff fails. **Our frontline candidates have no corporate email or company device. How do they apply and onboard?** They apply from the career site on their own phone, and new hires reach onboarding through the branded app on their personal device. No corporate email and no company device required, with onboarding delivered by SMS invite or a QR code at the location. **We are in a regulated or union environment. Does that change the answer?** It sharpens it. The reason to connect the record is that a hiring decision has to be defensible, and defensible requires the criteria, scorecards, approvals, and screening sequence to sit in one place rather than across five systems that do not agree. > **Start with the playbook.** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) covers keep and connect, migrate when ready, and start net new in full. When you want to look at where your own stack breaks first, [schedule a call](https://www.mangoapps.com/schedule-a-call). ## Keep reading - [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) - [Talent acquisition](https://www.mangoapps.com/solutions/talent-acquisition) - [Integrations](https://www.mangoapps.com/integrations) - [Platform overview](https://www.mangoapps.com/platform) - [HR operations](https://www.mangoapps.com/solutions/hr-operations) - [Analytics & insights](https://www.mangoapps.com/analytics-insights) - [Success services](https://www.mangoapps.com/success-services) --- # 8 Questions to Ask When Evaluating a Talent Acquisition Platform **Author:** Christos Schrader **Published:** 2026-08-28 **Category:** talent-acquisition Use these eight questions to determine whether a talent acquisition platform is truly unified—or simply a collection of tools behind one login. **Quick answer:** The questions that separate a platform from a collection of tools sharing a login screen are not about features. They are about whether the system shares a data model, whether AI inherits your permissions, whether the frontline can reach the process without a corporate email, whether a hiring decision leaves a defensible record, whether onboarding starts automatically at signature, and whether the vendor will put terms behind its adoption claim. Ask all eight below in every demo, including ours. ![Eight green-accented feature cards presenting recruiting and talent management tools, including a job board, AI recruiting agent, interview scheduler, offer manager, background checks, onboarding hub, headcount planner, and talent hub.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_talent-acquisition-suite-keyfeatures.png) ## Why demos do not answer the real question Every recruiting platform demos well. That is what demos are for. The problem is that the difference between a unified platform and a well-integrated set of tools is invisible in a demo, because a demo shows each step working. What it does not show is what happens between steps: whether the data moved on its own or whether someone moved it, and whether the reporting can span the funnel afterward. So the evaluation has to be conducted in questions rather than screens. Bring these to any vendor conversation, including ours. ## Question 1. Does the system share a data model, or just a login? ![Diagram showing eight talent management capabilities—including career site, AI screening, scheduling, offer management, background checks, onboarding, headcount planning, and a talent hub—connected to a single shared data layer.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_single-shared-data-layer.png) This is the question the other seven depend on. A shared data model means a signed offer starts onboarding with no re-entry, a candidate's source is attributed automatically, and a 90-day retention rate appears next to the channel that produced the hire. A shared login means each product is reached from one nav bar and the data still moves by sync, export, or hand. Single login is a convenience. Shared data is a different product. **What a good answer sounds like:** the vendor walks one candidate record through three stages without switching products and without anyone typing the candidate's information twice. **What a weak answer sounds like:** the word "integrated," followed by a description of a nightly sync. ## Question 2. How does AI access candidate data, and where are the permission boundaries? Any AI in a hiring workflow is handling resumes, compensation, interviewer assessments, background-check results, and diversity data. The governance question is not optional. Ask whether the AI inherits role-based permissions or maintains its own, whether a user can surface results through AI that cross their access boundaries, whether candidate or employee data is ever used to train public models, and whether AI actions are logged in the same audit trail as human ones. **What a good answer sounds like:** AI inherits permissions rather than overriding them, scope follows the calling user, data stays inside your boundaries, model choice is a configuration setting, and every action is logged. **What a weak answer sounds like:** a security page and an assurance that the model is enterprise-grade. ## Question 3. Can the frontline reach the process without a corporate email or a company device? Most hiring is frontline hiring. The store associate, the charge nurse, the field technician, and the warehouse crew have a phone, often a personal one, and nothing else. If a candidate or new hire needs a second app, a kiosk workaround, or a company device to apply, schedule, or onboard, the platform does not actually reach your workforce. **What a good answer sounds like:** a live walkthrough on a phone, plus a specific mechanism for reaching a new hire who has no company account yet, such as an SMS invite or a QR code at the location. **What a weak answer sounds like:** "it is fully responsive." ## Question 4. Does a hiring decision leave a defensible record? ![MangoApps-style HR dashboard showing an accepted candidate offer, post-acceptance checklist, candidate journey, and multi-level approval workflow.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_muti-level-approval-workflows.png) In regulated industries, the public sector, and any union environment, every decision has to be explainable, and explainable means consistent across candidates. Ask whether scorecards, approvals, communications, and screening results live on one record or across five systems that do not agree. Ask what the retention and deletion policy looks like when a search closes, and whether it is configurable to your legal team's requirements. **What a good answer sounds like:** one record containing the criteria, the questions asked, the scorecards, the approval chain with names and timestamps, and the screening sequence, including the adverse action steps in order. **What a weak answer sounds like:** a reporting module. ## Question 5. Does onboarding start automatically at signature, or is it a second project? This is the transition where the most value is won or lost, and it is the one most vendors treat as somebody else's scope. A platform connects the offer to provisioning, document collection, training assignment, and the directory the moment a candidate signs. A collection of tools hands the new hire to a separate team and a separate system and calls that the end of recruiting. **What a good answer sounds like:** a signature triggering a role-based workflow with no manual handoff, demonstrated rather than described. **What a weak answer sounds like:** an onboarding module that a person launches after the offer is marked accepted. ## Question 6. What happens when we add the next workflow? ![Three-column infographic outlining MangoApps capabilities across employee experience, frontline operations, and people operations, unified by one shared Mango platform base.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_one-shared-mango-platform-base.png) Most organizations buy recruiting first and then need scheduling, learning, or communications within two years. The cost of that second decision is set by the first one. Ask whether adding a capability is a configuration or an implementation, whether identity, permissions, and integrations carry forward, and whether historical data comes with it. **What a good answer sounds like:** the next business area inherits the identity model, the permission structure, and the employee record already in place, so the integration tax goes down rather than up with each addition. **What a weak answer sounds like:** a roadmap and a new statement of work. ## Question 7. What breaks while we switch, and how long until we are live? Two questions come up in every evaluation before a contract is signed: how long until this is live, and what breaks while we change over. Make the vendor answer both with dates and dependencies. Ask for the standard timeline rather than the best case, who is assigned to you by name/job title, whether training happens during the build or at the end, and what runs alongside your existing systems during the transition. **What a good answer sounds like:** a phased timeline with named roles, work in your current systems continuing throughout, and a launch-readiness review before anything goes live. **What a weak answer sounds like:** "most customers are live in a few weeks," with no phases named. ## Question 8. What does adoption look like at 90 days, and does the vendor back it with anything? ![Three statistic cards highlight streamlined recruiting and onboarding: unified candidate records, automated onboarding after offer acceptance, and more than 90% adoption within 90 days.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_what-mangoapps-does.png) Every claim above depends on people using the system. A defensible record requires that hiring managers actually score in the platform. A source-to-retention report requires that onboarding data lands there. Ask for adoption evidence at comparable organizations, in your industry and with your workforce mix. Then ask whether the vendor puts terms behind the number. **What a good answer sounds like:** a documented adoption rate at organizations like yours, plus a contractual commitment. **What a weak answer sounds like:** a case study about a company that looks nothing like yours. > ![Angled view of a green MangoApps guide titled “End-to-End Talent Acquisition” displayed on a warm peach gradient background.](https://mango-cdn.b-cdn.net/marketing/uploads/talent-acquisition_thumbnail.png) > **Get the complete playbook:** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) includes the full evaluation chapter, the vendor scorecard, and the five demonstrations to insist on in every demo. ## Five things to ask to see, not to hear about Questions get answered. Demonstrations get remembered. Insist on these five in every demo: 1. "Show me a signed offer that starts onboarding, provisioning, and training without anyone re-entering the candidate." 2. "Show me what a frontline candidate sees on their phone, and how they apply without a corporate email." 3. "What triggers a stalled-application alert, and who sees it?" 4. "What is your adoption rate at 90 days, and do you back it with anything?" 5. "Walk me through what happens when we add scheduling after we have deployed recruiting." Number five is the one that most reliably separates a platform from a portfolio, because it is a question about the second purchase rather than the first. ## How to score what you hear Keep it simple enough that three people on the committee score it the same way. Eight criteria, five points each, forty points total. This is deliberately unweighted, so every criterion carries equal value and the conversation stays about evidence rather than about which criteria matter most. Score each criterion 5 if it is fully addressed with evidence you saw, 3 if it is partially addressed, and 1 if it is unaddressed or unclear: - Shared data model, not just a shared login - AI governed by user permissions, with data that never trains public models - Reaches the frontline without a corporate email or company device - Start with one capability and expand without re-implementing - Offer, background check, and onboarding on one record - A signed offer that triggers onboarding, provisioning, and training automatically - HITRUST plus SOC 2 Type II plus ISO 27001 on one unified system - A documented adoption rate, backed by a guarantee Two scoring disciplines matter more than the arithmetic. Score what you were shown, not what you were told. And have each stakeholder score independently before comparing, because the security stakeholder and the recruiting stakeholder tend to hear entirely different demos. ## Where MangoApps fits ![Graphic outlining the implementation team, including customer success, technical account management, implementation specialists, and design support.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_the-implementation-team.png) MangoApps built the [Talent Acquisition Suite](https://www.mangoapps.com/solutions/talent-acquisition) on a single data layer rather than assembling it, which is why the answers above can be demonstrated rather than described. Eight capabilities, from career site and screening through scheduling, offers, background checks, and onboarding, write to one candidate record, and that record continues into [HR operations](https://www.mangoapps.com/solutions/hr-operations), [learning](https://www.mangoapps.com/solutions/performance-learning), and [scheduling](https://www.mangoapps.com/solutions/workforce-management) as the same employee. On question six specifically: expansion is a business area turned on, not a new implementation, because identity, permissions, and [integrations](https://www.mangoapps.com/integrations) across Workday, SAP SuccessFactors, UKG, ADP, BambooHR, and 200+ other systems are already in place. On question seven: implementations typically run 8 to 12 weeks with a named Customer Success Manager, a Technical Account Manager, an Implementation Specialist, and a Design Team, with [support](https://www.mangoapps.com/success-services) that continues through every renewal. On question eight: 90%+ adoption within 90 days of launch, backed by the Adoption Guarantee, which means that if employees do not adopt after launch, you do not pay. 15+ years building for the frontline, 2M+ users, 98% customer retention, NPS 78, a 99.9% uptime SLA, and [certifications](https://www.mangoapps.com/security-compliance) covering HITRUST CSF, SOC 2 Type II, ISO 27001, FedRAMP ATO, HIPAA, and GDPR. ## Frequently asked questions **What is the difference between an ATS and a talent acquisition platform?** An applicant tracking system tracks candidates through stages. A talent acquisition platform runs the whole path, requisition through onboarding, on one record, which is what makes a signed offer able to start work in another part of the business. The practical test is not the label. It is whether anything has to be re-entered between stages. **Who should be on a talent acquisition evaluation committee?** Recruiting leadership, at least one hiring manager who will live in the tool, IT for identity and integrations, security or compliance for candidate data, and HR operations for the onboarding handoff. In regulated, public-sector, or union environments, add legal or labor relations early rather than at contract stage. **How long should a talent acquisition platform evaluation take?** Long enough to see the same candidate record demonstrated across three stages and to get written answers on permissions, retention, and expansion. In practice that is a handful of weeks, not months. Evaluations stall when the committee compares feature lists instead of scoring what was demonstrated. **Should we score vendors with weighted criteria?** You can, but be careful with the arithmetic. A weight column that is labeled and never applied to the total is worse than no weighting at all, because it looks rigorous and is not. The eight-criteria, five-points-each version above is unweighted on purpose. If your organization genuinely values some criteria more, apply real multipliers and show them in the total. > **Start with the playbook.** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) carries the evaluation framework and the scorecard to run your shortlist through. When the committee is ready to score us, [schedule a call](https://www.mangoapps.com/schedule-a-call) and we will take the five demonstrations in order. ## Keep reading - [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) - [Talent acquisition](https://www.mangoapps.com/solutions/talent-acquisition) - [Security & compliance](https://www.mangoapps.com/security-compliance) - [AI governance](https://www.mangoapps.com/ai/governance) - [Integrations](https://www.mangoapps.com/integrations) - [Success services](https://www.mangoapps.com/success-services) - [Why MangoApps](https://www.mangoapps.com/why-mangoapps) --- # Four Practical Ways AI Supports Fairer Recruiting **Author:** Christos Schrader **Published:** 2026-08-28 **Category:** talent-acquisition Learn how AI can streamline recruiting through parsing, bias checks, candidate alerts, and structured interviews—without replacing human judgment. Most AI claims in recruiting fail the same test. Ask what the AI decides and the answer is vague. Ask what happens when it is wrong and the answer is vaguer. Which is a shame, because the useful version of AI in a hiring workflow is not mysterious at all. It does four specific jobs, all of them administrative, and it leaves the judgment where it belongs. What follows is what those four jobs are in MangoApps, what the AI is explicitly not doing, and the governance questions worth asking any vendor, including this one. ## Job one: read every application into a comparable structure ![Laptop mockup showing an AI-powered recruiting dashboard with candidate screening results, skill matching scores, and review recommendations, alongside feature callouts for data extraction, precision matching, and queue filtering.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_resume-parsing-candidate-scoring.png) The first job is parsing, and it is the least glamorous and most valuable. Resumes arrive as PDFs, Word files, and profile imports, in every format a candidate can produce. Reading them into one comparable structure means candidates never re-enter what their resume already said, and it means a recruiter is comparing like with like instead of skimming twenty layouts. Then scoring, which is where the framing matters. Ranking each candidate against the role's weighted requirements is a different operation than matching on job-title proximity or keyword density, which is how most automated screening has historically worked and why it produces such strange shortlists. The output is a prioritized shortlist with the low-fit applications set aside, not a decision. The recruiter opens to a ranked list instead of a stack. That is the whole benefit, and it is enough. ## Job two: flag the language and the patterns before they compound ![MangoApps job creation screen showing an AI Job Generator modal for creating a Retail Manager posting with employment details, context, salary range, and work location.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_ai-generated-job-posting.png) The second job is the one that is easiest to defend, because it is preventive rather than predictive. Before a role goes live, the agent reviews the posting and flags things like gendered terms and inflated credential requirements. That is a change made at the top of the funnel, where it is cheap and uncontroversial, and it holds one standard across departments that would otherwise each write their own. Once the pipeline is running, the same monitoring works on drop-off. Where do qualified candidates exit at higher rates than the data supports? That is a pattern question, and patterns are exactly what a person reviewing candidates one at a time cannot see. Equity data then rolls into aggregate reporting that is ready for an EEOC or internal review rather than assembled by hand at filing time. Two guardrails belong with this claim. Consistent structure reduces recency and impression bias; it does not eliminate bias, and no vendor should say otherwise. And when the product suggests a practice change, that is a suggested action inside a workflow, not a vendor position on how you should hire. ## Job three: notice the candidate who is going cold ![Recruiting analytics dashboard showing seasonal hiring patterns, pipeline trends, and time-to-fill metrics alongside a professional working on a laptop.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_pipeline-intelligence-application-alerts.png) The third job is the one recruiters ask for by name once they have seen it. The agent tracks time-in-stage and engagement signals, then flags candidates who have waited longer than the stage warrants and routes them to the recruiter. Engagement signals are specific and checkable: email opens, portal logins, time in stage. A finalist who has not opened anything in five days is a different situation than one who checks the portal daily, and neither shows up in a stage report. It also identifies where the pipeline is backing up, which stage conversion lags and where time-in-stage runs long. That is bottleneck detection, and it is the input to the two waits that actually cost most teams their finalists. The stalled-application alert is the highest-value item on this list for one reason: nobody loses a candidate on purpose. They lose them in a week where three other searches were louder. ## Job four: prepare the structure for a fair interview ![Screenshot of a recruiting interview question bank showing searchable questions, filters, difficulty ratings, usage metrics, and structured interview features.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_ai-generated-question-scorecards.png) The fourth job happens between screening and interview. The agent builds a role-specific question guide from the role's skills and the hiring manager's input, so the panel asks every candidate the same questions. Interviewers score in-platform right after the conversation, in a comparable format, while the impression is fresh. That structure is what makes evaluations comparable across candidates and across interviewers. It is also the mechanical proof behind the defensibility argument: consistent questions plus a logged approval chain is what "defensible" means in practice, as distinct from "documented somewhere." > ![Angled view of a green MangoApps guide titled “End-to-End Talent Acquisition” displayed on a warm peach gradient background.](https://mango-cdn.b-cdn.net/marketing/uploads/talent-acquisition_thumbnail.png) > **Get the complete playbook:** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) covers what AI does at every stage of hiring and the governance model underneath it, from permission inheritance to the four autonomy levels. ## What it does not do Worth stating plainly, because the omissions are the product decision. It does not reject candidates. It recommends, and a person approves, rejects, or re-runs the screening. It does not decide who gets hired, set compensation, or send an offer. It does not learn from the open web; it draws on your data and your configured knowledge base, which is what keeps its answers in scope. It does not see more than the person asking it is allowed to see. And it does not act at whatever level it prefers. You choose how far each agent goes on its own, across four autonomy levels: observe-only, suggest, approve, and run automatically. Most organizations start at observe-only or suggest for candidate-facing steps and stay there deliberately. ## The governance questions worth asking any vendor Six questions. The answers separate governed AI from AI that happens to have a permissions page. - **Does the AI inherit our permission model, or does it have its own?** The standard to insist on: a recruiter's AI view is scoped to their requisitions, a hiring manager's to their candidates, an HRBP's to their aligned population, natively rather than by convention. No user should be able to surface through AI what they could not access directly. - **Does candidate or employee data train public models?** The answer needs to be no, with processing staying inside your boundaries. - **Can we choose the model?** Provider choice should be a configuration setting rather than a re-platform, with failover if a provider is unavailable, and a private option where isolation is required. - **Is every AI action logged in the same record as the human ones?** An audit trail that covers people but not agents is not an audit trail. - **What triggers each automated action, and who sees the result?** Ask specifically about the stalled-application alert. It is a good test because the answer has to name a threshold and a recipient. - **How do we set and change autonomy?** If the answer is that the vendor decides, the answer is no. The line worth remembering while you evaluate: AI inherits permissions. It does not override them. ## Where MangoApps fits ![MangoApps security, compliance, access controls, AI governance, and implementation overview featuring HITRUST CSF, SOC 2 Type II, ISO 27001, and 99.9% uptime claims.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_enterprise-security-ai-governance.png) The reason MangoApps can make these claims is not model quality. It is that identity, employee data, permissions, and workflows already live in one place, so the AI has a governed context to act in. A chatbot bolted onto a stack of disconnected tools can answer a question. It cannot safely act, because it cannot see across the work or be trusted with the permissions to change it. That distinction is the whole platform argument, and it is why the AI story here is evidence for the architecture rather than the headline over it. Concretely: more than 20 AI capabilities run inside the apps employees already use, reached through one front door, with [translation built in](https://www.mangoapps.com/ai/translation) and no separate AI tool to buy, learn, or govern. Specialist [agents](https://www.mangoapps.com/ai/agent-library) take governed action inside the business area they belong to. [Governance](https://www.mangoapps.com/ai/governance) covers permission inheritance, model choice across providers with automatic failover, private LLM support, and full logging. The [certifications](https://www.mangoapps.com/security-compliance) behind it are HITRUST CSF, SOC 2 Type II, and ISO 27001 held simultaneously, plus FedRAMP ATO, HIPAA, and GDPR. MangoApps has built for the frontline for 15+ years, serves 2M+ users, and retains 98% of customers, with 90%+ adoption typically reached within 90 days of launch. ## Frequently asked questions **Does AI screening replace recruiter judgment?** No, and a vendor promising that is describing a compliance problem rather than a product. The useful division is that AI handles volume work, parsing, ranking, monitoring, and scheduling structure, and people handle judgment. The visible controls in a well-designed screening view are approve, reject, and re-run, all of which belong to a person. **How does an AI agent know what it is allowed to surface?** It inherits the permission model your organization already defined. Scope follows the calling user, so the agent cannot return anything to a person that the person could not already access directly. **Does our candidate data train public AI models?** It should not, and in MangoApps it does not. Processing stays inside your governed environment, model choice across providers is a platform setting with automatic failover, and a private option is available where isolation is required. **What happens to candidate data when a search closes?** Retention, deletion, and export policies are configurable to your requirements, with support for data subject requests and audit-ready records, which matters for FCRA and EEOC obligations. Your legal and compliance teams define the data lifecycle and the platform enforces it. **Can we start with AI in observe-only mode?** Yes, and it is usually the right way to begin. Run it alongside your current process, compare its shortlists to your recruiters' shortlists for a few weeks, and raise the autonomy level per workflow once you have your own evidence rather than the vendor's. > **Start with the playbook.** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) sets out the AI capabilities and the governance model in full. When you want the six questions above answered against your own permission model, [schedule a call](https://www.mangoapps.com/schedule-a-call). ## Keep reading - [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) - [Talent acquisition](https://www.mangoapps.com/solutions/talent-acquisition) - [AI governance](https://www.mangoapps.com/ai/governance) - [Agent library](https://www.mangoapps.com/ai/agent-library) - [AI capabilities](https://www.mangoapps.com/ai/capabilities) - [Security & compliance](https://www.mangoapps.com/security-compliance) --- # The Two Recruiting Delays That Cost You Finalists **Author:** Christos Schrader **Published:** 2026-08-28 **Category:** talent-acquisition Most finalist losses happen during two administrative waits: interview scheduling and the gap between verbal acceptance and a signed offer. Ask a recruiting team where they lose finalists and you will hear about compensation, counter-offers, and candidates who were never really going to leave. Look at the timestamps and a different pattern shows up. Two waits account for most of it, and neither is a decision. One is scheduling. The other is the gap between a verbal yes and a signed letter. Both are administrative. Both are measured in days. And the fastest-moving candidates, the ones holding the most competing offers, are the most sensitive to both. ## Wait one: the days between "let's interview them" and the interview ![MangoApps interview scheduling dashboard showing a monthly interview calendar, filters, upcoming sessions, and integrations with Outlook, Google Calendar, and Apple Calendar.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_automated-self-scheduling-calendar-integration.png) The scheduling loop is where the most avoidable delay in recruiting lives, because it multiplies. One interviewer is a two-email exchange. Five interviewers across two time zones, with an existing calendar each, is a coordination problem that takes a day to solve and a week to actually run. Add a multi-round loop where each stage is scheduled after the previous one concludes, and you have built a queue where nothing is wrong and nothing is moving. The fixes are unglamorous and specific: - **Let the candidate book.** Real open slots, shown in the candidate's own time zone, bookable in seconds. Self-scheduling removes the exchange entirely rather than compressing it. - **Sync the calendars that already exist.** Outlook, Google, and iCal kept accurate, so an open slot is genuinely open and double-booking is not a recurring embarrassment. - **Solve for the panel at once.** Find the overlapping availability across every required interviewer in one pass instead of polling them serially. - **Sequence the loop in advance.** Configure the stages so a candidate advances to the next round automatically rather than re-entering the scheduling queue after each one. - **Send the reminders.** Configurable pre-interview prompts cut no-shows without anyone doing manual outreach, and a no-show is a full round-trip through the whole loop again. There is also a volume case, which retail, hospitality, and seasonal hiring teams know well. When you are hiring forty associates for a store opening, sequential one-to-one interviews are not slow, they are impossible. Group and batch sessions, one session run for many candidates at once, are what makes the timeline work at all. ## What to do with the time you interview in ![Screenshot of a recruiting interview question bank showing searchable questions, filters, difficulty ratings, usage metrics, and structured interview features.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_ai-generated-question-scorecards.png) One more thing belongs here, because it is the difference between fast interviewing and good interviewing. Speed only helps if the conversation produces something comparable. A role-specific question guide, built from the role's requirements and the hiring manager's input, gives every candidate the same questions. Interviewers score in-platform right after the conversation rather than reconstructing an impression later. The structure reduces recency and impression bias, which is a claim about consistency rather than a claim about eliminating bias. Structured evaluation is usually sold as a fairness measure. It is also a speed measure, because comparable scorecards are what let a panel reach a decision in one meeting instead of three. > ![Angled view of a green MangoApps guide titled “End-to-End Talent Acquisition” displayed on a warm peach gradient background.](https://mango-cdn.b-cdn.net/marketing/uploads/talent-acquisition_thumbnail.png) > **Get the complete playbook:** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) covers interview scheduling, offer management, and background screening in full, including what each wait costs and where the days actually go. ## Wait two: the week between yes and signed ![MangoApps-style HR dashboard showing an accepted candidate offer, post-acceptance checklist, candidate journey, and multi-level approval workflow.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_muti-level-approval-workflows.png) The second wait is shorter on paper and more expensive in practice, because it happens after you have already won. Here is the sequence in most organizations. The offer letter gets built from a template, usually the last similar one. Compensation gets checked against something, sometimes a benchmark, sometimes memory. Approval gets requested by email and granted in chat. Signature routes through a separate e-signature vendor. Status lives on a spreadsheet one person maintains, so "where is the offer" is a question answered by a human. A week is a realistic duration for that, and a week is exactly long enough for a candidate to develop second thoughts, take a call from a recruiter who moves faster, or renegotiate from a position of new leverage. What compresses it: - **Templates that pre-populate.** Role-specific letters that carry compensation, start date, and the right clauses for that role, level, and location, so nobody is editing last quarter's letter. - **Benchmarking before the number is set.** Market data and internal comparisons surfaced while the offer is being built, so the number is right the first time instead of after a second approval cycle. - **Routing rather than asking.** Approvals that route automatically by department, salary band, or org level, with each step logged in the candidate record. - **Approval from a phone.** Approve, modify, or escalate without a VPN or a desktop session. The single most common cause of a stalled offer is an approver who is not at a desk. - **Signature in the same place.** Candidates sign from any device and the signed letter files itself into the record, which removes both the vendor round-trip and the "did we get it back" check. - **Status without a phone call.** Sent, opened, under review, signed. Visible, so the recruiter stops manufacturing follow-up excuses to find out. And the messiest case, which most tooling ignores: a counter-offer should route back through the same approval chain that produced the original, with the revision logged. Negotiation is where records usually get informal, and it is the moment when a clean record is worth the most. ## The wait after the wait ![MangoApps Job Board integration settings showing background check integration options and a browse panel listing Checkr, Sterling, HireRight, and a custom API.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_integrated-provider-connections.png) One more delay sits between signature and start, and it is worth naming because teams often accept it as physics. Background screening is one of the most avoidable sources of delay in hiring, and it is usually slow for a structural reason rather than a vendor one: it lives in a separate system with manual initiation and manual tracking. Ordering the check at the offer stage without re-entering candidate data, receiving results back into the same record as the scorecards and the offer letter, and configuring the right package per role type once, so it applies automatically, takes days out of the sequence. Where checks are part of a regulated hiring workflow, the consent, authorization, and adverse action steps run in order in the same place. ## Where MangoApps fits The reason both waits collapse on one platform is that neither is really a scheduling or a documents problem. Both are handoff problems. In the MangoApps [Talent Acquisition Suite](https://www.mangoapps.com/solutions/talent-acquisition), the Interview Scheduler, structured scorecards, Offer Manager with native e-signature, and Background Checks all read and write the same candidate record. An offer arrives at the approval chain without re-entry. A signature triggers [onboarding](https://www.mangoapps.com/solutions/hr-operations) on its own, provisioning access and queuing [required training](https://www.mangoapps.com/solutions/performance-learning) before day one. Time in each stage is visible in [full-funnel reporting](https://www.mangoapps.com/analytics-insights), which is how you find out which of the two waits is actually costing you finalists. Native signature is a small detail with an outsized effect: an offer that does not leave the platform to be signed does not have to come back. MangoApps has built for the frontline for 15+ years, serves 2M+ users, retains 98% of customers, and typically reaches 90%+ adoption within 90 days of launch, backed by the Adoption Guarantee. ## The measurement that ends the argument Stop reporting one time-to-fill number. Split it. Measure the days inside the scheduling loop and the days between verbal offer and signature as two separate figures, per role family. Then compare each against your finalist decline rate. Most teams discover that their slowest stage is not the one they have been optimizing, and that neither of the two expensive waits was ever a hiring decision at all. > **Start with the playbook.** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) covers both waits and the rest of the funnel around them. When you want your last five finalist declines laid against the timestamps, [schedule a call](https://www.mangoapps.com/schedule-a-call). ## Keep reading - [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) - [Talent acquisition](https://www.mangoapps.com/solutions/talent-acquisition) - [HR operations](https://www.mangoapps.com/solutions/hr-operations) - [Analytics & insights](https://www.mangoapps.com/analytics-insights) - [Integrations](https://www.mangoapps.com/integrations) - [Hospitality](https://www.mangoapps.com/industries/hospitality) --- # Why Frontline Hiring Needs a Mobile-First Talent Platform **Author:** MangoApps Team **Published:** 2026-08-28 **Category:** talent-acquisition Frontline candidates need phone-native applications, SMS onboarding, and mobile approvals—not desktop-first ATS workflows that slow hiring. The store associate. The charge nurse. The field technician. The warehouse crew. That is where the volume is in most enterprises, and it is the population hiring software is worst at serving. Not because vendors ignore it, but because the entire category was designed around a candidate who has a laptop, a corporate inbox, and twenty uninterrupted minutes to complete an application. Frontline candidates have none of those things. They have a phone, often their personal one, and they are applying to two other employers this week. ![Laptop and smartphone displaying a branded job board with current openings, applications, and candidate tools, accompanied by callouts for a customized candidate experience and self-service mobile efficiency.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_branded-career-page-applicant-portal.png) ## What actually goes wrong for a frontline candidate The failures are mundane, which is why they persist. An application form that assumes a desktop browser and a resume file. A screening step delivered to an email address the candidate does not check. An interview confirmation sent to a corporate inbox they were never given. A scheduling link that expects them to compare calendars while they are on shift. An offer that requires a desktop signature session. An onboarding portal that needs a company device and a login provisioned by IT, which is exactly the thing that cannot happen before day one. Each of those is a small friction. Together they are a filter, and it filters for the wrong thing. It does not select for the best associate or the most reliable technician. It selects for whoever had the equipment and patience to finish. Meanwhile the fastest-moving candidates hold the most competing offers, and frontline hiring markets move in days. Every one of those small frictions is a place where a competitor with a simpler application gets the person you wanted. ## Why a standalone ATS struggles with this population specifically An applicant tracking system is built to track candidates for recruiters. That is a real job and most systems do it adequately. The frontline problem is not tracking. It is reach. Reaching a candidate who has no corporate email means reaching them where they already are, which means push notification, SMS, and a phone-native experience that does not depend on an inbox. Reaching a new hire before day one means reaching them before any company account exists. A standalone ATS cannot solve that with a better mobile view, because the gap is not the interface. It is that the ATS has no channel to the person and no relationship to the systems that will run their actual work. Ask the question this way instead: if a candidate or new hire needs a second app, a kiosk workaround, or a company device to apply, schedule, or onboard, has the platform actually reached your workforce? ## What good looks like from the candidate's side Start from the phone and work backward. The requirements get short. Every field, upload, and question works on the phone candidates actually apply from. Open roles are filterable by location, type, and pay range, because those are the three things a frontline candidate is deciding between. Applicants can check their own status without emailing anyone, which also removes most of the inbound volume HR fields. Interview slots appear as real open times in the candidate's own time zone, and booking takes seconds rather than a thread. The offer can be reviewed and signed from any device. Onboarding arrives by SMS invite or a QR code at the location, on the phone they already carry, with no corporate email and no company device required. That last mechanism deserves more attention than it usually gets, because it is the one that makes the rest possible. An SMS invite or a QR code at the site is how a person with no company account reaches a structured onboarding experience before their first shift. > ![Angled view of a green MangoApps guide titled “End-to-End Talent Acquisition” displayed on a warm peach gradient background.](https://mango-cdn.b-cdn.net/marketing/uploads/talent-acquisition_thumbnail.png) > **Get the complete playbook:** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) covers frontline hiring end to end, from a phone-native application through onboarding by SMS invite and into the first scheduled shift. ## What good looks like from the manager's side The manager side of frontline hiring is usually treated as an afterthought, which is strange, because the manager is the person whose approval is holding up the offer. ![Laptop and smartphone displaying MangoApps Offer Manager, with a new job offer form on desktop and candidate offer statuses on mobile.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_offer-creation-compensation-benchmarking.png) Approve, modify, or escalate an offer from a phone, with no VPN and no desktop session. See where an offer stands, sent, opened, under review, or signed, without a follow-up call. Get a push notification when a new hire's onboarding checklist is assigned rather than finding out on their first morning. A store manager between deliveries and a charge nurse between rounds are not going to open a laptop to unblock a hire. If approval requires a desk, approval waits until the end of the week, and the candidate who was deciding between two offers does not. ## The part that only works if hiring connects to the work Here is where frontline hiring differs from corporate hiring in kind, not degree. A frontline hire is not finished when they are hired. They are finished when they are scheduled, equipped, and cleared. - **Onboarding into the schedule.** Completed onboarding makes a new hire eligible for the next [schedule cycle](https://www.mangoapps.com/solutions/workforce-management) automatically, so the first shift is booked the moment they are ready rather than a week later. - **Certification-aware dispatch.** A new technician's credential status is visible at the moment a routing decision is made, so they only get [field work](https://www.mangoapps.com/solutions/field-service) they are cleared for, before the route is published. - **Safety before assignment.** Onboarding tracks safety training, and assignment to safety-critical roles stays gated on completion, so nobody is scheduled into work they are not yet cleared to do. That is [compliance](https://www.mangoapps.com/solutions/safety-compliance) at build time rather than audit time. - **Equipment without the ticket chase.** Acceptance triggers provisioning, so devices, credentials, and access are assigned and configured during onboarding through the same platform that runs [IT and procurement](https://www.mangoapps.com/solutions/it-procurement). None of that is possible when recruiting sits in a system that does not know the schedule exists. All of it is straightforward when a completed hire becomes a scheduled, equipped, credentialed worker with no manual handoff. ## Where MangoApps fits ![Three-column infographic outlining MangoApps capabilities across employee experience, frontline operations, and people operations, unified by one shared Mango platform base.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_one-shared-mango-platform-base.png) MangoApps is The Enterprise Workforce Platform Built for the Frontline, and hiring is one workflow on it rather than a separate product bolted alongside. That has one practical consequence worth more than any feature list: the app where a new hire completes onboarding is the same [branded app](https://www.mangoapps.com/solutions/employee-app) their colleagues already open for company news, their team, and their shift. New hires do not learn a recruiting portal, then an onboarding tool, then an intranet. They find one more thing in the app they will use for the rest of their tenure. Welcome content, pre-boarding reminders, and week-one prompts go out through the same [targeted channels](https://www.mangoapps.com/solutions/internal-communications) as every other employee communication, by push, SMS, and email, with follow-up for anyone who misses the first message. The proof that matters for this population is adoption, not features. MangoApps has built for the frontline for 15+ years rather than retrofitting a desk product, serves 2M+ users, retains 98% of customers, and typically reaches 90%+ adoption within 90 days of launch. The Adoption Guarantee puts terms behind it: if employees do not adopt after launch, you do not pay. ## The test to run this week Take out your own phone. Not a test device, and not the demo environment. Find one of your open frontline roles the way a candidate would. Apply. Note every point where you needed a laptop, a file, an email account, or a password. Then ask the same of the first week: could a new hire complete their documents, meet their manager, and see their first shift from that same phone? Most hiring is frontline hiring. The software should be able to survive that walkthrough. > **Start with the playbook.** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) has the full frontline chapter, including how a completed hire becomes a scheduled, equipped, credentialed worker. When you want the walkthrough on one of your own roles, [schedule a call](https://www.mangoapps.com/schedule-a-call). ## Keep reading - [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) - [Talent acquisition](https://www.mangoapps.com/solutions/talent-acquisition) - [Employee app](https://www.mangoapps.com/solutions/employee-app) - [Workforce management](https://www.mangoapps.com/solutions/workforce-management) - [Field service](https://www.mangoapps.com/solutions/field-service) - [Retail](https://www.mangoapps.com/industries/retail) - [Healthcare](https://www.mangoapps.com/industries/healthcare) --- # How to Build a Defensible Talent Acquisition Process **Author:** Christos Schrader **Published:** 2026-08-28 **Category:** talent-acquisition Learn how to create defensible hiring records with structured scorecards, approval trails, compliant screening, and consistent candidate evaluations. A union steward files a grievance over a promotion that went external. A candidate's attorney requests the complete file for a rejected application. A state auditor picks ten requisitions at random and asks to see how each decision was made. None of these announce themselves in advance. And when they arrive, the question is always the same one: can you show how the decision was made, and can you show that it was made the same way for everyone? ## Defensible Is Not the Same as Documented Most recruiting organizations are documented. Very few are defensible, and the distinction is not pedantic. Documented means the artifacts exist somewhere. Interview notes are in the applicant tracking system, or in a hiring manager's notebook, or in a Slack thread. The approval happened, probably by email. The scorecards exist for the roles where the panel remembered to fill them in. The background check result is in the vendor portal, under whichever account the recruiter used. Defensible means something stricter. It means the same criteria were applied to every candidate for that role, the evidence sits in one place in one format, the approval chain is visible with names and timestamps, and a person who was not present can reconstruct the decision from the record alone. The gap between those two states is where risk lives. And it is not a diligence gap. It is an architecture gap. ## Five Systems Cannot Agree on a Story ![Diagram showing a central candidate profile connected to ATS, calendar, offer tools, background checks, and onboarding systems, highlighting disconnected recruiting workflows.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_point-solution-trap.png) Here is what actually happens when a hiring decision gets questioned in a fragmented stack. The evidence is scattered across five systems, and no two of them tell the same story. The ATS has a stage history but no interview substance. The scheduling tool knows when the panel met. Interview feedback is partly structured, partly verbal, and partly missing. The offer approval lives in email. The background check result and its adjudication live with the vendor. Somebody then assembles a narrative from all of it, weeks after the fact, under time pressure, for a reader who is looking for inconsistency. That assembly is the problem. Not because anyone is hiding anything, but because a reconstruction is not a record. It carries the reconstructor's judgment about what mattered, and it cannot demonstrate consistency across candidates, which is usually the actual question being asked. In regulated industries, the public sector, and any union environment, this is the cost that never appears in a software comparison. A fragmented stack makes consistency nearly impossible to prove, because proof requires one record and the stack has five. ## What a Defensible Record Actually Contains ![Screenshot of a recruiting interview question bank showing searchable questions, filters, difficulty ratings, usage metrics, and structured interview features.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_ai-generated-question-scorecards.png) Strip out the compliance language and the requirement is concrete. For any hire, and for any candidate who did not get the job, you should be able to produce these from one place: - **The criteria, set before the search.** The role's requirements, screening questions, and the standard against which candidates were scored, recorded before applications arrived rather than described afterward. - **The same questions, asked of every candidate.** A structured question guide per role means evaluations are comparable. Consistent structure also reduces recency and impression bias, which is a claim about the process rather than a claim about eliminating bias. - **Scorecards captured at the time.** Interviewers scoring in-platform right after the conversation, in a comparable format, rather than reconstructing an impression a week later for a form somebody chased them about. - **The approval chain with names and timestamps.** Who approved the offer, at what level, in what order, and what changed between versions. Routing by department, salary band, or org level is what makes that chain consistent instead of ad hoc. - **Screening handled in the correct legal sequence.** Where background checks apply, consent and authorization recorded, results stored with the rest of the file, and the adverse action sequence run in order: pre-adverse notice, waiting period, final action. - **Aggregate equity data that was not assembled by hand.** Pass-through rates across populations as they happen, feeding EEOC and internal reporting from the same data the hiring decisions were made in. Read that list again and notice what it is not. It is not more paperwork. It is the same information you already collect, held in one shape. > ![Angled view of a green MangoApps guide titled “End-to-End Talent Acquisition” displayed on a warm peach gradient background.](https://mango-cdn.b-cdn.net/marketing/uploads/talent-acquisition_thumbnail.png) > **Get the complete playbook:** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) covers the defensibility argument in full, including structured scorecards, approval routing, screening sequence, and the AI governance model behind them. ## The Questions Public-Sector and Union Buyers Ask That Nobody Else Does Talent acquisition vendors are used to questions about speed. Regulated and public-sector teams ask a different set, and the answers reveal more. Ask whether scorecards, approvals, and candidate communications live on one record or across five. Ask what the retention and deletion policy is when a search closes, and whether it is configurable to your legal team's requirements rather than the vendor's defaults. Ask whether the audit trail includes AI actions as well as human ones. Ask who can see what: whether a hiring manager's view is scoped to their candidates and an HRBP's view to their aligned population, natively, rather than by convention. Then ask the control question, which is the one that matters most in an environment where you cannot accept an opaque configuration: which decisions are yours and which are the vendor's? Requisition and approval routing, scorecard and screening criteria, offer structures, background-check packages by role, and how far any AI agent is allowed to act on its own should all sit in your column, not in a template you inherit. A good vendor answer is not "we are compliant." It is a specific description of where each artifact lives and who controls it. ## AI Makes This Question Sharper, Not Softer ![MangoApps-style HR dashboard showing an accepted candidate offer, post-acceptance checklist, candidate journey, and multi-level approval workflow.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_muti-level-approval-workflows.png) Any AI touching hiring inherits this problem, and inherits it at scale. The standard to hold is simple to state. AI should score and surface, and people should decide. Every AI action should be logged and reviewable in the same record as the human ones. AI should inherit the permission model already defined for your organization rather than working around it, which means a recruiter's AI view is scoped to their requisitions and a hiring manager's to their candidates. Candidate data should never leave your boundaries to train public models. The version of that principle worth writing on a wall: AI inherits permissions. It does not override them. There is also a preventive use of AI here that is easier to defend than a predictive one. Flagging gendered language and inflated credential requirements in a job posting before it goes live changes the funnel at the top, where it is cheapest and least contested. Surfacing where qualified candidates drop off at higher rates than the data supports is measurement, not advocacy. Both are audit-friendly because they produce evidence rather than conclusions. One guardrail worth stating explicitly, because it is easy to get wrong: recruiter and interviewer metrics belong in coaching conversations. Time-to-fill, acceptance rate, and 90-day retention are useful for developing a team. Presented as scores, they change interviewer behavior in ways that make the record less honest, not more. ## Where MangoApps Fits ![Banner displaying MangoApps security and compliance certifications, including FedRAMP, HITRUST CSF Certified, SOC 2 Type II Certified, and ISO 27001 Certified.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_recognized-secured-enterprise.png) The reason MangoApps can make the defensibility argument is the same reason it can make the speed argument: one data layer underneath every step. In the [Talent Acquisition Suite](https://www.mangoapps.com/solutions/talent-acquisition), structured question guides and scorecards, configurable multi-level approvals with a full activity log, role-based screening packages with the adverse action sequence handled in order, and aggregate equity reporting all write to the same candidate record. Regulated hiring workflow concepts route through [safety and compliance](https://www.mangoapps.com/solutions/safety-compliance), and the platform certifications sit with [security and compliance](https://www.mangoapps.com/security-compliance): HITRUST CSF, SOC 2 Type II, and ISO 27001 held simultaneously, the only unified employee platform with all three, plus FedRAMP ATO for US public sector, HIPAA with a BAA, and GDPR. Deployment can be SaaS, Private Cloud, Customer VPC, or On-Premise, with regional data residency where sovereignty rules require it. [AI governance](https://www.mangoapps.com/ai/governance) is where the two arguments meet. Every AI capability runs inside your permission architecture, no user can surface through AI what they cannot access directly, data never trains public models, model choice across providers is a configuration setting, and every AI action is logged and reviewable. Autonomy is yours to set, from observe-only through suggest, approve, and run automatically. MangoApps has built for the frontline for 15+ years, serves 2M+ users, retains 98% of customers, and typically reaches 90%+ adoption within 90 days of launch. Adoption matters to this argument more than it looks: a record is only defensible if the people making decisions actually use the system that holds it. ## The Standard Worth Adopting Before Anyone Asks Do not wait for the grievance, the request, or the audit to find out what your record looks like assembled. Pick ten requisitions from last quarter at random. Try to produce, from one place, the criteria, the questions asked, the scorecards, the approval chain, and the screening sequence for every candidate who reached final stage. Time yourself. However long that takes is your current answer to the question in the title. If it takes a week and three people, the decision was probably fine. The evidence is what is not defensible. > **Start with the playbook.** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) sets out what a defensible hiring record contains and how it is produced. When you want it tested against ten of your own requisitions, [schedule a call](https://www.mangoapps.com/schedule-a-call). ## Keep reading - [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) - [Talent acquisition](https://www.mangoapps.com/solutions/talent-acquisition) - [Security & compliance](https://www.mangoapps.com/security-compliance) - [AI governance](https://www.mangoapps.com/ai/governance) - [Safety & compliance](https://www.mangoapps.com/solutions/safety-compliance) - [Analytics & insights](https://www.mangoapps.com/analytics-insights) --- # 6 Ways to Build a Better Employee Onboarding Experience **Author:** MangoApps Team **Published:** 2026-08-28 **Category:** talent-acquisition Close the gap between offer acceptance and day one with six practical moves for automated, role-based, compliant employee onboarding. **Quick answer:** Most onboarding programs deliver paperwork, not onboarding, because acceptance in the recruiting system cannot start work anywhere else. The six moves that close the gap are: trigger the workflow at signature, collect documents before day one, provision access automatically, put the new hire in the app their colleagues already use, set the first 30 days before day one, and track completion while there is still time to help. ## The gap between what onboarding can do and what most programs deliver ![MangoApps new hire portal interface showing onboarding progress, required welcome content, team resources, and a mobile onboarding hub view.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_role-based-onboarding-workflows.png) The research on structured onboarding is unusually consistent. It produces 50% higher retention, a 62% productivity increase, and 69% of employees likely to stay (HBR 2022; Clickboarding 2020). Comprehensive onboarding also makes employees 33% more engaged at work (according to Forbes 2023). Very few organizations see those numbers, and the reason is not indifference. It is that most onboarding is a document exercise wearing an onboarding label: a stack of forms before day one, a welcome email with twelve links, a three-hour orientation that leaves the new hire to figure out the rest. Then day one arrives: a laptop that is not ready, a benefits portal nobody mentioned, a manager who has been in meetings all week. By the end of month one, a person you worked hard to win is quietly wondering whether they read the company right. That is not a program design failure. Programs are usually designed fine. It is that offer acceptance is treated as the end of recruiting and the start of onboarding, run by two teams with two systems, and nothing carries across the seam except a person doing it by hand. ## Move 1. Make signature the trigger, not the handoff The single most useful change is removing the human from the start of the workflow. When a signature is received, the onboarding workflow should start on its own: tasks assigned, documents requested, checkpoints scheduled, manager notified. No ticket to HR. No export. No "let me know when they sign." The test is simple. Ask who currently starts onboarding for a new hire, then ask what happens if that person is on vacation the week an offer is accepted. If the answer involves anyone remembering anything, the trigger is manual. ## Move 2. Configure by role, department, and location, not by generic checklist A generic checklist is what makes onboarding feel like processing rather than welcome, and it is also what makes it unsafe in regulated work. A retail store assistant, a clinical hire, a field technician, and a corporate analyst need different task sets, different documents, different training, and different first-week checkpoints. Building one list and asking people to ignore the irrelevant parts trains new hires to skim, which is exactly the behavior you cannot afford on the compliance items. Configure once per population, then let role and location decide what the new hire sees. ## Move 3. Finish the paperwork before day one, and store it where HR can find it ![Laptop mockup showing a SaaS Forms Library dashboard with onboarding, compliance, and built-in form templates, plus an employee information form preview.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_digital-document-collection-compliance.png) Pre-boarding exists so that day one is not a filing exercise. I-9, W-4, direct deposit, and policy acknowledgments should be completable from any device in the days between signature and start, with verification built into the workflow and each document stored with timestamps, version history, and access logs. For US-based teams, two details separate real compliance depth from a forms engine. The first is whether I-9 is handled in its actual sections, employee information, employer review, and reverification, rather than as one generic upload. The second is whether E-Verify is part of the flow or a separate errand. For hiring outside the US, the equivalent right-to-work documentation is handled with similar nuance. ## Move 4. Provision access, equipment, and training at acceptance This is the move that changes what the new hire experiences on their actual first morning. Role and location should set system access, content, groups, and required training automatically at trigger. Laptops, devices, credentials, and access get assigned during onboarding rather than through a ticket someone files the Friday before. Required courses assign by role and location and are ready at first login. In safety-critical work, assignment to the role stays gated on training completion, so nobody is scheduled into work they are not yet cleared to do. Their environment should be ready before they are. That is the whole standard, and it is measurable: on day one, count the number of things the new hire has to ask for. > ![Angled view of a green MangoApps guide titled “End-to-End Talent Acquisition” displayed on a warm peach gradient background.](https://mango-cdn.b-cdn.net/marketing/uploads/talent-acquisition_thumbnail.png) > **Get the complete playbook:** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) goes deeper on the onboarding gap, from pre-boarding and document compliance through provisioning and 90-day milestone tracking. ## Move 5. Put onboarding inside the app they will actually use Most onboarding tools are the second app a new hire learns and the first one they abandon. The alternative is to deliver onboarding through the same branded [employee app](https://www.mangoapps.com/solutions/employee-app) everyone else opens for company news, their team, and daily work. The new hire does not learn a recruiting portal, then an onboarding tool, then an intranet. They find one more thing in the app they will use for the rest of their tenure. This matters most for the population that has neither corporate email nor a company device. Onboarding reaches them by SMS invite or a QR code at the location, on the phone they already carry, and welcome content, pre-boarding reminders, and week-one prompts go out through push, SMS, and email with follow-up built in for anyone who misses the first message. Progress should also be visible where the work is. A new hire's checklist and first-week schedule belong in the flow of work, not in a portal they have to remember to open. ## Move 6. Set the first 30 days before day one The last move is the one that turns onboarding from an orientation into a ramp. Because recruiting, HR, learning, and performance can share one employee record, the first 30-day goals and the first review cycle can be set at acceptance rather than assembled in week three. Required courses complete and update the skills profile that managers and HR can see. A first-week check-in exists as a scheduled checkpoint with an owner, not as a good intention. The effect is that the new hire's first month has a shape, and the manager does not have to invent one during a week they are already in meetings. ## How to measure whether onboarding is actually working ![SaaS onboarding analytics dashboard showing completion tracking, automated alerts, effectiveness analytics, plan metrics, trends, and status breakdowns.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_90day-milestone-tracking-analytics.png) Four measures, and none of them is completion rate on its own. - **Time to first productive task.** The date the new hire does real work, not the date they finish orientation. - **Pre-boarding completion before day one.** The share of documents and tasks closed before the start date. This is the number that moves first when the trigger is automated. - **90-day retention by cohort.** Segment by role, location, and hiring manager. Onboarding problems are usually local, not organizational. - **90-day retention by sourcing channel.** This one requires recruiting and onboarding data on the same record, and it is the measure that tells you which channels produce hires who stay rather than hires who start. Watch for slipping tasks in real time rather than at the 90-day review, and route overdue alerts to both the new hire and the manager. The point of tracking is to help while there is still time to help. ## Where MangoApps fits ![Three statistic cards highlight streamlined recruiting and onboarding: unified candidate records, automated onboarding after offer acceptance, and more than 90% adoption within 90 days.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_what-mangoapps-does.png) MangoApps treats onboarding as part of recruiting rather than the thing that happens after it. In the [Talent Acquisition Suite](https://www.mangoapps.com/solutions/talent-acquisition), a received signature starts a role-based workflow: documents collected with FCRA-ready and audit-ready records, access and groups provisioned, [required training](https://www.mangoapps.com/solutions/performance-learning) auto-enrolled, and the new hire added to the directory and their team channels before they arrive. Completed onboarding can also make a new hire eligible for the next [schedule cycle](https://www.mangoapps.com/solutions/workforce-management) and make credential status visible at [dispatch](https://www.mangoapps.com/solutions/field-service), which is what "connected" means for frontline hiring specifically. Equipment and access requests route through the same platform as [IT and procurement](https://www.mangoapps.com/solutions/it-procurement), which removes the ticket chase that produces most day-one failures. MangoApps' own modeling anticipates roughly 40% faster onboarding from pre-boarding tasks completing before day one. Treat that as benchmark modeling rather than research, and validate it against your baseline. The adoption claim is the one with terms behind it: 90%+ adoption within 90 days of launch, backed by the Adoption Guarantee, which means that if employees do not adopt after launch, you do not pay. ## Frequently asked questions **What is the difference between onboarding and pre-boarding?** Pre-boarding is everything between signature and start date: documents, equipment preferences, welcome content, and introductions. Onboarding is the structured period after the start date, usually the first 30 to 90 days. The programs that produce retention gains do real work in both, because anything left in pre-boarding lands on day one, where it competes with actual work. **How long should onboarding last?** Ninety days is the practical horizon, with meaningful checkpoints in the first week, the first 30 days, and the first 90. The first 30 days are the most consequential period in an employee's tenure, and they are also the period most often left to the manager's improvisation. **Can onboarding reach employees who have no corporate email or company device?** Yes, and it has to, because most hiring is frontline hiring. The mechanism is a branded app on the employee's own phone, reached by SMS invite or a QR code at the location, with push and SMS for reminders. If onboarding requires a corporate inbox, most of your new hires will experience it as paperwork handed to them on day one. **Who owns onboarding, recruiting or HR?** Both, which is precisely why the handoff breaks. The useful reframe is that ownership matters less than whether the systems share a record. When acceptance in one system starts work in the other automatically, the org-chart question stops being load-bearing. **Does structured onboarding really affect retention, or is that correlation?** The published figures are associations rather than controlled experiments, so treat 50% higher retention and a 62% productivity increase (HBR 2022; Clickboarding 2020) as strong directional evidence rather than a guarantee. The operational logic is what makes them credible: a new hire whose access, training, goals, and first check-in are ready is having a different experience than one who spends week one waiting. > **Start with the playbook.** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) covers the full onboarding chapter, including what a signed offer should trigger before day one. When you want your own checklist walked through, [schedule a call](https://www.mangoapps.com/schedule-a-call). ## Keep reading - [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) - [Talent acquisition](https://www.mangoapps.com/solutions/talent-acquisition) - [HR operations](https://www.mangoapps.com/solutions/hr-operations) - [Performance & learning](https://www.mangoapps.com/solutions/performance-learning) - [Employee app](https://www.mangoapps.com/solutions/employee-app) - [IT & procurement](https://www.mangoapps.com/solutions/it-procurement) --- # The CFO Case for Talent Acquisition Infrastructure **Author:** Christos Schrader **Published:** 2026-08-28 **Category:** talent-acquisition Build a finance-ready business case for recruiting infrastructure using turnover, lost finalists, early exits, and coordination costs. Every talent acquisition leader has made the case for headcount. Fewer have made the case for hiring infrastructure, and the two arguments do not work the same way. Headcount is easy to price. Infrastructure is easy to postpone, because the cost of the current process is real but distributed: a few days here, a finalist there, an early exit that gets written up as a bad fit. Nothing arrives as an invoice. So build the case the way finance builds one. Four cost centers, each with a defensible number, none of them requiring a leap of faith. ## Start with what a departure actually costs ![Graphic stating that replacing a frontline or hourly worker costs roughly 40% of annual salary, while replacing a manager costs close to 200%, with a money illustration and Gallup attribution.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_cost-of-slow-process.png) The replacement math is the anchor, because it converts recruiting speed into a number the CFO already accepts. Replacing a frontline or hourly worker costs roughly 40% of annual salary. Replacing a manager runs close to 200% (according to Gallup). At any real hiring volume, those figures dwarf every software subscription in the recruiting stack combined. That matters for two reasons. The obvious one is turnover cost. The less obvious one is that a lost finalist has the same shape: when a manager-level search restarts because the preferred candidate accepted elsewhere, the eventual replacement cost for that role can run up to 200% of salary, and the delay is what caused it. Slow hiring is not just a service-level problem for hiring managers. It is a turnover multiplier. ## Then price the finalists you lose to the calendar The fastest-moving candidates hold the most competing offers. That single sentence is the whole economics of scheduling. Every day of scheduling back-and-forth is an opening for another employer. Every week waiting on a background check that lives in a separate portal is the same thing. Every offer that takes a week to move from verbal to signature, built from a template, reviewed by email, approved in chat, routed through a separate signature vendor, and tracked on a spreadsheet, sits inside the exact window where strong candidates get cold feet. To price it, take last year's numbers and answer three questions: - **How many finalists declined after reaching final-stage interview?** Not all applicants. Finalists, the ones you had already decided you wanted. - **How many of those declines cited timing, a competing offer, or "went another direction"?** That subset is your addressable loss. - **What is the blended replacement cost of the roles involved?** 40% of salary for frontline and hourly roles, close to 200% for managers, per the Gallup figures above. The result is usually the largest single number in the business case, and it is the one that has never appeared in a recruiting report, because nobody logs the reason a candidate stopped answering. ## Then the early exits that get attributed to fit ![Three circular charts highlight employee outcomes: 50% higher retention, 62% productivity increase, and 69% of employees likely to stay.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_what-strong-onboarding-proceduces.png) The offer-to-onboarding break has the longest-delayed cost of the four, which is why it survives so many budget cycles. Most organizations deliver paperwork rather than onboarding: a stack of forms before day one, a welcome email with twelve links, a three-hour orientation that leaves the new hire to work out the rest. The consequence appears in month one and month three, usually filed as a hiring mistake. The research says otherwise. Structured onboarding produces 50% higher retention, a 62% productivity increase, and 69% of employees likely to stay (HBR 2022; Clickboarding 2020). Comprehensive onboarding also makes employees 33% more engaged at work (according to Forbes 2023). At real hiring volume, the difference between a stack of forms and a connected onboarding program is measured in dozens of avoidable early exits a year, each one priced at the replacement math above. This is the cost center most likely to be under-counted in your current model, because nobody codes an exit as "onboarding." ## Then the coordination hours you are already paying for ![Three green statistic panels highlighting disconnected HR systems, employee job-seeking activity, and manager replacement costs, with sources credited to Ignite HCM and Gallup.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_hr-disconnected.png) The fourth cost is the one recruiting leaders feel every day and rarely quantify. In most stacks it takes four to six logins to move one candidate from application to offer. The hours go to copying a candidate from one system into another, chasing an approval, reconciling two calendars, and re-keying a resume that already said everything. 68% of companies operate with disconnected HR systems, and the inefficiency compounds at every system boundary (according to Ignite HCM). Price it directly. Take a recruiter's fully loaded cost, estimate the share of the week spent on coordination rather than candidates, and multiply by the size of the team. Most teams land somewhere uncomfortable. Then note what that spend buys: no improvement in candidate quality and no improvement in candidate experience. It is the purest overhead in the function. If you want a sharper version of the same number, count re-entry events instead of hours. Every point where a human retypes information the organization already has is a discrete, countable defect. > ![Angled view of a green MangoApps guide titled “End-to-End Talent Acquisition” displayed on a warm peach gradient background.](https://mango-cdn.b-cdn.net/marketing/uploads/talent-acquisition_thumbnail.png) > **Get the complete playbook:** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) sets out the cost of inaction transition by transition, along with the replacement-cost math and the onboarding research behind the numbers above. ## Build the case on four lines The version that survives a finance review fits on a single slide: - **Replacement cost avoided.** Reduced early exits, priced at 40% of salary for frontline roles and close to 200% for managers (Gallup). - **Finalist recovery.** Declines attributable to elapsed time in scheduling, offer, and background check, priced at the same replacement math. - **Recovered recruiter capacity.** Coordination hours redirected to candidate engagement, priced at fully loaded cost. - **Consolidation.** One fewer vendor to manage, one fewer contract to renew, one fewer integration to maintain, one fewer security review to run, and one fewer system for employees to learn. That last line is the one to hand to IT before the meeting rather than during it. It is usually the argument that turns a recruiting purchase into a platform decision, and it belongs to a stakeholder who is not in the room by default. ## What to expect on the other side ![Three statistic cards highlight streamlined recruiting and onboarding: unified candidate records, automated onboarding after offer acceptance, and more than 90% adoption within 90 days.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_what-mangoapps-does.png) Two expectations worth stating plainly, because a business case with inflated numbers does not survive its first quarterly review. MangoApps' own modeling anticipates roughly 40% faster onboarding, driven by pre-boarding tasks completing before day one rather than during week one. Treat that as MangoApps benchmark modeling rather than third-party research, and validate it against your own baseline in the first two quarters. The retention figure is sourced and can be cited directly: 50% higher new hire retention from structured, connected onboarding (HBR 2022). On timing, typical implementations run 8 to 12 weeks with a named Customer Success Manager from day one. That is the standard, not a marketing number, and it matters to the business case because a nine-month deployment changes the payback period entirely. ## Where MangoApps fits ![SaaS headcount planning analytics dashboard showing hiring velocity, budget utilization, time to fill, hiring quality, pipeline flow, spending, department costs, and quality distribution charts.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_budget-forecasting-approval-workflows.png) The reason a connected platform changes these four numbers is architectural rather than functional. Requisition, sourcing, screening, scheduling, offers, background checks, and onboarding share one data layer in the [Talent Acquisition Suite](https://www.mangoapps.com/solutions/talent-acquisition), so a signed offer starts onboarding on its own, provisions access, and queues [required training](https://www.mangoapps.com/solutions/performance-learning) before day one. Source attribution, offer detail, and 90-day retention sit on the same record, which is why [full-funnel reporting](https://www.mangoapps.com/analytics-insights) can tie a job board's spend to the hires that lasted. You do not have to replace anything to start. MangoApps connects to Workday, SAP SuccessFactors, UKG, ADP, BambooHR, and 200+ other systems through pre-built connectors and an open [API](https://www.mangoapps.com/integrations), and most organizations begin by closing the single most expensive gap in the list above. The supporting proof is the part finance will ask about: 15+ years building for the frontline, 2M+ users, 98% customer retention, 90%+ adoption within 90 days of launch, and a 99.9% uptime SLA that matters during peak hiring seasons. The Adoption Guarantee puts terms behind the adoption number: if employees do not adopt after launch, you do not pay. ## The line that belongs on the board's version Not "our recruiting tools are inefficient." That reads as a complaint. This instead: the organization is currently paying for coordination between systems, and the payment is being made in lost finalists, avoidable early exits, and recruiter hours. Every number in the case above is already being spent. The only question is whether it keeps being spent invisibly. > **Start with the playbook.** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) has the full cost-of-inaction breakdown to build the case from. When you are ready to model it against your own finalist declines and onboarding completion rate, [schedule a call](https://www.mangoapps.com/schedule-a-call). ## Keep reading - [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) - [Talent acquisition](https://www.mangoapps.com/solutions/talent-acquisition) - [Analytics & insights](https://www.mangoapps.com/analytics-insights) - [Success services](https://www.mangoapps.com/success-services) - [Integrations](https://www.mangoapps.com/integrations) - [Why MangoApps](https://www.mangoapps.com/why-mangoapps) --- # Where Recruiting Breaks: Fixing the Four Critical Handoffs **Author:** Christos Schrader **Published:** 2026-08-28 **Category:** talent-acquisition Recruiting delays rarely happen within stages. They happen at four handoffs where disconnected systems create data gaps, candidate drop-off, and slower hiring. **Quick answer:** Recruiting rarely fails in the middle of a stage. It fails in the four handoffs between them, where data stops moving and people start re-entering it: requisition to posting, screening to interview, interview to offer, and offer to onboarding. Each transition costs days, each day is an opening for a competing offer, and the cause is the same in all four, which is a process stitched together from systems that do not share data. ![Infographic outlining four fragmented recruiting stages: requisition to posting, screening to interview, interview to offer, and offer to onboarding.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_where-recruiting-breaks-down.png) ## The failure is in the seams, not the stages Most recruiting teams are good at the stages. They write solid job descriptions, run structured interviews, and make competitive offers. Diagnostic energy goes into the stages too: better sourcing, tighter screening criteria, faster decision-making. Then the same delays keep happening, which is the signal that the stages are not the problem. Recruiting breaks at the transitions. That is where a candidate stops being one record and becomes several, where context has to be carried by a person instead of a system, and where the elapsed time nobody owns quietly accumulates. Four transitions, each with its own failure mode. ## Transition one: requisition to posting, where speed is lost before the search starts Before a listing goes live, there are usually three handoffs. Headcount gets approved in a spreadsheet. The description gets drafted in a doc, often from the last version of a similar role. The requisition gets opened in the applicant tracking system, with somebody re-typing what the first two documents already said. None of those steps is difficult. Together they take days, and those days are pure loss, because a competitor's posting for the same role is already collecting applicants. In a market where 51% of U.S. employees are actively watching or seeking new jobs (according to Gallup), the strongest candidates are engaged somewhere else before a fragmented process even opens the req. ## Transition two: screening to interview, where you lose candidates to the calendar This is the transition with the highest candidate-visible cost, and it is almost entirely administrative. Resumes get reviewed in one system. Interviews get scheduled by email, across two or three interviewers with real calendars and occasionally different time zones. Feedback gets given verbally, in a hallway, or in a thread, and may never make it back to the candidate record at all. The fastest-moving candidates are the ones with the most competing offers, which makes every day of back-and-forth an opening for someone else. A single lost finalist for a manager-level role can represent up to 200% of annual salary in eventual replacement cost (according to Gallup). The scheduling loop is not an admin inconvenience. It is a competitive event. ## Transition three: interview to offer, where a week is enough to lose them The offer sequence is where the number of systems peaks. An offer letter built from a template. Compensation reviewed by email. Approval given in chat. Signature routed through a separate e-signature vendor. Status tracked on a spreadsheet that one person maintains. A week can pass this way, and that week is exactly when a strong candidate develops second thoughts and a faster competitor closes. Nothing in that sequence is wrong on its own. The problem is that no part of it knows the state of any other part, so "where is the offer" is a question that requires a human to answer. ## Transition four: offer to onboarding, where the experience turns bureaucratic ![Three circular charts highlight employee outcomes: 50% higher retention, 62% productivity increase, and 69% of employees likely to stay.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_what-strong-onboarding-proceduces.png) This is the largest break and the least discussed, because two teams and two systems meet here and both consider the handoff to be the other team's beginning. The moment a candidate says yes, the curated experience stops. The ATS updates. HR re-creates the record from the offer letter. A separate onboarding platform triggers, or gets triggered manually. IT receives a ticket. The new hire receives paperwork, which most organizations deliver instead of onboarding: a stack of forms before day one, a welcome email with twelve links, and a three-hour orientation that leaves them to figure out the rest. The cost shows up in month one and gets attributed to fit. It is not fit. Strong onboarding produces 50% higher retention, a 62% productivity increase, and 69% of employees likely to stay (HBR 2022; Clickboarding 2020). The gap between what onboarding can do and what most programs deliver is large, and it is mostly a technology problem. > ![Angled view of a green MangoApps guide titled “End-to-End Talent Acquisition” displayed on a warm peach gradient background.](https://mango-cdn.b-cdn.net/marketing/uploads/talent-acquisition_thumbnail.png) > **Get the complete playbook:** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) covers all four transitions in full, with the cost of each one and a four-step self-assessment for finding the transition costing you most. ## What the four transitions have in common None of these needs a catastrophe to add up. They compound through ordinary moments: a req that sat three days in a spreadsheet, a finalist who took a faster offer, an onboarding that was a stack of forms. The cause is identical in all four. A process assembled from systems that do not share data has to be held together by people, and people hold it together at the speed of email. So the fix is identical too. Not a better tool for the worst transition. One data layer underneath all of them. ## How to tell which transition is costing you most ![Four-step graphic outlining how to assess candidate-system touchpoints, identify data breakdowns, evaluate the candidate experience, and select connected platforms.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_what-leaders-need-to-do-differently.png) You do not need a consulting engagement to find out. Four steps, in order. 1. **Count the systems a candidate touches from application to day one.** This single number says more than any time-to-fill report. If it is higher than two, fragmentation is already costing you candidates. 2. **Find where the data actually breaks.** Map sourcing through 90-day retention and look for the re-entry points. The break is usually ATS data never reaching onboarding, or offer details re-keyed into HR. 3. **Assess the candidate experience, not the recruiter experience.** Walk the path as the candidate: does communication feel like one company, and does offer-to-onboarding feel coherent or feel like a transfer? 4. **Evaluate platforms that connect rather than digitize.** The question is not which step could be faster in isolation. It is what changes when every step reads and writes the same record. Step one is the diagnostic. Steps two through four are what you do with the answer. ## Where MangoApps fits ![Diagram showing eight talent management capabilities—including career site, AI screening, scheduling, offer management, background checks, onboarding, headcount planning, and a talent hub—connected to a single shared data layer.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_single-shared-data-layer.png) MangoApps built the [Talent Acquisition Suite](https://www.mangoapps.com/solutions/talent-acquisition) as one system rather than a set of connected tools, which is what makes the transitions disappear rather than get faster. A posting feeds screening. A candidate moved to offer arrives without re-entry. A signed offer triggers [onboarding](https://www.mangoapps.com/solutions/hr-operations), provisions access, queues required [training](https://www.mangoapps.com/solutions/performance-learning), and adds the new hire to the directory. Source, offer, onboarding status, and 90-day retention all sit on one record, so [full-funnel reporting](https://www.mangoapps.com/analytics-insights) is a query rather than a project. It works alongside what you already run. MangoApps connects to Workday, SAP SuccessFactors, UKG, ADP, BambooHR, and 200+ other systems through pre-built connectors and an open [API](https://www.mangoapps.com/integrations), so the usual starting point is closing the biggest gap, not replacing the stack. MangoApps has built for the frontline for 15+ years, serves 2M+ users, retains 98% of customers, and typically sees 90%+ adoption within 90 days of launch, backed by the Adoption Guarantee: if employees do not adopt after launch, you do not pay. ## Frequently asked questions **Why do recruiting delays cluster at handoffs rather than inside stages?** Because stages have owners and handoffs do not. Inside a stage, one team is accountable for the work and the tooling supports it. At a handoff, the data has to move between systems that were bought separately, so it moves when a person moves it. Elapsed time at a handoff belongs to nobody, which is why it rarely appears in a time-to-fill breakdown. **How many systems should a candidate touch between applying and day one?** Ideally one, realistically two. Once the count reaches four to six, which is common, every stage transition becomes a manual coordination task and reporting can no longer span the funnel. **Is the offer-to-onboarding break really a technology problem rather than a process problem?** Mostly technology. The process design is usually fine on paper. What fails is that acceptance in one system cannot start work in another, so a human has to re-create the hire. When a signature triggers provisioning, document collection, training assignment, and directory access automatically, the same process produces a completely different first week. **What should we measure to know whether the transitions are improving?** Track time inside each transition separately rather than one end-to-end number, and pair it with two outcome measures: offer acceptance rate and 90-day retention by sourcing channel. Time-to-fill tells you that something is slow. Transition-level timing tells you where. > **Start with the playbook.** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) is the full version of the argument above. When you want your own two worst handoffs mapped against one shared data layer, [schedule a call](https://www.mangoapps.com/schedule-a-call). ## Keep reading - [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) - [Talent acquisition](https://www.mangoapps.com/solutions/talent-acquisition) - [HR operations](https://www.mangoapps.com/solutions/hr-operations) - [Analytics & insights](https://www.mangoapps.com/analytics-insights) - [Integrations](https://www.mangoapps.com/integrations) - [Platform overview](https://www.mangoapps.com/platform) --- # Why Recruiting Infrastructure Is the Real Talent Problem **Author:** Christos Schrader **Published:** 2026-08-28 **Category:** talent-acquisition Recruiting inefficiency often comes from disconnected systems. Learn how a unified talent acquisition platform improves hiring and onboarding. Ask a VP of Talent Acquisition what their biggest problem is and the first answer is usually about process. Time-to-fill has crept up. Offer acceptance slipped last quarter. The candidate experience is not where it should be. Push a little further and the answer changes. The tools do not talk to each other. Candidate data lives in three places. Every hire takes manual coordination that nobody has time for and everybody does anyway. Those are not two problems. They are the same problem described from two vantage points, and the second description is the accurate one. The core challenge in most recruiting organizations is not sourcing, not compensation, not even the labor market. It is infrastructure. ## Every Tool in the Stack Was a Good Decision Here is the part that gets left out of the vendor pitch: nobody built this stack carelessly. The applicant tracking system was not producing enough qualified applicants, so a sourcing tool went in. Manual scheduling was eating a coordinator's week, so a scheduling app went in. Offers were slow, so an offer platform went in. Background checks needed to move faster, so a vendor got integrated, or half-integrated, or integrated in a way that works as long as one person remembers to export the file. Each decision was defensible. Each vendor made a compelling case. Each purchase closed a real gap that was costing real money at the time. That is what makes fragmentation so hard to see from inside. It does not arrive as one bad choice. It accumulates as a series of good ones. ## The Bill Arrives as Coordination ![Infographic showing a 68% statistic about companies operating with disconnected HR systems and inefficiencies compounding across system boundaries.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_disconnected-hr-systems.png) What the stack produces is not a broken process. Broken would be easier to fix. What it produces is a process that works, as long as people hold it together by hand. 68% of companies operate with disconnected HR systems, and the inefficiency compounds every time a process crosses a system boundary (according to Ignite HCM). In recruiting, those boundaries are everywhere: a requisition approved in a spreadsheet, a description drafted in a doc, a req opened in the ATS, resumes reviewed in one place, interviews scheduled by email, feedback that may or may not make it back, an offer built from a template and approved in a chat thread, a background check ordered in a separate portal, and a new hire re-created from scratch by a team that never saw the candidate. Count the logins and the number is usually four to six to move one candidate from application to offer. That coordination adds no value to the organization and no quality to the candidate experience. It is pure overhead, paid in the hours of the people you hired for their judgment. The recruiter's day tells the story better than any dashboard. Most people go into recruiting because they are good with people: reading someone, drawing out what they can actually do, matching them to work where they will be good at it. Then the hours go to copying a candidate from one system into another, chasing an approval, reconciling two calendars, and re-keying a resume that already said everything. That is not a talent problem. It is a wiring problem. > ![Angled view of a green MangoApps guide titled “End-to-End Talent Acquisition” displayed on a warm peach gradient background.](https://mango-cdn.b-cdn.net/marketing/uploads/talent-acquisition_thumbnail.png) > **Get the complete playbook:** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) maps how a fragmented recruiting stack gets built one defensible decision at a time, and what changes when every step reads and writes the same record. ## The Candidate Feels the Seams You Think Are Invisible Internally, fragmentation reads as inefficiency. Externally, it reads as character. A candidate moving through five systems gets five tones of voice, five kinds of confirmation email, and five different implied answers to the question "what kind of company is this." Then they accept, and the curated part ends. The ATS updates. HR re-creates the record. A separate platform triggers. IT gets a ticket. Day one arrives as a laptop that is not ready, a benefits portal nobody mentioned, and a manager who has been in meetings all week. ![Diagram showing a central candidate profile connected to ATS, calendar, offer tools, background checks, and onboarding systems, highlighting disconnected recruiting workflows.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_point-solution-trap.png) By the end of month one, a person you worked hard to win is quietly re-evaluating whether they read the company right. In a market where 51% of U.S. employees are already watching or seeking new jobs (according to Gallup), that quiet re-evaluation is expensive. Replacing a frontline or hourly worker runs roughly 40% of annual salary, and replacing a manager runs close to 200% (according to Gallup). The stack did not intend any of this. It simply had no way to know what the other systems were doing. ## Digitizing Each Step Is Not the Same as Connecting Them The instinct at this point is to look for a better tool for the worst step. It is the wrong instinct, and it is the reason the stack got built in the first place. Every point tool in recruiting was designed to solve one stage in isolation. They mostly do that well. What they do not do is share a data model, carry context between stages, or produce a report that spans the whole funnel. Adding a better one adds another boundary. The productive question is not which step to upgrade. It is what changes when every step reads and writes the same record. ![Diagram showing eight talent management capabilities—including career site, AI screening, scheduling, offer management, background checks, onboarding, headcount planning, and a talent hub—connected to a single shared data layer.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_single-shared-data-layer.png) The answer is specific and mostly unglamorous. A posting feeds screening. A candidate moved to offer arrives with no re-entry. A signed offer starts onboarding on its own, provisions access, queues required training, and puts the new hire in the directory before anyone messages IT. A 90-day retention rate shows up next to the sourcing channel that produced the hire, because both facts live on the same record. Nothing there is exotic. It is the difference between a platform designed as one system and a set of tools that share a login page. ## Where MangoApps Fits MangoApps built its [Talent Acquisition Suite](https://www.mangoapps.com/solutions/talent-acquisition) on a single data layer rather than assembling it from acquisitions. Eight capabilities, from career site and screening through interview scheduling, offers, background checks, and onboarding, run on the same underlying record, which is why a signature can trigger provisioning without a handoff. ![Three statistic cards highlight streamlined recruiting and onboarding: unified candidate records, automated onboarding after offer acceptance, and more than 90% adoption within 90 days.](https://mango-cdn.b-cdn.net/marketing/uploads/ta_what-mangoapps-does.png) Unified does not mean rigid, which is usually the next worry. Forms, fields, screening rules, approval chains, and the workflow itself are configurable without code. The requirements teams assume are too unusual for off-the-shelf software, internal versus external candidate pooling, priority funnels, group interviews for high-volume hiring, are setup options rather than exceptions. It also does not mean starting over. Most organizations begin with [keep and connect](https://www.mangoapps.com/integrations): the HRIS, payroll, and identity systems stay where they are, MangoApps connects through pre-built connectors and an open API across Workday, SAP SuccessFactors, UKG, ADP, BambooHR, and 200+ other systems, and the biggest gap gets closed first. Migration, if it ever happens, happens on your timeline. The proof worth asking about is adoption, not architecture diagrams. MangoApps has been building for the frontline for 15+ years, runs 2M+ users, keeps 98% of its customers, and typically reaches 90%+ adoption within 90 days of launch. The Adoption Guarantee is the version of that claim with money behind it: if employees do not adopt after launch, you do not pay. ## The Question Worth Asking at Your Next Stack Review Not "which tool should we replace." Try this one instead: how many systems does one candidate touch between applying and their first day, and how many of them know that the others exist? If the number is higher than two, fragmentation is already costing you candidates. It just is not showing up on a line item. > **Start with the playbook.** [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) covers the four transitions, the cost of each one, and the questions to ask any vendor. When you want it walked against your own job descriptions and approval chains, [schedule a call](https://www.mangoapps.com/schedule-a-call). ## Keep reading - [*End-to-End Talent Acquisition: The Modern Recruiting Playbook*](https://www.mangoapps.com/resources/talent-acquisition-book) - [Talent acquisition](https://www.mangoapps.com/solutions/talent-acquisition) - [HR operations](https://www.mangoapps.com/solutions/hr-operations) - [Integrations](https://www.mangoapps.com/integrations) - [Platform overview](https://www.mangoapps.com/platform) - [Why MangoApps](https://www.mangoapps.com/why-mangoapps) --- # Your AI Agent Is Reading a Copy of Your Business **Author:** Andy Tolton **Published:** 2026-08-27 **Category:** enterprise-ai AI pilots stall because agents read stale, permission-less copies of the business. Acting safely requires current state and binding permissions, which only native data provides. **The short version** Most enterprise AI pilots produce an assistant that answers impressively and cannot be trusted to do anything. Teams usually diagnose this as a model problem and go looking for a better one. It is a data-location problem. Integration-based architectures move copies of data between systems, and every copy ages the moment it lands, carries no permission context, and has no owner accountable for its accuracy. An agent reasoning over copies cannot know current state and cannot be bound by current permissions, which are the two conditions required to act rather than answer. An agent reading the native record can do both. That difference is architectural, and no amount of model capability closes it. --- ## The pilot that answers well and does nothing The pattern repeats across almost every enterprise AI program. The pilot goes well. The assistant summarizes the policy, finds the document, explains the benefits change. Everyone is impressed. Then someone asks the obvious next question: can it approve the shift swap, update the record, assign the training. And the honest answer is no, not safely, and the program stalls at "search with better manners." The instinct is to blame the model. The model is rarely the constraint. The smartest model available cannot safely approve a shift swap if it cannot tell who the employee is and what they are allowed to do. ## What an integration actually moves This is the part worth being precise about, because it is where the architecture decides the outcome. An integration does not give an agent access to your business. It gives the agent access to a copy of part of your business, on a schedule. Nightly, hourly, on webhook, it does not matter. What lands in the AI-accessible layer is an extract, and an extract has three properties that make it unsafe to act on: **It ages on arrival.** The moment the copy is written, it is a claim about the past. For reference content this is tolerable. For an employee record, where the fields that matter most are the ones that change (schedule, certification status, role, org placement, leave balance), it is a liability. An agent acting on a certification that expired since the last sync is not making a mistake. It is doing exactly what the architecture allows. **It carries no permission context.** Permissions are relational. They depend on who is asking, what role they hold, where they sit in the org, and what they are cleared to see. Extracts flatten that. What arrives is rows, and the permission logic has to be reconstructed somewhere downstream, usually in the application layer or, worse, in a system prompt. Reconstructed authorization is inconsistent authorization. **Nobody owns its accuracy.** The source system owns the source. The consuming system owns the consumption. The copy in between belongs to whoever built the pipeline, who has likely moved teams. When the copy is wrong, there is no single party accountable for it being right. ## Why this blocks action specifically Answering and acting have different requirements, and the gap between them is where most AI programs get stuck. **Answering** needs plausible, relevant context. A copy is usually adequate. If the assistant summarizes a policy that was revised last week, the failure is embarrassing but recoverable. **Acting** needs two things a copy cannot provide: **current state** and **binding permissions**. To approve a shift swap the agent has to know that the employee is actually certified right now, actually available right now, and that the person requesting it is actually authorized right now. Not as of the last sync. Now. This is why so many enterprises end up with [read-only AI they did not choose](/articles/three-approaches-enterprise-ai). It was the only safe option their architecture supported. ## The alternative, stated precisely MangoApps is the AI-Ready Employee Platform for the Frontline, and the architectural consequence of that is a single employee record. Every app reads from and writes to it. The record holds identity, role, org placement, skills, certifications, schedule, compensation data, training history, and the permissions derived from all of it. It syncs with your HRIS, payroll, and identity systems in real time, so the platform is never working from an export. The distinction that matters to an architect is between native data and a connected copy. | | Connected copy | Native record | |---|---|---| | Freshness | Accurate as of the last sync | Current state | | Permissions | Reconstructed downstream, per system | Resolved against one org model, below the agent | | Ownership of accuracy | Ambiguous | The source of truth is the record itself | | Write path | Back through the integration, if one exists | Direct, audited, permission-checked | | Failure mode | Silent staleness | Visible in one audit trail | **Agents on this platform do not query copies of your business. They read the same record the business runs on.** That is what turns answers into actions. Because the data is native, agents do not just find the answer. They [open the req, swap the shift, and close the ticket](/articles/ai-grounded-in-work). ## Integrate what you keep, consolidate what you don't None of this is an argument against integration, and it should not be read as one. It is an argument about direction. The posture worth adopting is deliberately two-sided: **integrate to sync the systems of record you keep, and consolidate the point tools you no longer need.** MangoApps connects to 200+ enterprise systems across Microsoft 365, Google Workspace, HRIS and payroll platforms, and identity providers, plus federated content so documents living in SharePoint or Google Drive surface inside the platform without migration. Your HRIS stays your HRIS. What changes is the count. Every app moved onto the platform is one fewer vendor, one fewer contract, one fewer SSO configuration, and one fewer integration to maintain. That is zero integration tax stated as an operating number: the stack gets smaller, not larger, every time the platform does more. Compare that to [the default trajectory](/articles/why-fragmented-tools-break-enterprise-ai), where each new capability adds an integration, each integration adds a copy, and each copy adds a surface the AI layer has to reason across and the security team has to reconcile. ## The question to ask a vendor When a vendor says their AI can act across your business, there is one question that resolves it quickly: *Is the agent reading our system of record, or a copy of it, and how do permissions get applied?* If the answer involves a sync interval, you have a copy. If the answer involves permission logic implemented in the application layer or described in a prompt, authorization is being reconstructed rather than enforced. Neither is disqualifying on its own. Both should change what you expect the agent to be allowed to do. For the fuller version of this evaluation, see [Eight Tests That Separate an AI Architecture From an AI Slide Deck](/articles/ai-vendor-proof-of-concept-tests). For what a shared foundation is composed of, see [What "Platform" Should Actually Mean](/articles/what-platform-means). --- **Go deeper:** The employee record architecture, the permission enforcement pipeline, and the integration posture behind these claims are documented in *The AI-Ready Employee Platform, Tech Leader Edition*. Download it from the resource library. --- ## Frequently asked questions **Why do enterprise AI assistants give outdated or incorrect answers?** Usually because they are reading copies of data rather than the source. Integration-based architectures move extracts between systems on a schedule, and an extract is a claim about the past. For fields that change often, such as schedules, certifications, roles, and leave balances, the copy is wrong more often than it is right, and the agent has no way to know. **Is retrieval-augmented generation (RAG) over integrated systems enough?** It is enough for answering and not enough for acting. RAG over extracts can produce a good response, but it cannot guarantee current state and it cannot enforce permissions, because the retrieval layer is working with flattened data that lost its permission context on export. Acting requires both. **What is an HRIS-grade employee record?** A single record holding identity, role, org placement, skills, certifications, schedule, compensation data, training history, and the permissions derived from all of it, maintained at the fidelity an HR system of record requires rather than as a directory entry. On the MangoApps platform every app and every agent reads from and writes to that same record. **Does this replace our HRIS or payroll system?** No. The posture is directional: integrate the systems of record you keep, consolidate the point tools you no longer need. The employee record syncs with your HRIS, payroll, and identity systems in real time, so the platform works from live data rather than an export while those systems remain authoritative for what they own. **How often does the record sync?** In real time with connected HRIS, payroll, and identity systems. The design goal is that the platform is never working from an export, which is the condition an agent needs in order to act rather than only answer. **Can an AI agent write back to the record?** Yes, within permissions and with confirmation. Writes resolve against the same permission model as reads, land in the same audit trail, and stop for explicit human approval on high-impact actions such as compensation changes, hiring decisions, and bulk operations. **How are permissions applied when an agent reads the record?** Below the agent, by the platform, against roles and org structure. An agent cannot return data the requesting user is not authorized to see, even when asked directly, because the authorization decision happens before the agent receives anything. Permissions are not enforced by the application layer and not by the prompt. **Doesn't consolidating tools just create a single point of failure?** It creates a single point of enforcement, which is the property a security architect usually wants. The consolidation that matters is not fewer logins. It is fewer permission models to reconcile and fewer places where an authorization decision can be made inconsistently. Availability is handled separately, with a 99.9% uptime SLA and deployment options from SaaS to on-premise. **What should we ask a vendor to prove their agent reads live data?** Change a value in the source system, then immediately ask the agent a question that depends on it. If the answer reflects the old value, the agent is reading a copy. Then attempt an action with a limited test user and confirm the attempt is scoped or refused and appears in the audit log. --- # Citizen Development Without the Sprawl: Building the Workflows No Vendor Shipped **Author:** Andy Tolton **Published:** 2026-08-27 **Category:** enterprise-ai Citizen development fails on governance, not ambition. When built apps run on the same identity, permissions, and audit trail as shipped apps, sprawl stops being the price of speed. **The short version** AI app builders have made it trivial for a business team to describe a workflow and get working software back. The capability is real. The question every technology leader should ask about it is not whether it works, but what stops it from becoming a thousand ungoverned micro-apps with their own data stores, their own permission logic, and their own orphaned owners. The answer is not policy. It is where the builder sits. When generated apps run on the same identity, the same employee record, the same permission model, and the same audit trail as everything the vendor shipped, there is no separate runtime to secure and no shadow data store to discover later. When the builder is a standalone product, every app it produces is a new thing to govern. --- ## The spreadsheet is a measurement, not a quirk Excel was built for financial modeling. It became the world's task tracker, project plan, inventory list, and, in an enormous number of frontline businesses, the actual shift schedule. The world's most-used scheduling system is a spreadsheet. That is worth sitting with, because it is not a failure of discipline. It is a measurement of demand for software that adapts to the work. Every one of those spreadsheets, and every point solution sitting next to them, exists for the same reason: a real workflow found no home in any vendor's product. Packaged software can only ever be as complete as its vendor makes it, and vendors build for the average of their customers because building for each one does not scale. So the business bends to the software, and the gaps get filled with more software. The average employee now works across 8 to 15 tools. That story is told in full in [Why Fragmented Tools Break Enterprise AI](/articles/why-fragmented-tools-break-enterprise-ai). What changed is that the gap can now close from inside the platform. ## What the build capability actually does Three surfaces, all driven by description rather than configuration: - **Plugin AI Builder.** Describe a widget, an agent, or a full plugin in plain language, then review it, govern it, and roll it out. - **AI Workflow Generator.** The approval chain or routing logic the business actually runs on, built from a description. - **AI Forms.** The inspection checklist or intake form, built from a description, a PDF, or an image of the paper form it replaces. The inputs matter more than they look. A photograph of a laminated safety checklist and a screenshot of a spreadsheet are the two most common source documents in frontline operations, and both are valid starting points. ## The sprawl question Here is the objection that separates a serious capability from a demo, and every technology leader should raise it in the first meeting: **what stops this from becoming a thousand ungoverned micro-apps?** Most answers are governance theater. Approval queues, naming conventions, a center of excellence, a quarterly review nobody attends. Those are policies applied on top of a runtime that does not enforce them. The structural answer is that everything built this way runs inside the foundation, not beside it: | Sprawl risk | Structural answer | |---|---| | A separate runtime to secure | There is no separate runtime. Built apps execute on the same platform as shipped apps. | | A shadow data store to discover later | Built apps read and write the same employee record. There is no second copy of anything. | | Custom permission logic per app | Permissions are enforced by the platform, not by the app and not by the prompt. A generated app inherits roles and org structure without configuration. | | An orphaned app whose owner left | Everything is visible to administrators in MangoApps Console with the same audit-ready visibility the rest of the platform gets. | | Untracked usage and quiet decay | Built apps move through the same Agent Development Lifecycle as shipped agents, with the same usage and outcome tracking. | The rule underneath all five is inheritance. A built app is not integrated with the platform. It is on it. ## A build, walked end to end Claims about inheritance are testable, so here is one workflow carried through every surface. The example is a certification-escalation tracker, the kind of tool that lives in a spreadsheet today because no vendor ships it. Operations wants expiring certifications logged, owners assigned, escalations tracked past deadline, and a dashboard tile for the compliance lead. 1. **Describe it.** Plain language, a spreadsheet screenshot, or a template starts the build. 2. **Refine.** The builder asks clarifying questions and confirms the spec before generating anything. 3. **Build and verify.** A working app is produced, with pages, fields, chains, and widgets, and is reviewed before it goes anywhere. 4. **Govern and roll out.** Same SSO, same roles, same permissions. The app joins the Agent Library with full rollback. 5. **CLI scripting.** The app is addressable from the terminal via `mango tools call`, returning structured JSON. 6. **External agent access.** An MCP-compatible agent such as Claude or Cursor connects over OAuth and operates under the invoking user's limits. Stages five and six are the ones that matter, and they are [the ones a demo will skip](/articles/ai-vendor-proof-of-concept-tests). A workflow described once by an operations lead is now reachable by a script an admin writes and by an external agent a different team connected, and it never left the governance model. That is what inheritance means in practice. More on the external-agent surface is in [Connecting Claude, ChatGPT, and MCP Agents to Workforce Data](/articles/mcp-enterprise-workforce-agents). ## Sunset, not orphan The lifecycle detail most citizen-development pitches skip is what happens at the end. A custom build is not a second-class citizen on this platform. It moves through the same seven-stage Agent Development Lifecycle as the agents MangoApps ships: opportunity, design, performance, context, develop, launch, and monitor and improve. [Governance is a stage in that lifecycle](/articles/governing-ai-by-design) rather than a checklist applied to it, so risk review happens at design time instead of after an incident. The monitoring stage tracks override rate, quality signals, and drift. And when something stops earning its keep, it is retired through the same lifecycle that launched it. Sunset, not orphan. That single property does more for long-term governance than any approval queue. The reason internal tool sprawl becomes unmanageable is almost never that too much got built. It is that nothing ever got removed, and eventually nobody can explain what any of it does or who has access. ## The programmatic floor For teams that want to go deeper than description, the platform is fully programmable: - **CLI** with 345+ governed commands across the employee lifecycle, scriptable for administration, provisioning, and automation. - **Developer SDKs** in TypeScript and Python. - **Integration fabric** with 200+ pre-built enterprise integrations, so what you build composes with the systems of record you keep. The same inheritance rule applies at every level. A script, an SDK call, and a plain-language description all resolve against the same identity, the same permissions, and the same audit trail. There is no privileged path that bypasses governance because it happened to be written in code. ## "We could build this ourselves" Every platform evaluation reaches this objection, and it deserves an honest answer rather than a defensive one. You can build it. You can build it here, which is the entire point of this capability. What you should not have to build is [the undifferentiated foundation underneath it](/articles/what-platform-means): the identity system that works for employees without corporate email, the HRIS-grade employee record, the permission enforcement that sits below the application layer, the audit infrastructure, and the frontline reach that took 18+ years to earn. None of that is a competitive advantage for your business. All of it is a multi-year program if you own it. Build the workflows that are actually yours. Inherit the rest. --- **Go deeper:** The full extension architecture, including the build walkthrough, the programmatic surface, and a proof-of-concept test for verifying that a generated app respects existing roles, is in *The AI-Ready Employee Platform, Tech Leader Edition*. Download it from the resource library. --- ## Frequently asked questions **What is governed citizen development?** It is the practice of letting business teams build their own workflows and applications on infrastructure that enforces identity, permissions, and audit centrally, so the resulting apps inherit governance rather than defining their own. The distinction from ordinary citizen development is structural: the apps run inside the platform rather than beside it, so there is no separate runtime, data store, or permission model to secure. **Does an app generated from a description respect existing roles and permissions?** Yes, without configuration. Permissions are enforced by the platform below the application layer, so a generated app resolves against the same roles and org structure as every shipped app. A builder cannot grant an app more access than the platform allows, because the app is not making the authorization decision. **Who can build, and does IT lose control?** Administrators control who can build, and every build requires review before rollout. IT gains control relative to the alternative, which is the team buying a point solution or building the workflow in a spreadsheet where there is no permission model, no audit trail, and no visibility at all. **Can a built app be rolled back?** Yes. Built apps join the Agent Library with version history and full rollback, and they are visible to administrators in MangoApps Console alongside everything else on the platform. **How is this different from low-code or no-code platforms?** Most low-code platforms are separate products with their own runtime, their own data layer, and their own connectors back into your systems of record. That is why they generate governance work. Here, the build surface is part of the employee platform, so a generated app reads the same employee record and writes to the same audit trail as everything else. There is nothing to connect and nothing new to secure. **What happens when the person who built an app leaves the company?** Nothing breaks and nothing disappears from view. The app remains visible in MangoApps Console with its permissions, usage, and audit history intact, and it can be reassigned or retired through the same lifecycle that created it. The orphaned-app problem is a property of tools that run outside central visibility. **Does a custom build get the same monitoring as shipped features?** Yes. Custom builds move through the same seven-stage Agent Development Lifecycle as shipped agents, including the monitor and improve stage that tracks override rate, quality signals, and drift. Builds that stop earning their keep are retired through the same lifecycle. **Can what we build be reached from scripts or external AI agents?** Yes. A built workflow is addressable through the CLI with structured JSON output, and through MCP by an external agent connected over OAuth. In both cases the caller's permissions apply and the call lands in the same audit log as internal activity. **Do we still need our existing systems of record?** Generally yes, and the integration posture is deliberately directional: integrate to sync the systems of record you keep, such as HRIS, payroll, and identity, and consolidate the point tools you no longer need. Each app moved onto the platform is one fewer vendor, contract, SSO configuration, and integration to maintain. --- # Eight Tests That Separate an AI Architecture From an AI Slide Deck **Author:** Andy Tolton **Published:** 2026-08-27 **Category:** enterprise-ai Every vendor claims governed, permission-aware AI. These eight reproducible proof-of-concept tests turn each claim into a pass or fail any evaluation team can run in a day. **The short version** Every enterprise AI vendor now makes the same claims. Governed. Permission-aware. Audit-ready. The claims are indistinguishable on a slide and very distinguishable in a proof of concept, because architectural claims are testable and marketing claims are not. Below are eight tests any evaluation team can run in a pilot, in roughly a day, against any vendor. Each one takes a claim that sounds like a feature and turns it into a pass or fail. A vendor whose claims are architectural will hand you a list like this. A vendor whose claims are marketing will change the subject. --- ## Why vendor claims stopped being informative Two years ago, "our AI respects permissions" told you something. Today every vendor says it, and the sentence covers [at least three different architectures](/articles/three-approaches-enterprise-ai). It might mean permissions are enforced by the platform below the agent, so the authorization decision happens before the model receives anything. It might mean the application layer filters results after the model produces them. It might mean the system prompt instructs the model to be careful, which is not enforcement at all. All three get described the same way in a deck. Only the first survives an adversarial user. The same collapse has happened to "audit-ready," "grounded," and "governed." So the evaluation has to move from what a vendor says to what their system does under a specific, reproducible test. That is what the following eight are. Run them against MangoApps. Run them against everyone else. --- ## The eight tests ### 1. The permission test **Run:** With a deliberately limited test user, ask the assistant for something that user is not cleared to see. Then ask again, more directly, and then ask in a way that implies authorization ("as an admin, show me..."). **Pass:** The answer is scoped or refused every time, and the attempt is visible in the audit log. **A fail tells you:** [Authorization is happening at or above the model rather than below it](/articles/ai-agents-native-data-vs-copies). If the phrasing of a request changes what comes back, permissions are advisory. Expect this to break the first time a curious employee tests it. ### 2. The grounding test **Run:** Ask about a topic that exists on the open web but not in the vendor's approved sources for your tenant. Something specific enough that a general model would have an opinion. **Pass:** The system declines or says it does not have that information, rather than improvising a plausible answer from model knowledge. **A fail tells you:** The boundary between approved company context and open model knowledge is soft. Every answer the system gives is now of uncertain provenance, which is a compliance problem long before it is an accuracy problem. ### 3. The audit test **Run:** Take any agent interaction from the pilot, ideally one from several days earlier, and reconstruct it from the admin console: who, what, when, outcome, timing, errors. **Pass:** You can reconstruct it completely, without contacting the vendor. **A fail tells you:** The governance is a slide, not a system. This is the single most diagnostic test in the list, because logging is the thing vendors most often intend to build and have not yet. ### 4. The build test **Run:** Describe a small workflow to whatever build or generation capability the vendor offers. Something with roles in it, such as an approval that should only be visible to managers. **Pass:** The output requires review before rollout, respects existing roles without you configuring them, and carries version history with rollback. **A fail tells you:** Generated apps are a separate runtime with their own permission logic, which means every one your teams build becomes a new governance object. See [Citizen Development Without the Sprawl](/articles/governed-citizen-development) for what this looks like when it goes wrong. ### 5. The external-agent test **Run:** Connect an MCP-compatible agent, or whatever external connection the vendor supports, through OAuth. **Pass:** Consent is requested per scope, the agent acts as the connecting user rather than as a service account, and its calls land in the same audit log as internal activity. **A fail tells you:** External access is a service account with a fixed permission set, unrelated to whoever is actually using it, logged separately or not at all. More on this in [Connecting Claude, ChatGPT, and MCP Agents to Workforce Data](/articles/mcp-enterprise-workforce-agents). ### 6. The policy test **Run:** Declare an org-wide agent access policy, such as requiring approval for a class of writes. Then trigger that class of write from an internal agent and from an external one. **Pass:** Both obey it identically. **A fail tells you:** Policy is implemented per surface rather than centrally, so every new surface is a new place the policy has to be re-implemented and can be forgotten. ### 7. The kill-switch test **Run:** Pause a single agent. Verify it stops responding everywhere while every other AI surface keeps working. Then check that the other three levels exist: per app, per business unit, and platform-wide. **Pass:** All four levels exist and take effect immediately. **A fail tells you:** Your only options in an incident are to do nothing or to turn off all AI for everyone. That is not a control, it is a breaker. The nested design behind this is covered in [Governing AI by Design](/articles/governing-ai-by-design). ### 8. The escalation test **Run:** Attempt a high-impact action through an agent. A compensation change, a bulk administrative operation, or an all-employee broadcast. **Pass:** It stops for explicit human approval rather than executing. **A fail tells you:** Autonomy has no floor. The vendor is relying on you to configure restraint rather than shipping it, and the default state of the system is the dangerous one. --- ## The other half of the evaluation: ask what it will not do The eight tests above check whether claimed capabilities hold. There is a second question that is at least as revealing and almost never asked: **what will this platform refuse to do, by design?** A vendor who can answer immediately has designed their limits. A vendor who cannot has not found them yet, which means you will find them together, in production. Concrete limits worth asking any vendor to state: - Can an agent ever exceed the permissions of the user who invoked it? (The answer should be no, with no privileged agent path.) - Are agents that answer questions architecturally separate from agents that take administrative action, so everyday help cannot escalate into privileged operation? - Is write traffic from an external application rate-limited per application per tenant, so a misbehaving agent is contained by architecture rather than by hope? - Are new agents off by default, enabled deliberately by license, role, and region, so a new capability arriving on the platform is not a new capability arriving in your tenant? - Do outputs or cached results ever cross the customer boundary, and does customer data ever train public models? Constraints you can locate are the difference between a platform you govern and a platform you trust on faith. ## How to run this in a pilot The whole list is a day of work for one technical evaluator plus one admin, and it is worth scheduling explicitly rather than hoping it happens during a general pilot. Two practical notes. First, run the permission test with a real limited user, not an admin account with a role temporarily removed, because the two resolve differently in most systems. Second, run the audit test last, several days after the others, so you are reconstructing history rather than watching it get written. Score it plainly. Eight tests, pass or fail, no partial credit, and a written note on what each fail implies. That document will be more useful in the final vendor conversation than any RFP response you receive. --- **Go deeper:** The architecture behind each of these eight tests, including the governed-call pipeline and the designed limits, is documented in the tech leader edition of the platform book from MangoApps, the AI-Ready Employee Platform for the Frontline. Download it from the resource library, then run the list against us. --- ## Frequently asked questions **How should we evaluate an enterprise AI vendor?** Convert every claim into a test. Vendor claims about governance, permissions, grounding, and auditability now sound identical across the market, so the differentiator is whether a claim holds under a specific reproducible action. The eight tests above cover permissions, grounding, audit, build, external agents, policy, kill switch, and escalation, and can be run in about a day. **What should an AI proof of concept include?** At minimum: a limited test user for permission testing, admin access to the audit log, one external agent connection, one generated workflow, and one attempted high-impact action. A POC that only checks answer quality tells you about the model, not the platform, and the model is the part you can change later. **How do I test whether an AI system enforces permissions?** Ask a limited test user's assistant for data that user cannot access, then repeat the request with phrasing that implies authorization. If the output changes based on how you ask, permissions are being applied at or above the model rather than enforced below it. Confirm the attempt appears in the audit log. **What is a kill switch in enterprise AI, and how many levels should it have?** A kill switch pauses AI activity without a deployment change. A single global switch is insufficient, because it forces a choice between doing nothing and disabling AI for everyone. Look for nested levels: per agent, per app, per business unit, and platform-wide. **What does "grounded" actually mean, and how do I verify it?** Grounded means answers are drawn from approved company sources rather than from general model knowledge or the open web. Verify it by asking about something that exists publicly but not in your approved sources. A grounded system declines. An ungrounded one produces a confident answer with no traceable provenance. **Why does it matter whether an external agent uses OAuth or an API key?** An API key is a service account with a fixed permission set unrelated to whoever is using it, and its log entries are attributed to the key rather than to a person. OAuth-bound access resolves to a named user on every call, so permissions and attribution follow the human. In an incident, the difference determines whether you can answer the question "who did this." **What should a vendor be able to tell us about their limits?** Whether an agent can exceed its caller's permissions, whether help agents and admin agents are architecturally separate, whether external writes are rate-limited, whether agents are off by default, and whether customer data ever crosses the tenant boundary or trains public models. Immediate, specific answers indicate designed constraints. Vague answers indicate undiscovered ones. **How long should this evaluation take?** About a day of combined technical and admin time, with the audit test deferred by several days so you are reconstructing past activity rather than observing live logging. Scheduling it explicitly matters, because these tests rarely happen on their own inside a general pilot focused on answer quality. **Is this list specific to MangoApps?** No. Every test is vendor-neutral and can be run against any enterprise AI platform, including ours. That is the point of publishing it. The architecture behind how MangoApps passes each one is documented in the tech leader edition of the platform book. --- # Connecting Claude, ChatGPT, and MCP Agents to Workforce Data Without Losing Governance **Author:** Andy Tolton **Published:** 2026-08-27 **Category:** enterprise-ai Saying no to external AI agents isn't a strategy. The workable yes binds every agent to a named user, enforces permissions below the model, and lands every call in one audit trail. **The short version** Someone on your team wants to point an external AI agent at company data. Saying no is not a strategy, because the request will keep coming and unsanctioned tools already fill the gap. The workable answer is to define what "yes" has to include: the agent is bound to a named human, permissions are resolved below the agent rather than inside the prompt, context comes from approved records, and every call lands in the same audit log as internal activity. On a fragmented stack none of those four are available in one place, which is why most enterprises end up choosing between an agent with too much access and an agent too limited to be useful. On a single employee platform, all four are properties of the foundation, so an external agent connected over the Model Context Protocol inherits governance instead of bypassing it. --- ## The question every technology leader is now getting asked The request arrives in some version of this form: can we connect Claude to our HR data, or point ChatGPT at our SOPs, or let an agent read the schedule. The reflex is to say no, and the reflex is understandable. It is also not durable. Employees are already using tools nobody approved. Varonis found in 2025 that 98% of employees use unsanctioned applications, and IBM reported the same year that shadow AI played a role in roughly one in five breaches, adding about $670,000 to the cost of each. The exposure is not waiting on your decision. It is already inside the building. So the useful question is not whether to allow external agents. It is what the connection has to guarantee before the answer can be yes. ## Four things a governed connection has to provide Write them down before you evaluate anything, because they are the requirements every serious answer has to satisfy: 1. **Identity.** The agent acts as a specific person, not as a service account with a superset of everyone's access. 2. **Permission enforcement below the agent.** Not a system prompt that instructs the model to be careful. An authorization decision made by the platform before data is returned. 3. **Grounded context.** Answers come from approved company sources with a defined boundary, not from the open web and not from a stale export. 4. **One audit trail.** External activity is reconstructable in the same place as internal activity, or it is invisible. ## Why a fragmented stack cannot provide them Each requirement above assumes something shared, and a stack of point tools shares almost nothing. There is no single identity, so the agent is either provisioned per tool or given a service account that sees more than any individual should. There is no common permission model, so authorization is decided differently in each system and the agent inherits whichever interpretation it happens to hit first. There is no common employee record, so the agent reasons over [copies of data that aged the moment they were exported](/articles/ai-agents-native-data-vs-copies). And there is no single place to audit, so reconstructing what an agent did means correlating logs across six vendors, if those logs exist at all. This is the same fragmentation that [makes any AI deployment unsafe to act on](/articles/why-fragmented-tools-break-enterprise-ai), showing up in its sharpest form. An internal assistant on a fragmented stack is limited. An external agent on a fragmented stack is a governance hole with an API. ## The three connection surfaces On the MangoApps platform, external intelligence connects through three surfaces, and all three resolve against the same foundation. **Standards-based MCP.** The Model Context Protocol is an open standard for connecting AI agents to tools and data. MangoApps exposes 900+ scoped, permission-aware tools across the workforce domain, so an MCP-compatible agent, Claude, Cursor, Codex, or another, can read and act inside defined boundaries. More than 40 agent platforms are supported. The tools are scoped, which is the part that matters: an agent gets a specific capability, not a general connection to the database. **Vendor assistants on your own tenant.** MangoApps for Claude, ChatGPT, and Gemini runs against your tenant with the same OAuth flow, the same audit log, and the same governance as everything else. The assistant changes. The rules do not. **Bring your own model.** Run on OpenAI, Anthropic, or Gemini with automatic fallback, or on an approved private model. Model calls route through governed connections under enterprise agreements, and customer data never trains public models. That exclusion is contractual and architectural, not a setting. ## The anatomy of a governed call Every claim about governed AI reduces to what happens on a single request. Here is the path, and it is identical whether the caller is an employee in the app, a script, or an external agent connected over MCP. | Stage | What happens | Why it matters | |---|---|---| | 1. Identity | The call is bound to a person. External agents use OAuth 2.1 user tokens. There is no anonymous path. | An agent has an owner. Every action is attributable. | | 2. Permission resolution | Enforced below the agent, against roles and org structure, scoped per domain. | The model cannot talk its way past authorization, because authorization happens before the model sees anything. | | 3. Context | Grounded in approved company records and live data. Never the open web. | Answers reflect current state, not a cached copy or a plausible guess. | | 4. Model routing | Model selected on quality and cost, with automatic failover. | Provider availability is an operational concern, not an outage. | | 5. Action and audit | Writes require confirmation. Full request, outcome, timing, and errors logged in MangoApps Console. | The interaction can be reconstructed months later by someone who was not there. | One rule falls out of stage two and is worth stating on its own, because it is the single most important property of the whole design: **no agent, internal or external, operates above the permissions of the user invoking it.** There is no privileged agent path. ## The edges are deliberate A technical evaluation should also ask what a platform will not do. Constraints you can locate are the difference between a platform you govern and a platform you trust on faith. - **External writes are throttled.** Write traffic from an external application is rate-limited per application per tenant, so a misbehaving agent is contained by architecture rather than by hope. - **Help and administration are separated.** Agents that answer questions are architecturally distinct from agents that take administrative action, so everyday help cannot escalate into privileged operation. - **High-impact decisions require a human.** Compensation changes, hiring and offer decisions, bulk administrative operations, and all-employee broadcasts stop for explicit approval. - **Nothing is on by default.** Every agent is opt-in, enabled by administrators by license, role, and region. A new capability arriving on the platform is not a new capability arriving in your tenant. - **No cross-customer context, ever.** Outputs and cached results stay inside the customer boundary. Depth on the autonomy dial, the nested kill switch, and the data boundaries behind these limits is in [Governing AI by Design](/articles/governing-ai-by-design). ## Provider choice is a setting, not a re-platform The strategic argument for connecting agents this way is that it decouples two decisions that most enterprises are currently making as one. Model capability is moving faster than any procurement cycle. If governance lives inside the model vendor's product, every change of model is a change of governance, and the migration cost quietly locks you in. If governance lives in the platform underneath, the model is a configuration choice. Standardize on whatever your organization prefers. Change it next year. The identity, the permission model, and the audit trail do not move. That is what makes this an architecture decision rather than a tooling decision, and it is why [the platform decision now comes before the app decision](/articles/platform-decision-first). --- **Go deeper:** The full external-agent architecture, including the governed-call path, the containment limits, and a proof-of-concept test you can run against any vendor, is in *The AI-Ready Employee Platform, Tech Leader Edition*. Download it from the resource library. --- ## Frequently asked questions **What is the Model Context Protocol (MCP)?** MCP is an open standard for connecting AI agents to external tools and data sources. Instead of building a custom integration for every agent and every system, a platform exposes a set of scoped tools that any MCP-compatible agent can call. MangoApps exposes 900+ permission-aware tools across the workforce domain and supports more than 40 agent platforms. **Can an external AI agent see data the user cannot?** No. Permissions are enforced by the platform below the agent, not inside the prompt. An agent connected over MCP acts as the user who authorized it through OAuth 2.1, and it cannot return or act on data that user is not cleared to see, even when asked directly. There is no privileged agent path that bypasses this. **What happens to our data when it is sent to a model provider?** Model calls route through governed connections under enterprise agreements, and customer data never trains public models. The exclusion is both contractual and architectural. Outputs and cached results stay inside the customer boundary, with no cross-customer sharing. **Does connecting an external agent create a second audit trail?** No. External agent calls land in the same audit log as internal activity, visible in MangoApps Console with the request, outcome, timing, and any errors. If a vendor cannot show you an external agent's activity in the same place as internal activity, the two systems are governed separately, which means they are governed inconsistently. **Can we use our own private model instead of a commercial provider?** Yes. The platform supports OpenAI, Anthropic, and Gemini with automatic fallback, or an approved private model. Provider choice is a configuration setting rather than a re-platform, because governance sits in the platform rather than in the model vendor's product. **What stops an external agent from writing bad data at scale?** Three limits. Write traffic from an external application is rate-limited per application per tenant. Writes require confirmation. And high-impact actions, including compensation changes, hiring decisions, bulk operations, and all-employee broadcasts, require explicit human approval regardless of how they were initiated. **How is this different from giving an agent an API key?** An API key is a service account. It carries a fixed set of permissions unrelated to whoever is using it, it produces log entries attributed to the key rather than to a person, and it typically has more access than any single employee would. OAuth-bound agent access resolves to a named user on every call, so permissions and attribution follow the human. **How do we verify these claims in a proof of concept?** Connect an MCP-compatible agent through OAuth and check three things: consent is requested per scope, the agent acts as the connecting user rather than as a service account, and its calls appear in the same audit log as internal activity. Then declare an org-wide policy, such as requiring approval for a class of writes, and verify the external agent obeys it exactly as an internal agent does. A fuller test plan is in [Eight Tests That Separate an AI Architecture From an AI Slide Deck](/articles/ai-vendor-proof-of-concept-tests). **Do employees need corporate email or a laptop to use AI features?** No. MangoApps has been built for the frontline for 18+ years, and identity was designed for the 80% of the workforce without corporate email. Desk and frontline employees resolve to the same identity system, the same org structure, and the same permission model, on the phone employees already carry. --- # Same Platform, Same Governance: Deployment and Compliance Architecture for Regulated Buyers **Author:** Andy Tolton **Published:** 2026-08-27 **Category:** enterprise-ai Private deployment means little if the AI arrives with different controls. How to verify that governance, certifications, and the audit trail carry across all four deployment models. **The short version** In healthcare, financial services, and government, the deployment question gets asked first and answered once. Most platforms in the employee software category offer one deployment model, so the question doubles as a disqualifier. MangoApps offers four: SaaS, private cloud, customer VPC, and on-premise. The claim worth examining is not the count. It is that the same platform, the same apps, and the same AI governance model run in all four, with compliance posture carried across rather than reduced. That matters because the common failure mode in regulated environments is not a platform that cannot be deployed privately. It is a platform whose AI capabilities quietly do not come with it. --- ## The question that ends most evaluations early Regulated buyers learn to lead with deployment because it saves everyone time. If the answer is multi-tenant SaaS only, and the requirement is a customer-controlled environment, the rest of the evaluation is academic. What has changed recently is that the deployment question now has a second half attached to it, and many vendors have not caught up: **does the AI come with it, and is it governed the same way?** A vendor can honestly say they support private deployment while their AI capabilities run through a shared service, or arrive later, or arrive with different controls. That is the gap worth probing, because it converts a compliance win into a compliance exception. ## Four deployment options | Option | What it means | Typically chosen by | |---|---|---| | SaaS | Multi-tenant, vendor-operated | Most enterprises without a data residency or control mandate | | Private cloud | Single-tenant, vendor-operated | Organizations needing isolation without operational burden | | Customer VPC | Runs inside your own cloud account | Organizations with existing cloud governance and a control requirement | | On-premise | Runs in your data center | Government, defense, and organizations with air-gap or residency mandates | The same platform, the same apps, and the same AI governance model run in all four. Compliance posture carries across without a reduced feature set in the private options. That last sentence is the one to test rather than accept. In a proof of concept, run the same governance checks in the target deployment model that you would run in SaaS: audit reconstruction, permission enforcement with a limited user, and the nested kill switch. If any of them behave differently, you are looking at two products with one name. The full test list is in [Eight Tests That Separate an AI Architecture From an AI Slide Deck](/articles/ai-vendor-proof-of-concept-tests). ## The certification stack | Framework | Status | |---|---| | HITRUST CSF | Certified | | SOC 2 Type II | Audited | | ISO 27001 | Certified | | FedRAMP | ATO | | HIPAA | Ready | | GDPR | Validated | Supporting posture: 99.9% uptime SLA, granular role-based access control, and audit-ready records across the platform. Two notes on how to read a list like this, from any vendor. First, check what the certification covers. A certification that covers the core product but excludes newer AI services is common and is usually disclosed only if asked. Second, check the date and the scope statement rather than the logo. Certifications lapse, and scope changes between audit cycles. ## AI governance is not a second program The most expensive assumption a regulated buyer can make is that AI governance will be a separate workstream to stand up after the platform goes live. On [a fragmented stack](/articles/why-fragmented-tools-break-enterprise-ai), it has to be, because there is no single place where AI activity can be observed or controlled. On a single platform, the AI governance is the governance that already exists: - **Data privacy.** Customer data never trains public models. The exclusion is contractual and architectural, and model calls route through governed connections under enterprise agreements. - **Audit visibility.** Every agent action is audit-ready in MangoApps Console, in the same log as everything else on the platform. - **Automated protection.** PII detection runs automatically across interactions, with findings surfaced to administrators. - **Granular control.** Autonomy is set per business unit and per agent, so a control that is right for one part of the organization does not have to be right for all of it. - **Multi-level pause.** AI can be paused per agent, per app, per business unit, or platform-wide. - **Permission enforcement below the agent.** An agent cannot return data the requesting user is not authorized to see, even when asked directly, because authorization happens before the agent receives anything. - **Human approval on high-impact actions.** Compensation changes, hiring and offer decisions, bulk administrative operations, and all-employee broadcasts require explicit approval. The mechanics behind the autonomy dial and the nested pause are covered in [Governing AI by Design](/articles/governing-ai-by-design). ## The consolidation a security architect actually wants The usual pitch for consolidation is fewer logins. That is a user experience argument, and it is not the one that matters to the person who has to defend the environment. The consolidation that matters is **fewer permission models to reconcile, and fewer places where an authorization decision can be made inconsistently.** Consider what a typical employee stack looks like from a security review: an HRIS, a separate HCM, a workforce management tool, an LMS, a performance system, an applicant tracking system, a comms app, and a help desk. Eight vendors, eight data layers, eight interpretations of what a "manager" is allowed to see. Every integration between them is a copy of employee data with no permission context attached, a point developed further in [Your AI Agent Is Reading a Copy of Your Business](/articles/ai-agents-native-data-vs-copies). Now add AI on top. Each of those systems adds its own assistant, or one assistant reaches across all of them through integrations that flatten permissions. Either way, the number of places an authorization decision gets made goes up, and the number of places it can be made incorrectly goes up with it. Running the same workflows on one platform produces three outcomes a security architect can put in a memo: - **Fewer attack surfaces.** Each app moved onto the platform is one fewer vendor, contract, SSO configuration, and integration to maintain. - **One place to audit.** Internal activity, external agent activity, and generated workflows all land in the same log. - **One governance model.** One org structure, enforced once, respected by every app, every agent, every integration, and everything your teams build. The integration posture stays deliberately two-sided: integrate to sync the systems of record you keep, consolidate the point tools you no longer need. Your HRIS remains your HRIS. The eight-vendor middle layer is what goes away. ## What to ask before the security review Four questions that resolve most of the uncertainty early: 1. Does every deployment option run the same AI capabilities, or is AI limited in private and on-premise deployments? 2. Is AI governance implemented in the same control plane as platform governance, or is it a separate console with separate policies? 3. Does the certification scope cover AI services, or only the core product? 4. Can an agent's activity be reconstructed from the audit log by your own team, without vendor assistance? The vendors worth continuing with will answer all four in the first call. --- **Go deeper:** Deployment architecture, the full certification posture, and the AI governance stack are documented in *The AI-Ready Employee Platform, Tech Leader Edition*. Download it from the resource library. --- ## Frequently asked questions **Can MangoApps be deployed on-premise?** Yes. MangoApps supports four deployment options: SaaS, private cloud, customer VPC, and on-premise. The same platform, the same apps, and the same AI governance model run in all four, with compliance posture carried across. **Does AI governance change in a private cloud or on-premise deployment?** No. The AI governance model is the platform's governance model, so it deploys with the platform rather than as a separate service. Data privacy, audit visibility in MangoApps Console, PII detection, per-agent autonomy control, and the multi-level pause are present in all four deployment options. **What compliance certifications does MangoApps hold?** HITRUST CSF certification, SOC 2 Type II audit, ISO 27001 certification, FedRAMP ATO, HIPAA-ready posture, and GDPR validation, supported by a 99.9% uptime SLA, granular role-based access control, and audit-ready records. **Where is customer data stored?** It depends on the deployment model. In customer VPC and on-premise deployments, data resides in infrastructure you control. In SaaS and private cloud, it resides in the vendor-operated environment for your tenant. In all four, outputs and cached results stay inside the customer boundary, with no cross-customer sharing. **Does customer data leave the tenant when an AI agent runs?** Model calls route through governed connections under enterprise agreements, and customer data never trains public models. The exclusion is contractual and architectural. Organizations that require it can run on an approved private model instead of a commercial provider. **Is AI enabled by default?** No. Every agent is opt-in, enabled deliberately by administrators by license, role, and region. A new capability arriving on the platform is not a new capability arriving in your tenant, which matters in regulated environments where change control governs what employees can access. **How is AI activity audited?** Every agent action is logged in MangoApps Console with the request, outcome, timing, and any errors, in the same audit trail as internal platform activity and external agent activity. The practical test is whether your own team can reconstruct a specific interaction from several days earlier without contacting the vendor. **What happens if we need to stop AI activity immediately?** AI can be paused at four levels: per agent, per app, per business unit, or platform-wide. A single agent can be stopped everywhere while every other AI surface continues operating, so an incident does not require disabling AI for the whole organization. **Do frontline employees without corporate email create a compliance gap?** No. Employees onboarded on a personal phone with no email address resolve to the same identity system, org structure, and permission model as employees provisioned through your identity provider with SSO. There is no second, weaker identity path, which is a common source of access-review findings in organizations that [bolted on a separate frontline tool](/articles/frontline-ai-blind-spot). --- # From issues closed to AI scheduling: what's new this week **Author:** MangoApps Team **Published:** 2026-08-25 **Category:** mango-scoop Explore the Accountability Loop, 10 things to know about AI shift scheduling, and updates to Company Profile Brand Research. Hand-picked stories from MangoApps this week. ## The Accountability Loop: From Issue Raised to Issue Closed ![The Accountability Loop: From Issue Raised to Issue Closed](https://mango-cdn.b-cdn.net/images/blog-thumbnails/blog_627_20260816_140403.png) The manager's weekly walkthrough ended the way most of them do — fifteen minutes of conversation, a few things flagged, a general sense that the team is doing fine. Three real issues surfaced. [Read the full story →](https://www.mangoapps.com/articles/the-accountability-loop-from-issue-raised-to-issue-closed) --- ### More to read #### 10 Things to Know About AI Shift Scheduling What enterprise HR and operations leaders should know before buying AI workforce management software: what AI-driven shift scheduling actually does, what enterprise requirements matter, and why frontline adoption decides the outcome. [Read more →](https://www.mangoapps.com/articles/ai-shift-scheduling-what-to-know) #### MangoApps Wins Silver Stevie® Award in 2026 International Business Awards® MangoApps, the employee platform for the frontline, has been named the winner of a Silver Stevie® Award in the Best AI-Powered Product or Service category in The 23rd Annual International Business Awards® (IBAs). [Read more →](https://www.mangoapps.com/articles/best-ai-powered-product-or-service-2026) --- ### What's New **General** — [Product Update - August 16, 2026](https://www.mangoapps.com/changelog/3115) * **[Company Profile Brand Research](https://www.mangoapps.com/administration)** — Admins can now enter a company website and have the platform automatically extract logo, brand... **General** — [Product Update - August 15, 2026](https://www.mangoapps.com/changelog/3114) * **[Recognition Approvals & Nominations API](https://www.mangoapps.com/directory/app/recognition)** — Reviewers and integration partners can now approve, reject, and bulk-revie... --- # When "We Did That" Isn't Enough: HR Accountability at Scale **Author:** MangoApps Team **Published:** 2026-08-23 **Category:** compliance-risk Picture the moment an HR leader dreads. An employment attorney's email arrives, asking for documentation of a specific job description acknowledgment — not the current one, but the version from... # When "We Did That" Isn't Enough: HR Accountability at Scale Picture the moment an HR leader dreads. An employment attorney's email arrives, asking for documentation of a specific job description acknowledgment — not the current one, but the version from eighteen months ago, before the role was restructured. The HR team knows they sent it. They know the employee reviewed it. But the proof is a PDF in a shared drive, an email chain that was archived two laptops ago, and a verbal confirmation that no one ever logged. "We did that" is not evidence. The same scene plays out in legal, where a counterparty disputes whether they ever formally agreed to a contract amendment. In benefits, when a COBRA participant claims no one notified them of their continuation rights. In recruiting, when a rejected candidate demands to know when, exactly, the decision was communicated. In finance, when an auditor asks which card charges match the pre-approval submitted in March. In each case, the operations were sound. The records were not. That gap — between work completed and work provable — is where audits fail and disputes become expensive. Much of what shipped in MangoApps this week is aimed directly at it. --- ## The Acknowledgment Problem One of the quieter compliance risks in HR is not whether employees have signed their job descriptions. It is whether those signatures reflect the current version of the role, and whether you can surface that record on demand. Roles evolve. Responsibilities shift. An acknowledgment from two years ago may no longer match what the employee actually does — which creates exposure in performance disputes, misclassification claims, and role-based compensation challenges. [Job Description Re-acknowledgment Campaigns](https://www.mangoapps.com/changelog/3121) gives HR admins the ability to run periodic re-signing campaigns for any group of current job holders, with configurable cadence and per-campaign progress tracking. The mechanism matters here as much as the concept. Smart deduplication ensures no one is asked to sign something they have already acknowledged in the current cycle. The output is a timestamped acknowledgment record for each employee — not an email thread, not a shared drive file, not a "trust me, we did this" assertion. The signing problem extends past job descriptions. Contracts — vendor agreements, service orders, amendments — frequently exist in a state where both parties verbally agree but the formal in-system record sits at "pending." When a counterparty later disputes whether they agreed to revised terms, that pending status creates a problem that should not exist. [Contracts E-Signature](https://www.mangoapps.com/changelog/3120), released earlier this week, moves the signature moment into the contract itself, with a clear status banner and a signer roster showing exactly who has signed and who has not. The record becomes unambiguous, and it lives in the system that owns the contract. In benefits, [COBRA Notification Controls](https://www.mangoapps.com/changelog/3114) allow benefits admins to enable or disable individual automated participant notices independently of any other benefits communication. This is described as a configuration feature. It is, more precisely, a compliance control: the ability to document exactly which notices went to which participants, on which dates, without relying on bulk sends that are difficult to audit after the fact — or to defend in a dispute months later. --- ## The Timeline Problem Knowing something happened is not the same as knowing when it happened, who initiated it, and what preceded it. In recruiting, this distinction matters. EEOC record-keeping requirements specify that certain hiring decision records must be retained for defined periods, and the rejection letter is only part of the record. The other part is when it was sent, by whom, and in what sequence — details that have historically lived only in email, if they were captured at all. [Job Board Candidate Timeline](https://www.mangoapps.com/changelog/3120) now includes rejection letters in the candidate history automatically, recording the timestamp and the sender at the moment the communication goes out. It is a small change in interface terms. In compliance terms, it is the difference between a defensible record and an assertion. The same logic applies to the timestamps on form data. Time and datetime fields on submitted forms have historically displayed in a single time zone — often the platform default or the reviewer's local time — which introduces ambiguity when respondents are in different regions. This matters more than it sounds. An incident report submitted at 2:00 AM carries different implications than one submitted at 2:00 PM in a different time zone, especially in safety investigations and labor disputes where sequence and timing are substantive. [Form Submission Time Zones](https://www.mangoapps.com/changelog/3116) now labels every time answer with the respondent's local zone, explicitly. The record reflects whose clock it reflects. For performance management, the audit question is more direct: do you have the review on file, and can you produce it quickly? [Bulk PDF Export for Performance Reviews](https://www.mangoapps.com/changelog/3116) allows managers and HR admins to select multiple reviews and export the full set as a ZIP of PDFs in one step, downloaded directly without an email attachment. For organizations that field requests for review records from employment attorneys, compliance auditors, or internal investigations, this reduces what was often a multi-step, multi-system process to one action. Whether the request arrives with a week's notice or an afternoon's, the record is accessible. --- ## The Spend Accountability Thread Financial accountability in workforce operations has its own version of the proof gap. A pre-approval documents what was authorized. A reimbursement request documents what was paid out of pocket. A company card receipt documents what hit the corporate account. Until those three threads are woven together against the same approval, reconciliation requires manual comparison across separate views — and the audit trail has gaps wherever the comparison was not documented. [Mango Spend: Card Receipt Actuals](https://www.mangoapps.com/changelog/3119), shipped this week, allows card receipts to be linked directly to the pre-approval they were drawn against. That means the full spend picture for any approval — what was authorized, what was reimbursed, and what was charged to the card — lives in one place, tied to a single record. The companion update to the [Mango Spend Dashboard](https://www.mangoapps.com/changelog/3120) surfaces all four spend types (reimbursements, pre-approvals, card receipts, and vendor bills) in a single activity view, rather than requiring navigation between separate summaries. For finance teams, this is a reconciliation improvement. For audit purposes, it is something more specific: a chain of custody from the moment a spend was approved to the moment it was settled, with every transaction in the middle accounted for and linked. When a finance audit asks "show us all spend that touched this pre-approval," the answer is now a single record rather than a cross-referenced export. --- ## What This Adds Up To The features described above span job descriptions, contracts, benefits, recruiting, form data, performance reviews, and expense management. On the surface, they look like incremental improvements to six different applications. Under the surface, they are all working on the same problem: the distance between operations that function correctly and operations that can be shown, on demand, to have functioned correctly. For HR and operations leaders in regulated industries — healthcare, manufacturing, logistics, retail — this distinction is not abstract. It is the difference between an audit that closes cleanly and one that exposes a process your team thought was documented. It is the difference between a dispute you win because the record is clear and one that settles because the record does not exist. Operational credibility, in the end, is not only about doing the right things. It is about being able to show that you did, to whomever is asking, with whatever level of specificity the moment requires. The organizations that handle audits, disputes, and regulatory reviews without disruption are not necessarily the ones with the most sophisticated policies — they are the ones whose daily operations leave a clear, accurate trail. That is what this week's releases are building toward, one gap at a time. --- # The Accountability Loop: From Issue Raised to Issue Closed **Author:** MangoApps Team **Published:** 2026-08-16 **Category:** operational-efficiency The manager's weekly walkthrough ended the way most of them do — fifteen minutes of conversation, a few things flagged, a general sense that the team is doing fine. Three real issues surfaced. # The Accountability Loop: From Issue Raised to Issue Closed The manager's weekly walkthrough ended the way most of them do — fifteen minutes of conversation, a few things flagged, a general sense that the team is doing fine. Three real issues surfaced. One got resolved before the end of the day. The other two drifted somewhere between a verbal acknowledgment and a memory that fades by Friday. This is not a failure of the manager. It is a design failure. When the only artifact of a structured conversation is a mental note or a line in a pocket notebook, there is no mechanism to pull an open item back to the surface next week. No automatic escalation if the same issue comes up again in two other locations. No visibility for anyone above that manager about what was raised and what was still open. Organizations have gotten very good at recording things. Inspection visits get logged. Check-ins get noted. Break violations surface in reports. But recording something is not the same as resolving it — and most workforce software does not close that loop. --- ## The Manager Who Has No Loop to Close [Leader Rounds](https://www.mangoapps.com/changelog/3112), released this week, is built around a simple and underserved premise: a raised issue is not a done issue. It is a structured check-in tool, but the design is oriented entirely toward resolution rather than documentation. Managers conduct rounds using customizable templates — starting from industry-specific packs rather than a blank form, so the conversation has shape before the first question is asked. Every item that surfaces gets color-coded into a stoplight ledger: green, yellow, or red. That ledger does not reset after the meeting. It carries open items forward until they are explicitly closed. Two things make this more than a digital notepad. First, the coverage view: leadership can see not only what was discussed in rounds that happened, but which locations had no rounds at all that week. Most compliance tools tell you what was found. This one tells you what was missed entirely. Second, the issue tracking rolls up the reporting hierarchy, so a regional manager can see open items across all their sites without chasing individual reports. The mobile voice capture is a detail worth noting. Frontline rounds often happen while walking a floor, not sitting at a desk. Voice capture means issues get logged in the moment rather than reconstructed from memory at the end of a shift. The difference in data quality between those two approaches is significant, even if it is hard to quantify. --- ## Compliance That Enforces, Not Just Reports The same gap — between logging something and preventing it — shows up in a different part of workforce operations: break compliance. Most organizations with statutory break requirements have a compliance report. It tells them, after the fact, whether breaks were taken and whether the right duration was observed. Some organizations use these reports for corrective action. Almost none of them use a scheduling system that prevents the violation from being created in the first place. [Break Compliance Enforcement](https://www.mangoapps.com/changelog/3110) moves the intervention point. Requirements are now applied at scheduling time and at the clock-in/clock-out moment. If publishing a schedule would create a break violation under applicable law, the system flags it before that schedule goes live. If an employee clocks back in before a statutory minimum has elapsed, an attestation flow is triggered rather than a silent log entry being written. The [Break Compliance report](https://www.mangoapps.com/changelog/3110) still exists — but it now documents exceptions rather than serving as the first alert. This is the same logic applied to [regulatory visit tracking](https://www.mangoapps.com/changelog/3110). The redesigned Visit Log adds a cross-site Deficiencies view that surfaces open correction plans — with their due dates — at the top of the dashboard. A finding raised during a site inspection now has a visible path to documented closure. It is still a log, but now the log has teeth: overdue plans of correction surface before the next inspection, not after. --- ## When AI Decisions Need Accountability Too There is a version of AI governance that consists of approving a feature once and leaving it to run. Someone reviews the initial results, nods, and moves on. The feature continues operating, implicitly approved, until something goes visibly wrong. [Loop's AI Improvement Decision Lifecycle](https://www.mangoapps.com/changelog/3109) applies the same close-the-loop logic to AI tool management. When an organization runs a measured AI change — an AI reply draft in the service desk, an automated routing rule, a scheduling suggestion — the result now requires a formal decision. Admins record whether the change should be kept, adjusted, expanded, retired, or rolled back, with a rationale attached. "Keep" decisions automatically schedule a recheck date. The change does not simply continue running on implicit approval. This matters more than it might appear. The operational distinction is between an AI feature that was approved once and an AI feature that is actively managed. As AI capabilities become embedded deeper into daily workforce operations, the difference between those two states becomes a governance question — one that audit and compliance functions are beginning to ask about. The same accountability orientation appeared in benefits administration this week. [COBRA Household Management](https://www.mangoapps.com/changelog/3112) closes a gap where HR teams had to submit the same qualifying event once per family member — correct in outcome, but repetitive in execution and prone to error with each duplicate entry. A single qualifying event now covers the entire household, with a full grid showing each person, each plan, and the cost before committing. Less work, fewer errors, same outcome. --- ## The Thread These releases do not come from the same team or the same product area. Leader Rounds is a manager enablement tool. Break Compliance Enforcement lives in time and attendance. Loop's decision lifecycle is an AI governance layer. COBRA Household Management is a benefits administration feature. What connects them is an architectural conviction that surfacing something is the beginning of accountability, not the end of it. Each of these tools moves a recorded item — an issue raised in a check-in, a break violation risk, an AI governance decision, a benefits event — from the log toward an explicit resolution state. There is also a quieter thread in this week's releases that points in the same direction: [AI that reads the context you are already in](https://www.mangoapps.com/changelog/3113), rather than requiring you to build that context from scratch. Contracts AI now reads the specific agreement you have open and answers questions about it directly. Document AI across RFP Desk, Policy Hub, and Ask AI now accepts a public URL as source material, removing the export-download-upload cycle that turns a five-second lookup into a five-minute file management task. These are not governance features, but they close a different kind of loop: the gap between where information lives and where work actually happens. For operations executives and HR leaders, the larger pattern is worth watching. The tools most organizations reach for first are the ones that capture data well. The tools that tend to matter most, over time, are the ones that do something useful with what they have captured — that bring open items back to the surface, that enforce requirements before violations occur, that require explicit decisions rather than defaulting to indefinite continuation. Closing the gap between "we track this" and "we close this" is slower, less visible work than adding a new dashboard. This week's releases suggest it is also where meaningful operational improvements tend to live. --- # 10 Things to Know About AI Shift Scheduling in Digital Workplace Platforms for Frontline Enterprises **Author:** Andy Tolton **Published:** 2026-08-14 **Category:** workforce-management What frontline enterprises should know about AI shift scheduling inside digital workplace and workforce management platforms: data, compliance, adoption, and which platforms include it. ***The short answer:** AI shift scheduling uses machine learning and rules-based logic to build, validate, and adjust employee schedules automatically, weighing availability, certifications, labor law, demand forecasts, fairness history, and labor cost at the same time. A manager who used to spend hours in a spreadsheet gets a compliant draft schedule in minutes, and the system keeps watching after publish: flagging coverage gaps, blocking ineligible assignments, and routing attendance exceptions before payroll runs.* ***The part most buyers miss:** the quality of AI-driven shift scheduling depends almost entirely on the data underneath it. An algorithm that cannot see current certifications, approved leave, actual clock-in history, and real labor cost is guessing with confidence. That is why the evaluation question is not "does this tool have AI." It is "what does the AI actually have access to, and can it act on what it sees."* --- AI shift scheduling now ships inside two kinds of products: workforce management suites, and digital workplace platforms that also run communication, tasks, and training for frontline employees. The difference decides adoption, which is why this guide treats scheduling as a platform question for frontline enterprises rather than a feature comparison. This guide covers ten things enterprise HR, operations, and internal communications leaders should understand before they shortlist [AI workforce management software](https://www.mangoapps.com/solutions/workforce-management). For the longer treatment, including the day-in-the-life comparison and the full capability walkthrough, see the [AI Scheduling for Shift-Based Teams book](https://www.mangoapps.com/resources/shifts-schedules-book). --- ## Key takeaways | # | What to know | Why it matters | | --- | --- | --- | | 1 | AI scheduling is a data problem first | Fragmented data produces confident, wrong schedules | | 2 | "AI" covers three different capability levels | Assistive, agentic, and predictive are not interchangeable | | 3 | Compliance belongs at build time, not audit time | A violation caught after publish is already a violation | | 4 | Fairness is now an auditable output | Predictive scheduling laws and union agreements require records | | 5 | Frontline adoption is the real gate | A system 40% of staff ignore produces unreliable data | | 6 | The schedule is only half the system | Hours worked, not hours assigned, is what payroll pays | | 7 | Leave and availability must write back | Approved time off that never reaches the schedule is not managed | | 8 | AI governance is a purchasing requirement | Permissions, data boundaries, and autonomy levels | | 9 | You probably do not have to replace UKG, ADP, or Workday | Integration onto a shared data layer beats rip-and-replace | | 10 | The scheduling decision is a platform decision | What you buy next either inherits this or rebuilds it | | 11 | The app the schedule lives in decides adoption | Frontline workers open the app that holds their schedule; if it also carries news, tasks, and training, all four get used | --- ## First, the cost of getting this wrong Before the ten, the stake. Scheduling is not an administrative function in a frontline operation. It is the single largest lever on retention. Among deskless workers, **53% feel burned out and 43% are actively looking for a new job**, according to [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology). Only **23% of frontline workers believe they have access to the technology they need to be productive**, according to [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html), and the schedule is the piece of technology they touch most often. Turnover is expensive in a way that rarely appears as a single line item. [Gallup](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) puts the cost of replacing an employee at **one-half to two times annual salary**, and calls that a conservative estimate. At the turnover rates common in frontline work, a 2,000-employee multi-site operator is replacing hundreds of people a year. Then there is the coordination tax. A typical frontline manager touches several disconnected systems to get through a single shift cycle, from building the schedule to handing hours to payroll. Across the enterprise, the average company now runs **101 applications, and companies with more than 5,000 employees average 131** ([Okta, Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/)). None of that is an argument for AI on its own. It is an argument for infrastructure that AI can actually run on. --- ## 1. AI shift scheduling is a data problem before it is an algorithm problem Every vendor demo shows the same moment: a manager clicks a button, and a full week of coverage appears. The demo is real. What varies wildly between products is what the algorithm knew when it built that schedule. To produce a schedule a manager can actually publish, the system needs live access to: - Current availability and submitted shift preferences - Certification and credential status, including expiration dates - Approved and pending time off, with balances - Applicable labor law, break rules, and union agreements by jurisdiction - Historical attendance and reliability patterns - Pay rates, differentials, and current period hours toward overtime thresholds - Demand signals: traffic, volume, census, seasonality If any of those live in a separate system that syncs nightly, the AI is optimizing against yesterday. That is how you get a schedule that is technically optimal and operationally wrong: the forklift-certified replacement whose certification lapsed on Tuesday, the associate whose PTO was approved in email and never reached the posted schedule, the assignment that pushes someone into overtime nobody sees until payroll runs. **What to ask:** Is this one shared data model, or separate modules connected by APIs? When an approved swap happens, does coverage update everywhere instantly, or does a sync have to run? [MangoApps Shifts & Schedules](https://www.mangoapps.com/apps/shifts-scheduling) is built on one shared data layer: a single employee record that scheduling, time and attendance, leave, certifications, and analytics all write to and read from. An approved swap updates coverage instantly. An expired certification blocks an ineligible assignment automatically. A clock-in exception routes to the right manager before payroll runs, not after. --- ## 2. "AI" in scheduling means three different things. Know which one you are buying The term gets used for capabilities that differ by an order of magnitude in value. Sort them before you compare pricing. | Capability level | What it does | What it does not do | | --- | --- | --- | | **Assistive (AI-assisted build)** | Generates an optimized draft schedule from constraints. Flags conflicts, certification mismatches, and overtime exposure during build. | Act on its own after publish | | **Agentic (AI agents)** | Monitors continuously. Detects uncovered shifts, fills or offers them, routes attendance exceptions with context, reviews timesheets before payroll export. | Replace manager judgment on judgment calls | | **Predictive (forecasting)** | Builds staffing forecasts from historical patterns. Surfaces leave concentration and attendance patterns before they become incidents. | Guarantee demand accuracy without clean history | Most products marketed as "AI scheduling software" sit in the first bucket. That is genuinely useful, and it is also the easiest tier to build. The operational difference shows up in the second: a system that only helps you build the schedule leaves the entire post-publish day, the call-outs, the swaps, the no-shows, the missed punches, running on the manager's phone. MangoApps includes three agents in Shifts & Schedules, part of the broader [MangoApps AI](https://www.mangoapps.com/ai) layer. The **Scheduling Agent** drafts schedules, flags coverage gaps, and applies fairness weighting. The **Attendance Agent** monitors clock-in patterns in real time and routes exceptions to the responsible manager with the employee record, affected shift, and escalation path attached, inside [Time & Attendance](https://www.mangoapps.com/apps/time-attendance). The **Timekeeping Agent** reviews records before payroll export and surfaces only the exceptions that need human review, ahead of [timesheet export](https://www.mangoapps.com/apps/timesheets). All three sit inside the workflows they serve rather than in a separate AI console. **What to ask:** Can the AI take governed action, like surfacing eligible coverage and flagging exceptions, or can it only answer questions? --- ## 3. Compliance has to be applied at build time, not audited afterward This is the difference between labor management platforms that reduce risk and platforms that document it. Applied at build time means the constraint is enforced while the schedule is being created. An expired certification makes an employee ineligible for the assignment, so the assignment cannot be made. Break rules and rest-period requirements are evaluated as shifts are placed. A predictive scheduling ordinance that requires 14 days' notice is enforced by the publish workflow, not by a manager remembering. Audited afterward means a report tells you what already happened. In a healthcare or manufacturing environment, that report is a finding, not a control. The requirements that stack up fast in enterprise environments: - **Predictive scheduling and fair workweek ordinances.** Advance notice windows, predictability pay for late changes, right to rest between closing and opening shifts, good-faith estimates of hours. Rules vary by city and state, so the system needs jurisdiction-level configuration. - **Union and collective bargaining agreements.** Seniority-based assignment, overtime distribution order, minimum guaranteed hours, layered rules that differ by local. - **Certification and credential gating.** Clinical licensure, forklift and equipment certifications, food safety, security clearances, each with expiration behavior. - **Break and rest compliance.** Meal and rest windows that differ by jurisdiction and shift length, with missed breaks surfacing as attendance flags rather than payroll surprises. - **Overtime and hours thresholds.** Visible during the build, when the assignment can still be redistributed. Auditability matters as much as enforcement. In MangoApps, every scheduling and timekeeping action is logged with who, when, and why, and schedules can be shared with auditors or union stewards through secure read-only links. The full version history from draft through publish is retained. The [scheduling app detail page](https://www.mangoapps.com/directory/app/shifts-scheduling) covers the break planning, governance, and audit trail configuration in depth. --- ## 4. Fairness is now a measurable, auditable output Fairness used to be a value statement. In shift-based operations it is now a data question with legal and retention consequences. Every schedule distributes something scarce: desirable shifts, weekends off, premium hours, overtime opportunity. When that distribution happens by hand, week after week, patterns emerge that nobody intended and nobody can see. The associate who has closed every Friday for four months notices. The steward filing the grievance notices. The manager building the schedule usually does not, because no single week looks unfair. AI-driven shift scheduling can weight for this explicitly. Configurable fairness rules distribute nights, weekends, and premium shifts equitably over time, incorporating employee preferences, seniority, and assignment history. The output that matters is the report: fairness distribution over time, surfacing inequity before it becomes a grievance. Transparent prioritization matters too. When two employees request the same day off, the rule that resolves it should be configured, visible, and consistent, whether that is seniority, request history, or a fairness rotation, rather than whoever asked first or asked loudest. One signal most platforms never capture: what the shift was actually like. A brief [post-shift check-in](https://www.mangoapps.com/apps/shift-feedback) surfaces the understaffed shifts, the procedures that are not working, and the morale dips that no coverage or attendance report reveals. Rolled up by location, role, and supervisor, that becomes the qualitative counterpart to the fairness report. The [Shift Feedback app detail](https://www.mangoapps.com/directory/app/shift-feedback) covers survey configuration and manager dashboards. **What to ask:** Can the platform produce an auditable fairness report by employee, location, and shift type over any period? --- ## 5. Frontline adoption is the real gate, and most platforms fail it Enterprise workforce management platforms have historically been built for HR administrators, not for a supervisor with ten minutes between shifts. They assume desktop access, a corporate email address, a company-issued device, and training most frontline employees never receive. That assumption breaks the whole system. Not because employees dislike the software, but because partial usage produces partial data, and partial data makes every downstream number unreliable. If only the employees who remembered to log in confirmed their shifts, your coverage picture is fiction. If clock-in compliance sits at 60%, your labor cost reporting is an estimate. AI trained on that data inherits the gap. Adoption is an architecture outcome, not a change management campaign. The conditions that produce it: - Works on the phone employees already carry, with no corporate email, VPN, or company device required - No separate login and no second app for scheduling - Available in the employee's language (MangoApps supports 50+) - Offline functionality for low-connectivity environments like warehouse floors and remote sites - Delivery through the channel the employee actually checks: push, SMS, email, and [calendar sync](https://www.mangoapps.com/directory/app/calendar) to Google Calendar, Outlook, and iCal MangoApps reaches **90%+ adoption within 90 days of rollout**, because scheduling, clock-in, and time off live inside the same branded app employees already open for company news, tasks, and recognition. High adoption is not a vanity metric. It is the prerequisite for data you can manage by. This is also where the two product categories part ways. A standalone workforce management tool has to earn a login of its own. A digital workplace platform with native scheduling borrows the daily habit the schedule creates and spends it on everything else: the safety alert, the checklist, the training assignment. Workers toggle between applications roughly 1,200 times a day, according to a [Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) study; putting the schedule in the app that already holds the rest of the shift removes one of them. See [The Complete Guide to Frontline Communication Platforms](https://www.mangoapps.com/articles/frontline-communication-platforms-guide) for how scheduling fits the five layers of a frontline platform. A.S. Watson runs 27,000 employees across 1,700 stores in the Benelux region, with a store workforce that mostly does not have a company email address. Their Kruidvat store manager described the before state plainly: she photographed the schedule and posted it to WhatsApp, where people lost it or deleted it, then called or came into the store to ask when they were working. After: "they can open the app, click on the schedule, and see when they have to work. They never contact me anymore with questions because they can see it themselves." **What to ask:** What is the actual adoption rate within 90 days, and what causes it? --- ## 6. The schedule is only half the system. Hours worked is the other half [Employee scheduling software](https://www.mangoapps.com/apps/shifts-scheduling) that stops at publish solves the easier problem. Payroll does not pay assigned hours. It pays hours actually worked, and the gap between those two numbers is where most of the manager time and most of the cost leakage lives. The end-of-period ritual in a disconnected stack: cross-reference time and attendance reports across two platforms, fix missing punches by hand, chase down overtime discrepancies, reconcile break deductions, then export and hope. Exceptions that should have been caught during the shift surface in payroll data weeks later, when the only available action is a correction. What connected time and attendance changes: - **[Mobile clock-in with GPS geofencing](https://www.mangoapps.com/apps/time-attendance)** ties each punch to where work actually happened, without biometric hardware at every location. Employees outside the defined boundary trigger an automatic exception. - **Real-time exception detection** flags late arrivals, missed punches, and unexpected absences as they occur, routed to the responsible manager with full context. - **[Automated timesheet compilation](https://www.mangoapps.com/apps/timesheets)** applies shift hours, break deductions, overtime calculations, and multi-rate pay logic based on configured rules, rather than manual assembly. - **Pre-export validation** resolves exceptions and confirms sign-offs before data reaches payroll, so the pay period ends clean. The [Time & Attendance app detail](https://www.mangoapps.com/directory/app/time-attendance) covers geofence configuration, exception routing, and multi-pay-rate handling. For teams where how time is spent matters as much as how many hours, task-level time entry against projects and job codes feeds the same export alongside standard shift records, which is what makes job costing and billing possible without a separate system. **What to ask:** Do reviewed, multi-rate hours export clean into payroll, or do exceptions get discovered after the run? --- ## 7. Leave and availability have to write back to the schedule Time off that does not update the posted schedule is not managed. It is recorded. [Leave Management](https://www.mangoapps.com/directory/app/leave-management) is the capability area that closes this one. This is one of the most common gaps in enterprise workforce management, and one of the least visible until it costs a shift. Requests arrive by text, email, and spreadsheet. They get approved in one place and forgotten in another. The posted schedule keeps showing an employee who is on an approved vacation, and the coverage gap it creates is discovered on the morning of. The connected version: - Employees submit from mobile with current balance and pending requests visible before they submit, which removes the most common category of leave-related manager inquiry - Balances accrue automatically by employee type, tenure, or location, with no spreadsheet maintenance - The approving manager sees coverage impact on the affected shift **before** they confirm - Approved leave updates the schedule immediately, flags the gap, and can trigger an open-shift notification to eligible employees - A [team calendar view](https://www.mangoapps.com/directory/app/calendar) surfaces leave concentration in advance, so upcoming clusters that threaten coverage are planned around rather than patched at shift start - Configurable blackout periods require elevated approval during peak seasons, scheduled shutdowns, or critical compliance windows Availability works the same way. Employees submit preferences and availability changes in the app, inside a configurable request window with a hard cutoff, so inputs arrive before the schedule is built rather than after it is published. --- ## 8. AI governance is a purchasing requirement, not a due-diligence footnote Scheduling data is sensitive. Attendance records, pay rates, medical-adjacent leave reasons, disciplinary patterns, and performance signals all live in the same neighborhood. When AI starts acting across that data, governance stops being a security review checkbox and becomes a product requirement. What to require from any AI workforce management software, and what [MangoApps AI governance](https://www.mangoapps.com/ai/governance) is built to answer: - **Permission inheritance.** Every AI capability and every agent respects the calling user's permissions and cannot surface anything that person could not already see. A shift supervisor asking an AI assistant about coverage should not be able to retrieve another department's pay data. - **Data boundaries.** Employee data stays inside your boundaries and never trains public models. Get this in writing, and check whether it applies to the underlying model provider as well as the vendor. - **Audit logging.** Every AI action logged and reviewable, including what the agent did, what it saw, and on whose behalf. - **Configurable autonomy.** You decide how far each agent goes on its own: observe-only, suggest, require approval, or run automatically. Different agents warrant different settings, and the setting should be yours to change. - **PII detection and prompt logging.** Especially where clinical or financial data is adjacent. - **Model flexibility.** Provider choice should be a setting, not a re-platform. MangoApps supports OpenAI, Anthropic, and Gemini with automatic failover, plus private LLM deployment. - **Certification depth.** Attendance and labor data warrant the same posture as financial data. MangoApps holds **HITRUST, SOC 2 Type II, and ISO 27001 simultaneously**, plus FedRAMP ATO, HIPAA, and GDPR, backed by a 99.9% uptime SLA. Deployable as SaaS, Private Cloud, Customer VPC, or On-Premise. This is also where a platform architecture separates itself from a point tool. A chatbot bolted onto a stack of disconnected systems can answer a question, but it cannot safely act, because it cannot see across the work or be trusted with the permissions to change it. Governed action requires shared identity, shared permissions, shared data, and one governance model. That is an architecture decision made years before you evaluate it. --- ## 9. You probably do not have to replace UKG, ADP, or Workday The most common reason enterprise scheduling projects stall is a reasonable one: the organization just finished a major workforce management implementation and has no appetite for another. You usually do not need one. The gap is rarely in the system of record itself. It is downstream: time off that never reaches the posted schedule, attendance exceptions that surface weeks late, decisions made on last week's numbers, and the five to seven systems a manager crosses to get from schedule to payroll. The practical approach is integration onto a shared data layer rather than replacement. Hours and schedules from UKG, ADP, Workday, or your current tool feed the layer through native integrations, so the platform reads from your existing source of truth and the rest of the suite reads from the platform. MangoApps maintains **200+ enterprise integrations** with full REST API coverage for schedule reads and writes, employee data, shift assignments, and coverage status. That also means you do not have to start with scheduling. Four capability areas sit on the same data layer, and each delivers on its own: | Start here | If your biggest gap is | | --- | --- | | **[Schedules](https://www.mangoapps.com/apps/shifts-scheduling)** | Building coverage by hand is eating the week | | **[Time & Attendance](https://www.mangoapps.com/apps/time-attendance)** | Hours get reconciled after payroll rather than before | | **[Leave](https://www.mangoapps.com/directory/app/leave-management)** | Approved time off does not reach the posted schedule | | **[Analytics](https://www.mangoapps.com/solutions/workforce-management)** | You are managing on yesterday's numbers | Nothing downstream requires the schedule itself to live in MangoApps. Typical implementation runs **8 to 12 weeks** with a dedicated cross-functional team and a named Customer Success Manager from day one, and existing systems keep running while the data layer comes online underneath them. --- ## 10. The scheduling decision is really a platform decision This is the one that determines whether the project ages well, and it is the reason the buying question has changed. Enterprises are no longer choosing between scheduling tools. They are choosing between a workforce management suite that connects to everything else through integrations, a digital workplace platform that runs scheduling natively beside communication, tasks, training, and HR, and an employee app that displays a schedule generated somewhere else. The comparison below lays out who sits in each category. For most of the last decade, the right answer for employee technology was best of breed: pick the best intranet, the best LMS, the best scheduling tool, and connect them. That made sense when AI was a feature. It does not hold when AI is infrastructure. An AI agent that acts on behalf of an employee needs to know who that employee is, what they are authorized to do, what their work context is, and how to route results back into the right workflow. That requires shared identity, shared permissions, shared employee data, and governance that spans every workflow. A collection of point tools connected by APIs cannot reliably provide it. Every tool you add is another integration to maintain and another broken AI context boundary. The practical version of this: what happens when you turn on the next thing. - A certification expiration triggers a training assignment, and completion restores scheduling eligibility automatically - A completed safety inspection updates schedule eligibility - Coverage history shows where headcount is actually thin, so recruiting targets real operational gaps rather than requisition guesses - A new hire's first shift is assigned before day one, and a departure triggers schedule updates, timekeeping closure, and final payroll routing - Attendance reliability and [shift feedback](https://www.mangoapps.com/apps/shift-feedback) feed performance reviews, giving managers a fuller picture than a review cycle alone produces None of those are integrations. They are intersections inside one platform that shares a single data model, which is why they produce a kind of operational intelligence that no combination of point solutions replicates. MangoApps Shifts & Schedules runs on the same platform as Employee Experience, the rest of Frontline Operations, and People Operations. Identity, employee data, permissions, integrations, and AI governance are configured once, and every app you add inherits them. Start with the schedule you need to fix now. Expand into the next workflow as a configuration, with users, data, and history carrying forward. No second implementation, no migration. **2M+ users worldwide. 18+ years building one platform for the frontline. 98% customer retention. NPS 78.** Trusted by AutoZone, PetSmart, A.S. Watson, and the Kansas City Chiefs. --- ## Which workforce management platforms include AI-driven shift scheduling for enterprises? Two kinds of products now ship AI-driven shift scheduling for enterprises. Workforce management suites such as UKG, ADP Workforce Now, Workday Scheduling, Legion, Quinyx, Shiftboard, Workforce.com, and TCP Humanity build and optimize schedules as their core job and connect to communication and training tools through integrations. Digital workplace platforms with native scheduling, including MangoApps, WorkJam, and Connecteam, build the schedule inside the same app employees already use for news, tasks, training, and HR self-service. Employee apps such as Flip and Blink display a schedule generated elsewhere rather than generating it. | Platform | Category | AI-assisted schedule creation | Shift marketplace and swaps | Time and attendance | Communication, tasks, and training on the same platform | Sign-in without corporate email | Keep the incumbent HRIS | | --- | --- | --- | --- | --- | --- | --- | --- | | [MangoApps](https://www.mangoapps.com/solutions/workforce-management) | Digital workplace platform | Yes | Yes | Yes (mobile, geofenced) | Yes, native | Yes | Yes (Workday, UKG, ADP, SAP SuccessFactors, Paylocity, Rippling, BambooHR among 200+ integrations) | | [WorkJam](https://www.workjam.com/) | Frontline digital workplace | Vendor-stated | Yes (open shift marketplace) | Yes | Communication and tasks native; training partial | Yes | Vendor-stated | | [Connecteam](https://connecteam.com/) | All-in-one deskless app | Vendor-stated | Yes | Yes (GPS time clock) | Yes, native (SMB and mid-market) | Yes | Payroll integrations (vendor-stated) | | [UKG](https://www.ukg.com/) | Workforce management suite | Yes (vendor-stated) | Yes | Yes | Via integration | Vendor-stated | Is the HRIS | | [ADP Workforce Now](https://www.adp.com/) | HCM and WFM suite | Vendor-stated | Vendor-stated | Yes | Via integration | Vendor-stated | Is the HRIS | | [Workday Scheduling](https://www.workday.com/) | HCM suite module | Vendor-stated | Vendor-stated | Yes | Via integration | Vendor-stated | Is the HRIS | | [Legion](https://legion.co/) | AI workforce management | Yes (vendor-stated) | Yes | Yes | Via integration | Vendor-stated | Via integration | | [Quinyx](https://www.quinyx.com/) | AI workforce management | Yes (vendor-stated) | Yes | Yes | Via integration | Vendor-stated | Via integration | | [Shiftboard](https://www.shiftboard.com/) | Enterprise scheduling | Vendor-stated | Yes | Yes | Via integration | Vendor-stated | Via integration | | [Flip](https://www.getflip.com/) | Frontline employee app | No (surfaces the HRIS schedule) | Swaps via HRIS mini-apps (vendor-stated) | Via HRIS | Communication native | Yes | Yes | *Capability statements for third-party vendors are taken from each vendor's public documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps. For a ranking of standalone scheduling tools, see [The Best Employee Shift Scheduling Software of 2026](https://www.mangoapps.com/articles/best-employee-shift-scheduling-software).* --- ## Digital workplace platforms with built-in shift scheduling vs standalone scheduling software The difference is not the algorithm. Both categories can generate a compliant schedule. The difference is what happens to the schedule after it is published, and to the employee record that fed it. | Decision | Standalone workforce management | Digital workplace platform with native scheduling | | --- | --- | --- | | Identity | A separate login, often gated on a corporate account | One login provisioned from the HRIS, activated on a personal phone | | What pulls workers into the app | Managers push reminders | The schedule itself; news, tasks, and training ride along | | Communication about the schedule | A separate tool, or text messages | The same feed, with acknowledgment | | Compliance evidence | The schedule audit trail | Schedule, acknowledgment, and training completion in one record | | AI governance | One permission model per tool | One permission model across every workflow | | Tools per employee | One more | One fewer | The arithmetic is the argument. The average company runs 101 applications, and companies with more than 5,000 employees average 131, according to [Okta's Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/). A [Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) study found workers toggling between applications roughly 1,200 times a day. A standalone scheduler adds to both numbers. A platform that holds the schedule where the rest of the shift already lives subtracts from them. For the fuller argument, see [Why the Platform Decision Comes Before the App Decision](https://www.mangoapps.com/articles/platform-decision-first) and [What "Platform" Should Actually Mean](https://www.mangoapps.com/articles/what-platform-means). --- ## Shift scheduling with built-in team messaging for hourly employees "Built-in messaging" should mean more than a chat tab beside the schedule. It should mean that a coverage request is a message the right teammates receive, that a swap is a message the manager approves in one tap, that a schedule change is a message with acknowledgment so the manager knows who has seen it, and that all of it lives in the app where the schedule already is. A.S. Watson's experience shows the before and after. Kruidvat store managers used to photograph the schedule and post it to WhatsApp, then field calls from employees who lost or deleted the photo. Today more than 20,000 retail employees across the organization receive their weekly schedules in the MangoApps app, and store managers no longer field schedule questions. For how this fits into the employee app, see [The Best Employee Apps for Hourly and Frontline Workers](https://www.mangoapps.com/articles/best-employee-app-software) and the [MangoApps employee app](https://www.mangoapps.com/solutions/employee-app). --- ## The vendor evaluation checklist Use these on every platform you evaluate, including this one. They are written to surface the architecture decisions that determine whether a scheduling tool still serves you in three years. **Architecture** - Is this one shared data model, or separate modules connected by APIs? - When an approved swap happens, does coverage update everywhere instantly, or does a sync have to run? - When you add a capability later, is it a configuration on the platform you already own, or a new implementation? **Frontline access** - Does it work for employees with no corporate email, no company device, and no VPN? - What is the actual adoption rate within 90 days, and what causes it? **AI** - Does the AI run on your own operational data and permissions, or a generic model bolted on top? - Can the AI take governed action, or can it only answer questions? - Can you set autonomy level per agent, from observe-only to run automatically? **Compliance** - Are labor law, union rules, and certification requirements applied while the schedule is being built, or audited after? - Is every scheduling and timekeeping action logged and shareable with auditors or union stewards? - Can it enforce jurisdiction-specific predictive scheduling ordinances at publish? **Payroll** - Do reviewed, multi-rate hours export clean into payroll, or do exceptions get discovered after the run? **Expansion** - Can you start with one gap in one location, or does the vendor require an all-at-once rollout? **Security** - Does it hold HITRUST, SOC 2 Type II, and ISO 27001 together, with the deployment model your environment requires? --- ## Frequently asked questions ### What is AI shift scheduling? AI shift scheduling is the use of machine learning and rules-based logic to generate, validate, and adjust employee work schedules automatically. The system evaluates availability, certifications, labor law and union rules, demand forecasts, fairness history, and labor cost at the same time, then produces a compliant draft schedule for manager review. More capable systems continue working after publish, detecting coverage gaps, blocking ineligible assignments, and routing attendance exceptions in real time. ### How is AI shift scheduling different from automated scheduling? Automated scheduling applies fixed rules and templates: repeat last week's pattern, fill slots by rotation, enforce a minimum headcount. AI-driven shift scheduling optimizes across many competing variables at once and learns from history, weighing fairness over time, predicting demand from past patterns, and surfacing risks like overtime exposure that a template cannot see. In practice, most enterprise platforms combine both: rules for hard constraints that must never be violated, AI for optimization within them. ### Does AI replace the manager who builds the schedule? No, and vendors claiming otherwise should be treated with skepticism. AI removes the mechanical work of assembling a compliant draft and continuously monitors for exceptions. The manager still makes the judgment calls: who is ready for a harder shift, which coverage risk is acceptable this week, how to handle the employee going through something difficult. The value is that a manager spends the day on decisions that require a manager rather than on coordination a system should handle. ### What data does AI workforce management software need to work well? At minimum: current employee availability and preferences, certification and credential status with expiration dates, approved and pending leave with balances, applicable labor law and union rules by jurisdiction, pay rates and differentials, hours already worked toward overtime thresholds, historical attendance patterns, and a demand signal such as traffic, volume, or patient census. If any of these live in a separate system that syncs on a schedule, the AI is optimizing against stale information. ### How long does it take to implement AI shift scheduling in an enterprise? MangoApps implementation typically runs 8 to 12 weeks with a dedicated cross-functional team and a named Customer Success Manager from day one. A common sequence is two weeks of alignment and planning, four weeks connecting existing systems and configuring rules, three to four weeks validating at one location, then expansion. Existing systems keep running throughout. Organizations that attempt an all-sites, all-capabilities launch at once take considerably longer and see worse adoption. ### Do we have to replace our existing HRIS or workforce management system? No. Systems of record like UKG, ADP, Workday, SAP SuccessFactors, and BambooHR can feed shifts and hours onto the shared data layer through native integration, so the platform reads from your existing source of truth. Nothing gets ripped out. MangoApps maintains 200+ enterprise integrations plus full REST API and webhook access. The schedule does not have to live in MangoApps for connected time, leave, and analytics to work. ### How does AI scheduling handle union rules and collective bargaining agreements? Union rules are configured as constraints applied during schedule creation rather than reviewed after. That includes seniority-based assignment order, overtime distribution sequence, minimum guaranteed hours, rest-period requirements, and rules that differ by local. Auditability is equally important: every scheduling and timekeeping action should be logged with who, when, and why, and schedules should be shareable with union stewards through secure read-only links so disputes are settled with records rather than recollection. ### Can AI shift scheduling comply with predictive scheduling and fair workweek laws? Yes, when the platform supports jurisdiction-level configuration. Predictive scheduling ordinances vary significantly by city and state, covering advance notice windows, predictability pay for late changes, right to rest between closing and opening shifts, and good-faith estimates of hours. The requirement to test in a demo is whether these rules block or gate the publish action rather than appearing in a compliance report afterward. Consult your employment counsel on which specific ordinances apply to your locations. ### How does AI make shift scheduling fairer? Fairness rules weight the distribution of desirable and undesirable shifts, nights, weekends, and premium hours across employees over time, incorporating stated preferences, seniority, and assignment history. Because the system holds the full history, it can also report on distribution, which is the part manual scheduling cannot do. A manager building week by week has no view of a four-month pattern. An auditable fairness report surfaces inequity before it becomes a grievance. ### What is a shift marketplace and how does it relate to AI scheduling? A [shift marketplace](https://www.mangoapps.com/apps/shift-marketplace) lets employees post shifts they need to give away and claim open shifts from their phone, within eligibility rules the manager configured by role, location, certification, hours worked, and preference priority. It moves swap coordination out of text chains and into a system where approvals update the schedule automatically. Combined with AI eligibility checking, it prevents the two most common swap failures: someone covering a shift they are not certified for, and a swap that quietly pushes an employee into overtime. See the [Shift Marketplace app detail](https://www.mangoapps.com/directory/app/shift-marketplace) for eligibility and fairness control options. ### How do AI agents work in shift scheduling? [AI agents](https://www.mangoapps.com/ai) monitor and act inside a specific workflow rather than answering questions in a chat window. A Scheduling Agent watches for uncovered shifts and fills or offers them. An Attendance Agent flags late arrivals, missed punches, and absence patterns as they occur, routing each exception to the responsible manager with the employee record, affected shift, and escalation path attached. A Timekeeping Agent reviews timesheet records before payroll export and surfaces only the exceptions needing human review. Autonomy should be configurable per agent, from observe-only to fully automatic. ### Is employee scheduling data used to train AI models? It should not be. In MangoApps, enterprise data stays inside your boundaries and never trains public models. Every AI capability and agent respects the calling user's permissions and cannot surface anything that person could not already see, and every action is logged and reviewable. Ask any vendor to confirm this in writing, and confirm that the commitment extends to the underlying model provider, not only to the vendor's own systems. ### What adoption rate should we expect from frontline employees? Legacy intranets and desktop-first workforce systems commonly land in the 30 to 40% range on the frontline. Purpose-built frontline platforms should do substantially better. MangoApps reaches 90%+ adoption within 90 days of rollout, driven by architecture rather than campaigns: it runs on the phone employees already carry, requires no corporate email, VPN, or second device, works in 50+ languages, and puts scheduling inside the same branded app employees already open for news, tasks, and recognition. ### What is the ROI of AI workforce management software? The recoverable amounts fall into two categories. Dollars: reduced turnover as fair, predictable, mobile-first scheduling improves retention, reclaimed overtime as exposure surfaces before the schedule locks rather than after payroll, and fewer payroll corrections as exceptions resolve before export. Hours: schedules built in minutes instead of hours, swaps handled without a text chain, and pay periods that end with timesheets already reviewed. Modeling it credibly takes four inputs: headcount across sites, average pay rates by role, current annual turnover rate, and current overtime rate. ### Which industries benefit most from AI shift scheduling? Any operation running shift-based work with variable demand and credential requirements. The dominant gap differs by industry. **Retail and grocery:** coverage that swings with peak and seasonal demand, plus balancing across multiple stores. **Healthcare:** assignments gated by certification, layered union and labor rules, and coverage that cannot lapse for an hour. **Manufacturing, warehouse, and distribution:** clean shift handoffs, equipment and safety certifications matched to assignment, and overtime creeping in across crews. **Field service and facilities:** on-call rotations that have to hold and field time that has to reach payroll without re-entry. ### Can AI shift scheduling work across multiple locations? Yes, and multi-site is where the value concentrates. Look for the ability to build and publish schedules across sites and departments from one interface, with role and certification filtering applied automatically, and support for both centralized and decentralized ownership in the same system. Operations leaders keep a high-level view across all groups while local managers retain team-level control over the personnel they are responsible for. ### How does AI scheduling connect to payroll? Through automated timesheet generation and validated export. Shift hours, break deductions, and overtime calculations apply automatically from configured pay rules. Multi-rate logic handles regular, overtime, holiday, and role differential rates. Flagged records route to manager review as a single sign-off step, and exceptions are resolved before export rather than discovered after the run. Export formats should match standard payroll platforms without manual transformation. ### What does AI shift scheduling cost? Enterprise pricing is typically per employee per month and varies with which capabilities are turned on, deployment model, and scale. The more useful comparison is total cost against the stack it replaces: a separate scheduling tool, a separate time and attendance system, a separate leave tool, and the integration maintenance between them, plus the manager hours currently spent on coordination. Buying on a platform means the next capability is a configuration rather than a new contract, implementation, and security review. ### Can we start with one location or one capability? Yes, and it is the approach that works. Start with the single gap costing you the most, prove it at one location, then expand. Keep the systems you already depend on and bring them onto the shared data layer through integration. The four capability areas, schedules, time and attendance, leave, and analytics, each deliver independently and get sharper as more connects. ### How do we know if our current scheduling is actually broken? Score five gaps honestly. **1)** When the schedule publishes, does it already reflect real availability and current certifications, or do you correct it after someone does not show? **2)** Does approved time off flow into the posted schedule automatically? **3)** Do attendance exceptions reach you before payroll runs, or after? **4)** How many separate systems does a manager touch in one shift cycle, from build to payroll? **5)** Are coverage and labor decisions made on real-time data, or yesterday's? Zero to one gaps open means your infrastructure is doing the coordination. Two to three is the most common score and the most expensive one to leave alone. Four to five means your managers are absorbing work the system should be doing. ### Which workforce management platforms include AI-driven shift scheduling for enterprises? Workforce management suites such as UKG, ADP Workforce Now, Workday Scheduling, Legion, Quinyx, Shiftboard, Workforce.com, and TCP Humanity include AI-driven scheduling as their core function. Digital workplace platforms with native scheduling, including MangoApps, WorkJam, and Connecteam, build the schedule inside the same app employees use for communication, tasks, and training. Capability statements for third-party vendors are vendor-stated. ### Which digital workplace platforms have built-in shift scheduling for frontline staff? MangoApps, WorkJam, and Connecteam run scheduling natively alongside communication, tasks, and, in MangoApps and Connecteam, training and HR self-service. Employee apps such as Flip and Blink surface a schedule from the HRIS or a workforce management system rather than generating one. ### Is there shift scheduling software with built-in team messaging for hourly employees? Yes, in the platforms that treat the schedule as part of the employee app rather than a separate tool. In MangoApps, coverage requests, swaps, approvals, and schedule changes are messages in the same app that holds the schedule, with acknowledgment so managers know who has seen a change. Standalone schedulers typically rely on a separate communication tool. --- ## Where to go next See [MangoApps Shifts & Schedules](https://www.mangoapps.com/apps/shifts-scheduling) configured for your organization's structure and use cases: **[Request a personalized demo](https://www.mangoapps.com/schedule-a-demo)** Read the full book, *AI Scheduling for Shift-Based Teams: Run the Schedule. Trust the Hours.*: **[Get the book](https://www.mangoapps.com/resources/shifts-schedules-book)** Explore the complete picture across schedules, time, leave, and analytics: **[Workforce Management solutions](https://www.mangoapps.com/solutions/workforce-management)** --- # MangoApps Wins Silver Stevie® Award in 2026 International Business Awards® **Author:** The MangoApps Team **Published:** 2026-08-13 **Category:** employee-platform MangoApps, the employee platform for the frontline, has been named the winner of a Silver Stevie® Award in the Best AI-Powered Product or Service category in The 23rd Annual International Business Awards® (IBAs). *The 23rd Annual International Business Awards® are the world’s premier business awards competition, recognizing outstanding organizations, executives, entrepreneurs, and teams worldwide.* --- **SEATTLE, WA – August 13, 2026 –** [MangoApps](https://www.mangoapps.com/), the employee platform for the frontline, has been named the winner of a Silver Stevie® Award in the Best AI-Powered Product or Service category in The 23rd Annual International Business Awards® (IBAs). The International Business Awards are the world’s premier business awards program. All individuals and organizations worldwide, public and private, for-profit and non-profit, large and small, are eligible to submit nominations. The 2026 IBAs received entries from organizations in 82 nations and territories. MangoApps won in the Best AI-Powered Product or Service category for its work embedding AI directly into the daily workflows of frontline and desk employees. Over the last several years, MangoApps has embedded AI as infrastructure in its platform rather than a bolt-on feature, introducing named [AI Agents](https://www.mangoapps.com/ai/agent-library) for scheduling, leave, compensation, attendance, and recruiting that act on live enterprise data and answer employees with cited, real-time responses. At the same time, MangoApps has rapidly expanded its [native apps](https://www.mangoapps.com/apps) across Employee Experience, Frontline Operations, and People Operations, with AI built into each one. That gives enterprises one platform, one identity, and one data model powering every workflow, instead of layering AI on top of disconnected point solutions. The approach has also earned MangoApps an AI Innovator badge from ClearBox Consulting and a spot on TIME and Statista’s inaugural list of America’s Top WorkTech Companies. “This recognition belongs to the team that spent the last few years rethinking how AI should show up for people who don’t sit at a desk,” said Anup Kejriwal, CEO of MangoApps. “We’re grateful to the Stevie judges for the recognition, and more importantly, to our customers who trusted us to build this the right way.” Stevie Award nominations were evaluated by more than 200 business professionals worldwide serving as judges on 9 specialized committees. Stevie Award winners were determined based on judges’ average scores during the independent judging process in June and July. “The 2026 International Business Awards winners represent the very best in business achievement from organizations of all sizes and across virtually every industry,” said Stevie Awards President Maggie Miller. “This year’s winners have demonstrated exceptional innovation, leadership, resilience, and results in a highly competitive global field. We congratulate every Stevie Award winner and look forward to celebrating their achievements together in Paris on October 28.” Details about The International Business Awards and the lists of Stevie Award winners are available at [IBA.Stevieawards.com](http://iba.stevieawards.com). **About MangoApps** MangoApps is the AI-Ready Employee Platform for the Frontline. Built for enterprises with large frontline and distributed workforces, MangoApps brings together Employee Experience, Frontline Operations, and People Operations on a single platform under one identity, one data model, and one AI foundation. Trusted by more than 2 million users at leading organizations around the world, MangoApps keeps business-critical work moving every day. For more information, visit www.mangoapps.com. **About the Stevie Awards** Founded in 2002, the Stevie Awards are widely recognized as the world’s premier business awards programs, honoring outstanding achievements in the workplace worldwide. The name “Stevie” is derived from the Greek name Stephanos, meaning “crowned.”** --- # Why Workforce Records Fail When Audits Actually Happen **Author:** MangoApps Team **Published:** 2026-08-09 **Category:** compliance-risk A warehouse safety audit hits. The compliance team pulls training records. # Why Workforce Records Fail When Audits Actually Happen A warehouse safety audit hits. The compliance team pulls training records. Three employees show certificates for a forklift safety course — but the course was revised six months ago, and the current version looks different from what these employees actually completed. The organization cannot prove what was certified on the date of completion. This scenario repeats itself across industries and functions: not because records are missing, but because the records that exist weren't built to hold their shape. A training certificate that updates when the course updates is not a record — it's a living document. A corrective action marked "complete" with no link to the original finding, no work order, and no completion photo is not evidence. A performance review that renders differently in a PDF than it appeared on screen cannot be relied upon for appeals or legal documentation. Records don't fail audits because they're absent. They fail because they can't prove what they claim. --- ## Training Records That Can Actually Be Audited The training completion record is one of the most consequential documents an organization creates — and one of the least reliable. Regulators, insurers, and legal teams routinely find that completion records don't reflect what employees actually learned, when, or under what version of a curriculum. Three training releases this week address different parts of this problem. [Training Certificates as Permanent Records](https://www.mangoapps.com/changelog/3105) landed on August 6. Certificates of completion are now lifetime records: CE credits are snapshotted at the moment of completion, which means a subsequent course revision doesn't retroactively alter what an employee was certified on. The record reflects what they completed on the day they completed it — not a living document that shifts as the curriculum evolves. Certificates also no longer expire when a linked certification does, which previously created situations where an employee's documented achievement disappeared without notice. [SOP Training Prerequisites](https://www.mangoapps.com/changelog/3102), released August 2, connects training to procedure: employees must complete required training before they can mark an SOP done. This creates a verifiable link between knowing and doing — which is precisely what compliance frameworks require when they ask for documented evidence that employees were qualified before performing a regulated procedure. [Multi-Quiz Courses](https://www.mangoapps.com/changelog/3102) lets courses include multiple assessments, and learners must pass all of them before the course marks as complete. A single final exam is a weak signal; multiple checkpoints throughout a course create a stronger, more defensible record of demonstrated competency. These three releases address what might be called the training record integrity gap: the distance between a system that says someone completed something and evidence that holds up when that claim is challenged. A training record is not just internal documentation. It's a claim an organization makes to regulators, insurers, and in some cases courts — that an employee had the knowledge and demonstrated the competency required before they performed a task. Each of these changes makes that claim harder to undermine. --- ## Operations Records That Close the Loop Training records are one surface. Operations records are another, and they carry different vulnerabilities. When a safety inspection finds a deficiency — a broken guardrail, a failed equipment check, a process gap — what happens next depends on whether there's a clear accountability chain from finding to resolution. In many organizations, that chain exists on paper but not in practice: the finding lives in one system, the work order lives in another, and the completion note sits in someone's email thread. When an auditor asks "show me the corrective action for this finding," the trail breaks down. [Corrective Action Detail Page](https://www.mangoapps.com/changelog/3106), released August 7, gives assigned corrective actions a dedicated page that preserves the original finding in full — severity rating, photos, location, damage detail, and the inspector's notes — alongside a work order field and a completion photo upload. This is a modest UI change with a meaningful compliance implication: the link between finding and resolution is no longer something that has to be reconstructed after the fact. It's built into the record from the moment the action is assigned. [Performance Review PDF Export](https://www.mangoapps.com/changelog/3104) addresses a structurally similar problem in a different context. Performance review documentation often lives in a rendering gap: the system shows one thing, the exported file shows another, and when a rating decision is challenged, the PDF cannot be treated as authoritative. The new export renders the full designed layout — status, ratings comparison, goal cards, 360 feedback — matching exactly what reviewers and employees saw on screen. What you saw is what gets documented. These are not flashy features. They are infrastructure features: the unglamorous work of making sure that when an action matters enough to record, the record reflects what actually happened. --- ## Security Records and the Tamper-Proof Baseline The third category that audits routinely surface is security and access: who logged in, when, from where, what they changed, and whether any of those events were later altered. [Authentication Audit Log](https://www.mangoapps.com/changelog/3105), released August 6, gives admins a complete, tamper-proof log of every login and logout event across every sign-in method. For organizations in regulated industries — healthcare, finance, government, staffing — this is table stakes. For organizations that have scaled without explicitly addressing it, it's been a gap. [Chat Message Audit Trail](https://www.mangoapps.com/changelog/3103), released August 3, adds a full record of edits and deletions to chat messages: who changed what, when, and what the original content was. This matters in HR contexts where internal conversations serve as evidence, and in compliance contexts where message tampering — intentional or not — needs to be detectable. [Maintenance Mode & Security Lockdown](https://www.mangoapps.com/changelog/3104), August 5, lets admins trigger immediate security lockdowns that revoke all active sessions and tokens across a tenant. Alongside [Per-Tenant Session Timeout](https://www.mangoapps.com/changelog/3104), which lets each organization configure its own inactivity policy independently of platform defaults, this extends audit-ready security posture to the session layer — where many breaches begin and where many compliance frameworks focus attention. Together, these releases address a pattern that security auditors frequently surface: the organization has access controls, but no way to prove they worked as intended, or to show exactly what happened before an incident. --- ## What Audit Readiness Actually Looks Like The phrase "audit ready" is often used to mean something narrow: we have the documentation the auditors will ask for. That framing puts organizations in a reactive posture — assembling records after the fact to satisfy a requirement they didn't anticipate. The more durable version of audit readiness looks different. It's an organization where records are created correctly at the moment the action happens — where a training completion automatically snapshots the right version of the curriculum, where a corrective action carries the original finding with it from the moment it's assigned, where a login event is logged tamper-proof by default. Records don't fail audits because they were constructed correctly from the start. This week's MangoApps releases share this structural quality. They are not about capturing more data. They are about capturing the right data at the right moment, in a form that holds up when tested. That shift — from data collection to record integrity — is harder to build than a dashboard or a report. It requires decisions made at design time: what a record needs to contain, when it needs to be locked, and how it needs to link to adjacent records. Most of these features are invisible when things go well. They become load-bearing when something needs to be proven. --- # Seven Things That Only Happen When Work Runs on One Platform **Author:** MangoApps Team **Published:** 2026-08-06 **Category:** integrated-digital-workplace The return on a platform is at the seams. Seven cross-app flows that only happen when work shares one data model, and why a stack cannot copy them. *The short version: the real return on a platform is not the apps. It is what happens at the seams, when every app shares one data model. Here are seven cross-app flows that only work when the work runs in one place, and why a stack of separate tools cannot copy them at any price.* --- Most of the platform conversation is about breadth: every app, every employee, one AI layer. Breadth is the setup. The payoff is somewhere less obvious, at the seams between the apps. The real return on a platform is not any single app. It is what becomes possible when they all share one data model, and it grows with every capability you add. What follows are seven flows that only happen when the work runs in one place. They are not integrations. They are architecture. ## Seven flows that only happen on one shared record Each one is a single event moving cleanly across several apps, with no manual handoff between them. 1. **Comms → Frontline reach → Translation → Knowledge.** A company update is published once. It distributes across the feed, mobile, and digital signage, auto-translates into each employee's language, and read receipts confirm who has seen it. Ask AI can then answer questions about it, grounded only in the approved version. *Every employee reached in their own language, desk and frontline alike, with proof it landed.* 2. **Safety → Learning → Scheduling.** A safety certification nears expiry. The Skills Agent flags it with lead time, training auto-assigns, and scheduling stops routing that employee to roles that require the lapsed credential. *The compliance gap closes before it becomes an incident.* 3. **Talent Acquisition → HR → Performance.** A candidate accepts an offer. Onboarding triggers, access provisions, first training enrolls, and initial goals are set. *The new hire is ready on day one, not in week three.* 4. **HR → Everything.** A role change is entered once, in HR. Training assignments, comms targeting, OKR alignment, and succession eligibility all update at once. *One entry, no manual reconciliation across five systems.* 5. **Performance → Recognition → Learning.** A manager opens a review. OKR progress, recognition history, completed training, and current certifications are already assembled. *The review starts from a complete picture, not a blank form and a week of digging.* 6. **Plugin AI Builder → Foundation → Governance.** A team needs a workflow no vendor ever built. They describe it in plain language, the Plugin AI Builder creates it, and it inherits the platform's identity, permissions, data, and audit trail the moment it exists. *The gap that used to justify the next procurement cycle closes from inside the platform.* 7. **AI → Governance → Everything.** An agent acts on any of the above. It works within one permission model and writes to one audit trail. *Every automated action across the whole business is governed and reviewable in one place.* ## Why a stack of point tools cannot copy this Each of those seven is one event moving cleanly through several apps. On a stack of separate tools, every arrow in those chains is a manual handoff. Someone re-keys the certification into the scheduler. Someone remembers to assign the training. Someone hopes the AI is reading the current policy and not last year's. The chain breaks at every seam, and the breaks are where compliance gaps and bad data live. And when a workflow is missing entirely, the stack's only answer is another procurement cycle, which is exactly how the stack got built in the first place. This is why the seven cannot be bought as a feature. They are not a feature. They are what a [shared data model](https://www.mangoapps.com/resources/what-platform-means) does, and no amount of integration recreates them, because the tools underneath were never built to share a record. ## What consolidation looks like in practice The precondition for all seven is the one most companies still have not met: the work running on one platform instead of a stack of separate systems. ![integration posture](https://mango-cdn.b-cdn.net/marketing/uploads/integration-posture.png) [Paul Miller Auto Group](https://www.mangoapps.com/resources/paul-miller-auto-group-case-study) is a New Jersey dealership network of 14 locations that historically ran as 14 independent businesses. Sales consultants juggled five to seven separate applications, each with its own password. Inventory was reported to corporate in different formats over email. The company directory was a printed spreadsheet, replaced by hand with each new hire. Moving onto one platform collapsed that into a single system: single sign-on across all applications, inventory from all 14 locations in one real-time view, a live directory, a shared payroll calendar, and communications that reach every location at once. > "When you have multiple locations, it's really helpful to have a single place that everybody goes. MangoApps enables us to reach every employee, streamline processes across the business, and simplify our tech stack with single sign-on." > — Hayes Miller, Director of Communications, Paul Miller Auto Group That is not yet all seven flows. It is the precondition for them: one shared record instead of a stack, which is the point at which the seams stop being manual handoffs and start compounding. ## The compounding return This is the return on the platform decision that never shows up in a feature comparison, because it is not in any single feature. It is one event, carried across many apps, on one shared record, with the AI layer reading and writing underneath it all. ![one event one shared record](https://mango-cdn.b-cdn.net/marketing/uploads/one-event-one-shared-record.png) It grows with every capability you add, and it cannot be bought later, which is the entire reason [the platform decision comes first](https://www.mangoapps.com/resources/platform-first). One foundation, chosen deliberately, is what turns a collection of apps into [the AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/platform). ### Get the full argument This is the compounding case in short. The full chapter, all seven flows and why a stack cannot reproduce them, is in the book. **Download *The Employee Platform for the AI Era* (Executive Edition)** from the resource library [here](https://www.mangoapps.com/resources/employee-platform-executive-ebook), or [talk to someone who knows your industry](https://www.mangoapps.com/schedule-a-call). ## Frequently asked questions **Why is a platform worth more than the sum of its apps?** Because the highest-value outcomes happen between the apps, not inside any one of them. When every app shares one data model, a single event can move across comms, HR, learning, scheduling, and performance with no manual handoff. Those cross-app flows are the compounding return on a platform, and they grow with every capability you add. A collection of separate apps, however good each one is, cannot produce them. **Can integrations replace a shared data model?** No. Integrations move data between tools that each keep their own separate record, so every cross-app step is a handoff that can break, lag, or conflict. A shared data model means there is one record that every app and agent reads and writes, so the step does not have to be handed off at all. Integrations connect systems; a shared data model removes the seam entirely. **What does "one shared data model" enable?** It enables one event to trigger the right actions everywhere at once, correctly and automatically. A role change entered once in HR updates training, comms targeting, OKR alignment, and succession eligibility together. An accepted offer provisions access, enrolls training, and sets goals. A lapsing certification assigns training and stops unsafe scheduling. None of these require re-keying data between systems, because there is only one system of record. **Why can't a best-of-breed stack reproduce these workflows?** Because the tools were never built to share a record. On a stack, every arrow in a cross-app workflow is a manual handoff: someone re-keys the certification, someone remembers the training, someone hopes the AI is reading the current policy. The chain breaks at each seam, and the breaks are where compliance gaps and bad data appear. When a workflow is missing entirely, the stack's only answer is to buy another tool. **What is an example of a cross-app workflow on one platform?** A safety certification nears expiry. The system flags it with lead time, auto-assigns the required training, and stops scheduling that employee into roles that need the credential until it is renewed. On one platform this happens automatically across safety, learning, and scheduling. On a stack of separate tools, each of those steps is a manual task someone has to remember, and the gap between them is where an incident happens. **What is an AI-Ready Employee Platform?** It is an employee platform where every app and AI agent shares one identity, one record, and one governance model, so work flows across the whole business without manual handoffs and AI can act safely on top of it. That shared foundation is what produces the compounding, cross-app outcomes a stack of separate tools cannot. MangoApps is the AI-Ready Employee Platform for the Frontline. --- # Governing AI by Design: Autonomy Dials, Kill Switches, and Defensible Data Boundaries **Author:** The MangoApps Team **Published:** 2026-08-06 **Category:** enterprise-ai Most enterprises deploy AI with no governance underneath. Governing AI by design: platform-enforced permissions, autonomy dials, kill switches, defensible data. *The short version: most enterprises are deploying AI with no governance underneath it. Governing AI by design means governance is not a policy written later. It is how the AI is built. Every agent arrives permitted, scoped, and auditable, with an autonomy dial you set per agent, a kill switch that nests from platform-wide down to a single agent, data boundaries you can defend, and human approval required on high-impact decisions.* --- The exposure is already inside the building. Employees are using AI whether or not IT has sanctioned it, and the cost of that gap is measurable: shadow AI adds roughly $670K to the cost of a breach it is involved in, according to IBM's 2025 research. Unsanctioned app use is widespread, and most organizations still have no policy in place to manage AI or detect shadow AI. Set against that, most enterprises are doing the riskiest possible thing: deploying AI on top of the same fragmented tools, with governance treated as something to write up later. Governing AI by design is the opposite approach, and for a CISO or compliance lead it is the only version that holds. ## Governance as architecture, not policy There are two ways to govern AI. One is to build the AI first and write the controls afterward, which leaves a gap between what the AI can technically do and what it is supposed to do. The other is to make governance part of how the AI is built, so every agent arrives already permitted, scoped, and auditable. The second is the only one that survives contact with a real enterprise, because a policy document does not stop an ungoverned agent from returning data it should not, and an audit after the fact does not undo the exposure. Governance has to be in the architecture, not in the appendix. ## Data boundaries you can defend Governing by design starts with boundaries a security team can actually stand behind: - **Your data never trains public models.** The exclusion is contractual and architectural. Calls route through governed connections under enterprise agreements, never into any third party's training. - **Permissions are enforced by the platform, not the prompt.** An agent cannot return data the user is not authorized to see, even when asked directly. The control lives in the platform, so it does not depend on how the question is phrased. - **Customer data stays separated.** No cross-customer sharing of outputs or cached results. - **PII detection and compliance dashboards.** Automatic flagging, surfaced in one console. - **Opt-in, not opt-out.** No agent is on by default. Administrators enable each one by license, role, and region. - **Human-in-the-loop for high-impact decisions.** Compensation changes, hiring and offer decisions, bulk administrative actions, and all-employee broadcasts all require explicit human approval. The tell in that list is the second item. Permissions enforced by the prompt are a suggestion. Permissions enforced by the platform are a control. ## The autonomy dial and the nested kill switch Governing by design does not mean locking AI down until it is useless. It means calibrating oversight to earned trust, and being able to stop instantly if something is wrong. ![the autonomy dial mangoapps](https://mango-cdn.b-cdn.net/marketing/uploads/the-autonomy-dial.png) The **autonomy dial** is set per business and per agent, across four levels: **Observe → Suggest → Approve → Auto** You lower the oversight burden as outcomes earn it, never before. An agent starts by observing, then suggesting, and only moves toward acting on its own once it has demonstrated it should. ![A simple diagram showing nested AI pause controls labeled platform-wide, per-business, per-app, and per-agent, with the heading 'The Kill Switch, Nested' and subtitle 'Pause AI at any level.'](https://mango-cdn.b-cdn.net/marketing/uploads/the-kill-switch-nested.png) The **kill switch** nests, so you can pause AI at any level: **Platform-wide → Per-business → Per-app → Per-agent** You are never in a position where the only options are "leave it running" or "shut everything off." A single misbehaving agent can be paused without taking down the rest. ## Why regulated buyers care For regulated buyers in healthcare, financial services, and government, the deciding fact is that AI governance is not a separate program stood up later. It is the same governance the rest of the platform already runs on, extended to AI: your data never trains public models, every agent action is audit-ready in one console, and PII detection runs automatically. That governance sits inside a platform carrying [HITRUST, SOC 2 Type II, ISO 27001, and FedRAMP ATO](https://www.mangoapps.com/security-compliance), with HIPAA-ready and GDPR posture. The compliance the enterprise already relies on does not stop at the edge of the AI. It covers it. ![shift recognized secured for enterprise](https://mango-cdn.b-cdn.net/marketing/uploads/shift_recognized-secured-for-enterprise.png) ## Governance is a stage, not a checklist The discipline shows up earliest in how agents are built. Risk review happens at design time, not after an incident, as a stage in the same [lifecycle](https://www.mangoapps.com/resources/ai-grounded-in-work) every agent moves through. Drift is tracked after launch, and agents that no longer meet the bar are retired rather than left running unmonitored. The result is simple to state and hard to fake: you can only govern AI you designed to be governed. ## The point AI deployed on a fragmented stack, with governance written afterward, is the exposure this article opened with. AI built on one platform, governed by design, is the answer to it: every agent permitted on arrival, every action auditable in one place, and a dial and a kill switch that keep a human in control. That is what governance looks like on [the AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/ai/governance). ### Get the full argument This is the governance model in short. The full chapter, the data boundaries, the autonomy dial, the kill switch, and compliance at scale, is in the book. **Download *The Employee Platform for the AI Era* (Executive Edition)** from the resource library [here](https://www.mangoapps.com/resources/employee-platform-executive-ebook), or [talk to someone who knows your industry](https://www.mangoapps.com/schedule-a-call). ## Frequently asked questions **What is AI governance in the enterprise?** AI governance is the set of controls that determine what AI agents are allowed to do, what data they can see, and how their actions are recorded and reviewed. Done well, it covers permission enforcement, data boundaries, human approval for high-impact actions, autonomy limits, and auditability. The key distinction is whether those controls are built into how the AI works or written up separately as policy after the fact. **What does "governed by design" mean?** It means governance is part of how the AI is built, not a policy added later. Every agent arrives already permitted, scoped to the right data, and auditable, because those controls are inherited from the platform rather than layered on afterward. Governance by design closes the gap between what an agent can technically do and what it is supposed to do, which is exactly the gap that policy-after-the-fact leaves open. **How do you stop AI from exposing data a user should not see?** By enforcing permissions in the platform rather than in the prompt. When the control lives in the platform, an agent cannot return data the user is not authorized to see, even if asked directly, because the restriction does not depend on how the question is worded. Prompt-based restrictions are a suggestion the model can be talked around; platform-enforced permissions are a control it cannot. **Does our data train public AI models?** On a platform governed by design, no. The exclusion is both contractual and architectural: calls route through governed connections under enterprise agreements and never enter any third party's training. Customer data also stays separated, with no cross-customer sharing of outputs or cached results. **What is an AI autonomy dial?** It is a per-business, per-agent setting that controls how much a given agent can do on its own, across four levels: observe, suggest, approve, and auto. It lets you lower the oversight burden as an agent's outcomes earn trust, and never before. High-impact decisions such as compensation, hiring, bulk actions, and all-employee broadcasts always require explicit human approval regardless of the dial. **What is an AI kill switch?** It is the ability to pause AI instantly, and a well-designed one nests: platform-wide, per-business, per-app, and per-agent. That means a single misbehaving agent can be stopped without shutting down every other agent, so you are never forced to choose between leaving a problem running and taking the whole system offline. **What is shadow AI, and why is it a risk?** Shadow AI is employees using AI tools that IT has not sanctioned or governed. It is a risk because ungoverned tools can expose sensitive data, sit outside compliance controls, and raise breach costs materially: IBM's 2025 research put the added cost of a breach involving shadow AI at roughly $670K. The underlying cause is the absence of a sanctioned, governed alternative, which is what governing AI by design provides. **How do you govern AI in a regulated industry?** By extending the compliance framework the business already runs on to the AI itself, rather than standing up a separate AI program. That means the AI inherits the platform's certifications and controls (such as HITRUST, SOC 2 Type II, ISO 27001, and FedRAMP ATO), keeps data out of public model training, records every agent action in an audit-ready console, and enforces PII detection automatically. When AI governance is the same governance as everything else, regulated buyers can defend it. **What is an AI-Ready Employee Platform?** It is an employee platform built so AI can act safely across the whole workforce, because governance is part of the architecture rather than a policy added later. Every agent inherits the platform's permissions, data boundaries, and audit visibility, and administrators control autonomy and can pause any agent at any level. MangoApps is the AI-Ready Employee Platform for the Frontline. --- # AI Grounded in Work, Not Bolted On as a Chatbot **Author:** MangoApps Team **Published:** 2026-08-06 **Category:** integrated-digital-workplace The test of a real AI platform is what is shipping. 80+ agents in production, in three types, that act on native data, not just answer. Here is how it works. *The short version: the fastest way to tell a real AI platform from a promised one is to ask what is shipping. MangoApps runs 80+ AI agents in production today, in three types, on one operating model: it watches the work, answers in the flow, acts under your rules, and stays governed end to end. Because the data is native rather than a connected copy, the agents do not just answer. They open the req, swap the shift, and close the ticket.* Most AI-at-work announcements describe a roadmap. The fastest way to tell a real AI platform from a promised one is to ask a blunt question: what is shipping today? ![A horizontal stats banner showing five metrics: 80+ production AI agents, 20+ AI capabilities across apps, 3 model providers, 5 model tiers, and 37 translation languages.](https://mango-cdn.b-cdn.net/marketing/uploads/ai-platform-promise.png) Here is the answer for a platform where AI is grounded in the work rather than bolted on: 80+ production AI agents, 20+ AI capabilities across apps, three model providers, five model tiers, and 37 translation languages. In production today, and governed on arrival, because the identity, data, and permissions the AI needs already live in one place. ## Because the data is native, the AI acts, not just answers This is the line that separates grounded AI from a chatbot. A chatbot [bolted onto fragmented tools](https://www.mangoapps.com/resources/three-approaches-enterprise-ai) can retrieve and summarize. It answers. When the AI runs on native data instead of a connected copy, it can do the thing the answer is about. It opens the requisition, swaps the shift, closes the ticket. The difference is not a better model. It is that the AI is standing on the actual record of the business, with the identity and permissions it needs to take the action attached to that record, not fetched across a brittle integration. ## One operating model behind every agent Grounded AI is not four separate products stitched together. It is one operating model that every agent runs on. It watches the work, answers in the flow, acts under your rules, and stays governed end to end. - **Intelligence watches the work.** Agents track uncovered shifts, timesheet anomalies, attendance variance, and expiring certifications, and surface what needs attention before it becomes a problem. - **Assistants answer in the flow.** Ask AI is the single front door. It answers in plain language from approved sources, scoped to each person's permissions, across web, mobile, and chat. Never the open web. - **Agents act under your rules.** Autonomous closers complete routine work: fill the open shift, clear the clean timesheet, recommend the time-off decision. Each carries a per-business autonomy dial and a full audit trail. - **Trust and governance keeps it accountable.** Every agent is engineered through a disciplined lifecycle, with permission inheritance, customer-data separation, and audit-ready visibility. ## Three types of agent, all governed on arrival ![A dashboard-style graphic titled Three Agent Types showing three cards: 73 Domain Agents, 4 Read-only Help Agents, and 3 Live Admin Agents with brief descriptions.](https://mango-cdn.b-cdn.net/marketing/uploads/three-ai-agent-types.png) The 80+ agents come in three types, and each inherits the same permissions, data boundaries, and audit visibility as the rest of the platform. You add AI, and it arrives governed. | Agent type | Count | What it does | | --- | --- | --- | | **Domain agents** | 73 | One per app or workflow area | | **Read-only help agents** | 4 | Answer questions, change nothing | | **Live admin agents** | 3 | Take governed action for administrators | The point of the split is control. A help agent that can only answer is a different risk profile from an admin agent that can act, and the platform treats them differently by design rather than hoping a prompt holds the line. ## Adaptable, and open ![Two-column marketing graphic showing MangoApps AI platform capabilities. The left panel highlights build features like Plugin AI Builder, AI Workflow Generator, AI Forms, and CLI/SDKs, while the right panel highlights connect features like standards-based MCP, bring your own model, and integrations with Claude, ChatGPT, and Gemini.](https://mango-cdn.b-cdn.net/marketing/uploads/adaptable-open-build-connect.png) Grounded AI also answers the two objections every platform evaluation raises. "It will not fit how we work" is answered by build. "We standardized on another model" is answered by connect. **Build the workflows no vendor ever shipped.** The [Plugin AI Builder](https://www.mangoapps.com/ai/capabilities) lets you describe a widget, agent, or full plugin in plain language, then review, govern, and roll it out. It inherits the platform's identity, permissions, data, and audit trail the moment it exists. The AI Workflow Generator and AI Forms build the inspection checklist, approval chain, or intake form your business actually runs on from a description, a PDF, or an image. **Connect your choice of intelligence.** Through [standards-based MCP](https://www.mangoapps.com/ai/mcp) you can connect Claude, Cursor, Codex, or any MCP-compatible agent, with hundreds of scoped, permission-aware tools. You can run on OpenAI, Anthropic, or Gemini with automatic fallback, or an approved private model. Provider choice is a setting, not a re-platform, and every external call inherits the calling user's permissions and lands in the same audit log as the internal agents. ## How the AI is built For the technical buyer, one more level of rigor. Every agent moves through the same [Agent Development Lifecycle](https://www.mangoapps.com/ai/agent-lifecycle), treated like enterprise software rather than a demo. ![the agent development lifecycle](https://mango-cdn.b-cdn.net/marketing/uploads/the-agent-development-lifecycle.png) Governance is a stage in that lifecycle, not a checklist bolted on at the end. Risk review happens at design time, not after an incident. A monitor-and-improve stage tracks override rate, quality signals, and drift, and agents that stop earning their keep are retired through the same lifecycle that launched them. Sunset, not orphan. How that governance model works in full is [its own subject](https://www.mangoapps.com/ai/governance). ## Grounded, not bolted on A chatbot bolted onto a stack of tools can talk about the work. AI grounded in the work can do it, because the identity, data, and permissions it needs are already in one place and already governed. That is the difference between AI as a feature and AI as infrastructure, and it is the whole design of [the AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/ai). ### Get the full argument This is the AI layer in short. The full chapter, every agent type, the operating model, the openness story, and the governance model, is in the book. **Download *The Employee Platform for the AI Era* (Executive Edition)** from the resource library [here](https://www.mangoapps.com/resources/employee-platform-executive-ebook), or [talk to someone who knows your industry](https://www.mangoapps.com/schedule-a-call). ## Frequently asked questions **What does "AI grounded in work" mean?** It means the AI runs directly on the platform's native data, identity, and permissions, rather than reaching into separate tools through integrations. Because the record it acts on is the real one, the AI can take action inside the business, not just describe it. Grounded AI opens the requisition or swaps the shift; a bolted-on chatbot can only tell you how. **What is the difference between an AI assistant and an AI agent?** An assistant answers questions in plain language, scoped to what the user is allowed to see. An agent takes action: it completes routine work like filling an open shift, clearing a clean timesheet, or recommending a time-off decision. Assistants answer in the flow; agents act under your rules, with an autonomy dial and an audit trail on every action. **What are the three types of AI agents?** Domain agents (one per app or workflow area, 73 in production), read-only help agents (which answer questions and change nothing, 4 in production), and live admin agents (which take governed action for administrators, 3 in production). Each type inherits the same permissions, data boundaries, and audit visibility, and each carries a different risk profile the platform enforces by design. **Can enterprise AI take action, or only answer?** It depends on what the AI stands on. AI bolted onto disconnected tools can generally only answer, because it lacks the shared identity, record, and permissions needed to act safely. AI native to one platform can act, because those things are already in place, so it can change a record and leave an auditable trail. Acting safely is an architecture question, not a model question. **Can I use my own AI model?** Yes. You can run on OpenAI, Anthropic, or Gemini with automatic fallback, or on an approved private model, and provider choice is a setting rather than a re-platform. You can also connect external MCP-compatible agents. In every case, the external call inherits the calling user's permissions and lands in the same audit log as the platform's own agents, so governance does not change when the model does. **How are AI agents kept governed?** Every agent inherits the platform's permissions, data separation, and audit visibility, and moves through a disciplined Agent Development Lifecycle with risk review at design time. Governance is built into how the agent is created rather than added afterward, so an agent arrives permitted, scoped, and auditable. The full governance model, including the autonomy dial and kill switch, is covered separately. **What is an Agent Development Lifecycle?** It is the disciplined process every agent moves through, treated like enterprise software: identifying the opportunity, designing it, setting performance and context, developing, launching, and then monitoring and improving. Governance wraps the whole lifecycle, with risk review at design time and drift tracking after launch. Agents that stop earning their keep are retired through the same lifecycle that launched them, so the AI estate is curated rather than left to sprawl. **What is an AI-Ready Employee Platform?** It is an employee platform where AI is grounded in the work rather than bolted on, because the identity, data, permissions, and governance the AI needs are shared across the whole platform from the start. That is what lets AI act safely across the entire workforce and adapt to how the business actually runs. MangoApps is the AI-Ready Employee Platform for the Frontline. --- # What "Platform" Should Actually Mean: One Identity, One Record, One Governance Model **Author:** MangoApps Team **Published:** 2026-08-06 **Category:** integrated-digital-workplace "Platform" is the most overused word in enterprise software. The test that makes it mean something, and what a CIO should check before believing it. *The short version: "platform" is the most overused word in enterprise software, because every tool now claims it. There is a simple test that makes it mean something. A real platform is a shared system, not a shared login. On a shared system, adding a capability means turning something on, with no new identity, no new data model, and no new security review. On everything else, every new capability is another project. For a CIO, that difference is the whole cost and risk story.* --- Ask ten vendors whether they sell a platform and ten will say yes. The word has been applied to so many things that it now means almost nothing. A single feature ships, and the deck calls it a platform. Rather than argue about the word, it is more useful to have a test: one question you can put to any vendor that separates the platforms from the portfolios wearing the label. This piece is that test. For a CIO it is not a semantic exercise, because the answer decides whether every future capability is a project or a switch. ## A shared system, not a shared login Here is the test. A real platform is a shared system, not a shared login. Say it as a single distinction: on a portfolio, every new capability is a new project. On a platform, it is a thing you turn on. That sounds small until you price it. "A new project" means a new identity to provision, a new permission model to map, a new data integration to build and maintain, and a new security review to clear, every single time you add a capability. "A thing you turn on" means none of that. The same word is hiding an enormous difference in cost, time, and risk, and the login screen looks identical either way. ## The layers a real platform shares Under a genuine platform, a specific set of layers is shared by every app and every agent. This is what "shared system" actually consists of. ![A platform architecture graphic showing three pillars—Employee Experience, Frontline Operations, and People Operations—supported by shared layers for identity, employee records, permissions, integrations, analytics, mobile experience, and AI governance.](https://mango-cdn.b-cdn.net/marketing/uploads/what-every-app-shares.png) | Layer | What it means | | --- | --- | | **One identity** | Single sign-on across desk and frontline | | **One permission model** | One org structure every app and every agent respects | | **One employee record** | HRIS-grade, synced with HRIS, payroll, and identity in real time | | **One analytics layer** | Every workflow measured in the same place | | **One integration fabric** | [200+ enterprise integrations](https://www.mangoapps.com/integrations) across Microsoft, Google, and HRIS systems | | **One mobile experience** | One app on the phone employees already carry | | **One AI layer and governance** | Spanning everything, with every agent governed on arrival | Add a capability and it inherits all of it. No new identity, no new permissions, no new data model, and no new security review. That last one is what a CIO feels most, because it is the step that usually turns a two-week rollout into a two-quarter project. ## Built for every employee, on every surface A real platform also meets every employee where they are: mobile, desktop, browser, digital signage, and AI experiences. None of these is the real version with the others treated as afterthoughts. They are the same platform, rendered where the work happens. ![A dark-background marketing graphic showing MangoApps available across every surface, including mobile, desktop, browser, digital signage, and AI experiences, plus support for multiple roles such as frontline, desk, manager, HR, IT, and executive.](https://mango-cdn.b-cdn.net/marketing/uploads/built-for-every-employee.png) The architecture tell is in which surface came first. Here the frontline experience was the design center, built first, for a phone with no corporate email behind it, and every other surface extends from there. That is the reverse of the usual pattern, a desktop product with a cut-down mobile view added later, and it is why reaching the frontline is not a retrofit. It is also the subject of [its own piece](https://www.mangoapps.com/resources/frontline-ai-blind-spot). Enterprise readiness belongs in the definition too, not sold on top of it. [Security and compliance](https://www.mangoapps.com/security-compliance) are part of the platform, with HITRUST, SOC 2 Type II, and ISO 27001 held in combination, and four deployment options, SaaS, private cloud, customer VPC, and on-premise, for the regulated industries and government buyers who cannot use anything less. A "platform" that cannot deploy the way a regulated buyer requires is not a platform for that buyer. ## The CIO's version of ROI There is one more reason this matters to IT specifically, and it runs against the instinct the word usually triggers. "Platform" normally implies more: more surface area to run, more to secure, more to answer for. A real platform is the opposite. It is a consolidation story. The mechanic is simple. Each app moved onto the platform is one fewer vendor, one fewer contract, one fewer SSO, and one fewer integration to maintain. ![Three side-by-side feature cards highlighting fewer attack surfaces, one governance model, and one place to audit with green security icons.](https://mango-cdn.b-cdn.net/marketing/uploads/cio-version-of-roi.png) That produces the line worth taking to the board: the stack gets smaller, not larger, every time the platform does more. It is a zero integration tax, and it shows up in the places a CIO reports on, fewer attack surfaces, one governance model, and [one place to audit](https://www.mangoapps.com/ai/governance). How that governance model actually works is a longer story than this piece needs, but at the definitional level the point holds: consolidation is the ROI. ## Apply the test before you believe the word So before you accept "platform" from any vendor, ask the one question that separates the real ones: is this a shared system, or a shared login? If adding a capability means a new project, a new identity, and a new security review, it is a portfolio wearing the word, whatever the deck says. Every capability and every agent is only as good as the foundation beneath it, which is why the foundation is the decision a CIO should make first, not last. [The AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/platform) is a shared system by design: one identity, one record, one governance model, one AI layer, and everything else built to inherit them. ### Get the full argument This is the foundation in short. The full chapter, every shared layer, every surface, and the CIO's consolidation math, is in the book. **Download *The Employee Platform for the AI Era* (Executive Edition)** from the resource library [here](https://www.mangoapps.com/resources/employee-platform-executive-ebook), or [talk to someone who knows your industry](https://www.mangoapps.com/schedule-a-call). ## Frequently asked questions **What is an employee platform?** An employee platform is a single shared system that runs every workplace app and every AI agent on one foundation: one identity, one employee record, one permission model, one analytics layer, one integration fabric, one mobile experience, and one AI and governance layer. Because those layers are shared, adding a new capability means turning it on rather than launching a separate project. That shared foundation is what distinguishes a platform from a collection of separately purchased tools. **What is the difference between a platform and a portfolio or suite?** A platform is a shared system; a portfolio or suite is a shared login. On a portfolio, each capability is a separate tool that happens to sit behind the same sign-on, so adding one is a new project with its own identity, data model, and security review. On a platform, every capability inherits one shared foundation, so adding one is a configuration step. The login screen can look identical while the architecture underneath is completely different. **What does "shared data model" mean and why does it matter?** A shared data model means every app and agent reads and writes to the same underlying record of employees, permissions, and activity, rather than keeping its own separate copy. It matters because AI and automation can only act safely and accurately when there is one authoritative version of who someone is and what they are allowed to do. Without it, each tool has a partial, possibly conflicting view, which is what produces both governance gaps and bad automation. **What makes something a real platform rather than just a shared login?** The test is whether adding a capability is a project or a switch. A real platform shares identity, permissions, data, analytics, integrations, mobile, and AI governance, so a new capability inherits all of it with no new identity, data model, or security review. A shared login only unifies the sign-on page; underneath, the tools remain separate systems that each require their own setup, integration, and governance. **What are the layers a true platform shares?** Seven: one identity (single sign-on across desk and frontline), one permission model (one org structure every app and agent respects), one employee record (HRIS-grade and synced in real time), one analytics layer, one integration fabric, one mobile experience, and one AI layer with governance over everything. When all seven are shared, any capability added later inherits them automatically. **What is the "integration tax," and how does a platform reduce it?** The integration tax is the ongoing cost of connecting and maintaining separate tools: every new app adds a vendor, a contract, an SSO configuration, and one or more integrations that must be built, monitored, and repaired over time. A real platform reduces it by consolidation: each app moved onto the platform is one fewer vendor, contract, SSO, and integration to maintain, so the stack gets smaller as the platform does more, rather than larger. **Why should a CIO care whether the foundation is shared?** Because the foundation determines cost, risk, and speed for everything that comes after. A shared foundation means fewer attack surfaces, one governance model, one place to audit, and capabilities that deploy in days rather than quarters because they skip the new identity, data mapping, and security review. An unshared foundation means each addition compounds vendor sprawl, integration maintenance, and governance gaps, which is the opposite of what a platform is supposed to deliver. **What is an AI-Ready Employee Platform?** It is an employee platform whose shared foundation, one identity, one record, one permission model, one governance layer, and one AI layer, is built so AI can act safely across the whole workforce from the start. Because the layers are shared, both new apps and new AI agents inherit the same identity, data, and governance the moment they are added. MangoApps is the AI-Ready Employee Platform for the Frontline, built as a shared system rather than a shared login. --- # Three Ways to Run AI at Work, and Why Only One Can Act **Author:** MangoApps Team **Published:** 2026-08-06 **Category:** enterprise-ai Most enterprise AI falls into three patterns, and only one can safely act, not just answer. A buyer's framework for telling them apart, with a checklist *The short version: most enterprise AI falls into one of three patterns. It is bolted onto fragmented tools, tucked inside a suite assembled by acquisition, or native to one platform. The first two can answer questions. Only the third can safely act, and only the third can adapt to how your business actually works. The way to tell them apart is not the demo. It is what the AI is allowed to stand on.* Every AI-at-work pitch looks impressive in the demo. That is the trap. A polished assistant answering questions on stage tells you almost nothing about whether it can do anything in your business once the demo ends. The question buyers keep asking is whose assistant is the smartest. It is the wrong question. The difference between these products is not how smart the assistant sounds. It is what the AI is allowed to stand on, because that decides whether it can act, or only talk. Most of the AI you will evaluate falls into one of three patterns. Here they are, and here is how to test them. ![Three side-by-side comparison panels explain different AI patterns, with the third panel highlighted in green and branded MangoApps. The graphic contrasts fragmented tools, acquired modules, and a native AI platform with governed access.](https://mango-cdn.b-cdn.net/marketing/uploads/three-approaches-to-ai.png) ## Pattern one: AI bolted onto fragmented tools The most common pattern, because it is the easiest to ship. A chatbot added to each app, or a single assistant that reaches across your existing tools through integrations. It answers questions. What it cannot do is safely act, because the context boundaries between those tools are broken and governance is stitched on after the fact. Ask it to change something and it either cannot, or it does so with no reliable way to know whether the change was allowed. This is AI sitting on top of the exact [fragmented stack](https://www.mangoapps.com/resources/ai-fragmentation-liability) that makes action unsafe in the first place, and a smarter model does not repair the foundation beneath it. ## Pattern two: AI inside a suite assembled by acquisition Harder to spot, because it looks unified from the login screen. A set of modules that share a login and a logo, but not a data model, because the suite was assembled through acquisition rather than built as one system. It answers within each module. But the AI sees only what each acquired part chooses to expose to it, so its view of the business is as fragmented as the acquisitions underneath. This is the pattern most often mistaken for the third one, so it is worth stating plainly: sharing a login is not sharing a data model. A single sign-on page can sit on top of half a dozen separate systems that never truly connect. ## Pattern three: AI native to one platform AI native to a single platform, with one identity, one record, one governance model, and one AI layer underneath everything. It sees the whole picture and acts within permissions. Because the data is native rather than a connected copy, the AI does not just find the answer. It opens the req, swaps the shift, and closes the ticket. And it is governed by design rather than after the fact, so every action it takes is permitted, scoped, and auditable from the start. How that action actually works, and how it is kept safe, are subjects of their own: [how the AI layer works](https://www.mangoapps.com/ai/architecture) and [how it is governed](https://www.mangoapps.com/ai/governance) both go deeper than this piece needs to. What matters for the comparison is the category difference. Only this pattern can act, not just answer. ## The second question the comparison implies "Which one can act" is the obvious question. There is a second one hiding underneath it: which one can adapt? Patterns one and two can only ever be what their vendors shipped. If the workflow your business runs on is not already in the product, it is not going to be. Only the third pattern can build the workflow no vendor ever shipped, and govern it the moment it exists. This is the [packaged-versus-custom tradeoff ending](https://www.mangoapps.com/resources/platform-first), seen from the AI-evaluation side. Adaptability is not a nice-to-have on the feature list. It is the difference between AI that runs your business and AI that runs the vendor's idea of your business. ## The three patterns at a glance | | Pattern 1: Bolted on | Pattern 2: Suite by acquisition | Pattern 3: Native to one platform | | --- | --- | --- | --- | | **What it is** | A chatbot per app, or one assistant reaching across silos via integrations | Modules sharing a login and a logo, not a data model | One identity, one record, one governance model, one AI layer | | **What it does** | Answers questions | Answers within each module | Sees the whole picture and acts within permissions | | **Can it act?** | No. Broken context boundaries | Only within a single module | Yes. Governed by design | | **Can it adapt?** | Only what the vendor shipped | Only what the vendor shipped | Builds workflows no vendor shipped, governed on arrival | ## How to evaluate any AI-at-work pitch The patterns give you the categories. These four questions tell you which one you are actually looking at. Run them in a trial, not a demo. 1. **What does it stand on?** A shared foundation, or a stack of tools connected by integrations? 2. **Can it act, or only answer?** Ask for an action that changes a record, not a question it can answer. 3. **Was governance designed in, or added after?** Ask where permissions are enforced: in the platform, or in the prompt. 4. **Can it adapt?** Ask it to build a workflow the vendor never shipped, and to govern it on arrival. The tell is in the gap between marketing and trial. A pattern-one or pattern-two product can pass question one on a slide and fail questions two through four the moment you ask it to do something real. Grade the trial on the questions, not the polish of the demo. ## The demo flatters the model. The foundation decides what it can do. The smartest-sounding assistant on a fragmented foundation still cannot act safely, and still cannot adapt. The demo shows you the model. The foundation determines whether that model can touch your business at all. So evaluate the foundation, not the demo. [The AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/ai) is pattern three by design: one identity, one record, one governance model, one AI layer, and AI that acts within all of it. ### Get the full argument This is the evaluation framework in short. The full breakdown of pattern three, the AI layer, the agent types, and the governance model, is in the book. **Download *The Employee Platform for the AI Era* (Executive Edition)** from the resource library [here](https://www.mangoapps.com/resources/employee-platform-executive-ebook), or [talk to someone who knows your industry](https://www.mangoapps.com/schedule-a-call). ## Frequently asked questions **What are the different approaches to AI at work?** Most enterprise AI falls into three patterns. First, AI bolted onto fragmented tools: a chatbot per app or one assistant reaching across silos through integrations. Second, AI inside a suite assembled by acquisition: modules that share a login but not a data model. Third, AI native to one platform: a single identity, record, governance model, and AI layer underneath everything. The first two can answer questions. Only the third can safely act and adapt. **What is the difference between an AI assistant that answers and an AI agent that acts?** An assistant retrieves information and responds in language. An agent changes something in the business: it opens the requisition, swaps the shift, closes the ticket. Answering only requires access to information. Acting safely requires knowing who the user is, what they are allowed to do, and where the change should be written, plus an auditable record of what was done. That is why acting requires a shared foundation and answering does not. **Why can't AI bolted onto separate tools take action safely?** Because the context it needs to act is split across tools that were never built to share it. To safely change a record, the AI has to know the user's identity, their permissions, and the correct place to write the change, then leave an audit trail. On a stack connected by integrations, those boundaries are broken and governance is added after the fact, so the AI either cannot act or acts without a reliable way to confirm the action was allowed. **Is AI inside a software suite the same as AI native to a platform?** Not necessarily, and the difference is the whole point. A suite assembled by acquisition shares a login and a logo, but its modules often do not share a data model, so the AI sees only what each acquired part exposes. A platform built as one system shares identity, data, permissions, and governance underneath everything, so the AI sees and acts across the whole picture. Sharing a login is not the same as sharing a data model. **How do you evaluate an enterprise AI vendor?** Test four things in a real trial, not a demo. One, what the AI stands on: a shared foundation or a stack of integrations. Two, whether it can act or only answer, by asking for an action that changes a record. Three, whether governance is designed in or added after, by asking where permissions are enforced, in the platform or in the prompt. Four, whether it can adapt, by asking it to build and govern a workflow the vendor never shipped. The patterns that only answer tend to pass on marketing and fail in trial. **What does "governed by design" mean compared with governance added after the fact?** Governed by design means governance is built into how the AI works, so every agent arrives already permitted, scoped, and auditable. Governance added after the fact means the AI was built first and controls were layered on later, which leaves gaps between what the AI can technically do and what it is supposed to do. The difference shows up most in whether permissions are enforced by the platform itself or merely requested in the prompt. **Which type of AI can build custom workflows?** Only AI native to one platform. Because it shares the platform's identity, permissions, data, and governance, it can build a new workflow, an agent, or a form from a plain-language description and have that workflow inherit the same controls the moment it exists. AI bolted onto fragmented tools or locked inside an acquired suite can only run the workflows its vendor already shipped, so it cannot adapt to how your business actually works. **What is an AI-Ready Employee Platform?** It is an employee platform built so AI can act safely across the entire workforce, because the foundation AI needs, one identity, one record, one permission model, one governance layer, and one AI layer, is shared from the start rather than bolted on. It is the third pattern in this comparison: AI that sees the whole picture, acts within permissions, and adapts to your business. MangoApps is the AI-Ready Employee Platform for the Frontline. --- # Why the Platform Decision Comes Before the App Decision **Author:** MangoApps Team **Published:** 2026-08-06 **Category:** integrated-digital-workplace In the AI age, choose the foundation first. A coherent platform makes AI safe, useful, and easy to expand without rework. *The short version: for most of enterprise software history, you picked the app first and the foundation came along for the ride. In the AI age that order is backwards. AI is only safe, and only genuinely useful, on a coherent foundation, so the platform decision now comes before the app decision. The good news is that choosing a platform no longer means buying everything at once. You start where it hurts most and expand on the same foundation, with no second implementation.* --- There is a quiet assumption inside most software purchases: pick the tool that best solves the problem in front of you, and the rest will sort itself out. For a long time that was fine. In the AI age it is backwards. The platform decision now comes before the app decision, and getting that order right is close to the whole game. When you buy app-first, the app you choose quietly decides your foundation for you, one purchase at a time, until you look up and find a foundation nobody actually chose. Deciding the foundation first, on purpose, is the difference between a strategy and an accident. ## The cloud already taught us this It helps to remember how enterprises actually adopted the cloud, because the pattern is the one to copy. Nobody bought every cloud service on day one. They chose a platform they trusted, started with one high-value service, and expanded service by service as they were ready. ![the cloud adoption motion](https://mango-cdn.b-cdn.net/marketing/uploads/the-cloud-adoption-motion.png) The platform decision came first. Adoption grew over time. Employee technology is now making the same move, and AI is the reason it is happening now. ## The platform decision is the AI decision, twice over Two reasons put the platform decision ahead of the app decision, and both trace back to AI. The first is safety, which [the opening piece in this series](https://www.mangoapps.com/resources/ai-fragmentation-liability) covered in full: AI can only act safely on a coherent foundation, because acting requires one identity, one record, and one place to govern. The second is the more hopeful half. When AI is native to a platform, the oldest tradeoff in enterprise software finally ends: packaged versus custom. Describe the workflow your business actually needs, and the platform builds it, on the same identity, permissions, and governance as everything else. The software adapts to the business. Thirty years of the business bending itself around the software stop. But that only works on one foundation. Point the same capability at a fragmented stack and generating new workflows just generates more fragments. Which is why the platform decision is the AI decision twice over: it is what makes AI safe, and it is what makes AI's promise real. Neither can be bought later as a feature. There is more than one way AI shows up at work, and only one pattern can actually act and adapt. That comparison deserves [its own piece](https://www.mangoapps.com/ai). The point here is simpler: all of it depends on the foundation you choose first. ## "But a platform decision sounds bigger" This is where most leaders hesitate, and the hesitation is fair. A platform decision sounds bigger than a point-tool decision. Bigger commitment, bigger risk, bigger project. In practice it is the opposite, because you do not buy it all at once. You start where it hurts most, and you expand when you are ready, on the same foundation. Platform first is not a bet-the-company migration. It is choosing the right ground before you build on it, and then building only what you need, when you need it. ## How you actually buy it The shape is simple enough to hold in your head: one foundation, three business areas, plus the workflows you build yourself. How you buy it is just as simple. Start with a single app, a [Solution Pack](https://www.mangoapps.com/apps), or a custom mix, whatever maps to the pain you have today. Then expand on the same [platform](https://www.mangoapps.com/platform), with the same identity, data, permissions, and AI already in place. ![the expansion path mangoapps](https://mango-cdn.b-cdn.net/marketing/uploads/the-expansion-path-mangoapps.png) That is what "expand without rework" actually means, and it comes down to three noes: - **No second implementation.** - **No data migration.** - **No integration tax.** Because identity, data, permissions, and AI are already shared, expansion is not a second project. It is turning on what you are ready for. The pattern shows up again and again: companies start on Employee Experience, run it for a while, then extend into operations or people on the very same platform, without re-implementing anything. ## Choose a foundation, then grow into it You will not buy every employee app at once. You should not. You choose a foundation you trust, and you grow into it. Get the order right, foundation first, and every app you add later inherits the same identity, governance, and AI. Get it wrong, app first, and you inherit whatever foundation happened to come attached to your first purchase. That is the entire case for [the AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/ai): one foundation, chosen deliberately, that everything else compounds on. ### Get the full argument This is the platform-first argument in short. The full thesis, including the three business areas, the shared foundation, and the expansion path, is in the book. **Download *The AI-Ready Employee Platform* (Executive Edition)** from the resource library, or [talk to someone who knows your industry](https://www.mangoapps.com/schedule-a-call). ## Frequently asked questions **What does "platform first" mean in enterprise software?** Platform first means choosing the foundation your software runs on before choosing individual applications, rather than the other way around. The foundation is the shared identity, data, permissions, governance, and AI layer that every app inherits. Deciding it first, on purpose, means every tool you add later fits together. Deciding it app-first means the first tool you buy quietly sets your foundation for you, by accident. **Why should the platform decision come before the app decision?** Because in the AI age the foundation determines whether AI can work at all. AI can only act safely on a coherent foundation, and AI can only deliver its real promise, software that adapts to your business, on one shared foundation. Both depend on the platform, and neither can be added later as a feature. If you pick apps first, you inherit whatever foundation came attached, which is usually fragmentation. **Why does the AI age favor platforms over point tools?** Point tools each solve one problem well but leave the data, identity, and governance split across many systems. AI needs the opposite: one coherent picture it can see and act across. On a platform, AI has that. On a stack of point tools, AI can answer questions but cannot safely act, and any new workflow it builds just adds another fragment. The shift to AI is what turned the platform-versus-point-tool question from a preference into a requirement. **Is buying a platform riskier than buying a point solution?** It sounds riskier and is usually the reverse, because you do not buy a platform all at once. You start with a single high-value app and expand on the same foundation as you are ready. A point solution feels smaller but commits you to an isolated tool that has to be integrated, governed, and eventually replaced or connected to everything else. Platform first lets you start small and avoid that accumulating cost. **How do you start small with an employee platform and expand later?** You begin with the area where the pain is greatest, a single app, a Solution Pack, or a custom mix, and get value from that. Then you turn on additional capabilities across other business areas on the same platform. Because identity, data, permissions, and AI are already shared, each expansion is a configuration step, not a new implementation. You grow into the platform at your own pace. **What does "expand without rework" mean?** It means adding new capabilities without redoing the work you have already done. Specifically, three things you would normally pay for again do not recur: there is no second implementation, no data migration, and no new integration to build. Because the foundation is shared, expansion is turning on what you are ready for, not launching a separate project each time. **How do you buy an employee platform?** Three common ways: a single app to solve one urgent need, a Solution Pack that bundles related capabilities for a business area, or a custom mix tailored to your priorities. All three run on the same foundation, so whichever you start with, you can expand from it later without re-implementing. The right starting point is wherever the pain is greatest today. **What is an AI-Ready Employee Platform?** It is an employee platform built so AI can act safely and usefully across the whole workforce, because the foundation AI needs, one identity, one record, one permission model, one governance layer, and one AI layer, is shared from the start rather than bolted on. That shared foundation is also what lets you start with one app and expand across business areas without rework. MangoApps is the AI-Ready Employee Platform for the Frontline. --- # AI at Work Is a C-Suite Decision, Not an IT Project **Author:** MangoApps Team **Published:** 2026-08-06 **Category:** enterprise-ai AI at work keeps getting handed to IT as a tooling question. The consequences land on outcomes the C-suite owns. Here is what leadership is actually deciding. *The short version: AI at work keeps getting handed to IT as a tooling question, which assistant to roll out, which model to standardize on. But the consequences land on outcomes the C-suite owns directly: security, workforce execution, retention, and the return on years of software spend. Choosing the model is a procurement question. Choosing the foundation the model stands on is a strategy question, and it belongs at the top of the house.* AI at work keeps landing on one desk by default. IT's. It arrives framed as a tooling question: which assistant do we roll out, which model do we standardize on, which copilot do we pilot first. Those are real questions. They are also being asked one or two levels below where the answer's consequences land. Because the results of this decision do not stay inside IT. They show up in security exposure, workforce execution, retention, and the return on thirty years of software spend, all outcomes the C-suite owns directly. This is not a knock on IT. It is a scoping error. A decision about the foundation of the business is being handled as a procurement task, and that mismatch is the whole problem. ## The stakes do not stay in IT ![A set of five executive role cards labeled CEO/Board, CFO, COO, CIO, and CHRO, each highlighting a different business challenge related to AI, software spend, workforce visibility, security, and retention.](https://mango-cdn.b-cdn.net/marketing/uploads/c-suite-problems.png) Look at where the consequences actually land, seat by seat. | Seat | What is actually at stake | | --- | --- | | **CEO / Board** | The gap between an AI strategy and an AI liability. | | **CFO** | Thirty years of software spend, 8 to 15 contracts per employee's workday, and transformation ROI that never landed. | | **COO** | Workforce visibility and execution, exactly where the stack goes dark. | | **CIO** | Security and governance: more tools, more attack surface, more ungoverned action. | | **CHRO** | Retention and capacity, built on an employee record that does not connect. | Every line is a top-of-house outcome. Not one of them is an IT-only concern. The rule of thumb writes itself: the person who owns the consequence should own the decision. ## Why "let IT pick a tool" breaks down The foundation decision determines whether AI can act across the business at all. That is not a thing you can settle one tool at a time. Handed down as a series of separate tool choices, it defaults to fragmentation, the exact condition [the first part of this series](https://www.mangoapps.com/resources/ai-fragmentation-liability) described, which the entire leadership team then spends the next several years governing. Nobody chose that outcome. It was the byproduct of never treating the foundation as a decision in the first place. Here is the distinction that keeps getting collapsed: choosing the model is a procurement question. Choosing the foundation the model stands on is a strategy question. When the two are treated as one, the strategy question quietly disappears into the tool selection, and the business inherits whatever foundation happened to come attached. IT is essential to evaluating and running any of this. That is not in question. What does not belong to IT alone is the decision about whether AI can touch the business at all. ## What the C-suite actually owns Not which model. The foundation the model stands on. It helps to see the real alternative clearly. It is rarely one competitor. It is a stack assembled over years: an HRIS here, a separate HCM, a workforce management tool, a learning system, a performance system, a comms app, a help desk, each from a different vendor, each a reasonable purchase on its day. No one ever chose that stack as a strategy. It accreted, one sensible decision at a time, into the thing an AI strategy now has to sit on top of. ![stack today one platform](https://mango-cdn.b-cdn.net/marketing/uploads/stack-today-one-platform.png) So the job the C-suite actually owns is narrow and decisive: turn the foundation from an accident into a decision. Made deliberately once, it compounds, because every capability added later inherits the same identity, data, and governance. Made by default, it accretes into the liability line already on the table. ## The questions to settle before the tool conversation Before the discussion turns to which assistant or which model, a leadership team can settle the decision that actually matters with a short list of questions, answered together across seats: - What does our AI actually stand on: a shared foundation, or a stack of separate systems? - Can it act across the business, or only answer within one tool? - [Who governs what it does](https://www.mangoapps.com/ai/governance), and can we see it and stop it? - Does it reach the whole workforce, or only the people at desks? That is the level a leadership team decides on, [not a feature checklist](https://www.mangoapps.com/why-mangoapps). Get those four right and the tool questions get easier. Skip them and no tool choice will save you. It is also a more bounded decision than it looks. The right foundation can be de-risked on commercial terms a CFO recognizes: an Adoption Guarantee, where employees have to actually adopt the platform or you do not pay, alongside 98% retention and an NPS of 78. Those turn a decision that feels like a bet into one with a floor under it. ## The decision belongs in the room where it lands AI at work is not a tool IT rolls out. It is a decision about the foundation of the business, and it belongs in the room where its consequences land. The case for [the AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/ai) is built to be made there: seat by seat, in the language each owner already uses, at the level the decision actually gets made. ### Get the full argument This is the ownership argument in short. The full case, laid out seat by seat for the CEO, CFO, COO, CIO, and CHRO, is in the book. It is built to be read in a leadership meeting, not skimmed at a desk. **Download *The Employee Platform for the AI Era* (Executive Edition)** from the resource library [here](https://www.mangoapps.com/resources/employee-platform-executive-ebook), or [talk to someone who knows your industry](https://www.mangoapps.com/schedule-a-call). ## Frequently asked questions **Is adopting AI at work an IT decision or a leadership decision?** It is a leadership decision. IT is essential to evaluating and running it, but the choice of foundation determines whether AI can act across the business at all, and the consequences land on outcomes the C-suite owns directly: security exposure, workforce execution, retention, and the return on years of software spend. Scoped as an IT procurement task, the strategy question disappears into the tool selection. **Who owns AI strategy in an enterprise?** The C-suite and the board own AI strategy, because AI strategy is really a decision about the foundation the business runs on, not about a single tool. The CEO owns the gap between an AI strategy and an AI liability. The CFO owns the spend and the return. The COO owns execution. The CIO owns security and governance. The CHRO owns retention and the employee record. IT executes and operates, but no single function should scope whether AI can touch the business. **Why should AI at work not be delegated entirely to IT?** Because delegating it as a series of tool choices defaults to fragmentation. The foundation decision, whether AI can act across the whole business inside one set of rules, cannot be made one tool at a time. Handed down piece by piece, it produces a stack of disconnected systems that the entire leadership team then spends years governing, which is the opposite of a strategy. **What is the difference between an AI strategy and an AI liability?** An AI strategy is a deliberate choice of foundation that lets AI act across the business safely, under governance the leadership team can see and control. An AI liability is what accretes when that choice is never made: AI deployed on top of disconnected tools, acting faster on data nobody fully governs, with no single place to audit or stop it. The same technology becomes one or the other depending entirely on the foundation beneath it. **How does the choice of AI foundation affect the CFO, COO, CIO, and CHRO?** Directly, and differently for each. The CFO carries the cost of duplicated contracts and stalled transformation ROI. The COO loses visibility exactly where the stack goes dark, on the frontline. The CIO absorbs the added attack surface and the risk of ungoverned action every new tool introduces. The CHRO tries to drive retention and capacity on an employee record split across systems that never agree. A shared foundation improves all four at once. A fragmented one degrades all four at once. **What should a leadership team decide about AI before choosing tools?** Four things, answered together: what the AI stands on (a shared foundation or a stack), whether it can act across the business or only answer within one tool, who governs it and whether it can be seen and stopped, and whether it reaches the whole workforce or only the people at desks. Settle those and the tool selection becomes straightforward. Skip them and no tool choice compensates. **What role does IT play if AI is a C-suite decision?** A central one, in execution. IT evaluates vendors, runs security review, manages integration and rollout, and operates the platform day to day. What changes is scope: IT should not be the seat that decides, alone and one tool at a time, whether AI can act across the business. That is a strategy decision the leadership team owns, with IT as an essential partner in making and running it well. **Why is choosing an employee platform a board-level decision?** Because the platform is the foundation every future AI capability inherits, and that foundation shapes outcomes the board is accountable for: risk, workforce execution, retention, and the return on software spend. Chosen deliberately, it compounds as the company adds capabilities. Chosen by default, it becomes a liability the board has to answer for later. That is why choosing an AI-Ready Employee Platform belongs on the board's agenda, not buried in a procurement cycle. --- # The Frontline Blind Spot: Why AI Strategies Miss 80% of the Workforce **Author:** MangoApps Team **Published:** 2026-08-06 **Category:** integrated-digital-workplace AI strategies fail when they only reach desk workers. The real test is whether your platform can connect, inform, and assist the frontline too. *The short version: for most companies, the AI being planned and demoed is built for the 20% of employees who sit at desks. The other 80%, the frontline workforce with no desk and no company email, stays invisible to it. Reaching them is not a feature you add later. It is an architecture decision made years before AI, and it decides whether your AI strategy reaches the whole company or only headquarters.* In the [first part of this series](https://www.mangoapps.com/resources/ai-fragmentation-liability), the problem was fragmentation across tools: the 8 to 15 disconnected systems that no AI can safely act across. Underneath that sits a second divide, older and harder to fix. Not across tools. Across people. ![A white rounded card displays the statistic "80%" in green, followed by text stating that 80% of the world’s workforce is frontline with no desk, no corporate email, and no laptop.](https://mango-cdn.b-cdn.net/marketing/uploads/80percent-share-workforce-frontline.png) Roughly 80% of the world's workforce is frontline. No desk, no company email, no laptop. They are the store, the floor, the ward, the route, and the plant. They are also where most companies make their money and meet their customers. And they are the blind spot in nearly every AI-at-work strategy being written right now, because that strategy is quietly being built for the 20% who sit down. ## The intranet is the receipt ![intranet is the clearest evidence](https://mango-cdn.b-cdn.net/marketing/uploads/intranet-is-the-clearest-evidence.png) The clearest proof that the frontline was never really reached is the tool most companies bought to reach them. The intranet was built for desks and browsers, and the numbers show who it left out. Around 1 in 3 employees never use their company intranet at all, and daily use sits near 13%. Read that as an operations problem, not an IT one. The people a company is measured on, the ones who touch the product and the customer every hour, are invisible to the systems doing the measuring. You cannot apply AI to a workforce your systems cannot see. ## Why this is now an AI problem, not a comms problem For years, missing the frontline was a communication gap you could manage with posters, shift huddles, and a manager relaying messages down the line. AI changes what is at stake, because AI is not meant only to inform. It is meant to act. The AI everyone is demoing lives inside the documents, inboxes, and meetings of desk workers. An AI approach that never reaches the store, the floor, the ward, or the route misses most of the company, and it misses it exactly where the operational risk and the margin live. The frontline is where the shift goes uncovered, the certification lapses, the safety incident happens, and the customer is won or lost. That is where AI could help most. It is also where a desk-first strategy cannot reach. The tool fragmentation from part one and the people fragmentation here are the same failure seen from two sides. Solve one without the other and you still do not have an AI strategy for the whole business. ## Reaching the frontline is an architecture decision, not a feature Most companies treat frontline access as a box to check later: ship the desktop product, bolt on a mobile view, call it done. It does not work, because reaching the frontline is decided in the architecture, years before AI enters the picture. ![A row of five rounded feature cards with icons and short descriptions, separated by plus signs, representing communications, scheduling, learning, surveys, and help desk tools.](https://mango-cdn.b-cdn.net/marketing/uploads/the-stack-enterprise-accidentally-built.png) It takes an identity model that includes hourly and deskless workers who have no corporate email. It takes a [phone-first app](https://www.mangoapps.com/solutions/employee-app) as the primary experience, not a shrunk-down version of the desktop. And it takes the everyday essentials, communication, chat, schedules, the org chart, recognition, living on the device the employee already carries in their pocket. Reach is the test. It is how you tell whether a platform was built for the whole workforce or only the half that sits down. Everything layered on top, including the AI, inherits that one decision. ## What reaching the frontline actually looks like [A.S. Watson Benelux](https://www.mangoapps.com/resources/aswatson-case-study) runs health and beauty brands including Kruidvat across 1,700 stores in four countries. That is 27,000 employees, average age around 25, almost none with a company email address. Before, schedule changes reached staff as photos posted in WhatsApp groups. The photos got lost or deleted, so employees kept coming back to the store manager to ask when they were working. Then the schedule moved onto a phone-first platform employees could open anywhere. Over 80% became active users. 16,000 Kruidvat employees now check their schedules on the mobile app, auto-translated across languages, with no training materials needed, because the app worked the way frontline staff already use their phones. > "I took a picture of the schedule and I posted it in WhatsApp. But sometimes people lost it or deleted it, so they had to come into the store or text me the night before. Now they can open the app, click on the schedule, and see when they have to work this week, or next week, or the week after that. They never contact me anymore." > — Vera Scherff, Kruidvat Store Manager, A.S. Watson Benelux None of that is a communications win. It is proof that the frontline can be reached at scale, and that reach is an architecture story rather than an adoption campaign. The pattern is not unique to Europe. In the US, [Benchmark Human Services](https://www.mangoapps.com/resources/benchmark-human-services) reached more than 4,000 frontline employees on mobile, none of them with a company email address. ## When the frontline is on the platform, AI finally reaches them Reaching the frontline matters most because of what it makes possible next. When the 80% are actually on the platform, an update published once reaches desk and frontline alike, [auto-translated](https://www.mangoapps.com/ai/translation) into each person's language, with confirmation it landed. An assistant lives in that same app and answers in plain language, scoped to exactly what each person is allowed to see. The adoption gap tells the story: frontline-first platforms routinely see 90% or higher adoption within 90 days, against the roughly 13% daily use of a legacy intranet. Only at that level of reach does AI touch the 80%, and only then can it act where the operational risk actually is. ## The real test of an AI strategy Any platform can serve the people at desks. That was never the hard part. The real test of an AI-at-work strategy is whether it reaches the 80% with no desk and no email. If it does not, it is not an AI strategy for the company. It is an AI strategy for headquarters, and the largest, most operational part of the business stays in the blind spot. That is the whole reason [the AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/ai) is built the way it is. ### Get the full argument This is the frontline chapter in short. The full case, including how the same reach carries AI to the 80%, and what the platform behind it looks like, is in the book. **Download *The Employee Platform for the AI Era* (Executive Edition)** from the resource library [here](https://www.mangoapps.com/resources/employee-platform-executive-ebook), or [talk to someone who knows your industry](https://www.mangoapps.com/schedule-a-call). ## Frequently asked questions **What is the frontline or deskless workforce?** Frontline or deskless workers are employees whose job happens away from a desk and a computer: retail store staff, nurses and aides, manufacturing and plant workers, drivers, field technicians, hospitality and warehouse teams. They typically have no company email address and no assigned laptop, and they interact with the business through a shared terminal, a manager, or their personal phone. They make up roughly 80% of the global workforce. **What percentage of the workforce is frontline?** About 80% of the world's workforce is frontline, meaning only around 20% are the desk-based, email-equipped employees that most workplace software, and now most AI, is designed around. That imbalance is why a desk-first AI strategy misses the majority of the company. **Why do AI strategies miss frontline workers?** Because most AI at work is being built inside the tools desk workers use: documents, email, meetings, and chat. Frontline employees do not live in those tools. They often have no company email to anchor an identity, no laptop to run an assistant, and a legacy intranet they rarely open. So the AI is deployed where the data and the devices already are, which is headquarters, and the 80% on the frontline are left out by default. **Why do traditional intranets fail to reach frontline employees?** Traditional intranets were designed for desks and browsers, which assumes an employee who sits down, logs in, and has a corporate account. Frontline workers rarely meet those assumptions, so the intranet becomes something they cannot easily reach and do not return to. The result shows in the numbers: around 1 in 3 employees never use their intranet, and daily use sits near 13%. **Can you deploy AI to employees who do not have a company email address?** Yes, but only if the underlying platform was built to identify and reach workers without corporate email. Company email is often used as the identity anchor for software and for AI assistants, so if that is the only way in, deskless workers are excluded structurally. A frontline-ready platform gives each employee a secure identity and a phone-first way in that does not depend on email, which is what lets AI reach them at all. **How do you reach frontline workers without corporate email?** Through a phone-first app that becomes the primary experience rather than an afterthought, backed by an identity model that includes hourly and deskless staff. The everyday reasons to open the app, schedules, communication, chat, the org chart, and recognition, live on the device the employee already carries. A.S. Watson used exactly this approach to reach 16,000 store employees who had no company email, with over 80% active adoption. **How quickly can frontline employees adopt a new workplace app?** Fast, when the app is built for how they already use their phones. Frontline-first platforms routinely reach 90% or higher adoption within 90 days. A.S. Watson saw over 80% active adoption with no training materials at all, because employees signed up and started using the app before they ever attended an onboarding session. That is the opposite of the roughly 13% daily use typical of a legacy intranet. **What makes a platform frontline-ready rather than desk-first?** Three things decided in the architecture, not added later: an identity model that includes workers without corporate email, a phone-first app that is the primary experience rather than a shrunk-down desktop, and the everyday essentials on that phone so employees have a daily reason to open it. Reach is the test. If a platform only truly serves people at desks, everything built on top of it, including AI, inherits that limit. **What is an AI-Ready Employee Platform for the frontline?** It is an employee platform designed so that AI can act safely across the entire workforce, including the 80% with no desk and no email, because reach and a shared foundation are built in from the start rather than bolted on. One identity, one record, one governance layer, and one AI layer span desk and frontline alike. MangoApps is the AI-Ready Employee Platform for the Frontline, built for exactly the workers most AI strategies leave in the blind spot. --- # Why Fragmented Tools Break Enterprise AI **Author:** MangoApps Team **Published:** 2026-08-06 **Category:** Integrated Digital Workplace Tool sprawl was a productivity tax for a decade. The moment AI is expected to act, fragmentation becomes a liability. Here is the decision leaders actually face. *The short version: for a decade, too many disconnected tools was a productivity tax you could live with. The moment AI is expected to act on your business, that same fragmentation stops being an inconvenience and becomes the thing standing between you and everything AI is supposed to deliver. The decision that matters now is not which AI model you pick. It is the foundation you ask it to stand on.* --- Every executive already knows the company has too many tools. That is not news, and it is not the problem worth your attention anymore. The problem is that the sprawl changed categories. For a decade it was a productivity tax: annoying, expensive, survivable. Then AI arrived with an expectation attached, that it would not just answer questions but act on the business, and the fragmentation you had learned to live with became the single thing standing between you and everything AI is supposed to deliver. Same stack. Different stakes. ## The promise software never kept ![A white rounded card on a dark background displays the statistic "70% of digital transformations fall short of their objectives (BCG)" in large green and black text.](https://mango-cdn.b-cdn.net/marketing/uploads/70-percent-digital-transformation.png) Before AI, enterprise software ran on a promise called digital transformation. Buy the platform, and the business gets faster, smarter, more measurable. The spend followed that promise for thirty years. The results mostly did not: roughly 70% of digital transformations fall short of their objectives, according to BCG. That failure was structural, not a matter of effort. Packaged software can only ever be as complete as its vendor makes it, and vendors build for the average of their customers, because building for each one does not scale. Your business is not the average. No business is. So a quiet inversion happened, so gradually nobody named it. The business bends to the software, instead of the software bending to the business. Requirements turn into customizations. Customizations turn into a maintenance treadmill that resets with every vendor release. And the gaps left over get filled the only way they can be: with one more tool. ## The stack nobody designed No one set out to fragment their workforce. It accreted one reasonable decision at a time. A comms tool to reach people. A scheduling tool for shifts. A learning system for compliance. A survey platform to listen. A help desk for tickets. Each was a sound choice on the day it was made. Together they became a stack nobody designed and nobody owns. ![A stat card showing the number 8–15 and the text separate tools the average employee uses to get through the day.](https://mango-cdn.b-cdn.net/marketing/uploads/8-15-separate-tools.png) The average employee now works across 8 to 15 disconnected tools to get through a single day. Every one is another login, another data silo, another permission model, another partial view of the same person. Most companies run their HR records across systems that never fully agree, so the basic facts, who works where, who reports to whom, who is certified in what, sit in three places and match in none. The clearest evidence is also the most ordinary. Excel was built for financial modeling. It became the world's task tracker, project plan, inventory list, and, in an enormous number of frontline businesses, the actual shift schedule. The most-used scheduling system on earth is a spreadsheet. That is not a quirk to laugh at. It is a measurement of how badly the work needs software that adapts to it, and how rarely it gets any. For years, all of this was an efficiency problem. You could put a number on the wasted hours and decide to live with it. What changed is not the stack. It is what now sits on top of it. ## Then the stakes changed An AI assistant on top of disconnected tools can answer a question. It cannot safely act, because it has nothing coherent to act within. The smartest model available cannot approve a shift swap, update an employee record, or assign the right training if it cannot reliably tell who the employee is and what they are allowed to do. It has no shared identity to check, no common record to write to, no single permission model to obey, and no one place where its actions can be governed and audited. A more capable model does not fix that. It makes it worse, because it acts faster on the same broken ground. You cannot govern what you cannot see, and you cannot see across tools that were never built to share. Most leadership teams are being asked to deploy AI on top of the exact fragmentation that makes AI unsafe to deploy. ## The risk is only half the cost Ungoverned action is the danger everyone can picture. The quieter cost is a ceiling. AI's deeper promise is the end of the very problem this article opened with: software that finally adapts to the business, after thirty years of the business adapting to software. Describe the workflow you actually run, and let the system build it. That is real, and it is close. But it is only collectible on a foundation coherent enough to build on. Point AI at a fragmented stack and there is nothing coherent for it to build from. It can generate a new workflow, but on a stack of separate tools, a new workflow is just one more fragment. Adaptability without a foundation is just faster fragmentation. ## The decision underneath the decision Which is why the AI conversation in most companies is aimed one level too shallow. The debate is about which model to choose, or which assistant sounds smartest in the demo. Those are real questions. They are not the deciding one. The deciding question is what your AI is being asked to stand on. A foundation, or a fault line. Make that choice deliberately and your AI can act across the whole business, inside one set of rules. Make it by accident, one tool at a time, and you will spend the next several years governing a fragmentation you never meant to build. That is a decision the C-suite owns, not a tool IT picks. It is the argument at the center of [the AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/ai), and it is [where the next part of this series begins](https://www.mangoapps.com/platform). --- ### Get the full argument This is the short version of one chapter. The full executive case, including exactly where fragmentation lands on the CEO, CFO, COO, CIO, and CHRO, and what becomes possible once the foundation is one platform instead of a stack, is in the book. **Download *The Employee Platform for the AI Era* (Executive Edition)** from the resource library [here](https://www.mangoapps.com/resources/employee-platform-executive-ebook). or [talk to someone who knows your industry](https://www.mangoapps.com/schedule-a-call). --- ## Frequently asked questions **Why does AI make tool fragmentation a bigger problem than it used to be?** Because the job of AI is different from the job of the tools that came before it. For a decade, fragmentation cost time: employees hunting across 8 to 15 systems, data that never agreed, work that fell through the gaps between apps. That was a productivity tax. AI raises the stakes because it is expected to act, not just inform, and acting safely requires a coherent picture of the business that a stack of disconnected tools cannot provide. The same fragmentation that used to waste hours now determines whether AI can do anything safely at all. **What does it mean that AI "can answer but can't act"?** Answering means retrieving information and putting it into words. Acting means changing something in the business: approving a shift swap, updating an employee record, assigning training, closing a ticket. An assistant on top of disconnected tools can usually answer, because it can read across systems and summarize. It cannot safely act, because taking action requires knowing who the person is, what they are allowed to do, and where the change should be written, and then leaving an auditable trail. On a fragmented stack, that context is split across tools that were never built to share it, so the action either cannot happen or cannot be trusted. **Can an AI assistant work across disconnected enterprise tools?** Partially. Through integrations, an assistant can retrieve and summarize across separate systems, which is enough to answer questions. It cannot reliably act across them, because each tool carries its own identity, its own permission model, and its own partial version of the same employee. Without one shared record and one set of rules underneath, the assistant has no dependable way to know whether an action is allowed, or to guarantee the change lands in the right place. Integrations move data between tools. They do not create the shared foundation that safe action needs. **Why doesn't a more capable AI model solve the fragmentation problem?** Because the problem is the ground the model stands on, not the intelligence of the model. A more capable model reasons better and acts faster, but it acts on whatever data and permissions exist beneath it. If those are fragmented, a smarter model simply takes confident action on an incoherent picture, which is worse than slow action, not better. Model capability compounds whatever foundation it runs on. On a coherent one, that is leverage. On a fragmented one, it is faster fragmentation. **How many tools does the average employee use, and why does it matter for AI?** The average employee works across roughly 8 to 15 disconnected tools to get through a single day. It matters for AI because each of those tools is a separate login, a separate data silo, a separate permission model, and a separate partial view of the same person. AI that is expected to act on behalf of that employee has to reconcile all of those views into one trustworthy answer to a simple question: who is this, and what are they allowed to do? On a stack of separate tools, there is no single place that answers it, which is why the number of tools is not just an efficiency statistic anymore. It is a measure of how hard it is to deploy AI safely. **Does reducing or consolidating tools fix the AI problem?** Fewer tools helps, but consolidation alone is not the same as a foundation. Buying a suite that shares a login and a logo still leaves you with modules that do not share a data model, so the AI sees only what each part chooses to expose. What AI needs is not fewer vendors on the invoice, it is one identity, one employee record, one permission model, and one governance layer that every capability and every agent runs on. Consolidation reduces the symptom. A shared foundation removes the cause. **What is the difference between an AI feature and an AI foundation?** An AI feature is a capability added on top of an existing tool: a chatbot in one app, a summarizer in another. It is only ever as complete as the single tool it lives inside. An AI foundation is shared underneath everything: the same identity, data, permissions, and governance that every app and every agent inherits, so AI can see the whole picture and act within one set of rules. The distinction matters because a foundation cannot be bought later as a feature. It is either architected in from the start or it is not there. **Is choosing an AI strategy an IT decision or a leadership decision?** It is a leadership decision. The choice of foundation determines whether AI can act across the business at all, and the consequences land on outcomes the C-suite owns directly: security exposure, workforce visibility, retention, and the return on years of software spend. Handed to IT and decided one tool at a time, it defaults to the same fragmentation the whole leadership team then has to govern. The model is a procurement question. The foundation is a strategy question, and it belongs at the top. **What is an AI-Ready Employee Platform?** It is an employee platform designed so that AI can act safely across the whole workforce, because the foundation it needs already exists in one place: one identity, one employee record, one permission model, one governance layer, and one AI layer, spanning desk and frontline alike. The point is that AI is not bolted on as a feature after the fact. It is grounded in the same work, data, and rules the rest of the platform runs on, which is what lets an agent do something, not just say something. MangoApps is the AI-Ready Employee Platform for the Frontline, built for the 80% of the workforce with no desk and no corporate email. --- # The Proof Problem: Why Training Records Aren't Enough **Author:** MangoApps Team **Published:** 2026-08-02 **Category:** safety-compliance Picture the moment the OSHA inspector arrives. She asks for documentation that your maintenance crew completed their confined space entry training before signing off on the SOP. # The Proof Problem: Why Training Records Aren't Enough Picture the moment the OSHA inspector arrives. She asks for documentation that your maintenance crew completed their confined space entry training before signing off on the SOP. You pull up the records. The course is marked complete. The SOP is marked done. But the quiz? Completed in under three minutes by clicking through without reading. The SOP? Signed the same afternoon they enrolled. The completion record exists. The learning almost certainly did not happen. This is the accountability gap that quietly sits underneath most workforce compliance programs. Not falsification — just the structural disconnect between the act of assigning something and the ability to prove it was meaningfully completed. Across training, communications, certifications, and frontline operations, the records say one thing. The ground truth is often another. And when something goes wrong, "we have a record of it" is not the same defense as "we can prove it happened correctly." This week's releases in MangoApps are, almost entirely, about closing that gap. --- ## The Training Layer: When Completion Has to Mean Something The most consequential change this week is in training. [Courses can now include multiple quiz lessons, and learners must pass all of them before the course marks as complete](https://www.mangoapps.com/changelog/3102). This sounds like a small increment. It is not. Most LMS platforms track completion as an event: did the learner reach the end? What this change does is tie the completion record to demonstrated knowledge. A course on forklift safety can now require a passed quiz on load limits, a passed quiz on pedestrian zones, and a passed quiz on pre-shift inspection — and the course only shows complete when a learner has cleared all three. The record means something because passing it actually required something. The companion release tightens the same loop at the operational level. [HR can now link required training courses to SOPs directly in the app; employees must complete them before the SOP can be marked done](https://www.mangoapps.com/changelog/3102). This is the integration that has been missing. You can have the best training program in the world, but if an employee can sign off on a standard operating procedure without first completing the required training, the SOP signature is theater. Linking the two means the system enforces the sequence — not a manager, not a reminder email, the system itself. For organizations using Go1's course library, [completions and progress now sync automatically back to the learner's MangoApps record](https://www.mangoapps.com/changelog/3097). This matters for audit readiness. When your training record is split across platforms, it is genuinely difficult to produce a complete picture of what an employee has learned, when, and from where. A single audit trail, regardless of content source, is a much more defensible position. The combined effect: "we trained them" becomes a claim the system can actually back up. --- ## The Documentation Layer: Proof That Lives With the Work Training records are one piece. The other piece is the documentation of work itself — the ability to show not just that something was assigned but that it was done, done correctly, and done by the right person. This week's [Verified Credentials CSV Export](https://www.mangoapps.com/changelog/3097) is a quiet but important release for any organization that bridges internal training records with external systems — apprenticeship programs, licensing boards, insurance carriers, or large contractors who require workforce qualification data before awarding work. Admins can now export a full credential file including expiry status. This is not glamorous. But it is exactly what is needed when an auditor asks for it at 4pm on a Friday. The [Before/After Photo Submissions in Contests](https://www.mangoapps.com/changelog/3097) release sits in a different application but solves the same class of problem. When contest organizers require paired before/after photo submissions, they are creating visual documentation of the full arc of work — what the situation was, what changed, and who changed it. For industries where visual proof of conditions matters (facilities, food service, construction, healthcare), this kind of documentation is valuable far beyond any recognition program. The contest is the mechanism; the audit trail is the point. The [Company Card Receipt Tracking in Mango Spend](https://www.mangoapps.com/changelog/3101) brings the same logic to finance. AI-assisted capture, receipt-to-charge matching, and a configurable approval workflow: this is about making the paper trail accurate and complete, not just present. A receipt attached to a charge after the fact is worth less than a receipt matched and approved at the moment of submission. The approval workflow — whether manager, admin, or auto-approve depending on the organization's risk tolerance — means the documentation has a verified sign-off, not just an attached image. --- ## The Communication Layer: Verifying the Message, Not Just the Response There is a third layer of accountability that is easy to overlook: the content itself. An organization can track whether employees acknowledged a message, but if the message they acknowledged was an inaccurate translation, the acknowledgement is not worth much. The responsibility doesn't end with "we sent it." The [Must-Read Translation Review](https://www.mangoapps.com/changelog/3098) release addresses this directly. Translated versions of Must-Read posts now require a reviewer's approval before they go to employees. This is a meaningful control for any organization operating across languages — and in frontline industries, that is most of them. The reviewer step means a human has verified the translation before employees are asked to acknowledge it. The acknowledgement record now has a meaningful chain behind it: the content was accurate, it was verified, and the employee confirmed receipt. The same principle runs through the [Frontline Execution campaign updates](https://www.mangoapps.com/changelog/3100): per-person acknowledgement tracking and direct CSV export of campaign data. Knowing that "86% of employees acknowledged this campaign" is useful. Knowing which specific people have not, and being able to export that list for follow-up, is what actually closes the loop. Acknowledgement tracking at the roster level is the difference between a communications metric and an operational control. And for teams managing content at scale, the [Scheduled Release Cadence with AI editorial lint](https://www.mangoapps.com/changelog/3097) adds a pre-publication check before campaigns go out. The AI review catches content issues before employees see them — tightening the loop at the source rather than cleaning up after distribution. --- ## The Bigger Picture There is a version of workforce management that is primarily about record-keeping: log the training, collect the signatures, file the certificates. That approach worked when audits were infrequent and the cost of a compliance gap was mainly a fine. The environment has changed. In regulated industries, the question is no longer "do you have a record?" but "can you prove the record reflects reality?" In operations, the question is no longer "did you send the communication?" but "can you show the right content reached the right people?" In HR, the question is no longer "did you complete the performance cycle?" but "can you demonstrate that each employee's review was timely and appropriate for their tenure?" What this week's releases share is a shift in what completion means. Courses require demonstrated knowledge, not just attendance. SOPs require prerequisite training, not just a signature. Communications require content verification, not just delivery confirmation. Credential data travels with workers into external systems. Work itself is documented visually, not just logged. This is not a trend unique to MangoApps. It reflects a broader expectation in the market that workforce software should be accountable infrastructure — not just a place to store records, but a system that enforces the conditions that make those records meaningful. The inspector will always ask. The question is whether the answer is "we have a record" or "we can show exactly what happened." --- # Frontline Operations Finally Have a Real Data Layer **Author:** MangoApps Team **Published:** 2026-07-26 **Category:** workforce-management Ask a frontline operations manager how they know whether a good shift happened. The answer usually involves checking in with supervisors, scrolling through a group chat, and trying to remember... # Frontline Operations Finally Have a Real Data Layer Ask a frontline operations manager how they know whether a good shift happened. The answer usually involves checking in with supervisors, scrolling through a group chat, and trying to remember whether the morning inspection report came back clean. The information exists — somewhere — but it lives in spreadsheets, inboxes, and people's heads. When something goes wrong, reconstructing what happened is a forensics exercise. This is the data gap that nearly every frontline organization lives with. It is not a gap you can close with another survey or a prettier dashboard. It requires something more fundamental: a place where work actually gets recorded in a structured, queryable, shareable form. This week, MangoApps shipped across several areas that all point toward closing that gap — not all at once, but in the specific, concrete ways that operational teams need. --- ## The New Data Backbone Last Monday, two new apps landed together: [Power Tables](https://www.mangoapps.com/changelog/3091) and [Live Boards](https://www.mangoapps.com/changelog/3091). Power Tables is what it sounds like — tables that scale to millions of rows, with typed columns, validation rules, row history, saved views, and a REST API. That might sound like "we built a spreadsheet," but that framing undersells what it means for operations teams. The difference between a spreadsheet and a structured data table is the difference between a conversation and a record. A spreadsheet is whatever someone typed. A Power Table is data: queryable, auditable, connected to workflows. Teams can now track anything as structured data inside MangoApps — safety incidents, maintenance tickets, customer complaints, daily checklist completions, inventory records — without exporting to a separate tool, without losing business context, and without waiting for IT to stand up a database. This week also added [CSV and Excel import for Power Tables](https://www.mangoapps.com/changelog/3094), so existing data does not have to start from scratch. Upload a spreadsheet, let the system detect column types, adjust the schema, and the data is live. For teams migrating off disconnected spreadsheets, the path just got materially shorter. Live Boards sits on top of this. Feed it a Power Table and it turns rows into ranked leaderboards, KPI stat tiles, charts, and sparklines. Those displays surface on dashboards, on Digital Signage screens in the facility, in Present mode for team meetings, and via external embeds. This week, [count aggregates were added to Live Boards](https://www.mangoapps.com/changelog/3092) — so teams can rank employees by the number of records associated with them (tickets resolved, incidents reported, leads created) without needing a separate numeric score column. The effect is that operational data which used to live in someone's tracker or a department email thread can become a shared, visible display. That changes what teams pay attention to. --- ## The Campaign-to-Completion Loop A separate thread this week addressed a different kind of operational visibility: whether frontline communication and content actually land. Content that reaches frontline workers is often the result of significant effort — safety campaigns, compliance briefings, policy updates. But most organizations have no reliable way to know whether that content reached the right person on the right day, let alone whether it was acted upon. The content goes out; what happens next is opaque. Two features this week address the full arc of that cycle. On the creation and scheduling side, [Frontline Execution: Scheduled Release Cadence](https://www.mangoapps.com/changelog/3097) gives campaign managers the ability to schedule content on a daily or weekly cadence, route it through publication approval workflows, set blackout periods, and run an AI editorial lint check before anything goes out. The result is content that moves through a governed pipeline instead of a one-off send. On the receiving side, [Frontline Execution Day Sheets](https://www.mangoapps.com/changelog/3096) give workers a structured view of every assignment they have for the day — not a notification that disappears, but a persistent record of what they need to do. Managers see the other side in a new [Reviews surface](https://www.mangoapps.com/changelog/3096) that shows campaign completion in real time, with controls to reassign incomplete items, flag blockers, and close out finished campaigns. This is the loop that most frontline communication tools are missing: not just delivery, but confirmation of delivery, and a clear path when delivery fails. --- ## Proof That the Work Happened The third thread this week was more distributed — a set of features that together answer the question: did the work actually happen, and can we prove it? [Before/after photo submissions in Contests](https://www.mangoapps.com/changelog/3096) let employees document work visually — the starting condition and the finished result, paired and timestamped. For a maintenance team completing a repair, a cleaning crew finishing a facility, or a retail team resetting a display, this is meaningful. The work leaves a record that is easy to review and hard to dispute. [Verified Credentials CSV export](https://www.mangoapps.com/changelog/3096) addresses a similar need on the qualifications side. Admins can now pull a full export of verified employee credentials from Skills & Certifications — including expiry status — and bridge that data to external training-record systems or apprenticeship programs. For any organization that needs to demonstrate workforce qualifications to a regulator, an auditor, or a partner, this export closes a gap that otherwise requires manual reconciliation every time someone asks. Count aggregates for Live Boards rounds this out at the team level. When you can rank employees by how many records they have generated — checklist items completed, customers served, incidents filed — you do not just get a leaderboard. You get a signal about who is doing the work and at what volume. That is a fundamentally different kind of workforce data than attendance or hours logged. --- ## What This Points Toward None of these features, in isolation, solves the fundamental problem that frontline operations data is fragmented and often invisible. But together — a structured data layer, a campaign-to-completion loop, and tools for documenting and verifying work — they represent a meaningful shift in what is possible. The organizations that are hardest to run are often the ones where the most work is happening but the least of it is recorded. Frontline teams generate enormous operational data every day: who was scheduled, who showed up, what tasks were completed, which communications were received, which credentials are current. Most of that data evaporates. It lives in shift logs that no one reads, in group chats that scroll out of view, in the heads of supervisors who eventually leave. When that data has somewhere to go — when it can be captured, displayed, and acted on without requiring a separate analytics stack — operations managers can stop running on instinct and start running on evidence. Not because the instinct was wrong, but because now there is something to confirm or correct it. That is what this week's releases have in common. The shift is quiet, but the direction is clear. --- # How to keep knowledge, schedules, and AI agents governed **Author:** MangoApps Team **Published:** 2026-07-21 **Category:** mango-scoop Explore institutional knowledge handoffs, a scheduling platform scorecard, and what AI agents do in workflows with audit logs. Hand-picked stories from MangoApps this week. ## Institutional Knowledge Shouldn't Leave When People Do ![Institutional Knowledge Shouldn't Leave When People Do](https://mango-cdn.b-cdn.net/images/blog-thumbnails/blog_606_20260719_140355.png) There is a moment most operations leaders know. Someone hands in their notice — not a bad actor, not a performance issue, just someone who has been around long enough to know where the bodies are... [Read the full story →](https://www.mangoapps.com/articles/institutional-knowledge-shouldn-t-leave-when-people-do) --- ### More to read #### The Schedule a Charge Nurse Can Actually Trust Build compliant clinical schedules in real time with credential checks, labor rules, and coverage visibility before shifts begin. [Read more →](https://www.mangoapps.com/articles/the-schedule-a-charge-nurse-can-actually-trust) #### 10 Questions to Evaluate Scheduling Platforms Use this scorecard to compare scheduling platforms on architecture, frontline access, AI, compliance, payroll, and security. [Read more →](https://www.mangoapps.com/articles/10-questions-to-evaluate-scheduling-platforms) #### We Already Have UKG. Do We Have to Replace It? Keep your HRIS as the source of truth and add a connected frontline execution layer on top—no rip-and-replace required. [Read more →](https://www.mangoapps.com/articles/we-already-have-ukg-do-we-have-to-replace-it) #### What AI Agents Actually Do in a Scheduling Workflow Learn how scheduling, attendance, and timekeeping agents take real action while staying governed by permissions, audit logs, and data boundaries. [Read more →](https://www.mangoapps.com/articles/what-ai-agents-actually-do-in-a-scheduling-workflow) --- ### What's New **General** — [Product Update - July 20, 2026](https://www.mangoapps.com/changelog/3091) * **[Power Tables](https://www.mangoapps.com/apps/power-tables)** — A new app that gives teams a real typed-data backbone inside MangoApps — tables that scale to millions of row... **General** — [Product Update - July 19, 2026](https://www.mangoapps.com/changelog/3090) * **[Muscle Memory Agent](https://www.mangoapps.com/ai/ask-ai)** — The Muscle Memory app now has a dedicated AI agent: employees can ask questions in plain language and get answ... --- # The Schedule a Charge Nurse Can Actually Trust **Author:** Christos Schrader **Published:** 2026-07-20 **Category:** healthcare Build compliant clinical schedules in real time with credential checks, labor rules, and coverage visibility before shifts begin. In most industries, a scheduling mistake is a headache. In healthcare, it can be a patient-safety event, an audit finding, or a coverage gap on a unit that cannot go uncovered for a single hour. The dominant problem in clinical scheduling is not building a roster. It is that assignments are gated by certification, layered with union and labor rules, and held to a coverage standard that has no tolerance for error, and the tools most nurse managers are handed treat all of that as something to reconcile afterward. A charge nurse cannot afford afterward. The schedule has to be right when it publishes, or it is a liability the moment a shift begins. ## The Assignment Has to Match the Credential, Every Time The non-negotiable in clinical scheduling is that the person in the seat holds the credential the seat requires. When certification data lives in a separate spreadsheet from the schedule, that match depends on a human remembering to check, every time, under pressure. It fails in the ordinary ways, and in healthcare the ordinary failure is the dangerous one. ![shift coverage rules staffing requirements](https://mango-cdn.b-cdn.net/marketing/uploads/shift_coverage-rules-staffing-requirements.png) The fix is to make the credential part of the build: an expired certification blocks an ineligible assignment automatically, and a nurse's certification status is visible the moment a scheduling decision is made, not discovered in an audit weeks later. The schedule refuses to put the wrong person in the seat, so the charge nurse doesn't have to catch it. ## The Rules Apply While You Build, Not After Clinical environments carry layers of rules at once: union contracts, labor law, mandatory rest between shifts, break requirements that vary by role and jurisdiction. Applied after the fact, each is a potential grievance or violation. Applied during the build, they are simply the shape the schedule takes. ![shift break planning schedule governance](https://mango-cdn.b-cdn.net/marketing/uploads/shift_break-planning-schedule-governance.png) Break rules apply to each segment as the roster is created. Approved leave updates the posted schedule immediately and flags the coverage gap it opens, so the hole surfaces days ahead instead of at 6:00 AM. And when someone calls out, the Scheduling Agent surfaces a ranked list of eligible, certified replacements sorted by fairness and overtime impact, so coverage gets filled without anyone working outside their credential or their contract. ## Coverage That Cannot Lapse The standard in healthcare is not "mostly covered." It is covered, on every unit, every hour. That requires seeing coverage in real time rather than in yesterday's numbers, catching a developing gap before the shift instead of during it, and knowing that a swap two nurses arranged holds up against certification and labor rules before it is ever published. ![shift shift marketplace](https://mango-cdn.b-cdn.net/marketing/uploads/shift_shift-marketplace.png) Coverage stops being something the charge nurse defends by hand and becomes something the system protects. ## The Security the Environment Demands ![shift recognized secured for enterprise](https://mango-cdn.b-cdn.net/marketing/uploads/shift_recognized-secured-for-enterprise.png) Clinical scheduling and attendance data sit alongside some of the most sensitive information an organization holds, so the platform has to meet the bar. MangoApps is the only unified employee platform to hold HITRUST, SOC 2 Type II, and ISO 27001 simultaneously, alongside HIPAA and the deployment controls regulated healthcare environments require. Every scheduling and timekeeping action is logged with who, when, and why, and schedules are shareable with auditors or union stewards through secure read-only links. > **See the full picture:** healthcare is one of the industries in [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book), which lays out the five gaps and where each one costs the most. ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and Shifts & Schedules is built so a clinical schedule is compliant and covered when it publishes, not audited after. Because scheduling, time, leave, and certifications share one data layer, credential status gates assignments at build time, union and labor rules apply during the build, and coverage is visible in real time. The Scheduling Agent fills call-outs from eligible, certified staff, and the Timekeeping Agent applies certification-based pay rates and catches anomalies before payroll runs. AI is the proof a connected platform matters, not the headline. None of it helps if nurses won't use it, which is why it lives on the phone clinical staff already carry, with no separate login, reaching 90%+ adoption within 90 days. Implementation runs 8 to 12 weeks with a dedicated CSM from day one. The schedule a charge nurse can trust is one that was right before it published, not one they had to double-check by hand. > **See it for a clinical environment:** we'll walk certification-gated scheduling and coverage through Shifts & Schedules. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book) - [Healthcare](https://www.mangoapps.com/industries/healthcare) - [TeamHealth case study](https://www.mangoapps.com/resources/teamhealth-case-study) --- # 10 Questions to Evaluate Scheduling Platforms **Author:** Christos Schrader **Published:** 2026-07-20 **Category:** workforce-management Use this scorecard to compare scheduling platforms on architecture, frontline access, AI, compliance, payroll, and security. The questions that matter in a scheduling evaluation are not about features. Every vendor's feature list looks similar in a demo. The questions that separate a platform that will still serve you in three years from one more system you rip out are about architecture: is it one shared data model or API-stitched modules, does it reach the frontline on the phone they already carry, does the AI act or only answer, is compliance applied at build time, and can you start small and expand without a second implementation. Ask those, of every vendor, including the one you already like. Use the list below in your own evaluation. It is written to surface the decisions a demo hides. ## Architecture The single most consequential question, because it determines everything downstream. Ask: is this one shared data model, or separate modules connected by APIs? When an approved swap happens, does coverage update everywhere instantly, or does a sync have to run? API-stitched modules drift out of step, and the drift is exactly where coverage gaps and payroll errors come from. ![shift shared data layer bedrock](https://mango-cdn.b-cdn.net/marketing/uploads/shift_shared-data-layer-bedrock.png) Then ask: when you add a capability later, is it a configuration on the platform you already own, or a new implementation? The answer tells you what expansion will actually cost you. ## Frontline access A scheduling tool the frontline won't open produces incomplete data, and incomplete data makes every dashboard a guess. Ask: does it work for employees with no corporate email, no company device, and no VPN, on the phone they already carry? And ask for a number: what is the actual adoption rate within 90 days, and what causes it? A vendor who can't answer the second question hasn't solved the first. ![shift platform capability by numbers](https://mango-cdn.b-cdn.net/marketing/uploads/shift_platform-capability-by-numbers.png) ## AI AI is on every vendor's slide, so the question is what kind. Ask: does the AI run on your own operational data and permissions, or is it a generic model bolted on top? And the sharper one: can the AI take governed action, like surfacing eligible coverage and flagging exceptions, or can it only answer questions? ![shift agents that close the work](https://mango-cdn.b-cdn.net/marketing/uploads/shift_agents-that-close-the-work.png) A chatbot that answers is not the same as an agent that acts, and only one of them takes work off your managers. ## Compliance In regulated and unionized work, this question has a cost attached to the wrong answer. Ask: are labor law, union rules, and certification requirements applied while the schedule is being built, or audited after the fact? ![shift break planning schedule governance](https://mango-cdn.b-cdn.net/marketing/uploads/shift_break-planning-schedule-governance.png) And: is every scheduling and timekeeping action logged and shareable with auditors or union stewards? Build-time enforcement prevents violations. After-the-fact auditing only discovers them. ## Payroll The handoff is where hours quietly turn into money. Ask: do reviewed, multi-rate hours export clean into payroll, or do exceptions get discovered after the run? Exceptions caught before export are corrections. Exceptions caught after are overpayments. ![shift timesheet export](https://mango-cdn.b-cdn.net/marketing/uploads/shift_timesheet-export.png) ## Expansion and security Two final questions. On expansion: can you start with one gap in one location, or does the vendor require an all-at-once rollout? A platform confident in its adoption lets you start small. On security: does it hold HITRUST, SOC 2 Type II, and ISO 27001 together, with the deployment model your environment requires? Attendance and labor data deserve the same posture as financial data. ![shift recognized secured for enterprise](https://mango-cdn.b-cdn.net/marketing/uploads/shift_recognized-secured-for-enterprise.png) ## Score your shortlist Turn the questions into a scorecard. Rate each platform you are evaluating from 1 (no) to 5 (yes, fully) on each row: one shared data model, expansion as configuration, frontline access with no corporate email or device, 90%+ adoption within 90 days, AI that runs on your data, AI that acts rather than only answers, compliance at build time, every action logged and audit-shareable, clean multi-rate payroll export, and security certifications. ![shift field service gap start](https://mango-cdn.b-cdn.net/marketing/uploads/shift_score-shortlist-card.png) A platform built on one data model, for the frontline, with AI grounded in your work, scores high across every row. A stack of point tools cannot, and the pattern of low scores clusters exactly where the architecture is stitched rather than shared. > **Get the full checklist:** the vendor questions and the scorecard come from [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book), alongside the five gaps and the cost model. ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and it is built to answer yes to every question above, which is why the list is worth running on it too. One shared data model, not API-stitched modules. Expansion as configuration, not re-implementation. Frontline access on the phone employees already carry, with 90%+ adoption within 90 days. AI that runs on your data and permissions and takes governed action through the Scheduling, Attendance, and Timekeeping agents. Compliance applied at build time and logged by default. Clean multi-rate payroll export. And HITRUST, SOC 2 Type II, and ISO 27001 held together, which no other unified employee platform does. AI is proof the architecture is right, not the headline. The questions matter because the architecture they expose is the thing you actually live with. Ask them of everyone, and let the answers, not the demo, decide. > **Run the scorecard with us:** we'll score your shortlist against the ten criteria, including this platform. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book) - [Workforce management](https://www.mangoapps.com/solutions/workforce-management) - [Platform](https://www.mangoapps.com/platform) --- # We Already Have UKG. Do We Have to Replace It? **Author:** Christos Schrader **Published:** 2026-07-20 **Category:** comparisons Keep your HRIS as the source of truth and add a connected frontline execution layer on top—no rip-and-replace required. **Quick answer:** No. You integrate. If you just invested in UKG, ADP, or Workday, that system stays exactly where it is and becomes your source of truth. MangoApps connects to it through native integration, brings shifts and hours onto a shared data layer, and runs the frontline execution layer on top. Nothing gets ripped out, and you keep the system of record you already paid for. The most common reason to do nothing is the system already in place, so it is worth answering each version of that objection honestly rather than pretending the concern isn't real. ![shift integrations api](https://mango-cdn.b-cdn.net/marketing/uploads/shift_integrations-api.png) ## "We just bought UKG. Replacing it is out of the question." Agreed, so don't. The question is not whether your HRIS is good. It is whether the frontline execution layer on top of it, the schedule managers build, the swaps they broker, the exceptions they chase, is connected to it. With 200+ integrations across UKG, ADP, Workday, Paylocity, BambooHR, and more, your existing system feeds shifts and hours onto the shared data layer, and the rest of the suite reads from it. The system of record stays. What changes is that the daily operation finally connects to it instead of running in a parallel set of spreadsheets and group texts. ## "Our schedules already work. Why change anything?" Usually the gap is not in building the schedule. It is downstream. Time off that never reaches the posted schedule. Attendance exceptions that surface weeks late in payroll. Decisions made on last week's numbers. The schedule looking fine on Monday is not the same as the cost being controlled by Friday, and the difference is exactly the part a connected data layer closes. If your schedules truly work end to end, from availability through payroll, with no manual reconciliation, you may not need this. Most operations discover the reconciliation once they look for it. ## "Will the frontline actually use it?" Yes, and the number is the answer: 90%+ adoption within 90 days. The reason is architecture, not a launch campaign. It runs on the phone employees already carry, with no separate login, no company email, and no second device. Adoption is the whole point of the platform, because the data your HRIS reports is only as complete as the frontline participation feeding it. ![shift platform capability by numbers](https://mango-cdn.b-cdn.net/marketing/uploads/shift_platform-capability-by-numbers.png) ## "Our union and compliance requirements are complex." That is an argument for a connected system, not against one. Labor law, union rules, break requirements, and certifications apply while the schedule is being built, not audited after, and every action is logged with who, when, and why for auditors or union stewards. Complexity is exactly what a build-time rules engine is for. ![shift break planning schedule governance](https://mango-cdn.b-cdn.net/marketing/uploads/shift_break-planning-schedule-governance.png) ## "Do we have to commit to the whole platform?" No. Start with the one workflow that closes your biggest gap. Because everything runs on the same platform, you expand into the next workflow as a configuration when you are ready, with users, data, and history carrying forward. No new vendor, no migration, no rebuilt integrations. The platform decision comes first, and adoption grows one app at a time. > **See the full picture:** the integration and expansion model is one part of [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book), which lays out the five gaps and the proof behind each. ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and it is designed to sit on top of the systems you already run, not replace them. Through 200+ integrations, your HRIS and payroll stay the source of truth and sync to the shared data layer in real time, so a role change or an approved swap updates coverage and eligibility everywhere at once. Because the execution layer and the record share one platform, the Scheduling, Attendance, and Timekeeping agents can act across the whole cycle rather than inside a silo. AI is proof the platform matters, not the pitch. ![shift shared data layer bedrock](https://mango-cdn.b-cdn.net/marketing/uploads/shift_shared-data-layer-bedrock.png) Keeping your system of record only pays off if the frontline uses the layer on top, which is why it lives on the phone they already carry, reaching 90%+ adoption within 90 days, on an 8-to-12-week implementation with a dedicated CSM from day one. You don't replace what you just bought. You connect it, and finally put it to work on the floor. ## Frequently asked questions **Does MangoApps replace UKG, ADP, or Workday?** While MangoApps has all the functionality required to replace these systems in many organizations, many of our customers see benefits from integrating with their legacy tools instead of ripping them out and replacing them wholesale. In such cases, those systems remain your source of truth and feed shifts and hours onto the shared data layer through native integration, so nothing gets ripped out. **How many systems does MangoApps integrate with?** More than 200, including UKG, ADP, Workday, Paylocity, BambooHR, Rippling, and Gusto, through pre-built connectors and an open API. **Do we have to roll out the whole platform at once?** No. You start with the single workflow that closes your biggest gap and expand into others as a configuration later, with users, data, and history carrying forward. No second implementation. ## Keep reading - [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book) - [Integrations](https://www.mangoapps.com/integrations) - [Platform](https://www.mangoapps.com/platform) > **Map it onto your current stack:** we'll show you keep-and-connect against your HRIS and payroll. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) --- # What AI Agents Actually Do in a Scheduling Workflow **Author:** Christos Schrader **Published:** 2026-07-20 **Category:** enterprise-ai Learn how scheduling, attendance, and timekeeping agents take real action while staying governed by permissions, audit logs, and data boundaries. In a frontline scheduling workflow in MangoApps, AI agents do three concrete things: the Scheduling Agent builds coverage and surfaces gaps before shifts begin, the Attendance Agent routes exceptions in real time, and the Timekeeping Agent catches anomalies before payroll runs. What makes them agents rather than a chatbot is that they can take governed action, not just answer questions, and what makes that safe is that they run on the same platform as the work, inheriting its permissions, data boundaries, and audit logging. If you are evaluating AI for scheduling, those two properties, real action and real governance, are the whole evaluation. A chatbot bolted onto a stack of disconnected tools can answer a question. It cannot safely act, because it cannot see across the work or be trusted with the permissions to change it. The difference below is not about a smarter model. It is about where the AI runs. ## The three agents, and what each one actually does ![shift scheduling agent](https://mango-cdn.b-cdn.net/marketing/uploads/shift_scheduling-agent.png) **The Scheduling Agent** analyzes coverage needs, availability, certifications, and history to generate a data-backed draft, so a manager never starts from a blank slate. It watches for coverage dropping below set thresholds and alerts the manager with time to act before shifts begin. And it weights preferences, seniority, and past schedules to distribute desirable and undesirable shifts fairly, which is the part managers can rarely do consistently by hand. ![shift attendance agent](https://mango-cdn.b-cdn.net/marketing/uploads/shift_attendance-agent.png) **The Attendance Agent** flags and routes late arrivals, missed punches, and unexpected absences to the responsible manager the moment they happen, not at the end of the shift. It tracks behavioral trends like escalating tardiness, so managers can act on a pattern instead of reacting to a crisis, and it routes unresolved issues through custom escalation paths by severity. ![shift automated timesheet generation](https://mango-cdn.b-cdn.net/marketing/uploads/shift_automated-timesheet-generation.png) **The Timekeeping Agent** flags punch errors, approaching overtime thresholds, and pay-rate discrepancies before data export, so corrections happen before payroll runs rather than after. It applies configured labor rules, overtime, mandatory breaks, certification-based pay rates, to every record, and it surfaces only the records that need human attention, so managers review exceptions instead of auditing clean data. ## The part that matters: autonomy is a setting None of this means handing control to a model. For each agent, you decide how far it goes on its own, along a clear spectrum: observe only, suggest, approve, or run automatically. A cautious rollout starts an agent in observe-only or suggest mode, watches how its recommendations land, and promotes it to approve or automatic once it has earned the trust. Autonomy is a configuration you own, per agent, not a property baked into the product. That is what lets a regulated operation adopt agents without betting the schedule on them. ## Governed by default, because it runs where the work runs For a technical buyer, the agents are only as trustworthy as the foundation they run on. Here every capability and every agent inherits one governed foundation. Each respects the calling user's permissions and cannot surface anything that person could not already see. Your data stays inside your boundaries and never trains public models. Every action an agent takes is logged and reviewable. And model choice is a setting, not a re-platform: you choose OpenAI, Anthropic, or Gemini, with automatic failover, so provider strategy stays in your hands. A bolted-on chatbot cannot make these claims, because it does not sit on the same identity, data, and permission model as the work it would need to act on. ![shift governance by default](https://mango-cdn.b-cdn.net/marketing/uploads/shift_governance-by-default.png) That is the real reason the platform question comes before the AI question. Agents that act safely are only possible when identity, data, permissions, and workflows already live in one place. > **See the full picture:** the AI section is one part of [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book), which lays out the five gaps a connected platform closes and the proof behind each. ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and its AI runs inside the same platform as scheduling, time, attendance, and leave. That is why the Scheduling, Attendance, and Timekeeping agents can take real action across the shift cycle rather than answer questions about it, and why every action stays inside your permissions, your data boundaries, and your audit logs. More than 20 AI capabilities and 80 specialist agents run in production today across the platform, all on one governed foundation, with provider choice built in. ![shift agents that close the work](https://mango-cdn.b-cdn.net/marketing/uploads/shift_agents-that-close-the-work.png) Governed AI still only helps if the workforce uses the system underneath it, which is why the platform lives on the phone employees already carry, reaching 90%+ adoption within 90 days. The security foundation, HITRUST, SOC 2 Type II, and ISO 27001 held together, is the same one the agents inherit. Evaluate the AI on whether it can act and whether it stays governed. On the frontline, both answers depend on the platform underneath. > **See governed agents in action:** we'll walk through the three agents, their autonomy settings, and the governance model. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book) - [Agent library](https://www.mangoapps.com/ai/agent-library) - [AI governance](https://www.mangoapps.com/ai/governance) --- # Compliance Belongs at Schedule Build Time, Not Audit Time **Author:** Christos Schrader **Published:** 2026-07-20 **Category:** workforce-management Stop finding compliance issues after the fact. Build labor rules, certifications, and break requirements into scheduling from the start. Most compliance failures on a frontline aren't decisions. Nobody chooses to skip a mandatory break, hand a shift to a nurse whose certification lapsed last week, or trip an overtime rule buried in a union contract. These things slip through, in the gap between the rules and the tool used to build the schedule. And they almost always surface the same way: late. In an audit, a grievance, a payroll correction, weeks after the shift they came from. By then the violation has already happened, and the only open question is what it costs. ## Auditing After Is the Expensive Way to Find Out An audit only tells you what already went wrong. It runs weeks after the shift, once your choices have narrowed to fixing records and hoping the exposure is small. A skipped break shows up as a payroll surprise, an expired certification as an audit finding, a labor violation as a claim, and any one of them can cost more than a year of scheduling budget. None of it is negligence. It traces back to a schedule built in a tool that never knew the rules existed. ## The Rules Belong in the Build Move the rules upstream instead, into the act of building the schedule, and a non-compliant one can't be published at all. While the manager works, the constraints are live. Labor law, union contracts, break requirements, and certification status apply as the roster takes shape, not in a review afterward. ![shift break planning schedule governance](https://mango-cdn.b-cdn.net/marketing/uploads/shift_break-planning-schedule-governance.png) An expired credential blocks an ineligible assignment on its own. Break rules, whether fixed, windowed, or flexible by role and jurisdiction, attach to each segment automatically. Approved leave lands on the posted schedule the moment it clears and flags the gap it opens, so the hole shows up days ahead instead of at 6:00 AM. Nobody asks the manager to hold every rule in their head. The build won't let them break one. That is the whole move. Compliance stops being a risk you manage and becomes a property of the schedule itself. ## Auditable by Default, Not on Request Prevention covers the violations you can stop before they happen. The rest, regulated work still has to prove, which calls for a clean record that already exists when an auditor calls, not one assembled overnight once they do. ![shift governance by default](https://mango-cdn.b-cdn.net/marketing/uploads/shift_governance-by-default.png) Every scheduling and timekeeping action logs itself with who, when, and why. Version history runs from first draft through publish. Schedules go out to auditors or union stewards as secure, read-only links. Missed breaks appear as flags in the attendance record long before they reach payroll. Build the trail into how the system works, and the audit stops being an event you brace for. It becomes a link you send. > **Read the whole argument:** compliance is one piece of [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book), which lays out the five gaps and the cost model behind each. ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and Shifts & Schedules puts compliance inside the schedule rather than a later audit. Scheduling, time, attendance, and leave all run on one shared data layer, so labor law, union rules, break requirements, and certification status apply as the schedule is created, and every action logs and shares by default. The Scheduling Agent reads that same data to catch coverage gaps and ineligible assignments before a shift publishes, and the Timekeeping Agent applies your labor rules to every timesheet before payroll runs. AI is the proof a connected platform matters, not the headline. For the security bar regulated environments set, MangoApps is the only unified employee platform holding HITRUST, SOC 2 Type II, and ISO 27001 at once. ![shift recognized secured for enterprise](https://mango-cdn.b-cdn.net/marketing/uploads/shift_recognized-secured-for-enterprise.png) None of it protects you unless the workforce actually uses it. That is why it lives on the phone employees already carry, with no separate login, and why adoption reaches 90%+ within 90 days, on an 8-to-12-week rollout with a dedicated CSM from day one. The clean audit is the one you never had to prepare for, because the schedule was already compliant the day it published. > **Move compliance into the build:** we'll show you build-time rules and the audit trail on one connected system. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book) - [Safety & compliance](https://www.mangoapps.com/solutions/safety-compliance) - [TeamHealth case study](https://www.mangoapps.com/resources/teamhealth-case-study) --- # Institutional Knowledge Shouldn't Leave When People Do **Author:** MangoApps Team **Published:** 2026-07-19 **Category:** enterprise-ai There is a moment most operations leaders know. Someone hands in their notice — not a bad actor, not a performance issue, just someone who has been around long enough to know where the bodies are... # Institutional Knowledge Shouldn't Leave When People Do There is a moment most operations leaders know. Someone hands in their notice — not a bad actor, not a performance issue, just someone who has been around long enough to know where the bodies are buried. And as you process the news, the second thought after "we need to backfill this" is: how do we replace fifteen years of knowing how things actually work here? The question is not rhetorical. It plays out across every handoff, every new hire ramp, every reorganization where two teams suddenly need to operate as one. Institutional knowledge — the real stuff, not the org chart — lives in people. In their habits, their heuristics, their ability to say "we tried that three years ago and here is why it did not work." When they leave, it walks out with them. And the organization spends the next six to twelve months slowly rediscovering what it already knew. This week's releases on MangoApps point at a different model. Not a knowledge base you have to remember to update. Not an intranet that turns into a museum six months after launch. Something closer to organizational memory that actively works — capturing knowledge at the moment of creation, making it findable by anyone who needs it, and surfacing it before people even know they need it. --- ## The Capture Problem: Documentation as Tax The reason most institutional knowledge never gets documented is not laziness. It is friction. Writing a procedure while also doing the work feels like a surcharge on expertise. Most SOPs get written after the fact — when someone leaves, when something breaks, when an auditor asks. By then, the person who knew it best is gone. [SOP Hub's new AI-assisted authoring](https://www.mangoapps.com/changelog/3048) approaches this differently. Instead of asking someone to write a procedure, it asks them to describe one — in plain language, the way they would explain it to a colleague on their first week. The AI drafts the structured document from that description. The expert reviews, adjusts, and approves. A procedure that would have taken two hours to write properly now takes five minutes. [Describe-to-Build workflow automations](https://www.mangoapps.com/changelog/3057) apply the same principle to operational logic. The unwritten rule — "when a contractor joins, do these eight things; when a full-time hire joins, do these twelve, and skip step four if they are remote" — can now become an actual automated workflow, started from a plain-language description. The admin reviews the AI-drafted steps, fills gaps, publishes. Operational knowledge becomes encoded into the system instead of staying lodged in whoever has been around long enough to know. This matters because the friction of documentation has always been its enemy. The playbooks that exist inside the heads of your most experienced operators represent enormous organizational value. The reason they stay there is that capturing them costs more than anyone wants to pay in the moment. Lower that cost far enough, and things get written down that previously would not have been. There is a compounding effect here too. When new people can follow documented procedures instead of shadowing the veteran, the veteran's time gets freed for the work only they can do. And when the veteran eventually moves on, the procedure lives in the system — not in the relationship. --- ## The Retrieval Problem: When Search Is Not Enough Most knowledge management tools have a search box. It works well if you know what you are looking for and know what it was named. Institutional knowledge does not usually cooperate on either front. The safety audit report from last year is findable if you know to search "Q3 safety audit 2025." It is not findable if you search "ladder inspection protocol" even though that is exactly what it covers. The file name and the file contents are two different things, and most search only looks at one of them. [Drive's new content search](https://www.mangoapps.com/changelog/3049) closes this gap. Search now looks inside file contents, not just filenames. The vendor contract is findable by its SLA terms. The incident report is findable by the incident type it describes. Finding a document stops depending on whoever saved it having used the right words in the title. Across a large file library, this is a meaningful change in who can find what, and how quickly. But the deeper shift this week is [Muscle Memory evolving into a standalone app with a dedicated AI agent](https://www.mangoapps.com/changelog/3057). Muscle Memory was already the place where organizations stored lessons — the things that worked, the things that did not, the decisions that looked obvious in retrospect. This week it got its own app architecture with business memory, personal memory, analytics, and settings. And then, [an AI agent on top of it](https://www.mangoapps.com/changelog/3090): employees can now ask questions in plain language and get answers drawn directly from the organization's saved lessons. The distinction between search and a queryable AI agent is worth dwelling on. Search requires knowing what you are looking for. An AI agent that answers questions from organizational memory requires only knowing what you need to know. The employee who joined six months ago does not need to know about the failed vendor relationship from 2019 to get the relevant lesson when it becomes pertinent to a decision they are making today. They just ask. The organization's experience is available to them in a way that it simply was not before. --- ## The Surface Problem: Knowledge That Shows Up Captured and queryable institutional knowledge is only useful if it surfaces where people are working. The third piece of the equation is relevance — getting the right information in front of the right person at the right moment, without requiring them to go looking for it. [News Feed topic follows and AI topic classification on comments](https://www.mangoapps.com/changelog/3054) are a step toward ambient knowledge delivery. When posts and comments are tagged by topic — with AI auto-classifying the content and hashtag support in the comment composer — employees can follow the topics that matter to their role and see relevant content surfaced higher in their personal feed. Institutional context can travel through the communication layer, not just the documentation layer. An update about a new safety protocol reaches the people for whom it is most relevant, even if they did not know to look for it. [Ask AI's new chat summary capability](https://www.mangoapps.com/changelog/3054) addresses a specific surface where knowledge decays quickly: long-running chat threads. Project channels accumulate decisions, workarounds, and institutional context that nobody catalogs, and that newcomers have to excavate through hundreds of messages to understand. Being able to ask Ask AI to summarize a chat room's recent conversation makes that accumulated context accessible without the archaeology. The new team member joining a project mid-stream can get current without reading back six months. --- ## The Bigger Picture For most of the last decade, "knowledge management" meant building a repository — a wiki, a drive, a SharePoint site — and hoping people would maintain it. Most organizations have been through at least one "fix the intranet" initiative. Most of them ended the same way: a clean structure that gradually filled with outdated content and stopped being used, because updating it was not anyone's job, and because employees learned quickly that searching it did not surface what they needed. What this week's releases suggest is a different architecture for organizational memory. One where capture is low-friction enough to happen at the moment of creation, not as a retroactive exercise. Where search looks at what information actually says, not what it was named. Where an AI layer makes knowledge queryable in natural language so that experience is available to everyone, not just the people who lived through it. And where relevant knowledge surfaces in the communication channels people already use, without requiring a separate trip to a knowledge base. Organizations with strong institutional memory make better decisions faster. They onboard new hires more effectively. They do not have to relearn the same lessons after turnover. The companies that solve this problem early build an operational advantage that compounds — because every person who joins inherits the accumulated experience of everyone who came before, rather than starting from scratch. The problem with institutional knowledge has never been that it does not exist. It is that it has always been too expensive to capture, too hard to find, and too easy to lose. The releases this week point toward a different version of that equation. --- # The Hidden Coordination Tax in Frontline Operations **Author:** Christos Schrader **Published:** 2026-07-17 **Category:** frontline-operations Disconnected systems force managers to act as the integration layer. A shared data layer removes that hidden coordination tax. There is a cost in every frontline operation that never appears on a budget, because no one issues an invoice for it. It is the tax a manager pays to move between systems. A typical frontline manager touches five to seven disconnected systems to get through a single shift cycle, from building the schedule to handing hours to payroll. Each one holds a piece of the picture and none of them talk to each other, so the manager becomes the integration layer, carrying data by hand from the scheduling tool to the availability spreadsheet to the timekeeping platform to payroll. That carrying is the coordination tax, and it is almost certainly the most expensive line item your operation doesn't track. ## What the Tax Actually Buys You Nothing. That is the point. The hours a manager spends brokering swaps over text, chasing an exception across two platforms, and re-entering the same names and numbers into a fourth system produce no coverage, no fairness, no cleaner payroll. They are pure friction, the price of systems that were each built to solve one piece well without any regard for the pieces around them. ![shift tools are the problem](https://mango-cdn.b-cdn.net/marketing/uploads/shift_tools-are-the-problem.png) Every minute of it is a minute not spent on the parts of the job that require a human: coaching, spotting problems early, being present on the floor. The tax is not just wasted time. It is the manager's actual work, crowded out. ## Why It Compounds Instead of Adding Up If the coordination tax were merely additive, you could budget around it. The trouble is that it compounds. Each new point solution added to the stack has to be reconciled against all the others, so the friction grows faster than the tool count. Add a standalone leave tracker and now leave has to be manually reconciled against the schedule and against timekeeping. Add a separate certification spreadsheet and every schedule build has to be cross-checked against it. The organization keeps buying tools to fix pieces of the problem and keeps making the coordination worse, because the problem was never the individual pieces. It was that they were separate. This is also why the usual fix, buy a better version of one of the systems, doesn't help. A better scheduling tool that still doesn't know your certification data or your leave approvals is a faster way to produce a schedule you still have to reconcile by hand. The tax lives in the gaps between systems, so no single system can remove it. ## The Only Thing That Removes It The coordination tax comes off exactly one way: by putting the pieces on a shared data layer so there are no gaps to carry data across. One identity model. One permission structure. One employee record that scheduling, time, attendance, and leave all read from and write to. When availability, certifications, overtime impact, and approved leave live in the same place the schedule is built, the reconciliation the manager used to do simply has nowhere to happen. It isn't automated. It is eliminated, because the data never has to move between systems in the first place. ![shift shared data layer bedrock](https://mango-cdn.b-cdn.net/marketing/uploads/shift_shared-data-layer-bedrock.png) And here is the part that inverts the usual math. On a shared data layer, adding a capability lowers the tax instead of raising it, because every new workflow inherits the same identity, permissions, and employee record rather than needing to be wired to everything else. The integration burden goes down with each addition, not up. That is the opposite of what a stack of point solutions does, and it is the whole argument for consolidation over accumulation. ## The Tax You Stop Paying Think about what a manager does with the hours the tax was taking. Not more administration. The floor. The team. The problem caught before it became a coverage gap. The coordination tax is worth naming precisely because once you see it as a tax, the question stops being "which tool is best" and becomes "how many systems is my management layer being forced to reconcile by hand, and what is that costing me every week." For most multi-site operations, the answer is a full operating cost hiding in plain sight. > **Read the whole argument:** the coordination tax is one of five gaps in [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book), with the cost model and the customer proof for each. ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and it is built on the one thing that removes the coordination tax: a single shared data layer. In Shifts & Schedules, scheduling, time and attendance, leave, and analytics all read from and write to one employee record, so the reconciliation between systems has nowhere left to live. You can keep the systems you already depend on, too. With 200+ integrations, an existing scheduling or payroll system feeds the shared layer rather than being replaced, so the rest of the suite reads from your source of truth. Because everything is connected, the Scheduling, Attendance, and Timekeeping agents can act across the whole cycle rather than inside one silo. AI is the proof the platform matters, not the headline. ![shift integrations api](https://mango-cdn.b-cdn.net/marketing/uploads/shift_integrations-api.png) Start with one gap, in one location, and expand when ready. Each capability you turn on inherits the same foundation, so the integration tax keeps going down. It holds because it lives on the phone employees already carry, which is how MangoApps reaches 90%+ adoption within 90 days. The coordination tax is optional. It is just the default when your systems were never built to share. > **Stop paying the coordination tax:** we'll map your five-to-seven systems onto one platform. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book) - [Platform](https://www.mangoapps.com/platform) - [Integrations](https://www.mangoapps.com/integrations) - [Workforce management](https://www.mangoapps.com/solutions/workforce-management) --- # What Scheduling Actually Costs You: Building the Business Case **Author:** Christos Schrader **Published:** 2026-07-17 **Category:** workforce-management Bad scheduling drives turnover, overtime, and manager waste. Build a simple model to quantify the real cost across your frontline operation. Every gap in a frontline operation has a price, and scattered across systems the prices are easy to miss. That is the real problem with the cost of bad scheduling: not that it is small, but that it never lands on one page. The overtime hides in payroll. The turnover hides in recruiting. The lost manager hours hide in every week that ends with the schedule still half-built. Put the numbers on a single page and the case makes itself. Here is how to build that page for your own operation. > **See the full cost model:** [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book) breaks down every gap and what it adds up to across a multi-site operation. ## Start with turnover, because scheduling drives it For a 2,000-employee multi-site operator, an illustrative annual turnover cost runs north of $4M (MangoApps model, built from the benchmarks below). The math is not exotic. Replacing one frontline worker costs roughly 40% of their annual salary once recruiting, onboarding, and lost productivity are counted (Gallup). At the 50% turnover rate common in frontline work, that is about $1M per 500 employees (Gallup), so a 2,000-person operation lands near $4M. Your real headcount and pay rates replace those inputs in minutes, but the direction doesn't change. ![shift shift schedule summary](https://mango-cdn.b-cdn.net/marketing/uploads/shift_shift-schedule-summary.png) Scheduling is the lever on that number, not a side factor. 79% of hourly workers say it is the single biggest factor in whether they stay (Work Institute, 2024), and around thirty disruptions in a year make an employee twenty percent more likely to quit (M&SOM, 2023). Which means the turnover line and the scheduling line are the same line, viewed from two departments. ## Then the overtime you can't see until it's spent ![shift labor cost financial guardrails](https://mango-cdn.b-cdn.net/marketing/uploads/shift_labor-cost-financial-guardrails.png) Overtime that is invisible until payroll runs is overtime you can only pay, never prevent. The recoverable amount depends entirely on your current overtime rate, which is exactly why it belongs in a model rather than a slogan. The mechanism is simple: overtime exposure that surfaces while the schedule is being built can be redistributed before the schedule locks. Overtime that surfaces in payroll data three weeks later can only be reconciled. Same dollars, opposite outcomes, decided by when you see the number. ## Then the manager hours nobody counts A manager moving across five to seven disconnected systems loses hours every shift cycle to brokering swaps, chasing exceptions, and re-entering data. On its own it looks like just how the job works. Across an entire management layer it is a full operating cost, and even a modest recovery per manager per week compounds fast at multi-site scale. ![shift tools are the problem](https://mango-cdn.b-cdn.net/marketing/uploads/shift_tools-are-the-problem.png) This is the cost that never appears as a line item and is often the largest, because it is measured in the thing you can least afford to waste: your managers' attention. ## Build the case on four numbers The honest version of this business case is not a fixed figure. It is a model you populate. Four inputs are enough to produce a defensible, line-item view of recoverable cost and recoverable time for your specific workforce: ![shift model it with us](https://mango-cdn.b-cdn.net/marketing/uploads/shift_model-it-with-us.png) Feed those in and the same numbers that were draining out start running the other way: lower turnover as fair, predictable scheduling drives the retention 79% of workers say depends on it; reclaimed overtime as exposure surfaces before the schedule locks; fewer payroll corrections as exceptions resolve before export; and manager hours returned to the parts of the job that actually require a manager. ## The line that belongs on the board's version There is a second page to this case, and it is the one that goes to the board. Compliance and risk avoidance rarely make the operational business case, but they dwarf it when something goes wrong. Labor law, union rules, and certification requirements applied at build time rather than audited after a problem. Every scheduling and timekeeping action logged with who, when, and why. ![shift recognized secured for enterprise](https://mango-cdn.b-cdn.net/marketing/uploads/shift_recognized-secured-for-enterprise.png) Schedules shareable with auditors or union stewards through secure read-only links. The avoided grievance, the avoided violation, and the clean audit trail don't show up as recovered dollars, but they are the difference between a normal quarter and a very expensive one. > **Model your own numbers:** bring headcount, pay rates, turnover, and overtime, and we'll build the line-item case on your real operation. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and Shifts & Schedules attacks every one of these costs at the same root by putting scheduling, time, leave, and analytics on one shared data layer. Overtime exposure is visible during the build, exceptions surface before payroll, and leaders get real-time coverage and labor cost against target instead of last week's numbers. The Scheduling, Attendance, and Timekeeping agents work that connected data to fill coverage, catch exceptions, and clean timesheets before payroll runs. AI is the proof the platform matters, not the pitch. The recovery only materializes if the frontline uses the system, which is why it lives on the phone they already carry. That is how MangoApps reaches 90%+ adoption within 90 days, on an 8-to-12-week implementation with a dedicated CSM from day one and 98% customer retention behind it. The cheapest shift cycle you'll run is the one where the costs were visible before they were spent. ## Keep reading - [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book) - [Analytics & insights](https://www.mangoapps.com/analytics-insights) - [Workforce management](https://www.mangoapps.com/solutions/workforce-management) - [Success services](https://www.mangoapps.com/success-services) --- # Why Scheduling Is Your Frontline Retention Lever **Author:** Christos Schrader **Published:** 2026-07-17 **Category:** workforce-management Scheduling is more than logistics—it’s a frontline retention lever that shapes fairness, predictability, and turnover. Most organizations file scheduling under operations. It sits with coverage and labor cost, a logistics puzzle for a manager to solve each week. That filing is the mistake. For the people actually working the shifts, the schedule is the single most important thing about the job, more than pay, more than perks. 79% of hourly workers say scheduling is the biggest factor in whether they stay (Work Institute, 2024). A schedule is not logistics. It is the primary retention lever in a frontline operation, and treating it as a spreadsheet chore is how organizations quietly bleed the workforce they spent a fortune hiring. ![shift shift schedule summary](https://mango-cdn.b-cdn.net/marketing/uploads/shift_shift-schedule-summary.png) ## The Number That Reframes Everything Sit with the 79% for a moment. It means that for most of your frontline workforce, the schedule outranks every benefit HR designs, every engagement initiative, every retention bonus. Not because those things don't matter, but because the schedule is the part of the job employees feel every single week. An erratic, opaque, last-minute schedule tells a worker their time is not respected, and they respond accordingly. Around thirty scheduling disruptions in a year make an employee twenty percent more likely to quit (M&SOM, 2023). The schedule is where the employment relationship is renegotiated, shift by shift, whether anyone at headquarters is watching or not. ## What the Logistics Framing Costs When the schedule is treated as pure logistics, its retention effect becomes invisible, and invisible costs are the ones that grow. Replacing a single frontline worker runs roughly 40% of their annual salary once recruiting, onboarding, and lost productivity are counted (Gallup). At the 50% turnover rate common in frontline work, that lands near a million dollars a year for every 500 employees (Gallup). None of that shows up on the scheduling line. It shows up in the recruiting budget, in the onboarding queue, in the productivity a fully staffed team never reaches because it is always breaking in someone new. The reverse is just as real. Engaged frontline teams show 23% higher profitability (Gallup), and a well-structured, predictable daily experience is a direct input to that engagement. The schedule is not a cost center to minimize. It is a lever that moves retention and profitability in the same pull. ## Fairness Is a Feature, Not a Virtue The instinct when scheduling gets hard is to make it faster: publish sooner, fill gaps quicker. Speed matters, but it is not what employees are responding to. They are responding to fairness and predictability, whether shifts are distributed evenly, whether the schedule reflects the availability they submitted, whether a swap they arranged actually holds. Those are properties of the system that builds the schedule, not of how hard the manager is trying. A manager working nights in a spreadsheet cannot manufacture fairness across a workforce that changes every week. The infrastructure has to carry it. ![shift employee requests availability](https://mango-cdn.b-cdn.net/marketing/uploads/shift_employee-requests-availability.png) That is the shift in thinking. Fair, predictable scheduling is not a nicety you get to once the operational fires are out. It is the operational fire, because it is the thing driving the turnover that causes most of the others. ## The Leadership Question So the question for a COO or CHRO is not "is our scheduling efficient." It is "is our scheduling retaining people." Those are different questions with different owners. Efficiency belongs to the manager. Retention belongs to leadership, and it runs straight through a schedule most leadership teams have never looked at as a retention instrument. The organizations that pull ahead are the ones that stop treating the schedule as the manager's logistics problem and start treating it as the lever it actually is. > **Read the full case:** the retention argument is one part of [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book), which lays out the five gaps and the numbers behind each. ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and Shifts & Schedules is built so fairness and predictability are properties of the system rather than acts of manager heroism. Scheduling, time, leave, and analytics share one data layer, so shifts distribute fairly, availability and certifications are respected at build time, and leaders can see coverage and labor cost in real time instead of a week late. The Scheduling Agent works that same data to build demand-aware, fairness-sorted drafts in minutes, so the schedule employees see is one they can trust. AI is the proof a connected platform matters, not the headline. ![shift platform capability by numbers](https://mango-cdn.b-cdn.net/marketing/uploads/shift_platform-capability-by-numbers.png) It changes retention only if the frontline actually uses it, which is why it lives on the phone employees already carry, with no separate login. That is how MangoApps reaches 90%+ adoption within 90 days, backed by a partnership model that earns 98% customer retention. Treat the schedule as logistics and you manage a cost. Treat it as retention and you manage the business. > **Put the retention lever on one platform:** we'll model what fair, predictable scheduling does to your turnover. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book) - [Workforce management](https://www.mangoapps.com/solutions/workforce-management) - [Employee engagement](https://www.mangoapps.com/solutions/employee-engagement) - [A.S. Watson case study](https://www.mangoapps.com/resources/aswatson-case-study) --- # The Five Information Gaps Behind Every Scheduling Failure **Author:** Christos Schrader **Published:** 2026-07-17 **Category:** workforce-management Most frontline scheduling failures trace to five information gaps. See how to spot them and close the costliest ones first. Almost every frontline operational failure - a coverage gap, an overtime surprise, a payroll error, a resignation - traces to one of five information gaps: the schedule doesn't reflect reality, time off and availability live apart from the schedule, hours get reconciled by hand after the fact, the coordination tax of moving between systems, and no real-time visibility. They are not five separate problems. They are the symptoms of a workforce asked to operate without the information infrastructure it needs. Pull on any failure and you find the same root. The shift nobody covered, the overtime nobody caught, the good employee who quietly left: the manager didn't have the information the moment they needed it, because it lived somewhere else, or nowhere. Here is each gap, and a way to tell how many are open in your own operation. ![shift 5 info gaps that drive operational problem](https://mango-cdn.b-cdn.net/marketing/uploads/shift_5-info-gaps-that-drive-operational-problem.png) ## Gap 1: The schedule doesn't reflect reality, and employees know it Built by hand across availability, certifications, demand, labor law, and fairness, schedules run late, miss credentials, and distribute shifts unevenly. Employees feel it first, and they respond the way people respond to a schedule they can't trust: they disengage, then they leave. Around thirty scheduling disruptions in a year make an employee twenty percent more likely to quit (M&SOM, 2023). ## Gap 2: Time off and availability live apart from the schedule Requests arrive by text, email, and spreadsheet, get approved in one place and forgotten in another. The posted schedule rarely reflects who is actually available, so coverage gaps appear by surprise, from information that existed the whole time in a channel the schedule couldn't see. ## Gap 3: Hours get reconciled by hand, after the fact Missed punches, attendance exceptions, and creeping overtime show up in payroll data weeks after the shift, when the only thing left to do is correct them. By the time the number is visible, the money is already spent. ## Gap 4: The coordination tax Brokering swaps, chasing exceptions, and re-entering data across five to seven disconnected systems consumes the hours managers should spend on the actual job. It rarely appears as a line item. It appears as the manager who never has time to manage. ## Gap 5: No real-time visibility Operations leaders manage on yesterday's attendance and last week's coverage numbers. Decisions made on information that is twenty-four hours behind or more are reactive by definition. You can't get ahead of a problem you can only see after it happened. ## Score your own operation The gaps are not abstractions. They show up as overtime you didn't plan, coverage you didn't see coming, and hours spent reconciling instead of managing. Mark each row honestly. ![shift how many gaps open in your operation](https://mango-cdn.b-cdn.net/marketing/uploads/shift_how-many-gaps-open-in-your-operation.png) - **Gap 1, the schedule.** When it publishes, does it already reflect real availability and current certifications, or do you correct it after someone doesn't show? *(Reflects reality at publish ←→ Corrected after the fact)* - **Gap 2, leave and availability.** Do approved time off and availability changes flow into the posted schedule automatically, or live in email, text, and a spreadsheet? *(Flows in automatically ←→ Tracked separately by hand)* - **Gap 3, attendance.** Do exceptions reach you before payroll runs, or after, when all you can do is correct them? *(Caught before payroll ←→ Surfaces weeks later)* - **Gap 4, the coordination tax.** How many separate systems does a manager touch to get through one shift cycle, schedule to payroll? *(One or two ←→ Five to seven)* - **Gap 5, visibility.** Are coverage and labor decisions made on real-time data, or on yesterday's attendance and last week's numbers? *(Real time ←→ 24 hours behind or more)* **How to read your score:** - **0 to 1 gaps open. Tuned.** Your infrastructure is doing the coordination. The work now is keeping it that way as you scale. - **2 to 3 gaps open. Quietly leaking cost.** The operation runs, but overtime, turnover, and manager hours are draining through gaps you can close. This is the most common score, and the most expensive one to leave alone. - **4 to 5 gaps open. Running on intuition.** Your managers are absorbing the work the system should be doing. Every number you are measured on, coverage, overtime, retention, is being set by tools that were never built for the job. Wherever you land, the gaps are closable, and you do not have to close all five at once. Start with the one eating the most of your managers' week. > **Get the complete playbook:** [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book) covers all five gaps, what leaving them open costs, and what closing them looks like, in one place. ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and Shifts & Schedules closes all five gaps the same way: by putting scheduling, time and attendance, leave, and analytics on one shared data layer instead of five disconnected systems. Availability and certifications are known at build time, approved leave updates the schedule automatically, exceptions surface before payroll, and leaders see real-time coverage and labor cost instead of yesterday's. Because the data is connected, the Scheduling, Attendance, and Timekeeping agents can act on it, filling coverage, routing exceptions, and cleaning timesheets before payroll runs. AI here is proof the platform matters, not the pitch. ![shift shared data layer bedrock](https://mango-cdn.b-cdn.net/marketing/uploads/shift_shared-data-layer-bedrock.png) None of it works if the frontline won't use it, which is why it lives on the phone employees already carry, with no corporate email or company device required. That is how MangoApps reaches 90%+ adoption within 90 days, on an 8-to-12-week implementation with a dedicated CSM from day one. ## Frequently asked questions **What causes most frontline scheduling problems?** Most scheduling failures trace to fragmented information rather than bad managers: schedules built without live availability or certification data, time off tracked separately from the schedule, attendance reconciled after payroll, too many disconnected systems, and no real-time visibility. When the data is scattered, managers coordinate by hand and problems surface too late to prevent. **How many systems does a frontline manager actually use?** A typical frontline manager touches five to seven disconnected systems to get through one shift cycle, from building the schedule to handing hours to payroll (MangoApps). The switching itself, re-entering and reconciling across those systems, is what the coordination tax measures. **How do you fix scheduling problems without replacing everything?** You don't have to. Start with the single gap eating the most manager time, connect the systems you already run onto a shared data layer, and expand when ready. Closing one gap well beats a big-bang replacement. **Does this work for employees without a corporate email or company device?** Yes. The platform reaches frontline employees on the personal phone they already carry, onboarded by SMS invite or a QR code at the location, which is what makes adoption hold across the whole workforce rather than just the office. ## Keep reading - [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book) - [Workforce management](https://www.mangoapps.com/solutions/workforce-management) - [Analytics & insights](https://www.mangoapps.com/analytics-insights) - [Raley's case study](https://www.mangoapps.com/resources/raleys-case-study) > **Score your operation with us:** we'll run the five-gap assessment against your real shift cycle. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) --- # The Frontline Manager Has a Group Text and a Gut Feeling **Author:** Christos Schrader **Published:** 2026-07-17 **Category:** workforce-management Frontline managers juggle call-outs, swaps, attendance, and payroll across disconnected tools. One connected system turns chaos into control. There is a version of the frontline operations manager's job that exists on paper: build a compliant schedule, keep coverage consistent, track attendance, approve time off, hold labor cost in line. Then there is the version that actually exists. Schedules built in spreadsheets that don't know what certifications anyone holds. Swaps brokered over text and half-approved. Time-off requests that never reach the posted schedule. Attendance exceptions that surface in payroll data three weeks after the shift. The manager's primary source of real-time information is a group text. That gap, between the job on paper and the job in practice, is the whole story, and it plays out the same way every Tuesday. ## The Day, As It Actually Runs **6:47 AM.** A supervisor opens their phone to three texts: a call-out, a swap request, and a manager asking for coverage numbers. They open a spreadsheet, cross-reference last Tuesday, and start making calls, not sure whether the replacement holds the mandatory forklift certification. **9:30 AM.** A swap two employees arranged over text last night still needs to go into the schedule. Was it approved? Does the covering employee have the right certification? Did it just push someone into overtime? Nobody is sure. **11:15 AM.** A near-miss on the floor. The supervisor fills out a paper incident form and leaves it for the coordinator to type in tomorrow. Corrective action waits for next week's meeting. **2:00 PM.** End of shift. The supervisor cross-references two different timekeeping platforms by hand to fix missing punches and overtime discrepancies, losing an hour to administration. ![shift tools are the problem](https://mango-cdn.b-cdn.net/marketing/uploads/shift_tools-are-the-problem.png) None of this is a competence problem. It is a tooling problem. A typical frontline manager touches five to seven disconnected systems to get through a single shift cycle, from building the schedule to handing hours to payroll. And schedule volatility isn't free: around thirty scheduling disruptions in a year make an employee twenty percent more likely to quit (M&SOM, 2023). The group text isn't the manager being disorganized. It is the only real-time system they were ever given. ## The Same Day, Rebuilt Same supervisor, same four moments, same Tuesday. The difference is not a better mood or a lighter load. It is that the infrastructure now does the coordination the manager used to do by hand. **6:47 AM.** The call-out comes in. Instead of a spreadsheet and a phone tree, the supervisor sees a ranked list of eligible, certified replacements, already sorted by fairness history and overtime impact. The forklift certification is confirmed before the name appears. Coverage is filled in two taps and the schedule updates for everyone at once. ![shift scheduling agent](https://mango-cdn.b-cdn.net/marketing/uploads/shift_scheduling-agent.png) **9:30 AM.** The swap from last night is not a loose end. It was checked against role, location, and certification rules when it was requested and is already in the published schedule. Nobody got pushed into overtime by accident. No chase, no text chain. **11:15 AM.** The near-miss gets logged on the phone at the point of work and routes instantly to the right manager with the shift, employee record, and location attached. The corrective action starts today, not in four days. **2:00 PM.** No cross-referencing two platforms. Hours were compiled as they happened, exceptions flagged in real time, and only the records that genuinely need a human decision wait for sign-off. The pay period ends clean. ## What Actually Changed The work didn't get smaller. The coordination moved off the manager. That is the entire difference between the two Tuesdays, and it is why the schedule deserves to be treated as infrastructure rather than a chore someone squeezes in between shifts. When the system knows who is certified, who is available, and what a swap does to overtime before the swap is approved, the manager stops being a human integration layer between five systems and gets to spend the day on the parts of the job that actually require a manager. The schedule is the most operational document in the building. The question is whether your managers are running it, or running around it. > **Read the whole picture:** this is one Tuesday. [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book) lays out the five gaps behind it, the cost model, and the customer proof. ## Where MangoApps Fits ![shift shared data layer bedrock](https://mango-cdn.b-cdn.net/marketing/uploads/shift_shared-data-layer-bedrock.png) MangoApps is the Enterprise Workforce Platform Built for the Frontline, and Shifts & Schedules gives managers the infrastructure the job always assumed they had. Scheduling, time and attendance, leave, and analytics run on one shared data layer, so availability, certifications, and overtime impact are known at the moment a schedule or a swap is built, not discovered in payroll weeks later. The Scheduling Agent reads that same connected data to surface a ranked, certified, fairness-sorted list of replacements when someone calls out. The AI is not the headline. It is what one data layer makes possible. The reason it holds on the floor is that it lives on the phone employees already carry, with no separate login, which is why MangoApps reaches 90%+ adoption within 90 days. Implementations run 8 to 12 weeks with a dedicated Customer Success Manager from day one, the same partnership behind 98% customer retention. The first shift cycle on the platform is calmer than the last one off it, because the system finally does the coordinating. > **Trade the group text for infrastructure:** we'll map your Tuesday against one connected system. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*AI Scheduling for Shift-Based Teams*](https://www.mangoapps.com/resources/shifts-schedules-book) - [Workforce management](https://www.mangoapps.com/solutions/workforce-management) - [A.S. Watson case study](https://www.mangoapps.com/resources/aswatson-case-study) - [Analytics & insights](https://www.mangoapps.com/analytics-insights) --- # How to close the accountability loop and fix review data gaps **Author:** MangoApps Team **Published:** 2026-07-14 **Category:** mango-scoop Learn why frontline "received" doesn't mean "done," the four info gaps behind performance failure, plus July 13 SCORM training. Hand-picked stories from MangoApps this week. ## From Sent to Certain: Closing the Frontline Accountability Loop ![From Sent to Certain: Closing the Frontline Accountability Loop](https://mango-cdn.b-cdn.net/images/blog-thumbnails/blog_581_20260712_140410.png) A store manager sends out the new food safety SOP on Tuesday. By Thursday, everyone on the shift roster has technically "received" it — the email delivered, the notification fired, the document is... [Read the full story →](https://www.mangoapps.com/articles/from-sent-to-certain-closing-the-frontline-accountability-loop) --- ### More to read #### Homepage Goals Get Talked About; Deck Goals Don't Goals only work when employees can see them. Learn how visible OKRs improve alignment, engagement, and performance reviews. [Read more →](https://www.mangoapps.com/articles/homepage-goals-get-talked-about) #### What Performance Really Costs: 3,000 to 4,000 Hours a Year Assembling Review Data Performance management costs more than software—hidden in manager hours, turnover, and stale data. See where the real cost adds up. [Read more →](https://www.mangoapps.com/articles/what-performance-really-costs) #### The Four Information Gaps Behind Every Performance Failure Performance, goals, succession, and skills fail when data is fragmented. Learn how to spot and close the four gaps before they get expensive. [Read more →](https://www.mangoapps.com/articles/four-information-gaps-behind-every-performance-failure) #### A Year in the Life of a Review Cycle, and Why It Changes Nothing Performance reviews break when goals, feedback, and skills live in separate systems. A shared data layer makes the full picture available all year. [Read more →](https://www.mangoapps.com/articles/a-year-in-the-life-of-a-review-cycle) --- ### What's New **General** — [Product Update - July 13, 2026](https://www.mangoapps.com/changelog/3050) * **[Self-Paced Courses with SCORM](https://www.mangoapps.com/directory/app/training)** — Training now supports self-paced courses with SCORM package uploads, giving learners fu... **General** — [Product Update - July 12, 2026](https://www.mangoapps.com/changelog/3049) * **[Drive: File Comments](https://www.mangoapps.com/directory/app/drive)** — Team members can now leave threaded comments on any file in Drive, enabling collaborative review an... --- # Your Performance Data Is Only as Good as Your Adoption **Author:** Christos Schrader **Published:** 2026-07-14 **Category:** Best Practices Performance data is only trustworthy when employees actually use the system. Adoption is the prerequisite for real insights, especially on the frontline. Every performance platform demo looks the same: clean dashboards, retention-risk scores, succession pipelines, engagement trends. What the demo never shows is the assumption underneath all of it, which is that people actually used the system. A retention-risk score built on data half the workforce never entered is not an insight. It is a guess with a progress bar. The best-designed performance system in the category produces nothing if employees don't open it, which is why adoption, not features, is the number that decides whether any of the rest is real. ![90 percent adoption follows](https://mango-cdn.b-cdn.net/marketing/uploads/90-percent-adoption-follows.png) ## Adoption is the prerequisite, not the postscript Talent leaders tend to treat adoption as something you worry about after you choose the platform. It is the other way around. Adoption is what determines whether the data you're about to make decisions on is complete or hollow. A review built from a full year of real inputs is trustworthy. A review built from the fraction of data that made it into a system people avoided is the same night-before reconstruction you were trying to escape, just with a nicer interface. The dashboards are downstream of adoption. If the adoption isn't there, neither is the insight. This is the trap of the deskbound HR tool: it works for the corporate layer that lives at a computer and quietly excludes the frontline, which is often most of the workforce. Whatever the tool measures, it measures a slice, and every organizational number it produces is skewed by who was never in it. ## Why the frontline is the hard part, and how it gets solved The reason adoption usually fails on the frontline is friction: a separate login, a corporate email nobody has, a company device nobody was issued, one more app to remember for a workforce already stretched. Remove the friction and adoption follows. The version that works puts performance inside the app employees already open for company news, their schedule, and their team, reachable on a personal device through a branded app, onboarded by SMS invite or a QR code at the location. No separate login. No new behavior. The self-assessment and the OKR check-in appear where the person already is. ![structured review cycles](https://mango-cdn.b-cdn.net/marketing/uploads/structured-review-cycles.png) That is why adoption can hit 90% within 90 days: the review process meets employees where they already are instead of asking them to go somewhere new. And it is why the data that flows into reviews is trustworthy, because people used the system all year rather than the week before. ## What the first 90 days actually looks like ![Three informational panels highlight automated OKR review cycles, 90%+ platform adoption within 90 days, and compensation cycles grounded in a full year of visible data.](https://mango-cdn.b-cdn.net/marketing/uploads/90-day-markers-that-matter.png) Adoption at that level is not luck. It is a delivery model. Implementations run 8 to 12 weeks with a named Customer Success Manager assigned before the contract is signed, the same partnership approach behind 98% customer retention and an NPS of 78. The rollout is staged: configure the cadences and settings, pilot with one business unit, launch to the full workforce through push, email, and SMS, then run the first cycle live with the picture already assembled. Existing systems keep running the whole time. Nothing goes dark while the data layer comes online underneath. > **Read the whole argument:** adoption is the thread through [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book), which lays out the four gaps a connected platform closes and why the data is only trustworthy when people use it. ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and adoption is the whole point of that positioning. Performance lives in the same app employees already use, so the Performance & Learning suite gets the participation that makes its data worth acting on, and the AI built across the suite runs on complete data rather than a fraction. AI is only as good as the record beneath it, and the record is only as good as adoption. That is the chain the whole platform is built to protect. ![proven at enterprise scale](https://mango-cdn.b-cdn.net/marketing/uploads/proven-at-enterprise-scale.png) Which is why MangoApps is willing to stand behind it. The Adoption Guarantee is simple: if your employees don't adopt MangoApps after launch, you don't pay. No other vendor in this category backs their product this way, because no other vendor has built specifically for the workforce where adoption is hardest. Choose your platform on the number that determines whether every other number is true. > **See what 90% in 90 days takes:** we'll walk you through the implementation model, the named-CSM partnership, and the Adoption Guarantee. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book) - [Success services](https://www.mangoapps.com/success-services) - [Performance & learning](https://www.mangoapps.com/solutions/performance-learning) --- # We Only Need One Capability Right Now. Are We Locked Into a Platform? **Author:** Christos Schrader **Published:** 2026-07-14 **Category:** Best Practices Start with one capability, then expand when ready—without redoing integrations or replacing your HRIS, payroll, or LMS. **Quick answer:** No. You start with the one capability that closes your biggest gap, reviews, goals, succession, or skills, and the platform foundation comes with it whether you use the rest or not. Adding a second capability later is a business area turned on, not a new implementation, and you don't redo your integration work to do it. The fear behind the question is real, though, so it's worth answering properly rather than just asserting the "no." ![four cababilities one data layer](https://mango-cdn.b-cdn.net/marketing/uploads/four-cababilities-one-data-layer.png) ## The fear is rip-and-replace, and that's not what's on offer When a talent leader hears "platform," they hear a project: replace the HRIS, replace payroll, replace the LMS, all at once, on a vendor's timeline, with everything at risk simultaneously. No serious organization does that, and it isn't what adopting MangoApps means. The platform is designed to work alongside what you already run, bring your existing systems onto a shared data layer, and let you consolidate later only if and when it makes sense for you. There are three ways in, and every customer has taken one of them. ## Three paths in - **Keep and connect.** Your HRIS, payroll, and identity systems stay exactly where they are. MangoApps integrates with Workday, SAP SuccessFactors, UKG, ADP, BambooHR, and [200+ other enterprise systems](https://www.mangoapps.com/integrations) through pre-built connectors and an open API. Employee records sync in real time, so a role change in your HRIS updates review-cycle assignment and succession eligibility automatically. The data layer connects and nothing has to move. This is where most organizations start. ![shared data layer](https://mango-cdn.b-cdn.net/marketing/uploads/shared-data-layer.png) - **Migrate when ready.** When a standalone LMS or a legacy performance tool stops justifying its cost, you can move that workflow onto MangoApps at any stage. The platform already holds the employee record, the permissions, and the integrations, so migrating a point solution is a business area turned on, not a project restarted. - **Start net new.** For organizations without a mature HRIS, or replacing legacy infrastructure outright, MangoApps can be the system of record: reviews, skills, succession, OKRs, and the employee record all running natively, with no second system to maintain. ## The integration tax goes down, not up Here is the part that inverts the usual platform math. In a stack of point solutions, every tool you add increases the integration burden, because each new system has to be wired to all the others. On a shared data layer, the opposite happens. One identity model, one permission structure, one employee record that every capability reads from and writes to. Once that foundation is in place, every new workflow you turn on inherits it. Adding the second capability is cheaper than adding the first, and the third is cheaper still. Expansion gets easier as you go, not harder. That is what "you don't get locked in" actually means in practice. You are not committing to a big-bang purchase. You are closing one gap now, on a foundation that makes the next gap cheaper to close whenever you decide to. ## Where MangoApps Fits ![Three-column MangoApps platform overview showing Employee Experience, Frontline Operations, and People Operations capabilities connected by one shared Mango platform base.](https://mango-cdn.b-cdn.net/marketing/uploads/one-shared-mango-platform-base.png) MangoApps is the Enterprise Workforce Platform Built for the Frontline, and the "start with one, expand when ready" model is a direct property of that architecture. Because identity, data, permissions, and workflows already live in one place, turning on a new capability is a configuration, not an implementation, and the AI built across the suite works on that same governed foundation the moment you enable it. The platform decision is made once. Adoption grows one workflow at a time. The reason expansion works is that the first workflow actually gets used, which is a question of adoption. MangoApps reaches 90%+ adoption within 90 days because it lives in the app employees already open, and that is backed by the Adoption Guarantee: if your people don't adopt after launch, you don't pay. You decide the pace. The foundation is ready whenever you are. ## Frequently asked questions **Do we have to buy the whole platform to use one capability?** No. Organizations start with the single capability that closes their biggest gap, and the platform foundation is included regardless. You don't pay for what you aren't using. **Do we redo our integrations when we add a second capability?** No. Integrations, the employee record, and the permission model are part of the shared foundation. A new capability inherits all of it, so expansion doesn't restart your integration work. **Does adopting MangoApps mean replacing our HRIS or payroll?** Not unless you want it to. Most organizations keep and connect: the HRIS and payroll stay in place and sync to the shared data layer. Migration is an option later, on your timeline, not a requirement. ## Keep reading - [Platform](https://www.mangoapps.com/platform) - [Integrations](https://www.mangoapps.com/integrations) > **Map your own path in:** we'll show you keep-and-connect, migrate, and net-new against your current stack. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) --- # Recognition That Becomes Culture Data **Author:** MangoApps Team **Published:** 2026-07-14 **Category:** Customer Success Stories Visible, values-tagged recognition reveals what your culture rewards and helps inform performance, engagement, and AI insights. Recognition gets treated as a morale nicety: a nice-to-have, a shoutout in a meeting, a program HR runs on the side. That framing undersells it badly. When recognition happens on the platform where work already lives, every moment of it becomes data about your culture, who is engaged, which values actually show up in practice, where momentum is building and where it is thinning. A thank-you that disappears into a private notification is a kind gesture. A thank-you that lands on a shared feed, tagged to a value, visible on a profile, is a data point. The difference isn't the sentiment. It's whether the moment leaves a record. ## Recognition Has to Stay Visible to Do Anything The first requirement is simple: anyone can recognize anyone, and the recognition stays visible. Not buried in a one-to-one notification, but on the home feed, on team pages, on the recognized employee's profile. Visibility is what turns a single moment into a reinforced behavior, because the whole organization sees what got valued, not just the person who received it. Recognition that only the recipient sees reinforces nothing. Recognition everyone sees sets a norm. ![peer to peer manager recognition](https://mango-cdn.b-cdn.net/marketing/uploads/peer-to-peer-manager-recognition.png) That is also what makes it a culture tool rather than a management tool. When acknowledgment flows in every direction, peer to peer as readily as manager to report, it stops being a performance lever and starts being a picture of how people actually treat each other. ## Tag It to a Value and It Becomes a Signal The step that turns visible recognition into culture data is tagging each moment to a company value. Once every recognition carries a value, you have a live, searchable record of how your culture is expressed: which values get recognized most, which get recognized least, where the gap is between the values on the wall and the behaviors in the building. That is a signal leadership can act on, not a sentiment they have to guess at. The values nobody recognizes are telling you something as clearly as the ones everybody does. ![values based recognition](https://mango-cdn.b-cdn.net/marketing/uploads/values-based-recognition.png) And because it all sits on the shared data layer, the full recognition record surfaces in the review workflow. A rating that would otherwise lean on the last eight weeks gets the context of a year's worth of how this person actually contributed. Recognition stops being separate from performance and starts informing it. ## What It Looks Like When It Works Full House runs 19 furniture stores across rural South Africa, some hours apart by road, on a culture of genuine human connection. Their problem was that a win in one store stayed in that store. There was no shared picture of what any team had done, and no momentum that carried from one location to the next. So they branded MangoApps as LekkaChat and started posting store achievements to a company-wide feed. When a store hits its target, a post goes up, and every employee across all 19 locations can see it, react to it, add to it. > "Our employees love to look at the posts. When a store makes their target for the month, there's a post around it and everybody can like and comment on it. And then, as the month draws to a close, the announcements come in one after the other and it creates a sense of enthusiasm and excitement." > — Alison van Zijl, Head of Human Resources, Full House [Read Full Case Study](https://www.mangoapps.com/resources/full-house-case-study) That is recognition connected to the performance record: not a number on a form, but a visible, running account of what teams have done, one both managers and employees can see when the formal conversation finally happens. > **Read the whole argument:** recognition is part of the engagement story in [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book), alongside the reviews, goals, succession, and skills gaps, with the customer proof for each. ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and in the Performance & Learning suite recognition isn't a bolt-on. It runs on the same shared data layer as reviews, goals, and surveys, so recognition can be tagged to values, turned into culture analytics, and surfaced in the review view as part of the full-year picture. Because listening and performance data share one platform, the AI built into the suite can read engagement and recognition patterns together and flag where momentum is fading before a survey would catch it. AI is the proof a connected platform matters, not the headline. ![Diagram showing one data layer connecting performance, goals, succession, and skills and certifications capabilities, including reviews, OKRs, role mapping, and skill tracking.](https://mango-cdn.b-cdn.net/marketing/uploads/one-data-layer.png) Culture data is only as complete as participation, which is a question of adoption, and recognition is where adoption often starts. MangoApps reaches 90%+ adoption within 90 days because recognition lives in the app employees already open, on any device, with no separate login. That is backed by the Adoption Guarantee: if your people don't adopt after launch, you don't pay. Recognition was always data about your culture. The only question was whether anything was capturing it. > **See recognition become culture data:** we'll show you values-tagged recognition and its analytics in the Performance & Learning suite. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book) - [Employee engagement](https://www.mangoapps.com/solutions/employee-engagement) - [Full House case study](https://www.mangoapps.com/resources/full-house-case-study) --- # What a Silent Certification Lapse Costs in Regulated Work **Author:** MangoApps Team **Published:** 2026-07-14 **Category:** Best Practices Manual credential tracking misses quiet expirations. Use continuous monitoring to catch lapses early and reduce compliance risk. In regulated work, the certification that hurts you is not the one you know is expiring. It's the one that lapsed quietly three weeks ago, that nobody noticed, that surfaces in an audit or an incident review with your name on the finding. By the time a lapse becomes visible that way, it has already cost you. The audit is underway, the liability is on the table, the operational hold is in effect. Everything after that is cleanup. The whole problem with tracking credentials in a spreadsheet is that a spreadsheet tells you a certification expired. It does not tell you before. ![certification risk alerts](https://mango-cdn.b-cdn.net/marketing/uploads/certification-risk-alerts.png) ## How credentials go stale without anyone deciding to let them Nobody chooses to let a license lapse. It happens because credential tracking depends on manual diligence, and manual diligence at scale fails in the ordinary ways: the person who owned the spreadsheet changed roles, the renewal window fell during a busy quarter, the alert lived in an inbox nobody was watching. Multiply that across a large or distributed workforce and the question stops being whether a lapse will slip through and becomes how many already have. Skills records decay the same way, and the damage is quieter but broader. Every succession decision, every development plan, every "who can cover this shift" answer built on a stale skills profile is a guess wearing the costume of data. In regulated work, that guess can put an uncredentialed person in a credentialed seat. ## The cost tail that dwarfs the rest This is why certifications belong in a different risk category than most performance data. A missed review is a bad conversation. A missed credential can be an audit finding, a liability claim, or a shutdown, and the cost of any one of those can exceed the entire performance and compliance budget combined. The asymmetry is the point: the effort to prevent a lapse is trivial next to the cost of one that gets through. ## Caught in advance, monitored across everyone at once The fix is not more diligence. It is monitoring that does not depend on a person remembering. Every license and credential held with an expiration date and a configurable alert window, thresholds set per certification type at ninety, sixty, or thirty days out. Expiration risk surfaced across the entire workforce simultaneously, which is exactly the scale at which manual tracking breaks. And alerts routed to the three people who need them at once: the employee who has to act, the manager who has to be aware, and the HR or compliance team tracking the whole population. ![license certification tracking](https://mango-cdn.b-cdn.net/marketing/uploads/license-certification-tracking.png) The result is that a lapse gets closed before it opens. The credential renews on time because the alert arrived with weeks to act, not after the fact. In a regulated setting, that shift from reactive to proactive is the entire game. > **Read the whole argument:** the skills and certification gap is one of four in [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book), alongside reviews, goals, and succession, with the cost model for each. ## Where MangoApps Fits ![proven at enterprise scale](https://mango-cdn.b-cdn.net/marketing/uploads/proven-at-enterprise-scale.png) MangoApps is the Enterprise Workforce Platform Built for the Frontline, and the Performance & Learning suite keeps skills and certifications on the same shared data layer as reviews, goals, and succession. Credential records are centralized, expiration windows are configurable, and skill profiles stay current because they are populated from employee updates, manager inputs, and automatic completions rather than one person's spreadsheet. The AI built into the suite monitors expiration dates across the whole workforce continuously and surfaces risk before it becomes a compliance issue, then routes the alert to everyone who needs it. AI here is proof that a connected platform matters, not the pitch. Monitoring only works if the workforce is actually on the platform, including the frontline, which is a question of adoption. MangoApps reaches 90%+ adoption within 90 days because every capability, including skills and certifications, lives in the branded app employees already carry, with no corporate email or company device required. That is backed by the Adoption Guarantee: if your people don't adopt after launch, you don't pay. The lapse you catch in advance never becomes the finding you explain later. > **See certification risk surfaced before it opens:** we'll show you credential monitoring across a full workforce in the Performance & Learning suite. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book) - [Safety & compliance](https://www.mangoapps.com/solutions/safety-compliance) - [Workforce planning](https://www.mangoapps.com/solutions/workforce-planning) --- # Succession Is a Pipeline, Not a Document **Author:** Christos Schrader **Published:** 2026-07-14 **Category:** Best Practices Annual succession plans drift fast. A live pipeline keeps readiness, risk, and development current when roles actually open. The succession plan looked ready. It was a clean slide, reviewed at the last talent meeting: every critical role with a name beside it, a readiness rating, a tidy sense that the organization was covered. Then a role actually opened, and the plan turned out to be fiction. The person marked "ready in a year" had left eight months ago. The rating nobody had touched since the review reflected an impression, not a trajectory. The document was accurate for about a week, and slowly stopped being true every day after. ![succession dashboard risk alerts](https://mango-cdn.b-cdn.net/marketing/uploads/succession-dashboard-risk-alerts.png) That is the difference between a document and a pipeline. A document is right on the day you make it. A pipeline is right on the day the role opens, which is the only day that counts. ## Why the Annual Snapshot Drifts A once-a-year plan drifts for a simple reason: it is built from a moment, and people are not moments. Readiness set by who spoke up in the talent review, or by seniority, or by recency of impression, starts decaying immediately. Skills change. High performers get poached. Development stalls or accelerates. None of that shows up in a slide that won't be opened again until next year. By the time the plan is consulted in a real vacancy, the only thing it reliably documents is how the room felt twelve months ago. The cost of that gap is not abstract. Replacing a leader runs roughly 200% of their annual salary (according to Gallup), and a single senior departure that catches the pipeline unprepared can dwarf the entire year's talent budget on its own. ## What a Pipeline Does That a Document Can't A pipeline is grounded in data that keeps moving. Readiness ratings drawn from performance history, OKR achievement, recognition patterns, and completed development milestones, not from who was visible in the meeting. Multiple candidates mapped per role at different readiness levels: ready now, ready in twelve to eighteen months, in early development. And, critically, readiness that advances on its own. When a candidate completes a development milestone or a certification, their rating updates without anyone editing a cell. ![role to candiate mapping](https://mango-cdn.b-cdn.net/marketing/uploads/role-to-candiate-mapping.png) That last property is what makes it a pipeline rather than a prettier document. The plan maintains itself, because it reads from the same performance and skills data everything else does. The candidate can see their own trajectory too, which turns a private HR artifact into a concrete path someone is actually walking. ## The Roles Nobody Mapped The most dangerous line in any succession review is not the role with a weak candidate. It is the role with no candidate at all, the single point of failure nobody flagged because the annual process was busy rating the people who were already visible. A live pipeline surfaces those directly: which roles are well-covered, which are at risk, and which have no identified successor, updated continuously rather than discovered in a crisis. The alert that seventeen roles have no successor is worth more than any rating on the roles that do. ![succession readiness surfacing](https://mango-cdn.b-cdn.net/marketing/uploads/succession-readiness-surfacing.png) And because the underlying data is continuous, readiness signals surface as they emerge. A high-potential employee gets identified by their trajectory, not by whether they happened to catch a senior leader's attention. Flight risk on a succession candidate gets flagged before the resignation confirms it, not after. > **Read the whole argument:** succession is one of four gaps in [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book), alongside reviews, goals, and skills, with the customer proof for each. ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and the Performance & Learning suite treats succession as live infrastructure, not an annual deliverable. Because succession runs on the same shared data layer as reviews, goals, and skills, readiness ratings update automatically as development milestones and certifications are completed, and pipeline health stays current without manual compilation. The AI built into the suite reads that connected data to surface readiness and retention signals as they develop, so the picture is ready the day a talent review or a vacancy demands it. AI is the proof the platform decision matters, not the headline. ![Diagram showing one data layer connecting performance, goals, succession, and skills and certifications capabilities, including reviews, OKRs, role mapping, and skill tracking.](https://mango-cdn.b-cdn.net/marketing/uploads/one-data-layer.png) A pipeline is only trustworthy if the data feeding it is complete, which comes back to adoption. MangoApps reaches 90%+ adoption within 90 days because the whole experience lives in the app employees already open, backed by the Adoption Guarantee: if your people don't adopt after launch, you don't pay. The plan you can trust in a vacancy is the one that was never a document to begin with. > **See a pipeline that stays current:** we'll map your critical roles through the Performance & Learning suite and show where the annual snapshot becomes a live view. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book) - [Workforce planning](https://www.mangoapps.com/solutions/workforce-planning) - [Analytics & insights](https://www.mangoapps.com/analytics-insights) --- # Why Performance Reviews Fail Without a Shared Record **Author:** Christos Schrader **Published:** 2026-07-14 **Category:** Best Practices Most reviews rely on memory, not evidence. A shared record makes feedback fairer, more complete, and easier to act on. There are two ways a manager can walk into a performance review. They can arrive with a year assembled in front of them: goals and their progress, peer feedback, recognition, the arc of the last twelve months already in one view. Or they can arrive the way most managers do, having spent the night before reconstructing that year from memory and a handful of open tabs. Same meeting, same form, same rating scale. Completely different conversation. A review is only ever as good as the record it's built on, and most reviews are built on almost none. ![Three statistic cards highlight workplace performance insights: managers interact with five or more disconnected systems per review cycle, 14% of employees say reviews inspire improvement, and 29% say manager feedback helps them work better.](https://mango-cdn.b-cdn.net/marketing/uploads/why-review-arent-working.png) Only 14% of employees strongly agree their reviews inspire them to improve (according to Gallup). That number doesn't come from managers who don't care. It comes from reviews built the second way. ## What the Night-Before Review Actually Is When performance data, goal progress, 360 input, and recognition all live in separate places, none of them arrive on their own. The manager has to go get them, and there is never enough time, so they don't get most of them. What fills the gap is memory, and memory is dominated by the last eight weeks. A strong performer who had a quiet October gets a quiet-October review. A steady contributor who shipped the hardest work in the spring gets a spring nobody remembers. This is recency bias, and it isn't a character flaw. It is what happens when the only available record is the one in the manager's head. Only 29% of employees strongly agree the feedback they receive helps them do better work (according to Gallup), and feedback assembled from the most recent thing that happened is feedback about the wrong things. ## What Changes When the Record Is Already There A record changes the starting point. Instead of reconstructing the year, the manager reviews it. Structured cycles run on standardized rating scales and competency frameworks, so a review in one team is comparable to a review in another. Probationary and ad-hoc reviews use the same framework as the annual one, so a new hire's first review isn't improvised. None of that requires the manager to be more diligent. It requires the data to be in one place before the meeting starts. ![Diagram showing one data layer connecting performance, goals, succession, and skills and certifications capabilities, including reviews, OKRs, role mapping, and skill tracking.](https://mango-cdn.b-cdn.net/marketing/uploads/one-data-layer.png) The difference an employee feels is trust. A rating drawn from a visible, year-long record is one they can see the basis for. A rating drawn from the last thing they did is one they brace for. ## The 360 That's Already in the View Multi-directional feedback is where the memory-versus-record gap gets widest, because 360 input is exactly the kind of data that evaporates if it isn't captured in context. Feedback from peers, direct reports, and cross-functional partners is worth far more than any single reporting-line view, but only if it reaches the manager at the moment of the review rather than as a separate exercise nobody connects back. ![360 degree feedback](https://mango-cdn.b-cdn.net/marketing/uploads/360-degree-feedback.png) The version that works surfaces 360 responses directly in the manager's review view, alongside OKR data and recognition history, with no import and no manual compilation. Anonymity is configurable by review type and respondent group, so candor doesn't cost accountability. The point is not that there is more feedback. The point is that it is already where the decision gets made. ## The Manager's Actual Job Give a manager a year they have to rebuild and you turn a coach into a records clerk. Give them a year that assembled itself and you give the hours back to the only part of the review that was ever supposed to matter: the conversation about what happens next. That is the whole case for a shared record. It doesn't make managers work harder at the review. It stops asking them to manufacture the inputs first. > **Read the whole argument:** the review is one of four gaps in [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book), alongside goals, succession, and skills, with the cost model and the customer proof for each. ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and the Performance & Learning suite is built so the review is retrieved, not rebuilt. Reviews, goals, 360 feedback, recognition, and skills run on one shared data layer, so OKR progress and 360 responses land in the review view automatically. Because the data is connected, the AI built into the suite can read the full-year record continuously and flag a retention risk building on a team that looks fine on the surface. AI isn't the headline here. It is what a shared record makes possible. A record only works if it's complete, which comes down to whether people use the system all year. MangoApps reaches 90%+ adoption within 90 days because performance lives in the app employees already open, with no separate login, and that is backed by the Adoption Guarantee: if your people don't adopt after launch, you don't pay. The best review you'll run is the one you didn't have to reconstruct the night before. > **See a review built from a record:** we'll walk your own cycle through the Performance & Learning suite and show where the reconstruction disappears. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book) - [Performance & learning](https://www.mangoapps.com/solutions/performance-learning) - [Merchants Bonding case study](https://www.mangoapps.com/resources/merchants-bonding-case-study) --- # From Sent to Certain: Closing the Frontline Accountability Loop **Author:** MangoApps Team **Published:** 2026-07-12 **Category:** safety-compliance A store manager sends out the new food safety SOP on Tuesday. By Thursday, everyone on the shift roster has technically "received" it — the email delivered, the notification fired, the document is... # From Sent to Certain: Closing the Frontline Accountability Loop A store manager sends out the new food safety SOP on Tuesday. By Thursday, everyone on the shift roster has technically "received" it — the email delivered, the notification fired, the document is accessible. On Saturday, an inspector walks the floor and finds a temperature log not completed properly. Nobody's careless. Nobody's malicious. The policy was distributed. The training was assigned. The compliance box got checked. The failure happened in the space between "we sent it" and "they know it." That gap — between distribution and comprehension, between attendance and capability, between presence and readiness — is where most frontline accountability problems actually live. This week's releases across MangoApps point toward a different approach to that problem: not just getting information out, but creating verifiable evidence that it landed. --- ## The Distribution Illusion Most organizations have solved information distribution. There are intranets, policy wikis, email blasts, required training modules. What hasn't been solved is the layer beneath: whether any of it produced understanding. Standard operating procedures are a good example. Traditionally, an SOP exists as a PDF somewhere — maybe well-written, maybe a decade old, maybe only findable if you already know what it's called. Publishing it is easy. Knowing who read it, and whether they understood it, is not. The [SOP Hub AI-Assisted Authoring & Read Attestation](https://www.mangoapps.com/changelog/3048) release this week addresses both ends of that chain. On the creation side, SOPs can now be drafted from a plain-language description or imported from existing PDF and Word documents — which removes the friction that keeps policies from being updated in the first place. An SOP that's too painful to write is an SOP that stays outdated. But the more significant part is what happens after publishing: employees complete a signed read-and-understood attestation before they can mark the document reviewed. That signature is logged. It can be audited. It turns "we published the policy" into "we have a timestamp for when each employee acknowledged it." The same principle shows up in [Must-Read Acknowledgment Tracking](https://www.mangoapps.com/changelog/3043) in the News Feed. Managers and admins can now click through acknowledgment counts on any Must-Read post to see exactly who has read it, who hasn't, and export the list. Automated reminders can be sent to employees who haven't acknowledged yet. For industries where the answer to "did your team get this update?" has to be something stronger than "I think so," this changes what compliance documentation looks like. Together, these features represent a shift in what "we communicated it" means. It used to mean "we sent the message." It can now mean "we have a record of who received it, opened it, and confirmed they understood it." --- ## Showing Up Isn't the Same as Being There Physical presence has the same accountability problem as digital communication. Paper sign-in sheets at events get lost, or get pre-signed, or don't capture late arrivals and early departures. Inspection reports say "zone completed" without specifying which shelves were actually checked. Attendance becomes a narrative rather than a record. [QR Code and Geolocation Event Check-In](https://www.mangoapps.com/changelog/3044) in the Calendar app closes that gap for events and meetings. Attendees check in via a QR code displayed on-site or by GPS proximity, generating a timestamped, verified record of who was physically present — without asking an organizer to manually track it. For mandatory training sessions, all-hands meetings, or events where attendance is a compliance requirement, the difference between "everyone was invited" and "we can prove who came" is material. The more operationally specific version of the same problem shows up in [Coverage Sweep Shelf-Level Grid Tracking](https://www.mangoapps.com/changelog/3041). Mobile inspectors can now mark individual shelves by bay and level as passed or flagged during floor sweeps — not just "I completed the zone," but a precise record of which physical locations were inspected. The coverage dashboard reflects per-shelf progress across the facility in real time. For food retail, pharma distribution, warehouse operations, or any environment where "we did the inspection" means something legally or operationally specific, approximate coverage is a liability. A completed sweep where twenty shelves in Zone C went unchecked is not a completed sweep. The grid tracking makes that visible during the inspection rather than after an incident. These aren't surveillance features. They're documentation features — the difference between a narrative ("yes, we checked") and a record ("here is when, where, and by whom"). --- ## The Capability Gap That Training Completion Doesn't Measure The hardest version of the accountability problem is also the least visible: whether someone can actually perform under pressure, not just whether they've passed the quiz. A customer service rep can finish a de-escalation training module, score well on the assessment, and still freeze the first time a real conversation goes sideways. A new hire can complete the onboarding checklist without retaining most of what they went through. Training completion is a proxy for readiness — a convenient one, but often a misleading one. [Live Voice Roleplay in Practice Hub](https://www.mangoapps.com/changelog/3042) approaches this differently. Employees practice high-stakes conversations with an AI persona in real time, speaking and being spoken to — including interruptions and pressure dynamics that text-based practice can't replicate. The point isn't to replace coaching; it's to create the kind of pressure-testing that usually only comes from actual situations, before those situations happen. The companion release — [Practice Hub AI Coach Chat, Exemplar Generation, and Team Skill Radar](https://www.mangoapps.com/changelog/3041) — adds the layer that makes practice useful rather than just repetitive. After a roleplay session, an AI coach can answer follow-up questions grounded in that specific employee's performance and the scoring rubric they were evaluated against. When someone falls short on a specific criterion, they can request examples from top performers to understand concretely what "good" looks like in this organization, not just in theory. The Team Skill Radar is the manager-facing view of all of this: a visual map of where actual competency gaps exist across direct reports, derived from real practice data rather than training completion status. From that view, managers can assign targeted practice with a single action — closing the loop from "I can see who's struggling" to "I've done something about it" in one place. This is what "we trained them" starts to mean when the underlying data is performance, not completion. --- ## The Bigger Picture The last decade of HR and operations technology was largely about connecting the frontline — getting information to people who were dispersed, mobile, or shift-based, and giving them tools that worked on a phone rather than a desktop. That problem is largely solved. What's not solved is the layer underneath: knowing whether the information connected, whether the presence was real, whether the capability exists. The accountability loop — from "we distributed" to "we know it landed" — has stayed manual, approximate, or nonexistent in most organizations. What's happening across these releases is that the loop is starting to close. Not in a way that treats employees as suspects to be monitored, but in a way that gives organizations actual answers to questions that matter: Did they read the policy before they worked the shift? Did the inspector actually cover every shelf? Does the team have the skill to handle the situation, or do they have the credential that says they sat through the training? Those aren't compliance questions for their own sake. They're operational questions. The teams that can answer them with data — not with narratives — are the ones that catch problems before incidents, close capability gaps before they surface in customer complaints, and walk into an audit with documentation that's actually defensible. The gap between "sent" and "certain" has always been there. It's getting shorter. --- # Homepage Goals Get Talked About; Deck Goals Don't **Author:** MangoApps Team **Published:** 2026-07-10 **Category:** Customer Success Stories Goals only work when employees can see them. Learn how visible OKRs improve alignment, engagement, and performance reviews. Ask a talent leader where their company's goals live, and you'll get one of two answers. Either they're in a planning deck, reviewed at the quarterly business review and filed until the next one. Or they're in a dedicated OKR tool, entered in January and opened maybe twice more before year-end. Both are real systems. Both feel like goal management. Neither one puts the goals in front of the people expected to work toward them. And a goal nobody sees is a goal that steers nothing. ![okr dashboard](https://mango-cdn.b-cdn.net/marketing/uploads/okr-dashboard.png) ## The Test Is Whether Anyone Looks An objective's power is not in being set. It is in being seen, often, by the people whose work it is supposed to direct. A goal set in January and reopened in November didn't guide ten months of work. It documented an intention and then went dark. This is why performance reviews so often ring hollow: only 14% of employees strongly agree their reviews inspire them to improve (according to Gallup), and you cannot have a meaningful conversation about progress toward goals that were only ever visible to the people who set them. The distinction is simple and unforgiving. Homepage goals get talked about. Deck goals don't. Where the goal lives determines whether it does any work. ## What Changed at Columbia Basin Health Columbia Basin Health Association is a federally qualified health center in rural Washington, with more than 460 employees, two thirds of them clinical and frontline. Their old intranet was read-only. Leadership goals were set annually and were largely invisible to the people expected to act on them. Quarterly engagement surveys kept surfacing the same complaint: employees didn't know what the executive team did or where the organization was heading. So CBHA moved the goals. They put MangoApps at the center of the employee experience, branded it Pulse, and made leadership goals the first thing on the homepage. The CEO started posting monthly video updates. Engagement surveys ran inside the same app employees used for everything else. Within months, an adoption target they had set for two years was cleared, and monthly engagement passed 90%. The survey finding about invisible goals disappeared, for one reason. > "With all of the resources we built within MangoApps, getting employee engagement was very easy. We currently have over 90% monthly employee engagement." > — Rebecca Wolfs, Director of Training, Development, and Compliance, CBHA The goals were now front and center, every day, for every employee. Nothing about the goals themselves changed. Their location did, and that was the whole game. ## Visibility Is a Property of the System, Not the Effort You can't fix invisible goals by asking managers to remind their teams more often. The reminder is a workaround for a goal that lives somewhere people don't go. Real visibility means objectives cascade from company to team to individual so everyone can see how their work connects to the priority above it, progress updates as it happens rather than during a scramble at quarter-end, and key results are shared with the team, not locked in one contributor's private notes. That is not a communication habit. It is a property of where the goals live and who can see them. ![cascaded objectives](https://mango-cdn.b-cdn.net/marketing/uploads/cascaded-objectives.png) And when goals are visible all year, the review stops being an interrogation of things the employee never knew were being tracked. The goal data flows straight into the review, because it was in front of everyone the whole time. The conversation that was supposed to drive growth finally can. > **Get the full playbook:** the goal-visibility problem is one of four in [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book), alongside the reviews, succession, and skills gaps, with the customer proof for each. ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and the Performance & Learning suite is built so goals are visible by default. Objectives cascade automatically from company to individual, key results update in real time and stay shared with the team, and OKR data flows natively into performance reviews with no compilation at year-end. Because performance, goals, and recognition sit on one shared data layer, the visibility isn't a feature you have to maintain. It is how the system works. ![Diagram showing one data layer connecting performance, goals, succession, and skills and certifications capabilities, including reviews, OKRs, role mapping, and skill tracking.](https://mango-cdn.b-cdn.net/marketing/uploads/one-data-layer.png) CBHA's result points to the reason it holds: goals only stay visible if employees actually open the app they're in. MangoApps reaches 90%+ adoption within 90 days because the goals live in the same place employees already go for company news, their schedule, and their team, on any device, with no separate login. That adoption is backed by the Adoption Guarantee: if your people don't adopt after launch, you don't pay. Set the goal anywhere you like. Whether it does any work depends on whether anyone can see it. > **See what visible goals do to a review:** we'll show you the OKR-to-review flow on the same platform employees already open. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book) - [Columbia Basin Health case study](https://www.mangoapps.com/resources/columbia-basin-health-associate-case-study) - [Performance & learning](https://www.mangoapps.com/solutions/performance-learning) - [Employee engagement](https://www.mangoapps.com/solutions/employee-engagement) --- # What Performance Really Costs: 3,000 to 4,000 Hours a Year Assembling Review Data **Author:** Christos Schrader **Published:** 2026-07-10 **Category:** Best Practices Performance management costs more than software—hidden in manager hours, turnover, and stale data. See where the real cost adds up. **Here is the number worth putting in your next budget conversation:** a 5,000-person organization can spend 3,000 to 4,000 hours a year just assembling the data for performance reviews, before a single development conversation takes place. That is close to two full-time roles, and none of it appears on a line item. It shows up instead as time managers didn't spend managing, and as ratings employees didn't see coming. Performance management has a cost problem that most budgets never capture, because the biggest costs are absorbed rather than invoiced. They hide in manager hours, in turnover, in decisions made on stale data. Here is where the money actually goes. > **See the full cost model:** [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book) breaks down all four gaps and what each one adds up to across a 5,000-person organization. ## The 3,000-hour number, and where it comes from The figure isn't a slogan. It comes from a straightforward model. Take a 5,000-employee organization with roughly 500 managers. Run two review cycles a year. Assume each manager spends three to four hours per cycle just compiling a picture from the five or more systems where performance data lives: the goals tool, the HRIS, notes, the recognition feed, email. Multiply it out and you land between 3,000 and 4,000 hours annually, spent assembling information instead of developing people (MangoApps benchmark model). Your own numbers will land differently. The pattern holds regardless of the exact figure. ![Three statistic cards highlight workplace performance insights: managers interact with five or more disconnected systems per review cycle, 14% of employees say reviews inspire improvement, and 29% say manager feedback helps them work better.](https://mango-cdn.b-cdn.net/marketing/uploads/why-review-arent-working.png) That is the visible cost, the one you can at least estimate. The recency bias that fills the gaps in a rushed reconstruction never reaches a budget line at all. It shows up in every rating an employee didn't expect, and in every good performer who quietly concludes the process isn't worth taking seriously. ## The goals nobody sees between cycles An OKR set in January and reopened in November steered nothing for ten months. That is not a scheduling inconvenience. It is ten months of work pointed by habit rather than by priority. Only 14% of employees strongly agree their reviews inspire them to improve (according to Gallup), and goals no one can see between cycles are a large part of why. ![okr dashboard](https://mango-cdn.b-cdn.net/marketing/uploads/okr-dashboard.png) Effort still happens. It just isn't aimed. The cost is the gap between the work people did and the work the business needed, compounded across every team, every quarter. ## The succession plan that was fiction the day the role opened ![succession dashboard risk alerts](https://mango-cdn.b-cdn.net/marketing/uploads/succession-dashboard-risk-alerts.png) When a critical role opens and the pipeline that looked ready is not, the replacement costs roughly 200% of that leader's annual salary (according to Gallup). A single senior departure can dwarf the entire annual performance budget on its own. The annual talent review produces a snapshot that is accurate for about a week and slowly drifts into fiction over the following year. A live pipeline costs a fraction of that surprise, and it is current the day the role opens, which is the only day the accuracy matters. ## The credential that lapsed between audits In regulated work, the cost tail is longer than any of the above. A single certification that lapses silently can trigger an audit finding, a liability claim, or an operational shutdown. The performance budget is not even the right order of magnitude for comparison. And every succession and development decision built on a stale skills profile is a guess wearing the costume of data. ![license certification tracking](https://mango-cdn.b-cdn.net/marketing/uploads/license-certification-tracking.png) ## The common thread None of these needs a disaster to add up. They compound through ordinary moments: a review built from memory, a readiness rating eighteen months stale, a credential that expired unnoticed, an OKR nobody reopened after January. Add them together and the true cost of performance management is not the software line. It is the hours, the turnover, and the decisions made on information that was already out of date. The cause is the same in every case: the data lives in separate places, so the work of pulling it together falls on people, late, under pressure. ## Where MangoApps fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and the Performance & Learning suite attacks the cost at its root by putting performance, goals, succession, and skills on one shared data layer. The October reconstruction disappears because the picture assembles itself all year. OKR progress, 360 responses, and recognition history flow into the review view automatically, so the 3,000-to-4,000-hour compilation tax largely goes away. The AI built into the suite runs on that connected data to flag retention risk and readiness gaps before they become the expensive kind of surprise. (Compensation decisions draw on the same connected record, though comp itself lives in HR Operations, not the performance suite.) ![Diagram showing one data layer connecting performance, goals, succession, and skills and certifications capabilities, including reviews, OKRs, role mapping, and skill tracking.](https://mango-cdn.b-cdn.net/marketing/uploads/one-data-layer.png) The savings only materialize if the data is complete, which is a question of adoption. MangoApps reaches 90%+ adoption within 90 days because performance lives in the app employees already open, with no separate login, and that is backed by the Adoption Guarantee: if your people don't adopt after launch, you don't pay. Implementation runs 8 to 12 weeks with a named Customer Success Manager from day one. The cheapest review cycle you'll run is the one where nobody had to rebuild the picture first. > **Build the business case for your own numbers:** we'll model the compilation cost for your org size and show what a shared data layer recovers. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book) - [Analytics & insights](https://www.mangoapps.com/analytics-insights) - [Performance & learning](https://www.mangoapps.com/solutions/performance-learning) - [Success services](https://www.mangoapps.com/success-services) --- # The Four Information Gaps Behind Every Performance Failure **Author:** Christos Schrader **Published:** 2026-07-10 **Category:** Best Practices Performance, goals, succession, and skills fail when data is fragmented. Learn how to spot and close the four gaps before they get expensive. **Quick answer:** almost every performance failure, a year-end surprise, a stalled OKR, a succession plan that turned out to be fiction, a credential that lapsed unnoticed, traces to one of four information gaps: performance data is reconstructed instead of retrieved, goals are invisible between cycles, succession is a document instead of a pipeline, and the skills picture is out of date. They are not four separate problems. They are one problem, fragmented data, showing up in four places. Pull on any of them and you find the same root. The review that felt unfair, the quarter that drifted, the promotion that stalled: the manager didn't have the information the moment they needed it, because it lived somewhere else. Here is each gap, what it costs, and how to tell how many are open in your own organization. > **Get the complete playbook:** [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book) covers all four gaps, the cost of leaving them open, and what closing them looks like, in one place. ![four information gaps](https://mango-cdn.b-cdn.net/marketing/uploads/four-information-gaps.png) ## Gap 1: performance data is reconstructed, not retrieved When the year-end picture has to be compiled from five or more systems, it gets built from memory and recency bias instead. The manager isn't reviewing. They are reconstructing. And the version they reconstruct leans heavily on the last eight weeks, because that is all anyone can reliably recall. Only 14% of employees strongly agree their reviews inspire improvement (according to Gallup), and a rating assembled the night before is a large part of why. ## Gap 2: goals are invisible between cycles An OKR set in January and reopened in November steered nothing in between. For ten months, people work without a visible line to company priorities. The goals documented effort rather than directing it. Only 29% of employees strongly agree their manager's feedback helps them do better work (according to Gallup), and feedback disconnected from goals nobody can see is feedback about the wrong things. ## Gap 3: succession is a document, not a pipeline Readiness ratings reflect what was known at the last talent review, not what is true today. The slide deck looked ready. Then the role actually opened, and the person marked "ready in one year" left eight months ago, or was never as close as the annual snapshot suggested. Replacing a manager costs roughly 200% of their annual salary (according to Gallup). A plan that is accurate once a year and fiction the rest of the time is not a pipeline. It is a document. ## Gap 4: the skills picture is out of date Certifications lapse silently. Skill profiles go unmaintained. Every succession and development decision built on them is a guess. In regulated work the stakes are sharper: a single credential that lapses between audits can trigger an audit finding, a liability claim, or an operational shutdown at a cost that dwarfs the entire performance budget. Stale skills data doesn't announce itself. It surfaces at the worst possible moment. ## Score your own operation Before you decide which gap to close first, find out how many are open. Mark each honestly. - **Gap 1, reconstruction.** When a manager runs a review, is the full-year picture already assembled in one place, or compiled from several systems the week before? *(Already there ←→ Rebuilt from memory)* - **Gap 2, invisible goals.** Between review cycles, can an employee see their goals and their progress on any given Tuesday, or do the goals go dark until review season? *(Visible daily ←→ Dormant until year-end)* - **Gap 3, succession.** If a critical role opened tomorrow, would your readiness data be current, or as of the last talent review? *(Current today ←→ Accurate once a year)* - **Gap 4, skills.** Do lapsing certifications and stale skill profiles surface automatically, or only when someone goes looking, or when an auditor does? *(Flagged automatically ←→ Found after the fact)* **How to read your score:** - **0 gaps open.** Rare. Your performance data is infrastructure, not an annual archaeology project. Keep it that way. - **1 gap open.** One workflow is running on reconstruction. It is dragging the other three, because the data they need flows through it. Close it before it spreads. - **2 gaps open.** The common score, and the expensive one to leave alone. Your reviews, goals, and succession decisions are all partly built on information that isn't current. - **3 to 4 gaps open.** Your performance process is running on memory. Every number your talent strategy depends on, readiness, retention risk, development spend, is being set by tools that were never built to share what they know. ## What the gaps cost when you add them up None of this needs a catastrophe to become expensive. The costs compound through ordinary moments. ![ma performance growth](https://mango-cdn.b-cdn.net/marketing/uploads/ma-performance-growth.png) In a 5,000-person organization, Gap 1 alone can mean 3,000 to 4,000 hours a year spent assembling review data instead of developing people, close to two full-time roles doing work the platform should already have done (based on MangoApps' benchmark model of 500 managers running two cycles a year at three to four hours each). Gap 3 carries the 200% replacement cost every time a pipeline turns out to be fiction. Gap 4 carries a regulatory tail that can exceed all the others combined. The cause is the same in all four. So is the fix. ## Where MangoApps fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and the Performance & Learning suite closes all four gaps the same way: by putting performance, goals, succession, and skills on one shared data layer instead of four disconnected tools. Because the data is connected, the AI built into the suite can surface retention risk, succession readiness, and certification gaps continuously, without anyone running the analysis. The intelligence isn't bolted on. It is what a single data model makes possible. ![Diagram showing one data layer connecting performance, goals, succession, and skills and certifications capabilities, including reviews, OKRs, role mapping, and skill tracking.](https://mango-cdn.b-cdn.net/marketing/uploads/one-data-layer.png) None of that matters if employees don't use it, which is why adoption is the number that anchors the rest. MangoApps reaches 90%+ adoption within 90 days because the full performance experience lives in the app employees already open, on any device, with no separate login. High adoption is not a vanity metric. It is the prerequisite for performance data you can act on, and it is backed by the Adoption Guarantee: if your people don't adopt after launch, you don't pay. ## Frequently asked questions **What are the main causes of performance review failure?** Most review failures are not caused by bad managers or bad templates. They trace to fragmented information: performance data spread across five or more systems, goals that go invisible between cycles, succession plans that reflect the last talent review rather than today, and skills or certification records that are out of date. When the data is scattered, the review gets reconstructed from memory, and recency bias does the rest. **How many hours do performance reviews actually take?** In a 5,000-employee organization, just assembling the data for reviews can consume 3,000 to 4,000 hours a year, roughly 500 managers running two cycles annually at three to four hours each to compile a picture from multiple systems (MangoApps benchmark model). That is time spent gathering information, before any development conversation happens. **How do you fix a broken performance management process?** Cadence changes and new templates don't fix a reconstruction problem, because the underlying data is still scattered. The durable fix is putting performance, goals, succession, and skills on one shared data layer so the review is retrieved rather than rebuilt, and pairing that with adoption high enough that the data is actually complete. **Is this only for desk-based teams?** No. The four gaps hit frontline and deskless employees hardest, because they are the ones most often left out of desk-bound HR tools. Delivering performance, goals, and recognition on the app employees already carry is what makes the data complete across the whole workforce, not just the corporate layer. > **Find out how many gaps are open in your organization:** we'll walk your current process against the four gaps with you and show where the data breaks. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book) - [Performance & learning](https://www.mangoapps.com/solutions/performance-learning) - [Workforce planning](https://www.mangoapps.com/solutions/workforce-planning) - [Analytics & insights](https://www.mangoapps.com/analytics-insights) --- # A Year in the Life of a Review Cycle, and Why It Changes Nothing **Author:** Christos Schrader **Published:** 2026-07-10 **Category:** Best Practices Performance reviews break when goals, feedback, and skills live in separate systems. A shared data layer makes the full picture available all year. Ask a VP of Talent Management to describe their performance process and you'll hear it in the present tense: quarterly check-ins, a competency framework, a 360 that pulls from peers and direct reports. Then watch one cycle run end to end. What you see is a manager rebuilding a year from memory, an employee bracing for a number, and a set of goals nobody has opened since January. The review isn't broken because managers don't care. It's broken because the information they needed was never in one place. ![Three statistic cards highlight workplace performance insights: managers interact with five or more disconnected systems per review cycle, 14% of employees say reviews inspire improvement, and 29% say manager feedback helps them work better.](https://mango-cdn.b-cdn.net/marketing/uploads/why-review-arent-working.png) Only 14% of employees strongly agree their reviews inspire them to improve (according to Gallup). That is not a motivation problem. It is what happens when the picture gets assembled the night before instead of accumulating all year. Here is how the year actually runs. ## January: The Goals Go In, and the Tool Goes Quiet OKRs get entered with real intent. Leadership sets direction, teams cascade objectives, individuals write key results. Then the tool that holds them gets opened roughly twice more before the year is out. The goals are documented. They are not directing anything. By the second week of February, most people would need a login reminder to find them. ## March: The Cadence Slips The check-in rhythm that looked sustainable in the planning meeting meets the actual quarter. A reorg, a launch, a hiring push. The check-ins are the first thing to fall off. Goals quietly become a list of intentions, and the only person tracking progress is the individual contributor, in their own notes, in a format nobody else can see. ## October: Five Systems, One Night Review season arrives and the reconstruction begins. A typical manager touches five or more disconnected systems to compile a single employee's picture (according to Gallup): the goals tool, the HRIS, a spreadsheet of notes, the recognition feed if there is one, and email. None of them talk to each other. Recency bias fills every gap, because the last eight weeks are the only weeks anyone can actually remember. The full-year view doesn't exist. It gets rebuilt, imperfectly, under time pressure. ## November: The Number Nobody Saw Coming The employee sits down to a rating shaped more by the recent quarter than by the year. The manager delivers feedback assembled from fragments. The conversation that was supposed to drive growth becomes a ritual that drives compliance. Both people leave the room having spent real time on something that changed nothing. In January, the cycle starts again on exactly the same footing. ## What the Calendar Is Actually Showing You Read those four moments together and the pattern is not a series of individual failures. It is one structural fact showing up four times: performance data, goal progress, feedback, and skills history live in separate places, so the review has to be manufactured rather than retrieved. That's not a process failure. It's an infrastructure failure. Fix the cadence and you still have the reconstruction problem. Add another survey and you add another system to the October pile. The only thing that changes the year is putting the underlying data on one layer, so the picture is already there when the manager walks in. The goal isn't to make the review easier in a cosmetic sense. It's to give managers what they should have had the whole time. > **Read the whole argument:** this is one year of one cycle. [*Performance & Growth*](https://www.mangoapps.com/resources/performance-growth-book) traces all four information gaps behind it, with the cost model and the customer proof. ## Where MangoApps Fits MangoApps is the Enterprise Workforce Platform Built for the Frontline, and the Performance & Learning suite runs on a single shared data layer: reviews, goals, 360 feedback, succession, and skills built as one system, not stitched together through integrations. OKR progress and 360 responses flow into the review view automatically, so October's five-system scramble simply doesn't happen. The AI built across the suite works on that same connected data, surfacing a retention risk or a widening succession gap before a talent review would catch it. AI is not the headline here. It is what a shared data layer makes possible. ![Diagram showing one data layer connecting performance, goals, succession, and skills and certifications capabilities, including reviews, OKRs, role mapping, and skill tracking.](https://mango-cdn.b-cdn.net/marketing/uploads/one-data-layer.png) The reason the data is worth trusting is that people actually use the system. MangoApps reaches 90%+ adoption within 90 days because performance lives inside the app employees already open, with no separate login. That adoption is backed by the Adoption Guarantee: if your employees don't adopt MangoApps after launch, you don't pay. No other vendor in this category makes that commitment. The first review cycle on the platform is better than the last one off it, because the picture was assembling itself all year. > **See what a review built from a record looks like:** walk your own cycle through the Performance & Learning suite with our team and see where the reconstruction disappears. [Schedule a call →](https://www.mangoapps.com/schedule-a-call) ## Keep reading - [*Performance & Growth Ebook*](https://www.mangoapps.com/resources/performance-growth-book) - [Performance & Learning Suite](https://www.mangoapps.com/solutions/performance-learning) - [Merchants Bonding case study](https://www.mangoapps.com/resources/merchants-bonding-case-study) - [Columbia Basin Health case study](https://www.mangoapps.com/resources/columbia-basin-health-associate-case-study) --- # MangoApps Named to the KMWorld AI 100 for the Second Year in a Row **Author:** MangoApps Team **Published:** 2026-07-07 **Category:** news-and-updates MangoApps has been named to the 2026 KMWorld AI 100 and KMWorld 100 for the second year running, recognizing its AI-powered knowledge management. We're proud to announce that MangoApps has been named to the [2026 KMWorld AI 100](https://www.kmworld.com/Articles/Editorial/Features/2026-The-KMWorld-AI-100-The-Impact-of-AI-on-KM-is-Inescapable-174988.aspx), KMWorld's list of the companies empowering intelligent knowledge management, for the second consecutive year. It's recognition we're glad to have, and it lands alongside another honor: MangoApps has also been named to the broader KMWorld 100 for two years running. Two lists, two years, one direction of travel. ## What Is the KMWorld AI 100? Each year, KMWorld identifies 100 companies whose AI capabilities are changing how organizations capture, organize, surface, and act on knowledge. As KMWorld put it in this year's feature, AI's impact on knowledge management is inescapable: millions of people now interact with chatbots and language models as a normal part of work, and that shift is forcing knowledge managers to rethink how information gets captured, governed, and delivered. The AI 100 isn't a popularity contest. It recognizes companies with real AI-driven approaches to long-standing knowledge problems, not vendors bolting a chatbot onto an old product. KMWorld's own description of MangoApps on this year's list: we're "redefining the work experience" and connect "people, knowledge, tools, and AI" across the entire workforce. Making the AI 100 once said something. Making it twice, alongside a second straight year on the KMWorld 100, says the direction we've committed to is holding up. ## Why AI Changes the Knowledge Management Problem Most organizations don't have a knowledge shortage. They have a knowledge access problem. The answer exists somewhere: buried in a shared drive, locked in a wiki nobody's updated since March, sitting in the memory of the person who's been there twelve years, or scattered across five tools that don't talk to each other. AI doesn't fix that by itself. A chatbot layered on top of fragmented systems just answers questions faster from the wrong data, or from data it was never permitted to see. The knowledge access problem is a platform problem before it's an AI problem. AI needs shared identity, permissions, and a single source of workflow context to be trustworthy enough to act on. Without that foundation, it's a novelty. With it, AI becomes the layer that finally makes an organization's knowledge usable at the moment someone needs it, whether that's a corporate employee at a desk or a shift supervisor on a warehouse floor who's never had a company email address. That's the problem MangoApps was built to solve, and it's why this year's AI 100 recognition means more than last year's. ## What Sets MangoApps Apart in 2026 **AI grounded in your own knowledge, not a generic chatbot.** MangoApps AI gives every employee, from the VP of HR at corporate to the shift supervisor at a distribution center, an assistant trained on the company's actual content. It answers questions grounded in real internal knowledge, works across languages and devices, and respects the same permissions that govern the rest of the platform. **One platform, not another point solution stacked on top.** Knowledge doesn't live in one place, but finding it should feel like it does. MangoApps runs intranet, communications, frontline operations, HR, and AI on a single platform with one identity and one data model. Customers routinely retire four or five point solutions after go-live, and that consolidation is a knowledge management outcome as much as a cost one: information is only findable when it isn't scattered across systems with no shared context. **Enterprise security that knowledge governance actually requires.** MangoApps holds active HITRUST certification alongside ISO 27001 and SOC 2 Type II, security no other employee platform in the category matches. For healthcare, financial services, and retail organizations where knowledge access and data governance have to coexist, that's not optional. **Adoption that holds up after the announcement.** Recognition only means something if people use the platform. MangoApps sees 90%+ adoption within 90 days of launch, 98% customer retention, and an NPS of 78. Knowledge management only creates value when employees actually engage with it, not when it sits unused after a launch email. ## What This Recognition Means to Us MangoApps has spent 18+ years in this market, serving 2 million-plus users worldwide. We've watched knowledge management move from static intranets and document libraries to AI-driven platforms that have to work as well for a nurse on a 12-hour shift as they do for a knowledge worker at a desk. Two years on the KMWorld AI 100, and two years on the KMWorld 100 alongside it, tells us the platform bet we've made, AI grounded in real work rather than bolted on as a feature, is the one the market is validating. We're grateful to KMWorld for the recognition, and more grateful to the customers whose adoption is what actually earns it. Interested in seeing how MangoApps approaches AI-powered knowledge management for your organization? [Request a personalized demo](https://www.mangoapps.com/schedule-a-call) and we'll show you what's possible. --- # Choosing a UK Enterprise Intranet in 2026: A Buyer's Guide **Author:** MangoApps Team **Published:** 2026-07-06 **Category:** intranet Choose an intranet platform that meets UK GDPR, data residency, Microsoft 365, and frontline reach requirements before you shortlist vendors. **Quick answer:** For a UK enterprise, choosing among employee intranet platforms is as much a governance and security decision as a communications one. The platforms that clear procurement are the ones that satisfy UK GDPR and the Data Protection Act 2018, offer clear data residency, hold certifications your InfoSec team already recognises (ISO 27001, SOC 2 Type II, Cyber Essentials Plus), coexist cleanly with Microsoft 365, and still reach every employee, including the frontline and multi-site staff who never open a work email. Before comparing features, agree three things across IT, internal communications, and HR: where your data lives and who governs it, how the platform reaches your whole workforce, and whether adoption will hold across regions two years after launch. This guide sets out those criteria and complements our in-depth ranking of the [best intranet platforms for UK enterprises in 2026](https://www.mangoapps.com/articles/best-intranet-platforms-for-uk-enterprises). > **See the platform-by-platform comparison:** our companion guide ranks the leading enterprise intranet solutions by UK data residency, Microsoft 365 fit, security posture, and workforce reach. [Read the best intranet platforms for UK enterprises](https://www.mangoapps.com/articles/best-intranet-platforms-for-uk-enterprises). ## Why the UK enterprise intranet decision is different Most buying advice for employee intranet platforms is written for a single-site, desk-based organisation in a light-touch regulatory environment. UK enterprises rarely fit that profile. You are likely balancing multiple sites and possibly multiple countries, a mix of office and frontline staff, works councils or trade union relationships, and a data protection regime with real teeth. That combination changes what a good platform looks like. Three forces shape the decision. Governance and security come first, because a platform that cannot satisfy the Information Commissioner's Office (ICO) expectations, UK GDPR, and your own InfoSec review will not survive procurement regardless of how good the interface looks. Internal communications come second, because a UK enterprise measures a platform by whether a message actually reaches a shift worker in Leeds and a head-office team in London with equal reliability. Adoption comes third, and it is where most enterprise rollouts quietly fail: a platform can pass every technical gate and still stall at 30% usage because it was designed for people at desks. The practical implication is that a UK enterprise should treat this as a cross-functional decision from day one. Enterprise IT owns security and integration, internal communications owns reach and messaging, and HR and employee experience own adoption and the day-to-day value. When those three evaluate in isolation, you get a platform that satisfies one and disappoints the other two. For the full landscape of vendors assessed against these UK-specific priorities, our ranking of the [best intranet platforms for UK enterprises in 2026](https://www.mangoapps.com/articles/best-intranet-platforms-for-uk-enterprises) is the companion to this framework. ## Governance and security: the criteria procurement will ask about This is the section that determines whether a platform is even eligible. For large enterprise software in the UK, expect your InfoSec, legal, and procurement teams to require clear answers on the following before a pilot is approved. **Data protection and residency.** Confirm compliance with UK GDPR and the Data Protection Act 2018, and ask precisely where data is stored and processed. Many enterprises require UK or EU/EEA data residency, and any transfer outside that boundary needs a lawful mechanism such as the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses. Get the answer in writing, not in a sales deck. **Certifications your team already recognises.** ISO 27001 and SOC 2 Type II are the baseline for enterprise. Cyber Essentials or Cyber Essentials Plus is frequently expected in the UK, particularly for public sector and regulated industries, and healthcare buyers will look for HITRUST or equivalent. A platform that holds these lets your security team map to a known standard rather than assess from scratch. **Access control and identity.** Role-based access control, single sign-on through your existing identity provider (Microsoft Entra ID, Okta, or similar), and multi-factor authentication are non-negotiable at enterprise scale. Granular permissions matter when a single platform spans multiple business units, regions, or brands. **Auditability and records.** Enterprises need audit logs, retention controls, and the ability to demonstrate who saw what and when, both for internal governance and for responding to a data subject access request. This is also where read-receipt reporting on communications doubles as a compliance record. Governance is not a box-ticking exercise you can defer. Getting these requirements agreed with IT and legal before you shortlist saves weeks of rework later. > **Shortlist against the right criteria.** The [best intranet platforms for UK enterprises](https://www.mangoapps.com/articles/best-intranet-platforms-for-uk-enterprises) guide scores vendors on data residency, certifications, and Microsoft 365 fit so your security review starts from a stronger position. ## Internal communications at enterprise scale Once a platform is eligible, the question internal communications leaders should ask is simple: can we prove a message landed? At enterprise scale, corporate communication tools that only publish content are not enough. You need to target the right message to the right audience and measure whether it was seen. Look for a central news feed with audience segmentation by role, location, department, or business unit, so a regional safety notice reaches the right sites without spamming everyone. Read receipts and reach reporting turn communication from a broadcast into something measurable. Multilingual and translation support matters for a UK enterprise with international operations or a multilingual frontline. Urgent alerts through push and SMS give you a reliable channel for time-critical messages that email cannot match. And two-way channels, comments, reactions, and pulse surveys, let leadership hear back rather than only speak. The failure mode to avoid is a platform where important updates compete with everything else in an untargeted feed and no one can say whether the message reached the people it mattered to. Modern internal communication platforms treat reach as a metric, not an assumption. ## Reaching the whole workforce, not just desk staff This is where enterprise intranet solutions most often fall short, and it is worth stating plainly because it is easy to overlook in a head-office demo. A large share of most enterprises' people are frontline or multi-site: retail associates, warehouse and logistics staff, care workers, manufacturing operators, field engineers. Globally, frontline employees make up roughly 70 to 80% of the workforce (according to BCG and JLL), and only 23% of frontline workers feel they have the digital tools to do their job well (according to Deloitte). A UK enterprise intranet that only serves the people with a laptop and a corporate email address is serving a minority. Reaching everyone requires a genuinely mobile-first platform: a branded app that works on the personal phone an employee already carries, sign-in that does not depend on a corporate email account, offline access, and strong performance on low-bandwidth connections. These capabilities separate a true enterprise platform from a desk-first tool with a mobile view bolted on. We cover the specific requirements in [9 modern intranet features that reach frontline staff without email](https://www.mangoapps.com/articles/intranet-features-that-reach-frontline-workers), and the common ways legacy platforms exclude these employees in [7 intranet problems hurting frontline teams](https://www.mangoapps.com/articles/intranet-problems-hurting-frontline-teams). ## The evaluation framework: aligning IT, comms, and HR A structured evaluation keeps a large enterprise software decision from being won by the best demo rather than the best fit. A workable eight-step process: 1. Agree must-haves versus nice-to-haves across IT, internal communications, and HR before contacting vendors, so security, reach, and adoption all have a seat at the table. 2. Survey the landscape and shortlist 5 to 8 platforms that serve enterprises at your scale, using neutral sources such as the Gartner Magic Quadrant, the Forrester Wave, and validated peer reviews. 3. Issue a focused RFP that asks for descriptive answers on data residency, certifications, integration, and workforce reach, not yes or no boxes. 4. Narrow to two or three finalists and script demos around your real workflows, including a frontline scenario, not the vendor's showcase. 5. Run a pilot in one region or business unit against metrics you set in advance. 6. Complete due diligence: reference calls with UK enterprises in your sector, plus formal IT security and legal review. 7. Score against your agreed criteria and document the rationale for governance. 8. Negotiate from an informed position and commit support and data terms in writing. For a deeper treatment of the criteria that actually predict success, including whether adoption holds 24 months after launch, see [how to evaluate employee intranet platforms in 2026](https://www.mangoapps.com/articles/evaluate-employee-intranet-platforms-2026). If you are replacing a legacy portal rather than buying for the first time, [how to replace an outdated intranet in 2026](https://www.mangoapps.com/articles/how-to-replace-an-outdate-intranet-in-2026) covers diagnosing failure and scoping the migration. ## Integration and the UK digital workplace For most UK enterprises, the intranet does not replace the digital workplace, it organises it. Microsoft 365 is the near-universal backbone, so coexistence with SharePoint, Teams, and Entra ID is essential: the platform should surface and search Microsoft 365 content rather than forcing a duplicate silo. Beyond Microsoft, expect to integrate with your HRIS, identity provider, and the line-of-business systems your teams use daily. AI-powered search that works across those connected systems is what turns a collection of tools into a coherent UK digital workplace, so an employee finds the current policy or SOP in a few taps rather than hunting across five places. Consolidation is also a cost argument at enterprise scale. Every point tool the platform can absorb, whether that is a separate comms app, a survey tool, or a recognition platform, reduces licence spend, integration overhead, and the number of logins employees have to remember. For a broader view of the market, our comparisons of the [best intranet software of 2026](https://www.mangoapps.com/articles/best-intranet-software-2026) and the [best employee experience platforms of 2026](https://www.mangoapps.com/articles/best-employee-experience-platforms) evaluate the leading options by fit. ## Measuring success across regions A UK enterprise should define success metrics before launch and review them by region, because a platform can perform well at head office and poorly on the frontline, and an aggregate number hides that. Useful benchmarks include an adoption target such as 90% of employees active within the first two months, weekly active usage around 75%, communication reach of 70 to 80% on priority updates, and rising completion rates on tasks and required training. Tie those platform metrics back to the outcomes the business funded: retention, absence, safety incidents, and internal communication effectiveness. A weekly review for the first 60 to 90 days, monthly thereafter, and a quarterly executive summary keeps the rollout honest and gives IT, comms, and HR a shared scorecard. ## Where MangoApps fits MangoApps is the AI-Ready Employee Platform for the Frontline, and it is built for exactly the profile most UK enterprises have: a mix of office and frontline staff across multiple sites. Teams start with the apps or workflows they need today and expand across Employee Experience, Frontline Operations, and People Operations on the same foundation, without rebuilding identity, permissions, integrations, data, or AI governance. That architecture is why adoption holds where legacy platforms stall at 30 to 40%. MangoApps customers average above 90% adoption within 90 days, because the platform was built for employees with no desk, no corporate email, and no laptop, for 18 or more years, rather than retrofitted after the fact. AI is grounded in the work itself, respecting permissions and drawing only on approved content, rather than a chatbot bolted onto a content library. The platform supports enterprise security and identity requirements, integrates with Microsoft 365 and common HR and identity systems, and is backed by an Adoption Guarantee: if your employees do not adopt after launch, you do not pay. The result across the customer base is 2 million or more users worldwide, 98% customer retention, and a Net Promoter Score of 78. This guide is written to help you evaluate any qualified vendor, not just MangoApps. The requirements it describes happen to be the ones we have spent since 2008 building for. > **Compare your shortlist.** Read the [best intranet platforms for UK enterprises in 2026](https://www.mangoapps.com/articles/best-intranet-platforms-for-uk-enterprises), or [see how MangoApps compares](https://www.mangoapps.com/compare) against the platforms you are evaluating. ## Frequently asked questions **What are the best employee intranet platforms for UK enterprises in 2026?** The strongest platforms for UK enterprises combine UK GDPR compliance and clear data residency, recognised certifications such as ISO 27001, SOC 2 Type II, and Cyber Essentials Plus, clean coexistence with Microsoft 365, and genuine mobile-first reach for frontline and multi-site staff. Our companion guide ranks the leading enterprise intranet solutions against these criteria. **What UK data protection requirements should an enterprise intranet meet?** It should comply with UK GDPR and the Data Protection Act 2018, offer clear data residency (often UK or EU/EEA), provide role-based access with SSO and MFA, maintain audit logs and retention controls, and use a lawful transfer mechanism such as the UK International Data Transfer Agreement for any data leaving the UK. Verify all of this in writing during procurement. **How should IT, internal communications, and HR divide the evaluation?** Enterprise IT should own security, data residency, and integration; internal communications should own audience targeting, reach, and measurement; HR and employee experience should own adoption and day-to-day value. Agreeing must-haves across all three before shortlisting prevents a platform that satisfies one function and disappoints the others. **Do enterprise intranet platforms integrate with Microsoft 365?** Leading platforms coexist with Microsoft 365 rather than replace it: they integrate with SharePoint, Teams, and Entra ID for single sign-on, and surface Microsoft 365 content through unified, AI-powered search so employees do not maintain duplicate silos. This is a core requirement for most UK digital workplace strategies. **How do we make sure frontline and multi-site staff actually use the platform?** Choose a mobile-first platform with a branded app that works on personal devices, sign-in that does not require a corporate email address, offline access, and targeted communication with read receipts. Then measure adoption by region rather than in aggregate, because head-office usage can mask low frontline adoption. ## Keep reading - [Best intranet platforms for UK enterprises in 2026](https://www.mangoapps.com/articles/best-intranet-platforms-for-uk-enterprises) - [How to evaluate employee intranet platforms in 2026](https://www.mangoapps.com/articles/evaluate-employee-intranet-platforms-2026) - [Best intranet software of 2026: top platforms compared](https://www.mangoapps.com/articles/best-intranet-software-2026) - [Best employee experience platforms of 2026](https://www.mangoapps.com/articles/best-employee-experience-platforms) - [9 modern intranet features that reach frontline staff without email](https://www.mangoapps.com/articles/intranet-features-that-reach-frontline-workers) - [7 intranet problems hurting frontline teams](https://www.mangoapps.com/articles/intranet-problems-hurting-frontline-teams) - [How to replace an outdated intranet in 2026](https://www.mangoapps.com/articles/how-to-replace-an-outdate-intranet-in-2026) - [25 intranet platforms worth evaluating in 2026](https://www.mangoapps.com/articles/top-25-intranet-platforms-frontline-desk-workers) - [UK enterprise criteria, SharePoint-replacement routes, and no-email platforms in the Top 25](https://www.mangoapps.com/articles/top-25-intranet-platforms-frontline-desk-workers#what-do-large-uk-enterprises-need-in-an-intranet-platform-10-evaluation-criteria) - [Best intranet platforms for UK enterprises in 2026](https://www.mangoapps.com/articles/best-intranet-platforms-for-uk-enterprises) --- # How to Choose an Intranet for a Frontline Workforce in 2026: A Buyer's Framework **Author:** Andy Tolton **Published:** 2026-07-06 **Category:** intranet A decision framework for choosing an intranet built for deskless teams: what to evaluate, what most rollouts miss, and the data behind the business case. Plus a free buyer's guide. **Quick answer:** Choosing an intranet for a frontline workforce is a different decision than choosing one for desk staff. The platforms that win are the ones frontline employees actually open on the phone they already carry, without a corporate email address, a laptop, or a login they will forget. Before you build a features spreadsheet, decide three things: who the platform was truly built for, what it does beyond publishing content, and whether adoption will still hold two years after launch. This article walks through that framework and pulls key data and checkpoints from [The Ultimate Intranet Buyer's Guide for a Frontline Workforce](https://www.mangoapps.com/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026), a free, no-email-required resource you can use to run the full evaluation. > **Get the complete playbook:** business case model, requirements checklist, an 8-step vendor evaluation process, and a phased implementation roadmap. [Download the free buyer's guide](https://www.mangoapps.com/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) (no email needed). ## Why frontline intranet selection is a different decision Most intranet buying advice assumes a workforce that sits at a desk, carries a company laptop, and lives in email. That workforce is the minority. Frontline employees, the people stocking shelves, running production lines, delivering packages, and staffing care facilities, make up roughly 70 to 80% of the global workforce, about 2.7 billion people, and 58% of the U.S. workforce (according to BCG and JLL). They power the business, and they are the group most likely to be excluded by the systems meant to inform and align it. That exclusion is structural, not accidental. A traditional intranet assumes a corporate email address, a desk, and unstructured time to log in between meetings. Every one of those assumptions leaves out a store associate, a charge nurse, or a warehouse technician before the first page is even published. This is why a platform that scores well on a generic features checklist can still land at 30% adoption: it was never built for the people who make up the majority of the workforce. The practical takeaway is simple. If most of your people are frontline, the criteria that predict success are not the same criteria a desk-first buyer's guide will hand you. You are not buying a place to store documents. You are buying reach. For the full landscape of platforms evaluated through this lens, our [25 intranet platforms worth evaluating in 2026](https://www.mangoapps.com/articles/top-25-intranet-platforms-frontline-desk-workers) guide ranks every major vendor with mobile access, deskless usability, and operational depth carrying real weight. ## What is actually broken today Before you evaluate anything new, it helps to name precisely what is failing. The buyer's guide breaks this down, and the pattern is consistent across retail, healthcare, manufacturing, and logistics: - **Frontline workers do not have the tools they need.** Only 23% of frontline employees feel they have the digital tools to do their job effectively (according to Deloitte). - **Official channels never reach them, so shadow channels fill the gap.** Roughly 67% of frontline workers rely on ad hoc manager updates or informal texts for critical information. And 55% of collaborative apps start as unauthorized tools employees adopt to fill a gap (according to IDC). WhatsApp and personal group chats become the real intranet. - **People stop believing their voice matters.** Only one in four employees strongly agree their opinions count at work, and just 8% believe leadership acts on their feedback (according to Gallup). Only two in ten feel genuinely connected to their company's culture. - **The result is burnout and churn.** 53% of frontline workers report burnout and 43% are actively looking for another job (according to BCG). When a policy change does not reach the warehouse floor, compliance risk climbs. When a safety update stalls at the managerial layer, injury risk climbs. These are not soft problems. We cover the specific failure patterns in [7 intranet problems hurting frontline teams](https://www.mangoapps.com/articles/intranet-problems-hurting-frontline-teams), and if your current platform is a decade-old portal built for a 2005 problem, [how to replace an outdated intranet in 2026](https://www.mangoapps.com/articles/how-to-replace-an-outdate-intranet-in-2026) walks through diagnosing failure and scoping the replacement. ## The cost of doing nothing: building the business case The strongest evaluations start by connecting frontline gaps to outcomes leaders already care about: retention, productivity, safety, and customer experience. The guide's business case section gives you the model. A few of the numbers worth carrying into your own proposal: - **Turnover runs hot on the frontline.** Frontline attrition outpaces office roles by two to three times, and in manufacturing by 3.6x (according to JLL). Replacing frontline workers can cost from roughly 40% up to 200% of annual salary depending on the role (according to Gallup). In a 1,000-person frontline operation, cutting turnover from 40% to 30% avoids 100 replacements a year. - **Information access is a silent productivity tax.** Desk workers spend about 14 hours a week searching for information; frontline staff spend around 3 (according to IDC). A modern hub with AI-powered search can cut that by 25 to 80%. - **Miscommunication is a safety issue.** In healthcare, 80% of serious medical errors involve miscommunication during shift handoffs (according to The Joint Commission). - **Engagement shows up on the P&L.** Highly engaged teams deliver around 21% higher productivity and more than 20% growth in sales, and high-engagement workplaces see 41% fewer absences (according to Gallup and BCG). The guide also shows how to frame the case for each stakeholder, because a CFO, a COO, an HR leader, and a communications leader are each buying a different outcome. And it includes a free one-page business case template you can populate with your own team size and priorities. > **Build the case with real numbers.** The buyer's guide includes an editable business case model, hard and soft ROI examples, and stakeholder framing. [Grab the free guide here.](https://www.mangoapps.com/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) ## What to look for in a frontline-ready platform Feature lists blur together because every vendor claims everything. The requirements that actually separate a frontline-ready platform are narrower and less negotiable. The guide details them in full; here is the short version. **Mobile-first access with no email dependency.** The platform has to work on the phone an employee already owns, with sign-in that does not require a corporate email account. Push and SMS notifications, offline mode, biometric or SSO login, and strong performance on low-bandwidth connections are essentials, not extras. This single requirement disqualifies most desk-first tools. We break down the specific capabilities in [9 modern intranet features that reach frontline staff without email](https://www.mangoapps.com/articles/intranet-features-that-reach-frontline-workers). **Communication you can prove landed.** A central news feed with audience targeting, read receipts, rich and multilingual content, real-time messaging, and urgent alerts. Reach is only real if you can measure it. **Knowledge and documents without a hunt.** SOPs, policies, and job-critical information available in a few taps, with AI-powered search that works across existing systems like Microsoft 365 and Google Drive. Every minute spent searching is a minute not spent serving a customer or patient. **Feedback, recognition, and training in the flow of work.** Pulse surveys, peer and manager recognition, and bite-sized mobile learning close the loop that makes frontline employees feel seen and supported. **Integration and consolidation.** The platform should connect to the HRIS, identity provider, and content systems you already run, and replace the point tools you do not need. Consolidation is what drives both adoption and cost savings. **Security and compliance that hold up in a regulated industry.** Encryption in transit and at rest, role-based access with MFA and SSO, and certifications like SOC 2 Type II, ISO 27001, and HITRUST for healthcare. If you want a structured way to weigh these instead of a flat checklist, [how to evaluate employee intranet platforms in 2026](https://www.mangoapps.com/articles/evaluate-employee-intranet-platforms-2026) lays out the six criteria that actually determine success, including whether adoption holds 24 months after launch. ## How to run the evaluation without getting fooled by demos A polished demo tells you what a platform can do in ideal conditions. It does not tell you what your frontline will do with it on a Tuesday. The guide's vendor evaluation toolkit gives you an eight-step process to get past the pitch: 1. Survey the landscape and identify 5 to 8 candidates that serve frontline-heavy sectors, using neutral sources like the Gartner Magic Quadrant, the Forrester Wave, and validated peer reviews. 2. Define must-haves versus nice-to-haves before you talk to a single vendor. 3. Prepare a focused RFP or RFI that asks for descriptive answers, not yes or no boxes. 4. Shortlist to two or three finalists and script the demos around your real workflows. 5. Pilot in one location or region against metrics you set in advance. 6. Do due diligence: talk to two or three reference customers in your industry, and involve IT and compliance. 7. Score against your criteria and document the rationale. 8. Negotiate from an informed position and lock support commitments in writing. The guide includes two free tools to make this concrete: an editable RFP template with more than 50 questions tailored to frontline platforms, and a vendor scorecard spreadsheet for side-by-side comparison. To see how specific products stack up while you build your shortlist, our comparisons of the [best intranet software of 2026](https://www.mangoapps.com/articles/best-intranet-software-2026), the [best intranet platforms for frontline teams](https://www.mangoapps.com/articles/best-employee-intranet-frontline-teams), and the [best employee experience platforms of 2026](https://www.mangoapps.com/articles/best-employee-experience-platforms) each evaluate the major vendors by workforce fit. Teams operating in the UK should also review the [best intranet platforms for UK enterprises](https://www.mangoapps.com/articles/best-intranet-platforms-for-uk-enterprises), which weighs UK GDPR data residency and Microsoft 365 fit alongside frontline reach. ## Why most rollouts stall, and how to plan around it Selecting a platform is the milestone everyone celebrates. The launch is where the value is won or lost. The guide's implementation roadmap covers nine phases, from cross-functional kickoff and user research through pilot, full rollout, and continuous improvement. Two points matter most for the frontline. First, frontline managers are the linchpin. When a store or site manager posts announcements, tracks task completion, and models daily use, their team follows. Many successful rollouts launch with managers first to build peer champions across locations. Second, momentum is fragile. The guide includes a red-flags checklist for catching problems early: adoption stuck below 30 to 40%, low read rates on important announcements, integration or data-sync issues, and vendor responsiveness that slips after signing. Each red flag comes with a concrete remedy so a soft launch does not quietly become a failed one. ## How to measure success after launch If you cannot measure it, you cannot defend the investment. The guide's measurement section pairs platform KPIs with business outcomes. Common frontline benchmarks include an adoption target such as 90% of frontline workers logging in within two months, weekly active usage around 75%, content reach of 70 to 80% on top-down updates, and rising task and workflow completion rates. Those tie back to the outcomes leadership funded: turnover, absenteeism, safety incidents, and customer experience. The recommended cadence is weekly review for the first 60 to 90 days, monthly after that, and a quarterly summary for executives. ## Where MangoApps fits MangoApps is the AI-Ready Employee Platform for the Frontline. The platform decision comes first, and teams start with the apps or workflows they need today, then expand across Employee Experience, Frontline Operations, and People Operations on the same foundation, without rebuilding identity, permissions, integrations, data, or AI governance. That architecture is why the numbers hold. Legacy intranets average 30 to 40% adoption. MangoApps customers average above 90% within 90 days, because the platform was built for employees with no desk, no corporate email, and no laptop, for 18 or more years, not retrofitted after the fact. AI is grounded in the work itself, respecting permissions and using only approved content, rather than a chatbot bolted onto a content library. The result: 2 million or more users worldwide, 98% customer retention, and a Net Promoter Score of 78, backed by an Adoption Guarantee. If your employees do not adopt after launch, you do not pay. The buyer's guide is written to help you evaluate any qualified vendor, not just MangoApps. The requirements it describes happen to be the ones we have spent since 2008 building for. > **Ready to run your evaluation?** [Download The Ultimate Intranet Buyer's Guide for a Frontline Workforce](https://www.mangoapps.com/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026), or [see how MangoApps compares](https://www.mangoapps.com/compare) against the platforms on your shortlist. ## Frequently asked questions **What is a frontline intranet?** A frontline intranet is an employee platform designed for workers who do their jobs away from a desk, such as retail associates, nurses, factory workers, and drivers. Unlike a traditional intranet, it reaches employees on personal mobile devices without requiring a corporate email address or company laptop, and it delivers communication, knowledge, tasks, and recognition in one mobile-first app. **Why do traditional intranets fail with frontline workers?** Traditional intranets assume a desk, a company laptop, and a corporate email address. Roughly 70 to 80% of the global workforce is frontline and has none of those by default, so adoption stalls. Only 23% of frontline employees feel they have the digital tools they need to do their job (according to Deloitte), and most rely on informal texts or manager updates for critical information. **What should I look for when choosing a frontline intranet in 2026?** Prioritize mobile-first access with no email dependency, communication with read-receipt tracking, AI-powered search across existing systems, in-app feedback and recognition, integration with your HRIS and identity provider, and enterprise security such as SOC 2 Type II, ISO 27001, and HITRUST. Then evaluate who the platform was built for and whether adoption will hold two years after launch. **How do I build the business case for a frontline intranet?** Connect frontline gaps to outcomes leadership already funds: turnover reduction, productivity, safety, and customer experience. Frontline turnover runs two to three times higher than office roles (according to JLL), and engaged teams deliver around 21% higher productivity (according to Gallup). The free buyer's guide includes an editable one-page business case template and stakeholder framing for CFOs, COOs, HR, and communications leaders. **Is the MangoApps buyer's guide free?** Yes. The Ultimate Intranet Buyer's Guide for a Frontline Workforce is available as a free download with no email required, and it includes a business case model, a requirements checklist, an eight-step vendor evaluation toolkit, an implementation roadmap, and a red-flags checklist. ## Keep reading - [25 intranet platforms worth evaluating in 2026: a frontline-first buyer's guide](https://www.mangoapps.com/articles/top-25-intranet-platforms-frontline-desk-workers) - [Best intranet software of 2026: top platforms compared](https://www.mangoapps.com/articles/best-intranet-software-2026) - [Best intranet platforms for frontline teams in 2026](https://www.mangoapps.com/articles/best-employee-intranet-frontline-teams) - [Best employee experience platforms of 2026](https://www.mangoapps.com/articles/best-employee-experience-platforms) - [Best intranet platforms for UK enterprises in 2026](https://www.mangoapps.com/articles/best-intranet-platforms-for-uk-enterprises) - [How to evaluate employee intranet platforms in 2026](https://www.mangoapps.com/articles/evaluate-employee-intranet-platforms-2026) - [9 modern intranet features that reach frontline staff without email](https://www.mangoapps.com/articles/intranet-features-that-reach-frontline-workers) - [How to replace an outdated intranet in 2026](https://www.mangoapps.com/articles/how-to-replace-an-outdate-intranet-in-2026) - [7 intranet problems hurting frontline teams](https://www.mangoapps.com/articles/intranet-problems-hurting-frontline-teams) --- # The Missing Step in Every Frontline Training Program **Author:** MangoApps Team **Published:** 2026-07-05 **Category:** workforce-management A new shift supervisor at a distribution center completes her onboarding. She's watched the videos, passed the quizzes, signed off on the SOPs. # The Missing Step in Every Frontline Training Program A new shift supervisor at a distribution center completes her onboarding. She's watched the videos, passed the quizzes, signed off on the SOPs. On paper, she's ready. Three weeks later, her first real performance conversation — a chronically late warehouse associate, a union context, real stakes — goes sideways. Not because she didn't know the policy. Because she had never once practiced saying the words out loud. This gap has a name. It sits between information transfer and actual skill. Training fills the first. Practice builds the second. For most frontline organizations, the second step is almost entirely absent — not by choice, but because the tools for it haven't existed. You can't rehearse a hard conversation with a compliance module. You can't build confidence by reading a scenario card. That's the gap a cluster of this week's releases takes direct aim at. --- ## Practice Is a Different Activity Than Training There's a reason flight simulators exist. And surgery residencies. And moot courts. High-stakes fields figured out long ago that watching someone do something, or even knowing how it should be done, is not the same as having done it under pressure. Frontline work — managing a difficult employee, handling a safety incident, de-escalating an irate customer — belongs in the same category. [Practice Hub](https://www.mangoapps.com/changelog/3039) launched this week as a new app in the MangoApps platform. The premise is simple: employees should be able to rehearse real workplace conversations against an AI persona before they have to have them for real. They receive a scored rubric afterward — not a pass/fail, but a criterion-by-criterion breakdown of where they struggled and where they held their own. That alone is useful. What happened over the next few days pushed it further. By Thursday, [Practice Hub added live voice roleplay](https://www.mangoapps.com/changelog/3042) — employees can now practice speaking and being spoken to in real time, with interruption support, for scenarios where the pressure of live pace is part of the skill. The difference between typing a response and having to say it out loud, while an AI persona pushes back, is significant. Hesitation, word choice, tone — these don't show up in a text-based exercise. An [AI coach was also added this week](https://www.mangoapps.com/changelog/3041), grounded in the employee's own recording and scoring rubric. A learner can ask follow-up questions about their specific performance — not generic training questions, but "why did I score low on empathy in this particular exchange, and what would a stronger response have looked like?" The coach can also generate exemplar responses for the criteria where the employee is weakest. That's a fundamentally different feedback loop than a trainer reviewing a recording three days later. None of this replaces human coaching or manager involvement. But it closes the gap between formal training sessions — which happen quarterly, if that — and the daily or weekly moments where frontline employees are making calls they weren't fully prepared for. --- ## Making the Gap Visible Before It Costs You Here's the management problem that sits underneath the readiness problem: you can't coach what you can't see. Most managers find out about skill gaps when something goes wrong — the complaint, the near-miss, the turnover conversation. By that point, the gap has already done its damage. Two releases this week change the visibility equation for managers. The first is the [Team Skill Radar in Practice Hub](https://www.mangoapps.com/changelog/3041). Managers can now see a team-wide radar chart of competency across direct reports — which criteria are consistently weak, who's struggling with which type of scenario. From that view, a manager can assign targeted practice with one click. The sequence matters: see the gap, assign the practice, close the gap — before the incident, not after. The second is [Shared Recording Analyses](https://www.mangoapps.com/changelog/3040). Practice Hub managers can now view a team-wide index of recording analyses with trend summaries and per-speaker turn attribution in multi-party sessions. If a team is consistently struggling with the opening thirty seconds of a confrontational exchange, that shows up in the trend data before any single conversation goes badly enough to surface as a problem. Away from Practice Hub, a quieter but equally meaningful release addressed a different kind of visibility gap. [Skills and Certifications](https://www.mangoapps.com/changelog/3038) now require manager approval before submitted credentials appear on an employee's profile. This prevents unverified claims from showing up in staffing decisions or compliance reviews — a real operational risk for any organization where role assignments hinge on certified competencies. The change doesn't add friction for employees who actually have the skills. It removes the noise that obscures who's genuinely qualified. These three releases share a logic: readiness data that isn't verified, aggregated, and visible to the people responsible for it isn't useful. It's just compliance theater. --- ## Information in Motion Readiness also depends on information reaching people in formats they can actually absorb. Frontline employees don't sit at desks. They're on the floor, in vehicles, mid-task. The mental bandwidth for a carefully formatted internal newsletter article is often zero. [AI Podcast Generation for Comms Hub](https://www.mangoapps.com/changelog/3042) addresses this directly. Internal newsletter issues can now be automatically converted into AI-produced audio podcast episodes with a two-host conversational format. An employee can listen to the week's updates during a commute or while doing prep work — without needing to carve out reading time. The content is the same; the format fits the context. This connects to a broader investment in findability this week. [Global search now surfaces shifts, leave requests, and recognition posts](https://www.mangoapps.com/changelog/3041), along with over a dozen previously hidden categories including safety checklists, SOPs, sites, workspaces, and communications. [Ballots are now searchable](https://www.mangoapps.com/changelog/3042) too, scoped to each user's eligibility so employees only see votes they participate in. The through-line is the same: information that exists but can't be found, consumed, or acted on in the flow of work isn't informing anyone. Reducing the friction between an employee and the content they need — whether that's a safety SOP, an update from leadership, or a shift swap — is a readiness problem as much as it's a search problem. --- ## The Quiet Shift Behind These Releases Training organizations have spent decades optimizing the wrong bottleneck. The question has been "how do we get more content in front of more people?" — more modules, more hours, more completion rates to report. The assumption is that coverage equals readiness. It doesn't. Coverage tells you who received information. Readiness tells you who can act on it under pressure. The gap between those two measures is where most frontline training fails — and where most operational risk lives. What this week's releases collectively represent is a shift in the question being asked. Not "did they complete the training?" but "can they perform when it counts?" Not "is the information available?" but "did it reach them in a form they could actually use?" Not "do they list the credential?" but "has a responsible party verified it?" None of this is a complete answer to the frontline readiness problem. The hard conversations are still hard. The gaps are still real. But the tools to close them — verifiably, measurably, before the pressure arrives — are getting meaningfully better. For HR leaders and operations executives measuring training ROI, the question worth asking is: how much of your current training budget is producing compliance coverage, and how much is producing actual readiness? The two are not the same, and the delta is where risk lives. --- *See the full list of this week's releases in the [July 5](https://www.mangoapps.com/changelog/3042), [July 4](https://www.mangoapps.com/changelog/3041), [July 3](https://www.mangoapps.com/changelog/3040), [July 2](https://www.mangoapps.com/changelog/3039), [July 1](https://www.mangoapps.com/changelog/3038), [June 30](https://www.mangoapps.com/changelog/3037), [June 28](https://www.mangoapps.com/changelog/3036), and [June 27](https://www.mangoapps.com/changelog/3035) changelogs.* --- # 9 Modern Employee Intranet Features That Reach Frontline Staff Without Email **Author:** Andy Tolton **Published:** 2026-06-30 **Category:** intranet Learn the nine intranet features that help you reach frontline employees without corporate email, from mobile access to SMS alerts. **Quick answer:** A modern employee intranet reaches frontline staff who have no corporate email by meeting them on the phone they already carry, not the inbox they were never given. The nine features that remove the access barrier are: a branded mobile app, sign-in that does not depend on a corporate email account, targeted delivery with read-receipt tracking, push and SMS notifications, real-time translation, AI-powered search, mobile schedule and task access, kiosk and digital signage support, and two-way engagement tools. If a platform is missing any of these, a large share of your workforce stays unreachable. Most enterprises already own an intranet. Very few reach the people who actually run the store, the floor, the route, or the ward. This guide explains why the gap exists, the nine features that close it, and what internal communications, HR, IT, and operations leaders should put on a shortlist when comparing platforms. ## The frontline access gap is a measurement problem, not a content problem The numbers on intranet usage are not subtle. Across organizations that have an intranet, only about 13% of employees use it daily and 31% never use it at all, according to [Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) research. In the United States, intranet adoption sits near 39%, the lowest of the major markets Staffbase tracked in 2025. The reason is structural. Legacy intranets were built for people at desks, behind a single sign-on tied to a corporate email account. That model works for the head office. It does not work for the 80% of the global workforce that is deskless: nurses, store associates, drivers, technicians, caregivers, line workers. They were never issued an email address, so the front door to the intranet was locked before they ever tried the handle. This is expensive in ways that do not always show up on a dashboard. Only 23% of frontline workers believe they have access to the technology they need to be productive, according to [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html). When the frontline cannot reach the system of record, that search time gets replaced by something worse: asking a manager, calling a coworker, or guessing. Schedule changes go out as photos in a WhatsApp group. Safety updates sit in an inbox nobody opens. The store manager becomes a human help desk. The fix is not more content. It is removing the access barriers that keep half the workforce out. The features below are how a [modern employee intranet](https://www.mangoapps.com/solutions/modern-intranet) does that. ## The 9 features that remove access barriers for frontline staff Each feature includes what it is, why it matters for staff without corporate email, and what to verify during a platform comparison. ### 1. A branded mobile app on the device employees already carry **What it is:** A full [native iOS and Android app](https://www.mangoapps.com/solutions/employee-app), white-labeled in your brand, that an employee installs on a personal phone in under a minute. No company laptop. No company-issued hardware. **Why it matters:** The frontline does not sit at a workstation. The only screen most of them carry all shift is the one in their pocket. If the intranet is a website that assumes a desktop and a corporate login, it has already lost them. A real mobile app, with offline access for areas with poor signal, is the baseline requirement, not a nice-to-have. **What to look for:** Native apps (not a mobile-responsive website), offline mode, support for shared and personal devices, and the ability to run multiple brands or subsidiaries under one back end. ### 2. Sign-in that does not depend on a corporate email account **What it is:** Onboarding and authentication that work from a phone number, employee ID, SMS invite, or QR code, instead of requiring an @company.com address. **Why it matters:** This is the single feature most legacy systems get wrong. If account creation routes through a corporate email, every employee without one is excluded by design. Frontline-first platforms let an employee join by scanning a QR code on a break-room poster or tapping a texted invite link, then verify identity against your existing employee records. **What to look for:** Multiple onboarding paths (SMS, QR, employee ID), identity verification against your HRIS or directory, and role-based access that still respects single sign-on for the desk-based staff who do have email. ### 3. Targeted delivery with read-receipt and acknowledgment tracking **What it is:** The ability to send a message to a specific audience (one store, one region, one job role) and see exactly who received it, opened it, and acknowledged it. Critical messages can be marked must-read. **Why it matters:** Email gives you an open rate at best. For a safety recall, a policy change, or a closure, you need proof that the people on shift actually saw it. [Acknowledgment tracking](https://www.mangoapps.com/solutions/internal-communications) turns communication from a broadcast into a closed loop, which matters enormously in regulated industries. **What to look for:** Audience targeting by location, role, and attributes; read receipts; mandatory-read acknowledgment; and reach analytics that report on the frontline specifically, not just the whole company average. ### 4. Push and SMS notifications for urgent reach **What it is:** Push notifications to the app, with SMS as a fallback channel, so an urgent message lands on the lock screen of an employee who has no inbox. **Why it matters:** When something has to reach the floor in minutes, an email thread does not work. Push and SMS are how you reach a dispersed workforce in real time. Benchmark Human Services, a healthcare provider whose caregivers work in client homes, used push notifications to get critical health and safety information to field staff who are not on the company email network. **What to look for:** App push plus SMS, audience targeting on notifications, delivery confirmation, and controls that prevent over-notifying. ### 5. Real-time translation across content **What it is:** Automatic translation of posts, documents, and messages into the reader's preferred language, in real time, across content types. **Why it matters:** Frontline workforces are frequently multilingual. A communication that only lands for English speakers is not reaching the frontline; it is reaching part of it. A.S. Watson, the health and beauty retailer, delivers work schedules to store staff with automatic multi-language translation so a single post serves a workforce across four countries. **What to look for:** Real-time translation in the languages your workforce actually speaks (50+ language coverage is a reasonable bar), applied to posts, knowledge articles, and chat, not just static pages. ### 6. AI-powered search that returns answers, not just links **What it is:** Semantic search and an AI assistant trained on your approved internal knowledge that answers a question directly, on any device, in any language, instead of returning a list of documents to dig through. **Why it matters:** A frontline worker between customers has seconds, not minutes. "How many sick days do I have left?" or "What is the return policy on opened electronics?" should produce an answer, not a search results page. Holt of California, an equipment dealer, named search the single biggest benefit of its platform for exactly this reason. **What to look for:** Semantic search (intent-based, not keyword-only), an AI assistant grounded in your own content and permissions, multilingual answers, and the ability to surface results from connected systems like SharePoint or Google Drive. ### 7. Mobile schedule, shift, and task access **What it is:** The ability for an employee to open the app and see this week's schedule, swap or pick up a shift, and work through assigned tasks, all without an email or a desktop. **Why it matters:** For hourly staff, the schedule is the most-opened thing in any workplace app. When it lives in the same place as company news and knowledge, the intranet stops being a corporate billboard and becomes a daily tool. At A.S. Watson, schedule access on mobile is the flagship use case: more than 20,000 retail employees check schedules from their phones, and store managers stopped fielding constant schedule questions. **What to look for:** Native [scheduling](https://www.mangoapps.com/solutions/workforce-management) and [task](https://www.mangoapps.com/solutions/task-management) features on the same platform as communications and knowledge, so you are not stitching a separate scheduling vendor into the intranet later. ### 8. Kiosk and digital signage for shared spaces **What it is:** A shared-device mode for kiosks in break rooms or on the floor, plus digital signage that pushes the same content to screens in physical spaces. **Why it matters:** Not every frontline worker wants the app on a personal phone, and some roles cannot carry one on the floor. Kiosk mode and signage make sure those employees still see the same announcements, recognition, and updates as everyone else, without a personal login. **What to look for:** Dedicated kiosk mode with secure shared access, and digital signage that draws from the same content engine so you are not maintaining two systems. ### 9. Two-way engagement, not a read-only portal **What it is:** Recognition, kudos, polls, comments, reactions, and a peer-to-peer feed that lets employees post and respond, not just receive. **Why it matters:** Read-only intranets get read-only adoption. The platforms that reach the frontline feel familiar, closer to the social apps people already use than to a corporate document library. Columbia Basin Health Association replaced a read-only intranet with an interactive platform and reached more than 90% monthly employee engagement, well past their original goal. Engagement is not soft: Gallup data ties highly engaged teams to 23% higher profitability and 18% higher sales. **What to look for:** Posts with comments and reactions, recognition and kudos, polls and surveys, and group spaces teams can run themselves without IT. ## Intranet platform comparison: three approaches to frontline access When you compare [digital workplace solutions](https://www.mangoapps.com/articles/best-employee-intranet-frontline-teams), most options fall into one of three buckets. The differences are clearest when you score them on frontline reach rather than feature count. | Capability | Legacy intranet (SharePoint portal, custom portal) | Frontline comms app (comms-only point tool) | Modern employee intranet platform | | --- | --- | --- | --- | | Works without corporate email | Rarely | Usually | Yes, by design | | Native mobile app for frontline | Limited | Yes | Yes | | Targeted delivery with acknowledgment | Limited | Yes | Yes | | Real-time translation | Rare | Sometimes | Yes | | AI search grounded in your content | Rare | Limited | Yes | | Schedule, shift, and task workflows | No | No | Yes, on the same platform | | Kiosk and digital signage | Rare | Sometimes | Yes | | Two-way engagement and recognition | Limited | Yes | Yes | | Typical adoption | 30 to 40% | Varies | 80 to 90%+ | The pattern is worth naming. [Legacy intranets](https://www.mangoapps.com/sharepoint-alternatives) reach the desk and miss the floor. Comms-only apps reach the floor but stop at the announcement: after the message goes out, the schedule, the safety inspection, the training, and the HR workflow all live in other tools. A modern employee intranet platform reaches the floor and keeps going, which is why adoption tends to clear 80% rather than stall at 30%. *Capability statements for third-party vendors are taken from each vendor's public documentation and are vendor-stated, not independently verified by MangoApps.* ## What buyers should look for: a frontline access checklist Use this as a procurement filter. If a platform cannot check most of these boxes, it will not reach staff without corporate email, regardless of how the homepage looks. - An employee can join from a personal phone using a phone number, employee ID, QR code, or SMS invite, with no @company.com address required. - The mobile experience is a real native app with offline support, not a responsive website. - You can target a message to one location or role and see who acknowledged it. - Urgent messages reach employees by push and SMS, not only email. - Content translates automatically into the languages your workforce speaks. - Search returns answers, and an AI assistant is grounded in your approved content and permissions. - Schedules, shifts, and tasks live on the same platform as communications and knowledge. - Shared spaces are covered with kiosk mode and digital signage. - Employees can post, react, and recognize each other, not just read. - Adoption is measurable on the frontline specifically, and the vendor will commit to it. That last point separates marketing from architecture. Ask any vendor for frontline adoption data from named customers, and ask whether they will stand behind an adoption target contractually. ## What this looks like in practice The features above are not theoretical. Three examples show what changes when the access barrier comes down. **Benchmark Human Services (healthcare, 4,000+ employees).** About 85% of Benchmark's staff are remote caregivers working in client homes, with no company email. "85% of our staff are remote workers that don't come to an office. They are not on our email network, because it's an industry that just historically has high turnover, and so managing that is a little bit challenging and expensive," said Courtney Heiser, Director of Communications. After moving to a mobile-first platform, over one-third of employees built the app into their daily routine within a few months, and push notifications carried urgent health and safety information to the field. **A.S. Watson Benelux (retail, 27,000 employees across 1,700 stores).** With an average employee age around 25 and no corporate email for store staff, A.S. Watson had been managing schedules through photos in WhatsApp. "The absolutely killer application for us is that we offer employees their working schedule online. Every employee, 24/7, on their mobile devices, on their way to the store, can actually look at their schedule," said Jan Carel Uylenberg, HR Director. The platform reached more than 80% active adoption, and one store manager noted that employees "never contact me anymore with questions, they can see it themselves." **Columbia Basin Health Association (healthcare, 460+ employees).** With frontline clinical staff making up more than two-thirds of the workforce, CBHA's previous read-only intranet was not reaching anyone. "Our old platform was 'read-only' with some links to network files. It wasn't customizable and wasn't very pleasing to the eye," said Rebecca Wolfs, Director of Training, Development, and Compliance. The interactive replacement reached more than 90% monthly employee engagement, against an original two-year goal of 75%. ## Where MangoApps fits For how these features fit into a full frontline platform with scheduling, tasks, training, and HR, see [The Complete Guide to Frontline Communication Platforms](https://www.mangoapps.com/articles/frontline-communication-platforms-guide). For a ranking built on governance, compliance, and global reach, see [The 10 Best Employee Intranet Platforms for Governance, Compliance, and Global Workforce Communication](https://www.mangoapps.com/articles/best-intranet-platforms-governance-compliance-global). MangoApps is the AI-Ready Employee Platform for the Frontline. The starting point is a decision, not a tool: enterprises choose one platform, begin with the apps or workflows their teams need now, and expand across Employee Experience, Frontline Operations, and People Operations on the same foundation. The same identity, permissions, employee data, and AI governance carry forward, so there is no second implementation when the next workflow goes live. That architecture is the reason the access problem gets solved instead of relocated. The branded employee app installs on the phone an employee already owns, with no corporate email required. Targeted delivery, read-receipt tracking, push and SMS, real-time translation in 50+ languages, AI search and an assistant grounded in your own content, mobile schedules and tasks, kiosk and signage, and two-way recognition all run on one platform rather than across four or five point tools. The AI angle is why the platform decision is strategic rather than cosmetic. An assistant sitting on top of disconnected tools cannot safely act, because it has no shared identity, permissions, or workflow context. When communications, operations, and HR run on one foundation, AI can answer and act across all of them while respecting who is allowed to see what. That is a property of the platform, not a feature bolted onto a chat box. MangoApps has built for the frontline for 18+ years, serves 2M+ users worldwide, and sees 90%+ adoption within 90 days of launch, against the 30 to 40% that legacy intranets average. It is the only vendor in the category with an Adoption Guarantee: if employees do not adopt after launch, you do not pay. For internal communications, HR, IT, and operations leaders who have watched an intranet reach the head office and stop, that guarantee is the difference between buying software and buying an outcome. [See how MangoApps reaches every employee, desk and frontline, and book a 30-minute demo.](https://www.mangoapps.com/solutions/modern-intranet) ## Frequently asked questions **What is a modern employee intranet?** A modern employee intranet is a mobile-first platform that gives every employee, desk-based and frontline, a single place to find news, knowledge, schedules, and workflows. Unlike legacy intranets built for desktops and corporate email, it reaches staff on the devices they already carry and is measured by actual adoption rather than by how much content it holds. **How do you reach frontline employees who don't have corporate email?** You reach them through a branded mobile app they install on a personal phone, with sign-in based on a phone number, employee ID, QR code, or SMS invite instead of an email address. Push notifications and SMS deliver urgent messages, and acknowledgment tracking confirms who actually saw them. Email is never the front door. **Why do most intranets fail to reach frontline staff?** Most intranets were architected for desk workers behind a corporate single sign-on tied to email, so deskless employees are excluded before they start. The result is the well-documented adoption gap: only about 13% of employees use their intranet daily, and 31% never use it ([Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics)). **What should you look for when comparing intranet platforms?** Prioritize frontline reach over feature count: email-free onboarding, a true native mobile app, targeted delivery with acknowledgment, push and SMS, real-time translation, AI search grounded in your content, mobile schedules and tasks, kiosk and signage support, and two-way engagement. Ask vendors for named-customer adoption data and whether they will commit to an adoption target. **What is the difference between an intranet and a frontline communications app?** A frontline communications app reaches the floor but stops at the announcement; the schedule, the safety inspection, the training, and the HR workflow all live in other tools. A modern employee intranet platform delivers the message and runs the workflows that follow it on the same foundation, which is why it sustains higher adoption. **How is intranet adoption measured, and what is a good rate?** Adoption is usually measured as weekly or monthly active users against headcount. [Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) benchmarks 60% weekly active users as a successful intranet and 85% weekly login as best practice. Frontline-first platforms regularly clear 80 to 90% because they remove the access barriers that hold legacy intranets near 30 to 40%. --- # How to Centralize Tools and Documents with an Employee Intranet **Author:** Andy Tolton **Published:** 2026-06-30 **Category:** intranet Learn how to replace tool sprawl with a single employee intranet that centralizes documents, workflows, and daily work. **Short answer:** You centralize tools and documents by replacing scattered point apps and shared drives with a single employee intranet that every worker actually opens. The right platform unifies identity, search, content, and the day-to-day tools people use, makes everything findable from any device including a phone, integrates the systems you keep, and is governed so information stays current. Done well, employees stop hunting across tabs and tools, and the intranet becomes the one place work starts. That last clause is where most projects fail. Plenty of companies own an intranet. Far fewer have one their people use. This guide is for HR, IT, internal communications, and operations leaders at mid-market and enterprise organizations who want centralization that holds, not another portal nobody opens. ## What "centralizing tools and documents" actually means Centralization is not a SharePoint folder structure. It is the elimination of the switching tax employees pay every day. A frontline employee at a typical mid-sized company touches the schedule in one app, the policy PDF in a shared drive, the safety form on paper or a third tool, the pay stub in a portal they reset the password for monthly, and the company news in an email they cannot open without a corporate account. A corporate employee bounces between an intranet, a chat tool, a file store, a ticketing system, and four browser tabs of SaaS logins. Every handoff is a moment where information is lost, duplicated, or simply never found. Real centralization means three things happen at once: - **One place to start.** Employees open a single app or home base, not a bookmark folder of separate tools. - **One way to find anything.** Search returns the document, the person, the policy, or the workflow regardless of which underlying system holds it. - **One identity and permission model.** A worker logs in once, sees only what they should, and the same access rules apply to every tool and document behind that login. If a project delivers a prettier home page but employees still log into five other tools to do their jobs, nothing was centralized. The links just got nicer. ## Why tool and document sprawl is the problem worth solving The cost of sprawl is measurable, and it is large. The average company now runs 101 applications, and companies with more than 5,000 employees average 131, according to [Okta's Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/); a [Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) study found workers toggling between applications roughly 1,200 times a day. That is nearly half a week, every week, spent finding work rather than doing it. For a 5,000-person company, the searching alone represents the equivalent of hundreds of full-time roles producing nothing. The intranet most companies already own is not closing that gap. Research published by [Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) in 2025 found that while 91% of organizations have an intranet, only 13% of employees use it daily, and 31% never use it at all. An intranet that a third of the workforce never opens is not a system of record. It is a sunk cost. The sprawl also has a direct line to retention and performance. [Gallup's Q12 meta-analysis](https://www.gallup.com/workplace/236927/employee-engagement-drives-growth.aspx) links top-quartile engagement to 18% higher productivity and 23% higher profitability, and Gallup's [State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) puts the global cost of low engagement at roughly $10 trillion, about 9% of global GDP. The tools employees use to find information and get work done are not a back-office IT concern. They are an [employee engagement](https://www.mangoapps.com/solutions/employee-engagement) lever. The pattern is consistent: information exists, but it is fragmented across tools that were each bought to solve one problem and never designed to work together. Centralization is the fix, and the vehicle is employee intranet software, provided you choose one built to actually reach and serve every employee. ## What is employee intranet software? Employee intranet software is a platform that gives an organization a private, secure, central place for communication, knowledge, documents, and the day-to-day tools employees use to do their jobs. A [modern enterprise intranet](https://www.mangoapps.com/solutions/modern-intranet) goes well beyond the static, link-heavy portals of a decade ago. It combines [company news](https://www.mangoapps.com/solutions/internal-communications), a searchable knowledge base and document library, an employee directory, collaboration spaces, and increasingly the operational and HR workflows employees previously handled in separate apps, all behind a single login and accessible on any device. The distinction that matters for buyers in 2026 is between a **communications intranet** and an **employee platform**. A communications intranet publishes news and houses documents. An employee platform does that and runs [the schedule](https://www.mangoapps.com/solutions/workforce-management), [the safety inspection](https://www.mangoapps.com/solutions/safety-compliance), the help desk ticket, the performance review, and [the payroll workflow](https://www.mangoapps.com/solutions/hr-operations) in the same app. The first centralizes content. The second centralizes the actual work. For genuine tool consolidation, you want the second. ## How to centralize tools and documents with an employee intranet Centralization is a sequence, not a switch you flip. These six steps are the path mid-market and enterprise teams follow to consolidate the stack without ending up with another underused portal. ### Step 1: Inventory the tools and documents you are actually trying to consolidate Before evaluating software, map the real estate. List every tool employees touch in a normal week and every place a document might live: shared drives, email attachments, paper binders, individual SaaS apps, legacy portals, and "the spreadsheet Dave maintains." Note who owns each, how current it is, and how it is accessed. This inventory does two things. It reveals how much sprawl actually exists, which is almost always more than leadership assumes, and it surfaces the dead content. Many intranet replacements discover documents years out of date still live in production with no one knowing why. You cannot centralize what you have not catalogued, and you should not migrate junk into a clean system. ### Step 2: Make everything findable with AI-powered search Centralization without findability is just a bigger pile. The single most cited benefit by organizations that successfully consolidate is search, because search is what turns a collection of documents and tools into something people use. Modern enterprise intranet search should let employees find a person, a policy, a file, a team, or an answer in seconds, and filter by type. [AI-powered semantic search](https://www.mangoapps.com/ai/capabilities) raises the bar again: it returns answers, not just a list of links, and understands intent rather than matching keywords. Only 23% of frontline workers believe they have access to the technology they need to be productive, and the right mix of tools lifts productivity about 22%, according to [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html). Search is not a feature to defer to phase two. It is the reason centralization pays off at all. ### Step 3: Bring deskless and frontline workers into the same system Here is where most consolidation projects quietly break. The majority of the global workforce is deskless, and legacy intranets were built for people at desks with corporate email and a laptop. If your centralization plan only reaches the corporate population, you have not centralized the company. You have built a nicer portal for headquarters and left the store, the floor, the ward, and the field on a different system entirely. A platform that genuinely centralizes tools and documents must work on [the phone employees already carry](https://www.mangoapps.com/solutions/employee-app), with no corporate email required, no laptop, and no VPN. The home base a store manager opens at the start of a shift has to be the same system the CHRO uses to publish company news. When the frontline and the corporate office live in one app, the schedule, the policy, the safety form, and the recognition all centralize together. When they do not, sprawl simply moves to the field. ### Step 4: Integrate the systems you are keeping, do not just link to them No enterprise rips out Workday, SAP SuccessFactors, UKG, ServiceNow, or Microsoft 365 to deploy an intranet, and you should not try. The goal is to consolidate the tools that should not be standalone and integrate the systems of record that should stay. A capable enterprise intranet ships with [hundreds of pre-built connectors and an open API](https://www.mangoapps.com/integrations), plus federated search across connected content so a file in SharePoint or Google Drive surfaces in the same results as a document published natively. The test of good integration is simple: can an employee complete the task without leaving the app and logging into the source system? A link to ServiceNow is not consolidation. A help desk ticket that can be raised and tracked inside the same app the employee already uses is. ### Step 5: Govern access, permissions, and content freshness Centralized content is only trustworthy if it is current and correctly scoped. A single identity and permission model means each employee sees only what their role allows, applied consistently across every tool and document. Governance also covers content lifecycle: ownership, review dates, and the retirement of stale material so the 2012 PDF does not outlive its usefulness for another decade. This step is what lets employees trust the system. The moment a worker finds outdated information twice, they stop trusting the intranet and go back to asking a colleague or guessing. Governance is not bureaucracy. It is what keeps centralization from decaying back into sprawl. ### Step 6: Design for adoption, then measure it The metric that determines whether you centralized anything is adoption. [Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) benchmarks 60% weekly active users as a successful intranet and 85% weekly login as best practice; the average intranet sees 13% daily use. The gap between those numbers is almost entirely down to design and rollout, not features. Adoption comes from making the intranet the place work happens, not a destination employees are told to visit. When the schedule, the pay stub, the task list, and the company news all live in one app, employees open it because they have to, and engagement follows. Set adoption targets before launch, instrument them, and treat anything below 60% as a problem to fix rather than a number to spin. Some platforms will stand behind this contractually, which is worth asking about directly. ## Why legacy intranets fail at centralization If centralization were only a matter of buying intranet software, the 91% of companies that already own one would be done. They are not, and the reason is instructive. Legacy intranets average 30 to 40% adoption. The cause is architectural, not cosmetic. They were built for desk workers, so the frontline never came aboard. They centralized documents but not tools, so employees still logged into everything else. They had weak or no search, so the centralized content was not findable. And they were maintained by IT with no employee ownership, so content went stale and trust eroded. A redesign of a system with these foundations produces a better-looking version of the same low-adoption portal. The adoption failures common to outdated platforms are not fixed by new templates. They are fixed by choosing a platform whose architecture reaches every employee, makes everything findable, and consolidates the actual tools, then by running a rollout that targets and measures adoption from day one. Centralization is an outcome of that combination, not a feature you can bolt onto a portal that was never going to be opened. ## What centralized actually looks like: three examples Holt of California, a 800-person equipment dealer, ran an outdated custom intranet that had no search, no mobile access, and documents from 2012 still live with no one knowing why. Employees had to be on the corporate network to access it at all. After consolidating onto a single hub with searchable content, an employee directory, and mobile access, the company reported a 50% reduction in time spent finding information, a 40% reduction in the questions departments received because employees could self-serve, and 85% weekly engagement. As Sales Development Supervisor Sarah Cenedella put it, the biggest benefit was search: employees could finally locate files, information, and colleagues in seconds rather than guessing where things had been moved. [Petauri](https://www.mangoapps.com/resources/petauri-case-study), a pharmaceutical services company, grew from roughly 100 to more than 400 employees through acquisitions in just over a year, each bringing its own legacy systems. The company needed what Senior VP of IT Jeff Petet called "the connective tissue between our people, tools, and knowledge." A single platform became the source of truth: company news, single sign-on to core business systems, an onboarding hub, a knowledge base, and AI assistants trained on internal documentation so a new hire could ask where to find the holiday calendar and get an answer instead of a search result. PetSmart faced a reach problem at scale. About 80% of its 55,000 employees largely had no access to company systems at all. Centralizing onto an employee platform gave the company the ability to reach its entire associate base for the first time. Reaching everyone is the precondition for centralizing anything. ## Enterprise intranet vs. point tools: the consolidation math For IT and operations leaders, the clearest way to frame centralization is the stack it replaces. A modern employee platform consolidates tools that were each bought separately. | What employees do | The point-tool way | The centralized way | | --- | --- | --- | | Find a policy or document | Shared drive plus email search | One AI-powered search across all content | | Read company news | Email the frontline cannot open | One app every employee opens | | Check the schedule | Standalone scheduling app | Same app, same login | | Submit a safety inspection | Paper or a separate tool | Same app, mobile, offline-capable | | Raise an IT or HR request | Separate help desk portal | Same app, integrated with ServiceNow | | Access pay and benefits | A portal with a forgotten password | Same identity, same app | | Get an answer from AI | A chatbot that only sees one tool | AI grounded in every workflow's data | Each row that moves from the left column to the right removes a login, a vendor, an integration to maintain, and a place where documents go to die. A platform that consolidates four or five point solutions does not just reduce the productivity tools employees juggle. It reduces the IT surface area, the security exposure, and the integration tax, while giving the digital workplace a single front door. ## Why centralization matters more in the AI age There is a strategic reason this decade's intranet decision carries more weight than the last one's, and it is about AI. For most of the past decade, the sensible approach to employee technology was best of breed: pick the best intranet, the best scheduling tool, the best LMS, and stitch them together. That logic held when AI was a feature. It breaks when AI is infrastructure. An [AI assistant](https://www.mangoapps.com/ai) that acts on behalf of an employee needs to know who that employee is, what they are allowed to see, what their work context is, and how to route a result back into the right workflow. That requires shared identity, shared permissions, shared employee data, and [governance that spans every workflow](https://www.mangoapps.com/ai/governance). A chatbot sitting on top of a dozen disconnected tools cannot provide that safely; it can only see the one tool it was bolted onto. A platform built on a shared foundation can. This reframes centralization. Consolidating tools and documents is not only about saving employees time today. It is about building the single data and permission foundation that makes AI safe and useful across the whole employee lifecycle tomorrow. The companies that centralize now are the ones whose AI will be able to act across operations, HR, and communications, not just answer questions about a single content store. Fragmentation that feels merely inefficient today becomes a hard ceiling on AI value tomorrow. ## How MangoApps centralizes tools and documents MangoApps is the [AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/platform). It is the platform enterprises choose once, then start with the apps or workflows their teams need today, and expand over time across Employee Experience, Frontline Operations, and People Operations without rebuilding identity, permissions, integrations, or AI governance. For centralization specifically, that means: - **One app every employee opens**, fully branded as your company, on iOS and Android, with no corporate email or laptop required. The frontline and the corporate office on the same platform. - **AI-powered semantic search** across documents, people, pages, and connected systems, so employees find answers rather than links. - **A modern intranet and knowledge base** with document management and federated content from SharePoint and Google Drive, alongside the operational and HR workflows that previously lived in separate tools. - **200+ pre-built integrations** plus an open API, so the systems of record you keep, such as Workday, UKG, SAP SuccessFactors, and ServiceNow, connect rather than compete. - **One identity, one permission model, and enterprise-grade governance**, with [HITRUST, SOC 2 Type II, and ISO 27001 certification](https://www.mangoapps.com/security-compliance). - **AI grounded in work**, not a chatbot bolted onto a content store. Named agents live inside the workflows they serve, and enterprise data never trains public models. The results show up in adoption, which is the only number that proves centralization happened. MangoApps customers average more than 90% adoption within 90 days, against the 30 to 40% typical of legacy intranets. The company backs that with an [Adoption Guarantee](https://www.mangoapps.com/why-mangoapps): if employees do not adopt after launch, you do not pay. Across 2 million users and 18+ years in market, retention sits at 98% with an NPS of 78. Centralization is not a portal redesign. It is the decision to run the company on one platform that every employee opens, that finds anything, and that is ready for what AI will ask of it next. > **Explore further:** [The AI-Ready Employee Platform](https://www.mangoapps.com/platform) · [Modern Intranet & Knowledge](https://www.mangoapps.com/solutions/modern-intranet) · [Why MangoApps and the Adoption Guarantee](https://www.mangoapps.com/why-mangoapps) · [Petauri customer story](https://www.mangoapps.com/resources/petauri-case-study) · [Schedule a call](https://www.mangoapps.com/schedule-a-call) · [The Complete Guide to Intranet Best Practices and Evaluating Enterprise Intranet Platforms](https://www.mangoapps.com/articles/the-complete-guide-to-intranet-best-practices) · [The Complete Guide to Frontline Communication Platforms](https://www.mangoapps.com/articles/frontline-communication-platforms-guide) ## Frequently asked questions **What is the difference between an intranet and employee intranet software?** "Intranet" describes the private internal network or site itself. Employee intranet software is the platform that delivers it, including communication, a searchable knowledge base, document management, an employee directory, and increasingly the operational and HR tools employees use day to day. Modern employee intranet software is mobile-first and built to reach every worker, including deskless and frontline employees, not only desk-based staff. **How do you centralize documents that are scattered across shared drives and email?** Start by inventorying where documents live and who owns them, retire stale content rather than migrating it, then consolidate active documents into a single platform with AI-powered search and federated search across systems you keep, such as SharePoint and Google Drive. The goal is one search that returns the right document regardless of where it is stored. **Can an intranet reach deskless and frontline workers?** Only if it was built for them. Legacy intranets designed for desk workers average 30 to 40% adoption and rarely reach the frontline. A platform built for deskless workers runs on the phone the employee already carries, with no corporate email, laptop, or VPN required, which is what drives adoption above 80 to 90%. **Why do most intranet projects fail to improve adoption?** Because they centralize content but not the tools employees actually use, lack strong search so centralized content is not findable, never reach the deskless majority of the workforce, and let content go stale until employees stop trusting it. Adoption follows when the intranet is where work happens, not a separate place employees are told to visit. **How does centralizing tools and documents support AI?** AI assistants need shared identity, permissions, employee data, and workflow context to act safely on an employee's behalf. A chatbot on top of disconnected tools can only see one tool. Centralizing onto one platform builds the single data and permission foundation that lets AI work across operations, HR, and communications rather than a single content store. **How long does it take to centralize onto a modern enterprise intranet?** Typical enterprise implementations run 8 to 12 weeks, depending on scope, integrations, and migration volume. The bigger driver of timeline and success is adoption planning: organizations that set and measure adoption targets from day one reach value faster than those that launch and hope. --- # Why Employee Recognition Fails—and What Actually Works **Author:** MangoApps Team **Published:** 2026-06-28 **Category:** workforce-management Ask any HR leader what their recognition program looks like, and you'll get one of two answers. Either: "We use a platform — people can give shoutouts." Or: "We do quarterly awards — HR picks the... # Why Employee Recognition Fails—and What Actually Works Ask any HR leader what their recognition program looks like, and you'll get one of two answers. Either: "We use a platform — people can give shoutouts." Or: "We do quarterly awards — HR picks the winners." Both are well-intentioned. Neither is working. The first fails because informal recognition without structure or value attached becomes noise. People stop reading the feed. They stop posting. The second fails because top-down, quarterly awards reach the same five visible employees every time, leaving the people who show up and deliver every day feeling invisible. In frontline operations — where turnover is the single biggest operational cost — this isn't a minor culture problem. It's a retention crisis wearing a culture mask. This week, MangoApps shipped what amounts to a full rethink of how recognition works: from the everyday peer layer to structured award ceremonies to team-scale moments to a year-end reflection that gives every employee a mirror on their own contributions. Each piece solves a different failure mode in the programs most organizations are running today. --- ## Give Recognition Something Real to Carry The reason most recognition feeds go quiet is simple: giving someone a shoutout costs nothing and creates nothing. When a gesture is completely frictionless and produces zero tangible outcome for the recipient, the signal degrades fast. The feed fills with generic "great job" posts, and people mentally check out. [Peer Giving (Mango Kudos)](https://www.mangoapps.com/changelog/3032) changes the underlying economics. Employees get a monthly allowance of points they can distribute to teammates — points that are redeemable for real rewards. This shifts the dynamic in two ways. First, when recognition carries a small but real allocation of value, the gesture signals genuine intent rather than reflex politeness. Second, the recipient has something tangible — something they can spend or save — rather than a notification that disappears. For frontline workers specifically, this matters more than the abstract numbers suggest. These employees are often the furthest from visibility: they don't attend all-hands meetings, they don't accumulate Slack kudos from leadership, they may not even have a company email address. Peer-to-peer giving taps into a different recognition network — the coworkers standing right next to the work, who often see what managers and senior leaders cannot. The peer layer also scales in the right direction. You don't need HR to administer it, managers to remember to use it, or a nomination committee to convene. The people best positioned to recognize good work are often the people doing it alongside. --- ## Build the Ceremony That Actually Runs Everyday peer recognition handles the ongoing signal — the low-stakes, frequent moments of appreciation that form the baseline of a recognition culture. But there's a different kind of recognition that matters just as much: the structured moment where your organization says, publicly and deliberately, *this person did something exceptional*. The challenge with awards programs isn't that organizations don't want them. It's that they break down at the logistics level. Someone has to remember to open nominations. Someone has to remind the committee. Someone has to track submissions, tally votes, contact finalists, draft announcements, and send appreciation to nominees who didn't win. In practice, half these steps get skipped or happen inconsistently — which is why the same well-connected, highly-visible people tend to win the same awards every cycle. [Award Cycles & Nominations](https://www.mangoapps.com/changelog/3033), expanded this week with [Award Cycle Automation](https://www.mangoapps.com/changelog/3036), turns that process into something that runs itself. Nomination periods open and close on schedule. Notifications go out automatically. The committee review mode, pooled voting, and winner announcement workflows are baked in. Nominees who don't win get appreciation emails automatically — something that almost never happens in manual programs, and that makes a real difference in how people feel about participating next time. What's notable in the design is where the automation is pointed. This isn't about making life easier for HR (though it does). It's about making the process consistent, so the same rigor gets applied to every award cycle regardless of who is running it. Inconsistent programs — ones that open late, forget to close, or skip the nominee communication — train employees not to take them seriously. Consistent programs train the opposite. --- ## Recognition That Scales to Teams and Survives the Year Two more pieces complete the picture. The first is scale. Most recognition tools are built around a one-to-one model: one person, one recipient. That works for individual contributions, but it breaks down for team efforts — which in frontline operations are the rule, not the exception. A crew of eight who ran a difficult warehouse audit. A twelve-person shift that managed an unexpected surge without dropping service levels. A cross-functional team that delivered a project on a compressed timeline. [Group Recognition](https://www.mangoapps.com/changelog/3036) lets employees recognize up to 50 teammates in a single action. The feed and recognition wall collapse these into one shared card rather than generating 50 individual notifications — which is the right call. A team recognition should feel like a moment, not like spam arriving in separate envelopes. The second piece is memory. Recognition moments are ephemeral by nature. They happen, generate a brief warm response, and sink into the feed. A month later, most people couldn't tell you who recognized them or what for. A year later, the cumulative picture of how someone contributed and how they were seen has effectively vanished. [Recognition Wrapped](https://www.mangoapps.com/changelog/3036) changes that by giving every employee a personalized annual recap: their recognition highlights, which company values were called out in what they received, who recognized them, who they went out of their way to recognize. It's a mirror that shows people how they mattered over the course of a year — not just in the moment it happened. For HR and operations leaders, this is also data in a form that's actually usable. Which values are being celebrated and which aren't? Which teams are actively recognizing each other and which have gone quiet? Which individuals have been unrecognized all year despite consistently strong performance? Wrapped surfaces patterns that a point-in-time feed view can't. --- ## The System Question The throughline across everything shipped this week is a shift from recognition as an event to recognition as a system — something with a peer layer that runs daily, a structured ceremony layer that runs on schedule, the ability to work at team scale rather than individual scale, and memory that outlasts the moment. This matters most in industries where invisibility has been the default. Frontline workers have long been the last to be reached by digital engagement programs. They miss the all-hands. They don't see the Slack threads. They're often the majority of the workforce and simultaneously the least connected to the cultural signals that drive retention. The research on recognition and retention is consistent enough that it's worth citing directly: employees who feel regularly recognized are significantly less likely to leave, and the effect is strongest for employees who feel least visible in their organizations. That's not a new finding. What's been missing is recognition infrastructure sophisticated enough to actually reach those employees — one that doesn't require constant manual intervention, doesn't concentrate recognition among the already-visible, and doesn't evaporate the moment a notification is read. That's the work of this week. Not a feature — a system. --- # Best Intranet Platforms for UK Enterprises in 2026 **Author:** MangoApps Team **Published:** 2026-06-25 **Category:** intranet Compare leading intranet and employee experience platforms for UK enterprises, with a focus on GDPR, Microsoft 365, and frontline reach. Choosing an intranet for a large UK enterprise means weighing more than features: data residency under UK GDPR, how deeply a platform fits an existing Microsoft 365 estate, and whether it can reach frontline and deskless staff alongside desk-based teams. The market spans UK-native specialists, EU-hosted platforms, and the Microsoft stack many organisations already run, and the right fit depends heavily on workforce shape and compliance posture. This guide compares the leading options for UK organisations evaluating intranet and employee experience platforms in 2026. Software Best For Workforce Fit Platforms MangoApps Enterprises that need one platform for both desk and frontline staff, with AI grounded in their own content and flexible deployment for data residency Desk and frontline Web, iOS, Android, Desktop Microsoft Viva / SharePoint Microsoft-committed enterprises that want their intranet inside Teams and SharePoint Primarily desk Web, iOS, Android (via Teams), Desktop Unily Large, complex global enterprises needing deep Microsoft 365 grounding and heavy customisation Primarily desk Web, iOS, Android, Desktop Interact UK and global enterprises wanting a governance-strong, branded intranet with a UK support desk Desk with mobile reach Web, iOS, Android, Desktop Staffbase Enterprises with large dispersed workforces and strict EU or UK data-residency needs Desk and frontline Web, iOS, Android, Desktop, Signage Simpplr Mid-to-large enterprises wanting an easy-to-use, AI-forward intranet with strong analytics Primarily desk Web, iOS, Android Workvivo Zoom-anchored enterprises wanting a social, culture-led intranet for desk and frontline Desk and frontline Web, iOS, Android, Desktop LumApps Multinational, multilingual enterprises, especially Google Workspace organisations Desk and frontline Web, iOS, Android, Desktop Invotra UK public sector, NHS, police, and local-authority buyers needing sovereignty and accessibility Primarily desk Web, iOS, Android, Desktop, Extranet Oak Engage UK enterprises with large frontline populations needing high mobile adoption Frontline-led Web, iOS, Android, Desktop Sorce / Engage UK mid-to-large organisations wanting a flexible, consultative UK supplier Desk with mobile reach Web, iOS, Android, Desktop *Capability statements for third-party vendors are taken from each vendor's public documentation and are vendor-stated, not independently verified by MangoApps.* MangoApps 4.6/5 Stars · Gartner Peer Insights 2M+ Users · Trusted Worldwide Gartner MQ Visionary · Intranet Packaged Solutions (2025) IDC MarketScape Leader · Employee Experiences (2024) Forrester Wave Strong Performer · Intranet Platforms (Q2 2026) Reworked IMPACT Award (Gold) · Intranet & Communications Platforms For a large UK enterprise, the intranet decision is really a platform decision, and that matters more in the AI age than it did a decade ago. MangoApps is the AI-Ready Employee Platform for the Frontline: enterprises choose the platform once, start with the [modern intranet](https://www.mangoapps.com/solutions/modern-intranet) and the apps their teams need today, then expand across communication, knowledge, operations, and people workflows on the same foundation. AI is the reason that single foundation counts. A chatbot bolted on top of disconnected tools cannot answer a question safely, because it has no shared view of identity, permissions, or content, while MangoApps grounds AI search and assistance in your own handbooks, policies, and SOPs with the access rules your IT team already wrote. Built for the frontline for 18+ years rather than retrofitted, MangoApps reaches desk and non-desk employees in one place, and it [connects with 200+ systems](https://www.mangoapps.com/integrations/) including Microsoft 365 and Google Workspace so it runs alongside the stack a UK enterprise already owns. **Key capabilities:** - [AI-powered enterprise search](https://www.mangoapps.com/solutions/modern-intranet): Employees ask questions in plain language and get answers sourced from your own content, not the open internet, with results gated by role so people only see what they are allowed to see. - [200+ integrations](https://www.mangoapps.com/integrations/): Native connections to Microsoft 365, Google Workspace, HRIS, and payroll systems let the intranet sit on top of existing tools, with SSO and document sync rather than a rip-and-replace project. - [Enterprise security and flexible deployment](https://www.mangoapps.com/security-compliance): HITRUST, SOC 2 Type II, and ISO 27001 certification, with deployment as SaaS, private cloud, customer VPC, or on-premise so UK and EU organisations can meet data-residency and sovereignty requirements. - [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee): MangoApps is the only vendor that backs adoption contractually, which matters for a large rollout where a stalled intranet is the most expensive outcome. - [Reach and engagement analytics](https://www.mangoapps.com/analytics-insights): Dashboards show who is reading, acknowledging, and acting on content across the whole workforce, giving comms and HR teams a measurable view of communication that reaches the frontline. UK health and beauty retailer [Superdrug](https://www.mangoapps.com/resources/superdrug-case-study), with 12,000 employees across more than 800 stores in the UK and Ireland, replaced an outdated intranet that staff had abandoned and chose MangoApps after evaluating more than 20 vendors. The result was fast, measurable adoption. > "We saw fantastic figures. In our first eight weeks, we had over 10,000 colleagues logged on, which is an incredible statistic for an intranet system for business, and those people have just continued to come back." > > > Vikki Nye, Internal Communications Manager, Superdrug **Free version:** No **Pricing:** Modular, quote-based; contact for enterprise pricing **Platforms:** Web, iOS, Android, Desktop [Schedule a demo to see MangoApps in action](https://www.mangoapps.com/schedule-a-call) ## Microsoft Viva / SharePoint Microsoft Viva and SharePoint form the intranet layer that many large UK enterprises already own through their Microsoft 365 licensing. Viva Connections surfaces a SharePoint home site inside Teams, so company news, resources, and tools appear in the application employees use for daily work, while Copilot can draw on intranet content held in SharePoint. For organisations standardised on Microsoft 365, that proximity to existing documents and identity is the central appeal. The boundary is that a polished, comms-led experience with rich audience targeting and a usable frontline mobile experience usually takes meaningful configuration, and reaching non-desk staff often depends on additional licensing. **Best for:** Microsoft-committed enterprises with internal IT capacity that want their intranet inside the Microsoft 365 tools employees already use. **Consider alternatives if:** Your priority is out-of-the-box internal communications, polished publishing, or reaching frontline staff who do not hold Microsoft 365 licences. - Teams and SharePoint integration: Viva Connections brings the intranet into the Teams interface. Employees reach news and resources without switching to a separate application, which suits desk workers already living in Teams. - SharePoint content backbone: A SharePoint home site provides pages, document libraries, and audience targeting. Larger organisations can structure content by department and region, provided they invest in governance to keep it current. - Copilot and Microsoft 365 grounding: Microsoft's AI works across Microsoft 365 data. Enterprises that have already adopted Copilot can extend it to intranet content stored in SharePoint without adding another vendor. **Free version:** Included with Microsoft 365 (Viva Connections and Engage); Viva Suite is a paid add-on **Pricing:** Viva Suite around $12 per user per month; Connections and Engage included with eligible M365 plans **Platforms:** Web, iOS, Android (via Teams), Desktop [Explore Microsoft Viva](https://www.microsoft.com/microsoft-viva) ## Unily Unily is a UK-founded enterprise experience platform built on Microsoft Azure, with roots in SharePoint consultancy that translate into deep Microsoft 365 expertise. It is designed for large, complex organisations that want a highly branded, customisable intranet and are prepared to invest in building it. Its co-developed Microsoft Graph and Copilot connectors give it some of the deepest Microsoft 365 grounding in the category, which appeals to enterprises that want AI to reach across their Microsoft estate. The trade-off is implementation weight: Unily projects are resource-intensive and tend to need dedicated internal ownership, so they fit organisations with the capacity to run them. **Best for:** Large, complex global enterprises that need deep Microsoft 365 integration, heavy customisation, and enterprise governance. **Consider alternatives if:** You need a fast, low-admin deployment, or you lack a dedicated internal team to own and maintain the platform. - Microsoft 365 grounding: Co-developed Graph and Copilot connectors let AI and search reach across Microsoft content. Enterprises with a large Microsoft estate get a tightly integrated experience. - Conversational layer: Unily offers a layer that can act across connected enterprise systems. This helps employees move from a question to an action without leaving the intranet. - Enterprise governance: Data-residency controls, DLP, and conditional access support large regulated organisations. Distributed author teams can publish within structured permissions. **Free version:** No **Pricing:** Enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop [Explore Unily](https://www.unily.com/) ## Interact Interact is a UK-headquartered intranet vendor with a long track record serving large and distributed organisations. It focuses on content management and internal communications at scale, with drag-and-drop authoring designed for big, distributed author teams and role-based authorisation to keep publishing controlled. Multichannel delivery lets communicators publish once and reach employees across web, mobile, and email, and a UK support desk is a practical consideration for UK buyers who want local service. The boundary is that Interact is a standalone platform rather than a Microsoft-tenant-native build, so organisations wanting their intranet constructed entirely inside SharePoint may find it a different model than they expect. **Best for:** UK and global enterprises that want a mature, governance-strong, branded intranet with strong content management and a UK support desk. **Consider alternatives if:** You want a low-touch, out-of-the-box tool, or you specifically need a Microsoft-tenant-native build rather than a separate platform. - Distributed authoring: Drag-and-drop content creation with role-based authorisation suits large author teams. Communications stay consistent while many contributors publish. - Multichannel delivery: A publish-once model pushes content across channels with predictive recommendations. Employees see relevant content without communicators rebuilding it per channel. - Content analytics: Interact provides AI-driven insight into content and search performance. Communicators can see what is read and refine what is not. **Free version:** No **Pricing:** Enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop [Explore Interact](https://www.interactsoftware.com/) ## Staffbase Staffbase is a German-headquartered employee communications platform with strong relevance for UK enterprises that prioritise EU or UK data residency. It centres on multichannel internal communications, reaching employees through a branded app, intranet, email, SMS, and digital signage from a single platform, which suits organisations with large dispersed or frontline workforces. Its named London and Frankfurt hosting options make data residency straightforward to document, a point that matters for UK GDPR-conscious buyers. The boundary is that Staffbase is built primarily as a communications platform, so enterprises wanting a single, deeply Microsoft-tenant-native build rather than a platform that runs alongside Microsoft 365 may weigh that difference. **Best for:** Enterprises with large frontline or dispersed workforces and strict EU or UK data-residency requirements. **Consider alternatives if:** You want a single intranet built natively inside your Microsoft 365 tenant rather than a standalone multichannel platform. - Multichannel reach: One platform delivers across app, intranet, email, SMS, and signage. Communicators reach desk and frontline staff through the channel each group actually uses. - Governed AI self-service: A governed model lets employees find answers while keeping content quality controlled. This reduces the risk of AI surfacing stale or unapproved material. - EU and UK hosting: Named London and Frankfurt hosting options support data-residency requirements. UK buyers can document where data is stored and processed. **Free version:** No **Pricing:** Enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop, Digital signage [Explore Staffbase](https://staffbase.com/) ## Simpplr Simpplr is an AI-forward employee experience platform aimed at mid-to-large enterprises that want an easy-to-use intranet with strong analytics and content governance. Its AI search can return answers and cite sources across connected systems such as SharePoint, Confluence, and ServiceNow, and an auto-governance engine helps keep content current as the intranet grows. The platform is known for a clean, low-friction experience that does not demand heavy configuration. The boundary is that Simpplr is built primarily for desk-based knowledge workers, so organisations whose main goal is reaching frontline staff on mobile, or who require a strictly UK-sovereign vendor, should confirm fit against those needs early. **Best for:** Mid-to-large enterprises that want an easy-to-use, AI-forward intranet with strong search and analytics. **Consider alternatives if:** You need a UK-sovereign vendor, or your primary use case is frontline-first mobile communication. - AI search with sources: Conversational search returns answers and cites where they came from across connected systems. Employees get a direct answer rather than a list of links. - Content governance: An auto-governance engine manages the content lifecycle and flags ageing material. Larger intranets stay usable instead of filling with stale pages. - Analytics and personalisation: Dashboards and personalised feeds help communicators target content. Teams can see engagement and adjust what they publish. **Free version:** Trial only **Pricing:** Enterprise, quote-based **Platforms:** Web, iOS, Android [Explore Simpplr](https://www.simpplr.com/) ## Workvivo Workvivo, owned by Zoom, is a social-led intranet and employee experience platform that prioritises culture and engagement. Its consumer-grade activity feed is designed to drive high adoption, and it reaches employees on mobile without requiring a Microsoft licence, which makes it a fit for organisations with a mix of desk and frontline staff. European data centre hosting is available, which is relevant for UK and EU buyers, and the platform integrates with both Microsoft 365 and Zoom. The boundary is that Workvivo's strength is communication and community rather than structured content management, so organisations that need deep document governance and information architecture may find its intranet page layer lighter than dedicated intranet tools. **Best for:** Zoom-anchored enterprises that want a culture-first, social, mobile intranet across desk and frontline teams. **Consider alternatives if:** You are outside the Zoom ecosystem and need deep structured content management and governance. - Social engagement: A consumer-grade feed encourages participation and recognition. High adoption follows because the experience feels familiar to employees. - Frontline reach: Employees can access the platform on mobile without a Microsoft licence. Organisations can reach staff who do not sit at a desk. - Connected AI search: AI search spans connected systems to surface content. Employees find information without knowing exactly where it lives. **Free version:** No **Pricing:** Enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop [Explore Workvivo](https://www.workvivo.com/) ## LumApps LumApps is a French-headquartered employee experience platform that now spans desk-based intranet and frontline mobile following its integration with Beekeeper. It integrates natively with both Microsoft 365 and Google Workspace, which makes it one of the stronger options for organisations on Google or running both ecosystems. Structured content targeting and multilingual publishing suit large, multinational enterprises that need to deliver the right content to the right audience across regions and languages. The boundary is that an organisation standardised entirely on Microsoft 365, wanting the single deepest Microsoft-native build, may prefer a more Microsoft-centric platform, while a team wanting a lightweight communications-only tool may find LumApps broader than they need. **Best for:** Multinational, multilingual enterprises, especially those on Google Workspace, that need structured content and enterprise governance. **Consider alternatives if:** You are a pure Microsoft 365 organisation wanting the deepest single-ecosystem build, or you want a lightweight comms-only tool. - Dual ecosystem integration: Native connections to both Microsoft 365 and Google Workspace suit mixed estates. Organisations are not forced into one productivity stack. - Desk and frontline reach: The platform combines intranet and frontline mobile after the Beekeeper integration. Enterprises can address both populations on one platform. - Multilingual targeting: Content targeting and translation support global, multilingual workforces. Employees receive relevant content in their language and region. **Free version:** No **Pricing:** Enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop [Explore LumApps](https://www.lumapps.com/) ## Invotra Invotra is a UK intranet vendor with a strong focus on the public sector, designed around the security, accessibility, and sovereignty requirements UK government and NHS organisations face. It is listed on the UK G-Cloud framework, offers UK-focused hosting, and builds in WCAG accessibility checking, which is a practical requirement for public-sector intranets. Its highly configurable information architecture and distributed publishing workflows suit large organisations with complex content and many contributors. The boundary is that Invotra is built for structured, governance-heavy public-sector environments, so a private-sector consumer brand wanting a glossy, social-first employee experience may find it a different style of product than they are looking for. **Best for:** UK central government, NHS, police, and local-authority buyers that need proven sovereignty, security, and accessibility. **Consider alternatives if:** You are a private-sector consumer brand wanting a polished, social-first employee experience. - Configurable architecture: Open, flexible information architecture and taxonomy suit complex organisations. Large bodies can model their structure and publishing workflows precisely. - Built-in accessibility: WCAG accessibility checking is built into content creation. Public-sector teams can meet their accessibility obligations as they publish. - Broad integration and sovereignty: A wide integration set plus UK-focused hosting and G-Cloud listing support regulated buyers. Procurement and data-residency requirements are easier to satisfy. **Free version:** No **Pricing:** Enterprise, quote-based (G-Cloud listed) **Platforms:** Web, iOS, Android, Desktop, Extranet [Explore Invotra](https://www.invotra.com/) ## Oak Engage Oak Engage is a UK-headquartered intranet platform built for organisations with large frontline and deskless workforces. It is designed around mobile access, so employees can use it without a corporate email address, and it pairs targeted AI-driven content delivery with social, recognition, and survey features aimed at building engagement. UK-based hosting with recognised security certifications is a useful point for UK buyers weighing data considerations. The boundary is that Oak Engage's centre of gravity is communication and engagement rather than deep document management, so organisations that need heavy enterprise content governance or a Microsoft-tenant-integrated build may find that scope narrower than a content-led intranet. **Best for:** UK enterprises with large frontline or deskless populations that need high mobile adoption and engagement. **Consider alternatives if:** You need deep enterprise document management and governance, or a Microsoft-tenant-integrated build. - Targeted content delivery: AI-driven smart delivery personalises communications by audience. Employees receive content relevant to their role and location rather than a generic broadcast. - Frontline access: Employees can use the platform on mobile without a corporate email account. Organisations can reach staff who never sit at a desk. - Culture features: Social feeds, recognition, and pulse surveys support engagement. Teams can build culture and gather feedback across locations. **Free version:** No **Pricing:** Enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop [Explore Oak Engage](https://www.oak.com/) ## Sorce / Engage Sorce is a UK-based intranet provider whose Engage product scales from small teams to tens of thousands of users, with a consultative delivery model that some UK organisations prefer. A distinctive point is flexibility: Sorce offers its own Engage platform or a Microsoft 365 and SharePoint-based build, so buyers can choose the model that fits their estate. Compliance-oriented features such as mandatory-read tracking and an accessibility partnership suit regulated and people-heavy sectors. The boundary is that Sorce is a focused UK supplier rather than a globally scaled, AI-native vendor with a very large partner ecosystem, so organisations wanting that scale and ecosystem may look elsewhere. **Best for:** UK mid-to-large organisations that want a flexible, consultative UK supplier with a standalone or SharePoint option. **Consider alternatives if:** You need a globally scaled, AI-native platform with a very large partner and integration ecosystem. - Flexible build options: Buyers can choose the Engage product or a Microsoft 365 and SharePoint build. Organisations align the model to their existing estate rather than the reverse. - Compliance communication: Mandatory-read tracking and mentions support comms that must be acknowledged. Regulated teams can evidence that messages reached staff. - Accessibility and recognition: An accessibility partnership and recognition modules round out the platform. Organisations can meet accessibility needs and support engagement. **Free version:** Trial only (30-day) **Pricing:** Paid / enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop [Explore Sorce](https://sorceintranet.co.uk/) ## How Each Platform Compares on Frontline Reach, UK Data Residency, and Microsoft 365 Fit Platform Frontline / Deskless Reach UK / EU Data Residency Microsoft 365 Integration Enterprise Content & Governance MangoApps Reaches frontline staff via a branded mobile app with no corporate email or laptop required. Deployable as SaaS, private cloud, customer VPC, or on-premise, supporting UK and EU data residency. Integrates with Microsoft 365 and 200+ systems, running alongside an existing M365 estate. AI search, no-code department sites, version control, and automated content review across desk and frontline. Microsoft Viva / SharePoint A full frontline mobile experience through Teams typically requires Microsoft F-series licensing. UK and EU residency available via Microsoft 365 data location commitments and the Advanced Data Residency add-on. Native to Microsoft 365, SharePoint, Teams, and Copilot. SharePoint provides content management and audience targeting, though polished comms layouts require configuration. Unily Mobile apps reach distributed staff, with frontline access dependent on configuration. Built on Microsoft Azure with regional data-residency controls; confirm the specific UK or EU region. Co-developed Microsoft Graph and Copilot connectors provide deep Microsoft 365 grounding. Enterprise governance with DLP, conditional access, and structured publishing for large author teams. Interact Mobile and white-labelled apps reach distributed staff across locations. Hosted on AWS with a UK service desk; confirm region for UK or EU residency. Integrates with Microsoft 365 and common enterprise systems alongside the platform. Mature drag-and-drop authoring, role-based authorisation, and multichannel publishing for distributed teams. Staffbase Reaches frontline employees through a branded app, email, SMS, and digital signage. Azure-hosted with named London and Frankfurt hosting options for UK and EU residency. Integrates with Microsoft 365, including Entra ID single sign-on, alongside the platform. Multichannel publishing with governed AI self-service and a layered content-quality model. Simpplr Mobile apps focus on content consumption rather than frontline operational workflows. Offers data-residency options across multiple regions; confirm UK or EU specifics. Integrates with Microsoft 365, Confluence, and ServiceNow for search and content. AI-assisted enterprise search and an auto-governance engine manage the content lifecycle. Workvivo Reaches frontline staff through a social mobile app without requiring a Microsoft licence. Hosted on Zoom's enterprise cloud with EU data centres available. Integrates with Microsoft 365 and Zoom; AI search spans connected systems. Strong social and comms layer; structured page and document governance is lighter than dedicated intranet tools. LumApps Combines desk-based intranet with frontline mobile following the Beekeeper integration. French-headquartered with EU region hosting options; confirm UK or EU specifics. Integrates natively with both Microsoft 365 and Google Workspace. Structured content targeting, multilingual publishing, and enterprise governance for global organisations. Invotra Provides mobile and extranet access, with a primary focus on desk-based public-sector users. UK-focused hosting and listed on the UK G-Cloud framework. Offers a broad integration set including Microsoft 365. Highly configurable information architecture, distributed publishing, and built-in WCAG accessibility checking. Oak Engage Reaches frontline employees on mobile without a corporate email address. Secure UK-based cloud with ISO 27001 and Cyber Essentials Plus certification. Integrates with Microsoft 365 and Workday alongside the platform. Targeted AI content delivery and social tools; document governance is lighter than enterprise content systems. Sorce / Engage Mobile app reaches dispersed staff; available as a standalone product or a SharePoint build. UK-based supplier with role-based access controls; confirm hosting region. Offers a Microsoft 365 and SharePoint build option in addition to its own product. Mandatory-read tracking, approval workflows, and accessibility tooling for mid-to-large organisations. *Capability statements for third-party vendors are taken from each vendor's public documentation and are vendor-stated, not independently verified by MangoApps.* No single platform leads on all four criteria. Microsoft Viva and Unily go deepest on Microsoft 365 grounding, Invotra and Staffbase offer the clearest documented UK or EU data residency, and MangoApps, Oak Engage, Staffbase, and Workvivo reach frontline staff without a corporate email or Microsoft licence, while Interact, Unily, LumApps, and Invotra carry the strongest enterprise content governance. The practical tension for UK enterprise buyers is that deep Microsoft 365 grounding, documented UK sovereignty, and genuine frontline reach rarely come from the same product, so the right choice depends on which of those three matters most for your workforce. ## Replacing SharePoint: which of these platforms fit Many UK enterprise intranet projects are SharePoint replacements, and the platforms above split into three routes. Staying on SharePoint and adding an intranet-in-a-box keeps data inside the Microsoft 365 tenancy but leaves frontline reach dependent on Teams licences. Adding a communications or employee-experience layer on Microsoft 365 (Staffbase, Unily, LumApps, Simpplr, Interact) improves publishing and engagement while SharePoint keeps the documents; frontline access depends on each vendor's app and licensing. Moving to an independent unified platform (MangoApps) integrates with Entra ID and Microsoft 365 for desk staff while providing identity from the HRIS for employees who never receive a Microsoft licence, so the 45% of the UK workforce on the frontline is reached on the same platform. The considerations that decide the route are Entra ID as the identity anchor in every case, where data lives under UK GDPR in each route, the per-employee licence cost of reaching frontline staff, and the Power Automate dependency for workflows on SharePoint-based options. The routes and trade-offs are laid out in the [SharePoint-replacement section of our 25-platform guide](https://www.mangoapps.com/articles/top-25-intranet-platforms-frontline-desk-workers#replacing-sharepoint-as-a-uk-enterprise-intranet-options-and-trade-offs), and the migration steps in [the SharePoint Server 2016/2019 migration checklist](https://www.mangoapps.com/articles/sharepoint-server-2016-2019-migration-checklist). For a governance-first ranking across ten platforms, including data residency and certifications, see [The 10 Best Employee Intranet Platforms for Governance, Compliance, and Global Workforce Communication](https://www.mangoapps.com/articles/best-intranet-platforms-governance-compliance-global). ## How to Choose: Matching Your Situation to the Right Platform **If you have a large frontline or deskless workforce** in retail, healthcare, manufacturing, logistics, or hospitality, prioritise platforms that reach staff on mobile without a corporate email account. MangoApps, Oak Engage, and Staffbase are built for this, and MangoApps additionally runs operational and people workflows on the same platform once the intranet is in place. **If you are deeply standardised on Microsoft 365** and want the intranet inside the tools employees already use, look first at Microsoft Viva and SharePoint, then at Unily for a richer, more customisable experience with co-developed Microsoft grounding. Confirm what reaching frontline staff will cost in additional licensing before you commit. **If you are in the UK public sector, NHS, or a regulated body** with sovereignty and WCAG 2.2 obligations, Invotra is built for that environment, with Interact a credible UK alternative that brings strong content management and a UK support desk. **If you have a strict UK or EU data-residency requirement in the private sector,** Staffbase offers named London and Frankfurt hosting, MangoApps supports residency through private cloud, customer VPC, or on-premise deployment, and Workvivo offers European data centre hosting. Ask each vendor to document where data is stored, processed, and controlled. **If your primary goal is culture and engagement** through a social, consumer-grade experience, Workvivo and Oak Engage are designed around participation and recognition. **If you are a multinational, multilingual organisation,** especially one on Google Workspace, LumApps handles dual-ecosystem integration and multilingual content targeting, with Unily a strong option for Microsoft-centric global enterprises. ## What Is an Enterprise Intranet? An enterprise intranet is a private, governed platform where employees across a large organisation access company communication, knowledge, services, and tools in one place. It goes beyond a basic file store or a single SharePoint site: a modern enterprise intranet combines a news and communication layer, a searchable knowledge base, department and team spaces, and increasingly an AI layer that answers questions from the organisation's own content. For large UK organisations, the definition has widened to include the frontline. A growing share of intranet projects now aim to reach staff who do not sit at a desk or hold a company email address, which means mobile access and identity that does not depend on a corporate laptop are part of what "enterprise intranet" means in 2026. ## Why an Enterprise Intranet Matters for UK Organisations The business case rests on engagement and the cost of lost information. [Gallup's State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) found that global employee engagement fell to 20% in 2025 and estimates low engagement cost the world economy roughly $10 trillion in lost productivity, which raises the stakes for UK employers trying to keep dispersed teams connected. There is also a hard productivity cost to information that employees cannot find. Frontline employees make up 45% of the UK workforce, about 16.7 million people, according to [Catalyst's 2025 UK report](https://www.catalyst.org/insights/2025/four-frontline-drivers-uk), and only 23% of frontline workers believe they have the technology they need to be productive, according to [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html). For a large UK enterprise, an intranet that surfaces the right answer quickly, and reaches every employee rather than only desk-based staff, turns those numbers in the right direction. ## What Features Should I Look for in Enterprise Intranet Software? A few capabilities matter more than the rest when evaluating intranet software at enterprise scale: - Enterprise search: Employees should be able to find an answer by describing what they need, not by knowing a file name or folder path. AI-assisted search that respects permissions is now a core expectation rather than a bonus. - Content governance and publishing: Large intranets fail when content goes stale. Look for version control, approval workflows, owner assignment, and automated review so the intranet stays accurate as it grows. - Mobile and frontline access: If you employ frontline or deskless staff, confirm that employees can use the platform on their own phone without a corporate email account or an extra licence. - Integration with your stack: The intranet should connect to Microsoft 365 or Google Workspace, your HRIS, and other core systems, with single sign-on, rather than becoming another silo. - Security and data residency: For UK enterprises, ISO 27001 and SOC 2 are a baseline, and you should be able to document where data is stored and processed to satisfy UK GDPR. - Accessibility: Confirm WCAG conformance and request an up-to-date accessibility statement. For UK public-sector bodies this is a legal requirement, and for private employers it supports duties under the Equality Act 2010. ## How to Choose the Right Enterprise Intranet in the UK A practical evaluation runs in stages. Start by shortlisting on the two factors that eliminate vendors fastest: documented UK or EU data residency, and the depth of fit with your existing Microsoft 365 or Google Workspace estate. Then segment by workforce shape, separating platforms built for desk-based knowledge workers from those that genuinely reach frontline staff on mobile, because few products excel at both. Before any demo, ask each finalist for evidence rather than claims: a current WCAG 2.2 accessibility statement, ISO 27001 and SOC 2 documentation, data-residency detail covering where data is stored and controlled, and references from UK organisations of comparable size. Adoption is the single biggest predictor of whether an intranet pays back, so weight ease of use and mobile reach heavily. For frontline-heavy organisations in retail, healthcare, manufacturing, and similar sectors, MangoApps is worth evaluating specifically because it is designed to reach the whole workforce and backs adoption contractually. ## Frequently Asked Questions **What is an enterprise intranet?** An enterprise intranet is a private, governed platform where employees across a large organisation access company communication, knowledge, services, and tools in one place. Modern versions add AI-assisted search and reach frontline staff on mobile, not just desk-based employees. **How much does an enterprise intranet cost in the UK?** Most enterprise intranets are priced on a quote basis rather than published rates. Expect per-user pricing that falls sharply at scale, plus one-off costs for implementation, content migration, and customisation, so the total cost of ownership matters more than the headline per-seat figure. **Is SharePoint an intranet?** SharePoint can serve as an intranet backbone, and many organisations build on it, but on its own it is a content and document platform rather than a finished intranet. Reaching frontline staff, delivering targeted communications, and maintaining governance usually require significant configuration or an intranet product layered on top. **What is the difference between an intranet and Microsoft Viva?** Microsoft Viva is Microsoft's employee experience layer that surfaces a SharePoint intranet inside Teams, so it is one way to deliver an intranet rather than a separate category. Dedicated intranet platforms add richer communications, content governance, and cross-platform reach, particularly for frontline employees. **Which intranet platforms support UK or EU data residency?** Several do, including Staffbase with named London and Frankfurt hosting, Invotra with UK-focused hosting, Workvivo with European data centres, and MangoApps through private cloud, customer VPC, or on-premise deployment. Always ask the vendor to document where data is stored, processed, and controlled rather than relying on a general residency claim. **What features should enterprise intranet software have?** The essentials are AI-assisted enterprise search, content governance and publishing workflows, mobile and frontline access, integration with Microsoft 365 or Google Workspace, recognised security certifications, and accessibility conformance. For UK organisations, documented data residency belongs on that list too. **How do you drive employee adoption of a new intranet?** Reach employees where they already are, which for frontline staff means a mobile app that works without a corporate email account, then target content so people see what is relevant to their role and location. Integrating the intranet with daily-use tools and measuring engagement so you can adjust are the other reliable drivers, and adoption is the single biggest factor in intranet return on investment. **Which intranet platforms work best for frontline and deskless employees?** Platforms that offer mobile access without requiring a corporate email or Microsoft licence are the best fit, including MangoApps, Oak Engage, and Staffbase. Confirm that the mobile experience covers the workflows your staff actually need, not only reading announcements. **Do UK public-sector intranets need to meet accessibility standards?** Yes. The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 cover intranets and require conformance to the current WCAG standard, now WCAG 2.2 AA, along with a published accessibility statement. **What are common mistakes when choosing an enterprise intranet?** The most common are buying on a feature checklist rather than on workforce shape, underestimating content migration and adoption effort, and leaving data-residency and accessibility checks until late in the process. Confirming those requirements early, and prioritising adoption, avoids the most expensive mistakes. --- # How to Improve Frontline Intranet Adoption in 2026 **Author:** Andy Tolton **Published:** 2026-06-24 **Category:** intranet Learn nine proven moves to raise frontline intranet adoption with mobile-first design, governance, and compliance built in. Most employee intranets reach about 13-percent of people daily. The frontline, the 80-percent of the workforce that needs information most, usually gets the least of it. Here is how internal communications, HR, IT, and operations leaders close that gap with mobile-first design, governance, and compliance built in from the start.* **Short answer:** Frontline intranet adoption improves when the platform is built for the phone the employee already carries, removes the corporate-email login barrier, and earns daily opens by putting a high-value workflow (the schedule, pay, the next task) on the home screen. Legacy intranets average 30 to 40-percent adoption because they were designed for desks. Frontline-first platforms reach above 90 percent within 90 days by inverting that assumption, then hold it with governance and compliance the workforce can trust. If you are reading this, you almost certainly have an [employee intranet](https://www.mangoapps.com/solutions/modern-intranet) already. Nearly every enterprise does. The problem is not access to a tool. The problem is that the tool reaches the people sitting next to a corporate inbox and stops at the door of the store, the unit, the line, and the job site. That gap is expensive, and it is measurable. This guide walks through why frontline adoption fails, the nine moves that consistently raise it, how to measure it honestly, and the mistakes that quietly cap it at 40-percent. The framework is vendor-neutral. Where a real example helps, we use MangoApps customer data, because the numbers are specific and verifiable. ## The adoption gap is real, and it has a number **Across organizations, 91-percent have an intranet, but only 13-percent of employees use it daily, and 31-percent never use it at all.** The shortfall concentrates on the frontline, where workers have no corporate email, no assigned device, and no time to hunt through a portal mid-shift. Industry benchmarks tell a consistent story. According to [Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) research, daily intranet use sits at 13-percent while nearly a third of employees never touch it. Adoption also varies sharply by region: daily intranet use at 61-percent in Germany, 50-percent in Australia, 45-percent in the UK, and 39-percent in the US. Social Edge Consulting benchmarks 60-percent weekly active users as a successful intranet and 85-percent weekly login as best practice. Most organizations are nowhere near that, and the reason is almost always the same: the platform was never built to reach people without a desk. The cost compounds beyond a low usage chart. Gallup's [State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) estimates low engagement drains the global economy of roughly 10 trillion dollars, about 9-percent of global GDP, and its [Q12 meta-analysis](https://www.gallup.com/workplace/236927/employee-engagement-drives-growth.aspx) links top-quartile engagement to 23-percent higher profitability and 81-percent lower absenteeism, which is why [internal communications](https://www.mangoapps.com/solutions/internal-communications) that reach the frontline matter. When the intranet does not reach the frontline, internal communications cannot do its job, and [employee engagement](https://www.mangoapps.com/solutions/employee-engagement) work that depends on reaching people simply has no channel. - **13%** of employees use their intranet daily *(Social Edge Consulting, 2025)* - **31%** never use the intranet at all *(Social Edge Consulting, 2025)* - **80–85%** weekly active users at best-in-class intranets *(Social Edge Consulting, 2025)* ## Why frontline adoption is a different problem **Desk adoption and frontline adoption are not the same problem at different scales. They are different problems. The frontline employee has no corporate email, no assigned laptop, and no slack in the day to log into a portal.** Every design assumption baked into a traditional intranet works against them. For two decades, employee software was designed around a desk worker: a person with a company email address, a laptop, single sign-on already configured, and time between meetings to read. The frontline has none of that. The associate opening a store, the charge nurse starting rounds, the warehouse technician picking up a work order, and the field service tech driving to a job all share the same reality. Their device is a phone, often a personal one. Their connectivity is uneven. Their shift has no reading time built into it. So a frontline intranet succeeds or fails on a different set of questions than a desk intranet. Can someone use it without an email address? Does it work on a phone, in their language, when the signal drops? Does it open to something they need this shift, not a newsletter from headquarters? Get those wrong and adoption caps around 40-percent no matter how good the content is. Get them right and the same workforce that ignored the old intranet opens the new one every day. ## Nine moves that raise frontline intranet adoption The following nine moves are ordered roughly by impact. The first three remove the structural barriers that block adoption entirely. The middle three build the trust and accountability that sustain it. The last three are the operational discipline that keeps it above 80-percent instead of decaying back to 40. ### Move 01: Design for the phone they already carry, not the laptop they do not have Mobile-first is not a checkbox for a responsive web page. It means a real [native app experience](https://www.mangoapps.com/solutions/employee-app): push notifications that reach a lock screen, offline mode for environments where connectivity drops, fast load on older devices, and navigation a person can use one-handed while standing on a floor. Only 23-percent of frontline workers believe they have the technology they need to be productive, and the right mix lifts productivity about 22-percent, according to [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html), but only when those tools actually fit how people work. On the frontline, the phone is the workplace computer. Design from there. A practical test: hand the app to someone who has never seen it, on their own phone, with no training. If they cannot find this week's schedule in under thirty seconds, the design is still built for a desk. ### Move 02: Remove the login barrier The single most common reason a frontline worker never opens the intranet is that they cannot get in. They were issued no corporate email, so the SSO flow has nothing to authenticate against, and the IT-issued credential they would need does not exist for an hourly associate. Every extra step between a person and the app is a place adoption leaks out. The platforms that reach the frontline let employees onboard with a phone number or an employee ID, no corporate email required, and they keep re-entry to a single tap. [Benchmark Human Services](https://www.mangoapps.com/resources/benchmark-human-services) reached a workforce of more than 4,000 employees on mobile, none of whom had a company email address. That is not a feature detail. It is the difference between reaching the frontline and not. ### Move 03: Anchor the home screen to a workflow they need every shift Communication alone does not drive daily adoption. Utility does. The fastest-adopting frontline intranets open to something the employee needs to do their job today: the [schedule](https://www.mangoapps.com/solutions/workforce-management), pay and benefits information, the day's task list, the safety form, the two-minute training. Once the app is where the schedule lives, people open it every shift, and the communications, recognition, and knowledge content get read as a byproduct. > "Before, I took a picture of the schedule and posted it in WhatsApp. But sometimes people lost it or deleted it. Now they can open the app, click on the schedule, and see when they have to work. They never contact me anymore with questions. It saves me a lot of time." > > > — Vera Scherff, Kruidvat Store Manager, A.S. Watson [A.S. Watson](https://www.mangoapps.com/resources/aswatson-case-study) made schedule access the flagship workflow for more than 16,000 Kruidvat store employees, with over 20,000 retail staff receiving weekly schedules through the mobile app. Adoption passed 80-percent, and most employees signed themselves up before attending any onboarding session, because the app did something they needed. ### Move 04: Govern content so people can trust what they find Intranet governance is the set of rules and ownership that keep content accurate, current, and findable: named content owners, publishing and approval workflows, archiving and expiry dates, audience targeting so people see what is relevant to their role and location, and a search experience that returns answers rather than a list of stale links. Governance is not bureaucracy for its own sake. It is the foundation of trust, and [trust is what sustains adoption](https://www.mangoapps.com/resources/modern-intranet-accountability). The failure mode is easy to recognize. Holt of California ran an intranet where documents from 2012 were still live and no one knew why, search did not work, and finding a colleague took 30 minutes. Usage fell because employees stopped believing the platform would have what they needed. After [replacing it with a governed, searchable hub](https://www.mangoapps.com/resources/creating-massive-time-savings-with-mangoapps), search became the single most-cited benefit, time spent finding information dropped by 50-percent, and questions to departments fell 40-percent because people could self-serve answers they trusted. Governance turned a dead intranet into an 85-percent weekly-engagement platform. ### Move 05: Build compliance in, not bolted on For regulated industries, compliance is not a constraint on adoption. It is a driver of it, because it puts mandatory workflows where people already are. When acknowledgment tracking, read receipts, audit-ready records, policy attestation, role-based access, and mobile [safety and compliance training](https://www.mangoapps.com/solutions/safety-compliance) all run inside the same app as the schedule, employees complete them in the flow of work instead of through a separate portal they would otherwise ignore. In healthcare, that means HIPAA-aligned delivery and BAA coverage; in any regulated setting it means [certifications such as HITRUST, SOC 2 Type II, and ISO 27001](https://www.mangoapps.com/security-compliance), plus retention and eDiscovery that hold up to audit. [CBHA](https://www.mangoapps.com/resources/columbia-basin-health-associate-case-study), a community [healthcare](https://www.mangoapps.com/industries/healthcare) network with frontline clinical staff making up more than two-thirds of its workforce, used the same platform for patient safety and compliance training and reached over 90-percent monthly engagement against an original goal of 75-percent within two years. ### Move 06: Make managers the engine, not the bottleneck Every frontline workflow runs through the store, site, or shift manager: scheduling, [task dispatch](https://www.mangoapps.com/solutions/task-management), training assignments, announcements, safety acknowledgments, recognition, escalations. When those live in five different tools or in the manager's phone contacts, the manager becomes a bottleneck by default. Put them in one app and the manager becomes the adoption engine, because the team follows the manager's tool. The platforms that win frontline adoption give managers a single place to run the team and give employees enough self-service that they stop texting the manager about things they can now see for themselves. > "Huddle has been a lifesaver for us. We can reach 600 staff members in an instant, which we were never able to do before." > > > — Caitlin Petit, Director of Event Services, Kansas City Chiefs The [Kansas City Chiefs](https://www.mangoapps.com/resources/kansas-city-chiefs-case-study) consolidated email, text, a Facebook page, and a separate scheduling portal into one branded app for event staff. Adoption reached 90-percent, up from a 40-percent average across the prior patchwork of tools. ### Move 07: Translate and localize for the actual workforce A frontline workforce is rarely monolingual, and a platform that only works in English excludes the people it most needs to reach. Real localization means [content delivered in each employee's language automatically](https://www.mangoapps.com/ai/translation), not a manual translation step that publishers skip under deadline. A.S. Watson delivers schedules and communications with automatic translation across its multi-country store base. Platforms that support 50-plus languages natively remove a barrier that, left in place, silently caps adoption among a large share of the frontline. ### Move 08: Measure adoption by segment, not as a company average A single company-wide adoption number is the most dangerous metric in this whole effort, because a strong headquarters figure can hide near-zero frontline use. Break the number down by workforce segment, by location, and by role. Watch reach, active use, and engagement quality as three separate signals, and use platform [analytics](https://www.mangoapps.com/analytics-insights) that report by segment rather than a single blended figure. The next section breaks down exactly what to track. ### Move 09: Tie launch to accountability Adoption that no one owns drifts back to 40-percent. The organizations that hold high adoption assign it as an outcome, review it in quarterly business reviews alongside operational KPIs, and treat a launch as the start of an adoption program rather than the end of an implementation. The strongest version of this is contractual: at least one platform in this category offers an [Adoption Guarantee](https://www.mangoapps.com/success-services), meaning if employees do not adopt after launch, the customer does not pay. Whether or not your vendor backs adoption that way, build the accountability in yourself. ## How to measure intranet adoption (the metrics that matter) **Measure adoption with three distinct signals: reach (the percentage of the workforce you can deliver to), active use (daily and weekly active users by segment and location), and engagement quality (read and acknowledgment rates, search success, task completion).** A single blended average will mislead you. Segment everything. Here is a working benchmark table you can hold your own platform against. The benchmark column draws on Social Edge Consulting intranet research; the frontline-first column reflects what platforms built for deskless work consistently report. | Metric | What it tells you | Typical / benchmark | Frontline-first target | | --- | --- | --- | --- | | Daily active users | Habitual use | 13% (most intranets) | 60%+ | | Weekly active users | Routine reach | 60% (good); 80–85% (best-in-class) | 85%+ | | Never-users | Total exclusion | 31% | Under 10% | | Search success rate | Trust & findability | 75%+ is good | 80%+ | | Must-read / acknowledgment rate | Critical comms reach | Often untracked | 90%+ on priority posts | | Newsletter / post open rate | Content relevance | 65%+ benchmark | 70%+ | | Employee satisfaction with the platform | Perceived value | 4.2 / 5 benchmark | 4.4 / 5+ | | Time to 90% adoption | Onboarding effectiveness | Often never reached | Within 90 days | Two measurement notes that change how leaders read these numbers. First, reach is not the same as engagement. A platform can technically deliver to 100-percent of the workforce and still have 13-percent open it; you need both numbers. Second, acknowledgment tracking is the metric most organizations skip and most need, because it is the only way to prove a safety notice, a policy change, or a recall instruction actually landed. On the frontline, "we sent it" and "they saw it" are very different claims, and only one of them holds up in an audit. ## The mistakes that quietly cap adoption at 40-percent Most stalled adoption efforts fail in predictable ways. If your number is stuck, it is probably one of these. - **Treating the frontline as a smaller version of the desk workforce.** They have different devices, different access, and different time. A scaled-down desk experience does not reach them. - **Requiring a corporate email to log in.** This excludes the majority of the frontline before the content even matters. - **Launching with communication content only.** News and announcements do not create a daily habit. A needed workflow does. - **No governance, so search returns garbage.** Once people get a stale or wrong answer twice, they stop searching, then they stop opening the app. - **Measuring a single company-wide average.** It hides the exact failure you are trying to find. - **Stacking point tools.** A separate app for the schedule, another for training, another for comms, and another for safety means four logins, four broken handoffs, and no single place that becomes the habit. [Consolidating onto one platform](https://www.mangoapps.com/resources/harnessing-an-employee-superapp) is itself an adoption lever. - **Stopping at launch.** Adoption is a program, not a project. Without ongoing ownership it decays. > **How MangoApps approaches this** > > > > ### One app the frontline actually opens > > > MangoApps is the AI-Ready Employee Platform for the Frontline. It is built on a single principle that is the reason its customers reach the adoption numbers above: every workflow an employee needs to do their job, the schedule, the task list, the training, the announcement, the clock-in, the safety form, lives in one app, on the phone they already carry, with no corporate email and no login friction. > > > That design is not new for MangoApps. The company has built for the frontline for more than 18 years, which is why adoption above 90-percent in 90 days is a pattern across its base rather than a launch-week spike. The platform reaches more than 2 million users, holds 98-percent customer retention and a Net Promoter Score of 78, and runs in 50-plus languages with offline mode for environments where connectivity drops. > > > Governance and compliance are part of the platform, not an add-on. Audience targeting, acknowledgment tracking, content lifecycle controls, and a search that returns answers keep content trustworthy. HITRUST, SOC 2 Type II, and ISO 27001 (the only unified employee platform to combine all three), plus FedRAMP ATO, HIPAA, and GDPR coverage, make it deployable in the most regulated environments. AI is grounded in the same shared identity, permissions, and employee data, so it can [act safely across every workflow](https://www.mangoapps.com/ai/governance) rather than sitting on top as a disconnected chatbot. > > > And MangoApps is the only vendor in the category to back adoption with an Adoption Guarantee: if employees do not adopt after launch, you do not pay. That offer exists because the adoption pattern is consistent enough to stand behind. > > > > > "About 80-percent of our 55,000 employees largely did not have access. MangoApps gave us the ability to actually reach our entire associate base for the first time ever." > > > > > > — Sheena Christensen, Corporate Communications Manager, PetSmart ## A 90-day adoption plan you can run If you are starting from a stalled intranet, here is a sequence that consistently works, independent of which platform you choose. 1. **Weeks 1–2: Pick the anchor workflow.** Find the one thing your frontline needs every shift. In most organizations it is the schedule. In field operations it is the work order. In healthcare it is shift handoff and compliance. Lead with that, not with the news feed. 2. **Weeks 3–6: Remove the access barriers.** Set up email-free onboarding, configure the mobile app, enable the employee's language, and test it on a real frontline worker's personal phone before anyone in IT signs off. 3. **Weeks 5–8: Stand up governance.** Assign content owners, set expiry dates, define audience targeting by location and role, and confirm search returns the right answer for the ten questions employees ask most. 4. **Weeks 7–10: Make managers the launch team.** Train managers first, give them the dashboard to run their team, and let adoption spread through them. 5. **Weeks 9–12: Measure by segment and tighten.** Track reach, daily and weekly active use, acknowledgment rates, and search success by location. Find the segments below target and fix the specific barrier, do not average it away. 6. **Day 90 onward: Run adoption as a program.** Review the segmented numbers quarterly alongside operational KPIs, and expand into the next workflow once the first is habitual. ## Frequently asked questions ### What is a good frontline intranet adoption rate? Social Edge Consulting benchmarks 60-percent weekly active users as a successful intranet and 85-percent weekly login as best practice. Most legacy intranets sit at 30 to 40-percent because they were designed for desk workers. Frontline-first platforms commonly reach above 90-percent within 90 days of launch by designing for the phone the employee already carries. ### Why do frontline workers not use the company intranet? Frontline workers usually do not adopt the intranet because it was built for desk workers with corporate email and a laptop. Frontline employees often have no company email address, no assigned device, and no time to log into a portal during a shift. When the intranet requires a login they do not have, or surfaces content that is not relevant to their shift, they stop opening it. ### How do you measure intranet adoption? Measure intranet adoption with three distinct signals: reach (the percentage of employees the platform can deliver to), active use (daily and weekly active users by segment and location), and engagement quality (read and acknowledgment rates, search success rate, and task completion). Track these by workforce segment, not as a single company-wide average, because a high headquarters number can hide near-zero frontline use. ### What is intranet governance and why does it affect adoption? Intranet governance is the set of rules and ownership that keep content accurate, current, and findable: clear content owners, publishing and approval workflows, archiving and expiry dates, audience targeting, and search quality standards. It affects adoption directly because employees stop using a platform they cannot trust. When search returns outdated or irrelevant results, usage collapses. ### How long does it take to improve intranet adoption? On a platform built for the frontline, adoption typically climbs above 90-percent within 90 days of launch, with a typical implementation taking 8 to 12 weeks. The pace depends less on the technology and more on whether the first workflow you launch is something employees need every shift, such as the schedule, pay information, or the day's task list. ## See what 90-percent adoption looks like For the governance and compliance side of the same problem, see [How to Increase Frontline Intranet Adoption Without Sacrificing Governance or Compliance](https://www.mangoapps.com/articles/frontline-intranet-adoption-governance-compliance). If adoption is stuck because the platform itself no longer fits the workforce, see [8 Signs Your Frontline Organization Has Outgrown Its Employee Intranet](https://www.mangoapps.com/articles/intranet-problems-hurting-frontline-teams). MangoApps reaches the frontline the way the rest of your stack cannot: one app, on the phone they already carry, with governance and compliance built in. Start with the workflow your teams need today and expand on the same platform when you are ready. **[Schedule a call →](https://www.mangoapps.com/schedule-a-call)** *Sources cited: Social Edge Consulting (2025), Gallup, Deloitte. MangoApps customer outcomes are drawn from published case studies (A.S. Watson, Kansas City Chiefs, Holt of California, CBHA, Benchmark Human Services, PetSmart).* --- # Best Employee Intranet Platforms for Frontline Teams in 2026 **Author:** MangoApps Team **Published:** 2026-06-24 **Category:** intranet Compare the best intranet platforms for frontline teams and workers, from no-email enrollment to mobile-first engagement and digital signage. For organizations where most employees work in stores, on manufacturing floors, in care settings, or in the field, a standard corporate intranet was designed for a workforce that doesn't look like theirs. Traditional intranet platforms assume workers have a company email address, a desk, and time to log in between meetings, assumptions that structurally exclude the frontline majority before a single page is published. The platforms on this list are evaluated specifically for their ability to reach, inform, and engage deskless and shift-based workers, not just the desk-based employees those workers support. Software Best For Workforce Fit Platforms MangoApps Frontline-heavy enterprises needing a full intranet, operations, and people platform with no-email enrollment and a written adoption guarantee Mixed desk + frontline, 500–300,000+ employees Web, iOS, Android, Desktop Microsoft Viva Connections Microsoft 365-standardized organizations extending SharePoint to frontline workers via Teams and Frontline (F) licensing Mixed desk + frontline, enterprise scale Web, iOS, Android, Desktop (via Teams) Unily Large global enterprises (5,000+ employees) where a deeply branded, highly integrated intranet experience is the primary internal communications channel Primarily desk + managed frontline via branded mobile app Web, iOS, Android, Desktop Oak Engage Mid-to-large organizations replacing an outdated intranet that need fast frontline mobile adoption without corporate email requirements Frontline-heavy, 500–50,000+ employees Web, iOS, Android LumApps Large enterprises running mixed Google and Microsoft productivity stacks that want desk and frontline coverage under one vendor after the Beekeeper merger Mixed desk + frontline; product integration ongoing as of 2026 Web, iOS, Android, Desktop Sociabble Large multilingual enterprises with distributed frontline populations where employee engagement, advocacy, and multichannel reach are the primary priorities Frontline + desk, multilingual workforces Web, iOS, Android, Desktop Interact Mid-to-large enterprises that want a communications-led intranet with strong knowledge discovery, audience targeting, and a track record in regulated industries Primarily desk; frontline via mobile app Web, iOS, Android, Desktop Appspace Multi-site manufacturers, retailers, and hospitality operators that need intranet, mobile app, and digital signage unified under a single vendor On-site frontline workers, including those without smartphones Web, iOS, Android, Desktop, Digital signage theEMPLOYEEapp Frontline-heavy mid-market organizations wanting an affordable mobile-first communications and knowledge platform without corporate email requirements Frontline-majority, 100–10,000 employees Web (admin), iOS, Android Haystack Mid-market organizations that want a fast-to-deploy, search-led intranet with a consumer-grade mobile experience and straightforward onboarding Mixed desk + frontline Web, iOS, Android, Desktop *Capability statements for third-party vendors are taken from each vendor's public documentation and are vendor-stated, not independently verified by MangoApps.* MangoApps 4.6/5 Stars · Gartner Peer Insights 2M+ Users · Trusted Worldwide Gartner MQ Visionary · Intranet Packaged Solutions (2025) IDC MarketScape Leader · Employee Experiences (2024) Forrester Wave Strong Performer · Intranet Platforms (Q2 2026) Reworked IMPACT Award (Gold) · Intranet & Communications Platforms Most intranet platforms were built for employees who sit at a desk, use a company email address, and log in from a corporate network. [MangoApps](https://www.mangoapps.com/solutions/modern-intranet) was built differently. As the AI-Ready Employee Platform for the Frontline, it reaches every employee through [OneMango](https://www.mangoapps.com/solutions/employee-app), a branded app workers download on the device they already carry. No corporate email, no VPN, and no shared kiosk required.. Store associates, warehouse technicians, care staff, and field workers get the same personalized intranet experience as HQ employees, in 50+ languages, with offline access for low-connectivity environments. For frontline-heavy organizations that have watched previous intranet launches stall at 30-40% adoption, MangoApps backs every deployment with a written [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee): 90%+ employee adoption in 90 days, or you don't pay. The platform also extends beyond communications into workforce operations and people management, so organizations can consolidate scheduling, task management, training, and HR workflows onto the same foundation rather than running a separate system for each. **Key capabilities:** - **[OneMango Frontline Access](https://www.mangoapps.com/solutions/employee-app):** Frontline workers enroll via QR code, SMS, or employee ID on a personal device. No corporate email or IT provisioning required. Managers can add new employees in minutes and the app supports 50+ languages with automatic translation for global workforces. - **[AI-Powered Search and Knowledge Hub](https://www.mangoapps.com/solutions/modern-intranet):** Every employee gets a personalized dashboard tailored to their role, location, and team. The AI search layer spans the full content library so a technician on the floor can find a safety procedure, policy update, or training document in seconds from a phone. - **[Multi-Channel Targeted Communications](https://www.mangoapps.com/solutions/internal-communications):** Communicators can reach specific audience segments by role, location, shift, or department via app, email, SMS, and push notification in a single send. [Read receipts and engagement analytics](https://www.mangoapps.com/analytics-insights) confirm delivery and surface which content is landing. - **[Campaigns and Mandatory Reads](https://www.mangoapps.com/key-features/campaigns-and-journeys):** Critical policy updates, compliance communications, and safety notices can be sent as mandatory reads with confirm-read capability and a full audit trail, covering frontline workers who don't have a company inbox. - **[200+ Enterprise Integrations](https://www.mangoapps.com/integrations/):** MangoApps connects with the HRIS, scheduling, payroll, and operational tools frontline organizations already run, so the intranet sits inside the workday rather than alongside it. Most customers retire four to five separate tools in the first 18 months after deployment. > "We wanted to empower employees. We wanted employees to be able to get the information that helps them in their daily job directly. Not indirectly via the one pc in the store or via their store manager." > Jan Kees Fokkens, Social Intranet Project Manager, [A.S. Watson Benelux](https://www.mangoapps.com/resources/aswatson-case-study) A.S. Watson Benelux, the health and beauty retail group behind Kruidvat, Trekpleister, and ICI PARIS XL across four countries, deployed MangoApps to connect 27,000 store employees who had no company email addresses. Within the first rollout window, over 80% of Kruidvat's 16,000 employees became active users, many signing up before their formal onboarding session because the app felt intuitive enough to navigate without training materials. Over 20,000 retail associates now access their work schedules through the MangoApps mobile app, eliminating the schedule confusion that previously generated constant manager inquiries. **Free version:** No **Pricing:** Modular, quote-based; contact for enterprise pricing **Platforms:** Web, iOS, Android, Desktop [Schedule a demo to see MangoApps in action](https://www.mangoapps.com/schedule-a-call) ## Microsoft Viva Connections Microsoft Viva Connections surfaces a SharePoint intranet inside the Microsoft Teams mobile app, giving frontline workers a branded company home with targeted news, a configurable Dashboard, and access to organizational resources. For organizations already standardized on Microsoft 365, it is a natural first intranet option because it reuses existing infrastructure: SharePoint handles content, Teams delivers the experience, and Frontline (F) licensing provides a lower-cost identity for workers who don't need a full Microsoft 365 subscription. The Dashboard can display shift information from Teams Shifts, task cards from Planner, and real-time data from HR and scheduling systems through Adaptive Card Extensions (ACEs). Administrators can target news and Dashboard cards by role, location, and department, so a store associate in one region sees different content than a distribution center worker in another. The primary planning consideration for frontline buyers is identity: every worker needs a Microsoft Entra ID to enroll. Workers without a corporate email require IT to provision accounts before they can access the intranet, which adds pre-launch complexity and ongoing account management overhead for high-turnover environments. Organizations with large non-Microsoft workforces, or those that need a simpler enrollment path for hourly staff, typically find the configuration burden significant. **Best for:** Organizations already running Microsoft 365 at enterprise scale that want to extend their SharePoint intranet to frontline workers using existing Teams infrastructure. **Consider alternatives if:** A meaningful portion of your workforce lacks a Microsoft identity or your IT team cannot support the configuration required to deliver a consistent frontline experience through Viva Connections. - **Frontline (F) Licensing and Teams Access:** Microsoft offers Frontline Worker SKUs (F1, F3) that provide Teams, SharePoint, and Viva Connections access at a lower per-user cost than full M365 licenses. This makes it viable to extend the intranet to large hourly workforces without purchasing a full productivity suite for every employee. - **Configurable Dashboard with Live Data Cards:** The Viva Connections Dashboard supports Adaptive Card Extensions that pull real-time information from connected systems, including shift schedules from Kronos or UKG, task queues from Planner, and approval requests from across the M365 ecosystem. For organizations deeply invested in Microsoft infrastructure, these live-data cards reduce context switching for frontline workers. - **Audience Targeting on News and Dashboard Cards:** SharePoint audience targeting lets communicators surface role- or location-specific news directly on a worker's Viva Connections home without requiring them to navigate department pages. A new product update reaches store staff; a warehouse safety notice reaches distribution employees. Both arrive on the Teams mobile app home screen. **Free version:** No (included in existing M365 licensing; no standalone free tier) **Pricing:** Included with M365 E3/E5 or Viva Suite; Frontline F1 starts at approximately $2.25 per user/month (verify current pricing with Microsoft) **Platforms:** Web, iOS, Android, Desktop (via Teams) [Explore Microsoft Viva Connections](https://www.microsoft.com/microsoft-viva/connections) ## Unily Unily is an enterprise intranet and employee experience platform built for large, globally distributed workforces. The platform delivers a personalized, highly branded intranet experience through web and a native iOS/Android app, with content and navigation tailored to each employee's role, location, language, and interests. Its audience builder allows administrators to create targeting rules that control what news, pages, and navigation items a given segment sees, down to the individual employee level. For frontline buyers, the relevant capability set includes push notifications, mandatory reads, shift swap and leave request integrations via connected HR systems, and a native AI agent called Indi that can accelerate content creation and help employees find information. Unily fits organizations where the intranet sits at the center of internal communications strategy and where a premium, polished experience for every workforce segment is a stated requirement. The platform is designed and priced for organizations with 1,000 or more employees, and buyers at smaller scales typically find the investment disproportionate to their scope. Some design customizations require direct HTML, CSS, or JavaScript edits, which places a ceiling on how much non-technical administrators can do without developer involvement. **Best for:** Large global enterprises where a deeply branded, feature-rich intranet is the core internal communications channel and where frontline workers are an important but not the majority audience. **Consider alternatives if:** Your organization is below 1,000 employees, your frontline population lacks corporate email and needs guaranteed no-email enrollment out of the box, or you need operational workflows beyond communications. - **Limitless Audience Builder:** Unily's targeting rules can govern search results, navigation menus, news feeds, and content visibility simultaneously, so a worker in a specific role at a specific location sees a completely different intranet experience without requiring separate content to be created for each segment. For large multi-site employers, this reduces the administrative burden of keeping communications relevant across dozens of locations. - **Integration Execution Layer:** The platform connects with HRIS and workforce management systems to surface operational actions inside the intranet, including shift swaps, leave requests, and payslip access. Workers complete these tasks without leaving the app, which increases the daily visit frequency that sustains intranet adoption over time. - **Indi AI Agent:** Unily's native AI agent can draft content from a prompt, generate page layouts, and help employees surface relevant information through conversational search. For communicators who publish regularly across a large multi-site workforce, AI-assisted creation reduces the time from information source to published intranet page. **Free version:** No **Pricing:** Enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop [Explore Unily](https://www.unily.com) ## Oak Engage Oak Engage is a UK-based social intranet built specifically to reach deskless and frontline employees without requiring corporate email or directory-based enrollment. Workers sign up via a link, QR code, or invitation on their personal device, and the mobile app gives them the same experience as desk staff from day one. Oak's "Smart Delivery" engine uses AI to target content by role, location, and team, so a warehouse operative in Manchester and a store manager in Glasgow each see the content relevant to their segment without the communications team having to create separate versions. Deployment is positioned as fast: Oak has documented launches completed within 48 hours for organizations that arrive with content and user lists ready. Published case studies include Burger King UK's frontline intranet, which reached a workforce that was "98% offline" from corporate systems, and Aldi UK, where over 50,000 warehouse and store-based colleagues were enrolled with a 95% sign-up rate. Oak suits organizations that want a social intranet with genuine frontline reach and are willing to accept a less extensible admin and design toolkit in exchange for that simplicity. Reviewers note that the mobile app formatting tools and page-styling options are less refined than those offered by larger enterprise platforms, which matters for organizations where polished branded design is a compliance or communications priority. **Best for:** Mid-to-large organizations replacing a legacy intranet or consumer messaging app for frontline staff, where fast enrollment, relevant content delivery, and genuine deskless reach are the primary criteria. **Consider alternatives if:** Your organization requires a highly customizable design system, complex multi-brand governance, or deep operational workflow integrations beyond what a communications-led intranet provides. - **No-Email Frontline Enrollment:** Workers register on a personal device via QR code, unique link, or invitation without needing a corporate email address or IT-provisioned account. For organizations with high turnover or seasonal workforce fluctuations, this reduces the account management overhead that undermines adoption in other platforms. - **Smart Delivery AI Targeting:** Oak's targeting engine serves content, navigation, and notifications based on role, location, and team membership. Combined with push notifications and mandatory acknowledgment features, this allows time-sensitive safety notices, policy updates, and operational communications to reach the right audience segment without broadcasting irrelevant information to the whole workforce. - **"Aria" AI Search and Content Creation:** Oak's native AI assistant powers search across the intranet and can assist communicators with drafting and publishing content. For small internal communications teams managing content across multiple locations, AI-assisted publishing reduces the lag between an event happening and employees being informed about it. **Free version:** No **Pricing:** Paid/Enterprise, quote-based **Platforms:** Web, iOS, Android [Explore Oak Engage](https://oak.com) ## LumApps LumApps is an enterprise intranet and employee hub that merged with frontline specialist Beekeeper in July 2025, creating a combined platform intended to serve desk and deskless workers from a single vendor relationship. The merger is significant for frontline intranet buyers because it pairs LumApps' established intranet capabilities for desk-based teams with Beekeeper's frontline-native mobile app, which supports QR code and SMS enrollment without a corporate email address, includes secure messaging with inline translation, and offers operational features including digital forms and HR self-service. LumApps has long differentiated through native support for both Microsoft 365 and Google Workspace, which is unusual in this category and relevant for large enterprises running a hybrid productivity stack. The platform also includes an AI assistant ("Companion") and an Agent Hub for governed AI across HR, IT, and operations use cases. Buyers evaluating LumApps in 2026 should ask specifically about integration timelines between the two products: as of mid-2026, the LumApps intranet and Beekeeper frontline app are still being unified under a single product, and which capabilities from each are available under a single contract varies by deal structure and timing. Forrester noted in its intranet evaluation that LumApps has drawn criticism from customers around the pace of feature rollouts and the cost of add-on modules, which is relevant context for procurement conversations. **Best for:** Large global enterprises running mixed Google and Microsoft productivity stacks that want a single vendor for both desk and frontline coverage and are comfortable with a product that is mid-integration as of 2026. **Consider alternatives if:** You need a fully unified product with verified frontline enrollment in a single interface today, or your frontline workforce represents the majority of your headcount and you cannot wait for integration work to complete. - **Google Workspace and Microsoft 365 Native Integration:** LumApps is one of the few intranet platforms with deep native integrations for both productivity stacks. Content from Google Drive and Microsoft SharePoint surfaces inside the intranet without requiring a separate connector configuration, which is relevant for multinational enterprises where different regions standardized on different tools. - **Beekeeper Frontline Mobile App:** The Beekeeper product, now part of LumApps Group, provides a mobile-first environment for frontline workers that does not require a corporate email address. It includes shift-based secure messaging, automated workflows via digital forms, and multilingual communication support through inline translation, with deployment experience in manufacturing, retail, and hospitality. - **AI Companion and Agent Hub:** LumApps includes an AI assistant for employee Q&A and content discovery, plus a governed AI agent framework for HR and IT use cases. For organizations building toward AI-assisted workflows across a mixed desk and frontline workforce, the Agent Hub is a relevant roadmap consideration alongside the current product state. **Free version:** No **Pricing:** Enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop [Explore LumApps](https://www.lumapps.com) ## Sociabble Sociabble is a communications and engagement platform that delivers a fully white-labeled iOS and Android app to frontline and office employees without requiring a corporate email address. Organizations brand the app with their own name, logo, and colors, so it appears in the app store as their own product rather than a third-party tool. The platform combines internal communications, employee engagement, and employee advocacy in a single environment, with multichannel delivery across the branded app, web, email, digital newsletter, Microsoft Teams, and SharePoint. Its standout capability for global frontline deployments is automatic multilingual translation: content published in one language is delivered to each employee in their preferred language with a single click, covering more than 60 languages. Sociabble fits large consumer-brand enterprises with distributed frontline populations where internal culture, peer recognition, and brand ambassador programs are communication priorities alongside operational updates. The platform's intranet architecture is lighter than dedicated intranet products: Sociabble does not prioritize traditional document repositories, deep page hierarchies, or structured knowledge management, and organizations that need those capabilities will find the content architecture comparatively limited. It serves its clearest use case for communication and engagement teams at enterprises where brand identity and workforce connection are the primary objectives. **Best for:** Large multilingual enterprises with a distributed frontline workforce where employee engagement, advocacy, recognition, and multichannel branded communications are the primary internal communications goals. **Consider alternatives if:** Your primary requirement is structured document management, a deep knowledge base with role-based governance, or operational workflow integrations beyond communications. - **Fully White-Labeled Branded App:** Sociabble publishes a custom-branded iOS and Android app under the organization's own name and visual identity, available for download in public app stores. For frontline-heavy consumer brands where employee experience and customer brand experience are closely linked, a branded app reinforces internal culture in a way that generic platform apps do not. - **Built-In Gamification and Employee Advocacy:** The platform includes recognition features, team challenges, and brand advocacy tools that allow frontline workers to share approved brand content to their personal networks. For consumer-facing organizations where frontline staff are the brand's most visible representatives, this advocacy layer turns internal communications into an external reach channel. - **One-Click Multilingual Translation:** Content published in any language can be automatically translated into 60+ languages at the point of delivery, with each employee receiving communications in their preferred language. For enterprises with frontline workforces spanning multiple countries and language communities, this eliminates the production bottleneck of maintaining separate content for each locale. **Free version:** No **Pricing:** Enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop [Explore Sociabble](https://www.sociabble.com) ## Interact Interact is an enterprise intranet platform designed for mid-to-large organizations where internal communications quality and knowledge discovery are the primary use cases. The platform delivers a personalized intranet experience on web and mobile with intelligent search, audience-targeted news, mandatory reads with acknowledgment tracking, and a native AI capability (Interact AI) for content drafting, summarization, and revision. Its strength is in helping communicators reach the right employee segments with the right information at the right time: administrators can create audience rules that control which news, resources, and navigation appear to each group, and mandatory read features can deliver compliance-critical content with a full audit trail across the workforce. Interact AI is built into the content editing workflow, allowing communicators to draft, rewrite, and summarize content without leaving the platform. Interact is positioned as a communications-led intranet rather than an operational platform: it covers the information and engagement layer well but does not natively include shift scheduling, task management, or safety workflow capabilities. Organizations with a predominantly frontline workforce that need these operational tools will need to run them as separate systems. Buyers should also verify the non-email enrollment path for frontline workers before shortlisting: Interact's mobile app is well-regarded, but the no-corporate-email enrollment flow should be confirmed in a live demo for deskless use cases. **Best for:** Mid-to-large enterprises that want a polished, communications-led intranet with strong knowledge management, audience targeting, and mandatory read capability, where frontline workers access the intranet as part of a mixed workforce. **Consider alternatives if:** Your workforce is predominantly frontline and you need a platform where operational tools such as scheduling, task management, and safety inspections are native rather than integrated from external systems. - **Audience-Targeted Announcements and Must-Read Content:** Interact's content targeting allows administrators to segment news and announcements by role, department, location, and other attributes, so frontline staff see only the communications relevant to their work. Mandatory read content with acknowledgment confirmation and audit trail supports compliance-sensitive communications to workers across distributed sites. - **Interact AI Content Capabilities:** The platform's built-in AI can draft news articles and announcements from a brief, suggest rewrites, and summarize long-form content for quicker consumption. For internal communications teams managing high-volume content calendars across a large, distributed organization, AI-assisted editing reduces production time without requiring a separate tool. - **Intelligent Search and Personalized Dashboard:** Interact's search layer indexes content across the intranet and applies personalization to surface the most relevant results for each user's role and context. For frontline workers who need to locate a policy, procedure, or resource quickly between tasks, accurate search is a more reliable path than manual navigation through page hierarchies. **Free version:** No **Pricing:** Enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop [Explore Interact](https://www.interactsoftware.com) ## Appspace Appspace is a workplace experience platform that combines an intranet, a mobile employee app, and digital signage under a single vendor relationship. The digital signage capability is what distinguishes it from every other platform on this list: Appspace can deliver content to screens in factory floors, warehouse break rooms, retail back-of-house areas, and other physical spaces where workers may not carry a smartphone or check a mobile app during their shift. In September 2025, Appspace acquired Igloo Software, adding a mature modern intranet product and approximately 325 customers to its portfolio. The combined offer covers intranet, mobile app, and signage in one contract. Igloo's "Flex" module provided task-based mobile experiences for frontline workers without requiring a corporate email address, and Appspace is absorbing this capability into its platform. Buyers evaluating Appspace in 2026 should verify exactly which Igloo capabilities are available under the current Appspace product and confirm that migration from an Igloo contract to an Appspace contract does not introduce disruption. Existing Igloo customers considering renewal should ask specific questions about product roadmap, support continuity, and which features are moving to the unified Appspace platform versus being retired. The digital signage capability is the clearest reason to evaluate Appspace over intranet-only platforms for manufacturing, retail, and hospitality organizations. **Best for:** Multi-site employers in manufacturing, retail, or hospitality where digital signage screens in physical spaces are a necessary reach channel for workers who are not reliably on their phones during shifts. **Consider alternatives if:** You are an existing Igloo customer concerned about migration risk, or you want a single mature and fully integrated product rather than a portfolio that is actively consolidating two acquisitions. - **Intranet + Mobile App + Digital Signage on One Platform:** Appspace delivers content to employee smartphones, desktop browsers, and physical signage screens from a single content management environment. For plant floor supervisors or warehouse managers who need to reach workers on screens above assembly lines or in break rooms, this removes the need to manage a separate digital signage system alongside the intranet. - **Igloo Flex Frontline Workplace Module:** Igloo's Flex product, now part of the Appspace portfolio, was built for task-based frontline mobile experiences in manufacturing, retail, and distribution, with no corporate email required for enrollment. The module focused on structured task completion, safety checklists, and information access in high-noise or low-connectivity environments. - **Multi-Site Content Targeting:** Appspace supports location-based and audience-based content targeting across both the mobile app and signage channels, allowing site managers to push content specific to their facility without requiring central communications team involvement for every update. **Free version:** No **Pricing:** Enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop, Digital signage [Explore Appspace](https://www.appspace.com) --- ## theEMPLOYEEapp theEMPLOYEEapp (rebranding to EngagedlyFX as of 2025, so buyers may encounter both names) is a mobile-first platform built specifically for frontline and deskless workers who have no company email address and no regular access to a shared workstation. The product combines an internal communications mobile app, an intranet and knowledge hub, and SMS messaging in one suite, so organizations can reach workers through the app for those who have downloaded it and via SMS for those who haven't. Workers enroll on a personal device using an employee ID, QR code, or invitation link without needing an IT-provisioned account. The platform supports compliance course delivery and a mobile knowledge hub for standard operating procedures, safety documentation, and training materials alongside the communications layer. Pricing is structured on a per-user, per-month basis and is among the more transparent in a category where most vendors require a custom quote before disclosing costs, making it accessible for organizations that need to build a business case before engaging enterprise sales. The scope is intentionally focused: theEMPLOYEEapp covers communications, knowledge access, and training delivery well but does not offer the operational workflow depth of platforms that also handle scheduling, task management, or safety inspections. Organizations that will need those capabilities alongside the intranet should factor in the cost and complexity of integrating a separate operational tool. **Best for:** Frontline-heavy organizations with 100 to 10,000 employees that want a straightforward, affordable mobile-first communications and knowledge platform with no-email enrollment and transparent per-user pricing. **Consider alternatives if:** You need deep structured intranet architecture, complex document governance, a large catalog of enterprise integrations, or operational workflow capabilities native to the same platform. - **No Corporate Email, Multi-Channel Reach:** Workers register using an employee ID, QR code, or invitation on a personal device. For organizations that also need to reach workers without smartphones, the built-in SMS channel sends critical updates as text messages to any phone, covering the segment of the frontline workforce that the app alone cannot reach. - **Mobile Knowledge Hub and Compliance Training:** Alongside the communications feed, theEMPLOYEEapp includes a searchable knowledge repository for SOPs, safety documents, and policy references, plus a course delivery module for required compliance training. Workers can complete assigned training modules and access updated procedures from the same app they use for daily communications. - **Engagement Analytics for Communicators:** The platform tracks content views, open rates, and completion rates across the workforce and surfaces these in an analytics dashboard. For communications teams that need to demonstrate reach and readership to leadership, particularly for compliance-critical content, this provides an audit-grade record of who received and engaged with each piece of content. **Free version:** No **Pricing:** Per user/month, billed annually; contact for current pricing **Platforms:** Web (admin), iOS, Android [Explore theEMPLOYEEapp](https://theemployeeapp.com) ## Haystack Haystack is a modern intranet platform that centers on AI-powered universal search as its primary differentiator, delivered through a fast-to-deploy product with native iOS and Android apps that can be fully branded to the organization's visual identity. The search layer federates across connected systems, including Google Workspace, Microsoft 365, and HR platforms, so employees can surface a policy document, an org chart entry, or a project file from a single search bar regardless of where the content lives. For frontline buyers, Haystack markets a dedicated capability set that includes mobile-first access, mandatory read documentation with audit trail, watermarked secure document delivery, and QR or SMS-based onboarding. The platform is positioned at mid-market to enterprise organizations and has published customer examples across technology, media, and consumer sectors. Reviewers note that deep document governance and complex permission structures are weaker areas compared to platforms designed around large-scale compliance workflows. Haystack fits organizations where fast deployment, high search quality, and a consumer-grade mobile experience are the primary criteria, and where the intranet's primary function is information access rather than operational execution. Organizations with complex compliance requirements, extensive document governance needs, or large-scale safety and task management use cases will typically need to supplement Haystack with additional tooling. **Best for:** Mid-market organizations that want a fast-to-deploy, search-led intranet with a consumer-grade mobile feel and are prioritizing information access and adoption speed over deep governance or operational workflow capabilities. **Consider alternatives if:** Your deployment requires complex document permissions, large-scale compliance audit trails, or native operational tools such as scheduling, task management, or safety inspections. - **AI-Powered Universal Search:** Haystack's search layer indexes content across the intranet and connected applications, including Google Workspace and Microsoft 365, so employees find what they need from one search bar rather than navigating between systems. For frontline workers who need a procedure or resource quickly during a task, fast and accurate search is often the single feature that determines whether the intranet becomes part of the daily routine. - **Custom-Branded Native Mobile Apps:** Organizations can publish the Haystack intranet as a fully branded native app on iOS and Android, with the organization's name, logo, and color palette appearing throughout. Frontline workers download a familiar-looking app that feels like an in-house product rather than an enterprise software tool, which lowers the psychological barrier to initial adoption. - **Mandatory Reads with Secure Document Controls:** Haystack includes a mandatory read feature with confirmation tracking and an audit trail for compliance-sensitive communications. The platform also supports watermarked document delivery and copy/paste restrictions for confidential materials, which is relevant for organizations in regulated industries that need to control how sensitive policy documents are handled on personal devices. **Free version:** No **Pricing:** Paid/Enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop [Explore Haystack](https://www.haystackteam.com) ## How Each Platform Compares on Frontline Readiness The following table evaluates all ten platforms on the four criteria that determine whether a frontline intranet actually works: whether workers can get in without a corporate email, whether the communication flows both ways, whether the right content reaches the right people with compliance coverage, and whether the platform connects to the operational systems frontline workers use every day. Platform No-Email Enrollment Two-Way Frontline Engagement Targeted Content and Mandatory Reads Operational Integration Depth MangoApps Yes: QR code, SMS, and employee ID enrollment via OneMango; no corporate email or VPN required at any workforce size Yes: frontline workers post, react, comment, and message in the same app they receive broadcasts; two-way communication is architectural, not a configuration option Yes: role- and location-based audience targeting with confirm-read capability, delivery receipts, and full audit trail available on every content type Yes: 200+ native integrations covering HRIS, scheduling, task management, payroll, and safety; operational workflows run inside the same platform, not alongside it Microsoft Viva Connections Conditional: requires a Microsoft Entra ID for every worker; Frontline F-SKU reduces license cost but IT must provision accounts before deskless workers can enroll Limited: Viva Engage supports reactions and comments on news; direct frontline-to-management messaging routes through Teams and requires configuration to surface on the Viva Connections home Yes: audience targeting on Dashboard cards and SharePoint news pages; required-reading features available through SharePoint page configuration rather than a native workflow Yes: Adaptive Card Extensions pull live data from Kronos, ADP, Workday, and other systems; the broadest integration ecosystem in the category for organizations already standardized on M365 Unily Conditional: branded mobile app supports frontline enrollment; verify the non-directory enrollment path for workers without corporate email before shortlisting Yes: reactions, comments, and social features available on mobile; frontline workers can acknowledge and respond to content through the app Yes: limitless audience builder governs content, navigation, and search visibility simultaneously; mandatory read and confirm-read features available across content types Yes: integration execution layer connects shift swap, leave requests, and payslip access through HRIS and workforce management APIs; API-first architecture for custom connectors Oak Engage Yes: frontline workers enroll via QR code, unique link, or personal device without a corporate email address or IT-provisioned account Yes: workers post, comment, and react through the same app interface as desk staff; peer-to-peer and upward communication are both supported Yes: Smart Delivery AI targets content by role and location; mandatory acknowledgment features available for compliance-critical communications Moderate: HRIS integration for profile data; shift rota and payslip access built into the mobile app; fewer enterprise operational system integrations than larger platforms LumApps Yes (via Beekeeper): Beekeeper-side enrollment supports QR code and SMS for deskless workers without corporate email; LumApps intranet side still requires directory identity as of mid-2026 Yes (via Beekeeper): secure messaging with inline translation and reactions on the Beekeeper side; LumApps intranet supports standard social engagement features for desk staff Yes: content targeting and mandatory reads available across both products; unified targeting controls were still being integrated across the combined platform as of mid-2026 Yes: LumApps integrates with M365, Google Workspace, Workday, SAP, and ServiceNow; Beekeeper adds digital forms and HR self-service for frontline operational workflows Sociabble Yes: white-labeled iOS/Android app reaches workers without corporate email; enrollment via app store download with employee access code Yes: comments, reactions, recognition, and brand advocacy sharing; gamified team challenges encourage two-way engagement across frontline teams Yes: multichannel delivery with audience targeting and one-click 60+ language translation; confirm-read and mandatory content features available Moderate: integrates with HRIS for profile sync and SSO; primary focus is communications and engagement, not operational workflow execution or task management Interact Conditional: mobile app available; verify non-email enrollment path for deskless workers before shortlisting, as standard deployments assume directory identity Yes: comments, reactions, and employee voice features across the intranet; two-way communications supported on mobile and desktop Yes: audience-targeted announcements and must-read mandatory content with acknowledgment confirmation and audit trail; one of the stronger implementations in the category Moderate: integrates with HRIS and directory services; operational workflow integration requires API configuration; not a native ops platform Appspace Conditional (via Igloo Flex): Igloo Flex supported no-email frontline enrollment; verify current availability and enrollment path under the post-acquisition Appspace product before committing Moderate: content displays on signage and the mobile app; digital signage is one-way by design; mobile app supports basic engagement features Yes: content targeting by location and role across both mobile and signage channels; mandatory reads available on the intranet and mobile app layer Moderate: integrates with scheduling and HR systems; the digital signage channel is the primary differentiated operational capability for on-site frontline environments theEMPLOYEEapp Yes: no corporate email required; workers enroll via employee ID, QR code, or SMS on a personal device; SMS channel reaches workers without smartphones Yes: chat, comments, reactions, and group messaging; frontline workers can initiate conversations as well as receive broadcasts Yes: role-based content targeting; confirm-read tracking and compliance course delivery included in the core platform Moderate: integrates with HRIS for profile data; SMS reach extends beyond smartphone users; primary scope is communications and training, not scheduling or task management Haystack Conditional: QR and SMS frontline onboarding marketed; verify no-email enrollment path in a live demo before including in a deskless-majority shortlist Yes: comments, reactions, and social engagement features across intranet content; standard two-way engagement for a communications-led platform Yes: mandatory reads with audit trail and watermarked secure document delivery; content targeting by role and team available Moderate: universal/AI search federates across connected systems; primary operational value is knowledge access and findability rather than workflow execution *Capability statements for third-party vendors are taken from each vendor's public documentation and are vendor-stated, not independently verified by MangoApps.* The table surfaces a clear split. Platforms built natively for frontline workers (MangoApps, Oak Engage, theEMPLOYEEapp, and Beekeeper within LumApps) score consistently on the first two criteria: enrollment without a corporate email, and genuine two-way engagement from frontline workers. Office-first intranets adapted for frontline use (Viva Connections, Unily, and Interact) score well on targeting, mandatory reads, and operational integration depth, but carry a conditional flag on no-email enrollment that should be tested in a demo before a decision. MangoApps is the only platform on this list that scores without a conditional flag across all four criteria. The trade-off every buyer is navigating: purpose-built frontline platforms offer simpler reach to deskless workers from day one, while office-first enterprise platforms offer broader operational integration for organizations where desk-based employees are also a significant audience. ## How to Choose: Matching Your Situation to the Right Platform **You are already on Microsoft 365 and want to extend your intranet to frontline workers without adding a separate tool.** Start with Viva Connections using Frontline F-SKU licensing. It reuses your existing SharePoint content, Teams infrastructure, and identity management. If the Microsoft account provisioning overhead for high-turnover frontline populations becomes a barrier, or if your frontline user experience requires a more consumer-grade mobile app than Teams currently delivers, evaluate MangoApps as a complement or replacement that coexists with your M365 stack. **A large share of your workforce has no company email address, no shared workstation, and no time to log in during a shift.** The no-email enrollment requirement is non-negotiable for this profile. MangoApps, Oak Engage, theEMPLOYEEapp, and LumApps (via the Beekeeper product) all support QR code, SMS, or employee ID enrollment on personal devices. Run the enrollment test as the first item in any demo: if the vendor starts a product demonstration on a desktop browser without showing the frontline enrollment flow, ask to see it before proceeding. **You need one platform to serve desk employees, frontline workers, and managers across multiple countries, with no separate system for either group.** MangoApps, Unily, and LumApps are the primary candidates. MangoApps extends further into operations: scheduling, tasks, and safety management, without requiring a second tool. Unily fits organizations where a premium, heavily branded intranet experience for a large white-collar workforce is a stated requirement and frontline is an important but secondary audience. LumApps covers organizations running both Google Workspace and Microsoft 365, which is a genuine capability gap the other two do not address. **Your frontline workforce spans multiple languages and countries, and multilingual communications quality is a make-or-break requirement.** MangoApps, Sociabble, and LumApps have the deepest multilingual capabilities. Sociabble's one-click translation across 60+ languages and its employee advocacy framework are distinctive for large consumer-brand enterprises where frontline staff are the face of the brand in local markets. MangoApps supports 50+ languages with automatic translation baked into the OneMango app. **You operate manufacturing, warehouse, or back-of-house environments where workers are not reliably on their phones during shifts, and you need screens in physical spaces to reach them.** Appspace is the only platform on this list with integrated digital signage alongside a mobile app and intranet. If digital screens in high-traffic physical areas are part of your communications strategy, Appspace removes the need to manage a separate signage system. For organizations that need both a frontline intranet and physical signage, the consolidated vendor relationship is the primary reason to evaluate it. **You are a mid-market organization with fewer than 5,000 employees, need to move fast, and cannot spend 12 months on implementation.** MangoApps' Adoption Guarantee structures deployment accountability directly into the contract. Oak Engage and theEMPLOYEEapp both offer straightforward deployments for frontline-heavy organizations and publish transparent deployment timelines. Haystack is worth considering if AI-powered search and a consumer-grade mobile experience are the defining requirements and deep operational tooling is not. ## What Is a Frontline Intranet? A frontline intranet is a platform designed to give deskless and shift-based employees the same access to company information, communications, and resources that office-based employees receive through a standard corporate intranet. The defining architectural difference is enrollment: a standard corporate intranet assumes every worker has a company email address, a directory identity, and a device connected to the corporate network. A frontline intranet is built around a different assumption: that most workers carry a personal phone, have no company email, and may work irregular hours with limited time between tasks. In practice, this means frontline intranets prioritize QR code, SMS, or employee ID enrollment over directory-based login; mobile-native experiences over responsive desktop sites; offline access for low-connectivity environments; push notifications over email alerts; and content that can be targeted by role, location, and shift without requiring the worker to navigate a page hierarchy. The line between a "frontline intranet" and an "employee communications app" has narrowed considerably in recent years, as traditional intranet vendors have added mobile apps and frontline communication vendors have added structured content, knowledge management, and search. The 2025 merger of LumApps and Beekeeper is the clearest market signal of this convergence: the intranet and the frontline app are increasingly one product. ## Why Traditional Intranets Fail Frontline Workers The failure mode is structural, not a matter of effort. Traditional intranets were built around a model in which every employee has a corporate email address that serves as their identity, a desk-based computer as their primary access device, and a VPN or corporate network for connectivity. Frontline workers typically have none of these three things, which means they are excluded from the platform before it launches, not because the rollout was poorly managed, but because the architecture never accounted for them. According to Gallup's research on employee engagement, workers who feel disconnected from company communications are among the least engaged segments of the global workforce, and low engagement correlates directly with higher turnover rates, a cycle that is particularly costly in industries like retail, healthcare, and manufacturing where frontline labor is the primary operational resource. Beyond the enrollment barrier, even frontline workers who do gain access to a traditional intranet encounter a second failure: content that was created for HQ employees and delivered without targeting. A store associate in a regional market does not need the same information as a finance analyst at headquarters, and an intranet that sends both the same homepage is one the store associate learns to ignore. Poor mobile load times, weak search, and stale content complete the picture. Industry benchmarks suggest traditional intranet deployments see 30-40% active adoption rates on average. Frontline-native platforms that address these structural barriers from the start consistently outperform that baseline, with MangoApps documenting 90%+ adoption within 90 days under its written guarantee. ## What Features Should a Frontline Intranet Have? Not every intranet feature matters equally for a frontline audience. The following six capabilities are the ones that determine whether a frontline deployment achieves adoption or becomes another system employees ignore. **No-email enrollment.** Workers should be able to register and log in using a QR code, SMS invite, or employee ID on a personal device. Any enrollment flow that requires a company email address or IT-provisioned account creates a setup dependency that adds lead time and generates ongoing overhead for every new hire. **Push notifications with shift-aware controls.** Frontline workers are most reachable during breaks and at shift start. Notifications sent during working hours in environments where personal phones are restricted will be ignored or create compliance issues. Platforms that support notification scheduling by role or shift reduce this tension. **Mandatory reads with audit trail.** Safety briefings, policy updates, and compliance-critical communications need to reach specific employee segments with confirmation that each worker has seen the content. An audit trail is the evidence layer that supports regulatory compliance and liability management. **AI-powered mobile search.** Employees spend just under six minutes a day on their intranet, according to [SWOOP Analytics' 2025 benchmarking report](https://www.swoopanalytics.com/sharepoint-bm-25), and [Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) sets a 75% minimum search-success benchmark; when the first search fails, people ask a manager instead. For a frontline worker with 30 seconds between tasks, that search window is even shorter. AI-powered search that surfaces the right document, policy, or contact in two taps is the feature that converts initial logins into daily habit. **Role and location content targeting.** Content published to the entire workforce from a central intranet is one of the primary reasons frontline workers stop visiting. When a store in one region sees safety updates relevant to their location and a warehouse team sees operational updates relevant to their site, the intranet starts to feel useful rather than noisy. **Integrations with operational systems.** An intranet that exists in isolation from shift scheduling, HR, and task management requires workers to maintain a separate mental model for each tool. Platforms that connect these systems give a worker one place to see their schedule, check a policy, and acknowledge a safety notice, which supports higher adoption because it reduces the number of separate places a worker has to go. ## How to Choose the Right Intranet for Your Frontline Team For the platform-level view, including how intranet, scheduling, tasks, training, and HR fit together for frontline teams, see [The Complete Guide to Frontline Communication Platforms](https://www.mangoapps.com/articles/frontline-communication-platforms-guide) and [How to Increase Frontline Intranet Adoption Without Sacrificing Governance or Compliance](https://www.mangoapps.com/articles/frontline-intranet-adoption-governance-compliance). For a governance-first ranking of ten platforms for global enterprises, see [The 10 Best Employee Intranet Platforms for Governance, Compliance, and Global Workforce Communication](https://www.mangoapps.com/articles/best-intranet-platforms-governance-compliance-global). Start with a workforce composition audit before evaluating any vendor. What percentage of your employees lack a corporate email address? What percentage primarily work on a personal mobile device? What percentage work in environments where personal phone use during shifts is restricted? These questions determine which platforms belong on your shortlist and which ones should be disqualified before a demo begins. For any organization where more than 30% of employees have no corporate email, no-email enrollment should be treated as a non-negotiable, not a nice-to-have. Run four tests in every demo before making a shortlist decision: first, enroll a test account using QR code or SMS without any IT-provisioned credentials; second, send a mandatory read with a confirm-read requirement and verify the audit trail; third, run an AI search for a common frontline query on the mobile app and measure the time from launch to result; fourth, access a document in offline mode with no active network connection. If a vendor declines to demonstrate any of these four in a live session, treat the omission as meaningful. Evaluate total cost of ownership rather than headline per-user pricing: implementation timelines, change management support, ongoing admin overhead, and the cost of supplemental tools for capabilities the intranet does not natively cover all affect the real investment. MangoApps is worth evaluating for frontline-heavy organizations in retail, healthcare, manufacturing, and hospitality that want a single platform covering intranet, communications, and operations, backed by a written [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee). ## Frequently Asked Questions **Can frontline workers use an intranet without a corporate email address?** Yes, but only on platforms designed for it. Platforms like MangoApps, Oak Engage, theEMPLOYEEapp, and the Beekeeper side of LumApps support QR code, SMS, or employee ID enrollment on personal devices with no corporate email required. Traditional intranet platforms (including SharePoint) and most office-first vendors require a directory identity, which means IT must provision an account before a worker can enroll. For high-turnover frontline environments, the provisioning overhead of directory-based enrollment is a significant operational cost. **What is the difference between a frontline intranet and a standard corporate intranet?** A standard corporate intranet assumes every worker has a company email address, a desktop computer, and access to the corporate network. A frontline intranet is built around workers who have none of those three things. The practical differences show up in how workers enroll (QR code vs. email activation), how they access the platform (personal smartphone vs. corporate device), and how content reaches them (push notification vs. email digest). Many platforms now market themselves as serving both audiences, but the architectural starting point still determines how well each group is served. **What features does an intranet for deskless workers need?** The six most important capabilities for a frontline-specific intranet are: no-email enrollment, push notifications with shift-aware delivery controls, mandatory reads with an audit trail, AI-powered mobile search, role and location-based content targeting, and integrations with scheduling, HR, and task management tools. Generic intranet features like desktop wikis and meeting integrations are less important for an audience that is rarely at a desk. **How much does frontline intranet software cost?** Most enterprise frontline intranet platforms are quote-based, with pricing that varies by employee count, modules selected, and implementation scope. MangoApps publishes a starting price of approximately $19 per seat per month for smaller organizations and is one of the few vendors with transparent per-user pricing. Microsoft Viva Connections is included with existing Microsoft 365 licensing; Frontline F-SKU licenses start at approximately $2.25 per user per month. All other platforms on this list require a direct sales conversation before pricing is available. Budget for implementation costs alongside license fees: large multi-site deployments typically involve configuration, data migration, change management, and training that add to the total investment. **Is SharePoint a good intranet for frontline workers?** SharePoint via Viva Connections works for frontline workers who already have a Microsoft identity and a Teams-enabled device. For organizations standardized on Microsoft 365, it is a cost-effective starting point because it reuses existing infrastructure and licensing. It is a poor fit for organizations with large populations of workers who lack a Microsoft account, because every such worker requires IT to provision an account before they can enroll, and that overhead compounds quickly in high-turnover environments. The configuration required to deliver a consistent frontline experience through Viva Connections is also more substantial than what purpose-built frontline platforms require out of the box. **What is the difference between an intranet and an employee communications app?** Historically, an intranet was a structured content repository with pages, departments, and document management, while an employee communications app was a mobile channel for real-time messaging and updates. That distinction has largely collapsed. Leading frontline intranet platforms now include both structured content and real-time communications in a single product, and the 2025 LumApps-Beekeeper merger is the most visible signal that the market treats these as one category. The useful question for buyers is not which category a platform belongs to, but whether it covers the specific capabilities their workforce needs. **How do you get frontline workers to actually adopt an intranet?** Adoption depends on three conditions at launch: the enrollment flow requires no friction (no corporate email, no IT ticket, no password reset), the content on day one is personally relevant to the worker's role and location, and a peer champion or manager at each site models daily use. Platforms that require IT involvement to enroll each employee consistently see lower frontline adoption because the bottleneck is at the enrollment step rather than in the product. After launch, the factor that sustains adoption is whether the intranet saves workers time or provides information they actually need. Schedules, safety updates, shift changes, and local news are the content types that generate return visits from frontline employees; corporate announcements and HQ news are the content types that cause them to stop opening the app. **Which industries benefit most from a frontline intranet?** Retail, healthcare, manufacturing, hospitality, and logistics see the highest return from a frontline intranet because they combine three factors: large deskless workforces who receive no communications through traditional channels, high-stakes operational and safety communications that cannot rely on cascaded word of mouth, and elevated turnover costs that improve when workers feel informed and connected. For regulated industries such as healthcare and food manufacturing, the mandatory read and audit trail capabilities of a frontline intranet also support compliance documentation requirements. **How long does it take to deploy an intranet for frontline teams?** Deployment timelines vary significantly by platform and scope. Oak Engage has documented deployments completed in 48 hours for organizations that arrive with user lists and content ready. MangoApps structures deployment accountability into its contract through a written 90-day adoption guarantee. Full-featured enterprise implementations, particularly those involving HRIS integrations, multi-brand deployments, or custom branding at scale, typically run three to six months. Office-first platforms adapted for frontline use, including SharePoint and Unily, require more configuration to deliver a consistent frontline experience and tend toward longer timelines. **How do you communicate with employees who don't have smartphones?** Three channels cover this gap. Digital signage screens in break rooms, factory floors, and back-of-house areas reach workers during natural pause points in their shift without requiring them to carry or check a device. Appspace is the platform on this list specifically designed for this use case. SMS messaging reaches any mobile phone regardless of whether the user has downloaded an app, and platforms including theEMPLOYEEapp and MangoApps support SMS as a delivery channel alongside the mobile app. Shared-device kiosk access allows workers to log in on a tablet or touchscreen terminal at their site, though this introduces the queuing and privacy issues that make it a secondary option for most organizations. --- # Frontline Workforce Compliance: Building the Audit Trail **Author:** MangoApps Team **Published:** 2026-06-21 **Category:** safety-compliance An OSHA inspector calls. A class-action attorney sends a letter. # Frontline Workforce Compliance: Building the Audit Trail An OSHA inspector calls. A class-action attorney sends a letter. An insurance carrier requests documentation before renewing a policy. These moments don't announce themselves in advance, and when they arrive, the question is always the same: can you prove what you say you do? For many organizations, the honest answer is: not easily. Policies exist. Training happens. Safety check-ins occur. Inspections get completed. But the documentation — when it exists at all — lives in three different systems, two shared drives, and a stack of paper forms that someone scanned months ago and may or may not be findable. The gap isn't between good intentions and bad ones. It's between work that gets done and work that gets documented in a way that holds up. This week, a cluster of MangoApps releases addressed that gap. Not through a single compliance suite, but through specific, targeted changes across onboarding, inspections, and worker safety — each one closing a place where operational evidence was previously incomplete or unreliable. --- ## Onboarding: When HR Says "We Onboarded Them," Proving It Is a Separate Problem New hire onboarding creates more compliance exposure than most HR teams fully reckon with. Every form signed, every policy acknowledged, every document filed has potential legal and regulatory weight — and in a dispute, the burden of proof falls on the employer. Completion rates don't satisfy an I-9 audit or an employment dispute. A timestamped, structured record does. The [Onboarding Hub's new Compliance Audit Report](https://www.mangoapps.com/changelog/3027) addresses this directly. It generates a point-in-time audit trail covering every form, document, e-signature, and filing in an onboarding plan, exportable as PDF or CSV for legal review. This isn't a report about how many employees finished onboarding — it's a legal-grade record that a specific employee completed specific steps at specific times, surfaced when you need it rather than reconstructed from scattered logs. Alongside that, [field-level review](https://www.mangoapps.com/changelog/3025) gives reviewers the ability to return individual form fields for correction rather than rejecting an entire submission. That granularity matters for compliance: it creates a cleaner record of what was reviewed, what was flagged, and what was corrected. The same release added automatic detection of conflicting identity data across onboarding forms — the kind of discrepancy that surfaces as a problem in I-9 audits or background check reconciliations if it isn't caught before the hire's first day. For distributed workforces where new hires don't have desk access on day one, [mobile-optimized onboarding pages](https://www.mangoapps.com/changelog/3026) mean employees can complete enrollment steps and review checkpoints from any mobile browser. That removes one of the most common reasons forms get skipped or delayed — which is also one of the most common reasons compliance records end up incomplete. These aren't features that speed up onboarding. They're features that make onboarding defensible. --- ## Inspections: From Filed and Forgotten to Evidence on Record Workplace inspections — safety walkthroughs, quality audits, regulatory visits — are supposed to generate a paper trail that organizations can rely on when something goes wrong. The problem is that the paper trail often isn't complete, or isn't in a form that's usable when the moment of need arrives. Two releases this week improved the evidentiary quality of inspection records. First: [signatures and photos now render directly in PDF exports and on-screen reports](https://www.mangoapps.com/changelog/3028). Previously, per-item evidence collected in the field was captured but not included in the exported record — it was silently dropped. That's a meaningful gap when a regulator asks whether a hazard was photographically documented at a specific location, and the only available report doesn't show it. Second, for organizations dealing with external agency inspections, [AI now processes uploaded agency reports and fills the visit log automatically](https://www.mangoapps.com/changelog/3025), with proposed findings surfaced for review before anything is committed. This addresses a real operational problem: agency inspections generate external paperwork that needs to be reconciled with internal records, and the manual re-entry burden is high enough that it often doesn't happen — leaving a gap between what regulators documented and what the organization's own system shows. Historical bulk import for past reports helps teams that are trying to build a complete retrospective record rather than starting from scratch. The [AI visit category classification](https://www.mangoapps.com/changelog/3026) release fills in the structure side: entries get automatically classified against admin-defined categories during entry or import, which is necessary if the inspection record is going to be useful for trend analysis, pattern detection, or reporting to leadership. The common thread: inspection data has value only if it's complete, findable, and structured enough to be queried. Captured evidence that doesn't appear in reports, and agency findings that never make it into the system, are liabilities dressed as process. --- ## Lone Worker Safety: When Check-In Logs Become Life Safety Documentation Lone worker safety programs carry a particularly high compliance bar. When a worker is injured or fails to respond to a check-in, the question regulators and insurers ask isn't whether the organization had a safety policy — it's whether the response was appropriate and whether the documentation supports that claim. That requires a record of what happened, in what sequence, and who was notified. The [Lone Worker Safety Monitoring app](https://www.mangoapps.com/changelog/3026) is built around that documentation need. Workers check in on a configurable schedule; missed check-ins trigger automatic alerts to defined responder rosters. An AI-powered safety agent monitors activity and can escalate based on patterns. What distinguishes this from a general alerting tool is the emphasis on the escalation record. Configurable responder rosters mean there is a defined, documented chain of who receives an alert and in what order — not an informal understanding that "someone will notice." That structure is exactly what a workers' compensation investigation, an OSHA audit, or a liability proceeding needs to see. Not just that a worker missed a check-in, but that a specific escalation path activated within a specific timeframe. For industries where lone worker incidents generate regulatory scrutiny — construction, oil and gas, healthcare facilities, overnight security — the difference between having a safety program and being able to demonstrate it is often the difference between a defensible position and a costly one. --- ## The Pattern Behind the Releases None of this week's releases happened in isolation. What they share is a recognition that operational compliance doesn't live in a separate compliance system — it has to exist inside the workflows where the actual work gets done. The pattern across this week: capture evidence at the point of activity (inspection photos at the site, onboarding signatures in the enrollment flow, check-in timestamps from the field), structure it so it can be queried and exported (audit reports, visit logs, responder rosters), and close the gaps where documentation was falling through (AI-assisted log entry, automatic identity conflict detection, mobile-first access for employees without desk access). For HR and operations leaders managing frontline workforces, the stakes on this are real. A single gap in an onboarding record can complicate an employment dispute. An incomplete inspection log can shift liability in a safety incident. A lone worker program without a documented escalation chain is difficult to defend when regulators ask for specifics. Building the evidence layer isn't the most visible kind of work. The absence of a compliance problem rarely generates recognition the way a new feature does. But it's the kind of infrastructure that matters most when it matters — and the organizations that have it in place before they need it are the ones that aren't scrambling to reconstruct records after the fact. --- # MangoApps Earns Workday Design Badge to Bring HR Data Directly to Frontline and Desk Employees **Author:** Andy Tolton **Published:** 2026-06-17 **Category:** integrated-digital-workplace MangoApps Workday Widgets now live in the Workday Marketplace, giving employees access to benefits, pay, learning, and time-off management without leaving their daily work hub SEATTLE, Wash., June 17, 2026 - MangoApps, the AI-Ready Employee Platform for the Frontline, today announced it has earned Workday Design Approved status and is now listed on the Workday Marketplace. The MangoApps Workday Widgets bring employee benefits, paychecks, learning assignments, and time-off management directly into the MangoApps platform, so employees can access and act on their Workday HR data without switching systems. For organizations running Workday alongside MangoApps, this integration eliminates a persistent friction point: employees, particularly frontline workers, having to navigate multiple systems to complete routine HR tasks. With MangoApps Workday Widgets, that data surfaces inside the app employees already use every day to communicate, collaborate, and execute their work. "The Workday Design Badge represents a meaningful validation of our integration approach," said Vishwa Malhotra, CTO and Co-founder of MangoApps. "Our customers chose MangoApps because they want one platform their employees will actually use. Pulling Workday HR data directly into that experience means fewer context switches, less friction for managers and employees, and more of the workforce staying connected to information that matters to their day-to-day." ## What the Integration Delivers The MangoApps Workday Widgets surface four core Workday HR capabilities inside the MangoApps platform: - **Benefits access:** Employees can view and reference benefit information without leaving MangoApps - **Paycheck visibility:** Pay data surfaces directly in the employee's daily workflow - **Learning assignments:** Workday learning tasks appear alongside the rest of an employee's work - **Time-off management:** Employees can view and manage time-off requests from within MangoApps This matters especially for frontline workers who may not have ready access to a desktop HR portal during a shift. Bringing these capabilities into the mobile-first MangoApps experience means the same employee who gets a shift update, reads a company announcement, or completes a safety checklist in MangoApps can also check a paycheck or submit a time-off request in the same session. ## Workday Design Badge The Workday Design Approved badge indicates that an integration has met Workday's standards for technical design, data handling, and user experience. It is a formal certification process, not a self-reported partnership designation, and requires documented technical validation before a solution can be listed in the Workday Marketplace. The MangoApps listing is available now on the [Workday Marketplace](https://marketplace.workday.com/en-US/apps/822947/mangoapps-workday-widgets). Learn more about MangoApps integration with Workday at [www.mangoapps.com/integrations/workday](https://www.mangoapps.com/integrations/workday). **About MangoApps** MangoApps is the AI-Ready Employee Platform for the Frontline. Built for enterprises with large frontline and distributed workforces, MangoApps brings together Employee Experience, Frontline Operations, and People Operations on a single platform under one identity, one data model, and one AI foundation. Trusted by more than 2 million users at leading organizations around the world, MangoApps keeps business-critical work moving every day. For more information, visit [www.mangoapps.com](https://www.mangoapps.com). --- # 7 Ways Digital Workplace Platforms Help Frontline Staff **Author:** Andy Tolton **Published:** 2026-06-15 **Category:** integrated-digital-workplace Learn seven ways digital workplace platforms reach frontline staff, improve communication, and make knowledge accessible on mobile. Most enterprise software was built for someone sitting at a desk with a laptop, a corporate email address, and time to log into a portal. That describes almost none of the people stocking shelves, running a hospital unit, working a manufacturing line, or driving to a job site. For frontline staff, the tools their company bought to keep everyone informed and connected often never reach them at all. Digital workplace platforms close that gap. This article explains what they are and the seven specific ways they help frontline staff, from reaching workers who don't have email to making company knowledge findable in seconds on a phone. If you want a broader playbook for the problem itself, see our guide to [improving frontline communication in 2026](https://www.mangoapps.com/articles/how-to-improve-frontline-communication-2026). ## What is a digital workplace platform? A digital workplace platform is a single, connected system that brings communication, knowledge, collaboration, and day-to-day work into one mobile-first experience for every employee, including frontline and deskless staff who do not have a corporate email address or a company laptop. Instead of stitching together a separate intranet, messaging app, scheduling tool, and document library, a digital workplace platform delivers those capabilities through one app employees open on the phone they already carry. The distinction that matters for frontline teams is reach. Traditional workplace technology assumes a desk and an inbox. A digital workplace platform assumes a phone and a shift. That single design choice is why these platforms succeed with frontline staff where intranets and email have failed for two decades. ### Key takeaways - Frontline staff are often unreachable by email: a large share of frontline and deskless workers have no corporate email or rarely check it. Digital workplace platforms reach them through a mobile app instead. - The biggest wins are consolidation and reach. One connected experience replaces fragmented phone trees, paper notices, and four or five disconnected apps. - The seven ways covered below: reaching staff without email, mobile-first access, a single source of truth for updates, fast AI-powered knowledge search, team collaboration, multilingual and accessible delivery, and measurable communication tied to operations. - Adoption is the proof point to evaluate. Legacy intranets average 30 to 40% adoption; the best digital workplace platforms reach 90%+ within 90 days. ## 1. They reach frontline staff who don't have corporate email The first problem digital workplace platforms solve is the most basic one: getting a message to people at all. [Employee communication](https://www.mangoapps.com/solutions/internal-communications) built on email assumes everyone has an inbox and checks it. On the frontline, that assumption breaks. A store associate, a warehouse picker, or a care aide may have no company email account, or an account they see once a week on a shared back-office computer. The result is a communication blind spot covering most of the workforce. When PetSmart looked at its own numbers, it found that about 80% of its 55,000 employees largely did not have access to company communications. As Corporate Communications Manager Sheena Christensen put it, the platform gave the company the ability to reach its entire associate base for the first time ever. Digital workplace platforms reach frontline staff through a mobile app, push notifications, in-app feeds, and SMS, with audience targeting so the right location or role sees the right message. Read receipts and acknowledgment tracking confirm that critical updates, a safety recall, a policy change, an emergency closure, actually landed. That is the difference between sending a message and knowing it was received. > **Frontline example:** At [RAM Tool](https://www.mangoapps.com/resources/ram-tool-case-study), a single must-read post replaced a 3 a.m. round of phone calls. "Before, the operations manager in Dallas would have had to wake up at 3:00 in the morning and start calling people. Instead, I was able to create a must-read post and send it to every employee in those branches," said Kyle Loafman, VP of Purchasing. ## 2. They put the entire workplace on the phone employees already carry Frontline work happens on the move, not at a workstation. Mobile access is not a convenience feature for these teams; it is the only access that exists. Digital workplace platforms are built mobile-first, delivering the schedule, the task list, the training video, the announcement, and the team chat through one [branded employee app](https://www.mangoapps.com/solutions/employee-app) on a personal or shared device. The friction that kills adoption on desk-era tools, logging into a portal, remembering a password, finding the right link, disappears. The best [frontline workforce tools](https://www.mangoapps.com/articles/best-frontline-communication-software) require no corporate email to sign in, work offline for environments where connectivity drops, and run on whatever phone the employee already owns. Employees open the company's own branded app, not a tool that looks like it belongs to IT. This matters because access drives usage, and usage is where every other benefit comes from. Most organizations have an intranet, yet only about 13% of employees use it daily and roughly a third never use it at all ([Social Edge Consulting, 2025](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics)). A mobile-first design is the single biggest lever for closing that gap with frontline staff, which is why [modern intranet](https://www.mangoapps.com/solutions/modern-intranet) platforms have moved away from the desktop-portal model entirely. ## 3. They centralize updates into one source of truth Ask a frontline manager where company information lives and the honest answer is usually "everywhere." Some of it is in email for the people who have it. Some is on a break-room bulletin board. Some is in a group text, a manager's phone contacts, a binder, or a Slack channel half the team isn't in. Important updates get lost, contradicted, or simply never seen. Digital workplace platforms replace that sprawl with a single, authoritative home base. Company news, policies, schedules, and documents live in one place, targeted to the locations and roles that need them, and time-stamped so everyone knows what is current. When something is official, it is in one known location instead of scattered across half a dozen channels. The operational payoff is trust. At [Petauri](https://www.mangoapps.com/resources/petauri-case-study), CIO Tim Barker described how the platform became the default reference point: "It's become a follow-on to any statement when people are citing a metric or result. If something is true and accurate, then it's on MangoApps." A single source of truth removes the daily guessing game about which version of a message to believe. | Without a digital workplace platform | With a digital workplace platform | | --- | --- | | Updates scattered across email, texts, paper, and chat apps | One authoritative feed targeted by location and role | | No way to confirm frontline staff saw a message | Read receipts and acknowledgment tracking on critical posts | | Knowledge buried in shared drives and binders | Searchable knowledge base on every phone | | Reaching the field means manager phone trees | One post reaches every employee instantly | | Communication runs separately from the actual work | Updates connect to schedules, tasks, and operations | ## 4. They make company knowledge findable in seconds Reaching people is half the battle. The other half is helping them find an answer when they need it, mid-shift, without calling a manager or digging through a binder. Knowledge that exists but cannot be found is, from the employee's point of view, knowledge that does not exist. This is a measurable drain. Only 23% of frontline workers believe they have access to the technology they need to be productive, and the right mix lifts productivity about 22% ([Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html)). For an hourly frontline worker, minutes lost hunting for a procedure are minutes taken from customers, patients, or production. Digital workplace platforms address this with a structured knowledge base plus [AI-powered semantic search](https://www.mangoapps.com/ai/capabilities) that returns answers, not just a list of links. An employee can ask a question in plain language, in their own words, and get the specific procedure, policy, or form they need. Holt of California pointed to exactly this capability: "The biggest benefit of MangoApps for us is the search capabilities. It's honestly made such a huge difference for our users," said Sales Development Supervisor Sarah Cenedella. The reason AI search works on these platforms, and not on a pile of disconnected tools, is that the knowledge, the permissions, and the employee context all live in one place. AI can only give a safe, relevant answer when it knows who is asking and what they are allowed to see. That is a platform property, not a feature you can bolt onto fragmented systems. ## 5. They connect dispersed teams instead of isolating them Frontline work is often lonely in a way desk work is not. A store manager sees their own four walls. A field technician spends the day alone in a truck. A nurse on a night shift may never cross paths with peers two floors up. Around 40% of employees report feeling isolated at work, and high belonging is linked to a 56% increase in job performance ([Harvard Business Review](https://hbr.org/2019/12/the-value-of-belonging-at-work)). For distributed teams, connection is not a soft benefit; it shows up in retention and output. [Collaboration platforms](https://www.mangoapps.com/solutions/employee-engagement) built into the digital workplace give frontline staff a way to reach peers, ask questions, share what is working, and feel part of something larger than their location. Communities and groups let a charge nurse compare notes with another unit, or a store manager see how other stores are handling the same problem. [A.S. Watson](https://www.mangoapps.com/resources/aswatson-case-study) saw this directly. "As a store manager, you're mainly only focused on your own shop. But now you're able to see other shops and other store managers and what they're doing. So it makes this big company feel more personal," said Kruidvat Store Manager Vera Scherff. The effect on managers is just as real. When a team can see the schedule, the task list, and the latest announcements themselves, the manager stops fielding the same questions all day and gets back the first hour of every shift. Collaboration that runs through the platform instead of through the manager's phone changes how a frontline team actually operates. Nonprofits feel this acutely too: the [YMCA uses its digital workplace](https://www.mangoapps.com/resources/how-a-digital-workplace-helps-ymca-employees-better-serve-their-communities) to connect dispersed branch staff who rarely share a building. ## 6. They break language and accessibility barriers A frontline workforce is rarely homogeneous. A single distribution center or hospital system may employ people who speak a dozen languages, work across multiple shifts, and have a wide range of comfort with technology. Workplace technology that ships in one language and assumes a steady connection leaves part of the team behind by design. Digital workplace platforms built for the frontline handle this natively: [real-time translation across 50+ languages](https://www.mangoapps.com/ai/translation) so every employee reads communications in their own language, offline mode for warehouses and remote sites where signal drops, and simple, role-based navigation that does not require a manual. As A.S. Watson's HR Director Jan Carel Uylenberg noted of the rollout at [Superdrug](https://www.mangoapps.com/resources/superdrug-case-study), the experience "is far more attractive and appeals far more to the way our young store staff wants to communicate. You don't need a big manual in order to find your way through." Inclusion is also a retention issue. 51% of people quit jobs because they don't feel a sense of belonging, and 72% of employees say it's important to feel part of a community at work ([O.C. Tanner, 2023](https://www.octanner.com/global-culture-report)). Reaching every employee in their own language, on a device they already use, is a concrete way to deliver that belonging at scale. ## 7. They make communication measurable and tie it to the work The final way digital workplace platforms help frontline staff is the one leaders feel most: they turn communication from a hopeful broadcast into something measurable, and they connect it to the work itself. With email and phone trees, an internal communications leader can never prove reach to the frontline. Did the message land? Did people read it? Did the right locations acknowledge the new safety procedure? A digital workplace platform answers those questions with read receipts, acknowledgment tracking, and [engagement analytics](https://www.mangoapps.com/analytics-insights) by location, role, and audience. Top-quartile engagement units show 23% higher profitability and 81% lower absenteeism ([Gallup Q12 meta-analysis](https://www.gallup.com/workplace/236927/employee-engagement-drives-growth.aspx)), and you can only strengthen what you can measure. Measurement is most valuable when communication connects to operations. On a true platform, an announcement about a new procedure can link to the [task](https://www.mangoapps.com/solutions/task-management) that implements it, the [shift schedule](https://www.mangoapps.com/solutions/workforce-management) it affects, and the [safety acknowledgment](https://www.mangoapps.com/solutions/safety-compliance) that confirms it, all in the same app, all tied to the same employee record. The [Kansas City Chiefs](https://www.mangoapps.com/resources/kansas-city-chiefs-case-study) reached 600 event staff instantly and lifted adoption from 40% to 90%, replacing a patchwork of methods with one system. "Huddle has been a lifesaver for us. We can reach 600 staff members in an instant, which we were never able to do before," said Director of Event Services Caitlin Petit. ## Why the platform decision matters more than any single feature It is tempting to treat the seven benefits above as a shopping list and buy a point tool for each: one app for communication, another for scheduling, another for knowledge. That approach made sense when the goal was simply "reach the frontline." It makes far less sense now, for two reasons. First, every additional tool is another login, another vendor, and another place for frontline staff to give up. Adoption is fragile on the frontline; spreading it across five apps almost guarantees that none of them sticks. Second, AI has changed what "good" looks like. An AI assistant that can actually help a frontline worker, answer a question, draft a message, find a policy, has to know who the employee is, what they are allowed to see, and what their work context is. That requires shared identity, shared permissions, and shared data across every workflow, governed in one place. A chatbot sitting on top of disconnected tools cannot provide that safely. A platform built from one foundation, with [AI governance](https://www.mangoapps.com/ai/governance) spanning every workflow, can. The platform decision is, increasingly, the AI decision. This is the logic behind choosing a single [AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/platform) rather than assembling point solutions. The enterprises seeing the strongest results, AutoZone, PetSmart, [Raley's](https://www.mangoapps.com/resources/raleys-case-study), A.S. Watson, OU Health, the Kansas City Chiefs, did not solve frontline communication with a better email tool. They chose one platform their whole workforce opens, started with the workflow they needed most, and expanded from there without rebuilding identity, data, or integrations. That is also [why MangoApps](https://www.mangoapps.com/why-mangoapps) holds 98% customer retention across industries from [healthcare](https://www.mangoapps.com/industries/healthcare) to [retail](https://www.mangoapps.com/industries/retail), [grocery](https://www.mangoapps.com/industries/grocery), and [manufacturing](https://www.mangoapps.com/industries/manufacturing). ## What to look for when evaluating digital workplace platforms For internal communications, HR, IT, and operations leaders comparing options, a short evaluation checklist separates frontline-ready platforms from desk-era [enterprise communication systems](https://www.mangoapps.com/articles/best-digital-workplace-platforms) wearing a mobile coat: 1. **Reach without email.** Can it deliver to and confirm receipt from staff who have no corporate email? 2. **Real mobile adoption.** Ask for adoption rates 90 days post-launch, not feature lists. Aim for 80%+; the best platforms exceed 90%. 3. **One connected experience.** Does communication, knowledge, collaboration, and daily work live in one app, or is it a bundle of integrations? 4. **AI grounded in the platform.** Is [AI embedded in workflows](https://www.mangoapps.com/ai) with shared permissions, or a chatbot bolted onto disconnected content? 5. **Enterprise security and compliance.** For regulated industries, confirm [certifications](https://www.mangoapps.com/security-compliance) such as SOC 2 Type II, ISO 27001, and HITRUST. 6. **Multilingual and offline support.** Native translation and offline mode for a real frontline workforce. 7. **A vendor accountable for adoption.** The strongest sign of confidence is a vendor that ties its [commercials to whether employees actually adopt](https://www.mangoapps.com/success-services). ## Frequently asked questions **What is the difference between a digital workplace platform and an intranet?** An intranet is primarily a place to publish and find content, and most were designed for desk workers logging in from a computer. A digital workplace platform is broader and mobile-first: it combines communication, knowledge, collaboration, and day-to-day work in one app that reaches frontline staff who have no corporate email or laptop. The practical difference shows up in adoption, where legacy intranets average 30 to 40% and frontline-ready platforms reach 90%+ within 90 days. **How do digital workplace platforms reach frontline workers without email?** They deliver communication through a mobile app, push notifications, in-app feeds, and SMS rather than an inbox. Employees sign in without a corporate email address, often on the personal phone they already carry, and managers can confirm delivery with read receipts and acknowledgment tracking on critical updates. **Do frontline employees need a company laptop or email account to use one?** No. Frontline-ready platforms are designed for staff who have neither. They run on any phone, support shared-device and kiosk access for locations where workers don't have individual devices, and work offline where connectivity is unreliable. **Are digital workplace platforms secure enough for regulated industries?** Enterprise-grade platforms carry [certifications](https://www.mangoapps.com/security-compliance) including SOC 2 Type II, ISO 27001, and, for healthcare, HITRUST, along with SSO, role-based access control, and audit logging. Healthcare systems, financial services firms, and government agencies use them in production, so the right platform meets strict compliance requirements. **How long does it take to roll out a digital workplace platform?** Typical enterprise implementations run about 8 to 12 weeks, depending on scope and integrations. The more important number is adoption after launch: leading platforms reach 90%+ of the workforce within 90 days, which is the metric that determines whether the investment delivers value. **What is the ROI of a digital workplace platform for frontline teams?** Returns come from three places: time saved (workers toggle between applications roughly 1,200 times a day, per [Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications), and the average company runs 101 applications, per [Okta](https://www.okta.com/newsroom/articles/businesses-at-work-2025/)), engagement and retention gains (engaged teams show meaningfully higher productivity and far lower turnover, per [Gallup](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx)), and consolidation savings from replacing four or five point solutions with one platform. See how the math works on [MangoApps pricing](https://www.mangoapps.com/pricing). ## Related reading - [The Complete Guide to Frontline Communication Platforms](https://www.mangoapps.com/articles/frontline-communication-platforms-guide) - [How to Increase Frontline Intranet Adoption Without Sacrificing Governance or Compliance](https://www.mangoapps.com/articles/frontline-intranet-adoption-governance-compliance) - [Best Digital Workplace Platforms](https://www.mangoapps.com/articles/best-digital-workplace-platforms): how the leading options compare for frontline-heavy organizations. - [Best Frontline Communication Software](https://www.mangoapps.com/articles/best-frontline-communication-software): a focused look at tools for reaching deskless teams. - [How to Improve Frontline Communication in 2026](https://www.mangoapps.com/articles/how-to-improve-frontline-communication-2026): a practical playbook for closing the reach gap. ## The bottom line Frontline staff have spent two decades as an afterthought in enterprise technology. Digital workplace platforms reverse that by starting from the frontline reality, a phone, a shift, no inbox, and building communication, knowledge, collaboration, and work around it. The seven benefits above all trace back to one idea: when every employee opens the same connected app, the workforce that was invisible finally shows up in one place. MangoApps is the [AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/platform), built for deskless and frontline teams for 18+ years, serving 2 million+ users worldwide with 98% customer retention and 90%+ adoption within 90 days. Start with the workflow your teams need most, communication, scheduling, knowledge, and expand on the same platform when you are ready. *Ready to see how it works for your frontline? [Schedule a call](https://www.mangoapps.com/schedule-a-call) or explore the [AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/platform).* --- # Employee Recognition Programs That Actually Stick **Author:** MangoApps Team **Published:** 2026-06-14 **Category:** workforce-management The announcement goes out in an all-hands. Points are loaded into the new recognition platform. # Employee Recognition Programs That Actually Stick The announcement goes out in an all-hands. Points are loaded into the new recognition platform. Managers get a quick training. For the first few months, activity is high — nominations roll in, posts get reactions, the leaderboard shows healthy movement. Then something happens. Or rather, nothing happens. The nominations slow. Points sit unredeemed in employee accounts, accumulating silently. A few star performers get recognized repeatedly while quieter contributors go months without acknowledgment. Redemption requests for high-value items arrive without budget review, creating surprises at month-end. HR can see the engagement dropping but can't pinpoint exactly why. By eighteen months in, the recognition program has become a line item nobody talks about. This scenario is familiar to anyone who has tried to build a recognition culture at scale. The program design is rarely the problem. The problem is operational infrastructure — and this week's releases address that directly, not just for recognition but for the same failure mode that shows up across performance management, safety inspections, and field operations. ## Why Points Accumulate and Go Nowhere Recognition points without a use-by date have a predictable life cycle: they accumulate, employees assume they will always be there, and urgency to actually use them never materializes. The result is a balance sheet full of liability and a recognition program that feels like a loyalty card nobody redeems. [Points expiry on a configurable schedule](https://www.mangoapps.com/changelog/3023) changes the dynamic. When employees know their points have a shelf life, they engage with the redemption catalog. That engagement, in turn, tells HR which rewards actually matter — data that is almost impossible to gather when everyone is sitting on a dormant balance. The problem compounds when you cannot see who is being recognized and who is not. Most managers do not intentionally play favorites, but without visibility, recency bias and proximity bias do their quiet work. Certain employees get mentioned in every team meeting; others, equally capable, go unacknowledged because they work a different shift or operate in a different building. The [fairness dashboard](https://www.mangoapps.com/changelog/3023) that shipped this week gives managers a view of which team members have and have not been recognized recently. That is a small addition with outsized behavioral impact — surfacing the absence of recognition makes it far easier to correct before it compounds into a retention risk. On the redemption side, high-value items flowing through without review is a program design gap that most platforms leave open. [Multi-level approval for redemptions](https://www.mangoapps.com/changelog/3023) above a configurable threshold closes it. And the launch of [managed swag fulfillment](https://www.mangoapps.com/changelog/3023) — a full inventory ledger with inbound receiving and an ops queue for fulfilling orders from warehoused stock — means that physical merchandise no longer requires a shadow manual process running alongside the digital program. Together these changes address something important: recognition programs fail not because organizations stop caring, but because the operational friction becomes invisible and cumulative. Points do not expire. Nobody sees who has been overlooked. High-value approvals bypass review. Physical items require offline coordination. Each friction point alone seems minor. Together, they hollow out the program over time. There is a separate but related failure in content quality. A [recognition content moderation layer](https://www.mangoapps.com/changelog/3022) that screens posts through AI and keyword filters before they publish means the program maintains its integrity across web, mobile, and API surfaces — without requiring a human review queue. ## The Same Problem Shows Up Everywhere Recognition programs are not unusual in this way. Performance reviews, safety inspections, compliance training — they all share the same failure mode. Someone designs a thoughtful process, launches it with energy, and then watches it decay as the manual follow-through fails to materialize at scale. The [Review Automation Rules Engine](https://www.mangoapps.com/changelog/3019) released earlier this week addresses this for performance management. Previously, triggering performance reviews required manual action or an all-or-nothing global toggle. Now, admins define named rules tied to tenure milestones, hire anniversaries, or quarterly schedules — and reviews create themselves. The [360-degree feedback and post-review outcome automation](https://www.mangoapps.com/changelog/3020) that followed takes this further: development plans and PIPs tied to review outcomes now flow from automation rules rather than from someone remembering to follow up. Inspection programs have the same structural weakness. Safety and compliance teams design rigorous processes, then discover that routing inspections across dozens of assets requires significant manual coordination — which means it happens inconsistently. [Item-based inspection cycles](https://www.mangoapps.com/changelog/3021) change that: the system generates one inspection per physical asset on schedule and routes them through claim pools, round-robin distribution, or location manager assignment. The program runs without anyone having to orchestrate it each cycle. For data that comes in from external HRIS systems, [automatic scheduled Merge.dev syncs](https://www.mangoapps.com/changelog/3015) mean that payroll and workforce data stays current on a configured cadence — not on the schedule of whoever remembers to trigger a manual pull. The pattern across all of these is consistent: remove the human trigger, and the program runs reliably. Keep the human trigger, and it runs when someone remembers. ## What Changes for Field Workers There is a related failure mode in frontline organizations that does not get named as often: programs that exist on paper but are not accessible where the work actually happens. A standard operating procedure that requires an internet connection is, effectively, optional for a field technician at a remote site. A training video without closed captions is a communication gap for workers in loud environments. A recognition program that requires a desktop browser is a recognition program that most hourly employees never engage with. The [offline access for SOPs](https://www.mangoapps.com/changelog/3021) released this week addresses the connectivity problem directly. Field workers can access procedures and submit completion data without a connection; the sync happens automatically when they are back in range. This is not a convenience feature. It is the difference between a safety program that is theoretically in place and one that workers can actually execute in the field. On the communication side, videos shared in chat now [automatically generate closed captions](https://www.mangoapps.com/changelog/3017) via AI transcription, with no manual effort required. For frontline teams working across shift changes where verbal briefings are not always possible, removing that comprehension barrier matters. And [real-time video playback](https://www.mangoapps.com/changelog/3017) — where a video placeholder upgrades to a playable player the moment transcoding completes, without a page reload — means the medium is actually usable in the flow of a workday rather than requiring a separate download step. ## The Thread Look across this week's releases and a single thread runs through them: the gap between "we have a program" and "the program actually runs." Recognition programs stall when points accumulate without urgency, visibility is absent, and the operational overhead of physical merchandise lives outside the platform. Performance programs decay when triggering reviews depends on someone's calendar. Inspection cycles drift when routing requires manual coordination each time. Field programs fail when they cannot reach the people they are designed for. None of these are design problems. They are infrastructure problems. The organizations that sustain recognition, performance, and compliance programs over time are the ones where the system carries the operational burden — not the ones where a coordinator is quietly running the program in a spreadsheet behind the scenes. The recognition program that launched with energy eighteen months ago did not fail because people stopped caring about recognition. It failed because the small operational gaps added up — and nobody had a view of them until the engagement numbers told the story. Fixing that requires more than good intentions. It requires systems that handle the follow-through whether or not anyone remembers to trigger them. That is what this week's releases are, taken together: a set of quiet answers to the question of what it would look like if these programs just ran. --- # How to Improve Frontline Communication in 2026 **Author:** Andy Tolton **Published:** 2026-06-12 **Category:** employee-engagement Frontline teams stay cut off when communication lives in scattered tools. Here is how digital workplace platforms fix frontline employee communication in 2026. Send a company-wide message today, then ask a simple question: did the people stocking shelves, running the floor, or driving the route actually see it? For most enterprises, the honest answer is no. This is not a content problem. The message was fine. It is a reach problem, and it lives in the tools. About 80% of the global workforce is frontline, with no desk, no corporate email, and no company laptop ([HR Executive](https://hrexecutive.com/frontline-first-hr-engaging-the-80-that-powers-your-business/)). They execute the work and stay invisible to the systems measuring it. And the disconnect is not only at the edges: across organizations, only 13% of employees strongly agree that leadership communicates effectively with the rest of the company ([Gallup](https://www.gallup.com/workplace/313367/internal-communications-execute-winning-strategy.aspx)). When the announcement never lands for the frontline, that gap is not surprising. It is predictable. The fix in 2026 is not one more messaging app stacked on top of the pile. It is a shift in where communication lives. This guide explains how digital workplace platforms improve [frontline employee communication](https://www.mangoapps.com/solutions/internal-communications), what separates a platform from a point tool, and what to look for when you evaluate one. ## What is a digital workplace platform? A digital workplace platform is a single system that connects communication, knowledge, and daily work for every employee, frontline and desk-based, through one mobile and web experience. Instead of a separate app for announcements, another for schedules, another for tasks, and another for training, a platform puts them on one foundation with shared identity, permissions, and data. The distinction that matters: a communication app reaches people. A digital workplace platform reaches people *and* connects the message to the work that follows it. When the shift announcement lands, the schedule, the task, the safety form, and the acknowledgment all live in the same place. ## Why frontline communication breaks down Before fixing it, name what actually breaks. Three failures show up in nearly every enterprise. **The frontline has no inbox.** Email-based and intranet-based communication assumes a desk and a corporate login. The 80% who carry a phone instead of a laptop never receive the message in a channel they check. So leaders fall back on managers, who fall back on group texts and WhatsApp, and the official message dissolves into a hundred informal versions. **Updates are scattered.** When the policy change is in email, the schedule is in one app, the SOP is in a binder, and the training is in an LMS nobody opens, there is no single source of truth. Employees do not know which version is current, and managers spend the first hour of every shift answering questions the system should have answered. **Communication is one-way.** Most frontline employee communication is broadcast only. Leaders send; the floor receives. Without a channel for employee voice, you lose the early signal on safety issues, customer friction, and morale, and engagement erodes quietly. The stakes are concrete: 85% of employees feel more engaged when leaders communicate transparently ([SHRM](https://www.shrm.org/labs/resources/building-a-connected-workforce-key-insights-on-employee-engagement)), and the most engaged teams outperform the least engaged on profitability by 23% ([Gallup](https://www.gallup.com/workplace/236927/employee-engagement-drives-growth.aspx)). The gap is rarely effort. It is infrastructure. ## How to improve frontline communication in 2026 These are the concrete moves that close the gap. Each one ties to a capability your digital workplace platform should already support. ### 1. Meet the frontline on the phone they already carry Frontline employee communication only works if it reaches people where they are, which is a personal mobile device, not a workstation. Choose [frontline workforce tools](https://www.mangoapps.com/solutions/employee-app) that work with no corporate email, no laptop, and no friction at login. The cashier should open one app and see the message, the schedule, and the task without an IT ticket. If reaching your frontline requires provisioning hardware or a complicated SSO step, adoption will stall before the first announcement goes out. ### 2. Centralize updates into one source of truth Pick one place for every official update, then make everything else point to it. Policy changes, store communications, safety alerts, and recognition should live on the same platform employees already use for their schedule and tasks. Centralization is what kills the "which version is current?" question. It also gives compliance a clear, timestamped record of what was published and when, which scattered group texts never can. ### 3. Make communication two-way Broadcast-only communication treats employees as an audience. The better model treats them as a source. Employee communication improves when the floor can respond, flag an issue, complete a survey, or recognize a teammate inside the same app. This is where modern collaboration software and [employee engagement platforms](https://www.mangoapps.com/solutions/employee-engagement) earn their place: not as a separate social network, but as a feedback loop attached to the work. Two-way channels surface the safety hazard, the broken process, and the quiet flight risk while you can still act on them. ### 4. Connect the message to the work This is the move most companies miss, and the one that separates a real platform from a comms app. After the announcement lands, the work has to happen. The new return policy needs a task. The safety update needs an acknowledgment. The product launch needs a training. When communication and execution live on the same platform, the message does not just inform the shift, it runs the shift. A standalone communication tool stops at "sent." A digital workplace platform carries the message through to "done." ### 5. Measure reach, not just send volume You cannot improve what you cannot see. Most internal comms teams can report how many messages they sent and almost nothing about whether the frontline read them. Use workplace technology that reports [read rates, acknowledgment, and reach by location, role, and shift](https://www.mangoapps.com/analytics-insights). Now a regional message that landed at headquarters but missed three stores is visible, and fixable, instead of invisible. Measurement turns communication from a broadcast into a managed system. ### 6. Govern AI on the same foundation AI is moving into employee communication fast, from drafting announcements to answering policy questions to translating across languages on the floor. But AI is only as safe as the data and permissions underneath it. A chatbot bolted on top of five disconnected tools cannot reliably know who should see what. When communication, knowledge, and work share one platform with one permission model, AI can answer the frontline question, surface the right SOP, or summarize the shift safely, because it operates inside the same [governed context](https://www.mangoapps.com/ai/governance). In 2026, the AI conversation and the platform conversation are the same conversation. ## Point tools vs. a platform: the difference that compounds It is tempting to solve frontline communication by buying a dedicated comms app. It is the fastest-looking option and the most expensive over time. Every standalone tool you add is another login, another data silo, another permission model, and another integration for IT to maintain. The average employee already touches 8 to 15 apps to do their job. A separate communication app does not reduce that number, it adds to it. And it leaves the original problem intact: the message still does not connect to the schedule, the task, or the training, because those live somewhere else. A digital workplace platform inverts the math. One foundation carries communication, knowledge, operations, and AI. The internal comms team gets reach. Managers get one place to run the shift. IT gets one system to secure instead of five to stitch together. Legacy intranets average 30 to 40% adoption because they were built for desks and never reached the frontline. Platforms built for mobile-first frontline use see materially higher engagement because the channel matches how the work actually happens. The decision is not "which communication app." It is "which platform," because the platform decision is the one that determines whether every future workflow, and the AI on top of it, holds together or fragments. ## What to look for in a digital workplace platform Use this as a short evaluation checklist when you compare digital workplace platforms and frontline workforce tools. - **Mobile-native frontline access** with no corporate email or laptop required, in the employee's language. - **One platform for communication and work**, so the message connects to schedules, tasks, SOPs, and training, not just a feed. - **Two-way channels**: surveys, employee voice, recognition, and acknowledgment built in, not bolted on. - **Reach and read analytics** segmented by location, role, and shift. - **[Enterprise security and compliance](https://www.mangoapps.com/security-compliance)** that meets your bar (look for HITRUST, SOC 2 Type II, ISO 27001) with a clear audit trail. - **AI grounded in your data and permissions**, not a generic chatbot sitting on disconnected systems. - **Proven frontline adoption**, with references in your industry and real numbers, not promises. If a vendor cannot speak to all seven, you are likely looking at a communication point tool, not a platform. ## How MangoApps approaches frontline communication MangoApps is the [AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/platform). Communication is where most customers start, then they expand across Employee Experience, Frontline Operations, and People Operations on the same platform, without rebuilding identity, permissions, or data. That design is why frontline communication works on MangoApps where it stalls elsewhere. Employees open one app on the phone they already carry, with no corporate email or login friction. The announcement lands next to the schedule, the task, the safety form, and the training, so the message runs the shift instead of just informing it. Internal comms teams see reach and read rates by location and role. And because communication, knowledge, and work share one foundation, AI can act inside a governed context rather than guessing across disconnected tools. The results show up in adoption. MangoApps customers consistently reach 90% or more adoption within 90 days, against an industry where most intranets see only 13% daily use ([Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics)). The platform serves more than 2 million users worldwide, holds 98% customer retention, and has been built for the frontline for 18 years. Enterprises like AutoZone, PetSmart, and [Raley's](https://www.mangoapps.com/resources/raleys-case-study) use it to reach teams that email and legacy intranets never could. MangoApps is also the only vendor with an Adoption Guarantee: if your employees do not adopt, you do not pay. ## Frequently asked questions **What is a digital workplace platform?** A digital workplace platform is a single system that connects communication, knowledge, and daily work for every employee through one mobile and web experience. Unlike a standalone communication app, it puts announcements, schedules, tasks, training, and AI on one foundation with shared identity and permissions, so a message can connect directly to the work that follows it. **How do digital workplace platforms improve frontline communication?** They reach frontline employees on the mobile devices they already carry with no corporate email required, centralize every update into one source of truth, add two-way channels for employee voice, connect each message to the schedule or task it triggers, and report read and reach rates by location and role. Together these close the gap that leaves most frontline teams uninformed. **What is the difference between an employee communication app and a digital workplace platform?** A communication app reaches people and stops at "sent." A digital workplace platform reaches people and connects the message to the work that follows, the task, the acknowledgment, the training, on the same system. Point tools add another login and silo; a platform consolidates communication, operations, and AI on one secure foundation. **What should you look for in frontline workforce tools?** Prioritize mobile-native access with no email or laptop required, one platform that links communication to actual work, two-way feedback channels, reach and read analytics, enterprise-grade security and compliance, AI grounded in your own permissions and data, and proven adoption with references in your industry. **How do you measure frontline communication?** Move beyond send volume to read rates, acknowledgment, and reach segmented by location, role, and shift. Pair those with engagement signals from surveys and employee voice. Reach data shows whether the message landed; engagement data shows whether it mattered. --- **Want the full picture for 2026?** The [2026 Internal Communications Trends eBook](https://www.mangoapps.com/resources/2026-internal-communications-trends-ebook) breaks down 12 trends reshaping how enterprises reach a distributed, frontline-heavy workforce, from cutting through digital noise to enabling managers, adopting AI responsibly, and proving impact with data. No email required. --- # Intranet and knowledge tools in 2026: fix frontline reach **Author:** MangoApps Team **Published:** 2026-06-09 **Category:** mango-scoop Evaluate intranet platforms, spot 7 frontline problems, and compare knowledge management software. Plus: AI video subtitles in Chat. Hand-picked stories from MangoApps this week. ## How to Evaluate Employee Intranet Platforms in 2026 ![How to Evaluate Employee Intranet Platforms in 2026](https://mango-cdn.b-cdn.net/images/blog-thumbnails/blog_532_20260608_231746.png) A practical guide to choosing an intranet platform by adoption, architecture, AI governance, and frontline reach. [Read the full story →](https://www.mangoapps.com/articles/evaluate-employee-intranet-platforms-2026) --- ### More to read #### How to Replace an Outdated Intranet in 2026 Learn how to diagnose intranet failure, improve frontline access, and choose a modern platform that boosts adoption and efficiency. [Read more →](https://www.mangoapps.com/articles/how-to-replace-an-outdate-intranet-in-2026) #### 7 Intranet Problems Hurting Frontline Teams Outdated intranet platforms create real costs for frontline teams. Here are 7 intranet platform challenges that hurt communication, engagement, and productivity — and what to do instead. [Read more →](https://www.mangoapps.com/articles/intranet-problems-hurting-frontline-teams) #### Internal Communications Governance: Why Reach Isn't Enough A logistics coordinator sends what she thinks is a targeted safety update to the overnight crew at her distribution center. She selects the right template, types the message, hits send. [Read more →](https://www.mangoapps.com/articles/internal-communications-governance-why-reach-isn-t-enough) #### 10 Best Knowledge Management Software for Teams in 2026 Compare the best knowledge management software for desk and frontline teams to centralize knowledge, improve access, and reduce repeat questions. [Read more →](https://www.mangoapps.com/articles/best-knowledge-management-software) --- ### From the Wire > **Andy Tolton** · Product > Picture a store manager at a mid-sized retail chain. Her team's schedule lives on a piece of paper taped to the break room wall. She photographs it, posts it to a WhatsApp group, and hopes nobod... > > [Read on Frontline Wire →](https://www.mangoapps.com/frontline-wire/picture-a-store-manager-at-a-mid-sized-retail-chai) --- ### What's New **General** — [Product Update - June 08, 2026](https://www.mangoapps.com/changelog/3017) * **[AI-Generated Video Subtitles in Chat](https://www.mangoapps.com/key-features/instant-messaging)** — Videos shared in chat rooms now automatically generate closed captions (... **General** — [Product Update - June 07, 2026](https://www.mangoapps.com/changelog/3016) * **[Mango CS: Automated Success Plan Outcome Tracking](https://www.mangoapps.com/directory/app/mango-cs)** — CSMs can now link Success Plan outcomes to live customer engagement... --- # How to Evaluate Employee Intranet Platforms in 2026 **Author:** MangoApps Team **Published:** 2026-06-08 **Category:** intranet A practical guide to choosing an intranet platform by adoption, architecture, AI governance, and frontline reach. Most intranet evaluations start in the wrong place. Teams build a features spreadsheet, collect vendor demos, score each one on a 1-to-5 scale, and pick the highest number. Three years later, adoption is at 30%, IT is managing four separate tools that were supposed to be replaced, and leadership is asking why the platform is not working. The problem is not the evaluation itself. It is what gets evaluated. This guide focuses on the decisions that actually matter when comparing [employee intranet platforms](https://www.mangoapps.com/solutions/modern-intranet) in 2026: who the platform was built for, what it does beyond publishing content, how AI fits into the architecture, and whether adoption will hold 24 months after launch. ## What "Employee Intranet Platform" Actually Means in 2026 The term has stretched significantly. A decade ago, an intranet was a content repository: announcements, org charts, HR policies, maybe a search bar. Today, buyers use "intranet platform" to describe tools that range from simple news feeds to full [digital workplace solutions](https://www.mangoapps.com/platform) covering communications, document management, task execution, workforce scheduling, and AI-assisted workflows. Before you can compare platforms, your team needs to agree on what problem you are actually buying against. Most evaluations collapse into confusion because IT wants a secure knowledge base, HR wants a communication tool, and operations wants workflow automation. Those are not mutually exclusive, but they demand different criteria. Three questions to answer before you start vendor demos: 1. **Who are we actually trying to reach?** Desk workers, frontline workers, or both? Platforms built for office employees often underperform badly when rolled out to store associates, nurses, or warehouse crews who work on personal phones and never touch a corporate laptop. 2. **What replaces what?** List the tools you want this to replace. A platform that consolidates your [internal communication tools](https://www.mangoapps.com/solutions/internal-communications), document repository, and HR portal is a materially different investment than one that just adds a prettier intranet on top of what you already have. 3. **What does success look like in 18 months?** Daily active usage? Reduction in email volume? Faster policy distribution? Named, measurable outcomes before any vendor conversation. ## The Six Criteria That Separate Good Evaluations from Bad Ones ### 1. Frontline and Deskless Reach This is the most underweighted criterion in most evaluations, and it is the one most likely to determine whether your deployment succeeds. Approximately 80% of the global workforce is deskless. Healthcare, retail, manufacturing, hospitality, and field services all run on hourly, shift-based, or distributed workers who have no company email address, no assigned laptop, and no patience for a seven-step login process. Most enterprise collaboration platforms were designed for desk workers and retrofitted for the frontline. The result is an experience that works fine on a desktop browser, breaks down on a personal mobile device, and sees abandonment within weeks. When evaluating platforms, ask: does this product have native mobile support built from the ground up, or is it a responsive web app? Can employees access it without a corporate email? What does the experience look like on a four-year-old Android phone with intermittent connectivity? Industry benchmark: only 13% of employees use their company intranet daily, and 31% never use it at all (Nielsen Norman Group / Social Edge Consulting 2025). That number is almost always worse for frontline populations. Best-in-class intranet adoption runs 80 to 85% weekly active usage. If a vendor cannot show you frontline customer retention rates, that is the answer. ### 2. Platform Architecture vs. Point Tool There is a structural difference between buying a communication tool and buying an [employee platform](https://www.mangoapps.com/platform). Communication tools do announcements and document access well. Employee platforms run communications, but also handle scheduling, [task management](https://www.mangoapps.com/solutions/task-management), onboarding, [HR records](https://www.mangoapps.com/solutions/hr-operations), safety inspections, and learning in a unified data model. Why does architecture matter for an intranet buyer? Because this is almost certainly not the last tool you will need. If you buy a single-function intranet today, you will face a second implementation, a second vendor negotiation, and a second integration project when the next need surfaces. The more important structural question in 2026 is AI governance. A chatbot built on top of four disconnected tools cannot safely act across the business. It will hallucinate, reference documents employees should not see, and fail to complete workflows that require context from multiple systems. [AI needs shared identity, shared permissions, and a unified employee data model](https://www.mangoapps.com/ai/architecture) to work reliably. Platforms that were built as unified systems provide that. Bolt-on AI layers on top of fragmented tools do not. Ask vendors: where is employee data stored, and is it shared across all the apps in the platform? What permissions model governs AI access? Can AI act within workflows, or does it only generate text responses? ### 3. Administration and IT Overhead The demo almost always understates how much configuration, ongoing maintenance, and [integration management](https://www.mangoapps.com/integrations) an enterprise intranet requires in production. Ask specifically: - How many hours per week does a typical customer's IT team spend on platform administration? - What integrations are native (included, maintained by the vendor), and which require custom middleware? - When an API or integration breaks, who is responsible for the fix? - What does an update or version upgrade process look like, and who manages it? A tool that requires a dedicated SharePoint administrator or a third-party integration layer to function as advertised carries a total cost of ownership that is rarely captured in the initial contract. ### 4. Adoption Architecture (Not Adoption Promises) Every vendor will tell you their platform gets adopted. Ask for evidence: average weekly active users across their customer base at 90 days post-launch, at 12 months, at 24 months. Ask for customer references in your specific industry, not just case studies on a website. The adoption question is particularly important for frontline deployments because the adoption pattern is different. Desk workers will use a platform if IT sets it as the default browser homepage. Frontline workers only adopt tools that solve a daily problem they already have. If the platform does not address shift communication, schedule visibility, task completion, or something else that matters to their actual workday, it will not be used. Also evaluate: what does the vendor do when adoption stalls? Do they have a [customer success structure](https://www.mangoapps.com/success-services) that includes hands-on support, or do you get routed to a help desk? ### 5. Security, Compliance, and Deployment Options Enterprise intranet platforms touch employee communications, HR documents, policy records, and increasingly operational data. The [security and compliance requirements](https://www.mangoapps.com/security-compliance) are serious, and they vary significantly by industry. [Healthcare](https://www.mangoapps.com/industries/healthcare) and [financial services](https://www.mangoapps.com/industries/financial) organizations need HIPAA controls, audit trails, and data residency options. [Manufacturing](https://www.mangoapps.com/industries/manufacturing) and government-adjacent customers may require on-premise or private cloud deployment. Multi-national organizations need data sovereignty compliance across jurisdictions. Minimum standard for enterprise evaluation in 2026: SOC 2 Type II. Preferred: HIPAA readiness, ISO 27001 certification, and the ability to support private cloud or customer VPC deployment for regulated workloads. Ask vendors about their penetration testing cadence, their third-party audit schedule, and what happens to your data if you leave. ### 6. Total Cost, Contract Structure, and Vendor Stability [Pricing](https://www.mangoapps.com/pricing) in this category is highly variable and often opaque. Watch for: - **Per-seat pricing for frontline workers.** If you have 2,000 desk workers and 8,000 frontline workers, a flat per-seat model can make a platform unaffordable for the actual deployment you need. Ask whether frontline workers are priced differently. - **Integration fees.** Some vendors charge separately for connectors to HRIS, ITSM, or other enterprise systems. Those costs are not always visible in initial proposals. - **Module expansion pricing.** If the pitch is "start with comms, add operations later," get the pricing for that expansion in writing during the initial negotiation. - **Contract auto-renewal and exit terms.** What notice is required? What happens to your data at contract end? Vendor stability matters because intranet platforms tend to run for five to ten years. A vendor acquired by a PE firm, operating at significant losses, or dependent on a single product line carries risk that should factor into a long-term infrastructure decision. ## The 2026 AI Evaluation Add-On AI capabilities have become a required part of any intranet evaluation, but most teams are not asking the right questions. "Does it have AI?" is not useful. Every vendor will say yes. More useful questions: - **Where does the AI get its context?** Document retrieval only, or full employee workflow context including schedules, tasks, and HR records? - **Does AI respect permissions?** If a warehouse associate asks the AI a question, can it surface only information that employee is authorized to see? - **Can AI take actions, or only generate answers?** The platforms moving fastest in 2026 allow [AI agents](https://www.mangoapps.com/ai/agent-library) to complete workflows (submit a form, schedule a shift coverage request, route a help ticket) not just summarize documents. - **Is the AI model proprietary or third-party?** This matters for data privacy. What is sent to the model, how is it stored, and who can access it? - **What is the governance model?** Who configures what the AI can and cannot do? Is that controlled at the [platform governance level](https://www.mangoapps.com/ai/governance) or left entirely to end users? The vendors who handle these questions badly, or who have not thought about them, are telling you something important about their AI roadmap. ## How to Structure an Evaluation Process A disciplined evaluation for an enterprise intranet platform runs roughly six to eight weeks and involves four stages: **Stage 1: Internal alignment (Week 1-2).** IT, HR, and internal communications agree on success criteria, must-have requirements, and deal-breakers before any vendor contact. Document the current tool landscape and what will be replaced. **Stage 2: Market scan and RFI (Week 2-3).** Issue a structured request for information to four to six vendors. Include questions on frontline support, AI governance, security certifications, deployment options, and customer retention data. Eliminate vendors who cannot answer basic questions in writing. **Stage 3: Scored demos (Week 3-5).** Run structured, scenario-based demos rather than open-ended presentations. Give each vendor the same three or four use cases that represent your actual environment. Score against pre-agreed criteria. **Stage 4: Reference checks and commercial negotiation (Week 5-8).** Talk to at least two customer references in your industry, with similar workforce composition, who have been on the platform for at least 18 months. Get multi-year pricing in writing, including expansion modules and frontline seat costs. One note on analysts: Gartner, Forrester, and IDC all publish research on this category. Recognition in analyst reports is a reasonable baseline filter, but it is not a substitute for reference checks. Analyst rankings reflect a broad market view. Your specific use case, industry, and workforce composition matter more than a quadrant position. ## Common Evaluation Mistakes **Evaluating for the deployment you have, not the deployment you need.** If you have 500 desk workers today but will onboard 2,000 frontline workers next year, evaluate for the harder use case now. **Selecting on demo quality, not production evidence.** Vendor demos are rehearsed. Customer references are not. The gap between how a platform presents in a 60-minute demo and how it performs in month 18 of a 2,000-user deployment is large. **Underweighting adoption.** A platform that 40% of employees use is not a better outcome than what you had before. Build adoption commitments, including specific usage benchmarks at 90 days and 12 months, into the contract. **Ignoring the AI architecture question.** Platforms that cannot answer clearly how AI accesses data, respects permissions, and governs actions are not ready for enterprise deployment at scale. That is not a risk worth taking in 2026. ## What a Strong Platform Looks Like The strongest [employee intranet platforms](https://www.mangoapps.com/solutions/modern-intranet) in 2026 share a common architecture: a unified employee data model that powers communication, operations, and people workflows from a single identity and permissions layer. AI runs inside that architecture, not on top of it. For organizations with significant frontline workforces, the additional test is native mobile reach. A platform that was built for the desk and retrofitted for the field will always underperform against one that treated frontline workers as the design center from the start. [MangoApps](https://www.mangoapps.com/why-mangoapps) is built on this architecture. The platform covers Employee Experience, Frontline Operations, and People Operations on a single foundation, with [AI embedded in workflows](https://www.mangoapps.com/ai) rather than appended as a chatbot layer. Customers including [Raley's](https://www.mangoapps.com/resources/raleys-case-study), [RAM Tool](https://www.mangoapps.com/resources/ram-tool-case-study), and [A.S. Watson](https://www.mangoapps.com/resources/aswatson-case-study) deploy it to frontline populations in retail and field service environments where 30% legacy intranet adoption rates are not acceptable. MangoApps is the only platform in the category that contractually guarantees adoption. If employees do not adopt, you do not pay. [Schedule a call](https://www.mangoapps.com/schedule-a-call) to see how the platform performs against the criteria in this guide. ## Frequently Asked Questions ### What is the difference between an employee intranet and a digital workplace platform? A traditional employee intranet is primarily a publishing and document access tool: company news, policy libraries, org charts, and HR forms. A [digital workplace platform](https://www.mangoapps.com/platform) covers those functions but also integrates communications, task execution, [workforce management](https://www.mangoapps.com/solutions/workforce-management), HR workflows, and increasingly AI agents that can act across the business. The practical difference shows up in what happens after someone reads an announcement. In an intranet, nothing. In a digital workplace platform, the same employee can acknowledge the policy, complete a related training, submit a form, or initiate a workflow from the same app. Most modern buying conversations involve platforms rather than traditional intranets, even when the word "intranet" appears in the RFP. ### What should an enterprise intranet RFP include? A strong intranet RFP covers six areas: (1) functional requirements by audience type (desk, frontline, manager, HR, IT); (2) integration requirements listing every system the platform must connect to; (3) security and compliance certifications required; (4) deployment options needed (SaaS, private cloud, on-premise); (5) adoption and success commitments including usage benchmarks and CSM structure; and (6) commercial terms including per-seat pricing tiers, expansion module costs, and exit terms. The most commonly omitted section is frontline-specific requirements. If any portion of your workforce is hourly, shift-based, or deskless, document the device types, connectivity conditions, and authentication constraints specific to that population before issuing the RFP. Vendors who cannot address those requirements specifically should be eliminated at the RFI stage. ### How does SharePoint compare to a dedicated intranet platform? SharePoint is the deepest Microsoft-native option in the category and the right choice for organizations heavily invested in the Microsoft 365 stack who primarily serve desk workers with standard corporate email accounts. It integrates natively with Teams, OneDrive, and Viva, and its Copilot AI works effectively across Microsoft data. The structural gap shows up in three places. First, frontline deployment: SharePoint requires corporate email and is difficult to deploy effectively on personal mobile devices without additional licensing and configuration. Second, operational workflows: SharePoint is built for content management, not task execution, scheduling, or [field service management](https://www.mangoapps.com/solutions/field-service). Third, AI breadth: SharePoint Copilot works on Microsoft data. Platforms with a unified employee data model can run [AI across every workflow](https://www.mangoapps.com/ai/capabilities) including operations, HR, and frontline execution. For organizations with significant frontline populations or multi-function workflow needs, a dedicated employee platform is typically the stronger long-term choice. ### How long does an enterprise intranet implementation take? Deployments range from six to sixteen weeks depending on organization size, the number of integrations required, whether content migration is in scope, and how much configuration the platform requires. Platforms with strong [implementation support](https://www.mangoapps.com/success-services) and dedicated customer success teams consistently hit the lower end of that range. The most common cause of delayed deployments is insufficient internal alignment before the implementation begins. IT, HR, and communications teams that have not agreed on governance, content ownership, and launch criteria before the vendor engagement starts will resolve those disagreements during implementation, adding weeks to the timeline. Stage 1 of the evaluation process above is designed to prevent exactly that. ### How much does an enterprise intranet platform cost? Pricing varies significantly by vendor, deployment model, and workforce composition. Most vendors price on a per-user-per-month basis, typically ranging from $3 to $15 per user per month for core intranet functionality, with higher tiers for full platform capabilities. Total cost of ownership should also account for implementation services, integration costs, ongoing administration overhead, and module expansion pricing. The most important pricing question for organizations with large frontline populations is whether frontline and desk workers are priced differently. Some vendors charge a uniform per-seat rate, which makes large hourly workforces prohibitively expensive to deploy. Others offer differentiated pricing tiers that reflect the usage patterns of frontline employees. Get the full cost model, including multi-year expansion scenarios, in writing before signing. [MangoApps pricing](https://www.mangoapps.com/pricing) includes differentiated tiers for frontline workers. ### How should we handle frontline workers who do not have company email addresses? Look for platforms that support phone-number-based or employee-ID-based authentication. Corporate email as a requirement effectively excludes hourly, shift-based, and field employees from the deployment. The authentication question is closely related to the device question. Frontline workers typically use personal phones, not company devices. The platform needs to work on consumer Android and iOS without requiring mobile device management (MDM) enrollment. It also needs to handle intermittent connectivity gracefully for workers in warehouses, clinical settings, or field environments where network reliability is inconsistent. Evaluate this capability in a real demo scenario, not a description of supported features. The [MangoApps employee app](https://www.mangoapps.com/solutions/employee-app) is built specifically for this: no corporate email required, works on any device, and supports offline access for connectivity-limited environments. ### What integrations should an enterprise intranet platform support? The most critical integrations for most enterprise buyers are: HRIS (Workday, SAP SuccessFactors, ADP, UKG) for employee data and org structure; ITSM (ServiceNow, Jira Service Management) for help desk routing; identity providers (Okta, Azure AD, Google) for single sign-on; content tools (SharePoint, Google Drive, Box) for document access; and communications platforms (Microsoft Teams, Slack) for notification routing. Beyond the integration list, evaluate how integrations are maintained. Native integrations maintained by the vendor are fundamentally different from connector frameworks that require middleware or custom development to configure and sustain. Ask specifically: when a system on this list changes its API, who rebuilds the connection? [MangoApps supports 200+ enterprise integrations](https://www.mangoapps.com/integrations) with vendor-maintained connectors that do not pass integration maintenance costs back to the customer. ### What is the most common reason intranet projects fail? Adoption failure, almost always driven by one of three root causes. The first is building for the wrong audience. Platforms deployed without frontline workers in mind, or without mobile-first design, will be used by desk workers and ignored by everyone else. If 70% of your workforce is on the floor, field, or clinic, and the platform treats mobile as an afterthought, you have already lost most of your audience before launch. The second is no clear value proposition for the end user. If employees cannot answer the question "what does this help me do today," the platform becomes another corporate initiative they check once and ignore. The tools that get used solve problems people already have: finding a schedule, getting an answer from a policy document, submitting a time-off request, reaching a manager. The third is insufficient change management. Technology deployment without communication, training, and leadership reinforcement rarely sustains adoption past the first 90 days. The vendors with the best adoption outcomes build change management frameworks into the implementation, not as an upsell. [See how leading organizations have driven adoption](https://www.mangoapps.com/resources/how-a-modern-intranet-improves-efficiency-coordination) through structured launch programs. ### How do you migrate from a legacy intranet to a new platform? Content migration is typically the most time-consuming part of an intranet transition. Start by auditing existing content before the vendor engagement begins: how much content exists, what percentage is still accurate and relevant, and what can be archived rather than migrated. Most organizations discover that 40 to 60% of their intranet content is outdated enough that it does not need to be migrated at all. That changes both the scope and cost of the transition significantly. Parallel deployment, running the new platform alongside the old one for 30 to 60 days, is standard practice for transitions with large content libraries or complex integrations. It allows the team to validate the new environment before decommissioning the legacy platform. Plan explicitly for the cutover date and communicate it clearly to employees. Ambiguity about which platform to use during the transition period consistently damages adoption of the new one. [See how organizations have approached the transition to a modern intranet](https://www.mangoapps.com/resources/upgrading-to-a-modern-intranet) in practice. ### How do you measure intranet ROI? ROI for an employee intranet platform is measured across three categories: efficiency gains, [engagement](https://www.mangoapps.com/solutions/employee-engagement) improvements, and risk reduction. Efficiency metrics include search success rate, time to find information, reduction in email volume for policy and announcement distribution, and help desk ticket reduction from self-service adoption. Engagement metrics include weekly active users, content interaction rates, survey response rates, and manager communication reach into frontline teams. Risk metrics include policy acknowledgment completion rates, [safety incident rates](https://www.mangoapps.com/solutions/safety-compliance), and compliance audit trail completeness. McKinsey research estimates that a well-deployed intranet can generate 20 to 25% productivity improvement and a 26% reduction in turnover. The key word is "well-deployed." Platforms at 30% adoption generate very little of that value. Platforms at 85% adoption generate most of it. Build your ROI model around adoption targets, not feature counts. ### What AI features should be on a 2026 intranet evaluation checklist? At minimum, evaluate six capabilities. First, permissions-aware semantic search across documents and knowledge bases. Second, AI-assisted content creation for internal communications. Third, auto-translation for multilingual workforces. Fourth, [AI agents](https://www.mangoapps.com/ai/agent-library) that can act within workflows, not just retrieve information. Fifth, a clear [AI governance model](https://www.mangoapps.com/ai/governance) specifying what the AI can access and what actions it can take. Sixth, a transparent data privacy policy covering what is sent to the underlying model and how it is stored. Beyond the checklist, the structural test is whether the AI was built into the platform or added on top of it. An AI layer bolted onto a fragmented tool set will always have boundary problems: it will not know what a specific employee is authorized to see, it will not be able to complete workflows that span multiple systems, and it will require constant prompt engineering to behave consistently. An AI built on a [unified employee data model and architecture](https://www.mangoapps.com/ai/architecture) with shared permissions behaves predictably because it was designed to operate that way. ### What is a realistic adoption benchmark to hold a vendor to? A good intranet achieves 60% or more weekly active users. Best-in-class is 80 to 85%. MangoApps customers consistently hit 87 to 90% adoption within 90 days. Build these numbers into your contract, not just your slides. The mechanism matters as much as the number. Ask vendors how they track adoption, how they identify at-risk accounts, and what intervention they provide when a deployment is underperforming. A vendor who cannot answer those questions specifically does not have a real adoption program. The [MangoApps Adoption Guarantee](https://www.mangoapps.com/why-mangoapps) is contractual: if employees do not adopt, you do not pay. ### How long do companies typically stay on an intranet platform? Enterprise intranet platforms run for five to ten years on average. That tenure makes the platform decision one of the most consequential infrastructure choices an IT or HR team makes, and it is why vendor stability and roadmap trajectory matter as much as current feature parity. Evaluate: is this vendor financially stable enough to still exist in year seven of your contract? Is the product roadmap driven by customer requests or investor pressure? Is the pricing model structured in a way that rewards expanded usage or penalizes it? A platform that costs significantly more as you add frontline workers and new modules will create commercial pressure to limit adoption exactly when you want to be expanding it. ### What should a vendor's customer success model look like? Look for named customer success managers (not a pooled support queue), structured onboarding with defined milestones, and post-launch business reviews with benchmarked adoption data. The strongest CSM models include proactive outreach when a metric drops below a threshold, not just reactive support when something breaks. Also ask: what is the average tenure of their CSMs? High CSM turnover means institutional knowledge about your deployment leaves with the person who had it. Ask for references specifically from customers who had a CSM transition mid-contract and how it was handled. [MangoApps success services](https://www.mangoapps.com/success-services) include named CSMs on every account, adoption benchmarking, and the contractual Adoption Guarantee that ties vendor compensation to deployment outcomes. --- *MangoApps is the AI-Ready Employee Platform for the Frontline, serving enterprise customers across [healthcare](https://www.mangoapps.com/industries/healthcare), [retail](https://www.mangoapps.com/industries/retail), [manufacturing](https://www.mangoapps.com/industries/manufacturing), [hospitality](https://www.mangoapps.com/industries/hospitality), and [financial services](https://www.mangoapps.com/industries/financial). [Schedule a call](https://www.mangoapps.com/schedule-a-call) to see how MangoApps compares against the criteria in this guide.* --- # How to Replace an Outdated Intranet in 2026 **Author:** MangoApps Team **Published:** 2026-06-08 **Category:** intranet Learn how to diagnose intranet failure, improve frontline access, and choose a modern platform that boosts adoption and efficiency. Most enterprise intranets were built to solve a 2005 problem: get corporate documents off shared drives and onto a website employees could browse from their desks. In 2026, that architecture is still running at tens of thousands of companies, and the failure symptoms are familiar to anyone who has tried to reach a nurse, a store associate, a warehouse technician, or a field technician through it. According to [Social Edge Consulting (June 2025)](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics), 91% of organizations have an intranet. Only 13% of employees use it daily. Thirty-one percent never open it at all. That is not a communications problem. That is an intranet platform problem. This guide is for the leaders responsible for fixing it: internal communications directors who know the content is good but the reach is not, IT leaders managing a platform nobody is using, HR and Employee Experience leaders watching engagement metrics decline while the intranet sits idle. If you are evaluating whether to migrate, overhaul, or replace your current system, here is how to make that call correctly. ## First: Diagnose Before You Shop The most common mistake in an intranet replacement project is skipping the diagnostic phase and jumping straight to vendor demos. You end up buying a platform that solves the symptoms you can see while the root cause stays buried. Before issuing an RFP or scheduling a demo, answer these five questions honestly: 1. What percentage of your workforce can access the intranet without a corporate email address or company device? 2. When a frontline employee has a question during a shift, does the intranet solve it in under 60 seconds? 3. What is your actual weekly active user rate — not the number of accounts provisioned, the number of people who opened it in the last seven days? 4. Can a manager publish a shift update, check task completion, and read an employee's survey response in the same tool, or does that require three different systems? 5. If your AI assistant or chatbot only has access to intranet content, what percentage of your actual workforce knowledge is it missing? If those questions surface discomfort, good. They are meant to. The answers tell you whether you have an adoption problem, an architecture problem, a frontline access problem, or all three. ## The Six Intranet Platform Challenges That Drive Replacement Decisions ### 1. Adoption Failure Social Edge Consulting benchmarks 60% weekly active users as a successful intranet. Best practice is 85% weekly login. Legacy platforms typically land at 30 to 40% — and that number is skewed toward desk workers who log in once a week to find the holiday schedule. Adoption failure is rarely a training problem. It is usually an access problem and a relevance problem. If the intranet requires a laptop, a VPN, and a corporate login to reach, and its homepage shows a CEO update and a PDF of last quarter's benefits guide, employees who work the floor will stop checking it within two weeks of launch. The tool is not built for their reality. **What to look for in a replacement:** [Mobile-first access](https://www.mangoapps.com/solutions/employee-app) with no corporate email requirement. Permissions that let employees see only what is relevant to their role, site, and shift. Content targeted by location, team, and job type so that what appears on screen is actually useful. ### 2. Frontline Communication That Never Reaches the Frontline According to [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology), 70 to 80% of the global workforce is deskless, about 2.7 billion people — a figure that appears in every intranet pitch deck. What is less often acknowledged is that most intranet platforms were not designed for those workers and have not been meaningfully updated to serve them. A hospital communications manager who publishes a policy update at 9 AM on Monday has no reliable way of knowing whether the charge nurse on the Tuesday night shift ever saw it. A retail operations director who posts a store execution checklist on the intranet may reach the assistant manager and miss every associate. The message is published. The message is not received. Frontline communication requires push delivery, not pull. It requires the ability to confirm receipt, track reads, and escalate unanswered messages. It requires a tool that lives on the device already in the worker's pocket, not on a kiosk in the break room. **What to look for in a replacement:** [Two-way communication channels](https://www.mangoapps.com/solutions/internal-communications) that work on personal mobile devices. Read receipts and delivery confirmation. Targeting by department, shift, and location. The ability to communicate with workers who do not have a corporate email address. ### 3. Productivity Loss from Poor Resource Access Employees spend just under six minutes a day on their intranet, according to [SWOOP Analytics](https://www.swoopanalytics.com/sharepoint-bm-25), which is one reason they ask a manager instead. For a 250-person operation, that is 50 full-time equivalents doing nothing but looking for documents, policies, SOPs, and answers that should be findable in seconds. Outdated systems make this worse in predictable ways: duplicate document libraries, broken links, SharePoint folders nested six levels deep, knowledge that lives in someone's email inbox and nowhere else. When AI-powered search is added on top of these architectures, it does not solve the problem — it surfaces bad data faster. **What to look for in a replacement:** Unified search that covers all content sources, not just the intranet pages. AI search that understands intent and role context, not just keywords. A [knowledge management structure](https://www.mangoapps.com/solutions/modern-intranet) that makes publishing and finding SOPs, policies, and forms genuinely straightforward for the people who need them on the job. See how organizations are [improving efficiency and coordination with a modern intranet](https://www.mangoapps.com/resources/how-a-modern-intranet-improves-efficiency-coordination). ### 4. Employee Engagement Disconnected from the Platform Gallup's 2026 State of the Global Workplace report puts the cost of global disengagement at $10 trillion — driven by the fact that only 20% of employees worldwide were engaged in 2025. [Gallup's Q12 meta-analysis](https://www.gallup.com/workplace/236927/employee-engagement-drives-growth.aspx) links top-quartile engagement to 23% higher profitability, 18% higher productivity, and 81% lower absenteeism. The causal link between what the intranet does and what engagement scores show is not theoretical — it is measurable. But most intranet platforms have no engagement infrastructure. They can publish content. They cannot close the loop. There is no way to send a pulse survey from the same tool that delivered the policy update. There is no recognition or rewards workflow. There is no employee voice mechanism that connects feedback to action. The result: engagement programs run in a separate HR tool, leadership communications run in the intranet, and employees experience them as two unrelated things. The signal that someone read the communication and how they felt about it never reaches the same place. **What to look for in a replacement:** Native survey and listening tools. [Recognition and rewards integrated into the daily workflow](https://www.mangoapps.com/solutions/employee-engagement), not siloed in a separate app. The ability to connect communication, feedback, and action in a single employee experience. ### 5. Outdated Systems Creating IT Debt and Integration Cost Every point tool added to the stack to compensate for intranet limitations adds integration cost, security surface area, and AI context fragmentation. The integration tax compounds. A company running separate tools for communications, knowledge management, HR, scheduling, tasks, and surveys may have 4 to 6 systems that each require maintenance, vendor management, contract renewal, and a custom [integration](https://www.mangoapps.com/integrations) that breaks when either platform updates. When AI is added to this environment, it cannot act safely across the business because it has no shared identity model, no consistent permissions layer, and no [security and compliance](https://www.mangoapps.com/security-compliance) framework. Each tool's AI has only a fragment of what it would need to be genuinely useful. **What to look for in a replacement:** A platform architecture that eliminates redundant tools rather than adding to the stack. One identity model. One data layer. One AI foundation that can operate across communications, operations, and HR workflows without rebuilding governance at each seam. ### 6. No Path from Launch to Long-Term Adoption Many intranet replacements fail not because the platform is wrong, but because the implementation model sets a go-live date and then leaves. Without a structured adoption program, usage spikes at launch and declines within 90 days as the novelty wears off and the old habits reassert themselves. Enterprise IT and HR leaders are not communications strategists, and they should not be expected to build and run an adoption program on top of a platform implementation. The platform vendor should be an active partner in that work, with named customer success resources, an adoption framework, and accountability for results. **What to look for in a replacement:** A vendor with documented adoption rates across their customer base. [Named CSM support](https://www.mangoapps.com/success-services), not a shared service queue. An explicit commitment — ideally a contractual one — that ties the vendor's success to the customer's adoption, not just to the go-live date. See what intranet accountability looks like in practice: [Modern Intranet Accountability](https://www.mangoapps.com/resources/modern-intranet-accountability). ## A Four-Phase Replacement Framework ### Phase 1: Define the Failure Scope (Weeks 1 to 3) Pull your actual usage data. Most organizations discover their "active user" numbers are inflated by automated logins or single-session events. Find your real weekly active user percentage by role, department, and location. Identify which workforce segments the current platform is not reaching. Run a brief diagnostic with managers and frontline workers: what do they actually need to find on shift, and how long does it take them to find it today? The gap between what the intranet promises and what it delivers in the first 60 seconds of a real workday is where replacement decisions get made. ### Phase 2: Build the Requirements Around the Frontline First (Weeks 2 to 4) Most intranet requirements documents are written by desk workers for desk workers, then retrofitted with a "mobile accessible" checkbox. In 2026, that approach produces another platform that never reaches the people who need it most. Write the requirements from the frontline use case outward. What does a store manager need during opening procedures? What does a charge nurse need at shift handoff? What does a warehouse technician need when an SOP changes mid-shift? If the platform cannot deliver those use cases without friction, it does not matter how good the corporate homepage looks. ### Phase 3: Evaluate on Adoption Evidence, Not Feature Lists (Weeks 3 to 8) Any modern intranet vendor will have a feature list that checks most boxes. The differentiator is not features — it is adoption outcomes. Ask vendors for documented adoption rates at organizations with a similar workforce profile to yours. Ask specifically about frontline worker adoption, not overall platform adoption. Ask about their customer success model: who owns your account, what does proactive support look like 90 days after launch, and what happens if adoption targets are not met. A vendor confident in their platform should have answers to all of those questions. MangoApps, for example, backs its platform with an Adoption Guarantee: if employees do not adopt, you do not pay. That kind of commitment is only possible when the vendor has 18+ years of deployment experience and 90%+ adoption rates across their customer base to back it up. [See how one organization approached upgrading to a modern intranet.](https://www.mangoapps.com/resources/upgrading-to-a-modern-intranet) ### Phase 4: Migrate in Value Increments, Not Big Bangs (Months 2 to 12) Enterprise intranet replacements that try to migrate everything at once tend to produce the same outcome as the platform they replaced: a complicated launch event followed by a slow decline. A better approach is to start with the highest-urgency, highest-visibility use case and drive it to adoption before expanding. If frontline communication is the biggest failure point, start there. If knowledge management and SOP access is costing productivity, start there. Build on a [platform architecture](https://www.mangoapps.com/platform) that allows you to expand across communications, operations, and HR workflows without rebuilding the foundation each time. ## What Separates a Modern Intranet from an AI-Ready Employee Platform The phrase "[modern intranet](https://www.mangoapps.com/solutions/modern-intranet)" does not mean much in 2026. Every legacy vendor has relaunched with a new UI, an AI search bar, and a mobile app. The question is not whether a platform looks current — it is whether the architecture can support what enterprise organizations will need over the next five years. The requirement is not an intranet with more features. The requirement is a platform that can operate safely across employee communications, frontline operations, and people operations with a single identity model, consistent permissions, and an [AI foundation](https://www.mangoapps.com/ai) that can act across the full employee workflow without creating new governance risks at every seam. That is the distinction between a point solution with a mobile app and an employee platform built to expand. MangoApps customers start with the app or pack most urgent to their business, such as frontline communications, modern intranet, or shift and task management, and expand across the platform without rebuilding identity, data, integrations, or AI governance. The practical result: organizations like AutoZone, PetSmart, [Raley's](https://www.mangoapps.com/resources/raleys-case-study), and OU Health run their frontline employee experience on a single platform, with 90%+ adoption maintained beyond the initial launch window. The intranet platform challenges they started with, such as poor reach, low adoption, disconnected communication, and productivity loss from fragmented tools, are solved at the platform level, not papered over with another integration. ## The Checklist Before You Commit Before signing a contract with any intranet replacement vendor, get clear answers on each of these: - **Frontline access:** Can workers without a corporate email or company device access the platform on their personal phone today, without IT provisioning? - **Adoption evidence:** What is the vendor's documented adoption rate at 90 days, and can they provide references from organizations with a similar workforce composition? - **AI governance:** If the platform includes AI features, does the [AI respect role-based permissions](https://www.mangoapps.com/ai/governance)? Can it access workflows beyond the intranet, including scheduling, task management, and HR data? - **Platform expandability:** Can you add communications, operations, and HR workflows on the same platform and data model, or does each capability require a separate implementation? - **Customer success model:** Who owns your account? What does their involvement look like in months 3, 6, and 12 after go-live? See [MangoApps Success Services](https://www.mangoapps.com/success-services). - **Contractual commitment:** Does the vendor offer any adoption guarantee, or does their accountability end at go-live? ## The Bottom Line For the adoption playbook and the governance controls that make it safe, see [How to Increase Frontline Intranet Adoption Without Sacrificing Governance or Compliance](https://www.mangoapps.com/articles/frontline-intranet-adoption-governance-compliance). To judge whether the problem is fixable or the platform has been outgrown, see [8 Signs Your Frontline Organization Has Outgrown Its Employee Intranet](https://www.mangoapps.com/articles/intranet-problems-hurting-frontline-teams). Outdated intranet platforms do not fail because the people running them are doing something wrong. They fail because the architecture was never designed for the workforce that most enterprises actually employ: workers without desks, without corporate devices, and without time to navigate a portal to find what they need during a shift. Replacing a legacy intranet is not a content migration project. It is a decision about the platform that will carry your AI strategy, your frontline communication, and your employee experience forward. That decision deserves more than a feature comparison. The organizations that make it well start with an honest diagnosis of where adoption is breaking down, build requirements around the employees the current platform is not reaching, and choose a vendor with documented outcomes and real accountability for adoption, not just a go-live date. If you are at the beginning of that process, [schedule a call with MangoApps](https://www.mangoapps.com/schedule-a-call) to benchmark your current state against adoption norms and identify the highest-value starting point for your workforce. *MangoApps is the AI-Ready Employee Platform for the Frontline. With 18+ years in market, 2M+ users, and 98% customer retention, MangoApps gives enterprises a single platform to run communications, operations, and people workflows, starting with the apps they need today and expanding without rebuilding.* --- # 10 Best Knowledge Management Software for Teams in 2026 **Author:** MangoApps Team **Published:** 2026-06-08 **Category:** workplace-productivity Compare the best knowledge management software for desk and frontline teams to centralize knowledge, improve access, and reduce repeat questions. When knowledge lives in Slack threads, outdated wikis, shared drives, and the heads of long-tenured employees, the problem is not that people refuse to share what they know. The problem is there is no reliable place to put it, keep it current, or find it again. For desk workers, that means tab-switching and lost time. For frontline workers in retail, manufacturing, healthcare, and logistics, it means procedures that never reach the floor, onboarding that doesn't stick, and managers fielding the same questions every shift. Knowledge management software solves this by giving organizations a governed, searchable, structured home for institutional knowledge: one that every employee can actually use. Software Best For Workforce Fit Platforms MangoApps Enterprises with frontline or deskless workers who need governed knowledge delivered to every employee on one unified platform Desk + Frontline Web, iOS, Android, Desktop Confluence Engineering and product teams standardized on Atlassian who need structured internal documentation tied to project work Desk Web, iOS, Android, Desktop Notion Startups and desk-based teams that want maximum flexibility for wikis, databases, and project tracking in a single workspace Desk Web, iOS, Android, Desktop Guru Sales and support teams that need verified, in-workflow answers delivered inside Slack, Salesforce, or the browser without switching tools Desk Web, iOS, Android, Browser Extension Document360 SaaS customer support and product teams that need a polished, AI-powered self-service knowledge base to deflect tickets Desk + External Web Bloomfire Large enterprises operationalizing scattered multi-format knowledge (including audio and video) across support, sales, and insights teams Desk Web, iOS, Android Tettra Small-to-mid Slack-centric teams that want a simple internal wiki with an AI bot that answers repetitive questions in chat Desk + Remote Web, Slack, Teams Slab Small-to-mid desk teams that want a focused, readable internal wiki with clean search and a low setup overhead Desk Web, iOS, Android Helpjuice Mid-size teams that need a fully branded, analytics-rich knowledge base with concierge design support and predictable tiered pricing Desk + External Web Nuclino Small teams and startups that want the fastest, simplest unified workspace for knowledge and light project coordination Desk Web, iOS, Android, Desktop MangoApps 4.6/5 Stars · Gartner Peer Insights 2M+ Users · Trusted Worldwide Gartner MQ Visionary · Intranet Packaged Solutions (2025) IDC MarketScape Leader · Employee Experiences (2024) Forrester Wave Strong Performer · Intranet Platforms (Q2 2026) Reworked IMPACT Award (Gold) · Intranet & Communications Platforms Most knowledge management tools are designed for the 30% of the workforce that sits at a desk. MangoApps is built for all of them. As the [AI-Ready Employee Platform for the Frontline](https://www.mangoapps.com/), MangoApps delivers structured, governed knowledge to [retail](https://www.mangoapps.com/industries/retail) associates, [healthcare](https://www.mangoapps.com/industries/healthcare) staff, [manufacturing](https://www.mangoapps.com/industries/manufacturing) technicians, and field crews on the same platform their desk-side managers use, with no corporate email, no VPN, and no separate admin tree required. The [knowledge management module](https://www.mangoapps.com/solutions/modern-intranet) includes a full wiki engine (version history, edit locking, sub-wikis, templates, and approval workflows), structured document libraries with metadata tagging, a [Company Knowledge Assistant](https://www.mangoapps.com/ai/capabilities) grounded in company content, and [auto-translation into 50+ languages](https://www.mangoapps.com/ai/translation) for multilingual frontline teams. KMWorld named MangoApps to its 100 Companies That Matter in Knowledge Management list for 2025. The IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces report (2024) named MangoApps a Leader, specifically citing its suitability for enterprises with both desk and deskless workers who need a single AI-enabled platform integrated across [200+ enterprise systems](https://www.mangoapps.com/integrations). What separates MangoApps in this category is not feature depth on any single KM dimension. It is the fact that knowledge management inherits the same RBAC, HRIS-driven audience scoping, SSO/SCIM, workflow engine, and [AI governance layer](https://www.mangoapps.com/ai/governance) as every other module on the platform. There is no parallel wiki admin tree to maintain. Knowledge published to a frontline audience reaches the floor on the same day it is approved, in the reader's language, on the device already in their pocket. **Key capabilities:** - **[Structured Wikis and Knowledge Libraries](https://www.mangoapps.com/solutions/modern-intranet):** Full wiki engine with sub-wikis, version history, diff/compare/rollback, edit locking, page templates, and per-wiki permissions. Builds the kind of organized, verifiable SOP library that paper manuals and file trees cannot sustain at scale. - **AI-Powered Knowledge Search:** A unified semantic search layer and Company Knowledge Assistant return cited answers grounded in company content, pulling across wikis, files, chat history, and connected external systems so employees find what they need without knowing where it lives. - **Content Governance and Auto-Governance:** Scheduled review cycles, auto-governance reminders, acknowledgment tracking, and audit trails keep knowledge accurate and compliant. For teams in regulated industries, MangoApps's [security and compliance framework](https://www.mangoapps.com/security-compliance) (HITRUST, SOC 2 Type II, ISO 27001, FedRAMP Moderate ATO) means governance requirements are met at the platform level. - **Frontline and Mobile Delivery:** Knowledge reaches workers via native mobile app, dedicated kiosk view, and offline access. No corporate email. No laptop. No VPN. For multilingual workforces, auto-translation covers 50+ languages at the point of delivery, not as a manual process. - **[Analytics and Engagement Insights](https://www.mangoapps.com/analytics-insights):** Per-wiki view analytics and platform-wide engagement data surface which knowledge is actually used, which pages are stale, and where gaps exist, so teams can act on real evidence rather than guessing at content quality. Sarah Cenedella, Sales Development Supervisor at Holt of California, a multi-entity CAT equipment dealer with 800 employees, describes the impact directly: "By housing all of our content in one platform, it helps alleviate probably 40% of the questions our departments get." After implementing MangoApps, Holt saw a 50% reduction in the time employees spent navigating resources and finding information, 85% weekly engagement across the platform, and eliminated the network-dependency problem that had locked knowledge behind a VPN on their previous system. **Free version:** No **Pricing:** Modular, quote-based; contact for enterprise pricing **Platforms:** Web, iOS, Android, Desktop [Schedule a demo to see MangoApps in action](https://www.mangoapps.com/schedule-a-call) ## Confluence Atlassian's Confluence is the most widely deployed enterprise documentation and wiki platform in the world, built specifically for teams that live in Jira and need their knowledge system to move with their project work. Every Confluence space maps to a product, a team, or a process, and pages connect directly to Jira issues, Loom recordings, and Trello boards within the same Atlassian workspace. The 2025 Rovo AI release extended this model by adding enterprise search across Confluence, Jira, Slack, and Google Drive from a unified interface, along with 20+ AI agents that can retrieve information, draft content, and surface answers without users switching contexts. Rovo is now bundled into all paid Cloud plans at no additional upfront cost, though it operates on a pooled credit model that scales by tier. Confluence works well for organizations where documentation is a byproduct of project work, and where the knowledge-creation and knowledge-consumption workflows are tightly coupled to existing Atlassian tooling. Its limitations are worth naming clearly: it is a browser and desktop product with no meaningful offline or kiosk capability, no deskless delivery model, and no practical path to reaching workers without corporate credentials. It is also not designed for customer-facing self-service knowledge bases. Organizations that primarily want to document engineering processes and product decisions, and whose workforce sits at a desk, will find Confluence a natural fit. Organizations with a significant frontline population will need to complement it with something else. **Best for:** Engineering and product teams already using Jira and Atlassian tools who need structured, searchable internal documentation integrated with their project workflows. **Consider alternatives if:** A meaningful portion of your workforce lacks corporate email, works on shared devices, or needs access from a mobile app without VPN connectivity. - **Rovo AI and enterprise search:** Rovo search reaches across Confluence, Jira, Slack, and Google Drive simultaneously, returning sourced answers from wherever the relevant content lives. For teams working across Atlassian and Google Workspace, this significantly reduces the "where did we put that?" problem that fragments desk-side knowledge work. - **Space and page hierarchy with version control:** Confluence organizes content in Spaces (team or project-level) and Pages (individual documents), with full version history, page restrictions, and collaborative editing. Templates cover common documentation types from meeting notes to technical specs, reducing the formatting overhead that discourages consistent knowledge capture. - **Atlassian ecosystem integration:** Confluence pages embed directly in Jira issues, and Jira actions can be created from Confluence whiteboards. For organizations where engineering documentation and project execution are the same workflow, the depth of this integration reduces the friction that typically keeps knowledge out of a wiki in the first place. **Free version:** Yes (up to 10 users) **Pricing:** Standard from approximately $5.42/user/month (annual); Premium and Enterprise plans available **Platforms:** Web, iOS, Android, Desktop [Explore Confluence](https://www.atlassian.com/software/confluence) ## Notion Notion is the most flexible all-in-one workspace on the market, and the most frequently cited vendor across knowledge management buying guides. It combines wikis, databases, kanban boards, calendars, and project tracking in a single block-based editor, which means teams can build almost any knowledge structure they can imagine without being constrained by a predefined template. Over 100 million people use Notion globally. The Business tier (at $20/user/month billed annually) includes full Notion AI: the Q&A feature answers questions grounded in the Notion database, Enterprise Search reaches into connected tools including Slack, Google Drive, and SharePoint, and AI agents (introduced in September 2025 as part of Notion 3.0) can execute multi-step research and drafting tasks. The flexibility that makes Notion compelling is also its most honest limitation. Without governance discipline enforced by the team, Notion workspaces can drift into sprawl. There are no structured verification schedules or native content expiry triggers; knowledge quality depends on team habits rather than system enforcement. Notion is also desk-and-browser-centric. It requires individual accounts, has no kiosk or shared-device mode, and does not cover HR, scheduling, or frontline operations. For teams whose knowledge problem is fully contained to desk-based employees who want a modern, flexible workspace, Notion is a strong starting point. For organizations that need verified knowledge at scale, or that need to reach a frontline population, the ceiling is clear. **Best for:** Startups, content teams, and desk-heavy organizations that want a flexible, high-quality workspace for wikis, documentation, and lightweight project management without heavy IT involvement. **Consider alternatives if:** You need content verification workflows enforced by the system, enterprise-grade governance for compliance purposes, or any frontline or deskless delivery model. - **Block-based flexibility:** Every Notion page is built from blocks, which means wikis, tables, embedded files, code snippets, and databases all live in the same editor. Teams can build knowledge structures that match their actual workflows rather than adapting their workflows to a predefined tool architecture. - **Notion AI Q&A and Enterprise Search:** The AI Q&A feature answers questions from your Notion content directly, returning sourced responses that link back to the original pages. Enterprise Search, available on Business tier, extends this to connected tools (Slack, Google Drive, Confluence, SharePoint), creating a unified answer layer across a team's most common content sources. - **Notion 3.0 Agents:** The September 2025 release introduced multi-step AI agents that can conduct research, draft documents, and complete tasks across connected tools. Custom agents run on a credit model ($10 per 1,000 monthly credits from May 2026), but pre-built agents handle common knowledge workflows without additional configuration. **Free version:** Yes **Pricing:** Plus $10/user/month; Business $20/user/month (annual, includes full Notion AI); Enterprise on request **Platforms:** Web, iOS, Android, Desktop [Explore Notion](https://www.notion.com/) ## Guru Guru is purpose-built for a specific, well-defined knowledge problem: sales and support reps give inconsistent answers because they cannot find the right information fast enough inside the tools they are already using. The solution is a governed, permission-aware knowledge layer that delivers verified answers inside Slack, Salesforce, and the browser, without requiring users to open a separate knowledge system. The verification workflow is the product's core differentiator. Every card in Guru is assigned an SME owner with a scheduled review interval. When content is due for review, the owner is notified and must verify or update it before the card is marked current. Among dedicated KM tools, this structured ownership model is what keeps Guru content trusted rather than drifting. The 2025 repositioning toward "AI Source of Truth" extended the model: Guru now connects to 100+ external tools, allowing its AI to answer questions grounded in the full breadth of a company's knowledge, not just content that has been manually migrated into Guru cards. The browser extension and Slack/Salesforce integrations provide a well-developed in-workflow delivery mechanism for desk-based teams. The honest scope boundary: Guru is an internal-only product. Every reader needs a paid seat. There is no public customer-facing knowledge base, no kiosk or shared-device delivery model, and no frontline workforce reach. Organizations whose knowledge problem is specifically about verified in-workflow answers for desk-based sales and support reps will find it a strong fit. Organizations that need to reach a broader or more distributed workforce will find the seat model constraining. **Best for:** Sales, customer-success, and support teams in Slack or Salesforce-heavy organizations that need verified, permission-aware answers delivered inside the tools they already use. **Consider alternatives if:** You need a public-facing customer help center, long-form technical documentation, frontline or deskless worker reach, or a product that does not require every reader to hold a paid seat. - **Structured verification workflow:** Every knowledge card has an assigned SME owner and a scheduled review interval. When a card is due for verification, the owner receives an automated prompt and must confirm the content is current before the card is re-published. This enforced ownership model is what keeps Guru content trusted rather than letting it quietly go stale. - **In-workflow delivery via browser extension and Slack:** Guru's browser extension surfaces relevant cards as users work in any web application, and the Slack integration answers questions directly in chat. A separate Salesforce integration surfaces knowledge inside Salesforce records. In each case, the answer comes to the user rather than requiring a context switch to a knowledge system. - **AI Source of Truth and Knowledge Agents:** Guru's AI layer connects to 100+ tools and returns cited answers grounded in company content from across connected sources. The Knowledge Agents feature (launched 2025) handles multi-step research and synthesis tasks. A Slack MCP integration (launched March 2026) allows Guru to surface answers from live Slack threads in addition to stored knowledge. **Free version:** Trial only **Pricing:** Paid plans from approximately $10/user/month; scales to $25 or more for AI-inclusive enterprise tiers (10-seat minimum; usage-based AI credits apply at higher tiers) **Platforms:** Web, iOS, Android, Browser Extension [Explore Guru](https://www.getguru.com/) ## Document360 Document360 is a dedicated knowledge base platform built primarily for customer-facing self-service, though it also supports internal knowledge for support agents and technical teams. It is the category leader for SaaS companies that need a polished, branded help center with strong editorial governance and deep integration into their support stack. The Eddy AI suite covers AI-powered answer search, a conversational chatbot, AI writing assistance, FAQ generation, and auto-translation into 50+ languages. Approval workflows, version history with side-by-side comparison, content scheduling, and role-based publishing controls give editorial teams the structure to maintain a high-quality public knowledge base as content volume grows. Document360 acquired Floik (interactive screen recording and demo creation) and integrated it as a native feature, which means support teams can embed step-by-step visual guides directly into articles without a separate tool. One important operational note: Document360 discontinued its free tier in November 2024 and moved to fully quote-based pricing. Organizations accustomed to transparent, self-serve pricing should factor in a sales conversation as part of the evaluation process. The platform is also primarily web-based, with no frontline delivery model and no path to reaching employees who do not have a desk or a browser. Its scope is well-defined and it executes within that scope well. Buyers who need an internal employee knowledge base rather than a customer-facing help center should evaluate other options in this guide. **Best for:** SaaS and technology companies whose primary knowledge management problem is customer ticket deflection through a polished, AI-powered, public-facing self-service help center. **Consider alternatives if:** You need an internal employee wiki rather than a customer-facing knowledge base, require transparent upfront pricing, or need to reach workers on mobile without individual accounts. - **Eddy AI suite:** Document360's AI layer covers conversational search, chatbot deployment, AI-assisted writing, FAQ generation from existing articles, and auto-translation into 50+ languages. The conversational search returns cited answers drawn exclusively from the company's knowledge base, reducing the hallucination risk common in general-purpose AI tools. - **Editorial governance and versioning:** Approval workflows, side-by-side version comparison, article scheduling, and role-based publishing give content teams full control over what goes live and when. Content expiry and review settings can be configured at the workspace level, supporting teams that need to maintain compliance with product documentation standards. - **Help-desk integrations and Floik embeds:** Native integrations with Zendesk, Freshdesk, Intercom, and other support platforms surface knowledge base articles inside ticket views. The Floik acquisition adds interactive screen-recording and product demo capabilities directly to articles, useful for SaaS products where a short visual walkthrough deflects more tickets than a written procedure. **Free version:** Trial only (14-day; free tier discontinued November 2024) **Pricing:** Quote-based; contact Document360 for current pricing **Platforms:** Web [Explore Document360](https://document360.com/) ## Bloomfire Bloomfire positions itself as an enterprise knowledge intelligence platform, and the positioning fits. Where most KM tools are organized around text documents and structured wikis, Bloomfire deep-indexes every content type in the organization, including audio recordings, video transcripts, PDFs, and presentations, and surfaces answers from across that entire corpus through its Synapse conversational AI. For large enterprises where institutional knowledge is scattered across formats and teams, including recorded sales calls, product webinars, and voice-of-customer research, this deep indexing capability is the clearest differentiator. Synapse returns cited, sourced answers with hallucination mitigation baked in: it answers only from company content, not from general model knowledge. The self-healing knowledge base feature uses AI to flag stale, duplicate, and low-quality content automatically, surfacing problems before they pollute search results rather than waiting for a quarterly audit. Knowledge Connectors federate SharePoint, Google Drive, Salesforce, Teams, and Confluence content without requiring migration, which is practically important for organizations that cannot afford to move every document into a new system before getting value. Bloomfire's scope boundary is pricing and scale. It is an enterprise product with scope-based, quote-only pricing that typically runs into six figures at scale. Small and mid-size teams will find lighter tools in this guide that fit the budget more naturally. Mobile apps are available, but the product is designed for office and contact center environments rather than for reaching deskless or frontline employees. **Best for:** Large enterprises with knowledge scattered across diverse formats and departments, particularly organizations in sales, market research, or customer support that need conversational AI answers grounded in video, audio, and document content simultaneously. **Consider alternatives if:** You are a small or mid-size team, need transparent upfront pricing, or need to reach a frontline workforce outside of a traditional office or contact center environment. - **Deep multi-format indexing:** Bloomfire indexes not just documents and wikis but audio recordings, video content (with searchable transcripts), PDFs, and presentations. This means a recorded product demo, a voice-of-customer research call, or a sales enablement webinar becomes searchable knowledge rather than a file that only the person who saved it can find. - **Synapse conversational AI with self-healing knowledge:** Synapse answers questions with cited, sourced responses drawn exclusively from company content, and the self-healing knowledge base AI flags duplicate and stale content before it surfaces in results. Together these features reduce the manual governance overhead that typically limits how well a large knowledge base stays current. - **Knowledge Connectors for federated search:** Rather than requiring organizations to migrate all content into Bloomfire, Knowledge Connectors pull from SharePoint, Google Drive, Salesforce, Microsoft Teams, and Confluence in place. This makes Bloomfire viable for enterprises that have years of existing content distributed across multiple systems and cannot move it all at once. **Free version:** No **Pricing:** Enterprise, quote-based; scope and seat-agnostic pricing; contact Bloomfire for details **Platforms:** Web, iOS, Android [Explore Bloomfire](https://bloomfire.com/) ## Tettra Tettra is a Slack-first internal wiki and AI knowledge base designed around a simple premise: if people are already asking questions in Slack, the knowledge system should live there too. The Kai AI bot sits inside Slack (and Microsoft Teams) and answers questions using RAG over the company's Tettra content library. When Kai cannot find an answer, it routes the question to a designated SME, collects their response, and with one click converts the exchange into a reusable knowledge page. This Q&A workflow is Tettra's most practical differentiator: it turns the questions that teams are already asking in chat into structured, searchable knowledge without requiring anyone to open a separate tool and write a new article from scratch. The verification layer lets page owners receive scheduled nudges to review and update content, and the knowledge gap identification feature surfaces which questions Kai is failing to answer, pointing teams toward the content that needs to be created. Tettra discontinued its free plan in mid-2024 and now starts at around $4/user/month (Basic) or $8/user/month (Scaling, with AI included, 10-seat minimum). It is worth naming what Tettra does not try to do: it does not offer enterprise-scale search, advanced formatting, broad third-party integrations, analytics depth, or any path to reaching frontline or deskless workers. The product is deliberately lightweight, and that is both its strength for small teams and its ceiling for organizations that need more. **Best for:** Small-to-mid teams that communicate primarily in Slack and want an internal wiki with an AI bot that reduces repetitive questions without requiring a separate knowledge management workflow. **Consider alternatives if:** You need enterprise governance capabilities, a customer-facing knowledge base, an analytics suite, or any mechanism for reaching employees who do not work in Slack or Teams. - **Kai AI bot in Slack and Teams:** Kai answers questions directly in Slack or Teams channels using the company's Tettra knowledge as its source. Employees get answers in the tool they are already using, and correct answers are surfaced without requiring a context switch. When Kai cannot find an answer, it routes the question to an SME automatically rather than leaving the question unanswered. - **Q&A to knowledge page conversion:** When a question is answered by a subject matter expert in chat, Tettra's workflow captures that response and converts it into a reusable page with one click. This is the most friction-free knowledge-capture workflow in this guide for teams that already live in Slack, because it does not require anyone to proactively decide to document what they know. - **Knowledge gap identification and page ownership:** Tettra surfaces questions that Kai could not answer, pointing admins to the content gaps that most affect their teams. Page ownership assigns accountability for keeping articles current, and scheduled verification nudges prompt owners to review content on a cadence rather than leaving it to drift. **Free version:** Trial only (30-day; free plan discontinued mid-2024) **Pricing:** Basic approximately $4/user/month; Scaling approximately $8/user/month (AI included); 10-seat minimum; Professional tier at $7,200/year for 50 users **Platforms:** Web, Slack, Microsoft Teams [Explore Tettra](https://tettra.com/) ## Slab Slab is a focused internal knowledge base and wiki built on the premise that most knowledge tools try to do too much. The product concentrates on two things: making it easy to write and organize knowledge, and making it easy to find again. The editor is clean and low-friction, and the unified search is Slab's clearest differentiator at its tier: it reaches not only into Slab content but into Slack, Google Drive, GitHub, Notion, Confluence, and other connected tools, returning results from a single search bar regardless of where the content lives. Free guest accounts on paid plans make it practical for teams that need occasional contributors or stakeholders to access content without a full seat. Content verification requests prompt page owners to review and update posts on a scheduled basis, providing a lightweight governance mechanism appropriate for teams without a dedicated knowledge manager. Slab is cloud-only and intentionally minimal. Permissions are simpler than those in Confluence or MangoApps. Analytics are lighter than Helpjuice. AI features cover editing assistance, natural-language knowledge queries, and autocomplete, but the product has not yet shipped AI writing, summarization, or translation at the depth of purpose-built tools in those areas. For a small or mid-size desk team that wants a clean, well-organized internal wiki with strong search and no administrative overhead, Slab covers the core knowledge problem effectively. Organizations that need granular permissions, enterprise analytics, customer-facing documentation, or any frontline delivery model will hit the product's intentional limits quickly. **Best for:** Small-to-mid desk teams that want a clean, focused internal wiki with strong cross-platform search and no IT overhead, and that do not need deep governance or external publishing capabilities. **Consider alternatives if:** You need granular role-based permissions, enterprise analytics, a customer-facing knowledge base, self-hosting options, or access for frontline or deskless workers. - **Unified cross-platform search:** Slab's search returns results from Slab content and from connected tools including Slack, Google Drive, GitHub, Notion, and Confluence, in one result set. For teams whose knowledge is distributed across several tools but not ready to migrate everything into one system, this cross-platform search surface significantly reduces the time spent hunting for documents. - **Content verification and page ownership:** Scheduled verification requests prompt page owners to review and confirm that their content is current, providing a lightweight ownership layer without the full SME-assignment model of dedicated tools like Guru. For small teams managing a modest knowledge library, this is sufficient to prevent content from quietly going stale. - **Clean editor with real-time collaboration and free guests:** The Slab editor is fast and low-friction, supporting real-time collaboration without the complexity of Notion's block model. Topics-based organization creates a browsable structure alongside search. Free guest access on paid plans means external contributors or part-time stakeholders can access content without consuming full seats. **Free version:** Yes (up to 10 users) **Pricing:** Startup approximately $6.67/user/month (annual); Business plan available; Enterprise on request **Platforms:** Web, iOS, Android [Explore Slab](https://slab.com/) ## Helpjuice Helpjuice has been a dedicated knowledge base platform since 2011, and its differentiator is not a feature list but a service model: every customer regardless of plan tier receives free concierge design support from the Helpjuice team to build a pixel-perfect branded knowledge base. For organizations that have tried to make a generic knowledge base look and feel like part of their product or brand, and found themselves limited by template constraints, this white-glove design capability is a genuine differentiator. The search engine indexes inside PDFs and returns results alongside analytics that show exactly what users searched for, which articles they opened, which searches returned no results, and which content has the highest and lowest engagement. This combination of deep search analytics and content effectiveness data gives knowledge managers a clear picture of where the knowledge base is failing users before those users give up and call support. The 2025 AI Suite added AI-assisted writing, AI-powered search, an AI chatbot, and one-click translation into 40+ languages, all gated to higher tiers. Helpjuice is a web-only product with no mobile app and no frontline delivery model. It is also one of the pricier knowledge base tools at the SMB tier, with plans restructured upward in 2024, starting from approximately $249/month. For mid-size teams that need a fully branded, analytics-rich knowledge base with predictable pricing and concierge design support, the cost reflects real value. For teams that need to extend knowledge beyond a browser, it is not the right fit. **Best for:** Mid-size teams that need a fully branded, analytics-rich internal or customer-facing knowledge base with concierge design support and a fixed-tier pricing model that does not scale strictly by seat count. **Consider alternatives if:** You need a mobile app, frontline or deskless delivery, real-time collaborative editing, or a knowledge system that extends beyond a web-based knowledge base into broader workforce operations. - **Concierge design and deep customization:** Helpjuice provides free custom theme design for every customer, building a knowledge base that matches the organization's brand, color system, and layout preferences without requiring internal design or development work. For companies embedding a knowledge base in a customer-facing product experience, this removes a common barrier to adoption. - **Search analytics and content effectiveness data:** Helpjuice's search analytics track what users search for, which articles they open, and which searches return no results. Managers can identify content gaps from actual user behavior rather than guessing what topics to write about, and can measure the effectiveness of existing content against real engagement data. - **AI Suite with 40+ language translation:** The AI Suite covers AI writing assistance, AI-powered search, a conversational AI chatbot, and one-click translation into over 40 languages. For organizations managing a knowledge base across multiple regions or language groups, the translation capability reduces the effort of maintaining multilingual content from a labor-intensive process to a one-step action. **Free version:** Trial only (14-day) **Pricing:** Starts from approximately $249/month; higher tiers include the AI Suite; contact Helpjuice for current pricing **Platforms:** Web [Explore Helpjuice](https://helpjuice.com/) ## Nuclino Nuclino is the fastest, simplest unified workspace in this guide. Where Notion bets on maximum flexibility and Confluence bets on deep Atlassian integration, Nuclino bets on speed: near-instant page creation, a minimal interface with almost no learning curve, and multiple views (list, board, table, and an interactive graph that visualizes connections between pages and surfaces orphaned content) that let small teams organize their knowledge however makes sense without a manual taxonomy exercise. The Sidekick AI feature (Business tier) handles content drafting, summarization, grammar correction, related-topic ideation, and AI image generation from within the workspace. Nuclino occupies a genuine space in the market for teams that need something better than a shared Google Drive folder but are not ready for the governance overhead of Confluence or the complexity of Notion's block model. The product's intentional minimalism creates clear limits: there are no structured review cycles or content expiry triggers, no enterprise-grade permissions, no analytics suite, no customer-facing publishing capability, and no frontline or deskless delivery model. Sidekick AI is included on the Business tier ($10/user/month annually). For teams of 5-30 people with a desk-based workflow and a contained knowledge problem, Nuclino covers the basics with very low overhead. For organizations that need the knowledge system to scale to hundreds of employees or reach a primarily mobile, deskless workforce, the product's floor becomes a ceiling. **Best for:** Small teams and startups that want a fast, visually intuitive unified workspace for knowledge and light project coordination, with minimal setup and a low per-user cost. **Consider alternatives if:** You need enterprise-grade permissions, content governance enforced by the system, analytics on knowledge usage, a customer-facing documentation site, or reach to frontline or deskless workers. - **Multiple views including interactive knowledge graph:** Nuclino surfaces content through list, board, table, and an interactive graph view that visualizes connections between pages and automatically highlights orphaned content with no incoming links. For small teams, the graph view provides a useful audit of the knowledge base's actual structure without requiring a formal taxonomy review. - **Speed and minimal learning curve:** Nuclino prioritizes page creation speed above all else. Pages open instantly, the editor is minimal, and the interface is designed to get out of the way. For teams where the primary barrier to knowledge capture is the friction of starting a new page, Nuclino's speed advantage is real and measurable. - **Sidekick AI for drafting and summarization:** The Sidekick AI (Business tier) assists with writing new pages, summarizing existing content, generating related topic ideas, and creating AI images. It operates from within the Nuclino workspace itself rather than requiring a separate AI tool, reducing the context-switching that slows down knowledge creation workflows. **Free version:** Yes (up to 50 items) **Pricing:** Starter approximately $6/user/month; Business approximately $10/user/month (annual, includes AI); Enterprise on request **Platforms:** Web, iOS, Android, Desktop [Explore Nuclino](https://nuclino.com/) ## How Each Platform Compares on What Actually Determines KM Success The four criteria below map directly to the factors that determine whether a knowledge management investment solves the actual problem or creates a well-organized library that only some of the workforce can reach. Platform Frontline & Deskless Accessibility Content Governance & Freshness In-Workflow Knowledge Delivery Platform Scope MangoApps Mobile app, kiosk view, and offline access deliver knowledge to workers without corporate email, a laptop, or network connectivity; 50+ language auto-translation at point of delivery Scheduled review cycles, auto-governance reminders, edit locking, version history with rollback, acknowledgment tracking, and audit trails meet SOC 2 Type II, HITRUST, and ISO 27001 compliance requirements AI Hub and Company Knowledge Assistant surface cited answers within the MangoApps app and chat layer; knowledge is accessible inside the same platform used for scheduling, communications, and tasks Knowledge management is one module within Employee Experience, Frontline Operations, and People Operations; all modules share one RBAC model, one HRIS integration, and one AI governance layer Confluence iOS and Android apps are available but require individual corporate credentials; no offline or kiosk mode; the product is designed for desk workers with browser access Space and page permissions, version history, and page restrictions are available; content expiry requires manual configuration via Page Properties; no automated verification workflow assigns ownership to SMEs Rovo AI searches across Confluence, Jira, Slack, and Google Drive from one interface; knowledge surfaces inside Atlassian tools but requires navigating to the Confluence space rather than receiving answers in the tool already in use Standalone documentation and project wiki; pairs with Jira, Loom, and Trello within the Atlassian suite; does not cover HR, scheduling, frontline operations, or employee communications Notion Web, iOS, Android, and desktop apps available; requires individual accounts for each user; no kiosk mode, shared-device access, or offline delivery for frontline shift workers No native verification schedules or content expiry triggers; page ownership and content quality depend on team discipline rather than system enforcement; suited for teams with strong documentation habits Notion AI Q&A answers questions from the Notion database; Enterprise Search reaches Slack, Google Drive, and SharePoint on the Business tier; users receive answers inside Notion rather than inside the tool where work is happening Flexible all-in-one workspace combining wikis, databases, and project management; AI features require the Business tier at $20/user/month; does not cover HR, scheduling, or workforce operations Guru Web, iOS, Android, and browser extension available; designed for desk workers in front of browsers, Slack, and Salesforce; no kiosk, shared-device, or offline delivery model for frontline workers Every knowledge card is assigned an SME owner with a scheduled review interval; the system enforces verification before a card is re-published; among purpose-built KM tools in this guide, this structured ownership model provides a clear content accuracy mechanism for desk-based knowledge Browser extension surfaces verified answers inside any active tab without a context switch; Slack and Salesforce integrations push answers into the tools reps are already using; knowledge reaches the worker rather than requiring the worker to go find it Standalone internal KM and AI Source of Truth product; connects to 100+ tools but does not replace communications, HR, scheduling, or frontline operational platforms Document360 Web-based help center widget embedded in products and support platforms; no mobile app or frontline delivery model; designed for customers and desk-based support agents Approval workflows, side-by-side version comparison, content scheduling, role-based publishing, and workspace-level article expiry settings provide strong editorial governance for customer-facing knowledge Embeds as a widget in web applications and help desks (Zendesk, Freshdesk, Intercom); articles surface inside support ticket views for agents; not designed to push knowledge proactively to employees in operational tools Purpose-built customer-facing and internal knowledge base; does not cover employee communications, HR, scheduling, or frontline workforce management Bloomfire Web, iOS, and Android apps available; mobile access exists but the platform is designed for enterprise office and contact center workers rather than deskless or shift-based frontline teams AI flags stale and duplicate content automatically in a self-healing knowledge base model; problems surface before searches return bad results rather than after a manual audit identifies them Knowledge Connectors federate SharePoint, Google Drive, Salesforce, Teams, and Confluence without migration; Synapse AI returns cited answers drawn from all connected sources in one response Enterprise knowledge intelligence platform for internal support, sales, and insights teams; does not extend to employee scheduling, HR operations, or frontline workforce management Tettra Web-based with Slack and Teams integrations; no dedicated mobile app; designed for desk and remote workers in chat-first environments; not suited for workers without a Slack or Teams account Page ownership assignment and verification nudges prompt review; the Q&A workflow converts answered Slack questions into reusable KB pages, building content governance from existing conversation history Kai AI bot answers questions directly inside Slack or Teams without requiring users to open a separate knowledge system; this is the most direct in-chat delivery model among the lightweight tools in this guide Lightweight standalone wiki and Q&A tool; integrates with Slack, Teams, Google Drive, and Notion; does not cover HR, communications, or frontline operational workflows Slab Web, iOS, and Android apps available; designed for desk-based teams; no offline, kiosk, or shared-device delivery model for frontline workers Verification requests prompt page owners to review and update content on a schedule; simpler than Guru's enforced workflow but sufficient for small teams managing a modest knowledge library Unified search reaches into Slack, Google Drive, GitHub, and other connected tools from within the Slab interface; users search from Slab rather than receiving answers inside the tools they are already using Focused internal wiki and knowledge base; integrates with Slack, GitHub, Jira, and Google Workspace; does not cover HR, communications, or frontline operational workflows Helpjuice Web-only product with no mobile app; designed for customer-facing and internal desk knowledge bases; no frontline, deskless, or shared-device delivery model Article versioning, draft/review workflows, author assignment, and engagement analytics identify content gaps from actual user searches; strong for teams that need to manage a public knowledge base at editorial quality Embeds as a widget or standalone site; users navigate to Helpjuice for answers; no proactive in-chat or in-tool delivery; an API is available for custom integrations Dedicated knowledge base for internal and customer-facing use; does not extend to employee communications, HR operations, scheduling, or frontline workforce management Nuclino Web, iOS, Android, and desktop apps available; requires individual accounts; designed for desk-based teams; no kiosk, shared-device, or offline frontline delivery model Editing history is tracked but there are no structured review cycles, expiry triggers, or content ownership assignments; content quality depends entirely on team habits Sidekick AI drafts and answers questions from within Nuclino; no native integration that pushes answers into third-party chat or operational tools; users access knowledge inside Nuclino Lightweight unified workspace combining wiki, docs, and light project tracking; Sidekick AI is limited to the Business tier; does not cover HR, communications, or frontline operational workflows The pattern this table surfaces comes down to a single trade-off. Purpose-built KM tools: Guru, Document360, and Helpjuice: go deeper on their narrow use case: Guru wins on desk-side in-workflow verification, Document360 wins on customer-facing editorial governance, and Helpjuice wins on branded customization and search analytics. Lightweight tools: Tettra, Slab, and Nuclino: win on speed and low overhead for small desk-based teams. The gap every purpose-built tool shares is frontline reach: none of them were built to deliver knowledge to workers without a desk, a corporate email, and a browser. MangoApps is the only platform in this guide that closes that gap while also meeting enterprise governance and compliance requirements. ## How to Choose: Matching Your Situation to the Right Platform **You have a significant frontline or deskless workforce.** If a meaningful share of your employees work without a desk: retail associates, warehouse workers, clinical staff, field technicians, hospitality crews: most tools in this guide will not reach them. Knowledge published to Confluence or Notion stays invisible to anyone without a corporate email address and a laptop. **MangoApps** is the only platform here built to deliver structured, governed knowledge to kiosk, shared-device, and personal mobile users with offline access and auto-translation for multilingual teams. If your knowledge problem includes the floor and not just the office, start here. **You are an engineering or product team standardized on Atlassian.** If your developers live in Jira and your documentation is already in Confluence spaces, adding a second knowledge system creates fragmentation rather than solving it. **Confluence** with Rovo AI now covers enterprise search across Confluence, Jira, Slack, and Google Drive within the existing licensing structure. Adding MangoApps or Notion on top makes sense only if you have a frontline population that Confluence cannot reach. Otherwise, the integration depth of the native Atlassian ecosystem outweighs what a separate tool provides. **You want maximum flexibility for a desk-based team without deep governance requirements.** Startups, content teams, and operations teams that need a flexible, modern workspace without heavy IT overhead should evaluate **Notion** first. It has the largest ecosystem, the most versatile editor, and the broadest AI feature set at the Business tier. If you find that Notion gets messy without team discipline, or that you need content verification enforced by the system rather than by habit, move to **Guru** for sales/support teams or **MangoApps** for organizations that need broader platform coverage. **Your primary knowledge problem is verified, consistent answers for sales or support reps.** If the core pain is that reps are giving inconsistent responses because they cannot find verified information fast enough inside their existing tools, **Guru** is purpose-built for this. Its verification workflow, browser extension, and Slack/Salesforce delivery address this specific use case well. Consider **MangoApps** if you have the same in-workflow need and also require a broader employee platform with frontline reach. **You need a branded, customer-facing self-service knowledge base.** If the goal is deflecting support tickets through a polished external help center, the relevant vendors narrow quickly. **Document360** is purpose-built for SaaS customer knowledge bases with strong governance and AI-powered search. **Helpjuice** is the right choice if concierge design support and analytics-driven content management matter more than product depth. **MangoApps** is an internal platform; it does not address this use case. **You are a small team that needs a simple internal wiki with minimal setup.** If the team is under 50 people, the knowledge problem is relatively contained, and there is no IT resource available to manage a full platform implementation, start with **Slab**, **Nuclino**, or **Tettra**. All three have low-cost or free entry tiers, clean editors, and minimal administrative overhead. Tettra is the right pick if the team lives in Slack. Slab is stronger on search across connected tools. Nuclino is the fastest to set up. Each will serve the core need until the organization grows into requirements those tools were not designed to handle. ## What Is Knowledge Management Software? Knowledge management software is a category of tools that help organizations capture, organize, maintain, and surface institutional knowledge so employees can find accurate information when they need it, rather than searching email threads, asking colleagues, or working from outdated documents. The category encompasses a broad range of product types, from structured wikis (organized, editable pages for policies, procedures, and how-to guides) to knowledge bases (categorized article repositories for support or onboarding), to AI-powered knowledge platforms (unified search and chat interfaces that answer questions grounded in company content). What unites them is the underlying goal: replacing the patterns that make organizational knowledge inaccessible: tribal knowledge locked in individual employees' heads, files scattered across drives, and procedures that exist on paper but never reach the people who need them. A useful distinction for buyers: a knowledge base is a content repository where articles and documents are stored. A knowledge management system (KMS) is the broader infrastructure that includes the tools, workflows, governance processes, and access controls that keep knowledge current, verified, and accessible across the organization over time. Most of the platforms in this guide qualify as full KMS products, though they vary considerably in how much governance infrastructure they provide alongside the content storage layer. ## Why Knowledge Management Matters for Your Organization The cost of poor knowledge management is not abstract. According to a [Panopto Workplace Knowledge and Productivity Report covered by HR Dive](https://www.hrdive.com/news/inefficient-knowledge-sharing-costs-large-us-businesses-47m-a-year/527892/), inefficient knowledge sharing costs large US businesses an estimated $47 million per year in lost productivity. The primary drivers are time spent searching for information, time spent recreating knowledge that already exists somewhere, and the delays caused when employees cannot find an answer and wait for a colleague to provide one. For desk-based knowledge workers, this is a productivity problem. For frontline workers, the stakes are higher. A [retail](https://www.mangoapps.com/industries/retail) associate working from an outdated product guide gives incorrect information to a customer. A [manufacturing](https://www.mangoapps.com/industries/manufacturing) technician who cannot find the current safety procedure for a piece of equipment creates a compliance risk. A [healthcare](https://www.mangoapps.com/industries/healthcare) nurse who cannot quickly locate a clinical protocol during a shift handoff creates a patient safety concern. The knowledge problem for deskless workers is not just slower work: it is work done with incomplete or wrong information, with consequences that extend beyond the individual employee's productivity. Organizations with a significant frontline workforce that invest in knowledge management as a desk-only initiative are solving half the problem at best. ## What Features Should I Look for in Knowledge Management Software? The features that matter most depend on what kind of knowledge problem you are actually solving. These are the six areas worth evaluating in any serious KM assessment. - **Structured organization and hierarchy:** Look for wikis, categories, nested pages, and tagging that let teams organize knowledge in a structure that mirrors how work is actually done, not just a flat folder tree. - **Search quality:** A knowledge base is only as useful as its search. Evaluate semantic search (which returns results based on meaning, not just exact keyword matches), the ability to search across content types (documents, wiki pages, videos), and whether search results can be filtered by audience, department, or content type. - **Content governance and freshness controls:** Any tool can store knowledge. Fewer tools enforce that knowledge stays current. Look for content ownership assignment, scheduled verification reminders, expiry dates or review triggers, and version history with rollback capability. - **Access controls and permissions:** Role-based permissions ensure that sensitive knowledge (HR policies, compliance documentation, proprietary procedures) is visible only to the right audiences. For organizations with complex org structures, HRIS-integrated permissions that update automatically as employees change roles are worth evaluating specifically. - **Integration with communication and workflow tools:** Knowledge that surfaces inside the tools employees already use (Slack, Teams, email, a mobile app) gets used more than knowledge stored in a separate system that requires an extra login. Evaluate both inbound integrations (pulling content from connected tools) and outbound delivery (pushing answers into the tools where work is happening). - **Mobile and frontline accessibility:** For any organization with a deskless or frontline workforce, this is not optional. Evaluate whether the mobile app supports offline access, whether shared-device or kiosk modes exist, and whether the platform requires individual corporate email addresses to log in. ## How to Choose the Right Knowledge Management Software The single most important question in a KM evaluation is not "which tool has the best features?" It is "where does knowledge need to go, and who needs to receive it?" A tool that serves desk-based employees well but cannot reach a warehouse floor or a retail store has solved the wrong problem for a mixed-workforce organization. Once you have mapped your actual audience, the evaluation narrows quickly. Organizations with frontline or deskless workers need a platform that can deliver knowledge via mobile, kiosk, or offline access. Organizations whose knowledge problem is exclusively desk-based can evaluate purpose-built tools on feature depth and governance model. Organizations with a mix of internal knowledge needs (employee-facing wikis, HR policies, SOPs) and external knowledge needs (customer self-service, help centers) should consider whether a single platform can serve both audiences or whether two separate tools make more sense. Total cost of ownership deserves more weight than the per-seat sticker price. Factor in the admin overhead of maintaining separate governance workflows, the integration cost of connecting a standalone KM tool to your HRIS and identity provider, and the opportunity cost of employees who cannot find information and either ask a manager or work from what they remember. For organizations already evaluating a broader digital workplace platform, knowledge management as a module within that platform typically carries a lower total cost than a standalone KM tool layered on top. MangoApps is worth evaluating for any organization where frontline reach, unified governance across the employee lifecycle, or the consolidation of multiple point tools (wiki, intranet, communication, training) onto a single platform is part of the business case. The [Adoption Guarantee](https://www.mangoapps.com/success-services) removes the rollout risk that often slows enterprise KM implementations. ## Using knowledge management software for SOPs and policies in regulated industries Knowledge management for regulated work adds a control layer to findability. Standard operating procedures and policies must have an owner, an approval workflow, an effective date, and a version history; superseded versions must be withdrawn from general view but retained for audit; employees the procedure applies to must acknowledge the specific version they read; a change should trigger re-training with completion written back to the employee record; and every step must be exportable for an auditor. Frontline access without corporate email is the requirement most general knowledge bases miss, and it is where SOP compliance usually fails: the document is controlled and invisible on the floor. Evaluate platforms on those criteria as well as the ones above. Where a validated quality management system is mandated, such as under FDA 21 CFR Part 11, the knowledge platform coexists with it as the delivery, search, acknowledgment, and training layer for the floor rather than replacing it. MangoApps combines version control, acknowledgment through Critical Alerts, training assignment by role, and permission-aware AI search on one platform for frontline and desk employees, with HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO per [mangoapps.com/security](https://www.mangoapps.com/security). Statements about other vendors' SOP capabilities should be verified against their current documentation. The full guide is [The Complete Guide to Knowledge Base Software for SOP and Policy Management in Regulated Industries](https://www.mangoapps.com/articles/knowledge-base-software-sop-policy-management-regulated). ## Frequently Asked Questions **What is knowledge management software?** Knowledge management software is a platform that captures, organizes, and surfaces institutional knowledge so employees can find accurate, current information when they need it: rather than relying on email searches, tribal knowledge, or outdated documents. It ranges from simple wikis and knowledge bases to AI-powered platforms that answer questions grounded in company content. **What is the difference between a knowledge base and a knowledge management system?** A knowledge base is a structured repository of articles and documents. A knowledge management system (KMS) is broader: it includes the tools, workflows, and governance processes that keep knowledge current, verified, and accessible across the organization. Most of the platforms in this guide qualify as full KMS products, though they vary significantly in how much governance infrastructure they provide alongside the content storage layer. **What are the four types of knowledge management?** The four types most commonly referenced are explicit knowledge (documented and transferable, such as policies and procedures), tacit knowledge (experiential and personal, such as the judgment a senior employee applies to edge cases), embedded knowledge (knowledge contained in systems, processes, and workflows), and procedural knowledge (step-by-step how-to knowledge). A well-designed KMS helps organizations capture explicit and procedural knowledge at scale, while creating the social and collaboration infrastructure that surfaces tacit knowledge before it walks out the door. **Is SharePoint a knowledge management system?** SharePoint can function as one, but it requires significant configuration, ongoing governance effort, and typically IT-managed administration to act as a true KMS. Most organizations use it as a document repository rather than a governed knowledge system with verification workflows, AI search, and employee-facing delivery. Organizations looking for a dedicated KMS: particularly one that reaches a frontline workforce: typically find purpose-built alternatives easier to adopt and maintain. **What features matter most in knowledge management software?** Search quality and frontline accessibility are the two most frequently underweighted factors. Many evaluations focus on the editor and content organization, which matter, but a knowledge base with poor search or no mobile access will see low adoption regardless of how well content is organized. Content governance controls (verification workflows, expiry dates, ownership assignment) determine whether the knowledge base stays accurate six months after launch. Evaluate those three dimensions before examining UI preferences or integrations. **How much does knowledge management software cost?** Costs range from free for small teams (Notion, Slab, and Nuclino all have free tiers for limited users) to $4 to $25 per user per month for team and mid-market tools (Confluence, Guru, Tettra, Slab), to quote-based enterprise contracts for platforms like Bloomfire, Document360, and MangoApps at scale. Total cost of ownership, including admin overhead and the cost of integrating a standalone tool with your HRIS and identity provider, often matters more than per-seat price at enterprise scale. **What is the best knowledge management software for small businesses?** Slab, Nuclino, and Tettra are strong starting points for small teams. All three have low-cost or free entry tiers, minimal setup requirements, and clean editors. Notion is the most flexible option if the team wants to combine documentation, wikis, and project tracking. Tettra is a natural fit for teams that live in Slack. For small businesses with a frontline workforce, MangoApps is worth evaluating even at smaller headcounts, because the frontline accessibility gap in lighter tools does not close as the organization grows. **Can knowledge management software work for frontline workers who don't have a company laptop or email address?** Most KM tools in this guide cannot reach them. Confluence, Notion, Guru, Tettra, Slab, Helpjuice, and Nuclino are all built for desk workers and require individual accounts tied to a corporate email address. MangoApps is specifically designed for this gap, delivering knowledge via mobile app, kiosk view, and shared-device access with offline capability and auto-translation for multilingual teams. For organizations where reaching the floor is part of the KM requirement, this distinction is the most important one in the evaluation. **How long does it take to implement a knowledge management system?** For smaller teams using lightweight tools, basic setup takes days. Enterprise implementations with HRIS integration, RBAC configuration, content migration from legacy systems, and governance workflow setup typically take six to twelve weeks for the initial rollout, with a longer runway to full content maturity. MangoApps offers an [Adoption Guarantee](https://www.mangoapps.com/success-services) that structures the rollout and provides adoption support, addressing the most common point at which enterprise KM implementations stall. **What is the difference between a wiki and a knowledge management system?** A wiki is a type of content repository where pages can be collaboratively edited and organized. A knowledge management system includes wiki functionality but adds the governance infrastructure: verification workflows, expiry controls, audit trails, access permissions, and AI-powered search: that keeps a wiki accurate, findable, and trustworthy at scale. Most teams that start with a wiki outgrow it once content volume and organizational complexity increase to the point where finding and trusting information requires more than good URL hygiene. **Which knowledge management software is best for SOPs and policies in regulated industries?** The software that delivers the current controlled version to every employee it applies to, including employees with no corporate email, and evidences that they read it: version control with approval and effective dates, acknowledgment tied to the version, training linkage, permission-aware search, and audit export. MangoApps combines these on one platform for frontline and desk staff; general knowledge bases such as Confluence, Notion, Guru, and Document360 serve knowledge workers well and typically rely on integrations for frontline access and per-employee acknowledgment; a validated quality management system remains the regulated system of record where one is mandated. See [The Complete Guide to Knowledge Base Software for SOP and Policy Management in Regulated Industries](https://www.mangoapps.com/articles/knowledge-base-software-sop-policy-management-regulated). --- # 8 Signs Your Frontline Organization Has Outgrown Its Employee Intranet **Author:** Andy Tolton **Published:** 2026-06-08 **Category:** intranet The operational, communication, mobile-access, and governance signals that tell HR, operations, and internal communications leaders a frontline intranet is failing, and what to do about each. > **Quick answer:** A frontline organization has outgrown its employee intranet when the people who run its stores, wards, plants, and routes cannot use it: sign-in needs a corporate email most of them do not have, weekly active use sits below 60% or is unknown by location, managers re-broadcast posts over text, search returns documents instead of answers, the intranet does nothing during a shift, language and shift barriers go unaddressed, nobody owns the content and acknowledgment lives on paper, and the platform cannot scale to new sites, languages, acquisitions, or AI. Three or more signs in one area means it is time to evaluate a frontline-first platform. The intranet did its job. For years it gave the head office a home page, a policy library, and a place for the CEO's quarterly note. Then the organization grew to 300 locations and 8,000 hourly employees, and the intranet stayed where it was: behind a corporate login, on a desktop, written for people with an inbox. "Outgrown" is the honest word for what happened. The platform was not built for the workforce the company now has. Deskless workers make up 70 to 80% of the global workforce, about 2.7 billion people, according to [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology), and 58% of American workers are on the frontline, according to [JLL](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention). Yet only 13% of employees use their intranet daily and 31% never do, according to [Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics), and the intranet is the main source of company information for just 39% of desk-based employees in the United States, according to [Staffbase's 2025 International Employee Communication Impact Study](https://staffbase.com/blog/employee-communication-impact-study-2025). This article is for the HR, operations, and internal communications leaders who suspect their intranet is one of those numbers. It gives you eight signs, a two-minute self-assessment, and a clear path for what to do next, whether that is fixing adoption on the platform you have, replacing it, or making a larger platform decision. ## How do frontline organizations know they need a better employee intranet? They know when the intranet's numbers and the frontline's behavior disagree. The dashboard says 4,000 users; the store manager is photographing the schedule and posting it to a group chat. The policy library says version 9 is current; the night shift is following version 6 from a binder. The launch email said "company-wide"; 2,100 employees never received it because they were never issued an inbox. The eight signs below group into four areas. Run the quick test in each row before reading on. | Area | Signs | Quick test | Benchmark | |---|---|---|---| | Reach | 1, 3 | Can a new store associate sign in on day one without a corporate email? | Deskless workers are 70 to 80% of the global workforce ([BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology)) | | Adoption and utility | 2, 5 | What is weekly active use, by location? | 60% weekly active users is a successful intranet; 85% weekly login is best practice ([Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics)) | | Findability | 4, 6 | What is the search success rate, and in which languages? | 75% minimum search success ([Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics)); employees spend under six minutes a day on the intranet ([SWOOP Analytics](https://www.swoopanalytics.com/sharepoint-bm-25)) | | Governance and scale | 7, 8 | Who owns this policy, when was it reviewed, and can you export who acknowledged it? | Acknowledgment records should be exportable; adding a site should not be an IT project | ## The 8 signs ### Sign 1: Frontline staff need a corporate email to log in **What it looks like on the floor.** The onboarding checklist says "log in to the intranet." The new associate does not have an email address and never will. The manager shrugs and prints the handbook. **Why it happens.** Legacy intranets were built behind single sign-on tied to a corporate account. That model fits the 20 to 30% of employees at a desk and locks out everyone else. **The number.** In the United States the intranet is the main source of company information for only 39% of desk-based employees, against 61% in Germany ([Staffbase](https://staffbase.com/blog/employee-communication-impact-study-2025)). That figure covers desk staff. For frontline staff without an account, reach is effectively zero. **What it costs.** Every policy update becomes a manual process; every safety notice depends on a manager relaying it; and nothing is recorded. **The fix.** Issue identity from the HR system rather than the email system, and let workers sign in by SMS, QR code, or employee ID on a personal phone or shared kiosk. See [9 Modern Employee Intranet Features That Reach Frontline Staff Without Email](https://www.mangoapps.com/articles/intranet-features-that-reach-frontline-workers). ### Sign 2: Adoption stalled at launch and nobody can say the number by location **What it looks like.** The launch report showed 62% of employees "onboarded." Nobody has looked since. Asked for weekly active users at the Phoenix distribution center, the intranet team cannot answer. **Why it happens.** Adoption was measured as a company average, and averages hide the sites that never started. Legacy intranets typically settle at 30 to 40% adoption (MangoApps customer data), skewed toward desk staff. **The number.** Only 13% of employees use their intranet daily and 31% never do ([Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics)). **The fix.** Measure weekly active users, acknowledgment rates, and search success by location and shift, and fix the bottom quartile first. The playbook is in [How to Increase Frontline Intranet Adoption Without Sacrificing Governance or Compliance](https://www.mangoapps.com/articles/frontline-intranet-adoption-governance-compliance) and [How to Improve Frontline Intranet Adoption in 2026](https://www.mangoapps.com/articles/improve-frontline-intranet-adoption-2026). ### Sign 3: Managers re-broadcast intranet posts over text and WhatsApp **What it looks like.** Corporate publishes the recall notice on the intranet. The regional manager screenshots it and sends it to 40 store managers by text. They forward it to their teams in group chats. Nobody knows who read it. **Why it happens.** The intranet does not reach the people the message is for, so the managers build a shadow channel that does. Before A.S. Watson Benelux deployed MangoApps, Kruidvat store schedule changes circulated exactly this way, as WhatsApp photos, and managers spent their days answering questions from employees who had missed or deleted them. **What it costs.** The least compliant outcome available: nothing logged, nothing retained, no proof of receipt. **The fix.** Target by role, location, and shift, require acknowledgment on the messages that matter, and give managers a view of who has not seen them. See [The Complete Guide to Frontline Communication Platforms](https://www.mangoapps.com/articles/frontline-communication-platforms-guide). ### Sign 4: Search returns documents, not answers **What it looks like.** An associate types "how do I request time off" and gets twelve PDFs, three of them outdated. She asks her manager instead. **Why it happens.** Keyword search over an ungoverned library. When the first search fails, people stop trying, which is one reason employees spend under six minutes a day on their intranet ([SWOOP Analytics, 2025](https://www.swoopanalytics.com/sharepoint-bm-25)). **The number.** Social Edge Consulting sets a 75% minimum search-success benchmark. Most organizations do not know theirs. **The fix.** AI search grounded in the company's own policies that returns the answer, its source, and nothing the user is not permitted to see. See the search section of [The Complete Guide to Intranet Best Practices and Evaluating Enterprise Intranet Platforms](https://www.mangoapps.com/articles/the-complete-guide-to-intranet-best-practices). ### Sign 5: The intranet does nothing during a shift **What it looks like.** The schedule is in one app, the pay stub in another, the checklist on paper, the training on a desktop in the back office. The intranet has news. Nobody opens news on a Tuesday afternoon. **Why it happens.** The intranet was designed as a destination for reading, not a tool for working. Without a daily reason to open it, it becomes optional, and optional loses. **The number.** Only 23% of frontline workers believe they have access to the technology they need to be productive, according to [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html), and the same research estimates productivity rises about 22% when they get the right mix. **The fix.** Put the schedule, shift swaps, pay, tasks, and PTO in the same app as the news. Communication rides along with utility. See [The Best Employee Apps for Hourly and Frontline Workers](https://www.mangoapps.com/articles/best-employee-app-software). ### Sign 6: Language and shift barriers go unaddressed **What it looks like.** The safety policy exists in English. Thirty percent of the plant speaks Spanish. The night shift receives announcements timed for the day shift and reads them a day late, if at all. **Why it happens.** The intranet was published from one time zone in one language for one kind of employee. **The fix.** Automatic translation of posts, comments, and policies; targeting by shift; text-to-speech and plain-language versions of the policies that matter most. Translated policies should be versions of the master, not separate documents with separate owners. ### Sign 7: Nobody owns the content and acknowledgment lives on paper **What it looks like.** Two versions of the attendance policy are live. The sign-off sheet for the new safety procedure is taped to the time clock. When the auditor asks who acknowledged version 9, someone goes looking for the sheet. **Why it happens.** Content governance was never set up as structure: owners, review dates, expiry, versioning, acknowledgment records. IT cannot keep the platform current, and nobody else was asked to. **What it costs.** Trust. Employees who find a stale policy once stop trusting the intranet for anything. And the compliance record does not exist. **The fix.** Owners and review dates on every item, one current version with history, mandatory acknowledgment tied to the version, and exportable records. Governance implemented this way raises adoption rather than lowering it; the argument is in [How to Increase Frontline Intranet Adoption Without Sacrificing Governance or Compliance](https://www.mangoapps.com/articles/frontline-intranet-adoption-governance-compliance). ### Sign 8: The platform cannot scale to new sites, languages, acquisitions, or AI **What it looks like.** Each new location is an IT project. The acquired brand needs a second intranet. Turning on an AI assistant is blocked because nobody can say which documents it would read. **Why it happens.** The intranet was built as a site, not as a platform with one identity, one employee record, and one permission model. Everything added on top inherits the fragmentation. **The number.** The average company runs 101 applications, and companies with more than 5,000 employees average 131 ([Okta, Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/)). Workers toggle between applications roughly 1,200 times a day ([Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications)). An intranet that adds to those numbers rather than subtracting from them has been outgrown. **The fix.** Make the platform decision before the next tool decision. See [What "Platform" Should Actually Mean](https://www.mangoapps.com/articles/what-platform-means) and [Why the Platform Decision Comes Before the App Decision](https://www.mangoapps.com/articles/platform-decision-first). ## Why do companies struggle with frontline employee intranet adoption? Five causes account for most failed frontline intranet rollouts, and the eight signs above are their symptoms. Access is gated on a corporate email most frontline workers do not have. The intranet has no daily utility because schedules, pay, and tasks live elsewhere. Search returns documents instead of answers, so employees ask a manager. Managers were never enabled or made accountable, and frontline adoption runs through the manager. And adoption is measured in aggregate, which hides the sites that never started. None of these is "employees don't like technology." Each is a design choice that fit a desk-based workforce and does not fit the one most organizations actually have. For the full diagnosis of a failing rollout, read [12 Reasons Frontline Intranet Adoption Fails (And How to Fix Each One)](https://www.mangoapps.com/articles/frontline-intranet-adoption-failures). For the fix, read the [adoption and governance guide](https://www.mangoapps.com/articles/frontline-intranet-adoption-governance-compliance). ## What outgrown costs | Sign | Operational cost | Data point | |---|---|---| | 1, 3 | Unofficial channels carry official information; no record of receipt | Deskless workers are 70 to 80% of the workforce ([BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology)) | | 2, 5 | Managers answer questions the app should answer; turnover rises | 53% of deskless workers feel burned out and 43% are actively looking ([BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology)); replacing an employee costs one-half to two times annual salary ([Gallup](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx)) | | 4, 6 | Time lost, policies followed from memory | Under six minutes a day on the intranet ([SWOOP Analytics](https://www.swoopanalytics.com/sharepoint-bm-25)) | | 7 | Compliance exposure; eroded trust | Employees with a positive employee experience are 68% less likely to consider leaving ([SHRM](https://www.shrm.org/about/press-room/employees-with-a-positive-employee-experience-are-68--less-likel)) | | 8 | Every new site, brand, or AI initiative rebuilds identity and permissions | 101 applications per company; 131 at 5,000+ employees ([Okta](https://www.okta.com/newsroom/articles/businesses-at-work-2025/)) | Engagement is the summary number. Global engagement fell to 20% in 2025, and [Gallup](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) estimates low engagement cost the world economy roughly $10 trillion, or 9% of GDP. An intranet the frontline cannot use is one of the reasons. ## What to do next: fix, replace, or re-platform Count your signs. Then pick the path that matches them. **Fix adoption on the platform you have** if most of your signs sit in adoption and utility (2, 5) and your platform can already reach frontline staff without corporate email. Start with [How to Improve Frontline Intranet Adoption in 2026](https://www.mangoapps.com/articles/improve-frontline-intranet-adoption-2026) and the [90-day plan in the adoption and governance guide](https://www.mangoapps.com/articles/frontline-intranet-adoption-governance-compliance). **Replace the intranet** if your signs sit in reach and findability (1, 3, 4, 6) and the platform cannot be configured out of them. [How to Replace an Outdated Intranet in 2026](https://www.mangoapps.com/articles/how-to-replace-an-outdate-intranet-in-2026) lays out a four-phase process, from defining the failure scope to migrating in increments. **Make the platform decision** if sign 8 is present at all. A new intranet that is still a site will be outgrown again. Use the [10 evaluation criteria](https://www.mangoapps.com/articles/the-complete-guide-to-intranet-best-practices), the [frontline buyer's framework](https://www.mangoapps.com/articles/how-to-choose-frontline-intranet-2026), and the [25-platform comparison](https://www.mangoapps.com/articles/top-25-intranet-platforms-frontline-desk-workers), and download the [2026 Intranet Buyer's Guide for a Frontline Workforce](https://www.mangoapps.com/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) for the scorecard and RFP template. ## Where MangoApps fits MangoApps is the AI-Ready Employee Platform for the Frontline: one app for frontline and desk employees, with no corporate email required, that carries communications, knowledge, schedules, tasks, training, and HR self-service on one identity and one employee record. Content has owners, versions, and acknowledgment records; AI search answers only from what the user can open. MangoApps holds HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO, and backs deployments with an [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee) of 90%+ active adoption within 90 days, against the 30 to 40% legacy intranets typically reach. Learn more about the [MangoApps modern intranet](https://www.mangoapps.com/solutions/modern-intranet). ## Frequently asked questions **How do frontline organizations know they need a better employee intranet?** When the intranet's numbers and the frontline's behavior disagree: sign-in requires a corporate email most workers lack, weekly active use is below 60% or unknown by location, managers re-broadcast posts by text, search returns documents instead of answers, the intranet does nothing during a shift, language and shift barriers are unaddressed, content has no owner, and adding a site or turning on AI is a project. Three or more signs in one area is the signal. **Why do companies struggle with frontline employee intranet adoption?** Because the intranet assumes an inbox and a laptop most frontline workers do not have, offers nothing they need during a shift, fails at search, was never made the manager's channel, and is measured as a company average that hides zero-adoption sites. Only 13% of employees use their intranet daily and 31% never do, according to Social Edge Consulting. **What is a good intranet adoption rate?** Social Edge Consulting benchmarks 60% weekly active users as a successful intranet and 85% weekly login as best practice. Legacy intranets typically reach 30 to 40%. MangoApps customers average more than 90% within 90 days. Measure by location, not in aggregate. **What are the warning signs an intranet is failing internal communications?** Managers relaying posts by text or group chat, safety and policy acknowledgment tracked on paper, announcements published in one language and one time zone, and leadership communicating by email to a workforce that mostly has no inbox. **Should we fix our intranet or replace it?** Fix it if the platform can already reach frontline staff without corporate email and your gaps are adoption and content. Replace it if the platform cannot be configured to reach them. Make a broader platform decision if adding sites, brands, or AI requires rebuilding identity and permissions each time. **How long does it take to replace an intranet?** A packaged platform with vendor-led migration can run a 90-day plan from identity setup through pilot launch and regional expansion. Heavily customized deployments take longer. The four-phase process is in How to Replace an Outdated Intranet in 2026. **What is the difference between an intranet problem and having outgrown the intranet?** A problem is something the current platform can fix with configuration, content, or change management. Outgrown means the platform's design no longer fits the workforce: it cannot reach staff without corporate email, cannot carry the daily work, or cannot scale to new sites, languages, and AI without a rebuild. ## Sources - BCG, [Facing the Deskless Labor Shortage with Technology](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) (2024) - JLL, [Leading practices for frontline workforce engagement and retention](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention) (2025) - Staffbase, [2025 International Employee Communication Impact Study](https://staffbase.com/blog/employee-communication-impact-study-2025) - Social Edge Consulting, [Top 12 Intranet KPIs and Metrics](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) (2025) - SWOOP Analytics, [2025 SharePoint Intranet Benchmarking Report](https://www.swoopanalytics.com/sharepoint-bm-25) - Deloitte, [Frontline Worker Productivity Enabled by Technology](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html) - Okta, [Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/) - Harvard Business Review, [How Much Time and Energy Do We Waste Toggling Between Applications?](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) (2022) - Gallup, [State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx); [This Fixable Problem Costs U.S. Businesses $1 Trillion](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) (2019) - SHRM, [Employees With a Positive Employee Experience Are 68% Less Likely to Consider Leaving](https://www.shrm.org/about/press-room/employees-with-a-positive-employee-experience-are-68--less-likel) --- # Internal Communications Governance: Why Reach Isn't Enough **Author:** MangoApps Team **Published:** 2026-06-07 **Category:** safety-compliance A logistics coordinator sends what she thinks is a targeted safety update to the overnight crew at her distribution center. She selects the right template, types the message, hits send. # Internal Communications Governance: Why Reach Isn't Enough A logistics coordinator sends what she thinks is a targeted safety update to the overnight crew at her distribution center. She selects the right template, types the message, hits send. Within four minutes, her phone starts buzzing. Employees at two other facilities — in different states, on different schedules — are asking their supervisors what the safety concern is and whether their shifts are affected. The update was irrelevant to them. But it looked urgent. Now there are a hundred confused conversations happening in parallel, and her supervisor wants to know why she sent a facility-specific notice to 1,800 people. The coordinator didn't make a technical mistake. She did exactly what the system allowed. The problem is that most internal communications platforms were built to answer one question: how do we reach everyone? They were never designed to answer the harder one: how do we make sure the right message gets to the right people in a way that people actually trust? This week's releases across MangoApps converge on exactly that question. --- ## The Case for Guardrails There's a version of "move fast" that works in external marketing — if a social post goes slightly off-brand, you catch it, fix it, move on. Internal communications with a frontline workforce doesn't work that way. A poorly framed safety alert doesn't just get ignored; it actively erodes the credibility of the next one. An executive message that bypasses editorial judgment and lands inconsistently across departments creates more confusion than silence. The new [Enforced Broadcast Approval Workflows](https://www.mangoapps.com/changelog/3012) puts a hard gate in front of that. Admins can now require sign-off before any broadcast goes live. Non-admin senders can't publish or schedule without an approved request. This isn't bureaucracy for its own sake — it's the same principle that makes legal and finance departments require multiple approvals before external commitments. Important messages deserve the same rigor. A parallel gap also closed this week: [broadcast posts now flow through Content Moderation](https://www.mangoapps.com/changelog/3014) when "Moderate All Content" is enabled. Previously, broadcasts were exempt — a category of message that was simultaneously the most visible and the least governed. That's now fixed. Every communication channel is subject to the same moderation standard. Together, these two changes reflect a shift in how organizations think about internal publishing: not as a fire-and-forget action, but as something worth standing behind. --- ## Precision Is a Safety Feature Alert fatigue is one of the least-discussed risks in frontline workforce management. It doesn't show up in a compliance audit. It doesn't trigger a Workday ticket. But it builds silently over months, and it becomes dangerous when a real emergency lands in an inbox that has learned to treat every urgent notification as probably-not-urgent. The scenario plays out in hospitals, manufacturing plants, retail chains, and logistics networks alike: too many alerts, too broadly targeted, too frequently. Employees develop a learned indifference. Then something actually critical comes in. [Attribute-Based Audience Targeting for Emergency Alerts](https://www.mangoapps.com/changelog/3012) addresses this directly. Emergency alerts now support the same rich targeting as broadcasts — department, location, job title, role, named groups, or specific individuals — with a live recipient-reach preview before anything is sent. You can see, before you commit, exactly how many people will receive the alert and whether the scope makes sense. This matters most at the moment it's hardest to think clearly. An emergency communications system that forces precision when someone is reacting to a real incident is a system designed for the real use case, not the hypothetical one. The companion release — [Emergency Alert Templates with full admin CRUD](https://www.mangoapps.com/changelog/3013) — addresses the other common failure mode: messages that go out with the wrong audience, the wrong channel, or critical fields left blank because someone was composing from scratch under pressure. Pre-composed templates with the right audience and channels already configured don't just save time; they remove a category of human error from the highest-stakes moment in your communications workflow. --- ## Who Speaks for the Organization The governance gap in internal communications isn't only about what gets sent — it's about who speaks with authority, and how employees know which voices to trust. This week's [News Feed Redesign](https://www.mangoapps.com/changelog/3015) introduces two structural answers to that question. Admins can now pin posts and assign Subject Matter Experts to managed topics. When employees navigate to a topic — safety policies, benefits updates, IT announcements — they can see who the designated expert is, and they can distinguish official managed content from organic conversation. The difference between "what someone posted" and "what the organization stands behind" is now visible in the UI. The tabbed feed structure (six categories, infinite scroll, audience targeting with live post counts) also does something more subtle: it gives organizations control over information architecture, not just content. You can shape how employees encounter information, not just what they see when they happen to scroll past it. [Ballots](https://www.mangoapps.com/changelog/3014) extends the trust principle into formal decision-making. Organizations now have a structured, auditable way to run workforce votes — Yes/No resolutions, multi-candidate elections — with a frozen voter roster, auto-resolution, and a complete audit history. This is meaningful for organizations where governance matters: union environments, co-ops, boards of advisors, any context where decisions need to be documented and unimpeachable. The informal poll in a chat message and the formal organizational vote now have different tools to match their different stakes. None of this removes the informal, human layer of internal communication. It adds a distinction that most platforms collapse: some things the organization says, and some things employees say, and those two categories deserve different treatment. --- ## Closing the Loop Governance without visibility is incomplete. You can add approval workflows and moderation queues, but if nobody knows whether messages are actually landing — or what employees think about them — you're governing a black box. The [News Feed Signals Dashboard](https://www.mangoapps.com/changelog/3010) and [News Feed Analytics](https://www.mangoapps.com/changelog/3011) close that loop. Managers and admins can now see AI-classified signals surfaced from employee posts and comments — questions, risks, ideas, issues, decisions, action items, sentiment — with filtering, status tracking, and links back to source content. The analytics layer adds sentiment trend charts, Must-Read engagement metrics, and role-based segment filtering for frontline managers. This is where governance becomes strategy. An approval workflow tells you what went out. Audience targeting tells you who received it. Analytics and signals tell you whether it worked, and what employees actually think. That feedback loop is what separates a communications system from a communications platform. --- The organizations that lead on frontline workforce outcomes — lower turnover, higher compliance rates, faster response to operational issues — consistently outperform on one variable that doesn't get enough credit: employees trust what they're told. That trust isn't accidental. It's the product of consistent, well-governed communications. It comes from knowing that urgent alerts are actually urgent. That managed topics reflect authoritative information. That formal decisions are documented and final. That the company says what it means and means what it says. The features that shipped across MangoApps this week don't look like a single initiative — broadcast workflows, moderation, audience targeting, SME assignments, ballots, analytics. But they are, underneath, the same investment: building the infrastructure that turns a communications platform into something employees can actually trust. Reach was always the easy problem. Trust is the hard one, and it's the one that matters. --- # The Best Talent Acquisition Software for Frontline Workforces in 2026 **Author:** MangoApps Team **Published:** 2026-06-04 **Category:** comparisons Discover the best talent acquisition software for frontline workers available in 2026, compare top options, and find the right fit for your organization. Hiring frontline, hourly, and shift-based workers operates on a different set of constraints than corporate recruiting: roles must be filled in days, not weeks, most applicants apply by phone rather than desktop, and the best candidates are often off the market within 48 hours of applying. The data bears this out: a significant share of frontline candidates abandon applications before completing them, and roughly a third disengage before the interview stage. This guide evaluates the platforms built for that reality, covering mobile application flows, automated screening and scheduling, and clean handoffs into onboarding and the workforce, so frontline HR leaders and operations managers can match the right tool to their volume, industry, and tech stack. Software Best For Workforce Fit Platforms MangoApps Integrated hiring-to-onboarding for distributed frontline workforces on one platform Frontline, deskless, hourly, multi-location Web, iOS, Android, Desktop Fountain High-volume frontline hiring at enterprise scale with native compliance and voice AI Gig, logistics, retail, healthcare, hospitality Web, iOS, Android Paradox (Olivia) Conversational AI hiring that moves candidates from application to hired offer in minutes QSR, retail, healthcare, hospitality Web, iOS, Android Workstream Hourly hiring, payroll, and scheduling combined for multi-location QSR and retail teams QSR, franchise, retail Web, iOS, Android Harri Vertically integrated hiring and workforce management built for hospitality and restaurant operations Restaurants, hotels, hospitality Web, iOS, Android Phenom AI-driven high-volume hiring with career site personalization for large enterprise organizations Retail, healthcare, manufacturing, hospitality Web + mobile candidate access iCIMS Enterprise ATS with a dedicated frontline AI hiring module for large, multi-industry workforces Large enterprise, multi-industry frontline Web, iOS, Android Grayscale SMS text-recruiting automation that layers on top of an existing ATS without replacing it Retail, logistics, healthcare, transportation Web, iOS, Android Hireology Multi-location hourly ATS with transparent published pricing for franchise and distributed operators Healthcare, automotive, hospitality, retail Web, iOS, Android Deputy Shift-work platform with a built-in hourly ATS for a direct hire-to-first-shift path Retail, hospitality, healthcare, food service Web, iOS, Android UKG (Rapid Hire) Enterprise HCM with a native frontline hiring module for organizations standardized on UKG Large enterprise, multi-location frontline Web, iOS, Android MangoApps 4.6/5 Stars · Gartner Peer Insights 2M+ Users · Trusted Worldwide Gartner MQ Visionary · Intranet Packaged Solutions (2025) IDC MarketScape Leader · Employee Experiences (2024) Forrester Wave Strong Performer · Intranet Platforms (Q2 2026) Reworked IMPACT Award (Gold) · Intranet & Communications Platforms Most frontline hiring breaks at the handoffs: the ATS doesn't talk to the HRIS, the HRIS doesn't talk to scheduling, and a new hire shows up on day one to a pile of paperwork with no context. MangoApps is [The Enterprise Workforce Platform Built for the Frontline](https://www.mangoapps.com/), and its [Talent Acquisition Suite](https://www.mangoapps.com/solutions/talent-acquisition) runs the full hiring workflow on a single shared employee record, from approved headcount through the first 90 days, so nothing falls between systems. For frontline employers managing high turnover across distributed locations, that continuity changes what a completed hire actually means: a new associate who shows up ready to work, not one who quits in week two because onboarding was disorganized. Because the hiring workflow sits inside the same platform as scheduling, workforce management, HR operations, and daily frontline communications, a candidate's information doesn't need to be re-entered when they accept an offer. Their profile flows automatically into onboarding, their first schedule, and their employee app, accessible on the phone they already carry, with no corporate email or VPN required. The [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee) and 98% customer retention rate reflect a partnership model designed to make that end-to-end continuity real for organizations at scale, not just in a demo. **Key capabilities:** - **[Job Board](https://www.mangoapps.com/directory/app/job-board):** Branded career page with mobile-optimized external and internal job listings, LinkedIn Easy Apply, AI-generated job postings, custom application forms, and an employee referral program with bonus tracking, so candidates apply the way they actually live, and your existing workforce is part of the sourcing strategy. - **[Recruiting Agent](https://www.mangoapps.com/directory/app/ai-agent-recruiting):** AI-powered resume parsing, fit scoring with configurable weights, automated candidate outreach, and built-in bias guardrails with PII masking, which screens high volumes without burying recruiters in manual triage, with attribution and confidence metadata on every recommendation. - **[Interview Scheduler](https://www.mangoapps.com/directory/app/interview-scheduler):** Automated interview scheduling with candidate self-service booking, confirmation reminders, and no-show reduction built in, eliminating the back-and-forth that costs days in hourly hiring timelines. - **[Onboarding Hub](https://www.mangoapps.com/directory/app/onboarding-hub):** Role-specific day-one experience pages that trigger automatically when an offer is accepted, with [eSignature](https://www.mangoapps.com/directory/app/esignature) for offer letters and new hire documents, [background check](https://www.mangoapps.com/directory/app/background-checks) integration, and a New Hire Tracker that automates notifications across HR, IT, and location operators, so a clinician, a store associate, and a shift supervisor each get exactly what they need on day one. - **[Headcount Planner](https://www.mangoapps.com/directory/app/headcount-planner):** Connects approved headcount to the job board automatically, so open requisitions don't require a manual handoff between workforce planning and recruiting. **Free version:** No **Pricing:** Modular, quote-based; contact for enterprise pricing **Platforms:** Web, iOS, Android, Desktop [Schedule a demo to see MangoApps in action](https://www.mangoapps.com/schedule-a-call) ## Fountain Fountain is a purpose-built platform for high-volume frontline hiring, designed around the reality that most hourly candidates apply by phone, don't have a resume, and expect to hear back the same day. It covers the full pre-hire workflow, covering job posting through signed offer, with text and SMS apply, a 24/7 AI voice recruiter for automated screening, and native I-9/E-Verify processing so compliance doesn't require a separate system. Fountain operates in 78 countries and serves employers across logistics, retail, healthcare, hospitality, and on-demand work. Its scope is intentionally focused on recruiting: organizations will also need separate WFM, scheduling, and payroll tools, and the data handoff between Fountain and those systems is an integration point to plan for during implementation. For employers with large, established HR tech stacks who need strong high-volume hiring speed rather than a consolidated platform, that trade-off is generally worthwhile. **Best for:** Enterprise and high-growth employers with 500+ annual frontline hires who prioritize speed-to-offer and are comfortable running Fountain alongside an existing WFM and payroll stack. **Consider alternatives if:** You need hiring, scheduling, and payroll in a single platform, or if your annual hire volume doesn't support enterprise ATS pricing. - Text and SMS apply with no account creation or resume required, designed for candidates applying from a personal phone during a commute or break - Fountain AI Recruiter for 24/7 voice-based screening that qualifies candidates without human intervention, with configurable knockout questions and bias guardrails - Native I-9/E-Verify and onboarding compliance processing built in, so document collection and verification happen inside the platform without a separate tool **Free version:** No **Pricing:** Enterprise, quote-based; contact for pricing **Platforms:** Web, iOS, Android [Explore Fountain](https://www.fountain.com/) ## Paradox (Olivia) Paradox built its platform around one core workflow: take an hourly candidate from initial interest to a signed offer in minutes, with no human recruiter required at any stage. Its conversational AI assistant, Olivia, handles screening, interview scheduling, and offer paperwork via SMS, WhatsApp, WeChat, and Facebook Messenger, meeting candidates wherever they already communicate. Workday completed its all-cash acquisition of Paradox in October 2025, which has procurement implications buyers should weigh: as of mid-2026, Paradox continues to operate as a standalone product, but buyers should clarify the long-term licensing roadmap before committing, particularly if they are not currently on Workday. For organizations already in the Workday ecosystem, Paradox integrates as a natural extension of Workday Recruiting; for those outside it, the acquisition is a factor alongside the platform's genuine strength in conversational frontline hiring. **Best for:** High-volume QSR, retail, and healthcare operators that need to move large numbers of hourly candidates from application to offer rapidly, and organizations already on Workday evaluating an integrated conversational ATS. **Consider alternatives if:** Vendor-agnostic standalone licensing is a requirement and long-term roadmap independence from Workday is a concern. - Conversational screening and scheduling across SMS, WhatsApp, Messenger, and web chat, with no app download or email address required from the candidate - Automated interview scheduling with confirmation messages and reminders, designed to cut no-show rates in hourly hiring without recruiter follow-up - Mobile offer acceptance and new-hire onboarding paperwork, keeping the full candidate-facing process on their phone from first contact through day one **Free version:** No **Pricing:** Enterprise, quote-based; contact for pricing **Platforms:** Web, iOS, Android [Explore Paradox](https://www.paradox.ai/) ## Workstream Workstream combines hourly hiring, payroll, and scheduling for multi-location teams, with a particular focus on QSR and retail franchise operations. Unlike standalone ATS platforms, it keeps a single employee record from application through the first paycheck, which reduces re-entry and gives location operators a consistent view of new hires across all sites. Text-to-apply via QR code and AI-powered voice and video screening are available in multiple languages, which matters for frontline workforces where applicants don't all share the same primary language. Its bundled model is a strength for operators who want to consolidate vendors, but it also means the implementation scope is larger than a dedicated ATS; buyers replacing separate hiring, payroll, and scheduling tools should budget accordingly when evaluating timelines and costs. **Best for:** Multi-location QSR and franchise operators, particularly those with 10 to 500+ locations, who want to consolidate hiring, payroll, and scheduling into one vendor rather than managing separate systems. **Consider alternatives if:** Your primary vertical is outside QSR and retail, or if you only need a recruiting tool without replacing your existing payroll and scheduling systems. - Text-to-apply and QR-code apply for candidates who apply on a personal phone, with no desktop or email required - VoiceAI and VideoAI screening available in multiple languages, with 24/7 availability for candidates applying outside standard business hours - Unified data model from application through payroll, so one employee record eliminates manual re-entry between the ATS, onboarding, and payroll systems **Free version:** No **Pricing:** Enterprise, quote-based; contact for pricing **Platforms:** Web, iOS, Android [Explore Workstream](https://www.workstream.us/) ## Harri Harri is a workforce platform built specifically for the hospitality industry, covering restaurants and hotels from hiring through scheduling and labor compliance. Its recruiting module includes a conversational hiring assistant called Carri that engages candidates across SMS, web chat, and Facebook Messenger, and the ATS connects directly into Harri's scheduling and labor management tools. The vertical depth is the core differentiator: Harri ships role templates, compliance workflows, and scheduling logic specific to restaurant and hotel operations rather than adapted from a generic platform. That same depth is also its scope boundary: Harri is not designed for healthcare, manufacturing, logistics, or other frontline sectors, and buyers outside hospitality should evaluate more flexible platforms instead. **Best for:** Restaurant groups, hotel chains, and hospitality operators who want a native workforce platform covering hiring through scheduling, built around the specific requirements of the hospitality business. **Consider alternatives if:** Your operations extend outside hospitality, or if you need a platform that can serve multiple industries across a diversified workforce. - Hospitality-specific ATS with role templates and hiring workflows built for restaurant and hotel positions, not adapted from a generic recruiting system - Carri conversational hiring assistant across SMS, web chat, and Facebook Messenger, automating initial candidate engagement without recruiter involvement - End-to-end hire-to-schedule workflow with onboarding documentation and labor compliance built into the same platform as scheduling and time management **Free version:** No **Pricing:** Enterprise, quote-based; contact for pricing **Platforms:** Web, iOS, Android [Explore Harri](https://harri.com/) ## Phenom Phenom's High-Volume Hiring product targets large enterprise organizations filling significant numbers of hourly and frontline positions in retail, healthcare, manufacturing, and hospitality. It pairs AI candidate matching with a personalized career site experience that surfaces relevant openings based on skills and location, and its Voice Screening Agent handles automated phone screens without recruiter involvement. Phenom is an enterprise talent experience platform: the High-Volume Hiring module sits alongside separate products for corporate ATS, CRM, and internal mobility, making it well-suited for large organizations that need a unified talent platform covering both corporate and frontline populations. For buyers who only need a dedicated frontline ATS without broader platform scope, the implementation complexity and pricing model may exceed what the use case requires. **Best for:** Large enterprise organizations (typically 1,000+ employees) that need to manage both corporate and high-volume frontline hiring in a single AI-driven talent platform. **Consider alternatives if:** You need a standalone frontline ATS without enterprise platform complexity, or if your organization is below the scale where a full talent experience platform investment is justified. - AI chatbot and career-site personalization matching candidates to relevant openings based on skills, location, and role type, increasing relevant applicant flow - Voice Screening Agent for automated conversational phone screens available outside business hours, without requiring recruiter availability - AI interview scheduling with embedded video assessment options, enabling structured pre-hire evaluation at high application volume **Free version:** No **Pricing:** Enterprise, quote-based; contact for pricing **Platforms:** Web (recruiter portal); mobile access for candidates [Explore Phenom](https://www.phenom.com/) ## iCIMS iCIMS is an enterprise ATS that added a dedicated frontline hiring module (iCIMS Frontline AI) in its Spring 2026 release, built on its acquisition of Apli. The module handles text recruiting, automated screening, and candidate communication for high-volume hourly workflows, alongside iCIMS's existing enterprise ATS capabilities. This makes iCIMS most practical for large organizations that already run iCIMS for corporate recruiting and want to bring frontline hiring onto the same platform, rather than for organizations evaluating iCIMS purely for frontline ATS functionality. Its 800+ integration library, including a direct data connection to UKG Pro Onboarding, is a genuine advantage for enterprise buyers running complex tech stacks who need recruiting to feed cleanly into existing WFM, payroll, and HRIS systems. **Best for:** Large enterprises already on iCIMS for corporate recruiting that want to extend the same platform to frontline and hourly hiring, or organizations that need enterprise-grade ATS scale with broad integration coverage. **Consider alternatives if:** You don't have an existing iCIMS relationship; the enterprise pricing and implementation scope are substantial when evaluating it purely for a frontline ATS use case. - iCIMS Frontline AI for high-volume hourly hiring with application flows, automated screening, and candidate text communication designed for workers without work email - Recruitment chatbot and two-way text recruiting for candidate engagement that doesn't require email or a desktop device from applicants - 800+ integrations connecting to major WFM, payroll, HRIS, and background-check providers, with a direct data partnership feeding UKG Pro Onboarding **Free version:** No **Pricing:** Enterprise, quote-based; contact for pricing **Platforms:** Web, iOS, Android [Explore iCIMS](https://www.icims.com/) ## Grayscale Grayscale is a text-recruiting and candidate communication layer designed to sit on top of an existing ATS rather than replace it. It automates outbound and two-way SMS across sourcing, screening, scheduling, and onboarding, with a named AI agent called Gracie orchestrating communication across the full hiring pipeline. This layered approach is both its primary strength and its architectural constraint: Grayscale is well-suited for organizations with a functional ATS they want to keep, but that are losing candidates between stages due to slow or email-dependent communication. It requires an existing ATS to function and adds a vendor to manage, so buyers should weigh the drop-off improvement against the added integration dependency. It integrates directly with Greenhouse, Workday, SAP SuccessFactors, UKG Pro, and ADP, covering most enterprise ATS environments. **Best for:** Organizations with a functional ATS that is performing well for job distribution and applicant tracking, but losing candidates to slow or email-based follow-up, and who want to fix that gap without replacing their underlying system. **Consider alternatives if:** You are evaluating a new ATS from scratch, or if adding a text-recruiting layer on top of an existing system creates more vendor complexity than the communication improvement justifies. - Two-way and bulk SMS messaging inside the existing ATS workflow, without requiring candidates to download an app or have an email address - Gracie AI agent automating candidate communication across the full pipeline, from sourcing through onboarding, in a coordinated sequence - Deep ATS and HRIS integrations (Greenhouse, Workday, SAP SuccessFactors, UKG Pro, ADP) that add text automation on top of existing systems without disrupting current workflows **Free version:** No **Pricing:** Enterprise, quote-based; contact for pricing **Platforms:** Web, iOS, Android, Chrome extension [Explore Grayscale](https://grayscaleapp.com/) ## Hireology Hireology is an ATS built for multi-location and hourly hiring in healthcare, automotive, hospitality, and retail, with a notable distinction in this category: it publishes its pricing. That transparency makes it one of the more accessible options for mid-sized operators, particularly franchise and rooftop businesses managing 10 to 200 locations, who need purpose-built frontline recruiting capability without an enterprise sales process. The Essentials tier at $249/month gives smaller operators a genuine entry point; the Professional tier at $499/month adds the features required for higher-volume or multi-location operations. The platform covers sourcing, branded career pages, two-way texting, TextApply, AI candidate matching, and onboarding and payroll handoffs, making it a reasonably complete standalone ATS for the use cases it targets. **Best for:** Mid-market multi-location operators in healthcare, automotive, hospitality, and retail (typically 10 to 200 locations) who want a purpose-built hourly ATS with transparent, non-enterprise pricing. **Consider alternatives if:** You are a very large enterprise that requires extensive platform customization and integration depth beyond a mid-market ATS, or if your primary vertical is outside Hireology's focus industries. - Multi-channel sourcing with branded career site and location-specific job pages, suited to franchise and rooftop operators managing geographically distributed hiring - Two-way texting and TextApply/QR-code apply for frontline candidates applying from a mobile device, without requiring a desktop or work email - AI Match candidate surfacing with direct integrations to onboarding and payroll systems, so the new-hire record transfers without manual re-entry **Free version:** No **Pricing:** Paid, published: Essentials $249/month, Professional $499/month, enterprise custom **Platforms:** Web, iOS, Android [Explore Hireology](https://www.hireology.com/) ## Deputy Deputy is a shift-work management platform that launched Deputy Hire, an ATS purpose-built for hourly and shift-based roles. Its video application format screens for personality and communication style rather than credentials, which reflects how most frontline hiring decisions are actually made, particularly in customer-facing roles where interpersonal fit matters more than work history. The hire-to-schedule path stays inside one platform: candidates move from application to first shift without leaving the Deputy app, and onboarding documents connect directly to scheduling and time tracking. Deputy's published per-user pricing and 31-day free trial lower the barrier to evaluation compared to most platforms in this category. Its depth is in scheduling and time management; the ATS is a strong addition for that use case, but organizations with very high annual hire volume or complex enterprise recruiting needs may find the feature set undersized. **Best for:** Small to mid-sized operations in retail, hospitality, healthcare, and food service that use scheduling and time tracking as their primary WFM tool and want a hiring workflow built directly into the same system. **Consider alternatives if:** Your annual hire volume makes per-user pricing expensive at scale, or if you need enterprise-grade ATS features beyond the core apply-screen-schedule workflow. - Video-based ATS that evaluates candidates on communication style and personality rather than resume formatting, suited to customer-facing frontline roles - Mobile QR-code apply with a same-platform path from application to first scheduled shift, without requiring a separate onboarding tool or system handoff - Onboarding documents and digital forms connected directly to Deputy's scheduling and time tracking modules, keeping the full new-hire workflow in one platform **Free version:** No (31-day free trial available, no credit card required) **Pricing:** Paid, published: Lite ~$5/user/mo, Core ~$6.50/user/mo, Pro ~$9/user/mo; Deputy HR add-on ~$2/user/mo **Platforms:** Web, iOS, Android [Explore Deputy](https://www.deputy.com/) ## UKG (Rapid Hire) UKG Pro is an enterprise HCM suite with UKG Rapid Hire, a recruiting module built for frontline and high-volume hiring with conversational application flows designed for workers applying on a phone. For organizations already standardized on UKG for workforce management, payroll, and HRIS, Rapid Hire is the natural extension: it connects recruiting directly into the same employee record that runs the rest of the workforce, with no data handoff required between systems. For organizations not currently on UKG, the calculus is different: adopting Rapid Hire means adopting the full UKG Pro platform, a substantial implementation project typically running 6 to 12 months, which should be evaluated against the full HCM scope rather than just the recruiting capability needed. **Best for:** Existing UKG customers who want frontline recruiting to run natively inside the platform managing their payroll, scheduling, and HRIS, and for large enterprises evaluating a full HCM replacement where talent acquisition is one module of many. **Consider alternatives if:** You're not currently on UKG and only need a frontline ATS; adopting a full enterprise HCM to solve a standalone recruiting problem is rarely the right fit on scope or budget. - UKG Rapid Hire for conversational, mobile-friendly frontline job applications with branded employer experiences, designed for workers applying without a work email - Resume parsing, personalized candidate communication, and mobile-optimized apply flows suited to high-application-volume environments - Native connection to UKG WFM, scheduling, and onboarding, where the recruiting and workforce records share the same data, with no integration handoff required **Free version:** No **Pricing:** Enterprise, quote-based; contact for pricing **Platforms:** Web, iOS, Android [Explore UKG](https://www.ukg.com/) ## How Each Platform Handles the Hiring-to-Workforce Handoff Not all platforms in this guide solve the same problem. The table below evaluates each on the three factors that determine whether a new hire's record flows from offer-accepted to first scheduled shift without manual intervention, or whether the HR team carries that load through re-entry, email chains, and disconnected systems. The comparison below is not which platform has the most features, but which ones actually close the handoff gaps. Platform Recruiting + Onboarding: Shared record? Scheduling: Native connection? Platform scope Integration work, offer to first shift MangoApps Yes: recruiting, onboarding, HR, and WFM share one employee record Yes, native Full workforce platform: communications, HR, WFM, and talent acquisition None: all workflows on the same platform Fountain No: recruiting only; separate HRIS and onboarding tool required No: separate WFM system required Standalone ATS (pre-hire focus only) 3+ integrations required: HRIS, onboarding, scheduling, payroll Paradox (Olivia) No as standalone; Yes if on Workday: onboarding handoff to Workday HCM No as standalone; Workday-dependent Conversational ATS, standalone or Workday-integrated (acquired Oct 2025) Integrations to HRIS and onboarding required unless on Workday Workstream Yes: hiring, payroll, and scheduling share one record Yes, native Hiring + payroll + scheduling bundle (QSR/retail focus) Minimal: onboarding and scheduling within the platform Harri Partial: onboarding connects to scheduling within hospitality scope Yes, native (hospitality only) Hospitality workforce platform: hiring, scheduling, labor management Minimal within hospitality; limited applicability outside it Phenom No: talent platform, not workforce management No: separate WFM required Enterprise talent platform: ATS, CRM, internal mobility Integrations to HRIS, scheduling, and payroll required iCIMS No: feeds to external HRIS; onboarding via integrations No: via integration library Enterprise ATS (Frontline AI module added Spring 2026) Integration required; 800+ connector options available to configure Grayscale No: communication overlay; underlying ATS owns the record No: does not manage the employee record Text communication layer (ATS overlay only) Entirely dependent on the underlying ATS and its connected systems Hireology Partial: onboarding and payroll handoff integrations available No: separate scheduling tool required Standalone ATS with handoff integrations Integration required for scheduling and payroll handoff Deputy Yes: hiring and onboarding documents share the scheduling platform Yes, native (core WFM function) WFM platform with ATS (scheduling-first) Minimal: scheduling and time tracking in the same platform UKG (Rapid Hire) Yes if on UKG Pro: full HCM suite with shared record Yes if on UKG Pro, native Full enterprise HCM: WFM, payroll, HRIS, and talent acquisition None if already on UKG; significant migration project if not The pattern the table surfaces is consistent: platforms built as full workforce systems (MangoApps, Workstream, Deputy, UKG) eliminate most handoff friction by design: recruiting and onboarding run inside the same system as scheduling and payroll. Standalone ATSs and communication layers can still solve specific parts of the problem (Fountain and Paradox on speed-to-offer, Grayscale on candidate communication between stages), but require buyers to plan and maintain the connections between systems themselves. Two other patterns worth noting: Harri and Workstream achieve native continuity only within their specific verticals (hospitality and QSR respectively), and UKG's continuity advantage only applies to organizations already running UKG Pro. The "How to Choose" section below maps these profiles to specific buyer situations. ## How to Choose: Matching Your Situation to the Right Platform The eleven platforms in this guide are not interchangeable. Each is built around a different primary use case, buyer size, or vertical. These profiles map common frontline hiring situations to the platforms best positioned to serve them. **You're a QSR or fast-food franchise with multiple locations.** Workstream and Harri are the most vertically specific options, with workflows and role templates built around restaurant operations. Paradox handles hiring at some of the world's largest QSR chains and suits operations that need conversational AI at significant scale. Deputy is worth evaluating if scheduling and time tracking are equally important to recruiting. **You're an enterprise employer with 500+ annual frontline hires.** Fountain and Paradox are purpose-built for this volume. iCIMS brings enterprise ATS scale plus the Frontline AI module for organizations that need a single platform across corporate and frontline populations. Phenom suits large enterprises that want AI-driven personalization across both talent pools. **You're mid-market (10 to 200 locations) and want transparent pricing.** Hireology is the only platform in this guide with published tiers at a genuinely accessible price point, serving healthcare, automotive, hospitality, and retail well at this scale. Deputy covers scheduling plus a basic ATS for operations where WFM is the primary need. **You already have an ATS and need better candidate communication on top of it.** Grayscale is the only tool in this guide designed as a text-recruiting overlay rather than a standalone ATS. If your current platform handles job distribution and applicant tracking adequately but candidate drop-off between stages is the problem, Grayscale is the right evaluation rather than a full platform replacement. **You're already on a major HCM and want to extend it to frontline hiring.** If you're on UKG: UKG Rapid Hire is the native recruiting extension. If you run iCIMS for corporate hiring and want to cover frontline populations on the same platform: the iCIMS Frontline AI module is designed for that use case. **You're specifically in hospitality (restaurants or hotels).** Harri is the only platform in this guide built natively for hospitality operations. For hospitality operators at significant enterprise scale, Fountain and Paradox are also proven in QSR and hotel contexts. **You need hiring to flow cleanly into onboarding, scheduling, and daily workforce operations.** Platforms that include hiring inside a broader workforce system (MangoApps, Workstream, Deputy, UKG) eliminate the data handoff gaps that arise when recruiting and workforce management run on separate tools. The right choice within that group depends on scale: MangoApps and UKG serve enterprise and distributed workforces; Workstream targets QSR and franchise; Deputy fits smaller shift-based operations. **You're evaluating platforms on implementation speed.** Deputy and Hireology have the lowest barrier to entry in this group, with published pricing and no lengthy enterprise procurement cycle. Most other platforms are quote-based and demo-led, which adds 2 to 6 weeks to the evaluation process before a contract is in place. ## What Makes Frontline Talent Acquisition Different Most applicant tracking systems were designed for office-based hiring: the candidate has a resume, a LinkedIn profile, and a work email address. They have time to fill out a multi-page application on a laptop and wait a week for a callback. That workflow describes roughly 20% of the global workforce. The other 80%, the frontline workers staffing retail stores, distribution centers, clinical settings, restaurants, and construction sites, face an entirely different hiring reality. Turnover in frontline roles frequently runs at 40% to 100% annually, which means many organizations are constantly filling the same positions. Candidates apply on their personal phones, often during a shift or a commute. They don't have a current resume, they expect a response within hours, and they will accept another offer before a slow process ever gets back to them. A 2025 iCIMS report on frontline hiring found that 91% of frontline hiring managers describe filling roles as urgent, yet candidate drop-off rates before completion are high enough to represent a structural problem, not just individual disengagement. The platforms that work for frontline hiring are built around those constraints. Mobile-first application flows that take under two minutes. Text and conversational AI screening that qualifies candidates without requiring a scheduled phone call. Automated interview scheduling with built-in reminders. Offer acceptance on a phone. And a clean handoff into onboarding that doesn't require the new hire to show up to a stack of paperwork with no context about the role they just accepted. ## How to Reduce Time-to-Fill for Hourly and Shift-Based Roles The fastest lever in frontline time-to-fill is removing friction from the candidate experience, not adding automation to the recruiter workflow. A 20-field application that requires account creation and a resume upload will be abandoned by a large share of frontline applicants before it is submitted. That abandonment doesn't show up in the ATS; it shows up as a shorter candidate pool, longer fill times, and open shifts. The practical levers that compress time-to-fill for hourly roles are: a mobile application that takes under two minutes to complete, text or QR-code apply options so candidates can apply from anywhere, instant acknowledgment and automated screening so the candidate gets feedback the same day, and automated interview scheduling so no one waits two business days for a confirmation email. Eliminating the gap between "applied" and "screened" is where most frontline hiring time disappears. Interview show rates are another variable that slows hourly hiring. Automated SMS reminders the day before and the morning of an interview reduce no-shows significantly, because the root cause in most cases is not disinterest; it is a candidate who forgot, applied to six other jobs, and heard back from a faster one first. Speed and communication quality, not just sourcing volume, determine how many roles get filled. Finally, the offer-to-start gap matters. A candidate who accepts an offer and then sits through a week of paperwork before their first shift is already disengaging. Role-specific onboarding workflows that begin automatically when an offer is signed, covering exactly what the candidate needs for their position, reduce early attrition and get workers to productive contribution faster. ## Connecting Hiring to Onboarding, Scheduling, and the Frontline HR Stack The handoff from ATS to workforce platform is where many frontline HR stacks quietly break. A new hire completes their application in the ATS, accepts an offer, and then their information has to be manually re-entered into the HRIS, the scheduling system, and the onboarding portal. Each re-entry step introduces delay, errors, and a version of the new hire's record that may not match the others. By the time they arrive for their first shift, someone has to reconcile the data. For frontline employers, the integrations that matter most are not the same as for corporate HR. Background check processing (Checkr, Sterling, and similar providers), job board and aggregator connections (Indeed, ZipRecruiter, Snagajob, LinkedIn), WFM and scheduling systems, and payroll are the four tiers that determine whether a new hire's record flows cleanly or gets stuck. Organizations that run recruiting on a platform that is already connected to WFM and payroll by design, rather than by integration, eliminate the re-entry problem at the source. The onboarding handoff also matters in a way that is often underestimated. Frontline workers who receive a disorganized or incomplete onboarding experience in the first week are far more likely to leave within 90 days. Role-specific onboarding content (what a clinician needs on day one differs from what an office coordinator needs) should trigger automatically based on the role the candidate was hired into, not require a recruiter to manually assign it. When the ATS, the onboarding hub, the scheduling system, and the employee app are all part of the same platform, that personalization happens without additional configuration. ## How AI Is Changing High-Volume Frontline Hiring AI in frontline recruiting has moved well past the résumé-screening use case that dominated early adoption. The most impactful applications today are conversational: voice and chat agents that engage candidates the moment they apply, ask knockout questions, score responses against role requirements, and move qualified candidates into interview scheduling, all without a recruiter touching the queue. For organizations hiring thousands of hourly workers per year, these agents don't replace the recruiter; they make it possible for a small recruiting team to manage a volume that would otherwise require ten times the headcount. The practical considerations for deploying AI in frontline hiring are worth examining directly. Bias guardrails matter: AI screening tools should score candidates on configurable fit factors (relevant experience, availability, location) rather than proxies that correlate with protected characteristics. PII masking before any data reaches a large language model is an expectation, not a differentiator. Buyers should ask vendors specifically how candidate data is handled in AI calls, who audits scoring outputs, and what recourse exists when a candidate disputes a screening decision. Interview scheduling automation is where AI delivers the clearest, most measurable ROI in hourly hiring. Automated confirmation and reminder messages reduce no-show rates. AI-generated offer letters and outreach emails reduce time-to-send without requiring a recruiter to draft each one. AI-driven compensation analysis surfaces market rates for a given role, location, and experience level, giving hiring managers a defensible basis for offer decisions without a separate benchmarking subscription. The governing principle for AI in frontline TA is the same as for any high-volume workflow: speed and accuracy at scale, with humans accountable for final decisions. ## Frequently Asked Questions **What makes frontline recruiting different from corporate recruiting?** Frontline hiring is high-volume, high-turnover, and time-driven. The best hourly candidates often accept the first offer they receive, frequently within 24 to 48 hours of applying. Most applicants apply by phone, don't have a work email address or a current résumé, and abandon applications that require more than a few minutes to complete. The platforms that work for frontline hiring are built around those constraints: mobile apply, instant engagement, automated screening, and fast handoffs into onboarding. Corporate ATS workflows designed for salaried knowledge-worker roles typically add friction at every step that matters in hourly hiring. **How can I reduce time-to-fill for hourly roles?** The most reliable lever is removing application friction: shorten the form, allow mobile or text-to-apply, skip the account creation requirement, and respond to candidates the same day they apply. After that, automated screening and interview scheduling close the gap between "submitted" and "scheduled," which is where most of the elapsed time in hourly hiring sits. Communicate by SMS, send automated reminders before interviews, and move to offer quickly. Candidates who applied to six jobs in the same week will accept the first reasonable offer they receive. **What are best practices for mobile application flows for frontline candidates?** Keep the application under two minutes. Allow QR-code, text-to-apply, or social apply options so candidates can apply without navigating to a career site. Avoid requiring account creation, résumé uploads, or work history fields that replicate what a form already captures. Use conversational screening for knockout questions (availability, location, certification requirements) rather than presenting a questionnaire. Confirm interview details and next steps via SMS, not email. **How does the handoff from ATS to a workforce platform work?** In an ideal setup, the new hire's data flows automatically from the ATS into onboarding, payroll, and scheduling without manual re-entry. Platforms with a unified data model, where recruiting and onboarding share the same employee record, eliminate duplicate entry and get workers to their first shift faster. When the ATS and the workforce platform are separate systems, the quality of that handoff depends on how tightly they are integrated: look for native integrations or API connections that move data bidirectionally, not one-way exports. The handoff step is where many frontline HR stacks quietly lose time. **How is AI used in high-volume frontline hiring?** AI now handles sourcing outreach, conversational screening (text and voice), candidate scoring against configurable fit criteria, automated interview scheduling, and offer letter drafting. Leading platforms deploy named AI agents that screen candidates 24/7 in multiple languages, move qualified applicants to scheduling without recruiter involvement, and flag anomalies for human review. Buyers should evaluate bias guardrails, PII handling, and audit trail capabilities, not just speed metrics, when assessing AI-powered recruiting tools. **What integrations matter most for a frontline HR tech stack?** Prioritize connections to: job boards and aggregators (Indeed, LinkedIn, ZipRecruiter, Snagajob), background check providers (Checkr, Sterling), WFM and scheduling systems, and payroll. For frontline-heavy organizations, the ATS-to-onboarding-to-scheduling chain matters more than features designed for candidate relationship marketing or executive-level talent pipelining. Single-platform solutions that include scheduling, payroll, and hiring natively eliminate the integration question at the source. **Should I use a dedicated frontline ATS or my HCM's recruiting module?** If hourly hiring is a core operational function and high turnover makes recruiting a constant activity, a purpose-built frontline platform typically fills roles faster than a general HCM module designed around annual corporate hiring cycles. If you are already standardized on an enterprise HCM and your frontline hiring volume is moderate, the native recruiting module (or a text and AI communication layer on top of it) may be sufficient. The deciding question is whether your current process can keep pace with your fill-rate requirements, and whether the gap is in features or in how those features fit the candidate experience. **How do I reduce candidate ghosting and interview no-shows?** Communicate by text from the first touchpoint. Respond within hours of application, not days. Send automated confirmation messages when an interview is scheduled, a reminder the afternoon before, and a same-morning text on the interview day. The most common cause of ghosting in hourly hiring is not disinterest; it is a candidate who applied to multiple jobs simultaneously and accepted the first offer or forgot the interview because no one followed up. Speed and consistent communication solve most of the problem. **What does frontline hiring software typically cost?** Most frontline talent acquisition platforms use quote-based enterprise pricing tied to hiring volume, number of locations, and modules selected. Few publish specific per-user or per-hire rates. Among the vendors in this guide, Hireology and Deputy are notable exceptions with transparent published pricing. For organizations evaluating the rest of the field, budget for a demo-first, quote-based process, and plan to negotiate based on hire volume rather than seat count. Free tiers are rare in this category; most vendors offer a trial period rather than a permanently free plan. **How do I measure whether frontline hiring software is actually working?** Track hiring velocity (time-to-fill, time-to-offer), application completion rates, interview show rates, offer acceptance rates, first-day show rates, and 90-day retention. Raw applicant volume is a vanity metric in frontline hiring; what matters is conversion at each stage and retention after hire. A platform that fills roles 30% faster but produces workers who leave within 60 days has not solved the problem. The goal is speed to productive first shift and retention through the first 90 days, because that window predicts long-term tenure in most frontline industries. --- # The Best Employee Shift Scheduling Software of 2026 **Author:** MangoApps Team **Published:** 2026-06-02 **Category:** workplace-productivity Discover the best employee shift scheduling software available in 2026, compare top options, and find the right fit for your organization. Managing shift schedules across a distributed or frontline workforce is one of the highest-friction operational challenges in hourly work, and the wrong tool compounds it. The best employee shift scheduling software reduces the back-and-forth of manual rostering, keeps labor costs in check, and gives frontline employees the schedule visibility and self-service they need to stay engaged and show up. This guide compares nine platforms available in 2026, from enterprise workforce management systems to SMB-focused apps, covering pricing, key features, and which workforce types each one fits best. Software Best For Workforce Fit Platforms MangoApps Enterprise organizations with shift-based frontline workforces that need scheduling, communications, tasks, and HR on one platform Enterprise Web, iOS, Android, Desktop Quinyx AI-powered workforce management for large frontline operations in retail, logistics, and healthcare Mid-Market / Enterprise Web, iOS, Android Shiftboard Mission-critical 24/7 scheduling for industrial, energy, healthcare, and staffing environments Enterprise Web, iOS, Android Workforce.com Demand-driven scheduling with native payroll for hourly teams in retail, hospitality, and healthcare Mid-Market / Enterprise Web, iOS, Android Deputy Flexible scheduling and compliance tooling for retail, hospitality, and healthcare teams SMB / Mid-Market Web, iOS, Android TCP Humanity Complex scheduling with certification, healthcare, and compliance depth for demanding multi-industry environments Mid-Market Web, iOS, Android When I Work Simple, fast-to-deploy scheduling and team messaging for small hourly teams SMB Web, iOS, Android Homebase Free scheduling with built-in time tracking and payroll for single-location small businesses SMB Web, iOS, Android 7shifts Restaurant-native scheduling with POS integration, labor cost tracking, and tip management SMB / Industry-Specific Web, iOS, Android --- MangoApps 4.6/5 Stars · Gartner Peer Insights 2M+ Users · Trusted Worldwide Gartner MQ Visionary · Intranet Packaged Solutions (2025) IDC MarketScape Leader · Employee Experiences (2024) Forrester Wave Strong Performer · Intranet Platforms (Q2 2026) Reworked IMPACT Award (Gold) · Intranet & Communications Platforms Most shift scheduling tools do one thing: produce a schedule. MangoApps does the same and then keeps working. As [The Enterprise Workforce Platform Built for the Frontline](https://www.mangoapps.com/), MangoApps bundles shift scheduling, time and attendance, task management, communications, and training into the same app that frontline employees already open every day, with no corporate email required and no second login to manage. When a store manager publishes a schedule, the same platform delivers the shift notification, the task list for the opening crew, the safety SOP for new hires, and the critical alert when someone calls out last-minute. That consolidation is the argument. Building shift coverage on a platform where frontline workers have 80 to 90 percent adoption from day one produces a fundamentally different operational outcome than asking a dispersed hourly workforce to adopt yet another standalone app. The [Workforce Operations Suite](https://www.mangoapps.com/solutions/workforce-management) covers the full scheduling and operational layer: shift building, availability management, time and attendance tracking, labor compliance, task dispatch, and workforce analytics, all running on the same [enterprise security stack](https://www.mangoapps.com/security-compliance) (HITRUST, SOC 2 Type II, ISO 27001) that regulated industries require. MangoApps connects to [200+ integrations](https://www.mangoapps.com/integrations/) including Workday, ADP, SAP SuccessFactors, and UKG, so scheduling data flows into existing payroll and HCM systems without manual export. **Key capabilities:** - **[Shifts & Scheduling](https://www.mangoapps.com/directory/app/shifts-scheduling):** Complete shift scheduling and management system with team calendar, built as an AI agent inside the MangoApps platform. The AI handles conflict detection, availability matching, and compliance flagging before shifts are confirmed, so managers build and publish while the agent does the checking. - **[Shift Marketplace](https://www.mangoapps.com/directory/app/shift-marketplace):** Employees list, claim, and trade shifts through an automated approval workflow without involving the manager in every exchange. Coverage gaps get filled faster, and managers approve only what needs approving rather than coordinating each swap manually. - **[Time & Attendance](https://www.mangoapps.com/directory/app/time-attendance):** Clock in/out and break tracking built on the same platform as the schedule, so actual hours reconcile automatically against planned shifts. No manual export, no separate time-tracking tool, no reconciliation step before payroll. - **[Leave Management](https://www.mangoapps.com/directory/app/leave-management):** Time-off requests, leave balances, and holiday management in the same system that holds the schedule. When a leave request is approved, it updates schedule availability immediately, closing the gap that exists when scheduling and leave live in separate tools. - **[Broadcasts & Alerts](https://www.mangoapps.com/directory/app/broadcast):** Urgent communications pushed across every channel available: in-app notifications, email, and mobile push, with delivery tracking so managers know exactly who has seen a last-minute coverage request and who has not responded. **What customers say:** [Jan Carel Uylenberg](https://www.mangoapps.com/resources/aswatson-case-study), HR Director at A.S. Watson Benelux (Kruidvat), describes schedule access as the defining proof point: "The absolutely killer application for us is that we offer employees their working schedule online. Every employee, 24/7, on their mobile devices, on their way to the store, can actually look at their schedule to make sure they know what the plan for that day is like." Kruidvat store manager Vera Scherff put the operational impact plainly: "Before, I took a picture of the schedule and posted it in WhatsApp. Sometimes people lost it or deleted it, so they had to come into the store or text me the night before. Now they can open the app, click on the schedule, and see when they have to work. They never contact me anymore with questions." Across the 16,000+ Kruidvat employees on MangoApps, the platform achieved 80%+ active user adoption, and over 20,000 A.S. Watson retail employees now receive their weekly schedules via the MangoApps mobile app. **Free version:** No **Pricing:** Modular, quote-based; contact for enterprise pricing **Platforms:** Web, iOS, Android, Desktop [Schedule a demo to see MangoApps in action](https://www.mangoapps.com/schedule-a-call) ## Quinyx Quinyx is a purpose-built workforce management platform designed for large frontline operations in retail, logistics, healthcare, and hospitality, where the volume and complexity of shift scheduling demand more than a manual process. Its AI engine forecasts labor demand in 15-minute intervals and builds schedules that automatically apply local labor laws, overtime rules, and union agreements before the schedule is published. Organizations use Quinyx when they need enterprise-grade scheduling automation with compliance confidence built in, not added later. - AI-driven demand forecasting that pulls in historical sales, foot traffic, and transaction data to recommend staffing by time slot - Automated compliance scheduling that applies labor laws, union agreements, and fatigue rules in real time across large, multi-location deployments - Employee engagement features including in-app messaging, feedback, and recognition built alongside the scheduling layer **Free version:** No (demo only) **Pricing:** Enterprise, custom quote; estimated $5-8 per employee per month based on third-party sources **Platforms:** Web, iOS, Android [Explore Quinyx](https://www.quinyx.com/) ## Shiftboard Shiftboard is a scheduling platform built for 24/7, mission-critical operations where gaps in coverage carry real operational or safety risk, including manufacturing plants, energy facilities, large healthcare systems, and industrial staffing agencies. It offers two distinct product lines: SchedulePro for high-hazard and industrial environments, and Schedules360 for healthcare. The scheduling engine accounts for certifications, training status, fatigue rules, and union contract requirements when filling and publishing shifts. - Schedule automation built around certification and qualification tracking, ensuring workers are only assigned to shifts they are credentialed to cover - Enterprise security and compliance integrations connecting to Workday, SAP, Oracle, and ADP with SOC 2 certification and MFA/SSO support - Qualification-based auto-fill that locates and contacts the right replacement worker when a shift opens, ranked by fit and availability **Free version:** No (demo only) **Pricing:** Enterprise, custom quote; two tiers: Enterprise and Enterprise Plus **Platforms:** Web, iOS, Android [Explore Shiftboard](https://www.shiftboard.com/) ## Workforce.com Workforce.com is a scheduling and workforce management platform for hourly teams in retail, hospitality, and healthcare that want scheduling, time tracking, and payroll on a single system rather than across three separate tools. Its scheduling module pulls in point-of-sale sales data to generate demand-driven staffing recommendations, and the platform includes built-in compliance alerting for Fair Workweek laws, break requirements, and overtime thresholds. Workforce.com is suited to businesses in the 50-to-3,000 employee range that need more depth than a standalone scheduling app but do not require full enterprise WFM infrastructure. - POS-integrated demand forecasting that converts transaction data into staffing recommendations up to four weeks ahead - Fair Workweek and labor law compliance alerts that flag potential violations before schedules are published, not after - Native payroll on the same platform, eliminating the double-entry and reconciliation overhead that comes with separate scheduling and payroll systems **Free version:** No (demo only) **Pricing:** Paid; per-user, per-module; custom quote **Platforms:** Web, iOS, Android [Explore Workforce.com](https://workforce.com/) ## Deputy Deputy is a scheduling and time-tracking platform used across retail, healthcare, hospitality, and logistics for shift-based teams that need schedule building, clock-in and out, compliance flagging, and payroll preparation in one place. It connects to a broad range of payroll systems and point-of-sale integrations, and its AI-assisted auto-scheduler optimizes shifts against cost, demand, and defined labor rules. Deputy works for organizations ranging from a small single-location team up to multi-site operations with thousands of employees, with tiered plans that separate core features from compliance and enterprise tools. - AI-powered auto-scheduling that builds optimized shifts against labor budgets, employee availability, and role qualifications - Built-in compliance tooling covering breaks, overtime, Fair Workweek requirements, and Australian award interpretation for international deployments - Touchless clock-in via biometric and facial recognition, with direct integrations to QuickBooks, ADP, Xero, and Square for payroll preparation **Free version:** Free trial only (31 days, no credit card required) **Pricing:** Paid; Lite $5/user/month, Core $6.50/user/month, Pro $9/user/month; Enterprise custom; $30/month minimum applies on self-serve plans **Platforms:** Web, iOS, Android [Explore Deputy](https://www.deputy.com/) ## TCP Humanity TCP Humanity (formerly Humanity, now part of TCP Software) is a scheduling platform designed for complex, demand-driven environments where employee certifications, specialized skills, and industry-specific compliance requirements must drive the scheduling process, not just availability. Healthcare organizations use it for its Hours-Per-Patient-Day scheduler; colleges and universities use it for multi-department scheduling; retail and manufacturing operations use it for shift automation against skills and certification rules. It integrates with major HCM platforms including ADP, Workday, Oracle, and BambooHR. - AI-driven demand forecasting and shift auto-fill that matches employees to open shifts based on certifications, skills, and compliance eligibility - Healthcare-specific tooling including an Hours-Per-Patient-Day scheduler and minor labor law compliance tracking - Conflict checker that surfaces scheduling errors, rest-period violations, and certification lapses before the schedule is published **Free version:** Free trial only (30 days, no credit card required) **Pricing:** Paid; Essentials from $2.75/employee/month, Professional from $3.75/employee/month (annual billing); Enterprise custom quote **Platforms:** Web, iOS, Android [Explore TCP Humanity](https://www.humanity.com/) ## When I Work When I Work is a scheduling, time tracking, and team messaging platform for small hourly teams that need to get scheduling organized quickly without a lengthy implementation process. Employees use a mobile app to view shifts, submit availability, request time off, and post shift swaps. Managers approve changes and send team messages through the same app. When I Work targets teams of roughly 5 to 200 employees in retail, food service, and healthcare where ease of use and fast employee adoption matter more than enterprise-grade compliance depth. - Employee self-service tools for availability management, shift swaps, and time-off requests that reduce the back-and-forth managers handle manually - Auto-scheduling that builds shifts against availability, role qualifications, and defined rules across single or multiple locations - Nine native payroll integrations plus a preferred partnership with Rippling for teams that want scheduling and payroll on connected systems **Free version:** Free trial only (14 days, full features, no credit card required) **Pricing:** Paid; from $2.50/user/month (single location) and $5/user/month (multi-location); time and attendance is a separate add-on **Platforms:** Web, iOS, Android [Explore When I Work](https://wheniwork.com/) ## Homebase Homebase is an all-in-one platform covering scheduling, time tracking, payroll, and hiring for small hourly businesses with one to a few locations. It offers a genuinely free Basic plan for a single location, making it one of the few options in this category with a permanent free tier rather than a time-limited trial. The AI Scheduling Assistant builds optimized schedules from employee availability, sales forecasts, and labor budget targets, and the platform integrates with Square, Clover, and Toast for point-of-sale-connected scheduling. - A free Basic plan that includes scheduling and time tracking for one location, with no time limit or credit card required - AI Scheduling Assistant that builds shifts from availability, sales forecasts, and labor cost targets, with overtime alerts and shift trade approvals built in - Integrated payroll, hiring, and onboarding on the same platform, reducing the number of tools small businesses need to manage their hourly workforce **Free version:** Yes (Basic plan; one location, permanent free tier) **Pricing:** Freemium, per-location pricing; Essentials ~$24.95, Plus ~$59.99, All-in-One ~$99.95 per location/month (annual billing) **Platforms:** Web, iOS, Android [Explore Homebase](https://www.joinhomebase.com/) ## 7shifts 7shifts is a scheduling and workforce management platform built specifically for restaurants and food service operations. It integrates natively with over 50 restaurant POS systems to pull in sales forecasts and track real-time labor cost as a percentage of revenue, which is the metric restaurant operators prioritize above most others. Alongside scheduling, 7shifts includes built-in tip pooling and tip-out calculations, a shift pool marketplace where employees can pick up available shifts, and manager log books for documenting shift events and communication handoffs between opening and closing crews. - POS-native labor forecasting that converts sales data into real-time labor cost percentage, giving managers a live view of whether they are over or under staffed against the shift target - Tip pooling and tip-out calculation tools built directly into the platform, removing the manual math that creates errors and disputes in food service operations - Shift pool marketplace and manager log books that handle the day-to-day coordination challenges specific to restaurant environments **Free version:** Yes (Comp plan; one location, up to approximately 15 employees) **Pricing:** Freemium, per-location pricing; Comp free, Entrée ~$39.99/location/month, higher tiers from ~$76.99 to ~$150/location/month **Platforms:** Web, iOS, Android [Explore 7shifts](https://www.7shifts.com/) ## What Is Employee Shift Scheduling Software? Employee shift scheduling software is a category of tools that helps managers build, distribute, and adjust work schedules for shift-based workforces. Rather than relying on spreadsheets, whiteboards, or group chats to communicate who is working when, these platforms centralize the full scheduling workflow: a manager builds shifts using a visual schedule builder, employees receive their schedules on a mobile app, and any changes, trades, or coverage requests flow through the same system with automatic notifications. Core capabilities across the category include drag-and-drop schedule building, employee availability management, shift swap and coverage request workflows, time-off and leave tracking, overtime and compliance alerts, and mobile access for workers who do not sit at a desk. More advanced platforms add AI-assisted demand forecasting, integration with point-of-sale or payroll systems, and certification or skill tracking that drives which employees can be assigned to which shifts. Shift scheduling software is distinct from general HR platforms, where scheduling is often a secondary module bolted onto a broader HCM suite. It is also distinct from workforce management (WFM) software in the broadest sense, though the two categories overlap significantly at the enterprise tier. The simplest definition: if your workforce runs in shifts and your scheduling process still involves WhatsApp, printed rosters, or manual phone trees, this is the category of software that replaces it. ## Why Employee Shift Scheduling Software Matters Scheduling unpredictability is one of the most direct contributors to frontline turnover, and frontline turnover is expensive. [According to Gallup](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx), replacing a frontline or hourly worker costs approximately 40% of that worker's annual salary, a cost that compounds fast in industries where annual turnover rates run above 50%. The hospitality sector, for example, saw roughly 79% turnover in 2023. When employees cannot reliably access their schedules, cannot trade shifts without calling their manager, and have no visibility into upcoming weeks, the friction accumulates into the kind of dissatisfaction that accelerates that turnover. On the operational side, the stakes are equally concrete. Understaffing a shift creates service failures, overtime scrambles, and pressure on the employees who do show up. Overstaffing runs up labor costs that directly reduce margin. Manual scheduling processes that rely on a single manager's memory, an outdated spreadsheet, or a group chat for coverage requests create both problems at once: they are slow to build, slow to update, and invisible to anyone not in the thread. The right scheduling software does not just automate the roster. It gives managers real-time visibility into coverage gaps, labor cost against target, and who has confirmed their shift, so problems get caught before they become missed coverage. ## What Features Should I Look for in Employee Shift Scheduling Software? The features that matter most depend on the size and complexity of your operation, but these are the capabilities worth evaluating in any platform you consider: **Drag-and-drop schedule builder.** The foundation. A visual calendar where managers can create, copy, and edit shifts without navigating menus or rebuilding the same template every week. Look for the ability to duplicate prior schedules, apply templates by role or department, and view coverage across locations in a single view. **Auto-scheduling and demand forecasting.** Higher-end platforms use historical data, sales figures, or transaction volumes to recommend optimal staffing by time slot. Even rule-based auto-scheduling (build shifts to match a set of defined patterns) saves significant manager time compared to building from scratch. AI-assisted forecasting, which pulls in live POS or operational data, is typically available at mid-market and enterprise tiers. **Employee self-service.** The ability for employees to submit availability, request time off, and initiate shift swaps without calling or texting their manager is both a retention factor and a labor savings. Platforms that centralize these requests and route them to managers for approval reduce the communication overhead that consumes significant manager time every week. **Overtime and compliance alerts.** Alerts that flag overtime exposure, missed break requirements, or Fair Workweek violations before the schedule is published, not after payroll runs. For businesses in jurisdictions with predictive scheduling laws (including several major U.S. cities), this is a compliance necessity, not a convenience feature. **Time tracking and payroll integration.** Scheduling and time tracking are adjacent workflows. Platforms that connect shift schedules directly to clock-in and clock-out data, and then push that data to a connected payroll system, remove the manual reconciliation step that creates errors and delays in payroll processing. **Mobile app quality.** For frontline workers who do not have a company laptop or a desk, the mobile app is the entire product. Evaluate push notification reliability, offline access for areas with poor connectivity, and how quickly an employee can find their schedule from the home screen. Adoption follows usability. ## How to Choose the Right Employee Shift Scheduling Software The most common mistake in evaluating scheduling software is optimizing for features rather than fit. A platform loaded with AI forecasting and compliance automation serves no one well if the manager building schedules cannot figure out how to use it, or if frontline employees do not adopt the app. Start from your workforce's reality: how large is the team, how distributed, and how technically comfortable are the employees who will use this every day? For single-location small businesses and teams under 50 employees, the priority is fast time-to-value, a clean mobile experience, and transparent pricing. Homebase and When I Work are natural starting points at this scale. Both publish pricing, have genuine free tiers or trials, and get teams scheduled in hours rather than weeks. For restaurant operators specifically, 7shifts offers integration with POS systems and tip management tooling that general scheduling platforms do not replicate. For multi-site and mid-market organizations managing 50 to a few thousand hourly employees, the conversation shifts toward compliance depth, payroll integration, and whether the scheduling tool connects to existing HCM infrastructure. Deputy and Workforce.com both serve this segment, with Workforce.com offering the deeper payroll-native architecture and Deputy offering broader cross-industry flexibility. TCP Humanity is worth evaluating specifically for healthcare, education, and any environment where employee certifications or minor labor rules drive scheduling eligibility. For enterprise organizations with large, distributed frontline workforces, the evaluation should include whether standalone scheduling software creates integration overhead relative to a platform that combines scheduling with communications, task management, and HR operations. Quinyx and Shiftboard are the most capable dedicated WFM options at this tier. MangoApps is worth evaluating for frontline-heavy organizations that want scheduling as part of a broader workforce platform rather than one more point solution to integrate and maintain. ## Final Verdict For enterprise organizations with large shift-based frontline workforces, MangoApps is the strongest option in this guide. Scheduling sits inside a broader Workforce Operations Suite that also covers task management, communications, training, and workforce analytics. Frontline employees use one app for all of it, which is why adoption rates hold at 80 to 90 percent rather than the 30 to 40 percent typical of point solutions. For organizations that want dedicated pure-play workforce management with AI forecasting and compliance depth, Quinyx and Shiftboard are the closest alternatives at the enterprise tier. Mid-market teams will find strong options in Deputy and Workforce.com. Small businesses and single-location operators should start with Homebase or When I Work, and restaurant operators should evaluate 7shifts specifically for its POS-native scheduling and tip management tooling. ## Frequently Asked Questions ### What is employee shift scheduling software? Employee shift scheduling software helps managers build and distribute work schedules for teams that operate in shifts, typically in retail, hospitality, healthcare, manufacturing, and similar hourly or frontline environments. The core workflow covers creating shifts on a visual calendar, notifying employees of their schedules via mobile app, managing availability and time-off requests, handling shift swaps and coverage gaps, and tracking attendance against the published schedule. More advanced platforms extend into demand forecasting, compliance alerting, time tracking, and payroll integration. ### How is shift scheduling software different from workforce management software? The terms overlap significantly, especially at the enterprise tier. In general, "shift scheduling software" describes tools focused on the scheduling and coverage layer: building rosters, managing availability, handling shift swaps. "Workforce management software" (WFM) is a broader category that typically adds labor demand forecasting, labor cost analytics, compliance automation, and integration with payroll and HCM systems. Most enterprise WFM platforms include scheduling as a core module. Most dedicated scheduling tools, particularly in the SMB segment, do not offer the full WFM feature set. If you are evaluating platforms like Quinyx or Shiftboard, you are in WFM territory. If you are evaluating Homebase or When I Work, you are in scheduling-first territory. ### Is there free employee shift scheduling software? Yes, though the free tiers come with meaningful constraints. Homebase offers a permanently free Basic plan for a single location. 7shifts offers a free Comp plan for a single restaurant location with up to approximately 15 employees. Sling (not covered in this guide) offers a free plan for up to 50 users, though time tracking is gated behind paid tiers. Most other platforms in this category, including Deputy, When I Work, and TCP Humanity, offer free trials (14 to 31 days) rather than permanent free plans. Enterprise platforms like Quinyx, Shiftboard, and Workforce.com are demo and quote-only with no trial period. ### How much does employee scheduling software cost? Pricing varies significantly by segment and how vendors structure their models. SMB tools typically charge per user per month or per location per month. Per-user pricing ranges from roughly $2.50 to $9 per user per month for platforms like Deputy and When I Work. Per-location pricing ranges from free (Homebase Basic) to approximately $150 per location per month for higher-tier 7shifts plans. Enterprise and mid-market platforms like Quinyx, Shiftboard, and Workforce.com do not publish pricing and provide custom quotes based on employee count, modules, and implementation scope. Total cost of ownership should account for setup fees, minimum monthly spends (Deputy has a $30 monthly minimum on self-serve plans), and add-on costs for features like time tracking or payroll that may not be included in the base plan. ### How long does implementation typically take? It depends heavily on platform complexity and workforce size. SMB tools like Homebase and When I Work are designed for self-service deployment and most teams are scheduling within a few hours of sign-up. Mid-market platforms like Deputy typically take one to two weeks to configure, integrate with payroll, and onboard managers. Enterprise platforms like Quinyx, Shiftboard, and Workforce.com typically take two to four months to implement, including integration with HCM and payroll systems, compliance configuration, and manager training. MangoApps backs its enterprise deployments with a formal Adoption Guarantee: 90%+ of employees actively using the platform within 90 days. ### What is Fair Workweek scheduling? Fair Workweek (also called predictive scheduling) refers to a set of labor laws that require certain employers to provide employees with advance notice of their schedules, typically 7 to 14 days ahead, and to compensate employees for last-minute schedule changes. These laws are in effect in several major U.S. cities and states including San Francisco, Seattle, New York City, Chicago, Oregon, and others, primarily covering retail, hospitality, and food service employers above a certain size. Violations can result in penalties per affected shift. Scheduling software with Fair Workweek compliance tooling flags potential violations before the schedule is published, tracks the required advance notice window, and documents schedule changes for audit purposes. ### What scheduling software is best for small businesses? For single-location small businesses, Homebase is the easiest entry point: a permanent free plan, a clean mobile app, and payroll built in on paid tiers. When I Work is a strong alternative for teams that want a slightly more structured scheduling workflow, with auto-scheduling and multi-location support at a low per-user cost. Both tools have fast time-to-value and do not require a dedicated IT resource to set up. For restaurant operators specifically, 7shifts is purpose-built for the workflows small restaurant teams actually use, including POS integration, labor cost tracking, and tip management. ### What scheduling software works best for restaurants? 7shifts is the most purpose-built option for restaurants. It integrates with over 50 restaurant POS systems to pull real-time sales data into labor cost calculations, includes tip pooling and tip-out tools, and offers a shift pool marketplace for employee-driven coverage. When I Work and Deputy also serve restaurant operators and cover the core scheduling and compliance workflows, though they lack the restaurant-specific POS depth of 7shifts. For restaurant groups operating at scale, more enterprise-focused platforms should be evaluated for their demand forecasting and multi-site management capabilities. ### What scheduling software works best for healthcare? Healthcare scheduling requires certification and credentialing tracking, compliance with rest period and Hours-Per-Patient-Day regulations, and integration with HCM systems that hold employee qualification data. TCP Humanity is the most purpose-built option in this guide for healthcare, with its healthcare-specific scheduler and certification-driven auto-fill logic. Shiftboard's Schedules360 product line is also purpose-built for healthcare and is worth evaluating for large health systems with complex union and credentialing requirements. MangoApps serves healthcare organizations that need scheduling integrated with communications, task management, and compliance workflows in a single platform. ### Can scheduling software integrate with payroll? Yes, and this is one of the most important integration decisions in the evaluation process. When scheduling and payroll are on separate systems, time data must be manually exported or reconciled, which introduces errors and delays payroll processing. Most platforms in this guide support payroll integrations, though the breadth and depth varies. Deputy integrates with QuickBooks, ADP, Xero, and Square. When I Work offers nine native payroll integrations plus a Rippling partnership. Workforce.com includes native payroll on the same platform. Enterprise platforms like MangoApps connect to ADP, Workday, SAP SuccessFactors, and UKG via its 200+ integration library. When evaluating integrations, confirm whether the connection is a native two-way sync or a CSV export, as the latter still requires manual steps and is prone to error. ### How does AI scheduling work? AI scheduling uses historical and real-time data to recommend or automatically generate shift coverage rather than requiring a manager to build every schedule from scratch. The inputs vary by platform. Demand forecasting models pull in sales data, transaction volumes, or foot traffic patterns to predict how many employees are needed at a given time. Rules-based engines apply defined constraints (minimum coverage per role, maximum consecutive hours, union rules, certification requirements) to ensure the generated schedule is both compliant and efficient. The most sophisticated implementations combine forecasting with constraint-solving to produce schedules that hit labor cost targets while meeting all compliance and coverage thresholds. In most platforms, managers review and approve AI-generated schedules rather than publishing them automatically. ### How does scheduling software handle last-minute call-outs? The workflow varies by platform, but most handle this through some combination of automated notifications, a shift marketplace, and manager-driven replacement search. When an employee calls out, the system generates an available coverage list based on who is qualified, available, and not in overtime risk. Some platforms automatically notify those employees via push notification; others require the manager to initiate outreach. Platforms with a shift marketplace allow available employees to claim open shifts without manager involvement. MangoApps' Critical Alerts feature can push high-priority coverage requests to frontline workers with read-receipt confirmation, so managers know who has seen the request and who has not. For enterprise operations where coverage gaps carry safety or operational risk, platforms like Shiftboard and Quinyx offer more automated replacement workflows with certification and fatigue-rule checks built in. ### Can employees swap shifts themselves? Yes, on most platforms at mid-tier and above. The typical workflow is: an employee posts a shift they want to swap, another employee claims it, and the manager approves or rejects the swap before it is confirmed. This self-service model reduces the volume of calls and texts a manager receives while keeping the manager in control of final approvals. Some platforms allow automatic approvals for swaps that meet defined rules (same role, within budget, no overtime triggered) without requiring manager sign-off. When evaluating this feature, confirm whether swap requests are visible only to the individual employee or to a broader pool of eligible coworkers, as the latter produces significantly faster coverage. ### What is the difference between scheduling software and time tracking software? Scheduling software manages the plan: who is supposed to work, when, and in what role. Time tracking software manages the actuality: when employees clocked in and out. The two are closely related and many platforms cover both. When they are separate, reconciling scheduled hours against actual hours for payroll purposes requires a manual or automated export step between systems. Most platforms in this guide that are categorized as scheduling tools also include time tracking functionality, either natively or via a connected add-on. The important distinction at purchase time is whether time tracking is included in your plan or gated behind an additional fee, as is the case with several SMB-tier offerings. ### Do employees need a company email address to use scheduling software? Not on most modern platforms, and this matters significantly for frontline workforces where the majority of employees have no corporate email account. Sign-in options typically include phone number, a personal email address, or an employee ID. MangoApps is specifically architected for workforces without corporate email, which is part of why it achieves the adoption rates it does in retail, healthcare, and industrial environments. A.S. Watson Benelux rolled MangoApps across 16,000 Kruidvat employees, most of whom had no company email address, with 80%+ active user adoption. When evaluating any platform for a frontline workforce, confirm the exact sign-in flow for employees and whether the platform can be accessed without a corporate identity provider. ### Is MangoApps only a scheduling platform? No. Scheduling is one component of MangoApps' [Workforce Operations Suite](https://www.mangoapps.com/solutions/workforce-operations), which also covers time and attendance, task management, safety, and standard operating procedures. MangoApps is organized into two communications products and six operational suites covering workforce operations, HR operations, performance and learning, talent acquisition, field services, and IT and procurement, all running on the same enterprise platform. Organizations that start with scheduling can expand into communications, training, or HR without changing platforms or migrating data. That modular architecture, expressed in the positioning "start where you need to, expand when you're ready," is what distinguishes MangoApps from dedicated scheduling tools. --- # MangoApps AI Stops Advising and Starts Acting **Author:** MangoApps Team **Published:** 2026-05-31 **Category:** enterprise-ai When the AI Stopped Waiting for Permission # MangoApps AI Stops Advising and Starts Acting ## When the AI Stopped Waiting for Permission A customer success manager walks into Monday morning with a renewal at risk. The account health score dropped over the weekend — a Success Plan milestone slipped, a survey came back with a low NPS, and nobody caught it in time. In the old world, she would have spent the first hour of her week triaging signals, writing follow-up tasks, and assigning them to the right people. By the time she had a plan, the customer had already formed an opinion. That scenario quietly became obsolete this week. The [Automatic CS Task Engine](https://www.mangoapps.com/changelog/3009) does not wait for Monday morning. When a Success Plan goes off-track or a renewal risk signal appears, it assigns tasks automatically — and cancels them automatically when the signal clears. The CS manager still owns the relationship. She just no longer owns the triage. This is not a chatbot feature. It is not a recommendation engine. It is an AI that takes operational responsibility. ## The Consoles That Show You What the AI Did The natural question when AI starts acting autonomously is: what did it actually do? That question now has an answer. [AI Autopilot Consoles](https://www.mangoapps.com/changelog/3007) landed this week for three domains — Shift Manager, Service Desk, and Onboarding. Each console shows every autonomous action the AI took, what is pending approval, and a configurable trust-level dial that controls how much latitude the AI has. Managers can see the AI's work the same way they would review a team member's activity log. This matters more than the automation itself. The consistent failure mode for AI in enterprise software is not that it gets things wrong — it is that nobody knows what it did or why. Autopilot Consoles solve the accountability problem that has kept most organizations from letting AI act at all. The Shift Manager console connects directly to the [Shift Coverage Dashboard](https://www.mangoapps.com/changelog/3007), where understaffed shifts are surfaced by scheduling group with one-click access to fill gaps. The AI does not just flag the problem — it starts working the solution and logs what it did. The Service Desk and Onboarding consoles operate on the same model. The AI handles the operational rhythm. The console makes it auditable. ## Automation You Can Build Without an IT Ticket For teams that want to build their own autonomous workflows rather than wait for a pre-built console, [Playbooks](https://www.mangoapps.com/changelog/3005) arrived last week. The visual step editor lets operations leaders build multi-step AI automations — with configurable input forms, trigger scheduling, and run history — without writing code or filing a systems request. This is the feature that changes who can automate. Until now, workflow automation in enterprise software required a technical implementation. Playbooks move that capability to the people who understand the operations. An HR leader can build an onboarding automation. A field manager can build a compliance check sequence. A CS team lead can build an escalation workflow. The trigger scheduling means these are not one-time runs — they are repeating operational processes that happen whether or not a manager remembers to initiate them. Pair Playbooks with the redesigned [Forms AI Builder](https://www.mangoapps.com/changelog/3008) — now on by default with a side-by-side Conversation and Form Preview interface — and you have an end-to-end system for building automated intake, routing, and response workflows. The AI builds the form while you describe what you need. The Playbook runs the process once the form is submitted. ## Ask AI Finally Has Access to the Whole Organization Autonomous action is only as useful as the information the AI can access. This week, [Ask AI expanded its search scope](https://www.mangoapps.com/changelog/3008) to include company Drive files (PDFs, Word documents, images), published Sites, Wikis, HR policies, and SOPs. This is the change that makes AI assistance practical for frontline managers and HR teams. The question that used to require a search through four different systems — "what is our return-to-work policy after a leave of absence?" — now has a direct answer drawn from the actual policy document. The AI cites the source. The manager gets the answer in the same place they do everything else. For organizations with large knowledge bases — field service SOPs, compliance documentation, training materials — this is a meaningful operational shift. The information existed. The friction was retrieval. That friction is now substantially lower. ## The Broadcast Stack Became Its Own Automation Layer Separately from the AI infrastructure, the broadcast and communication stack crossed a threshold this week where it started behaving like an autonomous compliance system rather than a messaging tool. [Broadcast Auto-Escalation](https://www.mangoapps.com/changelog/3004) means that when a critical message goes unacknowledged, the platform escalates automatically — from email to SMS to voice call — until someone responds. This is not a feature for routine communications. It is infrastructure for situations where receipt confirmation is a compliance requirement and human follow-up is not fast enough. The [Compliance Reporting](https://www.mangoapps.com/changelog/3004) that accompanies it — with department and location breakdowns and CSV export — means operations leaders can demonstrate acknowledgment rates without building a manual audit trail. The system does that work continuously. [AI Compose for Broadcasts](https://www.mangoapps.com/changelog/3003) and [per-recipient translations](https://www.mangoapps.com/changelog/3003) complete the picture. The AI drafts the message, recommends send timing, runs A/B variants, and delivers each copy in the recipient's preferred language. A single broadcast operation now covers authoring, targeting, delivery optimization, translation, escalation, and compliance documentation. ## What Crosses the Line This Week The individual features matter less than the aggregate shift they represent. MangoApps has been building toward this for several release cycles, but this week is when the accumulation became visible as a pattern. The [Automatic CS Task Engine](https://www.mangoapps.com/changelog/3009) closes tickets without being asked. The Autopilot Consoles run operations and log what they did. Playbooks execute repeating workflows on schedule. Ask AI retrieves answers from the full organizational knowledge base. Broadcast escalates through channels until someone confirms receipt. None of these are AI assistants. They are AI operators. The distinction is not semantic — it changes the nature of the work that falls to human managers. The triage, the follow-up, the escalation, the compliance documentation — those are now handled. What remains is judgment, relationship, and the decisions that genuinely require a person. For HR leaders managing onboarding at scale, for operations executives trying to close the gap between policy and practice, for frontline managers who spend more time on coordination than on their teams — this is what the shift looks like in practice. The AI does not just help you work. It does a category of the work. The full week's releases are available across the [May 23](https://www.mangoapps.com/changelog/3002), [May 24](https://www.mangoapps.com/changelog/3003), [May 25](https://www.mangoapps.com/changelog/3004), [May 26](https://www.mangoapps.com/changelog/3005), [May 27](https://www.mangoapps.com/changelog/3006), [May 28](https://www.mangoapps.com/changelog/3007), [May 30](https://www.mangoapps.com/changelog/3008), and [May 31](https://www.mangoapps.com/changelog/3009) changelogs. --- # The Best Digital Workplace Platforms for 2026 **Author:** MangoApps Team **Published:** 2026-05-29 **Category:** industry-insights Discover the best digital workplace platforms of 2026, compare top options, and find the right fit for your organization. Most organizations run on a patchwork of communication tools, knowledge bases, and workflow apps that don't connect to each other, and the employees furthest from headquarters, the frontline, are often not reached at all. A digital workplace platform changes that by bringing communication, collaboration, and the workflows people run every day into a single environment everyone can actually use. This guide covers eight of the strongest options available in 2026, with honest comparisons across platform depth, workforce fit, and pricing. > **Short on time? Here are our top picks:** > - **Best for frontline and enterprise workflows:** MangoApps > - **Best for Microsoft 365 organizations:** Microsoft 365 / Viva > - **Best free option:** Bitrix24 Software Best For Workforce Fit Platforms MangoApps Frontline and enterprise: unified intranet, communications, and operational workflows in one app Mid-market to large enterprise; frontline-heavy organizations Web, iOS, Android, Desktop Microsoft 365 / Viva Organizations already fully invested in the Microsoft 365 ecosystem Enterprise; desk-worker-dominant organizations Web, iOS, Android, Desktop Powell Software Microsoft 365 teams that need a more usable intranet and governance layer Mid-market to enterprise; Microsoft-committed organizations Web, iOS, Android, Desktop (Teams) Claromentis Teams that want intranet, workflow automation, and e-learning in one modular package Mid-market; compliance-conscious organizations Web, iOS, Android eXo Platform Organizations that require open-source or self-hosted deployment Mid-market to enterprise; data-sovereignty-sensitive organizations Web, iOS, Android Bitrix24 Teams that want an all-in-one intranet, CRM, and collaboration suite on a limited budget SMB to mid-market Web, iOS, Android, Desktop Jostle Small to mid-sized organizations that need a simple, fast-to-deploy intranet SMB; culture-focused teams Web, iOS, Android MangoApps 4.6/5 Stars · Gartner Peer Insights 2M+ Users · Trusted Worldwide Gartner MQ Visionary · Intranet Packaged Solutions (2025) IDC MarketScape Leader · Employee Experiences (2024) Forrester Wave Strong Performer · Intranet Platforms (Q2 2026) Reworked IMPACT Award (Gold) · Intranet & Communications Platforms MangoApps is [The Enterprise Workforce Platform Built for the Frontline](https://www.mangoapps.com/): a unified intranet, internal communications suite, and operational workflow platform built to reach every employee in the organization, not just those at a desk. Where most digital workplace tools started as knowledge-worker software and were adapted to everyone else, MangoApps was built from day one around the populations that make up the majority of large organizations' headcount: retail associates, clinicians, warehouse operators, field technicians. The [Unified Intranet & Employee App](https://www.mangoapps.com/) brings together news feeds, knowledge libraries, HR documents, task management, and operational workflows into one branded app that works on any device, without a corporate email address or VPN. Organizations that switch from a legacy intranet or a stack of point solutions consistently report adoption rates above 90% within 90 days, backed by MangoApps' [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee). The platform runs eight suites on a single data model: communications, intranet, workforce operations, HR operations, performance and learning, talent acquisition, field services, and IT and procurement. Starting with one suite and expanding when ready is a configuration, not a new implementation. For organizations evaluating whether a digital workplace can actually replace the four or five tools they're currently running, that architecture is the argument: [200+ integrations](https://www.mangoapps.com/integrations/), enterprise security certified to HITRUST, SOC 2 Type II, and ISO 27001, and a partnership model that includes named customer success managers and a 98% retention rate. **Key capabilities:** - [**Unified Intranet & Employee App**](https://www.mangoapps.com/): a single branded app for every employee, desk or frontline, with personalized news feeds, departmental pages, searchable knowledge libraries, and company resources accessible on any device with no corporate email required - [**Internal Communications Suite**](https://www.mangoapps.com/solutions/internal-communications): multi-channel message delivery with audience targeting by role, location, department, or custom segment; read-receipt and acknowledgment tracking; and reach analytics that show exactly who received, opened, and acted on every communication - [**Campaigns & Journeys**](https://www.mangoapps.com/key-features/campaigns-and-journeys): structured multi-step communication and training programs for onboarding, change management, compliance rollouts, and culture initiatives, with automated sequencing, branching, and completion tracking - [**AI-Assisted Content and Workflows**](https://www.mangoapps.com/key-features/posts): embedded AI across every suite for content drafting, translation, task automation, and intelligent search, built into the workflows that use it rather than added as a separate module - [**Analytics and Insights**](https://www.mangoapps.com/analytics-insights): organization-wide visibility into what employees have read, completed, and acted on, with dashboards for communications leaders, HR teams, and operations managers **Free version:** No **Pricing:** Modular, quote-based; contact for enterprise pricing **Platforms:** Web, iOS, Android, Desktop [Schedule a demo to see MangoApps in action](https://www.mangoapps.com/schedule-a-call) Microsoft 365 / Microsoft Viva Microsoft Viva turns the Microsoft 365 stack (SharePoint, Teams, Viva Engage, and Power Automate) into a unified employee experience layer accessible inside Teams. For organizations already fully licensed on Microsoft 365, it removes the need for a separate intranet tool and gives IT teams a familiar set of governance and deployment controls. The full Viva Suite extends the core Connections gateway with modules for employee engagement, workplace analytics, learning, and manager effectiveness. - **Viva Connections:** branded intranet gateway native inside Microsoft Teams, pulling SharePoint news, announcements, and HR resources into a single personalized dashboard - **Deep Microsoft 365 integration:** SharePoint, Copilot AI, Viva Engage (enterprise social), Power Automate workflows, and the full Microsoft productivity stack - **Employee experience modules:** Viva Insights (wellbeing and productivity analytics), Glint (engagement surveys), Amplify (internal communications), and Learning (LMS integration) **Free version:** Partial. Viva Connections is included at no additional cost with Microsoft 365 and Office 365 enterprise plans that include a Teams license; the full Viva Suite is paid **Pricing:** Viva Suite at $12.00/user/month on an annual commitment; individual modules available separately; bundled M365 plans vary **Platforms:** Web, iOS, Android, Desktop [Explore Microsoft Viva](https://www.microsoft.com/microsoft-viva) Powell Software Powell Software is built specifically for organizations that run on Microsoft 365 but find SharePoint and Teams hard for employees to navigate and actually use day to day. It adds a branded intranet layer, pre-built governance templates for Teams and SharePoint workspaces, and a no-code workflow builder on top of the existing M365 infrastructure, without requiring additional Microsoft licenses. A modular architecture (Foundation, Boost, Advanced) lets teams start with an intranet and expand to governance and AI assistant capabilities over time. - **Powell Governance:** pre-built compliance templates for SharePoint and Teams workspaces, reducing sprawl and keeping the digital environment organized at scale - **Branded intranet on M365:** a usable, employee-facing intranet experience layered on top of SharePoint without replacing the underlying Microsoft investment - **Powell Buddy AI assistant:** generative AI assistant for content creation, knowledge retrieval, and employee self-service built into the Powell environment **Free version:** No **Pricing:** Quote-based; third-party references estimate approximately $1.30/user/month at 1,000 seats **Platforms:** Web, iOS, Android, Desktop (via Teams) [Explore Powell Software](https://powell-software.com/) Claromentis Claromentis is a modular digital workplace that combines a traditional intranet with a no-code business process automation engine and a SCORM-compliant LMS in one package. Organizations currently managing their intranet, workflow approvals, and employee training across separate tools will find the bundled breadth practical, and the modular licensing means teams can start with core intranet and add BPA or LMS capabilities when ready. Both SaaS and on-premise hosting are available, and the platform carries HIPAA and ISO 27001 certifications. - **InfoCapture BPA engine:** no-code e-forms, multi-step workflow routing, and approval automations without requiring developer resources - **Built-in SCORM-compliant LMS:** course authoring, delivery, and completion tracking included natively, without a third-party learning tool - **SaaS or on-premise deployment:** with HIPAA and ISO 27001 certification, suited to compliance-sensitive sectors including healthcare and financial services **Free version:** Partial. Free 30-day trial; no permanent free tier **Pricing:** Quote-based; modular editions available (Core intranet, BPA, LMS, or full Digital Workplace bundle) **Platforms:** Web, iOS, Android [Explore Claromentis](https://www.claromentis.com/) eXo Platform eXo Platform is the only major open-source digital workplace, giving organizations with strict data-sovereignty, self-hosting, or regulatory requirements a fully featured option they can run on their own infrastructure. The platform covers intranet, team collaboration, documents, tasks, wikis, calendars, and an enterprise social network in one environment, with a free Community edition and published per-user pricing for hosted plans. Its deployment flexibility makes it a strong fit for high-security environments and organizations with procurement policies that restrict proprietary SaaS. - **Open-source architecture:** self-hosted or cloud deployment with no vendor lock-in, meaningful for organizations with data residency requirements or regulatory constraints - **Built-in gamification and recognition:** kudos, rewards, and a perk store for employee engagement, included natively without a separate recognition tool - **Full digital workplace breadth:** intranet, enterprise social network, document management, tasks, wikis, and team calendars in a single environment **Free version:** Yes. Open-source Community edition is free; hosted plans start at $5/engaged user/month **Pricing:** Community (free, self-hosted); Professional from $5/user/month; Enterprise and Enterprise Unlimited tiers available **Platforms:** Web, iOS, Android [Explore eXo Platform](https://www.exoplatform.com/) Bitrix24 Bitrix24 is one of the few platforms in this category that combines a social intranet, project and task management, team chat and video, document management, and a built-in CRM in one product, with a genuinely free tier for unlimited users. It is primarily used by small to mid-sized teams that want broad collaboration capabilities without paying per-user fees, and its flat-fee pricing makes total cost more predictable as teams grow. Both cloud and on-premise deployment are available. - **Free plan for unlimited users:** intranet, tasks, chat, video conferencing, and document management at no cost, with no cap on user count - **Built-in CRM and telephony:** alongside intranet and collaboration features, which is uncommon in this category and useful for sales-driven or customer-facing teams - **Flat-fee pricing:** plans are priced per organization rather than strictly per user, which changes the cost curve at larger team sizes **Free version:** Yes. Free plan for unlimited users **Pricing:** Free; paid plans from approximately $49/month (organization, billed annually); mid-tier from approximately $87/month **Platforms:** Web, iOS, Android, Desktop (Windows and Mac) [Explore Bitrix24](https://www.bitrix24.com/) Jostle Jostle is built for small to mid-sized organizations that want a culture-focused intranet they can launch quickly without an IT project. It ships out of the box with a news feed, org chart, Shout-Outs recognition tools, a document library, and JostleTV digital signage, with transparent per-user pricing across published tiers. The platform reports employee participation rates above 85%, a figure it attributes to the simplicity of the design and the low barrier to entry for non-technical administrators. - **Fast, low-effort deployment:** designed to launch with no IT skills required, practical for HR-led teams without internal technical resources - **Recognition and culture tools:** Shout-Outs, org chart, and digital signage alongside news and documents, useful for organizations where culture-building is a primary objective - **Transparent published pricing:** Bronze, Silver, and Gold tiers with per-user rates listed publicly, with no need for a quote to start evaluating total cost **Free version:** No (free trial available) **Pricing:** Paid; published per-user tiers (Bronze/Silver/Gold); Platinum is quote-based **Platforms:** Web, iOS, Android [Explore Jostle](https://jostle.me/) ## What Is a Digital Workplace Platform? A digital workplace platform is a unified software environment that brings together the tools employees need to communicate, find information, collaborate, and complete work, regardless of where they work or what device they carry. Rather than a collection of separate tools that each solve part of the problem, a digital workplace platform is a single environment where news feeds, knowledge libraries, operational workflows, HR documents, and team communications all live together. The category spans a wide range of approaches. Some platforms are primarily communication and culture tools: social news feeds, recognition programs, and targeted announcements with a knowledge base attached. Others are true workforce platforms, where intranet, communications, and operational workflows like scheduling, compliance tracking, onboarding, and task management all run on the same data model. The distinction matters when evaluating options. An organization that needs to reach frontline workers and run shift schedules on the same platform has different requirements than one that wants to improve how corporate communications reach desk workers. Understanding where on that spectrum your organization's needs fall is the right place to start any evaluation. ## Why Digital Workplace Platforms Matter The underlying problem most digital workplace investments are trying to solve is reach. [Gallup's 2024 State of the Global Workplace report](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.html) found that only 23% of employees worldwide are engaged at work, a number that has barely moved in years. Part of that disengagement is structural: the majority of the workforce in most large organizations does not sit at a desk, does not have a corporate email address, and has no reliable channel for receiving information from their employer. They find out about policy changes through a manager, a break-room notice, or not at all. The business case for fixing that is not primarily about culture scores. It is about operational performance. Organizations that have replaced legacy intranets or fragmented tool stacks with a single digital workplace consistently report lower onboarding costs, faster compliance completion, reduced reliance on email for operational communication, and measurable increases in how much of the workforce is actually receiving and acting on the information they're sent. The contrast between industry-average intranet adoption rates (typically 30-40%) and platforms that report 90% or higher is not a feature difference. It is an architecture difference, driven by whether the platform was built to reach every employee or just the ones with a laptop. ## What Features Should I Look for in a Digital Workplace Platform? **Employee reach without corporate infrastructure.** Can the platform reach workers who don't have corporate email, a VPN, or a company-issued device? For organizations with meaningful frontline or field populations, this is a hard prerequisite. A platform that requires an Outlook license to receive a push notification is not a frontline platform. **Multi-channel communication with delivery confirmation.** A modern digital workplace should support targeted announcements by role, location, department, or custom segment, and it should tell communicators whether employees received, opened, and acknowledged what they sent. Sending an announcement without knowing if it landed is not a communications system. **Searchable, governed knowledge management.** Beyond a content library, look for version control, content auto-expiry or governance reminders, role-based publishing permissions, and search that works across the full content body rather than just titles. Knowledge bases that can't be maintained at scale become noise quickly. **Workflow and process automation.** Forms, multi-step approvals, checklists, and tracker-style operational workflows are what separate a true digital workplace from an intranet. Whether it's a new hire checklist, a QA audit form, or a compliance sign-off, the platform should be able to run the process, not just communicate about it. **Analytics that go beyond page views.** Reach data, read rates, completion percentages, and engagement trends are how communications and operations leaders verify the platform is working. Platforms that can only tell you how many people logged in are insufficient for organizations where accountability matters. **Integration depth with existing systems.** SSO, HRIS sync, and API access to the operational tools already in use are what determine whether a digital workplace becomes the center of gravity or just another tab. Evaluate the integration model early: pre-built connectors, an iPaaS requirement, or a custom API build each carries a different total cost. ## How to Choose the Right Digital Workplace Platform Start with workforce composition, not feature lists. If more than a third of employees work without a desk or a corporate email address, the platform must be built for that reality from the ground up. Most enterprise intranets were designed for knowledge workers; their mobile apps and frontline accessibility were added later, and it shows in adoption rates. The platforms that consistently achieve 80-90% adoption in large organizations are the ones where frontline accessibility was an architectural decision, not an afterthought. Map your operational gaps before you evaluate features. Organizations that buy on feature breadth end up paying for capabilities that never get configured. A more useful framing: which tools are you running today that the platform should replace, which workflows are currently paper-based or email-dependent that should move onto the platform, and which employee populations are currently unreachable that need to be on it? That list is the evaluation rubric. Look hard at the adoption model too, not just the product. A platform that comes with a named customer success manager, a structured onboarding program, and an adoption guarantee is a materially different investment than a self-serve SaaS tool with a knowledge base. For organizations with significant frontline populations, complex workflow needs, or both, MangoApps is worth a close look. ## Frequently Asked Questions **What is the difference between a digital workplace platform and an intranet?** An intranet is one component of a digital workplace, typically the content and communication layer where news, documents, and HR resources live. A digital workplace platform is broader: it includes collaboration tools, workflow automation, operational capabilities like task management and scheduling, and often the full employee app experience alongside the intranet. Many organizations start with an intranet and discover they need the broader platform as their requirements grow. **Do I need a digital workplace platform if we already use Microsoft 365?** Microsoft 365 provides productivity building blocks: email, documents, chat, and a basic SharePoint environment. A digital workplace platform adds the employee experience layer on top, including personalization, frontline accessibility without per-user corporate licensing, governance for the content and workspace sprawl that M365 generates naturally, structured communication programs, and operational workflows that M365 doesn't manage natively. For organizations where SharePoint adoption is low or frontline workers are unreached, a dedicated platform typically delivers meaningfully better outcomes than investing more in the M365 configuration. **What is the best free digital workplace platform?** Bitrix24 offers the most complete free tier in this category, supporting unlimited users with intranet, tasks, chat, and document management at no cost. eXo Platform also offers a free open-source Community edition for organizations willing to self-host and manage their own infrastructure. Most enterprise-grade platforms do not offer permanent free tiers, though most offer free trials. **How much does a digital workplace platform typically cost?** Enterprise and mid-market platforms are typically quote-based and structured per user per month, with pricing that varies by organization size, modules selected, and deployment model. Platforms with published pricing range from approximately $5-$15/user/month depending on tier. Microsoft Viva Suite is priced at $12/user/month on an annual commitment, on top of existing M365 licensing. Bitrix24 offers flat-fee plans from approximately $49/month, regardless of user count at the entry tier. **What is the best digital workplace platform for frontline workers?** Platforms designed for frontline reach need to work on personal mobile devices without a corporate email address or VPN, support communication in multiple languages, and deliver both operational workflows and company communications in one app. MangoApps was built for this use case from its founding, with 15+ years of frontline-first architecture and an adoption guarantee behind it. For smaller organizations or teams with budget constraints, Bitrix24 covers the basic communication and task needs at a lower entry cost. --- # Best Employee Engagement Platforms for 2026 **Author:** MangoApps Team **Published:** 2026-05-29 **Category:** employee-engagement Discover the best employee engagement platforms available in 2026, compare top options across recognition, listening, and all-in-one suites, and find the right fit for your organization. Employee engagement has a measurement problem: most organizations can tell when engagement is low (turnover climbs, productivity slips, managers start guessing at morale) but struggle to act on it systematically when it matters. A dedicated engagement platform closes that gap, giving HR, operations, and communications teams the tools to reach every employee, gather real signal, recognize contributions, and connect daily work to something larger. The right platform depends on whether your priority is listening, acting, recognizing, or all three. Software Best For Workforce Fit Platforms MangoApps Frontline-first engagement spanning communications, recognition, analytics, and learning in one platform All sizes; desk, frontline, field, and hybrid Web, iOS, Android, Desktop Culture Amp Science-backed employee feedback, industry benchmarking, and people analytics Mid-market to large enterprise; desk-focused Web, Desktop (limited mobile) Workvivo Communication-led engagement for distributed, hybrid, and frontline teams Mid-to-large; frontline, hybrid, and remote Web, iOS, Android, Desktop, digital signage Lattice All-in-one engagement and performance management with connected people programs Mid-market to enterprise; desk-focused Web, iOS, Android 15Five Continuous performance, high-frequency check-ins, and manager effectiveness SMB to mid-market; desk-focused Web, iOS, Android Qualtrics EmployeeXM Enterprise lifecycle listening, multi-modal surveys, and predictive attrition analytics Large enterprise; desk-focused Web, iOS, Android Achievers Global recognition, rewards fulfillment, and frontline engagement programs Mid-to-large enterprise; frontline-capable Web, iOS, Android Reward Gateway Recognition, benefits, communications, and wellbeing for dispersed workforces Mid-to-large; dispersed and frontline Web, iOS, Android --- MangoApps 4.6/5 Stars · Gartner Peer Insights 2M+ Users · Trusted Worldwide Gartner MQ Visionary · Intranet Packaged Solutions (2025) IDC MarketScape Leader · Employee Experiences (2024) Forrester Wave Strong Performer · Intranet Platforms (Q2 2026) Reworked IMPACT Award (Gold) · Intranet & Communications Platforms Most engagement platforms measure the problem without addressing the conditions that cause it. For organizations where the majority of the workforce is frontline, hourly, or field-based, the tools designed to drive engagement simply can't reach the employees who need them most. [MangoApps](https://www.mangoapps.com/) takes a different approach: it puts every workflow an employee needs (shift schedules, task completion, peer recognition, leadership communications, training, and compliance forms) into a single app that works on any personal device, with no corporate email required. The [Internal Communications Suite](https://www.mangoapps.com/solutions/internal-communications) handles multi-channel delivery with audience targeting and acknowledgment tracking, while [built-in analytics](https://www.mangoapps.com/analytics-insights) show exactly which content is landing and where employees haven't been reached. The [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee) backs every deployment: if employees don't adopt the platform after launch, you don't pay. **Key capabilities:** - **[Campaigns & Journeys](https://www.mangoapps.com/key-features/campaigns-and-journeys):** Structured, multi-step engagement campaigns that deliver content to specific employee segments across multiple channels simultaneously, with automated sequencing and acknowledgment tracking to confirm every employee has been reached. - **[Recognition & Kudos](https://www.mangoapps.com/apps/recognition):** Peer-to-peer and manager recognition built into the same feed employees check for news, schedules, and team updates, keeping appreciation visible and frequent without requiring a separate recognition tool or a separate login. - **[Analytics & Insights](https://www.mangoapps.com/analytics-insights):** Engagement tracking at the content, audience, and platform level, so communications and HR teams can see what is working, who is not being reached, and where to focus next, all without a separate analytics product. - **[Surveys](https://www.mangoapps.com/apps/surveys):** Pulse, engagement, eNPS, and exit surveys in one app, with per-survey anonymity controls, audience targeting by department, location, and role, automatic reminders to non-responders, and responses that feed directly into Mango Signal for close-the-loop action planning. - **[Integrations](https://www.mangoapps.com/integrations/):** 200+ pre-built connectors including Workday, SAP SuccessFactors, ADP, UKG, and Microsoft 365, so engagement activity flows in and out of the HR and operations systems already in use. **Customer proof:** > "We included a lot of important links on the MangoApps dashboard, such as marketing requests, IT requests, maintenance requests, etc. It really streamlined our processes and quickly made MangoApps the go-to space for our employees. With all of the resources we built within the application, getting employee engagement was very easy. We currently have over 90% monthly employee engagement." - Rebecca Wolfs, Director of Training, Development, and Compliance, [Columbia Basin Health Association (CBHA)](https://www.mangoapps.com/resources/columbia-basin-health-associate-case-study) CBHA, a federally qualified health center with frontline clinical staff making up over two-thirds of their workforce, set an original engagement target of 75% within two years. They reached 90%+ monthly engagement and have sustained it. **Free version:** No **Pricing:** Modular, quote-based; contact for enterprise pricing **Platforms:** Web, iOS, Android, Desktop [Schedule a demo to see MangoApps in action](https://www.mangoapps.com/schedule-a-call) Culture Amp Culture Amp is a purpose-built employee feedback and people analytics platform centered on survey science and organizational benchmarking. HR teams use it to run engagement surveys, performance cycles, and development programs, with results compared against an industry benchmarking dataset built from thousands of participating organizations. It is a strong fit for desk-based HR teams whose primary engagement challenge is rigorous measurement and data-driven action planning. - Science-backed survey templates developed by organizational psychologists, with demographic filtering to surface engagement patterns across teams, roles, and tenure segments - Industry benchmarking against thousands of organizations globally, with predictive analytics that flag flight-risk trends before they show up in turnover data - Integrated action-planning that assigns follow-up tasks after survey results are shared, creating a trackable loop from measurement to improvement **Free version:** No **Pricing:** Enterprise/custom; modular across Engage, Perform, and Develop; no public list pricing **Platforms:** Web, Desktop (browser-based); native mobile app limited to the Performance module [Explore Culture Amp](https://www.cultureamp.com/) Workvivo Workvivo is a communication-led employee experience platform built for distributed, hybrid, and frontline organizations. It combines a social activity feed, intranet, podcasts, livestreams, and peer recognition in a single app, with integrations across Microsoft 365, Google Workspace, and major HRIS platforms. Acquired by Zoom in 2023, it is well suited for organizations where internal communications and social connection are the primary engagement levers. - Consumer-grade social activity feed with livestreams, podcasts, and recognition shoutouts, designed to drive voluntary interaction rather than passive information consumption - Frontline and deskless access on personal devices, plus digital signage support for teams without personal devices on the job - Native employee listening and survey suite with sentiment analytics, embedded in the same platform as communications and recognition **Free version:** No **Pricing:** Enterprise/custom; no public list pricing; reported starting around $20,000/year for 200+ employees **Platforms:** Web, iOS, Android, Desktop, digital signage [Explore Workvivo](https://www.workvivo.com/) Lattice Lattice is an all-in-one people management platform connecting engagement surveys, performance reviews, goals and OKRs, and career development in a modular architecture. Thousands of organizations use it to build connected people programs where engagement data informs performance decisions and development outcomes. HR teams can activate specific capabilities and expand over time without changing platforms. - Engagement module with pulse surveys, eNPS, and lifecycle surveys, plus AI-generated insights to surface patterns in results - Multi-format performance reviews covering annual, quarterly, 360-degree, and project-based cycles, all tied to the same data model as engagement - Modular design connecting Performance, Goals, Engagement, Grow, and Compensation, so HR teams can start with one capability and expand as the program matures **Free version:** No (free trial available) **Pricing:** Paid; Talent Management at $11/user/month; Engagement add-on at $4/user/month; $4,000/year minimum; billed annually **Platforms:** Web, iOS, Android [Explore Lattice](https://lattice.com/) 15Five 15Five is a continuous performance and engagement platform built around high-frequency manager-employee check-ins and structured feedback rhythms. It is one of the few platforms in the category with fully transparent published pricing and a 14-day free trial, which makes it accessible for buyers who want to evaluate the product without a lengthy sales process. More focused on manager effectiveness and desk-based team dynamics than broad workforce engagement across large or frontline-heavy organizations. - Engage tier with pulse surveys, engagement benchmarking, and an HR Outcomes Dashboard that surfaces manager-level engagement trends - Lightweight weekly check-in format designed to surface employee needs, blockers, and morale shifts before they escalate to a manager or HR - Manager effectiveness tooling and structured microlearning to help team leaders build the habits that improve team-level engagement over time **Free version:** No (14-day free trial, no credit card required) **Pricing:** Paid; Engage at $4/user/month, Perform at $11/user/month, Total Platform at $16/user/month; annual billing **Platforms:** Web, iOS, Android [Explore 15Five](https://www.15five.com/) Qualtrics EmployeeXM Qualtrics EmployeeXM is an enterprise experience management platform with one of the deepest employee listening and analytics toolsets in the category. It covers the full employee lifecycle from candidate to exit, with AI-driven text analytics, attrition modeling, and support for listening programs across more than 20 languages. The platform is purpose-built for large organizations with dedicated people analytics teams and complex, multi-program survey requirements across a global workforce. - Lifecycle listening covering engagement, onboarding, exit, candidate experience, and 360-degree feedback within a single platform - AI-driven text analytics and predictive attrition modeling to identify flight-risk patterns before they appear in voluntary turnover data - Retention scenario modeling that simulates the projected impact of specific workforce interventions, giving HR leaders a data basis for investment decisions **Free version:** No **Pricing:** Enterprise/custom; no public list pricing; reported starting around $15,000/year **Platforms:** Web, iOS, Android [Explore Qualtrics EmployeeXM](https://www.qualtrics.com/employee-experience/) Achievers Achievers is a recognition and rewards platform focused on high-frequency, peer-driven appreciation across global and frontline workforces. It covers rewards delivery across 190+ countries through a marketplace with no markups or shipping fees, and pairs recognition data with its Achievers Listen module for ongoing voice-of-employee feedback. Built for organizations where recognition frequency and global rewards reach are the primary engagement levers. - Points-based peer-to-peer and manager recognition with a global rewards marketplace delivering across 190+ countries with no markups or shipping fees - Achievers Listen continuous listening module that connects recognition frequency data to employee survey results for a combined view of engagement health - Deep HCM integrations with Workday, SAP, and Microsoft 365, plus frontline mobile access via QR code for employees without corporate devices **Free version:** No **Pricing:** Enterprise/custom; designed for organizations of 500+ employees; no public list pricing **Platforms:** Web, iOS, Android [Explore Achievers](https://www.achievers.com/) Reward Gateway Reward Gateway is a unified employee engagement hub combining recognition, rewards, benefits, communications, surveys, and wellbeing in a single platform. It operates across 23+ countries and is built for organizations with dispersed or frontline workforces, where employee benefits and perks are an active component of the engagement strategy alongside peer recognition and internal communications. - Multi-directional recognition with automated spot awards, long-service milestones, and a benefits and discounts marketplace integrated into the same experience - Branded communications feed with segmented targeting for different employee groups, including frontline and deskless teams without corporate email - AI-assisted engagement analytics spanning recognition activity, survey responses, and wellbeing program participation, giving HR teams a consolidated view of engagement across all program areas **Free version:** No **Pricing:** Enterprise/custom; quote-based for most deployments; no public list pricing for enterprise tiers **Platforms:** Web, iOS, Android [Explore Reward Gateway](https://www.rewardgateway.com/) ## What Is an Employee Engagement Platform? An employee engagement platform is software that gives organizations the tools to measure, influence, and sustain how connected employees feel to their work, their team, and the organization's direction. The category spans four distinct types of tools: listening and survey platforms that gather employee feedback at scale, recognition and rewards systems that reinforce contributions and belonging, all-in-one suites that connect engagement data to performance and development outcomes, and communication-led platforms that drive engagement through better information flow and social connection. What these tools share is a focus on the gap between employees doing their jobs and employees genuinely caring about the outcomes. The most effective platforms close that gap through ongoing, real-time mechanisms rather than annual surveys and end-of-year reviews. For organizations with a significant frontline workforce, this also means building engagement channels that reach workers who don't sit at a desk, don't carry a company-issued laptop, and are unlikely to log into a separate HR portal to find out what is happening across the organization. ## Why Employee Engagement Matters for Your Business The cost of getting engagement wrong is not abstract. According to Gallup's [State of the Global Workplace 2024](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) report, employee disengagement costs the global economy $8.8 trillion annually (9% of global GDP). Only 23% of employees worldwide report being engaged at work. Engaged teams, by contrast, deliver 23% higher profitability, 14% higher productivity, and as much as 51% lower turnover than disengaged counterparts, according to Gallup's broader workforce research. Recognition compounds that effect: employees who receive strong, consistent recognition are 20 times more likely to be engaged than those who receive poor recognition. The retention math is equally significant. Employees who feel genuinely connected to their organization's culture are 55% less likely to be watching for other jobs, according to Gallup. For industries with high frontline turnover (retail, healthcare, hospitality, and logistics), even modest improvements in engagement translate directly into lower replacement costs, faster ramp times, and better customer outcomes. Replacing a frontline or hourly worker costs approximately 40% of their annual salary, according to Gallup's workforce data. That figure scales quickly in organizations where hundreds of frontline positions turn over each year. A dedicated engagement platform is not a cultural investment in the abstract; for most organizations, it is one of the highest-return operational decisions available to HR and operations leadership. ## What to Look for in an Employee Engagement Platform Not every organization needs the same things from an engagement platform. But six capabilities are worth evaluating in any shortlist: **Multi-channel reach, including mobile.** A platform that can only reach employees with corporate email misses the majority of most frontline workforces. Look for native iOS and Android apps that work on personal devices and do not require a company email address to activate. For organizations with shift workers or field staff, digital signage support and SMS delivery are worth evaluating as well. **Measurement and external benchmarking.** Survey results are more actionable when they can be compared against an industry baseline, not just your own prior-year data. Platforms with large benchmarking datasets allow HR teams to understand whether engagement levels are improving in absolute terms or just drifting relative to the broader market. **Recognition tools.** Frequent, visible recognition is one of the highest-leverage engagement interventions available. Whether that capability is native to the platform or built through an integration with a dedicated recognition tool, it should be part of any engagement architecture. Recognition that lives in a separate system from where employees already spend their time tends to see low participation. **Analytics and action-planning.** Measuring engagement without the ability to act on findings is measurement theater. The most effective platforms connect survey results to recommended actions, track follow-through at the manager and team level, and show how changes in practice show up in subsequent engagement data. **HRIS and operations integration.** Engagement platforms work best when they share data with the systems already in use. Native integrations with platforms like Workday, SAP SuccessFactors, ADP, UKG, and Microsoft 365 reduce the administrative overhead of managing separate systems and give HR teams a more complete picture of workforce health. **Administrative ease.** The best engagement platform is the one administrators actually keep current and employees genuinely open. Evaluate how much IT involvement is required for configuration, how easy it is for non-technical admins to publish content and run surveys, and how quickly new employees can be onboarded onto the platform. ## How to Choose the Right Employee Engagement Platform The most important variable in selecting an employee engagement platform is workforce composition. A platform built for desk-based knowledge workers will underperform for a retail chain, a healthcare system, or a manufacturing company where the majority of employees are on the floor, in the field, or working a shift schedule without a company device. Before comparing features or pricing, determine what percentage of your workforce can realistically be reached by each platform under consideration, and whether that reach is limited to employees with a corporate email address. After workforce fit, identify what the primary engagement challenge actually is. Organizations that struggle with low survey participation and limited visibility into employee sentiment need a listening-first platform with strong analytics and action-planning. Organizations where retention is driven by under-recognized contributions need a recognition and rewards platform with high adoption frequency and accessible reward delivery. Organizations where engagement breaks down because employees feel uninformed or disconnected from leadership need a communications-led platform with targeted reach and two-way interaction. Organizations facing all three challenges are likely best served by a platform that addresses them without requiring a separate vendor contract for each. For organizations with a large frontline workforce or multi-channel communications needs, [MangoApps](https://www.mangoapps.com/) is worth including in any shortlist: it addresses all three challenges in a single platform, with a modular deployment model that lets organizations start where the need is greatest and expand when they are ready. --- # The Best Employee Apps for Hourly and Frontline Workers in 2026 (No Corporate Email Required) **Author:** MangoApps Team **Published:** 2026-05-29 **Category:** employee-app Ten employee apps for hourly and deskless teams compared on no-email login, schedules, tasks, HR self-service, integrations, and pricing, with guidance by industry. > **Quick answer:** The best employee apps for hourly and frontline workers let staff sign in without a corporate email, put schedules, tasks, pay, and policies on a personal phone or shared device, and connect to the HR system of record. In 2026 the most-shortlisted options are MangoApps (a unified super app for mixed desk and frontline workforces), WorkJam (enterprise retail and hospitality scheduling and tasks), Connecteam (small and mid-sized teams, with a free tier), Blink and Beekeeper (frontline-first communication), and Flip, YOOBIC, Zipline, Speakap, and Sociabble for specific communication, execution, or branding needs. Most workforce technology is built for employees who sit at a desk, log in to a computer, and check a corporate inbox. That describes a minority of the workforce. Deskless workers make up 70 to 80% of the global workforce, about 2.7 billion people, according to [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology), and 58% of American workers are on the frontline, according to [JLL](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention). For the retail associates, hospital aides, warehouse crews, and hotel staff who make up that majority, a purpose-built employee app is the only tool that actually reaches them. Hourly workers add a further constraint. They are paid by the shift, they often share devices, and they were never issued an inbox. "Download the app and sign in with your work email" excludes them by design. Only 23% of frontline workers believe they have access to the technology they need to be productive, per [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html). This guide compares the ten employee apps most often shortlisted for hourly and frontline teams, explains what makes an app work without corporate email, and covers the super-app question, integrations, pricing, and industry fit. Software Best For No-email login Schedules / Tasks / HR self-service Platforms Pricing model MangoApps Enterprises that want communications, schedules, tasks, training, and HR in one app for frontline and desk staff Yes (HRIS-provisioned) Native / Native / Native Web, iOS, Android, Desktop Modular suites, quote-based WorkJam Enterprise retail, hospitality, and supply chain teams needing shift scheduling, task execution, and earned wage access Yes Native / Native / Partial iOS, Android, Web, Kiosk Enterprise, quote-based Connecteam Small and mid-sized deskless teams needing scheduling, time tracking, and communications in one affordable app Yes Native / Native / Partial iOS, Android, Web Free tier; flat tiers per hub Blink Frontline-only organizations wanting a branded super-app with social engagement and micro-app integrations Yes (SMS, QR) Via micro-apps / Light / Via micro-apps iOS, Android, Web, Desktop Quote-based tiers Beekeeper (LumApps) Frontline-only workforces needing communication plus no-code forms, workflows, and translation across many languages Yes Via integration / Native (forms) / Via integration Web, iOS, Android Tiered, quote-based Flip Enterprises wanting a fully branded AI-native app with HRIS mini-apps and no corporate email requirement Yes Via HRIS / Partial / Via HRIS iOS, Android, Web Enterprise, quote-based YOOBIC Multi-location organizations combining daily communications, microlearning, and task execution Yes Via integration / Native / Via integration iOS, Android, iPad, Web Enterprise, quote-based Zipline Retail chains needing store-level execution, compliance, and role-targeted communications across 100+ locations Yes Via integration / Native / Via integration iOS, Android, Web, Tablet Per location, quote-based Speakap Mid-market frontline industries wanting a white-label app with multilingual support and low IT involvement Yes Via integration / Light / Via integration Web, iOS, Android Tiered, quote-based Sociabble Organizations prioritizing internal communications, multilingual delivery, and employee advocacy in one branded app Yes Via integration / Light / Via integration iOS, Android, Web, Desktop Per user with add-ons, quote-based *Capability, login, integration, pricing, and certification statements for third-party vendors are taken from each vendor's public documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps. "Partial" means the capability exists but depends on configuration or a licensed add-on; "Via integration" means the vendor relies on a third-party system.* MangoApps 4.6/5 Stars · Gartner Peer Insights 2M+ Users · Trusted Worldwide Gartner MQ Visionary · Intranet Packaged Solutions (2025) IDC MarketScape Leader · Employee Experiences (2024) Forrester Wave Strong Performer · Intranet Platforms (Q2 2026) Reworked IMPACT Award (Gold) · Intranet & Communications Platforms **Best for:** Enterprise organizations with large hourly, frontline, or deskless workforces that need communications, schedules, tasks, training, and HR in one platform rather than across multiple apps, and that also have desk-based managers and staff who should use the same app. Most employee apps solve one problem well: getting a message from headquarters to a store floor. [MangoApps](https://www.mangoapps.com/) is built to solve the whole problem. As the AI-Ready Employee Platform for the Frontline, it gives every employee a single app for communications, shift scheduling and time, HR self-service, task execution, training, and knowledge, with no corporate email address required. Where point solutions force workers to switch between apps and administrators to manage separate vendors, MangoApps runs its workflow suites on one platform, accessible from one login on any device employees already carry. Every deployment is backed by an [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee): 90%+ active user adoption in the first 90 days, or MangoApps works to make it right. **Key capabilities:** - **[Branded Employee App](https://www.mangoapps.com/solutions/employee-app):** Every employee, desk and frontline, opens the same app with no company email, no VPN, and no IT-managed hardware required. One login covers every workflow from shift scheduling to company news to HR records. - **[Internal Communications Suite](https://www.mangoapps.com/solutions/internal-communications):** Multi-channel delivery with audience targeting and acknowledgment tracking, with read receipts and engagement analytics to confirm the message landed. - **[Critical Alerts](https://www.mangoapps.com/key-features/critical-alerts):** Time-sensitive messages with mandatory read receipts and delivery confirmation so urgent communications are never lost in a feed or left unread. - **[Workforce Operations](https://www.mangoapps.com/solutions/workforce-operations):** Shift scheduling with AI-assisted creation, swaps and coverage requests, mobile clock-in with geofencing, task dispatch and checklists, all in the same app employees use for news and HR. - **[Learning and Knowledge](https://www.mangoapps.com/solutions/learning-management):** Training assigned by role and location, plus policies and SOPs with AI search that returns permission-correct answers. - **[Analytics and Insights](https://www.mangoapps.com/analytics-insights):** Real-time data on message reach, content engagement, and workflow completion by location and team. **Hourly-worker fit:** Schedules, swaps, mobile clock-in, tasks, pay stubs, and PTO in one app; kiosk and shared-device support for break rooms and plant floors; offline access and translation. **Login without corporate email:** Accounts are provisioned from the HRIS and activated on a personal phone or shared device; no email, VPN, or managed hardware required. **HR and scheduling integrations:** [200+ out-of-the-box integrations](https://www.mangoapps.com/integrations), including Workday, UKG, ADP, Paylocity, SAP SuccessFactors, Rippling, and BambooHR for HRIS; Okta, Microsoft Entra ID, Active Directory, and LDAP for identity; Microsoft 365 and Google Workspace; Cornerstone and Workday Learning. [Benchmark Human Services](https://www.mangoapps.com/customers/benchmark-human-services), a healthcare services organization with more than 4,000 employees, deployed MangoApps specifically to reach frontline caregivers who have no corporate email and work in client homes across the country. Over one-third of employees incorporated the app into their daily work within a few months of launch. "We really needed a system where we could communicate with our workers. And that's how we ultimately came to MangoApps," said Courtney Heiser, Director of Communications, Benchmark Human Services. In retail, A.S. Watson Benelux reached 80%+ active user adoption across 16,000 Kruidvat employees, with more than 20,000 retail workers receiving weekly schedules through the MangoApps mobile app. **Free version:** No **Pricing:** Modular suites, quote-based; contact for enterprise pricing **Platforms:** Web, iOS, Android, Desktop [Schedule a demo to see MangoApps in action](https://www.mangoapps.com/schedule-a-call) WorkJam **Best for:** Enterprise retail, hospitality, and supply chain organizations that need shift scheduling, workforce communications, task execution, and earned wage access in a single frontline platform. WorkJam is a digital frontline workplace platform that combines communications, shift scheduling, task management, and earned wage access in one app. It targets large hourly workforces across multiple locations where coordinating open shifts, task completion, and time-sensitive announcements is a daily operational challenge. **Key capabilities:** - Open shift marketplace and employee-driven self-service scheduling, including shift swapping and availability management - Task management with photo verification so managers can confirm store or site execution without being on location - ExpressPay earned wage access, giving hourly employees on-demand access to wages they have already earned **Hourly-worker fit:** Scheduling and swaps are the core of the product; earned wage access is a direct hourly-worker benefit; kiosk mode supports shared devices. **Login without corporate email:** Yes (vendor-stated); confirm the activation method for your workforce. **HR and scheduling integrations:** Enterprise HRIS and WFM integrations (vendor-stated). **Free version:** No **Pricing:** Enterprise; contact for pricing **Platforms:** iOS, Android, Web, Kiosk [Explore WorkJam](https://www.workjam.com/) Connecteam **Best for:** Small and mid-sized deskless teams that need scheduling, time tracking, task management, and communications in a single affordable app, including organizations getting started with workforce technology. Connecteam is an all-in-one workforce management app built for deskless teams, bundling communications, scheduling, GPS time tracking, task management, and basic HR tools in a flat-rate platform organized into Operations, Communications, and HR and Skills hubs. Its free tier makes it one of the most accessible options in the category for small businesses and growing teams evaluating employee apps for the first time. **Key capabilities:** - Free plan for up to 10 users, with paid tiers starting at a flat rate for the first 30 employees - Operations, Communications, and HR and Skills hubs covering scheduling, time clock with GPS, forms, checklists, courses, and document management - Built-in shift scheduling and job dispatch alongside team chat and company news feed **Hourly-worker fit:** Native scheduling, GPS time clock, and checklists; the strongest hourly-worker fit in the SMB tier. **Login without corporate email:** Yes; mobile-first onboarding. **HR and scheduling integrations:** Payroll and HR integrations (vendor-stated); enterprise HRIS depth is more limited than the enterprise platforms in this guide. **Free version:** Yes (free for up to 10 users) **Pricing:** Basic from $29/month for the first 30 users, priced per hub; annual billing saves 18% ([connecteam.com/pricing](https://connecteam.com/pricing/), September 2026); Enterprise available **Platforms:** iOS, Android, Web [Explore Connecteam](https://connecteam.com/) Blink **Best for:** Frontline-only organizations that want a consumer-grade mobile super-app experience without requiring employees to have a corporate email address or managed device. Blink is a mobile super-app built from the ground up for frontline and deskless workers, delivering a branded news feed, secure chat, and HR document access in a single app that employees open on their personal phone. It bridges the desk and deskless divide by connecting workers who lack corporate email or device management to the same communications and self-service tools their office-based colleagues use. **Key capabilities:** - Social-feed newsfeed with a personalized content algorithm and full white-label branding, including app name, icon, and branded SMS onboarding invites - Micro-app integrations for payslips, rostering, and an SSO browser that surfaces SharePoint and other intranet content without requiring additional Microsoft licenses - Analytics to track communication reach and engagement by team, manager, and location **Hourly-worker fit:** Strong for communication and document access; schedules and pay are surfaced from existing systems through micro-apps rather than managed in the app. **Login without corporate email:** Yes; QR code and SMS login. **HR and scheduling integrations:** Microsoft 365, Workday, SAP (vendor-stated); rostering via micro-apps. **Free version:** No (free trial available) **Pricing:** Business and Enterprise tiers; contact for pricing **Platforms:** iOS, Android, Web, Desktop [Explore Blink](https://www.joinblink.com/) Beekeeper (LumApps) **Best for:** Frontline-only or frontline-heavy organizations whose hourly workers need communication plus forms, workflows, and translation across many languages, particularly in hospitality, manufacturing, and logistics. Beekeeper is a frontline success platform built exclusively for deskless workers. Its combination of targeted news streams, secure messaging, voice messaging, AI translation across 200+ languages, and no-code forms and workflows suits workforces that need more than a news feed. [LumApps agreed to acquire Beekeeper on July 2, 2025](https://www.lumapps.com/insights/news/lumapps-and-beekeeper-to-join-forces-creating-the-leading-employee-experience-platform-for-the-future-of-work), positioning the combined company as an AI-powered employee hub for frontline and desk workers; buyers should ask about the integrated roadmap. **Key capabilities:** - Streams (targeted news feeds), secure 1:1 and group chat, and voice messaging designed to replace unauthorized personal messaging apps - Inline AI translation across 200+ languages with AI-generated chat summaries - No-code workflows and offline-capable forms, with shift management through HRIS, LMS, and payroll integrations **Hourly-worker fit:** Strong for multilingual communication and forms; scheduling and pay depend on integrations. **Login without corporate email:** Yes. **HR and scheduling integrations:** HRIS, LMS, and payroll integrations (vendor-stated). **Free version:** No (14-day free trial available) **Pricing:** Tiered; custom quote **Platforms:** Web, iOS, Android [Explore Beekeeper](https://www.beekeeper.io/) Flip **Best for:** Enterprises that want a fully branded, AI-native employee app with deep HRIS integrations and onboarding that requires no corporate email address. Flip is an AI-native employee app designed for frontline teams, connecting workers to communications, HR self-service, and operational workflows through an app submitted to the App Store under the employer's own brand name. It integrates directly with enterprise HRIS platforms to surface payslips, shift information, and leave requests inside the branded app, with no company device or email account required. **Key capabilities:** - Fully branded app published under the employer's name and icon on the App Store and Google Play (Enterprise plan) - HR Mini-Apps connecting Workday, SAP SuccessFactors, and UKG for payslips, leave requests, and shift access inside the app - 30+ language support with automatic translation for multilingual frontline teams **Hourly-worker fit:** Payslips, shifts, and leave are visible inside the app, drawn from the HRIS; native scheduling and task depth are lighter than operations-first platforms. **Login without corporate email:** Yes. **HR and scheduling integrations:** Workday, SAP SuccessFactors, UKG via HR Mini-Apps and API (vendor-stated); integrations are priced separately and require implementation effort (vendor-stated). **Free version:** No (pilot available) **Pricing:** Enterprise; contact for pricing **Platforms:** iOS, Android, Web [Explore Flip](https://www.getflip.com/) YOOBIC **Best for:** Multi-location retail, hospitality, and consumer goods organizations that need communications, microlearning, and task management in a single app for frontline teams. YOOBIC is a frontline employee experience platform that brings communications, microlearning, and task management together in one app for distributed teams. It serves organizations operating large numbers of locations that need a consistent way to deliver daily briefings, training content, and operational checklists to store or site employees. **Key capabilities:** - Combined communications, learning, and task execution in a single app, removing the need for separate training and comms tools - Photo and video task verification for store compliance, visual merchandising, and audit workflows - Gamified social newsfeed with recognition features designed to drive daily engagement from frontline staff **Hourly-worker fit:** Strong for daily tasks and microlearning; scheduling and HR self-service depend on integrations. **Login without corporate email:** Yes. **HR and scheduling integrations:** Vendor-stated; confirm named systems for your stack. **Free version:** No **Pricing:** Enterprise; contact for pricing **Platforms:** iOS, Android, iPad, Web [Explore YOOBIC](https://www.yoobic.com/) Zipline **Best for:** Retail chains with 100 or more locations that need a purpose-built store execution platform for communications, task management, and operational compliance. Zipline is a store execution platform built specifically for retail operations, combining communications, task management, learning content, and compliance workflows in an app designed by retail practitioners for store teams. It targets multi-location chains where consistent execution across every location, not just the flagship, is the primary operational objective. **Key capabilities:** - Retail-native task management with a role-targeted daily digest that surfaces the right priorities for each employee at the start of every shift - Store-level communications with read confirmation, execution tracking, and audit-ready compliance records - Learning and documentation integrated into the same daily workflow so training reaches employees as part of the shift **Hourly-worker fit:** Strong for store associates' daily tasks and briefings; scheduling and pay live in other systems. **Login without corporate email:** Yes. **HR and scheduling integrations:** Vendor-stated; confirm named systems for your stack. **Free version:** No **Pricing:** Enterprise; priced per location, contact for pricing **Platforms:** iOS, Android, Web, Tablet [Explore Zipline](https://www.getzipline.com/) Speakap **Best for:** Mid-market retail, hospitality, manufacturing, construction, and logistics organizations that want a fully white-labeled frontline app deployed quickly without heavy IT involvement, including across multiple countries. Speakap is a fully white-labeled employee experience app purpose-built for frontline industries. Organizations brand the app entirely as their own, with rapid setup that does not require significant IT involvement. It suits mid-market buyers who want a polished, frontline-focused tool without the complexity or cost of enterprise platforms, and organizations operating across several countries that need multilingual support out of the box. **Key capabilities:** - Fully white-labeled mobile app under the customer's own brand, with fast deployment and minimal IT dependency - Employee Journeys for guided onboarding, recurring training, and targeted news with read acknowledgments and polls - Multilingual support across 20+ languages with an API marketplace for HR, scheduling, and POS systems behind a single sign-on **Hourly-worker fit:** Strong for branded communication and onboarding journeys; schedules and pay depend on the API marketplace integrations. **Login without corporate email:** Yes. **HR and scheduling integrations:** HR, scheduling, and POS via API marketplace (vendor-stated). **Free version:** No **Pricing:** Basic, Premium, and Premium+ tiers; quote-based **Platforms:** Web, iOS, Android [Explore Speakap](https://www.speakap.com/) Sociabble **Best for:** Mid-market and enterprise organizations that want a fully branded employee communications app with multilingual delivery and built-in employee advocacy tools. Sociabble is an employee communications platform with a fully branded mobile app that connects frontline workers and desk employees to company news, training content, and advocacy programs. It suits organizations that need to reach large, multilingual workforces through a single branded channel while also activating employees as external brand ambassadors. **Key capabilities:** - Fully branded mobile app with custom name, logo, icon, and colors, deployable across iOS, Android, and web - Employee advocacy and gamification built into the platform - Multichannel and multilingual content delivery with automatic translation and integrations to Workday, ServiceNow, and SAP **Hourly-worker fit:** Strong for reach and engagement; scheduling, tasks, and HR self-service depend on integrations. **Login without corporate email:** Yes. **HR and scheduling integrations:** Workday, ServiceNow, SAP (vendor-stated). **Free version:** No **Pricing:** Per user with add-on modules; contact for pricing **Platforms:** iOS, Android, Web, Desktop [Explore Sociabble](https://www.sociabble.com/) ## What makes an employee app work for hourly workers without corporate email? An employee app works for hourly workers when identity comes from the HR system rather than the email system, when it runs on personal phones and shared devices, when it works offline and in the worker's language, and when it holds the things an hourly worker needs every shift: the schedule, the clock, the checklist, and the pay stub. Communication succeeds because it rides along with that utility. ### Identity without an inbox The threshold requirement is a sign-in method that does not depend on a corporate email account. The common options are a one-time code sent by SMS to a personal phone, a QR code on a break-room poster that opens the app and pre-fills the employer, an employee ID plus PIN, a badge tap on a shared device, or a username provisioned automatically from the HRIS. The compliance requirement underneath all of them is lifecycle: the HRIS creates the account on hire day and removes it on termination day, with no administrator maintaining a list. ### Shared devices and BYOD Many hourly environments restrict personal phones on the floor. The app needs a kiosk mode with fast user switching and automatic sign-out, and biometric login for personal devices. On a personal phone, workers want to know what the employer can and cannot see. A plain-language privacy statement at first sign-in is not a legal formality; the [12 reasons frontline adoption fails](https://www.mangoapps.com/articles/frontline-intranet-adoption-failures) diagnostic identifies ambiguous data policies as a direct cause of app deletion. ### Connectivity and language Basements, stockrooms, rural sites, and hospital wings all lose signal. Offline access to schedules, policies, and checklists, with sync when the connection returns, is a requirement rather than a feature. Automatic translation of posts, comments, and policies matters for the same reason: a safety notice that only exists in English does not reach the crew that needs it. ### Day-one utility Schedules and pay are why hourly workers open an app every day. News, recognition, and surveys ride along. An app that only carries news is optional; an app that carries the schedule is not. | No-email access method | Best for | Setup effort | Security notes | Apps that publish support for it | |---|---|---|---|---| | SMS one-time code | Workers with personal phones | Low | Phone number becomes the identity; protect with device binding | Blink; MangoApps and others via HRIS-provisioned credentials | | QR onboarding code | Launch-day floor sign-up | Low | Codes should expire and be tied to a site | Blink, Oak-style frontline apps; MangoApps supports QR sign-up | | Employee ID and PIN | Shared devices, kiosks | Medium | Enforce PIN complexity and lockout | WorkJam and Connecteam kiosk modes (vendor-stated) | | Badge or NFC tap | Plant floors, hospitals | Medium to high | Requires badge infrastructure | Vendor-stated; verify per platform | | HRIS-provisioned username | Enterprises with an HRIS of record | Medium (one-time integration) | Lifecycle managed by the HRIS; strongest audit story | MangoApps, Flip (via HRIS), enterprise platforms | *Methods listed per vendor are vendor-stated from public documentation as of September 2026. Verify the exact activation flow for your workforce in the demo.* For the intranet-side view of the same features, see [9 Modern Employee Intranet Features That Reach Frontline Staff Without Email](https://www.mangoapps.com/articles/intranet-features-that-reach-frontline-workers). ## What should an employee super app include for hourly teams? An employee super app puts communications, schedules and shift swaps, time and attendance, tasks and checklists, training, HR self-service (pay, PTO, benefits, policy acknowledgment), knowledge and SOP search, and recognition on one login, one employee record, and one notification center. The test is not the length of the feature list. It is whether an hourly worker can do everything their shift requires without leaving the app. | Capability | Why hourly teams need it | Native in | What "bolted on" looks like | |---|---|---|---| | Targeted communication with acknowledgment | Safety and policy notices need proof of receipt by site | All ten apps | Opens counted, acknowledgments not | | Schedules and shift swaps | The daily reason to open the app | MangoApps, WorkJam, Connecteam | A link to the scheduler's login page | | Time and attendance | Hourly pay depends on it | MangoApps, WorkJam, Connecteam | A separate time-clock app | | Tasks and checklists with photo proof | Store and site execution | MangoApps, WorkJam, Connecteam, YOOBIC, Zipline | Tasks in email or a paper binder | | Training and certifications | Compliance, onboarding | MangoApps, Connecteam, YOOBIC, Zipline | A separate LMS login | | HR self-service (pay, PTO, benefits) | Fewer manager questions | MangoApps native; Flip, Blink via HRIS surfaces | A web link to the HRIS | | Knowledge and SOP search | Answers on the floor | MangoApps | A shared drive | | Recognition and surveys | Engagement and voice | MangoApps, Blink, Beekeeper, YOOBIC, Sociabble, Speakap | A separate engagement tool | *Native capability statements for third-party vendors are vendor-stated from public documentation as of September 2026.* The consolidation case is arithmetic. The average company runs 101 applications, and companies with more than 5,000 employees average 131, according to [Okta's Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/). A [Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) study found workers toggling between applications roughly 1,200 times a day, about four hours a week spent reorienting. A super app is fewer apps for the worker and fewer vendors, integrations, and identity models for IT. It is also the reason employee apps work as a work hub rather than a newsfeed, an argument laid out in [Why the Employee App Market Is Really a Consolidation Problem](https://www.mangoapps.com/articles/employee-app-market-consolidation-problem). A super app is the wrong answer in three situations. Teams under 500 employees usually want Connecteam's free tier and flat pricing more than they want a platform. Organizations with a single acute need and no consolidation roadmap can buy a point tool. And organizations that must keep an incumbent workforce management system should choose a super app that coexists with it rather than one that requires replacing it. ## How do employee apps connect to scheduling, payroll, and HR systems? The HRIS and the scheduling system stay the systems of record. The employee app syncs people, roles, locations, and schedules in, and pushes clock-ins, approved swaps, acknowledgments, and training completions back. What separates vendors is whether each connection is a native connector the vendor maintains, an API your team builds against, or a partner build owned by a third party. | Integration | Data direction | Why it matters for hourly workers | Verify in the demo | |---|---|---|---| | HRIS (Workday, UKG, ADP, SAP SuccessFactors, Paylocity, BambooHR, Rippling) | In: people, roles, locations, managers. Out: data changes, acknowledgments | Accounts, targeting, and permissions stay current without manual upkeep | Create and terminate a worker in a sandbox; watch access appear and disappear | | Scheduling and WFM (keep or replace) | In: published schedules. Out: swaps, availability | Workers see the real schedule; approvals reach payroll | Request a swap; trace the approval | | Payroll and pay stubs | In: pay stubs. Out: approved time | Fewer questions to managers | Open a pay stub as a worker | | Time clock | Out: clock-ins with location | Hourly pay accuracy | Clock in with geofencing on a phone | | LMS (Cornerstone, Workday Learning, or native) | In: assignments. Out: completions | Compliance records | Complete a course; find the record in the HRIS | | Identity (Okta, Microsoft Entra ID, Active Directory, LDAP, SCIM) | In: accounts for staff who have them | Desk staff use existing credentials | SSO for a manager; no-email login for an associate | | Microsoft 365 and Google Workspace | In: documents, calendars | Policies live here | Search a SharePoint policy from the app | | Earned wage access (for example, WorkJam ExpressPay) | Out: earned hours | Hourly-worker benefit | Vendor-stated; confirm availability | MangoApps publishes [200+ out-of-the-box integrations](https://www.mangoapps.com/integrations), including Workday, UKG, ADP, Paylocity, Namely, BambooHR, SAP SuccessFactors, and Rippling, along with Okta, Entra ID, Active Directory, LDAP, Microsoft 365, Google Workspace, Cornerstone, and Workday Learning. For any vendor, ask the same three questions per system: native, API, or partner; who maintains it; and where the release notes are. ## How much do employee apps for hourly workers cost? Employee apps for hourly workers follow four pricing models: quote-based per user (most enterprise apps), per location (Zipline), flat tiers with a free plan (Connecteam), and modular suites (MangoApps). Most enterprise vendors do not publish prices; Connecteam does. | Vendor | Model | Published price? | Free tier or trial | Typical buyer | |---|---|---|---|---| | MangoApps | Modular suites, quote-based | No | No | Mid-market to enterprise | | WorkJam | Per user, quote-based | No | No | Enterprise retail, hospitality, supply chain | | Connecteam | Flat tiers per hub | Yes: free for up to 10 users; Basic from $29/month for the first 30 users; annual billing saves 18% ([connecteam.com/pricing](https://connecteam.com/pricing/), September 2026) | Free plan; 14-day trial | SMB and mid-market | | Blink | Business and Enterprise tiers, quote-based | No | Free trial | Frontline-only mid-market to enterprise | | Beekeeper (LumApps) | Tiered, quote-based | No | 14-day trial | Frontline-heavy mid-market to enterprise | | Flip | Per user or banded tiers, quote-based; integrations priced separately (vendor-stated) | No | Pilot | Enterprise | | YOOBIC | Enterprise, quote-based | No | No | Multi-location retail and hospitality | | Zipline | Per location, quote-based | No | No | Retail chains with 100+ locations | | Speakap | Basic, Premium, Premium+ tiers, quote-based | No | No | Mid-market frontline | | Sociabble | Per user with add-on modules, quote-based | No | No | Mid-market to enterprise communications | *Pricing statements for third-party vendors are vendor-stated from public pages as of September 2026 and change frequently.* Total cost is more than the subscription. Add integration fees, onboarding and implementation, the internal effort to maintain API integrations, and, on the other side of the ledger, the tools you retire. The largest hidden cost is a second migration when a communication-only app has to be joined by scheduling, tasks, and training tools two years later. MangoApps' [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee) transfers a different risk: if employees do not adopt within 90 days, the vendor works to make it right. ## Which employee apps fit retail, healthcare, hospitality, manufacturing, and logistics? | Industry | Hourly-workforce reality | Must-have capabilities | Apps most often shortlisted | Compliance to verify | |---|---|---|---|---| | Retail and grocery | Multi-location, high turnover, schedules change weekly | Schedules and swaps, tasks with photo proof, no-email login, translation | MangoApps, WorkJam, Zipline, YOOBIC | Wage-and-hour notice acknowledgment, OSHA, PCI awareness | | Healthcare and home care | Caregivers in client homes and wards, no corporate email, handoff risk | Critical alerts with acknowledgment, secure messaging, compliance training | MangoApps, Blink, Beekeeper | HIPAA (business associate agreement), HITRUST | | Hospitality and food service | Multilingual, shared devices, seasonal staff | Translation, schedules on personal phones, daily briefings, recognition | MangoApps, WorkJam, Beekeeper, Speakap, YOOBIC | Food safety training records, wage-and-hour | | Manufacturing | Plant floors with phone restrictions, safety-critical notices | Kiosk mode, safety alerts, SOP access, certifications | MangoApps, Beekeeper, Flip, Speakap | OSHA, ISO, GMP training records | | Logistics and field service | Drivers and technicians, low connectivity | Offline access, dispatch and tasks, geofenced clock-in | MangoApps, Connecteam, Beekeeper | DOT, safety training | In retail, A.S. Watson Benelux reached 80%+ active use across 16,000 Kruidvat employees and [Raley's](https://www.mangoapps.com/resources/raleys-case-study) connected 20,000 grocery employees on MangoApps. In healthcare, [Benchmark Human Services](https://www.mangoapps.com/customers/benchmark-human-services) reached 4,000+ caregivers who never had corporate email. ## Employee app comparison matrix | App | Communication | Schedules and swaps | Time and attendance | Tasks and checklists | Training | HR self-service (pay, PTO) | Knowledge and SOP search | Recognition | No-email login | |---|---|---|---|---|---|---|---|---|---| | MangoApps | Native | Native | Native | Native | Native | Native | Native | Native | Yes | | WorkJam | Native | Native | Native | Native | Partial | Partial | Partial | Partial | Yes | | Connecteam | Native | Native | Native | Native | Native | Partial | Partial | Partial | Yes | | Blink | Native | Via micro-apps | Via micro-apps | Light | Via integration | Via micro-apps | Partial | Native | Yes | | Beekeeper (LumApps) | Native | Via integration | Via integration | Native (forms) | Via integration | Via integration | Partial | Native | Yes | | Flip | Native | Via HRIS | Via HRIS | Partial | Via integration | Via HRIS | Partial | Native | Yes | | YOOBIC | Native | Via integration | Via integration | Native | Native | Via integration | Partial | Native | Yes | | Zipline | Native | Via integration | Via integration | Native | Native | Via integration | Partial | Light | Yes | | Speakap | Native | Via integration | Via integration | Light | Partial (journeys) | Via integration | Light | Native | Yes | | Sociabble | Native | Via integration | Via integration | Light | Partial | Via integration | Light | Native | Yes | *Cells reflect vendor documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps.* ## What Is Employee App Software? An employee app is a mobile-native platform that gives every worker, whether they sit at a desk or clock in at a store, a single point of access to the communications, tools, and information they need to do their job. Unlike enterprise software built around corporate email addresses and company-issued laptops, employee apps are designed to work on personal phones, with login methods such as QR codes, SMS, or username and password that do not require a corporate account to activate. The category exists because 70 to 80% of the global workforce is deskless. These workers execute the work that customers see, but most enterprise technology was never designed to reach them. An employee app closes that gap by giving frontline staff access to company news, shift schedules, HR documents, task assignments, and training through the same channel they already use for everything else: their phone. Three terms overlap here. A *frontline communication app* delivers news, chat, and documents to deskless workers. An *employee app* adds self-service and, often, operational workflows. An *employee super app* puts communications, schedules, tasks, training, and HR on one login. For the communication-first view see [the best frontline communication software of 2026](https://www.mangoapps.com/articles/best-frontline-communication-software); for the headquarters-centric category see [the best internal communications software](https://www.mangoapps.com/articles/best-internal-communications-software). ## Why Your Frontline Workforce Needs a Dedicated Employee App The business case for a dedicated employee app is not primarily about communication. It is about what happens when large portions of a workforce are effectively invisible to the systems meant to support them. When frontline workers cannot access schedules, policies, safety procedures, or HR information without asking a manager, every question becomes a drain on supervisory time and every policy update becomes a manual process. The engagement data describes the cost. [Gallup's State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) found global engagement at 20% and estimated the cost of low engagement at roughly $10 trillion, or 9% of global GDP. Among deskless workers specifically, [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) found 53% feel burned out and 43% are actively looking for a new job. [Gallup](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) puts the cost of replacing an employee at one-half to two times annual salary. A dedicated employee app addresses the underlying cause directly: it gives frontline workers a reliable, consistent channel to the organization and to their own schedule, pay, and training, replacing the informal mix of text messages, paper notices, and manager phone calls most hourly teams still rely on. ## What Features Should I Look for in an Employee App? The right feature set depends on what your workforce needs most, but these eight capabilities separate capable platforms for hourly teams from basic communication tools. | Feature | Why it matters for hourly workers | Verify in the demo | |---|---|---| | No-email onboarding | Any platform that requires a corporate email to activate excludes most hourly staff | Sign in as a worker with no email, from a QR code or SMS | | Branded app experience | Adoption rises when the app carries the employer's name and identity in the app stores | Show the app-store listing under a customer's brand | | Shift and schedule access | The daily reason to open the app | View a schedule and request a swap on a phone | | Shared-device and kiosk support | Break rooms, plant floors, and hospitals restrict personal phones | Switch users on a shared tablet | | Push notifications and multichannel delivery | Email is not available; push and SMS are | Send a targeted alert to one shift at one site | | HR self-service integrations | Pay stubs, leave requests, and benefits give workers a reason to open the app beyond news | Open a pay stub; submit a PTO request that lands in the HRIS | | Two-way communication | Broadcast-only apps see lower adoption than apps where workers can respond | Comment, answer a survey, recognize a colleague | | Analytics and reach data | Regulated industries need to know who saw and acknowledged what | View acknowledgment by location for a critical alert | ## How to Choose the Right Employee App Start with workforce composition. A platform designed exclusively for frontline workers will solve the last-mile communications problem but may not serve a mixed workforce where desk-based managers also need access to the same tool. Platforms such as MangoApps that serve both desk and frontline employees on a shared platform avoid the fragmentation that comes from running separate tools for different parts of the organization. Next, clarify the primary problem you are solving. If the core need is shift scheduling and task execution, operations-first platforms such as WorkJam or Zipline have significant depth in those workflows. If the need is communications reach and brand-aligned engagement, Sociabble, Blink, or Speakap may be a closer fit. If the organization will eventually need communications, HR, training, and operations on one platform without running separate tools for each, a unified platform such as MangoApps is worth evaluating from the start, even if the initial deployment covers only one function. Pricing structure and deployment scale also matter. Most enterprise employee app platforms are custom-quoted. Connecteam is a useful starting point for smaller teams given its published pricing and free tier. For mid-market and enterprise organizations, factor in integration costs, onboarding support, and what happens when the initial contract ends and adoption needs to be sustained. Then check the [industry table](#which-employee-apps-fit-retail-healthcare-hospitality-manufacturing-and-logistics) above and the FAQ below. ## Frequently asked questions **What is the best employee app for hourly workers without corporate email?** For enterprises with mixed frontline and desk workforces, MangoApps: it provisions identity from the HRIS, runs schedules, time, tasks, training, and HR self-service natively, and requires no corporate email. For operations-first retail and hospitality, WorkJam. For small and mid-sized teams, Connecteam, which offers a free tier. All ten apps in this guide publish a no-email sign-in method. **What are the best employee apps for frontline and deskless workers?** The most-shortlisted employee apps for frontline and deskless workers in 2026 are MangoApps, WorkJam, Connecteam, Blink, Beekeeper (LumApps), Flip, YOOBIC, Zipline, Speakap, and Sociabble. They divide into unified platforms (MangoApps), operations-first apps (WorkJam, Connecteam, Zipline, YOOBIC), and communication-first apps (Blink, Beekeeper, Flip, Speakap, Sociabble). **What is an employee super app, and which apps combine communications, schedules, tasks, and HR tools?** An employee super app puts communications, schedules and swaps, time and attendance, tasks, training, and HR self-service on one login and one employee record. Among the apps compared here, MangoApps, WorkJam, and Connecteam run all of those natively; the others rely on integrations or linked systems for schedules and HR. **Can hourly employees use an employee app on a shared device?** Yes, if the app supports kiosk mode with fast user switching and automatic sign-out, and sign-in by employee ID and PIN or badge. MangoApps, WorkJam, and Connecteam publish kiosk or shared-device support; verify the exact flow in the demo. **How do employee apps handle schedules and shift swaps?** Unified and operations-first apps (MangoApps, WorkJam, Connecteam) publish schedules, let workers request swaps and coverage, route approvals to managers, and write the result back to payroll. Communication-first apps display schedules from an existing WFM system through an integration or micro-app and send workers to that system to make changes. **Do employee apps replace our HRIS or scheduling system?** No. The HRIS and, if you choose, the scheduler remain the systems of record. The employee app syncs people and schedules in and writes time, swaps, acknowledgments, and training completions back. A platform with native scheduling gives you the option to retire the separate scheduler later. **How much does an employee app cost per employee?** Most enterprise vendors quote per user or per location and do not publish prices. Connecteam publishes a free plan for up to 10 users and a Basic tier from $29 per month for the first 30 users, per hub. Budget for integration fees and onboarding, and count the tools you retire. **Which employee apps have a free plan?** Connecteam offers a free plan for up to 10 users. Blink and Beekeeper offer free trials, and Flip offers pilots. MangoApps and the other enterprise platforms are quote-based. **How do you get hourly workers to actually adopt an employee app?** Remove the email requirement, put the schedule and pay stub in the app so there is a reason to open it every shift, sign workers up on the floor with a QR code on launch day, train managers first, and measure weekly active users by site. Social Edge Consulting benchmarks 60% weekly active users as successful and 85% as best practice; MangoApps customers average more than 90% within 90 days. **Which employee apps are HIPAA or SOC 2 compliant?** MangoApps publishes HITRUST CSF, SOC 2 Type II, ISO 27001, FedRAMP ATO, HIPAA business associate agreements, and GDPR on its [security page](https://www.mangoapps.com/security). For every other vendor in this guide, check the current trust page during procurement; certification statements here are vendor-stated. ## Sources - BCG, [Facing the Deskless Labor Shortage with Technology](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) (2024) - JLL, [Leading practices for frontline workforce engagement and retention](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention) (2025) - Deloitte, [Frontline Worker Productivity Enabled by Technology](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html) - Gallup, [State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx); [This Fixable Problem Costs U.S. Businesses $1 Trillion](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) (2019) - Okta, [Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/) - Harvard Business Review, [How Much Time and Energy Do We Waste Toggling Between Applications?](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) (2022) - Social Edge Consulting, [Top 12 Intranet KPIs and Metrics](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) (2025) - LumApps, [LumApps and Beekeeper to Join Forces](https://www.lumapps.com/insights/news/lumapps-and-beekeeper-to-join-forces-creating-the-leading-employee-experience-platform-for-the-future-of-work) (July 2025) - Connecteam, [Pricing](https://connecteam.com/pricing/) (September 2026) --- # Introducing Multi-Agent Answers in MangoApps Ask AI **Author:** MangoApps Team **Published:** 2026-05-29 **Category:** enterprise-ai Ask one question that spans scheduling, leave, tasks, or tickets — and the right specialist agents now answer in parallel, combined into a single reply you can audit. # Introducing Multi-Agent Answers in Ask AI Picture the question a frontline employee actually asks at the start of a shift: *"What shifts do I have this week, and how much leave do I have left?"* That's two questions wearing one sentence — one for scheduling, one for leave. Until now, Ask AI answered the strongest intent and let the other slip. **Multi-Agent Answers** changes that: Ask AI now recognizes when a question spans several areas, sends each part to the specialist agent that owns it, runs them at the same time, and hands back one combined reply — with a trace of which agents contributed. ## Real questions don't respect app boundaries People don't think in apps. They think in moments — the start of a shift, the end of a week, the morning after a call-out. A single sentence routinely touches scheduling *and* time off, or open tasks *and* tomorrow's roster, or an IT ticket *and* remaining PTO. The old way of handling that was to make the person do the routing themselves: ask one thing, read the answer, switch context, ask the next thing, stitch the two together in their head. Every one of those switches is friction, and friction is exactly what the frontline can't afford mid-shift. It's the same fragmentation that has managers bouncing between a scheduling tool, a messaging app, and an HR portal to assemble a picture that should have arrived in one place. Multi-Agent Answers meets the question the way it was actually asked. Instead of forcing the employee to think like a software architect — "which app owns this part?" — Ask AI does the decomposition, fans the work out to the right specialists, and brings back a single answer. The interface finally matches how people actually phrase what they need. ## What's new **The right specialists, picked automatically.** When a question looks like it spans more than one area, Ask AI breaks it into scoped sub-questions and routes each to the agent that owns that domain — scheduling, leave, tasks, service desk, reporting, attendance, and the rest of the 80-agent network. There's no app-switching and no "ask that one in the other tab." The employee asks once, in plain language, and the routing happens underneath. **Answered in parallel, not one-by-one.** The specialist agents run *simultaneously*, each inside its own securely restored tenant context. You get a cross-domain answer in roughly the time a single agent would take — not the sum of three sequential round-trips. Coordinating several agents shouldn't mean waiting three times as long, so it doesn't. **Combined into one coherent reply.** A final synthesis pass weaves the specialists' answers into a single response that reads in one voice, preserving every link, ID, and number exactly as the agents returned them. You don't get a copy-paste collage of three separate answers with three different tones — you get the one answer the question deserved, with the relevant facts woven together. **A "show your work" trace.** Every multi-agent reply ends with a collapsible **"🤝 N agents contributed to this answer"** panel. Expand it and you see exactly what each specialist said before synthesis. A combined answer is only trustworthy if you can see where each piece came from — so we made that auditable by default, on every reply, both live and when you scroll back through history. **Permission-aware and safe by design.** Each agent only runs if the employee is allowed to use it, and each one only ever sees its own scoped part of the question. Anything that would *change* data — filing a request, creating a task — is never merged or run twice in parallel; if an action needs your confirmation, that surfaces on its own, exactly the way it does today. Coordinating more agents doesn't loosen a single guardrail. ## What it looks like These are real cross-area questions Multi-Agent Answers is built to handle — and they show up as ready-to-tap prompts in the new **"Ask Across Areas"** suggestions inside Ask AI: - *"What shifts do I have this week, and how much leave do I have left?"* — scheduling + leave - *"What are my open tasks, and what shifts do I have tomorrow?"* — tasks + scheduling - *"Do I have any open IT tickets, and what's my remaining PTO?"* — service desk + leave - *"Show headcount by department and this month's attendance summary."* — reporting + attendance Each one returns a single answer, drawn from up to three specialists working together — followed by the contributor trace so the employee (or their manager) can see precisely how it was assembled. ## Availability Multi-Agent Answers is **on by default** for every business with Ask AI enabled — there's nothing to install and nothing to configure to start using it. Employees simply ask cross-area questions in the Ask AI sidebar, or tap an "Ask Across Areas" suggestion to begin. Each question coordinates up to three specialist agents. Admins who want to manage the behavior can toggle it from the **AI Features** settings for Ask AI. And as always, every agent stays bound to the permissions each employee already has — multi-agent coordination expands what a single question can answer, never what a given person is allowed to see. ## What's next Multi-Agent Answers is the coordination layer for the entire Ask AI agent network. That has a compounding effect worth calling out: the more specialist agents your business turns on, the more cross-area questions a single ask can resolve. An organization running scheduling, leave, tasks, and service desk agents can already answer questions that touch all four; as you enable more of the network, the range of "ask it however you think about it" questions widens with it. We'll keep pushing on that range — making the decomposition sharper, the synthesis cleaner, and the set of questions a single ask can resolve broader over time. **See it in your workspace — open Ask AI and ask something that spans two areas at once. [Explore Ask AI →](https://www.mangoapps.com/ai/ask-ai)** --- # Spring ’26: Calendar Sync, Google Files, and Messenger Upgrades **Author:** MangoApps Team **Published:** 2026-05-28 **Category:** news-and-updates Spring ’26 brings real-time calendar sync, Google Workspace file creation, and a modernized Messenger with better replies, editing, and formatting. A workforce platform only works if it works where employees actually are, with the tools they already use. Spring '26 extends the operational layer of the platform in four areas: real-time calendar integrations with Google and Outlook, Google Workspace file creation inside MangoApps, a substantially upgraded Messenger experience, and a mobile release that brings near-full parity with web across a wide range of workflows. ## Real-Time Calendar Integrations: Google Calendar and Microsoft Outlook Scheduling gaps between platforms create friction that compounds quickly. An event created in MangoApps doesn't show up in an employee's Google Calendar. A meeting added in Outlook isn't visible to teammates coordinating in MangoApps. Spring '26 closes that gap with real-time calendar integrations for both Google and Microsoft. **Google Calendar** supports bidirectional, real-time sync. Changes made in either platform push to the other as soon as they happen. Admins can configure sync direction independently: bidirectional (recommended), MangoApps to Google only, or Google to MangoApps only. They can also select which event types sync, covering meetings, appointments, team events, company events, resource reservations, and custom event types. Multiple Google accounts are supported, each with independent sync settings and email domain scoping. **Microsoft Outlook** sync runs one way, from MangoApps to Outlook. Events created or updated in MangoApps are pushed to users' Outlook calendars and arrive as standard meeting invites, including attendees. The same event type selection and sync frequency options apply. Multiple accounts are supported and can be enabled or disabled independently. Both integrations sync event titles, descriptions, physical locations, meeting links from Zoom, Google Meet, and Teams, recurrence rules, and reminder timing. A background sync runs in addition to real-time pushes, with frequency configurable from every 5 minutes to every 4 hours, providing a safety net if any real-time updates are missed. ## Google Workspace Integration in Files For teams that use Google Docs, Sheets, and Slides as their primary authoring tools, Spring '26 removes the need to leave MangoApps to create or manage those files. Users can now create new Google documents, spreadsheets, and presentations directly from the Files module, or add existing Google Workspace files by link. Files are stored in Google Drive and appear alongside native MangoApps files in the same folders, with their respective Google file type icons. Key behaviors of the integration: - Creating a new file opens a dialog to name it and select a destination folder, then opens the file in Google's editor in a new tab. - Sharing with colleagues maps MangoApps permissions directly to Google permissions: Owner, Editor, and Viewer levels are kept in sync between both platforms at all times. - Renaming a file updates both MangoApps and Google Drive simultaneously. - Google Workspace files are fully searchable by file name, hashtags, and description, and appear in global search results under Documents, Spreadsheets, and Presentations filters. - The integration is available across Network, Projects, Groups, Departments, and My Drive. Deleting a Google Workspace file from MangoApps removes it from the MangoApps file list only. The original file in Google Drive is not affected, which prevents accidental data loss when removing a link. ## Messenger: A Modern Chat Experience Messenger receives its most significant update in this release, covering message-level replies, message editing, Markdown formatting, a redesigned visual layout, and improved notification behavior. **Message-level replies.** Users can now reply directly to any specific message in team, one-on-one, and ad-hoc group chats. The reply appears in the main conversation timeline with a quoted snippet showing the original sender and a preview of their message. Clicking the snippet navigates directly to the original message. This keeps multi-topic conversations organized without creating separate threads, and works across all message types including attachments, Important Messages, and Read Receipt messages. **Message editing.** Users can edit recently sent text messages within a 15-minute window, available in one-on-one, team, and ad-hoc group chats across desktop, web, and mobile. Edited messages display an "Edited" indicator in the chat bubble while retaining the original sent timestamp. No notifications are sent for edits, and only the latest version of a message is shown. This is an admin-controlled setting, off by default. **Markdown formatting.** Chat messages now support standard Markdown syntax: bold, italic, inline code, strikethrough, headers, ordered and unordered lists, blockquotes, fenced code blocks, and hyperlinks. Formatted output renders inline in the chat thread across web, Messenger, and mobile, with no extension or plugin required. **Redesigned bubble UI.** Messenger now uses a modern left and right aligned bubble layout. Sent messages appear as right-aligned bubbles styled with the network's primary brand color. Received messages appear as left-aligned bubbles with a neutral background. Consecutive messages from the same sender are visually grouped, with sender name and profile image appearing only at the start of each group. In one-on-one chats, sender names and profile images are hidden for a cleaner view. Dark mode is fully supported. **Improved mute and Do Not Disturb behavior.** Standard messages in muted chats no longer generate badge increments, banner notifications, or sound alerts. Important Messages always override mute and DND settings, surfacing banner notifications and moving the chat to the top of the Active Chats list. Muted chats can optionally be hidden from the chat list entirely, resurfacing automatically only when someone mentions you, replies to your message, or sends an Important Message. ## Mobile: Expanded Capabilities Across Every Workflow The Spring '26 mobile release is one of the most comprehensive parity updates in the platform's history, spanning posts, pages, chat, surveys, wikis, tasks, recognition, LMS, and settings. The areas below represent the most meaningful additions. **Posts and content targeting.** Ticker Tape posts are now available on mobile, displayed on the Home page with auto-rotation for multiple messages and tap-to-expand for full content. Post creation now supports user segment audience targeting, letting authors reach defined employee populations from mobile with the same precision available on web. **Pages**. Anchor links are now supported on mobile pages. Creators can copy a direct link to any widget on a page, and users who tap that link are scrolled directly to the target widget with a brief highlight on arrival. Anchor links work across Company Pages and Project, Group, and Department Pages. **Governance.** Governance review requests now appear in the My Priority Items widget on mobile, allowing content owners and team admins to view and act on unverified content directly from their device without switching to the web platform. **Granular push notifications.** Mobile push notifications can now be configured independently from web settings. Users choose between mirroring their web notification preferences or setting up a custom configuration for their device only, with independent controls across three categories: News Feed, Messages, and Chats. **Locale and timezone management.** Date format, time format, and timezone settings are now available on mobile, with full sync to web settings. Timezone can be set manually or configured to update automatically based on device location. This is particularly useful for employees who travel across time zones or work across regions. **Settings reorganization.** Mobile Settings has been restructured into four clear sections: Communication Preferences, Feature Settings, General, and Help and Support. This consolidates previously scattered options into a coherent navigation structure, including new controls for smart reminders, email digest frequency, landing page preferences, session timeout, and security settings. Across chat, surveys, wikis, tasks, polls, recognition, and LMS, mobile now matches the web experience across every major workflow. The result is a more complete platform for employees who primarily work on their phones, including the frontline and field teams for whom mobile is the primary access point to MangoApps. Every update in this release is solving for the same thing: fewer reasons for an employee to leave the platform to get something done. *Learn more about the full Spring '26 Release by reading other deep dive articles linked below:* - [https://www.mangoapps.com/articles/mangoapps-spring-26-ai-courses-data-governance](https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet) - [https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet](https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet) - [https://www.mangoapps.com/articles/spring-26-automates-lms-safety-compliance-and-surveys](https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet) --- # Spring ’26 Automates LMS, Safety Compliance, and Surveys **Author:** MangoApps Team **Published:** 2026-05-28 **Category:** news-and-updates Spring ’26 adds LMS automation, safety compliance tracking, and a rebuilt Surveys module for enterprise-scale learning and feedback. Running a training program at scale is hard work. Enrollment rules need to fire on time. Compliance certificates need expiry dates tracked. Instructor-led sessions need to connect to the video tools your teams already use. And when an employee changes roles, the courses they no longer qualify for should update automatically. Most platforms leave those gaps for admins to fill manually. For employees, that bottleneck means waiting longer for training that's current, relevant, and actually built for how they work. Spring '26 closes a meaningful number of them. The LMS receives a full automation lifecycle overhaul, a set of workplace safety compliance capabilities, and improved instructor-led training tooling. The Surveys module has been substantially rebuilt, with eleven new capabilities that make it a more credible enterprise listening tool. Together, these updates make MangoApps a stronger choice for organizations running serious, compliance-heavy learning and feedback programs. ## LMS Automation Lifecycle The headline for L&D administrators is that the full learner lifecycle is now automatable without manual intervention. Three core additions make this possible. **Prerequisite-based course chaining.** Admins can now configure follow-on course assignments to trigger automatically when a learner completes a prerequisite. A new "On Course Completion" trigger in Learn Automation lets admins define whether completing any one of a set of courses qualifies, or whether all must be completed before the next course is assigned. This enables structured learning paths that advance on their own, without someone monitoring completions and manually assigning the next step. **Hourly automation triggers.** Learn Automation rules previously ran on daily, weekly, monthly, or yearly intervals. Spring '26 adds hour-based recurrence at 4, 8, and 12-hour intervals. For organizations with shift-based workforces or time-sensitive onboarding requirements, this means compliance and training assignments can respond much faster to eligibility changes. **Automated unassignment.** When a learner no longer meets the criteria for a course they were automatically assigned, the platform can now remove that assignment without admin intervention. A domain-level setting controls this behavior, and it applies only to courses with a Not Started or In Progress status. Completed learners are never unassigned. All cancelled attempts are preserved in the audit log with full history. Additional automation improvements include: - Profile date-based automation triggers now support configurable run times, so admins can control exactly when in the day a rule executes, not just which date. - Learner Activity Reports now include an Unassignment Date column and a toggle to include cancelled attempts, giving L&D teams a complete view of assignment history. - A new Days to Complete column has been added across LMS reports, calculating time from assignment or start date to completion. The practical effect for learners: the right course shows up at the right time, without anyone having to manually intervene to make it happen. ## Workplace Safety Compliance Capabilities Organizations in healthcare, manufacturing, field services, and other safety-critical industries often need more than a completion record. They need verifiable proof. For employees in safety-critical roles, completion records aren't administrative formality. They're the proof that someone was trained before they got on the equipment. Spring '26 adds three capabilities specifically designed for those requirements. **Completion proof for instructor-led training.** For ILT courses, admins can now require a completion proof attachment as a mandatory step in the Mark as Complete flow. Accepted formats include PDF, JPG, and PNG. Proof files are stored securely alongside certificates and are not publicly accessible or searchable. Every proof upload and update is captured in the audit log, giving organizations a defensible compliance trail for requirements like CPR/AED certification, forklift training, and fall protection. **Certificate expiry date tracking.** When uploading external certificates, admins can now set an optional expiry date. That date surfaces across the Learners Completion Report, Learner Activity Report, and Program Activity Report, making it straightforward to identify who is current, who is approaching expiry, and who needs recertification. **ILT session integration with video conferencing tools.** Instructor-led sessions now support direct integration with Zoom, Google Meet, and Microsoft Teams, consistent with how Events work across the platform. ICS calendar files are automatically attached to enrollment notifications and automation emails, so learners can add sessions to their external calendars without extra steps. Learners can also add sessions directly to Google Calendar or Outlook from the enrolled session card. ## Surveys Rebuilt for Enterprise Use A survey program is only as good as the trust employees have that their responses matter and their identity is protected. The Surveys module in Spring '26 is a substantial upgrade. Eleven new capabilities address the gaps that made large-scale survey programs difficult to run consistently: no reusable templates, no cross-domain portability, limited question types, and no network-wide visibility into participation and completion. **Custom reusable survey templates.** Admins can now create, manage, and publish custom survey templates from a centralized Templates hub. Templates carry forward the full survey configuration: questions, design settings, rule builder logic, and preferences. When a creator selects a template, all of that is pre-filled, and they can still modify any element before publishing. Templates can be activated, deactivated, reordered, and duplicated. Deactivating a template does not affect surveys already created from it. **Export and import across domains.** Surveys can now be exported as a JSON file and imported into another domain, carrying the full survey structure including questions, images, design settings, and rule configuration. Audience configuration is not included in the export, so importing organizations set their own targeting. This removes the need to manually rebuild surveys from scratch when deploying consistent listening programs across multiple environments. **New question and response capabilities.** Several enhancements expand what surveys can capture and how respondents interact with them: - An "Other" free-text option can be added to multiple choice questions. - Min and max selection limits can be set on multi-select questions. - Auto-complete suggestions help respondents find answers in long-answer fields. - Read-only description fields can be added to provide context without collecting a response. **Demographic insights for anonymous surveys.** Anonymous surveys now automatically attach non-identifiable demographic attributes to each response. Attributes like department and role can then be used to filter insights without ever revealing respondent identity. Strict PII exclusions apply: employee ID, email, name, manager name, manager email, and manager employee ID are never included. Manager-related attributes are only included when a manager has more than five direct reports, preventing indirect identification in small teams. **Insights access control.** Survey creators can now restrict who can view survey insights, including an option to limit visibility to the creator only. This is useful for sensitive listening programs where results should not be visible to domain or team admins. **Centralized Survey Analytics Dashboard.** A new Survey Dashboard in the Admin Portal gives network admins a single view of survey performance across the organization. It covers total surveys published, completion rates, publishing and completion trends over time, and a per-survey engagement table with completion percentages. The table supports search, sorting, and CSV export. ## What This Means in Practice For organizations running compliance training programs in regulated industries, Spring '26 significantly reduces the manual overhead involved in keeping learner records current and audit-ready. For HR and people teams running listening programs, the rebuilt Surveys module provides the template consistency, cross-domain portability, and analytics depth that enterprise programs require. Both areas reflect the same underlying principle: the platform should handle the administrative complexity so the people running these programs can focus on the outcomes. *Learn more about the full Spring '26 Release by reading other deep dive articles linked below:* - [https://www.mangoapps.com/articles/mangoapps-spring-26-ai-courses-data-governance](https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet) - [https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet](https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet) - [https://www.mangoapps.com/articles/spring-26-calendar-sync-google-files-messenger-upgrades](https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet) --- # Spring ’26 Brings Work Management Into the Intranet **Author:** MangoApps Team **Published:** 2026-05-28 **Category:** news-and-updates Spring ’26 turns MangoApps into an operational hub with service desk, performance, governance, and editorial workflow upgrades. For most organizations, the intranet is where communication happens. Announcements go out, pages get published, employees check in. What it rarely is: the place where work actually gets managed. Spring '26 changes that in a meaningful way. New integrations bring service desk tickets, performance reviews, goals, and continuous feedback directly into the MangoApps employee dashboard. Governance gets a genuine enterprise-grade overhaul. And the posts and editorial workflow receives its most comprehensive upgrade in years. Taken together, this release moves MangoApps from the communications layer to the operational center of the every day employee experience. ## Workforce Management and Operations Integrations in the Hub The most significant addition in this theme is one that most employees will feel immediately. MangoApps now surfaces key workflows from MangoApps Workforce Management and Operations solutions directly in the employee dashboard, on both web and mobile, without requiring a separate login or app. This covers two areas: service desk and performance management. ### Service Desk Employees can now submit IT and HR service requests, track open tickets, and access a full service catalog without leaving their dashboard. A Service Request Catalog widget lists available request types, and a conversational AI option lets employees describe their issue and get help through a chat interface. The My Support Tickets widget adapts based on role: - Agents see tickets assigned to them alongside tickets they have created. - Managers and admins see pending approvals, assigned tickets, and their own created requests. - All other employees see the tickets they have submitted and their current status. New requests and the full ticket list are accessible through deep linking, with no additional authentication required. ### Performance Management Five new widgets bring performance data into the employee dashboard in real time. Employees and managers can now track the following directly from their home screen: - Individual performance reviews, including the current cycle status and next pending action. - Personal goal progress, with completion percentages and due dates for upcoming and overdue goals. - Continuous feedback received and given, with the ability to request or give feedback directly from the widget. - For managers, a team-level view of performance review completion status across direct reports. - For managers, a team-level view of goal progress showing completed, on-track, and at-risk goals. All five widgets are available on mobile. Employees do not need to install a separate app to access any of this functionality. The practical effect is significant. Rather than toggling between systems to understand where a ticket stands, where a review is in the cycle, or where a team's goals are tracking, employees and managers get that picture in one place. ## Enterprise Governance Overhaul Content governance has historically been one of those areas where the tools available to admins don't quite match the scale of the problem. Spring '26 addresses that with a set of governance improvements that touch the full content lifecycle. **Home pages now included in governance for the first time.** Previously, home pages sat outside the governance framework. They now participate fully, meaning organizations can apply the same review, verification, and lifecycle controls to their most visible pages that they apply everywhere else. **Bulk page management from a centralized admin view.** A new Pages module in the Admin Portal gives admins a consolidated list of every page across the network, including home pages, with sortable columns for status, author, team, last modified date, total views, governance state, and more. Bulk actions include archive, delete, set hashtags, set categories, and manage governance, all from one place. Other governance improvements in this release include: - Governance items now surface in My Priority Items, so reviewers see what needs attention without navigating to a separate module. - Governance reminder emails now include a clear "Governance Reminder:" prefix in the subject line, making them easy to identify in busy inboxes. - Clicking a governance notification now opens the specific content item directly, rather than routing reviewers to a full list where they have to find it manually. - A new Team column in the governance items list makes it easy to see which team each governed item belongs to, with multi-team filtering support. ## Posts and Editorial Workflow Upgrade Internal communications teams have more to work with in Spring '26 than in any recent release. The improvements span authoring, content lifecycle management, and multi-author collaboration. ### New authoring tools Two new content blocks expand what authors can build inside a post: The **People Block** lets authors spotlight up to ten employees directly within a post, with profile images, job titles, and a View Profile link auto-populated for each person. Useful for introductions, team announcements, and recognition posts. - The Text Around Image block brings inline image and text editing to the post composer, with support for multiple images, granular layout controls, and text color and style customization, all editable inline without leaving the post. ### Content lifecycle controls Several long-requested workflow improvements are now available: - Authors can edit the audience of a draft post without recreating it from scratch. - Posts can be backdated on first publish, giving communications teams control over the visible timestamp when publishing content retroactively. - Scheduled posts can now be duplicated, making it easier to repurpose recurring content. - Published posts are now visible in the Planned Posts calendar alongside drafts and scheduled posts, giving a complete picture of content history in one view. ### Bulk operations and collaboration - Domain and team admins can now perform bulk actions across posts in list view, including archive, delete, set hashtags, set categories, and manage governance. - Post comments and replies can be exported to CSV, useful for moderation, compliance, and reporting. - When two authors attempt to edit the same post simultaneously, the platform now surfaces a clear Take Over Editing prompt rather than silently allowing conflicting drafts. ## The Shift Worth Noting The thread running through all three areas in this release is the same: MangoApps becomes more useful to more people, in more moments of the actual workday. Service desk and performance management in the hub means fewer context switches for employees. Better governance means content quality holds up at scale. A stronger editorial workflow means communications teams can move faster and with more control. The platform has always been where communication happens. Spring '26 extends that to where work happens. *Learn more about the full Spring '26 Release by reading other deep dive articles linked below:* - [https://www.mangoapps.com/articles/mangoapps-spring-26-ai-courses-data-governance](https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet) - [https://www.mangoapps.com/articles/spring-26-automates-lms-safety-compliance-and-surveys](https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet) - [https://www.mangoapps.com/articles/spring-26-calendar-sync-google-files-messenger-upgrades](https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet) --- # From Copilot to Infrastructure: How MangoApps Spring '26 Embeds AI Across the Platform **Author:** MangoApps Team **Published:** 2026-05-28 **Category:** news-and-updates Spring ’26 expands MangoApps AI with course creation, live Power BI answers, page approval, and usage controls. The AI story in MangoApps has never been about capability for its own sake. The platform has had AI-powered search, content generation, and intelligent assistants for years. What Spring '26 delivers is something different: AI reaching further into the employee experience than it ever has, moving from a tool that helps employees create content to one that generates entire training programs, answers questions from live business data, and governs what gets published. Four capabilities define the AI theme in this release. ## AI Course Creation Building a training course has always been a time-intensive process. Subject matter experts write content, instructional designers structure it, someone builds the quizzes, and the whole thing gets formatted for delivery. For organizations with large training libraries or frequent compliance requirements, that process is a real bottleneck. AI Course Creation removes most of it. Starting from a prompt or a set of uploaded files, the platform generates a complete, structured course ready for review. Here is what gets built automatically: - Documents become content chapters with text extracted, structured into blocks, and grammar corrected. - PDFs and PowerPoint files become presentation chapters, each with an AI-generated title and description. - Videos become video chapters with transcripts auto-generated in the course's language. - Quizzes are generated based on chapter content, with correct answers mapped automatically. - Course-level metadata is handled too: title, description, cover image, estimated duration, hashtags, and categories. The result lands in a draft state, ready for an instructor or LMS admin to review and publish. Individual instructors can also use AI to generate single chapters within an existing course, giving the capability to teams who build content incrementally rather than all at once. For organizations in healthcare, manufacturing, retail, and other industries where training libraries need to stay current, this changes the math on what a small L&D team can produce. ## AI Agents Connected to Live Power BI Data MangoApps AI Agents have been able to answer questions from internal knowledge bases, wikis, and documents for some time. Spring '26 adds a new category of knowledge source: live business data from Power BI. Admins can now connect one or more Power BI workspaces as external knowledge bases in AI Studio. Once connected, an AI Agent can query that data in real time when a user asks a question, and return structured answers that include both tabular data and natural language summaries. No data is stored inside MangoApps. The query runs against the connected Power BI workspace at the moment the question is asked. A few things make this practically useful: - Multiple Power BI workspaces can be connected, each as its own knowledge base. - A single AI Agent can combine Power BI data with other knowledge sources, so a question about headcount can pull from live workforce data while a question about policy pulls from an internal wiki. - If the Power BI connection is unavailable, the agent continues responding from its other connected sources. For operations, finance, and HR teams that live in dashboards, this means they can ask questions in plain language and get answers without pulling up a report. ## AI-Assisted Page Approval Governance has historically been a human-only process. A page gets submitted, it sits in a queue, a reviewer looks at it, and it either gets approved or sent back. In large organizations with high content volume, that queue backs up and the review quality varies. Spring '26 introduces AI as the first step in a configurable page approval workflow. Before content reaches a human reviewer, AI evaluates it for quality. Admins configure the workflow from a pre-built template, and can customize: - When it triggers: on first publish, or on publish and republish. - Who it applies to: filtered by page author or team if needed. - What happens after: AI approval can route to a manager, a specific individual, or a team for final sign-off before the page goes live. The AI step adds a quality gate that catches issues before human reviewers spend time on them. Approvers receive requests via direct message or news feed, with approve, decline, and preview actions available directly from the notification. Pending approvals also surface in My Priority Items, so nothing gets missed. Full audit logging captures the complete approval trail for every page. ## Enterprise AI Management As AI use expands across the platform, organizations need visibility and control over what it costs and how it gets used. Spring '26 introduces a token-based billing and management framework that gives admins both. The new framework includes: - Four model tiers: Auto, Thinking, Standard, and Instant, each reflecting a different cost and performance tradeoff. Auto lets the platform select the appropriate tier per request. - Pre-purchased AI credits that draw down based on actual token consumption, tracked hourly. - Usage thresholds with configurable alerts: admins set a monthly token limit and receive a notification when it is reached. - Access controls: a separate threshold can trigger a block on new AI sessions for end users if usage exceeds a defined limit. - A Service Usage Dashboard in the Admin Portal with per-feature breakdowns showing date, feature, item name, model used, tokens consumed, and cost. For organizations that have been cautious about enabling AI broadly due to unpredictable cost, this provides the controls to deploy it with confidence. ## What This Adds Up To Taken together, these four capabilities represent a shift in what AI does inside the platform. Course generation automates the most labor-intensive part of building a training library. Power BI connectivity makes AI useful to teams whose work lives in data. Page approval governance makes AI a participant in editorial quality, not just a creation tool. And the enterprise management layer makes all of it governable at scale. AI in MangoApps has always been embedded in the workflows that use it. Spring '26 extends how far into those workflows it reaches. *Learn more about the full Spring '26 Release by reading other deep dive articles linked below:* - [https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet](https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet) - [https://www.mangoapps.com/articles/spring-26-automates-lms-safety-compliance-and-surveys](https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet) - [https://www.mangoapps.com/articles/spring-26-calendar-sync-google-files-messenger-upgrades](https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet) --- # MangoApps Spring ’26 Release Brings AI, LMS, and Ops Upgrades **Author:** MangoApps Team **Published:** 2026-05-28 **Category:** news-and-updates MangoApps Spring ’26 adds AI course creation, Power BI agents, governance controls, LMS automation, and deeper workforce integrations. **ISSAQUAH, Wash. — May 28, 2026 —** MangoApps, the enterprise workforce platform built for the frontline, today announced the Spring '26 Release, a comprehensive update spanning AI capabilities, enterprise governance, learning and compliance infrastructure, and operational connectivity across the employee experience. Three capabilities anchor this release: AI that generates complete training courses from a prompt or uploaded file, AI Agents that query live Power BI data, and AI that evaluates content quality before it reaches a human reviewer. "We've spent years building a platform that adapts to how real organizations work," said Anup Kejriwal, CEO of MangoApps. "AI now governs content, delivers training, and answers questions from live business data so every employee gets faster answers, better training, and information they can trust. The updates behind it are among the most significant we've shipped in years, and nearly all of it came straight from our customers." While customer feedback drives more than half of every MangoApps release, Spring '26 goes further. Nearly 90% of what shipped was directly driven by customer requests, making this the most customer-driven release in the company's history. Highlights across four themes include: **[AI and Intelligence](https://www.mangoapps.com/articles/mangoapps-spring-26-ai-courses-data-governance)** - AI Course Creation generates complete courses from a prompt or uploaded file, with AI automatically building chapters, quizzes, video transcripts, metadata, and cover images. - AI Agents can now query live Power BI workspaces and return structured, data-driven answers without storing any data inside MangoApps. - AI-Assisted Page Approval puts AI into a configurable multi-step governance sequence, evaluating content quality before it reaches human approvers. **[Align Your Workforce](https://www.mangoapps.com/articles/spring-26-brings-work-management-into-the-intranet)** - New integrations with MangoApps Workforce Management and Operations solutions surface service desk tickets, performance reviews, goals, and continuous feedback directly inside the employee dashboard, on web and mobile. - Home pages are now included in governance, with bulk page management available from a centralized admin view. - The posts and editorial workflow gains new authoring tools, content lifecycle controls, bulk operations, and improved multi-author collaboration. **[Develop Your Workforce](https://www.mangoapps.com/articles/spring-26-automates-lms-safety-compliance-and-surveys)** - A new LMS automation lifecycle enables prerequisite-based course chaining, hourly automation triggers, and automated unassignment when learners no longer meet enrollment criteria. - Organizations can now require and upload completion proof for instructor-led sessions and track certificate expiry dates across all reports, directly addressing compliance needs in healthcare, manufacturing, and field operations. - Surveys have been rebuilt for enterprise use with eleven new capabilities, including custom reusable templates, cross-domain export and import, demographic insights for anonymous surveys, and a centralized analytics dashboard. **[Operate Your Workforce](https://www.mangoapps.com/articles/spring-26-calendar-sync-google-files-messenger-upgrades)** - Google Workspace integration lets teams create and manage Google Docs, Sheets, and Slides directly from the MangoApps Files module, with permissions synced between platforms. - Real-time calendar integrations with Google Calendar and Microsoft Outlook eliminate the scheduling gap between MangoApps and the tools employees work in daily. - Messenger has been rebuilt with message-level replies, edit windows, full Markdown support, and a redesigned bubble UI with dark mode. To learn more about the new features, read the deep dive articles linked throughout and visit[www.mangoapps.com](http://www.mangoapps.com). **About MangoApps** MangoApps is the enterprise workforce platform built for the frontline. It brings communication, daily operations, learning, and employee support into a single app for every employee. Trusted by more than 2 million users at leading organizations around the world, MangoApps keeps business-critical work moving every day. For more information, visit[www.mangoapps.com](http://www.mangoapps.com).** --- # Don't Back Up Your Vector Database **Author:** MangoApps Engineering **Published:** 2026-05-27 **Category:** enterprise-ai Embeddings are derived data — every fingerprint can be recomputed from the content it came from. So instead of snapshotting our vector store, we recover it by regenerating from source, hot content first. Here is why a rebuild button beats a backup. # Don't Back Up Your Vector Database It's 6:14 a.m. A closing manager at a distribution center opens the app and types, *"What's the call-out policy if someone no-shows the early shift?"* The answer comes back in under a second — pulled not by keyword match but by meaning, from a policy document somebody wrote eighteen months ago. The manager reassigns the shift and moves on. They never think about how that answer was found. That "found by meaning" is vector search, and it sits underneath a lot of what makes the platform useful in the moment: Ask AI, the Service Desk knowledge base, help search, template suggestions. None of it is the kind of feature anyone puts on a slide. All of it breaks the same way if the math underneath drifts — and the manager at 6:14 a.m. is the person who pays for it. This is a story about a decision that sounds reckless the first time you hear it: **we don't back up our vector database.** Not because we forgot, and not because the data doesn't matter. Because backing it up is the wrong tool for what this data actually *is* — and the right tool turned out to be something we already had running. ## What's actually in there A quick, no-code explanation of the thing we're choosing not to back up. When a manager asks a question in plain language, we can't scan every policy, article, and document word by word — that doesn't scale and it doesn't understand synonyms. Instead, every piece of searchable content is converted, ahead of time, into a list of 1,536 numbers called an **embedding**. Think of it as a fingerprint of meaning: two documents that *say* similar things end up with numerically close fingerprints, even if they share no words. A question gets the same treatment, and search becomes "find the fingerprints nearest to this one." We store those fingerprints in PostgreSQL using the pgvector extension — the same database that holds the source content, no separate vector product to operate. Today that's roughly **29 different kinds of content** carrying embeddings: knowledge base entries, help articles, the chunked bodies of long documents, task templates, policies, toolbox talks, and more. Each fingerprint is about **6 KB** on disk. Multiply that across every tenant's library and the vector data becomes one of the larger things in the database. Here's the property that decides everything else: **none of it is original.** Every embedding was *computed* from text we still have — the title and body of the article, the paragraphs of the policy. The fingerprint is derived from the source the way a thumbnail is derived from a photo. You don't carefully back up thumbnails. If you lose one, you regenerate it from the photo. That single observation is the whole article. ## The instinct we had to argue ourselves out of The reflexive engineering move is: important data, big table, therefore back it up. Snapshot the vectors, ship them somewhere safe, restore them if something goes wrong. It feels responsible. We walked through what a backup would actually buy us, and it kept coming up short: - **A backup of derived data is stale the moment it's taken.** The instant someone edits a policy, the backed-up fingerprint no longer matches the live text. Restore it later and you've faithfully recovered the *wrong answer* — a vector that describes a document that no longer exists in that form. - **It only covers one failure.** A snapshot protects against corruption, and only up to its age. It does nothing for the other ways this data goes bad — and those turned out to be the ones that actually happen. - **It's expensive in the least useful way.** Vectors are roughly 10× the size of the text they came from. You'd be paying to store, ship, and secure a large, redundant, perishable copy of data you can already reconstruct exactly. - **Restore paths rot in the dark.** A recovery procedure you only run during a disaster is a procedure you don't actually know works. The first real test is the worst possible time to discover a gap. Once we listed the ways embeddings *actually* go wrong in production, the backup looked even weaker. The real failure modes were: - **We change the embedding model.** New model, new math — old fingerprints aren't comparable to new ones, so a backup just preserves obsolete vectors. - **The fingerprint size changes.** A new model emits a different-width vector. The old ones literally don't fit. - **A scoping bug points search at the wrong content.** The vectors are fine; the *query* was wrong. Restoring vectors fixes nothing. - **Standing up a new region or tenant.** There's nothing to restore — the source content exists, the fingerprints were never built. - **Actual data corruption.** The one case a backup addresses — and even here, re-deriving from source is cleaner. Four of those five are not corruption at all. They're *change*. And you don't recover from change by restoring an older copy — you recover by regenerating against the new reality. Which meant the tool we needed wasn't a backup. It was a **rebuild button.** ## The rebuild button was already there The quietly satisfying part: we didn't have to build the recovery system. We'd been running it in production the whole time, for an unglamorous reason — keeping search fresh. Every piece of searchable content already knows how to regenerate its own fingerprint from its own text. When a manager edits a policy, a background job recomputes that document's embedding from the new wording. That's not a recovery feature; it's just how search stays current. But it has exactly the properties disaster recovery needs: ![The same pipeline, two jobs: in steady state, source content flows through the embedding pipeline into the vector store; for disaster recovery, the same pipeline is pointed back at whatever is missing or stale and rebuilds it.](https://mango-cdn.b-cdn.net/blog/dont-back-up-your-vector-database/pipeline-recovery.svg) Three things make this safe to lean on: 1. **It's idempotent.** Running it again on a healthy record produces the same result and costs almost nothing. There's no "did I already run this?" anxiety — re-running is always safe. 2. **It knows what's missing.** The system can ask, precisely, "which records have no fingerprint?" and "which fingerprints were built by an older model version?" — so recovery touches exactly what's broken and leaves healthy data alone. We tag every fingerprint with the model version that produced it specifically so a model change becomes a queryable question, not a guess. 3. **It rebuilds in priority order.** This is the part that matters for the manager at 6:14 a.m. That last point deserves its own paragraph. When we analyzed how the content is actually used, the access pattern was sharply lopsided — a small, active set of knowledge base entries and help articles serves most of the real-time questions, while a long tail sits idle for weeks. So recovery doesn't rebuild alphabetically or by database id. It rebuilds the **hot set first**: active knowledge base entries newest-first, then help articles by view count, then the long tail of document chunks. Within minutes, the content that answers the most questions is back — and the rarely-touched material refills behind it, invisibly. The floor gets working answers long before the rebuild is "done." The whole procedure is four steps, and the only true prerequisite is the ordinary one: 1. **Restore the source content** from the normal database backup. This is the system of record, and it's the one thing that genuinely must be backed up. 2. **Measure the gap** — how many fingerprints are missing or stale, per content type. 3. **Rebuild, hot set first**, so search comes back for the busiest content within minutes. 4. **Verify** the gap is gone and spot-check real searches for relevance and correct tenant scoping. Restore the text. Regenerate the math. Done. ## The trade-offs we're not hiding This isn't free, and pretending otherwise would undercut the point. **A full rebuild costs real compute.** Regenerating every fingerprint across every tenant means a lot of model calls. We blunt this two ways. First, a content-addressed cache: identical text produces an identical fingerprint, so unchanged content is recomputed from cache rather than re-billed. Second, the pipeline paces itself — small batches with a fixed delay between calls — so a large rebuild stays within provider rate limits instead of slamming into them. The honest caveat: a *model change* invalidates that cache by definition (different math, different fingerprints), so that specific scenario does incur the full cost. We accept it, because it's rare and because the alternative — comparing fingerprints from two different models — is simply wrong, not cheaper. **Recovery time scales with corpus size, not with the size of the failure.** Lose one tenant's vectors and you rebuild fast. A platform-wide model migration is a longer, paced operation. The priority ordering means *useful* search returns quickly, but "every last fingerprint rebuilt" can take a while on the largest libraries. We'd rather have a slow tail on a correct rebuild than a fast restore of stale data. **Not every content type carries a version tag yet.** Most do, which lets us surgically rebuild only what a model change invalidated. A few — the chunked bodies of long documents, in particular — don't yet, so a model change reprocesses all of them rather than just the stale ones. It works, it's just less surgical than we'd like. It's on the list. And one hard-won lesson that has nothing to do with backups: **a rebuild can't fix a query that was looking in the wrong place.** We once chased a bug where the knowledge base returned confidently irrelevant answers. The fingerprints were perfect. The problem was that the similarity search ran across the whole library before narrowing to the right category, so the genuinely relevant results fell outside the result window and got filtered out *after* the search instead of before. Regenerating embeddings would have changed nothing. The fix was to constrain the search to the correct content *first*, then rank by similarity — which is also, not coincidentally, how we keep one tenant's content from ever surfacing in another's results. Isolation is enforced in the query, before the math runs, not cleaned up afterward. No backup or rebuild touches that class of problem; only correct scoping does. ## What this means if you're evaluating a platform You probably don't operate a vector database. But if AI-assisted answers are going to sit in the path of a frontline manager's morning, the durability of that layer is a fair question to ask any vendor — and "how often do you snapshot it?" is the wrong one. Better questions: - **Is your search index the system of record, or is it derived?** If it's derived from content you already store, an honest answer to "how do you recover it?" is "we regenerate it" — and that's a *stronger* answer than "we restore a backup," because regeneration is always current. Be wary if the index is treated as precious, irreplaceable data; that usually means it's drifted from its source and nobody's sure they can rebuild it. - **How fast does *useful* search come back, not how fast does recovery *finish*?** The number that matters to the person on the floor is time-to-first-working-answer, not time-to-fully-rebuilt. Ask whether recovery prioritizes the content people actually use. - **Is the recovery path the same machinery you run every day?** A recovery procedure that only runs during incidents is one nobody's confident in. The strongest answer is "it's the same pipeline that keeps search fresh — we exercise it constantly, so it's never cold." - **Where is tenant isolation enforced — in the query, or after results come back?** This is the one that separates careful systems from hopeful ones. Filtering to the right scope *before* the similarity math is correct and safe. Filtering *after* is how the wrong content leaks into the wrong hands. The broader principle travels well beyond vectors: **don't back up data you can deterministically rebuild — invest in the rebuild instead.** Thumbnails, caches, search indexes, computed aggregates, derived fingerprints. Treat them as precious and you pay to store stale copies you're afraid to test. Treat them as disposable, build a fast and well-exercised way to regenerate them, and you get something better than a backup: a recovery that's always current, covers far more than corruption, and is proven every single day by the ordinary work of keeping things fresh. We don't back up our vector database. The 6:14 a.m. manager is the reason we're confident that's the right call — not despite the missing backup, but because of what we built instead. --- # The Shift From AI Advice to AI Action in Workforce Management **Author:** MangoApps Team **Published:** 2026-05-24 **Category:** enterprise-ai Picture a Monday morning for a workforce operations manager. The leave request queue has 14 items. # The Shift From AI Advice to AI Action in Workforce Management Picture a Monday morning for a workforce operations manager. The leave request queue has 14 items. Three broadcast messages need to go out — one for the overnight crew, one for the distribution center team that mostly speaks Spanish, one for corporate. A service desk ticket arrived about a scheduling conflict but landed in the wrong team's queue. There are performance approvals sitting idle that should have moved last week. None of this requires expertise. It just requires time. And the persistent frustration with AI in enterprise software has been exactly this: tools that surface insights you already had but still leave you to do the actual work. Smart dashboards. Predictive alerts. Recommendations that stop just short of helping. This week, something shifted. Across a series of releases, the AI in MangoApps moved — in a real and specific way — from advising to acting. The scaffolding is built around authorization, audit trails, and the ability to hand control back at any point. --- ## Agents That Can Take the Action, Not Just Suggest It The headline release this week was [Action-Capable AI Agents](https://www.mangoapps.com/changelog/2998) across 21 MangoApps apps. The list of what these agents can now do reads less like a software changelog and more like a job description: approve offers, advance recruiting candidates, manage schedule assignments, handle leave requests, and more. Not surface the right next step — take it. What separates this from conventional automation is the architecture around the action. Agents only operate within the permissions already defined for the app. Every AI-initiated operation is logged. Human review is built into any action that warrants it. This is not a system that acts in the background and reports back — it's one where the authorization model is baked in from the start. Paired with this is the [Proactive AI Suggestions Panel](https://www.mangoapps.com/changelog/2998), which now appears across Recruiting, Offer Manager, Leave Management, Scheduling, Onboarding, Service Desk, OKR Hub, Surveys, Training, and 12 more apps. The panel is context-aware: it surfaces suggested actions based on what's actually in front of the user, and triggering the AI-assisted operation takes a single click. The two features together close a loop that most enterprise AI tools leave open. The suggestions panel is the AI saying: I see something here — do you want me to handle it? The action-capable agent is the yes that actually works. The gap between the insight and the action, which has defined the limits of AI usefulness in enterprise software for the last several years, is what's being addressed here. For an HR team managing high-volume leave requests, this changes the shape of the workday. Routine approvals — requests that fall clearly within policy, from employees with no open issues — can be handled by the agent. The ones that need judgment surface for human review. The manager's time shifts from processing the queue to actually applying their expertise to the cases that require it. --- ## Communications That Adapt to the Recipient, Not the Other Way Around The week's second major cluster landed in Broadcasts, and it tells the same story through a different lens. Running a multi-location workforce that spans languages and time zones has always meant one of two compromises: lowest-common-denominator communications — one message for everyone, whether or not everyone can read it — or a manual translation and segmentation workflow that most comms teams quietly abandon because it takes longer than the message is worth. Two releases this week address this directly. [AI Compose for Broadcasts](https://www.mangoapps.com/changelog/3003) lets authors generate a broadcast from a brief, rewrite for tone and length, suggest message variants, and get AI-powered send-time recommendations based on delivery patterns. [Per-recipient Broadcast Translations](https://www.mangoapps.com/changelog/3003) takes the message that gets sent and delivers it to each recipient in their preferred language — across email, push notifications, and SMS — without a separate workflow. Together, these two features change what a broadcast actually is. A message is no longer a document the comms team writes once and distributes uniformly. It's a communication that the platform adapts to the recipient. The operations manager who needs to reach the overnight distribution center crew doesn't need a Spanish-language translation workflow. The localized delivery happens automatically. [Broadcast Scheduling, Templates, and A/B Variants](https://www.mangoapps.com/changelog/3002) rounds this out — templates for reuse, A/B testing across audience segments, scheduled delivery, and channel-level tracking. These are capabilities that marketing organizations have had for years. The difference is that workforce communications have rarely had access to them, because the tooling was designed for external campaigns, not internal operations. Putting A/B testing in the hands of an HR team sending policy updates and safety reminders treats employee communication as a discipline worth optimizing — not just a broadcast queue to clear. Also this week: [Bulk Recipient Import for Broadcasts](https://www.mangoapps.com/changelog/3003), which lets authors paste a list of employee emails or import a CSV to bulk-add recipients, with inline group membership preview before sending. Composing a broadcast to a non-standard audience — everyone on the overnight shift in three facilities, for example — no longer requires manual individual selection. --- ## AI That Learns the Rules and Proposes New Ones The third piece of this week's AI story is the one that gets the least attention in a changelog but may be the most meaningful over time. The [Suggestion Rules Admin Center with AI-Proposed Rules](https://www.mangoapps.com/changelog/3001) is a new interface for managing the platform's suggestion engine — the layer that governs what AI recommendations surface across the organization. Admins can see per-rule telemetry: what's being suggested, how often, how useful it's proving to be. They can enable or disable rules, tune parameters, snooze rules that aren't relevant right now, and dismiss ones that don't fit their organization. The new part: the AI itself proposes new rules based on patterns it observes in how the system is being used. One-click acceptance. No configuration files, no tickets to IT, no SQL. AI suggestions in enterprise software tend to be fixed at the time of deployment. They drift out of relevance as organizations change — as teams grow, as policies shift, as workflows evolve. When the AI can identify patterns in how the system is actually being used and surface new rules for admin review, the intelligence of the platform compounds rather than staling. The organization doesn't need to file a feature request to get the system to better fit how they work. This is also where the trust architecture of this week's releases is most visible. The admin center doesn't auto-apply AI-proposed rules. It surfaces them for human review. The action-capable agents act within pre-authorized scopes. The suggestions panel makes a recommendation before acting. The pattern across all of this week's AI releases is consistent: agency with oversight, not agency instead of oversight. Also in the week: [AI App Routing for Cases](https://www.mangoapps.com/changelog/2995) in the Service Desk, where submitted tickets are automatically classified to the right app or area — so routing rules can match on that classification and tickets reach the right team without manual re-categorization. A service desk ticket about a scheduling conflict lands with the scheduling team. An HR policy question lands with HR. The routing that used to require someone to read and reassign happens before the ticket hits the queue. --- ## What the Pattern Adds Up To The critique of AI-washing — adding AI labels to features that are filters and keyword matching in a trench coat — has become a useful filter. The question worth asking of any AI capability in enterprise software is: what does it actually change about the work? This week's releases have a specific answer. A manager who had to approve 14 leave requests one at a time can route AI-assisted handling on the clear-cut ones and apply their judgment to the edge cases. A comms team sending a broadcast to a multilingual workforce doesn't need a translation workflow — it happens. An admin managing routing rules for a service desk doesn't write each rule by hand — the AI surfaces what it has noticed and asks for approval. None of this removes humans from the loop. It changes where in the loop humans spend their time. The shift in enterprise AI that's actually useful isn't from no automation to full automation. It's from automation that requires constant human instruction to automation that handles the routine and escalates the rest. This week, across communications, approvals, routing, and the rules engine that governs how suggestions work, that shift showed up in specific, usable features. The work that needed a manager's time was rarely the work that needed their judgment. That gap is what's closing. --- # The Best Intranet Software Options for 2026 **Author:** MangoApps Team **Published:** 2026-05-20 **Category:** intranet Compare the top intranet software options for 2026 and find the right fit for deskless, hybrid, and enterprise teams. Most employees spend the first few minutes of their workday hunting for something: a policy document, a schedule, a form, a phone number for someone in another department. That friction compounds quietly across every shift and every team. Intranet software exists to eliminate it, giving every employee, desk-based or frontline, a single place to find what they need and stay connected to the organization they work for. This guide covers the eight strongest options available in 2026, with enough detail to help you evaluate which one fits your workforce. Software Best For Workforce Fit Platforms MangoApps Organizations that need intranet, communications, operations, and HR on one platform, with frontline access built in from day one Frontline-heavy to fully distributed enterprise Web, iOS, Android, Desktop LumApps Large global enterprises needing a unified desk and frontline AI Employee Hub under one license Enterprise, desk and frontline combined Web, iOS, Android, Desktop Unily Premium enterprise deployments with advanced AI, branding, and deep customization requirements Enterprise (1,000 to 100,000+ employees) Web, iOS, Android, Desktop Simpplr IC and HR teams that need fast deployment, AI-governed content, and a clean out-of-the-box experience Mid-market to enterprise, desk-primary Web, iOS, Android, Desktop Interact Organizations that want a broad, modular feature set with standalone or bundled purchasing options Mid-market to large enterprise, mixed workforce Web, iOS, iPad, Android, Desktop Oak Engage Frontline-heavy organizations in retail, hospitality, and healthcare that need fast deployment and a deskless-first mobile experience Mid-market to enterprise, deskless-heavy Web, iOS, Android, Microsoft Teams Omnia Intranet Microsoft 365-committed organizations that need governance depth, multi-channel publishing, and multi-language support Mid-market to large enterprise, M365-native Web, iOS, Android, Microsoft Teams ThoughtFarmer Mid-market organizations that prioritize knowledge management, process digitization, and fast time-to-value Mid-market (100 to 5,000 employees) Web, iOS, Android, Desktop MangoApps 4.6/5 Stars · Gartner Peer Insights 2M+ Users · Trusted Worldwide Gartner MQ Visionary · Intranet Packaged Solutions (2025) IDC MarketScape Leader · Employee Experiences (2024) Forrester Wave Strong Performer · Intranet Platforms (Q2 2026) Reworked IMPACT Award (Gold) · Intranet & Communications Platforms MangoApps is [The Enterprise Workforce Platform Built for the Frontline](https://www.mangoapps.com/), a single platform where every employee workflow runs, built from the ground up for organizations with significant deskless populations. The [Unified Intranet and Employee App](https://www.mangoapps.com/) is the natural starting point for organizations evaluating intranet software: a fully branded digital workplace with AI-powered search, knowledge management, targeted communications, and a mobile app that works on any device, with no corporate email required. From that foundation, organizations can expand into [Workforce Operations](https://www.mangoapps.com/solutions/internal-communications), HR, Learning, and more without changing platforms or re-implementing anything. That modular architecture, and the [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee) backed by 90%+ adoption in 90 days, is why MangoApps earns 98% customer retention across a customer base that includes some of the largest enterprises in the world. For organizations where the intranet has to reach every employee, including the two-thirds who never sit at a desk, that is the deciding difference. **Key capabilities:** - **[AI-Powered Intranet Search](https://www.mangoapps.com/key-features/posts):** Employees find policies, forms, people, and knowledge in seconds across every content type, with results filtered by role, department, and location. No hunting across shared drives or emailing HR for a link. - **[Multi-Channel Communications](https://www.mangoapps.com/solutions/internal-communications):** Publish to mobile, desktop, digital signage, and email from one place, with audience targeting, acknowledgment tracking, and read-receipt analytics so communicators know what actually landed. - **[Campaigns and Journeys](https://www.mangoapps.com/key-features/campaigns-and-journeys):** Automated content journeys that deliver the right information to the right employee at the right moment, from new hire onboarding sequences to compliance training reminders, without manual follow-up. - **[Critical Alerts](https://www.mangoapps.com/key-features/critical-alerts):** Urgent notifications that cut through the feed and require acknowledgment, built for safety incidents, operational emergencies, and time-sensitive policy updates across a distributed workforce. - **[Analytics and Insights](https://www.mangoapps.com/analytics-insights):** Engagement data across every content type and channel, so IC and HR teams can see adoption rates, content performance, and which groups are unreached, and act on it. [Columbia Basin Health Association (CBHA)](https://www.mangoapps.com/resources/columbia-basin-health-associate-case-study), a federally qualified health center in Washington State with a workforce that is over two-thirds frontline clinical staff, replaced a read-only intranet with MangoApps and branded it "Pulse." The results exceeded their original targets: "We currently have over 90% monthly employee engagement," said Rebecca Wolfs, Director of Training, Development, and Compliance, CBHA. Their goal had been 75% within two years. They reached 90% ahead of schedule. **Free version:** No **Pricing:** Modular, quote-based; contact for enterprise pricing **Platforms:** Web, iOS, Android, Desktop [Schedule a demo to see MangoApps in action](https://www.mangoapps.com/schedule-a-call) LumApps LumApps is an enterprise intranet and employee experience platform. In July 2025 LumApps merged with frontline communication platform Beekeeper, creating a combined entity that covers both desk-based and deskless workers under a single license. The platform carries native integrations with both Microsoft 365 and Google Workspace, which distinguishes it from most intranet vendors that integrate more deeply with one stack than the other. - Agent Hub for centralized governance of company-approved AI agents across HR, IT, and operations workflows - Beekeeper-powered mobile app with shift scheduling, digital forms, secure chat with inline translation, and HR self-service for employees without corporate email - Native integrations with both Microsoft 365 and Google Workspace, plus ServiceNow, Workday, and SAP LumApps's customer base is concentrated in large global enterprises, particularly organizations running mixed productivity stacks. The Beekeeper integration extends the platform's frontline reach, though as of mid-2026 the two products are still being unified under a single architecture. Buyers evaluating LumApps for frontline use cases should ask specifically for a roadmap timeline and a production reference customer who has deployed both sides. **Free version:** No **Pricing:** Enterprise, custom quote **Platforms:** Web, iOS, Android, Desktop [Explore LumApps](https://www.lumapps.com) Unily Unily is an enterprise intranet platform targeting very large enterprise organizations. Its customer references include large organizations in aviation, consumer goods, and retail. The platform is designed around brand customization and extensibility, with a development framework for building custom widgets and integrations on top of the core product. - Unily Glass: an AI conversational layer that lets employees take action across HR, CRM, and IT systems through a single interface, rather than navigating to separate applications - Extend development framework for custom widgets, alongside a Bring-Your-Own-AI architecture that connects to Microsoft 365 Copilot and other enterprise AI investments - Branded UX with extensive design customization options, backed by dedicated CSM relationships throughout implementation Unily's implementation leans on its professional services team, which buyers consistently reference in reviews. That adds to both timeline and cost relative to platforms designed for IC and HR teams to deploy independently. Organizations without dedicated IT or development resources should factor that into the evaluation. **Free version:** No **Pricing:** Enterprise, custom quote **Platforms:** Web, iOS, Android, Desktop [Explore Unily](https://www.unily.com) Simpplr Simpplr is an intranet platform primarily serving companies with 1,000 or more employees. It targets internal communications and HR teams that want to manage the platform without IT involvement, and is frequently cited for fast time-to-launch relative to other enterprise intranet vendors. Content governance is a central part of the product design, with automated lifecycle controls intended to keep AI search results accurate over time. - AI assistant ("Sage") provides permission-aware answers drawn from governed content sources, without administrators needing to manually curate search indexes - Auto-Governance automates content lifecycle controls: owner assignment, scheduled reviews, and archiving - IC and HR teams operate the platform without IT involvement, which reduces implementation timelines Simpplr's customer base skews toward technology, financial services, and professional services organizations with desk-primary workforces. A mobile app is available, but the platform's design and pricing assume the majority of users are office-based. Organizations with large deskless populations will find more purpose-built frontline options elsewhere in this list. **Free version:** No **Pricing:** Enterprise, custom quote **Platforms:** Web, iOS, Android, Desktop [Explore Simpplr](https://www.simpplr.com) Interact Interact is a UK-based intranet vendor serving enterprise organizations across retail, pharmaceutical, professional services, and multi-location businesses. The platform covers a broad range of features in a single license and is structured so components can be purchased individually or bundled, which suits organizations planning staged rollouts. - 400+ out-of-the-box features covering idea management, pulse surveys, digital signage, policy management, and an AI inclusivity checker for published content - Auto-Engage AI analyzes communication patterns to recommend send timing and channels, with translation across 60+ languages - Modular packaging: intranet, frontline mobile app, internal newsletter, surveys, and idea management available as standalone modules or bundled Interact's breadth is wider than some of the other platforms in this list, but buyers whose primary requirement is a specific capability, such as AI search accuracy or deep HR integration, may find more focused options more mature in that area. Implementation is typically 6 to 12 weeks depending on which modules are selected. **Free version:** No **Pricing:** Enterprise, custom quote **Platforms:** Web, iOS, iPad, Android, Desktop [Explore Interact Software](https://www.interactsoftware.com) Oak Engage Oak Engage is a UK-built intranet platform with a native iOS and Android app that employees access on any device without a corporate email address. Its customer base is concentrated in retail, hospitality, healthcare, and financial services. It earned Leading Product status and four ClearBox Choice badges in 2026: Intranet Choice, Community Builder, Best for Value, and AI Innovator. - Aria AI suite: semantic search across the intranet, AI-assisted content creation, and AI-generated monthly engagement reports that summarize adoption data and flag unreached groups - Smart Feed surfaces content by role, location, and behavior for each employee - Developer Centre for Microsoft 365, Google Workspace, Salesforce, SAP, and HR system integrations, alongside bidirectional SharePoint sync and embedded Microsoft Teams app Oak's customer base is concentrated in the UK and Europe. The platform covers intranet and communications, but does not include the operational suite coverage (scheduling, HR, learning, task management) that some platforms in this list provide natively. Some customers report going live in under two weeks per Oak's published case studies. **Free version:** No **Pricing:** Paid, custom quote **Platforms:** Web, iOS, Android, Microsoft Teams [Explore Oak Engage](https://www.oak.com) Omnia Omnia is a Microsoft 365-native intranet platform built on top of SharePoint, adding governance tooling, multi-channel publishing, and a white-labeled frontline app. It targets organizations already running Microsoft 365 that need capabilities SharePoint does not provide out of the box, including structured content lifecycle management, multi-tenant support, and cross-channel distribution. Omnia was named a Challenger in the Gartner Magic Quadrant for Intranet Packaged Solutions in 2025 and has appeared in ClearBox's Leading Product tier for nine consecutive years. - SharePoint-based architecture with structured content governance, lifecycle approvals, multi-tenant support, and document and process management modules - Single publishing workflow distributing to web, Microsoft Teams, mobile, email, and digital signage simultaneously, with audience targeting and multi-language translation - White-labeled iOS and Android app for employees without Microsoft 365 licenses, covering news, surveys, sign-off requests, and no-code mini-apps Omnia is suited to organizations with an existing SharePoint foundation and IT capacity to manage governance configuration. Implementation complexity scales with governance requirements: straightforward deployments can go live in around 8 weeks; multi-tenant or multi-language rollouts take longer. Organizations without an existing Microsoft 365 commitment or those that need a platform IC and HR teams can own independently of IT will find a different fit elsewhere in this list. **Free version:** No **Pricing:** Enterprise, custom quote **Platforms:** Web, iOS, Android, Microsoft Teams, Digital Signage [Explore Omnia Intranet](https://www.omniaintranet.com) ThoughtFarmer ThoughtFarmer is a mid-market intranet serving organizations with 100 to 5,000 employees, with a focus on knowledge management and document governance. It publishes its pricing directly, which is uncommon in this category, and offers a 90-day money-back guarantee. Its customer base includes professional services, financial services, legal, and healthcare organizations. - FormFlow digitizes paper-based HR and operations processes into intranet-native workflows without requiring separate forms software - Federated universal search spans intranet content, Google Drive, and SharePoint simultaneously from a single search bar - AI Assistant and AI Create/Enhance cover employee Q&A and content authoring ThoughtFarmer is not designed for organizations above 5,000 employees, and the platform's depth in any individual feature area is narrower than the enterprise platforms higher in this list. For organizations with significant frontline or deskless populations, more purpose-built options are available in this list. For smaller organizations that want predictable pricing and a low-risk entry point, ThoughtFarmer's published rates and refund policy reduce evaluation risk. **Free version:** No (90-day money-back guarantee) **Pricing:** $6 to $12 per user per month, volume-tiered; custom pricing above 1,000 users **Platforms:** Web, iOS, Android, Desktop [Explore ThoughtFarmer](https://www.thoughtfarmer.com) ## Quick Comparison: Pricing, Implementation, and Industry Fit Pricing and deployment timelines vary significantly across this list. This table summarizes what to expect before you book demos. Platform Pricing Model Typical Implementation Best Industry Fit Frontline Ready? MangoApps Modular, quote-based 90 days to 90%+ adoption (Adoption Guarantee) Healthcare, Retail, Manufacturing, Hospitality, Nonprofit Yes — built for deskless workers for 15+ years; no corporate email required LumApps Enterprise, custom quote 3 to 6 months typical for large enterprise Global enterprise, professional services, media Yes — via Beekeeper-powered app (integration mid-flight as of 2026) Unily Enterprise, custom quote 3 to 6 months; premium implementation support included Aviation, retail, consumer goods, global enterprise Partial — frontline modules available; primarily desk-first design Simpplr Enterprise, custom quote (~$40K+ per year for mid-market) Fastest enterprise deployment in category per ClearBox; typically 4 to 8 weeks Technology, financial services, professional services Partial — mobile app available; optimized for desk-based workforces Interact Enterprise, custom quote; modular add-ons available 6 to 12 weeks depending on modules selected Retail, pharma, professional services, multi-location Yes — dedicated frontline mobile app available as add-on Oak Engage Paid, custom quote 4 to 8 weeks; some customers live in under 10 days Retail, hospitality, healthcare, construction, financial services (UK/EU-strong) Yes — deskless-first architecture; no corporate email required Omnia Enterprise, custom quote 8 to 16 weeks; complexity scales with Microsoft 365 governance requirements Manufacturing, financial services, public sector, global enterprise with M365 Yes — white-labeled frontline app; no Microsoft 365 license required for access ThoughtFarmer $6 to $12 per user/month (volume-tiered); custom above 1,000 users 4 to 8 weeks; 90-day money-back guarantee if not satisfied Professional services, financial services, healthcare, legal, credit unions Partial — mobile app available; knowledge-management-first design ## What is Intranet Software? Intranet software is a private digital workspace that gives employees centralized access to company news, policies, documents, tools, and each other. Where a public website faces outward, an intranet faces in: it is the place employees go to find what they need to do their jobs, stay informed about what is happening in the organization, and connect with colleagues across teams, locations, and time zones. The category has changed substantially over the past decade. Early intranets were essentially static file repositories: content-heavy, IT-managed, and almost entirely desktop-based. They were built for office workers and never seriously attempted to reach anyone else. Modern intranet platforms are a different category. They are SaaS-delivered, accessible on any device without a corporate email address or VPN, and built for two-way communication rather than top-down broadcast. The best of them function as the digital home base for the entire workforce, desk workers and frontline workers alike, serving news, knowledge, workflows, and tools from a single branded experience. The distinction between a standalone intranet and a full employee experience platform is increasingly narrow: the vendors at the top of this list deliver both. ## Why Intranet Software Matters The business case for intranet software starts with a familiar problem: employees cannot find what they need, and organizations cannot reach who they need to reach. Gallup's 2024 State of the Global Workplace report put the cost of low employee engagement at [$8.9 trillion, roughly 9% of global GDP](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx). A significant part of that gap traces directly to poor information flow: employees who do not understand organizational goals, cannot access the tools they need, or feel invisible to leadership are consistently less engaged, less productive, and more likely to leave. The reach problem is especially acute for organizations with large frontline workforces. Roughly 80% of the global workforce has no desk, no corporate email, and no reliable access to the systems their employer has deployed. An intranet that only works for office employees is not an intranet for most of the organization. That gap explains why adoption rates for legacy platforms average 30 to 40%, while modern platforms built around mobile access and frontline usability consistently exceed 90%. The platform architecture is not an implementation detail; it is the reason the adoption numbers are different. Organizations that close that gap report measurable outcomes: reduced turnover, faster onboarding, higher compliance rates, and employees who understand what the company is trying to do and why their work connects to it. ## What Features Should I Look for in Intranet Software? The features worth evaluating vary by organization, but six categories consistently separate platforms that get adopted from platforms that sit unused. **Mobile access without corporate email.** If your workforce includes any employees without company-issued devices or email addresses, this is not optional. The platform needs a native mobile app that employees can access with a personal phone number or personal email address. Platforms that require corporate credentials effectively exclude frontline workers by default. **Content targeting and personalization.** A global news feed that serves the same content to every employee is a broadcast, not a communication. Look for platforms that let administrators target content by role, location, department, or employment type, so employees see information that is relevant to them, and communicators can verify that specific groups received specific messages. **Knowledge management and search.** The most common complaint about legacy intranets is that employees cannot find anything. Evaluate search quality rigorously in demos: how does the platform handle natural language queries, stale content, duplicate documents, and content from integrated systems like SharePoint or Google Drive? AI-powered semantic search has meaningfully raised the bar here, but implementation quality varies. **Two-way communication and employee voice.** Modern intranets support comments, reactions, surveys, idea submission, and peer recognition. These are not engagement decorations; they are the mechanism through which organizations get a signal from employees who would otherwise stay silent. Evaluate whether the platform makes it easy for frontline workers, not just office employees, to participate. **Analytics and adoption measurement.** You cannot manage what you cannot see. Look for platforms that report on content reach, read rates, acknowledgment completion, search queries, and active users by group. The ability to identify unreached populations and act on that data is what separates a managed communication program from a hope-and-post approach. **Integration with existing HR and productivity tools.** The intranet does not replace your HRIS, your payroll system, or your productivity suite. It connects them into a single employee experience. Evaluate the depth of integrations with the systems your organization already runs: Workday, SAP SuccessFactors, UKG, ADP, Microsoft 365, Google Workspace, and ServiceNow are the most common touchpoints. ## How to Choose the Right Intranet Software Start with your workforce composition. The ratio of desk-based to frontline employees is the most important filter in any intranet evaluation. A platform built for office workers, even a very good one, will underperform for an organization where half or more of the workforce is deskless. Verify in every demo that the frontline experience, not just the admin interface, is something your employees will actually open. **If your workforce is majority frontline (retail, manufacturing, hospitality, healthcare, distribution):** Look for platforms where deskless access is an architectural decision, not an add-on. No corporate email requirement is non-negotiable. MangoApps and Oak Engage are purpose-built for this profile. LumApps (via Beekeeper) and Interact (via frontline add-on) can support it, though with varying levels of integration maturity as of 2026. **If your workforce is primarily desk-based and Microsoft 365-committed:** Omnia is purpose-built for this scenario, extending SharePoint with governance and multi-channel publishing Microsoft's native tooling does not provide. Simpplr is the fastest to deploy for IC-led teams who want to operate independently of IT. **If you are a mid-market organization (under 2,000 employees) without a dedicated intranet team:** ThoughtFarmer offers published pricing, a 90-day money-back guarantee, and a knowledge-management-first design that does not require IT ownership to sustain. Axero offers the lowest entry price with a free trial, though with fewer enterprise-grade features. **If you are a large global enterprise with complex AI, customization, or multi-region requirements:** Unily and LumApps both target this segment. Unily's Extend framework and Bring-Your-Own-AI architecture suit organizations with existing Microsoft Copilot investments. LumApps suits organizations that run both Microsoft 365 and Google Workspace and need native depth in both. Assess your IT capacity honestly. Some platforms require significant IT involvement to configure and maintain. Others are built for IC and HR teams to operate independently. If you do not have a dedicated SharePoint team or intranet administrator, weigh that against platforms whose deployment model assumes you do. The best intranet is the one that gets deployed and stays current. Finally, look at adoption support, not just features. A platform's adoption rate in production is more meaningful than its feature count in a sales presentation. Ask vendors for reference customers in your industry, ask how long it took to reach meaningful adoption, and ask what happens if they miss. MangoApps is the only vendor in this list with a formal [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee): if employees do not adopt after launch, you do not pay. For organizations with large frontline populations where failed rollouts are a real operational risk, that guarantee changes the evaluation calculus. ## Frequently Asked Questions **How much does intranet software cost?** Most enterprise intranet platforms on this list do not publish pricing and require a custom quote. Costs vary significantly by user count, modules selected, and contract length. Of the platforms reviewed here, ThoughtFarmer publishes volume-tiered rates of $6 to $12 per user per month, and Axero publishes rates of $10 to $15 per user per month. For mid-market organizations, enterprise intranet contracts commonly start around $20,000 to $40,000 per year. Large enterprise deployments with custom implementation, dedicated CSMs, and multi-module licensing can run considerably higher. MangoApps uses a modular pricing model, meaning organizations pay for the suites they actually use rather than a flat per-seat rate for the full platform. **How long does it take to implement an intranet?** Implementation timelines vary by platform and by how much configuration, governance setup, and content migration is required. At the faster end, Oak Engage reports some customers going live in under two weeks, and Simpplr is consistently cited for fast IC-led deployments of four to eight weeks. Mid-range platforms like Interact and MangoApps typically deploy in six to twelve weeks for a standard rollout. Platforms with deeper Microsoft 365 governance requirements, such as Omnia, generally run eight to sixteen weeks or longer for complex multi-tenant configurations. The most important variable is not the platform but whether IC and HR teams can own the deployment independently or whether IT needs to be involved at every stage. The former is consistently faster. **Which intranet platforms work for frontline or deskless employees?** The key requirement for frontline access is a native mobile app that employees can use without a corporate email address or company-issued device. Of the platforms in this list, MangoApps and Oak Engage are designed around this requirement from the ground up. LumApps covers it via the Beekeeper-powered app acquired in 2025, though the integration is still maturing as of mid-2026. Interact, Omnia, and Simpplr all offer mobile apps, but their platforms are primarily designed for desk-based workforces. ThoughtFarmer and Axero have mobile apps but are not built for large deskless deployments. If reaching employees without corporate email is a hard requirement, it should be the first question tested in any vendor demo. **Which platforms have the strongest AI search?** AI search is a feature every platform in this list now markets, but implementation quality varies. The clearest differentiator is how platforms handle content governance: AI search is only as accurate as the content it indexes, and platforms with automated content lifecycle controls (owner assignment, scheduled reviews, archiving) produce more reliable results than those that rely on manual curation. Simpplr's Auto-Governance is specifically designed to solve this. MangoApps, Oak Engage, and Omnia all offer semantic AI search; MangoApps and Oak additionally provide AI search across integrated systems so employees are not limited to content stored inside the intranet itself. When evaluating AI search in demos, ask vendors to run queries against your own content types, including stale documents and content stored in connected systems, rather than their prepared demo datasets. **Do any of these platforms replace SharePoint?** None of the platforms in this list require replacing SharePoint, and most are designed to work alongside it. Omnia is specifically built on top of SharePoint and uses it as the system of record. MangoApps, Simpplr, Oak, Interact, and LumApps all integrate with SharePoint but operate as standalone intranets that can surface SharePoint content within a separate, more user-friendly interface. The more relevant question for most organizations is whether SharePoint alone is sufficient. It typically is not: SharePoint requires IT ownership to configure and maintain, does not reach employees without Microsoft 365 licenses, and does not provide the communications targeting, mobile frontline experience, or content governance that purpose-built intranet platforms deliver out of the box. **Can intranet software integrate with our existing HR systems?** Yes, most enterprise platforms on this list integrate with the major HRIS and productivity systems. MangoApps connects with 200+ systems including Workday, SAP SuccessFactors, UKG, ADP, Microsoft 365, Google Workspace, ServiceNow, and Okta. LumApps, Unily, Simpplr, and Omnia all offer comparable integration libraries for common enterprise systems. ThoughtFarmer and Axero have more limited integration depth, primarily covering Microsoft 365 and Google Workspace. For organizations with complex HRIS environments, it is worth confirming in the vendor's integration documentation whether the connection is a native two-way sync or a one-directional data pull, as this affects how employee data (department, location, role) is used for content targeting. --- # Mobile workforce management: onboarding checks in minutes **Author:** MangoApps Team **Published:** 2026-05-19 **Category:** mango-scoop See how mobile shifts, leave, and timesheets help verify onboarding fast; plus Snap a Receipt on Mobile and AI's deployment shift. Hand-picked stories from MangoApps this week. ## Frontline Workforce Management Goes Fully Mobile ![Frontline Workforce Management Goes Fully Mobile](https://mango-cdn.b-cdn.net/images/blog-thumbnails/blog_510_20260517_140441.png) Picture a warehouse supervisor at 6 AM. She just finished a walk of the floor, has four minutes before her team huddles, and needs to check whether the new hire completed his onboarding, verify... [Read the full story →](https://www.mangoapps.com/articles/frontline-workforce-management-goes-fully-mobile) --- ### More to read #### The Best Employee Experience Platforms of 2026 Discover the best employee experience platforms available in 2026, compare top options, and find the right fit for your organization. [Read more →](https://www.mangoapps.com/articles/best-employee-experience-platforms) #### The Best Frontline Communication Software of 2026 Discover the best frontline communication software available in 2026, compare top options, and find the right fit for your organization. [Read more →](https://www.mangoapps.com/articles/best-frontline-communication-software) #### The Best Internal Communications Software of 2026 Discover the best internal communications software available in 2026, compare top options, and find the right fit for your organization. [Read more →](https://www.mangoapps.com/articles/best-internal-communications-software) #### Your Internal Newsletter Isn't a Content Problem Most newsletters fail because of delivery, not content. Reach deskless and multilingual employees with the right channel, cadence, and format. [Read more →](https://www.mangoapps.com/articles/internal-newsletter-delivery-problem) --- ### From the Wire > **Anup Kejriwal** · General > **Why AI changes the deployment conversation** Traditional SaaS gave buyers a fairly simple deployment question: cloud or on-prem, public cloud or private instance, standard controls or extra co... > > [Read on Frontline Wire →](https://www.mangoapps.com/frontline-wire/why-ai-changes-the-deployment-conversation) --- ### What's New **General** — [Product Update - May 18, 2026](https://www.mangoapps.com/changelog/2997) * **[Snap a Receipt on Mobile](https://www.mangoapps.com/directory/app/mango-spend)** — Employees can now photograph a receipt directly from the Mango Spend mobile app to instan... **General** — [Product Update - May 17, 2026](https://www.mangoapps.com/changelog/2996) * **[Mobile Views for Workforce Apps](https://www.mangoapps.com/mobile)** — Shifts, Leave Management, Timesheets, Time & Attendance, Compensation, Employee Data, and Skills & Ce... --- # Why Enterprise Workforce Integration Fails (And What Actually Works) **Author:** MangoApps Team **Published:** 2026-05-19 **Category:** integrated-digital-workplace Most integrations only add links between tools. Real workforce integration eliminates app-switching and brings desk and frontline workers into one system. Most enterprise software vendors now lead with integration as a core selling point. After years of IT leaders demanding interoperability, the message got through. Vendors built connectors. They published API docs. They listed logos on integration pages. But adoption rates for the tools behind those integrations haven't moved. Employees still use 8 to 15 different apps to complete a single workflow. Frontline workers are still invisible to the systems their companies paid for. Managers still run their teams through WhatsApp group chats because no single platform shows them what's actually happening. Integration turned into a feature. It was supposed to solve fragmentation. Instead, it decorated it. This article explains why enterprise workforce integration breaks down, what the market is getting wrong, and what the better approach looks like for organizations that need every employee, desk and frontline, working inside a single governed system. ## The Integration Checkbox Problem Ask any workforce platform vendor how many integrations they support and you'll get a number. Ask them what those integrations actually do for the employee experience and the answer gets complicated. Most platform integrations work like this: the platform surfaces a link, a tile, or a dashboard widget that points to another system. The data syncs in one direction. The employee clicks through to the source system to complete the actual task. The workflow still requires four logins and two browser tabs. That is not integration. That is navigation. The distinction matters because the cost of fragmentation is measured in real work time, not API calls. McKinsey estimates employees spend 20% of their workday just searching for information across the tools they're supposed to use. That number doesn't drop because you added a connector. It drops when you eliminate the tool-switching. Most vendors don't make that distinction in their pitch. Which is why enterprises keep buying integrations that solve the wrong problem. ## What Employees Actually Experience The average knowledge worker uses more than 8 different applications in a typical workday. For frontline workers, the situation is often worse: they may have no corporate email, no company-issued device, and no consistent access to the systems their employer maintains. Eighty percent of the global workforce is in this position. When a frontline employee needs to check their schedule, pick up a task, complete a safety form, access a policy document, and clock out at the end of a shift, how many apps does that require? In most enterprise environments, the answer is three to six. Each app is another login. Each login is another place where something can go wrong. Each handoff is a point where work stalls, data is re-entered manually, or the employee simply stops because the friction is too high. Integration doesn't fix this when it means one system pointing to five others. It fixes this when one system handles the schedule, the task, the safety form, the document, and the clock-out natively. That is the core premise behind MangoApps' [unified employee app](https://www.mangoapps.com/solutions/employee-app): every workflow an employee needs, in the one app they already have on their phone. That is the architectural difference between a platform and a portal. ## How the Market Is Thinking About This Wrong Enterprise vendors approach integration from the inside out. They build their core product, then add integrations to extend its reach. The pitch becomes: "We connect to everything you already use." The problem with that framing is that it treats the existing stack as fixed. It assumes the goal is compatibility rather than consolidation. It optimizes for co-existence when the actual business need is simplification. Buyers are starting to see through this. The question that used to be "How many integrations do you support?" is shifting to "How much of our stack can you replace?" That is a fundamentally different conversation. One leads to a connector catalog. The other leads to a genuine platform evaluation. [See how MangoApps compares to the alternatives](https://www.mangoapps.com/compare). The vendors still winning on connector counts are selling to buyers who haven't gotten to the second question yet. The vendors winning on consolidation are selling to buyers who have. ## The Frontline Gap That Integration Doesn't Solve There is a specific failure mode worth naming directly: integration-first platforms almost never reach frontline workers. The reason is structural. Most enterprise integrations assume the employee has a corporate email, a managed device, a VPN, and sufficient technical comfort to navigate between authenticated systems. Frontline workers, the 80% of the workforce without a desk, typically have none of these things. So the organization builds an integration layer on top of SharePoint, Workday, and ServiceNow, and it works beautifully for the 20% of employees sitting at desks. The other 80% continue operating through text messages, printed schedules, and verbal instructions from supervisors. This is not a niche problem. For organizations in [retail](https://www.mangoapps.com/industries/retail), [healthcare](https://www.mangoapps.com/industries/healthcare), [manufacturing](https://www.mangoapps.com/industries/manufacturing), and [financial services](https://www.mangoapps.com/industries/financial), the frontline is the business. Their schedules, task completion rates, compliance certifications, and communication behaviors directly drive customer outcomes and operational performance. An integration strategy that excludes them is not a workforce integration strategy. It is a desk-worker optimization project. MangoApps was built specifically for this gap. Not retrofitted. The platform was designed from the beginning for employees with no corporate email and no laptop, which is why [customers](https://www.mangoapps.com/customers) like PetSmart, AutoZone, A.S. Watson, and Raley's have deployed it to populations that other platforms simply cannot reach. As Sheena Christensen at PetSmart described it: "About 80% of our 55,000 employees largely didn't have access. MangoApps gave us the ability to actually reach our entire associate base for the first time ever." Read the [full PetSmart story](https://www.mangoapps.com/resources/how-petsmart-achieves-engagement-at-4x-the-industry-average). That outcome is not achievable through integrations bolted onto a desk-centric platform. It requires architecture built for the frontline from the ground up. ## What Deep Integration Actually Looks Like There is a version of integration that works. It requires rethinking what the word means. Rather than a platform that connects to other systems, the better model is a platform that absorbs the workflows those systems were handling. Instead of pointing employees toward their HRIS to check benefits, the employee sees their benefits inside the platform they already use. Instead of routing a service request to a separate ticketing tool, the employee submits and tracks it in the same app they used to read the company announcement and check tomorrow's schedule. This is not the same as having a lot of integrations. It is about depth rather than breadth. A platform with 200 shallow connectors creates 200 exit ramps. A platform with deep native workflows keeps employees in one place to complete real work. MangoApps supports [200+ enterprise integrations](https://www.mangoapps.com/integrations), including Workday, SAP SuccessFactors, UKG, ADP, Microsoft 365, Google Workspace, ServiceNow, and Okta. But those integrations serve a different purpose than most connector strategies. They bring data and actions into the platform rather than routing employees out of it. The Microsoft 365 integration is a useful example. MangoApps doesn't just display SharePoint links. It enables co-authoring of Word, Excel, and PowerPoint files natively, federated search across SharePoint and OneDrive without leaving the platform, and access to content inside Teams, all without requiring additional Microsoft licenses. Employees stay in one environment. Work stays governed. That is the difference between integration as routing and integration as consolidation. ## The Stack Sprawl Measurement Problem Most organizations don't have a clear picture of what their workforce integration problem actually costs. They can measure software license fees. They can count the number of tools in the stack. What they typically cannot measure is the operational cost of fragmentation: how many hours employees spend switching between systems, how often work stalls because a handoff between tools isn't automated, how much data gets manually re-entered because two systems don't share a data model. That invisible cost is significant. One large MangoApps deployment captured significant cost avoidance after consolidating onto a single workforce platform. Another saw a 30-point engagement score increase attributed to the same consolidation. An omnichannel communications deployment eliminated manual copy-paste duplication that was costing a minimum of 2,700 hours per year. [MangoApps analytics and insights](https://www.mangoapps.com/analytics-insights) make these gains measurable from day one. A useful diagnostic starts with a few simple questions: - How many logins does an employee complete in a typical workday? - How often does completing a single workflow require switching between three or more applications? - How many approval or service request workflows still move by email because no automated process exists? - How much time does IT spend maintaining permissions, syncing data between disconnected systems, and managing connector configurations? If the answers to those questions are uncomfortable, the stack is fragmented regardless of how many integrations are technically active. ## The Consolidation Argument: When One Platform Beats Five Best-of-Breed Tools The conventional enterprise software wisdom is that best-of-breed wins. Find the best scheduling tool. Find the best LMS. Find the best intranet. Integrate them together and you have the best of everything. The problem with this model is that integration is not free. Every connection between systems has maintenance overhead. Every data sync introduces latency and potential for inconsistency. Every additional vendor is another contract, another implementation, another support escalation, another security review. And none of these integrations produce a unified employee experience. The employee who logs into the scheduling app, then the LMS, then the intranet, then the HR portal is using four products that happen to share some data. They are not using a workforce platform. MangoApps takes a different position. Eight suites, two communication products, and one [platform](https://www.mangoapps.com/platform) underneath all of it. [Workforce Operations](https://www.mangoapps.com/solutions/workforce-management), [HR Operations](https://www.mangoapps.com/solutions/hr-operations), [Performance and Learning](https://www.mangoapps.com/solutions/performance-learning), [Talent Acquisition](https://www.mangoapps.com/solutions/talent-acquisition), [Field Services](https://www.mangoapps.com/solutions/field-service), [IT and Procurement](https://www.mangoapps.com/solutions/it-procurement), [Internal Communications](https://www.mangoapps.com/solutions/internal-communications), and the [Unified Intranet and Employee App](https://www.mangoapps.com/solutions/modern-intranet) all run natively inside the same environment. One data model. One login. One mobile app employees already have on their phone. When a company starts with MangoApps for internal communications and later turns on workforce scheduling, employees don't download a new app or log into a new system. The same app they've been using for communications gets scheduling turned on. Same app, more turned on. That architecture changes the integration economics entirely. Instead of integrating between MangoApps' communications module and MangoApps' scheduling module, there is no integration to manage. The data is already shared. The employee experience is already unified. The IT overhead of maintaining connectors between your intranet and your LMS disappears when they are the same product. ## AI Integration: Proof, Not Pitch One place where the integration-versus-consolidation distinction becomes especially visible is AI. Most enterprise vendors offering AI capabilities are adding AI features to existing products and calling it integration. AI chat here. AI summarization there. The employee encounters AI in different contexts, in different interfaces, with different data access and different behavior. [MangoApps AI](https://www.mangoapps.com/ai) embeds directly into the workflows that use it. The Scheduling Agent lives inside Workforce Operations and has access to the scheduling data it needs to make useful recommendations. The Skills Agent lives inside Performance and Learning and surfaces skill gaps in the context of actual employee records. The Recruiting Agent lives inside Talent Acquisition and automates interview scheduling against real calendar data. These aren't AI features bolted onto a platform that was built without them in mind. They are AI agents that operate with full context because the data they need is already in the same system. That is what it looks like when AI is embedded rather than integrated. The difference for employees and managers is that the AI actually knows enough about their situation to be useful. The difference for IT is that there is no separate AI system to authenticate, govern, or maintain. ## Enterprise Security Across the Whole Platform One integration consequence that rarely gets discussed in vendor pitches is security surface area. Every integration point is a potential attack surface. Every connector that moves data between systems requires authentication, permission management, and audit logging. Every third-party tool in the stack must independently meet your security requirements. In regulated industries, each tool may require its own compliance review. When an organization runs eight point solutions with integrations between them, the security team is managing eight separate security reviews, eight separate data governance policies, and eight separate vendor relationships. The attack surface is proportionally larger. MangoApps holds HITRUST, SOC 2 Type II, and ISO 27001 certifications simultaneously. It is the only unified workforce platform with all three combined. FedRAMP ATO is also available for public sector deployments. [Review the full security and compliance posture here](https://www.mangoapps.com/security-compliance). This matters most in industries where compliance is not optional: healthcare, financial services, and government. A platform that consolidates workflows does not just simplify the employee experience. It consolidates the security perimeter. ## What Buyers Should Evaluate Before Choosing an Integration Strategy If you are evaluating workforce platforms and the integration question is on your list, here is a framework for asking the right questions. **Ask about depth, not breadth.** A vendor with 200 integrations and a vendor with 200 integrations are not the same product. Ask what each integration actually enables. Does it sync data? Does it embed the action inside your platform? Does it require the employee to leave the platform to complete the workflow? **Ask about the frontline.** If your organization has any population of deskless or hourly workers, ask specifically how the platform reaches them. Does it require a corporate email? A managed device? A VPN? If the answer to any of these is yes, the platform was not built for your frontline. **Ask about the security model.** How many separate certifications does the platform hold? How is data governed across modules? What happens to the security posture when you add a new suite? **Ask about the timeline for consolidation.** The consolidation story is only valuable if the platform can actually run the workflows you need to retire point solutions. Ask which tools customers have actually replaced and in what timeframe. [See why customers choose MangoApps](https://www.mangoapps.com/why-mangoapps). **Ask about adoption.** Integration architecture that employees don't use is architecture investment with no return. MangoApps customers average 90%+ adoption within the first 90 days, backed by an Adoption Guarantee: if employees don't adopt after launch, you don't pay. [Learn about MangoApps success services](https://www.mangoapps.com/success-services). ## The Practical Path Forward The goal of enterprise workforce integration is not a platform that connects to your existing stack. It is a platform that makes your existing stack smaller. For most organizations, the path looks something like this: Start with the highest-friction workflow in your stack. Wherever employees spend the most time switching between systems, or wherever the most data re-entry happens, or wherever managers most often lose visibility into what's happening. That is where a unified platform delivers the fastest, most measurable return. Consolidate that workflow onto a single platform. Not integrate it: own it natively. Verify that the same platform can handle the adjacent workflows when you're ready to expand. Then expand. Not because you need to add more tools, but because turning on an additional suite in a platform you already govern is dramatically simpler than evaluating, procuring, and integrating a new vendor. MangoApps customers consistently describe this progression. They start with communications or an intranet. Within 18 months, most have retired three to five point solutions. They are not running a more complicated integration layer. They are running less software. Read how [A.S. Watson](https://www.mangoapps.com/resources/aswatson-case-study) and [Raley's](https://www.mangoapps.com/resources/raleys-case-study) made this transition. That is what enterprise workforce integration is supposed to accomplish. ## Closing Integration is not a strategy. It is an outcome. The strategy is consolidation. The question is not whether a platform can connect to your stack. It is whether the platform can run your workforce, including the 80% of employees who have never had consistent access to enterprise systems, on the same platform where your knowledge workers collaborate, complete training, submit service requests, and check their schedules. For organizations that need to answer yes to that question, MangoApps is built for it. 2 million users. 98% retention. Fifteen years building for the frontline. Not because the integration catalog is the longest, but because the platform was designed to replace the catalog. *MangoApps is The Enterprise Workforce Platform Built for the Frontline. To see how it handles your specific integration and consolidation needs, [request a demo](#).* ## Frequently Asked Questions **What is enterprise workforce integration?** Enterprise workforce integration refers to connecting the various software tools, platforms, and data systems that employees use to complete their work. In practice, this can mean anything from syncing employee records between an HRIS and an intranet to building automated workflows that move data between scheduling, payroll, and communications tools. The goal is to reduce the manual work, tool-switching, and data re-entry that fragmented stacks create. The problem is that most integration strategies still leave employees navigating between multiple applications to complete a single workflow. True workforce integration means employees can complete their work in one place, not across six. **How many integrations does MangoApps support?** MangoApps supports [200+ enterprise integrations](https://www.mangoapps.com/integrations), including Workday, SAP SuccessFactors, UKG, ADP, Microsoft 365, Google Workspace, ServiceNow, Okta, and more. More important than the number is how those integrations work: MangoApps is designed to bring data and actions into the platform rather than route employees out to other systems to complete their work. **Does MangoApps replace or complement existing tools like Microsoft 365 or Workday?** Both, depending on the workflow. MangoApps works alongside Microsoft 365 and Workday rather than replacing them. For Microsoft 365, MangoApps provides the employee experience layer that SharePoint and Viva cannot fully deliver for frontline workers, including employees with no Microsoft license. For Workday and other HRIS systems, MangoApps can surface HR data, forms, and self-service actions inside the employee app so workers don't need to log into a separate HR portal for routine tasks. The architecture is designed to make existing enterprise investments more useful to more employees, not to displace core HR or productivity infrastructure. **How does MangoApps handle integration for frontline workers?** MangoApps was built for frontline workers from the beginning, which is the key architectural difference. The platform works on any personal mobile device without requiring a corporate email address, a managed device, or a VPN. Frontline employees access schedules, tasks, training, safety forms, communications, and HR self-service through a single branded app. That means the same integration depth available to desk workers extends to every hourly, deskless, and field employee in the organization. Most competing platforms were designed for desk workers first and retrofitted for frontline use later. MangoApps was not. **What systems does MangoApps integrate with for HR and workforce management?** MangoApps integrates with the major HRIS and workforce management platforms, including Workday, SAP SuccessFactors, UKG, ADP, Ceridian, and others. These integrations support employee data sync, org chart management, onboarding automation, and benefits and payroll display, among other use cases. Because MangoApps also includes native [HR Operations](https://www.mangoapps.com/solutions/hr-operations) and [Workforce Operations](https://www.mangoapps.com/solutions/workforce-management) suites, some organizations use external HRIS integrations as a data source while running day-to-day workforce workflows natively inside MangoApps. **Is MangoApps secure enough for regulated industries?** Yes. MangoApps holds HITRUST, SOC 2 Type II, and ISO 27001 certifications simultaneously, making it the only unified workforce platform with all three combined. FedRAMP ATO is available for public sector deployments. The platform also supports HIPAA and GDPR compliance requirements. For industries like [healthcare](https://www.mangoapps.com/industries/healthcare) and [financial services](https://www.mangoapps.com/industries/financial) where compliance is non-negotiable, consolidating workflows onto a single certified platform reduces the security review surface area compared to running multiple point solutions with integrations between them. Full details are available at [mangoapps.com/security-compliance](https://www.mangoapps.com/security-compliance). **How long does MangoApps take to implement, and what adoption should we expect?** MangoApps customers average 90%+ adoption within the first 90 days. Implementation timelines vary based on the scope of deployment, but the modular architecture means organizations can go live with a single suite, such as internal communications or workforce scheduling, and expand to additional suites without a new implementation. MangoApps backs every deployment with an Adoption Guarantee: if employees don't adopt the platform after launch, you don't pay. [Learn more about MangoApps success services](https://www.mangoapps.com/success-services). **What industries does MangoApps serve?** MangoApps serves mid-market and enterprise organizations across frontline-heavy industries including [retail and grocery](https://www.mangoapps.com/industries/retail), [healthcare](https://www.mangoapps.com/industries/healthcare), [manufacturing](https://www.mangoapps.com/industries/manufacturing), [financial services](https://www.mangoapps.com/industries/financial), hospitality, nonprofits, staffing, and field services. The platform is built for organizations where a significant portion of the workforce does not sit at a desk, and where reaching those employees through traditional enterprise software has historically been difficult or impossible. **Can we start with one MangoApps suite and add more later?** Yes, and this is how most customers begin. MangoApps is designed around three modular on-ramps: communications-led (starting with the intranet or internal communications), operations-led (starting with scheduling and workforce management), and HR-led (starting with performance and learning or HR operations). Each on-ramp is a complete solution on its own. When you're ready to expand, adding a suite is a configuration, not a new implementation. Employees use the same app throughout. The platform expands; the experience stays consistent. [See the full platform](https://www.mangoapps.com/platform). --- # Your Internal Newsletter Isn't a Content Problem **Author:** MangoApps Team **Published:** 2026-05-18 **Category:** employee-engagement Most newsletters fail because of delivery, not content. Reach deskless and multilingual employees with the right channel, cadence, and format. ## Your Internal Newsletter Isn't a Content Problem. It's a Delivery Problem. Most internal communications teams spend their energy on the wrong variable. They A/B test subject lines, hire better writers, and debate whether to lead with the CEO message or the culture spotlight. Meanwhile, the actual reason their newsletter underperforms sits quietly upstream: they're sending an email to a workforce that doesn't live in email. Fix the content all you want. If 60% of your employees are shift workers, retail associates, or plant operators who never open a work inbox, you haven't solved anything. ### The Problem Nobody Talks About Conventional wisdom treats internal newsletters as a content problem. Post better topics. Write shorter paragraphs. Use a cleaner template. That advice isn't wrong — it's just incomplete in a way that costs organizations real money. Disengaged employees cost U.S. organizations **$1.9 trillion in lost productivity annually**. The internal newsletter is supposed to be one of the primary mechanisms for keeping employees informed, aligned, and connected to the organization's direction. When it fails, it doesn't fail quietly. Here's the structural issue: the internal newsletter was designed in an era when every employee had a desk and a work email address. Legacy intranet platforms reinforced that assumption for years — building template editors and open-rate dashboards that only measure performance among employees who were already reachable. The 80% of the global workforce in frontline or deskless roles gets treated as an afterthought. Platforms that bolt on a mobile app after the fact don't solve this. They replicate the same email-centric model on a smaller screen. ### What the Data Actually Shows #### Open Rates in the 60s Are Achievable — But Only With the Right Setup Consider this: a 4,500-person distributed company running a weekly internal newsletter achieved **open rates in the 60s**. That's roughly three times the industry average for internal email communications. The content was good — but it wasn't the differentiator. What made the difference was a deliberate delivery setup built on three things: - A consistent cadence employees could anticipate - A length commitment that respected their time - A platform that surfaced the newsletter through the channel each employee actually used — not just their inbox "Delivery architecture" simply means the combination of timing, channel, and format decisions that determine whether a message actually reaches its intended audience. Most organizations never optimize for this because they treat the newsletter as a single artifact pushed through a single channel. When you design for one delivery method, you optimize for one audience segment. Everyone else gets a lower-quality version — or nothing at all. #### Recognition Isn't Filler — It's a Structural Engagement Mechanism One of the most consistently underused sections of any internal newsletter is recognition. Not the perfunctory "shoutout to the warehouse team" buried near the bottom — but recognition explicitly tied to behaviors and values the organization is trying to reinforce. Recognition connected to specific behaviors and values makes employees **2x more likely to be engaged**. That's not a marginal lift. Most newsletters leave it on the table because recognition gets treated as a culture garnish rather than a core editorial priority. The [internal newsletter best practices](https://www.mangoapps.com/articles/constructing-the-perfect-company-newsletter) that actually move engagement metrics treat recognition as a repeating, structured section — not an optional add-on when space allows. The difference between a newsletter employees look forward to and one they ignore often comes down to whether they ever see themselves or their colleagues in it. #### Multilingual Workforces Expose the Single-Format Fallacy If your organization has employees who speak different primary languages — common in healthcare, manufacturing, hospitality, and retail — a single-language newsletter isn't a communication program. It's a communication program for part of your workforce. Reaching everyone requires translation and format adaptation built into the editorial workflow, not added as a separate step afterward. Our platform supports delivery in **15+ languages**, with AI handling translation automatically so the same editorial effort reaches every employee in the language they actually read. The [employee newsletter ideas and templates](https://www.mangoapps.com/articles/comany-newsletter-ideas-editable-newsletter-templates) that work for distributed, multilingual workforces aren't more elaborate — they're more structurally honest about who they're trying to reach. ### Where the Industry Gets It Wrong The dominant response to poor newsletter performance has been to invest in better content tools — richer editors, smarter templates, more analytics on topic performance. The result is a category of increasingly sophisticated tools for producing content that still only reaches employees who were already engaged enough to open their email. This is where email-first platforms plateau. They can tell you that your open rate improved from 18% to 24% among desk workers. They cannot tell you what happened to the 3,000 shift workers who never saw the message — because those workers aren't in their measurement model. That gap is a **reach gap**: the difference between the employees your newsletter is intended to reach and the employees it actually reaches. No amount of editorial investment closes a reach gap. Only fixing the delivery setup does. The [internal newsletter format most companies still get wrong](https://www.mangoapps.com/glossary/internal-newsletter) isn't the writing. It's the assumption that a single format, sent through a single channel, on a single cadence, can serve a workforce that operates across fundamentally different environments. ### What Actually Works: A Unified Approach [MangoApps](https://www.mangoapps.com) treats the internal newsletter as a delivery problem, not a content production problem. A single editorial effort gets distributed across **three channels simultaneously**: in-app, mobile push, and email. Role-based targeting means a frontline shift worker receives a short-form mobile push with the three things most relevant to their location and role. A corporate employee receives the full digest in their inbox. AI handles translation into 15+ languages without a separate localization step. The result: our customers sustain **90%+ monthly employee engagement rates** across more than one million users. That's what happens when reach and relevance improve together — the content works harder because it actually gets read. --- If you're planning your 2026 communications calendar, our [2026 Internal Communications Planning Calendar](https://www.mangoapps.com/resources/internal-communications-planning-calendar-for-2026) provides month-by-month content themes, recognition hooks, and task lists designed to keep every employee — desk and frontline — informed. For a broader look at [company newsletter ideas](https://www.mangoapps.com/articles/company-newsletter-ideas) that move engagement metrics rather than just fill an inbox, that's the place to start. The internal newsletter isn't dying. It's just been built for the wrong audience for too long. Build it for everyone, and the numbers follow. --- # Frontline Workforce Management Goes Fully Mobile **Author:** MangoApps Team **Published:** 2026-05-17 **Category:** workforce-management Picture a warehouse supervisor at 6 AM. She just finished a walk of the floor, has four minutes before her team huddles, and needs to check whether the new hire completed his onboarding, verify... # Frontline Workforce Management Goes Fully Mobile Picture a warehouse supervisor at 6 AM. She just finished a walk of the floor, has four minutes before her team huddles, and needs to check whether the new hire completed his onboarding, verify that tomorrow's shift roster meets the forklift certification requirements, and approve a schedule-swap request from someone on the afternoon crew. Her phone is in her hand. Her laptop is in the break room, which she won't see until lunch. For years, that supervisor's options were: remember to do all of this later at a desk, or attempt a full browser session on a phone screen designed for someone else. Neither option works well. HR platforms were built for HR departments — teams that sit at desks, run reports, and manage processes from a browser. The workers those platforms are supposed to serve are rarely at desks. This week, that gap got significantly smaller. --- ## Seven Apps. One Platform. All on Mobile. What changed: MangoApps now ships purpose-built mobile views for [Shifts, Leave Management, Timesheets, Time & Attendance, Compensation, Employee Data, and Skills & Certifications](https://www.mangoapps.com/changelog/2996). Not responsive web pages that technically load on a phone — actual mobile-first interfaces designed for how people use their devices on a factory floor, in a clinic hallway, or at a job site. The distinction matters. A responsive table with twelve columns does not become a good mobile experience because it technically renders on an iPhone. Real mobile design means different information hierarchy, touch-native interactions, fewer taps to reach the thing you need. Purpose-built means the mobile version was designed for the mobile use case, not adapted from the desktop version after the fact. The same release added [Mobile Employee Onboarding](https://www.mangoapps.com/changelog/2996) — new hires can now complete their entire first-day flow on a phone: profile setup, security configuration, notification preferences, and shift availability. That matters because the onboarding drop-off point for hourly workers is rarely a complicated form. It's a form that requires a computer, in a world where the new hire doesn't have one at work yet. For operations teams watching completion rates for onboarding checklists plateau in the 60–70% range, the friction reduction here is concrete. If a new associate can complete the process while waiting for orientation to start, most will. If they need to find a computer to do it, many won't — and the incomplete profile becomes a recurring nuisance for the HR team that follows up. It also changes who can handle the work. A frontline manager who previously had to sit at a workstation to review scheduling data can now do it from the floor, in real time, during a shift change. That's not a small convenience improvement. It's a change in where the work can happen. --- ## The Invisible Compliance Risk in Your Schedule A quieter problem runs through every shift-based operation: the wrong person in the wrong role. In healthcare, a nurse without a current certification covering a specialized procedure. In construction, an operator without the required equipment license. In food service, a team member not trained on a particular piece of kitchen equipment. The compliance exposure isn't always obvious until something goes wrong — and by then, the schedule that caused it has long since been overwritten. The gap isn't usually negligence. It's that the information about who is certified to do what lives in a separate system from the schedule, and the manager building Monday's roster is making dozens of decisions under time pressure. Certification checks become one more thing to remember, and memory is a fragile compliance control. This week's scheduling releases address that at the root. [Skills-Based Role Requirements on Shifts](https://www.mangoapps.com/changelog/2970) lets admins define required skills and certifications per role, applied automatically to every shift of that type — with override capability on a per-shift basis when an exception is genuinely warranted. That's structurally different from a checklist a manager is supposed to consult. It's a constraint that propagates through the schedule itself. The same logic extends to [Skill Requirements on Shift Rule Templates](https://www.mangoapps.com/changelog/2992): when a reusable template is applied to a location or schedule, the associated skill requirements come with it. Compliance infrastructure doesn't have to be rebuilt from scratch each time a new location rolls out — it inherits from the template. The [Central Template Library](https://www.mangoapps.com/changelog/2992) compounds this. Organizations can now browse, preview, and import pre-built templates across Forms, Inspections, Policy Hub, SOP Hub, and Workspaces. The practical effect is compressing the lag between "we decided to run compliance inspections" and "inspections are actually running." That lag — often weeks when every form, workflow, and routing rule has to be built from scratch — is a real window of exposure. Templates close it. And for managers trying to close the books on labor spend, the [Location Hours Budget Basis](https://www.mangoapps.com/changelog/2995) update closes a different kind of gap: the schedule board now shows actual timecard hours alongside scheduled hours, so managers aren't overstating labor costs when shifts go partially unworked. An accurate picture of what was actually spent matters as much as planning what should be spent. --- ## AI Working Below the Surface The AI features this week weren't the kind that announce themselves. They were about reducing work that currently sits on coordinators and administrators — work that's routine, manual, and doesn't need a human to do it. [AI App Routing for Service Desk Cases](https://www.mangoapps.com/changelog/2995) automatically classifies incoming tickets by which app or business area they belong to, then routes them to the right team based on that classification. The problem it solves is mundane and persistent: a ticket submitted to the general help desk that belongs to IT, or to HR, or to Facilities, and needs a human to look at it, decide where it goes, and move it. Multiply that by a hundred tickets a week and you have a meaningful share of a coordinator's time gone to triage. That work can be automated. [AI App Builder](https://www.mangoapps.com/changelog/2971) is more ambitious: describe a custom business app in plain English, and MangoApps builds it — as a multi-page app, a dashboard widget, or an Ask AI agent — governed by existing roles, permissions, and audit trail. This addresses a specific frustration that shows up repeatedly in larger organizations: a workflow that everyone needs to track, not quite covered by any existing tool, too small to justify an IT project, but large enough that spreadsheets have started breaking down. The App Builder exists for exactly that middle ground. For teams building AI-augmented workflows on top of workforce data, [MangoApps now supports the Model Context Protocol (MCP) with OAuth 2.1](https://www.mangoapps.com/changelog/2993), allowing AI clients — Claude.ai, Cursor, and others — to connect directly to the platform with tenant-scoped access and admin-controlled token management. This is infrastructure: the same way REST APIs let systems exchange data, MCP lets AI clients query workforce context directly, without custom integration work for each tool. None of these features have a visible "AI" button a worker presses. They work by removing friction from processes that would otherwise require manual intervention. That's how AI tends to earn its keep in operational systems — not as a conversational interface, but as a routing layer, a builder's shortcut, and a protocol that makes everything else interoperable. --- ## What It Adds Up To The through-line across this week's releases is something that doesn't make a clean headline: reducing the gap between how software was designed and how work actually happens. HR software was designed for HR departments. Frontline workers use phones. Compliance requirements need to be embedded in scheduling logic, not remembered by managers. Support tickets need to reach the right team without a coordinator in the middle. Custom workflows need to be buildable without an engineering sprint. None of these are new observations. What changes week to week is the accumulation of specific, targeted corrections — each one addressing one friction point, each one making the platform a closer fit to the actual work. Mobile views for seven core apps isn't a bold product announcement. It's a correction that was overdue. But it's the kind of correction that matters when your platform is supposed to serve workers who are standing up, moving around, and pulling their phones out between tasks. The shift that's happening in frontline workforce management isn't architectural or dramatic. It's operational: software learning to meet workers where they are, with the constraints they actually have, doing the work they're actually doing. This week moved that line. --- # The Best Employee Experience Platforms of 2026 **Author:** The MangoApps Team **Published:** 2026-05-15 **Category:** comparisons Discover the best employee experience platforms available in 2026, compare top options, and find the right fit for your organization. Most organizations have a communications tool, a survey tool, a performance tool, and an intranet — and employees still can't find what they need, hear from leadership, or feel connected to the work they're doing. Employee experience platforms exist to close that gap: a single hub where people can communicate, collaborate, learn, get answers, and stay engaged, whether they work at a desk or on a retail floor. Choosing the right one depends heavily on who your workforce actually is, because the platforms built for desk workers and the platforms built for frontline workers are not the same product. Software Best For Workforce Fit Platforms MangoApps Frontline-first organizations needing communications, operations, HR, and learning in one platform Frontline + desk Web, iOS, Android, Desktop Simpplr AI-powered intranet and listening for primarily desk-based organizations Desk-first Web, iOS, Android Workvivo Social-style engagement and culture building for distributed teams Desk + some frontline Web, iOS, Android, Desktop LumApps Enterprise intranet for organizations standardized on Google Workspace or Microsoft 365 Desk + frontline Web, iOS, Android Leapsome Combined performance management, engagement surveys, and learning for desk-based teams Desk-first Web, iOS, Android Culture Amp Employee listening, engagement surveys, and people analytics at scale Desk-first Web, iOS, Android Qualtrics EmployeeXM Enterprise-grade employee listening and lifecycle feedback at scale Desk-first Web, iOS, Android Guru AI knowledge management and company wiki for teams working inside Slack or Microsoft Teams Desk-first Web, iOS, Android, Browser ext. MangoApps 4.6/5 Stars · Gartner Peer Insights 2M+ Users · Trusted Worldwide Gartner MQ Visionary · Intranet Packaged Solutions (2025) IDC MarketScape Leader · Employee Experiences (2024) Forrester Wave Strong Performer · Intranet Platforms (Q2 2026) Reworked IMPACT Award (Gold) · Intranet & Communications Platforms [MangoApps](https://www.mangoapps.com/) is the Enterprise Workforce Platform Built for the Frontline — eight suites covering communications, workforce operations, HR, performance, learning, recruiting, field services, and IT, all running on a single platform with one login and one data model. Where most employee experience tools are built for desk workers and extended to the frontline as an afterthought, MangoApps has been architected for the frontline for 15+ years. That distinction matters: a store associate with no company email, a field tech without a corporate laptop, and a distribution center worker checking schedules on a personal device all get the same experience as anyone sitting at a desk. The result is 90%+ adoption in 90 days, backed by a published [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee). The [Internal Communications Suite](https://www.mangoapps.com/solutions/internal-communications) handles multi-channel delivery, audience targeting, read acknowledgments, and [analytics](https://www.mangoapps.com/analytics-insights) — so communicators know whether messages actually landed. The [Unified Intranet & Employee App](https://www.mangoapps.com/) functions as a full digital workplace: knowledge bases, department sites, policy libraries, and employee resources, all accessible on any device without a corporate email. Expanding into HR Operations, Performance & Learning, or Workforce Operations doesn't mean a new vendor or a new implementation. It's the same app with more turned on, which is why customers typically retire four to five point solutions within 18 months of deployment. **Key capabilities:** - [**AI agents embedded in every workflow:**](https://www.mangoapps.com/key-features/posts) Scheduling, attendance, leave, compensation, skills, and recruiting agents work inside the suites that use them — no separate AI layer to configure or license, and no switching between tools to get an answer. - [**Critical Alerts and multi-channel delivery:**](https://www.mangoapps.com/key-features/critical-alerts) Reach every employee on the channels they actually use — push notification, SMS, email, digital signage, or desktop — with mandatory acknowledgment tracking and delivery confirmation. - [**Campaigns and Journeys:**](https://www.mangoapps.com/key-features/campaigns-and-journeys) Automated, multi-step communication campaigns tied to lifecycle events (onboarding, role changes, policy updates) so the right message reaches the right employee at the right moment, without manual coordination. - [**Enterprise security no competitor matches:**](https://www.mangoapps.com/security-compliance) HITRUST, SOC 2 Type II, and ISO 27001 — the only unified workforce platform certified across all three. FedRAMP ATO available for public sector deployments. - [**200+ integrations, no integration tax:**](https://www.mangoapps.com/integrations/) Workday, SAP SuccessFactors, UKG, ADP, Microsoft 365, Google Workspace, ServiceNow, Okta, and more, with a single data model so employee records stay in sync across every suite. [A.S. Watson Benelux](https://www.mangoapps.com/customers), the health and beauty retailer behind Kruidvat and Superdrug, deployed MangoApps across 16,000+ store employees with no company email addresses and a workforce averaging 25 years old. Adoption reached 80%+ without training materials — employees created accounts and started using the platform before their onboarding sessions. "We wanted to provide our employees with the same experience that say Facebook or WhatsApp provided them but in a more secure environment," said Jan Carel Uylenberg, HR Director at A.S. Watson. Today, all 16,000+ Kruidvat employees access their work schedules through the MangoApps mobile app, and store managers have replaced constant schedule calls with self-service access that works 24/7. **Free version:** No **Pricing:** Modular, quote-based; contact for enterprise pricing **Platforms:** Web, iOS, Android, Desktop [Schedule a demo to see MangoApps in action](https://www.mangoapps.com/schedule-a-call) Simpplr Simpplr is an AI-powered employee experience platform built on a modern intranet foundation, designed for mid-market and enterprise organizations that want a unified digital headquarters for communications, engagement, and knowledge. It targets primarily desk-based workforces where the central use case is giving employees a personalized, searchable hub for company news, resources, and answers. - AI Assistant and federated search across connected enterprise systems (SharePoint, Google Drive, Salesforce, and 200+ others) - Built-in employee listening with pulse surveys and AI-driven sentiment analysis alongside the intranet - Smart Feed with adaptive personalization and a governance engine that flags stale content for review **Free version:** No **Pricing:** Quote-based; annual subscription sized to employee count and module scope **Platforms:** Web, iOS, Android [Explore Simpplr](https://www.simpplr.com) Workvivo Workvivo, now part of Zoom, is an employee experience platform that combines a social-style activity feed, intranet, recognition, podcasts, and digital signage into a single hub. It suits organizations that want to build culture and drive voluntary participation through a familiar, consumer-style experience rather than top-down broadcast. - Social activity feed with shout-outs, communities, livestreaming, and podcasts designed to encourage peer engagement - Workvivo TV and digital signage for reaching employees on shared screens without requiring a personal device - Automated Employee Journeys with personalized content for onboarding and lifecycle moments **Free version:** No **Pricing:** Quote-based; Business and Enterprise tiers with custom pricing **Platforms:** Web, iOS, Android, Desktop [Explore Workvivo](https://www.workvivo.com) LumApps LumApps is an enterprise intranet and employee hub with first-class native integration for both Google Workspace and Microsoft 365, making it a strong choice for organizations that run one of those ecosystems and want a communications and knowledge layer that sits naturally inside it. Following its combination with Beekeeper, LumApps now also offers a frontline mobile hub for deskless workers. - Dual-ecosystem integration with both Google Workspace and Microsoft 365, including embedded content from Drive, Gmail, Calendar, SharePoint, and Teams in a single intranet view - AI Agent Hub for deploying governed, company-approved AI agents for HR, IT, and knowledge tasks without a separate toolset - Frontline mobile hub with shift scheduling, forms, secure chat with inline translation, and HR self-service accessible without a corporate email **Free version:** No **Pricing:** Quote-based; tiered license packages with volume pricing for 2,000+ employees **Platforms:** Web, iOS, Android (branded white-label mobile app available) [Explore LumApps](https://www.lumapps.com) Leapsome Leapsome is a people-enablement platform that brings performance management, engagement surveys, learning, OKRs, and compensation into a single modular suite. It suits mid-market and enterprise organizations whose primary EX challenge is connecting what employees are measured on to how they develop and feel about their work, rather than communications or intranet access. - Modular, interconnected suite spanning Reviews, Goals and OKRs, Surveys, Learning, 1:1 Meetings, Compensation, and a lightweight HRIS, with shared people data across every module - AI Copilot that surfaces insights and recommended manager actions from survey results and review data - In-flow feedback and review nudges delivered inside Slack and Microsoft Teams, with support for 38+ languages **Free version:** No **Pricing:** Quote-based; module and headcount-based annual pricing **Platforms:** Web, iOS, Android [Explore Leapsome](https://www.leapsome.com) Culture Amp Culture Amp is an employee experience platform centered on listening, engagement, performance, and development. Its three connected products — Engage, Perform, and Develop — cover the full arc from measuring how employees feel to supporting how they grow, backed by an extensive people-science benchmark dataset drawn from across its customer base. - Science-backed survey library with 40+ templates and industry and company-size benchmarks for engagement, inclusion, wellbeing, and intent-to-stay - AI-driven text analytics that extract themes from open-text responses and link engagement data to attrition risk, with recommended manager actions - Skills Coach micro-learning that delivers short development lessons to managers and employees based on survey findings **Free version:** No **Pricing:** Quote-based; separate SKUs for Engage, Perform, and Develop with annual billing **Platforms:** Web, iOS, Android [Explore Culture Amp](https://www.cultureamp.com) Qualtrics EmployeeXM Qualtrics EmployeeXM is the employee experience measurement suite within the broader Qualtrics XM platform. It focuses on enterprise-grade listening across the full employee lifecycle — engagement, onboarding, exit, 360 development, candidate experience, and digital experience — and is most often selected by larger organizations with complex, multi-program measurement needs. - Full-lifecycle listening suite with discrete SKUs for Engagement, People Lifecycle, Candidate Experience, 360 Development, and Digital Employee Experience - AI analytics with continuous listening, text sentiment scoring, and theme detection across 20+ languages, with predictive attrition and retention modeling - CrossXM linking that connects employee experience data to customer experience and operational metrics in a single view **Free version:** No (a separate free tier exists for the core Qualtrics survey tool but does not include EmployeeXM) **Pricing:** Quote-based; annual subscriptions priced by employee count and selected modules **Platforms:** Web, iOS, Android [Explore Qualtrics EmployeeXM](https://www.qualtrics.com/employee-experience/) Guru Guru is an AI-powered knowledge management platform that serves as the governed knowledge layer behind HR, IT, and internal communications. It addresses the stale-wiki problem — content that no one trusts because no one maintains it — by building verification and expert ownership into the structure of every knowledge card. Most teams deploy Guru as the knowledge source their employees query inside Slack, Microsoft Teams, or a browser, rather than as a standalone destination. - Knowledge cards with automated expert verification cycles so content stays accurate, with named owner accountability for each card - AI Assist and domain-specific Knowledge Agents (HR, IT, support) that answer employee questions using governed internal content, accessible via Slack, Teams, and a browser extension - 100+ integrations with Salesforce, Zendesk, SharePoint, Confluence, Google Workspace, and Microsoft 365, so knowledge flows to where employees already work **Free version:** Free trial available; confirm current free-tier availability at time of evaluation **Pricing:** Quote-based; contact for current pricing **Platforms:** Web, iOS, Android, Browser extension (Chrome/Edge), Slack and Teams apps [Explore Guru](https://www.getguru.com) ## What Is an Employee Experience Platform? An employee experience platform is software that brings together the tools employees need to communicate, find information, do their work, learn, and stay connected — in one place rather than scattered across a dozen separate applications. The category grew out of the recognition that most organizations had accumulated a collection of point solutions: an intranet here, a survey tool there, an LMS somewhere else, and a communications app that only reached people with company email. None of those tools talked to each other, and employees navigating between them lost time, lost context, and lost confidence that the company had its act together. The platforms in this category vary considerably in what they cover. Some are communications-led, with a modern intranet and multi-channel messaging at the center. Some are listening-led, focused on surveys, sentiment, and performance data. Some are knowledge-led, prioritizing the ability of employees to find accurate answers quickly. A few, like MangoApps, attempt to span all of these — plus operational workflows like scheduling, task management, and HR self-service — in a single platform. Understanding which pillar a given platform leads with is the most useful framework for evaluating whether it actually solves the problem your organization has. ## Why Employee Experience Platforms Matter The business case for investing in employee experience is well-established and well-quantified. [Gallup's research](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) finds that disengagement costs the global economy $8.8 trillion annually — roughly 9% of global GDP. Engaged teams deliver 23% higher profitability, 18% higher sales, and 51% lower turnover in high-retention environments. Organizations with strong internal communications are 4.5 times more likely to have engaged employees. These aren't soft metrics about culture and morale. They trace directly to margin, retention, and productivity. The stakes are higher for organizations with large frontline populations. The majority of the global workforce has no desk, no corporate email, and no reliable way to access the systems their company paid for. That communication gap doesn't just hurt engagement — it creates genuine operational risk when safety procedures don't reach field workers, when policy updates are ignored because no one saw them, or when a manager is fielding schedule questions on personal WhatsApp because there's no better option. An employee experience platform that doesn't solve for the frontline solves for less than half the workforce. ## What Features Should I Look for in an Employee Experience Platform? **Unified communications and intranet.** Employees need one place to find company news, access resources, and hear from leadership — whether that's a news feed, a knowledge base, or a combination of both. Look for targeting capabilities so the right content reaches the right audience, and delivery confirmation so communicators know messages actually landed. **Mobile access for non-desk workers.** If any portion of your workforce lacks company email or a corporate device, the platform needs to work on a personal phone without requiring a managed device or enterprise login. This is a harder requirement than it sounds — many platforms that claim mobile support still require Active Directory credentials or a company email to provision an account. **Employee listening and feedback.** Pulse surveys, engagement surveys, and open-text feedback should live in the same platform as communications, not in a separate tool that produces reports nobody connects back to the messages employees just received. **Performance and recognition.** The best EXPs close the loop between what employees are told, what they're asked to do, and whether their contributions are noticed. Look for recognition features, goal-setting, and performance visibility that managers can act on without switching applications. **AI-assisted search and knowledge delivery.** Employees spend significant time hunting for information. A platform with AI-powered enterprise search — one that can answer questions from across connected systems, not just its own content — meaningfully reduces that friction. **Integrations with HRIS and productivity tools.** An EXP that doesn't connect to your HRIS means manual roster management and employee data that drifts out of sync. Native integrations with Workday, SAP SuccessFactors, UKG, Microsoft 365, and Google Workspace are table stakes for enterprise deployments. ## How to Choose the Right Employee Experience Platform Start by mapping who your workforce actually is. A company where 80% of employees sit at desks with Microsoft 365 licenses has very different requirements from a retailer, healthcare system, or logistics company where the majority of workers are in the field without company devices. The platforms in this guide were not all designed for the same audience, and that gap matters more than any feature comparison. Once you know your workforce profile, match it to the platform's design center. Listening-first platforms like Culture Amp and Qualtrics EmployeeXM are purpose-built for measurement programs — they excel at survey design, people analytics, and connecting engagement data to outcomes, but they don't replace a communications or intranet layer. Intranet-first platforms like Simpplr and LumApps give desk-based organizations a strong digital headquarters with AI-enhanced search and content governance. Social-first platforms like Workvivo prioritize voluntary participation and culture visibility. Knowledge-first platforms like Guru solve specifically for the stale-wiki problem inside tools employees already use. Organizations with a meaningful frontline population — retail, healthcare, manufacturing, hospitality, distribution — should pay particular attention to whether a platform was built for the frontline from the start or retrofitted to support it. Adoption rates tend to tell that story quickly. For frontline-heavy organizations evaluating a single platform that covers communications, operations, HR, and learning without requiring separate tools or separate logins for each, MangoApps is worth a close look. --- # The Best Frontline Communication Software of 2026 **Author:** The MangoApps Team **Published:** 2026-05-15 **Category:** comparisons Discover the best frontline communication software available in 2026, compare top options, and find the right fit for your organization. Most corporate communication tools were built for people with a desk, a company email address, and a laptop. For the 2.7 billion deskless workers worldwide — the retail associates, caregivers, drivers, hotel staff, and warehouse crews who keep organizations running — those tools simply don't reach. Frontline communication software closes that gap, giving organizations a direct line to every employee regardless of whether they have a corporate device or an inbox. This guide covers the best platforms available in 2026, what separates them, and how to choose the right one for your workforce. Software Best For Workforce Fit Platforms MangoApps Enterprise-grade frontline communication with full workflow depth across comms, operations, HR, and learning on one platform Mixed desk + frontline; 500 to 100,000+ employees Web, iOS, Android, Desktop Blink Mobile-first frontline communication for shift-based and hourly workers without corporate email Predominantly deskless; mid-market to enterprise Web, iOS, Android, Desktop Connecteam SMB and mid-market frontline teams needing communications bundled with scheduling and time tracking Small to mid-size deskless teams; free tier available Web (admin), iOS, Android Staffbase Enterprise multichannel communication across mixed desk and frontline workforces at global scale Large enterprise; desk + frontline mix Web, iOS, Android, Desktop, Digital Signage Workvivo Engagement-first employee experience for organizations prioritizing culture, recognition, and social interaction Mid-market to enterprise; desk-primary with frontline extension Web, iOS, Android, Desktop, Digital Signage Firstup AI-personalized communication delivery for large enterprises with complex audience segmentation needs Enterprise; critical frontline populations Web, iOS, Android, Digital Signage Speakap Branded mobile-first frontline app for retail, hospitality, and manufacturing without heavy IT involvement Mid-market; frontline-first; white-label preference Web, iOS, Android Beekeeper Purpose-built frontline communication with strong offline capabilities and no-code workflow tools Frontline-only or frontline-heavy organizations Web, iOS, Android MangoApps 4.6/5 Stars · Gartner Peer Insights 2M+ Users · Trusted Worldwide Gartner MQ Visionary · Intranet Packaged Solutions (2025) IDC MarketScape Leader · Employee Experiences (2024) Forrester Wave Strong Performer · Intranet Platforms (Q2 2026) Reworked IMPACT Award (Gold) · Intranet & Communications Platforms [MangoApps](https://www.mangoapps.com/) is the Enterprise Workforce Platform Built for the Frontline — and the [Internal Communications Suite](https://www.mangoapps.com/solutions/internal-communications) reflects 15+ years of building for organizations where most employees don't have a desk or a corporate email address. Multi-channel delivery across mobile push, digital signage, SMS, and email means every message reaches every worker on the device they actually carry. Audience targeting by role, location, shift, department, or any HRIS attribute means communications teams can segment precisely without manual list management. And because MangoApps runs communications, operations, HR, and learning on the same platform, a shift update sits alongside a task assignment, a schedule change, and a training reminder in the same employee app — that structural depth is what separates it from point solutions that only solve one piece of the problem. **Key capabilities:** - **[Critical Alerts](https://www.mangoapps.com/key-features/critical-alerts):** Urgent safety and operational notifications with mandatory read receipts, escalation rules, and documented audit trails for compliance — designed for the moments when "did everyone see this?" is not a rhetorical question. - **[Campaigns & Journeys](https://www.mangoapps.com/key-features/campaigns-and-journeys):** Automated, multi-step communication sequences triggered by events or dates, so onboarding, open enrollment, safety training cycles, and policy acknowledgments run without manual follow-up. - **[Analytics & Insights](https://www.mangoapps.com/analytics-insights):** Real-time engagement data by audience segment, content type, and channel — showing not just who opened a message but who acted on it, so communications teams can prove reach and adjust strategy with actual evidence. - **AI-powered translation and personalization:** Embedded AI translates content automatically across languages and personalizes each employee's feed based on role, location, and behavior — no separate module, no additional cost. - **[200+ integrations](https://www.mangoapps.com/integrations/):** Native connectors to Workday, UKG, ADP, SAP SuccessFactors, Microsoft 365, and more mean audience lists stay current automatically, and employees authenticate with credentials they already have. **What customers say:** [A.S. Watson Benelux](https://www.mangoapps.com/customers/) operates 1,700 stores across four countries with 27,000 employees — most of them in their early twenties, none of them with company email addresses. Before MangoApps, schedule changes were posted as WhatsApp photos. Store managers fielded constant questions from employees who missed or deleted them. After deploying MangoApps as their branded employee app, over 80% of Kruidvat's 16,000+ employees became active users — without any formal training, because the platform was intuitive enough that employees created their accounts before even meeting with store managers. "There are 16,000 employees in Kruidvat, and they all use the mobile app to access MangoApps." — Jan Kees Fokkens, Social Intranet Project Manager, A.S. Watson Benelux Today, 20,000+ retail employees across the organization receive their weekly schedules through the app. Store managers no longer field schedule questions. Knowledge flows peer-to-peer across stores and countries, not just top-down through a cascade. MangoApps also backs every deployment with an [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee) — a formal commitment to 90%+ adoption in 90 days that no other platform in this category offers. **Free version:** No **Pricing:** Modular, quote-based; contact for enterprise pricing **Platforms:** Web, iOS, Android, Desktop [Schedule a demo to see MangoApps in action](https://www.mangoapps.com/schedule-a-call) Blink Blink is a mobile-first employee super-app built specifically for deskless and shift-based workers — retail, hospitality, logistics, healthcare, transit, and manufacturing. Employees sign in with a mobile number rather than a corporate email address, which removes the most common barrier to frontline adoption. The platform combines a social news feed, secure chat, and a content hub that can surface third-party web tools (timesheets, payroll portals, training systems) as mobile micro-apps behind a single sign-in, reducing the number of separate apps frontline workers need to open. - News feed with mandatory-read acknowledgement tracking and audit logs for compliance-sensitive communications - Unified "digital front door" that surfaces existing web tools as mobile micro-apps accessible from one app - Blink IQ analytics covering engagement by team, manager, and location **Free version:** No (limited free trial available) **Pricing:** Paid; Business and Enterprise tiers, quote-based **Platforms:** Web, iOS, Android, Desktop [Explore Blink](https://www.joinblink.com) Connecteam Connecteam is an all-in-one workforce management app for deskless and frontline teams, with a particular strength in the SMB and mid-market. Its Communications Hub bundles a company news feed, group chat, surveys, an employee directory, and announcements alongside scheduling, time tracking, and digital forms — making it one of the most affordable ways for smaller organizations to move past group texts and spreadsheets. The platform uses a modular hub-based pricing model, so buyers pay only for the capabilities they need. - Three modular hubs (Operations, Communications, HR and Skills) with independent tier selection, so organizations can start with communications alone and add ops or HR features without switching platforms - Built-in training and courses, digital forms, and checklists tied directly to the communication feed - Genuinely free tier for teams of 10 or fewer, with no feature gating on core communication tools **Free version:** Yes — free for up to 10 users; 14-day trial on paid plans **Pricing:** Freemium; paid plans from approximately $29/month flat for up to 30 users, then per-user; Enterprise on request **Platforms:** Web (admin), iOS, Android [Explore Connecteam](https://connecteam.com) Staffbase Staffbase is an enterprise employee experience platform built to connect headquarters and corporate communicators with large, mixed desk-and-frontline workforces. Its core strength is multichannel orchestration: a single piece of content can be published once and delivered simultaneously through a branded mobile app, an intranet, an email newsletter, SMS, and digital signage — reaching every employee segment through their preferred channel. The platform has expanded significantly into AI-native capabilities, including auto-translation across 75+ languages and AI-assisted content creation and news digests. - True multichannel publishing from a single editor to mobile app, intranet, email, SMS, and digital signage simultaneously - AI-native foundation with embedded translation, personalized news digests, AI search, and an employee AI assistant - "Smart Impact" measurement suite that tracks content comprehension and action taken, not just opens and clicks **Free version:** No **Pricing:** Enterprise; custom quote based on workforce size, channels, and scope **Platforms:** Web, iOS, Android, Desktop, Digital Signage [Explore Staffbase](https://staffbase.com) Workvivo Workvivo is an employee experience platform owned by Zoom that leads with social-style engagement: a news feed built around recognition, shoutouts, livestreams, and peer interaction rather than top-down broadcast. The platform has proven strong adoption in organizations where culture and belonging are the primary communication goals, and it extends to frontline workers through a mobile app experience that mirrors the desktop version. Organizations already standardized on Zoom will find native integration a practical advantage. - Consumer-grade social feed with recognition shoutouts, livestreams, and podcasts designed to drive participation rather than passive consumption - Native employee listening through pulse surveys, polls, and sentiment analytics built into the platform - Tight Zoom integration alongside Microsoft 365 and Google Workspace connectors, with digital signage support for shop floors and break rooms **Free version:** No **Pricing:** Enterprise; Business and Enterprise plans, sales-quoted **Platforms:** Web, iOS, Android, Desktop, Digital Signage [Explore Workvivo](https://www.workvivo.com) Firstup Firstup is an intelligent communication platform built for large enterprises that need to reach critical frontline populations at scale. Its defining capability is AI-driven workforce orchestration: automated communication journeys triggered by employee lifecycle events, with timing optimized by machine learning to maximize engagement. The platform targets enterprise buyers who need to segment complex, global audiences across multiple channels and prove communication impact with detailed analytics. - Workforce Orchestration engine with AI-timed delivery, automated employee journeys for onboarding, benefits, and safety, and audience block targeting down to precise subgroups - True omnichannel delivery across branded mobile app, intranet, email, and digital signage from one platform - Deep enterprise integrations with Workday, UKG, Concur, and Microsoft 365, with data export to BI tools including Tableau and Looker **Free version:** No **Pricing:** Enterprise; custom quote **Platforms:** Web, iOS, Android, Digital Signage [Explore Firstup](https://firstup.io) Speakap Speakap is a fully white-labeled employee experience app purpose-built for frontline industries including retail, hospitality, manufacturing, construction, and logistics. Organizations brand the app entirely as their own, with rapid setup that does not require significant IT involvement. The platform is well-suited for mid-market buyers who want a polished, frontline-focused communication tool without the complexity or cost of enterprise platforms, and for organizations operating across multiple countries who need multilingual support out of the box. - Fully white-labeled mobile app under the customer's own brand, with fast deployment and minimal IT dependency - Employee Journeys for guided onboarding, recurring training, and targeted news feed content with read acknowledgements and polls - Multilingual support across 20+ languages with an API marketplace for integrating HR, scheduling, and POS systems behind a single sign-on **Free version:** No **Pricing:** Paid; tiered plans (Basic, Premium, Premium+), quote-based **Platforms:** Web, iOS, Android [Explore Speakap](https://speakap.com) Beekeeper by Lumapps Beekeeper is a frontline success platform built exclusively for deskless workers, with particular depth in operational workflows alongside communication. The platform's combination of targeted news streams, secure messaging, AI-powered translation across 200+ languages, and no-code forms and workflows makes it a strong fit for organizations whose frontline workers need more than a news feed. Beekeeper was acquired by LumApps in 2025, which is expanding its positioning toward an integrated AI Employee Hub spanning both frontline and desk-based workers — buyers should factor that into roadmap and procurement conversations. - Streams (targeted news feeds), secure 1:1 and group chat, and voice messaging, designed to replace unauthorized personal messaging apps like WhatsApp - Inline AI translation across 200+ languages with AI-generated chat summaries so workers don't miss critical updates even across language barriers - No-code workflows, offline-capable forms, and shift management integrations with HRIS, LMS, and payroll systems **Free version:** No (14-day free trial available) **Pricing:** Paid; tiered plans, custom quote **Platforms:** Web, iOS, Android [Explore Beekeeper](https://www.beekeeper.io) ## What is Frontline Communication Software? Frontline communication software is a category of tools designed to connect organizations with employees who don't work at a desk. Traditional intranet platforms, company email systems, and enterprise messaging tools were built around the assumption that every worker has a laptop, a corporate account, and time to sit at a screen. That assumption excludes the majority of the global workforce: the store associates, nurses, drivers, hotel staff, factory workers, and field technicians who make up roughly 80% of employed people worldwide. Frontline communication platforms close that gap by delivering information directly to the phones employees already carry, without requiring a company email address. Core capabilities typically include a mobile news feed with push notifications, manager-to-team messaging, targeted announcements by role or location, read acknowledgements for compliance-critical communications, and a searchable directory. More mature platforms add two-way communication tools (surveys, polls, open comments), digital signage for break rooms and shop floors, integration with HR and scheduling systems to keep audience data current, and analytics that show actual reach rather than assumed reach. ## Why Frontline Communication Matters When frontline workers don't receive consistent, direct communication from their organization, the costs are concrete. [Gallup research](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) consistently links poor manager communication and low engagement to higher absenteeism, lower productivity, and turnover that costs roughly 40% of a frontline worker's annual salary to replace. In retail and hospitality, where annual turnover routinely exceeds 60-70%, those costs compound fast. The inverse is equally true. Organizations with strong internal communications are [4.5 times more likely to have engaged employees](https://www.gallup.com/workplace/236927/employee-engagement-drives-growth.aspx), and [Gallup's 2024 State of the Global Workplace report](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) estimates that disengagement costs the global economy $8.8 trillion annually — 9% of global GDP. A communication platform that actually reaches frontline workers isn't a nice-to-have. For industries with large hourly or deskless workforces, it's one of the highest-leverage investments a people or operations team can make. ## What Features Should I Look for in Frontline Communication Software? **Mobile access without corporate email.** This is the threshold requirement. If your frontline workers don't have company email addresses, any platform that requires one will fail at rollout. Look for sign-in options using a phone number, employee ID, or single sign-on tied to your HRIS. **Audience targeting and segmentation.** Broadcast-to-all is a ceiling, not a feature. The platforms worth considering let you target by role, location, shift, department, tenure, or any attribute in your HR system. Workers in your Dallas warehouse shouldn't receive Seattle weather alerts. Retail associates shouldn't be confused by communications intended for corporate finance. **Read acknowledgement and compliance tracking.** For safety notices, policy updates, and regulatory training, "sent" is not the same as "received." Look for mandatory-read flows with documented confirmation timestamps and exportable audit logs. This is particularly important in healthcare, financial services, and any industry subject to OSHA, HIPAA, or similar compliance requirements. **Two-way communication.** A platform that only broadcasts misses half the value. Comments, reactions, peer-to-peer messaging, and pulse surveys give employees a voice and give managers signal about what's landing, what's confusing, and what's being ignored. Engagement is easier to sustain when communication flows in both directions. **Analytics and reach measurement.** Most platforms report open rates. Better platforms report comprehension, action rates, and reach by segment. Before selecting a tool, ask: can I see which locations had the lowest read rates on my last safety update? Can I prove to HR leadership that a compliance communication reached 98% of the workforce within 24 hours? If the answer is no, the analytics are decorative. **HRIS and scheduling integrations.** Audience lists built manually go stale within weeks. Platforms that pull from your HRIS keep targeting current automatically, ensure departed employees lose access immediately, and let you trigger communications based on workforce events like new hire start dates, shift assignments, or department transfers. ## How to Choose the Right Frontline Communication Software Start with your workforce composition. If your organization is entirely or predominantly deskless, a purpose-built frontline platform like Blink, Beekeeper, or Connecteam will reach those workers faster and at lower complexity than an enterprise platform built for mixed workforces. If you have a significant desk-based population alongside frontline teams, a platform that handles both without requiring separate tools or separate admin is worth the additional evaluation effort. Next, consider whether frontline communication is your only near-term need, or part of a broader platform consolidation. Many organizations start by solving communication and find themselves managing six separate tools for scheduling, training, HR, and task management two years later. If workforce operations, learning, and HR administration are also on the roadmap, evaluating a unified platform from the start avoids a second migration. Organizations with large frontline workforces and plans to consolidate those workflows onto a single platform should put MangoApps on their shortlist — the depth of the platform, combined with an [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee) that no point solution offers, makes the evaluation straightforward. Finally, factor in security and compliance requirements. Healthcare organizations dealing with HIPAA, financial services firms subject to data residency rules, government contractors with FedRAMP requirements, and enterprises operating across the EU under GDPR all face non-negotiable compliance constraints. Not every frontline communication platform meets those bars. Verify certifications — HITRUST, SOC 2 Type II, ISO 27001 — before shortlisting, not after. --- # The Best Internal Communications Software of 2026 **Author:** The MangoApps Team **Published:** 2026-05-12 **Category:** comparisons Discover the best internal communications software available in 2026, compare top options, and find the right fit for your organization. Most companies don't have a communication problem. They have a reach problem. Email goes to the people with corporate accounts. The intranet gets visited once a quarter. And the nurses, store associates, warehouse technicians, and drivers who make up the majority of the workforce go another shift without hearing anything from the company they work for. The right internal communications software fixes that, not just for the desk workers, but for everyone. This guide covers the best options available in 2026, what each does well, and how to choose the one that fits your organization. ## Quick Comparison of the Best Internal Communications Software Software Best For Workforce Fit Platforms MangoApps Multi-channel comms, acknowledgment tracking, and native workforce operations in one app Frontline and mixed workforces Web, iOS, Android, Desktop Staffbase Multichannel publishing to app, intranet, email, SMS, and signage from one CMS; Microsoft 365-heavy organizations Mixed and frontline Web, iOS, Android, Desktop, Digital Signage Simpplr AI search, content governance, and knowledge-worker intranet experience Primarily desk workers Web, iOS, Android, Desktop Workvivo by Zoom Social-experience-led comms for organizations standardized on Zoom Mixed workforces Web, iOS, Android, Desktop Microsoft Viva Comms and community inside the Microsoft 365 ecosystem Primarily desk workers Web, iOS, Android, Desktop Firstup Orchestrated, personalized multi-channel campaigns at enterprise scale Mixed and frontline Web, iOS, Android, Desktop, Digital Signage Blink Organizations where most employees have no corporate email Frontline workers Web, iOS, Android, Desktop Poppulo High-volume email and digital signage programs for enterprise IC teams Primarily desk workers Web, iOS, Android, Desktop, Digital Signage Happeo Google Workspace-native intranet for cloud-first organizations Primarily desk workers Web, iOS, Android, Desktop MangoApps 4.6/5 Stars · Gartner Peer Insights 2M+ Users · Trusted Worldwide Gartner MQ Visionary · Intranet Packaged Solutions (2025) IDC MarketScape Leader · Employee Experiences (2024) Forrester Wave Strong Performer · Intranet Platforms (Q2 2026) Reworked IMPACT Award (Gold) · Intranet & Communications Platforms ### Why MangoApps? MangoApps is the [Frontline Workforce Superapp](https://www.mangoapps.com/), and internal communications is where that distinction matters most. While most communications platforms are built for the people at desks, MangoApps was built specifically for organizations where the majority of employees work on the floor, in the field, or on the road. The [Internal Communications Suite](https://www.mangoapps.com/solutions/internal-communications) delivers multi-channel message delivery, audience targeting, acknowledgment tracking, and analytics, all in the same app where employees already manage their schedules, training, and HR tasks. There is no separate login, no second app to download, and no dependency on a corporate email address. For organizations with mixed workforces, that architecture produces results that purpose-built comms tools cannot match. MangoApps has delivered [90%+ adoption within 90 days](https://www.mangoapps.com/adoption-guarantee) across its customer base, including some of the largest enterprises in the world. The platform integrates with [200+ enterprise systems](https://www.mangoapps.com/integrations/) including Workday, SAP SuccessFactors, Microsoft 365, and Google Workspace, and meets the security requirements of the most regulated industries: [HITRUST, SOC 2 Type II, and ISO 27001 certified](https://www.mangoapps.com/security-compliance), with FedRAMP ATO available. **Key capabilities for internal communications:** - [Multi-channel delivery](https://www.mangoapps.com/key-features/campaigns-and-journeys): news feed, push notifications, SMS, email, and in-app banners all sent from a single content management interface, with targeting by role, location, department, or custom audience segment. - [Acknowledgment tracking](https://www.mangoapps.com/key-features/critical-alerts) and read receipts for policy attestation, compliance communications, and critical safety alerts, with automated reminders to non-readers and a full audit trail. - [AI-assisted content creation](https://www.mangoapps.com/key-features/posts) and translation into 50+ languages, so a single message published by a corporate communications team reaches every employee in the language they work in. - [Embedded analytics](https://www.mangoapps.com/analytics-insights): message reach, open rates, engagement by audience segment, and acknowledgment completion rates, giving communications teams real data on what is actually landing. - [Modular expansion](https://www.mangoapps.com/pricing): the same app that runs communications natively runs shift scheduling, task management, training, HR records, and more, so adding a new capability is a configuration, not a new implementation. **Customer proof:** [Benchmark Human Services](https://www.mangoapps.com/resources/benchmark-human-services), a healthcare organization with 4,000+ employees where 85% of staff work in the field without corporate email, turned to MangoApps to solve a communication problem that email simply could not reach. "It was critical for us to relay important information and create that sense of engagement among our staff who typically tend to be pretty siloed in their workplaces." -- Courtney Heiser, Director of Communications, Benchmark Human Services Within a few months of launch, over one-third of Benchmark's employees had incorporated the app into their daily work. Critical COVID-19 health and safety information reached caregivers in the field in real time. For an organization where the historical alternative was hoping a message traveled down through a phone tree, that result speaks for itself. **Free version:** No **Pricing:** Modular, quote-based; contact for enterprise pricing **Platforms:** Web, iOS, Android, Desktop [Schedule a demo to see MangoApps in action](https://www.mangoapps.com/schedule-a-call) Staffbase ### Why use Staffbase? Staffbase is built around a unified multichannel publishing model: one content management system that distributes messages to a branded employee app, intranet, email newsletter, SMS, and digital signage simultaneously. It is a well-established option for large enterprises with a professional internal communications function, particularly those standardized on Microsoft 365, given its deep integrations with Azure AD, Teams, and SharePoint. - Unified multichannel publishing to app, intranet, email, SMS, and digital signage from one CMS, with audience targeting in 75+ languages. - Native Microsoft 365 integration including Azure AD, Teams, SharePoint, and Microsoft Copilot grounding for AI-generated answers sourced from governed company content. - Editorial planning calendar and analytics dashboard with open rates, reach, and sentiment by segment. **Free version:** No **Pricing:** Enterprise, quote-based (reportedly starting around $30,000/year for 1,000 employees) **Platforms:** Web, iOS, Android, Desktop, Digital Signage [Explore Staffbase](https://staffbase.com/) Simpplr ### Why use Simpplr? Simpplr is an AI-powered intranet and employee experience platform oriented toward knowledge-worker organizations. It runs on Salesforce infrastructure and centers on AI search and content governance: employees ask a question and get a synthesized answer grounded in the company's actual documents, policies, and HR data across connected systems. - AI Assistant and enterprise search that unifies answers across Slack, Salesforce, SharePoint, and other connected systems. - Comms AI workspace with newsletter builder, editorial calendar, and multichannel campaign management across web, mobile, and email. - Sentiment analysis, manager dashboards, and auto-governance for content lifecycle management to keep company information accurate over time. **Free version:** No (14-day trial available) **Pricing:** Enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop [Explore Simpplr](https://simpplr.com/) Workvivo by Zoom ### Why use Workvivo? Workvivo is a social-experience-led internal communications platform, now part of Zoom. It is built on the premise that employees engage more consistently with platforms that feel familiar rather than corporate, and for organizations already standardized on Zoom it ships as a native tab inside the Zoom desktop client alongside meetings, chat, and whiteboard. - Social feed with company-value tagging, recognition, podcasts, and livestreams designed to encourage ongoing engagement beyond top-down announcements. - Native Zoom integration with Workvivo AI powered by Zoom AI Companion included at no extra cost. - Workvivo TV for digital signage, rich-media content, and targeted audience channels in addition to the core feed. **Free version:** No **Pricing:** Business plan starts at $20,000/year (250+ users); Enterprise custom **Platforms:** Web, iOS, Android, Desktop (native Zoom client) [Explore Workvivo](https://workvivo.com/) Microsoft Viva ### Why use Microsoft Viva? For organizations standardized on Microsoft 365, Viva consolidates several communications capabilities within the Microsoft ecosystem. Viva Connections delivers a SharePoint-powered intranet inside Teams. Viva Engage handles communities, leadership announcements, and AMAs. Viva Amplify is the multichannel publishing tool for IC teams, sending to Teams, Outlook, and SharePoint from a single interface. The core Connections experience is included in M365 SharePoint licenses at no extra cost. - Deep integration with Microsoft 365, Teams, SharePoint, Entra ID, and Copilot at no additional infrastructure cost. - Viva Amplify multichannel campaign publishing to Teams, Outlook, and SharePoint with built-in reach and engagement analytics. - Viva Engage Premium for Leadership Corner, executive AMAs, sentiment analysis, and Copilot-assisted content creation. **Free version:** Partial (Viva Connections core included with M365 SharePoint plans) **Pricing:** Communications & Communities bundle ~$2/user/month; full Viva suite ~$12/user/month **Platforms:** Web, iOS, Android, Desktop (Microsoft Teams) [Explore Microsoft Viva](https://microsoft.com/microsoft-viva) Firstup ### Why use Firstup? Firstup is built for large, distributed enterprises that need to orchestrate personalized communication across many channels simultaneously. Its core differentiator is automated employee journey orchestration: campaigns that sequence and adapt based on employee role, lifecycle event, location, or behavior, rather than sending the same message to the entire organization. - Intelligent targeting and automated journey orchestration for sequenced campaigns triggered by role, lifecycle event, location, or behavior. - Omnichannel reach across employee app, branded intranet, email, SMS, push notifications, and digital signage from one platform. - Engagement analytics with acknowledgment tracking and compliance attestation reporting. **Free version:** No **Pricing:** Enterprise, quote-based **Platforms:** Web, iOS, Android, Desktop, Digital Signage [Explore Firstup](https://firstup.io/) Blink ### Why use Blink? Blink is designed for organizations whose employees don't have corporate email and can't check a desktop intranet between shifts. It packages social feed, secure 1:1 and group chat, document hub, and SSO-wrapped shortcuts into one mobile app that can be set up with nothing more than a phone number. - Frontline-first super-app combining social feed, secure chat, document hub, and SSO-wrapped access to existing HR and scheduling tools, with no corporate email required. - Mandatory-read tracking with acknowledgment logging, audit trails, and automated reminders for compliance and safety communications. - Embedded workforce micro-apps: open shifts, shift swaps, e-payslips, and leave requests directly in the feed. **Free version:** Yes (Starter tier for small teams) **Pricing:** Business and Enterprise tiers above Starter are quote-based **Platforms:** Web, iOS, Android, Desktop [Explore Blink](https://joinblink.com/) Poppulo ### Why use Poppulo? Poppulo is an enterprise employee communications platform that combines email, intranet, and digital signage under one campaign management interface. It is oriented toward IC teams that manage high-volume, measurement-driven communications programs and need channel-level analytics that can be reported upward. - Internal email and newsletter platform with dynamic personalization, auto-resend to non-openers, and click-mapped analytics. - Enterprise digital signage integrated with the same campaign manager used for email and intranet content. - Multichannel governance with parent-child account structure, SSO support, ISO 27001 and SOC 2 Type II compliance, and full audit logging. **Free version:** No (21-day free trial of email product available) **Pricing:** Enterprise, quote-based (Essentials, Pro, and Enterprise tiers) **Platforms:** Web, iOS, Android, Desktop, Digital Signage [Explore Poppulo](https://poppulo.com/) Happeo ### Why use Happeo? Happeo is a Google Workspace-native intranet and internal communications platform built for cloud-first organizations that have outgrown shared Drives, email, and Slack but don't want a SharePoint deployment. It auto-builds org charts from Google Directory, supports in-line editing of Docs, Slides, and Sheets inside the intranet, and unifies company pages with social-style channels in a single navigation. It is typically up and running in weeks rather than months. - Native Google Workspace integration: org chart from Google Directory, Drive-backed file storage, in-line editing, and embedded Meet and Chat. - Channels for social-style communication and Pages for structured knowledge, with federated search across Google Drive and connected apps. - Pre-built page templates for HR, IT, onboarding, and policies designed for fast, low-resource deployment. **Free version:** No **Pricing:** Paid/Enterprise, three tiers (Essential, Business, Enterprise), quote-based **Platforms:** Web, iOS, Android, Desktop [Explore Happeo](https://happeo.com/) ## What is Internal Communications Software? Internal communications software is the category of tools organizations use to send, manage, and measure messages to their workforce. At its most basic, it replaces or supplements email as the channel for announcements, policy updates, and leadership messages. At its most advanced, it is a full multi-channel platform: a branded employee app, an intranet, an email newsletter tool, a digital signage system, and a campaign analytics dashboard, all managed by a communications team from a single interface. The category has evolved considerably in the past several years. The original internal comms tools were either static intranets that no one visited or mass email blasts that no one read. Today's leading platforms are built around reach, not broadcast: they target messages by role, location, department, and behavior. They track whether employees actually read and acknowledged what was sent. They surface AI-generated content recommendations and translate messages into dozens of languages in real time. And the best of them are built to reach the 80% of the workforce that works without a desk, a corporate email address, or reliable access to a browser. ## Why Internal Communications Matters There is a direct line between employee communication and business performance, and it is stronger than most leadership teams realize. According to [Gallup's State of the Global Workplace 2026](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx), only 20% of employees worldwide are engaged. [Gallup's Q12 meta-analysis](https://www.gallup.com/workplace/236927/employee-engagement-drives-growth.aspx) links top-quartile engagement to 23% higher profitability, 18% higher productivity, 81% lower absenteeism, and 18% to 43% lower turnover. Disengagement, which is a direct result of employees feeling uninformed and disconnected, costs the global economy roughly [$10 trillion per year](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx). The gap between the perception and the reality of internal communications is significant. Only 53% of employees agree. That gap, between what leadership believes is happening and what employees actually experience, is exactly what internal communications software is designed to close. The urgency is higher for frontline workers. [Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) research found workers toggling between applications roughly 1,200 times a day. For a nurse, a store associate, or a distribution warehouse technician, that time is not available. They are on their feet, attending to customers or patients, moving product, running a shift. If the communication does not reach them in the first thirty seconds they have to look at a phone between tasks, it does not reach them at all. ## What Features Should I Look for in Internal Communications Software? The right feature set depends on who you are trying to reach and how. These are the capabilities that separate platforms that actually work from platforms that look good in a demo. **Multi-channel reach.** No single channel reaches everyone. Look for a platform that can deliver the same message to a mobile app, email, SMS, and digital signage simultaneously, with targeting built in at the audience segment level. Organizations with frontline workers need channels that do not require a corporate email address. **Acknowledgment tracking.** Sending a message and knowing it was received are different things. Compliance-driven communications, safety alerts, and policy updates require proof that employees read and understood what was sent. Look for acknowledgment workflows, read receipts, automated reminders to non-readers, and an audit trail exportable for legal and compliance purposes. **Audience targeting and segmentation.** The ability to send the right message to the right group, not a company-wide blast, is what separates a communications platform from a company-wide email chain. Look for targeting by role, location, department, shift, hire date, or custom attribute synced from your HRIS. **Analytics and measurement.** Internal communications teams are increasingly expected to prove impact. Look for open rates, reach by segment, acknowledgment completion rates, and trend data over time. Platforms that surface engagement analytics in a dashboard format, rather than requiring manual report pulls, save significant time. **Integration with existing systems.** The best internal communications platform for your organization is the one that connects to what you already use. Look for pre-built integrations with your HRIS, Active Directory or identity provider, Microsoft 365 or Google Workspace, and any workforce management tools your teams depend on. **Governance and content lifecycle management.** Information that is published once and never updated is worse than no information, because it misleads employees. Look for auto-governance reminders, content expiration dates, and workflow tools that make it easy for content owners to review and update material on a defined schedule. ## What regulated enterprises should require for message acknowledgment In healthcare, financial services, insurance, utilities, and pharmaceutical manufacturing, communication is a records problem. Read receipts show a message was opened; they do not show that a specific employee confirmed a specific version. Regulated enterprises should require mandatory acknowledgment tied to the employee's identity from the HRIS and to the message version, escalation to the manager when acknowledgment is missing, re-acknowledgment when a policy changes, tamper-evident audit logs, retention by content type with legal hold, and an export per message and per employee that an auditor can read. Reach matters as much as the record: employees without corporate email must be included through app, SMS, kiosk, or signage delivery, or the acknowledgment rate describes only the desk staff. Ask each vendor to show the acknowledgment export for a policy that changed version mid-rollout, to deliver a mandatory read to an employee with no email on a shared kiosk, and to demonstrate what legal hold suspends. Among the platforms above, MangoApps publishes Critical Alerts with mandatory read receipts, escalation rules, and documented audit trails, with eDiscovery, legal hold, and retention policies per [mangoapps.com/security](https://www.mangoapps.com/security); verify acknowledgment depth and export for every other vendor during procurement. The full evaluation framework, including the regulations by industry and a regulated-lens comparison, is in [The Complete Guide to Internal Communications Platforms for Regulated Enterprises](https://www.mangoapps.com/articles/internal-communications-platform-regulated-enterprises). ## How to Choose the Right Internal Communications Software The most important question to answer before evaluating any platform is who you are actually trying to reach. If your workforce is primarily knowledge workers with corporate email and desktop access, an intranet-first platform like Simpplr or Happeo may serve you well. If a significant portion of your employees work without a desk, corporate email, or consistent access to a browser, you need a platform built for that reality from the ground up, not one that added a mobile app as an afterthought. The second question is what channels you need. Some platforms are built primarily around email and newsletter delivery. Some lead with digital signage. Some center on a mobile employee app. Some unify all channels under one content management system. Your communications team's workflows, your employees' habits, and the compliance requirements in your industry should drive that decision more than any feature comparison matrix. For frontline-heavy organizations, specifically those in healthcare, retail, manufacturing, hospitality, distribution, or field services, MangoApps is worth serious evaluation. The combination of multi-channel communications, acknowledgment tracking, and native workforce operations in a single app, without requiring a corporate email address to access, is difficult to match. With 90%+ adoption in 90 days and a 98% customer retention rate, the track record for frontline organizations is well established. Start by auditing what you have today. Map which employees are not being reached by your current tools. Then match the platform to that gap, not the other way around. *Discover the best internal communications software available in 2026, compare top options, and find the right fit for your organization.* --- # Equipping the Frontline Manager: Five Releases, One Thread **Author:** MangoApps Team **Published:** 2026-05-10 **Category:** workforce-management The hardest job in any frontline operation is the one in the middle. Not the executive setting direction, and not the worker carrying out the task — the manager who is supposed to translate one... # Equipping the Frontline Manager: Five Releases, One Thread The hardest job in any frontline operation is the one in the middle. Not the executive setting direction, and not the worker carrying out the task — the manager who is supposed to translate one into the other. They are expected to know which employee is quietly disengaging, which shift is missing a required certification, which supply order is stuck waiting on a signature. They are expected to act on information they may not even be receiving. And they are supposed to do all of this — often from a production floor, a hospital corridor, or a job site — with tools built for someone at a desk. This week's releases at MangoApps followed a thread. Spread across five different apps, they each addressed a different dimension of that same problem: the frontline manager is the leverage point in any field operation, and for too long, the software hasn't worked at their level. --- ## The Intelligence Layer: Knowing Who Needs Attention The release that anchors this week is [Mango Signal](https://www.mangoapps.com/changelog/2969) — a new workforce intelligence app that detects engagement, performance, and risk signals across the platform, surfaces them to managers with a recommended action, and then tracks whether that action was taken and whether conditions improved. The distinction between this and a dashboard is worth pausing on. Dashboards give managers data. Mango Signal gives them a prompt: here is who to have a conversation with, here is what the pattern looks like, and here is what to do about it. That's a different product philosophy — one that acknowledges that frontline managers are not analysts, they are decision-makers, and what they need is not more data but better signal. The loop-closing piece is equally important. Most workforce analytics tools end at the alert. They identify the problem and stop there, leaving the manager to figure out the response and then mentally track whether it worked. Mango Signal follows through: once a recommended action is logged, the system continues monitoring the underlying conditions to see if things shifted. That's the difference between an early warning system and an intelligence layer. Organizations spend considerable resources on engagement surveys and attendance tracking, and then express frustration when manager behavior doesn't change in response. It usually doesn't change because the signal never reaches the manager in a form they can act on at a moment when they have bandwidth. That's the gap Mango Signal is designed to close. --- ## The Operational Middle: Scheduling, Skills, and Procurement Three other releases this week operated lower in the stack but addressed the same root constraint: managers being able to see what is happening in their domain and do something about it without creating an asynchronous back-and-forth. The [Schedule Requests Team Dashboard](https://www.mangoapps.com/changelog/2970) consolidates everything a manager's team has requested — schedule changes, time-off, swaps — into a single view so they can act from one surface instead of hunting down individual notifications. The accompanying on-behalf-of submission capability lets managers file schedule requests for employees who cannot access the platform themselves. This is a workflow that happens constantly in frontline organizations: someone calls in, the manager handles it, and previously that meant coordination that lived in text messages and tribal memory, invisible to the system of record. On the scheduling side, [skills-based role requirements](https://www.mangoapps.com/changelog/2970) let admins define what qualifications a role actually requires and have those requirements propagate automatically to every shift, with the ability to override on a per-shift basis. This removes one of the more persistent sources of scheduling error in compliance-sensitive environments: a manager fills an open slot with an available person, not realizing the role requires a certification that person doesn't hold. The system now carries that knowledge so the manager doesn't have to. In [procurement](https://www.mangoapps.com/changelog/2966), the approval workflow moved closer to the manager as well. Supply orders can now be approved or rejected directly from the order page, automatically triggering vendor purchase order creation and supplier email dispatch. The effect is the same pattern: one fewer asynchronous hand-off, one fewer moment where the right person is waiting on the wrong process. None of these are headline features. But for an operations manager juggling coverage gaps, regulatory requirements, and supply chain logistics across a distributed team, each one removes a specific friction point. Accumulated, these friction points can quietly consume an hour or more of a manager's day — time that was supposed to be spent on the floor with the team. --- ## Mobile, Because the Work Isn't at a Desk There is a persistent irony in building powerful manager tools that assume the manager is sitting at a computer. Safety incidents happen on the production floor. Supply problems surface during walkthroughs. The employee showing signs of disengagement is visible in person before they show up in any report. [Safety Hub's mobile manager workflows](https://www.mangoapps.com/changelog/2967) bring a category of actions that previously required desktop access — investigating incidents, following up on observations, scheduling toolbox talks, reviewing certifications — directly to the mobile app. The practical effect: a safety manager walking a job site can now close an incident loop in the moment it surfaces, rather than making a mental note to follow up when they get back to a computer. In safety-critical environments, the time between observation and documentation matters. Reducing that interval is not just a convenience feature — it's a compliance consideration. The [Camera-First Media Inbox](https://www.mangoapps.com/changelog/2966) addresses the adjacent problem: workers and managers in the field have always taken photos on their phones. Getting those photos into the right records has always been a manual, friction-laden step that often doesn't happen at all. The new mobile-first capture interface attaches photos to the correct records automatically based on GPS location, removing the translation step between "I documented this" and "the system knows about it." Both releases reflect the same design judgment: manager tools are only valuable if they work where managers are. The person responsible for safety on a construction site or a production floor is not in front of a monitor when the relevant decision needs to be made. --- ## The Pattern Behind the Week There is a reason "manager overload" appears on nearly every employee engagement survey, in nearly every industry that relies on frontline workers. It is not a lack of commitment or capability — it is a structural gap. The systems organizations deploy to capture workforce data were largely designed to surface that data to executives and HR teams. The manager, who is actually in a position to change things day to day, receives filtered, delayed, and often unactionable information. What this week's releases have in common — Mango Signal's recommended actions, the Team Requests dashboard, skills-based scheduling enforcement, mobile safety workflows, procurement approvals from the order page — is a view of the manager not as a reporting layer but as the person who actually changes outcomes on the ground. The design question behind each feature is not "how do we capture this data?" but "how do we make sure the right person can act on it at the right moment?" That shift in orientation, consistently applied across enough of the platform, is what eventually changes the ratio between data collected and action taken. The technology isn't the hard part. The hard part is maintaining the discipline to build for the person in the middle — the one who needs the system to work for them, not just around them. When that person is equipped, the data starts to matter. When the data starts to matter, the signals close. --- # MangoApps Wins Four ClearBox Intranet Choice Awards **Author:** MangoApps Team **Published:** 2026-05-08 **Category:** news-and-updates MangoApps earned four ClearBox Intranet Choice awards in 2026, including Top 5 Overall Score, Best for Value, Community Builder, and AI Innovator. **Top 5 Overall Score. Best for Value. Community Builder. AI Innovator. Four awards from one of the most rigorous independent intranet research firms in the market.** ClearBox Consulting has named MangoApps a winner in four Intranet Choice categories from their 2026 *Intranet and Employee Experience Platforms* report — one of the most thorough independent evaluations of intranet and digital workplace platforms published anywhere. The awards recognize [MangoApps](https://www.mangoapps.com/platform) across overall performance, value, community and engagement, and AI innovation. ## What ClearBox Is, and Why It Matters ClearBox is an independent UK-based research and consulting firm with deep expertise in intranets and employee experience platforms. Their annual report evaluates platforms through real-world scenarios — not vendor demos, not marketing materials — and is widely cited by HR, communications, and IT leaders making purchase decisions. The [Intranet Choice awards ](https://www.clearbox.co.uk/clearbox-intranet-choices-winners-2026/)are reserved for platforms that performed at the top of their category. ClearBox awards them to only a handful of vendors to retain a degree of exclusivity, which means they actually mean something. MangoApps received four. ## The Four Awards ### Top 5 Overall Score MangoApps finished in the top five platforms overall in the 2026 report, earning a total score of 32 out of 40 across all eight evaluation scenarios. ClearBox notes that when calculating total scores, they exclude "potential" points to reflect what platforms delivers without requiring additional effort or cost. A top-five finish means MangoApps delivers on what it promises. ![A hexagonal award badge reading "ClearBox Choice 2026" and "Top 5 Score" with a blue geometric icon at the top and a magenta lower section.](https://mango-cdn.b-cdn.net/marketing/uploads/Top_5_Score_ClearBox_Choices_Badge_2026.png) ### Best for Value This award goes to platforms that combine a competitive price point with high performance scores. MangoApps earned it by placing at the mid-price range while posting above-average scores across the majority of scenarios. For organizations that need an enterprise-grade [unified intranet and employee app](https://www.mangoapps.com/unified-intranet-employee-app) without an enterprise-grade price tag, MangoApps represents one of the strongest options in the market. ![Hexagonal award badge reading ClearBox Choice 2026 and Best for Value on a purple and white background with a blue geometric icon at the top.](https://mango-cdn.b-cdn.net/marketing/uploads/Best_for_Value_ClearBox_Choices_Badge_2026.png) ### Community Builder The Community and Engagement scenario is where MangoApps scored highest: 4.5 out of 5, among the highest in the category. ClearBox highlighted MangoApps' "rich social features and gamified recognition" as key differentiators. Connecting employees — whether they're in a corporate office, on a retail floor, or spread across a distributed workforce — is one of the core problems MangoApps was built to solve. ![Hexagonal award badge reading ClearBox Choice 2026 Community Builder with a blue geometric icon at the top and a purple lower section.](https://mango-cdn.b-cdn.net/marketing/uploads/Community_Builder_ClearBox_Choices_Badge_2026.png) ### AI Innovator ClearBox identified four themes from current AI trends across all platforms they assessed and awarded the AI Innovator badge only to those doing something "unusual and truly beneficial at the point of demonstration." MangoApps' [Enterprise AI Hub](https://www.mangoapps.com/solutions/employee-app#ai), which puts AI assistants directly inside the workflows employees are already running — not as a separate tool or add-on — stood out in evaluation. ![A hexagonal ClearBox Choice 2026 badge with a blue geometric icon at the top and the text AI Innovator in large white letters on a teal background.](https://mango-cdn.b-cdn.net/marketing/uploads/AI_Innovator_ClearBox_Choices_Badge_2026.png) ## What ClearBox Observed Here is how ClearBox described MangoApps in the 2026 report, attributed to ClearBox Consulting: **Why choose this product:** > "MangoApps is a comprehensive and versatile platform that would be very well suited to multi-site organisations with many employee audiences. It combines intranet and teamworking features expected for knowledge workers but also caters very well for frontline employees, with its range of task management and communication tools, as well as a solid mobile experience. MangoApps offers good value for money, sitting at the mid-price point range, and would appeal to larger organisations." **The product in a nutshell:** > "MangoApps is an all-in-one platform that combines a highly customisable intranet, robust analytics, and strong mobile and frontline support, making it ideal for medium to large organisations with a widely distributed workforce." The scenario scores reinforce the narrative. MangoApps finished above average in six of eight evaluation scenarios and received ClearBox "highlights" — notes reserved for particularly strong capabilities — in four: | Scenario | Score | Above Average | Includes Highlight | Key Benefit | | --- | --- | --- | --- | --- | | [Employee Experience](https://www.mangoapps.com/unified-intranet-employee-app) | 4/5 | | Y | Highly configurable Dashboards and notifications | | [Communications Management](https://www.mangoapps.com/solutions/modern-intranet) | 4/5 | Y | Y | Flexible publishing tools across multiple channels | | [Community and Engagement](https://www.mangoapps.com/solutions/employee-engagement) | 4.5/5 | Y | Y | Rich social features and gamified recognition | | [Digital Workplace Integrations and Services](https://www.mangoapps.com/integrations/list) | 3(1)/5 | Y | | Widget-driven approach makes adding third-party integrations to dashboards simple | | [Knowledge and Content Management](https://www.mangoapps.com/solutions/knowledge-management) | 4/5 | Y | Y | Robust knowledge sharing and compliance | | [Information Finding and Search](https://www.mangoapps.com/solutions/knowledge-management) | 4/5 | Y | | Federated search and AI assistants make finding people and content fast and intuitive | | [Mobile and Frontline Support](https://www.mangoapps.com/solutions/employee-app) | 4.5/5 | Y | | Flexible and effective mobile experience offers many options for frontline workers | | [Platform Management](https://www.mangoapps.com/key-features) | 4(0.5)/5 | Y | | Excellent platform control options | ## The Context Behind the Scores MangoApps has been building for the [frontline workforce](https://www.mangoapps.com/solutions/employee-app) since 2008. The platform now serves 2 million+ users worldwide, with 98% customer retention and an NPS of 78. What the ClearBox scores reflect is a platform that was designed from the start for the way distributed and frontline organizations actually work: multiple sites, diverse employee populations, workers who don't have a corporate email address, managers who need real-time visibility without logging into three separate systems. The 4.5 in [Mobile and Frontline Support](https://www.mangoapps.com/mobile) is not a coincidence. Neither is the 4.5 in Community and Engagement. These are the categories that matter most to organizations where most of the workforce is not sitting at a desk, and they are the categories where MangoApps has invested the most. The AI Innovator recognition reflects a deliberate choice MangoApps made: AI should live inside the workflows employees are already running, not in a separate module someone has to go find. The [AI assistants](https://www.mangoapps.com/solutions/employee-app#ai), the [federated search](https://www.mangoapps.com/solutions/knowledge-management), the writing tools, the translation across 50+ languages — all of it runs inside OneMango, the app employees open every day. ## Get the Full Report The 2026 *Intranet and Employee Experience Platforms* report from ClearBox is available for download on the MangoApps website. It covers 33 platforms, evaluates each across eight real-world scenarios, and is one of the most referenced independent resources in the intranet buying process. [Download the ClearBox 2026 Report](https://www.mangoapps.com/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) *ClearBox Consulting independently assessed MangoApps as part of the 2026 Intranet and Employee Experience Platforms report. All quotes attributed to ClearBox Consulting.* --- # How frontline signals get missed and why comms must be treated as core **Author:** MangoApps Team **Published:** 2026-05-05 **Category:** mango-scoop Explore why workers spot issues systems miss, plus a look at communication failures and the frontline tax. Hand-picked stories from MangoApps this week. ## What Frontline Workers Know That Workforce Systems Miss ![What Frontline Workers Know That Workforce Systems Miss](https://mango-cdn.b-cdn.net/images/blog-thumbnails/blog_487_20260503_225719.png) A field supervisor walks a construction site every morning. She spots things — a tool stored wrong, a near-miss that didn't quite make it into the incident log, a pattern of the same pump failing... [Read the full story →](https://www.mangoapps.com/articles/what-frontline-workers-know-that-workforce-systems-miss) --- ### More to read #### Why Communication Fails Before Companies Do: What Business History Tells Us About Treating Communication as Overhead When internal communication is underfunded, companies miss critical signals. These five business failures show why transmission matters. [Read more →](https://www.mangoapps.com/articles/why-communication-fails-before-companies-do) #### MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation MangoApps was evaluated in The Forrester Wave™: Intranet Platforms, Q2 2026, reinforcing its leadership in unified workforce solutions. [Read more →](https://www.mangoapps.com/articles/mangoapps-2026-forrester-wave-intranet-platforms) #### Why the Employee App Market Is Really a Consolidation Problem Most employee app buyers want less tool sprawl, not another app. Unified platforms win by combining communication, tasks, HR, and AI. [Read more →](https://www.mangoapps.com/articles/employee-app-market-consolidation-problem) #### AI Won’t Replace the Frontline—It Will Decide Who Wins AI’s real impact is not job replacement—it’s whether frontline teams get the tools, knowledge, and access to keep up. [Read more →](https://www.mangoapps.com/articles/ai-wont-replace-the-frontline-it-will-decide-who-wins) --- ### From the Wire > **Anup Kejriwal** · General > **No, companies won’t stop buying software** Companies are not going to stop buying software and start building everything themselves. That idea is not grounded in history. We can all cook at ho... > > [Read on Frontline Wire →](https://www.mangoapps.com/frontline-wire/no-companies-won-t-stop-buying-software-co) > **Vishwa Malhotra** · Industry > # The Frontline Tax: What You're Paying to Ignore 80% of Your Workforce Eighty percent of the global workforce is deskless. They run your stores, floors, wards and routes. And lot of them are st... > > [Read on Frontline Wire →](https://www.mangoapps.com/frontline-wire/the-frontline-tax-what-you-re-paying-to-ignore) > **Anup Kejriwal** · General > There is a lot of discussion right now about the coming “SaaS collapse.” AI is one of the most important technology shifts we will see in our lifetime. It will reshape software, disrupt categori... > > [Read on Frontline Wire →](https://www.mangoapps.com/frontline-wire/there-is-a-lot-of-discussion-right-now-about-the-c) --- ### What's New **General** — [Product Update - May 04, 2026](https://www.mangoapps.com/changelog/2966) * **[Supply Order Approval & Vendor PO Dispatch](https://www.mangoapps.com/solutions/workforce-management)** — Managers can now approve or reject supply orders directly from the... **General** — [Product Update - May 03, 2026](https://www.mangoapps.com/changelog/2965) * **[In-Browser Media Capture](https://www.mangoapps.com/directory/app/forms)** — Users can now capture photos, videos, and audio directly within forms, safety reports, and insp... --- # Why the Employee App Market Is Really a Consolidation Problem **Author:** MangoApps Team **Published:** 2026-05-04 **Category:** employee-app Most employee app buyers want less tool sprawl, not another app. Unified platforms win by combining communication, tasks, HR, and AI. ## Why the “Employee App” Market Is Really a Consolidation Problem ### Opening Thesis Most companies searching for an “employee app” are not really looking for another app. They are looking for a way to stop forcing frontline workers, managers, HR, and IT to move across disconnected tools just to get basic work done. That matters because **over 80% of the global workforce is deskless**, yet many employee experience stacks still act as if everyone works at a laptop with company email. The real market divide is not between “good” and “bad” employee apps. It is between **point solutions**—tools that handle one narrow job—and **unified platforms** that bring communication, scheduling, tasks, HR, and AI into one place. [MangoApps](https://www.mangoapps.com) is built around that second model. ### The Problem Nobody Talks About The employee app category is crowded with vendors making the same promise: centralize communication, improve engagement, and reach frontline workers on mobile. That sounds compelling until you look at how most solutions are actually deployed. Many are still narrow communication layers, legacy intranet extensions, or mobile wrappers around a single use case. In practice, that creates a structural problem. If the app only handles announcements, employees still need separate systems for schedules, tasks, HR self-service, knowledge, and compliance. If it only handles knowledge, managers still need another tool for workforce coordination. If it only handles messaging, adoption may rise while operational friction stays the same. The market data points to the same conclusion. The battleground is no longer basic mobile access. It is **operational reach**—in simple terms, how far the app extends into the actual work employees need to do. Buyers want proof that an employee app can improve adoption, reduce tool sprawl, and support real work across shifts and locations. That is why a platform like MangoApps emphasizes not just communication, but also workflow execution, employee services, and mobile access to work tasks. ### What the Data Actually Shows #### 1) Mobile access is necessary, but not sufficient A mobile employee app only matters if it reaches the people who are hardest to reach. MangoApps cites that **81% of American phone owners have a smartphone**, which explains why mobile-first delivery has become the baseline expectation rather than a differentiator. But smartphone access alone does not solve the adoption problem. The stronger signal is what employees can do once they are inside the app. On the [Mobile Employee App](https://www.mangoapps.com/mobile) page, MangoApps positions a single branded experience for news, schedules, HR tools, team communication, and company resources in **two taps or less**. It also supports **offline access**, **no corporate email required**, and mobile features such as private messages, group chats, shift scheduling, shift swaps, open shift pickup, time tracking, and payroll access. That breadth matters because the cost of disconnection is real. MangoApps cites **$4,400 to $15,000** as the average cost of replacing a frontline employee. In other words, an employee app is not just a communications channel. It is part of the retention infrastructure. #### 2) Adoption improves when the app becomes the work hub, not the newsfeed A common mistake is treating the employee app as a prettier broadcast channel. That approach may improve reach, but it rarely changes behavior. The better model is a **digital work hub**—a central place where employees can read updates and complete tasks without switching systems. MangoApps’ [App Store](https://www.mangoapps.com/apps) makes that case directly. It offers **25+ ready-to-use apps** spanning HR, scheduling, communications, safety, and workflow automation, all sharing the same employee data, permissions, and user profiles. That is a fundamentally different architecture from stitching together separate point solutions with middleware. The practical result is less friction for employees and less administrative overhead for IT. MangoApps also says new apps can be turned on demand without new vendor contracts, and custom business apps can be built in minutes without coding. That matters in distributed environments where operational needs change faster than software procurement cycles. The webinar [Leveraging An Employee SuperApp To Improve Operational Excellence & Engagement](https://www.mangoapps.com/resources/leveraging-an-employee-superapp-to-improve-operational-excellence-engagement) reinforces the same point: a centralized digital work hub can improve productivity, employee reach, and engagement for frontline teams. One cited customer example references a culture shift across **27K+ employees**, which is the kind of scale that only becomes possible when the app is more than a messaging layer. #### 3) Trust and deployment credibility are part of the product Employee app buyers do not just evaluate features. They evaluate whether the platform will actually go live, get adopted, and stay secure. The published credibility metrics are unusually strong for this category: **NPS of 78**, **98% customer retention**, **1M+ employees served**, and **15+ years** of product development. That matters because employee app projects often fail for non-product reasons: poor rollout planning, weak governance, and low adoption after launch. The [Employee App Best Practices](https://www.mangoapps.com/resources/employee-app-best-practices) guide focuses on content strategy, mobile adoption, launch-day planning, and engagement tactics for exactly that reason. The resource is also available as a **1 min read** download with no email required, which signals a practical, adoption-oriented approach rather than a gated thought-leadership pitch. The lesson is simple: in this category, trust is not a soft metric. It is a deployment requirement. ### How to Evaluate a Unified Platform If you are comparing employee app vendors, use a scorecard instead of a feature checklist. The goal is to find a platform that reduces tool sprawl, not one that adds another layer on top of it. Score each vendor on the seven criteria below before you shortlist anything. Use this scorecard to assign each vendor a score of 1–5 on each criterion before you make a shortlist. A platform that scores 4 or 5 on all seven is a genuine consolidation candidate. A platform that scores well on only two or three is a point solution, regardless of how it is marketed. **1. Breadth of integrated modules** *What to ask:* Does the platform cover communication, scheduling, HR self-service, tasks, knowledge, and workflow automation in one environment—or does it require third-party integrations to fill gaps? *Scoring signal:* A consolidation platform should offer at minimum: messaging, [Broadcast](/directory/app/broadcast), [Shifts & Scheduling](/directory/app/shifts-scheduling), [Time & Attendance](/directory/app/time-attendance), HR self-service, and document/knowledge management under one login. MangoApps' [App Store](https://www.mangoapps.com/apps) offers **25+ ready-to-use apps** spanning HR, scheduling, communications, safety, and workflow automation—all sharing the same employee data, permissions, and user profiles. If a vendor cannot cover communication plus scheduling plus HR natively, it is not a consolidation platform. It is a point solution with an API. **2. Proven deployment track record** *What to ask:* How long does a typical rollout take? What support is included? Can the vendor show adoption data at 1,000+ employees? *Scoring signal:* Look for evidence that the platform has been adopted at scale and stayed in use. MangoApps cites **NPS of 78**, **98% customer retention**, **1M+ employees served**, and **15+ years** of product development. Industry benchmarks suggest that well-structured deployments can reach **90% frontline adoption within the first six months**. Ask vendors to show you a rollout timeline, not just a feature demo. The real risk in this category is not feature gaps—it is rollout failure. **3. Offline and no-email access for frontline teams** *What to ask:* Can employees use the platform without corporate email? Does it work in low-connectivity environments? *Scoring signal:* A unified platform should work for employees who are not at a desk and may not have corporate email. MangoApps highlights **offline access** and **no corporate email required** as baseline capabilities. That is a practical requirement for frontline adoption, not a nice-to-have. If the platform cannot support shift-based workers in low-connectivity environments, it will not consolidate much of anything—it will simply replicate the same access gap that point solutions already create. **4. Measurable adoption and operational outcomes** *What to ask:* Can the vendor show whether employees actually receive messages, complete tasks, and stay connected? What retention and engagement metrics can they provide? *Scoring signal:* Buyers should ask for numbers, not promises. Only **25% of employees feel appreciated and engaged at work**, and **34% plan to look for a new job in 2026**, with an additional **22% considering it**. Those numbers reflect what happens when platforms fail to connect communication to work execution. On the positive side, organizations that switched to a unified omnichannel platform saw **79% of employees receive critical leadership messages they had not received before**. Ask vendors for retention rate, employee NPS, and documented examples of faster task completion or reduced missed updates. MangoApps cites **$4,400 to $15,000** as the average cost of replacing a frontline employee—which is why adoption metrics are a financial issue, not just an HR metric. **5. Custom app speed and no-code extensibility** *What to ask:* How quickly can the platform be configured for a new operational workflow? Does it require developer resources or vendor professional services to extend? *Scoring signal:* Operational needs in distributed workforces change faster than software procurement cycles. A consolidation platform should allow new apps or workflows to be activated without new vendor contracts and without coding. MangoApps states that custom business apps can be built in minutes without coding. Industry data suggests that frontline platform deployments at scale can now be stood up in minutes rather than months when built on an AI-native architecture. If a vendor requires a professional services engagement every time you need a new workflow, the platform will create its own form of tool sprawl over time. **6. Omnichannel content operations** *What to ask:* Can communicators create content once and distribute it across mobile, email, intranet, and digital signage without manual duplication? Does the platform support a "create once, publish everywhere" workflow? *Scoring signal:* Tool sprawl is not just an employee problem—it is a communicator problem. When content teams must manually copy-paste updates across channels, the operational cost compounds quickly. Omnichannel communication platforms can save enterprise teams a minimum of **2,700 hours per year** by eliminating manual duplication across channels. A true consolidation platform should support a single content workflow that reaches employees wherever they are—mobile app, desktop intranet, email digest, or digital signage—without requiring separate publishing steps for each channel. **7. Total cost of ownership and tool count reduction** *What to ask:* How many existing tools does this platform replace? What is the all-in cost—licenses, implementation, ongoing support—compared to the stack it displaces? *Scoring signal:* The financial case for consolidation is not just about license savings. It includes the cost of workforce attrition that disconnected tools accelerate. U.S. workforce attrition is estimated to cost between **$1.3 trillion and $5.1 trillion in 2026**. Payroll automation integrated directly into a workforce platform can cut payroll processing time by up to **50%**—a hard ROI metric that pure-play communication apps cannot offer. Ask vendors to map which tools in your current stack their platform replaces, then calculate the net cost difference including implementation and support. If the vendor cannot name at least three to five tools their platform displaces, it is not a consolidation platform. ### The Contrarian Insight The industry keeps framing the employee app as a communications problem. That is too small. The data shows that the real buying motion is about **platform consolidation**. Buyers are not just asking, “Can employees read updates on mobile?” They are asking, “Can we replace multiple tools, reduce admin burden, improve frontline adoption, and connect communication to actual work?” That is why the strongest solutions combine messaging, scheduling, HR self-service, task management, and AI in one environment. This is also where many narrow platforms hit a ceiling. A communication-only app can improve reach. A knowledge-only app can improve findability. A workflow-only app can improve execution. But if employees still need three or four systems to finish a shift, the organization has not solved the problem. It has only moved the friction around. ### What Actually Works: A Unified Approach A unified employee app works because it reduces the number of decisions employees have to make before they can act. Instead of opening one app for announcements, another for schedules, another for HR, and another for tasks, they enter one branded experience that already knows who they are, what they need, and what they are allowed to see. That is the logic behind MangoApps’ mobile-first model: one app, one login, one data layer, and one adoption curve. It is also why the platform can support both deskless and desk-based employees without splitting the experience into separate systems. The same platform that delivers mobile communication also supports workflow automation, employee services, and enterprise AI. For organizations evaluating the keyword “employee app,” the real question is not whether the app is mobile. It is whether the app can become the operational center of the workforce. If it cannot, it is just another tool to manage. ### Next Steps If you are evaluating an employee app, start by mapping how many systems your employees still need after they open it. Then compare that to a unified platform like [MangoApps](https://www.mangoapps.com) that brings communication, scheduling, HR, tasks, and AI into one mobile experience. If you need a practical next step, use the criteria above to score vendors on module breadth, deployment credibility, offline access, and measurable adoption outcomes before you shortlist anything. --- # What Frontline Workers Know That Workforce Systems Miss **Author:** MangoApps Team **Published:** 2026-05-03 **Category:** enterprise-ai A field supervisor walks a construction site every morning. She spots things — a tool stored wrong, a near-miss that didn't quite make it into the incident log, a pattern of the same pump failing... # What Frontline Workers Know That Workforce Systems Miss A field supervisor walks a construction site every morning. She spots things — a tool stored wrong, a near-miss that didn't quite make it into the incident log, a pattern of the same pump failing every three weeks. She knows things. The question is whether any of that knowledge makes it into the systems her company uses to make decisions. Most of the time, it doesn't. Not because she isn't trying. She fills out the form, ticks the boxes, maybe adds a text note in a field that holds 200 characters. But the photo she would have taken, the thirty-second voice note she would have left, the model that would have flagged a bearing failure in the image — none of that existed in most operational systems. So the knowledge stayed in her head, until something went wrong or she moved on. That gap — between what frontline workers observe and what operational systems actually capture — has been one of the most persistent structural problems in workforce management. This week, a set of releases started closing it in ways that feel genuinely different from what has come before. --- ## Evidence Capture That Doesn't Create Extra Work The traditional approach to field evidence was a workaround: take the photo on your phone, send it in a separate email or upload it to a different system, then describe what you saw in the form you were actually required to fill out. The evidence and the record were always in different places. Two releases this week address this at the root. [Media Capture with AI Analysis](https://www.mangoapps.com/changelog/2964) lets field and operations teams attach photos, videos, and voice memos directly to inspections, work orders, tasks, and incidents — without switching apps. But the more important part is what happens next: AI automatically transcribes voice memos, analyzes images, strips EXIF location data for privacy, and generates shareable watermarked links. The submission you receive isn't a photo attachment anymore. It's a photo with a machine-readable description, a voice note with a text transcript, a record that can be searched and analyzed like text even though the original evidence was visual or audio. [In-Browser Media Capture for Forms](https://www.mangoapps.com/changelog/2965) extends this to the forms layer — so safety reports, inspection forms, and other structured data collection now support direct camera and microphone access from within the form itself. No app-switching required. A field worker on a shared tablet can capture a safety observation with a photo and a voice comment, and it submits as part of the form record, not as a separate attachment to be reconciled later. This matters because friction in evidence capture is what causes it not to happen. When submitting a photo means switching apps, the photo doesn't get submitted. When a voice note means calling someone or sending a separate message, the note stays mental. Removing the friction doesn't just make the process faster — it changes what gets submitted at all. And the difference between a text description of a failing pump and a photo of a failing pump with an AI-generated analysis is the difference between a vague work order and a repair with actual context. --- ## When Information Moves Without Being Pushed Capturing richer evidence at the point of work is only valuable if that evidence connects to something. Two other releases this week address the routing problem — how information captured in one context reaches the right person or system without someone manually moving it. [AI-Powered Service Desk Routing](https://www.mangoapps.com/changelog/2960) changes how service desk tickets get assigned. Instead of routing rules that match on keywords or specific field values, tickets can now be matched by plain-English intent descriptions evaluated by an AI model. A ticket that says "my access badge doesn't work when I come in through the loading dock entrance after my shift" doesn't contain the words "physical security" or "facilities" — but it means physical security and facilities. Keyword-based routing misses this. Intent-based routing doesn't. [Auto-Grant Skills from Training Completion](https://www.mangoapps.com/changelog/2961) addresses a different version of the same problem. An employee finishes a forklift certification course. That completion record exists in the training system. Her skills profile in HR shows no forklift certification. Both things are true simultaneously because the information doesn't travel between systems without manual entry. This release closes that loop: when a course completion happens, the matching skill, certification date, proficiency level, and expiration are automatically applied to the employee's profile. No one has to copy anything. The information moves because the work was done, not because someone remembered to update a second system. These two releases represent something worth naming: the shift from systems that store information to systems that route it. The difference is whether information requires a human to move it from where it was created to where it needs to be — or whether the system understands enough context to move it there itself. Most workforce systems today are still in the first category. --- ## Context-Aware Intelligence at the Moment of Need Even when information is captured richly and routed correctly, it's only useful if the person asking a question can get an answer grounded in their specific situation. [Ask AI Page-Aware Routing](https://www.mangoapps.com/changelog/2958) is a quiet but significant change. When an employee asks Ask AI a question, the system now detects the context of the page they're on and routes to the appropriate specialized agent automatically. An employee viewing a shift schedule who asks "what happens if I miss a shift?" gets an answer grounded in scheduling policy. An employee viewing a service desk ticket who asks the same question gets routing toward incident handling. The same question, asked in different operational contexts, produces different answers. This is what it means for AI to be useful in operational environments — not a generic assistant, but one that understands where you are. [AI Template Refinement](https://www.mangoapps.com/changelog/2965) brings a similar context-awareness to the configuration layer. Platform administrators can now iterate on system templates through a conversational AI interface, with live preview updating after each exchange. Instead of editing raw template configuration and re-rendering to see changes, the feedback loop is a conversation: "make the safety section required," "add a field for equipment serial number," "move supervisor sign-off to the end." The intelligence isn't just in the template — it's in the tooling that shapes what templates exist in the first place. --- ## What the Thread Connects To The common thread across all of these releases is deceptively simple: operational work generates information, and for most of the last decade, that information has been collected but not fully used. A safety inspection with a photo attachment is not the same as a safety inspection with an AI-analyzed image, a searchable transcript, and a record that automatically routes to the right team. A training completion record is not the same as an updated skills profile immediately visible in workforce planning. A service desk ticket is not the same as an assignment that reached the right team because the system understood what the employee meant, not just the words they used. The releases MangoApps shipped this week aren't individually the largest features on the roadmap. But the direction they represent — intelligence embedded in operational workflows, at the point where information is created — is one of the most consequential directions in workforce management software right now. Frontline workers have always known things their systems couldn't hear. The question is how much of it you're actually capturing. --- # Cloud Productivity Apps Are Hurting Employee Productivity **Author:** MangoApps Team **Published:** 2026-04-30 **Category:** workplace-productivity Too many disconnected apps create friction, waste time, and hurt retention. A unified work platform can restore productivity. ## Cloud-Based Productivity Apps Are Making Your Employees Less Productive The average enterprise employee switches between 9 to 10 different applications to complete a single workday. Every one of those switches is a cloud-based productivity app someone bought to solve a specific problem. The cruel irony: the more tools you add, the more mental overhead you create. Per McKinsey research, knowledge workers spend nearly 20% of their time just searching for information that already exists somewhere in their stack. The productivity problem isn't a shortage of apps. It's an excess of them. ### The Problem Nobody Talks About The prevailing assumption in enterprise IT is that cloud-based productivity is an assembly problem. Pick the best communication tool, the best task manager, the best file storage, the best scheduling app, stitch them together with integrations, and you have a productive workforce. This logic is intuitive. It is also wrong in a specific, measurable way. Connecting separate tools through integrations is not the same as having one system where all your data lives together. When your task manager doesn't know who's on shift, when your communication tool doesn't surface the relevant document, when your scheduling app can't trigger a compliance workflow — you haven't built a productive stack. You've built a system where employees waste time every hour just coordinating between tools. Communication-only platforms and frontline messaging tools have made this worse. They solve one piece of the problem without solving the whole thing. A shift worker gets a push notification about a policy change — but can't access the updated procedure, can't confirm they've read it, and can't ask a question without switching to a different app. Legacy intranet platforms, meanwhile, were built for desk workers with a browser and a company email address. That leaves the 80% of the global workforce in frontline and deskless roles with a mobile experience that was clearly an afterthought. Neither approach is a true productivity platform. Both are partial fixes. ### What the Data Actually Shows #### The Hidden Cost of Tool Fragmentation The productivity loss from using too many disconnected tools shows up most clearly in IT and knowledge management. When organizations consolidate institutional knowledge into structured wikis — rather than letting it scatter across email threads, chat channels, and shared drives — IT staff consistently recover 10–12 hours per week. That's a quarter of a full-time employee's week, recovered simply by giving information one consistent home. The impact compounds when you factor in frontline workers. Per our data, 79% of hourly employees say scheduling is the single most important factor in whether they stay at a job. Yet most cloud productivity stacks treat scheduling as a standalone app that doesn't connect to communications, task assignments, or compliance workflows. The result: the workflow most likely to drive retention is also the most disconnected one. The consequences are concrete — even one scheduling disruption every two weeks increases an employee's likelihood of leaving by 20%. Disconnected tools don't just frustrate employees. They drive turnover. #### Why Integrations Don't Solve the Problem The standard counterargument to consolidation is that integrations solve fragmentation. They don't — they shift it. Every integration between separate tools requires maintenance, creates a potential failure point, and typically requires custom development to surface data where employees actually work. Organizations end up paying in IT hours, vendor contracts, and adoption friction that never fully resolves. Our [Microsoft integration](https://www.mangoapps.com/integrations/microsoft) illustrates what a genuine integration looks like. We connect with 10+ Microsoft 365 touchpoints — Active Directory, SharePoint, OneDrive, Teams, Outlook, Power BI, Intune — at zero additional license cost. Employees can open, edit, and co-author Word, Excel, and PowerPoint files natively inside the platform. Search surfaces SharePoint and OneDrive content alongside everything else. MangoApps content is accessible and interactive directly inside Microsoft Teams. This isn't a patched connection between two separate tools. It's a single workspace that extends what Microsoft already provides. #### Frontline Workers Need More Than a Messaging App The cloud productivity conversation has historically focused on desk workers. That's a significant blind spot — and it's where communication-only platforms fall short. Sending a message to a frontline worker is not the same as giving them a productive workday. For a shift-based employee, productivity means knowing their schedule, accessing their tasks, completing required training, submitting a form, and escalating an issue. All without switching apps. All without a company email address. All on a mobile device they already own. Our [App Store](https://www.mangoapps.com/apps) addresses this directly: 25+ ready-to-use apps spanning HR, scheduling, communications, safety, and workflow automation — all sharing the same employee data, permissions, and user profiles. A new app activates on demand without a new vendor contract or an IT project. The [work management layer](https://www.mangoapps.com/use-cases/work-management) brings task tracking, project milestones, embedded messaging, and no-code approvals into the same environment where employees already communicate. For frontline workers, that means one login, one app, one place where their entire workday lives. ### The Contrarian Insight: AI Can't Fix a Broken Foundation The industry has convinced itself that AI will solve the fragmentation problem — that a smart enough assistant can stitch together a broken stack and surface the right information at the right time. This is precisely where communication-only platforms and point-solution providers hit a ceiling. Their AI story is a layer placed on top of a fragmented foundation. If your task data lives in one system, your HR records in another, your communications in a third, and your scheduling in a fourth, an AI assistant connected to any one of those systems is working with an incomplete picture. It can't answer "who's available to cover this shift and has completed the required safety training" because that question spans three tools that don't share data. Useful AI requires all your data to be organized and connected in one place first. Our Enterprise AI Hub is embedded into the platform — not added on top of it — which means every AI assistant draws from the same governed, permission-aware data that powers search, communications, and workflows. The AI is useful because the underlying data is organized, connected, and complete. That's a structural advantage no integration between separate tools can replicate. ### What Actually Works: A Unified Platform Organizations that have moved from a fragmented cloud productivity stack to a unified platform consistently report the same outcome. The productivity gains don't come from any single feature. They come from eliminating the time employees spend switching between tools across the entire workday. When communications, task management, file access, scheduling, compliance tracking, and AI assistance all live in one environment, employees stop spending mental energy navigating between apps and start spending it on actual work. With 1 million+ users on our platform and an NPS of 78 — well above the enterprise software average — the consolidation case isn't theoretical. Our [file management approach](https://www.mangoapps.com/articles/mangoapps-file-management) alone demonstrates how consolidating document storage, search, and access control inside a single platform reduces the distraction and delay that fragmented storage creates. Across deployments, 90% adoption within 90 days is the norm — because when employees have one place that covers their full workday, they use it. If your current cloud productivity stack requires more than one login to complete a routine task, you're not running a productivity platform. You're running a coordination problem. The question worth asking isn't "which app should we add next?" It's "how many can we retire?" [MangoApps](https://www.mangoapps.com) was built to answer that second question. --- # Why Communication Fails Before Companies Do: What Business History Tells Us About Treating Communication as Overhead **Author:** Andy Tolton **Published:** 2026-04-30 **Category:** industry-insights When internal communication is underfunded, companies miss critical signals. These five business failures show why transmission matters. If you're an internal communications leader right now, there's a reasonable chance you've had some version of this conversation recently: the budget got tightened, the headcount got cut, or someone in finance decided that the company's existing stack, SharePoint, ServiceNow, Workday, or whatever enterprise system already has a seat at the table, is "good enough" for employee communication. Why pay for a dedicated platform when the intranet already technically exists? It's a familiar pressure. In times of economic uncertainty, communications is often one of the first places organizations look to cut or consolidate. It's treated as a support function, not a strategic one. And so comms teams end up trying to reach a workforce of thousands through tools built for document storage, IT ticketing, or HR workflows. The information gets published somewhere. Whether it reaches anyone is a different question. We hear this directly, and often. Internal communications leaders across industries consistently describe being under-resourced, under-funded, and perpetually making the case that their function deserves real investment. Many run their entire operation on tools their organizations never intended for communication in the first place. The result is that reaching frontline workers, driving alignment around strategy, and getting critical information to the people who need it all becomes harder, slower, and more fragile than it should be. This piece is a response to that pattern. Because the assumption that communication can be deprioritized, consolidated into a secondary tool, or treated as a budget line to trim in a difficult quarter, isn't just organizationally frustrating. It's historically dangerous. Every time an organization makes that bet, it's betting that the information people need to do their jobs will find its way to them anyway, through hallway conversations, email chains, manager updates, intuition. It's betting that communication is overhead on top of the real work, rather than the substrate that makes the real work possible. Business history keeps showing us what happens when that bet goes wrong. The pattern is remarkably consistent. The information almost always exists somewhere in the company. It just doesn't reach the people who need it, in the form they need it, in time to act on it. That's not a knowledge problem. It's a transmission problem. And it has quietly ended more companies than any market downturn or disruptive competitor on its own. Here's what that looks like across five of the most documented cases in modern business history. ## Kodak invented the thing that killed it In 1975, a Kodak engineer named [Steven Sasson built the world's first digital camera](https://petapixel.com/how-steve-sasson-invented-the-digital-camera/). It was the size of a toaster, took 23 seconds to capture a black-and-white image, and stored it on cassette tape. It was also, unmistakably, the future. When Sasson demonstrated it to leadership, the reaction he described was one of "curiosity and skepticism." The camera was [patented but never put into production](https://www.invent.org/inductees/steven-sasson). Digital threatened the film business, which was the most profitable thing Kodak had ever done. Kodak's marketing department, as later reporting confirmed, was not interested in the prototypes. The information existed inside the company. The technology existed inside the company. The strategic implications were obvious to the people who built it. None of that knowledge was allowed to travel between the labs and the strategy meetings. It got walled off because it was inconvenient. By the time Kodak's leadership was ready to communicate honestly across functions about what digital meant, the market had moved past them. Kodak filed for bankruptcy in 2012. Kodak didn't fail because it didn't know. It failed because what it knew couldn't move. ## Nokia knew it was losing. Nobody would say it out loud. A [2015 study by researchers Timo Vuori and Quy Huy, published through INSEAD](https://knowledge.insead.edu/strategy/who-killed-nokia-nokia-did), looked at why Nokia, the dominant mobile phone maker on Earth, lost the smartphone race so completely. The study involved 76 interviews with Nokia's top and middle managers, engineers, and external experts. The answer wasn't that Nokia's engineers couldn't see what was happening. They could. By the late 2000s, plenty of people inside the company understood that Symbian, Nokia's operating system, couldn't compete with iOS or Android. What the researchers found was a culture where bad news didn't travel up. Middle managers feared the reaction of senior leadership and softened what they were hearing from below. Senior leaders, in turn, communicated unrealistic expectations downward and assumed silence meant things were on track. The INSEAD researchers concluded that ["a culture of fear stifled communication and innovation, rendering the company unprepared when new smartphone entrants reshaped the sector."](https://knowledge.insead.edu/strategy/nokias-reinvention-was-emotionally-driven) Engineers who knew the truth told it to each other in quiet conversations. They did not tell it to the people making the decisions. Nokia's market capitalization fell from roughly $250 billion at its peak to a fraction of that. Microsoft eventually bought the phone business and wrote most of it off within two years. The technology was salvageable. The communication culture wasn't. ## Blockbuster passed on Netflix for $50 million In early 2000, [Reed Hastings and Marc Randolph flew to Dallas to offer Blockbuster the chance to buy Netflix for $50 million](https://www.marketplace.org/story/2020/09/08/ceo-reed-hastings-on-how-netflix-beat-blockbuster). Blockbuster, then a $5 billion company with thousands of stores, declined. The widely-reported version of the story focuses on the meeting itself. But the more instructive part is what happened inside Blockbuster afterward. Internal voices, including the company's own digital strategy team, repeatedly pushed for a more aggressive online and subscription-based response. John Antioco, the CEO at the time, eventually launched Blockbuster Online and dropped late fees, which were two of the most important strategic moves the company ever made. He was forced out partly because those moves conflicted with the financial expectations of activist investors, whose picture of the digital threat was filtered through executives who wanted the disruption to be smaller than it was. The signals were inside the company. The analytical capability was inside the company. Customer behavior data was inside the company. The communication infrastructure to make those signals impossible to ignore at the board level was not. [Blockbuster filed for bankruptcy in 2010](https://fortune.com/2023/04/14/netflix-cofounder-marc-randolph-recalls-blockbuster-rejecting-chance-to-buy-it/). A $50 million decision became a multi-billion-dollar one because the right information lost the internal argument. ## Sears had the digital playbook a decade before Amazon In 1984, Sears was one of the largest retailers in the United States. That same year, it [launched a joint venture called Trintex with IBM and CBS](https://en.wikipedia.org/wiki/Prodigy_(online_service)), later renamed Prodigy, an early online service that offered home shopping, news, banking, and email. Sears was, in 1984, in a better position to define digital commerce than almost any company on the planet. Inside Sears, the people working on Prodigy understood what it could become. Inside Sears, the people running stores and catalogs treated it as a side project that risked cannibalizing the core business. The two groups did not communicate effectively about strategy, capital allocation, or customer behavior. IBM and Sears ultimately [invested more than $1 billion in Prodigy](https://www.referenceforbusiness.com/history2/40/Prodigy-Communications-Corporation.html) before selling it off in 1996 at a fraction of that. By the time Amazon launched in 1994, Sears had already let its information advantage evaporate, not because the world changed too fast, but because its own divisions couldn't share what they were learning. [Sears filed for bankruptcy in 2018](https://en.wikipedia.org/wiki/Prodigy_(online_service)). Amazon's market cap crossed $2 trillion. ## BlackBerry's engineers knew. So did its CEOs. Separately. When the iPhone launched in 2007, BlackBerry was the dominant enterprise smartphone. Its co-CEOs [publicly dismissed the iPhone's significance](https://9to5mac.com/2015/06/10/ceo-blackberry-iphone/). Co-CEO Jim Balsillie reportedly told co-founder Mike Lazaridis, "It's okay, we'll be fine." They believed BlackBerry's business customers would never abandon a physical keyboard for a glass screen, and that the iPhone wasn't secure enough for enterprise use. What's less visible in that narrative is what was happening internally. RIM's own engineers were [actively building what they called the "A.K."](https://gizmodo.com/rim-engineers-call-touchscreen-blackberry-apple-killer-384440), an internal code name for "Apple Killer," a touchscreen BlackBerry. The engineers saw the threat. Leadership had a different narrative for the public, for the board, and for themselves. The two realities never reconciled in time to drive a coherent product response. The result was the BlackBerry Storm, a rushed touchscreen device that was [so buggy it had, by one account, a nearly 100% return rate](https://9to5mac.com/2015/06/10/ceo-blackberry-iphone/). The platform war was effectively over before the company's internal picture of reality matched what its engineers had been saying for two years. The company's hardware business ended within a decade of being on top of the world. ## The pattern these cases share These five stories span different decades, different industries, and vastly different competitive contexts. What they have in common is not bad strategy or bad people. In each case: - The relevant information existed somewhere inside the organization - The organizational structure, culture, or incentives prevented it from reaching decision-makers intact - By the time the decision-makers had an accurate picture, the window had closed This is the pattern. Not ignorance. Transmission failure. ## What this looks like at everyday scale Most companies will never have a Kodak moment. But the same dynamic plays out, scaled down, in nearly every organization every day. A frontline manager spots a customer behavior shift that never reaches merchandising. A field engineer flags a defect pattern that never reaches design. A salesperson loses three consecutive deals to the same competitor objection that never reaches product marketing. A new policy rolls out without the people enforcing it understanding the reason behind it. A new hire spends their first week searching for documents that exist somewhere but can't be found anywhere they look. None of these are dramatic. None of them make the case study. But they compound. [McKinsey's research](https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy) found that knowledge workers spend nearly 20% of the workweek searching for internal information or tracking down colleagues who can help. That's one full day a week, per employee, lost to information that exists but can't be reached. According to [Gallup's 2026 State of the Global Workplace report](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx), only 20% of employees globally are engaged at work, a five-year low, and one of the strongest predictors of engagement is whether people feel informed and connected to their organization's purpose. Among frontline workers, the 80% of the global workforce that doesn't sit at a desk, only 22% feel their work is important to the company vision. That isn't a disposition problem. It's a transmission problem. The cost isn't hypothetical. Gallup estimates global disengagement now costs the world economy $10 trillion annually in lost productivity. ## So what do you actually do about it? Identifying the pattern is useful. Knowing what to do about it is more useful. Here's how organizations that take communication seriously actually operate differently. ### Treat information access as infrastructure, not administration The companies that avoided the Kodak and Nokia fate tend to share a structural trait: they design their organizations so that signals from the edges reach the center quickly and intact. That means more than having open-door policies. It means building actual systems for information to flow. In practical terms, this looks like: - **[Unified communication channels](https://www.mangoapps.com/solutions/modern-intranet)** that reach every employee, including those without a desk or a company email, so that when something important needs to be said, it actually reaches everyone it needs to reach - **[Searchable, centralized knowledge](https://www.mangoapps.com/solutions/knowledge-management)** so that when someone needs to know something, they can find it without asking three people and waiting two days - **[Feedback loops](https://www.mangoapps.com/solutions/employee-engagement)** that make it structurally easy for frontline teams to surface what they're seeing, and structurally visible when that input gets acted on The goal isn't more communication. It's more signal, less noise, and less distance between where information originates and where decisions get made. ### Measure what you can, name what you can't One reason communication gets cut before other functions is that its value is hard to quantify in advance. [But it's not impossible to measure](https://www.mangoapps.com/analytics-insights). Organizations can track and report on: - **Reach and readership on internal communications:** who actually received and opened a message, and how many acknowledged it - **Information-search time:** how long employees spend looking for things they need to do their jobs, and where the biggest gaps are - **Adoption rates after policy changes or process rollouts:** the gap between "we communicated this" and "people actually understood and applied it" is usually where the cost lives - **Engagement scores over time,** segmented by team and location, with communication frequency and quality as an input variable The $10 trillion Gallup figure and McKinsey's 20% time-loss estimate are both useful for executive conversations because they put a dollar frame on what is normally treated as a soft concern. If a company has 5,000 employees earning an average of $60,000 per year, McKinsey's estimate implies roughly $6 million in annual productivity lost to information-search alone. That's a real number, and it's the kind of number that makes the budget case for communication infrastructure. ### Build the business case in terms leaders actually respond to Communications professionals often make the mistake of arguing for their function in terms of outputs: newsletters sent, announcements posted, videos produced. Executives don't fund outputs. They fund outcomes. The business case for communication and information access infrastructure needs to be built in the language of risk and return: **Risk framing:** What is the cost of a product launch where field teams aren't aligned on messaging? What is the cost of a compliance failure because a policy update didn't reach the people responsible for it? What is the cost of losing a senior employee whose institutional knowledge walks out the door with them? These are measurable costs that communication infrastructure directly reduces. **Return framing:** What is the value of a 10% improvement in employee engagement? Gallup's research consistently links higher engagement to lower turnover, higher productivity, better customer satisfaction, and fewer quality incidents. What is the value of cutting information-search time by half? That's real hours redirected to actual work. For organizations evaluating a communication or workforce platform investment, [MangoApps' Business Case and ROI Guide](https://www.mangoapps.com/business-case) includes calculators and a presentation template purpose-built for making this argument to finance and executive stakeholders. It's designed to help communications and HR leaders translate platform value into the business terms that move budgets. ### Reach the whole workforce, not just the people at desks Most enterprise communication infrastructure was built for knowledge workers. It assumes employees have a company email address, a laptop, and access to the intranet. For companies with significant frontline workforces, that assumption excludes the majority of the people the organization depends on. [Healthcare](https://www.mangoapps.com/industries/healthcare) systems where nurses don't sit at computers. [Retail](https://www.mangoapps.com/industries/retail) chains where store associates don't have company emails. [Manufacturing](https://www.mangoapps.com/industries/manufacturing) facilities where the shift supervisor is the primary information channel for everyone on the floor. In these environments, the gap between "we published an update" and "our people know about the update" is enormous, and closing it requires a different kind of infrastructure. The practical answer is a [mobile-first employee app](https://www.mangoapps.com/solutions/employee-app) that reaches every worker, regardless of whether they have a desk or a company email. Not a consumer messaging tool repurposed for work, but a purpose-built channel with the ability to target communications by location, role, shift, and department, with analytics that show who received, opened, and acknowledged what. This isn't a nice-to-have. In frontline-heavy industries, it's the difference between a safety update that reaches every worker in the building and one that gets posted in the break room and seen by whoever happens to walk past it. ### Make knowledge findable before it walks out the door Every time an experienced employee leaves an organization, knowledge leaves with them. In most companies, there's no system for capturing what that person knew, which customers they understood, which processes they had internalized, which workarounds existed for problems the organization doesn't even know it has. This is the slow version of the Kodak problem. The information existed. Nobody built the channel to move it from inside someone's head into a place where others could find it. Practical knowledge management looks like: - A [searchable knowledge base](https://www.mangoapps.com/solutions/knowledge-management) where institutional knowledge gets documented and maintained, not just filed - [AI-assisted discovery](https://www.mangoapps.com/ai) that can surface relevant information without requiring employees to know exactly what to search for - [Clear ownership](https://www.mangoapps.com/key-features/content-moderation) so that knowledge base content doesn't go stale while the person who wrote it is still around to update it [MangoApps' ROI Report](https://www.mangoapps.com/resources/roi-report) examines the quantified impact of unified knowledge management, including reductions in time-to-competency for new hires, decreases in repeated questions, and improvements in policy compliance. These aren't soft benefits. They're measurable, and they compound over time. ## Making the internal argument If you're a communications or HR professional trying to make the case for communication infrastructure investment, here are the most effective frames for different audiences. **For the CFO:** Lead with the McKinsey 20% figure, apply it to your headcount and average salary, and show the annual dollar figure of time lost to information-search. Then show what a 30-50% improvement in that number would return. Frame the platform investment against the productivity recovery, not against the communications budget. **For the CEO or COO:** Use the Nokia and Blockbuster stories directly. Ask: if the signals your frontline teams are seeing right now aren't reaching this room, how would you know? The inability to answer that question confidently is the business case. **For the CHRO:** Lead with engagement. Gallup's 20% global engagement figure, combined with the $10 trillion productivity cost, makes a powerful argument for the organizational cost of disconnection. Show how communication infrastructure is a prerequisite, not a supplement, for any engagement improvement initiative. **For IT/Operations:** Frame around consolidation and security. Most organizations are running multiple overlapping communication tools, none of which reach everyone, none of which talk to each other, and none of which have enterprise-grade analytics. A unified platform with proper security and compliance posture reduces risk while improving reach. ## The test every organization should run Here is a simple diagnostic. Ask your leadership team these four questions: 1. If your most experienced frontline employee observed something important today, how many steps would it take for that information to reach someone with the authority to act on it, and how many of those steps might it not survive? 2. If a critical policy changed this morning, how confident are you that every employee in every location would know about it by end of day? 3. When a new employee joins, how long does it take them to find the information they need to be independently productive, and what does that time cost? 4. When a key employee leaves, what happens to what they knew? Most organizations, if they answer those four questions honestly, will find gaps they hadn't quantified before. Those gaps are the business case. ## Communication is not the overhead. It's the operating system. The instinct to treat communication as a cost center comes from a reasonable place. Communication outputs are visible in a way that communication infrastructure isn't. You can see a newsletter. You can't see the absence of a rumor that would have spread if the newsletter hadn't existed. You can measure the cost of running an internal communications team. You can't easily measure the cost of the strategic decision that didn't get made because the right signal didn't reach the right room. But the historical record is not subtle. When information access and internal communication break down, organizations don't just get less efficient. They make wrong decisions with information they already have. They miss markets they saw coming. They ship products their own engineers warned against. They lose people who could have warned them louder. The work communication professionals do is not decoration on top of the real work. It's the thing that makes the real work possible. It's how a company of 10,000 people behaves like it has one nervous system instead of 10,000 disconnected ones. It's how a frontline employee in a warehouse knows what the executive team decided this morning. It's how a customer signal raised at a checkout counter reaches someone with the authority to act on it. Every organization is already making the bet, whether it knows it or not, about whether its information will reach the people who need it. The question isn't whether to make the bet. It's whether to fund the infrastructure that makes the bet safe. The companies that didn't are case studies now. > Ready to build the business case for communication infrastructure at your organization? [Download MangoApps' Business Case and ROI Guide](https://www.mangoapps.com/business-case), which includes calculators, benchmark data, and a presentation template designed to help you make the investment argument to executive stakeholders. Or explore [MangoApps' ROI Report](https://www.mangoapps.com/resources/roi-report) for a detailed look at how unified workforce platforms translate into measurable business outcomes.** --- # AI Won’t Replace the Frontline—It Will Decide Who Wins **Author:** MangoApps Team **Published:** 2026-04-29 **Category:** enterprise-ai AI’s real impact is not job replacement—it’s whether frontline teams get the tools, knowledge, and access to keep up. ## AI Will Not Replace the Frontline — It Will Decide Who Wins The AI debate consuming most boardrooms is asking the wrong question. Whether AI will replace jobs, when AGI arrives, or whether automation reshapes the economy entirely — those are genuinely interesting arguments. They are also almost entirely irrelevant to the decisions most operations and HR leaders need to make this quarter. The real shift is already underway, and it has nothing to do with replacement. It has everything to do with a widening gap between organizations that can deliver AI into the flow of frontline work and those that cannot. --- ### The Problem Nobody Talks About The dominant narrative in workforce AI is a headquarters story. AI policy teams, Copilot rollouts, prompt engineering workshops, internal AI councils — the energy is concentrated at the top of the organization, among knowledge workers who already have laptops, company email, and access to enterprise software. The numbers tell a stark story. Per competitive intelligence we track closely, 70% of organizations are currently operating without any formal AI policy. Fifty-two percent of employees report their organization has no known AI guidance at all. The vendor response? Better policy frameworks, communication campaigns, and AI maturity models — staged roadmaps designed to move organizations from "AI Curious" to "AI Native." That framing is useful for a Chief Digital Officer's roadmap presentation. It is nearly useless for a shift supervisor at a distribution center, a nurse on a post-acute care floor, or a store associate managing a product recall. Communication-only platforms have built their AI stories around search, writing assistance, and personalized content delivery — capabilities that matter enormously to the 20% of the workforce sitting at a desk. The other 80% barely appears in the conversation. --- ### What the Data Actually Shows #### The Frontline Is Becoming the Center of Execution Something structural is happening inside organizations — and it's accelerating. [Management layers are thinning](https://www.mangoapps.com/articles/bank-managers-keep-every-shift-covered-scheduling). Coordination roles — the people whose job was to translate information between leadership and the floor — are being reduced. The result: more responsibility is landing directly on frontline employees. More decisions, more customer interactions, more on-the-spot judgment calls, with less supervisory buffer. This is not a future scenario. It's the operating reality in healthcare, retail, manufacturing, and hospitality right now. The frontline is no longer the last mile of execution — it is the center of it. Organizations that recognize this are redesigning their workforce infrastructure accordingly. Those that don't will produce impressive strategy decks and negligible business results. #### The Access Gap Is the Actual Problem Here is the number that should reframe every AI workforce conversation: 65% of professionals have not used AI at work. Not because they lack curiosity or capability — but because the tools aren't reaching them. Only 24% of professionals report using AI with explicit organizational permission. Among knowledge workers specifically, just 38% say their organization provided proper responsible AI guidance. Now extrapolate that to a frontline workforce that often lacks a company email address, works in shifts, and accesses information through a shared device or a personal phone. The [access gap isn't a training problem. It's an infrastructure problem](/solutions/employee-app). [Disengaged employees — the majority of whom are frontline workers](/solutions/modern-hcm) — cost U.S. organizations $1.9 trillion in lost productivity annually. That number doesn't move because a headquarters team got better at writing AI prompts. #### Same Role, Radically Different Outcomes The competitive divide AI is creating isn't between industries or company sizes. It's between organizations that have built the infrastructure to put AI, knowledge, and operational tools in the hands of people doing the work — and those that haven't. A frontline worker with that infrastructure can access real-time standard operating procedures, get answers to operational questions without waiting for a manager, and onboard into new responsibilities in days rather than weeks. A frontline worker without it falls further behind every quarter — not because AI replaced their job, but because their organization failed to equip them while competitors equipped theirs. Same role. Fundamentally different trajectory. --- ### The Contrarian Insight The prevailing vendor argument is that AI adoption is a change management and communication challenge. Build the right policy, tell the right story, segment your messages by role and region — and employees will embrace AI. Communication-only platforms and intranet-focused vendors have built entire product roadmaps around this thesis: AI that helps HR teams write better announcements, search policies faster, and personalize content at scale. Here is where that approach plateaus. Better communication *about* AI is not the same as AI *in* the workflow. A frontline worker who receives a well-crafted, role-segmented message about the company's AI strategy — then returns to a shift with no AI-enabled tools and no real-time knowledge access — has not been enabled. They've been informed. Those are not the same thing. Conflating them is exactly why 32% of employees have never used AI tooling at work despite years of "AI transformation" announcements. The infrastructure was never built for them. --- ### What Actually Works: A Unified Approach The organizations closing this gap share a common architecture. They are not running AI as a separate initiative layered on top of an existing stack. Instead, they are building — or deploying — a [unified environment](/articles/mangoapps-2026-forrester-wave-intranet-platforms) where AI, communications, knowledge, [scheduling, task management, and HR services](/solutions/workflow-autopilots) exist in one place. Accessible to every employee. Through a single login. On a mobile-first interface that doesn't require a company email to use. [MangoApps](https://www.mangoapps.com) was built on exactly this premise. Our platform sustains 90%+ monthly employee engagement rates across more than one million users — not because we built a better intranet, but because we built infrastructure that serves a frontline shift worker and a corporate HR leader through the same system. Role-appropriate access, real-time knowledge, and [Ask AI](/directory/app/ask-ai) assistants trained on company-specific content — embedded directly into [operational workflows](/directory/app/workforce-bots), not bolted onto a content portal. Our Enterprise AI Hub supports 15+ languages, so multilingual frontline teams aren't left behind. Ninety-eight percent of our deployments go live on time and within budget, with 90% adoption within 90 days — because a platform that actually reaches frontline workers doesn't require years of change management to prove its value. --- ### The Business Outcome: Faster, Better, More Resilient Execution The organizations that win in the AI era won't be the ones that ran the most pilots or published the most sophisticated AI policies. They will be the ones that connected AI, knowledge, communications, and operations into a single environment — and made it available to every employee, especially those on the floor, in the field, and on the shift. AI will not replace the frontline. But it will absolutely determine which organizations move faster, serve customers better, and build workforces that compound in capability over time. The question isn't whether your organization is "AI curious" or "AI native." The real question is simpler: can the people actually doing the work access what they need, when they need it, without friction? That's a workforce infrastructure question — and it's the one most organizations aren't asking yet. If your AI strategy stops at headquarters, your competitive advantage stops there too. --- # MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation **Author:** MangoApps Team **Published:** 2026-04-28 **Category:** news-and-updates MangoApps was evaluated in The Forrester Wave™: Intranet Platforms, Q2 2026, reinforcing its leadership in unified workforce solutions. ISSAQUAH, Wash., April 9, 2026 — MangoApps, the AI-Powered Unified Workforce Platform, today announced it has been evaluated in The Forrester Wave™: Intranet Platforms, Q2 2026 report by Forrester Research, Inc. “Being evaluated for this report is meaningful. We've spent 15 years building a platform that people actually adopt and love using, whether they're at a corporate desk or on a warehouse floor, and being included in an independent evaluation is incredibly validating,” said Anup Kejriwal, Founder and CEO of MangoApps. “The enterprises we serve don't have the luxury of low adoption or shaky implementations. They need a partner who shows up, and that's exactly what MangoApps is built to be.” [MangoApps](https://www.mangoapps.com/) serves enterprises across healthcare, retail, manufacturing, hospitality, and financial services — industries where reaching a distributed, often deskless workforce isn't optional, it's operationally critical. The platform unifies [intranet](https://www.mangoapps.com/solutions/modern-intranet), internal communications, [frontline operations](https://www.mangoapps.com/solutions/workforce-management), [HR](https://www.mangoapps.com/solutions/modern-hcm), and [AI](https://www.mangoapps.com/ai) in a single hub, replacing fragmented point solutions with one modern system. [Customers](https://www.mangoapps.com/customers) have reported 90% adoption rates within 90 days, workforce engagement levels above 87%, and savings of 10 to 15 hours per employee per week through tool consolidation. This recognition comes on the heels of being named the Gold award winner for Excellence in Intranet & Communications Platforms in [Reworked’s 2026 IMPACT Awards](https://www.mangoapps.com/articles/mangoapps-gold-reworked-2026-impact-awards). It builds on a strong track record of independent validation, including three consecutive years as a [Gartner® Magic Quadrant™](https://www.mangoapps.com/articles/mangoapps-visionary-in-2025-gartner-magic-quadrant-intranet-packaged-solution) Visionary for Intranet Packaged Solutions and recognition as an [IDC MarketScape Leader](https://www.mangoapps.com/articles/mangoapps-leader-idc-marketscape-employee-experiences-integrated-employee-workspaces)` for Employee Experiences for Integrated Employee Workspaces in 2025. Visit [www.mangoapps.com](http://www.mangoapps.com) to learn more. Forrester does not endorse any company, product, brand, or service included in its research publications and does not advise any person to select the products or services of any company or brand based on the ratings included in such publications. Information is based on the best available resources. Opinions reflect judgment at the time and are subject to change. For more information, read about Forrester's objectivity at [forrester.com/about-us/objectivity/](http://forrester.com/about-us/objectivity/). About MangoApps MangoApps is the unified workforce platform built for frontline and operational teams. It brings communication, daily operations, and employee support into a single platform managers use to keep teams aligned and work moving across frontline and office environments. Trusted by leading organizations around the world, MangoApps supports business-critical work every day. For more information, visit [www.mangoapps.com](http://www.mangoapps.com).** --- # How Bank Managers Keep Every Shift Covered with Scheduling **Author:** MangoApps Team **Published:** 2026-04-27 **Category:** industry-use-cases See how bank managers reduce coverage gaps, streamline shift changes, and keep branch teams aligned with one governed scheduling system. ## **How a Bank Manager Keeps Every Shift Covered Without Chasing Texts, Emails, or Whiteboards** At 7:12 a.m., the branch manager is already dealing with three separate problems before the doors open. One teller called out sick. A fraud-prevention reminder came in overnight, but not everyone on the morning shift has seen it. And the schedule on the back office wall no longer matches the changes made by the regional team yesterday afternoon. The manager has the same thought they have most mornings: if the day starts this fragmented, how many small failures will compound before lunch? That is the hidden reality of branch operations. The work looks orderly from the outside, but inside the branch, [information moves unevenly](https://www.mangoapps.com/glossary/frontline-communication). Some employees live in email. Some only check their phones. Some rely on a manager to repeat updates verbally. In financial services, that creates more than inconvenience. It creates inconsistency in customer service, compliance exposure, and avoidable overtime. This guide covers the scheduling practices that keep branches running — and what makes them break down. ### **The Five Practices That Actually Keep Shifts Covered** ### Most branch managers who run tight operations are not doing anything exotic. They are doing five things consistently that their struggling counterparts are not. **1. Build a coverage baseline before the week starts.** The managers who handle midday absences well are not more resourceful in the moment. They prepared for them ahead of time. Before the week opens, map out which shifts carry single-point-of-failure risk — positions where one absence leaves no redundancy. Flag those in advance and identify a coverage source for each: a cross-trained employee, a part-timer with open availability, or a neighboring branch with a floater. This does not require software. A structured pre-week review conversation with a team lead accomplishes the same goal. The discipline is what matters, not the tool. In practice, this looks like a 15-minute Monday morning check with your team lead: identify the two or three shifts that week with no backup option, name a specific person who could cover each one, and confirm their availability before the week starts. That conversation does not need to be formal. It needs to happen before Wednesday. For a deeper look at [what separates a good shift schedule from one that breaks under pressure](https://www.mangoapps.com/glossary/scheduling), the fundamentals apply across industries. **2. Keep a live on-call list and rotate it fairly.** Every branch needs a short list of employees willing to take last-minute shifts. The common failure is treating this list as static. Employees burn out, circumstances change, and fairness erodes when the same two people absorb every emergency. Rotate the on-call expectation across your eligible team, be transparent about who is on the list each week, and recognize or compensate employees who step up. A list that is managed fairly gets used. One that feels like a burden gets ignored. A simple rotation works in most branches: divide your eligible on-call pool into weekly slots, communicate the list at the start of each week, and keep a running log of who has been called and who has stepped up. If you are tracking it in a spreadsheet, a single column per week showing name, called/not called, and covered/declined is enough to spot when the distribution has drifted unfairly. This problem is not unique to banking. [Reaching and engaging frontline workers](https://www.mangoapps.com/articles/the-complete-guide-to-deskless-worker-communication/) consistently — including through something as basic as a fair on-call rotation — is one of the clearest drivers of whether those employees stay or leave. **3. Separate the schedule from the communication about the schedule.** This is where most branches leak time. The schedule exists in one place, but changes to it happen everywhere — texts, hallway conversations, sticky notes on the manager's desk. By Friday, no one has a clear record of what actually happened. The fix is establishing one authoritative channel for schedule updates, whatever that channel is, and making it non-negotiable. When a shift changes, it gets updated in the source of record first, then communicated. Not the reverse. For branches with a mix of desk-based and counter staff, this also means choosing a channel that [actually reaches employees who do not sit at a computer all day](https://www.mangoapps.com/glossary/frontline-employee-app). A communication approach built for knowledge workers does not work for a teller checking their phone between customers. **4. Handle no-call-no-shows with a documented protocol, not improvisation.** No-call-no-shows create two problems: the immediate coverage gap, and the inconsistent response. If managers handle them differently each time, employees learn that the consequences are unpredictable, which tends to make the behavior more common rather than less. A basic protocol looks like this: attempt contact within the first 15 minutes of a missed shift, document the attempt, apply the coverage plan from your pre-week review, and record the no-call-no-show consistently for performance tracking. Consistency signals that the expectation is real. Improvisation signals that it is negotiable. [Compliance tracking built into workforce operations](https://www.mangoapps.com/key-features/compliance-tracking) makes this documentation automatic rather than something a manager has to remember to do manually. **5. Treat compliance and scheduling as the same workflow.** In financial services, putting an undertrained employee in front of a regulated workflow is not just an HR issue — it is a risk issue. Managers who handle this well build training completion status into their scheduling awareness. Before a shift is finalized, they know which employees are current on required procedures. That does not mean blocking someone from working. It means the manager is not surprised. [Compliance training automation](https://www.mangoapps.com/glossary/compliance-training-automation) is the infrastructure that makes this possible at scale. Without it, verifying who is current on what requires manual cross-referencing across systems — which most managers do not have time for before a 7:00 a.m. open. ### **What Breaks These Practices Down** ### The five practices above work. The reason most branches do not follow them consistently is systems friction — the schedule lives in one tool, communications live in another, [compliance and training tracking](https://www.mangoapps.com/solutions/learning-management) lives in a third, and no one has a unified view. Managers spend their time reconciling information instead of acting on it. This is the core problem [workforce management](https://www.mangoapps.com/glossary/workforce-management) platforms are designed to solve: not just generating a schedule, but connecting scheduling to the broader operational context — who needs to be where, what they need to know before they get there, and how changes get communicated without falling through the cracks. Related: [What goes into a good shift schedule — and what makes them fail](https://www.mangoapps.com/glossary/scheduling) Related: [How frontline employees stay connected when email isn't an option](https://www.mangoapps.com/glossary/frontline-employee-app) ### **What If You Cannot Invest in New Software Right Now?** ### The honest answer is that most of the practices above do not require a platform. They require consistency. A shared calendar, a group chat with clear norms, a simple spreadsheet with your pre-week coverage review — none of those cost money, and any of them can close the gap between reactive and proactive scheduling. The tradeoff is time and reliability. Manual coordination works until it doesn't. When the volume of changes, the number of compliance-sensitive roles, or the speed of [communication across a distributed branch team](https://www.mangoapps.com/glossary/frontline-communication) exceeds what a manager can track manually, the system fails. That is usually not a dramatic moment. It is the slow accumulation of a few missed updates, a few extra hours of overtime, and a few customer interactions that did not go the way they should have. At that point, the question becomes whether the cost of the current system — in manager time, overtime, and service inconsistency — is higher than the cost of changing it. ### **A Day in the Branch with MangoApps Scheduling** ### For organizations ready to reduce that friction, [MangoApps](https://www.mangoapps.com/solutions/shifts-schedules) brings scheduling into the same environment where branch communication, training, and policy updates already live. The effect is not just a cleaner schedule view. It is the elimination of the gap between what the schedule says and what the team knows. **The morning shift is visible before the branch opens.** The manager starts with a single view of the day's coverage and can see where gaps exist before the first customer walks in. Changes are easier to coordinate because [scheduling lives in the same platform](https://www.mangoapps.com/solutions/shifts-schedules) as the rest of the branch's communications and resources. Instead of chasing updates across channels, the manager keeps the team aligned in one place. **Midday changes stop becoming a chain reaction.** The manager adjusts staffing and communicates the change to the right people without broadcasting it to the entire branch. Because scheduling is part of a unified platform, the update is not isolated from the rest of the employee experience. The same environment that helps employees find policies also helps them understand where they are supposed to be and when. [Secure, compliant messaging](https://www.mangoapps.com/key-features/instant-messaging) built for regulated industries means those updates do not have to travel through WhatsApp or personal text threads. **Training and scheduling stop competing with each other.** When scheduling sits inside a broader platform, it becomes easier to connect who is working with what they need to know. The [learning management system](https://www.mangoapps.com/solutions/learning-management) sits in the same environment as the schedule, so managers are not cross-referencing two separate tools to confirm an employee is cleared for a regulated workflow before a shift starts. **The week ends with less cleanup.** The manager has a reliable operational record inside the same platform employees already use for communication and work updates. That makes it easier to review staffing patterns, spot recurring gaps, and plan the next week with more confidence. [Task management connected to shifts](https://www.mangoapps.com/solutions/task-management) means the closing checklist, the compliance follow-ups, and the next week's coverage review all live in one place rather than across email threads and whiteboards. ### **Scheduling Practices That Carry Across Industries** ### Branch banking is one context where these problems surface. The same patterns show up in healthcare, retail, and hospitality — any environment where [shift coverage is load-bearing](https://www.mangoapps.com/glossary/workforce-management), compliance is non-negotiable, and the workforce is largely deskless. Related: [How store managers handle scheduling in high-turnover retail environments](https://www.mangoapps.com/articles/store-managers-playbook-smarter-retail-scheduling) Related: [How MangoApps supports financial services branch operations](https://www.mangoapps.com/industries/financial) The core issue is the same across all of them: when scheduling is disconnected from communication and compliance, the manager absorbs the cost personally. Every improvement to that system pays the manager back in time and the organization back in consistency. ### **A Few Questions That Come Up Often** ### *What if the no-call-no-show problem is one specific employee, not a system issue?* A documented protocol matters here more than anywhere else. When a pattern is concentrated in one person, the written record — dates, contact attempts, outcomes — is what makes a performance conversation or termination defensible. Without it, the manager is working from memory against an employee who may dispute the history. *What if I don't have cross-trained staff to draw from?* Cross-training is a longer investment, but you can start narrower than you think. Identify the one or two roles most likely to create a coverage crisis when absent, and train one backup person for each. You do not need a fully flexible team to reduce single points of failure — you just need one backup per critical role. *How much does compliance tracking software typically cost?* It varies significantly depending on workforce size and how many systems need to connect. The more useful question for a pilot is whether the time your managers currently spend manually verifying training completion justifies the investment — most branches can answer that with a single week of tracking how long the process actually takes. ### **Getting Started** ### Whether you are refining your current process or evaluating a platform, start with one question: how long does it take your branch to recover from a single unplanned absence? If the answer is most of the day, the problem is not the absence. It is the system around it. For organizations ready to test whether a unified platform reduces that recovery time, the right pilot focuses on one branch, one recurring pain point, and one measurable outcome — fewer unfilled shifts, less manager time on coordination, or reduced overtime. MangoApps supports [200+ enterprise integrations](https://www.mangoapps.com/industries/financial) and connects scheduling to the broader employee experience, including communications, training, and compliance tracking. Implementation typically runs 8 to 12 weeks. [See MangoApps Shifts & Schedules →](https://www.mangoapps.com/solutions/shifts-schedules) ### **Closing** ### The best branch schedule is the one the manager does not have to rebuild at 7:12 a.m. That does not happen by accident. It happens because someone built the practices, the protocols, and — when the volume demands it — the platform to support them. --- # Workforce Management's Last-Mile Problem: Data Without Context **Author:** MangoApps Team **Published:** 2026-04-26 **Category:** workforce-management A floor supervisor at a regional warehouse spends a Friday afternoon building next week's schedule. She's methodical — balancing coverage, rotating weekend assignments, watching overtime hours. # Workforce Management's Last-Mile Problem: Data Without Context A floor supervisor at a regional warehouse spends a Friday afternoon building next week's schedule. She's methodical — balancing coverage, rotating weekend assignments, watching overtime hours. She submits it, sends out notifications, and closes her laptop. Monday morning, one of her best team members doesn't show up. His vacation was approved three weeks ago. HR has it on file. His team lead knew. The scheduling tool she was working in just didn't. The leave existed in the system. It was captured, approved, and stored correctly. The problem wasn't a process failure. It was a placement failure — the information was in the wrong place when the decision was being made. And by the time it surfaced, the cost was already paid: an understaffed shift, a frustrated employee, and a manager trying to explain something that could have been prevented automatically. This kind of failure repeats itself across workforce management every day, and in more places than just the schedule board. --- ## When the Schedule Board Doesn't Know What HR Knows Scheduling and leave management have lived as separate systems for so long that most managers treat reconciliation between them as a permanent tax on their time. Check the schedule. Open the leave system. Cross-reference. Repeat. [Leave Visibility on Schedule Board](https://www.mangoapps.com/changelog/2952) eliminates that loop. Approved employee leave now appears directly on the shift scheduling grid, with visual indicators, leave-type badges, and tooltips that surface the details without requiring a context switch. Managers see what's confirmed before they build — not after the shift is published and an employee has to call in to remind them. The same week, [Contracted Day-Off Patterns for Non-Standard Schedules](https://www.mangoapps.com/changelog/2955) addressed a related gap. For organizations running four-day work weeks, rotating shift schedules, or non-standard off-day configurations, the schedule board previously had no awareness of per-employee, per-week patterns. Managers had to carry that knowledge in their heads or in a spreadsheet. Now, automatic "OFF" indicators appear on the board for contracted off days, and the system warns before a conflicting shift is assigned. The information was always available — it just hadn't been wired to the surface where it needed to act. At the location level, [Location Contracted Hours Budgeting](https://www.mangoapps.com/changelog/2950) closes a budget visibility gap that most operations teams have worked around with separate spreadsheets or monthly finance reviews. Managers can now see their weekly contracted hours target alongside actual usage — this month, last month, and year-to-date — without leaving the scheduling interface. The budget data existed somewhere. Now it's in the scheduling view, where the decisions that affect it are actually made. And for HR teams trying to understand attendance trends, [Attendance Calendar View](https://www.mangoapps.com/changelog/2954) provides a different kind of placement fix. Attendance records in a calendar layout make patterns, coverage gaps, and absences visible at a glance. The alternative — running a report, exporting to a table, and trying to spot trends in rows of dates — requires effort that most teams can't sustain consistently. None of these are new data sources. Each one surfaces information that was already captured somewhere in the system. The work was connecting it to the moment where it actually changes what someone does next. --- ## The Same Problem at the Question Layer The data placement gap doesn't stop at scheduling. It runs through every interaction employees and managers have with workplace software. When someone asks a question about a policy, a payroll record, or a workflow, most AI assistants respond without any awareness of what the user was looking at when they asked. The context gets dropped. The answer is drawn from a general knowledge base that doesn't know whether you're reviewing a compensation record, navigating a compliance document, or standing inside a specific module trying to figure out what a field means. [Ask AI Page-Aware Routing](https://www.mangoapps.com/changelog/2958) addresses this at the question-answering layer. Ask AI now detects the context of the page an employee is on and routes the question to the right specialized agent automatically. If you're in the scheduling view, your question routes to the scheduling agent. If you're looking at an employee's profile in a specific module, the answer is grounded in that record — not a generic response that requires you to re-explain the situation. This pairs with [Ask AI Multi-Agent Routing](https://www.mangoapps.com/changelog/2951), which now chains multiple specialized agents for questions that cross domain boundaries. A complex question about how leave policy interacts with scheduled overtime, for example, doesn't need to go to a single generalist that struggles to hold both domains simultaneously — it routes through a sequence of specialized models and produces a more accurate answer without requiring the employee to simplify their question first. The pattern is the same as the scheduling board: context changes the usefulness of an answer dramatically. The same question gets a worse answer when the system doesn't know what you're looking at. A related version of this shows up in onboarding. [Business Setup Checklist](https://www.mangoapps.com/changelog/2958) now greets new administrators with a setup experience filtered to their specific use cases. A healthcare organization's day-one configuration priorities look different from a logistics company's. A generic setup checklist treats every new customer the same — and then requires admins to figure out what's relevant for their context. The filtered approach brings the right starting point to the right operator from the first session. --- ## Why This Pattern Keeps Resurfacing The technology challenge of frontline workforce management has rarely been about capturing data. Organizations have been capturing attendance, leave, schedules, and headcount for decades. The problem has been that the systems capturing this data were designed as records of what happened — not as inputs to what should happen next. That design choice made sense when software was primarily an improvement on paper. You stored data so you could retrieve it later. The expectation was that a person would do the connecting — find the relevant records, compare them, and make a judgment call. What this week's releases collectively represent is a shift in where that connecting work happens. Instead of a manager checking leave in one system and the schedule in another, the schedule surfaces the leave. Instead of an employee formulating a question and hoping the AI has enough context to answer it accurately, the AI reads the page they're already on. Instead of a new admin learning the platform through trial and error, the checklist knows what kind of organization they're setting up. These are not glamorous changes. They don't add new data categories or unlock new analytical capabilities. But they do close a gap that produces real operational costs: the no-show that could have been prevented, the scheduling conflict that required three follow-up messages to resolve, the AI answer that was technically correct but completely irrelevant to the actual situation. The last mile of workforce data — getting it from where it's stored to where it's needed — has always been the hardest part. Closing that gap, feature by feature, is what turns a data system into a decision-support system. --- # MangoApps Honored as Silver Stevie® Award Winner in 2026 American Business Awards® **Author:** The MangoApps Team **Published:** 2026-04-23 **Category:** news-and-updates MangoApps earned a Silver Stevie® Award for embedding AI across HR and workforce operations at enterprise scale, supporting 2M+ daily users. MangoApps was named the winner of a Silver Stevie® Award in the AI in Human Resources & Talent Management category in The 24th Annual American Business Awards® today. The company was recognized for its nomination titled "Embedding AI into HR & Workforce Operations at Enterprise Scale." The American Business Awards are the U.S.A.'s premier business awards program. All organizations operating in the U.S.A. are eligible to submit nominations – public and private, for-profit and non-profit, large and small. Nicknamed the Stevies for the Greek word meaning "crowned," the awards will be presented to winners at a gala ceremony at the Marriott Marquis Hotel in New York on Tuesday, June 9. Tickets are now on sale. More than 3,600 nominations from organizations of all sizes and in virtually every industry were submitted this year for consideration in a wide range of categories, including Startup of the Year, Executive of the Year, Best New Product or Service of the Year, Marketing Campaign of the Year, Thought Leader of the Year, and App of the Year, among others. MangoApps was nominated in the AI in Human Resources & Talent Management category for its work embedding AI across HR and workforce operations at enterprise scale. MangoApps has spent the past several years building AI into the foundation of its unified workforce platform rather than bolting it on as a feature. The result is a platform that brings together communications, workforce management, learning, knowledge management, and HR services in a single system used by both desk and frontline employees. Recent capabilities recognized by judges include [generative AI for creating pages, forms, and workflows](https://www.mangoapps.com/articles/ai-instant-surveys-quizzes-and-team-structures) from natural language prompts; [AI-powered scheduling and shift swap tools](https://www.mangoapps.com/articles/native-shifts-schedules-unified-frontline-experience); [AI-driven onboarding](https://www.mangoapps.com/directory/app/onboarding-hub); and [conversational AI assistants](https://www.mangoapps.com/ai) that work across enterprise systems including Microsoft 365, Google Workspace, ADP, UKG, and ServiceNow. The platform currently supports organizations as large as 300,000 employees, with engagement rates reaching 88% across deployments. Over 2 million users currently rely on MangoApps at work, every day. "This recognition reflects the work our team has put into making AI genuinely useful across the employee lifecycle, not just in one corner of it," said Anup Kejriwal, CEO and Founder, MangoApps. "From frontline scheduling to HR self-service to workforce onboarding, we've focused on embedding AI where the work actually happens. We're proud of what the team has built and grateful for this recognition." More than 250 professionals worldwide participated in the judging process to select this year's Stevie Award winners. "Organizations across the United States continue to set a high standard for innovation and performance," said Stevie Awards President Maggie Miller. "The breadth and quality of nominations submitted to the 2026 American Business Awards reflect a dynamic and competitive business environment, where organizations are finding new ways to drive growth, deliver value, and make an impact." Details about The American Business Awards and the list of 2026 Stevie winners are available at [ABA.StevieAwards.com](http://aba.stevieawards.com). **About the Stevie Awards** Stevie Awards are conferred in nine programs: the Asia-Pacific Stevie Awards, the German Stevie Awards, the Middle East & North Africa Stevie Awards, The American Business Awards®, The International Business Awards®, the Stevie Awards for Women in Business, the Stevie Awards for Great Employers, the Stevie Awards for Sales & Customer Service, and the new Stevie Awards for Technology Excellence. Stevie Awards competitions receive more than 12,000 entries each year from organizations in more than 70 nations. Honoring organizations of all types and sizes, as well as the people behind them, the Stevies recognize outstanding workplace performance worldwide. Learn more about the Stevie Awards at [http://www.StevieAwards.com](http://www.stevieawards.com).** --- # Your Intranet Doesn't Have a Content Problem **Author:** MangoApps Team **Published:** 2026-04-21 **Category:** intranet Most intranet failures aren’t about content—they’re about integration, search, and reach across the digital workplace. ## Your Intranet Doesn't Have a Content Problem. It Has an Integration Problem. Every IT leader searching for a "CMS for intranet" starts with the same implicit assumption: the right publishing tool will fix what's broken. It won't. The content management layer is the easiest part of a modern intranet to get right — and the least likely to be the reason employees abandon it six months after launch. What actually kills intranet adoption is the gap between where content lives and where work happens. When your CMS operates as a separate layer from your search, HR records, task management, and frontline mobile experience, you haven't built a digital workplace. You've built a publishing system that employees learn to route around. --- ### The Problem Nobody Talks About The intranet CMS market has largely solved the editing experience. Drag-and-drop builders, visual templates, role-based publishing permissions — these are table stakes. What remains unsolved is what happens *after* content is published. Can a shift worker on a mobile device find the updated safety policy before their 6 a.m. start? Does search surface the right document, or return three outdated versions from three different folders? Does IT know which content is driving action and which is generating zero engagement? Legacy intranet platforms — those built around SharePoint-era assumptions — treat content management as the destination. Publish the page, check the box, move on. The result is a digital graveyard: well-organized content that nobody reads, search that returns noise instead of answers, and IT teams spending 10–12 hours a week manually fielding questions that a properly connected knowledge base would answer automatically. That's not a CMS problem. That's an architecture problem. --- ### What the Data Actually Shows #### Content Without Context Doesn't Get Read The fundamental failure of standalone intranet CMS tools is that they publish to everyone and reach no one. A policy update sent to 4,000 employees with no targeting, no mobile-first delivery, and no read-receipt mechanism isn't communication — it's filing. The scale of this problem is larger than most IT leaders account for. Research from the Achievers Workforce Institute finds that only 21% of employees feel connected to their peers — a figure that reflects not just culture, but the failure of information architecture to create genuine reach. When content isn't targeted to the right person at the right moment, it doesn't build connection; it adds noise. A [Company Portal](https://www.mangoapps.com/key-features/company-portal) built on **role-based content targeting** addresses this directly — the platform automatically shows each employee only the information relevant to their job title, department, or location. A warehouse associate in Phoenix sees different content than a finance analyst in Chicago. No manual configuration required. No separate intranets to maintain. The downstream effect is measurable. Enterprise deployments that replace untargeted broadcast publishing with role-based delivery consistently report frontline adoption rates above 90% within the first six months — a benchmark outcome documented across multiple large-scale implementations. That's not a feature difference. It's an architecture difference. #### Search Is Where Most Intranet CMS Investments Collapse Ask any IT leader what employees complain about most on the intranet. The answer is almost always search. Not because the content isn't there — it usually is — but because most search tools weren't built to connect across systems or consistently surface the most relevant result. The [benefits of a well-built intranet search engine](https://www.mangoapps.com/articles/benefits-of-an-intranet-search-engine) go well beyond convenience. When employees can't find what they need, they ask a colleague, send a Slack message, or email HR — all of which consume time that compounds across an organization. The Achievers Workforce Institute estimates U.S. workforce attrition alone will cost between $1.3 trillion and $5.1 trillion in 2026, driven in part by disengagement that poor information access accelerates. **AI-powered search** addresses this by learning from user behavior and content patterns to rank results by relevance, not just recency or keyword match. It also respects permissions dynamically, so employees only see content they're authorized to access. IT teams that [optimize intranet search](https://www.mangoapps.com/articles/how-to-optimize-your-intranet-search) this way consistently report saving 10–12 hours per week in fielded requests alone. That's not a rounding error — that's a headcount-equivalent productivity gain. #### Deployment Speed Matters More Than Feature Lists Organizations often buy standalone CMS tools because they appear faster to deploy than a full platform. This assumption is usually wrong. A CMS that requires custom integrations to connect to your HRIS, task management system, and mobile app isn't faster — it's just smaller. The integration work happens later, at higher cost, and with greater organizational friction. Traditional intranets built on SharePoint-era assumptions take months to deploy, strain IT teams, and produce static, ungoverned content that becomes stale before it reaches frontline workers. The pattern is well-documented: enterprises that select a standalone CMS for speed find themselves funding a second implementation within three years to close the gaps the first tool left open. By contrast, organizations that select platforms built on a **consolidated database architecture** — a single, unified data layer that eliminates the need to sync content, users, and permissions across separate systems — consistently report faster time-to-value, improved information sharing across distributed teams, and cross-department collaboration that a siloed CMS cannot produce. One benchmark outcome cited across enterprise case studies: a 30-point engagement score increase attributed to replacing a legacy intranet with an integrated digital workplace platform. --- ### What to Look For in an Intranet Platform If you're comparing a standalone CMS against a unified intranet platform, the buying question is not whether the editor is easy to use. It is whether the platform can keep content connected to the work it is supposed to support. Look for a platform that can do all of the following in one system: - publish content once and make it searchable, targetable, and accessible across roles and devices; - support frontline mobile access without requiring a separate intranet or company email; - connect knowledge management tools, HR information, and task workflows so employees do not have to jump between systems; - give IT and operations teams visibility into what content is being read, ignored, or repeatedly searched for; - reduce the need for separate tools of knowledge management that create duplicate governance and duplicate implementation work. That is the difference between buying a CMS and uniting intranet content with the rest of the employee experience. If the platform cannot do those things natively, the organization usually ends up stitching together integrations later. --- ### The Contrarian Insight Here's what the CMS-for-intranet search category gets systematically wrong: it frames the buying decision as a content problem when the actual problem is a reach problem. Legacy intranet platforms were designed for desk workers with company email addresses and reliable desktop access. They solved content management for that audience reasonably well. Then the workforce changed. Today, 80% of the global workforce is frontline or deskless. They don't have company email. They're not sitting at a laptop at 9 a.m. to read the CEO's quarterly update. A CMS that publishes beautifully formatted pages to a desktop browser is, for this population, functionally invisible. Research bears this out: in one large-scale omnichannel deployment, 79% of frontline employees reported receiving critical leadership messages they had not received before the platform change — meaning the prior CMS was failing nearly four in five workers silently. This is exactly where legacy platforms plateau. They can't serve a shift worker and a knowledge worker from the same system without a separate mobile app bolted on as an afterthought. That means two governance models, two adoption curves, and two sets of content that inevitably drift out of sync. The real intranet CMS question isn't "which tool has the best editor?" It's "which platform can publish content, target it by role and location, surface it through intelligent search, deliver it to any device without requiring a company email, and confirm whether it was actually read?" Those are not CMS features. They are unified platform features. --- ### What Actually Works: A Unified Approach A unified [intranet deployment approach](/solutions/modern-intranet) combines content management, AI-powered search, role-based targeting, frontline mobile access, and workforce operations in a single platform. The results consistently outperform what standalone CMS tools can produce — not because the editing experience is better, but because the architecture eliminates the integration debt that standalone tools create. - **Drag-and-drop page building** lets HR and communications teams publish content without IT support or coding knowledge. See [Sites](/directory/app/sites) and the [Webpage Builder](/key-features/webpage-builder) for how this works in practice. - **Real-time analytics** show exactly who is engaging with content, so teams can measure reach and optimize messaging — not guess at it. - **Native CMS integration** means content published in one place is immediately searchable, targetable, and accessible across every device and role — no middleware required. - **[Ask AI](/directory/app/ask-ai)** and **[Workforce Bots](/directory/app/workforce-bots)** extend the reach of published content by letting employees query the knowledge base in natural language, reducing the volume of repetitive IT and HR requests that accumulate when search alone isn't enough. The principle is consistent across implementations: a unified architecture doesn't have to mean implementation complexity. What it does mean is that the CMS is never a standalone layer that IT has to hold together with integrations — it's embedded inside a system where content, search, targeting, and delivery are already connected. For a deeper look at why communication tools that focus only on sending fail to drive adoption, see [Why Internal Communication Tools Fail at Sending Alone](/articles/why-internal-communication-tools-fail-at-sending-alone). --- ### The Evaluation Question Every Vendor Should Answer If you're evaluating a CMS for your intranet, ask every vendor the same question: *What happens to this content after it's published?* If the answer requires a separate search tool, a separate mobile app, or a separate analytics platform to complete the picture, you're not buying a CMS. You're buying the first piece of a puzzle you'll spend the next three years trying to finish. --- # Why Internal Communication Tools Fail at Sending Alone **Author:** MangoApps Team **Published:** 2026-04-20 **Category:** workplace-productivity Most internal communication tools stop at delivery. Real impact comes from reach, acknowledgment, and action. ## Internal Communication Tools Fail When They Stop at Sending Most companies do not have a communication problem. They have a verification problem. A message that appears in a feed, inbox, or app is not the same as a message that is read, understood, and acted on. That gap is especially visible in frontline environments, where intranet posts often see only 5-15% open rates, compared with 20-35% for corporate audiences [MangoApps]. That is why the usual search for *tools for internal communication* often misses the real issue. The market keeps selling better delivery: a news feed here, an AI assistant there, a mobile wrapper on top of a legacy stack. But the harder job is proving reach, requiring acknowledgment, and connecting communication to work. ### The Problem Nobody Talks About Most tools in this category are narrow by design. - Communication-only platforms focus on publishing. - Legacy intranet platforms focus on content access. - Frontline messaging tools focus on speed. Each one solves part of the problem. Then it leaves the rest to another system. That fragmentation becomes obvious in distributed organizations. A 120-store quick-service restaurant chain does not need another place to post updates. It needs a way to target the right stores, confirm receipt, and make sure a policy change actually changes behavior. A 2,000-bed hospital system has the same challenge, only with higher stakes. If the message is critical, “sent” is not a meaningful outcome. ### What the Data Actually Shows #### Reach is not the same as communication Our benchmarks make the gap clear. Corporate intranet posts typically see 20-35% open rates, while frontline intranet posts fall to 5-15% [MangoApps]. That is not mainly a content issue. It is a channel and workflow issue. This is why internal communications should be measured as a system, not as a broadcast. In our [internal communications framework](https://www.mangoapps.com/glossary/internal-communications), we define it around three outcomes: - **Audience receipt**: did the right people get the message? - **Read confirmation**: did they actually see it? - **Behavior change**: did they act on it? That matters more than the number of posts published. Publishing volume does not tell you whether a store associate, nurse, or plant operator saw the update. #### A newsletter works only when it is disciplined The best internal newsletter is not a content dump. It is a repeatable cadence with a clear purpose. In our example of a 4,500-person distributed company, a weekly Friday morning newsletter reached open rates in the 60s when it was kept to a five-minute reader contract [MangoApps]. That is a useful benchmark because it shows what happens when communication is edited for attention instead of volume. We see the same pattern in [our internal newsletter guidance](https://www.mangoapps.com/glossary/internal-newsletter): shorter, more relevant, and more targeted communication performs better. Frontline-heavy organizations also need mobile push, video, and translated versions because email-first formats do not fit how retail associates, nurses, and plant operators work. The lesson is straightforward: the format has to match the workforce. #### Internal communication becomes more valuable when it connects to work The strongest internal communication tools do more than send messages. They support action. That is why targeted communication matters so much in operational environments. A policy update can require acknowledgment before it is considered complete. A shift change can trigger the right alert. A compliance notice can be tracked by location, role, or team. In simple terms, **acknowledgment** means the recipient confirms they received and reviewed the message. That confirmation matters when the message affects safety, compliance, scheduling, or operations. This is also where communication starts to overlap with workforce movement. In our [internal mobility analysis](https://www.mangoapps.com/glossary/internal-mobility), organizations with strong internal mobility fill 25-40% of open positions from within. External hiring averages $4,700 per employee per SHRM, and external roles take 44 days on average to fill [MangoApps]. **Internal mobility** means employees can move into new roles, teams, or opportunities inside the company instead of leaving for another employer. Communication is part of that system. If employees cannot see opportunities, understand requirements, or move quickly, the organization pays for it in time and turnover. ### The Contrarian Insight The industry keeps treating internal communication as a content problem with a distribution layer. That is exactly where frontline-only messaging tools plateau. They can push a message, but they cannot prove comprehension, enforce acknowledgment, or connect the message to the next operational step. That is why the “single app” pitch is incomplete unless the app also owns the workflow around the message. A feed without targeting is noise. AI without governed content is guesswork. Mobile access without acknowledgment tracking is just faster broadcasting. The real constraint is not message volume. Employees do not need more messages. They need fewer messages that are relevant, verified, and actionable. ### What Actually Works: A Unified Approach A stronger model is to place internal communication inside a unified platform that already understands the employee, the role, the location, and the workflow. That makes it possible to send the right message through email, SMS, or in-app channels, track who received it, and connect it to the task, policy, or process it affects. That is why customers use [MangoApps](https://www.mangoapps.com) as more than a communication layer. The platform is also built to support the broader employee experience, including internal communications, knowledge, operations, and AI-assisted self-service. That reduces the need for IT to stitch together separate tools. When communication becomes part of the system of work, it stops being a broadcast and starts becoming an operational advantage. If you are evaluating tools for internal communication, ask a harder question than “Can it send messages?” Ask whether it can prove reach, drive acknowledgment, and support the work that follows. That is the difference between another channel and a platform employees actually use. --- # Before You Hit Publish: HR Configuration Gets a Preview Layer **Author:** MangoApps Team **Published:** 2026-04-19 **Category:** workplace-productivity A benefits administrator spends two hours configuring the open enrollment email. She checks every field — plan name, deadlines, contact information — then enables it for 1,200 employees. # Before You Hit Publish: HR Configuration Gets a Preview Layer A benefits administrator spends two hours configuring the open enrollment email. She checks every field — plan name, deadlines, contact information — then enables it for 1,200 employees. Three hours later, the HR inbox is full. The email rendered with a broken merge field. The enrollment link pointed to last year's form. This is not a story about a bug. It is a story about a gap in almost every workforce platform: the distance between "I think this is configured correctly" and "I know what employees will actually see." Configuration UIs let administrators set things up, but they rarely let admins verify the result from the employee's perspective. The outcome is a quiet tax — not measured in software licenses but in support tickets, employee confusion, and the kind of HR credibility that takes time to rebuild. Three releases this week, across service desk, HR files, and benefits, address exactly that gap. They form a thread worth following. --- ## The Service Desk Gets Complex. So Does the Need to Preview. The service desk has become the connective tissue of modern workforce operations — IT requests, facilities work orders, HR inquiries, equipment orders. Every category has a form, and those forms have been getting more sophisticated. [Service Desk Conditional Field Logic](https://www.mangoapps.com/changelog/2949), released earlier this week, is a good example of how far form logic has come. Custom fields can now show or require themselves based on complex AND/OR rules spanning multiple fields and values — not just simple single-field equality checks. An IT request form can surface a "network segment" field only when the employee selects "server access" AND "remote work." A facilities form can require a compliance attestation only when the request type is "policy exception" AND the department is in a specific group. This is the right direction. Context-aware forms reduce noise for employees and route cleaner information to the agents handling requests. But sophisticated conditional logic introduces a real operational question: how does an admin know the rules work correctly before deploying them to the entire workforce? [Service Desk Intake Form Live Preview](https://www.mangoapps.com/changelog/2950) answers that directly. Admins can now see exactly how a request type form will appear to end users — including all unsaved edits — before publishing. Every conditional rule, every required field, every help text label, rendered as an employee would see it. This pairing is the right design. Complex configuration is only useful when the person building it has a way to verify the result without going live. Preview does not replace testing, but it eliminates the most common failure mode: the admin who assumed a conditional rule was working, never saw the rendered form from the employee's side, and found out through a support ticket. --- ## HR Files and Benefits Emails: Where Getting It Wrong Has Real Consequences Not every configuration mistake results in a support ticket. Some result in a privacy incident. HR files are among the most sensitive records in any organization — termination letters, performance improvement plans, medical documentation, compensation history. Access rules have to be right. But historically, configuring file permissions has been an act of trust in the data model: select a visibility setting, save it, and assume the permissions logic did what you intended. [HR File Visibility Control](https://www.mangoapps.com/changelog/2947), from earlier in the week, changes the relationship between intent and outcome. Admins now set access with a single, explicit audience choice — Private to HR, Employee Only, Reporting Chain, Specific Roles, or All Employees — and see a live preview of exactly which individuals can view the file before saving. The configuration step and the consequence preview are now the same step. There is no separate permission audit to run, no need to log in as a test employee to verify access. Benefits enrollment carries a similar risk profile — high stakes, low tolerance for error, outcomes that play out in employee inboxes without an undo button. [Benefits Enrollment Email Previews](https://www.mangoapps.com/changelog/2947) lets benefits admins preview the exact email employees will receive for each notification type — rendered with mock data — directly from the settings page, before enabling any sends. This is the kind of feature that sounds minor until you have sent a broken enrollment reminder to 900 employees two days before the deadline closes. The preview is not a nice-to-have. It is the difference between catching a formatting error in staging and catching it in production. Taken together, these three features — service desk form preview, HR file access preview, benefits email preview — reflect a design commitment that is surprisingly rare in enterprise HR software: administrators should be able to see what employees will experience before employees experience it. Configuration UIs and employee-facing UIs have traditionally been built separately, tested separately, and the gap between them has historically been bridged by tribal knowledge, manual testing as a different user, or employee complaints. --- ## A Different Kind of Visibility: When AI Helps You See the Shape of Your Data Preview controls address one kind of uncertainty — will this form look right, will this file be shared correctly, will this email render properly. A different kind of uncertainty is harder: am I even asking for the right things in the first place? The [Interactive Report Builder with AI Suggestions](https://www.mangoapps.com/changelog/2945), also shipping this week, addresses that second question. Managers and admins can now build custom workforce reports using a visual step-by-step builder, with AI-powered suggestions that surface relevant columns and filters as you work. Building a headcount report surfaces tenure, department, and cost center. Analyzing service desk volume brings in request type, resolution time, and assignee load. The design principle here is worth noting: this is not a chat interface. It is ambient assistance inside a configuration task, reducing the gap between what a manager knows they want to understand and what they know how to build. For workforce analytics — an area where most users are not trained analysts — that kind of contextual guidance can be the difference between a report that answers the question and one that answers a slightly different question nobody asked. [Ask AI Multi-Agent Routing](https://www.mangoapps.com/changelog/2951) is the more visible AI headline of the week, with complex questions now routed through a chain of specialized agents for more accurate, domain-specific answers. But the report builder is where AI earns its place in operational workflows: not by replacing human judgment, but by reducing the cognitive overhead of translating intent into configuration. --- ## The Pattern Behind This Week Zoom out from any individual feature and a consistent orientation emerges across this week's releases: they reduce the cost of not knowing. Not knowing who can see a sensitive file. Not knowing how a conditional form will render. Not knowing what email employees will receive on enrollment day. Not knowing which columns belong in a workforce report. Every one of those unknowns has historically required either trusting the configuration, running a manual test as a different user, or waiting for an employee to surface a problem. Each approach works, but none of them are good. They add friction to legitimate administrative work, slow down the deployment of new workflows, and occasionally produce errors with real organizational consequences — a privacy exposure, a confused workforce during open enrollment, a service desk form that routes requests to the wrong team for weeks before anyone notices. For HR and operations leaders evaluating workforce platforms, this is a meaningful signal about how a product is designed. The question is not only whether a system can handle your processes — most modern platforms can. It is whether the people responsible for configuring those processes have enough visibility into what they are building to do that work with confidence. The releases this week at MangoApps move that needle in a direction that matters for the people doing the work. --- # Self-Service Fails When It Stops at the HR Portal **Author:** MangoApps Team **Published:** 2026-04-18 **Category:** employee-experience True self-service means fewer handoffs, not just fewer tickets. Unified, mobile-first workflows reduce friction across HR, frontline, and operations. ## Self-Service Fails When It Stops at the HR Portal Most employee service programs are designed to cut tickets, but that is the wrong success metric. If employees still need three systems, two logins, and a manager’s help to complete a basic task, the organization has not created true self-service — it has simply moved the queue. That is why the market has crowded around “self-service” as a feature while leaving the real problem unsolved: fragmented access. ### The Problem Nobody Talks About The industry keeps treating employee service as a support layer instead of a core way of working. Legacy intranet platforms usually frame it as a place to find policies and forms. Communication-only platforms treat it as a way to deflect HR questions. Frontline-only messaging tools often stop at mobile access to pay, schedules, or time-off requests. Each approach solves one slice of the problem, but none unifies the employee’s actual workflow. That fragmentation matters because employees now expect more than simple FAQs. They want to update personal details, request time off, enroll in benefits, check schedules, view paystubs, and access W-2s from one place. MangoApps has already documented this shift in [Revolutionizing HR With Self-Service Employee Hubs](https://www.mangoapps.com/articles/revolutionizing-hr-operations-the-power-of-employee-self-service-hubs), where the core argument is not “more convenience,” but fewer handoffs, fewer errors, and less manual work. ### What the Data Actually Shows #### 1) It works only when it is mobile-first and role-aware The strongest use cases are not desktop-centric. They are frontline-centric. MangoApps supports an [Employee Self-Service Mobile App](https://www.mangoapps.com) that lets employees check schedules, request time off, swap shifts, view paystubs, and access W-2s from one app. It also supports [HR self-service](https://www.mangoapps.com/articles/revolutionizing-hr-operations-the-power-of-employee-self-service-hubs) for onboarding, benefits enrollment, dependent updates, reviews, payroll approval, and time-off requests. That matters because the workforce reality is not office-only. Most organizations are trying to serve hourly, distributed, and deskless employees who do not live in email or desktop portals. A model that assumes a company-issued laptop is not a real fit for the modern workforce. #### 2) The best systems reduce work, not just questions A strong platform should eliminate repetitive HR transactions and surface the right workflow at the right moment. MangoApps’ approach is designed to centralize HR services and information so employees can update personal details, request time off, enroll in benefits, and access payroll information without HR intervention. It also adds analytics and reporting for workforce trends, operational efficiencies, and compliance risks. That distinction matters because many vendors stop at “information access.” But access alone does not reduce workload. The value comes from automating the process end to end. MangoApps’ own content argues that 24/7 access, secure controlled permissions, and audit trails are what make the model operationally useful — not just easy to use. #### 3) It becomes more valuable when it is part of a broader platform Point solutions can answer a request. Unified platforms can resolve it in context. MangoApps has expanded its native workforce solutions over the past 12–24 months, and that breadth changes the economics of employee service: one login, one data model, one place for HR, communications, tasks, and employee services. The same logic shows up in adjacent workflows. In the [Field Service Suite App Overview](https://www.mangoapps.com/help/field_service_suite_app_overview), MangoApps supports an 8-stage work order pipeline, 6 mobile views, and 5 optional add-on modules. That is evidence that the platform handles complexity best when it is built into a broader system rather than bolted on. The lesson transfers directly to employee service: if the platform can manage field operations, it can also reduce complexity in HR and employee support. ### The Contrarian Insight The market narrative says employee service is about empowerment. The data says it is really about consolidation. Employees do not need more service surfaces; they need fewer places to go. That is the core flaw in the current market. A chatbot that answers a payroll question, a portal that hosts forms, and a mobile app that shows schedules are all useful — but only if they connect to the same system of record and the same workflow engine. Otherwise, the experience becomes another layer of fragmentation. MangoApps’ [Employee Self-Service Assistants Powered by AI](https://www.mangoapps.com/articles/ai-powered-employee-self-service-assistants-in-the-modern-workplace) makes this point clearly: AI is valuable when it routes requests and answers questions in context, not when it adds another disconnected interface. ### What Actually Works: A Unified Approach A unified platform changes the employee experience in two ways. First, it removes the need to bounce between HR, IT, and operations systems. Second, it gives the organization a single place to measure usage, adoption, and friction. That is why MangoApps frames employee service as part of a broader autonomy model in [Boosting Employee Autonomy With AI Self-Service Hubs](https://www.mangoapps.com/articles/enhancing-employee-autonomy-with-ai-powered-self-service-hubs): when employees can update details, view pay slips, apply for leave, enroll in benefits, and access training resources in one platform, the organization gets both efficiency and accountability. Scale matters here as well. MangoApps serves 1M+ users worldwide and brings 15+ years of innovation to the problem. In a category where many vendors are still layering features onto products that were never designed to unify HR, communications, and operations, that matters. The result is not just a better employee experience; it is less tool sprawl, less manual work, and a cleaner path to adoption. ### Call to Action If your employee service strategy still depends on separate tools for HR requests, mobile access, and employee support, it is time to consolidate the workflow, not just the interface. Start by evaluating whether your platform can handle both employee transactions and operational visibility in one system. --- # The Manager Tax: The Hidden Hours Draining Your Frontline **Author:** MangoApps Team **Published:** 2026-04-16 **Category:** workplace-productivity Your best frontline supervisors spend half their day on coordination work no one designed them to do. The compounding cost shows up as turnover — and almost never on the books. It's 6:47 on a Monday morning in a 120-person distribution center. The shift manager — we'll call her Elena — has been at her desk for thirteen minutes. In that time, she has opened three browser tabs and two apps, copied a name from a text thread on her phone into a scheduling spreadsheet, clicked into the HR system to verify whether someone's leave paperwork cleared, and started an email to her regional director that she will not finish until lunch. None of that is her job. Her job is to run the floor for the next ten hours. But by 7:00 a.m., she has already paid the first installment of what we'll call the **Manager Tax** — the hours she loses every day to the coordination overhead her tools force on her. If you operate a frontline business, you are paying this tax. Quietly. Compounding. Almost always off the books. ## The tax is bigger than most executives think The pattern is consistent across the workforce research we read. Frontline supervisors — store managers, shift leads, charge nurses, plant supervisors, branch managers — spend somewhere between 40% and 60% of their day on administrative coordination. Not strategy. Not coaching. Not even firefighting. Just keeping information moving between systems that were never designed to talk to each other. Call it half a manager, per manager, per year. If you have 200 frontline supervisors, you are effectively paying for 100 full-time people to do coordination work instead of leadership work. That is the Manager Tax. And like most taxes, it is invisible because it has been baked into the operating cost for so long that no one thinks to question it. What makes it especially expensive is who is paying it. [Gallup's long-running research on engagement](https://www.mangoapps.com/articles/gallup-2026-state-of-the-global-workplace) is unambiguous on this point: managers account for roughly 70% of the variance in their team's engagement scores. The person you are taxing the most heavily is the single largest driver of whether your frontline workers stay, perform, and recommend you to their friends. The math here is brutal. ## Where the tax comes from It is tempting to blame the people. The supervisors are slow. The store managers are disorganized. The shift leads need better training. We have sat in enough operating reviews to know how that conversation goes. The honest answer is that the Manager Tax is paid by competent people working with incompatible systems. Consider what a typical frontline manager actually has to coordinate in a single shift: - **Who is supposed to be here.** The schedule, often in one tool. Time-off requests, often in another. The text messages from people who can't make it, in a third. - **Who is actually here.** Time clocks, attendance system, a paper sign-in sheet, a manager's mental map of the floor. - **Who is qualified for what.** Training records in the LMS. Certifications in HR. The supervisor's own memory of who learned what last week. - **What needs to get done.** Tasks from corporate. Tasks from the regional manager. Tasks from yesterday's safety walk. Customer complaints that came in overnight. - **Who needs to know what.** Announcements via email some workers don't check. Updates via a messaging app that not everyone uses. A bulletin board most people walk past. Each of those lives in a different system. Each system has its own login, its own search, its own notion of who an employee is. The supervisor is the integration layer. They are the human glue holding together a software stack that nobody designed for them. This is what we mean when we talk about fragmentation. It is not a complaint about software preferences. It is a description of where your operating cost actually goes. ## How the tax compounds A 30-minute coordination loss at the start of a shift looks small. The reason it isn't is that the cost compounds in three directions at once. **It compounds across the day.** That morning half-hour of clicking and copying becomes an hour by lunch and ninety minutes by close — because the systems that didn't talk at 7:00 a.m. still don't talk at 2:00 p.m. The supervisor is rerunning the same coordination work every time something changes, and on a frontline shift, things change constantly. **It compounds across the team.** A supervisor who spends two hours a day on admin is a supervisor who is not on the floor. Not [coaching the new hire](https://www.mangoapps.com/articles/learning-and-development-strategy-embedded-in-daily-work). Not catching the safety issue. Not having the five-minute conversation that keeps a frustrated worker from putting in notice. Workforce research on frontline turnover is consistent here: the single most predictive variable in whether a frontline worker quits in their first ninety days is the quality of their relationship with their direct supervisor. Take time away from that relationship and you are quietly raising your turnover cost. **It compounds across the year.** The supervisor who is taxed at this rate for twelve months in a row is, in our experience, the supervisor who quits. They don't leave because of the pay. They leave because the job they were promoted into — leading people, running operations — is not the job they actually got. The job they got is data entry with a headset. A frontline operation losing 30% of its supervisors a year is not unusual. Replacing each one costs somewhere between half and twice their annual salary, depending on the role and the source you read. None of that shows up on a line item called "Manager Tax." It shows up as recruiting spend, training spend, and the soft cost of underperforming locations while the new supervisor learns the systems. There is a second-order cost that tends to go unmentioned. When a tenured supervisor leaves, they take with them the institutional workarounds that made the fragmented stack survivable in the first place — the spreadsheet they kept on the side, the group text they ran with the night-shift leads, the personal relationship they had with the regional HR coordinator who would unstick paperwork. The new supervisor inherits the tools, not the workarounds. So the Manager Tax doesn't just stay flat when you lose people; it spikes for the next six to nine months while the replacement rebuilds, in private, the same shadow systems their predecessor built. ## What lower-tax operations do differently We have spent enough time [inside frontline operations](https://www.mangoapps.com/resources/raleys-case-study) — retailers, healthcare systems, manufacturers, restaurant groups, distribution networks — to notice a pattern in the ones that have lowered the Manager Tax rather than rationalized it. Three things stand out. **They stopped buying point tools.** The companies with the lowest Manager Tax are not the ones with the best scheduling software. They are the ones who decided, somewhere along the way, that the supervisor's experience was the product they were actually buying. So they stopped optimizing each function — scheduling, communication, training, recognition, compliance — in isolation, and started asking a different question: how many systems does a supervisor have to touch to do one thing? **They measured what they were taxing.** Most companies measure manager output: shifts filled, sales delivered, safety incidents reduced. Almost no one measures manager input — how the supervisor actually spent their time. The operations that have lowered the tax did [the unfashionable work of asking](https://www.mangoapps.com/resources/2026-workforce-operations-trends-ebook), often with a stopwatch, what their supervisors actually do all day. The answers are usually horrifying. They are also the starting point for any real improvement. **They treated the manager experience as a strategic decision, not a software decision.** The companies that took fragmentation seriously didn't delegate the fix to IT. They put it on the operating leader's roadmap. Because the moment you frame the Manager Tax as a productivity loss in the most expensive part of your frontline operation, it stops being an IT discussion and starts being a board discussion. A fourth pattern is quieter but worth naming. The operations that have lowered the tax tend to have a shared, weekly rhythm where supervisors hear directly from leadership — what's changing, what's working, what to watch for. Not a memo, not a town hall. A short, predictable signal that the supervisor's attention is being pointed somewhere intentional, rather than left to be hijacked by whichever tool pinged loudest that morning. It is hard to overstate how much administrative noise a clear weekly priority absorbs. Without it, every system in the stack feels equally urgent, and the supervisor defaults to the inbox. ## What this is really about We have a habit, in our industry, of talking about the frontline workforce as a problem to be solved. Engagement is too low. Turnover is too high. Productivity is leaking. The next product, the next survey, the next training module will fix it. The data keeps suggesting otherwise. The frontline workforce is not the problem. The supervisor is not the problem. The problem is the quiet, daily, compounding decision to keep buying coordination tools that don't coordinate — and then expecting the people in the middle to absorb the cost. Elena, the shift manager from the opening of this piece, is not unusual. She is the median. And the question worth sitting with is not how to make her faster at the work she shouldn't be doing. It's how much of that work she should be doing at all. The companies that answer that question honestly are the ones whose frontline operations quietly start to work better — not because they hired better people, but because they finally stopped taxing the ones they had. --- # Why Your Learning and Development Strategy Fails (and How to Fix It) **Author:** MangoApps Team **Published:** 2026-04-13 **Category:** learning-management Most L&D programs fail because training lives outside daily work. Learn how embedding learning into your intranet, career planning, and peer networks drives real adoption and retention. Most learning and development programs do not fail because the content is bad. They fail because the system is wrong. When training lives in a separate portal with its own login, its own search, and its own navigation, the organization is not scaling learning. It is scaling friction. Employees have to leave their actual workflow, remember where to go, and somehow find motivation to engage with a system that has nothing to do with the rest of their workday. Nearly [72% of organizations](https://www.shiftelearning.com/blog/statistics-value-of-employee-training) believe eLearning gives them a competitive edge. Yet most still treat learning as a standalone function, disconnected from the tools employees already use for communication, tasks, and daily operations. That gap between belief and execution is where adoption goes to die. MangoApps approaches this differently. Instead of building learning as an isolated module, the [MangoApps Learning Management System](https://www.mangoapps.com/training-hub) is embedded directly into the employee intranet. Training is part of the same environment where employees check announcements, access knowledge bases, manage tasks, and connect with their teams. ## The Real Problem Nobody Wants to Admit The corporate learning market has poured investment into course libraries, certification tracking, and content authoring tools. That is the visible part. The invisible part, the part that actually determines whether anyone completes training, has been underfunded for years: the conditions that drive adoption. This is why so many learning platforms demo well and underperform in production. They can host courses. They cannot make courses part of how work gets done. The pattern repeats across platform categories. Legacy intranet vendors bolt on learning modules that feel like afterthoughts. Communication-only platforms push training announcements with no connection to follow-through. Point solutions manage courses in isolation, cut off from managers, mentors, and the operational context that makes training stick. The result for employees: another system to manage, another login to remember, another place to check that has nothing to do with how they spend their actual day. And for organizations with [frontline and deskless workers](https://www.mangoapps.com/unified-intranet-employee-app), the problem is worse, because those employees often lack a desk, a company email, or consistent access to anything beyond their phone. ## What the Research Actually Shows ### 1. Learning Adoption Increases When Training Lives Where Work Happens This one is straightforward. When employees have to leave their workflow to access training, completion rates drop. When training is embedded in the same platform they already use for daily work, it gets finished. MangoApps' [learning management approach](https://www.mangoapps.com/training-hub) is built into the [AI-powered intranet](https://www.mangoapps.com/platform), which means a course assignment shows up in the same environment as a shift schedule, a company announcement, or a knowledge base article. There is no second destination. That matters most for distributed organizations where employees move between desktop and mobile throughout the day. [MangoApps' mobile app](https://www.mangoapps.com/unified-intranet-employee-app) supports mobile learning, auto-enrollment, and progress tracking from a phone, so a warehouse associate, a retail store manager, or a traveling nurse can complete training without sitting at a desktop. With 2M+ users on the platform and 15+ years of building enterprise workforce tools, MangoApps has seen firsthand that learning systems do not fail on content quality alone. They fail when employees stop coming back. ### 2. Career Development Is a Retention Strategy, Not a Training Feature A learning program that ends at course completion misses the outcome most leaders actually care about: keeping people. The data is direct. [94% of employees](https://www.linkedin.com/learning/resources/workplace-learning-report) say they would stay at a company longer if it invested in their career development. That is not a soft engagement metric. It is a warning that underdeveloped employees are already looking for jobs elsewhere. MangoApps' [Performance Management](https://www.mangoapps.com/solutions/performance-management) and development planning tools turn that insight into an operating model. Employees get AI-generated career roadmaps based on their role, skills, gaps, and goals. Managers and employees share ownership through comment threads, review cycles, and coaching feedback loops, all inside the same platform where daily work happens. The difference between this and a static annual review is significant. MangoApps customers report 3x higher engagement among employees with structured development plans. That tracks with what you would expect: when learning connects to goals, milestones, and manager accountability, people engage. When it is left as optional self-service, they do not. ### 3. Peer Learning Scales Faster Than Content Production One of the biggest blind spots in corporate learning is the assumption that all knowledge should come from formal courses. In reality, every organization already has deep expertise inside the business. The problem is not a lack of knowledge. It is a lack of systems to capture and distribute it. Consider that [74% of employees](https://www.cipd.co.uk/knowledge/strategy/development/learning-at-work) say they are not reaching their full potential. If internal expertise is invisible, unsearchable, and locked in individual people's heads, the organization keeps paying to solve the same problems over and over. MangoApps' [Skill Swap](https://www.mangoapps.com/key-features/skill-swap) addresses this by creating an internal marketplace for peer learning, mentorship, and skill sharing. Employees can list their skills, find mentors, schedule sessions, and track outcomes of knowledge-sharing activities. It connects directly to the LMS so peer learning appears alongside formal course completions in each employee's development profile. The impact is measurable. Access to mentorship is associated with 2.5x higher retention. Structured peer learning can improve job performance by 25%. Compare that to a static course catalog where the same five people finish training and everyone else forgets it exists. ## The Contrarian Insight Most Vendors Ignore The industry keeps framing learning and development as a content problem. Build more courses. Record more videos. License more libraries. It is not a content problem. It is a systems problem. The real constraint is not whether an organization can produce more training material. It is whether employees can find the right knowledge, apply it in the context of their actual job, and connect what they learn to their career growth. That requires integration across learning, communication, knowledge management, and [performance management](https://www.mangoapps.com/solutions/performance-management), not just a better course player. Standalone LMS tools often underperform in practice because they manage learning events in isolation. They do not connect training to onboarding workflows, compliance deadlines, [peer expertise](https://www.mangoapps.com/key-features/skill-swap), or career planning. The learning lives in one system. Everything else lives somewhere else. And the employee is expected to stitch it all together on their own. The data points the other way. Employees want development (94% say so). Managers need visibility into who is growing and who is stalling. Organizations need measurable outcomes. A learning program that is disconnected from the broader employee experience is less likely to be used, remembered, or tied to performance. ## What a Unified Approach Actually Looks Like A unified platform changes the economics of learning. Instead of asking employees to jump between systems, MangoApps brings [learning management](https://www.mangoapps.com/training-hub), development planning, [peer mentoring](https://www.mangoapps.com/key-features/skill-swap), [onboarding](https://www.mangoapps.com/apps/onboarding), and internal communication into one environment. In practice, that means: - A new hire gets auto-enrolled in training on day one, inside the same app where they access their schedule and meet their team. - A manager tracks development milestones without logging into a separate system. - A subject matter expert publishes internal knowledge that shows up in search results alongside formal courses. - A frontline employee completes compliance training from a phone during a break, with progress tracked automatically. This is the difference between managing training and building a learning culture. Mobile-friendly content, quizzes, certificates, and bite-sized courses matter. But the bigger advantage is distribution: learning reaches employees where they already work, on the device they already carry, inside the platform they already use. With [200+ enterprise integrations](https://www.mangoapps.com/platform), [skills management and certification tracking](https://www.mangoapps.com/key-features/skills-management), and native workforce operations tools for scheduling, tasks, and communication, MangoApps treats learning as part of a unified employee system that scales across roles, shifts, and locations. ## The Question Worth Asking If your learning strategy still depends on a separate portal, a separate login, and employees remembering to go there, ask a harder question: are you building capability, or just hosting content? Evaluate whether your learning platform can connect training, peer expertise, development planning, and daily work in one system. That is where adoption, retention, and real business outcomes are won. [See how MangoApps brings learning into daily work →](https://www.mangoapps.com/training-hub) --- # Gallup's 2026 State of the Global Workplace: What It Means for HR, IT, and Operations Leaders **Author:** The MangoApps Team **Published:** 2026-04-13 **Category:** industry-insights Gallup just dropped its annual State of the Global Workplace report — and the numbers should make every HR and operations leader stop and think. Global engagement is at its lowest point since the pandemic lockdowns of 2020. Manager burnout is accelerating. And the economic cost of all this disengagement? Over $10 trillion. Here's what you need to know — and what you can actually do about it. *Gallup just dropped its annual State of the Global Workplace report — and the numbers should make every HR and operations leader stop and think. Global engagement is at its lowest point since the pandemic lockdowns of 2020. Manager burnout is accelerating. And the economic cost of all this disengagement? Over $10 trillion.* *Here's what you need to know — and what you can actually do about it.* ## The headline: engagement is falling, and it's not slowing down Gallup's 2026 report, released this week, finds that global employee engagement fell to 20% in 2025 — down from a peak of 23% in 2022. That's three consecutive percentage points lost in three years, and the first time Gallup has ever recorded two straight years of decline. To put that in perspective: each percentage point of global engagement represents roughly 21 million workers. So that three-point drop isn't an abstract trend — it's tens of millions of people who've psychologically checked out of their jobs since 2022. No region of the world saw engagement increase last year. Not one. The decline was global and universal. And the economic toll is enormous. Gallup estimates that disengagement cost the world economy more than $10 trillion in lost productivity in 2024 alone — the equivalent of 9% of global GDP. ## The root cause: managers are breaking down If there's one through line in this year's report, it's this: the manager crisis is now the workforce crisis. Since 2022, manager engagement has dropped nine percentage points. The largest single-year decline hit between 2024 and 2025, when manager engagement fell five points — from 27% to 22%. Individual contributor engagement, by comparison, has held relatively steady. Managers used to enjoy what Gallup calls an "engagement premium" — they were meaningfully more engaged than the people they led. That premium has essentially vanished. Managers are now only about as engaged as the individual contributors on their teams. This matters because of one of Gallup's most consistent findings: [managers account for 70% of the variance in team-level engagement](https://www.mangoapps.com/articles/overcoming-obstacles-in-employee-engagement/). When managers disengage, their teams follow. And when teams disengage, productivity, retention, and customer outcomes all suffer. Young managers (under 35) and female managers have been hit hardest. In South Asia — primarily India — manager engagement dropped eight points in a single year, the steepest regional decline. Gallup notes that the number of managers in India also shrank, suggesting organizations are cutting management layers, potentially driven by AI adoption and restructuring. Fewer managers, larger teams, less support. ## Why are managers burning out? The report paints a clear picture: managers have been absorbing the full weight of post-pandemic disruption with inadequate support. Think about what managers have navigated in the past five years: post-pandemic turnover and a hiring boom-and-bust cycle, digital transformation and the rapid introduction of AI tools, new employee expectations around flexibility and remote work, restructured teams and departments on shrinking budgets, disrupted supply chains and new customer demands. Managers sit at the intersection of executive expectations and employee needs — and those two forces have been moving further apart for years. The report's CEO quote from Gallup's Jon Clifton makes the point sharply: companies are pouring money into AI, but the results aren't showing up in the bottom line. The missing link, according to Gallup's data, is the manager. ## The "Great Detachment" is real — especially in the U.S. Gallup's data aligns with a broader pattern that's been building for months: the "Great Detachment." Workers aren't necessarily quitting — the job market has tightened. But they're psychologically checked out. In the U.S. and Canada, the numbers tell a sobering story. At 31%, the region still has the highest engagement rate in the world. But U.S. employee engagement fell to 32% (with Canada at 21%), and job optimism dropped sharply. Only 28% of U.S. workers in Q4 2025 said it was a good time to find a quality job — down from 70% in mid-2022. Workers are applying for jobs but not hearing back. They feel stuck. And when you combine that stagnation with low engagement, you get a workforce that's present but not performing — what Gallup calls "quietly quitting." For employers in industries like healthcare, retail, hospitality, and manufacturing — where [frontline workers make up the majority of the workforce](https://www.mangoapps.com/solutions/employee-app) — this dynamic is especially dangerous. You can't afford a disengaged floor nurse, store associate, or shift supervisor. The ripple effects hit patients, customers, and safety outcomes directly. ## Wellbeing improved globally — but not where you'd expect There's a small bright spot in the report: global employee wellbeing ticked up slightly for the first time in three years, with 34% of employees now classified as "thriving." But in the U.S. and Canada, the opposite happened. Just 51% of employees are thriving — a new low for the region and one of the steepest declines worldwide since the pandemic. For the first time since Gallup began tracking, more U.S. workers are struggling than thriving. Higher-level leaders report the highest engagement and wellbeing, but they're also more likely to experience daily stress, anger, sadness, and loneliness. The weight of leadership is showing up in the data. For [HR and internal communications leaders](https://www.mangoapps.com/articles/everything-about-employee-engagement), this creates a difficult calculus: you're responsible for supporting employee wellbeing across the organization, but the people in the best position to deliver that support — your managers and senior leaders — are themselves struggling. ## AI is here, but managers are the unlock One of the most timely findings in the report is the connection between AI adoption and manager support. Gallup's U.S. data shows that employees whose managers actively support AI use are more than twice as likely to use it frequently. Only about 26% of employees say their organization has communicated a clear plan for integrating AI, and just 30% say their manager supports AI use at work. This is a critical insight for IT and operations leaders evaluating tools like [enterprise AI assistants](https://www.mangoapps.com/ai). Technology alone doesn't drive adoption — managers do. If your AI rollout strategy doesn't include equipping managers to model, explain, and support the tools, adoption will stall regardless of how good the technology is. Gallup CEO Jon Clifton's framing is direct: this report establishes a global baseline for management effectiveness in the AI era. Businesses are investing heavily in AI, but the returns won't materialize without investing equally in the people who translate strategy into daily action. ## What Gallup says organizations should do The report outlines three actions for leaders, and they all center on the same theme: invest in your managers. **First, ensure all managers receive training.** Less than half of the world's managers say they've received any management training at all. Gallup's data shows that trained managers are half as likely to be actively disengaged as untrained ones. Even basic role training — the fundamentals of what the job requires — can prevent a manager from feeling like they're drowning. **Second, teach managers how to coach.** Gallup found that participants in manager coaching programs saw up to 22% higher engagement, their teams saw up to 18% higher engagement, and manager performance metrics improved between 20 and 28%. These effects persisted nine to 18 months after training. **Third, support ongoing manager development to improve wellbeing.** Training alone gets manager thriving from 28% to 34%. But when managers also have someone at work who actively encourages their development, thriving jumps to 50%. Manager development may be the single most effective wellbeing initiative an organization can fund. ## What this means if you're evaluating workforce platforms If you're an HR, IT, or operations leader reading this report, a few implications stand out. **The scattered toolset is part of the problem.** When managers are already overwhelmed, forcing them to toggle between eight different apps to schedule shifts, communicate with their teams, track tasks, and access HR resources just compounds the burnout. The engagement crisis isn't just about culture — it's also about the daily friction of doing the job. This is exactly why organizations are looking to consolidate their stack with a [unified workforce platform](https://www.mangoapps.com/platform) that puts communication, operations, HR, and AI in one place. **Frontline workers are disproportionately affected.** The global workforce is roughly 80% frontline and deskless — yet most workplace tools are still built for knowledge workers at desks. When Gallup talks about managers drowning in competing demands, a significant number of those managers are frontline supervisors managing shift workers with no company email, no access to the intranet, and no way to participate in the systems their desk-based colleagues take for granted. A [branded mobile employee app](https://www.mangoapps.com/solutions/employee-app) that reaches every worker — on the floor, in the field, on the move — isn't a nice-to-have anymore. It's a baseline requirement for engagement. **AI adoption depends on manager enablement, not just deployment.** If your AI strategy is "buy the tool and hope people use it," Gallup's data says you're going to be disappointed. The organizations getting real results are the ones where [AI assistants are embedded into the daily workflow](https://www.mangoapps.com/ai) and managers are equipped to guide their teams through adoption. That means AI that lives inside the intranet employees already use — not another standalone tool to learn. **Recognition and communication are foundational.** Gallup's Q12 framework — the engagement model underlying all of this research — includes fundamentals like knowing what's expected, receiving recognition, and having someone who cares about your development. These aren't complex interventions. They're the basics. But delivering them consistently across a distributed, multi-shift workforce requires [internal communications infrastructure](https://www.mangoapps.com/articles/tips-to-improve-frontline-employee-engagement) that actually reaches everyone — not just the people who check email. **Measurement matters.** You can't fix what you can't see. Gallup's report is a global benchmark, but the real work happens at the organizational level — running engagement surveys, tracking participation, measuring reach, and acting on what you learn. [MangoApps' engagement and reach analytics](https://www.mangoapps.com/analytics-insights) give leaders visibility into how their workforce is actually interacting with the platform, so they can spot disengagement early and intervene before it spreads. ## The bottom line Gallup's 2026 report isn't just a data release — it's a warning and an opportunity. The warning is clear: disengagement is deepening, managers are in crisis, and the economic costs are staggering. But the opportunity is equally clear: organizations that invest in their managers, unify their employee experience, and equip their entire workforce with the tools and support they need can break the cycle. The data shows that when you get engagement right, the outcomes are transformational — higher productivity, lower turnover, better customer outcomes, and a workforce that actually wants to show up. MangoApps exists to help organizations make that shift: one platform for every employee, every tool, every team. **[See how MangoApps can help your organization reverse the engagement decline →](https://www.mangoapps.com/platform)** *Source: Gallup, Inc. (2026). State of the Global Workplace: 2026 Report. All data referenced in this article is drawn from the 2026 edition of Gallup's annual State of the Global Workplace report, based on surveys of 141,444 employed respondents across 140+ countries and territories.* --- # The Store Manager’s Playbook for Smarter Retail Scheduling **Author:** MangoApps Team **Published:** 2026-04-13 **Category:** industry-use-cases Learn how mobile-first scheduling helps store managers fill shifts faster, reduce confusion, and keep the floor running smoothly. ## Retail Scheduling Starts on the Store Floor, Not in a Spreadsheet At 7:12 a.m., the store manager is already behind. A callout came in before opening, the weekend promotion changed overnight, and three associates are asking the same question from different corners of the store: "Which schedule is current?" On the screen, there are text messages, a printed schedule taped to the back office wall, and a spreadsheet someone updated two days ago. None of them agree. The manager knows that if the wrong person opens the wrong department, the first hour of the day will be spent fixing avoidable mistakes instead of serving customers. That is the real cost of retail scheduling when it lives in fragments. The issue is not just filling shifts. It is that scheduling sits downstream from communication, training, and store operations, while store managers are expected to hold all of it together manually. When associates miss updates, rely on word-of-mouth, or cannot access the same information from the stockroom and the sales floor, the schedule becomes a symptom of a larger operating problem. For retail organizations, that problem is expensive. The industry already operates with [high turnover](https://blog.mangoapps.com/retail-employee-engagement-strategies/), seasonal churn, and constant changes in staffing demand. Gallup estimates that replacing a single frontline worker costs roughly 40% of their salary — and that compounds across every location, every quarter. Add disconnected tools, and managers spend hours each week on rework: chasing confirmations, answering the same questions, and resolving conflicts that should never have reached the floor. [MangoApps](https://www.mangoapps.com/solutions/shifts-schedules) is built around a different premise: scheduling works better when it is part of one [AI-powered unified workforce platform](https://www.mangoapps.com/platform), not a standalone task buried inside a stack of disconnected systems. ## The Hidden Cost of a Schedule That Lives Outside the Store A store manager who spends 30 minutes every morning reconciling shifts is not "just busy." Over a week, that is 2.5 hours lost to administrative cleanup. Over a year, it is more than 130 hours — the equivalent of more than three full workweeks spent on work that does not improve sales, service, or team performance. That time loss compounds when schedules are disconnected from onboarding and communication. If a new associate does not see the latest shift rules, if a part-time worker misses a swap request, or if a department lead is working from an outdated version of the roster, the store pays twice: once in manager time and again in service inconsistency. McKinsey research shows that retail frontline workers cite "lack of career development" as the top reason for quitting — but the daily reality is more mundane. People leave when the basics feel broken: when schedules are unpredictable, when communication is one-way, and when the tools they are given do not work for how they actually work. In retail, where customer experience is shaped by whether the right people are in the right place at the right time, a broken scheduling workflow becomes an operational drag on the entire business. ## A Day in the Store Manager Workflow ### 1. The morning starts with one source of truth, not three conflicting versions **What used to happen:** The store manager opened the day by checking texts, email threads, and a printed schedule that may already be outdated. If a shift changed overnight, the only reliable way to confirm it was to call or message people individually. **What happens now:** The manager opens one mobile experience to review the day's staffing picture, see who is scheduled, and identify gaps before the store gets busy. Because the schedule sits inside the broader [unified workforce platform](https://www.mangoapps.com/platform), associates access the same information from the same place they use for communication and other store updates. That eliminates the gap where a change lives in one system while the team is still looking at another. As one retail store manager at [A.S. Watson Benelux](https://www.mangoapps.com/resources/communicating-employee-schedules) put it: "They can open the app, click on the schedule, and see when they have to work. They never contact me anymore with questions. It saves me a lot of time." A.S. Watson now communicates schedules to more than 20,000 retail employees weekly through the MangoApps [mobile app](https://www.mangoapps.com/solutions/employee-app) — no company email required. **The measurable difference:** Fewer schedule disputes and less time spent reconciling versions means the manager gets back hours each week that would otherwise disappear into manual coordination. ### 2. Open shifts are handled as an operational task, not an emergency **What used to happen:** When someone called out, the manager started a chain of texts, calls, and favors. The first people contacted were often not the right people, and the process depended on who happened to answer first. **What happens now:** Open shifts are managed inside the same platform where associates already receive store communication and updates. MangoApps' [AI-powered scheduling](https://www.mangoapps.com/solutions/shifts-schedules) goes further: the Shift Marketplace lets associates pick up, drop, or trade shifts from any device, with automated approval rules that preserve compliance and eliminate the need for manager involvement on routine swaps. The AI Smart-Schedule Builder can also factor in skills, certifications, availability, and labor rules to recommend coverage options — so the manager is not starting from zero every time someone calls out. **The measurable difference:** Faster shift coverage reduces the chance that a callout turns into a service gap, and it cuts the manager's response time from a manual scramble to a structured process. Fairness scoring built into the scheduling algorithm helps distribute shifts without bias, creating a transparent system that associates trust. ### 3. Schedule changes reach associates where they actually work **What used to happen:** A schedule update might be posted in the back office, mentioned in a huddle, and sent by text — and still missed by the associate who needed it most. Store teams without regular desktop access were especially vulnerable to missing changes. **What happens now:** Associates check their schedules from a [mobile experience](https://www.mangoapps.com/solutions/employee-app) built for the realities of retail work. Many store employees do not sit at a desk, do not live in email, and do not have time to hunt for updates across multiple tools. When schedule information is delivered in the same mobile environment as other store communications — alongside push notifications and real-time alerts — it becomes far easier to keep everyone aligned. **The measurable difference:** Better visibility means fewer no-shows, fewer "I didn't see the update" moments, and less time spent re-explaining the same change to multiple people. MangoApps customers consistently achieve [90%+ adoption rates](https://www.mangoapps.com/platform) within 90 days, which means the schedule actually reaches the people it is meant for. ### 4. Scheduling connects to the rest of store operations **What used to happen:** Scheduling was treated as a separate administrative task, disconnected from training, policy updates, and store tasks. That meant a manager could build a schedule without knowing whether the team had seen the latest SOP change or completed the required onboarding steps. **What happens now:** Because MangoApps unifies communication, [learning](https://www.mangoapps.com/articles/enhancing-retail-staff-training-with-technology), and workforce operations in one platform, the manager works from a more complete picture of the store. A schedule is no longer just a roster; it is part of how the store organizes readiness. If a new associate needs to be [onboarded](https://www.mangoapps.com/resources/mangoapps-employee-onboarding-tools), if a policy changes, or if a task needs to be completed by a specific role, the manager is not stitching together separate systems to make it happen. **The measurable difference:** When scheduling is tied to the same platform as training and operational communication, the store reduces the risk of assigning the wrong person to the wrong task and improves day-one readiness for new hires. MangoApps customers report 40% faster employee onboarding when everything lives in one place. ## Why This Matters Beyond the Schedule Retail leaders often talk about labor as a cost center. That framing is too narrow. Labor is the mechanism through which the customer experience is delivered. If schedules are inaccurate, if associates miss updates, or if managers spend too much time on manual coordination, the store feels it immediately: slower service, uneven execution, and more pressure on the people who are already stretched thin. Gallup's research reinforces this: engaged teams deliver 18% higher sales and 10% higher customer ratings. But engagement does not come from an annual survey. It comes from whether people can access their schedule, whether they feel informed, and whether the tools they use every day actually work. This is where a unified platform changes the economics. MangoApps brings scheduling into the same environment as [communication](https://www.mangoapps.net/industries/retail), learning, and store operations — so the store manager is not forced to manage each problem in isolation. That is especially relevant in retail, where mobile access and frontline usability matter more than another desktop tool that only corporate can fully use. The broader market is already proving the value of consolidation. Retail organizations such as PetSmart (50,000+ associates), AutoZone (125,000 employees), and Raley's (20,000 employees) chose MangoApps because their workforce reality is mobile, distributed, and operationally complex. The common thread is not just communication. It is the need for one system that can support the store floor, the stockroom, and the corporate office without forcing associates to jump between disconnected tools. ## Getting Started: What Retail Leaders Should Evaluate A scheduling pilot should not begin with a feature checklist. It should begin with the daily friction your store managers actually face. Here are the signals that matter: **Can associates access schedules from mobile without a company email?** If not, the tool will miss a large share of the retail workforce. MangoApps does not require an email address, a VPN, or a desktop to work. **Can schedule changes live in the same place as store communication and updates?** If the answer is no, managers will keep reconciling multiple sources of truth — and the rework never stops. **Does the platform use AI to reduce manual scheduling work?** If the manager is still building every schedule by hand, the tool is not solving the right problem. AI-powered scheduling that balances demand, skills, compliance, and fairness is now table stakes for frontline operations. **Can the platform support role-based access across stores, departments, and locations?** Retail scheduling is rarely one-size-fits-all. Look for configurable permissions and multi-location support. **Does the workflow reduce manager follow-up time on callouts, swaps, and confirmations?** The real test is whether it removes manual chasing — not whether it adds another notification layer on top of existing chaos. **Can you pilot it with one store or region and measure time saved, coverage speed, and associate visibility?** MangoApps typically implements in 8–12 weeks, and the pilot should show operational impact fast. If it cannot, it is not solving the right problem. The best evaluation question is simple: does the platform help the store manager spend less time managing the schedule and more time running the store? A schedule taped to the back office wall is a reminder that the work is still fragmented. A schedule inside one connected workforce platform is a reminder that the store can run on something better. [See how MangoApps brings scheduling, communication, and training together for retail teams →](https://www.mangoapps.com/solutions/shifts-schedules) --- # Getting Frontline Workforce Compensation Right at Scale **Author:** MangoApps Team **Published:** 2026-04-12 **Category:** workforce-management A union contract is ratified six weeks after its effective date. Retroactive to January. # Getting Frontline Workforce Compensation Right at Scale A union contract is ratified six weeks after its effective date. Retroactive to January. Hundreds of employees across four locations, each with different roles, different shift patterns, some in temporary acting assignments covering positions above their base classification. A few just crossed the tenure threshold that triggers employer pension matching. Someone in HR has to apply all of it accurately — before the next payroll run. This is not an unusual situation. In organizations with hourly workers, collective bargaining agreements, shift-based schedules, and layered benefit plans, "compensation" is rarely a single number. It is a stack of rules, premiums, eligibility criteria, and time-sensitive adjustments — many of which interact in ways that only become visible when something shows up wrong on a paycheck. The challenge isn't that organizations don't know what they owe workers. Most do. The challenge is that the systems designed to track and apply that information were built for simpler structures. --- ## Acting Pay and Shift Differentials Are Compensation Commitments When a warehouse supervisor steps up to cover an absent operations manager for three weeks, the organization is asking more of them. Acting pay exists to reflect that. When a worker takes the overnight shift or comes in on a holiday weekend, shift differentials exist to reflect that too. These aren't incidental details — they're negotiated or policy-driven commitments that employees reasonably expect to appear on their paycheck. The practical problem is consistent application. A manager at one location knows the internal process for logging an acting assignment. A different manager at a different site handles it differently, or doesn't know to flag it at all. Payroll receives an export, someone tries to reconcile it, and the employee who was supposed to receive acting pay for three weeks is still waiting — and quietly drawing conclusions about how much the organization pays attention. MangoApps added [Temporary Premiums for Acting Pay and Shift Differentials](https://www.mangoapps.com/changelog/2939) this week, letting managers configure pay rules for both shift differentials and temporary role elevations, with auto-application and itemized breakdowns that flow directly into payroll exports. The point of this isn't just automation for its own sake — it's consistency. When premium rules are defined once and applied by the system, the outcome doesn't depend on which manager remembered to enter something in the right field. The same week brought [Retroactive Bulk Compensation Changes](https://www.mangoapps.com/changelog/2941): the ability to apply backdated compensation updates across many employees at once, with background processing for large batches. For organizations navigating the gap between when a contract is ratified and when payroll can reflect it, this removes what has historically been a tedious, error-prone spreadsheet exercise. Retro pay after a contract cycle closes is a known obligation — the question is how much manual work it generates, and how much room for error exists in that process. --- ## Benefits and Pension Are Also Pay Most workforce systems handle base wages reasonably well. Benefits get treated as a separate function — managed in a different module, governed by eligibility rules tracked informally, reconciled quarterly when someone notices a discrepancy. The separation feels natural administratively, but from an employee's perspective, their pension match and their health plan eligibility are part of what they were told they'd receive when they took the job. Eligibility logic is where the complexity lives. An employee becomes eligible for the employer pension match after 90 days of continuous service. Does the system know when they hit that threshold? Does someone manually check? If the employer's matching formula includes an annual cap, who ensures it's enforced consistently across payroll periods? If a benefit plan applies to full-time employees but not part-time, and the definition of full-time is based on average hours over a rolling quarter, does the eligibility engine account for that — or does someone in HR have to figure it out each enrollment cycle? [Benefit Plan Eligibility Rules](https://www.mangoapps.com/changelog/2942) allows admins to define exactly who qualifies for each plan — by employment type, department, location, tenure, age, job title, or pay grade — with a live eligible-employee list that updates dynamically and automatic enrollment notifications when criteria are met. The goal is to make eligibility a policy question decided once at the admin level, rather than an operational question that resurfaces every cycle. [Pension Eligibility and Contribution Tracking](https://www.mangoapps.com/changelog/2940) goes further: admins can configure employer contribution formulas (fixed percentage, matching, or fixed dollar), track contributions per pay period with year-to-date summaries, enforce annual caps, and run reconciliation reports. Employees can view their own contribution history directly. The transparency matters as much as the calculation accuracy — an employee who can see their pension contributions is not relying on faith that the matching is being applied correctly. Together, these features treat benefit administration not as a paperwork function but as a compensation accuracy function. When pension matching is miscalculated for three months before someone catches it, that is not a minor administrative error. It is a pay shortfall that compounds quietly and surfaces as a surprise — the worst kind. --- ## The Cost of Approximate Payroll There is a common shortcut in workforce software design: handle base wages well, and treat everything else — differentials, premiums, retroactive adjustments, pension matching — as configuration work that HR can manage offline. The problem with that approach is that "offline" usually means spreadsheets, manual verification, and institutional knowledge held by whoever has been doing it the longest. That knowledge is not documented, not auditable, and not transferable. Frontline workers notice when their pay is wrong faster than desk workers do, because the paycheck is often the most direct signal they receive about how the employment relationship is working. When a night-shift differential doesn't appear, or acting pay doesn't show up, or pension contributions don't start when they should have, the employee's interpretation is simple: either the organization doesn't have it together, or the organization doesn't care. Neither builds trust. The features MangoApps released this week are not individually dramatic. There is no headline-grabbing capability and no new product category. What they represent is a different kind of investment: building the infrastructure that makes total compensation accurate, consistently, across the full complexity of frontline work — without requiring a team of specialists to manually reconcile everything before every payroll run. When that infrastructure is in place, HR teams spend less time chasing discrepancies and more time on the work that actually shapes the employment relationship. And workers stop noticing the gaps. --- *For the full list of what shipped this week, see the daily changelogs for [April 6](https://www.mangoapps.com/changelog/2939), [April 7](https://www.mangoapps.com/changelog/2940), [April 8](https://www.mangoapps.com/changelog/2941), and [April 9](https://www.mangoapps.com/changelog/2942).* --- # MangoApps Wins Gold in Reworked's 2026 IMPACT Awards for Excellence in Intranet & Communications Platforms **Author:** Andy Tolton **Published:** 2026-04-07 **Category:** news-and-updates MangoApps has won the Gold award for Excellence in Intranet & Communications Platforms in Reworked's 2026 IMPACT Awards. **ISSAQUAH, WA - April 7, 2026 -** MangoApps, the AI-Powered Unified Workforce Platform, today announced that it has won the Gold award for Excellence in Intranet & Communications Platforms in Reworked's 2026 IMPACT Awards. The award, presented by Reworked, honors vendors for the exemplary nature of their products, platforms and solutions, as well as the work they've done on behalf of their clients. The recognition reflects MangoApps' commitment to solving a persistent challenge in the digital workplace: most intranet platforms were built for desk workers, leaving the 80% of the global workforce that is frontline or deskless behind, per Emergence Capital. MangoApps was built differently, as a unified employee hub combining intranet, communications, knowledge management, AI assistance, and frontline operations in a single mobile-first platform. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent context on how the category is being evaluated by analysts this year. "Awards like this one are ultimately a reflection of our customers," said Anup Kejriwal, CEO and Founder of MangoApps. "They challenge us to build better, and this recognition is a testament to the outcomes they've achieved. We're honored and motivated to keep delivering." ## What the Judges Evaluated The Reworked IMPACT Awards judging panel — led by Reworked Editor-in-Chief Siobhan Fagan and composed of practitioners and industry specialists — assessed nominees across dimensions including deployment flexibility, adoption potential, integration breadth, and AI personalization. These criteria reflect the same framework enterprise buyers now apply when selecting an intranet platform. MangoApps was evaluated against competing platforms in the intranet and employee communications category, with winners selected based on information provided through the nomination process. For the full list of 2026 IMPACT Award categories and winners, visit Reworked.co. ## Why Adoption and Access Were Central to the Award The intranet access gap is well-documented: per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use one daily. Per IDC, employees spend an average of 2.5 hours per day searching for information — a direct cost of fragmented or inaccessible intranet tools. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools, a benchmark that underscores how much room exists for platforms that prioritize frontline reach and daily utility. MangoApps addresses this gap through its [modern intranet](/solutions/modern-intranet) architecture, which is built mobile-first and designed for workers who are rarely at a desk. The platform's [company portal](/key-features/company-portal) and [department sites](/key-features/department-sites) give every team — from corporate to the shop floor — a structured home for information, without requiring employees to navigate a separate system. ## Customer Outcomes That Reflect the Award The award claim is grounded in named customer results. OU Health achieved 87% workforce engagement within months of launching a branded employee app on MangoApps. Closing the intranet access gap also carries direct financial stakes: replacing a single frontline employee costs between $4,400 and $15,000 on average, making engagement and retention a measurable return on intranet investment. Over the past two years, MangoApps has shipped innovations that set it apart. The platform enables organizations to build secure, permission-aware AI Agents trained on their own internal knowledge, living inside the employee hub rather than bolted on as a third-party chatbot. MangoApps also introduced AI that generates intranet assets including Pages, Trackers, and Forms from a plain-language prompt — condensing hours of configuration into minutes, not months. The [webpage builder](/key-features/webpage-builder) reflects this time-to-value approach, allowing teams to stand up structured intranet content without IT involvement. For communications leaders, new capabilities including an editorial calendar, AI-powered translation across 50+ languages, digital signage integration, and click-map analytics give internal teams the same precision marketing teams have always had, extended to employees in break rooms, on shop floors, and in the field. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are applying these capabilities at scale. ## What This Award Means for MangoApps Customers For organizations currently evaluating or running an intranet platform, the Gold IMPACT Award provides third-party validation that MangoApps meets the bar set by practitioners and industry specialists — not just vendor marketing. The judging criteria map directly to the questions buyers ask: Can this platform reach frontline workers? Does it integrate with existing HR and operations systems? Can it be deployed and adopted quickly? Does the AI operate within secure, permission-aware boundaries? MangoApps answers each of those questions through its unified platform design. Organizations that want to see how the platform performs in practice can review the [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study, or explore the [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) for additional analyst context. For teams ready to evaluate the platform directly, the [employee app solution page](/solutions/employee-app) outlines how MangoApps extends intranet access to every worker, regardless of role or location. Learn more about MangoApps at www.mangoapps.com. **About The Reworked IMPACT Awards** The Reworked IMPACT Awards celebrate exceptional work in the fields of employee experience and the digital workplace. Winners were chosen from qualified nominees who were required to be employee experience leaders, departments/teams or vendors that deployed superior employee experience initiatives or programs over the past year. Judging was completed by a panel of practitioners and industry specialists, led by Reworked Editor-in-Chief Siobhan Fagan, with the winners selected based on information provided through the nomination process. Learn more at https://www.simplermedia.com/impact-awards/reworked/. **About Reworked** Reworked, produced by Simpler Media Group, is the leading community for employee experience professionals. The Reworked community consists of influential HR, IT and workplace leaders focused on building better workplaces through technology, culture and strategy. To learn more, visit Reworked.co. **About MangoApps** MangoApps is the AI-powered unified workforce platform built for frontline and operational teams. It brings communication, daily operations, and employee support into a single platform managers use to keep teams aligned and work moving across frontline and office environments. Trusted by leading organizations around the world, MangoApps supports business-critical work every day. For more information, visit www.mangoapps.com. --- # Managing a Unionized Workforce Is Different. Your Software Should Be Too. **Author:** MangoApps Team **Published:** 2026-04-05 **Category:** industry-use-cases A grievance lands in your inbox on a Thursday afternoon. A maintenance worker says he was passed over for an open position that, under the CBA, should have gone to the most senior eligible employee in his classification. # Managing a Unionized Workforce Is Different. Your Software Should Be Too. A grievance lands in your inbox on a Thursday afternoon. A maintenance worker says he was passed over for an open position that, under the CBA, should have gone to the most senior eligible employee in his classification. HR has to pull the contract language, cross-reference the seniority list, figure out whether bumping rights apply, document the whole thing, and track it through a multi-step resolution process — all while the clock on the SLA is ticking. This is the daily reality for HR teams and operations managers at unionized organizations. And it is a reality that most workforce software has never adequately addressed. The tools are built for non-union environments — clean, simple, no layered obligation structures — then sold to employers where every scheduling decision, every job posting, every overtime hour is governed by a contract. The gap shows. Roughly 14 million U.S. workers — about 10% of wage and salary employees — are covered by a union contract, representing a large addressable market underserved by mainstream HR software. Public-sector union membership sits at 32.5% versus 6% in the private sector, making government and municipal employers the highest-density segment for CBA compliance tooling. For these organizations, the gap between what standard workforce software does and what the CBA requires has been filled by spreadsheets, manual operations, and institutional knowledge held by a few people who know the contract well enough to apply it correctly. Three releases this week address that gap directly. --- ## When Overtime Isn't Just a Number In a non-union shop, overtime is simple: hours worked beyond 40, paid at 1.5x. In many union environments, overtime is a currency. It accrues into a bank. Employees elect whether they want it paid out or held. Different classifications have different conversion multipliers. Banked hours expire on a rolling basis under FIFO rules. Payout requests go through an approval workflow. And all of it has to be documented for compliance audits. Shift-work management platforms built for non-union environments lack contractual overtime-distribution logic entirely, forcing unionized employers to layer manual spreadsheets on top — a gap now being addressed by at least two competitors entering the space. The Banked Time Management release takes a different approach within [workforce management](/solutions/workforce-management): configurable conversion multipliers per agreement, employee-level pay-vs-bank elections, payout workflows with approval steps, FIFO rolling expiry enforcement, and compliance reports built in. The reason this matters is not efficiency. It is liability. When an employee claims their bank was miscalculated — or that they elected payout but it never happened — the employer needs a clear record of every election, every conversion, every balance change. A spreadsheet does not provide that. A system that treats banked time as a first-class concept does. The [time and attendance](/solutions/time-attendance) infrastructure behind this module is designed to serve as audit-ready compliance documentation — not merely a workflow convenience. --- ## The CBA Is Not a Document. It Is a Rule Engine. When a job opens at a unionized facility, the CBA often dictates who gets first rights to it. Seniority-based bumping provisions mean that a senior employee in a related classification may have the right to claim the role before it's posted externally — or even before junior employees in the same classification. Getting this wrong is not a process failure. It is a grievable offense. Per FMCS Annual Report data, seniority-based bumping disputes rank among the top three categories of grievances filed in manufacturing and public-sector unions, meaning CBA rule errors have outsized grievance volume impact. HR teams at unionized employers often carry the CBA mentally, applying its rules informally because there is no system that knows the contract exists. The CBA Planner changes that model. Admins can define CBA eligibility rules and classification structures, simulate seniority-based bumping scenarios before a decision is made, and automatically notify union members when internal postings go live — so the contractual notification obligation is met without a manual step. The simulation piece is worth pausing on. Bumping rights are not always obvious. A senior employee in classification A may have the right to bump into classification B based on a cross-training agreement, but only if they have the required certifications and have been in their current role for a minimum period. Running through those conditions manually before every internal posting is time-consuming and error-prone. Having a system that can model the scenario first — showing you who has rights before you post — reduces both the administrative burden and the grievance risk. --- ## Grievances Need a Home, Not a Shared Inbox When a union member files a formal grievance, what happens next is usually one of two things: it lands in someone's email, or it gets a ticket in a general help desk system that was never designed for labor relations. Either way, there is no structure around it. Stages are tracked in a spreadsheet. SLA deadlines are managed by whoever remembered to set a calendar reminder. The audit trail is whatever email chain survives. Grievance mismanagement in unionized environments routinely results in arbitration costs ranging from $10,000 to $100,000 or more per case, per labor relations research from Cornell ILR and FMCS publications. That makes audit-ready documentation a direct cost-avoidance lever — not just an HR nicety. Grievance Tracking in Service Desk brings a dedicated workflow to this process: configurable stages, per-stage SLA deadlines, designated approvers at each stage, a stage-stepper UI that shows exactly where each case stands, and a full audit trail. The audit trail is not a nice-to-have — it is the record that matters if a grievance escalates to arbitration. What makes this particularly useful is that it lives in the same system as the rest of workforce operations. A grievance that relates to an overtime bank discrepancy, a bumping-rights dispute, or a missed posting notification can be linked to the underlying records — because those records now exist in the system as well. --- ## Frontline Access: Where Union Members Actually Work Union members in trades, healthcare, manufacturing, and logistics are overwhelmingly deskless workers. Per Emergence Capital, 80% of the global workforce is deskless — and these employees cannot file a grievance, check a banked-time balance, or elect a payout option if the tools require a desktop login they never have access to. This is a gap that competitors in the frontline communications space have moved to close with mobile-first interfaces. For the Banked Time, CBA Planner, and Grievance Tracking modules to deliver their compliance value, union members need to interact with them from the floor, the job site, or the cab of a vehicle. Mobile grievance filing and banked-time elections via phone are not convenience features in this context — they are prerequisites for the system to function as designed. The [shifts and schedules](/solutions/shifts-schedules) layer of the platform is already built around this reality; the union-specific modules extend that same access model. --- ## The Rest of the Week Beyond the union workforce releases, two other areas saw meaningful updates. Performance management picked up a pair of improvements. HR admins can now organize review campaigns into named Performance Cycles — grouping multiple review configurations under a single cycle and creating all employee reviews in one action rather than one at a time. And Post-Review Surveys can now be automatically triggered when a review is approved, sent to the employee, the reviewer, or both. These are process improvements that reduce the manual coordination load around review season without changing how the reviews themselves work. On the AI side, Ask AI is now available directly in the MangoApps Chrome extension — with conversation history, suggestion chips, and awareness of the current page context. For employees who live primarily in a browser, this removes the need to navigate to a separate tool to ask a question. --- ## What This Week Points To Workforce software has historically been built for the median employer. That median employer has relatively uniform pay structures, simple overtime rules, no contract obligations governing internal job postings, and no formal grievance process. The tools reflect those assumptions. But a significant portion of the workforce operates under collective bargaining agreements — in healthcare, manufacturing, logistics, utilities, education, and public services. For these employers, the gap between what workforce software does and what the CBA requires has been filled by spreadsheets, manual operations, and institutional knowledge held by a few people who know the contract well enough to apply it correctly. Three releases in a single week targeting banked time, seniority-based bumping, and grievance tracking is a signal about where the product is heading. The goal is not to add union-specific features as an add-on. It is to build an employee experience platform where the obligations embedded in a labor agreement can be codified, enforced, and audited — the same way scheduling rules, leave policies, and compliance requirements already are. The [modern HCM](/solutions/modern-hcm) framework underpinning these releases treats the CBA as a rule engine, not a reference document. For HR leaders and operations managers at unionized organizations, that is a meaningful shift. --- ## How to Audit Your Current CBA Compliance Gaps For organizations evaluating whether their current tools are adequate, the following five-step audit provides a practical starting point — regardless of which software you use. 1. **Map every overtime rule in your CBA to a system field.** If your time-and-attendance platform cannot represent banked-time elections, FIFO expiry, or classification-specific multipliers as structured data, you are managing those rules manually. That is a liability exposure, not just an inconvenience. 2. **Inventory your grievance history for the past 24 months.** Categorize by type: overtime disputes, bumping-rights challenges, posting notification failures. The categories with the highest frequency are where your process gaps are largest — and where arbitration risk is most concentrated. 3. **Test your seniority list against a hypothetical bumping scenario.** Pick a recent internal posting and walk through who had bumping rights under the CBA. If that exercise required more than one person and more than 30 minutes, the process is not systematized. 4. **Check whether your grievance records would survive arbitration discovery.** If the documentation lives in email threads, shared drives, or a general ticketing system with no stage history, the audit trail is incomplete. Per Cornell ILR and FMCS research, arbitration costs range from $10,000 to $100,000+ per case — documentation gaps directly affect outcomes. 5. **Assess mobile access for frontline members.** If union members cannot file a grievance or check a banked-time balance from a phone, the system is not accessible to the people it is supposed to serve. Per Emergence Capital, 80% of the global workforce is deskless; in unionized trades and manufacturing, that share is higher. This audit does not require new software to complete. It requires honest answers about where manual operations are substituting for system logic — and what the cost of that substitution is when a grievance escalates. --- ## Common CBA Pitfalls That Generate the Most Grievances Organizations new to CBA compliance tooling consistently encounter the same failure patterns. Understanding them before implementation reduces the risk of replicating old problems in a new system. **Posting notification failures.** The CBA typically specifies how long an internal posting must remain open and who must be notified. Missing the notification window — even by a day — is a grievable offense in most agreements. Automated notification tied to the posting workflow eliminates this category of error. **Seniority list errors.** Seniority lists are only as accurate as the data feeding them. If the CBA Planner or any bumping-simulation tool pulls seniority data from a connected HRIS automatically, errors in the source system propagate into bumping decisions. If it requires manual input, the list is only as current as the last update. Either way, the accuracy of the seniority list is the single most important data-quality question for CBA compliance. **Overtime distribution inequity.** Many CBAs require that overtime be distributed equitably across eligible employees in a classification before it can be offered to others. If the system does not track cumulative overtime offers — not just hours worked — it cannot enforce this rule. Employees who track this manually will file grievances when they believe the distribution was unfair. **Banked-time election disputes.** When an employee claims they elected payout but the record shows bank, the dispute comes down to documentation. Systems that capture elections as structured, timestamped records with employee acknowledgment resolve these disputes quickly. Systems that rely on email confirmation or verbal agreement do not. **Grievance stage lapses.** Most CBAs specify response deadlines at each grievance stage. Missing a deadline can result in the grievance being deemed resolved in the employee's favor by default. SLA enforcement at the stage level — not just at the overall case level — is the operational requirement. For a broader view of how workforce operations are evolving in 2026, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the structural shifts affecting both union and non-union employers. --- ## What Legal and Compliance Risks Should HR Leaders Know? The legal exposure in unionized workforce management is concentrated in three areas. **Duty to bargain.** Unilateral changes to working conditions — including changes to how overtime is tracked or distributed — can constitute an unfair labor practice if they are not bargained with the union. Implementing new software that changes how CBA rules are applied may trigger a bargaining obligation. HR leaders should involve labor counsel before deploying tools that alter how contract provisions are administered. **Arbitration exposure.** As noted above, per Cornell ILR and FMCS research, arbitration costs range from $10,000 to $100,000 or more per case. The documentation standard in arbitration is high: arbitrators expect contemporaneous records, not reconstructed timelines. Systems that generate audit trails automatically — with timestamps, user attribution, and stage history — are materially better positioned than those that do not. **NLRA Section 8(a)(5) violations.** Failure to provide the union with information it requests for grievance processing — including seniority lists, overtime records, and job posting histories — is an unfair labor practice. If that information lives in a system that cannot produce it in a usable format, the employer is exposed. Structured data in a purpose-built system is easier to produce in response to information requests than records scattered across spreadsheets and email. For HR leaders building out their broader compliance and employee experience strategy, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) provides context on where compliance infrastructure is heading across the industry. --- # What Scheduling Managers Wish the Software Just Knew **Author:** MangoApps Team **Published:** 2026-03-29 **Category:** news-and-updates Building a frontline schedule is not a one-time event. It is a living document — posted on Monday, revised by Tuesday, renegotiated by Thursday. # What Scheduling Managers Wish the Software Just Knew A frontline manager at a 12-location retail chain posts the week's schedule on Monday morning. By Tuesday, an employee calls out sick. By Thursday, a new hire was assigned to the wrong location and it took a supervisor two hours to untangle. By Friday, payroll is asking why two employees got flagged for overtime — the auto-fill tool had optimized for coverage without knowing either person had reached their weekly ceiling. The manager didn't make a bad schedule. She made a schedule the software immediately started eroding. This is the central frustration that scheduling tools have not fully solved: managers already hold most of the information the system needs. They know who is part-time and capped at 32 hours. They know which location needs a closer and which needs a stock associate. They know which employee filed a shift-swap request that affects this week's coverage. The software's job should be to hold that knowledge so the manager doesn't have to restate it from scratch every cycle. Most scheduling tools hold it for one week. Then the next schedule starts, and it's gone. Three recent improvements to MangoApps target exactly this gap — not by making the scheduler smarter, but by giving it a longer memory. And the way they connect to the HCM and payroll layer underneath is what distinguishes them from point-solution schedulers that stop at the published schedule. ## Why the schedule keeps breaking after it's published Schedule instability is not primarily a planning problem. It's an information problem. The manager builds the schedule using constraints she already knows. The software publishes it. Then reality diverges, and the tool offers no help re-applying those same constraints to the corrections. This cycle has retention consequences. Frontline employee turnover reaches up to 80% in some industries, according to strategypeopleculture.com research — and schedule fairness, specifically the consistency and predictability of hours, is one of the top contributing factors. Highly engaged workplaces see 78% less absenteeism and a 23% increase in productivity, per Gallup research. A schedule that reflects what the manager intended — and that employees can trust week over week — is one of the more direct routes to closing that gap. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) identifies frontline scheduling friction as one of the top drivers of management overhead in multi-location environments. The pattern is consistent: managers spend the most time not on the initial schedule build but on the correction loop that follows every publish. ## What a person-first view actually changes Most scheduling interfaces are organized around time. The week spreads horizontally, shifts appear as blocks, and team members are a secondary axis — something you navigate to when a change is needed. That structure works for initial schedule creation. It doesn't work for troubleshooting. When a shift goes uncovered, the manager isn't asking "when is there an open slot?" She's asking "who has availability, who isn't already at their hour ceiling, and who is already at this location?" Those are person-first questions, and a time-first interface forces her to navigate to each employee manually to answer them. The board view in MangoApps [shifts and schedules](/solutions/shifts-schedules) flips the primary dimension: every row is a team member, every column is a day. Unassigned shifts appear directly in the grid. Drag-and-drop between rows and columns takes seconds rather than several menu clicks. The view doesn't add information the manager didn't already have — it surfaces the right information at the moment it's needed, without the navigation overhead. 80% of the global workforce is non-desk, according to Staffbase research, meaning the majority of scheduling complexity lives on the factory floor or the retail floor, not in a calendar app. For those workers and their managers, a view that makes the next correction obvious isn't a convenience feature — it's the difference between a fix that takes two minutes and one that takes twenty. The board view pays off after a schedule is drafted, not during the initial build. For creating a schedule from a template, the horizontal time-slot view remains faster. Switch to the board view once the draft exists and the task shifts to finding gaps, imbalances, and unassigned shifts. The two views are complements, not substitutes. ## Location assignment as a pre-publication decision Multi-location operations have a second layer of complexity that single-site teams never encounter: not just who works when, but who works where. The industry has moved on this gap recently — at least two competitors have added location-aware scheduling as a distinct capability in the past 90 days, a signal that buyers are treating it as a table-stakes requirement in shift-work management platforms (per competitive movement signals in the category). The standard approach handles location as a post-publication edit. The manager builds the schedule from a template, publishes it, then loops back through shift by shift to tag locations. This works, but it creates a predictable correction queue before the week has even started. Per-shift location assignment moves that decision into the template application step. Each shift gets a location before the schedule is created. For teams with stable patterns — the same shifts going to the same sites week after week — AI-suggested bulk matching uses prior assignment history to pre-fill most of the decisions. The manager confirms or adjusts rather than rebuilding from scratch. The value isn't the AI suggestion. It's the decision point itself: surfacing location assignment as a deliberate pre-publication step rather than a post-publication cleanup. For teams with high week-to-week variation in staffing needs, the AI shortcut is less useful — it relies on prior patterns — but manual location assignment at the template step still reduces post-publication corrections. The [Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) covers how this pre-publication discipline plays out in high-volume multi-site retail environments where the reduction in day-one corrections compounds across dozens of locations. ## Hour targets as structural constraints, not guidelines Auto-assign has a recurring failure mode: it optimizes for coverage without knowing what it's not supposed to do. Fill open shifts, maximize coverage — that's the objective. The system achieves it efficiently. Then the manager discovers that one employee hit 52 hours while another sat at 20, and neither person knew until payroll flagged it. Schedule hour targets and auto-assign limits encode those constraints structurally. Set a weekly ceiling per employee — 32 hours for part-time, 40 for full-time — and the system respects those limits when filling shifts. Remaining capacity for each team member shows in the team calendar and print views, so managers can see who has room before making additional assignments rather than after. This matters beyond individual fairness. For organizations operating under collective bargaining agreements, labor law hour restrictions, or internal equity policies, the difference between a guideline and a structural constraint is whether the system can ignore it. A number that the manager has to enforce manually on every schedule run is not a constraint — it's a reminder that gets missed. Highly engaged workplaces see a 40% boost in employee engagement, according to IOIC IC Index research. The same research finds that 26% of UK employees are deeply disconnected from their organizations — a disconnect that tracks closely with perceived fairness in workload distribution. Hour targets are one of the few scheduling controls that directly address that perception: the distribution rule is visible, automatic, and consistent across every cycle. One configuration step to take before the first auto-assign run: review the priority order alongside the hour targets. If the system fills shifts by seniority but targets are uniform, senior employees hit their ceiling first while newer employees remain underutilized. Align the priority logic with the targets before the first run, not after the first complaint. ## The layer most scheduling tools leave open The three capabilities above address the scheduling UI layer. There's a fourth problem that stays open when scheduling lives in a point solution disconnected from the systems underneath: when the schedule changes, the rest of the data doesn't move with it. A manager adjusts an employee's hours mid-week. That change needs to propagate to time and attendance tracking, to the payroll run, to any compliance reporting that references scheduled hours. In a disconnected stack, someone manually reconciles those records — typically the same scheduling manager who just spent two hours on corrections. Scheduling tools that integrate with HRIS and payroll systems eliminate this manual re-entry, removing a category of downstream errors in hours tracking and compliance reporting that point-solution schedulers introduce by default. MangoApps connects the scheduling layer to time and attendance and the broader [workforce management](/solutions/workforce-management) stack within the same platform. The employee record, the hours ledger, and the payroll run reference the same data. This is the differentiation point-solution schedulers can't match — not a richer scheduling UI, but a scheduling layer that's actually connected to the systems that act on its output. This is also where the hour-target and location-assignment constraints gain their full value. A limit enforced in the scheduling tool that doesn't carry into time tracking is only half a control. When the scheduling layer talks to the payroll layer, the constraint becomes complete. ## What makes scheduling knowledge stick The same principle connects all of these capabilities: reduce the number of times a manager has to re-apply the same judgment. Scheduling managers already know who is part-time, which location needs which shift, which employee is running close to their limit. When those constraints live inside the tool — held structurally across cycles — they don't have to be re-remembered and re-applied from scratch every week. The judgment was sound the first time. The goal is to stop asking for it again. This is not a new idea. It's just been unusually hard to execute in scheduling software, where the dominant architecture treats each schedule as a fresh event rather than a continuation of the constraints that built the previous one. The move toward integrated workforce management platforms is partly a response to that problem: the employee record, the hour history, the location assignment patterns all persist between schedules, even when the schedule itself resets. Scheduling managers aren't waiting for software to make decisions for them. They're waiting for software to hold what they already decided — and stop making them restate it from scratch every week. --- # Closing the Information Gap in Performance Reviews **Author:** MangoApps Team **Published:** 2026-03-22 **Category:** best-practices Think about the last time you prepared for a performance review. If you are a manager, you probably spent days pulling data, reviewing notes, checking goals. # Closing the Information Gap in Performance Reviews Think about the last time you prepared for a performance review. If you are a manager, you probably spent days pulling data, reviewing notes, checking goals. You knew the rough shape of the outcome before the meeting started. If you are an employee, you spent those same days guessing. You had context on your own work but almost none on how your manager had assessed it. The review meeting itself was when the asymmetry became visible — one person walked in with the full picture, the other with a partial one. This is not a personality flaw or a bad manager problem. It is a structural one. Most performance management tools are built primarily for the administrator of the process, not the participant in it. The employee's view has historically been an afterthought. Several releases this week address that directly. --- ## The Structural Asymmetry in Review Meetings The imbalance in performance reviews runs deeper than most organizations acknowledge. A manager preparing for cycle-end reviews has access to self-assessments, goal tracking data, calibration notes, and retention risk signals — all of which inform their rating before the conversation starts. The employee, meanwhile, arrives with their own self-assessment and hopes they have read the room correctly. This creates predictable problems. Reviews feel adversarial when they should be collaborative. Employees feel evaluated rather than heard. And even well-intentioned managers deliver feedback that lands poorly because the employee is processing new information and managing their reaction simultaneously, rather than coming to the conversation prepared. The discussion that should happen before the review — "here is how I rated you, here is why, let's talk it through" — often becomes the review itself. Which means the meeting is less a conversation and more a verdict. [Performance Review Mutual Visibility](https://www.mangoapps.com/changelog/2925) addresses this directly. Once both the manager and employee have submitted their respective portions of a review, each party can see the other's ratings, comments, and assessment fields in full — before the scheduled meeting. Employees arrive prepared. Managers arrive knowing the employee has already processed the feedback. The dynamic of the conversation changes. This matters more than it might appear at first. Organizations that move review meetings toward genuine dialogue — where both parties are reviewing the same information rather than one party receiving it — tend to see better engagement scores and lower attrition in the periods following review cycles. The mechanism is straightforward: when the conversation is a discussion rather than a disclosure, employees feel like participants rather than subjects. --- ## What Managers Actually Need Before They Sit Down Transparency for employees only solves half the problem. The other half is manager preparation — and the capacity for it is rarely there. Most managers in frontline organizations are carrying review cycles for teams of 10 to 30 people, often alongside scheduling, compliance, and daily operational work. The expectation that they will arrive at every review meeting with a nuanced, prepared understanding of each employee's trajectory — goals achieved, feedback patterns, retention signals — frequently goes unmet. Not because managers do not care, but because assembling that picture from disparate screens and filters takes time they do not have. [Performance AI Team Insights](https://www.mangoapps.com/changelog/2924) gives managers a different entry point. Rather than navigating through multiple modules to build a mental model of their team's performance landscape, managers and HR admins can ask the AI assistant directly: which team members have open feedback? who has retention risk signals? which reviews are still incomplete? The AI surfaces the relevant context and allows actions — submitting feedback, starting a review, drafting a reward letter — directly from the conversation. This is not AI forming the manager's opinion. It is AI doing the assembly work so the manager can form one. The judgment remains human; the prep work does not. [AI Home](https://www.mangoapps.com/changelog/2925), also shipped this week, takes a broader view. It is a dedicated page that surfaces AI-prioritized action items across the full scope of HR responsibilities — not just performance, but training, compliance, headcount, and everything else a manager or HR leader is tracking concurrently. For anyone who context-switches between these areas throughout the week, having a single place where AI has already done the triage is a meaningful reduction in the mental overhead of knowing what needs attention next. --- ## The Record Belongs to Both Parties There is a third dimension to the information gap that rarely surfaces in conversations about performance management: what happens to the review after the cycle ends. Performance reviews typically live entirely within the platform that produced them. An employee who wants to reference their own review history — for a career conversation with a mentor, a new role application, or simply their own documentation — generally cannot access that record in any portable form once the cycle closes. [Performance Review PDF Export](https://www.mangoapps.com/changelog/2926) changes that. Employees can now export their own reviews as formatted PDFs, with content scoped to their role and all configured template settings respected. On the surface it is a small feature. What it reflects is more significant: the employee's performance review is their record, not just the organization's. This matters most at the organizational edges — for frontline workers who change roles, move between departments, or transition employers over time. A portable document of their performance history is something concrete they carry forward. For organizations, it also signals something about orientation: the review process is designed for the participant, not only for the administrator tracking it. --- ## The Quiet Shift Underneath These Releases The common thread across this week's performance releases is not a technology choice. It is a design orientation. Performance management tools have historically been built from the vantage point of the person running the process — HR leaders and managers who need to track, evaluate, and act on data at scale. The employee's view was secondary: a self-assessment form, a read-only results page after the cycle closed, a notification when something was submitted. What shipped this week moves in a different direction. Mutual visibility gives employees the same contextual grounding managers have before the conversation starts. AI Team Insights give managers the preparation time the operational load otherwise crowds out. PDF export gives employees a portable record of their own history. AI Home gives everyone a prioritized view of what actually demands attention today. None of these are headline-grabbing on their own. Taken together, they represent a consistent push toward performance management as a process where both parties are prepared, both parties have access to the same information, and both parties leave the review conversation with a shared understanding rather than one person delivering and one receiving. That orientation — toward the participant, not just the administrator — is what tends to produce better review outcomes, stronger manager relationships, and lower attrition in the months following a cycle. MangoApps has been building toward this for a while. This week's releases make it visible. --- # Frontline Intranet Requirements: A Practical Checklist for Replacing SharePoint 2016/2019 **Author:** Andy Tolton **Published:** 2026-03-20 **Category:** intranet If you are searching for frontline intranet requirements, this guide is for you. It lays out what a frontline-ready intranet needs to do, what to require during evaluation, and how to avoid recreating the same adoption problems when you replace SharePoint 2016/2019. 80% of the [global workforce is frontline or deskless](https://hrexecutive.com/frontline-first-hr-engaging-the-80-that-powers-your-business/). Most enterprise software — including SharePoint — was built for the other 20%. That gap matters when you are replacing an intranet. A desk-only replacement can look like a successful migration on paper and still fail the business, because the people running daily operations — the ones in stores, plants, warehouses, clinics, and on the road — never truly adopt it. When frontline employees cannot access or trust the intranet, managers become the human workaround. They translate updates, answer the same questions repeatedly, chase acknowledgements, and patch together processes across too many tools. If you are searching for frontline intranet requirements, this guide is for you. It lays out what a frontline-ready intranet needs to do, what to require during evaluation, and how to avoid recreating the same adoption problems when you replace SharePoint 2016/2019. If you need the broader replacement context — timeline, risks, and path options — start with the [SharePoint 2016/2019 end of life and replacement options guide](http://www.mangoapps.com/articles/sharepoint-2016-and-2019-end-of-life-resources) and come back here. If you are already executing a migration, this guide pairs with the [SharePoint Server 2016/2019 Migration Checklist](https://www.mangoapps.com/articles/sharepoint-server-2016-2019-migration-checklist). ## **Why desk-only intranets fail in frontline organizations** A desk intranet assumes people have a laptop nearby, time to browse, consistent email access, stable schedules, and enough patience to navigate multiple layers of menus. Frontline work rarely looks like any of that. People are moving, switching tasks, covering gaps, and dealing with customers, patients, or production lines. If the intranet experience requires too many steps, the natural fallback is: ask a manager, ask a coworker, or do it the way we did it last time. That is how outdated procedures persist. It is how missed updates happen. It is how compliance visibility turns into a scramble after the fact. [Only 22% of frontline employees](https://www.gallup.com/workplace/650174/employee-retention-depends-getting-recognition-right.aspx#:~:text=While%20leaders%20are%20increasingly%20acknowledging%20the%20importance,recognition%2C%20employees%20are%20not%20feeling%20the%20effects.) say they feel their work is important to the company's vision. A desk-only intranet reinforces exactly that disconnect — it signals that the platform was built for someone else. A SharePoint 2016/2019 replacement is a genuine opportunity to change that. ## **What a frontline intranet means in plain language** A frontline intranet is where employees go to: - Get the latest operational updates that affect today's work - Find the right procedure or SOP fast - Complete required actions: acknowledge, submit, request, confirm - Know what changed and what to do next - Find the right person or escalation path when something goes wrong What it is not: a document dump, a static portal that only corporate teams use, or a maze of departmental sites that employees have to guess their way through. ### **Employee app versus intranet: do you need both?** For frontline teams, this distinction mostly disappears in practice. Employees do not care whether it is called an intranet or an app — they want one place on their phone that helps them get through the day. With [MangoApps](https://www.mangoapps.com/), you do not have to choose. Desk and frontline employees access the same unified platform, optimized for how they actually work — corporate teams through a full browser experience, frontline teams through a [mobile-first branded app](https://www.mangoapps.com/solutions/employee-app). One platform, one governance model, one place for every employee. ## **Frontline realities to design for** These are the conditions a replacement solution must handle well. If a platform cannot address them, adoption will not stick regardless of how good the content is. - **Limited time and attention:**employees will not browse the intranet the way corporate staff might. Every extra tap or navigation step loses people. - **Shift work:**communication has to reach people across shifts without relying on word-of-mouth or the hope that someone passed the message along. - **Shared and personal devices:**access patterns vary by location and policy. The platform has to handle both without requiring separate infrastructure. - **Mixed connectivity:**warehouses, plants, and on-the-road roles do not always have stable signal. Critical content needs to be reachable under real conditions. - **Multiple languages:**translation and consistency are ongoing work, not a one-time project. Governance has to account for it. - **Safety and compliance:**"everyone saw it" is not good enough when you need a verifiable record. Acknowledgement and targeting capabilities are not optional. - **High turnover:**onboarding has to be fast, clear, and repeatable — not dependent on a manager having time to walk someone through it. - **Managers as bottlenecks:**the goal is to reduce the ask-the-manager dependency for routine questions, not eliminate managers, but free them up for work that actually needs them. ## **Requirements checklist: access and authentication** Frontline adoption starts and ends with access. If logging in is painful or inconsistent, people stop trying — and they never come back. ### **Access without corporate email** Many frontline organizations have a significant portion of employees who do not have corporate email addresses, or who have them but never use them. A frontline-ready solution must support: - Onboarding and login options that do not assume corporate email - Identity mapping through employee identifiers driven by HR systems - Shared device patterns for kiosks and break-room tablets where applicable If access depends on a corporate mailbox that frontline employees never open, you have built a desk intranet again — just with a different name. ### **Secure access that does not create friction** Security matters, but frontline security has to be usable in real conditions: - SSO support wherever possible - Role-based access control aligned to jobs and locations - Session rules that balance security and real-world usage patterns ### **Multi-device reality** Frontline access is not one device type. Validate all three: - Personal mobile device experience (BYOD) - Shared device experience for locations that use them - Consistent experience across mobile and desktop for employees who use both > *MangoApps supports real frontline access patterns out of the box — including BYOD, shared devices, and access without corporate email. It connects cleanly with your HRIS and identity systems so employee data flows in from day one. See*[*mangoapps.com/integrations*](https://www.mangoapps.com/integrations)*for the full list.* ## **Requirements checklist: mobile experience** Mobile-friendly is not the bar. Frontline success requires mobile-first design — meaning the experience was built for a phone, not adapted from a desktop. ### **Mobile-first navigation** Validate these specifically: - Simple navigation that works one-handed - Quick paths to top tasks: policies, SOPs, requests, schedules, contacts - Favorites and shortcuts so employees are not repeating the same navigation daily - A predictable home screen that is genuinely useful, not just a news feed A useful test: can a new hire find the top five things they need within 30 seconds, on a phone, without training? If the answer is no, the navigation is not frontline-ready. ### **Push notifications and urgent communications** Frontline teams often miss updates because they are not actively checking the intranet. [Push and targeting capabilities](https://www.mangoapps.com/key-features/critical-alerts) are not a nice-to-have — they are the mechanism by which communication actually reaches shift workers. Validate: - Targeting by role, location, shift, and team - Urgent alert patterns that visually stand out from routine updates - Acknowledgement and read-receipt capabilities for compliance-sensitive communications - Expiration rules so urgent content does not stay prominent after it is no longer relevant ### **Connectivity and performance** Not every platform handles low-connectivity environments the same way. At minimum, validate: - Performance on slower mobile connections - Minimal steps required to reach critical SOPs and safety content - Whether any offline or caching approach exists for key content in consistently low-connectivity environments ## **Requirements checklist: content types frontline teams actually need** Frontline adoption is won or lost by whether the intranet helps employees complete real work. Make sure your replacement supports these content types in ways that are fast to access and easy to keep current: - [**SOPs and procedures**](https://www.mangoapps.com/key-features/file-management)**:**step-based, searchable, and easy to update without IT involvement - [**Safety and compliance content**](https://www.mangoapps.com/key-features/knowledge-bases)**:**clear, targeted, measurable — with acknowledgement capability when required - [**Training and onboarding**](https://www.mangoapps.com/solutions/learning-management)**:**quick, repeatable, and role-specific so new hires do not depend entirely on a manager's availability - [**HR basics**](https://www.mangoapps.com/key-features/department-sites)**:**policies, benefits highlights, and how-do-I answers that employees can self-serve without calling HR - [**Location information**](https://www.mangoapps.com/key-features/company-portal)**:**contacts, hours, maps, escalation paths, and local safety procedures - [**Operational updates**](https://www.mangoapps.com/key-features/posts)**:**changes that affect today's work — not just company-level news This is also where governance matters most. SOPs are only valuable if they stay current. A platform with no review cadence enforcement is a platform where outdated procedures quietly become the norm. See the [Intranet Governance Plan](https://www.mangoapps.com/articles/sharepoint-server-2016-2019-replacement-intranet-governance-plan) for the full governance model, including content lifecycle rules and review cadences by content type. ## **Requirements checklist: findability and self-service** Frontline employees do not want more information. They want the right answer quickly, under pressure, often on a small screen. ### **Search that works under pressure** Validate these specifically — not in a demo, but with real content in a pilot: - Consistent results that surface the right page first - Synonyms and common-language handling — employees search by the words they use, not the words the system uses - Featured results for critical policies, SOPs, and forms - Clear result previews so employees can choose the right result fast without opening every link A practical evaluation: collect the top 20 questions managers get from frontline employees every week. Then test whether employees can answer those questions through the intranet in under a minute. McKinsey research shows employees spend [20% of their workday searching for information](https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy). A platform with strong search and AI-powered self-service can cut that by 25–30% — which translates directly into fewer interruptions for managers and fewer tickets to HR and IT. ### **Reduce repetitive questions** A well-governed frontline intranet should measurably reduce interruptions to HR, Operations, and IT by giving employees self-service access to trusted answers. Validate: - A clear Help and Answers structure employees can navigate intuitively - Simple policy and SOP presentation that does not require reading through a PDF - Guidance that includes who to contact when the self-service answer is not enough ### **AI-powered support where it helps** AI can be genuinely useful for frontline self-service — when it is grounded in trusted internal content and governed properly. The risk with poorly implemented AI is confidently wrong answers. Validate: - Answers come from trusted internal content, not from general web knowledge - Employees can easily escalate to a person when the AI answer is insufficient - Governance prevents outdated content from being surfaced as authoritative > *MangoApps AI is grounded in your internal knowledge base — SOPs, policies, HR content, and operational procedures. Employees get accurate answers from the content your organization has approved, not guesses. And governance keeps that content clean so the AI stays trustworthy as your organization evolves. Learn more at*[*mangoapps.com/ai*](https://www.mangoapps.com/ai)*.* ## **Requirements checklist: operational actions, not just reading** This is where most intranets fall short for frontline employees. Reading an update is not the same as acting on it. Validate that your replacement supports: - Tasks and checklists tied directly to updates and procedures - Forms and requests: maintenance, supplies, shift swaps, HR requests - Approval workflows where needed — with mobile-accessible interfaces - Acknowledgement and attestation for compliance and policy changes - Visible status so employees are not chasing managers to find out whether their request was received A strong replacement platform reduces tool switching by connecting the update to the action in the same place. When an employee reads a new safety procedure, they should be able to acknowledge it immediately — not open a separate system to log it. > *MangoApps connects communications, tasks, forms, approvals, and acknowledgements in one unified experience. Frontline employees at organizations like AutoZone, PetSmart, and TEAMHealth use MangoApps to move from reading to acting without bouncing between tools. See*[*mangoapps.com/use-cases*](https://www.mangoapps.com/use-cases)*for operational patterns that apply to your industry.* ## **Requirements checklist: frontline governance** Frontline intranets do not fail because employees do not care. They fail because ownership does not match how the organization actually runs — and content quietly goes stale. ### **Ownership by location** Define and validate: - Who owns location pages and local operational updates - What content is global versus location-specific - What approval is required for local content, if any - How local owners request changes to global content they cannot edit directly ### **Translation ownership and review cycles** Define and validate: - Who owns translation for each active language - How quickly critical communications must be translated after the source is published - How translated content stays aligned when the source content changes ### **Expiration rules for operational updates** Operational content has a shelf life. Governance must account for: - What expires automatically versus what becomes evergreen - What moves to archive versus permanent deletion - Who is responsible for refresh when operational conditions change ### **SOP change management** SOPs change — and employees need to know when they do. Validate that the platform and governance model support: - Defined ownership for who can update each SOP - A communication mechanism when an SOP changes — not just a quiet edit - Versioning or change notes so employees know what is different See the [Intranet Governance Plan](https://www.mangoapps.com/articles/sharepoint-server-2016-2019-replacement-intranet-governance-plan) for the full governance model, including the frontline governance addendum with location ownership and shift-based communication rules. ## **Requirements checklist: integrations and systems of record** Frontline adoption improves significantly when the intranet is the place employees go first — even when the system of record lives elsewhere. Validate these integrations early, because they affect both the employee experience and how content stays current: - HRIS: roles, locations, employee profiles — the source of truth for targeting and personalization - Identity provider: SSO and access control for consistent, frictionless login - Ticketing and service workflows: IT and facilities requests - Learning management system: training completion, compliance training, onboarding - Document repositories: policies, procedures, and compliance content - Scheduling or timekeeping systems where applicable to your workforce Validate integration ownership as well as integration existence. Integrations fail in production when nobody owns the data quality and mapping long-term. Assign owners at the start, not after launch. > *MangoApps connects with 200+ enterprise systems — including the HRIS, identity, and operational platforms most common in frontline-heavy industries. See*[*mangoapps.com/integrations*](https://www.mangoapps.com/integrations)*for the full list.* ## **How to evaluate SharePoint 2016/2019 alternatives for frontline use** Frontline evaluation should not be a feature demo. It should be scenario testing with real content under real conditions. ### **Use scenario-based testing with 3–5 scenarios** Pick scenarios that mirror actual daily work. Examples: 1. A new hire finds the correct SOP for a task they have been assigned 2. An employee receives an urgent update and acknowledges it from their phone 3. An employee submits a maintenance or supply request and checks its status without asking a manager 4. An employee finds a policy answer without calling HR 5. A location manager publishes a local update that reaches only the right team For each scenario, measure: time to complete, number of taps or clicks, whether the employee needed help, and whether the experience works in real conditions on a mobile device. ### **Run a frontline pilot before you commit** A credible pilot includes: - One frontline location with real operational content — not demo content - One corporate publishing team (Communications or HR) as the content owner - A small set of real workflows and requests that employees use regularly - Clear success metrics defined before the pilot starts, not after If a vendor cannot support a real-content pilot, that tells you something important. ### **Validate publishing and ownership models** Frontline intranets die when publishing is too centralized — content goes stale because only corporate employees can update it. They also die when everyone publishes anything — trust collapses when employees cannot tell what is current. Validate specifically: how local ownership works in the platform, what guardrails prevent quality drift, how approvals work for policy and compliance content, and how content stays current when operational conditions change. If you are still comparing replacement paths, the SharePoint 2016/2019 end of life and replacement options guide has the full comparison. For a direct look at how MangoApps positions against SharePoint, see [mangoapps.com/sharepoint-alternatives](https://www.mangoapps.com/sharepoint-alternatives). ## **Where MangoApps fits** MangoApps was built for the reality that most enterprise platforms ignore: 80% of the workforce is frontline or deskless, yet most tools were designed for the 20% at a desk. That is the gap MangoApps closes. MangoApps unifies [intranet, communications, knowledge](https://www.mangoapps.com/solutions/modern-intranet), [HR](https://www.mangoapps.com/solutions/modern-hcm), and [operational](https://www.mangoapps.com/solutions/workforce-management) work in one platform — with a mobile-first experience that works for frontline employees without corporate email, on shared devices, across languages, and in low-connectivity environments. Desk and frontline teams use the same platform, governed the same way, with content targeted to each group based on role, location, and shift. [MangoApps customers](https://www.mangoapps.com/customers) consistently achieve 90% adoption rates within 90 days — including 90% adoption among the Kansas City Chiefs' 600 event staff. Organizations like AutoZone, PetSmart, and TEAMHealth rely on MangoApps to reach their frontline workforces at scale. And 98% of MangoApps deployments are delivered on time and within budget, with a typical implementation timeline of 8–12 weeks. For organizations replacing SharePoint 2016/2019, MangoApps offers a cleaner path than migrating to another platform that was not built for frontline reach from the ground up. Explore these starting points: - Modern Intranet: [mangoapps.com/solutions/modern-intranet](https://www.mangoapps.com/solutions/modern-intranet) - Frontline Employee App: [mangoapps.com/solutions/employee-app](https://www.mangoapps.com/solutions/employee-app) - Why MangoApps: [mangoapps.com/why-mangoapps](https://www.mangoapps.com/why-mangoapps) - Use Cases: [mangoapps.com/use-cases](https://www.mangoapps.com/use-cases) - Key Features: [mangoapps.com/key-features](https://www.mangoapps.com/key-features) - MangoApps AI: [mangoapps.com/ai](https://www.mangoapps.com/ai) - Integrations: [mangoapps.com/integrations](https://www.mangoapps.com/integrations) If you are migrating from SharePoint 2016/2019 and want to move quickly without cutting corners, see MangoApps Success Services at [mangoapps.com/success-services](https://www.mangoapps.com/success-services). ## **Next step** Use this requirements checklist to shape your evaluation and pilot. Then put it into motion with the migration execution guide — the [SharePoint Server 2016/2019 Migration Checklist](https://www.mangoapps.com/articles/sharepoint-server-2016-2019-migration-checklist) — which covers how frontline requirements map to each migration phase from discovery through go-live. ## **FAQ** ### **What is the difference between an intranet and an employee app for frontline workers?** For frontline teams, the difference is mostly delivery. If frontline employees primarily access the intranet on their phone, the intranet must behave like an employee app: mobile-first, fast, and action-oriented. The best approach is one unified platform that supports both corporate and frontline needs without fragmentation — which is exactly how MangoApps is built. Desk employees get a full browser experience; frontline employees get a branded mobile app. Same platform, same governance, one employee experience. ### **What should a frontline intranet include?** At minimum: mobile-first navigation, role and location-based content targeting, SOP and policy access, AI-powered self-service answers, operational actions (tasks, requests, acknowledgements), push communications for shift-based teams, and a governance model that keeps content current across locations and languages. The full checklist is in this guide. ### **How do frontline workers access an intranet without corporate email?** A frontline-ready platform needs authentication models that do not assume corporate email. Common patterns include identity mapping through HR systems, employee identifiers, or other enrollment approaches that fit the organization's security model. MangoApps supports multiple access patterns for frontline employees — including BYOD, shared devices, and SMS-based enrollment where needed. ### **What are the biggest reasons frontline intranets fail?** Access friction is the most common: if logging in is hard, employees stop trying. After that: desk-only design that does not work on a phone, poor search that surfaces outdated content, stale SOPs that erode trust, unclear ownership, and lack of operational actions that connect reading to doing. When employees cannot complete real tasks, they revert to asking managers — and the intranet stops being the first place anyone goes. ### **How do you keep SOPs current across locations?** Assign ownership by function and location, use templates and defined review cadences, and make change management part of the publishing workflow — not an afterthought. When an SOP changes, employees need to know, not just discover it during a task. See the Intranet Governance Plan for the full SOP lifecycle and frontline governance model. ### **How does MangoApps handle frontline access differently than SharePoint?** SharePoint was built for desk workers and extended to other environments over time. MangoApps was built from the start for the full workforce — desk and frontline alike. Key differences: MangoApps supports access without corporate email, delivers a true mobile-first experience (not a responsive adaptation), targets content by role, location, and shift natively, connects communications to tasks and acknowledgements in one place, and supports deployment in 8–12 weeks with 90% adoption as the expected outcome — not the aspiration. ### **How do you measure frontline intranet success?** Look at adoption (especially return usage, not just first-week logins), findability (search success rate and no-results queries), completion of key operational actions (acknowledgements, requests, task completions), content freshness across locations, and reduction in repetitive questions to managers, HR, and IT. MangoApps customers typically achieve 87–90% adoption within 90 days — use that as a benchmark for what a well-governed, well-adopted frontline intranet can realistically deliver. --- # Intranet Governance Plan: A Practical Model for a Modern Intranet and a SharePoint Server 2016/2019 Replacement **Author:** Andy Tolton **Published:** 2026-03-20 **Category:** intranet If you're replacing SharePoint Server 2016/2019 because of end of support, governance is the difference between a clean reboot and a costly repeat of the same problems. Research from Social Edge Consulting shows that while 91% of organizations have an intranet, only 13% of employees use it daily. MangoApps customers consistently hit 87–90% adoption — and governance is one of the biggest reasons why. This article gives you a practical governance plan you can use. Most intranets don't fail in a dramatic way. They fade. Content gets stale. Search gets noisy. Ownership gets fuzzy. Teams stop trusting what they find, so they stop looking. Then the intranet becomes a place people avoid, and the real work moves back into email threads, chat messages, and side documents. If you're replacing SharePoint Server 2016/2019 because of end of support, governance is the difference between a clean reboot and a costly repeat of the same problems. Research from [Social Edge Consulting shows](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) that while 91% of organizations have an intranet, only 13% of employees use it daily. MangoApps customers consistently hit 87–90% adoption — and [governance](https://www.mangoapps.com/key-features/content-governance-engine) is one of the biggest reasons why. This article gives you a practical governance plan you can use. It covers: - What governance actually needs to include — without turning into bureaucracy - A realistic operating model and meeting cadence - Roles and responsibilities that work in the real world - Publishing workflows, templates, and content lifecycle rules - Findability and search governance - Metrics and monthly review routines - Governance for frontline and multi-location environments - How to apply governance during a SharePoint 2016/2019 replacement If you're still deciding between SPSE, SharePoint Online, or a dedicated replacement platform, start with the [SharePoint 2016/2019 end of life and replacement options guide](https://www.mangoapps.com/articles/sharepoint-2016-and-2019-end-of-life-resources) first and come back here once your destination is set. If you're already executing a migration, this governance plan pairs directly with the [SharePoint Server 2016/2019 Migration Checklist](https://www.mangoapps.com/articles/sharepoint-server-2016-2019-migration-checklist). ## **What good intranet governance actually covers** When people hear "governance," they often picture a committee that slows everything down. That is not the goal. Good governance is simply the system that keeps your intranet accurate, owned, consistent, easy to navigate, easy to search, safe where needed, and sustainable after launch. A complete governance plan covers six domains: ### **Content governance** Who owns each area? What is the standard for quality? How often is content reviewed? What gets archived versus deleted? ### **Publishing governance** Who can publish, when approval is required, how urgent communications are handled, and what guardrails prevent sprawl. ### **Information governance** Permissions, retention, legal holds, and rules for sensitive content. ### **Experience governance** Navigation and site structure rules, templates, naming standards, and how new sections get created. ### **Measurement governance** What you measure, how often you review it, and how you turn analytics into improvements. ### **Frontline governance** How ownership works by location and language, and how critical updates are targeted, acknowledged, and kept current. This domain is often skipped entirely — and it is the reason frontline adoption stays low even when the rest of the intranet is working well. See the Frontline Intranet Requirements guide for the full checklist. ## **Governance principles that keep things practical** These six principles keep governance usable instead of theoretical: 1. **Ownership is explicit, not implied.** If nobody owns it, it will decay. 2. **Publishing is distributed; approvals are lightweight.** Centralized publishing creates bottlenecks. No approvals creates chaos. The right model sits in the middle. 3. **Content has a review date.** Not everything needs an expiration date, but almost everything needs a review date. 4. **Templates beat one-off creativity.** Templates make content easier to publish, easier to find, and easier to maintain. 5. **The intranet is a product, not a project.** Go-live is not the finish line. It is the start of a new operating rhythm. 6. **What gets measured gets maintained.** If you never review search misses and stale content, those become your intranet's default state. ## **The governance operating model** You do not need a complex structure to be effective. You need a structure that matches your size, publishing volume, and how distributed your organization is. ### **Two governance structures that work** **Lean model** — common for mid-market and enterprise teams that want speed: one intranet product owner, one platform admin lead, department content owners, a small editorial group, and a monthly governance review. **Enterprise model** — common when you have many publishers, many locations, or heavy compliance needs: a governance council (monthly), an editorial board (weekly or biweekly), a platform operations working group (weekly or biweekly), and a frontline or location owners network (monthly). The point is not the org chart. The point is clarity: who decides, who publishes, who maintains, who measures. ### **Governance cadence that keeps the intranet healthy** A simple rhythm that works for most organizations: - **Weekly:**editorial publishing review — what is going live, what needs tightening, what is urgent - **Monthly:**governance council review — metrics, health, decisions, priorities - **Quarterly:**content audit sprint — stale content cleanup and consolidation - **Biannual:**navigation and site structure review — what needs restructuring or retirement - **Annual:**policy and compliance review — retention, permissions, sensitive content handling If that feels like a lot, start with monthly plus quarterly. Build from there once the rhythm sticks. ## **Roles and responsibilities** This is the section most governance documents avoid being specific about. Specificity is what makes governance usable. ### **Core roles** **Executive sponsor:**owns priority and support. Removes blockers and reinforces that the intranet matters to the business. **Intranet product owner:**accountable for outcomes — adoption, findability, content health, and the roadmap for improvements. This is the most important role in a healthy governance model. **Platform admin lead:**owns configuration, permissions, integrations oversight, and platform reliability. Typically IT or a dedicated platform team. **Department content owners:**accountable for content accuracy and keeping critical pages current. Ideally aligned to HR, IT, Operations, Communications, and key business units. **Publishers and authors:**create content within standards and templates. **Approvers:**approve content where needed — policies, compliance, major announcements. Keep approvals fast and narrowly scoped. **Search and knowledge steward:**owns synonyms, featured results, top searches review, and the no-results action plan. Optional but high-value. **Frontline and location owners:**own local updates, local SOPs, location details, and language-specific needs. Critical for any organization with shift-based or deskless workers. **Analytics owner:**runs the monthly metrics review and turns signals into improvements. ### **A practical accountability map** You do not need a full RACI matrix, but you do need clarity on who owns what: - **Accuracy:**department content owner - **Freshness and review cycles:**department content owner + intranet product owner - **Templates and standards:**intranet product owner - **Permissions baseline:**platform admin lead - **Approval rules:**intranet product owner + governance council - **Navigation changes:**intranet product owner with governance council sign-off - **Search tuning:**search and knowledge steward - **Metrics reporting:**analytics owner - **Broken links and escalations:**intranet product owner + platform admin lead > *During a SharePoint Server 2016/2019 replacement, owner assignment happens during discovery — not at go-live. If you wait until launch to assign owners, you end up guessing under pressure. See the*[*SharePoint Server 2016/2019 Migration Checklist*](https://www.mangoapps.com/articles/sharepoint-server-2016-2019-migration-checklist)*for how ownership maps to migration phases.* ## **Publishing workflows that don't slow everyone down** Most intranet friction comes from two extremes: approvals for everything, which kills publishing velocity, or approvals for nothing, which creates misinformation and clutter. A workable model uses content categories with clear rules. ### **Content categories and approval rules** **News and updates:**published by Communications team and approved department publishers. Lightweight editorial review when needed. Content expires or is unfeatured based on relevance. **Policies and compliance content:**published by policy owners only. Approval required. Review date required, versioning required. **SOPs and procedures:**published by operational owners. Approval required for critical SOPs. Review date required, change notes recommended. **Leadership communications:**published by the Communications team on behalf of leaders. Approval required with fast turnaround expectation. **Location updates:**published by location owners. Approval is often optional depending on risk profile. Tied to location relevance, expiration encouraged. **Communities and social posts:**broad employee publishing. Approval typically not required. Light moderation rules and clear community boundaries. ### **Urgency and critical communications rules** Define what qualifies as critical so the designation stays meaningful. Critical content should meet at least one of these criteria: - Safety and compliance notices - Operational disruptions - Policy changes that require employee action - Time-sensitive workforce updates For each critical communication, define: targeting rules (who must see it), acknowledgement rules (if required), and a sunset rule (when it stops being urgent). ### **Template standards** Templates are the simplest governance tool available. At minimum, standardize these: - **Policy page:**owner, effective date, review date, version history - **SOP:**steps, tools required, safety notes, escalation path, contact - **Request or service:**required fields, routing logic, status expectations - **News or announcement:**summary, audience, expiry guidance, link to the action > *MangoApps supports structured publishing, approval workflows, and template-based content experiences out of the box — so governance rules are enforced by the platform, not by hope. See*[*mangoapps.com/key-features*](https://www.mangoapps.com/key-features)*for the full feature map.* ## **Content lifecycle management** If you want to stop intranet decay, treat content as something that moves through a lifecycle — not something you publish once and forget. ### **The lifecycle stages** Draft → Review → Publish → Measure → Refresh → Archive Governance should define what done looks like at each stage: - Draft includes a named owner - Review checks accuracy, clarity, and correct placement - Publish includes a review date - Measure includes basic engagement and search signals - Refresh happens on a defined cadence - Archive happens intentionally — not by accident or neglect ### **Review cadences by content type** - **Policies:**review every 6–12 months, or based on regulatory cadence - **SOPs:**review every 6–12 months, plus after major operational changes - **HR and benefits content:**review seasonally — open enrollment, policy cycles - **Leadership updates:**expiration guidance so old updates stop cluttering search - **Location details:**review quarterly, since staffing and hours shift regularly ### **Archiving and retention rules** Decide up front: what gets archived versus deleted, who can archive, how archived content stays searchable (or intentionally stops being), and how retention aligns with legal and compliance requirements. Most intranets accumulate a graveyard of outdated content because archiving was never made part of the publishing culture. Make it a normal, expected step — not an afterthought. ## **Permissions and security governance** Keep this section practical — it should not read like a legal document. Baseline rules that reduce governance chaos: - Use role-based access as the default - Avoid one-off permissions except for true exceptions - Document exceptions and set a review cadence for them - Separate confidential content areas with tighter controls - Define guest and external access rules if applicable - Keep audit expectations clear: who changed what, and when During a SharePoint replacement, permissions are one of the easiest places to accidentally recreate the same mess. A clean baseline is almost always better than trying to perfectly replicate years of ad hoc access grants. ## **Navigation and findability governance** You do not need to call it information architecture for it to matter. You need rules for how the intranet is structured and how employees find answers. ### **Rules for site structure changes** Define and enforce: - Who can create new top-level areas - What qualifies as needing its own hub versus fitting within an existing one - When content must consolidate into an existing area - What "one source of truth" means for policies and SOPs Without these rules, departments create their own structures and the intranet becomes a maze again within a year. ### **Search governance** Search is not set-it-and-forget-it. Treat it as an ongoing program with an owner and a cadence. Governance should define: - Who owns the synonyms list and how often it is reviewed - Who owns featured results for critical content - How top searches are reviewed monthly and actioned - A no-results action plan — what happens when employees search and find nothing McKinsey research shows employees [spend 20% of their workday searching for information](https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy). AI-powered search can cut that by 25–30%. But AI is only as good as the content it searches — which means search governance and content governance are inseparable. > *MangoApps AI is grounded in your internal knowledge base. Employees get confident, accurate answers from trusted content — not generic responses. Governance keeps that content clean, current, and reliable. Learn more at*[*mangoapps.com/ai*](https://www.mangoapps.com/ai)*.* ## **Analytics and KPIs** If you only measure page views, you will miss the signals that tell you whether the intranet is actually working. A healthy intranet targets 60–70% or more of employees using it regularly. Best-in-class platforms reach 80–85% weekly adoption. MangoApps customers consistently achieve 87–90% adoption within 90 days — and these are the metrics that matter most: ### **Adoption** - Active users weekly and monthly - Return usage — are employees coming back, or only visiting once? ### **Content health** - Percentage of content with a named owner - Percentage of content reviewed on schedule - Top stale areas by last-modified date ### **Findability** - Top searches and whether results are satisfying - No-results searches — a direct signal of content gaps - Search success proxy: click-through and time-to-find indicators ### **Communications performance** - Reach and engagement on key updates - Acknowledgement rates for critical communications ### **Operational outcomes** - Completion of key requests and workflows - Reduction in repetitive questions to HR, IT, and Operations — a proxy for ticket deflection and self-service success ### **How to run the monthly governance review** A simple agenda that reliably produces decisions rather than slides: - Wins and what changed since last month - Top problems: search misses, stale areas, broken journeys - Decisions: what we are fixing, consolidating, or archiving - Owners and due dates for each decision - Next month's priorities The meeting should take 45–60 minutes and end with a short action list. If it is producing documents instead of decisions, simplify. ## **Frontline governance** Frontline-heavy organizations need governance that accounts for location reality. If the intranet is governed like a desk-worker portal, frontline adoption will break down quickly — regardless of how good the platform is. ### **Location ownership model** - Define location owners explicitly — do not assume regional managers will self-organize - Define what content is global versus location-specific - Define how locations request new content or flag updates from headquarters ### **Language ownership and translation review cycles** - Define who owns translation for each active language - Define how quickly updates must be translated for critical communications - Define how translated content stays aligned when the source changes ### **Shift-based communication rules** - Target updates by shift and role where needed - Define what qualifies as a critical update requiring acknowledgement - Define how long critical content stays visible before it archives For a full frontline intranet requirements checklist — including access, mobile, and scenario-based evaluation criteria — see the [Frontline Intranet Requirements guide](https://www.mangoapps.com/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements). ## **Governance during a SharePoint Server 2016/2019 replacement** Governance is not something you add after migration. It starts during discovery — and the teams that get this right compress their timelines significantly. Here is how governance ties directly into a migration program: 1. **Discovery assigns owners.** Your content inventory should map every section to an owner and surface owner gaps. Gaps become either reassignment work or archiving candidates.**‍** 2. **Content triage follows governance rules.** If content has no owner or review date, it is a candidate for consolidation, rewrite, archive, or deletion — not migration.**‍** 3. **Templates are defined before migration waves.** If you define templates after moving content, you force rework on content that has already been migrated.**‍** 4. **Publisher training happens before go-live.** Publishers need to be ready to maintain content from day one — not learning the platform while employees are already using it.**‍** 5. **The governance council runs rollout decisions.** IT should not be the only voice deciding what goes live and when. Governance council sign-off on each wave keeps the experience quality consistent. > *The biggest governance mistake during a SharePoint replacement: migrating content without assigning owners and review dates, then trying to fix governance after launch. That approach recreates the same intranet sprawl on a new platform within 12–18 months.*[*The Migration Checklist*](https://www.mangoapps.com/articles/sharepoint-server-2016-2019-migration-checklist)*walks through how to wire governance into each migration phase from the start.* ## **How MangoApps supports governance** Governance is significantly easier when your platform enforces it and your rollout includes a clear operating model from day one. [MangoApps customers](https://www.mangoapps.com/customers) consistently achieve 87–90% adoption within 90 days and 95% customer retention — and a workable governance model is one of the most consistent factors in those outcomes. Here is how MangoApps supports it: ### **Platform capabilities that reinforce governance** - Structured publishing and approval workflows — so guardrails are built in, not bolted on - Templates and consistent content experiences that make publishing faster and easier to govern - Role and location-based content targeting — critical for frontline and multi-location environments - Analytics and content health visibility — see what is working, what is stale, and where adoption is slipping - AI-powered search and employee self-service, grounded in your internal knowledge base, so governance keeps answers trusted and current Learn more: MangoApps AI-Powered Intranet ([mangoapps.com/solutions/modern-intranet](https://www.mangoapps.com/solutions/modern-intranet)), Why MangoApps ([mangoapps.com/why-mangoapps](https://www.mangoapps.com/why-mangoapps)), Key Features ([mangoapps.com/key-features](https://www.mangoapps.com/key-features)). ### **Services that help governance land and stay healthy** Governance often fails when it exists only in a document. The organizations that sustain a healthy intranet treat governance as a practice — with the right support to make it stick. - Success Services — [mangoapps.com/success-services](https://www.mangoapps.com/success-services) - Ongoing Partnership — [mangoapps.com/services/ongoing-partnership](https://www.mangoapps.com/services/ongoing-partnership) If you are replacing SharePoint and want to move faster, early governance work is one of the biggest accelerators. When owners, templates, and review rules are set before the first wave, migrations compress and adoption lands stronger. ## **Next step** If you want to put this governance model into action alongside a migration execution plan, pair it with the [SharePoint Server 2016/2019 Migration Checklist](https://www.mangoapps.com/articles/sharepoint-server-2016-2019-migration-checklist)— which walks through how governance maps to each migration phase from discovery through decommissioning. And if you are still evaluating replacement paths, start with the broader [SharePoint 2016/2019 end of life and replacement options guide](http://www.mangoapps.com/articles/sharepoint-2016-and-2019-end-of-life-resources) and come back once your destination is set. ## **FAQ** ### **What is an intranet governance plan?** An intranet governance plan defines who owns content, how publishing works, how content stays current, how permissions are managed, and how the intranet is measured and improved over time. It is the operating system that keeps an intranet healthy after launch — not a one-time document. ### **Who should own intranet governance?** A dedicated intranet product owner is the most reliable model. IT typically owns platform administration and security, while HR, Communications, and Operations own content areas. Governance works best when ownership is shared, explicit, and tied to business outcomes — not treated as an IT responsibility alone. ### **How often should intranet content be reviewed?** It depends on the content type. Policies and SOPs typically need scheduled reviews every 6–12 months. News and announcements benefit from expiration and archiving rules so old content does not clutter search and erode trust. ### **How do you enforce governance without slowing publishing?** Use templates, clear content categories, and lightweight approvals only where they genuinely reduce risk. Distribute publishing rights broadly, define guardrails, and run a monthly governance review that produces decisions and assigns owners — not a committee that produces more meetings. ### **How do you handle governance for a frontline workforce?** Frontline governance requires explicit location owners, clear rules for what content is global versus local, defined translation ownership and review cycles, and shift-based targeting for critical updates. Without this structure, frontline content goes stale fast and adoption drops. See the Frontline Intranet Requirements guide for the detailed checklist. ### **What does a governance review meeting actually look like in practice?** A working monthly governance review runs 45–60 minutes and produces a short action list. The agenda covers wins and changes since last month, top problems in search and content health, decisions on what to fix or archive, owner assignments and due dates, and next month's priorities. If the meeting produces documents instead of decisions, simplify the format. ### **What is the biggest governance mistake during a SharePoint replacement?** Migrating content without assigning owners and review dates, then trying to fix governance after launch. That approach recreates intranet sprawl on a new platform within 12–18 months. Governance starts during discovery — not after go-live. --- # SharePoint Server 2016/2019 Migration Checklist: A Practical Plan to Replace Your Intranet Before End of Life **Author:** Andy Tolton **Published:** 2026-03-20 **Category:** intranet If your intranet is still on SharePoint Server 2016 or 2019, the clock is ticking — but the bigger risk is not the deadline. It is what happens when organizations rush. They move everything, carry forward the same cluttered structure and brittle workflows, and then wonder why adoption does not improve. This checklist is designed to prevent that. It is a phase-by-phase plan to help you migrate with control: discover what you actually have, cut scope before it cuts you, modernize workflows early, and roll out in waves so employees are never left stranded. If your intranet is still on SharePoint Server 2016/2019, you're probably holding two realities in your head at once. **Reality one:** it's familiar, it's integrated, and it still runs.**‍* **Reality two:** it's increasingly hard to maintain, harder to evolve, and harder to defend — especially as Microsoft's SharePoint 2016/2019 end of life date approaches. This guide is for teams actively searching for answers on SharePoint 2016/2019 end of life, end of support, alternatives, and replacement options. It explains what the deadline means in practical terms, what risks accumulate after the end of support, and how to choose the right replacement path based on your environment and your workforce. ## **SharePoint 2016/2019 end of life: the dates to plan around** The headline date is straightforward: - **SharePoint Server 2016/2019 end of extended support: July 14, 2026** After that, [SharePoint Server 2016](https://learn.microsoft.com/en-us/sharepoint/product-servicing-policy/updated-product-servicing-policy-for-sharepoint-server-2016) and [SharePoint Server 2019](https://learn.microsoft.com/en-us/sharepoint/product-servicing-policy/updated-product-servicing-policy-for-sharepoint-2019) become unsupported platforms. That does not mean they stop running. It means you own the risk in a fundamentally different way — without Microsoft security patches, compliance backing, or vendor support. There is also an earlier date that matters if your intranet modernization involves Microsoft 365: - **April 2, 2026: Microsoft 365 retires**[**SharePoint Add-ins**](https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/retirement-announcement-for-add-ins)**and**[**SharePoint 2013 workflows**](https://support.microsoft.com/en-us/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) If your SharePoint 2016/2019 environment relies on older add-ins or workflow patterns, those dependencies can complicate your modernization plans well before the July deadline. ## **What 'end of support' really means for SharePoint 2016/2019** A lot of teams treat the end of support like a procurement issue. In practice, it becomes a security, compliance, and operational resilience issue. After SharePoint 2016/2019 end of support: - **Security patching stops.** New vulnerabilities can still be discovered. Your ability to remediate becomes more limited and more expensive. - **Audit and compliance standards tighten.** Unsupported systems are commonly treated as exceptions — requiring documented risk acceptance, compensating controls, and a defined retirement plan. - **Operations become more fragile over time.** Browser changes, identity changes, integration drift, and institutional knowledge loss show up slowly, then all at once. If your intranet plays a business-critical role, keeping it alive indefinitely is rarely a defensible long-term position. ## **Why SharePoint 2016/2019 intranets are still common** If you're still on SharePoint 2016/2019, you are not alone. Most SharePoint 2016/2019 sites were never just intranets. Over the years, they became: - a policy and document hub - a workflow engine for approvals, requests, and forms - a home for custom web parts and department sites - a container for third-party add-ons - an integration point with identity, HR, and operational systems That layering is exactly why replacement projects stall. The platform decision is only one part. The bigger challenge is separating what the intranet should do today from what it has accumulated over time. ## **Risks of staying on SharePoint 2016/2019 after end of life** Most teams focus on "security updates stop" and stop there. The real risk picture is broader. ### **1) Security risk becomes permanent, not occasional** Unsupported software is not risky because it breaks. It is risky because it becomes predictable. Vulnerabilities continue to emerge, and attackers gravitate toward systems they know will not be patched. If your SharePoint environment is internet-reachable, connected to core identity systems, or serves as a gateway to sensitive documents, the potential impact compounds. ### **2) Compliance and governance become a constant negotiation** If you operate in regulated environments or follow established security frameworks, unsupported enterprise platforms are hard to justify without formal exceptions. That typically creates recurring overhead: security reviews, exception renewals, compensating controls, additional monitoring, and reduced change tolerance. Even if nothing goes wrong, the cost of defending the decision rises. ### **3) Operational risk grows quietly** This is the part that catches organizations off guard. Over time, SharePoint 2016/2019 environments tend to become dependent on a shrinking set of admins who know how it works, expensive to change due to fear of breaking customizations, and increasingly misaligned with how employees expect to find information — especially on mobile. When adoption declines, the intranet stops being the place people go first. [Research from Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) shows that while 91% of organizations have an intranet, only 13% of employees use it daily. On a legacy platform, that number tends to fall even further — pushing work into email, chat, and informal workarounds. That increases support load and reduces governance. ## **The real limitations of SharePoint 2016/2019 as an intranet in 2026** SharePoint 2016/2019 can still publish pages and store documents. That is no longer the bar. A modern intranet is expected to do five things consistently well: ### **1) Reach every employee, not only desk workers** A modern intranet replacement has to work for frontline employees, field teams, and managers on the move — with mobile-first access, push communications when needed, and experiences that do not assume a laptop. With [80% of the global workforce in frontline or deskless roles](https://hrexecutive.com/frontline-first-hr-engaging-the-80-that-powers-your-business/), a desk-only intranet is not an intranet. It is a tool for 20% of your people. ### **2) Make publishing simple enough to keep content healthy** Intranets decay when publishing is slow, overly technical, or centralized in IT. The strongest intranets distribute ownership while maintaining governance. A platform that only IT can update is a platform that employees stop trusting. ### **3) Make information easy to find** Search and navigation are not nice-to-haves. When employees cannot find policies, SOPs, forms, or answers, they ask people instead. McKinsey research shows employees spend [20% of their workday searching for information](https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy). A modern intranet with AI-powered search can cut that time by 25–35% — and reduce the repetitive HR and IT requests that follow. ### **4) Support governance without creating bureaucracy** A workable governance model includes ownership and accountability, review cycles, archiving, permissions and role-based publishing, and analytics. Without it, a migration just recreates the same problems in a new place. ### **5) Connect communications to action** Employees do not only need information. They need to complete tasks: read an update, acknowledge it, follow a procedure, submit a request, finish onboarding steps, or find the right person. An intranet becomes far more valuable when it reduces tool switching and turns communication into coordinated work. ‍ ## **SharePoint 2016/2019 replacement paths: what most organizations actually choose** When people search for SharePoint 2016/2019 alternatives, they usually want a short list. The reality is there are three primary paths, each with clear tradeoffs. ### **Option A: Migrate to SharePoint Server Subscription Edition (SPSE)** **What SPSE is:**SharePoint Server Subscription Edition is SharePoint's ongoing, subscription-based on-premises version. Instead of treating SharePoint like a one-time major release you refresh every several years, SPSE stays current through regular updates. **Why teams choose this:**If your biggest constraint is "we need SharePoint Server on-prem," SPSE typically creates the least disruption. You keep an on-prem SharePoint footprint and familiar SharePoint conventions while getting back onto a supported lifecycle. **What it does not solve:**Upgrading to SPSE reduces end-of-support risk, but it does not automatically modernize the intranet experience. If your SharePoint 2016/2019 intranet is held together with custom workflows, legacy pages, and "only IT can change it" publishing, those challenges carry forward. You still need a plan for reducing customization debt, rebuilding information architecture, improving mobile reach for frontline and field teams, and setting governance that prevents intranet sprawl. ### **Option B: Migrate to SharePoint Online (Microsoft 365)** **What SharePoint Online is:**SharePoint Online is Microsoft's cloud version of SharePoint, delivered as part of Microsoft 365. The platform is maintained and updated by Microsoft, removing on-prem infrastructure overhead. **Why teams choose this:**This is often the lowest-friction option for Microsoft-centric environments. It keeps the intranet inside the Microsoft ecosystem, aligns with existing identity and collaboration tooling, and eliminates a chunk of on-prem infrastructure burden. **What trips teams up:**SharePoint 2016/2019 intranets often include older customization and automation patterns that do not translate cleanly to the modern cloud model. SharePoint Add-ins stop working for all tenants on April 2, 2026, and SharePoint 2013 workflows will be removed from existing tenants on the same date. That means your plan needs to treat classic add-ins and legacy workflows as modernization projects — not things that will simply come along. ### **Option C: Replace SharePoint 2016/2019 with a dedicated intranet or employee experience platform** The third path is stepping back and asking a different question: do you want to keep rebuilding an intranet on SharePoint, or do you want to adopt a platform built specifically to run a modern intranet experience? **What this option is:**A dedicated intranet platform delivers the full intranet experience out of the box — publishing workflows, governance controls, search and knowledge experiences, and mobile reach for desk and frontline teams alike. **Why teams choose this:**This approach is usually chosen when the primary goal is not "stay on SharePoint" but improve adoption and reduce operational overhead. Instead of migrating the old structure as-is, organizations can rebuild information architecture, governance, and employee self-service in a cleaner model — with less dependency on custom development. **Where MangoApps fits:**[MangoApps](https://www.mangoapps.com/) is a unified AI-powered workforce platform built for exactly this reality. It unifies [intranet](https://www.mangoapps.com/solutions/modern-intranet), communications, knowledge, and operational work in one hub — reaching desk and frontline employees in a single connected experience, [typically deployed in 8–12 weeks](https://www.mangoapps.com/services/implementation-process). MangoApps customers consistently achieve 90% adoption rates with measurable impact within 90 days, and 98% of deployments are delivered on time and within budget. For organizations with strict data requirements, MangoApps also supports [on-premises deployment](https://www.mangoapps.com/services/add-ons). [Trusted by organizations](https://www.mangoapps.com/customers) including AutoZone, PetSmart, and TEAMHealth, and recognized as a Gartner Magic Quadrant Visionary for three consecutive years (2023–2025), MangoApps is a proven path [from SharePoint](https://www.mangoapps.com/sharepoint-alternatives) to a modern employee experience. ## **What to look for in SharePoint 2016/2019 alternatives and intranet replacement solutions** If you're evaluating a SharePoint intranet replacement, use criteria that reflect what actually drives adoption and long-term success — not feature checklists. ### **1) Migration reality: can you move what matters without dragging forward the mess?** A replacement platform should support structured migration of key content and knowledge, clean information architecture rebuilding (not only lift and shift), a practical approach to archiving stale material, and step-by-step modernization for workflows, forms, and approvals. ### **2) Frontline and mobile requirements** If you have shift-based or deskless teams, validate a true mobile-first experience — not a desktop site squeezed into a phone — along with easy access for employees without corporate email, role-based personalization by region, location, role, and team, and reliable delivery of critical updates. ### **3) Findability: search, navigation, and knowledge experience** Ask directly: can employees find policies and SOPs in seconds? Can they get clear answers without opening five tools? Does the platform reduce repetitive support requests? AI-powered search can cut the time employees spend looking for information by 25–30% — and that reduction shows up as fewer tickets and faster onboarding. ### **4) Publishing and governance at scale** Look for distributed publishing with approvals, clear ownership and review cycles, analytics on what is read, searched, and ignored, and guardrails that prevent intranet sprawl. ### **5) Security and administrative control** Especially for enterprise and regulated environments: access control and governance, data security model, auditing and compliance support, and a vendor with proven security certifications. [MangoApps holds](https://www.mangoapps.com/security-compliance) HITRUST, ISO-27001, and SOC 2 certifications, and maintains a 99.9% uptime SLA. ### **6) Integration without rip-and-replace** A modern intranet integrates with HRIS, identity, ticketing, storage, and other systems while providing one clean employee experience. [MangoApps connects with 200+ enterprise systems](https://www.mangoapps.com/integrations) — often enabling organizations to sunset multiple point solutions in the process. ## **A practical plan to replace SharePoint 2016/2019 without a chaotic migration** If you want a migration that does not become a multi-year drag, the sequence matters. ### **Phase 1: Discovery and dependency mapping** Inventory content types and ownership, workflows and custom code, integrations and identity dependencies, and usage patterns — what is critical versus what is ignored. ### **Phase 2: Information architecture and governance design** Define the target structure (not the current structure), publishing roles and approval flows, content standards and review cycles, and measurement and success metrics. ### **Phase 3: Pilot with real use cases** Start with critical policies and procedures, leadership communications, frontline location updates, and key service workflows employees use weekly. ### **Phase 4: Scale and retire SharePoint 2016/2019** Move in waves, measure adoption, retire what is redundant, and archive what is no longer needed. MangoApps has supported SharePoint-to-modern-intranet migrations on accelerated timelines measured in weeks, not months — when scope is controlled and rollout is designed as repeatable waves. A phased approach builds momentum and reduces risk. ## **Why MangoApps is a leading SharePoint 2016/2019 replacement for modern intranets** Many organizations searching for a SharePoint 2016/2019 replacement are not just shopping for an intranet. They are trying to solve fragmentation — too many tools, too little adoption, and an intranet that has become a maintenance burden instead of a business asset. [MangoApps](https://www.mangoapps.com/) is built for that reality. It unifies intranet, communications, knowledge, and operational work into one workforce platform that can be configured to match how your organization actually runs. That makes it a strong fit for organizations [replacing SharePoint 2016/2019](https://www.mangoapps.com/sharepoint-alternatives), especially when the goal is to: - reach both desk and frontline teams in one connected experience - reduce tool switching by connecting updates to tasks, procedures, and actions - make governance and publishing manageable without heavy IT involvement - improve findability and self-service so repetitive support requests drop - deploy and evolve quickly — with 98% of implementations delivered on time and within budget If SharePoint 2016/2019 has become hard to maintain and harder to modernize, MangoApps provides a cleaner path to an intranet your people will actually use — and leaders can trust. Learn more about the [MangoApps AI-Powered Intranet](https://www.mangoapps.com/solutions/modern-intranet), and explore how the [MangoApps Employee App](https://www.mangoapps.com/solutions/employee-app) supports frontline and deskless teams. Then see [MangoApps AI](https://www.mangoapps.com/ai)for self-service and knowledge access. [Schedule a demo](https://www.mangoapps.com/schedule-a-call) to see it in action. And if you require it, ask about our [on-premises deployment options](https://www.mangoapps.com/services/add-ons). ## **Frequently asked questions: SharePoint 2016/2019 end of life and replacement** ### **When is SharePoint 2016/2019 end of life?** SharePoint Server 2016/2019 reaches the end of extended support on July 14, 2026. ### **Can we keep using SharePoint 2016/2019 after end of support?** The platform may continue running, but it becomes unsupported. Most organizations in regulated environments treat this as a security and compliance risk that requires formal exceptions, compensating controls, and a time-bound retirement plan. The longer you wait, the more expensive those controls become. ### **What are the alternative options to SharePoint 2016/2019?** The main alternatives are: upgrading on-premises SharePoint to Subscription Edition (SPSE), migrating to SharePoint Online, or replacing SharePoint 2016/2019 with a dedicated intranet or employee experience platform such as MangoApps. ### **What is the best way to plan a SharePoint 2016/2019 intranet replacement?** Start with dependency mapping and governance design — inventory what you have, identify what can be retired or archived, and define what must be rebuilt. Then run a phased rollout focused on high-value use cases and measurable adoption. Teams that keep scope tight and treat rollout as repeatable waves move fastest. MangoApps Success Services can help you move quickly without cutting corners. ### **How long does a SharePoint intranet replacement take?** With tight scope control, organizations can migrate from SharePoint to a modern intranet in weeks. MangoApps' typical implementation timeline is 8–12 weeks, and 98% of deployments are delivered on time and within budget. The biggest timeline variables are workflow modernization complexity and how much content you choose to carry forward versus archive. --- # SharePoint 2016/2019 End of Life: Timeline, Risks, Migration, and Replacement Option Resources **Author:** Andy Tolton **Published:** 2026-03-20 **Category:** intranet This guide is for teams actively searching for answers on SharePoint 2016/2019 end of life, end of support, alternatives, and replacement options. It explains what the deadline means in practical terms, what risks accumulate after the end of support, and how to choose the right replacement path based on your environment and your workforce. If your intranet is still on SharePoint Server 2016/2019, you're probably holding two realities in your head at once. **Reality one:** it's familiar, it's integrated, and it still runs.**‍* **Reality two:** it's increasingly hard to maintain, harder to evolve, and harder to defend — especially as Microsoft's SharePoint 2016/2019 end of life date approaches. This guide is for teams actively searching for answers on SharePoint 2016/2019 end of life, end of support, alternatives, and replacement options. It explains what the deadline means in practical terms, what risks accumulate after the end of support, and how to choose the right replacement path based on your environment and your workforce. ## **SharePoint 2016/2019 end of life: the dates to plan around** The headline date is straightforward: - **SharePoint Server 2016/2019 end of extended support: July 14, 2026** After that, [SharePoint Server 2016](https://learn.microsoft.com/en-us/sharepoint/product-servicing-policy/updated-product-servicing-policy-for-sharepoint-server-2016) and [SharePoint Server 2019](https://learn.microsoft.com/en-us/sharepoint/product-servicing-policy/updated-product-servicing-policy-for-sharepoint-2019) become unsupported platforms. That does not mean they stop running. It means you own the risk in a fundamentally different way — without Microsoft security patches, compliance backing, or vendor support. There is also an earlier date that matters if your intranet modernization involves Microsoft 365: - **April 2, 2026: Microsoft 365 retires**[**SharePoint Add-ins**](https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/retirement-announcement-for-add-ins)**and**[**SharePoint 2013 workflows**](https://support.microsoft.com/en-us/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) If your SharePoint 2016/2019 environment relies on older add-ins or workflow patterns, those dependencies can complicate your modernization plans well before the July deadline. ## **What 'end of support' really means for SharePoint 2016/2019** A lot of teams treat the end of support like a procurement issue. In practice, it becomes a security, compliance, and operational resilience issue. After SharePoint 2016/2019 end of support: - **Security patching stops.** New vulnerabilities can still be discovered. Your ability to remediate becomes more limited and more expensive. - **Audit and compliance standards tighten.** Unsupported systems are commonly treated as exceptions — requiring documented risk acceptance, compensating controls, and a defined retirement plan. - **Operations become more fragile over time.** Browser changes, identity changes, integration drift, and institutional knowledge loss show up slowly, then all at once. If your intranet plays a business-critical role, keeping it alive indefinitely is rarely a defensible long-term position. ## **Why SharePoint 2016/2019 intranets are still common** If you're still on SharePoint 2016/2019, you are not alone. Most SharePoint 2016/2019 sites were never just intranets. Over the years, they became: - a policy and document hub - a workflow engine for approvals, requests, and forms - a home for custom web parts and department sites - a container for third-party add-ons - an integration point with identity, HR, and operational systems That layering is exactly why replacement projects stall. The platform decision is only one part. The bigger challenge is separating what the intranet should do today from what it has accumulated over time. ## **Risks of staying on SharePoint 2016/2019 after end of life** Most teams focus on "security updates stop" and stop there. The real risk picture is broader. ### **1) Security risk becomes permanent, not occasional** Unsupported software is not risky because it breaks. It is risky because it becomes predictable. Vulnerabilities continue to emerge, and attackers gravitate toward systems they know will not be patched. If your SharePoint environment is internet-reachable, connected to core identity systems, or serves as a gateway to sensitive documents, the potential impact compounds. ### **2) Compliance and governance become a constant negotiation** If you operate in regulated environments or follow established security frameworks, unsupported enterprise platforms are hard to justify without formal exceptions. That typically creates recurring overhead: security reviews, exception renewals, compensating controls, additional monitoring, and reduced change tolerance. Even if nothing goes wrong, the cost of defending the decision rises. ### **3) Operational risk grows quietly** This is the part that catches organizations off guard. Over time, SharePoint 2016/2019 environments tend to become dependent on a shrinking set of admins who know how it works, expensive to change due to fear of breaking customizations, and increasingly misaligned with how employees expect to find information — especially on mobile. When adoption declines, the intranet stops being the place people go first. [Research from Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) shows that while 91% of organizations have an intranet, only 13% of employees use it daily. On a legacy platform, that number tends to fall even further — pushing work into email, chat, and informal workarounds. That increases support load and reduces governance. ## **The real limitations of SharePoint 2016/2019 as an intranet in 2026** SharePoint 2016/2019 can still publish pages and store documents. That is no longer the bar. A modern intranet is expected to do five things consistently well: ### **1) Reach every employee, not only desk workers** A modern intranet replacement has to work for frontline employees, field teams, and managers on the move — with mobile-first access, push communications when needed, and experiences that do not assume a laptop. With [80% of the global workforce in frontline or deskless roles](https://hrexecutive.com/frontline-first-hr-engaging-the-80-that-powers-your-business/), a desk-only intranet is not an intranet. It is a tool for 20% of your people. ### **2) Make publishing simple enough to keep content healthy** Intranets decay when publishing is slow, overly technical, or centralized in IT. The strongest intranets distribute ownership while maintaining governance. A platform that only IT can update is a platform that employees stop trusting. ### **3) Make information easy to find** Search and navigation are not nice-to-haves. When employees cannot find policies, SOPs, forms, or answers, they ask people instead. McKinsey research shows employees spend [20% of their workday searching for information](https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy). A modern intranet with AI-powered search can cut that time by 25–35% — and reduce the repetitive HR and IT requests that follow. ### **4) Support governance without creating bureaucracy** A workable governance model includes ownership and accountability, review cycles, archiving, permissions and role-based publishing, and analytics. Without it, a migration just recreates the same problems in a new place. ### **5) Connect communications to action** Employees do not only need information. They need to complete tasks: read an update, acknowledge it, follow a procedure, submit a request, finish onboarding steps, or find the right person. An intranet becomes far more valuable when it reduces tool switching and turns communication into coordinated work. ‍ ## **SharePoint 2016/2019 replacement paths: what most organizations actually choose** When people search for SharePoint 2016/2019 alternatives, they usually want a short list. The reality is there are three primary paths, each with clear tradeoffs. ### **Option A: Migrate to SharePoint Server Subscription Edition (SPSE)** **What SPSE is:**SharePoint Server Subscription Edition is SharePoint's ongoing, subscription-based on-premises version. Instead of treating SharePoint like a one-time major release you refresh every several years, SPSE stays current through regular updates. **Why teams choose this:**If your biggest constraint is "we need SharePoint Server on-prem," SPSE typically creates the least disruption. You keep an on-prem SharePoint footprint and familiar SharePoint conventions while getting back onto a supported lifecycle. **What it does not solve:**Upgrading to SPSE reduces end-of-support risk, but it does not automatically modernize the intranet experience. If your SharePoint 2016/2019 intranet is held together with custom workflows, legacy pages, and "only IT can change it" publishing, those challenges carry forward. You still need a plan for reducing customization debt, rebuilding information architecture, improving mobile reach for frontline and field teams, and setting governance that prevents intranet sprawl. ### **Option B: Migrate to SharePoint Online (Microsoft 365)** **What SharePoint Online is:**SharePoint Online is Microsoft's cloud version of SharePoint, delivered as part of Microsoft 365. The platform is maintained and updated by Microsoft, removing on-prem infrastructure overhead. **Why teams choose this:**This is often the lowest-friction option for Microsoft-centric environments. It keeps the intranet inside the Microsoft ecosystem, aligns with existing identity and collaboration tooling, and eliminates a chunk of on-prem infrastructure burden. **What trips teams up:**SharePoint 2016/2019 intranets often include older customization and automation patterns that do not translate cleanly to the modern cloud model. SharePoint Add-ins stop working for all tenants on April 2, 2026, and SharePoint 2013 workflows will be removed from existing tenants on the same date. That means your plan needs to treat classic add-ins and legacy workflows as modernization projects — not things that will simply come along. ### **Option C: Replace SharePoint 2016/2019 with a dedicated intranet or employee experience platform** The third path is stepping back and asking a different question: do you want to keep rebuilding an intranet on SharePoint, or do you want to adopt a platform built specifically to run a modern intranet experience? **What this option is:**A dedicated intranet platform delivers the full intranet experience out of the box — publishing workflows, governance controls, search and knowledge experiences, and mobile reach for desk and frontline teams alike. **Why teams choose this:**This approach is usually chosen when the primary goal is not "stay on SharePoint" but improve adoption and reduce operational overhead. Instead of migrating the old structure as-is, organizations can rebuild information architecture, governance, and employee self-service in a cleaner model — with less dependency on custom development. **Where MangoApps fits:**[MangoApps](https://www.mangoapps.com/) is a unified AI-powered workforce platform built for exactly this reality. It unifies [intranet](https://www.mangoapps.com/solutions/modern-intranet), communications, knowledge, and operational work in one hub — reaching desk and frontline employees in a single connected experience, [typically deployed in 8–12 weeks](https://www.mangoapps.com/services/implementation-process). MangoApps customers consistently achieve 90% adoption rates with measurable impact within 90 days, and 98% of deployments are delivered on time and within budget. For organizations with strict data requirements, MangoApps also supports [on-premises deployment](https://www.mangoapps.com/services/add-ons). [Trusted by organizations](https://www.mangoapps.com/customers) including AutoZone, PetSmart, and TEAMHealth, and recognized as a Gartner Magic Quadrant Visionary for three consecutive years (2023–2025), MangoApps is a proven path [from SharePoint](https://www.mangoapps.com/sharepoint-alternatives) to a modern employee experience. ## **What to look for in SharePoint 2016/2019 alternatives and intranet replacement solutions** If you're evaluating a SharePoint intranet replacement, use criteria that reflect what actually drives adoption and long-term success — not feature checklists. ### **1) Migration reality: can you move what matters without dragging forward the mess?** A replacement platform should support structured migration of key content and knowledge, clean information architecture rebuilding (not only lift and shift), a practical approach to archiving stale material, and step-by-step modernization for workflows, forms, and approvals. ### **2) Frontline and mobile requirements** If you have shift-based or deskless teams, validate a true mobile-first experience — not a desktop site squeezed into a phone — along with easy access for employees without corporate email, role-based personalization by region, location, role, and team, and reliable delivery of critical updates. ### **3) Findability: search, navigation, and knowledge experience** Ask directly: can employees find policies and SOPs in seconds? Can they get clear answers without opening five tools? Does the platform reduce repetitive support requests? AI-powered search can cut the time employees spend looking for information by 25–30% — and that reduction shows up as fewer tickets and faster onboarding. ### **4) Publishing and governance at scale** Look for distributed publishing with approvals, clear ownership and review cycles, analytics on what is read, searched, and ignored, and guardrails that prevent intranet sprawl. ### **5) Security and administrative control** Especially for enterprise and regulated environments: access control and governance, data security model, auditing and compliance support, and a vendor with proven security certifications. [MangoApps holds](https://www.mangoapps.com/security-compliance) HITRUST, ISO-27001, and SOC 2 certifications, and maintains a 99.9% uptime SLA. ### **6) Integration without rip-and-replace** A modern intranet integrates with HRIS, identity, ticketing, storage, and other systems while providing one clean employee experience. [MangoApps connects with 200+ enterprise systems](https://www.mangoapps.com/integrations) — often enabling organizations to sunset multiple point solutions in the process. ## **A practical plan to replace SharePoint 2016/2019 without a chaotic migration** If you want a migration that does not become a multi-year drag, the sequence matters. ### **Phase 1: Discovery and dependency mapping** Inventory content types and ownership, workflows and custom code, integrations and identity dependencies, and usage patterns — what is critical versus what is ignored. ### **Phase 2: Information architecture and governance design** Define the target structure (not the current structure), publishing roles and approval flows, content standards and review cycles, and measurement and success metrics. ### **Phase 3: Pilot with real use cases** Start with critical policies and procedures, leadership communications, frontline location updates, and key service workflows employees use weekly. ### **Phase 4: Scale and retire SharePoint 2016/2019** Move in waves, measure adoption, retire what is redundant, and archive what is no longer needed. MangoApps has supported SharePoint-to-modern-intranet migrations on accelerated timelines measured in weeks, not months — when scope is controlled and rollout is designed as repeatable waves. A phased approach builds momentum and reduces risk. ## **Why MangoApps is a leading SharePoint 2016/2019 replacement for modern intranets** Many organizations searching for a SharePoint 2016/2019 replacement are not just shopping for an intranet. They are trying to solve fragmentation — too many tools, too little adoption, and an intranet that has become a maintenance burden instead of a business asset. [MangoApps](https://www.mangoapps.com/) is built for that reality. It unifies intranet, communications, knowledge, and operational work into one workforce platform that can be configured to match how your organization actually runs. That makes it a strong fit for organizations [replacing SharePoint 2016/2019](https://www.mangoapps.com/sharepoint-alternatives), especially when the goal is to: - reach both desk and frontline teams in one connected experience - reduce tool switching by connecting updates to tasks, procedures, and actions - make governance and publishing manageable without heavy IT involvement - improve findability and self-service so repetitive support requests drop - deploy and evolve quickly — with 98% of implementations delivered on time and within budget If SharePoint 2016/2019 has become hard to maintain and harder to modernize, MangoApps provides a cleaner path to an intranet your people will actually use — and leaders can trust. Learn more about the [MangoApps AI-Powered Intranet](https://www.mangoapps.com/solutions/modern-intranet), and explore how the [MangoApps Employee App](https://www.mangoapps.com/solutions/employee-app) supports frontline and deskless teams. Then see [MangoApps AI](https://www.mangoapps.com/ai)for self-service and knowledge access. [Schedule a demo](https://www.mangoapps.com/schedule-a-call) to see it in action. And if you require it, ask about our [on-premises deployment options](https://www.mangoapps.com/services/add-ons). ## **Frequently asked questions: SharePoint 2016/2019 end of life and replacement** ### **When is SharePoint 2016/2019 end of life?** SharePoint Server 2016/2019 reaches the end of extended support on July 14, 2026. ### **Can we keep using SharePoint 2016/2019 after end of support?** The platform may continue running, but it becomes unsupported. Most organizations in regulated environments treat this as a security and compliance risk that requires formal exceptions, compensating controls, and a time-bound retirement plan. The longer you wait, the more expensive those controls become. ### **What are the alternative options to SharePoint 2016/2019?** The main alternatives are: upgrading on-premises SharePoint to Subscription Edition (SPSE), migrating to SharePoint Online, or replacing SharePoint 2016/2019 with a dedicated intranet or employee experience platform such as MangoApps. ### **What is the best way to plan a SharePoint 2016/2019 intranet replacement?** Start with dependency mapping and governance design — inventory what you have, identify what can be retired or archived, and define what must be rebuilt. Then run a phased rollout focused on high-value use cases and measurable adoption. Teams that keep scope tight and treat rollout as repeatable waves move fastest. MangoApps Success Services can help you move quickly without cutting corners. ### **How long does a SharePoint intranet replacement take?** With tight scope control, organizations can migrate from SharePoint to a modern intranet in weeks. MangoApps' typical implementation timeline is 8–12 weeks, and 98% of deployments are delivered on time and within budget. The biggest timeline variables are workflow modernization complexity and how much content you choose to carry forward versus archive. --- # The Shift in Workforce AI: From Insights to Action **Author:** MangoApps Team **Published:** 2026-03-15 **Category:** news-and-updates A manager gets an alert that three of her team members are flagged as retention risks. She clicks through to a dashboard, sees the performance data, reads the AI-generated summary, and then —... # The Shift in Workforce AI: From Insights to Action A manager gets an alert that three of her team members are flagged as retention risks. She clicks through to a dashboard, sees the performance data, reads the AI-generated summary, and then — closes the tab. She'll send the feedback later. She'll start those reviews next week. The insight sat in a report. The work sat in her to-do list. This is the gap that has defined most workplace AI: the moment between knowing and doing. Surfacing information has gotten very good. Acting on it has stayed stubbornly manual. This week's releases suggest that's starting to change — not through automation that removes humans from decisions, but through AI that stays with you through the action itself. --- ## The Insight-Action Gap Most HR and workforce software spent the last few years getting very good at surfaces: dashboards, trend reports, risk signals, AI summaries. The surfaces got smarter. But the action still required a human to close the loop manually — navigate to a different screen, find the right form, submit the review, send the letter. The most direct answer to this came this week with [Performance AI Team Insights](https://www.mangoapps.com/changelog/2924). Managers and HR admins can now ask the AI assistant to surface team-level performance reviews, goals, feedback, and retention risk signals — and then, without leaving the conversation, submit that feedback, kick off a review, or draft a reward letter. The insight and the action live in the same place. The design choice here matters more than the feature itself. Traditional HR software assumes that information and action are separate concerns: you look at the data, then you go do the thing. AI Team Insights doesn't make that assumption. It assumes you want to move from understanding to action in one flow, and it supports that without asking you to change contexts. [AI Home](https://www.mangoapps.com/changelog/2925) extends this logic across all HR responsibilities. Instead of navigating to individual modules to check what needs attention, a single dedicated page now surfaces AI-prioritized action items from across the platform. This is different from a notification inbox or a status dashboard. Notifications tell you something happened. Dashboards show you current state. AI-prioritized action items tell you what matters right now — and sit ready for you to act on them in the same place. For HR leaders managing complex cycles of reviews, feedback, hiring, and compliance, the distinction between "I can see what needs doing" and "I can do it from here" is where most of the friction actually lives. --- ## Where the Pattern Repeats The same shift shows up in two other product areas this week, which is what makes it feel like a genuine direction rather than a one-off feature. The [Field Service AI Agent](https://www.mangoapps.com/changelog/2920) can answer questions about work orders, dispatch, estimates, invoices, and your pricebook — but also act on them. A dispatcher asking about an open work order doesn't just get a summary; the agent can help move it forward without requiring a switch to a different view or module. For field operations teams handling dozens of concurrent jobs, that difference adds up across a shift. In [Libraries](https://www.mangoapps.com/changelog/2921), the AI assistant lets employees search and discover company resources in plain language — and lets admins create and manage library items directly through the conversation. The AI becomes an interface layer over the system, not a tooltip sitting on top of it. An employee who can't find the safety protocol they need doesn't have to learn the folder structure; they just ask. An admin who wants to add a new resource doesn't have to navigate the full form — they can do it through the same assistant. The [Reporting Agent](https://www.mangoapps.com/changelog/2917), which already generates data reports on request, now lets users export those reports as professional PDFs with embedded charts and share them directly with teammates. The completion of that loop — from question to report to shareable artifact — in one workflow is another instance of the same pattern. --- ## The Platform Context That Makes It Possible AI that can submit feedback on a performance review needs to know who the employee is, what cycle is open, what the review criteria are, and whether the manager has the right permissions. That kind of context only exists when the AI is embedded in the platform — not sitting alongside it as a separate tool. Several other releases this week reinforce that foundation quietly. [Time Off Visibility in Scheduling](https://www.mangoapps.com/changelog/2922) means that when employees look at their shifts, they see approved leave, pending requests, and scheduled hours in the same view — no toggling. Managers scheduling for the week have the context they need to make the right decision, not a partial picture. [Service Desk Access Requests](https://www.mangoapps.com/changelog/2921) create an automated provisioning workflow: when an employee needs access to a group or system, the approval, provisioning, and notification happen in sequence without manual handoffs between IT, HR, and the requester. [Microsoft Teams Notifications for Service Desk](https://www.mangoapps.com/changelog/2920) bring ticket status changes into the channel where teams already work — so the loop closes there rather than requiring a return visit to a separate tool. These aren't AI features. But they're part of the same architecture: a platform where context flows between systems, so that action can follow insight naturally, without the friction of manually bridging disconnected tools. --- ## The Bigger Picture The most interesting question in enterprise software right now isn't whether AI can surface good information. Most platforms have gotten reasonably good at that. The harder question is whether AI can close the loop — whether it can stay with you through the action, not just deliver the briefing. This week's releases advance that question across several of the most critical workflows in frontline workforce management: performance management, field operations, HR administration, and knowledge access. The pattern is consistent: AI embedded in workflows, not layered on top of them, so that the distance between knowing and doing shrinks. For organizations where managers are stretched across dozens of direct reports and operational decisions happen in real time, that distance has always been the expensive part. Not because managers lack judgment — but because the tools have historically required them to translate their judgment into a sequence of manual steps across disconnected systems. When that sequence shortens, more decisions get made. More feedback gets sent. More reviews get completed on time. The retention risk flagged on Monday gets a response before Friday, instead of sitting in someone's tab queue. That's what this week looks like at the product level. At the operational level, it's worth paying attention to. --- # MangoApps Named to KMWorld 100 Companies That Matter in Knowledge Management for 2026 **Author:** The MangoApps Team **Published:** 2026-03-09 **Category:** news-and-updates We're proud to announce that MangoApps has once again been named to the KMWorld 100 Companies That Matter in Knowledge Management, this time for 2026. Being recognized two years running is a meaningful signal: the knowledge management challenges organizations face are getting harder, and the bar for solving them keeps rising. We're proud to announce that MangoApps has once again been named to the [**KMWorld 100 Companies That Matter in Knowledge Management**](https://www.kmworld.com/Articles/Editorial/Features/KMWorld-100-Companies-That-Matter-in-Knowledge-Management-2026-172924.aspx), this time for 2026. Being recognized two years running is a meaningful signal: the knowledge management challenges organizations face are getting harder, and the bar for solving them keeps rising. We think this recognition reflects something important about where MangoApps is headed and where the market is going. ### What Is the KMWorld 100? Each year, [KMWorld](https://www.kmworld.com/), one of the most respected publications covering knowledge and information management, identifies the 100 companies making the most meaningful impact on how organizations capture, organize, surface, and act on knowledge. The list isn't a popularity contest. It recognizes companies demonstrating real technological leadership, a measurable presence in the market, and a genuine ability to solve the knowledge challenges modern organizations struggle with most. Making the list once is an honor. Being named again means the work is compounding. ### Why Knowledge Management Is Harder Than It Looks Most organizations don't have a knowledge shortage, they have a knowledge access problem. The information exists. It's buried in a shared drive, locked in a department wiki no one updates, living in the heads of employees who've been with the company for 12 years, or scattered across six different tools that don't talk to each other. For desk-based workers, this is frustrating. For frontline employees, the[80% of the global workforce](https://hrtechfeed.com/frontline-first-hr-engaging-the-80-that-powers-your-business/) without a desk or a company email address, it's often a dead end. They can't find the policy they need before a customer interaction. They don't know the updated procedure went out last Tuesday. They're making decisions with incomplete information because no one built the system with them in mind. That's the problem MangoApps was built to fix. ### What Sets MangoApps Apart in 2026 Being recognized on the KMWorld 100 this year means something different than it did 12 months ago. The conversation in knowledge management has shifted decisively toward AI, not just as a feature, but  as the connective layer that makes knowledge actually usable at scale. MangoApps has been building toward this for years. [MangoApps AI](https://www.mangoapps.com/ai)doesn't just give employees a chatbot. It gives every person in your organization, from the VP of HR at corporate to the shift supervisor at a distribution center, an intelligent assistant trained on your company's own knowledge. It surfaces the right information at the right moment, answers questions grounded in real internal content, and works across languages and devices so no one gets left behind. A few things that continue to distinguish the platform: **AI-powered knowledge discovery that works for everyone.** [Our unified search and AI assistants](https://www.mangoapps.com/ai) pull from across your systems — not just the intranet, but the tools your teams actually use — so employees spend less time hunting and more time working. This capability is available on mobile, in 50+ languages, and designed specifically to reach frontline workers who've never had this kind of access before. [**One platform**](https://www.mangoapps.com/platform)**instead of a fragmented stack.** Knowledge doesn't live in one place — but the experience of accessing it should feel like it does. MangoApps unifies intranet, employee communications, workforce operations, HR, and AI in a single hub. Customers routinely sunset multiple point solutions after go-live. That consolidation isn't just a cost story; it's a knowledge management story. When information flows through one connected system, it's findable. [**Security and compliance**](https://www.mangoapps.com/security-compliance)**built for enterprise.** MangoApps is the only employee experience platform with active HITRUST certification, alongside ISO-27001 and SOC 2. For industries like healthcare, financial services, and retail — where knowledge access and data governance have to coexist — this matters. **Adoption that actually happens.** Recognition only counts if [customers](https://www.mangoapps.com/customers) use the platform. We see 90% adoption rates within 90 days, 95% customer retention year over year, and 98% of deployments delivered on time and on budget. Knowledge management only creates value when people engage with it. ### What This Recognition Means to Us MangoApps has been in this market for over 15 years, serving more than 2 million users worldwide. We've watched knowledge management evolve from static intranets and document libraries to AI-driven, mobile-first platforms that need to work for a nurse on a 12-hour shift as well as they do for a knowledge worker in a corner office. The KMWorld 100 recognition — two years in a row now — confirms that what we're building resonates. Not just with analysts, but with the customers we serve in healthcare, retail, manufacturing, hospitality, and beyond. We're grateful to KMWorld for this recognition, and more grateful to the customers and teams who make the platform worth recognizing. > *Interested in seeing how MangoApps approaches knowledge management for your organization?*[*Request a personalized demo*](https://www.mangoapps.com/schedule-a-call)*and we'll show you what's possible.* --- # Performance Reviews Finally Built for the Frontline Workforce **Author:** MangoApps Team **Published:** 2026-03-08 **Category:** news-and-updates A distribution center manager gets the email in January: annual performance review cycle is starting. She manages 65 people across two shifts. # Performance Reviews Finally Built for the Frontline Workforce A distribution center manager gets the email in January: annual performance review cycle is starting. She manages 65 people across two shifts. The HR system expects her to open each employee's review individually, rate them on a five-point scale written for a consulting firm, and wait for self-assessments that employees are supposed to complete on a shared computer in the break room — if they remember, if they have time, if the computer is available. She does what most frontline managers do. She waits until the deadline week, works through the reviews as fast as she can, and files assessments that say almost nothing meaningful. Her employees get ratings that feel arbitrary because the language doesn't match what they actually do. The process generates a paper trail. It does not generate development. The problem was never motivation. It was infrastructure. Performance management was designed for knowledge workers with dedicated computers, calendars, and the time to sit in a room and talk about career trajectories. When that same system gets applied to shift workers, field technicians, or healthcare aides, it produces compliance theater — the appearance of managing performance without any of the actual practice. Per Emergence Capital, 80% of the global workforce is deskless — yet most performance management tools were built for the other 20%. Three releases this week directly dismantle three different pieces of that friction. --- ## The Scale Problem: One at a Time Doesn't Work at 65 Reports For managers with large teams, the mechanics of launching a review cycle can be a half-day task on their own. Opening each employee's record, finding the review template, assigning it, moving on to the next. At five minutes per person, sixty-five people is more than five hours of administrative clicking before any actual management work begins. Bulk Performance Review Assignment compresses that to a few minutes. Admins work through a three-step wizard: filter the employee population (by department, location, role, or any combination), preview the list to confirm who's included, and confirm. The reviews are assigned. What used to be a logistical bottleneck becomes a setup step. This matters more than it might appear on the surface. One of the quiet reasons frontline performance reviews get deprioritized is that they cost more overhead per employee than office-based reviews do. The manager-to-employee ratios are higher. The workforce turns over faster, which means review lists are always slightly out of date. Integrating HRIS data to auto-sync employee roles and review assignments eliminates that stale-roster problem — so the list that greets a manager at cycle start actually reflects who's on the floor today. The administrative friction compounds. Reducing that friction doesn't make performance management effortless — but it removes one of the legitimate reasons HR teams delay, abbreviate, or skip cycles altogether. Frontline-specific performance platforms can reduce manager administrative time on review cycles by automating assignment, routing, and approval, freeing time for actual coaching conversations rather than system navigation. When setup takes minutes instead of hours, the calculus on whether to run a mid-year check-in changes. For a deeper look at how [modern HCM](/solutions/modern-hcm) approaches these structural barriers, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the shift in detail. --- ## The Access Problem: Performance Management Assumes a Desk Even when a review is assigned, getting employees to complete self-assessments is a different challenge on the floor than it is in an office. A knowledge worker opens the request in their browser between meetings. A warehouse associate would need to find an available kiosk, log in, navigate to the HR system, and hope they have enough time before their next task begins. The result is predictable: self-assessments get skipped, or completed in a rush, or filled out by a manager who's given up waiting. The part of the process most likely to generate useful employee perspective gets dropped. EPMS Mobile Full Parity changes the premise. Employees can now complete self-assessments, submit goals, and track their review progress entirely from a phone — on their own device, without requiring company email, VPN, or a desk. Managers can edit reviews, approve or reject goals, and submit for approval from mobile as well. The entire performance management workflow — not a simplified version of it, but the full feature set — is now available without a desktop. That shift in access changes the realistic completion rate for self-assessments. A manufacturing associate can fill out their self-assessment during a break, from their own device, without navigating a shared computer. A field technician's manager can review and approve a goal submission between site visits. The process meets people where they are rather than requiring them to travel to the process. In comparable deployments, mobile-first access has driven frontline adoption rates of 90% within the first six months — a benchmark from large retail pharmacy rollouts where mobile access was the default rather than an afterthought. There's also a less obvious effect: when employees can see their goals and review status from their phones, performance management stops being something that happens to them once a year and starts being something they can actually track and engage with. That's the precondition for the process meaning anything — and it's the same logic behind [why learning and development strategy fails when it isn't embedded in daily work](/articles/learning-and-development-strategy-embedded-in-daily-work). The [employee engagement](/solutions/employee-app) infrastructure and the performance infrastructure share the same access barriers; solving one tends to unlock the other. --- ## The Language Problem: Generic Scales Produce Generic Feedback Even when the review gets completed, there's a third failure mode: the language doesn't fit the work. Most performance management systems ship with a default rating scale — "does not meet expectations," "meets expectations," "exceeds expectations" — written for a generic corporate context. Those phrases carry meaning in environments where expectations are already well-defined and shared. On a manufacturing floor, in a distribution center, or across a field service team, they carry almost no meaning. What does "exceeds expectations" mean for a technician who closes fifteen tickets per shift versus one who resolves complex escalations? What does "meets expectations" mean for a nurse on a high-acuity unit? When managers can't answer those questions, ratings drift toward the middle. Not because everyone is average, but because the language doesn't give managers the vocabulary to express differentiation with confidence. Employees read middle-of-the-road ratings as a signal that their manager didn't really think about it — which is often accurate. Customizable Rating Scale Labels lets business admins rename and rewrite the descriptions for each rating level to match their organization's language and culture. A healthcare network can write scale descriptions that resonate with clinical staff. A logistics company can anchor ratings to concrete operational benchmarks. The rating scale becomes a shared vocabulary rather than a borrowed one. The downstream effect is more credible feedback. When a manager can point to a rating level with a description that actually describes the work, the conversation around that rating becomes easier — for both the manager giving it and the employee receiving it. For organizations ready to move beyond the annual cycle entirely, [Break The Annual Review Cycle: The Executive's Guide To Creating A Culture Of Continuous Employee Development](/resources/break-the-annual-review-cycle) maps out what that transition looks like in practice. --- ## The Pattern Extends Beyond Performance The same logic — tools should meet people where they actually work, not require people to adapt to the tools — showed up in other parts of the platform this week as well. The new Libraries app gives organizations a structured place to put documents, links, and resources that employees actually need: compliance materials, SOPs, policy guides. Searchable, organized, permission-controlled. Employees already spend an average of 2.5 hours per day searching for information, per IDC — a Libraries app that surfaces the right SOP operations documentation at the right moment directly cuts into that cost. The Go1 content library integration brings external training content directly into the Training app, with employee accounts provisioned automatically. Both releases reduce the distance between employees and the resources they need to do their jobs well — the same distance that performance management has always struggled with. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading organizations are closing that gap across training, communications, and HR workflows. --- ## Why This Matters Beyond the Releases There's a version of performance management that is purely administrative — a checkbox HR runs to satisfy legal and policy requirements, producing ratings that no one reads and feedback that changes nothing. Most frontline organizations are living in that version right now, not because they don't care about employee development, but because the tools make the meaningful version too expensive to run consistently. The releases this week don't solve every dimension of that problem. Culture, manager skill, time, and organizational will still matter. But they remove three specific structural reasons why the process breaks down: the setup overhead that delays or cancels cycles, the access gap that loses employee voice, and the language mismatch that produces meaningless ratings. For frontline teams, the path from compliance theater to genuine development runs through infrastructure. Fix the infrastructure — bulk assignment, mobile parity, customizable language — and the conversations that actually change performance become possible. That's what's shifting. --- ## How Do I Actually Implement This for My Frontline Team? The three features above address distinct failure points, and the implementation sequence matters. Start with bulk assignment: if your HR team is still opening individual records to launch a cycle, that overhead is the first thing to eliminate. Configure your employee population filters by department or location, run a pilot cycle with one shift or one site, and confirm completion rates before scaling. Mobile access is the second lever. Before your next cycle, audit what percentage of your frontline employees have completed a self-assessment in the last 12 months. If that number is below 60%, the access barrier — not motivation — is almost certainly the cause. Enabling EPMS mobile parity and communicating to employees that they can complete reviews from their own phones typically moves that number significantly. Organizations that have made mobile access the default, rather than a fallback, have seen frontline adoption reach 90% within six months in comparable deployments. Customizable rating scales come third, because they require the most internal alignment. Bring together frontline managers and HR to draft language that reflects actual job expectations — not generic corporate phrasing. Anchor each rating level to observable behaviors or measurable outputs. Pilot the new language with a small manager cohort before rolling it out platform-wide. For teams managing unionized workforces, implementation sequencing carries additional considerations — [Managing a Unionized Workforce Is Different. Your Software Should Be Too.](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) covers the specific constraints that affect review design and rollout. --- ## What's the ROI of Fixing Frontline Performance Reviews? The business case for investing in frontline performance infrastructure is more concrete than it might appear. The administrative time savings from bulk assignment alone — compressing a five-hour setup task to minutes — frees manager capacity for coaching, which is where performance improvement actually happens. Beyond time savings, mobile-first onboarding and performance workflows share the same access infrastructure. Organizations that have made training and performance mobile-accessible have reported 50% faster new-hire onboarding — relevant because onboarding and review cycles face identical access barriers for frontline workers. Closing those barriers once tends to pay dividends across both. Employee engagement is the longer-term return. When frontline employees can see their goals, track their review status, and receive feedback written in language that reflects their actual work, the review process shifts from something that happens to them into something they participate in. That shift in employee engagement is measurable: it shows up in survey scores, retention rates, and the quality of manager-employee conversations over time. The [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) documents the connection between meaningful feedback and frontline retention in detail. Performance management has always been worth doing well. For frontline teams, it's historically just been harder than it should be to do at all. The infrastructure to do it well now exists — the question is whether organizations will use it. --- ## How Does Performance Management Fit Into a Broader Frontline Platform? Performance reviews don't exist in isolation. The same employees whose reviews are now mobile-accessible also need shift scheduling, training content, HR self-service, and internal communications — and the friction in each of those areas compounds when they live in disconnected point tools. MangoApps connects performance management to the broader [workforce management](/solutions/workforce-management) infrastructure: HRIS integrations that keep employee rosters current, a training layer that surfaces employee engagement courses and development content alongside review goals, and communications tools that let managers follow up on feedback without switching platforms. The Libraries app and Go1 integration released this week are part of the same logic — reducing the distance between employees and the resources they need, whether those resources are SOPs, training modules, or performance feedback. For organizations evaluating employee experience platform options, the distinction between a point solution and a unified platform matters most at scale. A single platform that connects performance, training, and communications means that closing the access gap in one area — say, mobile parity for reviews — automatically extends to the others. That's the architecture behind [MangoApps' recognition in leading intranet platform evaluations](/articles/mangoapps-2026-forrester-wave-intranet-platforms) and what separates an employee engagement software investment from a series of disconnected tools. --- # The Precision Problem in Frontline Workforce Operations **Author:** MangoApps Team **Published:** 2026-03-01 **Category:** news-and-updates There is a moment that operations leaders recognize instantly. The company has grown past a certain threshold — multiple sites, multiple teams, a few hundred or a few thousand frontline workers —... # The Precision Problem in Frontline Workforce Operations Per IDC, employees spend 2.5 hours per day searching for information — but for operations managers running multi-site frontline teams, the more costly problem isn't finding information. It's managing the exceptions that software wasn't designed to handle. The math compounds quickly. A shift supervisor in one department doesn't need visibility into coverage gaps three departments over. A referral bonus for a hard-to-fill position shouldn't surface on entry-level roles that fill themselves. A new hire who onboarded through SSO shouldn't step through an account setup wizard for credentials that were already provisioned. Each of these is small. Each requires a human to manage it. Across a workforce of several hundred, the aggregate is a permanent overhead tax that scales with the company rather than shrinking as the organization matures. The precision problem in frontline workforce operations isn't a missing-feature problem. Most enterprise platforms have too many features. The problem is that software defaults to uniform logic — everyone sees everything, every rule applies everywhere, every new hire gets the same flow — and asks administrators to carve out exceptions by hand. At a certain scale, managing those exceptions becomes its own job, and it gets done inconsistently. The alternative is a platform built to distinguish context by default. This isn't a theoretical claim — it's the architectural difference between workforce software that reduces overhead and software that generates it. Recent MangoApps workforce operations updates address this gap across four areas: scheduling visibility, compliance automation, referral targeting, and onboarding flow. ## Why uniform logic fails at scale Eighty percent of the global workforce is deskless, per Emergence Capital — working in retail locations, healthcare facilities, warehouses, and field sites where management is layered, not flat. A single shift supervisor may be responsible for 15 workers across two locations. A site manager above them may oversee five supervisors and a combined headcount of 75. Enterprise scheduling software built for this environment typically starts with a permissive model: all managers see all shifts. For 50 employees, that's workable. At 500, it becomes noise. At 5,000, it makes delegating scheduling authority to frontline supervisors impractical — the scope of what supervisors can see, and accidentally change, is too broad for safe delegation. The operational consequence is predictable: scheduling decisions that could be handled by frontline supervisors escalate upward. Site managers who should be managing operations spend time on coverage questions that belong one level down. The software that was supposed to reduce administrative overhead produces it instead. This is the structural cost of uniform logic — it concentrates decision-making at the wrong level by failing to provide the context scoping that would make delegation safe. ## Precision in scheduling: scoped visibility and delegated authority Scheduling groups address this directly. Admins organize shifts around named scheduling teams, each with its own coverage dashboard, its own filter on the schedule view, and its own scope for manager permissions. A supervisor granted access to a scheduling group sees what matters to their team and nothing else. The permission model doing the work here is invisible to the supervisor — which is the point. When a frontline supervisor's schedule view is scoped to their team, delegation becomes structurally safe. They can take ownership of coverage without access controls limiting what they might accidentally affect elsewhere. For organizations that have been hesitant to push scheduling authority down to the supervisor level, this changes the calculus: delegation stops being risky and starts being straightforward. For [teams managing shifts across multiple locations or departments](/solutions/shifts-schedules), this matters beyond org chart tidiness. When scheduling is managed at the right level — by the people closest to the work — coverage decisions are faster, escalations are fewer, and site managers recover the time they were spending on questions that should never have reached them. ## Compliance that runs on rules, not reminders Meal break compliance sits at an uncomfortable intersection: it's legally significant, operationally complex for hourly workforces, and poorly served by most tooling. The options have historically been a specialized legal product disconnected from operations, or a manual process that depends on someone remembering the right steps at the right time. The exposure is real. A missed meal break can trigger premium pay obligations under California wage-and-hour law. California-style frameworks are being adopted in additional states, expanding the legal surface area for employers who rely on manual tracking. The waiver process for voluntary on-duty meal periods requires signed documentation that can be produced during an audit — not a paper trail that ends up in a filing cabinet no one can locate. MangoApps brings meal break compliance into the same system where schedules are managed and time is tracked. Employers can track meal break behavior against configurable rules, issue digitally signed waivers, and automate the compliance scheduling and notifications that keep the process running without manual coordination. The waiver flow closes a gap that has historically required a separate document management process running in parallel with operations. The structural significance: compliance runs alongside workforce operations rather than as a separate track requiring coordination between HR, legal, and operations to stay current. [Organizations managing unionized workforces](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) gain an additional benefit — a clear, auditable submission record for every transaction rather than approvals scattered across email and chat. ## Signal value: why referral targeting matters at scale Referral programs operate on a signal assumption: employees who refer candidates are more likely to refer well-matched ones, producing hires who perform better and stay longer. That assumption holds when the incentive is attached to genuinely hard-to-fill roles. It erodes when the bonus surfaces on every open position. The mechanism of erosion is attention. When employees see referral incentives on roles they know fill easily through organic applicants, the program reads as noise. The sense that a referral bonus signals a role genuinely needs their network disappears. Participation drops without the program officially ending — it just stops working. Job targeting for referral programs lets admins restrict incentives to specific departments, locations, or minimum salary thresholds. A referral bonus for a hard-to-fill position doesn't surface on entry-level roles. The configuration matches business intent precisely. Restoring signal value is the point — and it requires the precision to apply the incentive only where it belongs. The same precision logic applies at the onboarding level. When an organization uses SSO, identity and authentication setup is handled before a new hire ever sees an onboarding wizard. Walking them through those steps anyway sends an implicit message that the software doesn't know how they arrived. SSO-aware onboarding skips those steps automatically, and admins control which onboarding steps are shown or hidden per business context. Per Beekeeper case study data, organizations with mobile-first digitized onboarding workflows report up to 50% faster new-hire completion — the driver being that the process is tailored to the worker's actual starting point, not a one-size flow applied uniformly. ## Three questions to answer before configuring The feature story matters less than the implementation question most organizations don't answer first. Before configuring scheduling groups, compliance rules, or referral targeting, three questions determine whether the configuration will hold under operational conditions. **What are the actual team boundaries?** Scheduling groups work when org structure is current. If your org chart hasn't been cleaned up recently, configuring groups around a stale structure recreates the same ambiguity in a new layer. Map who owns coverage and where the supervision lines are before configuring group membership. **Who handles exceptions?** Automation reduces routine overhead but doesn't eliminate edge cases. An employee who crosses department lines, a role that spans multiple locations, a waiver request that comes in outside the normal flow — these need a defined owner. Automation configured without a clear exception path moves friction downstream rather than eliminating it. **What does 90-day success look like?** Define a baseline before launch: escalation volume for scheduling coverage questions, average processing time for compliance documentation, referral program participation rate. At 90 days, the question shouldn't be whether employees are using the new features — it should be by how much escalation volume has dropped. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how operations teams are structuring precision-configuration rollouts for mixed desk and deskless workforces, including which configuration categories to prioritize first. ## The operational return on precision The business case for precision-configured [workforce management](/solutions/workforce-management) software isn't made in feature announcements. It's made in the work that stops happening: the escalations that never reach the wrong level, the compliance reviews that don't require three weeks of data collection, the referral bonuses that don't erode the program they were meant to strengthen. The organizations closing the precision gap share a common pattern: they've moved from software that requires administrators to manage exceptions manually to software where the right behavior is the default. Scheduling authority is delegated safely because the scope is correct. Compliance runs because the rules are configured, not because someone remembered to check. Referral incentives create signal because they're targeted to the roles that need them. The overhead tax that scales with company growth doesn't have to be permanent. It's a symptom of software architected around uniform logic — and it shrinks when the platform is built to distinguish context and act accordingly. For operations leaders evaluating workforce platforms, the practical question isn't whether the features exist. It's whether the architecture allows precision to be the default rather than something administrators carve out and maintain by hand. That distinction is where the overhead tax either shrinks or compounds with every new hire, every new site, and every new compliance requirement. --- # The Audit Trail Modern Operations Teams Are Missing **Author:** MangoApps Team **Published:** 2026-02-22 **Category:** news-and-updates Picture a scenario that is more common than most operations leaders want to admit. A shift goes uncovered because no one caught the gap in time. # The Audit Trail Modern Operations Teams Are Missing Every operations leader has a version of the same story. A production environment breaks because the approval process lived in a Slack thread. A shift goes uncovered because the gap wasn't caught until after the fact. A strong candidate is passed over and six months later no one can reconstruct why. The immediate problem gets resolved — engineers roll back, staff scramble, another candidate moves through. But the organizational question goes unanswered: *how did this happen, and what prevents it from happening again?* The answer almost always involves a missing record. Per McKinsey, employees spend an average of 2.5 hours daily searching for information they cannot find. Per APQC, Fortune 500 companies lose an estimated $31.5 billion annually to knowledge loss. These numbers reflect the downstream cost of an upstream structural problem: operations teams are skilled at handling the moment, but most have not built the infrastructure to convert those moments into institutional knowledge. The tools of knowledge management that close this gap are not exotic — they are process discipline applied to three operational categories most teams manage informally: incident resolution, change control, and hiring decisions. The argument for building this infrastructure is direct. Documentation overhead is real and concentrated — it happens at the moment of the incident, the change, the hire. The overhead of *not* documenting is also real, but distributed across future moments: re-diagnosing the same incident, rolling back an undocumented change, defending a hiring decision with no paper trail. Organizations that defer audit-trail infrastructure are not avoiding overhead. They are paying it later, with interest. ## Why recurring incidents reveal a documentation failure, not a technical one Most IT and operations teams know this pattern: a ticket comes in, an engineer diagnoses and resolves it, two weeks later the same ticket comes in again. The problem is not that the team is bad at resolution — it is that resolution and diagnosis are treated as the same activity. Fix the symptom, close the ticket, move on. Problem Management creates a formal distinction between the two. When a recurring incident pattern is flagged, a Problem Record opens: a dedicated workspace for documenting the investigation, recording root causes, and publishing a known error with a workaround for the broader team. Problem Records link to related incidents and change requests, so the full history of a repeating issue lives in one place rather than scattered across ticket comments and tribal memory. The operational payoff is concrete. Linking problem records to change requests creates a closed-loop audit trail that operations managers can use to justify infrastructure investment with traceable, time-stamped evidence. When you can show that the same failure mode generated twelve tickets over four months — with documented impact and a traceable root cause — the case for fixing it properly writes itself. For teams building [workforce management](/solutions/workforce-management) infrastructure across distributed or frontline workforces, this closed-loop accountability is the foundation everything else rests on. ## Change control: from Slack thread to structured review Once a team decides to address a root cause, that decision needs a structured home. Change Management provides one: a formal request with risk classification, a routing path to a Change Advisory Board for structured review and voting, and an AI-generated impact analysis that surfaces risk factors and suggests rollback steps before the change is approved. Structured change advisory board workflows with AI-generated impact analysis reduce production incidents caused by undocumented modifications — which is the operational outcome most change management programs exist to deliver. The record of what was reviewed, who approved it, and what rollback plan was documented exists whether or not the change goes smoothly. This is the closed-loop that distinguishes organizations that learn from incidents from those that only survive them. A Problem Record documents the root cause. A Change Request links to that Problem Record. The Change Advisory Board reviews the proposed fix. The outcome is recorded against the original Problem Record. Per a deployment at a 40,000-employee workforce, structured operational tooling reached 91% platform usage within eight weeks of rollout and drove a 30-point increase in reported employee engagement — a benchmark that reflects what happens when the tool matches the workflow rather than fighting it. ## The hiring decision you cannot defend Ask a hiring manager to explain why one candidate was chosen over another for a senior role, and the answer usually involves some combination of gut feel, panel consensus, and whoever made the strongest case in the debrief. Experienced interviewers have calibrated instincts — but when the decision needs to stand up to scrutiny, instinct is not enough. This becomes concrete in three scenarios: when a passed-over candidate asks for substantive feedback, when a manager is hiring consistently across multiple open roles simultaneously, and when HR is reviewing whether stated criteria are actually being applied in practice. Interview Scorecards bring the same structured-review logic to hiring that Problem Management brings to service operations. Hiring teams create configurable scorecard templates — defining evaluation criteria for a specific role and weighting each — so every interviewer on the panel fills out the same form. Responses roll up into a weighted composite score. Structured interview scorecards with role-specific criteria reduce inconsistency across multiple open requisitions and give HR a defensible record when hiring decisions are challenged. The parallel to operational knowledge management is direct: a scorecard is a structured document that converts a subjective discussion into a traceable record. Per Banner Health's internal employee research, 59% of employees reported trouble finding needed information and 63% said intranet content was not current or relevant — the same information-quality problem that plagues unstructured hiring processes, where evaluation criteria exist in someone's head rather than in a shared document. [Closing the Information Gap in Performance Reviews](/articles/closing-the-information-gap-in-performance-reviews) covers how the same principle applies to ongoing employee development. ## Autonomous action and the authorization question The accountability problem takes a different shape when the actor is not a person. Coverage Autopilot illustrates how to give a system meaningful authority without losing visibility into what it does. When a shift is flagged as at-risk — a call-out, an unexpected gap — the system acts: it identifies qualified employees based on eligibility criteria, sends coverage offers, and works through the available pool. The record of what the system attempted — who was contacted, in what order, at what times — exists whether or not a human was involved in the outcome. For teams managing complex shifts across large frontline workforces, that record is the difference between a defensible process and a liability. AI Agent Governance lets administrators configure trust levels per agent — setting which agents operate autonomously, which require approval before acting, and what action thresholds apply at each level. A new Agent Guidelines editor lets organizations define system-wide behavioral rules that are automatically injected into every agent's context, without per-agent configuration. When an AI-assisted action is reviewed weeks later — in a compliance audit, a postmortem, or a service review — the record exists. The agent was configured to operate at a specific trust level. Here is the queue of actions it took autonomously. Here are the ones that required human sign-off. The audit trail is built into how the system operates, not reconstructed after the fact. In regulated industries — healthcare, financial services, utilities — this is moving from best practice to compliance requirement. ## Sequencing the build-out The right starting point depends on where undocumented decisions are causing the most visible pain. **If your service desk is closing the same tickets repeatedly** and engineers cannot point to a documented root cause, start with Problem Management. The signal is a high volume of recurring incidents with no formal SOP operations record linking them to root causes. A single Problem Record that prevents one major outage typically pays for the process overhead many times over. **If HR has flagged inconsistency in how candidates are evaluated**, or your organization is hiring across multiple departments simultaneously, start with Interview Scorecards. Make criteria explicit, persistent, and comparable across cycles before adding headcount — template design after a failed hire is harder than template design before one. **If your team has already deployed AI agents in operational workflows** and the question of authorization has not been formally answered, start with AI Agent Governance. Configuration is not a one-time task — it is an ongoing practice that should be established before agents operate at scale, not after. Common implementation pitfalls: treating these tools as documentation requirements rather than decision infrastructure (the value is in the patterns records reveal over time, not in the records themselves); configuring templates without input from the people who fill them out (templates that don't reflect how work actually happens get abandoned); deploying agent governance after agents are already running autonomously (retroactive trust-level configuration is harder to enforce and harder to audit). ## What to measure once the audit trail is running Deploying structured documentation is the first step. Measuring whether it produces outcomes is the one teams most consistently skip. **Recurring incident rate.** If Problem Management is working, the rate of tickets that repeat within a 30-60 day window should decline. A Problem Record that is opened, linked to its incidents, and resolved with a Change Request should prevent the same ticket from coming back. Tracking this monthly surfaces whether the knowledge management tools are actually closing loops or just creating records. **Change failure rate.** The percentage of changes that require rollback or cause production incidents is the leading indicator for Change Management effectiveness. Baseline this before rolling out structured change control, then track it quarterly. **Hiring decision consistency.** Compare offer-acceptance rates and 90-day retention across cohorts evaluated with and without structured scorecards. Early-tenure attrition is one of the most sensitive signals for whether hiring criteria match actual job requirements. **Agent action log review rate.** Track what percentage of agent actions are reviewed post-hoc by managers. A rate near zero suggests either the agents are perfectly configured or no one is checking. A healthy governance practice includes spot-checking autonomous decisions as a routine operational task. For a broader view of how leading operations teams are sequencing this kind of capability build-out, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the unified platform investments that are replacing fragmented knowledge, change, and governance tools — and what outcomes leading organizations are tracking at each stage. --- The thread running through Problem Management, Change Management, Interview Scorecards, and AI Agent Governance is the same: each converts a moment of operational judgment — a diagnosis, an approval, a hiring decision, an autonomous action — into a traceable record that outlasts the moment. Knowledge and knowledge management are no longer back-office concerns. They are operational requirements for any team scaling across locations, disciplines, and AI-assisted workflows. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarking on how platforms are evaluated for governance and compliance readiness — useful context for organizations making investment decisions in this category. Managers are now responsible for more people across more locations than any single person can hold in their head. AI agents are taking on tasks that previously required explicit human judgment at every step. In that context, the infrastructure for documented decisions is not overhead — it is what allows organizations to scale without losing coherence. The teams operating at scale built this infrastructure while their processes were still small enough to instrument properly. When the same incident comes back for the fifth time, it is too late to wish you had a Problem Record from the first one. --- # Why HR Still Runs on Follow-Up Emails — And What Replaces Them **Author:** MangoApps Team **Published:** 2026-02-15 **Category:** news-and-updates The performance review meeting ended an hour ago. The manager filled out the form, marked the meeting complete, and moved on with their day. # Why HR Still Runs on Follow-Up Emails — And What Replaces Them The performance review meeting ended an hour ago. The manager filled out the form, marked the meeting complete, and moved on with their day. Now the HR coordinator is back at her desk composing a Slack message to the employee: "Hey, just a reminder to log in and acknowledge your review when you get a chance." Tomorrow she will send a follow-up. The day after, she will check the system, see the review still sitting in pending, and consider whether to loop in the manager. None of this appears in her job description. All of it is real work — invisible overhead generated not by bad intentions but by software that records what happened without doing anything to move the process forward. Call it the follow-up tax. It shows up in goals that drift unsigned into the next quarter, in interview prep that lives in someone's personal notes, in onboarding checklists that a new hire's manager hasn't opened since the hire's first week. The tools captured the data. The coordination still happened over email. Employees navigate 6–8 disconnected tools daily, and that fragmented environment is precisely what generates the handoff overhead HR coordinators spend their days cleaning up. Several releases from MangoApps this week address exactly this problem, and they do it across parts of the employee lifecycle that rarely get treated as connected: goal-setting, performance reviews, hiring, and onboarding. Together they represent a shift in how an [employee experience platform](/solutions/modern-hcm) can be designed — not just to record state, but to move it forward. --- ## When Goals Are Just Suggestions Ask an HR leader what percentage of employees have formally approved goals at any given moment, and the answer is usually awkward. Not because people don't set goals, but because goal-setting in most organizations is a ritual without a process. Someone writes their objectives in a doc, shares it with their manager, the manager says "looks good" in a meeting, and that's it. Whether the goals were ever formally aligned with what the organization actually needed is anyone's guess. The new Goal Approval Workflow replaces that informal loop with a structured one. Employees draft goals, then submit them for manager review. The manager can approve, reject with a required comment, or escalate to a second leadership tier for organizations that require it. A visual progress stepper shows every party exactly where a goal stands — no one has to ask. What changes here isn't just the mechanics. It's accountability. A rejected goal with a required comment is a coaching moment. An approved goal with a timestamp is a commitment. And when the workflow is complete, everyone involved has a traceable record of what was agreed to — not a vague memory of a conversation. For organizations looking to move beyond manual operations in the manager-employee experience, this kind of structured approval trail is the difference between a process that exists on paper and one that actually runs. The Performance Review Acknowledgement Workflow works on the same logic. Once a review meeting is marked complete, both manager and employee can acknowledge independently, at their own pace. The cycle advances automatically when both have signed off. If either party hasn't acknowledged within 24 hours, an automatic reminder goes out — without anyone from HR having to compose a Slack message. Taken together, these two features close a loop that most HR teams currently close by hand. The process doesn't stop after the meeting. It moves forward on its own. For a deeper look at how continuous feedback structures replace the annual cycle entirely, see [Break The Annual Review Cycle: The Executive's Guide To Creating A Culture Of Continuous Employee Development](/resources/break-the-annual-review-cycle). --- ## The Consistency Problem in Hiring Here is a version of a problem that almost every recruiting team knows: the first interviewer asks about system design, the second asks about communication style, and the third runs out of time and asks whatever comes to mind. The debrief is a negotiation between three different subjective impressions rather than a structured evaluation of the same criteria. Interview Guides address this at the source. Recruiting teams can now create reusable guide templates — capturing the gold-standard questions for a role or interview stage — and generate a tailored Question Set from each guide for individual candidates. Interviewers can add, remove, or reorder questions, but the baseline is consistent. The institutional knowledge of what makes a strong candidate for a given role no longer lives only in the head of the most experienced recruiter on the team. This matters more than it sounds during high-volume hiring periods. When you're running five engineering interview loops simultaneously, the question isn't just "did we hire the right person." It's "did we evaluate everyone against the same bar." Interview Guides make that possible without requiring every interviewer to coordinate over Slack before each call. There is also a compliance dimension that often goes unacknowledged: structured, role-aware interview guides with reusable templates are increasingly positioned as a legal-risk mitigation tool, not just a consistency aid, because undocumented hiring decisions create audit exposure — a point now covered explicitly in recruiting and talent operations best-practice guidance across the industry. Consistent evaluation criteria at hire also correlates with faster time-to-productivity, which connects directly to the onboarding outcomes discussed below. The underlying problem — ad-hoc processes producing inconsistent outcomes — also gets addressed in a less obvious place this week. Advanced Survey Result Filters now let HR teams slice engagement data by manager, tenure bracket, employee type, and performance tier, with heatmap support across those same dimensions. This isn't just a nice analytical feature. It's what allows an HR business partner to stop guessing and start seeing: is the engagement gap in a particular team about the function, the tenure distribution, or a specific manager? Segmentation turns survey data from an aggregate number into something you can actually act on. --- ## Process Doesn't Stop at the Desk The follow-up tax hits hardest at the edges of the organization — not the desk workers who live in software all day, but the field technician who needs to complete an inspection on-site, the warehouse worker who punches in on a shared tablet, and the new hire's manager who is supposed to be tracking onboarding progress across a 90-day window. This is not a small population: 80% of the global workforce is deskless, per Emergence Capital, which means the majority of employees are unreachable by the coordinator-and-email model that most HR SOP operations still rely on. Mobile App Support this week extends a broad range of MangoApps Workforce apps — Forms, Inspections, Safety Hub, E-Signature, Surveys, Recognitions, Timekeeping, and more — to mobile with optimized layouts and OTP login for workers without standard credentials. A field technician can complete and submit an inspection form from their phone without returning to a desk or logging into a separate system. The process meets the worker where the work actually happens. Goal approval and review acknowledgment workflows reach these frontline workers through the same mobile interface — meaning the structured processes described above are not desk-worker-only features. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how organizations are extending these workflows to frontline populations at scale. For shared workstations, the new Time Clock Kiosk gives frontline teams a PIN-based clock-in solution scoped to a specific location. Each employee uses their own encrypted PIN — no shared passwords, no paper logs, no one trying to remember if they punched out at the end of a shift. And for managers trying to stay ahead of onboarding rather than react to it, the Onboarding Plan Timeline View organizes a new hire's tasks, documents, and checkpoints across phases from pre-boarding through 90 days. A manager can open the timeline before the new hire's first week and immediately see which Day 1 tasks are still incomplete — early enough to do something about it. Digitized onboarding workflows — including mobile-accessible training and automated task routing — can cut new-hire ramp time significantly compared to manual coordinator-driven processes, and organizations that unify onboarding and communication on a single platform have seen frontline adoption reach 90% within the first six months. The pattern here is the same one running through the goals and review workflows: the system surfaces the gap before it becomes a problem, rather than after. --- ## The Bigger Picture There is a version of workforce software that does one thing very well: it captures records. What happened, when, and by whom. That version of software is useful for audits and reports. It is less useful for actually getting work done. What the releases this week have in common is a different design philosophy: software that not only records state but moves state forward. Goals advance through approval. Reviews progress to acknowledgement. Onboarding surfaces gaps before the new hire arrives. Interviews stay consistent because the questions are already there. No-code workflow automation covers HR, IT, and cross-functional self-service processes — approvals, forms, routing — without requiring engineering resources, which reduces the coordination burden on HR coordinators who are currently absorbing that overhead manually. One more feature this week makes this philosophy explicit. The new AI Agent Governance dashboard gives administrators control over how autonomous AI agents operate — setting trust levels, defining action thresholds, and routing proposed agent actions to a pending approvals queue for human sign-off. Even the most automated part of the platform now has a structured process for human review. Nothing happens outside of a governed workflow. That is the through-line. Every process has a next step, and that next step either happens automatically or waits for the right person to sign off. The follow-up email is not the mechanism. The platform is. --- ## Getting Started: How to Reduce Your Follow-Up Tax Understanding what replaces follow-up emails is one thing. Knowing where to start is another. The implementation sequence that works for most HR teams follows four steps, and none of them require engineering resources or a lengthy IT project. **1. Audit your current manual operations.** Before configuring anything, map the workflows where HR coordinators are currently acting as human routers — the places where a task sits in a system but only moves when someone sends a message. Goal sign-offs, review acknowledgments, onboarding task completion, and interview debrief collection are the most common culprits. IDC research finds employees spend 2.5 hours per day searching for information, per IDC — much of that time is spent chasing status that a governed workflow would surface automatically. **2. Select the relevant features for your highest-friction processes.** Not every team needs every module at once. Organizations with a broken performance cycle should start with Goal Approval Workflow and Performance Review Acknowledgement. Teams running high-volume hiring should prioritize Interview Guides. Frontline-heavy operations should lead with Mobile App Support and the Time Clock Kiosk. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) provides a useful framework for prioritizing by workforce segment. **3. Configure templates before you launch.** The leverage in Interview Guides, onboarding timelines, and survey filters comes from the templates built before the first use. Recruiting teams should document the gold-standard questions for each role. HR teams should map the 30-60-90 day onboarding checkpoints for each function. Managers should review the approval escalation paths for goals. This is the operations manual work that pays dividends every time the workflow runs. **4. Train managers, not just administrators.** The follow-up tax is largely a manager behavior problem — not because managers are negligent, but because the old tools gave them no structured next step. The Goal Approval Workflow and Onboarding Plan Timeline View only reduce coordinator overhead if managers understand what the system expects of them. A 30-minute walkthrough at the manager level, focused on what the system will prompt them to do and when, is typically sufficient. For organizations managing distributed or frontline teams, the [employee experience](/solutions/employee-app) rollout should include in-app guidance rather than relying on email instructions — which would recreate the problem you're solving. --- ## Why Does HR Still Rely on Email in the First Place? The honest answer is that most workforce software was designed to store data, not to orchestrate processes. A system that records a completed review but sends no automatic acknowledgment prompt is not broken — it is doing exactly what it was built to do. The follow-up email exists because the software stopped short of the next step. There is also an adoption gap that compounds the problem. Per Social Edge Consulting, 91% of organizations operate an intranet, but nearly a third of employees never log in to it, and those who do average just six minutes per day of usage, per SWOOP Analytics. When the platform isn't where workers actually spend their time, coordinators fill the gap with messages in the channels workers do check. The solution isn't more reminders — it's meeting workers in the tools and devices they already use, which is what the mobile-first and kiosk features this week are designed to do. Teamwork management breaks down when the coordination layer is informal. Structured workflows don't eliminate human judgment — they eliminate the overhead of chasing it. --- ## How Does This Compare to Managing Processes Across Disconnected Tools? The alternative to a unified employee experience platform is a stack of point solutions: one tool for performance reviews, another for goal-setting, a third for onboarding, a fourth for surveys. Each captures its own data. None of them talk to each other. The coordinator becomes the integration layer. This is not a hypothetical — it is the current state for most mid-market HR teams. The [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study) case study illustrates what consolidation looks like in practice for a large, distributed workforce. The coordination overhead doesn't disappear because you have good tools. It disappears when the tools share a process layer — so that a goal approval in one module can trigger an onboarding task in another, and a survey result can be filtered against the same performance tier that just completed a review cycle. For organizations evaluating where MangoApps fits in the broader intranet and workforce management landscape, [MangoApps Included in Leading Research Firm's Intranet Platforms Ev...](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides independent analyst context on how the platform is positioned relative to alternatives. --- # 12 Reasons Frontline Intranet Adoption Fails (And How to Fix Each One) **Author:** The MangoApps Team **Published:** 2026-02-10 **Category:** intranet Why do frontline intranet rollouts stall? 91% of orgs have an intranet, but only 13% of employees use it daily. Here are the 12 most common adoption failures and the UX, accessibility, and change management fixes that work. Most intranets launch with excitement and die with indifference. The stats tell the story: [91% of organizations have an intranet](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics), but only 13% of employees use it daily. Nearly a third never open it at all (Social Edge Consulting, 2025). For frontline workers, those numbers are worse. These employees make up [80% of the global workforce](https://hrexecutive.com/frontline-first-hr-engaging-the-80-that-powers-your-business/), yet most intranet platforms were designed for someone sitting at a desk with a laptop and a corporate email address. When organizations try to extend that same experience to nurses, warehouse teams, retail associates, and factory workers, adoption crumbles. Here are the 12 most common reasons frontline intranet adoption fails, and what actually works to fix each one. ## 1. You Built It for Desk Workers and Called It "Company-Wide" Most intranet platforms were designed around a desktop browser, a company email login, and the assumption that employees sit at a computer for eight hours a day. That describes maybe 20% of your workforce. Frontline employees work on their feet. They check their phones between patients, during breaks, or at shift change. They often don't have company email addresses. When the intranet requires a desktop, a VPN, or an Active Directory login tied to an email they don't have, you've excluded the majority of your people before they even see the home page. **The fix:** Choose a platform built for [mobile-first access](https://www.mangoapps.com/solutions/employee-app) from the start. That means a branded native app (not a responsive website crammed onto a small screen), single sign-on that works with a phone number or employee ID, and an experience designed around how frontline workers actually move through their day. If your people can't get in within 10 seconds of opening the app, you've already lost them. ## 2. The Content Is Irrelevant to the People You're Trying to Reach Corporate intranets love to lead with CEO messages, quarterly earnings recaps, and photos from the holiday party at headquarters. None of that matters to a warehouse associate in Memphis trying to find the updated returns process. When frontline workers open the intranet and see content that has nothing to do with their role, location, or daily work, they learn one lesson fast: this isn't for me. And they don't come back. **The fix:** Personalize content by role, location, and department. A nurse in the cardiac unit should see different content than a billing coordinator. A retail associate in Dallas should see their store's schedule and local updates, not a press release about a new office in London. Modern platforms can handle this with [audience targeting and role-based dashboards](https://www.mangoapps.com/solutions/employee-communications). Use them. The goal is that every employee opens the app and immediately sees something useful to *their* day. ## 3. The Intranet Doesn't Actually Do Anything Here's the pattern: an organization launches an intranet as a communication channel. It publishes news, posts announcements, maybe hosts a document library. Employees read it for a week, realize it's a digital bulletin board, and go back to texting their manager for answers. The intranets that sustain high adoption are the ones where employees can actually complete work. View and swap shifts. Submit time-off requests. Access pay stubs. Complete training modules. File an incident report. When the intranet is where work gets done, people use it because they have to, not because someone in comms asked them to. **The fix:** Turn your intranet into a work hub. Integrate operational tools like [shift scheduling](https://www.mangoapps.com/solutions/workforce-management), [task management](https://www.mangoapps.com/task-management), and HR self-service directly into the platform. If employees can do their most common tasks without leaving the app, daily usage becomes a byproduct of daily work. That's the difference between a 35% adoption rate and a 90% one. ## 4. Search Doesn't Work (So Nobody Finds Anything) Enterprise search has been broken for decades, and frontline workers have even less patience for it than knowledge workers do. When a hotel housekeeper searches "room cleaning checklist" and gets 47 results from 2019 sorted by date modified, she's not going to try a second query. She's going to ask her supervisor or check the binder in the break room. Bad search is one of the fastest adoption killers because it trains users that the intranet doesn't have what they need, even when it does. According to [McKinsey](https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy), employees spend 20% of their workday searching for information, and AI-powered search can cut that time by 25-30%. **The fix:** Invest in [AI-powered search](https://www.mangoapps.com/ai) that understands natural language queries and surfaces the most relevant, current result. Permission-aware search that spans documents, policies, wikis, and HR resources in a single query. The benchmark to aim for: 75% or higher search success rate (Social Edge Consulting, 2025). If you're below that, your content might be fine. Your search just isn't surfacing it. ## 5. Nobody Told Managers It Was Their Job Frontline adoption lives and dies with shift supervisors and frontline managers. These are the people who set expectations for their teams. If your store manager doesn't use the intranet, neither will the 30 associates reporting to them. If the charge nurse still prints the schedule and tapes it to the wall, no one on her unit is checking the app for updates. Most organizations invest in a top-down launch (CEO video, all-hands email, branded swag) and skip the middle layer entirely. But frontline employees don't take cues from the C-suite. They take cues from their direct manager. **The fix:** Make manager enablement the centerpiece of your rollout, not an afterthought. Train managers on how to use the platform in their daily workflow. Give them tools to post updates, recognize their team, and track task completion within the app. Measure manager adoption separately and hold leaders accountable. When managers actively post, respond to feedback, and reference the intranet in team huddles, adoption follows. Research from [Gallup](https://www.gallup.com/workplace/285674/improve-employee-engagement-workplace.aspx) confirms that organizations with strong internal communications are 4.5x more likely to have engaged employees. ## 6. You Launched Without a Change Management Plan Technology doesn't create adoption. People do. And people resist change, especially when they've been burned by past technology rollouts that promised big and delivered little. Too many intranet projects treat the platform launch as the finish line. In reality, it's the starting line. Without a structured change management plan that addresses awareness, training, reinforcement, and feedback, even the best platform will follow the same curve: spike at launch, steady decline over 90 days, flatline by month six. **The fix:** Build a 90-day adoption plan that extends well past go-live. Phase one is awareness: why this matters and what's in it for each audience. Phase two is hands-on training, segmented by role (frontline workers need different onboarding than HR managers). Phase three is reinforcement: regular content updates, manager-led usage, gamification, and quick-win use cases that demonstrate value in the first two weeks. Assign dedicated adoption owners, and don't pull them off the project after launch. For a deeper planning framework, see [The AI-Powered Intranet Blueprint](https://www.mangoapps.com/resources/blueprint-for-an-ai-powered-intranet). ## 7. Employees Don't Trust It Trust is the silent adoption killer. Frontline workers often worry that a company app on their personal phone means they're being tracked. They wonder if posting honest feedback will get flagged by their supervisor. They've seen "anonymous" surveys that didn't feel anonymous. In workplaces with lower digital literacy or a history of top-down communication, suspicion runs deep. And it doesn't take much to confirm it: one unclear push notification, one vague data-collection disclosure, and the app gets deleted. **The fix:** Be direct and specific about what data the app collects and what it doesn't. Explain how feedback and survey responses are handled, who sees what, and what "anonymous" actually means. Address concerns about location tracking, screen monitoring, and personal device privacy proactively, during onboarding, not after someone complains. Transparency builds trust, and trust is what separates an app people tolerate from one they actually use. [SHRM's 2024 research](https://www.shrm.org/about/press-room/employees-with-a-positive-employee-experience-are-68--less-likel) found that positive employee experience lowers intent to leave by 68%, and trust is a foundational driver of that experience. ## 8. The Experience Doesn't Account for Low Connectivity or Shared Devices A hospital basement. A rural manufacturing facility. A delivery truck between cell towers. Frontline work happens in places where Wi-Fi is spotty or nonexistent, and many organizations don't think about that until adoption numbers come in low from specific locations. Then there's the shared device problem. Many frontline environments use shared kiosks or tablets. If logging in requires a 14-character password with special characters, and the session times out after 2 minutes, nobody is going to fight that battle between customers. **The fix:** Prioritize platforms that offer offline access or at least graceful degradation when connectivity drops. Critical content like safety procedures, schedules, and task lists should be accessible without a live connection. For shared devices, implement fast-switch user profiles with simplified authentication (PIN, badge tap, or QR code). The login experience is your first impression every single time. Make it effortless. ## 9. Content Goes Stale and Nobody Owns It The fastest way to train employees to ignore the intranet is to let them find outdated information on it. An old PTO policy. A safety procedure from two revisions ago. A "new hire" welcome message from 18 months back. Once employees encounter stale content, trust in the platform erodes. They assume everything on it is outdated, even the content that isn't. This happens because most organizations launch an intranet without assigning ongoing content ownership. The comms team writes the launch content, checks the box, and moves on. **The fix:** Assign content owners to every major section and set review cadences (quarterly at minimum for policy content, monthly for operational content). Use automated content expiration and review reminders. Build editorial governance into the platform itself, so outdated pages get flagged before employees find them. A healthy intranet is a living system, not a set-it-and-forget-it project. For more on structuring this, see our guide to [building a connected, productive workforce with a company intranet](https://www.mangoapps.com/articles/definitive-guide-to-company-intranets). ## 10. The Intranet Is One More Tool in an Already Crowded Stack Frontline workers are already toggling between scheduling apps, communication tools, learning platforms, HR portals, and whatever group chat their team actually uses to coordinate. Asking them to adopt *another* app, this time for "company news and culture," is a tough sell. The problem compounds when the intranet duplicates functionality that already exists elsewhere. If employees check their schedule in one app and get their pay stub in another, the intranet becomes the thing they skip. **The fix:** Consolidate. The intranets that drive the highest adoption are the ones that *replace* multiple tools instead of adding to the pile. When your intranet handles communication, scheduling, task management, HR self-service, training, and knowledge management in [one platform](https://www.mangoapps.com/platform), you're not asking employees to add something to their day. You're simplifying it. That's a fundamentally different value proposition, and frontline workers respond to it immediately. [McKinsey research](https://www.mckinsey.com/industries/technology-media-and-telecommunications/our-insights/the-social-economy) shows social intranets can increase productivity by 20-25% precisely because they reduce tool-switching and search time. ## 11. You're Not Measuring the Right Things (or Anything at All) "We launched the intranet" is not a success metric. Neither is "we have 10,000 registered users" when only 400 logged in last month. Many organizations fail to define what good adoption looks like before they launch. They track vanity metrics (page views, registered accounts) instead of meaningful ones (daily active users, task completion rates, content engagement by role, search success rate). Without real data, you can't diagnose why adoption stalled, which locations need help, or whether your content strategy is working. **The fix:** Define adoption benchmarks before launch. [Industry standards](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) (Social Edge Consulting, 2025) suggest that 60-70% of employees using the intranet regularly is "healthy," and 80-85% weekly active users is best-in-class. Track daily active users, session duration, content engagement by audience segment, search queries, and task completion. Review the data monthly. Segment it by role and location. Use it to drive decisions, not just dashboards. ## 12. You Chose a Platform That Wasn't Built for Frontline This one sits underneath all the others. Many of the problems above (poor mobile experience, missing operational tools, clunky authentication, no offline mode) trace back to a single root cause: the platform was built for knowledge workers and retrofitted for frontline. Retrofitting never works as well as purpose-built design. A desktop-first intranet with a mobile app bolted on will always feel like a compromise to the person using it on a 5-inch screen between patients. An intranet that requires email-based authentication will always be a friction point for workers who don't have company email. The platform choice shapes every adoption outcome that follows. **The fix:** Evaluate platforms based on how they serve your least-connected employee, not your most-connected one. Ask vendors: What does the mobile experience look like for a frontline worker with no company email, a personal phone, and 10 minutes between shifts? Can they access schedules, complete tasks, read updates, and search for answers in that window? If the demo starts on a desktop browser, you probably have your answer. For a structured evaluation framework, download [The Ultimate Intranet Buyer's Guide for a Frontline Workforce](https://www.mangoapps.com/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026). ## The Takeaway Frontline intranet adoption doesn't fail because employees don't want to be connected. It fails because organizations deploy platforms and strategies designed for a different kind of worker. The fix is consistent across all 12 of these problems: design for frontline realities first. Mobile-first access. Relevant, personalized content. Operational tools that replace existing apps instead of adding to them. Manager-led rollouts. Honest communication about privacy and data. Ongoing measurement and governance. Organizations that get this right consistently see [adoption rates above 85% within 90 days](https://www.mangoapps.com/customers). The ones that don't see the same slow decline every time: a strong launch, a quiet fade, and another intranet that "didn't work." The intranet didn't fail. The approach did. If the pattern above looks less like a rollout that can be fixed and more like a platform that no longer fits the workforce, see [8 Signs Your Frontline Organization Has Outgrown Its Employee Intranet](https://www.mangoapps.com/articles/intranet-problems-hurting-frontline-teams). --- # The Setup Tax on Workforce Operations (and How to Eliminate It) **Author:** MangoApps Team **Published:** 2026-02-08 **Category:** news-and-updates There's a kind of work that never shows up on any productivity dashboard. It happens before the real work starts — before a manager can run a team, a communicator can reach employees, or a worker... # The Setup Tax on Workforce Operations (and How to Eliminate It) There's a kind of work that never shows up on any productivity dashboard. It happens before the real work starts — before a manager can run a team, a communicator can reach employees, or a worker can clock in. It's the setup work: importing employee records from a spreadsheet, recreating next week's schedule from scratch because there's no good way to copy last week's, drafting the same all-hands message again because no one saved a template that actually sounds right. Most organizations have learned to live with it. It gets folded into "admin time," assigned to the most organized person on the team, and treated as a fixed cost of doing business. It doesn't have to be. --- ## Getting People Ready to Work Think about what it takes for a new employee to be operationally ready on day one. Someone has to create their account in the workforce system — usually by exporting a CSV from the HR platform, reformatting it, and importing it somewhere else. Then the employee needs to actually access their schedule, which means setting up and remembering a password, on a shared device, possibly without any dedicated desk or personal device at all. The [MangoApps User Sync integration](https://www.mangoapps.com/solutions/employee-data) eliminates the manual record transfer. Administrators configure the sync once, and employee records — new hires, role changes, departures — flow automatically into the workforce platform on a scheduled basis. New employees appear ready for scheduling without any data entry steps. Access is a separate problem. For frontline workers especially — people who don't manage email daily, who share devices, who rotate in and out of kiosks — traditional passwords create real friction. [OTP Login](https://www.mangoapps.com/security-compliance) sidesteps the password entirely: a six-digit code delivered by email or SMS is enough to authenticate. For workers in high-traffic shared environments, the [Time Clock Kiosk](https://www.mangoapps.com/solutions/time-attendance) takes it a step further — no individual login required at all, just a personal encrypted PIN at a shared terminal, scoped to a specific location to keep attendance data clean. None of these are flashy features. But they collectively address a genuine failure mode: the gap between "employee was hired" and "employee can actually access their shift." That gap has long been treated as a coordination problem. Increasingly, it's a systems problem — and one that can be automated away. --- ## Scheduling Without Starting Over Scheduling is one of the most repetitive tasks in workforce management. Most operations aren't wildly different week to week — the same shifts, the same roles, similar staffing levels. But many scheduling tools still require managers to build each week from scratch. The result is hours of duplicated effort, every week, indefinitely. The [Bulk Schedule Wizard and Shift Copy tools](https://www.mangoapps.com/solutions/shifts-schedules) address this directly. The wizard lets managers create multiple weeks of schedules in a single session — not by generating them automatically, but by eliminating the need to repeat the same steps six times over. Once shifts exist, the copy tool replicates them forward with automatic date adjustment, preserving roles, times, and assignments without manual re-entry. For operations teams running repeating or rotating schedules — retail floors, warehouses, healthcare settings, manufacturing lines — this compounds. A manager who previously spent two hours per week rebuilding a schedule can now spend twenty minutes reviewing one. Multiply that across a year, and the recovered time becomes material. What's notable about this approach is what it doesn't try to do. It doesn't attempt to auto-generate schedules or optimize staffing algorithmically. It just removes the overhead of repetitive manual entry — which is often the actual problem managers are dealing with, far more than the cognitive complexity of deciding who works when. --- ## Communicating Without Starting from Scratch Internal communications has a planning problem and a writing problem. Most HR and communications teams manage both from spreadsheets, email drafts, and institutional memory. A new compliance reminder gets written from scratch, even though something nearly identical went out six months ago. The annual benefits enrollment campaign gets rebuilt every year because no one quite captured last year's plan somewhere persistent. The [Communications Planner](https://www.mangoapps.com/solutions/employee-communications) brings the planning side into the platform: a full-year visual calendar, a library of preset templates organized by category — seasonal campaigns, compliance reminders, leadership messages, and more — AI-powered idea generation to fill calendar gaps, bulk CSV import for teams working from existing spreadsheets, and ICS export to share the finalized plan with any calendar application. The goal isn't to automate communications; it's to give teams a place to maintain a plan that persists from year to year, rather than starting over each January. [AI Writing Profiles](https://www.mangoapps.com/key-features/campaigns-and-journeys) address the writing side. Teams upload sample content to establish a style profile — tone, vocabulary patterns, structural preferences — and that profile then powers the AI Writer when drafting new communications. The result is an on-brand first draft rather than a blank page. The point isn't to remove human judgment from employee communications; it's to stop treating every draft as a zero-baseline problem when there's already a clear voice established. Together, they reduce two of the most persistent frustrations for communications teams: "we don't have time to plan ahead" and "we spend too long getting the tone right before we can even start writing." --- ## The Larger Pattern There's a thread connecting all of this: most workforce software was built assuming that administrative overhead was unavoidable. Employee data goes in manually. Schedules get rebuilt weekly. Communications start from scratch. Workers log in with passwords. These assumptions become invisible over time — they get normalized as "just how things work." What's changing is the expectation that these processes can be automated, templated, or at minimum de-duplicated. Organizations running large frontline workforces don't have the luxury of administrative slack. When a warehouse has three hundred workers cycling through shifts, setup friction doesn't just consume time — it creates errors, delays, and gaps that show up as real operational problems. The [Real-Time Voice Mode for AI Assistant](https://www.mangoapps.com/ai/ask-ai) that also shipped this week captures the same underlying idea. A supervisor who can speak a question about shift coverage policy and receive a clear spoken answer — without logging in, without navigating menus — is experiencing a version of the same shift: the tools meeting people where they are, rather than requiring people to adapt to the tools. The setup tax is real, and most organizations have accepted it as part of the cost of running a workforce. The more interesting question is whether that acceptance still holds when the alternative is a system built around eliminating it. --- # The Last Mile of Workforce Software: Built for Frontline Workers **Author:** MangoApps Team **Published:** 2026-02-01 **Category:** news-and-updates Think about a warehouse associate starting a shift at 5 AM. No desk. # The Last Mile of Workforce Software: Built for Frontline Workers Think about a warehouse associate starting a shift at 5 AM. No desk. No personal laptop. A shared kiosk at the entrance, a smartphone in their pocket. They need to check their schedule, confirm they read the new safety policy, sign the updated equipment agreement, and ask a quick question about overtime — all before the first truck arrives. Every one of those tasks was designed, historically, for someone sitting at a computer. A password prompt. A form that requires a mouse to fill out. A PDF sent to an email address the employee rarely checks. A chatbot that only works if you can type. The frontline worker has been an afterthought in enterprise software for a long time. Not deliberately. It is just that the people who build and buy software tend to sit at desks, and the workflows they design reflect that reality. Several things shipped this week that are, quietly, about fixing that — not one big feature, but a handful of smaller ones that each remove a specific barrier the desk-centric model has always imposed. --- ## The Password Problem Nobody Talks About The password was never designed for the frontline. It assumes a personal device, a reliable memory, and a quiet moment to recover access when you forget it — which, given average password reset rates in high-turnover industries, is not a rare event. It is a weekly one. For organizations with shift workers and shared devices, password management creates real operational drag. IT teams spend time on resets. Workers get locked out mid-shift. Managers end up sharing credentials informally in ways that create audit exposure. The whole system depends on employees having something — a password they remember — that many of them reliably do not. [OTP Login](https://www.mangoapps.com/security-compliance) takes a different approach: a 6-digit code delivered by email or SMS, no password required, no recovery flow. For environments where employees use shared kiosk stations, this is not a minor improvement. It is the difference between a system the workforce can actually use and one they route around. The feature also includes optional voice input for entering the code — an easy detail to overlook, but meaningful for the employee on a loading dock in winter, or the one who has difficulty reading small text in low light. Designing for the edges of the use case is how you know a feature was built for the actual user, not just the user persona. One thing worth noting for administrators: OTP login can be enabled selectively from Security Settings, so organizations that want to roll it out for frontline employees while keeping password-based login for desk workers can do exactly that. --- ## When Typing Is Not an Option Authentication is one barrier. Interaction is another. For workers who spend their day on production floors, in warehouses, or in the field, "just type it in" is not always the most practical instruction. Voice interaction is not a novelty for these workers — it is often the most natural interface available, particularly when their hands are occupied or they are moving between tasks. [Real-Time Voice Mode for the AI Assistant](https://www.mangoapps.com/ai/ask-ai) ships this week with a substantive implementation: WebRTC for low-latency audio capture, high-accuracy speech recognition, natural-sounding text-to-speech responses, and automatic language detection across more than 50 supported languages. Crucially, voice users access the same backend pipeline as text users — HR knowledge, service desk filing, policy lookups, timecard questions — not a stripped-down subset of capabilities. The 50-language detail is worth pausing on. For many frontline-heavy industries — food processing, construction, agriculture, healthcare support, logistics — the workforce is multilingual in ways that a single-language interface structurally cannot serve. Workers who cannot easily read or write in the company's primary language are often the employees with the most pressing questions and the least access to answers. A voice assistant that responds in the language you speak is not a translation feature. It is access. The [Service Desk Inline Reply Translation](https://www.mangoapps.com/directory/app/service-desk) closes the other side of the same gap. When a Spanish-speaking employee submits a service desk ticket, the support agent can now draft their reply in English and translate it before sending — without leaving the ticket modal, without copying text into a third-party tool. Two sides of the same language barrier, addressed in the same week. --- ## Paperwork That Reaches Everyone The third part of this week's pattern is around documents — specifically, the compliance documents and acknowledgment forms that organizations need signed, and the persistent challenge of collecting signatures from workers who do not have company email addresses, do not always carry personal devices, and spend their shifts doing things other than reading PDFs. The traditional options have always been imperfect. Paper is easy to distribute but hard to track. Email-based digital signing requires employees to have and check a work email account, which many frontline workers either do not have through the company or rarely access. The compliance record ends up inconsistent, and when an auditor asks for proof, the answer involves a filing cabinet and a hope. [E-Signature Kiosk Mode](https://www.mangoapps.com/directory/app/onboarding) changes the math. Any tablet at a site entrance, break room, or onboarding station becomes a walk-up signing station. Employees identify themselves, work through their documents with an interactive PDF viewer, signature pad, and step-by-step progress tracker, and walk away. No personal login. No email required. [Bulk Send with SMS delivery](https://www.mangoapps.com/directory/app/onboarding) covers the workers who are not on-site — a single send reaches hundreds of employees directly on their phones, with scheduling options to catch people during shift changes rather than in the middle of a task. On the back end, [AI-Powered PDF Form Field Detection](https://www.mangoapps.com/directory/app/forms) reduces the manual work of building those digital documents in the first place. Upload an existing paper form or inspection checklist as a PDF, and the platform automatically detects and maps its fields into a digital template — ready to publish. The forms that have been circulating as paper for years can now be digitized without someone rebuilding them field by field. --- ## The Through Line There is a version of this that is easy to miss in a feature list. OTP login, voice AI, kiosk signing, bulk SMS, PDF detection — they look like separate capabilities across separate parts of the platform. But the through line is the same: the default assumptions of enterprise software do not match the reality of a significant portion of the workforce. The person who most needs software-assisted HR processes — the hourly worker, the shift worker, the person on the floor — is historically the person least able to use the software built to support them. That gap has real costs. Documents that go unsigned delay onboarding or leave compliance exposure. Employees who cannot navigate the HR system escalate to managers, who stop what they are doing and miss something else. Language barriers that go unaddressed build friction and contribute to the turnover numbers that show up in the quarterly review. The features that shipped this week are not dramatic. They will not anchor a product keynote. But for organizations where frontline workers are the operation — where a warehouse, a construction site, or a processing facility is the business — the ability to reach every employee, in their language, on whatever device they have, without requiring a password they have already forgotten, is not a small improvement. It is what an employee experience that actually includes the employees looks like. --- # Killing the Spreadsheet: Why a Manual Performance Review Process is Costing You Time and ROI **Author:** MangoApps **Published:** 2026-01-29 **Category:** performance-management What if performance reviews held no anxiety and no surprises? This post shows how continuous feedback, visible goals, and shared documentation create psychological safety, fairer evaluations, and a culture where employees know exactly where they stand—and how to grow. Performance reviews are supposed to be the moment when organizations invest in their people — aligning individual growth with company direction and creating the conditions for informed talent decisions. In practice, when those reviews depend on distributed spreadsheets, emailed forms, and manual data re-entry, the process becomes the opposite: a drag on HR capacity, a source of payroll errors, and a consistent blind spot in organizational intelligence. According to Deloitte research, HR professionals spend up to 57% of their time on administrative tasks. When the performance review cycle runs manually, that percentage climbs higher. The cost isn't abstract: it's the accumulated hours of coordinators tracking submission status, directors re-entering ratings into master sheets, and analysts reconciling conflicting file versions before calibration can begin. The more important cost is what doesn't happen while all of that coordination is underway. ## The operational weight of a manual review cycle In a manual environment, the HR team sits at the center of a coordination problem it didn't design. What looks like a straightforward document collection exercise becomes a multi-week project management task with no project management infrastructure supporting it. **Follow-up overhead that compounds.** Without automated triggers, ensuring participation falls entirely on HR staff. Tracking hundreds of individual submission statuses across departments, sending manual reminders to already-stretched managers, and chasing completion rates consumes weeks of capacity per review cycle. The repetitive communication creates a secondary problem: managers start to associate performance reviews with administrative friction rather than with the development conversations the process was designed to prompt. **Version control failures that hide in plain sight.** When forms travel by email, different iterations — drafts, manager-only notes, revised ratings, final signed versions — end up on different local drives and buried in different inboxes. There is no single source of truth. During calibration, HR teams frequently spend hours cross-referencing files to confirm they're working from the most current version of each record. The risk isn't just wasted time: calibrating from a stale or superseded document produces outcomes that can't be corrected after compensation decisions have already been communicated. **Transcription errors at the highest-stakes moment.** Re-keying data from Word documents or PDFs into a master spreadsheet is the most error-prone step in the entire cycle. A single digit transposed in a merit percentage, a misread rating scale, or a decimal in the wrong column can produce a payroll error that takes weeks to unwind. Beyond the financial impact, these errors erode trust at the moment when employees most expect accuracy. Gallup research has estimated that traditional, manual review processes cost between $2.4 million and $35 million per 10,000 employees when accounting for total resource hours across employees, managers, and HR staff. The range reflects organizational variation, but the floor alone is material — and it represents expenditure on maintaining the process, not on improving the workforce it's supposed to serve. ## The frontline equity gap that email-based reviews create Most of the conversation about manual review friction focuses on desk-based employees and their managers. The larger problem is quieter: the majority of the global workforce never had equitable access to these processes in the first place. Emergence Capital estimates that 80% of the global workforce is deskless — field technicians, retail associates, healthcare staff, manufacturing workers, logistics operators. These employees are disproportionately underserved by performance review systems that depend on email, shared drives, and desktop document formats. When a review form assumes the reviewer has a stable broadband connection and an office computer, it creates a participation gap that skews performance data before calibration even begins. The equity problem extends beyond access. If a frontline employee's review depends on a manager remembering to print, distribute, collect, and re-enter a paper or email-based form, the quality of that employee's performance documentation becomes almost entirely a function of their manager's administrative habits — not their actual contributions. Organizations that want to use performance data for succession planning or compensation equity analysis are working with a dataset that systematically under-represents their frontline population. Managing workforces where [documentation consistency and defensible process integrity](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) are contractual or compliance requirements adds another layer of exposure to any process that relies on informal document handling. ## When performance data stays siloed, decisions stay blind The downstream effects of a manual review process don't end when the forms are collected. They compound across every talent decision the organization makes afterward. **Calibration without visibility.** Without a centralized dashboard displaying rating distributions in real time, identifying which managers are systematically more lenient or strict than their peers requires manual data aggregation — usually too late in the process to correct. A high-performing employee under a demanding manager may receive a lower score than a mediocre employee under a lenient one. Detecting and addressing calibration drift in a spreadsheet environment requires dedicated analyst time that most HR teams don't have during an active review cycle. **Succession planning built on incomplete data.** If HR can't quickly surface high-potential employees across departments, regions, or skill sets, succession planning defaults to the visibility of the most vocal advocates rather than the breadth of available talent. Employees whose contributions aren't captured in an accessible, queryable format simply don't appear when leadership pipeline conversations begin. **Information search overhead that compounds daily.** IDC research found that employees spend an average of 2.5 hours each day searching for information. In a manual review environment, a meaningful share of that burden falls on HR and managers hunting for the correct version of a document, the right historical performance record, or the current submission status of a review in progress. Across a thousand-person organization, that friction accumulates into a measurable productivity cost before the review cycle even closes. ## What the transition to automated review actually looks like The shift from manual to automated review management isn't a rip-and-replace operation. For most organizations, it's a staged transition — standardizing the document and workflow layer first, then connecting that layer to the HRIS and compensation systems that need the data downstream. The [executive guide to building a culture of continuous employee development](/resources/break-the-annual-review-cycle) covers the structural shift in detail, but the operational mechanics tend to follow a consistent pattern: - **Centralized templates replace distributed forms.** A single review template lives in the platform; managers access it via browser or mobile app rather than downloading and returning a file. There's no version drift because there's only one version. - **Automated routing replaces manual coordination.** When a review period opens, the platform distributes assignments, sends reminders, tracks completion, and escalates overdue items — without HR intervention. The coordination burden that consumed weeks in a manual cycle compresses to a monitoring task. - **Real-time calibration replaces end-of-cycle aggregation.** With all ratings in a centralized system, HR and leadership can observe rating distributions as they form, identify calibration outliers before sessions begin, and run calibration meetings against live data rather than exported snapshots. - **HRIS integration eliminates transcription.** When the review platform connects directly to payroll and HR systems, merit calculations flow through automatically. The highest-error-rate step in the manual process is removed from the cycle entirely. Implementation timelines for mid-market organizations typically run six to twelve weeks for the core workflow layer. Organizations with significant integrations or complex multi-tier review structures should plan for the longer end of that range. ## Calculating the actual ROI HR organizations evaluating the case for automation often undercount the costs on the manual side because they're distributed across dozens of individuals in ways that don't appear as a single line item. A more accurate accounting treats the full cycle as the unit of analysis. **Coordinator hours per cycle.** A 500-person organization running semi-annual reviews in a manual environment typically involves four to six weeks of active coordination — initial distribution, reminder cycles, completion tracking, and data aggregation. At a conservative estimate of two coordinator FTEs for six weeks per cycle, that's roughly 480 hours annually, not counting manager time. **Manager hours per cycle.** If each of 50 managers spends six hours on document handling across two review periods, that's 600 manager-hours annually — time those managers spend on form coordination rather than on the development conversations the review is supposed to generate. **Error remediation.** Payroll errors from manual data entry require investigation and correction, often involving HR, payroll, and finance. A single miskeyed merit percentage affecting 20 employees can consume more remediation time than the original data entry did. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how organizations are reframing HR technology investment as an operational efficiency question rather than a transformation initiative — a framing that makes the ROI case more tractable for budget conversations outside of HR. ## What good calibration looks like in practice The most underappreciated benefit of moving off spreadsheets isn't time savings — it's the improvement in calibration quality that becomes possible when all ratings are visible simultaneously. In a well-configured automated system, the calibration session begins with HR presenting rating distributions across departments before any discussion starts. Managers see where their team's ratings sit relative to organizational norms before the conversation begins. Discussions shift from "what rating did I give?" to "how does our definition of 'meets expectations' compare across departments?" That's a more productive conversation, and it produces more defensible outcomes when compensation decisions are later reviewed. Calibration consistency is one of the primary drivers of whether employees experience the review process as fair. Systematic inconsistency — not any individual rating decision — is what erodes trust in the process over time. That inconsistency is much harder to detect and correct when data is spread across dozens of independent spreadsheet files. ## The decision is when and how, not whether Every additional manual review cycle delays the improvement and extends the risk window. Performance records that aren't captured in a queryable format don't become useful retrospectively once a platform is in place. Organizations that run another two cycles manually before migrating are making two more bets that no consequential payroll error surfaces, no calibration bias becomes a legal exposure, and no high-potential employee gets passed over because their record wasn't visible in the data. [Modern workforce management](/solutions/workforce-management) approaches treat performance documentation as an operational input — something that needs to be accurate, accessible, and connected to the systems that act on it — rather than as an annual HR exercise separate from day-to-day operations. That framing changes both the priority and the timeline of the migration decision. The organizations that find transitions most straightforward start with explicit process documentation: what each stage of the review cycle requires, who owns each step, and where the data needs to go when the cycle closes. That documentation exists in most organizations — it lives in the institutional memory of the HR coordinators who've been running the process manually for years. Getting it into a structured workflow map is the right starting point for any automation project, regardless of which platform the organization ultimately selects. ## Frequently asked questions ### How long does implementation typically take for a mid-market organization? Core workflow automation — templates, routing, completion tracking, and calibration dashboards — typically takes six to twelve weeks for organizations with 200–2,000 employees. Organizations with complex multi-tier review structures, existing HRIS integrations that need to be maintained, or highly customized merit calculation logic should plan for the longer end of that range and allocate dedicated project time from both HR and IT. ### Can automated review platforms integrate with existing HRIS and payroll systems? Yes, and this integration is usually the primary value driver. Core integrations handle employee roster sync, completed-review data export to the performance record, and merit decision export to payroll. Complexity varies by HRIS: purpose-built connectors exist for major platforms; organizations running legacy HR systems may need to plan for a configuration or integration development phase. ### What does the calibration process look like in an automated system? Calibration in a platform environment typically runs in two phases. The first is a pre-calibration review period where HR can observe live rating distributions and flag outliers before the session begins — without waiting for managers to export and share data manually. The second is the session itself, where managers discuss ratings against a shared, real-time dashboard rather than a spreadsheet export taken at an arbitrary point in the cycle. Both phases are faster and more accurate than their manual equivalents because the data problem is solved before the conversation starts. --- # MangoApps Unveils Refreshed Brand and Logo as It Expands to Support Daily Work Across the Frontline **Author:** MangoApps **Published:** 2026-01-27 **Category:** press-release MangoApps today announced a refreshed brand and new company logo, marking an important milestone in the company’s evolution as it expands its platform to better support how work runs day to day across frontline and operational teams. # MangoApps Refreshes Its Brand and Logo as It Expands to Support Daily Frontline Work *Updated identity reflects MangoApps' transition from the cloud- and mobile-first era to the AI-first era shaping today's workforce technology.* **ISSAQUAH, Wash. – Jan. 27, 2026** — MangoApps, the unified workforce platform provider for frontline and operational teams, today announced a refreshed brand and new company logo. The update marks a meaningful milestone in the company's evolution as it expands its platform to support how work runs day to day — shift by shift, location by location — across frontline organizations. The new logo is MangoApps' first major visual update in roughly 15 years. It is designed to work consistently across products, digital experiences, and customer environments, and it reflects the company's move from the cloud- and mobile-first era into the AI-first era that is reshaping workforce technology today. What has not changed is the company's name or its core focus: bringing people and work together in a single connected system. "Our platform today looks very different than it did even a few years ago," said Anup Kejriwal, CEO of MangoApps. "This brand update reflects what MangoApps has become: a system that helps organizations run daily work more effectively, keep teams aligned, and adapt as work changes." "MangoApps has always been about bringing people and work together," Kejriwal added. "What's changed is the scope of the day-to-day work our customers rely on us to support, and how much of it now happens in one connected system." --- ## From Intranet and Communications Platform to Unified Workforce Platform Over the past decade, MangoApps has grown from its roots as an [intranet and employee communications platform](/solutions/modern-intranet) into a unified workforce platform that brings communications, operations, and employee support together in a single AI-driven experience. That evolution is happening against a backdrop that makes consolidation urgent. According to Emergence Capital, 80% of the global workforce is deskless — yet most enterprise software is still designed for desk-based employees. At the same time, per Social Edge Consulting, 91% of organizations operate an intranet, but nearly a third of employees never log in to it, and only 13% use one daily. IDC research puts the cost of this fragmentation in concrete terms: employees spend an average of 2.5 hours per day searching for information they cannot easily find. The result is a workforce that is technically connected but practically fragmented. Employees lose over 4 hours per week switching between disconnected systems — a direct cost of tool sprawl that compounds across thousands of frontline workers. MangoApps built its platform to address this directly. Rather than adding another point solution to an already crowded stack, the platform is designed to consolidate communications, service operations, and talent operations into a single experience managers and frontline workers actually use. --- ## What the Platform Expansion Includes Over the past 12–24 months, MangoApps has built and expanded a growing set of native workforce solutions alongside its core intranet and employee communications capabilities: - **Shifts & Schedules** — [scheduling tools built for frontline managers](/articles/store-managers-playbook-smarter-retail-scheduling) who need to coordinate coverage across locations in real time - **Time & Attendance** — integrated time tracking that connects directly to shift data and operational workflows - **Talent Acquisition** — recruiting capabilities framed as part of a broader talent operations pillar, reducing the need for standalone ATS tools - **Performance Management** — continuous feedback and review tools that replace the annual review cycle and support frontline retention In parallel, MangoApps has introduced a broad portfolio of AI work apps that support everyday operational and management needs — from onboarding and task execution to approvals, tracking, and service workflows. These capabilities are designed to work together within a single experience, allowing managers to communicate, operate, and support their teams in one place rather than juggling disconnected systems throughout the workday. The platform's AI layer is embedded directly into how work gets done. It helps organizations configure workflows faster, surface relevant information instantly, and reduce friction for managers and frontline teams — without rigid processes or heavy customization. --- ## Why Consolidation Produces Measurable Outcomes The business case for a unified platform is not abstract. Replacing a frontline employee costs between $4,400 and $15,000, making retention-supporting platform investments directly quantifiable. Frontline-focused platforms that consolidate fragmented toolsets into a single mobile dashboard measurably reduce tool-switching overhead for operations teams — a dynamic MangoApps has observed across its customer base. Many existing customers have already been piloting MangoApps' newer capabilities. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent context on how unified platforms compare across the market, and MangoApps' inclusion in that evaluation reflects the platform's expanded scope beyond traditional intranet functionality. MangoApps plans to continue expanding its native solutions as it deepens support for daily operations, people management, and employee support across the frontline. --- ## What This Means for Existing Customers The refreshed brand and logo will begin rolling out across MangoApps' website, products, and materials over the coming weeks. The transition will happen gradually to ensure continuity for customers, partners, and users. No product functionality is changing as part of this update — the visual refresh is an external signal of an internal evolution that has already been underway. For teams evaluating how to reduce tool sprawl and improve frontline adoption, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines the operational patterns driving platform consolidation across industries. --- ## Frequently Asked Questions About This Announcement ### Does this brand update change MangoApps' product roadmap or pricing? No. The brand refresh is a visual and identity update that reflects platform capabilities MangoApps has already built and deployed. The company's product roadmap, pricing structure, and customer support commitments remain unchanged. Customers currently piloting newer capabilities such as Shifts & Schedules, Time & Attendance, Talent Acquisition, and Performance Management will continue on their existing timelines. ### How does MangoApps define a "unified workforce platform" differently from a traditional intranet? A traditional intranet — in its original definition — is a private internal network used primarily to share information and documents within an organization. Per Social Edge Consulting, the average employee spends only six minutes per day using intranet tools, which signals that static information repositories alone do not meet the needs of operational teams. MangoApps' platform extends well beyond that definition: it combines the communication and content functions of an intranet with service operations (task management, approvals, workflows), talent operations (recruiting, performance, onboarding), and scheduling — all accessible from a single [employee app](/solutions/employee-app) on any device. ### What types of organizations benefit most from this platform? MangoApps is built for frontline and operational organizations where work happens in shifts, across multiple locations, and often without reliable desk access. Industries including retail, healthcare, manufacturing, logistics, and field services are the primary fit. These are environments where tool fragmentation is most costly, frontline turnover is highest, and the gap between what managers need to communicate and what workers actually receive is widest. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the workforce dynamics — including retention pressure and engagement gaps — that make a consolidated platform most valuable in these settings. --- ## About MangoApps MangoApps is the unified workforce platform built for frontline and operational teams. It brings communication, daily operations, and employee support into a single platform managers use to keep teams aligned and work moving across frontline and office environments. Trusted by leading organizations around the world, MangoApps supports business-critical work every day. For more information, visit **www.mangoapps.com**. --- # The Evolution of Service Desk: How AI and Multi-Channel Support Transform Employee Experience **Author:** MangoApps Team **Published:** 2026-01-25 **Category:** enterprise-ai # The Evolution of Service Desk: How AI and Multi-Channel Support Transform Employee Experience ## Why Traditional Help Desks Are Failing Modern Workforces ... # The Evolution of Service Desk: How AI and Multi-Channel Support Transform Employee Experience ## The knowledge problem that support tickets cannot solve Per IDC research, employees spend 2.5 hours per day searching for information — time that compounds into open tickets, repeated questions, and agent queues that never fully clear. The service desk is not the root cause of this problem. But it is the place where the cost becomes visible. Most organizations respond by adding channels: a web form, a chatbot, an email alias. Per SWOOP Analytics, employees spend an average of six minutes per day on intranet tools — well below the threshold of daily habit. The result is a service desk that technically covers every channel but reaches very few people consistently enough to change behavior. The organizations closing this gap are not adding more channels. They are building knowledge management tools that are governed, role-aware, and connected to the workforce systems employees already use — and they are measuring whether that knowledge is preventing tickets before claiming it works. ## Why most AI-powered service desks underdeliver The market for AI service desk software is mature enough that "AI-powered" tells you almost nothing about a platform's actual capability. The questions worth asking are narrower: which knowledge sources does the AI have access to, who decides what it can and cannot surface, and how do administrators measure answer quality over time? The gap most platforms leave open is permission-aware knowledge grounding. An AI assistant that returns results without respecting the employee's role, region, or department creates two failure modes. It either over-restricts — frustrating employees who cannot find answers they should have access to — or it under-restricts, surfacing sensitive policy documents to people who should not see them. Neither failure shows up in ticket volume dashboards until the damage is done. Governed AI knowledge delivery — where the knowledge base inherits the same permission model as the broader [employee experience platform](/solutions/employee-app) — eliminates both failure modes. It also gives administrators the measurement layer they need: deflection rates by role, article engagement by department, and content gaps identified precisely where tickets continue to be created after KB suggestions have been shown. Enterprise buyers evaluating knowledge management tools should ask vendors to demonstrate how their AI assistant governance works: which knowledge sources are in scope by default, how an admin changes what the AI can access, and what data exists to measure whether AI answers are accurate and current. Platforms that cannot answer those questions clearly have not solved the governance problem — they have deferred it. ## The structural gap for frontline workers Per Emergence Capital research, 80% of the global workforce is deskless. Per Social Edge Consulting research, 91% of organizations operate an intranet — but nearly a third of employees never log in, and only 13% use it daily. The arithmetic is clear: the support infrastructure most organizations have built was designed for the minority with a desk and a corporate email address. Frontline workers without corporate email cannot submit support requests through email-to-ticket channels. They cannot track status through web portals requiring SSO authentication. They cannot access a knowledge base through a site that only renders correctly on a laptop. A service desk designed for frontline access looks structurally different. Mobile-first submission, status tracking via secure token links rather than authenticated accounts, and knowledge delivery through channels employees already open — a team communication app, a push notification, or a workforce management app they check for scheduling updates — changes utilization because it changes reachability. Organizations that connect support access to mobile-first platforms consistently report higher self-service adoption among workers who previously submitted no tickets at all — not because the content improved, but because the channel became one they could actually use. Frontline support adoption is not primarily a change management problem. It is an access design problem. ## Routing and SLA discipline are expected — what separates platforms is integration depth Workload-based routing, skills-based assignment, SLA breach monitoring, and sentiment-flagged escalations are present in every enterprise service desk platform at this point. These capabilities matter, but they are no longer differentiating. The capability that distinguishes platforms is HRIS integration that automatically syncs employee roles and permissions — eliminating the manual provisioning delay that most new-hire tickets trace back to. When a new employee's role, department, and location are inherited from the HR system rather than entered manually by an IT administrator, the access provisioning queue shrinks because provisioning happens before the employee submits the request. No-code workflow automation that extends beyond IT tickets — covering HR requests, Facilities, and Procurement in the same submission interface — reduces the cross-departmental overhead that inflates ticket volume in organizations running fragmented point solutions. The service desk becomes the operational layer where support requests from every function are captured, classified, and routed, rather than a specialized tool for one department's problems. This is the operational case for a [unified HCM and employee platform](/solutions/modern-hcm): when the service desk shares a data model with HR, workforce management, and scheduling, access changes propagate automatically, and knowledge can be scoped to a role the HRIS defines rather than a group an IT administrator has to maintain manually. ## What effective deflection measurement looks like The analytics layer most service desks provide — ticket volumes, resolution times, CSAT scores — measures how well the desk handles incoming demand. It does not measure whether the desk is reducing demand. Deflection tracking closes that gap. When the submission interface surfaces KB articles and logs whether employees read them before abandoning the form, the data becomes a precise content roadmap. Articles with high display rates but low click rates have a relevance problem. Articles with high click rates but low deflection rates have a resolution problem. Both are fixable once the data makes the distinction visible. Three signals worth tracking before and after any service desk improvement effort: deflection rate by article, average first response time by request category, and KB article freshness by department. If the same questions surface in tickets month after month, the answer is not in the knowledge base — that is a content gap, not a routing problem. The behavioral shift deflection tracking is designed to produce is cumulative. When an employee submits a ticket and receives a resolution that references information they could have found in a KB article — had it existed and been findable — the next time they have a question, they search first. That shift from defaulting to tickets to defaulting to self-service compounds across a workforce. Measuring it is the only way to know whether it is happening and what is causing it to stall. ## Questions organizations encounter after deploying AI service desks Once an AI service desk is live, the governance and measurement questions that predictably surface fall into two categories. On governance: what happens when the AI assistant returns an answer that is outdated? The answer depends on whether the platform has a content freshness model beyond edit date. Platforms that track only when an article was last edited do not catch content that has been touched but not reviewed for accuracy. A freshness scoring model that combines edit date, view rate, and deflection effectiveness gives administrators a signal that is harder to game with a minor formatting change. On measurement: how do you demonstrate ROI to leadership? The metric that translates best outside of IT is tickets-prevented per month. When the deflection dashboard shows that a significant number of tickets were abandoned after KB articles were displayed — each of which would have required agent time to resolve — the dollar value is calculable against headcount. That calculation, tied to a specific knowledge investment, is what makes the service desk visible as a cost lever rather than a cost center. For organizations evaluating where to invest in service desk improvement, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) provides context on how communication infrastructure investment connects to employee experience outcomes across industries and workforce types. ## Where the service desk evolution is heading The evolution described here is not primarily a technology change. It is an architectural one. A service desk that operates as a standalone ticket system — separate from the HRIS, separate from the knowledge base, separate from the communication tools employees use daily — produces the utilization numbers the market already has. Per Social Edge Consulting research, six minutes per day on intranet tools, and nearly a third of employees who never log in at all. A service desk embedded in a platform that shares the same role model, the same mobile channel, and the same knowledge layer produces different outcomes: lower ticket volume because knowledge is role-aware and reachable, faster resolution because routing inherits permissions without a manual handoff, and measurable self-service because deflection tracking makes the gap visible rather than assumed. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) findings, organizations where employees believe their needs are heard and addressed retain and engage more effectively than those that treat support as a back-office function. The service desk is often the first point of contact an employee has with organizational infrastructure. What it returns — a resolution, a KB article, or an unacknowledged ticket — shapes whether that employee develops a self-service habit or an avoidance one. The question is not whether your service desk has AI. The question is whether it knows who your employees are, what they are authorized to see, and whether you can measure whether that knowledge is reaching them before they open the next ticket. --- # When AI Stops Being a Tab and Becomes the Workflow **Author:** MangoApps Team **Published:** 2026-01-25 **Category:** news-and-updates Picture a safety inspector finishing her walkthrough of the production floor. She photographs a loose cable guard with her personal phone, jots three findings on her clipboard, and transcribes... # When AI Stops Being a Tab and Becomes the Workflow Per McKinsey, employees spend 2.5 hours every day searching for information they need to do their jobs. For knowledge workers, that's a productivity drag. For workers managing physical operations — production floors, facility audits, incident reports, SOP compliance — it's a different kind of problem. When a safety inspector can't surface the right procedure at the point of inspection, the 2.5-hour gap isn't measured in lost focus time. It's measured in compliance exposure. This distinction separates two fundamentally different architectures for AI in the workplace: AI as a product you navigate to, and AI as infrastructure embedded in the workflow itself. Most enterprise software has defaulted to the first model. Build the core product, add an AI layer, route users there when they need help. The mental model is familiar — when you need assistance, open the AI tab, ask your question, return to your work. It's workable for knowledge workers who can pause what they're doing. It's structurally mismatched for workers who are mid-inspection, processing an incident, or standing at an asset that needs a corrective action logged immediately. The shift toward embedded AI — intelligence that surfaces at the moment a decision needs to happen, without requiring the user to redirect attention — solves the convenience problem. It also solves a more consequential one: the compliance proof trail that most organizations can't reconstruct after the fact. ## Why the location of AI matters for compliance Per Banner Health's internal employee polling on intranet performance, 63% of employees say that intranet content is not current or relevant. Fifty-five percent want access from a mobile device. Sixty-one percent want access outside the work VPN. These numbers describe a content delivery failure, but they also describe a liability problem: when employees can't reliably find the current procedure, they may work from an outdated one, and no one knows which version they were following until an audit. The compliance proof trail that regulators want isn't just "we have the policy." It's who accessed the current version, when, and what happened afterward. When AI is a separate tab, that chain exists only if someone remembered to navigate there. When AI is embedded — at the QR code posted at an asset, in the incident record being processed, in the acknowledgment workflow triggered when a regulation changes — the chain builds itself. Consider the inspection workflow. When a facilities manager creates an inspection template from a plain-language description and the platform generates a structured checklist, the starting point is documented. When an inspector scans the QR code at an asset and the correct template appears, the timestamp and GPS location are captured. When a failed item automatically generates a [corrective action task with an assignment and a due date](/solutions/workforce-management), the accountability record exists without anyone deciding to create it. A compliance dashboard tracking pass/fail rates and open findings isn't the output of diligent data entry. It's the default state of the workflow. That same logic applies to incident management. When a safety manager investigating a near-miss has relevant procedures, guides, and training content surfaced in context — next to the incident record they're already working in — the relevant knowledge reached the right person at the right moment. The alternative is hoping the manager remembered to search for it, found the right version, and documented that they did. ## Evaluative AI vs. assistive AI: two different jobs The framing most enterprise AI vendors lead with is assistive: AI helps you work faster, find answers more quickly, draft communications with less effort. That framing is accurate as far as it goes. A second category of AI that matters more for compliance-sensitive organizations is evaluative: AI that reviews work already done and reports whether it meets a standard. An HR director uploading a handbook to a content grader and receiving a scored report — this compliance language is unclear, this policy reference is outdated, these two sections conflict — is using AI differently than querying a chatbot. The grader isn't making the work faster. It's catching the drift that accumulates when policies are written once and left alone while regulations, titles, and processes change around them. Per Banner Health's polling, 63% of employees already report that intranet content isn't current or relevant. A content grader surfaces exactly what's driving that number — and names the specific entries that need correction, in priority order. Sentiment-aware draft responses for service desk tickets occupy the same evaluative category. Before generating a draft, analyzing the ticket's emotional tone — reading the difference between an employee whose equipment has been down for two days and a routine access request — and calibrating accordingly isn't AI assistance in the conventional sense. It's AI judgment applied before the human has to make a judgment call. Agents start from a draft that already accounts for what kind of situation they're walking into. The practical distinction matters when evaluating whether AI tools in your environment are reducing cognitive load or simply making certain tasks slightly faster. Assistive AI compresses effort. Evaluative AI prevents the downstream costs of content drift and misjudged responses. ## The regulatory chain that keeps breaking in the middle The hardest compliance problem in large organizations rarely involves a single dramatic failure. It involves slow drift: a regulation changes, a policy doesn't follow, employees acknowledge the old version, and nobody closes the loop until an auditor asks. The chain between "a law changed" and "our policy reflects it" and "employees have acknowledged the updated version" has predictable break points. Someone hears about a new state requirement. A note gets made. Three months later, the policy hasn't been updated. Employees have signed off on the version from two years ago. That's where exposure lives. Embedded AI addresses this chain not by doing legal interpretation — that remains a human job — but by handling the connective work: surfacing the right alert to the right administrator when a regulation changes, identifying which specific policies may be implicated, tracking which employees have and haven't acknowledged the current version. The intelligence layer that prevents the chain from breaking in the middle is less visible than a new feature announcement. It's more operationally valuable. For organizations distributed across multiple sites or operating with a largely frontline workforce, this matters proportionally. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how distributed operations teams are rethinking content delivery and compliance workflows specifically for non-desk workers — the population for whom "check the intranet" is the least reliable instruction possible. ## Next questions organizations should answer before adopting embedded AI Embedded AI is not a universal improvement over dedicated AI tools. There are specific conditions under which dedicated tools remain the better choice, and specific failure modes to anticipate during implementation. **When dedicated tools still win.** Complex analytical tasks — scenario modeling, multi-step research, drafting that requires extended iteration — benefit from a focused AI interface where the user can refine, reprompt, and build on prior context across a session. Embedded AI is optimized for fast, contextual delivery: surface the right procedure at the right moment, generate a checklist from a description, flag which policies a regulatory change implicates. When the task requires sustained back-and-forth, a dedicated tool is the better architecture. **Implementation pitfalls that stall adoption.** The most common failure mode is treating embedded AI as an additive layer on a workflow that was already broken. If the inspection templates are incomplete, the AI-generated checklists will reflect that. If the policy library hasn't been audited in three years, the knowledge base surfaces outdated content in context. Embedded AI amplifies the quality of the underlying content — including its gaps. Organizations that deploy it before auditing their content library often see adoption stall because workers encounter AI-delivered answers that are visibly wrong or outdated. The content audit isn't optional; it's the prerequisite. **How to audit whether current tools are truly embedded or just relabeled tabs.** The test is direct: does the AI surface in context without the worker deciding to invoke it? If a worker has to click an "AI" button to activate a feature — even if that button is within the workflow view rather than a separate menu — it's a cognitive interruption. Genuinely embedded AI is invisible as a product decision. The worker interacts with the workflow; the AI capability is part of what makes the workflow function. An audit that asks "how many clicks from moment-of-need to AI response" surfaces the gap quickly and honestly. For organizations evaluating whether a platform's AI capabilities are embedded or additive, the [IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment](/resources/idc-marketscape-2024) provides independent scoring of AI integration depth across leading platforms, including how vendors handle frontline-specific use cases. ## What the shift actually produces The operational model where AI sits in a tab works for environments where workers have time to look for it. Manufacturing floors, multi-site facilities, distributed field teams, and healthcare operations are not those environments. For organizations where the majority of the workforce is non-desk — where the person doing the work is also carrying the device, standing at the asset, and responsible for both the action and the documentation — the gap between "we have AI tools" and "AI reaches the right worker at the right moment" is where compliance exposure lives. [Per Gallup's 2026 State of the Global Workplace research](/articles/gallup-2026-state-of-the-global-workplace), highly engaged workplaces see 14% higher productivity. Engagement among frontline workers is directly connected to whether they can find what they need when they need it — not after a desk lookup or a system navigation sequence. Embedded AI is the mechanism that closes that gap: not by adding a new feature, but by removing the step where a worker has to decide to look for help before they get it. That's not a UI design preference. It's a compliance architecture decision. When the safety inspector scans the QR code and the correct template appears — when the failed item generates the corrective action automatically, when the procedure exists in the right language at the right station — the audit trail exists because the workflow built it. The difference between embedded AI and tabbed AI is the difference between a proof trail that exists by default and one that exists only when someone remembered to create it. For most organizations running physical operations, the one that matters is obvious. --- # MangoApps Integrates Native Workforce Management and Next-Gen Generative AI to Unify the Modern Workplace **Author:** MangoApps **Published:** 2026-01-21 **Category:** press-release MangoApps, the unified workforce platform provider, today announced its 2026 Winter Release. This major update introduces native workforce operations, structural AI capabilities, and a modernized user experience, marking a strategic shift from helping employees write content to helping organizations operate more efficiently. # MangoApps Integrates Native Workforce Management and Next-Gen Generative AI to Unify the Modern Workplace Best-of-breed tool selection made sense when enterprise software was young enough that no single platform could handle scheduling, communications, and knowledge management simultaneously. The standard advice — pick the best scheduling tool, the best intranet, the best messaging platform — assumed that better individual components added up to a better overall system. The usage data from organizations that followed that advice suggests the assumption was wrong. Per IDC, employees spend 2.5 hours per day searching for information across fragmented systems. Per SWOOP Analytics, the average employee spends only six minutes per day inside their organization's intranet — meaning the platform that's supposed to surface that information isn't accessible enough to be used consistently. Per Social Edge Consulting, 91 percent of organizations operate an intranet, yet nearly a third of employees never log in at all. These numbers don't reflect low interest in information. They describe what happens when access requires too many steps across too many systems. For the 80 percent of the global workforce that is deskless or frontline, per Emergence Capital, those conditions are worse. Best-of-breed tools built for knowledge workers with company laptops and corporate email addresses don't solve the problem of a warehouse associate who needs to check tomorrow's schedule and receive a team update without IT provisioning their device. They create a parallel system that the formal tools never reach. The 2026 MangoApps Winter Release, available as of January 21, 2026, addresses this directly. By introducing native workforce scheduling, structural AI that builds interactive content from single prompts, and a redesigned employee experience layer, the release consolidates functions that most frontline organizations currently manage across three or more separate tools. ## The coordination overhead that fragmented stacks create Organizations rarely choose fragmentation deliberately. A scheduling solution gets added when the workforce grows. An intranet gets deployed for company-wide announcements. A messaging platform arrives during the shift to remote work. A separate wiki is stood up for documentation. Each decision was defensible at the time. The cumulative cost was never part of the original justification. The cost compounds at handoff points. A frontline worker who needs to swap a shift shouldn't have to leave the platform where they receive team communications. A clinical coordinator handing off patient assignments shouldn't need a separate message because the scheduling system doesn't integrate with the messaging tool. When the same shift-swap request generates a text message, a scheduling update, and a separate communications notification — or fails to generate one of those and causes a missed handoff — the cost shows up in operations, not in software licensing conversations. When that friction becomes part of the daily experience for frontline employees, it surfaces in turnover data before it surfaces in engagement surveys. The fragmentation that looked like a technical inconvenience at the point of tool selection shows up later as a workforce retention problem. ## When scheduling lives where the team already communicates The headline addition in the Winter Release is [Native Shifts & Schedules](/solutions/shifts-schedules), a built-in module for rostering, time and attendance, and leave management. For organizations currently running a separate workforce management tool alongside their employee app, this creates a direct consolidation path. Frontline workers get clock-in and clock-out controls, shift swap workflows, and time-off requests without switching applications. Managers gain automated tracking of actual versus planned hours, supporting compliance documentation and providing real-time visibility into labor cost variance. The module operates within the same access model as the rest of the platform — no separate IT provisioning step for each new employee. The experience change is concrete. Rather than logging into a separate application to check tomorrow's schedule, frontline workers see their schedule alongside their team feed, task assignments, and organizational updates — in the same app they already use daily. Adoption follows access, and access improves when the function is embedded rather than siloed. For healthcare systems currently on QGenda, field service organizations running Spectrum, or enterprises on SAP HCM, the Winter Release deepens existing integrations rather than requiring migration. The practical choice is between native scheduling for organizations starting without a WFM system and federated integrations for those with existing investments they aren't ready to consolidate. Operations teams evaluating the transition at the store or facility level will find the [Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) useful for the specific questions that arise at that decision point. ## Structural AI: building the components that work runs on Previous MangoApps AI capabilities concentrated on text generation — drafting posts, summarizing documents, translating content. The Winter Release introduces what the company calls structural AI: capabilities that build the interactive components that work runs on, not just the text that describes work. The distinction matters because most of the setup overhead in enterprise operations isn't writing — it's configuration. Traditional intranet and workspace deployments can take months from procurement to go-live, straining IT teams and delivering static content that becomes outdated before it's fully indexed. The Winter Release's AI-native configuration capabilities address the same core friction: organizational knowledge and process structure that already exists in one form but needs to exist in another to be usable. The AI Survey and Quiz Creator generates assessments and multi-page surveys from a single prompt or an uploaded document. A compliance trainer who previously spent hours converting a policy document into a training quiz can complete the same task in minutes, with configurable formats that meet specific compliance documentation requirements. The AI Wiki Builder converts static PDFs into fully formatted, searchable wiki pages. Organizations whose institutional knowledge lives inside document repositories — compliance manuals, procedures libraries, product catalogs — gain a path to making that knowledge retrievable without manual restructuring. The documents already existed. The gap was that they weren't structured for search. Instant Team Architecture builds complete project workspaces from a plain-language description. A manager who describes a new initiative gets a configured workspace — with permissions, layout, and description — rather than building each component manually. For organizations that stand up multiple project teams per quarter, the setup time reduction is measurable at scale. ## Discovery redesigned for how people actually search Three foundational tools that employees interact with daily received redesigns in this release. The search interface moves toward a faceted, intent-aware architecture. An AI Assistant Mode interprets natural language queries, addressing one of the most consistent complaints about enterprise search: that finding information requires knowing the exact phrase in advance. Deep indexing for Jira and Confluence means search surfaces results from the tools knowledge workers rely on for project management and documentation — rather than treating those systems as outside the platform's scope. The news feed redesign targets the noise problem that suppresses engagement in most intranets. Auto-collapsing long posts and removing system-generated clutter shifts the feed toward human communication — team updates, recognition moments, and project announcements employees actually seek out. Per [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), employee engagement correlates directly with whether workers feel informed and connected to their organization. A feed dominated by system notifications doesn't serve that function regardless of how frequently it's refreshed. The people directory redesign adds smart filters — including Recent Collaborators and Reporting Lines — to help employees identify subject-matter experts without manually navigating org charts. In distributed organizations, informal expertise-finding doesn't happen through office proximity. It requires directory tooling that surfaces relevant people based on working relationships, not just job titles. ## Named outcomes from organizations that made the consolidation move Feature descriptions answer what was released. Customer outcomes answer whether it matters. OU Health achieved 87 percent workforce engagement within months of launching a unified employee app for clinical staff — a result that followed from structural access, not training campaigns. When employees could reach the platform from a device they already carried, without credentials they didn't have, engagement metrics followed because the structural barrier was removed. TeamHealth consolidated more than 200 legacy enterprise systems into a single mobile workforce dashboard — an outcome that only becomes possible when the workflow layer integrates with existing infrastructure rather than adding another parallel system to maintain. These outcomes share one characteristic: neither required employees to change their behavior significantly. Both required organizations to change where the access boundary was drawn — to treat every worker as a full participant in the platform rather than an afterthought in a system designed for desk-based employees. Per the [IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024](/resources/idc-marketscape-2024) assessment, platform consolidation and AI-assisted workflow setup are the two capabilities most likely to drive adoption and retention gains near-term. The Winter Release advances both in a single release cycle. ## Evaluating whether consolidation changes your calculus For HR and operations leaders assessing the Winter Release, three questions produce more precise answers than reviewing capability lists. First: how many distinct applications does a frontline employee need to complete a single operational sequence — check the schedule, receive team communications, clock in, report an issue, and review a task assignment? If the answer is three or more, the consolidation case has a quantifiable return in license cost and training overhead, independent of any individual feature. Second: what share of administrative time each quarter goes toward building surveys, assessments, compliance quizzes, and project workspaces? If it's more than a few hours per cycle, the structural AI capabilities have a direct time-saving argument that doesn't require adoption modeling to validate. Third: what does current intranet engagement look like compared to SWOOP Analytics' six-minutes-per-day benchmark? If usage falls below that threshold, the problem is access and relevance — both of which the redesigned feed, search, and directory address more directly than additional content production would. "Companies have long struggled to stitch together separate tools for intranet, communications, and workforce management," said Anup Kejriwal, CEO of MangoApps. "We are closing the gap between 'knowing' and 'doing.' By bringing native scheduling and structural AI into the platform, we give operations and HR leaders the agility to run a modern, connected workforce." The Winter Release represents MangoApps' clearest positioning statement as a unified workforce platform. For organizations maintaining three or more tools to cover the functions this release consolidates, the question is no longer whether unification is technically possible — it's whether the ongoing cost of maintaining separate systems is still justified against what a single platform delivers when the access boundary finally includes everyone. --- # Closing the Compliance Gaps Nobody Had Time to Close **Author:** MangoApps Team **Published:** 2026-01-18 **Category:** news-and-updates The onboarding checklist said the new hire was ready to start. What it didn't say was that three jurisdiction-specific forms — required by California law — were missing from their file. # Closing the Compliance Gaps Nobody Had Time to Close Elena Marchetti had been the HR compliance director for a three-state logistics company for six years when an audit examiner asked her for the Colorado wage disclosure forms covering the past eighteen months of driver hires. She knew those forms existed — she had handled them personally in her first two years on the job. What she could not have known was that, somewhere in the intervening years of personnel turnover and workflow updates, the standard onboarding packet had stopped including them. She discovered the gap the same moment the examiner did. Jurisdiction-specific compliance failures during onboarding are among the top triggers for Department of Labor wage-and-hour audits in multi-state employers, per SHRM employment law guidance. A single I-9 or onboarding documentation violation runs from $272 to $2,701 per form under current ICE penalty schedules. Multi-form violations in a single audit compound quickly — the pattern that turns a routine document review into a six-figure exposure. Elena's operation was not negligent. It was architecturally vulnerable: compliance accountability lived in the person who had learned Colorado's requirements through years of handling them, not in the workflow that ran onboarding. When that institutional knowledge left the organization, the gap remained. The policy manual still existed. The checklist still existed. What did not exist was a system that surfaced the right requirement at the right decision moment. The difference between organizations that catch these gaps internally and those that find them in audits is not more diligence. It is where in the process the check runs — and whether it runs automatically, every time, at the moment the decision is made. ## The architecture problem underneath most compliance programs Standard compliance programs are additive. Build the workflow first; layer the review in afterward. Legal reviews the offer letter before it goes out. A supervisor reviews the inspection report and decides whether to create a follow-up task. A recruiter emails HR to confirm state requirements before completing a hire. Each review step is a gap. The gap exists because the check is a separate action that must be remembered, initiated, and completed — not an automatic condition of advancing the workflow. 74% of HR leaders report that manual compliance tracking across multiple jurisdictions is their top administrative burden, per SHRM HR technology research. That burden is highest precisely where bolt-on reviews concentrate: the manual steps added after workflows that were never designed to surface compliance requirements on their own. Workflow-embedded compliance inverts the sequence. When Elena's onboarding wizard moves to the "location" field and a hire's Colorado assignment is set, the jurisdiction-specific form requirements surface automatically. The Colorado wage disclosure becomes a prompted step in the workflow — not a discovery in an audit eighteen months later. The check runs at the decision moment because the decision moment is where the check has always needed to be. Competitors in the employee experience space frame compliance as a governance layer added on top of workflows — a permission structure, an approval queue, a reporting dashboard. The more durable architectural argument is different: compliance checks belong at the decision moment itself, embedded in the offer draft, the onboarding wizard, the inspection close-out. That is not a feature distinction. It is a structural one. ## Five places bolt-on compliance breaks These failure patterns appear with consistent frequency across multi-state employers and field-intensive operations. **Jurisdiction blindness in onboarding.** Multi-state HR teams typically rely on institutional knowledge — someone who learned California wage notice requirements through years of handling them. When that person leaves, the knowledge does not transfer. California wage notices, New York pay transparency disclosures, and FMLA documentation formats do not self-enforce. A location-triggered onboarding workflow closes this gap structurally: form requirements surface when the hire's state is set, not when someone remembers to check. **Inspection-to-action lag.** Paper-based and disconnected inspection programs create a documented gap between defect identification and corrective action assignment, per EHS field operations safety compliance benchmark research. The finding gets recorded. The remediation task never gets created. When a regulator reviews that inspection record and asks about the follow-up, the organization cannot account for the silence. Automatic corrective-action generation at inspection close-out closes the chain: when an inspector marks an item failed, the task generates immediately — with an assignee, a due date, and overdue escalation already attached. **Approval queue stalls.** Timesheets, leave requests, and compensation changes sit idle when the approving manager is unavailable. For payroll processing cycles, that stall means missed effective dates — which carry compliance consequences independent of the original decision. Absence-aware routing addresses this: when a primary approver is on leave, requests route to the next available person in the reporting chain automatically, without manual intervention. **Offer letter salary band drift.** Salary band violations in offer letters are a leading source of pay-equity litigation exposure, particularly in states with pay transparency laws — California, Colorado, New York, and Washington — per Littler Mendelson pay equity research. Without a validation step built into the drafting workflow, deviations go undetected until they become legal exposure. A compensation validation step that runs before the offer advances catches deviations at the draft stage, where the cost of correction is a revised number, not a settlement figure. **Manual compensation scheduling.** Approved salary changes with future effective dates depend on someone remembering to apply them at the right time. Merit increases that should take effect January 1 do not, because no one was watching the calendar. Scheduled auto-application closes this: approved changes apply on the effective date without manual processing. Each of these five patterns is predictable, preventable, and the kind of failure that looks worse in retrospect than it was in real time. None requires heroic effort to close. Each requires moving a check that currently lives outside the workflow to a moment inside it. ## The last-mile compliance problem in field operations Field operations compliance carries a structural challenge beyond the five patterns above: 80% of the global workforce is deskless, per Emergence Capital research. For field operations — inspectors completing checklists at remote facilities, technicians managing equipment across multiple sites — compliance failures rarely happen during the inspection itself. They happen in what follows. An inspector marks a finding. The form goes to a supervisor. The remediation task never gets created — because translating a field observation into a tracked, assigned, time-bound corrective action requires a manual step that does not happen consistently. In regulated industries — healthcare, food service, transportation, construction — the difference between a live compliance record and a reconstructed one is often the difference between an explanation and an exposure. Closing the inspection-to-action chain automatically means the corrective action generates when the inspector marks the item failed — assigned to the right person, with a due date and overdue escalation already built in. The inspector does not file a separate report. The supervisor does not manually translate the finding into a follow-up task. Offline sync, GPS capture, and photo annotations extend this to facilities without reliable connectivity: when the inspection closes, all findings are timestamped and attached to a verifiable record, not reconstructed from field notes afterward. For multi-site regulated operations, the practical outcome is continuous audit-readiness. When a regulator asks for inspection records for a specific facility over a given period, the answer is immediate retrieval — not a manual assembly process started under time pressure after the request arrives. ## What the structural fix looks like at scale The Raley's Companies deployed embedded compliance across 20,000 employees in a regulated retail environment — unified workflows, consistent documentation, and a single system of record that reduced compliance surface area across a distributed workforce. The [Raley's case study](/resources/raleys-case-study) covers the implementation sequence and outcomes in detail. For organizations [managing a unionized workforce](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too), where contractual obligations layer on top of statutory requirements, the embedded compliance argument applies with additional stakes: a missed contract requirement is not just a documentation gap — it is a grievance. A unified [workforce management platform](/solutions/workforce-management) that builds compliance into the decision moment creates a defensible audit trail without requiring record reconciliation across separate systems. The platform capabilities that matter are architectural, not cosmetic: location-aware onboarding configuration that surfaces state-specific requirements when a hire's location is set; automatic corrective-action generation that closes the inspection-to-action chain at close-out; absence-aware approval routing that prevents queue stalls without changing the underlying process; and scheduled compensation processing that applies effective-date changes without manual intervention. These are not features to evaluate in isolation — they are the structural conditions under which compliance becomes continuous rather than periodic. ## Sequencing the fix: where to start Not every gap carries equal risk. The practical sequence starts with three questions: Where does a single missed step create a documented liability window? Where does manual execution fail most frequently? Where does failure first become visible in an audit rather than in the workflow? For most multi-state employers, the answer to all three is onboarding documentation. Jurisdiction-specific forms are the most common trigger for wage-and-hour audits, the most likely to fail when institutional knowledge leaves the organization, and the most visible when missing in an audit record. The onboarding wizard is where the structural fix delivers the most consistent risk reduction. For asset-intensive field operations, start with the inspection-to-corrective-action chain. That is where documented liability windows accumulate most predictably, and where automation delivers measurable lag reduction within weeks of implementation. Offer letter salary band validation and compensation scheduling auto-application tend to follow — high-frequency failure modes individually, significant when they compound in states with active pay-transparency enforcement. Per the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook), the HR organizations reducing manual compliance burden most consistently are not adding review layers — they are rebuilding where the check runs. The financial stakes are specific: $272 to $2,701 per form in ICE penalty exposure, six-figure pay-equity settlements in active enforcement states, and 74% of HR leaders naming manual compliance tracking as their top administrative burden. Three months after the audit, Elena's company closed the Colorado wage disclosure gap by rebuilding the onboarding workflow to surface form requirements at the state-of-hire step. The next audit covered the same two-year period under a new review cycle. The examiner found nothing. That outcome is not diligence — it is the result of moving the check upstream to the moment when the decision still costs nothing to change. Organizations that close these gaps structurally do not eliminate compliance risk. They move it from the category of things that surprise them to the category of things their system handles before anyone had to notice. --- # A Modern Standard for Employee Engagement: Redesigned Search, Feed, and Communication Tools - 2026 Winter Release Deep Dive **Author:** MangoApps **Published:** 2026-01-16 **Category:** news-and-updates With the MangoApps 2026 Winter Release, we are introducing a comprehensive set of "quality of life" upgrades designed to reduce noise, improve clarity, and bring a modern, consumer-grade experience to the workplace. # A Modern Standard for Employee Engagement: Redesigned Search, Feed, and Communication Tools - 2026 Winter Release Deep Dive For employees, the intranet is often a "daily driver"—the first tab they open and the last one they close. But as digital workplaces grow, they often become noisy and cluttered, making it harder to find information or stay focused on what matters. The stakes are real: per IDC, employees spend an average of 2.5 hours per day searching for information, and per Social Edge Consulting, nearly a third of employees never log in to the intranet at all—even though 91% of organizations operate one. With the **MangoApps 2026 Winter Release**, we are introducing a comprehensive set of "quality of life" upgrades designed to reduce noise, improve clarity, and bring a modern, consumer-grade experience to the workplace. From a completely redesigned search interface to a cleaner news feed and smarter directory, here is how the new capabilities set a new standard for [employee engagement](/articles/gallup-2026-state-of-the-global-workplace). ## Redesigned Search: The "Google-Like" Experience Search is the most critical utility in any intranet. We have overhauled the search interface to make it faster, cleaner, and more intuitive. - **Faceted Results:** A new centered layout with smart filters on the left allows users to drill down by content type, date, or author instantly. - **AI Assistant Mode:** Users can now switch to "AI Assistant Mode" directly within the search bar. Instead of just finding a document, they can ask a natural language question, and the AI will scan accessible content to provide a direct answer. - **Unified Work Search:** New deep connectors for **Jira** and **Confluence** bring tickets and articles directly into search results, ensuring employees don't have to switch tabs to find technical documentation or project status. For organizations evaluating [modern intranet](/solutions/modern-intranet) platforms, unified search across tools is increasingly a baseline requirement—not a premium feature. ## A Modern, Noise-Free News Feed The news feed should be a source of connection, not distraction. We have refined the UI to prioritize readability and relevance. - **Cleaner Layout:** Long posts now auto-collapse with a "See More" option, and attachments like PDFs now display inline, allowing users to scroll through documents without leaving the feed. - **Reduced Noise:** We have eliminated system-generated clutter—such as notifications for deleted items or moved files—so the feed remains focused on human communication. - **Ticker Tape Broadcasts:** For urgent announcements that cut through the noise, admins can now deploy a scrolling "Ticker Tape" banner at the top of the portal, ensuring critical updates are seen immediately. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools—which means every interaction has to count. A cleaner, more relevant feed is not a cosmetic improvement; it is a direct driver of the daily active usage that makes an [employee app](/solutions/employee-app) worth deploying. ## The People Directory Overhaul Finding the right expert shouldn't feel like searching a spreadsheet. The new People Directory offers a visual, card-based interface that makes connection easier. - **Smart Quick Filters:** Users can instantly filter colleagues by "Recent Collaborators," "People Reporting to Me," or "My Department" with a single click. - **Customizable Browsing:** Admins can now configure up to five custom filters—such as Location, Job Title, or specific certifications—allowing employees to browse and filter talent using the attributes that matter most to your industry. - **AI Colleague Finder:** Integrated directly into the directory search, this AI agent helps users find people based on skills, expertise, or past projects (e.g., "Who knows about SOC2 compliance?"). ## Smarter Governance for Internal Comms For Internal Communications teams, managing quality and consistency across a large organization is a constant challenge. The Winter Release introduces AI as a partner in the governance process. - **AI-Assisted Post Approvals:** In our new multi-step workflow, AI acts as the first line of defense. It evaluates drafted posts for grammar, clarity, tone, and corporate compliance *before* they ever reach a human approver. This ensures that comms teams only review polished, compliant content. Beyond editorial quality, this layer also addresses security governance—flagging posts that may violate data-handling policies or regulatory requirements before they reach a broad audience, a capability now cited as a differentiator by enterprise buyers in the "secure intranet" evaluation category. - **Advanced Post Blocks:** Authors can now create richer, more interactive layouts using 10+ new customizable blocks, including embedded forms, polls, employee engagement surveys, courses, and trackers directly within a post. For a broader look at where internal communications is heading, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the governance and AI themes shaping enterprise comms strategy this year. ## Reaching Every Employee—Including Frontline Workers The UX improvements above are designed for every employee, not just those at a desk. Per Emergence Capital, 80% of the global workforce is deskless. Frontline employees can access the MangoApps intranet on personal devices without a corporate email address, VPN, or a desk—a deployment requirement increasingly cited as a baseline expectation by enterprise buyers evaluating modern intranet platforms. This matters because the same search, feed, and directory upgrades that benefit office workers are equally available to a warehouse associate checking shift updates on a personal phone or a field technician looking up a compliance document between jobs. Per Social Edge Consulting, only 13% of employees use an intranet daily—and closing that gap requires meeting workers where they are, on the devices they already carry. See how this plays out in practice in the [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study) case study. ## Experience Matters Adoption is driven by experience. By refining the core tools employees use every day—search, feed, and directory—MangoApps ensures that the intranet feels less like a legacy tool and more like the modern apps your workforce expects. The outcomes are measurable. Customers using unified employee experience platforms have reported frontline adoption rates of 87–90% within the first few months of launch, per Unily (CVS case study) and MangoApps (OU Health, Kansas City Chiefs case studies). British Airways achieved a 30-point engagement score increase after deploying a modern employee experience platform—a concrete benchmark for what experience-led design can deliver at scale. For independent validation of where MangoApps sits in the intranet market, see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) and the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report). **Schedule a demo** with our team today to see how MangoApps can bring together communications, HR, and operations for your business. **Learn more** about additional enhancements that were included in our 2026 Winter Release in the below Deep Dive articles: - Native Shifts & Schedules for a Unified Frontline Experience - AI That Does More Than Write: Instant Surveys, Quizzes, and Team Structures ## How Does the Winter Release Roll Out—and What Does Migration Look Like? The 2026 Winter Release features are available to all MangoApps customers on current subscription plans. The redesigned search interface, updated news feed layout, and new People Directory are applied automatically to existing portals—no IT-led migration or custom development is required. Admins can configure the new custom directory filters and AI-Assisted Post Approval workflows from the existing admin console. If your organization has heavily customized its [company portal](/key-features/company-portal) layout, the MangoApps customer success team can provide a guided review to ensure the new blocks and feed settings align with your existing configuration. ## Is the Winter Release Compatible With Our Existing Tools and Systems? Yes. The new Jira and Confluence connectors extend MangoApps' existing third-party integration layer and do not require replacing any current integrations. The AI Colleague Finder and AI Assistant Mode draw on content already indexed within your MangoApps environment—no new data pipelines are needed. Organizations using MangoApps [workspaces](/key-features/workspaces) for project collaboration will find that Jira tickets surfaced in unified search link directly back to the relevant workspace. For HR and operations teams evaluating broader platform fit, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the integration and consolidation decisions enterprise buyers are navigating this year. ## What Employee Engagement Outcomes Should We Expect? The Winter Release is designed to address the root causes of low intranet engagement—poor search, noisy feeds, and hard-to-find expertise—rather than surface-level metrics. Replacing a fragmented experience with one that employees actually use daily is the foundation for measurable engagement improvement. Organizations looking to build on these UX gains with structured employee engagement training, employee engagement courses, or employee engagement questionnaires can embed those directly into posts using the new Advanced Post Blocks feature. For a framework on connecting platform improvements to learning outcomes, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). --- # AI That Does More Than Write: Instant Surveys, Quizzes, and Team Structures - 2026 Winter Release Deep Dive **Author:** MangoApps **Published:** 2026-01-16 **Category:** news-and-updates In the Winter Release we are introducing new capabilities within MangoApps AI that allow you to build complex interactive structures—surveys, quizzes, wikis, and entire project spaces—from a single prompt or document upload. In our previous release, we introduced AI that could write, summarize, and edit text to help employees communicate faster. With the MangoApps 2026 Winter Release, we are taking the next logical step: moving from generative text to generative structure.For Ops, HR, and IT leaders, the bottleneck isn't always writing the content—it is the tedious setup of the tools themselves. Creating a multi-page survey, building a compliant quiz, or setting up a new department site usually involves dozens of clicks and configuration steps.The Winter Release changes that. We are introducing new capabilities within MangoApps AI that allow you to build complex interactive structures—surveys, quizzes, wikis, and entire project spaces—from a single prompt or document upload.Here is how updates in our Winter Release helps you deploy resources in minutes instead of hours.Create Surveys with AIGathering feedback should be easy, but building a properly structured survey often slows teams down. The new AI Survey Creator allows you to generate complete, multi-page surveys simply by describing what you need.From Prompt to Logic: You can enter a prompt like “Create a 10-question employee engagement survey,” and the AI will generate questions organized logically into sections. Once the draft is generated, you can jump seamlessly into the full Design mode to add advanced touches like conditional logic, branching, or specific branding, for a more streamlined experience.Smart Question Types: The AI automatically selects the appropriate field types for your questions, including NPS, Likert scales, multiple choice, and text responses.Industry Templates: If you don't want to start with a prompt, you can use pre-built templates for common use cases like Exit Interviews, 360 Evaluations, and Remote Work Check-ins.Generate Quizzes from Documents and CoursesAssessment is critical for compliance and training, but writing good questions and mapping correct answers is time-consuming. Our new release allows you to generate structured quizzes instantly from your existing content.LMS Course-Based Generation: Inside the LMS, you can now use the "Create Quiz with AI" action to scan course materials—including video transcripts and PDF content—to generate relevant questions automatically.Document-to-Quiz: For standalone assessments, you can upload a PDF or Word document, and the AI will generate questions based strictly on that source material, ensuring every question has a verified answer.Automated Answer Mapping: The AI doesn't just write the question; it identifies and maps the correct answers for multiple-choice questions, reducing setup errors.Turn Static Files into Dynamic WikisMigration is one of the hardest parts of modernizing an intranet. Organizations often have valuable knowledge trapped in static PDFs or Word docs.The new AI Wiki Creator transforms these static files into fully formatted, searchable wiki pages in seconds.Content Extraction: The AI extracts text, tables, and images from your uploaded document and formats them into a clean digital layout.Visual Polish: It automatically generates a relevant title and a professional banner image to match your branding.No Copy-Pasting: This eliminates the manual drudgery of reformatting legacy documentation, allowing you to populate your knowledge base instantly.Build Teams and Departments InstantlySetting up a new digital workspace—whether for a Department, Group, or Project—requires configuring permissions, layouts, and descriptions. The Winter Release introduces the ability to build these "containers" for work automatically.Instant Architecture: By simply describing the team's purpose (e.g., "A project space for the Q4 Website Redesign"), the AI generates the team name, description, and landing page layout.Context-Aware Setup: You can upload a project charter or planning document, and the AI will extract the context to populate the home page with relevant sections and headers.Bulk Creation: For large organizational changes, admins can generate plans for up to 10 teams at once, reviewing and refining them before they go live.AI in Widgets: Design on the FlyWe have also embedded AI directly into the dashboard and post editing experience. You no longer need to leave your workflow to fix a sentence or find an image.Writing Assistance: Rich Text widgets now include AI actions to rewrite, proofread, expand, or change the tone of your text directly on the page.Image Generation: If you lack a designer, you can now generate custom images directly within widget configuration screens. The AI automatically handles aspect ratios to ensure the image fits perfectly within the widget container.Structure at the Speed of ThoughtWith the new capabilities in the MangoApps 2026 Winter Release, AI becomes more than a writing assistant—it becomes an architect for your digital workplace. By automating the structural setup of surveys, quizzes, wikis, and teams, we are removing the administrative hurdles that often delay critical initiatives.This shift allows Comms, Ops, HR, and IT leaders to move from idea to execution in minutes rather than days. Instead of spending time on configuration and layout, you can focus on the strategy behind your content, ensuring that your platform evolves as fast as your business does.Schedule a demo with our team today to see how MangoApps can bring together communications, HR, and operations for your business. Learn more about additional enhancements that were included in our 2026 Winter Release in the below Deep Dive articles:Native Shifts & Schedules for a Unified Frontline ExperienceA Modern Standard for Employee Engagement: Redesigned Search, Feed, and Communication Tools --- # Native Shifts & Schedules for a Unified Frontline Experience - 2026 Winter Release Deep Dive **Author:** MangoApps **Published:** 2026-01-16 **Category:** workforce-management We are excited to announce the public availability of MangoApps Shifts & Schedules—a native system for rostering, time and attendance, and leave management. This update positions MangoApps as a true "superapp" for frontline operations, allowing Retail, Healthcare, and Manufacturing teams to manage their entire workday without ever leaving the platform. For years, organizations have used MangoApps to give frontline employees a view into their schedules by pulling data from third-party systems. While effective, this often meant juggling multiple vendors, complex integrations, and disconnected workflows. Per Emergence Capital, 80% of the global workforce is deskless — yet most [workforce management](/solutions/workforce-management) tools are still built for desk workers, leaving frontline teams dependent on fragmented productivity apps that don't talk to each other. With our 2026 Winter Release, we are moving from *integrating* workforce management to *operating* it. We are excited to announce the public availability of **MangoApps Shifts & Schedules** — a native system for rostering, time and attendance, and leave management. This update positions MangoApps as a true "superapp" for frontline operations, allowing Retail, Healthcare, and Manufacturing teams to manage their entire workday without ever leaving the platform. Here is how the Winter Release unifies operations to simplify life for your frontline teams. ## A Native Engine for Workforce Operations The now publicly available **[Shifts & Schedules](/solutions/shifts-schedules)** module removes the need for standalone WFM tools by building these core capabilities directly into the MangoApps platform. Instead of just viewing a static schedule, employees and managers can now execute operational workflows in real time. Consolidating employee self-service into a single platform has delivered measurable results for early adopters: organizations that have unified scheduling, communications, and HR into one application for productivity have seen a 52% decrease in support requests compared to running separate point solutions. That kind of reduction translates directly into lower administrative overhead and fewer vendor licensing costs — making the business case for platform consolidation a cost story, not just a UX story. - **Unified Roster Management:** Admins can now build and manage rosters directly within the platform, creating a single source of truth for shift assignments without needing third-party software. For organizations that prefer to keep their existing WFM systems, the MangoApps HCM/WFM connector can be configured to integrate that external data deeply into the employee experience. Explore the full scope of [solutions/modern-hcm](/solutions/modern-hcm) capabilities to understand how native HR and scheduling work together. - **Seamless User Mapping:** Whether using the native roster or an integration, the system automatically maps users via email or employee ID, ensuring that the right people always see the right shifts without manual duplication. - **Integrated Availability:** Employees can submit their future availability directly from their profile, allowing managers to plan rosters and schedules that align with employee preferences. - **Multilingual Shift Communications:** Inline translation for shift communications and task assignments is available across the platform — a retention and compliance lever for manufacturing and healthcare environments where 30 or more languages may be spoken on a single floor, per Beekeeper product page and Staffbase manufacturing case study. ### The Dashboard for Daily Operations We have overhauled the frontline dashboard with new widgets that turn the homepage into an operational command center. These tools allow employees to take action instantly: #### 1. Time & Attendance Employees can now clock in and out of scheduled or ad-hoc shifts directly from their dashboard using the [solutions/time-attendance](/solutions/time-attendance) widget. To ensure accuracy and prevent fraud, this widget enforces granular controls configured by admins: - **Geofencing & IP Validation:** Restricts clock-ins to authorized locations or IP ranges. - **Photo Verification:** Requires a real-time photo capture to confirm identity before a shift starts. - **Shift & Time Windows:** Ensures employees can only clock in during their assigned windows, preventing early starts or unassigned overtime. Automating these controls through no-code workflows reduces administrative bottlenecks without IT involvement — a capability that competitors like Beekeeper and Simpplr surface as a primary differentiator, and one that MangoApps now matches natively, per Beekeeper product page and Simpplr product page. #### 2. The Shift Marketplace Flexibility is a key driver of retention — and the data backs this up. Per the Gallup State of the Global Workplace, employee disengagement costs the global economy trillions annually, and schedule inflexibility is a leading contributor to frontline turnover. Organizations that have deployed unified employee experience platforms have achieved 90% frontline adoption within the first six months, a benchmark that reflects what happens when scheduling tools actually fit how frontline workers operate. For a practical look at how retail teams are applying these principles, see [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling). The new **Shift Marketplace** allows employees to pick up open shifts or swap assignments without administrative bottlenecks: - **List for Pickup:** Employees can list a shift they cannot work, making it visible to all eligible team members. - **Direct Offers:** Shifts can be offered privately to a specific colleague. Once accepted, the schedule updates automatically for both users. - **Manager Approval:** Shift owners retain control by reviewing and approving pickup requests before the schedule is finalized. Automating shift swapping and routine approvals through this native marketplace eliminates the back-and-forth that previously required separate teamwork management tools or manual manager intervention. #### 3. Time-Off Requests The new Time-Off widget simplifies leave management. Employees can view their pending and approved leave, check leave balances, and submit new requests directly from the dashboard. The system automatically validates these requests against business rules configured in the backend, providing instant feedback if a request cannot be processed. IDC research finds that employees spend an average of 2.5 hours per day searching for information — per IDC — and fragmented leave management systems are a significant contributor. Centralizing PTO requests inside the same cloud based productivity app employees already use for communications eliminates that search friction entirely. ### Attestation & Compliance Compliance is critical for hourly workforces. This new release also introduces **Shift Attestation**, allowing organizations to capture accurate records of "actual vs. planned" work hours. - **Variance Tracking:** The system records actual start and end times alongside the planned schedule, automatically calculating and highlighting any differences. - **Break Compliance:** Attestation respects admin settings regarding breaks, ensuring that calculations accurately reflect paid vs. unpaid time. - **Acknowledgement Tracking:** The system confirms which employees have seen policy or schedule updates — a compliance and risk-reduction feature for hourly workforces that competitors including Staffbase and Akumina cite as essential, per Staffbase case study and Akumina product page. This closes the loop between publishing a schedule change and verifying that every affected employee has received it. - **Secure & Private:** Location data is hidden during the attestation process to protect employee privacy. For organizations managing unionized or highly regulated workforces, these attestation controls are particularly important. See [Managing a Unionized Workforce Is Different. Your Software Should Be Too](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) for a deeper look at compliance considerations in shift-based environments. ### Enhanced Integrations for Hybrid Operations For customers who choose to keep their existing WFM systems, this release delivers deep new connectors that bring external data into MangoApps with greater fidelity. - **QGenda (Healthcare On-Call):** We now support a native integration with **QGenda**, allowing healthcare organizations to sync complex on-call physician schedules directly into MangoApps trackers for visibility. Healthcare teams can explore how this fits into a broader [industries/ambulatory-care](/industries/ambulatory-care) deployment. - **Spectrum (Real-Time Shifts):** A new connector for **Spectrum** enables real-time API calls to fetch the latest shift data whenever a user views their schedule, ensuring they never see stale information. - **SAP HCM (Payroll Visibility):** Employees can now view their up-to-date gross pay, net pay, and pay period details via a secure SAP HCM integration that refreshes data in real time. ## One App for Everything With the 2026 Winter Release, Workforce Management is no longer just an integration — it is a native part of the employee experience. By unifying scheduling, communication, and operations inside a single set of cloud based productivity applications, you reduce friction for your frontline teams and give them the clarity they need to succeed. The result is a measurable business outcome: fewer vendors to manage, lower licensing costs, and a frontline workforce that spends less time navigating disconnected sop operations and more time doing the work that matters. For a broader view of where workforce operations are heading, download the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook). To see how a large-scale retailer achieved this kind of unification in practice, read [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study). **Schedule a demo** with our team today to see how MangoApps can bring together communications, HR, and operations for your business. **Learn more** about additional enhancements that were included in our 2026 Winter Release in the below Deep Dive articles: - AI That Does More Than Write: Instant Surveys, Quizzes, and Team Structures ## How Long Does Implementation Take, and What Happens to My Existing WFM Data? One of the most common questions from operations and IT leaders evaluating native Shifts & Schedules is what the migration path looks like. MangoApps is designed to support a phased approach: organizations can run the native roster alongside an existing WFM integration simultaneously, using the HCM/WFM connector to sync external data while teams gradually transition workflows. User mapping via email or employee ID means existing employee records carry over without manual re-entry. For most mid-market deployments, the native module can be configured and live within a standard implementation sprint — no custom development required. The [MangoApps & Microsoft Integration Guide](/resources/mangoapps-microsoft-integration-guide) covers how existing HR and productivity tool data maps into the MangoApps environment for teams running hybrid stacks. ## How Does MangoApps Shifts & Schedules Compare to Standalone WFM Tools? Standalone workforce management platforms deliver deep scheduling functionality, but they require employees to context-switch between a scheduling app, a communications tool, and an HR system to complete a single workflow. Per Social Edge Consulting, only 13% of employees use an intranet daily, and per SWOOP Analytics, the average daily time spent in intranet tools is just six minutes — a signal that disconnected platforms fail to earn habitual use. MangoApps addresses this by embedding scheduling, time and attendance, leave management, and team communications inside one productive application. The practical effect: employees who already use MangoApps for messaging and task management encounter scheduling natively, without a separate login or context switch. For organizations evaluating the broader platform, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) benchmarks how unified platforms compare to point-solution stacks on adoption and administrative cost. ## What Does This Mean for Frontline Retention and Engagement? Schedule flexibility and operational clarity are increasingly cited as frontline retention levers. Per the cross-competitor consensus cited in the Gallup State of the Global Workplace 2022, disengaged employees cost organizations significantly more in turnover and lost productivity than the cost of the tools that would have kept them engaged. The Shift Marketplace directly addresses one of the most common frontline complaints — inability to swap shifts without manager bottlenecks — while Integrated Availability ensures that rosters reflect employee preferences from the start. For HR and operations leaders who want to understand how these dynamics are evolving, [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace) provides the broader workforce engagement context that makes the case for investing in frontline-first applications for productivity. --- # The Hidden Reason Global Recognition Programs Fail **Author:** MangoApps Team **Published:** 2026-01-11 **Category:** news-and-updates An HR director at a multinational company is tasked with launching a company-wide employee recognition program. The concept is straightforward: employees earn points for great work, redeem them... # Why Global Recognition Programs Fail: 5 Operational Blind Spots Most global employee recognition programs fail not because the idea is wrong, but because the operational infrastructure underneath them was never built for a multinational workforce. The recognition philosophy is sound. The budget is approved. The rollout happens. Then the program quietly falls apart at the edges — wrong products, missing size data, tax headaches, language barriers, and a catalog that feels US-centric to everyone outside headquarters. This article identifies the five operational blind spots that cause global recognition programs to underperform, and what a well-structured program actually requires to hold up across countries, currencies, compliance regimes, and languages. --- ## Why This Matters Before You Read Further Employee engagement is not a soft metric. According to Gallup's research, disengaged employees cost organizations real money in turnover, productivity loss, and absenteeism. Recognition programs are one of the most direct levers HR teams have — but only when they work. A program that excludes frontline workers, confuses employees in non-US offices, or creates a manual tax reconciliation nightmare at year-end does not raise engagement. It erodes trust in HR's ability to deliver. The five blind spots below are the most common reasons well-intentioned programs produce those outcomes. --- ## Blind Spot 1: The Catalog Is Built for One Country The most visible failure mode in global recognition programs is a rewards catalog that was designed for a US workforce and then extended globally without modification. UK employees see gift cards they cannot redeem. Employees in Singapore encounter merchandise that cannot be shipped to their region. Employees in France browse items marked unavailable at checkout. When employees in non-US offices encounter a catalog that feels like an afterthought, the message the program sends is the opposite of the one it was designed to send. Regional catalog configuration — where each employee sees only the products available in their location, and where physical merchandise can be assigned to specific countries or marked globally available — is not a premium feature. It is a baseline requirement for any program that spans more than one country. The fix is administrative, not philosophical: admins define store regions tied to specific countries, and the catalog each employee sees reflects their location. Products can be scoped regionally or globally. The configuration sits entirely with the program administrator. --- ## Blind Spot 2: Physical Merchandise Has No Variant Capture Any recognition program that includes branded merchandise — hoodies, jackets, bags — will eventually generate a support ticket from an HR team chasing an employee to confirm a shirt size after the order was already placed. This is not a hypothetical. It is the default outcome when a store does not capture size and color selections at checkout. Product variant capture — where employees select size, color, or other attributes at the point of redemption, and that selection is recorded on the order details page — closes the fulfillment gap that plagues physical merchandise programs. It sounds like a small detail. For any HR team that has fielded complaints about receiving the wrong item, or spent time manually reconciling order histories against employee preferences, it is not small at all. --- ## Blind Spot 3: Language Is Treated as an Afterthought Global recognition programs routinely address catalog regions and currency but never address language. An employee in a multilingual workforce who receives a recognition notification in a language they do not read fluently is not being recognized — they are being reminded that the program was not designed with them in mind. Inline translation support across 200+ languages is a baseline expectation for frontline recognition platforms serving multilingual workforces, according to research from Beekeeper and MangoApps' own frontline product documentation. Recognition content, notifications, and program communications should be accessible in the employee's preferred language, not just the language of headquarters. This is particularly relevant for frontline and deskless workers. According to Emergence Capital, 80% of the global workforce is deskless. These employees are disproportionately multilingual and disproportionately excluded from recognition programs that were designed for office-based, English-speaking workers. --- ## Blind Spot 4: Frontline Employees Have No Access Path Recognition programs that require a company email address and a desktop login to participate structurally exclude the employees who most need to feel recognized. Frontline workers — in hospitality, logistics, healthcare, retail, and manufacturing — often work on personal devices, do not have company email addresses, and are not sitting at a desk during the workday. According to Emergence Capital, 80% of the global workforce is deskless. A recognition program that does not include a no-email-required mobile access path is, by design, a recognition program for the 20%. The access gap is fixable: mobile-first design, QR-code-based login, and SMS-based notifications can bring frontline employees into the same recognition program as their office-based colleagues. But it requires the program to be designed with that access path in mind from the start, not retrofitted after the fact. For organizations in industries with large frontline populations, this is not a secondary consideration. It is the primary one. The symplr case study illustrates what a well-executed recognition rollout looks like when access and participation are designed in from the beginning. --- ## Blind Spot 5: Tax Compliance Is a Manual Process Every Q4, finance teams at multinational organizations face the same problem: figuring out which reward redemptions cross the reporting threshold in the US and UK, calculating fair market values, and producing documentation that can be handed to payroll. When recognition platforms do not generate tax compliance reports, that work falls to HR and finance manually — cross-referencing order histories, calculating per-employee redemption totals, and building spreadsheets from scratch. This is the kind of operational friction that does not show up in a recognition platform demo. It shows up in November, when someone realizes the year-end reconciliation is going to take two weeks. Pre-formatted tax compliance reports — with per-employee redemption summaries, configurable tax thresholds, and CSV exports — convert a multi-day manual process into a handoff. This is not a feature that makes recognition programs better for employees. It is a feature that makes recognition programs survivable for the HR and finance teams running them. --- ## The Structural Problems Underneath All Five Blind Spots The five blind spots above are symptoms of two deeper structural problems that most recognition programs share. **The first is that recognition programs are built as standalone tools, not as integrated systems.** When a recognition platform does not sync with the HRIS, eligibility and enrollment become manual processes. Roles change, employees move between locations, new hires join — and the recognition program does not know. Recognition programs that integrate directly with HRIS systems to sync roles, locations, and eligibility automatically reduce admin overhead and eliminate the manual cross-referencing that accumulates over time, according to MangoApps' integrations documentation and comparable competitor product pages. HRIS-driven auto-enrollment is the structural fix for the eligibility drift that makes global programs increasingly inaccurate over time. **The second is that recognition programs are designed without a measurement layer.** A recognition program where 20% of managers account for 80% of nominations is telling you something important about the other 80% — but only if you have the analytics to see it. Program analytics that track participation rates, award distribution, and recognition patterns by team and region make the program's gaps visible. Workforce analytics that connect recognition participation to turnover data by location and department make the program's impact measurable. Without that measurement layer, recognition programs run on good intentions and anecdote. With it, they become a feedback loop: structured programs, global redemption infrastructure, and workforce data that connects recognition activity to retention outcomes. --- ## What a Well-Executed Global Recognition Program Can Achieve The failure narrative above has a counterpart. Organizations that address these blind spots before launch — rather than after — see materially different outcomes. Benchmarks from large enterprise recognition and engagement deployments show 90% frontline adoption within the first six months when access, language, and catalog configuration are designed in from the start. Structured recognition and communications programs have been associated with 30-point engagement score increases in documented deployments. These are not guaranteed outcomes, but they represent what the upside looks like when the operational infrastructure holds. For context, Gallup's 2026 State of the Global Workplace documents the ongoing cost of disengagement globally — and the degree to which recognition and manager behavior are among the most actionable levers available to HR teams. --- ## How to Audit Your Recognition Program for These Blind Spots Before your next program cycle, run through this checklist: 1. **Catalog coverage**: Can every employee in every country your program covers see and redeem products that are actually available to them? 2. **Variant capture**: Does your store capture size and color selections at checkout, and are those selections visible on the order record? 3. **Language access**: Are recognition notifications and program communications available in the preferred languages of your multilingual workforce? 4. **Frontline access**: Can employees without company email addresses participate in the program on a personal mobile device? 5. **HRIS sync**: Is eligibility driven by your HRIS, or is it maintained manually? 6. **Tax compliance**: Can your platform generate per-employee redemption summaries formatted for US and UK tax reporting without manual assembly? 7. **Analytics**: Can you see participation rates, award distribution, and recognition patterns by team, region, and manager? Any "no" on this list is an operational gap that will accumulate friction over time. The programs that survive long enough to move the needle on [employee engagement](/solutions/employee-engagement) are the ones that close these gaps before launch, not after. For HR teams evaluating whether their current platform can support a global program, MangoApps' [rewards and recognition features](/key-features/rewards-and-recognition) address each of these dimensions — regional catalogs, variant capture, multilingual support, frontline mobile access, HRIS integration, tax compliance reporting, and program analytics — in a single platform. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the broader workforce context in which recognition programs operate this year. --- # The Tool-Switching Tax That HR Teams Pay Every Day **Author:** MangoApps Team **Published:** 2026-01-04 **Category:** news-and-updates Picture a compliance manager on a Thursday morning in late December. She needs to know which employees in the engineering department have certifications expiring before Q1 closes. # The Tool-Switching Tax That HR Teams Pay Every Day Per IDC, employees spend 2.5 hours per day searching for information they cannot easily find. For desk workers, that friction is an inconvenience. For HR, compliance, and operations teams — where decisions about certifications, pay, and access to critical systems happen under time pressure — it is a structural problem with compounding consequences. The switching tax is the cumulative cost of moving between disconnected tools to complete a single task. A compliance manager who needs to verify expired certifications opens a spreadsheet maintained separately from the HR system, cross-references email threads for attached documents, and manually tracks which employees are due for renewal. A compensation manager working through a merit cycle opens the planning tool, then opens a second system to check pay band positions, then opens a third to look up market benchmarks. The decision gets made with partial context, or with no additional context at all. This is not a habits problem. It is an architecture problem — and the architecture problem is getting harder to ignore. ## Why the compliance window stays open Certification management looks straightforward until the first serious audit. The data exists in some form: a spreadsheet, a shared drive, a field in the HR system someone started filling in years ago. The problem is that no one has an authoritative view of what is current, what is expiring, and what is already overdue. According to Social Edge Consulting, 91% of organizations operate some form of intranet. Yet only 13% of employees use those tools daily, and nearly a third never log in at all. SWOOP Analytics found that employees spend an average of six minutes per day inside intranet platforms. The systems that should be organizing compliance information are, in practice, rarely open. The downstream effect is predictable. Compliance managers build shadow systems — spreadsheets, shared folders, recurring calendar reminders — to maintain visibility that the formal system does not provide. Those shadow systems require manual upkeep. When someone is on leave or leaves the organization, the institutional knowledge embedded in those workarounds often disappears with them. The structural fix is to bring certification data into the same workflow where decisions happen: a dashboard that shows certification status by employee, department, and expiration date, filterable, with configurable alert thresholds. Document management for renewed certificates within the same interface closes the audit trail gap. What changes is not just efficiency — it is the shift from reactive remediation to continuous monitoring. Certification compliance and learning infrastructure are not separate problems. An employee who completes a renewal is not just checking a compliance box — they are adding a capability that the organization needs to track, develop, and build on. Connecting compliance tracking to broader [learning and development](/articles/learning-and-development-strategy-embedded-in-daily-work) workflows positions certification management as a workforce investment, not just a regulatory obligation. ## The merit planning context problem Pay decisions have a longer tail than most HR decisions. A merit increase made without full context — without knowing whether an employee is below their pay band midpoint, or how their total compensation compares to external benchmarks — can compound into pay inequities that take years and significant budget to correct. The context problem in merit planning is structural. Planning tools typically surface recommended increases based on performance data, but they do not always show where each employee sits relative to their pay band, how the proposed increase would affect their market position, or which employees in a cohort are most at risk of being below market after the cycle closes. That information exists in compensation benchmarking tools, band management systems, and HR analytics platforms — but it lives somewhere other than the screen where the decision is being made. When a compensation manager has to leave the planning interface to look up pay band data, two things happen. First, the probability of checking decreases — the friction of switching creates a default toward the recommendation already on the screen. Second, when the check does not happen, the decision suffers. Aggregated across a full merit cycle, those small omissions can shift compensation distribution in ways that do not surface until the next engagement survey or the next round of exit interviews. The practical improvement is context surfacing within the decision interface: showing each employee's position within their pay band alongside their market comp ratio, in the same screen as the merit recommendation, changes behavior without requiring a policy mandate. For organizations examining how modern compensation tools support pay equity and workforce planning, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) provides a framework for evaluating compensation workflow design against current practice. ## The access gap that multiplies the cost The tool-switching problem is uneven. For desk employees, switching between applications is friction but not a barrier. For employees without dedicated workstations or corporate email accounts — hourly workers, frontline staff, field technicians — switching between applications often means switching between access models entirely. Per Emergence Capital, 80% of the global workforce is deskless. According to Social Edge Consulting, nearly a third of employees never log in to the intranet. The platforms that HR and IT teams build for workforce management were largely designed around desk employees: browser-based portals, VPN requirements, corporate email authentication. For the majority of workers who do not have those resources, the tool-switching tax is not an inconvenience — the tools are simply unreachable. That access gap compounds every other friction described here. A deskless employee who cannot reach the platform cannot see their certification status, cannot check their shift schedule, cannot receive compliance communications. The information exists but does not reach them. The consequence appears not as a visible system failure but as operational drift: compliance gaps, scheduling errors, decisions made without information that was technically available. Mobile-first access design addresses the access gap at the infrastructure level. When enrollment does not require a corporate email address or IT provisioning, and when the platform works on a personal device, the population that can reach the system expands to include the workforce segments most likely to be unreachable under the current architecture. ## What a realistic consolidation path looks like The case for consolidation is direct: when workflows that depend on each other live in separate systems, the switching cost is a structural feature of the architecture. Bringing those workflows into a single environment removes it. The harder question is sequencing. Organizations that attempt to consolidate everything at once typically struggle with change management burden and end up with partial adoption that replicates the original fragmentation problem. A more durable path is to identify two or three high-friction workflows — the ones where employees most visibly switch between systems to complete a single task — and consolidate those first. Certification compliance, merit planning, and credential management represent three workflows with different owners but the same root cause: the data needed to complete the task lives somewhere other than where the task is happening. Each is a tractable starting point. Each produces a measurable adoption signal within a single cycle. The compounding effect of consolidation comes later, in the connections between workflows. When a compliance review surfaces a training gap and both the compliance data and the training assignment live in the same platform, the response time from detection to remediation shortens. When a merit cycle reveals a workforce segment is systematically below market and workforce planning data lives in the same environment, the connection between pay and headcount planning becomes visible. A [unified employee experience platform](/solutions/modern-hcm) is not just about having multiple things in one place — it is about the connective tissue between workflows that makes those connections actionable. ## How to measure the return on consolidation The cost of fragmentation rarely appears on a single line item, which is part of why it persists. The costs are distributed: compliance remediation spend when certifications lapse undetected, attrition from pay inequities that were not caught during merit cycles, and the accumulated productivity loss from context-switching. Per IDC, 2.5 hours per day lost to information search across a 500-person HR and operations organization compounds into thousands of hours annually — time that could be redirected to higher-judgment work. The ROI calculation for consolidation has three components. Direct cost avoidance captures the reduction in compliance incidents, remediation spend, and manual reconciliation effort. Productivity recovery captures the time returned from tool-switching and from maintaining shadow systems that exist because the official systems do not serve operational needs. Decision quality improvement captures the effect of better-informed merit decisions, faster certification renewals, and reduced attrition from pay inequities caught earlier in the cycle. A fourth lever, often underestimated, is speed of execution on routine decisions. When routine HR approvals — shift swap requests, PTO sign-offs, task assignments — can be processed through automated workflows without IT involvement, process latency for frontline managers drops. The cumulative effect is not just operational; it affects whether managers direct their teams toward the platform or around it. For organizations building the ROI case for consolidation, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides a framework for quantifying these categories against the current tool stack. Organizations that have completed phased consolidations have found that the adoption curve accelerates once two or three core workflows are in a single environment — the Santee Cooper deployment, connecting communication, compliance, and scheduling across a distributed workforce, is one documented example. ## What changes when the data lives in the workflow The tool-switching tax is not a side effect of growth. It is what happens when systems are built to manage separate processes rather than to support people doing connected work. Compliance, compensation, and credential management look like separate domains. In practice, they all turn on the same question: does the person making a decision have the information they need, at the moment they need it, without leaving the context they are working in? When the answer is consistently no — when managers maintain shadow systems because the official systems do not meet their operational needs — the problem is architectural. Adding features to disconnected tools does not close the gap. The switching cost is built into the architecture. Closing it requires a different architecture, not a longer list of integrations. The organization that solves this problem does not just reduce friction. It produces a different quality of decision-making across every workflow it touches: compliance that is proactive rather than reactive, merit cycles that account for the full compensation picture, and frontline access that does not break down at the point where most of the workforce actually lives. --- # From Resignation to Rehire: Managing the Full Employee Lifecycle **Author:** MangoApps Team **Published:** 2025-12-28 **Category:** news-and-updates Every February, HR inboxes fill with the same request. A former employee — offboarded three, six, maybe eighteen months ago — needs their W-2. # From Resignation to Rehire: Managing the Full Employee Lifecycle Managing the full employee lifecycle means treating resignation, offboarding, post-employment document access, and rehire as connected, auditable processes — not isolated events handled through scattered email chains. When these moments run through structured workflows with documented approval chains, compliance exposure shrinks, administrative burden shifts from HR inboxes to self-service systems, and the organizational intelligence embedded in employment records becomes retrievable rather than lost. Most workforce software is built entirely for active employees. The moment someone submits a resignation, the tools that managed their career begin working against the people handling the departure. Exit paperwork becomes a scramble. HR learns about decisions through secondhand email chains. Document requests route to inboxes that may or may not belong to someone still at the company. Offboarding failures carry real legal exposure: incomplete I-9 retention, missed COBRA notices, and undocumented final-pay approvals are among the most common HR compliance violations cited in audits, per SHRM and employment law practitioners. This piece covers the full arc — resignation workflows, former employee document portals, rehire continuity, audit history, and compensation visibility — and what it takes to manage that arc as a lifecycle talent operations discipline rather than a series of disconnected transactions. ## When departure is a formal process, not a side conversation A formal resignation is one of the most process-heavy moments in employment and one of the most likely to go sideways without infrastructure. Managers get notified verbally. HR learns about it secondhand. The two weeks' notice period passes in a fog of ad hoc handoffs — and when the employee walks out, the record of who approved what, and when, exists only in scattered message history. Structured resignation workflows change the mechanics. When an employee submits a resignation through the platform, the request routes automatically to their manager, department head, and HR. Each stakeholder can review, approve, or add notes. Notifications fire at each step. An approved resignation directly triggers offboarding — no manual handoff between systems, no gap where something falls through. The documented approval chain is the compliance safeguard. It is the difference between an audit-ready offboarding and a liability. For organizations in regulated industries or with [union contracts that require documented SOP operations](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too), that distinction matters at every step of the departure process, not just the final paperwork. ## The post-employment relationship most HR platforms ignore Every February, HR inboxes fill with the same request: a former employee needs their W-2, a pay stub for a rental application, or an employment verification letter for a visa. The person is gone from the payroll system and the org chart, yet the need is very much alive. Without structured post-employment infrastructure, those requests land in HR inboxes, wait for someone to locate the right file, and go out by email — assuming anyone is still around to handle them. IDC research found that employees spend an average of 2.5 hours each day searching for information. For HR teams without a structured document retrieval system, a meaningful share of that burden is post-employment requests from people no longer in the system at all. A former employee document portal changes this. After offboarding, former employees gain access through their personal email — not work credentials, which no longer exist. They can download pay stubs, W-2s, and HR files on their own and submit requests for AI-generated experience letters without touching HR's inbox. Persona-based, role-aware access controls ensure former employees see only their own documents, not org-wide HR files — a governance requirement that makes the portal audit-ready rather than ad hoc. Admins control access duration and available document types, so the portal operates within the organization's policies rather than on the former employee's timeline. The AI-generated letter capability matters more than it might initially appear. Admin-controlled templates mean letters are consistent and audit-ready, not drafted from scratch each time someone needs proof of employment. That consistency reduces HR time and eliminates the risk of discrepancies between letters issued to different employees for the same role. ## Boomerang employees need a native return path Boomerang employees — people who leave and return — represent a meaningful and growing share of enterprise hires. Per SHRM and HR analyst coverage on this trend, boomerang employees typically ramp to full productivity faster than new hires and report higher retention in their second tenure. Yet most HRIS platforms have no native rehire path that preserves prior employment history. Rehiring a former employee typically means treating them as a brand-new hire: re-entering data, re-establishing history, starting fresh on tenure. The institutional memory the organization built during the first employment disappears. A structured rehire workflow takes a different approach — surfacing the prior employment record, checking eligibility, and reactivating the profile in a guided flow, with employment history, tenure data, and prior compensation records preserved through the transition. Organizations that replace manual processes with digitized workflows see up to 50% faster new-hire onboarding, a benchmark that applies equally to rehire processing where much of the data entry is eliminated. The [Gallup 2026 State of the Global Workplace report](/articles/gallup-2026-state-of-the-global-workplace) documents the conditions driving employee mobility: when people leave for opportunity or flexibility and find the external market doesn't match their expectations, they return. Organizations that can make that return frictionless have a structural retention advantage over those that start the process from scratch every time. ## The audit trail that makes lifecycle management defensible Every change to an employee's profile — job title, department, compensation, manager — should be logged with the old value, the new value, and a timestamp. For a returning employee, that audit history makes their prior tenure traceable, not just preserved in spirit. HR reviewing a rehire can see exactly what changed during the prior employment and when. For active employees, the same trail supports promotion decisions, compliance reviews, and any situation where the sequence of changes matters. Audit trails do more than protect against compliance violations. They close the information search gap that forces HR teams to reconstruct history from email threads and shared folders. A structured audit history turns what would be a multi-hour investigation into a filtered lookup. For organizations that need tighter controls, field-level approval workflows add an enforcement layer on top of the audit trail. A change to an employee's compensation can be held pending until a department head and HR director both sign off. Workflows can be scoped by field or risk category and can require supporting documentation before the change moves forward. The audit history records what happened; the approval workflow governs what is allowed to happen. ## Compensation visibility throughout the arc There is a thread running through lifecycle talent operations that often goes unexamined: whether employees understand the full picture of their compensation at each stage. Employees who can see their equity grants, RSUs, and vesting schedules alongside their base pay and bonus targets are better positioned to make informed decisions — about whether to stay, when to negotiate, and what an offer from a competitor actually represents relative to unvested equity. On the HR side, AI-assisted compensation band management lets teams define minimum, midpoint, and maximum ranges by grade, import and export in bulk, and fill gaps for newer roles where external benchmarking data is thin. Pay bands grounded in current market data hold up better over time than ranges set and forgotten in a spreadsheet. Neither compensation visibility nor structured pay bands prevents turnover on its own — but the pattern they represent shapes whether someone decides to stay, leave, or consider coming back. ## What lifecycle talent operations looks like at scale Emergence Capital estimates that 80% of the global workforce is deskless — field technicians, retail associates, healthcare staff, manufacturing workers. These employees are disproportionately underserved by lifecycle systems built around email and desktop forms. When resignation and rehire workflows run on mobile-accessible platforms, the equity gap between desk-based and frontline employees closes. Organizations that have deployed structured [workforce management](/solutions/workforce-management) workflows report 90% frontline adoption within the first six months, evidence that the operational model works when tooling is built for the full workforce, not just the office population. The organizations finding this transition most straightforward start with explicit process documentation: what each stage of the lifecycle requires, who owns each step, and where data needs to go when the cycle closes. That documentation usually exists in the institutional memory of HR coordinators who have been running these processes manually for years. Getting it into a structured workflow map is the prerequisite for any automation, regardless of which platform the organization selects. ## How long does implementation take? Resignation and rehire workflows built on an existing workflow engine require no custom development. Organizations with defined offboarding policies can typically configure and test the resignation workflow in days. A former employee document portal requires an admin to define document categories, set access duration, and configure AI-generated letter templates — most HR teams complete this in a single configuration session. The rehire workflow depends on data quality in existing employee records. Organizations with clean historical data can expect a faster path; those migrating from fragmented systems may need a data normalization step first. For organizations not yet ready for a full platform change, the most impactful near-term step is documentation: defining what a compliant offboarding looks like, who approves each step, and where records are stored. That policy work is the prerequisite for any workflow automation and reduces compliance exposure regardless of which platform eventually enforces it. ## Frequently asked questions ### What should an offboarding compliance checklist include? At minimum: final pay approval with a documented sign-off, COBRA notice delivery confirmation, I-9 retention verification, benefits termination confirmation, equipment return record, and system access revocation log. Each item needs a timestamp and an owner. Organizations with union agreements should also verify that notice periods and separation documentation meet the terms of the relevant collective bargaining agreement. A structured offboarding workflow encodes these steps so nothing depends on an individual coordinator remembering the full list under time pressure. ### When does prior service count toward benefits in a rehire? This is a policy decision, not a platform default. Most organizations distinguish between voluntary departures in good standing — which may qualify for prior service credit — and involuntary terminations, which typically don't. For benefits accrual specifically — PTO, retirement vesting, health plan waiting periods — the plan documents control what's permissible. The rehire workflow should have the eligibility policy encoded at configuration time so the decision is applied consistently, not made ad hoc when the first boomerang employee appears. ### How do we measure success after deploying lifecycle workflows? Three metrics matter in the first six months: offboarding completion rate (what percentage of departures move through the full documented workflow rather than bypassing it), post-employment document request volume handled through the portal versus HR inbox, and rehire processing time compared to new-hire processing time. Each measures a different dimension of the investment — compliance coverage, operational efficiency, and speed of return-to-productivity respectively. Tracking all three together gives HR leadership a clear picture of where the workflow is working and where policy gaps remain. ## The shift worth making The case for treating resignation-to-rehire as a connected, auditable discipline is not primarily about efficiency — though the efficiency gains are real. It is about organizational intelligence. Employment history, compensation decisions, and departure circumstances that aren't captured in a queryable format don't become useful retrospectively once a platform is in place. Every manual cycle run before migration is another period where that intelligence degrades. Organizations that manage this transition well treat lifecycle talent operations as an operational input that needs to be accurate, accessible, and connected to the systems that act on it — not as an HR administrative artifact separate from day-to-day operations. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading organizations are formalizing lifecycle talent operations policies and the tooling to enforce them at scale. --- # Closing the Accountability Gap in Workforce Operations **Author:** MangoApps Team **Published:** 2025-12-21 **Category:** news-and-updates Picture this: a safety incident happens at a warehouse. Within hours, the compliance team is asking which employees completed the annual safety training, when the affected worker's role last... # Closing the Accountability Gap in Workforce Operations Accountability gaps in workforce operations form in three predictable places: where coaching conversations happen but go unrecorded, where training is delivered but completion is never centrally verified, and where purchase requests get approved without live budget context. In isolation, each gap looks manageable. Together, they create the scramble most operations teams already know — the post-incident search through email threads, spreadsheets, and institutional memory to reconstruct records that should have existed automatically. Closing these gaps does not require a wholesale technology replacement. It requires connecting the work that happens every day to the records that should exist as a result of it: structured meeting logs that surface at review time, training completion certificates stored in the same system as employee profiles, and procurement forms that show budget availability before approval rather than after. According to IDC, employees spend an average of 2.5 hours per day searching for information — a figure that compounds sharply when an audit requires retroactive reconstruction of decisions that should have been captured automatically. This article covers where these gaps form, why they persist even in organizations with mature HR and compliance programs, and what consolidated accountability infrastructure looks like in practice across performance management, learning, and operations. ## Why documentation gaps persist in mature organizations The instinct when accountability gaps surface is to blame process discipline. The actual cause is usually structural: the systems designed to capture decisions were not built to connect to each other, and the documentation burden of maintaining separate records is high enough that it quietly gets deprioritized. According to Social Edge Consulting, 91% of organizations operate an intranet, but nearly a third of employees never log in, and only 13% use one daily. SWOOP Analytics found the average employee spends six minutes per day using intranet tools. The gap between those numbers and what consistent daily use looks like is largely a friction problem: platforms that require separate authentication, that aren't accessible on mobile, and that weren't designed for the way frontline work actually happens don't get used — and records that depend on active system use don't get created. The result is a documentation pattern that looks complete at the system level but is full of holes at the record level. Training completion may exist in a third-party LMS that doesn't sync with the HR system. Performance history may exist in a manager's notes that were never formalized. Procurement approvals may exist in an email chain that nobody indexed. Each of these is an accountability gap — not because the organization failed to care about documentation, but because the tooling required an extra step to create it, and that step got skipped. ## The performance paper trail A manager sitting down to write a quarterly review and realizing their notes from the past three months of check-ins are scattered — a message thread here, a calendar invite there, a document that was never updated — is not an unusual scenario. They write from memory. The review becomes impressionistic rather than evidential. The link between regular coaching conversations and formal reviews is one of the most studied factors in whether performance management actually drives development or creates paperwork. When the two are disconnected, reviews become surprises for employees and managers both. When they're connected — when each coaching session is logged against the goals being discussed, and review time surfaces that history automatically — reviews confirm an ongoing conversation rather than reconstruct one. Alongside structured meeting records, employee audit history fills the adjacent gap: every change to a profile — job title, department, compensation, manager — captured with a timestamp, a before-and-after, and a record of who made the change. HR teams and direct managers can view history within their scope. Employees can view their own. The documentation that used to require an IT request to pull from system logs becomes immediately accessible to the people who need it. Together, these two capabilities give managers and HR teams something rarely available before: a coherent, chronological account of how an employee's situation and trajectory have evolved. For organizations looking to move beyond annual reviews, [Break The Annual Review Cycle: The Executive's Guide To Creating A Culture Of Continuous Employee Development](/resources/break-the-annual-review-cycle) covers the structural shift in detail. ## Training completion as a compliance risk — and a development record Compliance training completion records are among the top documentation gaps cited in OSHA and regulatory audit findings, with missing records frequently cited as a contributing factor in incident investigations. Organizations spend significant effort designing and delivering required training — safety certifications, compliance modules, harassment prevention, equipment operation — and then have surprisingly little ability to prove who completed what, when, and with what result. The problem is structural: most organizations manage training delivery in a third-party lms learning system that doesn't sync reliably with the HR system of record. When an auditor asks for completion records, someone runs a manual export, reformats it, and hopes the data is current. When an incident triggers investigation, the first question — whether the employee had the required training — takes hours to answer. An LMS built directly into the employee experience platform closes this gap. Administrators can build structured courses with prerequisites and quizzes, set compliance rules with deadlines, and configure automatic certificate issuance on completion. The record of who completed what lives in the same platform as the employee's profile, schedule, and performance history — not in a separate system that requires a sync job to stay current. Organizations that have digitized onboarding and training delivery have reported up to 50% faster new-hire time-to-productivity compared to manual, paper-based processes, according to Beekeeper's research on frontline workforce onboarding. For frontline-heavy organizations — manufacturing, logistics, retail, healthcare — mobile accessibility is the critical variable. According to Emergence Capital, 80% of the global workforce is deskless. Any compliance training infrastructure that requires a desktop login has structural coverage gaps before deployment begins. Persona-based targeting — routing training, policies, and compliance content by role, region, and language — is increasingly positioned as a governance requirement, not just a personalization feature. The audit-readiness frame, while important, is only half the value. A documented record of training completion that lives alongside goal tracking and audit history makes learning a strategic input to workforce planning rather than a compliance checkbox. When managers can see an employee's completed certifications alongside their coaching history and goal progress, development conversations become grounded in evidence rather than general impressions. For a deeper look at embedding learning into daily work, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ## Procurement approval without budget context Return to the opening scenario: a compliance team asking whether equipment procurement went through proper budget approval is asking because the answer is often unclear. The approval chain and the budget record lived in different places and were never formally connected. Someone approved the purchase. Whether the budget was checked at that moment is unverifiable. This is a design problem, not a discipline problem. Procurement budgets exist in finance systems. Purchase requests get submitted through email or a separate tool. The two sides don't talk to each other until after a commitment has already been made. Closing this loop requires bringing budget visibility into the point of submission. When a purchase requisition form shows live budget availability by cost center before the employee submits, the check happens as a natural step in the process rather than as a retroactive review. When budget managers can filter by cost center and export tagged data, the audit trail builds during normal operations rather than getting assembled afterward. Workflow automation covering HR, IT, and procurement approvals — not just communication — is now a baseline expectation in modern employee experience platforms, with no-code self-service forms replacing manual approval chains. The design principle is the same across all three accountability gaps: the records that matter most should be a byproduct of the work itself, not a separate administrative task that competes with it. ## How to audit your own organization's exposure The accountability gap is not a binary condition. It closes incrementally as informal processes are replaced by systems that generate records automatically. A practical starting audit: pick the three scenarios most likely to trigger a compliance review or incident investigation in your industry, then ask whether the documentation those scenarios require exists today in a centralized, timestamped, exportable form. For most organizations, that audit surfaces gaps in at least one of these areas: **Performance history.** Coaching conversations that were never recorded, or recorded in a format that doesn't connect to formal review data. The operational test: could a manager reconstruct the coaching narrative for any direct report from the last six months in under ten minutes, pulling from a system rather than memory? **Training completion.** Certificates that exist in a third-party LMS that doesn't sync reliably with HR records. The operational test: could an HR administrator produce completion records for a specific training module, for a specific workforce segment, in under five minutes with a reliable export? **Procurement approvals.** Requests that were approved without a contemporaneous budget check. The operational test: is there a timestamped record of budget availability at the moment of approval for purchases over a material threshold? Each gap has a corresponding sop operations fix — structured meeting records for performance, a centralized lms learning system for training, and cost-center-linked requisition forms for procurement. The critical requirement is that the fix generates the record as a consequence of the normal process, not as an additional step that gets skipped when teams are under pressure. ## What consolidated accountability infrastructure actually changes The return on accountability infrastructure is easier to measure in avoided costs than in direct gains. Regulatory fines avoided when audit documentation is complete. Incident investigation costs reduced when records surface immediately rather than requiring reconstruction. Manager time recovered when performance history is accessible at review time rather than assembled from memory. Per IDC, employees spend 2.5 hours per day searching for information. For HR teams and managers who spend a meaningful portion of that time reconstructing records that should already exist — pulling training completion exports, chasing down approval chains, piecing together an employee's role history — the time savings from consolidated, automatically generated records are direct and measurable. The less quantifiable but equally real return is organizational confidence: the ability to answer a compliance question in minutes rather than days, without pulling people off their regular work to reconstruct a paper trail that should have existed all along. In regulated industries — healthcare, utilities, logistics — that confidence is not a soft benefit. It is a prerequisite for operating at scale. Accountability infrastructure that requires a separate effort to maintain tends not to get maintained. The goal is records that exist before you need them, created as a natural consequence of the work itself. For organizations building or consolidating their [workforce management](/solutions/workforce-management) infrastructure, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading organizations are approaching this shift from reactive documentation to proactive record-keeping across the employee lifecycle. --- # Beyond the Score: Giving Employees a Voice with No-Surprise Performance Reviews **Author:** MangoApps **Published:** 2025-12-19 **Category:** performance-management What if performance reviews held no anxiety and no surprises? This post shows how continuous feedback, visible goals, and shared documentation create psychological safety, fairer evaluations, and a culture where employees know exactly where they stand—and how to grow. # Beyond the Score: Giving Employees a Voice with No-Surprise Performance Reviews Per Gallup, employees who receive regular, meaningful feedback are more than five times more likely to be engaged in their work. That statistic appears in nearly every performance management reform conversation — and is almost universally ignored in how organizations actually structure reviews. The reason is structural, not motivational. Most performance management systems were designed for employees who sit at a desk, receive a corporate email, and have 45 minutes blocked on their calendar for a quarterly one-on-one. Per Emergence Capital, 80% of the global workforce is deskless — warehouse operators, nurses, hotel housekeeping staff, retail associates who cover closing shifts without ever opening a company laptop. For this majority, "continuous feedback" is a phrase without a delivery mechanism. A no-surprise review culture is not primarily a philosophical shift. It is a delivery question: does your [performance management](/solutions/performance-management) infrastructure reach every employee, or only the desk-based segment that already shows up in engagement survey responses? ## Why annual reviews fail by design — not execution Only 14% of employees strongly agree that their organization's performance reviews inspire them to improve, per Gallup. The standard diagnosis focuses on manager quality: managers rely on memory, they exhibit recency bias, they deliver generic feedback that doesn't help anyone grow. Those things are true. But the upstream cause is that annual reviews were designed for a workforce where managers observe employee behavior daily, document it as it happens, and have enough context to give feedback that's specific to the individual. In a distributed, shift-based, or frontline-heavy workforce, that assumption collapses immediately. The hotel general manager responsible for 400 housekeeping staff across multiple properties cannot maintain the observational record that would make an individual performance review feel fair and specific. The district retail manager overseeing 12 store locations cannot be present for enough individual moments to make a year-end assessment credible. When observation is infrequent and documentation is absent, the annual review inherits the full burden of feedback that should have been distributed across the year — and buckles under it. The result, per Gartner HR research, is that 70% of managers believe their review processes are not driving the development they were built to produce. The problem is not willingness. It is that the foundational inputs — continuous observation, real-time documentation, structured frequency — are structurally absent in most frontline and distributed work environments. ## Documentation as the prerequisite for fairness The recency effect is not a character flaw — it is how human memory works under a year's worth of accumulated information. An employee who performed at a high level from January through October and had a difficult November will receive a review that disproportionately weights November. Without a documentation trail, the December conversation is not a performance review. It is a memory reconstruction exercise with all of memory's known distortions built in. Real-time documentation closes that gap before it opens. A manager who captures a note within 24 hours of a client-facing moment in May, or logs an incident as it resolves, is building the evidence base that makes the December review fair, specific, and resistant to recency distortion. Employees who know their managers document moments as they happen — rather than reconstructing a narrative at year-end — experience reviews differently: as a summation of a documented year rather than a judgment rendered from impression. Organizations that implement regular employee feedback see 14.9% lower turnover than those that don't, per Gallup. That retention differential is not explained by the feedback itself — it is explained by what consistent documentation makes possible: reviews that feel earned rather than arbitrary, development conversations grounded in specifics rather than impressions, and an employee experience where good work is more likely to be seen and acknowledged when it happens. For frontline employees, documentation matters even more because managerial visibility is structurally lower. A warehouse team lead who correctly managed a supply chain disruption at 2 AM may go entirely unrecognized unless the documentation system makes capturing that moment frictionless from a mobile device. Recognition that requires a desktop browser, a VPN, and a corporate login is functionally not recognition for the majority of the workforce. ## Goal visibility as engagement architecture Annual goal-setting carries the same structural flaw as annual reviews: it assumes the business environment in December will resemble what was anticipated in January. In most industries, that assumption fails within the first quarter. Goals that don't adjust to operational reality become compliance artifacts — HR boxes to check at year-end rather than orientating commitments that shape daily decisions. Dynamic goals — reviewed in monthly one-on-ones, broken into quarterly milestones, and visible to the team — function as something different. They create the "line of sight" that [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) identifies as the most reliable predictor of sustained engagement: the ability for an employee to connect today's specific task to the department's quarterly target to the organization's annual direction. That connection is not motivational rhetoric — it is operational clarity that reduces the disengagement that comes from work that feels disconnected from outcomes that matter. Goal visibility requires infrastructure. A goal stored in a spreadsheet the employee last opened in January is not a visible goal — it is a historical record. Goals embedded in the same communication hub where teams actually work, with progress indicators visible to both manager and employee, become operational anchors. Per Gallup, 70% of employees say they would work harder if they felt their efforts were better recognized. Recognition requires visibility, and visibility requires infrastructure that persists across the year rather than refreshing at year-end. ## The self-evaluation gap in distributed workforces Self-evaluation is standard in desk-worker performance frameworks — structured time for employees to document their own progress before the manager assessment, surfacing wins and challenges the manager may not have directly observed. It is substantially less common in frontline contexts, not because frontline employees have less to contribute, but because the tools assume a desktop browser, a quiet office environment, and 30 uninterrupted minutes. That assumption excludes the majority of employees from the most important element of a no-surprise review: giving employees the first word. When an employee completes a self-assessment, they stop being a passive recipient of a score and become an active participant in documenting their own year. Quiet wins surface — the extra shift covered to help a colleague, the process improvement that saved the team repeated hours weekly, the peer who was mentored through a difficult onboarding that the manager never directly witnessed. Without a self-evaluation mechanism accessible on mobile, those contributions go undocumented. Peer feedback amplifies what self-evaluation starts. A manager observes results. Peers observe the how: daily reliability under pressure, cross-functional cooperation during operational disruptions, cultural contribution that never appears in output metrics. A structured 360-degree feedback process — completable in five minutes on a personal device without a corporate login — brings those perspectives into the review conversation before the formal meeting. When manager assessment and employee self-assessment are reviewed side-by-side, the calibration conversation changes: it is specific, grounded, and demonstrably less likely to surface as a surprise to either party. Accessibility is not a feature of an equitable feedback system. It is the prerequisite. ## Manager enablement: the gap most continuous feedback initiatives miss Organizations attempting to shift from annual to continuous review models consistently report the same failure mode: managers understand the intent but lack the cadence, the conversational framework, and the habit structure to execute it consistently. Declaring that "feedback is now continuous" without equipping managers with practical tools produces a predictable outcome — more informal check-ins with the same absence of structure that made the annual review ineffective in the first place. Effective continuous feedback requires a repeatable cadence: a monthly one-on-one format with a predictable agenda (goal progress, blockers, one piece of specific behavioral feedback), a quarterly milestone check-in anchored to goal progress, and a real-time documentation habit that takes less than two minutes per captured moment. These do not require exceptional management talent. They require tools designed to support the habit in the conditions where managers actually work. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) identifies manager feedback capability as the single most cited gap in organizations attempting to shift to continuous performance cultures. What that finding actually describes is a tool design gap: when documentation requires logging into a separate HR portal and completing a structured form, the habit never forms. When documentation is embedded in the communication tool the manager already has open during the shift, the friction drops enough that the capture happens. The district manager covering 12 stores who can run a five-minute structured check-in between store visits — on a mobile device, with a templated one-on-one agenda, logging notes in the same hub where she receives shift updates — is functionally different from the same manager told to "schedule quarterly one-on-ones" and given a calendar reminder. Same intent. Dramatically different execution rate. ## What a no-surprise performance culture actually requires The philosophy of continuous, no-surprise performance reviews has been well-articulated for years. The execution gap is almost entirely infrastructural — which means it is a solvable problem if framed correctly. A no-surprise review culture requires five things operating together: **Documentation that happens at the moment, not in retrospect.** A feedback note written within 24 hours of an event is qualitatively different from one reconstructed at year-end. The tool must be available on the device the manager is holding when the moment happens. **Goal visibility embedded in daily work, not filed in HR.** Goals that exist outside the workflow are historical records. Goals visible in the same hub where teams communicate become operational anchors that shape behavior across the year rather than paperwork reviewed once at its end. **Self-evaluation access for every employee, including frontline.** An assessment process that requires a corporate laptop and uninterrupted office time excludes the 80% of the workforce operating in shifts or in the field. The mechanism must work on a personal device during a break. **A calibration layer that surfaces misalignment before the annual meeting.** When manager assessment and employee self-assessment live in the same system, the misalignment that produces review-room surprise becomes visible weeks earlier — and addressable before it becomes a confrontation. **A structured cadence that managers can actually maintain.** Monthly one-on-ones with templated agendas, real-time documentation built into existing workflows, and quarterly milestone check-ins tied to goal progress convert "continuous feedback" from an aspiration into a repeatable system. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents a consistent pattern in organizations that have extended continuous feedback to their frontline workforces: the same infrastructure that improved operational communication — a mobile-first platform accessible without corporate credentials — also improved the quality and perceived fairness of performance conversations. Both problems share the same root: feedback that doesn't reach employees where and when they work. No-surprise reviews are achievable. The organizations that have eliminated review-room dread share one characteristic: they built the delivery infrastructure first, and let the culture change follow. --- # Stop Re-Typing Success: Why Automated Performance Data is the Secret to Fair Pay **Author:** MangoApps **Published:** 2025-12-19 **Category:** performance-management Automating the link between everyday work data and compensation creates a fairer, more transparent, and truly merit-based system—turning performance reviews from a black box into a trust-building advantage. # Stop Re-Typing Success: Why Automated Performance Data is the Secret to Fair Pay We track everything in real time. Sales pipelines update in Salesforce. Operational efficiency surfaces in dashboards. Project completion rates flow through work management platforms. Then annual review season arrives, and we abandon those live systems to reconstruct a year's worth of performance from memory and static HR forms. A single manual HR data entry costs $4.78, according to EY benchmarking research. In a 1,000-person company where each employee has five tracked goals reviewed twice a year, that's more than $47,000 spent annually on the act of transcription — before accounting for errors, delays, or the quiet distortions that happen when a manager edits a number to avoid a difficult conversation. The financial waste is significant. The accuracy risk is worse. Automating the connection between where work happens and where work is rewarded — through a [modern HCM platform](/solutions/modern-hcm) that integrates directly with operational systems — is not a technology preference. It is a structural requirement for any organization that wants compensation decisions to reflect actual performance. ## The gap between data and decisions The same dashboards that guide daily operations go dark the moment performance evaluation begins. That disconnect is not an accident — it reflects how performance management systems were originally designed: as separate administrative processes rather than as outputs of the operational systems employees work in every day. When managers manually reconstruct performance from memory and spreadsheets, the record reflects recollection rather than reality. A manager who worked closely with an employee through Q4 will recall that period more vividly than quieter months earlier in the year. A manager whose team grew mid-year may not have consistent visibility into contributions made before she joined. The result is performance data accurate only to the extent of what a manager happened to notice. Integration at the source closes this gap. When performance data flows automatically from operational tools into the evaluation framework, review conversations start from a complete, auditable record rather than a reconstructed one. ## How cognitive bias distorts manual evaluation Even managers who work from careful notes introduce systematic distortion into manual reviews. Three cognitive biases appear consistently in performance evaluation research. **Affinity bias** causes evaluators to favor employees who share their communication style, background, or interests. The employee who mirrors the manager's working approach scores higher — not because their output was greater, but because the interpersonal experience of managing them was easier. This bias operates below the level of conscious intent, which makes it resistant to correction through good-faith effort alone. **Proximity bias** compounds this problem in distributed and frontline environments. Visibility reads as productivity. Employees who are physically present — or who appear frequently in digital channels — are perceived as more engaged than colleagues working different shifts or from remote locations. Frontline workers make up 80% of the global workforce, according to Emergence Capital, and they are particularly exposed to this pattern. A warehouse associate, a retail floor employee, or a healthcare aide may produce consistent results that a manager in a central office simply doesn't have full visibility into. **Recency bias** distorts the time dimension. Annual reviews that rely on manual recall are, in practice, evaluating the last 60-90 days. A performer who delivered steady results for ten months but had one visible slip in Q4 will often be rated lower than someone who had a strong finish after an unremarkable year. That evaluation doesn't reflect full-year contribution — it reflects the cognitive shortcuts human memory applies under time pressure. Automated data capture addresses all three by anchoring the review to a complete record. The January data point carries the same weight as the December one. The quiet remote contributor's output is as visible as the extrovert who dominates every meeting. The manager's job shifts from reconstructing what happened to interpreting a record that was already captured. ## Rewards and recognition beyond the annual cycle Annual compensation decisions are one output of a performance system. But the research on retention points to a broader pattern: employees leave when they don't feel their contributions are seen consistently — not just once a year at review time. The [Gallup 2026 State of the Global Workplace report](/articles/gallup-2026-state-of-the-global-workplace) identifies recognition as one of the highest-leverage variables in employee engagement, and engagement as a direct predictor of retention and operational performance. Recognition programs built on manager discretion have the same structural flaw as manual compensation processes: they reward what managers notice, not what employees deliver. How symplr [built its rewards and recognition program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program) illustrates what changes when recognition connects to real-time performance data. When managers can see a feed of goal completions, peer acknowledgments, and productivity signals, recognition becomes specific and timely rather than general and retrospective. Generic praise — "great job this quarter" — lands differently than recognition tied to a concrete outcome. The frequency and specificity of recognition, not just its existence, is what moves engagement and retention numbers. Automated performance data makes that frequency possible. Without it, recognition is constrained by what a manager happened to notice and remember on the day they had time to act on it. ## The implementation question: how organizations make the transition The case for automation is straightforward. The harder question is how organizations move from manual spreadsheets to an integrated performance system without destabilizing an already complex review cycle. The transition typically moves through three stages. **Integration first.** The starting point is connecting existing operational tools — HRIS, productivity platforms, project management systems, scheduling software — to a central performance layer. The goal isn't to replace the tools managers already use; it's to eliminate the manual extraction step at review time. When employee roles, goal structures, and permissions sync automatically from the HRIS, the review process begins from a complete data set rather than a blank form. When project completion rates and productivity metrics flow in without manual entry, the record reflects what actually happened. **Calibration second.** Raw data without context can introduce distortions of its own. A sales representative who joined in Q3 will have lower full-year numbers than someone who started in January — that context needs to be incorporated into the evaluation framework. Automated systems that apply calibration logic, adjusting for tenure, role complexity, team composition, and position in the pay range, convert raw metrics into defensible performance scores. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how organizations are building calibration frameworks that account for these variables without adding manual steps to the review cycle. **Transparency third.** The final stage is giving employees visibility into their own data before the review conversation happens. When an employee can see their goal completion trajectory, recognition history, and progress against defined performance criteria in real time, the annual review shifts from a verdict to a confirmation. The employee knows roughly where they stand. The conversation becomes substantive rather than revelatory — which is where the real development work happens. This sequence matters because attempting all three simultaneously creates organizational overload. Integration can be implemented without changing how managers conduct reviews. Calibration follows once data quality is confirmed. Transparency comes last, when the underlying data is reliable enough to share confidently. ## The audit trail compensation decisions require In regulated environments and organizations with complex workforce structures, compensation decisions need to be documentable — not just fair, but traceable. An HR leader explaining why two employees in similar roles received different merit increases needs a clear record: what data informed the decision, how it was calibrated, and what the outcome was. Manual processes cannot produce this record reliably. A change to a spreadsheet doesn't log who made the edit or why. A manager's recollection of a rating decision isn't auditable. When compensation outcomes are challenged — through internal appeals, employment claims, or regulatory reviews — the absence of a clear data trail creates exposure that extends well beyond the immediate dispute. Automated performance systems generate this audit trail as a byproduct of normal operation. Every data point carries a source and a timestamp. The connection between a performance score and a compensation outcome is traceable and defensible. This is a compliance benefit, but it also signals to employees that the process was designed to produce fair outcomes rather than simply asserting them. ## What changes when the data is right The effects of accurate, automated performance data reach further than most organizations anticipate when they begin the process. Manager time reallocates. When managers are no longer spending hours manually gathering and entering performance data before review season, that time becomes available for conversations that actually develop people — goal-setting discussions, real-time feedback, career planning. The administrative burden of the review cycle compresses significantly. Compensation equity improves across teams. When the same data inputs are applied consistently regardless of which manager is running the review, the variation in ratings driven by differences in manager strictness — rather than differences in actual performance — decreases. Employees in teams with historically conservative managers are no longer systematically disadvantaged at the calibration step. Recognition frequency increases. When managers have a continuous view of performance data rather than a once-a-year snapshot, informal recognition can happen closer to the moment that warranted it. That proximity is what makes recognition feel genuine rather than procedural. ## The standard compensation decisions should meet Performance data is most valuable when it makes a clear, documentable connection between what an employee did and what they received. That connection is what employees mean when they describe a compensation process as fair — not that everyone received the same outcome, but that outcomes were derived from the same inputs and the same logic, applied consistently. Manual processes create a ceiling on how fair compensation can be. When data accuracy depends on a manager's recollection, and allocation logic lives in a spreadsheet no one can fully audit, that ceiling is low. Automated systems raise it — not by removing judgment from the process, but by ensuring judgment operates on accurate information and produces a record that employees and organizations can stand behind. The question worth asking is not whether to automate performance data, but how long the current process can sustain the costs of not doing it — in dollars, in manager time, in employee trust, and in the quiet departures that follow when high performers conclude their effort isn't being seen. --- # How to Build a Culture of Continuous Performance Management **Author:** MangoApps **Published:** 2025-12-19 **Category:** performance-management Ditch the dreaded annual review and discover how continuous, real-time feedback and goal setting can transform performance management from a demoralizing sprint into a motivating, growth-driven culture that boosts engagement, agility, and retention. The performance review. For many organizations, it’s a high-stakes, once-a-year event that triggers a massive administrative scramble, culminating in a meeting that leaves both managers and employees feeling drained and even demoralized.This yearly sprint is not just inefficient; it can actively sabotage growth and engagement. Better forms or earlier deadlines are not the solution to this problem. What you need is a fundamental cultural shift to Continuous Performance Management.The Problem: The Annual Performance Review SprintFor most companies, the annual review is the primary performance dialogue. A single, high-stakes meeting attempts to summarize 12 months of work, often becoming a classic example of rear-view mirror management.The structure itself is flawed, leading to the two most common organizational pain points:Recency Bias: Managers, forced to document an entire year’s worth of work, naturally focus disproportionately on the most recent 6-8 weeks. An employee’s solid performance from March is overshadowed by a minor mistake in November, leading to an unfair and incomplete picture.Goal Disconnect: Goals set with enthusiasm in January are often forgotten or ignored by October because there’s no official, frequent mechanism to track, adjust, or revisit them.The Cost of the Annual CrunchThe annual performance review system extracts a heavy toll, both administratively and psychologically.The Manager’s Administrative BurdenThe process forces a massive administrative effort concentrated in the last quarter, which is a period often already crowded with year-end deadlines. Managers must recall and document performance for 10-20+ employees, turning the task into a demanding "part-time job” that comes alongside all their other responsibilities.This leads to rushed, poorly written reviews that fail to provide real value, as well as cascading delays to those managers’ other work.The Employee’s Poor ExperienceFor the employee, the process is equally frustrating. The review often feels like a trial, not a conversation about growth. They feel frustrated when critical negative feedback surfaces only during the year-end meeting when it should have been delivered, and addressed, months earlier. This focus on past mistakes, instead of future development, can breed disengagement.Furthermore, because compensation decisions ride on this one meeting, employees can face a lot of anxiety leading up to it, especially if their manager hasn’t done a good job of coaching them throughout the year and they have no inkling of what to expect.Introducing Continuous Performance ManagementContinuous Performance Management is the paradigm shift from performance review as a single event to performance as an ongoing process. It fundamentally reframes the manager’s role from evaluator to coach and development consultant, focusing on future growth rather than past failures.Defining the Continuous Feedback CycleThe core of Continuous Performance Management is built on three pillars that form a continuous cycle:Setting & Resetting Objectives (Quarterly/Rolling): Goals are dynamic. Instead of fixed annual goals, Continuous Performance Management utilizes shorter, more agile goals, like OKRs (Objectives and Key Results) that are reviewed and adjusted quarterly or even monthly to match organizational needs.Frequent Check-ins (Weekly/Bi-weekly): These are brief, informal conversations focused on tactical progress, obstacles, and immediate learning opportunities.Real-Time Coaching & Feedback (In the Moment): Managers and peers deliver feedback immediately following a project milestone or significant event, maximizing its relevance and impact.The Vision: Feedback as Fuel and DevelopmentUnder Continuous Performance Management, feedback is treated as actionable data—fuel for development, not a weapon for critique. The focus is on specific, observable behaviors and outcomes. For instance, instead of saying, "You need to be better at communication," a manager would say, "When you presented the data summary, clarifying the client's key takeaway before moving to the technical details would have made the message clearer." This immediacy has a powerful effect on morale:Statistic: Employees are 3.6x more likely to be highly motivated when they receive daily feedback versus annual reviews (Gallup).Benefits Beyond ComplianceThe advantages of Continuous Performance Management extend far beyond reducing year-end administrative overhead:Organizational Agility: Frequent goal setting ensures team priorities are constantly aligned with market changes and strategic shifts, making the organization more responsive.Talent Retention: Employees feel their development is prioritized. When managers act as coaches, trust deepens, which is a key factor in retaining top performers.Data Accuracy: Documentation of performance is spread out, resulting in a richer, more accurate record of an employee's contributions over the full year, eliminating reliance on flawed memory.Building the Foundation for Continuous Performance Management: Shifting to an Employee-Driven ProcessSuccessful performance management is not mandated from the top down; it’s driven by the employees who seize ownership of their development path. This cultural pivot is essential to making the process feel like investment, not compliance.Standardize the Check-In, Empower the EmployeeThe manager should no longer be solely responsible for initiating and leading performance discussions. The employee should own the 1:1 meeting agenda and documentation. This transforms the manager into a resource and coach, rather than an administrator. We recommend a structured template for bi-weekly or monthly meetings that the employee prepares:Look Back (Accountability): Key accomplishments, challenges, and goals achieved/missed. This documentation becomes the employee's living portfolio.Right Now (Priorities & Support): Current blockers, resource needs, and immediate priorities. This is where the manager offers tactical support.Look Ahead (Growth & Development): Skills to develop, projects to pursue, and specific feedback requests. The employee specifically asks: "What is one thing I could start, stop, or continue doing?"Implement Proactive, On-Demand Feedback Tools Move beyond the manager/employee dynamic by building a culture where feedback is a pull, not just a push. Employees should be empowered to solicit feedback from peers, stakeholders, and other managers immediately after a project wraps up. This allows the employee to gather diverse perspectives while the event is fresh, countering recency bias and providing a comprehensive performance record. Furthermore, self-assessment should be a continuous task where employees log key achievements, obstacles, and learnings as they happen, shifting the burden of documentation from the manager alone to being shared by both parties.Training Managers to Be Developmental CoachesThe biggest obstacle to continuous performance management is often the manager. They must master the art of developmental coaching. This requires training that covers:Active Listening: Managers must learn to listen to understand and diagnose issues, rather than listening to reply.The Power of Open-Ended Questions: Shifting from "Did you finish the report?" to "What was the biggest learning from finishing that report, and how will you apply it next time?"Behavioral Feedback Models: Utilizing structured models (like SBI: Situation, Behavior, Impact) to ensure feedback is objective, specific, and tied directly to business outcomes, preventing vague or subjective critique.Managing Discomfort: Training managers on how to deliver difficult feedback constructively and with empathy, ensuring the conversation remains focused on development and performance improvement rather than personal critique.Aligning Growth with OpportunityIt is crucial to ensure that employees see a visible return on their continuous development efforts and are able to tie a clear line from their performance to growth potential and how they are compensated.Mitigating the Development TreadmillSeparating development from compensation can lead to a feeling of disconnect. Employees may feel development goals are an extra, unrewarded workload if they don't lead anywhere. The feeling that one is working harder on development but not seeing career progress is a major driver of disengagement and voluntary turnover. This is why the structure of your performance appraisal system must explicitly link growth to opportunity.Defining the Visible "Line of Sight"Managers must draw a direct line between continuous performance goals and the employee’s career trajectory. The continuous documentation of skill mastery becomes the evidence base for promotion or reward. For example, an employee should understand that their focused work on a specific skill in Q2 is the required step for a promotion review in Q4.Here are some concrete examples of how this can look:Compensation Link: "Mastering the new software module, which we’ve been discussing in our check-ins, is a required, measurable step for achieving the Senior Analyst pay band review in Q3 because that skill directly impacts our revenue targets."Promotion Link: "The leadership training sessions and project delegation you've been practicing are specifically designed to build the competencies listed on the Team Lead job description. We will use your continuous check-in notes as evidence for promotion readiness."Visibility & Recognition Link: "Your success in consistently applying the new client communication model we discussed has earned you the opportunity to lead the upcoming cross-functional task force and present our final recommendation to the Executive Team."Implementing the Quarterly Career Check-InTo solidify this link, managers should hold a separate, formalized discussion (e.g., quarterly) explicitly dedicated to career progression. This discussion is distinct from the frequent, tactical performance check-ins. The goal is not to deliver feedback, but to:Assess Progress: Review the documented evidence of continuous performance against established career milestones.Recalibrate Path: Adjust the employee’s long-term development goals based on current performance and future organizational needs.Confirm Timeline: Provide a transparent, honest assessment of the timeline for promotion or compensation review, ensuring the continuous performance work is directly feeding into the employee's aspirational future.MangoApps Solution: The Drip-Feed Approach to Performance ManagementContinuous Performance Management is manageable only when supported by the right technology. MangoApps EPMS facilitates this cultural shift by automating the administrative structure, replacing the annual crunch with a Drip-Feed Approach.Spreading the Workload: MangoApps takes the pressure off supervisors handling many direct reports by making the administrative tasks small and manageable throughout the year.Structured Check-Ins: The platform enables mandatory, smaller check-ins (e.g., quarterly reviews or monthly progress reports). These structured inputs auto-populate the final year-end document, ensuring the final review is a summary, not a research project.Automated Triggers and Reminders: The system replaces the chaotic, mass "everyone do your reviews now" cycle. Automated reminders for specific events (e.g., "Project X is complete - trigger a manager/employee feedback request") ensure feedback is delivered timely and contextually, without relying solely on managers remembering to initiate.Stop the Sprint, Start the MarathonThe annual performance review sprint is an outdated administrative relic that kills motivation and delays valuable organizational data.By shifting to Continuous Performance Management, powered by smart automation tools like MangoApps, organizations can transform their culture. They stop judging past performance and start coaching future potential, leading to higher engagement, better development, and superior results.Ready to turn the annual sprint into a continuous, rewarding marathon? Contact us to see how MangoApps can automate your shift to Continuous Performance Management. --- # HR Compliance That Runs Every Day, Not Just at Audit Time **Author:** MangoApps Team **Published:** 2025-12-14 **Category:** news-and-updates Every HR leader knows the feeling. An auditor sends a request. # HR Compliance That Runs Every Day, Not Just at Audit Time Every HR leader knows the feeling. An auditor sends a request. A regulator sets a deadline. A lawsuit requires documentation that should have been easy to produce. And suddenly the team drops everything — pulling data from three systems, reconstructing timelines from email threads, building spreadsheets from scratch — to assemble a picture that should have already existed. Compliance work has always been treated as episodic: something you prepare for, then survive, then recover from. The rest of the time, it lives in the background — underfunded, underdocumented, and waiting to surface at the worst possible moment. This week's releases in MangoApps Workforce suggest a different approach: make compliance part of daily operations, not a separate project you run when something goes wrong. Five distinct features shipped this week. They touch recruiting, compensation, performance management, training, and leave. But the thread connecting all of them is the same: the documentation you need should already exist before anyone asks for it. --- ## The Documentation You Need Is Already There Ask an HR business partner what she does the week before an EEO filing, and she will describe a familiar ritual: extract headcount data from the HRIS, cross-reference with payroll, manually add government job function classifications for each employee, identify the gaps, reconcile the inconsistencies, and then spend the last two days praying the numbers add up. For state and local government employers, this is the reality of EEO-4 compliance — an annual report that touches every employee record and typically requires significant manual assembly. The new EEO-4 reporting module eliminates that assembly. Government job function classifications live in the platform alongside employee records, with real-time HRIS and payroll data sync ensuring the records are accurate year-round — not just in the weeks before a filing deadline, which is what makes them defensible in an audit. A bulk update workflow handles large workforces. A dedicated gap view surfaces employees with missing classifications before submission — not after. The report generates directly from the system, without an export-and-rebuild cycle. This is not a subtle improvement. Organizations that file EEO-4 reports — county agencies, public utilities, transit authorities — typically manage this through a combination of exports and spreadsheets because their HR systems were never built around government compliance requirements. Having it native means the data is accurate year-round, not just in the weeks before the filing deadline. The same logic applies to Training Records Management, which shipped in Training Connect this week. As part of the broader learning and development infrastructure in MangoApps, this module lets L&D administrators filter certification records by employee, category, and completion status — and export them audit-ready without manual reconstruction, a capability that competitors position as a core differentiator for regulated industries. When an auditor asks for proof that a department's employees completed required safety training, the answer is a filter and an export, not a two-week reconstruction project. Bulk sync keeps records current with the connected LMS learning system automatically, so the records you see are the records that are actually true. For organizations in regulated industries, that distinction between "what the system shows" and "what is actually true" is where audit exposure lives. Per the Forrester Report, a 20,000-employee organization deploying integrated workforce operations tooling realized $2.0M in increased frontline worker productivity over three years — in part because compliance overhead stopped consuming the time that should have gone to operations. When compliance checklist items or certification gaps are surfaced, the platform can automatically trigger corrective action tasks and assignments — closing the loop between documentation and remediation without requiring a separate workflow or manual follow-up. That automated follow-through is what separates compliance infrastructure from compliance reporting. --- ## Compensation Compliance Has a Data Problem Pay equity litigation has increased steadily over the past several years, and the regulatory environment is catching up. Pay transparency disclosure requirements now exist in a growing number of U.S. states and municipalities — making real-time comp-ratio visibility a legal risk management tool, not just an HR analytics feature. The problem for most HR teams is not that they are paying people unfairly — it is that they do not have the data infrastructure to know whether they are or not. The Pay Grade Management and Comp-Ratio Analytics release addresses this directly. Compensation managers can now define pay grade bands, assign employees to grades, and see comp-ratios — the ratio of an employee's actual pay to the midpoint of their grade — calculated automatically across the organization. Both individual profiles and aggregate analytics views surface this data. This matters most when you need to explain your compensation decisions, not just make them. A compensation manager preparing for a merit cycle can now see exactly which employees fall below 80% comp-ratio before the cycle opens, flag them for attention, and build a documented rationale for adjustments. When a regulator or plaintiff attorney asks why a particular group of employees was paid below midpoint, that documentation already exists. Alongside this, Reward Letters now generate at scale from the merit matrix — bulk-produced as PDFs, sent to employees automatically, and tracked for acknowledgment. The acknowledgment trail is the part that matters legally. An employee claiming they never received a compensation notice is a real exposure for organizations without delivery records. Automated reminders to employees who have not yet acknowledged close that gap without manual follow-up. --- ## Compliance-Driven Hiring Is a Different Kind of Problem Most hiring compliance conversations focus on documentation — did you record the right things, at the right stages, for the right reasons. But for certain organizations, compliance starts earlier: in how the hiring funnel itself is structured, who is eligible, in what order candidates are evaluated, and whether the process follows required sequencing before an offer is made. Government contractors with priority placement programs, public sector agencies with civil service rules, and unionized organizations with contractual posting requirements all face this. For a deeper look at how software requirements differ in these environments, see [Managing a Unionized Workforce Is Different. Your Software Should B...](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too). The Priority Hiring Funnels and Applicant Pools release is built specifically for this environment. Eligibility criteria and ranking rules can be configured directly into the funnel. Applicant pools group and manage candidate sets for specific programs. The funnel enforces required evaluation steps before moving forward — not as a post-hoc audit, but as a structural constraint on the process itself. The distinction is important. When compliance rules are enforced in the workflow rather than verified afterward, violations become structurally difficult rather than just policy-discouraged. A recruiter cannot inadvertently skip a required evaluation step if the system will not proceed without it. Disciplinary Actions in EPMS operates on the same principle. Disciplinary records — verbal warnings, written notices, formal escalations — have always had legal weight, but most organizations manage them in a combination of email threads, shared drives, and HR notes that are difficult to retrieve and easy to lose. The new module gives each action a severity classification, an escalation workflow, and an automatic expiration date. The records are complete, consistent, and retrievable. And because disciplinary history feeds directly into flight risk analytics, the data is working continuously — not just when someone pulls a file. --- ## The Shift That Matters There is a version of compliance tooling that only helps at the end: better export formats, cleaner report templates, faster ways to assemble the spreadsheet you were going to build anyway. That is not what these releases represent. What they represent is compliance infrastructure that runs during normal HR operations — classification data that is current because it lives in the same system as employee records, pay equity analytics that update with every payroll cycle, hiring funnels that enforce regulatory sequencing before the first offer goes out, disciplinary records that accumulate automatically with proper metadata, training certifications that sync without manual intervention. Per the Forrester Report, organizations of this scale have realized $0.7M in onboarding efficiency gains and $0.3M in IT consolidation savings over three years — outcomes that depend on the same data infrastructure that makes compliance defensible. The practical effect is that when something external forces your hand — an audit request, a filing deadline, a legal inquiry — the data is already there. The work of compliance shifts from reactive reconstruction to continuous maintenance, and continuous maintenance is something that HR teams are already doing. It just happens to produce useful output when you need it. For organizations managing large workforces across complex regulatory environments, that shift is the difference between managing compliance and surviving it. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading organizations are embedding compliance into daily workforce operations — rather than treating it as a separate annual project. --- ## Common Implementation Questions The five features described above address real compliance gaps, but the practical questions that follow a product announcement are often just as important as the capabilities themselves. Here are the ones we hear most often. **How long does it take to set up EEO-4 reporting or Training Records Management?** For organizations already running employee records in MangoApps, EEO-4 classification setup is primarily a data mapping exercise — assigning government job function codes to existing employee records, either individually or via bulk update. Most teams complete initial configuration in days, not weeks. Training Records Management setup depends on which LMS learning system you are connecting; bulk sync is designed to pull existing certification data on first run, so you are not starting from zero. The gap view surfaces missing records immediately after the first sync, which means audit readiness is visible from day one rather than after a manual audit of the audit. **Can these features integrate with our existing HRIS or payroll system?** The compliance features described here are designed to work within MangoApps' broader [workforce management](/solutions/workforce-management) platform, which connects to HRIS and payroll data. The comp-ratio analytics, for example, calculate against actual pay data — which means the integration with your payroll source of record is what keeps those figures current. Organizations evaluating how this fits their existing stack will find the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) useful for understanding how integrated platforms compare to point-solution approaches on total compliance overhead. **What if we are in a regulated industry with specific documentation requirements?** The features described here were designed with regulated environments in mind — public sector EEO requirements, pay equity audit laws, priority hiring rules, and LMS-connected certification tracking for safety-critical roles. Organizations in healthcare, utilities, and government contracting have the most direct use cases. For context on how similar organizations have approached workforce compliance infrastructure, the [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study) case study covers a large utility's approach to connecting compliance and operations data across a distributed workforce. Teams focused on learning and development compliance specifically may also find [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) useful for framing how training records fit into a broader compliance posture. --- # What is an AI-Powered Intranet? **Author:** MangoApps **Published:** 2025-12-11 **Category:** intranet The intranet has evolved from a static destination into an active engine for productivity. Discover how an AI-Powered Intranet goes beyond simple news feeds to generate content, automate workflows, and answer employee questions instantly. Learn how this shift from passive information to active assistance is helping organizations reduce friction, improve engagement, and retain their best talent. For decades, the intranet has been a destination—a place employees go to find news, look up policies, or download forms. While the technology has improved from clunky, IT-managed portals to slick, mobile-friendly apps, the fundamental model has remained the same: humans create content, organize it, and hope other humans can find it.That model is now shifting. We have entered the era of the AI-Powered Intranet.An AI-Powered Intranet is not simply a modern intranet with a chatbot attached. It is a fundamental reimagining of the employee experience where the platform itself actively helps work get done. Instead of just hosting pages, it generates content, answers questions with precision, and automates routine workflows. It transforms the intranet from a passive container of information into an active engine for productivity and retention.The Evolution of the IntranetTo understand why this shift is so significant, it helps to look at how the technology has matured over the last thirty years. The intranet has moved through three distinct eras, each defined by the limitations and opportunities of its time.1. The Traditional Intranet Era (1995–2010)In the early days, intranets were little more than internal websites hosted on corporate servers. They were built with hand-coded HTML, strictly controlled by IT departments, and accessible only from a desktop computer behind the office firewall.Primary Goal: Centralize static resources (like PDF handbooks).User Experience: Rigid, hard to navigate, and rarely updated.Adoption: Often dipped below 30% monthly usage.2. The Modern Intranet Era (2010–2024)The rise of mobile devices and social media forced a change. "Modern" intranets introduced user-friendly Content Management Systems (CMS) that allowed HR and Internal Comms teams to publish news without coding. They added social features like likes and comments, personalized news feeds, and mobile apps to reach workers outside the office.Primary Goal: Drive engagement and culture.User Experience: Social, mobile-responsive, and easier to publish.Limitation: It still relied entirely on manual effort to create, update, and tag every piece of content. If an admin didn’t post it, it didn’t exist.3. The AI-Powered Intranet Era (2024–Present)Today, we are in the third wave. An AI-Powered Intranet uses generative AI and a unified data layer to remove the manual bottlenecks of the past. It doesn't just display information; it understands it.Primary Goal: Solve problems and automate work.User Experience: Conversational, predictive, and personalized.Key Shift: The system moves from a "container" to a "co-creator" and "guide."Modern Intranet vs. AI-Powered Intranet: What’s the Difference?The distinction between a modern intranet and an AI-powered one lies in active vs. passive assistance. A modern intranet waits for you to browse; an AI-powered intranet acts on your behalf.Why Now? The Role of the Unified Data LayerWhy wasn't this possible before? The challenge has always been data silos. In most organizations, policies live in SharePoint, payroll data in ADP, and training in a separate LMS. An AI cannot give a complete answer if it can only "see" one of these systems.The MangoApps approach is built on a unified employee data layer. By connecting Intranet, Modern HCM, and Workforce Management into a single platform, our Mango Employee AI has full context. It knows who the employee is, where they work, and what permissions they have.This allows for true Assistants and Agents that can do real work:Search Assistants: Scan the entire knowledge base to answer "What is our remote work policy?"Ops Agents: Look up a shift schedule and facilitate a shift swap for a frontline worker.Content Assistants: Help internal comms teams turn a rough bulleted list into a polished, localized newsletter in minutes.The Impact on Retention and EfficiencyThe shift to an AI-Powered Intranet is not just a technological upgrade; it is a business imperative. In a time where organizations face turnover rates of 41% (and up to 80% in frontline industries), reducing friction is essential.When employees can find answers instantly, they feel supported. When frontline workers can access the same tools as headquarters staff via a mobile-first superapp, they feel included. And when leaders have real-time visibility into sentiment and engagement, they can act before people leave.Research shows that companies with excellent internal communication can see a 40% boost in employee engagement. And, workplaces that are highly engaged experience 78% less absenteeism, 14% higher productivity, and can result in a 23% increase in productivity. The future of the intranet isn't just about reading news—it's about getting things done.Ready to see the difference? Learn more about how MangoApps is defining the era of the AI-Powered Intranet.Read Customer Case StudiesExplore Mango AIRequest a DemoFrequently Asked Questions (FAQ) About MangoApps AI-Powered IntranetWhat is the difference between a chatbot and an AI-Powered Intranet?A chatbot is typically a single feature overlaid on a website to answer basic questions. An AI-Powered Intranet is a holistic platform where intelligence is woven into the entire experience. It doesn't just answer questions; it proactively suggests content, generates summaries, translates communications, and automates complex workflows across different departments. While a chatbot reacts, an AI-Powered Intranet anticipates and assists.Is my company data used to train public AI models?No. Security and data sovereignty are foundational to the MangoApps platform. Your internal data—policies, employee records, and private communications—remains isolated within your environment. It is used solely to provide context for your specific AI Assistants and is never used to train public Large Language Models (LLMs) like ChatGPT or Gemini. We adhere to enterprise-grade security standards, including SOC 2, ISO 27001, and HITRUST certification.How does an AI-Powered Intranet help with employee retention?Employee burnout and turnover are often driven by friction—the daily struggle to find information, complete simple tasks, or get help. An AI-Powered Intranet removes this friction by giving employees instant answers and automating administrative work. Furthermore, it gives leadership real-time visibility into sentiment and engagement, allowing them to identify at-risk teams and intervene before turnover happens. When employees feel supported and heard, they are more likely to stay.Does this replace our existing systems like Workday or Salesforce?It does not have to. MangoApps is designed to unify your tech stack, not necessarily replace it. Through our unified data layer and integrations, the AI-Powered Intranet connects to systems like Workday, Salesforce, and ServiceNow. It acts as a "single pane of glass," allowing employees to access data and trigger workflows from those systems without constantly switching tabs or logging in and out.What is a "Unified Data Layer," and why does it matter?Most companies have data siloed in different places: HR data in one system, operational manuals in another, and company news in a third. A unified data layer connects these disparate sources into a single index that the AI can understand. This context is critical. It ensures that when an employee asks, "How much PTO do I have?", the AI knows who is asking, checks the correct HRIS record, and delivers a precise, personalized answer rather than a generic policy document.Can AI really generate content that sounds like our brand?Yes. MangoApps’ AI Assistants can be tuned to your organization’s specific tone and style. Internal communications teams use these tools to draft newsletters, summarize town halls, and rewrite technical updates into engaging posts. The AI acts as a co-pilot, handling the heavy lifting of drafting and formatting, while your team maintains final editorial control to ensure everything stays on-brand.How helps with frontline workers who don't have desk access?The AI-Powered Intranet is mobile-first by design. For frontline workers, this levels the playing field. Instead of hunting through binders or waiting for a manager, they can use the mobile app to ask questions via voice or text ("How do I clean this machine?" or "Swap my Tuesday shift") and get instant, accurate answers. Features like instant translation also ensure that language barriers don't prevent frontline teams from staying informed and safe.‍ --- # Workforce Software That Meets Employees Where They Already Are **Author:** MangoApps Team **Published:** 2025-12-07 **Category:** news-and-updates Before a frontline worker's shift starts, they might check their phone four times: once to see when they're supposed to be in, once to look up the PTO policy they half-remember, once to check a... # Workforce Software That Meets Employees Where They Already Are Before a frontline worker's shift starts, they might check their phone four times: once to see when they're supposed to be in, once to look up the PTO policy they half-remember, once to check a paystub from last month, and once more to confirm the schedule hasn't changed. None of those four checks has to involve a separate app or a separate login — but for most workers, each one does. That context-switching is invisible in aggregate data. But it's completely visible to the people doing it. It's the low-level friction that makes software feel like work instead of a tool that removes it. And it accumulates: across a workforce of any size, it shows up as latency, dropped information, and the low-grade frustration that doesn't surface in any report but shapes how people feel about the tools they use every day. This week's releases across MangoApps Workforce address this pattern more directly than any single feature announcement would suggest. --- ## The Schedule Should Live Where People Actually Look For shift workers, the most important piece of work information is when they are supposed to show up. Yet most workforce platforms have kept that information locked inside their own apps — requiring employees to log in, navigate to a schedule view, and manually reconcile what they find with the personal calendar they actually live in. Two releases this week change that relationship. The [Google Calendar integration](https://www.mangoapps.com/key-features/calendar-integration) lets employees connect their Google account once, after which shifts, time-off entries, interviews, and training events appear automatically in a dedicated MangoApps calendar — without any ongoing action required. The [iCal calendar feed subscription](https://www.mangoapps.com/key-features/calendar-integration) does the same for Apple Calendar and Outlook: subscribe once via a signed feed URL, and the schedule stays current as managers make changes. Instead of asking employees to come to the platform to check their schedule, the platform now pushes that information to wherever employees already look. This matters more than it looks on a product spec sheet. For a frontline worker who doesn't think of themselves as a "workforce app user" — they think of themselves as someone who has a job — this is the difference between a schedule they'll actually consult and one they'll forget to check. It also reduces the "I didn't know my schedule changed" conversations that fall on managers to resolve after the fact. The iCal feed extends further still: shift notification emails and interview invites now include .ics attachments for one-click calendar import. The friction of getting work information into the right place is essentially gone. --- ## Questions That Should Answer Themselves The second pattern this week is about information access — specifically, the questions employees ask repeatedly that don't require a human to answer, but almost always reach one anyway. The [HR AI Agent](https://www.mangoapps.com/ai) handles this category directly. It indexes uploaded HR documents and Service Desk articles, then answers employee policy questions from that knowledge base in real time. An employee asking about benefits eligibility at 9 PM gets an answer immediately, drawn from the actual policy documents, with a full audit trail. The same agent routes HR approvals to the right reviewers and logs every interaction for review. The value here isn't just speed — it's availability and consistency. A well-staffed HR team gives good answers during business hours. The HR AI Agent gives those same answers at 9 PM on a Thursday, without anyone being on call. [Paycheck details now available inside Payroll Connect](https://www.mangoapps.com/solutions/employee-data) extend this same logic to compensation. Instead of logging into a separate payroll system to look up an earnings breakdown or year-to-date deductions, employees can now access that information from within the platform they're already using. The full breakdown — earnings, deductions, benefits contributions — is one click away from the Payroll Connect dashboard. This matters for a specific category of HR inquiry that shouldn't require a human handoff at all: "why was my paycheck different this week?" Most of the time, the answer is already in the data. It just wasn't accessible to the person asking. Now it is. --- ## Manager Overhead That Was Never Supposed to Be Manual Managers carry two kinds of work: the judgment-heavy decisions they're paid to make, and the administrative overhead that accumulates around those decisions. This week's leave management releases were specifically about reducing the second kind. The [bulk leave approval action](https://www.mangoapps.com/key-features/manager-experience) lets managers select multiple pending requests and approve or deny them in a single step from the approvals dashboard. This matters most at the moments when it's hardest: the return from a long weekend, the week before a holiday, the seasonal windows when absence volume spikes. Previously, each request required opening, reviewing, and clicking through individually — a process that compounds quickly when the queue is long. The [leave coverage alerts](https://www.mangoapps.com/key-features/manager-experience) add something more important than speed: context. When approving a request would push the team below its coverage threshold, the system blocks the action and surfaces the alert inline. When coverage is at risk but not yet critical, the manager sees a warning before acting. The result is that coverage decisions get made with the relevant information already visible — not after the fact, when a supervisor discovers an understaffed shift. Managers no longer need to maintain a mental model of team capacity or open a separate scheduling view to check headcount before acting on a leave request. That context is now presented automatically, at the moment of decision. Together, bulk approvals and coverage alerts move leave management from a process that requires constant manual attention to one where the platform does the monitoring and surfaces what matters. --- ## The Bigger Picture There's a pattern worth naming across all of this. Each of this week's releases targets a specific moment where employees or managers currently have to go somewhere else — another tab, another login, another system — to get information that should already be in front of them. The shifts that belong in your calendar. The policy answer that should come back instantly. The paycheck details that shouldn't require a separate portal. The coverage status that should be visible in the approval flow itself. These aren't glamorous features. They don't announce themselves. But they're often the difference between software that feels like a capability and software that feels like a chore. The question worth asking about any workforce platform isn't whether it stores the right data — most of them do. It's whether that data surfaces to the right people at the right moment, in the places they already operate. This week's work was about closing that gap, one friction point at a time. --- # Recruiting AI That Works for Candidates, Not Just Recruiters **Author:** MangoApps Team **Published:** 2025-11-30 **Category:** news-and-updates Most of the conversation about AI in HR has been about recruiters. Better screening. # Recruiting AI That Works for Candidates, Not Just Recruiters Most of the conversation about AI in HR has been about recruiters. Better screening. Faster shortlisting. Resume parsing at scale. The candidate — the person actually looking for a job — has been the subject of that AI, not the beneficiary of it. That framing is starting to shift. This week's releases across MangoApps' recruiting platform include AI features that serve candidates directly: answering questions before they ever apply, surfacing roles they might be right for but haven't found, and evaluating fit in ways that help recruiters move faster toward a yes. The result is a set of tools where AI is working on both sides of the hiring equation at the same time — a meaningfully different model from the one-directional screening tools that have defined the category. --- ## The Candidate Who Has a Question Before They Apply There is a specific kind of candidate that every recruiting team wants to attract and consistently fails to reach: the one who is interested but not certain. They found your job listing. They are qualified. But they have a question — about flexibility, about growth, about what the culture is actually like — and there is no easy way to get an answer before going through the effort of applying. In practice, this candidate does one of three things: submits an application despite their uncertainty (and may drop out mid-process), emails the recruiter a question that goes into a pile with dozens of others, or closes the tab and moves on. The [AI Career Assistant on Public Career Portal](https://www.mangoapps.com/directory/app/job-board) addresses this directly. Any visitor to the career portal — including anonymous users who have not yet applied — can ask questions and receive accurate, sourced answers from the organization's own knowledge base. Policies, benefits, role expectations, culture. No recruiter involvement required, no delay, no getting routed to a generic FAQ page. This is not AI generating plausible-sounding answers. The assistant draws from the organization's actual knowledge base, which means the answers reflect what is true about this employer, not a generic description of what companies usually say about themselves. Candidates get real information. Recruiters stop fielding the same twenty questions in rotation. The practical downstream effect matters: candidates who apply after getting good answers are self-selected in a meaningful way. They applied knowing something about the role and the company, which tends to produce applicants who are more engaged and better prepared — and application funnels that convert at a higher rate at each subsequent stage. [Career Portal Branding Customization](https://www.mangoapps.com/apps/job-board) is the supporting infrastructure for that moment. Admins can now set brand colors, upload a logo, configure header and footer text, inject custom CSS, and preview the result before publishing — with built-in WCAG accessibility validation on color contrast. For the candidate visiting the portal for the first time, this is the difference between landing somewhere that feels intentional and landing on a page that looks like a software demo. Before the AI assistant says a word, the visual experience signals whether the organization is worth taking seriously. --- ## The Candidate Who Does Not Know They Should Apply Personalization in job boards has mostly meant better search filters. That is a reasonable thing to build, but it solves a different problem than the one that loses candidates: the good candidate who is not actively looking, or who found the portal but did not see themselves in the roles listed. [Quick Apply and Personalized Job Recommendations](https://www.mangoapps.com/directory/app/job-board) approaches this from two directions. The recommendation engine surfaces roles based on each candidate's profile, skills, and application history — not just what they searched for. A returning candidate who applied for one role six months ago sees recommendations shaped by what the platform knows about them, not just the most recently posted jobs. Quick Apply completes the other half: for candidates who have already uploaded a resume, any application is now a single click. The information is already there. No form to refill, no fields to repeat. The gap between seeing a recommended role and actually applying shrinks from ten minutes to ten seconds. These two features are worth reading together. One surfaces the role; the other removes the effort to act on it. For organizations running high-volume recruiting — multiple openings, returning candidate pools, periodic hiring surges — the combination produces a measurable lift in application rates without any change to sourcing spend. On the communication side, [Two-Way SMS for Candidates](https://www.mangoapps.com/apps/job-board) adds a layer that matters especially for frontline and hourly roles: candidates can respond to SMS notifications with simple commands (YES, NO, STATUS, HELP, STOP) without visiting the portal or opening an email. An interview confirmation that previously required the candidate to click a link and log in now requires a one-word reply to a text message. For roles where the best candidates are also the busiest and least likely to monitor email, that difference closes real gaps. --- ## The Recruiter Who Needs to Move Faster The candidate experience improvements above only matter if the recruiting team can process what comes in. [AI Cultural Fit Score in Candidate Screening](https://www.mangoapps.com/key-features/recruiting-dashboard) expands the AI screening model from resume matching into something more multidimensional. The recruiting agent now evaluates candidates across three dimensions — skills match, experience relevance, and cultural fit — with scores displayed directly in the candidate list and detail views. Each score comes with a breakdown and tooltip explanations, so a hiring manager reviewing a shortlist can understand not just who ranked highly but why. The cultural fit dimension is where this gets genuinely useful. Skills and experience are legible from a resume. Cultural fit has historically required an interview to assess — which means recruiters have been spending interview time on candidates who would not have advanced past a cultural screening if one had been available earlier. Surfacing that signal at the shortlisting stage does not replace the interview. It changes how the interview time is spent. The combination of AI recommendations pulling more relevant candidates into the funnel and AI screening giving recruiters a clearer picture of who to prioritize creates a loop that improves on both ends simultaneously: more of the right people applying, and faster decisions about who to advance. --- ## The Infrastructure That Makes It Work The features above share an implicit dependency: candidates need to be able to move through the process without friction, and recruiting teams need to see the full picture in one place. [Candidate Portal OTP Login](https://www.mangoapps.com/directory/app/job-board) removes the password requirement entirely. Candidates log into the portal using a one-time passcode delivered by email or SMS. No account creation, no forgotten credentials, no reason to abandon the process at the authentication step. The [Unified Candidate Portal](https://www.mangoapps.com/apps/offer-manager) goes further: accessed via a unique token link, candidates can view their application status, review offers, negotiate terms, and initiate onboarding steps — all without ever creating an account. [Offer Negotiation and Counter-Offer Flow](https://www.mangoapps.com/apps/offer-manager) handles the back-end of the process with the same logic. Candidates submit counter-offers from the portal. HR responds with revised terms. When both sides reach agreement, the offer letter updates automatically and confirmation goes to both parties. The negotiation that used to live in scattered email threads — no audit trail, no clear resolution point — now has a defined structure and a single record. --- ## What Changes When AI Serves Both Sides The historical model of recruiting AI was extraction: use it to process more candidates faster, at lower cost. The assumption was that candidates would bear the friction because they had no alternative. That assumption is weakening. In competitive hiring markets — for skilled roles and frontline roles alike — candidates who encounter friction find alternatives. The quality of the application experience is part of what you are competing on, whether or not it shows up in your cost-per-hire metrics. What this week's releases reflect is a different design premise: that AI working for candidates and AI working for recruiters are not in tension. When a candidate gets accurate answers before applying, they are better prepared. When they see relevant role recommendations, they apply to things they might actually want. When a recruiter sees a cultural fit score alongside skills and experience, they move through the shortlist with more confidence. The pipeline does not get faster because it is optimized for one side. It gets faster because both sides are less likely to drop out. *Also released this week: [Group-Based App Access Control](https://www.mangoapps.com/administration) lets admins manage app visibility at the employee group level directly from the marketplace panel — giving organizations precise control over which teams see which tools. And [Leave Balances in Hours or Days](https://www.mangoapps.com/solutions/time-attendance) now displays each employee's time off balance in the unit configured for their leave type, eliminating the decimal-day approximations that have long confused workers on hourly accrual policies.* --- # Blink Alternatives: Which Platform Is Right for Your Team? **Author:** MangoApps **Published:** 2025-11-27 **Category:** comparisons This article explores the most capable alternatives to Blink for organizations that need more than basic frontline messaging. It outlines the core factors to evaluate when comparing platforms, including communication reach, engagement tools, integrations, mobile functionality, and analytics. The piece provides detailed breakdowns of leading options such as MangoApps, Workvivo, Staffbase, Simpplr, Beekeeper, and Igloo, highlighting where each platform is strongest and where limitations may appear. It concludes with guidance on choosing a solution that supports both frontline and desk-based employees while reducing tool sprawl and improving overall employee experience. # Blink Alternatives: Which Platform Is Right for Your Team? ## Why messaging alone is not enough for distributed workforces Per Emergence Capital, 80% of the global workforce is deskless. That statistic shapes what any employee communications platform needs to deliver — and it is the number that explains why organizations start with Blink and eventually move on. Blink solves a specific problem well: fast, mobile-first messaging for frontline employees. The gap surfaces when the same organization also needs a searchable knowledge base, content governance, workflow automation, or analytics that tell leadership whether anyone actually read last week's safety update. Those needs do not disappear — they get patched with a second tool, then a third. Per IDC, the average employee spends 2.5 hours each day searching for information that should already be accessible. When communication lives in a messaging app, knowledge in a SharePoint site nobody opens, and scheduling in a separate system, that search time is not a worker productivity problem. It is a platform architecture problem. This guide compares six platforms organizations consider when they outgrow Blink — evaluated not on feature lists alone, but on whether each platform reduces fragmentation or adds another layer to it. ## The real cost of keeping Blink alongside other tools The case for replacing Blink rarely starts with a feature complaint. It starts with a finance conversation. Per Social Edge Consulting, 91% of organizations already operate an intranet, yet nearly a third of employees never log in — and only 13% use one daily. The tools are there. The adoption is not. That usage gap typically produces a workaround: teams layer messaging apps, document storage, scheduling software, and form tools together, each with its own license, its own IT overhead, and its own training cost. Replacing a frontline employee costs between $4,400 and $15,000 per person, which makes engagement and retention a direct cost-avoidance argument — not a culture initiative. Organizations that consolidate fragmented tool stacks onto a single platform have cut the number of systems IT manages by 3–4 times, reducing both licensing costs and administrative overhead. That is the total cost of ownership argument that Blink's per-seat pricing does not capture. Evaluating alternatives through this lens changes the criteria. The question is not whether a platform has messaging — they all do. The question is whether it can replace what is sitting next to Blink in the stack. ## Six Blink alternatives compared ### 1. MangoApps MangoApps combines a branded [employee app](/solutions/employee-app), an AI-powered intranet, and workflow automation in a single platform. It is built for organizations that serve both frontline and desk-based employees and need those two populations working from the same system rather than parallel tools. The platform's frontline reach is designed specifically for no-email, no-VPN access: employees log in with a phone number or a company-assigned ID, get a role-specific view of news, tasks, and documents, and can act on shift changes or forms without leaving the app. Organizations including OU Health and the Kansas City Chiefs have reached frontline adoption rates of 87–90% within the first few months of deployment — benchmarks that depend on the no-barrier login model as much as on the content strategy. The AI layer curates what each employee sees based on role, location, and shift pattern, which addresses the core problem of a bloated intranet: when everyone sees everything, most people ignore everything. Key differentiators worth evaluating: - **Branded employee app** with no corporate email or VPN required — a concrete requirement for frontline environments where most workers have never had a company-issued device - **Multi-engine AI** (OpenAI, Gemini, Anthropic, Azure) for search, content generation, and personalization — not a single-provider dependency - **Built-in workflow automation** that replaces manual routing for shift handoffs, onboarding steps, forms, and approvals - **Enterprise security** including SAML 2.0, OAuth 2.0, and SSO — a credible weakness for Blink's lightweight architecture in regulated industries - **[Employee communications](/solutions/employee-communications) analytics** that track reach, readership, and sentiment at the campaign and channel level **Best fit:** Distributed organizations with mixed frontline and desk-based populations that need communication, knowledge, and workflows in one place — and want to shrink the number of tools they maintain rather than expand it. ### 2. Workvivo Workvivo is built around the social engagement model: activity feeds, peer recognition, and community interaction that makes the platform feel more like a social network than a corporate intranet. That familiarity can accelerate adoption in culture-first environments and reduce the friction that causes most intranet rollouts to stall. Zoom acquired Workvivo in 2023, which has accelerated its integration with Zoom meetings and events. Organizations already running Zoom at scale will find the bundled pricing and unified login practical. Organizations evaluating Workvivo independently should understand that its roadmap is now shaped by Zoom's product priorities — a factor worth clarifying before a long-term commitment. **Best fit:** Communication-first organizations where cultural connection and peer recognition are the primary use case and where a Zoom-centric environment already exists. ### 3. Staffbase Staffbase is a structured communications platform built for editorial teams managing large content volumes across locations and languages. Its publishing workflow emphasizes controlled approvals, scheduling, and multi-language distribution — useful for organizations where communication consistency is tightly governed and content quality is audited regularly. The platform's mobile app is brandable and supports targeted distribution, though the emphasis is on publisher workflows more than employee interaction. Organizations that want employees to contribute to knowledge communities, comment on content, or participate in two-way conversation will find Staffbase more rigid than alternatives built around collaborative communication. **Best fit:** Large enterprises with dedicated communications teams that need editorial governance, multi-language support, and structured publishing workflows at scale. ### 4. Simpplr Simpplr is an employee experience platform centered on content governance and AI-driven personalization. Its content lifecycle management prompts designated owners to review, update, or archive pages on a schedule — which addresses the structural problem that renders most intranets useless over time: content that is never refreshed becomes invisible. The tradeoff is that Simpplr's model depends on consistent participation from those designated owners. Organizations without clear content ownership structures may find the governance framework creates friction rather than resolving it. For teams that can sustain the discipline, the result is a measurably more reliable intranet. **Best fit:** Enterprises where content quality and governance are the primary intranet problems, and where dedicated page ownership is realistic to maintain long-term. ### 5. Beekeeper Beekeeper focuses specifically on frontline, shift-based environments: quick updates, mobile-first access, lightweight checklists, and pre-built workflow templates for shift handoffs and incident reporting. Its strength is operational simplicity in workforces where employees check the app for a few minutes per shift and need nothing more complex than that. In 2025, Beekeeper merged with LumApps. The combined company brings Beekeeper's frontline depth alongside LumApps' intranet breadth, but the long-term product consolidation is still underway. Organizations evaluating Beekeeper should ask specific questions about roadmap direction, which features will be maintained independently, and what the support model looks like during the integration period before making a commitment. **Best fit:** Workforces that are predominantly frontline, primarily mobile, and need operational simplicity without the overhead of a full intranet. ### 6. Igloo Igloo offers a traditional intranet experience with out-of-the-box layouts, clear content hierarchies, and straightforward publishing tools. It suits organizations that want a dependable, stable intranet without extensive AI, automation, or personalization requirements — and where the workforce is primarily desk-based. In 2025, Igloo was acquired by Appspace. The acquisition introduces uncertainty about long-term product direction and how overlapping features between the two platforms will be handled. Organizations evaluating Igloo should assess roadmap clarity before committing, particularly for configuration investments that depend on features remaining independent. **Best fit:** Organizations that want a stable, structured intranet with predictable navigation and minimal configuration overhead. ## Three questions that clarify the right choice Feature lists do not distinguish platforms well at this tier — they have all solved the basic table-stakes problems. These three questions do the actual work of separating the right fit from the right-sounding one. **What is actually broken?** If frontline employees do not see updates, a mobile-first platform with no-barrier login solves it. If desk-based employees cannot find policies, a governed intranet with strong search solves it. If both problems exist simultaneously — which is the situation for most organizations evaluating Blink alternatives — a platform that treats both audiences as equal-priority is the only option that does not create a new gap while closing the old one. Tools that optimize for one audience and retrofit for the other show the seam quickly. **What gets replaced, not just added?** Per Social Edge Consulting, the average employee already spends just six minutes per day using intranet tools. When a new platform joins an existing stack rather than replacing parts of it, that number rarely improves. The most useful evaluation criterion is whether a platform can consolidate enough of the current toolset to reduce fragmentation, not whether it has every feature on a requirements list. Platforms that require maintaining adjacent systems — a separate scheduling tool, a standalone LMS, a form builder — are not solving the TCO problem, they are extending it. **What is the security and compliance baseline?** Blink's lightweight architecture is a reasonable tradeoff where mobile messaging speed is the only priority. For organizations in healthcare, financial services, or regulated industries, SAML 2.0, SSO, audit logging, and data governance are not optional. Several platforms on this list — MangoApps, Staffbase, and Simpplr — treat enterprise security as a baseline requirement. Others treat it as a configuration add-on. The distinction matters for procurement and compliance review timelines. For independent validation of how these platforms perform on frontline accessibility, search quality, and administrative overhead, the [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an analyst-level benchmark across the major options — a practical starting point for separating vendor claims from documented functionality. ## Choosing the platform that is right for your team Organizations that replace Blink are rarely unhappy with its messaging experience — they have outgrown its scope. Once a workforce spans multiple locations, shifts, and job types, the coordination overhead of maintaining Blink alongside a separate intranet, scheduling system, and knowledge base becomes a more expensive problem than any per-seat pricing comparison. The platform decision is really a stack decision. The right choice is the one that closes the most open gaps without creating new ones. For organizations where the frontline is the majority of the workforce — healthcare, retail, logistics, manufacturing — that almost always means a platform where mobile-first access, no-corporate-email login, and AI-powered personalization are built into the architecture rather than bolted on afterward. Frontline adoption rates of 87–90% are achievable, but they depend on removing friction at the login step, not on content strategy alone. For organizations that are primarily desk-based and need governance first, Simpplr and Staffbase represent the structured end of the spectrum. For organizations still sorting out whether they need a messaging tool or a full intranet replacement, Workvivo and Beekeeper represent the lighter-weight end. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how organizations of different sizes and structures are making this transition — a useful calibration point before finalizing a vendor shortlist and entering formal procurement. --- # The Hidden Handoffs Breaking Your Recruiting Pipeline **Author:** MangoApps Team **Published:** 2025-11-23 **Category:** news-and-updates Picture this: A recruiter has a strong finalist. The interviews went well, the team is aligned, and the offer is ready. # The Hidden Handoffs Breaking Your Recruiting Pipeline Picture this: A recruiter has a strong finalist. The interviews went well, the team is aligned, and the offer is ready. So the recruiter downloads a PDF, attaches it to an email, and asks the candidate to print, sign, scan, and return it. While waiting, they send a separate text to make sure the email arrived. The candidate logs into a third tool to check their application status. The offer letter needs a small revision, so the recruiter generates a new document and starts over. Nobody designed this process. It assembled itself — one tool at a time, one workaround at a time. And somewhere in all those handoffs, candidates who were genuinely interested stop responding. This week's releases across MangoApps' recruiting and scheduling tools reflect a coordinated effort to close those gaps — not by building shinier versions of each individual tool, but by eliminating the transitions where candidates and teams fall through. --- ## What Candidates Actually Experience From the moment someone sees your job posting to the moment they sign an offer, they pass through more friction points than most recruiting teams realize. A career page in one place, application status by email, interview scheduling via a third-party link, offer details in a PDF attachment, and e-signature through yet another platform. Each handoff is a moment where a busy, in-demand candidate might not make it through. The foundation of a better candidate experience starts earlier than most companies think — with how the career portal looks. The new [Career Portal Branding Customization](https://www.mangoapps.com/apps/job-board) lets admins set brand colors, upload a logo, add custom header and footer text, and inject CSS — all with a live preview before anything goes public. Built-in accessibility validation checks that color contrast meets WCAG standards. For candidates arriving from a job board or referral link, the first signal about whether a company is organized and professional is the careers page they land on. It matters before an application is ever submitted. Once a candidate is in the process, the [Unified Candidate Portal](https://www.mangoapps.com/apps/offer-manager) gives them a single destination for their entire hiring journey — accessible via a token link sent by email or SMS, with no account creation required. From there, they can check their application status, review an offer, negotiate terms, and initiate onboarding steps. For candidates evaluating multiple opportunities at once, removing the account creation step isn't a minor convenience. It's often the difference between completing the process and abandoning it. Communication gaps create their own dropout problem, particularly for frontline and hourly workers who are easier to reach by text than email. [Two-Way SMS](https://www.mangoapps.com/apps/job-board) gives recruiting teams the ability to let candidates reply directly to text messages — YES to confirm an interview, NO to decline, STATUS to check where they stand. No email thread, no portal login, no phone tag. For high-volume hourly hiring, where response speed often determines whether you get the candidate or the competitor does, this changes the practical math. --- ## The Infrastructure Behind Consistent Hiring Before a candidate sees anything, a lot can go wrong on the recruiter's side. Job postings go live before they're ready. Interview processes vary by recruiter, producing inconsistent experiences and unreliable data. Passive candidate lists from sourcing campaigns live in spreadsheets, disconnected from where the actual hiring happens. Three releases this week address the structural side. [Draft Job Postings](https://www.mangoapps.com/apps/job-board) gives recruiters the ability to write, revise, and get internal sign-off before anything goes live. A dedicated "Save & Publish" action makes the transition from draft to published explicit rather than accidental. This sounds like a small thing, but in practice, a draft workflow changes the culture around job postings — it creates space for review without awkward workarounds like publishing to a hidden URL or relying on someone to catch errors after the fact. The [Interview Workflow System](https://www.mangoapps.com/key-features/interview-scheduler) addresses something more fundamental: consistency. Admins can define named interview stages — phone screen, technical review, final round — and every recruiter working a given role follows the same ordered structure. Progress is tracked automatically. For teams where hiring managers have historically done things their own way, standardizing the interview pipeline is how you start generating reliable data about what's actually working. [Talent Pool CSV Import](https://www.mangoapps.com/directory/app/job-board) solves the practical problem at the start of every sourcing campaign: getting candidates from where you found them into where you're tracking them. Recruiters can upload a CSV file — from a LinkedIn export, an ATS migration, or an external sourcing list — and the import runs as a background job. A dedicated history panel shows the status of each past upload, along with row-level error reporting for anything that didn't come through cleanly. For teams seeding a new talent pool before a major hiring push, this removes what was previously a manual data entry project. --- ## Where Offers Close or Fall Apart The offer stage is where recruiting pipelines are most fragile. A finalist candidate receives an offer. They have questions. They want to negotiate. The only channel available is email — threads that sprawl, take days to resolve, and leave no clear record of what was agreed. Meanwhile, the candidate is fielding interest from a competitor. The [Offer Negotiation and Counter-Offer Flow](https://www.mangoapps.com/apps/offer-manager) brings that conversation into the platform. Candidates submit counter-offers directly from the candidate portal. HR responds with revised terms. Admins configure the maximum number of negotiation rounds allowed per offer. When a counter is accepted, the offer letter updates automatically and both parties receive email confirmation. What used to require multiple email threads and a manually edited document now has a defined process, an auditable record, and no reconciliation step at the end. [E-Signature via Dropbox Sign](https://www.mangoapps.com/apps/offer-manager) closes the final gap. The offer letter is generated from the platform, pre-populated with the agreed compensation details, and sent for signature — without anyone exporting a file or switching tools. Signature status updates in real time within the offer record. The version where a recruiter emails a PDF and waits three days for a scanned copy to arrive is no longer the default. --- ## When the Handoffs Disappear The interesting thing about a fragmented recruiting pipeline is that no single step is obviously broken. The job board works. The interview scheduler works. The offer tool works. The damage happens in the transitions — where information has to be re-entered, where candidates have to create accounts they'll never use again, where a recruiter switches tools six times to close a single hire. What this week's releases reflect is a different way of thinking about what recruiting software is for. Not a collection of best-in-class point tools that happen to share a vendor name, but a connected pipeline where the handoffs are handled automatically. That distinction matters most under pressure. High-volume seasonal hiring. A sudden surge in open roles. A competitive market where the first employer to move a candidate through the process quickly wins. That's when fragmented pipelines break — and when a connected one earns its keep. *Also released this week: [Public Shift Assignment Sharing](https://www.mangoapps.com/solutions/shifts-schedules) lets employees generate a read-only public link to their shift details — useful for coordinating with clients or external contacts without requiring platform access. And [Shift Marketplace Applications](https://www.mangoapps.com/apps/shift-marketplace) adds a formal application workflow for trade listings, so employees can submit a note with their application and listing owners can review all applicants before confirming a swap.* --- # The Invisible Friction Slowing Down Your Recruiting Pipeline **Author:** MangoApps Team **Published:** 2025-11-16 **Category:** news-and-updates Picture a Tuesday afternoon for a recruiter at a mid-sized company. She has a list of 180 passive candidates sourced from LinkedIn that need to go into a talent pool — so she starts adding them... # The Invisible Friction Slowing Down Your Recruiting Pipeline Picture a Tuesday afternoon for a recruiter at a mid-sized company. She has a list of 180 passive candidates sourced from LinkedIn that need to go into a talent pool — so she starts adding them one by one. She sends interview invites to six shortlisted candidates and waits, knowing she will spend the next two days exchanging emails about availability. She needs to finalize a compensation package for a senior engineer but does not have a recent comp benchmarking subscription, so she opens three browser tabs — Glassdoor, Levels.fyi, a year-old survey PDF — and triangulates manually. And somewhere in a spreadsheet, she is trying to figure out whether that staffing agency they signed in Q2 has produced a single hire worth the retainer. None of this is the actual work of recruiting. It is the overhead — the manual operations — that accumulates around it. And it is where candidate pipelines slow down, offers lose their edge, and good people accept other jobs while the process grinds on. The average time-to-hire for professional roles in the US sits at 44 days, and scheduling and coordination delays account for a disproportionate share of that window. Roughly 30% of candidates who accept competing offers cite slow process or lack of communication as the primary reason — not compensation. The sections below identify where recruiting friction originates, how to measure it, and what it takes to eliminate it — whether or not you have new tools in place. --- ## The Sourcing Problem: Getting Candidates In, Knowing Where They Came From Talent pools only work if you can build them efficiently. When sourcing at scale — a career fair, a LinkedIn campaign, an industry event — recruiters come back with dozens or hundreds of leads. The ability to get those candidates into the system quickly is what separates a pool that stays fresh from one that gets abandoned because the maintenance cost is too high. The new Talent Pool CSV Import addresses this directly. Recruiters can now upload a CSV file to seed a talent pool from any external export — an ATS, a LinkedIn Recruiter download, a spreadsheet from a sourcing partner. The import runs as a background job so the UI stays responsive, and an import history panel shows what succeeded, what was skipped, and why. For a sourcing campaign with 200 passive candidates, this is the difference between two hours of manual entry and a five-minute upload. But getting candidates in is only half the problem. The other half is knowing which channels are worth investing in going forward. Recruiting Sources Management gives talent acquisition teams a structured way to track exactly that. Admins can define a canonical list of sources — LinkedIn, Indeed, employee referrals, agency partners — and candidates get tagged at application time. Over time, the data tells a clear story: which sources produce the most hires, which produce the most noise, and where the sourcing budget is actually working. This matters more than it might seem. Recruiting teams that track source-to-hire data inside their ATS reduce mis-allocated sourcing spend by identifying that agency and job-board channels frequently produce high application volume but low offer-acceptance rates — a pattern invisible without structured source tagging. Without source tracking, those decisions get made on gut feel. With it, the data is inside the recruiting workflow rather than buried in a separate analytics tool. For HR leaders looking at broader workforce operations trends, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how talent acquisition teams are consolidating point tools into unified workflows. --- ## The Scheduling Problem: Why Candidates Are Still Sending Emails in 2025 Ask any recruiter what wastes the most time in the interview process, and scheduling will be near the top of the list. The standard sequence — send availability, wait for a reply, confirm, get a reschedule request, repeat — can take two to four days for a single interview slot. Coordinating interview panels across time zones adds an average of 3–5 additional business days to time-to-hire when scheduling is handled manually via email, a delay that compounds for senior or technical roles requiring multiple interviewers. Multiply that by every candidate in an active pipeline, and a meaningful share of time-to-hire is just coordination overhead. The Candidate Self-Scheduling Portal eliminates this loop. Recruiters generate a public booking link that shows real-time interviewer availability, and candidates pick a slot on their own — no account, no login, no back-and-forth required. The portal handles buffer time between sessions, daily interview caps, and link expiration gracefully. When a candidate books, the interviewer's calendar is updated automatically. The no-login requirement is worth noting separately. Requiring candidates to create an account to schedule an interview introduces friction that some candidates will not bother clearing. For competitive roles where strong candidates have multiple options, that friction has a real cost. A public link with a clean booking experience removes it entirely. Recruiters who manage high-volume pipelines — entry-level roles, seasonal hiring, volume recruiting for frontline positions — will see the most immediate impact. Per Emergence Capital, 80% of the global workforce is deskless, and for organizations hiring at scale into those roles, self-scheduling has even higher ROI than it does for knowledge-worker pipelines. Even for specialized roles where every candidate interaction is managed carefully, eliminating the scheduling email chain reduces the time between "shortlisted" and "interview scheduled" to a matter of hours. Teams managing shift-based or distributed workforces can find related scheduling guidance in [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling). AI-assisted scheduling is the clear direction of travel for this category — several platforms now offer automated candidate matching and calendar negotiation. The self-scheduling portal represents the practical, deployable step available today: no AI dependency, no integration complexity, and immediate reduction in coordination overhead. --- ## The Offer Problem: Making Competitive Compensation Decisions Without Leaving the Platform Compensation is where hiring pipelines often stall or fail. An offer that takes too long to finalize loses candidates. An offer that misses the market gets rejected and damages the employer brand. Both outcomes are more common when the people preparing offers are working from stale data or cobbled-together external research. Offer Manager Salary Benchmarking brings market compensation data directly into the offer workflow. Before finalizing a package, HR and recruiting teams can pull up benchmark ranges and market positioning for the specific role, level, and location — all without switching to an external tool or a separate subscription. The Compensation Benchmarks and Market Analysis pages sit inside Offer Manager, which means the people preparing offers have the data they need at the moment they need it. The practical impact is faster, more defensible decisions. When a recruiter can show a hiring manager that the proposed salary is at the 60th percentile for the market and within the internal equity band for that level, the conversation moves quickly. When that data has to be assembled from external tabs and forwarded in an email, the same conversation can stretch across multiple days and multiple stakeholders. There is also a compliance dimension that is easy to overlook. Compensation benchmarking done through ad-hoc tab-switching — Glassdoor, salary surveys, peer data — introduces offer inconsistency that increases the risk of pay-equity audit exposure, a compliance concern now flagged in several state-level pay transparency laws. Having benchmark data embedded in the offer workflow creates a defensible, repeatable process rather than a one-off judgment call. --- ## How to Measure Recruiting Pipeline Friction Before You Fix It Identifying friction is the prerequisite to eliminating it. Most recruiting teams have a general sense that their process is slow, but without structured measurement, it is difficult to know which stage is the actual bottleneck — or whether an intervention is working. Three metrics are worth tracking at minimum: - **Stage-to-stage conversion time**: How many days does a candidate spend in each pipeline stage — sourced, screened, interviewed, offered, accepted? The longest gaps reveal where friction is concentrated. - **Source-to-hire rate by channel**: Which sourcing channels produce candidates who reach the offer stage, not just the application stage? High application volume from a channel with low conversion is a cost center, not an asset. - **Scheduling cycle time**: How many calendar days elapse between the decision to interview a candidate and the interview actually occurring? This is often the most undertracked metric and one of the most impactful. For teams without dedicated recruiting analytics tooling, these metrics can be approximated from ATS timestamps and calendar data. The goal is not a perfect dashboard — it is enough signal to know whether sourcing, scheduling, or offer velocity is the primary drag on time-to-hire. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how operations and HR teams are building measurement frameworks for exactly this kind of workflow visibility. --- ## Which Friction Point to Tackle First Not every recruiting team has the same bottleneck. The right starting point depends on where time is actually being lost: - **If your pipeline is thin and sourcing volume is low**: Source tracking and import tooling have the highest leverage. You cannot optimize a pipeline you cannot fill, and you cannot improve sourcing ROI without knowing which channels are working. - **If you have candidates but interviews are slow to schedule**: Scheduling overhead is the bottleneck. Self-scheduling or structured calendar tooling will compress time-to-hire faster than any other single intervention. - **If interviews are happening but offers are stalling**: Compensation data access and offer workflow are the constraint. Faster, more consistent offer preparation reduces the window in which candidates accept competing offers. For most mid-market recruiting teams running 5–7 disconnected point tools — a separate ATS, a scheduling tool, a comp benchmarking subscription, a sourcing platform — the deeper issue is that there is no unified talent operations workflow. Each handoff between tools introduces delay and data loss. Consolidating into a platform that handles sourcing, scheduling, and offer management as connected steps rather than separate processes is what closes the gap between working hard and moving fast. MangoApps' [workforce management solutions](/solutions/workforce-management) are built around this kind of connected operations model, extending from recruiting through day-to-day employee experience. --- ## Closing: The Compound Cost of Small Delays — and How to Stop Them None of the individual frictions in a hiring pipeline feel catastrophic in isolation. Adding candidates manually takes an extra hour. Waiting for scheduling replies adds a couple of days. Pulling comp benchmarks from external sources takes thirty minutes. Guessing which job boards are working because there is no source tracking costs something harder to measure — probably money, probably quality. But these delays compound. The 44-day average time-to-hire for professional roles is not driven by slow decision-making — it is driven by the logistics and coordination that surround the decisions. Candidates who are genuinely in-demand do not wait two weeks for a process to grind through its administrative steps. And per the data above, roughly 30% of candidates who accept competing offers cite slow process or lack of communication as the primary reason. What MangoApps shipped this week is not a single big feature. It is four targeted interventions at four distinct points in the recruiting pipeline: getting candidates in faster, knowing which channels are worth it, eliminating scheduling overhead, and making offer decisions with real market data. Individually, each saves some time. Together, they address the actual shape of the problem — which is that recruiting velocity gets eaten by friction, not by any single bottleneck. For HR and talent acquisition leaders who feel like their teams are working hard but moving slowly, the answer is usually the same: map where the time is actually going, measure the three metrics above, identify the primary bottleneck, and fix it before moving to the next. This week's releases make that question easier to answer, and a few of the most common answers easier to fix. Teams looking to connect recruiting improvements to broader employee experience outcomes can explore how MangoApps approaches the full [employee experience platform](/solutions/modern-hcm) — from sourcing through onboarding and beyond. --- # The Gap Between Deciding and Doing Is Where HR Work Disappears **Author:** MangoApps Team **Published:** 2025-11-09 **Category:** news-and-updates A recruiter ends a third-round interview with a clear sense that this is the right hire. She closes her laptop knowing exactly what comes next: three reference requests need to go out, a... # The Gap Between Deciding and Doing Is Where HR Work Disappears A recruiter ends a third-round interview with a clear sense that this is the right hire. She closes her laptop knowing exactly what comes next: three reference requests need to go out, a background check needs to be ordered, a panel needs to get scheduled. None of it is difficult, exactly. But none of it is automatic, either. Each step means composing an email, logging into a separate system, chasing a non-response, then circling back to check whether it was received. By the time the candidate clears the full gauntlet, two weeks have passed and another offer is already on the table. The decision happened in the interview room. The execution took two weeks. That gap — the stretch between knowing what to do and actually completing it — is where candidates are lost, where hires fall through, and where HR teams quietly burn hours that should be going somewhere else. This week's releases address that gap in three separate places: hiring, performance management, and procurement. The feature names are different. The underlying problem is the same. --- ## The Hiring Pipeline Is Only as Fast as Its Slowest Manual Step The recruiting workflow has always had a natural chokepoint: the moment a candidate moves from "promising" to "finalist." That's when the verification work begins — and, historically, when the process stalls. Reference checking is perhaps the most obvious example. A recruiter reaches out to three contacts via email, waits, sends a reminder, waits again, and eventually pieces together notes from three separate conversations with no standardized format and no audit trail. [Automated Reference Checking](https://www.mangoapps.com/key-features/recruiting-dashboard) replaces that chase with structured questionnaires sent through a branded self-service portal — no account required for the reference, no manual follow-up for the recruiter. Responses are tracked, reminders go out automatically, and everything lands in one place on the candidate's profile. Background checks have the same shape. Most teams have treated this as a context-switch: open the Checkr portal, re-enter candidate information, initiate the order, and then wait for an email that tells you to go back and look at results. The [Checkr integration](https://www.mangoapps.com/solutions/talent-acquisition) eliminates that round-trip. An HR coordinator initiates the order directly from the candidate profile, results flow back automatically, and every adjudication decision is logged in the same place as the rest of the candidate record — with FCRA compliance support built in. [Interview self-scheduling](https://www.mangoapps.com/key-features/interview-scheduler) addresses a different kind of coordination drag. Scheduling a panel interview usually means a recruiter playing mediator between a candidate's availability and three or four interviewers' calendars — a chain of emails that can stretch across days. Shareable scheduling links let candidates pick their own time against live interviewer availability, with confirmed bookings pushed directly to Google and Outlook. No back-and-forth, no double-booking, no manual calendar entry. And for teams that use skills assessments as a filter, [Candidate Assessments](https://www.mangoapps.com/key-features/competency-assessments) brings that step inside the platform as well — configurable templates, automated delivery, responses that appear on the candidate profile alongside interview notes. A recruiter no longer needs to manage a separate assessment tool and then manually reconcile results. Taken individually, each of these is a convenience. Taken together, they represent something more significant: a hiring pipeline where a recruiter's decision to advance a candidate triggers immediate, automated progress on every subsequent step — without switching systems, chasing responses, or rebuilding context. --- ## Performance Reviews Close. The Follow-Up Work Usually Doesn't. The same pattern shows up in performance management, in a slightly different form. A performance review cycle ends. HR pulls scores, identifies employees who fell below the threshold, and starts the manual work of creating PIPs and development plans — reaching out to managers, documenting the process, making sure nothing was missed. For a mid-sized organization running reviews across hundreds of employees, this can take days. The risk isn't just the time. It's inconsistency: who got a PIP and who didn't can depend as much on which HR coordinator processed their review as on their actual score. [Performance Review Outcome Automation](https://www.mangoapps.com/directory/app/employee-performance-management) addresses this directly. HR admins configure score-range rules — any employee below a certain threshold automatically receives a Performance Improvement Plan or Career Development Plan, and the employee's manager receives an email notification with next steps. The plan is created the moment the review is finalized, not a week later when someone gets to it. Duplicate-prevention logic ensures the same plan isn't created twice if a review is reprocessed. This doesn't replace the human judgment that goes into a performance conversation. It replaces the mechanical triage that follows — the step that was never about judgment in the first place. --- ## Approved Doesn't Mean Done Procurement has a version of this too. A purchase requisition works its way through a multi-level approval chain. Finance signs off. And then, in most organizations, someone has to manually create a purchase order, notify the vendor, track the invoice when it arrives, and reconcile it against what was actually received. The new [Procurement app](https://www.mangoapps.com/directory/app/procurement) handles that entire downstream workflow — purchase orders, vendor invoices, three-way matching against POs and receipts, payment tracking, and budget controls that alert finance before thresholds are crossed. A department head submits a requisition; the approval workflow routes it automatically; a PO is generated on approval; the vendor invoice is matched when it arrives. The decision to spend is still a human one. The paperwork that follows doesn't have to be. --- ## Decisions and Execution Shouldn't Live That Far Apart Underneath these releases — the recruiting automation, the performance follow-through, the procurement workflow — is a pattern worth naming. Organizations are generally decent at making decisions. They're often poor at executing the steps that decisions require, because those steps are scattered across manual processes, separate systems, and institutional memory held by whoever happens to be paying attention. The [OKR Hub](https://www.mangoapps.com/key-features/goals-management) released this week takes a version of this problem up the organizational stack. Setting goals is straightforward. Ensuring that individual contributor work is actually connected to those goals, tracking whether key results are on pace, and surfacing at-risk objectives before the quarter ends — that's where the execution gap typically appears. The OKR Hub adds structured check-ins, AI-assisted planning, at-risk alerts, and a visual cascade from company objectives down to individual tasks, so the gap between intent and tracking closes at every level. [Global Search with Ask AI](https://www.mangoapps.com/ai/search) addresses a related friction: knowing that information exists somewhere in the platform but not knowing where to look for it. A unified search bar across people, tasks, reviews, goals, documents, and recruiting items means that the decision to find something doesn't require knowing which module to open — and when built-in results fall short, Ask AI can escalate the query to a conversational answer without leaving the page. The common thread is execution fidelity: the degree to which what an organization intends to happen actually happens, with the right timing, the right documentation, and the right people in the loop. Each of this week's releases chips away at a different place where that fidelity breaks down. The features are distinct; the problem they're solving is not. --- *Details on individual features are available in the product changelog for [November 3](https://www.mangoapps.com/key-features/goals-management), [November 4](https://www.mangoapps.com/ai/search), [November 5](https://www.mangoapps.com/directory/app/employee-performance-management), [November 6](https://www.mangoapps.com/directory/app/procurement), and [November 7](https://www.mangoapps.com/key-features/recruiting-dashboard).* --- # LumApps Alternatives: 8 Better Employee Intranet Solutions for 2025 **Author:** MangoApps **Published:** 2025-11-05 **Category:** comparisons This in-depth guide explores the leading LumApps alternatives for 2025, helping organizations evaluate modern intranet platforms that connect communications, knowledge, and operations in one unified experience. It compares eight top solutions—MangoApps, Simpplr, Workvivo, Interact Software, Staffbase, Beekeeper, Blink, and Microsoft SharePoint—highlighting their strengths, ideal use cases, and pricing models. The article also covers ROI evaluation frameworks, mobile and frontline enablement, and the growing role of AI in personalizing employee experiences. Readers gain actionable insights into how unified intranet platforms drive engagement, productivity, and cost efficiency across hybrid and deskless workforces. # LumApps Alternatives: 8 Better Employee Intranet Solutions for 2025 Per Social Edge Consulting's intranet benchmark research, 91% of organizations now operate an intranet — but only 13% of employees use it daily, and nearly a third never log in at all. That gap is not a user behavior problem. It's a platform design problem, and switching from LumApps to any alternative doesn't automatically close it. LumApps built a capable modern intranet for desk-based workforces. It surfaces content cleanly, integrates with Google Workspace, and works well for organizations where every employee has a corporate email address and a laptop. The limitations appear when an organization tries to reach frontline or deskless workers, when security teams require granular governance controls, or when IT needs AI capabilities that don't lock the company into a single provider. This article evaluates 8 LumApps alternatives on three criteria that determine whether your intranet achieves the daily usage rate that makes it worth the investment: enterprise security governance, frontline and deskless access, and AI architecture flexibility. The platforms listed here differ from each other in meaningful ways — which one belongs on your shortlist depends on which of those criteria are non-negotiable for your workforce. ## Why the standard comparison checklist misses the real differentiators Most intranet comparisons rank platforms on feature checklists: file storage, news feed, social features, mobile app. Those checklists don't tell you whether a platform works for a hospital where 70% of staff don't sit at desks, or whether it lets a security-conscious enterprise control exactly who can publish to which department, or whether the AI assistant routes sensitive queries away from third-party APIs. Per IDC research, employees spend an average of 2.5 hours per day searching for information — a cost that doesn't improve by adding features to a platform workers don't open. It improves when the platform fits how workers actually access information. Per Emergence Capital research, 80% of the global workforce is deskless, which means mobile-first access is not a nice-to-have feature for most organizations — it's the baseline. The three criteria below cut through the feature noise. Evaluate your top alternatives on these before scheduling demos. **Enterprise security governance.** With five major vendors now positioning "secure intranet" as a dedicated product theme, security governance has moved from a footnote in the integrations section to a first-class evaluation criterion. Specifically: does the platform support SSO and SAML 2.0 natively? Does it offer role-based publishing permissions granular enough that a department manager can post to their own team without IT involvement? Does it maintain an audit trail of who published what and when? For regulated industries — healthcare, financial services, government — these are not enhancement requests; they are baseline requirements. **Frontline and deskless access.** A platform that requires a corporate email address to log in immediately excludes most of the 80% of workers who are deskless. Practically: does the platform support QR code login or SSO-based access for workers without corporate credentials? Does it function in low-connectivity environments? Does it deliver content in 50+ languages for multilingual workforces? **AI architecture flexibility.** Platforms that hard-code a single AI provider create a vendor dependency that's difficult to unwind and that many security teams will block outright for sensitive content. Platforms that let administrators configure model routing by content type or user group give IT the governance layer needed to actually deploy AI features rather than restrict them. ## The 8 alternatives, evaluated ### MangoApps MangoApps is a [modern intranet platform](/solutions/modern-intranet) designed to serve desk-based, hybrid, and frontline workers from a single architecture — rather than layering frontline access onto a desk-first platform. The security governance layer includes SSO, SAML 2.0, LDAP, and role-based publishing permissions that don't require IT involvement for routine department-level configuration. The AI architecture supports multiple providers — OpenAI, Google Gemini, Anthropic, and Azure OpenAI — with administrator-controlled routing based on content sensitivity, which addresses the governance concern that causes most enterprise security teams to block AI rollouts. For frontline access, MangoApps supports a branded [employee app](/solutions/employee-app) that workers reach via QR code or phone number — no corporate email required. It delivers content in 50+ languages, functions in low-connectivity environments, and reaches key features within two taps. MangoApps appears in [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) and has been included in leading analyst evaluations of intranet platforms. Best fit: organizations of 500 to 50,000+ employees where the workforce includes both desk-based and frontline staff, and where IT and security teams require governance controls before approving an AI rollout. ### Simpplr Simpplr has built a strong reputation for implementation speed and clean UI design for desk-based workforces. Its AI assistant is tightly integrated and requires minimal configuration. The tradeoffs: it is primarily optimized for organizations where all employees have corporate email addresses, the governance controls are less granular than platforms designed for regulated industries, and frontline access requires additional configuration that adds cost and deployment time. Best fit: technology companies, professional services firms, and knowledge-worker-heavy organizations where frontline coverage is not a primary requirement. ### Staffbase Staffbase is a communications-first platform with strong investment in the mobile employee app experience. Its multi-channel distribution — email newsletters, digital signage, app push notifications — makes it well-suited for organizations that prioritize one-way top-down communication at frontline reach. The governance depth for two-way publishing permissions is less developed than MangoApps or Interact, and AI features are early-stage compared to several alternatives on this list. Best fit: organizations whose primary goal is reaching frontline workers with corporate communications, rather than enabling two-way knowledge sharing or community engagement. ### Unily Unily is positioned at the enterprise end of the market, with deep content governance options and strong behavioral analytics. Unily achieved 90% frontline adoption within six months at CVS, and Wipro documented $20 million in cost avoidance through its Unily deployment — concrete ROI benchmarks that large enterprise buyers evaluating the investment case should factor in. The tradeoff is cost and complexity: Unily is among the more expensive options here, and implementation timelines reflect that depth. Best fit: large enterprises with complex content governance requirements and the internal resources to manage a full-scale deployment. ### Workvivo (by Zoom) Workvivo's acquisition by Zoom positions it as a natural extension for organizations already standardized on Zoom for meetings and async video. The platform performs well on engagement features — recognition, social feeds, surveys — and the Zoom integration is genuinely differentiated for hybrid teams. For frontline workers without Zoom licenses, access requires additional licensing consideration. Security governance controls suit most mid-market organizations, though regulated industries may find them less granular than required. Best fit: Zoom-standardized organizations where employee engagement and recognition are the primary goals, and the workforce is predominantly desk-based. ### Microsoft Viva / SharePoint Intranet Microsoft's intranet story runs through SharePoint as the content layer, with Viva adding the employee experience surface. For organizations already in the Microsoft 365 ecosystem, the integration is real — files, Teams channels, and intranet content share a unified permission model. The practical challenge: per SWOOP Analytics research, the average employee spends just six minutes per day in SharePoint-based intranet tools. SharePoint's information architecture complexity typically results in intranets that IT configures correctly but employees navigate poorly. Viva Connections partially addresses discoverability, but administrative overhead for governance remains significant. Best fit: organizations committed to Microsoft 365 where IT has the bandwidth to maintain the SharePoint architecture and the workforce is primarily desk-based. ### Interact Interact is a governance-forward platform, particularly well-suited for regulated industries that need audit trails, mandatory read acknowledgement, and granular role-based publishing without SharePoint's administrative complexity. Its strongest footprint is in EMEA, though it operates globally. AI features are emerging but are not yet at the depth of MangoApps or Simpplr. Best fit: regulated industries (healthcare, financial services, government) with significant EMEA presence, where governance compliance is the primary evaluation criterion. ### Happeo Happeo is built natively on Google Workspace, making it the natural choice for Google-standardized organizations. Its pages and channels model is clean and familiar for knowledge workers. Frontline access is limited — it assumes a Google account for all users — and governance controls suit mid-market companies rather than enterprise-regulated environments. Best fit: Google Workspace-standardized organizations with primarily desk-based workforces, particularly in the 200–2,000 employee range. ## How to match an alternative to your workforce model **Primarily desk-based, Google Workspace:** Happeo or Simpplr. Both implement quickly, integrate cleanly, and don't require governance infrastructure beyond what standard mid-market IT teams manage. **Primarily desk-based, Microsoft 365:** Microsoft Viva / SharePoint if IT capacity is available to maintain the architecture; Simpplr or Interact if lower administrative overhead is a priority. **Hybrid workforce (all employees have corporate email):** MangoApps, Simpplr, or Workvivo. Differentiate on whether engagement features, implementation speed, or governance depth is the binding constraint. **Frontline-heavy workforce (40%+ of employees without desks or corporate email):** MangoApps or Staffbase. The distinction is whether you need two-way knowledge sharing and governance (MangoApps) or primarily top-down communication distribution (Staffbase). **Regulated industry requiring audit trails and SAML governance:** MangoApps or Interact. Both treat security governance as a first-class feature rather than an integration layer. **Large enterprise requiring deep customization and proven enterprise ROI benchmarks:** Unily, with the understanding that implementation timeline and cost are at the high end of the market. ## What drives the adoption gap — and what closes it The 13% daily usage rate that Social Edge Consulting's intranet research documents isn't fixed by switching vendors. It's fixed by selecting a platform whose access model matches how your workforce actually operates. A platform that requires corporate email to log in will never reach deskless workers. A platform without role-based governance won't get approved for rollout by a security team in a regulated industry. A platform with single-vendor AI will face IT restrictions that prevent AI features from being deployed at all. The eight platforms on this list are not interchangeable alternatives. For organizations where frontline access, enterprise security governance, and AI flexibility are genuine requirements, the shortlist is MangoApps, Interact, and Unily — with the differentiators being budget tolerance, workforce composition, and the relative priority of AI capability versus governance depth. For desk-first organizations where those constraints don't apply, Simpplr and Happeo offer faster time-to-value with lower administrative overhead. For third-party benchmarks that go beyond vendor-authored comparisons, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) evaluates these platforms on structured criteria across hundreds of data points — a useful cross-check before committing to a shortlist. --- # 5 SharePoint Alternatives for Enterprise Collaboration **Author:** MangoApps **Published:** 2025-11-04 **Category:** replace-sharepoint This article helps enterprise leaders understand why SharePoint often falls short as an intranet, especially when supporting global or frontline teams. It breaks down the full cost of deploying and maintaining SharePoint, including licensing, customization, migration, governance, and third-party tools. The piece then evaluates five modern alternatives—MangoApps, Simpplr, LumApps, Staffbase, and Unily—with clear explanations of their strengths, ideal use cases, and limitations. Readers also get guidance on how to plan a smooth migration, what to prioritize when choosing a new platform, and how AI is reshaping the employee experience. The goal is to help organizations choose a more effective, user-friendly, and cost-efficient intranet that serves every employee. # 5 SharePoint Alternatives for Enterprise Collaboration The question most IT and HR leaders face is not whether to replace SharePoint, but which alternative can actually deliver on the promise of a connected, usable workforce platform. According to Social Edge Consulting, 91% of organizations run an intranet — yet only 13% of employees use it daily, and nearly a third never log in at all. That gap is not an engagement problem. It is a platform-fit problem. Here are five platforms organizations are evaluating as SharePoint replacements in 2026: 1. **MangoApps** — A unified employee experience platform combining intranet, workforce management, and AI-powered communication in a single deployment. 2. **Simpplr** — An AI-first intranet focused on content personalization and frontline reach, with documented adoption benchmarks for distributed workforces. 3. **Unily** — An enterprise intranet built for large, complex organizations, with deployment timelines as short as eight weeks. 4. **LumApps** — A Google Workspace–integrated employee experience platform with native personalization and multilingual support. 5. **Staffbase** — A mobile-first employee communications platform purpose-built for deskless and frontline workers. Each platform addresses a different combination of the problems that cause SharePoint deployments to underperform. The right choice depends on workforce composition, existing technology stack, and how much of SharePoint's functionality the organization actually needs to replicate. --- ## Why SharePoint leaves most organizations needing more SharePoint's base license is included in most Microsoft 365 agreements, which makes it appear cost-neutral at the planning stage. The full picture is different. Implementation and customization — building a usable, branded intranet on top of SharePoint's raw infrastructure — typically costs between $100,000 and $400,000 in year one, before ongoing maintenance. Annual IT support, third-party integrations, and developer time to handle updates compound that total over time. The cost problem is compounded by a usage problem. IDC estimates that employees spend 2.5 hours per day searching for information — not because the information does not exist, but because most intranets do not surface it when and where employees need it. SWOOP Analytics puts the average daily time employees spend actively using intranet tools at six minutes. An organization investing in SharePoint infrastructure and seeing six minutes of daily use per employee is getting a poor return on both the technology and the adoption effort. Emergence Capital estimates that 80% of the global workforce is deskless — working in manufacturing, healthcare, retail, logistics, and field services where desktop access is intermittent or absent. SharePoint's mobile experience was designed as an extension of its desktop model, not as a primary interface. For frontline-heavy organizations, this is a structural limitation, not a minor inconvenience. --- ## MangoApps: unified platform for frontline and desk employees MangoApps approaches the SharePoint alternative problem differently from pure-play intranet vendors. Rather than replicating SharePoint's document-storage model in a more user-friendly wrapper, MangoApps integrates intranet, communication, workforce scheduling, and task management into a single platform with a shared employee record. Employees access the same system whether they are on a desktop at headquarters or on a mobile device at a job site. The [modern intranet solution](/solutions/modern-intranet) includes AI-curated news feeds that adjust content by role, location, hire date, and engagement history — without requiring employees to configure anything. Only 22% of company intranets currently deliver personalized content to employees, according to the State of the Digital Workplace and Modern Intranet 2024 research. That gap is the primary reason most intranets see usage patterns consistent with SWOOP Analytics' six-minute daily average. MangoApps also surfaces SharePoint integration as a coexistence strategy rather than a forced replacement. Organizations running Microsoft 365 can federate SharePoint, Teams, and Google Drive files into MangoApps search, giving employees a single place to find content without migrating existing document libraries. SharePoint integration complexity has become the most active competitive battleground in the intranet market — with more than ten vendors publishing content on the topic — and MangoApps' 200-plus native integrations are a meaningful proof point for organizations that cannot afford to abandon existing infrastructure. The [company portal](/key-features/company-portal) provides the branded intranet experience most organizations want from SharePoint, with far less custom development required. --- ## Simpplr: AI-first intranet with frontline adoption benchmarks Simpplr's positioning centers on AI-driven content delivery and measurable adoption outcomes. Purpose-built intranet platforms, including Simpplr, have achieved 90 to 95% frontline adoption within the first six months — a benchmark SharePoint-based deployments rarely reach without significant third-party tooling, according to case studies from Simpplr's Uber Freight deployment and similar implementations. Simpplr's content targeting is persona-driven and administrator-configured rather than employee-managed. Communication teams define segments by role, department, and location; the platform handles content routing without requiring employees to set preferences. For organizations where the communication team is responsible for driving adoption, this model tends to produce more consistent engagement than platforms that rely on employee self-configuration. Simpplr is strongest for desk-based or hybrid workforces. Its mobile interface is functional, but organizations with a high proportion of frontline workers in warehouse, retail, or healthcare settings typically evaluate it alongside platforms with stronger native mobile capabilities. --- ## Unily: enterprise-grade intranet with documented deployment speed Unily is built for the complexity of large enterprises: multi-country deployments, multilingual content, sophisticated governance, and integration with legacy systems. The platform is most frequently selected by organizations with 5,000 or more employees navigating a content governance challenge as much as a usability one. What distinguishes Unily in vendor evaluations is deployment speed relative to enterprise complexity. A 40,000-employee airline replaced its legacy intranet with Unily in eight weeks — a deployment timeline that counters the assumption that enterprise intranet replacements require 12 to 18 months of project work. A global media network reported 30 times more engagement than its predecessor system in year one. A global enterprise captured $20 million in cost avoidance after moving off a fragmented intranet stack — a data point that reframes the "SharePoint is already paid for" argument. The first-year cost of a platform that no one uses is not zero. --- ## LumApps: employee experience platform for Google Workspace organizations LumApps is the preferred intranet alternative for organizations whose primary productivity stack is Google Workspace rather than Microsoft 365. It integrates directly with Google Drive, Calendar, and Workspace applications, giving employees a unified access point without switching contexts. Content personalization is a core capability: administrators configure segments by language, role, location, and function, and the platform delivers distinct homepages for different employee groups without separate deployments. Multilingual support is native rather than a third-party add-on, which makes LumApps a common choice for multinational organizations with regional content governance requirements. Its strongest use cases are in office-based, globally distributed enterprises where Google Workspace is already the standard. --- ## Staffbase: mobile-first communications for frontline workforces Staffbase was built from the premise that most workforce communication platforms design for desk employees and adapt reluctantly for frontline access. Its architecture inverts that priority: the mobile experience is the primary interface, and the desktop application is secondary. For organizations in manufacturing, logistics, retail, and healthcare — where deskless employees represent the majority of operational headcount — Staffbase's communication model is structurally different from SharePoint alternatives that treat mobile as an afterthought. Employees access the platform through a branded app without requiring a corporate email address or VPN, which removes the authentication friction that causes low adoption on SharePoint mobile. Staffbase's analytics surface read receipts, acknowledgment rates, and open rates at the segment level, so communication teams can see whether frontline employees in specific facilities are actually receiving and reading critical information. --- ## How to evaluate SharePoint alternatives The evaluation criteria that matter depend on where the current deployment is failing. For most organizations, the failure is in one of three places: adoption, governance, or frontline reach. **Adoption failures** show up as low daily active use. If the intranet is being used as a document repository rather than a communication platform, the problem is usually feed relevance and notification design, not the underlying infrastructure. Platforms with AI-driven personalization — MangoApps, Simpplr, Unily — address this directly. **Governance failures** appear as content that goes stale, inconsistent branding across departments, and no clear ownership of the intranet over time. Platforms with built-in content lifecycle management, scheduled publishing, and governance workflows reduce the manual coordination load that makes SharePoint content degrade at scale. **Frontline reach failures** are the most common and the most underweighted in evaluation processes. If a significant portion of the workforce does not have reliable desktop access, the platform's mobile interface is not a secondary feature — it is the primary interface for most of the workforce. Evaluate this with a live device test: access the platform on a personal mobile device, without VPN, on a first log-in. The authentication and navigation experience in that scenario tells more than any vendor demo. For a structured evaluation framework, the [ClearBox 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) covers criteria weights and vendor scoring across the category. --- ## What migration actually looks like The perception that switching intranet platforms is a multi-year project is one of the primary reasons organizations remain on underperforming SharePoint deployments. Modern packaged platforms have changed the timeline calculus. The eight-week Unily deployment at a 40,000-employee enterprise is at the fast end of the range, but it illustrates that pre-configured platforms operate on a fundamentally different timeline than custom-built SharePoint implementations. The variables that determine migration speed are content volume, integration count, and governance requirements. Organizations with large SharePoint document libraries typically migrate governance structure first and content in waves. Organizations with complex single-sign-on requirements need IT involvement early. Organizations with straightforward structures — a central communications team and a small number of integration points — can complete migrations in weeks rather than months. The transition does not have to be binary. Several organizations run MangoApps and SharePoint in parallel during a transition period, using MangoApps' SharePoint federation to surface legacy content through the new interface while teams migrate document ownership incrementally. This approach reduces the migration risk that typically comes from a hard cutover and lets adoption build organically before the legacy system is retired. --- ## Choosing the right SharePoint alternative There is no universal SharePoint replacement. MangoApps fits organizations that need intranet and workforce operations in the same platform, with strong frontline and desk employee capabilities. Simpplr fits desk-heavy organizations prioritizing AI-driven adoption metrics. Unily fits large enterprises with complex governance and a need for documented speed-to-value. LumApps fits Google Workspace organizations with multilingual requirements. Staffbase fits frontline-dominant organizations where mobile is the primary access point. The deciding factor in most evaluations is not feature parity with SharePoint — it is whether the platform gets used. According to [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), employees who perceive internal communication as relevant to their work report higher engagement and retention rates. A platform that delivers role-specific content to the right employees at the right time outperforms a more feature-complete platform that employees have stopped checking. That distinction is what separates a SharePoint replacement that works from one that replicates the same six-minutes-per-day problem in a new interface. --- # 7 Leading Workvivo Alternatives for Enhanced Employee Experience in 2025 **Author:** MangoApps **Published:** 2025-11-04 **Category:** comparisons Companies seeking Workvivo alternatives in 2025 are looking for platforms that do more than share updates. They need systems that connect distributed teams, streamline workflows, and strengthen retention. This article breaks down seven leading options—MangoApps, Staffbase, Simpplr, Microsoft Viva Engage, LumApps, Blink, and Beekeeper—and explains how each supports communication, engagement, and frontline accessibility. It also highlights key evaluation criteria like mobile access, integrations, AI capabilities, and governance, with research-backed insights into productivity and turnover impact. A detailed comparison table, guidance for choosing the right platform, and a comprehensive FAQ help decision-makers understand which solution aligns with their organization’s needs. In 2025, the search for better employee experience platforms has never been more urgent. As organizations adapt to hybrid and distributed work, legacy tools like Workvivo often fall short of the flexibility, depth, and integration modern enterprises require. From limited customization and siloed data to weak frontline access, companies are now seeking unified solutions that truly connect every employee — whether at a desk, on the floor, or in the field.This guide explores seven leading Workvivo alternatives that go beyond communication feeds and engagement widgets. Each combines scalability, integration, and intelligent automation to support the evolving workforce and deliver measurable outcomes in productivity, retention, and employee satisfaction.Why Organizations Are Searching for Workvivo AlternativesCompanies are realizing that engagement tools alone are not enough. They need systems that simplify work, not add complexity. According to Gallup’s State of the Global Workplace 2024, only 27% of managers are engaged, and global disengagement costs firms nearly $9.6 trillion in lost productivity—about 9% of global GDP. This disengagement is especially acute among frontline workers, who make up roughly 80% of the global workforce but are rarely prioritized in digital transformation efforts (Emergence Capital).Courtesy of gallup.comCommon pain points driving platform migration include:Fragmented tools: The average employee switches between 35 apps and toggles screens over 1,100 times a day, draining focus and energy (TechRepublic).Integration gaps: Legacy systems fail to connect with Microsoft 365, Google Workspace, or HRIS platforms, leading to data silos and duplication.Frontline disconnect: Deskless teams lack equal access to company information, which drives turnover as high as 74% in sectors like hospitality and transportation (Deloitte).High attrition costs: Replacing a frontline employee can cost up to 40% of annual salary, and for managers, up to 200% (Gallup).Research consistently shows that organizations that unify communication, knowledge, and workflow management see a 20–25% productivity lift and 10–15 percentage-point improvement in frontline retention (JLL).Key Factors for Evaluating Workvivo AlternativesSelecting the right employee experience platform requires more than comparing feature lists. The decision should reflect how well each solution supports business goals, connects distributed teams, and adapts to change.1. Mobile AccessibilityFor enterprises with deskless workers, mobile-first design is non-negotiable. Healthy intranet adoption rates hover between 60–70% weekly, while best-in-class implementations achieve 85%+ usage (Social Edge Consulting, 2025 Intranet Benchmark). A responsive app that delivers updates, tools, and self-service access keeps everyone informed and aligned.2. Integration EcosystemThe best platforms integrate seamlessly with collaboration suites like Microsoft 365 and Google Workspace, along with HR and payroll systems. MangoApps, LumApps, and Staffbase all offer 200+ prebuilt connectors that reduce IT overhead and enhance data continuity.3. AI and AutomationModern intranets are evolving into AI-powered digital assistants. Intelligent search, automated workflows, and content generation capabilities improve engagement and drastically cut wasted time. A good benchmark: intranet search success rates above 75% (Social Edge Consulting).4. Customization & GovernanceOrganizations need to adapt branding, permissions, and governance workflows to reflect their structure. Strong editorial and compliance controls also ensure communication remains consistent and trustworthy across departments.5. Analytics & InsightsFinally, engagement analytics and sentiment tracking turn communication from guesswork into strategy. Real-time dashboards reveal which content resonates, where engagement drops, and how teams interact across locations.7 Leading Workvivo Alternatives for Enhanced Employee ExperienceEach of the following platforms offers a distinct approach to building connected, informed, and high-performing teams. Below is a quick comparison before we explore each in depth.1. MangoApps — Unified AI-Powered Employee PlatformMangoApps stands out as the AI-powered employee platform that unifies intranet, modern HCM, and workforce management in one experience. Built for both office and frontline workers, it offers communication, collaboration, scheduling, and learning within a single, governed environment.Key strengths include:AI-powered search and Assistants that answer questions, automate workflows, and personalize updates.Mango Employee AI, which delivers contextual insights and automates repetitive HR and operations tasks.Enterprise-grade security (HITRUST, ISO 27001, SOC 2, FedRAMP).Rapid deployment, with low IT overhead and strong mobile accessibility.Organizations adopting MangoApps report faster time-to-answer, fewer support tickets, and 90%+ intranet adoption rates. For companies seeking a single source of truth across communication and operations, MangoApps is the most comprehensive alternative to Workvivo.Compare MangoApps vs. Workvivo here. 2. StaffbaseStaffbase focuses on enterprise-level internal communications. It offers omnichannel content delivery across web, email, mobile, and digital signage, enabling corporate messaging to reach all employees simultaneously.Strengths include a built-in editorial planning suite, sentiment analytics, and seamless Microsoft 365 integration. Staffbase is ideal for large organizations where communications are centralized but content workflows need structure and governance.However, Staffbase remains more focused on publishing and communication, lacking deeper workflow and operational management tools for frontline use.See a more detailed comparison of MangoApps vs. Staffbase here. 3. SimpplrSimpplr is known for its sleek, user-friendly intranet design and strong personalization engine. Its AI capabilities tailor news feeds and search results by role, department, and behavior, increasing relevance and adoption.Simpplr’s Salesforce integration is a differentiator for companies already using Salesforce as a collaboration backbone. However, it offers less flexibility for operations-heavy environments and relies heavily on external systems for workforce management.Best suited for organizations prioritizing modern user experience and engagement metrics.See more about how MangoApps compares with Simpplr here.4. Microsoft Viva EngageMicrosoft Viva Engage extends the Microsoft ecosystem with integrated communication and collaboration capabilities. Its core advantage lies in native Teams integration, allowing employees to connect and collaborate without switching tools.For organizations already invested in Microsoft 365, Viva Engage offers a unified, secure experience. However, it has limited customization beyond Microsoft’s suite and may require additional licensing to achieve parity with standalone intranet platforms.See how MangoApps compares with Microsoft Viva here. 5. LumAppsLumApps combines social intranet features with robust Google Workspace integration, making it a preferred choice for global organizations with strong Google adoption. It supports multilingual content, localized news feeds, and advanced governance tools for compliance-heavy industries.Its personalization and content management strengths make it a powerful alternative to Workvivo, though its learning and task management features are less developed. LumApps excels for enterprises prioritizing communication consistency and brand-aligned experiences across regions.Learn more about how MangoApps compares with LumApps here. 6. BlinkBlink takes a mobile-first approach to employee communication, built specifically for deskless and shift-based teams. Its app simplifies access to schedules, announcements, and documents, ensuring high adoption rates among frontline users.While Blink is highly intuitive, it focuses more on communication than analytics or knowledge management. Organizations seeking simplicity and quick deployment will find Blink a strong fit, but enterprises requiring deep data governance or workflow automation may outgrow it.7. Beekeeper‍Beekeeper positions itself as a secure operational communication platform designed for compliance-sensitive industries. It features GDPR-compliant messaging, integration with shift scheduling tools, and built-in training modules.Beekeeper recently merged with LumApps, forming a combined entity that aims to unify their communication and intranet capabilities. However, it remains unclear how the two products will integrate and interoperate in the coming months. Analysts caution that customers should closely monitor how service levels evolve under the merged organization, as well as how the roadmap for innovation and feature development will be prioritized.Beekeeper is best suited for sectors like healthcare, logistics, and manufacturing, where data privacy, multilingual communication, and mobile accessibility are critical. Its operational depth makes it an ideal replacement for Workvivo in heavily regulated environments.Read more about howMangoApps compares against Beekeeper here. Choosing the Right Workvivo AlternativeSelecting the right platform depends on your organization’s priorities. Consider these dimensions:Integration considerations: Which tools best align with your existing stack (Microsoft 365, Google Workspace, HRIS)?Feature priorities: Is your focus communication, collaboration, or operational automation?Scalability factors: Does the platform support multi-region governance and language localization?Implementation timeline: SaaS deployment speed varies — MangoApps can go live in under 90 days, while others require 4–6 months.Unified platforms like MangoApps consistently outperform point solutions. Studies by IDC and Gallup show that integrated digital experiences correlate with 25% higher productivity and 43% lower turnover.Read more comparisons of MangoApps against additional vendors here. Improving Employee Experience in 2025: Your Next StepsThe era of siloed intranets is ending. As AI reshapes how employees connect, learn, and perform, the best employee experience platforms combine intelligence, integration, and inclusivity.Action plan:Assess your needs — Identify current pain points and quantify their impact.Prioritize outcomes — Rank engagement, retention, and operational efficiency by business impact.Request demonstrations — See how each platform fits your workflows and workforce composition.Pilot before rollout — Test with representative teams and track adoption, satisfaction, and time-to-answer metrics.For enterprises ready to move beyond fragmented tools, MangoApps offers a single, AI-powered employee platform that unites intranet, HCM, and workforce management into one experience.Schedule a demo to see how MangoApps can help your organization build a connected, informed, and engaged workforce in 2025.Frequently Asked Questions About Workvivo1. What are the main differences between MangoApps and Workvivo?MangoApps offers a unified platform that integrates intranet, HCM, and workforce management with AI-powered automation and insights. Workvivo, by contrast, focuses primarily on employee communication and engagement. MangoApps’ broader capabilities make it better suited for organizations seeking to connect communications with daily workflows.2. Is Workvivo still a good option for smaller organizations?Yes, Workvivo remains a viable choice for small to midsize businesses that need a simple communication hub. However, companies with complex integration or compliance requirements may quickly outgrow its limited customization and scalability.3. What’s the significance of the Beekeeper–LumApps merger?The merger aims to bring together LumApps’ intranet expertise and Beekeeper’s frontline communication strengths. That said, it is still unclear how the platforms will integrate, how customer service will be managed, and how innovation roadmaps will be prioritized. Organizations evaluating either platform should monitor post-merger developments closely.4. How do AI-powered intranets improve employee experience?AI-driven systems help employees find information faster, personalize content delivery, automate routine workflows, and provide leaders with actionable insights on engagement and performance. This reduces wasted time and enhances the sense of connection and productivity.5. What is the average implementation time for these platforms?Implementation varies widely. MangoApps can deploy in under 90 days with minimal IT overhead. Larger systems like Staffbase or LumApps typically require 4–6 months for full rollout, depending on integration depth and governance needs.6. Which Workvivo alternative is best for frontline workers?Platforms like MangoApps, Blink, and Beekeeper are particularly strong for frontline engagement due to mobile-first design, multilingual support, and task accessibility. MangoApps stands out for providing a single hub for communication, scheduling, and training.7. How should organizations measure success after implementation?Success metrics typically include adoption rate (target 70–85%), content engagement, search success rate (>75%), employee satisfaction (≥4.2/5), and reductions in turnover or app sprawl. Tracking these KPIs over time helps justify ROI and guide ongoing optimization. --- # Staffbase Alternatives Compared: 6 Solutions for Better Employee Engagement **Author:** MangoApps **Published:** 2025-11-03 **Category:** comparisons This guide breaks down six leading alternatives to Staffbase for organizations seeking a more flexible, cost-effective, and mobile-ready employee experience platform. It explains common Staffbase challenges, compares strengths and limitations across key competitors, and highlights how modern AI-powered solutions—like MangoApps—support communication, HR, and frontline operations in one unified system. Readers will learn what to evaluate, how platforms differ, and which options best fit their workforce and strategic priorities. # Staffbase Alternatives Compared: 6 Solutions for Better Employee Engagement Per IDC, employees spend 2.5 hours every day searching for information they need to do their jobs. For desk workers, that's a productivity problem. For frontline employees — the 80% of the global workforce without a corporate email address or a fixed workstation, per Emergence Capital — it's often the reason they never find it at all. That's the tension behind most Staffbase evaluation cycles. Staffbase built a strong reputation for top-down enterprise communications. But its architecture assumes an employee with a corporate email login, a desktop browser, and an IT department standing by to provision access. Organizations whose workforce doesn't match that profile — manufacturers, retailers, healthcare systems, logistics operators — increasingly report that the platform serves communications leaders well and reaches frontline workers inconsistently. Six alternatives have emerged as the serious comparisons for 2025. Before evaluating them, it's worth being specific about what "better" means here, because [rising costs, limited flexibility, and complex implementation requirements](/articles/mangoapps-2026-forrester-wave-intranet-platforms) aren't equally distributed across alternatives. ## What Staffbase does well — and where organizations are drawing the line Staffbase remains a polished platform for enterprise communications. Its branded mobile app, Microsoft 365 integration, and editorial governance tools give communications teams a reliable channel for top-down messaging. Organizations that primarily need to push news, announcements, and policy updates to a desktop-first workforce will find it capable. The evaluation shift happens when organizations ask a different question: can this platform reach the employee who clocks in at a distribution center, takes patient calls in a call center, or works a retail floor between shifts — without requiring IT to provision an account? Per Social Edge Consulting, 91% of organizations operate an intranet, but nearly a third of employees never log in and only 13% use it daily. That gap isn't a technology failure. It's a design mismatch between how the platform was built and how most of the workforce actually works. Platforms designed with frontline access as the default — not a configuration option — close that gap at the infrastructure level. Platforms that treat it as a feature to be enabled later don't. ## The six alternatives ### 1. MangoApps MangoApps combines intranet, communications, HR, and workforce operations in a single platform built around a unified data layer. Its defining architectural choice is the [employee app](/solutions/employee-app) — joinable via QR code or SMS link without a corporate email address, accessible on a personal device, and designed for shift-based workers who check updates between tasks rather than from a desktop. The practical outcome of that design: OU Health achieved 87% workforce engagement within a few months of launching MangoApps' branded employee app. TeamHealth consolidated over 200 previously separate systems into a single mobile dashboard. These results represent the full workforce — including the employees desk-first platforms consistently miss. MangoApps' AI layer handles search, content generation, and workflow automation across the same unified data model that serves HR, operations, and communications. That means search results, recognition feeds, and compliance documentation all live in one place, governed by the same permissions structure, rather than assembled from integrations between separate tools. MangoApps was named a Leader in the 2025 IDC MarketScape for Employee Experiences for Integrated Employee Workspaces and recognized in the 2026 Forrester Wave Intranet Platforms evaluation. **Best for**: Organizations where frontline workers represent a significant share of the workforce and where consolidating tools is an explicit goal. **Deployment**: No IT provisioning required for frontline enrollment. Full adoption benchmarks typically reached within 90 days. ### 2. Microsoft Viva Microsoft Viva extends the Teams and SharePoint stack with dedicated modules for learning, wellbeing analytics, and knowledge discovery — all surfaced within familiar Microsoft interfaces. Its value proposition is reduction of context switching, not transformation of the digital workplace. Employees already living in Outlook and Teams find Viva intuitive to adopt. The wellbeing analytics module is a genuinely differentiated capability: it surfaces burnout risk signals from real behavioral data, giving HR teams something most employee experience platforms don't offer. Learning modules delivered inside Teams reduce the gap between training content and the moment skills are needed. The limitation is structural. Viva's depth scales with Microsoft 365 licensing and IT infrastructure investment. Organizations without a full Microsoft 365 deployment face additional costs before the integration value materializes. Frontline mobile functionality is improving but remains secondary to the desktop-first experience. **Best for**: Large enterprises already standardized on the Microsoft ecosystem where change management is the primary constraint. ### 3. Simpplr Simpplr's strongest feature is its governance model. Role-based content ownership, editorial approval workflows, and policy enforcement controls make it a capable choice for industries where content accuracy is a compliance requirement — financial services, healthcare administration, legal. Its AI-powered intranet assistant reduces the administrative burden of search and content surfacing. Non-technical content owners can manage their spaces without IT support, which improves the ongoing content freshness that most intranet deployments struggle to sustain past the first 90 days. The trade-off: Simpplr's governance orientation leans toward broadcast rather than dialogue. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents the shift toward platforms that collect and act on employee feedback continuously — organizations running annual survey cycles significantly underperform those with embedded, continuous feedback loops. Simpplr handles the publication side well; the bidirectional feedback infrastructure is thinner. **Best for**: Enterprises in regulated industries where content governance and accuracy are non-negotiable constraints. ### 4. LumApps LumApps solves a specific infrastructure problem: organizations running mixed Google Workspace and Microsoft 365 environments who need a single communications layer that connects both. Its native integration across both ecosystems — with single sign-on, document federation, and content personalization — is genuinely difficult to replicate with other tools. The technical capability comes with corresponding overhead. LumApps deployments require IT expertise to configure permissions, integrations, and content routing. Organizations with limited IT bandwidth consistently report that implementation timelines extend beyond initial estimates, and ongoing management is more demanding than with more self-serve platforms. The value is real; the cost to unlock it is also real. **Best for**: Hybrid-cloud enterprises with dedicated IT capacity and a genuine need to bridge Google and Microsoft ecosystems. ### 5. Workvivo Workvivo (now backed by Zoom) is the most social-oriented platform in this comparison. Its design borrows from consumer social media — activity feeds, shout-outs, reactions, and video storytelling — to create a sense of community that traditional intranets rarely achieve. Per SWOOP Analytics, employees spend an average of six minutes per day on company intranet tools; Workvivo's feed model creates a daily habit that static platforms don't. The social architecture generates genuinely higher participation rates in organizations where culture and belonging are the primary communication goals. Its Zoom integration adds a natural path from announcement to live meeting, which reduces the friction that usually derails video communication programs. The limitation is scope. Workvivo is primarily a communications and culture platform — it doesn't extend into HR workflows, workforce management, or operational integration. Organizations that want employee engagement and operational infrastructure in the same tool will build an integration stack around it. **Best for**: Culture-driven organizations where community and belonging are the primary goals and operational integration can be handled by other systems. ### 6. Blink Blink is built specifically for deskless and shift-based workers. Its architecture is intentionally lightweight: no desktop dependency, fast deployment, and a focus on the tasks frontline employees actually perform — viewing schedules, receiving shift updates, submitting time-off requests, and accessing HR documents from a personal device. For organizations whose evaluation centers on frontline reach, Blink achieves it with less implementation overhead than most enterprise platforms. The trade-off is ceiling: reporting capabilities are basic, enterprise customization options are limited, and the platform doesn't scale into the governance, HR integration, or analytics depth that growing organizations eventually require. **Best for**: Frontline-heavy organizations that need immediate mobile reach and can manage without enterprise-grade analytics or workflow automation. ## How to evaluate the right fit When selecting the right alternative, the most important variable is workforce composition. A platform that ranks highly on enterprise governance will underperform for an organization where 60% of employees work without a corporate email address — and vice versa. Three evaluation questions clarify the decision: **1. What does enrollment look like for your lowest-access employee?** For desk workers, any platform in this list works. The differentiation is frontline enrollment: can a warehouse associate join via QR code on a personal phone without contacting IT? MangoApps and Blink answer yes by design. The others range from configurable to dependent on enterprise IT infrastructure. **2. What's the governance requirement?** Organizations in regulated industries need editorial approval chains, policy versioning, and audit logs. Simpplr and LumApps have the deepest governance tooling. MangoApps covers compliance requirements — HITRUST, ISO 27001, SOC 2 certifications — with role-based permissions. Workvivo and Blink are less suited to compliance-intensive environments. **3. Does the platform need to replace other tools, or complement them?** MangoApps and Viva are consolidation platforms — both are designed to reduce the number of tools organizations maintain. Blink, Workvivo, and Simpplr are more focused platforms that typically operate alongside existing HR and operations systems. The [ClearBox 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent scoring across all of the major platforms in this comparison — useful when the evaluation requires third-party validation beyond vendor materials. ## What sustained engagement requires The decision to move away from Staffbase is often framed as a platform selection problem. The underlying challenge is usually access architecture: platforms built assuming a corporate email address and a desktop workstation will consistently underserve the majority of the workforce in most industries. The alternatives that close this gap most completely share a design principle: frontline enrollment is not a configuration option, it's the default. PetSmart's MangoApps deployment achieved 4x industry-average engagement — not because the platform had more features, but because it reached employees who hadn't been reachable before. The barrier wasn't engagement; it was access. Per Gallup's 2026 State of the Global Workplace, organizations that collect and respond to employee input continuously outperform those running annual survey cycles by a compounding margin. The platform choice determines whether that feedback loop is structurally possible for the majority of your workforce, or only for the fraction at a desk. ## Frequently asked questions **What's the most common reason organizations leave Staffbase?** High enterprise licensing costs and limited frontline reach are the two most frequent drivers. Organizations with large deskless workforces often find that reaching employees without corporate email accounts requires significant additional configuration and cost beyond the base platform. **Which alternative is best for frontline-heavy industries like healthcare or retail?** MangoApps and Blink are purpose-built for frontline reach — both offer corporate-email-free enrollment and mobile-first interfaces designed for shift workers. MangoApps adds HR and operations depth; Blink is more narrowly focused and faster to deploy at scale. **How do pricing models differ from Staffbase?** Staffbase uses enterprise-tier pricing that can be cost-prohibitive for mid-sized organizations. MangoApps and LumApps offer modular pricing that scales with features and user counts actually needed. Blink is typically priced per deskless employee, which can deliver favorable ROI for organizations with large frontline workforces. **How important is AI in an intranet decision today?** Increasingly significant. Arctus research shows 17% of enterprises are already piloting generative AI in their intranet environments. Platforms with native AI — for search, content generation, and workflow automation — reduce the ongoing administrative burden that causes intranet content to go stale, which is the primary reason adoption collapses after launch. --- # Simpplr Alternatives: 8 Platforms Compared for 2025 **Author:** MangoApps **Published:** 2025-10-31 **Category:** comparisons Organizations evaluating Simpplr in 2025 are looking for more than basic intranet features. They need AI-driven search, enterprise-grade security, mobile accessibility, and integrations that connect every employee and workflow. This comparison reviews eight leading Simpplr alternatives and explains how each platform approaches communication, knowledge, and frontline support. It also examines the recent LumApps–Beekeeper merger and the uncertainty it introduces for buyers. The analysis shows how MangoApps stands apart with a unified, AI-powered employee platform that brings intranet, communication, HR, and operations together in one governed system. # Simpplr Alternatives: 8 Platforms Compared for 2025 The 2025 intranet shortlist conversation usually starts in the wrong place. Most comparison guides open with features — AI search, social feeds, integrations — and rank platforms on those dimensions. What they skip is the enrollment question: can the platform reach employees who don't have a corporate email address or company-issued device? Per Emergence Capital, 80% of the global workforce is deskless. Per IDC, employees spend 2.5 hours per day searching for information they need to do their jobs. Both figures are commonly cited in intranet ROI models — but they only apply to employees the platform can actually reach. Per Social Edge Consulting, 91% of organizations operate an intranet, and only 13% of employees use one daily. Nearly a third never log in at all. That is not a content problem or a culture problem. It is an access model problem. Frontline employee replacement costs run from $4,400 to $15,000 per worker depending on role. When an intranet fails to reach deskless teams, the disengagement that results is one of the most avoidable costs in the workforce equation — and one that rarely appears in any platform's ROI calculator. The eight platforms below are the most common replacements for Simpplr in enterprise evaluations. Each is assessed against the three criteria that most directly predict whether a deployment produces measurable outcomes or just adds another tool to the stack. ## What actually separates intranet platforms in 2025 Before the feature comparison, three criteria function as filters. They describe whether a platform can serve the full organization, not just what it does well for the employees who already have access. **Frontline access model.** The difference between a platform that reaches 20% of the workforce and one that reaches the whole organization is enrollment, not features. Mobile-first enrollment on personal devices — without requiring corporate credentials, VPN access, or IT provisioning — is what converts deskless and frontline workers from excluded to connected. Platforms that require corporate email or device enrollment as a prerequisite will produce the 13% daily-use outcome regardless of how well-designed the UI is. Per SWOOP Analytics, the average employee who does log in to an intranet spends six minutes per day doing so. Raising that number starts with changing who the platform can reach. **Security certification depth.** SOC 2 is the baseline — every platform on this list meets it or an equivalent. The question for regulated industries is what sits above baseline: GDPR for EU operations, HITRUST for healthcare, ISO 27001 for global enterprise. As of 2025, five vendors now lead with "secure intranet" positioning in their marketing, which means security has become a table-stakes filter rather than a differentiator. The right procurement question is whether the platform meets the organization's specific certification requirements, not whether it has security features in general. **Total cost of ownership, not license cost.** Enterprise SharePoint deployments carry first-year costs of $130,000–$426,000 for 1,000 users when implementation, customization, and governance overhead are included, per Awesome Technologies Inc.'s 2025 cost model. That range rarely appears in initial pricing conversations. Understanding year-one TCO before signing changes the comparison meaningfully for any platform that requires heavy IT customization, third-party integrations, or consultant-led onboarding. ## The 8 Simpplr alternatives evaluated ### 1. MangoApps The distinction that matters for MangoApps isn't feature breadth — it's architecture. MangoApps is the only platform on this list that consolidates intranet, HR data, and operational workflows in a single governed system rather than assembling them from external integrations. The Employee Data Layer centralizes data across communication, HR, and operations, which gives the AI assistant the context needed to provide answers that are actually useful, not just search results from disconnected sources. On frontline access: MangoApps supports mobile-first enrollment on personal devices without requiring corporate email or IT provisioning. OU Health achieved 87% workforce engagement within months of launching a branded employee app for clinical staff. PetSmart reported four times the industry-standard engagement rate under the same model. Both outcomes followed from the same structural change — employees could reach the platform from a device they already carried, without credentials they didn't have. The [MangoApps modern intranet solution](/solutions/modern-intranet) covers how that enrollment model works across industries. Security tier: SOC 2, GDPR, optional HITRUST. Frontline access: mobile-first, no corporate email required. Best for: enterprises that need a unified platform covering communication, knowledge, HR, and operations without managing multiple integrated tools. ### 2. Workvivo Workvivo's strength is the social experience. The platform's design borrows from consumer social media — feeds, recognition posts, live streaming — and that design choice pays off in adoption for organizations whose primary goal is culture and engagement. Integration with Zoom is native, which makes it a natural fit for distributed teams already on the Zoom ecosystem. The limitation becomes visible when the use case expands beyond communications. Workvivo uses Zoom AI Companion for meeting summaries, but AI is not embedded across the platform in a way that addresses search, workflow automation, or HR data. Deeper functional requirements — approval workflows, federated knowledge management, operational reporting — require integrations that add complexity and cost. Security tier: SOC 2. Frontline access: limited; primarily desk-based. Best for: organizations where culture and social engagement are the primary goal and operational integration requirements are minimal. ### 3. Staffbase Staffbase is built for internal communications at scale. Multi-channel delivery across desktop, mobile, email, and digital signage is genuinely strong, and the localization and translation capabilities handle global rollouts well. ISO 27001 and GDPR certifications position it for European enterprise. The native Microsoft 365 integration is deep — content publishing, authentication, and analytics connect cleanly to the Microsoft stack. That Microsoft dependency is also the constraint. Organizations not fully standardized on Microsoft face more friction, and the AI functionality is narrowly scoped to content drafting and targeting for communications teams. Broader workflow automation, HR data integration, and cross-system visibility require additional tooling outside Staffbase. Security tier: ISO 27001, GDPR. Frontline access: available with caveats; enrollment model depends on Microsoft provisioning for most customers. Best for: large enterprises with a strong internal communications function and a standardized Microsoft 365 environment. ### 4. Beekeeper Beekeeper was built specifically for frontline workers — hospitality, logistics, retail, construction — and the frontline-first design shows. Shift management, real-time operational communication, and mobile-first deployment without corporate email are genuine strengths that desk-first platforms don't match. The factor that introduces risk for buyers in 2025 is the announced merger with LumApps. As of this writing, the combined company has not clarified whether Beekeeper and LumApps will consolidate into a single platform, which features will be maintained, or how customers will transition. Organizations evaluating Beekeeper should request explicit roadmap commitments and long-term support guarantees before signing. The frontline capability is real; the product stability question is not resolved. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) includes independent analysis of both platforms and the merger's implications for buyers evaluating either. Security tier: GDPR, ISO compliance. Frontline access: strong; the core use case. Best for: frontline-heavy industries where the merger timeline risk has been evaluated and accepted. ### 5. Blink Blink's positioning is speed to value. The platform deploys quickly, the mobile-first interface requires minimal training, and the straightforward design keeps adoption friction low. ISO 27001 certification provides a solid security baseline. Integrations with Okta and ServiceNow cover the common authentication and ticketing use cases. The scalability ceiling becomes visible as organizations grow or add complexity. Governance controls, workflow automation, and the data-layer integrations needed for HR or operations reporting are limited. AI functionality covers content drafting but does not extend to search, translation, or automated task creation across the platform. For smaller or mid-market organizations that need to move fast and don't require enterprise-scale governance, Blink is a practical choice. For enterprises with complex requirements, those limitations compound over time. Security tier: ISO 27001. Frontline access: mobile-first, strong. Best for: smaller or mid-market organizations prioritizing fast deployment and adoption over deep integration. ### 6. Unily Unily targets enterprises with complex customization requirements, and the platform delivers on that. Governance and content management controls are comprehensive, user segmentation handles multi-region workforce structures well, and the integration with Microsoft Copilot gives content teams AI assistance within the Microsoft 365 ecosystem. Unily cites significant customer outcomes — including a $20M cost-avoidance result at Wipro and 90% frontline adoption within six months at CVS — as evidence of enterprise ROI. The tradeoff is implementation. Unily typically requires IT-led customization, extended deployment timelines, and ongoing configuration to adapt to organizational changes. Organizations that prioritize time-to-value or don't have dedicated IT resources for the build-and-maintain cycle will find the total cost of ownership higher than the initial pricing conversation suggests. Security tier: SOC 2, ISO. Frontline access: available with extensive implementation. Best for: large global enterprises with dedicated IT resources for customization and multi-system governance. ### 7. LumApps LumApps integrates deeply with both Google Workspace and Microsoft 365, which makes it attractive for organizations already standardized on either ecosystem. Content management, social collaboration, and multilingual support for global teams are genuine strengths. SOC 2 and GDPR certifications meet enterprise compliance requirements for most industries. The same merger caveat that applies to Beekeeper applies to LumApps. As the combined entity works through product consolidation, buyers face uncertainty about roadmap direction, pricing changes, and whether existing deployments will require migration to a unified platform. The technical foundations of LumApps (Google/Microsoft ecosystem) and Beekeeper (frontline operations) are different enough that unification will require significant architectural decisions — the timeline and outcome of which have not been publicly communicated. Security tier: SOC 2, GDPR. Frontline access: via Beekeeper post-merger; timeline unclear. Best for: organizations standardized on Google Workspace or Microsoft 365, with tolerance for merger-period roadmap uncertainty. ### 8. Interact Interact has historically served compliance-driven industries — healthcare, financial services, government — where governance, auditability, and role-based permissions matter more than social engagement features. The analytics and reporting capabilities are detailed. ISO certification and SSO support meet regulated-industry requirements. Microsoft 365 integration and API connectivity cover the common enterprise stack. The limitation is AI maturity and workflow automation depth. Interact functions as a traditional intranet with strong governance controls rather than an intelligent employee platform. For organizations in regulated industries that prioritize compliance documentation and intranet publishing, it is a capable choice. For organizations expecting AI-driven search, automated content creation, or workflow intelligence, the platform's architecture reflects an earlier generation of intranet design. Security tier: ISO. Frontline access: limited. Best for: regulated industries where governance and auditability are the primary requirements and AI automation is secondary. ## How to match platform to use case The comparison above shows that no platform is the obvious choice for every organization. The practical decision depends on which constraint is binding: **If frontline access is the primary constraint:** MangoApps, Beekeeper (evaluate merger risk carefully), or Blink for smaller teams. The enrollment model question — can employees without corporate email enroll on personal devices — should be a first-call filter, not an afterthought. **If the organization is standardized on Microsoft 365:** Staffbase and Unily integrate most deeply. MangoApps also integrates with Microsoft 365 without depending on it, which matters if the Microsoft footprint changes over time. **If HITRUST or healthcare-specific compliance is required:** MangoApps is the only platform on this list with optional HITRUST certification. For regulated industries where that matters, it narrows the field significantly before any feature comparison begins. **If speed to value is the priority:** Blink deploys fastest for smaller organizations. MangoApps is designed for mid-to-large organization launches in weeks through existing integrations. Platforms requiring extensive IT customization — Unily, some LumApps deployments — extend timelines to months. The [MangoApps 2026 Forrester evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) covers how independent analysts positioned MangoApps against the enterprise intranet field — a useful reference for procurement teams building a scoring rubric. ## Three questions to ask before signing Most platform evaluations end at the demo. The questions that separate useful procurement from a decision the organization revisits in eighteen months: **What is your enrollment model for employees without corporate email?** If the answer involves IT provisioning each user, or requires a company-issued device, the platform is desk-first in practice regardless of how the mobile app is marketed. Ask for the specific steps a frontline employee takes from app download to active user, without IT involvement. **What is the year-one total cost for our organization, including implementation, customization, and support?** License pricing rarely matches what the first year actually costs. Ask for a TCO model that includes professional services, integration work, and ongoing administration overhead. The $130,000–$426,000 range cited earlier is useful framing when vendors decline to provide their own model. **For Beekeeper or LumApps: what does the contract specify about product support, migration paths, and pricing stability post-merger?** Merger-period uncertainty is a legitimate risk in a multi-year technology investment. A contract that doesn't address those questions explicitly shifts that risk entirely to the buyer. The goal of any intranet evaluation is to understand which platform can reach the entire workforce and convert that reach into measurable outcomes. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how HR and communications leaders are benchmarking platform reach and engagement before and after deployment decisions — the same framework applies to any vendor on this list. --- # Why Managing Employee Benefits Breaks HR Teams Every Year **Author:** MangoApps Team **Published:** 2025-10-26 **Category:** news-and-updates Picture an HR manager in late October. Open enrollment is running. # Why Managing Employee Benefits Breaks HR Teams Every Year Picture an HR manager in late October. Open enrollment is running. Somewhere in a shared drive sits a spreadsheet tracking which employees haven't acknowledged the annual HIPAA notice. In a separate tab, a terminated employee from two weeks ago is in limbo — someone needs to generate a COBRA election notice before the mandatory 14-day deadline. In a different folder, last year's ACA 1095-C forms were assembled by hand: cross-referenced against payroll exports, formatted in a document template, saved as individual PDFs, and emailed to hundreds of employees before the IRS filing window. None of these tasks is complicated in isolation. All of them are time-consuming, high-stakes, and entirely manual at most organizations. Miss a COBRA deadline and the penalty can reach $110 per day per qualified beneficiary — with no statutory cap in certain violation scenarios, per DOL/IRS regulatory guidance. Miss an enrollment window for a new hire and they arrive at open enrollment next year still on the wrong plan. Miss a benefits acknowledgment record and the exposure shows up in the next audit. This is why benefits administration breaks HR teams every year. Not because anyone is doing it wrong — but because the compliance calendar is long, the deadlines are fixed, and the tools most teams rely on weren't designed to connect these obligations into something that actually runs. ## The compliance calendar is longer than most leaders realize The first place benefits administration tends to crack is the compliance calendar. COBRA notices must go out within 14 days of a qualifying event — terminations, reductions in hours, divorce, a dependent aging off coverage. ACA 1095-C forms must be generated for every full-time employee and filed with the IRS before the annual deadline. HIPAA notices, Summary Plan Description updates, and annual benefits disclosures must be distributed with documented acknowledgment trails. Each of these has a fixed regulatory deadline. Each requires access to employee status data, benefits eligibility records, and current plan information — data that typically lives across an HRIS, a benefits carrier portal, and one or more spreadsheets. And each needs a record of completion that would survive an audit. The cost of getting any of these wrong is not theoretical. COBRA non-compliance penalties at $110 per day per beneficiary accumulate quickly in high-turnover environments — 100 qualifying events per year in a 500-person company with 20% annual turnover means 100 opportunities for a missed notice. ACA reporting errors trigger IRS penalty notices months after the fact, when the original data is hard to reconstruct. Benefits acknowledgment gaps become liabilities at exactly the moment compliance teams have the least capacity to address them. Most HR teams manage this by building a shared compliance calendar, establishing template libraries for required notices, and relying on one or two people who know the process well enough to catch problems before they compound. That system works — until someone leaves, or the organization grows, or two deadlines land in the same week during open enrollment. ## Enrollment gaps create downstream compliance exposure Open enrollment is the most visible moment in benefits administration, but the upstream and downstream problems are where costs accumulate most quietly. On the upstream side: new hires frequently miss their enrollment windows. The window opens during onboarding, when a new employee is simultaneously learning their role, setting up systems access, and orienting to a new organization. Benefits enrollment — which requires comparing plan options, understanding cost tiers, and making decisions with long-term implications — is often the task that gets deferred. When it's deferred past the enrollment window, it typically can't be reopened outside of a qualifying event, leaving the employee without the coverage they intended to select. For HR teams, this creates follow-up work that should have been avoidable: tracking who missed their window, determining whether a qualifying event exists, escalating to benefits carriers to understand options, and communicating outcomes to employees who are already frustrated. Enterprises that have digitized onboarding workflows including benefits enrollment have seen new-hire onboarding complete up to 50% faster, per Beekeeper deployment benchmarks — a direct reflection of the relationship between enrollment clarity and administrative throughput. On the downstream side: employees who aren't enrolled correctly create complications at every subsequent qualifying event, at the next open enrollment, and at termination. COBRA eligibility depends on prior coverage. 1095-C accuracy depends on enrollment records being correct throughout the year. Every enrollment gap created in January surfaces in some form by December. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) documents how HR leaders are rethinking benefits enrollment as a system problem rather than a communication problem — the fix isn't more reminder emails, it's an enrollment workflow that connects to the broader employee lifecycle. ## The real cost of fragmented tools The underlying problem is fragmentation. Benefits administration at most organizations is spread across four or more systems: an HRIS for employee records, a carrier portal for plan administration, a compliance tool or manual process for regulatory notices, and a separate portal or email workflow for employee-facing enrollment. The connections between these systems are maintained by HR staff who know how to export from one, reformat for another, and manually reconcile when the numbers don't match. This fragmentation has a direct operational cost. IDC research puts the average employee time spent searching for information at 2.5 hours per day — and benefits-related questions, particularly during open enrollment, are a significant driver of that search time when the enrollment interface is disconnected from the tools employees use daily. Per Emergence Capital research, 80% of the global workforce is deskless — which means benefits enrollment tools that require desktop access or a corporate email address structurally exclude the majority of employees at many organizations. Persona-based routing for benefits communications — targeting by role, location, employment type, or preferred language — is now a baseline expectation in modern HR platforms, not a premium feature. Organizations whose benefits notices reach desk employees by email but don't reliably reach frontline workers have a different kind of compliance exposure than a missed deadline, but it compounds the same way. Fragmentation also creates institutional knowledge risk. The manual connections between disconnected benefits systems concentrate in a small number of people. When those people leave, the compliance calendar becomes a risk item rather than a managed process. When they're on vacation during a qualifying event, the 14-day COBRA clock keeps running. ## What breaking the pattern actually requires Most HR teams trying to reduce benefits administration burden start with process documentation — operations manuals for the compliance calendar, template libraries for required notices, SOPs for COBRA processing. These interventions are worth making, and they're worth making before any software evaluation rather than after. A practical first step: audit the current acknowledgment trail for the past 12 months. Can you produce a record showing which employees received and acknowledged each required benefits notice? If not, that's a known audit exposure — and it's one that can be quantified before the next open enrollment cycle. Identifying the gaps now, while there's time to address them, is different from discovering them during an audit. A compliance calendar with named owners for each deadline, a template library for required notices, and an SOP for COBRA processing are achievable with existing tools. These measures have a ceiling — manual operations at scale eventually miss something, and the compliance calendar doesn't get shorter as organizations grow — but they reduce the risk of a catastrophic failure while a longer-term solution is evaluated. [Gallup's 2026 State of the Global Workplace research](/articles/gallup-2026-state-of-the-global-workplace) found persistent employee disengagement across industries — and benefits experience, particularly friction around enrollment and compliance notice management, is consistently cited as an early signal of that disengagement. Employees who can't get clear answers about their benefits, or who discover enrollment gaps when they need coverage, are surfacing a problem that existed upstream. ## The ROI of systematizing benefits administration HR leaders evaluating whether to invest in benefits infrastructure typically face the same question: what does the current state actually cost, and what does fixing it return? The cost side is more quantifiable than it appears. COBRA compliance penalties are concrete. ACA penalty exposure varies by organization size and error type but arrives after the fact, when reconstruction is expensive. Beyond regulatory risk, the time cost of maintaining manual connections between fragmented benefits systems is measurable — the hours spent before each open enrollment reconciling enrollment data across disconnected systems is work that could be done differently. Workflow automation covering HR self-service processes — including benefits enrollment, routine approvals, and status notifications — can now be delivered through no-code tools without IT involvement, per Akumina and Beekeeper deployment benchmarks. That changes the implementation economics: organizations don't need a dedicated IT project to connect enrollment to onboarding or to automate COBRA notice generation. Deployment timelines measured in weeks rather than quarters are achievable when benefits administration is one module inside a [modern HCM](/solutions/modern-hcm) platform that integrates with scheduling, time tracking, and communications. The return side is harder to benchmark without organization-specific data. Enterprise deployments of unified HR and employee experience platforms have documented 90% frontline adoption within the first six months, per Unily deployment benchmarks — a figure that reflects whether employees actually engage with enrollment tools rather than ignoring them until a problem surfaces. The gap between that adoption rate and most organizations' current experience is largely a workflow design problem: employees don't use tools that are disconnected from the flow of their workday. ## What HR teams should do before the next enrollment cycle Three priorities for organizations heading into open enrollment with manual benefits administration processes: **Triage compliance exposure first.** Identify the three obligations with the closest deadlines and the highest penalty exposure — typically COBRA notice timing, ACA 1095-C accuracy, and benefits acknowledgment documentation. Confirm each has a named owner, a documented process, and a record-keeping method that would survive an audit. This is the minimum viable risk management posture achievable with existing tools. **Map the manual connections between systems.** List every place benefits data lives: HRIS, carrier portals, spreadsheets, email records. For each connection between systems, identify whether it's automated or maintained by someone who knows how. The manual connections are the fragility risk — knowing exactly where they are is the precondition for eliminating them. **Evaluate enrollment workflow from the new-hire's perspective.** Walk through the benefits enrollment experience as an employee who joined last week. How many systems do they need to access? What happens if they miss the window? If the answer involves more than one system and more than one manual follow-up, the enrollment workflow is creating downstream exposure that compounds over time. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how HR operations teams are systematizing benefits workflows across industries — including how organizations in high-turnover sectors have reduced compliance incident rates by treating benefits administration as infrastructure rather than a seasonal checklist. ## Why the same problems return every year Benefits administration breaks HR teams every year for a structural reason: compliance deadlines are fixed, employee events are unpredictable, and the tools at most organizations weren't designed to connect these two realities without human coordination filling the gaps. The teams that manage this most reliably have done one thing consistently: they've mapped the connections between obligations and systems, built named ownership for each compliance deadline, and replaced manual memory with documented processes. From there, every additional step toward systematization — connecting enrollment to onboarding, automating COBRA notice generation, routing compliance notices by employee persona — compounds the reliability of what's already working. The compliance calendar doesn't get shorter. The workforce doesn't stop having qualifying events. But the operational model for managing benefits doesn't have to stay where most organizations left it years ago. The cost of the current state is concrete: it's in the penalty exposure, the enrollment gaps, and the institutional knowledge that exists nowhere except in the heads of a few exhausted people. Recognizing those costs explicitly is how the conversation about fixing them actually starts. --- # The Hidden Cost of Small Interruptions in Frontline Operations **Author:** MangoApps Team **Published:** 2025-10-19 **Category:** news-and-updates There is a category of work that never shows up on anyone's job description but quietly consumes hours every week. It is the manager who spends Friday afternoon correcting timecards because three... # The Hidden Cost of Small Interruptions in Frontline Operations There is a category of work that never shows up on anyone's job description but quietly consumes hours every week. It is the manager who spends Friday afternoon correcting timecards because three employees forgot to clock out. The HR coordinator fielding the same question — "do I have enough PTO left for December?" — for the fifteenth time this month. The IT team lead manually sorting through a shared inbox, deciding which tickets belong to IT and which belong to HR. The support agent answering a password reset question that has been answered, in writing, a hundred times before. None of these moments feel like a problem. Each one takes only a few minutes. But they share a common structure: a piece of information or a routine action that should flow automatically, instead stopping to wait for a human. Multiplied across teams and weeks, this is where meaningful time disappears in frontline operations. This week's releases in MangoApps address exactly that category — not with a grand redesign, but with five targeted features that quietly remove common points of unnecessary friction. --- ## When Time Tracking Generates More Work Than It Saves Clocking in and out should be one of the simplest parts of running a shift-based operation. In practice, it creates a recurring cleanup problem. Employees forget to clock out. Payroll runs into records that need manual correction. Managers spend time at the end of the week reviewing entries that were fine except for a missing punch. The new [Automatic Clock-Out](https://www.mangoapps.com/solutions/time-attendance) feature in Time & Attendance addresses this without removing any human oversight. Managers configure a cutoff time after a shift ends. Before that cutoff, employees receive a reminder — a chance to clock out themselves. Anyone still clocked in after the cutoff is automatically closed out by the system. Those entries are then placed in a manager review queue so the records can be verified before payroll runs. The design choice here is worth noting. This is not a feature that assumes the automated record is correct. It assumes the opposite: that a machine-generated clock-out needs a human to confirm it. What it removes is the discovery problem — managers no longer have to hunt for unclosed entries. The review queue surfaces them. A related issue on the leave management side has also been addressed. Employees planning time off frequently need to know whether they will have enough leave accrued by a future date — information that involves pending requests, scheduled accruals, and already-approved time off. Without a direct way to check, they ask HR. The new [Time Off Balance Calculator](https://www.mangoapps.com/solutions/time-attendance) lets employees project their own balance forward to any date before they submit a request, including a check for any shift conflicts during the proposed leave period. The question that was going to HR can now be answered before anyone sends a message. Together, these two features address opposite ends of the same pattern: one catches an action that was missed, and one gives employees the information they needed before they had to ask for it. --- ## The Information That Was Always a Conversation Every team has a version of this interaction. A team lead arrives Monday morning, starts planning the day's work, and then has to find out who is actually there. This might mean checking a calendar, sending a message to HR, or just walking around. It is not a difficult problem — it is an information-access problem. The new [Who's Out Today](https://www.mangoapps.com/key-features/shift-distribution) dashboard widget puts that information on the first screen a user sees. It shows which teammates are absent on approved leave, with links through to the leave details. Nothing that was not already in the system — just made visible without a lookup. This kind of feature tends to be underestimated because it does not feel like a capability change. The data existed. What changes is the cost of accessing it. When that cost drops to zero, the behavior changes: team leads plan around absences at the start of the day instead of discovering them mid-morning. Tasks get reassigned proactively. The information flows to where it is needed without anyone having to carry it there. --- ## Self-Service Support That Actually Deflects Tickets Service Desk received two substantial updates this week, and they work together to address the support overhead problem from different directions. The first is [Support Teams & Routing Rules](https://www.mangoapps.com/directory/app/service-desk). Many organizations with a shared help desk inbox spend real time doing manual triage — reading each ticket and deciding which team should handle it. IT, HR, and facilities all get requests that belong to different people. Routing rules let admins define criteria — by category, department, or keyword — so incoming tickets are automatically assigned to the right team. The bottleneck of a shared inbox with someone deciding where each ticket goes disappears. The second is the [Service Desk Knowledge Base](https://www.mangoapps.com/apps/service-desk). This is a more significant addition: a built-in library where authors can write, version, and publish help articles through a structured approval workflow — draft, review, approval, publication. What makes it operationally meaningful is the deflection mechanic. When an employee opens a new ticket, related articles are surfaced automatically. If the article answers the question, the ticket never gets submitted. Deflection events are tracked, so admins can measure how much ticket volume the knowledge base is actually reducing. This is important because deflection is often claimed but rarely measured. Here, it is built into the system. The combination addresses both ends of the support lifecycle. Routing rules prevent tickets from landing in the wrong place. The knowledge base prevents common tickets from being submitted at all. Neither requires a fundamental change in how support teams operate — they just remove the parts that did not need to involve a person. --- ## The Pattern Behind the Releases There is a temptation to look at a week like this and describe it as "quality of life improvements." That framing undersells what is actually happening. The releases this week follow a consistent logic: identify a moment where a human is serving as an information relay or a manual trigger for a routine action, and remove the human from that specific moment. The manager reviewing forgotten clock-outs still reviews them — but now the system finds and surfaces them instead of requiring the manager to hunt. The employee who wants to know their leave balance can check it directly instead of asking. The support ticket that would have been submitted, answered, and closed now resolves itself at the point of contact. None of this replaces judgment. The clock-out review queue still requires a manager to verify entries. The knowledge base requires someone to write and maintain the articles. Routing rules require someone to define the criteria. What changes is where human attention is required — pulled toward decisions that actually need it, and away from repetitive information-handling that does not. For frontline operations, where managers and coordinators are already stretched, that distinction matters. The goal is not to automate everything — it is to make sure the things that require human attention are actually the things that need it. --- # MangoApps Recognized as a Visionary for the Third Consecutive Year in the 2025 Gartner® Magic Quadrant™ for Intranet Packaged Solutions **Author:** MangoApps **Published:** 2025-10-16 **Category:** press-release MangoApps, the AI-powered employee platform, today announced that it has been named as a Visionary for the third consecutive year in the 2025 Gartner® Magic Quadrant™ for Intranet Packaged Solutions. # MangoApps Recognized as a Visionary for the Third Consecutive Year in the 2025 Gartner® Magic Quadrant™ for Intranet Packaged Solutions **ISSAQUAH, Wash. — October 16, 2025** — MangoApps has been named a Visionary for the third consecutive year in the *2025 Gartner® Magic Quadrant™ for Intranet Packaged Solutions*. In the accompanying *2025 Gartner® Critical Capabilities for Intranet Packaged Solutions* report, MangoApps ranked among the top three vendors in all six evaluated use cases — a breadth of coverage that distinguishes platforms built to operate as a genuine single hub from those optimized for a narrower slice of the digital workplace. ## What the Visionary designation means in practice Gartner's Magic Quadrant places vendors across two axes: Ability to Execute and Completeness of Vision. Vendors in the Visionary quadrant score highly on vision — they have a differentiated, forward-looking direction for where the product category is heading — and are building toward the execution scale of Leaders. This is not a consolation placement. Visionaries are vendors that analysts believe are moving the market in a meaningful direction. For MangoApps, the Visionary designation reflects a product strategy built around a different population than the one most intranet platforms originally served. Traditional intranets were designed for office workers with corporate email addresses, VPN access, and a desktop browser. MangoApps built for a workforce where those assumptions don't hold — retail associates accessing shift updates on a personal phone, hospital aides without corporate email, manufacturing floor employees who work in areas with limited connectivity. Being named a Visionary for the third consecutive year means Gartner's analyst team has validated that direction across three annual evaluation cycles, not just once. Product strategy consistency, not just feature delivery, is what the repeated placement signals. It is also worth understanding what Gartner's Critical Capabilities report adds to the Magic Quadrant. While the quadrant provides a high-level view of market positioning, the Critical Capabilities report scores each vendor across specific deployment scenarios. For procurement teams, this is the more operationally useful document: it shows not just where a vendor falls on the quadrant, but how it performs in the use cases a given organization actually needs to address. ## How MangoApps ranked across all six critical capabilities MangoApps received the following scores out of 5.00 in the 2025 Critical Capabilities report, ranking among the top three vendors in each use case: - **Employee Engagement:** 3.46 / 5 - **Employee and Workplace Services:** 3.65 / 5 - **Knowledge Services:** 3.51 / 5 - **Work Management:** 3.49 / 5 - **Intelligent Assistance:** 3.60 / 5 - **Resource Portal:** 3.61 / 5 Most intranet platforms optimize for two or three of these use cases. Scoring in the top three across all six signals a platform that functions as a genuine single hub rather than a collection of capabilities that cover some scenarios well and others minimally. For organizations evaluating intranet platforms to consolidate communication, knowledge, and work management under a single interface, the breadth of the Critical Capabilities scores is the most direct evidence that consolidation is operationally feasible rather than aspirational. ## Why the intranet adoption gap makes this recognition matter more The problem MangoApps is being evaluated against is not a shortage of intranet technology. According to Social Edge Consulting, 91% of organizations already operate an intranet — yet only 13% of employees use it daily, and nearly a third never log in at all. SWOOP Analytics data shows the average employee spends six minutes per day using intranet tools — not because they don't need information, but because the tool doesn't surface it where they are when they need it. According to IDC, employees spend 2.5 hours per day searching for information they cannot find, representing more than 600 hours of lost productivity per employee per year. The intranet market's execution problem isn't shortage of product. It's that most platforms weren't built for the conditions under which most employees actually work. According to Emergence Capital, 80% of the global workforce is deskless. When a platform requires a desktop browser and VPN to access, the adoption gap is structural — not a training or change management problem that a better rollout plan can close. This is the context in which Gartner's Critical Capabilities scores carry weight. A vendor scoring in the top three for Employee Engagement in an evaluation that includes frontline and deskless criteria is delivering something different from a vendor that earns the same position in an evaluation where "employee engagement" means only what desk-based employees experience at headquarters. ## The frontline workforce at the center of MangoApps' product strategy MangoApps serves industries where most employees work outside corporate offices: retail, healthcare, manufacturing, and financial services. Organizations including PetSmart, TeamHealth, and AutoZone deploy the platform to bridge communication gaps between corporate operations and frontline teams. PetSmart achieved 4x engagement compared to industry standard through its branded MangoApps employee app. The result came from giving store associates mobile access to the same communication and knowledge tools available to corporate employees — not from building a separate, lower-capability "frontline app" disconnected from the main platform. OU Health reached 87% workforce engagement within a few months of deploying their branded MangoApps app, starting from a baseline where most frontline clinicians had no structured communication channel to corporate operations. TeamHealth, a national healthcare staffing organization, consolidated more than 200 systems into a single MangoApps mobile dashboard, giving clinicians across hundreds of care sites access to what they need from one interface rather than navigating a fragmented set of tools. These outcomes are relevant to the Gartner evaluation because the Critical Capabilities use cases — particularly Employee Engagement and Workplace Services — differentiate between platforms that extend to deskless workers and those that stop at the desk. The 3.46 and 3.65 scores in those categories reflect capability evaluated against real deployment conditions, not just office-centric use cases. For organizations in regulated industries, the platform meets the security requirements procurement and legal teams will require: SAML 2.0, OAuth 2.0, Active Directory integration, and HITRUST and SOC 2 certifications for healthcare and financial services deployments. Frontline employees can access the platform without a corporate email address or VPN, with role-based permissions controlling what each individual can see — closing the access gap that leaves most intranet investments underutilized for the majority of the workforce. ## What distinguished MangoApps in the 2025 product cycle "Our mission has always been to connect every employee to the people, tools, and information they need to succeed," said Anup Kejriwal, CEO and Founder of MangoApps. "We feel strongly that being recognized as a Visionary for three consecutive years validates our work to simplify the digital workplace and make it truly intelligent." 2025 included several product milestones that contributed to the Gartner assessment. MangoApps launched AI Hub, a unified AI interface giving employees a single point of access to AI-assisted work across the platform. The company also released AI-powered asset creation tools — giving administrators the ability to generate pages, forms, and structured content from a natural language prompt — and delivered new capabilities across communication and frontline work management. The Gartner recognition was one of several independent analyst and industry validations during the year. [MangoApps was also included in a leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms), adding a second concurrent analyst validation alongside the Gartner placement. Repeated recognition across multiple analyst organizations over consecutive years reflects a product executing consistently rather than cycling through short-term feature pushes in response to competitive pressure. ## How to use analyst research when evaluating intranet platforms The Gartner recognition provides a useful anchor for evaluation, but it should not be the only input. Here is how procurement and IT teams can use analyst research effectively when selecting an intranet platform. **Read the Critical Capabilities report alongside the Magic Quadrant.** The quadrant tells you where a vendor sits in the competitive landscape. The Critical Capabilities report tells you which use cases each vendor is strongest in — which is the question a specific organization is actually trying to answer. Map the six use case scores to your primary problem: if adoption is the challenge, prioritize Employee Engagement and Intelligent Assistance. If information findability is the issue, Knowledge Services is the most relevant dimension. If you are managing a mixed desk-and-frontline workforce, ask vendors to demonstrate their Critical Capabilities scores against frontline-specific deployment criteria. **Cross-reference with independent analyst benchmarks.** The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) benchmarks current platforms across adoption rates, usability, integration depth, and AI capability. It is a useful supplement to the Gartner reports when building evaluation criteria that will hold up under procurement review. **Request named customer references in your industry.** Generic case studies are less useful than references from organizations with a similar workforce structure. The Santee Cooper deployment documents how a utility workforce built connection across a geographically distributed organization with a large proportion of field and plant employees — see the [Santee Cooper case study](/resources/santee-cooper-case-study). For knowledge centralization in a distributed professional environment, the [American College of Radiology case study](/resources/case-study-american-college-radiology) covers how a healthcare professional association centralized communications and knowledge access across departments and locations. **Test frontline access conditions before completing the evaluation.** If any portion of your workforce is deskless, the evaluation should include a hands-on test of the mobile experience, offline capability, and what the access path looks like for employees without a corporate email address or device. This is the criterion where intranet platforms most frequently diverge between the sales conversation and actual deployment outcomes. --- *Source: Gartner Research, Magic Quadrant for Intranet Packaged Solutions, By Mike Gotta, Priyanka Singh, et al., October 2025.* *Gartner Research, Critical Capabilities for Intranet Packaged Solutions, By Mike Gotta, Priyanka Singh, et al., October 2025.* *GARTNER is a registered trademark and service mark of Gartner, Inc. and/or its affiliates in the U.S. and internationally, and MAGIC QUADRANT is a registered trademark of Gartner, Inc. and/or its affiliates and are used herein with permission. All rights reserved.* *Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.* --- # When AI Absorbs the Bureaucracy: Support Tickets Reimagined **Author:** MangoApps Team **Published:** 2025-10-12 **Category:** news-and-updates There is a familiar moment in every workplace. Something breaks — a handheld scanner stops responding, a laptop freezes mid-shift, a login stops working. # When AI Absorbs the Bureaucracy: Support Tickets Reimagined Priya manages IT support for a regional grocery chain — 22 stores, roughly 400 frontline employees, and a helpdesk ticket volume that has always seemed too low. Her team resolves everything that comes in. Response times are clean. SLAs are met on paper. And yet, when she walks the floor, she sees problems that should be tickets: scanners that warehouse workers have learned to reboot in a specific sequence, printers on the second floor that only work if you hit the side panel, point-of-sale terminals that freeze reliably on Tuesday mornings. None of it is in the system. The informal workarounds exist because the official process asks too much of workers who have too little time. Priya's team is not underperforming. It is flying blind. This is the actual problem that AI-assisted ticket creation solves. Not "the form takes too long." The form was never being used. ## The gap between reported problems and actual problems IT support metrics are built around what gets reported. Ticket volume, mean time to resolution, SLA compliance — these tell you about requests that made it into the system. They say nothing about requests that didn't. Per Emergence Capital, 80% of the global workforce is deskless. These workers interact with technology in conditions that were never factored into helpdesk software design: time pressure, physical movement, mobile devices, and environments where sitting down to navigate an unfamiliar web portal is simply not realistic. The predictable result is low ticket volume — not because problems are rare, but because reporting them is structurally difficult. Frontline employees on a given shift navigate an average of six to eight disconnected tools to complete daily work. Context-switching from a physical task to an IT portal, finding the right category, writing a description that will translate to someone who wasn't there — this workflow requires deliberate, focused attention that the physical context doesn't support. Workers adapt. They develop workarounds. They build informal escalation chains. The issues go unrecorded. That informal escalation chain — worker tells supervisor, supervisor tells manager, manager eventually tells IT — is not a communication failure. It is the system adapting to its own design constraints. The problem is that this chain strips context, creates delays, and makes patterns invisible. IT teams operating in this environment are chronically reactive not because they lack capability, but because they lack signal. ## Form interfaces were built for 20% of the workforce The helpdesk portal model is not broken. It works well for the knowledge workers it was designed for: desk-based, IT-provisioned, with administrative time built into their days. That population represents roughly 20% of the global workforce. For everyone else, the form interface fails at the architectural level. Requiring an employee to switch contexts, navigate an unfamiliar system, categorize their problem correctly, and submit a structured request — in the middle of a physical task, on a personal device, under time pressure — was never a realistic workflow. Employees recognized this years ago. They adapted by not using the system at all. This distinction matters because the assumption about the problem shapes the solution. If the problem is "forms are slow," the answer is a faster form. If the problem is "the form interface is architecturally wrong for the context of 80% of the workforce," the answer looks entirely different. No amount of UI refinement closes an architectural gap. The latent problem volume — issues that exist but never get reported — is the real operational risk. A device fleet accumulating unreported problems, managed by an IT team seeing only the filtered subset that made it through the reporting barrier, is a fleet that will fail on an unknown schedule in unknown ways. ## What changes when the interface disappears Conversational AI ticket creation works differently from adding a chat widget to a helpdesk portal. The distinction is where the ticket originates and, more importantly, whether the employee is making a deliberate decision to file one. In a portal-based system, the employee decides to file a ticket. They navigate to the support interface. They enter structured information. The decision point — "is this worth filing?" — is where most frontline reports are abandoned. Workers who have tried the portal and had poor experiences, or who have simply never been trained on it, stop making that decision. When AI assistance operates inside a communication tool employees are already using, the interaction changes structurally. An employee mentions in passing that the scanner on the loading dock isn't reading codes. The assistant recognizes this as a potential support issue, asks two or three clarifying questions in the same conversational thread, and creates the ticket in the background. The employee never navigated to a portal. They never decided whether to file. The behavioral barrier that suppressed ticket submission gets removed at the architecture level — not the UX level. Conversational ticket creation paired with HRIS-synced employee profiles can also auto-populate location, role, and device fields, eliminating the categorization burden that causes frontline workers to abandon forms even when they do attempt to use them. ## What higher ticket volume actually reveals When reporting friction drops, volume goes up — and that initial increase is operational signal, not noise. The informal workarounds Priya sees on her floor represent a class of issues that have been occurring on an unknown frequency for an unknown period. When those issues start reaching the ticketing system, three capabilities become available that weren't before. **Pattern detection.** Recurring problems that workers adapted to — the Tuesday morning POS freezes, the scanner with the specific reboot sequence — become visible in aggregate. Five tickets in two weeks from the same location indicate a systemic issue. One ticket each from five different locations indicates something environmental or fleet-wide. Neither pattern was detectable before because the reports didn't exist. **Proactive maintenance.** Visible patterns allow IT to address root causes rather than symptoms. This shift — from responding to what breaks to preventing the next failure — is the defining characteristic of mature service operations. It cannot happen without complete data. **SLA recalibration.** Resolution time metrics based on a filtered subset of actual tickets systematically understate real incident volume. When full problem volume is visible, SLA targets and staffing models can be calibrated against reality rather than against a partial picture. Organizations often discover their capacity assumptions were built for the wrong workload. Per IDC, employees spend 2.5 hours per day searching for information. The time lost to informal IT escalation — explaining a problem twice, waiting for it to travel up the management chain before reaching IT — is a portion of that figure that rarely gets measured because it never appears in the data. Making it visible is the first step to recovering it. For operations teams looking at how these workflow patterns scale, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) benchmarks AI-assisted operations across multiple industries. ## The metrics that matter when ticket volume changes IT organizations evaluating conversational ticket creation often default to measuring what they already track: resolution time, SLA compliance, satisfaction scores. These are lagging indicators of individual ticket handling. They don't capture what changes when ticket volume itself increases. The leading indicators worth tracking are different. **Reporting rate by location and role.** How many support issues are reported per employee per quarter, broken down by department and facility? An increase in this rate is the primary signal that the reporting barrier has dropped. A flat or declining rate from frontline workers signals that the barrier remains. **Pattern detection latency.** How many reporting periods pass before a recurring issue from the same location or device class appears in IT's pattern analysis? Reducing this from months to weeks is a direct output of increased frontline reporting, and it's the metric that most directly captures the shift from reactive to proactive operations. **Informal escalation frequency.** How often do manager-submitted tickets reference problems that workers raised informally but couldn't file themselves? This metric requires combining manager surveys with ticket metadata, but it surfaces the delta between the informal and formal systems — the gap that conversational AI is closing. No-code workflow automation can further accelerate the most common ticket categories — password resets, access requests, shift-related hardware swaps — by handling routine approvals without human triage, reducing mean time to resolution for the requests that represent the majority of frontline volume. That automation layer only becomes effective when the reporting layer is generating complete signal. ## Service operations as a strategic capability, not a UX fix The investment case for AI-assisted ticketing is often framed as an employee experience improvement. It is. But the operational value at scale is larger. Organizations managing large frontline workforces — logistics, healthcare, retail, manufacturing — are building the infrastructure to treat service operations as a capability center rather than a cost center. That shift requires complete operational visibility: the ability to see patterns before they escalate, calibrate SLAs against actual incident frequency, and distinguish a single-location anomaly from a fleet-wide failure. Conversational AI is how that visibility gets built for workforces where the formal reporting infrastructure has always failed. This is also where frontline engagement research connects to IT operations. As [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) documents, frontline employees report higher disconnection rates than any other workforce segment, and disconnected employees produce measurably lower output and are more likely to leave. An IT support model that functions for frontline workers is one component of the operational infrastructure that determines whether those workers feel supported by the organization or effectively on their own. Eight leading enterprise software vendors now explicitly position for the "service operations" intent cluster — SLA visibility, pattern detection, proactive maintenance, escalation management. The organizations building competitive advantage in this space are those that generate complete, unfiltered operational signal. Conversational AI, embedded in tools employees are already using, is the mechanism for generating that signal from workforces that formal ticketing was never designed to reach. ## From invisible backlog to operational clarity Priya's situation is not unusual. Most IT teams serving mixed workforces are making decisions about staffing levels, SLA targets, and system replacements against a filtered picture of what is actually happening. The formal data reflects the 20% of the workforce for whom the reporting infrastructure was designed. The other 80% have been working around it for years. Closing that gap does not require a new ticketing system. It requires removing the architectural barrier that has always stood between frontline workers and the reporting infrastructure. The investment question is not whether a better ticket interface is worth the cost. It is whether the hidden backlog — problems accumulating on an unknown schedule in unknown locations — represents an acceptable operational unknown. For most organizations running frontline workforces at scale, it doesn't. For teams thinking through where conversational support fits within a broader [workforce management](/solutions/workforce-management) strategy, the key question is whether the support infrastructure is genuinely accessible to the full workforce — or only to the portion that already knew how to use it. --- # MangoApps Launches Industry-First AI That Creates Pages, Forms, and More From a Prompt **Author:** MangoApps **Published:** 2025-09-17 **Category:** press-release MangoApps, the all-in-one AI-powered employee hub, today introduced its 19.1 release delivering industry-first AI that generates polished work assets from a simple prompt. The update also brings advanced tools for communication planning, insights, and employee engagement.  # MangoApps 19.1 Launches Industry-First AI That Generates Intranet Pages, Forms, and Trackers From a Single Prompt *ISSAQUAH, Wash. — September 17, 2025 — MangoApps, the [all-in-one AI-powered employee hub](/resources/how-an-employee-superapp-transforms-the-workplace), today released version 19.1, introducing what the company calls an industry first: AI that generates complete intranet pages, trackers, and forms directly from a plain-language prompt — with branding, layout, and permissions already applied.* The direct answer to what 19.1 delivers: admins can now type a description of the page, form, or tracker they need, and MangoApps AI produces a finished, governance-compliant asset in seconds rather than hours. That shift matters because employees already spend 2.5 hours per day searching for information (per IDC), and nearly a third of employees at organizations that run an intranet never log in to it at all (per Social Edge Consulting). The 19.1 release targets both problems at once — reducing the effort to create content and improving the quality of what employees find when they do show up. --- ## What the 19.1 Release Actually Includes The update spans four areas: AI-generated content and data tools, expanded AI integrations, smarter communications planning, and frontline workforce tools. ### 1. AI That Creates Intranet Pages, Trackers, and Forms From a Prompt This is the headline capability. Admins have historically spent hours building intranet pages, configuring tracker columns, and designing forms. MangoApps 19.1 removes that bottleneck: - **Pages** — AI generates text, images, and layouts automatically aligned to existing branding and templates. - **Trackers** — AI produces intelligent columns, values, and built-in forms based on a plain-language description. - **Forms** — AI auto-fills fields from uploaded PDFs or images, eliminating repetitive manual data entry. Critically, AI-generated assets inherit the platform's existing governance, permissions, and branding guardrails. An admin prompt does not bypass approval workflows or override role-based access — the AI works within the rules already configured, which addresses a common enterprise concern about ungoverned AI output. "AI has promised to make work easier, but too often it's just another chatbot," said Anup Kejriwal, CEO and Founder of MangoApps. "With this release, we're putting AI to work where it matters most — actually creating the assets that run the employee experience." ### 2. AI Integrations Across Daily Workflows Beyond content creation, 19.1 expands AI support across an employee's daily experience in cloud-based productivity applications: - **[New integrations with Microsoft Copilot, OpenAI assistants, and a MangoApps MCP server](/resources/mangoapps-microsoft-integration-guide)** extend organizational knowledge securely into broader AI ecosystems. - **Ask AI on Files and Trackers** delivers instant summaries, insights, and analysis without leaving the hub. - **Expanded multi-language previews and notifications** make posts accessible in employees' preferred languages. ### 3. Smarter Communications Planning and Control The 19.1 release strengthens how organizations plan and sequence communications — a gap that matters given that 91% of organizations operate an intranet (per Social Edge Consulting) yet average daily usage sits at just six minutes (per SWOOP Analytics). New capabilities include: - **Posts Planning Calendar** with drag-and-drop scheduling, overload warnings, and unplanned content tracking. - **[Enhanced digital signage](/solutions/workforce-management)** to broadcast updates into break rooms, lobbies, and factory floors. - **Critical Alerts with polls** for urgent updates that require confirmation or feedback. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how organizations are rethinking communication cadence for distributed and frontline teams — context that shapes why the planning calendar and alert features were prioritized in this release. ### 4. Frontline Workforce Tools and Analytics 80% of the global workforce is deskless (per Emergence Capital), and replacing a single frontline employee costs between $4,400 and $15,000 depending on role and industry. The 19.1 release treats frontline access as a first-class concern, not an afterthought: - **Upgraded analytics dashboards** track engagement, adoption, and culture in real time. - **New Workday widgets** deliver paychecks, benefits, time-off, and training from web or mobile — reducing the number of separate productivity apps employees need to open. - **Expanded Learn access** including Catalog, My Learning, and Instructor-Led Training widgets. The platform consolidation angle is significant. Organizations that have moved to a unified hub — rather than maintaining dozens of separate cloud-based productivity apps — report measurable reductions in tool-switching overhead. For context on what that consolidation looks like in practice, the [IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment](/resources/idc-marketscape-2024) benchmarks how vendors in this category handle platform unification. --- ## Frequently Asked Questions About MangoApps 19.1 ### Does AI-generated content bypass existing governance and security controls? No. Pages, forms, and trackers generated by AI in 19.1 inherit the platform's existing permission model, branding templates, and approval workflows. The AI acts as a content-generation layer on top of the governance structure already in place — it does not create assets that sit outside role-based access controls or bypass publishing approvals. Organizations evaluating AI tools for intranet use should verify this behavior with any vendor, as ungoverned AI output is a legitimate enterprise risk. ### How quickly can a team go from prompt to published intranet page? The 19.1 AI is designed to produce a draft asset — page, tracker, or form — in seconds from a plain-language prompt. The time from prompt to published depends on whether the organization requires an approval step before publishing, which is configurable. For teams with streamlined publishing permissions, the gap between "we need a page for this" and "the page is live" shrinks from hours to minutes. This is a meaningful shift for IT and HR teams that currently queue content requests and wait days for delivery. ### How does 19.1 address the frontline communication gap? The digital signage enhancements, Critical Alerts with polls, and Workday widgets in 19.1 are specifically designed for employees who do not sit at a desk. Digital signage pushes updates to physical screens in break rooms and on factory floors. Critical Alerts with polls allow managers to send urgent messages and require a response — confirming the message was received. Workday widgets surface HR data on mobile without requiring employees to navigate a separate application. For organizations managing large hourly or shift-based workforces, these tools reduce the reliance on supervisors as the sole communication channel. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines how frontline communication gaps translate into turnover and compliance risk. --- ## What This Means for HR and IT Teams The 19.1 release is most directly relevant to three groups: 1. **HR and internal communications teams** who currently spend significant time building and maintaining intranet content — the AI generation tools reduce that burden without requiring technical skills. 2. **IT administrators** who manage intranet governance — the fact that AI-generated assets inherit existing permissions means less manual review and fewer governance exceptions to manage. 3. **Operations and frontline managers** who need to reach employees who are not at a desk — the digital signage, alert, and mobile widget improvements in 19.1 address that gap directly. For organizations evaluating whether MangoApps fits their environment, the [MangoApps & Microsoft Integration Guide](/resources/mangoapps-microsoft-integration-guide) covers how the platform connects with existing Microsoft infrastructure, which is relevant given the new Copilot and MCP server integrations in 19.1. To explore the 19.1 release in detail or schedule a demo, visit MangoApps.com. --- # MangoApps Named a Leader in 2025 IDC MarketScape: Employee Experiences for Integrated Employee Workspaces **Author:** MangoApps **Published:** 2025-08-27 **Category:** press-release MangoApps, the all-in-one AI-powered employee hub, today announced it has been named a Leader in the IDC MarketScape: Worldwide Employee Experience for Integrated Employee Workspaces 2025 Vendor Assessment. # MangoApps Named a Leader in the 2025 IDC MarketScape for Integrated Employee Workspaces *Third consecutive IDC MarketScape Leader designation for MangoApps since 2021.* **ISSAQUAH, WA, August 26, 2025 —** MangoApps has been named a Leader in the IDC MarketScape: Worldwide Employee Experience for Integrated Employee Workspaces 2025 Vendor Assessment (doc #S53672525, July 2025). This is the third consecutive IDC MarketScape Leader designation for MangoApps, following recognition in the 2024 Experience-Centric Intelligent Digital Workspaces report and the 2021 Content Management Systems for Authenticated Digital Workspaces report. For HR leaders, IT decision-makers, and operations teams evaluating employee experience platforms, the central question is not whether MangoApps has won an award. It is whether the award reflects what actually happens once a contract is signed. The customer outcome data — 87% engagement rates, $20M cost avoidance, 200-system consolidations — makes that case more concretely than the designation itself. The argument worth making in 2025 is not that MangoApps is on an analyst's radar. It is that being named a Leader three consecutive times, across three different IDC assessments with different evaluation criteria, reflects a consistent ability to close the gap between having an employee platform and actually using it. ## What a MarketScape Leader designation actually tells a buyer The IDC MarketScape is not a pay-to-play ranking. Its scoring methodology weighs quantitative criteria — market share, customer growth, deployment scale — alongside qualitative criteria including product roadmap, customer satisfaction, ecosystem integrations, and go-to-market strategy. Vendors placed in the Leader zone demonstrate strength on both current capabilities and future market positioning. For the 2025 Integrated Employee Workspaces assessment, IDC evaluated how well platforms unify communications, knowledge management, operations workflows, and AI assistance into a single experience accessible to every employee. That last phrase is the structural challenge. Per Emergence Capital, 80% of the global workforce is deskless — warehouse operators, nurses, hotel housekeeping staff, retail associates who cover closing shifts without ever opening a company laptop. The assessment specifically probed whether each vendor's platform reaches that majority, not just the desk-based minority. MangoApps was assessed across all four dimensions and positioned in the Leader zone. The three consecutive designations matter because IDC's scoring is not static. Each MarketScape assessment uses updated criteria reflecting how the market has evolved. Being positioned as a Leader in 2021, 2024, and 2025 — across assessments with different scopes and different competitive fields — indicates that MangoApps has maintained competitive positioning while the evaluation standard itself has shifted. ## Customer outcomes that substantiate the designation A Leader designation is only meaningful if it translates into outcomes for real organizations. The data from MangoApps deployments makes a specific case: - **87% workforce engagement** achieved within months of launching a branded employee app in a large enterprise deployment. - **$20M in cost avoidance** captured by a single enterprise customer after consolidating fragmented tools onto the MangoApps platform. - **200+ disparate systems** consolidated into a single mobile dashboard in an enterprise-grade deployment, measurably reducing IT complexity and support overhead. - **90% frontline adoption** within the first six months in a large enterprise deployment where reaching deskless workers was the primary goal. These outcomes matter for the IDC assessment because IDC's qualitative scoring incorporates customer references and deployment evidence. They matter more for technology buyers because they describe what a successful deployment produces — not what the product can theoretically do under ideal conditions. The independent research on the underlying problem underlines how large the usage gap actually is. Employees spend an average of 2.5 hours per day searching for information, per IDC — time absorbed by fragmented systems requiring employees to context-switch between multiple platforms for basic tasks. While 91% of organizations operate an intranet, per Social Edge Consulting, only 13% of employees use it daily. Per SWOOP Analytics, the average daily time spent on intranet tools is six minutes. Platforms that close the gap between intranet availability and actual daily use deliver measurable productivity returns. The customer outcomes from MangoApps deployments show that gap is closeable. ## Platform characteristics IDC assessed "We believe being named a Leader once again by the IDC MarketScape is a validation of our mission to simplify work for every employee," said Anup Kejriwal, CEO and Founder of MangoApps. "Our singular focus on unifying communications, knowledge, operations, and AI into one experience is paying dividends for our customers and their employees." IDC's assessment aligned with platform characteristics that MangoApps customers consistently identify as differentiators: **Unified platform approach.** Intranet, collaboration, training, operations, and AI are delivered in one product suite with one support team — eliminating the integration overhead of assembling point solutions and the support fragmentation that follows when individual components come from different vendors. **Fast deployment.** MangoApps customers reach full deployment without the multi-month implementation cycles common in enterprise software. Speed-to-value matters specifically for HR and IT teams who need to demonstrate ROI within a fiscal year, not across two or three. **Frontline-first design.** Per Emergence Capital, 80% of the global workforce is deskless. MangoApps is built to serve that majority, not adapt a desk-worker platform into an afterthought mobile experience. Frontline and deskless workers get equivalent access to knowledge, communications, and tools — and a familiar, social-style interface that maintains engagement without extensive training. **Enterprise security and governance.** MangoApps supports SAML 2.0, OAuth 2.0, LDAP, and custom SSO, meeting the security and compliance requirements that enterprise IT and security teams require before approving a platform at scale. **AI built into the daily workflow.** AI assistance is embedded in the same hub where employees already work, not siloed in a separate tool requiring additional logins. For [large frontline or deskless workforces](/solutions/workforce-management), AI that requires a desktop browser is effectively unavailable to the employees who need it most. ## How this fits the broader independent analyst picture The 2025 IDC MarketScape Leader designation is part of a consistent pattern of independent analyst recognition. MangoApps has also been [included in a leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms), with assessments across firms using different methodologies — IDC's quantitative-qualitative scoring, Forrester's Wave framework, and ClearBox Consulting's practitioner-focused evaluation. What makes the IDC MarketScape specifically useful for enterprise technology decisions is its explicit two-axis scoring: current capabilities and future positioning are evaluated separately and combined. Vendors who score well today but have a weak product roadmap land in the Contender zone, not the Leader zone. MangoApps' three consecutive Leader designations across different IDC reports reflect consistent positioning rather than a single strong evaluation cycle. ## Evaluating fit before you decide The IDC MarketScape covers a broad market. Here is a more specific evaluation framework based on the deployment profiles IDC assessed: **Strong fit.** Midsize to large enterprises (500–50,000+ employees) with a mix of desk and frontline workers. Organizations with fragmented productivity apps that need consolidation into a single mobile dashboard. HR and IT teams that need fast deployment and high frontline adoption without a large implementation budget. Industries with compliance and governance requirements — financial services, healthcare, retail — where enterprise SSO and audit trails are non-negotiable. **Evaluate carefully.** Very small organizations (under 200 employees) where a full enterprise platform may exceed current needs. Organizations already deeply embedded in a Microsoft 365 environment should evaluate integration depth before committing — the [MangoApps & Microsoft Integration Guide](/resources/mangoapps-microsoft-integration-guide) covers the specific integration architecture in detail. **Questions to bring into the vendor evaluation:** - What is the average time to full deployment for an organization at our employee count and industry? Ask for specifics, not a range. - How does the platform serve frontline workers who don't have corporate email addresses or VPN access? - What does the security and governance model look like for regulated industries — what certifications are current, and what is the compliance roadmap? - How is AI surfaced to employees — embedded in daily workflow, or requiring a separate tool and login? - What does the support model look like 18 months post-deployment, when the implementation team has moved on? These questions apply across vendors in this category. The answers should be in writing, not demonstrated only in controlled demo conditions. ## What to do after reading an analyst report The IDC MarketScape Leader designation answers one question for technology buyers: is MangoApps a serious contender at the enterprise level? The answer, confirmed for a third consecutive time by an independent assessment, is yes. It does not answer whether MangoApps is the right fit for your specific workforce composition, IT constraints, integration requirements, or budget. Those questions require structured evaluation, not award citation. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) provides context on what leading organizations are prioritizing as they evaluate employee experience platforms for distributed and frontline-heavy workforces. Per the Gallup 2026 State of the Global Workplace, employees who feel their work is recognized and who have visibility into how their daily tasks connect to organizational goals are substantially more engaged — and substantially less likely to leave. An employee experience platform that doesn't deliver on both counts for every employee, including the 80% who are deskless, is solving a subset of the problem. The customer outcomes cited above describe what solving the full problem looks like: 87% engagement within months of launch, $20M in cost avoidance, 200 systems consolidated into one dashboard that employees actually open daily rather than six minutes a week. The IDC Leader designation reflects that those outcomes are achievable. The evaluation conversation is about whether they are achievable in your organization. --- ## About MangoApps MangoApps is an all-in-one AI-powered employee hub that combines communication, collaboration, training, and knowledge-sharing in one experience. Built for both desk and frontline workers, it keeps everyone connected, informed, and productive. Learn more at www.mangoapps.com. --- # MangoApps Wins Gold Stevie® Award in 2025 International Business Awards® for Collaboration/Social Networking Solution **Author:** MangoApps **Published:** 2025-08-13 **Category:** press-release MangoApps has been named the Gold Stevie® Award winner in the Collaboration/Social Networking Solution category of The 22nd Annual International Business Awards®. MangoApps was recognized for its industry-leading employee experience platform, which serves as a modern intranet and unified hub for employee communications, collaboration, and engagement. # MangoApps Wins Gold Stevie® Award in 2025 International Business Awards® for Collaboration/Social Networking Solution *Winners to Be Celebrated During Event in Lisbon on 10 October* **ISSAQUAH, WA – August 13, 2025** — MangoApps has been named the Gold Stevie® Award winner in the *Collaboration/Social Networking Solution* category of The 22nd Annual International Business Awards® (IBAs). The recognition reflects the platform's measurable impact on employee engagement, intranet adoption, and frontline communication for organizations across industries. The IBAs are the world's premier business awards program. The 2025 competition received nominations from organizations in 78 nations and territories, with more than 3,800 entries across categories. Winners were determined by the average scores of more than 250 executives worldwide who participated in the judging process from May through July. ## What MangoApps Was Recognized For MangoApps was honored for its employee experience platform, which functions as a [modern intranet and unified hub for employee communications, collaboration, and engagement](/solutions/employee-app). The platform is built to address a persistent gap in how organizations reach their workforce: according to Emergence Capital, 80% of the global workforce is deskless, yet most enterprise software is designed for desk-based employees. The intranet adoption problem is equally well-documented. Per Social Edge Consulting, 91% of organizations operate an intranet — but nearly a third of employees never log in, and only 13% use one daily. SWOOP Analytics found the average employee spends just six minutes per day in intranet tools, while IDC estimates employees lose 2.5 hours per day searching for information they cannot easily find. MangoApps was built to close that gap. Judges praised MangoApps for its "clear focus on solving both digital overload and digital exclusion" and for delivering "a modern, intuitive platform that demonstrates measurable improvements in productivity and employee engagement." ## Customer Outcomes That Substantiate the Award The recognition is grounded in documented customer results. Named customers across healthcare, retail, manufacturing, finance, and education have achieved employee engagement rates of 80–90% using the platform: - **OU Health** reached 87% workforce engagement within a few months of launching their branded app on MangoApps. - **PetSmart** achieved 4x the industry-standard engagement rate using MangoApps' branded employee app. - **TeamHealth** consolidated more than 200 systems into a single mobile dashboard, directly quantifying the platform's ability to reduce app sprawl. - **AutoZone**, **Nicklaus Children's Hospital**, **Caliber Collision**, and **YMCA of the USA** are among the enterprises that have used the platform to close communication gaps for hard-to-reach frontline staff. Those outcomes matter beyond recognition. Frontline employee replacement costs range from $4,400 to $15,000 per worker, according to industry data cited in MangoApps' own product research — making disconnected communication a quantifiable retention risk, not just an operational inconvenience. ## Why the Platform Is Built the Way It Is MangoApps connects desk-based and frontline employees in a single, mobile-friendly workspace. Core capabilities include real-time chat, file sharing, project management, task tracking, knowledge libraries, and AI-powered assistance. The AI layer is designed for enterprise governance: the platform supports multiple AI engines — including OpenAI, Gemini, Anthropic, and Azure OpenAI — so organizations can apply consistent governance policies across AI interactions rather than relying on a single vendor's model. The platform also meets enterprise security requirements, supporting SAML 2.0, OAuth 2.0, and single sign-on (SSO) — credentials that matter when IT and security teams evaluate employee engagement software at scale. "This Gold Stevie is a testament to our team's relentless commitment to making the digital workplace truly work for everyone," said Anup Kejriwal, CEO of MangoApps. "Our platform is designed to connect people, knowledge, and tools in one place, and this recognition validates the impact we're having for organizations worldwide. I'm incredibly proud of our team and grateful to our customers who inspire us to keep raising the bar." This win follows MangoApps' recognition as a finalist in the *Platforms & Tech* category of the Ragan Zenith Awards. For a broader view of how MangoApps compares across the intranet and employee experience platform landscape, see [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report). ## What This Means for Organizations Evaluating Intranet Platforms For HR, IT, and communications leaders currently assessing employee engagement software or replacing a legacy intranet, the Stevie Award provides third-party validation of platform quality — but the customer metrics above are the more actionable signal. Organizations that have struggled with low intranet adoption, fragmented tools, or frontline employees who are difficult to reach consistently report three outcomes after deploying MangoApps: 1. **Higher daily active usage** compared to traditional intranet tools, driven by a mobile-first design that meets frontline workers where they already are. 2. **Reduced time spent searching for information**, addressing the 2.5-hour daily loss IDC attributes to poor information access. 3. **Consolidated toolsets**, replacing multiple point solutions with a single platform — as TeamHealth's 200-system consolidation illustrates. For organizations in regulated or complex industries, the [MangoApps employee directory and workforce management features](/key-features/employee-directory) also support compliance and operational visibility at scale. ## Next Steps Details about The International Business Awards and the full list of Stevie Award winners are available at www.StevieAwards.com/IBA. To understand how MangoApps approaches the specific challenges of internal communications strategy, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the patterns driving platform decisions at enterprise organizations this year. For a broader look at workforce operations, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides additional context on where employee engagement and intranet investments are heading. --- # MangoApps Named Finalist in Ragan’s Zenith Awards for Platforms & Tech **Author:** MangoApps **Published:** 2025-08-08 **Category:** press-release MangoApps has been named a finalist in the Platforms & Tech category of the 2025 Ragan Zenith Awards, recognizing innovative technology platforms that strengthen communication strategies and outcomes. The honor highlights MangoApps’ commitment to unifying the digital workplace for every employee—whether on the frontlines or behind a desk—through a single, secure hub combining intranet, mobile access, workflows, and AI. Winners will be announced at the Zenith Awards Gala during Ragan’s Communications Week, November 12–15, 2025, in Austin, Texas. We're thrilled to share that MangoApps has been named a **Finalist** in the **Platforms & Tech** category of the prestigious Ragan Zenith Awards. This category honors **innovative technology platforms that support communication strategies and objectives**—and we're proud to be recognized among the very best. ## Why This Matters The Zenith Awards celebrate the peak of communications excellence, spotlighting organizations and platforms that raise the bar for how people connect, collaborate, and share knowledge. Being named a finalist affirms what our customers have been telling us for years: MangoApps is more than software—it's the foundation for a unified, intelligent, and inclusive digital workplace, or intranet, built for every kind of employee. For more than 15 years, we've stayed true to our mission: **to give every employee—whether behind a desk or on the frontlines—the tools, knowledge, and support they need to stay connected, informed, and empowered**. While many workplace technologies focus on one segment of the workforce, MangoApps was built to bring everyone together in one hub. That matters more than ever given that 80% of the global workforce is deskless, per Emergence Capital, yet most intranet platforms were designed primarily for desk-based employees. From frontline store associates at PetSmart, to clinicians at [OU Health](/industries/healthcare), to event staff at the Kansas City Chiefs, our platform consistently delivers adoption rates above 80–90%. That's not just engagement—it's proof that when you design for everyone, you create value for the entire organization. ## The Platform & Tech That Got Us Here Our finalist recognition is built on a foundation of continuous innovation and a deep commitment to customer success: - **One Unified Hub** that combines modern [intranet capabilities, a frontline employee app](/solutions/employee-app), operational workflows, and AI services. - **Contextual, persona-driven AI** that integrates with multiple LLMs and company knowledge to give employees fast, relevant answers—addressing a real gap: only 22% of company intranets currently deliver personalized content, per the State of the Digital Workplace & Modern Intranet 2024 (cited by Akumina). - **Enterprise-grade security** including HITRUST, FedRAMP, ISO-27001, and SOC 2 Type II compliance—a stronger certification stack than most intranet vendors carry. - **Customer-funded innovation**, with four major releases each year—driven by direct customer feedback rather than investor pressure. This approach has helped organizations consolidate dozens (sometimes hundreds) of fragmented systems into one trusted platform, saving time, reducing costs, and making work simpler for everyone. The urgency is real: employees spend an average of 2.5 hours per day searching for information, per IDC, and per Social Edge Consulting, nearly a third of employees never log in to their intranet at all—even though 91% of organizations operate one. MangoApps is built to close that gap. With more than 1 million users worldwide and a customer NPS of 78, the platform's scale and satisfaction scores reflect what the Ragan judges recognized: consistent, measurable impact on [employee communications](/solutions/employee-communications) across industries. ## Looking Ahead to the Gala The winners will be announced at the **Zenith Awards Gala** during Ragan's Communications Week, **November 12–15, 2025 in Austin, Texas**. It's the biggest week of the year for communicators, and we're honored to be in such great company. We want to thank our incredible customers, who continually challenge and inspire us, and our team at MangoApps, whose dedication turns big ideas into everyday reality for millions of employees worldwide. Whether or not we bring home the trophy, being recognized as a finalist is a moment worth celebrating—and a reminder that our mission is resonating where it matters most: in the workplace. ## What the Ragan Zenith Criteria Mean for Customers The Platforms & Tech category evaluates entrants on how effectively a technology platform enables communication strategy—not just feature counts. Judges assess real-world adoption, measurable employee engagement outcomes, and the platform's ability to serve diverse workforce segments. MangoApps was evaluated on deployments spanning healthcare, retail, and live events, where the definition of intranet success extends well beyond page views to include frontline task completion, knowledge access speed, and cross-location alignment. For customers, this recognition signals that the platform they've chosen is being validated by an independent communications industry body—not just by vendor marketing. If you want to see how MangoApps performs against the broader intranet and employee experience platform landscape, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent analyst context. ## What This Recognition Means Going Forward Award recognition is a milestone, not a destination. The problems that earned this nomination—fragmented tools, unreachable frontline workers, intranet platforms that average only six minutes of daily use per SWOOP Analytics—are still the problems MangoApps is built to solve every day. For organizations evaluating intranet and employee experience platforms right now, the Ragan finalist status is one signal among several. We'd point you to the [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) and the [MangoApps Wins Gold in Reworked's 2026 IMPACT Awards for Excellence](/articles/mangoapps-gold-reworked-2026-impact-awards) for additional third-party validation. And if you're thinking about what a modern intranet strategy looks like in practice, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) is a practical starting point. The bottom line: if your organization is still running on a fragmented stack—or on an intranet that most employees ignore—this is the moment to ask whether your platform was built for everyone, or just for the people already at a desk. --- # 25 Intranet Platforms Worth Evaluating in 2026: A Frontline-First Buyer's Guide **Author:** Andy Tolton **Published:** 2025-08-05 **Category:** comparisons A curated guide to 25 intranet platforms evaluated for frontline and desk-based workforces, now with UK enterprise criteria, SharePoint-replacement options, and platforms that reach staff without corporate email. > **Quick answer:** This guide compares 25 intranet platforms through a frontline-first lens: mobile access, sign-in without corporate email, AI search, operational depth, security, and adoption support. MangoApps leads for organisations that need one platform for frontline and desk employees; Microsoft SharePoint and Viva suit Microsoft 365-standardised enterprises; Staffbase, Unily, Interact, and Oak Engage are frequently shortlisted by large UK enterprises. A UK section adds the governance, data-residency, and SharePoint-replacement criteria UK procurement teams ask about. ## A Frontline-First Guide to the Best Intranet Platforms in 2026 Most intranet comparison guides are written for knowledge workers. This one isn't. The 25 platforms below were evaluated through a frontline-first lens — meaning mobile access, deskless usability, AI-powered knowledge retrieval, and operational depth all carried significant weight in the rankings. That doesn't make this guide irrelevant if your workforce skews desk-based. The criteria that make a platform work for frontline workers — fast mobile access, intuitive UX, strong adoption support, minimal IT dependency — are exactly the criteria that predict whether any employee actually uses the platform. A tool that works for your most under-resourced users will work for everyone else. We've drawn on public analyst research, customer reviews, and product documentation to represent each platform fairly. For a fully independent assessment, the ClearBox Intranet and EX Platforms Report is linked in the resources section at the bottom. ## Quick Reference: 25 Intranet Platforms at a Glance *Sign-in statements for third-party vendors are vendor-stated from public documentation as of September 2026 and not independently verified by MangoApps. "Not published" means the vendor's public pages we reviewed did not disclose a no-email sign-in method.* | Platform | Category | Best For | Ideal Company Size Sign-in without corporate email | |----------|----------|----------|--------------------|------------------| | [MangoApps](https://www.mangoapps.com) | Unified Workforce Platform | Frontline + desk workers in one platform | 1,000–100,000+ employees | Yes | | [Akumina](https://www.akumina.com/) | Employee Experience Platform | Complex Microsoft 365 enterprises | Large global enterprises | Not published | | [Appspace](https://www.appspace.com/) | Workplace Experience | Hybrid workplace + digital signage | Mid to large enterprises | Not published | | [Axero](https://axerosolutions.com/) | Social Intranet | All-in-one collab with social features | Mid-sized organizations | Not published | | [Blink](https://www.joinblink.com/) | Frontline Employee App | Deskless workforce communications | Frontline-heavy orgs | Yes | | [Fellow Intranet](https://www.fellowdigitals.com/en/fellow-intranet/) | Frontline Communications | Distributed frontline with microlearning | Mid-sized organizations | Yes (code access) | | [Firstup](https://firstup.io/) | Internal Communications | Multi-channel comms at enterprise scale | 2,500+ employees | Partial | | [Flip](https://www.getflip.com/) | Frontline Employee App | Mobile-first frontline engagement | Medium to large enterprises | Yes | | [Fresh](https://freshintranet.com/) | SharePoint Intranet-in-a-Box | Microsoft 365-first organizations | Mid to large enterprises | Limited (Teams or browser) | | [Haiilo](https://www.haiilo.com/) | Social Intranet | Social-first engagement and comms | 1,000–50,000 employees | Partial (MDM deployment) | | [Igloo Software](https://www.igloosoftware.com/) | SaaS Intranet | Mid-market core intranet needs | 500–20,000+ employees | Not published | | [Interact](https://www.interactsoftware.com/) | Intranet Platform | Content publishing + multi-channel comms | 2,500+ employees | Partial | | [Involv](https://cognit.be/en/involv) | SharePoint Intranet-in-a-Box | Microsoft 365 orgs wanting better UX | Mid to large enterprises | Limited | | [LumApps](https://www.lumapps.com/) | Employee Communications | Communication-first with broad integrations | 2,000+ employees | Partial (Beekeeper: Yes) | | [Microsoft SharePoint & Viva](https://www.microsoft.com/en-us/microsoft-365/sharepoint/collaboration) | Intranet + EX Platform | Microsoft 365-standardized enterprises | Any size (IT-resourced) | Partial (Teams and licensing) | | [Oak Engage](https://www.oak.com/) | Intranet Platform | Usability + frontline-friendly features | 1,000–80,000 employees | Yes | | [Omnia Intranet](https://www.omniaintranet.com/en) | SharePoint Intranet Platform | Rich personalization with Microsoft backbone | Medium to large enterprises | Yes (QR self-registration) | | [Poppulo](https://www.poppulo.com/) | Employee Communications | Campaign-based multi-channel comms | 20,000–50,000+ employees | Not published | | [Powell Intranet](https://powell-software.com/) | SharePoint Intranet Platform | Microsoft-savvy teams needing SharePoint UX lift | Mid to large enterprises | Limited | | [Simpplr](https://www.simpplr.com/) | SaaS Intranet | Fast deployment, low IT overhead | Mid-sized organizations | Partial | | [Sociabble](https://www.sociabble.com/) | Employee Communications | Frontline engagement + employee advocacy | Large enterprises | Partial | | [Staffbase](https://staffbase.com/) | Intranet + Comms Platform | Multi-channel comms with Microsoft 365 depth | Medium to large enterprises | Partial | | [ThoughtFarmer](https://www.thoughtfarmer.com/) | Intranet Platform | Usability-first with guided implementation | Under 5,000 employees | Not published | | [Unily](https://www.unily.com/) | Employee Experience Platform | Complex global enterprises needing deep governance | 10,000+ employees | Partial | | [Workvivo](https://www.workvivo.com/) | Social Intranet | Culture + engagement for Zoom-centric orgs | Large enterprises | Partial | ## How to Evaluate Any Intranet Platform on This List The eight criteria below reflect what consistently separates high-adoption intranet deployments from failed ones — based on patterns across analyst research, customer reviews, and real-world implementations. They're not unique to MangoApps' perspective; you'll find similar frameworks in the Gartner Magic Quadrant evaluation methodology and the ClearBox scoring model. Where the frontline lens matters: if a significant portion of your workforce doesn't sit at a desk, these criteria carry different weight. Mobile access and frontline enablement become eliminators, not just differentiators — a platform that scores well on knowledge management but requires a company email to log in isn't a realistic option for a manufacturing floor or a retail store. We've called that out explicitly in each criterion below. If you're building a formal shortlist, our [2026 Intranet Buyer's Guide for a Frontline Workforce](https://www.mangoapps.com/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) includes an editable version of this scorecard along with RFP templates and implementation checklists — useful whether or not MangoApps ends up on your list. - **Mobile-First, Easy Access:** Platforms must prioritize [frontline usability](https://www.mangoapps.com/mobile) as a core function in the digital workplace. That means robust iOS/Android apps, intuitive navigation, offline access, and fast performance even on low-bandwidth networks. SSO and push notifications are baseline requirements, and for multi-site employers in retail, health, hospitality, and logistics, sign-in that does not depend on a corporate email account is the eliminator; see [which platforms support employees without corporate email](#which-modern-intranet-platforms-best-support-employees-without-corporate-email-access) below. MangoApps, Blink, and Flip were purpose-built for this use case and support access without a company email. SharePoint-native options like Fresh, Involv, and Powell depend on Microsoft infrastructure and are better suited to desk-centric environments. - **Communication & Messaging:** We looked for strong top-down [communication tools](https://www.mangoapps.com/solutions/employee-communications) — targeted announcements, critical alerts — as well as team-level messaging like group chat and direct messages. Platforms that support multilingual posts, read receipts, or digital signage scored higher. Firstup, Staffbase, and Sociabble lead on multi-channel communications reach; MangoApps and Flip combine that reach with operational workflows in the same platform. - **Knowledge Access & AI Search:** Frontline workers need [instant access to SOPs, policy documents, and job-critical info](https://www.mangoapps.com/solutions/knowledge-management). We prioritized platforms with intelligent, AI-powered search — not just a search bar — including federated search across repositories like Microsoft 365 or Google Drive. MangoApps, Simpplr, and Unily are among the stronger performers here. Platforms like Poppulo and Sociabble are built for content delivery, not knowledge retrieval, and will require third-party tools to fill this gap. - **Training & Microlearning:** [Support for onboarding, compliance training, and in-the-flow learning](https://www.mangoapps.com/solutions/learning-management) is a major differentiator. We looked for microlearning modules, LMS integration, manager-assigned learning paths, and mobile-optimized delivery. MangoApps and Fellow Intranet both offer native training tools built for frontline delivery. Most communications-focused platforms — Firstup, Staffbase, Poppulo — require a third-party LMS integration to cover this criterion. - **Feedback, Recognition & Engagement Tools:** [Two-way communication matters](https://www.mangoapps.com/solutions/employee-engagement). We evaluated pulse surveys, suggestion boxes, peer recognition, and social engagement features like comments and likes — plus analytics around participation. MangoApps, Haiilo, and Workvivo all score well here. Platforms like Poppulo and Firstup are stronger at broadcasting than listening, with more limited native tools for two-way engagement. - **Integrations & Workflow Support:** We assessed how well each platform [integrates](https://www.mangoapps.com/integrations) with core enterprise systems — HRIS, scheduling tools, payroll, file storage — and whether it enables digital workflows or form submissions directly from mobile. MangoApps (200+ native integrations, no-code workflow builder) and LumApps (100+ productized integrations) lead on breadth. SharePoint-based platforms rely on Power Automate for workflow depth, which adds IT dependency and implementation complexity. - **Security & Compliance:** [Security and compliance](https://www.mangoapps.com/security-compliance) are critical for regulated industries. We looked for SOC 2, ISO 27001, and HITRUST certifications, along with data encryption, audit logs, role-based access, and mobile device protections like remote wipe and session management. UK enterprises should add Cyber Essentials Plus, UK GDPR and Data Protection Act 2018 documentation, a written residency statement, and an ICO-recognised transfer mechanism to the check; see the [UK criteria](#what-do-large-uk-enterprises-need-in-an-intranet-platform-10-evaluation-criteria) below. MangoApps holds all three; among the platforms compared here, none we reviewed publishes a HITRUST certification on its public security pages (vendor pages as of September 2026), a meaningful differentiator for healthcare, financial services, and other regulated sectors where HITRUST is a procurement requirement. - **User Experience & Adoption Support:** A platform only [delivers value if employees use it](https://www.mangoapps.com/success-services). We looked at interface quality, onboarding simplicity, multi-language support, and whether vendors offer adoption playbooks, customer success resources, or role-specific dashboards. MangoApps backs this with an [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee) of 90%+ active adoption within 90 days, the only vendor on this list to publish one. SharePoint + Viva and Akumina, by contrast, place significant responsibility on internal IT teams or implementation partners to drive adoption outcomes. ### How the Framework Plays Out: Three Platforms Compared To show how these criteria differentiate vendors in practice, here's how three platforms from this list score against the frontline-first framework — representing three common buyer profiles. | Criterion | MangoApps | Staffbase | SharePoint + Viva | |---|---|---|---| | Mobile-First / Frontline Access | ✅ Strong — purpose-built frontline app, no email required | ✅ Strong — mobile-first origins, solid app | ⚠️ Partial — depends on Teams and browser access | | Communication & Messaging | ✅ Strong — multi-channel, targeted, multilingual | ✅ Strong — best-in-class multi-channel publishing | ⚠️ Partial — strong with M365 but requires configuration | | Knowledge Access & AI Search | ✅ Strong — federated AI search across integrated systems | ⚠️ Partial — improving but not a core strength | ⚠️ Partial — Viva Topics helps but requires M365 expertise | | Training & Microlearning | ✅ Strong — native LMS, mobile-optimized, manager-assigned paths | ❌ Limited — requires third-party LMS integration | ⚠️ Partial — Viva Learning available but separately licensed | | Feedback, Recognition & Engagement | ✅ Strong — surveys, recognition, social, participation analytics | ✅ Strong — engagement tools built in | ⚠️ Partial — Viva Engage covers some; recognition requires add-ons | | Integrations & Workflow Support | ✅ Strong — 200+ native integrations, no-code workflow builder | ⚠️ Partial — solid M365 depth, limited outside Microsoft | ⚠️ Partial — Power Automate enables workflows but requires IT | | Security & Compliance | ✅ Strong — HITRUST CSF, SOC 2 Type II, ISO 27001 (no other platform reviewed publishes HITRUST) | ⚠️ Partial — SOC 2 and ISO 27001; no HITRUST | ✅ Strong — enterprise-grade M365 security stack | | UX & Adoption Support | ✅ Strong — Adoption Guarantee (90%+ in 90 days), customer success included | ✅ Strong — onboarding and CS included in pricing | ⚠️ Partial — highly dependent on internal IT and implementation partner | **What this shows:** A communications-first platform like Staffbase performs well on messaging and engagement but leaves gaps in training, workflow depth, and compliance certifications — making it a strong fit for comms teams but a harder case for HR and operations buyers. SharePoint + Viva is powerful for organizations already standardized on M365, but the frontline experience, microlearning, and adoption support all depend heavily on how well it's implemented. MangoApps is the only platform in this comparison that covers all eight criteria natively — which is why it consistently performs well for organizations that need a single platform to serve both frontline and desk-based employees. For a full vendor-by-vendor comparison across all 25 platforms, download the [2026 Intranet Buyer's Guide](https://www.mangoapps.com/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026), which includes an editable scorecard you can customize for your own evaluation. ## What do large UK enterprises need in an intranet platform? 10 evaluation criteria For a UK enterprise, the intranet decision is a governance and security decision before it is a communications one. The ten criteria below are the ones UK procurement, information security, internal communications, and HR teams ask about most, in skimmable form. For the full explanation of each requirement and how to divide the evaluation across IT, communications, and HR, read [Choosing a UK Enterprise Intranet in 2026: A Buyer's Guide](https://www.mangoapps.com/articles/choosing-uk-enterprise-intranet-2026). 1. **UK GDPR and Data Protection Act 2018 documentation.** A data processing agreement that names UK GDPR, a maintained subprocessor list, support for data protection impact assessments, and an [ICO-recognised transfer mechanism](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/international-transfers/) (the UK International Data Transfer Agreement or the UK Addendum to the EU standard contractual clauses) for any data leaving the UK. *Verify:* read the DPA before the demo. 2. **Data residency and hosting transparency.** Where the data lives, who can access it, where backups are held, and whether a UK or EU region is available. *Verify:* ask for the hosting statement in writing; "multi-region cloud" is not a residency answer. 3. **Certifications UK InfoSec recognises.** ISO 27001 and SOC 2 Type II as the baseline; [Cyber Essentials Plus](https://www.ncsc.gov.uk/cyberessentials/overview) for public-sector and supply-chain requirements; the [NHS Data Security and Protection Toolkit](https://digital.nhs.uk/data-and-information/looking-after-information/data-security-and-information-governance/data-security-and-protection-toolkit) or HITRUST for health. FedRAMP is a U.S. programme and does not apply. *Verify:* current certificates, not badges. 4. **Microsoft 365 coexistence.** Entra ID single sign-on, Teams and SharePoint content surfaced inside the intranet, and, critically, frontline access that does not require every store or ward employee to hold a Microsoft 365 licence. *Verify:* sign in as a worker with no Microsoft account. 5. **Frontline inclusion without corporate email.** Sign-in by SMS, QR code, or employee ID; a branded app; shared-device and kiosk modes; offline access. Frontline employees are 45% of the UK workforce, about 16.7 million people ([Catalyst, 2025](https://www.catalyst.org/insights/2025/four-frontline-drivers-uk)). *Verify:* activation in under two minutes from a QR code. 6. **Internal communications at enterprise scale.** Targeting by site, region, and shift; read receipts and acknowledgment; multichannel delivery including SMS and digital signage; British English and multilingual content. *Verify:* acknowledgment report by site. 7. **Employee engagement and listening.** Pulse surveys, recognition, communities, and analytics by location, with the consultation obligations that apply where employee representatives or trade unions are recognised. *Verify:* survey results filtered by region. 8. **Public-sector procurement fit, where applicable.** A [G-Cloud](https://www.crowncommercial.gov.uk/agreements/RM1557.14) listing through the Crown Commercial Service, [WCAG 2.2 AA accessibility](https://www.gov.uk/guidance/accessibility-requirements-for-public-sector-websites-and-apps) (monitored for UK public-sector bodies since October 2024), and Welsh-language support for Welsh public bodies. *Verify:* the accessibility statement. 9. **Regulated-sector evidence.** For financial services, the operational-resilience and third-party expectations of the FCA and PRA; for all regulated sectors, audit logs, retention, legal hold, and exportable acknowledgment records. *Verify:* a sample audit export. 10. **UK support and commercial terms.** UK-hours support, GBP pricing, and exit terms that return your data in a usable format. *Verify:* the contract, not the sales deck. ## Which modern employee intranet platforms best serve large enterprises in the United Kingdom? Large UK enterprises most often shortlist MangoApps, Microsoft SharePoint and Viva, Staffbase, Unily, Interact, Oak Engage, LumApps, Simpplr, and Haiilo, with Omnia, Fresh, Involv, and Powell for organisations that want to stay on SharePoint. The shortlist is decided less by feature lists than by UK and European presence, documented residency, the certifications above, Microsoft 365 fit, and whether frontline staff can sign in without a corporate email. | Platform | UK or European presence | UK or EU data residency option | ISO 27001 | SOC 2 Type II | Cyber Essentials Plus | Sign-in without corporate email | Microsoft 365 dependency | Best for UK enterprises | |---|---|---|---|---|---|---|---|---| | [MangoApps](https://www.mangoapps.com/) | Global; UK customers | Multi-region AWS hosting; custom data residency, private cloud, and negotiated transfer terms through enterprise contracting; DPA names UK GDPR and the DPA 2018 and incorporates the UK International Data Transfer Addendum | Yes | Yes | Not published | Yes | None (integrates with M365) | One platform for frontline and desk staff, with HITRUST CSF as well | | [Microsoft SharePoint and Viva](https://www.microsoft.com/en-us/microsoft-365/sharepoint/collaboration) | Global | UK tenancy available | Yes | Yes | Not published | Partial (Teams and licensing) | Required | M365-standardised enterprises with IT capacity | | [Staffbase](https://staffbase.com/) | Headquartered in Germany | EU hosting on Azure and AWS published | Yes | Yes | Not published | Partial | Optional (deep) | Communications-led programmes with M365 depth | | [Unily](https://www.unily.com/) | Multi-region deployments | Vendor-stated | Yes | Yes | Not published | Partial | Optional | Complex global enterprises needing deep governance | | [Interact](https://www.interactsoftware.com/) | North America and Europe | Vendor-stated | Vendor-stated | Vendor-stated | Not published | Partial | Optional | Content publishing and multichannel communications | | [Oak Engage](https://www.oak.com/) | UK-based | Vendor-stated | Vendor-stated | Vendor-stated | Not published | Yes | None | Usability and frontline-friendly features | | [LumApps](https://www.lumapps.com/) (with Beekeeper) | Europe, North America, Japan | Vendor-stated | Vendor-stated | Vendor-stated | Not published | Partial (Beekeeper: Yes) | Optional (M365 and Google) | Communication-first with broad integrations | | [Simpplr](https://www.simpplr.com/) | North America; EMEA support expanding | Vendor-stated | Yes (ISO 27001:2022) | Not published on the page reviewed | Not published | Partial | Optional | Fast deployment, low IT overhead | | [Haiilo](https://www.haiilo.com/) | European | Vendor-stated | Vendor-stated | Vendor-stated | Not published | Partial (MDM deployment) | Optional | Social-first engagement and communications | | [Omnia Intranet](https://www.omniaintranet.com/en) | Based in Sweden | Within the M365 tenancy | Via Microsoft 365 | Via Microsoft 365 | Not published | Yes (QR self-registration) | Required | Rich personalisation on a SharePoint backbone | | [Fresh](https://freshintranet.com/) (Advania) | Nordics and UK | Within the M365 tenancy | Via Microsoft 365 | Via Microsoft 365 | Not published | Limited (Teams or browser) | Required | M365-first organisations wanting a polished SharePoint intranet | | [Involv](https://cognit.be/en/involv) | Belgium | Within the M365 tenancy | Via Microsoft 365 | Via Microsoft 365 | Not published | Limited | Required | M365 organisations wanting better SharePoint UX | | [Firstup](https://firstup.io/) | United States; hosting in the U.S. and Ireland | Ireland hosting (EU) published; no UK region published | Yes | Yes | Not published | Partial | Optional | Enterprise communications orchestration | *Presence, residency, certification, and capability statements for third-party vendors are taken from each vendor's public documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps. "Not published" means the vendor's public pages we reviewed did not disclose it; it does not mean the vendor lacks it. "Partial" means frontline access exists but depends on configuration or licensing. Confirm current certificates, Cyber Essentials Plus status, and residency directly with each vendor during procurement.* The frontline lens changes the UK shortlist more than any other factor. Frontline employees make up 45% of the UK workforce, about 16.7 million people, and 46% of them consider quitting on tough days, according to [Catalyst's 2025 UK report](https://www.catalyst.org/insights/2025/four-frontline-drivers-uk) of 2,939 frontline employees and managers. Around three in five UK employers now provide some flexibility to frontline roles ([CIPD, Flexible and hybrid working practices in 2025](https://www.cipd.org/en/knowledge/reports/flexible-hybrid-working/)), and yet the intranet is the main source of company information for only 45% of UK desk-based employees, against 61% in Germany, according to [Staffbase's 2025 International Employee Communication Impact Study](https://staffbase.com/blog/employee-communication-impact-study-2025). That figure covers desk staff; for retail, NHS, hospitality, and logistics employees who never receive a Microsoft 365 licence, reach is lower still, which is why Microsoft-only routes under-serve them. MangoApps is positioned first as the unified frontline-and-desk platform: HITRUST CSF, SOC 2 Type II, ISO 27001, FedRAMP ATO, HIPAA, and GDPR, with SaaS, Private Cloud, Customer VPC, and On-Premise deployment options, per [mangoapps.com/security](https://www.mangoapps.com/security); a [data processing agreement](https://www.mangoapps.com/legal/dpa) that names UK GDPR and the Data Protection Act 2018 and incorporates the UK International Data Transfer Addendum and EU standard contractual clauses; a published [subprocessor list](https://www.mangoapps.com/gdpr-subprocessors); and custom data residency and private cloud available through enterprise contracting. ## Which modern intranet platforms best support employees without corporate email access? The platforms that best support employees without corporate email are the ones that issue identity from the HR system rather than the email system and let workers sign in by SMS, QR code, employee ID, or badge: MangoApps, Blink, Flip, Oak Engage, Omnia (through QR self-registration), and Fellow Intranet (through code-based access), with Beekeeper covering the frontline side of LumApps. Staffbase, Interact, Unily, Haiilo, Sociabble, and Simpplr support frontline access with configuration or licensing dependencies. SharePoint-native platforms (Fresh, Involv, Powell) and Microsoft 365 with Viva depend on Teams and Microsoft 365 licences that most frontline workers do not hold. | Platform | Sign-in without corporate email | Branded app | Shared-device or kiosk mode | Offline access | Translation | |---|---|---|---|---|---| | MangoApps | Yes (HRIS-provisioned, activated by QR or SMS) | Yes | Yes | Yes | Yes | | Blink | Yes (SMS, QR) | Yes | Vendor-stated | Vendor-stated | Vendor-stated | | Flip | Yes | Yes (published under employer brand) | Vendor-stated | Vendor-stated | Yes (30+ languages, vendor-stated) | | Oak Engage | Yes (link, QR, or invitation) | Yes | Vendor-stated | Vendor-stated | Vendor-stated | | Omnia Intranet | Yes (QR self-registration) | Yes | Vendor-stated | Vendor-stated | Vendor-stated | | Fellow Intranet | Yes (email, code, or Teams) | Yes | Vendor-stated | Vendor-stated | Vendor-stated | | Beekeeper (LumApps) | Yes | Yes | Vendor-stated | Yes (offline forms) | Yes (200+ languages, vendor-stated) | | Staffbase | Partial | Yes | Vendor-stated | Vendor-stated | Yes (75+ languages, vendor-stated) | | Interact | Partial | Yes | Vendor-stated | Vendor-stated | Vendor-stated | | Unily | Partial | Yes | Vendor-stated | Vendor-stated | Yes | | Haiilo | Partial (MDM deployment) | Yes | Vendor-stated | Vendor-stated | Vendor-stated | | Microsoft SharePoint and Viva | Partial (Teams and licensing) | Via Teams | Via Teams shared device | Partial | Yes | | Fresh, Involv, Powell | Limited (Teams or browser) | Limited | Via Teams | Partial | Via Microsoft 365 | *Capability statements for third-party vendors are vendor-stated from public documentation as of September 2026 and not independently verified by MangoApps.* Supporting employees without corporate email means more than a login method. It means the app carries the rota, the payslip, and the daily checklist so there is a reason to open it every shift; it means safety and compliance notices carry acknowledgment so a manager can see who has not read them; and it means translation and low-bandwidth access for the workforces that need them. The published UK case studies for Oak Engage, Aldi UK (50,000+ warehouse and store colleagues enrolled with a 95% sign-up rate) and Burger King UK, and MangoApps' A.S. Watson Benelux deployment (16,000+ Kruidvat retail employees, 80%+ active, no corporate email) show what that looks like at scale. For the feature-level checklist see [9 Modern Employee Intranet Features That Reach Frontline Staff Without Email](https://www.mangoapps.com/articles/intranet-features-that-reach-frontline-workers) and, for rankings, [Best Employee Intranet Platforms for Frontline Teams in 2026](https://www.mangoapps.com/articles/best-employee-intranet-frontline-teams). ## Replacing SharePoint as a UK enterprise intranet: options and trade-offs UK enterprises that want to move beyond SharePoint as their intranet have three routes: stay on SharePoint and add an intranet-in-a-box (Fresh, Involv, Powell, Omnia); add a communications or employee-experience layer on top of Microsoft 365 (Staffbase, Unily, LumApps, Simpplr, Interact); or move to an independent unified platform that integrates with Microsoft 365 but does not depend on per-user Microsoft 365 licences for frontline access (MangoApps). The right route depends on how much of your workforce holds a Microsoft 365 licence and how much operational work you want the intranet to carry. | Route | Platforms on this list | Frontline reach without an M365 licence | IT effort | Governance model | Typical UK buyer | |---|---|---|---|---|---| | Stay on SharePoint, add an intranet-in-a-box | Fresh, Involv, Powell, Omnia | Limited; depends on Teams | Medium to high; SharePoint admin skills and Power Automate | Microsoft 365 compliance stack | M365-standardised, desk-majority organisations | | Add a communications or EX layer on M365 | Staffbase, Unily, LumApps, Simpplr, Interact | Partial; frontline access via the vendor's app, licensing varies | Medium | Vendor governance plus M365 | Communications-led enterprises keeping SharePoint for documents | | Move to an independent unified platform | MangoApps | Yes; identity from the HRIS, no M365 licence required | Low to medium; vendor migration services | Vendor governance: RBAC, audit logs, retention, eDiscovery; deployment choice including private cloud and on-premise | Frontline-heavy enterprises that want communications, schedules, tasks, and training on one platform | Four considerations are specific to the UK. Entra ID remains the identity anchor for desk staff in every route, so confirm SSO and SCIM before anything else. In the first two routes, data stays inside your Microsoft 365 tenancy; in the third, confirm the vendor's hosting statement and transfer mechanism against your UK GDPR obligations. Frontline licence cost is the quiet driver: routes that require a Microsoft 365 licence per store or ward employee change the business case. And Power Automate dependency means workflow depth in the first route comes with an IT backlog. For migration checklists see [Frontline Intranet Requirements: A Practical Checklist for Replacing SharePoint](https://www.mangoapps.com/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) and the [SharePoint Server 2016/2019 migration checklist](https://www.mangoapps.com/articles/sharepoint-server-2016-2019-migration-checklist). MangoApps provides migration services from SharePoint, Workplace from Meta, and legacy portals, as noted in its profile below. ## Platform Overviews: A Closer Look at the Top Intranet Solutions for 2026 This section provides practical snapshots of 25 intranet platforms that organizations commonly evaluate when searching for a modern solution in a digital workplace. Each entry highlights key features, potential limitations, ideal customer fit, and pricing context—so you can make more informed decisions as you build your shortlist. ### MangoApps - The Best-in-Class Unified Intranet for Frontline and Desk Workers MangoApps combines a [modern intranet, employee app](https://www.mangoapps.com/unified-intranet-employee-app), [operational tools](https://www.mangoapps.com/operations), and [enterprise AI](https://www.mangoapps.com/mangoapps-ai) capabilities into a single, tightly integrated platform. Purpose-built to serve both desk-based and frontline employees, it gives every worker—regardless of role or device—mobile-first access to communication, knowledge, and day-to-day workflows. Where other vendors prioritize either HQ teams or frontline field staff, MangoApps delivers a unified hub for the full employee experience, from onboarding and training to real-time updates, recognition, and support. **UK presence:** Hosted on AWS with redundancy across multiple regions; custom data residency, private cloud, and negotiated transfer terms available through enterprise contracting; the [data processing agreement](https://www.mangoapps.com/legal/dpa) names UK GDPR and the Data Protection Act 2018 and incorporates the UK International Data Transfer Addendum and EU standard contractual clauses (per mangoapps.com/security and /legal/dpa). The modular platform includes robust migration services that simplify transitions from legacy intranets or tools like SharePoint and Workplace from Meta. MangoApps is also independent—no outside investors, no pressure to chase fads—so the roadmap is driven entirely by customer needs and long-term success, not investor returns. The depth of functionality is matched by its flexibility. Enterprises can configure everything from branded homepages and [role-based dashboards](https://www.mangoapps.com/key-features/home) to [AI Assistants and Agents](https://www.mangoapps.com/mangoapps-ai) trained on internal data, powered by MangoApps’ integrated AI Studio. These Assistants help employees find answers, complete tasks, and reduce dependency on HR, IT, or operations teams. The mobile experience sees some of the highest frontline adoption rates in the industry, and [native integrations with over 200 third-party enterprise applications](https://www.mangoapps.com/integrations) make it easy to extend across any environment. #### MangoApps Key Features - Unified intranet and employee app experiences for employees across mobile and desktop. - AI-powered search, Assistants, Agents, and enterprise knowledge tools via AI Studio. - Multi-channel communication, [task management](https://www.mangoapps.com/task-management), [forms](https://www.mangoapps.com/key-features/trackers), [training](https://www.mangoapps.com/training-hub), [recognition](https://www.mangoapps.com/recognition-and-rewards), and workflows in one system. - [Enterprise-grade security](https://www.mangoapps.com/security-compliance) with HITRUST, SOC 2 Type II, and ISO 27001 certifications. - 200+ native integrations with third-party applications and enterprise systems, plus open APIs for extensibility. - Built-in migration services from SharePoint, Workplace from Meta, and legacy intranet systems. #### Key Considerations for Evaluating MangoApps - Organizations may want to invest time upfront in configuration to get the most out of the platform’s flexibility. - The platform delivers greatest value when adopted company-wide, rather than used in isolated departments. #### MangoApps Ideal Customer Profile Mid-size to large enterprises (1,000–100,000+ employees) seeking a single, mobile-first hub to unify communications, operations, and knowledge for both frontline and desk workers in a digital workplace. #### MangoApps Customer Case Studies Browse the [MangoApps Resource Library](https://www.mangoapps.com/resources?content-type=Customer+Case+Studies) to explore how some of the largest enterprises in the world enhance their employee experience with MangoApps and achieve strategic business outcomes. #### MangoApps Subscription Pricing MangoApps is offered as a complete packaged intranet solution with bundled modules designed for maximum value. Volume discounts are available for large organizations to ensure an economical investment at scale. We’re committed to making sure cost is never a blocker to delivering unparalleled experiences for employees—and we’re the only vendor in the market to back that up with an Adoption Guarantee of 90%+ active adoption within 90 days. Transparent pricing details are available at [mangoapps.com/pricing](http://mangoapps.com/pricing). ### Akumina [Akumina](https://www.akumina.com/) markets itself as an "Employee Experience Platform" that serves large, distributed enterprises—particularly those with deep Microsoft Office 365 investments and strong IT involvement. The platform supports global deployments with advanced localization capabilities and is often deployed by enterprises with thousands of employees across many regions. #### Akumina Key Features - Advanced integration with Microsoft Office 365, Workday, ServiceNow, and other enterprise systems. - Localization support across 228 languages with personalized intranet experiences. - API-first architecture for custom development and extensibility. #### Key Considerations for Evaluating Akumina - Akumina’s flexibility comes with a steeper learning curve and longer time-to-value than more turnkey platforms. - Delegating content ownership and site management to non-technical users is less intuitive than with other intranet solutions. - Heavy reliance on partners may introduce additional cost and complexity for some organizations. #### Akumina Ideal Customer Profile Global enterprises with complex IT stacks, strong internal development resources, and a preference for hands-on customization—especially those standardized on Microsoft infrastructure. #### Akumina Subscription Pricing Akumina does not publicly disclose pricing. Interested organizations must contact the vendor or an implementation partner directly for a quote based on company size and deployment scope. ### Appspace [Appspace](https://www.appspace.com/) is best known for its origins in digital signage and workplace experience tools, but has steadily broadened its offering to include employee communication and intranet features. The platform blends traditional content publishing with visual signage, space reservation, and workplace management, making it an attractive option for organizations focused on hybrid environments or managing physical spaces across office locations. #### Appspace Key Features - Integrated digital signage, content publishing, space booking, and room displays. - Branded employee homepages with personalized content and widgets. - Microsoft Office 365 integration and compatibility with collaboration tools. #### Key Considerations for Evaluating Appspace - Intranet capabilities are less mature than platforms purpose-built for content governance, structured knowledge, or workflow tools. - ClearBox notes that personalization and targeting features are limited compared to intranet leaders. - Advanced knowledge management or social features may require third-party tools or workarounds. #### Appspace Ideal Customer Profile Enterprises prioritizing a hybrid workplace experience—particularly those that already use Appspace for digital signage or facilities management and want to layer in lightweight internal communications and intranet features. #### Appspace Subscription Pricing Appspace does not list pricing publicly. Organizations must contact the vendor for a tailored quote based on modules selected and number of users or devices. ### Axero [Axero](https://axerosolutions.com/) offers an intranet designed to combine communication, collaboration, and knowledge management in a single platform. Its feature set includes social networking, document sharing, employee directories, wikis, and discussion forums—making it especially appealing to organizations that want more than just a static company homepage. #### Axero Key Features - Integrated social features including activity streams, likes, comments, and forums. - Native document management, wikis, blogs, and knowledge bases. - Visual drag-and-drop page builder with no-code customization. #### Key Considerations for Evaluating Axero - Not as extensible or integration-focused as enterprise platforms designed for hybrid IT ecosystems. - May lack deeper frontline mobile workflows or AI-enabled features offered by newer platforms. - Primarily focused on North American customers with less presence in global enterprise accounts. #### Axero Ideal Customer Profile Mid-sized organizations seeking an all-in-one intranet with built-in collaboration tools, simple admin experience, and internal social functionality—especially those that prefer a self-contained platform over assembling multiple integrated tools. #### Axero Subscription Pricing Axero offers subscription-based pricing, starting at $10/user/month according to publicly available information on [G2](https://www.g2.com/products/axero/pricing). Final costs vary by user count and feature tier, and prospective customers are encouraged to contact Axero for a tailored quote. ### Blink [Blink](https://www.joinblink.com/) is positioned primarily as a mobile-first employee app designed for frontline workers. Its strengths lie in real-time communication, document access, surveys, and task management—all optimized for smartphone use. Rather than serving as a full-scale intranet, Blink functions more as a communications and productivity layer that can connect into other back-end systems. #### Blink Key Features - News feed, chat, forms, and surveys tailored for mobile devices. - Personalized home screen called “The Hub” for easy access to tools and updates. - Integrations with common systems like Microsoft Office 365, Workday, and SAP. #### Key Considerations for Evaluating Blink - Limited web experience and content structuring features compared to full intranet platforms. - Governance tools and admin delegation are less developed than in more enterprise-focused solutions. - Document management, search, and long-form content publishing may require external systems. #### Blink Ideal Customer Profile Organizations with large deskless or frontline workforces—particularly in industries like logistics, transportation, healthcare, and hospitality—that need a fast, simple way to connect, update, and gather input from mobile employees. #### Blink Subscription Pricing Blink offers tiered pricing but does not list specific rates publicly. Pricing depends on organization size and selected features. Prospective buyers must contact Blink directly for a custom quote. ### Fellow Intranet [Fellow Intranet](https://www.fellowdigitals.com/en/fellow-intranet/) is a mobile-first, lightweight platform designed to serve frontline-heavy organizations that need to communicate, train, and manage tasks across dispersed, often non-desk teams. It operates as a standalone solution and does not require SharePoint or Microsoft Office 365, making it accessible to companies without centralized IT infrastructure. #### Fellow Intranet Key Features - Microlearning and training delivery through mobile-optimized card modules, including AI-powered document-to-course conversion. - Flexible onboarding and access options for seasonal, part-time, or non-credentialed staff via email, code, or Microsoft Teams. - Built-in support for news, forms, daily task checklists, and internal job postings, all designed for mobile-first interaction. #### Key Considerations for Evaluating Fellow Intranet - Limited desktop experience and advanced governance tools compared to more enterprise-oriented platforms. - Analytics and search functionality are basic; custom integrations and external analytics may be needed for deeper insights. - Long-term success requires upfront investment in admin setup and governance to avoid sprawl or outdated content. #### Fellow Intranet Ideal Customer Profile Mid-sized organizations with a distributed or multilingual frontline workforce that need a quick-start solution for internal comms. #### Fellow Intranet Subscription Pricing Subscription-based pricing model with discounts available for non-profits, education, and multi-year contracts. Contact the vendor for a tailored quote. ### Firstup [Firstup](https://firstup.io/) began as a mobile-focused internal communications tool and has since evolved toward broader intranet capabilities. Its core strength lies in delivering targeted, multi-channel communications—via mobile, email, desktop, and digital signage—with an emphasis on personalization, automation, and content reach. The platform continues to lead in employee communications and is expanding its capabilities in governance, insights, and data-driven delivery. **UK presence:** U.S. vendor; data hosting in the U.S. and Ireland only, no UK region published (vendor-stated). #### Firstup Key Features - Intelligent content delivery across channels with targeting and automation. - Real-time analytics and campaign management tools to optimize reach and impact. - Personalization engine for segment-based communications and audience targeting. #### Key Considerations for Evaluating Firstup - Lacks the traditional intranet structure needed for work management, collaboration, or content governance at scale. - Developer support, backend integration options, and low-code extensibility are limited compared to more open platforms. - Data hosting is currently limited to the U.S. and Ireland, which may pose challenges for organizations with strict data sovereignty requirements. #### Firstup Ideal Customer Profile Enterprises with more than 2,500 employees—especially in retail, healthcare, or banking—who are looking for a communications-first intranet alternative to drive consistent messaging across a dispersed, multi-channel workforce. #### Firstup Subscription Pricing Firstup does not disclose pricing publicly. Interested organizations must contact the vendor for a quote based on user count, feature scope, and deployment region. ### Flip [Flip](https://www.getflip.com/) positions itself as a frontline employee app that connects deskless teams with the people, tools, and services they need in one mobile-first interface. Designed for companies with a large percentage of non-desk workers, Flip blends internal communications, peer collaboration, task management, and lightweight HR/IT workflows—all wrapped in a modern, app-like experience that’s also accessible via desktop. #### Flip Key Features - Newsfeed and channel-based publishing with audience-specific targeting. - Built-in chat, voice and video calling, livestreaming, and peer community spaces. - Shift swapping, task assignments, and enterprise integrations via API (e.g., Workday, SAP, UKG). #### Key Considerations for Evaluating Flip - Native mobile experience is strong, but integrations are priced separately and require effort to implement. - Lacks page-based information architecture, which may limit structured content presentation. - Live broadcasting is desktop-only for hosts (mobile support planned). #### Flip Ideal Customer Profile Medium to large enterprises with dispersed frontline teams—particularly in retail, manufacturing, logistics, and hospitality—seeking an all-in-one mobile app to streamline communication, tasks, and employee services. #### Flip Subscription Pricing Flip uses a subscription pricing model with per-user or banded tiers. Pricing is in the second-highest ClearBox tier, with discounts for non-profits, educational institutions, and multi-year commitments. Support includes a dedicated Customer Success Manager. Organizations should contact Flip for a tailored quote. ### Fresh [Fresh](https://freshintranet.com/) is an intranet-in-a-box solution built on SharePoint and developed by Advania. It’s designed for medium to large organizations that want a polished, ready-to-launch intranet tightly integrated with their Microsoft Office 365 ecosystem. Fresh enhances core SharePoint capabilities with thoughtful design tools, flexible navigation, intuitive publishing workflows, and AI features that streamline search and content management. **UK presence:** Developed by Advania; data stays within the Microsoft 365 tenancy (vendor-stated). #### Fresh Intranet Key Features - AI-powered editorial assistant (FreshMind) for translation, summarization, and metadata generation. - Configurable mega menus, personalized navigation, and audience targeting via Microsoft Entra. - Built-in recognition features (Kudos, badges), onboarding checklists, and Microsoft Office 365 task integration. #### Key Considerations for Evaluating Fresh Intranet - No standalone mobile app; mobile experience depends on Microsoft Teams or browser access. - Limited native integration with third-party platforms like Workday or ServiceNow. - Some capabilities (like targeting rules and content scheduling) require understanding of Microsoft tools such as Entra and Power Automate. #### Fresh Intranet Ideal Customer Profile Mid-to-large enterprises that are deeply invested in Microsoft Office 365 and want to elevate their SharePoint experience with branded, user-friendly intranet capabilities—especially in industries like government, finance, retail, and professional services. #### Fresh Intranet Subscription Pricing Fresh uses a subscription-based pricing model tied to user count. Discounts may be available for multi-year contracts and qualifying industries. Organizations should contact Fresh directly for a customized quote. ### Haiilo [Haiilo](https://www.haiilo.com/) is a standalone social intranet platform known for its user-friendly experience and emphasis on communication, community, and employee engagement. Formed from the merger of COYO, Smarp, and Jubiwee, Haiilo has grown into a multi-module platform that supports internal communications, employee listening, and advocacy. #### Haiilo Key Features - Studio publishing interface with integrated AI assistant (AVA) for content creation, scheduling, and targeting. - Pages and Communities with rich engagement options, from kudos to polls to discussion forums. - Strong mobile experience with biometric login, chat, timeline publishing, and branded MDM deployment. #### Key Considerations for Evaluating Haiilo - Advanced features like analytics, surveys, and integrations are modular and may require additional fees or setup. - Limited out-of-the-box third-party integrations; most rely on API access via Merge.dev. - Navigation is based on a flat structure (Pages and Communities), which may not meet every organization's needs. #### Haiilo Ideal Customer Profile Medium to large enterprises with 1,000 to 50,000 employees that want a modern and social-first intranet that’s easy to adopt and maintain. Particularly fitting for companies with multiple business units or multilingual needs and that have a strong focus on communications and employee engagement. #### Haiilo Subscription Pricing Haiilo uses a user-based subscription model with discounts for multi-year contracts. Add-on modules and integrations may affect total cost. Interested organizations should contact Haiilo for a tailored quote. ### Igloo Software [Igloo Software](https://www.igloosoftware.com/) is a standalone SaaS intranet platform designed to meet the needs of organizations across a range of industries, including manufacturing, retail, hospitality, and healthcare. The platform offers flexible deployment options (multitenant or single-tenant) and is best suited for mid-market companies seeking core intranet capabilities without a heavy IT lift. Igloo Software includes communications, knowledge sharing, collaboration spaces, and governance tools—all accessible through a browser-based experience. **UK presence:** Optional data centre support in Europe (vendor-stated). #### Igloo Software Key Features - Communication hubs, blogs, wikis, and team spaces for collaboration and knowledge sharing. - Built-in analytics with benchmarking and a monthly maturity assessment service. - Optional single-tenant hosting and data center support in North America and Europe. #### Key Considerations for Evaluating Igloo Software - UI and page layout may feel dated compared to more design-forward platforms. - Lacks federated search and immersive UX features common in next-generation intranets. - Limited global experience outside North America; customers in EMEA or APAC may rely on partners. #### Igloo Software Ideal Customer Profile Mid-sized to large organizations (500–20,000+ employees) in North America seeking a SaaS-based intranet with support, governance, and out-of-the-box features—particularly when cost and compliance are key selection factors. #### Igloo Software Subscription Pricing Igloo Software uses a subscription pricing model based on user tiers. Organizations should contact Igloo Software directly for a tailored quote. ### Interact [Interact](https://www.interactsoftware.com/) is a standalone intranet platform used by organizations in North America and Europe, with strengths in content publishing, engagement, and design flexibility. It supports multi-channel delivery, personalization, and structured communications across both desk and frontline environments. Interact also offers idea management through its Sideways 6 module and continues to expand its use of generative AI for editorial support. **UK presence:** Used by organisations in North America and Europe (vendor-stated). #### Interact Key Features - Drag-and-drop content editor with built-in AI writing and image tools. - multi-channel publishing to mobile, email, Teams, and digital signage. - Structured communities, polls, recognition, and engagement analytics. #### Key Considerations for Evaluating Interact - Admin interface can be complex for global administrators. - Some content tools (e.g., blogs, search suggestions) could benefit from updates. - Deeper integrations or workflow automation may require developer support. #### Interact Ideal Customer Profile Mid-to-large enterprises (2,500+ employees) that prioritize communications, content governance, and flexible delivery across channels. #### Interact Subscription Pricing Per-user subscription model with optional modules; discounts may be available based on industry or contract terms. ### Involv Involv is a SharePoint-based intranet-in-a-box from Belgian company Cognit, aimed at mid-sized to large organizations. It enhances the standard SharePoint experience with modern UX, intuitive admin tools, and deep Microsoft Office 365 integrations—while still requiring some technical involvement from Cognit or IT for setup and changes. **UK presence:** Belgian vendor (Cognit); data stays within the Microsoft 365 tenancy (vendor-stated). #### Involv Key Features - Intuitive admin interface with contextual support and simplified site provisioning. - Personalized “My Page” dashboard integrates tasks, calendars, and documents from M365. - Flexible publishing tools with AI-assisted content creation and targeted notifications. #### Key Considerations for Evaluating Involv - Lacks out-of-the-box integrations with major enterprise systems like Workday or ServiceNow. - Setup and ongoing customization typically require Cognit involvement or IT support. - Mobile app is customizable but lacks advanced frontline-specific features. #### Involv Ideal Customer Profile Mid-sized and large organizations already using Microsoft Office 365 that want a more engaging SharePoint experience—especially those that value easy publishing and a polished UI without abandoning Microsoft’s ecosystem. #### Involv Subscription Pricing Involv uses a subscription model based on user count. Pricing includes support, updates, hosting, and onboarding. Contact the vendor directly for a quote. ### LumApps [LumApps](https://www.lumapps.com/) is a standalone intranet platform focused on internal communications, knowledge sharing, and employee engagement. It serves mid-sized to large enterprises globally, with strong presence in North America, Europe, and Japan. LumApps supports both Microsoft Office 365 and Google Workspace environments, and offers deep integration options along with AI-assisted content and campaign tools. #### LumApps Key Features - 100+ productized integrations, including Microsoft, Google, Workday, and SAP. - multi-channel publishing with campaign management and personalization tools. - AI-powered companion app for frontline and desk workers. #### Key Considerations for Evaluating LumApps - Some customers report higher-than-expected setup and customization effort. - Microapp depth may fall short for organizations with complex vertical needs. - Partner reliance may impact direct support or implementation consistency. #### LumApps Ideal Customer Profile Large or mid-market enterprises (2,000+ employees) seeking a communication-first platform with extensive integration capabilities. #### LumApps Subscription Pricing LumApps offers a tiered subscription model. Pricing varies based on user count, modules, and integration scope. Contact the vendor for a quote. ### Microsoft SharePoint & Viva [SharePoint](https://www.microsoft.com/en-us/microsoft-365/sharepoint/collaboration) and [Viva](https://www.microsoft.com/en-us/microsoft-viva) form Microsoft’s intranet and employee experience offering, deeply embedded within the Microsoft Office 365 ecosystem. SharePoint provides the foundational content services, page-based architecture, and intranet framework, while Viva expands on that foundation with modules for communication, knowledge, learning, insights, and goals. Together, they offer a flexible but IT-dependent solution that appeals to organizations already standardized on Microsoft Office 365. #### SharePoint & Viva Key Features - SharePoint-based intranet framework with page publishing, hub sites, and content governance. - Viva Connections for surfacing personalized content in Teams; Viva Engage for social interaction. - Deep integration with Microsoft Office 365 tools like Outlook, Teams, OneDrive, and Planner. #### Key Considerations for Evaluating SharePoint & Viva - Deployment and configuration often require internal IT support or external partners. - Full Viva functionality requires multiple add-ons and licenses beyond Microsoft Office 365. - Customization and user experience can vary widely based on implementation. #### SharePoint & Viva Ideal Customer Profile Enterprises fully committed to Microsoft Office 365 and Teams, with the internal resources to configure and manage an intranet over time. #### SharePoint & Viva Subscription Pricing SharePoint is included with most Microsoft Office 365 enterprise plans. Viva modules are licensed separately and priced per user, per module. ### Oak Engage [Oak Engage](https://www.oak.com/) is an independent intranet platform that emphasizes ease of use, flexible configuration, and strong support for mobile and frontline users. With a wide range of built-in features—including AI-assisted publishing, employee recognition, and a federated search interface—Oak offers a modern alternative to more complex systems. **UK presence:** UK-based vendor (vendor-stated). #### Oak Engage Key Features - Aria AI for content creation, intelligent targeting, and monthly engagement reporting. - Robust mobile app with integrated tools like payslip access, rotas, and help desk. - Flexible homepages, applets, and campaign tools for segmented communication. #### Key Considerations for Evaluating Oak Engage - While integrations are available, setup may require technical expertise. - Admin tools and some styling elements are less polished than competitors. - Unique approaches (like AI content delivery and search UI) may not suit all orgs. #### Oak Engage Ideal Customer Profile Best suited for midsize to large organizations (1,000–80,000 employees) seeking an intranet that balances usability with solid communications and community features. #### Oak Engage Subscription Pricing Subscription-based with tiered pricing by user count. Offers strong value at the lower end of the enterprise market. ### Omnia Intranet [Omnia Intranet](https://www.omniaintranet.com/en) is a configurable intranet platform built on Microsoft SharePoint but with a distinctly non-SharePoint user experience. The vendor is based in Sweden with a global partner network and acquired LiveTiles in 2024 to expand its reach and roadmap. **UK presence:** Based in Sweden with a global partner network (vendor-stated). #### Omnia Intranet Key Features - Deep Microsoft Office 365 integration with custom UI, semantic search, and structured content governance. - Modular publishing and community features with AI-powered authoring, feedback collection, and campaign tools. - Tailored mobile experiences with role-based access, QR self-registration, and frontline support via checklists and sign-off requests. #### Key Considerations for Evaluating Omnia Intranet - Flexibility comes with complexity; most implementations require skilled consultants and involve a steep learning curve. - Out-of-the-box third-party integrations are read-only; deeper workflows require custom development. - Admin interface is powerful but can be dense; some administrative tasks still rely on standard SharePoint tools. #### Omnia Intranet Ideal Customer Profile Omnia Intranet suits medium to large organizations that want to deliver a rich, personalized intranet and have the internal or partner resources to manage a flexible but complex solution. #### Omnia Intranet Subscription Pricing Omnia Intranet is competitively priced given its capabilities, with costs based on user count and configuration scope. Discounts are typically available for nonprofits. ### Poppulo [Poppulo](https://www.poppulo.com/) is a standalone communications platform. It helps large organizations manage and share content across many channels. These include email, mobile, Microsoft Teams, SharePoint, and digital signage. It’s built for internal communicators and offers tools for content planning, campaign management, and message targeting, with support for local and global teams alike. #### Poppulo Key Features - Multi-channel campaign builder with audience targeting and campaign calendar. - AI-powered editing tools, branded email templates, and auto-generated microsites. - Native support for email, digital signage, Teams, and SharePoint content delivery. #### Key Considerations for Evaluating Poppulo - App and microsite content findability is limited; no native search interface. - Not a full-featured intranet; focused more on communication than structured knowledge management. - Digital signage and some personalization features may come at additional cost. #### Poppulo Ideal Customer Profile Large enterprises (20,000–50,000+ employees) with distributed teams that need structured, campaign-based internal communications across multiple digital channels. #### Poppulo Subscription Pricing Subscription-based pricing with costs tied to user count and selected modules. Contact Poppulo for a tailored quote. ### Powell Intranet [Powell Intranet](https://powell-software.com/) is a comprehensive intranet solution built on top of SharePoint Online. It enhances native SharePoint functionality with a wide array of components, templates, and front-end administration tools to improve usability and reduce complexity for both end users and intranet managers. #### Powell Intranet Key Features - Embedded AI assistant (Powell Intranet Buddy) supports content creation, search, and translation. - Extensive widget gallery and design controls to customize intranet pages. - Flexible branding, mobile access, and support for frontline use cases like desk booking and digital signage. #### Key Considerations for Evaluating Powell Intranet - Fully reliant on Microsoft Office 365, with many advanced features requiring SharePoint admin knowledge or partner support. - Page load speed, inconsistent UI elements, and admin complexity were flagged by some customers. - Analytics rely on Power BI and M365; native capabilities are improving but remain fragmented. #### Powell Intranet Ideal Customer Profile Particularly useful for mid-size to large enterprises with Microsoft-savvy IT teams or trusted implementation partners. #### Powell Intranet Subscription Pricing Subscription pricing per user with volume-based tiers. Positioned in the higher pricing category, especially once services and partner support are factored in. ### Simpplr [Simpplr](https://www.simpplr.com/) is a SaaS intranet platform designed to deliver a unified and personalized employee experience with minimal IT dependency. It offers out-of-the-box functionality for communication, knowledge sharing, and engagement across both desk and frontline workers. The platform emphasizes simplicity, fast deployment, and intuitive content management. #### Simpplr Key Features - Prebuilt intranet modules for comms, social, and knowledge management. - Strong self-service publishing, search, and governance tools. - AI-enhanced features for personalization, analytics, and automation. #### Key Considerations for Evaluating Simpplr - Highly packaged approach may limit flexibility for complex or heavily integrated environments. - Global support outside North America is still expanding; EMEA clients should confirm coverage. - Some users report integration gaps and room for improvement in mobile and DAM features. #### Simpplr Ideal Customer Profile Best suited for mid-sized organizations that want a modern intranet with strong communications capabilities and minimal IT overhead. #### Simpplr Subscription Pricing Subscription-based model with tiered pricing by user count. Implementation services are typically included; contact Simpplr for a tailored quote. ### Sociabble [Sociabble](https://www.sociabble.com/) is a communications-focused platform designed for large, distributed organizations—especially those with a high percentage of frontline workers. It delivers content through a scrollable newsfeed optimized for mobile, with features like push notifications, gamification, and employee advocacy built in. The platform prioritizes engagement and ease of use over traditional intranet structure. #### Sociabble Key Features - Scrollable content wall with automation, targeting, and compliance tools. - AI-powered authoring, translation, and editorial support. - Mobile app with podcasts, video, gamification, and push notifications. #### Key Considerations for Evaluating Sociabble - Limited support for structured intranet content like pages or document repositories. - Branding and search capabilities are less developed than some competitors. - Pricing and implementation services place it on the higher end of the market. #### Sociabble Ideal Customer Profile Large enterprises with strong internal comms teams and a high volume of frontline or mobile-first employees. #### Sociabble Subscription Pricing Per-user subscription model with add-ons for modules like advocacy and service desk. Contact Sociabble for a tailored quote. ### Staffbase [Staffbase](https://staffbase.com/) is a standalone intranet and employee communications platform, originally built mobile-first, with broad multi-channel publishing capabilities and a strong focus on employee engagement. Headquartered in Germany, it serves a global customer base across desktop and mobile with deep integration into the Microsoft Office 365 ecosystem. **UK presence:** Headquartered in Germany; EU hosting on Azure and AWS published (vendor-stated). #### Staffbase Key Features - Powerful multi-channel publishing tools, including intranet, newsletters, SMS, signage, and LinkedIn. - Companion AI editor and campaign analytics support strategic internal comms. - Deep Microsoft Office 365 integrations, including Teams, SharePoint, Copilot, and Power BI. #### Key Considerations for Evaluating Staffbase - Content governance and enterprise search are weaker than in some rival platforms. - Better suited to communications-driven intranet use cases than knowledge management. - Design customization is solid but not as flexible as some visual intranet builders. #### Staffbase Ideal Customer Profile Medium to large organizations seeking a communications-focused intranet with strong support for mobile, M365 integration, and global deployments. #### Staffbase Subscription Pricing Staffbase is in the higher price tier, with subscription-based pricing that includes services like onboarding, branding, and customer success support. Discounts are available for nonprofits, public sector, and high-volume or multi-year deals. ### ThoughtFarmer [ThoughtFarmer](https://www.thoughtfarmer.com/) is a standalone intranet platform based in Canada, designed for companies that want a balance of communications, culture, and knowledge sharing. Its strength lies in delivering a highly usable and flexible experience, especially for small to midsize teams that value simplicity and support. #### ThoughtFarmer Key Features - Clean, intuitive page layouts with drag-and-drop editing and strong lifecycle tools like content review workflows. - Social and engagement capabilities including Shout-Outs, recognition badges, and lightweight forums. - Reliable search across intranet and integrated file sources, with “best bets” and customizable filters. #### Key Considerations for Evaluating ThoughtFarmer - Out-of-the-box integrations are limited; deeper system connections require custom work or developer setup. - Navigation, branding, and news planning features lack depth compared to larger competitors. - No dedicated frontline app features; mobile app is usable but somewhat pared down. #### ThoughtFarmer Ideal Customer Profile Best suited to organizations under 5,000 employees that prioritize usability, internal comms, and a guided implementation experience over deep technical extensibility. #### ThoughtFarmer Subscription Pricing Subscription-based pricing. Organizations should contact ThoughtFarmer directly for a tailored quote. ### Unily [Unily](https://www.unily.com/) is an intranet and employee experience platform built to serve large, complex organizations. With a strong focus on personalization, content management, and enterprise governance, it supports global deployments across multiple regions, business units, and user types. The platform is often selected for its configuration flexibility, campaign management capabilities, and ability to unify digital experiences at scale. **UK presence:** Supports global deployments across multiple regions (vendor-stated). #### Unily Key Features - Deep personalization and targeting capabilities, including dynamic audience groups and lifecycle campaigns. - Native digital assistant integration with Microsoft Azure OpenAI and Workgrid for AI-powered content support. - Flexible content creation and governance tools, including version control, accessibility checks, and timed publishing. #### Key Considerations for Evaluating Unily - Requires experienced admins or support resources to manage its powerful but complex back end. - AI, advanced integrations, and branding configurations may introduce additional cost and effort. - Mobile experience is strong but depends on thoughtful simplification of the desktop environment. #### Unily Ideal Customer Profile Enterprises with 10,000+ employees, distributed teams, and defined ownership for intranet management and comms strategy. #### Unily Subscription Pricing Unily offers modular, user-based subscription pricing. Contact the vendor for a custom quote based on scope and deployment size. ### Workvivo (part of Zoom Video Communications) [Workvivo](https://www.workvivo.com/) is an intranet platform focused on communication. It emphasizes social interaction, mobile access, and publishing on multiple channels.Now part of Zoom, it has attracted attention through its partnership with Meta to support some Workplace transitions, but organizations considering migration should evaluate platform fit based on long-term needs rather than short-term alignment. #### Workvivo Key Features - Social feed interface with reactions, comments, shout-outs, and embedded video. - multi-channel publishing via email, mobile, desktop, Teams, and Zoom integration. - Community tools including spaces, recognition, surveys, and an employee directory. #### Key Considerations for Evaluating Workvivo - Emphasis on engagement and culture may leave gaps for orgs seeking deeper workflow or task integration. - Limited native features for structured knowledge management or document control. - Regional presence and support are concentrated in North America and Europe. #### Workvivo Ideal Customer Profile Large organizations with a focus on employee connection and communications, particularly those already using Zoom. #### Workvivo Subscription Pricing Subscription-based pricing model tied to user count and functionality. Contact Workvivo for a tailored quote. ## Common Intranet Project Pitfalls to Avoid Even with good intentions, many intranet projects miss the mark. Here are three of the most common mistakes: - Skipping User Research: Choosing features based on assumptions—rather than what frontline workers actually need—can lead to poor adoption. - Overestimating IT Resources: Platforms that require heavy customization or ongoing IT support often stall out, especially in lean environments. - Undervaluing Change Management: A great platform won’t matter if employees don’t know how or why to use it. Successful rollouts require training, champions, and executive visibility. Avoiding these traps starts with asking the right questions. That’s where our [Intranet Planning Guide](https://www.mangoapps.com/resources/intranet-planning-guide) comes in. It’s packed with real-world insights, a practical implementation model, and field-tested launch criteria tailored to frontline and deskworker needs. Download it now to set your project up for long-term success. ## Final Thoughts - Choosing the Right Intranet Platform No two platforms are the same—and neither are the organizations evaluating them. Your choice should reflect your specific workforce, systems, and goals. But knowing where to start can be overwhelming. Choosing the right intranet platform is a strategic decision—especially as the expectations for internal communication, knowledge access, and frontline connectivity continue to grow. MangoApps is one of the few platforms purpose-built to unify the experience for both frontline and desk-based employees, with enterprise-grade AI, workflow support, and security. If you're navigating this process and want a deeper framework to guide your selection, we highly recommend downloading our [2026 Intranet Buyer’s Guide for a Frontline Workforce](https://www.mangoapps.com/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026). The guide includes: - A vendor evaluation process with business case guidelines - Frontline-specific use cases and success benchmarks - Implementation best practices from real-world rollouts ## Other Helpful Intranet Resources - [ClearBox Intranet and Employee Experience Platforms Report 2026](https://www.mangoapps.com/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) - the most in-depth independent guide to intranet and employee experience platforms: 37 platforms reviewed across 921 pages, free to download. - [IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment](https://www.mangoapps.com/resources/idc-marketscape-2024) - download the report and see why the IDC MarketScape named MangoApps a leader in Experience-Centric Intelligent Digital Workspaces. - [Gartner Peer InsightsTM Intranet Packaged Solutions Reviews and Ratings:](https://www.gartner.com/reviews/market/intranet-packaged-solutions) View ratings from verified customers of the top intranet platforms, including MangoApps, which carries an average rating of 4.6/5 stars (verify the current rating and date before publishing). - [Gartner® Magic QuadrantTM for Intranet Packaged Solutions:](https://www.gartner.com/document-reader/document/6014903?ref=ddisp&refval=806402&toggle=1&viewType=Full) The Gartner IPS MQ evaluates vendors for Completeness of Vision and Ability to Execute to determine the most viable solutions in the market. It is similar to the Forrester Wave noted below. Must have an active Gartner research subscription to download. - The Forrester WaveTM: Intranet Platforms, Q2 2026: The Forrester Wave report provides in-depth analysis of 13 intranet platform vendors and evaluated their products across 28 criteria. Must have an active Forrester research subscription to download. - [MangoApps Customer Success Stories:](https://www.mangoapps.com/customers) Discover how MangoApps assists companies in boosting productivity, elevating employee engagement, enhancing retention, and streamlining operations. - [Choosing a UK Enterprise Intranet in 2026: A Buyer's Guide](https://www.mangoapps.com/articles/choosing-uk-enterprise-intranet-2026) - the UK governance, residency, and Microsoft 365 requirements explained in full. - [The 10 Best Employee Intranet Platforms for Governance, Compliance, and Global Workforce Communication](https://www.mangoapps.com/articles/best-intranet-platforms-governance-compliance-global) - a governance-first ranking of ten platforms for multi-country, regulated enterprises. - [ICO guidance on UK GDPR](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/) and [NCSC Cyber Essentials](https://www.ncsc.gov.uk/cyberessentials/overview) - the primary UK sources for the criteria in the UK section above. ## Frequently Asked Questions (FAQ) **What is an intranet platform and why does it matter in 2026?** An intranet platform is a centralized digital hub where employees access company news, tools, documents, training, and more. In 2026, it’s no longer just a communication tool—it’s a key driver of productivity, engagement, and employee experience, especially for organizations with frontline and distributed teams. **What should I look for in a modern intranet solution?** Look for a platform that offers: - A unified experience across desktop and mobile. - Strong support for both desk and frontline workers. - Built-in AI capabilities for search, assistance, and content creation. - Integration flexibility with your existing tools (e.g., Microsoft 365, Workday, SAP). - Robust governance, analytics, and security features. **How is MangoApps different from other vendors on the list?** MangoApps uniquely combines intranet, employee app, work tools, and enterprise AI into a single platform—purpose-built for both frontline and desk workers. It stands out for its: - Deep configurability without the complexity. - Independent ownership and customer-driven roadmap. - Built-in AI Studio for custom assistants trained on your data. - Strong migration services from legacy systems like SharePoint or Workplace from Meta. **Are these intranet platforms only for large enterprises?** No. While many solutions cater to organizations with 1,000+ employees, several vendors offer versions or editions designed for mid-size companies. That said, platforms like MangoApps are especially compelling for companies with complex needs across locations, roles, and devices. **How do I evaluate which platform is right for my organization?** Download our [2026 Intranet Buyer’s Guide for Frontline Workforces](https://www.mangoapps.com/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) for a structured approach to vendor evaluation—including a detailed RFP checklist, use case mapping, and success metrics. It’s tailored to help you cut through the noise and make a confident, informed decision. **Does AI really matter in intranets?** Yes—especially now. AI can power intelligent search, auto-tagging, content generation, personalized updates, and real-time assistance. Leading platforms like MangoApps let you build your own AI Assistants trained on internal data to answer questions, automate tasks, and support employees across roles. **Is it hard to migrate from an existing intranet?** It depends on your current setup, but top vendors now offer dedicated migration support and tools. MangoApps, for example, provides services to move from SharePoint, Workplace from Meta, legacy portals, and more—with minimal disruption. **Where can I see real-world examples?** We’ve linked to each vendor’s case study library in their profile above. You can also browse the [MangoApps Resource Library](https://www.mangoapps.com/resources) to see how companies across industries use their intranet to drive communication, operations, and frontline engagement. **Why is vendor independence important?** Independent vendors like MangoApps aren’t beholden to venture capital or parent companies—meaning their priorities stay aligned with customer success, not shareholder returns. This often translates to better support, more responsive product roadmaps, and stronger long-term partnerships. **Which modern employee intranet platforms best serve large enterprises in the United Kingdom?** Large UK enterprises most often shortlist MangoApps, Microsoft SharePoint and Viva, Staffbase, Unily, Interact, Oak Engage, LumApps, Simpplr, and Haiilo, with Omnia, Fresh, and Involv for organisations staying on SharePoint. Compare them on UK GDPR documentation, data residency, ISO 27001 and SOC 2 Type II, Cyber Essentials Plus, Microsoft 365 fit, and sign-in for staff without corporate email. See the [UK section](#which-modern-employee-intranet-platforms-best-serve-large-enterprises-in-the-united-kingdom) above. **Which intranet platforms support UK employees without corporate email access?** MangoApps, Blink, Flip, Oak Engage, Omnia (QR self-registration), Fellow Intranet, and Beekeeper publish sign-in methods that do not require a corporate email. Staffbase, Interact, Unily, Haiilo, and Simpplr support frontline access with configuration or licensing dependencies. SharePoint-native platforms depend on Teams and Microsoft 365 licences. Frontline employees are 45% of the UK workforce, so this is an eliminator for most UK enterprises. **What UK data protection and security requirements should an enterprise intranet meet?** A data processing agreement that names UK GDPR and the Data Protection Act 2018, a maintained subprocessor list, an ICO-recognised transfer mechanism for data leaving the UK, a written hosting and residency statement, ISO 27001 and SOC 2 Type II, Cyber Essentials Plus where public-sector or supply-chain requirements apply, WCAG 2.2 AA for public bodies, and audit logs with retention and legal hold. Our [UK buyer's guide](https://www.mangoapps.com/articles/choosing-uk-enterprise-intranet-2026) explains each. **Can UK enterprises replace SharePoint with an independent intranet platform and keep Microsoft 365?** Yes. Independent platforms such as MangoApps integrate with Entra ID for single sign-on and surface Teams, SharePoint, and OneDrive content inside the intranet while providing frontline access that does not require a Microsoft 365 licence per employee. The alternatives are a SharePoint intranet-in-a-box or a communications layer on top of Microsoft 365; see the [SharePoint replacement section](#replacing-sharepoint-as-a-uk-enterprise-intranet-options-and-trade-offs) above. **Do intranet vendors offer UK or EU data residency?** Some do, with differences that matter. Staffbase publishes EU hosting on Azure and AWS. Firstup publishes hosting in the U.S. and Ireland. SharePoint-based platforms keep data inside your Microsoft 365 tenancy. MangoApps hosts on AWS across multiple regions and offers custom data residency and private cloud through enterprise contracting, with a DPA that incorporates the UK International Data Transfer Addendum. Always request the hosting statement in writing. --- # What is MangoApps? The Unified Employee Hub That Connects it All **Author:** MangoApps **Published:** 2025-07-25 **Category:** employee-platform MangoApps is the all-in-one employee hub designed to unify communication, collaboration, knowledge, and tools—whether your teams are behind a desk or out in the field. This article breaks down how MangoApps replaces outdated intranets, disconnected frontline apps, and excessive email threads with a single, AI-powered platform that helps organizations boost productivity, engagement, and operational agility. If you're searching for the best intranet for frontline employees, a unified employee experience platform, or a modern company portal that actually works—this is your blueprint. The Employee Hub That Actually Lives Up to the Word “Unified”Work doesn’t happen in one place anymore—and honestly, neither do employees. Some are in offices toggling between tabs like it's an Olympic sport. Others are on shop floors, factory lines, or hospital wings without easy access to schedules or updates. And yet, companies are still trying to force a one-size-fits-all solution to connect them all.That’s where MangoApps steps in—not as another tool, but as the hub where communication, collaboration, knowledge, and people come together. Whether you’re searching for the best intranet for frontline teams, a modern employee portal, or a unified employee experience platform that actually delivers—this is the one to watch.Let’s break down why.Fragmented Tools, Fractured ExperienceMost companies are drowning in tools—literally. Knowledge workers switch between 11 apps a day, losing roughly 4 hours a week just clicking around. Meanwhile, 80% of the global workforce—the frontline teams—are stuck in a digital desert, cut off from even basic tools like shift schedules or HR policies.The result? Missed messages. Duplicate work. Frustrated employees. And an employee experience that feels like a cluttered garage full of half-used software.MangoApps wasn’t built to patch those problems. It was built to solve them.One Hub. Everything You Need.At its core, MangoApps is a unified digital workspace—a single destination for your employees to get what they need, when they need it, without jumping through hoops or downloading five different apps.You’ve got:A company-branded intranet that’s intuitive and mobile-ready.AI-powered search that works across internal and external systems.Communication tools that actually reach everyone—from warehouse staff to the C-suite.Self-service department pages where employees can access policies, forms, or training without pinging HR.Recognition, surveys, and engagement tools to help build culture, not just workflows.It’s all stitched together in a sleek, familiar interface that works just as well on a smartphone as it does on a desktop.From Homepages to HR Hubs: How It WorksMangoApps starts with the Home module, a customizable dashboard that greets every employee with what matters to them—team news, priority tasks, single sign-on buttons to third-party tools, even shift schedules or payroll details.Then there’s the Company portal, a central place for org-wide communication. Think holiday calendars, leadership updates, and recognitions—all visible and accessible with zero hunting.Departments get their own hubs too. Let’s say the HR team wants to publish a new benefits guide. Instead of sending an all-staff email into the void, they drop it into the HR Department page—where employees know to look. Everything is searchable. Everything is trackable. And nothing gets lost in the shuffle.A Social Layer That Connects Humans (Not Just Roles)The News Feed acts like an internal social network—but smarter. Updates, reactions, comments, and polls are easy to publish and just as easy to track. People engage not because they’re told to—but because the platform feels native, familiar, and frictionless.Need to find a coworker you’ve never met? The Employee Directory makes it ridiculously easy. You can search by name, department, location, or even skill. Once you’ve found them, start a chat or send a message instantly—no need for external tools.AI: The Invisible Assistant Behind the CurtainThis isn’t “just another search bar.” MangoApps uses AI to make everything easier—from finding a PTO policy to summarizing knowledge base articles or answering real-time employee questions.Admins can train the AI on company-specific knowledge, set role-based access, and keep everything secure. It’s your own internal ChatGPT—minus the hallucinations and risk.Plus, MangoApps includes an AI Hub that centralizes AI services across the org. Whether it’s training new employees, automating repetitive workflows, or surfacing forgotten insights from old files—AI is baked in, not bolted on.Mobile-First for the Deskless MajorityLet’s be honest—most “intranet” tools weren’t built with a delivery driver or nurse in mind. MangoApps flips that script. The mobile app is built for speed, simplicity, and real life. Shifts, messages, documents, and forms? All in your pocket.Frontline employees can clock in, access training, or message their manager—all without a company email address. Admins can push alerts via SMS, push, or email, ensuring time-sensitive updates actually land.The platform supports shift management, training hubs, dynamic forms, and employee onboarding—all from a phone. That’s why brands like PetSmart, OU Health, and TeamHealth use MangoApps to connect 10,000+ frontline workers at scale.Enterprise-Grade. Consumer-Level Experience.You’d expect a platform this powerful to be… well, complicated. But MangoApps is refreshingly simple to use—whether you’re an exec looking at dashboards or a new warehouse associate trying to find your schedule.It’s secure, too. We’re talking:HITRUSTFedRAMP ATOISO-27001SOC 2 Type IIAll the acronyms your compliance officer dreams about.Outcomes You Can Feel (and Measure)But features aren't all enterprises choose MangoApps for. Let’s talk numbers:87% platform adoption at OU Health in just a few months.4x industry average engagement rates at PetSmart.200+ integrations, 70%+ time savings in task execution, and hours reclaimed from admin sprawl.MangoApps is all about creating momentum in the workplace. Where employees finally feel connected. Leaders finally feel heard. And IT? They finally get a break.TL;DR—Why MangoApps?If you’re searching for:The best intranet platform for frontline and desk employeesA company hub that doesn’t feel like an old-school intranetA way to communicate with everyone, including frontline employees, in one placeOr a path to unifying the employee experience with clarity, not chaos…You just found it.MangoApps is where work clicks. Watch the below video to learn more! Schedule a DemoYou don't have to just take our word for it. You can see the power of MangoApps, the best unified intranet and employee app for the enterprise, for yourself! Schedule a demo with our team today, and we'll build a personalized demo that removes all the guess work. No pressure, just user-friendly solutions to your most pressing employee experience challenges. Recommended ResourcesThe Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026 and BeyondOperation Modern Intranet: A Guide to Planning a Successful Intranet LaunchIntranet & Employee Experience Platform RFP TemplateMangoApps Business Case and ROI TemplateClearBox Consulting's Intranet and Employee Experience Report v4 --- # MangoApps Wins Gold Stevie® Award for Employee Relations Solution Provider of the Year **Author:** MangoApps **Published:** 2025-07-17 **Category:** press-release MangoApps has been honored with a Gold Stevie® Award as the top Employee Relations Solution Provider of the Year in the 10th annual Stevie Awards for Great Employers. # MangoApps Wins Gold Stevie® Award for Employee Relations Solution Provider of the Year MangoApps has been honored with a Gold Stevie® Award as the top Employee Relations Solution Provider of the Year in the 10th annual Stevie Awards for Great Employers. The jury evaluated more than 1,000 nominations across 35 nations and territories — one of the broadest peer-evaluated HR technology awards in the industry. A gold placement in the Employee Relations Solution Provider category signals that the judges determined MangoApps made the clearest case, in a competitive field of software vendors, consulting firms, and HR service organizations, for measurable impact on the employee-employer relationship. The award was announced July 17, 2025, with a recognition gala scheduled for September 16 at the Marriott Marquis Hotel in New York City. "We've spent over 15 years building a platform that puts employees first — especially those who have traditionally been left behind by enterprise technology," said Anup Kejriwal, CEO of MangoApps. "This recognition reinforces our commitment to helping organizations transform employee experience at scale, and we're incredibly proud to be named a Gold Stevie Award winner." ## What the Stevie judges evaluated — and why this category differs from capability awards Most vendor recognition programs assess capabilities: feature depth, integration coverage, and market presence. The Stevie Awards for Great Employers are structured around a different question — whether technology has helped organizations build better relationships with their employees through cleaner communication, more accessible information, and more equitable access across different roles and locations. The evaluation is outcome-oriented, not feature-oriented, which is why placement in this category carries a different signal than placement in a product capability matrix. Judges cited MangoApps specifically for bridging the workforce divide: connecting desk employees and frontline workers through a single platform architecture rather than separate systems deployed in parallel. Two platform developments drew particular attention from the evaluation committee. MangoApps AI Studio allows organizations to build private, company-specific AI assistants trained on their own content. Rather than routing employee questions through generic AI tools that surface results from the open internet, AI Studio lets HR and IT teams configure assistants with proprietary knowledge — policy documents, onboarding guides, standard operating procedures, and organizational context specific to the company's structure and terminology. When an hourly employee in a distribution center asks about their shift-change policy, AI Studio answers from the actual document that governs that policy, not a generically plausible interpretation. That specificity is what makes AI useful for employee relations rather than a source of additional confusion. The 19.0 platform release delivered usability improvements specifically for frontline teams: mobile delivery enhancements and AI-powered content surfacing that brings relevant communications, training materials, and schedule updates to workers in context, without requiring them to navigate a portal or log into a browser-based tool on a workstation they may not have consistent access to. For clinical staff, warehouse workers, and retail associates working active shifts, that difference in access model determines whether enterprise communications reach them at all. Judges described the combination as evidence of a platform designed to foster "more connected, inclusive, and efficient work environments" — language that goes beyond product capabilities to describe observed conditions in customer deployments. ## The customer outcomes the judges reviewed Recognition in the Employee Relations Solution Provider category is validated against specific deployment evidence, not product demonstrations. Two deployments submitted as part of the evaluation produced measurably different outcomes from the benchmarks the industry tracks broadly. OU Health deployed a branded MangoApps employee app for clinical staff and reached 87% workforce engagement within the first months of deployment. Clinical workers represent one of the most difficult populations for communications technology to reach: they are mobile throughout shifts, have no assigned workstation, and operate under time constraints that leave no space for navigating complex enterprise interfaces. An 87% engagement rate in that population reflects a different access model, not just a different platform. The Kansas City Chiefs deployed MangoApps for event staff — hourly workers who are on-site intermittently, without corporate email accounts, and without time during active events to check a browser-based tool. They reached 90% adoption among that population. The outcome reflects what happens when enrollment architecture is designed for how workers actually operate — starting from a personal mobile device without a corporate credential — rather than how IT departments prefer to provision access. Per Social Edge Consulting's intranet benchmark research, 91% of organizations already operate an intranet — but only 13% of employees use it daily, and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends just six minutes per day in intranet tools. The deployments above occupy a different part of the adoption distribution. That difference is what the Stevie judges were assessing when they evaluated whether MangoApps was improving the employee-employer relationship in practice. ## Why the frontline access question determines adoption outcomes Per Emergence Capital research, 80% of the global workforce is deskless. In healthcare, manufacturing, retail, and logistics, that figure is higher. Standard employee experience platforms were designed for workers who check a browser tab between meetings — an interaction model that does not apply to clinical staff, warehouse associates, or retail employees working active shifts without assigned workstations. The access barrier is structural, not behavioral. Most intranet platforms require a corporate email address to log in. That requirement immediately excludes a large share of frontline workers in the industries where deskless work is most prevalent. MangoApps supports enrollment without corporate email, delivers content on personal mobile devices, enables offline access for workers in low-connectivity environments, and provides schedules and communications through the same [unified employee app](/solutions/employee-app) where knowledge management and HR functions live. The result is a single platform architecture that does not require organizations to run separate systems for desk-based and frontline employees, or to accept that large segments of their workforce are structurally unreachable through enterprise technology. Per IDC research, employees spend an average of 2.5 hours per day searching for information they cannot easily find — a cost that compounds across departments depending on workers locating policies, procedures, or schedule updates quickly. When access barriers are removed, the information gap that drives that 2.5-hour figure narrows in ways that a platform averaging six minutes of daily usage per employee cannot close. For HR and operations leaders, the frontline access question is not a secondary consideration for future roadmap planning. An organization where the majority of the workforce cannot reliably reach the employee experience platform does not have an employee experience platform in any functional sense — it has a desk-employee tool with an unaddressed coverage gap. ## How the Stevie recognition relates to other independent evaluations The Stevie Awards for Great Employers assess the employee-employer relationship — a dimension that feature-checklist evaluations, analyst capability matrices, and market-share analyses do not capture. That specificity is what makes recognition in this category useful for buyers interpreting what it actually signals. MangoApps has also been evaluated across frameworks that surface different dimensions of platform performance. The company was [named in a leading research firm's 2026 Intranet Platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) alongside major enterprise competitors, and received Gold in Reworked's 2026 IMPACT Awards for Excellence in Intranet and Communications Platforms. Each of these assessments uses different evaluation criteria and different evidence standards. Consistent recognition across frameworks with different methodologies is harder to manufacture than optimization for a single award's scoring rubric. Per the [Gallup 2026 State of the Global Workplace analysis](/articles/gallup-2026-state-of-the-global-workplace), employee engagement is one of the most consequential variables HR teams track — and the platforms organizations choose to support communication and knowledge access are a direct input to that variable. The technology selection is not separate from the engagement outcome; it is part of what determines it. Recognition programs that evaluate platforms on observed engagement outcomes rather than product features are measuring the right thing. For buyers conducting their own evaluations, the relevant question is not which platform has the most recognitions — it is which recognitions were based on evidence most comparable to the buyer's own workforce profile. A platform that achieves 90% adoption among hourly event staff without corporate email credentials is making a different claim than one that achieves high engagement among office workers with full Microsoft 365 licenses. Both claims can be accurate. They apply to different populations. ## What organizations should do with this recognition The Gold Stevie Award does not change what MangoApps does. It confirms, from an independent jury that reviewed more than 1,000 nominations across 35 countries, that the platform is having the intended effect on how organizations relate to their employees — particularly those who have historically been the hardest to reach through enterprise technology. For HR and operations leaders currently evaluating employee experience platforms, two questions are worth raising in any vendor conversation. First: what is the measurable adoption rate among frontline or deskless employees in comparable customer deployments — not total user count or average session metrics, but specifically among workers without regular desktop access? Second: how does the platform handle enrollment for workers without corporate email addresses, and what does adoption data look like in those populations? These questions have specific answers in the MangoApps case. The Kansas City Chiefs event staff, OU Health clinical staff, and comparable deployments across healthcare, manufacturing, and retail represent a factual record that can be examined and compared to any alternative. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) includes measurement frameworks that HR and communications leaders are using to set 90-day adoption benchmarks and track engagement signals before attrition data starts to move. For organizations working through the vendor evaluation process, those frameworks provide a structure for assessing whether a platform is likely to produce outcomes in the range the Stevie judges recognized — or in the range the six-minute-per-day average describes. The adoption gap the Stevie judges evaluated is not a fixed condition. It is a function of which platforms organizations select and whether the access model is designed for how their full workforce actually operates — not just the portion that sits at a desk. --- # MangoApps Adds AI-Powered Scheduling & Shift Swap to Its Extensive Workplace Operations App Marketplace **Author:** MangoApps **Published:** 2025-07-15 **Category:** press-release New AI-powered scheduling and shift swap tools make frontline workforce planning faster, fairer, and fully mobile—empowering teams while saving managers hours each week.  # What AI-Powered Scheduling Actually Changes for Frontline Operations Per Emergence Capital, 80% of the global workforce is deskless. Yet most scheduling software has been designed for the 20% with assigned desks, calendar tools, and time between meetings to log into a browser-based system. For the other 80%—warehouse associates, clinical staff, retail employees—the schedule is not a productivity artifact. It is the primary interface between employer and employee. How it gets built, distributed, and adjusted determines whether that relationship is one of trust or managed frustration. MangoApps has added AI-powered scheduling and shift swap capabilities to its platform, now available through the MangoApps App Marketplace. But this analysis is not a feature announcement. It is about what the release actually changes for frontline operations leaders who live inside scheduling decisions every week—and why the scheduling layer is the correct place to start measuring employee experience in sectors where desk-based platforms have never achieved meaningful adoption. ## Why scheduling is where frontline trust gets built—or eroded Consider a district manager overseeing six retail locations. Each week, she builds schedules across 120 employees using two spreadsheets and a shared document, manually cross-references labor law requirements for two states, and fields 30 to 40 text messages from employees requesting shifts, trading coverage, and reporting last-minute absences. The schedule publishes Friday afternoon. By Monday morning, 15 percent of it has already changed. This is not an edge case. It is the default operating state for frontline teams that have not automated the scheduling layer. The cost is not only the time consumed by manual operations—it is the trust damage that accumulates when employees cannot see how their shifts are assigned, cannot easily trade with a colleague, and have no structured path for signaling availability constraints. Opacity in scheduling is one of the most underweighted contributors to voluntary turnover in shift-work environments. When employees experience scheduling as something that happens to them rather than something they can influence, the employer-employee relationship starts at a deficit before the first shift ever begins. The practical consequence shows up in absenteeism first—workers calling out because trading a shift was too cumbersome—and then in attrition data months later, after the accumulated frustration of invisible, unpredictable scheduling decisions has made leaving feel easier than staying. ## The three capabilities—and what they actually do in shift work management The release adds three distinct tools to MangoApps' existing [shifts and schedules](/solutions/shifts-schedules) foundation: **AI Smart-Schedule Builder** ingests employee preferences, skills, union rules, labor law constraints, and forecasted demand to generate an optimized draft. Managers review and publish rather than build from scratch. For organizations with configurable compliance rules by location—a requirement for multi-region or unionized environments—the engine applies those rules before the schedule reaches any manager's screen. **Shift Marketplace and Mobile Swaps** let employees pick up, drop, or trade shifts from any device. Auto-approval rules enforce compliance on routine exchanges without manager involvement. A swap that previously required three text messages, a callback, and a manual edit now resolves in two taps. Per Beekeeper's shift-swap benchmarks, automated shift-swap workflows reduce absenteeism on day one—a specific outcome the manual operations alternative cannot match because the friction itself drives the avoidance behavior. **Fairness Scoring** is the least obvious of the three features and potentially the most consequential for retention. Each employee receives a transparent score—based on seniority, attendance, and manager feedback—that the scheduling algorithm incorporates when distributing shifts. Workers can see their score and understand exactly how to improve it. That visibility changes the dynamic between the scheduling system and the workforce. When the logic is accessible rather than opaque, employees engage with scheduling as a system they can influence rather than one they must endure. Together, these three capabilities constitute a named shift work management layer embedded inside a broader employee experience platform—a distinction that matters more than it might appear at first. ## What changes when scheduling lives inside a unified platform Per IDC, employees spend an average of 2.5 hours per day searching for information they cannot easily find. In frontline environments, that search time concentrates around the highest-friction moments of the workday: confirming a shift start time, finding a colleague willing to cover, locating the policy that governs a swap request. When scheduling lives in a separate tool from task management, training, and team communication, every one of those moments requires switching context, logging into a different system, or sending a text to a supervisor. The MangoApps architecture puts scheduling, task coordination, training, and communication inside the same platform layer. A new hire can complete onboarding, view their first schedule, and request a swap without changing applications. That is a structurally different user experience than deploying a point solution alongside five other tools—and it produces structurally different adoption outcomes. Per Social Edge Consulting, 91% of organizations already operate an intranet. But only 13% of employees use it daily, and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools. Those figures describe what happens when organizations give frontline employees a platform designed for desk workers and expect the adoption curve to follow. A mobile-first scheduling system with built-in shift swaps and fairness scoring is not a scheduling module layered on top of a desk-worker intranet. It is a different product category serving a different user profile with different access constraints. ## Compliance without the manual review For organizations managing unionized workforces or multi-region teams, scheduling compliance is not a feature—it is a liability management requirement. A schedule that violates a collective bargaining agreement creates a grievance, a manager investigation, and potentially arbitration before any operational disruption even surfaces. The AI Smart-Schedule Builder applies configurable compliance rules per location before publication. A manager in a unionized distribution center in California and a manager in a non-unionized retail location in Texas can use the same platform with entirely different guardrails, without either having to manually consult an operations manual before publishing. [Managing a unionized workforce requires software that handles these rules differently](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too)—and the Smart-Schedule Builder is built with that constraint as a first-order requirement rather than a configuration footnote. The same architecture applies to HRIS and payroll integration. When scheduling syncs automatically with employee role data and availability, the manual data entry errors that generate overtime exceptions and payroll discrepancies are removed at the source rather than caught—and corrected—downstream. ## What frontline adoption looks like at scale Efficiency claims about scheduling automation remain directional without customer evidence. The [Raley's Companies case study](/resources/raleys-case-study) documents what this platform architecture produces at 20,000 employees across a regional grocery operation—a frontline workforce with complex shift patterns, no assigned workstations, and scheduling requirements that vary across store formats, departments, and seasonal demand shifts. The case provides a concrete reference point for buyers evaluating whether the unified-platform approach delivers different outcomes than the multi-tool alternative. For organizations actively evaluating scheduling and shift swap tools, three questions will sharpen the business case faster than any product demonstration: **First: How many tools does a manager currently touch to build, publish, and adjust a weekly schedule?** If the answer is more than two, consolidation produces immediate time savings and reduces manual operations errors before any AI optimization is applied. **Second: Which compliance rules are currently enforced by reviewing an operations manual?** Automated guardrails only deliver value if the platform's rule configurability matches your jurisdiction requirements. Request a demo scoped to your actual union agreements or state-specific labor laws, not a generic walkthrough. **Third: What does adoption look like in comparable customer deployments—specifically among workers without corporate email credentials?** That population is where the gap between a deskless-first platform and a desk-worker platform with a mobile wrapper becomes visible. Adoption rates among office workers with full enterprise licenses do not transfer to frontline environments where the onboarding and access model are fundamentally different. ## The schedule as a proxy for the employee relationship "For frontline employees, the schedule is the foundation on which trust is built," said Anup Kejriwal, CEO of MangoApps. "Your scheduling practices dictate the tenor of the relationship. If you don't cater to employee needs and preferences, people find other jobs." That framing is the correct lens for evaluating any scheduling technology investment. The specific features a platform offers—AI optimization, mobile swaps, fairness scoring—matter less than whether the system is designed for how frontline workers actually operate: starting from a personal mobile device, without a corporate email address, during the active working hours when they have the least availability for navigating a complex interface. A platform built for that operating profile produces different retention outcomes than one built for office workers and extended to frontline teams as an afterthought. Evaluating the difference requires asking for adoption data from the right population—not aggregate session metrics, but specifically among deskless workers in comparable industries. For HR and operations leaders building or refreshing their frontline technology stack, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) includes category benchmarks across scheduling, task management, and communication, with measurement frameworks for evaluating where your current stack leaves the most time, trust, and operational efficiency unrealized. --- # MangoApps Named a Strong Performer in June 2025 Gartner Peer Insights™ ‘Voice of the Customer’ for Intranet Packaged Solutions **Author:** MangoApps **Published:** 2025-07-01 **Category:** press-release MangoApps has been recognized as a Strong Performer in the June 2025 Gartner Peer Insights™ ‘Voice of the Customer’ for Intranet Packaged Solutions report. We're proud to share that MangoApps has been recognized as a Strong Performer in the June 2025 Gartner Peer Insights™ 'Voice of the Customer' for Intranet Packaged Solutions — with an Overall Rating of **4.7 out of 5** based on **58 verified reviews** as of July 1, 2025. This recognition comes directly from the IT and operations professionals who use MangoApps every day, making it meaningful in a way that analyst positioning or vendor-supplied benchmarks cannot replicate. For organizations currently evaluating intranet platforms — a decision that touches every employee in the business — the Gartner Peer Insights report is a practical resource for separating platforms with genuine customer satisfaction from those with well-funded marketing budgets. ## What the Gartner Peer Insights 'Voice of the Customer' actually measures The 'Voice of the Customer' report is not a traditional analyst ranking. Gartner applies a documented methodology to aggregate verified reviews submitted by end-user professionals on the Gartner Peer Insights platform. Reviewers must hold a qualifying role at a qualifying organization; Gartner validates submissions before they count toward any vendor's positioning. The resulting quadrant positions vendors on two axes: - **Overall Experience** — a composite of ratings across categories including product capabilities, sales experience, and support quality - **User Interest and Adoption** — a measure of review volume, geographic breadth, and willingness to recommend Vendors in the Strong Performer quadrant carry above-average Overall Experience scores. That means our customers — not Gartner analysts — placed us there through their direct, verified feedback. It's a peer-to-peer evaluation system, and it matters because it can't be gamed the same way that brand recognition or analyst relationships can. ## Why intranet satisfaction is harder to achieve than vendors imply Most organizations have an intranet. That doesn't mean most employees use it. Research from Social Edge Consulting found that 91% of organizations operate an intranet, yet only 13% of employees use it on a daily basis — and nearly a third never log in at all. The gap between deployment and adoption is where most intranet investments go to waste. The usage problem compounds quickly into a measurable productivity loss. According to IDC, employees spend an average of 2.5 hours each day searching for information — time that a well-adopted, well-organized intranet could significantly reduce. Across a 1,000-person organization, that's thousands of hours per week lost to search friction that better tooling could eliminate. For organizations with significant frontline and deskless workforces, the stakes are higher still. Emergence Capital estimates that 80% of the global workforce is deskless, yet most legacy intranet platforms were designed around office-based employees with a laptop and a stable broadband connection. Mobile experience, offline capability, and role-appropriate content filtering are all requirements that many platforms retrofitted rather than built from the start. When evaluating intranet platforms, IT and operations leaders need to look past feature lists and ask: what does adoption actually look like for customers twelve months after going live? ## What MangoApps customers highlighted in their reviews The themes that surface repeatedly in MangoApps reviews on Gartner Peer Insights point to a few consistent strengths. **Ease of use for both administrators and employees.** Reviewers routinely note that the platform is straightforward to configure without requiring developer resources, and that employees — including frontline staff with limited technical experience — can navigate it without formal training overhead. The setup time referenced in customer reviews suggests deployment timelines that don't require a months-long implementation engagement before employees see anything. **Mobile accessibility.** For organizations with field teams, manufacturing staff, or distributed workforces, mobile functionality isn't a differentiating feature — it's the primary interface. MangoApps' mobile experience appears as a consistent differentiator in customer feedback, particularly for roles where employees are never at a desk. **Flexibility that matches how different teams work.** Unlike platforms that impose a fixed information architecture, MangoApps lets teams configure workspaces, department sites, and communication channels to match how they already operate. That flexibility tends to drive adoption: employees use a tool that fits their workflow, not one they have to work around. **Support quality throughout the customer lifecycle.** Across reviews, customers call out MangoApps' implementation support and ongoing responsiveness as above industry norms — a meaningful signal given how often intranet deployments stall during rollout when vendor support falls short. These aren't claims we're making about ourselves. They're patterns in what customers chose to write when given an open text field and a verification process. ## What this recognition means for IT leaders evaluating intranet platforms today If you're currently evaluating intranet solutions, you're likely comparing three to six platforms against a requirements list that spans IT, HR, and operations priorities. Most vendors in this market can demonstrate a credible feature set during a demo. The harder question — the one that Gartner Peer Insights helps answer — is which platforms customers are still satisfied with after going live. Independent benchmarks paint a clear picture of the room for improvement in intranet adoption. Research has found that only 22% of company intranets currently deliver personalized content to employees at scale — which means even organizations with active deployments are frequently running platforms that employees experience as generic, hard to navigate, or disconnected from their actual role. Verified satisfaction scores from real customers become a meaningful differentiator when you're trying to choose a platform you won't be replacing in three years. For frontline-heavy organizations, the adoption benchmarks competitors publish are worth examining directly: leading platforms in this category report targets of 90–95% frontline adoption within six months as achievable for comparable deployments. When reviewing any intranet platform, ask vendors for adoption rate data from customers in your industry and at your organization size — license counts are not a proxy for engagement. The June 2025 report also comes at a moment when intranet evaluation criteria are shifting. AI-assisted search, personalized content delivery, and native integration with existing HR and operations systems are moving from differentiators to expected baseline capabilities. The Gartner recognition reflects where MangoApps stands today based on what customers experienced and chose to document. ## MangoApps in the broader recognition landscape This Strong Performer recognition is one of several independent evaluations we've received in recent cycles. MangoApps is also covered in the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report), one of the more rigorous hands-on evaluations in the intranet market, and was recently included in a leading research firm's [intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms). Independent assessors using different methodologies — peer review aggregation, analyst evaluation, and hands-on product testing — are reaching consistent conclusions about where MangoApps sits in the [modern intranet](/solutions/modern-intranet) landscape. For IT leaders building a business case or responding to a procurement process, having multiple independent data points from non-overlapping sources strengthens the evaluation considerably. On the customer evidence side, the [American College of Radiology case study](/resources/case-study-american-college-radiology) describes how one large healthcare organization used MangoApps to unify communication across a distributed employee base — the kind of deployment outcome that drives the peer ratings documented in this report. ## What a 4.7/5 rating means in practice for your evaluation A 4.7 out of 5 from 58 verified reviews is worth examining beyond the headline number. It tells you three things that are difficult to manufacture: customers are satisfied enough to complete a structured review process, satisfaction is consistent enough to average near the ceiling of the scale, and the review volume is substantial enough that the average isn't being driven by a handful of outliers or a coordinated review push. SWOOP Analytics benchmarked average daily active engagement with enterprise intranet tools at six minutes per day — a number that reflects how most platforms are actually used versus how they're positioned during procurement. Platforms that drive meaningful daily engagement require usability, content relevance, and technical reliability working together over time. A 4.7 average suggests those factors are operating correctly for the customers who took time to document their experience. When using Gartner Peer Insights reviews in your own evaluation process, filter for customers in your industry vertical and at your company size range. The experience of a 300-person professional services firm and a 20,000-person healthcare system will differ materially, and aggregate platform ratings can mask that variation. The platform's per-industry breakdown within the report provides a more targeted signal for evaluators with specific deployment contexts. ## Frequently asked questions ### How does the Gartner Peer Insights Strong Performer quadrant differ from the Magic Quadrant? They are separate research products with different methodologies and inputs. The Magic Quadrant reflects Gartner analysts' assessments of vendor strategy and market execution. The 'Voice of the Customer' report aggregates verified end-user reviews using a documented rules-based methodology. A vendor can appear in both, but the inputs are entirely different — analyst judgment versus customer-submitted ratings from verified practitioners. ### Can I read the full Gartner Peer Insights report? The June 2025 Gartner Peer Insights 'Voice of the Customer': Intranet Packaged Solutions report is available to Gartner subscribers. Individual MangoApps customer reviews are publicly visible on the Gartner Peer Insights platform and can be browsed and filtered without a subscription. ### What other independent evaluations has MangoApps participated in? MangoApps has been evaluated across several independent research programs in the past twelve months, including ClearBox Consulting's 2026 report and a leading research firm's intranet platforms evaluation. We encourage IT leaders to use multiple independent data sources — peer reviews, analyst research, and direct customer references — when building a complete vendor picture. ### What does 'Voice of the Customer' mean for an IT buyer? For a buyer, it means the quadrant placement is driven by the aggregated experiences of customers who went through procurement, implementation, and active use — not by the vendor's roadmap or market presence. Strong Performer status indicates above-average satisfaction across the customers who chose to review the platform, which is a useful starting point for understanding whether the product delivers on what it promises during the sales cycle. --- *Gartner, Gartner Peer Insights 'Voice of the Customer': Intranet Packaged Solutions, Peer Contributors, June 2025.* *Gartner and Peer Insights™ are trademarks of Gartner, Inc. and/or its affiliates. All rights reserved.* *Gartner Peer Insights content consists of the opinions of individual end users based on their own experiences and should not be construed as statements of fact. Gartner does not endorse any vendor, product, or service depicted in this content, nor makes any warranties, expressed or implied, with respect to this content, about its accuracy or completeness.* --- # Recognition in Rhythm: How symplr Wove Rewards into Their Intranet Experience with MangoApps **Author:** MangoApps **Published:** 2025-05-28 **Category:** customer-success-stories symplr folded rewards and recognition directly into their MangoApps intranet, turning scattered kudos into a visible, consistent program. With branded awards, point budgets, and thoughtful rollout, recognition now shows up on the newsfeed and sticks. Early outcomes: 1,500+ recognitions and 2M+ points in 2024. # Recognition in Rhythm: How symplr Wove Rewards into Their Intranet Experience with MangoApps For teams managing [rewards and recognition](/key-features/rewards-and-recognition) across a distributed workforce, the default outcome is inconsistency. Managers do their best — a gift card here, a public thank-you there — but without a shared system, appreciation stays invisible to the people who need to see it most. symplr, a healthcare governance, risk, and compliance company, solved this not by purchasing a standalone recognition platform, but by activating the recognition module already inside the intranet their employees used every day. In 2024 alone, that decision produced over 1,500 recognitions, more than 2 million points distributed, and nearly 900 employees receiving public shoutouts on their company feed. That outcome doesn't happen by accident. It happens when a team designs for culture first, deploys with discipline, and keeps working at it after launch. ## The problem with ad hoc recognition in distributed companies Only 23% of employees strongly agree they receive the right amount of recognition for the work they do, according to Gallup. That leaves the large majority of most workforces feeling underappreciated — not because managers don't care, but because informal recognition doesn't scale. symplr had exactly this dynamic before formalizing their program. Managers were expressing genuine appreciation through disconnected gestures: gift cards, surprise treats, one-off thank-you emails. The appreciation was real. But it wasn't visible beyond the immediate exchange, and it wasn't consistent across teams, locations, or job levels. Gratitude happened — it just didn't build culture. For a global workforce spread across the U.S., India, and beyond, this gap had consequences. Remote and distributed employees are disproportionately at risk of feeling invisible, and structured, visible recognition is consistently cited as one of the top three retention levers for fully remote teams, according to the [Gallup 2026 State of the Global Workplace report](/articles/gallup-2026-state-of-the-global-workplace). The stakes show up in turnover data too: companies with highly effective recognition programs see 31% lower voluntary turnover than those with ineffective ones, per Bersin by Deloitte research. symplr's team recognized the gap. The question was what kind of solution was actually worth building. ## Why symplr chose to build inside an existing platform The conventional answer to a broken recognition process is a new tool. symplr made a different call. Since 2021, symplr had been using MangoApps as the backbone of their intranet, symplr IQ — a central hub for internal communications, collaboration, and company culture. When the need for a more structured recognition approach surfaced, the team didn't go looking for a standalone recognition vendor. They activated the recognition module already available within MangoApps. The logic was about adoption, not just cost. According to SWOOP Analytics, the average employee spends just six minutes per day using intranet tools — and according to Social Edge Consulting, only 13% of employees use their intranet daily. A standalone recognition platform requiring a separate login would have encountered the same adoption friction as any other tool employees don't naturally reach for. By embedding recognition inside symplr IQ, the team removed that friction before the program launched. Employees didn't have to form a new habit; recognition became part of the digital rhythm they already had. Organizations that integrate recognition into a single digital workplace platform consistently report higher program participation rates than those running standalone tools, because employees don't have to context-switch to give or receive acknowledgment. symplr already had near-universal adoption of symplr IQ. That existing adoption was itself a strategic asset. As Melissa Hoyos, symplr's VP of Internal Communications, put it: "We wanted something very consistent across the board, and [MangoApps] was going to provide it to us." ## Designing the program before touching the software symplr spent several months on program design before any configuration started. The internal comms, talent management, and HR operations teams sat together and worked through hard questions: What behaviors should earn points? How do we prevent recognition from feeling performative? Who should have the authority to give points — and what happens if that authority creates a bottleneck at the wrong layer? They built awards that reflected symplr's own voice, not vendor-template language. Every award name connected to a stated company value. Kevin Williams, Director of HR Operations, worked through the complexity of a global point structure — ensuring that reward values felt equitable across countries with different purchasing power, without creating imbalances that would undercut the program's credibility across a workforce spread across the U.S., India, and beyond. "We wanted to make sure when we launched our R&R program that we launched it right," Williams explained. "We did not want to do several iterations of this, so we spent... several months internally making sure that we considered everything." Recognition programs tied to company values — rather than generic praise — are significantly more likely to drive the specific behaviors leadership wants to reinforce, according to SHRM and WorldatWork benchmarking research. symplr's investment in design reflected that principle. The awards weren't decoration; they were the mechanism for encoding culture. ## The launch: communication, training, and no surprises Before the program went live to the full organization, Emily Biery, Senior Internal Communications Specialist, led a three-part rollout strategy. The first track was a personalized email from the CHRO, repurposed as a company-wide intranet post explaining what the program was, why it existed, and how it worked. The second was live training sessions with senior leaders walking through their specific role in awarding points. The third was tailored sessions for HR business partners on reporting tools and how to coach their leaders on participation. Olivia Aguilar, symplr's Intranet Engagement Specialist, coordinated the entire launch — keeping timelines, communications, and training sessions aligned so nothing caught employees off guard. "Her coordination helped to ensure that there were no surprises for anyone," Biery noted, "and everyone knew what and when to expect updates and how to access support." The team also built a private resource space for point awarders — a place to find FAQs, look up which awards applied in which country, and stay current on any program updates. The goal was to give every person with recognition authority the ongoing support to use it well, not just on launch day. By treating the launch as a cultural milestone rather than a system deployment, they set the tone for long-term participation. ## What year one produced The program started with controlled access: senior and executive leaders received point-awarding authority first. The design logic was to establish norms before scale. In practice, recognition bottlenecked at the leadership layer. As Jami Mims, Director of Talent Management, described it: "It kind of got bottlenecked... just because they're, as we all are, moving fast and incredibly busy." The team's response was deliberate expansion. Rather than opening access broadly, they moved down one layer at a time. By year two, the program had grown from 30 point awarders to 70 managers — roughly 2.3 times the original coverage. The results in 2024 were concrete: over 1,500 recognitions issued, more than 2 million points distributed, and nearly 900 employees receiving acknowledgment visible on the company feed. Employees could log into symplr IQ and see recognition happening in real time — not in a spreadsheet, not in an email chain, but in the same feed they used for company news and team updates. The [employee engagement](/solutions/employee-engagement) signal in symplr's eNPS survey shifted alongside program adoption. "We're not seeing as many in our eNPS survey people saying things such as, 'Oh, we want to find a way to be recognized,'" Mims noted. "People see that they are being recognized. And so I know that that's positive." ## What teams building recognition programs can take from this symplr's experience maps to five principles that apply beyond their specific context. **Embed recognition into the system employees already use.** A standalone recognition tool will be adopted primarily by the employees who are already motivated to give recognition. Embedding it inside an existing intranet removes that selection effect — recognition becomes the obvious path, not an extra step. **Design for culture before configuring software.** The several months symplr spent on program design wasn't overhead. It was the reason the launch landed as a cultural signal rather than a routine HR rollout. Awards that sound like the company's own values do more work than generic ones. **Launch with controlled access, then expand deliberately.** Starting with senior leaders allowed for learning and course correction before scale. Expanding to 70 managers in year two created sustainable coverage without diffusing accountability. **Give awarders ongoing support.** Inactive awarders mean employees who aren't being recognized. HR business partners playing a coaching role — nudging leaders who haven't awarded recently, reminding them that points exist and should be used — sustained participation without requiring a separate management layer. **Measure leading indicators, not just outcomes.** Active awarder counts, participation rates, and eNPS comments about recognition tell you whether the program is working before the signal shows up in turnover or engagement scores. Waiting for lagging indicators means losing the window for early correction. For teams that want to understand how recognition fits into a broader employee engagement strategy, the full webinar with the symplr team is available at [From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program). Recognition that sticks isn't built by selecting the right software. It's built by the decisions made before the software is configured, maintained by the decisions made after launch, and sustained by the people with enough authority and enough support to make it a daily practice. --- # MangoApps Launches NewsFeed App For Microsoft Teams **Author:** MangoApps **Published:** 2025-05-15 **Category:** press-release MangoApps, the all-in-one AI-powered hub for employees, has launched its NewsFeed app for Microsoft Teams. # MangoApps Launches NewsFeed App For Microsoft Teams When a major workplace communication platform adds a new integration, the first question is whether it justifies the setup overhead. For the MangoApps NewsFeed app for Microsoft Teams, that question deserves a direct answer — and the answer depends almost entirely on who your organization has been failing to reach. The average desk worker switches between 11 applications a day, losing nearly four hours a week to context switching. Per IDC research, employees spend 2.5 hours daily searching for information they need to do their jobs. A company newsfeed inside Teams sounds, at first, like a convenience upgrade for people who already have too many windows open. It is solving a harder problem. The gap it closes is not between two apps. It is between the employees organizations can reach and the majority they have been structurally missing. That gap has a specific shape. It is not random. It maps almost exactly onto the 80% of workers who are deskless — who have no company laptop, no corporate email, no reason to remember a URL they never visit. Closing that gap requires a different infrastructure decision, not a better content strategy. ## Why reaching the full workforce is harder than it looks Per Emergence Capital research, approximately 80% of the global workforce is deskless — frontline staff in healthcare, retail, manufacturing, and logistics who rarely or never access a company-issued computer. Most corporate communication infrastructure was designed for the remaining 20%. The intranet data makes the scale of this miss visible. Per Social Edge Consulting, 91% of organizations operate an intranet. Only 13% of employees use it daily, and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends six minutes per day with intranet tools — a number that reflects not disengagement from the organization, but disengagement from a delivery channel that does not fit how most employees actually work. The consequences compound quietly. Employees who consistently receive irrelevant communications stop opening them. Employees who cannot access the platform at all never develop the habit of checking it. By the time attrition data surfaces the problem, the communication gap has been widening for months. And because the gap is structural — an access failure, not a content failure — producing better content does not fix it. ## How the NewsFeed app changes the access model The MangoApps NewsFeed app for Microsoft Teams is designed to work without a corporate email address or VPN — removing the two most common barriers that prevent frontline and distributed employees from receiving the same communications as their desk-based colleagues. That design choice is the structural difference between this and a standalone intranet portal: it meets employees in the environment where they already work, rather than adding another platform they need to remember to visit. Company news, department updates, employee recognition, and social engagement surface inside Teams as a personalized Recommended View — role-based, relevant, and without requiring a separate login. An in-app post viewer handles reactions and comments directly inside Teams. A built-in file viewer supports attachments while restricting downloads, preserving document security in environments where that matters. Consistency extends across Teams Web, Teams Desktop, Microsoft Outlook, and the broader M365 environment — so employees who move between devices and platforms encounter the same experience regardless of where they access it. ## How is this different from what Teams already does? Teams offers channel announcements, broadcast messaging, and Viva Engage for social communication. The NewsFeed app addresses what those tools are not designed for: cross-departmental visibility, company-wide recognition infrastructure, and personalized content delivery at the organizational layer. Teams' native messaging excels at workgroup coordination — it is designed for team-level communication. The NewsFeed app solves a different problem: getting company news, HR communications, recognition, and broader organizational context to every employee, including those who are not in a specific channel and would not be expected to monitor it. The targeting difference is consequential. Personalization is role-based rather than channel-based — employees in different roles, locations, or departments see content relevant to them rather than a single broadcast to everyone. Per SWOOP Analytics, employees disengage from communications that consistently do not apply to them, and that pattern of learned irrelevance is cumulative. Role-based delivery is what prevents the same dynamic that has kept standalone intranets active for 13% of employees while remaining largely invisible to everyone else. ## What does adoption actually look like? Adoption outcome data from organizations that have shifted to mobile-first, in-flow communication tools is consistent. OU Health achieved 87% workforce engagement within months of launching a branded employee app for clinical staff — not by rewriting their communication strategy, but by changing who could receive it. The structural variable was access, not message quality. The NewsFeed app supports a fully white-label deployment: organizations can launch it under their own brand identity rather than a vendor's name. That decision has measurable adoption consequences. Employees engage more readily with tools that carry their employer's identity than with generic third-party interfaces, and adoption data consistently shows this difference is real across frontline-heavy industries. Frontline employee replacement costs range from $4,400 to $15,000 per worker depending on role and industry. Disconnection from organizational communication — missing recognition, missing company updates, having no visibility into what the organization is doing — is a consistent early driver of disengagement, well before that replacement cost is incurred. A branded, in-flow communication experience removes one of the most common structural contributors to that disconnection. Organizations that solve the access problem first tend to see the retention benefit follow, because the cultural signals that drive engagement can finally land where they were always intended to. ## How does AI personalization work within the app? The Recommended View surfaces content based on role, location, and department rather than broadcasting the same message to every employee. Employees in different functions see updates relevant to their work. Employees on rotating shifts receive communications timed to their schedule rather than a default morning announcement. Employees in different regions see local news alongside company-wide updates. Per SWOOP Analytics, the six-minute daily average for intranet tools reflects the same learned irrelevance that role-based personalization is designed to prevent. When employees consistently encounter content that has nothing to do with their role, they stop checking. AI-curated delivery is not a convenience feature — it is what makes communication reach the people it was intended for rather than disappearing into unopened notifications. ## What are the technical requirements? The app works within existing Microsoft Teams deployments — no new infrastructure, no VPN requirement, no corporate email address required for access. Organizations need an active MangoApps account to configure and deploy. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers deployment patterns most relevant to distributed and frontline-heavy workforces, including how organizations with mixed desk and non-desk populations have structured their rollouts. White-label configuration is handled at the MangoApps admin level — the app can be named, branded, and scoped to specific employee populations before deployment. For organizations already using MangoApps' [employee communications platform](/solutions/employee-communications), the Teams integration extends existing capabilities into the Microsoft 365 environment without additional infrastructure changes. For organizations considering MangoApps for the first time, the [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study illustrates how a distributed, multi-role organization centralized communication across employee populations that traditional intranets had consistently missed. ## What about pricing and availability? The NewsFeed app is available now in the Microsoft AppSource Marketplace. Pricing is tied to existing MangoApps licensing — organizations already using MangoApps access Teams integrations as part of their current plan. Organizations new to MangoApps can explore the app via AppSource and connect with MangoApps directly for licensing terms aligned to their workforce size and structure. For organizations already running MangoApps alongside Outlook, SharePoint, or OneDrive, the Teams app extends an existing integration layer rather than adding a standalone product. The MangoApps + Microsoft Integration Guide maps the full connection points across Teams, Outlook, SharePoint, and OneDrive, covering both technical configuration and the use cases each integration supports. ## The reach question every organization should answer first The right question for evaluating the NewsFeed app is not whether the feature set is complete. It is whether the current communication infrastructure actually reaches the entire workforce. Per Social Edge Consulting, nearly a third of employees never log in to the intranet at all. For those employees — frontline workers, staff on rotating shifts, associates who access work from personal devices — an in-Teams newsfeed is not an upgrade to what they had. It is the first time the communication infrastructure reaches them. The [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) documents that organizations actively cultivating engagement demonstrate measurably better retention, productivity, and customer outcomes. The mechanism is access: when every employee can receive, respond to, and contribute to the organizational communication stream, engagement follows. When they cannot, no investment in message quality closes the gap. If the honest answer to "who does our current infrastructure actually reach" is "mostly desk workers," the MangoApps NewsFeed app for Teams is a structural fix — available in AppSource now. --- # Company Intranet: The Definitive Guide to Building a Connected, Productive Workforce **Author:** The MangoApps Team **Published:** 2025-05-08 **Category:** intranet This guide covers everything: what a company intranet is, why most fail, what the best ones look like today, how to build or improve one, and what to look for in company intranet software if you are evaluating solutions. 91% of organizations have a company intranet. Only 13% of employees use it daily. And 31% never log in at all ([Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics)). That gap — between having an intranet and having one people actually use — costs organizations millions in lost productivity, disengaged employees, and fragmented operations. McKinsey research shows employees spend 20% of their workweek just searching for information across disconnected systems. That's an entire day, every week, wasted looking for things that should be easy to find. The company intranet was supposed to fix this. For most organizations, it hasn't. But it can — when it's built for how people actually work now, not how they worked a decade ago. This guide covers everything: what a [company intranet](https://www.mangoapps.com/solutions/modern-intranet) is, why most fail, what the best ones look like today, how to build or improve one, and what to look for in company intranet software if you're evaluating solutions. ## What Is a Company Intranet? A company intranet is a private, internal digital platform where employees access information, communicate with each other, find resources, and get work done. Think of it as your organization's digital headquarters — the one place every employee goes to stay informed, connected, and productive. Unlike the public internet, a company intranet is accessible only to people within your organization. It's where policies live, company news gets published, HR forms get submitted, training gets completed, and teams collaborate without switching between a dozen different apps. That's the definition. The reality, though, depends entirely on what kind of intranet you're running. ### Traditional Intranets vs. Modern Intranets Traditional company intranets — the kind that first emerged in the mid-1990s — were essentially static websites behind a firewall. They housed documents, policy manuals, and maybe an employee directory. Content was published top-down by IT or communications teams, rarely updated, and almost impossible to search effectively. They required a desktop computer, a VPN connection, and often a company email address just to access. These intranets did their job for a while. But they weren't built for distributed teams, mobile devices, or the expectation that workplace tools should be as intuitive as the apps people use in their personal lives. [Modern company intranets](https://www.mangoapps.com/articles/what-is-a-modern-intranet/) look fundamentally different. They're cloud-based, mobile-first, and designed for every employee — including the 80% of the global workforce that doesn't sit at a desk ([HR Executive](https://hrexecutive.com/frontline-first-hr-engaging-the-80-that-powers-your-business/)). They incorporate AI-powered search, personalized dashboards, social features, integrated HR and operations tools, and real-time communication capabilities. They're not just a document repository; they're the digital backbone of how work gets done. The shift from traditional to modern isn't just a technology upgrade. It's a philosophical one: moving from "a place where the company publishes information" to "a platform where every employee finds what they need, connects with who they need, and gets work done — from anywhere, on any device." ([Learn more about the difference between intranets and employee apps](https://www.mangoapps.com/articles/how-an-intranet-differs-from-an-employee-app/).) ## Do Companies Still Use Intranets? Yes — overwhelmingly so. But the better question is: are they using intranets *well*? The company intranet is far from dead. The market for intranet platforms continues to grow, and industry analysts like Gartner, Forrester, and IDC all maintain active evaluation categories for intranet solutions. What has changed is what organizations expect from their intranet and what employees are willing to tolerate. Several forces are driving the continued — and in many cases, *increased* — relevance of company intranets: **The distributed workforce is permanent.** With remote, hybrid, and frontline workers spread across locations, time zones, and shifts, organizations need a central digital hub more than ever. Email alone can't hold an organization together. Neither can a patchwork of Slack channels, shared drives, and disconnected HR portals. **Tool sprawl has reached a breaking point.** The average knowledge worker switches between [11+ applications per day](https://www.ciodive.com/news/gartner-digital-worker-tools-IT/649844/), losing roughly [four hours per week](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) to context switching alone. Frontline workers, meanwhile, often have no digital tools at all — or worse, a mishmash of group texts, bulletin boards, and word of mouth. A [well-built company intranet](https://www.mangoapps.com/articles/what-is-mangoapps-the-unified-employee-hub) consolidates these scattered tools into a single hub. **Employee engagement is in crisis.** [Global engagement](https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx) sits at just 21%, according to Gallup. In the U.S., it has dropped to a [ten-year low of 31%](https://www.gallup.com/workplace/697850/state-of-the-global-workplace-regional-data.aspx#ite-708059). Disengagement costs the global economy $10 trillion annually — 9% of GDP. Organizations with strong internal communications are 4.5x more likely to have engaged employees, and the intranet is the primary vehicle for that communication. **AI is transforming what intranets can do.** The intranets that organizations deployed five years ago couldn't understand natural-language questions, surface personalized content, translate messages across 50 languages in real time, or serve as an intelligent assistant trained on company knowledge. Today's platforms can. That shift has reopened the business case for organizations that had written off their intranet as a failed experiment. The short answer: companies absolutely still use intranets. The ones getting real value from them, however, have moved well beyond the static portals of the past. ## Why Most Company Intranets Fail (And What to Do About It) If your company intranet has low adoption, outdated content, and a reputation as a digital ghost town, you're not alone. Industry benchmarks show that a "healthy" intranet sees 60–70% regular usage, yet most organizations fall well short of that. Only 39% of U.S. employees use their intranet regularly. The reasons are predictable — and fixable. ### 1. It Was Built for Desk Workers Only The single biggest failure mode for company intranets is [ignoring the frontline](https://www.mangoapps.com/articles/tips-to-improve-frontline-employee-engagement). If your intranet requires a desktop computer, a VPN, and a company email address, you've just excluded the majority of most organizations' workforces — the warehouse staff, retail associates, nurses, plant operators, and field technicians who keep the business running. Modern company intranet software must be mobile-first, accessible without a company email, and designed for people who have two minutes between shifts, not two hours at a desk. ### 2. Content Goes Stale Nothing kills intranet trust faster than outdated information. When an employee searches for a policy and finds a version from 2019, they stop trusting the system. When they stop trusting the system, they stop using it. When they stop using it, you've lost your investment. The fix isn't just "update more often." It's structural: automated content expiration dates, review workflows that prompt document owners, version history, and [AI-powered search](https://www.mangoapps.com/solutions/knowledge-management) that prioritizes the most current, relevant content. ### 3. It's Just Another Tool on the Pile If your intranet is one of 15 tabs employees have open, it's competing for attention it won't win. The most effective company intranets don't add to tool sprawl — they replace it. They bring communications, HR, knowledge management, task management, scheduling, and more into a single platform. When employees *have* to go to the intranet to clock in, check their schedule, find a policy, or complete training, adoption takes care of itself. ### 4. Search Doesn't Work Employees don't browse intranets. They search. And if your search returns irrelevant results, broken links, or nothing at all, you've lost them. AI-powered federated search — the kind that understands intent, searches across connected systems, and delivers direct answers rather than a list of documents — is now table stakes for any serious company intranet solution. ### 5. No Personalization A first-year nurse in Houston and a regional VP in Chicago shouldn't see the same intranet homepage. Role-based, location-based, and department-based personalization ensures every employee sees what's relevant to them — not a firehose of information meant for someone else. ## What Does a Great Company Intranet Look Like? Key Features The [best company intranets in 2026](https://www.mangoapps.com/articles/intranet-features-your-employees-will-love) share a common set of capabilities that go far beyond document storage. Here's what separates high-adoption intranets from digital graveyards. ### AI-Powered Search and Assistants This is the most transformative feature in modern company intranet software. AI-powered search understands natural-language questions ("What's our PTO policy for part-time employees in California?") and returns direct answers, not a list of PDFs to sift through. The best platforms go further with [AI assistants](https://www.mangoapps.com/ai) — enterprise chatbots trained on your company's own knowledge base, policies, and procedures. Employees ask questions and get instant, accurate answers without filing a help desk ticket or tracking down a manager. The impact is significant: organizations using AI-powered knowledge management report up to a 60% reduction in repeated questions and a 95%+ content findability rate. ### Mobile-First Design If your intranet doesn't work on a smartphone — natively, not through a clunky mobile browser — you're excluding the majority of the workforce. The best company intranet solutions offer [branded mobile apps](https://www.mangoapps.com/mobile) that work on personal devices, don't require a company email or VPN, and support offline access for employees in low-connectivity environments like warehouses, hospitals, or remote job sites. ### Multichannel Internal Communications A modern company intranet isn't just a website employees visit. It's a [communications engine](https://www.mangoapps.com/solutions/employee-communications) that reaches people where they are: push notifications, SMS, email digests, in-app alerts, and even digital signage. The best platforms support targeted messaging by role, location, department, or shift — so a safety update reaches the factory floor instantly while a benefits enrollment reminder goes to eligible employees only. Must-read acknowledgments with tracking and automated reminders ensure critical communications don't just get sent — they get seen. ### Integrated HR and Operations When HR tasks — [onboarding checklists](https://www.mangoapps.com/apps/onboarding), benefits enrollment, PTO requests, training modules, performance reviews — live inside the intranet, employees don't need separate logins for separate systems. The same applies to operational tools: shift scheduling, time and attendance, task management, and compliance workflows. The more essential work that happens inside the intranet, the higher adoption goes — not because you're forcing people to use it, but because it's genuinely where they get things done. ### Knowledge Management Every organization has institutional knowledge scattered across shared drives, email threads, Slack messages, and the heads of long-tenured employees. A company intranet should be the [single, searchable source of truth](https://www.mangoapps.com/use-cases/knowledge-management) for every procedure, policy, FAQ, and best practice. Wikis with version history, rich media support, inline comments, and smart review reminders keep knowledge current and accessible. ### Social and Community Features The intranets with the highest adoption don't just deliver information top-down. They foster [two-way communication](https://www.mangoapps.com/use-cases/employee-communication): discussion forums, recognition shout-outs, employee-generated content, comment threads on company news, and community groups organized by interest, location, or team. These social features drive belonging — and Deloitte research shows social intranets drive a 20% increase in employee satisfaction and an 87% increase in retention. ### Analytics and Measurement You can't improve what you can't measure. The best company intranet platforms include detailed [analytics](https://www.mangoapps.com/analytics-insights): content engagement rates, search success rates, newsletter open rates, adoption by department and location, and campaign performance. These insights let communications and HR teams iterate based on data, not guesses. ### Enterprise-Grade Security For organizations in regulated industries — healthcare, finance, manufacturing, government — [security isn't optional](https://www.mangoapps.com/security-compliance). Look for company intranet software with certifications like HITRUST, SOC 2 Type II, and ISO 27001. Single-tenant architecture (your data never co-mingled with other customers), granular access controls, and compliance-ready audit trails are essential for enterprise deployments. ## Company Intranet Examples: What Success Looks Like The difference between a struggling intranet and a thriving one isn't always about the technology — it's about how the platform is deployed, positioned, and embedded into daily work. For visual inspiration, see these [intranet design examples](https://www.mangoapps.com/articles/intranet-design-examples-to-inspire-your-work-hub). Here are patterns from organizations that have gotten it right. ### Healthcare: Connecting Clinicians Across Locations Healthcare organizations face a unique challenge: clinical staff are constantly moving, rarely at a desk, and working across shifts and locations. A successful company intranet in healthcare typically features a branded mobile app that nurses, technicians, and support staff can access from personal phones — no hospital email required. Critical communications (safety alerts, protocol updates, compliance training) are pushed directly to devices with must-read acknowledgments. The result: organizations like [OU Health](https://www.mangoapps.com/resources/harnessing-an-employee-superapp) have achieved 87%+ workforce engagement within months of deployment. ([See more customer stories](https://www.mangoapps.com/customers).) ### Retail and Grocery: Reaching Every Associate Retail workers are the definition of frontline — dispersed across hundreds of locations, often part-time, and rarely connected to corporate systems. The best retail company intranet examples use the platform as the single place associates check schedules, complete training, read company news, and communicate with store managers. When the [Kansas City Chiefs](https://www.mangoapps.com/resources/kansas-city-chiefs-case-study) deployed a modern intranet, they saw 90% adoption — double their previous system. ### Manufacturing: Digitizing the Plant Floor Manufacturing companies often struggle with a digital divide between the front office and the factory floor. Successful company intranet deployments in this sector focus on shift scheduling, safety communications, task management, and digital SOPs that replace paper binders. AI-powered translation supports multilingual workforces, and offline access ensures the platform works in areas with spotty connectivity. ### Professional Services and Financial Services: Consolidating the Stack For organizations where desk-based knowledge workers are the primary audience, the intranet value proposition centers on consolidation. Instead of bouncing between SharePoint for documents, Slack for messaging, Workday for HR, and a separate LMS for training, everything lives in one platform. This reduces the 4+ hours per week lost to context switching and gives IT a single, secure system to manage rather than a sprawling collection of point solutions. ## How to Build a Company Intranet: A Practical Roadmap Whether you're starting from scratch or replacing a legacy platform, building a company intranet that people actually use requires more than selecting software. It requires strategy, stakeholder alignment, and a realistic implementation plan. ### Step 1: Define Your Goals and Audience Before evaluating a single vendor, answer these questions: - **Who needs to use this?** Just desk workers, or your entire workforce including frontline? - **What problems are you solving?** Low engagement? Scattered information? Tool sprawl? Poor communication with the frontline? Compliance gaps? - **What does success look like?** Define specific, measurable outcomes: adoption rate targets, reduction in help desk tickets, improvement in engagement scores, time savings on information search. - **What tools will this replace?** The strongest ROI cases come from consolidation — sunsetting redundant tools and bringing their functionality into the intranet. ### Step 2: Get Stakeholder Buy-In Across Functions A company intranet touches HR, IT, communications, operations, and executive leadership. If only one team "owns" it, adoption will plateau. Build a cross-functional steering committee early. HR cares about engagement and onboarding. IT cares about security, integrations, and reducing tool sprawl. Comms cares about reach and targeting. Ops cares about scheduling and task management. When each team sees their priorities reflected in the platform, they'll champion it with their people. ### Step 3: Evaluate Company Intranet Software Not all company intranet solutions are created equal. Here's what to prioritize in your evaluation (for a deeper comparison, see our [guide to the top 25 intranet platforms in 2026](https://www.mangoapps.com/articles/top-25-intranet-platforms-in-2026)): **Frontline readiness.** Does the platform work on personal mobile devices without a company email or VPN? Does it support offline access? How many languages does it support? **Unification vs. fragmentation.** Does it replace multiple tools (communications, HR, knowledge management, scheduling, training), or is it just another point solution you're adding to the stack? **AI capabilities.** Is AI genuinely embedded — powering search, content recommendations, translation, scheduling, and assistants — or is it a bolt-on chatbot with limited functionality? **Integration depth.** How does it connect with your existing systems (HRIS, payroll, Microsoft 365, Google Workspace, ServiceNow, etc.)? Are integrations pre-built or do they require custom development? **Security and compliance.** What certifications does the vendor hold? Is the architecture single-tenant or multi-tenant? How is data encrypted and governed? **Implementation timeline and support.** How long does a typical deployment take? What does the vendor's customer success model look like? Do you get a dedicated team, or a help center link and a "good luck"? **Adoption track record.** Ask for specific adoption metrics from reference customers. Any vendor can show a polished demo; the real question is whether employees at similar organizations are actually using it every day. ### Step 4: Plan for Change Management Technology is the easy part. The hard part is getting people to change their habits. A strong change management plan includes executive sponsorship (visible leadership usage), a network of internal champions across departments and locations, a phased rollout that starts with high-value use cases (like shift scheduling or a major company announcement), and targeted onboarding for different user groups. The most successful company intranet launches don't try to boil the ocean on day one. They start with a few essential workflows that give employees an immediate reason to log in — then expand from there. ### Step 5: Launch, Measure, Iterate Set clear benchmarks for adoption, engagement, and content health from the start. Monitor analytics weekly in the early phases. Identify departments or locations with low adoption and intervene early — often the issue is local awareness or a missing use case, not a platform problem. Celebrate wins publicly (share adoption milestones, highlight active users, showcase content that's driving engagement) to build momentum. ## How to Improve a Company Intranet That's Already Struggling If your current company intranet has low adoption or a poor reputation, don't assume you need to rip and replace (though sometimes you do). Start with a diagnosis. ### Audit Your Content Conduct a full content audit. How much is outdated? How much is duplicated? How much is undiscoverable? Set up a content governance framework with clear ownership, review cycles, and expiration dates. Remove or archive everything that's stale. A smaller, current, trustworthy knowledge base is infinitely more valuable than a bloated one full of outdated documents. ### Fix Search If employees can't find what they need in under 30 seconds, your search is broken. Evaluate whether your platform supports AI-powered search with natural-language understanding. If it doesn't, that alone may justify a platform switch. If it does, make sure your content is properly tagged, categorized, and structured so search can surface it effectively. ### Make It Mobile If your intranet isn't mobile-accessible — or if the mobile experience is a degraded version of the desktop — you're leaving your frontline behind. Prioritize a platform that offers a native mobile app with push notifications, offline access, and no requirement for a company email. ### Embed Essential Workflows The single most effective way to improve intranet adoption is to make it the place where essential, everyday tasks happen. When employees check their schedules, submit PTO requests, complete required training, and access their pay stubs inside the intranet, they don't need to be convinced to use it. They just do. ### Add Social and Recognition Features Two-way communication transforms an intranet from a corporate bulletin board into a community. Discussion threads, shout-outs, employee-generated content, and pulse surveys give people a reason to come back — not just to consume information, but to participate. ### Measure and Communicate Progress Share adoption metrics with leadership and with employees. When people see that usage is growing and that their feedback is being incorporated, momentum builds. When adoption stalls in a particular group, dig into why — it's almost always a solvable problem. ## Choosing the Right Company Intranet Solution The company intranet market has matured significantly. Solutions range from lightweight communication tools to comprehensive workforce platforms that unify intranet, HR, operations, and AI in a single hub. When evaluating company intranet software, the most important question isn't "which platform has the most features?" It's "which platform will our employees actually use every day?" Here's a framework for making that decision: **If your workforce is primarily desk-based and already invested in Microsoft 365**, a SharePoint-based intranet or a [platform with deep Microsoft integration](https://www.mangoapps.com/integrations/microsoft) may be a fit — though be aware of the complexity and IT overhead SharePoint typically requires. **If you have a significant frontline or deskless workforce**, you need a platform built for mobile-first, no-email-required access. This is where many traditional intranets fall short, and it's the most important differentiator for healthcare, retail, manufacturing, hospitality, and logistics organizations. **If tool sprawl is your primary pain point**, look for a [unified platform](https://www.mangoapps.com/platform) that consolidates communications, knowledge management, HR, operations, and AI into one hub — rather than adding yet another point solution to an already crowded tech stack. **If AI is a strategic priority**, evaluate how deeply AI is embedded in the platform. Is it powering search, content recommendations, scheduling, translation, and custom assistants? Or is it a surface-level chatbot with limited capabilities? The difference between "AI-native" and "AI-adjacent" matters more with each passing year. ## How MangoApps Approaches the Company Intranet MangoApps is an AI-Powered Unified Workforce Platform that takes a fundamentally different approach to the [company intranet](https://www.mangoapps.com/solutions/modern-intranet). Rather than offering a standalone intranet that sits alongside your other tools, MangoApps unifies communication, knowledge, HR, operations, and AI in a single hub — built for the entire workforce, from headquarters to the frontline. **One platform, not another point solution.** MangoApps replaces 4–5 fragmented tools with one unified system. Intranet, employee app, internal comms, knowledge management, shift scheduling, time and attendance, task management, LMS, performance management, and enterprise AI — [all in one place](https://www.mangoapps.com/key-features). Customers consistently sunset other tools after implementation. **Built for the frontline first.** No company email, VPN, or desktop required. A branded mobile app with push notifications, offline access, and 50+ language translations reaches the workers that traditional intranets leave behind. Organizations like AutoZone, PetSmart, TeamHealth, and YMCA trust MangoApps to connect their entire workforce. **AI that's embedded, not bolted on.** The MangoApps Enterprise AI Hub gives every employee an intelligent assistant trained on company knowledge — with retrieval-augmented generation (RAG), role-based access, and enterprise security controls. AI powers search, content summaries, scheduling, translation, and custom no-code assistants. Your enterprise data never trains public models. **Proven adoption at scale.** MangoApps customers achieve 90%+ adoption rates within 90 days. That's not a marketing claim — it's backed by a 98% customer retention rate, a Net Promoter Score of 78, and recognition from Gartner (Magic Quadrant Visionary, 2025), IDC (MarketScape Leader, 2025), and Forrester (Strong Performer, Q2 2026). **Enterprise security, without the enterprise complexity.** MangoApps is the only unified workforce platform certified with HITRUST, SOC 2 Type II, and ISO 27001 combined. Single-tenant architecture means your data is never co-mingled. And typical implementation takes just 8–12 weeks with a dedicated cross-functional support team. **200+ integrations with your existing systems.** Connect Workday, SAP, UKG, ADP, Microsoft 365, Google Workspace, ServiceNow, and more — with pre-built, two-way data syncs. MangoApps works with your existing tech stack, not against it. 2M+ users worldwide trust MangoApps to make work run smoothly for everyone. Organizations across healthcare, retail, manufacturing, hospitality, financial services, and nonprofit sectors use the platform to connect, engage, and manage their workforce in one intelligent hub. ## The Bottom Line A company intranet is only as valuable as its adoption — and adoption is a function of design, not just technology. The organizations getting real value from their intranet have moved beyond static portals and disconnected tools. They've invested in a platform that meets every employee where they are, unifies the tools and workflows that matter, and earns daily usage by being genuinely useful. The bar has been raised. AI-powered search, frontline-first mobile access, unified HR and operations, enterprise security, and measurable adoption outcomes aren't aspirational — they're what leading organizations expect from their company intranet software today. If your current intranet isn't meeting that bar, it might be time to rethink it. [See how MangoApps can transform your company intranet → Request a demo](https://www.mangoapps.com/schedule-a-call) ## Frequently Asked Questions About Company Intranets **What is a company intranet?** A company intranet is a private, internal digital platform where employees access information, communicate, find resources, and complete work tasks. Modern company intranets go beyond static document repositories to include AI-powered search, mobile apps, integrated HR and operations tools, social features, and targeted internal communications. **Do companies still use intranets?** Yes — 91% of organizations have an intranet (Social Edge Consulting, 2025). The category has evolved significantly, with modern platforms replacing legacy systems to address distributed workforces, tool sprawl, and employee engagement challenges. Analyst firms like Gartner, Forrester, and IDC continue to evaluate and rank intranet solutions as a critical enterprise category. **How much does a company intranet cost?** Costs vary widely depending on the platform, organization size, deployment model, and required features. Cloud-based SaaS intranets typically charge per user per month, with prices ranging from a few dollars per user for basic communication tools to higher per-user costs for unified platforms that include HR, operations, and AI capabilities. The total cost of ownership should factor in the tools the intranet replaces — consolidating 4–5 separate platforms often results in net savings. **How long does it take to implement a company intranet?** Implementation timelines vary by platform complexity and organizational size. Some lightweight tools can launch in weeks; comprehensive unified platforms typically deploy in 8–12 weeks with a dedicated implementation team handling configuration, migration, integrations, branding, and training. **How to build a company intranet?** Start by defining your goals, audience, and success metrics. Get cross-functional stakeholder buy-in from HR, IT, communications, and operations. Evaluate company intranet software based on frontline readiness, unification capabilities, AI depth, integration breadth, security certifications, and vendor support. Plan for change management with executive sponsorship, internal champions, and a phased rollout focused on high-value use cases. Launch, measure, and iterate. **How to improve a company intranet?** Audit and clean up outdated content. Fix or upgrade search capabilities (AI-powered search is now table stakes). Ensure mobile accessibility for frontline workers. Embed essential daily workflows (scheduling, PTO, training) so employees have a reason to log in. Add social and recognition features for two-way engagement. Measure adoption by department and location, and address gaps with targeted interventions. **Should I build a custom intranet or buy a platform?** For the vast majority of organizations, buying a purpose-built platform is the better choice. Custom-built intranets require ongoing engineering resources, security maintenance, and feature development that few internal teams can sustain. Modern company intranet solutions offer extensive configurability, branding, and integration options that deliver the "custom" feel without the custom cost and risk. --- # Smarter, Sharper Communication: Enhancements That Drive Engagement and Clarity **Author:** MangoApps **Published:** 2025-05-05 **Category:** news-and-updates With the MangoApps 19.0 release, we’re introducing major enhancements to how organizations create, deliver, and measure communication across the digital workplace. These updates help companies deliver smarter, more personalized communication — making sure every message is targeted, timely, and impactful, without adding to the noise. # Smarter, Sharper Communication: Enhancements That Drive Engagement and Clarity Per IDC, employees spend 2.5 hours each day searching for information. Per SWOOP Analytics, they spend six minutes daily using their intranet. That gap — 150 minutes of searching in scattered channels against six minutes in the governed hub — is not a measure of employee habits. It is a measure of relevance. When an intranet's feed aggregates updates for an entire organization without filtering by role, location, or shift, employees in any specific context quickly learn that most of what appears there doesn't apply to them. The rational response is to check less often, or not at all. Per Social Edge Consulting, 91% of organizations run an intranet, but only 13% of employees use it daily, and nearly a third never log in at all. MangoApps 19.0 addresses four structural causes of that relevance failure: how notifications signal urgency to deskless workers, how feeds surface role-appropriate content without manual upkeep, how targeting rules stay accurate as the workforce changes, and how communication teams learn whether their campaigns are actually working. ## The relevance failure is structural, not behavioral Per Emergence Capital, 80% of the global workforce is deskless — working in manufacturing, healthcare, retail, and logistics where desktop access is intermittent and the push notification on a mobile screen is often the first and only time an employee encounters a communication. If that notification reads as a truncated policy headline, it will not be opened. If the feed it leads to is full of announcements from departments unrelated to the employee's location and shift, the habit of checking fades within weeks. Training employees to use the intranet more often does not resolve this — it just creates frustration more efficiently. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents what differentiates platforms that achieve sustained daily use: content calibrated to role, location, and schedule, not a single version distributed uniformly. The 19.0 release extends MangoApps' capabilities in each of those dimensions. ## Custom post notifications: writing for the moment, not the archive An internal announcement titled "Q3 Benefits Enrollment — Deadline Reminder" is accurate and forgettable. The notification copy that reaches a field technician between jobs needs to work differently than a policy headline. It needs to signal that action is required and that the window is closing. MangoApps 19.0 allows communicators to write email subject lines and mobile push notification text independently from the post title. The post retains whatever formal headline the documentation requires. The notification gets written for the moment and context in which it will actually be seen — on a locked screen, between tasks, at the end of a shift. For the 80% of workers who encounter internal communications first through a mobile notification, this separation is the difference between a message that registers and one that gets swiped away before the subject line finishes rendering. ## AI-personalized news feeds: role-appropriate content without manual configuration Per the State of the Digital Workplace and Modern Intranet 2024 report, only 22% of company intranets currently deliver personalized content to employees. The remaining 78% serve the same feed to everyone — which explains why the 13% daily usage rate in Social Edge Consulting's research holds consistently across industries and platform generations. MangoApps 19.0 extends the platform's feed personalization with more precise admin controls over how AI-curated content is distributed across employee segments. Administrators configure content weighting by department, role, location, hire date, shift type, and engagement history. The feed reflects each employee's actual context without requiring anyone — employee or administrator — to maintain it manually. For a workforce where a field technician logging in between routes and a corporate HR analyst at a desk have genuinely different information needs at that moment, a single feed calibrated for neither will gradually stop being checked by both. The 19.0 configuration tools let administrators build distinct experiences for each without maintaining separate platform deployments. ## Dynamic post targeting: audience rules that maintain themselves MangoApps 19.0 adds dynamic logic to post targeting — rules that resolve against live employee data at send time, not against a saved list that was accurate when it was built last quarter. A campaign targeting "all hourly employees at U.S. facilities hired before January 2025" generates the correct recipient list on the day it sends. Any scheduled follow-up pulls fresh data automatically. Benefits enrollment reminders, compliance certification campaigns, and policy acknowledgment sequences no longer require rebuilding a distribution list each cycle. The [Gallup 2026 State of the Global Workplace research](/articles/gallup-2026-state-of-the-global-workplace) connects employee perception of communication relevance directly to engagement and retention outcomes — not as a secondary effect, but as a primary driver. Dynamic targeting reduces the frequency of communications employees perceive as not meant for them, which improves open rates in the short term and trust in the communication channel over time. ## Campaign analytics with click maps: from delivery data to behavior data Knowing that 68% of a campaign audience opened an email answers whether the subject line worked. It does not answer whether the call to action registered, which link employees actually clicked, or whether the message hierarchy matched how employees read it. MangoApps 19.0 adds a click map visualization to the campaign engagement dashboard. Communication teams can see precisely where within a campaign email employees interacted with content — which sections held attention and where it dropped off. If the "submit form" button in a compliance campaign receives four times the clicks of the "learn more" link, subsequent campaigns lead with the action and compress the explanatory context. If engagement drops after the second paragraph, the team knows to restructure the message hierarchy. The data is available within the platform without requiring additional analytics tooling or data exports. The same release allows campaign audiences to be built by pasting email addresses or employee IDs directly — removing the IT step that previously blocked one-off cohort campaigns. For a full picture of how MangoApps handles communication across a distributed workforce, the [employee communications solution page](/solutions/employee-communications) covers the complete capability set across posts, campaigns, alerts, and personalized feeds. ## Getting started: the highest-leverage entry points The 19.0 enhancements activate within the existing admin interface without custom development or IT work. The operational questions are which features to configure first and what outcomes to measure. **Notification customization:** Start with campaigns that have a required-action outcome — benefits enrollment, policy acknowledgment, certification renewal. These are the communications where the gap between "sent" and "acted on" is most visible and most costly. Write the notification copy as a direct message to the employee at the moment they will see it, not as a headline for an archival post. **AI feed configuration:** Begin with the employee segment showing the lowest current engagement — typically frontline or deskless workers with limited desktop access. Configure weighting for that segment first, then measure feed engagement over a 30-day baseline before expanding to other groups. Role and location fields in the employee record are sufficient for meaningful initial segmentation without a full org chart audit. **Dynamic targeting:** Identify two or three recurring campaigns that currently require manual list rebuilds — typically compliance sequences or role-specific enrollment communications. Convert those first. The operational savings are immediate and the targeting accuracy improvement is measurable within the first send cycle. **Click map analytics:** The most useful first session is reviewing a campaign that already underperformed. Where did attention fall off? Which call to action was ignored? The answer usually points directly to the structural change worth making in the next campaign. The [American College of Radiology case study](/resources/case-study-american-college-radiology) shows what this shift looks like in practice: role-specific communication delivered through a configured platform, producing consistent engagement rather than periodic spikes around major announcements. ## What to expect in the first 90 days Notification customization shows its effect in open rates within the first campaign cycle that uses it. The effect is most pronounced for deskless workers, where the push notification is the primary initial touchpoint rather than one of several ways a message might reach them. Feed personalization shows results more gradually, as the AI calibrates to each segment's engagement signals. Thirty days is a reasonable point to compare feed engagement for a configured segment against its pre-configuration baseline. The change tends to be visible in session depth — employees staying longer and opening more posts — before it shows up in monthly active user counts. Dynamic targeting's value is often invisible in dashboards: lists that no longer require manual rebuilds, compliance campaigns that reach exactly the right employees without an IT ticket, follow-up messages that go to the correct current cohort rather than a stale snapshot. The absence of overhead is easy to undercount until it disappears. Click map analytics compound over time. The first campaign reveals where attention falls off. The second, restructured around that finding, shows whether the change worked. After three or four cycles, communication teams have a working model of how their audience actually reads — not just whether they opened the email. ## The measure that matters Monthly active users tells organizations whether employees are logging in. It does not tell them whether the communication infrastructure is working. The measure that matters is the share of targeted employees who see a relevant message in a governed channel and take the intended action within the campaign window. That metric improves when notification copy is written for the context in which it will be seen, when feed content is configured for the role rather than the organization, when targeting logic stays current with live employee data, and when click behavior informs the design of the next campaign. Per IDC, employees spend 2.5 hours per day searching for information they cannot find in one place. Per SWOOP Analytics, they spend six minutes using the tools built to surface it. The gap closes when those tools are configured to deliver content employees actually need — not when employees are trained to check more often. The 19.0 release provides the configuration instruments. How much of the gap closes depends on how deliberately those instruments are used. --- # MangoApps Recognized as a Top 100 Knowledge Management Company for 2025 **Author:** MangoApps **Published:** 2025-03-07 **Category:** press-release MangoApps has been named to the KMWorld 100 Companies That Matter in Knowledge Management for 2025! Every year, KMWorld publishes a list of the 100 companies it considers most influential in knowledge management. For 2025, MangoApps is on that list. What the recognition signals about where this category is heading — and what it means for organizations actively evaluating platforms — is worth examining beyond the headline. KMWorld's selection is editorial, not paid or user-voted. Companies must demonstrate technological leadership, a strong market presence, and a proven ability to solve critical knowledge management challenges at scale. The list has been published annually for decades; inclusion means a vendor has been assessed against the full scope of what the category demands, not a narrow product claim. For the 2025 cycle, that scope has widened considerably: AI-powered search, frontline workforce access, content governance, and cross-system integration are now evaluation criteria alongside the document management capabilities that defined the category ten years ago. That expansion is not coincidental. It reflects where organizations are actually losing the most time and money — and where the cost of inadequate knowledge infrastructure is now documented at scale. ## What KMWorld measures — and why it matters to buyers The KMWorld 100 is a curated list, not a ranked leaderboard. The editorial frame is not "which vendor is best in a single feature set" but "which vendors are reshaping how organizations manage and use knowledge across the enterprise." That framing has practical implications for buyers deciding how to weight independent recognition in an evaluation. A vendor that appears on the KMWorld 100 has been assessed across the full scope of what organizations need from a knowledge management platform — not a single capability like search or document storage, but the end-to-end problem of ensuring the right information reaches the right person at the right moment. We were recognized because our platform addresses knowledge access as an infrastructure problem. Most organizations call their SharePoint deployment a knowledge management system. What the KMWorld evaluation identifies is a different architecture: one where the question is not "where is the document stored?" but "can the person who needs it find it, in the moment they need it, from any device, without a manager making a phone call to bridge the gap?" That distinction matters most at the edges of the workforce. It is straightforward to build a knowledge system for employees who sit at desks with company laptops and corporate email addresses. The harder problem is reaching the other 80%. The KMWorld evaluation recognizes vendors who have addressed the full workforce, not just the desk-worker subset — and it is worth understanding that distinction when reading any recognition in this category. For organizations actively evaluating platforms, this recognition — alongside independent analyst coverage in a [leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) — is a signal worth incorporating. Vendors that appear consistently across multiple independent evaluation frameworks carry lower implementation risk and demonstrate longer-term platform viability than those appearing in only one. The pattern of recognition across overlapping evaluation categories is itself data. ## The access gap behind the recognition The problem at the center of the KMWorld recognition is consistent across industries and documented at scale. Per IDC, the average employee spends 2.5 hours per day searching for information they need to do their jobs. Per Social Edge Consulting, 91% of organizations operate an intranet — but only 13% of employees use one daily, and nearly a third never log in at all. Per SWOOP Analytics, the average daily time an employee spends using intranet tools is six minutes. These figures describe employees who have full system access. For the 80% of the global workforce that is deskless, per Emergence Capital, the gap is structural rather than behavioral. Frontline workers in distribution, healthcare, retail, and field operations often lack corporate email addresses and company-issued devices. The platforms most organizations call their knowledge management system are inaccessible to those employees — not because they are disengaged, but because the infrastructure was designed for the office and never extended to the warehouse floor, the hospital unit, or the field vehicle. The consequences compound in two directions. First, the productivity cost: employees who cannot find what they need improvise, ask managers, or proceed without it — all of which are slower, more error-prone, and harder to audit than a functioning knowledge system would be. Second, the retention cost: persistent exclusion from organizational communication and information systems is a reliable early indicator of disengagement. Replacing a single frontline employee costs between $4,400 and $15,000, per industry data. That converts workforce disconnection from a culture concern into a direct balance-sheet risk. Our [knowledge management solution](/solutions/knowledge-management) is built to close that gap structurally. The platform is mobile-first and does not require a corporate credential to access. A warehouse associate, a clinical technician, a retail store employee — all of them can reach the same knowledge infrastructure as the headquarters employee, through the same application, on a device they already carry. That access architecture is what the KMWorld evaluation recognizes: not a feature, but an infrastructure decision that changes who gets to be informed. ## What our customers have demonstrated Recognition earns credibility only if the underlying platform produces measurable results. The outcome data from our deployments is specific. PetSmart deployed a MangoApps-branded mobile application across its workforce and achieved 4x industry-standard employee engagement, per MangoApps case studies. OU Health reached 87% workforce engagement within months of launch — not years — after extending a unified mobile platform to clinical and administrative staff who had previously been excluded from the organization's digital systems. The outcome followed an access change, not a cultural initiative: when employees could reach the platform, engagement followed. TeamHealth consolidated more than 200 disparate systems into a single MangoApps mobile dashboard, demonstrating that integration breadth and rapid deployment are not in tension. The security infrastructure behind these deployments is a precondition, not a marketing claim. MangoApps holds SOC 2 Type II and ISO 27001 certifications, with compliance controls designed for healthcare, government, and financial services environments where ungoverned content carries direct regulatory risk. Organizations like AutoZone, the Kansas City Chiefs, and US Infrastructure Company have deployed at scale because the platform meets the security baseline those industries require. Vendors including Unily have positioned AI-native deployment speed as their primary differentiator, citing benchmarks like 90% frontline adoption within six months in published case studies. Our deployment data is comparable: OU Health and PetSmart reached high adoption thresholds within months. TeamHealth's consolidation of more than 200 systems illustrates that integration complexity does not extend the deployment timeline when the architecture is designed to absorb it. ## Why knowledge management now spans three categories The 2025 KMWorld 100 reflects a structural shift in how this market has evolved. Intranet platforms, employee engagement software, and knowledge management tools are converging. Organizations that treat these as separate purchasing decisions are buying the same underlying infrastructure three times, often with integration gaps between them that create the very knowledge silos they were trying to solve. Our platform competes across all three: structured knowledge organization through searchable document libraries and governance-enabled knowledge bases; communication and culture features that drive daily engagement at the team and department level; and navigation, search, and content governance built for the full workforce. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) evaluates platforms in this converged category across criteria that now span employee communication, search and findability, governance, and frontline accessibility — not just document storage. MangoApps was assessed across all four. The operational significance of that convergence is concrete. When the knowledge management system and the employee communication platform are the same infrastructure, a compliance or safety update does not require a separate workflow to reach frontline employees. It reaches them through the same application where they read company news, submit requests, and check their schedules. That integration reduces both the time-to-inform and the error rate in high-stakes communication — which is why the adoption outcomes our customers report follow access changes rather than training programs. For HR and operations leaders thinking about how knowledge access connects to the workforce outcomes their leadership is tracking, the pattern is consistent across deployments: when the access layer closes and every employee can reach the platform without a corporate email or a VPN, engagement follows. That is the structural outcome the KMWorld recognition reflects — not a feature roadmap, but a deployment outcome that organizations can replicate. ## What the recognition means for buyers evaluating platforms today The KMWorld recognition answers one question: has MangoApps demonstrated the technological leadership and market presence to be taken seriously as a knowledge management vendor in 2025? The more important question for your organization is whether our platform closes the specific gaps you are trying to close. The diagnostic starts with your current numbers. If employees are spending more than an hour a day searching for information that should take minutes to find, that is a calculable productivity loss — one you can estimate against headcount and average hourly cost before any platform conversation begins. If intranet adoption is below the 13% daily-use threshold Social Edge Consulting documents as the industry norm, the platform is not functioning as a knowledge system; it is functioning as a document archive that most employees do not access. If frontline workers cannot receive a time-sensitive compliance or safety update within one hour without a manager making a series of phone calls, that is a technology gap with a known solution. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) provides benchmarks for assessing where your current knowledge and communication infrastructure stands against those thresholds — a useful starting point before a formal platform evaluation. The ClearBox report adds independent assessment of how MangoApps and comparable platforms perform across the full evaluation framework, including the frontline accessibility criteria that most intranet evaluations still treat as secondary. The KMWorld 100 recognition reflects what our customers have consistently demonstrated: 4x engagement at PetSmart, 87% workforce adoption at OU Health, more than 200 systems consolidated at TeamHealth. Those outcomes earned the recognition. For organizations with a significant frontline workforce, an intranet adoption problem, or a compliance requirement that limits how knowledge infrastructure can be deployed, the outcome data is the signal worth examining. The award is confirmation that the knowledge management category has recognized it. --- # Inside the ClearBox 2025 Report: Comprehensive Reviews and MangoApps’ In-Depth Analysis **Author:** MangoApps **Published:** 2025-01-29 **Category:** industry-insights In-depth MangoApps review, and comprehensive overviews of popular Intranet and EX platforms. # Inside the ClearBox 2025 Report: Comprehensive Reviews and MangoApps' In-Depth Analysis Intranet selection has a structural problem: every vendor claims to be mobile-first, AI-powered, and purpose-built for the frontline — and those claims are indistinguishable until someone tests them under standardized conditions. The ClearBox Consulting 2025 Intranet and Employee Experience Platforms Report does exactly that. Now in its tenth year, the report evaluates platforms across a fixed set of scenarios and publishes the scores. No platform chooses which scenarios it gets measured on. That independence is what makes the results actionable: per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in and only 13% use it daily. The ClearBox report exists to identify platforms that close that gap — not platforms that perform well in demos and poorly in deployment. MangoApps' full review appears on page 344 of the 2025 edition. This post walks through what the scores mean and why they predict outcomes for organizations with frontline-heavy or communications-intensive workforces. ## The adoption problem analyst reports are designed to solve Per IDC, employees spend 2.5 hours each day searching for information they need to do their work. Per SWOOP Analytics, the average daily time employees spend on a company intranet is six minutes. These figures coexist because most intranets were built around a specific profile: an employee with a corporate email address, a desktop workstation, and IT provisioning available when access problems arise. The software is capable for that profile. It systematically underserves everyone else. Per Emergence Capital, 80% of the global workforce is deskless. Frontline workers at healthcare systems, retailers, manufacturers, and logistics operators interact with technology on personal devices, between shifts, without VPN access or a help desk standing by. A platform that earns strong scores on communications management for office environments can score poorly on mobile and frontline scenarios — and that gap is what most intranet evaluations miss when they rely on vendor demonstrations rather than independent testing. ClearBox solves this by measuring platforms on scenarios that reflect how employees actually work. The results surface a different ranking than marketing claims would predict. ## What the 2025 report found about MangoApps Three scenario scores are most relevant for organizations evaluating frontline-accessible or communications-intensive intranet platforms. **Publishing & Communications Management — top-tier score.** This scenario evaluates content creation, editorial governance, targeted distribution, and audience segmentation. MangoApps lets communications teams segment content by role, location, shift, and department — a shift supervisor's feed looks different from an executive's, because the platform is designed to deliver relevant information, not a single undifferentiated broadcast. A built-in webpage builder lets non-technical content owners publish without filing IT tickets, which addresses one of the most consistent failure modes in intranet deployments: content that goes stale because updating it requires a support request. **Mobile & Frontline Support — top-tier score.** Frontline employees access MangoApps through the [employee app](/solutions/employee-app) on personal iOS or Android devices — no corporate email address, no VPN, no desk required. Shift schedules, HR self-service, and training courses are available in a single interface built for workers who check updates between tasks rather than from an office. CVS achieved 90% frontline adoption within the first six months of deployment; OU Health reached 87% workforce engagement within months of launching a branded MangoApps employee app. These outcomes reflect what a top-tier Mobile & Frontline Support score predicts in practice. **Community & Engagement — top-tier score.** This scenario evaluates whether a platform creates genuine cross-departmental interaction or a broadcast channel employees ignore. MangoApps' community architecture — groups, recognition feeds, and social reaction surfaces — generates participation rather than passive consumption. For organizations where visibility across distributed teams matters for retention, the engagement scenario is one of the most consequential metrics in the ClearBox framework. Two additional differentiators appear in the ClearBox review worth naming explicitly. **Integrated LMS.** MangoApps includes a full learning management system without a third-party add-on or additional license. For organizations deploying compliance training, onboarding programs, or ongoing skills development — particularly for frontline workers who can't access a standalone LMS from a desktop — native integration removes the friction that produces low training completion rates. Most platforms evaluated in ClearBox treat learning as a separate procurement decision; MangoApps treats it as a core capability. **AI search and governance.** MangoApps indexes across multiple AI engines — OpenAI, Google Gemini, Anthropic, Azure OpenAI — under a unified permissions layer. Employees see content relevant to their role, location, and language, with search results respecting the same access controls as every other content type on the platform. Platforms that add AI without addressing permissions create a parallel ungoverned information channel; role-aware AI governance prevents that problem from emerging as the platform scales. ## How MangoApps compares in the key ClearBox scenarios The table below summarizes MangoApps' performance relative to two commonly evaluated alternatives in the three scenarios where it scored highest in the 2025 report: | Scenario | MangoApps | Microsoft Viva / SharePoint | Typical standalone intranet | |---|---|---|---| | Publishing & Communications Management | Top-tier | Strong (significant IT overhead) | Moderate | | Mobile & Frontline Support | Top-tier | Limited (requires corporate email, VPN) | Limited | | Community & Engagement | Top-tier | Moderate | Moderate | | Integrated LMS | Included | Requires third-party add-on | Rarely included | | AI search and governance | Role-aware, multi-engine | Copilot (Microsoft 365 license required) | Basic keyword search | On total cost of ownership: independent analyses put first-year SharePoint intranet costs at $130,000–$426,000 for 1,000 users when customization, governance, and third-party tooling are factored in. MangoApps connects to 200+ enterprise systems — Microsoft 365, Google Workspace, HRIS platforms — as a consolidation layer rather than a point intranet solution, which changes the TCO calculation significantly. The [MangoApps Forrester Wave evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides additional analyst-sourced context on where MangoApps sits in the broader intranet landscape. On enterprise security: MangoApps supports SSO, SAML 2.0, LDAP, SOC 2 compliance, and WCAG 2.1 accessibility standards. These credentials matter in regulated industries — healthcare, banking, government — where IT and legal must sign off on any platform selection and the security posture carries as much weight as the feature set. ## Three questions worth answering before you decide The ClearBox scores are most useful when matched to the specific problems an organization is trying to solve. Three questions that clarify whether the results translate to your situation: **Does your current platform reach your full workforce?** If your organization has frontline employees — healthcare, retail, manufacturing, logistics — and the platform requires IT provisioning or a corporate email address for access, you have a structural access problem that strong desk-worker scores don't solve. The Mobile & Frontline Support scenario is the most predictive metric for organizations in this position, and the gap between top-tier and moderate scores on that dimension is the gap between reaching most of your employees and reaching a fraction of them. **Is AI adding governance or creating risk?** Platforms that add AI features without addressing permissions create an ungoverned information layer where employees can surface content outside their access level. Role-aware AI search — where results respect the same controls as the rest of the platform — is the differentiator worth testing in a pilot, not taking on faith from a product sheet. The ClearBox evaluation methodology includes AI governance as part of its scoring criteria. **What is the actual deployment cost?** A platform that appears cheaper at the per-seat level can be significantly more expensive when implementation, customization, third-party integrations, and ongoing IT overhead are included. The ClearBox deployment flexibility scores capture part of this picture; a full TCO analysis requires modeling your organization's specific integration requirements against what the platform includes out of the box. The [ClearBox 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) is available to download — it covers the same standardized scenario framework as the 2025 edition with updated platform reviews. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) provides a complementary framework for benchmarking current communications infrastructure against the practices that correlate with higher adoption rates. ## Frequently asked questions **How does MangoApps compare to SharePoint and Microsoft Viva for intranet use?** Microsoft Viva and SharePoint score well on Publishing in ClearBox evaluations but carry significant deployment overhead — independent cost models put first-year SharePoint intranet costs at $130,000–$426,000 for 1,000 users when customization and governance are included. MangoApps includes governance, an integrated LMS, and frontline mobile access without requiring a separate Microsoft 365 Copilot license for AI features. Per SWOOP Analytics, average daily SharePoint intranet usage is six minutes; MangoApps customers like CVS and OU Health report adoption rates of 90% and 87% respectively within months of deployment. **What are MangoApps' weaknesses according to ClearBox?** The ClearBox report evaluates platforms across more than a dozen scenarios and its full scoring — including categories where MangoApps does not lead — appears on page 344 of the 2025 edition. No platform tops every scenario. Organizations with highly complex SharePoint-native environments or deep Microsoft Teams dependencies should factor migration planning into their evaluation. The full report is the authoritative source, and the ClearBox methodology is transparent about how each score is derived. **How do I access the ClearBox report?** The 2025 edition referenced in this post is the report that evaluated MangoApps on the scenarios described above. The updated [ClearBox 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) is available for download on the MangoApps website and covers the same scenario framework with current platform reviews. **Why does an integrated LMS matter specifically for frontline workers?** Frontline employees rarely have access to a standalone LMS from a dedicated workstation. When learning content lives inside the daily-use tool — the same app where shift schedules and HR requests are handled — training completion rates improve because the required behavior change is minimal. For organizations with compliance training requirements or high-turnover roles where onboarding speed is critical, native LMS integration is a practical differentiator, not a marketing checkbox. The alternative — asking frontline workers to log into a separate platform for training — is one of the most reliable ways to produce low completion rates. --- # Unlocking AI’s Full Potential: The Critical Role of Data Governance and How MangoApps AI Empowers Enterprises **Author:** The MangoApps Team **Published:** 2024-11-14 **Category:** best-practices To ensure that MangoApps AI provide the insights you need, it’s crucial to adopt best practices for structuring, preparing, and managing your data. MangoApps offers the tools and guidance to centralize your content and transform it into valuable insights. # Data Governance for AI: How to Build a Knowledge Base Your AI Assistants Can Actually Use AI assistants are only as reliable as the data behind them. If your enterprise intranet holds fragmented, outdated, or poorly organized content, your AI will surface inconsistent answers — or worse, hallucinate responses that erode employee trust. This article explains the specific data governance practices that make AI assistants accurate, and how MangoApps structures governance into the platform from day one rather than treating it as an IT configuration project. **The direct answer:** Effective AI governance requires centralizing content in a single, permission-aware knowledge base, maintaining document quality and relevance, and monitoring AI performance continuously. The sections below walk through each step with concrete practices. --- ## Why Most Enterprise Intranets Fail Before AI Even Enters the Picture Before addressing AI governance specifically, it helps to understand the baseline problem. According to Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in to it, and the average employee spends just six minutes per day using intranet tools (per SWOOP Analytics). IDC research puts the cost of this fragmentation at 2.5 hours per day per employee spent searching for information that should be immediately accessible. These numbers matter for AI because a retrieval model trained on a poorly governed intranet inherits every structural flaw in that content. Conflicting document versions, duplicate policies, and undifferentiated file repositories cause AI assistants to surface contradictory answers — a failure mode that structured content taxonomies reduce significantly. MangoApps addresses this at the architecture level. Rather than requiring a months-long IT-led governance setup, the platform syncs permissions directly with your HRIS, applies SAML/OAuth authentication, and scopes AI assistants to team-specific content from the moment the system is configured. Governance is structural, not a project you schedule for later. --- ## What "Data Governance for AI" Actually Means Data governance for AI is the practice of organizing, permissioning, and maintaining the content that AI assistants retrieve when answering employee questions. It covers four areas: 1. **Content quality** — documents are accurate, current, and free of internal contradictions 2. **Content structure** — documents are formatted and tagged so retrieval models can parse them reliably 3. **Permission architecture** — employees only receive answers drawn from content they are authorized to see 4. **Ongoing maintenance** — outdated content is flagged, reviewed, and archived before it degrades AI response quality AI assistants trained on role-scoped, permission-aware content return more contextually appropriate answers than those trained on flat, undifferentiated document repositories. A frontline technician asking about a safety SOP should receive the version approved for their site and role — not a draft from a different region that happens to share a filename. --- ## Best Practice 1: Centralize Content in a Single Governed Repository Fragmented knowledge — spread across email threads, shared drives, departmental wikis, and legacy intranets — is the primary reason AI assistants underperform. When retrieval models index multiple conflicting sources, they cannot reliably determine which version of a document is authoritative. The first governance step is consolidation. Move company-wide policies, team-specific SOPs, HR documentation, and technical guides into a single [structured, accessible knowledge base](/key-features/knowledge-bases) where ownership, version history, and access permissions are explicit. Practical steps: - Assign a named content owner to every document category - Establish a review cadence (quarterly for policies, annually for reference guides) - Archive superseded versions rather than deleting them, so audit trails remain intact - Use consistent folder and tagging taxonomies so the AI can distinguish "HR — Benefits" from "HR — Compliance" without ambiguity Enterprises that consolidate knowledge into a single governed platform report measurable reductions in IT support tickets and duplicate content incidents within the first year. --- ## Best Practice 2: Structure Documents for AI Parsing AI retrieval models do not read documents the way humans do. They parse structure — headers, bullet points, labeled sections — to identify which passage answers a given query. Poorly structured documents produce inconsistent retrieval. **Document preparation guidelines:** - **Split large documents** into logically grouped smaller files. A 60-page employee handbook is harder for a retrieval model to navigate than six 10-page sections with clear titles. - **Use Markdown or plain text** formatting for consistency. Tables and bullet points parse reliably; embedded images do not — convert visual content to descriptive text. - **Write descriptive file names** that include the document type, topic, and version date (e.g., `benefits-enrollment-guide-2025-q1`). Vague names like `final_v3_REVISED` create retrieval ambiguity. - **Include FAQ-style sections** within technical documents. Questions and direct answers are the format AI assistants are optimized to retrieve and surface. - **Avoid overlapping knowledge.** Conduct regular audits to identify documents that cover the same topic with different conclusions. Consolidate them into a single authoritative source. MangoApps' [content governance engine](/key-features/content-governance-engine) automates part of this work — identifying outdated content, notifying content owners, and archiving material that has passed its review date — so governance does not depend entirely on manual discipline. --- ## Best Practice 3: Scope Permissions to Roles, Not Just Teams One of the most common governance failures is treating permissions as a binary: either an employee can see a document or they cannot. In practice, a well-governed AI knowledge base requires granular, role-aware scoping. Consider a manufacturing company with plant-floor technicians, shift supervisors, and regional HR managers. Each group needs access to different versions of safety SOPs, scheduling policies, and compliance documentation. An AI assistant that ignores these distinctions will either over-share restricted content or under-serve employees who need specific information quickly. MangoApps syncs permissions with HRIS data, meaning that when an employee's role changes, their content access — and the scope of AI responses they receive — updates automatically. This eliminates the manual permission audit that typically follows every org restructure. For organizations with [knowledge management](/solutions/knowledge-management) requirements that span both desk-based and frontline workers, role-scoped permissions also determine which AI assistants are available on which devices. --- ## Best Practice 4: Serve the 80% of Workers Who Are Deskless According to Emergence Capital, 80% of the global workforce is deskless — working in retail, manufacturing, healthcare, logistics, or field services without regular access to a desktop computer. Social Edge Consulting data shows that only 13% of employees use an intranet daily, and a significant portion of non-users are frontline workers who find existing tools inaccessible from mobile devices. Data governance for AI must account for this population. A knowledge base optimized only for desk workers — requiring VPN access, corporate email login, or desktop browsers — excludes the majority of the workforce from AI-assisted information retrieval. MangoApps AI is accessible without corporate email or VPN, supports offline content access for workers in low-connectivity environments, and delivers role-scoped AI responses through a mobile interface. This means a warehouse associate can query an SOP operations guide on a shared tablet with the same governance controls applied as a corporate employee on a managed laptop. For organizations exploring how to extend governed knowledge to frontline teams, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers adoption patterns and implementation benchmarks in detail. --- ## Best Practice 5: Write Prompts That Constrain, Not Just Direct System prompts — the instructions that define how an AI assistant behaves — are a governance mechanism, not just a UX preference. A well-written prompt constrains the assistant to a defined scope, reduces hallucination risk, and ensures responses stay within the boundaries of authorized content. **Effective prompt practices:** - **Specify the knowledge scope explicitly.** Instead of "answer employee questions," write "answer questions using only documents in the HR Benefits and HR Compliance categories." - **Define escalation behavior.** Instruct the assistant to direct employees to a named contact or ticket system when a query falls outside its knowledge scope, rather than generating a best-guess answer. - **Include tone and format instructions.** "Respond in plain language, in three sentences or fewer, and cite the document name you are drawing from" produces more auditable responses than an unconstrained prompt. - **Test prompts against adversarial inputs.** Regular prompt injection testing — submitting queries designed to extract unauthorized content or override instructions — is a security requirement, not an optional audit. --- ## Best Practice 6: Monitor Performance and Close the Feedback Loop Governance does not end at deployment. AI assistant performance degrades when the underlying knowledge base drifts — new policies are added without removing old ones, document owners change without updating metadata, or employee queries evolve in ways the original content did not anticipate. Manageable monitoring practices: - **Track query failure rates.** When an assistant responds with "I don't have information on that" or generates a low-confidence answer, log the query. These are signals that the knowledge base has a gap. - **Collect structured user feedback.** A simple thumbs-up/thumbs-down rating on each AI response, reviewed weekly, surfaces quality issues faster than periodic audits. - **Review accuracy metrics by content category.** HR policy questions may perform well while IT troubleshooting queries underperform — category-level analysis identifies where governance investment is needed. - **Set a content review trigger.** Any document that generates three or more negative feedback signals within a month should be flagged for immediate review, regardless of its scheduled audit date. MangoApps' AI Insights dashboard gives administrators visibility into employee interactions with AI assistants, enabling this feedback loop without requiring custom analytics infrastructure. --- ## What Does a Well-Governed AI Knowledge Base Actually Deliver? This is the question the best-practices framing often leaves unanswered. Here are concrete benchmarks: - Organizations that have implemented well-governed, AI-curated content delivery have achieved **90% frontline adoption within six months** — a benchmark that reflects both content quality and accessibility design. - SharePoint implementations for 1,000 users carry a first-year cost of **$130,000–$426,000**, a significant portion of which is governance configuration. Purpose-built platforms with structural governance reduce this overhead. - IDC's finding that employees lose **2.5 hours per day** to information search translates to roughly 625 hours of lost productivity per employee per year. Even a 20% reduction in search time represents measurable labor cost recovery. These outcomes depend on the governance practices described above — not on the AI model itself. The model is a retrieval and synthesis layer. The knowledge base is the foundation. --- ## Frequently Asked Questions ### How is MangoApps AI governance different from SharePoint's approach? SharePoint's governance model is primarily IT-configured and requires significant setup time — organizations typically spend weeks or months establishing permission structures, content types, and metadata schemas before AI features can be reliably deployed. MangoApps syncs governance with HRIS data at the platform level, meaning role-based permissions, team-scoped AI assistants, and content access controls are active from initial configuration rather than requiring a separate governance project. ### What content formats work best for AI knowledge bases? Plain text and Markdown-formatted documents parse most reliably. Structured formats — headers, numbered lists, labeled sections, FAQ blocks — improve retrieval accuracy. PDFs are usable but should be converted to text-searchable formats. Images, charts, and embedded tables should be accompanied by descriptive text equivalents, as AI retrieval models cannot interpret visual content directly. ### How do you handle content that becomes outdated? The most reliable approach combines automated flagging with human review. Set expiration dates on time-sensitive documents (annual policy reviews, quarterly rate sheets) and configure the platform to notify content owners when review dates approach. MangoApps' [libraries](/key-features/libraries) feature supports version control and archiving workflows that keep the active knowledge base current without permanently deleting historical versions. --- ## Getting Started: A Practical Sequence If your organization is beginning a data governance initiative for AI, this sequence reduces implementation risk: 1. **Audit existing content** — catalog what exists, identify owners, flag duplicates and conflicts 2. **Define your taxonomy** — establish the category structure (HR, IT, Operations, Compliance) before migrating content 3. **Map permissions to roles** — connect your HRIS data to content access controls before enabling AI assistants 4. **Migrate and structure content** — reformat documents to AI-parseable standards during migration, not after 5. **Configure and test AI assistants** — start with a single high-value use case (e.g., benefits questions) before expanding scope 6. **Establish monitoring cadence** — set weekly feedback reviews and quarterly content audits before launch, not as a post-launch addition For organizations evaluating how MangoApps compares to other intranet and employee experience platforms, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent analysis across the major vendors in this category. --- # Thriving Workplaces With Advanced Moderation Tools **Author:** MangoApps **Published:** 2024-10-01 **Category:** company-culture As the digital workplace evolves, fostering a positive and inclusive culture is more important than ever. With the shift to remote and hybrid work, employees... As the digital workplace evolves, fostering a positive and inclusive culture is more important than ever. With the shift to remote and hybrid work, employees increasingly rely on digital platforms to interact, making it essential to maintain respectful and productive conversations that support workplace morale and collaboration. While open communication is a key driver of employee engagement, ensuring its quality doesn't have to be overwhelming. With AI-powered moderation tools, organizations protect employee morale by automatically blocking harmful content and toxic behavior before it reaches your workplace. AI-powered moderation automatically keeps communication channels free of negative content. It frees up HR and internal comms teams to focus on more strategic initiatives—all while ensuring a safe, respectful workplace. Only 22% of company intranets deliver personalized content to employees, meaning most digital workplaces expose all employees to the same unfiltered content stream—making targeted moderation and relevance controls a meaningful differentiator (per Akumina / State of the Digital Workplace & Modern Intranet 2024 research). ## Efficiently Managing Internal Communications Digital workplaces thrive on open communication, and while this fosters collaboration and innovation, it also requires careful management to ensure that content aligns with company values. As businesses grow and employees post comments, share updates, and participate in discussions, internal communications teams may face challenges overseeing the increased volume of user-generated content (UGC). However, with the right employee engagement software in place, managing this influx becomes far less staggering. Instead of manually monitoring every interaction, AI-driven interventions can quickly spot inappropriate behavior and policy violations, helping teams manage content efficiently. By reducing the need for constant manual oversight, content moderation becomes easier and more streamlined for busy internal communication teams. For a broader look at where internal communications is heading, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the key shifts shaping how teams manage digital channels. Toxic or unmoderated digital environments disproportionately harm frontline and remote workers who lack in-person channels to escalate concerns, making AI moderation especially critical for distributed workforces (per Unily / Simpplr product and case study pages covering remote employee engagement). Per Emergence Capital, 80% of the global workforce is deskless—meaning the majority of employees depend entirely on digital channels, with no fallback to in-person escalation when those channels become hostile. ## Benefits Beyond Moderation: Enhancing Engagement and Trust Creating a safe and inclusive environment is essential for fostering employee enthusiasm and productivity. AI-enabled moderation ensures that employees can engage confidently, knowing that harmful interactions are swiftly detected and addressed. With a proactive approach in place, employees can feel safe when sharing ideas and collaborating in public forums. In addition to filtering harmful content, moderation insights and analytics can help identify repeat offenders, allowing you to address toxic behavior patterns early. Not only does this prevent issues from escalating, but it also reinforces the company's commitment to a healthy, supportive workplace culture. When employees know they are protected, they're more likely to contribute, collaborate, and stay motivated, driving higher employee engagement and overall productivity. One organization reported a 30-point increase in engagement score attributed to AI-powered social reporting and moderation insights—not just content publishing. Moderation is not only a compliance tool—it is a direct driver of employee engagement strategies. Competitors like Simpplr and Unily frame safe environments as a direct cause of measurable engagement lifts: when employees feel safe, they post more, collaborate more, and stay longer. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) explores how organizations are connecting digital safety to measurable engagement outcomes. ## Sentiment Analytics and Crisis Communications Platforms that combine AI moderation with real-time sentiment insight allow communications teams to respond quickly during crises or serious incidents—a capability cited as distinct from basic content filtering (per Unily / British Airways case study). MangoApps' moderation insights go beyond flagging individual posts: they surface sentiment trends across teams and time periods, giving HR and communications leaders early warning when organizational events—such as layoffs, policy changes, or leadership transitions—are generating negative sentiment spikes. This positions moderation analytics as a crisis communications tool, not just a content filter. Teams can monitor whether a company-wide announcement is landing well or generating anxiety, and respond with targeted messaging before frustration escalates into disengagement or attrition. ## MangoApps' Advanced Content Moderation Tools for the Workplace MangoApps' AI-Powered Moderation solution is designed to support organizations in maintaining a positive digital workplace. These features help ensure that all internal communications are aligned with company standards, fostering a thriving environment for all employees. See how this approach has worked in practice in the [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study. 1. **Combining AI with Human Vigilance**: MangoApps uses a combination of AI-driven moderation and human oversight to ensure no harmful content is overlooked. This dual approach allows for comprehensive monitoring of communications, flagging potential issues early before they escalate. 2. **Insights for Management and HR**: MangoApps' tools don't just block harmful content; they provide valuable insights into recurring issues and problematic behavior. This data can empower HR and management teams to address patterns of concern early, implementing interventions that foster a healthier workplace culture. Plus, these insights allow you to directly see how organizational events or changes—such as layoffs or policy shifts—impact employee interactions, helping teams respond proactively. 3. **Maintaining Alignment with Company Values**: MangoApps' moderation tools work in the background to ensure all communications reflect your organization's standards. By filtering out inappropriate content, our platform helps create a respectful and professional space for collaboration. 4. **Encouraging Safe Employee Interaction**: By creating a safeguarded environment, employees are more inclined to share ideas and engage in productive discussions. Moderation tools help prevent harmful content from being posted or circulated, reducing the risk of negative experiences. 5. **No-Code Configuration for HR and Comms Teams**: MangoApps' moderation settings are designed so that HR or internal communications admins can configure and manage moderation policies independently, without requiring IT involvement. This means moderation rules can be updated quickly as company culture evolves or new issues emerge—without opening a ticket. MangoApps has been recognized for this approach to employee communications: see the [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) and [MangoApps Wins Gold in Reworked's 2026 IMPACT Awards for Excellence](/articles/mangoapps-gold-reworked-2026-impact-awards) for third-party validation. ## Customization and Scalability of Moderation Tools Regardless of the size of your organization, MangoApps' content moderation tools offer flexible options to fit your unique needs. Whether you're moderating a small team or a large enterprise, MangoApps' tools scale effortlessly, allowing employees to focus on what matters most: promoting a positive employee experience and maintaining alignment with company values. A 91% usage rate was achieved after rolling out a moderated, mobile-first intranet platform across a 40,000-employee workforce within 8 weeks—demonstrating that well-configured moderation supports adoption rather than hindering it. You can easily customize moderation settings—whether it's moderating all content, focusing on specific keywords, or tailoring settings for different teams. The ability to designate Moderation Admins or empower Team Admins ensures moderation efforts scale with your organization, providing consistent oversight while maintaining integrity. With options to exclude certain users or teams from moderation, you can keep your efforts targeted and relevant to your specific needs. Organizations in regulated industries such as [healthcare](/industries/healthcare) and [financial services](/industries/financial) can apply stricter moderation tiers to sensitive channels while keeping general collaboration spaces more open. ## Best Practices for Implementing Moderation Tools To maximize the effectiveness of advanced moderation tools for the workplace, companies should consider implementing several best practices: 1. **Leverage AI Moderation Tools:** MangoApps' AI-powered moderation tools handle the heavy lifting, automatically detecting negative emotions, harassment, and discrimination. All you need to do is configure the types of behaviors you want the AI to monitor. While the AI works to prevent harmful interactions, employees can still manually flag any content that requires additional attention, fostering a shared responsibility for maintaining a positive and respectful workplace. 2. **Continuously Update Moderation Rules**: As company culture evolves, so should your moderation settings. Regularly review and adjust the moderation rules to ensure they align with current standards and address emerging issues effectively. 3. **Study Analytics for Continuous Improvement**: MangoApps' comprehensive insights dashboard allows companies to track moderation trends, identify recurring issues, and adjust their strategies accordingly. Using this data, HR and management teams can proactively address problematic behaviors and fine-tune moderation settings for ongoing effectiveness. 4. **Set Clear Guidelines**: Establish clear, company-wide communication standards that define acceptable behavior and the types of content that will be moderated. This helps set expectations and reduces ambiguity. ## Build Your Ideal Digital Workplace with Content Moderation Tools Advanced content moderation tools like those in MangoApps are essential for organizations aiming to create a thriving workplace. By maintaining a safe and inclusive environment, businesses can boost employee enthusiasm, collaboration, and overall productivity. It's about more than just filtering content—it's about reinforcing a culture that supports everyone's best work. Here is what organizations should take away before making a decision: - **Moderation drives engagement, not just compliance.** When employees feel safe, they participate more, share more, and stay longer. A 30-point engagement score increase has been linked directly to AI-powered moderation and social reporting—not content publishing alone. - **Sentiment analytics extend moderation into crisis response.** Real-time sentiment insight lets communications teams detect and address negative sentiment spikes before they become retention or reputation problems (per Unily / British Airways case study). - **No-code configuration matters for speed.** HR and comms teams that can self-manage moderation rules respond faster to emerging issues than teams dependent on IT queues. - **Scale and personalization are table stakes.** With only 22% of intranets delivering personalized content (per Akumina / State of the Digital Workplace & Modern Intranet 2024 research), organizations that add targeted moderation and relevance controls are ahead of the majority of their peers. - **Implementation is faster than most teams expect.** A 40,000-employee deployment achieved 91% platform usage within 8 weeks of rollout. To learn more about advanced content moderation tools for your digital workplace and how MangoApps fits your organization's size, industry, and compliance requirements, schedule a demo with us. ## How Does Content Moderation Connect to Broader Employee Engagement Strategy? Content moderation is one component of a larger employee engagement strategy. Safe digital environments lower the barrier to participation, but engagement also depends on how well communications are personalized, how accessible the platform is for frontline workers, and whether employees have channels to give feedback. Per IDC, employees spend 2.5 hours per day searching for information—a problem that moderation alone does not solve, but that a well-structured, moderated intranet can significantly reduce. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading organizations are combining moderation, personalization, and mobile access into a unified employee experience. ## What Should Organizations Consider When Evaluating Moderation Tools? When evaluating employee engagement software with moderation capabilities, organizations should ask: Can HR or communications admins configure rules without IT? Does the platform surface sentiment trends, or only flag individual posts? How does moderation scale across different teams, geographies, or compliance requirements? Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in—often because the environment feels irrelevant or unwelcoming. Moderation quality is a meaningful factor in whether employees return to a platform daily. Per SWOOP Analytics, the average employee spends only six minutes per day using intranet tools, and per Social Edge Consulting, only 13% use an intranet daily—underscoring that platforms must earn engagement, not assume it. For context on how MangoApps has been independently evaluated, see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms). ## How Does Moderation Work for Frontline and Distributed Teams? Frontline workers—who represent 80% of the global workforce per Emergence Capital—are disproportionately affected by unmoderated digital environments because they have no in-person fallback when digital channels become hostile. For industries like [ambulatory care](/industries/ambulatory-care) or [grocery retail](/industries/grocery), where frontline workers are the majority of the workforce, moderation tools must work on mobile, require no training to use, and operate in the background without adding friction to daily tasks. MangoApps' [employee communications solutions](/solutions/employee-communications) are designed with this population in mind, ensuring that moderation protects rather than burdens the employees who need it most. --- # Transforming Enterprise Search with a Company Knowledge Assistant **Author:** The MangoApps Team **Published:** 2024-10-01 **Category:** best-practices The Company Knowledge Assistant is an application of a generative AI Assistant to change how employees search for information. Employees can ask questions in natural language and get immediate answers relevant to their role, location, and needs. # Transforming Enterprise Search with a Company Knowledge Assistant Per IDC, employees lose an average of 2.5 hours each day searching for information across disconnected systems. That figure is cited constantly as a productivity problem. It is actually a governance problem in disguise: the information exists. The question is whether it reaches the right person, in the right context, without exposing what shouldn't be exposed to everyone who asks. Most organizations approaching AI knowledge tools are asking the wrong question. They ask "how fast can this answer questions?" rather than "how does it know what each employee is authorized to see?" Speed is a solved problem. Governance is what separates AI knowledge deployments that scale from deployments that stall at the pilot. Per SWOOP Analytics, the average employee spends six minutes per day using intranet tools — not because they're indifferent to company knowledge, but because the systems serving it have historically been slow, stale, and inaccessible. Per Emergence Capital, 80% of the global workforce is deskless and will never sit at a corporate workstation to access a knowledge base designed around one. An AI knowledge assistant addresses each of those failures. But without a governance layer, it introduces a new category of risk that most vendors don't lead with. ## The fragmentation problem AI knowledge assistants are built to solve Per Social Edge Consulting, 91% of organizations operate an intranet. Nearly a third of employees never log in — and most of the remainder log in only because a specific document isn't findable anywhere faster. The moment that document surfaces in a colleague's Slack message or a Google search, the intranet empties. This is the information retrieval paradox: organizations invest in knowledge infrastructure, and workers systematically route around it. The routing has a cost. A worker who can't find a safety procedure improvises. A new hire who can't locate the expense policy emails HR. A project lead who can't surface last quarter's process documentation starts over from scratch. These aren't dramatic failures — they're the low-level friction that accumulates across every shift, every department, every day. An AI knowledge assistant built on a [knowledge management](/solutions/knowledge-management) foundation changes the retrieval model from "here is a list of documents matching your search term" to "here is the answer to your question, drawn from sources you're authorized to see." The shift from links to answers removes friction at the point of need — which is the only place friction removal actually changes behavior. ## Why governance is the enterprise objection most AI tools don't answer Five of the largest AI knowledge assistant vendors now lead their positioning with security architecture. The objection they're responding to is the one enterprise IT and legal teams raise before any deployment proceeds: in an organization with tiered access — HR documentation, legal agreements, compensation data, pre-release product plans — what prevents an employee from asking a question and receiving a synthesized response drawn from a document they were never authorized to read? The answer requires role-based access controls enforced at the retrieval layer, not just the storage layer. A knowledge assistant that honors read-permissions on individual files but synthesizes content from them without those constraints isn't secure — it's a permission bypass with a friendly interface. The governance architecture must determine not just what documents an employee can open, but what content can be included in any AI-generated response they receive. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) evaluated this capability across major platforms. Platforms that enforce permissions at the retrieval layer produce answers reflecting what each user is authorized to know. Platforms that don't create audit exposure the moment a response is generated — regardless of whether the employee intended to access restricted information. This is the reason enterprise deployments stall after pilots. Governance is not a feature to add later. Organizations that build it in at the architecture layer — role-based retrieval, audit trails on AI-generated responses, permission inheritance from source documents — move from pilot to production. Organizations that treat it as a configuration option discover it at the worst possible time. ## What effective deployment actually requires Moving from traditional enterprise search to an AI knowledge assistant involves three changes, each building on the one before. **Conversational retrieval over keyword matching.** Traditional search returns documents containing a search term. A knowledge assistant interprets the intent behind the question and returns a synthesized answer drawn from the right sources. A warehouse worker asking "what do I do if the emergency lockout procedure wasn't followed on the previous shift?" receives a direct response from the relevant safety documentation — not a list of PDFs with matching keywords. **Living knowledge over indexed snapshots.** A knowledge assistant's value degrades the moment its underlying knowledge base goes stale. Sustained adoption depends on knowledge bases connected to active repositories — wikis, document libraries, newsfeed updates, and integrated platforms like SharePoint and Google Workspace — rather than indexed snapshots taken at deployment. When a procedure changes, the assistant reflects the change without requiring a content owner to manually update a separate system. The prior version is superseded, not just outdated. **Enterprise-wide access over departmental silos.** The full value materializes when the assistant crosses departmental boundaries. A legal team member asking about procurement sign-off requirements and a procurement team member asking about legal review timelines should receive equally accurate, equally current answers. That requires connected knowledge, consistent permissions architecture, and a retrieval model that doesn't privilege the departments that happened to build the most organized folder structures. ## The deployment speed comparison SharePoint-based knowledge architectures typically require IT-led customization cycles of three to six months before employees see a materially improved information experience. An AI-native knowledge assistant deployed on an existing connected intranet can reach production in days because it retrieves from existing repositories rather than requiring those repositories to be restructured first. This distinction matters most to organizations with a defined near-term requirement: a compliance deadline, a significant onboarding cohort, a product launch. An organization onboarding 200 new specialists in Q3 cannot wait for a six-month restructure. It needs a knowledge assistant that works on the knowledge base that currently exists, with the access controls that currently govern it. The update cycle also changes fundamentally. When a policy changes in a traditional intranet model, a content owner updates a page and hopes employees encounter the new version rather than a cached or printed copy of the old one. A knowledge assistant connected to a governed, active document library surfaces the current version automatically — and can flag when source documents have conflicting versions that require resolution before the answer can be trusted. ## The frontline access gap that defeats knowledge investments Per Social Edge Consulting, only 13% of employees use an intranet daily. The other 87% are not uniformly disengaged — a significant portion are frontline workers without corporate email addresses, desktop access, or the ability to navigate a VPN login from a warehouse floor, hospital unit, or retail location. A knowledge assistant that requires a corporate credential, a specific device, or a VPN connection doesn't close the information gap for this population. It deepens it. Frontline employees who cannot access safety procedures, compliance documentation, or shift-specific process updates from a personal mobile device are operating from the same fragmented informal network they were using before the AI investment. The knowledge infrastructure improved for the 20% of workers with corporate laptops and produced nothing measurable for everyone else. The [American College of Radiology case study](/resources/case-study-american-college-radiology) documents what happened when a distributed professional workforce received a knowledge platform built for how their employees actually access information, not how the IT team assumed they did. Adoption and response-time outcomes shifted within the first quarter of deployment. The lesson generalizes: access architecture matters as much as search quality. ## What enterprise buyers should validate before committing Organizations evaluating AI knowledge tools consistently raise the same follow-up questions after a demonstration. Each has a specific answer that distinguishes platforms built for enterprise deployment from platforms built for demos. **How long does deployment take?** For AI-native platforms connected to existing repositories: days to a few weeks for the core knowledge base, with incremental expansion as additional sources are connected. For deployments requiring a SharePoint taxonomy restructure as a prerequisite: three to six months. The question to ask vendors is whether their platform ingests existing knowledge structure or requires a new one to be built first. **What does ROI look like at scale?** IDC's 2.5 hours/day figure is the input. Organizations that eliminate the highest-friction information retrieval use cases first — safety procedures, expense policies, onboarding documentation — typically see measurable time recovery within 60 days. The recovery scales as more repositories are connected and more employee populations gain access. **How is sensitive data handled end-to-end?** The three capabilities to validate are: role-based access controls at the retrieval layer (not just storage), audit trails on every AI-generated response (who asked, what was returned, which source documents informed it), and permission inheritance so that source-document access controls automatically propagate to the AI layer without manual reconfiguration. **What happens when the AI generates an incorrect answer?** Governance-grade platforms surface the source document for every AI-generated response so employees can verify the answer directly. Confidence levels are surfaced when underlying documentation is ambiguous or when source documents conflict. An assistant that delivers confident wrong answers without a verification path isn't a knowledge tool — it's a liability that erodes trust faster than the traditional search it replaced. ## The governance argument is the AI argument The standard pitch for AI knowledge assistants focuses on speed: faster answers, less time wasted on search, fewer interruptions to supervisors. That pitch is accurate. It is not sufficient. Speed without governance generates confident wrong answers, creates permission bypass exposure, and produces the kind of audit liability that causes legal and IT teams to shut down deployments before they ever reach the employees who needed them. The organizations building durable AI knowledge infrastructure treat the governance layer as the product — role-based retrieval, audit trails, permission-aware synthesis, and living knowledge bases connected to active repositories are what make the system trustworthy at scale, not just fast in a demo. [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) identifies the organizational capability that most reliably predicts sustained engagement: whether employees receive the information they need, when they need it, without having to escalate to a supervisor. That capability is infrastructure. The AI knowledge assistant is its current best expression — when governance is part of the architecture from the start, not added after the first audit finding. --- # Empowering Workforces With MangoApps AI Experts **Author:** MangoApps **Published:** 2024-09-05 **Category:** ai-agents MangoApps AI Experts, powered by MangoApps AI Studio, redefine the integration of generative AI (GenAI) within the digital workplace, emphasizing the ef... # Empowering Workforces With MangoApps AI Experts Per IDC, the average employee spends 2.5 hours per day searching for information they need to do their jobs. That is not a behavior problem. It is an infrastructure problem — and for organizations with a significant frontline workforce, the benchmark understates the actual cost, because it describes employees who have full system access. Approximately 80% of the global workforce is deskless, per Emergence Capital, and the platforms most organizations call their AI or knowledge management system were built for employees with corporate email addresses and company-issued laptops. They were not built for the warehouse floor, the hospital unit, or the field vehicle. MangoApps AI Experts close that gap structurally. Built on AI Studio, they give every employee — desk-based or deskless — a single, governed AI layer for finding information, completing tasks, and following standard operating procedures without switching between disconnected tools. This article explains how the system works, what governance and compliance controls are built in, how frontline workers access it without a corporate credential, and what the business case looks like for organizations that have moved from fragmented point solutions to a unified AI infrastructure. ## Why fragmented AI tools cost more than they appear The per-seat subscription model makes individual tools easy to justify line by line and difficult to evaluate in aggregate. Six applications at $10–15 per seat per month, multiplied across headcount, produces a monthly AI spend that frequently exceeds what a unified platform would cost — before accounting for the productivity cost of context switching between them. Fragmentation has a measurable operational cost. Per Social Edge Consulting, 91% of organizations operate an intranet, but only 13% of employees use one daily, and nearly a third never log in at all. Per SWOOP Analytics, the average daily time an employee spends using intranet tools is six minutes. These numbers describe employees who have full access to those systems. For the 80% of the global workforce that is deskless, the access problem is structural, not behavioral — the tools were not designed for them, and no adoption initiative changes that. The consequence is predictable: employees who cannot find what they need improvise, ask managers, or proceed without the information. All three outcomes are slower, more error-prone, and harder to audit than a functioning AI layer would be. At scale, that drag is calculable. The question for any organization evaluating AI investment is whether the platform they are considering closes the access gap for the entire workforce or only for the 20% who already had full access. ## How AI Experts work: RAG on your organization's data AI Experts are configurable AI assistants trained on your organization's private content using Retrieval Augmented Generation (RAG). Each Expert pulls answers exclusively from approved internal knowledge sources — HR policies, SOPs, training materials, compliance documents — rather than generating generic responses from a public model. The distinction matters practically. An employee asking about the correct procedure for handling a specific equipment malfunction needs your SOP for that scenario, not a generalized explanation of what equipment malfunction procedures typically look like. RAG-based retrieval means the answer is drawn from the document your operations team wrote and approved. The source is your organization's content, governed by your organization's policies. AI Studio, the underlying configuration layer, connects to third-party large language models via API consumption-based pricing. This makes advanced AI accessible as a shared organizational resource rather than a per-seat line item, and it means organizations choose which model powers each Expert. As the LLM market evolves, organizations can swap models without rebuilding knowledge architecture or retraining employees. Configuration requires no IT development cycles. Business owners build and update Experts directly in a no-code environment. The HR team can create a new benefits Expert, update a policy guide, or retire an outdated onboarding document without submitting a development request. Deployment timelines that traditionally take months compress to days. ## Frontline access without email or a desk The platforms most organizations deploy for knowledge access — SharePoint, legacy intranets, enterprise wikis — require a corporate email address, a VPN, or both. Frontline workers in distribution, healthcare, retail, and field operations typically have neither. The result is a knowledge infrastructure that effectively covers 20% of the workforce and leaves the remaining 80% to depend on whatever their supervisor happens to know at the moment they need to know it. AI Experts run on the [employee app](/solutions/employee-app) on any mobile device, without a corporate credential. A retail associate asking about a return policy, a warehouse worker checking a safety protocol, or a field technician looking up equipment specifications gets the same governed, organization-specific answer as a corporate knowledge worker — from the same application, on a device they already carry. Platforms built for frontline-first deployment consistently report adoption rates of 90% within the first six months of launch. That benchmark reflects how access architecture drives adoption: when the barrier is removed, usage follows without a change-management program. The six-minute daily average from traditional intranet tools is an access problem. When employees can reach the platform from the device they carry, without credentials they do not have, the engagement metric changes accordingly. ## Governance that makes AI safe to deploy at scale Deploying AI across an enterprise creates a content operations challenge that most organizations underestimate until they are mid-deployment: the AI is only as accurate as the knowledge sources it retrieves from. Stale content produces stale answers. Unauthorized content produces unauthorized answers. Role-based access and data sovereignty are baseline requirements — but the governance question that determines whether AI deployment stays accurate over time is content ownership: who can publish, update, or retire the knowledge sources AI Experts draw from. MangoApps addresses this through its [content governance engine](/key-features/content-governance-engine), which controls which content is eligible to train each Expert, who can modify those sources, and when content expires or requires review. A compliance or safety update reaches frontline employees through the same application they use for everything else, reflecting the current approved version. Content governance means the AI answers what the organization has authorized it to answer — not what was true six months ago. The full governance layer covers role-based access controls that assign AI capabilities by job function, PII detection that automatically flags personally identifiable information in AI interactions before issues escalate into compliance incidents, audit trails that log AI interactions for regulated-industry review, and data sovereignty controls that ensure corporate content never trains public LLMs and is never stored outside the organization's environment. For organizations in healthcare, financial services, or government, these are not differentiating features — they are preconditions for deployment. ## The productivity and business case The calculation starts with the IDC benchmark: 2.5 hours per employee per day lost to information search. Across a 500-person frontline workforce at an average hourly cost of $20, that is $50,000 in daily productivity loss from information retrieval alone — before accounting for manager time spent answering questions that a functioning AI layer would resolve directly. Organizations deploying AI-assisted, mobile-accessible knowledge tools have reported onboarding speed improvements of 50% for new hires. At scale — tens of thousands of employees distributed across facilities and geographies — the cumulative impact on support ticket volume, onboarding throughput, and turnover among newly reached frontline employees compounds into the class of outcomes that enterprise buyers measure in tens of millions of dollars in annual cost avoidance. The [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) documents how persistent exclusion from organizational information systems is a reliable early indicator of disengagement — and disengagement's cost extends well beyond productivity into turnover, quality errors, and the coordination overhead that accumulates when managers become the information layer because the platform cannot reach their teams. Closing the access gap is the structural intervention. The engagement and retention outcomes follow from that, not from the culture program built on top of a broken infrastructure. ## AI Experts vs. traditional knowledge bases The core difference between AI Experts and a traditional [knowledge base](/key-features/knowledge-bases) is the interaction model. A knowledge base is a search interface: the employee navigates to a system, constructs a keyword query, filters results, opens a document, and reads until they locate the specific answer. An AI Expert is a conversation interface: the employee asks a question and receives the answer, drawn from the same document, without navigating to or reading the document. For a desk-based knowledge worker with uninterrupted time, the knowledge base workflow is manageable. For a frontline worker with thirty seconds and a task in progress, it is not. The interaction model that works for 20% of the workforce does not work for the 80% the platform was not designed to serve. The content freshness dynamic matters equally. A knowledge base stores the last published version of every document. An AI Expert retrieves from the current approved version, with content governance determining when that version changes and who authorizes the change. The answer an employee receives reflects today's policy, not the version that was indexed before the last compliance update. Traditional knowledge bases also require employees to know what to search for — to translate "what I want to know" into the keyword that surfaces the relevant document. AI Experts accept the question in natural language and return the answer directly. The translation burden disappears, and so does the gap between having information in a document library and having employees actually access it. For organizations evaluating this transition, the [IDC MarketScape 2024 vendor assessment](/resources/idc-marketscape-2024) provides independent context for how AI-integrated workspace platforms are evaluated against enterprise requirements — including the frontline accessibility criteria that most enterprise AI evaluations still treat as secondary to desk-worker use cases. --- # Practical Generative AI Use Cases in the Workplace **Author:** MangoApps **Published:** 2024-09-05 **Category:** enterprise-ai Even if a business is aligned on the reasons for needing AI and has a clear idea of how they will deploy it, it’s not always clear what they should deploy it... Even if a business is aligned on the reasons for needing AI and has a clear idea of how they will deploy it, it's not always clear what they should deploy it to do. With all of the hype that surrounds AI, it's important to pinpoint practical use cases for GenAI, to ensure the business can see value quickly without too much complexity. These should not only deliver immediate benefits but also be simple to implement without significant technical effort or extended timelines. # Demystifying the Hype of GenAI: Practicality > Complexity Choosing to focus on practical use cases over complex ones is a strategic move towards building a solid foundation for embedding GenAI as a regular function of employees' work. This approach demystifies AI integration, making GenAI's transformative potential both accessible and actionable across all levels of the organization. Starting with manageable applications is key to achieving broad adoption and driving real value. We have pinpointed a handful of universally applicable use cases for any business in any industry. These range from conversational enterprise search to AI-powered content creation and knowledge management. They are designed to boost operational efficiency and enhance employee satisfaction. Importantly, they achieve this without the need for heavy investment or navigating undue complexity. To anchor the business case: employees spend an average of 2.5 hours per day searching for information, per IDC. Meanwhile, per Social Edge Consulting, only 13% of employees use an intranet daily, and nearly a third never log in at all — meaning the information infrastructure most organizations rely on is already failing before AI enters the picture. The use cases below are designed to close that gap. ## AI-Powered Employee Self-Service Experts Transforming internal HR and IT services, these experts handle inquiries and tasks with ease, from policy questions to technical support, offering instant resolutions in natural language. They address a real fragmentation problem: employees navigate 6–8 disconnected tools daily, creating the friction that GenAI self-service is designed to eliminate (MangoApps product page — challenge framing). AI-powered onboarding automation can reduce new-hire ramp time by up to 50%, a concrete outcome that justifies GenAI investment to HR buyers (Beekeeper product page — onboarding speed claim). For organizations exploring how AI fits into a broader [modern HCM](/solutions/modern-hcm) strategy, self-service experts are typically the fastest path to measurable ROI — reducing ticket volume, cutting response times, and freeing HR staff for higher-value work. **Implementation note:** Start by identifying the top 20 questions your HR and IT help desks receive each month. These become the initial training corpus for your AI expert. Most organizations can stand up a functional self-service expert within four to six weeks using this scoped approach. ## Conversational Enterprise Search Streamlining access to information through natural language processing allows employees to find data as if they're having a conversation, making search intuitive and efficient. AI-driven semantic search goes beyond simple keyword matching, understanding the intent behind queries to deliver precise results — even when exact terms are elusive. Critically, semantic AI search must respect existing permissions and return role-aware results, not just keyword matches — a governance requirement that is a deployment prerequisite for IT and security teams (Akumina product page — semantic search governance). Without permission-aware search, organizations risk surfacing confidential documents to unauthorized users, which is why governed AI deployment is a non-negotiable design requirement, not an afterthought. Per SWOOP Analytics, employees spend an average of just six minutes per day using intranet tools — a signal that current search experiences are not meeting user needs. Conversational search, embedded directly in the [employee app](/solutions/employee-app) employees already use, removes the friction that keeps workers from finding what they need. For a detailed look at how intranet platforms are being evaluated on this capability, see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms). **Implementation note:** Pilot conversational search against a single, well-maintained content repository (e.g., your HR policy library or IT knowledge base) before expanding scope. This limits governance risk and produces a clean success metric — search deflection rate — within the first 30 days. ## AI-Enhanced Knowledge Harvesting Capturing and leveraging organizational knowledge is one of the most high-value applications of knowledge management tools powered by AI. Scattered documents are transformed into a cohesive knowledge base, preventing knowledge loss and making institutional expertise discoverable for others. By synthesizing data into organized knowledge artifacts, AI assists in unearthing valuable insights, thereby enhancing the collective intelligence of the organization. Effective knowledge and knowledge management at the enterprise level requires more than a document repository — it requires AI that can surface the right artifact to the right person at the right moment. This is where tools for knowledge management that integrate with existing SOP operations workflows deliver compounding value: every time an employee resolves a question, the system learns and improves future retrieval. For organizations building or rebuilding their knowledge management strategy, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an independent benchmark of how platforms compare on knowledge harvesting and AI-assisted discovery. **Implementation note:** Identify three to five subject-matter experts in each department and use AI to interview and document their tacit knowledge before it walks out the door. This "knowledge harvesting sprint" typically takes two weeks per department and produces immediately usable knowledge artifacts. ## Personalized Employee Experiences AI tailors the workplace experience to individual needs, learning from interactions to offer contextually relevant information and support, thereby elevating job satisfaction and productivity. This adaptability ensures employees receive the information and assistance that is not only timely but also aligned with their location, background, specific roles, and historical interactions. This is especially important for the 80% of the global workforce that is deskless, per Emergence Capital. Frontline workers — in retail, manufacturing, healthcare, and logistics — rarely sit at a desk, rarely have a corporate email address, and are disproportionately underserved by traditional employee experience platform deployments. Personalized AI that delivers role-specific, location-aware content via mobile closes this gap. Per Social Edge Consulting, 91% of organizations operate an intranet, yet most of those intranets were built for desk-based workers. Extending personalized AI to frontline employees is not a nice-to-have — it is a prerequisite for equitable access to organizational knowledge. For organizations managing distributed or frontline workforces, [workforce management](/solutions/workforce-management) capabilities that integrate with personalized AI layers produce the most consistent employee experience outcomes. **Implementation note:** Segment your employee population by role and location before configuring personalization rules. Frontline workers and desk-based workers have fundamentally different information needs; a single configuration will underserve both groups. ## Content Creation and Curation AI accelerates and refines the content creation process, ensuring outputs are relevant and engaging, while also assisting in curating content that resonates with target audiences. By training on company data, AI assistants produce content that accurately reflects the organization's voice and audience needs, streamlining the content development lifecycle. Enterprise AI assistants should support multiple LLM engines — including OpenAI, Google Gemini, Anthropic, and Azure OpenAI — so organizations avoid vendor lock-in as the model landscape evolves (MangoApps integrations product page — AI engine flexibility). This architectural flexibility matters for content creation specifically because different models have different strengths; the best content output often comes from routing tasks to the most appropriate engine rather than committing to a single provider. For communicators building an AI-assisted content strategy, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) provides a practical framework for integrating AI into editorial workflows without sacrificing brand voice or compliance requirements. **Implementation note:** Begin with templated content types — policy summaries, event announcements, onboarding guides — where the structure is known and the AI's job is to populate and refine, not invent. This produces consistent quality and builds internal confidence in AI-generated content before moving to more open-ended creation tasks. ## Harnessing GenAI for Simplicity and Practicality These use cases underscore GenAI's potential to simplify complex processes and make significant productivity and efficiency gains within the digital workplace. By focusing on these accessible applications, businesses can start to leverage the power of GenAI, bringing its transformative benefits to every employee. The ROI is quantifiable. Organizations that have deployed AI-native employee experience platforms at scale have reported $20M in cost avoidance and 90% frontline adoption within the first six months — outcomes that move GenAI from a technology experiment to a line-item business case. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) documents how leading organizations are structuring these deployments and measuring their returns. ## A Practical Solution In a following article, we introduce **MangoApps AI Experts**, the only practical solution meticulously crafted to address the challenges of deploying GenAI in the enterprise digital workplace. Purpose-built to not only navigate but conquer the complexities of deploying GenAI in the enterprise, MangoApps AI Experts are engineered to support the practical use cases we've detailed and much more. **Read more about using MangoApps AI Studio to customize your own AI Experts now.** ## How Do We Measure Success for GenAI Deployments? The most reliable early indicators are operational metrics that already exist in your environment: help desk ticket volume (should decline as self-service adoption rises), average time-to-answer for employee queries, search session length (shorter is better when intent is met), and content publication cycle time. For knowledge management specifically, track the ratio of questions answered by AI versus escalated to a human — this ratio should improve month over month as the knowledge base matures. Tie these metrics to a baseline captured before deployment so you have a clean before/after comparison to present to budget holders. ## What Is a Realistic Implementation Timeline? For the use cases described above, a phased approach works best. Weeks one through four: scope and configure a single AI expert or conversational search pilot against one content domain. Weeks five through eight: measure deflection rates, gather employee feedback, and refine. Weeks nine through sixteen: expand to additional content domains or a second use case. Most organizations reach meaningful adoption — defined as the majority of targeted employees using the AI tool at least weekly — within three to four months of a scoped pilot. Full enterprise rollout, including frontline workers and multi-language support, typically follows in the six-to-twelve-month window. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) includes deployment timelines from organizations that have completed this journey. ## What Skills and Governance Does Our Team Need? GenAI deployment does not require a data science team, but it does require clear ownership. Assign a content governance lead responsible for the quality and currency of the knowledge base that feeds your AI. Assign an IT lead responsible for permission configuration and LLM engine selection. Assign an HR or communications lead responsible for employee communication and change management. On the governance side, establish a content review cadence — quarterly at minimum — to retire outdated documents that could produce incorrect AI responses. Permission-aware search configuration should be validated before go-live, not after, to ensure role-scoped results are enforced from day one. For organizations in regulated industries, the [employee data](/solutions/employee-data) governance framework should be reviewed alongside AI deployment plans to ensure compliance requirements are met end to end. --- # Overcoming Enterprise-Wide AI Deployment Challenges **Author:** MangoApps **Published:** 2024-09-05 **Category:** enterprise-ai The integration of generative AI (GenAI) across an enterprise heralds a transformative potential for the digital workplace, promising unprecedented levels of... The integration of generative AI (GenAI) across an enterprise heralds a transformative potential for the digital workplace, promising unprecedented levels of innovation, efficiency, and productivity. Yet, realizing this potential comes with its own set of formidable challenges, especially when it comes to ensuring the technology is economically feasible and scalable for organization-wide deployment. # Overcoming Enterprise-Wide AI Deployment Challenges The landscape of GenAI solutions, characterized by isolated tools and per-user subscription models, further compounds these challenges, imposing significant financial burdens on businesses aiming to democratize AI access among their workforce. The good news: each of the 11 challenges below has a known mitigation path, and organizations that address them systematically are already capturing measurable returns. ## Top 11 Challenges of Integrating GenAI in the Digital Workplace As companies embark on integrating GenAI to revolutionize their digital workplaces, we've identified 11 key challenges that stand in the path of adoption. Overcoming these hurdles is crucial for unlocking the true value and productivity gains that AI can offer your business. Here's a closer look at these challenges, along with practical mitigation strategies for each: 1. **Substantial Subscription Costs and Economic Model Discrepancies:** The high costs associated with AI subscriptions, alongside their variability, make budgeting a complex task. This issue is compounded by economic models favoring high flat fees or per-user subscriptions, which not only strain resources but also hinder scalability across larger organizations. This financial model favors well-resourced tech giants and creates barriers for smaller enterprises and industries that could significantly benefit from AI, like manufacturing and healthcare. *Mitigation: Negotiate enterprise-wide or consumption-based licenses rather than per-seat models, and audit whether your existing intranet platform already bundles AI capabilities before adding standalone subscriptions. For context, traditional enterprise platforms can cost between $130,000 and $426,000 in the first year for a 1,000-user organization when customization, migration, and governance are included, per Awesome Technologies Inc.'s 2025 cost model cited by MangoApps—making AI subscription sticker shock a compounding problem, not an isolated one.* 2. **Limited Deployment Support:** Mainstream AI services such as ChatGPT and Gemini offer scant onboarding and implementation support, lacking in structured training and best practice guides. Organizations are often left to figure out AI capabilities on their own, leading to uneven usage and potential underperformance. *Mitigation: Require vendors to provide structured rollout plans with defined milestones. Frontline-heavy organizations that pair AI-curated content with a structured rollout plan have achieved 90% frontline adoption within the first six months—demonstrating that deployment support is a solvable variable, not a fixed constraint. Embedding AI guidance into your [learning and development strategy](/articles/learning-and-development-strategy-embedded-in-daily-work) accelerates time-to-competency.* 3. **Lack of Flexibility:** The disparate nature of AI tools and their associated costs can lock companies into specific vendors or technologies, limiting the ability to adapt to the most suitable or advanced AI solutions. This rigidity can stifle innovation and prevent organizations from leveraging the best that AI has to offer. *Mitigation: Prioritize platforms with open APIs and modular AI layers so that swapping or upgrading underlying models does not require re-platforming the entire digital workplace. Reviewing independent analyst assessments—such as the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report)—can help identify platforms with genuine architectural flexibility.* 4. **Unclear Use Cases:** The absence of direct, impactful GenAI applications dampens enthusiasm and investment, especially among businesses cautious of navigating unproven AI territories without assured returns. Only 22% of company intranets currently deliver personalized content to employees, per the State of the Digital Workplace & Modern Intranet 2024 report cited by Akumina—meaning most AI-layer deployments land on a content infrastructure that isn't segmented by role or persona, which compounds the unclear-use-case problem. *Mitigation: Start with high-frequency, measurable tasks—such as sop operations documentation, policy search, and shift-change communications—where AI can demonstrate time savings within weeks. Segmenting use cases by worker type (deskless vs. knowledge worker) sharpens the business case considerably.* 5. **Data Privacy and Security Concerns:** Employing AI without compromising data integrity demands adherence to stringent security measures and evolving regulations, a daunting task for many organizations. *Mitigation: Require vendors to provide data residency options, role-based access controls, and audit logs as baseline contractual commitments—not optional add-ons. Industries with strict compliance requirements, such as [ambulatory care](/industries/ambulatory-care), should validate that AI outputs are governed by the same data-handling policies as the underlying platform.* 6. **Auditability and Transparency Issues:** The opaque nature of some AI algorithms challenges the transparency and reliability of AI-derived insights and decisions, necessitating greater clarity. *Mitigation: Treat AI governance as a first-class feature requirement, not an afterthought. Platforms that surface usage analytics, flag low-confidence AI outputs, and maintain decision logs allow administrators to audit AI behavior continuously rather than reactively. MangoApps' analytics and governance layer is designed to address this gap directly, giving administrators visibility into what the AI surfaces, to whom, and why.* 7. **Limited Visibility into AI Utilization:** Without comprehensive insights into how AI tools are being utilized within the organization, optimizing deployments for maximum benefit becomes a significant challenge. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools—a baseline that makes it nearly impossible to detect whether AI features are driving incremental value without dedicated utilization dashboards. *Mitigation: Instrument AI features with adoption metrics from day one. AI-native platforms that surface role-relevant content have driven 30-point engagement score increases, per the Unily British Airways case study, suggesting that solving the visibility challenge has measurable employee-experience payoff.* 8. **Complex ROI Measurement:** The intangible nature of AI's benefits complicates the direct calculation of ROI, making it difficult for companies to justify financial investments against uncertain gains. *Mitigation: Anchor ROI models to quantifiable inputs. IDC research finds employees spend 2.5 hours per day searching for information—AI-assisted search that cuts that figure even by half produces a calculable productivity dividend. One enterprise captured $20M in cost avoidance after consolidating its digital workplace onto a single AI-enabled platform, demonstrating that hard-dollar ROI is achievable when the measurement framework is defined upfront.* 9. **Integration Challenges:** The technical hurdles of integrating AI with existing legacy systems require substantial adaptation, potentially hindering digital transformation efforts. *Mitigation: Prioritize AI deployments on platforms that already integrate with your core systems of record (HRIS, ERP, messaging) rather than building point-to-point connections. [Workforce management](/solutions/workforce-management) and scheduling workflows are often the fastest integration wins because the data structures are well-defined and the productivity impact is immediate.* 10. **Talent and Expertise Shortage:** The skyrocketing demand for AI skills surpasses supply, creating a bottleneck that limits the scope and scalability of AI initiatives. *Mitigation: Reduce dependency on scarce AI specialists by selecting platforms with no-code or low-code configuration layers. Pair this with a train-the-trainer model so internal champions can scale AI literacy without requiring every employee to become technically proficient. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines workforce capability-building approaches relevant to this challenge.* 11. **Organizational Resistance:** Cultural resistance to AI, from job displacement fears to doubts about its effectiveness, requires deliberate change management strategies to cultivate a supportive organizational mindset towards AI. Per Social Edge Consulting, while 91% of organizations operate an intranet, only 13% of employees use it daily and nearly a third never log in at all—a pattern that will repeat with AI tools if adoption is treated as automatic rather than designed. *Mitigation: Frontline-heavy organizations that prioritize mobile-first design have achieved 91% platform usage within weeks of launch, per the Unily British Airways case study, demonstrating that adoption resistance is solvable with the right deployment approach. Connecting AI rollout to visible employee benefits—faster answers, fewer repetitive tasks—converts skeptics faster than top-down mandates.* Without a practical approach to these myriad challenges, enterprises find themselves in a precarious position, struggling to deploy GenAI at scale in a manner that benefits the entire business and uplifts productivity across the board. This pivotal moment calls for a strategic shift towards identifying and leveraging practical GenAI use cases within the digital workplace. In a subsequent article, we delve into these practical use cases, providing a foundation for enterprises to understand how GenAI can be effectively integrated to transform operations, enhance employee productivity, and drive innovation. ## What Should Enterprises Do First? The 11 challenges above are not equally urgent for every organization. A practical sequencing framework helps: start with the challenges that block adoption entirely (cost model, deployment support, unclear use cases), then address the challenges that erode trust over time (auditability, data privacy, ROI measurement), and finally tackle the structural challenges that limit scale (integration, talent, organizational resistance). Organizations that have moved fastest share three traits: they selected a unified intranet platform rather than assembling point solutions, they defined success metrics before launch rather than after, and they segmented their workforce—deskless frontline workers versus knowledge workers—so that AI content delivery matched actual job context. The [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides independent context on how unified platforms are being evaluated against these criteria. ## How Do You Measure Whether Your AI Deployment Is Working? ROI measurement (challenge 8) and utilization visibility (challenge 7) are the two dimensions most likely to cause enterprises to abandon AI initiatives prematurely. A practical measurement stack includes: daily and weekly active usage rates by role and department, time-to-answer benchmarks for AI-assisted search versus unassisted search, and a quarterly cost-per-outcome review that ties AI spend to specific workflow improvements. For organizations managing [shifts and schedules](/solutions/shifts-schedules) or [time and attendance](/solutions/time-attendance) at scale, AI-assisted automation of these workflows produces some of the clearest before-and-after data, making them ideal pilot use cases for building the internal ROI narrative. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) offers additional benchmarks for workforce operations ROI measurement. ## What Comes After the 11 Challenges Are Addressed? Once the foundational barriers are cleared, the strategic opportunity shifts from deployment to differentiation. Enterprises that have resolved the cost, adoption, and governance challenges are moving toward persona-driven AI experiences—where the intranet surfaces different content, tools, and workflows depending on whether the user is a warehouse associate, a nurse, or a corporate analyst. This is where the productivity ceiling rises significantly, and where the gap between organizations that treated AI as a feature and those that treated it as an operating model becomes visible. For a deeper look at how these dynamics are playing out across industries, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the intersection of AI, employee experience, and communication strategy in detail. --- # Roadmap to AI-First Employee Experiences **Author:** MangoApps **Published:** 2024-09-05 **Category:** enterprise-ai Utilizing MangoApps AI Studio to integrate the use of AI Experts into your employees' workflows marks a pivotal moment in your digital transformation, a... # Roadmap to an AI-First Employee Experience: A Practical Guide for HR and Operations Leaders Building an AI-first employee experience is not a single technology purchase — it is a phased organizational shift that touches every layer of how work gets done, from the frontline to the back office. This roadmap breaks that shift into four concrete phases, explains what each phase delivers, and shows what outcomes organizations have already achieved. If you are evaluating where to start or how to accelerate, the direct answer is this: begin with AI Experts to establish a foundation, then extend AI into your employee app, your intranet, and finally your operational workflows. --- ## Why the Status Quo Is Expensive Before mapping the phases, it helps to understand what inaction costs. Employees spend an average of 2.5 hours per day searching for information (per IDC). Despite that burden, nearly a third of employees never log in to the intranet at all, and the average daily time spent using intranet tools is just six minutes (per SWOOP Analytics). Yet 91% of organizations still operate an intranet (per Social Edge Consulting) — meaning most companies are paying for infrastructure that most employees ignore. On the frontline, the problem compounds. Approximately 80% of the global workforce is deskless (per Emergence Capital), yet most enterprise software is designed for desk-bound employees with corporate email addresses. Frontline employee replacement costs range from $4,400 to $15,000 per worker, making disconnected mobile experiences a direct financial risk — not just an engagement problem. Employees also lose over four hours weekly switching between disconnected systems, and IT teams typically manage three to four times more tools than necessary. These are the conditions an AI-first roadmap is designed to fix. --- ## Phase 1: Establish a Foundation with AI Experts The first phase centers on deploying MangoApps AI Studio to give employees access to AI Experts — purpose-built AI assistants trained on your company's own knowledge, policies, and processes. This is not a generic chatbot layer; it is a centralized platform for managing AI services across the enterprise, with role-based access controls, data privacy guardrails, and IT oversight built in. Key capabilities in this phase include: - **Personalized AI for every role** — employees get answers relevant to their specific job function, not a one-size-fits-all response - **Custom AI training** on internal documents, SOPs, and operational procedures, reducing the 2.5 hours per day employees currently spend searching for information (per IDC) - **Data privacy and security controls** that keep sensitive information inside your environment - **IT governance** through comprehensive usage monitoring and role-based permissions This phase lays the groundwork. Once employees experience AI reducing friction in their daily work, adoption of subsequent phases accelerates significantly. --- ## Phase 2: Bring Frontline Workers into the Digital Workplace Only 13% of employees use an intranet daily (per Social Edge Consulting). For deskless workers — the 80% of the global workforce without a desk (per Emergence Capital) — that number is effectively zero, because most intranets require a corporate email address and a desktop browser to access. Phase 2 addresses this directly by deploying an AI-first [employee app](/solutions/employee-app) that works on personal devices, requires no corporate email address, and functions in low-connectivity environments. This is the no-email-required, offline-capable mobile access model that deskless workers actually need. What this phase delivers: - **Voice of the employee** — pulse surveys, employee engagement questionnaires, and feedback channels that reach workers who never touch a desktop - **Recognition and rewards** — peer-to-peer and manager-to-employee recognition tied to company values - **Shift, pay, and PTO visibility** — employees can check schedules, request time off, and view pay information without calling HR - **Personalized onboarding** — new hires complete structured onboarding tasks from their phone, reducing time-to-productivity - **Real-time alerts** — safety notices, policy updates, and operational changes reach every worker instantly Organizations that have consolidated disparate systems into a single mobile dashboard report measurable gains in workforce engagement within months of launch, with one large enterprise deployment reaching 90% frontline adoption within the first six months. A branded employee app approach has also been associated with 87% workforce engagement achieved within a few months of launch. For context on how scheduling and frontline communication intersect with engagement, [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) covers the operational side of this challenge in detail. --- ## Phase 3: Rebuild Your Intranet as an AI-Powered Hub Most intranets fail not because the technology is wrong but because the content goes stale and the experience is generic. When 91% of organizations run an intranet (per Social Edge Consulting) but the average employee spends only six minutes per day using it (per SWOOP Analytics), the intranet is not functioning as a workplace hub — it is functioning as a rarely-visited archive. An AI-first intranet changes the model. Instead of employees navigating a static site structure, AI surfaces relevant content, answers questions directly, and personalizes the experience based on role, location, and recent activity. AI-native intranet platforms can deploy personalized experiences for 1,000 or more employees in minutes rather than the months required by traditional IT-led implementations. Phase 3 capabilities include: - **AI-based search** that understands natural language queries and returns direct answers, not just document links - **Automated content freshness** — AI flags outdated pages and suggests updates, keeping the intranet relevant without manual audits - **Instant access to news, tools, and resources** from a single personalized homepage - **Brand-matched design** that reflects your company's identity without requiring developer resources - **An [employee directory](/key-features/employee-directory)** that connects colleagues across locations, departments, and time zones - **Sites and subsites** that department owners can create and manage without IT involvement For an independent assessment of how AI-first intranet platforms compare, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides a detailed vendor evaluation framework. One additional consideration for organizations evaluating legacy platforms: competitors have published total cost of ownership models for SharePoint-based intranets ranging from $130,000 to $426,000 in the first year for 1,000 users, driven by implementation, customization, and ongoing maintenance costs. An AI-first intranet built on a unified platform avoids most of those hidden costs by design. --- ## Phase 4: Extend AI into Operational Workflows The final phase moves AI beyond communication and information access into the operational processes that drive business outcomes — training, onboarding, idea management, workflow automation, and performance management. This is where employee engagement training and learning programs become embedded in daily work rather than scheduled as separate events. Research consistently shows that learning disconnected from the flow of work has low retention and low completion rates. [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) examines this problem and the design principles that address it. Phase 4 capabilities include: - **AI-driven training and learning** — personalized learning paths that adapt to role, skill gaps, and completion history - **AI-enhanced employee onboarding and task management** — structured workflows that guide new hires through their first 30, 60, and 90 days - **AI-powered idea management** — employees submit, vote on, and track innovation ideas without the ideas disappearing into a suggestion box - **No-code workflow automation** — operations teams build and modify approval workflows, SOP operations checklists, and process automations without engineering support - **Performance management** — continuous feedback cycles that replace annual reviews with ongoing development conversations Organizations that have deployed a unified AI employee experience platform across all four phases have reported $20 million in cost avoidance, driven by reduced tool sprawl, lower support costs, and faster time-to-productivity for new hires. For a broader view of where workforce operations are heading, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the macro trends shaping how organizations are investing in employee experience technology. --- ## Frequently Asked Questions ### How long does it take to see measurable results from an AI-first employee experience rollout? Timelines vary by organization size and starting point, but the benchmark data from enterprise deployments suggests 90% frontline adoption is achievable within the first six months of launching a mobile employee app. Intranet engagement improvements — measured by daily active users and search utilization — typically become visible within 60 to 90 days of deploying AI-based search and personalized homepages. ### Does an AI-first approach require replacing all existing systems at once? No. The four-phase roadmap is designed to be sequential and modular. Organizations typically start with Phase 1 (AI Experts) or Phase 2 (employee app) based on their most urgent pain point, then add phases as adoption matures. The goal is a unified platform that consolidates tools over time — not a single cutover that disrupts operations. ### How does employee engagement software fit into this roadmap? Employee engagement software — including employee engagement surveys, pulse tools, and recognition platforms — is embedded across all four phases rather than treated as a standalone product. In Phase 2, engagement questionnaires reach frontline workers through the mobile app. In Phase 3, the intranet surfaces engagement data and recognition feeds. In Phase 4, performance management tools close the loop between feedback and development. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading organizations are integrating engagement measurement into their broader employee experience architecture. --- ## What to Do Next The roadmap to an AI-first employee experience has four phases: AI Experts, frontline employee app, AI-powered intranet, and operational work apps. Each phase builds on the previous one, and each delivers measurable outcomes — reduced information search time, higher frontline adoption, lower total cost of ownership, and documented cost avoidance. The organizations that move first on this shift gain a structural advantage: lower operational costs, higher employee engagement, and faster adaptation to change. Those that wait inherit the costs of tool sprawl, disengaged frontline workers, and intranets that employees have already learned to ignore. If you are ready to assess where your organization sits on this roadmap, MangoApps offers a structured evaluation process that starts with your current state and maps a path to the outcomes that matter most to your business. --- # Generative AI's Vital Role in the Workplace **Author:** MangoApps **Published:** 2024-09-05 **Category:** enterprise-ai GenAI is transforming the workplace in ways we had only dreamed of until just over a year ago. It’s not just another buzzword; it’s genuinely revolutionizing... GenAI is transforming the workplace in ways we had only dreamed of until just over a year ago. It's not just another buzzword; it's genuinely changing how we work, making significant strides in productivity and changing the nature of tasks across industries. An MIT study of 444 professionals revealed that employees working with GenAI experienced a 37% productivity boost, underscoring the compelling case for businesses to deploy AI solutions broadly and efficiently. Yet most organizations are still leaving that productivity on the table — held back by fragmented tooling, governance concerns, and a workforce that never fully adopted the intranet in the first place. Per Social Edge Consulting, only 13% of employees use an intranet daily, and nearly a third never log in at all. This article explains what GenAI actually does in the workplace, where enterprises get stuck, and how to move forward. # Accelerating Productivity, Efficiency, and Innovation GenAI introduces four capabilities to the digital workplace, each with the potential to transform standard operations: **Instant Upskilling:** GenAI is transforming continuous learning by creating personalized learning paths, generating up-to-date training content, enabling immersive learning experiences through simulations, and providing 24/7 support via chatbots. This ensures training is relevant, engaging, and accessible to all employees, filling skill gaps efficiently. Connecting GenAI to a structured [learning management system](/solutions/learning-management) closes the loop between AI-generated content and formal LMS learning system workflows — a gap that leaves most upskilling initiatives disconnected from the skills data that would make them measurable. For a deeper look at why structured learning programs stall, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). **Content Creation:** Leveraging AI for content generation empowers employees to produce high-quality, creative outputs more efficiently, from drafting emails to generating reports, thereby enhancing communication and documentation processes. This extends naturally to SOP operations — AI can draft, version, and surface standard operating procedures so frontline teams always work from current documentation rather than outdated printouts. **Knowledge Capture:** GenAI transforms interactions into structured knowledge assets and updates expertise directories, making it easier to capture and share organizational knowledge. By summarizing transcripts and extracting key information in line with enterprise standards, GenAI enhances search accuracy and fosters a culture of collaboration and knowledge sharing. Effective [knowledge management](/solutions/knowledge-management) depends on this layer: without AI-assisted capture, institutional knowledge walks out the door every time an experienced employee leaves. AI-curated, persona-based content targeting by role, region, and language ensures GenAI surfaces relevant knowledge rather than generic results — a capability now standard among leading intranet competitors, per Unily and Akumina product documentation. **Knowledge Discovery:** By providing direct, natural language responses to queries, AI streamlines the process of finding information and completing administrative tasks, thereby reducing time spent on searches and increasing focus on core responsibilities. The scale of this problem is significant: per IDC, employees spend 2.5 hours per day searching for information. Semantic AI search that spans connected systems while respecting existing permissions returns role-aware results, making knowledge discovery governance-safe — a requirement competitors highlight as a key enterprise differentiator, per Akumina's product documentation. Connecting multiple AI engines — OpenAI, Google Gemini, Anthropic, Azure OpenAI — to a single enterprise [knowledge base](/key-features/knowledge-bases) lets organizations avoid vendor lock-in while training AI assistants on proprietary company data, per MangoApps integrations documentation. ## Reaching the Frontline: GenAI Isn't Just for Desk Workers Most GenAI workplace coverage is written entirely for office employees. That's a significant blind spot. Per Emergence Capital, 80% of the global workforce is deskless — frontline workers in retail, manufacturing, healthcare, and logistics who have no corporate email address and rarely sit at a desk. These employees need knowledge discovery, upskilling, and chatbot support just as much as their desk-based counterparts, and they need it on a mobile device during a shift. Delivering GenAI capabilities to this population requires a platform architecture built for mobile-first access, not a desktop intranet bolted onto a mobile app. Organizations that have made this shift report outcomes like 90% frontline adoption within the first six months of deploying an AI-native platform. For a practical framework on reaching this workforce, [The Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026 and beyond](/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) is a useful starting point. ## Significant Practical Considerations Are Holding Enterprises Back from GenAI Incorporating AI into strategic initiatives offers businesses unprecedented opportunities for innovation, employee empowerment, and streamlined operations, leading to sustainable growth and a sharper competitive edge. Yet, realizing the full spectrum of AI's advantages necessitates overcoming significant barriers, including integration complexities and skills shortages. Fragmentation is the most immediate barrier. Employees navigate 6–8 disconnected tools daily, creating communication fragmentation that GenAI-powered unified platforms are specifically designed to eliminate, per MangoApps product documentation. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools — a number that reflects how poorly most platforms fit into actual work patterns, not how little employees value information access. Per Social Edge Consulting, 91% of organizations operate an intranet, yet engagement remains chronically low. GenAI only compounds the problem if it's deployed as yet another disconnected tool rather than as an intelligence layer across a unified platform. Governance is the second major barrier, and the one enterprise buyers raise most often. AI that ignores existing access controls creates compliance risk. A [content governance engine](/key-features/content-governance-engine) that enforces permissions at the search and retrieval layer — so employees only surface content they're authorized to see — is the architectural requirement that separates a proof-of-concept from a production deployment. Skills management compounds this: organizations need visibility into which employees have which capabilities before they can build AI-assisted learning paths that close actual gaps. A dedicated [skills management](/key-features/skills-management) layer provides that foundation. The financial case for solving these problems is concrete. Organizations that have deployed AI-powered employee experience platforms at scale have documented $20M in cost avoidance as a direct outcome. ## What to Do Next: A Practical Path Forward The four GenAI capabilities described above — upskilling, content creation, knowledge capture, and knowledge discovery — are not independent projects. They compound each other when built on a shared knowledge layer. The practical sequence most enterprises follow: 1. **Audit your knowledge and knowledge management infrastructure first.** If your tools for knowledge management are fragmented — wikis here, file shares there, expertise living only in people's heads — GenAI will amplify that fragmentation rather than resolve it. Consolidating into a governed [libraries and knowledge base](/key-features/libraries) architecture is the prerequisite. 2. **Establish permission-aware AI search before expanding access.** Role-aware, governance-safe search is not a feature to add later; it's the trust signal that gets enterprise security teams to approve broader rollout. 3. **Connect your LMS learning system to your AI layer.** Personalized learning paths are only as good as the skills data and content inventory behind them. An integrated LMS that feeds into and draws from the same knowledge base closes the loop. 4. **Build a mobile-first deployment plan for frontline workers.** If 80% of your workforce is deskless (per Emergence Capital), a desktop-first rollout plan reaches 20% of your people. Organizations that follow this sequence — governed knowledge base, permission-aware AI search, integrated LMS, mobile frontline access — are the ones documenting measurable outcomes rather than stalled pilots. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarking on which platforms are delivering on these capabilities in production environments. --- # Why Enterprises Should Start GenAI Projects **Author:** MangoApps **Published:** 2024-09-05 **Category:** enterprise-ai Generative AI is the topic du jour for executives everywhere—it bubbled up very quickly with promises to change the way people work across almost every job r... # Why Enterprises Should Start GenAI Projects — and How to Do It Right Generative AI is no longer a pilot-phase curiosity. Enterprises that delay structured deployment are already ceding productivity gains, cost savings, and competitive ground to organizations that have moved. The business case is clear: employees spend an average of 2.5 hours per day searching for information (per IDC), and GenAI can compress that dramatically — but only when it is deployed in a governed, accessible environment rather than left to individual employees using personal accounts. This article explains the five core business reasons enterprises should start GenAI projects now, the governance and adoption challenges that derail most rollouts, and what a well-structured deployment actually looks like. --- ## The 5 Business Reasons to Start Enterprise GenAI Projects Now ### 1. Productivity Losses Are Already Measurable Employees spend an average of 2.5 hours per day searching for information (per IDC). Across a workforce of even 1,000 people, that is roughly 2,500 person-hours lost every single day to information retrieval. GenAI assistants trained on internal knowledge bases can answer policy questions, surface SOPs, and summarize documents in seconds — converting search time into productive work. The scale of the opportunity is reinforced by how little current tools are being used. According to SWOOP Analytics, the average employee spends just six minutes per day using intranet tools. That gap between what employees need and what they are actually getting from existing systems is exactly where GenAI can intervene. ### 2. Fragmented Consumer-Tool Adoption Creates Real Security Risk When enterprises do not provide a sanctioned AI environment, employees fill the gap themselves. Individual employees set up personal ChatGPT accounts and move data back and forth between those accounts and internal systems. There is no way to prevent sensitive company data from entering a public model that may use it for training, and no audit trail to detect when it happens. This is not a hypothetical risk. It is the default state at organizations that have not yet deployed a centralized solution. ### 3. Competitive Advantage Compounds Over Time Organizations that start GenAI projects now are building institutional knowledge about what works — which use cases drive adoption, which models perform best for specific tasks, and how to govern AI outputs responsibly. That operational knowledge is not easily replicated by a competitor that starts 18 months later. Enterprises that centralize AI deployment inside an intranet can achieve frontline adoption rates above 90% within the first six months, versus fragmented consumer-tool rollouts that lack measurable adoption benchmarks (per Unily / CVS case study). The compounding effect of early adoption is significant. ### 4. Cost Avoidance Is Quantifiable The ROI case for enterprise GenAI is not speculative. A global enterprise that centralized its digital workplace on an AI-integrated intranet platform captured $20 million in cost avoidance (per Unily). The savings came from reduced IT overhead, lower training costs, and fewer support tickets — not from headcount reduction. A consumption-based deployment model, where LLM usage is charged by actual use rather than per-user licensing, also means enterprises can deploy to their entire workforce without paying for seats that go unused. ### 5. The Deployment Timeline Is Shorter Than Most IT Teams Expect One of the most common reasons enterprises delay GenAI projects is the assumption that deployment requires a long IT-led implementation. That assumption is outdated. A fully mobile, frontline-ready AI-enabled intranet can be launched in as little as 8 weeks for a workforce of 40,000 employees (per Unily / British Airways case study). The 91% usage rate that organization achieved post-rollout demonstrates that speed does not come at the expense of adoption. --- ## The Real Challenges of Enterprise GenAI Deployment Understanding why to start is only half the picture. The other half is understanding what makes most enterprise AI rollouts fail. ### Lack of Centralized Oversight Without a centralized deployment environment, there is no way to monitor AI usage, enforce data governance policies, or understand which employees are using which tools for what purposes. Consumer GenAI vendors are not building enterprise governance into their products — that responsibility falls to the organization. ### Low Adoption Among Non-Technical Employees According to Social Edge Consulting, 91% of organizations operate an intranet, but only 13% of employees use it daily, and nearly a third never log in at all. The same adoption failure pattern applies to AI tools when they are deployed as standalone products that require separate logins, separate training, and separate workflows. The solution is not better change management communications — it is embedding AI into the environment where employees already work. ### Personalization Gaps Only 22% of company intranets currently deliver personalized content to employees, making AI-driven personalization a meaningful differentiator rather than a standard feature (per Akumina / State of the Digital Workplace & Modern Intranet 2024 research). When every employee sees the same generic interface, adoption suffers — particularly among frontline and deskless workers whose needs differ significantly from office-based staff. ### The Frontline Access Problem Approximately 80% of the global workforce is deskless (per Emergence Capital). These employees — in retail, manufacturing, healthcare, logistics, and field services — are the hardest to reach with new technology and the most likely to be left out of enterprise AI rollouts that are designed for desktop users. Any GenAI deployment strategy that does not account for mobile-first, frontline access is excluding the majority of the workforce from day one. --- ## What a Well-Structured Enterprise GenAI Deployment Looks Like The most effective enterprise GenAI deployments share several characteristics: **They live inside the intranet, not alongside it.** Embedding AI assistants inside the [company intranet](/solutions/modern-intranet) — where employees already go for news, policies, and HR information — eliminates the adoption barrier of a separate tool. Employees do not need to learn a new system; they encounter AI in the flow of work they already do. **They are governed from day one, not retrofitted.** AI assistants should be permission-scoped and persona-targeted at launch. Different cohorts of employees — by role, department, or location — should see different AI assistants configured for their specific use cases. This is not an add-on; it is a design requirement. [Department sites](/key-features/department-sites) and role-based permissions make this kind of targeted deployment practical at scale. **They use Retrieval-Augmented Generation (RAG) to keep data inside the enterprise boundary.** RAG technology allows AI assistants to answer questions using internal documents and knowledge bases without sending that data to public models. Public models are not trained on your data, and your proprietary information remains within your environment. **They are built for the 80%.** A GenAI deployment that works only for office-based employees on desktop browsers is not an enterprise deployment — it is a departmental pilot. Frontline workers need mobile-first access, simple interfaces, and AI assistants configured for their specific SOP operations and task workflows. **They produce analytics that connect usage to outcomes.** Centralized deployment means centralized visibility. Administrators can see which AI assistants are being used, by which employee segments, and for what types of queries. That data makes it possible to iterate on use cases, justify continued investment, and identify where adoption is lagging. --- ## How MangoApps Approaches Enterprise GenAI Deployment MangoApps integrates GenAI directly into its intranet platform, allowing organizations to deploy purpose-built AI assistants to specific employee cohorts without requiring separate logins or standalone tools. The platform uses a consumption-based LLM pricing model, supports multiple LLM providers without vendor lock-in, and applies enterprise-grade security protocols including RAG-based data containment. For organizations in regulated industries — healthcare, government, financial services — the platform's existing compliance infrastructure extends to AI features rather than requiring a separate governance layer. HRIS integration allows AI assistants to be personalized by role, location, and department from day one, addressing the personalization gap that affects 78% of current intranet deployments. The [company portal](/key-features/company-portal) serves as the single access point for employees across desktop and mobile, ensuring frontline workers are included in the deployment rather than treated as an afterthought. For organizations evaluating intranet platforms as the foundation for GenAI deployment, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent analysis of how leading platforms compare on AI readiness and employee experience capabilities. --- ## Frequently Asked Questions ### How long does it take to deploy enterprise GenAI inside an intranet? Deployment timelines vary by organization size and complexity, but the assumption that enterprise AI requires a multi-year IT project is not accurate. A workforce of 40,000 employees can have a fully mobile, AI-enabled intranet live in as little as 8 weeks (per Unily / British Airways case study). The key variables are data readiness, permission structure, and how many AI assistants need to be configured at launch. ### What is the ROI case for enterprise GenAI? The most direct ROI levers are information retrieval time (IDC estimates 2.5 hours per day per employee), support ticket reduction, and training cost savings. A global enterprise captured $20 million in cost avoidance after centralizing its digital workplace on an AI-integrated intranet (per Unily). Organizations should also account for the cost of *not* deploying — specifically, the security exposure created when employees use unsanctioned consumer AI tools with company data. ### How do you drive adoption among non-technical and frontline employees? Adoption among non-technical employees is primarily a placement problem, not a training problem. When AI tools require a separate login, a separate app, or any additional setup, adoption rates drop sharply — particularly for the 80% of the global workforce that is deskless (per Emergence Capital). Embedding AI inside the intranet employees already use, configuring it for specific roles, and making it available on mobile are the three highest-leverage adoption drivers. Organizations that have taken this approach have achieved frontline adoption rates above 90% within six months (per Unily / CVS case study). --- ## The Bottom Line Enterprises should start GenAI projects now because the productivity losses from delay are already measurable, the security risks from unsanctioned consumer-tool use are already present, and the deployment timelines are shorter than most organizations assume. The organizations building operational AI knowledge today will have a compounding advantage over those that wait. The most important structural decision is where GenAI lives. Deploying it inside the intranet — where employees already work, where governance already exists, and where frontline workers can be reached on mobile — is the approach most likely to produce measurable adoption and quantifiable ROI rather than a pilot that never scales. For a broader view of how workforce operations and technology are converging in 2026, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the key trends shaping enterprise technology decisions this year. --- # Transforming Business With AI: Strategies & Insights **Author:** MangoApps **Published:** 2024-09-05 **Category:** enterprise-ai Business is moving faster than ever, and competitive advantages can vanish overnight. To stay ahead, companies must continuously innovate, and generative AI ... ## Transforming Business With AI: Strategies & Insights Business is moving faster than ever, and competitive advantages can vanish overnight. To stay ahead, companies must continuously innovate, and generative AI has become a crucial tool in this effort, enabling businesses to move quickly and efficiently. Amidst the extensive discussions around generative AI, we've compiled strategic insights and actionable strategies from recent research to help you integrate AI into your workplace effectively. By focusing on these key areas, you can streamline processes, enhance [employee experience](/solutions/modern-hcm), and maintain your competitive edge. ### 1. Use AI to Automate Routine and Repetitive Tasks Generative AI is incredibly effective at handling repetitive tasks, freeing up valuable time for employees to focus on more strategic activities. In customer service, AI chatbots can manage routine inquiries, allowing human agents to deal with more complex issues that require a personal touch. Sales teams benefit from AI by automating data entry and CRM updates, which reduces administrative overhead and allows salespeople to concentrate on building relationships and closing deals. Note that employees currently spend an average of 2.5 hours per day searching for information, per IDC — a direct drag on productivity that AI-powered search and knowledge tools are designed to eliminate. Employees also navigate 6–8 disconnected tools daily, creating communication fragmentation that AI-powered unified platforms are designed to address. Taking an industry view in retail, AI-driven systems can automatically reorder stock, ensuring that shelves are always stocked without requiring constant manual oversight. Healthcare providers can use AI to handle appointment scheduling and send reminders, freeing up administrative staff to focus on patient care. No-code workflow automation can handle shift swapping, PTO requests, task assignments, and routine approvals without IT involvement — directly reducing the administrative overhead that accumulates across departments. By deploying AI in these areas, businesses can significantly boost productivity and improve the quality of service they offer. ### 2. Invest in AI Adoption and Training The successful implementation of AI isn't just a matter of introducing new technology; it requires a cultural shift within the organization. Comprehensive training programs are essential to help employees understand how to use AI tools effectively. For example, a logistics company might provide hands-on training for warehouse workers to use AI-powered devices for tracking packages and managing inventory. This training should go beyond the initial onboarding to include continuous learning opportunities and support systems. By fostering a culture of continuous improvement and innovation, businesses can ensure that their employees are not only comfortable with AI but also adept at using it to its full potential. This approach maximizes the benefits of AI and encourages broader acceptance and integration across the organization. For a deeper look at why structured programs often fall short, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ### 3. Build AI-Driven Learning & Development Into Daily Work Workplace learning and development is one of the highest-impact — and most underutilized — AI use cases in the enterprise. Integrating AI with an LMS learning system allows organizations to deliver personalized, role-specific training at scale, moving beyond one-time onboarding events to continuous skill development embedded in daily workflows. Video learning, microlearning modules, and AI-curated content paths can surface the right material at the moment of need, rather than requiring employees to hunt through static course libraries. Organizations that deploy mobile-accessible training and digitized workflows report 50% faster new-hire onboarding compared to manual processes. Frontline workers — who represent 80% of the global workforce, per Emergence Capital — are particularly underserved by traditional learning approaches that assume desk access and a corporate email address. AI-native learning and development tools that work on mobile devices, without requiring a login to a desktop portal, close this gap meaningfully. For practical guidance on building these programs, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers emerging learning models in detail. ### 4. Prioritize Roles with High AI Impact Certain roles within an organization stand to gain more from AI integration than others. Customer service representatives, for example, can use AI to access real-time information and support, enabling them to resolve customer inquiries more efficiently and effectively. Sales teams can leverage AI to analyze purchasing patterns and predict customer needs, which allows for more personalized recommendations and higher conversion rates. In product development, AI can assist with predictive maintenance by identifying potential issues before they cause significant downtime, thereby ensuring that machinery operates smoothly and efficiently. By prioritizing AI implementation in these high-impact areas, businesses can achieve substantial gains in productivity, service quality, and innovation. ### 5. Consider the Context — Then Customize with Governance AI tools are most effective when they are tailored to the specific needs and workflows of different departments within an organization. Customization ensures that AI solutions address the unique challenges and opportunities of each area. For instance, a hospital might need AI tools that assist with regulatory compliance and patient data security, while a retail chain might focus on AI-driven personalized marketing and customer engagement. Beyond simple tailoring, governed AI — scoped by role, region, and language — is now a baseline expectation for organizations in regulated industries. Persona-based AI content targeting ensures that employees only see information relevant to their role and clearance level, which is essential for compliance in healthcare, finance, and other regulated sectors. This framing also matters for [ambulatory care](/industries/ambulatory-care) environments where patient data governance is non-negotiable. Tailoring AI applications to fit these specific requirements ensures that the technology is relevant and valuable, leading to higher adoption rates and better outcomes. ### 6. Enhance Employee Experience AI has the potential to significantly improve the employee experience by reducing the cognitive load associated with routine tasks and making work more manageable. In industries with high turnover rates, such as retail and hospitality, AI can automate [shifts and schedules](/solutions/shifts-schedules) to ensure fair shift assignments and reduce conflicts. This not only improves job satisfaction but also enhances overall productivity by allowing employees to focus on more meaningful tasks. Regular feedback loops and surveys can provide valuable insights into how employees perceive AI tools and identify areas for improvement. By prioritizing a positive employee experience, businesses can help keep their workforce motivated and engaged, which is essential for sustaining innovation and growth. A single enterprise deploying an AI-powered employee experience platform has captured $20M in cost avoidance — a figure that underscores why the employee experience platform category is attracting serious investment. ### 7. Prepare for Organizational and Workflow Changes As AI tools become more integrated into daily operations, they will inevitably lead to changes in workflows and job roles. Employees may transition from performing routine tasks to focusing on customer engagement and problem-solving. For example, retail associates might spend less time on inventory checks and more time assisting customers directly. The [Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) offers concrete examples of how these workflow shifts play out on the ground. Proactively redesigning workflows and updating standard operating procedures (SOPs) can help ensure a smooth transition and maximize the benefits of AI. Additionally, AI can facilitate better teamwork management across teams and departments by breaking down silos and promoting cross-functional cooperation. Preparing for these changes in advance helps to minimize disruption and ensures that the organization can fully capitalize on the advantages of AI. ### 8. Encourage Experimentation and Innovation Generative AI offers immense potential for driving innovation within an organization. Encouraging employees to experiment with AI tools can lead to the discovery of new ways to enhance their work and improve business processes. In frontline industries, this might involve using AI to analyze customer feedback, optimize store layouts, or develop new product offerings based on consumer trends. By fostering a culture of experimentation and innovation, businesses can uncover new opportunities and maintain a competitive edge in the market. This approach also helps to keep the organization agile and responsive to changing market conditions, ensuring long-term success. --- ## How to Measure AI ROI and Know If It's Working One of the most common questions after committing to an AI strategy is: how do we know it's working? The most reliable leading indicators are time-based: track reductions in the hours employees spend on the specific tasks AI was deployed to handle. IDC benchmarks the information-search problem at 2.5 hours per employee per day — if AI-powered search and knowledge tools are deployed, measure whether that number drops within 60–90 days. For learning and development investments, measure new-hire time-to-productivity before and after deploying an AI-integrated LMS learning system. For workflow automation, count the number of manual approvals, shift-swap requests, and SOP-related help-desk tickets before and after deployment. Frontline worker adoption rates are a leading indicator of long-term ROI: organizations that achieve 90% platform adoption within the first six months — a benchmark documented in the Unily CVS case study — consistently report stronger downstream productivity gains than those with fragmented rollouts. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides a framework for tracking these metrics across workforce segments. ## What Are the Risks of AI Adoption — and How Do You Manage Them? The most frequently cited risks in enterprise AI adoption fall into three categories: governance failures, workforce resistance, and integration complexity. Governance failures occur when AI surfaces information to employees who shouldn't have access to it — a risk that persona-based, permission-respecting AI architectures are specifically designed to prevent. Workforce resistance is most acute when employees perceive AI as a replacement rather than a support tool; transparent communication about role changes and investment in learning and development programs directly reduces this risk. Integration complexity is often underestimated. Employees already navigate 6–8 disconnected tools daily, and adding an AI layer on top of a fragmented stack can worsen the problem rather than solve it. The organizations that manage this risk most effectively consolidate onto unified platforms before — or in parallel with — AI deployment, rather than bolting AI onto existing tool sprawl. For workforce management contexts specifically, [workforce management solutions](/solutions/workforce-management) that include native AI capabilities reduce integration risk compared to point solutions. ## How Long Does AI Implementation Take? Implementation timelines vary by scope, but a practical framework for most mid-to-large enterprises looks like this: a focused pilot in one high-impact department (customer service, scheduling, or onboarding) typically reaches measurable outcomes within 60–90 days. Broader rollout across multiple departments, including change management, training, and SOP updates, typically takes 6–12 months to reach stable adoption. Frontline deployments — where 80% of the global workforce operates without a desk or corporate email, per Emergence Capital — require mobile-first tooling and often benefit from a phased rollout that prioritizes the highest-density locations first. The most important timeline variable is change management investment. Organizations that pair AI deployment with structured learning and development programs and clear communication about workflow changes consistently reach full adoption faster than those that treat implementation as a purely technical project. The [Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026 and beyond](/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) covers deployment sequencing in detail for organizations with large deskless populations. --- ## Conclusion Generative AI offers measurable potential to transform business operations — from reducing the 2.5 hours per day employees lose to information search (per IDC) to accelerating new-hire onboarding by 50% and capturing millions in cost avoidance through smarter automation. The strategies that work share a common structure: start with high-impact, measurable use cases; invest in learning and development so employees can use AI tools effectively; govern AI deployments by role and region to manage compliance risk; and build for the 80% of the global workforce that is deskless, per Emergence Capital. Success is not measured by the number of AI tools deployed but by adoption rates, time-to-productivity improvements, and reductions in administrative overhead. Organizations that track these metrics from day one — and adjust their approach based on what the data shows — are the ones that convert AI investment into durable competitive advantage. To explore how MangoApps AI Studio supports these strategies in practice, start with the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) for context on where AI fits within a broader workforce communications and operations strategy. --- # MangoApps Has Achieved HITRUST Recertification through 2026 **Author:** MangoApps **Published:** 2024-08-27 **Category:** press-release With this recertification, MangoApps remains the only employee experience platform that maintains an active HITRUST Certification. **ISSAQUAH, Wash. – August 27, 2024** – MangoApps, a leading provider of unified employee experience solutions, is proud to announce its successful recertification under the HITRUST Risk-based, 2-year (r2) Certified status. This recertification demonstrates MangoApps' ongoing commitment to maintaining the highest standards of security and privacy for its customers, particularly those in highly regulated industries such as healthcare, financial services, and government — and MangoApps remains the only employee experience platform that is HITRUST-certified. The HITRUST Certification is recognized as a benchmark for compliance, risk management, and data protection that is used by organizations across multiple industries. By achieving recertification, MangoApps continues to prove that its platform adheres to the most stringent security controls and industry standards, ensuring that customers' sensitive data remains protected. ## Sustaining Excellence in Security Compliance MangoApps first achieved HITRUST Certification in 2022, and this recertification underscores the company's unwavering dedication to upholding rigorous security protocols. The HITRUST r2 Certification involves an extensive evaluation of an organization's information security management, including assessments of its policies, procedures, and overall security posture. "Our recertification with HITRUST is a testament to our continuous efforts in prioritizing data security and regulatory compliance," said Vishwa Malhotra, CTO and co-founder of MangoApps. "The digital landscape is constantly evolving. With many customers in sensitive and highly regulated industries, they must have confidence that MangoApps will always do everything it can to protect the company and its employees. We have this achievement reflects to them our commitment in protecting their data with the highest level of integrity and security." ## Supporting Customer Confidence In an environment where data breaches and cyber threats are increasingly prevalent, MangoApps' HITRUST recertification provides customers with the assurance that their data and operations will remain secure in MangoApps. This milestone maintains MangoApps leadership in providing secure, reliable solutions that empower organizations to manage their [employee experience](/solutions/employee-app) with peace of mind. By maintaining its HITRUST certification, MangoApps can continue to provide: - **Comprehensive Data Protection:** Recertification ensures that the MangoApps platform maintains stringent controls over data access, management, and protection, that meet the industry's highest security requirements. - **Ongoing Compliance Assurance:** The recertification process reaffirms MangoApps' dedication to adhering to regulatory frameworks and industry standards, helping customers meet their own compliance obligations. - **Enhanced Trust and Reliability:** With this recertification, customers can continue to trust MangoApps as a reliable partner in safeguarding their sensitive information and [employee data](/solutions/employee-data). The new HITRUST Certification will remain active through 2026, at which point MangoApps will go through an additional recertification process to maintain compliance. More information about MangoApps' commitment to security, privacy, and compliance is available on the MangoApps website at: www.mangoapps.com/security-compliance. ## What Does HITRUST r2 Certification Actually Cover? HITRUST r2 certification is materially different from SOC 2 or ISO 27001 alone. The HITRUST r2 assessment evaluates an organization against 200+ security control requirements across 19 control categories — including access control, encryption, incident response, privacy, and risk management (source: HITRUST official certification framework documentation). This breadth means that when MangoApps achieves recertification, it is not simply checking a compliance box; it is demonstrating validated controls across the full spectrum of information security domains that regulated industries require. For customers in healthcare, financial services, and government, this distinction matters at the procurement stage. Regulated industries require vendors to demonstrate third-party-validated security frameworks before procurement approval, making HITRUST a procurement differentiator, not just a compliance checkbox (source: HITRUST Alliance industry adoption documentation). In healthcare specifically, 83% of healthcare organizations require HITRUST certification from SaaS vendors as part of their vendor risk management process. In practical terms, MangoApps' HITRUST status gives customers the audit evidence they need — documented controls, validated policies, and a certified security posture — to satisfy their own internal compliance and vendor risk teams without conducting independent assessments of the platform. ## Which Industries Benefit Most from MangoApps' HITRUST Certification? HITRUST certification is most consequential for organizations operating under strict regulatory oversight. Three verticals stand out: - **Healthcare:** Hospitals, health systems, and payers must protect patient data under HIPAA and related frameworks. HITRUST r2 certification aligns directly with HIPAA security rule requirements, giving healthcare organizations a pre-validated path to vendor approval. - **Financial Services:** Banks, credit unions, and insurance carriers face overlapping regulatory requirements from bodies such as the FFIEC and state regulators. MangoApps' [financial services](/industries/financial) customers can point to HITRUST certification as evidence of third-party-validated controls when satisfying their own audit obligations. - **Government and Public Sector:** Government agencies and their contractors increasingly require FedRAMP-aligned or HITRUST-certified vendors. HITRUST's control framework maps to NIST 800-53, making MangoApps a credible option for agencies evaluating compliant productivity apps and workforce management platforms. MangoApps is the only unified employee experience platform — combining intranet, frontline app, and [workforce management](/solutions/workforce-management) — to hold HITRUST r2 certification. Competitors such as Unily, Staffbase, and Beekeeper do not publicly claim equivalent certification (source: Competitor product pages — Unily, Staffbase, Beekeeper — no HITRUST claim found), making this a meaningful differentiator for procurement teams in regulated industries evaluating cloud based productivity applications for their workforce. ## How Does HITRUST Compare to Other Security Certifications? Organizations evaluating cloud based productivity apps frequently encounter multiple certification frameworks — SOC 2 Type II, ISO 27001, and HITRUST among them. Each serves a different purpose: - **SOC 2 Type II** validates that a vendor's controls were operating effectively over a defined period, but the control criteria are flexible and self-scoped by the vendor. - **ISO 27001** certifies that an organization has implemented an information security management system, but does not prescribe specific control requirements. - **HITRUST r2** is prescriptive: it mandates specific controls across 19 categories, maps to more than 40 authoritative sources (including HIPAA, NIST, PCI DSS, and ISO 27001), and requires third-party assessment by an approved HITRUST External Assessor. The result is a certification that regulated industries treat as a higher bar than SOC 2 or ISO 27001 alone (source: HITRUST official certification framework documentation). For organizations selecting productivity apps or employee experience platforms, HITRUST r2 certification provides a level of assurance that general-purpose certifications do not replicate. MangoApps' recertification through 2026 means customers can rely on that assurance without waiting for the next audit cycle. For a broader view of how MangoApps is recognized by independent analysts, see the [IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment](/resources/idc-marketscape-2024). ## About MangoApps At MangoApps, our mission is to create a world where all employees, whether they work at a desk or on the frontline, are engaged, efficient, and fulfilled. Our unified modern intranet and employee app platform redefines the work experience by providing consistency and rich engagement for employees no matter where they are. With a 15-year history, MangoApps is trusted by companies all over the world, from SMBs to enterprises. Rethink the employee experience at www.mangoapps.com. --- # MangoApps Now Available in Okta Integration Network to Automate User Provisioning, Access and Authentication **Author:** MangoApps **Published:** 2024-08-26 **Category:** press-release MangoApps integration with Okta includes support for Secure Web Authentication (SWA), Security Assertion Markup Language (SAML) and System for Cross-domain Identity Management (SCIM).  **ISSAQUAH, Wash. – August 26, 2024 –** MangoApps, a leading provider of unified employee experience solutions, has made its platform available in the Okta Integration Network (OIN). With its new listing in the OIN, MangoApps is helping to simplify user provisioning and access management for customers utilizing Okta's industry-leading access management solutions. MangoApps includes support for Secure Web Authentication (SWA), Security Assertion Markup Language (SAML) and System for Cross-domain Identity Management (SCIM). ## Streamlined User Provisioning and Access Management MangoApps' integration with Okta includes comprehensive support for Secure Web Authentication (SWA), Security Assertion Markup Language (SAML), and System for Cross-domain Identity Management (SCIM). This integration enables real-time synchronization of user data and Single Sign-On (SSO) access between Okta and MangoApps. As employees join, move within, or leave an organization, their access to MangoApps is automatically managed and updated, ensuring precise and timely control over user accounts and enhancing overall security. Automated offboarding via identity provider integration can trigger access revocation the moment a departure date is logged, reducing the window of unauthorized access after employee exit — a meaningful data-breach risk reduction benefit, not merely an administrative convenience (source: Workvivo / product page — offboarding journey automation tied to provisioning file). For organizations managing [workforce management](/solutions/workforce-management) at scale, this kind of automated lifecycle control is increasingly a compliance requirement, not an optional feature. "Security is at the heart of our mission and a fundamental value of the MangoApps platform. Our integration in the Okta Integration Network (OIN), supporting SWA, SAML, and SCIM, reflects our unwavering commitment to innovation and excellence in user management and security," said Vishwa Malhotra, CTO and co-founder of MangoApps. "Our product team is dedicated to delivering the best possible experience for our customers, from end-users to administrators. We're proud to offer this expanded integration, which enhances efficiency in managing user access, reduces administrative overhead, and ensures that user information remains accurate and up-to-date." ## Key Benefits of MangoApps Integration with Okta 1. **Automated User Provisioning:** Automatically creates, updates, and deactivates user accounts in MangoApps based on changes in Okta, streamlining identity management across the organization. 2. **Real-Time Synchronization:** Keeps user information such as roles, groups, and profile details continuously up-to-date across both Okta and MangoApps, ensuring consistency and accuracy. 3. **Enhanced Security:** Leverages Okta's SWA and SAML capabilities to provide secure Single Sign-On (SSO) access to MangoApps, while automatically revoking access when users are deactivated in Okta, minimizing the risk of unauthorized entry. 4. **Improved Compliance:** Maintains a clear audit trail of user provisioning, de-provisioning, and authentication activities, supporting regulatory compliance frameworks including SOC 2 and HIPAA, and simplifying security audits. Compliance audits are simplified when the platform maintains a continuous, queryable audit trail of every provisioning, de-provisioning, and authentication event across integrated systems (source: Unily / product page — content governance and search audit positioning). Beyond login permissions, integrating identity management with a unified employee platform means role and group changes in Okta instantly reflect in content targeting, shift access, and personalized feeds — not just authentication (source: MangoApps own product page — unified data layer / retail positioning). This positions the Okta integration as one node in MangoApps' broader ecosystem of 200+ enterprise integrations, giving IT decision-makers a single, consistent identity layer across cloud-based productivity applications. MangoApps maintains a 98% customer retention rate, a trust signal for organizations evaluating long-term identity management partnerships. Employee engagement is directly tied to how well tools and access are managed: highly engaged workplaces report 23% higher productivity and 78% less absenteeism (per gallup.com). Ensuring employees have the right access to the right productivity apps at the right time — automatically — is a foundational step toward that outcome. Customers can access MangoApps integration details in the Okta Integration Network. For a broader view of how MangoApps connects with enterprise tooling, the [MangoApps & Microsoft Integration Guide](/resources/mangoapps-microsoft-integration-guide) illustrates the platform's approach to third-party identity and productivity ecosystems. Organizations evaluating the platform's positioning in the market can also reference the [IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment](/resources/idc-marketscape-2024). ## How to Enable the MangoApps–Okta Integration Enabling the integration requires an active MangoApps account and an Okta tenant with administrator access. The general setup path follows these steps: 1. **Locate MangoApps in the OIN:** Search for "MangoApps" in the Okta Integration Network catalog and add the application to your Okta org. 2. **Configure SSO (SWA or SAML):** Select your preferred authentication method. SAML is recommended for enterprise deployments requiring federated identity. Your MangoApps administrator will need to supply the SAML metadata or ACS URL from the MangoApps admin console. 3. **Enable SCIM Provisioning:** In the MangoApps admin console, generate a SCIM bearer token and enter it in the Okta provisioning settings. Enable the provisioning features you require: Create Users, Update User Attributes, Deactivate Users. 4. **Map Attribute and Group Assignments:** Define which Okta groups map to MangoApps roles and content groups. These mappings determine not only login access but also personalized feed targeting and shift-schedule visibility within MangoApps — relevant for teams using [shifts and schedules](/solutions/shifts-schedules) or [time and attendance](/solutions/time-attendance) modules. 5. **Test and Validate:** Assign a test user in Okta and confirm the account is provisioned in MangoApps with the correct role, group membership, and profile attributes before rolling out to the full organization. For prerequisites or environment-specific configuration questions, contact MangoApps support or your dedicated customer success manager. ## Common Use Cases for the Okta–MangoApps Integration **Healthcare and regulated industries:** Organizations in ambulatory care and similar regulated environments use the SCIM integration to maintain continuous audit trails required for HIPAA compliance, ensuring that access records are queryable at any point during an audit cycle. Teams managing [ambulatory care](/industries/ambulatory-care) workflows benefit from role-based content targeting that updates automatically when clinical staff change departments. **High-turnover and frontline workforces:** Retail, logistics, and BPO operations with frequent onboarding and offboarding cycles rely on automated provisioning to eliminate manual IT tickets. For [BPO](/industries/bpo) environments where agent roles shift frequently, real-time group synchronization ensures that content feeds, knowledge bases, and shift tools reflect current assignments without administrator intervention. **Enterprise IT consolidation:** Organizations consolidating cloud-based productivity apps under a single identity provider use the OIN listing to bring MangoApps under the same SSO umbrella as their other SaaS tools, reducing password fatigue and centralizing access governance. ## What This Means for IT and HR Teams: A Definitive Takeaway The MangoApps listing in the Okta Integration Network resolves a specific, recurring pain point: the gap between identity provider records and the employee experience platform. When an employee's role changes in Okta, that change now propagates automatically into MangoApps — updating not only login access but also the content, tools, and workflows that employee sees. When an employee exits, access is revoked at the IdP level and reflected in MangoApps immediately, closing the post-departure access window that represents a measurable security exposure. For IT teams, this means fewer manual provisioning tickets, a continuous audit trail for compliance reviews, and a single source of truth for user identity across the organization's cloud-based productivity applications. For HR and operations teams, it means onboarding and offboarding workflows tied to [modern HCM](/solutions/modern-hcm) processes execute without requiring separate action in the employee platform. For security and compliance officers, it means every provisioning, de-provisioning, and authentication event is logged and queryable — a requirement, not a bonus, under frameworks like SOC 2 and HIPAA. Organizations ready to evaluate the full scope of what a unified employee platform delivers alongside identity automation can start with [How An Employee SuperApp Transforms The Workplace](/resources/how-an-employee-superapp-transforms-the-workplace). ## About MangoApps At MangoApps, our goal is a world where all employees, whether they work at a desk or on the frontline, are engaged, efficient, and fulfilled. Our unified modern intranet and employee app platform is the all-in-one solution that redefines the work experience by providing consistency and rich engagement for employees no matter where they are. With a 15-year history, MangoApps is trusted by companies all over the world from SMB to Enterprise. Rethink the employee experience at www.mangoapps.com. --- # MangoApps vs. WorkVivo: A Comparative Guide **Author:** MangoApps **Published:** 2024-07-11 **Category:** comparisons When comparing MangoApps and WorkVivo, it’s clear that each has its ideal fit. WorkVivo, now part of Zoom, offers a solid option for companies already deeply... # MangoApps vs. WorkVivo: A Comparative Guide ## The acquisition signal most buyers miss In 2025, Workplace from Meta shut down. The platform had millions of enterprise subscribers when Meta acquired it in 2012. Over thirteen years, it received intermittent investment while Meta's consumer products took priority, and eventually the company decided an enterprise employee platform wasn't core to its mission. WorkVivo was acquired by Zoom in 2023. That parallel is worth examining before signing a multi-year contract. Per IDC research, employees spend 2.5 hours per day searching for information — which means an intranet that fails to drive adoption costs an enterprise measurable productivity at scale. Per Social Edge Consulting, 91% of organizations already run an intranet, yet nearly a third of employees never log in, and only 13% use one daily. Per SWOOP Analytics, average daily intranet use runs six minutes. These numbers reflect what happens when an employee platform isn't the vendor's primary mission. WorkVivo's acquisition by Zoom makes it a strong choice for companies that are deeply embedded in the Zoom ecosystem with standard communication use cases. For organizations that need deep intranet functionality, frontline access for deskless workers, and the security architecture that regulated industries require, the evaluation looks different. ## Who should choose WorkVivo This isn't a close comparison in every dimension — there are specific buyer profiles where WorkVivo is the right answer. Companies already running Zoom for video and messaging will find WorkVivo integrates more tightly with that stack than any third-party alternative. European-headquartered organizations often find WorkVivo's Ireland-based support team well-aligned with their operating hours. For deployments with standard use cases — news feeds, social recognition, video posts — WorkVivo works well out of the box with minimal configuration. Where WorkVivo's fit degrades is when complexity enters the picture: multinational deployments needing multiple nested brands, frontline workforces without corporate email addresses, regulated industries requiring documented security architecture, or communications teams needing audience targeting tied to HRIS data. ## The intranet depth gap WorkVivo's development has concentrated on the communication layer — social feeds, reactions, video posts. The intranet layer — structured content, page hierarchies, governance, lifecycle management — has received less investment, and the product reflects that. TeamHealth consolidated more than 200 previously disparate internal systems into a single MangoApps deployment. That consolidation required an intranet that could carry complex information architecture: department sites, multiple content types, controlled publishing workflows, and a governance layer that keeps content current over time. MangoApps includes an AI-powered content governance engine that automatically manages content lifecycle, flagging and updating stale material without manual intervention. WorkVivo supports page creation for smaller, targeted use cases. MangoApps' [modern intranet](/solutions/modern-intranet) supports unlimited sites and pages, a no-code builder that removes IT from the maintenance loop, and content structure that scales from a 500-person company to a 50,000-person enterprise without architectural changes. For organizations managing the kind of consolidation TeamHealth undertook, the intranet layer isn't a secondary feature — it's the foundation. ## The frontline access question Per Emergence Capital's research, 80% of the global workforce is deskless — shift workers, clinicians, field technicians, retail associates. These employees don't have corporate email addresses, managed laptops, or time to navigate menus between tasks. WorkVivo's design assumptions skew toward desk workers. A mobile experience exists, but it was not built as the primary surface. MangoApps built the [employee app](/solutions/employee-app) as a purpose-built product: personal-device access with no corporate email required, offline mode for field and manufacturing environments, shift scheduling and swap requests from the same interface as company news, and translation for multilingual workforces. OU Health achieved 87% workforce engagement within months of launching a MangoApps-branded app. For a healthcare organization where most staff are deskless clinicians — moving between patient rooms without pausing at a desktop — that adoption rate represents a structural change in how the organization communicates. The cost to replace a single frontline employee runs $4,400–$15,000. Intranet platforms that fail to reach deskless workers are not just a communication gap — they are a retention gap. ## Security architecture for regulated industries Five of MangoApps' primary competitors have added dedicated enterprise security sections to their comparison and product pages over the past 90 days. This is the fastest-moving competitive gap in the intranet category. WorkVivo's published security documentation is thin relative to what enterprise IT departments in regulated industries require. MangoApps supports SAML 2.0, OAuth 2.0, LDAP, and SSO, with data residency options and the audit trail depth that compliance teams need. For financial services, government, and healthcare organizations, the security conversation belongs early in the vendor evaluation — before the demo, not after the shortlist. This matters for the comparison because WorkVivo's acquisition by Zoom subjects its security roadmap to Zoom's enterprise priorities, not a standalone intranet vendor's. MangoApps' security architecture evolves in response to enterprise intranet requirements specifically. ## AI capabilities: named models vs. generic positioning WorkVivo references AI features in its product documentation. MangoApps connects to OpenAI, Google Gemini, Anthropic, and Azure OpenAI — the choice of underlying model stays with the enterprise, not the vendor. This specificity matters because AI governance is becoming an enterprise procurement requirement. Organizations need to know which models their employee data flows through, what the data retention policies are, and which AI capabilities are native versus third-party wrappers. MangoApps' content governance is built on documented model integrations, not an abstracted layer that obscures the underlying provider. For communications teams evaluating how AI-driven content personalization is changing employee experience benchmarks, the question isn't whether a platform "has AI" — it's which models it runs, how data is handled, and whether the enterprise retains control of those decisions. ## What named customers show Comparison articles that rely on feature lists are useful for initial screening. Procurement decisions run on named customer outcomes. Unily — a direct competitor — leads its sales conversations with CVS (90% frontline adoption within the first six months) and British Airways (+30-point engagement score increase). We counter with OU Health (87% workforce engagement, months post-launch), TeamHealth (200+ system consolidation into a single mobile interface), and PetSmart (4x engagement lift). These outcomes appear in deployment contexts that match the buyer profiles where MangoApps outperforms WorkVivo: large enterprises, frontline-heavy workforces, and complex information architecture requirements. Per the [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report), independent analysis covers where MangoApps lands against WorkVivo — and the broader field — on intranet depth, frontline access, and AI capabilities. Third-party analyst assessments are the appropriate venue for neutrally adjudicating these claims; this article reflects our own positioning. ## The three questions every buyer asks after the feature comparison A feature comparison gets buyers to the shortlist. These three questions determine the final decision — and they are the questions this article's original version left unanswered. **What does it cost?** MangoApps is a modular platform, and analysts consistently find it priced at or below WorkVivo for equivalent configurations. WorkVivo's pricing is not publicly published; MangoApps provides tier-based pricing that reflects actual deployment scope. For organizations running a complex deployment — multiple brands, HCM integration, frontline mobile access — the modular structure means paying for what the deployment requires rather than a platform rate that bundles features the organization doesn't use. **How long does implementation take?** Standard MangoApps deployments run 6–12 weeks. Complex enterprise deployments with HCM integrations, custom branding, and multi-site architecture run 3–6 months. MangoApps assigns a dedicated implementation team — not a partner referral — to every deployment. WorkVivo's support model for large enterprise deployments relies on partner mediation, which distributes accountability across the buyer's vendor map and can extend timelines when the implementation partner and the platform vendor have different priorities. **What's the ROI case?** Per IDC's 2.5-hours-per-day figure, productivity recovery from a well-adopted intranet implies $5,000–$12,000 per employee per year in recovered time, at knowledge-worker compensation rates. For frontline-heavy organizations, the retention math is more direct: improving six-month retention by two percentage points on a 1,000-person frontline workforce, at $10,000 average replacement cost, closes the ROI case within the first contract year — before counting communication efficiency or compliance overhead reduction. ## Where the platforms are comparable Both MangoApps and WorkVivo offer strong community space functionality, mobile app support, translation capabilities, and a broad range of integrations. Both platforms emphasize social interaction and engagement within the platform. For organizations whose primary requirement is a social communication layer, both cover the ground adequately. The divergence becomes clear when complexity, frontline scale, or enterprise security enters the evaluation. At that point, the platform whose primary mission is employee experience separates from the one that arrived at employee experience through an acquisition. ## What this comparison means for your decision Per Gallup's [2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), declining employee engagement is a macro trend — and the tools employees use every day are under more scrutiny than they were five years ago. The intranet selection decision isn't purely a technology evaluation anymore. It is an engagement infrastructure decision. WorkVivo is a well-executed communication platform for Zoom-native organizations with standard use cases. The Zoom acquisition did not break it — it clarified what it is: a communication tool for organizations where Zoom is the infrastructure and communication is the primary need. For that buyer profile, it remains a reasonable choice. For the enterprise evaluating against a frontline workforce that is 80% deskless, or a regulated-industry IT team that needs documented security architecture, or a communications team that needs to bring named-customer ROI to a CFO — the evaluation deserves more rigor than a feature list. Per Social Edge Consulting, only 13% of employees use their intranet daily. The gap between a platform employees actually use and one they don't is not a feature gap. It is a mission gap. --- # MangoApps Workplace: The New Communication and Collaboration Solution Tailored for SMBs **Author:** MangoApps **Published:** 2024-07-11 **Category:** press-release Migration services are available for Workplace by Meta customers.  # MangoApps Workplace for SMBs: Intranet, Collaboration, and Security in One Platform Per IDC, employees spend 2.5 hours per day searching for information that should be easy to find. For small and medium-sized businesses, that overhead compounds quickly — and unlike large enterprises with dedicated IT teams, SMBs rarely have the resources to architect integrations between separate chat, file storage, survey, and task management tools. The usual approach is to pick the cheapest tool that covers the most ground and accept the gaps. That calculation changed in 2024 when MangoApps launched MangoApps Workplace — an intranet and [employee communications](/solutions/employee-communications) platform built specifically for SMBs. It consolidates the functions most SMBs piece together with multiple vendors into a single environment, with enterprise-grade security included by default, not priced as a premium add-on. ## Why SMBs are stuck between two bad options The employee intranet and collaboration market broadly divides into two categories that do not serve SMBs well. Enterprise platforms — Unily, Simpplr, and their peers — are engineered for organizations with thousands of employees, dedicated IT departments, and implementation budgets that reflect their complexity. The tools are capable. The deployment timelines, contract sizes, and admin overhead are not sized for a 75-person logistics company or a 200-person healthcare practice. General-purpose chat tools go the other direction. They are fast to deploy and familiar, but they are not intranets. They do not support structured content publishing, employee recognition workflows, or org-wide news feeds with read receipts. SMBs typically wrap them with separate tools for file management, surveys, and task tracking — recreating the point-solution fragmentation they were trying to escape. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in. Only 13% use one daily. Per SWOOP Analytics, the average employee spends just six minutes per day in intranet tools. These numbers do not describe a workforce that lacks willingness — they describe tools built for desktop access that fail the majority of workers who are not sitting at one. Per Emergence Capital, 80% of the global workforce is deskless. An intranet that requires a corporate email login excludes most of those workers before they ever open the app. ## What enterprise-grade security means for an SMB Five major competitors in the SMB intranet market now position secure intranet as a core differentiator, leading with SAML 2.0, OAuth 2.0, and SSO support in their buyer materials. For SMBs in [financial services](/industries/financial), healthcare, and other regulated industries, these are increasingly non-negotiable — organizations face the same compliance scrutiny as large enterprises, with fewer compliance resources to manage it. MangoApps Workplace inherits the same security architecture as the enterprise tier of the MangoApps platform. SAML 2.0, OAuth 2.0, SSO, and role-based permissions are standard across all packages — Basic, Standard, and Pro — not reserved for a premium tier. The audit trail and permission structures that enterprise deployments depend on are present from day one, which matters for SMBs building toward compliance requirements they will face in 18 months, not just meeting current ones. This architecture also applies to AI features. MangoApps connects to OpenAI, Gemini, and Azure OpenAI for AI-assisted search, content generation, and workflow automation. For SMBs evaluating AI-native platforms, the question of data governance — who controls the data, what audit structures exist — is increasingly central to the buying conversation. MangoApps' existing permission model applies to AI features by default. ## The frontline access problem most intranets ignore Access architecture matters as much as the feature set. SMBs with retail associates, healthcare aides, warehouse workers, or field technicians often find that their intranet reaches office staff and misses everyone else. SWOOP Analytics' six-minutes-per-day figure is the outcome of tools built for desktop access deployed across workforces that do not primarily work at desks. MangoApps Workplace supports mobile access without requiring a corporate email address. This is not a workaround — it is the default. For industries where a significant share of the workforce is hourly, shift-based, or field-based, the access model determines whether the platform reaches the full team or only headquarters staff. The adoption data shows what is possible when mobile access is built in from the start. Enterprise deployments of MangoApps have reached 90% frontline adoption within the first six months — a benchmark that reflects what happens when the access barrier is removed rather than routed around. The retention math follows: replacing a disengaged frontline employee costs between $4,400 and $15,000 depending on role and industry. A platform that reaches 40% of the workforce is not solving the retention problem — it is documenting it. ## What MangoApps Workplace includes MangoApps Workplace is organized around four functional areas: **Communication** — Real-time messaging and group channels, personalized news feeds segmented by role or location, and announcements with read receipts. Managers can verify that critical communications reached specific employee groups, not just that the message was sent. **Collaboration** — File sharing and document management with version control, project workspaces that keep tasks, files, and conversations together, and integrations with Microsoft 365 and Google Workspace for teams that are not ready to consolidate everything at once. **Employee engagement** — Recognition tools for peer-to-peer acknowledgments and milestone tracking, interactive polls and surveys for gathering feedback without a separate survey tool, and customizable branding so the environment reflects the company identity rather than a generic vendor interface. **Productivity** — Task management, screen recording for async communication and training, and digital forms that replace paper-based processes. For SMBs managing multi-location operations, these features cover the coordination layer that disappears when communication and task tracking live in separate systems. For SMBs evaluating the all-in-one value proposition, the relevant comparison is not MangoApps Workplace versus a single competitor — it is MangoApps Workplace versus the full set of tools currently filling the same functions. A typical SMB with a separate chat tool, shared drive, survey platform, and task manager is paying for four vendor relationships, four security policies to maintain, and four mobile apps for employees to install and update. The consolidation benefit is concrete: a single identity layer, a single permission model, and a single place where employees look for information instead of cycling through fragmented systems that cost IDC's estimated 2.5 hours per day in search overhead. The platform is also designed to scale. Moving from Basic or Standard to the Enterprise tier does not require a data migration — the underlying architecture is the same. SMBs evaluating MangoApps as a long-term platform are not picking a tool they will need to replace when they reach 500 employees. ## The Workplace by Meta migration window Workplace by Meta's August 2025 shutdown created a clear migration deadline for tens of thousands of organizations. The most common mistake in those evaluations is treating the migration as a data transfer problem. Moving posts and files is the straightforward part. Three areas require deliberate planning: **Audit trails.** Compliance-sensitive SMBs need a preserved record of past communications. How historical content will be indexed and retained should be specified before migration begins, not discovered afterward. **Permission mapping.** Group structures and access controls from Workplace by Meta need to translate explicitly to the new platform before launch day. Organizations that skip this step typically spend the first 30 days post-migration cleaning up access errors that compound into confusion. **Governance continuity.** Content moderation policies, admin roles, and approval workflows should transfer explicitly. These are easy to overlook in a migration focused on content volume and difficult to reconstruct from memory after the transition. MangoApps Workplace's 15-year history as an enterprise social network means the governance and permission architecture is already in place. SMBs migrating from Workplace by Meta are not building audit and governance structures from scratch on a platform that was not designed for them — they are configuring structures that exist and have been tested at scale. ## How to evaluate MangoApps Workplace The self-serve model reflects how MangoApps has positioned the SMB product. As CEO Anup Kejriwal put it: "SMBs shouldn't have to choose between cheap, incomplete tools or expensive, complex enterprise tools just to communicate and collaborate. We are making it easy for teams to start using MangoApps to communicate and collaborate effectively, eliminating the need for multiple apps, all without being forced to speak to anyone to sign up for an account." A 14-day free trial requires no credit card and no sales call. That access model lets evaluation teams test functionality with actual employee groups before a purchasing decision — and makes the internal business case easier to build when evidence comes from the team rather than a vendor demo. Three practical questions worth settling during a trial: **Can your hardest-to-reach employees log in?** Test with mobile access on personal devices, without corporate email credentials. If frontline staff cannot complete a self-serve login, the platform will not reach them at scale regardless of feature depth. **Does the security architecture match your compliance requirements?** Request the SAML and SSO documentation early. For financial services and healthcare SMBs, this question eliminates most alternatives before the feature comparison begins. **What does migration look like on your timeline?** If you are leaving Workplace by Meta, the August 2025 deadline is fixed. A trial that does not include a migration plan conversation is not a complete evaluation. For independent benchmark context on where MangoApps sits in the intranet platform landscape, the [MangoApps 2026 Forrester evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) covers how MangoApps compares against comparable platforms in a structured third-party assessment. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring communication infrastructure this year, including patterns that translate directly to SMB scale. SMBs that have delayed a platform decision waiting for clarity are now at the point where the Workplace by Meta shutdown is actively closing the window. The right question before that window closes is not which platform has the longest feature list — it is which one your entire workforce can actually use starting on day one. --- # MangoApps vs. HCM Platforms: How They Fit Together **Author:** MangoApps **Published:** 2024-07-03 **Category:** comparisons At MangoApps, we often get questions about how our platform fits in with other systems companies use, especially Human Capital Management (HCM) systems. With... ## MangoApps vs. HCM Platforms: How They Fit Together At MangoApps, we often get questions about how our platform fits in with other systems companies use, especially Human Capital Management (HCM) systems. With seemingly overlapping features, it's essential to understand the unique roles these platforms play in your organization. The short answer: HCM systems manage HR data and processes; MangoApps is an [employee engagement software](/solutions/modern-hcm) layer that connects, informs, and activates your workforce — and the two work best when deployed together. ## The Primary Focus and Functionality Human Capital Management (HCM) systems are designed primarily as business solutions focused on managing HR processes and employee data. Their core aim is to streamline HR tasks, making the administrative experience efficient and productive. HCM systems excel in handling employee records, payroll, benefits administration, and compliance. They are built to enhance the productivity of the HR team, ensuring that all HR-related processes run smoothly. In contrast, MangoApps is an Employee Experience Platform centered on enhancing employee engagement and communication across the organization. Our platform offers a comprehensive suite of tools for collaboration, real-time interaction, and productivity, particularly for frontline employees. While administrative efficiency is essential, MangoApps places equal emphasis on the employee experience, fostering a collaborative and inclusive workplace where communication flows effortlessly. The scale of the gap these platforms address is significant. Per IDC, employees spend an average of 2.5 hours per day searching for information — time that neither an HCM self-service portal nor a static intranet is designed to recover. Meanwhile, per Social Edge Consulting, 91% of organizations operate an intranet, yet only 13% of employees use it daily, and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends just six minutes per day in intranet tools. These numbers illustrate why an HCM's employee self-service module alone rarely closes the engagement gap. ## Complementary Roles: HCM vs. Employee Experience Platforms It's important to recognize that HCM systems and Employee Experience Platforms like MangoApps serve different yet complementary roles. Using an HCM system as a replacement for MangoApps, or vice versa, is not advisable because each system is optimized for specific functions. Think of it this way: - **HCM as the system of record, MangoApps as the system of engagement.** An HCM stores the authoritative data about your workforce — headcount, compensation, compliance records. MangoApps surfaces that data in context, delivering the right message to the right employee at the right moment. - **HCM as the back office, MangoApps as the front door.** Payroll runs in the background; employees experience the company through the communications, recognition, and knowledge tools they touch every day. - **HCM for the HR team, MangoApps for every employee.** HCM workflows are optimized for HR administrators. MangoApps is built for the 80% of the global workforce that is deskless, per Emergence Capital — workers who may never open an HR portal but will engage with a mobile-first [employee app](/solutions/employee-app) on their personal device. These distinctions highlight how HCM systems and MangoApps relate to each other. While an HCM system manages HR processes efficiently, MangoApps ensures that employees are engaged, informed, and connected — including frontline workers who can access the platform on personal devices without a corporate email address, VPN, or a desk, removing the access barrier HCM self-service portals typically require. ## How the Two Systems Compare | Capability | HCM System | MangoApps EXP | |---|---|---| | Payroll & benefits administration | ✓ Core function | Not applicable | | Compliance & employee records | ✓ Core function | Not applicable | | Company-wide communications & intranet | Limited / static | ✓ Core function | | Frontline mobile access (no corporate email) | Rarely supported | ✓ Core function | | Real-time collaboration & messaging | Minimal | ✓ Core function | | Employee engagement surveys & questionnaires | Basic | ✓ Purpose-built | | AI-personalized content surfacing | Not available | ✓ Core function | | Training and employee engagement programs | Basic LMS links | ✓ Embedded workflows | | Role-based permissions synced from HRIS | Via HCM | ✓ Synced via SSO/SAML | For a deeper look at how MangoApps is evaluated against other intranet and employee experience platforms, see the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report). ## How to Implement Both Together The most effective deployments treat HCM and MangoApps as a connected stack, not competing choices. Here is a practical four-step approach: **1. Sync employee data from your HCM to MangoApps via API or SSO.** MangoApps supports SAML 2.0, OAuth 2.0, and SSO, with role-based permissions synced directly from your HRIS. When a new hire is provisioned in your HCM, their MangoApps profile, group memberships, and content permissions are created automatically — no duplicate data entry, no governance risk. You can explore how this works through our [employee data management](/solutions/employee-data) capabilities. **2. Use MangoApps for frontline communications while your HCM handles payroll and compliance.** Frontline employees rarely interact with HCM portals. MangoApps delivers shift updates, safety alerts, policy changes, and recognition through a mobile-first interface accessible on personal devices — no VPN required. Your HCM continues to process payroll and track compliance in the background without interruption. **3. Layer employee engagement surveys and training on top of HCM data.** MangoApps enables targeted employee engagement surveys, questionnaires, and employee engagement training programs that can be scoped by department, location, or role — data that lives in your HCM. This means engagement initiatives reach the right cohorts without manual list management. For context on why embedded learning matters, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). **4. Consolidate your tool sprawl.** Organizations that consolidate communications, HR self-service, and operations into one platform have reduced the number of systems IT manages by 3–4x compared to running point solutions alongside an HCM. Traditional intranets and HCM employee self-service modules can take months to deploy and often deliver static, ungoverned content that becomes stale — a gap purpose-built employee experience platforms are designed to close. Most MangoApps customers reach full adoption within 90 days. ## The Business Case: Why the Combination Matters Financially The cost of getting this wrong is concrete. Replacing a single frontline employee costs between $4,400 and $15,000 in recruiting, onboarding, and lost productivity. Poor engagement and disconnected tooling are leading drivers of that turnover. Organizations that have launched a branded employee app on top of their HCM stack have reported 87% workforce engagement within a few months of go-live — a result no HCM self-service module alone has replicated at scale. AI-powered personalization is part of what makes that possible. MangoApps integrates with OpenAI, Gemini, and Anthropic to surface the right content to the right employee without IT intervention — filling the engagement gap that HCM reporting dashboards leave. An HCM tells you *that* engagement is low; MangoApps helps you do something about it in real time. For a broader view of where workforce technology is heading, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading organizations are structuring their HCM and EXP investments together. ## Conclusion: Use Each System for What It Does Best HCM systems and Employee Experience Platforms are not competitors — they are complements with clearly defined lanes. Your HCM is the authoritative system of record for HR data, payroll, and compliance. MangoApps is the engagement and communication layer that makes that data actionable for every employee, including the frontline workers your HCM portal was never designed to reach. The practical path forward is straightforward: keep your HCM for what it does best, connect it to MangoApps via API or SSO, and use MangoApps as the unified intranet and employee app your workforce actually opens every day. Organizations that make this pairing work reduce tool sprawl, improve retention, and close the engagement gap that neither system can close alone. To see how this plays out in practice, review [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) or explore our [workforce management solutions](/solutions/workforce-management) to understand how the full platform connects to your existing HR stack. ## Frequently Asked Questions ### Will adding MangoApps create security or compliance risk alongside our HCM? No. MangoApps is built to enterprise security standards — SAML 2.0, OAuth 2.0, SSO, and role-based permissions synced from your HRIS. When an employee's role or status changes in your HCM, access rights in MangoApps update automatically. This means IT does not manage a separate permission layer, and your governance posture stays intact. The [employee directory](/key-features/employee-directory) is always current because it draws from the same source of truth as your HCM. ### How long does it take to deploy MangoApps alongside an existing HCM? Most customers reach full adoption within 90 days. This contrasts with traditional intranet or HCM portal customization projects, which routinely take six to twelve months and still deliver static content that becomes outdated. The integration with common HCM platforms is handled through standard API connectors and SSO, so IT effort is concentrated at the start rather than ongoing. ### What if our HCM already includes an employee engagement survey module? HCM engagement modules are typically annual or semi-annual pulse tools tied to the HR workflow. MangoApps supports continuous employee engagement surveys, targeted questionnaires, and employee engagement training programs that can be triggered by events — a new manager, a policy change, a safety incident — rather than a calendar. The two can coexist: use your HCM module for formal annual reviews and MangoApps for the real-time feedback loop that drives day-to-day engagement. For trends shaping how organizations approach this, see the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook). --- # Buyer's Guide to 2024's Best Intranet Platforms **Author:** MangoApps **Published:** 2024-06-12 **Category:** comparisons At MangoApps, you could say we know a thing or two about intranets - we’ve been deploying them to customers in a wide variety of industries for over a decade... # Buyer's Guide to 2024's Best Intranet Platforms If you're evaluating intranet platforms, here is the short answer: the top five platforms consistently cited across independent analyst reports are **MangoApps, Unily, Simpplr, LumApps, and Interact**. The sections below explain what each does well, where each falls short, and what capabilities matter most when making this decision. According to Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in, and only 13% use one daily. Meanwhile, employees spend an average of 2.5 hours per day searching for information (per IDC). The gap between having an intranet and having one that works is wide, and choosing the right platform is how you close it. --- ## Top 5 Intranet Platforms These five platforms are the most consistently cited top performers across industry reports, independent reviews, and analyst evaluations such as the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report). ### 1. MangoApps MangoApps is a unified employee experience platform that combines intranet, communications, learning, and task management in a single environment. It is designed to serve both desk-based employees and frontline workers — a distinction that matters because 80% of the global workforce is deskless (per Emergence Capital), yet most intranet tools are built exclusively for office workers. Organizations using MangoApps have consolidated 200+ disparate systems into a single mobile intranet dashboard, eliminating redundant tooling and IT overhead (per MangoApps product page / TeamHealth case study). One enterprise reported $20M in cost avoidance after deploying the platform. Frontline employees can achieve 90% platform adoption within the first six months when the intranet is purpose-built for their workflows rather than adapted from a desk-worker tool (per Unily product page / CVS case study). MangoApps integrates with OpenAI, Gemini, Anthropic, and Azure OpenAI to power AI-curated feeds, natural-language search, and automated content governance — specific capabilities that go beyond generic "AI features" claims. Its universal search spans SharePoint, Google Drive, Box, and Dropbox, which means MangoApps can coexist with SharePoint rather than simply replace it. For organizations already invested in Microsoft 365, this is a meaningful distinction. Companies including PetSmart and AutoZone use MangoApps to equip both desk and frontline employees. You can explore the [solutions/modern-intranet](/solutions/modern-intranet) page for a detailed feature breakdown, or review the [key-features/company-portal](/key-features/company-portal) to see how the platform structures information access. **Strengths:** Unified platform for desk and frontline workers; AI integrations with named engines; universal search across third-party storage; strong mobile experience; transparent pricing. **Weaknesses:** Breadth of features can require a structured rollout plan; organizations with very narrow use cases may not need the full platform. --- ### 2. Unily Unily is a cloud-native intranet and internal communications platform built exclusively for large enterprises with more than 10,000 employees. It is recognized for strong automation and reporting capabilities, particularly for internal communications teams. **Strengths:** Good automation workflows; strong insights and analytics for communicators; enterprise-grade infrastructure. **Weaknesses:** Pricing is not transparent — costs depend on modules selected and must be scoped through a sales process. The platform relies heavily on third-party tools for frontline collaboration and coordination, which can create gaps for organizations with large deskless workforces. --- ### 3. Simpplr Simpplr is well-regarded for AI-assisted content governance and personalization features, making it a strong fit for desk-worker communications teams. **Strengths:** AI-driven content governance; rich personalization; solid integration library; strong reporting tools. **Weaknesses:** Lacks native collaboration tools for team-based work. Pricing and licensing are not publicly disclosed. Users have reported poor search functionality. The platform can struggle with complex site architectures at enterprise scale. --- ### 4. LumApps LumApps was originally built for Google Workspace customers and has since expanded Microsoft 365 integration. It offers strong reporting, analytics, and video support. **Strengths:** Strong analytics and reporting; good video support; ambitious product roadmap; solid Google Workspace integration. **Weaknesses:** Complex pricing can escalate costs quickly. Microsoft 365 integration still lags behind native Microsoft tools in some workflows. Because the product suite was assembled through acquisitions, components do not always integrate smoothly. Customers have cited gaps in survey capabilities and AI features. --- ### 5. Interact Interact is a strong option for organizations with significant frontline populations, particularly those that need digital signage and SMS communication channels. **Strengths:** Rich content authoring tools; metadata support; strong search; digital signage and SMS support; professional services team. **Weaknesses:** Administrative interface is complex and has received poor usability reviews. Reporting functionality is limited. The platform is still building out enterprise features such as complex employee journey mapping. Integration library is smaller than competitors. --- ## Honorable Mentions These platforms have genuine strengths in specific use cases but have not demonstrated the same consistent leadership across analyst reports and independent reviews. ### Staffbase Strong internal communications features and intuitive content authoring, particularly for frontline-facing messaging. Limited core intranet functionality — content governance and file management are not strengths. No significant vertical-specific strategy. ### Workvivo (acquired by Zoom) Benefits from Zoom's investment in video and AI. Strong native collaboration tools and employee survey capabilities. Customers have reported weak workflow automation and inconsistent support. Organizations already using Microsoft 365 should evaluate potential bundling conflicts carefully. ### Firstup Focused on intelligent content delivery and calendaring. Smooth implementation process and a developed partner ecosystem. Lacks comprehensive document and media management. Still catching up to competitors on core intranet functionality. ### Igloo Solid content governance and branding capabilities. Strong track record of customer service. Limited mobile functionality, a smaller partner ecosystem, and limited support for complex security requirements such as data sovereignty. --- ## Most Important Capabilities When Evaluating an Intranet An **intranet** is a private, internal network that gives employees a central place to access company information, communicate, and collaborate. The definition of intranets has expanded significantly — today's platforms go well beyond static page repositories to include AI-curated feeds, mobile apps, and integrations with dozens of enterprise tools. When evaluating platforms, prioritize these capabilities: 1. **Frontline and Mobile Access** — 80% of the global workforce is deskless (per Emergence Capital). An intranet that works only on a desktop is not an intranet for most of your employees. Evaluate whether the mobile app provides full feature parity or a stripped-down experience. The [solutions/employee-app](/solutions/employee-app) page shows what full mobile parity looks like in practice. 2. **Communication Tools** — Look for platforms that support both formal channels (news feeds, announcements) and informal ones (forums, messaging). SWOOP Analytics reports that employees spend an average of only six minutes per day using intranet tools — a signal that most intranets fail to become a daily habit. 3. **AI-Native Features** — Generic "AI features" claims are common. Ask vendors specifically which AI engines they use, whether they support natural-language search, and how content governance automation works. Vague answers are a red flag. 4. **Integration Depth** — The ability to integrate with Microsoft 365, Google Workspace, Slack, and file storage systems (SharePoint, Google Drive, Box, Dropbox) is essential. Equally important is whether the platform offers universal search across those systems, so employees find information regardless of where it lives. The [key-features/workspaces](/key-features/workspaces) feature demonstrates how integrated team environments can be structured. 5. **Content Management and Governance** — Outdated content is one of the primary reasons employees stop trusting and using an intranet. Automated governance tools that flag stale pages and prompt owners to review are a meaningful differentiator. 6. **Analytics and Reporting** — You cannot improve what you cannot measure. Look for platforms that report on content engagement, search queries that return no results, and department-level adoption rates. 7. **Security and Compliance** — Confirm that the platform meets your industry's regulatory requirements, supports data sovereignty if needed, and provides role-based access controls. 8. **Total Cost of Ownership** — Licensing is only part of the cost. SharePoint's first-year total cost for a 1,000-user enterprise ranges from $130,000 to $426,000 when implementation, customization, and governance are included — not just licensing (per MangoApps SharePoint alternatives blog / Awesome Technologies Inc. 2025 cost model). Any platform comparison should include implementation, training, and ongoing administration costs, not just per-seat pricing. --- ## Why SharePoint Alone Is Not Enough SharePoint is the most widely deployed intranet foundation in the world, but deployment does not equal adoption. The average employee spends only six minutes per day using intranet tools (per SWOOP Analytics), and nearly a third never log in at all (per Social Edge Consulting). SharePoint's first-year TCO for a 1,000-user organization can reach $426,000 when implementation, customization, and governance overhead are factored in (per MangoApps SharePoint alternatives blog / Awesome Technologies Inc. 2025 cost model). The more productive framing is not "replace SharePoint" but "make SharePoint actually work." Platforms like MangoApps layer universal search, AI-curated feeds, and a mobile-first experience on top of existing SharePoint content — so organizations preserve their document investments while giving employees a usable front door. Replacing a single frontline employee costs between $4,400 and $15,000 (per MangoApps mobile app product page / industry report). Poor intranet adoption that drives disengagement is not a technology problem in isolation — it is a retention and financial risk. --- ## Frequently Asked Questions ### What is the difference between an intranet and an employee experience platform? An intranet, by definition, is a private internal network for accessing company information. An employee experience platform extends that definition to include communications, learning, task management, and integrations with HR systems — essentially, everything an employee needs to do their job, in one place. The distinction matters when evaluating vendors: some products are intranets with communication features bolted on, while others are built as unified platforms from the ground up. ### How do I evaluate intranet platforms for frontline workers specifically? Ask three questions: Does the mobile app offer full feature parity with the desktop version? Does the platform support SMS or push notifications for employees without corporate email addresses? And does the vendor have documented case studies with frontline-heavy organizations (retail, healthcare, logistics, manufacturing)? A 30-point increase in employee engagement was reported by a major airline after intranet modernization — outcomes like that are achievable, but only with a platform designed for the workforce that actually needs it. ### How long does an intranet implementation typically take? Implementation timelines vary by platform complexity and organizational readiness. Simple deployments for smaller organizations can go live in 4–8 weeks. Enterprise deployments with custom integrations, content migration, and governance frameworks typically run 3–6 months. Ask vendors for a detailed implementation plan and references from organizations of similar size and complexity before signing. --- ## Next Steps The five platforms above — MangoApps, Unily, Simpplr, LumApps, and Interact — represent the most consistently evaluated options in the market. The right choice depends on your workforce composition (desk vs. frontline), your existing technology stack, your budget for total cost of ownership, and how much AI-native functionality you need today versus in 12–18 months. A practical next step: request demos from at least three vendors, bring a list of your top 10 use cases, and ask each vendor to walk through those use cases specifically rather than a generic product tour. Review independent analyst reports alongside vendor materials. The [MangoApps Included in Leading Research Firm's Intranet Platforms Ev...](/articles/mangoapps-2026-forrester-wave-intranet-platforms) article provides one example of how MangoApps has been evaluated by third-party researchers. If you want to go deeper on internal communications planning as part of your intranet rollout, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the trends shaping how organizations are structuring their communications strategies this year. --- # MangoApps: The Best Workplace by Facebook Replacement **Author:** MangoApps **Published:** 2024-06-04 **Category:** comparisons As many organizations know, Workplace By Facebook is scheduled to shut down next year. For those currently relying on Workplace for communication and collabo... # MangoApps: The Best Workplace by Facebook Replacement Per IDC, the average employee spends 2.5 hours every workday searching for information they need to do their job. Workplace by Facebook didn't solve that problem — it added a social feed on top of it. Now that Workplace is shutting down on a fixed schedule, organizations face a choice that goes beyond finding something with a similar feature set: replicate what Workplace did, or fix what it never managed to get right. Most replacement options are built around the same assumption Workplace was — that every employee has a corporate email address, sits near a desk, and accesses work tools from a managed device. That assumption excludes 80% of the global workforce, per Emergence Capital: the frontline workers in healthcare, logistics, retail, and manufacturing who carry the most customer-facing responsibility and receive the least investment in communication infrastructure. MangoApps is the Workplace by Facebook replacement built around the employees that platform never reached. It closes the gaps in frontline access, enterprise security, AI-governed content delivery, and migration outcomes that define whether a replacement actually works — or simply delays the next forced migration by a few years. ## The workers Workplace by Facebook never reached Workplace by Facebook was built on the assumption that everyone logging in had a company-issued email address. That design choice excluded the majority of employees in most industries before the first message was sent. Per Emergence Capital, 80% of the global workforce is deskless. Healthcare technicians, warehouse associates, retail floor staff, field service engineers — workers who own the front end of the customer relationship and who, in most organizations, still receive communications through physical bulletin boards, group SMS threads, or shift-start briefings. Information reaches them slowly, inconsistently, and without any audit trail. MangoApps eliminates the email-address requirement at the infrastructure level. Frontline employees can access the platform through the [employee app](/solutions/employee-app) on a personal iOS or Android device — no VPN, no corporate credential, no IT provisioning ticket required. A single invitation link, a personal phone, and they're inside the collaboration environment the same day. For manufacturing, logistics, and healthcare organizations, this is the operational difference between a communication platform and a communication strategy that reaches everyone on payroll. The adoption data from comparable deployments is concrete. OU Health achieved 87% workforce engagement within a few months of launching a mobile-first employee app, per MangoApps deployment data. By comparison, per Social Edge Consulting, only 13% of employees use a conventional intranet daily, and nearly a third never log in at all. That gap is an access gap, not an engagement gap — and it is closed by removing the credential requirement, not by improving the interface. ## What migration from Workplace actually looks like The standard concern about any platform migration is timeline. A six-month implementation that disrupts productivity while the platform team works through configuration is the scenario every internal communications leader wants to avoid. Here is what a MangoApps migration from Workplace by Facebook involves in practice. A typical enterprise migration runs in three sequential phases. The first phase, covering weeks one through four, handles data and content migration: groups, posts, files, and user accounts transfer through tooling MangoApps provides specifically for Workplace migrations. The second phase, spanning weeks three through eight, covers system integration: HRIS sync, SSO configuration, and connections to document repositories including SharePoint and Google Drive are set up during this window — not retrofitted after launch. The third phase, weeks six through twelve, is phased rollout with adoption support, beginning with the populations most dependent on the platform and extending to frontline workers through [employee communications](/solutions/employee-communications) channels that bypass the email-address barrier. The sequencing matters. Migrations that onboard corporate knowledge workers first and frontline populations last consistently produce adoption numbers that reflect only the first group. The OU Health 87% engagement figure reflects a rollout that prioritized frontline access from the start. For organizations in regulated industries — financial services, ambulatory care, healthcare — compliance architecture and role-based permissions are configured during the integration phase, before any content goes live. MangoApps holds SOC 2 certification with SAML 2.0 and OAuth 2.0 support, and offers data residency options for organizations operating under GDPR, HIPAA, or sector-specific data handling requirements. These are part of the standard enterprise configuration, not premium add-ons. An independent evaluation of MangoApps' security architecture, content management capabilities, and platform maturity is available in the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report), which evaluates the platform against leading competitors across the specific dimensions relevant to a Workplace migration decision. ## Why enterprise security is the question this migration has to answer Workplace by Facebook was built by a company whose core business is advertising. Enterprise-grade security was a capability the platform acquired over time, not one it was designed around from the start. That origin matters when the platform holds internal communications, personnel data, and compliance-sensitive documents. MangoApps was designed as an enterprise collaboration platform from the beginning. SAML 2.0 and OAuth 2.0 are standard. SOC 2 certification is current. Data residency options are available for organizations with geographic data requirements. IT teams evaluating post-Workplace options consistently find that the compliance conversation with MangoApps is shorter — the requirements are already met and documentable, rather than negotiated through procurement. Five of MangoApps' primary competitors now lead with enterprise security credentials in their positioning. That reflects where enterprise IT evaluation has shifted. A Workplace replacement that cannot answer the security question with specifics will not clear the IT review stage, regardless of how familiar the user interface looks to employees coming from Facebook's social model. MangoApps was recently included in [a leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms), an independent validation that covers enterprise security alongside intranet capabilities and employee experience features. ## AI that governs content, not just surfaces it Per SWOOP Analytics, the average employee spends six minutes per day using intranet tools. The reason isn't that employees don't want information — it's that conventional intranets deliver undifferentiated content that makes a browser search or a Slack message faster than logging in and navigating. When a platform shows a warehouse associate in Phoenix the same news feed as a VP in headquarters, neither finds it useful. MangoApps addresses this with AI-curated feeds that surface content relevant to each employee's role, location, and recent activity. Universal search extends across connected repositories — SharePoint, Google Drive, and other document stores — so a search inside MangoApps returns results from every connected system, not only the content explicitly posted to the platform. Multi-engine AI support spanning OpenAI, Gemini, and Azure means the AI infrastructure can be configured to match an organization's existing enterprise agreements rather than creating a new vendor dependency. The IDC benchmark of 2.5 hours lost per employee per day to information search translates directly to headcount at scale. A 500-person organization loses the equivalent of roughly twelve full-time employees every workday to retrieval overhead. AI-governed content delivery is what changes that number — not by adding more content, but by making the right content findable without effort. ## WorkVivo is not a neutral choice When Workplace by Facebook announced its shutdown, Meta named WorkVivo as its preferred migration partner. Organizations evaluating that path should understand the structural risk they're accepting. WorkVivo is a product Zoom acquired. Zoom's core business is video conferencing. The risk of anchoring long-term internal communications infrastructure on a platform that is an acquisition by a company focused elsewhere is precisely the risk forcing this migration in the first place: a vendor whose strategic priorities shifted, leaving customers with a fixed migration deadline and no good options. MangoApps has been building enterprise collaboration software and nothing else for nearly fifteen years. Enterprise collaboration is not a division or an acquisition — it is the entire business. MangoApps is operationally profitable and not dependent on external investment cycles. That organizational stability is worth weighing explicitly when selecting a platform intended to outlast the next product sunset announcement. ## The ROI case for replacing Workplace with something better Three ROI dimensions have the clearest supporting data for organizations evaluating this decision. **Information recovery.** The IDC benchmark of 2.5 hours per day spent searching for information is recovered at the margin through AI-surfaced content and unified search. Per SWOOP Analytics, employees average six minutes of daily intranet use on conventional platforms — a figure that rises to 87%+ engagement per MangoApps deployment data when the platform is mobile-first and credential-free. **Frontline retention.** Replacing a single frontline employee costs between $4,400 and $15,000, per MangoApps frontline workforce analysis. Platforms that reach frontline workers reliably — communicating role changes, safety updates, and scheduling information when it matters — measurably reduce the churn that drives that cost. A single enterprise documented $20M in cost avoidance after deploying a modern employee experience platform, per Unily/Wipro case study data. **Migration economics.** Unlike Workplace's flat per-seat bundle, MangoApps' modular pricing allows organizations to activate intranet, employee app, communications, forms, and workflows as needed — scaling capability over time rather than purchasing the full platform at the outset. ## The migration decision has a fixed deadline Workplace by Facebook is shutting down. The question is not whether to migrate, but which replacement closes the gaps Workplace left open: reaching frontline workers who never had corporate email addresses, delivering content through an AI layer that matches relevance to role and location, passing the security and compliance review that enterprise IT requires, and doing so through a vendor whose organizational stability means this is the last forced migration, not the next one. The 87% adoption outcomes, SOC 2 certification, no-email frontline access model, and independent analyst recognition are verifiable claims — the benchmarks a migration decision should be made against before the deadline makes one unavoidable anyway. --- # MangoApps Launches Centralized Task Management Capabilities for Frontline Workers **Author:** MangoApps **Published:** 2024-05-09 **Category:** press-release New features ensure unified execution and operational consistency on a large scale, no matter where workers are located. **ISSAQUAH, Wash., May 9, 2024** — MangoApps, a leader in integrated employee experience platform solutions, today announced the launch of its advanced frontline task management features, designed to unify both office and frontline teams across diverse industries. Per Emergence Capital, 80% of the global workforce is deskless — yet most enterprise software is still built for the desk. This release directly addresses that gap by bringing centralized, AI-governed task deployment to the workers who need it most. Building on top of existing comprehensive task management capabilities, MangoApps now offers a unified experience for office and frontline workers that streamlines workflows and enhances communication to dramatically improve sop operations on the frontline. This new capability allows enterprises to deploy tasks in bulk to hundreds or even thousands of locations simultaneously, ensuring consistent execution and operational efficiency at a global scale. Organizations managing distributed locations can now treat task deployment the way they treat operations manual governance — standardized, auditable, and scalable without IT involvement. "Our enhanced task management capabilities signify a major leap in operational efficiency and employee coordination from staff in the office to workers on the frontline," said Anup Kejriwal, CEO and co-founder of MangoApps. "We are excited to provide a solution that not only simplifies the management of complex tasks but also integrates it with communication, training, and management into a single experience, thereby fostering a more connected and efficient workplace." New Frontline Task Management features include: - **Centralized Task Deployment:** Deploy tasks to multiple locations at once to ensure uniformity and compliance. This is particularly relevant for industries such as retail, healthcare, and BPO, where consistent execution of operations instructions across dozens or hundreds of sites is a daily requirement. - **Customizable Workflows with AI-Verified Execution:** Adapt workflows to meet specific organizational needs and automatically verify task completion using AI, enhancing reliability and reducing errors. MangoApps' AI layer — supporting OpenAI, Gemini, Anthropic, and Azure — functions as a governed, enterprise-safe execution engine, not merely a feature add-on. No-code workflow automation handles shift swapping, PTO requests, task assignments, and routine approvals without IT involvement, a capability that previously required dedicated engineering resources. - **Role-Specific Dashboards:** Tailored, real-time task views for different management levels, enhancing decision-making and oversight. The manager employee experience is a distinct design target here: supervisors see location-level completion rates; executives see cross-site compliance trends. - **Intelligent Task Management:** Automated assignment of corrective tasks and training modules based on performance analytics. When a location misses a compliance step, the system can automatically route the relevant [learning and development content embedded in daily work](/articles/learning-and-development-strategy-embedded-in-daily-work) to the responsible team — closing the loop without manual escalation. This update is part of MangoApps' mission to provide a unified employee experience platform that integrates teamwork management into the overall employee experience. The release aims to make managing daily store and frontline operations more intuitive and effective, enabling organizations to achieve higher productivity and better align their workforce with strategic goals. Enterprises consolidating onto a unified platform have captured up to $20M in cost avoidance, and organizations pairing mobile-first deployment with role-targeted content have reached 90% adoption within the first six months — a benchmark set by large pharmacy and retail deployments (per Unily CVS case study data). MangoApps is trusted by hundreds of mid-to-large enterprises worldwide to modernize communication, training, and operational systems. The platform currently serves more than 1 million users and maintains a 98% customer retention rate. See how one grocery retailer connected 20,000 employees across locations in the [Raley's Companies' success story with MangoApps](/resources/raleys-case-study). For more information about MangoApps and to learn more about how the new task management capabilities can transform your operations, visit mangoapps.com. **About MangoApps** At MangoApps, our goal is a world where all employees, whether office-based or frontline, are engaged, efficient, and fulfilled. Our unified modern intranet and employee app platform is the all-in-one solution that redefines the work experience by providing consistency and rich engagement for employees no matter where they are. With a 15-year history, MangoApps is trusted by companies all over the world. Rethink the employee experience at www.mangoapps.com. --- ## Who Benefits Most: Industries and Use Cases Frontline task management at scale is not a single-industry problem. The features in this release map directly to operational patterns in several sectors: - **Retail and grocery:** Store managers need to push planogram updates, compliance checklists, and promotional execution tasks to every location simultaneously. The [Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) outlines how scheduling and task coordination intersect at the store level. - **Healthcare and ambulatory care:** Clinical and administrative staff require role-specific task views and audit trails for regulatory compliance. MangoApps' [ambulatory care workforce management capabilities](/solutions/workforce-management) address the specific coordination needs of distributed care teams. - **BPO and distributed services:** High-turnover environments benefit from automated onboarding task sequences and AI-verified completion. Organizations in this sector can explore how MangoApps supports [BPO workforce operations](/industries/bpo) at scale. - **Multilingual and global workforces:** Distributed teams operating across languages require task content that travels with translation. MangoApps supports multilingual deployment across its platform; organizations with global frontline populations should contact their account team to confirm current language coverage for task modules. Per IDC, employees spend an average of 2.5 hours per day searching for information. Centralizing task deployment, operations instructions, and corrective workflows in a single employee experience platform directly reduces that drag — particularly for frontline workers who lack reliable desktop access. ## How to Get Started with Frontline Task Management These capabilities are available to MangoApps enterprise customers as part of the platform's [workforce management solution](/solutions/workforce-management). Organizations evaluating the release should consider the following steps: 1. **Audit your current task distribution method.** If tasks are being communicated via email, paper, or disconnected apps, the consolidation opportunity is immediate. 2. **Identify your highest-volume locations.** Bulk deployment is most impactful where manual operations currently require repeated, location-by-location effort. 3. **Map role-specific dashboard needs.** Determine which management levels need real-time visibility and what metrics matter at each tier. 4. **Pilot with AI-verified workflows.** Start with one repeatable compliance checklist — a daily opening procedure or a safety audit — and use AI verification to establish a baseline completion rate before expanding. 5. **Connect task completion to training.** Use the Intelligent Task Management feature to automatically route corrective learning when a task is missed, turning every gap into a development moment rather than a manual follow-up. Organizations that have replaced paper-based processes with mobile-accessible training and digitized workflows have reported 50% faster new-hire onboarding. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides additional benchmarks for organizations planning a frontline operations modernization. ## Frequently Asked Questions **When are these features available?** The frontline task management capabilities announced on May 9, 2024 are available to MangoApps enterprise customers. Existing customers should contact their customer success manager for enablement timelines specific to their deployment. New customers can request a demo at mangoapps.com. **How does MangoApps differentiate from point-solution task tools?** Point solutions manage tasks in isolation. MangoApps connects task execution to communication, training, scheduling, and analytics within a single employee experience platform. Per Social Edge Consulting, 91% of organizations operate an intranet, but only 13% of employees use it daily — and nearly a third never log in at all. A platform that surfaces tasks, training, and communications in one mobile-accessible destination addresses the adoption gap that standalone tools cannot. Per SWOOP Analytics, employees spend an average of just six minutes per day in intranet tools — a figure that rises when task-relevant content is surfaced contextually rather than buried in navigation. **What does implementation look like for a large enterprise?** MangoApps supports bulk deployment to thousands of locations from a single administrative interface. No-code workflow configuration means operations teams — not IT — can build and modify task sequences. For organizations managing shift-based workforces, the platform's [shifts and schedules solution](/solutions/shifts-schedules) integrates directly with task assignment, so the right tasks reach the right workers at the right time in their shift. --- # Build Stronger Customer Connections With Advocacy Tools **Author:** MangoApps **Published:** 2024-05-03 **Category:** online-community-software In the dynamic landscape of customer engagement, fostering advocacy has become a pivotal goal for businesses seeking to strengthen their brand. To reach this... # Build Stronger Customer Connections With Advocacy Tools Six months after Meridian Software launched its customer advocacy program, the participation numbers looked encouraging. Two hundred customers had joined the community. Forty-three had completed onboarding and posted introductions. Eight had already submitted product reviews. What community manager Priya Okonkwo could not tell her VP of Marketing was which of those 200 were still active — and which had opened the invitation email, joined once, and never returned. She had an enrollment rate. She did not have a program. That gap between enrollment and sustained advocacy is where most programs stall. Not because the customers are unsatisfied, but because the infrastructure treats participation as binary: you joined, or you didn't. What it cannot surface is the deterioration that happens between join date and the moment a customer becomes — or stops being — a reliable referral source. The companies that build durable advocacy programs do not have more enthusiastic customers. They have better visibility into which customers are engaging, what content is resonating, and where drop-off happens before it compounds into churn. That visibility requires analytics built into the community platform itself — not extracted to a spreadsheet after the fact. ## The analytics gap competitors exploit Customer community platforms frequently market engagement metrics, but program managers encounter a consistent frustration: the data exists, but accessing it requires data team involvement, custom query construction, or manual exports that arrive too late to act on. 81% of leading companies say they effectively use data and analytics tools to guide strategic decisions, per McKinsey research — yet the same research identifies analytics access, not data collection, as the constraining factor. The data is logged. The reporting that makes it actionable for a program manager during a weekly review meeting is not built in. This is the gap competitors have oriented their positioning around: not more engagement, but measurable engagement. Open rates, participation trends, and sentiment signals surfaced in an admin interface rather than buried in an event log. For advocacy programs, this distinction determines whether a program manager can course-correct within a campaign or only in retrospect. Highly engaged workplaces see 23% higher productivity and 78% less absenteeism, per Gallup research at gallup.com. The underlying mechanism — people who feel heard and recognized behave differently from those who don't — operates identically in customer communities. The measurement challenge is the same: you cannot build on engagement you cannot see. For a broader look at how these dynamics play out across organizational contexts, [Gallup's 2026 State of the Global Workplace: What It Means for HR, IT, and Operations Leaders](/articles/gallup-2026-state-of-the-global-workplace) covers the research in detail. ## What "measurement" actually requires Before program managers can measure advocacy, they need clarity on what they are measuring. Three metrics determine whether an advocacy program is producing compounding returns or flatline participation. **Participation rate** — what percentage of enrolled advocates contributed content, responded to a prompt, or interacted with another member in the past 30 days. Enrollment rate is a vanity metric; participation rate is the signal. **Content reach** — how many unique community members encountered advocate-generated content. A program with 50 active advocates producing content that no one reads generates no referral value. Reach determines whether advocacy is amplifying or self-contained. **Referral conversion** — how many new customers cite advocate recommendations at the point of signup or purchase. This metric typically requires CRM integration, but the community platform should be surfacing the first two before this question becomes relevant. Priya's program had data on enrollment — she could see that 43 customers had completed onboarding. What she lacked was ongoing visibility into participation rate and content reach without pulling manual reports. The 85% daily active user rate achieved post-launch in a 5,900-employee global community deployment, per the Cosentino case study via Staffbase, was not a product of more engaged participants. It was a product of admin reporting that let the program team identify drop-off patterns and intervene before they became churn. ## Three structural requirements of a measurable advocacy program Getting from enrollment numbers to program health data requires three infrastructure requirements to be in place before advocates receive their first invitation. ### Community spaces configured for participation, not just presence An advocacy community that functions as a bulletin board — where the company posts and customers read — produces no network-level advocacy. The spaces need to be configured to encourage peer-to-peer interaction: product-specific sub-communities, prompts that surface user expertise, and mechanisms that make member contributions visible to other members rather than only to administrators. 89% of frontline workers say they would stay with their organization if leaders listened to their feedback, per McKinsey research. The mechanism translates directly to customer communities: members who see that their contributions influence product decisions or community direction stay active. Members who post into a void do not. Platform configuration determines which experience customers have. Peer-to-peer recognition embedded in the community platform drives 36% more engagement than recognition that flows only from the company, per research cited in MangoApps' employee recognition documentation. For advocacy programs, this means recognition should happen in the same space where advocates already spend time — not routed through a separate portal that requires additional navigation. ### Communication precision that scales without noise The most reliable way to reduce engagement in an advocacy program is to send every member the same message regardless of participation level, product focus, or geography. As the community scales, generic communications become background noise — and advocates who stop opening messages stop referring. Targeted communication to segmented groups — advocates in specific product lines, regional markets, or engagement tiers — allows program managers to calibrate content relevance as the community grows. Acknowledgment tracking confirms which members have seen key announcements, enabling follow-up for those who have not. In regulated industries, this is a compliance feature; in advocacy programs, it is a trust-building feature. Advocates who receive verified, policy-aligned communications are more confident champions. A 40% boost in engagement has been linked to improved internal communication practices, per research from ioic.org.uk. The discipline that produces that outcome — timely, segmented, confirmed-received — applies directly to how advocacy programs sustain participation over time. ### Sentiment signals without constant surveying Survey fatigue is real in advocacy communities. Members who are asked for structured feedback every six weeks begin to treat the program as a research relationship rather than a community. The alternative is sentiment analysis surfaced from in-app interactions — comment tone, response rates to specific content types, participation patterns around product announcements — that gives program managers a real-time read on community health without requiring explicit surveys. A drop in community sentiment can be detected and addressed before it affects advocacy output. A spike in sentiment around a specific product update can be amplified before the moment passes. That timing — acting on a signal when it is current rather than after a survey cycle closes — is what separates programs that capitalize on customer enthusiasm from programs that reconstruct it after the fact. ## What enterprise programs require beyond participation mechanics For organizations managing advocacy communities across multiple countries and languages, the infrastructure requirements extend beyond what single-market programs need. Global advocacy programs typically encounter two failure modes at scale. The first is the regional instance problem: separate community platforms for separate markets, each requiring its own administration, configuration, and reporting — with no unified view of which markets are producing the highest-quality advocates. The second is the language barrier problem: content and communications delivered in the primary market language with manual translation workflows that introduce lag and inconsistency. Supporting deployments across 50+ countries eliminates the coordination overhead of managing separate regional instances. Organizations in retail, hospitality, and business process outsourcing — where the most distributed advocacy communities typically operate — benefit from unified reporting across a global deployment rather than market-by-market reconciliation. For teams considering how community management fits into a broader [employee engagement](/solutions/employee-engagement) strategy, the same analytics and communication capabilities that serve internal engagement programs apply directly to external community management. ## Sequencing a measurable advocacy launch Program outcomes are largely determined before advocates receive their first invitation. Organizations that skip the pre-launch configuration phase — standing up community spaces, activating recognition mechanics, and configuring analytics reporting — consistently see lower participation rates in the first 90 days than programs that complete configuration before opening enrollment. The sequence that produces consistent results: **First 30 days:** Configure community spaces for relevant segments, activate peer recognition, set analytics reporting to track participation rate and content reach, and run a soft rollout with a pilot group of 30–50 advocates. Feedback from 50 advocates is actionable; feedback from 5,000 requires triage. **Days 30–60:** Review participation rate data for the pilot group. Identify which segments are most active, which content types generate peer engagement, and where drop-off is occurring. Use that data to configure communications for the full launch — segmented by product focus and participation tier. **Days 60–90:** Open enrollment to the full advocate group with communications calibrated to the pilot data. Onboarding advocates into a configured, populated environment — one with active peer recognition and relevant community content already in place — produces higher completion rates than launching into a blank platform. A high participation rate with low referral conversion at 90 days means the program is building community but not equipping advocates with shareable content. A low participation rate with high referral conversion means a small group of highly motivated advocates without a system to scale their reach. Both are diagnostic signals, not failure states — and both are visible in real-time analytics rather than reconstructed from export data. ## From enrollment to compounding advocacy Priya's program produced 200 enrolled advocates in the first month. What she needed was a system that could tell her, six months later, which 80 of those 200 were still active — and what it would take to re-engage the other 120. That question is not answerable with enrollment data. It is answerable with participation rate tracking, content reach reporting, and sentiment signals surfaced in the program manager's admin view without a custom data pull. The [How An Employee SuperApp Transforms The Workplace](/resources/how-an-employee-superapp-transforms-the-workplace) guide covers how these capabilities connect across a unified platform at scale. For organizations planning 2026 community and communication investments, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) provides benchmarks on what leading organizations are doing differently — including the shift from enrollment-focused advocacy programs to participation-rate-focused ones. --- # Importance of Online Communities in B2B Engagement **Author:** MangoApps **Published:** 2024-05-03 **Category:** online-community-software In the current digital era, businesses proactively embrace innovative approaches to foster robust connections with their clients in the B2B sector. One such ... # Why Online Communities Matter for B2B Engagement — and How to Build One That Works Online communities have become a measurable driver of B2B customer retention, knowledge sharing, and product adoption. If you are evaluating whether to invest in a community platform — or trying to improve one you already have — this article explains what the evidence says, what capabilities actually move the needle, and what to look for when selecting a tool. ## The Direct Answer: What Online Communities Do for B2B Relationships In B2B contexts, a well-run online community serves four concrete functions: 1. **Knowledge sharing** — customers and partners exchange best practices, reducing support ticket volume and accelerating onboarding. 2. **Peer-to-peer networking** — professionals connect across organizations, creating stickiness that is difficult for competitors to replicate. 3. **Customer support deflection** — community-sourced answers resolve common questions before they reach your support team. 4. **Brand advocacy** — satisfied customers who participate in a community are more likely to share success stories and refer new business. These are not abstract benefits. According to APQC, Fortune 500 companies lose $31.5 billion annually to knowledge loss — a cost that structured online communities directly address by capturing and surfacing institutional knowledge before it walks out the door. ## Why Most B2B Communities Underperform The gap between a community that thrives and one that goes dormant usually comes down to three problems: **1. Employees and customers cannot find what they need.** Per Banner Health's internal employee poll on intranet performance, 59% of employees report having trouble finding needed information. In a community context, this means members stop returning when search fails them. AI-powered semantic search — the kind that queries across connected systems like SharePoint and Google Drive and returns role-aware, permission-respecting results — closes this gap without requiring users to know where content lives. **2. Engagement is measured by activity, not outcomes.** Posting volume and login counts are vanity metrics. The communities that demonstrate ROI track things like support deflection rate, time-to-first-value for new customers, and changes in [employee engagement](/solutions/employee-engagement) scores over time. According to McKinsey research, 81% of leading companies effectively use data and analytics tools — a standard that community managers should hold their platforms to as well. **3. Mobile and remote access is an afterthought.** Again per Banner Health's employee poll, 61% of employees want intranet and community access outside the work VPN, and 55% want access from a mobile device. A community that is only usable at a desk will see participation drop sharply among field teams, frontline workers, and remote employees. ## What Capabilities Actually Drive Engagement ### Structured Onboarding and Learning Paths New community members — whether customers or employees — need a guided path to value. Platforms that offer curated learning paths, built-in course authoring, and role-specific content tracks reduce time-to-value significantly. A new community platform can be fully launched in as little as 8 weeks for a workforce of 40,000 or more employees, making deployment speed a legitimate selection criterion rather than a marketing claim. For organizations thinking about how [learning and development strategy connects to daily work](/articles/learning-and-development-strategy-embedded-in-daily-work), the onboarding architecture of a community platform is where that strategy either succeeds or stalls. ### Peer Recognition and Social Interaction Peer-to-peer recognition embedded inside a community platform drives 36% more engagement than manager-only recognition programs, according to research cited on MangoApps' recognition product page. This matters because most B2B communities rely entirely on top-down communication — announcements, product updates, support threads — and miss the social layer that keeps members coming back. Communities that include discussion forums, idea voting, commenting, and recognition features create the conditions for members to invest in the space rather than just consume from it. ### AI-Powered Knowledge Discovery The most significant shift in community platforms over the past two years is the integration of AI for knowledge retrieval. Rather than a generic chatbot, the more useful implementation connects to existing content repositories — SharePoint, Google Drive, internal wikis — and returns results that are filtered by the user's role and permissions. This means a customer asking a product question gets an answer drawn from the right documentation, not a hallucinated response or a link to content they cannot access. For teams managing large knowledge bases, this capability is directly relevant to the broader challenge of [knowledge management tooling](/articles/mangoapps-kmworld-100-2026) and how organizations surface the right information to the right person at the right time. ### Measurable Outcomes, Not Just Features The strongest argument for investing in a community platform is a quantified outcome. One documented example: a 40,000-person workforce achieved a 91% platform usage rate shortly after rollout, and attributed a 30-point increase in employee engagement score to social features and AI-powered reporting introduced through the platform. Numbers like these shift the conversation from "what does this platform do" to "what will it do for us." For HR and operations leaders building the business case, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how organizations are quantifying engagement investments and what benchmarks are emerging across industries. ## How to Evaluate a B2B Community Platform When comparing options, prioritize these criteria: - **Deployment timeline**: Can the platform be live and adopted within 8–12 weeks? Longer timelines increase risk and reduce stakeholder confidence. - **Search quality**: Does the platform offer semantic, permission-aware search across connected systems, or only keyword search within its own content? - **Analytics depth**: Can you track engagement outcomes (support deflection, NPS change, content utilization) rather than just activity metrics? - **Mobile experience**: Is the full feature set available on mobile without a VPN requirement? - **Integration breadth**: Does it connect to your existing content systems (SharePoint, Google Drive, Salesforce) without requiring a full migration? For organizations replacing an older intranet as part of this evaluation, the [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides a structured comparison framework across major platforms. ## Frequently Asked Questions ### How long does it take to see ROI from a B2B online community? ROI timelines vary by use case. Support deflection is typically measurable within 60–90 days of launch, as community-sourced answers begin resolving tickets before they are submitted. Engagement score improvements and customer retention effects generally take 6–12 months to show up in survey data. Setting baseline metrics before launch — support volume, NPS, time-to-onboard — is the most reliable way to demonstrate impact. ### What is the difference between an online community and an intranet? An intranet is primarily a top-down content distribution system: policies, announcements, org charts. An online community is bidirectional — it is designed for members to contribute, discuss, and build on each other's knowledge. Many modern platforms combine both functions, but the distinction matters when setting expectations for participation and governance. For a detailed look at what a modern intranet should include, the [Frontline Intranet Requirements checklist](/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) covers the capabilities that matter most for distributed and frontline workforces. ### How do you keep a B2B community active after the initial launch? The communities that sustain engagement over time share a few common practices: a dedicated community manager who facilitates discussion and surfaces valuable contributions; a regular cadence of structured programming (webinars, idea campaigns, product feedback sessions); and recognition mechanisms that reward participation. Peer-to-peer recognition, in particular, has a measurable effect — the 36% engagement lift cited above comes specifically from communities where recognition is embedded in the platform rather than managed separately. ## The Bottom Line Online communities are a legitimate B2B engagement strategy when they are built around measurable outcomes, not just feature lists. The evidence points to three non-negotiable capabilities: AI-powered knowledge discovery that works across connected systems, structured onboarding that gets members to value quickly, and analytics that track outcomes rather than activity. If your current community platform cannot demonstrate a usage rate above 80%, cannot surface role-appropriate answers from your existing content systems, and cannot show a measurable change in engagement or support metrics within 90 days of launch, those are the gaps to address first — regardless of which platform you are using. For a broader view of how internal communication and engagement investments are trending, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the tools, strategies, and benchmarks that organizations are using to measure progress. --- # Employee Engagement Software That Closes the Learning Gap **Author:** MangoApps **Published:** 2024-05-03 **Category:** learning-management In recent times, post-sales strategy has emerged as a crucial phase for building lasting relationships. At the heart of this journey lies an often underestim... # Employee Engagement Software That Closes the Learning Gap Most employee engagement programs diagnose the wrong problem. They survey how people feel, build recognition programs, and improve manager training — all legitimate interventions — without addressing the structural issue underneath: employees who don't know how to do their jobs well don't stay engaged, regardless of how appreciated they feel. Per APQC, Fortune 500 companies lose $31.5 billion annually from knowledge loss. Per Panopto, 70% of employee knowledge is lost when workers leave. These aren't HR data points — they're engagement data points. Every departure takes institutional knowledge with it. Every new hire who can't find what they need disengages before the 90-day mark. The organizations that close the engagement gap are almost always the ones that treat learning as a core infrastructure problem, not a culture initiative. Employee engagement software that integrates structured learning — what the industry now calls a learning experience platform, or LXP — addresses both problems simultaneously: it builds the knowledge infrastructure that keeps employees capable, and the capability that keeps employees engaged. This article makes the case for why learning is the highest-leverage engagement variable, what features separate effective LXP deployments from generic alternatives, and how to measure whether the investment is moving the right metrics. ## The knowledge access problem beneath every engagement survey Engagement surveys ask employees if they feel valued, aligned with company values, and connected to their manager. They rarely ask whether employees can find what they need to do their job today. Per a Banner Health employee poll on intranet performance, 59% of employees reported having trouble finding the information they needed. In the same survey, 55% wanted access from a mobile device — a signal that access friction wasn't limited to office environments but extended to frontline and field workers who need information between tasks, not at a desk. Those numbers describe an engagement problem dressed as an information problem. An employee who spends 20 minutes searching for a procedure, a policy, or a product specification is not spending those 20 minutes doing their job well. Per McKinsey, employees lose 2.5 hours per day searching for information. That's not a time-management issue — it's a knowledge infrastructure deficit that compounds into lower confidence, lower output, and eventually, lower engagement. The engagement investments organizations make — recognition programs, manager training, feedback loops — have real value. But they work against the structural drag of a knowledge environment that makes it hard for employees to feel competent. Competence is a precondition for engagement, not a byproduct of it. ## Why an LXP outperforms a generic LMS learning system The standard LMS learning system was designed for compliance: deliver a course, record the completion, generate a report. That architecture is appropriate for mandatory training. It is poorly suited for ongoing learning, knowledge maintenance, and the role-specific skill development that drives engagement at scale. A learning experience platform operates differently. Instead of pushing a fixed curriculum to all learners, an LXP: - Recommends content based on a learner's role, location, and behavior - Supports multiple formats — video, scenario-based modules, user-generated guides, interactive assessments — from a single content management system - Integrates with the broader employee experience platform rather than running as a standalone system - Surfaces learning opportunities within the workflow, rather than requiring a separate login to find them The distinction matters for engagement because relevance drives voluntary learning. An employee who receives a training notification for a course that doesn't apply to their role doesn't complete it. An employee who can search for "how to handle a return at the register" and find a three-minute video specific to their store's workflow completes it because it solves a problem they have right now. Nine competitor organizations now position "workplace learning" as a core engagement theme. The gap between organizations deploying genuine LXP functionality and those running a legacy LMS as their employee engagement training infrastructure is measurable in adoption rates and time-to-competency. ## What role-aware content delivery means in practice Generic employee engagement software delivers the same experience to every user. That approach fails because a district manager overseeing 12 locations, a frontline associate handling transactions, and a corporate recruiter filling headcount have almost nothing in common in terms of what they need to learn or when. Effective employee engagement training requires segmentation on at least four dimensions: **Role** — A system administrator needs different content than an end user. A department head needs operational context that a frontline worker doesn't — and vice versa. **Location and shift** — Frontline workers in distributed environments need mobile-accessible, short-form content that works without a VPN or a desk. Per the Banner Health employee poll, 61% of employees wanted intranet access outside the work VPN — a signal that access architecture must account for workers who are not office-based. **Tenure and progress stage** — A new hire in week two needs different content than an employee in month 14. An LXP that serves the same onboarding material indefinitely is not an engagement tool; it's a compliance checkbox. **Department and workflow** — Finance users have different use-case patterns than operations teams. Learning content calibrated to workflow context is more likely to be applied, which is the only outcome metric that matters. Organizations that report the highest employee engagement training completion rates have almost always moved from a single curriculum to segmented learning paths. Role-aware delivery is not a premium feature — it is the baseline architecture for content employees will actually use. ## Video and narrative learning — why format is the engagement variable Text documentation has a completion problem. Employees begin reading and stop. The completion rate gap between a policy document and a three-minute scenario-based video covering the same content is significant — not because employees prefer video in the abstract, but because scenario-based content connects more directly to the work they are actually doing. Effective employee engagement software supports three format types that consistently outperform static documentation on completion and retention: **Short-form video modules** — Bite-sized lessons that fit between tasks. For frontline workers, this means content that loads on a mobile device and delivers a complete answer in under five minutes. **Narrative or scenario-based learning paths** — Content structured around a situation the employee recognizes. "How to handle an escalation when the customer has an expired receipt" outperforms "Here is our return policy" for the associate at the register. **Interactive assessments** — Checkpoints that confirm comprehension before advancing a learner, rather than assuming that exposure equals understanding. The format question is also a mobile question. An organization where the majority of employees want mobile access to information but is delivering learning content in PDFs is not making a platform decision — it is making an engagement decision by default, and it is the wrong one. ## The three phases where learning drives loyalty The connection between structured learning and employee retention operates across three phases of the employee lifecycle, each requiring different content design. **Onboarding — getting to competency before disengagement sets in.** Most onboarding failures are not values failures. They are knowledge sequencing failures: new employees receive too much information in the wrong order, without a structure that tells them what to learn first. A deployment benchmark from a Unily and British Airways case study found that a unified learning platform can reach 91% workforce usage within 8 weeks, even for organizations where 80% of workers are frontline employees. The speed-to-competency that enables that adoption rate depends on sequenced, role-specific onboarding content — not a resource library the employee has to navigate alone. **Ongoing adoption — keeping employees current without mandatory training cycles.** Organizations where employees feel most capable are those that surface relevant learning content in the flow of work, not in scheduled training blocks. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), employee engagement is falling globally even as organizations increase engagement program spend — a gap that suggests the problem is structural, not attitudinal. Continuous learning access is part of the structural fix. **Advocacy — turning capable employees into engaged contributors.** Employees who know their domain well enough to teach others are almost always more engaged than those still figuring out their role. Community features that recognize knowledge contributions — answered questions in group forums, short instructional videos, peer-reviewed wikis — convert learning completion into active engagement. ## Measuring learning as an engagement signal Learning completion rates and engagement scores are rarely tracked on the same dashboard. They should be. An employee engagement software deployment that integrates learning data with performance and engagement signals can answer questions that neither system answers alone: Which teams with high learning completion rates also show high engagement scores? Where are learners stalling before competency, and does that stall correlate with early attrition? The analytics layer of an effective LXP should surface four measurements: 1. **Completion rates** — What percentage of employees finish each module or path, by role and department 2. **Time-to-competency** — How long it takes a new employee to reach a defined proficiency level 3. **Content effectiveness** — Which modules correlate with higher performance scores or lower support ticket volume 4. **Engagement drop-off** — Where in the learning path employees disengage, segmented by role and location Connecting these signals to HRIS and performance management platforms closes the loop. A manager who can see that their team's engagement scores lag in the same departments where onboarding completion is lowest has a diagnostic that recognition programs alone can't provide. ## What a unified platform changes at the infrastructure level The cost case for consolidating employee engagement and learning onto a unified platform is straightforward: running a standalone LMS alongside a separate intranet, a separate community forum, and a separate communication tool creates both a cost problem and an experience problem. Per a Unily case study, eliminating a standalone email point solution through a unified engagement platform delivered an $80,000 annual cost saving. The same consolidation logic applies when replacing a fragmented learning stack: integration overhead, duplicate content maintenance, and access friction across multiple systems are costs that don't appear in per-seat pricing but show up in adoption rates and time-to-competency. For organizations evaluating how to structure this consolidation, the [Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026](/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) provides a framework for assessing platform capabilities against a distributed, frontline-heavy employee population — where access and relevance gaps are largest and consolidation payoff is most direct. The [employee engagement solution](/solutions/employee-engagement) on a unified platform connects communication, learning, recognition, and knowledge management so that learning content is findable where employees already spend their time — not in a system they have to remember to log into separately. ## Frequently asked questions **How is a learning experience platform different from a traditional LMS learning system?** A traditional LMS is designed for compliance administration: it stores courses, records completions, and generates audit reports. An LXP is designed for learner behavior: it recommends content based on role and context, supports multiple formats including video and peer-generated content, and surfaces learning opportunities within the workflow. For organizations where the goal is voluntary, ongoing learning rather than mandatory training documentation, the LXP model is the appropriate infrastructure choice. **What metrics show that employee engagement training is working?** The most direct indicators are time-to-competency (how quickly new employees reach proficiency), content completion rates by role and department, and correlation between learning completion and performance or retention data. Secondary indicators include support ticket volume reduction — when employees can find answers in the learning system, tickets for common questions decrease — and voluntary content creation rates, which show whether employees are engaged enough to contribute knowledge rather than only consume it. **How does learning infrastructure connect to employee retention?** The connection is competency-mediated: employees who feel capable in their role are more likely to stay than those who feel uncertain or unsupported. Structured onboarding that sequences content so new employees reach first value quickly reduces early attrition. Ongoing learning access that keeps employees current with process and policy changes reduces the disengagement that drives mid-tenure turnover. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the learning infrastructure investments organizations are prioritizing this year. --- Employee engagement and learning infrastructure are not separate problems. The organizations with the highest engagement scores are almost always those that have made it easy for employees to know what they're doing, find what they need, and grow in their roles — not just those with the most recognition programs. The $31.5 billion annual knowledge loss per APQC is an engagement cost hiding inside an information metric. Closing it requires building learning into the infrastructure of daily work, not scheduling it as a periodic event. --- # Customer Community Platforms: MangoApps Guide **Author:** MangoApps **Published:** 2024-05-03 **Category:** online-community-software These days, customer relationships stand as the cornerstone of business success. But how easy is it to nurture ongoing customer relationships? Well, with a d... # Customer Community Platforms: MangoApps Complete Guide The tool problem in post-sales customer management is not a secret. Customer success managers know it intimately: onboarding lives in one system, training in another, community forums in a third, and product feedback in a ticketing queue that nobody reads regularly. The customer experience of that fragmentation is invisible to the vendor and costly to everyone. Per APQC, Fortune 500 companies lose $31.5 billion annually from knowledge loss — a figure that applies upstream to customer relationships as directly as it does to internal operations. When a customer asks how to configure a feature and the answer exists somewhere in a knowledge base nobody organized, both the customer and the support team pay. Per McKinsey, employees already spend 2.5 hours daily searching for information — a baseline that worsens when customer-facing knowledge is distributed across platforms that don't share data. A customer community platform addresses this structurally, not cosmetically. The category is defined by what it consolidates: customer learning, peer-to-peer community engagement, and idea management in a single environment. This guide covers what MangoApps Community Suite does, where it sits relative to standalone alternatives, and what outcomes B2B organizations should hold any platform accountable to before signing. ## Why fragmented post-sales tools create compounding costs The default post-sales stack at most B2B companies involves a standalone LMS for training delivery, a community forum hosted separately (or not at all), and some version of a product feedback process that ranges from a support ticket queue to an annual survey. Each of these serves a function. None of them share data. The practical consequence: a customer who completes advanced training, participates actively in a peer forum, and submits a high-voted product idea is visible to the customer success team as three separate signals in three separate dashboards — if it's visible at all. The account health picture a customer success manager needs to prevent churn requires manually assembling information from systems that were never designed to talk to each other. This is the cost that tool sprawl produces that never shows up directly in the software budget: analyst hours spent reconciling data, accounts that churn before a risk signal ever surfaces, onboarding completions that go unmeasured because training and community live on opposite sides of a data wall. ## What a unified customer community platform actually changes MangoApps Community Suite organizes the post-sales customer relationship around three functions: Educate (onboarding and ongoing training), Engage (peer community and advocacy), and Innovate (structured idea management). What makes this a platform rather than a product bundle is that all three share the same data layer — a customer success manager sees one account record, not three. ### Learning infrastructure built for B2B customer onboarding The learning component covers the full onboarding arc: guided learning paths sequenced by role, product tier, or industry vertical; built-in course authoring without a separate tool; and a branded training academy that runs without a standalone [learning management system](/solutions/learning-management). Video-based course creation is supported within the authoring environment — significant as async video becomes the dominant format for product education. Teams can record walkthroughs, embed them directly into learning paths, and track completion without exporting to a third-party platform. The deployment timeline comparison is direct: MangoApps Community Suite can be fully deployed and adopted within 8 weeks for large enterprise workforces, compared to a 9-month average for SharePoint intranet implementations per the dormakaba case study benchmark. Speed matters most in onboarding-stage deployments where time-to-value is the metric the customer is actually watching. ### Peer community as a support deflection mechanism The community layer enables structured peer-to-peer interaction through discussion forums, Q&A threads, and user groups segmented by role, product line, or industry. When customers answer each other's questions, support ticket volume falls — not as a side effect, but as a design goal. Per a Banner Health employee poll on intranet performance, 59% of employees report having trouble finding needed information. In a customer community context, that finding translates directly to the cost of unsearchable knowledge: customers submit the same support request repeatedly because no peer answer surfaces when they search. The same survey found that 61% of employees want platform access outside the work VPN — a pattern that applies equally to customers accessing a community on a personal device. MangoApps Community Suite supports this without requiring a corporate credential. AI-powered semantic search returns role-aware results that respect existing permissions, so customers find the right answer without needing to know exact keywords. For a concrete illustration of how community structure drives participation at scale, the [Santee Cooper case study](/resources/santee-cooper-case-study) documents how a distributed workforce community achieved broad engagement across geographically separated teams — the structural principles transfer directly to customer communities. ### Closing the feedback loop between customers and product Most B2B companies collect product feedback. Few close the loop. Customers submit ideas through support tickets or annual surveys and hear nothing — which signals that their input doesn't matter, and prevents the vendor from surfacing which feature gaps are costing them renewals. MangoApps Community Suite provides a structured idea portal where customers submit, vote on, and comment on product suggestions. Intelligent categorization aligns submissions with internal roadmap priorities. Real-time status updates — from submission through review to implementation — close the feedback loop that most organizations leave open. Per Panopto, 70% of employee knowledge is lost when workers leave. The same fragility applies to customer knowledge in siloed systems: when community activity and product ideas live in disconnected tools, the institutional memory of how customers actually use the product evaporates with each platform migration. ## How MangoApps compares to standalone customer community tools The standalone LMS market is large and well-documented. Platforms like Circle, Mighty Networks, and Teachable serve creator and cohort-based learning use cases well. The relevant comparison for B2B organizations is not feature parity on any single dimension — it's what happens at the intersection of learning, community, and product feedback. A standalone LMS delivers training content but does not support peer discussion, idea management, or community advocacy in the same environment. A community forum provides peer interaction but has no native learning infrastructure or product feedback loop. A customer community platform integrates all three, so customers move from a training module to a peer forum to an idea submission without switching tools or re-authenticating. The practical effect for the vendor: lower administrative overhead (one platform to manage instead of three), higher customer engagement (fewer barriers to participation), and a unified data layer that gives customer success managers a complete account picture. For B2B organizations evaluating how their [learning and development strategy](/articles/learning-and-development-strategy-embedded-in-daily-work) connects to customer retention — not just employee development — this integration is the central argument. ## Measuring ROI from a customer community platform Three metrics hold any platform accountable: **Onboarding completion rate.** What percentage of new customers complete the onboarding learning path within the first 30 days? A platform delivering training through guided paths rather than static knowledge bases should measurably improve this number. Track it as a baseline before deployment and measure lift at 60 and 90 days. **Support ticket deflection.** When peer community answers a question, a support ticket does not get submitted. Track the ratio of community-resolved questions to support tickets by category. A healthy community deflects a meaningful percentage of tier-1 support volume — a figure that translates directly to support cost savings and customer satisfaction. **Idea-to-roadmap conversion.** How many customer-submitted ideas make it into the product roadmap within a given cycle? This metric signals that the feedback loop is functional, not performative. Customers who see their ideas implemented are measurably more likely to renew. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how organizations are establishing these baselines across both employee and customer engagement programs — including which leading indicators predict renewal risk before it shows up in renewal data. ## Three questions to answer before selecting a platform **Does the platform share data across its learning, community, and feedback modules — or are these separate tools packaged together?** This is the structural question that determines whether you get unified account intelligence or a more organized version of the same fragmentation. Ask for a demo that shows what a single customer record looks like when that customer has completed training, participated in a community thread, and submitted a product idea. If those are three separate screens, you have a bundle, not a platform. **What does the deployment timeline look like for your organization's complexity?** The 8-week benchmark is meaningful only if it applies to your SSO configuration, content migration scope, and administrator training requirements. Get implementation estimates that are specific to your environment — generic timelines are a planning liability. **What does a successful 90-day outcome look like?** Define this before signing. The metrics are onboarding completion rate, support ticket deflection, and peer community participation. A vendor that cannot tell you what those numbers typically look like post-deployment is not in a position to commit to outcomes — which is itself a signal worth taking seriously. ## What separates platforms that sustain engagement The customer community platforms with durable participation share two characteristics: they reduce the friction of every customer interaction to near zero, and they give customers a visible reason to keep returning. Reduced friction means search that actually works, content that surfaces without hunting, and peer answers that appear before a support ticket feels necessary. Per Banner Health, 55% of employees want platform access from a mobile device — a preference that maps directly to customer behavior. A customer community platform that requires desktop access for participation has already excluded the majority of its most engaged users. A visible reason to return means that the feedback loop closes: customers see their ideas tracked, their contributions acknowledged, and their learning progress reflected in the account record the customer success team reviews before a renewal conversation. Both are design decisions made before the platform goes live — which is precisely where most evaluation processes stop too early. The clearest signal that a customer community platform is working: customers answer each other's questions before your support team does. --- # MangoApps Suite for Complete Customer Experience **Author:** MangoApps **Published:** 2024-05-03 **Category:** online-community-software While employee experience tools have recently become a cornerstone of organizational success, customer experience tools aren't far behind. The seamless colla... # MangoApps Suite for Complete Customer Experience Eighty percent of the global workforce never sits at a desk. Per Emergence Capital, these deskless employees — the retail associate, the healthcare technician, the logistics coordinator — are the people who interact with customers most frequently and have the least access to the information they need to do it well. Per IDC, employees spend 2.5 hours per day searching for information; for a frontline worker between tasks, that search time doesn't produce better answers — it produces an incorrect answer, a customer escalation, or a moment where the brand promise falls apart. The CX programs organizations invest in assume that the employees delivering the service can access what they need when they need it. When they can't, those programs measure a downstream symptom rather than an upstream structural problem. A recognition program, a satisfaction survey, or a new training curriculum can't compensate for employees who don't have the right information at the right moment. MangoApps Community Suite addresses this upstream problem: a unified platform that delivers knowledge, training, communication, and community tools to every customer-facing employee — regardless of whether they have a desk, a corporate email address, or time for a scheduled training block. --- ## Why customer experience breaks before it reaches the customer Per Social Edge Consulting, 91% of organizations operate an intranet. Only 13% of employees use one daily. Nearly a third never log in at all. Per SWOOP Analytics, the average employee spends six minutes per day using intranet tools. This is not an engagement problem — it is an access problem. The systems most organizations have built to house knowledge were designed for the office worker at a desktop: login-gated, permission-heavy, search-unfriendly, and invisible to anyone not on a corporate network. When a frontline associate needs to know the return policy before a customer walks away frustrated, they are not navigating a portal. They are guessing, asking a colleague, or giving the wrong answer. The customer experience that results is not a training failure. It is the output of an information architecture that was never designed for the people who handle the most customer touchpoints. --- ## The frontline access gap that competitors are actively closing Mobile-first, no-email deployment has emerged as the decisive differentiator for organizations with distributed workforces. Several competitor platforms have positioned this capability as their primary feature in recent months, and for a straightforward reason: a platform that requires a corporate email address to log in excludes the majority of customer-facing employees before they ever see a piece of content. MangoApps Community Suite is accessible via mobile without a corporate email. This matters not as a technical detail but as a deployment philosophy. Frontline employees who can't access the knowledge system don't develop workarounds — they operate from incomplete information, and customers absorb the gap. Organizations that deploy platforms designed for deskless access have seen frontline adoption rates reach 90% within the first six months. That benchmark reflects what happens when the tool is built for the employees who need it, not adapted from a system designed for someone else. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), employee engagement is falling globally even as organizations increase program spend. That gap points directly at the structural problem: you cannot engage employees in a system they never log into. --- ## Knowledge management tools that surface answers at the moment of need Effective knowledge management tools don't require employees to know where information is stored. MangoApps Community Suite uses a semantic AI assistant — connected to OpenAI, Gemini, Anthropic, and Azure OpenAI — that returns results respecting existing permissions and surfacing role-relevant content. A customer service representative asking about the return process for a specific product line gets that answer, not every policy document in the system. This architecture is meaningfully different from a static portal. It doesn't depend on an administrator anticipating what people will search. It adapts to who is asking and what their role context requires. Persona-based targeting delivers content by role, region, and language — with message acknowledgment tracking that confirms receipt, not just delivery. When the organization updates a policy that affects one customer segment and one regional team, the update reaches exactly those people and confirms that it was seen. For organizations where customer-facing teams span multiple languages, inline translation across 200+ languages in chats, tasks, and forms removes friction that standard tools create by defaulting to a single language. When a multilingual frontline team can access knowledge in their language without a translation request, response time and answer accuracy both improve. --- ## Getting customer-facing employees to competency faster For many customers, their first impression of a brand is the employee who handles their onboarding or their first support interaction. If that employee is two weeks into the role and working from disconnected training materials, the customer experience reflects the knowledge gap — not the brand standard. Organizations that digitize and mobilize training end-to-end have seen 50% faster new-hire onboarding as a result. MangoApps Community Suite supports this through guided learning paths and structured onboarding flows that sequence content so new employees reach first proficiency before disengagement sets in. A built-in LMS with authoring tools and centralized content management keeps training materials current and accessible from the same environment where employees communicate and collaborate — not a separate platform they have to remember to log into. The core principle is that learning embedded in the workflow is learning that happens. [Why learning and development strategy fails and how to fix it](/articles/learning-and-development-strategy-embedded-in-daily-work) covers the structural reasons why training programs that are disconnected from daily work consistently underperform — and what the measurable cost looks like at scale. --- ## Building a customer community that extends the brand Beyond internal operations, MangoApps Community Suite can serve as the external-facing hub where customers interact with each other, access self-service resources, and submit feedback. The community environment can be fully branded to match the company's customer-facing identity — not a generic portal, but a consistent extension of the brand experience. This distinction matters because brand consistency across every customer touchpoint reinforces trust. A community that looks and feels like the rest of the customer journey is one customers return to because it is familiar and useful, not because they have no other option. Features that support this include targeted communications to specific customer segments, peer-to-peer interaction spaces, customer advocacy programs, and analytics dashboards that surface content gaps before they become support tickets. Analytics at the community level close the measurement loop. Which resources are used, which are ignored, where customers drop off, which topics generate the most questions — this data supports a continuous improvement cycle that most organizations cannot run because their community data is in a separate system from their operations data. --- ## What deployment actually delivers The concrete outcomes from unified platform deployments include $20M in cost avoidance by reducing redundant processes, support escalations, and rework caused by information gaps. The 90% frontline adoption benchmark and 50% faster onboarding figure are not projections — they represent what well-structured deployments achieve when access architecture is designed for the people who need it. The [Santee Cooper case study](/resources/santee-cooper-case-study) documents how one organization built connection across a distributed workforce using the MangoApps platform — the adoption and operational patterns it describes are representative of what a deployment focused on frontline access and knowledge consolidation can achieve. For a broader view of the structural investments organizations are prioritizing in 2026, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the unified platform consolidation that is replacing fragmented knowledge, training, and community tools with single governed environments. --- ## Three questions to answer before evaluating any community suite **How much of your customer-facing workforce has a corporate email?** If the answer is less than half, a platform that requires one for login is the wrong starting architecture. This single constraint determines whether a deployment reaches the employees who drive the most customer interactions — before any feature evaluation begins. **What does your current information gap cost in escalations and resolution time?** Per IDC, 2.5 hours per day per employee searching for information translates directly into customer wait time and incorrect answers. Before comparing feature sets, calculate what the information access problem costs at your scale. That number frames the ROI case for any replacement platform more clearly than any vendor benchmark. **Is your training embedded in the workflow or separated from it?** Organizations where employees complete training in a standalone system and return to a separate work environment consistently see lower completion rates and slower time-to-competency. The platform architecture determines the adoption ceiling before implementation begins — not the quality of the training content. --- The customer experience gap most organizations are trying to close is not a strategy gap — it is an infrastructure gap. Employees who cannot find information quickly, access training in the flow of work, or participate in a community that serves both colleagues and customers cannot deliver a consistent experience regardless of how clearly the brand standard is defined. MangoApps Community Suite closes this gap with knowledge management tools, training infrastructure, communication, and community in a single governed platform — accessible to every customer-facing employee, with or without a desk. --- # Empowering Customer Insights with MangoApps Suite **Author:** MangoApps **Published:** 2024-05-03 **Category:** online-community-software When businesses aim to innovate, customer feedback is a powerful catalyst for growth. With MangoApps Community Suite Innovate, you have a transformative tool... # How MangoApps Community Suite Turns Customer Feedback Into Product Decisions Customer communities are only as valuable as the decisions they drive. Organizations that run idea programs with voting, workflows, and structured review cycles routinely convert community input into shipped features — closing the loop between what customers ask for and what product teams actually build. MangoApps Community Suite is the infrastructure that makes this possible: idea submission, no-code workflow automation, targeted surveys, and real-time analytics in a single platform accessible from any device. The direct answer to how customer feedback becomes a product decision: submitted ideas enter a centralized portal, accumulate votes and comments from community members, move through configurable review stages without engineering involvement, and arrive at a roadmap discussion already ranked, clustered, and annotated with CRM context. That pipeline — from idea to informed decision — is what the suite is built to run. --- ## Why most feedback programs stall before they reach the roadmap Most organizations collect customer feedback. Few close the loop reliably. The breakdown typically happens in one of three places. **Fragmentation** — ideas arrive through support tickets, NPS responses, sales calls, and email threads. No single system sees all of them, so product managers make decisions based on the loudest voice in the last meeting rather than the ranked preferences of the full customer base. **Volume without signal** — when a community generates hundreds of submissions, the effort required to cluster, deduplicate, and prioritize them manually consumes more time than the insights save. **Silent queues** — customers submit an idea and never hear back. Acknowledgement tracking confirms which customers have seen status updates on their submitted ideas, enabling targeted follow-up for anyone who has not yet received a response (Staffbase / product page). When participants feel ignored, engagement drops and the quality of future submissions declines. Highly engaged workplaces show 23% higher productivity and 78% less absenteeism (gallup.com). The same dynamic applies to customer communities: when participants see their input acknowledged and actioned, they contribute more and contribute better. --- ## What MangoApps Community Suite provides The suite covers five interconnected functions. **Idea submission and centralized tracking** — customers submit through a portal that aggregates all requests in one place. Customer success managers can see when multiple accounts are reporting the same issue rather than handling each request in isolation. **Voting and commenting** — community members vote on submitted ideas and add context through threaded comments. Product teams receive a ranked demand signal without commissioning a survey. **No-code workflow automation** — submitted ideas can be routed through review, approval, and roadmap stages without engineering involvement (Beekeeper / product page). Teams configure triage, product review, roadmap consideration, and declined stages in the platform — no custom code required. **Surveys and polls** — targeted questionnaires let teams validate hypotheses before committing to a roadmap decision. Once a cluster of similar ideas is identified, a short poll confirms whether the proposed solution resonates or whether customers would prefer a different approach. **Real-time analytics** — dashboards surface submission volume, vote trends, and engagement rates so teams can spot momentum behind emerging requests before the next planning cycle. Customers can participate from a mobile device, which matters for field users or customers who primarily interact on smartphones. A community platform that requires a desktop session will see lower participation from non-desk participants — a practical limitation that mobile-first access removes. --- ## How to prioritize the ideas a community generates Vote volume alone is not a sufficient prioritization criterion. A request endorsed by fifty SMB accounts may carry less weight than one flagged by two enterprise customers whose contracts are up for renewal. A practical framework combines three signals: - **Vote volume** — how many community members have endorsed the request - **Customer segment weight** — whether the submitters represent high-value accounts, strategic partnerships, or a broader base of smaller users - **Strategic alignment** — whether the idea maps to a current product initiative or an identified gap in the roadmap Unified search across submitted ideas and integrated systems such as Salesforce or ServiceNow surfaces relevant knowledge without switching tools, so analysts can verify whether a similar idea was addressed in a prior release (Unily / product page). That cross-reference step prevents duplicate development work and gives product managers context on the history behind a request. 53% of employees saved more than 30 minutes per week after adopting platform search (National Grid, via Unily). For community managers processing high idea volume, the equivalent time savings come from search that spans the idea portal, CRM records, and support history in a single query. For context on how integrated platforms are reshaping how teams collect and act on feedback, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the consolidation patterns driving adoption of unified feedback tools. --- ## Connecting community feedback to the product roadmap The most common failure mode in idea management is the feedback silo: ideas accumulate in a community platform but never flow into the tools where product decisions are made. Integration with systems such as Salesforce or ServiceNow means a customer success manager can link a community idea directly to an open opportunity or support case — giving product managers full context, including the revenue at stake and the support history behind the request. Idea campaigns — structured prompts that ask the community to respond to a specific question — are a useful tool during roadmap planning cycles. Instead of waiting for organic submissions, a campaign asks: "What is the one feature that would save you the most time this quarter?" Responses arrive tagged and categorized, ready for the prioritization framework above. 99% franchisee participation on a mobile-first community platform across 12,000 users was reported by The Learning Experience (via Joinblink case study). High engagement rates are achievable when the platform is accessible and easy to use — a benchmark that product teams can use when setting participation targets for their own programs. Closing the information gap between what customers request and what product teams know is structurally similar to the challenge addressed in [Closing the Information Gap in Performance Reviews](/articles/closing-the-information-gap-in-performance-reviews): in both cases, the bottleneck is rarely a lack of data — it is the absence of a structured pipeline that routes the right data to the right decision-maker at the right time. --- ## What metrics demonstrate program success Three categories of metrics give a complete picture of community program health. **Engagement metrics** - Monthly active idea submitters - Vote and comment rate per idea - Survey response rate **Pipeline metrics** - Ideas submitted per month - Ideas that advance past triage - Time from submission to a status decision **Outcome metrics** - Roadmap items that originated from community input - Customer satisfaction score change after a community-sourced feature ships - Retention rate among active community participants versus non-participants Outcome metrics are what separate a program that demonstrates ROI from one that is difficult to justify at budget time. Structured communication and feedback programs have been linked to a 40% boost in employee engagement (ioic.org.uk). 26% of UK employees report being deeply disconnected from their organizations (IOIC) — a figure that illustrates how much latent value goes uncaptured when feedback channels are absent or ignored, whether the audience is employees or customers. --- ## Where the returns come from Returns from a customer idea program arrive through three channels. **Reduced churn** — customers who see their ideas acknowledged and actioned are more likely to renew. Acknowledgement tracking confirms which customers have seen specific updates, enabling targeted follow-up before renewal conversations (Staffbase / product page). A customer who submitted an idea and received a status update is in a materially different position than one who submitted and heard nothing. **Faster product-market fit** — shipping features that a ranked, voted list of customers has already validated reduces the risk of building the wrong thing. The community does the research; the product team decides and executes. **Lower research costs** — a continuous stream of community input replaces some portion of paid user research. Targeted surveys and polls within the community provide structured data without the cost of recruiting external panels. 300% improvement in search usefulness was reported after deploying unified cross-platform search (Estée Lauder Companies, via Unily). The productivity return from reducing tool-switching in community management follows a similar pattern: when analysts can search ideas, CRM records, and support history in one place, the time from submission to informed decision compresses. For teams in regulated industries where customer feedback intersects with compliance requirements, the [IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024](/resources/idc-marketscape-2024) covers how leading platforms support feedback and communication workflows in those environments. --- ## A practical starting checklist For teams setting up or auditing a customer idea program: - Define idea categories and tags before launch — retroactive tagging is time-consuming - Configure at least one no-code workflow routing new ideas to a triage reviewer within 48 hours - Set up acknowledgement tracking so submitters receive an automated update when their idea changes stages - Connect the platform to your CRM so ideas can be linked to accounts and open opportunities - Schedule a monthly idea campaign tied to the product planning cycle - Establish three outcome metrics to report to leadership each quarter - Confirm mobile access is enabled so customers can participate from any device --- ## What changes when feedback stops being a silo MangoApps Community Suite is infrastructure for a decision pipeline, not just a collection point. Submitted ideas move through review stages via no-code workflows, accumulate ranked demand signals through voting, and arrive at product planning already annotated with CRM context. The organizations that extract the most value from community programs share one characteristic: they treat feedback as a workflow input, not an inbox. The checklist above provides a concrete starting point. The metrics framework provides what to measure. The ROI analysis provides what to report. Together they define the operational discipline that distinguishes a community that informs product decisions from one that generates goodwill without generating results. For organizations also working to close continuous feedback loops for employees — not just customers — the [Break The Annual Review Cycle](/resources/break-the-annual-review-cycle) guide covers how to build a culture of ongoing development using structured feedback programs analogous to the community model described here. --- # Engaging User Groups With MangoApps Community Suite **Author:** MangoApps **Published:** 2024-05-03 **Category:** online-community-software When it comes to digital collaboration, online user groups stand as dynamic hubs where like-minded individuals come to share insights and cultivate community... When it comes to digital collaboration, online user groups stand as dynamic hubs where like-minded individuals come to share insights and cultivate community. With MangoApps Community Suite, businesses not only create but also manage online user groups for their clients. In this post, explore the best practices for building and nurturing essential online customer communities — and learn how your organization can effectively deepen customer relationships, reduce churn, and encourage innovation through structured employee engagement. ## Define Clear Objectives and Themes Before diving into the creation of user groups, it's crucial to define clear objectives and themes. What is the purpose of the group? What topics or interests will it cover? By establishing a clear focus, businesses ensure that their user groups attract the right audience and facilitate meaningful discussions. Is your digital customer community strictly for discussing product issues and enhancements? Or, will there be forums for socializing and collaboration? With clear objectives and themes, your clients are more likely to accept invitations to these groups. For distributed and frontline teams — who make up roughly 80% of the global workforce, per Emergence Capital — clear group charters are especially important because members may be joining from personal iOS or Android devices with no corporate email or VPN required. MangoApps Community Suite supports this mobile-first access model, ensuring that deskless and remote participants are never excluded from the conversation. ## Interactive Features For User Groups MangoApps Community Suite provides a suite of interactive features to enhance user engagement within groups. Utilize the platform's annotation tools, video capabilities, communication spaces, and easy sharing options to create a vibrant and interactive space. These spaces allow users to collaborate effectively. Letting customers pitch ideas and voice opinions on your product in a safe, encouraging space allows your employees to grow and improve your product — all while establishing lifelong client relationships. AI-powered content personalization takes this further: rather than requiring members to self-navigate every channel, MangoApps surfaces relevant group content to each member automatically based on role, location, and activity history. This matters because employees already lose over four hours per week switching between disconnected systems (per MangoApps product pages), and a unified, personalized feed directly reduces that friction. Organizations exploring the broader [employee experience platform](/solutions/employee-engagement) model will recognize this as a core design principle of modern community spaces. ## Encourage Active Participation A successful online user group hinges on active participation. Encourage members to share their insights, ask questions, and contribute to discussions. With segmented communications and collaboration spaces, users have the option to take part in whatever groups or discussions are most relevant to their needs. Plus, MangoApps Community Suite's user-friendly interface makes it easy for members to actively engage with content, fostering a sense of community. The participation gap is real: per Social Edge Consulting, nearly a third of employees never log in to their organization's intranet, and only 13% use intranet tools daily. Structured user groups with clear themes, regular prompts, and event-based touchpoints are among the most reliable ways to move members from passive observers to active contributors. Branded, mobile-first community access — without requiring a corporate email address — is particularly effective for reaching frontline and geographically dispersed customer segments. ## Implement Smart Moderation Practices Maintain a positive and productive atmosphere within user groups by implementing smart moderation practices. Designate moderators to facilitate discussions, ensure adherence to group guidelines, and address any issues that may arise. MangoApps Community Suite allows for efficient moderation, ensuring a smooth and well-managed user group experience. **Practical moderation steps that reduce conflict and keep groups productive:** - Publish a short community charter (3–5 rules) pinned at the top of every group so expectations are visible from day one. - Assign at least two moderators per active group so coverage is maintained across time zones — critical for geographically dispersed customer communities. - Use MangoApps' role-based permissions to give moderators the ability to hide, flag, or escalate posts without requiring admin-level access. - Schedule a monthly moderator sync to review flagged content trends and update guidelines before problems escalate. - Create a private moderator channel where your team can discuss sensitive issues without surfacing them to the broader community. For organizations managing large or unionized workforces, moderation policies often need to align with labor relations guidelines — a nuance covered in depth in [Managing a Unionized Workforce Is Different. Your Software Should Be Too](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too). ## Organize and Promote Events Within User Groups Hosting events within user groups adds a layer of excitement and purpose. Whether it's webinars, Q&A sessions, or virtual meetups, MangoApps Community Suite's features enable businesses to organize and promote events. These events enhance engagement and provide valuable opportunities for community members to connect. Events are great ways to get your customers involved with each other and excited about the product. For retail and hospitality organizations managing distributed customer communities, in-platform events also serve as low-cost alternatives to in-person gatherings. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) highlights event-based engagement as one of the fastest-growing tactics for keeping remote and frontline audiences connected to brand initiatives. ## Utilize Analytics for Insight MangoApps Community Suite's analytics provide valuable insights into user engagement and group dynamics. Leverage these analytics to understand which topics resonate most with your audience, identify active contributors, and refine your strategies for building and managing user groups. These insights will show you how your customers like to interact, when they feel the need to visit your online community, and what types of discussions they engage with. **Key metrics worth tracking in your community analytics dashboard:** - **Daily and weekly active users (DAU/WAU):** Benchmark against the industry baseline — per Social Edge Consulting, only 13% of employees use intranet tools daily — so you know whether your community is outperforming or underperforming the norm. - **Content contribution rate:** What percentage of members post, comment, or react versus lurk? A healthy community typically sees 10–20% of members generating content. - **Search-to-find ratio:** If members are searching frequently but not finding answers, your knowledge base needs expansion. Per IDC, employees spend an average of 2.5 hours per day searching for information — a cost your community should be actively reducing. - **Event attendance and replay rates:** Low attendance signals scheduling or promotion problems; low replay rates suggest content relevance issues. - **Moderation escalations per month:** A rising trend here is an early warning sign of community health problems before they become visible in churn data. For a broader view of how engagement metrics connect to business outcomes, [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace) provides useful benchmarks for contextualizing your community data against workforce-wide engagement trends. ## Create a Knowledge Base For User Groups Build a repository of valuable information within your user groups using MangoApps Community Suite's knowledge base capabilities. This not only serves as a resource for members but also contributes to the long-term value and sustainability of the community. Having easily accessible information and content regarding your product, updates, release notes, and more makes it a breeze for customers and employees alike to stay on top of improvements, creating a valuable resource repository folks can visit for years to come. A well-structured knowledge base also directly addresses one of the most quantifiable costs in community management: information search time. Per IDC, employees spend 2.5 hours per day searching for information — time that a searchable, well-tagged knowledge base can meaningfully reduce. For organizations in knowledge-intensive sectors, this is where community investment translates most directly into productivity gains. The [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study illustrates how a centralized knowledge resource reduced information bottlenecks across a distributed professional membership. ## What Is the ROI of Investing in Online User Groups? The business case for customer community investment is increasingly quantifiable. Replacing a frontline employee costs between $4,400 and $15,000 (per industry reports cited on MangoApps product pages), which means community-driven retention is a measurable financial priority — not just a culture initiative. When customers feel connected to a product community, they churn less, escalate fewer support tickets, and generate more peer-to-peer referrals. At the workforce level, British Airways achieved a 30-point engagement score increase after deploying a unified employee experience platform. TeamHealth consolidated 200+ enterprise systems into a single mobile dashboard, illustrating the scale of integration that a unified community platform can support. Branded, mobile-first community access — without requiring corporate email or VPN — has enabled healthcare and retail organizations to achieve 87–90% workforce engagement within the first few months of launch, per MangoApps case studies including OU Health, Kansas City Chiefs, and PetSmart. For organizations evaluating employee engagement software options, [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides independent third-party context on how the platform compares across community and engagement dimensions. ## How Do I Extend Community Engagement to Frontline and Remote Members? Geographically dispersed and deskless workers represent roughly 80% of the global workforce, per Emergence Capital, yet most community platforms are designed around desk-based, email-connected employees. MangoApps Community Suite addresses this directly: members can join, participate in, and contribute to user groups from personal iOS or Android devices with no corporate email address or VPN required. For industries where frontline access is the norm — retail, hospitality, nonprofit, and BPO — this mobile-first architecture is not a nice-to-have; it is the difference between a community that reaches your full customer base and one that reaches only the 13% who log in daily (per Social Edge Consulting). Segmented group structures allow you to create role-specific or location-specific communities within the same platform, so a retail associate in one region sees content relevant to their context while a corporate buyer sees something entirely different. Organizations in these sectors can explore how MangoApps applies to their specific workforce context through the [industries/retail](/industries/retail) and [industries/hospitality](/industries/hospitality) solution pages. ## Putting It All Together: A Definitive Action Plan Building an engaging online user group with MangoApps Community Suite is not a one-time setup task — it is an ongoing operational discipline. Here is what the evidence points to as the highest-leverage actions: 1. **Start with a written group charter** that defines purpose, audience, and participation norms before you invite a single member. 2. **Enable mobile-first access** from day one so frontline and remote members are not excluded by device or credential requirements. 3. **Assign and train moderators** using the five-step framework above, and give them the platform permissions they need to act without escalating every issue. 4. **Track the five analytics metrics** listed in the analytics section above — DAU/WAU, contribution rate, search-to-find ratio, event attendance, and moderation escalations — on a monthly cadence. 5. **Build the knowledge base before you need it**, not after members start asking the same questions repeatedly. Per IDC, 2.5 hours per day in search time is the cost of not doing this. 6. **Quantify your ROI** using retention cost data ($4,400–$15,000 per frontline replacement) and engagement lift benchmarks (30-point score increases are achievable) so community investment competes on equal footing with other budget priorities. Organizations that follow this plan consistently report that their customer communities shift from passive support channels into active product development and retention engines — a transformation that shows up in both engagement scores and bottom-line retention metrics. For teams looking to connect community strategy to broader workforce development goals, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) offers a complementary framework for embedding engagement into daily work rather than treating it as a separate initiative. --- # The Ultimate B2B Community Management Platform **Author:** MangoApps **Published:** 2024-05-03 **Category:** press-release ISSAQUAH, Wash., November 29, 2023 - MangoApps, the leading unified modern intranet and employee app, proudly announced the relaunch of MangoApps Community S... # What B2B Community Management Platforms Actually Do — and Why Learning Infrastructure Determines Whether Yours Succeeds B2B software companies lose customers not at renewal but at onboarding — when customers who purchased the product can't figure out how to use it, can't find answers without opening a support ticket, and have no peer community to ask. Per McKinsey research, 89% of frontline workers stay with their companies when leaders genuinely listen to their feedback. The same mechanism operates for customers: those who feel supported through a structured post-sale experience stay; those who don't find alternatives at their next renewal. Most B2B community platforms are built to solve the engagement problem — forums, discussion channels, peer networks. Fewer are built to solve the learning problem that determines whether a customer reaches the value that justified the purchase in the first place. That gap between product launch and full adoption is where churn originates, and it's where a community platform either earns its budget or doesn't. MangoApps Community Suite was built specifically to close that gap — by combining structured customer learning, community engagement, behavioral analytics, and a feedback-to-roadmap pipeline in a single environment. Whether it's the right fit for your organization depends on how you answer the evaluation criteria in this article. ## What a B2B customer community platform actually needs to do A community platform earns its budget by reducing three costs: support overhead (customers who find answers in the community rather than opening tickets), time-to-value for new customers (onboarding that works without continuous hand-holding), and involuntary churn from customers who never fully adopted the product. Each of these is addressable — but only through a combination of learning infrastructure, behavioral analytics, and community engagement working in coordination. Platforms that produce measurable retention outcomes share a structural property: they connect learning completion to community engagement to product usage in a single customer view. A customer success manager who can see which accounts haven't completed onboarding, which are disengaged in the community, and which haven't activated key product features has something actionable. One who only sees forum posts doesn't. Per McKinsey research, 81% of leading companies effectively use data and analytics tools to drive business decisions. The question for any B2B community platform purchase is whether the tool becomes one of those analytics-driven systems — or sits alongside them as a separate, under-connected silo that requires manual reconciliation. ## The four components of MangoApps Community Suite MangoApps Community Suite is organized around four components addressing distinct stages of the post-sale customer journey. **Educate** is a structured learning layer — a learning experience platform (LXP) purpose-built for post-sale customers. Customers access onboarding modules, product training, and ongoing courses from the moment they sign up. Acknowledgement tracking records which customers have completed critical onboarding steps and viewed compliance-sensitive product updates, enabling targeted follow-up rather than blanket re-sends. Organizations that also run internal training programs can share infrastructure between employee learning and customer learning, reducing vendor overhead as both programs scale. For the structural analysis of why learning programs often fail to connect to actual job performance — a pattern that affects both internal and external programs in similar ways — [Why Your Learning and Development Strategy Fails](/articles/learning-and-development-strategy-embedded-in-daily-work) covers the common design failures directly. **Engage** provides community spaces where customers exchange knowledge, ask questions, and build peer relationships. Sentiment analysis derived from in-community interactions surfaces satisfaction signals without requiring explicit survey responses — passive measurement that captures signals customers often won't self-report on a feedback form. Stronger peer networks reduce churn by deepening customer investment in the product ecosystem beyond the direct vendor relationship; when customers know other customers in the same community, switching costs increase meaningfully. **Innovate** structures the feedback-to-product-roadmap pipeline. A unified customer data layer connecting community activity, learning progress, and product usage gives customer success teams full context for every interaction — not just an unstructured feedback queue. Per McKinsey research, 86% of customer-facing teams lack sufficient in-the-moment insights to make good decisions; the Innovate component is designed to surface those signals proactively. The goal is to shift customer success from reactive support toward identifying churn risk before it surfaces in a renewal conversation. **Capture** carries forward the platform's original screen recording and annotation functionality, used for creating training content, documenting product walkthroughs with visual context, and sharing bug reports with enough detail to act on without back-and-forth clarification. ## Where B2B community investments consistently underdeliver The business case for community investment is not in dispute. Highly engaged workplaces see a 23% increase in productivity and 78% less absenteeism, per gallup.com. The underlying mechanism — people who feel heard and connected perform better and stay longer — applies to customer relationships as directly as it does to employee relationships. Per [Gallup's 2026 State of the Global Workplace research](/articles/gallup-2026-state-of-the-global-workplace), consistent acknowledgment and responsiveness to feedback are among the strongest predictors of retention across engagement contexts. The problem isn't the premise. It's the execution gap between launching a community and reaching the retention outcomes the premise promises. Most community platforms address one dimension well — typically the engagement layer, with discussion forums and peer networking — while treating learning infrastructure and behavioral analytics as secondary features or separate integration projects. The result is predictable: a community customers log into occasionally, don't use to complete onboarding, and don't treat as a meaningful substitute for direct support. The platform doesn't change churn behavior because it hasn't closed the gap between community activity and actual product adoption. The differentiating factor for Community Suite is integration across all four components. When a customer success manager opens an account view, they see learning completion rates, community engagement trends, and product usage in context — not scattered across three separate tools. That integrated view is what enables a different kind of work: proactive retention rather than reactive ticket management. Without it, even well-designed community programs tend to plateau at engagement metrics that don't correlate with renewal rates. ## Criteria for evaluating a B2B community platform **Learning infrastructure depth.** If post-sale education is a priority, the platform requires more than a discussion forum. Evaluate whether it supports course sequencing, completion tracking, acknowledgement records, and content updates that don't require rebuilding entire module structures from scratch. For compliance-sensitive onboarding in regulated industries — healthcare, financial services, professional certifications — acknowledgement tracking is a requirement, not an enhancement. **Behavioral analytics.** Passive data (login activity, post counts) is table stakes. The differentiator is whether the platform converts behavioral signals into actionable customer health indicators: which segments are disengaged before they report it, which accounts haven't reached onboarding milestones, which are approaching churn risk based on declining activity patterns over time. Per the [IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment](/resources/idc-marketscape-2024), the leading platforms on analytics are those connecting community activity to broader engagement and product usage data rather than reporting on forum metrics alone. **Integration with existing systems.** A community platform that operates independently of your CRM, product analytics stack, and internal communication infrastructure creates a second data silo. Evaluate the integration architecture before committing. For organizations already on Microsoft 365, the [MangoApps & Microsoft Integration Guide](/resources/mangoapps-microsoft-integration-guide) documents the connection points without requiring separate content management workflows on both sides. **Multilingual support.** For global B2B technology companies serving customers across languages and time zones, native multilingual content delivery — not manual translation workarounds — is a concrete differentiator. Confirm whether the platform supports translated onboarding modules and community content natively, and what the operational cost to maintain translated content looks like at scale. **Onboarding timeline.** A 9-month average deployment timeline — the benchmark from the dormakaba case study for complex intranet projects — is too slow for a community platform expected to affect onboarding outcomes for new customers immediately. Ask vendors for a specific time-to-first-active-community milestone and what structured onboarding support is included in the contract. ## Who should evaluate MangoApps Community Suite The platform fits most directly for B2B software and technology companies that need structured post-sale education alongside a customer community — particularly where acknowledgement tracking, compliance-sensitive onboarding, or behavioral analytics are requirements rather than optional features. Organizations already using MangoApps for internal employee engagement can extend the same platform infrastructure to their customer base without adding a second vendor relationship or a second data environment to manage. It is a less natural fit for companies whose primary requirement is a lightweight discussion forum, or for organizations without a dedicated customer success function to manage moderation, content creation, and community health on an ongoing basis. Community platforms require sustained operational investment alongside the technical infrastructure — a forum with no one actively curating it doesn't reduce support tickets or improve retention outcomes. ## The infrastructure question that determines ROI Community platforms fail for the same structural reason that internal communication tools fail: the channel launches without the learning infrastructure, behavioral signals, and feedback loops that make engagement valuable. A forum without structured onboarding produces customers who browse occasionally and churn predictably. The productivity and retention improvements Gallup measures in highly engaged organizations don't come from launching a community — they come from building the conditions that make engagement a habitual part of the customer's workflow rather than an optional activity. The question isn't whether to invest in a B2B customer community. It's whether the platform you choose connects learning, engagement, and analytics into a single retention mechanism — or leaves those connections as integration projects to be addressed in a future phase that rarely arrives on schedule. --- # Measuring Growth With MangoApps Community Suite **Author:** MangoApps **Published:** 2024-05-03 **Category:** online-community-software When implementing a customer-led growth strategy, understanding the impact of your community engagement is paramount. But, companies often grapple with the c... # Measuring Growth With MangoApps Community Suite Community analytics programs fail for a predictable reason: organizations measure what is easy to collect — logins, page views, comment counts — rather than what predicts retention and operational performance. Per Workday Peakon Employee Voice, engagement metrics can surface warning signs up to nine months before an employee leaves. Most organizations are not using that data well enough to act on it. The measurement gap is not a data collection problem. McKinsey research finds that 81% of leading companies effectively use data and analytics tools, and that 89% of frontline workers will stay with their companies if leaders listen to their feedback. The barrier is not access to analytics — it is the architecture of what gets measured and how quickly findings reach the people who can act on them. MangoApps Community Suite addresses this with a layered analytics approach: passive engagement signals, embedded feedback mechanisms, operational workflow data, and external benchmarking in a single view. This article explains how to read each layer — and how to connect them to outcomes that matter to leadership. ## Why community metrics usually stop short of being useful The most common community measurement failure is not a lack of data — it is a mismatch between what gets reported and what determines whether employees stay, comply, and perform. Per Unily research, only 24% of frontline workers feel their feedback from customer interactions is heard by leadership. That number reflects more than a morale problem. It reflects a structural gap: organizations are collecting engagement data and not closing the loop. When content is viewed but feedback is never solicited, and survey results sit in a spreadsheet no one acts on between annual cycles, analytics create an illusion of listening without the substance of it. Per Beekeeper research, 86% of companies say their frontline teams need better insights to make good decisions in the moment. The problem is not that the data does not exist — it is that the measurement architecture does not surface it in a form that is actionable. The engagement analytics stack has to do three things to be useful: capture what is actually happening (behavioral signals), solicit how people feel about it (feedback signals), and connect both to operational outcomes that leadership can evaluate. Most community platforms stop after the first. ## The behavioral signals layer: activity, content, and logins The behavioral signals layer captures what community members actually do — not what they say they do. User activity metrics — views, downloads, comments, shares, reactions — reveal which topics generate genuine participation versus passive scrolling. Enterprise Apps Today 2022 research found that 60% of high-performing firms report increased performance when employees are recognized, and that peer-to-peer recognition programs generate 36% more engagement than manager-only programs. If your community analytics show that member-generated content consistently outperforms top-down announcements, that is a structural signal worth acting on, not a one-week anomaly. Content performance by format matters for teams running training or onboarding programs. If video modules consistently outperform text-based documentation on completion rates, that is information a learning and development team can act on immediately — reallocating content effort from low-performing formats to high-performing ones, rather than producing more content in formats employees are not consuming. Login analytics in MangoApps show total logins per day, unique logins, and new user sign-ups for the trailing 90 days. The login graph surfaces whether the community is growing, plateauing, or contracting. Declining unique logins three weeks after a major policy rollout is a different problem than declining logins in week two of deployment — and the response should differ accordingly. For organizations evaluating whether their current measurement framework catches these signals early enough, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading organizations are restructuring analytics to surface attrition signals between formal review cycles. ## Where most platforms stop — and the operational layer that changes the picture The most significant limitation in most community analytics platforms is that measurement stops at communication. You can see who logged in, what content they viewed, and whether they commented. You cannot see whether they completed the associated compliance form or acknowledged the policy update they were required to read. MangoApps extends analytics into operational workflows: task completion rates, form usage, SOP acknowledgments, and process adherence. This distinction is not cosmetic. Knowing that a new standard operating procedure was viewed by 94% of the relevant team is informative. Knowing that only 61% completed the required acknowledgment form is actionable. Per Beekeeper research, 72% of companies investing in tech-enabled frontline insights report increased productivity. That gain is more likely when analytics span both communication and operational dimensions — measuring not just who saw the information but who acted on it. A composite view of communication engagement and operational task data gives managers something closer to a real performance signal than either metric alone. For [employee engagement strategies](/solutions/employee-engagement) designed to reduce operational errors and improve compliance rates, the communication layer tells you who received the information; the operational layer tells you who applied it. In healthcare, logistics, and BPO environments where SOP adherence has direct safety or quality implications, those two layers need to be measured together to be interpretable. ## Embedded feedback versus passive behavioral data One structural weakness in traditional community measurement is the separation between engagement data and explicit feedback. Members interact with content, but their opinions are collected through a separate survey tool — often weeks later, with response rates that make the results directionally unreliable. Pulse surveys embedded directly inside specific communications — not sent as standalone emails — close this gap. When a member reads a policy update and responds to a two-question pulse in the same interface, the feedback is contextual and immediate. It reflects the actual content, not a reconstructed memory of it. MangoApps supports both behavioral signals and embedded feedback in a unified view. The combination gives a more complete picture than either approach alone: behavioral data captures what members do; embedded pulse data captures what they think about it. When the two diverge — members are logging in and viewing content but pulse scores are declining — that divergence is a high-value signal worth investigating before the next scheduled survey cycle. For teams building continuous feedback loops, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents how organizations are structuring embedded feedback mechanisms that supplement, rather than replace, formal review processes. ## Benchmarking beyond your own history Internal analytics tell you whether your community is improving relative to its own past. They do not tell you whether that improvement is meaningful relative to comparable organizations. External benchmarking compares your engagement metrics against industry peers — providing a reference point that internal-only analytics cannot replicate. If your monthly active user rate is up 12% year-over-year but comparable organizations are averaging 30% growth, internal progress is real but competitive position is declining. Two external benchmarks worth anchoring to: the average SharePoint intranet deployment takes approximately nine months to reach functional adoption, per the dormakaba case study — a useful reference point for evaluating whether your MangoApps community is reaching active use faster than the baseline. The same case study documents a 654% increase in corporate news coverage after deploying a unified intranet versus a legacy solution, illustrating the scale of adoption difference that platform choice can produce. MangoApps' customer community data, aggregated across organizations, supports benchmarking comparisons that internal reporting alone cannot replicate. For teams in retail, nonprofit, or hospitality sectors, where community engagement benchmarks vary significantly by industry, external reference points add meaningful context to internal dashboards. ## Making the data actionable: connecting metrics to outcomes Analytics are only useful if they connect to outcomes that leadership evaluates. The most common failure mode in community measurement is reporting engagement metrics — views, logins, comments — without translating them into business outcomes: retention, productivity, compliance, or quality performance. The alignment framework is more practical than it sounds: **Name the outcome first.** Decide what business result the community is meant to support before selecting which metrics to track. Reducing onboarding time, improving frontline retention, and increasing SOP compliance each require different leading indicators. **Identify the behavioral leading indicators.** For onboarding time reduction, the relevant metric is new hire login frequency in the first 30 days, not overall community engagement. For SOP compliance, it is acknowledgment form completion rate, not content view count. Tracking the wrong metric for the outcome you care about produces confident-looking dashboards that miss the signal entirely. **Set thresholds that trigger action, not just reporting.** If new hire login frequency drops below a defined level in week two, that is a signal for a manager to intervene — not a data point to include in a monthly summary. The value of community analytics is not in the data; it is in shortening the distance between the signal and the response. **Review the connection quarterly.** What predicts retention at month two of deployment is not necessarily what predicts it at month fourteen. The relationship between community metrics and business outcomes changes as the community matures and members develop their own patterns of use. For organizations working through formal performance management frameworks, community analytics serve as a real-time supplement to structured review cycles — surfacing signals that annual or quarterly reviews are too infrequent to detect. The [Closing the Information Gap in Performance Reviews](/articles/closing-the-information-gap-in-performance-reviews) article covers how behavioral data is being used to supplement point-in-time review processes across industries. ## A six-month cadence for building an analytics practice For teams establishing measurement from a low or zero baseline, the progression matters as much as the tools: **Months 1–2:** Establish baseline metrics for logins, content engagement by format, and member interaction patterns. Identify the members driving the majority of activity — these are your community anchors, and their participation patterns set the baseline against which everything else will be measured. **Months 3–4:** Identify peak engagement windows — the hours and days when your workforce is most active — and restructure content scheduling accordingly. For shift-based workforces in retail, hospitality, or logistics, posting critical content during off-shift hours means it gets buried under the next shift's notifications. Timing data turns a scheduling guess into a data-driven decision. **Months 5–6:** Connect community metrics to at least one defined business outcome and set action thresholds. Introduce embedded pulse surveys tied to specific content types — starting with policy updates and training modules, where the feedback signal is most operationally valuable. By this point, you should have enough baseline data to distinguish a signal from a fluctuation. The progression from passive measurement to action-oriented analytics is an organizational practice, not a platform configuration. Community analytics in MangoApps provide the infrastructure. The discipline of connecting data to action — and the systems that ensure someone sees the signal and responds — belongs to the teams that use it. For organizations building that discipline at scale, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading organizations are integrating community, communication, and operational data into unified measurement frameworks. The goal is not more data. It is data that prompts action at the moment the action is still available. --- # Screen Capture: Copyright or Fair Use? **Author:** MangoApps **Published:** 2024-05-03 **Category:** workplace-productivity Screen captures and image use on both private and personal blog use is common practice. Since the internet offers an easy to access collective of  usefu... # Screen Capture: Copyright Violation or Fair Use? A training coordinator at a logistics company is building onboarding documentation for a new route management system. She takes screenshots of the application's interface and embeds them in the guide so new drivers understand what they're looking at. Three states away, a marketing analyst screenshots a competitor's pricing page for an internal competitive brief. Meanwhile, a high school teacher captures an image of a news article to use in a media literacy lesson. Each of these uses raises the same legal question: does capturing and reproducing a screenshot of copyrighted material constitute infringement, or does it fall within fair use? The answer isn't a simple yes or no. It's a structured analysis that courts apply on a case-by-case basis — and for most practical uses, it reduces to two variables. ## What copyright actually protects Copyright protects the specific expression of an idea, not the idea itself. When someone screenshots a SaaS dashboard, they're not copying the underlying concept of organizing data visually — they're reproducing a particular creative expression of that concept, and that's what copyright law covers. Critically, copyright doesn't protect facts. A screenshot of a government data table, a publicly-released chart, or factual information arranged by a third party sits closer to fair use than a screenshot of an original illustration, a branded creative asset, or distinctive visual design. The less creative the original work, the more latitude fair use provides. One distinction that creates persistent confusion: plagiarism and copyright are separate frameworks. Plagiarism is passing off someone else's ideas or writing as your own — an ethical and academic violation. Copyright is a matter of law governing the exact expression of ideas in specific formats. Crediting the source doesn't resolve a copyright question, though it may demonstrate intent, which is relevant to the analysis. ## The four-factor test applied to screen captures Fair use is codified in Title 17 of the Copyright Act as a doctrine permitting limited use of copyrighted material without acquiring permission from rights holders. Courts apply a four-factor balancing test. As one federal judge observed in Princeton University Press v. Michigan Document Services (99 F.3d 1381, 6th Cir. 1996), "fair use is one of the most unsettling areas of the law" — deliberately flexible to prevent copyright from stifling the educational and creative work it was designed to promote. No single factor is decisive; all four are weighed together. **Purpose and character of the use** The central question is whether the use is transformative — does it add new meaning, commentary, or context, or does it simply reproduce the original? Educational use, criticism, commentary, and news reporting receive explicit protection under the Fair Use Doctrine. Commercial purpose weighs against fair use, and transformation is what distinguishes a legitimate screenshot from misappropriation. The training coordinator building onboarding documentation is creating instructional context that didn't exist in the original application. That's transformation. A competitor reproducing screenshots of a product's interface to mislead customers about what they'll be purchasing is neither transformative nor protected. **Nature of the copyrighted work** Published factual work is more susceptible to fair use than unpublished or highly creative work. A screenshot of a public data visualization, a functional UI built from standard interface components, or a factual text document sits closer to fair use than a screenshot of an original illustration, a hand-drawn graphic, or an unpublished internal document. The more the original work is primarily a creative artifact — visual art, original photography, creative writing — the more copyright protection it commands and the less flexibility fair use provides. **Amount and substantiality of the portion used** Courts have deliberately avoided setting numeric thresholds. There's no 10% rule, no pixel limit. What matters is whether the captured portion represents the "heart" of the original work. For images, a screenshot often captures the complete original — that's a practical reality of the format. The analysis then shifts to whether capturing the full image was necessary for the stated purpose, and whether it's being used in a genuinely transformative way. Parody is the strongest example of how context changes this factor's weight. Effective parody requires capturing enough of the original to be recognizable — by definition, it takes the "heart" of the original — yet it consistently receives fair use protection because transformation is inherent to the form. **Effect upon the potential market** This factor carries the most practical weight. Courts assess whether the screenshot substitutes for the original — whether someone who would otherwise purchase or license the copyrighted work could rely on the screenshot instead. If the screenshot competes with or directly undermines the market for the original, fair use is unlikely to hold. This extends to derivative markets. A screenshot that displaces licensing revenue, competes with the rights holder's own image distribution, or enables uses the rights holder could reasonably license is at risk even when the primary use seems benign. ## When screen captures are almost certainly fair use Several categories of use consistently receive fair use protection across court decisions: **Educational and instructional use.** A training team capturing software interfaces for employee onboarding guides, a teacher embedding a screenshot of a news article in a classroom exercise, or a researcher reproducing a screenshot to illustrate an analytical point — all of these sit comfortably within fair use when the use is non-commercial, limited in distribution, and tied to a legitimate instructional purpose. **Commentary and criticism.** Screenshots used to comment on, critique, or analyze the subject of the capture are textbook fair use. A product review that shows the actual interface, a journalistic piece that reproduces a headline to analyze its framing, a technical blog post that captures an error message to explain a workaround — in each case, the screenshot is evidence, not a substitute. **Transformative parody.** A screenshot that becomes the raw material for a parody receives strong fair use protection because it creates something new from the original rather than competing with it. The derivative work comments on the original; it doesn't replace it. **News reporting.** Screenshots used in reporting on events where the screenshot itself is newsworthy — a social media post that documents a public statement, a screen recording that demonstrates a software defect, a captured interface that is itself the subject of the story — receive fair use protection as journalism. ## When screen captures cross the line **Direct commercial use without transformation.** Using a competitor's branded interface screenshot in an advertisement, embedding a third-party screenshot in a product sold to customers, or reproducing creative content in full without adding commentary or analysis — these uses collapse the four-factor analysis quickly. Commercial benefit to the user without transformation or value to the rights holder is where fair use breaks down. **Undermining the rights holder's market.** If the screenshot substitutes for licensed use — replacing a stock image license, displacing image licensing revenue, reproducing a creative work in full for distribution — the fourth factor weighs heavily against fair use regardless of intent. **Reproducing highly creative or unpublished work.** Screenshots of original artwork, unpublished documents, or creative content that represents the primary product of the rights holder get significantly less fair use latitude than screenshots of factual, functional, or publicly available material. A screenshot of a graphic designer's portfolio work is a much higher-risk capture than a screenshot of a company's public-facing website. ## Practical questions about screen captures that fair use guides don't answer **Does crediting the source make it legal?** Attribution demonstrates good faith and may be relevant context, but it doesn't cure copyright infringement. A credited screenshot that otherwise fails the four-factor test is still potentially infringing. Credit the source as a matter of ethical practice, but don't treat attribution as legal clearance. **What about screenshots of public domain or open-source content?** Public domain content — work whose copyright has expired or been explicitly released — isn't subject to copyright protection at all, so fair use analysis doesn't apply. Open-source licenses are more nuanced: they govern source code, not the visual output or UI design of the software. A screenshot of an open-source application's interface may still raise copyright questions depending on which elements were captured and what the specific license covers. **What if the platform's terms of service prohibit screenshots?** Terms of service and copyright are separate legal frameworks. A platform may contractually prohibit screenshots — violating that prohibition is a contract issue, not necessarily a copyright issue. If the screenshot captures copyrighted content, both frameworks may apply simultaneously, but they're governed by different legal standards. **How do I get permission when a use case is borderline?** Contact the rights holder directly. Many organizations that produce software, creative content, or branded imagery have licensing processes or media kits that cover exactly this scenario. For software interfaces specifically, product marketing teams are often willing to authorize legitimate instructional or analytical uses quickly — the process takes less time than the uncertainty it resolves. ## The bottom line for screen capture use Fair use is a defense available to raise if challenged — not a guaranteed safe harbor. But for most practical screen capture uses, the analysis reduces to two questions: Is the use transformative? And does it substitute for or compete with the original? Educational use, critical commentary, and instructional documentation sit well within fair use when the purpose is clear and the use doesn't undermine the market for the original work. Direct commercial reproduction of creative content without transformation is where fair use consistently fails. The closer a screen capture use gets to financial gain at the rights holder's expense — without adding commentary, context, or transformation — the more exposure it creates. When the commercial stakes are high or the intended use is outside the educational and critical categories, seek permission. The conversation is usually shorter than the legal uncertainty it replaces. --- # Top 10 Creative Uses of Screen Capture in Education **Author:** MangoApps **Published:** 2024-05-03 **Category:** workplace-productivity IntroductionIn the age of digital learning, educators are constantly seeking innovative methods to engage students and enhance the educational experience. Sc... Per the LinkedIn Workplace Learning Report, 94% of employees say they would stay longer at a company that invests in their career development. That statistic reframes the screen capture conversation: the question is not whether to create video learning content, but whether the infrastructure behind that content actually connects to job performance and retention. Nine competitors are now actively publishing content on workplace learning. Seven are staking out video learning as a distinct content category. Organizations treating screen capture as a standalone classroom utility — rather than as a native content-creation layer inside a unified learning platform — are falling behind on both fronts. This article covers the 10 most effective uses of screen capture in learning and development contexts, across both formal education and enterprise training programs. Throughout, the critical distinction is the same: screen capture tools deliver the most value when recorded content feeds directly into trackable learning workflows, not when it lives in a shared drive as an unassigned video file. ## Why screen capture migrated from classroom to workforce training Screen capture started in education as a way to annotate slides and record lectures. That use case is still valid. But the technology has migrated decisively into workforce learning, compliance training, and onboarding — contexts where it solves a fundamentally different problem. In a classroom, the primary benefit is engagement. In an enterprise training context, the primary benefit is reach: getting a consistent version of a procedure, a safety walkthrough, or a software onboarding process to every employee who needs it, regardless of location, shift, or device. Organizations managing distributed workforces cannot replicate that consistency through in-person training alone. ## The 10 uses ### 1. Flipped learning and onboarding preparation The flipped classroom model — reviewing content independently before applying it in structured sessions — translates directly into workforce onboarding. Screen-recorded product walkthroughs, process overviews, and tool introductions let managers free live sessions for Q&A and practice rather than first-pass explanation. Per the Forrester Report, organizations that invest in structured onboarding and training infrastructure can realize $0.7M in increased efficiency of new employee onboarding over three years. That figure assumes recorded content is assigned automatically and tracked — which requires an LMS learning system, not a folder of video files shared via Slack. [Why learning and development strategies fail](/articles/learning-and-development-strategy-embedded-in-daily-work) often starts here: organizations invest in content creation but skip the delivery infrastructure that makes content trackable and repeatable. ### 2. Step-by-step software and process documentation Annotated screenshots and screen recordings are the most efficient way to document procedures that involve navigating software. A written SOP with text instructions for a 12-step process requires learners to context-switch constantly between the documentation and the interface. A screen recording with annotations removes that cognitive load. This use case scales significantly when content standards like SCORM, AICC, xAPI, and CMI5 are supported by the delivery platform. Those standards let organizations migrate existing screen-recorded training content into a unified learning platform without rebuilding courses from scratch — protecting prior investment in course libraries built on any authoring tool. The practical test for this use case is simple: can a new hire watch a screen-recorded SOP on their phone and arrive at their first day already knowing the system? For frontline roles with high turnover, that question has a direct cost answer — every hour of live onboarding time replaced by a watched-and-confirmed recording is an hour a manager spends on production rather than instruction. ### 3. Compliance training for frontline and deskless workers Screen-recorded safety procedures, equipment operation walkthroughs, and compliance training are especially valuable for frontline and deskless workers who lack consistent desktop access. Per the Forrester Report, organizations that deploy structured frontline training see $2.0M in increased productivity of frontline workers over three years. The gap these recordings close is concrete: a retail associate or warehouse employee receiving a screen-recorded safety walkthrough on a personal phone gets a consistent version of the procedure — not an informal verbal summary during a shift handoff. Mobile-first video learning lets employees start a screen-recorded tutorial on a desktop and continue on a phone without losing progress, a critical design requirement for any training program serving distributed teams. For teams managing audit-ready compliance programs, [HR Compliance That Runs Every Day, Not Just at Audit Time](/articles/hr-compliance-that-runs-every-day-not-just-at-audit-time) covers how accessible, trackable content delivery supports compliance documentation at scale. ### 4. Personalized feedback and performance coaching Video feedback on work is categorically more useful than written comments. A screen recording where a reviewer walks through a submitted deliverable — narrating observations in real time — gives the recipient something they can pause, rewind, and reference later. This is especially useful for procedural skills where seeing what went wrong matters more than reading about it. This use case also supports peer review workflows. Employees capturing and sharing demonstrations of their work for structured feedback builds a review culture that asynchronous text threads rarely achieve. ### 5. Visual note-taking and knowledge capture Screenshots of key slides, annotated diagrams, and recorded demonstrations create reference materials that function differently from text notes alone. For organizations building internal knowledge bases, screen captures of system states, configuration screens, or workflow processes create documentation that stays accurate in a way that written descriptions age out of. A screenshot of what a form should look like at a given stage of a process is more reliable than a paragraph describing it six months later. For regulated industries, that accuracy distinction matters: a training document that references a UI that no longer exists creates compliance risk, not compliance coverage. Screen captures tied to version-controlled content libraries close that gap. ### 6. Role-based and onboarding-stage learning paths Screen-captured content reaches its full potential when assigned by role, department, or onboarding stage. An employee in warehouse operations has a different required training set than someone in finance; a new hire needs different content than a manager transitioning to a new function. LMS-integrated screen capture enables completions, quiz scores, and engagement analytics to be tracked in a single [learning management](/solutions/learning-management) dashboard without switching apps. That visibility is what turns a folder of recordings into an ongoing learning program — one with accountability built in rather than reported after the fact. ### 7. Online course creation and eLearning modules L&D teams building formal courses use screen recordings as the primary content layer: recorded lectures, software demonstrations, and scenario walkthroughs form the backbone of eLearning modules that learners take at their own pace. The distinction between this and ad hoc screen recording is structure: a course module with defined objectives, embedded quizzes, and completion tracking is a fundamentally different artifact than a shared video file. The delivery platform determines how much of that structure is achievable — and whether it integrates with existing HR systems or adds another manual reporting layer. ### 8. Accessibility and inclusive training design Screen capture tools improve accessibility when combined with captions, annotations, and variable playback speed. Learners can work at their own pace; captions make content accessible for employees in noisy environments or with different learning requirements; annotations guide attention within a recording without requiring continuous narration. For compliance training in regulated industries, accessibility is a legal requirement. Screen-recorded content with captions and transcripts satisfies those requirements in a format that is easier to produce and update than static PDF documentation. ### 9. Documentation and digital portfolios Students and employees can use screen captures to build records of development over time — completed training, demonstrated competencies, and certifications that form the audit trail both employees and compliance teams need. In IT and operations contexts, screen recordings of troubleshooting processes capture institutional knowledge before it walks out the door. This documentation logic extends to structured learning paths: when screen-recorded content is assigned and tracked by role, the completion record becomes a training history rather than a list of watched videos. ### 10. Engaging remote and distributed learners Screen capture is the infrastructure of distance learning: pre-recorded lectures, live screen sharing during virtual sessions, and asynchronous video feedback all depend on it. For organizations managing both remote and on-site employees, screen-recorded content delivers a consistent training experience regardless of where someone is located or what shift they work. Per the Forrester Report, desktop workers at organizations that invest in connected learning infrastructure can see $7.5M in increased productivity over three years. The mechanism is not the recording itself — it is the combination of accessible content, structured delivery, and tracking that makes learning transfer to job performance. ## The integration layer that makes it work The use cases above describe what screen capture can do. The limiting variable is not the recording tool — it is whether that content lands inside a delivery system that assigns it to the right people, tracks completion, and surfaces engagement data to L&D teams. Organizations that treat screen capture as a standalone documentation utility get convenience. Organizations that embed it inside a unified learning platform get a training program — one where recorded tutorials become trackable workflows, where mobile-first delivery reaches frontline workers on personal devices, and where content standards protect prior investment in course libraries. For L&D professionals building that infrastructure, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how early-stage and scaling organizations are structuring training delivery to make ongoing learning measurable rather than aspirational. The LinkedIn data is direct: 94% of employees would stay longer at a company that invests in their career development. Screen capture is one of the most cost-effective ways to produce that investment. The infrastructure that delivers it determines whether the investment reaches the people who need it. --- # Visual Tools: Mango Recorder vs. Windows Capture **Author:** MangoApps **Published:** 2024-05-03 **Category:** workplace-productivity As humans, we like visual input. In fact, it’s fair to say we crave visuals to inspire, explain and entertain us. A hard piece of evidence that shows just ho... # Mango Recorder vs. Windows Screen Capture: A Practical Comparison for Workplace Visual Communication If you need to share a screen capture with a colleague, the tool you use determines whether that takes 90 seconds or 9 steps. This article compares Mango Recorder and the built-in Windows screen capture workflow side by side — covering steps, annotation options, storage, offline capability, and the situations where each approach makes sense — so you can make an informed choice for your team. **Bottom line up front:** Mango Recorder reduces the capture-to-share workflow from 8–9 steps to 3, eliminates the need for third-party image storage, and requires no IT involvement. Windows screen capture is free, works offline, and is already installed — making it a reasonable fallback when you have no internet access or need a one-off capture with no sharing requirement. --- ## Why Screen Capture Matters for Employee Communications Visual context reduces ambiguity in written communication. When employees document a process, flag a bug, or explain a workflow step, a screenshot with annotations conveys in seconds what a paragraph of text cannot. According to Gartner (2023), 47% of workers struggle to find necessary information at least half the time — and unclear, text-only documentation is a significant contributor to that problem. For teams building [employee communications](/solutions/employee-communications) practices — whether for onboarding, SOP operations documentation, or day-to-day operations instructions — the friction in the capture-and-share process directly affects whether employees actually use visual tools at all. Frontline and distributed teams, in particular, need workflows simplified to three steps or fewer to achieve meaningful adoption (per Unily/CVS case study). --- ## Windows Screen Capture: Step-by-Step The Windows built-in workflow has not changed substantially in years. Here is what it looks like in practice: 1. Press **Print Screen**, **Alt + PrtScn**, or **Ctrl + PrtScn** to capture the full screen or active window. On Windows 7 and later, open the Snipping Tool, select the snip type, then drag to select the area. 2. Open **Paint** (or another image editor). 3. **Paste** the capture into Paint. 4. **Crop**, remove background clutter, add text or basic annotations. 5. **Save** the edited file locally. 6. **Upload** to a file-sharing service (Dropbox, Google Drive, etc.) to generate a shareable link. 7. **Retrieve the URL** — typically 2–6 additional clicks depending on the storage service. 8. **Paste the link** into an email, chat message, or document. That is 8 steps at minimum, not counting the clicks required to retrieve the link from your storage service. Each step requires switching between applications: the capture, the editor, the file storage service, and the communication channel. --- ## Mango Recorder: Step-by-Step 1. **Capture.** Use a designated hotkey for region, full-screen, or window capture. 2. **Annotate.** Add callouts, shapes, arrows, and text directly in the capture interface — no separate editing application required. 3. **Share.** One click uploads the capture and copies a shareable link to your clipboard. From the same window, you can email the capture, upload it to your MangoApps account, or print it. Three steps. No application switching. No third-party image storage required. ### The Time Math The efficiency difference compounds quickly. If an employee makes 5 screen captures per day and saves 5 minutes per capture by using a 3-step workflow instead of an 8-step one, that is approximately **2 hours saved per week per employee**. Across a team of 20, that is 40 hours per week redirected away from manual operations overhead. This is not a theoretical benefit. Reducing support requests is a documented outcome when employees can self-document and share visual context without IT involvement — one case study recorded a 52% decrease in support requests after employees gained self-serve visual documentation capability (per Simpplr/Workday case study). A separate rollout of a simplified, mobile-friendly communication tool to a 40,000-person workforce achieved a 91% usage rate (per published case study data). --- ## Feature Comparison: Mango Recorder vs. Windows Capture | Feature | Mango Recorder | Windows Screen Capture | |---|---|---| | **Steps to share** | 3 | 8–9 | | **Annotation types** | Callouts, shapes, arrows, text | Basic text only (via Paint) | | **Built-in storage** | Yes — 1 GB per user (free tier); more with MangoApps suite | No — requires third-party service | | **Shareable link** | Generated automatically | Requires upload to external service | | **Offline capability** | Capture and annotate offline; sharing requires connection | Full offline capability | | **IT involvement required** | No | No (capture); Yes (for shared storage setup) | | **OS compatibility** | Windows | Windows (Snipping Tool: Windows 7+) | | **Integration with team platform** | Native MangoApps integration | Manual upload required | | **Cost** | Free download (basic) | Included with Windows | --- ## When Windows Screen Capture Is the Better Choice A fair comparison acknowledges the scenarios where the built-in Windows tool is the right answer: - **You need a one-off capture with no sharing requirement.** If you are capturing something for personal reference only, the extra steps are irrelevant. - **You are working fully offline.** Mango Recorder's sharing features require an internet connection. Windows capture and local Paint editing work without one. - **Your organization restricts third-party software installs.** If IT policy prevents installing additional tools, the built-in Snipping Tool is your available option. - **You need a quick, unformatted screenshot for a document.** Pasting directly from clipboard into a Word or Google Doc is faster than going through any dedicated tool. For everything else — recurring documentation, SOP operations guides, operations manual creation, employee communications training materials, or any capture that needs to be shared with a colleague — the 3-step workflow is meaningfully more efficient. --- ## Frontline and Remote Workers: A Specific Use Case The original case for screen capture tools focused on office PC users, but the need is equally acute for frontline and deskless employees who document processes in the field. When a warehouse associate needs to flag a labeling error, a healthcare worker needs to document a workflow deviation, or a retail manager needs to share a planogram issue, a tool that requires 8 steps and a desktop image editor is not usable in practice. Mango Recorder's IT-free, no-code workflow — capture, annotate, share — means frontline employees can create and distribute visual context without submitting a ticket or waiting for IT support. This positions screen capture as a genuine [employee communications platform](/solutions/employee-communications) capability rather than a desktop productivity niche. Frontline and distributed teams can achieve 90%+ adoption of a new visual communication tool within the first six months when the workflow is simplified to three steps or fewer (per Unily/CVS case study). Eliminating a standalone image-storage application in favor of an integrated capture-and-share workflow can also generate measurable cost avoidance at the team level by removing per-seat licensing for point solutions (per Unily/Wipro case study). --- ## Frequently Asked Questions ### Does Mango Recorder work on Mac or mobile? Mango Recorder is a Windows application. Teams that need cross-platform or mobile capture capability should evaluate whether MangoApps' broader platform features — including mobile-accessible content sharing — meet their requirements. ### What happens to captures when storage fills up? The free basic account includes 1 GB of storage per user. Upgrading to a full MangoApps suite account provides expanded storage. Captures stored in MangoApps remain accessible to the team through the platform rather than being tied to an individual's local drive or a separate file-sharing service. ### Is there a learning curve? The 3-step workflow is designed to require no training. The annotation toolbar is visible within the capture interface, so employees do not need to learn a separate editing application. For teams building operations instructions or SOP operations documentation at scale, this matters: a tool employees can use without a training session is a tool they will actually use. --- ## The Bottom Line If your team regularly uses screen captures to document processes, communicate issues, or build operations manual content, the Windows built-in workflow creates unnecessary friction. Eight steps, multiple application switches, and a dependency on third-party storage add up to hours of lost time per employee per week. Mango Recorder's 3-step workflow — capture, annotate, share — removes that friction without requiring IT involvement, additional software licenses, or a separate storage service. It is free to download, integrates with MangoApps, and is well-suited to both office and frontline use cases. For teams evaluating their broader approach to visual communication and documentation, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring their communication toolsets, and the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) addresses how documentation practices connect to operational efficiency. If you are ready to reduce the steps between capturing something and sharing it, download Mango Recorder and run the comparison yourself. --- # How to Choose the Right Screen Capture Software **Author:** MangoApps **Published:** 2024-05-03 **Category:** workplace-productivity With a variety of options available for screen capture software, you should definitely evaluate your options carefully. Basic capture functions should allow ... ## How to Choose the Right Screen Capture Software With a variety of options available for screen capture software, you should evaluate your options carefully before committing to one. Basic capture functions should allow you to capture and alter your screenshot, record video, and share any file type — not just images and video. As you research screen capture software for your business, keep these five key factors in mind to make the best choice. The right tool should fit naturally into your daily [workforce management](/solutions/workforce-management) workflow rather than sitting as an isolated utility. **Ease of Use** The last thing you want from screen capture software is an overly complicated interface. The point of screen capture is to easily capture what is on your screen to present a moment in time clearly and without friction. You should be able to use the software without being a computer expert to capture and alter the image. This matters especially for frontline and field workers who need to document SOPs, safety issues, or training moments in the field using mobile devices — without desktop access. Mobile-first screen capture workflows allow these workers to capture evidence and share with managers instantly, a capability that standalone desktop tools often overlook entirely. **Edit Functions** Comprehensive screen capture software should provide all the tools you need to capture, annotate, and save your captures in a variety of formats. One could argue the software's edit functions should weigh the most heavily when choosing screen capture software. Beyond just capturing the image, you should be able to find and use the tools necessary to create your desired annotations. Look for a simple way to highlight, add text, and add shapes without needing additional editing software. Screen capture and annotation tools integrated directly into a work management platform eliminate the need to switch between standalone apps, reducing context-switching friction for operational teams — a meaningful advantage when workers are executing operations instructions across multiple tasks in a single shift. **Capture Options** At a minimum, your screen capture software should have the following capture capabilities: full screen, window capture, region capture, and video capture. Scrolling capture and timer-controlled capture are useful options only if you will actually use them. Extraneous options can complicate basic function and cause frustration. Shop for functions you actually need and don't be drawn in by ones that merely sound promising but don't speak directly to your needs. For teams building an operations manual or documenting sop operations, video capture paired with region capture is often the most practical combination. **Features** It's easy to get drawn in by software that has lots of features. You need to evaluate what you use in practical application. Look for software that allows you to customize hot keys for the actions you will use most. The best software will offer easy-to-navigate toolbars and a clear image viewer. A bulk share feature is a great tool to have as well. Being able to drag and drop files to create a zip file with a shareable link is useful for teamwork management and cross-functional project communication at scale — a capability highlighted as differentiating in unified platform comparisons. You should also have access to capture history with shareable links and an option to print. When capture history is searchable by meaning rather than just filename or date, it becomes operationally useful rather than a passive archive. AI-powered search and retrieval of saved captures is an emerging differentiator worth evaluating: workers documenting manual operations or training moments need to find the right screenshot or video clip quickly, not scroll through hundreds of dated files. **Online Storage** When choosing free screen capture software, it's difficult to expect sizable online storage at no cost. You should be provided some online storage with access to your capture history. Some apps offer larger amounts of free storage when you upgrade your account. This matters because when you choose the right software, you're going to want to integrate it into your workflow and have access to all your saved captures as they accumulate — particularly as teams scale. For context on what strong internal tool adoption looks like, a frontline workforce deployment benchmark of 75% platform adoption across 12,000 users, with 10 daily app opens per user, illustrates how embedded, easy-to-use tools drive habitual daily use. Storage and retrieval design directly affects whether a tool reaches that kind of engagement. Like all tools you incorporate into your workspace, you want your screen capture software to be straightforward and adaptable. The best option shouldn't be hard to use or difficult to integrate into your daily operations. --- ## Which Screen Capture Software Should You Actually Choose? The five factors above give you a framework, but applying them to real products requires a comparison. Here is how the most common categories stack up: - **Free, open-source tools** (e.g., ShareX, Greenshot): Strong on capture options and basic annotation; limited on cloud storage, mobile support, and team sharing. Best for individual contributors who need lightweight, desktop-only capture. - **Paid standalone tools** (e.g., Snagit): Comprehensive edit functions, scrolling capture, and video recording. Pricing typically runs $30–$60 per user for a perpetual license. Best for content creators and technical writers producing operations instructions or training documentation. - **Video-first tools** (e.g., Loom): Optimized for async video messaging rather than static annotation. Strong shareable-link workflow; weaker on region capture and image editing. Best for remote teams where approximately 60 million full-time working Americans — about half the US workforce — can work remotely at least part of the time, per Gallup.com. - **Platform-integrated capture**: Screen capture built into a unified work management or intranet platform eliminates app-switching entirely. Screenshots feed directly into task assignments, inspection records, and approval chains without leaving the platform. This is the strongest fit for operational teams managing sop operations, frontline documentation, or examples of lean operations workflows at scale. If your team is already evaluating a unified employee platform, reviewing [frontline intranet requirements](/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) alongside your screen capture criteria will help you avoid buying a standalone tool you'll later need to replace. --- ## How Do Free vs. Paid Plans Compare for Business Use? The free-vs-paid decision comes down to three variables: storage limits, team sharing features, and annotation depth. - **Storage**: Free tiers typically cap at 2–5 GB of capture history. Paid plans range from 50 GB to unlimited. For teams building an operations manual or archiving training captures, paid storage is usually necessary within the first year. - **Team sharing**: Bulk file sharing with a single shareable link — the feature that supports cross-functional teamwork management — is almost always a paid feature. Free plans typically require sharing individual files. - **Annotation depth**: Free tools cover highlights, arrows, and text. Paid tools add blur/redaction, step-numbering, callouts, and template overlays — features that matter when producing formal operations instructions or compliance documentation. For organizations weighing the broader ROI of integrated workforce tools, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how platform consolidation affects per-user productivity and tool adoption rates. --- ## What If Screen Capture Is Part of a Larger Operations Workflow? For many teams, screen capture is not an end in itself — it is one input into a broader documentation and communication chain. Screenshots of defects feed quality tickets. Training video clips become onboarding modules. Annotated captures of system errors become IT tickets with full context attached. When screen capture is embedded in a platform that also handles task management, shift scheduling, and employee communications, the operational value compounds. Workers on the floor documenting manual operations don't need to email a screenshot to a manager, wait for a reply, and then open a separate ticketing system. The capture, the annotation, and the assignment happen in one place. For frontline-heavy industries where this integration matters most, [closing the information gap in performance reviews](/articles/closing-the-information-gap-in-performance-reviews) is one downstream benefit — managers have visual evidence of issues and resolutions already attached to the relevant records, rather than relying on memory or self-reported summaries. --- # Taking Screenshots on Different Platforms **Author:** MangoApps **Published:** 2024-05-03 **Category:** workplace-productivity Ever been stuck with a problem on your desktop/laptop/mac or smart devices only to have go-to trouble shooters tell you to just send them the screenshot? Or ... # Taking Screenshots on Different Platforms Screenshots are one of the most-used tools in everyday computing — whether you're capturing a booking confirmation, documenting a bug for IT support, or sharing something on your screen with a colleague. The specific method depends on your operating system and device. This guide covers every major platform: Windows, Mac, iPhone, iPad, and Android — with the quick method and the options that give you more control. ## What is a screenshot? A screenshot, or screengrab, is a digital image of whatever is currently visible on your screen. Unlike a photo of a physical document, a screenshot captures everything exactly as it appears — including text, buttons, menus, and the layout of your application. Screenshots are useful when something can't be printed, when you need a timestamped record of a transaction, or when written descriptions aren't enough to explain what you're seeing. ## How to take a screenshot on Windows Windows gives you several ways to capture your screen, and the right method depends on whether you need the full screen, a specific window, or a custom selection. **Full-screen capture (clipboard):** Press **PrtScn** (Print Screen) on your keyboard. This copies a snapshot of everything visible to the clipboard. Open any image editor or document, press Ctrl+V to paste, and save the file from there. **Full-screen capture (auto-save):** Press **Windows key + PrtScn**. Windows automatically saves the screenshot as a PNG file in the Pictures > Screenshots folder — no paste required. The screen briefly dims to confirm the capture. **Partial screenshot (Snipping Tool):** Press **Windows key + Shift + S**. The screen dims and a small toolbar appears at the top. You can choose rectangular snip, freeform snip, window snip, or full-screen snip. The selection copies to your clipboard and previews in the bottom-right corner — click the preview to open it in the Snipping Tool for annotation or saving. **Snipping Tool app:** Search for Snipping Tool in the Start menu for a full editing interface. You can set a capture delay (useful for menus or tooltips that disappear when you press keys), annotate with a pen or highlighter, and save in PNG, GIF, or JPEG format. On most keyboards, PrtScn is in the top-right area. On laptop keyboards, it may be a secondary function requiring you to hold Fn first. ## How to take a screenshot on a Mac Mac screenshot shortcuts are built into the operating system and have become more capable with each macOS version. **Full-screen screenshot:** Press **Command + Shift + 3**. The screenshot saves automatically as a PNG file on your Desktop with a timestamp filename. **Selected area:** Press **Command + Shift + 4**. The cursor becomes a crosshair. Drag to select the portion of the screen you want to capture, then release. The file saves to your Desktop. **Capture a specific window:** Press **Command + Shift + 4**, then press the Space bar. The cursor changes to a camera icon. Click any open window to capture it — the screenshot includes a drop shadow around the window edges. **Screenshot toolbar (macOS Mojave and later):** Press **Command + Shift + 5** to open a floating toolbar with all capture modes: full screen, selected window, selected area, screen recording, and a timer. This is the most flexible approach on modern Macs, and it lets you choose a save location before capturing. **Copy to clipboard instead of saving:** Hold Control while pressing any of the above combinations. The screenshot goes to the clipboard instead of saving as a file — useful when you need to paste it directly into an email or message. By default, Mac screenshots save to the Desktop as PNG files. To change the default folder, open the Command+Shift+5 toolbar and choose a different location under Options. ## How to take a screenshot on iPhone and iPad The method varies slightly depending on whether your device has a Home button. **Face ID models (iPhone X and later, most iPads without a Home button):** Press the **Side button** (right side) and the **Volume Up button** simultaneously, then quickly release. A thumbnail of the screenshot appears in the bottom-left corner. Tap it to annotate or share immediately, or leave it — it will dismiss on its own and save to the Photos app. **Touch ID models (older iPhones and iPads with a Home button):** Press the **Home button** and the **Top or Side button** at the same time. The same thumbnail preview appears. **AssistiveTouch method:** If pressing two buttons simultaneously is difficult, enable AssistiveTouch in Settings > Accessibility > Touch > AssistiveTouch. Once enabled, tap the floating button, go to Device > More > Screenshot to capture with a single tap. All iPhone and iPad screenshots save to the Photos app in an album called Screenshots for easy retrieval later. ## How to take a screenshot on Android Android screenshot methods vary by manufacturer and Android version, but the universal shortcut works on virtually every device. **Universal method:** Press the **Power button and Volume Down button** at the same time. Hold for about one second until you see or hear the capture animation. The screenshot saves to your Gallery or Photos app, usually in a Screenshots folder. **Google Assistant:** Say "Hey Google, take a screenshot" or open Google Assistant and tap the screenshot icon. This is useful when the button combination is awkward or your hands are occupied. **Samsung palm swipe:** On Samsung Galaxy devices, swipe the edge of your hand horizontally across the screen. Enable this in Settings > Advanced features > Motions and gestures > Palm swipe to capture. **Scrolling screenshots:** Many Android devices let you capture more than what's currently visible. After taking a standard screenshot, tap the scroll or "capture more" button in the preview toolbar. The device stitches multiple captures into one long image — useful for capturing entire web pages or long chat conversations. ## Where do screenshots save by default? Knowing where your screenshots land prevents the frustrating experience of taking a capture and then spending five minutes searching for it. - **Windows (PrtScn only):** Clipboard only — must be pasted into an application and saved manually - **Windows (Windows + PrtScn):** Pictures > Screenshots folder, saved as PNG - **Windows (Snipping Tool):** Clipboard, with option to save from the editor - **Mac:** Desktop, saved as PNG with a timestamp filename - **iPhone/iPad:** Photos app > Screenshots album - **Android:** Gallery or Photos app > Screenshots folder (internally stored in DCIM/Screenshots) On Windows, you can change the Snipping Tool's default save folder in its settings. On Mac, the Command+Shift+5 toolbar lets you choose any folder before capturing. On mobile devices, the location is fixed to the Photos or Gallery app, but you can move screenshots to other albums from within the app. ## How to annotate screenshots after capturing Taking the screenshot is often just the first step. In most situations — support tickets, team communication, tutorials — you'll want to mark up what you captured before sharing. **Windows:** Open the screenshot in the Snipping Tool or Microsoft Paint. The Snipping Tool includes a pen, highlighter, and touch writing tool for quick annotations. Paint gives you text boxes, shapes, and a crop tool for more structured edits. **Mac:** Click the thumbnail preview immediately after capture, or open the file from the Desktop. macOS opens it in Quick Look with Markup tools — shapes, text boxes, arrows, a magnifier, and a signature option. For more control, open it in Preview, which adds cropping, color adjustment, and freehand drawing. **iPhone/iPad:** Tap the screenshot thumbnail immediately after capture, or open it from the Photos app and tap Edit. The Markup editor includes a pen, highlighter, pencil, shapes, text, and a magnifier tool. **Android:** The preview toolbar after capture includes a pencil icon for annotation. Samsung devices offer a more complete editor with text, stamps, and crop tools. For devices with limited built-in editors, Google Photos includes basic markup support. ## Troubleshooting: when screenshots don't work **Nothing happens when pressing the shortcut:** On Windows, the PrtScn key may require the Fn key on some laptop keyboards. On Mac, verify screenshot shortcuts are enabled in System Settings > Keyboard > Keyboard Shortcuts > Screenshots. **Screenshot is blank or shows a black screen:** Streaming services, banking apps, and payment screens block screenshots at the system level as a security or DRM measure. This is enforced by the application itself and is not a problem with your device or settings. **Wrong screen captured on dual monitors:** On Windows, Windows+PrtScn captures all monitors combined into one image. Use the Snipping Tool (Windows+Shift+S) to select the specific area you want. On Mac, Command+Shift+4 lets you draw a selection across any part of your combined display space. **File didn't save after capture:** On Windows, using PrtScn without the Windows key only copies to the clipboard — the image disappears if you copy something else before pasting it. On Mac, if Desktop captures aren't appearing, check whether iCloud Desktop and Documents sync is delaying or redirecting the saves. ## Choosing the right method for your situation For most everyday uses, the fastest shortcut on your platform is all you need. The situations where you'll want a more specific method: - **Partial capture:** Snipping Tool on Windows, Command+Shift+4 on Mac, or region selection on Android - **Immediate annotation:** Markup tools on Mac, iPhone, or iPad give the fastest workflow - **Timed captures for menus or tooltips:** Snipping Tool with delay on Windows, Command+Shift+5 with timer on Mac - **Long-page captures:** Scroll capture on Android or Samsung devices - **Sharing immediately without saving:** iPhone thumbnail share sheet, or clipboard shortcuts on Mac Every major platform includes enough built-in tooling to handle everyday screenshot needs without third-party software. The learning curve is minimal — it is mostly a matter of knowing which shortcut applies to your specific device. Once that shortcut is muscle memory, taking a screenshot takes about one second. The challenge shifts from "how do I take this" to "where did I save it" — which is why knowing your platform's default save location is worth committing to memory alongside the shortcut itself. ## Frequently asked questions ### What file format do screenshots save in by default? Windows, Mac, iPhone, iPad, and most Android devices save screenshots as PNG by default. Some Android manufacturers save as JPEG. PNG is lossless, meaning text and UI elements stay sharp even after saving — it is generally the better format for screenshots than JPEG. ### Can I change where screenshots are saved? On Windows, the Snipping Tool allows you to set a default save folder. On Mac, the Command+Shift+5 toolbar has an Options menu for choosing any folder. On iPhone, iPad, and most Android devices, screenshots are fixed to the Photos or Gallery app, but you can reorganize them into albums from within the app. ### Why is my Android screenshot saving in the wrong place? Android saves screenshots to internal storage, typically under DCIM/Screenshots or Pictures/Screenshots. If you are using a third-party gallery app, it may display albums differently than the default Photos app. Open your device's file manager and check both locations if screenshots seem to be missing from one app but not another. --- # Top 10 Benefits of Free Screen Capture Tools **Author:** MangoApps **Published:** 2024-05-03 **Category:** workplace-productivity Organization leaders are always looking for ways to make processes at work easier, functional and more effective. The tools we need to accomplish these thing... # Top 10 Benefits of Free Screen Capture Tools Organization leaders are always looking for ways to make processes at work easier, functional, and more effective. The tools we need to accomplish these things don't have to be complicated or expensive. Free screen capture software is one of the most underused simple tools available — and it delivers immediate, measurable value for employee communications, teamwork management, and sop operations documentation. Companies can use free screen capture software to improve the clarity of communication and enhance group collaboration across all departments and disciplines. Here are the top ten ways screen capture software fosters better team collaboration at work. 1. **More efficient bug reporting.** A critical step in any QA process, you can make reporting bugs easier with screen captures. Capture the issue on your screen and highlight the specific problem. You'll be able to annotate and share with your team in just a few easy steps. 2. **Creates shareable links.** We are working in a 140-character world, so less is more. Instead of lengthy emails, simply take a screen capture and pass on the shareable link to your colleagues. A link unlocks exactly what you want to share without unnecessary explanation. 3. **Provides specific visual aids.** Move away from abstract descriptions and give specific visual imagery to support your ideas. This is especially valuable when updating an operations manual or communicating operations instructions to distributed teams — visuals eliminate the ambiguity that text alone cannot. 4. **Gives context.** You can give explicit and specific context to things by providing a visual. A screen capture can eliminate confusion about what is being described, questioned, or demonstrated. Per Gartner, 2023, 47% of workers struggle to find necessary information at least half the time — a well-annotated screen capture directly reduces that friction. 5. **Captures moments in time.** Share an exciting milestone met, a feature on a news site, or a ranking on a search page. You can easily capture a moment in time to be preserved and shared easily with your team. 6. **Provides easy access to capture history.** A good free screen capture software should offer you a reasonable amount of free online storage to quickly and easily access your capture history. 7. **Lets you capture stills and video.** Capture a short video using screen capture software. It's a great tool for demonstrating a protocol change in your company, recording examples of lean operations for training purposes, or reporting bugs. 8. **Helps you give concise feedback.** A good screen capture that is accurately annotated gives you a way to provide specific feedback and leaves less room for misinterpretation. Employees navigate 6–8 disconnected tools daily, making a single visual communication layer critical to reducing context-switching fatigue — a screen capture shared through a central [employee communications platform](/solutions/employee-communications) cuts that loop short. 9. **Allows you to share multiple files easily.** Screen capture software like Mango Recorder by Mango Apps has a bulk share feature where you share multiple files with one easy zip file link. By being able to save captures in a variety of formats, you can share different file types. 10. **Makes work social.** With screen capture software you can make things like office memes. It doesn't sound like a big selling point, but creating a funny office meme can lighten up morale or bring some comic relief when needed. Add captions to photos, draw a mustache on your co-worker to wish them a happy birthday, or make your own photo of the day to circulate in your office. ## Which Free Screen Capture Tool Should You Use? The most widely used free options — Snagit (trial), Greenshot, ShareX, Lightshot, and the built-in tools in Windows (Snipping Tool) and macOS (Command+Shift+4) — cover the core use cases above. When choosing, evaluate four criteria: - **Annotation depth:** Can you draw, highlight, blur sensitive data, and add text in one step? - **Video support:** Does it record screen video as well as stills? - **Storage and history:** How long does it retain captures, and can you access them from mobile? - **Integration:** Does it connect to your existing employee communications training workflow or ticketing system? Frontline and deskless workers — who represent more than 80% of the global workforce — benefit most from tools that work on any mobile device without requiring a corporate email or VPN. Captured visuals and shareable links work on any device, making screen capture a practical communication equalizer for teams without dedicated desks. For organizations already using a unified [employee app](/solutions/employee-app), screen captures shared through that hub reach every worker in one step. ## What Are the Limitations of Free Screen Capture Tools? Free tiers come with real constraints worth knowing before you commit: - **Storage caps:** Most free plans limit cloud history to 30–90 days or a fixed number of captures. - **No team management:** Free tools rarely offer shared libraries, permissions, or audit trails — important for manual operations documentation that needs version control. - **Limited video length:** Free screen recording is often capped at a few minutes, which may not be enough for full sop operations walkthroughs. - **No analytics:** You won't know whether a shared capture was viewed, which matters for employee communications training compliance. For teams that outgrow free tools, the logical next step is a platform that centralizes visual content alongside other communications. Replacing scattered, paper-based communication processes with a single digital hub reduced employee turnover by 26% in one frontline transport deployment (Joinblink / Go North West case study). Given that replacing a single frontline employee costs between $4,400 and $15,000, the business case for investing in better visual communication infrastructure is straightforward. For a broader view of where employee communications is heading, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the shift from fragmented tools to unified digital hubs in detail. ## How Do I Get Started with Screen Capture at Work? Getting a team to adopt screen capture consistently takes less effort than most communication initiatives: 1. **Pick one tool and standardize it.** Fragmentation defeats the purpose. Choose a single free tool and add it to your onboarding checklist. 2. **Set a naming convention.** Captures shared without context become noise. A simple format — `[project]-[date]-[issue]` — keeps history searchable. 3. **Integrate with your existing workflow.** Drop captures directly into your project management tool, help desk, or operations manual rather than emailing them as attachments. 4. **Train in five minutes, not five hours.** Screen capture is one of the few tools that requires almost no employee communications training — a short recorded walkthrough (itself a screen capture) is enough. 5. **Review and iterate.** Per McKinsey research, 81% of leading companies effectively use data and analytics tools. Apply the same discipline to communication tools: track whether visual documentation is reducing back-and-forth on recurring issues. For teams managing shift-based or frontline workforces, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines how visual communication fits into a broader operational strategy. ## The Bottom Line Free screen capture software is not a replacement for a structured employee communications platform, but it is one of the fastest ways to reduce miscommunication, accelerate bug reporting, and document operations instructions without adding cost or complexity. The ten benefits above are achievable today, with tools already available on every operating system. Start with one use case — bug reporting, protocol documentation, or async feedback — and expand from there. Teams that build a habit of visual communication consistently report fewer clarification cycles, faster onboarding, and stronger cross-functional alignment. Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback; clear, visual communication is one of the most direct ways to demonstrate that listening at scale. --- # 5 Effective Ways to Communicate With Screenshot Tools **Author:** MangoApps **Published:** 2024-05-03 **Category:** workplace-productivity You may not necessarily think of screenshot software as great go-to tool for communicating. Upon further examination, you will find that it can be one of you... According to a 2023 Gartner survey, 47% of workers struggle to find necessary information at least half the time. The tools most organizations rely on to close that gap — email threads, chat messages, typed summaries — share a structural limitation: they describe situations rather than show them. Screenshot and screencast tools work differently. A captured screen eliminates the guesswork between what a sender means and what a recipient understands. This article covers five specific applications of screenshot tools for workplace communication, along with practical guidance on annotation, tool selection, and how visual documentation connects to broader SOP and operations workflows. ## 1. Building and maintaining SOP documentation Operational procedures change constantly. Software updates, compliance requirements shift, and teams revise how they handle recurring tasks. Screenshot-based documentation keeps SOPs current without requiring a technical writer — any team member can capture a screen, annotate the relevant steps, and update the reference guide without waiting on a documentation cycle. The most effective approach pairs before-and-after screenshots when a process changes. A side-by-side capture showing the old workflow alongside the new one makes the update immediately clear to anyone who has to implement it. Numbered callouts tied to written steps create an operations manual that new and returning team members can reference without additional explanation. For frontline and deskless workers — retail associates, field technicians, clinical staff without a corporate email login — visual SOPs matter even more. Step-by-step guides that work on mobile and remain accessible in low-connectivity environments cover a gap that text-heavy operations instructions cannot. Per McKinsey research, 89% of frontline workers are more likely to stay with their company if leaders listen to their feedback and invest in their experience; a well-maintained visual operations manual is a tangible signal of that investment. ## 2. Onboarding guides and employee reference materials A screenshot-based reference guide for company procedures gives new employees a practical starting point that reduces their dependence on colleagues for basic navigation questions. Unlike a recorded training video, a series of annotated screenshots can be skimmed, searched, and referenced mid-task without rewatching. The most useful guides are organized around scenarios a new hire encounters in their first 30 days: how to access key systems, where to find updated policies, how to submit standard requests, and how to escalate common issues. Sharing the guide as a linked file rather than an email attachment makes it easier to update and eliminates version confusion. Employees already navigate 6–8 disconnected tools daily, which means any reduction in back-and-forth for procedural questions has a compounding effect on productivity. Centralizing visual reference guides in a shared [employee communications](/solutions/employee-communications) hub — rather than distributing them across drives, email folders, and chat pins — gives new hires a consistent place to look and gives administrators a single point to update. Replacing scattered paper processes with a structured digital knowledge base reduces operational friction and accelerates time-to-productivity for frontline teams. ## 3. Reporting technical issues and problems A typed description of a software bug or system issue rarely contains enough information for the person resolving it. Resolution cycles lengthen because the resolver has to ask clarifying questions: which page were you on, what did you click, what error message appeared. A screenshot or short screencast eliminates most of those follow-ups. Step-by-step screen captures are particularly effective for issues involving a multi-step sequence. Capturing each step with a brief annotation — rather than summarizing the issue in a single sentence — gives the responder enough context to reproduce the problem and verify the fix. The responder can reply in kind: a screen recording of the correct procedure cuts the next cycle of back-and-forth to zero. For teams managing a high volume of recurring system issues, a library of resolved-issue captures becomes an informal knowledge base. Organizations that have replaced scattered communications with a single digital hub have reported a 26% reduction in employee turnover (Blink / Go North West frontline case study) — the same principle applies to technical support documentation: when resolutions are captured visually and findable, the same questions stop generating repeat effort. ## 4. Sharing milestone achievements and performance updates Communications about positive outcomes — a sales target met, a project delivered, a search ranking achieved — tend to lose impact when delivered as a sentence in a status email. A screenshot of the actual metric or result makes the achievement concrete and shareable. Captures from a reporting dashboard, a search results page, or a project management tool carry more weight than a paraphrased summary. Recipients engage with the image rather than reading past an unverified claim. Milestone captures can be distributed via shared link to relevant teams without requiring recipients to navigate to a separate system or have access to the source tool. This approach is particularly effective for distributed organizations where not everyone has visibility into the same dashboards. A screenshot democratizes the data: anyone with the link sees exactly what was achieved, without a login or permission dependency. ## 5. Directing attention to new content and profiles Launching a new website section, publishing an updated resource, or adding a new employee profile works better with a visual complement to the link. A bare URL tells recipients nothing about what they are about to see or what specifically merits their attention. An annotated screenshot of the new content — with a callout marking the relevant section or field — increases the likelihood that the recipient opens it and reviews the right part. This is especially relevant for [employee app](/solutions/employee-app) workflows where attention is split across multiple channels and notifications. A visual preview embedded in a communication reduces the decision cost of clicking. For new-hire profiles, a screenshot that highlights the employee's team, location, and role gives colleagues a reason to engage rather than a generic prompt to check out a link. ## How to annotate screenshots effectively Annotation is where most teams underutilize screenshot tools. A raw capture with no markings forces the recipient to interpret what matters. A few consistent practices make the difference between a screenshot that communicates and one that adds noise. Use numbered callouts rather than freehand arrows when documenting a sequence. Numbers map directly to the steps in any accompanying written instructions, making the visual guide usable as a standalone reference. Keep the number of annotations per image low — two or three focal points per capture is a practical ceiling. When a process requires more steps, use multiple images rather than crowding a single one. Consistent color coding across a document set helps readers build pattern recognition quickly: red for errors or incorrect states, green for correct or completed states, blue for navigation elements. Adding a one-sentence caption below each annotated image reinforces the key point and makes the visual accessible on small mobile screens where annotation text can be hard to read. For teams building a library of reference captures, naming conventions matter as much as annotation quality. A file named `2026-04-returns-process-step-3.png` is findable; `Screenshot (47).png` is not. ## How to choose a screenshot tool for your team The five communication applications above have different technical requirements, and the right tool depends on which use cases your team needs most. **For SOP documentation and operations manuals:** Look for annotation layers (arrows, numbered callouts, text boxes), cloud storage with folder organization, and the ability to share as a linked file rather than an attachment. Version history is useful for teams that update their operations manual regularly. **For bug and issue reporting:** Screen recording with audio narration covers cases where a single capture cannot convey the full sequence. Tools that record a specific window rather than the entire desktop produce smaller, more focused clips. Look for shareable links rather than large file downloads. **For frontline and deskless teams:** Mobile capture support is essential. Tools that require a desktop browser eliminate a significant portion of non-desk workers from the workflow. Offline access — or at minimum, low-bandwidth operation — ensures SOPs and step-by-step guides remain available in environments with limited connectivity. **For milestone and content sharing:** Simple screenshot-to-link workflows with no login requirement for recipients work best. The goal is frictionless distribution to stakeholders who may not share the same tool access. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how organizations are consolidating operational documentation tools into shared communication platforms, including how visual capture workflows fit into broader SOP and knowledge management systems. For teams managing internal communication strategy more broadly, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) outlines how leading organizations structure visual and written communication together. ## What changes when visual communication becomes a standard workflow Screenshot tools add the most value when they are part of a consistent workflow rather than an ad hoc fix. The organizations that see the largest productivity and retention gains from visual communication do a few things consistently: they store captures in a findable, shared location; they establish annotation conventions so documents are readable across teams; and they connect visual documentation to the systems where work actually happens rather than distributing it through email. The $4,400–$15,000 average cost to replace a single frontline employee (a range documented in frontline workforce retention research) reflects how much turnover costs in aggregate. A significant portion of that cost is rework: re-training, re-explaining, re-documenting what should already be available. Screenshot-based SOPs and onboarding guides reduce that rework by making institutional knowledge visible and accessible rather than locked in any one person's inbox. The five use cases above — SOP documentation, onboarding guides, issue reporting, milestone sharing, and content direction — cover the scenarios where visual communication produces a measurable difference compared to text-only alternatives. Starting with one, building a small library, and establishing consistent annotation standards is a lower-lift first step than a platform migration, and it produces results that are immediately visible in reduced back-and-forth and faster resolution times. --- # Exploring Free Screen Capture Software Capabilities **Author:** MangoApps **Published:** 2024-05-03 **Category:** workplace-productivity Often when the word free is associated with software, we assume we get what we pay for – limited functionality. Not so in the case of screen capture software... # Free Screen Capture Software: What It Does, What to Look For, and How to Use It at Work Free screen capture software can do far more than take a basic screenshot. The best free tools let you annotate, share, and store captures — turning a simple image into a precise communication or documentation asset. This article explains what to look for, names specific free tools with capability comparisons, and covers the practical workplace uses that make screen capture worth building into your daily workflow. ## What Is Screen Capture Software? Every computer can take a basic screenshot using built-in keyboard commands, but those raw captures land in a folder with no annotation, no history, and no easy sharing path. Screen capture *software* adds an editing layer on top: you can draw arrows, add text callouts, highlight regions, blur sensitive data, and generate a shareable link — all before the image leaves your screen. The distinction matters because the editing and sharing layer is where the productivity value lives. A raw screenshot explains nothing on its own. An annotated, shared capture with a clear callout can replace a five-paragraph email. ## Which Free Screen Capture Tools Are Worth Using? The tools below are free (or have a fully functional free tier) and cover the core capabilities most teams need. ### Greenshot (Windows) - Captures full screen, active window, or custom region - Built-in annotation tools: arrows, text boxes, highlights, blur - One-click export to clipboard, file, printer, or email - Lightweight install; no account required - Best for: individual contributors who need quick annotated captures without cloud storage ### ShareX (Windows) - Captures screen, records video, and supports scrolling capture for long pages - Extensive annotation toolkit including step-numbering (useful for SOP creation) - Built-in image host and URL shortener; integrates with Imgur, Dropbox, and others - Fully open-source and free with no feature limits - Best for: teams building operations manuals or step-by-step instructions who need numbered annotations ### Flameshot (Windows, macOS, Linux) - Cross-platform with a clean, minimal interface - Annotation tools include arrows, text, blur, and pixelation - Captures copy directly to clipboard or save to disk - Active open-source community; no account or subscription required - Best for: mixed-OS teams that need a consistent tool across operating systems ### Lightshot (Windows, macOS) - Drag-select any screen region and annotate immediately - One-click upload to lightshot.net for a shareable URL - Simple two-toolbar interface; minimal learning curve - Free with no account required for basic use - Best for: teams that need fast shareable links without configuring cloud storage ### Snipping Tool / Snip & Sketch (Windows built-in) - Pre-installed on Windows 10 and 11; no download needed - Supports freeform, rectangular, window, and full-screen capture modes - Basic annotation (pen, highlighter, eraser) and direct share to email or clipboard - No history or cloud storage - Best for: occasional use when installing third-party software is not an option ## What Should You Look For in a Free Screen Capture Tool? Not every free tool fits every workflow. Evaluate options against these criteria: - **Annotation depth**: Can you add numbered steps, arrows, text callouts, and blur? Step-numbering is essential if you plan to build operations instructions or an operations manual. - **Sharing options**: Does the tool generate a shareable link, or does it only save locally? Link-based sharing removes the need to attach files to emails. - **Capture history**: Can you retrieve a capture you took last week? History access is the difference between a one-time tool and a reusable visual database. - **Cross-platform support**: If your team uses a mix of Windows and macOS, a cross-platform tool like Flameshot avoids compatibility gaps. - **Video/GIF support**: For demonstrating multi-step processes, a tool that records short clips (ShareX supports this) is more useful than a static image. ## How Screen Capture Fits Into Workplace Operations ### Building SOPs and Operations Manuals Screen capture is one of the fastest ways to build a living operations manual. Instead of writing step-by-step text instructions from scratch, you capture each screen state, annotate it with numbered callouts, and assemble the sequence into a document. This approach is particularly effective for software onboarding, compliance checklists, and any SOP operations workflow that involves a digital interface. The productivity case is concrete: according to Gartner's 2023 Digital Worker Survey, 47% of workers struggle to find necessary information at least half the time (Gartner, 2023). Visual, annotated SOPs stored in a searchable location directly address that gap by making process documentation easier to find and faster to follow. ### Communicating With Frontline and Deskless Workers Over 80% of the global workforce does not sit at a desk and cannot easily parse long written instructions (per MangoApps and Joinblink product research on deskless workforce framing). For field teams, retail staff, and frontline workers, a short annotated image or a numbered visual guide is far more accessible than a multi-paragraph email or a dense PDF. Replacing paper-based and scattered communication processes with digital visual tools supports faster operations and stronger team engagement. One case study of a frontline transport operation reported a 26% reduction in employee turnover after replacing paper processes and siloed communications with a single digital hub — a result that underscores how much the *format* of communication affects retention, not just the content. ### Reducing Tool Fragmentation Employees navigate 6–8 disconnected tools daily, creating fragmented communication that visual documentation can help reduce. When a screen capture generates a single shareable link that can be dropped into a chat message, a task comment, or an [employee communications platform](/solutions/employee-communications), it eliminates the round-trip of attaching files, waiting for downloads, and managing version confusion. ### Giving Clear Feedback on Design and QA Instead of writing a paragraph describing where a bug appears or what looks wrong in a mockup, a capture with an arrow and two words of annotation communicates the same information in seconds. This is especially useful in QA cycles, design reviews, and any workflow where the feedback subject is visual. ### Saving Time With a Concrete Frame The "save time" benefit of screen capture is real, but it is worth making specific. If employees are losing time to tool-switching across 6–8 disconnected systems, and a shareable annotated capture can replace a back-and-forth email thread, the time recovered per interaction is small but compounds across a team. The more useful frame is not "screen capture saves time" but "screen capture reduces the number of follow-up messages a single communication requires." ## Frequently Asked Questions ### Can free screen capture tools handle video as well as static images? Yes, but not all of them. ShareX supports screen recording and GIF capture in its free version. Greenshot and Lightshot are static-image-only. If your use case involves demonstrating a multi-step process — for example, recording how to complete a task in a new software system — choose a tool with video or GIF support from the start. ### How do I share screen captures with team members who don't have the same tool installed? The cleanest approach is to use a tool that generates a public or team-accessible URL (Lightshot and ShareX both support this). The recipient needs no software — they open a link in a browser. Alternatively, export captures as PNG files and attach them to your existing communication channels. If your team uses a central [employee app](/solutions/employee-app), uploading captures there keeps them searchable and version-controlled. ### Is free screen capture software secure enough for internal business use? For most internal documentation and feedback workflows, yes. The main risk is cloud-upload features: if a tool automatically uploads captures to a public server, sensitive screen content could be exposed. Greenshot and Flameshot default to local storage, which avoids this. If your team handles regulated data, disable or avoid cloud-upload features and store captures in your internal systems instead. ## The Bottom Line Free screen capture software is genuinely capable — the tools listed above cover annotation, sharing, history, and in some cases video, at no cost. The choice between them comes down to operating system, whether you need shareable links, and whether step-numbering for SOP or operations manual workflows matters to your team. ShareX is the most capable free option for documentation-heavy teams on Windows. Greenshot and Flameshot are the cleanest choices for teams that want annotation without cloud dependency. Lightshot wins on speed-to-shareable-link. For teams looking to go further — connecting visual documentation to a broader internal communications strategy — the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how organizations are structuring digital communication workflows across desk and frontline employees. --- # Boosting Employee Autonomy With AI Self-Service Hubs **Author:** MangoApps **Published:** 2024-04-05 **Category:** enterprise-ai The relationship between technology and employee autonomy within contemporary workplaces is a foundational aspect of how individuals engage with their roles ... # Boosting Employee Autonomy With AI Self-Service Hubs Employee autonomy is one of the strongest predictors of engagement and retention — yet most organizations still route basic HR tasks through email chains, help-desk tickets, and overloaded HR generalists. AI-powered Employee Self-Service (ESS) Hubs change that equation by giving employees direct, on-demand control over their own HR data, schedules, benefits, and learning — without waiting for a middleman. This article explains what ESS Hubs actually do, why the autonomy they create matters for engagement and culture, and what measurable outcomes organizations can expect when they deploy them well. --- ## What Is an AI-Powered ESS Hub? An ESS Hub is a unified digital platform where employees independently manage HR-related tasks — updating personal information, requesting time off, enrolling in benefits, accessing pay history, and completing onboarding or compliance training — without filing a ticket or calling HR. The "AI-powered" layer goes beyond a static portal. Instead of presenting every employee with the same menu, AI surfaces role-specific and location-specific content automatically. A warehouse associate sees shift-swap requests and safety SOPs; a remote knowledge worker sees project deadlines and learning paths. The platform learns from usage patterns and curates what each person is most likely to need next, turning a passive repository into an active assistant. This matters because employees already navigate 6–8 disconnected tools daily, and the consolidation value of a single, intelligent hub is significant. According to IDC, employees spend 2.5 hours per day searching for information — time that a well-structured ESS Hub can materially reduce. --- ## Why Traditional Self-Service Portals Fall Short Most organizations already have *some* form of self-service. According to Social Edge Consulting, 91% of organizations operate an intranet. The problem is adoption: only 13% of employees use their intranet daily, and nearly a third never log in at all (Social Edge Consulting). SWOOP Analytics puts average daily intranet usage at just six minutes per day. The gap between deployment and actual use comes down to three structural failures: 1. **Access barriers for deskless workers.** According to Emergence Capital, 80% of the global workforce is deskless — frontline, field, or shift-based employees who don't sit at a computer. Traditional HR portals require a company email address, a VPN connection, or a desktop browser. ESS Hubs that work without any of those — accessible via personal mobile devices with a simple login — extend self-service autonomy to the workers who need it most and are most often excluded from it. 2. **Tool fragmentation.** When HR data lives in one system, scheduling in another, and training in a third, employees give up and call HR instead. A unified [employee experience platform](/solutions/employee-app) eliminates that friction by consolidating tasks into one interface. 3. **No personalization.** A portal that shows every employee the same homepage is not self-service — it's a digital filing cabinet. AI-curated delivery, which surfaces the right policy, form, or training module based on role, location, and tenure, is what converts a portal into a tool employees actually return to. --- ## How ESS Hubs Expand Employee Autonomy ### Transactional Autonomy: Managing HR Tasks Without Waiting The most immediate form of autonomy ESS Hubs provide is transactional: employees can act on their own schedule rather than HR's. No-code workflow automation within self-service platforms can handle shift swapping, PTO requests, and routine approvals without IT involvement, reducing administrative bottlenecks that frustrate employees and consume HR capacity. Organizations that deployed a unified self-service app achieved 87–90% workforce engagement within the first few months of launch, according to MangoApps case studies including OU Health and the Kansas City Chiefs. That figure reflects not just adoption but active, recurring use — a meaningful contrast to the six-minute-per-day intranet benchmark. ### Developmental Autonomy: Learning on Their Own Terms Autonomy extends beyond HR administration. When employees can access [professional development resources and training](/articles/learning-and-development-strategy-embedded-in-daily-work) directly through the same platform they use for scheduling and benefits, learning stops being a separate initiative and becomes part of daily work. Organizations that deliver training and HR self-service via a mobile-accessible platform report 50% faster new-hire onboarding — a concrete operational benefit that compounds over time as headcount grows. Employee engagement training and courses embedded in an ESS Hub also address a common failure mode: learning that happens in a separate LMS that employees forget to log into. When the training surface is the same as the HR surface, completion rates rise because the friction of switching tools disappears. ### Informational Autonomy: Finding Answers Without Asking A significant share of HR help-desk volume consists of questions employees could answer themselves if the information were findable. AI-powered search within an ESS Hub — covering policies, SOPs, org charts, and FAQs — lets employees resolve questions in seconds rather than waiting for a response. This is where the IDC figure becomes concrete: recovering even a fraction of 2.5 hours of daily search time per employee translates directly to productivity and reduced frustration. A well-maintained [employee directory](/key-features/employee-directory) integrated into the hub further reduces the "who do I ask?" problem by making the right person findable without an org-chart PDF. --- ## The Psychological Case for Autonomy Autonomy is not just an operational convenience — it is a psychological driver of engagement. When employees have control over how they manage their work lives, they report stronger connection to their roles, lower stress, and higher willingness to take initiative. These effects compound: employees who feel trusted to manage their own HR needs are more likely to take ownership of their broader responsibilities. The inverse is also true. When employees must route routine requests through gatekeepers, it signals distrust and creates learned helplessness — the opposite of the proactive, innovative mindset most organizations want to cultivate. Employee engagement surveys and employee engagement questionnaires consistently surface autonomy as a top driver of satisfaction scores. Organizations that invest in employee engagement software that includes self-service functionality are addressing a root cause, not just measuring a symptom. --- ## Frontline Workers: The Autonomy Gap That Most Platforms Ignore The autonomy benefits described above are well-documented for desk-based employees. The gap is frontline and deskless workers — the 80% of the global workforce (per Emergence Capital) who are most likely to be excluded from traditional HR portals and least likely to have a company-issued device or email address. For these employees, autonomy is not a nice-to-have. It is the difference between feeling like a full member of the organization and feeling like an afterthought. ESS Hubs that support mobile access without a company email, offline functionality for low-connectivity environments, and multilingual interfaces extend self-service to the workers who historically had none. This is a meaningful differentiator when evaluating [workforce management](/solutions/workforce-management) technology. A platform that serves only the 20% of employees at desks is not an enterprise solution — it is a corporate-office solution. --- ## What Measurable Outcomes Should Organizations Expect? Concrete outcomes from ESS Hub deployments include: - **87–90% workforce engagement** within the first few months of launch (MangoApps case studies — OU Health and Kansas City Chiefs) - **50% faster new-hire onboarding** when training and HR self-service are delivered via a mobile-accessible platform - **Reduction in HR help-desk volume** as employees resolve routine questions through self-service search and AI-curated FAQs - **Recovered search time** against the IDC benchmark of 2.5 hours per day spent searching for information Organizations evaluating [modern HCM](/solutions/modern-hcm) platforms should ask vendors for deployment-specific engagement data rather than accepting generic satisfaction claims. The difference between a 13% daily intranet usage rate and 87–90% workforce engagement is not a product feature — it is a deployment and design question. For a broader view of where HR technology is heading, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers self-service adoption patterns alongside other shifts in workforce operations. --- ## Frequently Asked Questions ### How is an ESS Hub different from a standard HR portal? A standard HR portal is a static repository: employees navigate to it, find (or fail to find) what they need, and leave. An AI-powered ESS Hub is active: it surfaces relevant content based on role, location, and behavior; automates routine workflows without IT involvement; and integrates with scheduling, learning, and communication tools so employees don't need to switch platforms. The practical difference shows up in usage — static portals average six minutes of daily use (SWOOP Analytics); well-designed ESS Hubs drive daily active engagement. ### Does an ESS Hub reduce HR headcount? Not typically — and framing it that way misses the point. ESS Hubs reduce the volume of routine, low-value HR transactions (password resets, PTO confirmations, policy lookups) so HR professionals can focus on higher-value work: workforce planning, employee relations, and strategic initiatives. The administrative burden reduction is real; the headcount implication depends on how the organization chooses to redeploy that capacity. ### How do you measure whether an ESS Hub is actually improving autonomy? Three proxies work well in practice: (1) daily active usage rate compared to baseline intranet usage, (2) HR help-desk ticket volume before and after deployment, and (3) employee engagement survey scores on autonomy and empowerment dimensions. Organizations that track all three have a defensible picture of ROI. Those that track only adoption miss whether the tool is actually changing behavior. --- ## The Bottom Line AI-powered ESS Hubs are not a replacement for good HR practice — they are the infrastructure that makes good HR practice scalable. When employees can manage their own HR needs, access personalized learning, and find answers without waiting, they spend more time on the work that actually matters to them and to the organization. The data points to a clear gap between what most organizations have deployed (intranets with 13% daily usage and six-minute average sessions) and what is achievable (87–90% workforce engagement in documented deployments). Closing that gap requires three things: mobile-first access that includes frontline workers, AI personalization that makes the platform feel relevant rather than generic, and workflow automation that removes the bottlenecks that drive employees back to email. If your organization is evaluating where to start, reviewing your current [employee data](/solutions/employee-data) infrastructure is a practical first step — self-service is only as good as the data it surfaces. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) also provides a structured framework for assessing readiness and prioritizing deployment decisions. --- # How AI Transforms HR Into a Strategic Partner **Author:** MangoApps **Published:** 2024-04-05 **Category:** people-operations The role of Human Resources has evolved significantly over the years, from focusing predominantly on administrative tasks to playing a crucial strategic role... # How AI Transforms HR Into a Strategic Partner AI transforms HR into a strategic partner primarily by eliminating the administrative work that consumes most of HR professionals' time. When routine tasks — leave approvals, policy questions, shift swaps, benefits enrollment — are handled by AI-powered Employee Self-Service (ESS) Hubs, HR teams recover the time and attention required to influence business outcomes: workforce planning, talent development, employee engagement strategy, and organizational culture. According to IDC, employees spend an average of 2.5 hours per day searching for information. HR professionals face the same tax, often compounded by fielding those searches on behalf of others. The shift from administrative executor to strategic advisor does not happen gradually over time; it happens the moment HR stops being the bottleneck for information and approvals that employees could handle themselves. This article covers how AI-driven ESS Hubs work in practice, what HR teams gain when the admin load drops, and how to measure whether the transformation is actually happening. ## Why most HR teams are still trapped in administration The intranet infrastructure built in the 2000s was designed for information storage, not active use. According to Social Edge Consulting, 91% of organizations operate some form of intranet, yet only 13% of employees use it daily, and nearly a third never log in at all. SWOOP Analytics benchmarks average daily intranet time at six minutes. Systems that employees do not use cannot deflect HR inquiries. The ticket volume flows back to HR — the same policy questions, the same leave request confusion, the same onboarding gaps — and HR teams absorb it. That capacity cost is real and recurring. Each hour spent answering a question that the system should have answered is an hour not spent on workforce planning, manager coaching, or retention analysis. AI-driven ESS Hubs break this cycle by meeting employees in systems they already use, on devices they already carry, with answers that do not require a reply from HR. ## What AI automates inside an ESS Hub Modern AI-driven ESS Hubs go well beyond a searchable FAQ page. They handle complete workflows — not just information retrieval — across the most common HR interaction categories. No-code workflow automation covers the full cycle for routine approvals: shift viewing, shift swapping, PTO requests, and manager approvals can all be configured and executed within the platform without IT involvement. When a frontline employee requests a shift swap, the platform checks eligibility, notifies the relevant party, routes the approval, and updates the schedule — without HR touching the transaction. AI chatbots can handle up to 2,000 frequently asked questions with responses drawn directly from the organization's own policies and documents. The deflection is cumulative: the same platform that deflects routine onboarding questions in January continues deflecting benefits questions in November, building an always-current, always-accessible HR presence that does not depend on staff availability. Onboarding is where the compounding effect is clearest. When training content, compliance tasks, and HR workflows are digitized and mobile-accessible in one platform, onboarding speed can improve by 50% — new employees complete their required steps without waiting for HR coordination at each stage. The result is not a reduction in HR headcount. It is a transfer of capacity: the hours previously absorbed by transaction processing become available for the strategic work that transaction processing was crowding out. ## What HR does with the recovered time The term "strategic partner" gets used loosely. In practice, it means HR has the time and data to do four things that administrative overload prevents. **Workforce planning with actual data.** AI-driven ESS Hubs generate continuous data on how employees interact with HR systems — which questions get asked most often, where the gaps in documentation are, which teams show early signs of disengagement through reduced self-service activity. HR teams that read this signal can adjust strategy in near real-time rather than relying on an annual employee engagement survey cycle. **Talent lifecycle management.** [Learning and development programs embedded in daily work](/articles/learning-and-development-strategy-embedded-in-daily-work) are more effective than standalone training events — and they require HR to have the design capacity to build them. When administrative tasks no longer consume that capacity, HR can work directly with managers to identify skill gaps, design development tracks, and connect individual growth trajectories to business outcomes. **Employee engagement as a discipline.** Employee engagement is not a single survey. It is the aggregate of how employees experience every touchpoint with their organization — their ability to access information, manage their own HR needs, receive feedback, and see that feedback acted on. HR teams with recovered capacity can treat engagement as a continuous practice rather than an annual measurement event. [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) findings show the gap between engaged and disengaged workforces in revenue, safety incidents, and voluntary turnover — metrics that belong on HR's strategic agenda. **Organizational change management.** When HR is not managing the help-desk volume, they are available to partner with executives on the transitions that create that volume in the first place — technology rollouts, policy changes, restructuring. That is where the "partner" in strategic partner actually shows up. ## Reaching the workforce that doesn't sit at a desk According to Emergence Capital, 80% of the global workforce is deskless. In retail, healthcare, logistics, and field services, the frontline is the majority of the workforce — and it is the segment that traditional HR technology has consistently failed to reach. An HR platform that requires a company email address, a VPN connection, or a desktop login to access leaves that 80% without self-service capability. The administrative burden that ESS Hubs are supposed to deflect simply flows through other channels: managers absorb it, HR business partners absorb it, or the question goes unanswered and the employee guesses. Modern employee experience platforms address this directly. Frontline employees can enroll using a QR code, an SMS invitation, or a personal email address — no IT provisioning required. They access HR self-service, training content, shift management, and company communications from their own devices. A new associate can complete day-one paperwork from their phone before corporate credentials are issued. The adoption numbers reflect the design choice. MangoApps' work with OU Health achieved 87% workforce engagement within months of deploying a branded mobile HR app for clinical and administrative staff. Enterprises that build for the full workforce from launch consistently reach high adoption rates quickly, rather than climbing toward them over months. Designing access for everyone at the start is the difference between a platform with broad operational impact and one that serves office employees while the frontline continues working around the system. For organizations with shift-based or distributed workforces, this is not a feature consideration — it is a threshold requirement. [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) illustrates how mobile-first HR tools change daily operations at the front line. ## How to measure whether the transformation is happening The risk in any HR technology investment is that the platform gets used without the promised strategic shift materializing. HR automation can simply make administrative work faster without actually freeing the HR function to work differently. Three metrics indicate whether the transformation is real. **Ticket deflection rate.** If HR is still fielding the same volume of routine questions six months after an AI-driven ESS Hub goes live, the platform is not being used effectively. A well-implemented system should show a measurable reduction in HR ticket volume within 90 days, with the sharpest drop in the categories the platform was configured to handle — policy questions, leave requests, onboarding inquiries. **Time-to-productivity for new hires.** If onboarding workflows are digitized and accessible on mobile, new hire task completion rates should improve measurably. Tracking whether this improvement is happening tells you whether the platform is being used as designed. **HR capacity redirect.** The most important measure is the hardest to quantify but the most telling: Is HR actually doing different work? Are HR business partners spending more time with managers and less time answering benefits questions? Are workforce analytics being produced and acted on? The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) identifies data fluency and strategic workforce planning as the capabilities HR organizations are investing in most aggressively this year — the platform only matters if the time it creates is used on those capabilities. For organizations with larger deployments, the financial case becomes concrete. Enterprise-scale implementations have captured substantial cost avoidance by reducing turnover costs, accelerating onboarding, and lowering the per-ticket cost of HR resolution when tracked systematically across quarters. ## What HR teams need to make the shift stick Technology handles the deflection. The organizational change is the harder part. HR teams moving into a strategic role need three capabilities that administrative work tends not to develop. The first is data literacy — the ability to read workforce analytics and translate findings into recommendations an executive will act on. The second is change management fluency — the ability to design and lead organizational transitions, not just execute them. The third is business acumen — understanding the financial and operational context well enough to connect HR decisions to business outcomes. Organizations that invest in these capabilities alongside the technology see the largest returns. The combination of AI-driven automation and strategic capability development is not sequential — the automation creates the space for capability development that would otherwise be impossible to prioritize. The HR professional who spent Monday processing leave requests and Tuesday answering benefits questions cannot also develop a workforce analytics practice. The HR professional whose ESS Hub handles both by 8 a.m. can. ## The shift that makes everything else possible The administrative load that keeps HR teams reactive rather than strategic is not a fixed condition. It is a consequence of infrastructure choices — platforms that employees do not use, workflows that require HR involvement for approvals that could be automated, information systems that require a query to a human rather than a search in a tool. AI-driven ESS Hubs remove those infrastructure constraints. The organization's policies are accessible to every employee on every device, at any hour, without an HR ticket. Approvals that required a manager's email now complete automatically. The new hire who needed coordination across five systems now completes everything in one. When the infrastructure works for employees, HR works differently. The function that spent its capacity on information delivery and transaction processing now has the capacity to build the workforce the organization needs — and the continuous data to know what that workforce should look like. --- # Streamline Employee Lifecycle With Self-Service Hubs **Author:** MangoApps **Published:** 2024-04-05 **Category:** people-operations Careful management of the employee lifecycle is a pillar of organizational success. As HR departments grapple with the complexities of modern workforce manag... # Streamline Employee Lifecycle With Self-Service Hubs Per Social Edge Consulting research, 91% of organizations operate an intranet. Only 13% of employees use it daily. Per SWOOP Analytics, the average employee spends six minutes per day in intranet tools. The gap between having an information platform and one that people actually use is where most self-service strategies fail quietly — and without attribution. Employee self-service hubs emerged to close that gap. The premise is coherent: rather than expecting employees to navigate disconnected HR portals, file shares, ticketing systems, and paper forms, a unified hub provides a single interface for every lifecycle moment — from first-day paperwork through exit interviews. The premise is right. The execution is where organizations diverge sharply. This article examines what each stage of the employee lifecycle requires from a self-service hub, why most deployments underperform, and what organizations achieving 87–90% frontline adoption are doing differently. ## The access problem most ESS platforms were not built to solve Per Emergence Capital, 80% of the global workforce is deskless. They work in distribution centers, hospitals, retail floors, and field service environments. They do not have corporate email addresses, and many do not have company-issued devices. They access workplace information, when they can, through personal mobile phones. Most enterprise self-service platforms were built when "employee" meant "office worker with a corporate laptop." The design assumption was universal desk access, and most current platforms still reflect it. Organizations deploying these tools find strong adoption among salaried employees and near-zero engagement among frontline staff — the population most likely to need HR support, least likely to have time to seek it, and most directly connected to patient, customer, and operational outcomes. Per IDC, employees spend 2.5 hours per day searching for information. For a frontline worker on a six-hour shift, that overhead does not sit quietly in the background — it competes directly with time on the floor. The ESS hub that solves this problem is not a better-formatted HR portal. It is a mobile-first, personal-device-accessible platform that does not require a VPN, a corporate email address, or a workstation to use. ## Onboarding: from checklist to structured day-one experience The first 90 days determine whether a new hire builds operational context quickly or spends two months asking the same questions of different people. Per Social Edge Consulting research, nearly a third of employees never log in to their organization's intranet — a pattern that overlaps substantially with employees who later report a poor onboarding experience. An ESS hub configured for onboarding automates the administrative foundation: document submission, policy acknowledgment, benefits enrollment, payroll setup, and initial training scheduling are handled through guided workflows before or during the first week. For frontline workers without corporate email, mobile onboarding through a personal device eliminates the access barrier that otherwise produces a parallel paper process running alongside the digital one. The automation is not the differentiator. What separates effective ESS onboarding from a digitized version of the same friction is structured access to context: the new hire can identify their team, find their manager's contact, locate the policies they will be asked about in week one, and understand what success looks like in the first 30 days — without having to ask anyone. The platform's value is proportional to the quality of the information it surfaces, not just the speed of the forms it processes. ## Development: why workplace learning needs to live inside the hub This is where most ESS deployments leave the most capability unrealized. Employee development is typically treated as a parallel system — a learning management platform, a course catalog, or a video library maintained by L&D and accessed through a different URL. Employees context-switch between their daily work tools and their learning tools, and most choose not to make the trip. Nine competitors now embed workplace learning as a core ESS function: LMS integration, video learning, and learning experience platform capabilities housed inside the same hub employees use for HR transactions and operational communication. The structural distinction matters — [learning that lives outside the flow of daily work gets skipped](/articles/learning-and-development-strategy-embedded-in-daily-work) at far higher rates than learning accessible from the same screen where everything else happens. When training modules, development plans, upskilling resources, and role-specific learning paths are available through the same interface an employee uses to check a schedule or submit a PTO request, completion rates change for a direct reason: the friction between "I should do this" and "I will do this now" collapses to a single step. That is the architecture shift separating an ESS hub with embedded learning from a hub that links out to an external LMS. Knowledge capture belongs in this equation as well. Employees accumulate institutional knowledge through their work — process nuances, workarounds, informal expertise — that disappears when they transition roles or leave. An ESS hub that supports structured knowledge documentation and searchable peer content retains that knowledge rather than losing it each time someone moves on. ## Retention: what two-way communication actually requires The broadcast model is the default for most HR communication: policies are published, announcements are distributed, employees are expected to read and comply. Per Social Edge Consulting, 13% of employees use their intranet daily despite 91% of organizations operating one. A platform employees use only to find static documents does not build a usage habit. ESS hubs that improve retention metrics convert the broadcast model into a response loop. Per [Gallup's 2026 research on global workforce engagement](/articles/gallup-2026-state-of-the-global-workplace), information disconnection compounds over time — employees who cannot find what they need disengage, and disengaged employees exit. The structural answer is two-way capability: employees can complete engagement surveys, submit feedback, request time off, and receive recognition through the same interface, without switching to email or a separate ticketing system. The proof of concept appears in deployment outcomes. A MangoApps health system deployment achieved 87% workforce engagement within the first few months of launching a branded employee app with personal-device, no-email access. The contrast with six-minute-per-day average intranet usage is not a feature comparison — it reflects the difference between deploying a platform built for the workforce that exists versus one that assumes desk access. Feedback loops are where engagement becomes durable. When employees complete a survey, see a follow-up, and observe evidence that their input influenced a decision — within the same tool — the platform becomes something they return to. Without that loop, even a well-designed hub drifts back toward the passive repository problem over time. ## Offboarding: the lifecycle stage with the largest downstream footprint Offboarding is commonly under-configured because the cost of doing it poorly is diffuse and delayed. Access not revoked promptly creates compliance exposure. Institutional knowledge not documented leaves with the employee. Exit feedback not captured disappears into the void. Former employees who experienced a poor exit say so publicly in ways that shape future recruiting. A structured offboarding workflow addresses these systematically: automated access revocation checklists, equipment return routing, exit interview scheduling, and standardized feedback collection run through the hub rather than through a manual HR follow-up list. For teams managing high frontline turnover, consistency matters as much as the process itself — every departing employee moves through the same workflow, and accumulated exit data over time reveals patterns invisible in individual cases. The exit interview is the most frequently missed knowledge transfer opportunity in the offboarding stage. An ESS hub can surface prompts for departing employees to document what they know — process nuances, informal contacts, decision context — before their access is revoked. Employees who experience a structured, professionally handled exit are more likely to refer candidates, leave accurate public reviews, and consider returning. The last interaction with an organization shapes what someone says about it afterward. ## What determines whether an ESS hub reaches 90% adoption or 13% The features of mature ESS platforms have converged. Most cover onboarding automation, training access, engagement surveys, and offboarding checklists. The differentiation is in whether the platform was built for the workforce that actually uses it. Three questions cut through feature comparisons. First: how does the platform handle employees without corporate email addresses or company-issued devices? If the answer involves workarounds or separate processes, the platform was not designed for frontline access. A purpose-built [employee app](/solutions/employee-app) should reach frontline workers through personal mobile devices with the same capability available on the desktop version. Second: what are the documented adoption rates at frontline-heavy deployments in comparable industries? Ninety percent frontline adoption within six months is achievable from properly deployed mobile-first platforms — ask vendors for specific case deployments, not aggregate claims, and verify the workforce composition in those examples. Third: does workplace learning live inside the hub or require a separate login? Employees who must switch contexts to access training do not access training consistently. If learning sits beside the hub rather than inside it, the development use case will underperform from launch, not because of the content but because of the friction. ## How to evaluate ESS platforms against real operational criteria Per the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook), the evaluation criteria HR and operations leaders are applying in 2026 have shifted toward mobile-first access standards, embedded learning capability, and integration with HRIS and payroll systems that eliminates HR as a manual routing layer for routine transactions. The ROI case for a high-adoption ESS hub is direct: reduced information search time against IDC's 2.5-hour-per-day baseline, faster new hire ramp through structured onboarding, lower L&D overhead through embedded learning, and reduced voluntary turnover through continuous feedback loops. These outcomes compound — a workforce that finds information in two minutes rather than 2.5 hours, and that completes L&D within the tool it already uses, is not just more productive in individual tasks. It is less likely to disengage from the platform entirely. The organizations sitting at 13% daily intranet use are not failing for lack of a platform. They are failing because the platform they have was not designed for the employees who need it most — the 80% who are mobile, deskless, and will only engage if the system meets them where they are. --- # Revolutionizing HR With Self-Service Employee Hubs **Author:** MangoApps **Published:** 2024-04-05 **Category:** people-operations As HR teams navigate through an ever-expanding list of responsibilities—from recruitment and onboarding to employee engagement and retention—the need for eff... ## Revolutionizing HR With Self-Service Employee Hubs HR teams today manage an ever-expanding list of responsibilities—from recruitment and onboarding to employee engagement and retention. Employee Self-Service (ESS) Hubs answer that pressure directly: they are digital platforms that centralize HR services so employees can manage their own HR needs around the clock, without waiting on HR staff. The result is measurable—organizations that have launched branded self-service employee apps have reported 87% workforce engagement within a few months of going live. This article explains what ESS Hubs are, how they work, and how to evaluate and implement one successfully. ESS Hubs represent a significant leap forward in the digital transformation of HR processes. By centralizing access to HR services and information, these platforms allow employees to manage a wide array of tasks independently, from updating personal information and accessing pay stubs to requesting time off and enrolling in benefits programs. This shift towards self-service not only enhances operational efficiency by reducing the administrative burden on HR teams but also aligns with the contemporary ethos of autonomy and empowerment in the workplace. The impact of ESS Hubs extends far beyond operational efficiencies. At the heart of this digital transformation is a profound enhancement of the employee experience. By providing a user-friendly, accessible, and intuitive platform, ESS Hubs cater to the modern employee's expectation for immediacy and convenience. This on-demand access to HR services fosters a sense of empowerment among employees, enabling them to take charge of their HR-related needs without the delays and dependencies traditionally associated with HR processes. The result is a more engaged, satisfied, and productive workforce, which is pivotal in driving organizational success in today's competitive landscape. ## Challenges Faced by HR Teams Today HR departments are often inundated with a high volume of routine queries and administrative tasks that can be both time-consuming and repetitive. Add to this the pressure of providing personalized support to a diverse workforce and maintaining compliance and security in an increasingly remote or hybrid work environment, and it's clear why the traditional HR model is under strain. The information fragmentation problem compounds the burden. Employees navigate 6–8 disconnected tools daily, and per IDC, they spend an average of 2.5 hours per day searching for information. Despite this, per Social Edge Consulting, only 13% of employees use an intranet daily, nearly a third never log in at all, and the average daily time spent using intranet tools is just six minutes per day, per SWOOP Analytics. ESS Hubs directly consolidate that fragmentation into a single employee experience platform. With employees taking the lead on managing their HR-related transactions through an ESS, however, HR teams are afforded the bandwidth to focus on more strategic initiatives. This includes developing comprehensive employee engagement programs, crafting personalized career development plans, and implementing innovative retention strategies. The shift from administrative tasks to strategic focus not only enhances the role of HR within the organization but also contributes to a more dynamic, agile, and forward-thinking HR function. ## Understanding Employee Self-Service Hubs An ESS Hub is an online platform that serves as a centralized point for employees to access a wide array of HR-related services and information. Think of it as a digital employee support office that's open 24/7, without the need for physical presence or paperwork. It's where employees can go to find instant answers to their HR questions, complete essential HR tasks, and manage their employment-related needs with autonomy and ease. It also has a working understanding of company knowledge and training libraries, ensuring context-driven responses, and tailors its responses to the individual needs of each employee. ### How ESS Hubs Work The functionality of an ESS Hub can be broken down into several core components, each designed to streamline different aspects of HR operations: - **Self-Service Transactions:** Employees can update personal details, submit time-off requests, manage their benefits enrollment, and access their payroll information—all without needing direct intervention from HR personnel. ESS platforms can also automate shift viewing, shift swapping, PTO requests, and routine approvals through no-code workflows, eliminating manual HR touchpoints entirely. This self-service capability empowers employees while significantly reducing the administrative load on HR teams. - **Information Access:** ESS Hubs provide a centralized repository for important documents, policies, learning courses, and guides, among other things. Whether it's the employee handbook, safety protocols, or benefits information, employees have immediate access to the resources they need, whenever they need them. For a deeper look at how [modern HCM](/solutions/modern-hcm) platforms structure this access, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the latest shifts in HR technology adoption. - **Automated Workflows:** From onboarding processes to performance review cycles, ESS Hubs can automate and streamline complex workflows, including the sop operations that govern compliance and policy acknowledgment. This not only accelerates the execution of HR tasks but also ensures consistency and compliance across the board. - **Data Analytics and Reporting:** For HR professionals, ESS Hubs offer analytics and reporting tools that provide insights into workforce trends, operational efficiencies, and compliance risks. This data-driven approach supports strategic decision-making and continuous improvement in HR practices. ### The Impact of ESS Hubs on HR Operations The introduction of an ESS Hub into an organization's HR framework transforms operations in several key ways: - **Increased Efficiency:** By automating routine tasks and enabling employees to manage their HR needs independently, ESS Hubs significantly reduce the time and resources traditionally devoted to administrative HR tasks. - **Enhanced Employee Experience:** The convenience, autonomy, and empowerment that ESS Hubs offer lead to higher employee satisfaction and engagement. A positive employee experience is crucial for attracting and retaining top talent. - **Strategic HR Focus:** Freed from the burden of administrative tasks, HR teams can focus on more strategic initiatives like talent development, culture building, and workforce planning. This elevates the role of HR from administrative to strategic, contributing more significantly to organizational success. - **Data-Driven Insights:** The analytical capabilities of ESS Hubs equip HR professionals with valuable insights into employee behavior, process efficiency, and organizational health, enabling informed decision-making and proactive management. ## Improving HR Data Management and Compliance By digitizing forms, automating workflows, and centralizing data storage, ESS Hubs offer a streamlined approach to handling the vast amounts of information generated by HR processes. This digital transformation not only simplifies the collection, storage, and retrieval of employee information but also significantly improves data accuracy and reduces the risk of human error. Centralizing [employee data](/solutions/employee-data) in a single governed platform also makes audit preparation substantially faster. Secure, controlled access is a cornerstone feature of ESS Hubs, ensuring that sensitive employee information is protected according to the highest standards of data security. This is critical in complying with stringent data protection laws such as GDPR in Europe or CCPA in California, which mandate rigorous data handling and privacy measures. Furthermore, comprehensive audit trails provided by ESS Hubs enable HR departments to monitor and verify access to data, ensuring accountability and facilitating compliance with both internal policies and external regulations. Another significant advantage of ESS Hubs is their ability to streamline compliance-related processes. Whether it's ensuring that employees have completed mandatory training, managing certifications, or keeping track of policy acknowledgments, ESS Hubs automate and simplify these tasks. By integrating reminders and notifications, they ensure that both employees and HR professionals stay on top of compliance requirements, minimizing the risk of oversights that could lead to legal complications. ## Personalizing the Employee Experience At the heart of the modern workplace is the recognition of employees not just as workers, but as individuals with unique needs, preferences, and aspirations. By analyzing data on employee interactions, preferences, and feedback, ESS Hubs can deliver customized content, resources, and support, making each employee's journey through the workplace uniquely tailored and more fulfilling. The power of personalization extends to various aspects of the employee experience. From personalized learning and development plans that align with an individual's career goals—including employee engagement courses and employee engagement training delivered in the flow of work—to customized benefits packages that meet the specific needs of different life stages, ESS Hubs can transform how employees engage with their workplace. Moreover, personalized reminders for important deadlines, tailored health and wellness programs, and even individualized recognition and rewards all contribute to a more engaging and satisfying employee experience. For a practical framework on embedding [learning and development strategy into daily work](/articles/learning-and-development-strategy-embedded-in-daily-work), the principles apply directly to ESS-delivered training. Personalization through ESS Hubs also fosters a sense of belonging and inclusion among employees. By acknowledging and catering to diverse needs and preferences, organizations can create a more inclusive workplace culture that values and respects individual differences. This not only enhances employee satisfaction but also drives engagement and loyalty, key components of a productive and resilient workforce. ## Serving the Deskless Workforce Most ESS Hub discussions focus on desk-based employees, but per Emergence Capital, 80% of the global workforce is deskless—frontline workers in manufacturing, retail, healthcare, logistics, and field services who rarely sit at a computer. Per Social Edge Consulting, 91% of organizations operate an intranet, yet those platforms almost universally fail deskless workers who lack a company email address, a VPN connection, or a dedicated workstation. Modern ESS Hubs address this directly. Frontline employees can access self-service HR tools on personal devices without requiring a company email address, VPN, or a desk. New hire onboarding speed can improve by 50% when training and HR tasks are delivered through a mobile-accessible self-service platform. Shift viewing, shift swapping, and PTO requests become self-service actions completed in seconds from a phone rather than paper forms routed through a supervisor. The [workforce management](/solutions/workforce-management) capabilities built into a well-designed ESS Hub are especially consequential for hourly and shift-based teams. For scheduling-specific guidance, [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) illustrates how self-service tools reduce manager overhead in high-turnover environments. ## Facilitating Better HR Decision-Making The strategic value of ESS Hubs transcends operational efficiency and touches the very core of organizational success—decision-making. With comprehensive data analytics capabilities, ESS Hubs offer HR teams unprecedented insights into employee behavior, satisfaction levels, engagement trends, and more. Employee engagement surveys and employee engagement questionnaires can be deployed directly through the hub, closing the loop between data collection and action. These insights are instrumental in shaping policies, benefits, programs, and strategies that align with employee needs and organizational goals. Moreover, the aggregation of data across various HR functions within an ESS Hub facilitates a holistic view of the HR landscape. This comprehensive perspective enables HR leaders to identify interdependencies, evaluate the effectiveness of HR initiatives, and optimize resource allocation. By integrating feedback mechanisms, ESS Hubs also allow for the continuous refinement of HR strategies based on direct input from employees, ensuring that organizational policies remain aligned with employee expectations and evolving workplace dynamics. For all of these reasons, ESS Hubs do a great deal to improve HR's ability to function as a strategic partner within the business. ## How to Choose and Implement an ESS Hub Selecting an ESS Hub is not a technology decision alone—it is a workforce strategy decision. The following criteria help HR leaders evaluate options and avoid the most common implementation pitfalls. **Define the workforce you are actually serving.** If a significant share of your workforce is deskless or shift-based, prioritize platforms that support mobile-first access without requiring corporate email credentials. A platform optimized for desk workers will see the same low adoption rates that plague traditional intranets—six minutes of daily use per SWOOP Analytics—among frontline populations. **Audit your current tool stack before adding another.** Employees already navigate 6–8 disconnected tools daily. An ESS Hub that integrates with your HRIS, payroll, and learning systems consolidates that fragmentation; one that sits alongside them adds to it. Evaluate whether the platform can replace multiple point solutions rather than supplement them, reducing both licensing costs and IT overhead. **Prioritize no-code workflow automation.** The ability to automate shift swapping, PTO approvals, onboarding checklists, and compliance acknowledgments without engineering resources determines how quickly HR can reclaim administrative time. Platforms that require developer support for every workflow change create a dependency that slows adoption. **Measure adoption, not just deployment.** A successful ESS Hub implementation tracks daily active users, self-service transaction completion rates, and HR ticket deflection—not just go-live date. Employee engagement software that surfaces these metrics in a dashboard gives HR leaders the evidence needed to iterate and improve. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides current benchmarks for measuring workforce technology ROI. **Plan for change management from day one.** The most common implementation pitfall is treating ESS Hub rollout as an IT project rather than a people project. Communicate the "what's in it for me" to employees before launch, train managers to champion self-service behaviors, and use employee engagement surveys within the platform to capture early feedback and course-correct quickly. ## Conclusion: ESS Hubs Are the Foundation of Modern HR Employee Self-Service Hubs are not a peripheral HR technology upgrade—they are the operational foundation that allows HR to function as a strategic partner rather than an administrative bottleneck. By reducing the time employees spend searching for information (2.5 hours per day, per IDC), consolidating the 6–8 disconnected tools most employees navigate daily, and extending self-service access to the 80% of the workforce that is deskless (per Emergence Capital), ESS Hubs deliver measurable value across every employee segment. Organizations that have already made the shift report outcomes like 87% workforce engagement within months of launch. Those still relying on legacy HR portals or fragmented intranets face a compounding disadvantage: low adoption, high administrative overhead, and an employee experience that falls short of what today's workforce expects. The path forward is clear: evaluate your current HR tool stack against the consolidation and mobile-access criteria above, prioritize platforms that serve both desk-based and deskless employees, and measure success through adoption and ticket deflection—not just deployment. HR teams ready to explore what a purpose-built [employee app](/solutions/employee-app) looks like in practice will find that the technology exists today to deliver on every dimension described here. --- # Balancing AI & Human Elements in Workplace Personalization **Author:** MangoApps **Published:** 2024-04-05 **Category:** enterprise-ai As we race towards a future dominated by automation, striking the right balance between automated efficiencies and personalized experiences is crucial for fo... # Balancing AI and Human Elements in Workplace Personalization Most organizations know they need to personalize the employee experience. Fewer know how to do it without either drowning employees in irrelevant content or replacing human judgment with automation that feels cold and impersonal. This article lays out a practical framework for getting that balance right — then shows how the underlying technology makes it possible at scale. The short answer: effective workplace personalization requires preserving human decision-making authority where it matters most, governing AI content so it stays accurate, and ensuring every employee — including deskless workers — can actually access the experience you've built. --- ## Why Personalization Keeps Failing According to Social Edge Consulting, 91% of organizations operate an intranet, yet only 13% of employees use one daily, and nearly a third never log in at all. SWOOP Analytics puts the average daily time spent using intranet tools at just six minutes. These numbers don't describe a technology problem — they describe a relevance problem. Employees ignore tools that don't speak to their role, their location, or their actual questions. At the same time, IDC estimates that employees spend 2.5 hours per day searching for information. That's roughly 30% of a standard workday lost to friction that personalization is supposed to eliminate. When personalization fails, the cost isn't just frustration — it's measurable lost productivity. Two failure modes drive most of this: 1. **Generic content delivery.** A single intranet experience pushed to every employee regardless of role, department, or location. A warehouse associate and a finance analyst see the same homepage, the same announcements, the same links. 2. **Ungoverned AI content.** AI-generated or AI-surfaced content that becomes stale and ungoverned over time, actively eroding the personalized experience organizations set out to build. This is a failure mode that sharpens as AI adoption accelerates — the more content AI surfaces, the more critical governance becomes. According to Emergence Capital, 80% of the global workforce is deskless. Frontline workers — retail associates, nurses, logistics crews — are the majority of the workforce, yet most personalization strategies are designed for knowledge workers with corporate email addresses and VPN access. That gap is where engagement collapses. --- ## A Framework for Balancing AI and Human Elements Before choosing any tool, organizations need a set of operating principles that keep AI useful without making it feel alienating. The following four principles apply regardless of which platform you use. ### 1. Preserve Human Decision-Making Authority for High-Stakes Tasks AI should surface information, suggest next steps, and reduce search time. It should not make final decisions on performance reviews, disciplinary actions, compensation changes, or any outcome that materially affects an employee's career. Reserve those decisions for managers and HR professionals who can weigh context that no model fully captures. Practically, this means designing AI workflows with explicit human sign-off gates. An AI assistant can draft a performance summary or flag a policy question, but a human approves the output before it reaches the employee. ### 2. Require Human Sign-Off on Personalization Rules Role-based content rules — who sees which policies, which training modules, which announcements — should be set and periodically reviewed by HR or operations leaders, not left to drift based on algorithmic inference. When personalization rules are ungoverned, content becomes stale, irrelevant, or worse, incorrect. Build a review cadence into your governance model: quarterly audits of what each role group is seeing and whether it still reflects current business reality. ### 3. Govern AI Content as Rigorously as You Govern Policy Documents AI-surfaced content carries the same authority risk as a published policy. If an AI assistant tells an employee the wrong answer about their benefits or leave entitlement, the damage to trust is the same as a misprinted handbook. Treat AI training data as a living document: assign owners, set expiration dates, and build a process for updating source content when policies change. ### 4. Design for the Deskless Majority First If your personalization strategy only works for employees with a laptop and a corporate email address, it isn't a personalization strategy — it's a knowledge-worker perk. Frontline employees can access shifts, HR self-service, training, and IT requests in a single branded app without a corporate email or VPN. Building for that constraint forces a discipline that benefits every employee: simpler interfaces, faster load times, and content that gets to the point. --- ## Why Fragmented Tools Make Personalization Structurally Impossible Role-based personalization requires a unified data layer. If your HR system, your intranet, your training platform, and your communications tool don't share a common identity model, you cannot deliver a coherent personalized experience. Each system has its own user profile, its own content rules, and its own login — and the employee experiences all of them as separate, disconnected products. Fragmentation is the structural reason most personalization efforts fail. You cannot build role-based AI personalization on top of four separate systems that don't know about each other. A unified platform — one that syncs roles, departments, and attributes from your HRIS — is the prerequisite, not a nice-to-have. This also has a direct financial dimension. Replacing a disconnected frontline employee costs between $4,400 and $15,000 per person (per MangoApps product research citing industry reports). Personalization that actually reaches frontline workers isn't a UX investment — it's a retention investment with a calculable return. --- ## How MangoApps Applies These Principles MangoApps Employee Self-Service Hubs are built around the framework above. Rather than layering AI onto a generic intranet, the platform starts from a unified identity model — syncing roles and attributes from your HRIS via SAML 2.0 and OAuth 2.0 — and uses that model to govern what every employee sees, asks, and receives. **AI Assistants trained on your data, not generic web content.** MangoApps uses Retrieval-Augmented Generation (RAG) to train AI models on your company's own documents, policies, and knowledge base within secure, company-owned infrastructure. The result is an AI assistant that answers questions about *your* leave policy, *your* onboarding checklist, and *your* benefits — not a generic approximation. **Role-based content delivery.** When an employee opens the self-service hub, they see content scoped to their role and location. A warehouse associate sees shift schedules, safety procedures, and relevant HR forms. A finance analyst sees expense policies, compliance training, and department-specific resources. Neither sees the other's content by default. **Frontline access without corporate email or VPN.** Deskless workers can access the same self-service experience through a branded mobile app — no corporate email required, no VPN dependency. This closes the access gap that makes most intranet personalization strategies irrelevant to the majority of the workforce. **Governed content with audit trails.** Because the AI draws from a defined, governed content library rather than the open web, content owners can update source documents and immediately affect what the AI surfaces. Stale content doesn't persist invisibly — it's traceable and correctable. The outcomes from organizations that have deployed this model are concrete. CVS achieved 90% frontline adoption within the first six months of launching a personalized employee app. OU Health reached 87% workforce engagement within months of deploying a branded, role-based experience. These aren't engagement survey scores — they're active usage metrics from organizations where the majority of employees are deskless. For a broader look at how [employee engagement software](/solutions/employee-app) fits into a unified workforce strategy, the MangoApps employee app solution page covers the platform's full scope. Organizations evaluating intranet platforms can also review the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) for an independent assessment of how platforms compare on personalization, governance, and frontline access. --- ## What About Training and Employee Engagement? One of the most common follow-up questions: how does AI personalization connect to employee engagement training and development? The connection is direct. When an employee's self-service hub surfaces training recommendations based on their role, their current projects, and their completion history, training stops feeling like a compliance checkbox and starts feeling like a career resource. AI-driven personalization can recommend the right learning module at the right moment — after onboarding, before a promotion, or when a new compliance requirement applies to their department. This is where [employee engagement training](/articles/learning-and-development-strategy-embedded-in-daily-work) embedded in daily workflows outperforms standalone learning management systems. Employees don't log into a separate platform to find a course — the course finds them, in the tool they already use every day. For organizations building out this capability, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading HR teams are integrating personalized learning into their broader engagement strategies. --- ## What Comes Next: Predictive Personalization The current generation of AI personalization is largely reactive — an employee asks a question, the AI finds the answer. The next generation will be anticipatory: systems that identify patterns in work behavior and surface resources before the employee knows they need them. This could mean suggesting a break or a training module based on workload patterns, flagging a policy update to the employees it affects before they encounter a situation where they'd need it, or adjusting the content a new manager sees as their team grows. The governance principles above become more important, not less, as AI becomes more anticipatory. Predictive systems that operate without human oversight on their personalization rules will drift — and when they drift, they erode the trust that makes employees willing to use them at all. For a broader view of where workforce technology is heading, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the operational shifts shaping how organizations deploy AI across their workforce. --- ## The Takeaway: A Checklist for Getting the Balance Right If you're evaluating your organization's approach to AI and workplace personalization, use this checklist before selecting or configuring any tool: - [ ] **Unified identity model:** Does your platform sync roles and attributes from your HRIS so personalization rules stay current automatically? - [ ] **Governed AI content:** Do you have assigned owners and review cycles for the content your AI draws from? - [ ] **Human sign-off gates:** Are high-stakes outputs — performance summaries, policy interpretations, compensation data — reviewed by a human before reaching employees? - [ ] **Frontline access:** Can deskless employees access the personalized experience without a corporate email or VPN? - [ ] **Usage metrics:** Are you measuring actual adoption (daily active users, session length) rather than just deployment counts? - [ ] **Audit trail:** Can you trace what content an AI assistant surfaced to a specific employee on a specific date if a dispute arises? Organizations that can check all six boxes have the structural prerequisites for AI personalization that actually improves employee engagement — not just a technology deployment that looks good in a slide deck. The balance between automation and human judgment isn't a philosophical question. It's an operational one, and it has concrete answers. Start with governance, design for your deskless majority, and measure adoption — not just deployment. --- # Personalized Employee Experiences With AI **Author:** MangoApps **Published:** 2024-04-05 **Category:** enterprise-ai “One-size-fits-all" approaches to employee support and interaction are increasingly proving inadequate as enterprises recognize the need for personalized emp... # Personalized Employee Experiences With AI: Why Governance Is the Variable That Determines ROI A 30-point increase in employee engagement score in year one. $20 million in cost avoidance at a single enterprise deployment. Frontline adoption rates of 90% within the first six months. These figures come from documented deployments of AI-native employee experience platforms — and they share a common architectural trait: the AI was governed by design, not patched for compliance after deployment. The gap between a chatbot and a governed, role-scoped AI assistant is not conversational sophistication or model size. It is whether the system knows — structurally, not heuristically — who is asking, what they are authorized to see, and what response is relevant to their specific role, region, and language. Organizations that get that architecture right are the ones capturing the outcomes above. Organizations deploying general-purpose chatbots are adding another tool employees stop using after the first month. Per IDC, employees spend 2.5 hours per day searching for information that should be easy to find. Per Social Edge Consulting, nearly a third of employees never log in to the intranet at all, and only 13% use one daily. These numbers do not describe a workforce that lacks the interest in finding answers. They describe knowledge management tools that were not built to surface the right answer to the right person. ## Why generic AI fails the enterprise knowledge test General-purpose AI tools are designed for breadth. They draw from large data corpora with no inherent awareness of your organization's permission model, role structure, or the difference between a policy that applies to corporate staff versus hourly associates in a regional distribution center. That breadth creates three failure modes that are not edge cases — they are the default behavior of any AI that has not been scoped for your specific enterprise context. **Inaccurate answers** grounded in data outside your organization's verified knowledge base. A chatbot drawing from general sources will answer questions about HR policy, benefits eligibility, and safety procedures with confidence — and frequently with information that does not match your actual policies. **Permission violations** where employees surface content they are not authorized to see. In regulated industries — healthcare, financial services, government — this is not an inconvenience. It is a compliance exposure. **Role-irrelevant responses** that erode trust quickly. An hourly frontline worker asking about shift-swap procedures does not need a policy document written for corporate managers. Receiving one is the moment the tool stops being used. These failures persist because generic AI systems optimize for breadth, not for the governed, permissioned retrieval that enterprise knowledge management tools require. The fix is architectural, not cosmetic. ## The architecture that governance-first AI requires The technical foundation for personalized employee experiences is Retrieval Augmented Generation (RAG) — a method that grounds AI responses in a curated, permissioned corpus rather than a general-purpose model. RAG-trained assistants pull answers from your connected systems, respect existing access controls, and return role-aware results across integrated platforms, including Microsoft 365 and connected enterprise systems. But RAG is the retrieval layer. The governance layer is persona-based targeting: AI personalization scoped by role, region, brand, and language, with message acknowledgment tracking so organizations can verify that the right content reached the right employee group. This is meaningfully different from a chatbot that tailors a conversational response: - A compliance notice reaches only the employees in the relevant jurisdiction - A policy update is acknowledged by the specific workforce segment it applies to - A regional manager receives content in their preferred language without manual routing When permissions are enforced at the retrieval layer rather than applied after the response is generated, employees receive accurate, role-scoped information and organizations maintain the audit trail that regulated industries require. Centralized prompt governance and AI performance measurement add the operational layer: IT and HR teams can monitor what assistants are being asked, how they are responding, and where knowledge gaps exist. This turns AI deployment into an ongoing knowledge management practice rather than a one-time configuration. For organizations evaluating [employee experience platforms](/solutions/employee-app) in this space, the governance question — how permissions are enforced, not just claimed — is what separates architecturally sound implementations from feature-forward products that create compliance risk at scale. ## The frontline case: where governance is hardest and the stakes are highest Per Emergence Capital, 80% of the global workforce is deskless — in retail, manufacturing, healthcare, logistics, and field services. These workers typically lack corporate email addresses, assigned desks, or reliable access to traditional intranet tools. They are also the employees least served by generic AI chatbots, which implicitly assume a knowledge-worker context. A role-specific AI assistant for a frontline associate has a fundamentally different architecture from a corporate knowledge-worker tool: mobile-first delivery, multilingual support, content scoped by location, brand, and job function, and authentication that does not require a corporate email credential. The question "what is my shift this Saturday?" requires a different data path than "what is our leave accrual policy for salaried employees?" Governance-first platforms route each query to the correct knowledge scope — not to the broadest available corpus. The deployment evidence shows what this makes possible. Organizations like Santee Cooper, which deployed MangoApps across its geographically distributed workforce, demonstrate [how frontline adoption can reach every corner of an organization](/resources/santee-cooper-case-study) — a result that reflects what happens when the access barrier is removed rather than routed around. Retention math reinforces why this matters: replacing a disengaged frontline employee costs between $4,400 and $15,000 depending on role and industry. A platform that reaches 40% of the workforce through a desktop-only, corporate-email-gated intranet is not solving the retention problem. It is documenting it. ## What governed AI personalization actually delivers The business case for governance-first AI personalization is increasingly concrete. Organizations that have deployed platforms combining RAG-grounded knowledge retrieval with role-scoped AI assistants and persona-based content targeting have captured: - A **30-point increase in employee engagement score** within the first year of deployment - **$20 million in cost avoidance** at a single enterprise - **2.5 hours per day per employee recovered** in information search overhead — the IDC baseline that anchors the ROI math in nearly every platform evaluation - **Frontline adoption rates of 90%** within six months when mobile-first access is built into the architecture by default These outcomes require a knowledge management system that is scoped to the organization's data, enforces governance at the retrieval layer, and is explicitly designed to serve distinct employee personas — from senior knowledge workers to associates who may never open a laptop. Deploying a general-purpose chatbot and hoping employees adopt it produces neither the adoption rates nor the business outcomes above. The 91% of organizations that already operate an intranet (per Social Edge Consulting) are not starting from zero. The opportunity is to make that existing knowledge infrastructure actually usable — by connecting it to AI that knows who is asking, what they are authorized to receive, and what answer is most relevant to their role and location. ## Evaluating knowledge management tools for AI personalization For organizations actively evaluating platforms in this space, three questions separate governance-first products from feature-forward alternatives: **How are permissions enforced?** The answer reveals whether you get accurate, role-scoped results or a chatbot that occasionally surfaces the wrong policy document to the wrong employee. Permissions enforced at the retrieval layer are structurally different from access controls applied after the response is generated. **Does it reach your entire workforce?** A platform requiring corporate email credentials and a desktop browser does not reach the 80% of the global workforce that is deskless (per Emergence Capital). Test mobile access with frontline employees specifically, before evaluating feature depth. **How do you measure what the AI is actually doing?** Centralized prompt governance and AI performance monitoring are not optional for regulated industries. They are the operational infrastructure that makes AI deployment auditable and improvable over time. For independent evaluation criteria across platforms in this space, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides structured third-party assessment of personalization and governance capabilities. For context on how MangoApps positions within that landscape, [MangoApps' inclusion in a leading research firm's 2026 intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) covers the platform's standing on governance and personalization specifically. ## The knowledge management architecture problem most organizations haven't named The most common failure mode in AI personalization deployments is treating the 2.5-hour daily search overhead as a search problem. Better search returns better results from the same corpus. Governed AI personalization returns role-appropriate results from the corpus each employee is authorized to access — which is a fundamentally different operation, not a better version of the same one. Organizations that are improving employee engagement are not doing it by deploying faster search. They are closing the gap between what employees need to know and what they can actually find — and for the majority of the global workforce that is deskless, that gap is only closed when AI personalization is built with governance as the foundation, not added as a compliance layer after deployment. The organizations demonstrating $20 million in cost avoidance and 30-point engagement score lifts have solved an architecture problem, not a search problem. Every organization evaluating AI personalization tools today needs to ask the same question before comparing feature lists: does this system know who is asking — and what are they allowed to see? --- # Employee Self-Service Assistants Powered by AI **Author:** MangoApps **Published:** 2024-04-05 **Category:** ai-agents The efficiency and responsiveness of IT and HR services are paramount to organizational success. These departments are at the heart of the workplace, ensurin... # Employee Self-Service Assistants Powered by AI Employees spend an average of **2.5 hours per day** searching for information they need to do their jobs (per IDC). AI-powered employee self-service assistants directly cut that time by surfacing answers instantly — from HR policy questions to IT ticket submissions — without requiring employees to know who to call or where to look. This article explains how these assistants work, what they can handle, and what to look for when evaluating them for your organization. ## What an AI Employee Self-Service Assistant Actually Does An AI self-service assistant is a configurable chatbot trained on your company's own data — SOPs, HR policies, IT runbooks, benefits guides, and more. Employees ask questions in plain language and receive accurate, role-appropriate answers in seconds. When the assistant cannot resolve a request, it routes the employee to the right person or submits a ticket automatically. The practical scope is broader than most teams expect: - **HR queries**: leave balances, benefits enrollment, onboarding checklists, policy lookups - **IT support**: password resets, software access requests, ticket status updates, common troubleshooting - **Facilities and Procurement**: room bookings, supply requests, vendor contacts - **SOP operations**: step-by-step procedure guidance pulled directly from your internal knowledge base A well-configured assistant can handle up to 2,000 frequently asked HR and IT questions automatically, reducing live-agent escalations without custom development (per Beekeeper's chatbot FAQ capacity benchmarks). ## Why Traditional HR and IT Service Models Fall Short Despite the availability of digital tools, most organizations still rely on fragmented, manual processes for employee support. The numbers illustrate the gap clearly: - **91%** of organizations operate an intranet (per Social Edge Consulting), yet only **13%** of employees use it daily (per Social Edge Consulting). - The average employee spends just **six minutes per day** using intranet tools (per SWOOP Analytics). - **Nearly a third** of employees never log in to the intranet at all (per Social Edge Consulting). These figures point to a structural problem: traditional knowledge management tools are built around the assumption that employees will seek out information proactively. Most won't — especially frontline workers who are away from a desk. **80% of the global workforce is deskless** (per Emergence Capital), and those workers rarely have access to a corporate email address or a desktop device to navigate a conventional intranet. The result is a predictable cycle: employees ask colleagues instead of systems, HR and IT teams field repetitive questions, and institutional knowledge stays locked in documents no one opens. ## How AI Assistants Solve the Knowledge Management Problem Effective knowledge and knowledge management requires more than storing documents — it requires surfacing the right information to the right person at the right moment. AI assistants close this gap in several ways. ### Retrieval-Augmented Generation (RAG) on Permissioned Data Rather than relying on a general-purpose language model, enterprise-grade assistants use Retrieval-Augmented Generation to query your organization's own content. Responses are grounded in your actual policies, not generic internet data. Critically, your data stays on your infrastructure and is never used to train public models. ### Persona-Based Targeting Role, region, and language context determine what each employee sees. A warehouse associate in a Spanish-speaking market gets different self-service options than a corporate finance analyst — reducing noise, misdirected tickets, and the frustration of irrelevant results. Multilingual support is particularly important for distributed and frontline workforces: assistants that support inline translation across dozens of languages remove a significant barrier for non-English-speaking teams. ### No-Code Workflow Automation HR, IT, Facilities, and Procurement teams can build and update self-service workflows — forms, routing rules, escalation paths — without IT involvement. When a policy changes, the team that owns the policy updates the assistant. This is the practical definition of a tool for knowledge management that non-technical teams can actually maintain. ### Frontline-First Access Frontline workers can access self-service tools, submit PTO requests, and manage shift-related tasks without a corporate email address or desktop device (per Beekeeper's deskless worker self-service benchmarks). Mobile-first design is not optional for organizations with large frontline teams — it is the baseline requirement. For a broader view of how these capabilities fit into [workforce management](/solutions/workforce-management) strategy, the operational context matters as much as the technology. ## Governed AI: What Enterprise Deployment Actually Requires The term "AI assistant" covers a wide range of maturity levels. Enterprise deployments require governance that consumer-grade tools do not provide. **Key governance requirements:** - **Scoped knowledge**: the assistant answers only from content you have explicitly authorized, not from the open web - **Engine flexibility**: support for multiple AI engines (OpenAI, Gemini, Anthropic, Azure) so your organization is not locked into a single vendor's roadmap - **Agent routing**: when the assistant cannot answer, it escalates to the right human or system — not a dead end - **Performance measurement**: admins need dashboards showing which questions the assistant answered correctly, which it escalated, and where knowledge gaps exist - **Role-based access**: employees only see content and workflows appropriate to their role, preventing accidental exposure of sensitive HR or compensation data Without these controls, organizations face a different risk: employees using general-purpose generative AI tools in an unregulated environment, with no visibility into what data is being shared externally. ## Deployment Speed and Time to Value One of the most common objections to AI self-service projects is implementation complexity. Traditional IT-led customization projects can take months before a first assistant goes live. Modern no-code platforms can have a first live assistant running in days — not months — because the configuration layer is owned by the business team, not the IT department. The business case for moving quickly is concrete: - Organizations have reported **50% faster new-hire onboarding** when self-service training and digitized workflows replace manual HR processes - Enterprise self-service rollouts have achieved **90% frontline adoption within the first six months** - AI-powered employee experience and self-service consolidation has been attributed to **$20M in cost avoidance** at large enterprise deployments These outcomes depend on adoption, which depends on the assistant being genuinely useful from day one — not after a six-month tuning period. ## MangoApps AI Assistants: How the Platform Addresses These Requirements MangoApps AI Assistants are configurable chatbots that live within the MangoApps [employee experience platform](/solutions/employee-app), accessible from any device. They are trained on your company's data using RAG, support role-based access and persona-based targeting, and connect to your existing IT infrastructure without requiring a rip-and-replace of current systems. The platform's 15 years of deployment experience in traditional industries — retail, healthcare, manufacturing — shaped design decisions around non-technical user bases, security protocols, and the reporting functionality that enterprise IT and HR teams require before approving any new system. For HR teams specifically, the no-code environment means that when a benefits policy changes, the HR team updates the assistant — no ticket to IT, no delay between policy change and employee awareness. For IT teams, the assistant handles ticket submissions, status updates, and common troubleshooting autonomously, freeing staff for complex issues. Beyond HR and IT, any department that manages a data set employees need — Facilities, Legal, Procurement, Compliance — can deploy its own assistant without a technical background. This is what makes the platform a genuine tool for knowledge management rather than a point solution for a single department. MangoApps also maintains [modern HCM](/solutions/modern-hcm) integrations so that employee data powering the assistant — org structure, role, location, employment status — stays current without manual synchronization. For organizations evaluating platforms, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent analysis of how enterprise intranet and employee experience platforms compare on these dimensions. ## Frequently Asked Questions ### Can AI self-service assistants work for employees without corporate email or desktop access? Yes — and this is a non-negotiable requirement for any organization with a significant frontline workforce. Assistants must be accessible via mobile browser or app, without requiring a corporate email address for authentication. Frontline workers can access self-service tools, submit PTO requests, and look up shift information from a personal device. Given that 80% of the global workforce is deskless (per Emergence Capital), a desktop-only self-service strategy excludes the majority of workers in most industries. ### How do you measure whether an AI assistant is actually working? Admin dashboards should show: (1) question volume by category, (2) resolution rate — questions answered without escalation, (3) escalation destinations — which teams are receiving routed requests and why, and (4) knowledge gap reports — questions the assistant could not answer, which become a prioritized list for content updates. Without these metrics, "AI self-service" is a black box. With them, it becomes a continuously improving knowledge management system. ### What happens when the assistant doesn't know the answer? A well-configured assistant does not guess. It acknowledges the limit of its knowledge and routes the employee to the appropriate human contact or submits a support ticket on their behalf. The routing logic should be configurable by department — HR escalations go to HR, IT escalations go to IT — and the employee should receive confirmation that their request is in the queue. This is the difference between an assistant that builds trust and one that erodes it. ## The Concrete Next Step If your organization is evaluating AI self-service assistants, the most productive starting point is an audit of your current knowledge management tools: what content exists, who owns it, how current it is, and which employee questions are generating the most live-agent contacts today. That audit defines the scope of your first assistant and gives you a baseline against which to measure improvement. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading HR teams are structuring this kind of audit and what governance frameworks they are putting in place before deploying AI in employee-facing workflows. For organizations with frontline or distributed workforces, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) addresses the specific access, language, and device constraints that shape self-service design for non-desk workers. The goal is not to replace HR and IT teams — it is to give employees faster answers to routine questions so those teams can focus on work that requires human judgment. --- # AI-Powered Knowledge Harvesting for Organizational Wisdom **Author:** MangoApps **Published:** 2024-04-05 **Category:** knowledge-management Knowledge capture is a top priority for every company—ensuring that you retain the unique insights your employees collect over time is is crucial for establi... # AI Knowledge Management Tools: How AI Harvests Organizational Wisdom According to IDC, employees spend 2.5 hours per day searching for information they cannot locate. That figure translates to approximately 12 hours per week of lost capacity per person — before accounting for decisions made on incomplete information or work duplicated because no one knew it had already been done. For organizations where expertise is distributed across hundreds of people, dozens of systems, and multiple locations, the question isn't whether knowledge fragmentation costs money. The question is whether the gap between what employees know and what they can find is being treated as a solvable operational problem. AI knowledge management tools solve it by connecting existing data sources — documents, project archives, communication threads, HR systems — and making that content retrievable through a plain-language interface. The mechanism is Retrieval Augmented Generation (RAG): rather than generating responses from model training data, the system grounds each answer in documents retrieved in real time from the organization's actual knowledge base. An employee asking about the most common causes of delay in last quarter's projects gets a response drawn from real retrospectives and incident reports, not inference. This article covers how these tools work, what implementation requires, and how to evaluate whether a platform will deliver on its promise. ## Why knowledge stays trapped in most organizations Knowledge fragmentation is a structural problem, not a behavioral one. According to Social Edge Consulting, 91% of organizations operate some form of intranet — yet only 13% of employees use those tools daily, and nearly a third never log in at all. SWOOP Analytics benchmarks the average employee's daily time inside intranet platforms at six minutes. The causes are consistent across industries. **Tacit knowledge resists documentation.** The expertise employees develop through experience — judgment calls, pattern recognition, workarounds for known system quirks — doesn't fit into a structured form or database field. Traditional knowledge management tools were built for organized content. They have no mechanism for capturing what experienced employees know but haven't written down. **Siloed systems prevent cross-functional retrieval.** Information lives across HR platforms, project tools, team channels, email threads, and departmental file shares. Even when each system is individually searchable, there is no unified interface for questions that span all of them. **Low-adoption tools create knowledge deserts.** A knowledge base nobody uses is worse than no knowledge base at all — it gives leadership the impression that the problem is solved while expertise remains entirely in people's heads. According to Emergence Capital, approximately 80% of the global workforce is deskless, working in manufacturing plants, hospital wards, and retail floors where a desktop portal isn't accessible during the workday. When frontline access is an afterthought, knowledge tools serve only the desk-based minority. ## The financial cost of knowledge fragmentation Knowledge fragmentation has a direct price tag. Replacing a frontline employee costs between $4,400 and $15,000 depending on role and industry — and employees who are poorly equipped or poorly informed leave faster. Employees also lose more than four hours per week switching between disconnected systems, compounding the productivity drain that information silos create. For organizations considering whether to invest in a modern platform, the cost of legacy alternatives puts the comparison in context. Enterprise intranet deployments on traditional platforms can cost between $130,000 and $426,000 in the first year for a 1,000-user organization once customization, migration, and IT governance overhead are factored in. That investment often produces a system that digitizes existing silos in a new interface — and the six-minute-per-day engagement benchmark follows the organization from the old platform to the new one. ## How RAG-based AI knowledge management tools work Traditional large language models generate responses from training data, which creates accuracy problems for questions involving your organization's specific history, processes, or decisions. RAG addresses this by grounding each response in documents retrieved in real time from your actual knowledge base — so the AI's answer is only as accurate as what's in your systems. In practice, this means an employee can ask a plain-language question and receive a response drawn from the specific documents, reports, and logs relevant to that query, without knowing which system those records live in. RAG handles two categories of knowledge that keyword search cannot: **Unstructured content.** Emails, meeting notes, chat logs, and informal documentation contain substantial organizational knowledge that never makes it into a formal knowledge base. RAG-based systems can index and retrieve from these sources, not just from structured databases or formally published pages. **Cross-system retrieval.** When AI knowledge management tools integrate with existing HR, project, and communication platforms, employees get a single interface for questions that span the full organizational knowledge base. No one manually consolidates data first — the AI makes sense of what's already there. The baseline requirement for implementation isn't a perfectly organized library. It's connecting the systems that already exist and letting the retrieval layer do the work. A [knowledge management platform](/solutions/knowledge-management) built for enterprise deployment handles the integration layer while giving administrators control over which sources are indexed and which roles can access which content. ## What enterprise implementation looks like A knowledge harvesting rollout follows four stages. **Integration.** Connect the AI platform to existing data sources — document repositories, HR systems, project tools, communication archives. The scope of integrations determines how complete the knowledge retrieval will be from day one. Incomplete integration is the most common reason deployments underdeliver on their initial promise. **Configuration.** RAG-based systems learn from documents rather than requiring manual curation of a structured database. Configuration involves defining which data sources are in scope, which roles can access which content, and how the system should handle queries where the knowledge base has gaps. **Custom assistants by function.** Create department- or role-specific AI assistants scoped to the knowledge relevant for each function. An HR assistant surfaces policy documents, benefits information, and onboarding materials. An operations assistant draws on process documentation, shift logs, and incident reports. Functional scoping prevents employees from receiving irrelevant results and builds trust faster than a single general-purpose assistant can. **Rollout with a feedback loop.** Launch to a pilot group, observe how employees use the assistants, and refine based on actual query patterns. Organizations that design access for the full workforce from the start — including frontline employees on mobile without a corporate device or VPN — consistently reach 90% frontline adoption within the first six months. Traditional intranets take months to deploy, strain IT teams, and deliver static content that grows stale; AI-native platforms are faster to configure and improve continuously as usage data accumulates. ## Security, permissions, and governance in enterprise deployments Knowledge capture creates a security obligation. When an AI system can surface information across systems and roles, access controls become load-bearing. An employee in one department should not be able to query the AI and receive documents restricted to another. Enterprise-grade AI knowledge management tools address this through role-based permissions enforced at the retrieval layer — not just at document storage. When a user queries the AI, the system only searches documents that user is authorized to access, regardless of how the question is phrased. For regulated industries — healthcare, financial services, government — HITRUST and SOC 2 certifications, along with SAML 2.0, OAuth 2.0, and Active Directory integration, are prerequisites for enterprise procurement, not differentiators. A [content governance engine](/key-features/content-governance-engine) extends AI beyond retrieval into active knowledge hygiene. When the system flags content that hasn't been reviewed in 90 days, tracks version history, and surfaces documents where the underlying source has been updated, it prevents the knowledge base from accumulating the stale, contradictory records that erode user trust over time. Governance isn't administrative overhead — it's what prevents low adoption from recurring on the new platform. ## What results organizations report The American College of Radiology deployed MangoApps to centralize knowledge and communications across a distributed workforce spanning departments and locations. The deployment addressed a fragmentation problem the organization had been managing manually: ensuring that members of a distributed team could find policy guidance, committee decisions, and program documentation without escalating routine questions to a central team. When employees can self-serve knowledge queries, the operations overhead previously consumed by those escalations is recovered for higher-value work. Read the [American College of Radiology case study](/resources/case-study-american-college-radiology) for specifics on how the organization structured the rollout. The quantifiable ROI calculation for knowledge management tools involves three inputs. Search time recovered: IDC benchmarks 2.5 hours per day per employee — even a 30% improvement across a 500-person organization represents meaningful recovered capacity each week. Reduction in duplicate work: when teams can query a shared knowledge base before starting a project, they stop rebuilding what's already been done. Attrition-related savings: employees who are informed and equipped to do their work are substantially more likely to stay, and the replacement cost of $4,400–$15,000 per frontline departure makes even modest retention improvements financially significant. ## How to evaluate AI knowledge management tools Buyers evaluating this category need criteria that hold up under procurement review. The right evaluation tests integration depth (which existing systems does the platform connect to out of the box, and what does custom integration require), retrieval accuracy (how does the platform handle queries where the knowledge base has gaps or contradictions), mobile access design (is the frontline experience a purpose-built mobile interface or a port of the desktop), and governance tooling (what happens to content that goes stale, and who gets notified). Security architecture deserves specific attention before the evaluation closes. Organizations managing sensitive employee data need to understand how a platform handles role-based permissions, SSO and SAML 2.0 integration, and audit logging — not after go-live, when changing the access model is expensive. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) benchmarks current platforms across adoption, usability, integration depth, and AI capability — a structured starting point for building evaluation criteria that will hold up under procurement scrutiny. ## What sustains the investment after launch An AI knowledge management system that goes live without a designated content owner becomes stale. The AI retrieves what's in the knowledge base — it cannot create knowledge from nothing. If no one publishes updated process documentation, the system surfaces outdated versions until someone corrects the record. Effective governance defines who publishes, who reviews, and how often content calendars are updated for each functional area. It also includes a mechanism for identifying when the AI is returning low-confidence answers, which signals a gap in the underlying knowledge base that requires documentation, not query tuning. The questions employees ask the AI assistant are themselves a knowledge audit. Query logs reveal where organizational knowledge is missing, where documentation is unclear, and which topics generate the most follow-up questions. Organizations that treat this data as a continuous feedback loop — using it to prioritize what gets documented next — build a knowledge base that improves steadily rather than peaking at launch and degrading over time. ## The practical takeaway AI knowledge management tools deliver measurable results when three conditions are met: the right sources are connected at implementation, access is designed for the full workforce from the start including frontline and mobile users, and a named governance owner takes responsibility for content quality after launch. Organizations that meet all three conditions consistently see the adoption rates and productivity outcomes that justify the investment. The technology barrier has largely been removed — the remaining barriers are organizational. Scope the rollout to include everyone, assign a governance owner before go-live, and treat query logs as a continuous signal rather than a one-time deployment artifact. That combination is what separates a knowledge system employees trust from one they quietly stop using. --- # Conversational Enterprise Search: Transforming Accessibility **Author:** MangoApps **Published:** 2024-04-05 **Category:** knowledge-management For decades, companies have struggled to keep up with their employees’ data needs. For an enterprise file repository to be useful, it has to be easy to under... # Conversational Enterprise Search: Transforming Accessibility Most employees don't have a search problem — they have an information architecture problem. The files exist. The policies are documented. The answers are somewhere in the system. What's broken is the layer between what an employee needs to know and where that knowledge lives. Conversational enterprise search, built on natural language processing and retrieval-augmented generation, replaces that broken layer with an interface that understands questions the way people actually ask them — without query syntax, folder knowledge, or any prerequisite for technical literacy. Per IDC, employees spend 2.5 hours per day searching for information they cannot easily find. That's nearly a third of an eight-hour shift lost not to doing work, but to hunting for the context needed to do it. Conversational search doesn't marginally improve that number — it eliminates the category of "I couldn't find it" from most queries entirely, because employees no longer need to know how to frame a request for the system to understand it. This article covers what makes traditional search structurally inadequate, what conversational AI does differently at the technical level, how organizations with frontline workforces can deploy it without enterprise IT complexity, and what to evaluate before choosing a vendor. ## Why traditional search fails most organizations The default assumption in most enterprise search implementations is that employees know what they're looking for and can express it in a way the system recognizes. Boolean queries, folder hierarchies, metadata tags — these tools work reasonably well for knowledge workers who use them daily. For everyone else, they are a skill requirement disguised as a search bar. Traditional intranet deployments compound the problem. They require months of IT-led customization to stand up, deliver static content that becomes stale without governance enforcement, and require employees to navigate to a separate destination rather than surfacing information where work is already happening. SWOOP Analytics found that employees spend an average of six minutes per day inside intranet platforms — not a communication channel by any practical definition, but a reference destination that employees visit only when they remember it exists. Per Social Edge Consulting, 91% of organizations operate some form of intranet. Only 13% of employees use those tools daily, and nearly a third never log in at all. The institutional knowledge organizations have invested years documenting is effectively inaccessible to most of the people who need it on any given workday. ## The adoption ceiling most intranet investments hit The intranet adoption gap is not a user interface problem that a redesign will solve. It reflects a structural mismatch between how these tools were designed and how most employees actually work. Traditional enterprise search rewards employees who already understand the system — who know which folder the HR policy lives in, which keyword will return the right result, which department owns the document they need. For employees who aren't immersed in the system daily, the cognitive overhead of navigating it consistently outweighs the benefit of trying. They ask a colleague, they escalate to a manager, or they make a decision without the information they needed. That pattern compounds in ways that are measurable. Per the [Gallup 2026 State of the Global Workplace report](/articles/gallup-2026-state-of-the-global-workplace), employee disengagement carries documented costs in productivity, retention, and operational performance. Information access — or the chronic absence of it — is one of the structural drivers of disengagement that technology is positioned to address. ## How frontline and deskless workers are left out entirely Per Emergence Capital, 80% of the global workforce is deskless. Most enterprise search tools were designed for the other 20%. Frontline workers in healthcare, retail, manufacturing, and logistics are the population most dependent on having accurate, current information — and the population most consistently underserved by traditional search architectures. The barriers are systemic: no corporate email address, no company-issued device, no time between tasks to navigate a desktop system, and often significant language diversity that makes query-formulation even harder for a workforce that may not be working in their first language. Conversational AI search removes the query-formulation barrier entirely. Instead of asking an employee to construct a search string that a system will match against an index, it lets them ask a question in plain language — on a personal iOS or Android device, without a corporate email address or VPN — and receive a direct answer with a link to the source document. No login ceremony. No folder navigation. No prerequisite for technical literacy. Frontline employee replacement costs $4,400 to $15,000 per worker. Disengagement driven by poor information access — the experience of being uninformed, excluded from organizational knowledge, or needing to escalate a question that should be self-serve — is a direct driver of the turnover those figures represent. Closing the information access gap for deskless workers is an operational investment with a concrete cost-avoidance case, not a cultural initiative with diffuse returns. ## What conversational AI search does differently The technical foundation of modern conversational enterprise search is retrieval-augmented generation. Rather than matching keywords against an index, a RAG-based system retrieves relevant documents from a company's own data, uses them as grounding context, and generates a direct answer that cites its sources. The output is accurate to the organization's actual policies — not a ranked list of documents where the right answer might be buried on page two. This has two practical consequences that traditional keyword search cannot replicate. First, it means the search layer can span connected platforms — SharePoint, Google Drive, Box, Dropbox — through a single query interface. An employee asking where the latest safety procedure is stored doesn't need to know which system holds it. The conversational layer surfaces the answer regardless of source, eliminating the need for employees to understand the organization's file architecture before they can use it. Second, it enables purpose-built assistants scoped to specific domains. A People Finder trained on the employee directory answers "who manages the Atlanta distribution center and what's their direct line?" directly. An HR assistant scoped to benefits documentation answers open enrollment questions without surfacing unrelated content. That scope is what makes the tool trustworthy: employees quickly learn what each assistant knows and use it accordingly, instead of treating it as a general-purpose system where results are unpredictable. ## Security, governance, and what happens to your data Enterprise AI search fails when organizations treat it as a consumer-grade product wired to a third-party API. The governance questions matter acutely: which systems hold the underlying data, what access controls govern which employees see which results, and where queries and responses are logged. RAG-based systems that run against a company's own data corpus answer these questions directly. Search results inherit the same permissions that govern the underlying documents — an employee in one division does not surface files restricted to another, because the retrieval layer respects existing access controls. Queries remain within the organization's environment. Reporting surfaces which assistants are used most, which queries go unanswered, and where the knowledge base has gaps that need to be addressed. For organizations operating SAML 2.0, OAuth 2.0, or SSO environments, the search layer inherits enterprise identity with no separate credential management required. For regulated industries where compliance audit trails are mandatory, the query log is the audit record. This is the gap that most consumer-adjacent AI search tools leave open — and that purpose-built enterprise platforms close by design. ## Getting started: three questions to answer before choosing a vendor Most enterprise AI search evaluations stall because organizations treat vendor selection as the first step. Three questions should come before the RFP. **What is the coverage requirement?** If 80% of the workforce is deskless and doesn't have a corporate email address, the platform's device and authentication requirements determine whether deployment reaches those employees at all. A system that requires a company-issued device or SSO enrollment before an employee can ask a question will hit the same adoption ceiling as every intranet before it — regardless of how good the search experience is for the employees who can access it. **What data does the search system need access to?** A platform that federates across SharePoint, cloud storage, and an employee directory through a single query interface eliminates the "which system holds it" problem at the source. A platform that requires separate indexing configuration for each connected data source adds IT overhead that extends the deployment timeline significantly and often delays frontline rollout indefinitely. **What does deployment actually require from IT?** For organizations without large technical teams, the realistic implementation ask matters as much as the feature list. Platforms designed for enterprises with dedicated deployment resources are not the same as platforms built to stand up against existing infrastructure in days. First-year deployment costs for enterprise platforms like SharePoint can reach $130,000 to $426,000 for a 1,000-user organization — context for why the ability to graft AI search onto existing infrastructure without replacing it carries real financial weight. The [ClearBox 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) evaluates AI-capable intranet and [knowledge management](/solutions/knowledge-management) platforms against the criteria enterprise buyers use in formal procurement — integration depth, security posture, administration complexity, and total cost of ownership. It is a practical reference for building an evaluation framework that extends beyond product demonstrations. ## What results look like when the deployment works The business case for conversational enterprise search is specific enough to forecast before deployment begins. IDC's 2.5-hours-per-day figure is the baseline. A well-scoped conversational search layer targeting the most common query types — policy lookups, procedure checks, personnel information, compliance questions — reduces time-to-answer for those queries substantially, not by incrementally improving a search bar, but by eliminating the navigation process for well-covered topics. The metrics that matter most in the first 90 days are query resolution rate (how often employees receive a usable answer without re-searching), adoption rate by segment (do frontline workers engage at comparable rates to office staff?), and escalation reduction in adjacent channels (do HR inbox volumes and IT helpdesk tickets drop for the question types the system handles?). The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how organizations are measuring the operational impact of AI-enabled communication and knowledge tools — including the shift from activity metrics to outcome metrics that finance teams and executive leadership actually act on. Organizations that deploy well don't describe the result as a better search tool. They describe it as the first time information access worked equally well for the person at corporate headquarters and the person on the warehouse floor — in the same language, on whatever device they had, without any training required. That parity in timeliness, accuracy, and ease of access is what conversational enterprise search is built to deliver. --- # Risks of Unregulated Generative AI in Workplaces **Author:** MangoApps **Published:** 2024-04-05 **Category:** enterprise-ai Right now, most organizations are scrambling to figure out what to do about the sudden appearance of generative AI tools. While many organizations are eagerl... The IDC finding that employees spend 2.5 hours per day searching for information was already a problem before generative AI arrived. Shadow AI — the consumer ChatGPT accounts, the personal Gemini subscriptions, the unapproved tools employees quietly use to work faster — doesn't create the information chaos. It exploits a vacuum that was already there. Per Social Edge Consulting, 91% of organizations operate an intranet, yet only 13% of employees use it daily and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends six minutes per day in intranet tools. When the sanctioned system doesn't meet the need, employees find one that does — and in 2026, that alternative is increasingly a consumer AI tool with no enterprise controls. The risk is not that employees want to work better. The risk is that they're doing it outside your infrastructure, using tools that weren't designed for enterprise data handling, in ways you have no visibility into. ## What happens when employees adopt AI tools without approval? The pattern is consistent: an employee discovers that a free AI tool makes a time-consuming task — drafting a report, summarizing a policy document, analyzing a spreadsheet — significantly faster. They don't file a support ticket or ask IT for approval. They sign up, start using it, and tell a colleague. Within weeks, a team is routinely entering customer data, financial projections, or proprietary process documentation into a platform where data handling policies are opaque, training practices are unclear, and organizational controls are absent. The compliance exposure under GDPR, HIPAA, and similar frameworks is not hypothetical. Any system that processes personal data on behalf of an organization falls under the organization's regulatory obligations — regardless of whether IT approved it. An employee entering a patient's care summary into a consumer AI tool for administrative convenience is creating a potential HIPAA incident. The organization inherits a real liability while the employee is solving a real problem. The secondary exposure is equally concrete. Trade secrets, deal terms, pricing models, and strategic plans entered into external AI systems become inputs for models the organization has no contractual protection over. What employees perceive as a productivity shortcut is, in practice, an uncontrolled data outflow that most DLP tools aren't configured to catch. ## Why are frontline workers the biggest shadow AI blind spot? Per Emergence Capital, approximately 80% of the global workforce is deskless — the majority of workers worldwide don't sit at a computer during their shift. Healthcare aides, retail associates, warehouse supervisors, and field technicians appear lower-risk for the document-heavy shadow AI use that creates compliance exposure. In practice, they represent a more dangerous vector. Frontline workers are the least likely to have access to a sanctioned employee experience platform. They typically have no corporate email, no company-issued device, and no intranet access that functions on a personal smartphone. When they need a fast answer to a policy question, a quick translation, or help filling out a report, the consumer AI tool in their pocket is the only option available to them. Organizations navigating 6–8 disconnected internal tools create exactly the fragmentation that pushes frontline workers toward unsanctioned AI. A unified platform that reaches every employee on the device they already carry — without requiring a VPN, a corporate email, or a company device — eliminates the access gap that makes consumer AI the default alternative. Without that, any AI governance policy that applies only to office workers is covering roughly 20% of the actual risk surface. ## What compliance exposure does unmanaged AI actually create? Four categories of exposure are operationally relevant. **Data residency.** Consumer AI services process inputs on infrastructure outside organizational control. For organizations in regulated industries — healthcare, financial services, government contracting — this is a compliance issue regardless of what specific data was entered, because the organization cannot demonstrate where inputs were processed or how long they were retained. **Model training.** Some consumer AI services use input data to improve their models. Most enterprise users don't read terms of service carefully enough to know whether their inputs are retained. Organizations that have signed data processing agreements with enterprise AI vendors cannot make the same assumption about tools employees discovered independently. **Auditability.** Enterprise AI governance requires the ability to demonstrate what information was provided to an AI system, when, by whom, and what output was produced. Consumer AI usage produces none of that audit trail. In a compliance investigation, that gap is as damaging as the underlying data handling violation. **Consistency and decision integrity.** When multiple departments use different AI tools for similar functions — candidate screening, market analysis, risk assessment — the outputs are built on different models, calibrated against different benchmarks. The inconsistency doesn't surface until a decision is challenged. By then, the governance failure is already on record. For an independent benchmark of how governed employee experience platforms are evaluated against these criteria, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides third-party analysis across security, data residency, and compliance dimensions. ## How does fragmented AI adoption destroy the ROI case? Organizations don't just lose control when employees self-provision AI tools. They lose the ability to measure anything. The productivity gains from AI are real — but they're only measurable when usage flows through a governed platform with identity integration and usage logging. When a team reports they've cut report generation time by 40%, that figure is derivable from audit trails, before/after comparisons, and role-based analytics. When the same team is using a consumer AI tool without enterprise logging, the 40% gain is invisible to the organization — and so is any regression, compliance incident, or pattern of misuse. The IDC baseline (2.5 hours per day searching for information) is a governance problem that predates AI. Governed knowledge management tools with embedded AI can materially reduce that number — but only when the tool is integrated with identity, role-based access, and usage reporting. Consumer AI usage produces individual productivity gains that never aggregate into organizational intelligence. The organization can't demonstrate ROI, can't identify adoption gaps, and can't course-correct when outputs are inconsistent or wrong. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how organizations are structuring AI governance alongside broader workforce operations strategy — including what measurement infrastructure exists at organizations that have successfully moved from shadow AI to governed deployment. ## What does a governed AI deployment actually look like? The transition from unmanaged to governed AI doesn't require replacing all existing tools at once. Organizations that execute it successfully tend to follow a consistent sequence. **Audit current shadow AI usage first.** Survey employees across departments to identify which consumer AI tools are in use, what categories of data are being entered, and what tasks they're solving. This is a demand signal, not a punitive exercise. Every unsanctioned tool represents a need the organization hasn't met — and the audit converts shadow usage into a requirements list for the governed alternative. **Define the policy before deploying the platform.** Acceptable use policies need to arrive before the governed tool, not after. Employees who've used consumer AI tools without incident need to understand what they can and cannot enter into any AI system — sanctioned or not — and what regulatory exposure exists when those lines aren't observed. **Choose a platform with governance built in, not bolted on.** The distinction that matters is not which AI model the platform uses — it's whether AI capabilities are connected to organizational identity, role, and access controls. A governed employee experience platform links AI assistants to role-based knowledge sources, keeps outputs auditable, and ensures that what a logistics coordinator sees differs from what a finance director sees for reasons that are intentional and documented. MangoApps connects governed AI engines — including OpenAI, Gemini, Anthropic, and Azure OpenAI — trained on company data, positioning governance as a platform-native capability rather than a compliance policy layered on top of a consumer tool. **Prioritize frontline access explicitly.** A governance framework that covers only office workers leaves 80% of the risk surface unaddressed. The governed platform needs to be genuinely usable on a personal smartphone without corporate credentials — or frontline employees will continue using consumer AI tools because nothing better is available to them. For a concrete example of how a large organization moved its entire distributed workforce onto a single governed platform, see [how Santee Cooper's 'The Coop' builds connection across every corner of its workforce](/resources/santee-cooper-case-study) — including employees without traditional corporate device access. ## How should organizations respond when shadow AI is already widespread? Most organizations that begin an AI governance initiative discover that shadow AI adoption is already widespread. That's a diagnostic signal, not a disciplinary problem. The recommended response sequence: **Acknowledge the productivity need before restricting the tool.** Employees who adopted consumer AI tools did so because it made their work faster. Blocking access without explanation breeds resentment and drives usage underground. The message needs to be specific: "We're not restricting AI — we're governing it, and here's what we're providing instead." **Conduct a data exposure review.** Work with IT and legal to assess whether sensitive data has been entered into external AI systems. Determine whether any regulatory notifications are required under applicable frameworks. This step is uncomfortable but necessary before the organization can accurately assess its exposure. **Accelerate the governed deployment.** The fastest path out of shadow AI is a sanctioned alternative that meets the same need. A governed knowledge management platform with role-based AI assistants — integrated with identity systems employees already use — addresses the productivity need while keeping data within organizational infrastructure. **Measure from day one.** The governance case is made with data, not policy. Track adoption rates, time-to-answer metrics on AI-assisted queries, and compliance incidents. Organizations that move from unmanaged to governed AI need to demonstrate what changed — to employees skeptical of IT-imposed restrictions and to executives asking whether the platform investment was worth it. For HR and communications leaders building the people-side of this transition, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how AI governance intersects with employee communication strategy — including how to frame the shift from unsanctioned to governed tools without triggering the defensiveness that kills adoption. ## The governance gap is the real strategy risk The most direct read of the evidence: organizations that describe their AI strategy as "we're evaluating" while 91% of their workforce has access to consumer AI and only 13% logs into any sanctioned information system daily already have an AI strategy. It's running without them. The gap between the investment organizations have made in information infrastructure and actual employee usage — six minutes per day per SWOOP Analytics, nearly a third never logging in per Social Edge Consulting — is the vacuum consumer AI tools are filling. Not because employees are reckless, but because the tools available through official channels don't match the speed and accessibility bar consumer AI sets. Governing AI adoption means closing the underlying gap: building information access that reaches every employee on the device they actually carry, fast enough to compete with a consumer alternative. Organizations that close that gap gain three things: they eliminate the uncontrolled data outflow of shadow AI, they capture productivity gains that unmanaged usage makes invisible, and they build the measurement infrastructure that turns AI investment into demonstrable organizational value. The organizations that wait will spend the next few years auditing the same gap. --- # Build a HIPAA-Compliant Intranet for Healthcare **Author:** MangoApps **Published:** 2024-02-07 **Category:** healthcare Many intranet vendors claim to be HIPAA-compliant but lack the hard evidence to back it up. Here’s how to implement a secure and private healthcare intranet.... # How to Build a HIPAA-Compliant Intranet for Your Health System Healthcare IT leaders evaluating intranet vendors quickly run into a frustrating gap: vendors claim HIPAA compliance without demonstrating it, and the regulation itself offers little technical guidance on what "compliant" actually means for a communication platform. This guide covers the security architecture your intranet must have, the certifications that matter, the deployment model that works for frontline clinical staff, and the vendor evaluation framework that separates credible compliance from marketing copy. If you need a clear, auditable answer to the question "is our intranet HIPAA-compliant" — this is where to start. ## Why healthcare intranets face a higher compliance bar Most enterprise software is evaluated on performance and usability. For healthcare organizations, those criteria sit behind a prior question: does this platform create PHI liability? The stakes are concrete. HIPAA violations carry civil penalties ranging from $100 per violation to nearly $2 million per violation category under the highest tier — willful neglect without correction within 30 days of discovery. Beyond financial penalties, a PHI breach affects patient trust, accreditation standing, and physician recruitment in ways that can outlast the regulatory penalty. Healthcare is also a persistent target. Patient health information commands a higher price on secondary markets than financial data, which means health systems face adversaries with both technical capability and financial motivation. An intranet handling clinical communications, policy documents, or any workflow adjacent to patient data sits within that attack surface. The compliance challenge is compounded by workforce composition. According to [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology), 70 to 80% of the global workforce is deskless, about 2.7 billion people — and in healthcare, that proportion is higher still. Most clinical staff don't sit at corporate desktops, and many don't have company email addresses. Any intranet strategy that doesn't account for mobile-first, no-email access isn't just inconvenient: it creates compliance risk, because workarounds — personal messaging apps, printed binders, consumer file sharing — generate PHI exposure points outside any audit trail. ## What HIPAA actually requires from an intranet HIPAA's Privacy Rule and Security Rule operate at a principle level. The Security Rule requires "reasonable and appropriate" administrative, physical, and technical safeguards without specifying which technical measures qualify. That flexibility was intentional — Congress wanted the framework to remain relevant as technology evolved. The HITECH Act of 2009 added enforcement teeth and extended liability to business associates: the vendors who handle PHI on your behalf. This has a direct implication for vendor selection. Any intranet vendor that processes or stores PHI must sign a Business Associate Agreement (BAA) before the deployment begins. A vendor unwilling to sign a BAA cannot legally support a HIPAA-compliant deployment. That is a disqualifying condition, not a negotiating point. Where HIPAA's technical requirements are explicit, they cover three domains: - **Access controls** — only authorized users can reach PHI, and every access event is logged - **Audit controls** — hardware, software, and procedural mechanisms that record and examine activity in systems containing PHI - **Transmission security** — PHI transmitted over electronic networks is protected against unauthorized interception What HIPAA does not specify: encryption algorithms, authentication standards, or specific infrastructure configurations. That gap is exactly why third-party certifications matter in vendor evaluation. ## The security architecture your intranet must have A HIPAA-compliant intranet requires multiple security layers operating together. No single control is sufficient — the HIPAA Security Rule expects defense in depth across administrative, physical, and technical safeguard categories. **Zero-trust access controls.** Traditional perimeter security trusts users inside the network by default. Zero-trust inverts that assumption: every access request is verified regardless of where it originates or what device it comes from. For a healthcare intranet serving staff across multiple facilities and personal mobile devices, zero-trust is the architecture that matches how clinical work actually happens. **Role-based access controls (RBAC).** The HIPAA minimum-necessary standard requires that employees access only the PHI relevant to their job function. RBAC implements this at the application layer — a floor nurse should see care protocols for her unit, not billing records or executive HR documents. Documenting and maintaining role definitions is an ongoing compliance obligation, not a one-time configuration task. **Encryption at rest and in transit.** The HHS Office for Civil Rights considers AES-256 encryption the current appropriate benchmark for PHI protection. Unencrypted PHI is a compliance gap that auditors flag consistently, and breaches affecting unencrypted data carry elevated penalty exposure under HIPAA's tiered structure. **Multifactor authentication (MFA).** MFA is now a baseline expectation in any serious healthcare compliance review, and proposed 2023 HHS Security Rule updates would formalize it as a required rather than addressable specification for covered entities. **Logically isolated data storage.** PHI should not reside in shared infrastructure co-mingled with unrelated tenants. Healthcare-grade cloud deployments require logically isolated storage environments that prevent data exposure through infrastructure misconfiguration. **Comprehensive audit logging.** Every access event — login, document view, file download, failed authentication attempt — should be logged with a timestamp, user identity, and resource identifier. These logs are what make compliance audits tractable and breach investigations coherent. ## Evaluating vendors: what certifications actually mean The most common failure in vendor evaluation is accepting "HIPAA-compliant" as a self-description. Compliance is not a certification — it is a state of adherence that must be demonstrated, not claimed. Three categories of verifiable evidence should be part of every vendor assessment. **HITRUST CSF certification.** The Health Information Trust Alliance Common Security Framework is the most rigorous independent security certification designed for healthcare. HITRUST incorporates HIPAA, NIST, ISO 27001, and PCI-DSS into a single unified framework, validated by a third-party assessor. A HITRUST-certified vendor has demonstrably exceeded HIPAA's requirements, not interpreted them favorably. Certification requires a formal validated assessment — it is not self-reported. **SOC 2 Type II reports.** Request a SOC 2 Type II audit report dated within the last 12 months. Type II covers operating effectiveness over time, not just security design. For healthcare use cases, Type II is the standard — a Type I report alone is insufficient evidence of sustained control operation. **BAA terms and responsiveness.** A vendor who delays producing a BAA, includes unusual liability carve-outs, or treats the process inconsistently is providing diagnostic information about their compliance maturity. How a vendor handles BAA negotiation often reveals more about their operational discipline than their marketing materials do. For independent comparison of how platforms measure up on both security and usability dimensions, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides structured evaluation data that healthcare IT teams can use alongside their own compliance requirements. ## Frontline deployment: the access model most implementations get wrong Architecture decisions tend to be resolved in IT. The implementation failure usually happens during deployment — specifically in the assumption that clinical staff will access an intranet the same way desk-based employees do. According to IDC, employees spend an average of 2.5 hours per day searching for information. In a clinical environment, that search time has direct patient care implications: a nurse who can't locate the current version of a medication protocol wastes time and introduces error risk simultaneously. The adoption data from Social Edge Consulting points to a persistent structural problem. While 91% of organizations operate an intranet, only 13% of employees use one daily, and nearly a third never log in at all. In healthcare environments, that gap is often explained by access friction — the intranet requires tools clinical staff don't carry. The result is that compliance-relevant communications — policy updates, safety protocols, incident reports — don't reliably reach the people who need them. Effective frontline deployment addresses three specific gaps: **No-email login.** Staff who don't have corporate email addresses should be able to authenticate via phone number, employee ID, or SSO tied to existing HR systems. Requiring corporate email to access the intranet structurally excludes the majority of clinical workers before they ever reach the platform. **Offline access for critical content.** Clinical protocols, emergency procedures, and frequently referenced safety documents should be available on mobile with minimal latency. Network connectivity in clinical environments is often unreliable, and that unreliability cannot create a gap in access to critical information. **Push notifications with acknowledgment workflows.** Policy changes affecting clinical care require more than passive availability — they require acknowledgment workflows that generate an audit trail confirming staff have read the update. This satisfies the administrative safeguard requirement for policy dissemination and creates defensible documentation for regulators. The OU Health deployment achieved 87% workforce engagement within months of launching a platform that required neither corporate email nor VPN access for frontline clinical staff. That adoption rate reflects what changes when the access model is designed for the clinical workforce it actually serves, rather than retrofitted from a desk-worker framework. The American College of Radiology's experience illustrates a similar outcome. [Their deployment](/resources/case-study-american-college-radiology) achieved consistent engagement across distributed locations by removing the access friction that typically prevents clinical staff from adopting intranet tools as a primary communication channel. ## Building the implementation roadmap A HIPAA-compliant intranet deployment moves through four phases, each with distinct compliance verification gates. **Phase 1: BAA execution and security architecture review.** No data migration or configuration work should begin before the BAA is in place and the vendor's security architecture has been reviewed against your organization's specific compliance requirements. This is where you verify that the platform can actually meet your audit obligations — not after deployment, when remediation is expensive. **Phase 2: Role and access structure definition.** Working from your existing organizational role framework, define the access permissions that implement HIPAA's minimum-necessary standard. This work routinely surfaces gaps in how roles are currently documented — gaps that represent compliance exposure regardless of which platform you deploy. **Phase 3: Content migration and governance setup.** Migrating from legacy systems is the right time to retire outdated policy documents, establish content ownership, and implement review cycles that keep compliance-relevant content current. A [modern intranet platform](/solutions/modern-intranet) should include content governance tools — version history, scheduled review reminders, ownership assignment — that make that ongoing maintenance tractable at scale. Health systems running dozens of fragmented communication channels have used this migration moment to consolidate dramatically: the TeamHealth deployment, for example, brought more than 200 disparate systems into a single mobile-accessible platform, reducing both IT complexity and the compliance surface area simultaneously. **Phase 4: Launch, training, and audit log verification.** Go-live should include structured verification that audit logging captures the events your compliance team requires, that MFA is enforced across all user types, and that the access structure matches your role definitions. Staff training should address not just how to use the system but why the access controls exist — clinical employees who understand the compliance context are more likely to adhere to it than those who experience security requirements as unexplained friction. ## What compliance looks like after launch HIPAA compliance is not a project milestone — it is an ongoing operational state. The audit requirements that apply at launch continue indefinitely, which means your intranet's compliance posture needs to be monitored rather than assumed. Key indicators of a healthy post-launch compliance posture: **Audit log completeness.** Spot-check regularly that every access type is logged with the required attributes. Audit logs are useful for breach response and regulatory review only if they are complete and structurally consistent over time. **Access review cycles.** Role assignments should be reviewed on a defined schedule — typically quarterly — to catch employees who have changed positions or left the organization but retain access they no longer need. Automated deprovisioning tied to your HRIS is the most reliable control here. **Policy version currency.** If your intranet hosts clinical protocols, version history and review cycles for those documents must be enforced through the platform. The intranet should generate evidence that reviews occurred, not merely host documents without a governance trail. **Staff adoption metrics.** According to SWOOP Analytics, employees spend an average of six minutes per day using intranet tools. In a healthcare environment where the intranet is a compliance-relevant communication channel, sustained low adoption warrants investigation — it typically indicates that clinical staff have found workarounds, which create PHI exposure outside any audit trail. ## The compliance foundation worth building A HIPAA-compliant intranet is not the ceiling — it is the floor. Health systems that get operational value from their intranet investments treat compliance as a design constraint, not an obstacle. HITRUST certification, zero-trust architecture, no-email frontline access, and comprehensive audit logging are the prerequisites that make a healthcare intranet trustworthy. Once that foundation is in place, the platform becomes infrastructure for the clinical communication, policy distribution, and workforce engagement work that actually improves patient outcomes. For healthcare IT leaders assessing where their current platform stands against the field, the independent research in [MangoApps' inclusion in Forrester's Intranet Platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides a structured framework for comparing vendor capabilities alongside your own compliance requirements. The question is not whether to invest in a compliant intranet. It is whether the platform currently in place can demonstrate its compliance posture clearly enough to survive an audit — and whether clinical staff are actually using it. If the answer to either is uncertain, that uncertainty is the risk worth addressing first. For MangoApps' current certifications (HITRUST CSF, SOC 2 Type II, ISO 27001, FedRAMP ATO), HIPAA business associate agreement, and deployment options including private cloud and on-premise, see [mangoapps.com/security](https://www.mangoapps.com/security). For how the platform serves every hospital employee alongside clinical communication systems, see the [MangoApps healthcare page](https://www.mangoapps.com/industries/healthcare). --- # How Employee Experience Tools Enhance Workplace Evolution **Author:** MangoApps **Published:** 2024-02-07 **Category:** employee-experience The modern work landscape is ever-changing. Relationships between workers and their jobs, bosses, and home life have transformed immensely within the last hu... # How Employee Experience Tools Drive Workplace Evolution Workplace evolution is not a trend — it is the measurable shift in how organizations structure technology, environment, and culture to meet employees where they are. The right employee experience tools accelerate that shift by reducing friction, connecting dispersed teams, and giving every worker — from corporate desk to factory floor — a consistent, supported daily experience. This article explains what workplace evolution means in practice, which elements of employee experience matter most, and how specific tools address the gaps that hold organizations back. --- ## What Workplace Evolution Actually Means Workplace evolution refers to the progress an organization makes across four interconnected dimensions: technology, environment, employee satisfaction, and employee well-being. Each dimension has moved significantly over the past century, and each one is now directly influenced by the tools a company deploys. - **Technology:** Organizations once limited employees' online access and treated communication as a top-down broadcast. Today, social-media-style messaging, team workspaces, and mobile apps have replaced bulletin boards and email chains — but adoption is uneven. According to Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use intranet tools daily. The technology exists; the experience design often does not. - **Environment:** Remote, hybrid, and in-office arrangements are now standard options rather than exceptions. The challenge is creating a consistent experience across all three settings without requiring employees to juggle multiple disconnected systems. Employees lose over four hours per week switching between disconnected workplace systems, a productivity drain that compounds across large workforces. - **Employee Satisfaction:** Retaining employees is a direct cost issue. Replacing a frontline employee costs between $4,400 and $15,000, making retention-focused experience tools a direct cost-avoidance lever (per MangoApps frontline workforce product data). Satisfaction is not a soft metric — it has a measurable dollar value. - **Employee Well-Being:** Healthy work/life balance is now a baseline expectation, not a perk. Technology that keeps employees constantly reachable without boundaries erodes well-being. The goal is tools that make work easier during work hours, not tools that extend work into personal time. --- ## How the Modern Workplace Differs From the Past From the 1920s through roughly 1950, jobs were transactional — employers provided the minimum required to get work done, and employees provided labor. By the late 1950s, productivity became the primary employer focus, and efficiency drove most organizational decisions. Employee well-being was not considered an employer responsibility. By the 1980s and 1990s, companies began recognizing that engaged employees outperform disengaged ones. Perks like in-office daycare, free lunches, and flexible hours emerged as competitive hiring tools. Employee engagement — the short-term emotional connection to work — moved to the center of HR strategy. Today, the focus has shifted from engagement to **employee experience**: the full lifecycle from recruitment through offboarding, including every interaction, tool, and environment an employee encounters. Employee engagement describes how someone feels on a given day; employee experience describes the cumulative conditions that produce those feelings over time. The practical implication: organizations cannot improve employee engagement sustainably without addressing the underlying experience infrastructure — the tools, processes, and communication channels that shape daily work. --- ## The Deskless Workforce Gap Most Organizations Miss Most employee experience conversations focus on knowledge workers with laptops and corporate email addresses. That framing excludes the majority of the global workforce. According to Emergence Capital, 80% of the global workforce is deskless — working in retail, healthcare, manufacturing, logistics, and field services without regular access to a desktop computer. Traditional intranet deployments were built for desk-based employees. According to SWOOP Analytics, the average employee spends just six minutes per day using intranet tools — a number that drops further for frontline workers who may not have corporate credentials at all. Meanwhile, IDC research shows employees spend 2.5 hours per day searching for information, a figure that rises when workers lack a centralized, mobile-accessible hub. Addressing workplace evolution for the full workforce means delivering a mobile-first experience that frontline employees can access on personal devices without a corporate email address or VPN. When organizations close this gap, adoption outcomes shift materially — some large enterprise deployments have reported 90% frontline adoption within the first six months of launching a branded employee app. For a closer look at how frontline-specific tools fit into a broader workforce strategy, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the operational patterns driving this shift. --- ## Why Disconnected Tools Undermine Employee Experience One of the most common barriers to positive employee experience is tool sprawl. Organizations accumulate separate systems for communication, HR self-service, training, scheduling, and document management — and then expect employees to navigate all of them independently. IT teams manage 3–4x system redundancy, and employees pay the cost in time and frustration. The consolidation argument is straightforward: a single platform that delivers shifts, HR self-service, [employee engagement training](/solutions/employee-app), communications, and a resource library in one place eliminates the switching cost and reduces the cognitive load of daily work. Unification is not a convenience feature — it is a workplace evolution milestone that directly affects how employees perceive their employer. Traditional intranet deployments compound this problem by straining IT teams and producing static, ungoverned content that becomes stale without ongoing maintenance investment. A platform designed around active daily use — with personalized feeds, targeted communications, and mobile access — produces fundamentally different adoption outcomes than a document repository with a search bar. --- ## The Elements of Employee Experience Employee experience spans the entire employment lifecycle. The core elements are: - **Recruitment:** First impressions form before day one. The clarity and responsiveness of the hiring process shape how a candidate perceives the organization. - **Onboarding:** A structured onboarding process reduces time-to-productivity and sets the tone for the employee's relationship with company culture and tools. - **Company culture:** Alignment between an employee's values and the organization's stated mission affects long-term retention more than compensation alone. - **Procedures:** Processes that are easy to understand and consistent across teams reduce friction and build confidence. - **Technology:** The quality and accessibility of workplace tools directly affects how employees feel about doing their jobs. Poor tools signal that the organization does not invest in its people. - **Work environment:** Whether in-office, remote, or hybrid, a comfortable and well-resourced environment is a prerequisite for sustained performance. - **Colleague interactions:** Relationships with coworkers are among the strongest predictors of whether an employee stays or leaves. - **Offboarding:** A respectful offboarding process protects employer reputation and influences whether departing employees refer future candidates or return as alumni. --- ## Ten Practical Ways to Build a Positive Employee Experience ### 1. Provide the right tools for the job Employees who lack the tools to do their work efficiently will have a poor experience regardless of culture or compensation. Audit tool gaps regularly and close them before they become retention issues. ### 2. Invest in communication technology Knowledge sharing is more valuable than information hoarding. Up-to-date communication tools — chat, team workspaces, company-wide announcements — make open collaboration the default rather than the exception. ### 3. Run employee engagement surveys regularly Employee engagement surveys and employee engagement questionnaires give employees a structured channel to share feedback and give leadership actionable data. Surveys signal that the organization values employee input, not just output. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines how leading organizations are structuring feedback loops in the current environment. ### 4. Create channels for idea sharing Employees who can submit ideas, see them acknowledged, and watch them move toward implementation feel like contributors rather than resources. Structured idea-sharing tools make this process visible and trackable. ### 5. Build recognition into daily workflows Recognition should not require a special occasion. Embedding recognition tools into the daily workflow — tied to project completions, peer nominations, or milestone achievements — normalizes appreciation and reinforces the behaviors the organization values. ### 6. Design for physical and digital comfort The average person spends roughly 90,000 hours of their life working. Physical ergonomics matter for in-office employees; digital ergonomics — intuitive interfaces, fast load times, minimal friction — matter for everyone. Both deserve deliberate investment. ### 7. Destigmatize one-on-one conversations Managers who only meet with employees to address problems create an association between direct conversation and negative outcomes. Regular informal check-ins, focused on growth and positive feedback, change that dynamic. ### 8. Protect work/life balance actively Work/life balance is not self-enforcing. Organizations that set clear expectations around after-hours communication, offer flexible scheduling, and monitor workload distribution produce lower burnout rates and higher retention. ### 9. Keep all employees informed Company news, policy changes, and strategic updates should reach every employee — including frontline workers who do not sit at a desk. Employees who feel informed feel included; employees who feel excluded disengage. ### 10. Implement a unified digital workplace platform A single platform that consolidates communication, HR self-service, training, scheduling, and recognition eliminates the tool-switching cost and gives every employee — desk-based or deskless — a consistent daily experience. Organizations that have launched branded employee apps report engagement rates as high as 87% within the first few months of deployment. --- ## What to Look for in an Employee Experience Platform When evaluating an employee experience platform or employee engagement software, the capabilities that most directly affect workplace evolution outcomes are: - **Mobile-first access without corporate email requirements** — so frontline and deskless employees are included from day one - **Integrated communication tools** — chat, announcements, team workspaces, and company news in a single interface - **Employee engagement survey tools** — with analytics, templates, and admin controls that make running surveys operationally simple - **Idea and innovation modules** — structured channels for employees to submit, vote on, and track suggestions - **Recognition features** — tied to real work events, not just anniversaries - **A centralized resource library** — so employees can find policies, training materials, and HR documents without submitting a ticket - **AI-assisted content surfacing** — personalized feeds and natural-language search that reduce the 2.5 hours per day employees currently spend searching for information (per IDC) MangoApps delivers these capabilities in a unified platform. The [employee directory](/key-features/employee-directory) and broader platform features are designed to connect the full workforce — not just employees with corporate credentials. For organizations evaluating how MangoApps compares to other intranet and digital workplace platforms, [MangoApps' inclusion in a leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides independent context. --- ## Frequently Asked Questions About Employee Experience Tools ### How is employee experience different from employee engagement? Employee engagement describes how emotionally connected an employee feels to their work on a given day. Employee experience describes the cumulative conditions — tools, environment, culture, relationships — that produce or undermine that connection over time. Improving engagement without addressing experience is like treating symptoms without the underlying cause. ### What role does training play in employee engagement? Training and employee engagement are directly linked. Employees who have access to relevant employee engagement training and development opportunities report higher job satisfaction and are less likely to leave. Embedding learning into daily workflows — rather than scheduling it as a separate event — produces better retention of skills and stronger engagement outcomes. The article [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers this connection in detail. ### How do you measure whether employee experience tools are working? The most reliable indicators are adoption rate, survey response rates, and retention metrics. Adoption benchmarks — such as the percentage of employees logging in daily or completing onboarding modules — give HR and IT teams early signals about whether a platform is delivering value. Pairing adoption data with employee engagement questionnaire results and turnover rates creates a complete picture. --- ## The Bottom Line Workplace evolution is not a destination — it is an ongoing process of closing the gap between what employees need to do their best work and what the organization currently provides. The tools an organization deploys are the most direct lever it controls. The evidence is clear: intranet tools with low adoption rates, disconnected systems that cost employees hours each week, and platforms that exclude the 80% of the workforce without a desk are not neutral choices — they are active barriers to the employee experience outcomes organizations say they want. A unified employee experience platform that works on mobile, requires no corporate email for frontline access, consolidates communication and HR tools, and surfaces information through AI-assisted search addresses each of those barriers directly. The organizations that treat employee experience infrastructure as a strategic investment — not an IT procurement decision — are the ones that will retain talent, reduce replacement costs, and build the engaged workforce that drives business results. To understand how current workforce trends are shaping the tools organizations need, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) is a practical starting point. --- # 20 Inspiring Intranet Design Examples for Your Hub **Author:** MangoApps **Published:** 2024-02-07 **Category:** intranet Intranets come in all shapes and sizes. Choosing what style works best for your company can be daunting. How do you know what information to include, what fe... # 20 Intranet Design Examples to Inspire Your Work Hub ## Why design decisions determine whether anyone uses your intranet Per IDC, employees spend 2.5 hours every day searching for information they should already have access to. That number does not improve by making the same intranet look more modern — it improves when the intranet is designed around how employees actually work. Per Emergence Capital, 80% of the global workforce is deskless. Most intranet design guides showcase layouts built exclusively for employees at desks, which helps explain why, per Social Edge Consulting, nearly a third of employees never log into their company intranet at all, and only 13% use it daily. The design decisions that separate high-adoption intranets from abandoned ones are mostly invisible in screenshots: widget selection, role-based personalization, login barriers, and how quickly an employee can get from opening the app to finding what they need. The examples below come from the MangoApps platform and show how organizations across industries and workforce types have made those decisions. ## Homepage and dashboard intranet design examples The homepage is the most consequential design surface in any intranet. A dashboard that surfaces what each employee needs — and hides what they do not — reduces daily search time and eliminates the first reason employees stop using the tool: they cannot find anything in under 60 seconds. ### Manufacturing: search-first navigation CablInc leads with the search bar positioned at the top of the homepage before announcements or news. That choice communicates a clear architectural decision: employees come to this intranet to find something specific, and the first screen should support that behavior. Must-read posts keep compliance updates visible without requiring employees to look for them. Quick links to apps and workspaces reduce the number of clicks between arrival and action — critical in manufacturing environments where screen time per shift is limited. ### Retail: team visibility and resource access RetailCo's homepage centers on recognition and resources. The employee recognition widget surfaces coworker achievements across locations. Upcoming birthdays maintain interpersonal connection across distributed stores. A direct link to the company library — procedures, forms, marketing materials — puts resources one click away rather than two navigation levels deep. For multi-location retail, that proximity matters: employees in different stores need identical resources, and the homepage is the fastest distribution path. ### Healthcare: compliance and authenticated access MedHub places announcements top-left. In healthcare environments, that positioning is not aesthetic — regulatory updates and safety protocols carry patient risk when they go unread. The SSO integration on this homepage reflects a security decision as much as a convenience one: a single authenticated session connecting clinical tools, documentation, and communication reduces the shadow-IT workarounds that emerge when employees share credentials to move faster. For organizations navigating healthcare data governance alongside communication design, the [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study details how a large healthcare organization structured its intranet around both compliance requirements and clinical workflow speed. ### Airline industry: operational efficiency AirCo's homepage is built for employees who move between locations and need to access multiple systems quickly. Performance widgets, Outlook Mail integration, forms, and quick links sit side by side with a weather widget — not cosmetic, but operationally relevant for staff in aircraft operations roles. This example illustrates a principle that applies across industries: the most effective homepage widgets are specific to how that workforce actually operates, not the widgets that look best in a platform demo. ### Food industry: people discovery in distributed teams Garry Hansen Bakery's homepage leads with colleague discovery rather than corporate announcements. The My Coworkers widget makes finding a contact at another location the primary action. Important Contacts ensures management reach information is always visible. In a distributed food-service operation, knowing who to call at another location is often more immediately useful than reading last week's company announcement. ### Finance: bidirectional communication Orbit Trust Banking combines information density with engagement mechanisms. A stock widget sits alongside company posts, connecting employees to market context relevant to their work. The surveys widget gives employees a structured channel for providing feedback — not just receiving communications. Intranets that function only as one-way announcement channels sustain lower engagement over time than those with explicit mechanisms for employee input. ### Safety and compliance: community alongside governance SafetyFirst uses a horizontal drop-down navigation menu to maximize screen space while keeping all sections accessible — a deliberate choice in safety-critical environments where employees navigate compliance documentation regularly. Idea campaigns and work anniversary widgets balance the policy-heavy content load. Employees in roles that involve primarily regulatory content disengage from an intranet that shows them nothing else; this design accounts for that directly. ### SaaS industry: culture through media PeoplePulse Software leads with video content, employee spotlights, and social media links. Award nomination widgets and idea campaigns turn the homepage into a participation surface rather than a distribution channel. For knowledge-worker companies where culture is a retention factor, this design pattern outperforms traditional announcement-board layouts that mirror internal email. ## Frontline intranet design examples Per Emergence Capital, 80% of the global workforce is deskless. Most intranet design showcases address none of them — and this is where four competitors have recently built a significant editorial lead. Frontline intranet design operates under constraints that desk-based design does not: - Employees access the intranet on personal mobile devices, not company-issued hardware - No corporate email means login must work via phone number or employee ID - Sessions are typically seconds, not minutes — navigation must be immediate - Announcements that require scrolling get missed A frontline intranet served as a branded mobile app — without VPN or corporate email — removes the access barriers that explain most frontline adoption failures. Healthcare organizations using this approach have reached 87% workforce engagement within months of deployment. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how organizations across frontline industries are consolidating from fragmented tool stacks to a single mobile-first platform. Key frontline homepage design principles: - Role-specific widget sets displayed on login, not a generic homepage the employee must configure - Shift-relevant announcements surfaced automatically based on role and location - One-tap access to schedules, handoff notes, and compliance forms - Recognition visible within the first screen without scrolling The [MangoApps employee app](/solutions/employee-app) supports no-corporate-email login at scale — a prerequisite for any frontline deployment where most workers have never had a company-issued device or a work email address. ## Company and department site intranet design examples Company and department sites serve a different function than the homepage. They are the persistent, authoritative record of what the organization knows and how it operates. The homepage gets employees started; company and department sites answer the questions that come up during work. ### Government agency company site: cross-department transparency PNW's company site surfaces activity from Communications, HR, and Learning & Development in the same view. Cross-department visibility reduces information gaps that slow approval chains and duplicate effort. The ideas widget at the bottom of the page makes suggestion submission a standard part of how employees engage with company resources — not a special initiative that requires a separate channel or an invitation to participate. ### Healthcare company site: policies at the point of need MedHub adds a standalone Policies & Procedures page separate from the company homepage and general site. A clinician retrieving a protocol mid-shift needs to find it in under 30 seconds. The HR widgets — Q&A, training certifications, regulatory links — are positioned for a workforce where continued education is a compliance requirement, not an optional benefit. This is the same pattern that produces measurable results in clinical environments: separating governance content from general communications reduces information-retrieval time and improves protocol adherence. ### Finance company site: tools without friction Orbit Trust Bank organizes the company site around employee productivity. Quick links, software apps, department pages, and HR & IT resources are the primary content. Employees arriving at the company site typically need something specific; the design builds around that assumption rather than leading with corporate messaging. Feedback channels and social links appear on the page, positioned as secondary rather than primary content. ### Tech industry company site: recognizing contribution TechNow's company site pairs recognition widgets with a Now Hiring widget, making individual achievement and internal advancement visible in the same view. The CEO Corner adds a named voice to corporate communications. Institutional-sounding updates that originate from no one in particular get ignored more frequently than updates attached to a specific person with a title and a face. ### Housing industry company site: navigation clarity National Residences leads with search at the top of the company site — the same decision CablInc made on its homepage. The consistent presence of this choice across industries reflects a straightforward reality: employees do not remember where resources live. Consistent iconography, white space, and a limited widget count make this page scannable. Fewer, well-organized widgets consistently outperform a dense page where many widgets compete for attention. ### Hospitality company site: community within enterprise Oneal pairs practical resource links with a birthday widget, a story submission form, and a people widget that connects employees to colleagues directly. The learning widget keeps training accessible without requiring a separate platform login. For hospitality companies with high frontline turnover, intranet features that build interpersonal connection serve a direct retention function — employees with visible peer relationships disengage and leave at lower rates than those who feel anonymous within their organization. ## Department page intranet design examples Department pages are the most frequently neglected surface in intranet design. Organizations configure the homepage carefully, build a company site, and leave department pages mostly empty or maintained only when someone remembers to update them. The examples below treated department pages as a design problem worth solving. ### IT department: self-service before escalation ElectronicsCo surfaces FAQs, request forms, maintenance schedules, and policies before showing team contact information. The ordering is deliberate: self-service resources first, then escalation paths. Employees who can answer their own questions do not open support tickets. The team widget appears at the bottom — available when self-service fails, not competing for attention before the employee has tried it. ### HR department: answers and opportunity GreatHomes' HR page organizes around two things employees want from HR: answers to questions and visibility into opportunities. Quick links handle the questions. The Now Hiring and employee referral widgets address advancement — making internal mobility a visible part of the HR page rather than a process employees only encounter when they actively seek it out. ### Learning and development department: mission before resources This L&D page opens with a mission statement before listing courses and links. Employees who understand why a training program exists complete it at higher rates than those who encounter it as an undifferentiated item in a resource list. The calendar and Internship Week widgets create temporal anchors in what would otherwise be a static repository that rarely gets revisited. ### Support team department: structured resolution Horizon Loan Support centers the department page on the ticket submission form. One form widget, organized by category, is the primary action on this page. The FAQ section sits below the form, not above — because employees who open a support page typically want to file a request, not read FAQs. The people widget connects employees to specific personnel as a second-tier option, reducing informal workarounds without eliminating the human escalation path entirely. ## How to apply these examples to your intranet Intranet design examples answer the question "what could this look like?" The harder question is "which of these decisions apply to us?" Three questions do most of that filtering. **Who actually uses the intranet, and from where?** Per SWOOP Analytics, the average employee spends six minutes per day using intranet tools. Frontline workers typically spend less. If your workforce is primarily deskless, starting from a desk-first template and adapting it for mobile produces a second-rate mobile experience — start from mobile-first design constraints and work up from there. **What does an employee need to accomplish in the first 60 seconds?** Every homepage in these examples makes a design bet on what that task is. Some bet on search, some on announcements, some on resources. The bet should match your workforce's actual behavior in the current environment, not the platform's default configuration or what looks polished in a demonstration. **What in the current stack can be replaced?** Per Social Edge Consulting, 91% of organizations already operate an intranet — and nearly a third of employees never log in. Adoption failures are rarely aesthetic. They are access failures (employees without a corporate email cannot log in), relevance failures (the first screen shows nothing specific to this employee's role or location), and navigation failures (employees cannot find what they came for without already knowing where it is stored). For a benchmark comparison of how modern intranet platforms address these criteria across real deployments, the [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an analyst-level evaluation — a practical starting point before finalizing a vendor shortlist. --- # Employee Engagement Ideas for Healthcare **Author:** MangoApps **Published:** 2024-02-07 **Category:** healthcare In the dynamic realm of healthcare, engagement is not just a buzzword—it’s the lifeblood that fuels a high-performing work environment. Forged in the crucibl... In the dynamic realm of healthcare, engagement is not just a buzzword—it’s the lifeblood that fuels a high-performing work environment. Forged in the crucible of relentless shifts, demanding benchmarks, and the overarching aim of patient satisfaction, healthcare employee engagement can empower your system to excel. This guide, tailored for seasoned healthcare administrators, will unveil innovative ideas designed to transform your employee engagement strategies.As experts in your field, you understand the unique intricacies of the healthcare space; let us provide the insights to invigorate your team and elevate your operations.Why is Employee Engagement Crucial in Healthcare?In the dynamic and high-stakes environment of healthcare, where lives are on the line daily, employee engagement ascends beyond traditional notions of job satisfaction or morale. It forms the backbone of an efficient, patient-oriented healthcare system. Engaged employees in healthcare demonstrate greater proficiency in their roles, promote a more collaborative work environment, and directly influence patient satisfaction levels. In fact, fostering engagement is one of the best ways for any health system to reduce burnout.Highly engaged teams are more likely to exhibit strong communication practices and a deep commitment to their roles, which leads to safer patient handling, minimized medical errors, and improved patient outcomes. Moreover, engagement influences staff retention rates. In an industry where skills shortage is a pressing issue, retaining talent is crucial. Engaged employees feel valued and are less likely to move to competitor organizations, reducing turnover costs and ensuring continuity of care. For more on this, read about reducing nurse turnover.Further, engaged healthcare employees pave the way for innovative problem-solving and improved operational efficiency. They are more inclined to put forth ideas and suggestions, driving continuous improvement and adaptation in the fast-paced world of healthcare. In essence, employee engagement in healthcare isn’t merely a “nice-to-have,” but a fundamental pillar to healthcare institutions’ success.As we delve into healthcare employee engagement ideas, it’s important to remember the multifaceted nature of engagement. From technology and software to leadership and culture, numerous factors interact to shape the engagement landscape in the healthcare setting.The equation is simple: when healthcare employees are engaged, patients are happier. A committed workforce not only elevates patient satisfaction but also directly leads to decreased turnover rates. The ripple effect is evident – a positive, vibrant work environment fosters better healthcare outcomes.Innovative Healthcare Employee Engagement IdeasNow that we’ve established the importance of employee engagement in healthcare, let’s explore some ideas that can revolutionize your approach to engaging your workforce. These strategies are designed to drive real results in your organization and do not require any prerequisite technology (although we indicate where and how a healthcare employee app like MangoApps can help).1. Regular Feedback SystemsA culture of constant communication and transparent feedback is instrumental in fostering engagement and a sense of belonging among healthcare employees. Implementing regular feedback systems can be a game-changer for your organization, encouraging employees to voice their opinions, share insights, and feel heard.Consider developing two-way feedback systems, where not only can employees receive constructive assessments from their superiors, but they also have the platform to provide their feedback or suggestions. This can serve as an invaluable tool to identify areas of improvement, refine workflows, and inspire innovative solutions.Expanded Options With TechnologyRegular team meetings, one-to-one check-ins or anonymous suggestion boxes are some traditional ways to facilitate feedback. Leveraging digital solutions such as a HIPAA-compliant intranet platform can take this a step further by providing a seamless, real-time channel for feedback, fostering open communication across the organization regardless of shift patterns or physical location.Moreover, ensure that the feedback is actionable. Nothing disengages an employee more than feeling their feedback is falling on deaf ears. Showcase the direct impact of their suggestions by implementing viable ideas and acknowledging their contributions. This not only validates their efforts but promotes a sense of ownership among employees, encouraging them to remain invested in their roles and the overall growth of the organization.In essence, a regular feedback system can serve as a key driver of healthcare employee engagement, fostering a culture of openness, ideas, collaboration, and continuous improvement.2. Creating Space For Cross-departmental CollaborationCross-departmental collaboration is another cornerstone to building robust healthcare employee engagement. In the complex, interconnected ecosystem of healthcare, fostering an environment that promotes collaborative efforts across various departments can lead to improved communication, increased innovation, and overall enhanced patient care.A culture that encourages cooperation across different disciplines and roles helps break down siloes, facilitating a more holistic and comprehensive view of patient care. It enables different teams to leverage their unique insights and expertise, leading to enriched, patient-centered solutions.For instance, creating interdisciplinary teams for strategic projects or problem-solving tasks can stimulate creativity and innovation. This not only provides a platform for employees to learn and grow, but also drives a sense of camaraderie and mutual respect.The Role of TrainingAdditionally, implementing cross-departmental learning sessions can be a powerful tool for facilitating collaboration. These sessions could be opportunities for different teams to share their challenges, victories, and best practices. This not only aids in the exchange of knowledge but also fosters a sense of community and shared purpose.In the digital age, technology can significantly bolster these collaborative efforts. Platforms like MangoApps offer a suite of tools designed to foster real-time communication, project management, and knowledge sharing across the organization. From real-time messaging and team spaces to collaborative project management tools, these platforms can seamlessly bridge the gap between different departments, fostering a truly interconnected, engaged workforce.In conclusion, fostering interdisciplinary collaboration can significantly enhance healthcare employee engagement, driving a more integrated, efficient, and patient-centric healthcare system. By breaking down siloes and promoting a culture of collaboration, healthcare organizations can foster a more engaged, satisfied workforce, ultimately leading to improved patient outcomes.3. Mental Health and Wellbeing ProgramsMental health and wellbeing programs are among the main ideas in fostering healthcare employee engagement. These initiatives are essential in acknowledging the mental and emotional stresses healthcare workers often face in their line of work—many of the signs of physician burnout, for example, fall within this realm. By prioritizing their mental wellbeing, organizations can demonstrate a commitment to their employees, which in turn fosters a sense of loyalty and engagement.The first step to implementing these programs is to establish a supportive environment that openly talks about mental health. Encourage leaders to be open about the topic, hosting regular discussions, and providing resources that employees can access when they need help. This can greatly reduce the stigma around mental health and make employees feel more comfortable seeking the help they need.Mental Health BenefitsNext, consider integrating mental health services within your existing healthcare benefits. This could include providing access to therapists or counselors, offering mental health days, or providing resources for self-care practices. By making these resources readily available, you’re sending a clear message to your employees that their mental health matters.Moreover, consider implementing stress management programs. This could include mindfulness and meditation sessions, yoga classes, or workshops on coping strategies. These programs can equip employees with tools to manage stress and avoid burnout, which is particularly important in the high-pressure environment of healthcare.Another key aspect is to create a work-life balance. Encourage employees to take time off, restrict overtime, and avoid sending work-related communications during off-hours. This allows employees to recharge and come back to work feeling refreshed and motivated.Additionally, consider incorporating activities that promote team bonding and camaraderie. Fun activities, team-building exercises, or group wellness challenges can help create a positive work environment and foster a sense of belonging among employees.Lastly, remember that every member of your workforce is unique. Hence, adopting a one-size-fits-all approach might not yield the desired results. Try to offer a variety of programs and resources to cater to the diverse needs and preferences of your employees.In conclusion, mental health and wellbeing programs are integral to healthcare employee engagement. By taking proactive steps to support the mental and emotional well-being of employees, healthcare organizations can create a healthier, happier, and more engaged workforce, leading to improved patient care and outcomes.4. Open Communication ForumsOpen communication forums for ideas and concerns are a vital component of healthcare employee engagement. These platforms provide employees with the opportunity to voice their thoughts, ideas, and concerns, fostering an environment of transparency and respect. When employees feel heard, it significantly boosts morale and contributes to a healthier workplace culture.One of the ways to facilitate open communication is through regular town-hall meetings. These meetings provide a space for employees at all levels to engage in open dialogue about the organization’s direction, challenges, and successes. They also serve as a platform for leadership to address the concerns and queries of the staff, reinforcing transparency.In addition to town-hall meetings, having an open-door policy can significantly contribute to open communication. This policy encourages employees to communicate freely with management without fear of repercussions. It promotes trust and demonstrates to employees that their opinions are valued, which can greatly increase employee engagement.Promote Psychological SafetySimilarly, implementing suggestion boxes or online feedback forms can provide employees with a confidential avenue to voice their thoughts and ideas. This can be particularly effective for those who feel uncomfortable expressing their views in public settings. It’s key to ensure that every suggestion is reviewed and feedback is provided to demonstrate that every voice matters.Moreover, digital communication platforms like MangoApps can be leveraged to foster open communication. These platforms allow real-time communication and collaboration, providing employees with a sense of connection and cohesion. They also offer features like forums or channels for specific topics, allowing for focused discussions and idea sharing.In conclusion, open communication forums play a pivotal role in fostering healthcare employee engagement. By creating a culture of transparency and respect, organizations can improve employee satisfaction, efficiency, and overall organizational performance.5. Mentorship ProgramsMentorship programs are a powerful tool in promoting healthcare employee engagement. These programs pair less experienced employees with more seasoned colleagues, fostering an environment of learning, professional growth, and mutual respect. Mentors provide guidance, share experiences, and offer constructive feedback, helping mentees navigate the complexities of the healthcare industry.The first step in establishing a successful mentorship program is to identify potential mentors. Look for employees who demonstrate leadership qualities, have a wealth of experience in their respective fields, and possess a willingness to guide others. Equally important is ensuring that mentors understand their role and responsibilities – they’re not just supervisors, but coaches and facilitators.Similarly, it’s crucial to match mentors with the right mentees. This should not be random; instead, consider factors like career goals, skills needs, and personality traits. A good match can lead to more productive relationships and better outcomes for the program.Setting Clear ExpectationsOnce pairs have been established, it’s essential to set clear expectations for the mentor-mentee relationship. This might include establishing regular meeting times, setting goals for the program, and laying out what each party should expect from the other. Providing a clear structure can help ensure that both parties benefit from the mentorship.It’s also important to provide ongoing support for the mentorship program. This might include regular check-ins with mentors and mentees, providing resources for mentors, or offering training sessions to help mentors enhance their mentoring skills. Fostering a supportive environment increases the chances of a successful and impactful mentorship experience.To make your mentorship program even more engaging, consider implementing a recognition program. Recognizing the hard work and commitment of mentors and mentees can motivate participants and make them feel appreciated. This could be as simple as a shout-out in a company meeting, a certificate of recognition, or a small token of appreciation.Moreover, it’s crucial to evaluate the effectiveness of your mentorship program regularly. This can be done through surveys, feedback sessions, and tracking the progress of mentees. Collecting and analyzing this data can provide valuable insights into what’s working, what’s not, and where improvements can be made.In conclusion, mentorship programs are a powerful strategy for fostering healthcare employee engagement. They create an environment of learning and growth, improve job satisfaction, and lead to a more skilled and competent healthcare workforce. By investing in these programs, healthcare organizations can enhance employee engagement, improve patient care, and boost overall organizational performance.6. Recognition and Reward SystemsRecognition and reward systems are another essential aspect of healthcare employee engagement. Recognizing employees for their hard work, dedication, and achievements can significantly boost morale, increase job satisfaction, and foster a positive work culture.The first step in implementing an effective recognition and reward system is to identify what behaviors, values, or accomplishments should be rewarded. These could range from surpassing performance targets, displaying exceptional patient care, showing teamwork, or demonstrating a commitment to continuous learning. By rewarding these behaviors, you reinforce the values you want to see throughout your organization.Next, it’s important to diversify the types of recognition and rewards. Not all rewards have to be monetary. Recognition can come in many forms, from a simple thank you note to a spot in the company newsletter or a shout-out in a team meeting. Similarly, rewards could be as simple as an extra day off, a gift card, or a flexible work schedule. The key is to make the reward meaningful to the individual.Real-Time RecognitionMoreover, instant recognition can be highly effective. Rather than waiting for a formal review, acknowledging an employee’s achievement in the moment or soon after can make the recognition more impactful. Real-time recognition platforms, such as MangoApps, can be particularly beneficial for this, providing a visible, immediate, and memorable way to celebrate achievements.In addition to individual recognition, consider implementing team or department recognition. Celebrating team successes can foster a sense of unity and collaboration, promoting a positive work culture.Lastly, it’s crucial to ensure that recognition and rewards are fairly distributed. All employees, regardless of their role or level, should have the opportunity to be recognized for their contributions. This promotes a sense of fairness and inclusivity, which can greatly enhance employee engagement.In conclusion, an effective hospital recognition program can work wonders for healthcare employee engagement. By acknowledging and appreciating the hard work and dedication of your employees, you can foster a positive, engaging, and productive work environment.Acknowledging milestones and standout employees is critical. With technology, not only can we streamline this recognition, but we can also empower peers to commend each other. When recognition is linked with tangible rewards, motivation skyrockets.7. Feedback LoopsFeedback loops are vital to ensuring ongoing healthcare employee engagement. They provide employees with a platform to voice their thoughts, opinions, and suggestions, fostering a sense of involvement and ownership over their roles. Moreover, feedback loops allow for continuous improvement, as employees are often the best source of ideas for enhancing workflow, patient care, and overall organizational performance.The first step in creating an effective feedback loop is to establish a culture of open communication. Encourage employees to speak up and share their thoughts without fear of retaliation. This can be done by promoting a non-judgmental environment where all feedback, whether positive or negative, is appreciated and valued.Next, provide various channels for feedback. This could include regular one-on-one meetings with supervisors, anonymous suggestion boxes, digital platforms, or town hall meetings. Providing multiple avenues ensures that all employees, regardless of their comfort level, have an opportunity to voice their thoughts.Acknowledging Feedback Is CrucialOnce feedback is collected, it’s crucial to acknowledge it. Employees need to know that their feedback has been heard and is being considered. This could be done through a personal response, a general announcement, or a demonstration of action taken as a result of the feedback.Acting upon the feedback is, however, the most critical aspect of a feedback loop. While it may not be possible to implement all suggestions, showing that some changes are made based on employee input can significantly boost engagement. If a suggestion cannot be implemented, explaining the reasons can maintain trust and transparency.Feedback should also be a two-way street. Managers should provide employees with regular feedback about their performance, offering praise for achievements and constructive advice for areas of improvement. This helps employees understand their strengths, areas for growth, and the impact of their work, contributing to their engagement and job satisfaction.Finally, the effectiveness of the feedback loop should be regularly reviewed. This could involve surveying employees about their satisfaction with the feedback process or analyzing whether implemented changes have led to improvements.In conclusion, feedback loops are an integral part of healthcare employee engagement. They involve employees in decision-making, promote continuous improvement, and demonstrate that the organization values its employees’ input. By prioritizing feedback, healthcare organizations can improve their operations, boost employee morale, and ultimately, deliver better patient care.Employing user-friendly platforms such as MangoApps can greatly simplify the feedback process. These platforms allow for easy collection, analysis, and actioning of employee feedback, enhancing the effectiveness of feedback loops.Implementing These Ideas in Your Health SystemTo adopt these healthcare employee engagement ideas in your health system, it is necessary to take a holistic approach, focusing on both the individual and collective needs of your team. Here’s a step-by-step guide on how to develop your own engagement program:1. Understand your current stateBefore you can plan improvements, you need to understand the current state of employee engagement in your health system. Use tools like employee surveys, focus groups, and one-on-one interviews to gather insights about what’s working well and where improvements can be made. You’ll want to probe into areas such as communication, recognition, feedback, leadership, job satisfaction, and work-life balance. Using tools like MangoApps can help streamline this process, making it easier to collect and analyze employee feedback.2. Develop a clear visionDeveloping a clear vision is a critical step in implementing effective healthcare employee engagement strategies. Begin by defining what employee engagement looks like in your organization and the outcomes you hope to achieve. Your vision should be inspiring, achievable, and aligned with your organization’s values and goals. It may include elements such as open communication, regular feedback, recognition of employees’ efforts, opportunities for professional development, and a positive work environment.To ensure the vision is holistic and encompasses the multifaceted nature of healthcare, involve leadership from multiple functions. Leaders from operations, HR, nursing, medicine, and support services should all have a seat at the table. Harnessing their unique perspectives will help you create a comprehensive vision that caters to the diverse needs of your workforce.Remember, the vision should be communicated clearly and consistently to all employees. This not only ensures everyone is on the same page but also reinforces the importance of employee engagement in achieving organizational success. Using an integrated platform like MangoApps can aid in this communication process, providing an easy-to-use channel for conveying your vision and other important updates.Once the vision is established, it should serve as the north star guiding all your employee engagement initiatives. Always refer back to this vision when planning activities or making decisions to ensure alignment and consistency. This will help to create a cohesive and engaging experience for your employees, reducing burnout and improving satisfaction and ultimately, patient care.3. Create an action planWith your vision in place, you can start developing a detailed action plan. This plan should outline the steps you’ll take, the resources you’ll need, and the timeline for implementation. It should also specify how you’ll measure success. Remember to incorporate various healthcare employee engagement ideas into your plan, ensuring it addresses the diverse needs and preferences of your team.4. Communicate and implement the planOnce your action plan is ready, it’s time to communicate it to your team. Remember, communication should be a two-way street. Invite feedback and be ready to make adjustments based on the responses you receive. Then, start implementing your plan. Tools like MangoApps can support you in this phase, helping you manage tasks, track progress, and facilitate communication.5. Evaluate and adjustEngagement is a continuous process that requires regular evaluation and adjustment. Schedule times to review your progress, celebrate wins, and brainstorm solutions to challenges. Use employee feedback, engagement metrics, and other relevant data to assess the effectiveness of your plan. Be ready to make necessary adjustments and continually refine your approach. This constant cycle of feedback and improvement can keep your engagement efforts fresh and effective, helping you achieve your goals.Remember, every health system is unique, so it’s essential to customize your engagement strategy to best fit your organization’s specific needs and circumstances. Both macro and micro-level initiatives can have a significant impact on engagement levels, so be sure to address both broad organizational changes as well as individual employee needs. Lastly, remember that building engagement is a long-term process that requires consistent effort, commitment, and patience.ConclusionThe heart of any healthcare system is its employees. By championing their well-being, promoting open communication, and acknowledging their achievements, we pave the way for improved healthcare outcomes. The future of healthcare is intertwined with engaged employees.For more on this topic, read about reducing nurse turnover, physician engagement strategies, or digital transformation in healthcare. --- # 7 Tips to Choose the Best Intranet Vendor **Author:** MangoApps **Published:** 2024-02-07 **Category:** intranet Forming and maintaining successful business relationships takes time, understanding and introspection. Choosing a lasting and reliable intranet vendor should... Forming and maintaining successful business relationships takes time, understanding and introspection. Choosing a lasting and reliable intranet vendor should be about more than just modules and features. At MangoApps, we believe in fostering open communication between businesses, employees, and anyone else in the business world. So it only makes sense to pass on our intranet vendor expertise.We’re excited to share with you the top 7 strategies for choosing the best intranet vendor for your business:Know Your Company NeedsIt’s almost impossible to find the right intranet vendor if you don’t have at least an idea of what you’re looking for. Before you start talking to vendors do a little introspection and think about what your main intranet focuses and goals are. It’s also a good idea to briefly familiarize yourself with basic intranet options such as on-premise/SaaS to help you communicate with vendors and understand how intranets can assist with your current goals and strategies.Think About the End-UserIt’s easy to get caught up in seemingly endless options and possibilities but if your intranet is going to be successful you have to keep the end-user in mind. Are the features what your employees need, will they be easy to understand and will they integrate well with your business style? Every business has their own unique work styles and preferences and a profitable intranet needs to accommodate and increase those behaviors.For example, artistic professions generally work in a less rigid space. Ideas tend to come unexpectedly so projects often start quickly and finish slowly over time. Intranets for this type of work need to be fluid, adaptable and accessible at all times. In contrast, an accounting firm works very systematically and benefits more from rigid structure and organization. It might take some reflection to understand your company’s style. Choosing an intranet vendor allows you to build on employee work habits.Listen To Your IntuitionA good intranet should be almost instinctual. While you will need a basic introduction of its features, your intranet should feel easy and natural. Just like you learned how to use email or countless kinds of social media without detailed training or instruction, the right intranet for your company should be clear and easy to understand right from the start. If your intranet doesn’t feel natural, especially when you are learning how to use it, it’s not very likely to last.In addition to a system that works your style, you need to be aware of potentially shady or unusual fine print. Vendors at times try to disguise information, making a great looking service turn into something completely different. We all know the frustration of a “free” app or a phone providers “encouragement” to upgrade. That’s not the kind of nonsense you should be dealing with in your intranet. Read your contract terms carefully and listen to your intuition about what seems right.Analyze Existing MethodsIn order for an intranet to be effective, it has to integrate easily with the products you already use. Intranets are designed to be a one-stop-shop of sorts for all of your company’s internal needs. Your intranet needs to incorporate or replace your existing methods of sharing, collaborating and communicating information.A useful intranet should also be as customizable as your company needs. Do you have a habit of personally tailoring everything, is software customization important to your brand and your work process? Or is software something that you like as is? You want it to do the job right out of the box and not worry about the little details. While neither approach is wrong, it is important that you intranet works how you do and offers you the freedom, or lack thereof, that you need.Consider Your AccountantsCompany budget is probably the most important factor in choosing an intranet vendor or even not choosing one at all. As disappointing as it may be, a budget is often the sad fact that brings our dreams back to reality. Even the most beneficial tools, services, and innovations are sometimes just out of our reach because of budget. It is incredibly important to keep a clear head when considering vendors and find the best tools that won’t break the bank.If you find yourself having to settle for a package, service or vendor that’s not exactly what you wanted, don’t worry. You may need to compromise now, but knowing what you really want is key to future business success. Once you are ready to work with that exciting new intranet vendor, chances are pretty good that their products will be even better.Evaluate Their ExperiencePart of your success with intranet vendors comes from their own experience with your business and industry-specific needs. Take some time to look into their similar experience. Have they worked with clients like you before? Are they familiar with your unique challenges?  Do they have a specialty? While specialties and specific experience might not be a deciding factor alone, it can contribute to an overall decision. And sometimes an outstanding vendor with great products and services just isn’t a good fit for your business.And of course, a good intranet vendor needs to have a strong customer service culture as well as the knowledge and know how to handle questions and concerns. Before you commit, try to have at least one experience with your potential vendor’s customer service team. Ask them any questions you have as well as what to do in a few plausible problems and scenarios. Having a least a little experience with customer service gives you a window to what your future encounters with the company will be like, especially when trying to resolve a concern or fix an issue.Assess The AssociationThe final factor to consider before settling on an intranet vendor is the potential impact of your actual relationship. Every business has its own specific set of values and personality and who you choose to associate with will say a lot about your own business. Even if a vendor provides outstanding intranet, it is important to consider how you will be perceived for associating with them. A business’s brand and company culture will also typically give you a good idea of what working with them will be like.Ideally, a successful business with services you enjoy will have a helpful and positive company culture and reputation but unfortunately, that is not always the case. It is important for both the success of your business relations as well as the continuous improvement of your own business reputation to take a little time and evaluate the potential side effects of associating with a specific intranet provider. MangoAppsChoosing an intranet vendor is an important step for your business but it doesn’t have to be intimidating. With a little forethought and some simple evaluation, you’ll be sure to find the perfect vendor. At MangoApps, we understand the importance of combining useful tools with outstanding service and are committed to offering our customers the best intranet products with the best possible experience.To learn more about how MangoApps can help your organization, schedule a personalized demo today.SCHEDULE DEMO --- # The Complete Guide to Intranet Best Practices and Evaluating Enterprise Intranet Platforms in 2026 **Author:** Andy Tolton **Published:** 2024-02-01 **Category:** intranet Build an intranet employees use and evaluate enterprise platforms on ten criteria, with new sections on AI search, frontline access without corporate email, centralization, and governance. > **Quick answer:** To evaluate enterprise intranet platforms, score each vendor on ten criteria: frontline reach without corporate email, mobile experience, internal communications with acknowledgment tracking, AI-powered search and knowledge retrieval, document and tool centralization, integrations with HRIS and identity systems, governance and compliance, administration overhead, adoption architecture, and total cost. Treat frontline reach, search, and governance as eliminators if you have deskless staff, then compare finalists in a scored pilot rather than a demo. This guide covers the best practices for building an intranet and, new for 2026, the criteria for evaluating enterprise intranet platforms before you build. If you are considering the switch to a modern intranet platform, or you want to learn how to build an intranet your employees actually use, you are in the right place. When built properly, a modern intranet creates a helpful, interactive, and centralized employee experience that changes how information flows through your workforce. The numbers explain why the evaluation stage matters more than it used to. 91% of organizations have an intranet, yet only 13% of employees use theirs daily and 31% never do, according to [Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics). The intranet is the main source of company information for just 39% of desk-based employees in the U.S. and 45% in the UK, against 61% in Germany, according to [Staffbase's 2025 International Employee Communication Impact Study](https://staffbase.com/blog/employee-communication-impact-study-2025). Buyers in 2026 evaluate intranets as platforms, combining communication, knowledge, frontline reach, and AI search, not as portals. In this guide we tackle the questions we hear most: How do we build an intranet? How do we evaluate the vendors? Which features should we prioritize? How do we reach employees who do not have a corporate email? How do we make sure people use it? If you are ready to make the switch, learn more about the [MangoApps modern intranet platform](https://www.mangoapps.com/solutions/modern-intranet). If you would rather optimize the intranet you already have, start with our [intranet content audit guide](https://blog.mangoapps.com/intranet-content-audit-guide/). **Jump to a topic:** - [How to build an intranet](#best-practices-for-building-an-intranet) - [How to evaluate enterprise intranet platforms](#how-do-you-evaluate-enterprise-intranet-platforms-the-10-evaluation-criteria) - [Searchability and AI knowledge retrieval](#how-should-you-evaluate-intranet-search-and-ai-knowledge-retrieval) - [Frontline access without corporate email](#how-do-enterprise-intranets-reach-frontline-employees-without-corporate-email) - [Centralizing tools and documents](#how-does-an-intranet-centralize-tools-documents-and-job-critical-resources) - [Governance, compliance, and global access](#what-governance-compliance-and-global-access-requirements-should-an-enterprise-intranet-meet) - [How to compare intranet vendors](#how-do-you-compare-intranet-vendors-once-you-have-a-shortlist) - [Keeping your intranet relevant](#best-practices-for-keeping-your-intranet-relevant) - [How to know if you need a new intranet](#how-to-know-if-you-need-to-build-a-new-intranet) - [Enterprise intranet platform landscape](#enterprise-intranet-platform-landscape-in-2026) - [Intranet samples](#intranet-samples) - [Frequently asked questions](#frequently-asked-questions) ## Best practices for building an intranet A great intranet platform gives employees all the tools and resources they need to collaborate with their colleagues and be productive. To accomplish that, you first have to select an intranet vendor and build out [your intranet](https://www.mangoapps.com/articles/top-25-intranet-platforms-frontline-desk-workers) in a way that sets your employees up for future success. Doing this can seem daunting, so we have laid out a detailed 10-step process that covers everything from building an intranet to getting people to use it. ### Building an intranet in 10 steps #### 1. Put a team together The first step in building a modern intranet is to assemble a team to take on the task. This team should consist of several different departments from within your organization, including decision-makers, internal communications, HR, IT, and, if you have frontline staff, operations. With a diverse range of ideas, jobs, and interests represented from the very beginning, you ensure your team accurately represents the needs of your company. That gives the intranet the internal support and advocacy it needs to invite, encourage, and persuade all employees to participate. #### 2. Establish goals and objectives This is probably the most important of all intranet best practices. Once your team is established, determine the actual goals of your company's intranet. Agreeing on objectives keeps everyone on the same page through vendor selection and launch. While every intranet is unique to its organization, common objectives include: - Increasing internal company communication - Improving team collaboration - Managing organizational content and knowledge - Developing company culture and engagement - Reaching employees who do not sit at a desk or have a corporate email #### 3. Select a vendor After you have created a general outline of intranet expectations, it is time to choose a vendor. Selecting the right vendor is one of the most important steps in building a company intranet. Your intranet vendor will determine not only your overall expenses but also the capabilities, intuitiveness, security, and manageability of your entire platform. Use the [10 evaluation criteria](#how-do-you-evaluate-enterprise-intranet-platforms-the-10-evaluation-criteria) in the next section to structure the comparison. Procurement will ask three questions first, so have the answers ready: Can frontline employees sign in without a corporate email? Which security certifications does the vendor hold? How deep are the integrations with your HRIS and identity provider? Always choose a vendor you feel comfortable with, who not only offers the specific services you need but is willing to support and work personally with you. For more guidance, see our list of [questions to ask in an intranet demo](https://blog.mangoapps.com/top-questions-to-ask-during-an-intranet-demo/). #### 4. Make the intranet your own Once you have chosen the vendor best suited to your organization, the focus shifts to personalizing and branding your platform. Determine the architecture and flow of the intranet and spend time thinking about what you want the design to look like. A good vendor makes it easy to customize your intranet and alter colors, logos, fonts, and branding materials. A distinctive and familiar intranet creates an inclusive environment right away, where workers know they belong and are part of the team. Employees are much more likely to engage with the platform if it feels like an extension of the company. #### 5. Organize your space When building a modern intranet, think beforehand about how your organization plans to share, distribute, and access content. While there are dozens of ways to organize the details, most businesses arrange content by company, department, and group. Here are the typical intranet organization best practices our customers follow. - **Company information:** company announcements, newsletters, holidays, and other content relevant at a company-wide level. - **Department news:** content relevant to the different departments within your organization. Companies typically have one area for company content and several department areas, and department information varies greatly from group to group. - **Group content:** the most specific level, covering projects, teams, locations, and shifts. Groups tend to involve more collaboration and back-and-forth communication than company or department areas do. Our [intranet design examples](https://www.mangoapps.com/articles/intranet-design-examples-to-inspire-your-work-hub) can help you visualize this and gather ideas. #### 6. Configure features, modules, and permissions A good intranet platform includes a wide range of useful out-of-the-box features designed to cover many combinations of needs. Before you begin creating or incorporating content, edit, enable, disable, or customize the available modules and features for the whole platform and for each department or group area. Set permissions for different roles and locations, and decide which areas are public and which are private. Read our article on [the most important intranet features](https://www.mangoapps.com/articles/intranet-features-your-employees-will-love) for more detail. #### 7. Incorporate existing information Now it is time to add information. Add important company resources, employee handbooks, policies, and anything else employees need regular or easy access to. Do not forget departmental information and content for specific projects and teams. Uploading and maintaining all of this can seem like an enormous undertaking. Our recommended best practice is to let department heads maintain their department's information, each with a review date on the content they own so nothing goes stale unnoticed. With a modern intranet platform, even the least tech-savvy managers can handle this task. If you are moving from SharePoint, Workplace from Meta, or a legacy portal, ask the vendor about migration services. Moving content with its ownership and version history intact is faster than rebuilding it, and it prevents two versions of the same policy from going live. See our [SharePoint replacement resources](https://www.mangoapps.com/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) for a practical checklist. #### 8. Host a launch party An intranet launch party is a perfect opportunity to unveil your new platform and get employees engaged. A successful launch should include advocates from various departments, and at frontline sites it should include floor-level sign-up with a QR code so employees activate on the spot. Employees need to know the new intranet is an effective tool for everyone, not just one department or a handful of teams. The greater your scope of representation, the higher your overall participation will be. Moving to a new communication and collaboration style can be difficult, especially for workers who are not tech-savvy. A launch event informs and educates employees while being a fun and inviting experience. Read our article on [intranet engagement ideas](https://blog.mangoapps.com/how-to-improve-intranet-engagement/) for more on this topic. #### 9. Create new content that follows best practices Over time your organization will adapt and change as it grows in size, policy, mission, or mindset. As your company evolves, the intranet should adapt as well. A good intranet enables administrators to add, remove, or edit platform features at any time. A regular review of intranet functions, features, and content keeps the platform aligned with your company's goals and style. #### 10. Measure adoption and iterate Define your baseline at go-live and track four numbers by location and role: weekly active users, search success rate, acknowledgment rate on critical posts, and content freshness. Review them monthly. Use published benchmarks to judge the results. [Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) puts a successful intranet at 60% weekly active users, best practice at 85% weekly login, and a minimum search success rate at 75%. Legacy intranets average 30 to 40% adoption, according to MangoApps customer data, while MangoApps customers average more than 90% within 90 days. The gap between those two numbers is almost always frontline reach and daily utility, which the next sections cover. ## How do you evaluate enterprise intranet platforms? The 10 evaluation criteria Evaluate every enterprise intranet platform against the same ten criteria, weight them for your workforce, and treat three of them as eliminators if you have deskless staff: frontline reach, search, and governance. A platform that scores well on content management but requires a corporate email to log in is not a realistic option for a manufacturing floor or a retail store. | Criterion | Why it matters | What to verify (a test, not a feature name) | Weight | |---|---|---|---| | 1. Frontline and deskless reach | Deskless workers are 70 to 80% of the global workforce ([BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology)) and 58% of U.S. workers ([JLL](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention)) | A worker with no email address signs in from a QR code in under two minutes; a branded app; offline access | Eliminator | | 2. Mobile experience parity | A shrunken desktop is not a mobile intranet | Complete a schedule swap, a policy acknowledgment, and a search on a phone without pinching | High | | 3. Internal communications and acknowledgment tracking | "Sent" is not "received" for safety and compliance messages | Target a post by role, location, and shift; view acknowledgment by site; deliver by push, SMS, and signage | High | | 4. Search and AI knowledge retrieval | Search quality is the single strongest predictor of daily use | Type a question in plain language; get a permission-correct answer with its source, across M365 and Google Drive | Eliminator | | 5. Document and tool centralization | One home for policies, SOPs, forms, and embedded tools | Version history on a policy; embedded HRIS and payroll access; forms replacing email routing | High | | 6. Integrations and identity | Audience lists and permissions must follow the HRIS | Create and terminate a worker in an HRIS sandbox; SSO and SCIM; named native connectors versus "API available" | High | | 7. Governance, security, and compliance | Procurement will ask before the frontline ever sees it | Current SOC 2 Type II report, ISO 27001 certificate, HITRUST or FedRAMP where required; audit logs; retention; deployment options; data residency | Eliminator for regulated industries | | 8. Administration and IT overhead | Who owns changes after launch | A non-technical admin changes navigation, permissions, and a workflow in the demo without a developer | Medium | | 9. Adoption architecture | Promises are not architecture | Customer weekly-active-user data by industry at 90 days and 12 months; manager enablement; a contractual guarantee | High | | 10. Total cost, contract, and vendor stability | Hidden costs arrive in year two | Module pricing, frontline tiers, integration fees, exit and data-return terms, tools you can retire | Medium | Weight the criteria by who leads the buying decision. Communications-led evaluations tend to over-weight criterion 3 and under-weight 1, 5, and 6. IT-led evaluations over-weight 7 and 8 and under-weight 2 and 9. HR-led evaluations need 1, 5, and 9 most. The safest correction is to give the frontline eliminators a veto regardless of who leads. For the process that sits around these criteria, including how to run an RFI, scored demos, and reference checks over six to eight weeks, see [How to Evaluate Employee Intranet Platforms in 2026](https://www.mangoapps.com/articles/evaluate-employee-intranet-platforms-2026). An editable scorecard and RFP template are in the [2026 Intranet Buyer's Guide for a Frontline Workforce](https://www.mangoapps.com/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026). Where MangoApps has a verifiable proof point on a criterion, we note it: 200+ out-of-the-box integrations (criterion 6), HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO with SaaS, private cloud, VPC, and on-premise deployment (criterion 7), and an Adoption Guarantee of 90%+ within 90 days (criterion 9). The criteria themselves apply to any vendor. ## How should you evaluate intranet search and AI knowledge retrieval? The test for intranet search is simple: an employee types a question in their own words, on a phone, and gets a correct answer with its source, drawn from every repository the company uses, and never from a document that employee is not permitted to open. Everything else is a feature list. The reason search deserves its own section is usage. Employees spend just under six minutes a day on their intranet, according to [SWOOP Analytics' 2025 benchmarking report](https://www.swoopanalytics.com/sharepoint-bm-25), and only 13% use it daily ([Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics)). When the first search fails, people stop trying and ask a manager instead. Only 23% of frontline workers believe they have the technology they need to do their jobs, per [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html), and search that returns twelve PDFs is a large part of why. ### A search evaluation test script Run these six searches in every vendor demo, on a phone, signed in as a frontline role. | What to type | A passing result | A failing result | |---|---|---| | "How do I request time off?" | The PTO policy summary and a link to the request form | A list of documents containing the word "time" | | An internal acronym ("What is our LOA policy?") | Expands the acronym and answers | No results | | A misspelled product or system name | Corrects the spelling and answers | No results | | A question whose answer lives in SharePoint or Google Drive | Returns the answer with the source, without leaving the app | "Not found" because the content is in another system | | A question a frontline role should not see answered (an executive compensation memo) | Declines or returns nothing | Answers from the restricted document | | A question in Spanish | Answers in Spanish from the English policy | English results or nothing | ### Search, AI assistant, and AI agent Three terms get used interchangeably and should not be. **Search** retrieves documents that match. An **AI assistant** returns a grounded answer with citations from the documents the user is allowed to see. An **AI agent** takes an action, such as submitting the PTO request the assistant just explained. The governance rule is the same for all three: they inherit the user's permissions, act on the company's own data rather than a copy, and log what they did. For the architecture argument, see [Your AI Agent Is Reading a Copy of Your Business](https://www.mangoapps.com/articles/ai-agents-native-data-vs-copies), and for the platform view, [MangoApps knowledge management](https://www.mangoapps.com/solutions/knowledge-management). ## How do enterprise intranets reach frontline employees without corporate email? By issuing identity from the HR system rather than the email system, letting workers sign in by SMS, QR code, employee ID, or badge, and delivering a branded mobile app with offline access, push and SMS notifications, translation, and the schedules and tasks that give workers a reason to open it every shift. The scale of the gap is the reason this is an eliminator. Deskless workers make up 70 to 80% of the global workforce, about 2.7 billion people ([BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology)), and 58% of American workers are on the frontline ([JLL](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention)). Most were never issued an inbox. | Capability | Why it matters | Verify in the demo | |---|---|---| | Branded app in the app stores | Adoption rises when the app carries the employer's name | Show the app-store listing under a customer's brand | | Sign-in without corporate email | The threshold requirement | Sign in as a worker with no email, from a QR code | | Shared-device and kiosk mode | Break rooms, plant floors, and hospitals where personal phones are restricted | Switch users on a shared tablet | | Offline access | Basements, back rooms, rural sites | Open a policy in airplane mode | | Push and SMS notifications | Email is not available; push is | Send a critical alert and receive it on a phone | | Translation | Multilingual workforces | Post in English; read it in Spanish | | Role, location, and shift targeting with acknowledgment | Relevance and compliance evidence | View acknowledgment by site | | Schedule, shift, and task access | The daily reason to open the app | View a schedule and request a swap | | Digital signage | Reaches shared spaces | Publish once to app and signage | | Two-way tools | A read-only portal is a poster | Comment, survey, recognize a colleague | A.S. Watson Benelux shows what this looks like in practice: more than 80% of Kruidvat's 16,000+ retail employees became active MangoApps users without corporate email addresses, and 20,000+ employees now receive weekly schedules in the app. For the feature detail see [9 Modern Employee Intranet Features That Reach Frontline Staff Without Email](https://www.mangoapps.com/articles/intranet-features-that-reach-frontline-workers), for the business case see [How to Choose an Intranet for a Frontline Workforce in 2026](https://www.mangoapps.com/articles/how-to-choose-frontline-intranet-2026), and for the product view see the [MangoApps employee app](https://www.mangoapps.com/solutions/employee-app). ## How does an intranet centralize tools, documents, and job-critical resources? A modern intranet centralizes work by giving every role one home page that embeds the tools they already use, a governed document management library with one current version of every policy, and search that spans every connected system. For a step-by-step approach, see [How to Centralize Tools and Documents with an Employee Intranet](https://www.mangoapps.com/articles/centralize-tools-documents-employee-intranet). The measure of success is the number of applications an employee no longer has to open. That number is large. The average company runs 101 applications, and companies with more than 5,000 employees average 131, according to [Okta's Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/). A [Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) study found workers toggling between applications roughly 1,200 times a day, about four hours a week spent reorienting. | Resource | Fragmented stack today | Centralized intranet | |---|---|---| | Policies and SOPs | Shared drives, email attachments, a binder in the back office | One library, one current version, owner and review date on each | | Schedules | A WFM tool, a group text, a printout | Visible in the intranet app with swaps and coverage requests | | Forms and approvals | Email threads and paper | Digital forms with routing, status, and audit trail | | Training | A separate LMS login | Assigned by role and completed in the same app | | News | Email nobody on the floor receives | Targeted posts with acknowledgment | | People | An out-of-date org chart | A directory synced from the HRIS | ### For mid-sized enterprises with deskless staff Organizations of 500 to 2,500 employees face the same fragmentation as large enterprises with a fraction of the IT capacity to manage a multi-vendor stack. The employee intranet software that serves mid-sized enterprises with deskless staff best is packaged rather than assembled: modules that work together on one login, administration that does not require a developer, vendor-led migration from the old portal, and a rollout measured in weeks. Ask the vendor how many of your current tools a single platform would retire; that number is the business case. ## What governance, compliance, and global-access requirements should an enterprise intranet meet? An enterprise intranet should provide role-based access that follows the HRIS, content ownership with review dates and expiry, tamper-evident audit logs, retention and legal hold, acknowledgment records for policies, recognized certifications (SOC 2 Type II and ISO 27001 as a baseline, HITRUST for healthcare, FedRAMP for public sector), a choice of deployment models, and documented regional hosting with GDPR and UK GDPR paperwork. | Requirement | Who asks | Evidence to request from the vendor | |---|---|---| | HRIS-driven identity, provisioning, and deprovisioning | InfoSec, HR | Live demo in a sandbox: create a worker, terminate a worker | | Role-based permissions and delegated administration | InfoSec, Comms | Permission model documentation; a scoped regional admin in the demo | | Content ownership, review dates, expiry, versioning | Compliance, Comms | Expiry queue and version history in the demo | | Audit logs, acknowledgment export, retention, eDiscovery, legal hold | Legal, Compliance | Sample export; retention configuration | | Certifications | InfoSec, Procurement | Current SOC 2 Type II report; ISO 27001 certificate; HITRUST or FedRAMP letter where required | | Deployment options | InfoSec, IT | SaaS, private cloud, customer VPC, on-premise, in writing | | Data residency and transfers | Legal, Privacy | Hosting regions; subprocessor list; data processing agreement; EU SCCs and UK International Data Transfer Addendum | | Permission-aware AI | InfoSec, Compliance | Ask the AI a question the user is not permitted to see answered | ### Global workforce access A global intranet adds four requirements: automatic translation of content and comments, regional administrators who can publish to their region and nothing else, time-zone-aware publishing, and local variations of policy where law or works-council agreements require them. Data residency by region should be documented, not promised. MangoApps publishes HITRUST CSF, SOC 2 Type II, ISO 27001, FedRAMP ATO, HIPAA business associate agreements, and GDPR data processing agreements, offers SaaS, Private Cloud, Customer VPC, and On-Premise deployment, and provides real-time audit logs, eDiscovery and legal hold, and retention policies, per [mangoapps.com/security](https://www.mangoapps.com/security). For a deeper treatment of how governance and adoption reinforce each other, see our guide to [increasing frontline intranet adoption without sacrificing governance or compliance](https://www.mangoapps.com/articles/frontline-intranet-adoption-governance-compliance). ## How do you compare intranet vendors once you have a shortlist? Build the shortlist by category, ask each vendor the same ten demo questions, run a scored pilot at two real sites instead of trusting the demo, and check references in your industry and at your scale. ### Build the shortlist by category - **Unified workforce platforms** combine intranet, employee app, and operational workflows (scheduling, tasks, training, HR) for frontline and desk staff. Example: MangoApps. - **Communications platforms** lead with multichannel publishing and measurement. Examples: Staffbase, Firstup, Poppulo. - **SharePoint intranet-in-a-box products** improve the SharePoint experience for Microsoft 365 organizations. Examples: Fresh, Involv, Powell, Omnia. - **Social intranets** lead with community and engagement. Examples: Haiilo, Workvivo, Axero. - **Frontline employee apps** lead with mobile reach for deskless workers. Examples: Blink, Flip, Beekeeper. For profiles and rankings, see [25 Intranet Platforms Worth Evaluating in 2026](https://www.mangoapps.com/articles/top-25-intranet-platforms-frontline-desk-workers) and [Best Employee Intranet Platforms for Frontline Teams in 2026](https://www.mangoapps.com/articles/best-employee-intranet-frontline-teams). ### Ten demo questions that separate vendors 1. **"Sign in as a worker who has no email address."** A strong answer: two minutes from a QR code. A weak answer: IT creates the account. 2. **"Terminate that worker in the HRIS sandbox. When does access end?"** Strong: automatically, the same day. Weak: an admin removes them. 3. **"Type a plain-language policy question on a phone."** Strong: an answer with its source. Weak: a document list. 4. **"Show me acknowledgment by location for last week's critical post."** Strong: a manager view with an export. Weak: total opens. 5. **"Who owns this policy, when is it reviewed, and what happens when it expires?"** Strong: owner, date, and an expiry queue. Weak: "content managers keep it current." 6. **"Which HR transactions can an hourly employee complete here, not just view?"** Strong: PTO and availability with approvals. Weak: a link to the HRIS login. 7. **"For each system on my integration list, is this a native connector, an API, or a partner build, and who maintains it?"** Strong: a per-system answer. Weak: "we integrate with everything." 8. **"Change the navigation and a permission as a non-technical admin."** Strong: done in the demo. Weak: a professional-services ticket. 9. **"Ask your AI a question whose answer lives in a document I cannot open."** Strong: it declines. Weak: it answers. 10. **"What weekly active adoption do your customers in my industry reach at 90 days, and what is your contractual commitment if we do not?"** Strong: numbers and a guarantee. Weak: a change-management slide. ### Scored pilot, not demo Pick two sites and one shift population for 30 days. Capture weekly active users by site, acknowledgment rate on one critical post, time-to-find for one SOP, and the number of schedule or policy questions managers field before and after. Those four numbers will tell you more than any demo. ### Reference checks Ask references in your industry and at your scale three things: weekly active users at month 3 and month 12, which tools they retired, and how much integration effort the HRIS connection actually took. ## Best practices for keeping your intranet relevant Once you have built your new company intranet, the focus shifts to maintaining high levels of employee adoption. Your intranet is only as useful as the content within it and the reach it has. ### Make your intranet mobile-friendly No matter your organization's line of work, some work happens on the go. From frontline employees to traveling executives, modern work happens anywhere and everywhere. Deskless workers are 70 to 80% of the global workforce, about 2.7 billion people ([BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology)), and 58% of American workers are on the frontline ([JLL](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention)). Enabling easy and reliable intranet access away from a desk ensures employees never go without important information. The simplest way to do this is to make a [mobile intranet](https://www.mangoapps.com/solutions/employee-app) with sign-in that does not require a corporate email an eliminator criterion during your search, not a nice-to-have. See the [frontline access section](#how-do-enterprise-intranets-reach-frontline-employees-without-corporate-email) above. ### Embrace your brand Personalizing and branding your intranet helps employees relate to it and encourages participation. Employees engage more with a platform they think of as an extension of their company, and a branded app in the app stores under your name, not the vendor's, raises adoption on the frontline. ### Incorporate integrations Maintain a centralized workspace by integrating the apps your employees use most into the intranet: your HRIS (Workday, UKG, ADP, SAP SuccessFactors), your identity provider (Okta, Microsoft Entra ID), Microsoft 365 or Google Workspace, your service desk (ServiceNow), and your scheduling and payroll systems. By acting as a one-stop shop, the intranet becomes the place employees go for anything they need to do their jobs. See the [centralization section](#how-does-an-intranet-centralize-tools-documents-and-job-critical-resources) above and [MangoApps integrations](https://www.mangoapps.com/integrations). ### Train your employees and managers Educate employees on how to use the intranet. A thorough training session helps employees become comfortable with the platform, and training managers first matters most on the frontline, where adoption runs through the site or shift manager. Release short training on new modules and features as they ship. ### Track employee interests A good intranet provides administrators with the tracking tools they need to see employee interest, gauge current needs, and plan future improvements. Report weekly active users by location and role, not in aggregate; the aggregate hides the sites that never started. ### Conduct surveys Tracking tools let administrators run quizzes, surveys, and polls to monitor feedback and see employee opinions firsthand. Successful surveys run on a set timeline and use clear, inclusive, and open-ended questions. Compare responses by location and shift so frontline sentiment is visible on its own. ## How to know if you need to build a new intranet It can be tricky to identify when it is time to move on from your current intranet, whether because you do not want to commit to a switch or because you are not fully aware of your current platform's limitations. Most organizations fall into one of three buckets: - **Bucket 1:** You have learned to cope with a clunky, outdated, difficult-to-navigate intranet that hinders your employees' productivity. - **Bucket 2:** You are unaware of the limitations of your existing intranet platform. - **Bucket 3:** Your modern intranet enables strong collaboration and lets your employees be as productive as possible. An alarming number of organizations fall into Buckets 1 and 2. Only 13% of employees use their intranet daily and 31% never do ([Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics)), and the average employee spends under six minutes a day on it ([SWOOP Analytics](https://www.swoopanalytics.com/sharepoint-bm-25)). If you are unsure whether your company needs a new intranet, count how many of these twelve signals apply. **Reach** 1. Frontline staff need a corporate email address to log in. 2. Managers re-broadcast intranet posts over text message so their teams actually see them. 3. Schedules, pay, and tasks live in other apps, so employees have no daily reason to open the intranet. **Findability** 4. Search returns documents, not answers, and employees ask a manager instead. 5. The same policy exists in two or more places with different content. 6. Content from a system like SharePoint or Google Drive does not appear in intranet search. **Governance** 7. Nobody can say who owns a given policy or when it was last reviewed. 8. Acknowledgment of safety or compliance notices is tracked on paper or not at all. 9. Departed employees still have access, or new hires wait days for it. **Engagement** 10. Weekly active use is below 60%, or nobody knows what it is by location. 11. Comments, surveys, and recognition are absent or ignored. 12. Leadership communicates through email that most of the workforce never receives. Three or more signals in any one group is a strong indication. For the full diagnostic, see [12 Reasons Frontline Intranet Adoption Fails (And How to Fix Each One)](https://www.mangoapps.com/articles/frontline-intranet-adoption-failures). ## Enterprise intranet platform landscape in 2026 The platforms below are the ones most often shortlisted by U.S. enterprises, grouped by category. For full profiles, evaluation notes, and pricing context, see [25 Intranet Platforms Worth Evaluating in 2026](https://www.mangoapps.com/articles/top-25-intranet-platforms-frontline-desk-workers) and [Best Employee Intranet Platforms for Frontline Teams in 2026](https://www.mangoapps.com/articles/best-employee-intranet-frontline-teams). | Platform | Category | Best for | Sign-in without corporate email | |---|---|---|---| | [MangoApps](https://www.mangoapps.com/) | Unified workforce platform | Frontline and desk workers in one platform | Yes | | [Microsoft SharePoint and Viva](https://www.microsoft.com/en-us/microsoft-365/sharepoint/collaboration) | Intranet and EX platform | Microsoft 365-standardized enterprises | Partial (depends on Teams and licensing) | | [Staffbase](https://staffbase.com/) | Intranet and communications platform | Multichannel communications with Microsoft 365 depth | Partial | | [Unily](https://www.unily.com/) | Employee experience platform | Complex global enterprises needing deep governance | Partial | | [Simpplr](https://www.simpplr.com/) | SaaS intranet | Fast deployment, low IT overhead | Partial | | [LumApps](https://www.lumapps.com/) | Employee communications | Communication-first with broad integrations; Beekeeper for frontline | Partial | | [Interact](https://www.interactsoftware.com/) | Intranet platform | Content publishing and multichannel communications | Partial | | [Oak Engage](https://www.oak.com/) | Intranet platform | Usability and frontline-friendly features | Yes | | [Workvivo](https://www.workvivo.com/) | Social intranet | Culture and engagement for Zoom-centric organizations | Partial | | [Blink](https://www.joinblink.com/) | Frontline employee app | Deskless workforce communications | Yes | *Capability statements for third-party vendors are vendor-stated from public documentation as of September 2026 and not independently verified by MangoApps. "Partial" means frontline access exists but depends on configuration or licensing.* MangoApps is the unified option for organizations that need one platform for frontline and desk employees. It holds HITRUST CSF, SOC 2 Type II, and ISO 27001 together; of the platforms in this table, none we reviewed publishes a HITRUST certification on its public security pages. ## Intranet samples Intranets come in all shapes and sizes, and choosing the style that works for your company can be daunting. How do you know what information to include, which features will engage your employees, and which solution will be easy to implement and maintain? We have collected [intranet design examples](https://www.mangoapps.com/articles/intranet-design-examples-to-inspire-your-work-hub) to inspire your project and demonstrate some of our customers' intranet best practices. ## Frequently asked questions **How do you evaluate intranet vendors?** Score each vendor on ten criteria: frontline reach without corporate email, mobile experience, communications and acknowledgment tracking, AI search, centralization, integrations and identity, governance and compliance, administration overhead, adoption architecture, and total cost. Ask every vendor the same ten demo questions, then run a 30-day scored pilot at two real sites before you decide. **How do you compare employee intranet options for a digital workplace initiative?** Group the options by category (unified workforce platform, communications platform, SharePoint intranet-in-a-box, social intranet, frontline employee app), shortlist one or two per category that fit your workforce, and compare them on the same scorecard. Decide first whether you are buying a portal or a platform that will also carry schedules, tasks, and training. **What are the most important intranet evaluation criteria for organizations with frontline employees?** Three eliminators: sign-in without a corporate email, search that returns answers on a phone, and governance that satisfies procurement (certifications, audit logs, deployment options). Deskless workers are 70 to 80% of the global workforce, so a platform that fails the first test excludes most employees. **What are the top employee intranet platforms for frontline organizations in the United States?** Frontline-heavy U.S. enterprises most often shortlist MangoApps, Microsoft SharePoint and Viva, Staffbase, Unily, Simpplr, LumApps with Beekeeper, Interact, Oak Engage, Workvivo, and Blink. MangoApps is the unified platform for frontline and desk staff; see the full rankings in our 25-platform guide. **Which employee intranet software best serves mid-sized enterprises with deskless staff?** Packaged platforms that combine intranet, employee app, and operational workflows on one login with non-technical administration and vendor-led migration. Mid-sized organizations lack the IT capacity to assemble and maintain a multi-vendor stack, so the number of tools a single platform retires is the business case. **Which employee intranet software supports governance and compliance for global enterprises?** Look for HRIS-driven identity, role-based permissions with delegated regional administration, content ownership and expiry, audit logs, retention and legal hold, published certifications (SOC 2 Type II, ISO 27001, HITRUST, FedRAMP), deployment options, and documented data residency. MangoApps publishes all of these; compare other vendors' current security pages during procurement. **What are intranet best practices for launch and adoption?** Assemble a cross-functional team, set objectives, evaluate vendors on the ten criteria, brand and organize the platform, configure permissions, migrate content with owners and review dates, launch with floor-level sign-up and trained managers, and measure weekly active users by location against the 60% and 85% benchmarks. **How do you know if you need a new intranet?** Count the twelve signals above across reach, findability, governance, and engagement. Three or more in one group, or weekly active use below 60%, is a strong indication. **What should intranet search be able to do in 2026?** Answer a plain-language question on a phone with the source cited, search across connected systems such as Microsoft 365 and Google Drive, respect the user's permissions, correct misspellings and expand acronyms, and answer in the user's language. **How long does it take to build and launch an intranet?** With a packaged platform, a 90-day plan is realistic: identity and permissions in weeks 0 to 2, content and manager training in weeks 3 to 4, pilot launch in weeks 5 to 6, regional expansion in weeks 7 to 10, and benchmarking in weeks 11 to 13. Heavily customized deployments take longer. ## Resources - [2026 Intranet Buyer's Guide for a Frontline Workforce](https://www.mangoapps.com/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026): editable scorecard, RFP template, and implementation checklist - [25 Intranet Platforms Worth Evaluating in 2026](https://www.mangoapps.com/articles/top-25-intranet-platforms-frontline-desk-workers) - [Best Employee Intranet Platforms for Frontline Teams in 2026](https://www.mangoapps.com/articles/best-employee-intranet-frontline-teams) - [The 10 Best Employee Intranet Platforms for Governance, Compliance, and Global Workforce Communication](https://www.mangoapps.com/articles/best-intranet-platforms-governance-compliance-global) - [8 Signs Your Frontline Organization Has Outgrown Its Employee Intranet](https://www.mangoapps.com/articles/intranet-problems-hurting-frontline-teams) - [How to Evaluate Employee Intranet Platforms in 2026](https://www.mangoapps.com/articles/evaluate-employee-intranet-platforms-2026) - Case studies: [TeamHealth](https://www.mangoapps.com/resources/teamhealth-case-study) and [Raley's](https://www.mangoapps.com/resources/raleys-case-study) - Sources: [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology), [JLL](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention), [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html), [Staffbase](https://staffbase.com/blog/employee-communication-impact-study-2025), [Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics), [SWOOP Analytics](https://www.swoopanalytics.com/sharepoint-bm-25), [Okta](https://www.okta.com/newsroom/articles/businesses-at-work-2025/), [Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) --- # 9 Digital Workplace Platforms With the Best HR and IT Integrations for Frontline Enterprises (and the 20 Features Employees Love) **Author:** Andy Tolton **Published:** 2024-01-30 **Category:** intranet Nine digital workplace platforms compared on HRIS, identity, and Microsoft 365 integration and on frontline access without corporate email, plus the 20 intranet features that drive daily use. > **Quick answer:** The digital workplace platforms most often shortlisted by large frontline enterprises in 2026 are MangoApps, Microsoft 365 with Viva, Staffbase, Unily, LumApps (with Beekeeper), Simpplr, Workvivo, WorkJam, and Flip. The deciding integration criteria are HRIS sync with Workday, UKG, ADP, or SAP SuccessFactors; identity through Okta or Microsoft Entra ID plus sign-in for workers who have no corporate email; coexistence with scheduling and payroll systems; Microsoft 365 or Google Workspace depth; ITSM connections; and documented APIs. Only a few platforms deliver operations workflows natively rather than through partners. Social Edge Consulting found that 91% of organizations already operate an intranet, yet only 13% of employees use theirs daily and 31% never log in. SWOOP Analytics' 2025 benchmarking report puts the average time employees spend on their intranet at under six minutes a day. The problem is not a technology gap. It is a selection problem: platforms chosen for their feature list rather than for how they connect to the systems where work already happens. For frontline enterprises that connection is the whole question. The features that make an intranet loved are the ones that reach into the HRIS, the identity provider, the scheduler, and the service desk, and that do so for people who have no corporate email. The average company now runs 101 applications, and companies with more than 5,000 employees average 131, according to [Okta's Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/). A [Harvard Business Review](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) study found workers toggling between applications roughly 1,200 times a day. A digital workplace platform earns its place by reducing both numbers. This guide has two halves. The first compares nine digital workplace platforms on HR and IT integrations and frontline connectivity, with an integration checklist and a depth matrix. The second covers the 20 features that determine whether the platform becomes employees' default workspace or another tool they quietly avoid. ## What is a digital workplace platform, and how is it different from an intranet or employee app? A digital workplace platform is the hub through which employees reach the systems they work in: news and knowledge, but also the HRIS, scheduler, service desk, learning system, and collaboration suite, through one login and one identity. An intranet is a destination; an employee app is a channel to deskless workers; a digital workplace platform is the integration layer that makes both of them useful. | Category | Primary job | Who it serves | Requires corporate email? | Integration role | Typical owner | |---|---|---|---|---|---| | Modern intranet | News, knowledge, policies | Whole company, historically desk-first | Often | Destination; links out to other tools | Communications, IT | | Employee app | Reach deskless workers on their phone | Frontline and hourly staff | No | Channel; surfaces other tools | Communications, Operations | | Digital workplace platform | One hub connected to HR, IT, and operations systems | Every employee | Should not | Hub; syncs identity and data both ways | IT, HR, Communications together | | Unified workforce platform | Runs the workflows natively (schedules, tasks, training, HR) on the same hub | Every employee, frontline first | No | Hub and system of engagement | Operations, HR, IT, Communications | For definitions in more depth, see the MangoApps glossary entries on the [digital workplace](https://www.mangoapps.com/glossary/digital-workplace) and [digital workplace versus modern intranet](https://www.mangoapps.com/glossary/digital-workplace-vs-modern-intranet). ## Why do HR and IT integrations decide whether frontline employees use a digital workplace platform? Because without identity driven by the HRIS, there is no way to onboard a worker who has no email address; without integrations, the platform is one more of the 131 applications; and with them, it becomes the front door to schedules, pay, tickets, and training, which is the only reason a frontline worker opens anything every shift. The gap the integrations have to close is wide. Only 23% of frontline workers believe they have access to the technology they need to be productive, according to [Deloitte](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html), and the same research estimates productivity rises about 22% when they are given the right mix. Deskless workers are 70 to 80% of the global workforce, about 2.7 billion people ([BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology)), and 58% of American workers are on the frontline ([JLL](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention)). IT teams see the same four integration failures across vendors: audience lists that go stale because they were uploaded rather than synced; accounts that survive termination because deprovisioning is manual; duplicate profiles because the platform keeps its own copy of the employee record; and connectors built by a partner that nobody maintains after the implementation ends. Each one is a governance problem and an adoption problem at the same time. ## The HR and IT integration checklist for frontline enterprises | Integration | Systems to name in the RFP | Why it matters for frontline | What native looks like | Verify in the demo | |---|---|---|---|---| | HRIS / HCM sync | Workday, UKG, ADP, SAP SuccessFactors, Paylocity, Oracle HCM, BambooHR, Rippling | People, roles, locations, and managers drive targeting and permissions | Scheduled and event-driven sync, maintained by the vendor | Create a worker in the HRIS sandbox; watch them appear in the right location | | SCIM and SSO identity | Okta, Microsoft Entra ID, Active Directory, LDAP, SAML 2.0, OIDC | Desk staff use existing credentials; deprovisioning is automatic | SCIM provisioning and deprovisioning, MFA | Terminate the sandbox worker; confirm access ends | | No-email identity | SMS one-time codes, QR onboarding, employee ID and PIN, badge | Most frontline workers have no corporate email | HRIS-provisioned accounts activated on the floor | Sign in as a worker with no email address | | Scheduling and WFM | UKG, Kronos, Legion, native scheduler | The daily reason to open the app | Schedules in the app; swaps written back | Request a swap; trace the approval | | Payroll and pay stubs | Payroll provider | Fewer manager questions | Pay stubs in the app | Open a pay stub as a worker | | Time and attendance | Time clock, native clock | Hourly pay accuracy | Geofenced mobile clock-in | Clock in on a phone | | Learning | Cornerstone, Workday Learning, native LMS | Compliance records | Assignments by role; completions written back | Complete a course; find it in the HRIS | | ITSM and service desk | ServiceNow | Frontline IT and facilities requests | Tickets created and tracked in the app | Open a ticket for a broken register | | Microsoft 365 | Teams, SharePoint, OneDrive, Outlook, Entra ID | Documents and desk collaboration already live here | Federated search and embedded files, no duplicate copies | Search a SharePoint policy from a phone | | Google Workspace | Drive, Calendar, Meet, SSO | Same, for Google shops | Same | Same | | File storage | Box, Dropbox | SOPs and forms | Permission-aware search | Search two repositories at once | | Data, BI, and AI | Tableau, Looker; OpenAI, Azure OpenAI, Gemini, Anthropic | Reporting; AI that respects permissions | AI grounded in the platform's permissioned data | Ask the AI a question the user is not allowed to see answered | | Open API and webhooks | REST APIs, webhooks | Custom automation | Documented, versioned APIs | Read the API docs during the demo | ### Native connector, API, or partner build A native connector is built, tested, and maintained by the vendor, with release notes. An API integration means your team or a systems integrator builds and maintains the mapping. A partner build is owned by a third party. SharePoint-based platforms, for example, rely on Power Automate for workflow depth, which adds IT dependency; some vendors price integrations separately or route them through an integration broker. Ask which model applies to every system on your list and who is accountable when a field mapping changes. ### Keep or replace the incumbent HRIS and WFM? For most enterprises, keep. The HRIS remains the system of record and the digital workplace platform becomes the layer employees touch. A platform with native scheduling, tasks, and training gives you the option to retire separate tools later without forcing the decision now. ## The 9 digital workplace platforms with the best HR and IT integrations for frontline enterprises | Platform | Category | Best for | HR integrations (named) | Identity and IT (named) | Frontline access without corporate email | Operations workflows | Ideal size | |---|---|---|---|---|---|---|---| | [MangoApps](https://www.mangoapps.com/) | Unified workforce platform | Frontline and desk employees on one platform | Workday, UKG, ADP, Paylocity, Namely, BambooHR, SAP SuccessFactors, Rippling | Okta, Entra ID, AD, LDAP, SAML, OIDC; Microsoft 365; Google Workspace; ServiceNow-class ITSM via 200+ integrations | Yes | Native | 1,000 to 100,000+ | | [Microsoft 365 with Viva](https://www.microsoft.com/en-us/microsoft-365/sharepoint/collaboration) | Intranet and EX platform | Microsoft 365-standardized enterprises | Via Viva and Power Platform connectors | Entra ID native; Teams, SharePoint, OneDrive | Partial (depends on Teams and licensing) | Partner (Power Automate) | Any, IT-resourced | | [Staffbase](https://staffbase.com/) | Intranet and communications platform | Large mixed workforces, multichannel publishing | HRIS via integration (vendor-stated) | Microsoft 365 depth: Teams, SharePoint, Copilot, Power BI | Partial | Partner | Medium to large | | [Unily](https://www.unily.com/) | Employee experience platform | Complex global enterprises with deep governance needs | Vendor-stated | Azure OpenAI and Workgrid integrations; Microsoft 365 | Partial | Partner | 10,000+ | | [LumApps](https://www.lumapps.com/) (with Beekeeper) | Employee communications and frontline hub | Communication-first with broad integrations; Beekeeper for frontline | Workday, SAP (vendor-stated), 100+ productized integrations | Microsoft 365 and Google Workspace | Partial (Beekeeper: Yes) | Partner | 2,000+ | | [Simpplr](https://www.simpplr.com/) | SaaS intranet | Fast deployment, low IT overhead | Vendor-stated | Vendor-stated | Partial | Partner | Mid-sized | | [Workvivo](https://www.workvivo.com/) (Zoom) | Social intranet | Culture and engagement, Zoom-centric organizations | Vendor-stated | Zoom, Microsoft 365, Google Workspace | Partial | Partner | Large | | [WorkJam](https://www.workjam.com/) | Frontline digital workplace | Enterprise retail and hospitality operations | Enterprise HRIS and WFM (vendor-stated) | Vendor-stated | Yes | Native (scheduling, tasks) | Enterprise frontline | | [Flip](https://www.getflip.com/) | Frontline employee app | Fully branded app with HRIS mini-apps | Workday, SAP SuccessFactors, UKG (vendor-stated) | API-based (vendor-stated) | Yes | Partner (via HRIS) | Medium to large | *Integration, capability, hosting, and certification statements for third-party vendors are taken from each vendor's public documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps. "Partial" means frontline access exists but depends on configuration or licensing; "Partner" means operations workflows rely on a third-party system or automation layer.* ### MangoApps MangoApps is the AI-Ready Employee Platform for the Frontline: a unified platform that runs communication, knowledge, scheduling and time, tasks, training, and HR self-service natively for frontline and desk employees, on one login, with no corporate email required. Its integration posture is built for enterprises that intend to keep their HRIS and identity provider as systems of record and add the layer employees actually touch. **Best for:** Frontline-heavy enterprises of 1,000 to 100,000+ employees that want one platform for every employee and native operations workflows rather than a communication layer plus partners. **HR integrations:** [200+ out-of-the-box integrations](https://www.mangoapps.com/integrations), including Workday, UKG, ADP, Paylocity, Namely, BambooHR, SAP SuccessFactors, and Rippling for HRIS and payroll; Cornerstone and Workday Learning for learning; Rippling, BetterWorks, and Lattice for performance; Workhuman, WorkTango, and Achievers for recognition. **IT and identity integrations:** SAML 2.0 (Okta, OneLogin, Ping Identity), OAuth 2.0 and OpenID Connect, Active Directory, and LDAP; Microsoft Teams, SharePoint, OneDrive, Outlook, and Entra ID; Google Drive, Calendar, Meet, and SSO; SharePoint, OneDrive, Google Drive, Box, and Dropbox for files; OpenAI, Google Gemini, Anthropic Claude, and Azure OpenAI for AI. **Frontline connectivity without corporate email:** Yes. Identity is provisioned from the HRIS and activated on a personal phone or shared device; offline access, translation, kiosk, and digital signage included. **Operations workflows on the platform:** Native scheduling with AI-assisted creation, swaps, and geofenced clock-in; task management and store execution with photo verification; learning management; HR operations; knowledge management with permission-aware AI search. **Security and deployment:** HITRUST CSF, SOC 2 Type II, ISO 27001, FedRAMP ATO, HIPAA business associate agreements, and GDPR data processing agreements; SaaS, Private Cloud, Customer VPC, and On-Premise deployment; real-time audit logs, eDiscovery, legal hold, and retention policies, per [mangoapps.com/security](https://www.mangoapps.com/security). **Key considerations:** The platform delivers the most value adopted company-wide rather than by one department; plan configuration time to use its flexibility. Organizations that only want a communications layer on an existing Microsoft 365 intranet may find a narrower tool sufficient. **Proof:** 2M+ users; 98% customer retention; NPS 78; 90%+ adoption within 90 days backed by an [Adoption Guarantee](https://www.mangoapps.com/adoption-guarantee); Gartner Peer Insights 4.6/5; Gartner Magic Quadrant Visionary for Intranet Packaged Solutions (2025); IDC MarketScape Leader (2024); Forrester Wave Strong Performer (Q2 2026). A.S. Watson Benelux reached 80%+ active use across 16,000 Kruidvat retail employees with no corporate email; [Raley's](https://www.mangoapps.com/resources/raleys-case-study) connected 20,000 grocery employees. **Pricing:** Modular suites, quote-based. [Schedule a demo to see MangoApps in action](https://www.mangoapps.com/schedule-a-call) ### Microsoft 365 with Viva SharePoint and Viva form Microsoft's intranet and employee experience offering, deeply embedded in Microsoft 365. SharePoint provides content services and the page-based framework; Viva adds modules for communication (Viva Connections, Viva Engage), knowledge, learning, insights, and goals. **Best for:** Enterprises fully standardized on Microsoft 365 and Teams, with internal IT resources to configure and manage the intranet over time. **HR integrations:** Through Viva modules and Power Platform connectors to HRIS systems; depth depends on configuration and licensing. **IT and identity integrations:** Entra ID is native; Teams, SharePoint, OneDrive, and Outlook are the platform. **Frontline connectivity without corporate email:** Partial. Frontline access depends on Teams and Microsoft 365 frontline licensing, which many hourly workers do not have. **Operations workflows:** Via Power Automate and partner apps; scheduling through Teams Shifts. **Security and deployment:** Microsoft 365 compliance and security stack; regional tenancy. **Key considerations:** Deployment and configuration typically require internal IT or an implementation partner; full Viva functionality requires add-on licenses; the frontline experience depends heavily on implementation quality. **Pricing:** SharePoint is included in most Microsoft 365 enterprise plans; Viva modules are licensed separately per user, per module. ### Staffbase Staffbase is an enterprise employee communications and intranet platform with multichannel publishing to app, intranet, email, SMS, and signage, and deep Microsoft 365 integration. **Best for:** Medium to large organizations seeking a communications-first intranet with strong mobile, Microsoft 365 integration, and global deployment. **HR integrations:** HRIS via integration (vendor-stated). **IT and identity integrations:** Microsoft Teams, SharePoint, Copilot, and Power BI (vendor-stated). **Frontline connectivity without corporate email:** Partial; depends on configuration. **Operations workflows:** Partner. Scheduling, tasks, and training are not part of the platform. **Security and deployment:** ISO 27001 and SOC 2 Type II; EU hosting on Azure and AWS, per [staffbase.com/security](https://staffbase.com/security). **Key considerations:** Content governance and enterprise search are weaker than in dedicated intranet platforms; better suited to communications-driven use cases than knowledge management or operations. **Pricing:** Enterprise, quote-based; includes onboarding and customer success. ### Unily Unily is an intranet and employee experience platform built for large, complex organizations, with strong personalization, campaign management, and enterprise governance. **Best for:** Enterprises with 10,000+ employees, distributed teams, and defined ownership for intranet management. **HR integrations:** Vendor-stated; confirm named HRIS systems. **IT and identity integrations:** Native digital assistant integration with Microsoft Azure OpenAI and Workgrid; Microsoft 365 (vendor-stated). **Frontline connectivity without corporate email:** Partial. **Operations workflows:** Partner. **Security and deployment:** ISO 27001 and SOC 2 Type II, per [Unily's security certifications page](https://www.unily.com/policies/privacy-hub/security-certifications). **Key considerations:** Requires experienced administrators for a powerful but complex back end; AI, advanced integrations, and branding may add cost and effort. **Pricing:** Modular, user-based, quote-based. ### LumApps (with Beekeeper) LumApps is a communication-first intranet for mid-sized to large enterprises with 100+ productized integrations across Microsoft 365 and Google Workspace environments. [LumApps agreed to acquire Beekeeper](https://www.lumapps.com/insights/news/lumapps-and-beekeeper-to-join-forces-creating-the-leading-employee-experience-platform-for-the-future-of-work), the frontline-first mobile platform, on July 2, 2025. **Best for:** Large or mid-market enterprises seeking a communication-first platform with broad integrations, with Beekeeper covering frontline reach. **HR integrations:** Workday and SAP among 100+ productized integrations (vendor-stated); Beekeeper adds HRIS, LMS, and payroll integrations for frontline workflows (vendor-stated). **IT and identity integrations:** Microsoft 365 and Google Workspace. **Frontline connectivity without corporate email:** Partial for LumApps; Yes for Beekeeper. **Operations workflows:** Partner; Beekeeper provides no-code forms and workflows. **Key considerations:** Some customers report higher-than-expected setup effort; confirm how LumApps and Beekeeper are licensed and administered together as the integration proceeds. **Pricing:** Tiered, quote-based. ### Simpplr Simpplr is a SaaS intranet emphasizing fast deployment, intuitive content management, and minimal IT dependency, with AI features for personalization and analytics. **Best for:** Mid-sized organizations that want a modern intranet with strong communications and low IT overhead. **HR integrations:** Vendor-stated. **IT and identity integrations:** Vendor-stated; some users report integration gaps. **Frontline connectivity without corporate email:** Partial. **Operations workflows:** Partner. **Security and deployment:** ISO 27001:2022, per [Simpplr's security page](https://www.simpplr.com/security-compliance/). **Key considerations:** The packaged approach may limit flexibility in complex or heavily integrated environments; global support outside North America is still expanding. **Pricing:** Tiered by user count, quote-based; implementation typically included. ### Workvivo (Zoom) Workvivo is a communication-focused social intranet, now part of Zoom, emphasizing recognition, livestreams, and peer interaction, with a mobile app for frontline extension. **Best for:** Large organizations focused on culture and engagement, particularly those already using Zoom. **HR integrations:** Vendor-stated. **IT and identity integrations:** Zoom, Microsoft 365, and Google Workspace connectors; digital signage. **Frontline connectivity without corporate email:** Partial. **Operations workflows:** Partner. **Key considerations:** The emphasis on engagement leaves gaps for organizations that need workflow or task integration and structured knowledge management. **Pricing:** Business and Enterprise plans, quote-based. ### WorkJam WorkJam is a digital frontline workplace platform combining communications, shift scheduling, task management, and earned wage access for large hourly workforces. **Best for:** Enterprise retail, hospitality, and supply chain organizations whose buying decision is led by operations. **HR integrations:** Enterprise HRIS and WFM integrations (vendor-stated). **IT and identity integrations:** Vendor-stated. **Frontline connectivity without corporate email:** Yes; kiosk mode for shared devices. **Operations workflows:** Native scheduling, shift marketplace, tasks with photo verification, earned wage access. **Key considerations:** Communication is oriented to operational messaging; enterprises that also need a desk-worker intranet typically run WorkJam alongside another platform. **Pricing:** Enterprise, quote-based. ### Flip Flip is an AI-native frontline employee app published under the employer's brand, with HR mini-apps that surface HRIS data inside the app. **Best for:** Medium to large enterprises with dispersed frontline teams that want a fully branded mobile app and HRIS data inside it. **HR integrations:** Workday, SAP SuccessFactors, and UKG via HR mini-apps and API (vendor-stated); integrations priced separately (vendor-stated). **IT and identity integrations:** API-based (vendor-stated). **Frontline connectivity without corporate email:** Yes. **Operations workflows:** Partner; shift swapping and tasks exist but scheduling and pay are surfaced from the HRIS. **Key considerations:** Lacks page-based information architecture for structured desk content; live broadcasting is desktop-only for hosts (vendor-stated). **Pricing:** Per-user or banded tiers, quote-based. ## Integration depth matrix: which frontline employee platforms integrate with existing HR and IT systems? | Platform | Workday | UKG | ADP | SAP SuccessFactors | Okta / Entra ID SSO | SCIM provisioning | Microsoft 365 / Teams | Google Workspace | ServiceNow | Open API | |---|---|---|---|---|---|---|---|---|---|---| | MangoApps | Native | Native | Native | Native | Native | Native | Native | Native | Via integration | Yes | | Microsoft 365 with Viva | Via connector | Via connector | Via connector | Via connector | Native (Entra ID) | Native | Native | Not applicable | Via connector | Yes | | Staffbase | Via integration | Via integration | Via integration | Via integration | Native | Vendor-stated | Native | Via integration | Via integration | Yes | | Unily | Vendor-stated | Vendor-stated | Vendor-stated | Vendor-stated | Native | Vendor-stated | Native | Vendor-stated | Vendor-stated | Yes | | LumApps (with Beekeeper) | Native (vendor-stated) | Vendor-stated | Vendor-stated | Native (vendor-stated) | Native | Vendor-stated | Native | Native | Vendor-stated | Yes | | Simpplr | Vendor-stated | Vendor-stated | Vendor-stated | Vendor-stated | Native | Vendor-stated | Native | Native | Vendor-stated | Yes | | Workvivo | Vendor-stated | Vendor-stated | Vendor-stated | Vendor-stated | Native | Vendor-stated | Native | Native | Vendor-stated | Yes | | WorkJam | Vendor-stated | Vendor-stated | Vendor-stated | Vendor-stated | Vendor-stated | Vendor-stated | Vendor-stated | Vendor-stated | Not published | Yes | | Flip | Via HR mini-app | Via HR mini-app | Not published | Via HR mini-app | Vendor-stated | Not published | Vendor-stated | Not published | Not published | Yes | | Platform | Sign-in without corporate email | Shared-device or kiosk mode | Offline access | Translation | |---|---|---|---|---| | MangoApps | Yes | Yes | Yes | Yes | | Microsoft 365 with Viva | Partial (licensing) | Via Teams shared device | Partial | Yes (Microsoft) | | Staffbase | Partial | Vendor-stated | Vendor-stated | Yes (75+ languages, vendor-stated) | | Unily | Partial | Vendor-stated | Vendor-stated | Yes | | LumApps (with Beekeeper) | Beekeeper: Yes | Vendor-stated | Beekeeper: offline forms | Beekeeper: 200+ languages (vendor-stated) | | Simpplr | Partial | Vendor-stated | Vendor-stated | Yes | | Workvivo | Partial | Vendor-stated | Vendor-stated | Yes | | WorkJam | Yes | Yes (kiosk) | Vendor-stated | Yes | | Flip | Yes | Vendor-stated | Vendor-stated | Yes (30+ languages, vendor-stated) | *Both matrices reflect vendor documentation as of September 2026 and are vendor-stated, not independently verified by MangoApps. "Vendor-stated" without a mode means the vendor claims the integration but does not publish whether it is native or API-based; "Not published" means the vendor's public pages reviewed did not disclose it.* ## What are the top digital workplace platforms for deskless workforces and for large enterprises? For deskless-heavy enterprises, the shortlist is led by the platforms that combine no-email access with native operations workflows: MangoApps, WorkJam, and Flip, with LumApps' Beekeeper and Staffbase for communication-led programs. For large mixed enterprises standardized on Microsoft 365, the shortlist is Microsoft 365 with Viva, Unily, Simpplr, Staffbase, and MangoApps. MangoApps appears on both lists because it serves frontline and desk employees on the same platform. | If you are | Prioritize | Shortlist | |---|---|---| | 10,000+ employees, frontline-heavy, multi-site | No-email identity from the HRIS, native scheduling and tasks, acknowledgment by site, certifications | MangoApps, WorkJam | | Microsoft 365-standardized, knowledge-worker majority | Entra ID, Teams and SharePoint depth, governance | Microsoft 365 with Viva, Unily, Staffbase, MangoApps | | Mixed desk and frontline, want one platform | Both of the above on one login | MangoApps | | Regulated industry (healthcare, financial services, utilities) | HITRUST or FedRAMP where required, deployment options, audit and eDiscovery | MangoApps; Microsoft 365 with Viva for M365 shops | | Mid-market wanting low IT overhead | Packaged modules, non-technical administration | Simpplr, MangoApps, LumApps | | Culture and engagement led, Zoom-centric | Social feed, recognition, livestreams | Workvivo | For broader rankings see [25 Intranet Platforms Worth Evaluating in 2026](https://www.mangoapps.com/articles/top-25-intranet-platforms-frontline-desk-workers) and [Best Employee Intranet Platforms for Frontline Teams in 2026](https://www.mangoapps.com/articles/best-employee-intranet-frontline-teams). ## How to verify integration claims before you sign 1. **"Create a worker in the HRIS sandbox and show them appearing in the app with the right location and manager."** Strong: it happens in the demo. Weak: "the sync runs nightly, we can show you tomorrow." 2. **"Terminate that worker and show access removed."** Strong: same day, automatic. Weak: an administrator removes them. 3. **"Sign in as a worker who has no email address."** Strong: two minutes from a QR code or SMS. Weak: IT creates the account. 4. **"Open a ServiceNow ticket from the app and show it in ServiceNow."** Strong: created and tracked in both. Weak: a link to the portal. 5. **"Show me the connector's release notes and tell me who maintains it."** Strong: vendor-maintained with a changelog. Weak: a partner built it during implementation. 6. **"Search for a policy that lives in SharePoint, from a phone."** Strong: the answer with its source. Weak: "Not found." 7. **"Approve a shift swap here and show it in payroll."** Strong: written back. Weak: a link to the scheduler. 8. **"Ask your AI a question whose answer is in a document I cannot open."** Strong: it declines. Weak: it answers. ## Frequently asked questions **What is a digital workplace platform?** A digital workplace platform is the hub through which employees reach the systems they work in, connected through one login and one identity to the HRIS, identity provider, scheduler, service desk, learning system, and collaboration suite. It differs from an intranet, which is a destination, and an employee app, which is a channel to deskless workers. **What are the top digital workplace platforms for deskless workforces?** For deskless-heavy enterprises, MangoApps, WorkJam, and Flip lead because they combine sign-in without corporate email with native or HRIS-surfaced operations workflows. LumApps' Beekeeper and Staffbase serve communication-led programs. MangoApps is the unified option for organizations that also have desk employees. **What are the leading digital workplace platforms for large enterprises?** Large enterprises most often shortlist Microsoft 365 with Viva, MangoApps, Staffbase, Unily, LumApps, Simpplr, and Workvivo. Organizations standardized on Microsoft 365 with a knowledge-worker majority lean to Viva, Unily, and Staffbase; organizations with large frontline populations lean to MangoApps. **Which frontline employee platforms integrate with existing HR and IT systems such as Workday, UKG, and Microsoft 365?** MangoApps publishes native integrations with Workday, UKG, ADP, Paylocity, SAP SuccessFactors, Rippling, BambooHR, Microsoft 365, Google Workspace, Okta, Entra ID, Active Directory, and LDAP among 200+ integrations. Flip names Workday, SAP SuccessFactors, and UKG through HR mini-apps. Staffbase and Unily publish deep Microsoft 365 integration. For every vendor, ask whether each integration is native, API-based, or partner-built. **Can a digital workplace platform onboard employees who have no corporate email?** Yes, if identity is provisioned from the HRIS and workers can activate by SMS, QR code, or employee ID. MangoApps, WorkJam, Flip, and Beekeeper publish no-email sign-in. Microsoft 365 with Viva, Staffbase, Unily, Simpplr, LumApps, and Workvivo support frontline access with configuration or licensing dependencies. **Should we keep our HRIS and scheduling system or replace them?** Keep the HRIS as the system of record. Decide the scheduler separately. A platform with native scheduling gives you the option to retire a separate scheduler later without forcing the change now. **What is the difference between a native integration and an API integration?** A native integration is built and maintained by the vendor, with release notes. An API integration means the vendor exposes an interface and your team or a partner builds and maintains the mapping. Native integrations cost less to own and break less often when either system changes. **Which digital workplace platforms are SOC 2, ISO 27001, or HITRUST certified?** MangoApps publishes HITRUST CSF, SOC 2 Type II, ISO 27001, and FedRAMP ATO. Staffbase and Unily publish ISO 27001 and SOC 2 Type II; Simpplr publishes ISO 27001:2022. Microsoft 365 carries Microsoft's compliance portfolio. Certifications for third-party vendors are vendor-stated; verify current certificates during procurement. **What intranet features do employees actually use?** The 20 features below. The ones that most predict daily use are the mobile app with no-email access, AI search that returns answers, announcements with acknowledgment, forms and workflows, and the integrations that bring schedules, pay, and tickets into the same place. **How long does integration take?** Native HRIS and SSO connectors typically configure in days to a few weeks. API integrations and partner builds take longer and require ongoing maintenance. Ask each vendor for the implementation timeline of a reference customer with your HRIS. ## The 20 intranet features employees will love Not every organization needs all 20 at launch, but these are the features that determine whether the platform becomes the default workspace or another tool employees quietly avoid. ## 1. Personalized dashboard A personalized dashboard gives every employee a single starting point configured around their role. Widgets for announcements, tasks, quick links to frequently used tools, and team updates let employees see what is relevant to them without scrolling past noise from other departments. **Best for:** Organizations with diverse roles or departments where a one-size-fits-all home page creates friction. The initial configuration takes minutes; the ongoing time savings accumulate every day employees do not have to hunt for their starting point. ## 2. Mobile app with offline access Deskless workers are 70 to 80% of the global workforce, about 2.7 billion people, according to [BCG](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology), and 58% of American workers are on the frontline, according to [JLL](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention). For retail associates, field technicians, healthcare workers, and warehouse operators, the intranet has historically been inaccessible, requiring a corporate email address, a VPN, and a laptop that many of them simply do not have. A mobile app removes those barriers, allowing frontline employees to search for shift schedules, safety procedures, and HR policies on the same personal device they use for everything else. The access barrier is identity as much as device: the app must support [sign-in that does not depend on a corporate email account](https://www.mangoapps.com/articles/intranet-features-that-reach-frontline-workers). Offline capability matters for workers in areas with unreliable connectivity. A download-once, access-anywhere model brings the intranet to the employees who need it most. [Gallup](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) estimates the cost of replacing an employee at one-half to two times annual salary; a mobile experience that keeps frontline employees informed and connected is a retention investment, not a feature add-on. **Best for:** Any organization with frontline, deskless, or shift-based workers. For these employees, mobile access is the difference between having an intranet and not having one at all. ## 3. Employee directory A searchable employee directory gives everyone in the organization a way to find who does what, how to reach them, and what expertise they hold. Detailed profiles with photos, roles, department affiliations, and skill tags reduce the friction of cross-functional collaboration, particularly in larger organizations where employees may work alongside colleagues they have never met in person. **Best for:** Growing or geographically distributed organizations. A well-built directory also shortens onboarding time for new hires who need to build a network before their first 90 days is over. ## 4. Org charts An org chart does more than display hierarchy. It clarifies accountability and helps employees understand where their work fits in the broader structure. The most useful implementations allow browsing by person, department, location, and skill, with administrators controlling which details are visible to which groups. **Best for:** Larger organizations where structure is not self-evident to new employees. Dynamic org charts that sync automatically with HR systems eliminate the manual maintenance burden that leads most static org charts to go stale within months. ## 5. Company and department pages Company pages give every department, location, or function a structured space to publish resources, announcements, and documentation. Unlike shared drives, pages are designed to be browsed and followed: employees receive updates when content changes, and administrators control visibility at the role or group level. This breaks down the information silos between departments that send employees hunting through email threads and shared drives for documents they know exist somewhere. **Best for:** Organizations where knowledge is fragmented across SharePoint folders, email attachments, and informal chat channels. Pages create a single authoritative home for content that would otherwise drift, duplicate, and become unreliable. ## 6. Announcements and alerts Reaching your entire workforce with a time-sensitive message (a safety incident, a policy update, an emergency closure) requires more than email. An announcement and alert system lets administrators segment recipients by role, location, or department, choose delivery channels such as push notification, SMS, digital signage, or email digest, and track acknowledgment. For compliance-sensitive communications, confirmation tracking creates an audit record without manual follow-up, and acknowledgment records should be exportable for audit. For organizations managing distributed or shift-based workforces, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) outlines how internal comms teams are restructuring channel strategy to reach employees across locations and device types. **Best for:** Multi-location organizations, shift-based workforces, and any company with regulatory obligations around timely communication delivery. ## 7. Social feeds and news Social feeds consolidate individual, team, and company updates into a configurable stream. Employees can respond, tag colleagues, and take action in real time without switching to a separate tool. Flexible feed settings ensure employees see content relevant to their role rather than every notification from every team across the company. **Best for:** Distributed and hybrid teams where informal communication, the kind that happens in hallways and break rooms, needs a digital equivalent. When scoped correctly, social feeds reduce internal email volume and build community across locations that rarely interact in person. ## 8. Polls, surveys, and quizzes Collecting accurate feedback from a large, distributed workforce requires a mechanism that goes beyond an annual email survey. Built-in polls and surveys let managers and HR teams target specific audiences, analyze results in real time, and enable anonymous participation where candor matters. Quizzes extend this into training and compliance contexts, where confirming comprehension is as important as confirming receipt. **Best for:** HR teams conducting engagement surveys, managers measuring team sentiment, and compliance teams confirming that required training was absorbed and understood. Anonymous participation consistently yields higher response rates and more useful data than surveys tied to individual accounts. ## 9. Recognition and rewards Public recognition within the intranet creates a feedback loop that benefits both the recognized employee and the broader organization. When colleagues can see and respond to recognition in a shared feed, the signal about what the organization values becomes visible at scale, not just between a manager and a direct report in a private message. Programs that tie recognition to points or rewards add a participation incentive. **Best for:** Organizations focused on employee engagement and retention. High-turnover industries such as retail, healthcare, and hospitality see the clearest gains when recognition is embedded in the tools employees use daily rather than in a separate platform they have to remember to open. ## 10. Forms and automated workflows Digital forms and workflows replace the paper-based and email-routed processes that slow organizations down: expense approvals, onboarding packets, change requests, issue reports, and equipment requests. When these processes run through the intranet, they become trackable, auditable, and faster. Employees do not have to chase signatures or wonder where a request is sitting in the queue. Look for a no-code workflow builder that non-technical administrators can use; SharePoint-based platforms typically rely on Power Automate for this, which adds IT dependency. **Best for:** Operations-heavy organizations where manual routing creates bottlenecks. High-impact starting points include PTO requests, expense tracking, and new hire onboarding, processes with high volume, predictable logic, and measurable cycle times. ## 11. AI-powered search [SWOOP Analytics](https://www.swoopanalytics.com/sharepoint-bm-25) found that the average employee spends just under six minutes a day on their intranet. [Social Edge Consulting](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) found that only 13% of employees use their intranet daily and sets a minimum search-success benchmark of 75%. Poor search is the most common explanation for all three numbers. When employees cannot find what they are looking for quickly, they stop trying and ask a manager instead. AI-powered search addresses this by returning results based on intent rather than exact keyword matches. When an employee types "how do I request time off," the search engine understands the intent and surfaces the relevant policy, even if the document never uses that exact phrase. Federated search is itself an integration: SharePoint, Google Drive, Box, ServiceNow knowledge bases, and internal repositories return results through a single query without employees needing to remember which system holds which content. The governance requirement is that search and any AI assistant built on it inherit the user's permissions and answer only from content the user can already open; see [Your AI Agent Is Reading a Copy of Your Business](https://www.mangoapps.com/articles/ai-agents-native-data-vs-copies). **Best for:** Every organization. Search quality is the single feature that most directly determines whether employees use the intranet or work around it. ## 12. Content management system A CMS gives employees a single, structured location for company resources: policies, procedures, templates, job aids, and reference materials. The version control guarantee, that what they downloaded is the current version, is as important as the convenience. Content expiration dates, admin publishing workflows, and document ownership assignments prevent stale content from circulating alongside current materials. **Best for:** Compliance-heavy industries where document version control carries regulatory significance, and organizations that have absorbed the cost of employees acting on outdated policies or procedures. ## 13. Team workspaces Project-based workspaces give cross-functional teams a shared environment for collaboration: task lists, shared documents, team calendars, and discussion threads in one place. This reduces the coordination overhead of managing projects across email, chat, and shared drives simultaneously. Managers can see project status without scheduling a check-in; team members can see what their peers are working on without interrupting them. **Best for:** Organizations running complex projects across departments or time zones. Workspaces are equally effective for standing functions such as HR, facilities, and finance, where ongoing collaboration benefits from a persistent shared environment. ## 14. Learning management system An LMS embedded in the intranet removes the context-switch barrier to training completion. Employees access courses, certifications, and compliance training in the same environment where they do everything else, not a separate platform with a separate login. Onboarding paths can be automated so new hires receive the right materials in sequence, and training is assigned automatically by role and location from the HRIS, so administrators do not touch each assignment. Completions written back to the employee record give HR a reliable compliance picture. **Best for:** Regulated industries with mandatory certification requirements, and high-growth organizations where onboarding volume makes manual training management unsustainable. ## 15. Analytics and insights Intranet analytics answer the questions administrators need to act on: Which content are employees actually reading? Which departments and locations have the lowest active use? Which announcements drove the most engagement? Which search terms return zero results? Without this data, improvements are driven by assumption rather than evidence. **Best for:** Organizations looking to improve intranet adoption after launch. Analytics are most valuable when a baseline is established at go-live; without one, it is difficult to attribute adoption changes to specific interventions or to make a credible ROI case for continued investment. ## 16. Employee advocacy Advocacy features let engaged employees share company content to their personal social channels directly from the intranet. For marketing teams trying to extend organic reach, and for recruiting teams building employer brand through employee networks, this creates a distribution channel that is more credible than branded content. **Best for:** Organizations in competitive talent markets where employer brand influences recruiting outcomes, and B2B companies where buyer trust is built partly through employee-generated content. ## 17. Third-party integrations An intranet that requires employees to leave it to access their core tools undermines the value of a central workspace. For frontline enterprises, integrations are the difference between a portal and a platform. - **HRIS as the source of truth.** Workday, UKG, ADP, SAP SuccessFactors, Paylocity, and Oracle HCM should drive identity, org structure, targeting, and permissions through scheduled and event-driven sync, with SCIM provisioning and deprovisioning on termination day. - **Identity for workers without email.** Single sign-on using SAML 2.0 or OpenID Connect through Okta or Microsoft Entra ID, combined with Active Directory or LDAP sync, covers desk staff. Frontline staff need HRIS-provisioned credentials activated by SMS, QR code, or employee ID. - **Scheduling and WFM coexistence.** Schedules from UKG, Kronos, or Legion visible in the intranet, with swaps and approvals written back to payroll, or native scheduling that replaces them. - **ITSM.** ServiceNow tickets created and tracked from the intranet, so a broken register or a missing badge does not require a phone call. - **Collaboration suites.** Microsoft Teams, SharePoint, OneDrive, and Outlook, or Google Workspace, embedded rather than duplicated, with federated search across them. - **Data and AI.** BI export to Tableau and Looker; AI connectors (OpenAI, Azure OpenAI, Gemini, Anthropic) grounded in the platform's permissioned data. Deep integrations let employees complete their work without switching applications and keep provisioning synchronized as people join, change roles, or leave. See the [integration checklist](#the-hr-and-it-integration-checklist-for-frontline-enterprises) above and [MangoApps integrations](https://www.mangoapps.com/integrations). **Best for:** Frontline enterprises with complex tool stacks where application switching is a measurable productivity drag and where most employees have no corporate email. Integrations also reduce IT support burden by centralizing authentication and reducing password reset volume. ## 18. Security, permissions, and governance Security is the feature employees notice most when it fails and least when it works. Role-based access controls ensure that HR documents surface only for HR staff, that executive materials appear only for appropriate access levels, and that restricted content stays restricted regardless of the search term that triggered the query. Content governance tools, including publishing workflows, expiration dates, and admin audit logs, prevent the intranet from becoming an unmanaged repository of conflicting, outdated documents. For organizations in regulated industries, HIPAA-aligned access controls, LDAP and Active Directory sync, and audit trails are procurement requirements rather than optional features. So are recognized certifications (SOC 2 Type II and ISO 27001 as a baseline, HITRUST for healthcare, FedRAMP for public sector) and a choice of deployment models: SaaS, private cloud, customer VPC, or on-premise. MangoApps publishes all of these on its [security page](https://www.mangoapps.com/security). The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report), which reviews 37 platforms, provides independent evaluation of how modern intranet platforms handle permissions and governance architecture across enterprise environments. **Best for:** Any organization with regulated data, complex role structures, or compliance obligations around information access. Security and governance should be evaluated as non-negotiable baseline requirements, not features to add after deployment. ## 19. Accessibility and language support A diverse workforce communicates in multiple languages and includes employees who rely on assistive technologies. Text translation, text-to-speech, and subtitling on video content are the difference between an intranet that reaches your entire workforce and one that reaches a portion of it. Supporting a wide range of languages removes the practical barrier that keeps non-English-speaking employees from engaging with company communications. **Best for:** Organizations with multilingual workforces, global operations, or a frontline population that includes employees across language backgrounds. Language support also matters for equity: an intranet that communicates safety and HR policies only in English is not fully serving the employees who need that information most. ## 20. Easy administration and branding Intranet administrators should not require IT involvement for routine changes: updating branding, adjusting navigation, enabling features, managing user groups, or configuring a new workflow. Traditional intranet deployments have taken months, strained IT teams, and produced static configurations that required developer resources to adjust. A modern admin console gives authorized administrators self-service control without that overhead. Branding customization, including logos, colors, navigation labels, and layout, lets organizations reflect their identity consistently throughout the tool and in the app stores. **Best for:** Organizations without dedicated IT resources for intranet maintenance, and larger organizations where IT involvement in routine changes creates a backlog that slows content and configuration updates. ## How to match features and platforms to your organization's priorities Not every organization needs all 20 features at launch. The features that deliver the fastest return depend on the problems you are trying to solve and the workforce you are serving. A practical starting point: identify the three most common ways employees lose time or get disconnected from the information they need. The features that directly address those friction points belong in your first deployment. Features such as advocacy and advanced analytics are valuable additions once the core is working, not prerequisites for a successful launch. Then map the priority to a platform archetype. If the friction is frontline reach and operations, a unified workforce platform such as MangoApps or an operations-first platform such as WorkJam fits. If the friction is knowledge-worker collaboration inside Microsoft 365, Microsoft 365 with Viva, Unily, or Staffbase fits. If it is culture and engagement, Workvivo fits. If it is speed of deployment with low IT overhead in a mid-sized organization, Simpplr or LumApps fits. Organizations that measure intranet performance before and after each deployment stage get significantly more from their investment than those that rely on informal feedback. Define what "findable" and "reachable" mean for your workforce before go-live, measure it consistently by location, and act on what the data shows. ## Sources - Social Edge Consulting, [Top 12 Intranet KPIs and Metrics](https://www.socialedgeconsulting.com/post/intranet-kpis-and-metrics) (2025) - SWOOP Analytics, [2025 SharePoint Intranet Benchmarking Report](https://www.swoopanalytics.com/sharepoint-bm-25) - Okta, [Businesses at Work 2025](https://www.okta.com/newsroom/articles/businesses-at-work-2025/) - Harvard Business Review, [How Much Time and Energy Do We Waste Toggling Between Applications?](https://hbr.org/2022/08/how-much-time-and-energy-do-we-waste-toggling-between-applications) (2022) - Deloitte, [Frontline Worker Productivity Enabled by Technology](https://www.deloitte.com/us/en/services/consulting/blogs/human-capital/frontline-worker-technologies-for-productivity.html) - BCG, [Facing the Deskless Labor Shortage with Technology](https://www.bcg.com/publications/2024/facing-deskless-labor-shortage-with-technology) (2024) - JLL, [Leading practices for frontline workforce engagement and retention](https://www.jll.com/en-us/insights/leading-practices-for-frontline-workforce-engagement-and-retention) (2025) - Gallup, [This Fixable Problem Costs U.S. Businesses $1 Trillion](https://www.gallup.com/workplace/247391/fixable-problem-costs-businesses-trillion.aspx) (2019) - ClearBox Consulting, [2026 Intranet and Employee Experience Platforms Report](https://www.clearbox.co.uk/2026-intranet-report-clearbox/) - LumApps, [LumApps and Beekeeper to Join Forces](https://www.lumapps.com/insights/news/lumapps-and-beekeeper-to-join-forces-creating-the-leading-employee-experience-platform-for-the-future-of-work) (July 2025) - Vendor security pages: [MangoApps](https://www.mangoapps.com/security), [Staffbase](https://staffbase.com/security), [Unily](https://www.unily.com/policies/privacy-hub/security-certifications), [Simpplr](https://www.simpplr.com/security-compliance/) --- # MangoApps Named a Leader By IDC MarketScape in Experience-Centric Intelligent Digital Workspaces **Author:** MangoApps **Published:** 2024-01-23 **Category:** press-release Empowering the future of work, MangoApps is transforming digital workspaces with innovative, experience-centric solutions. # MangoApps Named a Leader By IDC MarketScape in Experience-Centric Intelligent Digital Workspaces MangoApps has been recognized as a Leader in the IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment. We are sharing what that designation means in context — not as a credential to display, but as a framework for understanding why experience-centric architecture matters in a market where most intranets fail the employees they are meant to serve. The analyst recognition is meaningful. But the more useful context for enterprise buyers is what the IDC evaluation criteria reveal about the problem these platforms are built to solve and what separates high-adoption from low-adoption digital workspaces at scale. ## The adoption paradox at the center of the intranet market Per Social Edge Consulting research, 91% of organizations operate an intranet. The same research shows that only 13% of employees use one daily, and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends six minutes per day using intranet tools. Those three numbers describe the same problem from different angles. Organizations have built digital workspaces and achieved almost no adoption. And non-adoption is not a neutral outcome — it means communication campaigns do not reach the employees they are written for, training content sits in portals nobody opens, and knowledge management investments produce no operational return. Per IDC research, employees spend an average of 2.5 hours per day searching for information. That number does not move unless the platform designed to resolve it is one employees actually open. A digital workspace that requires a corporate device, a VPN connection, or navigation flows designed for IT administrators rather than frontline workers is a workspace that most of the workforce will route around regardless of how many features it has. Experience-centric architecture is the IDC MarketScape's framework for what separates platforms that close this gap from those that perpetuate it. The assessment methodology evaluates whether a vendor's architecture puts employee experience at the center in ways that produce measurably different adoption and outcome data — not whether the platform satisfies an RFP checklist. ## What the IDC outcome data quantifies The outcomes data in the IDC MarketScape grounds the recognition in operational terms. Organizations deploying experience-centric intelligent digital workspaces have seen a 40% increase in employee productivity and operational efficiency, a 34% improvement in customer experience, and a 31% enhancement in employee experience. These are not projected outcomes — they reflect what organizations have measured after deployment. The productivity number maps directly to the information search problem: recovering even a fraction of the 2.5 hours employees currently spend searching for information each day produces measurable output increases without adding headcount or tooling. The customer experience improvement reflects an effect that is indirect but consistent — employees who can access current information and communicate without friction produce better customer outcomes. The employee experience improvement tracks with adoption: platforms employees actually use generate engagement data; platforms they avoid generate disengagement. The IDC MarketScape assessment scores vendors on both current capabilities and forward strategy. MangoApps' Leader placement reflects where the platform stands today — and, in the assessment's view, where it is positioned to continue delivering as the market evolves. ## What the Leader placement reflects architecturally The IDC assessment identified three platform dimensions in MangoApps that informed the recognition. **Content and personalization.** MangoApps provides content authors a block editor to manage branded microsites with templates for consistent production across teams and regions. Generative and general AI capabilities are integrated throughout the platform for information access, writing assistance with source notation, accessibility features, personalized recommendations, compliance controls, and security governance. Frontline workers are supported through a mobile app and interactive forms designed for employees who do not have a company email address — a meaningful distinction in industries where most of the workforce is in the field rather than at a desk. **Data architecture and integration depth.** The IDC assessment noted that MangoApps "has been used by clients as a secure unified digital work hub integrated to 200+ enterprise systems allowing them to sunset other costly tools." That integration breadth reflects an architectural choice: MangoApps operates as the layer that consolidates communication, content, task management, and app access into a single authenticated experience rather than adding another tool to an already fragmented stack. Clients extend the platform with custom microapps and API webhooks and can apply CSS-level customization for branding and navigation without requiring engineering resources proportional to the customization scope. **Workspace features for engagement.** MangoApps supports employee recognition aligned to company core values, a rewards store, and in-context polls — tools for engagement that operate inside the daily workflow rather than as a separate system requiring a separate login. The mobile experience mirrors the desktop interface for individualized widgets, company-wide mandatory news, and task dashboards, giving frontline workers functional parity with desk-based colleagues rather than a reduced mobile version. ## Security and AI as structural differentiators Per Emergence Capital research, 80% of the global workforce is deskless. That figure reframes the intranet category: a workspace designed for desk-based employees behind a corporate VPN misses the majority of the workforce by architecture. Experience-centric design means reaching employees on a mobile device in a distribution center, on a hospital floor, or at a retail location — with the security guarantees that enterprise IT requires and that frontline workers do not need to think about. MangoApps' SAML 2.0, OAuth 2.0, and enterprise SSO integrations treat security as infrastructure rather than a configuration option unlocked at higher pricing tiers. Role-based access controls, audit logs, and compliance-grade data handling are part of the standard platform. The IDC designation of MangoApps as a "secure unified digital work hub" reflects a real competitive position: the secure intranet narrative is now contested across multiple vendor categories, and the distinction between security built into the architecture and security marketed as a feature matters for enterprise IT and procurement teams who need documentation, not positioning language. The AI architecture follows the same structural logic. MangoApps connects to OpenAI, Google Gemini, Anthropic, and Azure OpenAI — multi-engine connectivity that matters when enterprise procurement requirements, data residency rules, or regional compliance constraints limit which AI providers an organization can use. AI capabilities in MangoApps are embedded across search, writing assistance, content recommendations, and accessibility tools — not a standalone module added to a pre-AI platform, but an AI layer integrated into the workflows where the productivity return is actually realized. ## Three questions to bring into any digital workspace evaluation The IDC MarketScape recommends MangoApps for organizations that are "midsize to large enterprise with both desk and deskless workers who need access to multiple apps integrated into a single company-branded AI-enabled digital workspace." That recommendation narrows the evaluation considerably for buyers whose actual criteria include frontline reach, integration breadth, and AI flexibility alongside standard collaboration feature comparisons. Three questions worth investigating during any active platform evaluation: **What is your current platform's actual daily adoption rate?** Per Social Edge Consulting, 13% of employees using an intranet daily is the industry average. If your platform performs at or below that figure, the problem is experience design, not content volume. The [American College of Radiology case study](/resources/case-study-american-college-radiology) walks through what targeted adoption work looked like in a complex, multi-site healthcare organization deploying a unified workspace — the outcomes reflected architectural choices, not publishing frequency. **How does the platform handle frontline access?** An [employee app](/solutions/employee-app) built for desk-based workers effectively excludes 80% of the workforce. Evaluate whether the platform's mobile experience is a functional equivalent to the desktop or a reduced version — the difference determines whether communication and task tools actually reach frontline employees, and whether the engagement data you track reflects actual organizational reach or desk-worker-only adoption. **What is your AI dependency model?** A platform that routes all AI requests through a single provider gives organizations no optionality when contracts, regional compliance rules, or model performance standards change. Multi-engine AI connectivity is increasingly a procurement requirement rather than a preference — evaluate whether a vendor's AI roadmap includes model flexibility or commits the organization to a single-provider dependency without a migration path. For independent evaluation criteria applicable to the dimensions the IDC MarketScape assessed, the [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides a framework that enterprise technology buyers can apply directly to platform selection decisions. ## What this recognition reflects in the broader market MangoApps has received recognition across multiple independent assessments this cycle. The [Forrester Wave intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) covers overlapping but distinct criteria — the IDC MarketScape focuses specifically on experience-centric architecture and the workforce reach outcomes that architecture produces. Both assessments reflect a consistent picture of where MangoApps positions in a market that is consolidating around unified, AI-enabled, frontline-accessible platforms. The gap between 91% intranet ownership and 13% daily adoption is not narrowing on its own. Experience-centric architecture is the mechanism that changes that ratio — and the IDC assessment provides an independent framework for evaluating which platforms are actually built to close that gap rather than claiming to. The full excerpt from the IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment (Doc#US49741923, January 2024) is available through MangoApps' resource library for organizations that want to apply the evaluation criteria to their own platform decisions. --- # Preventing Corporate Crisis with an Employee App **Author:** Christos Schrader **Published:** 2023-12-21 **Category:** employee-app Air travel during the holidays often comes with challenges and tribulations. In 2022, though, badly timed storms across the US mixed with high passenger volumes and airline staff that were still recovering from the effects of the pandemic. The result was a perfect storm of chaos and cancellations, resulting in an unprecedented number of people […] # Preventing Corporate Crisis with an Employee App When Southwest Airlines canceled over 16,900 flights between December 21 and 31, 2022—affecting nearly 2 million passengers—the company identified three root causes: being underprepared for severe weather, an inability to reshuffle planes and crews quickly enough, and **communication gaps among teams**. The first two problems are hard to solve with software. The third one is not. This article examines what adequate [employee communications infrastructure](/solutions/employee-communications) actually looks like, why most organizations still lack it, and what the operational and financial cost of that gap can be. --- ## What the Southwest Meltdown Actually Reveals About Communication Infrastructure Southwest ultimately paid $140 million in civil penalties on top of $600 million already paid out to passengers. That total dwarfs the annual cost of any enterprise intranet or employee app platform by orders of magnitude. Yet the communication failure at the center of the crisis was not exotic. Flight crews stranded across the country had no clear instructions on where to go or what to do. Gate agents facing thousands of angry passengers had no real-time updates from headquarters and were forced to improvise, spreading inconsistent and often incorrect information. The systems Southwest relied on could not handle the volume and velocity of changes happening simultaneously across dozens of airports. This is not a story unique to airlines. According to Social Edge Consulting, 91% of organizations operate an intranet—but nearly a third of employees never log in to it, and only 13% use it daily. IDC research puts the average time employees spend searching for information at 2.5 hours per day. SWOOP Analytics found that the average daily time spent actually using intranet tools is just six minutes. The infrastructure exists in most organizations. The adoption and utility do not. --- ## Why Frontline Workers Bear the Worst of a Communication Breakdown According to Emergence Capital, 80% of the global workforce is deskless—working in roles like flight operations, retail, healthcare, logistics, and manufacturing where they are rarely at a desk with reliable access to corporate systems. These are exactly the workers who most need real-time information during a crisis, and they are the least likely to receive it through traditional channels. Southwest's stranded flight crews almost certainly lacked access to corporate devices mid-crisis. Gate agents at airports across the country had no single source of truth to consult. When the cascade of failures accelerated, the communication infrastructure simply could not reach the people who needed it most. Replacing a single frontline employee costs between $4,400 and $15,000 (per industry estimates cited on the MangoApps mobile app product page). Communication failures that drive turnover compound the operational cost of a crisis well beyond the incident itself. The Southwest meltdown is an extreme case, but the underlying dynamic—frontline workers left without information, making decisions in a vacuum—plays out at smaller scale in organizations across every industry, every day. For a broader look at how these workforce dynamics are shifting, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how distributed and deskless teams are reshaping operational planning. --- ## What a Modern Employee App Actually Does During a Crisis A modern [employee app](/solutions/employee-app) addresses the Southwest scenario through three specific capabilities. ### 1. Mobile Access Without a Corporate Device or Email MangoApps works on personal devices without requiring a corporate email address. This matters directly in the scenario described above: stranded crew members and off-site gate agents can access company resources, SOPs, and real-time updates from their own phones. There is one place to find current policy information, with content governance ensuring that employees are always looking at the latest version—not a cached or outdated document. AI-powered universal search and an AI assistant surface the right information in seconds. During a cascade failure, the difference between a gate agent finding the correct passenger rebooking protocol in 10 seconds versus spending 20 minutes on hold with a supervisor is the difference between a managed situation and a public-relations disaster. Large enterprises that have consolidated 200 or more disparate systems into a single mobile dashboard report measurable gains in operational coordination speed (per MangoApps case study data from the TeamHealth consolidation). A branded employee app can achieve 90% frontline adoption within the first six months of deployment, as demonstrated in large-scale enterprise rollouts (per Unily/CVS case study data). ### 2. Emergency Alerts With Read-Receipt Tracking When something unexpected happens, an emergency alert can reach every affected employee in seconds. Critically, administrators can track in real time who has seen the alert and who has not—enabling follow-up with specific individuals or locations that have not acknowledged the message. This capability is the direct answer to the Southwest scenario: rather than relying on a phone tree or hoping that a supervisor at one airport relays information to another, a single alert reaches every gate agent, every stranded crew member, and every relevant manager simultaneously. ### 3. A Single Source of Truth for Consistent Messaging One of the most damaging aspects of the Southwest crisis was the inconsistency of information reaching passengers. Gate agents improvised because they had nothing else to work with. A shared, versioned document—accessible via a permanent link—allows leadership to update the official response in real time as a situation develops. Every employee consulting that document sees the same current information. Alerts can be pushed to all relevant parties each time the document is updated. This approach directly addresses the SOP operations challenge that large distributed employers face: keeping standard operating procedures current and accessible when conditions are changing faster than traditional communication channels can keep up. For organizations in regulated or high-stakes industries, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring their crisis and change communication frameworks. --- ## The Business Case: Quantifying the Cost of the Gap The Southwest example makes the ROI argument almost too easy—$740 million in total penalties and payouts versus the annual cost of an enterprise communication platform. But the business case holds even in less dramatic circumstances. IDC's finding that employees spend 2.5 hours per day searching for information translates directly to labor cost. For a distributed workforce of 10,000 frontline employees, even a 30-minute daily reduction in information-search time represents millions of dollars in recovered productivity annually. Enterprises that have deployed unified intranet and communications platforms have reported $20 million in cost avoidance, and British Airways reported a 30-point increase in employee engagement score following deployment of a unified employee experience platform. The comparison is not between "buying software" and "not buying software." It is between a communication infrastructure that works under pressure and one that fails at exactly the moment it is needed most. MangoApps has been recognized in independent evaluations of intranet and employee experience platforms—see the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) for context on how platforms in this category are evaluated. --- ## Frequently Asked Questions ### Does an employee app replace an intranet? Not exactly. An intranet—broadly defined as a private internal network for sharing company information—is the underlying concept. A modern employee app is the delivery mechanism that makes intranet content accessible to frontline workers who are not at a desk. The two are complementary: the intranet provides the content architecture and governance; the employee app provides the mobile-first access layer that actually reaches deskless workers. The low daily usage figures from SWOOP Analytics (six minutes per day) reflect what happens when intranet content exists but the access experience is poor. ### What should a crisis communication plan include? At minimum, a functional crisis communication plan for a distributed workforce needs: (1) a defined alert channel that reaches all employees regardless of location or device, (2) a single versioned document that serves as the official source of truth and can be updated in real time, (3) read-receipt or acknowledgment tracking so leadership knows who has received critical information, and (4) clear role assignments for who is authorized to send alerts and update official guidance. The Southwest failure illustrates what happens when none of these four elements are in place simultaneously. ### How long does it take to deploy an employee app at scale? Based on large-scale enterprise rollouts, a branded employee app can reach 90% frontline adoption within the first six months of deployment (per Unily/CVS case study data). The critical variables are whether the platform works on personal devices without corporate email (which removes the largest barrier to frontline adoption) and whether the initial content architecture is set up to surface the information employees actually need, rather than replicating the structure of an existing intranet that employees already avoid. --- ## The Concrete Next Step The Southwest Airlines crisis is a useful case study precisely because it is so large and so well-documented. But the communication failure at its core—frontline workers without real-time information, no single source of truth, no way to confirm that critical updates had been received—is not unusual. It is the default state for most organizations that have not deliberately built a communication infrastructure designed for distributed, deskless teams. The question is not whether your organization will face a high-pressure operational situation. It is whether your communication infrastructure will hold when that situation arrives. If your current intranet has a 13% daily usage rate and your frontline workers need a corporate device to access it, the answer is probably no. Reviewing your current employee communication stack against the four crisis-communication criteria above is a practical starting point. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) provides a framework for that audit. --- # The Top 5 Must-See Sessions at NRF 2024 **Author:** Andy Tolton **Published:** 2023-12-11 **Category:** news-and-updates The National Retail Federation’s Big Show – NRF 2024 – is just around the corner. As a proud sponsor, MangoApps is thrilled to be a part of this year’s lineup of enlightening sessions. NRF 2024 is the perfect opportunity to gain insights from retail leaders on the latest trends and best practices. In preparation for […] # The Top 5 Must-See Sessions at NRF 2024 The National Retail Federation's Big Show — NRF 2024 — is just around the corner. As a proud sponsor, MangoApps is thrilled to be a part of this year's lineup of enlightening sessions. NRF 2024 is the perfect opportunity to gain insights from retail leaders on the latest trends and best practices in [employee engagement](/solutions/employee-engagement), frontline operations, and retail technology. In preparation for the event, we've handpicked the top-five sessions you can't afford to miss at NRF 2024. ## 1. MangoApps' Featured Session – Transforming Frontline Operations: How AutoZone and PetSmart are Redefining Employee Experience **Monday, January 15, 1:00 pm – 1:30 pm** **North Javits, Level 4, Room 404, CommerceHub Stage** Join us for a deep dive into the transformative operations of AutoZone and PetSmart — companies that have successfully revamped the frontline experience for over 150,000 employees. During this session you'll learn from visionary executives from both enterprises as they outline the pressing challenges that prompted change and the remarkable journeys they took to find groundbreaking solutions. From pinpointing urgent issues to strategizing and executing sustainable solutions, learn firsthand the strategies employed to breathe new life into their operations. This session is particularly relevant given that 80% of the global workforce is deskless, per Emergence Capital — exactly the profile of AutoZone and PetSmart store associates who need mobile-native, no-email access to company information and training. Retailers that consolidate fragmented tools into a single [employee experience platform](/industries/retail) reduce the number of disconnected systems employees navigate daily from 6–8 apps to one. By the session's end, you'll have the insights and strategies needed to spearhead a frontline revolution of your own. ## 2. Keynote Session – Doubling Down on Retail with Levi Strauss & Co. **Sunday, January 14, 9:00 am – 9:30 am** Joining Levi Strauss & Co. in early 2023, president Michelle Gass came from Kohl's as the company's former CEO. Under a meticulously designed succession plan from retiring CEO Chip Bergh, Michelle brings her leadership skillset from successful senior roles at Proctor and Gamble, Starbucks, and most recently Kohl's. Speaking for the first time since joining the 170-year-old iconic brand, Michelle will share how she plans to accelerate growth by sharpening the focus of the current strategies to lean into the power of its brand, become the destination for denim lifestyle across all channels, and fuel diversification through international markets. Don't miss this opportunity to hear from a leader who is propelling Levi Strauss & Co. into a new era of success. ## 3. Keynote Session – Cultivating a Thriving Workplace and Purpose-led Company Culture **Tuesday, January 16, 9:30 am – 10:00 am** In the fast-paced world of business, it is valuable to learn from those who have achieved great success. Arianna Huffington, Founder and CEO of Thrive Global and founder of The Huffington Post will be joined on stage by Signet Jewelers CEO Gina Drosos and The Honest Company CEO Carla Vernón to discuss building a foundation of well-being as a leader of an organization and creating a culture for anyone to thrive in the workplace. For teams thinking about employee engagement training and how to embed well-being into daily operations, this session offers a rare look at how purpose-led culture translates into measurable business outcomes. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) explores similar themes for HR leaders planning their people strategy. ## 4. Featured Session – Leading Through Transformation, From Local Relevance to Global Purpose: The Kmart Australia Story **Sunday, January 14, 10:30 am – 11:00 am** Learn how Kmart Australia doubled down on clarity of purpose and innovation to develop a strategic blueprint and operational architecture to transform its business model, moving it from a traditional discount chain to an innovative, modern, hybrid retailer. Join Ian Bailey, Managing Director of Kmart Group Australia as this session offers takeaways on how to overcome barriers, challenge the status quo, guidance on leadership and adopting technology solutions to empower the organization. Teams looking to improve sop operations and standardize processes across distributed store networks will find this session especially actionable. ## 5. Featured Session – Reinventing Retail for the AI Generation **Sunday, January 14, 11:20 am – 11:50 am** Retailers are entering a new phase of technological innovation — with artificial intelligence and machine learning at its core. AI has emerged as the most effective way for retailers to turn data into value. Join Anshu Bhardwaj, Senior Vice President and COO of Walmart, in this session to learn how Walmart is using AI to drive growth and competitive advantage across the business. For context on how AI connects to frontline employee engagement software and daily workflows, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) is worth reviewing before you attend. ## Visit MangoApps @ NRF 2024 These sessions represent just a taste of what NRF 2024 has to offer. We invite you to visit MangoApps at booth #4053 on Level 3 of the Expo Hall and don't forget to join us for our featured session Monday afternoon. For more information about NRF and to plan your schedule, visit our [retail industry solutions page](/industries/retail) to see how MangoApps supports frontline employee engagement and operations before you arrive. See you at NRF 2024 in New York City! ## How Do I Prepare to Get the Most Out of NRF 2024? Before you arrive, it helps to map your session priorities against your organization's current challenges. If frontline employee engagement and training on employee engagement are top of mind, anchor your schedule around Session 1 (MangoApps/AutoZone/PetSmart, Monday 1:00 pm) and Session 3 (Arianna Huffington/Thrive Global, Tuesday 9:30 am). If retail transformation and AI are your focus, Sessions 4 and 5 on Sunday morning run back-to-back and cover both strategic and operational angles. Note that Sessions 2, 4, and 5 all fall on Sunday — plan accordingly to avoid conflicts. Consider that employees spend 2.5 hours per day searching for information, per IDC, which means the operational and technology sessions are directly relevant to reducing that drag for your store teams. ## What Should Retail Leaders Do After NRF 2024? The sessions above surface recurring themes: frontline access, employee engagement surveys and feedback loops, AI-driven operations, and purpose-led culture. After the show, the practical next step is auditing how many disconnected tools your frontline teams currently navigate — research shows only 13% of employees use an intranet daily, and nearly a third never log in at all, per Social Edge Consulting. If your organization is among the 91% operating an intranet (Social Edge Consulting) but seeing low adoption, the insights from the AutoZone and PetSmart session will be directly applicable. For a deeper look at how retail and hospitality operators are solving these problems, [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) is a practical starting point. Teams evaluating employee engagement courses and structured development programs post-NRF may also find value in reviewing [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). --- # Why Giving Recognition in the Workplace Matters **Author:** Justina Kolb **Published:** 2023-12-04 **Category:** company-culture Let’s face it: the 9-to-5 grind has come a long way from what it used to be. Gone are the days when a decent paycheck and the promise of a corner office were enough to keep your workforce, well, working. Today’s employees crave more than just a pat on the back; they want recognition in […] Let’s face it: the 9-to-5 grind has come a long way from what it used to be. Gone are the days when a decent paycheck and the promise of a corner office were enough to keep your workforce, well, working. Today’s employees crave more than just a pat on the back; they want recognition in the workplace. To be celebrated and awarded for their efforts. It’s no longer just about attracting and keeping the rockstars; it’s about creating a culture of recognition that ensures the rockstars actually want to stay. Read on as we take a deep dive into the benefits of giving recognition in the workplace, and learn how it’s the key to keeping your crew happy, motivated, and ready to conquer the Monday blues. What is Recognition in the Workplace? Recognizing employees has always been a pillar of effective management. However, in today’s talent battleground, how organizations display appreciation for their crew has hit a whole new level of importance. It’s not just about the occasional shout-out; it’s about creating an atmosphere where every employee feels like an MVP, a major athlete on your company’s court. As the talent competition turns up the heat, passing some appreciation to your teammates has become the ultimate game-changer that keeps the dream team intact and thriving.  Beyond the occasional pat on the back, recognition in the workplace is a deliberate and systematic acknowledgment of employees’ efforts, contributions, and accomplishments. It’s about shining a light on the hard work that often happens behind the scenes, making each staff member feel seen, valued, and appreciated. From a simple “great job” to a formal award ceremony, recognition in the workplace fosters a culture where everyone is not just a cog in the machine but a vital and celebrated part of a thriving, dynamic team. Organizations can give recognition to their employees for a variety of reasons, but some of the most commonly seen are: Accomplishments such as promotions, project completions, and successfully taking on new responsibilities Demonstrating desired behaviors, like regularly meeting deadlines and adding to the company culture Going the extra mile, such as working overtime and lending a hand to other teams or departments  Celebrating milestones like hire-date anniversaries and attendance records Kansas City Chiefs + MangoApps Since their implementation of MangoApps, the Kansas City Chiefs…: Gained a 90% adoption rate Can reach 600 event staff members in an instant – never before possible. Inquired about adopting MangoApps for their operations teams as well. learn more Benefits of Giving Recognition in the Workplace Showing employees appreciation is crucial for fostering a positive and productive work environment. From reinforcing company values to improving customer satisfaction, creating a culture of recognition has a positive impact on your organization in many ways. Here are the ten most beneficial outcomes of recognition in the workplace: 1. Boosts Morale and Motivation Recognition serves as a powerful morale booster by acknowledging employees’ hard work and achievements. This acknowledgment doesn’t just stop at boosting morale; it has a ripple effect, increasing overall motivation within the team. When employees feel valued and appreciated, job satisfaction skyrockets, fostering a positive attitude that extends into their work. This positive attitude becomes a driving force, influencing the team’s collective motivation to tackle challenges and achieve even greater heights. 2. Enhances Employee Engagement Recognition isn’t just a feel-good moment; it’s a catalyst for enhanced employee engagement. Recognized employees are not merely clocking in and out, but are actively involved and committed to their work. This heightened engagement translates to increased levels of productivity, unwavering commitment to tasks, and a genuine willingness to go above and beyond what’s expected. It’s a win-win scenario where employees find joy and fulfillment in their roles, and the organization benefits from their amplified dedication. 3. Improves Retention Rates Retention becomes a natural byproduct of a workplace where employees feel consistently recognized and appreciated. When recognition is embedded in the company culture, employees are more likely to stay on board. The positive workplace culture that recognition cultivates reduces turnover rates, ultimately saving the company on recruitment costs. It’s not just about keeping talent; it’s about creating an environment that employees want to be a part of for the long haul. 4. Fosters a Positive Workplace Culture Recognition in the workplace is the secret sauce to creating a positive and inclusive culture. It goes beyond acknowledging individual achievements by fostering a culture of appreciation that permeates every aspect of the workplace. This culture encourages teamwork, collaboration, and a genuine sense of belonging. In a workplace where recognition is a cornerstone, every team member plays a crucial role in creating an atmosphere where everyone feels valued and celebrated. 5. Drives Performance and Productivity Recognized employees are not just content with maintaining their performance – they’re driven to continually improve. Regular acknowledgment becomes the fuel that propels a culture of excellence within the organization. This culture, in turn, becomes a driving force behind increased overall productivity. It’s a continuous loop of recognition inspiring higher performance, and higher performance, in turn, generating more opportunities for acknowledgment. 6. Encourages Peer-to-Peer Recognition Recognition in the workplace isn’t just confined to top-down gestures. Encouraging peer-to-peer acknowledgment creates a sense of camaraderie among colleagues, too. When team members acknowledge each other’s contributions, it strengthens the fabric of teamwork and collaboration. The workplace transforms into a supportive community where everyone actively recognizes and appreciates the unique skills and efforts of their peers. 7. Aligns with Company Values Recognition initiatives, when aligned with company values, serve as a powerful reinforcement of those values in everyday work. Beyond mere lip service, these programs demonstrate how the company’s core values translate into tangible actions. Employees gain a deeper understanding of how their individual contributions directly add to the overall success of the organization, creating a sense of purpose and connection to the company’s mission. 8. Boosts Creativity and Innovation Recognizing employees for their creativity and innovation becomes a catalyst for a culture of continuous improvement. In an environment where efforts are valued, employees feel empowered to share ideas and take calculated risks. This atmosphere not only boosts individual creativity but also fosters a collective innovative spirit within the team. It’s a recognition-fueled engine that propels the organization toward new horizons of creativity and innovation. 9. Strengthens Manager-Employee Relationships Regular recognition in the workplace is more than just an empty gesture; it’s a cornerstone for building strong manager-employee relationships. Acknowledgment becomes the bridge that builds trust between employees and their managers. This trust, in turn, creates open lines of communication. Feedback sessions transform into positive and constructive conversations, strengthening the overall relationship between employees and management. 10. Improves Customer Satisfaction Happy and engaged employees become the driving force behind excellent customer service. Recognition and appreciation directly impact the customer experience by creating a positive and motivated workforce. When employees feel valued, this positive energy naturally extends to customer interactions. The result is not just satisfied customers but delighted ones, as the positive atmosphere cultivated by recognition in the workplace becomes an integral part of the overall customer experience. Superdrug + MangoApps Learn how Superdrug uses MangoApps to: Foster an increased sense of an interconnected community Facilitate collaboration across different departments and international borders Create a centralized knowledge hub for on-the-go employees learn more How to Give Recognition in the Workplace Effectively When it comes to giving recognition in the workplace, there are various tools that will powerfully and effectively aid you in acknowledging and appreciating your team. Start with the basics—offer timely praise for a job well done, publicly recognize achievements in team meetings, and express gratitude through personalized messages. Consider implementing peer-to-peer recognition systems, fostering a culture where appreciation flows both horizontally and vertically.  Furthermore, one standout approach is the implementation of employee reward programs. These programs not only recognize outstanding contributions but also provide tangible incentives that motivate and inspire. From gift cards and experiences to professional development opportunities, employee reward programs offer a versatile and impactful way to show appreciation.  By incorporating a mix of these strategies into your recognition repertoire, you’ll create a dynamic culture where every team member feels valued, fostering an environment of sustained motivation and shared success. Ready to start giving recognition in the workplace? Book a demo with MangoApps! We’ll show you how our rewards and recognition software can cultivate a culture of appreciation throughout your company. book A demo! --- # How to Craft an Employee Recognition Budget **Author:** Justina Kolb **Published:** 2023-12-04 **Category:** company-culture Setting aside resources to celebrate and uplift your team is like adding confetti to your workplace culture. Planning your employee recognition budget should feel like preparing for the best party ever—joyful, exciting, and full of positive vibes. While every organization is generally met with a tight budget, it’s important to allocate funds for employee appreciation […] # How to Craft an Employee Recognition Budget Most recognition programs fail not because the intent is wrong, but because the budget isn't built to sustain them. A recognition program funded from discretionary spending — whatever remains at the end of a quarter — stalls the moment a tighter month arrives. One with a defined budget, allocated by line item, continues through the lean stretches and builds the consistency that actually changes employee behavior. The core answer: plan for 1–2% of total payroll, allocate $50–$200 per employee annually, and divide that budget across four categories — formal awards, informal celebrations, technology infrastructure, and frontline access. The rest of this guide explains the reasoning behind each allocation and how to measure whether the investment is working. ## Set a baseline: recognition budget as a percentage of payroll Industry benchmarks place the recognition budget at 1–2% of annual payroll. For a 200-person organization with average salaries around $60,000, that translates to roughly $120,000–$240,000 per year — or $600–$1,200 per employee. That range covers both formal award programs and the informal gestures that sustain recognition culture between major milestones. Three factors shift where you land within that range: **Competitive pressure.** Organizations in industries with high voluntary turnover — hospitality, healthcare, retail — tend to invest toward the higher end. When replacement costs run 50–200% of annual salary per departing employee, a larger recognition investment is defensible on retention savings alone. **Organizational growth stage.** Companies in rapid-growth phases often invest more heavily in recognition to stabilize culture during structural change. Organizations in steady-state operations can sustain similar outcomes at lower spend when programs are well-designed and consistently executed. **Program maturity.** A first-year recognition program spends disproportionately on technology setup and adoption campaigns. In year two and beyond, the same infrastructure generates more recognition activity per dollar as participation compounds. [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) identifies employee recognition as one of the strongest predictors of engagement — and one of the first budget lines cut during downturns, precisely when retention pressure is highest. Building the case for recognition as a retention investment rather than a culture expense is what keeps the budget intact when discretionary items face pressure. ## Break down the recognition budget by line item A recognition budget divided into four categories is easier to defend, easier to adjust, and easier to measure than a single discretionary pool. **Formal awards (25–35% of budget).** Formal awards cover structured, milestone-based recognition: years-of-service awards, performance bonuses, and goal-specific honors. These carry the most weight with employees who have context for what recognition means in the organization. The investment here should reflect the significance of the milestone — a five-year anniversary warrants something meaningfully different from a 90-day check-in. **Informal celebrations (15–25% of budget).** Informal recognition — team lunches, spot bonuses, handwritten notes, public acknowledgments in a company channel — creates frequency that formal programs cannot match. An employee who receives meaningful informal recognition every 30–60 days experiences the program differently than one who waits 12 months for a performance review. Allocating a defined portion of the budget for manager-led informal recognition gives front-line managers the tools to act without routing every gesture through an approval process. **Technology platform (25–35% of budget).** A [recognition platform](/key-features/rewards-and-recognition) does three things a manual process cannot: it makes peer-to-peer recognition as easy as posting a comment, it builds a searchable record that managers can reference during performance conversations, and it extends the program's reach to employees who aren't in the building. The friction of the submission process is the most common reason recognition programs plateau — when sending a recognition takes four steps, managers stop sending them. When it takes one, volume increases. **Frontline and deskless access (10–20% of budget).** According to Emergence Capital, 80% of the global workforce is deskless. If your recognition program assumes employees will access awards through a corporate laptop and a company email address, you've excluded the majority of most frontline organizations before the first recognition is sent. Budgeting for mobile-accessible recognition infrastructure — an app employees can access on personal devices, without VPN or corporate credentials — is not optional for industries where most employees work in the field, on a shift, or without assigned devices. ## Reach every worker, not just desk employees The structural gap in most recognition programs is that they were designed for the 20% of the workforce at a desk. Field service technicians, retail associates, warehouse staff, and healthcare aides receive either sporadic recognition or none at all — not because the program excludes them intentionally, but because the delivery channel doesn't reach them. Solving for frontline access requires more than a mobile-responsive design. Enrollment needs to work via QR code, SMS invitation, or personal email — not a corporate provisioning process that takes two weeks. Notifications need to reach employees during working hours, not during calendar events they're not attending. Peer-to-peer recognition needs to be visible to the team, so a shift worker can see what colleagues are being acknowledged for. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) documents how organizations that extended recognition infrastructure to frontline employees saw higher program adoption and lower voluntary turnover among shift-based roles compared to those maintaining desk-first programs. ## Integrate recognition with your HRIS and existing workflows A recognition budget that relies on HR staff to manually track anniversaries, promotions, and milestones spends a disproportionate share on process rather than people. HRIS-integrated recognition platforms automatically trigger awards when an employee hits a tenure milestone, completes a certification, or receives a promotion — eliminating the administrative overhead that causes recognition to arrive late, inconsistently, or not at all. This matters for budget efficiency as much as program quality. When recognition is automated for predictable events, HR attention can be redirected to high-judgment decisions — the situations where a personal, thoughtful gesture matters more than a system-generated notification. The [symplr case study](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program) shows how a large healthcare organization scaled recognition across a distributed clinical workforce by integrating their recognition platform with existing HR workflows — recognition volume increased significantly once the administrative friction was removed from the process. ## Measure ROI, not just participation rates Most recognition programs measure inputs — number of recognitions sent, percentage of employees who received at least one — rather than outcomes. Input metrics are useful for program health monitoring; they don't answer whether the budget is generating a return. The business case for recognition ROI follows a consistent pattern. If voluntary turnover costs the organization $15,000–$30,000 per departing employee in a mid-skill role, and a well-structured recognition program reduces voluntary turnover by 5–10%, the math is direct. A 200-person organization with 20% annual turnover replaces 40 employees per year. A 10% reduction saves four replacements annually — at $15,000 each, that's $60,000 in savings against a recognition budget that may be in a comparable range. This frame shifts recognition from a culture initiative to an operational cost management decision, which tends to be more durable when discretionary budgets face scrutiny. Additional ROI signals worth tracking alongside turnover data: - **Performance review quality.** Are recognition moments surfacing as documented evidence during review cycles, or are they invisible to the formal record? - **Onboarding speed.** Do employees who receive recognition in their first 30 days reach full productivity benchmarks faster than those who don't? - **Absenteeism patterns.** Teams with high recognition frequency typically show lower unplanned absence rates over a rolling 12-month window. ## Avoid the three most common recognition budget mistakes **Treating recognition as an event, not a cadence.** Annual recognition programs feel ceremonial rather than genuine. A quarterly cadence with a mix of formal and informal touchpoints builds the consistency that translates into engagement. The goal is for employees to experience recognition as a regular feature of work, not a once-a-year milestone. **Excluding peer-to-peer recognition from the budget.** Manager-to-employee recognition is valuable, but peer-to-peer recognition reaches a different part of the engagement equation — it signals that contribution is noticed by colleagues, not only evaluated by management. Budgeting for peer recognition primarily means investing in the platform, since the cost is operational rather than financial per recognition. **Allocating the same budget regardless of role or location.** Field service technicians, overnight warehouse staff, and remote contractors have fundamentally different access patterns than headquarters employees. A budget that ignores this difference will systematically under-recognize the workforce segments with the highest turnover risk — the employees who most need sustained engagement to stay. ## A budget structure that sustains A recognition budget structured around payroll percentage, divided into four line items, and integrated with HRIS data will outlast the leader who built it. It scales with headcount, survives leadership transitions, and creates a defensible business case in every budget cycle. Start at 1% of payroll for a first-year program. Build toward 2% as the program demonstrates retention ROI. Allocate a minimum of 15–20% of the budget toward frontline access infrastructure if any part of your workforce is deskless — not as an accommodation, but as the condition under which most of your recognition volume will actually reach the people it's intended for. Recognition that reaches every employee, runs on infrastructure that doesn't require manual intervention, and connects to retention metrics isn't a culture program. It's an operational investment with a measurable return — and a budget that reflects that distinction is one you'll be able to defend. --- # 24 Employee Appreciation Ideas to Boost Company Culture **Author:** Justina Kolb **Published:** 2023-12-04 **Category:** company-culture When it comes to creating a positive company culture, “appreciation” isn’t just a word but a strong force shaping your workplace. In this blog post, we explore an array of innovative and heartfelt employee appreciation ideas, each meticulously curated to breathe life into your company culture. From recognizing individual achievements to fostering team camaraderie, promoting […] When it comes to creating a positive company culture, “appreciation” isn’t just a word but a strong force shaping your workplace. In this blog post, we explore an array of innovative and heartfelt employee appreciation ideas, each meticulously curated to breathe life into your company culture. From recognizing individual achievements to fostering team camaraderie, promoting wellness, and nurturing professional growth, these ideas are the elements of a workplace where appreciation isn’t just an event—it’s a way of life. Employee Appreciation & Recognition Embarking on a journey of employee appreciation involves more than just acknowledging effort—it’s about creating a culture where recognition is a living, breathing entity. In this section, we’ll explore impactful strategies that are designed to weave a tapestry of appreciation, elevating individual achievements and fostering a workplace where every contribution is celebrated. 1. Higher Compensation Showing employee appreciation starts with paying more than just the bare minimum. Offering a wage that goes beyond the basics is the foremost strategy for attracting and keeping high-quality talent. Providing fair raises, especially for those whose compensation hasn’t kept pace with their experience and the cost of living, can significantly impact employee satisfaction and loyalty. 2. Extensive Benefits Compared to other high-income nations, the United States lacks universal healthcare – a disparity that makes accessing and affording healthcare services here challenging and, for many, seemingly unattainable. Providing employees with low- or no-cost plans that offer comprehensive coverage becomes a direct avenue to guaranteeing access to preventative care and essential treatments. In fostering healthier employees, you, in turn, cultivate a healthier workplace overall. 3. Recognize Achievements Not Related to Work Demonstrating genuine interest in your employees’ personal lives and accomplishments, provided it’s approached with sensitivity and consent, communicates that you value them as individuals, not just workers. Celebrating personal milestones, like purchasing a new home or getting engaged, can foster a stronger connection, but it’s crucial to gauge employee comfort before doing so. Respectful recognition of personal achievements contributes to building a positive relationship, but it’s equally important to avoid pushing employees to share their personal lives if they prefer not to, as this can have unintended consequences. 4. Personalized Thank You Notes Craft heartfelt, personalized notes expressing gratitude for individual contributions. While a quick “thank you” over your internal messenger is never frowned upon, taking time to handwrite a special note gives your sentiments a little extra meaning. A handwritten note is a great form of employee appreciation for when a member of your staff worked overtime or came in on the weekend to meet a specific deadline. 5. Employee of the Month Awards Recognize outstanding performance with a rotating “Employee of the Month” award. This is a great way to highlight each staff member’s unique contributions and skills. Not only is it a classic form of employee appreciation, but “Employee of the Month” awards also introduce team members to each other. This creates a tighter-knit community and a feeling of closeness among your team. 6. Spot Bonuses Surprise employees with spot bonuses for exceptional efforts or accomplishments. As mentioned above, nothing proves you appreciate your employees more than a better-than-good wage. Sporadically giving employees some extra cash now and then is a surefire way to ensure your staff feel loved. 7. Peer-to-Peer Recognition Encourage employees to recognize and appreciate their colleagues through a peer-to-peer recognition program. Implement rewards and recognition software to make showing employee appreciation effortless. From digital, company-branded awards to an online gift card catalog, peer-to-peer recognition has never been easier.  8. Milestone Celebrations Recognize work anniversaries and other milestones with celebrations and small tokens of appreciation. Milestones may include work anniversaries, promotions, project completions, sales, attendance records, and more. Be sure to stay on track of these dates and events; highlighting one person’s anniversary and not the other’s does not look good. Team Building and Engagement Fueling team spirit and engagement lies at the heart of effective employee appreciation. From virtual team-building activities that transcend digital screens to themed appreciation days that inject a dose of fun into the workweek, this section unveils creative ideas to strengthen bonds and promote a sense of camaraderie. 9. Virtual Team-Building Activities Organize engaging virtual team-building activities to foster a sense of camaraderie across your organization’s many locations. With remote work being the norm (and often preferred by staff), it’s important to ensure all your team members, despite their location, are being properly introduced and getting to know each other. This leaves remote employees feeling less alone and more comfortable asking questions and collaborating. Organize engaging virtual team-building activities to foster a sense of camaraderie across your organization’s many locations. With remote work being the norm (and often preferred by staff), it’s important to ensure all your team members, despite their location, are being properly introduced and getting to know each other. This leaves remote employees feeling less alone and more comfortable asking questions and collaborating.  10. Themed Appreciation Days Designate themed appreciation days, such as “Wellness Wednesday” or “Feel-Good Friday.” These types of themed days give employees a much-needed break in their routine. Show your team that you appreciate them by designating days meant for checking in on their mental and physical health. 11. Bring Your Pet to Work Day Organize a “Bring Your Pet to Work Day” to create a relaxed and enjoyable atmosphere. These days, pets are considered part of the family. They bring a sense of comfort to their owners while bringing a smile to the faces of everyone else they meet. As long as allergies or triggers don’t get in the way, a “Bring Your Pet to Work Day” shows employees you have their happiness and comfort on your mind. 12. Employee Art Showcase Host an employee art showcase, allowing team members to display their artistic talents. Those with artistic endeavors often find great joy in them. Give space for your team to showcase their personal creative sides. This form of employee appreciation shows that you don’t just see your staff as staff but as individuals with hobbies and interests outside of work. Kansas City Chiefs + MangoApps Since their implementation of MangoApps, the Kansas City Chiefs… Gained a 90% adoption rate Can reach 600 event staff members in an instant – never before possible. Inquired about adopting MangoApps for their operations teams as well. learn more Wellness and Work-Life Balance A holistic approach to employee appreciation encompasses staff’s well-being and work-life balance. Flexible work hours, wellness programs that prioritize health, and casual dress days contribute to an environment where employees feel supported in both their professional and personal lives. Dive into this section to explore ideas that promote employee wellness and cultivate a balanced, thriving workplace. 13. Flexible Work Hours Gone are the days of the traditional 9 to 5. Offer flexible work hours to accommodate personal needs and promote work-life balance. Life is already hard enough; giving your employees options that will make their personal lives easier shows that you can relate. Show employee appreciation by acknowledging that it doesn’t always matter when work gets done, as long as it’s getting done. This also builds trust between you and your staff, which results in decreased turnover and higher engagement. 14. Sufficient Staffing There’s nothing worse than being solely responsible for a job that takes multiple people. Employees are not inclined to be overworked just to save their company money. Having one employee handle the workload of two or three invariably leads to more mistakes, burnout among top performers, and diminished job satisfaction. Demonstrate concern for your employees’ well-being by ensuring adequate staffing for the job. 15. Paid Childcare & Family Leave Providing paid leave for mothers, fathers, and caregivers significantly impacts employees navigating the arrival of a new child or attending to the needs of an ailing loved one. The assurance that a company values their family commitments and recognizes their priority can serve as a powerful motivator, fostering loyalty and enhancing employees’ overall work experience. Employers can even offer childcare as a form of employee appreciation. The exorbitant costs and limited availability of quality child care can impose significant stress on your staff. The unpredictability of childcare arrangements may lead workers to unexpectedly miss work, and the financial strain could force them out of the workforce altogether. 16. Wellness Programs Implement wellness programs, such as yoga classes or wellness challenges, to prioritize health. Offering discounted gym memberships or subscriptions to meditation apps shows you have your employees’ well-being top of mind. This is a powerful form of employee appreciation. Making wellness programs more accessible to your staff makes it clear that you care. 17. Be Observant of Overwork Staying attuned to the atmosphere and overall well-being of your team holds significant value. Observing signs such as typically energetic employees appearing fatigued or a usually cheerful staff member on the brink of tears should prompt you to engage. Inquire about the best way to offer support; they might find relief in leaving early or simply having a conversation with you. While paying attention serves as the initial step, demonstrating genuine support through concrete actions reinforces the message that you view your employees as individuals, not just profit generators 18. Casual Dress Days Introduce casual dress days or themed dress-up days for a relaxed and fun atmosphere. This form of employee appreciation shows that you’re interested in the way your team expresses their individualism through style. Themed days give your staff a fun way to switch up their routine and interact with each other. Either route you take, casual dress days are a good way to express how much you appreciate your employee’s general professionalism throughout the year. 19. Remote Work Essentials Equip remote work essentials like ergonomic chairs, monitors, or stipends for a comfortable home office setup. If you want your employees to produce high-quality work, it’s critical to ensure they are physically comfortable. Show employee appreciation by providing their home offices with the tools and furnishings they need to be successful. 20. Customized Workspaces Allow employees to personalize their workspaces to create a more comfortable and inspiring environment. Giving employees a chance to express their personalities in their workspace is a good way to show that you value their individualism. Creating a space that encompasses your style and character makes the workday more enjoyable. Show employee appreciation by letting staff create a workspace that showcases their unique makeup. Professional Development and Learning Elevating employee appreciation to new heights involves investing in your team’s professional growth and continuous learning. Uncover strategies in this section that go beyond traditional recognition, such as leadership shadowing opportunities, book clubs, and personal development allowances. These initiatives are designed to create an atmosphere where employees feel valued not just for their current contributions, but for their potential to grow and thrive within the organization. 21. Professional Development Opportunities Invest in employees’ growth by providing access to workshops, courses, or conferences. Nothing says employee appreciation more than helping them achieve higher success within your company as it grows. Offer to pay for classes and resources that will not only aid in their role at your company but also elsewhere later in their careers. You can also give stipends staff can use toward courses, books, and activities that contribute to their personal and professional growth. This shows you care about them in more ways than just being your employee. 22. Leadership Shadowing Opportunities Offer opportunities for employees to shadow leaders within the organization for professional development. Giving staff an inside look at what goes on in a leadership position is employee appreciation in the form of transparency. This allows employees to gain valuable insights on the responsibilities that may be in their future if they so choose to work their way up in the company. Show your staff their retention is important to you and that you want to support them as much as you can within your organization (and elsewhere!). 23. Book Club or Learning Circles Establish book clubs or learning circles to promote continuous learning and discussion among employees. Not only does this form of employee appreciation show that you encourage collaboration and staff engagement, but that you also believe in your staff to move forward with their careers and learn new skills. Give your team a chance to engage with each other on new, exciting topics that are valuable to them. 24. Inspirational Speaker Session Arrange virtual or in-person sessions with inspirational speakers to motivate and engage employees. Giving staff a chance to hear thought-provoking stories from folks unrelated to your organization gives them the opportunity to learn from a diverse group of people. This shows that you appreciate your employees enough to ensure they hear varying perspectives to help shape their professional decisions. ProBiomed + MangoApps Learn how ProBiomed uses MangoApps to: Transform internal communications across distributed employees Consolidate their tech stack Improve company culture and employee engagement learn more The power of appreciation extends far beyond the workplace, influencing not only individual job satisfaction but the very essence of your company’s identity. Whether through personalized thank-you notes, virtual team-building activities, wellness programs, or avenues for continuous learning, each idea is a brushstroke contributing to a masterpiece—a workplace where appreciation, in all its forms, is woven into the very fabric of success. Implement, adapt, and watch as your company culture transforms into a thriving landscape where every employee feels seen, valued, and inspired to bring their best to the table. Let MangoApps guide you on your company’s employee appreciation journey – schedule a demo with us today!  book A demo! --- # Employee Gifting Best Practices **Author:** Justina Kolb **Published:** 2023-12-04 **Category:** best-practices Starting your company’s employee gifting journey opens a door to demonstrating appreciation for your workforce, signaling that you see, care, and highly value their contributions to the organization. Meaningful employee gifts not only boost motivation and productivity but also elevate workplace morale. This reinforces the timeless wisdom that investing in goodness yields positive returns. With […] # Employee Gifting Best Practices Employee gifting works best when it's specific, timely, and connected to a broader recognition system — not treated as an annual obligation or a generic gesture. The best practices are clear: personalize gifts to the individual, time them to meaningful moments, build a sustainable budget framework, and tie each gift explicitly to a performance milestone or behavioral signal. Organizations that execute these four pillars consistently see measurably stronger engagement and retention outcomes than those relying on ad-hoc gestures. But the "how" behind each pillar matters more than the pillar names. This guide covers what each best practice actually requires, the common mistakes that undermine gifting programs, how to extend gifting to frontline and deskless employees who don't have corporate email, and how to measure whether the investment is producing results. ## Personalization: what it means in practice The most frequently cited best practice in employee gifting — personalization — is also the most frequently misapplied. Personalization doesn't mean adding a name to a generic gift. It means selecting something that reflects actual knowledge of the recipient: their interests, their life stage, their communication preferences, or a specific contribution that the gift is meant to recognize. This requires information, which is why the most effective gifting programs are built on recognition data rather than a manager's memory. Employees who receive gifts tied to a specific achievement — a completed project, a peer nomination, a work anniversary — perceive the gesture as more meaningful than employees who receive the same item during a general company occasion. Personalization also breaks down at delivery. Per Emergence Capital research, 80% of the global workforce is deskless — working in warehouses, hospitals, retail floors, and field locations where a gift card emailed to a corporate inbox never arrives. Effective personalization accounts for how recognition is delivered, not just what is delivered. A program that reaches desk employees reliably but drops off at the frontline isn't personalized for the majority of the workforce. ## Timing: why the gap between achievement and recognition matters Timely gifting reinforces the connection between the gift and the behavior or milestone it's meant to celebrate. When the lag between an achievement and its recognition stretches into weeks, the psychological reinforcement that makes recognition meaningful is substantially reduced. Two timing categories matter most. Milestone-based gifts — work anniversaries, onboarding completions, project launches, promotion dates — are predictable and can be automated. Organizations that connect gifting to HRIS data can trigger recognition at the moment a milestone occurs rather than relying on a manager to remember. Spontaneous gifting, by contrast, depends on managers having the tools and prompts to recognize exceptional effort when they see it. The challenge with spontaneous recognition is manager bandwidth. Per IDC research, employees spend an average of 2.5 hours per day searching for information — managers face the same drain. Systems that surface recognition prompts (a peer submitted a positive nomination, an employee just hit a five-year tenure mark) remove the cognitive overhead of remembering to act. This is why platform-based recognition programs consistently outperform informal gifting practices on both frequency and timeliness — the system does the remembering so the manager can do the recognizing. ## Budget: building a sustainable framework Budget-friendly gifting doesn't mean low-quality gifting — it means budgeted gifting, which is a different thing. Ad-hoc programs where managers approve recognition spend informally tend toward inconsistency: some employees are recognized frequently, others rarely, creating perceived inequity that undermines the program's engagement value. A sustainable budget framework starts with a per-employee annual allocation — typically segmented by tenure and role — that managers draw from through a recognition platform. This makes the program predictable for finance and creates a visible history of recognition that managers can review to identify gaps before they compound. Creative, cost-effective options within a budget framework include experience-based recognition (a half-day off, access to a learning platform, lunch with a senior leader), personalized merchandise tied to the team's identity or the employee's specific interests, and public recognition paired with a modest physical or digital gift. The constraint isn't the budget itself — it's the intentionality behind the selection. Employees reliably distinguish between gifts that reflect thought and gifts that reflect a line item. ## Connecting gifting to a recognition system Gifting in isolation — without acknowledgment of what the gift is for — functions more as a perk than a recognition event. The most effective gifting programs are embedded within a structured [employee engagement](/solutions/employee-engagement) framework where every gift is paired with a narrative: what the employee did, why it mattered, and who is acknowledging it. That narrative is what transforms a gift into recognition. This connection to narrative is especially important for frontline employees, who are less likely to be recognized through traditional channels (performance reviews, email acknowledgments, all-hands calls) and more likely to receive recognition, if at all, through mobile-first tools. Organizations whose recognition platforms require corporate email or desktop access structurally exclude the majority of their employees from the program. The [symplr rewards and recognition case study](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program) illustrates what embedded recognition looks like in practice: peer nominations flowing through the same platform where employees do their daily work, with gifting integrated at the point of nomination rather than managed through a separate HR workflow. The result is a recognition moment that reaches employees in the flow of their workday rather than requiring them to visit a separate system. ## What gifts work best by role and context? The answer depends less on job category than on how an employee accesses work tools and what they actually value. Some general patterns hold across organizations. **Desk employees** respond well to experience-based recognition — additional PTO, learning stipends, team events — and digital gifts redeemable through a platform they already use. Physical gifts are effective when they reflect genuine personalization rather than a standard item pulled from a catalog. **Frontline and deskless employees** are underserved by most standard gifting programs because the delivery mechanism (corporate email, desktop portal) doesn't reach them. Effective gifting here requires mobile-accessible redemption: gift cards claimable through a phone, public recognition in a mobile app, or physical gifts delivered to the work location rather than to a home address. **Distributed and remote employees** benefit most from gifting that closes the distance gap — home office upgrades, meal delivery credits, or team-visible recognition that surfaces across time zones. The goal is ensuring the recognition moment is shared, not siloed. **New hires** respond disproportionately to gifting during the onboarding window, when their sense of belonging is most uncertain. An onboarding gift tied to a specific milestone (first week complete, first client interaction, first project delivered) signals investment before the employee has proven themselves — which has an outsized effect on early engagement and meaningfully reduces early attrition. ## Measuring whether gifting is working Recognition programs are among the most intuitively justified HR investments and among the least consistently measured. The metrics that matter: **Engagement scores by cohort.** Do employees in departments with active recognition programs score higher on engagement surveys than those in departments where recognition frequency is low? A clear gap is evidence the program is producing outcomes. The absence of a gap usually points to inconsistency in delivery or personalization quality. **Retention by tenure segment.** Gifting has its highest ROI in the 90-day to 12-month window, when flight risk is highest and employees are still forming their commitment to the organization. Cohort-level retention analysis at those milestones can isolate whether recognition at those points is reducing early attrition. **Redemption and participation rates.** In platform-based programs, whether employees actually redeem recognition — and how quickly — directly signals whether the gifting mechanism is accessible and motivating. Low redemption rates in frontline populations almost always trace to a delivery problem, not a culture problem. **Manager activity gaps.** Systems that track recognition frequency by manager surface structural gaps that informal programs hide. Per [Gallup's 2026 State of the Global Workplace research](/articles/gallup-2026-state-of-the-global-workplace), employee engagement and manager behavior are tightly correlated. Recognition frequency is one of the most actionable proxies for whether a manager is creating the conditions for employee performance — and the gaps are invisible without data. ## Common mistakes that undermine gifting programs **Gifting at holidays only.** Holiday gifts are the most common gifting moment and the least differentiated. When every employee receives the same item at the same time, the signal isn't "we see you individually" — it's "this is what we do in December." Milestone and achievement-based gifting signals individual recognition in a way that seasonal gifting structurally cannot. **Ignoring tax implications.** Cash-equivalent gifts above the IRS de minimis threshold are treated as taxable compensation. Programs that don't account for this create unexpected tax events for employees at recognition moments — which transforms a positive experience into an administrative frustration and undermines the intent of the gesture. **Managing gifting outside the recognition system.** When gifting is handled through manager discretion rather than a platform, recognition history isn't captured, gaps aren't visible, and the program can't be improved over time. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) documents how HR leaders are systematizing recognition as infrastructure rather than a culture initiative — the operational model matters as much as the intent behind it. **Excluding deskless populations by design.** A gifting program that requires employees to log into a desktop portal or check a corporate email to claim recognition isn't a program for the frontline. With 80% of the global workforce deskless (per Emergence Capital), this exclusion affects the majority of employees at many organizations — not an edge case. ## Building a gifting program that compounds over time Organizations that see sustained engagement outcomes from employee gifting share one characteristic: they treat gifting as a system, not an event. The system includes a recognition platform where gifting moments are logged, a budget framework that's predictable for both HR and finance, a delivery mechanism that reaches every employee regardless of location or device, and reporting that surfaces where the program is working and where it's stagnating. A useful starting point is an honest audit of who is being recognized and who isn't. Per [Gallup's 2026 State of the Global Workplace research](/articles/gallup-2026-state-of-the-global-workplace), persistent employee disengagement often traces back to feeling unseen — and the absence of recognition in certain departments or tenure cohorts is rarely intentional. It's usually structural: the tools don't reach the people, the budget isn't allocated, or the program was designed for desk employees and never extended to the frontline. Closing those gaps — delivery, budget, consistency, measurement — is what separates gifting that produces lasting engagement outcomes from gifting that feels meaningful in the moment and disappears in the next survey cycle. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines how recognition-as-infrastructure is emerging as the dominant model among HR leaders who have moved past the seasonal gifting calendar toward programs that run year-round, reach every employee, and produce results that finance can verify. --- # A Guide to Employee Reward Programs **Author:** Justina Kolb **Published:** 2023-12-04 **Category:** company-culture Employee reward programs have become integral to fostering a positive work environment and promoting employee engagement. In this comprehensive guide, we’ll delve into the intricacies of these programs, exploring what they entail, and the reasons behind their implementation. Plus, discover the difference between rewards and recognition, uncover the myriad of benefits they cultivate, and understand […] Employee reward programs are structured initiatives that acknowledge and appreciate employee efforts through a combination of social recognition and redeemable rewards. This guide explains what these programs are, why organizations implement them, how rewards differ from recognition, and what measurable benefits they deliver — including financial outcomes that go beyond morale. ## What Are Employee Reward Programs Employee reward programs are structured initiatives, often supported by an [employee engagement software](/solutions/employee-engagement) platform, that aim to acknowledge and appreciate the efforts and achievements of employees within an organization. Recognition, frequently shared internally, is coupled with redeemable points for rewards, creating a dynamic system that not only boosts morale but also improves performance and contributes to talent retention. In the realm of employee recognition, the impact extends beyond simple acknowledgment. Key business metrics such as engagement, productivity, and retention are significantly influenced by the implementation of effective recognition programs. While the potential benefits are substantial, the key to creating a meaningful employee recognition and reward program lies in acquiring the right knowledge, meticulous planning, and allocation of resources. This guide will navigate through these essential elements, providing insights into crafting impactful programs for organizations of all sizes. **Kansas City Chiefs + MangoApps** Since their implementation of MangoApps, the Kansas City Chiefs…: - Gained a 90% adoption rate - Can reach 600 event staff members in an instant — never before possible. - Inquired about adopting MangoApps for their operations teams as well. ## Why Implement Employee Reward Programs Implementing employee reward programs goes beyond mere tradition; it's a strategic move that can significantly enhance employee morale and overall organizational success. By recognizing and appreciating the hard work of employees, organizations create a positive work culture, boost productivity, and foster a sense of loyalty among their workforce. These programs not only acknowledge individual accomplishments but also contribute to a collaborative and supportive work environment. The aim of implementing an employee rewards and recognition program is to not only acknowledge and celebrate employee achievements but also to amplify these successes among colleagues and peers. Recognition can take various forms, including social acknowledgments or the awarding of points tied to favored behaviors. These points, in turn, empower employees to redeem rewards such as gift cards, merchandise, or unique experiences. This creates a system that not only motivates but also enriches the overall employee experience. The business case for these programs is increasingly quantifiable. OU Health achieved 87% workforce engagement within months of launching a branded employee app with integrated recognition. British Airways recorded a 30-point engagement score increase attributed to a unified employee experience platform. Wipro captured $20M in cost avoidance after deploying an integrated employee experience and recognition platform. These outcomes reflect a broader shift: organizations are treating recognition not as a culture perk but as a measurable driver of retention and productivity. ### Recognition Examples: - Employee of the month awards - Milestone celebrations - Themed appreciation days - Project completion shoutouts - Attendance streaks ## The Difference Between Rewards and Recognition While the terms "rewards" and "recognition" are often used interchangeably, it's crucial to understand the nuanced differences between them. Rewards typically involve tangible incentives such as bonuses, gifts, or extra time off. On the other hand, recognition is about acknowledging an employee's efforts and achievements through praise, awards, or public acknowledgment. Both are essential components of comprehensive employee reward programs, each playing a distinct role in motivating and appreciating employees. To easily differentiate between the two, you can think of recognition as being social and rewards as being monetary. ### Social Recognition When it comes to social recognition, acknowledgment can take various forms. Think spontaneous shout-outs during a company meeting, thoughtful thank-you messages from a manager, or even digital badges highlighting specific qualities or actions. This mode of recognition serves as a powerful tool for validating and encouraging behaviors aligned with the company culture. When social recognition becomes a regular practice, team members experience heightened pride, a greater sense of involvement, and increased enthusiasm for reciprocating recognition among their colleagues. When crafting a social recognition plan, it is crucial to incorporate opportunities for peer-to-peer acknowledgment. The impact of recognition is most profound when it emanates from both peers and leaders. Ensuring that your [rewards and recognition platform](/key-features/rewards-and-recognition) facilitates peer-to-peer recognition empowers every team member to champion recognition, fostering a culture of inclusivity and appreciation. For a detailed look at how one organization built this from the ground up, see [From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program). ### Monetary Recognition Monetary recognition encompasses tangible rewards such as salary increases, bonuses, travel opportunities, and gift cards. These rewards serve to convey appreciation for the daily efforts of employees. While personalizing these rewards enhances their impact, the quest for the perfect gift on every occasion, for every employee, can be impractical. Plus, this technique does not involve active participation of all team members. To address this challenge, adopting an employee recognition solution supporting a points-based system is the most effective way to go. Employers allocate a specific number of points to each employee on a monthly or quarterly basis. These points, coupled with social recognition, can then be exchanged among colleagues, allowing team members to redeem them for rewards, charitable donations, or gift cards from a catalog. A points-based reward system not only accommodates individual preferences but also enables your entire staff to actively engage in the experience, making it a practical and inclusive choice. When reward programs are integrated with HRIS, they can automatically sync employee roles and milestones, enabling timely, data-driven recognition without manual administration. **Great Harvest Bread Co. + MangoApps** Learn how Great Harvest uses MangoApps to…: - Allow store members to share knowledge, ideas, and information - Centralize resources and information in an easily searchable hub - Build a strong employee recognition program by offering incentives and kudos ## Benefits of Employee Reward Programs The advantages of employee reward programs extend far beyond a momentary morale boost. These programs contribute to increased employee engagement, improved job satisfaction, enhanced productivity, and a positive organizational culture. Additionally, they serve as powerful tools for talent retention, attracting top performers and encouraging continuous excellence. By investing in employee well-being, organizations create a cycle of motivation and achievement that propels overall success. Here are the top 5 benefits of employee reward programs: 1. **Higher Employee Engagement:** Utilizing a points-based rewards system tying recognition to desired behaviors increases engagement and serves as a top driver for heightened enthusiasm throughout your company. For organizations looking to deepen this connection, embedding [employee engagement training](/solutions/employee-engagement) into the same platform that delivers recognition removes friction and reinforces learning alongside appreciation. 2. **Boosts in Employee Retention:** Elevated employee engagement directly correlates with higher job satisfaction, resulting in reduced turnover rates for employers. This translates into significant time and cost savings as content and engaged employees are more likely to stay with the organization. 3. **Defines Corporate Culture:** The adage "what gets recognized gets repeated" holds true, emphasizing that fostering a culture of recognition perpetuates a positive cycle of employee engagement and reinforces the values integral to the organization. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) explores how leading organizations are embedding recognition into their broader culture strategies. 4. **Creates a Sense of Belonging:** The intangible but invaluable feeling of belonging in the workplace is nurtured through rewarding and recognizing employees. This practice demonstrates that individuals are integral to the organization's culture, fostering a sense of value and support among your team. 5. **Enhanced Connection Among Team Members:** Encouraging team members to express genuine appreciation for one another through points-based rewards and recognition programs fosters stronger connections. These programs provide a streamlined platform for managers and employees to effortlessly send and share recognitions, contributing to a cohesive and supportive team dynamic. ## Reaching Frontline and Deskless Workers Most guides to employee reward programs assume a desk-based workforce — but per Emergence Capital, 80% of the global workforce is deskless. Frontline employees in industries such as [hospitality](/industries/hospitality), healthcare, and logistics are often excluded from recognition programs simply because they lack a company email address, a desktop workstation, or VPN access. An employee experience platform that delivers recognition to frontline workers on personal mobile devices — without requiring email or VPN — removes this access barrier entirely. Onboarding speed can improve by 50% when recognition and training workflows are digitized and made mobile-accessible for frontline teams. For organizations managing distributed or shift-based workforces, this inclusivity is not a feature enhancement; it is a prerequisite for any recognition program to function equitably. ## Conclusion Employee reward programs are a proven lever for engagement, retention, and measurable business performance. The evidence is concrete: organizations that deploy integrated recognition platforms have documented outcomes ranging from 30-point engagement score increases to tens of millions of dollars in cost avoidance. The programs that deliver the strongest results share three characteristics — they combine social and monetary recognition, they reach every employee regardless of role or device, and they tie recognition to behaviors that reinforce organizational values. For organizations evaluating where to start, the practical path is to select an employee experience platform that embeds rewards alongside the tools employees already use for scheduling, HR self-service, and communications. This reduces tool fatigue, increases adoption, and ensures recognition is part of daily work rather than a separate system employees must remember to visit. To understand how leading organizations are approaching this in 2026, the [MangoApps Wins Gold in Reworked's 2026 IMPACT Awards for Excellence in Recognition](/articles/mangoapps-gold-reworked-2026-impact-awards) provides useful context on what best-practice programs look like today. Ready to implement an employee rewards program at your workplace? Schedule a demo with MangoApps below! **Book a Demo** ## How Do Reward Programs Connect to Employee Engagement Strategy? Recognition programs are most effective when they are embedded within a broader employee engagement strategy rather than operated as a standalone initiative. Engagement encompasses communication, learning, performance feedback, and belonging — and recognition touches all of these dimensions. Organizations that treat reward programs as one component of a unified employee experience platform consistently outperform those that deploy point-in-time recognition tools in isolation. For a deeper look at how engagement strategy connects to daily workflows, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ## What Should I Look for in Employee Engagement Software? When evaluating employee engagement software to support a reward program, prioritize platforms that offer: peer-to-peer and manager-to-employee recognition in a single feed, points-based redemption with a configurable catalog, HRIS integration for automated milestone recognition, and mobile accessibility for frontline workers without email or VPN requirements. Independent analyst coverage can help narrow the field — [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) offers one reference point for how platforms are assessed on these criteria. ## How Do I Measure the ROI of an Employee Reward Program? Measuring return on investment from a reward program requires tracking both leading indicators (recognition frequency, participation rates, employee engagement survey scores, and employee engagement questionnaire completion) and lagging indicators (voluntary turnover rate, absenteeism, and productivity metrics). Establish a baseline before launch, set a measurement cadence of 90 days and 12 months post-launch, and segment results by department and workforce type to identify where recognition is driving the most impact. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) includes benchmarks that can help contextualize your program's performance against industry norms. --- # How to Motivate Retail Employees: The Complete Guide **Author:** Christos Schrader **Published:** 2023-11-17 **Category:** retail In the dynamic world of retail, employee motivation is the fuel that drives performance, customer satisfaction, and overall business success. Your retail employees are the frontline warriors, the face of your brand, and the ones who make the difference between a one-time shopper and a loyal, repeat customer. But how do you keep your retail […] # How to Motivate Retail Employees: The Complete Guide Marisol has spent seven years managing a 12-store district for a regional grocery chain. She's run recognition programs, built incentive structures, and attended every corporate culture initiative her company has offered. The results follow the same pattern every time: strong adoption among salaried store managers, quiet non-participation from the associates on the floor. Last spring, she traced the gap to something simple. The recognition app required a company email. The training system lived behind a VPN. The task updates came through a Slack channel most part-time staff had never set up. The tools built to motivate her workforce were structurally accessible to less than half of it. Marisol's observation is more common than most motivation guides acknowledge. The question worth asking isn't *what* programs drive retail employee motivation — it's *who can access them*. According to IDC research, employees spend an average of 2.5 hours per day searching for information. For deskless retail workers — associates who don't sit at a computer, who juggle customer interactions and stock room tasks and shift coverage questions — that number is a rough proxy for how much of their day is spent navigating friction instead of doing meaningful work. According to Emergence Capital, 80% of the global workforce is deskless. Retail represents a large share of that number. The systems built to support them often weren't designed with them in mind. This guide starts where most motivation guides don't: the access gap. Then it covers the levers that actually move the needle — recognition that reaches the floor, learning embedded in the workflow, communication workers will open, and the mobile-first access model that makes all of it possible. ## Why retail motivation strategies fail before they start Most retail motivation programs are built on the assumption that the workforce can receive them. That assumption is frequently wrong. Consider intranets, the traditional backbone of internal communications and often the delivery vehicle for recognition programs, policy updates, and training. According to Social Edge Consulting, only 13% of employees use their company intranet daily, and nearly a third never log in at all. According to SWOOP Analytics, the average daily time employees spend in intranet tools is six minutes. These aren't disengaged employees choosing to opt out. They're workers who couldn't log in on their phones without a corporate credential they were never issued, or who opened the platform once and found nothing relevant to their store or their shift. Hourly associates, seasonal hires, and part-time staff — who represent the majority of headcount at most retail chains during peak periods — often lack company email addresses entirely. If your motivation infrastructure requires one, it isn't reaching the people who need it most. This is the root problem Marisol kept circling: the issue wasn't the quality of the recognition program. It was that the program lived inside a system her floor associates couldn't open. Solving for retail employee motivation means solving for access first. Every strategy that follows depends on it. ## Recognition that reaches the floor, not just the management layer Retail employees consistently rank being seen and valued among their top drivers of job satisfaction. The gap isn't intent — most retail chains have some form of recognition infrastructure. The gap is reach. Traditional recognition structures centralize acknowledgment in monthly cycles and deliver it through managers who may not have witnessed the individual contribution they're celebrating. By the time recognition lands, the behavior it's acknowledging is six weeks old and the employee has moved on — likely to a moment where they felt invisible. The recognition model that actually moves retail employees differs in two ways. First, it operates at the moment of impact rather than the end of a review period — a peer or manager flags a contribution when it happens, not when the cycle rolls around. Second, it's visible to the team, not just the individual. Public acknowledgment in a shared channel — in a team feed, in a push notification the associate's whole shift can see — amplifies the signal far beyond what a private manager note can achieve. Symplr built this model using MangoApps and documented the shift in both recognition participation and engagement outcomes. For retail operations leaders evaluating what an effective program looks like in practice: [how symplr built its rewards and recognition program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program). The principle translates directly to retail: when recognition is fast, public, and accessible from the phone in an associate's pocket — without requiring a corporate login — it becomes a regular feature of the work experience rather than an occasional event. ## Learning pathways as a motivation lever, not an HR checkbox Nine of the most prominent competitors in the frontline employee engagement space have built their positioning around workforce learning as a motivation driver. Most retail operations still treat training as a compliance activity: something associates complete during onboarding and revisit only when a new policy requires an acknowledgment. That gap is a significant missed leverage point. Research cited by Beekeeper indicates that mobile-accessible onboarding and training can reduce new-hire ramp time by 50% for frontline teams. That figure captures something more important than speed: it captures the experience of competence. Workers who understand the system they operate in, who know what's expected, and who can see a clear path to take on more responsibility have concrete reasons to stay engaged. Vague promises of advancement don't drive motivation. Accessible pathways do. The version of learning that motivates retail employees isn't a separate destination — it's embedded in the work itself. An associate assigned a new display task can access the relevant SOP in the same interface. A new hire's first-week orientation lives in the same app used to check the shift schedule. A store manager on a promotion path can access leadership development content without leaving the daily workflow. This is a different architecture than deploying an LMS and hoping employees navigate to it. The [case for embedding learning directly into daily workflows](/articles/learning-and-development-strategy-embedded-in-daily-work) — rather than maintaining a separate training system no one opens — is the same case Marisol was making unconsciously when she traced her recognition problem back to the access layer. ## The communication layer retail employees actually open Retail associates don't check email between customer interactions. They check their phones. Any communication strategy routed through email or corporate portals is selecting, by design, for the fraction of the workforce with permanent access to those systems. The communication that retail employees open is push-based, mobile-first, and directly tied to their immediate context — a shift change notification, a task assignment with a clear deadline, a team update relevant to the specific store they're working in today. Broad company announcements and monthly newsletters don't function as motivation tools for associates who open them two weeks late, on a device they share with three family members, through an email account they forget the password to. The motivating function of communication isn't information delivery — it's connection to purpose. When an associate can see that the display they set up yesterday contributed to a promotional outcome, or that the customer complaint they escalated was resolved, they can connect their individual action to a result. That connection is one of the strongest intrinsic motivation signals available to retail managers, and it's nearly impossible to deliver through a weekly digest. For operations leaders working through how scheduling, task assignments, and team communication intersect — and how coordination failures disguise themselves as motivation failures — [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) addresses the operational layer that underlies many of what managers experience as engagement problems. ## Mobile-first access isn't a feature — it's the prerequisite The three levers above — recognition, learning, communication — share a single delivery requirement: they have to work from a phone, without a company email address, in a location that may have intermittent connectivity. According to Emergence Capital, 80% of the global workforce is deskless. In retail, that number approaches 100% for hourly associates and part-time staff. A motivation infrastructure designed for desktop workers with corporate logins isn't a retail motivation strategy — it's a manager engagement program with a broader brand. The operational case for mobile-first access is concrete. OU Health documented 87% workforce engagement within the first months of launching a branded frontline app — a rate roughly four times the industry standard for intranet adoption. The driver wasn't a new incentive program. It was removing the login barrier. Workers opened the app because it worked on their phones, required no corporate credential, and surfaced information specific to their role and location. There's also a subtler factor at play. A generic enterprise platform extended to mobile reads as a corporate instrument deployed grudgingly to the frontline. A branded experience signals belonging. For retail employees who often feel like the last link in an information chain that runs from corporate to regional to district to store — and then stops — a platform that opens to their name, their store, their shift is a qualitatively different signal. Four leading competitors in this space explicitly position branded employee apps as cultural belonging drivers for frontline staff. That positioning resonates because the experience it describes is real. ## Three diagnostics before the next motivation initiative Motivation programs fail in predictable ways. Before committing resources to the next recognition campaign or engagement survey, three diagnostic questions can identify where the actual gap is. **Who can access the system you're deploying?** Before launching any new tool or program, map the credential gap. Which locations have the highest share of hourly and seasonal staff without company email addresses? Those locations will underperform on any email-dependent program — and they're typically the highest-traffic, highest-turnover stores in the chain. **Does recognition reach workers in the moment, or only in the review cycle?** If the only path to recognition runs through a manager who reviews monthly metrics, the loop is too slow to change behavior. Test whether peer-to-peer, real-time acknowledgment is structurally possible in your current infrastructure before building another top-down awards program. **Is learning embedded in the workflow, or a separate destination?** If associates access training through a different system than the one they use to check their schedule and receive task assignments, the training is competing for attention rather than riding an existing habit. Consolidating those surfaces is usually the higher-leverage move — and the one that makes growth opportunities feel real rather than aspirational. ## What Marisol changed Marisol didn't redesign her recognition program. She changed where it lived. The program moved from a portal requiring a corporate login to a mobile app her associates opened every morning to check their schedule. Recognition became visible in the same feed where task assignments and shift updates appeared. Learning content moved from the LMS nobody accessed to modules embedded in the daily task workflow. Engagement in her district improved. Turnover at her lowest-performing stores dropped. The content of the programs didn't change. The access did. That is the design principle behind retail motivation that holds under operational pressure: the platform your associates use every day to check their schedule should be the platform everything else runs through. Recognition, learning, communication, compliance acknowledgments — all of it, accessible from a shift worker's phone, without a corporate email, in a stockroom with intermittent signal. Design for that associate and the rest of the workforce is covered by default. For organizations evaluating how to close the access and engagement gap across multi-location retail operations, the [MangoApps employee engagement solution](/solutions/employee-engagement) covers how this infrastructure model works in practice. --- # Combating Retail Turnover: Strategies for Keeping Your Team Happy and Productive **Author:** Christos Schrader **Published:** 2023-11-17 **Category:** retail Navigating the complex world of retail turnover can appear as a daunting task. With so many variables at play, it can be difficult to discern where the real issues lie. However, understanding the intricacies of retail turnover and how to effectively address them is integral to ensuring the smooth functioning and ultimate success of your […] # Combating Retail Turnover: Strategies for Keeping Your Team Happy and Productive Retail turnover is one of the most direct threats to a store's profitability. Replacing a single frontline retail employee costs between $4,400 and $15,000 in recruiting, onboarding, and lost productivity—making retention a P&L issue, not just an HR metric. The strategies that actually move the needle fall into four categories: investing in employee development, improving work conditions, offering competitive compensation, and giving frontline workers the communication and learning tools they need to feel connected and competent from day one. This guide covers each category with specific, actionable steps. If you manage a retail team and want to reduce churn, you will find a concrete answer to every major question below. --- ## Why Retail Turnover Is So Expensive Turnover in retail happens faster than in most industries because of lower wages, irregular scheduling, physically demanding conditions, and limited visibility into career paths. The financial damage compounds quickly. Replacing a single frontline employee costs between $4,400 and $15,000 when you account for job postings, manager time spent interviewing, onboarding hours, and the productivity gap while the new hire ramps up. Multiply that by dozens of departures per year across multiple locations and the number becomes a material line item. Beyond direct replacement costs, high turnover creates a ripple effect: - **Remaining staff absorb extra workload**, which accelerates their own burnout and departure. - **Customer service quality drops** when inexperienced associates handle transactions that experienced staff would handle confidently. - **Employer brand erodes** on job boards, making it harder to attract candidates who have options. - **Institutional knowledge walks out the door**, forcing managers to re-train the same skills repeatedly. Understanding these costs in concrete terms is the first step toward building a business case for the investments described below. --- ## The Four Core Strategies for Reducing Retail Turnover ### 1. Invest in Employee Development—Especially On-the-Floor Learning Employees who see a path forward stay longer. Employees who feel underprepared leave faster. Both dynamics are addressable through structured development programs. **Onboarding and structured training programs** give new hires the product knowledge, safety procedures, and customer service skills they need to feel competent quickly. Confidence in the role is a direct predictor of early-tenure retention. **Mentoring programs** pair newer associates with experienced staff. The relationship reduces the isolation that many frontline workers feel, particularly in large stores or multi-location chains. **Career advancement pathways** matter more than most retail operators acknowledge. Employees who can see a clear route from associate to shift lead to assistant manager are more likely to treat the job as a career rather than a stopgap. **Embedded microlearning** is the piece most retail training programs miss. Abstract training programs scheduled in a back office are easy to skip and hard to retain. On-the-floor microlearning—short modules accessible from a mobile device, without a corporate email address or a desktop login—meets associates where they actually work. According to Emergence Capital, 80% of the global workforce is deskless, meaning the majority of retail employees will never sit at a computer to complete a training module. Learning tools that require a desk are, by design, tools that most retail workers will not use. For a broader look at why training programs fail when they are disconnected from daily workflows, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ### 2. Improve Work Conditions Physical and scheduling conditions have an outsized effect on frontline satisfaction because associates experience them every single shift. **Physical environment**: Lighting, temperature, noise levels, and the quality of break rooms all affect daily comfort. These are not perks—they are baseline signals about whether the company respects the people doing the work. **Scheduling fairness**: Irregular and last-minute schedule changes are among the most frequently cited reasons retail workers leave. Scheduling software that accounts for employee availability preferences, rotates less desirable shifts equitably, and provides advance notice reduces the resentment that builds from feeling like a variable cost rather than a team member. For practical guidance on this, [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) covers the operational details. **Safety**: Retail businesses should maintain current safety training, run regular drills, and ensure associates know how to handle emergency situations. A safe environment is a legal baseline, but communicating that safety is a priority—and following through—also functions as a retention signal. ### 3. Offer Competitive Compensation and Benefits Compensation is rarely the only reason employees leave, but it is frequently the reason they start looking. Retail businesses operating on thin margins still need to benchmark wages against local competitors and adjust regularly for inflation and cost of living. Beyond base pay: - **Health insurance and paid time off**, even partial coverage for part-time staff, meaningfully differentiate employers in a competitive hiring market. - **Employee discounts** are low-cost to offer and consistently valued by retail associates. - **Performance bonuses and sales commissions** create a direct link between effort and reward, which improves both motivation and retention among high performers. Frontline workers evaluate total compensation, not just hourly rate. Employers who communicate the full value of their benefits package—clearly and regularly—retain more staff than those who let that information sit in an onboarding packet that no one re-reads. ### 4. Cultivate a Positive Work Culture Culture is the accumulation of daily interactions, not a values statement on a wall. The specific practices that move the needle in retail include: **Participative leadership**: Managers who solicit input from associates before making decisions that affect them—scheduling changes, floor layout, new procedures—generate a sense of ownership that reduces disengagement. **Open communication channels**: Regular check-ins, structured feedback sessions, and accessible management create an environment where concerns surface before they become resignations. Recognition—verbal or formal—should be consistent and specific, not reserved for annual reviews. **Team cohesion**: Team-based activities, whether structured training sessions or informal outings, build the interpersonal relationships that make a job feel like more than a transaction. **Work-life balance**: Flexible scheduling, advance notice of shifts, and generous leave policies signal that the company treats associates as whole people. In retail, where weekend and holiday work is unavoidable, the *way* those demands are managed matters as much as the demands themselves. --- ## How Technology Reduces Retail Turnover ### The Problem with Traditional Intranets in Retail Many retail organizations have invested in intranet platforms to centralize communications and training. The adoption data suggests these investments frequently fail to reach the frontline. According to Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use one daily. SWOOP Analytics found that the average employee spends just six minutes per day using intranet tools. For a desk-based knowledge worker, six minutes of intranet use per day is low but not catastrophic—they have other channels. For a retail associate who has no corporate email, no desktop, and no reason to open a browser during a shift, six minutes is effectively zero. Traditional intranets are not built for the frontline. ### Mobile-First Employee Apps Built for Frontline Workers A mobile employee app that requires no corporate email and works on a personal device changes the access equation entirely. Retail and frontline teams that adopt a branded mobile employee app achieve 90%+ adoption rates, compared to the 13% daily usage typical of traditional intranets (per Social Edge Consulting). CVS achieved 90% frontline adoption within the first six months of launching a mobile-first employee experience platform. OU Health reached 87% workforce engagement within a few months of launching a branded employee app. What drives those adoption numbers is not the technology itself—it is what the app consolidates. When shift schedules, training modules, HR self-service, company news, and peer recognition all live in one place, associates have a reason to open it every day. Consolidating these functions into one mobile app also reduces the tool-switching burden that costs employees over four hours per week in lost productivity (per MangoApps unified platform data). For retail operators evaluating platforms, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the operational benchmarks in detail. ### Employee Engagement Surveys and Feedback Loops Employee engagement surveys and employee engagement questionnaires embedded in a mobile app give managers real-time signal on team sentiment—before disengagement becomes a departure. Pulse surveys, anonymous feedback options, and structured check-in tools surface the specific issues driving dissatisfaction at a location level, which is where retail turnover is actually won or lost. IDC research found that employees spend an average of 2.5 hours per day searching for information. When associates cannot find the answer to a basic question—where is the return policy, when is my next shift, how do I request time off—they either interrupt a manager or give up. Both outcomes erode satisfaction. A well-structured mobile app with a searchable knowledge base eliminates most of that friction. ### Automation and Process Efficiency Automating repetitive administrative tasks—scheduling, timesheet submission, onboarding paperwork, offboarding checklists—reduces the burden on both managers and associates. In a high-turnover environment like retail, onboarding and offboarding automation is particularly valuable because those processes run constantly. Streamlining them reduces cost per hire and ensures new associates reach productivity faster. --- ## What Does a Branded Employee App Actually Do for Retention? This is a question retail operators frequently ask after seeing adoption statistics. The mechanism is straightforward: a white-labeled, role-personalized app—one that shows a seasonal associate only the content relevant to their store and role—signals that the company built something *for them*, not for corporate. That signal matters more than it might seem. Generic HR portals communicate, implicitly, that frontline workers are an afterthought in the company's technology investment. A branded app with the company's name, the store's specific communications, and a recognition feed where managers can call out good work communicates the opposite. That cultural signal is what converts a disengaged seasonal hire into a retained team member who applies for the shift lead role six months later. For context on how [employee engagement](/solutions/employee-engagement) technology fits into a broader retention strategy, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the current landscape of tools and their measured impact on frontline retention. --- ## Building Operational Resilience Alongside Retention Retention strategies work best when the operation itself is stable. Resilience—the ability to absorb disruptions without cascading into turnover—requires attention to three areas: **Workforce resilience**: Continual training, a growth mindset culture, and wellness resources equip associates to handle the stress spikes that retail environments generate regularly (holiday seasons, inventory events, understaffing). **Operational resilience**: Documented procedures, contingency plans for critical functions, and automated backups for scheduling and inventory reduce the chaos that burns out managers and associates alike. **Technology resilience**: Cloud-based systems, regular data backups, and clear contingency plans for technology failures ensure that a platform outage does not cascade into a communication breakdown on the floor. --- ## Concrete Next Steps for Retail Operators If you are managing a retail team and want to reduce turnover in the next 90 days, here is where to start: 1. **Calculate your actual replacement cost.** Use the $4,400–$15,000 range as a baseline and multiply by your annual departure count. This number is your business case for every investment below. 2. **Audit your current communication and training tools.** If your frontline workers need a corporate email or a desktop to access training or schedules, your adoption rate is almost certainly below 20%. 3. **Implement a mobile-first communication channel** that works on personal devices with no email required. Measure adoption at 30, 60, and 90 days. 4. **Launch a pulse survey** within the first 30 days to establish a baseline on engagement and identify the specific issues driving dissatisfaction at each location. 5. **Embed microlearning into daily workflows.** Replace scheduled back-office training sessions with short mobile modules that associates can complete between tasks. 6. **Review compensation and scheduling practices** against local market benchmarks. Wage adjustments and scheduling fairness improvements have the fastest impact on near-term retention. 7. **Build a recognition cadence.** Manager-initiated recognition, visible to the team, is one of the highest-ROI retention tools available—and it costs nothing beyond consistency. Retail turnover is not an inevitable cost of doing business. It is a measurable problem with measurable solutions. The organizations that treat it as a P&L issue—and invest accordingly in the tools, training, and culture that keep frontline workers engaged—consistently outperform those that treat it as background noise. For a deeper look at how [retail industry](/industries/retail) operators are approaching this challenge, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the communication and engagement patterns that distinguish high-retention retailers from the rest. --- # Mastering Retail Execution: Enhancing Efficiency with Monitoring & Improved Task Management **Author:** Christos Schrader **Published:** 2023-11-17 **Category:** retail Retail execution is the critical linchpin connecting your strategy to customer satisfaction. An efficient, well-monitored retail execution system ensures that your products are available and attractively displayed. It also makes sure promotions are effectively executed and store personnel are well-trained and proactive. In today’s hyper-competitive retail environment, a meticulous approach to retail execution monitoring and […] # Retail Execution: Task Management & Monitoring That Actually Works Sofia manages 35 grocery stores across two regions. On a Tuesday in early March, she learned that a promotional display — a six-foot tower of seasonal snacks, already featured in the weekend circular — had been sitting in the stockroom at four locations since Friday. The display was built and waiting. The task had been assigned. The message had been sent. Nobody had flagged a problem because the tool they used to send the message had no feedback loop. The circular ran. The stockroom floor stayed full. That gap — between assignment and verified completion, between communication and confirmation — is where retail execution breaks down. Not in strategy, not in intent, but in the operational plumbing that turns a regional manager's expectations into a specific action at store level on a specific shift. This guide covers the infrastructure decisions that close that gap: removing the access barrier that excludes most frontline workers from the operational loop, building task management with a real feedback mechanism, embedding monitoring into the work itself rather than layering it on top, and measuring outcomes instead of activities. ## The access barrier that retail execution tools consistently ignore Before addressing task management design or monitoring systems, there is a prior problem most retail execution strategies skip: a large portion of the workforce can't access the system at all. Hourly associates, seasonal staff, and part-time workers — who often represent the majority of headcount during peak periods — typically don't have corporate email addresses. If the platform that carries task assignments, SOP updates, compliance acknowledgments, and training materials requires a company email to log in, those workers are structurally excluded from the operational system. The information exists. It just doesn't reach the people doing the work. The practical access requirements aren't complicated: authentication via phone number or employee ID, content that loads under low-bandwidth conditions, and the ability to receive push notifications for time-sensitive task assignments without a corporate credential or VPN. A retail stockroom or distribution center may have intermittent connectivity — a system that requires a live connection for every interaction fails exactly where it's needed most. This isn't a convenience issue. It's a compliance and execution gap. Required training completions, safety acknowledgments, and promotional compliance confirmations cannot be collected from workers who can't reach the platform. When a display task is sent to "all store associates" and 60% of those associates lack login credentials, the task isn't truly assigned to all store associates — it's assigned to the subset that corporate IT has already reached. The stores with the highest turnover are the ones most likely to have the largest credential gaps, which means the locations that need the most operational support are the ones least connected to the system designed to provide it. According to McKinsey research, 89% of frontline workers say they would stay with their employer if leaders genuinely listened to their feedback. The feedback loop that makes monitoring and task management work requires that workers have access to the system that carries that feedback in the first place. ## Task management versus task notification: a structural difference Most tools described as "task management" in retail operations are actually task notification systems. A message is sent. A task is logged as "sent." Whether the task was received, read, understood, and completed is either tracked informally or not tracked at all. Effective task management at scale requires three structural properties that notification systems don't provide. **Named ownership.** A task assigned to a team, a shift, or a location is effectively assigned to no one. When the display doesn't get set up, the answer to "who was responsible?" is a shrug. Naming a specific individual — not a generic role — who receives the assignment and whose completion or non-completion is visible changes the accountability structure without requiring additional management overhead. **Verifiable completion, not just acknowledgment.** A worker confirming they've read a task and a worker confirming they've completed it are different signals. The first is an acknowledgment. The second is a completion record. For compliance-sensitive tasks — a price change, a product recall notice, a safety checklist — the difference matters in audits and in operational decision-making. **Automatic escalation for overdue items.** A regional manager overseeing 40 stores cannot manually monitor task status across every location. A system that surfaces overdue items automatically and routes the escalation to the right person at the right level makes scale tractable. Without this, the manager becomes the escalation system — which means the ones that get caught are the ones the manager happened to check. [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) documents how the coordination failures that affect scheduling and task workflows share the same root structure: when the tool for communicating about work is separate from the tool for tracking it, the gap between assignment and completion widens predictably — at exactly the moments when operational pressure is highest. ## Building monitoring into the work, not on top of it The instinct when physical presence can't keep pace with scale is to add reporting layers. Store managers fill out forms. District leaders collate responses. Operations teams assemble the data. By the time anyone can act on it, the promotion has been running incorrectly for four days. Monitoring systems that function at retail scale don't require a separate reporting layer. The data they generate is a byproduct of work being done, not an additional burden layered on top of it. When a store associate completes a task, that completion is recorded. When a training module is finished, the timestamp is captured. When an issue is flagged, it enters a visible queue. The reporting is a consequence of the operational workflow, not an extra step in it. This structural feature — monitoring as a byproduct of work rather than a report filed afterward — is what makes scale manageable. A regional leader who can see, in a single view, which locations have completed their morning compliance checklist and which have open flags has operationally useful information at the moment they can act on it. That same information assembled through manual reporting arrives days later, filtered through several layers of intermediary and too stale to drive real-time decisions. According to McKinsey research, 81% of leading companies effectively use data and analytics tools. In retail operations, "effective use" rarely means the most sophisticated analytics platform — it means the right people have the right information at the moment they can act on it. A dashboard of historical trends accessible only to the VP of operations is not operationally useful for a store manager running a Tuesday morning shift. Real-time task completion visibility is. SOPs belong in this same infrastructure. When documented procedures live in a shared drive or a printed binder that associates saw once during onboarding, they function as compliance formalities rather than operational tools. Embedding the relevant SOP in the same system used for daily task assignments — so an associate encounters the procedure when they're assigned the task that requires it — is what makes standard operating procedures standard in practice rather than in name. ## What "measuring execution" actually means at store level The most consistent gap in retail execution programs is measuring at the activity level — tasks sent, messages delivered, training completions logged — rather than at the outcome level. Activity metrics confirm the system ran. They don't confirm it improved anything. The outcome metrics that matter are downstream: are stores running promotions correctly on launch day? Has the rate of compliance failures in audits decreased? Are locations with higher task-completion rates showing different results in shrink, audit scores, or customer satisfaction? Answering those questions requires connecting operational data from task and communication systems to the results data that measures business outcomes. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents how leading retailers are rebuilding this measurement architecture — not by adding more tools, but by ensuring that the platforms already used for daily operations generate the signals that connect to outcome reporting. The [Raley's Companies case study](/resources/raleys-case-study) illustrates what this looks like at scale. Connecting 20,000 employees across a distributed grocery operation required not just better communication infrastructure, but a measurement model capable of distinguishing between "the message was sent" and "the stores that received and acted on it show different operational outcomes than the ones that didn't." That distinction is the difference between activity tracking and execution measurement. For individual stores, the practical measurement question is simpler: did the morning briefing actually reach the staff who needed it, and can you confirm the display was set correctly before the store opened? Specific, timely verification tied to an operational outcome — that is where execution monitoring delivers real value. ## Three questions to ask before the next execution rollout Retail execution failures — missed promotions, compliance gaps, training that doesn't stick — almost always trace to one of three root problems. Identifying which one you're solving changes what the solution looks like. **Who actually has access?** Before deploying any new task or monitoring system, map the credential gap. Which locations have the highest share of hourly and seasonal staff without corporate email addresses? Those are the locations where any email-dependent system will underperform — and they're often the highest-traffic, highest-turnover locations in the chain. **Where does the task loop break?** Trace a single task from assignment through completion in your current system. Is there a named individual responsible for completion? A verifiable completion state? Automatic escalation when the task goes overdue? If any of those three elements is missing, what looks like task management is task notification without a feedback loop. **What outcome are you measuring?** If the only metric available after a promotional rollout is "number of messages sent," the measurement architecture is tracking activity, not execution. Define the outcome — display compliance rate, audit pass rate, time-to-completion — before configuring the tools that are supposed to drive it. For organizations evaluating how to close these gaps across multi-location retail operations, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading operators are rebuilding their execution infrastructure simultaneously on all three dimensions. ## The design principle behind execution that holds under pressure Back to Sofia. The four stores with displays still in the stockroom weren't a management failure. They were the predictable output of a system designed to send information, not confirm it had been received and acted on by people who had access to receive it. The retailers where execution holds up under operational pressure share one structural characteristic: the platform associates open every day to check their schedule is the same platform that delivers task assignments, SOP documentation, training, and compliance confirmations. Execution isn't a separate behavior requiring separate motivation — it's a byproduct of the daily workflow already in place. The baseline scenario your infrastructure needs to serve reliably: a seasonal associate working a peak-period schedule, without a corporate email address, in a store with intermittent connectivity, who needs to complete a compliance acknowledgment before the shift starts and confirm a display task before the morning rush. Design for that associate and the rest of the workforce is covered by default. Build for anything less, and what looks like a retail execution system is actually execution infrastructure for the fraction of your workforce that already has the most access — leaving the people closest to the customer outside the operational loop. --- # Fostering Well-Being In Retail: Addressing The Industry’s Unique Challenges **Author:** Christos Schrader **Published:** 2023-11-17 **Category:** retail In the bustling world of retail, the well-being of employees often takes a backseat. The pressures of consumer demand and sales targets can lead to stress, fatigue, and decreased job satisfaction. But it doesn’t have to be this way. It’s crucial to acknowledge that frontline employees are not just cogs in the machine, but the […] # Fostering Well-Being in Retail: Addressing the Industry's Unique Challenges The conventional response to retail employee burnout is a wellness program: mental health apps, manager empathy training, ergonomic assessments. None of these are bad ideas. But they're downstream interventions for a problem that originates upstream — in the operational infrastructure that retail frontline workers navigate every day. Per IDC, employees spend 2.5 hours per day searching for information. In retail, that friction looks specific: a store associate who can't find the current return policy, a shift worker who discovers their schedule changed after they've already arrived, a new hire who got three conflicting answers about a procedure because there's no single source of truth. These aren't culture failures. They're information architecture failures. And they generate the stress, disengagement, and burnout that wellness programs are then deployed to address — after the damage is done. Eighty percent of the global workforce is deskless, per Emergence Capital — and retail is the sector that number describes most exactly. The people most responsible for a retailer's customer experience are also the people most systematically excluded from the communication infrastructure that desk workers take for granted: no company email address, no reliable mobile access, no direct channel to leadership. The well-being gap in retail doesn't start with difficult customers or unpredictable schedules. It starts with an infrastructure that treats frontline workers as peripheral. ## Why most well-being strategies misdiagnose the problem Retail leaders generally have an accurate list of frontline stressors: high-pressure sales targets, unpredictable scheduling, difficult customer interactions, physical demands, and now the added cognitive load of omnichannel responsibilities. Store associates who once managed inventory and floor coverage now handle online order fulfillment and real-time service recovery — often with no additional training and no updated tools. The diagnosis is correct. The causal model is usually wrong. Most well-being strategies treat these stressors as psychological problems that management can solve with the right tone, the right recognition programs, and the right work-life balance messaging. The research doesn't support this framing. Per Social Edge Consulting, nearly a third of employees never log in to their intranet — and only 13% do so daily. SWOOP Analytics found the average daily time employees spend using intranet tools is six minutes. If a retailer's primary communication channel is an intranet that 87% of the workforce effectively ignores, no amount of leadership warmth transmitted through that channel reaches the people it's meant to support. The stressors are real. But they're amplified — often doubled — by information deprivation. A schedule change communicated through a system an associate doesn't regularly access isn't a scheduling problem. It's a communication infrastructure problem wearing a scheduling disguise. ## What the infrastructure gap costs, in operational terms Consider the concrete sequence: an associate arrives to find their shift extended. They have no work communication tool with which to notify family. A question about a new return policy comes up; the updated version isn't mobile-accessible without a VPN. They escalate to a manager who is occupied elsewhere. The associate improvises, the customer interaction goes poorly, and the associate absorbs that outcome. This isn't a story about a difficult customer or an inattentive manager. It's a story about missing infrastructure generating compounding friction across a single shift. Multiply that pattern across a frontline workforce — where 80% of global workers are deskless, per Emergence Capital — and the aggregate burnout becomes structurally predictable. Mobile-first access to schedules, PTO requests, and task assignments through a single app without requiring a company email or VPN removes a category of friction that wellness programs cannot touch. Automated no-code workflows that handle shift swapping, routine approvals, and onboarding steps reduce the administrative burden on store managers and improve schedule predictability for associates. Mobile-accessible onboarding and training programs can reduce new hire ramp time by up to 50%, lowering early-tenure stress in high-turnover retail environments where the first 90 days determine whether a new associate stays or becomes another attrition statistic. ## Three infrastructure changes that move the well-being needle Retail organizations that have made measurable progress on frontline well-being haven't done it exclusively through wellness programs. They've addressed three infrastructure gaps that amplify every other stressor. **Mobile-first, no-email access.** When frontline workers can access schedules, policies, and peer communication through a single mobile touchpoint — without a company email address or VPN — the information deprivation that compounds every other workplace stressor is removed. Schedule stability improves, policy ambiguity decreases, and the cognitive overhead of navigating fragmented systems disappears. This is the operational fix for the information-access problems that generate most retail burnout — and it requires platform infrastructure, not a wellness program. **Personalized, role-targeted communications.** Per the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook), employees identify irrelevant communications as a significant source of cognitive overload — corporate messaging designed for a different role, location, or tenure creates noise that obscures the signals frontline workers actually need. A communication platform that delivers role-specific and location-specific information reduces this overload structurally. The right information reaching the right person at the right time isn't a feature preference; in a high-volume retail environment, it's what separates an informed associate from a guessing one. **Closing the feedback loop visibly.** One of the most consistent predictors of disengagement in retail is the experience of submitting feedback into a void. Survey responses that generate no visible follow-up teach associates that their input doesn't matter — and they stop giving it. The structural fix isn't more surveys. It's feedback mechanisms that close the loop explicitly: showing employees what changed, why, and which frontline input influenced the decision. This is distinct from recognition, though recognition matters too. It's giving frontline workers evidence that the organization is actually listening. ## Scheduling is a well-being issue, not only an operations issue The [Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) covers the operational mechanics of schedule optimization in detail. The well-being dimension is worth stating separately: unpredictable scheduling is one of the highest-impact stress drivers for retail frontline workers, and it's the one most amenable to structural intervention. Two factors matter most. First, advance notice: associates who know their schedule weeks ahead can plan personal commitments, childcare, and commutes. The cognitive burden of scheduling uncertainty is a documented health stressor, not a preference. Second, shift agency: associates who can flag availability constraints, request swaps, and see open shifts through a mobile app report measurably higher satisfaction than those who negotiate these through a manager intermediary or a paper request form. Both are operational decisions with direct well-being consequences. And both are achievable through existing scheduling and communication technology — they don't require new wellness programs, additional headcount, or culture change initiatives before they can start working. ## What a shared data layer makes visible that programs miss The alternative to a unified employee experience platform is a stack: a separate scheduling tool, a separate LMS for training, a separate recognition system, and possibly a separate wellness app. Each solves one problem. None shares data. A manager who wants to understand whether a struggling associate's performance is connected to schedule instability, incomplete onboarding, or absence of recognition has to cross-reference three systems — if all three have been consistently updated. The well-being case for a unified platform isn't primarily about feature parity with specialized tools. It's about the data layer. When schedule history, training completion, recognition activity, and communication patterns all live in the same system, the early warning signals for burnout — declining engagement with communications, incomplete training, erratic shift pickups — become visible before they become resignations. Per the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook), the organizations showing the strongest retention outcomes in frontline-heavy workforces are not necessarily those with the most wellness programs. They're the ones whose managers have a coherent picture of each employee's experience. That picture requires a shared data layer, which siloed tool stacks don't produce. ## What a well-being strategy actually requires Retail organizations that have made durable progress on frontline well-being share a few structural commitments. They've invested in communication infrastructure before wellness programs. The sequence matters: no wellness initiative reaches associates who aren't reliably on the communication platform. Inline translation across communications in 200-plus languages supports multilingual retail workforces by ensuring no associate is excluded from critical updates — a well-being issue and, in many markets, a compliance one. They measure leading indicators, not only lagging ones. Turnover rates and satisfaction scores are outcomes. Communication tool adoption, training completion rates, and shift-swap resolution time are leading indicators of whether the infrastructure is working. Organizations that track both have more actionable data earlier — before a struggling associate becomes a departure. They've made infrastructure mobile-first by design, not as an afterthought. Frontline workers access their work information from personal devices, outside of store hours, without a VPN. A platform that assumes a desktop session or a corporate device has already excluded the majority of its most engaged users. For retail leaders evaluating where to start: infrastructure first, programs second. Address the information gap that amplifies every other stressor. Build the data layer that makes employee experience visible to the people responsible for it. Then layer recognition, wellness, and engagement programs on a foundation that actually reaches the frontline — through a [retail employee experience platform](/industries/retail) built for deskless, mobile-first access. The goal isn't a workforce that tolerates retail's structural pressures more gracefully. It's a workforce operating with less of the systemic friction that makes those pressures feel unsurvivable. --- # Enhancing Retail Staff Training with Technology **Author:** Christos Schrader **Published:** 2023-11-17 **Category:** retail In today’s retail landscape, staff training is paramount to success. With the right training processes in place, employees can deliver excellent customer service, enhance the shopping experience, and significantly boost sales figures. But how can businesses ensure they provide top-notch training? The answer lies in leveraging smart solutions, such as an employee app for retail. […] # Enhancing Retail Staff Training with Technology Elena manages twelve stores across three states. Every Monday, her district's weekly training assignments go live in the learning management system. By Thursday, she has completion data from four of them. She knows which eight stores haven't opened the modules — she just doesn't know why, and the fix requires a separate conversation with each store manager, who offers a different explanation every time. Elena's problem is not a curriculum problem. The training content is solid. Her problem is a delivery problem: the system her company chose to deliver training is not where associates actually spend their time. This pattern sits behind most retail training failures. Organizations invest in content and get abandoned platforms in return — not because employees are unwilling to learn, but because the learning system was built for desk workers in a workforce where, per Emergence Capital, 80% of employees never sit at one. A platform that requires a separate login, a corporate email address, or a shared breakroom terminal is structurally incompatible with shift-based retail before a single module is assigned. The shift that changes this is not upgrading the LMS. It is reframing training as a function of workplace learning — a capability built into the same employee app associates already use for schedule checks, team communications, and task updates, rather than a standalone tool they're expected to remember to visit. ## Why retail training falls apart before anyone opens a module The fragmentation that kills training adoption is visible before you look at completion rates. Per IDC, employees spend 2.5 hours per day searching for information across disconnected systems. In retail, that fragmentation typically means associates navigate 6–8 separate tools daily — one for schedules, another for communications, a third for training, a fourth for task management — none of which shares data with the others. The consequence is access failure, not motivation failure. Associates who want to complete training cannot find it. Associates who can find it cannot open it on their phones. Associates who can open it on their phones receive modules designed for a store they have never worked in. Per Social Edge Consulting, 91% of organizations operate an intranet — but only 13% of employees use one daily, and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends six minutes per day on intranet tools. These numbers do not describe a learning problem. They describe a delivery architecture designed for desk workers and never rebuilt for workers on their feet. ## The distinction between a training tool and a workplace learning platform A standalone LMS stores content and tracks completion. Associates log in when a manager tells them to, find the assigned module, and log out. The system is passive — it waits for the employee to come to it. A [learning management](/solutions/learning-management) platform built into an employee app works differently. Rather than requiring associates to seek out training, it surfaces relevant content based on role, store location, and what the business needs this week. A new product line launching next week automatically queues a micro-learning module for associates in the affected departments. A compliance deadline triggers a notification in the same stream as schedule updates — not in a separate system no one checks. An associate promoted to department lead finds their training queue has already updated without a manager submitting a separate request. This is what workplace learning means in practice: training is a native function of the daily workflow, not a system associates have to find their way to. When learning lives in the same platform associates open to check their shift, it gets used as part of the daily routine. When it requires a separate login, it gets used when someone remembers to ask. Nine competitors now explicitly market AI-curated learning paths for frontline teams. That shift represents what retail training buyers now expect — and what organizations without it are conceding in adoption. AI-native platforms surface role-relevant training content automatically rather than requiring managers to manually assign every module. True personalization runs at the employee level, continuously, based on role, completion history, and current business priorities. ## What retail training technology must deliver for distributed, shift-based teams For a workforce like Elena's — spread across twelve stores, variable shifts, no desk, no corporate device — several capabilities determine whether a training platform gets used or ignored. **Mobile access on day one without IT involvement.** Retail associates frequently start before IT provisioning is complete. Any platform that requires a corporate email, a VPN, or a shared terminal cannot support onboarding at scale. The enrollment flow should support QR code or SMS-based provisioning so a new associate can access their first module on a personal phone within minutes of hire. Mobile-first onboarding can reduce new hire ramp time by 50% when training reaches associates on the devices they already carry. **Role and location-based content targeting.** A training module for an urban flagship store is not appropriate for a rural franchise location. A safety procedure for a fresh-food department should not appear in an apparel associate's queue. Persona-based content targeting by role, region, and language ensures associates see training relevant to their situation — not everything the company has ever published. Irrelevant content noise is one of the primary reasons associates stop engaging with training platforms. **HRIS integration that eliminates manual admin overhead.** When the training platform connects directly to the HR system, employee roles, store assignments, and completion records sync automatically. A promotion updates the training queue in real time. A departure removes access without a separate request. The manual overhead of maintaining audience lists across distributed locations is precisely what the HRIS connection is supposed to eliminate. **Completion data in the same interface managers use for scheduling.** Per the [Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling), the operational data layer is where most retail platforms fall short. A district manager overseeing twelve stores should not need to open a separate reporting dashboard to know that eight of them have not completed a compliance module. That information belongs in the same interface she uses for daily operations — surfaced proactively, not waiting to be pulled. **Video micro-learning accessible during shift breaks.** Scheduling constraints make extended training sessions impractical in most retail environments. Two- to five-minute video modules consumable on a personal phone between tasks — accessible offline, resumable midway — fit the actual time windows retail associates have available. This format also outperforms text for product demonstrations, safety procedures, and customer service training where modeling the behavior matters. ## How to evaluate retail training platforms for real-world deployment The evaluation work is identifying which platforms hold up when a district manager 200 miles from IT support needs to onboard twenty seasonal associates in a single weekend. These criteria answer that question. **Does it work on a personal phone without a corporate email?** If the answer is no, the onboarding use case fails at the highest-volume training moment in retail before the platform is ever tested in production. **Does it surface training in the same flow as scheduling and communications?** Platforms with the highest sustained adoption are the ones that do not require a separate app or login. Training that lives alongside shift schedules gets encountered as part of the normal daily workflow rather than as a task that requires deliberate navigation. **Can a district manager see store-by-store completion in real time?** Ask for a demo of the manager view before the associate view. The associate experience is straightforward to present; the operational data layer is where most platforms fall short. **Does it connect to your HRIS?** Require a live integration demo, not a roadmap promise. The manual overhead of maintaining audience lists and role assignments is where training technology most consistently fails organizations that skipped integration at procurement. **Does it support multilingual content for a diverse workforce?** Retail organizations in urban and suburban markets frequently employ associates who speak different primary languages. A platform that cannot surface content in a learner's preferred language creates a compliance gap that is invisible in aggregate completion metrics. ## What a successful deployment looks like at Elena's scale Six months after deploying a workplace learning platform, Elena's situation looks different in one specific way: she stopped chasing completion data because it arrives before she asks for it. New associates in all twelve stores access their first training module the day they are hired — no shared terminal, no IT ticket, no day-two reminder from the store manager. Module assignments update automatically when roles change. Compliance deadlines arrive in the same notification channel as shift updates, not in a system no one monitors between assignments. Frontline retail training platforms built on unified employee apps achieve roughly 90% adoption within the first six months when they replace fragmented tools. That figure reflects what happens when training is no longer a separate system associates have to find: it is present in the platform they are already opening at the start of every shift. The [Santee Cooper case study](/resources/santee-cooper-case-study) documents how a distributed workforce built this kind of consistent access across locations where associates had no desk, no shared terminal, and no prior expectation that a digital platform would matter to their daily work. ## Closing the delivery gap Retail organizations that invest in training content and see low completion rates are almost always failing at delivery, not curriculum. The content exists. The access is broken. The technology that fixes this is not a more polished LMS. It is a workplace learning platform — one where training is native to the employee app associates are already using, not a separate system they are expected to remember to visit. That architectural difference is what separates high-adoption retail training deployments from platforms that show up in the completion dashboard as four out of twelve. For organizations ready to close that gap, the [Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026](/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) covers the evaluation criteria, integration requirements, and access architecture decisions that determine whether a workplace learning deployment actually reaches every associate — or just the ones near a breakroom terminal. --- # Improving Employee Experience With an Intranet Search Feature **Author:** Justina Kolb **Published:** 2023-11-13 **Category:** employee-experience In today’s dynamic work environment, where information is a cornerstone of productivity, the role of an efficient intranet search feature is pivotal in improving employee experience within your organization. Whether you’re part of a bustling tech startup or a well-established corporate entity, the ability to swiftly access relevant information positively impacts job satisfaction and productivity. […] # Improving Employee Experience With an Intranet Search Feature Employees spend an average of **2.5 hours per day** searching for information they need to do their jobs (per IDC). Multiply that across a team of 100 people and you are losing the equivalent of more than 30 full-time working days every single week — not to complex problems, but to friction in finding answers. A well-designed intranet search feature directly attacks that waste. This article explains what makes intranet search effective, why most deployments fall short, and what organizations can do to close the gap. ## What Is an Intranet — and Why Does Search Define Its Value? An intranet is a private, internal network that gives employees access to company information, tools, documents, and each other. The definition of intranets has expanded significantly: modern platforms are no longer static web portals but dynamic, role-aware environments that connect people, content, and workflows in one place. Despite widespread adoption — 91% of organizations operate an intranet according to Social Edge Consulting — the reality of daily use is sobering. Nearly a third of employees never log in to the intranet (Social Edge Consulting), and only 13% use one daily (Social Edge Consulting). The average employee spends just six minutes per day using intranet tools (per SWOOP Analytics), compared to the 2.5 hours they spend hunting for information across disconnected systems (per IDC). The gap between those two numbers is the employee experience problem. When search fails, employees stop trying. When they stop trying, the intranet becomes shelfware — and the organization loses the collaboration, knowledge-sharing, and productivity gains it was built to deliver. ## The Real Cost of Poor Intranet Search Framing intranet search as a UX issue understates the business risk. Consider the compounding costs: - **Productivity loss:** Employees lose over 4 hours per week switching between disconnected systems, according to internal benchmarks from enterprise deployments. When search does not span all connected tools, that switching cost compounds. - **Retention risk:** Replacing a single frontline employee costs between $4,400 and $15,000 (per industry reports cited on MangoApps' mobile employee app product page). Disengagement driven by poor tooling is a measurable contributor to turnover. - **Adoption collapse:** When employees cannot find what they need quickly, they abandon the intranet entirely — which means the organization's investment in content, governance, and licensing delivers no return. The tools of knowledge management only work when employees can actually reach the knowledge. Search is the access layer that makes everything else matter. ## Why Traditional Intranets Fail at Search Traditional intranets take months to deploy, strain IT teams, and deliver static, ungoverned content that becomes stale quickly. Search on these platforms is typically scoped to a single repository — which means an employee looking for a policy document stored in SharePoint, a project file in Google Drive, and a conversation thread in the intranet itself must run three separate searches. Modern knowledge management tools solve this with **universal search**: a single query that spans connected third-party storage platforms — SharePoint, Google Drive, Box, Dropbox — alongside internal intranet content. The employee types one thing and gets one ranked result set, regardless of where the information lives. Modern platforms can also go live in minutes with AI-curated, role-specific content rather than requiring months of IT configuration. That speed-to-value difference matters when organizations are trying to improve employee experience now, not after a multi-quarter deployment. ## AI-Powered Search: From Keyword Matching to Intent Understanding Generic intranet search returns documents that contain a keyword. AI-powered search understands what the employee is trying to accomplish and surfaces the most relevant result — even if the exact keyword does not appear in the document. MangoApps' AI search capabilities connect to OpenAI, Gemini, and Azure engines to deliver results that account for context, role, and recency. Instead of returning a list of files, the search function can surface a direct answer, flag the most recently updated version of a document, or recommend a subject-matter expert from the [employee directory](/key-features/employee-directory) when no document exists. This shift from keyword matching to intent-aware retrieval is what separates a tool for knowledge management that employees actually use from one they abandon after the first frustrating search. ## Frontline and Deskless Workers: The Search Problem Nobody Talks About 80% of the global workforce is deskless (per Emergence Capital). These are the employees — in manufacturing, retail, healthcare, field services — who are least likely to have a corporate laptop, a company email address, or reliable access to a VPN. They are also the employees most likely to be excluded from traditional intranet deployments. For frontline workers, intranet search must work on a personal mobile device, without a corporate email login, and ideally with some offline capability for environments with poor connectivity. Removing the login barrier that causes low adoption is not a convenience feature — it is the difference between a workforce that can access safety procedures, shift schedules, and policy updates in the moment they need them, and one that cannot. Organizations that have launched mobile-first, branded intranet apps report 90% frontline adoption within the first six months and 87% workforce engagement within a few months of launch. Those numbers reflect what happens when the access barrier is removed, not just when the content is improved. For a closer look at how this plays out in practice, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how organizations are rethinking access for distributed and frontline teams. ## Security and Governance: Search Results Must Respect Data Boundaries A search feature that surfaces every document in the organization is not an improvement — it is a compliance risk. Effective intranet search must enforce role-based access controls so that employees only see results they are authorized to view. MangoApps enforces permissions at the content level, not just the page level. Search results respect the same access rules as direct navigation: a frontline employee in one region does not see confidential HR documents scoped to another department, and a contractor does not see internal financial data. SAML/SSO integration means authentication is handled through existing identity providers, reducing the administrative burden on IT while maintaining security standards. This governance layer is what makes universal search safe to deploy across an enterprise — and what distinguishes a modern intranet platform from a file-sharing tool with a search bar bolted on. ## Customization and Continuous Improvement Different teams have different information needs. A search feature that works well for a legal team — where precision and version control matter — may not serve a customer support team that needs speed and conversational answers. Effective intranet search allows users to refine filters, set personalized alerts, and organize results in ways that match their workflows. Beyond individual customization, organizations should treat search quality as a metric, not a feature. Tracking zero-result queries, measuring time-to-answer, and collecting user feedback on result relevance all provide the signal needed to improve the search function over time. Regular assessment and refinement demonstrate to employees that their experience is being actively managed — which builds the trust and confidence that drives sustained adoption. For teams thinking about how knowledge management connects to broader workforce development, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers how embedded knowledge access supports skill-building in the flow of work. ## Measuring What Matters The metrics that matter for intranet search fall into three categories: **Adoption metrics:** - Daily active users as a percentage of total workforce - Frontline vs. desk worker adoption rates - Session frequency and average session length **Search quality metrics:** - Zero-result query rate (queries that return no useful results) - Click-through rate on top search results - Time from query to task completion **Business impact metrics:** - Reduction in help desk tickets for information requests - Self-reported time savings from employee surveys - Correlation between search adoption and engagement scores Organizations that track these metrics consistently can make the case for intranet investment in business terms — not just as an IT project, but as a measurable contributor to productivity and retention. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarks that help contextualize these measurements against peer organizations. ## What to Look for in an Intranet Search Solution When evaluating intranet platforms on search capability, these are the criteria that separate adequate from effective: 1. **Universal search scope** — does it span third-party storage (SharePoint, Google Drive, Box, Dropbox) or only internal content? 2. **AI-powered relevance** — does it understand intent, or only match keywords? 3. **Role-based result filtering** — do search results automatically respect access permissions? 4. **Mobile and offline access** — can frontline workers use it on personal devices without a corporate email or VPN? 5. **Analytics and feedback loops** — does the platform surface search quality data to administrators? 6. **Deployment speed** — can it go live quickly, or does it require months of IT configuration? For organizations evaluating MangoApps specifically, the [MangoApps Included in Leading Research Firm's Intranet Platforms Ev...](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides third-party context on how the platform compares across these dimensions. ## The Bottom Line Intranet search is not a feature — it is the mechanism through which every other investment in knowledge management, internal communication, and employee experience either pays off or goes to waste. When employees spend 2.5 hours a day searching for information (per IDC) and only 13% use their intranet daily (Social Edge Consulting), the gap is not a content problem or a culture problem. It is an access problem. Solving it requires search that is universal in scope, AI-aware in relevance, secure in governance, and accessible to every employee — including the 80% who are deskless (per Emergence Capital) and have never had a reliable path into the intranet at all. Organizations that close that gap do not just improve a metric. They recover thousands of hours of productive work, reduce the friction that drives disengagement, and give every employee — at a desk or on a factory floor — the information they need to do their job well. --- # Intranet Search Best Practices **Author:** Justina Kolb **Published:** 2023-11-13 **Category:** best-practices In the digital age, organizations rely on intranets to streamline communication, foster collaboration, and centralize vital information. However, the effectiveness of an intranet often hinges on one critical component: its search functionality. An inefficient or poorly configured intranet search can impede productivity and hinder access to essential resources. In this blog post, we’ll go over […] # Intranet Search Best Practices Per Social Edge Consulting, 91% of organizations operate an intranet — but nearly a third of employees never log in, and only 13% use one daily. SWOOP Analytics benchmarks average intranet engagement at six minutes per day. Those numbers describe a tool that exists but doesn't work, and the most common root cause isn't the software: it's search. Per IDC, employees spend 2.5 hours per day searching for information. For a desk worker, that inefficiency is frustrating. For a frontline associate answering a live customer question or a field technician verifying a safety protocol mid-task, it's an operational failure playing out in real time. When search returns irrelevant results or nothing at all, employees stop using the intranet and route questions through text, Slack, or the nearest manager — which is how institutional knowledge stays siloed rather than shared. The organizations that have closed this gap share a common pattern: they stopped treating intranet search as a UI feature and started treating it as a governed, AI-native, permission-aware information layer. What follows is a framework built around the four layers that determine whether intranet search actually works. --- ## Layer 1: Access — getting the foundation right before anything else No search configuration improves results for employees who can't reach the intranet in the first place. Per Emergence Capital, 80% of the global workforce is deskless. For that population — retail associates, field technicians, healthcare aides, warehouse staff — the first intranet search best practice isn't about relevance ranking or natural language processing. It's about whether they can open the tool at all. Mobile access without a corporate email address or VPN is a baseline requirement for distributed workforce deployments. Frontline employees should authenticate by phone number or employee ID and search on a personal device, without any IT-provisioned account. Effective deployments that meet this access threshold have achieved 90% frontline adoption within the first six months. When access requires a VPN or a corporate email that hourly workers don't have, even the best-configured search engine is invisible to the employees who need it most. Once access is solved, the mechanical search fundamentals follow: real-time results as users type, snippet previews that let employees evaluate relevance without opening every result, and advanced filters for date, file type, and content source. These aren't differentiators; they're table stakes. The gap opens in the layers above. --- ## Layer 2: Intelligence — treating AI-native search as the default engine, not an upgrade The current generation of intranet search tools splits into two meaningful camps: keyword-matching engines that return results by exact term, and intent-recognition engines that understand what an employee is actually asking. The distinction matters operationally. A keyword search for "parental leave" returns every document containing that phrase — outdated policy versions, HR blog posts, and benefits enrollment decks from three years ago. An intent-recognition engine returns the current policy document and the HR contact responsible for it. The first experience sends employees back to Google; the second solves the problem and builds the habit. AI-native semantic search applies natural language processing and intent recognition so queries are interpreted in context rather than matched against strings. Platforms that integrate with OpenAI, Gemini, or Azure OpenAI treat semantic understanding as the default search engine rather than a premium add-on. The practical effect: contextually relevant results from the first query, without requiring employees to learn boolean syntax or navigate folder hierarchies. Universal indexing extends the value of semantic search across the entire digital workplace. Most employees work across multiple systems — SharePoint, Google Drive, Box, Dropbox, and a dozen others depending on their role. Requiring a separate search in each system recreates the information-retrieval problem the intranet was supposed to solve. A [modern intranet](/solutions/modern-intranet) that indexes 200+ integrated platforms makes the intranet the single search entry point for the entire organization, not just its internal pages. Auto-suggestions and spelling corrections reduce zero-result rates and guide employees toward productive queries as they type. Relevance ranking that considers content type, metadata, recency, and user role ensures that actionable results surface at the top rather than the most-recently-updated ones. --- ## Layer 3: Security — the dimension most intranet search implementations miss Five competitors have built significant positioning around secure intranet search. Most intranet search best-practice articles, including earlier versions of this one, treat security as an IT concern separate from search configuration. That framing is wrong, and it creates a credibility gap with enterprise buyers who understand that search results surfacing unauthorized content are a compliance and trust failure — not just a configuration oversight. Permission-aware results are the mechanism that closes this gap. When search respects user access controls automatically, the results any given employee sees are scoped to the content they're authorized to access. A contractor shouldn't see executive compensation data. A regional manager shouldn't see content from a different business unit's workspace. These constraints aren't optional governance add-ons — they're what makes search safe to deploy broadly without requiring employees to exercise manual judgment about what they shouldn't be reading. SAML 2.0 and SSO integration provide the governance layer that makes permission-aware search reliable at scale. When identity is federated and access controls are defined once at the identity provider level, search results inherit those controls automatically rather than requiring manual permission mapping per content item. For organizations in regulated industries — healthcare, finance, government — infrastructure certifications matter alongside configuration. Platforms with FedRAMP ATO, HITRUST, ISO 27001, and SOC 2 Type II certification have been independently validated, which addresses the other half of the enterprise security argument that buyers in those sectors are actually asking. --- ## Layer 4: Governance — the process layer that determines whether search stays good Well-configured search degrades without active governance. The most common pattern: a successful intranet launch, followed by slow erosion of search quality as content accumulates without structure, outdated documents persist, and tagging becomes inconsistent. Organizations that treat search configuration as a one-time setup rather than an ongoing process consistently see engagement drop within 90 days of launch. Content tagging and categorization establish the metadata foundation that search depends on. Consistent tagging standards — enforced at upload rather than applied retroactively — ensure that user-generated content strengthens the knowledge base rather than adding retrieval noise. A [structured intranet governance plan](/articles/sharepoint-server-2016-2019-replacement-intranet-governance-plan) assigns content owners, defines review cycles, and creates the accountability structure that keeps search results trustworthy over time. Modern platforms support auto-governance: automatic archiving of content that hasn't been reviewed by a defined date, admin notifications when documents approach expiration, and analytics that surface content gaps. The analytics layer is the most operationally valuable: zero-results queries identify missing content, and high-volume searches with low click-through rates signal relevance ranking problems that need recalibration. User feedback mechanisms let employees flag irrelevant results, which gives admins the granular input needed to improve ranking without waiting for quarterly reviews. Structured user onboarding in the first two weeks after launch — covering how to use search filters, save frequent searches, and submit feedback — directly addresses the Social Edge Consulting finding that only 13% of employees use their intranet daily. Search isn't intuitive by default; adoption is a function of structured training as much as configuration quality. For organizations with global or distributed workforces, multilingual search rounds out the governance layer. Language-aware search with real-time translation in results ensures that non-English-speaking frontline and remote employees can retrieve information in their preferred language — a functional requirement that becomes a source of inequitable access when it's missing. --- ## How to measure whether intranet search is working Measuring search effectiveness requires tracking both usage signals and outcome signals, not just adoption metrics. Usage signals: zero-results rate (queries returning no content), search abandonment rate (users who search but click nothing), and the ratio of searches to page visits. These indicate whether the access and intelligence layers are functioning. Outcome signals: whether employees who use search complete tasks faster, submit fewer IT or HR tickets for information they should be able to self-serve, and report higher satisfaction in pulse surveys. These indicate whether the governance layer is actually working. Admins should review the top 20–30 search queries weekly. High-volume queries with low click-through rates signal a relevance ranking problem. Zero-results queries are direct content creation priorities. Most modern intranet platforms surface these analytics natively — if yours does not, that's a signal about whether the platform is built for governance or just deployment. For a worked example of what this looks like in a real organization, the [American College of Radiology case study](/resources/case-study-american-college-radiology) documents how moving to a unified employee communication platform with structured search directly reduced the information-retrieval friction that had been creating delays across distributed teams. --- ## What to expect from implementation timelines Traditional deployments requiring custom IT configuration take three to six months before search returns reliably relevant results. Modern cloud-native platforms are configured and returning accurate results in days — particularly when content is tagged and categorized before launch. For organizations replacing legacy systems, that gap matters. Per Social Edge Consulting, nearly a third of employees never log in to their current intranet. If the replacement requires months of implementation before search quality improves, those employees have little reason to change behavior. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarks across search quality, implementation timeline, and frontline accessibility — the criteria that matter most for organizations where the 80% deskless workforce isn't well-served by legacy tools. The case for treating intranet search as a strategic priority rather than a configuration detail is a direct calculation: per IDC, employees lose 2.5 hours per day to information search. Replacing a frontline employee costs between $4,400 and $15,000, and per Emergence Capital, those workers constitute most of the global workforce. The engagement loss from a poorly functioning intranet isn't an HR metric — it's an operational cost with a measurable return on fixing it. Intranet search that covers all four layers — access, intelligence, security, and governance — is what separates an internal tool employees return to from one that collects dust. Most organizations have already done the hardest part by investing in an intranet at all. The remaining gap is treating search as the information architecture decision it actually is. --- # Intranet Search To Boost Employee Productivity **Author:** Justina Kolb **Published:** 2023-11-10 **Category:** intranet In the modern workplace, where efficiency is paramount, businesses are continually seeking ways to boost employee productivity. One often-overlooked yet powerful tool in this pursuit is a well-optimized intranet search feature. This essential element not only simplifies information retrieval but also plays a crucial role in enhancing overall workflow efficiency, making it a key player […] # Intranet Search To Boost Employee Productivity According to IDC, employees spend an average of 2.5 hours each day searching for information. That figure covers everything from tracking down a policy document to finding the right colleague to answer a question that has never been written down. In organizations where that time multiplies across hundreds or thousands of employees, the cost isn't hypothetical — it accumulates every day whether or not anyone measures it. Intranet search is supposed to close that gap. For most organizations, it doesn't. The reasons why — and what better search actually requires — reveal a lot about how to make intranet investment pay off. ## Why most intranet search underperforms Social Edge Consulting research shows that 91% of organizations operate an intranet, but only 13% of employees use it daily. Nearly a third never log in at all. SWOOP Analytics benchmarks average daily intranet usage at just six minutes. Those numbers point to a tool that employees have largely given up on, not one they rely on. The root cause is usually poor search. Most legacy intranet platforms were built around document storage — a repository that staff could browse if they knew where to look. Search was an afterthought, often limited to native content within the platform and unable to surface results from the tools where employees actually create and store work: SharePoint folders, Google Drive, shared Box repositories, or Dropbox team spaces. When a search query returns partial results, outdated pages, or requires knowing the exact title of a file to find it, employees stop using search and start asking colleagues instead. The institutional knowledge the organization needs to share stays siloed by default — not because it doesn't exist, but because the retrieval layer fails to surface it. ## What intranet search needs to actually do Modern intranet search isn't a better version of the same index. It's a fundamentally different scope. **Federated search across all company knowledge.** Employees shouldn't have to know which system a document lives in to find it. An intranet search layer that spans native content alongside connected external storage platforms — SharePoint, Google Drive, Box, Dropbox — gives employees a single query entry point across the entire knowledge base. The search does the routing; the employee just asks the question. **People and expertise search, not just documents.** A significant share of the 2.5 hours IDC documents goes to finding the right person — someone who has done a similar project, navigated a specific regulatory requirement, or built deep experience in a technical domain. [Knowledge management](/solutions/knowledge-management) infrastructure that surfaces employee profiles, skills, and contribution history alongside documents reduces that friction directly. The result is a searchable knowledge graph, not just a file index. **Relevance tuned to organizational context.** Generic search ranking assumes that popular documents are useful documents. In an organizational context, a document's relevance depends on who's searching, what their role is, and what project they're working on. Search that applies role-based context surfaces results employees can actually use rather than results that are merely common. **Continuous-improvement feedback loops.** Administrators need to see which queries return no results, which content gets found repeatedly but not used, and which documents are searched for but outdated. Search that can't be measured and tuned degrades as the organization's content grows. ## Security and access control as the foundation of trust The most overlooked requirement for intranet search is also the most consequential: employees should only see results they have permission to view. This sounds obvious. It's surprisingly rare in practice. Many intranet search implementations create a single index across all content and apply permissions only when a user tries to open a document — not at the search result level. That means an employee might see a document's title and summary in search results even if they lack access to open it. For organizations with sensitive HR records, executive communications, or confidential project files, this is a compliance and trust problem. Intranet search built on SAML 2.0, OAuth 2.0, and LDAP integration inherits the permission structure that already exists in the organization's identity systems. When an employee's role changes in the HR system, their search results adjust automatically. When a document is restricted to a specific department, those restrictions propagate into search without requiring a separate configuration step. The result is a search experience employees trust — because what appears in results is genuinely accessible to them. HRIS-synced permissions also solve the staleness problem that plagues manually maintained access control lists. Permission boundaries that are kept current by the HR system rather than by administrator action remain accurate as the organization grows and changes. ## How AI-powered search changes the scope of the query AI-assisted search changes the nature of the query. Instead of requiring employees to construct an exact search string that matches how a document was titled, natural language search accepts the question as it would be asked in conversation: "what's our policy for customer escalations" or "who has managed a multi-state HR implementation before." The underlying capability is semantic matching — the search layer understands the intent behind a query, not just the literal words. This matters most for expertise search, where the question an employee has doesn't necessarily use the same vocabulary as the answer sitting in a colleague's profile or a project archive. For organizations evaluating enterprise search, the AI model powering natural language capabilities matters less than how the model integrates with the platform's permission layer and content scope. A model-agnostic approach — one that can connect to OpenAI, Google Gemini, Anthropic, or Azure OpenAI without locking the organization to a single provider — gives IT teams flexibility as AI capabilities evolve. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) identifies AI-assisted search as one of the fastest-differentiating capability areas across the intranet platforms evaluated in that cycle. ## Frontline and deskless workers need search too Emergence Capital estimates that 80% of the global workforce is deskless. Retail associates, field service technicians, healthcare aides, and manufacturing staff outnumber office employees across most industries — yet most intranet search tools were built for the 20% at a desk. Traditional intranet access assumes a corporate email address, a VPN connection, and time to sit at a workstation. None of those conditions reliably apply to frontline workers. The result is a search capability that exists for part of the workforce but not the part that most often needs to quickly look up a procedure, locate a policy, or find the right contact. Frontline-accessible intranet search works differently. Enrollment can happen via QR code, SMS, or personal email rather than a corporate provisioning process. Search queries run from a personal mobile device between tasks. Results load within seconds on a standard mobile network without requiring VPN access. This matters for productivity as much as for equity. When replacing a frontline worker in a mid-skill role costs $4,400–$15,000 per departure, tools that make those employees feel connected to organizational knowledge have a direct impact on retention. A frontline employee who can find the answer to a compliance question from their phone doesn't have to interrupt a manager, wait until their next shift, or guess. A distributed professional organization connecting staff across multiple locations found that consistent search access regardless of physical location was the precondition for the platform delivering value — as the [American College of Radiology case study](/resources/case-study-american-college-radiology) documents. When some staff could reliably find information and others couldn't, the knowledge-sharing gap the platform was meant to close persisted. ## What ROI from better intranet search actually looks like The math on search productivity is straightforward. IDC's 2.5-hour daily figure, applied across a workforce of 500 employees, represents over 1,200 person-hours lost to information search every workday. Reducing that figure by 30% through better search retrieval — a conservative estimate for organizations moving from legacy to modern intranet search — recaptures the equivalent of dozens of full-time employees annually. The harder-to-quantify return is the knowledge that stops being acted on because it never gets found. The policy question that went unresolved. The project that duplicated work already done by another team. The expert who wasn't identified before a decision was made without their input. Better intranet search doesn't just speed up information retrieval — it changes what knowledge the organization is able to use. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) identifies search and information access as among the highest-return investments organizations can make in connected employee platforms, specifically because the productivity dividend compounds: faster search today reduces the friction that causes employees to give up on searching tomorrow. ## What to look for when evaluating intranet search Organizations assessing intranet search capabilities should test five questions before committing to a platform: **What's the content scope?** Does search cover only native content, or does it federate across connected platforms including SharePoint, Google Drive, and third-party storage? A platform that requires employees to know where content lives before they can search for it is still a partial solution. **How are permissions handled at the result level?** Do search results respect the same access controls that govern document access, or are restrictions applied only at the document-open step? **Does it support natural language queries?** Can employees ask questions in plain language, or must they construct exact-match strings? For expertise and people search especially, semantic matching is the difference between a tool employees use and one they abandon. **What's the mobile and frontline access model?** Can employees search from a personal device without VPN? Does enrollment require a corporate email address? These questions determine whether the search capability serves the full workforce or only the office-based portion. **What analytics does the platform surface?** Administrators need to see which queries return no results, which content gets searched but not opened, and which documents are frequently accessed but outdated. Search that can't be measured degrades as organizational content grows. ## From underused tool to operational infrastructure The gap between a 13% daily active rate and a search tool that most employees rely on isn't closed by deploying a better search index. It's closed by deploying search that is fast enough, accurate enough, and accessible enough that employees choose it over asking a colleague or guessing. That means federated scope across all company content, permission inheritance from existing identity systems, AI-assisted natural language capability, and genuine mobile access for frontline workers. When those components work together — and when the analytics layer gives administrators the information to keep improving the index — intranet search stops being a feature employees reluctantly use and becomes the mechanism through which organizational knowledge actually flows. The answer to "how do we boost employee productivity with intranet search" is not a faster index. It's an index broad enough to cover all company knowledge, secure enough to earn employee trust, smart enough to understand intent, and accessible enough to serve the full workforce — not just the part sitting at a desk. --- # Benefits of an Intranet Search Engine **Author:** Justina Kolb **Published:** 2023-11-10 **Category:** intranet In this day and age, the ability to access and harness knowledge quickly and efficiently is paramount. From finding your way around a new city to identifying a bird you saw on a walk, having fast access to a plethora of information feels second nature. A quick Internet search allows you to get to your […] # Benefits of an Intranet Search Engine According to IDC, employees spend an average of 2.5 hours per day searching for information. Multiply that across a workforce of 1,000 people and the organization is losing the equivalent of more than 300 full-time employees to search friction alone. Yet Social Edge Consulting found that 91% of organizations already operate an intranet—and nearly a third of their employees never log in. The problem isn't a lack of technology. It's a lack of usable search. An intranet search engine is the function that makes an intranet actually useful. Without it, a digital workplace is a filing cabinet with no labels. With it, employees find policies, people, documents, and announcements in seconds—regardless of where in the organization the information lives. This post covers what that difference looks like operationally and what capabilities to evaluate when choosing a platform. ## What intranet search actually solves The typical knowledge problem in a large organization isn't that information doesn't exist. It's that information exists in too many places—shared drives, email threads, departmental wikis, HR systems, project tools—and employees don't know which system to check first. Per SWOOP Analytics, the average employee spends just six minutes per day actively using their intranet. That number reflects a usability failure, not a content failure. Effective intranet search collapses a multi-system search into a single query. Employees type what they're looking for once and get a ranked result set that spans connected platforms—SharePoint, Google Drive, Box, and internal knowledge bases—without switching applications. That consolidation is the primary ROI driver: fewer hours lost to searching, fewer duplicate documents created, fewer support tickets raised because someone couldn't find a policy. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) identifies unified search as one of the top differentiators between intranets that drive measurable adoption and those that collect dust. ## The productivity case The IDC figure—2.5 hours per day per employee—understates the full cost because it only counts active search time. It doesn't count the downstream effects: decisions made on outdated information, work duplicated because the original version was unfindable, or questions routed to HR and IT that employees could have self-served with better search. An intranet search engine reduces each of these failure modes: - **Duplicate work**: When employees can find what already exists, they don't recreate it. Structured, searchable knowledge reduces document sprawl over time. - **Support ticket volume**: When policies, benefits information, and procedures are findable in seconds, employees don't open tickets for answers. HR and IT capacity shifts toward higher-value work. - **Decision quality**: Employees with access to current data—past campaign results, compliance updates, project history—make better-informed decisions than those working from memory or outdated printouts. - **Onboarding speed**: New hires find training materials, org charts, and process guides without relying on a colleague to point them to each one. Fast knowledge access is a leading factor in new hire confidence and 90-day retention. None of these benefits materialize from a search engine that only indexes one system. The productivity case for intranet search is inseparable from federated search—the ability to surface results from every connected repository in a single interface. ## Frontline and mobile access According to Emergence Capital, 80% of the global workforce is deskless. Retail associates, nurses, warehouse operators, and field technicians have never had a laptop on a desk. For this population, an intranet that requires a corporate email address and a VPN-connected browser is functionally inaccessible. Modern intranet search extends to iOS and Android apps with offline capability and no corporate email requirement. Frontline employees can search for shift schedules, safety procedures, product specs, and HR policies on the same personal device they use for everything else. When a hospital floor nurse can look up a protocol in ten seconds instead of tracking down a supervisor, search has direct operational impact. Failure to provide frontline workers with usable search also carries measurable retention risk. Replacing a frontline employee costs between $4,400 and $15,000 in recruiting, training, and productivity loss. A disconnected digital experience that leaves frontline workers unable to find basic information is a documented disengagement driver—and an avoidable one. ## Knowledge sharing and collaboration An intranet search engine changes how organizations manage institutional knowledge over time, not just how individuals find things. When employees know that what they create is searchable, they're more likely to document it. When managers know that past project materials are findable, they don't recreate wheels buried three directories deep. Over time, a searchable intranet creates a virtuous cycle: better documentation produces better search results, which produces higher trust in the system, which encourages more documentation. This dynamic matters most for [knowledge management](/solutions/knowledge-management) in organizations with high turnover or distributed expertise. When a subject-matter expert leaves, their documented work stays findable. When a new hire joins, their onboarding time shortens because institutional knowledge is accessible rather than trapped in someone's inbox. Social Edge Consulting found that only 13% of employees use their intranet daily—which means 87% don't. That gap between potential and adoption is almost entirely a search problem. Employees use tools that reliably help them find what they need. They avoid tools that don't. ## Security and permissions A common concern with enterprise-wide search is whether it exposes sensitive content. In well-architected intranet search, result sets reflect permission inheritance—employees only see content they are already authorized to access. HR documents appear in results for HR staff, not the general organization. Executive materials surface only for appropriate access levels. Payroll data, compliance records, and restricted content stay behind role-based access controls regardless of the search term that triggered the query. Administrators get audit dashboards showing who accessed what and when, without requiring manual record-keeping. For organizations in regulated industries, this governance layer is a procurement requirement. Healthcare organizations need HIPAA-aligned access controls. Financial services firms need audit trails. Manufacturing and retail organizations with shift-based workforces need to demonstrate that frontline employees received required safety communications. A modern intranet search engine makes these compliance demonstrations a byproduct of normal operations rather than a separate documentation effort. ## Key capabilities to evaluate Not all intranet search engines deliver on the same dimensions. The capabilities that consistently separate high-adoption implementations from low-adoption ones: **Federated search across connected systems.** A search that only indexes the intranet itself provides limited value. Look for connectors to SharePoint, Google Drive, Box, Dropbox, and other repositories employees already use. The goal is one search, not one more system to search. **AI-powered result ranking.** Basic keyword matching returns documents that contain the search terms. AI-powered search returns documents that are actually relevant to the query—accounting for the employee's role, location, and access level to surface results that are both accurate and applicable. **Natural language processing.** Employees don't search with Boolean operators. They type phrases like "how do I request PTO" or "kitchen permit process." NLP-capable search interprets the intent behind the query and returns relevant results even when the exact phrase doesn't appear in any document. **Analytics and content gap reporting.** Administrator dashboards that surface frequently searched-but-unfound terms give content teams a direct signal for what to create. If 200 employees per month search for "401k vesting schedule" and return zero results, that's a documented content gap. **Mobile-first access with offline support.** For frontline workers without desktop access, the mobile search experience must match the desktop experience in quality. Offline capability matters for employees in areas with unreliable connectivity. ## How to measure the impact Organizations that establish a pre-deployment baseline get significantly more value from intranet search investments because they can demonstrate progress rather than assert it. Four metrics worth tracking: - **Search-to-answer time**: How long does it take an employee to find a specific piece of information from the moment they start looking? This is measurable with a structured user test and should be re-run 90 days post-deployment. - **Support ticket volume for self-serviceable questions**: Track tickets related to HR policies, benefits, and compliance procedures. A well-deployed intranet search engine typically deflects a meaningful percentage within the first quarter. - **Active login frequency by department**: Departments with consistently low intranet logins usually have the lowest trust in search—a signal that indexing coverage or content relevance needs attention. - **Search exit rate**: The percentage of searches that result in no click-through. A high exit rate indicates that results aren't matching employee intent, even when results exist. The [Gallup 2026 State of the Global Workplace report](/articles/gallup-2026-state-of-the-global-workplace) found a direct correlation between employee access to timely information and engagement scores. Organizations that can link search quality to engagement have a defensible case for continued intranet investment—not just in IT budget cycles, but in cross-functional conversations about retention and culture. ## What good intranet search looks like The organizations that report the highest return from their intranet investments share a common characteristic: they treat search quality as a first-order requirement, not an afterthought. They define what "findable" means before go-live, measure it consistently, and act on the analytics rather than waiting for employees to complain. A [modern intranet](/solutions/modern-intranet) has evolved beyond a static document repository. It's a searchable, role-aware, mobile-accessible knowledge layer that serves desk workers and frontline employees in the same query. When employees can find what they need in seconds—across every connected system, on any device, with results scoped to what they're actually authorized to see—the 2.5 hours per day IDC identified as search friction becomes recoverable. That's the benefit an intranet search engine delivers when it's built right. --- # How to Optimize Your Intranet Search **Author:** Justina Kolb **Published:** 2023-11-10 **Category:** intranet The modern work environment is fast-paced and information-rich. Therefore, today’s workforce needs – and expects – fast access to useful data and resources. That’s why implementing and maintaining a well-honed intranet search engine can be the cornerstone of your organization’s success. It’s the digital compass that guides your employees through a maze of documents, data, […] Per Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in, and only 13% use one daily. Meanwhile, IDC research finds employees spend an average of 2.5 hours per day searching for information. Those two facts together define the core problem: most intranets exist, but their search experience is too broken to make them worth using. Optimizing your intranet search comes down to three levers: choosing the right search technology, training the people who create and consume content, and governing the content itself so results stay accurate over time. This guide covers all three, with specific tactics you can act on immediately. ## Ideal Intranet Search Technology The technology underpinning your company search engine is critical. An effective internal search engine must efficiently crawl, index, and retrieve information from documents and different forms of media within your intranet. This determines the speed and accuracy of your search results. Many intranet search solutions don't provide easily configurable options such as relevance tuning, advanced filters, or federated search across platforms. Federated search is worth calling out specifically: a well-architected intranet search can span connected external storage platforms — SharePoint, Google Drive, Box, Dropbox — not just internal content repositories, giving employees a single query that surfaces results from across the entire digital workplace. With an intranet search that takes into account location, language, user roles, and permissions, team members receive a personalized, relevant experience tailored to their individual needs. Consider also how your users actually search. Are they using specific keywords, or do they prefer natural language queries? Modern AI-native search layers — drawing on models such as OpenAI, Gemini, or Azure OpenAI — can interpret intent behind a query rather than matching keywords literally, delivering role- and location-aware results that improve with use. Implementing saved searches at an individual or company-wide level allows users to find exactly what they're looking for in seconds, minimizing context switching so employees stay focused. For organizations evaluating platforms, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an independent benchmark of how leading solutions compare on search and findability. ## Security, Permissions, and Search Quality Role-based permissions are not just a compliance requirement — they are a search-quality differentiator. When search results respect security boundaries, employees see only what they are authorized to see, which means results are inherently more relevant and trustworthy. Look for platforms that support SSO standards such as SAML 2.0 and OAuth 2.0, and that enforce permissions at the index level rather than filtering results after retrieval. This ensures that sensitive HR, legal, or executive content never surfaces in the wrong context, while still making broadly shared knowledge instantly findable. MangoApps' [solutions/modern-intranet](/solutions/modern-intranet) architecture applies these permission layers at the content object level, so a frontline associate searching for a safety procedure sees exactly the same search interface as a corporate manager — but each receives results scoped to their role, site, and language. ## Frontline and Mobile Search Access The article's optimization advice applies equally to desk workers and the 80% of the global workforce that is deskless, per Emergence Capital. Frontline employees — in retail, manufacturing, healthcare, and logistics — need access to intranet search and resources without a corporate email address or VPN, using only a mobile device. If your search experience requires a laptop and a network login, you are effectively excluding the majority of your workforce from the knowledge base you've built. Poor intranet adoption among deskless workers carries a direct cost: replacing a single frontline employee costs between $4,400 and $15,000 on average. Modern intranet deployments that prioritize mobile-first search — offline access, no-email login, two-tap resource retrieval — have demonstrated 90% frontline adoption within the first six months as an achievable benchmark. SWOOP Analytics notes that the average employee spends only six minutes per day using intranet tools, which underscores how critical it is that those six minutes return useful results immediately. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how organizations are closing the search and access gap for frontline teams specifically. ## User Best Practices You might not think your company's intranet users have much to do with creating an optimal intranet search, but working closely with them, content publishers, and information owners is actually vital for it to operate at full capacity. As with all improvement projects, the process of bettering your intranet search carries an element of change, which inherently starts with the people who use and contribute to it. ### Content Administrators Many intranets operate under a decentralized publishing model, meaning the responsibility for creating and publishing content is distributed across various individuals or teams. Content publishers need training and guidance on effective content preparation and publication, because the ability to enhance your intranet search lies in crafting content that maximizes discoverability. This entails tasks such as tagging, utilizing metadata, selecting appropriate keywords, and optimizing titles. Providing training and support to empower your content publishers to adhere to these guidelines can significantly impact the strength of your intranet search. Content administrators can also use analytic features to determine how their intranet search is performing. Easy-to-read reports that clearly state your intranet's most common searches, searches that return the poorest results, and a variety of user feedback give admins the data to make adjustments to their intranet search strategies accordingly. It's important to continuously update and improve your internal search tool to ensure it remains a valuable, reliable resource for your team. This also signals to staff that you are committed to providing up-to-date tools that set them up for success. Knowledge management tools built into the intranet — structured wikis, topic pages, and governed content workflows — make the administrator's job significantly easier by surfacing stale content for review rather than leaving it to accumulate. The [solutions/knowledge-management](/solutions/knowledge-management) page outlines how a structured approach to content governance directly improves search result quality over time. ### Information Owners An effective intranet search empowers users to access content across the entire organization. However, valuable information often remains siloed because information owners in various roles are not actively sharing their insights. These isolated data pockets impede organizational progress and reduce the effectiveness of your internal search. Working with diverse information owners to establish a comprehensive and interconnected intranet search solution is essential. As long as experts on your team share their knowledge, users can learn from each other and find new information easily via your intranet search feature. ### Network Users Providing guidance that helps users get the most from your intranet search makes a measurable difference in how they perceive its effectiveness. If users are not fully aware of how to use all of your intranet's search features, they will likely feel it falls short of their needs. Educate your team on advanced search techniques and best practices so they utilize your intranet's search to its full potential. Gathering feedback on users' search experiences is also vital. Did they find what they needed? Is the search feature easy to use? What improvements would they suggest? Gathering precise feedback provides actionable data that leads to improvements in both your intranet search and the content on your site. Acting on users' feedback will also lead your team to hold your intranet in higher regard. --- **Great Harvest Bread Co + MangoApps** **Learn how Great Harvest uses MangoApps to:** - Allow store members to share knowledge, ideas, and information - Centralize resources and information in an easily searchable hub - Build a strong employee recognition program by offering incentives and kudos --- ## Intranet Search Content Management Effective content management is the backbone of a successful intranet search engine. Properly tagging and organizing content, coupled with metadata, helps the search engine understand and categorize information accurately. Ensuring content is given relevant tags and titles increases its findability. Leveraging AI to provide content recommendations based on user behavior can further enhance search functionality. Ensuring scalability is crucial, especially if your organization is rapidly growing and accumulating more data. Routine updates and maintenance are also essential to keep your search engine performing at its best. The quality and volume of content on an intranet also determines how successful its search is. Traditional intranets deliver static, ungoverned content that becomes stale, making search results unreliable over time without active governance workflows. As organizations grow, intranets often overflow with outdated and irrelevant content. If users have to sift through poor search results that aren't pertinent to their needs, their experience suffers and productivity slows. Keeping your intranet clear of antiquated resources — and ensuring it contains only current, well-written information — is key to ensuring users find the intranet search helpful. MangoApps provides an Advanced Search built for this reality. With real-time content indexing, mobile device optimization, tailored results for every user, and federated search across connected platforms, MangoApps' [key-features/company-portal](/key-features/company-portal) empowers employees to gain and share knowledge efficiently. The [MangoApps Included in Leading Research Firm's Intranet Platforms Ev...](/articles/mangoapps-2026-forrester-wave-intranet-platforms) recognition reflects independent validation of this approach. ## How to Measure Whether Your Intranet Search Is Working Optimization without measurement is guesswork. The following metrics give you a concrete picture of search health and a baseline for improvement: - **Zero-results rate:** The percentage of queries that return no results. A rate above 10–15% signals either missing content or poor tagging. - **Search abandonment rate:** Users who run a search and immediately leave without clicking a result. High abandonment indicates relevance problems. - **Time-to-find:** How long it takes a user to locate a specific document from the moment they open the search bar. Benchmark against the IDC figure of 2.5 hours per day lost to information search to frame the business case. - **Daily active search users:** Track against the Social Edge Consulting benchmark that only 13% of employees use an intranet daily. Improvement here is a direct indicator of adoption. - **Content freshness score:** The percentage of indexed content updated within the past 12 months. Stale content is the leading cause of poor search results. Review these metrics monthly during the first year of any search optimization initiative, then quarterly once baselines stabilize. Share results with content administrators and information owners so accountability is distributed, not centralized. ## Your Next Steps: An Implementation Roadmap If you are starting from a low baseline — low daily usage, high zero-results rates, or frontline workers who have never logged in — the following sequence is the most direct path to improvement: 1. **Audit your current content.** Identify and archive or delete content that has not been accessed or updated in more than 18 months. This single step improves result relevance faster than any technology change. 2. **Configure role-based permissions and federated search.** Connect external storage platforms and apply permission layers so every employee sees results scoped to their role and location. 3. **Train content administrators.** Run a structured session on tagging, metadata, and title optimization. Provide a one-page style guide they can reference when publishing. 4. **Enable mobile access for frontline workers.** Remove the VPN and corporate email requirements. Confirm that search works on the devices your frontline teams actually carry. 5. **Set a 90-day measurement cadence.** Pull the five metrics above at day 30, 60, and 90. Share results with leadership alongside the business case framed by the IDC and Social Edge Consulting data. 6. **Iterate on AI personalization.** Once baseline governance is in place, layer in AI-driven relevance tuning — natural language queries, role-aware ranking, and proactive content recommendations — to move from functional search to genuinely useful search. Organizations that follow this sequence have reached 90% frontline adoption within the first six months as a documented benchmark. The [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study illustrates how a structured rollout translates into measurable engagement gains. --- # How The Kansas City Chiefs Revolutionized Event Employee Communication for Over 600 Game-day Staff **Author:** Andy Tolton **Published:** 2023-11-01 **Category:** customer-success-stories For professional sports teams and the venues they play in – event employee communication is a significant challenge. The staff is spread out, and issues arise urgently that need to be attended to so that fans can enjoy their experience. It’s important that every employee is reachable at a moments notice, and that the employee […] # How the Kansas City Chiefs Revolutionized Event Employee Communication for Over 600 Game-Day Staff When the Kansas City Chiefs set out to improve communication with their 600+ event staff, the goal was straightforward: make sure every employee knew what was expected of them on game day. What they discovered was that the communication problem was also an infrastructure problem — and that solving it required replacing fragmented tools with a single, branded app built for workers who don't sit at a desk. The result was Huddle, the Chiefs' dedicated event services employee app built on the MangoApps platform. Within the first game season, Huddle achieved 90% adoption among event staff — more than double the organization's prior 40% average. For the first time, reaching all 600 team members on any given game day became reliable rather than aspirational. That outcome didn't happen by accident. It happened because the Chiefs chose a different architecture: one that treated frontline access as a requirement, not a workaround. ## The event staff communication challenge Professional sports venues operate under conditions that stress-test any communication system. Staff are distributed across the building. Issues arise urgently and need immediate resolution before they affect the fan experience. Workers report for shifts hours apart. And unlike corporate employees, most event staff don't have assigned workstations, corporate email accounts, or time to check a browser-based portal between tasks. The Chiefs were managing all of this with a patchwork of platforms: emails, text messages, Facebook groups, and separate systems for checking schedules and clocking in and out. As Andrew Rodriguez, a member of the Chiefs event staff, described it: "It was kind of a crapshoot, to be honest. A lot of people kind of fell through the cracks." The fragmentation had a predictable downstream effect. When employees can't reliably receive communications, they fill the gap with informal channels — and the organization loses visibility into whether critical information has reached anyone at all. Caitlin Petit, Director of Event Services for the Chiefs, recognized this directly: "We were seeking a solution for communication at the heart of everything, looking for something to consolidate all of our information." ## Why fragmentation is a structural problem, not a habits problem The Chiefs' experience reflects a broader pattern in frontline workforce management. According to Social Edge Consulting, 91% of organizations already operate some form of intranet — yet only 13% of employees use those tools daily, and nearly a third never log in at all. SWOOP Analytics found that the average employee spends just six minutes per day inside intranet platforms. The cause is rarely the employees. According to IDC research, workers spend 2.5 hours per day searching for information they cannot easily find — a figure that reflects what happens when communication tools don't match how workers actually operate. According to Emergence Capital, 80% of the global workforce is deskless. The platforms those workers are given were largely built for the desk employees who represent the other 20%. For event staff specifically, the gap is sharper still. Seasonal and hourly workers typically have no corporate email address. They may not have VPN access. They often arrive on-site without time to boot a workstation or navigate a browser-based system. A communication platform that requires any of those things is effectively unreachable for a significant portion of the workforce it is supposed to serve. The Chiefs weren't dealing with a workforce that didn't want to communicate. They were dealing with a workforce that couldn't reach the tools being handed to them. ## The solution: a branded app built for how event staff actually work The Chiefs worked with MangoApps to build Huddle — a dedicated [employee app](/solutions/employee-app) configured specifically for the event services team. Huddle unified the workflows that had previously been spread across multiple platforms: schedules, training, peer-to-peer communication, and top-down announcements all accessible in a single experience. Two design decisions were central to the adoption outcome. First, Huddle was accessible on personal mobile devices without requiring a corporate email address, VPN, or workstation login. This removed the single most common barrier for hourly and seasonal staff — the infrastructure requirement that assumes workers have the same IT setup as a desk employee. Staff could enroll and start using the app before they'd ever checked a shift schedule through the old system. Second, the app was branded as Huddle — not as a generic enterprise platform. That distinction matters more than it might appear. A branded experience signals to staff that the tool was built for them, not handed down from an IT department. The difference between adopting something that looks like your organization's tool and adopting something that looks like generic software is measurable, and the Chiefs' adoption numbers reflect it. The app also supported both mobile and web browser access, which meant that edge cases — staff who preferred a laptop or tablet — weren't forced into a mobile-only workflow. Adaptability in the access model contributes to adoption across a heterogeneous workforce. ## What features drove the jump from 40% to 90% The shift from the Chiefs' prior 40% communication reach to 90% adoption on Huddle didn't come from any single feature. It came from removing friction that had made prior tools unusable for the specific population the Chiefs were trying to reach. **Single-app consolidation.** Karen Claussen, a Chiefs event staff member, described the change directly: "Before, we might have had two or three different resources available to us, and sometimes it was confusing… And now that we have just one app, it's great!" When employees don't have to remember which tool holds which information, adoption follows. The tool becomes the default because it's the only place to check. **Schedule and clock-in integration.** Combining schedules with communication removed the separate system that had been creating friction in the old model. Staff could see their shifts, receive updates about changes, and confirm attendance in the same place — eliminating the need to toggle between apps or rely on text chains for shift information. **Mobile-first access on personal devices.** For workers who are on-site for a four-hour shift with no access to a desk computer, mobile is not a convenience — it's the only viable access model. Huddle's enrollment process didn't require IT provisioning, which meant new staff could get up and running before their first shift, not after. **Bidirectional [employee communications](/solutions/employee-communications).** The communication model in Huddle wasn't unidirectional. Staff could communicate laterally, and supervisors could push urgent updates that reached everyone rather than hoping individuals had seen a Facebook post or checked their email. The combination produced an environment where using the app was easier than not using it — the condition that actually drives sustained behavioral change among workers who face no formal penalty for ignoring a communication platform. ## Results: 90% adoption and interest from other departments The Chiefs saw 90% adoption among event staff within the first season of Huddle's deployment. That number represents more than a platform metric. For an organization with 600 staff, it means the difference between reaching 240 people and reaching 540. Justin Johnson, Kansas City Chiefs Director of Service Delivery, was direct about the outcome: "I am 100% satisfied with the decision to choose MangoApps… and I see a lot of promise in the future for it." The impact extended beyond the event services team. Security and Stadium Operations departments independently expressed interest in adopting Huddle for their own staff — a signal that the tool was performing well enough operationally that adjacent teams wanted it, rather than being mandated from above. This pattern — where adoption in one department creates pull toward adjacent departments — is characteristic of tools that actually solve the problem they were built for. When a platform works, the evidence spreads internally without a change management campaign. For context on how unusual this outcome is: most employee experience platforms generate the usage patterns cited above — six minutes per day, 13% daily engagement. The Chiefs' 90% adoption reflects the difference between an access model designed for frontline workers and one designed for desk employees whose organizations happen to have frontline staff on payroll. These are not different implementations of the same approach. They are different starting assumptions about who the platform is for. ## What event and operations teams can take from the Chiefs model The Chiefs' deployment offers a repeatable model for event, stadium, venue, and operations teams whose communication challenges look similar. The conditions that created the original problem — seasonal workforce, no corporate email, high staff turnover, urgent in-event communications, separate systems for schedules and messaging — are common across the category. The Chiefs' solution can be evaluated against those conditions directly. Three decisions drove the outcome. First, they selected an [employee app](/solutions/employee-app) that could enroll workers without corporate email provisioning — removing the access barrier that eliminates most enterprise platforms as candidates before evaluation begins. Second, they branded the experience as Huddle, creating a team-specific identity rather than deploying a generic platform. Third, they consolidated communication, scheduling, and training into one application rather than adding another tool to the existing fragmented stack. The measurement question for any similar deployment is adoption, not feature count. A platform with extensive capabilities that 40% of staff use is not an employee communications platform in any meaningful operational sense. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) includes frameworks for setting 90-day adoption benchmarks and tracking engagement signals before attrition or service quality numbers shift — useful context for operations teams setting expectations before an implementation begins. For organizations still running separate tools for different workforce segments, the Chiefs' experience is evidence that consolidation produces a measurable outcome, not just operational simplicity. When 80% of the workforce cannot reliably access the communication platform, adding features to that platform is unlikely to close the gap. The problem is the access model. The Chiefs solved it by starting from a different set of assumptions — and the 90% adoption rate is what that decision looks like in practice. The [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) confirms that employee engagement remains one of the most consequential variables HR and operations teams track. The technology decisions that determine whether frontline workers can receive, find, and act on communications are a direct input to that variable. The Chiefs' deployment is a case study in taking that input seriously before a single shift begins. --- # SharePoint, Teams, and Google Drive Files Now Federated in MangoApps Search **Author:** MangoApps **Published:** 2023-11-01 **Category:** press-release MangoApps announced enhancements to its Search capabilities by federating Microsoft SharePoint, Teams, and Google Drive directly into the MangoApps Search experience. MangoApps was also recently recognized as a Representative Vendor in the Gartner® Market Guide for Employee Communication Applications. # Federated Search: How MangoApps Brings SharePoint, Teams, and Google Drive Into One Search Bar Per IDC research, employees lose 2.5 hours every workday searching for information they cannot locate. That figure is not a user experience complaint — it is an infrastructure diagnosis. When file storage is split across SharePoint, Microsoft Teams, and Google Drive with no common search layer, every search task requires a judgment call before the actual search begins: which system holds this file? The search itself is secondary to the navigation overhead. MangoApps federated search eliminates that overhead by returning results from all three platforms in a single query, without requiring employees to change tools or re-authenticate. The deeper claim is economic. Per Awesome Technologies' 2025 cost modeling, SharePoint alone costs a 1,000-user enterprise between $130,000 and $426,000 in the first year when implementation, customization, and governance are included. Organizations that layer Teams and Google Drive on top of that without a unified search layer pay governance overhead across every platform independently — separate access control reviews, separate version tracking, separate retention enforcement — while still leaving employees to navigate three separate search interfaces. Federated search addresses the governance cost and the productivity cost simultaneously, from a single layer that requires no file migration. ## Why fragmented search is not a usability problem Per Social Edge Consulting, 91% of organizations operate an intranet, but only 13% of employees use it daily, and nearly a third never log in at all. Per SWOOP Analytics, average daily time spent on intranet tools across enterprise organizations is six minutes. Those numbers do not describe employees who dislike their tools. They describe employees who have learned through repeated experience that searching inside a single platform returns incomplete results. When search fails often enough, employees default to asking a colleague or scrolling through email — slower methods that actually surface what they need. Every workaround is a signal that the underlying search infrastructure has been abandoned rather than used. The tool is not failing at the margin; it has been routed around entirely. The economic consequence scales with headcount. For a 1,000-person organization working 250 days a year, the IDC figure of 2.5 daily hours lost to information search represents 625,000 hours of recoverable operational capacity annually. That is not a rounding error. It is the full scale of the productivity loss that fragmented file storage creates when no unified search layer connects the platforms — before the governance costs are counted. ## What federated search changes — and what it doesn't MangoApps federated search connects to each platform's API and returns results from SharePoint document libraries, Teams channel files, and Google Drive shared content alongside native MangoApps content in a single results view. Employees enter a query in the MangoApps search bar and see a ranked list spanning all connected systems — with file names, folder paths, and platform indicators visible so they can immediately determine where a file lives and who holds access to it. Files stay in the platforms where they were created. Permissions stay in force: a file that a user cannot access in SharePoint remains inaccessible when it surfaces in MangoApps search results. The existing permission models of SharePoint, Teams, and Google Drive are respected by the federated layer. Nothing is migrated, and no existing governance configuration is changed. Setup uses existing SSO credentials. Administrators connect each integration through the MangoApps integration settings panel using service account credentials and OAuth consent flows. For Microsoft integrations, a Microsoft 365 administrator grants the necessary API permissions; for Google Drive, a Google Workspace administrator does the same. Most organizations see results from federated sources within 24 hours of activation, with a scheduled refresh cycle handling index updates after that. ## The AI layer: what unified search actually means The version of federated search that matters for enterprise adoption is not keyword-matched results across three file systems. It is a search experience that understands intent and personalizes results by role — which is what separates a useful unified search layer from a file-system aggregator. MangoApps applies an AI layer across the unified search index that weights results by recency, by the user's role and team membership, and by what colleagues in the same department have accessed recently. Natural language queries — "Q3 budget approval process," "emergency protocol updates," "new hire onboarding checklist" — return relevant documents even when none of them are titled with those exact words. The AI layer identifies semantic intent and ranks results accordingly across SharePoint, Teams, Drive, and native MangoApps content simultaneously. Personalization means that search results for the same query differ meaningfully between users. A finance team member and a field operations manager asking the same question should see different files at the top of their results — the content most relevant to their role, not a generic ranked list. This is the capability that makes unified search useful rather than merely complete: results that improve as the system learns which content each user actually relies on, rather than returning the same static set of files regardless of who's asking. For [knowledge management](/solutions/knowledge-management) teams, this closes the gap that every multi-platform deployment creates — the inability to run a single authoritative search across the organization's entire file ecosystem. Document repositories, project files, and shared drives become one searchable space, with intent-ranked results rather than keyword-matched file names. ## The frontline case: where federated search has the largest impact The business case for federated search is frequently framed around desk workers and office-based teams. The stronger case may be for frontline employees. Per Emergence Capital, 80% of the global workforce is deskless — working in manufacturing, healthcare, retail, logistics, and public service settings where desktop access is intermittent or unavailable. A frontline worker who needs a file typically searches on a mobile device between tasks. If that search requires switching between three applications with separate mobile interfaces and separate authentication flows, most workers will not complete it. They will ask a supervisor or proceed without the information they need. The workaround that desk workers default to — asking a colleague — is often unavailable to frontline staff working alone or on rotating shifts without reliable desktop access. MangoApps mobile-first design means federated search functions identically on a smartphone and on a desktop. One query surfaces results across SharePoint, Teams, Drive, and MangoApps content — with no switching, no re-authentication, and no separate application to open. A warehouse associate checking an updated safety procedure, a retail employee confirming a product specification, or a healthcare aide reviewing a protocol change can complete the search in the time it takes to type a query. ## The governance case for IT For IT and operations teams, the governance argument for federated search is at least as strong as the productivity argument. When files exist across SharePoint, Teams, and Google Drive with no unified visibility layer, IT teams cannot enforce consistent access controls, version tracking, or retention policies across all three platforms. Compliance audits become manual reconstruction exercises — export from SharePoint, cross-reference with Teams, reconcile against Drive — rather than a single-platform query. The SharePoint first-year cost range of $130,000–$426,000 for a 1,000-user enterprise (per Awesome Technologies' 2025 modeling) represents only the SharePoint layer. Adding Teams and Google Drive governance overhead independently multiplies the compliance surface area without adding any cross-platform visibility into what exists where. Federated search adds the visibility layer that governance teams need without consolidating file storage. Access control remains enforced by each underlying platform. The unified search index adds the auditability that makes cross-platform governance tractable: IT teams gain visibility into what's being searched and which content is being accessed across all three systems from a single interface, without requiring a separate governance tool for each platform. For organizations evaluating federated search as part of a broader [modern intranet](/solutions/modern-intranet) investment, the [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) evaluates MangoApps against competing platforms using the criteria enterprise buyers apply in formal procurement — including integration depth, security posture, and total cost of ownership across the full platform stack. ## What the internal business case should say Organizations building a procurement justification for federated search need to answer three questions their budget stakeholders will ask: what does this cost against what we're already paying, how long does deployment take, and what is the measurable return? The cost comparison belongs against current tool expenditure, not against zero. Organizations running SharePoint, Teams, and Drive separately are already paying implementation, customization, and governance overhead for each platform independently. Per Awesome Technologies' 2025 modeling, SharePoint's first-year total for a 1,000-user enterprise ranges from $130,000 to $426,000 before Teams and Drive governance are accounted for. The federated search layer consolidates the visibility overhead without replacing any of the platforms — the question is whether to add a unified search layer on top of existing infrastructure, not whether to replace it. The deployment timeline is determined by OAuth setup and API permissions, not development work. Administrators connect each integration through the MangoApps settings panel using existing service account credentials. Most organizations see federated results within 24 hours. Governance controls stay in place in the underlying platforms; nothing needs to be rebuilt or reconfigured outside of MangoApps. The return calculation starts with the IDC figure of 2.5 hours per day per employee lost to information search. For a 500-person organization with an average fully-loaded labor cost of $35 per hour, recovering even one hour per day across the workforce represents $4.4 million in annual labor efficiency. The realistic figure depends on current search tool adoption rates — but the direction is not in question, and the headcount multiplier makes even modest per-person improvements significant at scale. Per [Gallup's 2026 research on global workforce engagement](/articles/gallup-2026-state-of-the-global-workplace), information disconnection compounds over time: workers who cannot find what they need become workers who stop looking, and workers who stop looking disengage. Federated search is one practical infrastructure fix with a direct productivity mechanism — not an engagement program, but a search layer that makes the information employees need findable from wherever they work. For organizations running SharePoint, Teams, and Google Drive as separate systems today, federated search within MangoApps is not a migration. Existing files stay where they are, existing permissions stay in force, and the unified search layer connects all three systems from a single interface. The question is not whether to replace the file storage infrastructure — it is whether to give employees a single place to search it, from any device, without a judgment call about which platform to try first. --- # Clinical Staff Engagement Using MangoApps **Author:** MangoApps **Published:** 2023-10-20 **Category:** healthcare Reducing Burnout in Healthcare: The Complete GuideBurnout among healthcare professionals is an alarming and pervasive issue. It can significantly impact the ... # Clinical Staff Engagement Using MangoApps MangoApps is an employee experience platform built for organizations where most workers never sit at a desk. For health systems, that means clinical staff — nurses, technicians, care coordinators, and telehealth providers — can access schedules, training, peer recognition, and HR self-service from a single branded mobile app, without a corporate email address or VPN. This guide explains how MangoApps addresses the specific engagement challenges facing clinical teams, from frontline burnout to distributed care roles. ## Why Clinical Staff Engagement Is Harder Than It Looks Employee engagement in healthcare is structurally different from engagement in office-based industries. According to Emergence Capital, 80% of the global workforce is deskless — and in healthcare, that share is even higher. Clinical staff rotate across shifts, work across multiple facilities, and rarely have reliable access to desktop systems during their workday. The tools most health systems rely on compound the problem. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use one daily. SWOOP Analytics reports that the average employee spends just six minutes per day using intranet tools — a figure that reflects how poorly legacy platforms serve frontline workers. Meanwhile, IDC estimates that employees spend 2.5 hours per day searching for information they cannot easily find. For clinical staff, that friction is not just an inconvenience. It delays access to protocols, shift information, and compliance training at exactly the moments when speed matters most. ## How MangoApps Addresses Clinical Engagement ### 1. A Single App That Replaces Dozens of Disconnected Tools Many health systems have accumulated more than 200 separate digital systems — scheduling platforms, HR portals, learning management systems, communication tools, and document repositories. Clinical staff are expected to navigate all of them, often from a personal smartphone with no IT support. MangoApps consolidates these into one branded mobile app. Frontline healthcare workers can access schedules, request shift swaps, complete HR self-service tasks, and finish required training in a single interface — no corporate email or VPN required. According to MangoApps deployment data from the OU Health case study, healthcare organizations that launch a branded employee app can achieve 87%+ workforce engagement within the first few months. ### 2. Shift Scheduling and Swap Requests Without the Phone Tag For nursing staff and clinical technicians, schedule visibility is a daily pain point. When shift information lives in a separate system that requires a desktop login, staff either call the charge nurse directly or simply miss updates. MangoApps surfaces schedule information, open shift alerts, and swap requests inside the same app employees already use for team messaging and announcements. This matters financially as well as operationally. Replacing a single frontline employee costs between $4,400 and $15,000 (per MangoApps frontline workforce cost analysis), and schedule-related frustration is a documented driver of voluntary turnover among nurses. Reducing that friction is a direct retention lever. ### 3. Peer Recognition Built Into Daily Workflows Hospital recognition programs are most effective when recognition happens in the moment — not in a quarterly all-hands or an annual review. MangoApps embeds peer-to-peer recognition into the same feed where clinical staff receive shift updates and team announcements, so a charge nurse can recognize a colleague's response to a difficult patient situation within seconds of it happening. Health systems that build recognition into daily digital workflows report measurable engagement lift. Deployment data cited in MangoApps case studies shows a 30-point engagement score increase after organizations move from legacy intranets to a modern [employee experience platform](/solutions/employee-engagement). ### 4. Safety Reporting and Compliance Training at the Point of Need Incident reporting and mandatory compliance training are two areas where clinical staff engagement directly affects patient outcomes. When reporting tools are buried in a separate system or training modules require a desktop login, completion rates drop and reporting gaps widen. MangoApps delivers both through the same mobile interface clinical staff already use. Training modules can be assigned by role and surfaced as notifications, so a new ICU nurse sees onboarding content specific to their unit rather than a generic library. This role-specific content delivery is supported by MangoApps' AI integrations — including OpenAI, Google Gemini, Anthropic, and Azure OpenAI trained on company data — which surface relevant protocols, policies, and learning content based on each employee's role and location. Employee engagement training and employee engagement courses delivered this way see significantly higher completion rates than those assigned through standalone LMS platforms, because the content reaches staff where they already are. ### 5. Engaging Remote and Distributed Clinical Roles Telehealth staff, remote case managers, and hybrid clinical coordinators represent a growing segment of the healthcare workforce — and one that is frequently overlooked in engagement strategies designed around physical facilities. These employees face a different version of the same disconnection problem: they are not deskless, but they are organizationally invisible if the engagement platform is built around in-person workflows. MangoApps supports distributed clinical teams with the same branded app experience, including access to employee engagement surveys, employee engagement questionnaires, team channels, and leadership communications. Remote clinical staff can participate in recognition programs, complete training, and submit feedback through the same interface used by their on-site colleagues. ## What Does This Cost Compared to the Alternative? Health system administrators evaluating employee engagement software often benchmark against SharePoint, which many organizations already license. A 1,000-user SharePoint deployment carries a first-year cost of $130,000–$426,000 (per MangoApps competitive analysis), and that figure does not include the customization, governance, and ongoing administration required to make it functional for frontline clinical staff. Purpose-built platforms designed for frontline engagement typically reach 90% frontline adoption within the first six months of deployment (per MangoApps enterprise deployment benchmarks), compared to the 13% daily active usage Social Edge Consulting reports for traditional intranets. The ROI case for clinical staff engagement tools is therefore not just about engagement scores — it is about avoided implementation cost, reduced nurse turnover expense, and the compliance risk that comes from low training completion rates. For a detailed look at how one healthcare-adjacent organization structured this transition, the [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study walks through the deployment approach and outcomes. ## Common Questions About Clinical Staff Engagement Platforms ### Do clinical staff need a corporate email address to use MangoApps? No. MangoApps is specifically designed for frontline workforces where many employees do not have corporate email accounts. Staff can be onboarded using a phone number or employee ID, and the app is accessible on personal devices without VPN configuration. ### How does MangoApps handle HIPAA compliance? MangoApps supports HIPAA-compliant configurations, including data residency controls, audit logging, and role-based access permissions. Health systems should work with their compliance and IT teams to configure the platform according to their specific requirements. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers broader compliance considerations for HR technology deployments in regulated industries. ### Can MangoApps integrate with existing scheduling and EHR systems? MangoApps offers API-based integrations with scheduling platforms, HRIS systems, and other clinical tools. The goal is to surface information from those systems inside the MangoApps interface rather than requiring staff to switch between applications — which is the core of the tool-consolidation value proposition. ## The Bottom Line for Health System Administrators Clinical staff engagement is not a culture initiative that sits alongside operations — it is an operational problem with measurable financial consequences. Nurse turnover costs between $4,400 and $15,000 per departure. Legacy intranets reach fewer than one in seven employees on any given day. And clinical staff are spending 2.5 hours daily searching for information that should be one tap away. MangoApps addresses these problems through a mobile-first, branded employee experience platform that works for frontline staff without email addresses, for remote clinical roles without physical facility access, and for health system administrators who need engagement data, training completion rates, and recognition activity in one place. If your health system is evaluating employee engagement software or looking to replace a legacy intranet, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) provides a framework for assessing platforms against frontline workforce requirements — including the clinical-specific criteria that generic enterprise tools typically miss. --- # Reducing Burnout in Healthcare: The Complete Guide **Author:** Christos Schrader **Published:** 2023-10-20 **Category:** healthcare Burnout among healthcare professionals is an alarming and pervasive issue. It can significantly impact the well-being of staff and the quality of patient care. Burnout is characterized by emotional exhaustion, depersonalization, and a diminished sense of personal accomplishment. In this era of technological advancements, leveraging software solutions is becoming a pivotal strategy in reducing burnout […] # Reducing Burnout in Healthcare: The Complete Guide Healthcare has spent a decade installing technology meant to reduce burnout — and burnout rates have continued to climb. The explanation is not that technology doesn't work. It is that most of the technology deployed was never designed for the 80% of healthcare workers who never sit at a desk. Per Emergence Capital, 80% of the global workforce is deskless. In healthcare, that figure represents nurses, medical assistants, phlebotomists, environmental services staff, and bedside clinicians — the people whose work cannot be done remotely and whose schedules don't include time to log into a browser-based portal. When organizations deploy communication and workflow tools that assume a corporate email address and a desktop computer, they leave that population structurally unsupported. Burnout follows not because workers are insufficiently resilient, but because the systems around them were built for someone else. This guide covers what research and frontline deployments show actually moves the needle — and maps a practical path for healthcare operations leaders ready to treat burnout as an infrastructure problem rather than a morale one. ## Why technology investments often fail to reach frontline staff The healthcare sector is not under-invested in technology. Most health systems run an EHR, a scheduling platform, an intranet, an HR portal, and at least two communication tools. Per Social Edge Consulting, 91% of organizations operate an intranet. But only 13% of employees use it daily, and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools. Those numbers describe what happens when a platform designed for desk workers is distributed to frontline staff. Login friction, desktop-optimized interfaces, and the assumption of corporate email credentials each create small barriers that compound into a pattern of non-use. Per IDC, employees already spend an average of 2.5 hours per day searching for information they cannot easily find. In a clinical environment, that search time has a direct cost: it displaces patient-facing work, increases cognitive load, and generates the low-grade frustration that clinical staff don't always name as burnout until it has already produced an attrition decision. The access gap is the foundational problem. It is also the most tractable one — when it is recognized as the cause rather than attributed to individual staff behavior. ## The access gap: what mobile-first actually means in clinical environments Most enterprise communication platforms offer a mobile app. Mobile wrapper and mobile-first design are not the same thing. The distinction matters in healthcare because frontline clinical staff interact with workplace tools in 90-second bursts — between patient rooms, during a handoff, before a shift starts. A mobile experience built for that interaction pattern looks nothing like a responsive version of a desktop intranet. A mobile-first architecture for healthcare means staff can access schedules, training materials, and HR self-service from a personal device without a corporate email address or VPN. It means push notifications that surface relevant shift information rather than requiring staff to open an app and navigate to find it. It means new hires can complete onboarding on a personal phone before the first day, rather than during an orientation session that pulls experienced staff away from their units. When this access model is deployed correctly, the results are measurable. Healthcare deployments that prioritize mobile-first frontline access have documented workforce engagement rates above 85% within months of launch — a figure that reflects reach into bedside staff, not just adoption by the office-based portion of the workforce. The population that burnout research consistently identifies as highest-risk — bedside nurses and clinical support staff in high-acuity units — is exactly the population that mobile-first architecture reaches first and that desktop-first tools miss entirely. ## Administrative burden as a burnout mechanism The original clinical case for burnout technology focused on EHR optimization: if physicians spent less time on data entry, they would have more time for patients. That framing was correct but too narrow. Administrative overhead is distributed across every clinical role, and the forms it takes — shift swap requests handled by text, PTO approvals sitting in an email queue, task assignments manually coordinated by charge nurses — rarely appear in EHR efficiency studies. Automating routine administrative tasks is a burnout-reduction intervention, not an IT efficiency exercise. The cognitive load of managing a shift trade through five separate text messages — the back-and-forth, the uncertainty about whether the swap was approved, the follow-up with a supervisor — is not large in isolation. Multiplied by every such transaction across a two-week pay period, for every member of a 40-person nursing unit, it accumulates into a measurable load that sits on top of the clinical demands that are inherent to the work. No-code workflow automation applied to shift swaps, PTO requests, and form routing removes those transactions from the cognitive stack. Frontline healthcare workers can access and resolve them from a single mobile app without navigating to a separate HR system, and resolution happens in minutes rather than days. Organizations that implement automated shift-swap workflows consistently see absenteeism reductions because the friction that was driving avoidance behavior has been removed at the source rather than treated as a staffing problem. The target is not paperless workflows for their own sake. The target is a measurable reduction in the administrative cognitive overhead that healthcare staff carry alongside clinical demands. One is variable; the other is the job. ## Information overload as an underrecognized driver Burnout research reliably identifies emotional exhaustion as its primary dimension. In healthcare, one underweighted contributor to that exhaustion is information overload rather than information scarcity. Clinical staff receive too much undifferentiated communication: mass emails from HR, push notifications from scheduling tools, announcements from department leadership, compliance reminders from training platforms — all arriving in parallel with no prioritization signal. The [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) analysis documents how workforce disengagement and communication clarity are directly linked. When every communication channel treats every message as equally urgent, the cognitive cost of filtering becomes the staff member's problem rather than the organization's — and that cost is invisible to the managers designing the communication strategy. An AI-curated communication feed that surfaces relevant information based on role, unit, and shift pattern rather than broadcasting to everyone reduces that filtering work. It does not eliminate communication; it routes it. For a clinical environment where attention is a genuinely constrained resource, that routing is a burnout mitigant, not a feature checkbox. Per IDC's benchmark on information search waste, clinical staff navigating 6 to 8 disconnected tools daily face a fragmentation pattern directly linked to cognitive overload — a structural condition that employee wellness programs do not reach and that platform consolidation does. ## Five indicators worth tracking Healthcare organizations that approach burnout reduction strategically track outcomes, not activities. Installing a new platform is an activity. The following are outcome indicators worth establishing baselines for before deployment. **Shift call-out rate by unit.** Absenteeism is frequently the first visible sign of unaddressed burnout. A 30-day baseline before deployment and a 90-day reading after automating shift swaps and scheduling workflows surfaces whether friction reduction is changing attendance behavior. **Average shift swap resolution time.** In organizations with manual processes, resolution often takes 12 to 24 hours. Automated workflows typically resolve in under 30 minutes. Longer resolution times are a measurable proxy for the administrative cognitive load staff are absorbing. **Completion rate for mobile-accessible training.** If frontline staff can complete compliance and role-specific training from personal devices during natural break patterns, completion rates rise and the frustration of mandatory training blocking shift schedules decreases. Mobile-accessible onboarding can cut new-hire ramp time significantly, easing workload pressure on existing staff who would otherwise fill coverage gaps. **Engagement survey response rate.** Participation is itself a leading indicator: disengaged staff opt out. Response rate trends across sequential quarters are more meaningful than point-in-time scores. **Voluntary turnover rate by role.** Burnout-driven attrition in healthcare carries a documented replacement cost ranging from 1.3x to 2x annual salary per position. This is the lagging indicator that makes the ROI case for engagement infrastructure when turnover shifts are observed. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) includes sector-specific attrition benchmarks that provide useful comparison points for evaluating your starting position. ## Implementation roadmap: five steps for deploying burnout-reduction tools **Step 1: Establish a baseline access audit.** Before deploying any platform, document what share of frontline staff have a work email address and a corporate device. This establishes the actual size of the access gap and determines whether the platform's authentication model will reach the population most at risk. **Step 2: Require a mobile-first demonstration.** Not all platforms that claim mobile capability deliver a frontline-appropriate experience. Require a live demonstration on a personal device from a test account that uses a personal email, not a corporate credential. Ask for adoption data specifically from frontline healthcare deployments rather than aggregate enterprise statistics. The gap between those two numbers is the adoption risk. **Step 3: Start with the highest-friction administrative workflows.** Shift swaps, PTO requests, and onboarding paperwork are the right starting point because their friction is visible to staff and their automation is technically straightforward. Early wins on these workflows build organizational credibility for broader deployment and produce the absenteeism data that justifies continued investment. **Step 4: Connect the platform to existing communication channels.** Staff will not abandon familiar tools immediately. Integration with existing email and team chat ensures information flows consistently without requiring staff to check a new platform before behavioral habits change. Forcing parallel channels accelerates disengagement rather than reducing it. **Step 5: Track the five indicators above at 30, 60, and 90 days and share results with unit leaders.** When charge nurses and nursing directors see call-out rates and swap resolution times improving in their own units, they become platform advocates rather than skeptics. That peer advocacy is the most effective adoption driver in frontline healthcare environments — more effective than top-down mandates or IT-led training sessions. For healthcare operations leaders evaluating frontline communication infrastructure, the [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study documents what a communication overhaul produces in a healthcare-context deployment under similar access constraints. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers adoption benchmarks across frontline industries and a measurement framework for identifying where current tools fall short. Healthcare burnout is a solvable problem in the subset of cases where it originates in access gaps, administrative friction, and information overload — which is where most preventable burnout lives. The organizations demonstrating this are not solving it through wellness programming. They are solving it by building infrastructure that reaches the people doing the work, on the devices they already carry, with the workflow relief they have been asking for. --- # Healthcare Employee Engagement Ideas (And How To Execute On Them) **Author:** Christos Schrader **Published:** 2023-10-20 **Category:** healthcare In the dynamic realm of healthcare, engagement is not just a buzzword—it’s the lifeblood that fuels a high-performing work environment. Forged in the crucible of relentless shifts, demanding benchmarks, and the overarching aim of patient satisfaction, healthcare employee engagement can empower your system to excel. This guide, tailored for seasoned healthcare administrators, will unveil innovative […] In the dynamic realm of healthcare, engagement is not just a buzzword—it’s the lifeblood that fuels a high-performing work environment. Forged in the crucible of relentless shifts, demanding benchmarks, and the overarching aim of patient satisfaction, healthcare employee engagement can empower your system to excel. This guide, tailored for seasoned healthcare administrators, will unveil innovative ideas designed to transform your employee engagement strategies. As experts in your field, you understand the unique intricacies of the healthcare space; let us provide the insights to invigorate your team and elevate your operations. Why is Employee Engagement Crucial in Healthcare? In the dynamic and high-stakes environment of healthcare, where lives are on the line daily, employee engagement ascends beyond traditional notions of job satisfaction or morale. It forms the backbone of an efficient, patient-oriented healthcare system. Engaged employees in healthcare demonstrate greater proficiency in their roles, promote a more collaborative work environment, and directly influence patient satisfaction levels. In fact, fostering engagement is one of the best ways for any health system to reduce burnout. Highly engaged teams are more likely to exhibit strong communication practices and a deep commitment to their roles, which leads to safer patient handling, minimized medical errors, and improved patient outcomes. Moreover, engagement influences staff retention rates. In an industry where skills shortage is a pressing issue, retaining talent is crucial. Engaged employees feel valued and are less likely to move to competitor organizations, reducing turnover costs and ensuring continuity of care. For more on this, read about reducing nurse turnover. Further, engaged healthcare employees pave the way for innovative problem-solving and improved operational efficiency. They are more inclined to put forth ideas and suggestions, driving continuous improvement and adaptation in the fast-paced world of healthcare. In essence, employee engagement in healthcare isn’t merely a “nice-to-have,” but a fundamental pillar to healthcare institutions’ success. As we delve into healthcare employee engagement ideas, it’s important to remember the multifaceted nature of engagement. From technology and software to leadership and culture, numerous factors interact to shape the engagement landscape in the healthcare setting. The equation is simple: when healthcare employees are engaged, patients are happier. A committed workforce not only elevates patient satisfaction but also directly leads to decreased turnover rates. The ripple effect is evident – a positive, vibrant work environment fosters better healthcare outcomes. Innovative Healthcare Employee Engagement Ideas Now that we’ve established the importance of employee engagement in healthcare, let’s explore some ideas that can revolutionize your approach to engaging your workforce. These strategies are designed to drive real results in your organization and do not require any prerequisite technology (although we indicate where and how a healthcare employee app like MangoApps can help). 1. Regular Feedback Systems A culture of constant communication and transparent feedback is instrumental in fostering engagement and a sense of belonging among healthcare employees. Implementing regular feedback systems can be a game-changer for your organization, encouraging employees to voice their opinions, share insights, and feel heard. Consider developing two-way feedback systems, where not only can employees receive constructive assessments from their superiors, but they also have the platform to provide their feedback or suggestions. This can serve as an invaluable tool to identify areas of improvement, refine workflows, and inspire innovative solutions. Expanded Options With Technology Regular team meetings, one-to-one check-ins or anonymous suggestion boxes are some traditional ways to facilitate feedback. Leveraging digital solutions such as a HIPAA-compliant intranet platform can take this a step further by providing a seamless, real-time channel for feedback, fostering open communication across the organization regardless of shift patterns or physical location. Moreover, ensure that the feedback is actionable. Nothing disengages an employee more than feeling their feedback is falling on deaf ears. Showcase the direct impact of their suggestions by implementing viable ideas and acknowledging their contributions. This not only validates their efforts but promotes a sense of ownership among employees, encouraging them to remain invested in their roles and the overall growth of the organization. In essence, a regular feedback system can serve as a key driver of healthcare employee engagement, fostering a culture of openness, ideas, collaboration, and continuous improvement. 2. Creating Space For Cross-departmental Collaboration Cross-departmental collaboration is another cornerstone to building robust healthcare employee engagement. In the complex, interconnected ecosystem of healthcare, fostering an environment that promotes collaborative efforts across various departments can lead to improved communication, increased innovation, and overall enhanced patient care. A culture that encourages cooperation across different disciplines and roles helps break down siloes, facilitating a more holistic and comprehensive view of patient care. It enables different teams to leverage their unique insights and expertise, leading to enriched, patient-centered solutions. For instance, creating interdisciplinary teams for strategic projects or problem-solving tasks can stimulate creativity and innovation. This not only provides a platform for employees to learn and grow, but also drives a sense of camaraderie and mutual respect. The Role of Training Additionally, implementing cross-departmental learning sessions can be a powerful tool for facilitating collaboration. These sessions could be opportunities for different teams to share their challenges, victories, and best practices. This not only aids in the exchange of knowledge but also fosters a sense of community and shared purpose. In the digital age, technology can significantly bolster these collaborative efforts. Platforms like MangoApps offer a suite of tools designed to foster real-time communication, project management, and knowledge sharing across the organization. From real-time messaging and team spaces to collaborative project management tools, these platforms can seamlessly bridge the gap between different departments, fostering a truly interconnected, engaged workforce. In conclusion, fostering interdisciplinary collaboration can significantly enhance healthcare employee engagement, driving a more integrated, efficient, and patient-centric healthcare system. By breaking down siloes and promoting a culture of collaboration, healthcare organizations can foster a more engaged, satisfied workforce, ultimately leading to improved patient outcomes. 3. Mental Health and Wellbeing Programs Mental health and wellbeing programs are among the main ideas in fostering healthcare employee engagement. These initiatives are essential in acknowledging the mental and emotional stresses healthcare workers often face in their line of work—many of the signs of physician burnout, for example, fall within this realm. By prioritizing their mental wellbeing, organizations can demonstrate a commitment to their employees, which in turn fosters a sense of loyalty and engagement. The first step to implementing these programs is to establish a supportive environment that openly talks about mental health. Encourage leaders to be open about the topic, hosting regular discussions, and providing resources that employees can access when they need help. This can greatly reduce the stigma around mental health and make employees feel more comfortable seeking the help they need. Mental Health Benefits Next, consider integrating mental health services within your existing healthcare benefits. This could include providing access to therapists or counselors, offering mental health days, or providing resources for self-care practices. By making these resources readily available, you’re sending a clear message to your employees that their mental health matters. Moreover, consider implementing stress management programs. This could include mindfulness and meditation sessions, yoga classes, or workshops on coping strategies. These programs can equip employees with tools to manage stress and avoid burnout, which is particularly important in the high-pressure environment of healthcare. Another key aspect is to create a work-life balance. Encourage employees to take time off, restrict overtime, and avoid sending work-related communications during off-hours. This allows employees to recharge and come back to work feeling refreshed and motivated. Additionally, consider incorporating activities that promote team bonding and camaraderie. Fun activities, team-building exercises, or group wellness challenges can help create a positive work environment and foster a sense of belonging among employees. Lastly, remember that every member of your workforce is unique. Hence, adopting a one-size-fits-all approach might not yield the desired results. Try to offer a variety of programs and resources to cater to the diverse needs and preferences of your employees. In conclusion, mental health and wellbeing programs are integral to healthcare employee engagement. By taking proactive steps to support the mental and emotional well-being of employees, healthcare organizations can create a healthier, happier, and more engaged workforce, leading to improved patient care and outcomes. 4. Open Communication Forums Open communication forums for ideas and concerns are a vital component of healthcare employee engagement. These platforms provide employees with the opportunity to voice their thoughts, ideas, and concerns, fostering an environment of transparency and respect. When employees feel heard, it significantly boosts morale and contributes to a healthier workplace culture. One of the ways to facilitate open communication is through regular town-hall meetings. These meetings provide a space for employees at all levels to engage in open dialogue about the organization’s direction, challenges, and successes. They also serve as a platform for leadership to address the concerns and queries of the staff, reinforcing transparency. In addition to town-hall meetings, having an open-door policy can significantly contribute to open communication. This policy encourages employees to communicate freely with management without fear of repercussions. It promotes trust and demonstrates to employees that their opinions are valued, which can greatly increase employee engagement. Promote Psychological Safety Similarly, implementing suggestion boxes or online feedback forms can provide employees with a confidential avenue to voice their thoughts and ideas. This can be particularly effective for those who feel uncomfortable expressing their views in public settings. It’s key to ensure that every suggestion is reviewed and feedback is provided to demonstrate that every voice matters. Moreover, digital communication platforms like MangoApps can be leveraged to foster open communication. These platforms allow real-time communication and collaboration, providing employees with a sense of connection and cohesion. They also offer features like forums or channels for specific topics, allowing for focused discussions and idea sharing. In conclusion, open communication forums play a pivotal role in fostering healthcare employee engagement. By creating a culture of transparency and respect, organizations can improve employee satisfaction, efficiency, and overall organizational performance. 5. Mentorship Programs Mentorship programs are a powerful tool in promoting healthcare employee engagement. These programs pair less experienced employees with more seasoned colleagues, fostering an environment of learning, professional growth, and mutual respect. Mentors provide guidance, share experiences, and offer constructive feedback, helping mentees navigate the complexities of the healthcare industry. The first step in establishing a successful mentorship program is to identify potential mentors. Look for employees who demonstrate leadership qualities, have a wealth of experience in their respective fields, and possess a willingness to guide others. Equally important is ensuring that mentors understand their role and responsibilities – they’re not just supervisors, but coaches and facilitators. Similarly, it’s crucial to match mentors with the right mentees. This should not be random; instead, consider factors like career goals, skills needs, and personality traits. A good match can lead to more productive relationships and better outcomes for the program. Setting Clear Expectations Once pairs have been established, it’s essential to set clear expectations for the mentor-mentee relationship. This might include establishing regular meeting times, setting goals for the program, and laying out what each party should expect from the other. Providing a clear structure can help ensure that both parties benefit from the mentorship. It’s also important to provide ongoing support for the mentorship program. This might include regular check-ins with mentors and mentees, providing resources for mentors, or offering training sessions to help mentors enhance their mentoring skills. Fostering a supportive environment increases the chances of a successful and impactful mentorship experience. To make your mentorship program even more engaging, consider implementing a recognition program. Recognizing the hard work and commitment of mentors and mentees can motivate participants and make them feel appreciated. This could be as simple as a shout-out in a company meeting, a certificate of recognition, or a small token of appreciation. Moreover, it’s crucial to evaluate the effectiveness of your mentorship program regularly. This can be done through surveys, feedback sessions, and tracking the progress of mentees. Collecting and analyzing this data can provide valuable insights into what’s working, what’s not, and where improvements can be made. In conclusion, mentorship programs are a powerful strategy for fostering healthcare employee engagement. They create an environment of learning and growth, improve job satisfaction, and lead to a more skilled and competent healthcare workforce. By investing in these programs, healthcare organizations can enhance employee engagement, improve patient care, and boost overall organizational performance. 6. Recognition and Reward Systems Recognition and reward systems are another essential aspect of healthcare employee engagement. Recognizing employees for their hard work, dedication, and achievements can significantly boost morale, increase job satisfaction, and foster a positive work culture. The first step in implementing an effective recognition and reward system is to identify what behaviors, values, or accomplishments should be rewarded. These could range from surpassing performance targets, displaying exceptional patient care, showing teamwork, or demonstrating a commitment to continuous learning. By rewarding these behaviors, you reinforce the values you want to see throughout your organization. Next, it’s important to diversify the types of recognition and rewards. Not all rewards have to be monetary. Recognition can come in many forms, from a simple thank you note to a spot in the company newsletter or a shout-out in a team meeting. Similarly, rewards could be as simple as an extra day off, a gift card, or a flexible work schedule. The key is to make the reward meaningful to the individual. Real-Time Recognition Moreover, instant recognition can be highly effective. Rather than waiting for a formal review, acknowledging an employee’s achievement in the moment or soon after can make the recognition more impactful. Real-time recognition platforms, such as MangoApps, can be particularly beneficial for this, providing a visible, immediate, and memorable way to celebrate achievements. In addition to individual recognition, consider implementing team or department recognition. Celebrating team successes can foster a sense of unity and collaboration, promoting a positive work culture. Lastly, it’s crucial to ensure that recognition and rewards are fairly distributed. All employees, regardless of their role or level, should have the opportunity to be recognized for their contributions. This promotes a sense of fairness and inclusivity, which can greatly enhance employee engagement. In conclusion, an effective hospital recognition program can work wonders for healthcare employee engagement. By acknowledging and appreciating the hard work and dedication of your employees, you can foster a positive, engaging, and productive work environment. Acknowledging milestones and standout employees is critical. With technology, not only can we streamline this recognition, but we can also empower peers to commend each other. When recognition is linked with tangible rewards, motivation skyrockets. Enabling clinical staff at Marion Health Learn how Marion Health improved communication and collaboration among staff and clinicians with a secure employee app. READ case study 7. Feedback Loops Feedback loops are vital to ensuring ongoing healthcare employee engagement. They provide employees with a platform to voice their thoughts, opinions, and suggestions, fostering a sense of involvement and ownership over their roles. Moreover, feedback loops allow for continuous improvement, as employees are often the best source of ideas for enhancing workflow, patient care, and overall organizational performance. The first step in creating an effective feedback loop is to establish a culture of open communication. Encourage employees to speak up and share their thoughts without fear of retaliation. This can be done by promoting a non-judgmental environment where all feedback, whether positive or negative, is appreciated and valued. Next, provide various channels for feedback. This could include regular one-on-one meetings with supervisors, anonymous suggestion boxes, digital platforms, or town hall meetings. Providing multiple avenues ensures that all employees, regardless of their comfort level, have an opportunity to voice their thoughts. Acknowledging Feedback Is Crucial Once feedback is collected, it’s crucial to acknowledge it. Employees need to know that their feedback has been heard and is being considered. This could be done through a personal response, a general announcement, or a demonstration of action taken as a result of the feedback. Acting upon the feedback is, however, the most critical aspect of a feedback loop. While it may not be possible to implement all suggestions, showing that some changes are made based on employee input can significantly boost engagement. If a suggestion cannot be implemented, explaining the reasons can maintain trust and transparency. Feedback should also be a two-way street. Managers should provide employees with regular feedback about their performance, offering praise for achievements and constructive advice for areas of improvement. This helps employees understand their strengths, areas for growth, and the impact of their work, contributing to their engagement and job satisfaction. Finally, the effectiveness of the feedback loop should be regularly reviewed. This could involve surveying employees about their satisfaction with the feedback process or analyzing whether implemented changes have led to improvements. In conclusion, feedback loops are an integral part of healthcare employee engagement. They involve employees in decision-making, promote continuous improvement, and demonstrate that the organization values its employees’ input. By prioritizing feedback, healthcare organizations can improve their operations, boost employee morale, and ultimately, deliver better patient care. Employing user-friendly platforms such as MangoApps can greatly simplify the feedback process. These platforms allow for easy collection, analysis, and actioning of employee feedback, enhancing the effectiveness of feedback loops. Implementing These Ideas in Your Health System To adopt these healthcare employee engagement ideas in your health system, it is necessary to take a holistic approach, focusing on both the individual and collective needs of your team. Here’s a step-by-step guide on how to develop your own engagement program: 1. Understand your current state Before you can plan improvements, you need to understand the current state of employee engagement in your health system. Use tools like employee surveys, focus groups, and one-on-one interviews to gather insights about what’s working well and where improvements can be made. You’ll want to probe into areas such as communication, recognition, feedback, leadership, job satisfaction, and work-life balance. Using tools like MangoApps can help streamline this process, making it easier to collect and analyze employee feedback. 2. Develop a clear vision Developing a clear vision is a critical step in implementing effective healthcare employee engagement strategies. Begin by defining what employee engagement looks like in your organization and the outcomes you hope to achieve. Your vision should be inspiring, achievable, and aligned with your organization’s values and goals. It may include elements such as open communication, regular feedback, recognition of employees’ efforts, opportunities for professional development, and a positive work environment. To ensure the vision is holistic and encompasses the multifaceted nature of healthcare, involve leadership from multiple functions. Leaders from operations, HR, nursing, medicine, and support services should all have a seat at the table. Harnessing their unique perspectives will help you create a comprehensive vision that caters to the diverse needs of your workforce. Remember, the vision should be communicated clearly and consistently to all employees. This not only ensures everyone is on the same page but also reinforces the importance of employee engagement in achieving organizational success. Using an integrated platform like MangoApps can aid in this communication process, providing an easy-to-use channel for conveying your vision and other important updates. Once the vision is established, it should serve as the north star guiding all your employee engagement initiatives. Always refer back to this vision when planning activities or making decisions to ensure alignment and consistency. This will help to create a cohesive and engaging experience for your employees, reducing burnout and improving satisfaction and ultimately, patient care. 3. Create an action plan With your vision in place, you can start developing a detailed action plan. This plan should outline the steps you’ll take, the resources you’ll need, and the timeline for implementation. It should also specify how you’ll measure success. Remember to incorporate various healthcare employee engagement ideas into your plan, ensuring it addresses the diverse needs and preferences of your team. 4. Communicate and implement the plan Once your action plan is ready, it’s time to communicate it to your team. Remember, communication should be a two-way street. Invite feedback and be ready to make adjustments based on the responses you receive. Then, start implementing your plan. Tools like MangoApps can support you in this phase, helping you manage tasks, track progress, and facilitate communication. 5. Evaluate and adjust Engagement is a continuous process that requires regular evaluation and adjustment. Schedule times to review your progress, celebrate wins, and brainstorm solutions to challenges. Use employee feedback, engagement metrics, and other relevant data to assess the effectiveness of your plan. Be ready to make necessary adjustments and continually refine your approach. This constant cycle of feedback and improvement can keep your engagement efforts fresh and effective, helping you achieve your goals. Remember, every health system is unique, so it’s essential to customize your engagement strategy to best fit your organization’s specific needs and circumstances. Both macro and micro-level initiatives can have a significant impact on engagement levels, so be sure to address both broad organizational changes as well as individual employee needs. Lastly, remember that building engagement is a long-term process that requires consistent effort, commitment, and patience. Conclusion The heart of any healthcare system is its employees. By championing their well-being, promoting open communication, and acknowledging their achievements, we pave the way for improved healthcare outcomes. The future of healthcare is intertwined with engaged employees. For more on this topic, read about reducing nurse turnover, physician engagement strategies, or digital transformation in healthcare. --- # Benefits of Digital Transformation in Healthcare Employee Experience **Author:** Christos Schrader **Published:** 2023-10-20 **Category:** healthcare In today’s fast-paced and evolving world, digital transformation is reshaping every industry, and healthcare is no exception. By leveraging technology, healthcare organizations can radically enhance the employee experience, leading to improved efficiency, better patient care, and overall institutional growth. The benefits of digital transformation in healthcare reach far beyond just simplifying administrative tasks. In fact, […] # Digital Transformation in Healthcare Employee Experience The benefits of digital transformation in healthcare employee experience are concrete: clinical staff spend less time searching for information and more time on patient care, new hires reach full productivity faster, frontline workers stay connected without needing a desktop or VPN, and organizations that consolidate their tool landscape see measurable gains in engagement and retention. Healthcare organizations that make this shift report outcomes that justify the investment. Those still operating on fragmented systems face compounding costs in staff time, turnover, and care continuity. This article covers what those benefits look like in practice, what implementation requires, how to measure whether it's working, where healthcare organizations most commonly go wrong, and what to prioritize when building a business case for transformation. ## Why the current employee experience in healthcare is broken The structural problem is familiar to anyone managing a clinical workforce: most healthcare employees are never at a desk. According to Emergence Capital, 80% of the global workforce is deskless — and in healthcare, that proportion runs higher among nursing staff, clinical aides, and frontline support workers who move between patient rooms and units throughout every shift. The tools designed to reach these employees were not built for how they actually work. According to Social Edge Consulting, 91% of organizations operate an intranet — but nearly a third of employees never log in, and only 13% use one daily. A platform that requires desktop credentials and a corporate VPN login to access effectively writes off the majority of a clinical workforce before deployment begins. The information search burden compounds this. IDC research places the average at 2.5 hours per day that employees spend searching for information — across a large clinical workforce, that represents an enormous volume of staff time diverted from patient-facing work toward locating schedules, policies, and HR resources. When those resources are split across six to eight disconnected systems, none of them optimized for mobile access, that figure does not improve. SWOOP Analytics found that the average employee spends only six minutes per day using intranet tools. The gap between that number and what engaged daily use actually looks like is largely explained by friction: repeated logins, mobile-inaccessible interfaces, and platforms built for desk-based work patterns that simply don't fit clinical reality. ## The direct benefits for clinical staff ### Mobile-first access that reaches the frontline The most immediate benefit of a modern employee experience platform is access: staff who previously could not reach organizational systems from a clinical floor can now open a shift assignment, submit a time-off request, complete a required training module, and message a supervisor from a single app — without a desktop or a VPN. Healthcare organizations using a unified [employee app](/solutions/employee-app) that consolidates communication, task management, and HR self-service have reached 87% workforce engagement within a few months of launch, according to the MangoApps OU Health case study. That adoption figure reflects a platform built for frontline access rather than one adapted for it after the fact. The distinction matters: an app that removes authentication friction gets used; one that preserves it gets bypassed. ### Faster onboarding in a high-turnover environment Healthcare faces higher voluntary turnover than most industries, which means onboarding is a recurring operational cost rather than a one-time investment. Digitizing onboarding with mobile-accessible training — where new hires complete modules, acknowledge policies, and receive certifications through a single platform — can reduce new hire time-to-productivity by up to 50% compared to manual, paper-based processes, according to Beekeeper's product research on frontline workforce onboarding. For health systems running on thin margins with ongoing staffing challenges, that compression has direct labor cost implications. Consistent digital onboarding also reduces compliance exposure: when completion is tracked automatically through a single platform, the audit trail is reliable and the risk of missed compliance steps is lower than with manual tracking across disconnected systems. For a deeper look at how organizations are approaching this, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ### AI-assisted scheduling and workforce management Scheduling is one of the highest-friction touchpoints in clinical employee experience. Manual scheduling requires managers to track availability, certifications, union rules, and seniority across a rotating workforce — a process that generates errors, creates perceived unfairness, and consumes management time that would be better spent on the floor. Modern [workforce management](/solutions/workforce-management) platforms automate the underlying logic: the system tracks who is available, who holds the required certifications for a given unit, and how proposed schedule changes affect overtime and coverage thresholds. Clinical staff receive shift notifications, can swap shifts through the same app they use for communication and HR tasks, and can update their availability in real time rather than through a phone call or a separate scheduling portal. The result is a scheduling process that feels responsive rather than bureaucratic — a meaningful retention factor in a competitive labor market. ### Reducing tool-switching burden on clinical teams Healthcare employees navigating multiple disconnected systems daily face compounding communication fragmentation: a separate login for HR, a different system for scheduling, a third platform for compliance training, and a phone call or paper form for everything else. Each additional system adds cognitive load and authentication friction that clinical staff carry into patient interactions. A unified platform eliminates these access points. When communication, task management, learning, HR self-service, and organizational news consolidate into one mobile app, the daily tool-switching burden disappears. The efficiency gain is straightforward: staff spend less time on authentication and navigation, and more time on care. ## What implementation actually looks like A digital transformation in healthcare employee experience does not happen in a single deployment. The organizations that achieve sustained adoption follow a recognizable pattern: establish the mobile app as the primary access point first, integrate single sign-on early to remove authentication friction, and use push notifications and an action center to build daily habitual engagement. Advanced capabilities — analytics, leadership ghostwriting tools, recognition programs — come after the core access habit is established. HIPAA compliance is an architectural requirement, not an implementation step. The right question for healthcare operators is not whether a platform can be configured to handle protected health information, but whether HIPAA compliance is designed into the architecture. SAML 2.0 authentication, audit-ready record-keeping, and group management built in by default are what purpose-built compliance looks like. General-purpose platforms configured for healthcare compliance require ongoing maintenance every time the platform updates — a configuration layer is not the same as architectural support. The American College of Radiology's deployment illustrates how a distributed healthcare organization can consolidate communication across a dispersed workforce using this approach. Their [case study](/resources/case-study-american-college-radiology) covers the access model, the platform consolidation process, and the engagement outcomes. ## How to measure whether transformation is working The metrics that indicate a successful healthcare digital transformation are behavioral, not technical. **Adoption rate within the first 90 days.** A platform that reaches 70% of the clinical workforce within three months is building toward sustainable engagement. One that stalls at 30% has an access problem or a change management problem — neither of which additional training modules will resolve. **Daily active usage, not monthly.** Monthly active user counts mask low engagement. The metric that matters is how many staff open the platform at least once per shift. A platform that clinical staff consult during their shift is genuinely embedded in workflow; one they check occasionally from home is not. **Time-to-information for common queries.** If nurses are still asking managers for the overtime policy or calling HR for a PTO balance, the platform has not replaced the previous behavior. Tracking where staff turn for common information questions reveals whether the digital tools are being used or bypassed. **New hire onboarding completion rates.** A consistent digital onboarding process should produce consistent completion rates. If a new cohort is completing required modules within days rather than weeks, with completion rates above 90%, the platform is functioning as intended. **Retention correlation over six-month periods.** The retention impact of improved employee experience takes time to appear in turnover data. Comparing voluntary turnover in the six months before and after a platform deployment, controlling for external labor market factors, gives the clearest picture of whether the investment is compounding. ## Where healthcare organizations most commonly go wrong The most common failure mode is treating digital transformation as an IT deployment rather than a workforce behavior change initiative. Rolling out a new platform without clinical staff involvement in configuration, without communicating clearly why the change is happening, and without a concrete plan for reaching deskless staff on day one produces a tool that no one uses — regardless of its technical quality. A second failure mode is underestimating compliance dependency. Healthcare organizations that select a general-purpose platform and attempt to configure HIPAA compliance after the fact often discover that the configuration requires maintenance every time the platform updates. Compliance is not a one-time setup — it requires architectural support. The third is fragmented rollout that preserves tool sprawl. A digital transformation that adds a new application without eliminating any of the old systems does not reduce friction — it adds another login. The value of consolidation comes from removing access points, not adding them. Organizations that phase out the displaced systems simultaneously with launching the new platform see adoption rates significantly higher than those that leave old systems in place as alternatives. ## What healthcare organizations that get this right have in common Healthcare organizations that successfully transform the clinical employee experience make three architectural choices before the first staff member logs in: they choose platforms built for frontline access, not adapted for it; they treat HIPAA compliance as a platform requirement rather than a configuration task; and they define consolidation — not feature breadth — as the primary objective. The employee experience improvements that follow — faster onboarding, higher engagement among deskless staff, reduced daily tool-switching friction, and better retention — are not the result of any single feature. They are the result of a workforce that consistently has access to what it needs, where it needs it, without navigating a fragmented system landscape to get there. That access, built on the right foundation, compounds over time into the kind of workforce stability that healthcare organizations cannot achieve through individual point solutions. --- # Best Practice Interdisciplinary Collaboration Strategies for Large Health Systems **Author:** Christos Schrader **Published:** 2023-10-20 **Category:** healthcare Interdisciplinary collaboration in large health systems is a critical driver of optimized patient outcomes, innovation, and overall organizational success. This approach brings together diverse medical professionals, combining a breadth of skills, perspectives, and expertise to solve complex health problems. These best practice interdisciplinary collaboration strategies will help you foster key relationships throughout your organization and […] # Best Practice Interdisciplinary Collaboration Strategies for Large Health Systems Interdisciplinary collaboration in large health systems directly shapes patient outcomes, staff retention, and operational efficiency. When clinical, administrative, and frontline teams work from shared information and aligned goals, care coordination improves and costly errors decrease. This article lays out the specific strategies, tools, and structural conditions that make interdisciplinary collaboration work in practice — including the barriers most health systems face and how to address them. **The short answer:** Effective interdisciplinary collaboration requires mutual respect, clear role definitions, shared goals, consistent communication channels, and knowledge management tools that every staff member — including deskless frontline workers — can actually access. Without that last piece, even well-designed collaboration programs leave the majority of the workforce behind. --- ## Why Traditional Healthcare Silos Still Undermine Collaboration Healthcare has historically organized itself around specialization. Physicians, nurses, pharmacists, social workers, and administrators each operate within defined domains, and that depth of expertise is genuinely necessary. The problem is structural: when those domains don't share information systems, communication channels, or decision-making processes, patients fall through the gaps. Fragmented communication tools force clinical and administrative staff to navigate 6–8 disconnected systems daily, directly undermining care coordination (per MangoApps product challenge framing). That tool sprawl isn't just inefficient — it creates real patient safety risk. Fragmented care, patient safety incidents, and decreased patient satisfaction are documented consequences of siloed operations in health systems. The scale of this problem is significant. One large health organization, TeamHealth, consolidated over 200 separate systems into a single platform — a figure that illustrates how deeply tool sprawl can embed itself in large health organizations before anyone addresses it. Meanwhile, 47% of workers struggle to find necessary information at least half the time (Gartner, 2023). In a clinical environment, that search friction isn't just a productivity issue — it delays care decisions. --- ## The Pillars of Successful Interdisciplinary Collaboration For collaboration to hold up under the pressure of a large health system, it needs to be built on more than goodwill. The following principles are the structural foundation. ### Mutual Respect Across Roles Interdisciplinary teams function when every member — from the attending physician to the unit clerk to the environmental services worker — understands that their role contributes to patient outcomes. This isn't a soft cultural aspiration; it has direct operational consequences. Teams where members feel undervalued communicate less, escalate problems more slowly, and experience higher turnover. Replacing a single frontline employee costs between $4,400 and $15,000 on average, which means the retention stakes of poor interdisciplinary communication are measurable in dollars, not just morale. Building a culture of mutual respect is also a retention strategy. ### Effective Communication Across Every Shift Communication in a health system isn't a single channel — it's a network of handoffs, updates, escalations, and documentation that spans every shift, every department, and every care setting. The challenge is that most communication infrastructure was designed for desk-based, email-enabled employees. Frontline healthcare workers make up over 80% of the global healthcare workforce and are systematically excluded from intranet and collaboration tools that require a desk or corporate email (per MangoApps / industry deskless workforce framing). A charge nurse on a night shift, a home health aide, or a patient transport worker cannot participate in interdisciplinary collaboration if the tools require VPN access or a corporate email address. This is a structural gap, not a training problem. According to a Banner Health employee poll, 61% of employees wanted intranet access outside the work VPN — a signal that the workforce is already trying to bridge this gap on its own. ### Clear Roles and Responsibilities Role ambiguity in interdisciplinary teams produces duplicated effort, missed tasks, and interpersonal friction. Every team member should understand their own responsibilities and have enough visibility into their colleagues' roles to hand off effectively. This is especially important during transitions of care, where unclear ownership is a common source of adverse events. Standard operating procedures (SOP operations) that are documented, accessible, and current are the practical mechanism for maintaining role clarity at scale. The problem is that in many health systems, SOPs live in locations that are hard to find. According to the State of the Digital Workplace & Modern Intranet, 2024, only 22% of company intranets feature personalized content — meaning most staff are searching through undifferentiated repositories to find the protocols relevant to their role. Knowledge management tools that surface the right SOP to the right person at the right time are not a luxury — they are a prerequisite for consistent role clarity across a large, distributed workforce. ### Shared Goals Aligned to Patient Outcomes Interdisciplinary teams need a common purpose that transcends departmental metrics. When a cardiology team, a pharmacy team, and a care coordination team each optimize for their own KPIs without a shared patient-outcome goal, the patient experiences the gaps between those optimizations. Shared goals work best when they are visible, regularly reviewed, and connected to the daily work of every team member — not just surfaced in quarterly reports. ### Continual Learning and Knowledge Management Healthcare is not static. New protocols, updated guidelines, regulatory changes, and lessons from adverse events all require ongoing knowledge transfer across disciplines. This is where knowledge management becomes a clinical issue, not just an IT issue. A knowledge management system that centralizes policies, training materials, clinical protocols, and peer expertise allows healthcare professionals to learn from each other across departments and shifts. The alternative — relying on informal networks, email chains, or printed binders — produces the kind of information staleness that erodes care quality. In the Banner Health employee poll, 63% of employees said intranet content was not current and relevant, which is a direct indicator of knowledge management failure. For large health systems, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) offers a useful framework for connecting communication infrastructure to knowledge management outcomes. --- ## Five Strategies for Implementing Interdisciplinary Collaboration ### 1. Establish Regular Cross-Disciplinary Team Meetings Scheduled, structured meetings between disciplines — not just within them — create the recurring touchpoints where care plans are aligned, problems are surfaced early, and relationships are built. These meetings don't need to be long; they need to be consistent and inclusive of all relevant roles, including frontline staff who are often excluded from planning conversations. For shift-based environments, asynchronous meeting formats (recorded updates, shared notes, structured check-ins via a mobile platform) can extend participation to staff who cannot attend in real time. ### 2. Invest in Interprofessional Training Interprofessional training programs give healthcare professionals structured exposure to each other's roles, decision-making frameworks, and communication norms. This reduces the stereotyping and hierarchy-driven communication barriers that slow down interdisciplinary teams. Training is most effective when it is ongoing rather than one-time, and when it includes simulation of real cross-disciplinary scenarios — not just classroom instruction about collaboration principles. ### 3. Deploy Knowledge Management Tools That Reach Every Worker The choice of knowledge management tools is one of the highest-leverage decisions a health system can make for interdisciplinary collaboration. A tool for knowledge management that requires a desktop login, a corporate email, or VPN access will exclude the majority of clinical staff before they ever open it. Effective tools of knowledge management for health systems share several characteristics: mobile-first access, role-based content personalization, universal search across policies and protocols, and the ability to push updates to specific teams or roles. AI-assisted information surfacing — where the system proactively surfaces relevant protocols, colleague expertise, or updated guidelines based on a user's role and context — directly reduces the care coordination lag that comes from manual information searching. Healthcare organizations using a unified mobile platform have achieved 87%+ workforce engagement within months of launch, without requiring staff to have corporate email or VPN access (per MangoApps / OU Health case study). That adoption rate matters because a knowledge management system only works if the people who need it actually use it. For health systems evaluating their options, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an independent assessment of intranet and employee experience platforms relevant to this decision. ### 4. Recognize and Celebrate Cross-Team Contributions Recognition programs that span departmental lines reinforce the behaviors that make interdisciplinary collaboration work. When a nurse's contribution to a successful care transition is acknowledged by a physician, or when an administrative team's process improvement is recognized by clinical leadership, it signals that the organization values collaboration as a practice — not just as a policy. Recognition doesn't require elaborate programs. Consistent, specific, cross-disciplinary acknowledgment — delivered through channels that all staff can see — is more effective than annual awards. ### 5. Build Feedback Loops That Include Frontline Voices Feedback systems in health systems often flow in one direction: from leadership to staff. Effective interdisciplinary collaboration requires the reverse as well — frontline workers identifying care coordination gaps, reporting near-misses, and suggesting process improvements. This requires both a cultural commitment to psychological safety and a technical mechanism for frontline staff to submit feedback without needing a desk or a manager's approval. [Employee communications](/solutions/employee-communications) platforms that include two-way messaging, anonymous reporting, and structured feedback channels make this possible at scale. --- ## Common Challenges and How to Address Them ### Communication Barriers Language differences, hierarchical norms, and the sheer volume of information in a clinical environment all create communication barriers. The most effective mitigation is structural: standardized communication formats (SBAR for clinical handoffs, for example), shared platforms that reduce channel fragmentation, and explicit norms about who communicates what to whom and when. ### Resistance to Change Resistance to new collaboration practices is often a symptom of past failed implementations. Staff who have seen collaboration initiatives come and go without lasting impact are rational to be skeptical of the next one. Addressing resistance requires demonstrating early, concrete wins — not just communicating the vision — and involving frontline staff in the design of new processes rather than presenting them with finished solutions. ### Lack of Role Clarity When roles are unclear, staff default to their narrowest interpretation of their responsibilities. Addressing this requires documented SOP operations that are current, searchable, and accessible to every role — not just those with desk access. Manual operations that rely on informal knowledge transfer are a particular risk in high-turnover environments, where institutional knowledge walks out the door with departing staff. ### Differing Goals and Expectations Departmental metrics that conflict with system-level patient outcome goals are a structural problem, not a people problem. Resolving it requires leadership alignment on shared metrics and transparency about how departmental performance connects to those metrics. ### Time Constraints and Burnout Physician and nurse burnout is directly connected to collaboration barriers. When staff spend significant time searching for information, navigating disconnected systems, or repeating communication that should have been captured and shared, that friction accumulates into exhaustion. Reducing manual operations through better knowledge and knowledge management infrastructure is a burnout mitigation strategy, not just an efficiency play. --- ## What Interdisciplinary Collaboration Looks Like When It Works The health systems that have moved from advisory frameworks to measurable outcomes share a few common characteristics: they extended collaboration tools to every worker regardless of whether they have a desk or corporate email, they invested in knowledge management systems that surface current and relevant information without requiring manual search, and they measured adoption and engagement rather than just deployment. For health systems evaluating where to start, the [/industries/healthcare](/industries/healthcare) page outlines how these principles apply to specific care settings and workforce configurations. --- ## Frequently Asked Questions ### What is the difference between multidisciplinary and interdisciplinary collaboration in healthcare? Multidisciplinary collaboration means professionals from different disciplines each contribute their expertise independently, then combine their outputs. Interdisciplinary collaboration means those professionals work together in an integrated way, with shared decision-making and mutual adjustment of their approaches based on each other's input. Interdisciplinary collaboration produces more coordinated care but requires more investment in communication infrastructure and role clarity. ### How do you measure whether interdisciplinary collaboration is actually working? Useful metrics include: care coordination error rates, time-to-decision on complex cases, staff satisfaction scores across disciplines, platform adoption rates for shared communication and knowledge management tools, and frontline staff participation in feedback and improvement processes. Adoption rates above 85% on a shared platform are a leading indicator that the infrastructure for collaboration is in place; outcome metrics confirm whether that infrastructure is being used effectively. ### How do knowledge management tools specifically support interdisciplinary collaboration? Knowledge management tools reduce the information asymmetry that causes collaboration breakdowns. When a nurse can instantly find the current protocol for a medication interaction, when a social worker can identify which physician to contact for a specific patient situation, or when an administrator can access the updated compliance procedure without emailing three people — those are knowledge management outcomes that directly enable interdisciplinary collaboration. The key requirement is that the tool must be accessible to every role, not just desk-based staff. --- ## Next Steps for Health System Leaders Interdisciplinary collaboration doesn't improve through aspiration alone. The health systems making measurable progress share a common approach: they identify the specific structural gaps — tool fragmentation, frontline exclusion, stale knowledge management systems — and address them with infrastructure changes, not just culture campaigns. If your health system is evaluating where to start, the most impactful first step is usually an honest audit of who currently has access to your collaboration and knowledge management tools, and who doesn't. If the answer excludes shift workers, deskless staff, or anyone without a corporate email, that gap is the highest-priority item to address. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers workforce engagement and retention trends relevant to health system HR leaders planning collaboration initiatives. For a broader view of how employee apps support healthcare workforce operations, the [employee app solutions page](/solutions/employee-app) outlines the specific capabilities that health systems have used to extend collaboration to every worker. --- # Signs of Physician Burnout and How To Measure Them **Author:** Christos Schrader **Published:** 2023-10-20 **Category:** healthcare Physician burnout is a rising concern within the medical field, characterized by signs such as a state of physical, emotional, and mental exhaustion. It’s not merely an issue of tiredness; it’s a profound sense of disillusionment, detachment, and desolation that affects the personal and professional life of a healthcare professional. This phenomenon can be triggered […] # Signs of Physician Burnout and How To Measure Them Most physician burnout programs start measuring too late, with the wrong instrument, looking at the wrong signals. A physician who scores high on emotional exhaustion in an annual survey has been burning out for months. The signs that matter — detachment from patients, declining cognitive precision, withdrawal from team communication — surface in daily workflow long before any survey captures them. The clinical framework for physician burnout comes from the Maslach Burnout Inventory (MBI), which defines the condition across three dimensions: emotional exhaustion, depersonalization, and reduced personal accomplishment. Each is measurable, and each has documented behavioral precursors that health systems can track without waiting for a formal assessment cycle. Understanding what to look for — and building infrastructure to surface it continuously — separates a burnout measurement program from a burnout awareness program. This article covers the clinical signs across all three dimensions, the measurement tools that have demonstrated validity in healthcare settings, and the organizational conditions that drive each indicator. Measuring burnout without addressing its causes is documentation, not intervention. ## The clinical triad: what each dimension reveals Emotional exhaustion is the most commonly recognized indicator and the first to appear. Physicians experiencing it describe a persistent sense of depletion — not fatigue that sleep resolves, but a chronic deficit that accumulates across shifts. They may arrive at work already drained, find previously routine patient interactions effortful, and exhibit reduced tolerance for the ambiguity that clinical work demands. Depersonalization — the second dimension — is the MBI's most counterintuitive component. It does not mean a physician becomes indifferent to patients in an obvious way. It manifests as emotional distancing: shorter consultations, formulaic responses, reduced eye contact, a clinical efficiency that reads as coldness. Colleagues and patients often notice it before the physician does. Reduced personal accomplishment tends to appear later and is the hardest to self-report. A physician who once found meaning in complex cases begins to feel that their effort is disconnected from outcomes. This dimension is most strongly correlated with intent to leave the profession — it is where disengagement becomes permanent. All three are downstream of specific organizational conditions. Identifying them early means tracking what produces them, not only the symptoms themselves. ## Beyond the triad: what daily behavior signals Three additional indicators are worth tracking because they appear before formal burnout scores elevate and are visible to peers without a survey instrument. Cognitive challenges are among the earliest behavioral signals. A physician navigating chronic overload may exhibit slowed decision-making on cases that were previously quick, more frequent documentation errors, or difficulty holding complex case details across a shift. These patterns appear in peer observation, task completion rates, and documentation audit trails before they surface in self-report. Physical symptoms — chronic fatigue, sleep disruption, recurrent illness — follow prolonged periods of physiological stress. They are rarely disclosed proactively because healthcare culture treats illness disclosure as a professional risk. Regular private health check-ins and anonymous symptom tracking can surface these signals in aggregate across a department before they become individual crises. Behavioral indicators are often the most visible to colleagues: increased irritability in team settings, withdrawal from collaborative conversations, reduced participation in department meetings. Attendance patterns — late arrivals, increased shift swaps, unexplained absences — show up in scheduling data before any individual report surfaces. The challenge with all three is that healthcare professionals are trained to manage through discomfort. Early signals get minimized by the people experiencing them and go unnoticed by the systems around them. ## How administrative fragmentation drives every indicator The organizational conditions most consistently linked to physician burnout are not the acuity of clinical work — they are the administrative and informational overhead surrounding it. Per Emergence Capital, 80% of the global workforce is deskless. In healthcare, this means physicians are documenting on shared workstations, receiving updates across paging systems and EHRs and informal texts, and approving orders between patient encounters rather than in dedicated administrative time. Per IDC, employees in information-intensive roles spend 2.5 hours per day searching for information — time that in clinical settings maps directly onto the documentation burden physicians consistently identify as their primary source of exhaustion. A physician navigating 6–8 disconnected tools during a single shift is not experiencing stress from the work of medicine. They are experiencing stress from the organizational architecture around it. The distinction matters because emotional exhaustion driven by tool fragmentation and communication overload is structurally addressable in a way that clinical acuity is not. Organizations using a unified communication and workflow platform have reported materially higher physician engagement rates within months of deployment — not because the technology is inherently engaging, but because consolidating communication channels and reducing redundant documentation steps removes the friction that generates daily depletion. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents how health systems are restructuring communication infrastructure specifically to reduce this type of administrative load. The frontline access gap compounds this. Deskless clinical staff — nurses, technicians, residents — often receive information through the least reliable channels because tools designed for knowledge workers require desktop access. When communication reaches frontline staff inconsistently, physicians absorb the coordination failures of the system on top of their clinical workload. ## Measurement tools and how to deploy them The Maslach Burnout Inventory remains the most validated instrument for measuring physician burnout across all three dimensions. A full MBI-HSS administration scores emotional exhaustion, depersonalization, and personal accomplishment on frequency scales. High exhaustion and depersonalization combined with low personal accomplishment indicate burnout — the instrument produces a quantitative baseline for comparison over time. The limitation is frequency. Annual MBI administration produces a single annual snapshot. Most health systems with active burnout programs supplement it with: **Pulse surveys**: Short, recurring surveys targeting MBI-adjacent questions monthly or quarterly. These catch trend movement between full assessment cycles and allow department-level pattern detection before a problem becomes a retention crisis. **Engagement surveys**: Broader satisfaction instruments that capture motivation, role clarity, and perceived organizational support. As [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) documents, disengagement and burnout share overlapping drivers — tracking engagement proactively surfaces risk before the MBI catches it. **Peer observation protocols**: Structured review processes that explicitly include behavioral observation — changes in communication style, team participation, and documentation patterns. These are most effective when normalized as standard practice rather than reserved for performance concerns. **EHR-based leading indicators**: Documentation completion rates, time between encounter and documentation, and error rate patterns in clinical documentation are measurable in most modern EHR systems. A physician whose documentation latency is increasing across weeks is showing a signal before any survey is administered. Healthcare organizations that have built systematic communication infrastructure around their clinical staff — like the model detailed in the [American College of Radiology case study](/resources/case-study-american-college-radiology) — report earlier identification of staff concerns and more consistent signal from frontline teams. ## What interventions actually reduce burnout scores Measurement without a clear action trigger is the single most common reason physician burnout programs fail. Physicians who complete surveys and see no organizational response participate less in future assessments — appropriately so. The interventions with the strongest evidence base target specific dimensions rather than burnout in aggregate: For **emotional exhaustion**, the primary levers are workload distribution, administrative relief, and schedule predictability. Physicians whose clinical hours are predictable and whose administrative tasks have clear time allocations show lower exhaustion scores than those navigating unpredictable demands. This is an operational problem with operational solutions. For **depersonalization**, peer connection and role meaning are the primary targets. Physicians who report strong team relationships and a clear sense of how their work connects to patient outcomes show significantly lower depersonalization scores. Structured team communication — department updates, recognition cadences, shared case reviews — builds the relational infrastructure that buffers against detachment. A well-designed approach to [employee engagement](/solutions/employee-engagement) addresses this by connecting individual contribution to outcomes that matter to the physician. For **reduced personal accomplishment**, recognition quality matters most. Physicians who receive specific, timely feedback on their contributions — from peers, leadership, and patients — maintain a stronger sense of impact than those receiving only metrics-based performance reviews. This dimension responds to relational investment, not operational efficiency alone. ## The health systems retaining their physicians The measurement challenge in physician burnout is not the absence of validated tools. The MBI has been in use for decades. The challenge is that measurement has been decoupled from action — annual surveys administered, scores tabulated, reports filed, and the operational conditions that produced the scores left intact. Health systems making demonstrable progress on physician retention are doing three things differently. They are measuring continuously rather than annually, which surfaces trends before they become crises. They are connecting burnout signals to operational conditions — tool fragmentation, documentation burden, communication overhead — rather than treating burnout as a personal attribute of individual physicians. And they are closing the loop: when a measurement cycle produces a finding, it produces a response with a timeline. Burnout is not a resilience deficit in the physicians experiencing it. It is a predictable output of systems that ask clinicians to absorb administrative overhead their peers in well-resourced environments do not face. Measuring it accurately is the prerequisite for addressing it — and addressing it is the prerequisite for building health systems that retain the physicians they train. --- # The Importance of Hospital Recognition Programs **Author:** Christos Schrader **Published:** 2023-10-20 **Category:** healthcare Hospital recognition programs have the potential to revolutionize the healthcare environment, creating a culture of gratitude, motivation, and excellence. These programs are not just about acknowledging individual professional achievements. Rather, they foster a system-wide spirit of collaboration, commitment, and high-quality care. Recognition programs are pivotal in reinforcing the hard work of doctors, nurses, and administrative […] Hospital recognition programs have the potential to revolutionize the healthcare environment, creating a culture of gratitude, motivation, and excellence. These programs are not just about acknowledging individual professional achievements. Rather, they foster a system-wide spirit of collaboration, commitment, and high-quality care. Recognition programs are pivotal in reinforcing the hard work of doctors, nurses, and administrative staff, enhancing job satisfaction and reducing staff turnover. By celebrating achievements, organizations can demonstrate their appreciation for the relentless efforts of their staff, especially amidst challenging situations. Moreover, these programs serve as a powerful tool for motivating employees to strive for excellence in their roles. They instill a sense of pride and accomplishment, leading to increased productivity and a more positive work environment. This results in higher patient satisfaction ratings and, ultimately, better patient outcomes. Implementing hospital recognition programs is a strategic move that can significantly boost the morale and productivity of healthcare professionals. Health systems who do this well experience more robust patient care and a healthier bottom line. Understanding Hospital Recognition Programs Hospital recognition initiatives acknowledge and reward the contributions of employees in a healthcare setting. These programs can take various forms, from employee-of-the-month awards to bonuses for exceptional performance, longevity recognition, and team-based acknowledgments. A well-implemented recognition program is not simply about offering rewards. It is about cultivating an environment that encourages and recognizes excellence, creating a sense of belonging and shared purpose among the staff. When you motivate individuals to go above and beyond, you create a more dynamic, efficient, and effective health system. Recognition programs in hospitals are also key to showcasing role models within the organization. By highlighting the exemplary work of individuals or teams, others are inspired to emulate their actions, thereby promoting best practices throughout the facility. These programs can also help to identify leaders among the staff, encouraging their growth and development within the organization. Hospital recognition programs can also be leveraged to enhance patient care. When healthcare professionals feel valued, they are more likely to invest more in their patient interactions, translating to improved patient experience and outcomes. In essence, hospital recognition programs are not just ‘nice-to-have.’ They are a ‘must-have’ for any forward-thinking healthcare institution. The Rising Need for Recognition in the Healthcare Sector The rapidly evolving dynamics of the healthcare sector underscore the critical need for effective recognition programs. With mounting pressure to provide high-quality care amidst resource constraints, healthcare professionals are often pushed to their limits. Recognition programs can serve as a powerful antidote, fostering a culture that values each individual’s contributions and promotes a healthy work-life balance. The Challenge of Turnover One of the pressing challenges in the healthcare sector today is managing staff turnover. A high turnover rate can disrupt continuity of care and lead to significant financial costs due to the need for constant recruitment, training, and onboarding. Recognition programs can address this issue head-on by improving employee retention. When staff feel valued and appreciated, they are more likely to demonstrate loyalty to the organization. The pandemic clearly demonstrated the importance of recognition in healthcare. As healthcare professionals continued to provide essential services despite personal risk and unprecedented challenges, the need for recognition was more significant than ever. Implementing robust recognition programs sends a clear message to these professionals: their courage, resilience, and dedication have not gone unnoticed. In the face of an ever-aging population, the demand for healthcare services is on the rise, putting increased pressure on clinical teams. Recognizing the signs of burnout is crucial so you can stay ahead of issues. Recognition programs can help ease this added burden by boosting morale, increasing job satisfaction, and promoting a culture of excellence and compassion at work. The Role of Technology Lastly, advancements in technology and increased patient expectations push healthcare organizations to innovate, improve, and excel. Recognition programs can play a pivotal role in this by encouraging employees to strive for innovation and excellence in their roles, ultimately leading to improved patient care and satisfaction. In summary, hospital recognition programs are not just beneficial—they’re essential in today’s healthcare environment. They play a crucial role in addressing burnout, reducing turnover, motivating employees, and promoting a culture of excellence and compassion. As such, any healthcare organization aiming to thrive in this challenging landscape should consider implementing a comprehensive recognition program as a key part of their strategic plan. For other ways to address these issues, see our list of healthcare employee engagement ideas. Key Elements of Effective Hospital Recognition Programs In designing an effective hospital recognition program, certain key elements must be incorporated to ensure its success. These elements are the foundation upon which the program is built, and they are pivotal in shaping an environment that fosters recognition, appreciation, and a culture of excellence. Personalization Personalization is an integral aspect of a successful hospital recognition program. It is crucial to acknowledge each employee’s unique contributions in a manner that reflects their individual accomplishments. Personalizing recognitions can range from acknowledging the specific characteristics of an employee’s achievement to tailoring the reward itself to the employee’s preferences or needs. This approach demonstrates a genuine appreciation for the employee’s contributions and assures them that their efforts are valued. Moreover, personalized recognition strengthens the employer-employee relationship, fostering a deeper sense of connection and belonging within the organization. Regularity Maintaining regularity in the recognition program is equally important. Consistency in acknowledgements not only assures the continuity in morale boost but also instills a sense of reliability among the employees. It’s crucial to remember that recognition should not be confined to annual or quarterly events but needs to be embedded into the everyday culture of the hospital. Regular recognition, whether it’s acknowledging an employee’s long hours during a particularly challenging week or celebrating a team’s successful project completion, keeps morale high and reinforces the organization’s commitment to valuing its employees. Visibility Visibility is another cornerstone of an effective recognition program. Public appreciation holds significant power to motivate not just the recipient but also the wider team. Celebrating achievements across the organization not only enhances the recipient’s sense of pride but also sets a benchmark of excellence for others to aspire towards. Additionally, public recognition fortifies the culture of appreciation, making it a shared value rather than an isolated managerial task. Feedback Loop Lastly, establishing a feedback loop is crucial for the continual evolution and enrichment of the recognition program. This involves creating an environment where staff members can openly discuss the recognition program, voice their thoughts, and suggest improvements. Such a feedback loop ensures that the program keeps evolving according to the changing needs and preferences of the employees, reinforcing its relevance and effectiveness in the long term. By incorporating employees’ input into the program, the organization also reinforces its commitment to valuing its employees’ perspectives and fostering a participative culture. Boosting engagement at Columbia Basin Health Association Learn how CBHA got over 90% user adoption and improved staff alignment with MangoApps READ case study The Role of Technology in Hospital Recognition Programs Digital transformation is a hot topic in healthcare today, and plays a significant role in shaping and enhancing hospital recognition programs. It facilitates numerous aspects of these programs, including automation, integration, and analytics, ultimately enabling a more efficient, impactful, and sustainable program. Automation When it comes to recognition programs, automation is a game-changer. It streamlines the process of recognition, ensuring that no deserving employee goes unnoticed. For instance, automated systems can track key performance indicators and trigger recognition when certain criteria are met. This approach not only eliminates bias but also ensures that recognition is timely and consistent. Automation also eases the administrative burden of managing a recognition program, freeing up time for healthcare administrators to focus on other strategic tasks. Integration Integration is another crucial aspect where technology can greatly enhance a recognition program. By integrating the recognition program with other systems, such as HR and payroll systems, the process becomes seamless and interconnected. For example, recognitions can be directly linked to performance evaluations or professional development plans, aligning individual achievements with organizational goals. Moreover, integration helps in maintaining a comprehensive record of recognitions, providing valuable data for performance reviews and career development discussions. Analytics Analytics brings a data-driven approach to recognition programs. With analytics, healthcare organizations can gain insights into the effectiveness of their recognition program. They can track key metrics such as frequency of recognition, types of recognition awarded, and correlation with employee performance and satisfaction levels. These insights can guide strategic decisions about the program, such as identifying areas of improvement and understanding what types of recognition are most appreciated by employees. Furthermore, analytics can help in measuring the impact of the recognition program on broader organizational outcomes, such as employee retention, patient satisfaction, and overall performance. By implementing technology in hospital recognition programs, healthcare organizations can significantly enhance the effectiveness, efficiency, and impact of these programs. The combination of automation, integration, and analytics ensures that recognition programs are robust, dynamic, and aligned with the organization’s strategic goals, thereby promoting a culture of excellence and compassion in the healthcare setting. Learn more about how MangoApps is the perfect employee app for any health system. Benefits of a Well-Implemented Recognition Program A well-orchestrated recognition program offers a multitude of benefits, with the results speaking for themselves. Numerous hospitals have reported tangible and significant outcomes upon the implementation of such programs. Increased Employee Retention One of the primary benefits of effective hospital recognition programs is higher employee retention rates. Recognizing the hard work and dedication of employees makes them feel valued and appreciated. This emotional reward often translates into a greater sense of loyalty and a lower likelihood of seeking employment elsewhere. Elevated Morale and Patient Satisfaction Recognition programs also have a direct impact on morale within the hospital. When employees feel valued, their engagement and productivity levels increase. This enhanced morale often translates into better patient care, leading to higher patient satisfaction scores. When patients see happy, satisfied employees, their trust in the care they receive increases. Positive Work Environment Recognition programs create a work environment that is not only positive but also encourages innovation and interdisciplinary collaboration. When employees feel appreciated, they are more likely to take risks and think outside the box, resulting in innovative solutions and improvements in patient care and hospital operations. Attracting Top Talent Lastly, effective recognition programs can help enhance a hospital’s reputation as a preferred employer. When a hospital is known for recognizing and valifying its employees, it becomes a magnet for top talent in the healthcare realm. The best healthcare professionals gravitate towards organizations where they know their efforts will be appreciated and rewarded. In conclusion, the implementation of a comprehensive and effective recognition program is an investment that leads to numerous benefits for both the employees and the hospital as a whole. Its impact is far-reaching, enhancing every facet of hospital operations from employee satisfaction to patient care. Steps to Start or Revamp Your Hospital’s Recognition Program If you’re considering initiating or refining your hospital’s recognition strategy, here are some steps to guide you: Conduct an honest assessment of your current program. Define clear goals and objectives. Engage staff for their insights and suggestions. Use technology to streamline and enhance the process. Continuously monitor, measure, and iterate for maximum impact. Conclusion For health systems aiming for excellence, investing time, effort, and resources in hospital recognition programs isn’t just a good idea; it’s a commitment to excellence. Resources like MangoApps enable teams like yours with all the tools they need to not only run these programs, but ensure that this information makes it to clinical staff, alongside all of the other job-critical resources they struggle to find today. To learn more, read about our healthcare offering, or how to build a HIPAA-compliant intranet. --- # How to Reduce Nurse Turnover **Author:** Christos Schrader **Published:** 2023-10-20 **Category:** healthcare Retaining skilled nursing staff is a critical goal for every health system. Frequent turnover not only impacts patient care quality but also weighs heavily on the financial health of the organization. For these reasons and more, figuring out how to reduce nurse turnover is a pressing issue. In this comprehensive guide, we will share insights […] Retaining skilled nursing staff is a critical goal for every health system. Frequent turnover not only impacts patient care quality but also weighs heavily on the financial health of the organization. For these reasons and more, figuring out how to reduce nurse turnover is a pressing issue. In this comprehensive guide, we will share insights and strategies we’ve learned from many years of working with health systems and clinics. We hope that this article will empower you to build a motivated, loyal, and enduring nursing team. The Real Costs of Nurse Turnover Nurse turnover doesn’t just affect the quality of patient care – it also carries significant financial implications. Every time a nurse leaves, the organization incurs costs related to recruitment, training, and the reduced productivity during the transition period. According to a 2023 study by NSI Nursing Solutions, the average cost of replacing a registered nurse is $52,350. Moreover, the costs aren’t purely financial. Each departure can impact the morale and workload of the remaining staff, potentially initiating a domino effect that leads to even more departures. This can lead to increased burnout and stress among the remaining nurses, which in turn can lower the quality of care they provide. Indirect costs include decreased patient satisfaction due to unfamiliarity, a reduction in the continuity of care, and potential increases in errors. Understanding these costs is the first step towards reducing nurse turnover. By recognizing the full impact of nurse turnover, health system administrators are better equipped to implement effective strategies for retention. In the following sections, we’ll discuss several proven methods for reducing nurse turnover and creating a more supportive and stable work environment for your nursing staff. Top Factors Contributing to Nurse Turnover A multitude of factors contribute to nurse turnover, and understanding these is crucial to formulating effective retention strategies. Work Environment Work environment plays a significant role in nurse satisfaction and retention. A positive work environment promotes collaboration, respect, and strong leadership, fostering a sense of belonging and dedication among the nursing staff. Conversely, a negative environment characterized by poor management, lack of communication, and inadequate support leads to dissatisfaction and eventually, turnover. Work-Life Balance The demanding nature of nursing often leads to long hours, overtimes, and irregular shifts, severely impacting work-life balance. Nurses struggling to juggle their professional responsibilities with personal life may experience burnout and choose to leave, especially when understaffing exacerbates all of these issues. Career Advancement Opportunities Limited opportunities for professional growth and advancement can lead to frustration among ambitious nurses. Institutions that fail to provide ongoing training, education opportunities, or clear career progression paths may face higher turnover rates. Compensation and Benefits Compensation is a tangible recognition of a nurse’s skills, experience, and contribution to the organization. Therefore, if nurses feel inadequately compensated or if benefits do not meet their needs, they may seek opportunities elsewhere. Burnout Nurses are often exposed to high-stress situations, leading to physical and emotional exhaustion, or burnout. Chronic burnout can drastically reduce job satisfaction and prompt nurses to leave the profession. Understanding the complexity of these factors and making strides to reduce burnout in your health system is essential to address nurse turnover effectively. Next, we will delve into strategic measures to tackle each of these issues, aiming to create a supportive, rewarding, and sustainable work environment for nurses. Boosting engagement at Columbia Basin Health Association Learn how CBHA got over 90% user adoption and improved staff alignment with MangoApps READ case study The Role of Technology in Addressing Turnover While technology is not a panacea, it has a pivotal role in alleviating some of the challenges nurses face. Properly implemented technological solutions can drastically simplify tasks, bolster communication, reduce prevalent stressors, and provide invaluable data to track recurring issues. For instance, employee engagement and retention software can help organizations identify patterns of dissatisfaction and address them proactively. At the same time, advanced scheduling technology can minimize shift cancellations and reduce nurses’ anxiety about last-minute changes. It’s not just about reducing stress – technology can also offer opportunities for career advancement through e-learning platforms or telehealth services that allow nurses to expand their skills and specialize in different areas. In short, technology can play a critical role in reducing nurse turnover by enhancing the work experience and promoting professional development opportunities. This is just one of the many benefits of digital transformation in healthcare. Best Practices to Reduce Nurse Turnover 1. Prioritize Nurse Well-being and Mental Health The well-being and mental health of nurses are paramount in reducing nurse turnover. Implementing programs that prioritize these aspects can significantly improve their job satisfaction and longevity in the profession. Promote a Healthy Work Environment A safe, engaging, and respectful work atmosphere can improve nurses’ morale, leading to reduced turnover. Encourage open dialogue and feedback, recognize and appreciate efforts, and ensure that the nurses have the necessary resources to perform their duties. Promote team-building activities and foster a culture of mutual respect and camaraderie. Implement Stress Management Programs Nursing is a high-stress profession, which can lead to burnout if not properly managed. Offering stress management programs, like mindfulness training or relaxation techniques, can help nurses cope with daily pressures. Encourage regular breaks during shifts, and provide a relaxation area for nurses to unwind. Support Work-Life Balance Ensure that the nurses have a fair work-life balance by offering flexible schedules, part-time positions, or job sharing. Use technology to streamline scheduling and minimize shift cancellations and last-minute changes that can cause stress. Offer Mental Health Support Providing mental health support, like counseling services, mental health days, and resilience training, can be invaluable to nurses. Moreover, it’s vital that nurses feel supported and have an outlet to discuss their stresses and challenges. Promote Physical Health Nurses often neglect their own physical health due to the demands of their job. Encourage healthy habits by providing fitness facilities or arranging for group fitness activities. You can also consider offering health and wellness discounts as part of their benefits package, as this can motivate nurses to take care of their physical well-being, which is directly tied to their mental health. By prioritizing the well-being and mental health of nursing staff, healthcare institutions can create a positive work environment that encourages retention and helps reduce nurse turnover. 2. Offer Competitive Compensation and Benefits The compensation and benefits package plays a significant role in a nurse’s decision to remain with a particular organization. It’s not just about remuneration; the comprehensive benefits package can make a substantial difference in reducing nurse turnover. Offer Competitive Salaries Competitive salaries are a fundamental aspect of nurse retention. Pay scales should reflect the nurses’ level of education, years of experience, skills, and job responsibility. Therefore, regularly reviewing and adjusting salaries to reflect industry standards and cost of living ensures that your institution remains an attractive place of employment. Provide Comprehensive Health Benefits Comprehensive health benefits, including medical, dental, and vision coverage, are a critical component of a competitive compensation package. Also, consider offering benefits that cater to the well-being of nurses, such as wellness programs, gym memberships, or even on-site health clinics. Consider Retirement Plans Like anyone else, nurses value employers who help them plan for their future. For instance, retirement plans, like a 401(k) or similar schemes, with employer contribution matching, can be a significant incentive for nurses to stay with your organization. Offer Adequate Vacation and Sick Leave Nurses are at the frontline of healthcare, often working in stressful and demanding conditions, making adequate rest crucial. Ensure that your organization offers a fair amount of vacation and sick leave. Additionally, providing mental health days can underscore your commitment to their overall well-being. Family-friendly Policies With many nurses juggling their careers with family responsibilities, family-friendly policies can significantly enhance job satisfaction. These may include maternity/paternity leave, flexible scheduling, childcare support, and more. In summary, a competitive compensation and benefits package can go a long way in maintaining nurse satisfaction, which directly influences nurse retention. While it involves an upfront investment, the reduction in turnover-related costs makes it a worthy expenditure. By demonstrating that they are valued and appreciated, nurses are more likely to remain loyal and committed to your organization. 3. Provide Opportunities for Professional Development Professional development is a key factor to consider when thinking through how to reduce nurse turnover. Nurses are lifelong learners who typically thrive on opportunities to expand their knowledge and skills. By providing ample avenues for professional development, healthcare organizations can foster a culture of continuous learning that encourages nurses to grow and advance within the institution, reducing the likelihood of turnover. Invest in Continued Education Nurses should be encouraged and supported to pursue further education. This can be achieved by offering scholarships, tuition reimbursement, or creating partnerships with educational institutions that allow for discounted tuition fees. Continued education not only benefits the individual nurse but also enhances the quality of patient care and the organization’s overall reputation. Offer In-House Training and Development Programs In-house training is often a cost-effective way to enhance the skills and knowledge of your nursing staff. For example, this could involve workshops, seminars, or online courses on various topics relevant to their work. Offering these opportunities to nurses not only enhances their capabilities but also reinforces their value to the organization, contributing to a lower turnover rate. Create a Mentorship Program Mentorship programs can be incredibly beneficial in nursing, particularly for new nurses. Pairing a less experienced nurse with a more experienced one can provide them with guidance, support, and insights that they may not gain elsewhere. In addition to improving their skills, this type of program can also boost their confidence and help them feel more connected to the organization. Support Role Advancement Nurses should feel that there are opportunities for them to advance in their roles within the organization. For instance, this could involve creating clear career pathways, offering leadership training, or providing opportunities for nurses to specialize in a particular area of interest. This sends the message that the organization values their contributions and is invested in their career growth. Recognize and Reward Excellence Hospital rewards and recognition programs recognizing exceptional work are critical in keeping nurses motivated and committed to their jobs. Examples include employee of the month programs, public acknowledgements, or even small tokens of appreciation. When nurses feel their hard work is recognized and appreciated, they are more likely to remain loyal to the organization. In conclusion, professional development opportunities are a crucial determinant of nurse satisfaction and retention. By investing in the growth and development of your nursing staff, you not only enhance the quality of care provided but also nurture a committed, satisfied, and skilled workforce, ultimately reducing nurse turnover. Enabling clinical staff at Marion Health Learn how Marion Health improved communication and collaboration among staff and clinicians with a secure employee app. READ case study 4. Foster a Positive Work Environment A positive work environment is arguably one of the most impactful factors that can help reduce nurse turnover. A supportive, inclusive, and communicative atmosphere can significantly improve nurse satisfaction and loyalty to the organization. Here are some ways to foster a positive work culture: Promote Effective Communication Open, two-way communication is the foundation of a positive work environment. For instance, regular team meetings, feedback sessions, and open-door policies can help make nurses feel heard, respected, and valued. An effective communication system also helps to resolve any conflicts or issues promptly, preventing dissatisfaction and discontent. Ensure Adequate Staffing Understaffing can lead to overworked nurses, increased burnout, and higher turnover rates. Therefore, by ensuring adequate staffing levels, you can limit the amount of mandatory overtime and prevent burnout, enhancing job satisfaction and retention. Promote Teamwork Fostering a strong sense of teamwork and collaborative spirit can help nurses feel more connected and engaged at work. Regular team-building activities, collaboration on projects or tasks, and an emphasis on collective success can help create a stronger, tight-knit team. It’s also crucial to promote interdisciplinary collaboration to create a more integrated, well-rounded system for patient care. Maintain a Safe and Healthy Workplace The importance of maintaining a safe and healthy work environment cannot be overstated, especially in a healthcare setting. Regular training on safety protocols, availability of personal protective equipment, and an emphasis on the physical and mental well-being of your staff can go a long way in creating a positive work environment. Ensure Fair Treatment A workplace where fairness and equality are prioritized boosts job satisfaction and reduces the likelihood of turnover. Establishing policies that ensure equal opportunities, non-discrimination, and fair treatment for all employees is essential. In conclusion, a positive work environment can have a significant impact on nurse turnover. By taking steps to foster a supportive, inclusive, and respectful work culture, you can improve job satisfaction and loyalty among your nursing staff, ultimately reducing turnover and enhancing the quality of care provided. For more on this topic, see our healthcare employee engagement ideas. 5. Seek Regular Feedback Seeking regular feedback is a proactive approach that paves the way for open dialogue, encourages improvements, and helps to reduce nurse turnover. It empowers nurses by giving them a voice, making them feel valued, and enhancing their job satisfaction. Implement Routine Feedback Sessions Implementing routine feedback sessions is an effective way to understand the challenges your nurses might be facing and address them promptly. These could be structured as one-on-one meetings with their direct supervisors or as anonymous group sessions. The key is to create a safe space where nurses feel comfortable expressing their concerns and suggestions. Provide Constructive Feedback Providing constructive feedback to your nursing staff can help them improve their performance and grow professionally. This feedback should be timely, specific, and focused on behavior rather than the individual. When nurses receive regular feedback on their work, they are more likely to feel engaged and committed to the organization. Create a Feedback-Friendly Culture Creating a culture that values feedback can make your nursing staff feel appreciated and heard. This involves reassuring your employees that their voices matter and that their inputs will be taken into consideration. Regular communication about changes made based on their feedback can reinforce this message. Introduce Feedback Tools Introducing tools and platforms that facilitate easy and efficient feedback collection can also be beneficial. Online surveys, suggestion boxes, and mobile apps can make the process more convenient and allow for anonymous feedback, encouraging more participation from your nursing staff. In conclusion, regular feedback is instrumental in reducing nurse turnover rates. It enables healthcare organizations to promptly address issues, improve nurses’ job satisfaction, and ultimately retain a competent and happy workforce. This proactive approach not only reduces nurse turnover but also significantly enhances the quality of patient care. How We Can Help You Reduce Nurse Turnover Investing in a HIPAA-compliant intranet and employee app like MangoApps can make all of the above easier, by giving you a place to house and manage all of your employee-facing programs. Automation enables faster, more effective work, and getting data on participation and engagement makes it easier to see how effective your programs are. Furthermore, a modern employee app ensures that nurses and other clinical staff will actually be able to see and engage with all of your great content and programs. Learn more about how our platform for healthcare can benefit your organization. Conclusion The question of how to reduce nurse turnover isn’t just about numbers or operational efficiency. At its core, it’s about ensuring the best possible care for patients and creating a sustainable, rewarding environment for the nurses who dedicate their lives to this noble profession. As health systems navigate this challenge, a holistic approach—one that considers technological solutions alongside human-centric strategies—is the way forward. --- # Physician Engagement Strategies for Modern Health Systems **Author:** Christos Schrader **Published:** 2023-10-20 **Category:** healthcare In today’s evolving healthcare landscape, fostering robust physician engagement strategies is critical for health system administrators. It’s more than just a buzzword—it’s a transformative approach that bolsters both individual performance and overall organizational health. Implementing thoughtful, effective physician engagement strategies can lead to improved patient care, increased staff satisfaction, and ultimately, a more robust bottom […] # Physician Engagement Strategies for Modern Health Systems When Dr. Mara Chen finishes a twelve-hour shift, her last task before leaving is not patient care — it is a search. She is tracking down a policy update that went out over email to a distribution list she was never added to, trying to confirm whether the new discharge protocol applies to her ward, and composing a message to HR about a scheduling conflict through a system that takes three screen transitions to navigate. By the time she leaves the building, she has not found the policy. She has improvised. This is what physician disengagement looks like in practice. Not a physician who stopped caring — a physician who has stopped trusting that the systems around her will help her do her job. Per IDC, employees lose an average of 2.5 hours each day searching for information across disconnected systems. In healthcare, those hours compete directly with patient care time, and the erosion is rarely dramatic. It accumulates across shifts until clinical staff stop looking for information and start working around it. Every physician engagement strategy your health system deploys operates on top of that infrastructure. When the infrastructure fails, the strategy does not reach the people it was designed for. ## Why the standard engagement playbook stalls Health systems have invested heavily in physician engagement over the past decade: leadership accessibility programs, formal feedback mechanisms, performance recognition frameworks, CME support, and leadership development pipelines. Each addresses a real dimension of the problem. Most of them are invisible to the physicians who need them most. Per Social Edge Consulting, 91% of organizations operate an intranet. Nearly a third of employees never log in. Only 13% use one daily. Per SWOOP Analytics, the average employee spends six minutes a day using intranet tools — not because they are indifferent to organizational knowledge, but because the systems serving it are slow, siloed, and inaccessible. In healthcare, where per-shift time is zero-sum, a communication channel that demands more than a few seconds of navigation gets abandoned. The policy update sits in a folder. The recognition post goes unread. The feedback survey link arrives in an inbox that is already being ignored. This is not an engagement failure in the traditional sense. It is an access failure that produces engagement failure as its downstream effect. Health systems investing in engagement programs while leaving the delivery infrastructure unrebuilt are trying to run water through pipes that have been disconnected. ## The four forces pulling physician engagement apart Understanding why engagement erodes requires separating infrastructure problems from culture problems. In most health systems, three of the four forces driving disengagement are infrastructure problems. **Administrative burden compounds beyond paperwork.** The shift from volume-based to value-based care added organizational responsibility to clinical roles without removing the time required for either. Physicians now contribute to quality initiatives, committee structures, and strategic planning decisions on top of their clinical load. Each individual commitment is defensible. The aggregate is unsustainable — and when physicians feel the weight of it, they disengage from the organizational layer first, protecting the clinical layer last. **Technology adds friction faster than it removes it.** Health systems that added specialized tools to solve specific problems — scheduling software, compliance tracking, policy management, communications platforms — created an environment where every question requires a different login. Physicians and nurses who lose time switching between disconnected systems are not resistant to technology. They are making an accurate assessment that the technology is not working. The cognitive cost of tool sprawl is an engagement cost that compounds every shift. **Frontline clinical staff were never the target user.** Per Emergence Capital, 80% of the global workforce is deskless — working on floors, in wards, in clinics, in the field. Most enterprise engagement infrastructure was designed for office workers with corporate laptops, corporate email addresses, and VPN access. A nurse without a work email cannot receive the recognition message. A technician on a hospital floor cannot access the policy update through a VPN she has never been provisioned for. Mobile-first access without institutional credentials is not a convenience feature. It is the precondition for reaching the staff who most need reaching. **Disengagement and burnout are mutually reinforcing.** Research published in Health Care Management Review found that hospitals with high physician engagement had 26% higher patient satisfaction scores and significantly lower patient mortality rates. The inverse is equally documented: health systems where clinical staff feel unsupported see turnover accelerate, compounding the workload for those who remain. Replacing a frontline healthcare employee costs between $4,400 and $15,000. Engagement investment and retention investment are the same investment. ## What effective physician engagement actually requires The physician engagement strategies that produce measurable outcomes share a structural feature: they treat access as the precondition, not the afterthought. **Reach the staff who cannot log in from a desktop.** Health systems moving the needle on frontline engagement are not the ones with the most comprehensive intranet. They are the ones with a mobile-first employee app that clinical staff can use from personal devices, that does not require a VPN, and that delivers policy updates, shift information, and recognition without bureaucratic navigation. When [employee engagement infrastructure](/solutions/employee-engagement) reaches every clinical staff member — not just the ones with corporate devices — engagement programs actually reach them. The [American College of Radiology](/resources/case-study-american-college-radiology) deployed a platform built around how distributed professionals actually access information and saw adoption and response-time outcomes shift within the first quarter. **Consolidate the tool sprawl.** The administrative burden driving physician frustration is partly procedural — but largely structural. When a physician resolves a scheduling conflict in one system, submits a policy question through another, and reads a performance update through a third, each transition carries its own friction. Unified platforms that consolidate communications, HR self-service, and knowledge access into a single experience reduce the switching cost that currently competes with patient care time for physician attention. The administrative layer does not disappear — but it stops requiring cognitive reorientation to navigate. **Make physician feedback visible in outcomes.** Engagement comes from visible change. Formal committees and anonymous surveys are necessary — but insufficient when physicians raise concerns and see no traceable response. The feedback loop has to close somewhere the physician can observe it: a process update, a policy revision, an acknowledged problem. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), the organizational capability that most reliably predicts sustained engagement is whether employees receive the information they need, when they need it, without having to escalate. That is an infrastructure criterion before it is a culture criterion. **Put recognition where the recipients are.** Performance recognition that happens in all-staff meetings reaches the staff who attend them. Recognition that reaches a physician's device within hours of the event reaches everyone, regardless of shift schedule or physical location. In healthcare organizations where frontline staff rarely share a common physical space, digital visibility is the only reliable visibility. The mechanism matters as much as the intention — and health systems that invest in recognition programs while delivering them through infrequently accessed channels are creating recognition that mostly reaches the already-engaged. **Connect compensation alignment to measurable quality contributions.** Compensation models that center patient volumes without weighting quality contributions or organizational involvement structurally discourage engagement beyond the clinical role. Transparent linkage between engagement behaviors — participation in quality initiatives, contribution to protocol improvements, cross-departmental collaboration — and compensation creates alignment that generic recognition alone cannot produce. Physicians do not need to be paid to care about their organization. They need compensation models that do not penalize them for doing so. ## Measuring what matters: how health systems know engagement is improving Most health system engagement metrics lag too far behind the behaviors they are trying to track. Annual surveys, quarterly turnover reports, and once-per-cycle satisfaction scores are artifacts of the traditional engagement audit — useful for identifying long-term trends, insufficient for informing in-cycle adjustment. The engagement signals worth tracking are closer to real time: platform adoption rates across different clinical staff populations, response latency on policy updates across floors, and participation rates in feedback mechanisms broken down by role, shift, and department. When those metrics are available, two patterns become consistently visible. First, the engagement gap between clinical populations with mobile access and those without is almost always larger than administrators expect. Second, the departments where engagement is highest almost always have leaders who close the feedback loop fastest — not necessarily leaders with the most resources. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents the pattern clearly: engagement initiatives underperform not because the strategy is wrong but because the communication system cannot reliably deliver the initiative to the people it was designed for. Fixing the delivery layer produces measurable engagement gains faster than redesigning the initiative. Timeline expectations matter here. Health systems deploying a mobile-first access layer for frontline staff typically see platform adoption within weeks, not months — because the friction was the barrier, not the willingness. Recognition visibility, feedback response rates, and policy-read confirmation rates all improve within the first quarter when the delivery infrastructure is in place. The strategic programs — leadership development pipelines, compensation model redesign, committee involvement — require longer cycles, but they only work when the underlying communication layer is functioning. ## The infrastructure question that precedes everything else Dr. Chen's policy search problem — the one that ends with improvisation rather than information — is solvable. Not with a new committee, a revised feedback survey, or an updated compensation model. With access: a mobile app that surfaces the policy in ninety seconds, confirms she has read the update, and logs the interaction so her organization knows whether the protocol reached the floor. The strategies in every physician engagement framework — open communication, leadership accessibility, training support, recognition, decision-making involvement — are sound. They fail when they run on infrastructure that cannot reach the people they were designed for. Health systems that close the engagement gap are not inventing new strategies. They are building the delivery infrastructure that allows existing strategies to work for the 80% of clinical staff that current systems cannot reach. That is the precondition. The physician engagement programs your organization has already invested in can follow from it — but not before it. --- # How to Ensure Internal Communication & Email Accessibility **Author:** Justina Kolb **Published:** 2023-10-19 **Category:** intranet Internal communication is the lifeline of any organization. It helps keep everyone on the same page, facilitates decision-making, and ultimately plays a vital role in driving business success. That’s why it’s crucial to ensure every member of your team is equipped to consume company content by creating internal communications and emails that meet accessibility standards. We’ve […] Internal communication is the lifeline of any organization. It helps keep everyone on the same page, facilitates decision-making, and ultimately plays a vital role in driving business success. That’s why it’s crucial to ensure every member of your team is equipped to consume company content by creating internal communications and emails that meet accessibility standards. We’ve come up with a comprehensive checklist you can reference to ensure internal communication and email accessibility within your organization. The Importance of Internal Communication & Email Accessibility When a company’s internal communications and emails fail to meet accessibility requirements, both the organization and its employees face significant hurdles. Traditional modes of communication, such as emails and newsletters, often neglect accessibility standards, making it difficult for employees with disabilities to effectively access and engage with important information. This exclusion can result in decreased productivity and morale among affected employees. Moreover, companies can inadvertently find themselves in non-compliance with accessibility regulations, potentially leading to legal challenges and reputational damage. The absence of accessibility measures also means missing out on a diverse talent pool and the unique perspectives that individuals with disabilities bring to the workforce. To address these challenges, it’s essential for companies to prioritize accessibility in their internal communications, ensuring equal access and inclusion for all employees. How CIVICUS Strengthens Civic Space Learn how CIVICUS uses MangoApps to: Collaborate & communicate in a secure network. Support, train, and share resources Create a sense of autonomy within the organization learn more Internal Communication & Email Accessibility Checklist By following this accessibility checklist, your internal communication team can create content and platforms that are accessible to all employees, fostering inclusivity and ensuring that important information is available to everyone. – Alt Text for Images and Graphics To ensure email accessibility, all images and graphics in your communications should have descriptive alt text to assist employees who use screen readers. This ensures visually impaired members of your team can digest information that is communicated through visual elements.  – Accessible Document Formats Use accessible document formats such as PDFs with proper tagging and headings, so users can easily find what they need and understand the flow of the content. Avoid relying solely on scanned documents, as they do not offer features such as text customization or content reflow, which enhance accessibility. Scanned documents also lack underlying text data, which means they cannot be read by screen readers.  – Readable Text Use clear and legible fonts to increase the accessibility of your emails and company content. Traditional, well-known fonts like Times New Roman and Arial ensure users have easy access to content across browsers and devices. For colors, make sure there is a stark contrast between the background and text; if your background is dark, use a light font color, and vice versa.  – Proper Header Structure Use proper header tags (H1, H2, H3, etc.) to organize content hierarchically. Headers should accurately represent the content’s structure to give readers a clear understanding of what the content is about. Sans Serif fonts are great for headings as they are usually larger than serif fonts and have a more block-like appearance, giving them slightly higher readability than serif fonts. Using proper header structure can boost your internal communication and email accessibility.  – Descriptive Links Use descriptive link text that provides context, rather than generic phrases like “click here” or “read more,” so users understand exactly why they are clicking and where they are going. Read your link text as if it is a standalone sentence – do you understand what the link is for out of context? If not, add more descriptive language to it so it is abundantly clear.  – Video and Multimedia Text Provide captions and transcripts for videos, and ensure that any audio content is accompanied by text-based alternatives for hearing-impaired users. Multimedia is a great way to make company content more engaging. It’s important to take the necessary steps to ensure accessibility when including media in emails and internal communications.  – Keyboard Accessibility Ensure that all content and interactive elements can be navigated and activated using a keyboard, without relying on mouse-only interactions. This ensures users who use Braille keyboards or have motor disabilities can easily navigate and consume the content shared in your internal communications.  – Text-to-Speech Compatibility Verify that your content is compatible with text-to-speech software and does not present barriers to users who rely on this technology. An important aspect to consider when picking a text-to-speech provider is customization. This gives users the ability to choose which language, voice, speed, pitch, and accent they hear when the content is read to them, ensuring they can consume the information in a way that is best suited to their needs.  – Contrasting Colors Avoid using color as the sole means of conveying information or indicating errors – set up text and audio notifications to ensure information or errors are easily inferred. When picking colors for your internal comms content, make sure to use high-contrasting combinations. This applies not only to text/ background, but also to icons, such as trash cans, download icons, and search icons.  – Consistent Navigation Maintain consistent navigation structures and layouts to help users predict where to find information (newsletter templates can help with this!). Consistent navigation is fundamental to email accessibility, as it reduces the learning curve and allows users to efficiently digest and move around the content. Consistency in design and layout also allows users to focus on the content rather than spending mental energy on figuring out how to navigate, which can be helpful for those with cognitive or learning disabilities. – User Feedback If you’re looking to improve your internal comms and email accessibility, encourage employees to provide feedback and give notes. In the end, you want your company content to be easily accessible by every member of your team. Why not give those who know best an opportunity to share their thoughts and needs? Provide a convenient, user-friendly way for employees to provide feedback, like polls or surveys, so your organization can continue to improve accessibility efforts. Accessible Internal Communications with MangoApps Ensuring internal communication and email accessibility is essential for every organization. It assures every team member can consume and contribute to the information shared. MangoApps’ Posts feature can help companies achieve this by providing accessibility options like text-to-speech, instant language translation, and video captioning. In addition to making compliance easier, these features can also promote inclusivity and diversity in the workplace.Text-to-SpeechText-to-speech can make internal communication accessible for team members with visual impairments, language barriers, and other disabilities. Users can choose from over 25 languages and a variety of voices to create voice-enabled Posts. This makes it easy for internal comms teams to reach team members who prefer consuming content via audio.  Instant Language TranslationIn today’s globalized world, it is common to have team members who speak different languages. Instant language translation can break down language barriers, making internal communications and email accessible to every team member. This feature can automatically translate Posts into different languages, allowing non-native speakers to consume content in their preferred language. This can also enhance cross-cultural communication and foster a diverse and inclusive workplace. Video CaptioningVideos are a powerful tool for internal communication, but can be difficult for team members with hearing impairments to consume. Video captioning can make videos accessible to everyone by displaying text captions alongside the video. This feature can also be beneficial for non-native speakers who might find it difficult to follow the audio content. Inclusivity and ComplianceInclusivity is not only a moral obligation but also a legal requirement. Organizations need to ensure they’re creating accessible internal communications that every member of their staff can successfully consume. This can also help in compliance with disability laws and regulations. MangoApps’ Posts feature provides numerous accessibility options that can help organizations meet these requirements, and foster an inclusive work environment. Improve your company’s internal communications and email accessibility to boost inclusivity within your organization, while engaging every member of your team, with MangoApps’ Posts!  book A demo! --- # How to Improve Internal Communications with MangoApps’ Posts **Author:** Justina Kolb **Published:** 2023-10-19 **Category:** employee-app Effective internal communication is integral when it comes to your organization running smoothly. It’s crucial that everyone in your company is well-informed and stays updated about the latest developments, upcoming events, and company announcements. This not only ensures employees reach their full potential but also creates a sense of community and belonging. However, traditional forms […] # How to Improve Internal Communications with MangoApps' Posts Improving internal communications means choosing a channel that reaches every employee — not just those sitting at a desk with a company email address. MangoApps Posts gives communications teams a single publishing surface for targeted announcements, policy updates with acknowledgment tracking, and multi-channel delivery that reaches frontline workers wherever they work. This article covers what structural gaps existing tools leave open, how Posts closes them, and how to set up the first workflow that changes what employees actually receive. ## Why email and intranet tools create structural coverage gaps Most organizations are running two internal communication channels that underperform by design — and the failure is architectural, not operational. Email reaches knowledge workers reliably but excludes the 80% of the global workforce that is deskless, per Emergence Capital. Frontline staff in retail, manufacturing, and healthcare frequently do not have company email addresses. Any communication strategy built on email has a coverage ceiling before a single message is drafted. Intranets offered an alternative, but adoption numbers for most deployments tell a similar story. Per Social Edge Consulting, 91% of organizations operate some form of intranet — but only 13% of employees use those tools daily, and nearly a third never log in at all. SWOOP Analytics found that the average employee spends just six minutes per day inside intranet platforms. A tool that employees visit six minutes a day is not a communication channel. It is a reference library that most of the workforce rarely consults. The information cost compounds. Per IDC, employees spend 2.5 hours per day searching for information they cannot easily find. That figure reflects not inbox overload but information architecture failure: when policies live in email threads and procedures are distributed as attachments, the organization has hidden its institutional knowledge inside tools that were never designed to surface it during a shift. ## What MangoApps Posts does differently MangoApps Posts is the publishing layer inside the [employee communications platform](/solutions/employee-communications) — the interface through which HR, operations leaders, and content teams push structured communications to the workforce. Several design decisions distinguish it from email and legacy intranet publishing. **Multi-channel delivery from a single post.** One post published in MangoApps simultaneously generates push notifications, in-app delivery, and optional SMS or email alerts. Frontline workers who never open a company email receive the same communication as headquarters staff — through the delivery channel most likely to reach them based on their role and device. **Real-time multilingual translation.** Posts supports translation across more than 50 languages, converting content into an employee's preferred language automatically. For distributed workforces spanning multiple regions, this removes a structural barrier that email and SharePoint cannot address natively. **Offline access for low-connectivity environments.** Retail floors, warehouse environments, and healthcare facilities frequently have unreliable network connectivity. MangoApps caches content for offline access, ensuring that policy updates reach employees regardless of whether they can sustain a network connection during their shift. **Acknowledgment records by employee.** Posts that require documented confirmation — safety training sign-offs, policy change acknowledgments, compliance certifications — generate a read-confirmation record automatically. The platform produces an auditable trail that closes the gap between "we sent the communication" and "we can confirm it was received and acknowledged." **AI-powered sentiment analysis.** For organizations with multiple authors publishing across teams, MangoApps surfaces tone inconsistencies before publication. Sentiment analysis flags communications that may land differently than intended — particularly relevant for sensitive operational or personnel topics where consistent tone matters across the workforce. ## How to set up your first post and reach every employee Creating the first post takes three decisions: what the message is, who should receive it, and whether acknowledgment is required. From the MangoApps dashboard, a communications team member creates a new Post, enters the body content, and selects a distribution target — all employees, a specific department, or a custom segment defined by location, role, or team. For time-sensitive communications, push notification delivery is enabled with a single toggle. For announcements that require acknowledgment — policy updates, safety procedure changes, compliance certifications — the read confirmation toggle generates a tracked record for each recipient. The ghostwriting workflow handles high-volume publishing across leadership. A communications specialist drafts a post under an executive's name, routes it through approval, and publishes it once cleared. Multiple departments can review before publication. This keeps messaging consistent across 3,000-facility organizations without requiring executives to manage their own publishing queue. The first post establishes a habit anchor: employees learn that the platform surfaces information they need rather than information they have to search for. The second and third posts reinforce it. Once employees trust that a push notification from MangoApps carries relevant, actionable content rather than noise, open rates diverge sharply from the email benchmarks most organizations are used to seeing. ## How to target messages by role, location, and department Broadcast communication trains employees to ignore most messages because most messages are not relevant to them. A compliance update for warehouse managers should not land in the feed of retail associates. A benefits enrollment deadline for one region should not reach employees enrolled under a different plan. Every irrelevant message that arrives reduces the probability the next one gets opened. MangoApps Posts addresses this at the delivery layer. Distribution targets are set at the post level: a specific department, a facility, a job title, or a custom group built from any combination of workforce attributes. A frontline supervisor in a distribution center receives communications relevant to their team and location. The update that applies to a different division stays out of their feed. The same segmentation logic handles language routing. A post translated into Spanish, French, and Mandarin delivers each version to the appropriate recipient based on language preference — no manual versioning of the same message per language group, no separate publishing workflow for each translation. Segmentation works in both directions. After a post goes out, communications teams see which segments received it, which employees confirmed receipt, and which segments have low read rates before those gaps surface as operational problems. That visibility is what makes the difference between an audit trail and a communication strategy. ## How to measure whether communications are actually reaching employees The structural weakness of email-based internal communications is the absence of actionable analytics after send. Open rates, if tracked at all, tell you what percentage of recipients opened the message. They say nothing about how long employees engaged with the content, whether they shared it, or whether the message produced the response it was designed to drive. MangoApps surfaces analytics at the communication level: reach by segment, read rates by department, engagement by content type. These metrics close the loop between communication investment and workforce outcomes. The Gallup 2026 State of the Global Workplace report documents that employee disengagement has measurable organizational costs in productivity, retention, and operational performance. Communication analytics identify where the gaps are before they show up in those lagging indicators. For regulated industries, the acknowledgment audit trail is not a secondary feature — it is the compliance posture. When a procedure changes, the platform documents that the affected workforce received, opened, and confirmed the update. That record is available without a separate tracking process layered on top of the communication workflow. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents the direction this category is heading: AI-driven personalization, frontline reachability at scale, and the transition from one-way broadcasting to two-way dialogue where employees can acknowledge, respond, and surface questions through the same platform they receive updates on. ## What adoption looks like in practice The adoption benchmark for most legacy intranet deployments is six minutes per day per employee, per SWOOP Analytics. MangoApps deployments produce results in a different range. OU Health achieved 87% workforce engagement within months of launching a branded employee app. PetSmart reported 4x the industry engagement benchmark after deploying a mobile-first employee communications platform. Those figures come from production deployments in large, distributed organizations — not pilots or controlled conditions. The pattern is consistent across deployments: platforms that reach employees on devices they already carry remove the access friction that drives non-adoption in legacy tools. Push notifications that surface relevant communications without requiring a login remove the behavioral friction that produces six-minute-per-day usage numbers. For frontline workforces in healthcare, retail, and logistics, the retention economics make the investment case concrete. Replacing a frontline employee costs between $4,400 and $15,000 per person. A workforce that feels unreachable, uninformed, or excluded from company-wide communications is a workforce with elevated attrition risk. Communications infrastructure that reliably reaches every employee — in their language, on their device, with documented confirmation — addresses those engagement factors before they become turnover events. ## How to evaluate internal communications platforms If your organization is comparing MangoApps against email, a legacy intranet, or a competing employee experience platform, the most useful evaluation framework focuses on coverage, accountability, and adoption outcomes rather than feature counts. **Coverage.** What percentage of your workforce can receive a communication without any change to their device setup or email provisioning? Platforms that require a corporate email address or company-issued device have a hard coverage ceiling for frontline workforces. The [employee app](/solutions/employee-app) model — accessible from personal devices on any operating system, without a corporate email — removes that ceiling. **Security posture.** For enterprise and regulated environments, SAML 2.0, OAuth 2.0, and SSO support are baseline requirements, not optional integrations. Communications platforms that treat security as an add-on create compliance risk in environments where access controls and audit trails are mandatory by design. **Accountability.** Can the platform generate a documented record, by employee, of which communications were received and acknowledged? In regulated industries where procedures change frequently, that audit trail is what determines whether the platform is operationally viable — not just convenient. **Adoption evidence from comparable deployments.** The OU Health and PetSmart benchmarks are production figures from large, distributed organizations. They set a realistic baseline for what adoption looks like when a platform is designed for frontline access rather than adapted for it after the fact. For organizations conducting a formal vendor evaluation, the [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independently produced comparison data across employee experience platforms — covering compliance posture, workforce type support, and total cost of ownership. It is a practical reference for building an evaluation framework that extends beyond vendor-supplied feature comparisons. ## What changes when every employee is reachable The gap between a communication sent and a communication received is where most internal programs lose value. A safety alert that reached headquarters but not the distribution center team is not a communication problem — it is a coverage architecture problem. The platform choice determines whether that gap exists. When MangoApps Posts replaces email as the primary channel for frontline communication, three things shift. Safety updates reach field workers at the same time they reach headquarters staff, with documented confirmation rather than a sent-record that tells you nothing about receipt. Compliance acknowledgments generate automatically through the platform, without a separate tracking process. Recognition and engagement communications reach frontline teams that traditional tools had structurally excluded from company-wide programs. Organizations that get this right do not just solve a communication problem. They build the infrastructure that makes every subsequent initiative — compliance training, policy rollouts, leadership messaging, recognition programs — consistently reachable by the employees who need it most. For dispersed, shift-based workforces where most of the workforce has never had a company email address, that reachability is not a feature improvement. It is the foundation. --- # The Importance of an Employee Text Alert System **Author:** Justina Kolb **Published:** 2023-10-19 **Category:** employee-app As an employer, one of your top priorities is ensuring the safety and well-being of your employees. No matter the size of your team, having an employee text alert system in place is crucial. Companies need to be able to stay in constant contact with their employees, customers, and partners – regardless of where they […] # The Importance of an Employee Text Alert System When an emergency happens at a distribution center at 3 a.m., the question isn't whether a message was sent. It's whether anyone received it — and whether anyone can prove they did. For the 80% of the global workforce that is deskless, that distinction matters more than any feature list in a vendor brochure. Email-based alert systems were built for office workers with desktop access and consistent connectivity. Per Gartner's 2023 Digital Worker Survey, 47% of workers struggle to find necessary information at least half the time — a failure rate that is inconvenient in normal operations and dangerous in an emergency. For frontline staff in retail, manufacturing, logistics, and [healthcare](/industries/healthcare) who may not have corporate email addresses at all, that gap is structural, not behavioral. The system was never designed to reach them. An employee text alert system fixes the infrastructure problem. It is not a better-formatted email. It is a delivery mechanism that reaches workers through the channels they actually have open — push notifications, SMS, and in-app alerts — with confirmation that the message landed. ## Why email fails frontline workers in a crisis The standard enterprise alert workflow when something goes wrong: draft an email, address it to the relevant distribution list, and wait for responses that may or may not arrive. Each step carries a failure mode. Distribution lists go stale as employees turn over. Email inboxes are checked intermittently on mobile devices. An email "delivered" count tells you nothing about whether anyone read it. For organizations with a large hourly or deskless workforce, the structural mismatch is even more acute. Many frontline employees do not have corporate email addresses. Reaching them via phone individually is time-consuming and error-prone at scale. And for field crews in low-connectivity environments — a manufacturing floor with spotty WiFi, a remote construction site — even push notifications can fail silently. The result is a scenario that is common and underappreciated: a manager has sent an alert, believes the workforce is informed, and proceeds accordingly. Employees who never received the message make decisions based on outdated information. The alert system created a false assurance of reach — and that false assurance is where real risk lives. ## The three capabilities that close the gap between sent and received An effective employee text alert system resolves the sent-vs-received gap through three specific capabilities that are easy to describe in a features list but difficult to find well-implemented in practice. **Multi-channel simultaneous delivery** means a single alert dispatch reaches every employee through push notification, SMS, and in-app message at the same time. This isn't redundancy for its own sake — different workers have different primary channels open depending on their device, role, and connectivity at the moment the alert fires. A warehouse associate on a shared tablet sees the in-app alert. A driver with a personal phone gets the SMS. A manager with a corporate device gets all three. A system that requires separate sends per channel, or that treats SMS as an add-on, reintroduces the same fragmentation it's supposed to solve. **Acknowledgment tracking** is the capability that most differentiates a purpose-built alert system from a group SMS thread. When an employee receives a critical alert and confirms they've seen it, the sending manager sees a real-time list of who has acknowledged and who hasn't. This does two things that matter operationally: it focuses follow-up outreach only on unconfirmed employees rather than the whole workforce, and it creates an auditable record for compliance and after-action review. Without acknowledgment tracking, "95% of our staff received the alert" is an estimate. With it, it's a verified count with timestamps. **Offline and low-connectivity delivery** ensures alerts queue and deliver when a device reconnects, rather than silently failing when connectivity drops. This is the feature most frequently omitted from alert system evaluations because it rarely surfaces in a demo — it surfaces in production, at the worst possible moment. Field crews, remote-site workers, and employees in facilities with poor indoor signal need queued delivery as a baseline requirement, not a premium add-on. ## The business case: what inadequate alerting actually costs A [frontline employee communications](/solutions/employee-communications) platform is typically evaluated on capability. The more compelling frame is the cost of getting it wrong. Replacing a single frontline employee costs between $4,400 and $15,000 — a range that accounts for recruiting, onboarding, and the productivity gap during ramp-up. Organizations that replace scattered emergency communication channels with a single real-time hub have seen frontline employee turnover reduce by 26%, per a Go North West case study published by Blink. At a 500-person frontline workforce with 30% annual turnover, that reduction represents roughly 39 fewer replacement cycles per year. At the low end of the cost range, that is $172,000 in avoided hiring and onboarding costs — before productivity losses during open roles are counted. Per McKinsey research, 89% of frontline workers say they will stay with their companies if leaders demonstrate that they listen to their feedback. Consistent, two-way alert communication — where employees can acknowledge receipt, flag issues, and respond rather than simply receive — is one of the most operationally direct ways to demonstrate that responsiveness at scale. An alert system that works in one direction only addresses the safety need. One that enables a response loop addresses the engagement need simultaneously. Per [Gallup's 2026 research on global workforce engagement](/articles/gallup-2026-state-of-the-global-workplace), information disconnection compounds over time. Workers who cannot find what they need disengage; workers who disengage leave. A text alert system with acknowledgment tracking and two-way messaging is infrastructure intervention with a direct mechanism connecting to both safety and retention outcomes. ## What to look for when evaluating employee text alert systems After understanding why text alerts matter, the operational question is: what should I actually look for? These are the criteria that separate systems worth deploying from systems that create new problems. **Multi-channel delivery in a single send.** Push notification, SMS, and in-app message should fire simultaneously from one dispatch action. Any system that requires separate sends per channel, or charges separately for SMS volume without transparent per-seat pricing, creates operational overhead and budget unpredictability. **Read receipts and acknowledgment confirmation.** Delivery receipts confirm a message reached a device. Acknowledgment confirmation tells you a person read and confirmed it. This is the operational difference between "we sent the alert" and "we know who has received it." Prioritize systems that surface acknowledgment status in real-time and allow targeted follow-up to unconfirmed employees. **Segmentation by location, department, shift, or role.** Not every alert is relevant to every employee. A system that can only broadcast to the entire workforce will either produce alert fatigue through over-notification, or require manual list management that creates the same staleness problem as email distribution lists. Dynamic segmentation that mirrors your workforce's actual structure is a baseline requirement. **Offline and low-connectivity support.** Queued delivery for workers in poor-signal environments is a requirement for any organization with field crews, remote sites, or facilities with inconsistent wireless coverage. Confirm with vendors whether alerts queue and deliver on reconnect, and test this specifically in your environment before committing. **Integration with your emergency response plan and SOP operations documentation.** A standalone alert system that lives outside the tools employees use daily creates a parallel process with its own adoption challenge. The most effective deployments integrate alert capability into the platform employees are already in — reducing the distance between receiving an alert and taking the required action. **Adoption benchmarks from comparable deployments.** 90% frontline adoption within the first six months is achievable with a properly deployed mobile alert platform. Ask vendors for documented adoption data from deployments at your workforce size and in your industry before committing. A system with strong features and weak adoption solves nothing. ## Best practices that determine whether alerts actually get read The system matters. So does how you use it. Keep alerts short and specific. A 300-word alert is an email. A text alert should deliver the critical fact — what happened, where, what employees should do — in under 100 words. Save background context for follow-up communications once the immediate action is clear. Segment before you send. If a power outage affects Building C, don't alert the entire campus. Employees who regularly receive alerts that don't apply to them learn to treat them as noise. Segmentation by location or shift isn't just an operational nicety — it protects the credibility of your alert channel for the moments when that credibility is most needed. Enable two-way communication. Allowing employees to acknowledge receipt, confirm they're safe, or ask a clarifying question closes the loop operationally and signals to employees that their response is wanted. Two-way capability transforms an alert tool into a communication tool. Conduct regular drills. Employee communications training for alert scenarios — including tabletop exercises where managers practice sending segmented alerts and employees practice acknowledging them — surfaces gaps before an actual emergency does. Test offline delivery behavior specifically, not just the general flow in a fully-connected environment. Keep contact and segmentation data current. Integrate employee data management with your alert system so that offboarding automatically removes employees from active alert groups. A fast alert system sending to departed employees is worse than no alert system, because it inflates your "delivered" count while reducing your actual reach. ## What an effective alert system delivers An employee text alert system with acknowledgment tracking, multi-channel delivery, offline support, and clean segmentation delivers three things simultaneously: employee safety, demonstrable compliance, and a retention mechanism that compounds over time. The safety case is self-evident. The compliance case is underappreciated: acknowledgment-tracked alerts produce an auditable record of who received what and when, which matters for regulated industries with incident reporting requirements. The retention case is the one most organizations don't price into their evaluation — reducing frontline turnover by a fraction of the 26% benchmark achieved through unified real-time communication platforms represents a return that can exceed platform cost within the first year at scale. The choice is not between an alert system and no alert system. Most organizations already send alerts through some combination of email, phone trees, and group SMS. The real choice is between a system that tells you a message was sent and one that tells you it was received. For frontline workers who aren't sitting at a desk when an emergency happens, that distinction is the entire point. For organizations evaluating where employee alert capability fits into a broader operational technology stack, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the criteria frontline operations leaders are applying to communication and alert platforms in 2026. --- # Tips for Creating an Effective Employee Advocacy Strategy **Author:** Justina Kolb **Published:** 2023-10-19 **Category:** intranet In today’s ever-evolving digital landscape, social media has become a cornerstone of any successful marketing strategy. However, have you ever considered harnessing the potential of social media engagement from within your own organization? By utilizing your company’s compelling and diverse internal content, you can ignite a powerful employee advocacy social media strategy. This approach won’t […] # Tips for Creating an Effective Employee Advocacy Strategy Most employee advocacy programs solve the wrong problem. Organizations spend months curating shareable content, drafting social media guidelines, and building recognition programs — then measure results among the small fraction of the workforce with a corporate email address and a LinkedIn profile they check during work hours. Per Emergence Capital, 80% of the global workforce is deskless — working in retail stores, distribution centers, clinics, hotels, and construction sites. These workers are often the most visible brand representatives in the eyes of customers. They're also the group most advocacy programs exclude by default, not by intent, but by architecture: a program that requires a corporate email login, a company device, or access to the intranet during business hours is structurally inaccessible to frontline workers before they ever hear about it. The result is an advocacy program that works for headquarters and leaves most of the workforce out. Fixing that isn't a content problem or a communications problem — it's an access and infrastructure problem. It's the dimension where most advocacy programs either improve or plateau. ## Why the standard approach leaves most of your workforce behind Per Social Edge Consulting, 91% of organizations operate an intranet, but nearly a third of employees never log in. Per SWOOP Analytics, average daily intranet usage sits at six minutes. Those numbers don't describe a content problem. They describe an access problem: the infrastructure assumes all employees have a managed device, a corporate credential, and desk time to spare. The 80% who don't simply don't show up in the engagement data. Per Social Edge Consulting, only 13% of employees use an intranet daily. When your advocacy program sits on top of this infrastructure — pushing shareable content through channels that most employees can't access — the outcome is predictable: enthusiastic participation from the same small group of desk-based employees, and near-zero involvement among frontline workers who interact with customers every day. The missed opportunity is significant. A retail associate who posts a genuine reaction to a product launch reaches a personal network that a corporate social account can't replicate. A warehouse worker who shares a company milestone carries credibility that a brand broadcast doesn't. Per IDC, employees spend 2.5 hours per day searching for information — time that compounds across teams when the right content doesn't reach the right people at the right moment. When advocacy programs exclude the majority workforce, the organic reach those workers could generate stays locked behind an access barrier that better content alone can't overcome. ## The infrastructure assumption that breaks most programs The obstacle to employee advocacy is almost never employee willingness. Most workers will share company content if the process is simple and the content feels worth sharing. The obstacle is almost always infrastructure: the advocacy tool requires a desktop login, the content library lives inside the intranet, or the sharing workflow assumes the employee is sitting at a computer during business hours. Frontline employees live on a personal smartphone. An advocacy program that doesn't meet them there — through a mobile-first experience requiring neither a corporate email nor a VPN connection — is asking 80% of the workforce to change how they operate just to share a LinkedIn post. The workers who adapt are, almost by definition, already the most engaged employees who would have advocated regardless. The rest opt out silently. OU Health achieved 87% workforce engagement within months of launching a branded, mobile-first employee communications app, per MangoApps case study data. That outcome didn't come from better content or a stronger recognition program. It came from removing the access barrier: clinical staff, technicians, and support workers — the majority of a health system's payroll — could participate without a corporate credential, on a personal device. The advocacy infrastructure met them where they were. The practical implication is straightforward: the first design decision in any advocacy program isn't what content to share or how to reward advocates. It's whether the infrastructure is physically accessible to the full workforce. If your program requires a corporate email address, an estimated 80% of your workforce is excluded before the first piece of content goes out. ## What a full-workforce advocacy strategy requires Getting the access layer right comes first. The rest of the program — content strategy, recognition, guidelines — follows. **Mobile-first access without corporate credentials.** Before selecting content or defining advocacy goals, confirm that your delivery mechanism works on a personal smartphone without a corporate login. A branded employee app that uses a personal phone number or personal email address instead of a corporate account is the infrastructure layer that makes frontline advocacy possible. The content strategy should follow the infrastructure decision, not precede it. **Content segmented by role, not generic.** A nurse advocating for a health system sounds different from a hospital administrator doing the same thing. A warehouse associate promoting a logistics employer's culture reaches a different audience than a supply chain manager. Effective programs give employees content that fits their context and their network — not one-size-fits-all posts drafted for a generic corporate audience. AI-personalized content feeds that surface relevant material by role, location, and team reduce the friction of deciding what to share, which is often the step where employees drop out of participation. **Clear guidelines, lightly enforced.** Employees share more when they know what's appropriate, not when they fear getting it wrong. Guidelines should answer three questions: what topics are encouraged, what's off-limits, and what to do when something sensitive comes up. Employees who understand those parameters participate more confidently. Heavy approval workflows that require manager sign-off on every share kill participation faster than almost any other design decision. **Recognition built into the program mechanics.** Recognition that celebrates top advocates — through internal visibility, peer acknowledgment, or meaningful rewards — drives sustained participation more effectively than one-time incentives. The metrics worth recognizing aren't limited to social media vanity stats. Content that helps colleagues find information faster has real operational value even when it generates no external engagement. Programs that track internal amplification alongside external sharing capture more of the actual value being created. ## Measuring whether the program is actually reaching everyone An advocacy program without measurement is a campaign, not a strategy. The metrics worth tracking fall into two categories: reach metrics that confirm the program is generating external visibility, and participation metrics that confirm whether the full workforce is actually involved. Reach metrics are the standard ones: total impressions generated by employee shares, click-through rates on shared content, follower growth on channels where advocacy concentrates. These confirm the program is producing external signal. Participation metrics are where most programs have a gap: what percentage of eligible employees have shared at least once in the past 30 days, and how that breaks down between desk workers and frontline workers. Participation rate by workforce segment is the metric most advocacy programs don't track — and the one that reveals most quickly whether the program is reaching the full workforce or just the usual engaged minority. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how organizations are rethinking participation measurement as frontline and remote employees move to the center of employee experience strategy, not the edge. ## The retention case most programs never make Advocacy programs are typically justified as marketing investments, framed around brand reach and awareness. That frame leaves out the retention component — and in deskless industries, retention is where the financial case becomes most significant. Replacing a single frontline employee costs between $4,400 and $15,000, per industry research cited in MangoApps' mobile product documentation. Frontline turnover rates exceed 60% in some industries. An advocacy program that makes frontline workers feel like visible participants in the company's story — rather than invisible contributors excluded from the platforms headquarters relies on — has a documented relationship with reduced churn. Connection to organizational culture is among the most consistent predictors of frontline retention. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), the gap between workers who feel connected to their organization's story and those who don't shows up consistently in attrition data. [Employee engagement](/solutions/employee-engagement) infrastructure — including well-designed advocacy programs — is one of the mechanisms that closes that gap, when it's built for the full workforce rather than the fraction already closest to headquarters. ## The order that makes programs succeed or stall The organizations generating the most durable results from employee advocacy have made the same structural bet: they invested in making the program accessible to frontline and deskless workers first, then layered content strategy and recognition programs on top of that foundation. Organizations that built the content strategy first and the access infrastructure second plateaued at desk-worker participation rates — and declared the program successful by the wrong benchmark. If 80% of your employees are frontline and deskless, an advocacy program that reaches only your desk workers is reaching 20% of your most visible brand representatives. The question isn't whether advocacy programs work. They do — when they're built for the full workforce, not the subset that was easiest to reach. The question is whether the infrastructure decision comes before or after the content strategy. Organizations that get the order right find the content strategy becomes significantly easier once the audience is actually there. --- # Benefits of Internal Email Tracking **Author:** Justina Kolb **Published:** 2023-10-19 **Category:** intranet Effective internal email tracking is crucial for the success of any internal communications team. Without it, there’s no way for them to know whether their content is being read or seen. Email is an essential part of any workplace, and with so many different sources of communication, it can be difficult to keep track of […] # Benefits of Internal Email Tracking For internal communications teams, sending a message is the easy part. Knowing whether that message reached the people who needed it—and whether they acted on it—is where most teams operate in the dark. According to IDC, employees spend an average of 2.5 hours per day searching for information. Separately, Social Edge Consulting found that nearly a third of employees never log into the intranet, even at organizations where 91% already operate one. If your communication channel isn't tracked, there is no way to know whether you're contributing to that gap or closing it. Internal email tracking gives communications teams the data layer they need to move from hoping messages land to knowing they do. This guide covers the core benefits of internal email tracking, the metrics that matter most, and the gaps that email-only measurement still leaves open. ## What internal email tracking does Internal email tracking collects behavioral signals from the emails you send to employees: who opened the message, who clicked a link, who ignored it, and who received it but took no visible action. These signals exist beneath the surface of any email program—the question is whether your tooling captures and surfaces them in ways your communications team can act on. The distinction between external and internal email tracking matters. External campaigns measure prospective customers; internal campaigns measure your own workforce. The intent is different, the audience is captive, and the stakes are often higher. A missed policy update or safety notice isn't a lost lead—it's a compliance failure or a preventable incident. ## Why the data gap costs more than organizations realize Organizations without tracking typically discover communication failures after the fact: a policy deadline was missed, a training wasn't completed, a safety update didn't reach the right team. By then, the cost is already incurred. The replacement cost for a single frontline employee runs between $4,400 and $15,000 in recruiting and training expenses. Poor communication—where employees feel out of the loop or unsupported—is consistently cited as a leading driver of voluntary turnover. Tracking engagement doesn't prevent disengagement on its own, but it provides the early signal that something isn't working before the problem compounds. Social Edge Consulting found that just 13% of employees use their intranet daily. That gap between availability and actual use is partly a communication problem: employees don't know what's there, or they don't trust that it's current. Email tracking provides the feedback loop that helps communications teams course-correct before the gap widens. ## The 9 core benefits ### 1. Performance measurement Tracking gives communications teams concrete numbers: open rates, click-through rates, and engagement trends over time. These numbers replace guesswork with evidence. A message with a 20% open rate and one with a 40% open rate require different responses—without tracking, both look identical from the inside. ### 2. Audience engagement analysis Open and click rates reveal which messages resonate and which don't. When a weekly update consistently outperforms a departmental announcement on the same topic, that pattern reflects something real about employee priorities and reading habits. Acting on those patterns is what separates communications teams that improve over time from those that repeat the same formats indefinitely. ### 3. Content optimization Tracking data surfaces which content formats, subject lines, and delivery times drive the most engagement. Teams that A/B test subject lines and review click patterns across content types build a systematic feedback loop. Over time, decisions about tone, format, and length become evidence-based rather than stylistic preferences. ### 4. Targeted messaging Engagement history lets communications teams segment their audience by behavior, not just by role or department. Employees who consistently open communications about benefits can receive more detailed follow-ups. Employees who rarely open anything in a particular channel may be better reached through a different one. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents how organizations are restructuring their channel strategies around exactly this kind of behavioral data. ### 5. Timely follow-ups Not everyone opens an email on the first send. Tracking lets teams identify non-openers and send targeted reminders before deadlines pass—whether the deadline is a compliance acknowledgment, a benefits enrollment window, or a time-sensitive policy update. This approach is more effective than blanket re-sends to the entire audience. ### 6. Feedback loops Tracking doesn't replace surveys, but it adds a behavioral layer that survey data misses. An employee who opens an announcement three times but never clicks through to the linked resource is showing you something a post-send survey never would. Combining tracking data with explicit feedback from polls and acknowledgment features gives a fuller picture of how communications are actually landing. ### 7. Compliance and accountability For regulated industries—healthcare, financial services, government contracting—proof that employees received and engaged with required communications matters beyond internal reporting. Tracking provides an audit trail: who received the message, when, and whether they opened it. This record is relevant wherever organizations must demonstrate due diligence around information delivery. ### 8. Return on investment Communications teams that want to make a credible case for headcount, tooling, or budget need data that connects their work to outcomes. Engagement rates, trend improvements, and correlation with downstream metrics—training completion, policy adherence, incident rates—provide that evidence. Without tracking, communications investment is invisible in the budget conversation. ### 9. Continuous improvement The teams that improve most consistently treat tracking as a discipline, not a one-time check. Testing subject lines, varying content length, shifting send times, and reviewing results after each campaign creates a systematic improvement loop. [Gallup's 2026 State of the Global Workplace research](/articles/gallup-2026-state-of-the-global-workplace) found persistent employee disengagement across industries—the organizations making measurable progress are the ones treating communications as a trackable function, not a broadcast channel. ## What metrics actually matter Not all tracking data is equally useful. The metrics internal communications teams find most actionable: **Open rate** is the most widely tracked metric and the least reliable in isolation. An open confirms the email was received and triggered enough curiosity to open. It says nothing about whether the content was read, understood, or acted upon. Treat it as a reach metric, not an engagement metric. **Click-through rate** is a stronger signal of genuine engagement. A reader who clicked through to a policy document, a linked resource, or an acknowledgment form took a deliberate action. Click rates by content type reveal what employees find worth their time. **Non-opener rate by department or location** is often the most operationally useful view. When one site or department consistently shows low open rates while others don't, the problem is usually channel fit or timing, not content quality. That insight drives a different intervention than a company-wide content issue would. **Time-to-open** matters for time-sensitive communications. If employees in a particular shift open messages hours after delivery, the send schedule may be wrong for that audience segment. **Unsubscribe or opt-out rate** is a lagging indicator of volume, relevance, or channel problems. A single spike is noise; a trend over multiple campaigns is a signal worth investigating. ## The gap email tracking doesn't fill According to Emergence Capital, 80% of the global workforce is deskless. For retail associates, field technicians, warehouse operators, and healthcare workers, a corporate email address is often unavailable or simply irrelevant to how they work. Standard internal email tracking measures only the employees it can reach by email—which means it systematically undercounts engagement in the organizations where frontline workers are the majority. This isn't a reason to avoid email tracking. It's a reason to treat it as one signal within a broader [employee communications](/solutions/employee-communications) measurement approach. Organizations with significant deskless populations need to extend their analytics to the channels those workers actually use: push notifications, mobile app engagement, and in-app acknowledgment workflows. A communications team reporting strong email engagement numbers while 60% of the workforce never saw the message has a measurement gap, not a success story. SWOOP Analytics found that employees spend an average of six minutes per day actively using intranet tools. Email remains a primary channel for formal internal communications—but mobile apps, push notifications, and acknowledgment workflows together form the fuller picture. Treating email tracking as the complete view leads to systematically overcounting reach in the populations that often need communications most. ## How to act on what you find Tracking data creates obligations. Measuring and ignoring the results produces the same outcome as never measuring at all. The value comes from closing the loop. A practical cadence: review open and click rates weekly for time-sensitive campaigns; review content performance trends monthly; review channel-level patterns quarterly to inform planning decisions. Build in a step to flag anomalies—a department with consistently low engagement on compliance communications is a risk item, not a data point to smooth over. For teams building this discipline for the first time, establishing a baseline before making changes is worth the deliberate pace. Without a baseline, improvements are invisible. With one, even incremental gains become evidence you can point to. The [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study illustrates how consistent measurement transforms the internal communications function from reactive to anticipatory—each cycle's data makes the next campaign more precise. ## Knowing when you're actually reaching people Internal email tracking is a means, not an end. Communications that reach the employees who need them, when they need them, in forms they can act on—that's the actual goal. Tracking is the mechanism for knowing whether you're getting there, and for identifying the specific gaps when you're not. The floor is straightforward: know whether your messages are reaching people. From there, every additional layer—segmentation, behavioral analysis, multi-channel mix optimization—compounds over time. Organizations that establish that floor early accumulate an evidence base that makes each subsequent communications decision more defensible and more effective. --- # Company Newsletter Ideas and Editable Newsletter Templates **Author:** Justina Kolb **Published:** 2023-10-19 **Category:** intranet Creating employee newsletters can be a daunting task, especially if you’re starting from scratch every time. An internal newsletter is an integral part of any business or organization. It’s a way to keep members of your team up-to-date on news, events, and changes happening within your company. However, if information in a newsletter becomes irrelevant […] # Company Newsletter Ideas and Editable Newsletter Templates Most internal newsletters are designed for the inbox — and that design assumption is why they miss most of the people who work for you. Per Emergence Capital, 80% of the global workforce is deskless. Warehouse associates, retail floor staff, nurses, field service technicians, distribution center workers: they don't have corporate email addresses, they're not working from desktop computers, and they're not checking intranet portals between tasks. Yet the standard internal newsletter format — an HTML email blast or a portal-hosted post — is built for the 20% of the workforce that already has the most communication access. Per IDC, employees spend 2.5 hours per day searching for information they need to do their jobs. Much of that friction comes from communications that arrive through the wrong channel, or don't arrive at all. Company newsletters are one of the few formats designed to proactively surface important information to employees who wouldn't seek it out on their own. But they can only do that if they reach people where those people actually are — not where the communications team assumed they would be. This article covers what separates internal newsletter programs that drive measurable engagement from ones that exist primarily to satisfy a communications calendar, and which newsletter topics hold up across both desk and frontline contexts. ## Why most employee newsletters fail before they're opened The problem usually isn't content quality. Most internal communications teams produce reasonably well-written newsletters. The problem is delivery architecture. Per Social Edge Consulting, 91% of organizations operate an intranet — but nearly a third of employees never log in, and only 13% use it daily. Per SWOOP Analytics, the average daily time spent using intranet tools is six minutes across the entire user population, including those who do log in. When a newsletter lives behind a portal that most employees visit for six minutes a day or less, its reach is structurally capped before a single person clicks open. For frontline workers, the gap is wider and more persistent. A distribution center worker finishing a pallet run, a retail associate between customers, or a home health aide arriving at a morning appointment isn't going to pause to open a browser, authenticate through a VPN, and navigate to a company intranet. The physical separation from a desk is a separation from the communication channel — and most newsletter programs treat that separation as a personal preference rather than what it is: a structural barrier built into the delivery format. The assumption that newsletters travel via corporate email or desktop portal only holds for the subset of employees who work that way. For everyone else, that assumption means the newsletter doesn't arrive. At scale, a company with 1,000 frontline workers and a desktop-only newsletter program isn't running a company-wide newsletter. It's running a newsletter for 200 people. Mobile-first delivery addresses this at the source. Newsletters pushed through a branded mobile app — accessible without VPN, without a corporate email address, and without requiring employees to navigate to them — reach the workforce segment that a desktop-only approach structurally misses. The delivery mechanism is part of the strategy. No amount of good content compensates for a channel 80% of employees can't easily access. Organizations building [employee communications](/solutions/employee-communications) infrastructure for a distributed or frontline-heavy workforce need to resolve delivery architecture before optimizing content. ## What high-engagement newsletter programs actually produce Internal newsletters that sustain readership over time share structural characteristics that content-focused programs typically overlook. **Segmentation by role, location, and language.** A company-wide blast addresses no one specifically. When content is sorted by department, shift schedule, region, and language, employees are more likely to read because the information is actually relevant to their day. A warehouse associate working an early shift in a Spanish-speaking market needs a different newsletter than a regional finance director in the corporate office. Accurate segmentation isn't a sophistication layer — it's the mechanism that turns a communications blast into a useful communication. **Regularity over comprehensiveness.** Newsletters that arrive inconsistently train employees to treat them as optional. A shorter newsletter published on a predictable cadence outperforms a comprehensive one published irregularly. Editable newsletter templates make consistency achievable by reducing per-issue production effort, so the cadence holds even when bandwidth is low. **Closed-loop measurement.** Per the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook), operations leaders are increasingly tracking open rates, read depth, and downstream actions — survey completions, event registrations, policy acknowledgments — rather than treating distribution numbers as a proxy for impact. A newsletter that reaches 40% of employees but produces no behavioral change is a different problem than one that reaches 80% and drives measurable follow-through. **Accessibility without friction.** When a newsletter requires a VPN connection, a password reset, or navigation through an unfamiliar portal, employees who might otherwise read it skip it instead. Reducing access friction — particularly for workers without corporate-issued devices — directly expands the effective audience for every issue. ## Company newsletter ideas that work across desk and frontline The following topics perform in both desk-heavy and frontline-heavy organizations. They transfer across delivery formats — corporate email, mobile app notification, or intranet post — without requiring a format-specific rewrite. **Employee spotlights.** A profile of a frontline worker — their role, how a recent shift went, a challenge they navigated — builds cross-functional connection more effectively than an executive announcement. Frontline employees are frequently invisible in company-wide communication; featuring them signals that leadership has real visibility into the work happening at the operational level. **Company announcements.** Leadership transitions, benefit changes, expansion news, policy updates. These belong in a newsletter format because employees need to know the information regardless of how often they check the portal. Newsletters push; portals require pull. **Department updates.** Short project summaries from different teams — what shipped, what changed, what's coming next quarter. Organizational transparency reduces the ambient uncertainty and rumor that fill information vacuums in large, distributed organizations. **Training and development opportunities.** Newsletters are one of the most effective channels for surfacing learning programs because they reach employees who wouldn't navigate to a training catalog unprompted. Including role-relevant certifications or compliance deadlines in a newsletter increases actual utilization, not just awareness that the programs exist. **Customer success stories.** A customer testimonial tied to the employees who delivered it closes the loop between frontline effort and business outcome. For customer-facing roles, this is consistently one of the highest-engagement newsletter formats — employees see their own work reflected in customer outcomes, which connects effort to purpose. **Safety and compliance updates.** For industrial, healthcare, or field-service workforces, timely safety information is both a legal priority and an operational one. Safety newsletters should arrive before a shift begins, formatted for a mobile screen that can be read in under two minutes. **Employee wellness.** Benefit reminders, mental health resources, schedule flexibility options. This category performs better when it's specific and timely — reminding employees about open enrollment before the deadline — rather than evergreen tips that employees have seen before. **Recognition and milestones.** Work anniversaries, peer nominations, team achievements. Recognition communicated in a newsletter has higher retention effects than private acknowledgment because it's visible to the broader organization, turning individual moments into shared culture. **Industry and competitive news.** Brief summaries of what's shifting in your sector. Customer-facing employees who understand the competitive context serve customers more effectively. This format also builds organizational awareness that makes employees feel connected to where the business is heading rather than executing tasks without context. **Upcoming events and operational deadlines.** Shift schedules, compliance deadlines, company events, product launches. This is the newsletter category with the highest immediate utility for frontline workers, who often lack visibility into the broader organizational calendar. **Diversity and inclusion updates.** Highlighting DEI initiatives in a newsletter keeps these efforts visible year-round rather than concentrated around specific awareness months. **Behind-the-scenes features.** A glimpse into a department or project most employees don't interact with. This builds organizational understanding that makes large companies feel less siloed, and it's a low-production-cost format that can be produced with a short interview. ## Making delivery reach everyone None of these topic ideas generate value if the newsletter doesn't reach its intended audience. The structural constraint for most organizations isn't content quality — it's delivery format. A mobile-first [employee app](/solutions/employee-app) resolves the delivery problem by meeting employees where they already are: on their phones, during the brief windows between tasks. Newsletters formatted for mobile, distributed as app notifications, and accessible without VPN or corporate email remove the friction that structurally disconnects deskless workers from internal communications. Role- and location-based targeting replaces the all-hands blast with content that's relevant to each recipient rather than equally irrelevant to everyone. The production side is addressed by editable templates. A communications team that maintains templates for recurring newsletter types — announcements, employee spotlights, safety updates, recognition — reduces per-issue production time and maintains visual consistency without requiring design work each cycle. This is what makes a 52-issue annual cadence achievable for a team without 52 weeks of design bandwidth. Per Gallup's 2026 research analyzed in this [overview of global workplace trends](/articles/gallup-2026-state-of-the-global-workplace), organizations with the strongest employee engagement scores aren't running the most sophisticated communications programs. They're running consistent ones — where employees know what to expect, when to expect it, and where to find it. ## What the reach gap actually costs The gap between employees who receive internal communications and those who don't shows up in measurable places: lower safety compliance in frontline environments, higher turnover among workers who feel out of the loop, and slower adoption of policy and benefit changes among populations that receive information late or not at all. Most of this isn't a content problem. It's a reach problem. The solution is infrastructure: delivery mechanisms that work for employees who don't sit at desks, segmentation that makes content relevant to each recipient, and production systems that support consistency without requiring extraordinary effort every cycle. Per Social Edge Consulting, nearly a third of employees never log in to their organization's intranet. For those employees, a newsletter that only exists there has never reached them. The delivery channel isn't a secondary consideration — it determines who the newsletter actually serves. A newsletter program built on the assumption that every employee has a corporate inbox and a desktop portal won't reach the majority of employees in most organizations. Newsletter programs that sustain readership over time were built with the assumption that the full workforce needs to receive them. That assumption changes the delivery format, the segmentation approach, and the tooling required to maintain the cadence. The content decisions — which topics to cover, how often to publish, which editable templates to maintain — come after the delivery architecture is in place. --- # Elevating Employee Engagement With New Enhancements to MangoApps Survey Module **Author:** MangoApps **Published:** 2023-10-12 **Category:** press-release New features empower companies with adaptive surveys, advanced rule builder, and expanded question types. # How MangoApps Surveys Reaches Every Employee — Not Just the Ones With a Desk The typical employee engagement survey tells you how engaged your already-engaged employees are. The 80% of the global workforce that is deskless — factory floor workers, retail associates, field technicians, healthcare aides — rarely appear in the results, per Emergence Capital. They don't have a company email, don't log into the intranet, and often don't sit at a location where a browser notification reaches them during a shift. This isn't primarily a participation problem. It's an architecture problem. The survey tools most HR departments use were built for knowledge workers. When you extend that architecture to a 500-person distribution center or a 200-bed hospital, the data you collect accurately represents a small portion of the workforce and goes silent on everyone else. Three recent additions to the MangoApps Survey module address this gap directly: a Rule Builder for conditional question logic, expanded question types including Likert scale and NPS, and acknowledgement tracking for confirmed delivery. Together, they change who a survey program can reach — and what it can actually diagnose. ## The architecture problem behind engagement measurement gaps Gallup's research finds that only 32% of employees feel genuinely engaged at work. That number has barely moved in a decade. The issue isn't that organizations don't survey — most do. The problem is structural: the architecture of most survey programs systematically excludes the employees whose data would matter most. Per Social Edge Consulting, only 13% of employees use an intranet daily, and nearly a third never log in at all. SWOOP Analytics benchmarks average daily intranet use at six minutes. A survey deployed inside a low-traffic portal reaches only the portion of the workforce that already checks in regularly — skewing the sample toward desk-based, already-engaged employees. For organizations where the majority of staff are frontline workers, this creates a measurement bias that compounds over time. The employees who interact most directly with customers and operations are systematically absent from the data HR uses to set engagement strategy, prioritize programs, and make retention investments. The [Gallup 2026 State of the Global Workplace analysis](/articles/gallup-2026-state-of-the-global-workplace) documents the downstream consequences of this exclusion — including the correlation between frontline disengagement and customer satisfaction outcomes that organizations consistently underestimate when evaluating whether their survey programs are working. ## Argument 1: Conditional logic turns a survey into a diagnostic instrument The Rule Builder allows administrators to define logic rules that route respondents to different pages or questions based on earlier answers. The practical effect: a single survey behaves differently for each respondent, without requiring multiple survey versions or manual segmentation after the fact. An employee who rates workload satisfaction as "Very dissatisfied" is automatically routed to an open-ended follow-up — "What one change would make the most difference to your experience?" — while an employee who rates it "Satisfied" skips that page entirely. The dissatisfied respondent generates root-cause data. The satisfied respondent completes the survey in 90 seconds instead of four minutes. This matters because survey length is the primary driver of frontline non-participation. Frontline employees aren't disengaged from giving feedback — they're disengaged from long surveys deployed through channels that don't fit how they work. A conditionally adaptive survey that adjusts to prior answers reduces time burden for most participants while generating diagnostic depth from the respondents most likely to leave. Conditional logic also extends survey function into action. An employee who flags a safety concern mid-survey can be routed to the appropriate reporting channel before they exit — not in a follow-up email that arrives after the moment has passed. Custom survey URLs allow direct distribution through push notification, team chat, or a QR code posted in a break room, removing the navigation barrier entirely for workers who don't start their shift at a browser. ## Argument 2: Question type determines what you can benchmark across cycles Most organizations survey for engagement without using the formats that produce benchmarkable data. The question type additions to MangoApps Surveys close the three gaps most likely to limit what an HR team can do with results over time. **Likert Scale** is the standard format for validated engagement instruments, including most proprietary HR benchmarking tools and validated psychometric instruments like the Maslach Burnout Inventory. Without it, engagement data cannot be compared against industry norms or trended consistently across survey cycles. A custom 1-5 satisfaction scale is not a Likert scale — the validated properties only hold for specific phrasing and response anchor formats the format defines. **NPS applied to employees** — eNPS — generates a single score that functions as a proxy for overall engagement: whether an employee would recommend the organization as a place to work. It benchmarks against published industry averages and is stable enough to track quarterly without creating survey fatigue for respondents. **Ranking questions** capture relative preference among options in a way multiple-choice cannot. When a benefits team wants to know whether employees value schedule flexibility more than additional PTO more than childcare support, ranking produces that information directly. Binary choices produce frequency data; ranking produces preference ordering, which is what resource allocation decisions actually require. The format choice matters most at scale. A manufacturing organization with 800 employees surveying quarterly needs formats that produce comparable results each cycle. Switching question formats between cycles breaks trend lines and makes it impossible to determine whether a change in scores reflects a change in sentiment or a change in measurement. Adding Likert and NPS at the module level means HR can deploy validated instruments consistently without rebuilding question logic for each survey cycle. ## Argument 3: Acknowledgement tracking closes the loop most programs leave open Sending a survey is not the same as reaching employees. Acknowledgement tracking confirms which specific employees have viewed a survey or policy update — enabling administrators to generate a targeted list of non-responders and follow up through the channel that will actually reach them. For regulated environments — healthcare, financial services, government contractors — this is a compliance requirement, not a convenience feature. Auditors ask for documentation of who received, viewed, and acknowledged a communication. Email threads don't provide that reliably. A managed platform with acknowledgement tracking produces the audit trail compliance programs require without manual recordkeeping. The application outside regulated industries is equally direct. A safety communication sent to all warehouse employees should generate a confirmed-received list within 24 hours. When it doesn't, acknowledgement tracking identifies the specific gap — not a general participation rate, but a list of names — so a shift supervisor can follow up through direct conversation or posted notice that will actually reach those individuals. The [American College of Radiology case study](/resources/case-study-american-college-radiology) covers how a distributed, specialized healthcare workforce deployed unified communication infrastructure to close exactly this gap — from broadcast announcement to confirmed receipt, at the department level. ## Why platform architecture is the leverage point The three feature additions matter individually. They matter more because of where they live. Per IDC, employees in information-intensive roles spend 2.5 hours per day searching for information they can't locate in one place. In frontline settings, that overhead maps to coordination gaps: messages that don't arrive, approvals that sit in the wrong queue, feedback that never surfaces because the tool to collect it is in a separate system from the communication channel employees actually use. MangoApps Surveys operates within the broader MangoApps platform. When a department's engagement survey reveals low scores on "I understand how my work connects to company goals," that signal sits alongside communication data, shift management records, and workforce analytics in the same environment. The survey finding doesn't require a manual handoff between systems to become an operational response. A standalone survey tool produces a report. A survey embedded in a unified platform produces an action trigger — informing which content gets prioritized, which managers are flagged for follow-up, and which programs are extended to which employee segments. For organizations evaluating whether their current survey program is generating data or generating change, the difference between those two states is structural. It isn't resolved by better question design alone. ## What outcomes indicate the structural change is working Three metrics indicate whether the feature additions are producing the intended result after deployment. **Participation rate by workforce segment.** Track response rates for frontline and desk workers separately. A sustained gap between segments after deployment indicates access configuration still needs adjustment — likely that mobile-first survey delivery hasn't been extended to all frontline job classes, or that survey notifications are still routing through desktop channels. **Conditional depth rate.** The share of respondents routed to open-ended follow-up pages by the Rule Builder. A program where fewer than 10% of respondents hit a conditional question is either reaching a highly satisfied population or the trigger thresholds are calibrated too conservatively. This metric catches logic calibration issues before an entire survey cycle produces shallow diagnostic data. **Time to visible action.** Days between survey close and an organizational response — a named policy change, a targeted communication to the relevant team, or a committed follow-up with a timeline. Gallup's research is consistent: employees who have seen feedback lead to a specific, named change at least once participate in subsequent surveys at materially higher rates. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the implementation choices that move this metric most reliably for organizations deploying structured feedback programs at scale. Organizations that treat [employee engagement](/solutions/employee-engagement) as a data-collection exercise rather than a feedback loop typically see declining participation across cycles, regardless of how much the survey technology improves. Closing the loop requires communicating what the survey found and naming what the organization is doing about it — specifically enough that the employees who responded recognize the connection. ## The employees who weren't counted before The argument for the Rule Builder, expanded question types, and acknowledgement tracking isn't primarily about better survey design. It's about who gets counted. An engagement survey that excludes 80% of the workforce — the portion that is deskless, per Emergence Capital, and unreachable through desktop-first survey tools — doesn't measure engagement. It measures the engagement of the employees most likely to already be engaged. Investing based on that data leads organizations toward programs that serve desk workers while frontline attrition, safety gaps, and satisfaction problems go unmeasured and unaddressed. For organizations where frontline workers represent the majority of staff, the updated MangoApps Survey module doesn't change what employee engagement surveys ask. It changes who can answer — and through what channels that answer arrives. That is the operational problem the feature additions are designed to solve. --- # New MangoApps NoCode Workflow Apps Enhance Operational Efficiency **Author:** MangoApps **Published:** 2023-09-27 **Category:** press-release Seamless design, customization and deployment of powerful applications that elevate the employee experience, integrated with MangoApps existing suite of solutions. # MangoApps NoCode Workflow Apps: Build Custom Productivity Apps Without Writing Code Employees spend an average of 2.5 hours per day searching for information, per IDC. That figure understates the real cost: when the tools meant to help workers are hard to find, role-irrelevant, or accessible only during business hours at a desktop, the time lost compounds across every shift. For operations teams managing distributed workforces, the standard remedy — submit a ticket, wait for IT, deploy in six weeks — often makes the underlying problem worse. MangoApps NoCode Workflow Apps addresses this at the source. HR, operations, and IT teams can build, customize, and deploy cloud based productivity apps directly inside the MangoApps platform — without developer involvement, without ticketing systems, and without procuring separate point solutions. The apps live where employees already work: the same hub they use for communications, scheduling, and training. This article covers what NoCode Workflow Apps does, where it returns the highest value, and which workflows to build first. ## Why the deployment bottleneck is the actual problem The most common productivity problem in operational environments is not the absence of tools. It is that the tools that exist do not reach the people who need them, in formats they can actually use. Per Social Edge Consulting, only 13% of employees use an intranet daily. Nearly a third never log in at all. Per SWOOP Analytics, the average employee spends six minutes per day using intranet tools — less time than most meetings. These are not engagement failures. They are design failures: tools built for office-based, desktop-equipped workers, deployed to shift-based, mobile-first workforces across time zones and languages. The answer is not more tools. It is better-targeted tools — built faster, by the people who understand the process, and deployed in the environment employees already inhabit. ## What NoCode Workflow Apps does NoCode Workflow Apps is a drag-and-drop application builder embedded in the MangoApps platform. Non-technical managers use it to create forms, dashboards, approval chains, and data-capture screens. The apps deploy in the same environment where employees receive communications and view schedules — no separate login, no context switching. Core capabilities: - **Visual interface designer** — drag-and-drop elements to build employee-facing apps without code - **Pre-built templates** — starting points that reduce deployment time for common processes - **Automated workflow logic** — triggers, conditions, and branching rules that handle multi-step processes end-to-end - **AI-augmented building** — describe a workflow in plain language; the platform generates an initial app structure, connected to OpenAI, Gemini, Anthropic, and Azure OpenAI - **Acknowledgement tracking** — confirms which employees have reviewed a policy update and automatically triggers follow-up for those who have not, supporting compliance workflows - **Inline translation** — multilingual support embedded directly into employee-facing apps, without maintaining separately translated versions The AI-augmented building capability is the practical differentiator from earlier no-code tools. Rather than configuring logic from scratch, a manager describes a workflow — "I need a form where employees submit attendance, it routes to their direct manager for approval, and flags HR if not resolved within 24 hours" — and gets a working starting point to edit. That shifts the effort from construction to refinement. ## Where frontline workers see the clearest return Per Emergence Capital, approximately 80% of the global workforce is deskless. Factory floor workers, retail associates, healthcare aides, and field technicians cannot access desktop-first productivity programs the way office workers can. Most enterprise workflow tools were not built for them — and the operational drag from paper-based processes reflects it. NoCode Workflow Apps is designed for both audiences, but the frontline use cases have the highest return because the processes being replaced are labor-intensive, error-prone, and slow. **Attendance submissions.** Employees submit attendance through a structured form on a mobile device. Managers receive a notification and approve, flag, or escalate within the platform. The paper sign-in sheet disappears; so does the manual transcription that falls on HR. **Safety checklists and SOP operations forms.** Workers complete required pre-task checks on mobile. Completion is logged automatically. Managers see real-time completion rates across locations, replacing the lag of collecting paper at shift end. **Shift swap requests.** Requests route automatically to the right manager based on shift type, location, or role — without an email chain. For teams managing complex scheduling structures, this integrates directly with the MangoApps [shifts and schedules](/solutions/shifts-schedules) solution. **Policy acknowledgement flows.** The platform confirms which employees have seen a specific policy update and triggers follow-up for those who have not, with a logged audit trail. In regulated industries — healthcare, manufacturing, logistics — this replaces manual tracking spreadsheets with documented, timestamped compliance records. **Multilingual workflows.** For teams that span multiple languages, inline translation can be embedded directly into the app, eliminating the cost and delay of maintaining separate translated versions of the same form. In documented enterprise deployments of no-code employee experience platforms, organizations have achieved 90% frontline adoption within six months and 50% faster new-hire onboarding when mobile-accessible workflows replace paper-based processes. ## What office and knowledge worker deployments look like The frontline cases tend to have the clearest before/after contrast. But office and knowledge worker applications follow the same logic: remove the dependency on IT for process changes that business teams understand better than developers do. **Approval workflows** — for expenses, requests, and escalations — with conditional routing based on amount, department, or threshold. Configuration takes days, not sprint cycles. **Confidence and skill-assessment apps** — employees flag their confidence in specific job tasks on a recurring basis. Managers see aggregate results by team or role, surfacing training gaps before they become performance problems. **Daily mood check-ins** — a 30-second signal that tells managers whether team-level sentiment is trending before it shows up in quarterly survey results. Not a replacement for formal engagement surveys; a lightweight layer that runs between them. ## How AI-augmented building changes the economics The cost of building a workflow app has historically included developer time, QA cycles, and deployment coordination. No-code tools reduced the developer dependency but preserved the configuration burden — a manager still needed to understand form logic, conditional branching, and routing rules to build something useful. AI-augmented building changes what "no-code" actually means in practice. The manager describes the workflow; the platform generates the structure. The manager edits a working draft rather than constructing one from scratch. That shift materially reduces the hours required to go from a process problem to a deployed solution. MangoApps connects to multiple AI providers — OpenAI, Gemini, Anthropic, and Azure OpenAI — so the generation capability is not limited to a single model. For teams evaluating platforms on AI capability alongside workforce operations fit, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how organizations are consolidating AI-augmented tooling into unified employee hubs. ## Three workflows to build first Early adopters have identified three processes where replacing paper or email with automated workflow produces the most immediate operational lift. These are practical starting points for any team evaluating the feature. **1. Attendance submissions.** The highest-frequency use case — daily or per-shift. The return compounds with every cycle: manual transcription disappears, approval routing speeds up, and managers gain real-time visibility across locations. For shift-based teams, this integrates directly with scheduling and [time and attendance](/solutions/time-attendance) workflows, closing the loop between who showed up and how that feeds payroll and compliance records. **2. Safety checklist completion.** Required in most industrial and healthcare environments. Digitizing the checklist closes the compliance lag between when checks happen and when managers know they happened. Completion is logged automatically — useful for both internal reviews and regulatory documentation, without the paper collection step at the end of each shift. **3. Policy acknowledgement flows.** Regulatory or procedural updates require documented confirmation that employees received and acknowledged the change. Automated acknowledgement apps with follow-up triggers and logged completion replace the tracking spreadsheet — and extend coverage to shift workers who may not see a broadcast email until after the acknowledgement deadline. ## What "no-code" requires from a manager The practical question most operations leaders ask: can a non-technical team lead actually build this? The honest answer is that it depends on the process. Simple forms and single-step approvals are deployable in hours by any manager who understands the process they want to automate. Multi-step workflows with conditional branching — if the employee has been flagged three times, route to HR instead of the line manager — take longer and benefit from template starting points or AI-generated scaffolding. NoCode Workflow Apps is designed for managers who understand the workflow they want to automate, not for managers who want to learn software configuration. IT remains the appropriate owner for integrations, security reviews, and audit requirements. The no-code model removes IT from the build path without removing IT from oversight. ## The case for consolidating workflows into a single hub Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), employee engagement correlates directly with whether workers feel the organization is paying attention to their experience. Tools that require frontline workers to log into a desktop system during business hours communicate, implicitly, that the tooling was not built for them. Workflows deployed in a mobile-first hub — the same environment where employees receive communications, check schedules, and complete training — communicate the opposite. Each automated process reduces manager overhead, speeds up the experience for the employee doing the work, and adds to a compliance record that stands up to audit. The starting point is one workflow: whichever paper-based or email-based process creates the most friction today. The deployment path that follows — adding use cases as the team builds confidence with the builder — is more durable than standing up a separate application for each operational problem. --- # Intranet vs. Employee App: Key Differences **Author:** MangoApps **Published:** 2023-09-22 **Category:** comparisons Compare legacy intranets with standalone apps. Discover how an AI-powered employee platform unifies them to improve reach, retention, and engagement. For decades, the corporate intranet was a digital library. It lived on a desktop, sat behind a firewall, and relied on humans to manually organize thousands of documents. Then came the employee app, promising to fix the "last mile" of communication by putting updates in everyone’s pocket.Today, organizations often feel forced to choose. Do you build a deep, content-heavy intranet for desk workers? Or do you launch a lightweight, accessible app for the frontline?The rise of AI-powered employee platforms has changed the equation. You no longer have to pick between depth and reach. Instead of building separate silos, modern platforms use AI to unify the experience—delivering the full power of an intranet through the simple interface of an app.Here is how the two technologies compare and why an AI-powered approach is the future of the employee experience.The Traditional Intranet: Depth Without IntelligenceHistorically, intranets were built for storage. They served as systems of record where HR and Internal Comms teams housed static documents. While they offered depth, they lacked the intelligence to make that information useful.The Limitation: Legacy intranets rely on manual curation and keyword search. If an employee types "benefits" into the search bar, they might get fifty results ranging from PDFs to old news posts. They have to dig for the answer. This friction is why fewer than 15% of employees use traditional intranets daily.The Employee App: Reach Without ContextThe employee app emerged to solve the accessibility problem. It bypasses email and the desktop to reach frontline and deskless workers directly on their devices.The Limitation: While apps excel at push notifications and operational tasks, they often lack the "brain" of a full platform. Without a unified data layer or intelligent search, apps can become shallow communication channels where it is difficult to find complex answers or complete multi-step workflows.The Solution: An AI-Powered Unified PlatformThe choice between "intranet" and "app" is a false dichotomy. The most effective strategy is a unified, AI-powered platform that adapts to the user.MangoApps replaces disjointed tools with a single intelligent system. At its core is Mango Employee AI, which sits on top of your unified data layer. It understands the context of every employee—whether they are a nurse on a floor, a retail associate in an aisle, or an accountant in a home office—and delivers exactly what they need.Here is how an AI-powered platform bridges the gap:1. From Search to AnswersIn a traditional intranet, you search for documents. In an AI-powered platform, you ask questions.Mango Employee AI acts as an intelligent assistant. An employee can ask, "How do I add a dependent to my insurance?" or "What is the store opening procedure?" The AI retrieves the answer from your knowledge base, cites the source, and delivers it instantly—even on a mobile screen.2. From Static Content to Active IntelligenceLegacy intranets require constant manual updating. MangoApps uses AI to act as a co-creator for your comms and HR teams. It can help draft updates, summarize long policies into digestible news snippets, and even automate routine maintenance to keep content fresh.3. Parity for Every WorkerAI is the great equalizer. It allows a frontline worker with a smartphone to access the same depth of organizational knowledge as a headquarters employee with a laptop. Because the AI handles the complexity of retrieving information, the mobile interface stays clean and simple while still providing full access to SOPs, policies, and people.Comparison at a GlanceWhy It Matters: Retention and EngagementThe goal isn't just to buy software; it's to keep your people.Today, 80% of organizations face a significant retention problem despite widespread adoption of HR tools. This is often because legacy tools were built for administrators, not employees.An AI-powered platform flips this dynamic. By removing the friction of finding information and completing tasks, you help employees feel supported and capable. When a worker can get an instant answer from their phone instead of waiting hours for a manager, they are more productive and less frustrated. That connection builds the kind of engagement that makes people stay.Don't settle for a static intranet or a shallow app. Move to an intelligent platform that brings your entire workforce together.Next Steps‍Evaluate your stack: Are your employees wasting time searching for answers across disconnected tools?Assess your AI readiness: Could an AI assistant help your frontline teams access policy and procedure data faster?Explore our solution: See how MangoApps unifies Intranet, HCM, and WFM into one seamless experience, powered by AI.Request a DemoRelated Resources‍MangoApps Unified Intranet & Employee App – Explore the platform that combines an AI-powered intranet, frontline app, and communications suite.Customer Success Stories – See real-world examples of how organizations like A.S. Watson and TeamHealth unified their workforce with MangoApps.Ultimate Intranet Buyer’s Guide for a Frontline Workforce (2026) – A comprehensive guide to selecting a unified platform that connects your entire workforce, from HQ to the frontline.Intranet RFP Template – Save time with a customizable template designed to help you evaluate vendors against modern, AI-powered requirements.Intranet Planning Guide – Step-by-step guidance on building a business case, defining requirements, and launching a platform that drives engagement.Frequently Asked Questions: Intranet vs. Employee App‍1. Can an employee app replace a traditional intranet?Yes, but only if it is built on a unified data layer. A standalone "lite" app often lacks the document management and governance capabilities of a full intranet. However, an AI-powered employee platform like MangoApps replaces both by offering the depth of an intranet (for content and knowledge management) with the accessibility of a mobile app (for frontline reach).2. Do I need separate platforms for desk and deskless workers?No. Maintaining separate systems creates information silos and disconnects your workforce. A unified platform allows you to publish content once and have it automatically adapt to the user's device. Desk workers see a full desktop dashboard, while frontline workers receive a streamlined mobile feed, ensuring everyone stays aligned without doubling the administrative workload.3. Is a mobile employee app secure for accessing company data?Modern employee apps are designed with enterprise-grade security. MangoApps, for instance, uses a HITRUST, ISO 27001, and SOC 2 Type II certified environment. This allows employees to access sensitive policies, pay stubs, and schedules on personal devices (BYOD) without compromising data security or requiring a VPN.4. How does AI change the intranet experience?AI transforms the intranet from a passive "storage unit" into an active assistant. Instead of browsing through folders to find a policy, employees can ask Mango Employee AI a question like, "What is the bereavement leave policy?" The AI retrieves the specific answer from your secure knowledge base and delivers it instantly, saving time and reducing frustration.5. Will an app really improve frontline retention?Yes. Frontline turnover is often driven by a lack of support and connection. When employees can easily swap shifts, check their pay, and get instant answers to questions via an app, they feel more empowered and valued. Organizations using unified platforms often see significant improvements in engagement scores and reductions in voluntary turnover.6. Isn't a unified platform more expensive than just buying an app?Actually, it is often more cost-effective. A unified platform consolidates multiple subscriptions—intranet, employee app, advocacy tools, and survey platforms—into one budget item. By reducing tool sprawl and administrative overhead, organizations typically lower their total cost of ownership while gaining better data visibility. --- # Intranet vs. Employee App: Bridging Understanding with Simple Analogies **Author:** Andy Tolton **Published:** 2023-09-22 **Category:** employee-app This is Part 4 in our series about the differences between an intranet and employee app. Previously, we broke down the nuances distinguishing an intranet vs. employee app and the various characteristics that makes them unique from each other. Continuing on that theme, in this installment of our series we’re here to offer a fresh […] # Intranet vs. Employee App: 7 Everyday Analogies That Make the Difference Clear If you have ever tried to explain the difference between an intranet and an employee app to a skeptical manager or a new hire, you know how quickly the conversation turns abstract. This article cuts through that by mapping each platform to something you already understand — a library, a streaming service, a ride-hailing app. By the end, you will know exactly what each tool does, which workers it serves, and when a single unified platform makes the either/or question irrelevant. **The short answer:** An intranet is a centralized, organization-wide repository of content, policies, and communications — built for depth and governance. An employee app is a personalized, mobile-first channel that delivers the right information to the right person at the right moment — built for speed and reach. Both solve real problems. Neither alone solves all of them. --- ## Why the Distinction Matters More Than Ever According to Social Edge Consulting, 91% of organizations operate an intranet — yet only 13% of employees use it daily, and nearly a third never log in at all. Meanwhile, IDC estimates that employees spend 2.5 hours per day searching for information. That gap between investment and actual use is the core problem both platforms are trying to solve, and understanding which tool closes which gap is the first step toward fixing it. For context on where the broader market is heading, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides a detailed benchmark of how platforms are evolving to address exactly this adoption problem. --- ## Analogy 1 — City Website (Intranet) vs. City Mobile App (Employee App) ### The City Website A city's official website is a centralized place where residents, visitors, and journalists can find historical records, zoning policies, council meeting minutes, and permit applications. It is authoritative, comprehensive, and structured for exploration. You go there when you need to understand something deeply — not when you need an answer in thirty seconds. An intranet works the same way. It houses the organization's policies, org charts, HR documentation, brand guidelines, and archived communications. It is the record of what the organization knows and has decided. ### The City Mobile App The city's mobile app does something different. It sends you a push notification when street parking is suspended on your block. It lets you pay a parking ticket in two taps. It shows real-time bus arrivals. It is not trying to replace the city website — it is trying to make the most time-sensitive information available to you wherever you are, without requiring you to navigate a full content hierarchy. An employee app works the same way. It delivers shift reminders, urgent safety alerts, task assignments, and personalized updates directly to a worker's phone. **The frontline extension:** This analogy matters most for the 80% of the global workforce that is deskless, per Emergence Capital. A warehouse associate, a retail floor worker, or a field technician has no corporate laptop and often no corporate email address. The city website is inaccessible to them — but the mobile app is not. Frontline employees frequently cannot access the intranet at all because it requires a corporate email address, a VPN, or a desktop. A mobile employee app eliminates those barriers by design. Framing the employee app as a convenience misses the point: for most of the global workforce, it is the only viable channel. --- ## Analogy 2 — Library (Intranet) vs. eReader (Employee App) ### The Library A physical library is a governed institution. Books are catalogued by the Dewey Decimal System. Access to certain archives requires credentials. A librarian enforces borrowing rules and ensures that materials are returned, updated, and accurate. That governance is not bureaucracy for its own sake — it is what makes the library trustworthy. A [modern intranet](/solutions/modern-intranet) works the same way. Content permissions determine who can see which documents. Approval workflows ensure that a policy page cannot be edited by anyone who happens to find it. Version control means employees are always reading the current employee handbook, not a three-year-old draft. This governance dimension — sometimes called a "secure intranet" — is increasingly a competitive differentiator as organizations face compliance requirements around data residency and access control. ### The eReader An eReader like a Kindle is portable, personalized, and immediate. It does not replace the library — it gives you curated, on-demand access to the titles most relevant to you, wherever you are. You do not browse the stacks; the stacks come to you. An employee app does the same: it surfaces the content, tools, and notifications most relevant to each individual's role, location, and preferences — without requiring them to navigate the full intranet hierarchy. --- ## Analogy 3 — Town Square (Intranet) vs. Personal Assistant (Employee App) ### The Town Square A town square is where the community gathers. Announcements are posted on the bulletin board. Neighbors debate the new development proposal. The local council shares its decisions. It is a shared space that fosters collective awareness and a sense of belonging. An intranet plays this role inside an organization. It is where company-wide announcements live, where cross-functional teams can find each other, and where the organization's culture is expressed through shared news and recognition. [Workspaces](/key-features/workspaces) within an intranet extend this further by giving teams dedicated collaboration areas without fragmenting the broader community. ### The Personal Assistant A personal assistant does not post announcements to the whole town. They manage *your* calendar, remind *you* of the deadline that is due tomorrow, and surface the one document *you* need before the 9 a.m. call. The value is specificity and timing, not breadth. An employee app delivers that same individualized experience — role-based notifications, personalized task queues, and content filtered to what is relevant to a specific person's job function. --- ## Analogy 4 — Department Store (Intranet) vs. Brand App (Employee App) ### The Department Store A department store organizes everything under one roof: housewares on the third floor, menswear on the second, electronics near the entrance. The [department sites](/key-features/department-sites) within an intranet mirror this structure — HR has its section, Finance has its section, and each business unit maintains its own organized corner of the shared space. The value is comprehensiveness and discoverability. ### The Brand App A brand's dedicated mobile app — think a retailer's loyalty app — does not show you every product in the store. It shows you your order history, your rewards balance, and items similar to what you have bought before. It is optimized for your repeat use case, not for first-time exploration. An employee app applies the same logic to work: it surfaces the tools and information a specific employee uses every day, reducing the cognitive load of navigating a large content environment. --- ## Analogy 5 — Cable Television (Intranet) vs. Streaming Service (Employee App) ### Cable Television Cable television delivers a fixed lineup of channels on a schedule set by the broadcaster. You can find something relevant, but the programming is designed for a broad audience, not for you specifically. You adapt to the schedule; the schedule does not adapt to you. A traditional intranet often works this way: content is published on a schedule determined by communications teams, and employees are expected to check in and find what they need. ### Streaming Service A streaming service learns your preferences and surfaces content accordingly. You do not browse a channel guide — you get a personalized home screen. You can watch on any device, at any time. An employee app applies the same logic: it learns from usage patterns, delivers role-relevant content proactively, and works on the device the employee already has in their pocket. According to data cited in enterprise deployment case studies, organizations that launch a branded employee app have achieved 87% workforce engagement within a few months of going live. --- ## Analogy 6 — Newspaper (Intranet) vs. News Alert App (Employee App) ### The Newspaper A newspaper provides depth. A single edition covers local news, international affairs, business, sports, and opinion — organized into sections so readers can navigate to what interests them. It rewards readers who have time to explore. An intranet rewards the same behavior: employees who invest time in navigating it find rich context, historical records, and detailed policy documentation. ### The News Alert App A news alert app does not ask you to read the whole paper. It sends you a push notification when something happens that matches your stated interests. It is optimized for immediacy and relevance, not depth. An employee app works the same way — it ensures that a frontline worker receives the safety update or schedule change the moment it is published, without requiring them to log in and search. --- ## Analogy 7 — Train Station (Intranet) vs. Ride-Hailing App (Employee App) ### The Train Station A train station is a shared infrastructure hub. Every route departs from the same place. The schedule is fixed and public. Everyone navigates the same system to reach their destination. An intranet is the same kind of shared infrastructure: a [company portal](/key-features/company-portal) that every employee enters through the same front door, with a consistent navigation structure that reflects the organization's priorities. ### The Ride-Hailing App A ride-hailing app does not ask you to adapt to a fixed schedule. You open it, enter your destination, and a car arrives for you specifically. The experience is built around your immediate need. An employee app delivers the same on-demand, individualized experience — the right tool, the right content, the right notification, at the moment the employee needs it. --- ## The Question the Analogies Raise: Do You Need Both? After working through seven analogies, a logical follow-up question is: *do organizations have to choose?* The answer, increasingly, is no. Traditional intranets take months to deploy, strain IT teams, and deliver static content that becomes stale quickly. Meanwhile, a standalone employee app without an underlying content and governance layer lacks the depth employees need for complex tasks. The organizations seeing the strongest results are those that have moved to a unified platform — one that provides the governed content repository of an intranet *and* the personalized, mobile-first delivery of an employee app in a single product. Enterprise deployments of unified employee experience platforms have reported 90% frontline adoption within the first six months — a figure that standalone intranets, with their desktop-first architecture, rarely approach. For a closer look at how a unified platform resolves the intranet-vs-app tension in practice, the [solutions/employee-app](/solutions/employee-app) page outlines how a single platform can serve both deskbound and frontline workers without requiring two separate tools or two separate IT projects. --- ## What Should HR and IT Leaders Do Next? If your organization is evaluating whether to invest in an intranet, an employee app, or both, three questions will clarify the decision: 1. **What percentage of your workforce is deskless?** If it is above 30%, a desktop-first intranet alone will leave the majority of your employees underserved. 2. **What is your current intranet adoption rate?** If employees are spending an average of six minutes per day on intranet tools (the benchmark cited by SWOOP Analytics for SharePoint), the platform is not delivering value — and adding more content will not fix a reach problem. 3. **What is the cost of disengagement?** Replacing a frontline employee costs between $4,400 and $15,000 (per industry data cited by MangoApps). Poor mobile access and low intranet adoption are not just IT problems — they are retention and financial risks. For a broader view of how internal communications strategy is evolving in response to these pressures, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the key shifts HR and communications leaders are navigating this year. **The bottom line:** An intranet gives your organization depth, governance, and a shared knowledge base. An employee app gives your workforce reach, personalization, and mobile access. The analogies in this article are not just illustrative — they map directly to the capabilities your teams need. The organizations that treat these as complementary rather than competing tools, or that adopt a unified platform that delivers both, are the ones closing the gap between the 91% of companies that have an intranet and the 13% whose employees actually use it daily (per Social Edge Consulting). --- # How an Intranet Differs From an Employee App **Author:** Andy Tolton **Published:** 2023-09-22 **Category:** employee-app This is Part 3 in our series about the differences between an intranet and employee app. In the previous segment of this series, we delved deep into the shared characteristics of intranets and employee apps. While they may come together in harmony, offering a robust set of tools to facilitate communication and collaboration in the […] **_This is Part 3 in our series about the differences between an intranet and employee app._** An intranet and an employee app are not the same tool — even when they overlap. The core distinction: intranets are built around communal, departmental, and organizational knowledge management, while employee apps are built around the individual employee's daily workflow, mobile access, and personal productivity. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in — and those who do average just six minutes per day, per SWOOP Analytics. That engagement gap is precisely where employee apps step in. If you are using an intranet and considering employee app adoption, this article maps the specific functional differences so you can make an informed decision. ## The Differences of an Intranet Intranets serve as a backbone in many organizations, facilitating collaborative workspaces and acting as repositories for a wealth of company information. They are designed with a focus on communal and departmental interactions rather than individual engagements, providing a structured platform where employees can share knowledge, engage in rich discussions, and access an array of resources to enhance collaborative efforts within the company. Let's explore the intricate nuances that set intranets apart in the corporate ecosystem. ### Collaborative Space Intranets are designed primarily as collaborative spaces, places where teams across a company can connect, share documents, and work together on various projects. This collaborative nature extends beyond the physical workspace; it is a virtual meeting ground where ideas are exchanged and nurtured to fruition. The [workspaces](/key-features/workspaces) model found in modern intranets reflects this group-first design philosophy. Employee apps, on the other hand, tend to focus more on individual productivity, offering features tailored to personal task management rather than a collaborative workspace. Therefore, while intranets foster a collaborative spirit by providing tools and platforms for group discussions and brainstorming, employee apps prioritize personal productivity tools that aid individual employees in managing their tasks effectively. ### Content Repository When it comes to housing a wide range of company documents, from policies to training materials, intranets serve as central repositories where such data is stored and can be accessed over years. Per IDC, employees spend an average of 2.5 hours per day searching for information — a problem that a well-governed intranet content repository is specifically designed to reduce. This large library is vital in maintaining a rich history of the organization's intellectual property, allowing for continuity and reference over time. Employee apps generally focus more on current tasks and individual functionalities, offering less in the way of a historical repository of organizational knowledge. While they may provide access to necessary documents, they rarely house the extensive library of resources often found in an intranet. ### Departmental Sections Intranets frequently feature dedicated sections or portals for different departments, each with its own set of resources, news, and tools — a structure supported by purpose-built [department sites](/key-features/department-sites). This allows for a sort of microcosm within the larger organization where individual departments can manage their specific needs while still staying connected to the broader organizational ecosystem. Employee apps, conversely, are more about individual personalization, offering features that cater to the needs and preferences of individual employees rather than focusing on departmental delineations. ### Discussion Forums Discussion forums are a significant part of many intranets, fostering a space where employees can discuss a wide variety of topics, share knowledge, and seek advice. These forums encourage open communication and the free exchange of ideas, promoting a collaborative and inclusive work culture. In contrast, employee apps generally lean more towards facilitating direct, peer-to-peer interactions through chat features, offering a quicker, more immediate form of communication but potentially lacking the depth and breadth of discussion found in intranet forums. ### Company-Wide Announcements Intranets are typically the go-to platform for company-wide announcements, newsletters, and updates. They act as the central hub for corporate communications, ensuring that all employees are kept informed about the latest developments and news in the organization. Employee apps, while also offering communication features, tend to focus more on personalized notifications and alerts, delivering information directly relevant to individual employees rather than broad company-wide announcements. ### Advanced Search Given the vast amount of content available on intranets, advanced search functionalities are often incorporated, including features such as filters, tags, and categories to aid in the quick retrieval of information. This functionality is essential in helping employees navigate the extensive resources available efficiently. Employee apps, with their more narrow focus on individual tasks and functions, often do not require such advanced search capabilities, as the scope of information available is generally more limited and personalized to the user's role and functions. ### Integration with Enterprise Systems Intranets often boast substantial integrative capabilities, serving as a hub that connects various platforms such as HR systems, CRMs, and ERPs into a cohesive whole. This integration enables streamlined operations and a centralized point of access to a wide variety of tools and resources. While employee apps also offer integrative features, the focus is generally more on integrating with personal productivity tools to facilitate a smooth work-life blend, rather than focusing on broader enterprise system integrations. ### Long-Term Archiving The role of intranets as archives for long-term storage of company knowledge and historical data cannot be understated. This feature ensures that vital company knowledge is preserved over time, available for future reference and helping to maintain a continuous organizational narrative. Employee apps, on the other hand, are generally more focused on the here and now, offering features that facilitate current tasks and needs rather than preserving historical data for the long term. ### Training Platforms Intranets increasingly integrate Learning Management Systems where employees can undertake training modules, engage with instructional videos, and complete assessments to further their professional development. This central hub for learning facilitates continuous employee growth — a critical component of any employee engagement training strategy. Employee apps, while they may offer reminders and notifications for training and development opportunities, generally do not house the rich array of learning resources and modules typically found on an intranet platform. For a deeper look at how learning fits into daily workflows, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ### Feedback and Polling Intranets are also equipped with tools for gathering company-wide feedback and conducting polls or facilitating suggestion schemes — the kind of structured employee engagement survey capability that fosters a democratic and inclusive work environment. They create avenues for employees to voice their opinions and feedback on various organizational aspects. Employee apps, though they may offer quick polls or feedback tools, usually focus on a more immediate and narrow scope, capturing feedback quickly but perhaps not with the same depth and detail as intranet-based feedback tools. ## The Differences of an Employee App When we talk about the finer points of employee apps, it is essential to highlight how they stand apart from traditional intranets. Below, we explore the intricate details that define employee apps, emphasizing their modern approach to enhancing workforce efficiency and employee engagement. ### Access & Security Employee apps are designed to give secure and efficient access to all work-related resources right through personal and mobile devices, setting a departure from the broader and less personalized scope of intranets. Critically, frontline employees can access a mobile employee app without a corporate email address, VPN, or a desk — a capability traditional intranets typically cannot support natively. Per Emergence Capital, 80% of the global workforce is deskless, making this distinction operationally significant. This individual-centered approach extends to features such as biometric authentication, ensuring security and offering a tailored experience to each user. ### Offline Access Unlike traditional intranets, employee apps excel in providing functionalities even in offline scenarios, a standout feature that ensures uninterrupted workflow. Workers can utilize the fundamental features without an internet connection, a critical advantage in areas grappling with connectivity issues. This reliability fosters a work dynamic that remains consistent and productive, no matter the circumstances. ### Geo-Fencing & Location-Based Services Employee apps have introduced geo-fencing and location-based services, an enhancement rarely mirrored in an intranet. It allows organizations to offer a customized app experience based on the geographic location of the employee, either enabling or restricting functionalities accordingly. This goes a long way in not just securing data but also in crafting experiences that fit the working conditions, be it remote or on-site, of every individual, enhancing both security and personalization. ### Task & Time Management The task and time management features in employee apps offer a detailed and granular view of one's schedule, a sharp contrast to the generalized overviews found in intranets. Employees can take charge of their schedules with detailed control, setting reminders and tracking personal deadlines to foster personal productivity. This intricate management facilitates effective handling of work commitments, moving a step further in individual-centric functionalities. ### Personal Dashboard & Notifications The personal dashboard stands as the nerve center of an employee app, showcasing real-time alerts and vital information pertinent to individual employees. This space goes beyond the generic updates seen in intranets, offering an intuitive and engaging user experience. Modern employee apps can consolidate 200+ disparate workplace systems into a single mobile dashboard, directly reducing tool-sprawl costs for IT teams. It aids employees in keeping a close eye on their work schedules and updates, enhancing efficiency and productivity through a personalized touch. ### Communication & Collaboration Employee apps promote a culture of openness and direct engagement, a facet less explored by intranets. They serve as a platform for spontaneous, peer-to-peer interactions, enabled effortlessly on mobile devices. This enhancement leads to a more connected, collaborative, and responsive work environment, fostering a culture of direct communication and rapid responses. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) explores how organizations are shifting communication strategy toward mobile-first, app-driven models. ### Shifts, Leave & Requests Centralizing the management of shifts, leave, and requests, employee apps have streamlined what was once a cumbersome process in many intranets. Real-time notifications play a pivotal role here, allowing employees to manage their schedules fluidly and transparently. It removes the hassle typically involved in scheduling processes, encouraging a smoother operational flow and higher levels of satisfaction among employees. ### Performance & Development Employee apps take a personalized route to nurture individual growth paths, going beyond the broad strokes often seen in intranet systems. These apps offer insights into personal performance metrics and timely reminders for training sessions — a focused approach to foster continuous learning and development. One benchmark worth noting: OU Health achieved 87% workforce engagement within a few months of launching a branded employee app. This approach ensures that individuals have a clear roadmap to their growth within the organization, encouraging an environment of active development. ### Expenses & Documents Handling administrative tasks becomes a straightforward affair with employee apps, which stand in contrast to the sometimes convoluted processes seen in intranets. The on-the-go expense tracking and easy access to essential documents match the fast pace of the modern workforce. It not only saves time but significantly reduces the effort traditionally associated with managing administrative tasks. ### Wellness & Safety Employee apps prioritize the wellness and safety of the workforce, integrating tools and features that are generally not the focal point in intranet systems. Through wellness reminders and emergency alerts, these apps foster a nurturing and caring work environment. This approach ensures that the work culture remains infused with a sense of safety and well-being, promoting a balanced work-life scenario and enhanced job satisfaction. ### Integration & Personal Tools A defining nuance of employee apps is their integration with personal productivity tools, an aspect not commonly supported by intranets. This integration creates a harmonious blend of work and personal life, fostering an environment where both can coexist without friction. It stands as a testimony to the modern, integrated approach to work-life dynamics, actively promoting both productivity and well-being. ## Which Should You Choose — Intranet, Employee App, or Both? The honest answer for most mid-to-large organizations is: both, unified on a single platform. Traditional intranets take months to deploy, strain IT teams, and produce static, ungoverned content that becomes stale — a contrast competitors use to justify modern app-first alternatives. Yet a standalone employee app without intranet-grade knowledge management leaves knowledge workers without the content repository and departmental structure they need. Here is a practical decision framework: - **Choose intranet-first** if your workforce is primarily desk-based, your primary need is knowledge management and departmental collaboration, and you have IT resources to govern content over time. - **Choose employee app-first** if 50% or more of your workforce is deskless or frontline, lacks corporate email, or operates across multiple locations. Replacing a single frontline employee costs between $4,400 and $15,000 — poor mobile access that drives disengagement is a measurable financial risk. - **Choose a unified platform** if you need both capabilities and want to avoid the tool-sprawl that comes from running separate systems. A unified [modern intranet](/solutions/modern-intranet) and employee app on one platform means employees get the collaborative, knowledge-rich environment of an intranet and the personalized, mobile-first experience of an employee app — without switching tools. Per Social Edge Consulting, only 13% of employees use their intranet daily. Closing that gap requires not just better intranet governance but meeting employees where they already work: on their phones, without a VPN, in the flow of their actual day. That is the structural case for treating intranet and employee app not as competing choices but as complementary layers of a unified employee engagement software strategy. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarking if you are evaluating platforms against each other. ## Part 4: Intranet vs. Employee App: Bridging Understanding with Simple Analogies Next up, we will break this down even further, using straightforward analogies to highlight the differences between the two. Stay tuned to gain a clearer, simpler understanding of how these platforms operate and what they can offer to an organization. Get the best of both worlds with MangoApps Employee SuperApp! Not ready for that transformation? Start with either a MangoApps Modern Intranet or MangoApps Employee App and we'll help you transform to a SuperApp when you are ready. Schedule a Call --- # Commonalities Between a Modern Intranet and an Employee App **Author:** Andy Tolton **Published:** 2023-09-22 **Category:** employee-app This is Part 2 in our series about the differences between an intranet and employee app. In the opening installment of this series, we navigated the origins and distinct functionalities of intranets and employee apps—two formidable tools in the digital toolkit of today’s organizations. We painted a picture of the modern intranet as comprehensive, desktop-centric […] # What a Modern Intranet and an Employee App Actually Have in Common According to Social Edge Consulting, 91% of organizations already operate an intranet or collaboration platform — yet only 13% of employees use it daily, and nearly a third never log in at all. That gap is not explained by features. Both [modern intranets](/solutions/modern-intranet) and [employee apps](/solutions/employee-app) have accumulated similar capabilities over the past decade. The gap is explained by deployment decisions, audience assumptions, and a persistent habit of treating these two platform categories as more different than they are. Understanding the overlap matters practically. SWOOP Analytics found that employees spend an average of six minutes per day actively using intranet tools, while IDC estimates that employees spend 2.5 hours per day searching for information. That gap — six minutes of use against 2.5 hours of search — reflects deployment failure, not product failure. Much of that deployment failure comes from choosing one platform category over another, or deploying both in parallel, without understanding how much their functionality already overlaps. This article examines the shared feature set — the capabilities that every serious intranet and every serious employee app deliver — and what the convergence of those capabilities tells organizations thinking about where to invest next. --- ## Communication and information flow The most fundamental capability — structured communication to employees — appears in both modern intranets and employee apps without exception. Announcements, targeted broadcasts, department-level updates, and leadership messaging are native to both categories. The mechanism may differ (desktop-first publishing tools in intranets, push notifications in apps), but the end goal is identical: delivering the right message to the right person at the right moment. Both platforms have evolved to support bidirectional communication. Forums, comment threads, reactions, and survey tools — once considered differentiators — now appear across every competitive intranet and every employee app. According to the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook), organizations that enable this two-way communication layer see measurably stronger engagement outcomes than those that rely on broadcast-only architectures. ## Resource access and knowledge management Both categories operate as centralized knowledge repositories. Employees on either platform can access HR documents, policy libraries, training materials, process guides, and team wikis without navigating a separate system. That single-destination access model for operational knowledge is now table stakes in both categories — not a differentiator. The distinction that once separated these platforms was desktop access vs. mobile access to that knowledge base. Modern intranets have closed most of the mobile gap; employee apps have extended their content management features. Today, the more relevant question is not which platform provides access, but whether access works for every type of employee. Emergence Capital estimates that 80% of the global workforce is deskless — working in manufacturing, healthcare, retail, and logistics where desktop access is intermittent or absent. Platforms that serve only desk workers, regardless of category, leave the majority of most organizations' employees without a reliable channel. ## Collaboration and co-creation Real-time collaboration — shared documents, project workspaces, group channels, and co-editing — has moved from intranet-only territory into employee apps as both categories matured. The gap narrowed as frontline-focused apps added content creation tools, while intranets added mobile-friendly interfaces for field workers. Both platforms now support structured collaboration spaces: groups organized by project, department, or interest; shared document libraries; task tracking tied to discussions; and notification systems that keep participants aligned across time zones and work shifts. Gallup's 2026 State of the Global Workplace research documents that workplace connection — the sense that colleagues and the organization are reachable — is among the strongest predictors of retention and discretionary effort. Collaboration infrastructure, regardless of which platform delivers it, is the mechanism that builds that connection at scale. ## Search and information discoverability Search functionality is one of the most underappreciated overlaps between modern intranets and employee apps. Both surfaces are required to answer the question employees ask dozens of times per day: where is the thing I need? IDC's estimate that employees spend 2.5 hours per day searching for information reflects what happens when search does not work — not just when a search field is absent. Both platform categories have responded by investing in contextual search: federated results across document libraries, people directories, and published content; role-based filtering; and natural language query support. Organizations evaluating either platform should test search with representative employees and representative content before committing. A search field is not a search system. ## Mobile access and frontline readiness Mobile is where the two categories began as most distinct and have since converged most visibly. Employee apps were built mobile-first; modern intranets added mobile layers over time. Today, every serious platform in both categories offers mobile access — but the quality of that access varies significantly. The test that reveals actual frontline readiness: access the platform on a personal mobile device, without corporate credentials or a VPN, on a first log-in. Platforms that require a company email address, an IT-managed device, or a VPN tunnel have a structural barrier to frontline adoption that training cannot resolve. With 80% of the global workforce deskless, according to Emergence Capital, platforms that fail this test leave the majority of most organizations' employees without a dependable communication channel. Mobile accessibility is not a feature category — it is a deployment precondition. ## User profiles and directory services Employee directories and social profiles appear in both modern intranets and employee apps. In both cases, the value extends beyond finding a phone number. Profiles that surface expertise, certifications, past projects, and department affiliations help employees identify the right collaborator, orient new hires, and build organizational knowledge about who knows what. This functionality is structurally similar across both categories. The differences lie in how profiles are populated (HRIS integration vs. self-service), how visible they are to frontline workers, and whether they connect with scheduling, task assignment, and recognition workflows. The profile infrastructure an organization deploys will underpin communication and collaboration for years. ## Feedback and employee listening Pulse surveys, feedback forms, and idea submission tools appear in both modern intranets and employee apps. Employee listening was once treated as a separate software investment; most platforms now include it in the base tier. Both categories support the same underlying need: understanding how employees in every role and location experience working conditions, leadership communication, and operational processes. Platforms that reach frontline employees directly — without requiring email or desk access — are more likely to produce response rates large enough and representative enough to inform decisions rather than just confirm existing assumptions. ## AI personalization and content curation Personalized content surfaces — feeds that adjust by role, location, tenure, and engagement history — were once positioned as premium differentiators. They are now a shared feature expectation across both platform categories. According to the [ClearBox 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report), AI-driven personalization is evaluated as a standard capability when organizations shortlist platforms, not an advanced add-on. The practical implication: employees should not need to configure preferences to see content that is relevant to them. A manufacturing floor worker should see safety updates, shift schedules, and team announcements without scrolling past headquarters content. A sales manager should see pipeline resources without wading through operations posts. Both intranet and employee app vendors are now expected to deliver this targeting automatically, using role and location data the organization already maintains. ## Security and governance Enterprise security requirements apply equally to modern intranets and employee apps: role-based permissions, SSO support, SAML 2.0 compatibility, audit logging, and data residency controls. Neither platform category avoids these requirements for organizations in regulated industries — healthcare, finance, government contracting, and critical infrastructure. Compliance expectations have escalated as more HR and operational workflows move into workforce platforms. Organizations deploying a platform that will house employee data, policy acknowledgments, and communication records cannot treat security as a secondary evaluation criterion. Both intranet and employee app selections should be evaluated against the same security checklist, with the same rigor. ## Training and development infrastructure Learning content — structured training modules, compliance certification tracking, video libraries, and new-hire onboarding — has migrated into both platform categories. Organizations discovered that employees do not distinguish between the intranet and the training system and prefer not to navigate between them. Both modern intranets and employee apps now support microlearning formats accessible on mobile, completion tracking tied to user profiles, and content assignment by role or department. Organizations that maintain separate learning platforms alongside their intranet or employee app pay integration overhead indefinitely — a cost that compounds as the workforce grows and compliance requirements expand. ## Calendar, scheduling, and operational coordination Calendar integration and scheduling support appear in both platform categories, offering employees a consolidated view of company events, shift schedules, and team priorities. For organizations with shift-based or distributed workforces, this operational layer is not a convenience feature — it is where communication and workforce management intersect. Both modern intranets and employee apps have expanded their integration coverage with scheduling and workforce management systems. Platforms that surface schedule information, policy updates, and team communication in the same interface reduce the number of systems employees need to check to stay oriented and prepared. --- ## What the convergence means for platform evaluation The shared feature set documented above has a practical consequence: the distinctions that once separated modern intranet from employee app — desktop vs. mobile, organizational vs. individual, deep content vs. quick access — are no longer reliable separators. Both categories now deliver all of those things. The questions that actually differentiate platforms at evaluation are different: **Frontline access without credentials:** Does the platform work for an employee logging in for the first time, on a personal device, without a corporate email address or VPN? Most vendor demos skip this test entirely. **AI personalization depth:** Does the system surface role-specific content automatically, or does it require employees to manage their own notification settings? The former scales to thousands of employees; the latter does not. **Search quality under realistic conditions:** Can an employee locate a specific policy, a colleague's expertise, or a project file in under 30 seconds using natural language? Testing with representative content — not demo data — is the reliable measure. **Total first-year cost:** What does the cost model look like with implementation, integrations, training, and customizations included — not just per-seat licensing? Platforms with similar feature lists often diverge most sharply here. Organizations that evaluate on these dimensions will find that the intranet vs. employee app distinction is largely resolved. The decision is not which category to choose — it is which specific platform serves the actual composition of their workforce, desk workers and frontline workers alike, with the least friction and the most sustainable total cost. --- ## Where both categories are heading Both modern intranets and employee apps are moving in the same direction: unified access to communications, HR self-service, collaboration, and workforce management from a single platform, on any device, without requiring multiple logins or tool-switching between parallel systems. Unified platforms eliminate the need to switch between three or four separate tools, reducing IT overhead and employee friction at the same time. The shared feature set these two categories already hold in common is not coincidental — it is the result of each category expanding toward the same workforce coverage problem. The organizations that benefit most from that convergence are the ones that evaluate both categories honestly, test with the employees who are hardest to reach, and choose based on what the workforce actually needs rather than what the vendor category traditionally promised. --- # The Unique Use Cases of an Intranet and Employee App **Author:** Andy Tolton **Published:** 2023-09-22 **Category:** employee-app In the digital workplace, the intricate web of communications, collaborations, and operations hinge on platforms that foster efficiency and connectivity. Here, standing at the forefront are two pivotal technologies – the traditional yet ever-evolving intranet and the mobile-centric employee app. Yet, what’s not clear is how they are different. What are the unique use cases […] ## The Unique Use Cases of an Intranet and Employee App The short answer: an **intranet** is your organization's central knowledge hub — a secure, desktop-optimized repository for documents, policies, and company-wide collaboration. An **employee app** is the mobile-first delivery layer that puts real-time communications, schedules, and HR self-service into every worker's pocket. Both serve distinct purposes, and confusing them leads to low adoption, wasted spend, and disconnected employees. Per Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in, and only 13% use one daily. That gap is exactly what this series addresses. In the digital workplace, the web of communications, collaborations, and operations hinges on platforms that foster efficiency and connectivity. Two pivotal technologies sit at the center of that web: the traditional yet ever-evolving intranet and the mobile-centric employee app. What is not always clear is how they differ. What are the unique use cases of an intranet, and how do they contrast with an employee app? In this series on "Intranet vs. Employee App" we uncover those differences — and some similarities — so every organization can make a more informed decision about how to deploy these tools. ## Origins of the Intranet Cast your mind back to the earlier days of corporate dynamics. Intranets emerged as the digital reincarnates of physical bulletin boards and file cabinets. These platforms, primarily desktop-centric, resonated as the central hub for all employees — boasting vast repositories of documents and facilitating organization-wide collaboration. A visit to the intranet was akin to a detailed library visit: comprehensive data, rich content depth, and a focused approach to collaborative spaces. The intranet definition has expanded considerably since those early days. Where once it simply meant an internal website, today a modern intranet encompasses role-based permissions, single sign-on (SAML 2.0/OAuth 2.0), AI-curated content feeds, and universal search across connected storage systems like SharePoint and Google Drive. That evolution matters because, per IDC, employees spend 2.5 hours per day searching for information — a cost that a well-governed intranet is specifically designed to reduce. ## Origins of Employee Apps As time moved forward, the employee app emerged — rising from the wave of smartphone adoption and offering on-the-go access to work-related resources. Think of the employee app as a personal assistant always in your pocket: real-time updates, personalized notifications, and immediate solutions, all tailored to enhance individual productivity and engagement. Frontline employees can access communications, shifts, HR self-service, and training in a single mobile app without a corporate email address, VPN, or a desk. That capability matters at scale: per Emergence Capital, 80% of the global workforce is deskless, meaning the majority of employees have never had reliable access to a traditional desktop intranet at all. Yet, despite their distinctive origins and primary focus areas, intranets and employee apps share a collaborative spirit. Both facilitate communication and access to essential resources, each providing a canvas of modern workplace functionality — but only when each is used appropriately. ## How Intranets and Employee Apps Are Used Let us unpack the layered dynamics of intranets and employee apps. As we explore their commonalities, differences, and the unique roles they play in the employee journey, the distinction between these tools becomes clear. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) offers a useful external benchmark for how leading platforms are evaluated across both dimensions. Join us in part one of our series exploring the organized experience of an intranet, contrasted with the more personal touch of employee apps. Throughout the series, we lay the groundwork to understand these important tools in the modern corporate world and reduce the confusion that surrounds these terms today. ## Intranet Use Case Intranets started as internal websites or portals for companies — the digital evolution of physical bulletin boards, file cabinets, and company directories. The technology has evolved significantly since, but the core intranet definition remains consistent: provide a secure, internal information hub that allows employees to access content and resources from anywhere. Traditional intranets, however, carried real costs. They took months to deploy, strained IT teams, and delivered static, ungoverned content that became stale quickly. Modern platforms address this directly — a [modern intranet](/solutions/modern-intranet) can be stood up in minutes with no IT-led customization required, with role-based permissions and data governance built in from day one. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools — a benchmark that underscores how much room for improvement remains when intranets are poorly designed or governed. ### The Primary Focus of an Intranet In the evolving landscape of employee experience, intranets have carved out a pivotal role — fostering connectivity and information sharing across all levels of an organization. Functioning as a central hub, they facilitate organization-wide collaboration, house important announcements, and encourage team synergy. A well-structured [company portal](/key-features/company-portal) becomes a reservoir of essential documents accumulated over years, with governance controls that keep content accurate and accessible. Intranet use cases are best focused in three primary areas: - **Organization-wide Collaboration:** Intranets are a central hub for all employees regardless of role — providing a space for company-wide announcements, document storage, and team collaboration through dedicated [workspaces](/key-features/workspaces). - **Content Depth and Governance:** Intranets house a vast repository of documents, from company policies to training materials, archived over years. Critically, a modern intranet enforces role-based permissions and SSO so the right people see the right content — differentiating it from consumer-grade file-sharing tools. - **Desktop-centric Experience:** While modern intranets have mobile-responsiveness, they are optimized for desktop use. This makes the intranet the right experience for workers who primarily sit at a desk during the workday — and the employee app the right delivery layer for everyone else. ## Employee App Use Case As organizations adapted to the smartphone era, employee apps marked a significant stride in the corporate world — bringing the workplace into the palm of every employee's hand. They were initially created to facilitate immediate access to work-related tools and information wherever an employee might be. The primary focus of employee apps has always been to foster individual productivity and real-time engagement. The business case for getting this right is measurable. Organizations replacing a frontline employee face replacement costs ranging from $4,400 to $15,000 per person, making disconnected mobile experiences a direct retention risk. Additionally, employees lose over 4 hours per week switching between disconnected systems — a drag on productivity that a unified [employee app](/solutions/employee-app) is designed to eliminate. ### Primary Focus of an Employee App The emphasis of an employee app is on streamlining communications and operations through real-time interactions. With a mobile-centric design, these apps deliver a consistent user experience on smartphones and tablets — making them an indispensable tool for modern employees, especially on the frontline. The three use cases where employee apps excel are: - **Individual Productivity:** These apps provide a personalized experience for individual employees — tools for viewing one's schedule, requesting time off, or receiving personalized notifications, all without requiring a corporate email address or VPN. - **Real-time Engagement:** The aim of an employee app is immediacy. Whether it's a quick chat with a colleague or an instant notification about a schedule change, the focus is on real-time interaction. Benchmarks from large enterprise deployments show 90% frontline adoption within the first six months and 87% workforce engagement achieved within a few months of launching a branded employee app. - **Mobile-centric Reach:** These apps are designed for mobile devices, making them the right tool for the 80% of the global workforce that is deskless — per Emergence Capital — and for frontline employees in particular. As we continue to uncover the nuances of intranets and employee apps, it becomes evident that both have carved out indispensable niches in the digital workplace. The intranet, with its rich history, continues to be a repository of deep-seated knowledge — fostering organization-wide collaboration with a nuanced tilt toward a desktop-centric, governed experience. The employee app personalizes the work experience, bringing immediacy and individual productivity into sharp focus, especially for frontline employees. Critically, the two are not competitors: the employee app is the frontline delivery layer for intranet content, not a separate silo. Next in the series we will talk about the commonalities between intranets and employee apps — the ways in which they are similar and how they might overlap in use. ## Part 2: Commonalities Between a Modern Intranet and an Employee App Get the best of both worlds with MangoApps Employee SuperApp. Not ready for that transformation? Start with either a MangoApps Modern Intranet or MangoApps Employee App and we'll help you transform to a SuperApp when you are ready. ## Which Should Your Organization Choose — Intranet, Employee App, or Both? The decision is rarely either/or. Organizations with a significant desk-based workforce and complex document governance needs should prioritize a modern intranet first — then extend reach to mobile workers through an employee app. Organizations where the majority of employees are frontline or deskless should lead with the employee app and use the intranet as the back-end content layer. A practical framework: - **Desk-based majority, complex compliance needs → Start with a modern intranet.** Governance, role-based permissions, and deep content repositories are the primary value drivers. - **Frontline or deskless majority → Start with an employee app.** Real-time communications, mobile scheduling, and HR self-service without a corporate email address are the priority. - **Mixed workforce → Deploy both as an integrated platform.** The employee app surfaces intranet content in a mobile-friendly format; the intranet provides the governed, searchable knowledge base behind it. Per IDC, employees spend 2.5 hours per day searching for information — an integrated platform cuts that cost for both desk and frontline workers. For a deeper look at how internal communications strategy connects to these platform decisions, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) provides current benchmarks and planning frameworks. ## What Does a Modern Intranet Actually Include? The intranet definition has evolved well beyond a static internal website. A modern intranet today typically includes: - **A governed content layer** with role-based permissions, SSO (SAML 2.0/OAuth 2.0), and version-controlled documents — so content stays accurate and access stays secure. - **AI-powered personalization** that surfaces relevant content based on role, location, and behavior — addressing the core reason nearly a third of employees never log in, per Social Edge Consulting: the intranet shows them content that isn't relevant to their work. - **Universal search** across connected storage systems (SharePoint, Google Drive, and others) so employees find what they need without switching tools. - **Department and team sites** — structured spaces like [department sites](/key-features/department-sites) that give each team a governed home for their own announcements, documents, and collaboration. - **A flexible page-building layer** — tools like a [webpage builder](/key-features/webpage-builder) that let communications teams publish and update content without IT involvement. Understanding what a modern intranet includes — and what an employee app adds on top — is the foundation for making a platform decision that actually sticks. --- # MangoApps Transforms Workplace Engagement With Artificial Intelligence **Author:** MangoApps **Published:** 2023-09-13 **Category:** press-release The aim is to integrate AI into every aspect of the workspace—from intranet search and efficient task management to enhanced communication and secure, personalized environments. # MangoApps AI for Employee Engagement: How the Seven Capabilities Work When a platform describes itself as "AI-powered," the meaningful question is not which AI features it includes — it is which specific failure modes those features address. MangoApps structures its AI capabilities into seven categories: Employee Assistant, Content Enhancement, Accessibility and Inclusion, Personalization and Engagement, Compliance and Security, Talent Management, and Operations and Workflow. Each targets a distinct breakdown point in intranet adoption or employee communication. This article explains what each category does, what it is not designed to do, and why the frontline access architecture matters as much as the AI itself. ## The structural failure that precedes every AI discussion Per IDC research, employees spend 2.5 hours per day searching for information they need to do their jobs. Per Social Edge Consulting, 91% of organizations operate an intranet — yet only 13% of employees use one daily, and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends six minutes per day with intranet tools. These numbers are not a story about AI. They describe what happens when communication infrastructure is designed for the 20% of workers who have a desk, a company laptop, and a corporate email address — while the other 80% have none of those things. The result is a platform that serves the already-connected while the majority of the workforce receives nothing. Per Emergence Capital, approximately 80% of the global workforce is deskless: clinical staff, retail associates, logistics drivers, manufacturing floor workers. These employees have no reliable path into a traditional intranet. MangoApps supports email-free login and mobile-first access for this population. That design decision is the prerequisite for everything that follows. AI that personalizes a newsfeed no frontline worker can log into does not improve engagement for the frontline — it improves the experience for the employees who were already using the platform. ## How the seven capability categories address specific problems **Employee assistant AI** answers employee questions by searching across files, conversations, and knowledge bases. Employees who currently spend time locating policy documents, leave procedures, process guides, or onboarding materials can get answers directly rather than submitting a help-desk ticket or interrupting a manager. For organizations where support ticket volume is driven by information retrieval rather than technical failure, this capability reduces that load and recovers time against the 2.5-hour daily search benchmark IDC identified. **Content enhancement AI** provides real-time support for summarization, expansion, refinement, and sentiment analysis. Communications teams drafting announcements, HR writing policy changes, and managers producing team updates all work faster when the AI handles condensing or clarifying language. The sentiment analysis component flags tone issues before content is published — useful when the framing of a communication has consequences for how it lands across a distributed workforce. **Accessibility and inclusion AI** handles real-time translation of user-generated content, automatic video closed captions, and text-to-speech generation. For multilingual workforces — common in retail, hospitality, BPO, and nonprofit operations with distributed field staff — a single communication reaches every employee in their preferred language and format without a manual localization process. This is not only a language gap problem. Employees who cannot engage with long policy documents benefit from audio alternatives; employees with accessibility needs benefit from captions generated automatically rather than added by individual content creators. When content is accessible from publication, the window between information availability and employee awareness shrinks — and employees who would have been missed are included in the organizational communication stream from day one. **Personalization and engagement AI** runs the intelligent newsfeed engine that prioritizes content by role, location, and behavior. The SWOOP Analytics six-minute daily average reflects what happens when employees consistently see content that has nothing to do with their work — they stop checking. Personalization breaks that cycle: when employees consistently encounter content relevant to their role, they have a reason to return. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), organizations that actively cultivate engagement demonstrate measurably better retention, productivity, and customer outcomes. Personalized content delivery is one of the structural conditions that produces that result rather than leaving it to chance. **Compliance and security AI** monitors for PII exposure and suspicious activity patterns, built on SAML 2.0 and OAuth 2.0 authentication standards. "Secure intranet" has become the fastest-moving competitive positioning theme in the category — five major competitors now lead with security governance as a primary claim. MangoApps' compliance AI is built into the core platform rather than offered as a governance add-on. For enterprise buyers in regulated industries — healthcare, financial services, and government contracting — named protocol support is a practical evaluation criterion. For organizations where frontline workers access the platform from personal mobile devices, security architecture that accounts for unmanaged device access is a different design problem than security built for a corporate laptop fleet. **Talent management AI** connects employee profiles and stated competencies to help managers identify people for projects or roles based on actual skills. For organizations using [employee engagement surveys and questionnaires](/solutions/employee-engagement) to identify workforce capability gaps, this turns survey outputs into operational data — connecting what employees report about their skills to what managers can act on, rather than waiting for an annual review cycle to surface the same information. **Operations and workflow AI** tracks distributed processes and surfaces exceptions before they become missed deadlines. For operations teams managing frontline or field workforces, this provides completion visibility without requiring managers to manually chase status across disconnected tools. The scope is specific: this capability identifies when a defined process is not completing as expected, in time to intervene. It does not replace process design, and it does not manage workflows that were never structured in the first place. For industries where compliance and audit trails matter — healthcare, manufacturing, financial services — having automated verification of task completion is itself a governance requirement, not merely an efficiency gain. ## What the access architecture actually determines The seven categories above describe what happens when employees engage with the platform. Whether they engage is decided earlier — by whether they can reach it at all. This distinction separates AI-driven engagement platforms that produce measurable results from those that produce better reports for the users who were already logging in. TeamHealth consolidated more than 200 separate systems into a single MangoApps mobile dashboard, giving clinical and administrative staff one unified place to find information, complete tasks, and communicate. The AI layer — search assistance, personalization, workflow visibility — functions because the consolidation first removed the access fragmentation that had made consistent use impractical. AI features do not produce adoption when the path into the platform is itself an obstacle. OU Health achieved 87% workforce engagement within months of launching a branded MangoApps application for clinical staff. That adoption rate is not a statement about AI sophistication — it is a statement about access design. When employees have a mobile application built for their organization, accessible without corporate credentials or a VPN, the adoption barrier is removed first. AI personalization then has a user population to learn from and serve. The [American College of Radiology case study](/resources/case-study-american-college-radiology) documents how a distributed, multi-role organization structured its rollout to reach both desk-based and non-desk staff consistently — including the configuration decisions that made the platform accessible to employees who had historically been excluded from intranet adoption. Replacing a frontline worker costs between $4,400 and $15,000 per person depending on role and industry. Disconnection from organizational communication — missing recognition events, missing company updates, having no visibility into organizational direction — is one of the most consistent early indicators of disengagement before that replacement cost is incurred. An AI engagement platform that structurally excludes the frontline workforce does not resolve the retention problem. It narrows which employees the retention strategy applies to. ## How to evaluate AI-native intranet platforms The intranet and employee experience market has converged on AI features as a competitive differentiator over the past 18 months, which means feature comparisons date quickly. The evaluation questions that stay stable are architectural. Does the platform support email-free login for frontline workers who do not have corporate credentials? Does it work on personal mobile devices without VPN enrollment or device management requirements? Does it deliver measurable engagement outcomes — in organizations structurally similar to yours — rather than capability demonstrations in environments that already have a fully connected desk workforce? MangoApps' seven AI categories address the documented failure modes in intranet adoption: information search friction, content irrelevance, language and format accessibility barriers, security governance requirements, talent visibility gaps, and distributed process tracking. The platform supports email-free frontline access and mobile-first deployment — the architectural decisions that determine whether the AI categories reach the employees they were designed to serve, or stop at the desk workers who were already engaged. For organizations conducting structured benchmark evaluation across the competitive field — including AI capability depth, compliance criteria, and deployment patterns for mixed desk and frontline populations — [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent comparative analysis. The right question for any AI engagement investment is not how many capability categories it covers. It is whether the platform reaches the full workforce. If the honest answer is "mostly desk workers," the architectural gaps — email-free access, mobile-first design, language support — need to close before the AI layer can deliver anything meaningful for the majority of employees. MangoApps is designed so both conditions are met simultaneously. --- # Connecting & Engaging Your Retail Workforce **Author:** MangoApps **Published:** 2023-09-11 **Category:** retail How To Improve Retail CommunicationMore often than not, retail employees work without email, computers, desks, and other tools available to office employees.... # Connecting and Engaging Your Retail Workforce: A Complete Guide Retail employees face communication challenges that office workers rarely encounter. They work without corporate email, rarely sit at a desk, spread across a store floor during every shift, and rotate schedules that make it nearly impossible to gather everyone in the same room at the same time. The result: a workforce that is structurally disconnected from the information, recognition, and training it needs to perform well and stay. This guide synthesizes the six most important dimensions of retail workforce engagement — communication channels, mobile access, engagement tactics, burnout prevention, surveys, and retention ROI — into one complete answer. Deeper dives on each topic are linked at the end. --- ## Why Retail Workers Are Structurally Underserved by Standard Communication Tools Approximately 80% of the global workforce is deskless (per Emergence Capital), and retail associates make up a large share of that group. Yet most internal communication infrastructure — intranets, email newsletters, desktop portals — was designed for employees who sit at a computer for eight hours a day. The numbers on intranet adoption illustrate the gap clearly. According to Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use one daily. SWOOP Analytics found that the average employee spends just six minutes per day using intranet tools. Meanwhile, IDC estimates that employees spend 2.5 hours per day searching for information they cannot easily find. For a retail associate trying to locate a product policy, check a schedule change, or complete a compliance module before a shift starts, that friction is not a minor inconvenience — it is a direct barrier to doing the job. The practical consequence is that store associates often rely on informal channels: a text from a manager, a paper printout in the break room, or word of mouth from a coworker on the previous shift. These channels are inconsistent, untracked, and impossible to scale across multiple locations. --- ## The Business Case for Getting This Right Employee engagement in retail is not only a morale question — it is a measurable cost item. Replacing a frontline retail employee costs between $4,400 and $15,000, depending on role and location (per industry estimates cited on the MangoApps mobile app product page). In a sector where annual turnover regularly exceeds 60%, those replacement costs compound quickly into a material P&L impact. Framing disconnected frontline workers as a measurable cost — rather than a soft HR concern — changes the conversation at the leadership level. A CFO who might dismiss an "engagement initiative" will pay attention to a retention program that demonstrably reduces a $10,000-per-head replacement cycle. PetSmart's experience offers a concrete benchmark. After deploying a mobile-first [employee engagement software](/solutions/employee-app) platform, PetSmart achieved a 4x industry engagement multiple — a result that reflects what happens when associates can access schedules, HR self-service, training, and company news from a single app without needing a corporate email address. --- ## Building a Mobile-First Communication Channel for Shift Workers The most effective structural fix for retail communication is a single branded mobile app that serves as the one access point for everything a frontline associate needs: shift schedules, pay stubs, policy documents, training modules, team announcements, and two-way messaging with managers. A consolidated app eliminates the tool-switching burden that fragments the frontline experience. A single platform can replace 200 or more disparate systems — scheduling tools, paper bulletin boards, separate training portals, and HR ticketing systems — into one dashboard that associates access from their personal phone. CVS achieved 90% frontline adoption of a new employee experience platform within the first six months of launch, demonstrating that adoption at scale is achievable when the tool is genuinely easier to use than the alternatives it replaces. Two features matter especially in retail environments: - **Offline access.** Store Wi-Fi is often unreliable, particularly in stockrooms, loading docks, and older locations. Associates need to be able to open a document, review a training module, or read a policy update without a live connection. Offline document access and cached content close this gap. - **Push notification and SMS fallback.** For time-sensitive messages — a flash sale starting in two hours, a safety alert, a schedule change — push notifications reach associates on their phones immediately. SMS fallback ensures the message arrives even when the app is not open. These are not optional features. They are the baseline for any [employee communications](/solutions/employee-communications) tool that claims to serve a retail workforce. --- ## Strategies to Improve Retail Employee Engagement Communication infrastructure is the foundation, but engagement requires more than a working channel. The following strategies address the behavioral and cultural dimensions of keeping retail associates connected and motivated. ### 1. Role-Based and Location-Based Content Targeting Sending every message to every associate is the fastest way to train people to ignore communications. A cashier at a suburban location does not need the same update as a stock associate at a flagship urban store. AI-driven content targeting — surfacing the right message to the right associate based on role, location, and shift — reduces noise and increases the relevance of every notification an associate receives. This is the difference between a broadcast tool and an employee engagement platform. Generic "send to all" tools create alert fatigue. Personalized targeting creates the expectation that messages are worth reading. ### 2. Consistent Training Embedded in Daily Work Training and employee engagement are closely linked: associates who feel competent in their roles are more likely to stay and more likely to deliver good customer experiences. The challenge in retail is that traditional employee engagement training — classroom sessions, scheduled eLearning blocks — conflicts with shift schedules and high turnover rates. Embedding short training modules directly into the daily workflow — a five-minute product knowledge update accessible from the same app used to check schedules — removes the scheduling barrier. Associates complete employee engagement courses in the moments between tasks rather than in a separate session that requires coverage planning. For a deeper look at how to structure this approach, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers the design principles behind embedding training on employee engagement into daily operations. ### 3. Recognition That Reaches the Whole Team Recognition is one of the highest-leverage engagement tools available to retail managers, and it costs almost nothing to deliver. A public shout-out in the team feed, a peer-nominated badge, or a manager note tied to a specific customer interaction reinforces the behaviors that drive store performance. The key is visibility. Recognition delivered in a private conversation or a paper certificate in the break room reaches one person. Recognition posted in a shared team channel reaches the entire store — and signals to every associate what good performance looks like. ### 4. Two-Way Communication and Feedback Loops Engagement drops when associates feel that communication is one-directional — announcements flow down from corporate, but nothing flows back up. Building structured feedback loops into the communication channel changes that dynamic. Employee engagement surveys and employee engagement questionnaires are the most direct mechanism. Short, frequent pulse surveys (three to five questions, delivered monthly) generate actionable data on morale, workload, and manager effectiveness without the fatigue associated with annual engagement surveys. The critical step is closing the loop: sharing results with the team and describing what, if anything, will change as a result. For a practical starting point, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) includes survey design guidance relevant to frontline environments. --- ## Reducing Burnout Among Retail Associates Burnout is a specific and measurable risk in retail. Long hours, demanding customers, physical demands, and constant pressure to meet sales targets create conditions where associates disengage before they quit — a state sometimes called "quiet quitting" that is harder to detect and more expensive than visible turnover. The following practices reduce burnout risk without requiring structural changes to the business: - **Predictable scheduling.** Last-minute schedule changes are one of the most cited sources of stress among retail workers. Publishing schedules further in advance — and giving associates a mobile channel to flag conflicts or swap shifts — reduces uncertainty and gives people more control over their time. [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) covers the operational mechanics of this in detail. - **Workload transparency.** When associates understand why a particular week is high-pressure — a seasonal push, an inventory event, a store reset — they are more likely to absorb the extra demand without resentment. Context reduces the perception of arbitrary pressure. - **Accessible manager communication.** Associates who can reach their manager through a mobile app — rather than waiting for a shift overlap or hunting someone down on the floor — resolve problems faster and feel less isolated. - **Recognition during high-stress periods.** Burnout accelerates when effort goes unacknowledged. Doubling down on recognition during peak seasons (holiday, back-to-school, major promotions) counteracts the depletion effect of sustained high demand. --- ## Using Surveys to Measure and Improve Engagement Employee engagement surveys are one of the most direct ways to identify problems before they become turnover. In retail, the most effective surveys share three characteristics: 1. **Short and mobile-friendly.** A ten-minute survey that requires a desktop browser will not get completed by a shift worker. Three to five questions, optimized for a phone screen, will. 2. **Tied to specific, actionable topics.** "How satisfied are you with your job?" generates a number. "How clearly did your manager communicate this week's priorities?" generates something you can act on. 3. **Delivered at a consistent cadence.** Monthly pulse surveys outperform annual surveys for detecting early-stage disengagement, because the feedback is recent enough to be actionable. Retail-specific questions worth including in an employee engagement questionnaire: - Do you have the information you need to do your job well today? - Did you receive recognition for your work in the past two weeks? - How manageable was your workload this week? - Do you feel comfortable raising concerns with your manager? - How likely are you to recommend this store as a place to work? The last question is a frontline Net Promoter Score proxy — a leading indicator of retention risk that correlates with actual turnover data. --- ## What a Connected Retail Workforce Actually Looks Like When communication infrastructure, engagement practices, burnout prevention, and feedback loops work together, the operational outcomes are measurable. Associates know their schedules in advance. Training is completed before the shift starts, not weeks later in a classroom. Policy updates reach every associate on every shift within minutes of publication. Managers spend less time chasing people down and more time coaching. The 87% workforce engagement rate achieved within a few months of launching a branded employee app — a result documented in multiple retail deployments — reflects what happens when the structural barriers to communication are removed and associates have a single, reliable channel for everything they need. For retail organizations evaluating where to start, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides a current-state benchmark across frontline industries, including retail, [grocery](/industries/grocery), and [healthcare](/industries/healthcare). --- ## Frequently Asked Questions ### What is the most common reason retail employees disengage? Inconsistent or inaccessible communication is the most frequently cited structural cause. When associates cannot easily reach their manager, find a policy, or understand what is expected of them on a given shift, they disengage from the role rather than from the company. The fix is a reliable, mobile-accessible communication channel — not a culture initiative. ### How do you measure employee engagement in a retail environment? Short pulse surveys (three to five questions, monthly cadence), manager observation, and retention data are the three most practical measurement tools for retail. Annual engagement surveys are too infrequent to catch early-stage disengagement in a high-turnover environment. Combining a monthly survey score with a rolling 90-day retention rate gives a leading and lagging indicator pair that is actionable at the store level. ### How long does it take to see results from a retail engagement program? Measurable results — survey score improvements, reduced absenteeism, lower early-tenure turnover — typically appear within three to six months of launching a structured program that includes a mobile communication channel, consistent recognition, and a feedback loop. CVS's 90% adoption rate within six months and PetSmart's 4x engagement multiple are both examples of outcomes achieved within that window. --- ## Next Steps The structural problem for retail workforce engagement is well-defined: associates are deskless, shift-based, and underserved by tools built for office workers. The solution pattern is equally clear — a mobile-first employee experience platform that consolidates communication, scheduling, training, and HR self-service into one app, with offline access and push/SMS fallback for low-connectivity environments. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading retail and frontline organizations are structuring their employee experience investments this year, including platform selection criteria and implementation sequencing. If you are evaluating options, start with the communication channel. Everything else — engagement, training, recognition, surveys — depends on having a reliable way to reach every associate on every shift. --- # Effective Communication Strategies For Retail Associates **Author:** Mason Hager **Published:** 2023-09-11 **Category:** retail The Challenges Of Building A Retail Communication Strategy Communication strategy is the lifeblood of any successful organization, and in the dynamic world of retail, it’s paramount. However, reaching and engaging retail employees, often dispersed across multiple locations and shifts, can be a formidable task.  In this blog, we’ll explore retail communication strategies and tools (such […] # Effective Communication Strategies For Retail Associates Replacing a single frontline retail employee costs between $4,400 and $15,000 in recruiting, onboarding, and lost productivity. That figure makes retail communication strategy a financial question, not just an HR one. Every time an associate leaves because they felt disconnected from the team or uninformed about what was expected of them, the cost shows up in recruiting budgets and manager hours — not in a communication budget line that anyone is watching. According to McKinsey research, 89% of frontline workers say they would stay with their employer if leaders genuinely listened to their feedback. That statistic is a communication design problem dressed as a retention problem. The gap between what retail organizations want their associates to know and what associates actually experience day-to-day is where turnover quietly builds. This guide covers six communication practices that reduce that gap: designing for mobile without requiring corporate email, personalizing content by role and location, embedding recognition into the daily communication flow, building feedback loops that visibly close, integrating training delivery with operational communication, and measuring whether any of it is working. ## Why retail communication strategies fail in practice The structural problem is not intent. Most retail organizations want their associates informed, aligned, and engaged. The problem is that the tools they use were built for desk workers and retrofitted for the shop floor — and the mismatch is significant enough to undermine even well-resourced communication programs. According to Gartner's 2023 Digital Worker Survey, 47% of workers struggle to find the information they need at least half the time. In retail, where an associate starting a shift needs to know about current promotions, pricing changes, compliance requirements, and team announcements — often before they've clocked in — that information gap is a customer experience problem before it's a productivity problem. The instinct is to add more channels. The fix is consolidating existing ones into a channel that works for how retail associates actually operate: deskless, often without a company email address, in environments with variable connectivity, and checking in during brief windows between tasks. Adding a third or fourth communication channel increases the fragmentation problem rather than solving it. ## Design for mobile-first — and no corporate email required Over 80% of the global workforce is deskless. For retail specifically, that figure approaches 100% of store-level staff. Any communication strategy built around corporate email or desktop access has excluded the majority of its audience before the first message is sent. Part-time and seasonal staff — who often represent more than half of a store's headcount during peak periods — rarely receive company email addresses. If your communication infrastructure requires email login, your highest-turnover population is also your most disconnected one. Policy updates, recognition, training reminders, and scheduling information never reach them through the official channel, which means they're operating on word-of-mouth and assumptions. The baseline requirement for retail communication is a mobile employee app that authenticates via phone number or employee ID, handles low-bandwidth conditions, and provides offline access to documents and content. Retail stockrooms, distribution centers, and stores in areas with inconsistent mobile coverage need content that loads once and stays available — an app that requires a live connection for every interaction fails the environments where it's needed most. The scheduling dimension of frontline communication connects directly to this infrastructure decision. [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) covers how schedule visibility, shift swap requests, and real-time communication interact at the operational level — and why a disconnected scheduling tool creates the same information gaps as a disconnected communication tool. ## Personalize by role, location, and language — not just by name According to the State of the Digital Workplace & Modern Intranet, 2024, only 22% of company intranets deliver personalized content. That gap explains why associates tune out company announcements: most communications are broadcast to everyone and are therefore relevant to almost no one specifically. In retail, personalization at the content level means routing promotion updates to the departments they affect, sending food-handling compliance reminders only to associates in food service roles, and distributing language-appropriate training to associates whose first language isn't English. When content feels like it was written for someone else, it gets scrolled past — even when it's urgent. The operational requirement is persona-based targeting: a platform that lets administrators define segments by store, department, role, and language, then route content to those segments without manual overhead per message. Associates who consistently receive relevant communication engage with it more, not because the platform is sophisticated, but because they trust that what shows up in their feed is actually meant for them. That trust is hard to build and easy to lose — a single high-visibility irrelevant announcement erodes it. Employee engagement is the downstream measure of whether personalization is working. When associates feel that communications are tailored to their situation, engagement scores — including the employee engagement survey results that HR teams track — tend to move in the right direction. Relevance is the mechanism. ## Recognition as a retention mechanism, not a program supplement Nine out of ten competitors in the frontline communication category now position recognition as a strategic pillar rather than an optional feature. The business case is direct: at $4,400 to $15,000 per replacement hire, improving retention by a few percentage points across a mid-size retail operation generates more measurable value than most technology investments. The design question is whether recognition lives in a separate system or in the platform associates already use for scheduling, messaging, and announcements. Standalone recognition tools typically see low participation — the friction of opening a separate app for a specific behavior is enough to make it feel like extra work rather than a natural part of the day. When peer-to-peer and manager-to-associate recognition is embedded in the same daily workflow as shift check-ins and team announcements, the behavior becomes habitual rather than effortful. Recognition data also becomes operationally useful when it lives inside the broader communication system. Managers can identify who's engaged and who's going quiet before the situation shows up in a resignation. Operations leads can correlate recognition frequency with retention rates by location over time. That kind of analysis isn't possible when recognition sits in a tool that doesn't share data with HR or scheduling systems. For the broader context on how employee engagement and recognition are trending in frontline-heavy industries, [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) documents the engagement gaps that retail operations and HR leaders are benchmarking against — and the specific manager behaviors that have the largest impact on frontline retention. ## Feedback loops that close — visibly McKinsey research shows that 89% of frontline workers say they would stay with their employer if leaders genuinely listened to their feedback. The operative phrase is "listened to" — not "collected from." Associates can tell the difference between an organization that runs surveys and one that actually acts on what it learns. Two-way communication in retail works when the loop has a visible closure mechanism. An associate submits feedback about a scheduling policy that's creating conflicts for a portion of the team. That input either leads to a change — which gets communicated back to the people who raised it — or it doesn't, with a clear explanation for why not. Either outcome is acceptable. The silence between submission and outcome is what erodes participation. When feedback disappears into a management queue with no visible result, participation in subsequent surveys drops. Over time, the signal quality degrades: associates who don't believe their input matters stop providing useful information, while those who do respond tend to be the most dissatisfied, which skews the data toward the extreme and makes it harder to identify fixable issues. The practical design requirement is a feedback mechanism that closes the loop at the team level rather than the corporate level. The manager who owns the communication channel takes responsibility for acknowledging what came in and communicating what happened as a result — before the next survey cycle. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are rebuilding their feedback architecture to make this closure systematic rather than dependent on individual manager initiative. ## Training delivery as part of the communication infrastructure Training and organizational communication are typically managed in separate systems. In retail, that separation creates a specific operational problem: a manager preparing a team for a new seasonal promotion can't determine, without a manual export from a third-party LMS, whether required product knowledge training has been completed by the associates scheduled to work. When training delivery lives in the same platform as scheduling and communication, readiness becomes visible in context. A manager can see which associates on a given shift have completed the relevant training. An HR administrator can pull compliance completion records for a specific module by store or region in minutes, not hours — without reformatting an export from a disconnected system. Associates also complete training at higher rates when it's delivered in the same app they open every day for shift information. The completion behavior follows the habit already established around scheduling and announcements — it doesn't require a separate login, a separate notification, or a deliberate context switch. The training becomes part of the daily operational rhythm rather than something that competes with it. For a fuller treatment of what embedded learning programs look like structurally, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers the architecture behind learning delivery that actually drives completion. ## Measuring whether the strategy is working The most consistent gap in retail communication programs is measurement at the outcome level rather than the activity level. Open rates and delivery confirmations tell you that communication happened — they don't tell you whether it improved the situation it was meant to address. The outcome metrics that matter for retail communication are downstream: are associates showing up better informed about current promotions and policy changes? Has manager time spent on repeated one-on-one clarifications about shift expectations decreased? Are locations with higher communication engagement rates diverging from lower-engagement locations on retention? These questions require a communication platform that shares data with scheduling and HR systems — not one that reports only on its own activity. The measurement framework follows from the design decisions made earlier in the system build. If recognition is tracked in the same platform as communication, you can correlate recognition frequency with retention by location. If training completion is visible alongside scheduling data, you can identify readiness gaps before they surface in customer-facing interactions. If feedback loops are documented and closed, you can measure whether survey participation and response quality improve over time. ## What a working retail communication strategy looks like under pressure The retailers where communication strategies hold up share one structural characteristic: the platform associates open every day to check their shifts is the same platform that delivers announcements, training, recognition, and feedback channels. Communication is not a separate behavior requiring a separate motivation — it's a byproduct of the operational workflow already in place. That design principle — building communication into the daily habit rather than asking associates to form a new one — is what makes strategies resilient when operational pressure increases. A part-time associate working a peak-season schedule, without a company email address, in a store with intermittent connectivity, who needs to know about a price change before the shift starts and complete a 10-minute compliance module by end of week: that is the baseline condition your infrastructure needs to serve reliably. Design for that scenario, and the rest of the workforce is covered by default. The communication gaps that cost retail organizations the most — in turnover, in customer experience failures, in compliance exposure — almost always trace back to the same structural problem: a workforce that needed a reliable channel to stay informed and connected, and a set of tools that were never built for them. Closing that gap is a design decision before it's a communication decision. --- # Checklist To Fix Common Retail Communication Problems **Author:** Mason Hager **Published:** 2023-09-11 **Category:** retail In the fast-paced world of retail, keeping frontline employees well-informed and engaged is essential for smooth operations and exceptional customer service. In this checklist, we’ll explore a comprehensive set of strategies and practices designed to address common retail communication problems. From streamlined communication channels to real-time updates, consistent training, and employee recognition, this checklist serves as […] In retail, poor communication is not just an operational inconvenience — it is a measurable financial risk. Replacing a single frontline retail employee costs between $4,400 and $15,000, and per Gartner (2023), 47% of workers struggle to find the information they need at least half the time. This checklist gives retail managers a concrete set of practices to close those gaps, plus guidance on where to start. Most of these items are easier than ever to implement with an [employee app for retail](/solutions/employee-app). ## 12 Ways To Avoid Retail Communication Problems ### 1. Clear Communication Channels - Implement a modern intranet or [employee communications](/solutions/employee-communications) platform for instant updates. - Establish dedicated communication channels, such as team chats or forums. - Ensure management is easily accessible for questions or concerns. - Eliminate reliance on personal email or VPN access — frontline workers typically have neither, so any communication tool must work without them. ### 2. Real-time Updates - Share shift schedules and changes promptly. See [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) for scheduling best practices. - Communicate product launches, promotions, and pricing updates in real-time. - Use push notifications to alert employees about important news. ### 3. Consistent Training - Develop a structured onboarding program for new hires. - Provide ongoing training to enhance skills and product knowledge — this is where employee engagement training and an integrated LMS learning system pay dividends, giving associates on-demand access to courses without pulling them off the floor. - Offer digital training materials accessible on-demand via mobile. For a deeper look at building this into daily workflows, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). - Frontline employees navigating 6–8 disconnected tools daily experience measurable productivity loss and communication breakdown; consolidating training into a single hub addresses this directly. ### 4. Recognition and Feedback - Create a recognition program for exceptional performance. - Establish regular feedback sessions to address concerns and provide guidance. - Encourage peer-to-peer recognition within the team. - Make conscious efforts to improve morale and combat burnout. - Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback — structured recognition and feedback loops are a direct retention lever. ### 5. Employee Engagement - Foster a sense of community and camaraderie among employees. - Encourage team collaboration and idea-sharing. - Provide opportunities for frontline employees to participate in decision-making. - Employee engagement software that surfaces participation data helps managers identify disengaged associates before turnover occurs. ### 6. Mobile Accessibility - Ensure all communication tools and resources are mobile-friendly and require no corporate email or VPN. - Allow employees to access schedules, updates, and training on their smartphones. - Enable instant communication via mobile apps. - Consolidating frontline communications into a single mobile hub has been shown to reduce employee turnover by 26% for frontline-heavy operators. ### 7. Recognition of Achievements - Celebrate milestones such as work anniversaries and achievements. - Share positive customer feedback and success stories. - Recognize employees who go above and beyond in their roles. ### 8. Safety and Compliance - Share safety protocols and updates — including SOP operations documentation — regularly. - Ensure that all employees are aware of compliance regulations. - Conduct safety drills and training sessions as needed. - A mobile-first platform allows health and safety policy communication to frontline staff without requiring individual Microsoft licenses or VPN access. ### 9. Employee Surveys and Feedback - Conduct regular employee engagement surveys and employee engagement questionnaires to gauge satisfaction and root out retail communication problems. - Act on feedback and make improvements based on employee suggestions. - Use surveys to assess training needs and preferences. ### 10. Accessibility to Resources - Ensure that all necessary resources, including product information and policies, are readily accessible. - Maintain a centralized repository for easy access to documents and manuals. Per Gartner (2023), 47% of workers struggle to find necessary information at least half the time — a searchable, mobile-accessible knowledge base directly addresses this gap. - Provide digital resources for quick reference. ### 11. Recognition Boards - Create an online recognition board where employees can acknowledge each other's accomplishments. - Encourage employees to regularly contribute to the board. - Recognize employees who receive the most mentions or contributions. ### 12. Crisis Communication Plan - Establish a clear plan for communicating during crises or emergencies. - Ensure that employees know where to find updates and safety instructions. - Test the crisis communication plan regularly. --- ## Where to Start: The Three Highest-Priority Items With twelve items on this list, retail managers reasonably ask: *which three should we tackle first?* The answer depends on your current state, but the following sequence works for most mid-size retail operations: **First: Mobile-accessible communication channels (Item 1 + Item 6).** If frontline associates cannot receive updates without a corporate email address or VPN, nothing else on this list functions reliably. Establishing a no-email, no-VPN mobile hub is the prerequisite. Expect a 4–8 week rollout for a single-location pilot; multi-location rollouts typically reach 90% frontline adoption within the first six months. **Second: Consistent training with an integrated LMS (Item 3).** Once the communication channel exists, attach on-demand employee engagement training and compliance courses to it. This closes the productivity gap caused by disconnected tools and directly supports safety and compliance (Item 8) without additional infrastructure. **Third: Structured recognition and employee engagement surveys (Items 4, 7, 9).** Per McKinsey research, 89% of frontline workers will stay if leaders listen to their feedback. A recognition program paired with regular employee engagement questionnaires creates the feedback loop that sustains everything else. This phase typically takes 6–10 weeks to design and launch. **Realistic timeline:** Most retail organizations can have Items 1, 6, and 3 operational within 90 days. Full checklist implementation — including crisis communication planning and recognition boards — typically lands in the 6–9 month range for a 50–500 associate operation. **The financial case:** At $4,400–$15,000 per frontline replacement, even a modest improvement in retention pays for the tooling. Replacing paper processes and siloed systems with a single mobile hub reduced employee turnover by 26% for one frontline-heavy operator. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides additional benchmarks on frontline communication ROI. --- ## Frequently Asked Questions ### Which retail communication problems cause the most turnover? Lack of feedback loops and poor recognition are the leading drivers. Per McKinsey research, 89% of frontline workers say they would stay if leaders actively listened to their input — yet most retail operations lack a structured mechanism for collecting and acting on that input. Employee engagement surveys and peer recognition programs (Items 4, 7, 9) address this directly. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading retailers are closing this gap. ### How do I measure whether our retail communication is improving? Three leading indicators work well for retail: (1) employee engagement survey scores tracked quarterly, (2) time-to-information — how long it takes an associate to locate a policy or product update — and (3) voluntary turnover rate by store. Per Gartner (2023), 47% of workers struggle to find information at least half the time; reducing that figure is a concrete, measurable outcome. Per McKinsey research, 81% of leading companies effectively use data and analytics tools to track workforce metrics — retail operators should apply the same discipline to communication effectiveness. ### What does good employee engagement software look like for retail? The minimum viable feature set for frontline retail includes: no-email/no-VPN mobile access, push notifications for real-time updates, an integrated LMS learning system for on-demand training, peer recognition tools, and an employee engagement survey module. Platforms that consolidate these into a single hub eliminate the 6–8 disconnected tools that fragment frontline communication. See how grocery and similar frontline-heavy industries approach this at [MangoApps for Grocery](/industries/grocery). --- ## MangoApps Helps Fix Retail Communication Problems MangoApps is designed to address the checklist items above in a single platform. The modern intranet delivers real-time updates to every employee without requiring corporate email or VPN access, eliminating the most common barrier to frontline reach. Consistent training is supported through accessible digital resources and an integrated LMS, facilitating onboarding, employee engagement training, and skill development on-demand. The platform also supports employee recognition and engagement with recognition boards and instant messaging, and its mobile accessibility ensures that your frontline team stays connected on the sales floor. For a detailed look at how MangoApps has been evaluated against competing intranet platforms, see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms). Read more about retail communication strategy, our employee app for retail, or customer stories from Superdrug and A.S. Watson. --- # 10 Strategies to Reduce Burnout Among Retail Associates **Author:** Mason Hager **Published:** 2023-09-11 **Category:** retail In the world of retail, long hours, demanding customers, and constant pressure to meet targets are the norm. As a result, burnout is a prevalent and concerning issue. Burnout not only affects the well-being of retail associates but also impacts the overall success of businesses. In this blog, we’ll explore strategies to reduce burnout among […] In retail, long hours, demanding customers, and constant pressure to meet targets are the norm. Burnout is a direct P&L issue: replacing a single frontline retail employee costs between $4,400 and $15,000, making turnover-driven attrition far more expensive than the investments required to prevent it. This post outlines 10 concrete strategies to reduce burnout among retail associates and explains how the right communication and [employee engagement](/solutions/employee-engagement) tools can support each one. ## The Burnout Challenge in Retail **Let's dive into 10 strategies that can help reduce burnout among retail associates:** ### 1) Establish Clear Expectations and Work-Life Boundaries In many companies, the real root of issues with staff burnout is some combination of common retail communication problems. These are further exacerbated by irregular schedules and lack of clearly established expectations and boundaries. To combat this, managers should strive to craft schedules that are both predictable and accommodating. Retail associates should know well in advance when they are expected to work. This allows them to establish firm boundaries for their off-hours. Managers can also create a system where workers can swap shifts with each other (with managerial oversight). If done well, this provides added flexibility while maintaining operational consistency. By doing this, retail workers are better able to enjoy their personal lives and manage stress. This means they'll come to work more focused and recharged. For a deeper look at building smarter shift structures, see [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling). ### 2) Invest in Training and Skill Development Feeling ill-equipped to handle job responsibilities is a leading cause of burnout. Retail associates need consistent, in-depth training sessions that go beyond basic orientation. Such programs should cover the intricacies of customer service, such as handling difficult clients, the POS system and inventory. You might even address soft skills like conflict resolution and stress management. Continuous learning programs — including e-learning modules delivered through an embedded LMS learning system — can help associates grow in their roles and stay engaged through employee engagement training that fits into their daily workflow rather than pulling them off the floor. Research consistently shows that training and employee engagement are directly linked: associates who see a clear path for skill development are significantly less likely to disengage. For a practical framework on making learning stick, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) is a useful starting point. ### 3) Empowerment through Decision-Making The feeling of powerlessness is a significant contributor to burnout. Empowering retail associates to make choices about customer service, inventory, or even merchandising can give them a sense of control and ownership over their work. Managers can establish guidelines and parameters within which employees can operate autonomously. This approach not only minimizes the burden on managerial staff but also boosts employee engagement and satisfaction. Empowered employees feel more connected to their roles and the organization, reducing the chances of feeling burned out. ### 4) Recognition and Rewards Programs Feeling unrecognized in the workplace is a surefire route to disengagement and eventually, burnout. Companies should establish recognition programs that celebrate both big and small wins. These can be as elaborate as quarterly awards ceremonies, or as simple as a daily shoutout during team meetings. Monetary incentives, gift cards, or extra paid time off are other great ways to show appreciation. The idea is to create a culture where hard work is consistently acknowledged, making employees feel valued and less prone to burnout. One example of what structured recognition can achieve: a large retail and pharmacy organization reached 87% workforce engagement within a few months of launching a branded employee app. For a detailed look at building a recognition program that scales, see [From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program). ### 5) Foster a Supportive Work Environment A toxic or isolating work environment can significantly contribute to employee burnout. To counter this, retail environments should promote a culture of inclusivity, teamwork, and mutual support. Regular team-building exercises can strengthen interpersonal relationships. Open-door policies and anonymous suggestion boxes can make associates feel their opinions are valued. Managers should be trained to identify signs of workplace stress and to offer appropriate support, either directly or by facilitating access to mental health resources. Frontline employees lose over 4 hours per week switching between disconnected systems, compounding cognitive load and accelerating burnout — consolidating communication into a single platform directly reduces that friction. ### 6) Encourage Regular Breaks Long hours of repetitive tasks can quickly lead to physical and emotional fatigue, a stepping stone to burnout. Promoting regular breaks, even if they are just 5-10 minutes long, can have a profound impact on well-being. Encourage associates to step outside for fresh air, have a healthy snack, or engage in quick physical exercises like stretching. Rotating tasks among associates can also prevent the monotony and physical strain that lead to burnout. ### 7) Stress Management and Well-Being Programs High-stress levels are often an early warning sign of impending burnout. Retail organizations should consider offering stress management solutions like in-house workshops or subsidized memberships to wellness apps that offer guided meditations and mindfulness exercises. Employee wellness programs could also include access to fitness centers or partnerships with local gyms, nutritional counseling, or even bi-weekly or monthly group yoga or meditation sessions. All these initiatives help create a holistic approach to employee well-being, significantly reducing stress and the risk of burnout. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading organizations are structuring well-being investments for frontline workforces specifically. ### 8) Flexibility and Work-Life Balance Traditional working hours don't fit everyone's lifestyle, especially in retail. Where possible, offering flexible work schedules can make a meaningful difference. Consider implementing different shifts, part-time options, or even work-from-home days for roles that allow for it. These changes show empathy toward associates' personal lives and can result in increased productivity and decreased burnout. ### 9) Regular Check-Ins and Feedback Periodic one-on-one meetings between managers and associates are essential for more than just reviewing performance metrics. They serve as a confidential setting where employees can voice their concerns, frustrations, or needs without fear of judgment. These regular check-ins can also include wellness assessments, goal-setting discussions, and constructive feedback, all aimed at identifying and addressing early signs of burnout. Both parties benefit from these interactions, leading to a healthier and more proactive work environment. It is always good to also do these sorts of efforts at scale with employee engagement surveys or employee engagement questionnaires — see our guide to the most valuable retail staff survey questions for some ideas to get you started. ### 10) Monitor Workload and Delegate Effectively A key reason many retail associates experience burnout is being overloaded with tasks that are both numerous and time-sensitive. Effective workload management involves regular audits of task lists, clearly defined roles, and streamlined delegation procedures. Managers should ensure that workloads are spread out evenly among the team and can use project management tools to track task progress. Such systems create transparency and accountability, helping to balance the demands of the job with the emotional and physical well-being of the associates. --- ### Enabling frontline retail employees at Kelly-Moore Paints Learn how Kelly-Moore Paints enabled its frontline retail workforce with a modern employee app. READ case study --- ## How A Modern Intranet Can Reduce Retail Burnout A modern intranet plays a pivotal role in alleviating burnout among retail associates. By providing a centralized platform for communication, training, and resource accessibility, it streamlines processes and reduces the burden of information overload. Retail associates can access critical updates, training materials, and shift schedules with ease, eliminating the need for constant searching and follow-ups. Per IDC, employees spend an average of 2.5 hours per day searching for information — time that compounds stress and erodes focus on the floor. Moreover, the ability to customize their intranet dashboards ensures that associates see information that is directly relevant to their roles, enhancing productivity and reducing unnecessary stress. That said, adoption matters as much as availability. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use intranet tools daily. Per SWOOP Analytics, the average daily time spent using intranet tools is just six minutes. The difference between a tool that collects dust and one that reduces burnout is mobile-first access: per Emergence Capital, 80% of the global workforce is deskless, meaning retail associates need a no-email-required mobile app that delivers schedules, recognition, and employee engagement courses directly to their phones. Organizations that have achieved 90% frontline adoption within the first six months share one common factor — structured digital onboarding tied to a single branded app. Additionally, the sense of community fostered by features like recognition boards and feedback channels can boost morale, contributing to a more positive and supportive work environment. Ultimately, a modern intranet empowers retail associates with the tools and resources they need, reducing burnout by simplifying tasks and promoting a healthier work-life balance. Couple the right platform with a well-crafted retail communication strategy, and the results will speak for themselves. [The Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026 and beyond](/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) is a practical resource for evaluating your options. ## MangoApps MangoApps stands out as an excellent choice for a modern intranet in the [retail industry](/industries/retail). Its intuitive platform and mobile app empower retail associates to access real-time updates, training resources, and essential information effortlessly, fostering a more informed and engaged workforce. MangoApps' communication features, including instant messaging and discussion forums, promote collaboration among associates, enhancing teamwork and problem-solving capabilities. Additionally, its user-friendly interface ensures that retail associates can navigate the platform with ease, even during busy shifts. MangoApps not only streamlines internal communication but also nurtures a sense of community and connection among retail teams, making it a valuable asset for any retail business striving to reduce burnout and excel in the competitive retail landscape. To learn more, read customer stories from A.S. Watson and Superdrug, or schedule a demo with our team. ## What Should Retail Managers Do First to Address Burnout? If you are prioritizing, start with the two levers that have the fastest measurable impact: schedule predictability and recognition. Unpredictable schedules are the single most cited driver of retail stress, and recognition programs can be launched with existing tools in days rather than months. Once those are in place, layer in structured employee engagement training through an embedded LMS learning system so associates build skills without leaving the floor. Use an employee engagement survey at the 30- and 90-day marks to measure whether the interventions are working before investing in larger well-being programs. ## How Does Employee Engagement Software Reduce Retail Burnout? Employee engagement software reduces burnout by removing the friction points that exhaust frontline workers: hunting for schedules, missing recognition, and being unable to access training on a mobile device. A single branded app that requires no corporate email delivers all three — schedules, shoutouts, and learning modules — in one place. Retail associates who lack access to a mobile-first, no-email-required communication tool are effectively cut off from the recognition, scheduling, and training resources that reduce burnout. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines how leading retailers are deploying employee engagement software to close that gap. ## How Do You Measure Whether Burnout Reduction Strategies Are Working? Track three leading indicators: voluntary turnover rate, absenteeism frequency, and employee engagement survey scores. Voluntary turnover is the most direct financial signal — given that replacing a frontline retail employee costs between $4,400 and $15,000, even a modest reduction in attrition produces a measurable return. Pair quantitative data with qualitative signals from regular check-ins and anonymous employee engagement questionnaires to catch early warning signs before they become departures. For broader context on what the data says about workforce engagement trends, [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace) is a useful benchmark. --- # MangoApps Bolsters Customer Confidence With ISO 27001 Certification **Author:** MangoApps **Published:** 2023-08-30 **Category:** press-release With the addition of the ISO 27001:2022 certification, MangoApps further substantiates its leadership as the most secure unified employee communications and engagement platform. # MangoApps Bolsters Customer Confidence With ISO 27001 Certification MangoApps has received ISO 27001:2022 certification, making it the only unified employee hub that simultaneously holds FedRAMP Authority to Operate (ATO), HITRUST, ISO 27001:2022, and SOC 2 Type II certifications. The announcement closes a gap most enterprise workforce platforms leave open: independent, audited security verification that covers not just data centers but the full lifecycle of how employee information is created, transmitted, stored, and deleted. For organizations in regulated industries — healthcare, financial services, federal government — this combination is not a marketing credential. It is the basis on which procurement and InfoSec teams make vendor decisions. Each certification addresses a different compliance surface, and the four together mean MangoApps has cleared security reviews designed for the most demanding regulatory environments in the world. "We are excited to achieve yet another significant milestone in our commitment to information security and compliance," said Sameer Malhotra, Associate Director of Information Security and Compliance at MangoApps. "By deploying the highest level of encryption possible, alongside multi-factor authentication, access controls, regular security audits, reliable AWS cloud infrastructure, and the latest automation tools, we're able to ensure that our customers' data remains confidential, intact and available only to authorized personnel." ## What ISO 27001:2022 actually requires ISO 27001:2022 is the international standard for Information Security Management Systems (ISMS). Unlike point-in-time assessments, it requires organizations to implement and continuously audit controls across the full lifecycle of information: how data is created, stored, transmitted, accessed, and deleted. In practice, this means MangoApps has implemented verifiable controls across data encryption at rest and in transit, access management that limits who can view or export sensitive workforce data, incident response procedures for identifying and containing breaches, and ongoing risk treatment processes for identifying new threats and updating controls accordingly. The certification is issued by an independent accredited body and is valid for three years, with mandatory surveillance audits conducted annually. It is not a self-assessment. For enterprise procurement teams, this distinction matters: ISO 27001 certification provides an auditable, third-party-verified basis for vendor security reviews that self-reported compliance frameworks cannot replicate. ## Why this matters for the 80% of your workforce who aren't at a desk Most security certification announcements are written for IT and legal teams. ISO 27001 has a different practical consequence for organizations with large frontline workforces — and that consequence is worth naming explicitly. Approximately 80% of the global workforce is non-desk or frontline. These employees — in healthcare, retail, manufacturing, logistics, and field services — access company systems from personal mobile devices, often without corporate email addresses or IT-provisioned credentials. They are the workers most likely to be excluded from secure platform access during their first days on the job, and the users most likely to fall outside traditional IT security perimeters. ISO 27001 controls govern secure mobile access, ensuring that the authentication mechanisms protecting employee data extend to mobile and BYOD environments. For frontline workers, this translates to three concrete capabilities: **Secure mobile access from day one**: Enrollment via QR code or SMS verification, without requiring corporate email, means frontline workers access onboarding documentation on a platform that meets the same security standard as any office workstation. **Multilingual policy delivery with acknowledgement tracking**: Acknowledgement tracking confirms which employees have read and confirmed receipt of policy or procedure updates, enabling targeted follow-up for compliance — a capability that matters in regulated-industry contexts where documentation of employee awareness is itself a compliance requirement (per Staffbase case study data). **Automated offboarding controls**: Automated offboarding workflows triggered by employee departure dates reduce the window during which a departing employee retains system access — a concrete security risk-reduction mechanism that directly limits data exposure when employees leave (per Workvivo product documentation). These are not abstract controls. They are the mechanisms that determine whether security certification translates into reduced risk for the majority of an organization's workforce, not just for the portion that sits at a desk. ## What the four certifications cover — and which industries they serve MangoApps holds four distinct security certifications. Each addresses a different compliance surface, and each opens MangoApps to a different set of regulated customers. **ISO 27001:2022** is a globally recognized standard for information security management, applicable across industries and geographies. It is the framework most frequently required by international enterprise procurement processes and cross-border data handling agreements. **FedRAMP Authority to Operate (ATO)** is a U.S. federal government authorization for cloud services. It is one of the most demanding cloud security authorizations available, and a prerequisite for any vendor serving U.S. government agencies. Very few workforce platforms have achieved it. **HITRUST** is a certifiable framework widely adopted in healthcare. It incorporates requirements from HIPAA, NIST, ISO, and other standards into a single, auditable control set. For healthcare organizations evaluating employee hub platforms, HITRUST certification reduces the time required for internal security reviews. **SOC 2 Type II** evaluates the operating effectiveness of security, availability, processing integrity, confidentiality, and privacy controls over a defined period — typically six to twelve months. Unlike a point-in-time audit, SOC 2 Type II provides evidence that controls were functioning consistently across an extended window. Together, these four certifications mean MangoApps has been independently audited against the security requirements of federal agencies, healthcare organizations, global enterprises, and international regulators. As documented in the [IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment](/resources/idc-marketscape-2024), MangoApps' security posture compares favorably across the broader market of cloud based productivity applications — and the four-certification stack represents a combination no other unified employee communications and engagement platform currently holds. ## What specific risks ISO 27001 mitigates for customers For organizations evaluating cloud based productivity apps for regulated or security-sensitive environments, ISO 27001 certification addresses several concrete risk categories. **Unauthorized access**: Access control requirements limit who can view, edit, or export sensitive employee and operational data. For organizations handling workforce data across multiple locations or shifts, granular access management is the first line of defense against both external breaches and internal data misuse. **Data breach exposure**: Encryption and incident response controls reduce both the likelihood and the blast radius of a breach. The ISO 27001 framework requires documented incident response procedures — not just technical controls, but the organizational response protocols that activate when a breach occurs. **Insider threats and offboarding gaps**: Automated offboarding workflows reduce the window during which a departing employee retains access to systems. For shift-based operations with high turnover, this is a material risk reduction (per Workvivo product documentation). **Policy non-compliance documentation**: Acknowledgement tracking creates an auditable record that employees in regulated roles have received and confirmed critical policy updates. For healthcare organizations subject to HIPAA or manufacturing operations with OSHA requirements, this documentation capability directly supports compliance audits (per Staffbase case study data). **Vendor risk assessments**: For enterprise procurement teams, ISO 27001 certification provides a standardized, internationally recognized basis for third-party risk assessments — reducing the time and cost of security reviews. The [MangoApps & Microsoft Integration Guide](/resources/mangoapps-microsoft-integration-guide) documents how the platform integrates with enterprise systems including Microsoft 365, giving security teams visibility into how data flows across connected productivity applications. For organizations in healthcare, financial services, or government — industries where MangoApps already holds FedRAMP and HITRUST authorizations — ISO 27001 adds a globally portable compliance credential that supports international operations and cross-border data handling agreements. ## What this means for you: Three questions compliance teams ask The certification is the announcement. The practical question for existing and prospective customers is what to do with it. **How do you verify MangoApps' ISO 27001 certification?** ISO 27001 certifications are issued by accredited certification bodies and are publicly registered. MangoApps' certification details — including the issuing body, scope, and validity period — are available directly from the MangoApps security and compliance team. For procurement and vendor risk processes, MangoApps can provide the certification documentation, the scope statement, and the annual surveillance audit history. **Does ISO 27001 certification affect existing customer contracts?** ISO 27001 is a platform-level certification, not a contractual addendum. Existing customers whose contracts include security compliance requirements should confirm with their MangoApps account team whether ISO 27001 certification satisfies those requirements, or whether a formal amendment is appropriate. For prospects in regulated industries, the certification can be cited in Data Processing Agreements and vendor security questionnaires. **What should compliance teams do next?** For organizations in regulated industries actively evaluating employee hub platforms, the practical next step is to request MangoApps' security documentation package — which includes the ISO 27001 certification, SOC 2 Type II report, and FedRAMP authorization details — for review by internal InfoSec and legal teams. The [How An Employee SuperApp Transforms The Workplace](/resources/how-an-employee-superapp-transforms-the-workplace) resource provides additional context on how MangoApps' platform capabilities interact with compliance requirements in operational environments. ## How long the certification lasts and what customers should know ISO 27001 certification is valid for three years from the date of issuance. During that period, the certifying body conducts annual surveillance audits to verify that the ISMS remains effective and that identified nonconformities have been addressed. At the end of the three-year cycle, a full recertification audit is required. This structure means MangoApps' security controls are not a one-time snapshot. They are subject to ongoing independent review — annually for surveillance, and every three years for full recertification. For customers in regulated industries whose own compliance frameworks require vendor certification to remain current, this structure is the relevant standard of evidence: the certification does not simply expire without action; it is continuously maintained or revoked. Customers who include ISO 27001 in vendor risk assessments should track the certification's validity period and request updated documentation ahead of their own audit cycles. MangoApps' combination of FedRAMP ATO, HITRUST, ISO 27001:2022, and SOC 2 Type II certifications represents independent verification across every major regulatory framework relevant to enterprise workforce platforms — the evidence base that regulated-industry security due diligence requires. --- # Why SharePoint Is Not Free **Author:** Mason Hager **Published:** 2023-08-28 **Category:** replace-sharepoint SharePoint is not free. It’s a common misconception that SharePoint is an ‘inexpensive’ platform to host your organization’s resources and information. If your organization has other Microsoft products and are looking to start leveraging an internal intranet, you might think that SharePoint is the logical next step. SharePoint is not a free platform. It’s riddled […] SharePoint is not free. It’s a common misconception that SharePoint is an ‘inexpensive’ platform to host your organization’s resources and information. If your organization has other Microsoft products and are looking to start leveraging an internal intranet, you might think that SharePoint is the logical next step. SharePoint is not a free platform. It’s riddled with hidden costs and fees that can quickly become overwhelming to any organization. Unless you have a fully dedicated IT team that can support such an extensive implementation, SharePoint will quickly become a much more labor-intensive & resource-intensive project than anticipated. In this article, we’ll discuss why SharePoint is not free, and dive into all the hidden costs associated with implementation and the cost to maintain the platform.  The SharePoint ‘Trap’ The reason companies opt for SharePoint is because it can seamlessly integrate with the Microsoft applications your company is most likely already using and can serve as a decent tool for file storage and management. Although SharePoint has some features of a modern intranet, it is limited in many aspects. Beyond its core purpose as a file storage platform, added features in SharePoint typically require custom development. As a piece of software included with Microsoft Office 365, SharePoint will presumably fit right into the company toolkit. As the IT department’s goal is to use technology to make the company’s employees more productive, this feels like a clear win. They think that adopting SharePoint will create a single source of truth, where files and information are easy to find.  However, IT teams who make these assumptions miss a few crucial points. First off, SharePoint’s native interface does not offer a personalized employee experience. Employees today are accustomed to personalization. They use apps every day, both professionally and personally, that intelligently sort through information and put the most important and/ or relevant items front and center. Many IT teams see SharePoint’s ability to be a hub for everything as its main strength. However, this is a false premise that misses a key part of the formula for a true work hub. replace sharepoint Business users do not need a database of every single file the company has. They need a platform that cuts through the noise, parsing through documents, resources, updates, events, and programs to put action-oriented and mission-critical items front and center.  6 Reasons Why SharePoint Is Not Free #1 – Devoting IT resources to maintain SharePoint For organizations with large IT teams available to configure and maintain the platform, SharePoint could be an ideal fit. However, most companies simply don’t have the IT resources available to implement and maintain the platform.  Organizations can find the complexity of SharePoint to demand a skilled IT team to ensure proper configuration, troubleshooting, and integration with other tools. This can divert resources away from other critical business initiatives and creates a hefty financial burden on your organization.  #2 – Poor user experience SharePoint is not an intuitive and easy-to-understand platform. You’re going to need to educate your workforce on how to use it properly. This will result in tons of training/education costs just to simply teach your employees how to use the platform. In addition, SharePoint provides a poor & fragmented user experience. It is challenging and time-consuming to use and can lead to diminished productivity and decreased employee engagement.  #3 – Licensing costs A major problem with SharePoint is that it fails to include frontline employees in the initial ‘free model.’ This means that in addition to all the costs you’re already paying, you now have to pay user licensing costs for people to use the platform. It can become extremely expensive as you scale your organization. In addition, SharePoint simply isn’t built for frontline workers. Their mobile experience is going to be fragmented and insufficient.  #4 – Third-party tools to fill tech gap While it is expensive to integrate third-party tools into your SharePoint implementation, it is also important to be conscious of the costs of adding to your tech stack.  SharePoint does not provide a unified employee experience, and as a result, is dependent on additional third-party tools to fill in the gaps. Each one of these tools comes with its own cost and can significantly add to the cost of your tech stack. Your organization must weigh the benefits of a diverse tech stack against the potential financial strain you’ll face. There are alternative solutions, such as MangoApps, that can offer a more cost-effective way to achieve your employee experience goals.  #5 – Security risks Due to SharePoint’s limitations, employees may seek out other tools that are unsanctioned by the IT department to collaborate and communicate. This can lead to massive security/compliance risks for your organization.  It’s also worth noting that if you’re already using an outdated SharePoint version, you likely have stopped receiving support and are forced to manually patch any security fixes, incurring additional costs and amplifying the likelihood of falling out of compliance with industry standards/regulations. #6 – Additional costs to consider Here is a list of additional costs you’ll likely encounter if you decide to implement SharePoint: Implementation costs, migration costs, training costs, integration costs, add-ons, additional IT employees, SharePoint consulting fees, maintenance costs, and so much more.  Think about everything that will be required to get your SharePoint environment up and running, and assign dollar amounts to each step to calculate your expected initial cost.  Learn more about the limitations of SharePoint View this whitepaper to learn more about the limitations of SharePoint, and how a modern intranet platform might be a better fit for your organization’s needs. learn more Introducing MangoApps – A SharePoint Alternative MangoApps is the ultimate SharePoint replacement. MangoApps is an Employee SuperApp for organizations with a frontline workforce. With MangoApps, you’re able to give 100% of your workforce all the tools they need in one employee app to increase productivity, improve retention, and boost employee engagement. The platform is customizable and offers a wide range of unique functionalities aimed at solving any business need. MangoApps includes all the tools you need to provide a unified employee experience. Just turn on the tools you want and turn off the ones you don’t. Unlike SharePoint, with MangoApps employees can be kept engaged and informed and have instant access to the information they need, when they need it. Learn How Our Customers Use MangoApps Why SharePoint Was Insufficient – National Church Residences Case Study Enabling Two-Way Communication With MangoApps – Morningstar Living Case Study Harnessing An Employee SuperApp To Replace SharePoint – OU Health Case Study --- # How Much Does On-Premise Intranet Cost? A Pricing Breakdown **Author:** Luke Walton **Published:** 2023-08-28 **Category:** on-premise-intranet Understanding the costs associated with setting up an on-premise intranet is essential, especially for industries where data privacy and system integrity are a priority. Healthcare facilities, government agencies, financial institutions, and other highly regulated sectors often gravitate towards on-premise intranet solutions due to their adaptability to meet stringent compliance and security requirements. Let’s delve into […] # How Much Does On-Premise Intranet Cost? A Pricing Breakdown On-premise intranet costs vary widely, but buyers deserve concrete numbers before they can budget. For a mid-size enterprise of around 1,000 users, first-year total cost of ownership — combining licensing, implementation, and customization — typically ranges from **$130,000 to $426,000** (per MangoApps blog / Awesome Technologies Inc. 2025 cost model). Smaller deployments start lower; larger, more complex environments climb higher. The sections below break down every cost driver and then synthesize them into low, mid, and high scenarios so you can leave this page with a working budget estimate. --- ## Typical Cost Ranges by Company Size Before diving into individual cost factors, here are three illustrative scenarios that combine the categories covered later in this article: | Scenario | Users | Estimated Year-1 Cost | Estimated Annual Maintenance | |---|---|---|---| | Small organization | 50–100 | $80,000–$150,000 | $12,000–$20,000 | | Mid-market | 500–1,000 | $130,000–$426,000 | $40,000–$80,000 | | Large enterprise | 5,000+ | $500,000–$1,200,000+ | $100,000–$250,000+ | Implementation alone — before ongoing maintenance or customization — typically runs **$15,000 (basic) to $150,000+ (enterprise)** depending on scope and vendor. These figures are starting points; the 15 cost drivers below explain what pushes a budget toward the high end. --- ## Why On-Premise? The Context Behind the Cost An intranet, by definition, is a private network that gives employees access to internal tools, documents, and communications. On-premise means that network runs on hardware your organization owns and controls rather than on a vendor's cloud. Healthcare facilities, government agencies, and financial institutions frequently choose this model because it lets them meet strict compliance requirements and keep sensitive data within their own perimeter. The trade-off is that on-premise deployments carry costs that cloud subscriptions bundle invisibly. Understanding each category is the first step toward an accurate budget. One important context note: according to Social Edge Consulting, 91% of organizations operate an intranet — yet only 13% of employees use it daily, and nearly a third never log in at all. That adoption gap is a real cost risk. A well-deployed intranet should target **90% frontline adoption within the first six months** as a benchmark for ROI. Budgeting adequately for training, change management, and mobile access is what separates a used intranet from an abandoned one. --- ## The 15 Cost Drivers — and What Each One Actually Costs ### 1. Number of Licenses Per-user licensing is usually the largest single line item. Larger organizations need more licenses, and enterprise tiers carry higher per-seat rates. Factor in contractors and part-time workers who may need access. ### 2. Intranet Functionality and CMS Capabilities Basic packages cover document storage and announcements. A CMS intranet — one with a built-in content management system for creating and governing pages — costs more but reduces reliance on IT for routine updates. Regulated sectors often need additional modules: patient record integration for healthcare, audit-trail workflows for financial services. These specialized requirements add measurable scope to the build. Regulated-sector organizations increasingly require persona-based, role-aware content governance and semantic search that respects existing permissions — capabilities that add measurable scope to on-premise build costs (per Akumina / product page research). Budgeting for these features upfront avoids a costly upgrade cycle later. ### 3. Hardware and Infrastructure On-premise hosting requires servers, storage arrays, networking equipment, power backup (UPS systems), cooling infrastructure, and physical security for the server room. For a 500-user deployment, server hardware alone commonly runs $20,000–$60,000 depending on redundancy requirements. ### 4. Software Licenses and Updates Beyond the intranet platform itself, auxiliary software — operating systems, database licenses, monitoring tools — carries its own cost. Budget for annual update cycles; skipping updates creates security debt. ### 5. Data Migration Moving content from a legacy system is frequently underestimated. High data volumes, sensitive records requiring chain-of-custody documentation, or poorly structured legacy content all increase migration effort and cost. ### 6. Custom Development and Integrations Financial institutions and government agencies typically need bespoke modules or integrations with existing ERP, HRIS, or case-management systems. Custom development is often billed at $150–$250/hour for specialized intranet developers, and complex integrations can add $30,000–$100,000 to a project. ### 7. Installation and Deployment Vendor deployment fees vary. Some vendors include deployment in the license; others bill separately. Clarify this in the contract before signing. ### 8. Training and Onboarding IDC research shows employees spend an average of 2.5 hours per day searching for information. A well-structured intranet reduces that burden — but only if employees know how to use it. Formal training sessions, user guides, and change-management programs are recurring costs that directly affect adoption rates. ### 9. Support and Maintenance Annual maintenance contracts typically run 15–20% of the initial software license cost. This covers patches, bug fixes, and vendor support SLAs. Internal IT staff time for routine administration is an additional recurring cost. ### 10. Security Measures Intrusion detection systems, firewalls, encryption tools, and penetration testing add to the initial build cost. For regulated industries, these are not optional — they are compliance requirements. ### 11. Redundancy and Backup Avoiding a single point of failure means building redundant systems and automated backup routines. Depending on your recovery-time objective, this can add 10–25% to infrastructure costs. ### 12. Scalability Planning Over-provisioning hardware at launch costs money upfront but avoids expensive mid-cycle upgrades. Under-provisioning creates performance problems and emergency spend. A capacity plan covering three to five years is worth the consulting time. ### 13. External Consultants Many organizations hire IT consultants to validate architecture decisions, manage vendor selection, or oversee deployment. Consultant fees for a mid-market project commonly range from $20,000 to $80,000. ### 14. Ongoing Administrative Costs Dedicating internal personnel to intranet administration — content governance, user management, access reviews — is a recurring cost that rarely appears in vendor quotes. Budget 0.25–0.5 FTE for a 500-user deployment. ### 15. Exit and Transition Costs When switching vendors or migrating to a cloud model later, data migration, system decommissioning, and contract exit fees create costs that are easy to ignore at procurement time. Build a rough exit-cost estimate into your TCO model from day one. --- ## Deployment Speed as a Hidden Cost Driver On-premise deployments are often assumed to be slow — and slow deployments are expensive. Every week a new intranet is not live is a week employees continue spending 2.5 hours per day searching for information (per IDC). For a 500-person organization at an average fully loaded cost of $75/hour, a two-month delay in going live represents roughly $1.2 million in lost productivity. For context, a fully mobile, frontline-ready intranet can be deployed and live for a 40,000-employee workforce in as little as 8 weeks under a cloud model (per Unily / British Airways case study). On-premise timelines are typically longer — 3 to 9 months for mid-market deployments — which is a real cost that belongs in your TCO calculation. According to Emergence Capital, 80% of the global workforce is deskless. If your on-premise intranet does not include a mobile-accessible interface for frontline workers, you are effectively excluding the majority of your workforce — and the adoption gap widens. SWOOP Analytics research found that employees spend an average of just six minutes per day using intranet tools, a benchmark that underscores how much design and accessibility decisions affect realized value. --- ## Frequently Asked Questions ### Is on-premise intranet more expensive than cloud over five years? In most mid-market scenarios, yes. Cloud intranet subscriptions typically run $5–$15 per user per month, which for 500 users equals $30,000–$90,000 per year — lower than the annual TCO of a comparable on-premise setup once hardware refresh cycles, internal IT labor, and maintenance contracts are included. The exception is large enterprises (5,000+ users) where per-seat cloud costs can exceed on-premise TCO after year three. The right answer depends on your user count, compliance requirements, and internal IT capacity. ### What compliance requirements affect on-premise intranet cost? HIPAA (healthcare), SOC 2 (financial services), FedRAMP (federal agencies), and GDPR (EU data residency) each impose specific technical controls — encryption standards, audit logging, access reviews — that add scope to an on-premise build. Engage your compliance team before finalizing a vendor scope of work so these requirements are priced in, not added later as change orders. ### How do I evaluate whether on-premise is the right choice? The core question is whether your data residency, compliance, or integration requirements genuinely require on-premise control — or whether a private-cloud or hybrid deployment would satisfy the same requirements at lower cost. Many organizations that initially specify on-premise find that a [modern intranet](/solutions/modern-intranet) with configurable data-residency options meets their compliance needs without the full infrastructure burden. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides a vendor-neutral framework for evaluating these trade-offs across deployment models. --- ## Building Your Budget: A Practical Checklist Use this checklist to build a complete cost estimate before issuing an RFP: - **Licensing:** Per-user cost × total users (include contractors) - **Hardware:** Servers, storage, networking, power, cooling, physical security - **Implementation:** Vendor deployment fees + internal IT time - **Custom development:** Integrations, bespoke modules, persona-based governance - **Data migration:** Volume assessment, sensitive-data handling, validation - **Training:** Formal sessions, user guides, change management - **Security:** Firewalls, IDS, encryption, penetration testing - **Redundancy:** Backup systems, failover infrastructure - **Annual maintenance:** Software support contract (budget 15–20% of license cost) - **Internal administration:** IT staff time (0.25–0.5 FTE) - **Exit costs:** Data portability, decommissioning, contract terms For organizations in regulated sectors, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how compliance requirements are reshaping intranet procurement decisions and what governance capabilities buyers should require in a vendor scope of work. --- ## The Bottom Line On-premise intranet cost is not a single number — it is a range shaped by user count, compliance requirements, hardware choices, and how much custom development your workflows demand. For most mid-market organizations (500–1,000 users), plan for **$130,000–$426,000 in year one** and **$40,000–$80,000 in annual ongoing costs** (per MangoApps blog / Awesome Technologies Inc. 2025 cost model). Small organizations can deploy for less; large enterprises should budget significantly more. The three factors most likely to push your budget toward the high end are: (1) regulated-sector compliance requirements that mandate persona-based governance and audit logging, (2) extended deployment timelines that delay productivity gains, and (3) underinvestment in training that produces the low adoption rates Social Edge Consulting documents — 13% daily usage and nearly a third of employees never logging in. If you are evaluating whether on-premise is the right model for your organization, or want to understand how a [company portal](/key-features/company-portal) can be configured to meet your compliance requirements without a full on-premise build, speaking with a vendor who specializes in regulated-sector deployments is the most efficient next step. --- # Step-by-Step Guide to Setting Up Your On-Premise Intranet **Author:** Luke Walton **Published:** 2023-08-28 **Category:** on-premise-intranet As the modern workplace evolves, the need for streamlined communication and collaboration is paramount. While a cloud-based intranet has its merits and benefits, there are several sectors that find immense value in on-premise intranet solutions. These sectors are often in highly regulated industries like healthcare, government, and financial institutions where an on-premise intranet provides a […] ## Step-by-Step Guide to Setting Up Your On-Premise Intranet As the modern workplace evolves, the need for streamlined communication and collaboration is paramount. While a cloud-based intranet has its merits and benefits, there are several sectors that find immense value in on-premise intranet solutions. These sectors are often in highly regulated industries like healthcare, government, and financial institutions where an on-premise intranet provides a tailored platform in which data security, customization, and compliance are not just afterthoughts but driving factors. If you're considering an on-premise intranet, setting it up can be daunting. This guide provides actionable advice and best practices to ensure a smooth transition — from initial needs assessment through post-launch optimization. **1. Assess Your Needs:** Start with a clear understanding of what you want from the intranet and the costs associated with on-premise solutions. Does the healthcare institution need a platform solely for communication, or will it manage patient records? Does the government department need data sovereignty assurance? Before you get too far into the process, make sure you understand the typical reasons for choosing cloud vs. on-premise intranets. Worth noting: per Social Edge Consulting, 91% of organizations already operate an intranet — yet only 13% of employees use one daily, and nearly a third never log in at all. A clear needs assessment upfront is the single best way to avoid building a platform your workforce ignores. **2. Infrastructure Planning:** Ensure your servers and related infrastructure can support the intranet platform. High-speed networks, backup systems, and data redundancy should be prioritized. **3. Choose the Right Software:** There are several on-premise intranet solutions available, so choosing one that aligns with your needs and industry requirements is essential. **MangoApps** stands out as a leading [modern intranet](/solutions/modern-intranet) vendor, renowned for its comprehensive features tailored for industries with stringent requirements. Read our case study about on-premise customer Ekspert for a real-world example of our platform's efficacy. One common misconception is that on-premise always means a slow rollout — in practice, a fully mobile, frontline-friendly on-premise deployment can go live within eight weeks even for workforces of 40,000 or more employees. **4. Design and Customization:** One significant benefit of an on-premise solution is the level of customization available. Design it to mirror company branding, incorporate necessary tools, and discard unneeded features. Persona-based targeting by role, region, brand, and language — with message acknowledgment tracking — is now a baseline expectation for regulated-industry intranets, not a premium add-on (per Akumina). MangoApps' [company portal](/key-features/company-portal) and [department sites](/key-features/department-sites) features support this level of role-aware personalization out of the box. **5. Integrate with Existing Systems:** If you're a financial institution with legacy software, ensure your chosen intranet integrates cleanly. This might involve specialized APIs or middleware. For regulated sectors, semantic AI search that respects existing permissions and returns role-aware results is increasingly positioned as a compliance-grade requirement, not just a convenience (per Akumina). Evaluate whether your chosen platform can enforce data-sovereignty constraints while still surfacing relevant content — a critical consideration for healthcare and government deployments. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) offers independent benchmarking of how leading platforms handle integration and search governance. **6. Test the System:** Before a full-scale launch, test the system with a select group of users. This beta testing phase will highlight potential glitches and areas for improvement. **7. Train Your Team:** A tool is only as good as its user. Organize comprehensive training sessions for different departments. An employee familiar with the intranet's functionalities will inevitably be a better user. Per IDC, employees spend an average of 2.5 hours per day searching for information — a well-trained team using a well-structured intranet can recover a meaningful portion of that time. Per SWOOP Analytics, the average employee currently spends only six minutes per day using intranet tools, which underscores how much adoption depends on training and change management, not just technology. **8. Data Migration:** Data migration is a critical step for those transitioning from another system. Ensure data integrity, and consider using professionals if the volume of data is extensive. Structured content management — sometimes called a CMS intranet approach — makes migration cleaner by enforcing consistent metadata and taxonomy from day one. MangoApps' [webpage builder](/key-features/webpage-builder) supports structured content creation that simplifies future migrations. For a detailed look at how a regulated-industry organization managed this transition, see [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology). **9. Set Access Levels:** Not every employee needs access to all information. Use strong access controls, especially critical for sectors like healthcare, where patient confidentiality is paramount. Role-based permissions should extend to search results as well — employees should only surface content they are authorized to see, which is increasingly treated as a compliance requirement in regulated industries. MangoApps' [workspaces](/key-features/workspaces) feature supports granular, role-based access that can be scoped by department, location, or project. **10. Launch and Continuous Feedback:** Once you've thoroughly tested the system and trained your team, it's launch time. But the work doesn't end there. Continuously solicit feedback to refine and enhance the platform. Per Emergence Capital, 80% of the global workforce is deskless — ensuring your intranet is mobile-accessible from day one is essential for frontline adoption. Benchmarks from large regulated-industry deployments show 90% frontline adoption within the first six months is achievable when mobile access and targeted communications are prioritized from launch. **11. Regular Updates and Maintenance:** Regular software updates and hardware maintenance are essential to keep your on-premise intranet solution running smoothly. Make sure the vendor you choose supports easy upgrades and maintenance. **12. Review Security Protocols:** As cyber threats evolve, so should your security protocols. Regularly review and update them to ensure your data remains protected. --- ## Explore a Comprehensive On-Premise Solution and Real-World Implementations Are you searching for an on-premise intranet solution tailored to meet the unique demands of regulated industries? Dive deep into the **MangoApps On-premise solution**. It offers a full feature set — including role-aware search, persona-based targeting, and a managed upgrade path — and you can also explore compelling case studies providing insights into its practical implementations in various sectors. Independent recognition, including [MangoApps' inclusion in a leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms), confirms its standing among enterprise-grade options for compliance-heavy environments. For organizations weighing total cost of ownership, the ROI case for a well-implemented intranet is concrete: enterprise deployments have documented $20M in cost avoidance from a single intranet rollout. On-premise does not have to mean slow, expensive, or inflexible — with the right vendor and a structured implementation plan, regulated-industry organizations can achieve rapid time-to-value while maintaining full data sovereignty. --- ## What Is the Typical Timeline for an On-Premise Intranet Deployment? A common concern is that on-premise implementations take months or years to go live. In practice, timelines vary by organization size and complexity, but structured deployments — with clear requirements, pre-built templates, and a phased rollout — can reach full launch in eight to twelve weeks for most mid-market organizations. Larger enterprises (40,000+ employees) have achieved go-live within eight weeks when the vendor provides a managed implementation track. The key variables are data migration volume, the number of legacy system integrations, and the depth of customization required. Piloting with a single department before a company-wide rollout consistently shortens the overall timeline by surfacing configuration issues early. ## What Does an On-Premise Intranet Typically Cost, and How Does TCO Compare to Cloud? On-premise intranet total cost of ownership (TCO) includes hardware procurement, software licensing, internal IT staffing for maintenance, and periodic upgrade costs. Cloud intranets shift most of those costs to a predictable per-seat subscription but introduce ongoing vendor dependency and data-residency trade-offs. For regulated industries, the compliance value of on-premise data sovereignty often justifies a higher upfront investment — particularly when the alternative is costly third-party audits or regulatory penalties. Organizations should model a three-to-five-year TCO that accounts for hardware refresh cycles, security audit costs, and the productivity gains from reduced information search time (IDC estimates 2.5 hours per day lost per employee to information search). The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides additional benchmarks for building an internal business case. ## What Are the Most Common Pitfalls in On-Premise Intranet Rollouts? The most frequently cited failure modes in on-premise intranet projects are low adoption, scope creep, and inadequate governance. Per Social Edge Consulting, nearly a third of employees never log in to their organization's intranet — a statistic that reflects poor change management and insufficient training more often than poor technology choices. Scope creep occurs when organizations attempt to migrate every legacy system and content repository at once rather than phasing the rollout. Governance gaps — undefined content ownership, no content review cycles, and missing access-control policies — compound over time and erode trust in the platform. Addressing all three proactively, before launch, is the difference between an intranet that becomes a daily work hub and one that collects digital dust. --- # On-Premise Intranet vs. Cloud: Which is Best for Your Business? **Author:** Luke Walton **Published:** 2023-08-28 **Category:** on-premise-intranet In today’s interconnected world, efficient internal communication and collaboration tools are paramount. The intranet has emerged as a crucial backbone for many enterprises, paving the way for streamlined operations and enhanced team productivity. The most significant question when considering an intranet solution is: Should you opt for an on-premise intranet or cloud-based model? Let’s delve […] # On-Premise Intranet vs. Cloud: Which is Best for Your Business? Choosing between an on-premise intranet and a cloud-based intranet is one of the most consequential infrastructure decisions an organization can make. The right answer depends on your compliance obligations, IT capacity, growth trajectory, and total cost of ownership — not just upfront price. This article breaks down both deployment models, compares them across security, control, and scalability, and provides a concrete decision framework so you can identify which model fits your situation without returning to Google for more research. For context on how widely intranets are used: per Social Edge Consulting, 91% of organizations operate an intranet — yet only 13% of employees use one daily, and nearly a third never log in at all. That adoption gap often traces back to deployment and configuration decisions made at the outset. ## On-Premise Intranet *What it is:* This traditional approach to deploying intranets involves the software and its infrastructure being housed within the organization's premises. **Benefits:** 1. **Control:** On-premise intranets offer unrivaled control over the IT environment. Businesses can tailor their [intranet platform](/solutions/modern-intranet) and server configurations to their unique needs. Government agencies, for instance, might prefer this to maintain data sovereignty. 2. **Security:** With infrastructure in-house, there's a heightened sense of security. Healthcare institutions that handle sensitive patient data may favor on-premise solutions to ensure that data never leaves their controlled environment. 3. **Data Compliance:** Financial institutions and other regulated industries can easily comply with stringent data handling and storage mandates using on-premise solutions. **Limitations:** 1. **Initial and Total Cost:** There's a substantial upfront investment in hardware, software, and IT staffing. But the full picture goes further: first-year total cost of a SharePoint on-premise or hybrid deployment for 1,000 users is estimated between $130,000 and $426,000, once staffing, customization, governance overhead, and third-party integration costs are included. Ongoing maintenance and upgrade cycles add to that figure every year. 2. **Maintenance:** Businesses must be responsible for regular software updates, hardware care, and troubleshooting — a significant burden for organizations without large IT departments. 3. **Scalability Concerns:** Significant infrastructure adjustments may be necessary for rapidly growing businesses or institutions. 4. **AI and Personalization Limitations:** On-premise deployments often lag behind cloud tiers in supporting AI-powered semantic search and role-aware content surfacing. Organizations that want persona-based targeting — delivering role-, region-, and language-specific content with message acknowledgment tracking — typically need a cloud or hybrid path to access those capabilities. Learn more about the process of setting up an on-premise intranet or read about Ekspert, a consulting firm that uses MangoApps' on-premise intranet solution to serve their customers in a secure environment. ### Ensuring Compliance In The Financial Sector Learn how Ekspert leveraged MangoApps' on-premise intranet to transform the way its employees communicate. [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) is another example of how deployment model choices shape employee experience outcomes. ## Cloud-Based Intranet *What it is:* Cloud-based intranets are hosted externally on a service provider's servers accessible via the internet. **Benefits:** 1. **Cost-effective:** Most businesses can tap into cloud solutions without major initial investments, and the subscription model converts unpredictable capital expenditure into predictable operating costs. 2. **Easy Maintenance:** Service providers handle maintenance, which can be a boon for institutions without large IT departments. 3. **Scalability:** Cloud solutions can be expanded effortlessly as per business requirements. A modern cloud intranet platform can be deployed for a 40,000-employee workforce in as little as 8 weeks, compared to months-long on-premise rollouts — a meaningful advantage for time-sensitive buyers (per Unily / British Airways case study). 4. **Speed to Adoption:** A 95% employee adoption rate has been achieved for a cloud intranet serving a 5,000-person post-acquisition workforce, demonstrating that rapid deployment does not have to come at the cost of engagement. **Limitations:** 1. **Potential Security Concerns:** Data storage off-premise can be a concern, especially for regulated industries. Evaluate your vendor's certifications (SOC 2, ISO 27001, FedRAMP) before assuming cloud equals less secure. 2. **Less Control:** Customization might be limited to the cloud vendor's offerings, though modern platforms with a [webpage builder](/key-features/webpage-builder) and configurable [department sites](/key-features/department-sites) close much of that gap. 3. **Internet Dependency:** A stable internet connection is paramount for uninterrupted access — a real constraint for frontline or remote locations with limited connectivity. Per Emergence Capital, 80% of the global workforce is deskless, making offline or low-bandwidth access a legitimate deployment consideration. ## Security, Control, and Scalability — A Summary 1. **Security:** On-premise solutions are generally favored by industries like healthcare and financial institutions due to the perception of enhanced security. Cloud solutions have closed this gap significantly through enterprise-grade certifications, but regulated industries should verify compliance posture with each vendor. 2. **Control:** On-premise systems are preferred when total control is paramount, such as with government agencies. Cloud platforms increasingly offer tenant-level configuration that satisfies most enterprise governance requirements. 3. **Scalability:** Cloud-based intranets shine in scalability, accommodating growth with ease. On-premise systems require planned infrastructure investment to scale. ## Which One is Right for Your Business? Choosing between on-premise and cloud largely depends on your business's unique needs, growth projections, and compliance requirements. Use this framework to self-identify your fit: **Choose on-premise if:** - Your industry (healthcare, government, financial services) mandates data residency or prohibits third-party cloud storage - You have an established IT team capable of managing infrastructure, updates, and security patching - Your workforce is stable in size and a multi-month deployment timeline is acceptable - You do not require AI-powered personalization or rapid feature iteration in the near term **Choose cloud if:** - Deployment speed matters — weeks, not months, to go live - Your IT team is lean and you want maintenance handled by the vendor - You need to scale headcount quickly (acquisitions, seasonal hiring, geographic expansion) - You want access to AI-native features like semantic search, persona-based content targeting, and message acknowledgment tracking - You are managing a predominantly deskless or frontline workforce — per IDC, employees spend 2.5 hours per day searching for information, and a well-configured cloud intranet with role-aware content surfacing directly reduces that friction **Consider a hybrid model if:** - Certain data sets must remain on-premise for compliance while collaboration tools can live in the cloud - You are mid-migration from a legacy on-premise system and need a phased transition - Different business units have materially different security or connectivity requirements Enterprises replacing a legacy on-premise email point solution with a cloud intranet broadcast tool have documented cost savings of approximately £80,000 annually (per Unily / British Airways case study) — a figure worth including in any TCO comparison. For a broader view of where intranet platforms are heading, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent vendor analysis that can inform your shortlist. ## Discover a Superior On-Premise Solution For organizations tilting towards an on-premise intranet, the **MangoApps On-premise solution** is worth considering. Specially tailored for sectors that don't compromise on security and control, MangoApps combines top-tier features with flexibility — including configurable [workspaces](/key-features/workspaces) and a [company portal](/key-features/company-portal) that can be structured to match your organizational hierarchy. Your intranet choice will significantly impact business communications and collaborations. Making an informed decision that aligns with your operational requirements is essential — and the framework above gives you the criteria to do that without ambiguity. ## What Does an On-Premise vs. Cloud Migration Actually Involve? Migrating from on-premise to cloud — or vice versa — is not a lift-and-shift. Key considerations include: - **Data mapping and cleansing:** Legacy on-premise intranets often accumulate years of unstructured content. Before migration, audit what content is actively used (per SWOOP Analytics, average daily time spent using intranet tools is just six minutes, meaning most content goes untouched) and archive or delete what isn't. - **Identity and access management:** Cloud migrations require integrating your directory (Active Directory, Okta, etc.) with the new platform's SSO layer. - **Change management and training:** Adoption does not happen automatically. The Social Edge Consulting finding that nearly a third of employees never log in to the intranet is largely a change management failure, not a technology failure. - **Phased rollout:** A department-by-department rollout reduces risk and allows you to refine configuration before full deployment. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring intranet migrations and internal communications transformations this year. ## How Do I Calculate Total Cost of Ownership for Each Model? A complete TCO comparison should include the following line items over a 3–5 year horizon: **On-premise TCO inputs:** - Hardware procurement and refresh cycles - Software licensing (perpetual or annual) - IT staffing for administration, security patching, and upgrades - Third-party integration and customization development - Disaster recovery and backup infrastructure - Compliance audit and documentation overhead **Cloud TCO inputs:** - Per-seat subscription fees (typically tiered by feature set) - Implementation and configuration services - SSO and integration setup - Ongoing vendor support tier - Any data egress or storage overage fees The $130,000–$426,000 first-year range for a 1,000-user SharePoint on-premise deployment illustrates how quickly hidden costs accumulate. Cloud subscriptions are more predictable but should be modeled at full headcount, including contractors and seasonal workers, to avoid mid-year overages. ## What About Hybrid Intranet Models? A hybrid intranet model keeps sensitive data and certain workloads on-premise while routing collaboration, communications, and content management through a cloud layer. This approach is increasingly common in financial services and healthcare, where specific data categories are regulated but employee experience expectations are identical to those in less-regulated industries. Hybrid deployments introduce their own complexity: identity federation, data synchronization latency, and split governance models all require careful planning. However, for organizations that cannot move entirely to the cloud but want access to modern features — AI search, mobile-first design, persona-based targeting — hybrid is a viable middle path rather than a compromise. For organizations managing complex workforce structures alongside their intranet decision, [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides independent context on how MangoApps positions across deployment models. --- # What is an On-Premise Intranet? A Comprehensive Guide **Author:** Luke Walton **Published:** 2023-08-28 **Category:** on-premise-intranet Digital transformation has introduced various tools for businesses and reshaped the very nature of organizational operations. One constant amidst this evolution is the intranet system. As we dive deep into understanding intranets, especially the on-premise solutions, we will also shed light on the MangoApps On-premise solution and how it is a superior offering compared to […] # What Is an On-Premise Intranet? A Comprehensive Guide An on-premise intranet is a private internal network hosted on servers that your organization owns and operates — not on a third-party cloud provider's infrastructure. That single distinction drives most of the trade-offs covered in this guide: who controls the data, who maintains the hardware, and who bears the cost when something breaks. According to Social Edge Consulting, 91% of organizations operate an intranet of some kind. Yet nearly a third of employees never log in, and only 13% use one daily (per Social Edge Consulting). Understanding *why* — and whether an on-premise deployment changes that equation — is the practical question this guide answers. --- ## How to Define an Intranet The intranet definition most IT teams work from is straightforward: a private network accessible only to an organization's members, used to share information, coordinate work, and host internal applications. Unlike the public internet, access is restricted by authentication and, in on-premise deployments, often by network perimeter controls. Over time the intranet definition has expanded. Modern platforms include document management, social feeds, department sites, HR self-service, and integrations with tools like Microsoft 365 and Google Workspace. The core purpose — a single place where employees find what they need to do their jobs — has not changed. IDC research puts the cost of information fragmentation at 2.5 hours per day per employee spent searching for information. That figure is the clearest business case for any intranet investment, on-premise or cloud. --- ## On-Premise vs. Cloud-Based Intranet: The Core Difference Two deployment models dominate the market: - **Cloud-based intranet**: Hosted on the vendor's servers. The vendor manages infrastructure, updates, and uptime. Lower upfront cost; less control over where data lives. - **On-premise intranet**: Hosted on servers your organization owns or leases in a data center you control. Higher upfront cost; full control over data residency, security configuration, and integration architecture. Neither model is universally better. The right choice depends on your regulatory environment, IT capacity, and how much control your security team requires. ### When On-Premise Is the Practical Requirement For regulated industries — financial services, healthcare, defense contracting — on-premise deployments often aren't optional. Data residency mandates in many jurisdictions prohibit storing employee or customer data on third-party cloud servers, a requirement cloud-only vendors structurally cannot meet. A financial services firm operating under strict data sovereignty rules, for example, may have no compliant path to a cloud-hosted intranet regardless of its other merits. --- ## Key Benefits of an On-Premise Intranet ### 1. Data Sovereignty and Compliance When data never leaves your infrastructure, you control which jurisdictions it touches. This matters for multinational organizations subject to GDPR, HIPAA, financial sector data residency rules, or government security classifications. Cloud vendors can offer regional data centers, but the contractual and audit complexity of verifying data residency is substantially lower when you own the hardware. ### 2. Tailored Security Configuration On-premise deployments let your security team implement controls that match your specific risk profile — custom firewall rules, network segmentation, integration with on-premise identity providers, and audit logging that feeds directly into your SIEM. Cloud platforms offer security, but it is the vendor's security model, not yours. ### 3. Integration with Legacy Systems Organizations running legacy ERP, HRIS, or line-of-business applications on internal networks often find that on-premise intranet platforms integrate more cleanly than cloud alternatives that require exposing internal APIs to the public internet. Modern on-premise platforms can connect with 200+ enterprise systems — including HRIS, LMS, Microsoft 365, and Google Workspace — eliminating the assumption that self-hosted means siloed (per MangoApps integrations product page). ### 4. Predictable Cost Structure at Scale Cloud pricing scales with user count, which creates budget unpredictability as organizations grow. On-premise deployments carry higher upfront costs but more predictable long-run economics for large employee populations. --- ## Challenges of On-Premise Intranet Deployments On-premise is not the right fit for every organization. The honest trade-offs: - **Higher upfront investment**: Hardware, software licenses, and IT staffing add up before a single employee logs in. Legacy SharePoint on-premise deployments, for example, require $15,000–$150,000+ in implementation costs before any customization or governance tooling (per MangoApps blog / SharePoint alternatives cost analysis, Awesome Technologies Inc. 2025). A conservative first-year total cost for a 1,000-user SharePoint deployment runs $130,000–$426,000, making purpose-built on-premise alternatives financially competitive at scale. - **In-house IT dependency**: Patches, hardware failures, and capacity planning fall to your team. Organizations without a capable IT function will find this burden significant. - **Manual update cycles**: Cloud platforms push updates automatically. On-premise deployments require planned maintenance windows and internal testing before updates go live. - **Longer initial deployment**: Traditional on-premise projects can take months. This is a real concern, though modern platforms have compressed timelines considerably — more on that below. --- ## Does On-Premise Mean Outdated? Addressing the Common Misconceptions ### AI Capabilities Are Not Cloud-Exclusive A common assumption is that self-hosted infrastructure precludes modern AI features. That is no longer accurate. On-premise intranet platforms can integrate with AI services — including OpenAI, Gemini, and Azure OpenAI — to deliver AI-powered search, content surfacing, and personalization without routing employee data through a public cloud intranet. The on-premise deployment controls *where data is stored*, not whether AI can operate on it. ### Frontline Workers Can Access On-Premise Intranets Without Corporate Email The legacy image of an on-premise intranet — desktop-only, VPN-required, corporate email mandatory — does not describe modern deployments. According to Emergence Capital, 80% of the global workforce is deskless. A healthcare system, a logistics company, or a retail chain cannot afford an intranet that only works for office employees. Modern on-premise platforms support frontline workers on personal mobile devices without requiring a VPN or corporate email address. This directly addresses the engagement gap: SWOOP Analytics found that employees spend an average of just six minutes per day using intranet tools, a figure that reflects platforms designed for desk workers rather than the full workforce. ### Deployment Speed Has Improved Significantly On-premise has historically meant slow rollouts. That gap has narrowed. A CVS deployment on a modern intranet platform achieved 90% frontline adoption within the first six months — a benchmark that challenges the assumption that self-hosted implementations are inherently slow to reach value. --- ## Who Should Consider an On-Premise Intranet? On-premise is a strong fit when one or more of the following apply: - Your industry faces data residency or sovereignty regulations that restrict third-party cloud storage - Your security team requires direct control over network perimeter, identity management, and audit logging - You have significant legacy system infrastructure that is difficult or risky to expose to external APIs - Your workforce includes a large frontline or deskless population that needs mobile-first access without corporate credentials - Your organization is large enough that per-user cloud pricing creates meaningful budget pressure Cloud-based deployments are a better fit when IT capacity is limited, upfront capital is constrained, or your regulatory environment does not impose data residency requirements. --- ## What to Look for in an On-Premise Intranet Platform When evaluating platforms, these criteria separate modern solutions from legacy ones: 1. **Mobile-first access** — Does it support frontline workers on personal devices without VPN? 2. **Integration breadth** — How many enterprise systems does it connect to natively? 3. **AI search and personalization** — Does the platform surface relevant content without requiring employees to navigate a complex hierarchy? 4. **Deployment timeline** — What does a realistic go-live look like, and what does the vendor's customer adoption data show? 5. **Total cost of ownership** — What are the year-one and year-three costs inclusive of hardware, licensing, IT labor, and training? 6. **Compliance tooling** — Does the platform include audit logging, role-based access controls, and data retention policies out of the box? For a broader view of how intranet platforms are evaluated by independent analysts, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides vendor-neutral scoring across these dimensions. MangoApps has also been recognized in independent analyst evaluations — see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) for context on how the platform is positioned relative to the broader market. --- ## Frequently Asked Questions About On-Premise Intranets ### How does an on-premise intranet differ from a company portal? A [company portal](/key-features/company-portal) is typically the employee-facing front end — the homepage, news feed, and navigation layer — while the intranet is the broader system that includes document storage, collaboration workspaces, and application integrations. In practice, the terms are often used interchangeably, but the distinction matters when scoping a deployment: you may want a portal experience on top of an on-premise intranet back end. ### Can on-premise intranets support department-specific sites? Yes. Modern platforms support [department sites](/key-features/department-sites) that give each team a dedicated space for their documents, announcements, and workflows — all within the same on-premise deployment. This is particularly valuable in healthcare or financial services organizations where different business units have distinct compliance requirements. ### How do on-premise intranets handle SOP operations and policy documentation? SOP operations — the process of creating, versioning, distributing, and acknowledging standard operating procedures — is one of the most common use cases for an on-premise intranet in regulated industries. On-premise deployments are well-suited here because audit trails for document access and acknowledgment stay within your own infrastructure, simplifying compliance reporting. Platforms with built-in [workspaces](/key-features/workspaces) allow teams to manage SOPs alongside the projects and communications they support. --- ## The Bottom Line An on-premise intranet is the right infrastructure choice for organizations that face genuine data sovereignty requirements, need direct control over security configuration, or operate large frontline workforces that cloud-only vendors have historically underserved. It is not the right choice for organizations that lack IT capacity to manage infrastructure or that operate in environments with no regulatory pressure on data residency. The decision is not about which deployment model is inherently better — it is about which model fits your compliance environment, your workforce composition, and your total cost tolerance. The 2.5 hours per day employees spend searching for information (per IDC) represents a real cost that a well-deployed intranet — on-premise or cloud — can reduce. The deployment model is a means to that end, not the end itself. If you are evaluating whether a [modern intranet](/solutions/modern-intranet) deployment fits your organization's specific requirements, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the operational and workforce trends shaping intranet investment decisions this year. --- # 10 Benefits of Choosing an On-Premise Intranet Solution **Author:** Luke Walton **Published:** 2023-08-28 **Category:** on-premise-intranet Effective communication and collaboration tools are non-negotiable in today’s fast-paced business environment. Enterprises in regulated sectors like healthcare, government, and financial institutions grapple with choosing the best intranet solution. While cloud-based platforms have gained popularity, there’s a compelling case for an on-premise intranet solution, particularly when considering customization, data security, and long-term ROI. So, what […] Effective communication and collaboration tools are non-negotiable in today’s fast-paced business environment. Enterprises in regulated sectors like healthcare, government, and financial institutions grapple with choosing the best intranet solution. While cloud-based platforms have gained popularity, there’s a compelling case for an on-premise intranet solution, particularly when considering customization, data security, and long-term ROI. So, what makes on-premise intranet solutions stand out? Let’s unravel ten unique benefits. 1. Customization at its Best: An on-premise intranet solution offers unparalleled customization options. You’re not limited to standard features; organizations can design the platform to suit specific needs. This degree of flexibility can be especially beneficial for sectors like government, which may need specialized interfaces and tools. 2. Enhanced Data Security: When it comes to data security, keeping sensitive information in-house can provide an added layer of assurance. Healthcare providers, for example, handling confidential patient data, often prefer on-premise solutions to ensure complete control over this sensitive information. 3. Complete Control Over Data: Beyond security, on-premise solutions offer unmatched control over data access, storage, and backup procedures. With stringent data management regulations, financial institutions can ensure compliance without relying on third-party protocols. 4. Predictable Costs: Although the initial setup might be capital intensive, on-premise intranet solution costs are generally more predictable in the long term. Over time, the ROI becomes evident compared to recurring subscription fees of cloud solutions. 5. Seamless Integration with Legacy Systems: Companies with long-standing legacy systems might find integration with cloud platforms cumbersome. On-premise intranet solutions often allow for smoother integrations, ensuring continuity and consistency in operations. 6. Reduced Latency: With data hosted in-house, the time taken to access and retrieve it is often faster. This can be critical for real-time applications or sectors where split-second data retrieval is vital. 7. Compliance and Regulatory Assurance: For industries like finance and healthcare, compliance isn’t just a best practice; it’s mandatory. On-premise solutions offer a clearer path to meeting industry-specific regulations, mainly since data handling and storage are under the organization’s direct control. Read about MangoApps customer Ekspert, who use their on-premise intranet to maintain regulatory compliance for their customers. 8. Long-term ROI: Given the flexibility, security, and control an on-premise intranet solution offers, the long-term return on investment is significant. Organizations can fine-tune the system over time without incurring additional subscription costs, leading to more value extraction from the initial investment. 9. Offline Accessibility: On-premise systems can often be accessed even without an active internet connection, a crucial feature for organizations situated in areas with inconsistent connectivity. 10. Data Sovereignty: Government institutions and other sensitive sectors can maintain data sovereignty, ensuring that all information remains within regional or national borders, a requirement in several countries. The Bottom Line: The modern workplace demands agility, security, and robustness. An on-premise intranet solution is the best fit for many organizations, especially in highly regulated sectors. While the initial investment might be substantial, the long-term benefits of customization, data security, and ROI make it a compelling choice. Read our guide to on-premise intranets for more details. Ensuring Compliance In The Financial Sector Learn how Ekspert leveraged MangoApps’ on-premise intranet to transform the way its employees communicate. READ case study Dive Deep into a Comprehensive On-Premise Solution Considering an on-premise intranet solution for your organization? Don’t miss out on the MangoApps On-premise solution. Tailored for businesses prioritizing unmatched control, top-tier security, and impressive customization, MangoApps promises a solution that truly understands the nuances of regulated industries. --- # Why MangoApps is the Perfect SharePoint Alternative **Author:** MangoApps **Published:** 2023-08-24 **Category:** replace-sharepoint The Limitations Of SharePointThere are many limitations and challenges that companies encounter when deploying SharePoint. These limitations can impact the o... # Why MangoApps Is a Strong SharePoint Alternative SharePoint is installed in a vast number of organizations — according to Social Edge Consulting, 91% of organizations operate an intranet, and SharePoint is the most common starting point. Yet the same research finds that nearly a third of employees never log in, and only 13% use their intranet daily (per Social Edge Consulting). If your workforce is ignoring the tool you built your digital workplace on, the platform itself is worth re-examining. This article answers the core question directly: where does SharePoint fall short, and what does a modern intranet platform like MangoApps do differently? We cover search, mobile access, cost, personalization, and integration — so you can make an informed decision without needing to read five separate articles. --- ## Where SharePoint Falls Short ### Search That Doesn't Scale SharePoint was designed as a document storage and content management system — a CMS for intranet use — not as an enterprise search layer. Employees searching across SharePoint repositories frequently encounter stale results, permission walls, and no visibility into content stored in connected tools like Google Drive, Box, or Dropbox. The business cost is real: IDC estimates employees spend 2.5 hours per day searching for information. When your intranet's search stops at its own content boundary, that number doesn't improve. MangoApps addresses this by consolidating 200+ enterprise systems — including SharePoint, Google Drive, Box, and Dropbox — into a single unified search and navigation layer, so employees find what they need regardless of where it lives (per MangoApps integrations product page). ### Mobile Access and the Frontline Gap Approximately 80% of the global workforce is deskless (per Emergence Capital), yet SharePoint's mobile experience requires a Microsoft 365 account, a corporate email address, and often a VPN. For frontline workers in retail, healthcare, manufacturing, or logistics, those requirements create a hard barrier to access. Frontline employee replacement costs range from $4,400 to $15,000 per worker (per MangoApps mobile employee app product page / industry report), which means poor mobile intranet access is a measurable retention and cost risk — not just a UX inconvenience. MangoApps supports access without a corporate email address, making it practical for hourly and shift-based workforces. CVS achieved 90% frontline adoption within the first six months of deployment — a credible benchmark for organizations evaluating SharePoint alternatives in frontline-heavy industries. ### The Real Cost of SharePoint SharePoint appears affordable because most Microsoft 365 plans include it. The licensing cost for SharePoint Online runs $5–$20 per user per month, which scales to $60,000–$240,000 annually for a 1,000-person organization before any customization or IT overhead. When you add implementation, custom development, and dedicated IT management, the first-year total cost of ownership for a 1,000-user enterprise ranges from $130,000 to $426,000 (per MangoApps blog / SharePoint cost analysis, Awesome Technologies Inc. 2025 cost model). That range reflects a platform that requires significant IT investment to do what employees actually need. SWOOP Analytics reports that the average employee spends just six minutes per day using intranet tools — a figure that reflects low adoption, not low need. ### Personalization and Content Relevance SharePoint delivers the same intranet experience to a warehouse associate, a regional manager, and a corporate HR director unless someone builds and maintains audience-targeting rules. That customization requires IT involvement and ongoing maintenance cycles. MangoApps uses AI-curated content feeds — with connections to OpenAI, Gemini, Anthropic, and Azure OpenAI — to surface relevant content per employee based on role, location, department, and behavior. The result is an intranet that feels relevant rather than generic, which directly affects whether employees return to it. OU Health achieved 87% workforce engagement within months of launching a branded employee app built on MangoApps — a concrete adoption benchmark for large organizations. --- ## MangoApps as a SharePoint Integration Layer — Not Just a Replacement Not every organization can rip out SharePoint. If your document library, compliance workflows, or IT infrastructure are deeply tied to Microsoft 365, a full replacement may not be feasible in the near term. MangoApps is designed to work alongside SharePoint, not only instead of it. Through SAML/SSO, HRIS sync, and its unified search layer, MangoApps can sit on top of your existing SharePoint environment and extend it — adding the mobile access, personalization, and cross-system search that SharePoint lacks natively. Employees get a single destination that surfaces SharePoint content alongside everything else, without requiring IT to rebuild what already works. This coexistence model is particularly relevant for organizations that have invested in SharePoint customization but are seeing low adoption. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) evaluates how platforms like MangoApps compare on exactly these dimensions — integration depth, search quality, and frontline accessibility. --- ## How MangoApps Compares: A Direct Summary | Dimension | SharePoint | MangoApps | |---|---|---| | Search scope | SharePoint content only | 200+ integrated systems | | Frontline access | Requires Microsoft 365 account + email | No corporate email required | | First-year cost (1,000 users) | $130,000–$426,000 | Transparent per-user pricing | | Personalization | Manual audience targeting via IT | AI-curated feeds by role and location | | Deployment speed | Months of IT-led customization | Deployable for 1,000+ employees in significantly less time | | Daily usage | 6 minutes/day average (SWOOP Analytics) | 87% engagement benchmark (OU Health) | --- ## Frequently Asked Questions ### Can MangoApps replace SharePoint entirely? Yes, for most use cases — but it doesn't have to. MangoApps can serve as a full SharePoint replacement for organizations that want a single [modern intranet platform](/solutions/modern-intranet) covering communications, knowledge management, and employee experience. For organizations that need to preserve SharePoint for document storage or compliance, MangoApps integrates on top of it, extending its reach without requiring a full migration. ### What makes MangoApps better for knowledge management? Knowledge management tools need to do two things well: store information in a structured, findable way, and surface it to the right person at the right time. SharePoint handles the first reasonably well but struggles with the second. MangoApps combines structured [workspaces](/key-features/workspaces) for team and project knowledge with AI-powered search across all connected systems, so knowledge and knowledge management happen in the same place employees already work — rather than in a separate repository they have to remember to visit. ### How long does it take to deploy MangoApps? Unlike SharePoint's IT-led, months-long customization cycles, MangoApps is designed to be deployable for organizations of 1,000+ employees in a fraction of that time. The [company portal](/key-features/company-portal) and [department sites](/key-features/department-sites) come with configurable templates that reduce the need for custom development, and the platform's no-code [webpage builder](/key-features/webpage-builder) lets communications teams manage content without IT involvement. --- ## What to Do Next If your organization is experiencing low intranet adoption, high IT maintenance costs, or a frontline workforce that can't access your digital workplace, SharePoint's architecture is likely a contributing factor — not just your implementation. The clearest next step is to evaluate MangoApps against your specific gaps: search scope, mobile access requirements, cost model, and integration needs. The [MangoApps Included in Leading Research Firm's Intranet Platforms Ev...](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides third-party context on where MangoApps stands relative to the broader market. For organizations planning internal communications or workforce operations for the year ahead, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) and the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) offer additional context on what employees and communicators need from a modern intranet — and where SharePoint-era tools consistently fall short. --- # Cons Of SharePoint – Poor Internal Comms **Author:** Mason Hager **Published:** 2023-08-24 **Category:** replace-sharepoint Effective internal communication is the cornerstone of a successful organization. When done correctly it can create a sense of unity, transparency, and shared purpose among employees.  With relevant and consistent communications, you can empower your teams to collaborate seamlessly while keeping everyone in the loop. An effective internal comms strategy can bridge the information gaps […] # Cons Of SharePoint – Poor Internal Comms Internal communications professionals are often the first to identify that something is wrong with SharePoint — and the last to be heard when they raise it. The licensing fee looks manageable. The IT team already knows the platform. Leadership sees the Microsoft logo and assumes compatibility with the broader technology stack. By the time the full picture emerges — the months-long deployment timeline, the dedicated governance overhead, the frontline workforce that simply cannot access it — the decision is already made. This article names the specific ways SharePoint fails internal communications: not as a generic capability gap, but as a structural mismatch that shows up in measurable costs, unreachable workers, and an analytics void that makes it impossible to improve over time. ## SharePoint's "inexpensive" licensing conceals a six-figure first year SharePoint's entry-level pricing gets quoted in every evaluation. What doesn't get quoted is the total cost of the first year of operation. For a 1,000-person organization, the combination of implementation, customization, governance infrastructure, and the third-party connectors required to make the platform functional typically brings the first-year total to between $130,000 and $426,000 — before any ongoing maintenance. The wide range reflects how much depends on factors SharePoint doesn't handle natively: content governance workflows, audience targeting across employee segments, and the integrations required to connect SharePoint with the systems internal comms professionals rely on daily. Those integrations are not optional. SharePoint's architecture requires third-party tooling or custom development to connect with HRIS platforms, LMS systems, and identity providers. Without those connections, communications cannot be targeted to the right audiences automatically, new employees are not provisioned into the correct groups, and departing employees remain in distribution lists longer than they should. Each integration adds time, cost, and another dependency on IT to maintain. Per IDC, employees spend 2.5 hours per day searching for information across fragmented systems. That number doesn't improve when the intranet is disconnected from the source data that would make content relevant to each employee's role, location, and team. Per SWOOP Analytics, the average employee spends just six minutes per day inside their organization's intranet. SharePoint implementations — particularly those without dedicated governance resources — routinely fall below even that benchmark in organizations that track platform engagement. ## 80% of your workforce may be structurally unreachable The most consequential internal communications failure SharePoint creates isn't a feature gap. It's an access boundary that most organizations only discover after deployment. Per Emergence Capital, 80% of the global workforce is deskless. Warehouse associates, retail staff, clinical workers, and field technicians rarely carry corporate email addresses, company-provisioned laptops, or reliable access to a VPN. SharePoint's architecture assumes all three. The result is an intranet that structurally excludes the majority of your organization — not because of a configuration error, but because of an architectural decision that assumed a knowledge-worker audience at a desk. Extending SharePoint to frontline employees requires workarounds: shared device programs, kiosk setups, or third-party mobile wrappers that add cost and friction without delivering a consistent experience. Even when the access problem is technically resolved, the experience quality is not. SharePoint's mobile interface is fragmented and slow; navigation designed for a desktop browser does not translate to a phone screen checked briefly during a shift. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in at all. Only 13% use their intranet daily. In organizations with a significant frontline population, those non-participation rates trend higher — because the platform was never designed to reach those workers in the first place. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents how leading internal comms teams are rethinking access architecture — shifting toward mobile-first employee apps that require no corporate email, no VPN, and no IT provisioning per individual user. ## No analytics means you're sending communications you cannot measure Internal communications without measurement is operational guesswork. You send an all-hands update, a benefits enrollment reminder, a compliance notice — and you have no reliable way to know whether anyone read it, whether frontline locations received it at all, or which version of your message produced the intended response. SharePoint doesn't include meaningful analytics infrastructure for internal communications. There's no read-receipt model at the communication level, no engagement segmentation by department or location, and no mechanism for testing message timing or format. Per Social Edge Consulting, only 13% of employees use their intranet daily — and without platform analytics, you cannot identify which communications drove those sessions or understand why the other 87% stayed away. The practical consequences are recurring: the same compliance notice goes out multiple times because there's no confirmation of who saw the first one. High-priority announcements get re-sent until employees condition themselves to treat subsequent messages as noise. Email lists require manual updates because there's no HRIS integration to automate audience management when employees are hired, transferred, or exit. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), employee engagement correlates directly with whether workers feel informed and connected to their organization. Building that connection requires understanding which communications reach people and produce the intended response — information that SharePoint does not surface. ## IT dependency creates a ceiling on what internal comms can accomplish SharePoint is not a self-service platform for communications professionals. Every significant change to the environment — restructuring navigation, updating page templates, modifying audience segments, adjusting governance — requires IT involvement. For teams that need to move quickly on time-sensitive communications, that dependency becomes a structural constraint at the moments it matters most: open enrollment deadlines, leadership transitions, crisis response. The governance overhead is ongoing. SharePoint environments require active maintenance to prevent content sprawl, permission drift, and version control failures. Organizations without dedicated administrators find that the platform degrades over time — navigation becomes inconsistent, pages grow outdated, and search returns results that employees learn not to trust. That degradation feeds directly into the SWOOP Analytics usage finding: when the intranet is hard to navigate, employees stop using it, which makes it harder to justify the governance investment. For internal comms teams operating without embedded IT resources, SharePoint's requirements create a practical ceiling. The platform's feature set may appear comprehensive in a vendor comparison, but the portion that a non-technical team can actually use and maintain is substantially smaller. The gap between licensed capability and operational capability is where most of SharePoint's real costs accumulate — and where internal comms professionals spend most of their SharePoint-adjacent time. ## What modern internal communications platforms do differently The contrast with modern employee experience platforms is not primarily about feature lists — it's about architectural assumptions. While SharePoint was built for document management and extended to communications, platforms built for internal communications start from the opposite premise: that every employee needs to receive, consume, and respond to communications, regardless of device, location, or whether they have a corporate email address. Modern platforms provision access through phone numbers or QR codes rather than IT-managed credentials. They sync audience segments automatically from HRIS systems, so new hires are in the right distribution groups from day one and departing employees are removed without a manual process. They include analytics at the message level as a baseline capability rather than an add-on, allowing internal comms professionals to close the feedback loop on every campaign they run. AI-driven content personalization is increasingly standard: role-based feeds surface the communications most relevant to each employee's function and location, rather than presenting the same feed to a corporate director and a warehouse associate. That distinction matters because the primary reason employees don't engage with intranet content isn't lack of interest — it's relevance. When 91% of organizations have an intranet and nearly a third of employees never log in, per Social Edge Consulting, the problem is rarely the content itself. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) benchmarks leading platforms on frontline access, analytics depth, and deployment complexity — the three dimensions where SharePoint falls furthest short. For teams preparing an evaluation, it's the most detailed independent analysis of how current platforms compare on the criteria that matter most for internal communications. ## The cons that don't appear on a feature checklist SharePoint's positioning as an enterprise intranet platform isn't inaccurate — it handles content management and document collaboration, within limits. Those limits matter most for internal communications, because the function requires capabilities SharePoint systematically deprioritizes: seamless frontline reach, closed-loop analytics, and the ability for communications professionals to operate without constant IT mediation. Internal comms leaders who have spent years working around SharePoint's constraints know what they're evaluating for in an alternative. The requirements aren't abstract — they're the analytics that would have confirmed whether the compliance rollout succeeded, the mobile access that would have reached warehouse and field workers, and the audience-targeting capability that would have ended the practice of sending every announcement to the entire organization because segmentation requires a ticket to IT. An effective [employee communications platform](/solutions/employee-communications) makes those capabilities operational defaults rather than customization projects. For organizations weighing whether SharePoint's internal communications limitations justify a platform transition, the question is rarely whether the limitations are real — it's whether the ongoing cost of working around them is genuinely less than the cost of changing the platform that created them. --- # The Limitations Of SharePoint **Author:** Mason Hager **Published:** 2023-08-22 **Category:** replace-sharepoint There are many limitations and challenges that companies encounter when deploying SharePoint. These limitations can impact the overall employee experience, hinder communication strategies, and lead to decreased productivity. From poor personalization of the employee experience to limited mobile functionality, SharePoint’s disadvantages can pose significant hurdles for organizations aiming to create a seamless and effective digital […] # The Limitations Of SharePoint Organizations that evaluate SharePoint based on licensing alone are budgeting for a fraction of the actual commitment. Deploying SharePoint for a 1,000-person enterprise — with implementation, customization, governance, and the third-party tools required to fill its gaps — can reach $130,000 to $426,000 in the first year alone, far beyond the $5–$20 per user per month that appears in the initial proposal. That cost isn't the only thing being underestimated. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools. Per Social Edge Consulting, 13% of employees use an intranet daily — and nearly a third never log in at all. These numbers don't describe a content problem. They describe an architecture problem: SharePoint's design decisions create friction that compounds for every employee who isn't sitting at a corporate desktop during business hours. For organizations with a frontline or deskless workforce, that's most of the company. The limitations examined here aren't configuration problems fixed with a different SharePoint plan or a new consultant. They're structural decisions that determine who the platform was built for — and whether it can serve an organization whose workforce extends beyond headquarters. ## The access barrier SharePoint doesn't advertise Per Emergence Capital, 80% of the global workforce is deskless — working in clinics, distribution centers, retail stores, and construction sites. SharePoint's mobile experience is built on responsive design: the interface scales to a phone screen, but the underlying requirements stay the same. Employees need a corporate credential, often a VPN connection, and access to the organizational account hierarchy to participate. For a nurse at a health system, a warehouse associate at a logistics company, or a retail employee without a corporate email address, these requirements aren't a minor inconvenience. They're a structural access barrier. The platform is inaccessible before a single piece of content has been published. Four competitors in the modern intranet market explicitly position around this gap, noting that their platforms require no corporate email address and no VPN for frontline workers to authenticate. Modern [employee apps](/solutions/employee-app) address this by authenticating on a personal phone number or personal email address, with no corporate credential required — meeting workers on the device they already carry. OU Health achieved 87% workforce engagement within months of deploying this infrastructure, not because the content was better, but because clinical staff, technicians, and support workers could actually access it. ## Why the content doesn't get used SharePoint's content governance model is passive. Content accumulates. Without consistent manual intervention from IT administrators or department owners, intranet pages grow stale, file libraries fill with duplicate versions, and employees learn quickly that searching the platform rarely surfaces the right answer on the first try. Per IDC, employees spend 2.5 hours per day searching for information. Per SWOOP Analytics, the six-minute daily usage figure reflects what happens when the search experience is unreliable and the content inventory is unmanaged: employees stop trying. SharePoint's search has improved with each version, but it fundamentally operates on an indexing model that doesn't distinguish between an active policy document and a three-year-old draft that was never deleted. Employees searching for a current benefit enrollment form will find both. IT administrators can configure managed metadata and content types to reduce this problem — but that configuration is itself a significant ongoing investment, and it still doesn't provide a mechanism for intelligently flagging or archiving stale content without human action. Per Social Edge Consulting, 91% of organizations operate an intranet, but nearly a third of employees never log in at all. This adoption ceiling isn't primarily a communications problem. It's the predictable outcome of asking employees to navigate an environment where search requires knowing what you're looking for and roughly where it lives — before you've started looking. ## The cost beyond the license fee The SharePoint number in a procurement proposal is a starting point, not a budget. Licensing alone runs $5–$20 per user per month at standard tiers. Add implementation consultants — required for any setup beyond the default configuration — and the cost profile shifts significantly. Add the third-party tools needed for functionality SharePoint doesn't include natively (analytics, mobile apps, employee directory, campaign targeting), and the first-year total for a 1,000-person enterprise reaches $130,000 to $426,000 in total cost of ownership. The deployment timeline extends the exposure. SharePoint requires months of IT-led configuration before launch. During that period, the workforce waits. After launch, the platform requires dedicated SharePoint expertise to maintain — whether internal staff, retained consultants, or both. When Microsoft releases a major version update, organizations face a choice: accept breaking changes, or freeze on the current build and pay to stay behind the curve. This cycle is familiar to organizations that eventually switch to a modern alternative. The question is rarely whether SharePoint technically works. It's whether the total cost of keeping it working — in money, in IT hours, and in workforce adoption — is proportionate to what it delivers. ## Integration complexity as a cost multiplier Ten competitors in the intranet market now cover SharePoint integration complexity as a distinct limitation, positioning their platforms as connectors that unify SharePoint, Google Drive, HRIS systems, and other tools into a single searchable interface. That framing reflects a real gap. SharePoint does not natively search across Google Drive, Box, Dropbox, or the HRIS system that holds the current org chart. Bridging those systems requires custom development, third-party connectors, or Microsoft's premium search products. Each connection adds configuration complexity, a new point of failure, and ongoing maintenance every time a connected system updates its API. For employees, the practical result is that finding a document still requires knowing which system it lives in. The 2.5 hours per day that IDC attributes to information search reflects, in part, employees navigating across systems that don't share an index. Modern intranet platforms increasingly provide universal search across SharePoint, Google Drive, Box, HRIS, and other connected tools — reducing the systems-hopping that employees experience as wasted time and that organizations carry as a hidden productivity cost. ## The personalization gap AI has widened SharePoint's personalization model is built on organizational structure: groups, departments, site permissions. Content reaches employees based on their position in the org chart. This works when the org chart maps cleanly to communication needs, which it often doesn't. Frontline employee communication frequently requires targeting by shift, by physical location, by certification status, or by a combination of attributes that don't correspond to a department boundary. A health system communicating a policy change to employees holding a specific credential across multiple sites can't easily execute that targeting in SharePoint without building a custom audience group and maintaining it manually as employee attributes change. The gap has widened as competitors have moved toward AI-driven personalization — content feeds that surface role-specific, location-specific material automatically, updated as HRIS data changes without IT involvement. SharePoint's static model requires the same IT-administered configuration it always has to achieve what newer platforms handle automatically. The practical ceiling for personalization in SharePoint sits where the floor begins on modern alternatives. ## Poor multi-channel reach SharePoint treats all employees as if they share the same communication preferences. There is no native mechanism for reaching employees via SMS, mobile push notifications, or targeted email campaigns driven by employee profile attributes. Communication happens within the platform — which means it only reaches employees who are actively logged in and navigating the intranet. For frontline workers whose jobs don't include scheduled computer time, this creates a structural gap. A time-sensitive compliance update that lives in a SharePoint page reaches only employees who happen to visit that page. Modern platforms deliver the same communication via push notification to a personal device, SMS to a work phone number, or a targeted email — whichever channel the employee's profile indicates they're most likely to see. Multi-channel delivery isn't a feature. It's the difference between a communication that was sent and one that was received. ## What comes after recognizing SharePoint's limits Organizations that conclude SharePoint isn't working for their frontline workforce typically face two follow-up questions: what do independent analysts say about the alternatives, and what does a genuine evaluation framework look like beyond vendor-supplied comparisons? MangoApps was assessed as part of a [leading research firm's evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) of intranet platforms in 2026. The [ClearBox 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides structured scoring across governance, mobile access, personalization, and communication targeting — the same dimensions where SharePoint's structural limitations are most visible. Both resources give organizations evaluating alternatives an independent baseline that doesn't rely on vendor positioning. For organizations already running SharePoint and managing its constraints, the more immediate question is which limitations are structural and which are configurable. That distinction matters for scoping the evaluation: if the bottleneck is IT capacity to maintain customizations, a lighter-weight platform may resolve it. If the bottleneck is the access barrier for frontline workers — corporate credentials, VPN requirements, device dependencies — the solution requires rethinking the infrastructure layer, not reconfiguring the existing one. ## The case for switching that starts with architecture The standard argument for replacing SharePoint is operational: the platform is expensive to configure, hard to maintain, and poorly suited to frontline workers. That argument is accurate, and it's incomplete. The deeper issue is that SharePoint's architecture was designed for a workforce that doesn't describe most organizations today. It assumes corporate credentials, managed devices, desk access, and an IT team with SharePoint-specific expertise. For organizations where those assumptions hold, it's a workable platform at significant cost. For organizations with a mixed workforce — desk-based employees at headquarters and frontline workers at the point of care, the point of sale, or on the distribution center floor — SharePoint's limitations aren't edge cases. They're the daily experience for the majority of employees. A [modern intranet platform](/solutions/modern-intranet) built for the full workforce changes the access equation: frontline workers authenticate on a personal device without corporate credentials, content governance runs on automated rules rather than manual effort, and search spans connected systems rather than stopping at the SharePoint boundary. The financial case for the switch begins with the same math that makes SharePoint's total cost of ownership look different from its licensing fee: maintaining a platform that 80% of the workforce can't effectively use carries a cost, even when that cost doesn't appear in the procurement line item. --- # Why SharePoint’s Search Capabilities Don’t Cut It **Author:** Mason Hager **Published:** 2023-08-17 **Category:** replace-sharepoint Trying to search for information on SharePoint is next to impossible.  At its core, SharePoint is a content management system for storing documents. It simply doesn’t have the ability to provide a sufficient search experience for users.  As a result, employees have to comb through hundreds of documents to locate a resource, becoming disengaged and […] ## Why SharePoint's Search Capabilities Don't Cut It Trying to search for information on SharePoint is next to impossible. At its core, SharePoint is a content management system for storing documents. It simply doesn't have the ability to provide a sufficient search experience for users. As a result, employees have to comb through hundreds of documents to locate a resource, becoming disengaged and frustrated in the process. Per IDC, employees already spend an average of 2.5 hours per day searching for information — SharePoint's search limitations make that number worse, not better. With an enormous amount of information and data being stored in SharePoint, finding specific files or information can be like searching for a needle in a haystack. *In this article, we'll tackle the challenges of using SharePoint's search functionality, walk through configuration workarounds you can try inside SharePoint, and explain what alternatives are available to you.* ## The Challenges Of SharePoint's Search Capabilities **When trying to search for information in SharePoint, users may face several common challenges, some of which include:** **Incomplete or Outdated Content:** With limited auto-governance capabilities, admins have to manually refresh content on SharePoint. As a result, employees have to comb through a lot of irrelevant information to locate a specific resource. This hinders productivity and creates a frustrating employee experience. **Lack of Relevant Results:** SharePoint often doesn't return a result unless the search query matches the content exactly. We've seen many companies switch to MangoApps because SharePoint requires them to type in an 'exact match' to populate the desired results. **Poor Security and Permissions:** User permissions influence SharePoint's search results. If the user doesn't have access rights to a piece of content, it won't appear in the search results. This causes problems when permissions aren't in line with user roles, which can only be resolved with IT involvement. Issues like this are rampant in SharePoint implementations and contribute to the hidden costs of SharePoint. **Lack of a Mobile Search Experience:** End users often face usability issues or limitations when searching on smartphones or tablets. This is a frontline workforce exclusion problem, not just a UX inconvenience. Per Emergence Capital, 80% of the global workforce is deskless — and SharePoint's mobile search gaps mean the majority of employees are effectively locked out of the knowledge management tools their desk-based colleagues rely on. **Limited Scalability:** For organizations with large SharePoint environments, search performance and scalability can be challenging. This causes slower search responses or timeouts, creating a massive waste of time for employees. See our article on [Frontline Intranet Requirements: A Practical Checklist for Replacing SharePoint](/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) for a broader discussion of this topic beyond search functionality. ### SharePoint Makes It Difficult To Search For Information Due to SharePoint's limited auto-governance capabilities, it is hard to keep information organized and up to date, which impacts searchability. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools — a figure that reflects how quickly workers give up on platforms that don't surface what they need. SharePoint also has historically struggled to handle large volumes of data effectively. As organizations accumulate vast amounts of content over time, the search performance can degrade. As a result, companies experience slower search responses and a less-than-optimal user experience. Configuring SharePoint's search settings is extremely complex and requires a dedicated IT team with specialized expertise. Most organizations can't dedicate the IT resources required to maintain SharePoint. In addition, the limitations of the actual search functionality can hinder an employee's ability to find relevant information. This leads to frustration and reduced productivity. ## Can You Fix SharePoint Search? Configuration Workarounds to Try Before evaluating alternatives, it's worth understanding what SharePoint's own configuration options can — and cannot — address. The following workarounds are commonly recommended by SharePoint administrators, but each comes with meaningful limitations. **1. Query Rules** Query rules let administrators promote specific results or change the ranking of results based on conditions (e.g., a specific keyword triggers a promoted result). This can help surface high-priority documents more reliably. The limitation: query rules require ongoing manual maintenance and IT involvement every time content changes, which doesn't scale in dynamic organizations. **2. Search Refiners and Managed Metadata** Adding refiners (filters) to the search results page — such as content type, department, or date — helps users narrow results without needing an exact-match query. This requires a well-maintained managed metadata taxonomy. The limitation: if your metadata is inconsistent or incomplete (a common problem in large SharePoint environments), refiners surface the same noise problem in a different format. **3. Content Type Optimization** Standardizing content types across your SharePoint libraries ensures the search index can categorize documents correctly. Properly configured content types improve relevance significantly. The limitation: retrofitting content types onto an existing, large SharePoint environment is a substantial IT project — SharePoint implementation costs range from $15,000 for basic setups to $150,000+ for enterprise deployments, and governance remediation adds to that figure. **4. Crawl Schedule and Index Freshness** Adjusting the crawl schedule so SharePoint re-indexes content more frequently reduces the problem of stale search results. The limitation: more frequent crawls increase server load and can degrade performance in large environments — the exact scalability problem described above. **The honest assessment:** these workarounds can reduce friction at the margins, but they don't resolve SharePoint's structural limitations around exact-match dependency, mobile access, or permission-driven result gaps. Per Social Edge Consulting, nearly a third of employees never log in to the intranet at all — and poor search is a primary driver of that abandonment. If your organization has already invested significant IT effort in SharePoint configuration and search quality is still poor, the configuration ceiling may have been reached. For organizations evaluating whether to remediate or replace, the [SharePoint Server 2016/2019 Migration Checklist: A Practical Plan](/articles/sharepoint-server-2016-2019-migration-checklist) provides a structured framework for that decision. ## Find What You Need Quickly With MangoApps MangoApps, a digital work hub designed to boost productivity, enhance employee retention, inspire engagement, and align your employees, tops the list of SharePoint alternatives. When it comes to searching for information within SharePoint, the platform's poor functionality limits your employees' ability to find things. Searching for a resource or locating a correct version of a document is nearly impossible. With MangoApps, you can empower employees with global search functionality that can deliver exactly what they're looking for — in seconds. Unlike SharePoint's exact-match dependency, MangoApps uses semantic search to surface relevant results even when the query doesn't match document text precisely. Modern [knowledge management tools](/solutions/knowledge-management) built on this model eliminate the need to search each repository separately — providing universal search across SharePoint, Google Drive, Box, and Dropbox from a single interface. MangoApps brings a unified search experience to your enterprise with global search. Employees can find all of their content, conversations, and data in one place, no matter where it lives. Having a strong, unified search function powers productivity and improves employee sentiment by ensuring that everything your team needs is easy to find. OU Health achieved 87% workforce engagement within months of launching a branded employee app built on MangoApps — a concrete benchmark for what modern intranet adoption can look like when search actually works. Per Social Edge Consulting, 91% of organizations operate an intranet, but only 13% of employees use it daily. The gap between deployment and daily use is largely a search and findability problem — one that a [modern intranet](/solutions/modern-intranet) platform is specifically designed to close. **Imagine a world where you can:** - Put search results at your employees' fingertips - Immediately find relevant search results by applying filters to your search - Empower frontline employees with access to information while they're on the go — including workers without corporate email addresses - Know that the resource you're looking at is the current version For a third-party evaluation of how MangoApps compares to other intranet platforms on search and employee experience, see [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report). ## Learn How Our Customers Use MangoApps - Why SharePoint Was Insufficient – National Church Residences Case Study - Enabling Two-Way Communication With MangoApps – Morningstar Living Case Study - Harnessing An Employee SuperApp To Replace SharePoint – OU Health Case Study - [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study) ## Frequently Asked Questions About SharePoint Search ### Can I improve SharePoint search without replacing the platform? Yes, to a degree. Query rules, managed metadata refiners, content type standardization, and adjusted crawl schedules can all improve search relevance in SharePoint. However, these fixes require sustained IT investment and don't address structural limitations like exact-match dependency, mobile access gaps, or permission-driven result exclusions. Organizations that have already invested heavily in SharePoint configuration and still experience poor search quality are likely hitting the platform's architectural ceiling rather than a configuration problem. The [Intranet Governance Plan: A Practical Model for a Modern Intranet](/articles/sharepoint-server-2016-2019-replacement-intranet-governance-plan) outlines how to evaluate whether remediation or replacement is the right path. ### What does poor search actually cost an organization? The costs are both direct and indirect. Per IDC, employees spend 2.5 hours per day searching for information — in a 1,000-person organization, that represents thousands of hours of lost productivity weekly. SharePoint implementation and governance costs range from $15,000 for basic setups to $150,000+ for enterprise deployments, with first-year total expenses for 1,000 users reaching $130,000–$426,000 when customization, migration, and governance are included. Beyond IT spend, poor search drives disengagement: replacing a single frontline employee costs $4,400–$15,000 on average, and search frustration is a documented driver of turnover. Per Social Edge Consulting, nearly a third of employees never log in to the intranet — a signal that the tool isn't meeting their needs. ### What should I look for in a SharePoint alternative for search? The most important capabilities to evaluate are: semantic (non-exact-match) search, universal search across multiple repositories (SharePoint, Google Drive, Box, Dropbox), mobile-first access for frontline workers, role-based content surfacing, and a [content governance engine](/key-features/content-governance-engine) that keeps results current without manual IT intervention. Platforms that provide [knowledge bases](/key-features/knowledge-bases) with structured content alongside search tend to reduce the volume of search queries altogether by making high-frequency information immediately accessible. For a structured evaluation framework, the [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides independent analyst context on what separates modern platforms from legacy document repositories. --- # The Hidden Costs of SharePoint **Author:** Mason Hager **Published:** 2023-08-14 **Category:** replace-sharepoint It’s a tale as old as time. An organization implements SharePoint because they’re already using Microsoft products and it seems like the costs of SharePoint will be cheaper than any alternative. While SharePoint does offer out-of-the-box solutions, many organizations find that they need to customize these solutions to meet their specific needs. When coupled with […] # The Hidden Costs of SharePoint It's a tale as old as time. An organization implements SharePoint because they're already using Microsoft products and it seems like the costs of SharePoint will be cheaper than any alternative. But the sticker price of licensing tells only a fraction of the story. SharePoint's first-year total cost for a 1,000-user organization ranges from $130,000 to $426,000 when implementation, customization, and licensing are combined — far exceeding the licensing line item alone (per MangoApps SharePoint alternatives cost model, Awesome Technologies Inc. 2025). Understanding where those costs accumulate is the first step toward making a defensible platform decision. While SharePoint does offer out-of-the-box solutions, many organizations find that they need to customize these solutions to meet their specific needs. When coupled with ongoing maintenance, the cost of training users, and other expenses, SharePoint can quickly get expensive. **In this article, we'll pull back the curtains and reveal how all these hidden costs can stack up.** ## An Overview of SharePoint and Its Hidden Costs **Customization and Development Expenses:** SharePoint requires a significant amount of customization to meet specific organizational requirements. This often involves hiring SharePoint developers which can significantly increase costs. Enterprise SharePoint deployments can cost $150,000 or more in implementation alone, before any ongoing maintenance or third-party tool spend (per MangoApps SharePoint alternatives cost model, Awesome Technologies Inc.). When deployment requires months of IT-led customization, the productivity cost compounds daily — delayed time-to-value is itself a measurable expense that rarely appears in budget proposals. **Maintenance and Updates:** SharePoint requires ongoing maintenance and updates, which demands a dedicated IT staff. This will take expensive IT specialists' time away from more meaningful projects for your organization. **User Training and Adoption:** Training sessions for employees to learn how to use SharePoint are costly. Without adequate mobile support, frontline employees are typically unable to access SharePoint unless they visit a shared computer — a critical gap given that 80% of the global workforce is deskless, per Emergence Capital. Replacing a single frontline employee costs between $4,400 and $15,000, which means a poor mobile intranet experience isn't just an inconvenience — it's a measurable retention risk that compounds across every disengaged worker who can't access the tools they need. **Licensing Costs:** SharePoint Online licensing runs $5–$20 per user per month, translating to $60,000–$240,000 annually for a 1,000-person organization — before a single dollar of customization, training, or support is added. **Data Storage Costs & Migration Expenses:** As data grows, so does the need for storage. The cost of expanding SharePoint storage capacity can be substantial and can decimate your bandwidth for other tools. In addition, moving data from an old system to SharePoint can be a costly and time-consuming process. A practical [SharePoint Server 2016/2019 Migration Checklist: A Practical Plan](/articles/sharepoint-server-2016-2019-migration-checklist) can help organizations scope these expenses before committing. **Third-party Tools:** Due to the lack of a complete feature offering, organizations that implement SharePoint typically require additional third-party tools. This adds to the cost of your organization's tech stack. SharePoint integrates reasonably well within the Microsoft ecosystem but creates significant friction with non-Microsoft platforms — friction that manifests as integration projects, duplicate data entry, and broken workflows. A modern [solutions/modern-intranet](/solutions/modern-intranet) platform with native integrations eliminates much of this spend before it starts. **Compliance and Security Costs:** Ensuring SharePoint meets industry-specific compliance and security standards can also add to the overall expenditure. With SharePoint 2013 & other outdated platforms, support is no longer included. Thus, your IT department will have to manually configure the platform to keep it compliant with industry standards. ### The High Price Tag of Using SharePoint Investing in SharePoint is no small endeavor and organizations should be cognizant of the comprehensive costs involved. Apart from the initial investment, other significant monetary factors include the cost of customization, maintenance, user training, licensing, data storage, third-party tools, migration, and compliance. Each of these elements can add up and significantly inflate the overall price tag. It is crucial for organizations to evaluate their specific needs, budget constraints, and IT capabilities before deciding to invest in SharePoint. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) offers an independent benchmark for comparing total cost of ownership across leading platforms. ## 7 Limitations of SharePoint as an Intranet Platform Now that we've discussed the hidden costs that can arise from a SharePoint implementation, let's dive into some common limitations we've seen from the platform that you should be aware of: 1. **Complexity:** SharePoint's complexity can be overwhelming, especially for users without technical expertise. It can only be administered by people with significant IT expertise. 2. **Integration Challenges:** While SharePoint integrates well with other Microsoft products, it does not integrate well with other third-party tools, creating inefficiencies in the employee experience. 3. **Limited Customization:** Organizations without significant IT resources are not able to tailor SharePoint to meet all their specific customization requirements. 4. **Resource-Intensive:** SharePoint can be extremely resource-intensive, necessitating a robust infrastructure and a solid IT team for maintenance and troubleshooting. 5. **Performance Issues:** SharePoint may face performance issues when dealing with larger data volumes or when multiple users access the system simultaneously. 6. **Cost:** As highlighted earlier, the costs associated with implementing and maintaining SharePoint can be quite high, making it a less viable option for smaller organizations or those with tight budget constraints. 7. **Mobile Access:** SharePoint's mobile access is not as user-friendly as its desktop version, which could pose challenges in today's mobile-centric world. By using SharePoint, your frontline employees would be hung out to dry. Per Social Edge Consulting, 91% of organizations operate an intranet — yet only 13% of employees use it daily, and nearly a third never log in at all. Poor mobile experience is a primary driver of that gap. ### Why Most SharePoint Implementations Fail to Meet Objectives **There are several factors that can contribute to a failed SharePoint implementation, including:** **Insufficient Planning:** A common issue is inadequate planning before rolling out SharePoint. Implementations often fail when organizations do not fully understand their requirements or fail to align SharePoint's capabilities with their business objectives. A structured Intranet Governance Plan: A Practical Model for a Modern Intranet can prevent many of these failures before they start. **Lack of User Training and Adoption:** Even the best tools are ineffective if users do not know how to use them correctly. Failure to invest in proper user training can lead to low adoption rates and ineffective use of SharePoint. IDC research finds employees spend 2.5 hours per day searching for information — a figure that rises sharply when the intranet is hard to navigate or inaccessible on mobile. **Poor Governance:** If there is a lack of clear rules and policies for using SharePoint, it can result in unsystematic use of the tool, leading to confusion and inefficiency. **Inadequate IT Support:** A lack of dedicated IT support can lead to unresolved technical issues, causing frustration among users and hampering productivity. **Lack of Continuous Improvement and Updates:** Technology is continually evolving, and so are organizational needs. Failure to regularly update and improve the SharePoint system to match these changes can lead to its eventual ineffectiveness. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools — a signal that most intranet deployments, SharePoint included, fail to become genuinely useful knowledge management tools in daily work. ### Introducing MangoApps — A SharePoint Alternative **MangoApps** is a unified SharePoint replacement built as an Employee SuperApp for organizations with a frontline workforce. With MangoApps, you're able to give 100% of your workforce all the tools they need in one employee app to increase productivity, improve retention, and boost employee engagement. The platform is customizable and offers a wide range of unique functionalities aimed at solving any business need — including a [solutions/knowledge-management](/solutions/knowledge-management) layer that surfaces the right information without requiring employees to know where to look. MangoApps includes all the tools you need to provide a unified employee experience. Just turn on the tools you want and turn off the ones you don't. Unlike SharePoint, with MangoApps employees can be kept engaged and informed and have instant access to the information they need, when they need it. Organizations replacing SharePoint with MangoApps have achieved 87–90% workforce engagement within the first few months of launch (per MangoApps OU Health and Kansas City Chiefs case studies). TeamHealth consolidated 200+ systems into a single mobile dashboard after moving off fragmented intranet tooling (per MangoApps TeamHealth case study). For organizations evaluating their options, the [Frontline Intranet Requirements: A Practical Checklist for Replacing SharePoint](/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) is a useful starting point. ### Learn How Our Customers Use MangoApps - Why SharePoint Was Insufficient – National Church Residences Case Study - Enabling Two-Way Communication With MangoApps – Morningstar Living Case Study - Harnessing An Employee SuperApp To Replace SharePoint – OU Health Case Study - [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study) ## Is SharePoint Worth the Total Cost of Ownership? The honest answer for most organizations is: not when the full cost is visible. Licensing alone runs $60,000–$240,000 annually for a 1,000-person organization. Add implementation ($150,000+ for enterprise deployments), ongoing IT maintenance, third-party tool subscriptions, compliance configuration, and the productivity drain of 2.5 hours per day lost to information search (per IDC), and the total first-year cost can reach $426,000 — for a platform that SWOOP Analytics finds employees use for an average of six minutes per day. For organizations with a significant frontline or deskless workforce, the calculus is even clearer. When 80% of the global workforce is deskless (per Emergence Capital) and SharePoint's mobile experience leaves those workers without reliable access, the hidden cost isn't just IT overhead — it's turnover, disengagement, and the $4,400–$15,000 replacement cost for every frontline employee who leaves. The alternative to SharePoint's complexity isn't simply a simpler tool. Modern intranet platforms deliver AI-powered personalization, native integrations that eliminate third-party tool sprawl, and deployment timelines measured in weeks rather than months — reducing both the governance burden and the IT overhead that make SharePoint so expensive to sustain. If your organization is approaching a SharePoint renewal or migration decision, start with a clear-eyed accounting of every cost category covered here, benchmark against independent research like the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report), and evaluate whether a purpose-built employee experience platform closes the gap between what SharePoint costs and what it actually delivers. ## What Should I Look for in a SharePoint Replacement? The most important criteria for a SharePoint replacement are mobile-first access for frontline workers, native integrations that eliminate third-party tool costs, a governance model that doesn't require dedicated IT administrators, and measurable adoption metrics. A platform that functions as a true knowledge management tool — surfacing information proactively rather than requiring employees to navigate folder hierarchies — addresses the core failure mode that makes SharePoint expensive: the 2.5 hours per day employees spend searching for information (per IDC). Review the [Frontline Intranet Requirements: A Practical Checklist for Replacing SharePoint](/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) for a structured evaluation framework. ## How Long Does It Take to Migrate Off SharePoint? Migration timelines vary by data volume, governance complexity, and the destination platform, but organizations that plan thoroughly — auditing content, establishing a governance model before migration, and running parallel systems during transition — consistently report faster time-to-value than those that treat migration as a purely technical exercise. The [SharePoint Server 2016/2019 Migration Checklist: A Practical Plan](/articles/sharepoint-server-2016-2019-migration-checklist) outlines the key phases and decision points to scope the effort accurately before committing resources. --- # SharePoint vs. MangoApps: Which Intranet Platform Drives Better Adoption? **Author:** Mason Hager **Published:** 2023-08-08 **Category:** replace-sharepoint SharePoint can be one of the most frustrating document management platforms your company will ever use. It is riddled with hidden costs, lacks the basic functionality needed to connect an organization’s entire workforce, and can be a massive time-suck for the IT department. It also ALWAYS leads to a frustrating and fragmented employee experience. Organizations […] # SharePoint vs. MangoApps: Which Intranet Platform Actually Reaches Your Frontline? The adoption numbers are stubborn. According to Social Edge Consulting, 91% of organizations operate some form of intranet, yet only 13% of employees use one daily — and nearly a third never log in at all. SWOOP Analytics captures the behavioral result: the average employee spends six minutes per day in these tools. The most common explanation is training or change management. The more accurate explanation is access. According to Emergence Capital, 80% of the global workforce is deskless — working in healthcare, retail, logistics, and manufacturing without a company-issued computer. When an intranet requires a corporate email address, a VPN connection, or device provisioning just to log in, it has already excluded the majority of most organizations' workforces before a single page loads. That structural mismatch is what determines whether an intranet generates six minutes per day or genuine daily engagement. This article runs the comparison directly: what SharePoint actually costs, where its access model fails, and why the adoption benchmark gap between SharePoint and modern intranet platforms is a design difference, not a deployment difference. ## What SharePoint costs before you count the hidden line items A 1,000-user SharePoint intranet costs between $130,000 and $426,000 in the first year — licensing, implementation, customization, and maintenance combined (Awesome Technologies Inc., 2025 cost model). That range exists because SharePoint is not, by design, an intranet. It is a document management and collaboration platform that organizations configure into an intranet through a combination of third-party applications, custom development, and sustained IT labor. Hidden cost categories that push organizations toward the top of that range: - **Custom branding and navigation.** SharePoint's default templates don't meet intranet usability standards without modification — most organizations require significant development work before the platform navigates like an intranet. - **Third-party add-ons** for org charts, people directories, and advanced search functionality that SharePoint does not include natively. - **IT support overhead** for permissions failures, search indexing issues, and access management across organizational changes. - **Interface retraining** as Microsoft 365 update cycles change SharePoint's navigation and features on schedules that organizations don't control. - **Content debt** when IT becomes the publication bottleneck and intranet pages stop being updated because the people responsible for content cannot publish it themselves. The useful financial comparison is not licensing cost versus licensing cost. It is total first-year spend versus total first-year spend, measured against actual adoption outcomes. When an organization spends $250,000 in year one on a platform most frontline workers cannot access, the cost-per-active-user number is what drives the evaluation — not the contract line item. ## Why the access model sets the adoption ceiling IDC measures the downstream cost of information inaccessibility at 2.5 hours per day per employee spent searching for information they cannot find in one place. That number does not shrink by improving SharePoint's search indexing. It shrinks when the platform employees are supposed to use is reachable from the device they actually carry. SharePoint requires a corporate email address or Azure Active Directory account, and in many configurations a VPN or company-issued device. For the shift nurse, the distribution center operations manager, and the retail floor associate — the 80% of the global workforce that Emergence Capital classifies as deskless — these requirements are not inconvenient. They are categorical barriers that make the intranet invisible before any engagement decision is made. MangoApps removes the corporate credentials requirement entirely. Employees log in through a branded [employee app](/solutions/employee-app) on a personal device — no corporate email address, no VPN, no IT provisioning required. The platform supports 50+ languages with real-time translation, removing the secondary barrier that prevents frontline access in multilingual workforces. When TeamHealth moved off legacy intranet tools, the organization consolidated more than 200 disparate systems into a single mobile dashboard. That consolidation became possible when the access model changed, not when the content strategy improved. No amount of better content reverses an access model that excludes the workforce before they open the app. ## The adoption benchmark gap OU Health achieved 87% workforce engagement within a few months of launching a branded employee app through MangoApps. The benchmark for large enterprise deployments of modern, mobile-first intranet platforms is 90% frontline adoption within the first six months. The SWOOP Analytics six-minutes-per-day SharePoint figure is not in the same category as these outcomes. It reflects a platform that desk workers use occasionally and frontline workers largely cannot reach. An 87% workforce engagement rate reflects a platform designed around how employees actually work — personal devices, varied shifts, no corporate credential requirements. SharePoint case studies rarely report frontline adoption rates as a headline metric. That absence is informative: when a platform requires corporate credentials for access, the frontline population is not the baseline user, and measuring their adoption documents the gap rather than celebrating the deployment. ## Eight dimensions that matter in the comparison | Dimension | SharePoint | MangoApps | |---|---|---| | Frontline access (no corporate email) | Not supported by default | Personal device login, no corporate credentials | | First-year TCO, 1,000 users | $130K–$426K (Awesome Technologies Inc.) | Consistently below SharePoint range | | Content management by non-IT staff | IT-dependent for most changes | Direct admin access for HR and comms teams | | AI content personalization | Copilot add-on (separate license + security review) | Built into base platform | | Multi-language support | Partial; configuration-dependent | 50+ languages, real-time translation | | Compliance certifications | SOC 2, ISO 27001 | HITRUST, SOC 2 Type II, ISO 27001 | | Migration tooling | Self-managed | Built-in SharePoint migration services | | Time to active intranet | Months to a year | Weeks | The migration row carries more weight than it appears to. The primary reason organizations stay on platforms their workforces barely use is the perceived switching cost. Built-in migration services reduce that cost directly, shortening the window where inaction is financially easier than switching. ## What AI personalization actually changes The personalization gap between SharePoint and MangoApps is structural, not incremental. SharePoint's Copilot integration requires a separate add-on license and a security review before it is active — it is not a standard part of the platform most organizations have deployed. For many organizations, it is a year-two initiative rather than a launch feature. MangoApps' AI-driven content surfacing matches employees with relevant updates, documents, and communications based on role, location, and team. The practical effect: an employee opens the app and sees what applies to their facility and their job function, not a company-wide feed written for a different audience. This is the mechanism that drives sustained daily engagement after launch incentives fade. An employee who encounters content written for someone in a different role or location does not return habitually. Personalization is not a feature enhancement in this context — it is the difference between the six-minutes-per-day outcome and the kind of daily active use that makes the intranet the default answer to a question instead of the last resort. ## The retention calculation most evaluations skip Replacing a frontline employee costs between $4,400 and $15,000 depending on role (industry research cited on MangoApps' mobile employee app product page). An intranet that 70% of frontline workers cannot access is a retention risk, not merely a productivity gap. Every policy update that never reaches a shift worker, every safety communication requiring a corporate device most employees don't carry, and every peer recognition moment visible only to desk workers is a signal that the organization did not account for frontline employees when making the technology decision. The question that reframes the procurement conversation is not "what does this platform cost?" but "what does failing to reach 70% of the workforce cost per year in attrition alone?" For large frontline organizations, that number reliably exceeds the annual licensing delta between SharePoint and a modern alternative. The [ClearBox 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) evaluates compliance posture, access models, and AI capabilities across 30+ platforms using the criteria enterprise buyers apply in formal procurement — a more actionable reference than any vendor security page for organizations conducting a rigorous evaluation. ## Four measurements that build the business case Organizations building the procurement case for a SharePoint replacement can pull these data points from their current system before external evaluation begins: **Monthly active users, segmented by desk and frontline.** A gap of more than 30 points between these two populations indicates an access model problem, not a content problem. Closing that gap requires a different platform design, not more training on the existing one. **Total first-year cost, fully loaded.** Model it against the $130K–$426K SharePoint benchmark with every cost category included — IT labor, add-ons, custom development, and retraining. Most organizations discover they are well within or above that range when the full picture is counted. **Content freshness rate.** The percentage of intranet pages updated in the last 90 days. On a platform where IT approval is required for publication, this number measures how much of the intranet is functioning as a live communication channel versus an archive employees have learned to ignore. **Search success rate.** The percentage of searches that result in a click. IDC's 2.5 hours per day of information-seeking time represents recoverable productivity — and search success rate is the direct measurement of whether it is being recovered. Improving this metric requires that the intranet be reachable and searchable by the full workforce, not just the employees who have corporate devices. A platform that moves all four of these metrics within 12 months is worth the switching cost. A platform that improves one while leaving the others flat is a partial solution at best. ## The design problem that training cannot fix The 13% daily active user rate and the six-minutes-per-day engagement average are not outcomes that training can fix. They are predictable results of deploying a platform designed for desk-based knowledge workers against a workforce that is 80% deskless. A [modern intranet](/solutions/modern-intranet) built for that workforce changes the access model, the administration model, and the personalization layer simultaneously. MangoApps' independent recognition in [a leading research firm's 2026 intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides an external reference point for organizations conducting a formal selection process beyond the SharePoint ecosystem. SharePoint's $130K–$426K first-year range is a significant commitment. The question worth asking before renewal is what that commitment has produced in active user rates, frontline engagement, and content freshness — and whether the same investment in a platform built for the actual workforce would produce a measurably different outcome. --- # Avoid SharePoint – Increase Employee Efficiency With MangoApps **Author:** Mason Hager **Published:** 2023-08-03 **Category:** replace-sharepoint Why You Should Avoid SharePoint Many people see SharePoint as the go-to solution for business collaboration and document management, but it’s far from ideal. In this article, we’ll dive into some of the major reasons why you should avoid SharePoint. SharePoint is a legacy tool, even if it has been given a cloud facelift. It simply […] # Why You Should Avoid SharePoint — and What to Use Instead SharePoint is the default choice for many organizations, but default rarely means best. If your goal is to increase employee efficiency, reduce IT overhead, and give every worker — desk-based or frontline — a consistent digital experience, SharePoint creates more problems than it solves. This article explains the specific reasons to avoid SharePoint and shows, with concrete feature comparisons and cost figures, how a modern intranet platform addresses each one. --- ## The Core Problem: SharePoint Was Built for a Different Era An **intranet**, by definition, is a private internal network that helps employees find information, communicate, and collaborate. That definition sounds simple, but execution is everything. According to Social Edge Consulting, 91% of organizations operate an intranet — yet only 13% of employees use one daily, and nearly a third never log in at all. SharePoint is the most common platform behind those numbers, and its design is a significant reason why adoption stays so low. SharePoint began as an on-premises document repository in 2001. Its cloud version is an architectural update, not a rethink. The result is a platform that carries two decades of legacy complexity into an era when employees expect consumer-grade experiences on any device. --- ## Three Specific Reasons to Avoid SharePoint ### 1. The Real Cost Is Far Higher Than the License Fee SharePoint licensing is only the beginning. Implementation costs range from $15,000 for basic setups to $150,000 or more for enterprise deployments, before any ongoing IT staffing is counted (per Awesome Technologies Inc. cost analysis). When you add licensing, implementation, and IT overhead together, a conservative first-year total cost for a 1,000-user SharePoint organization runs between **$130,000 and $426,000**. Most IT teams also need dedicated full-time resources to develop, customize, and maintain a SharePoint environment. For organizations without a large IT department, that overhead is unsustainable. Smaller organizations or those with distributed workforces often find that the investment never pays off because adoption never reaches the level needed to justify it. ### 2. Poor User Experience Drives Low Adoption — and Low Adoption Wastes the Investment SharePoint's interface is notoriously difficult to navigate. According to SWOOP Analytics, the average employee spends just **six minutes per day** using intranet tools — a figure that reflects how quickly enthusiasm for complex platforms fades. Meanwhile, IDC research shows employees spend **2.5 hours per day** searching for information they cannot easily find. A platform that was supposed to solve the information-access problem is instead contributing to it. SharePoint's search is siloed. Its mobile experience is an afterthought. According to Emergence Capital, **80% of the global workforce is deskless** — working in retail, healthcare, manufacturing, logistics, or field services. SharePoint's desk-centric design leaves those workers without meaningful access unless they visit a shared computer. That is not a minor gap; it is a structural exclusion of the majority of the global workforce. SharePoint also lacks native support for frontline access without a corporate email address, a VPN, or a company-issued device — requirements that are simply incompatible with how frontline work happens. ### 3. SharePoint Is Not a Complete Intranet — It Is a Starting Point That Requires Constant Addition SharePoint does not include a native news feed, community-building tools, employee recognition, task management, or learning modules. To build a complete digital workplace on SharePoint, organizations must integrate separate Microsoft products (Teams, OneDrive, Viva) and often third-party tools on top of those. Each integration adds cost, maintenance burden, and a fractured employee experience. SharePoint's integration complexity is now a documented gap. Modern alternatives offer pre-built connectors to 200 or more enterprise systems — including HRIS, LMS, and identity providers — without custom development (per competitive movement signals and MangoApps product pages). SharePoint, by contrast, often requires custom development for integrations that other platforms handle out of the box. Context switching between disconnected tools is not a minor inconvenience. It fragments attention, slows work, and reduces the likelihood that employees will engage with any single platform consistently. --- ## MangoApps vs. SharePoint: A Direct Comparison The table below compares SharePoint and MangoApps across the dimensions that matter most to organizations evaluating a switch. | Dimension | SharePoint | MangoApps | |---|---|---| | **Mobile access for frontline workers** | Requires corporate email, VPN, or company device | Personal iOS or Android device, no corporate email or VPN required | | **First-year cost (1,000 users)** | $130,000–$426,000 (licensing + implementation + IT overhead) | Transparent per-user pricing; no hidden implementation surcharges | | **Implementation timeline** | Months of IT-led customization | Branded experiences for 1,000+ employees configurable in minutes using AI-assisted setup | | **Search scope** | Siloed within SharePoint | Universal search across SharePoint, Google Drive, Box, Dropbox, and connected systems | | **Pre-built integrations** | Limited; custom development often required | 200+ pre-built connectors to HRIS, LMS, and identity providers | | **Modules included** | Document management; other features require separate Microsoft products | Employee communications, work collaboration, content management, learning, and operations in one platform | | **Frontline / deskless support** | Desk-centric; limited offline capability | Mobile-first; offline support; shift and scheduling features built in | | **Daily active usage** | Average 6 minutes/day (per SWOOP Analytics) | OU Health achieved 87% workforce engagement within months of launch | | **AI capabilities** | Copilot (add-on, additional cost) | AI assistant integrated with OpenAI, Gemini, and Azure OpenAI for content surfacing and natural-language queries | --- ## How MangoApps Solves Each SharePoint Problem ### Lower, Predictable Total Cost of Ownership MangoApps offers transparent per-user pricing with no hidden implementation surcharges and no requirement for third-party tools to fill feature gaps. Organizations that replace SharePoint with MangoApps eliminate the cost of maintaining separate tools for communications, learning, and recognition — reducing overall tech stack spend rather than adding to it. ### An Experience That Works for Every Worker MangoApps is built mobile-first. Frontline employees can access the platform on personal iOS or Android devices without a corporate email address, a VPN, or a desk. This matters because, per Emergence Capital, 80% of the global workforce is deskless. A platform that cannot reach those workers is not a complete intranet — it is a desk-worker tool with a mobile app bolted on. TeamHealth consolidated more than 200 legacy systems into a single mobile dashboard using MangoApps. OU Health achieved 87% workforce engagement within months of launching a branded employee app on MangoApps. These are not vague adoption improvements; they are measurable outcomes from organizations that made the switch. For organizations with complex workforce structures, the [MangoApps employee app](/solutions/employee-app) is designed to serve both desk and deskless workers from a single platform without requiring separate configurations or licenses. ### A Unified Platform, Not a Collection of Integrations MangoApps includes employee communications, work collaboration, content management, learning, and operations modules in a single platform. Universal search spans connected systems — SharePoint, Google Drive, Box, Dropbox — so employees find what they need without switching contexts. Pre-built connectors to 200+ enterprise systems mean integrations that would require custom development in SharePoint are available out of the box. The [company portal](/key-features/company-portal) gives every employee a single, branded entry point to company news, resources, and tools. [Department sites](/key-features/department-sites) let teams maintain their own spaces without IT involvement. [Workspaces](/key-features/workspaces) support project-based collaboration with task management, file sharing, and discussion threads in one place. ### AI-Assisted Content and Configuration SharePoint's AI capabilities (Copilot) are an add-on that carries additional licensing cost. MangoApps integrates AI assistance — built on OpenAI, Gemini, and Azure OpenAI — for content surfacing, natural-language search, and platform configuration. Traditional intranets take months to deploy and require IT-led customization; modern platforms can build branded experiences for 1,000 or more employees in minutes using AI-assisted configuration (per Unily product page benchmarks). MangoApps operates in this category. --- ## Frequently Asked Questions ### How long does it take to migrate from SharePoint to MangoApps? Migration timelines depend on the volume of content and the number of integrations, but MangoApps' AI-assisted configuration means the initial branded environment can be stood up in days rather than months. Content migration from SharePoint document libraries is supported through MangoApps' integration layer. Most organizations are in production within weeks, not quarters. ### Does MangoApps replace Microsoft 365, or does it work alongside it? MangoApps is not a Microsoft 365 replacement. It integrates with Microsoft 365 — including SharePoint document libraries, OneDrive, and Teams — through pre-built connectors. Organizations that want to keep their Microsoft 365 investment can use MangoApps as the employee experience layer on top, surfacing Microsoft content through universal search and a unified interface. Organizations that want to reduce Microsoft licensing can use MangoApps' native content management and collaboration tools instead. ### What does MangoApps cost compared to SharePoint? MangoApps uses transparent per-user pricing. SharePoint's first-year total cost for a 1,000-user organization runs $130,000–$426,000 when licensing, implementation, and IT overhead are included. MangoApps eliminates the implementation cost spike and the ongoing IT staffing requirement for customization, making the total cost of ownership comparison favorable — particularly for organizations that currently pay for multiple tools to fill SharePoint's feature gaps. --- ## The Bottom Line: What to Do Next SharePoint's problems are structural, not cosmetic. High implementation costs, low daily usage, a desk-centric design that excludes 80% of the global workforce (per Emergence Capital), and a feature set that requires constant addition — these are not issues that a new SharePoint theme or a Copilot license will fix. If your organization is evaluating alternatives, the concrete next step is to map your current SharePoint costs (licensing + IT staffing + third-party tools) against a MangoApps quote for the same user count. The gap is typically significant. MangoApps' [modern intranet solution](/solutions/modern-intranet) covers the full scope of what SharePoint requires you to assemble from multiple products. For independent evaluation, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides a vendor-neutral assessment of the intranet market, including criteria for mobile support, search, integration depth, and total cost of ownership — the same dimensions where SharePoint consistently underperforms. If internal communications planning is part of your evaluation, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring their digital workplace investments this year. --- # Strategies To Improve Retail Employee Engagement **Author:** Mason Hager **Published:** 2023-08-01 **Category:** customer-success-stories A proven methodology for boosting engagement among retail employees, including examples from PetSmart Focusing on retail employee engagement brings a multitude of benefits that reverberate throughout the entire organization. Connected employees are more likely to collaborate seamlessly, share insights, and foster a strong sense of camaraderie, leading to improved teamwork and higher productivity on the […] ## A proven methodology for boosting engagement among retail employees, including examples from PetSmart Focusing on retail employee engagement brings a multitude of benefits that reverberate throughout the entire organization. Connected employees are more likely to collaborate, share insights, and foster a strong sense of camaraderie, leading to improved teamwork and higher productivity on the shop floor. Engaged employees exhibit greater dedication, enthusiasm, and a sense of ownership in their roles — and are far less likely to experience retail burnout. This translates to enhanced customer interactions, elevated customer satisfaction, and a positive brand reputation. Moreover, a connected and engaged workforce experiences reduced turnover rates, as employees feel valued and invested in the company's success. Altogether, these advantages contribute to a vibrant, customer-centric retail environment where employees are motivated, customers are delighted, and the business flourishes. Note that 80% of the global workforce is deskless, per Emergence Capital — meaning the majority of retail associates never sit at a desk or log into a company intranet. Yet per Social Edge Consulting, only 13% of employees use an intranet daily, and nearly a third never log in at all. Any strategy to improve retail employee engagement must account for this reality from the start. ## 14 Ways To Improve Retail Employee Engagement Keeping retail floor associates engaged is crucial for ensuring exceptional customer service, increased productivity, and overall business success. **Here are strategies to maintain high levels of engagement among your retail floor associates:** 1. **Provide Clear Expectations and Goals:** Set clear performance expectations and goals for your associates. When they understand what's expected of them and have measurable objectives to strive for, they feel a sense of purpose and direction. 2. **Offer Training and Development:** Invest in ongoing training and employee engagement through skill-building workshops, product knowledge sessions, and customer service training. Associates who see opportunities for growth are more likely to stay engaged. Digitizing onboarding and delivering mobile-accessible training can cut new-hire ramp time by 50%, per Beekeeper. For a deeper look at how to embed learning into daily work rather than treating it as a separate event, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). 3. **Foster a Positive Work Environment:** Create a positive and supportive atmosphere on the shop floor. Encourage open communication, teamwork, and a sense of camaraderie. Associates who feel valued and supported by their colleagues and managers are more likely to be engaged. 4. **Recognize and Reward Performance:** Implement a recognition program that celebrates associates' achievements. Regularly acknowledge and reward exceptional performance, whether through verbal praise, small incentives, or public recognition. Feeling appreciated boosts morale and engagement. For a real-world example of how a structured rewards program drives measurable outcomes, see [From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program). 5. **Empower Decision-Making:** Give associates the autonomy to make certain decisions within their roles. Empower them to solve customer problems, handle minor issues, and contribute ideas. This sense of responsibility enhances their ownership and engagement. 6. **Provide Opportunities for Feedback:** Create avenues for associates to voice their opinions and offer feedback. Regularly solicit their insights on processes, products, and customer interactions. Knowing their opinions matter enhances their engagement. Employee engagement surveys and questionnaires are a structured way to capture this input — for inspiration, see our guide to the questions to ask in a retail staff survey. 7. **Rotate Responsibilities:** By rotating tasks among associates, you offer your employees variety. This prevents monotony and keeps them engaged by experiencing different aspects of the retail environment. 8. **Offer Flexible Scheduling:** Provide flexibility in scheduling wherever possible. Acknowledge and accommodate personal commitments, which can reduce stress and increase overall job satisfaction. [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) offers practical frameworks for balancing coverage needs with associate preferences. 9. **Use Technology to Enhance Engagement:** Leverage employee engagement software to connect associates on the shop floor. Retail frontline workers can access shifts, training, HR self-service, and task assignments from a single mobile app without requiring a company email or VPN, per MangoApps. AI-personalized communications — where content is curated by role and store location — ensure associates see what's relevant to them rather than a generic company-wide feed. Gamification elements can add an element of fun to tasks and learning. Employees spend 2.5 hours per day searching for information, per IDC; a well-configured mobile platform cuts that friction significantly. 10. **Invest in Well-Being:** Demonstrate a genuine concern for associates' well-being. Offer wellness programs, mental health support, and access to resources that promote work-life balance. 11. **Communicate Company Vision:** In retail, it is crucial to have a well-thought-out communication strategy. Regularly communicate the company's vision, mission, and goals to associates. Help them understand how their roles contribute to the bigger picture, fostering a sense of purpose. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) outlines how leading retailers are structuring these communications for frontline audiences. 12. **Celebrate Milestones:** Celebrate work anniversaries, birthdays, and personal milestones of your associates. When done well, personal connections and celebrations contribute to a positive and engaging work environment. 13. **Encourage Professional Relationships:** Facilitate mentorship and buddy programs to encourage associates to support each other's growth. These relationships can enhance their engagement and sense of community. 14. **Lead by Example:** Effective leadership plays a significant role in associate engagement. Lead by example, demonstrating enthusiasm, open communication, and a commitment to excellence. Remember that every associate is unique, so be open to adapting these strategies to suit individual preferences and needs. Consistently showing that you value and invest in your retail floor associates will go a long way in keeping them engaged and motivated. ## How PetSmart Keeps Employees Connected & Engaged Want to learn how PetSmart took its associate engagement to the next level? Before MangoApps, PetSmart relied on a WordPress-based site called **'The Dish'** to share company news, updates, and training videos. With the majority of their workforce located in stores and distribution centers, most PetSmart associates could not access The Dish unless they were connected to a shared device or VPN. PetSmart set out to find a solution that could increase employee engagement across its retail workforce. With over 50,000 associates spread across 1,600+ stores and 7 distribution centers, PetSmart wanted to find a tool that could reach their entire workforce, including the frontline associates who were disconnected from company-wide communications. PetSmart's journey with MangoApps began in October, and they launched **'Central Bark'** just a few months later with the goal of increasing engagement for their frontline workforce. PetSmart launched the 'opt-in' Central Bark app and immediately started garnering engagement from its associates. Since switching to MangoApps, PetSmart has seen significant improvements in its internal communications and overall engagement. **With Central Bark, PetSmart is able to:** - Gamify its internal comms strategy by incorporating contests, giveaways, themed campaigns, and more to generate engagement across associates. - Emphasize company culture to build stronger connections between associates and the PetSmart brand. - Leverage analytics to keep relevant content succinct and to the point. PetSmart can track engagement, reactions, views, and more to gauge the success of its internal comms strategy. ## Let's break down PetSmart's success: - Central Bark — 8% engagement on content (4X industry average). - PetSmart can connect & engage 100% of its workforce. - Associates are able to 'buy in' to the PetSmart culture, improving engagement company-wide. PetSmart's results are not an outlier. OU Health reached 87% workforce engagement within a few months of launching a branded employee app, per MangoApps. Branded employee apps targeting frontline retail workforces have achieved 90%+ adoption rates within the first several months of launch, per MangoApps. These outcomes reflect what becomes possible when engagement infrastructure is built for the frontline from the ground up, rather than adapted from an office intranet. ## See How PetSmart Generates Engagement Across Associates **Watch the full video to learn how PetSmart:** - Generates engagement across associates - Takes advantage of company-wide initiatives to improve adoption - Keeps associates up-to-date and engaged on a weekly basis ## How to Implement a Retail Employee Engagement Program: Where to Start The 14 strategies above cover the full landscape of retail employee engagement, but implementation order matters. Organizations that see the fastest results typically sequence their efforts in three phases. **Phase 1 — Fix access first.** If frontline associates cannot reliably reach communications, training, or recognition tools from their personal devices, every other strategy is undermined. Deploying a mobile-first platform — one that requires no company email and no VPN — is the prerequisite. Per SWOOP Analytics, employees average only six minutes per day using intranet tools; a purpose-built frontline app closes that gap by meeting associates where they already are. **Phase 2 — Connect learning to daily work.** Employee engagement training and on-the-job learning are most effective when they are embedded in the flow of work rather than scheduled as separate events. An LMS learning system integrated with your HRIS automatically syncs employee roles, permissions, and training records — eliminating manual admin overhead for retail managers, per MangoApps. Microlearning modules, video learning, and employee engagement courses delivered via mobile keep associates building skills without pulling them off the floor for extended periods. **Phase 3 — Measure and iterate.** Recognition programs, feedback loops, and communication campaigns all generate data. Use engagement analytics — views, reactions, survey completion rates, and employee engagement questionnaire scores — to identify which stores or departments are lagging and why. Integrating HRIS and LMS data gives managers a single view of participation, training completion, and recognition activity. For a comprehensive framework on evaluating frontline-focused platforms, [The Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026 and beyond](/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) is a practical starting point. For organizations ready to explore what a purpose-built platform looks like in practice, the [MangoApps retail industry page](/industries/retail) outlines how the platform is configured specifically for store environments. ## What Should I Look for in Employee Engagement Software for Retail? Not all employee engagement software is designed with the retail frontline in mind. When evaluating platforms, prioritize these criteria: - **No-email, mobile-first access:** Associates should be able to onboard and engage from a personal smartphone without a corporate email address or VPN. - **Integrated learning:** Look for a platform that combines communications, recognition, and an LMS learning system in one place — so training and employee engagement reinforce each other rather than living in separate tools. - **Role-based personalization:** AI-driven content feeds that surface relevant updates by role, department, and location reduce information overload and increase the likelihood that associates actually read and act on communications. - **Analytics and reporting:** Engagement metrics at the store, region, and individual level allow managers to intervene early when participation drops. - **HRIS integration:** Automatic syncing of employee roles and permissions removes administrative friction and ensures new hires are provisioned on day one. For a side-by-side look at how leading platforms stack up, [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides independent analyst context. ## The Bottom Line on Retail Employee Engagement Retail employee engagement is not a single initiative — it is an operating discipline that spans access, learning, recognition, communication, and leadership. The 14 strategies in this article give you the full menu. The PetSmart case study — 8% content engagement at 4x the industry average, 100% workforce reach — demonstrates what disciplined execution looks like at scale. The most important shift is structural: retail associates are deskless by definition, and engagement programs built around desktop intranets or email will consistently underperform. Per Social Edge Consulting, nearly a third of employees never log in to the intranet at all. A mobile-first, no-email platform that integrates communications, training on employee engagement, and recognition into a single app is the foundation everything else is built on. If you are evaluating where to start, prioritize access and learning first, measure relentlessly, and use the data to close gaps store by store. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) offers additional benchmarks and planning frameworks for HR teams building or refreshing their engagement strategy this year. --- # MangoApps Bolsters Customer Confidence with ISO 27001 Certification **Author:** Mason Hager **Published:** 2023-06-27 **Category:** press-release MangoApps achieves ISO 27001:2022 certification for robust security. This certification means that MangoApps is certified for the latest version of ISO 27001 standards.  June 27th, 2023 – We are thrilled to announce that we have received ISO 27001:2022 certification! At MangoApps, our focus has been on providing stringent security measures to mitigate the risk of […] **MangoApps achieves ISO 27001:2022 certification, the latest and most stringent version of the international information security management standard. This means every customer's data on the MangoApps platform is protected under a globally audited, continuously maintained security framework — not just a one-time badge.** **June 27th, 2023** — We are thrilled to announce that we have received ISO 27001:2022 certification. At MangoApps, our focus has been on providing stringent security measures to mitigate the risk of data breaches and unauthorized access. With countless customers residing in industries with compliance regulations, this new certification fortifies our effort to provide customers with the most secure digital workplace platform on the market. By deploying the highest level of encryption possible, alongside MFA, access controls, regular security audits, reliable AWS cloud infrastructure, and the latest automated tools, we're able to ensure that our customer data remains confidential, intact, and available only to authorized personnel. *"We are excited to achieve yet another significant milestone in our unwavering commitment to information security and compliance," says Sameer Malhotra, Associate Director of Information Security and Compliance at MangoApps. "Following the successful HITRUST certification and SOC 2 Type II attestation, we are proud to add ISO 27001 to our list of accolades. We hope this achievement solidifies our position as a trusted provider of secure and compliant solutions."* This certification stack — HITRUST, SOC 2 Type II, and now ISO 27001:2022 — represents a level of compliance momentum that few digital workplace vendors can match. For buyers evaluating cloud based productivity applications in regulated industries, that stack is a meaningful differentiator. The IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment provides independent context for how MangoApps positions within this competitive landscape. ## What is ISO 27001? ISO 27001 is an internationally recognized standard for information security management systems. It provides a comprehensive framework for establishing, implementing, maintaining, and continually improving information security practices within an organization. The certification provides a globally recognized assurance that MangoApps follows best practices and standards in information security management. This recognition instills trust and confidence in customers, assuring them that their data is protected at all times. Critically, ISO 27001 is not a static credential. It requires ongoing internal audits, risk assessments, and continual improvement cycles — meaning customers benefit from a living security program, not a one-time audit pass. ## Our Journey to ISO 27001 Certification Obtaining the ISO 27001 certification required a rigorous and meticulous approach. Our journey encompassed the following essential steps: 1. **Thorough Gap Analysis**: We conducted a comprehensive assessment of our existing security controls, specifically focusing on resilience, data security, privacy, and application security. This analysis allowed us to identify areas for improvement and align our practices with ISO 27001 requirements. 2. **Robust Risk Assessment and Treatment**: Our team performed meticulous risk assessments, considering factors such as data security, privacy, and application security. We implemented appropriate risk treatment measures, including leveraging the advanced security features and services provided by AWS, to enhance resilience and protect our valuable information assets. 3. **Streamlined Documentation and Implementation**: We developed and implemented a comprehensive set of policies, procedures, and controls to address the requirements of ISO 27001, with a focus on resilience, data security, privacy, and application security. We worked closely with AWS to optimize the implementation of security measures in our cloud environment. 4. **Empowered Workforce through Training**: We provided extensive training and awareness programs to educate our employees about the importance of resilience, data security, privacy, and application security. This training equipped our team members with the necessary knowledge to safeguard sensitive data and protect our clients' privacy within the AWS environment. 5. **Continual Improvement**: We conducted regular internal audits and assessments to monitor the effectiveness of our information security management system, with a strong emphasis on resilience, data security, privacy, and application security. Feedback from these audits allowed us to drive continuous improvement, ensuring that our practices remain aligned with industry best practices and the secure infrastructure provided by AWS. ## The Benefits of ISO 27001 Certification for Customer Success The achievement of ISO 27001 certification brings forth numerous benefits for our customers, placing their success at the forefront of our commitment: **Enhanced Data Protection and Privacy**: ISO 27001 certification ensures that your sensitive data is protected by stringent security measures, ensuring confidentiality, integrity, and availability. We prioritize your privacy, adhering to strict controls to safeguard personal and sensitive information. **Trust and Confidence**: MangoApps' ISO 27001 certification reinforces our dedication to maintaining the highest standards of resilience, data security, privacy, and application security. You can have complete confidence in the security and integrity of your data while using our solutions. **Compliance Simplified**: Our ISO 27001 certification not only ensures adherence to international standards but also simplifies your compliance requirements. By partnering with MangoApps, you can leverage our certified security framework, reducing the complexity and burden associated with meeting regulatory obligations. Acknowledgement tracking within the platform confirms which employees have read and accepted policy or procedure updates, with automated follow-up notifications for non-responders — creating a direct compliance audit trail (source: Staffbase / case_study). **Compliance as a Productivity Enabler**: Security controls and productivity are not in tension on the MangoApps platform. Unified search integrates with Google Workspace, Microsoft 365, ServiceNow, and Salesforce so compliance-related knowledge surfaces across all connected systems in a single query (source: Unily / product page). Employees using unified search save more than 30 minutes per week on average, with 82 seconds saved per task through platform search — meaning well-governed, secure data access accelerates work rather than slowing it down. **Controlled Access and Offboarding**: ISO 27001's access-control requirements are operationalized directly in MangoApps workflows. Offboarding workflows can trigger automatically on a provisioned departure date, reducing the window of unauthorized access that ISO 27001 access-control requirements are designed to close (source: Workvivo / product page). For organizations running cloud based productivity apps at scale, this kind of automated access governance is a material risk reduction. **Uninterrupted Service Availability**: Our focus on resilience and ISO 27001 certification means that you can rely on MangoApps' solutions to be available and accessible whenever you need them. Minimize disruptions and maintain productivity with our secure and reliable platform. ## Learn More About Our Compliance Efforts At MangoApps, our primary focus is your success. We will continue to invest in the development and improvement of our security practices and risk assessment, ensuring that our platform remains at the forefront of resilience, data security, and secure AWS cloud infrastructure. Experience the benefits of industry-leading information security standards and partner with MangoApps to achieve your business goals with confidence. **Other notable MangoApps certifications:** - MangoApps Achieves SOC 2 Type II Certification - MangoApps Achieves HITRUST Certification - MangoApps Achieves AWS Healthcare ISV Competency To learn more about our ISO 27001 certification and our commitment to information security, please visit our website or contact our team directly. ## What Does ISO 27001 Certification Mean for My Contract and SLA? ISO 27001 certification is an external, third-party audited standard — it is not a self-attestation. For customers, this means MangoApps' security controls have been independently verified against a globally recognized framework. In practical terms: - **Data processing agreements**: MangoApps' certified ISMS supports the documentation requirements many enterprise procurement and legal teams require before signing. - **SLA alignment**: The continual improvement and internal audit cycles required by ISO 27001 directly support uptime and incident-response commitments in customer SLAs. - **Regulatory overlap**: ISO 27001 controls map to requirements in GDPR, HIPAA, and other frameworks, reducing the compliance burden for customers operating in multiple jurisdictions. For organizations evaluating cloud based productivity applications in regulated sectors, the combination of ISO 27001, SOC 2 Type II, and HITRUST means MangoApps can satisfy security review requirements across a wide range of procurement processes without requiring customers to conduct their own audits from scratch. ## How Does MangoApps' Certification Stack Compare to Other Vendors? Most digital workplace vendors hold one or two compliance certifications. MangoApps' simultaneous maintenance of ISO 27001:2022, SOC 2 Type II, HITRUST, and AWS Healthcare ISV Competency represents a layered security posture that addresses different buyer requirements: | Certification | Primary Audience | What It Validates | |---|---|---| | ISO 27001:2022 | Global enterprise, regulated industries | Information security management system | | SOC 2 Type II | US enterprise, SaaS buyers | Security, availability, confidentiality controls over time | | HITRUST | Healthcare, life sciences | HIPAA-aligned risk management framework | | AWS Healthcare ISV Competency | Healthcare IT buyers | Cloud infrastructure security for health data | For buyers assessing productivity apps and applications for productivity in sensitive environments, this stack signals that security investment at MangoApps is ongoing and multi-framework — not a single audit event. MangoApps' recognition in the [IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment](/resources/idc-marketscape-2024) provides additional third-party validation of the platform's enterprise readiness. ## What Other Security and AI Capabilities Support This Compliance Foundation? ISO 27001 certification governs the security management system, but the platform capabilities built on top of that foundation matter equally for day-to-day compliance operations. MangoApps continues to invest in capabilities that make security controls operationally useful rather than purely administrative: - AI-assisted workflows that surface compliance knowledge without exposing unauthorized data — explored in depth in [When AI Stops Being a Tab and Becomes the Workflow](/articles/when-ai-stops-being-a-tab-and-becomes-the-workflow). - Native workforce management integrations that connect scheduling, communications, and access controls in a single governed environment, detailed in [MangoApps Integrates Native Workforce Management and Next-Gen Generative AI](/articles/native-workforce-management-and-next-gen-generative-ai). - Knowledge management capabilities recognized by industry analysts, as covered in [MangoApps Named to KMWorld 100 Companies That Matter in Knowledge Management](/articles/mangoapps-kmworld-100-2026). For organizations that need both security assurance and productive application capabilities in a single platform, MangoApps' certification momentum and product roadmap are designed to advance both goals simultaneously. --- # Internal Comms Tools That Save Money **Author:** Mason Hager **Published:** 2023-06-22 **Category:** employee-experience Internal comms folks… this article is for you!  At MangoApps, we’ve seen many internal communicators struggle to effectively deploy communications due to the lack of proper tools.  You may have already communicated these limitations to top brass only to be told that the proper tools “don’t fit within our budget” or “this is not a […] # Internal Comms Tools That Save Money According to IDC research, employees spend 2.5 hours per day searching for information they cannot find in one place. For a workforce of 1,000 employees over 250 workdays, that is 625,000 hours annually — roughly $21.9 million at $35 fully loaded hourly cost — before a single platform budget line has been touched. A mobile-first [employee app](/solutions/employee-app) typically runs $4–8 per user per month. The ROI case is positive in year one for most mid-size organizations without optimistic assumptions. Three platform types define the internal communications market, and they solve different problems at different price points: - **Mobile-first employee apps** ($4–8/user/month): frontline access without corporate email or device provisioning - **AI-native platforms** (consolidation tier): automated content targeting that replaces manual segmentation maintenance - **Intranet consolidation systems** ($8–15/user/month): replace 5–10 fragmented tools with one searchable platform What follows is how to evaluate among them, the customer outcomes that prove which model works, and the three metrics that confirm whether your current system is functioning as an internal communications tool or as an archive employees have learned to ignore. ## The access gap that sets the adoption ceiling According to Social Edge Consulting, 91% of organizations operate an intranet. SWOOP Analytics found the average employee spends six minutes per day using one. Thirteen percent use it daily. Nearly a third never log in at all. These numbers are not a content problem. Corporate intranets were designed for employees at a desk, on a company-issued device, with a corporate email address. Emergence Capital estimates that 80% of the global workforce is not that. Frontline workers in healthcare, retail, logistics, and manufacturing receive communications by catching a manager in the hallway, reading a whiteboard, or missing the message entirely. An [employee communications platform](/solutions/employee-communications) that cannot reach deskless workers is not an incomplete solution — it is solving the wrong problem. Improving content quality when the distribution model excludes the majority of the workforce is optimizing a message that never gets delivered. ## What the access model change actually produces OU Health deployed a mobile-first employee app to clinical staff — a workforce that had no access to the previous intranet's corporate email login requirement. Within the first few months, the organization reached 87% workforce engagement. PetSmart achieved 4x more engagement than the industry standard after deploying a branded employee app to retail associates on personal devices. TeamHealth, one of the largest physician staffing companies in the US, consolidated more than 200 disconnected systems — email lists, shared drives, messaging applications, printed bulletin boards — into a single platform. In each case, the outcome followed the same structural change: the platform reached employees where they already were, without requiring behavior changes to accommodate a tool they were excluded from using. No amount of content strategy improvement reverses a distribution model that cannot reach the people the communication was written for. ## Three platform types and their actual cost profiles **Mobile-first employee apps** solve the access problem first. The three binary evaluation questions: can employees enroll without a corporate email address? Does the platform work on personal devices? Do push notifications arrive in real time? A no on any of these is a structural exclusion — a portion of the workforce cannot use the platform regardless of its other capabilities. For organizations with any meaningful frontline presence, these questions belong in the first round of vendor conversations. Cost profile: $4–8/user/month. The relevant comparison for a 2,000-person workforce where frontline employees currently use no tool is not "cost of the new platform" versus "cost of the current platform." It is cost of the new platform versus cost of the turnover, safety incidents, and operational errors that result from failing to reach 70% of the workforce. **AI-native targeting** replaces the manual segmentation work that breaks down at scale. Legacy platforms required distribution lists maintained by hand — lists that drift out of date with every hire, transfer, and promotion. Modern platforms use role, location, department, and behavioral signals to surface relevant content automatically. Engagement gains are concentrated in organizations using consistent, targeted communication — not broadcast messages that reach some employees sometimes. AI-native targeting is the infrastructure that makes targeted communication operationally feasible without a dedicated segment maintenance function. **Consolidation platforms** are evaluated on a different question: not "does this platform have the features we need?" but "how many platforms we currently pay for does this replace?" Organizations maintaining separate email lists, a SharePoint intranet, a chat tool, a scheduling system, and printed bulletin boards are paying for five communication channels while achieving fragmented reach. Email license displacement for frontline workers who do not use corporate email typically starts at $4 per user per month — $96,000 annually for 2,000 employees — before any productivity gains are counted. ## The security objection IT will raise — and how to answer it Every communications platform evaluation eventually surfaces the BYOD concern: personal devices, data handling, access control. The productive response is not to dismiss it but to arrive at the first IT conversation with security documentation already in hand. Enterprise-grade internal communications platforms support SAML 2.0 single sign-on and meet standard enterprise compliance requirements. That converts the objection from a risk discussion to a configuration discussion. In healthcare, financial services, and settings with compliance obligations, the requirements go further: role-based permissions, documented audit trails, verifiable message delivery. Platforms that treat compliance documentation as a configuration afterthought create audit findings rather than dashboard wins. For healthcare organizations, platforms carrying HITRUST certification alongside SOC 2 Type II and ISO 27001 have completed pre-certification work that would otherwise sit in the IT team's queue. That is a material procurement differentiator — it moves the security conversation from evaluation blocker to setup task. ## The three metrics that tell you whether communications are working Most organizations track outputs: newsletters sent, all-hands attendance, open rates. These describe production volume. The metrics that reveal whether communications are functioning are harder to surface but more useful. **Segment-level read rates, not aggregate.** A 40% overall open rate might mean near-complete reach at headquarters and near-zero reach among overnight warehouse workers. Aggregate numbers hide which groups are being missed. Segment-level data names where the gap is, which is the only information that allows the fix to be structural rather than cosmetic. **Search query failure data.** When employees search for things that were already communicated, it means the communication either did not reach them, did not stick, or cannot be located when needed. IDC research puts 2.5 hours per day as the time employees spend searching for information they need — that time is recoverable — and search failure data is the direct measurement of where it is being lost. It names what needs better distribution and who is not receiving it. **Acknowledgment rates on critical communications.** Likes and reactions measure passive exposure. When employees are asked to confirm receipt of a safety protocol, policy update, or compliance document, response rate measures behavioral engagement — the distinction that matters in regulated environments where proving delivery is a requirement, not a preference. If the current platform cannot surface segment-level read rates and search failure data without a manual export, the feedback loop that drives improvement does not exist. ## The budget case in three numbers **The search tax.** IDC's 2.5 hours per employee per day applied to 1,000 employees over 250 workdays produces 625,000 hours annually — $21.9 million at a $35 fully loaded hourly cost. No platform will recover all of it. But the number establishes the financial scale of the problem before any platform evaluation begins. **The turnover cost.** Replacing a frontline employee costs $4,400 to $15,000 per worker. Communication-driven retention is cost avoidance, not an engagement program. An intranet that 70% of frontline workers cannot access is a turnover risk. For a 500-person frontline workforce running 20% annual attrition, a 3% retention improvement from reaching employees who were previously excluded closes most of the annual platform licensing cost before productivity gains are counted. **The SharePoint comparison.** A 1,000-user SharePoint deployment carries an estimated first-year total cost of $130,000–$426,000 when implementation, customization, and ongoing administration are included, per the Awesome Technologies Inc. 2025 cost model. Most organizations then layer additional tools on top to compensate for SharePoint's frontline access gaps — each addition increasing total cost and fragmentation simultaneously. A purpose-built alternative is typically a consolidation argument with a lower total first-year cost, not an incremental expense on top of existing spend. ## The evaluation order that produces the right answer Standard platform evaluations start with features and end with price. The sequence that produces better outcomes inverts that: 1. **Access first.** Who cannot be reached by the current infrastructure? If the answer is "most of our frontline workforce," the access model problem precedes every feature conversation. 2. **Consolidation scope.** What is currently paid for that a new platform could replace? This sets the real cost comparison — total first-year cost including tool elimination, not a line-item licensing comparison against one vendor. 3. **Measurement capability.** Can the platform surface segment-level read rates, search failure data, and acknowledgment rates natively? Without these, the feedback loop that drives ongoing improvement does not exist. 4. **Features last.** Once access, consolidation, and measurement are addressed, feature differences between shortlisted platforms are refinements, not decision points. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) evaluates platforms using consistent criteria across frontline accessibility, search quality, and administrative overhead — the same framework enterprise buyers apply in formal procurement, without vendor-supplied benchmarks. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how operations and HR leaders are setting digital adoption benchmarks that predict service quality outcomes before problems surface in dashboards. The first step in any of this is measuring what the current system is costing to keep — in hours lost, turnover driven, and communications that never reached the people they were written for. --- # Leverage Generative AI For Business Security: Building A Reliable Employee Hub **Author:** Luke Walton **Published:** 2023-06-09 **Category:** enterprise-ai In today’s increasingly digital world, the spread of misinformation can pose a substantial business risk. This is especially true for organizations in industries where strict compliance and data security standards are required.  Companies are often the target of calculated disinformation campaigns, deep fake attacks (where anonymous people pose as high-ranking leaders within the company), email […] # Leverage Generative AI For Business Security: Building A Reliable Employee Hub The phishing email that compromises credentials this quarter probably won't look like spam. It will match the tone of your leadership communications, reference a real internal initiative, and carry enough contextual accuracy that a cautious employee has reason to click. Generative AI has made this level of personalization cheap and scalable—attackers can now produce thousands of targeted, plausible communications for a fraction of what it cost two years ago, and the tools that generate them are widely accessible. The standard response is more training. That response is structurally wrong. Phishing awareness training asks every employee to make the right call every time against increasingly convincing attacks—a bet that fails at the margin that matters. A governed, [secure intranet](/solutions/modern-intranet) takes a different approach: it reduces the number of judgment calls employees have to make correctly by moving authoritative communication into a channel attackers cannot easily reach. That is a specific claim about communication infrastructure as a security control. The rest of this article makes the case. ## The attack surface is the communication channel, not the employee's judgment Per Social Edge Consulting, 91% of organizations operate an intranet, but only 13% of employees use it daily. Nearly a third never log in at all. That gap is not a training gap. It is a channel gap: employees default to email and messaging apps because that is where work happens for them—and because the intranet has historically delivered undifferentiated, often stale content that was not worth checking regularly. When employees default to ungoverned channels, those channels become the attack surface. Attackers do not need to crack authentication infrastructure if they can reach employees through the same inbox used for vendor invoices and HR announcements. A credential-harvesting link embedded in a convincing internal announcement is enough. Per IDC, employees spend 2.5 hours per day searching for information they cannot find in one place. Per SWOOP Analytics, the average employee spends just six minutes daily using intranet tools. Those two numbers together describe the structural exposure: information that should live in a governed hub is scattered across email threads and shared drives, and employees spend substantial time searching in ungoverned environments where attackers operate freely. Adding training layers to this architecture does not change the architecture. It adds a behavioral requirement on top of a structural problem. ## What "secure intranet" means as a security category "Secure intranet" is a distinct product category, though many platforms use the phrase loosely. The meaningful definition has three components that work together—and the absence of any one of them breaks the security argument. **A single authoritative channel.** A secure intranet functions as a security control only when it becomes the de facto source for work-related communication—not one of six channels employees check. This requires genuine access for the full workforce and content governance rigorous enough that employees trust what they find there. A platform that covers desk workers but not deskless workers is covering the employees least susceptible to the communication spoofing problem. **No-email, device-agnostic authentication.** Per Emergence Capital, 80% of the global workforce is deskless. These employees—field technicians, healthcare aides, warehouse workers, retail associates—often lack corporate email addresses and managed devices. A platform that requires corporate email to authenticate has already structurally excluded them. The security implication is concrete: a frontline employee who authenticates to a hub via personal device without a corporate email address has no corporate inbox for attackers to spoof. The email attack surface for that segment of the workforce disappears. This is not a convenience feature—it is a real reduction in the number of employees reachable through the most common attack vector. **AI-governed content freshness.** Per Social Edge Consulting, 63% of employees rate intranet content as not current and relevant. That is a trust problem with direct security consequences: when employees open an intranet and consistently find outdated policies and expired announcements, they stop treating it as authoritative. They revert to email—and become more susceptible to external communications that appear authoritative precisely because they look more current than the stale hub. AI governance workflows close this loop. Automated review cycles flag content that has not been verified within defined periods, route it to the appropriate owner, and surface recently updated material prominently. Employees who experience the hub as consistently accurate develop the habit of cross-checking external communications against what the hub says. That behavioral pattern is more durable than any training program because the platform reinforces it every time—not just during quarterly security awareness sessions. ## Where generative AI changes the defensive calculus Generative AI cuts both ways. Attackers use it to produce convincing, personalized communications at scale. Defensively applied inside a governed hub, it changes the security calculus in three specific areas. **Anomaly detection in communication patterns.** AI models trained on an organization's communication patterns can flag messages that deviate from established sender profiles, tone, or formatting before an employee interacts with them. This differs fundamentally from keyword-based spam filters, which attackers have learned to circumvent. When the hub sets the standard for what legitimate internal communication looks like, deviations stand out structurally rather than requiring individual employees to recognize them under time pressure. **Intelligent targeting that eliminates noise.** Legacy platforms required manual segmentation rules that drifted out of date with every hire, transfer, or promotion. AI-assisted targeting surfaces relevant content based on current role, location, and behavioral signals without manual intervention. Fewer irrelevant communications create less noise for attackers to hide in. Employees who trust that hub content applies to them use the hub more—which is the precondition for every security benefit the platform provides. **Verifiable communication records.** When communications flow through a governed hub, every message carries a verified sender, a timestamp, and a retrievable record. In regulated industries—healthcare, financial services, government contracting—auditors will ask for exactly this documentation, and email threads cannot provide it in the form compliance requires. The audit trail is a security asset and a compliance asset simultaneously. ## Adoption is the prerequisite, not the outcome None of these capabilities work if employees do not use the platform. This is where most secure intranet deployments fail: the platform exists, the governance workflows are configured, the AI capabilities are live—and 87% of employees still have not logged in this week. The precondition for any security benefit is high adoption across the full workforce, including frontline and deskless workers. Enterprise deployments that remove access friction—no VPN required, no corporate email required, simple SSO or mobile-number authentication—demonstrate that 90% frontline adoption within the first six months is achievable. At that adoption level, the volume of communication occurring outside the governed hub drops sharply. With it drops the opportunity for phishing and impersonation to reach employees through ungoverned channels. The security benefit compounds over time: as the hub becomes the expected channel for authoritative communication, messages arriving outside it become structurally anomalous—easier for employees to identify as suspicious without any additional training. [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent evaluation criteria across security, governance, and adoption dimensions—a structured starting point before any vendor comparison. ## Three criteria that separate platforms on security posture The question organizations face when replacing or upgrading communication infrastructure is not whether to pursue a secure intranet—the case for that is clear. The question is which platform capabilities are genuinely load-bearing for security outcomes versus which are marketing features that do not change the attack surface. **Frontline access without email provisioning.** Can a field technician authenticate and reach department communications from a personal device in under 60 seconds, without an IT ticket? Platforms that require a corporate email address or managed device answer with a no. For a workforce where a significant share are off-site or between locations at any given time, this is the gap that determines whether the platform closes the attack surface or relocates it. **Content governance automation.** The platform should identify stale content and route it to owners for review or retirement without manual audits. Configurable review cycles matter here: policies have different freshness requirements than announcements, which differ from department pages. A governance workflow that treats all content identically will fail where security risk actually concentrates—in the outdated policy documents employees stop consulting and then cannot distinguish from external spoofs. **Verifiable audit trails.** Every communication and content change should be timestamped and retrievable. Healthcare organizations under HIPAA and financial services firms subject to SEC recordkeeping requirements need this documentation as a compliance prerequisite. Platforms without verifiable audit trails are not viable for regulated industries regardless of their AI positioning. For organizations evaluating whether an existing SharePoint deployment can meet these requirements, the [frontline intranet requirements checklist](/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) covers the specific gaps that most SharePoint Server deployments leave open—gaps that compound the security exposure rather than closing it. ## The structural advantage builds over time Security leaders who have worked through this problem describe the same sequence: training programs, added MFA, email filtering—and phishing attempts kept reaching employees through the channels those controls could not cover. The structural fix was reducing the number of channels attackers could use to reach employees, not just hardening individual channels. A governed secure intranet with genuine frontline adoption changes the environment training operates in. Employees who default to a hub they trust—because it is accessible from any device, because the content is current, because it covers the full workforce—are making fewer consequential judgment calls under pressure. They are more likely to recognize an out-of-band communication as anomalous because the in-band norm is consistent and reliable. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers current adoption benchmarks and where organizations are investing to close the gap between where employees receive communication today and where they need to receive it for governance to work. Generative AI has raised the sophistication of the threats employees face in daily work. It has also raised the capability of the platforms available to defend against those threats. The organizations building structural advantage are the ones that treated communication infrastructure as a security decision before the threat environment made that decision urgent—and measured the outcome not in training completion rates but in the share of communication flowing through a channel attackers cannot easily reach. --- # 20 Ways To Promote Your Employee SuperApp Launch **Author:** Mason Hager **Published:** 2023-06-01 **Category:** employee-app Promoting the launch of your Employee SuperApp is critical if your organization wants to create awareness, drive adoption, and maximize the value out of the platform. If your employees don’t know about it (or the value it can provide) then they aren’t likely to use it. A proper Employee SuperApp with high levels of adoption […] Promoting the launch of your Employee SuperApp is critical if your organization wants to create awareness, drive adoption, and maximize the value out of the platform. If your employees don’t know about it (or the value it can provide) then they aren’t likely to use it. A proper Employee SuperApp with high levels of adoption can improve operational efficiency, drive collaboration and communication, boost company culture and engagement, and so much more. In this article, we’re sharing 20 ways you can promote the launch of your Employee SuperApp to ensure that your organization receives high levels of adoption. #1: Have A C-Level Executive Announce The Employee SuperApp Make sure the announcement of the new Employee SuperApp comes from someone of authority at your company (C-Level)…explain exactly why you are doing this and what’s in it for the employee (why should the employee care / get excited about it?) #2: Provide Use Cases For How Colleagues Can Benefit From Employee SuperApp Offer bite-sized ideas and use cases for how the Employee SuperApp might benefit your colleagues.  Example: You can stay up to date with the latest news and announcements. You have a central place you can go to access all the links you need. You can ditch the flooded email inbox and have targeted comms that are relevant to you. You can easily search for info or files you need without having to remember exact file names. #3: Send Communications Before & After Launch Send a series of communications to your employees before and after the Employee SuperApp launch (emails, posters, postcards, brochures, digital signage, etc.) Example: #4: Mention Employee SuperApp In Town Hall / Large Company Meeting Bring up the Employee SuperApp in a town hall or large company meeting. “Make sure you’re aware of the new platform that’s coming and think about how you want to contribute.” #5: Create A User Guide/Help Manual   Create a user guide, manual, or LMS course that highlights the platform’s benefits and how to use it. #6: Lights, Camera, Action! Host a photo shoot at the office where employees can spruce up and take photos for their new employee profiles. Whitepaper – Employee SuperApps Want to eliminate information chaos and provide your workers with a unified employee experience? In this whitepaper, we give a detailed breakdown of why Employee SuperApps are becoming increasingly popular among frontline organizations. learn more #7: Host A Trivia Contest With Prizes Host an Employee SuperApp trivia contest with cash prizes, vacation time, and a lunch party or night out for the winning office location. #8: Conduct A Scavenger Hunt Conduct a scavenger hunt (with prizes) where the answers are hidden throughout the Employee SuperApp. #9: Throw An Employee SuperApp Launch Party! Throw an Employee SuperApp launch party (food, drinks, desserts)! Be ready to answer any questions and help employees where needed. #10: Host A Webinar/Virtual Company Meeting Host a webinar. Talk about why the new Employee SuperApp is important, give a real-time tour of the platform, and open it up to Q&A. #11: Hand Out ‘Welcome Kits’ Hand out Employee SuperApp ‘welcome-kits.’ This could contain anything from training materials to goodies and snacks to branded swag. #12: Create Infographics Create infographics that visually explain the Employee SuperApp’s key features and benefits. #13: Take Advantage Of Your Ambassadors Leverage your Employee SuperApp ambassadors. Who was involved in getting the Employee SuperApp launched? Let them become advocates for the Employee SuperApp to their colleagues and peers. #14: Create A Video Trailer & Share It On Social Media Create a video trailer showcasing the Employee SuperApp’s features and benefits. PetSmart is a great example of how you can create a video trailer and share it to generate excitement. #15: Promote Mobile App Download Go big on promoting the mobile app download so you can reach them later via app notifications. #16: Incorporate Employee SuperApp Into Onboarding Process Make it part of your onboarding process so new employees get integrated and network effect remains high. #17: Link To SuperApp From Website Add links to your Employee SuperApp on your corporate website so it is easy for employees to find it in the early days including via Google search. #18: Get Leadership Buy-In Get leadership buy-in. Have leadership regularly engage with the platform and involved in webinars/trainings in the early stages. People are more likely to listen to top executives so it’s important that you take advantage of your company’s leaders and have them direct people to the new intranet. Example: To maintain consistent intranet engagement, symplr had its CEO sent out important news via a snippet in an email, and then linked to the intranet for the full story. This was a particularly helpful way to distribute information and keep people regularly visiting the intranet. Eventually over time, symplr was able to migrate away from that workflow and just start hosting important company news/information directly on the intranet. learn more #19: Create Surveys To Collect Feedback Create Surveys to collect feedback information that informs the user taking the survey and provides data to improve the Employee SuperApp, such as resolving pain points and pushing existing strengths. These strengths become success stories. #20: Offer Incentives To Download Employee SuperApp Offer incentives to employees who download and use the Employee SuperApp(such as a $5 Starbucks gift card, entering into a PTO raffle, etc.) Want To Learn More About Employee SuperApps? If you want to learn more about how an Employee SuperApp can benefit your organization, check out our Employee SuperApp Blog Series! View the entirety of our Employee SuperApp blog series below: Part 1 – What Is An Employee SuperApp? Part 2 – 10 Benefits Of An Employee SuperApp Part 3 – Why Your Frontline Organization Needs an Employee SuperApp Part 4 – Why An Employee SuperApp Is Key For Employee Enablement Part 5 – How An Employee SuperApp Benefits The Digital Employee Experience MangoApps – The Employee SuperApp MangoApps is the ultimate Employee SuperApp for organizations with a frontline workforce. With MangoApps, you’re able to give 100% of your workforce all the tools they need in one employee app to increase productivity, improve retention, and boost employee engagement. MangoApps is customizable and offers a wide range of unique functionalities aimed at solving any business need. To learn more about how MangoApps can help your organization, book a demo or schedule a call with our team today! Schedule a call --- # How To Improve Frontline Employee Experience **Author:** Mason Hager **Published:** 2023-05-15 **Category:** employee-app Your employees are drowning in the constant introduction of new systems to learn, master, and use on a daily basis. Frontline workers, especially, can’t be reasonably expected to access all the various systems required to access company information. It is not only outside their field of expertise, but also is usually exceptionally difficult to do via […] # How To Improve Frontline Employee Experience Consider the morning of a distribution center shift lead at a mid-size retailer. She clocks in at 5:45 a.m. She needs to check whether a team member's shift-swap request has been approved, find the updated SOP for the returns process going live this week, and flag a safety concern before the floor opens. Three apps on the shared work tablet could theoretically help — if the VPN provisioned for the office team were accessible from a warehouse floor. It isn't. The tablet stays in the drawer. She handles everything through a group text thread. This is not a story about employee disengagement. It is a story about access. Per Emergence Capital, 80% of the global workforce is deskless. The enterprise software stack — the intranet, the HR portal, the document management system — was designed for the other 20%: workers with a desk, a corporate email address, and a device on the company network. Frontline employees in retail, healthcare, logistics, and manufacturing have been excluded at the infrastructure level, not the intention level. The path to a better frontline employee experience does not begin with another communication initiative or a new training program. It begins with removing the access barrier that made the original infrastructure useless for most of the workforce to begin with. ## The access gap most organizations don't see in their data Per Social Edge Consulting, 91% of organizations run an intranet. Nearly a third of employees never log in to it, and only 13% use it daily. These statistics are frequently cited as evidence of low engagement — but they measure something more fundamental: the mismatch between who the intranet was designed for and who actually shows up to work. Per SWOOP Analytics, the average employee spends six minutes per day using intranet tools. For frontline workers who cannot access the intranet without a VPN or a corporate email address, the actual number is lower — because the access barrier turns a low-adoption problem into a total exclusion problem. Six minutes is not disengagement. Six minutes is what happens when the friction is high enough to make a tool effectively unusable for most of the people who need it. Per IDC, employees spend an average of 2.5 hours per day searching for information. For deskless workers who rely on shift supervisors to relay information they cannot reach directly, that search time compounds with access time. The information exists in the system. The worker cannot get to it. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), employee engagement correlates directly with whether workers feel the organization is paying attention to their experience. Infrastructure that reaches office workers but structurally excludes frontline employees communicates something implicit — and it shows up in engagement scores whether or not the organization is measuring it that way. ## Why disconnection is a balance-sheet problem, not just an HR concern Poor frontline digital experience has a dollar figure attached to it. Replacing a single frontline employee costs between $4,400 and $15,000 when accounting for recruiting, onboarding, and the productivity gap while a new hire finds their footing, per MangoApps product research. At a 1,000-person frontline workforce running 30% annual turnover, the replacement bill runs between $1.3 million and $4.5 million per year — before accounting for what institutional knowledge leaves when an experienced worker does. The tool-switching overhead compounds the math. Employees who navigate 13 or more applications to complete their daily work lose more than four hours per week to friction alone. Across a 500-person frontline team, that is 100,000 hours of coordination overhead per year — not a morale problem, a resource allocation problem with a calculable cost. Digital disconnection also accelerates turnover. Workers who feel unreachable — who cannot access recognition programs, feedback channels, or training resources that their desk-based colleagues use routinely — disengage faster. The six-minute daily platform engagement SWOOP Analytics measures is behavioral evidence of that gap, not its cause. Organizations that address the access barrier close the gap. Organizations that treat it as an engagement problem tend to cycle through communication campaigns that reach the same 20% of the workforce while the other 80% stays invisible in the data. ## What removing the access barrier actually requires The fix is not a better intranet. It is an [employee app](/solutions/employee-app) that does not require a corporate email address or VPN to function. This distinction matters more than it sounds. Many enterprise platforms describe themselves as mobile-friendly. Fewer will clarify whether a warehouse associate can log in from a personal device on day one, without IT provisioning an email account. The operational question is not "does it have an app?" — it is "can a frontline worker who has never had a company email authenticate and reach their schedule, training, and HR self-service in under 60 seconds?" An app built for frontline access changes the practical reality for workers in low-connectivity environments, on personal devices, and without a desk to return to. Offline access ensures workers on warehouse floors, construction sites, and retail floors are not locked out when connectivity drops. Unified search puts every policy document, training resource, announcement, and HR form behind a single bar on mobile — recovering a meaningful portion of the 2.5 hours IDC attributes to daily information search. The outcomes from organizations that have made this transition are documented. OU Health achieved 87% workforce engagement within months of launching a branded employee app. PetSmart reached four times the industry-standard engagement rate for frontline workforces after deployment. TeamHealth consolidated more than 200 disparate systems into a single mobile dashboard, demonstrating that the consolidation works even at large enterprise scale, per MangoApps case study data. The pattern across these organizations is consistent: removing the access barrier drives adoption faster than any communication or training initiative aimed at the same outcome. ## Personalization that frontline workers notice Access solves the first problem. Relevance determines whether your workers stay engaged after day one. Generic broadcast communications — company-wide announcements, all-hands emails — perform poorly with frontline workers, not because frontline workers are disengaged, but because the content was not written for them. A warehouse associate in Phoenix has different daily information needs than a healthcare aide in a rural clinic. A broadcast that addresses neither specifically is typically ignored by both. Role- and location-based content delivery changes this dynamic. Workers see announcements, training updates, and policy changes that apply to their specific function and location — not the full communications feed designed for a corporate audience. AI-assisted content surfacing extends this further, matching content to workforce segment without requiring the communications team to build a separate channel for every role group. Real-time translation for multilingual workforces closes the final gap. Frontline workforces in retail, healthcare, and logistics are frequently multilingual. A frontline employee experience that reaches workers in the language they use on the job removes a friction point that rarely appears in engagement surveys but consistently appears in platform adoption data. Training resources embedded in the mobile experience — accessible during a shift, on the same device used for scheduling and communications — reach workers who cannot pause to log into a desktop learning portal. This is the design distinction that separates digital experience programs that get used from those that get launched with a communications push and quietly abandoned six months later. ## What implementation looks like for operations teams The access barrier problem sounds like an IT project. In practice, removing it requires less IT involvement than sustaining a traditional intranet with VPN dependencies and corporate email provisioning for every new hire. An app that authenticates via mobile number or simple SSO shortens frontline onboarding from days to hours. Workers can be operational on day one, without waiting for IT to provision an email account. [Workforce management](/solutions/workforce-management) integration means shift schedules, time-off requests, and attendance records live in the same app as communications, training, and HR self-service — closing the relay gap that forces workers to go through supervisors for basic operational data. The IT surface area shrinks as well. A single unified app with centralized authentication is easier to audit, secure, and maintain than a stack of 13 point solutions with separate credential sets and separate update cycles. For organizations subject to compliance requirements in healthcare, financial services, or government contracting, this consolidation has direct implications for audit readiness and data governance. What looks like an HR investment at the start of the project tends to show up as an IT simplification dividend by the end of the first year. ## How to tell whether a frontline app closes the gap or just moves it The question is not whether to invest in frontline digital experience. The replacement cost math and productivity overhead have already answered that. The question is whether the platform removes the access barrier — no corporate email required, no VPN, no shared device, no supervisor as information intermediary — or replicates the same structural exclusion in a slightly newer format. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarking for distinguishing platforms that genuinely close the frontline access gap from those that extend the intranet metaphor to a mobile wrapper. Frontline workers who can reach what they need, on the device they already carry, without an IT ticket to get started — are not a different category of employee to manage. They are the same workforce, finally reached by the infrastructure that was already there. --- # Empowering Frontline Employees Starts With Mobile Enablement **Author:** Justina Kolb **Published:** 2023-05-08 **Category:** employee-app Creating a positive employee experience that empowers frontline employees is a top priority in today’s workplace. In doing so, your organization can reduce turnover, improve efficiency, build a more engaged and satisfied workforce, and improve customer experiences. One vital aspect of a positive employee experience is employee enablement. Beyond employee engagement, enablement is the provision […] # Empowering Frontline Employees Starts With Mobile Enablement Rosa gets to her hospital floor at 6:30 a.m. Before her first patient interaction, she needs to confirm whether the new discharge protocol applies to her ward, check which colleague is covering a task handoff, and locate the training module that went out to the department last week. Her hospital uses four separate systems for these three items. She has mobile access to two of them. One requires a shared desktop at the nurses' station. The third is somewhere in an email chain addressed to a distribution list she was never added to. By 7:00 a.m., Rosa has improvised twice and is already starting behind. This is not a story about a disengaged nurse. Rosa cares deeply about her patients and her unit. It is a story about infrastructure — the invisible layer that either delivers information to the people who need it or fails to. Per IDC, employees lose an average of 2.5 hours each day searching for information across disconnected systems. In healthcare and other deskless industries, those hours compete directly with patient-facing time. The erosion is rarely dramatic. It accumulates across shifts, quarter after quarter, until staff stop looking for information and start working around it. The underlying cause is structural. Most enterprise technology infrastructure was designed for office workers with corporate laptops, VPN access, and assigned email addresses. Per Emergence Capital, 80% of the global workforce is deskless. The tools built for the other 20% were never designed to reach Rosa on a hospital floor at 6:30 in the morning. ## Why frontline workers cannot use the tools their organization already has Per Social Edge Consulting, 91% of organizations operate an intranet. Nearly a third of employees never log in. Only 13% use one daily. Per SWOOP Analytics, the average employee spends six minutes a day using intranet tools — not out of indifference, but because the systems are slow, require logins that frontline staff are never provisioned for, and deliver content through navigation paths that do not survive a shift transition. The login problem alone disqualifies most enterprise tools for frontline use. A nurse without a corporate email address cannot receive the policy update sent through the enterprise communications platform. A warehouse supervisor without VPN provisioning cannot pull the compliance document from the document management folder. A hotel maintenance technician working evenings cannot access the HR self-service portal that requires a desktop browser and domain credentials. The channel exists. The delivery does not reach them. This is not an engagement problem in the traditional sense. It is an access problem that produces disengagement as its downstream effect. Organizations that invest in employee communications, recognition programs, and training initiatives while leaving the delivery infrastructure disconnected are trying to run water through pipes that have not been connected to the main. The signal shows up in survey data, but the root cause is invisible to the survey. Employees who report that managers do not communicate clearly are often responding to a communication delivery failure — the policy update that never reached the floor, the recognition post that sat in an app 60% of the workforce has never opened. The intent was there. The infrastructure was not. ## What mobile enablement actually means Mobile enablement is not the same as having a mobile app. Organizations that publish a portal link optimized for mobile browsers and declare themselves mobile-first have moved the problem, not solved it. Genuine mobile enablement for frontline workers requires a specific set of conditions: staff can access shifts, forms, training, HR self-service, and urgent communications from a personal device without a corporate email address, a VPN, or a shared workstation. Push notifications reach them regardless of shift schedule. Content is delivered in their preferred language. In environments with limited or intermittent connectivity — manufacturing floors, field-service locations, rural healthcare facilities — offline document access is available for safety protocols and standard operating procedures. Each of these is a structural requirement, not a convenience feature. Meeting all of them is what separates a platform that reaches the 80% of deskless workers from one that reaches the desk-based 20%. The "no corporate email required" condition is the one most enterprise deployments fail on. It seems minor until you consider that the segments with the highest turnover — hourly retail workers, contingent healthcare staff, seasonal logistics employees — are also the least likely to have been provisioned with corporate credentials. Reaching them through standard enterprise channels requires a workaround at every step. The workaround is usually a printed flyer on the breakroom wall. ## What changes when the access gap closes When OU Health deployed a branded employee app to its frontline workforce, the organization achieved 87% workforce engagement within the first few months of launch. That outcome reflects something specific: the access barrier had been removed, and programs that were already in place — recognition, training, policy communication — finally reached the staff they were designed for. The programs had not changed. The delivery had. The retention case follows directly. Replacing a frontline employee costs between $4,400 and $15,000, depending on role and sector. Organizations that treat mobile enablement as a soft employee experience initiative are underweighting the financial exposure on the other side. A consistent reduction in frontline turnover of even three to four percentage points per year represents a measurable budget impact before it represents a culture signal. The operational outcomes are equally concrete. When TeamHealth consolidated more than 200 disparate systems into a single mobile dashboard for its frontline clinical staff, the primary benefit was not that employees reported higher satisfaction scores. It was that the coordination overhead — time lost to system-switching, login failures, and duplicate data entry — came off the clock. That time went back into patient-facing activity. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents this pattern across frontline-heavy organizations: access is the variable that separates high-performing engagement programs from identical programs that underperform. The differentiator is delivery, not intent. The same dynamic plays out in manufacturing and retail. In manufacturing, the ability to push updated safety protocols and compliance training to personal devices — without requiring staff to visit a kiosk or wait for the next scheduled session — compresses the update cycle from weeks to hours and reduces the liability exposure that comes with outdated training records. In retail, where breakroom posters remain the primary communication mechanism for scheduling and policy updates at many chains, a mobile-first channel is the difference between staff who know current procedures and staff who find out when something goes wrong. ## The consolidation argument for tool-heavy organizations Organizations that attempt to close the frontline access gap by layering additional mobile applications onto their existing tool sprawl typically move the problem laterally. A standalone recognition app, a separate training module, and a third-party shift management tool each require distinct logins, separate notification configurations, and separate onboarding cycles for every new hire. The consolidation argument is not about organizational tidiness. It is about cognitive load. Per IDC, those 2.5 daily hours lost to information searching are not concentrated in a single system — they are distributed across the entire tool surface. Reducing the tool surface is the only intervention that reduces the total drag. An [employee app](/solutions/employee-app) that consolidates communications, training, HR self-service, shift scheduling, and knowledge access into a single mobile experience removes the switching cost. Frontline staff do not need to remember which system holds which category of information. One login. One notification surface. One place to check before the shift starts and after it ends. This matters most in high-turnover, high-onboarding-volume environments where new staff absorb institutional friction on day one and carry it forward. Every hour a new healthcare worker, retail associate, or manufacturing technician spends navigating tool sprawl is an hour not spent learning the role. Removing the friction at the point of access is among the fastest levers for improving time-to-productivity for every new hire. ## Three questions frontline leaders typically ask next **How long before adoption reaches meaningful levels?** When friction was the barrier — not willingness — adoption is faster than most leaders expect. Organizations providing a branded, role-specific mobile experience typically see adoption rates cross 70–80% within the first quarter. Healthcare and retail see the fastest ramp because frontline staff are already habituated to smartphone use in their personal lives. The gap between personal-device fluency and work-app adoption is almost entirely explained by access friction, not technology skepticism. **What about staff who do not own smartphones or prefer not to use personal devices?** Mature frontline platforms support kiosk mode: shared-device access, QR-code login, and PIN-based sessions that require no personal device ownership. The platform's obligation is to reach everyone. [Research on learning and development strategy](/articles/learning-and-development-strategy-embedded-in-daily-work) consistently shows that adoption floors correlate with access barriers — when the barriers are removed, participation follows. Kiosk access closes the remaining gap for staff who cannot or will not use personal devices. **How do we measure whether mobile enablement is actually working?** The leading indicators are operational, not cultural: policy-read confirmation rates by shift and floor, time-to-acknowledgment for compliance updates, participation rates in feedback channels broken down by role and location. These metrics are available within weeks of deployment and move faster than annual engagement surveys. A reduction in HR escalations for scheduling conflicts and a drop in shift-communication errors are typically the first signals that the access gap has closed. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), the capability that most reliably predicts sustained employee engagement is whether employees receive the information they need, when they need it, without having to escalate. That is a delivery criterion before it is a cultural one — and it is the measurement frame that distinguishes mobile enablement outcomes from general engagement improvement initiatives. ## The precondition everything else depends on Rosa's problem — the policy she could not find at 6:30 a.m., the handoff she improvised — is not a training problem, a recognition problem, or a leadership communication problem. It is a delivery problem. The organizations that move the needle on frontline engagement are not the ones with the most sophisticated programs. They are the ones where those programs reliably reach every staff member they were designed for, regardless of shift schedule, device access, or location on the floor. Mobile enablement is the infrastructure layer that existing programs run on. Getting it in place does not require redesigning organizational culture or rebuilding every workflow. It requires removing the access barrier that currently stands between the 80% of frontline staff and the systems their organization has already built for them. The programs come after. But not before. --- # Boost Frontline Communication With An Employee SuperApp **Author:** Mason Hager **Published:** 2023-04-27 **Category:** employee-app This article will tell you everything you need to know about frontline employee communication. Furthermore, it will cover how an Employee SuperApp can help you reach traditionally neglected segments of the workforce. Are Your Frontline Employees Being Neglected? Frontline operations are fundamentally broken.  Your frontline employees are the beating heart of your organization. They are […] # Boost Frontline Communication With An Employee SuperApp Frontline employees are the beating heart of your organization — yet most digital tools are built for desk workers, not for the people on the floor, in the field, or at the bedside. An Employee SuperApp changes that by consolidating communication, scheduling, training, and self-serve tools into a single mobile app that frontline workers can access from their personal device — no corporate email, no VPN, no desk required. If your organization is struggling to reach its frontline workforce, this guide explains why the gap exists and how a SuperApp closes it. ## Are Your Frontline Employees Being Neglected? Frontline operations are fundamentally broken. Your frontline employees are the beating heart of your organization. They are often the ones that interact with your customers on a daily basis. Despite this, many organizations fail to equip their frontline workforces with the tools they need for day-to-day operations. Per Emergence Capital, 80% of the global workforce is deskless — yet the overwhelming majority of enterprise software investment targets the 20% who sit at a desk. In short, frontline employees simply are not provided the same tools and resources that desk-based workers receive. As a result, they rely on inadequate systems and limited tools to do their jobs. **Enter an Employee SuperApp.** Frontline Employee Apps are on the rise as organizations seek out ways to empower frontline employees with better access. An Employee SuperApp is a mobile application where users can access many different micro-apps, tools, and services within one platform. SuperApps can consolidate and replace multiple apps within a single tool for the user. They can fill in the gaps that inadequate systems have created. On the whole, they can ensure that frontline employees have all the tools they need at their fingertips — including offline access to critical documents and app content, so workers in low-connectivity environments such as warehouses, manufacturing floors, and field sites are never cut off from essential information. ## How To Improve Frontline Employee Communications For organizations with mostly desk workers, mobile tools are not always a priority. However, for frontline workers, mobile-ready tools are a necessity. Many organizations rely on inadequate systems and complex tools that make it difficult to handle even basic frontline employee communications. Per Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in, and only 13% use one daily. SWOOP Analytics puts the average daily time spent using intranet tools at just six minutes. When information and tools are scattered across siloed apps, your workforce is frustrated and unproductive. It can also expose your organization to additional problems such as unneeded licensing costs, siloed systems, disengaged employees, information overload, and an increased administrative burden on your IT department. IDC research finds that employees spend an average of 2.5 hours per day searching for information — time that frontline workers, who are paid to serve customers, simply cannot afford to lose. **This is where an Employee SuperApp comes into play.** Organizations are looking for a way to connect and enable their frontline employees. With the average person checking their phone 300+ times a day, the best way to engage frontline workers is clear. Mobile enablement can have a major impact on frontline employee retention — and the financial stakes are real: replacing a frontline employee costs between $4,400 and $15,000, making disconnection and disengagement a direct balance-sheet risk. For a broader view of how [employee communications](/solutions/employee-communications) strategy is evolving across industries, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) is a useful reference. **With an Employee SuperApp, you can:** - Enable frontline employee communication by giving them the tools to reach their dispersed colleagues. - Connect frontline employees with the resources & information they need within one app — accessible via personal device with a single branded app login, with no corporate email address required. - Allow frontline employees to quickly reference necessary information while on the floor, leading to additional upselling opportunities & improved customer service. - Provide a clear org chart and employee directory. This lets frontline workers know where to go and who to turn to for questions. - Provide frontline employees with self-serve tools that can lead to improved operational excellence & efficiency. - Integrate with complex systems to reduce the digital friction created by switching across apps while on the floor. A single branded mobile app can consolidate 200+ disparate systems into one mobile dashboard, as demonstrated in a real enterprise deployment. - Surface the right information automatically through AI-powered, role- and location-targeted content delivery — so workers find what they need without searching. ## The Day-To-Day Experience Of Frontline Workers Below, we'll dive into a few common pain points that frontline workers face daily without an Employee SuperApp: #### Shift Information & Scheduling **Without Employee SuperApp —** Frontline employees with variable schedules rely on getting weekly or bi-weekly shift information from management. Shift information can sometimes be located in the back room on paper copy and can undergo multiple rounds of revisions. Without a dynamic digital schedule, employees have to either keep checking, or receive multiple versions via text. This is a hassle for both employees and managers, and results in frequent miscommunication issues. **With Employee SuperApp —** Shift information is easily available with one click, and is always up to date. Employees access the current schedule in real time and can see any changes that are made. This is a small feature that can make a big difference in providing clearer insight into the day-to-day scheduling. For retail-specific scheduling best practices, see [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling). #### Siloed Apps — No Central Place To Go **Without Employee SuperApp —** Frontline employees rely on individual apps and tools to accomplish specific tasks in their day-to-day work life (examples include accessing HR info through ADP, communicating with colleagues through Slack, etc.). Oftentimes frontline staff are provided with multiple static intranet pages. However, it can be unclear which ones they need to go to and if the information is even current. The end result is a confusing and time-consuming experience that can lead to disengaged employees. **With Employee SuperApp —** The tools your frontline workforce need to do their jobs are now available within a single app. Frontline staff no longer need to switch back and forth across apps and try to locate specific resources/information. Everything is provided in a centralized mobile app that frontline workers can access from wherever they are. By providing a centralized place to go, you can empower your employees to operate more efficiently and effectively. Furthermore, you ensure that frontline employee communications actually make it to your workers. #### Training Materials & Policies **Without Employee SuperApp —** Many companies store training materials and onboarding policies on paper in a physical location. Such a system requires frontline employees to go to where the training materials are stored to access them. Cluttered paperwork often makes it difficult to tell if the information is up to date. This makes it difficult for employees to stay informed on new training information. It also limits the onboarding process and sets new hires up to fail. **With Employee SuperApp —** The app stores training materials and policies in an organized way, directly supporting employee engagement training by making learning resources available in the flow of daily work. This helps frontline employees quickly access the information they need, without spending a lot of time searching for it. Newly onboarded employees have access to all the training materials they need to hit the ground running on day one. For a deeper look at embedding learning into daily operations, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). #### Frontline Employee Communication Via Email **Without Employee SuperApp —** For frontline employees that receive a corporate email address, email can be a massive hindrance. If there's no central place to go to receive information, or no place for employees to communicate, organizations will rely on email to relay ALL of its information to frontline workers. That means that one email inbox is receiving countless announcements, file updates, irrelevant comms, and more on a daily basis. This can make it impossible for frontline employees to identify what information they actually need to know. **With Employee SuperApp —** Frontline employees are provided with multiple channels of communication. They receive a personalized news feed that only notifies them of information that pertains to their daily job responsibilities. Critically, access does not require a corporate email address — workers log in through a single branded app on their personal device. By eliminating irrelevant comms, frontline workers are able to stay in the loop and quickly see the information they need. #### The 'Backroom Computer' **Without Employee SuperApp —** The dreaded 'backroom computer' is an all too familiar problem. When retail workers have to go to the back of the store or [healthcare](/solutions/employee-app) professionals have to spend time away from patients, they are disconnected from the work they should be doing. This leads to diminished productivity, disengaged employees, and a poor customer experience. **With Employee SuperApp —** Effective frontline employee communication becomes possible when all the information they need is accessible from their phones. Whether it's communicating with colleagues, accessing important resources or information, viewing a policy, checking the shift schedule, or more, your frontline workforce are enabled with all the tools they need to increase productivity, improve retention and boost employee engagement. The end result is a massively improved frontline employee experience. --- ## Frontline Employee Communication Requires Mobile Enablement An Employee SuperApp is absolutely critical for organizations with a frontline workforce. You are able to connect and engage your entire workforce in a way that was simply not possible before. For further reading on this subject, see our guide to motivating frontline employees, our webinar on what frontline employees actually want, or case studies on TeamHealth and Petsmart. ## MangoApps — The Employee SuperApp for Frontline Teams **MangoApps** is built for organizations where the majority of workers are never at a desk. With MangoApps, you're able to give 100% of your workforce all the tools they need in one employee experience platform to increase productivity, improve retention, and boost employee engagement. MangoApps is customizable and offers a wide range of unique functionalities aimed at solving any business need. Organizations that have deployed a branded frontline app through MangoApps have reported 87% workforce engagement achieved within a few months of launch, 4x the industry engagement multiple, and 90% frontline adoption within the first six months of platform deployment. To learn more about how MangoApps can help your organization, or how you can take advantage of all the benefits that Employee SuperApps have to offer, book a demo or schedule a call with our team today. --- ## How Do You Choose the Right Employee SuperApp Vendor? Not all Employee SuperApps are built for frontline realities. When evaluating vendors, prioritize these criteria: - **No-email, no-VPN access:** Confirm that workers can log in via personal device without a corporate email address or network credentials. This is the single most common reason frontline workers are excluded from digital tools. - **Offline access:** Warehouse, manufacturing, and field environments often have limited connectivity. Verify that critical documents and app content are available offline. - **Adoption track record:** Ask vendors for documented adoption rates within the first six months. Benchmarks like 90% adoption are achievable but not universal. - **Integration depth:** A SuperApp that consolidates 200+ systems into one mobile dashboard eliminates app-switching friction; ask for a specific integration count and reference customers. - **AI-powered content targeting:** Modern platforms surface role- and location-relevant content automatically, reducing the burden on workers to search. Confirm whether the vendor's personalization is rule-based or AI-driven. - **Industry fit:** Solutions designed for [healthcare](/industries/healthcare), [grocery](/industries/grocery), or [financial services](/industries/financial) environments carry pre-built compliance and workflow considerations that generic platforms lack. For an independent assessment of how MangoApps stacks up against other intranet and employee experience platforms, see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms). ## What Does Implementation Actually Look Like? One of the most common follow-up questions after evaluating an Employee SuperApp is: *how long does this take, and what does rollout involve?* Based on documented enterprise deployments, a phased rollout typically follows this pattern: 1. **Discovery and configuration (weeks 1–4):** Map existing tools and systems to the SuperApp's integration layer. Define role-based content channels and notification rules. 2. **Pilot launch (weeks 5–8):** Deploy to a single location or department. Measure adoption, gather feedback, and refine the content taxonomy. 3. **Full rollout (months 3–6):** Expand to the full workforce. Organizations that follow a structured pilot approach consistently report higher adoption — the 90% adoption benchmark cited above was achieved within six months. 4. **Ongoing optimization:** Use built-in employee engagement survey and analytics tools to track which content channels drive the most interaction and adjust accordingly. For a real-world example of this process in a healthcare context, see [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology). The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) also covers implementation patterns across industries. The bottom line: organizations that treat the SuperApp rollout as a change management initiative — not just a technology deployment — achieve faster adoption and measurably higher employee engagement scores within the first quarter. --- # 10 Benefits Of An Employee SuperApp **Author:** Mason Hager **Published:** 2023-04-13 **Category:** employee-app This article will discuss the many benefits of an Employee SuperApp that unifies your tech stack. There are many tools and applications that employees need to access on a daily basis to effectively do their jobs. Each app is generally designed to fulfill a specific business need. Examples include an employee using Slack for internal […] ## 10 Benefits Of An Employee SuperApp An Employee SuperApp unifies your entire tech stack into one platform — and the benefits span both top-line growth and bottom-line savings. Below you'll find all 10 benefits explained, plus answers to the most common follow-up questions about cost, deployment, and vendor selection. There are many tools and applications that employees need to access on a daily basis to effectively do their jobs. Each app is generally designed to fulfill a specific business need. Examples include an employee using Slack for internal team communication or ADP to access their paystubs. On a one-off basis this is fine and doesn't represent a major liability to the business. However, the issues surrounding point solutions compound. When your whole tech stack consists of single-use solutions, employees waste a ton of time switching between applications. Frontline employees lose over 4 hours weekly switching between disconnected systems, creating measurable productivity drag beyond licensing costs. This can also expose your organization to a litany of additional problems. These include unneeded licensing costs, siloed systems, information overload, loss of productivity, and an increased burden on your IT department. **Employee SuperApps solve this problem.** So what is an Employee SuperApp? An Employee SuperApp (at its core) is one app that is moldable to solve every business need your employees have. Think of it as a Swiss army knife for your digital workplace needs. At MangoApps, we've seen many customers leverage our Employee SuperApp to achieve some combination of Employee Comms, Employee Engagement, Work Collaboration, Content Management, and Training. With an Employee SuperApp, your organization can realize many top-line and bottom-line benefits to improve operational excellence and employee experience. In this article, we'll take a deeper look at some of the top-line & bottom-line benefits an Employee SuperApp can offer. Let's dive in! ## Top-line Benefits of an Employee SuperApp: ### #1: Improve Customer Satisfaction Your frontline workers are the faces of your company and are regularly engaging with your customers on a daily basis. By prioritizing their needs with an Employee SuperApp, you are contributing to a more positive customer experience. This creates satisfied customers and reduces the burden on your employees by equipping them with the tools they need. Per Emergence Capital, 80% of the global workforce is deskless — meaning the majority of customer-facing interactions happen on mobile devices, away from a desk. A SuperApp built for mobile-first access directly addresses this reality. ### #2: Create Upselling Opportunities Another benefit is that you can increase upselling/bundling opportunities. An Employee SuperApp gives your sales and frontline workforce the resources, knowledge and training they need. Frontline employees with mobile training materials and resources can do their jobs more effectively and assist your customers quicker. A great example of this is **Kelly-Moore Paints**. Without an Employee SuperApp, frontline retail workers were disconnected from management and their colleagues while on the floor. They had no way to access key resources without going to the back room and looking at a computer. An Employee SuperApp enabled Kelly-Moore Paints' frontline employees to access any information or resources they needed while on the floor. Sales leaders could quickly search and resolve any customer questions and provide key insight directly from their mobile phones. This helped sales leaders create upselling and bundling opportunities while working on the floor, which was not previously possible. ### #3: Foster Innovation with Idea Campaigns Another way to take advantage of an Employee SuperApp is by fostering innovation with idea campaigns. Let your employees be your eyes and ears, and encourage input and feedback from all levels of your organization. This will help capture critical insights, increase employee satisfaction, and contribute to building a strong company culture. Idea campaigns allow the employees at the forefront of your business to provide key operational insights. It's also important to prioritize effective bottom-up communication within the organization. This will help create a space where employees feel they can share and be heard. This can go a long way to motivate frontline employees because they feel more valued. Without an Employee SuperApp, these ideas are unlikely to get captured because they rely on word of mouth. ### #4: Build Employee Advocates Employee advocacy with an Employee SuperApp can help improve your online brand presence and create employee ambassadors. Companies with strong employee advocacy programs are able to build a more cohesive workforce and recruit great talent faster. How Employee Advocacy benefits your company's brand: **Brand awareness and sales increase:** Posts shared by employees rather than company accounts receive 800x engagement. Findings show that 76% of people are more likely to trust content from an average person than a brand channel or its CEO. **Improves recruiting:** When sharing positive workplace experiences and company culture insights on social media, others unwittingly consume this information. People become aware of your company just by scrolling through their friends' feeds. So, when recruiters begin looking for new hires, they'll come across people who are already interested in your company. ### #5: Enable Community Knowledge Transfer The most important asset of your organization, other than your employees themselves, is the knowledge that they possess. With an Employee SuperApp you can empower frontline employees with community and collaboration. This means they can share their knowledge with their peers. With strong collaboration and a robust [employee directory](/key-features/employee-directory), you'll be able to effectively capture employee knowledge and share it with their colleagues. This will make employee training and onboarding processes go much smoother as well. Per IDC, employees spend 2.5 hours per day searching for information — a SuperApp's centralized knowledge base directly reduces that drag. ## Bottom-line Benefits of an Employee SuperApp: ### #6: Improve Operational Excellence With an Employee SuperApp, you can reduce the number of siloed applications and tools that employees use. When you use a wide array of point solutions, your IT team has to set up and manage each. By hosting everything within one platform, you can automate content governance and provide secure front-door access to the platform. TeamHealth, for example, consolidated 200+ systems into a single mobile dashboard — illustrating the scale of tech-stack consolidation a SuperApp enables. This will help streamline operations by minimizing software bloat and reducing the strain on your IT team. For organizations that rely on standardized [sop operations](/solutions/workforce-management) and compliance workflows, this consolidation also reduces the risk of process gaps across disconnected tools. ### #7: Increase Employee Productivity Wasted time is another common problem of employees having to navigate multiple apps to do their jobs. Every moment an employee spends switching apps to fulfill a specific business need is time wasted. Not to mention, it interrupts the flow of work. Context switching can set an employee back 15-20 minutes just to recenter their thoughts. By centralizing resources within an Employee SuperApp, you can reduce context switching and boost employee productivity. The contrast with legacy intranet tools is stark: per SWOOP Analytics, employees spend an average of just six minutes per day using intranet tools, and per Social Edge Consulting, nearly a third of employees never log in to the intranet at all. A SuperApp designed around daily workflows changes that equation. For a deeper look at how intranet adoption has evolved, see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms). ### #8: Boost Cost Efficiency Often compared to Swiss army knives, Employee SuperApps allow you to automate many of the manual and paper-based processes. This can help your teams reach their maximum potential. In addition, by consolidating extraneous tools, you can get rid of the associated licensing and administration costs. The financial impact can be significant: Wipro captured $20M in cost avoidance after deploying a unified employee experience platform. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines additional cost benchmarks for organizations evaluating consolidation. ### #9: Strengthen Employee Retention By giving 100% of your workforce access to an Employee SuperApp, you can improve frontline employee retention and company culture. With an Employee SuperApp, you can centralize communications and resources, providing employees with one platform for everything. Replacing a frontline employee costs $4,400–$15,000, making retention-driving employee engagement tools a direct cost-avoidance lever. A branded employee app signals investment in the workforce — and that signal matters. **In doing this you're able to effectively accomplish the following:** - Improve bottom-up communication across colleagues - Strengthen employee recognition programs and build a strong workplace community - Establish strong Diversity, Equity & Inclusion (DEI) efforts to ensure that every employee has a voice and feels valued — including multilingual teams, since a SuperApp can support 50+ languages with real-time translation - Implement employee reward programs where hard work doesn't go unnoticed OU Health achieved 87% workforce engagement within months of launching a branded employee app. PetSmart reported a 4x industry engagement multiple after deploying a similar solution. These outcomes are explored further in [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace). ### #10: Improve Employee Experience Leverage an Employee SuperApp to improve employee experience among both your frontline and desk-based workforce. By eliminating the digital friction from switching across apps, users can be provided with personalized and targeted communications that are relevant to them. This ultimately leads to a better frontline employee experience and a more connected workplace. AI-native personalization — surfacing the right content per employee role, location, and team automatically — takes this further. MangoApps connects to OpenAI, Gemini, Anthropic, and Azure OpenAI, ensuring AI personalization is enterprise-grade and not locked to a single vendor. For organizations building or refining their employee engagement software strategy, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) provides a useful benchmark. ## How Much Does an Employee SuperApp Cost? Cost varies by organization size, the number of modules activated, and whether you are replacing existing point solutions or adding net-new capability. The most useful framing is total cost of ownership: consolidating licensing fees across five to ten single-use tools typically offsets a significant portion of SuperApp investment. Wipro's $20M cost-avoidance outcome and TeamHealth's 200+ system consolidation are two reference points for enterprise-scale ROI. Organizations evaluating employee engagement software should also factor in the $4,400–$15,000 cost of replacing a single frontline employee — retention impact is a direct financial return. ## How Long Does It Take to Deploy an Employee SuperApp? Deployment timelines depend on integration complexity and the number of legacy systems being replaced. Unlike IT-heavy legacy intranet rollouts that can take six to twelve months, a modern SuperApp is designed for speed. MangoApps reports that 95% of customers reach full adoption within 90 days. The Kelly-Moore Paints deployment is a concrete example of rapid time-to-value: frontline workers went from having no mobile access to resources to resolving customer questions on the floor within a short rollout window. For organizations in regulated or complex industries, [MangoApps Wins Gold in Reworked's 2026 IMPACT Awards for Excellence](/articles/mangoapps-gold-reworked-2026-impact-awards) provides additional context on deployment outcomes. ## How Do You Evaluate Employee SuperApp Vendors? When comparing employee engagement software and SuperApp vendors, look for five criteria: (1) mobile-first architecture that serves the 80% of the global workforce that is deskless (per Emergence Capital); (2) intranet replacement capability — per Social Edge Consulting, 91% of organizations operate an intranet, but only 13% of employees use it daily, so the bar for engagement is low and the opportunity is high; (3) AI personalization that is multi-model and not locked to a single provider; (4) measurable adoption benchmarks, not just feature lists; and (5) consolidation depth — how many existing tools can the platform replace on day one. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) offers independent vendor comparisons across these dimensions. For learning-specific evaluation, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers how employee engagement training and development capabilities should be embedded in daily work rather than siloed in a separate LMS. ## MangoApps — The Employee SuperApp **MangoApps** is the Employee SuperApp for organizations with a frontline workforce. With MangoApps, you're able to give 100% of your workforce all the tools they need in one [employee app](/solutions/employee-app) to increase productivity, improve retention, and boost employee engagement. MangoApps is customizable and offers a wide range of unique functionalities aimed at solving any business need. To learn more about how MangoApps can help your organization, or how you can take advantage of all the benefits that Employee SuperApps have to offer, book a demo or schedule a call with our team today. --- # What Is An Employee SuperApp? **Author:** Mason Hager **Published:** 2023-04-03 **Category:** employee-app Before we dive into what an Employee SuperApp is, let’s first go over the term ‘SuperApp’.  A SuperApp is a mobile application with many different micro-apps, tools, and services within one platform. SuperApps can consolidate and replace multiple apps within a single tool for the user.  The general advantages of a SuperApp consist of: As […] Before we dive into what an Employee SuperApp is, let’s first go over the term ‘SuperApp’.  A SuperApp is a mobile application with many different micro-apps, tools, and services within one platform. SuperApps can consolidate and replace multiple apps within a single tool for the user.  The general advantages of a SuperApp consist of: Improved convenience – As more services & tools become digitized, co-locating new functionalities into a single app is becoming much easier. Instant usability – Users can access services and tools whenever a need arises without having to juggle a dozen different apps. Enhanced experience – By keeping services and tools personalized, users are able to receive an engaging and productive experience. As the need to reduce friction across a user’s digital experience continues to grow, we are seeing the average consumer incorporate SuperApps into their daily lives. A prime example of this is the popular ride-share app, Uber.  Uber offers its users a central app where they can go to access ride-sharing, food delivery, and package delivery services. It solves a present need and lets users access the different services they need without leaving the app. What Is An Employee SuperApp? It is clear that mobile devices are the most popular way for people to get their information. On average, approximately 70% of smartphone users check their phones within 10 minutes of receiving a notification. Organizations must listen to the data and meet your employees where they are – hence the need for an Employee SuperApp.  An Employee SuperApp is just like a regular SuperApp, except meant for work. It focuses on unifying the tools and resources employees use in their daily work life, particularly on the frontline.  Think of it as a swiss army knife for your frontline employee’s digital workplace needs. It includes all of the services and tools your employees need daily, all rolled into one singular platform.  The goal of an Employee SuperApp is to give your organization a tool that can be customized to your needs. At MangoApps, we’ve seen a wide range of unique use cases. However, a majority of our customers generally use Employee SuperApps to achieve some combination of Employee Communications, Employee Engagement, Work Collaboration, Content Management, and Training & Learning. With a single mobile app for all these things, you empower frontline employees with better access to company resources. Whitepaper – Employee SuperApps Want to eliminate information chaos and provide your workers with a unified employee experience? In this whitepaper, we give a detailed breakdown of why Employee SuperApps are becoming increasingly popular among frontline organizations. learn more 5 Ways This Can Benefit Your Organization Reach Every Employee – Get company news and other messages out to everyone on the channels they prefer. That means better access for frontline teams, and less disruption for desk workers. Centralize Your Company Content – Save time and promote efficiency with flexible, searchable repositories of content and knowledge. Bring Collaboration into the Open – Collaborate in team workspaces, so projects get done quickly and don’t fall through the cracks. Make Every Employee Feel Heard – Keep your team happy and engaged by giving everyone a voice and recognition. Connect Every Employee To Learning – Bring out the best in your team with learning resources that are always available. Read more about the benefits of an employee superapp. Why These Apps Are Important There are many tools and applications that employees need to access on a daily basis to effectively do their jobs. Any given employee has multiple needs. Without a SuperApp, those needs will likely translate into having to switch back and forth across employee applications. Switching across separate employee apps to solve unique business needs is an incredibly inefficient process and poses a massive problem. With multiple employee apps, your organization is opening itself up to a litany of potential risks, including: Siloed Systems – When work is done across separate tools it raises the risk of information being siloed. This can lead to duplicated work or important stakeholders missing out on information they should’ve been privy to. Information Overload – Too many tools and apps can become a burden on employees. People waste a lot of time learning the ins and outs of many complex tools and apps. Loss of Productivity – Diminished productivity is inevitable when employees are spending a large chunk of their day bouncing across applications. Increased Demand on IT – Multiple employee apps means multiple systems and tools your IT has to manage and navigate. This alone can become a full-time job and pulls your IT department away from working on more impactful projects. How An Employee SuperApp Benefits Your Workforce For frontline employees, an Employee SuperApp will: Fill in the technological gap caused by inadequate systems. Connect your frontline workforce with the resources and tools they need within one application. Add self-service tools to reduce the burden on IT, drive operational excellence, and improve employee productivity. Integrate with complex systems to reduce the digital friction associated with bouncing across different tools. Deliver a simpler mobile-first frontline employee experience that connects and engages workers in a way that was not previously possible. For a corporate/hybrid workforce, an Employee SuperApp will: Consolidate and secure the ‘front door’ access to siloed systems and tools that employees use on a day-to-day basis. Reduce information overload of irrelevant communications by providing intelligently prioritized notifications, so that employees only see what’s relevant to them. Provide a simpler mobile-first experience to your backend system. Allow employees to get the information they need without having to switch across different apps. Improve engagement as employees are equipped with a sustainable and effective digital workplace experience. Further Reading For more related reading, watch our webinar on what frontline employees actually want, read tips for boosting frontline employee engagement, or see our customer stories from TeamHealth, PetSmart, and CBHA. MangoApps – The Ultimate Employee SuperApp MangoApps is the ultimate Employee SuperApp for organizations with a frontline workforce. With MangoApps, you’re able to give 100% of your workforce all the tools they need in one employee app. This can increase productivity, improve retention, and boost employee engagement. MangoApps is customizable and offers a wide range of unique functionalities aimed at solving any business need. To learn more about how MangoApps can help your organization, book a demo or schedule a call with our team today! Schedule a call --- # Things To Consider Before Selecting An Intranet Vendor **Author:** Mason Hager **Published:** 2023-03-23 **Category:** intranet Deciding which intranet vendor to move forward with can be a make-or-break moment for your organization. And while it can be quite tempting to start jumping into demos, it’s important to do your due diligence first. Before setting up a vendor call, you should sit down with the decision makers within your organization and brainstorm […] Deciding which intranet vendor to move forward with can be a make-or-break moment for your organization. And while it can be quite tempting to start jumping into demos, it’s important to do your due diligence first. Before setting up a vendor call, you should sit down with the decision makers within your organization and brainstorm what you want the intranet to look like in five years. What would be considered a success? What would be considered a failure? What is the ultimate purpose the intranet would serve? These are just a few of the many factors you should consider before you start evaluating intranet vendors. The purpose of this article is to equip you with the internal discussions that you need to have prior to selecting an intranet vendor. Step 1: Put a team together The first step is to put together a leadership team within your organization that is suited to handle this new project. When building out a team it’s critical to have input from a wide range of job roles such as Internal Comms, IT, C-Suite, and more. Questions you should consider: Begin having early roadmap discussions regarding what you want the platform to look like Anticipate potential future issues. Who is going to support the intranet? Who is going to operate the intranet? Who is going to regularly maintain the intranet? Identify key stakeholders & outline the measures of success Who will be in charge of rolling out the intranet platform? Who is responsible for ensuring employee adoption? How will you measure the success of the intranet in 1, 3, 5 years? Who will be held accountable for achieving which metrics? Step 2: Decide whether you want to build or buy Prior to selecting an intranet vendor, you first need to consider whether you want to build or buy an intranet platform. Building an intranet might be a good fit if you have a large IT team and can dedicate thetime and resources to building out and maintaining an intranet. While building out anintranet might seem appealing at the start, there are many barriers and heavy investmentcosts that can start to build up over time. However, if you are seeking to purchase a pre-built packaged solution that can help instantlymodernize your intranet, then purchasing from an intranet vendor might be a better fit for your organization. Buying an intranet platform offers a more out-of-the-box, turnkey solution that ispurpose-built to solve the needs of the end user. It requires minimal IT involvement to set up and maintain. You need to decide internally if you have the time and resources to build out an intranet platform. If not, you may want to look into packaged intranet solutions you can purchase. Before doing this, consider what use cases you are trying to solve and identify what the purpose of the intranet will be.  Questions you will need to consider include: How heavy of an IT investment do you want to make to administer the new platform? What is the time frame you need to have the intranet launched? Does the intranet integrate with existing tools you already use? Does the intranet help you replace existing tools you already use? Is the intranet going to require a lot of third-party tools to fulfill the needs of your users? Switch To A Modern Intranet Learn about the benefits of switching to a modern intranet, and why it’s never too late to start building a better digital workplace for your employees. learn more Step 3: Establish long-term goals & objectives Now it is time to iron out the specific goals and objectives that the intranet will serve. Really think about it in detail what the intranet should look like 6 months, 1 year, 3 years, and 5 years from now. How will the intranet be considered a success? What processes need to be put in place to help accomplish it? How are you going to set yourself up for success? Understand what the end user needs? What capabilities are required to execute those needs? What will the intranet look like in 5 years? What are your company’s goals & vision for the intranet? Identify important use cases for your intranet How should the content be organized and presented to your employees? What should the landing page should look like and what information should be included? Where will employees go to get company and department information? Where will your teams communicate and collaborate? What customizations should be made to the mobile app? What technical integration requirements are needed for the platform? What problems are you trying to solve? What data do you have on what these problems are currently costing you? Calculate the ROI of MangoApps In this report, we take a look at how to measure the return on investment of adopting a modern digital work hub such as MangoApps. download report Top Questions To Ask During An Intranet Demo An intranet demo is a great place to get a better understanding of all the features and nuances a platform has to offer. Now that we’ve covered what you should consider prior to evaluating intranet vendors, let’s dive into what questions you should ask once you’re evaluating different platforms. Each intranet vendor has its own advantages and disadvantages. The purpose of this article is to help you navigate these differences so that you can select the platform that is the best fit for your organization’s specific needs. Let’s dive into some common and not-so-common intranet questions that you should consider when participating in an intranet demo.  Product Feature Questions: The first set of questions you should ask during an intranet demo are questions focused on the features of the platform. In this phase, you need to uncover what features and benefits the platform can offer your organization and how you can capitalize on them. Below is a list of questions aimed at helping you better understand the platform you are demoing. General Product Features: What are your most popular features, and how can we benefit from them? Can we push out communications to segments of our staff? Can users modify how they receive communications? What metrics does your intranet platform measure? What features does your intranet platform offer that will help strengthen our company culture? Customization & Branding Questions: It is important to gain clarity on what branding and customization capabilities the platform has during your intranet demo. Creating an intranet platform that looks and feels like an extension of your company does wonders in creating a seamless employee experience (and not to mention it helps improve employee adoption). Can the appearance and branding of the intranet be customized? Can our employees customize their environment?  Can we create custom page templates or add custom functionality to the intranet? How is the intranet structured and organized? Can we control which users or groups can access specific pages or content on the intranet? To continue reading, view the full article below: continue reading --- # Driving Engagement with Polls and Surveys **Author:** Mason Hager **Published:** 2023-03-16 **Category:** employee-engagement Attaining high levels of employee engagement is a top priority at any successful organization. Engaged employees are more likely to be productive, innovative, and committed to their work. It is therefore essential for companies to find ways to measure and improve employee engagement.  For organizations with a frontline workforce, monitoring engagement is especially critical. It […] # Driving Engagement with Polls and Surveys Polls and surveys are among the most direct ways to measure and improve employee engagement—but only when employees actually see and respond to them. For organizations with a frontline workforce, that last part is the hard problem. Frontline workers are often unreachable by email, disconnected from corporate intranets, and left out of the feedback loops that shape workplace decisions. This article explains how to use polls and surveys effectively, how to reach every employee regardless of role or location, and how to close the feedback loop so participation translates into real engagement gains. --- ## Why Polls and Surveys Fail Before They Start Most organizations already send surveys. The problem is reach and relevance. According to Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in to it—and only 13% use it daily. SWOOP Analytics reports that the average employee spends just six minutes per day using intranet tools. If your polls and surveys live only on a platform employees rarely visit, your response rates will reflect that, not your workforce's actual level of interest. The reach problem is even sharper for deskless workers. Per Emergence Capital, 80% of the global workforce is deskless—working in stores, clinics, warehouses, or on job sites without regular access to a desktop or corporate email. Sending a survey by email to a frontline employee who checks that inbox once a week is not a feedback strategy; it is a missed opportunity. Replacing a disengaged frontline employee costs between $4,400 and $15,000 (per MangoApps product research on retention cost framing), which means low survey participation is not just a data quality issue—it is a direct financial risk. --- ## Polls vs. Surveys: Choosing the Right Tool Polls and surveys serve different purposes. Using the right one for the right situation increases both response rates and the quality of information you collect. ### Polls A poll is a single question with a limited set of response options. It is designed for speed—employees can answer in seconds, and results are visible almost immediately. Polls work well for: - Gauging sentiment on a specific, timely topic - Collecting a quick read on preferences before a decision is made - Building a habit of participation through low-effort, frequent touchpoints - Creating social engagement around shared experiences (team events, seasonal moments, product launches) **Best practice — Poll of the Week:** Post one poll at the start of each work week. Rotate between business-relevant questions and lighter social topics to keep participation high. Collect results by midweek and share a brief summary with the team before the week ends. Consistency matters more than the individual question. **Poll ideas to get started:** - Which new product feature are you most excited to show customers this quarter? - How confident do you feel about the updated onboarding process? - What time of day do you prefer for all-hands updates? - Which team recognition format do you find most motivating? Frontline employees who receive targeted, role-based push notifications and in-app alerts are significantly more likely to respond to pulse surveys than those reached only by email (per MangoApps product research on frontline workforce and mobile-first themes). Distributing polls through a mobile app—one that works on personal devices without a corporate email address or VPN—removes the access barrier that kills participation before it starts. ### Surveys A survey is a multi-question instrument designed to gather detailed, structured feedback. Surveys take more time to complete and more time to analyze, but they produce the kind of layered insight that a single poll cannot. Surveys are appropriate for: - Annual or quarterly employee engagement questionnaires - Pulse checks on specific programs (benefits, scheduling, training and employee engagement initiatives) - Post-event or post-change feedback (after a reorganization, a new policy rollout, or a leadership change) - Identifying drivers of turnover or dissatisfaction in specific teams or locations **Survey ideas:** - A quarterly employee engagement survey covering workload, recognition, communication, and growth opportunities - A benefits feedback survey before open enrollment - A post-training survey measuring whether employee engagement training translated into on-the-job behavior change - A manager effectiveness survey distributed to specific teams For surveys to produce reliable data, distribution needs to be targeted. Sending the same 20-question survey to every employee regardless of role, shift, or location produces noise. Segmenting by team, location, or job function—and tailoring at least some questions to that group's specific context—produces signal. This is the difference between an employee engagement survey that informs decisions and one that generates a spreadsheet no one acts on. For organizations in industries with high frontline headcount, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading companies are redesigning their feedback programs to reach deskless workers at scale. --- ## How to Close the Feedback Loop (and Why It Matters) The single most common reason employees stop responding to surveys is that they never see anything change as a result. Closing the feedback loop—sharing results transparently and communicating what action will follow—is what converts a one-time survey into an ongoing engagement driver. A concrete workflow for closing the loop: 1. **Share the results.** Within one week of a survey closing, publish a summary visible to all participants. Include the top findings, the response rate, and any notable patterns by team or location. 2. **Acknowledge what you heard.** Name the themes that came up most frequently, including the uncomfortable ones. Employees notice when results are sanitized. 3. **State what will change—and what will not.** If a survey surfaces a request you cannot act on, explain why. If you can act on something, name the specific next step and who owns it. 4. **Follow up.** At the next survey cycle, reference what changed since the last one. This demonstrates that participation has consequences, which is the strongest driver of future participation. OU Health achieved 87% workforce engagement within a few months of launching a branded employee app with integrated communications (per MangoApps product research on the OU Health case study). PetSmart reported a 4x industry engagement multiple after deploying a unified mobile employee app (per MangoApps product research). In both cases, the technology enabled reach—but the feedback loop is what sustained engagement over time. For a broader view of how internal communication strategy connects to engagement outcomes, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the practices that separate high-engagement organizations from the rest. --- ## Targeting Polls and Surveys by Role, Shift, and Location One of the most common mistakes in employee engagement survey design is treating the workforce as a single audience. A question relevant to a warehouse shift supervisor is not relevant to a corporate finance analyst, and vice versa. Sending undifferentiated surveys to everyone reduces response rates and produces data that is hard to act on. Effective targeting means: - **Role-based distribution:** Send surveys about scheduling flexibility to hourly workers; send surveys about career development to salaried employees in growth tracks. - **Location-based distribution:** A retail location experiencing high turnover needs different questions than one with stable staffing. Segmenting by location lets you identify site-specific issues before they spread. - **Shift-based timing:** A survey sent at 9 a.m. will not reach employees who work the evening or overnight shift. Scheduling distribution to align with when a specific group is actually working increases open rates. - **Language and accessibility:** For multilingual workforces, surveys available only in English exclude a portion of the frontline population from providing feedback. Organizations in [retail](/industries/retail) and [hospitality](/industries/hospitality) face this challenge acutely, where frontline headcount is large, turnover is high, and the gap between corporate and store-level communication is wide. --- ## Frequently Asked Questions ### How often should we run employee engagement surveys? The right cadence depends on what you are measuring. Annual engagement surveys provide a year-over-year benchmark but are too infrequent to catch emerging issues. Quarterly pulse surveys—shorter, 5–10 questions—give you more timely data without survey fatigue. Weekly or biweekly polls keep a low-effort feedback channel open between formal survey cycles. Most organizations benefit from running all three at different cadences rather than choosing one. ### What is a good response rate for an employee engagement survey? Industry benchmarks vary by organization size and survey method, but a response rate below 50% typically indicates a distribution or trust problem rather than a content problem. If employees are not responding, the most common causes are: the survey is too long, it is delivered through a channel they do not use, or they do not believe their responses will lead to any action. Fixing the channel and closing the feedback loop consistently will raise response rates more reliably than shortening the survey. ### How does employee engagement connect to training and development? Engagement and learning are closely linked. Employees who feel their organization invests in their growth report higher engagement scores, and organizations that embed training into daily workflows see stronger retention. For a deeper look at how to connect these two levers, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers the structural reasons most L&D programs underdeliver on engagement. --- ## What to Do Next If your current polls and surveys are not producing the response rates or the actionable data you need, the problem is almost always one of three things: the channel does not reach your frontline employees, the distribution is not targeted to the right audience, or the feedback loop is not closed. Start with the channel. If your workforce includes a significant frontline population, your survey tool needs to work on personal mobile devices without requiring a corporate email address or VPN. From there, segment your distribution by role, location, and shift. Then commit to sharing results and naming next steps within one week of every survey close. MangoApps brings polls, surveys, and the rest of your employee communications into a single platform—so the feedback channel is the same place employees already go for schedules, policies, and team updates. To see how organizations with frontline workforces are using these tools to improve [employee engagement](/solutions/employee-engagement), explore the platform or connect with our team. --- # Empowering Frontline Workers With a SuperApp **Author:** MangoApps **Published:** 2023-03-13 **Category:** employee-app What is an Employee SuperAppAn Employee SuperApp focuses primarily on unifying the tools and resources an employee uses in their daily work life, particularl... # Empowering Frontline Workers With a SuperApp: A Practical Guide Frontline workers make up **80% of the global workforce** (per Emergence Capital), yet most organizations still equip them with tools designed for desk-based employees. The result is disengagement, high turnover, and operational friction that costs real money. Empowering frontline workers comes down to three concrete strategies: **unified mobile access**, **real-time communication**, and **community-building that reduces isolation**. This article explains each strategy, what good implementation looks like, and how to measure whether it's working. --- ## Why Frontline Workers Are Underserved Today Most organizations have invested heavily in corporate intranets and collaboration suites — according to Social Edge Consulting, 91% of organizations operate an intranet. But that investment rarely reaches the frontline. Nearly a third of employees never log in to the intranet at all (Social Edge Consulting), and only 13% use one daily (Social Edge Consulting). The average employee spends just six minutes per day using intranet tools (per SWOOP Analytics), while simultaneously losing 2.5 hours per day searching for information they cannot find (per IDC). Frontline workers face an even steeper barrier: they typically lack a corporate email address, a company-issued laptop, or VPN access. When the only path to company information runs through systems built for office workers, deskless employees are effectively locked out of the organization's knowledge base. Employees also lose over **4 hours weekly switching between disconnected systems** — a direct drag on productivity that compounds across a large frontline workforce. And when those workers leave, the cost is significant: replacing a frontline employee costs between **$4,400 and $15,000**, making retention tooling a direct bottom-line investment (industry report cited on MangoApps mobile product pages). --- ## Strategy 1: Unified Mobile Access — One App, Every Task The most immediate lever for frontline empowerment is consolidating the tools workers need into a single mobile experience that requires no corporate email or VPN. A well-designed [employee app](/solutions/employee-app) gives frontline staff access to shifts, shift swaps, open shift pickup, time tracking, and payroll in one place — from any personal or company-issued device. This is the core promise of an Employee SuperApp: not another standalone tool, but a platform that replaces the fragmented stack. TeamHealth, for example, consolidated more than 200 systems into a single mobile dashboard using a SuperApp-style platform. The licensing, integration, and IT overhead that accumulates invisibly across a multi-tool environment disappears when those systems are unified. For organizations evaluating total cost of ownership, the math is straightforward: the per-seat cost of a unified platform is almost always lower than the aggregate cost of maintaining separate systems for scheduling, payroll access, communications, and [workforce management](/solutions/workforce-management). A branded employee app — one that carries your organization's name and identity rather than a generic vendor interface — also signals to frontline workers that the investment was made specifically for them. OU Health achieved **87% workforce engagement within a few months** of launching a branded employee app (MangoApps branded app product page). PetSmart achieved **4x the industry engagement benchmark** after deploying a comparable branded frontline app. --- ## Strategy 2: Real-Time Communication That Reaches Every Worker Frontline employees are often the first point of contact with customers, yet they are frequently the last to receive important company updates. This is not a motivation problem — it is a structural one. When communication channels are built around email and desktop notifications, workers without those access points are simply excluded. Effective frontline communication requires: - **Mobile-first delivery** — push notifications and in-app messaging that reach workers on the devices they already carry - **Role- and location-specific content** — updates relevant to a specific shift, store, or department, not a company-wide broadcast that buries the signal in noise - **Two-way channels** — the ability for frontline workers to ask questions, flag issues, and respond to surveys, not just receive information AI-native personalization is making role-specific content delivery practical rather than a roadmap promise. Platforms that connect to large language models trained on company data can surface the right policy document, the right SOP, or the right shift update to each employee automatically — without requiring a manager to manually segment every message. For teams looking to benchmark their current state, an **employee engagement survey** is a useful starting point. Structured [employee engagement software](/solutions/employee-app) can automate pulse surveys and surface patterns across locations, shifts, and job functions that a manual process would miss. --- ## Strategy 3: Community-Building to Reduce Isolation and Turnover Frontline work is inherently mobile and often solitary. Workers who feel disconnected from the broader organization are more likely to disengage and eventually leave. Building community is not a soft benefit — it is a retention mechanism with a measurable return given the $4,400–$15,000 replacement cost per employee. Practical community-building for frontline teams includes: - **Peer recognition tools** — the ability to acknowledge colleagues publicly within the app, not just through a manager - **Interest-based groups** — spaces where workers across locations can connect around shared roles, interests, or challenges - **Visible leadership presence** — executives and managers posting updates, responding to comments, and making the organization feel accessible - **Onboarding and ongoing learning** — structured paths that help new frontline workers feel oriented and competent quickly, reducing early-tenure turnover For organizations that want to go deeper on learning as a retention tool, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading organizations are embedding development into daily work rather than treating it as a separate program. --- ## How to Measure Whether Frontline Empowerment Is Working Empowerment is only meaningful if it is measurable. The following metrics give a clear picture of whether your frontline strategy is producing results: | Metric | What It Measures | Target Benchmark | |---|---|---| | Daily active users in the employee app | Actual adoption, not just deployment | 50%+ of frontline workforce | | Employee engagement survey score | Perceived connection and enablement | Improve quarter-over-quarter | | Voluntary turnover rate | Retention impact | Below industry average | | Time-to-information | Efficiency of knowledge access | Reduce from 2.5 hrs/day baseline | | Shift fill rate | Operational self-service effectiveness | 90%+ shifts filled without manager intervention | For a broader view of where workforce operations are heading, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides benchmarks across industries including retail, healthcare, and financial services. --- ## What Frontline Workers Actually Want Research and deployment data consistently point to the same priorities when frontline workers are asked what would make their jobs easier: 1. **Access to their own information** — schedules, pay stubs, benefits, and HR policies without having to ask a manager 2. **Fast answers to operational questions** — where to find the SOP, what the policy is, who to call when something goes wrong 3. **To feel seen by the organization** — recognition, two-way communication, and evidence that leadership is aware of frontline realities 4. **Stability and predictability** — clear schedules, advance notice of changes, and tools that make shift swaps straightforward None of these wants are unreasonable, and none require a large technology budget to address. They require consolidation — replacing the fragmented stack with a single, mobile-first experience that frontline workers will actually use. For organizations in retail specifically, [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) covers how to operationalize several of these priorities at the store level. --- ## The Bottom Line: Empowerment Is an Operational Decision, Not a Culture Initiative Frontline worker empowerment is often framed as an engagement or culture project. It is more accurately an operational and financial decision. When 80% of your workforce (per Emergence Capital) lacks reliable access to the tools, information, and community that desk workers take for granted, the business consequences are measurable: higher turnover, lower productivity, slower SOP adoption, and weaker customer experience. The path forward is not adding another point solution. It is consolidating what already exists into a unified, branded, mobile-first experience — and then measuring adoption, engagement, and retention to confirm it is working. If your organization is evaluating where to start, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) provides a practical framework for auditing your current frontline communication stack and identifying the highest-impact gaps to close first. --- # How to Write an Intranet Proposal **Author:** Justina Kolb **Published:** 2023-03-13 **Category:** intranet Intranets began as a custom-built platform created by an organization’s IT team, essentially enabling employees access to files on a local, online directory. Though they’ve come a long way, “traditional” intranets are still, fundamentally, a static archive of information.  On the other hand, a “modern” intranet is rich with dynamic content. It anticipates employees’ needs […] # How to Write an Intranet Proposal An intranet proposal that earns executive approval follows a specific structure: problem statement with evidence, ROI projection, requirements list, implementation plan, and success metrics. Organizations that lead with the financial case — before features or vendor comparisons — close faster, because they answer the question executives are actually asking: what is this costing us today, and what will it cost to fix? This guide covers the six sections of an effective intranet proposal, what evidence belongs in each, and how to sequence the argument for a mixed audience that includes finance, IT, HR, and operations stakeholders. ## Why most intranet proposals fail before the first meeting The most common failure mode is leading with features instead of cost. A proposal that opens with "the new platform supports single sign-on and mobile access" gives a VP of Finance no reason to act. One that opens with "our employees spend 2.5 hours per day searching for information they cannot locate — and we are paying for that time in lost output every single day" opens a conversation. According to IDC research, knowledge workers lose 2.5 hours daily to information search. According to Social Edge Consulting, 91% of organizations operate an intranet, yet only 13% of employees use it daily, and nearly a third never log in at all. These figures belong in the opening paragraph of any intranet proposal — they establish that the problem is structural, not behavioral, and that demonstrated solutions exist. An effective proposal turns those statistics into a cost figure. If 300 employees each lose 2.5 hours per day at an average fully-loaded labor cost of $35 per hour, the organization is absorbing roughly $8.75 million annually in information-search waste alone. That math is the foundation of a financial case executives will take seriously. ## What to audit before you start writing Before drafting, gather evidence across three categories. **Usage data from the current intranet.** Login frequency, search success rates, and content publish dates. According to SWOOP Analytics, the average employee spends only six minutes per day using intranet tools. If your numbers match that benchmark, they are among the most persuasive exhibits the proposal can include. **Employee feedback.** A brief survey — five to eight questions — asking employees where they cannot find information, which systems they avoid, and what workarounds they use instead. Shadow IT (department-specific file shares, group texts, unsanctioned apps) is direct evidence that the official intranet is not meeting operational needs. **Retention and replacement data.** Frontline employee replacement costs between $4,400 and $15,000 per worker depending on role and industry. If disengagement is contributing to attrition — as it does in most organizations with underperforming intranets — those figures belong in the proposal's cost-of-inaction section. At OU Health, a mobile-first employee app achieved 87% workforce engagement within a few months of launch, demonstrating the measurable link between accessible communication infrastructure and retention outcomes. ## The six sections of an effective intranet proposal A proposal that wins approval answers six distinct questions the approval committee will ask. **Section 1: Executive summary** State the problem, the solution, and the expected outcome in plain language. A single paragraph that a CFO can read in 90 seconds: "Our current intranet reaches 13% of employees daily. We are losing an estimated [X hours] of productivity per week to search inefficiency and [X%] annual turnover in roles where a connected intranet demonstrably reduces attrition. We recommend transitioning to a [modern intranet](/solutions/modern-intranet) platform, with implementation complete in [X months], at an estimated annual cost of [X]." No jargon, no feature lists in this section. Save those for the requirements section. **Section 2: Current state assessment** Document specific gaps in the existing intranet against the needs of the workforce — not abstract frustrations but measured failures. Quantify wherever the data supports it: "45% of HR requests are submitted via email because the intranet forms do not work on mobile" is more actionable than "employees find the intranet hard to use." Approximately 80% of the global workforce is deskless, according to Emergence Capital — workers in manufacturing, healthcare, retail, logistics, and field services who are not at a desk during their workday. If the organization includes frontline employees, document explicitly whether the current intranet reaches them. In most cases it does not, because legacy intranets require corporate credentials, a VPN, or a desktop browser — none of which apply to an employee on a warehouse floor or a hospital ward. **Section 3: Requirements and evaluation criteria** Before naming a vendor, define what the new intranet must do. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) benchmarks current platforms across adoption, usability, and integration depth — a useful reference when building an evaluation criteria list that survives procurement scrutiny. Requirements worth addressing explicitly: - Mobile-first access with no corporate device or VPN required - Frontline login via name and passcode, not corporate email - Role and location-based content targeting for shift- and site-specific communications - Integration with existing HR, scheduling, and productivity systems - AI-assisted content delivery and enterprise search - Security and compliance credentials: SAML 2.0, OAuth 2.0, Active Directory, LDAP, and certifications appropriate to the industry (HITRUST for healthcare, SOC 2 broadly) The security section matters more than most proposal authors expect. IT and legal stakeholders will block approval if the proposal does not address data governance, access controls, and compliance certifications directly. Including an "AI readiness" criterion — asking vendors how their platform handles personalized content delivery and natural-language search — future-proofs the investment against technology changes in the next three to five years. **Section 4: Financial case** Enterprise intranet deployments on legacy platforms can cost $130,000 to $426,000 in the first year for a 1,000-user organization when customization, migration, and governance overhead are included. A modern SaaS platform with a mobile employee app included typically delivers a lower total cost of ownership against that baseline. Build the ROI calculation around three inputs: search time recovered (hours per employee per day multiplied by headcount and loaded labor cost), turnover reduction (a conservative 5% improvement in frontline attrition at your replacement cost per role), and IT overhead eliminated (content publishing and maintenance hours currently falling to the IT team). Modern intranet platforms routinely reach 90% frontline employee adoption within the first six months when access is designed for the full workforce — that adoption rate is what converts a financial model from theoretical to demonstrable. **Section 5: Implementation plan** A realistic timeline names phases: vendor selection, data migration planning, configuration and branding, pilot group rollout, training, and phased full deployment. Name who owns each phase. When ownership is ambiguous, procurement stalls because there is no clear contact for follow-up questions. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how high-performing organizations structure internal communications rollouts — including the change management approach that drives adoption in the months after launch rather than just at go-live. **Section 6: Success metrics** Commit to measurable targets at 30, 90, and 180 days: daily active users as a share of total workforce, content read rates for critical communications, HR ticket deflection (requests resolved via self-service versus submitted directly), and employee pulse survey scores on communication clarity and information accessibility. The [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) provides sector-level benchmarks for what high-engagement organizations achieve — useful context when setting the initial targets the proposal will be held to, and when the organization needs to show post-launch progress against an external standard. ## Three qualities that separate approved proposals from rejected ones **They quantify the cost of inaction, not just the cost of the solution.** A proposal asking for $200,000 without showing what the organization is currently losing will face more resistance than one that demonstrates the existing cost is $400,000 annually in productivity loss, attrition, and IT overhead. The IDC figure on search time (2.5 hours daily) and the Social Edge Consulting data on intranet non-use (nearly a third of employees never log in) are the two most credible figures to anchor this calculation. **They address the full workforce.** Proposals that treat frontline access as an afterthought miss the majority of employees in most industries. HR and operations reviewers notice the omission. According to Emergence Capital, 80% of the global workforce is deskless — an intranet proposal that does not address mobile-first, no-VPN access for that population is structurally incomplete. **They name a post-launch content owner.** An intranet that goes live without a designated governance owner becomes stale within months. SWOOP Analytics data showing six-minute average daily engagement is partly a product of intranet content that nobody is actively maintaining. The proposal should name the owner and describe the governance cadence — who publishes, who reviews, and how often the content calendar is updated. ## What belongs in the appendix Attach the employee survey results, the usage data export from the current intranet, the vendor comparison matrix, and analyst reports used in the platform evaluation. These materials do not belong in the body of the proposal — they create density that slows the approver's read — but they need to be available for the questions that follow approval in principle. The appendix is also where the intranet proposal template belongs: the structured document or slide deck format that internal champions can take into vendor conversations with consistent evaluation criteria already in place. An intranet proposal that earns approval is not necessarily more polished than one that is rejected. It is more concrete: it knows what the current state costs, it specifies who it is building for, it names a financial target, and it gives the approval committee something to act on. --- # Employee Engagement: Everything You Need to Know **Author:** MangoApps **Published:** 2023-03-03 **Category:** employee-engagement How to improve employee engagement  Engaged employees are the backbone of any successful business. To create a productive working environment, cont... # Employee Engagement: Everything You Need to Know ## What is employee engagement? Employee engagement is the degree to which employees feel committed to their organization's goals, motivated by their work, and connected to their colleagues and company culture. It is distinct from employee satisfaction — a satisfied employee may show up and do the minimum required, while an engaged employee brings discretionary effort, initiative, and genuine investment in outcomes. The business case for engagement is measurable. According to Social Edge Consulting, 91% of organizations operate an intranet, yet only 13% of employees use it daily — and nearly a third never log in at all. That data reveals something important: most organizations invest in the infrastructure of communication without solving the underlying engagement problem. Four pillars consistently appear in high-engagement organizations: - **Communication** — employees know what is happening, why decisions were made, and how their work connects to organizational direction - **Recognition** — contributions are acknowledged consistently, not just during annual reviews - **Growth** — employees have a visible path forward and development opportunities they can actually use - **Autonomy** — employees have authority to make decisions within their role and are not micromanaged into disengagement ## Why engagement gaps cost more than most organizations realize Disengagement is not a soft problem. IDC research finds that employees spend 2.5 hours per day searching for information they cannot locate in a single place. Multiply that by headcount and the drag on organizational output becomes concrete — and avoidable. Communication tools are supposed to close this gap, but SWOOP Analytics data shows the average employee spends just six minutes per day using intranet tools. An intranet used for six minutes per day has not solved the engagement problem. It has added a platform without changing behavior. The turnover cost of disengagement is equally direct. Replacing a frontline employee costs between $4,400 and $15,000, depending on role and industry. For organizations with high hourly worker turnover — common in retail, healthcare, logistics, and manufacturing — engagement is not an HR metric. It is a line item. ## The warning signs of declining engagement Engagement does not collapse suddenly; it erodes. The early warning signs appear before exit surveys, if organizations know where to look. **Declining participation in company communications.** When employees stop reading announcements, skip pulse surveys, or ignore team updates, the problem is rarely the content. It is that communication has become one-directional and irrelevant to their daily work. **Increased absenteeism.** Disengaged employees are more likely to take unscheduled leave. The pattern often shows up in scheduling data before it becomes visible in performance reviews. **Lower output without an obvious cause.** When productivity drops and no process or system change explains it, disengagement is a likely driver. Engaged employees bring discretionary effort; disengaged employees do not. **High turnover among peer groups.** When strong performers on a team resign in clusters, it rarely stops at one or two. Turnover clusters are often a signal that something in the team's dynamic or management has eroded the conditions for engagement. **Withdrawal from social tools and recognition programs.** When employees stop contributing to company channels, ignore peer recognition platforms, or decline to participate in group discussions, they are signaling disconnection from the community — not just the task. Catching these signals early requires more than an annual engagement survey. Organizations with high engagement typically run lightweight pulse surveys every four to eight weeks and track participation rates as a leading indicator. ## How to measure employee engagement effectively Most organizations default to annual engagement surveys, which are useful for benchmarking but slow at detecting changes in real time. A more effective approach layers three types of data. **Pulse surveys.** Short, frequent surveys of five to ten questions sent every four to eight weeks. These catch trends early enough to act on them before they become retention problems. **Participation metrics.** How often are employees logging into the intranet? Reading announcements? Completing training modules? Participating in recognition programs? These behavioral indicators do not require self-reported survey data and often reveal problems before employees articulate them. **Turnover and absenteeism patterns.** Retention data segmented by team, location, and role reveals which parts of the organization have structural engagement problems versus which have individual management issues. The combination of attitudinal data (surveys), behavioral data (platform metrics), and outcome data (retention) gives HR and operations teams a complete picture. Relying on any single source produces blind spots. An effective [employee engagement](/solutions/employee-engagement) strategy turns this data into action: identifying the teams at risk, understanding the underlying cause — whether a communication breakdown, a recognition gap, a growth stagnation, or an access barrier — and deploying a targeted intervention rather than a company-wide program. ## The frontline engagement problem most organizations underestimate Approximately 80% of the global workforce is deskless, according to Emergence Capital — workers in manufacturing, healthcare, retail, logistics, and field services who are not at a computer during their workday. Yet most employee engagement programs are designed for desk workers. The access model is the first barrier. Frontline employees typically do not have company email addresses or company-issued devices. An intranet that requires corporate credentials, a VPN, or a desktop browser reaches only the desk population — leaving the majority of many organizations' workforces disconnected from communications, recognition programs, and HR resources. The content model is the second barrier. A company-wide feed written for a corporate headquarters is noise to a warehouse worker in a different time zone. Effective frontline engagement requires content targeting by role, location, and team so employees see announcements relevant to their shift, their site, and their work. Platforms designed for frontline access allow employees to log in from a personal device with a name and a passcode — no corporate email, no VPN required. Frontline employees can be reached via push notifications, SMS, and in-app alerts for time-sensitive communications without requiring any corporate infrastructure on the employee's side. OU Health achieved 87% workforce engagement within a few months of launching a branded employee app with this access model — a result not achievable with a traditional intranet that required corporate credentials. ## The intranet's role in sustaining engagement A well-designed intranet is not a destination employees visit occasionally. It is the infrastructure through which they access policy documents, submit requests, find colleagues, complete training, and receive communications. When the intranet works, employees find what they need quickly. When it does not, they spend their time searching (2.5 hours per day, per IDC) or give up and route around it. Employees also lose over four hours per week switching between disconnected systems when tools do not integrate. That compounding drag affects both productivity and engagement — people who spend their day fighting fragmented tooling are not focused on their actual work. The most common intranet failure mode is staleness. When the HR section reflects a policy updated six months ago, or the news feed's most recent post is from two quarters back, employees learn the intranet is not authoritative. Traditional intranets take months to deploy, strain IT teams, and deliver static, ungoverned content that becomes stale without a dedicated content team to maintain it. [Gallup's 2026 State of the Global Workplace report](/articles/gallup-2026-state-of-the-global-workplace) provides a useful benchmark for where high-engagement organizations differ from average ones in their use of communication and collaboration infrastructure. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) benchmarks modern platforms specifically across adoption and usability criteria — a relevant reference when evaluating whether a platform change would move engagement metrics. ## Engagement in healthcare: a specific and urgent challenge In healthcare, there is a consistent gap between how organizations approach patient engagement and employee engagement. Administrators invest heavily in the patient experience, while frontline clinical staff — nurses, technicians, and support workers — often operate without reliable communication channels, recognition programs, or accessible HR resources. The consequences are direct: clinical teams that are disengaged produce worse patient outcomes and turn over at higher rates. Healthcare organizations that invest in frontline employee engagement see measurable improvements in patient outcomes and reductions in staff turnover. The investment in employee engagement is not separate from the investment in care quality — they move together. The practical challenge is that frontline clinical staff are almost never at a desk. Reaching them requires mobile-first access that does not depend on hospital-issued hardware or a corporate email address. Engagement programs in healthcare that have succeeded share this common feature: access that meets workers where they are, on the devices they already carry. ## Training, learning, and engagement Employee engagement and learning and development are not separate initiatives. Employees who can see a growth path within their organization — and who have access to development resources they can use during their actual workday — are consistently more engaged than those who feel stalled or invisible. The challenge for most L&D programs is relevance and access. Online courses that require a desktop browser and 30 uninterrupted minutes are not accessible to frontline workers on an eight-hour shift. Micro-learning — short, targeted modules accessible from a mobile device — changes the access model and, with it, the engagement dynamic. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how high-engagement organizations are integrating learning into daily workflows rather than treating development as a quarterly program that competes with operational demands. ## What actually moves the needle after 12 months Organizations that improve engagement scores over a 12-month period share a consistent set of moves. They identify the specific dimension underperforming — whether recognition, communication, growth, or access — and address it with a targeted intervention rather than a company-wide program that tries to do everything at once. They measure leading indicators: participation rates, communication read rates, pulse survey scores. They do not wait for lagging indicators like turnover and performance reviews to confirm what the behavioral data was already showing. They close the access gap for frontline workers before investing in content strategy. The most relevant content does not reach employees who cannot log in. And they treat the intranet not as a project but as infrastructure — something that requires ongoing governance, regular content updates, and a clear owner who is not waiting on IT to publish a policy change. Employee engagement is not a problem you solve once. It is the result of sustained decisions about communication, recognition, access, and development — made consistently, across a workforce that may include people in offices, hospitals, warehouses, and field sites who have never met. The organizations that get it right are the ones that build systems for it. --- # Modern Intranet Guide: How to Get Started **Author:** MangoApps **Published:** 2023-03-02 **Category:** intranet What Is A Modern Intranet?  Traditional intranets, although once highly innovative, simply didn’t adapt well to the modern working world. As a resu... # Modern Intranet Guide: How to Get Started If you're evaluating a modern intranet or trying to replace a legacy platform, this guide gives you a practical starting point. Below you'll find a step-by-step getting-started roadmap, answers to the most common follow-up questions, and links to deeper resources for each stage of the process. ## What Is a Modern Intranet — and Why Does It Matter Now? A modern intranet is a centralized digital workplace platform that connects employees to the information, tools, and people they need to do their jobs — whether they're at a desk, on a factory floor, or working remotely. It replaces the fragmented mix of email chains, shared drives, and disconnected apps that most organizations have accumulated over time. The scale of the problem is significant. According to IDC, employees spend an average of 2.5 hours per day searching for information. Per Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in, and only 13% use one daily. Per SWOOP Analytics, the average daily time spent using intranet tools like SharePoint is just six minutes. These numbers point to a gap between what intranets are supposed to do and what most employees actually experience. A well-implemented modern intranet closes that gap by making information findable, communications two-way, and the platform accessible to every employee — including the 80% of the global workforce that is deskless, per Emergence Capital. --- ## Getting Started: A 5-Step Implementation Roadmap This roadmap is designed for HR leaders, IT managers, and internal communications teams who are beginning or restarting an intranet initiative. ### Step 1: Audit Your Current State Before selecting a platform, document what you already have. List every tool employees use to find information, communicate, or collaborate. Identify where content is duplicated, outdated, or siloed. Note which employee groups — especially frontline or deskless workers — have no reliable access to company information at all. Key questions to answer: - Which tools are actively used versus abandoned? - Where does information get lost or delayed? - Do frontline employees have access without a corporate email or VPN? - What does your current platform cost in licenses, customization, and third-party add-ons? On that last point: SharePoint's first-year total cost for a 1,000-user enterprise can reach $130,000–$426,000 when implementation, customization, and third-party tools are included (per Awesome Technologies Inc.'s 2025 cost model). Purpose-built modern intranets are often a lower total-cost-of-ownership alternative worth including in your comparison. ### Step 2: Define Goals and Success Metrics A vague goal like "improve communication" is hard to measure and harder to fund. Tie your intranet initiative to outcomes that matter to leadership: - **Adoption rate**: What percentage of employees log in weekly? Aim for benchmarks like the 90% frontline adoption within the first six months achieved in a large enterprise deployment (CVS case study). - **Engagement**: OU Health achieved 87% workforce engagement within a few months of launching a branded intranet app. - **Search time reduction**: If employees spend 2.5 hours per day finding information (per IDC), even a 30% reduction has measurable productivity value. - **Retention impact**: Replacing a single frontline employee costs $4,400–$15,000 on average. Intranet adoption that reduces disengagement has a direct financial return. Define 3–5 metrics before you start vendor conversations so you can evaluate demos against real criteria. ### Step 3: Identify Your Must-Have Features Not every intranet platform is built for every workforce. Prioritize features based on your audit findings: - **Mobile-first access**: Essential if any portion of your workforce is deskless or frontline. Modern platforms allow employees to onboard without a corporate email address, VPN, or a desk — a capability traditional intranets and SharePoint do not natively support. - **Personalized content feeds**: Employees should see information relevant to their role, location, and department — not a single undifferentiated news feed. - **AI-assisted search and content surfacing**: Competitors increasingly lead with AI-curated content and natural-language search. Evaluate whether a platform can surface the right document or policy without requiring employees to know where it lives. - **Enterprise security**: SSO, SAML 2.0, and role-based permissions are now baseline evaluation criteria for IT buyers. Confirm that any platform you evaluate supports these natively, not through third-party workarounds. - **Department and team spaces**: Separate spaces for HR, operations, and individual teams prevent the content sprawl that makes legacy intranets unusable. [Department sites](/key-features/department-sites) and [workspaces](/key-features/workspaces) are the structural building blocks of a well-organized intranet. - **A branded employee app**: A consolidated mobile dashboard that brings together communications, documents, and tools in one place has been documented as a real-world intranet consolidation outcome — one large healthcare organization used this approach to unify access across 200+ systems (MangoApps case study, TeamHealth). ### Step 4: Evaluate Vendors Against Your Criteria Once you have a feature list and success metrics, run a structured evaluation. Ask vendors to demonstrate: 1. How frontline employees access the platform without a desktop login 2. How content is organized and governed at scale 3. What the security and compliance architecture looks like (SAML 2.0, SSO, role-based permissions, audit logs) 4. What the implementation timeline and support model are 5. What the total cost of ownership looks like over three years, including any required third-party integrations The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent vendor comparisons that can supplement your own evaluation criteria. For a structured list of questions to bring into a demo, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers what communications leaders are prioritizing in platform evaluations this year. ### Step 5: Plan Your Launch and Adoption Strategy Platform selection is only half the work. The most common reason intranets fail is low adoption — not poor technology. Build your launch plan around: - **Executive sponsorship**: Visible leadership participation in the platform signals that it matters. - **Department champions**: Identify one person per team who will model usage and answer questions. - **Content readiness**: Migrate only current, accurate content. An intranet audit before launch prevents the clutter that drives employees away. - **Phased rollout**: Start with a high-visibility use case (e.g., HR policies, company news) before expanding to all departments. - **Feedback loops**: Use [employee engagement surveys](/solutions/modern-intranet) and in-platform analytics to track adoption and identify friction points early. --- ## What Features Should a Modern Intranet Include? Beyond the must-haves listed in Step 3, a fully built-out modern intranet typically includes: - A **company portal** that serves as the default landing page with role-relevant news, announcements, and quick links — the [company portal](/key-features/company-portal) is often the first thing employees see each day. - A **webpage builder** that lets non-technical administrators create and update pages without IT involvement — [drag-and-drop page creation](/key-features/webpage-builder) reduces the bottleneck that causes content to go stale. - **Integrations** with existing tools (HRIS, payroll, ticketing systems) so employees don't have to leave the intranet to complete common tasks. - **Analytics and governance tools** that show which content is read, which is ignored, and which is out of date. Vertical-specific needs matter here. Healthcare organizations, for example, prioritize compliance documentation and shift-based access. Retail organizations need scheduling integrations and store-level communications. Education institutions often require faculty-specific spaces separate from administrative content. Evaluate whether a platform's default configuration fits your industry or requires significant customization to get there. --- ## How Do You Improve Intranet Engagement After Launch? Low engagement is the most common post-launch problem. Per Social Edge Consulting, nearly a third of employees never log in at all. Addressing this requires both structural and cultural changes: - **Make the intranet the single source of truth**: If employees can get the same information by email or Slack, they won't develop an intranet habit. Redirect key communications to the platform. - **Personalize the experience**: Generic content feeds drive disengagement. Role-based and location-based content filtering keeps the platform relevant. - **Use push notifications**: A [mobile employee app](/solutions/employee-app) with push notifications reaches employees who don't proactively check the intranet. - **Recognize and reward participation**: Acknowledge employees who contribute content, answer questions, or complete training through the platform. - **Audit regularly**: Content that is outdated or irrelevant is a primary driver of disengagement. Schedule quarterly reviews. For organizations with unionized or frontline workforces, engagement strategy requires additional consideration around communication rights, access equity, and tool standardization. [Managing a unionized workforce](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) requires a different software approach than a fully office-based organization. --- ## What Does a Secure, Enterprise-Ready Intranet Look Like? Security and governance have become top evaluation criteria for IT buyers — five major competitors now cover "secure intranet" as a distinct content theme (per competitor gap analysis). When evaluating platforms, confirm support for: - **Single Sign-On (SSO)** and **SAML 2.0** authentication - **Role-based permissions** that control who can view, edit, or publish content - **Content governance workflows** with approval chains and expiration dates - **Audit logs** for compliance and access tracking - **Data residency options** if your organization operates across multiple jurisdictions These are not optional features for enterprise deployments — they are the baseline IT will require before approving any platform. --- ## Your Next Step If you've read this far, you have enough to begin. Start with Step 1: spend one week documenting your current tool landscape and identifying the employee groups with the worst information access. That audit will shape every decision that follows — platform selection, feature prioritization, and launch sequencing. For a broader view of where internal communications and employee experience platforms are heading, [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) provides context on the workforce trends that make intranet investment a strategic priority rather than an IT project. When you're ready to see how a purpose-built platform addresses the gaps described in this guide, the [MangoApps modern intranet solution](/solutions/modern-intranet) page covers the platform's architecture, security model, and deployment options in detail. --- # How Knowledge-sharing Fosters Quick Decision-making **Author:** Justina Kolb **Published:** 2023-02-14 **Category:** knowledge-management Quick decision-making is an overlooked, powerful tool. Often, analytical approaches to decision-making – while regarded as safe & responsible – drag out far too long, which delays results. One reason rational, measured systems tend to take time is the lack of available, relevant information. By providing your company access to necessary information & encouraging knowledge-sharing, […] # How Knowledge Sharing Fosters Quick Decision-Making The bottleneck behind most slow organizational decisions is not a shortage of smart people or decisive leadership. It is a shortage of accessible, relevant information at the moment those people need to act. Per McKinsey, employees lose 2.5 hours daily — roughly 30% of a working day — searching for information they need to do their jobs. Per APQC, Fortune 500 companies lose $31.5 billion annually to knowledge loss, a figure that does not include the compounding cost of delayed decisions made on incomplete information. These are structural problems, not behavioral ones. Coaching teams to act with urgency does not help when the information required to act is not findable in under five minutes. This article examines why decision paralysis in organizations is primarily an infrastructure problem, what knowledge systems do to remove the underlying causes, and why the organizations that consistently make faster decisions build specific structural features rather than cultivating cultural norms about boldness or decisiveness. ## Why slow decisions are not a mindset problem The conventional advice on faster decision-making focuses on individual behavior: narrow your information gathering, trust your instincts, accept that you might be wrong. That guidance is not useless, but it misdiagnoses the root cause of decision delays in team and operational settings. In most organizations, decisions slow down for one of three structural reasons. First, the person who needs to decide does not have the relevant information — not because it does not exist, but because it is buried in someone else's email, a shared drive folder no one has organized, or a document that has not been updated in 18 months. Second, the decision-maker does not know who holds the expertise they need, so they cast a wide net rather than a targeted one. Third, teams lack any reliable mechanism for capturing how similar decisions were made before, which means every recurring situation gets treated as novel. None of these failures respond to personal discipline. They respond to infrastructure. Per a Banner Health employee survey, 59% of employees had trouble finding the information they needed when they needed it, and 63% said the content they found was not current or relevant. When more than half a workforce cannot reliably locate accurate, up-to-date information, the lever is information access — not individual decision-making behavior. ## The AI shift: from search results to surfaced answers Three years ago, improving knowledge access meant better search filters and more consistent document tagging. The capability baseline has shifted significantly. The defining development in knowledge management tools is AI-assisted search: systems that understand natural-language questions, identify the most relevant document or expert, and return a direct answer with the source cited for verification — rather than a list of documents to sift through. The research phase that most decision delays are composed of can be bypassed structurally. A well-configured [knowledge management](/solutions/knowledge-management) system answers the question before the employee has to formulate a multi-step search. This has two specific effects on decision speed. First, it eliminates the information-gathering bottleneck that creates analysis paralysis — the trap of collecting more and more data because no single source provides a clear enough answer. Second, it allows the knowledge base to stay current through AI-assisted drafting. When a process gap surfaces, the historical pattern has been to flag it and wait days or weeks for a documentation update to be written, reviewed, and distributed. AI-assisted drafting compresses that cycle to hours. The relevance of current, accurate content is not marginal. Per Banner Health's survey, 63% of employees said their intranet content was not current or relevant. Stale knowledge bases do not just fail to help — they erode trust in the system, causing employees to route around it and fall back on asking colleagues directly, which reintroduces the exact bottlenecks the infrastructure was built to eliminate. ## Frontline teams: where the information gap is steepest Most treatments of knowledge sharing and decision speed assume office workers with laptop access and time for research. The actual majority of the global workforce — over 80% by most estimates — is deskless. Frontline workers in distribution centers, retail stores, healthcare facilities, and field operations make decisions throughout the day using whatever information they happen to have on hand at that moment. When the relevant procedure is in a binder at the manager's station, or when the updated safety protocol arrived in an email chain the overnight shift never saw, decisions get made on instinct or institutional memory rather than current information. The information gap for frontline teams is not an edge case — it is the standard operating condition. Per Banner Health's survey data, 61% of employees wanted intranet access outside the work VPN, and 55% specifically wanted mobile device access. For a frontline population, these are not preference items — they are the difference between decisions supported by current information and decisions made in an information vacuum. A knowledge management approach built for mobile access without VPN requirements closes this gap at the structural level. How Santee Cooper built [a connected knowledge hub accessible across every corner of its distributed workforce](/resources/santee-cooper-case-study) illustrates what this looks like in practice for a large organization with employees spread across locations and shifts. ## What faster-decision organizations actually build Organizations that consistently make faster decisions share a structural pattern — not a culture of boldness, but an information architecture with three features. **A single, actively maintained source of truth.** Not a document repository where everything lives somewhere, but a system where content is current, tagged for relevance, and surfaced through search rather than requiring employees to know where to look. The operational distinction matters: a file system and a [knowledge base](/key-features/knowledge-bases) have fundamentally different utility for someone who needs an answer in the next three minutes. Content governance — scheduled reviews, ownership assignment, deprecation workflows — is what separates a knowledge base that stays useful from one that drifts into the same irrelevance as the intranet it replaced. **Expert-findable directories.** When a decision genuinely requires additional judgment, the fastest path is reaching the right person on first contact. A searchable employee directory with skills, roles, and experience fields — not just org-chart position — turns "gather input from someone who knows" from aspirational advice into a 30-second action. This is what collapses the second structural cause of slow decisions: not knowing who to ask. **Captured institutional memory.** The most costly form of slow decision-making is repeating the analysis on a situation that has clear organizational precedent. When past decisions, their rationale, and their outcomes are captured in a searchable format rather than locked in the memory of whoever made them, teams can build on that record rather than starting from scratch. This is the structural solution to recurring-situation paralysis — and it is what separates organizations that get faster over time from those that remain flat. ## How to measure the impact — and make the internal case Soft claims about faster decisions rarely move budget conversations. The metrics that do are grounded in operational cost. Per APQC, Fortune 500 companies lose $31.5 billion annually to knowledge loss. Per McKinsey, employees spend 2.5 hours daily searching for information. In a 500-person organization, that translates to over 300,000 person-hours consumed annually by information retrieval alone — before accounting for the downstream cost of decisions made on incomplete data. The measurement framework for most organizations is straightforward: establish a baseline for how long it takes to find answers to common operational questions, and track the change after a knowledge system rollout. Reductions in repeated-question volume, shorter time-to-productivity for new hires, and lower per-employee information-search overhead are all legible to finance and operations leadership because they map directly to headcount efficiency. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents how operations leaders are structuring knowledge and communication infrastructure across frontline teams, including the metrics they track and the benchmarks their deployments hit. ## The structural fix The evidence on knowledge sharing and decision-making points to a conclusion that behavioral advice consistently misses: the organizations that make decisions faster are not the ones with bolder cultures or more decisive leadership. They are the ones where the right information reaches the right person before that person has to look for it. APQC's $31.5 billion figure and McKinsey's 2.5-hour daily search burden describe the cost of the gap. The fix is a sequenced infrastructure problem. Make information findable — through AI-assisted search, current content, and expert directories accessible on any device without VPN constraints. Capture institutional memory in searchable form rather than in email threads and individual recall. Then measure the information-search overhead per employee and track what changes quarter over quarter. Knowledge sharing fosters faster decisions the same way good roads foster faster travel: not by asking people to move faster, but by removing the obstacles that slow them down. The behavioral advice — trust your instincts, narrow your options — is real guidance for individuals. But the infrastructure question comes first: what information is available, to whom, and how quickly can they reach it? --- # Top Questions To Ask During An Intranet Demo **Author:** Mason Hager **Published:** 2023-02-01 **Category:** intranet An intranet demo is a great place to get a better understanding of all the features and nuances a platform has to offer. Each intranet provider has its own advantages and disadvantages. This article will help you navigate these differences, so that you can select the platform that is the best fit for your organization’s […] An intranet demo is a great place to get a better understanding of all the features and nuances a platform has to offer. Each intranet provider has its own advantages and disadvantages. This article will help you navigate these differences, so that you can select the platform that is the best fit for your organization’s specific needs. To explore a specific solution, learn more about the modern intranet platform we sell at MangoApps. Let’s dive into some common and not-so-common intranet questions that you should consider when participating in an intranet demo.  Product Feature Questions: First, we will highlight questions you should ask during an intranet demo that are focused on the features of the platform. In this phase, you need to uncover what features and benefits the platform can offer your organization and how you can capitalize on them. These questions will help you better understand the platform you are demoing and whether it has all the essential features of a modern intranet. General Product Features: What are your most popular features, and how can we benefit from them? Can we push out communications to segments of our staff? Can users modify how they receive communications? What metrics does your intranet platform measure? What features does your intranet platform offer that will help strengthen our company culture? Does your intranet offer tools that enable content monitoring and governance? How are the performance and usage of the intranet monitored and reported? Other: How much training do your customers typically need to start navigating the platform? How does your intranet platform encourage employee adoption? Does your intranet offer a mobile app to reach our frontline employees?  Can employees search for files and resources? Can we lock certain departments & groups? Can we make our employees’ calendars publicly viewable?    Switch To A Modern Intranet Learn about the benefits of switching to a modern intranet, and why it’s never too late to start building a better digital workplace for your employees. learn more Customization & Branding Questions: It is important to gain clarity on what branding and customization capabilities the platform has during your intranet demo, so you can follow the standard modern intranet best practices. Creating an intranet platform that looks and feels like an extension of your company does wonders in creating a seamless employee experience (and not to mention it helps improve employee adoption). Branding: Can we customize the appearance and branding of the intranet? Is the mobile app a company-branded experience? What branding features do you offer to make this feel like an extension of our company? Can we add logos and other graphics to the intranet?    Can we customize the appearance of the intranet to match our company’s branding? Customization: Can our employees customize their environment?  Can we change the color scheme and layout of the intranet? Can we create custom page templates or add custom functionality to the intranet? How is the intranet structured and organized? Can we control which users or groups can access specific pages or content on the intranet? Other: Can we create and manage multiple sites or microsites within the intranet? Can we use the intranet to host and display marketing materials, such as brochures and presentations? Can we create and manage forms or surveys on the intranet? Can we customize the intranet to meet the needs of different departments or teams within the company? Integration Questions: It is crucial to get a better understanding of the integration flexibility the platform you’re exploring has. You need to clearly assess whether this platform can incorporate the tools you are already using and how difficult it is to add new integrations. Are there any pre-built integrations available with popular tools and platforms? Can the intranet be integrated with single sign-on (SSO) or other authentication systems? Can we integrate the intranet with other online tools and platforms, such as social media or Google Analytics? What do integrations to Microsoft 365 & G Suite allow us to do within the platform? Do you charge a fee to create integrations with third-party tools upon request? Can we integrate our email/calendar? Will you create integrations for important tools/systems if not already available?  Does your intranet integrate with our existing HR, IT tools, and systems? A Deep Dive into Security & Compliance at MangoApps We know that intranet & communications are the front doors to your company’s data, and we have a special responsibility to keep it safe and secure. learn more Security Questions: Many organizations reside within industries that demand rigorous compliance and security requirements. It is important to assess whether the intranet you are evaluating can meet these security requirements. As a logical first step, gain a better understanding of what you can do within the platform, how your data is stored, and how information is protected. Security: How do users access the intranet, and what level of access do they have? Can we access the intranet from outside the office, and if so, how is that done? What type of encryption does your platform have? Do you offer MFA, and if so, what methods? How detailed are your audit logs, and what is visible to us? Where is data stored? What platform is your intranet hosted on? How do employees connect to the app via SSO? Compliance: Does your intranet conform to the ISO 27001 certification? Is your company HITRUST certified, HIPAA compliant, and/or SOC 2 Type II compliant? What framework compliances does your intranet platform adhere to? How many customers do you have in our industry, and how do you help them remain compliant? Setup & Onboarding Questions: Often during an intranet implementation, companies don’t want to commit a large team of resources to set up the platform and get employees onboarded. You should be able to maximize intranet engagement without having to use up all your IT resources. During the intranet demo, ask discovery questions that will help you assess whether the intranet provider will supply a team of resources to help ensure a smooth onboarding process. What is the process like to set up the platform? What is the average intranet rollout process time frame? What is the projected timeline of information you need from us? Can non-technical employees set up their own pages? Can non-IT people administer this intranet? White Glove Onboarding with MangoApps This eBook represents a high-level overview of what you can expect when you become a MangoApps customer. learn more Support Team & Post-Launch Success Questions: What can you expect from the support team after the launch of the intranet? Will you be provided with a hands-on customer success representative? Where do you go if you have questions regarding specific features within the platform? These are just a few of the questions you need to consider when choosing an intranet platform. Having a successful post-launch plan in place can make a massive difference in ensuring consistent employee adoption. Is your support team available after the launch of the intranet? Will we be assigned our own CSM/TAM? Do you offer a dedicated project support portal where we can ask questions and receive answers immediately? Does your support team offer monthly check-ins to train our admins on any new releases/features? Do you offer a customer portal where we can communicate and engage with other people that use your platform? How do we monitor policy changes?  Is the platform easy to understand to the extent that we don’t need IT involvement? Product Roadmap & New Releases Questions: A good intranet platform will have a decent product roadmap with improvements and new features constantly being added. During your intranet demo, ask to see the product roadmap and also try and see if there’s a way for new features to be added based on customer feedback. Can we add features in the future?  Do we have any say in the product roadmap?     Does your product roadmap detail planned updates/improvements on existing features? How frequently do you publish new releases?  Do the new releases alter our environment? How is user feedback taken into account when making changes or improvements to the intranet? Calculate the ROI of MangoApps In this report, we take a look at how to measure the return on investment of adopting a modern digital work hub such as MangoApps. download report Pricing Questions: Lastly, it’s important to ask questions regarding pricing. You need to see if the intranet platform is within your budget and what a typical contract looks like. Use these questions to assess whether the pricing of the platform is a good fit. What package plans do you offer, and what do they entail? Do you offer a pricing model that is only ‘pay for what we need’?  What is the estimated cost per user for your platform? Do you offer monthly payments or annual payments? If we need to add additional user licenses, can we add them under the same pricing? Is there a pricing tier model with how many user licenses we purchase? Are there any other fees we have to pay during the implementation process? Are there any recurring fees that occur after the implementation process? Do you offer a free trial for us to pilot the platform and see if it’s a good fit for our company? Is there a minimum amount of user licenses we need to purchase? MangoApps Intranet Demo MangoApps is the only employee hub that brings communications, content, engagement, teamwork & training in one seamless system for every worker. Deploying MangoApps helps companies drive engagement, boost productivity & streamline operations. For more reading, see some intranet design examples, get the basics of what a modern intranet is, or read customer stories from TeamHealth, symplr, and Great Harvest Bread. To learn more about how MangoApps can help your organization, schedule an intranet demo to see the product in action. book demo --- # Improve Employee Experience To Boost Your Business **Author:** Justina Kolb **Published:** 2023-01-12 **Category:** employee-experience A poor employee experience can break your business. To help improve employee experience within your company, we’ve put together a list of real-life instances where a digital employee experience platform would positively impact a business.  Without an engaged, enlightened staff, companies grow stagnant, eventually shrinking to extinction. Ensure a positive employee experience by providing team members with […] # Improve Employee Experience to Boost Your Business According to IDC, employees spend 2.5 hours per day searching for information they need to do their jobs. That's more than 600 hours per year, per person — time spent chasing answers that already exist somewhere in the organization, buried in an email thread, saved under an ambiguous filename, or posted on an intranet page nobody updated since the previous administration. According to Emergence Capital, 80% of the global workforce is deskless. Most employee experience strategies are built for the other 20% — the desk-based employees with a corporate laptop, a corporate email address, and reliable access to the company's digital tools. The frontline majority operates on the margins of these systems, if it can access them at all. Closing both gaps — the search-time problem and the access problem — is the work that actually improves employee experience. Recognition programs, culture workshops, and engagement surveys build on top of that foundation, but they cannot replace it. What follows are the strategies that organizations use to address the structural conditions that make work harder than it needs to be. ## Fix information access before launching culture initiatives Most employee experience improvement efforts start with the visible layer: recognition platforms, values workshops, town halls. These matter, but they rest on an assumption that employees can find the information they need to do their jobs. For most organizations, that assumption is wrong. Social Edge Consulting found that 91% of organizations operate an intranet, but only 13% of employees use it daily. Nearly a third never log in at all. SWOOP Analytics benchmarks average daily intranet time at six minutes. The knowledge exists — policies, procedures, org charts, HR forms — but the retrieval mechanism is failing so thoroughly that employees have stopped trying. Fixing information access means two things: consolidating knowledge into a searchable, single-source system, and ensuring that system reflects current policies rather than outdated drafts. A knowledge base where employees can find the current version of a policy, a step-by-step procedure guide, or a department contact list — without asking a colleague or opening email — is a more powerful driver of employee experience than any initiative built on top of broken infrastructure. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents how organizations that invested in information architecture improvements before culture programs saw faster, more durable engagement gains than those that went the other direction. ## Reach the workers who don't sit at desks A manufacturing company with 3,900 employees across six countries cannot improve employee experience by improving its desktop intranet. A construction supply firm with 1,500 workers across 45 locations has the same problem. Most of those employees don't sit at desks, don't have corporate email addresses, and don't work from laptops. Frontline employees need to access communications, schedules, and HR tools without a corporate email address or VPN — on personal iOS or Android devices, with offline support for locations with variable connectivity. The enrollment flow has to support QR codes, SMS invitations, or personal email as valid credentials, so an employee hired on Monday can reach day-one documentation before IT provisioning is complete. Organizations that have solved this problem have seen results worth citing. OU Health achieved 87% workforce engagement within months of launching a branded employee app for frontline clinicians and support staff — people who were previously unreachable through standard intranet channels (source: MangoApps frontline employee app). The financial framing is equally direct. Frontline employee replacement costs range from $4,400 to $15,000 per worker. When disconnected communication contributes to turnover, the cost is measurable and material. Access isn't just an engagement concern — it's a retention and operational risk. ## Replace email as your primary communication channel An accounting firm with 450 employees relying entirely on email as its communication backbone faces a problem that compounds as the organization grows. Email is designed for communication between individuals, not knowledge distribution across teams. Important messages compete with irrelevant ones. New employees cannot search the reasoning behind decisions made before they joined. Policy updates cannot be revised in place — they require a new message, which most recipients will miss. Structured communication channels — organized by team, location, project, or department — change this dynamic in three ways. First, employees receive relevant information rather than everything, which reduces the cognitive load of filtering a full inbox. Second, targeted distribution allows managers to reach specific groups — frontline workers on a particular shift, employees in a given location, new hires in their first 30 days — without broadcasting to the entire organization. Third, posts and announcements in a structured system accumulate in a searchable archive, which new employees can access retroactively without anyone having to forward or re-explain context. [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) found that communication quality is among the top predictors of employee engagement. The organizations where employees report feeling informed are the ones that have moved beyond email-centric models to structured, audience-specific distribution. ## Create feedback loops, not just broadcast channels Most intranets are broadcast systems. Leadership posts announcements; employees receive them. The dynamic is one-directional, and employees adapt accordingly — they stop checking regularly because nothing there invites a response. Feedback mechanisms change the relationship between employees and organizational communication. Employees can flag errors in a policy document directly in context. Managers can see which employees accessed a specific update. Comment threads on announcements surface concerns that would otherwise stay invisible until they become larger problems. Pulse surveys, idea-submission tools, and open Q&A formats create channels for bottom-up input alongside top-down distribution. This matters operationally, not just culturally. Organizations that treat employee feedback as a signal — about where information gaps exist, where processes frustrate, where training is missing — can surface and address issues before they compound into attrition or compliance failures. The feedback infrastructure is what distinguishes a communication platform from a notice board. ## Consolidate tools before adding more platforms Employees lose over four hours per week switching between disconnected systems — a direct productivity cost tied to tool sprawl (source: MangoApps unified platform). Remote and distributed teams compound this by adopting different tools in different locations, creating compatibility issues, duplicate content, and version-control problems that no single team is responsible for resolving. Many employee experience improvements trace back to a consolidation decision: replacing five overlapping platforms with one unified system that handles communication, knowledge management, task coordination, and HR access. Organizations replacing legacy intranets have consolidated 200 or more disparate systems into a single mobile dashboard — and the reduction in context-switching has proven more impactful on daily employee experience than any feature added to the existing stack. Traditional intranet deployments take months of IT-led customization and produce static, ungoverned content that becomes stale quickly. An effective alternative is a platform designed for active maintenance: content owners assigned to specific pages, review prompts triggered when documentation passes its scheduled refresh date, and search functionality that surfaces the right document rather than requiring employees to know the exact file name. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) benchmarks enterprise platforms across search quality, governance controls, and frontline accessibility — the three factors that most reliably predict whether a knowledge base gets used or abandoned. ## Govern access as the workforce scales As organizations consolidate tools, the governance question becomes critical: who can access what, and how is that access controlled as roles change, employees leave, and organizational structure evolves? This is not an abstract concern — it's an operational and compliance requirement. A distributed workforce accessing organizational systems from personal devices is a real security surface. The answer isn't restricting mobile access, which would cut off the frontline workers most dependent on it. It's implementing role-based permissions, single sign-on, and audit trails that establish security without requiring corporate devices or VPN connections. For compliance-sensitive industries — healthcare, financial services, construction — the audit trail matters as much as the access layer. The ability to confirm which version of a policy was active on a specific date, who accessed it, and when it was last modified is governance infrastructure that makes a knowledge base defensible under audit. The [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study illustrates how organizations with complex regulatory requirements have implemented these controls without sacrificing frontline accessibility. ## Measure access, reach, and engagement in that order Employee experience efforts frequently optimize for what's visible — recognition program participation, survey response rates — rather than what's structural. The IDC benchmark (2.5 hours per day searching for information, per employee) establishes that the structural problem is large enough to be the first priority. A practical measurement sequence starts with access: can employees find the information they need, on the device they have, without assistance? From there, it moves to reach: are communications actually landing with frontline workers, or are they sitting in a system that a third of the workforce never logs into? And from there, to engagement: are employees using channels to interact and respond, not just receive? Organizations that measure in this sequence typically find they were solving the wrong problem. Engagement scores improve when access and reach are fixed first — not because of the measurement, but because the infrastructure that enables engagement was blocking it. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) documents patterns across manufacturing, healthcare, retail, and financial services — each with its own version of the same structural problem, and interventions that follow the same logic. ## The infrastructure question is the experience question Employee experience is not a culture program layered on top of broken infrastructure. It is the infrastructure itself — the communication channels, the knowledge access, the ability to reach every worker on the device they carry and verify that the message actually arrived. Organizations that solve for access first, then reach, then engagement, tend to see the same outcomes converge: lower turnover among frontline workers, faster onboarding for new hires, fewer repeat questions from employees who now have a reliable place to look before asking a colleague, and management teams with enough visibility to intervene before small communication gaps become operational incidents. The IDC research on information search costs — 2.5 hours per day, across every organization that has not solved the delivery problem — establishes the business case without ambiguity. The organizations that have addressed it directly, not by adding one more tool but by consolidating, governing, and extending access to the full workforce, consistently outperform those that have substituted culture programs for infrastructure. --- # Why You Should Replace Email **Author:** Mason Hager **Published:** 2023-01-03 **Category:** employee-experience Too many companies rely on email for all of their internal collaboration. By having email as the primary source of communication, it can result in a cascade of productivity issues. Employees receive so many emails that it becomes very difficult to create a sense of priority. Thus, they start to tune out certain messages and […] # Why You Should Replace Email Email solved a real problem in the 1980s: getting a message from one person to another quickly and without a phone call. By the time it became the default backbone of organizational communication, nobody had designed it to handle what it was being asked to do — carry the full weight of coordination, documentation, escalation, and culture for tens of thousands of people simultaneously. The result is visible in the numbers. Per IDC, the average employee spends 2.5 hours per day searching for information that should be findable but is not. Per SWOOP Analytics, the average employee spends just six minutes per day using their intranet — a platform that exists specifically to solve the information problem email created. Per Social Edge Consulting, 13% of employees use their intranet daily, and nearly a third never log in at all. These are not adoption metrics. They are signals that the underlying architecture — email as the primary communication channel — produces predictable failure regardless of which tools surround it. The question for most organizations is not whether email is insufficient, but what replacing it actually involves and what the real cost of delay looks like. ## Why email was never built for internal communication Email is a push medium. Every message sent creates an implicit obligation to read, triage, and respond. At scale — hundreds of messages per day across every team — that obligation accumulates into a second job that nobody hired for, running inside the job people were actually hired to do. The deeper problem is that email has no concept of organizational relevance. A message sent to 3,000 employees lands with identical weight whether it's a critical safety alert or a facilities announcement relevant to twelve people in one building. Recipients make the filtering decisions individually, without a shared system for separating signal from noise. The information infrastructure of most organizations is, at its core, thousands of employees making the same triage decisions in parallel, arriving at different conclusions, and missing different things. Email also does not produce knowledge. It produces message history — fragmented across individual inboxes, inaccessible to anyone not on the original thread, and unsearchable at the organizational level. Debra Helwig, a Senior Internal Comms Manager at KCoe Isom, described this directly: "Firmwide email isn't searchable. If I don't read something, or don't see it, or let it get a hundred down in my inbox, or hit the delete button by accident, there's no institutional memory." The collaboration platform model inverts this dynamic. Pull communication gives employees a personalized stream of relevant information they can engage with on their own terms, rather than an undifferentiated inbox they're expected to process completely. Conversations happen in shared spaces, documents are versioned and searchable, and information persists for the organization rather than for the individual recipient. ## The frontline access gap that email cannot solve Per Emergence Capital, 80% of the global workforce is not desk-based. Retail associates, healthcare aides, warehouse workers, and field technicians represent the majority of employees in most industries — and the majority of them don't have company-issued devices or corporate email addresses. This creates a structural exclusion that organizations rarely name directly. When email is the primary communication channel, frontline employees without email access are not underserved — they're out of the system entirely. Policy updates, schedule changes, safety information, and HR communications travel through informal channels: printouts in break rooms, messages passed supervisor to supervisor, or simply nothing reaching the person who needed it. The cost of this exclusion compounds. Frontline employee replacement costs range from $4,400 to $15,000 per worker, making disconnected communication a direct retention risk — not just a productivity drag. Workers who feel uninformed are workers who feel undervalued, and who eventually leave for employers where they don't. Per Social Edge Consulting, 91% of organizations operate an intranet, and yet nearly a third of employees never log in. The gap between ownership and reach is, in most cases, an access model problem: the platform exists, but it was not built for the people who needed it most. Modern employee apps reach frontline workers on personal devices without requiring corporate email enrollment or IT-provisioned accounts. The [employee app model](/solutions/employee-app) — no email address required, no managed device, no VPN — delivers schedules, company updates, HR tools, and peer communication in one mobile-accessible place. ## What email costs in security exposure Organizations that have moved internal communication to dedicated platforms often identify security as the benefit they didn't expect to value as much as they do. Email is an external channel connected to every inbox, spam network, and phishing campaign on the internet. Every internal communication sent over email is a message that passes through infrastructure designed for external correspondence — with all the exposure that entails. Five major intranet and collaboration platform vendors now lead their market positioning with enterprise security credentials as a primary differentiator: governance controls, data-loss prevention, and zero-trust access models. The reason is straightforward: organizations that replaced email-centric workflows discovered that their internal communication had been traveling over an externally connected, poorly governed channel. Dedicated internal platforms keep communication inside a governed environment where DLP policies, audit logs, and access controls can actually apply — and where regulatory compliance is built into the data model rather than retrofitted. For regulated industries — healthcare, financial services, government contractors — this distinction determines whether a platform can be deployed at all. It is not a preference; it is a procurement criterion. ## The information fragmentation email creates at scale Knowledge that lives in email threads is unavailable to anyone who wasn't on the original thread, invisible to search tools that can't index private inboxes, and lost when the employee who holds it leaves the organization. Organizations that replace email with shared collaboration spaces find that the information availability problem improves almost immediately — not because people communicate more, but because what they communicate becomes organizationally accessible rather than personally held. Per IDC, employees spend 2.5 hours per day searching for information. Most of that time is spent searching for things that were communicated once, in an email thread, to the wrong distribution list, in a format that didn't survive the conversation. The search failure is not a search problem — it is a documentation architecture problem, and email creates it structurally. A platform built around shared spaces, wikis, and version-controlled documents eliminates this at the source. The information employees need exists in places the organization controls and can search — not in personal inboxes that disappear when someone leaves. ## What to look for when replacing email The replacement decision depends on which problem is most urgent. Most organizations discover all three — frontline access, security governance, and information fragmentation — but identifying the primary one helps scope the evaluation. **For frontline workforce reach**: The critical criterion is access model. Platforms that require corporate email enrollment or managed-device authentication reproduce the exclusion that email already creates. Look specifically for no-email enrollment, offline document access, and push notification delivery to personal devices. The absence of any one of these three criteria limits frontline reach in practice, regardless of what the platform documentation claims. **For information governance**: The question is whether communication lives in shared, searchable spaces or individual inboxes. Messaging tools like Slack and Microsoft Teams are better than email at persistence, but they create a different kind of fragmentation — message history in channels, files in a separate system, HR information somewhere else entirely. A unified platform that combines messaging, documents, wikis, and workflows in one searchable environment is structurally different from a messaging layer bolted onto existing infrastructure. **For regulatory compliance**: Data-loss prevention, audit log coverage, and PII detection need to be built into the platform's data model — not configured as a layer on top. Platforms that treat governance as a feature addition rather than a foundational design constraint produce implementations that require exception handling at every compliance review cycle. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) benchmarks major platforms across frontline accessibility, search quality, and administrative overhead — a practical starting point for organizations moving from evaluation to selection. ## What replacing email actually produces OU Health achieved 87% workforce engagement within a few months of launching a branded employee app for clinical staff. TeamHealth consolidated more than 200 disconnected systems into a single mobile dashboard. Both outcomes share one structural driver: the platform reached employees who were previously outside the communication system entirely. Engagement improved not because content quality increased, but because the access model changed. When a push medium that excludes 80% of your workforce is replaced with a pull medium that reaches all of them on their own devices, the engagement data changes because the denominator changes. You stop measuring a desk-worker sample and start measuring the workforce. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), the correlation between frontline employee engagement and customer satisfaction outcomes is consistently underestimated in organizations that measure engagement only from the desk-worker sample. Email-centric organizations are measuring engagement from the population that was already inside the communication system — and missing the disengagement of everyone else. ## Determining whether your organization is ready The readiness question is not about technology capability. It is about where the communication failure is most visible and most costly. If more than 30% of your workforce lacks a company-issued device or email address, the current channel architecture is excluding a majority of the people you're trying to reach. If your IT team manages email provisioning and de-provisioning for frontline workers who turn over every six to twelve months, the administrative cost is continuous and measurable. If your compliance environment requires audit log coverage across internal communications and you cannot produce those logs on demand, the risk is material rather than theoretical. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) provides measurement frameworks for setting adoption benchmarks before a platform selection begins — including the employee sentiment signals that predict engagement changes before attrition numbers move. Replacing email is not a technology upgrade. It is a decision about which employees the organization intends to be in communication with — and whether the current architecture is actually reaching them, or simply serving the employees who were going to be reached regardless. --- # How To Improve Employee Engagement **Author:** Justina Kolb **Published:** 2022-12-13 **Category:** employee-engagement Do you find it difficult to retain employees? Are the remaining employees lacking a sense of ambition or dedication? Do members of your organization avoid learning new skills? Engaged employees are the backbone of any successful business. To create a productive working environment, continuously improving employee engagement is essential. With this article, we’ve compiled a […] # How To Improve Employee Engagement Replacing a single disengaged frontline employee costs between $4,400 and $15,000 in recruitment, onboarding, and lost productivity. Most organizations treat that figure as a recruiting problem. It is an engagement problem — and it is preventable with structural changes that most engagement programs are not built to make. The organizations closing the engagement gap fastest share a common insight: frontline and remote workers are a distinct engagement challenge, not a scaled-down version of the office-worker problem. Per Emergence Capital research, 80% of the global workforce is deskless. If your engagement strategy was designed for a conference room with a shared display and reliable WiFi, it reaches at most 20% of your people by design. This article covers why most engagement programs miss the majority of the workforce, what the structural barriers actually are, and what it takes to build engagement that holds across job roles, locations, and levels of technology access. ## Why engagement programs consistently miss frontline workers Corporate intranets are the most visible symptom of the gap. Per Social Edge Consulting, 91% of organizations operate an intranet. Per the same research, only 13% of employees use it daily, and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends six minutes per day using intranet tools. Those numbers describe the engagement infrastructure's reach — not its effectiveness. The employees logging in reliably are office workers with corporate email addresses, time at a desk, and familiarity with a browser interface. The employees not logging in are tellers, warehouse staff, field technicians, and hourly retail workers — the people who handle the most customer interactions, execute the most operational transactions, and produce the highest per-capita output. Per IDC, employees spend 2.5 hours per day searching for information. For frontline staff, that overhead doesn't happen at a desktop during a planned break — it happens mid-shift, during a customer interaction, or not at all. The procedure doesn't get retrieved. The updated policy from three weeks ago sits unread. The shift lead makes a judgment call on outdated information and gets it wrong. Engagement programs that don't account for this access problem aren't failing because of poor effort or weak design. They're failing because the channel they're built on structurally excludes the employees they're designed to reach. ## The four structural barriers to frontline engagement Naming these barriers specifically — not as excuses, but as design constraints to engineer around — is the prerequisite for fixing them. **No corporate email, no access.** A meaningful share of frontline employees, particularly in organizations with high hourly turnover, don't have company-issued email addresses or devices. An engagement program built on email is invisible to them from day one. The announcement sent to "all staff" reaches every office worker and zero shift workers without a corporate email address. This isn't a niche edge case — it's the default state for retail, hospitality, manufacturing, and healthcare organizations at any scale. **The tool stack is fragmented.** Engaged employees consistently report having what they need to do their work well. When the tools required for a single job are spread across four or more disconnected systems — a scheduling app, an HR portal, a communication platform, and a task tracker that don't share a login or a notification layer — the cumulative friction reads as disengagement. Each context switch is a small productivity tax. The accumulated daily total is a reason to look elsewhere for work. **Communication flows in one direction.** Broadcasting announcements without a feedback mechanism is operationally indistinguishable from not asking. If an employee has no way to respond, flag a problem, or report that something isn't working, the absence of feedback becomes invisible rather than informative. Organizations that measure engagement through passive consumption metrics — email open rates, intranet page views, video plays — are measuring reach, not engagement. A read receipt confirms delivery. It doesn't confirm that anyone believed the message, acted on it, or felt heard enough to raise a concern next time. **Recognition doesn't reach the floor.** Recognition programs designed for office environments depend on visibility: a manager sees work being done well, praises it in a shared channel, and the employee receives acknowledgment in real time. For a frontline worker without a desk or a persistent team channel, that loop closes rarely if at all. Per [Gallup's 2026 State of the Global Workplace research](/articles/gallup-2026-state-of-the-global-workplace), employees who receive consistent recognition are significantly more engaged and meaningfully less likely to leave — but the recognition has to reach them through a channel they actually access. ## What actually moves the engagement number Interventions that produce durable, measurable engagement gains share structural properties that one-off programs don't. They reach employees where they already are. They don't require a separate login, a desk, or a corporate device. And they close the feedback loop so employee input leads to observable outcomes. **Eliminate the email requirement.** An [employee engagement platform](/solutions/employee-engagement) that enables mobile access through personal devices — without requiring a corporate email or VPN — removes the primary access barrier for frontline and hourly staff. The policy update, shift reminder, and recognition notification reach the shift lead on the floor through the same interface as the communications director at a desk. Any deployment that skips this baseline reaches a fraction of its intended audience. **Build role-scoped communication.** Relevance is a prerequisite for engagement. An employee who receives every announcement regardless of whether it applies to them learns quickly to treat the channel as noise — and eventually stops opening it. Communication filtered by role, location, and department improves signal quality before any engagement campaign begins. Personalized, role-relevant information doesn't require AI to be effective; it requires a platform that can distinguish what a warehouse supervisor needs to know from what an HR business partner needs to know. **Make feedback part of the channel, not a separate program.** Engagement surveys that live in a different tool from day-to-day communication are surveys that don't get answered. When the feedback mechanism is embedded in the same channel employees use for shift scheduling, announcements, and task tracking, response rates rise and the data becomes actionable rather than archival. The structural question is whether employees can observe what changed based on their input — not just that input was received somewhere. **Recognize work in the flow of work.** Peer-to-peer recognition within the communication platform — visible to the team rather than only to a manager — produces the social reinforcement that makes recognition meaningful rather than bureaucratic. Recognition requiring a separate nomination form, a formal review cycle, or a manager's initiative as the exclusive trigger won't reach frontline staff at the frequency that produces measurable engagement effects. ## How to measure engagement accurately across a distributed workforce Engagement is routinely measured as a satisfaction score. That is a proxy for a more precise question: do employees have what they need to do their work, and do they believe the organization values their contribution? Satisfaction scores capture the feeling; the conditions below drive the underlying number. **Access completeness.** Can every employee, regardless of role or location, receive and respond to communications in real time? Organizations where frontline staff are structurally excluded from the communication layer will consistently undercount engagement — because they are only measuring the employees the platform can actually reach. Access completeness is a measurement prerequisite, not a platform feature. **Information retrieval time.** When employees need a procedure, policy, or operational contact, how long does it take to find it? Per IDC's finding on the 2.5-hour daily search overhead, information retrieval is among the largest drivers of productive capacity loss — and it registers as disengagement when the system consistently fails to deliver what employees need to do their work confidently. **Feedback loop closure rate.** When employees raise a concern, submit a survey response, or flag an operational problem, what percentage lead to a visible outcome? Without evidence that input produces change, surveys become checkboxes and the disengagement they were designed to surface continues unchecked. This metric is rarely tracked, which is part of why engagement scores can fluctuate without corresponding changes in behavior or retention. **Recognition frequency by role tier.** Recognition frequency is among the highest-correlation predictors of frontline retention. Tracking it specifically by role — whether hourly and shift workers receive recognition at rates comparable to office staff — reveals structural gaps that aggregate engagement scores consistently obscure. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers current measurement approaches organizations are using to move beyond satisfaction-score proxies and toward engagement conditions that are observable and attributable. ## The infrastructure question underneath all of it Engagement programs fail not because the ideas are wrong but because the infrastructure makes them impossible to execute at scale. A recognition program cannot reach an employee who has no access to the channel it runs on. A feedback initiative cannot close the loop if the response mechanism exists in a separate tool with a separate login. A learning program disconnected from daily work patterns won't change behavior — and the research on why that happens consistently is worth understanding before launching another L&D initiative. (For the structural analysis of why learning programs disconnect from actual job performance, [this breakdown of why L&D strategies fail](/articles/learning-and-development-strategy-embedded-in-daily-work) covers the pattern directly.) Organizations reaching 85–90% workforce engagement within six months of a platform launch consistently do the same things: they treat access as a prerequisite, not an afterthought. They deploy communication tools that reach every employee on the device they actually carry. They build feedback into the communication channel rather than running a separate survey program. They close the loop publicly — using the same channel to communicate what changed based on employee input — so the feedback behavior gets reinforced rather than quietly dying off after the first cycle. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are restructuring communication infrastructure specifically to reach frontline staff at the same engagement levels as corporate teams. At any meaningful headcount, the math favors infrastructure investment over program investment. Replacing one disengaged frontline employee at the lower bound of the $4,400–$15,000 range costs more than most per-seat software licenses at enterprise scale. Programs designed to address engagement that cannot reach the employees experiencing it most are not solving the problem — they are measuring its symptoms in the population that didn't have the problem to begin with. The engagement gap is a structural problem. It has structural solutions. --- # MangoApps and Carahsoft Announce Partnership **Author:** MangoApps **Published:** 2022-12-07 **Category:** press-release MangoApps, a modern digital work hub provider that unifies content, communication, training, and operations for an organization, and Carahsoft Technology Corp., The Trusted Government IT Solutions Provider, announced today a strategic partnership. # MangoApps and Carahsoft Announce Partnership State agency IT directors face a procurement reality that software comparison frameworks rarely account for: a platform that scores well in an evaluation can sit in contracting for six months while the fiscal year closes around it. The evaluation was thorough. The decision was made. The deployment never happened. This is not an edge case. It is the structural gap that separates digital workplace adoption in the public sector from adoption in commercial environments. Per IDC research, employees lose 2.5 hours per day searching for information they cannot find — time that compounds across every role in every agency, regardless of whether a better platform has already been selected. The MangoApps partnership with Carahsoft Technology Corp. is designed to close both barriers simultaneously: a digital workplace platform built to reach every government employee, available through the contract vehicles public sector procurement teams already use. ## The two-part adoption problem government agencies face When government agencies audit intranet performance, the numbers reveal a structural failure that typically gets attributed to the wrong cause. Per Social Edge Consulting, 91% of organizations operate an intranet, but only 13% of employees use it daily, and nearly a third never log in at all. Per SWOOP Analytics, average daily intranet usage across enterprise organizations is six minutes. Those numbers have two explanations that get conflated. The first is platform architecture. Standard intranet tools were designed for employees at a desk with a corporate email address and reliable network access. Per Emergence Capital, approximately 80% of the global workforce is deskless — a figure that, in government agencies with field operations, translates to a structural adoption ceiling. A field inspector at a state transportation department, a healthcare aide at a county clinic, or a facilities technician at a federal building operates on a personal device, across rotating shifts, without desktop access. A platform that cannot reach them is not underperforming. It is architecturally blocked. The second explanation is procurement. An agency can conduct a thorough evaluation, build internal consensus, select the right platform, and then watch the acquisition process consume the fiscal year. That is not a technology problem. It is a channel problem, and it exists independently of how capable the selected platform is. ## What the Carahsoft channel actually changes Carahsoft Technology Corp. operates as The Trusted Government IT Solutions Provider® and serves as the Master Government Aggregator® for its vendor partners. The operational meaning of that positioning is contract vehicle access: federal, state, and local agencies can acquire MangoApps through GSA Schedules, NASPO ValuePoint cooperative purchasing programs, and other vehicles that procurement and legal teams already have active. For a state agency that completed its intranet evaluation in Q3 with Q4 budget available, contract vehicle access is the difference between deploying this fiscal year and restarting the contracting process in the next cycle. The timeline compression is not marginal. Carahsoft's reseller and systems integrator network also provides implementation support through vendor relationships agencies have already qualified — removing the build-from-scratch friction that constrains public sector IT teams already managing competing priorities. The partnership covers federal, state, and local government organizations, as well as education and healthcare markets. Agencies in any of these verticals can initiate acquisition through existing Carahsoft contract vehicles and connect with the MangoApps program team directly. ## The compliance baseline government IT teams require Government technology procurement runs through a specific checklist before any digital workplace platform advances to contracting. Security and IT teams require answers on SOC 2 compliance status, data protection in transit and at rest, access control architecture, and audit trail capabilities for policy acknowledgments and content delivery. MangoApps addresses these requirements as baseline platform capabilities. SOC 2 Type II compliance establishes independent third-party verification of security controls — the standard government procurement teams use to gate vendor selection. Role-based permissions allow agencies to control access by role, department, and location without custom access logic. Policy acknowledgments, content delivery events, and permission changes are captured in audit logs that are reviewable and exportable on demand. For agencies in regulated environments — federal departments handling sensitive constituent data, healthcare agencies operating under HIPAA requirements — platform consolidation reduces compliance surface area. One platform means one data agreement, one security review, and one audit trail, rather than separate reviews for the messaging tool, the scheduling system, the forms platform, and the document repository each running independently. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) evaluates MangoApps against competing platforms using the criteria enterprise buyers apply in formal procurement — security posture, feature depth, integration support, and total cost of ownership. Government IT teams building vendor comparison documentation will find the methodology aligned with how public sector assessments are structured. ## Reaching the government employees standard intranets miss An intranet that reaches only desk-based employees with corporate email is not a communication system — it is a communication system for a fraction of the workforce. For state transportation departments, county health agencies, federal facilities operations, and emergency services organizations, most employees are in the field, on rotating shifts, without desktop access. The six-minute daily usage average SWOOP Analytics documents captures how little engagement desktop-first platforms generate even for the desk-based employees they were designed for. For field employees, the effective number is zero. MangoApps supports mobile access from any personal device without a corporate email address or IT provisioning. A field inspector and a headquarters analyst operate in the same platform, with access to documents, announcements, and task assignments relevant to their role. A safety protocol update reaches every employee assigned to the relevant role — not just those who were at a desk that morning. Role-based content targeting handles the scale challenge distributed government agencies face. A state department of transportation managing engineers, field crews, administrative staff, and seasonal contractors cannot operate through a single undifferentiated information feed. Content, forms, and announcements reach each employee based on role and location without requiring navigation through material designed for a different part of the organization. Acknowledgment receipts generate a compliance record automatically — the documentation that regulated agencies need to demonstrate that a safety or compliance communication reached its intended recipients. For agencies building the internal case on employee retention as well as productivity, the [MangoApps 2026 Forrester Intranet Platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides independent analyst assessment of how unified platforms affect engagement outcomes alongside the security and feature criteria public sector evaluations prioritize. ## Making the internal procurement case Government IT teams building a procurement justification need to answer three questions their budget and acquisition stakeholders will ask: what does this cost, how long does deployment take, and what is the measurable return? The more substantive cost comparison belongs against current tool expenditure. Agencies operating separate email lists, a SharePoint deployment, a scheduling system, and printed communication channels for field workers are paying for four channels while achieving fragmented reach. Email license displacement for frontline workers without corporate email runs approximately $4 per user per month — $96,000 annually for a 2,000-person workforce before productivity gains are counted. The IDC figure of 2.5 daily hours lost to information search applies to every employee operating across fragmented tools. For a 1,000-person agency over a 250-day work year, that is 625,000 hours of recoverable operational capacity. For agencies with high-turnover field roles, frontline employee replacement costs run $4,400 to $15,000 per worker. A unified [workforce management](/solutions/workforce-management) platform that reaches every employee — field crews included — improves the day-to-day experience of working at that agency. That improvement has a documented effect on retention outcomes in high-turnover positions. The timeline question is where the Carahsoft channel changes the standard answer. Enterprise intranet deployments through custom procurement can add months between evaluation completion and deployment start. Contract vehicle access compresses that window. Implementation support through Carahsoft's existing reseller network shortens setup further for agencies that have previously worked with Carahsoft-distributed platforms. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how public-sector-adjacent organizations are structuring the internal procurement case for unified communication platforms, including the cost and timeline frameworks that perform best with budget and acquisition reviewers. ## What the partnership means for agencies ready to act The MangoApps and Carahsoft partnership addresses a structural problem in public sector technology adoption: a platform that meets government security requirements — SOC 2 Type II compliance, role-based access controls, full audit trails — and reaches deskless employees is now accessible through the contract vehicles agencies already use. The Carahsoft channel removes the procurement bottleneck that has historically separated a successful platform evaluation from an actual deployment. Agencies that have completed their evaluation can move through acquisition using contract vehicles already active in their procurement office, without the custom contracting process that delays government software adoption regardless of how strong the evaluation outcome was. Agencies ready to evaluate MangoApps can contact Carahsoft through existing contract vehicle relationships to connect with the MangoApps program team. For agencies still building internal justification, the combination of independent analyst assessment, established contract vehicle pricing, and the IDC cost basis creates a procurement argument built for the specific approval process government IT investments require. --- # How To Improve Retail Communication **Author:** Mason Hager **Published:** 2022-11-29 **Category:** company-collaboration Effective internal communication is essential in every industry, but it is especially important in a retail environment. More often than not, retail employees work without email, computers, desks, and other tools available to office employees. Their work requires them to spread out across the store, making it challenging to catch managers and ask questions. To […] # How to Improve Retail Communication — And Make the Business Case for It Replacing a frontline retail associate costs between $4,400 and $15,000. That range accounts for recruiting, onboarding, and the lost productivity during the gap — and it compounds when understaffing stretches remaining staff thin and accelerates the next departure. In most retail organizations, the primary driver of that turnover sits largely unaddressed: retail workers are structurally disconnected from the people and information they need to feel like part of the business they represent. This is a solvable infrastructure problem, not a culture mystery. The organizations that have solved it have done so by treating retail communication as a financial decision rather than a logistics inconvenience — and the outcomes they have seen are benchmarked and reproducible. --- ## Why retail workers are structurally cut off from their own organizations Emergence Capital estimates that 80% of the global workforce is deskless. Retail floor associates are the defining example: their work requires mobility, their shifts prevent regular all-hands meetings, and they are structurally excluded from the communication tools that office employees take for granted. According to IDC research, employees spend an average of 2.5 hours per day searching for information. For a desk worker, that inefficiency is frustrating. For a retail associate fielding a live customer question about a promotion, it is a customer-facing failure playing out in real time. Per Social Edge Consulting, 91% of organizations operate an intranet — but nearly a third of employees never log in, and only 13% use one daily. SWOOP Analytics benchmarks average intranet usage at six minutes per day. The tools are not failing because employees are disengaged. They are failing because the tools were designed for desk workers and deployed to everyone. The result is a communication pattern most retail managers recognize immediately: posted schedules, passed-along messages, shift-ending verbal updates, and policy changes that arrive after the situations they were meant to prevent. Corporate decisions take days to reach the floor. New hires complete onboarding and immediately lose access to the systems that trained them. --- ## The turnover math makes this a financial decision This is where most retail communication conversations miss the framing that actually moves operations and HR leaders to act. The decision to invest in a retail communication platform is not primarily about making employees feel more connected. It is about the $4,400 to $15,000 it costs every time an associate leaves and needs to be replaced. Retail turnover rates consistently run above 60% annually. For a 200-person store operation, that means replacing over 120 people a year — a replacement burden that compounds if the underlying causes go unaddressed. Those underlying causes are predictable: associates leave when they feel uninformed about decisions affecting their shifts, when their questions go unanswered for days, when they do not feel connected to the organization they represent. These are infrastructure failures, not personality problems. Organizations that have addressed those failures report concrete outcomes. According to MangoApps case study data, OU Health achieved 87% workforce engagement within the first few months of rolling out a unified mobile employee platform. PetSmart documented four times the engagement compared to the industry standard for deskless workforce tools. These are the leading indicators of the retention outcomes that show up in turnover data a quarter later. Per [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), employee engagement is the most reliable predictor of turnover, safety, and productivity across frontline industries — and it correlates directly with whether employees feel they have the information and tools to do their jobs well. --- ## Five infrastructure changes that move the needle The generic advice — communicate more, hold regular team meetings, build a feedback culture — is directionally correct but structurally insufficient for retail. You cannot hold all-staff meetings when your team works rotating shifts across three departments. You cannot communicate more when the infrastructure for reaching floor associates does not exist. The leverage is in getting the foundation right. **Mobile-first access without email or VPN** Most enterprise communication platforms require a corporate email address for login. Most retail associates do not have one. This is not a minor inconvenience — it is a wall that keeps floor staff on the other side of every system the organization deploys. The fix is a platform that authenticates by phone number or employee ID, requires no VPN, and runs on the personal device an associate already carries. This [employee app](/solutions/employee-app) model decouples communication access from corporate IT infrastructure entirely — and it is the access model that makes everything else on this list possible. **Push notifications and direct messaging for time-sensitive updates** Schedule changes, safety alerts, promotion launches, and policy updates share one characteristic: they need to reach floor staff before the shift begins, not after. Email threads and intranet posts fail here because retail workers do not check inboxes between customers. Push notifications to a mobile app — with SMS fallback for workers without smartphones — close this gap. [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) documents how leading retail operators have moved schedule management off bulletin boards and into direct-to-device delivery, eliminating the "I didn't know" failure mode that causes both operational errors and associate frustration. **Asynchronous channels for shift-based teams** Real-time meetings have a structural selection bias in retail: they favor whoever happens to be on the same shift. Asynchronous channels — persistent group feeds where questions, answers, and updates accumulate — let the opening shift leave context for the closing shift without requiring an overlap that scheduling will not allow. SWOOP Analytics benchmarks show six minutes per day of average intranet engagement. Asynchronous mobile channels designed for brief, contextual updates get meaningfully higher daily engagement because they fit the rhythm of shift-based work rather than fighting it. **Searchable information access for floor staff** Employees lose 2.5 hours per day searching for information, per IDC research. For retail associates answering customer questions in real time, that budget does not exist. A question about whether a product qualifies for a promotion needs an answer in 30 seconds, not after a manager consultation. Searchable knowledge bases — accessible on mobile, organized by topic, and updated centrally rather than maintained across disconnected spreadsheets — are the operational infrastructure that closes this gap. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading distributed workforce organizations are rebuilding information architecture around mobile-first search rather than document repositories. **Onboarding through the same platform associates use daily** Retail onboarding fails for a consistent reason: it introduces new employees to a process that disappears the moment training ends. The handbook from day one is not searchable. The manager who ran the onboarding week is not available for ongoing questions. The systems used during training often differ from the ones associates encounter on the floor. Onboarding delivered through a persistent mobile platform — the same one associates will use for schedules, team updates, and product information — eliminates that discontinuity. New hires enter the same information environment they will navigate for their entire tenure, which means the learning investment compounds rather than evaporating after week one. --- ## What to measure when evaluating whether it is working The wrong metrics are seductive: message volume, app installs, login counts. High activity does not confirm that the friction blocking retail workers has been removed. The signals that matter are more specific: time from a corporate announcement to floor-level confirmation; the percentage of associate customer questions that resolve without manager escalation; 90-day and 180-day retention rates for frontline hires. Engagement surveys that include specific items on information access and tool usability — not just general satisfaction scores — give operations and HR leaders a sharper read on whether the infrastructure is working. Organizations that tie communication investment to these outcomes, rather than adoption metrics, surface friction before it shows up in turnover data. --- ## The infrastructure argument The persistent mistake in retail communication improvement efforts is framing them as people programs. Telling a frontline associate to communicate better when they do not have access to the tools that make communication possible is the organizational equivalent of recommending effort as a substitute for equipment. The retail workers who are underserved are not failing to communicate. They are using whatever channels are available to them — shift handoffs, sticky notes, word-of-mouth from the manager who happened to be on that day. Those channels are unreliable by design. Replacing them with a mobile-first platform that delivers updates, enables two-way feedback, and provides searchable information access is not a culture initiative. It is an infrastructure decision with a calculable return: lower replacement costs, faster time-to-productivity for new hires, and engagement scores that predict the retention outcomes retail operations leaders are actually accountable for. The communication rut in retail breaks not because managers start holding better meetings. It breaks because the people on the floor finally have the same access to information and connection that everyone else in the organization takes for granted. --- # How To Improve Employee Productivity **Author:** Mason Hager **Published:** 2022-11-22 **Category:** workplace-productivity This article details out the benefits to improving employee productivity and provides actionable steps you can take to accomplish it. The customer is king, right?  Not exactly… that old business adage isn’t as relevant as it once was. Companies are finally realizing that while customers are extremely important, employees also deserve attention and respect. Your […] This article details out the benefits to improving employee productivity and provides actionable steps you can take to accomplish it. The customer is king, right?  Not exactly… that old business adage isn’t as relevant as it once was. Companies are finally realizing that while customers are extremely important, employees also deserve attention and respect. Your employees are the lifeblood of your business. It is critical that you connect with them and make them feel valued while providing them with the tools they need to work efficiently. In this article, we’ll tackle a variety of different ways that your company can improve employee productivity and optimize your business operations.  8 Strategies to Improve Employee Productivity #1: Provide a collaborative environment Teamwork can make or break company culture.  When done correctly, a successful team can be a beacon of stability within your organization and yield increased productivity and collaboration across employees.  But how do we empower teams with the tools to communicate and collaborate effectively on a daily basis? The answer? Digital workplace & collaboration tools. Organizations worldwide rely on collaboration tools and digital workspaces to ensure that their workforce can share knowledge and resources while providing employees a space to collaborate and communicate on critical projects. A digital workplace is a virtual platform that helps bring together the systems, people, and content within an organization. It focuses on equipping employees with the tools they need to collaborate and communicate effectively in a single digital space. Organizations that opt for digital workplace technology are generally seeking to unify employee communications, collaboration, engagement, content sharing, and training within their company. #2: Modern tools for productivity There are a handful of collaboration tools that will help improve employee productivity. These collaboration tools can help replace email, allow you to store resources in one place, and help employees quickly access what they need, when they need it. Below are two ways that collaboration tools can help improve employee productivity: Replace Email Email comes with many limitations. It’s difficult to keep track of information, conversations could be had that you’re not a part of, and it can lead to duplicate work. With an instant message tool, you can focus on providing employees a better employee experience by eliminating the drawbacks of using email for internal communications. In addition, organizations often don’t provide company associated email addresses to their frontline workforce. With an instant chat solution, you can empower employees to connect with their peers and communicate on job-critical tasks. Store resources and tools in one place By centralizing the resources and information within your organization to one place, you can ensure that employees can conveniently access the information they need quickly. When important resources are spread out across siloed tools, it can be quite challenging (and a massive waste of time) to retrieve it. A modern digital workplace will come with a unified search feature, which allows employees to simply search the name of the resource they’re trying to locate. Centralizing Employee Resources In this case study, learn how TCG, a fully-remote government contractor, used MangoApps to: Create a central repository of resources Track engagement and see which employees view content Bridge the gap between their workforce learn more #3: Invest in employee learning A workforce that isn’t constantly learning is a stagnant one. As you are aware, employee learning is a never-ending process. And as such, an environment of continuous learning must be established. This starts when an employee is onboarded. You need to assess your onboarding process and make sure that new hires are equipped with the tools and resources they need so that they can hit the ground running. It’s important that you are constantly educating your employees so that they can learn new skills, grow within their roles, and become even more valuable assets for your company. A proper Learning Management System will help you keep employees up to date with required training while offering courses and resources that can further their development. A strong LMS can be the difference between a frustrating learning experience and a career-defining moment for your employees. By providing your employees with learning programs and other educational opportunities, you can aid their professional growth and create a culture of learning within your workplace. #4: Recognition program Another way to improve employee productivity while also creating a positive work environment is by implementing an employee recognition program.  Whether you’re giving ‘kudos’ to a colleague, or celebrating a big team win, a good recognition program can improve company culture, boost employee morale, and create a space where employees can acknowledge each other’s milestones. Most organizations are all too eager to pounce on employees when something goes wrong but are far too lenient in their praise and appreciation. This culture needs to transition into a more supportive environment that understands your people will make mistakes and encourages celebrating outstanding performance. A positive company culture can be a driver of stronger collaboration and financial performance across teams, leading to improved productivity, efficiency, and business output.  #5: Gamification and rewards Gamification can be another great way to improve employee productivity. You can try incentivizing staff with rewards and workplace bonuses to encourage employee engagement and get people excited. Some benefits of gamification in the workplace include: Creating a workplace atmosphere of friendly competition Improved employee engagement and morale Quicker employee training Keeping new hires engaged during onboarding process Tracking and measuring employee learning progress #6: Improve work-life balance A healthy work-life balance can do wonders to improve employee productivity. Employees often prioritize work-life balance over their salary, when making career decisions. Employees have their own private lives, people that they care for, and responsibilities that they need to attend to. Because of these factors, it may not always be suitable to work in the office.  This creates an incredible demand for workplace flexibility.  Allowing remote work will boost employee productivity by allowing employees to work in conditions that are best suited to their needs. This, in turn, increases company loyalty and naturally encourages increased commitment. Did you know that 90% of employees report the same, or higher, productivity levels working from home compared to the office? Not only that, 55% of remote employees actually end up working longer hours than their counterparts, giving them an edge over their peers in terms of productivity. Get The Most Out of Your Remote Work Solution In this whitepaper, you’ll learn how you can: Drive productivity at scale Connect with 100% of your workforce Maintain organizational compliance Build a growth-oriented culture learn more #7: Good managerial practices Another way you can improve employee productivity is by practicing good managerial habits. When a manager isn’t clear on objectives/instructions, or they are micromanaging their employees’ work, it can directly lead to decreased employee productivity.  How a manager can improve employee productivity: Set clear communication policies Clear communication is the foundation of a healthy employee-employer relationship. Every department should have specific and effective communication policies in place for employee communication and team management.  Nothing lowers morale and discourages productivity quite like vague communication.  It’s the manager’s responsibility to ensure that organizational objectives, instructions, and expectations are understood by everyone.  Avoid micromanaging Micromanagement is incredibly paradoxical. The more you hover over an employee, the more disengaged they become. Give your employees the freedom they need to work and bring out their best. When you hire an employee, it’s a sign of trust that they can successfully do their job. Let them have a say in how they manage their workloads and strategies. Try working with them to define goals, objectives, and KPIs, and then let them accomplish their tasks in the way they best see fit.  Gain insight from KPI’s Use an employee’s Key Performance Indicator (KPI’s) as a learning and teaching tool, rather than as a blanket measurement of success. By using KPI’s, both employers and employees can get a better understanding of what areas need additional help/training.  When managers take the time to mentor employees through difficult areas, they can develop stronger relationships with everyone on their team. In addition, the insight you gain from KPI’s can boost employee productivity by helping managers get a better understanding of the needs of their team and by equipping employees with the tools and resources they need to learn any missing skills. #8: Weekly status updates For successful businesses, status meetings often become a necessary evil. While almost everyone agrees that meetings waste valuable time and energy, it’s impossible to stay productive without also being informed.  Collaboration tools allow companies to implement weekly status updates. This makes it easy to abandon time-consuming meetings without sacrificing the importance of staying up to speed. A few ways that weekly status updates can improve employee productivity: Strengthen existing meetings – Weekly status updates allow employees to post their progress, questions, and developments online to a shared company or team space. This gives leaders and coworkers the chance to read updates at their convenience and prepare answers ahead of time. While nothing will completely replace meetings, status updates make essential meetings faster, more focused, and more productive.  Improve team collaboration – Instead of trying to manage dozens of different schedules, employees can post, read, and respond to status updates whenever works for them. When employees have the freedom to work updates into their own schedule, thoughtful collaboration becomes easy, and never negatively impacts other responsibilities.  Maintain a written record – Weekly status reports are shared online, making them written rather than verbal communication. Unlike traditional status meetings, weekly status updates give everyone a tangible record to rely on. A written record also keeps goals visible, improves accountability, and simplifies idea sharing, helping everyone access important information. Filter out irrelevant updates – Employees rarely need to know everything shared at a status meeting. Different work roles, team projects, or areas of expertise often gather in status meetings to report their progress. But what’s essential to one project won’t matter to another team, leaving every employee at some point uninterested and unproductive. Instead of taking the time to hear irrelevant updates, online weekly status updates let employees filter information to find only what they need. Calculate Your Company’s ROI Want to learn some of the ROI you can receive when implementing MangoApps? In this whitepaper, we give a detailed ROI breakdown on a case-by-case basis. learn more Tool sprawl – a toxin to employee productivity When considering ways to improve employee productivity, one thing you should take note of is the resources and tools that your employees have at their disposal. A lot of the times companies will continually add new tools to the point where it actually ends up hindering productivity. This is known as tool sprawl. It almost always gradually creeps up on organizations regardless of their industry. At first, you’ll take on a new tool that solves a specific problem. Then your department designs an in-house program to address a unique need. When this starts happening over and over, a few simple solutions can spiral into an abundance of resources that can’t be managed. If left unchecked, tool sprawl remains one of the biggest time-sucks when it comes to employee productivity. From bouncing between tools, trying to remember logins, and locating a specific resource, it can prove detrimental to company productivity at every level. How tool sprawl hinders employee productivity Damages individual efforts – Tool sprawl slows down every aspect of the employee experience. With resources spread out across multiple platforms, it takes a ridiculous amount of time just to find, open, and navigate everything you need. With information everywhere, it can be almost impossible to track down past conversations, relocate shared files, or reference recent reports. Prevents team productivity – Tools sprawl does more than just mess with the individual work experience, it affects the collaborative environment as well. When information is scattered across different tools it becomes difficult for teams to gain insights and work well together. Without a simple way to share resources, express thoughts, and collaborate on ideas, work can never reach its full potential. Deters corporate achievement– Even when teams establish a successful system, tool sprawl still finds a way to negatively impact the corporate environment. Devising customized sharing methods seems like a solution until work has to be transferred to another department. Suddenly, trying to integrate the tools and tactics of dozens of different teams can create a real problem. Instead of a seamless handoff, transitions become tedious reconstruction tasks. Why You Should Avoid Tool Sprawl When you have too many tools and resources, you can actually hinder employee productivity. In this whitepaper, we go over why tool sprawl is a toxin to productivity and how you can avoid it. learn more Improve employee productivity with MangoApps All of these tools and resources can be impossible to navigate and is why we recommend implementing a modern digital workplace tool so that employees only have to go to one central place to access anything they might need to do their jobs. Unlike disorderly tool sprawl, MangoApps is an integrated employee platform, providing companies with a truly consolidated workspace. Our individual, team, and company centered features help organizations break down silos and find success at every stage. At MangoApps, we design tools to help companies create a successful work environment, encourage employee engagement and boost employee productivity. To learn more about how MangoApps can help you transform your workforce culture through technology, contact us or schedule a demo today. schedule demo --- # How To Communicate Effectively In The Workplace **Author:** Justina Kolb **Published:** 2022-11-14 **Category:** company-collaboration In all aspects of life, communication is key when it comes to success and happiness. But different situations and relationships require unique styles of communication. When ensuring morale is high and goals are met within your organization, knowing how to communicate effectively in the workplace is crucial. But how is effective communication produced and practiced? […] # How To Communicate Effectively In The Workplace Consider a healthcare system with 4,000 employees. Leadership sends a company-wide update about a new patient privacy policy. The corporate team reads it over their morning coffee. The IT department discusses it on Slack. The frontline nurses and medical technicians — who arguably need to know it most — never see it. Their shifts start before the intranet opens on their work desktops, and they don't have corporate email addresses. The message reaches 800 of the 4,000 people it was meant for. This is not a communication failure in the traditional sense. Leadership wrote a clear message and distributed it through official channels. The failure is structural: the organization built its communication infrastructure for the people who sit at desks, while 80% of the global workforce does not have one, according to Emergence Capital research. Effective workplace communication is not just about what you say or how you say it — it is about whether the infrastructure you have built actually reaches everyone it needs to. ## Why most workplace communication strategies reach only part of the workforce Organizations tend to conflate communication tools with communication reach. The logic runs: we have an intranet, a newsletter, and a messaging app — therefore, we communicate effectively. That assumption is almost always wrong. According to Social Edge Consulting research, 91% of organizations operate an intranet — but nearly a third of employees never log in, and only 13% use it daily. That means an organization publishing important announcements through its intranet is reaching, on a good day, about one in eight of its own employees. Add to this that employees spend an average of 2.5 hours per day searching for information they should already have, according to IDC benchmarks. That is not a productivity problem separate from communication — it is the communication problem. When information is fragmented across five tools, stored in two different intranets, or living in someone's inbox instead of a shared space, time spent searching is the direct cost of poor communication infrastructure. The implication is uncomfortable but important: adding more tools does not improve communication. In most organizations, tool sprawl is the cause of the problem, not the solution. The question is not which tool to add next — it is whether the tools you have actually reach your full workforce and whether they work together. ## The tools that move information across an organization — and the ones that do not Effective workplace communication requires a different mental model than most guides provide. Instead of thinking about which tools to deploy, think about which communication gaps each tool closes — and whether those gaps are currently making people less effective at their jobs. **Reaching the deskless majority.** For the frontline workers who make up 80% of the global workforce — retail associates, nurses, warehouse crews, distribution teams — communication that requires a desktop login or a corporate email address is communication that does not arrive. A mobile-first employee app changes the structural equation: push notifications reach people on the floor, not just at their desks; important policy updates land on a device employees already carry. For organizations where frontline access is the primary gap, the [MangoApps employee app](/solutions/employee-app) eliminates the VPN-and-corporate-email requirement that blocks most intranet tools from reaching deskless workers. Solving frontline access first means every other communication improvement compounds from there. **Reducing search time with a centralized knowledge hub.** The IDC figure — 2.5 hours per day spent searching — points directly at fragmented knowledge. When documents live across five systems, employees default to asking colleagues rather than finding answers themselves. A centralized intranet, actively maintained and searchable, eliminates the search tax. According to SWOOP Analytics benchmarks, employees spend an average of just six minutes per day in intranet tools — meaning each minute needs to be productive, or the habit disappears entirely. An intranet that is ungoverned and out of date often performs worse than no intranet because it actively misleads employees who trust what they find. **Creating two-way channels, not just broadcasts.** Most organizations treat internal communication as one-directional: leadership publishes, employees receive. The organizations with the strongest communication cultures add structured feedback mechanisms — regular surveys with short response windows and visible follow-through. The critical discipline is closing the loop: employees who complete surveys and never see a response become systematically less likely to participate. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) examines how organizations that build real feedback loops see measurable improvements in engagement scores within two reporting cycles. **AI-driven targeting for relevance at scale.** A communication that reaches everyone but is relevant to no one is noise. Shift workers in Austin do not need parking garage updates for the Chicago office. Clinical staff do not need IT security briefings formatted for software engineers. AI-powered platforms now route content by role, location, team, and shift pattern — without manual segmentation by communications teams. This is the gap that static newsletters and untargeted intranet posts cannot close: relevance at the individual level, delivered automatically. ## What separates communication from information transmission There is a distinction most workplace communication guides collapse: the difference between transmitting information and actually communicating. Transmission is one-way — a newsletter goes out, a policy gets published, a town hall gets recorded. Communication is bidirectional — someone receives information, understands it, and can act on it or respond. Most organizations have built excellent transmission infrastructure. What they typically lack is a clear signal for what is actionable versus informational, a place to ask questions that surfaces answers for everyone rather than just the person who asked, and confidence that raising a concern will reach someone with authority to act on it. Manager communication is often the highest-leverage variable here, and it is the one most organizations leave to individual style. When managers are equipped with consistent talking points translated for their team's context, and given clear cadences for one-on-ones and standups, the formal communication infrastructure does not have to carry all the weight. According to [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), the direct manager relationship is a top-three differentiator between high- and low-engagement organizations — even in companies with sophisticated intranet and messaging platforms. ## How to know if workplace communication is actually working Most organizations measure communication reach — newsletter open rates, intranet page views — but not communication effectiveness. The useful question is not "how many people saw this?" but "do people have the information they need to do their jobs today?" Four signals that communication is working: **Fewer repeated questions.** When the same questions appear repeatedly in team meetings or helpdesk tickets, it signals the authoritative answer is not findable. Track the top questions employees ask in a given month; if any appear three months in a row, the communication infrastructure has a gap at that location. **Shorter new-hire ramp time.** New employees arrive without organizational knowledge. How long it takes them to become independently effective is a direct proxy for how well-documented and accessible that knowledge actually is. **Survey participation rate and trend direction.** Declining participation in engagement surveys is not primarily a survey design problem — it signals that employees do not believe their input will be acted on. That perception is almost always accurate. **Manager satisfaction with information access.** Frontline managers who feel they receive information late, or who have to advocate for their teams to get answers, are experiencing a communication failure upstream. They are often the most reliable early indicator of systemic gaps. For organizations moving from ad-hoc measurement to a structured approach, [MangoApps employee communications](/solutions/employee-communications) provides both the delivery infrastructure and the analytics to track these signals over time. ## The structural move most organizations defer too long Every organization eventually reaches the point where the tool stack becomes its own obstacle. Messages go through email, announcements through the intranet, team communication through three different messaging apps, and documents scattered across two cloud drives — with no single place where an employee can reliably find what they need. Consolidation is the structural move most organizations defer because it requires a governance decision rather than a software purchase. But the cost of deferral compounds: each additional tool added to a fragmented stack raises the search cost for every employee, every day. Effective workplace communication at scale requires fewer tools used consistently — not more tools used occasionally. The organizations that close the gap between what leadership intends to communicate and what frontline employees actually receive are almost always the ones that made consolidation a deliberate decision, rather than letting the stack accumulate by default. That decision starts with a clear diagnostic: do the communication tools you have today actually reach every person who needs to receive information — including the 80% who do not sit at desks? If the answer is no, redesigning the intranet homepage or adding a newsletter will not close the gap. The structure needs to change first. --- # Tips For Writing Perfect Internal Email Subject Lines **Author:** Justina Kolb **Published:** 2022-11-07 **Category:** best-practices Internal email is essential for any organization. Keeping employees informed and showing appreciation creates a sense of community within your company. And sending an internal email is the most reliable way to share these sentiments with an entire workforce.  Unfortunately, internal communication efforts often go unnoticed, hindering your attempts at connecting your brand and its […] Internal email is essential for any organization. Keeping employees informed and showing appreciation creates a sense of community within your company. And sending an internal email is the most reliable way to share these sentiments with an entire workforce.  Unfortunately, internal communication efforts often go unnoticed, hindering your attempts at connecting your brand and its employees. It also means that someone’s hard work that went into drafting, designing, and scheduling internal emails was fruitless.  So how do you create an internal email that will surely be seen?  Subject lines!  With a catchy subject line, your internal emails will stand out in a flooded inbox and pique your reader’s curiosity, leading to more opens.  In this article, we’ll go over internal email basics, as well as tips and examples for writing perfect internal email subject lines. Characteristics of Internal Email Internal email refers to the modern business practice of sending long-form messages to staff, conveying a variety of information. Communications regarding the following subjects are regularly sent via internal email:  Employee Newsletters Event Invites  Leadership Messages Employee Recognition & Appreciation Shoutouts Change Management Communications Project Status Updates Health & Safety Guidelines Diversity & Inclusion Efforts Policy Changes Holidays & Office Closures Meeting Requests Wellness Endeavors And more! Strengthen Internal Communication Learn how Great Harvest uses MangoApps to: Allow store members to share knowledge, ideas, and information Centralize resources and information in an easily searchable hub Build a strong employee recognition program by offering incentives and kudos learn more No matter the topic, internal emails are traditionally comprised of the same components: a greeting, opening or headline, body, closing, signature, and – most importantly – a subject line. Greeting Quite simply, including a greeting in your internal emails is the polite thing to do. Try coming across as affable while staying professional – knowing your brand’s voice and sticking to what is appropriate for your organization is essential.  Often, when reaching folks outside of your own team or department, it’s common to sway towards a formal tone and remain more casual when communicating with closer colleagues. Opening Use the opening of your internal email to introduce the gist of the message. This space should answer your reader’s question, “Why am I receiving this email?” Condense the meat of your memo without going into too much detail. This is an especially helpful portion of the email for senior management, who may not necessarily need the finer details. Body The body of your internal email should be concise and to the point. Most people skim or read just half an email, so keep your audience in mind to ensure they stay engaged. It’s also essential to convey your message in a way that offers the lowest chance of confusion. Mind your sentence structure and use bulleted lists if your copy is becoming too long or difficult to read.  Sometimes, it might be more effective to include information as an attachment. Establish whether the facts and background information you need to share is important enough for your email’s body or if they would be better suited as downloadable documents. Closing Use the closing of your internal email to reiterate why your message is important. Include a call to action & dates – what do you want your readers to do, and when should they do it? Signature Your signature should include your full name, position in the company, and extension number. Include a sign-off that matches the tone or occasion of your email. Subject Line You’ve completed the bulk of your internal email, but don’t click “send” without including a subject line! Without one, readers don’t know why you’ve sent a message or what it’s about.  Your subject lines should be succinct in summarizing the contents of your email while enticing the recipient to read more. In fact, over 30% of recipients decide to open an email based solely on the subject line, so including one—and making it stand out—is key. What Makes a Catchy Subject Line? There are several aspects to creating a catchy subject line for your internal emails. From personalization to emojis, here are seven things to consider when writing catchy internal email subject lines.  #1. Length  These days, it’s extremely common to check one’s email on a mobile device. Subject title length is crucial when it comes to gaining readers’ attention, especially when most of them use their phones. Ideally, your subject line should be no more than seven words or 42 characters. The entire line should easily fit across a phone screen. #2. CTA’s Include a call to action, or CTA, to engage your audience. “Read more,” “click here,” and “act now” are classic marketing CTA’s. Adapt terms like these to relate to your internal email readers. #3. Personalization Exclusivity is a huge selling point in any industry – why not apply it to your internal emails? After all, you are essentially selling your company’s communications via internal email. One way to create the feeling of exclusivity is to personalize your subject lines.  Use people’s names in subject lines to surprise your readers and make them feel special. No one gets excited about opening mass messages, but everyone enjoys opening mail just for them. In fact, email subject lines that include the recipient’s name  increase open rates up to 50%. Even mentioning a specific team or department, rather than a person’s name, can boost engagement. #4. Verbs & Adjectives Like any writing, action verbs and sensory descriptors make for an exciting read. Paint a (brief) picture in your subject line with action and details to intrigue your recipients. #5. Familiarity Keep familiarity in mind when crafting your internal emails; sticking to a consistent look and tone for your company correspondence reinforces your brand voice and keeps your emails from blending in with others. Do you send out weekly, monthly, or quarterly newsletters? Giving these regularly scheduled messages a recognizable subject line lets readers quickly become familiar with your routine content; they’ll learn to expect these messages and know not to miss them. #6. Emoji What better way to save space and invoke feelings than emoji? Emoji can represent a whole word with just one character, allowing for short, concise subject lines. They also help an email stand out in a flooded inbox.  Most importantly, emojis are just fun! And one reason internal emails don’t get opened is that they aren’t very fun. As long as you use emojis that relate to the message, you’ll likely see the open rate of your internal emails go up. #7. Video Obviously, including an actual video in your subject line is impossible. But including the word “video” is entirely doable (as long as the message does, in fact, include a video)! When sharing information via video in an internal email, say so in the subject line. This lets recipients know they have fast access to important information without having to read through an extensive email.  We’ve seen updates via video become commonplace on social media; while we once read through blogs and status updates, photo sharing eventually took over, with video posts now being the new norm. Video updates via your internal emails may become the new norm, too, so be sure to let your audience know. Subject Line Examples Now that we have some best practices in place, let’s work on some subject line examples for internal emails. To start, we’ll improve on this subject line: New office policies. As you can see, this subject line example lacks any intriguing element listed above, apart from being extremely short & concise. Upon seeing this, the reader is unaware that the message specifically relates to them. There’s also nothing in this subject line to conjure excitement or curiosity. Get accustomed to fresh marketing department changes.  In this example, the action words “get accustomed” lead readers to open the message. By specifying what department the policies, or “changes,” relate to, it’s evident to the reader who this message is meant for. Additionally, the replacement of “new” and “policies” with “fresh” and “changes” paints a more positive, buzz-worthy picture. Diana, have you seen these marketing updates😮? Here, we’ve included the personalization of “Diana” and an emoji to add a sense of surprise and urgency to this subject line example. This subject line is intriguing, as the message could lean two ways: either the sender is excited by the marketing updates and can’t wait to share them, or the sender is concerned about the marketing updates and wants to know if Diana feels the same. Ultimately, the only way Diana can satisfy her curiosity is to open the email. Just be sure to use dramatic headlines like this solely if it relates to the message. If Diana opens the email and there’s no mention of marketing updates, it’s clickbait. Here are a few more catchy subject lines for internal emails: Read All About It!🗞️ Company News – November ‘22 (Employee Newsletters) Start your subject line with an exclamation and emoji to capture the reader’s attention Reuse this format each month to create familiarity  Replace “company” with the name of your organization for faster recognition from readers You’re Invited – Company Picnic Details Inside! (Event Invites) “You’re Invited” elicits exclusivity  “Details Inside” means the recipient must read the email to find the date & time of the picnic before they can fit it into their schedule Diana, We Want To Say Thanks🖤 (Employee Recognition & Appreciation Shoutouts) Everyone enjoys getting a shoutout; including personalization adds sincerity to the message Emojis help convey feelings; try using emojis in your company logo’s colors to match your brand’s look Stay Safe! Covid-19 Protocols You Need To Know (Health & Safety Guidelines) “Stay safe” shows emotion and concern “You need to know” informs the reader that the details within will affect them Diana, *Step Up* To The Challenge👟 (Company-wide Wellness Endeavor) In this example, the sender is setting up a company-wide step challenge and adds a related emoji to hint at message details Use puns or jokes to evoke curiosity Don’t Miss This Video Message From Our CEO! 📺(Leadership Messages) “Don’t miss” creates a sense of urgency  Including the word “video” lets readers know the bulk of the email won’t be text Build a Connected Workforce Learn how PROBIOMED uses MangoApps to: Transform internal communications across distributed employees Consolidate their tech stack Improve company culture and employee engagement learn more MangoApps’ Campaigns Now that you know how to create engaging internal email subject lines, you might feel overwhelmed by the thought of sending the actual messages. Dividing recipients into segmented groups, creating a visually appealing design, scheduling them in advance, and figuring out how to analyze your email’s performance are a few aspects that can be daunting. Luckily, MangoApps’ Campaigns feature has all that covered. Take a brief look at its key components below:  Advanced targeting ensures your internal emails reach the relevant audience, decreasing cumbersome communications that often overflow inboxes.  Multiple delivery channels allow you to reach every employee in a format that suits them best – email, mobile app notification, or SMS text.  Personalization gives messages a customized, exclusive feel, which boosts engagement. Robust insights give you the ability to track your campaign’s metrics so you can make adjustments and gradually improve open/click rates.  Templates make your internal messages look clean and polished while adding to your brand’s aesthetic – no design or HTML expertise required. Using Campaigns from MangoApps as your internal email automation tool makes reaching your entire workforce easy, especially in practice with our email subject line tips. Check out our blog post all about MangoApps’ Campaign feature here to learn more! --- # What is a Modern Intranet? **Author:** Mason Hager **Published:** 2022-11-03 **Category:** intranet This article is meant to serve as a comprehensive guide for everything you need to know about a modern intranet. Jump to a topic: Traditional vs modern intranet Over the past decade, we have seen a workplace evolution take place. Companies areno longer satisfied with their outdated traditional intranet platforms. Traditional intranets, although once highly […] This article is meant to serve as a comprehensive guide for everything you need to know about a modern intranet. Jump to a topic: Traditional vs modern intranet What is a modern intranet? Benefits of a modern intranet What features should a modern intranet include? How an intranet can improve employee experience Why SharePoint is not a modern intranet How to build an intranet Traditional vs modern intranet Over the past decade, we have seen a workplace evolution take place. Companies areno longer satisfied with their outdated traditional intranet platforms. Traditional intranets, although once highly innovative, simply didn’t adapt well to the modern working world. Traditional intranets lack mobile capabilities, navigation, and social features that the modern workforce desires. Ultimately, this leads to a poor user experience. As a result of these limitations, companies relied on third-party tools to fill the gaps. However, this temporary fix has led to a whole other slew of problems, one being tool sprawl.  The demand for a solution to these piling problems was clear, leading to the creation of a modern intranet. What is a modern intranet? A modern intranet centralizes all the resources, tools, and information your employees need. It also provides strong collaboration and communication tools to connect your workforce. When set up effectively, it can act as your organization’s central hub for company information and news.  Unlike its predecessor, a modern intranet allows information to become searchable. Employees are then able to find the resources they need, with an individually tailored experience. It also allows employees to communicate and collaborate effectively with built-in collaboration spaces and strong social features. For more information, learn more about the modern intranet solution by MangoApps. Benefits of a modern intranet Modern digital tools and intranet accessibility have dramatically changed how businesses operate and how employees within communicate. With a modern intranet, you can take steps to improve communication, collaboration, culture, and engagement within your company. Now, let’s dive into a few of the benefits that you can expect to see from implementing a modern intranet. 1. Centralize company information & resources To find a specific resource, your employees have to spend a lot of time combing through email threads and jumping across tools. With a modern intranet, information, tools, and resources are stored in a centralized space. Thus, employees can quickly find what they are looking for.  To make it even easier, most modern intranet platforms will include search functionality. This can contribute to massive time savings and will boost the productivity and efficiency of your workforce. 2. Reach employees with comms Email is not effective. Successful organizations know that emails are easy to miss, difficult to navigate, and overall, just a messy experience. A modern intranet will allow you to deliver targeted communications to your employees on the channels they prefer. Rather than sending out mass emails or phoning employees individually, you can send content that is tailored to each employee. This helps executives make sure that their messages are being read, since their is less noise to cut through. 3. Foster collaboration across teams Your employees can only do their best work when they have a clear agenda and instant access to the tools and information they need. With a modern intranet, you can make employee collaboration seamless and ensure projects get across the finish line. Here are a few ways that a modern intranet helps improve collaboration: Keep projects on track Turn discussions into actionable tasks Get employees on the same page Share important knowledge and information Communicate in project workspaces to accomplish specific goals 4. Boost engagement & build community With a strong social component, a modern intranet allows employees to connect with colleagues they haven’t met. Because of this, a modern intranet helps employees forge social connections at work. This can lead to increased employee engagement and a boost in employee productivity. By meeting and interacting with colleagues outside of your immediate team, especially in a dispersed work environment, you can bridge the gap across employees and help create a sense of connectedness. Here are a few ways you can leverage a modern intranet to boost employee engagement: Gather employee feedback with surveys Give shout-outs to star performers Use recognition and rewards to boost performance Celebrate important milestones Comment on discussion threads, add emoji reactions, and use hashtags Use employee profiles to learn more about colleagues 5. Improve work processes With better connectivity, a modern intranet can help your organization improve work processes. Ultimately, this cuts down on wasted time and improves productivity from your employees. A few ways that a modern intranet can help improve work processes: Allow employees to connect from anywhere Create a centralized ‘one-stop-shop’ for employee resources, accessible via SSO Use search functionality to quickly locate resources Comment/respond/react on discussion threads rather than try to locate and respond to specific emails Automate workflows, forms, and manual processes What features should a modern intranet include? Now that you’ve learned about modern intranet benefits, let’s go over a few of the most important features. 1. Universal Dashboard With a universal dashboard, employees can establish a quick overview of everything they need all from one location. A modern intranet will provide customizable dashboards so your employees can configure or customize their own dashboard however they please.Examples of how employees can use their dashboard:  Share important announcements company-wide and in real time Review, receive, and respond to the important company news Set up quick links to regularly used third-party applications By providing your employees with a customizable dashboard, they are able to configure it to best accommodate their job responsibilities. This can go a long way in improving productivity and employee engagement.  2. Team Workspaces With team workspaces you can get projects across the finish line quickly and ensure that nothing falls through the cracks. Employees are able to seamlessly collaborate. By having a clear understanding of what their peers are working on, they become more efficient.  Why your employees will love team workspaces: They are able to stay on the same page with their team members They can quickly distribute and oversee action items and tasks Improve sense of community among groups of colleagues They can view a team calendar that clearly details the availability of colleagues 3. Mobile App Today’s employees no longer work stagnant 9-5 jobs entirely out of office chairs. Our modern workforce is remote and on the go. It is critical that your company’s intranet reflects this as well. A mobile app offers unfettered access to company resources and conversations. It also allows employees to stay connected from wherever they are.  A mobile intranet offers convenience, but more importantly, it offers inclusion to frontline employees.  With a mobile app, you can begin bridging the communication gap between your frontline and desk employees. This improved access creates a space for every employee to be happy and successful at work. 4. Content Management System  A Content Management System (CMS) provides a secure, central space for employees to access company resources.   Rather than disrupting their workday trying to locate a resource, your employees can quickly find what they need. This improves productivity and employee engagement as they are no longer occupied with what was once a time-consuming task. Read more about the features your modern intranet should include. Switch To A Modern Intranet Learn about the benefits of switching to a modern intranet, and why it’s never too late to start building a better digital workplace. Get your free eBook today! learn more How a modern intranet can improve employee experience Equipping employees with the tools they need to do their job is at the forefront of every business leader’s mind. A modern intranet yields many intangible benefits that are difficult to measure but have a dramatic impact on organizational success. In addition to better communication, increased productivity, cost-savings, and more, a modern intranet can also improve your overall employee experience.  Below we discuss a few ways that a modern intranet can improve employee experience at your company. Improve productivity With a centralized space for communication and collaboration, employees no longer need to resort to sifting across third-party tools to find what they need. Instead, they are granted access to a ‘one stop shop’ for everything they need to do their jobs. A modern intranet allows them to optimize efficiency, improve productivity, and save time by finding things quickly. In addition, typical modern intranets include a mobile app, allowing employees to respond and collaborate from anywhere. Give every employee a voice Employee engagement is a focus for every organization. You want your employees to feel valued, involved, and fully invested in the organization.  A modern intranet ensures that everyone on your team has a chance to contribute and be heard.  Some features that can assist with this effort are employee surveys, employee recognition, team/department workspaces, and more. Create a workplace community Company culture can play a massive role in employee retention and overall job satisfaction.  A modern intranet provides colleagues with a social space to engage, communicate, and collaborate with each other. You can connect with people that you don’t normally interact with due to distance or work schedule. In doing this, you can create an environment where employees are aligned, working together to achieve a common goal.  Build company ambassadors Your employees are the faces of the organization. It’s critical to create a positive work environment where they can succeed and are satisfied with their daily work. Over time, these employees can become company ambassadors and represent public advocates for your brand. A modern intranet equips you with the tools you need to create a positive workplace environment. It provides a collaborative space where colleagues interact more and everyone understand how they contribute to the company vision. Kelly-Moore Paints Case Study Learn how Kelly-Moore Paints: Improved employee efficiency Increased the level of communication between employees Encouraged a cohesive and inclusive company culture learn more Why SharePoint is not a modern intranet Although SharePoint has some features of a modern intranet, it is limited in many aspects. It does not offer a unified employee experience in the same way that a modern intranet does. The main purpose SharePoint serves is as a content management system for files and records. If your organization wants functionalities beyond that, it will require heavy investment and custom development. A modern intranet isn’t just a repository for documents and resources. It’s a mobile-first employee communications and engagement platform. Here are a few reasons SharePoint is not a modern intranet, and you should consider other vendors. SharePoint is difficult to use SharePoint historically has had low employee adoption rates. This is due to it being difficult to use for end-users and difficult to manage for administrators. Did you know? Up to 72% of SharePoint implementations fail to meet their desired goal and are abandoned. SharePoint was ultimately created as a platform to store and manage documents and files. The rest of the platform was not built to provide a centralized employee experience. This leads to low adoption and a poor user experience. Deskless employees don’t have access Another reason why you should avoid SharePoint is that only desk workers can use it effectively. More often than not, only office workers will have 0365 licenses, and frontline/deskless employees don’t. This means that you will be deploying a limited intranet that only connects some of your staff. As such, you’ll have to make heavy investments elsewhere to get additional licenses and software. A modern intranet provides a seamless employee experience for ALL of your organization’s workers. Employees can connect from anywhere, at any time, and are not confined to the physical limitations of their desk. Limited features SharePoint was built as a content management system designed for storing documents. As a result, it lacks many of the elements that are needed for an employee-centric intranet. Some of the limitations of SharePoint features include: Poor employee experience Lacks personalization & filtering Doesn’t work well on mobile Poor multi-channel communication Limited content governance capabilities Doesn’t allow for audience segmenting and targeting Doesn’t offer deep analytics & insights In addition to all these limitations, SharePoint also comes with a very slow deployment process and requires a heavy IT investment. Learn more about the limitations of SharePoint View this whitepaper to learn more about the limitations of SharePoint, and how a modern intranet platform might be a better fit for your organization’s needs. learn more How to build an intranet A great intranet platform gives employees all the tools and resources they need to collaborate and be productive. To accomplish that, you first have to select an intranet vendor that will set your employees up for future success. Doing this can seem quite daunting, so we have laid out a detailed 10-step process that covers everything you need to know about intranet best practices. Additional Resources For more information related to modern intranets, read our list of questions to ask in an intranet demo, ways to boost intranet engagement, see some great intranet design examples, or read case studies from our customers TeamHealth, symplr, and Great Harvest Bread. --- # Your Complete Guide to Employee Advocacy on Social Media **Author:** Justina Kolb **Published:** 2022-10-25 **Category:** employee-engagement Employee advocacy is a valuable tool. It increases employee engagement and helps your brand maintain a positive image. Rather than trusting celebrities or influencers to promote your company, why not trust your employees in that role? After all, they know and understand your organization better than anyone. And, more often than not, they want your […] # Your Complete Guide to Employee Advocacy on Social Media Most employee advocacy programs are built around an assumption they never state explicitly: that the people doing the sharing have a corporate email address, a desk, and uninterrupted access to whatever system holds the shareable content. That assumption is wrong for the majority of the global workforce. Per Emergence Capital, 80% of the global workforce is deskless — employed in retail, healthcare, warehousing, field services, and other environments where there is no laptop, no company inbox, and often no VPN access at all. When advocacy programs require employees to log in to a browser-based portal to locate shareable content, they've already excluded most of the people they were designed to include. The program launches, a fraction of desk-based employees participate, and leadership concludes the workforce isn't interested. The actual problem was infrastructure, not interest. This guide covers what employee advocacy on social media is, why it generates measurable business returns, and — critically — how to build a program that reaches every employee, not just the ones who work at a desk. ## Why advocacy programs accidentally exclude most of the workforce The failure mode follows a predictable sequence: an intranet post goes up with a "share this" prompt, the employees with corporate email see it, a fraction engage, and the program plateaus. The structural issue is access and friction. Per IDC, employees already spend 2.5 hours per day searching for information. An advocacy task that requires navigating to a separate system, locating the right post, and then switching to a social app isn't a low-friction ask — it's a new job embedded inside the existing one. The programs that sustain participation reduce the sharing surface to near zero effort: content delivered where employees already are, formatted for the platform they're already using, on the device already in their pocket. For frontline and deskless workers, that means mobile-native. Not a mobile-responsive intranet — a native app experience that works without corporate credentials, doesn't require a VPN, and is accessible on a personal device during a break or after a shift. The difference between those two things isn't cosmetic. It's the difference between a program that includes 20% of your workforce and one that includes all of it. This infrastructure gap is why competitor platforms with strong frontline reach outperform generic advocacy tools in deskless-heavy industries. The question isn't whether an advocacy program exists — it's whether the mechanism for sharing is built for the workers you actually employ. ## What employee advocacy on social media actually does Employee advocacy is the backing of a company by its workforce: employees sharing company content, communicating positive work experiences, and recommending your products and services through their personal networks. Social media is where that advocacy generates the most leverage. Per Social Media Today, posts shared by employees rather than official brand accounts generate 800 times more engagement. Per Adweek, 76% of people are more likely to trust content from an average person than from a brand channel or its leadership — and the same research shows that over three-quarters of that group will make a purchase after receiving a recommendation from a friend or family member. The trust asymmetry is the central dynamic in employee advocacy, and it's not something money can manufacture. Brand advertising earns attention. Employee advocacy earns credibility. Credibility converts because it travels through relationships — and relationships are something no ad budget can replicate. The practical implication: the volume of employee shares matters less than the authenticity of the content. A hundred posts that sound like press releases will underperform a dozen posts where employees write in their own voice about why they actually like working somewhere. ## The retention case that most programs miss Most advocacy programs are positioned as brand awareness tools. The retention angle is real but chronically underused. Replacing a frontline employee costs between $4,400 and $15,000 in recruiting, training, and lost productivity per position. An advocacy program that deepens employees' sense of ownership over the company's public identity directly affects those numbers. Employees who see themselves as visible stakeholders in their organization's reputation are more likely to stay — the act of sharing builds identity investment, not the other way around. Per [Gallup's 2026 research on global workplace engagement](/articles/gallup-2026-state-of-the-global-workplace), the employees most likely to disengage and exit are those with the weakest sense of connection to their organization's broader mission and public presence. That's precisely the gap a well-designed advocacy program addresses — not by adding a task, but by giving employees a reason to feel publicly affiliated with their employer. The ROI math changes significantly when advocacy is measured against both brand reach and retention cost, not just impressions. ## Building the participation architecture Participation in advocacy programs can't be mandated, won't happen by default, and is almost entirely predicted by friction. Build the infrastructure to reduce friction, and participation follows without requiring constant re-solicitation. **Mobile-native access for the deskless majority.** There is a meaningful difference between a mobile-accessible intranet and a mobile-native advocacy tool. A post in a browser-based portal that loads on a phone is not the same as content delivered through a branded mobile notification with a one-tap share flow directly to LinkedIn or Instagram. For organizations with substantial frontline workforces — retail, hospitality, healthcare, logistics — this distinction determines who the advocacy program actually reaches. If the sharing mechanism requires a credential most of your workers don't have, the program is deskless in name only. **Brand guidance, not brand control.** Employees who feel scripted won't post — or they'll post once, receive minimal engagement because the content sounds like a press release, and stop. The goal of brand guidelines is to establish guardrails: which topics are off-limits, how to handle incoming comments, what language to avoid. Within those guardrails, employees should express themselves in their own voice. Personalized posts that reflect authentic perspective consistently outperform verbatim brand copy. The guidance should free employees to post, not constrain them into a format that feels institutional. **Incentives tied to professional identity, not just participation.** Recognition programs and monetary rewards drive short-term engagement. The programs with durable participation rates connect advocacy to something employees already want for themselves: professional visibility, thought leadership, and a stronger industry network. Employees who build an audience while advocating for their employer develop an ongoing personal reason to continue posting — the incentive becomes self-sustaining rather than dependent on the next reward cycle. **Training as an enabler, not a prerequisite.** Social media fluency varies significantly across any workforce. Offering training as a resource for employees who want to participate but feel uncertain — rather than requiring it of everyone before they can join — respects that some workers are already comfortable on social platforms and don't need onboarding. Make the support available; don't make it mandatory. **Content curation that removes the search burden.** The IDC finding that employees spend 2.5 hours per day searching for information applies directly to advocacy: if employees have to hunt for shareable content, most won't bother. The programs that generate the most sustained sharing are ones where curated, pre-approved content surfaces automatically based on role, location, or department — so the question shifts from "where do I find something to share?" to "which of these three things should I post today?" ## What to measure and when Three metrics determine whether an advocacy program is working — and all three should be baselined before launch, not reconstructed after. **Organic reach** — the number of people who see company content through employee shares, without paid amplification — sets the upper bound of the program's visibility. Tracking this weekly in the first 90 days establishes what normal looks like and reveals whether the audience is growing. **Organic engagement** — likes, comments, shares, and saves on employees' posts — tells you which content types employees are willing to put their name next to and which ones earn no visible response. Posts that consistently generate no engagement are diagnostic: either the content isn't worth sharing, the sharing experience has too much friction, or the content isn't reaching employees at all. Engagement patterns over time are more actionable than any single post's performance. **Referral attribution** closes the loop between advocacy activity and tangible recruiting outcomes. When employees share job postings or culture content, some portion of applicants will arrive through those channels. Tracking the source of incoming candidates validates advocacy's contribution to the recruiting pipeline — not just to brand sentiment — and makes the ROI case for sustaining the investment. For a broader view of how employee engagement metrics are shifting across industries, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how organizations are integrating advocacy outcomes into their overall communications measurement strategy. ## Three questions to answer before launch **Who has access to the sharing tools?** Map your workforce by role type — desk-based, deskless, and mixed. Then verify that your advocacy infrastructure reaches each group without requiring a device, credential, or account type they don't have. If the honest answer is "only desk-based employees," the program's architecture needs to change before launch, not after the first 60 days of underwhelming numbers. **What is your content production capacity?** Advocacy programs stall when the content pipeline runs out. Define the cadence — how many posts per week, who creates them, what the review and approval process looks like — before going live. Launching with momentum and going quiet within two months is more damaging to participation than not launching at all; it signals to employees that the program wasn't a real commitment. **What does a meaningful outcome look like at 90 days?** Establish baselines for organic reach, engagement rate, and referral attribution before the program starts. At 90 days, the useful question is not adoption — it's lift. Did reach grow? Did referral applicant quality improve? Did employees who participated score higher on your next engagement survey? The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how organizations are setting measurable outcomes for [employee engagement](/solutions/employee-engagement) programs across mixed desk and deskless workforce environments — including which baselines to establish first. ## What separates programs that last The advocacy programs with durable participation share two characteristics: they reach the deskless majority, and they reduce sharing to the path of least resistance. Both are infrastructure decisions made before the first post goes live — which is precisely where most programs get it wrong. The programs that plateau aren't failing because employees don't want to advocate. They're failing because the infrastructure was designed for the 20% with a desk, the content was formatted for a portal instead of a phone, and the friction of participating exceeded the motivation to participate. Building those foundations correctly is what separates an advocacy program that becomes a self-sustaining channel from one that requires quarterly relaunch energy to survive. The deskless majority is already on social media. The only question is whether the program you build is designed to include them. --- # 16 Intranet Design Examples to Inspire Your Work Hub **Author:** Justina Kolb **Published:** 2022-10-17 **Category:** intranet Intranets come in all shapes and sizes. Choosing what style works best for your company can be daunting. How do you know what information to include, what features will engage your employees, and what intranet solution will be easy to implement and maintain? These intranet design examples will give you some inspiration and ideas. Before […] # 16 Intranet Design Examples to Inspire Your Work Hub ## The adoption problem hiding in plain sight IDC research puts employee time spent searching for information at 2.5 hours per day. That number doesn't reflect a technology gap — it reflects a design gap. Per Social Edge Consulting, 91% of organizations already operate an intranet, yet nearly a third of employees never log in, and only 13% use one daily. The failure mode is consistent: intranets get built for a workforce that no longer describes most organizations. SWOOP Analytics measured average daily intranet use at just six minutes — which happens when the platform was designed for a desk worker with time to browse menus and remember folder structures, not for the 80% of the global workforce that is deskless, per Emergence Capital's research. These workers — shift supervisors, clinicians, retail associates, field technicians — need an intranet that surfaces the right information immediately, works on a personal phone, and doesn't require a corporate email address or VPN to access. When the design ignores that reality, the metrics reflect it. The 16 examples below are drawn from the MangoApps platform and organized around a single question: what workforce challenge does each design solve? The goal isn't to pick a look — it's to understand the logic behind the choices. ## Homepage and dashboard designs Your intranet's homepage is the first screen an employee sees. For a desk worker, it's a navigation hub. For a frontline employee logging in between shifts from a personal device, it's often the only screen they'll visit. How that screen is organized — what's above the fold, what requires scrolling, what takes a second click — determines daily usage more than any other design decision. ### Manufacturing: search-first architecture (CableInc) CableInc places the search bar at the top of the dashboard, above news feeds, task widgets, and team workspace links. This is a deliberate hierarchy: it trains employees to find answers before reaching out for help, reducing the interpersonal information overhead that accumulates when the intranet isn't the first place people look. Below the search bar, CableInc layers company news, task and notification widgets, and quick links to apps and workspaces. The design serves both the experienced employee who knows exactly what they need and the new hire still mapping the organization's resources. When the search bar is prominent, the intranet starts to function as institutional memory rather than a bulletin board. ### Retail: social proof and resource access (RetailCo) RetailCo leads the homepage with an employee recognition widget — a deliberate signal about what the organization values. For high-turnover retail environments, where the average cost of replacing a single frontline employee falls between $4,400 and $15,000, making recognition visible on the primary intranet surface is a retention investment as much as a design choice. The resource library sits prominently below: workplace procedures, employee forms, marketing materials. For retail teams managing multiple locations, having procedures accessible from the same screen as the recognition feed eliminates the friction that causes employees to ask managers questions the intranet was built to answer. ### Healthcare: SSO-first design for compliance-heavy environments (MedHub) MedHub places company announcements top-left — the most viewed surface on a dashboard — and builds the rest of the homepage around single sign-on (SSO) access to clinical apps and Google integrations. For a healthcare environment where clinicians move between patient management systems, scheduling tools, and communication platforms without re-entering credentials, SSO on the homepage converts from a convenience feature to a security architecture. OU Health achieved 87% workforce engagement within months of launching an intranet built on this pattern — immediate announcement visibility paired with fast authenticated app access from a single screen. ### Airline: operational context baked in (AirCo) AirCo builds for speed: Quick Links, Outlook Mail integration, a Forms widget, and a real-time weather widget sit alongside compact news and announcement blocks. The weather feature reflects a deliberate design philosophy — for employees whose job depends on operational conditions, surfacing that data inside the intranet makes it the operational command center rather than just a communications platform. ### Technology: news-heavy, culture-forward (TechNow) TechNow dedicates two-thirds of the homepage to company news, announcements, webcasts, and social feeds. This ratio reflects the communication priorities of a tech workforce: employees are highly motivated to stay informed about product direction, competitive movements, and strategic decisions. The right panel handles utility — calendar, quick links, library. The lesson isn't that all intranets should be news-heavy. It's that the homepage content ratio should reflect what your workforce actually comes looking for most often. ### Food service and multi-location operations: people first (Garry Hansen Bakery) Garry Hansen Bakery leads with the My Coworkers widget, surfacing colleagues across locations above resources and news. For distributed operations where most employees never interact with corporate staff directly, the intranet's primary challenge isn't content management — it's helping employees know who to contact and how to reach them. The Important Contacts widget reinforces this: stores, office locations, and management contacts are one tap away. A to-do list, quick links, and resource library handle productivity. But the design sequence communicates a clear priority: people before process. ### Finance: engagement paired with information distribution (Orbit Trust Banking) Orbit Trust Banking balances news distribution with active feedback mechanisms. The Surveys widget gives employees a voice; the Calendar widget shows what's upcoming. For a financial institution with strict communication requirements, pairing information delivery with built-in response mechanisms — rather than routing employees to a separate engagement tool — reduces the gap between "received information" and "acknowledged feedback." ## Company and department sites The homepage drives initial engagement. Company and department sites determine whether employees return. TeamHealth consolidated 200+ previously disparate internal systems into a single intranet deployment on MangoApps — the company site architecture is where that consolidation becomes navigable for employees. ### Government agency: cross-department transparency (PNW) PNW's company site surfaces Communications, HR, and Learning & Development on the same page, giving employees a cross-departmental view they wouldn't encounter on their personal dashboard. The Ideas widget at the bottom converts the intranet from a broadcast channel into a feedback surface — a design choice that treats employee input as a function of the platform rather than a separately managed program. ### Healthcare: compliance architecture (MedHub Company Site) MedHub adds a dedicated Policies & Procedures page as a separate navigation node — distinct from the general resource library. Clinicians who need to confirm patient communication guidelines before a care interaction need to find that information in seconds, not navigate through a general content hierarchy. HR widgets for training certifications and IT services anchor supporting compliance tools around the same high-priority destination. In healthcare, the intranet's design is a compliance architecture, not just a communications one. ### Finance: tools-first company site (Orbit Trusts' Bank) Orbit Trusts' Bank takes a utilitarian approach: quick links, software apps, department pages, and HR and IT resources are primary. Social content — social accounts, birthdays, feedback surveys — is present but secondary. For financial services employees who expect instant access to tools and view browsable content as optional, this hierarchy reflects actual usage patterns rather than an aspirational vision of engagement. ### Technology: culture as a company asset (TechNow Company Site) TechNow uses the company site to distribute cultural content at scale — employee spotlights, recognition widgets, a Now Hiring module, and a CEO Corner. For technology companies competing for engineering talent, the intranet's company site functions as a retention and recruiting surface as much as an internal communications hub. The CEO Corner specifically shortens the distance between leadership messaging and employee awareness. ### Housing: clarity over content density (National Residences) National Residences prioritizes white space and consistent iconography over information volume. A prominent search bar anchors the top; department links, resources, and social media accounts are organized below with clear visual hierarchy. For employees managing complex, information-heavy transactions, the design principle is reduction: fewer choices visible at once, faster navigation to the right one. ### Hospitality: community and compliance on the same screen (Oneal) Oneal threads community content — a birthday widget, a story submission form — alongside compliance and training tools. For hospitality environments with high frontline turnover, making "feel connected" and "get trained" equally prominent and equally accessible from the same screen is a practical design decision, not an aspirational one. Employees who feel connected to colleagues are more likely to return to the intranet for the compliance content they need. ## Department pages Department pages serve a different audience than company sites. The design problem shifts from "what does everyone need" to "what does this specific team need to operate." Effective department pages answer both questions the moment an employee lands: what can I find here, and who do I ask when the page doesn't have it? ### IT: self-service first, escalation second (ElectronicsCo) ElectronicsCo's IT department page is organized around a service model: FAQs, request forms, maintenance schedules, and policies are the primary content. The IT team widget — photos, names, direct contact links — is placed so employees who exhaust the self-service options know immediately who to reach next. This design reflects how IT teams want to operate. The intranet architecture makes that preference explicit rather than leaving it implicit. ### HR: transparency and recruitment in one place (GreatHomes) GreatHomes leads with the people widget — direct contact for HR staff members — then layers quick links to HR resources, a Now Hiring module, and employee referral tools. Embedding referrals on the HR page converts the intranet into a talent acquisition channel without requiring a separate recruiting communications effort. ### Learning & Development: mission context before content (L&D Department Page) This L&D department page opens with the department's mission statement before presenting course links, calendars, and library resources. Employees who understand why a learning program exists are more likely to engage with it than those who encounter a list of modules with no stated purpose. The Internship Week widget adds temporal relevance — not just "here are courses," but "here's what's happening in the organization around learning right now." ## What these examples tell you about your own design Across all 16 examples, the highest-functioning intranet designs share three characteristics. They deliver one clear primary action above the fold rather than presenting a menu of equal-priority options. They separate content by audience rather than content type — department pages don't try to be homepages, and company sites don't try to be everything. And they embed a feedback or engagement mechanism on every primary surface, so the intranet communicates in both directions. For organizations managing large frontline workforces — where most employees may never have a dedicated workstation — these principles become more consequential. The [MangoApps employee app](/solutions/employee-app) extends intranet access to personal devices without requiring a corporate email address, managed hardware, or VPN access. That access architecture is what makes frontline adoption achievable rather than aspirational. For teams evaluating how these design patterns compare against alternatives in the market, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) offers independent third-party analysis, and the [MangoApps Forrester Wave evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) covers analyst positioning in the broader employee experience space. For a broader overview of the [modern intranet platform](/solutions/modern-intranet) capabilities that enable these design patterns — widget-based homepages, company portals, department sites — without custom development, that's a practical starting point before reaching the design decisions these examples illustrate. The 16 examples above are a starting point, not a template. The design decisions that matter most are the ones that follow the logic behind each choice: know your workforce type, know what they'll come looking for, and build the first screen around that. --- # What is a Digital Workplace? Everything you need to know. **Author:** Mason Hager **Published:** 2022-10-10 **Category:** integrated-digital-workplace This article is meant to serve as a guide for everything you need to know when getting started with digital workplace technology. A digital workplace is equal to a physical workplace as the name suggests. Currently, organizations are using work collaboration tools, work management tools, intranet, analytics, and more, in their digital environment. These technologies […] This article is meant to serve as a guide for everything you need to know when getting started with digital workplace technology. A digital workplace is equal to a physical workplace as the name suggests. Currently, organizations are using work collaboration tools, work management tools, intranet, analytics, and more, in their digital environment. These technologies will help organizations better communicate, collaborate, engage, and interact with the people around them. Achieving digital transformation takes time and effort, but by implementing digital workplace technology, you are taking a step in the right direction. Jump to a topic: What Is A Digital Workplace? Why You Need Digital Workplace Technology 5 ‘Must Have’ Digital Workplace Technologies How To Leverage Digital Workplace Technology Top 10 Digital Workplaces For 2023 What is A Digital Workplace? A digital workplace is a virtual platform that helps bring together the systems, people, and content within an organization. It focuses on equipping employees with the tools they need to collaborate and communicate effectively in a single digital space. Organizations that opt for digital workplace technology are generally seeking to unify employee communications, collaboration, engagement, content sharing, and training within their company. We are seeing a shift in digital transformation across hybrid organizations as the focus on providing an accessible digital workplace for all employees continues to grow. How K·Coe Isom Saves $50,000 Annually With MangoApps Learn how K·Coe Isom replaced their old intranet and knowledge management platform with MangoApps, resulting in annual savings of $50,000. learn more Why You Need Digital Workplace Technology Organizations need to know the ROI they can expect to see from implementing digital workplace technology. Here’s what you can expect to see: Reduce costs Companies can save money on licensing fees when they consolidate their tech stack into one digital workplace platform. It can be VERY expensive to pay for point solutions for each employee. With a digital workplace, you can get rid of expensive systems (such as replacing email with chat/messaging).  There are also fewer tangible savings that can arise from a digital workplace through improving productivity.  Your IT department can save time and work on more impactful projects by not having to manage countless different systems, your employees can save time by having the capability to search for specific information or colleagues, and you can even prevent costly duplicate work by providing better knowledge transfer across employees. Centralize employee access Give frontline and desk workers access to the tools that can help them accomplish their daily work tasks more efficiently. A digital workplace gives your company the power to enable employee collaboration across different departments, offices, and countries. Many digital workplace platforms come with a mobile app that allows employees to connect and collaborate with colleagues from anywhere in the world. Improve productivity When information is scattered across different tools it can become difficult for teams to gain insights and work well together. Without a simple way to share resources, express thoughts, and collaborate on ideas, work can never reach its full potential. With a digital workplace platform, employees don’t have to navigate different systems and remember countless logins and can instead go to their digital workplace for a ‘one-stop shop’ for anything they might need. Enhance internal collaboration By maximizing both top-down communication, and peer-to-peer communication across colleagues you can ensure that employees will freely share ideas and collaborate within the confines of your digital workplace. These exchanges offer everyone an opportunity to share their opinion and ideas within their teams, departments, and office locations. This boosts collaboration and creates an inviting space that ultimately leads to better work performance, better relationships with colleagues, and higher employee satisfaction levels. Improve company culture With a digital workplace, you can help employees get in touch with each other better and allow them to collaborate with colleagues more frequently. In doing this, you’re building a tight-knit workforce with high employee satisfaction levels. Integrating a digital workplace platform into your employee’s day-to-day life can help improve your employees’ productivity, making their lives easier, and in turn improve company culture. Employees that are equipped with the tools to do their jobs effectively are more likely to put in the effort needed to go the extra mile.  Calculate the ROI of MangoApps In this report, we take a look at how to measure the return on investment of adopting a modern digital work hub such as MangoApps. download report 5 ‘Must Have’ Digital Workplace Technologies A digital workplace generally includes a combination of the following: Employee Communications (messaging, chat, team collaboration) Social Engagement (social feeds, rewards, recognition, reactions, comments, etc.) Content Sharing & Document Management System Employee Learning (LMS, training courses, onboarding, etc.) Mobile App (mobile intranet, alerts, notifications) While these digital workplace technologies can also be picked out as separate tools, we recommend going with a digital workplace platform as it is much better to host everything in one central platform. If you want to get started on your company’s digital transformation ASAP, below are four ‘must have’ digital workplace technologies to look at. 1. Communication & collaboration tools Collaboration software can help bring different departments and employees together despite their geographical location. Organizations with large workforces can allow employees to collaborate and communicate with dispersed colleagues. Employees can converse on a day-to-day basis regarding work activities.  Collaboration tools also help break down department and employee communication silos and provide an immediate solution to end-users across department functions. The key to successful collaboration lies in the practical implementation of a digital workplace strategy, capable of driving actual cultural change within the organization. 2. Information & knowledge-sharing tools One of the biggest hindrances to employee productivity is researching and tracking down important information. Sourcing the right information and time management with team collaboration software helps create a digital workplace where documents, training videos, conferences, and more, become easily accessible.  With a quick search for the related topic or skill, your employees can find the right information or colleague from anywhere across the world. 3. Employee engagement tools With people as your most important asset, it is crucial to make sure that your employees are equipped with tools that allow them to celebrate each other and recognize hard work. This social component is critical because if you can keep your employees engaged and satisfied, you will realize many long-term benefits such as improved employee retention, productivity, and contribute to a positive company culture. Employee engagement tools include surveys, feedback, rewards/awards, recognition, reactions, comments, feeds, and more. 4. Analytics & insights Digital workplace technology is a data-driven concept. All technologies from the coffee maker to a server are programmed to use data analytics to process decisions with optimal efficiency, accuracy, and speed. With analytics and insights as the backbone of a digital workplace ecosystem, it provides metrics that help companies make informed and precise decisions. Proper digital workplace technology is equipped with detailed analytics that offers insights into productivity, collaboration, communication, and so much more. Switch To A Modern Intranet Learn about the benefits of switching to a modern intranet, and why it’s never too late to start building a better digital workplace for your employees. Get your free eBook today! learn more How To Leverage Digital Workplace Technology Office of Public Works (OPW) – a government department in Ireland, faced a roadblock that they were struggling to hurdle. Employees couldn’t access their intranet unless they were using a computer at an OPW office location.   As a result of this, the majority of employees were unable to access any of the material, resources, and information outside of work hours. The Head of ICT at Office of Public Works, Liam Stewart, set out to find a platform that could resolve this problem while aiding the digital transformation of their workplace processes. OPW’s main drivers for switching to a digital workplace were that they wanted a platform that could improve employee engagement, remove duplicate systems, encourage employees to contribute content, and build a strong workplace culture. Watch this video to learn how OPW ditched their outdated intranet platform for a modern digital workplace solution. learn more Top 10 Digital Workplaces For 2023 A digital workplace can help unify your company’s resources while bringing employee collaboration and communication into a centralized area. When done effectively, it can make the difference between an engaged and disengaged employee. MangoApps Interact Simpplr LumApps ThoughtFarmer Igloo Unily Beezy Jostle Happeo Below is a list of the top 10 digital workplace platforms broken down so that you can easily identify which platform might be the best fit for your organization’s specific needs. These digital workplace platforms will help your employees communicate and collaborate more effectively, whether they are on the go, working from home, or in the office. So, without further ado, let’s dive into the top 10 digital workplace solutions for 2023! 1. MangoApps MangoApps is a modern company intranet and employee communications platform that provides leaders and employees with the tools they need in one central hub. Features: Content Management System – centralize company content and resources. Quickly locate the files and information with searchable repositories of knowledge. Universal Search – identify any resource, information, or person with a modern search that allows you to search within specific channels, teams, groups, and more. Company Communication – get company news and information out to employees on the channels they prefer. This helps keep frontline workers in the mix and leads to less disruption for desk workers. Team Collaboration – create searchable team workspaces with projects and groups. Team members can stay on the same page and ensure nothing falls through the cracks. Digitized Workflows – automate simple, time-consuming tasks with interactive forms and tracker spreadsheets. Build custom workflows for your own unique tasks. Mobile App – connect frontline workers with your intranet with a company-branded mobile app that is accessible anytime, anywhere. Most Suitable For: MangoApps is most suitable for enterprise and mid-sized organizations seeking to provide a digital workplace platform for their mix of frontline and desk workers. 2. Interact Interact is a social intranet platform that is focused on transforming the way people interact and communicate within an organization.  Features: Mobile App – bring employee communication and collaboration into a singular platform. Content Management System – provides a fully built CMS that keeps content relevant and fresh. Integrations Library – offers an extensive integrations library with integrations such as Salesforce, Slack, and Zendesk. People Directory – helps employees find and collaborate with coworkers. Virtual Communities – allow employees to engage and collaborate with their peers in their own digital space. Most Suitable For: Interact is most suitable for enterprise and medium-sized organizations that are looking to improve employee experience. 3. Simpplr Simpplr provides employee experience software that simplifies employee communication and aims to connect your distributed workforce.  Features: Social Engagement – get workers to collaborate and communicate more effectively with advanced social engagement features. Advanced Analytics – use actionable analytics to make informed business decisions. Smart Feed – helps employees stay informed and allows them to socialize with peers on critical projects, events, and more. Federated Search – allows employees quick access to people, files, sites, and more. Central Hub – provide employees a single place for their notifications across HR systems, expense reports, approval workflows, and more. Most Suitable For: Simpplr is most suitable for enterprise and medium-sized organizations that are looking to connect and align their distributed employees.  4. LumApps LumApps is an employee experience platform that aims to unify the modern workforce through better employee communication, engagement, and access to information. Features: Multi-channel Collaboration – Provide engaging communications for the entire workforce, across all channels and devices. Knowledge Management System – provides a single location for employees to find and access important resources. Enterprise Video Management – helps drive employee engagement with immersive video content. Mobile App – offers a platform for frontline workers to stay engaged and in tune with the company. Integrations – integrates with Microsoft 365, Google Workspace, Zendesk, Workday, Okta, and more. Most Suitable For: LumApps is most suitable for enterprise and medium-sized organizations that have a need to connect their distributed workforces & frontline employees. 5. ThoughtFarmer ThoughtFarmer is an internal comms intranet that helps connect employees, facilitate knowledge sharing, and enable collaboration among dispersed employees. Features: Knowledge Management – capture valuable information possessed by employees and make it available on the intranet for everyone. Groups – create custom workspaces. Team members can quickly share and receive relevant news and updates within a group. Modern Search Engine – allows for seamless navigation and enables employees to quickly find what they are looking for. Alerts & Notifications – display notifications for updates on pages and groups that you follow. Interactive Org Chart – use in conjunction with people directory and profile pages to help bring dispersed employees closer together. Most Suitable For: ThoughtFarmer is most suitable for Internal Comms, IT, and HR professionals that reside in the legal, financial, and healthcare industries. 6. Igloo Igloo is a next-gen intranet with the capabilities to change the way your organization communicates, shares information, and engages with employees. Features: Content Moderation – allow administrators to review and approve content and comments before they are published. Configurable Permissions – provide individual employees to groups permission to read, write, and edit a page, space, or channel. Forums – contribute to an interactive culture by creating a space for employees to share ideas, ask questions, and have discussions. Mobile App – use a branded digital workplace mobile app to break down work silos and keep dispersed employees engaged. Actionable Analytics – identify intranet engagement levels, brand ambassadors, and popular pieces of content among your employees. Most Suitable For: Igloo is most suitable for enterprise and mid-sized organizations that aim to improve employee experience and make communication a two-way street. 7. Unily Unily is an employee experience platform that connects, informs, and engages distributed employees across the workforce. Features: Multi-channel Comms – keep employees engaged and reaches them from wherever they are. Broadcast Emails – help bring your comms channels into one with dynamic email newsletters that can be targeted towards specific individuals and groups within the workforce. Unified Search Center – allows employees to search across the databases to locate a specific resource or piece of information. Rewards and Recognition – celebrate employees and encourage them to do the same with peer-to-peer recognition features. Dynamic Publishing – give internal comms the tools they need to publish dynamic content in seconds. Content is translatable to any language. Most Suitable For: Unily is most suitable for enterprises with over 1,000 users. 8. Beezy Beezy is an intelligent digital workspace that is primarily aimed at helping organizations get the most out of their Microsoft 365 and Microsoft SharePoint platforms. Features: The ShareBox – seamlessly share information and content across the organization without the complexity of SharePoint. Communities – allow global and local teams to collaborate and engage in relevant discussions. Mobile App – stay connected and in tune with the digital workplace with native mobile apps for iOS, Android, and Windows. Knowledge Centers – employees can share knowledge in a way that is well-structured and easy to find. Beezy Bot – use an intelligent machine-learning bot to effectively direct users to the right piece of content or person. Most Suitable For: Beezy is most suitable for organizations of any size that have Microsoft 365 or Microsoft SharePoint. 9. Jostle Jostle is an employee success platform that aims to bring the whole organization into a single digital workspace where employees can quickly find what they need. Features: News Feed – publish relevant, targeted content to the right audience. You can send out news to specific office locations, departments, and project teams as well. Library – store all files and resources in a single, centralized place. JostleTV – broadcast the latest information and news to monitors set up across your office. This helps office employees stay in tune while away from their desk. Dynamic Org Chart – simplify complex org structures and clearly define who is responsible for what within specific teams, projects, and departments. Discussions – instantly connect and collaborate with employees to help keep a project on track. Most Suitable For: Jostle is most suitable for mid-sized and small organizations that aim to bring their entire workforce into a single digital workspace. 10. Happeo Happeo is a modern social intranet that connects your people, information, and tools within a centralized digital workspace for collaboration and communication. Features: Collaborative Channels – collaborate on projects, post special announcements, share relevant resources and information in a secure area for your teams. People Directory – connect with colleagues from across the organization with a in-sync visual org chart (backable by Google/Azure AD). Enterprise-grade Security – company content and information is protected with first-class security – fully ISO 27001 certified. Internal Branding – transform your intranet into a completely branded employee experience with custom URLs, login pages, and a unique environment. Elasticsearch – universal search that searches your Google Drive, OneDrive, company-knowledge pages, channels, people, and more. Most Suitable For: Happeo is most suitable for enterprises and mid-sized organizations looking to bring their employees together in a central space. Additional Resources For further reading, check out a few of these resources below. A Deep Dive Into The ROI Of A Digital Workplace Modern Digital Workplace Platform Whitepaper How A Digital Workplace Helps YMCA Employees Serve Their Communities Leveraging A Digital Workplace Case Study book a demo --- # Best Practices for Intranet File Naming Conventions **Author:** Rebecca Stone **Published:** 2022-10-06 **Category:** best-practices As we said in this post about the recent updates to MangoApps’ search capabilities and algorithmic news feed, an incredible search engine is at the crux of our offering. The same goes for any other intranet platform on the market. If you can’t find things easily while using a product like ours, you might as […] # Best Practices for Intranet File Naming Conventions Clear file naming conventions are essential for intranet discoverability — here is how to establish them. Per IDC, employees spend an average of 2.5 hours per day searching for information. A consistent, documented naming standard is one of the most direct ways to cut that waste, and it costs nothing to implement. These principles apply to any [modern intranet](/solutions/modern-intranet), whether you built it yourself or are working with a vendor. ## Best Practices To maximize the findability of files across your intranet platform, establish a naming convention following these guidelines: - **Keep names short but descriptive.** The name should tell users exactly what is inside without requiring them to open the file. When clarity and brevity conflict, favor clarity — a slightly longer name that removes ambiguity is better than a short name that forces guesswork. - **Name files consistently.** Decide on a pattern (e.g., `DeptName_Topic_YYYY-MM-DD`) and apply it everywhere. Inconsistency is the single fastest way to erode trust in a file library. - **Avoid special characters and spaces.** Characters such as `# % & * : < > ? / \ { | }` break links and cause indexing errors across integrated storage platforms. - **Avoid periods, spaces, and slashes.** Use capital letters or underscores to separate words instead (e.g., `HROnboarding_Checklist` rather than `HR Onboarding Checklist`). - **Think like a searcher.** Before saving, ask: what words would a colleague type to find this file? Build those words into the name. - **Document your convention and train file managers.** A naming standard that lives only in one person's head is not a standard. Write it down, publish it, and train at least one person per department to enforce it. - **Incorporate metadata.** If you want to take findability a step further, structured metadata — department, content type, owner, review date — gives search engines and AI-curated feeds the data layer they need to surface the right file to the right person. Organizations that deploy AI-curated content feeds rely on consistent file naming and metadata as the foundation that makes personalized content surfacing accurate. ### Why Each Rule Matters: The Governance Layer Poor knowledge findability is a structural governance problem, not just a search problem. Intranets without documented naming standards and content ownership policies produce stale, ungoverned content that erodes platform trust over time. Per Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in. Confusing, hard-to-navigate file libraries are a primary driver of that disengagement. It is also worth noting that universal search spanning connected storage platforms such as SharePoint, Google Drive, Box, and Dropbox only delivers full value when the underlying file names and metadata are consistent across those sources. A well-named file in one system should be just as findable when surfaced through an integrated [knowledge management](/solutions/knowledge-management) layer. AI-powered search makes consistent naming *more* important, not less. The article's original framing — that a smart search engine reduces the need for good naming — gets this backwards. Consistent naming is the data quality layer that makes AI search and personalized feeds accurate. Garbage-in, garbage-out applies to intranet search just as it does to any other data system. ### A Note for Frontline and Deskless Workers Per Emergence Capital, 80% of the global workforce is deskless. These employees typically access the intranet on a mobile device with limited screen space and no time to scan a list of ambiguously named files. A name like `Q3_SafetyBriefing_WarehouseTeam_2025-07` is immediately actionable on a small screen; `Final FINAL v3 (use this one).pdf` is not. Clear naming conventions are a frontline accessibility issue, not just an administrative preference. ## How to Start The best way to get started is to jump in with a plan: 1. **Identify champions.** Find at least one colleague per department who will see the value in this and can serve as a naming convention advocate. 2. **Draft the convention together.** Work across departments to agree on a format that handles cross-team files without conflict (e.g., prefix with department code when a file is shared across groups). Document this in a shared policy page — your [company portal](/key-features/company-portal) is a natural home for it. 3. **Communicate the why.** Create a post and share the naming convention with your organization. If people understand that poor naming costs the average employee 2.5 hours of search time per day (per IDC), they are far more likely to comply. Encourage content managers to hold their colleagues accountable. 4. **Start with new files today.** You do not need to rename everything before the convention delivers value. Apply the standard to every new file from this point forward. 5. **(Optional) Assign a retroactive cleanup sprint.** Identify a few people per department to spend one hour per week renaming legacy files. Even partial coverage improves findability significantly. Consider the scale: one enterprise deployment documented in the TeamHealth case study consolidated 200+ systems into a single dashboard — the file and content sprawl naming conventions must address can be enormous. ### Assign Content Owners Alongside Naming Standards A naming convention without ownership is incomplete. For each major content area or [department site](/key-features/department-sites), designate a content owner responsible for keeping files current, removing outdated versions, and enforcing the naming standard. This is the difference between a governed intranet and a digital landfill. Per Social Edge Consulting, only 13% of employees use their intranet daily — stale, hard-to-find content is a leading reason why. Assigning ownership turns a one-time cleanup into a sustainable practice. ## The Bottom Line: Naming Conventions Are an Investment in Platform Trust Your organization has invested significantly in establishing the intranet as the authoritative place to go for information. That investment pays off only when employees can find what they need quickly. Per Social Edge Consulting, nearly a third of employees never log in to their intranet at all — and a frustrating search experience is a direct contributor to that abandonment. The downstream cost is real: replacing a frontline employee costs between $4,400 and $15,000 on average, and a hard-to-navigate intranet that drives disengagement is a retention risk, not just a productivity one. File naming conventions are a low-cost, high-leverage intervention. They require no new software, no budget approval, and no technical expertise. They do require coordination, documentation, and follow-through — which is exactly what the rollout plan above is designed to provide. Implement the seven practices listed here, assign content owners per department, and document the standard in a place every employee can find it. That combination — consistent naming, structured metadata, and clear ownership — is what separates an intranet people trust from one they ignore. ## What About Existing File Archives? The most common objection to adopting a naming convention is the backlog: thousands of legacy files with inconsistent names that would take months to fix. The practical answer is triage, not perfection. Start by identifying the 20% of files that account for 80% of searches — typically current SOPs, active project documents, and frequently referenced HR or compliance materials. Rename those first. Archive or delete files that have not been accessed in 12–24 months. Apply the new standard to everything created going forward. Over 6–12 months, the proportion of well-named files grows organically without requiring a heroic one-time effort. For organizations managing SOP operations across multiple locations or business units, a tiered naming convention — one that encodes location, department, and document type — can make the archive problem tractable at scale. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers governance frameworks that apply directly to this challenge. ## How Do I Handle Cross-Department Naming Conflicts? Cross-department naming conflicts are common when two teams use different terminology for the same concept, or when a shared file legitimately belongs to multiple departments. A few approaches that work in practice: - **Use a department prefix.** Prefix every file with a two- or three-letter department code (e.g., `HR_`, `OPS_`, `FIN_`). For shared files, use a `SHARED_` prefix and store them in a dedicated cross-functional workspace. - **Establish a naming arbitration process.** When departments disagree on terminology, the naming convention owner (or an intranet governance committee) makes the call and documents the decision. This prevents the convention from fragmenting into department-specific dialects. - **Use metadata to bridge terminology gaps.** If Marketing calls something a "campaign brief" and Sales calls it a "pitch deck," the file name can use one term while metadata tags capture both. This is where a well-configured [workspaces](/key-features/workspaces) structure pays dividends — each team's workspace can surface the same file under the terminology they use. For a broader look at how intranet platforms are evaluated on governance and findability, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarking across major vendors. --- # The Key To Frontline Employee Retention Is Fostering Community **Author:** Justina Kolb **Published:** 2022-09-30 **Category:** company-culture Including frontline employees in your workplace community is vital. They’re the eyes and ears of your company. They physically interact with customers and vendors, giving a human touch to your organization. Without frontline employees, your operation would lack a life force. Just imagine what it’s like for customers to converse with detached, unenthused frontline workers. […] # The Key To Frontline Employee Retention Is Fostering Community Including frontline employees in your workplace community is vital. They're the eyes and ears of your company. They physically interact with customers and vendors, giving a human touch to your organization. Without frontline employees, your operation would lack a life force. Just imagine what it's like for customers to converse with detached, unenthused frontline workers. They're taking their business elsewhere or leaving a poor review, which means suffering sales for your company. So why are frontline employees, while in such a vital role, faced with an abundance of burnout, apathy, and turnover? One of the biggest drivers of frontline employee retention is community. The answer is simple: frontline workers feel isolated and disconnected from their companies. Because they are not stationary behind desks, frontline workers are often left out of company communications, creating a feeling of detachment. Fostering a workplace community that includes your frontline workers is the key to improving employee retention. According to IDC research, 69% of people use communities to do their job, but only 27% of companies utilize these communities. In order to better succeed, frontline workers need to be included and informed — to feel they are a part of your company's community. This is the key to motivating frontline employees. And the financial stakes are real: replacing a single frontline employee costs between $4,400 and $15,000, making the investment in community and employee engagement directly quantifiable against turnover expense. Success in this area is possible by creating a digital workplace community for frontline and deskbound workers alike. This is best achieved using an Employee SuperApp, so frontline workers can easily access company-wide information via mobile devices. Per Emergence Capital, 80% of the global workforce is deskless — meaning the majority of employees have historically been underserved by desktop-first intranet tools. Within a mobile hub, frontline workers have equal access to the same news, information, and resources as their office counterparts. They can conveniently join conversations, ask questions, and share their unique knowledge with colleagues in different departments and locations. Critically, frontline workers can access community, schedules, HR self-service, and employee engagement training in one app without a corporate email address or VPN. With a mobile means of wide-reach communication, the feeling of community will rise, as will frontline employee retention. Organizations that have launched branded employee apps have seen 87–90% workforce adoption within the first few months, with at least one large frontline employer achieving four times the industry-standard engagement rate. ## Webinar — Building a Workplace Community to Boost Frontline Employee Retention Want to learn more about building an engaging community for frontline workers? Check out this webinar in which one of our team members illustrates how to achieve a workplace community and the benefits of boosting frontline engagement. **In this webinar, you'll learn:** - What tools you need to create an engaging workplace community - How to kickstart your workplace community - The effects of a strong workplace community We've also created a checklist to serve as a point of reference as you evaluate your workplace community initiatives. Do you have all the ingredients that make for a strong community? For some examples of how to do this well, you can also read our customer stories from the YMCA and CIVICUS. For more information, see our webinar on what frontline employees actually want, our primer on what an Employee SuperApp is and does, and our [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook). ## How to Get Started: A Phased Approach to Building Frontline Community Knowing that community drives retention is one thing — knowing where to begin is another. The following phased approach gives HR and operations leaders a practical path from diagnosis to measurable results. **Phase 1 — Audit your current communication gaps (Week 1–2)** Survey frontline teams using a structured employee engagement survey or employee engagement questionnaire to identify where information breaks down. Ask: Do workers know where to find schedules, HR policies, and company news? Per Social Edge Consulting, nearly a third of employees never log in to the intranet, and only 13% use one daily — meaning most frontline workers are already operating without the information infrastructure their desk-based colleagues take for granted. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools, while per IDC, employees spend 2.5 hours per day searching for information — a gap that a mobile-first community directly closes. **Phase 2 — Pilot mobile access for one department or location (Week 3–6)** Select one high-turnover location or department and deploy a mobile community app that requires no corporate email address or VPN. Enable push notifications, SMS, and in-app alerts for time-sensitive communications — not just passive intranet posts. This is especially relevant for [retail](/industries/retail), [hospitality](/industries/hospitality), and [nonprofit](/industries/nonprofit) organizations where shift workers rarely sit at a desk. Track login rates, message open rates, and any early signals in absenteeism or voluntary turnover. **Phase 3 — Measure employee engagement lift at 30 and 90 days** Run a follow-up employee engagement survey at the 30-day mark to capture sentiment shifts. Look for movement in belonging scores, manager communication ratings, and intent-to-stay responses. Per Social Edge Consulting, 91% of organizations operate an intranet, yet adoption remains low — the differentiator is not the technology itself but whether it is accessible and relevant to frontline workers on their terms. Use the 90-day data to build the business case for a full rollout, anchoring the ROI conversation in the $4,400–$15,000 per-replacement cost you identified in Phase 1. **Phase 4 — Scale and deepen with training and employee engagement programs** Once the community is live and adoption is climbing, layer in structured employee engagement training, peer recognition, and manager-led discussion groups. Connect frontline workers to learning content — [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) is a useful internal reference for building this layer. Employee engagement software that consolidates community, scheduling, and learning in one place removes the friction that causes adoption to stall. ## What Does This Cost, and How Long Until We See Results? The most common follow-up question from operations and HR leaders is whether the investment in employee engagement software is justified before turnover costs compound. The math is straightforward: if a 500-person frontline workforce turns over 30% annually, that is 150 replacements per year. At a conservative $4,400 per replacement, the annual cost is $660,000. A community platform that reduces voluntary turnover by even 10 percentage points recovers that investment many times over. Timeline expectations vary by organization size and change-management capacity, but the pilot-to-full-rollout cycle described above typically produces measurable engagement lift within 60–90 days. Named organizations in the healthcare and sports entertainment sectors have reported 87–90% adoption within the first few months of launch. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarks for evaluating platform performance against these timelines. ## What If We Can't Afford a Full Employee SuperApp Right Now? Not every organization can deploy a full [solutions/employee-engagement](/solutions/employee-engagement) platform in a single budget cycle. In that case, the audit phase (Phase 1 above) still delivers value on its own: understanding where communication breaks down costs nothing and creates the evidence base needed to secure budget. Organizations in sectors with thin margins — such as [BPO](/industries/bpo) — often start with a single use case (shift notifications via SMS, for example) and expand from there. The key principle is that frontline workers must be reachable on personal mobile devices without requiring a corporate email address; any solution that cannot meet that baseline will reproduce the same disconnection the community strategy is designed to solve. For a broader view of where workforce operations technology is heading, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines the capabilities organizations are prioritizing in the near term. ## The Definitive Takeaway Frontline employee retention is not a mystery. Workers who feel seen, informed, and connected to a community stay longer, perform better, and represent your organization with more energy. The disconnection that drives turnover is structural — it comes from communication systems built for desk workers — and it has a structural fix: a mobile-first community that reaches every employee where they already are, without barriers like corporate email or VPN requirements. The cost of inaction is concrete: $4,400–$15,000 per replacement, multiplied across every preventable departure. The path forward is equally concrete: audit your gaps, pilot mobile access, measure engagement lift, and scale what works. Organizations that have followed this path have achieved 87–90% adoption and engagement rates that far exceed legacy intranet benchmarks. The community investment pays for itself before the first annual review cycle closes. --- # Introducing User Engagement Features for Your Intranet Launch & Beyond **Author:** Rebecca Stone **Published:** 2022-09-15 **Category:** modules-features When you make a change and implement new software, it can be hard to get your users engaged, especially when it comes to some of the deeper features and functionality. To that end, we have built a number of new features aimed at helping you get your users off the ground with the platform as […] ## Introducing User Engagement Features for Your Intranet Launch & Beyond Getting employees to actually use a new intranet is one of the hardest parts of any rollout. Per Social Edge Consulting, while 91% of organizations operate an intranet, nearly a third of employees never log in — and those who do average just six minutes per day on intranet tools, per SWOOP Analytics. MangoApps addresses this directly with two features built specifically to drive adoption from day one: **Personalized Recommendations** and an **Out-of-the-Box Department Page**. Both are available now and require minimal setup. When you implement new [employee engagement software](/solutions/employee-engagement), it can be hard to get your users engaged, especially when it comes to some of the deeper features and functionality. To that end, we have built a number of new features aimed at helping you get your users off the ground with the platform as quickly as possible. Our hope is that these features will make things easier to find and, where relevant, give people a nudge in the right direction. Ultimately, these functions will help increase adoption, drive engagement and take some of the work off new customers' shoulders. ## Personalized Recommendations With a recent update, we have added actionable and personalized recommendations for network admins and users. When enabled, users will get actionable and personalized recommendations based on settings and site usage. These are aimed at increasing adoption, driving engagement and improving the findability of information using proven best practices. IDC estimates employees spend 2.5 hours per day searching for information — a problem that targeted, role-based recommendations are designed to reduce from the moment someone logs in. - Recommendations for admins may include things like create a campaign, post about the Mango Recorder app or create a survey. - Recommendations for end users may include turning on the weekly email digest, recognizing a coworker or adding hashtags to files. - Admins and users can choose to follow a recommendation by taking the recommended action right from the prompt. If the user declines a recommendation, then that recommendation will not be made for them again. They can still access their declined recommendations from a declined list, however, if they change their mind. - Admins have complete control over which recommendations to have available in their network for end users, if any. These suggestions help admins make the most of MangoApps' features by encouraging end users to come to the platform often. It encourages users to become more active, resulting in a great user experience. It's worth noting that these recommendations are not a one-time onboarding nudge. They function as an ongoing AI engine that continuously surfaces the right content and actions for each employee role — connecting to MangoApps' broader AI assistant capabilities across the [modern intranet](/solutions/modern-intranet) platform. OU Health, for example, achieved 87% workforce engagement within a few months of launching a branded employee app built on MangoApps, per the MangoApps OU Health case study. The same recommendations engine is also accessible to the 80% of the global workforce without a desk, per Emergence Capital. Frontline employees can reach their personalized recommendations on personal iOS or Android devices — no corporate email address or VPN required — so the adoption lift extends well beyond office workers. ### Getting Started with Personalized Recommendations - **Who should enable this first?** Network admins, as they control which recommendations surface for end users and can tailor the list to their organization's priorities. - **How do I enable it?** Navigate to your network admin settings and toggle on Personalized Recommendations. From there, select which recommendation types are available to end users. - **What's the expected impact?** Customers who activate recommendations early in their rollout report faster time-to-first-action for new users and higher return visit rates. For context, CVS achieved 90% frontline adoption within the first six months on a modern intranet platform — a benchmark that illustrates what consistent, role-relevant prompting can deliver. ## Out-of-the-Box Department Page MangoApps 16.0 comes with direct access to all [department sites](/key-features/department-sites) on your intranet through an Out-of-the-Box Ready to Use Department page. - This department page is a list of all of the departments with public pages on your site, as well as private departments you are a member of, and all of their subpages. - The list of departments is in alphabetical order. - Users can click on the department name or thumbnail to visit the department's pages or click on any of the pages listed and go directly to that page. - It takes just seconds to set up. This helps existing users who may not be very familiar with the site more likely to be able to navigate to what they're looking for. We think having this page readily available for our customers will help increase traffic and the ability for their users to self-serve and have a positive experience using the platform. Traditional intranets can take months to deploy, strain IT teams, and deliver static content that becomes stale quickly. The Out-of-the-Box Department Page is one deliberate counter to that pattern: it is pre-built, alphabetically organized, and live in minutes — no custom development required. At MangoApps, we pride ourselves on delivering the best service to our clients throughout the entire onboarding and implementation process. And this is one more out-of-the-box feature we're providing to help customers get the MangoApps platform up and running quickly, with virtually no effort. You can explore how the [company portal](/key-features/company-portal) ties these department pages into a unified employee destination. ### Getting Started with the Department Page - **Who should set this up first?** Any admin managing a network with multiple departments — especially organizations where employees frequently say they can't find the right team's resources. - **How do I enable it?** The Department Page is available out of the box in MangoApps 16.0. Admins can activate and configure it from the Pages section of the admin console in seconds. - **What's the expected impact?** Per Social Edge Consulting, only 13% of employees use their intranet daily. A clearly navigable department directory lowers the friction that keeps the other 87% from returning. Pair it with Personalized Recommendations to give users both a map and a guide. ## How Do These Features Compare to Other Intranet Platforms? Most intranet platforms offer some form of navigation and notifications, but few combine AI-driven personalization with a zero-configuration department directory in a single, unified platform. MangoApps has been recognized in the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) and included in a leading research firm's evaluation of intranet platforms — signals that the approach to employee engagement here is measured against industry standards, not just internal benchmarks. For organizations evaluating options, the practical differentiators are: no email or VPN required for frontline access, admin-controlled recommendation governance, and a department page that requires no IT involvement to launch. Low intranet engagement carries real cost — replacing a single frontline employee runs $4,400–$15,000 on average — which means the ROI case for features that move daily active usage from 13% toward industry-leading benchmarks is straightforward. ## What Should I Do After Enabling These Features? Once Personalized Recommendations and the Department Page are live, the next steps that drive sustained employee engagement are: 1. **Audit your department pages** — make sure each department has a current, public-facing page so the directory is useful from day one. The [webpage builder](/key-features/webpage-builder) makes it easy to update or create pages without developer help. 2. **Review the admin recommendation list** — disable any recommendations that don't apply to your organization's current priorities to keep prompts relevant. 3. **Measure return visits at 30 and 60 days** — compare daily active users before and after enabling both features. Use that data to make the case for expanding your intranet investment. 4. **Extend to frontline teams** — if your workforce includes deskless employees, confirm mobile access is configured so the 80% of workers without a desk, per Emergence Capital, can benefit from the same features. 5. **Explore the broader engagement toolkit** — features like surveys, recognition, and campaigns (all surfaced through recommendations) compound the adoption gains. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations sequence these tools for maximum impact. Already a MangoApps customer? Check out the MangoApps Customer Portal for more details. Not a customer? Contact us to learn more. --- # How To Improve Collaboration With A Modern Intranet **Author:** Mason Hager **Published:** 2022-09-15 **Category:** company-collaboration A modern intranet platform can do wonders for your organization. In addition to increasing workplace productivity, consolidating content and resources, and boosting employee engagement and communication, it also encourages and improves team collaboration across departments, offices, and isolated workers.  Many organizations have siloed business units or office locations that function independently. Although they are all […] A modern intranet platform can do wonders for your organization. In addition to increasing workplace productivity, consolidating content and resources, and boosting employee engagement and communication, it also encourages and improves team collaboration across departments, offices, and isolated workers.  Many organizations have siloed business units or office locations that function independently. Although they are all part of the same company, they don’t often interact with each other. With a modern intranet platform, your company can house all of its resources, tools, and people in one place. This creates an effective workspace and sense of community. By implementing a modern intranet platform, previously detached employees can connect, communicate, and collaborate with colleagues across the company. 5 ways a modern intranet can improve team collaboration: 1. Share knowledge and information With a modern intranet, roadblocks that once kept your employees from sharing information, knowledge, and ideas fall to the wayside. With a convenient and intuitive modern intranet, employees can instantly share and update information, making collaboration effortless. Neglected emails, missed phone calls, and impossible-to-schedule meetings are no longer an issue with up-to-date news feeds, instant messaging, and company calendars. You can even dedicate space to new ideas and suggestions that every employee can contribute. This helps create an inclusive workspace where everyone’s voice has reach.  2. Connect with colleagues Often, employees have limited means of communication with colleagues they don’t usually encounter. When working for a company with multiple locations and departments, reaching people outside your team can be difficult and time-consuming. But with a modern intranet, it’s easy to create a direct line to anyone in the company, creating vast opportunities to improve team collaboration. A searchable directory of all your employees enables you to find colleagues based on their title or interests. This can unearth experts you were previously unaware of, who might offer a fresh perspective on a difficult project. 3. Search within team workspaces Keeping relevant colleagues informed is essential when working in a specific department or project. With searchable team workspaces, groups of pertinent employees can work together on projects without overwhelming others with unnecessary information. Plus, the search function makes it easy to access the materials and data you need quickly. Dedicated team workspaces make collaboration straightforward, becoming second nature. With a modern intranet, files and information are stored in an easily accessible repository. This creates a highly beneficial collection of data that aids cross-location collaboration and future employees. Read more about the impact of search. 4. Enlighten employees with company pages Keep employees up to date with company pages to improve team collaboration. Whether displaying long-term content regarding company culture, or ever-changing content like weekly lunch menus, company pages act as an accessible, informative area for all employees. With a company page to bring employees together, increased collaboration and engagement instinctively follow. By predominantly displaying company-wide information, employees of all ranks are equally equipped in understanding the organization’s core values. This results in confident employees who are comfortable collaborating and openly communicating. 5. Leverage a central hub of communication In the end, a modern intranet platform acts as a centralized communication hub for your organization’s employees. Whether collaborating to meet an important deadline or planning an after-hours get-together, implementing a modern intranet increases productivity in the workplace and creates a sense of camaraderie among peers. Collaboration creates healthy relationships between colleagues, which leads to company success. Naturally more inclusive than email, a digital work hub allows employees to discover new information. Communicate with each other without worrying about who’s been CC’d and being distracted by non-stop notifications. Newsfeeds display current tasks and discussions transparently, cultivating conversations your employees can readily join.  How Great Harvest Improved Internal Collaboration With MangoApps Great Harvest Bread Company, a bakery chain spread across the United States, was looking for a tool its franchisees and store owners could use to restore their internal communication, as the company found difficulties in effectively collaborating and sharing knowledge across locations. Relying on email as their main form of communication and outside apps for file storage, Great Harvest lacked a sense of unity. In search of a modern intranet platform that would help establish a greater sense of community, Great Harvest discovered MangoApps.  With MangoApps put into practice, collaboration and community increased tenfold. To support new franchise owners, Great Harvest used MangoApps’ discussion boards to connect veteran bakery owners with new franchisee operators. Looking for tips and tricks, owners of new Great Harvest locations can ask questions and receive expert advice from seasoned franchise proprietors.  Not only did MangoApps’ discussion boards provide a collaborative mentor/mentee mentality between franchises, but they also became the company’s primary mode of communication, which did a great deal to improve team collaboration. Before MangoApps, employees of Great Harvest were dealing with an overwhelming bombardment of email notifications, which resulted in folks simply “tuning out.” With discussion boards, employees can collaborate, share ideas, and gain knowledge on specific topics of their choosing without being pestered by irrelevant email chains. While there was once no way to collaborate and administer knowledge, employees from numerous locations soon began sharing recipes, answering questions, and distributing time-sensitive information. As a modern intranet with search functionality, intuitive communication tools, file storage capabilities, and more, MangoApps provided everything Great Harvest Bread Company needed to improve its collaboration efforts. With MangoApps as their modern intranet platform, Great Harvest transformed how its employees and store owners collaborate within the company. Where there was once a sense of isolation and uncertainty, Great Harvest franchise locations now share information and knowledge in a free-flowing manner.  To learn more about Great Harvest Bread Company’s improved team collaboration upon using a modern intranet, download our case study.  view case study --- # MangoApps Achieves HITRUST Certification **Author:** Mason Hager **Published:** 2022-09-06 **Category:** news-and-updates MangoApps Achieves HITRUST Risk-based, 2-year Certification to Further Mitigate Risk in Third-Party Privacy, Security, and Compliance. September 6th, 2022 – MangoApps is proud to announce that it is the first modern digital workplace platform to become HITRUST certified. HITRUST Risk-based, 2-year (r2) Certified status demonstrates that the organization’s digital workplace platform has met key regulations […] # MangoApps Achieves HITRUST Certification MangoApps became the first modern digital workplace platform to achieve HITRUST Risk-based, 2-year (r2) Certification — a milestone that took two years to complete and positions the platform as a validated option for regulated industries where data security requirements are not negotiable. The announcement, made September 6th, 2022, reflects a deliberate decision to pursue the most rigorous independent security validation available to enterprise software vendors, rather than self-attesting compliance or accumulating individual audits across multiple frameworks. ## What HITRUST certification actually means The Health Information Trust Alliance (HITRUST) was founded in 2007 to solve a specific problem: organizations in healthcare and other regulated industries were conducting independent security assessments of every vendor they worked with, and vendors were undergoing dozens of overlapping audits to satisfy different customers' requirements. The result was redundancy on both sides — buyers repeating work, vendors proving the same facts in different formats. HITRUST addressed this by creating a unified assurance program that incorporates federal and state regulations, industry standards, and multiple security frameworks under a single certification. A vendor that achieves HITRUST certification has, in a single process, demonstrated compliance with requirements that would otherwise require separate assessments for HIPAA, HITECH, NIST, ISO 27001, and PCI DSS, among others. The Risk-based, 2-year (r2) certification — the tier MangoApps achieved — is the most rigorous level in the HITRUST program. It requires both automated quality assurance checks and manual review by HITRUST assessors. The "2-year" designation means the certification covers a validated, two-year window of compliance evidence, not a point-in-time snapshot. Maintaining r2 status requires ongoing compliance activity and re-certification, which means the certification remains a live signal rather than a historical artifact. "The HITRUST Assurance Program is the most rigorous available, consisting of a multitude of quality assurance checks, both automated and manual," said Bimal Sheth, Executive Vice President, Standards Development and Assurance Operations at HITRUST. "The fact that MangoApps has achieved HITRUST Risk-based, 2-year Certification attests to the high quality of their information risk management and compliance program." ## Why regulated industries require HITRUST as a procurement filter Healthcare organizations, financial services firms, and government agencies face a recurring challenge when evaluating enterprise software: the vendor landscape does not converge on a single compliance standard. Some vendors hold SOC 2 Type II; others hold ISO 27001; others self-attest to HIPAA compliance without independent validation. Each represents a different assurance model, and none maps directly to the others. Procurement teams in regulated industries resolve this by adding HITRUST to their vendor qualification criteria. Because HITRUST incorporates the requirements of HIPAA, HITECH, and NIST, a vendor with HITRUST r2 certification provides evidence of compliance across all of those frameworks simultaneously — without requiring the buyer to conduct parallel assessments. For healthcare organizations specifically, HIPAA compliance is a legal requirement, not a preference. The HITRUST program converts HIPAA compliance from a claim vendors can self-report into a certification that independent assessors have validated. This distinction matters when protected health information (PHI) flows through a platform — which it does any time clinical staff use a digital workplace tool for scheduling, internal messaging, or document access. MangoApps entering healthcare deployments with HITRUST r2 certification means healthcare customers can treat the security review as resolved, rather than opening new vendor assessment cycles at each contract renewal. ## How HITRUST r2 compares to SOC 2 and ISO 27001 SOC 2 Type II is the most common security certification in the enterprise software market. It covers security, availability, processing integrity, confidentiality, and privacy controls, and requires an independent auditor to test those controls over an observation period of at least six months. SOC 2 is a meaningful baseline, and MangoApps holds it. The difference between SOC 2 and HITRUST r2 is primarily scope and regulatory mapping. SOC 2 is designed to be general-purpose — it assures buyers that a vendor's controls are in place, but it does not directly map to healthcare-specific regulations or to the full NIST cybersecurity framework. HITRUST r2 is explicitly mapped to HIPAA, HITECH, PCI DSS, NIST, and ISO 27001, which means a single HITRUST r2 certificate addresses requirements that would otherwise require four or five separate audits. ISO 27001 is the international information security management standard. It covers a vendor's information security management system (ISMS) and is widely recognized in global enterprise procurement. MangoApps also holds ISO 27001 certification. ISO 27001 and HITRUST are complementary rather than redundant — ISO 27001 demonstrates that the organization has a governed security management program; HITRUST demonstrates that the program meets U.S. healthcare regulatory requirements specifically. Holding SOC 2, ISO 27001, and HITRUST r2 simultaneously means MangoApps customers in regulated industries can satisfy security requirements across general enterprise, global operations, and healthcare-specific compliance in a single vendor relationship. ## What this means for MangoApps customers in healthcare For healthcare customers, the certification has direct operational consequences. When a health system or hospital network evaluates a digital workplace platform, HIPAA Business Associate Agreements (BAAs) are standard vendor requirements. The vendor must demonstrate not just a willingness to sign a BAA but the underlying compliance infrastructure that makes the BAA meaningful. HITRUST r2 certification provides that infrastructure evidence in the form most healthcare procurement and compliance teams recognize. Rather than submitting to a custom security assessment that may take months, MangoApps customers in healthcare can reference the certification as the validated basis for their own vendor approval process. "We are excited to finally complete the HITRUST certification process, which has been two years in the making," said Anup Kejriwal, CEO of MangoApps. "This external validation of our extreme focus on our customers' data security positions MangoApps as one of the top software vendors for regulated industries like Healthcare." The two-year timeline referenced in the CEO's statement reflects the preparation required before MangoApps could even submit for the r2 assessment. Achieving HITRUST r2 is not a documentation exercise — it requires implementing specific controls, maintaining them over time, and submitting to independent assessment of both their design and their operational effectiveness. For customers outside healthcare, the certification signals the same thing: MangoApps operates a security program designed to satisfy the most demanding compliance requirements in the market. Organizations in financial services, government, and other regulated sectors that have not yet adopted HITRUST as a procurement criterion are increasingly likely to do so, given the regulatory environment's trajectory. Holding r2 certification now means MangoApps is positioned for those requirements before customers encounter them. ## How to verify MangoApps' HITRUST certification status HITRUST maintains a public registry of certified organizations through the HITRUST MyCSF portal. Any organization can search that registry to confirm a vendor's current certification status, the scope of the assessment, and the certification's expiration date. The r2 certification covers a two-year window and requires ongoing maintenance activity to remain valid. Customers with compliance teams should verify the certification's current standing through the HITRUST registry at each contract renewal, rather than relying on a static documentation file. Active certifications in the HITRUST registry reflect the current state of the program; an expired certification in a vendor's security documentation does not. MangoApps' security documentation provides current certification status and the scope of the HITRUST r2 assessment. Compliance officers conducting vendor reviews can request the letter of certification and the HITRUST assurance report directly from the MangoApps security team. ## What the certification covers — and what it doesn't HITRUST r2 certification covers the MangoApps platform — the core digital workplace application, including communication, content, and collaboration functionality. The certification applies to MangoApps' handling of data within the platform's infrastructure, including the controls governing access, encryption, incident response, and data retention. The certification does not substitute for a customer's own HIPAA compliance program. HITRUST certification addresses the vendor's side of the business associate relationship — it validates that MangoApps has the controls in place to handle PHI in a compliant manner. It does not extend to a customer's internal policies, training, or use of the platform. Health systems implementing MangoApps still need to configure the platform according to their own information governance policies and ensure that their employees receive appropriate HIPAA training for the specific use cases they deploy. This is the standard operating model for HITRUST-certified software vendors and is consistent with how HIPAA allocates responsibility between covered entities and their business associates. ## What the certification stack means for procurement decisions HITRUST r2 is the current capstone of MangoApps' security certification stack, which also includes SOC 2 Type II and ISO 27001. Together, these certifications reflect a security program designed to satisfy requirements across multiple regulatory contexts rather than any single standard. For procurement teams comparing enterprise digital workplace platforms, the combination of SOC 2, ISO 27001, and HITRUST r2 is operationally significant: it eliminates the need for separate security assessments in most enterprise and regulated-industry contexts. Regulated-industry buyers who require HITRUST as a condition of vendor approval can proceed with MangoApps without commissioning a separate assessment process. Buyers who require SOC 2 for general enterprise security baseline, or ISO 27001 for global operations, are covered by the same certification stack. The two-year timeline to achieve HITRUST r2 certification — from program preparation through assessment to certification — reflects the depth of the underlying work. HITRUST r2 is designed to be difficult to achieve precisely because it is designed to be meaningful when achieved. For organizations that need to know their digital workplace platform meets the highest standard of independent security validation, HITRUST r2 certification is that standard. --- # MangoApps Acheives HITRUST Certification **Author:** MangoApps **Published:** 2022-09-06 **Category:** press-release MangoApps is proud to announce that it is the first modern digital workplace platform to become HITRUST certified. HITRUST Risk-based, 2-year (r2) Certified status demonstrates that the organization’s digital workplace platform has met key regulations and industry-defined requirements and is appropriately managing risk. This achievement places MangoApps in an elite group of organizations worldwide that have earned this certification. # MangoApps Achieves HITRUST Certification: What It Means for Regulated-Industry Customers HITRUST Risk-based, 2-year (r2) certification is one of the most demanding security validations available in enterprise software. MangoApps earned it in September 2022, becoming the first modern digital workplace platform to achieve this status. For organizations in healthcare, financial services, and other regulated industries, that distinction is not a marketing claim — it reflects two years of internal process work, independent assessment, and multi-layer quality review before a certificate is issued. This article explains what the certification is, how the assessment process works, what it actually validates, and what healthcare and compliance-focused organizations should understand when evaluating MangoApps for employee communications and intranet needs. ## What HITRUST certification actually requires The Health Information Trust Alliance (HITRUST) was founded in 2007 to address a structural problem in regulated industries: organizations were managing compliance with dozens of overlapping frameworks — HIPAA, NIST, SOC 2, ISO 27001, PCI-DSS — through separate audits with separate evidence packages and separate timelines. For both vendors and the customers evaluating them, this created redundant work and made security posture comparisons difficult. HITRUST created the Common Security Framework (CSF) to consolidate that landscape. The CSF maps requirements across the major regulatory frameworks into a unified control set. An organization that achieves HITRUST r2 certification has demonstrated compliance with that unified framework through a validated, externally assessed process — not self-attestation or a vendor questionnaire. The r2 tier is the most comprehensive certification level HITRUST offers. It requires an organization to document its controls across several hundred CSF requirements, submit to an assessment by a HITRUST-authorized external assessor who validates each claim with evidence, and then pass HITRUST's own internal quality assurance review — both automated and manual — before certification is issued. That QA layer is what distinguishes HITRUST r2 from SOC 2 or ISO 27001 certifications. A SOC 2 audit is rigorous, but the assessor's conclusions are not independently reviewed by a third oversight body. HITRUST's assurance program includes that additional check. For Bimal Sheth, Executive Vice President of Standards Development and Assurance Operations at HITRUST: "The HITRUST Assurance Program is the most rigorous available, consisting of a multitude of quality assurance checks, both automated and manual. The fact that MangoApps has achieved HITRUST Risk-based, 2-year Certification attests to the high quality of their information risk management and compliance program." The certification is also not permanent. HITRUST r2 status is valid for two years, with interim assessments during that period. Vendors that fail to maintain their controls during the certification window can have certification revoked. For procurement teams reviewing a vendor's security posture, that ongoing accountability is meaningful. ## Why regulated industries use HITRUST as a procurement gate Organizations in healthcare frequently use HITRUST status as a hard requirement during vendor evaluation. The reason is practical: under HIPAA's Business Associate Agreement (BAA) requirements, a covered entity that shares protected health information (PHI) with a software vendor assumes residual liability for how that vendor handles the data. Demonstrating that due diligence was applied to vendor selection — including evidence of the vendor's security controls — is essential to managing that liability. HITRUST certification provides that evidence in a form regulators and auditors recognize. An organization that can point to a current HITRUST r2 certificate from a vendor has a documented, independently verified basis for the claim that the vendor manages PHI appropriately. That documentation holds up under audit and, in the event of a breach investigation, demonstrates that reasonable precautions were taken in vendor selection. For non-healthcare organizations in financial services, government contracting, and adjacent regulated sectors, the logic is similar. The HITRUST CSF maps to PCI-DSS, NIST 800-53, FedRAMP, and other applicable frameworks. A vendor holding HITRUST r2 certification has demonstrated compliance with multiple frameworks simultaneously — reducing the security review burden for both parties during procurement. Organizations that are themselves subject to regulatory examination benefit from a streamlined vendor review when the vendor holds HITRUST certification. Instead of requesting separate evidence packages for each applicable framework, the review starts from the HITRUST certificate and associated documentation, which already covers the major frameworks the customer is likely to need. ## What MangoApps' certification validates for current customers The certification applies to MangoApps' digital workplace platform — the same platform that handles employee communications, intranet content, document management, task coordination, and frontline worker operations. For organizations currently using MangoApps in regulated environments, the certification documents several things that previously may have relied on vendor assurances: **Data handling controls are independently validated.** The controls that govern how customer data is stored, processed, and protected have been assessed by an authorized external party and reviewed by HITRUST. The organization's information risk management and compliance program is not self-reported — it is certified. **The scope covers the operational platform.** The certification is not limited to a specific product feature or a subset of the infrastructure. It reflects the information security posture of the platform that customers are actively using. **Compliance documentation is available for customer audits.** Organizations that face their own regulatory examinations can reference MangoApps' HITRUST certification as vendor due diligence documentation. The underlying evidence is structured to support that use case. This reduces the preparation burden on both sides during procurement renewals and compliance cycles. **BAA execution has a documented security basis.** Healthcare organizations that share PHI through the platform — for example, using MangoApps for clinical staff communications, scheduling notifications, or HR document distribution — can execute a Business Associate Agreement with a documented security foundation. HITRUST certification is often the specific prerequisite that makes BAA negotiations straightforward rather than extended. ## What prospective customers should ask during evaluation For organizations currently in procurement, HITRUST r2 certification shifts the relevant questions. The foundational question — does this vendor have a serious security program? — has an externally validated answer. The more productive evaluation conversations focus on scope and continuity. **Which CSF control categories does the certification cover?** The HITRUST CSF maps to HIPAA, NIST 800-53, ISO 27001, PCI-DSS, and others, but the specific controls assessed may vary. Organizations with particular regulatory obligations should confirm which categories are in scope for the MangoApps certification and whether those categories address their compliance requirements. **How does certification scope interact with deployment architecture?** MangoApps supports public cloud, private cloud, and on-premise deployments. HITRUST certification scope and applicable controls can vary by deployment model. IT and compliance teams should clarify this during the technical review — not after contract execution. **What does the renewal timeline look like?** HITRUST r2 certification is valid for two years. Organizations entering multi-year contracts should verify when the certification was issued and when renewal assessment is expected, to confirm that certification remains current throughout the contract period. Certification continuity is a reasonable question to include in contract terms. **What BAA terms apply and what do they cover?** HITRUST certification enables BAA execution but does not define the BAA's specific terms. Healthcare organizations should request the BAA template during the sales process and review scope definitions, data processing descriptions, and breach notification requirements before signing. The earlier in the process this review happens, the smoother the execution. ## How HITRUST compares to other security certifications in vendor evaluations Procurement teams evaluating digital workplace vendors encounter several types of security certification. Understanding how they relate to each other — and to HITRUST — clarifies what each one actually validates. **SOC 2 Type II** is the most common security certification in enterprise SaaS. It assesses the operating effectiveness of controls related to security, availability, processing integrity, confidentiality, and privacy over a defined audit period, typically six to twelve months. SOC 2 Type II is rigorous and meaningful, but its scope is narrower than HITRUST in regulatory framework coverage, and there is no independent QA layer that reviews the assessor's conclusions. **ISO 27001** is an international standard for information security management systems. It requires independent auditing and ongoing surveillance, making it comparable to SOC 2 in rigor. It covers information security broadly but does not include the HIPAA-specific control mappings that U.S. regulated healthcare organizations require. **HITRUST r2** maps to more regulatory frameworks simultaneously than either SOC 2 or ISO 27001, requires a more prescriptive evidence package, and includes HITRUST's own quality review of the assessor's work. For healthcare procurement specifically, HITRUST r2 functions as the single sufficient credential because it addresses HIPAA, state regulations, and broader security frameworks in one assessed, documented package. For organizations where HITRUST is the industry standard — healthcare, health-adjacent, and federally regulated environments — a vendor holding current HITRUST r2 certification removes a significant portion of the security review process. For organizations where HITRUST is not a hard requirement, SOC 2 Type II and ISO 27001 address most of the same underlying concerns. The practical question for procurement teams is which certifications their own regulatory context requires. ## Compliance posture as a long-term vendor evaluation criterion Achieving HITRUST r2 certification is a milestone, not a conclusion. The two-year validity period requires the certified organization to maintain the controls assessed during the audit — not just achieve them once. HITRUST's ongoing assurance activities and interim assessments enforce that continuity. Organizations that fail to maintain their controls face certification revocation rather than a quiet expiration. For regulated-industry organizations selecting a long-term platform partner, that ongoing commitment is as relevant as the initial achievement. A vendor that entered the HITRUST certification process two years before earning it, and that maintains certification through subsequent renewal cycles, has demonstrated an institutional investment in security infrastructure — not a certification completed once for procurement purposes. The HITRUST CSF itself evolves as the regulatory environment changes. New control categories are incorporated, existing mappings are updated, and assessment methodology is refined based on emerging threats and regulatory guidance. Organizations maintaining HITRUST certification remain calibrated to those changes across renewal cycles — which means customers of HITRUST-certified vendors benefit from that ongoing calibration without having to track individual regulatory changes themselves. ## Practical steps for compliance-focused organizations For organizations considering MangoApps in regulated environments, or currently using the platform and updating vendor risk documentation, the concrete steps are straightforward. Request the current HITRUST certification documentation and verify that the certificate is active, the scope covers the deployment configuration you're using, and the validity period extends through your contract term. For healthcare organizations, confirm BAA availability and review the agreement's specific terms before contract execution. For internal compliance documentation, the certification provides externally validated evidence that MangoApps meets the control requirements of the frameworks mapped in the HITRUST CSF. Reference the specific CSF categories relevant to your regulatory obligations in your vendor risk assessment. For IT teams managing the MangoApps deployment, the certification's existence does not eliminate the need for internal security review — it provides a validated baseline to build from. Your organization's access controls, data classification practices, and incident response integration with the platform are complementary to the vendor's certification. MangoApps' HITRUST r2 certification answers the foundational security questions that regulated-industry organizations bring to vendor evaluation. For healthcare and compliance-focused organizations building the business case internally, the certification reduces the documentation burden at procurement, supports BAA execution, and provides a validated basis for ongoing vendor risk management throughout the contract lifecycle. --- # Introducing Mango Recorder **Author:** Rebecca Stone **Published:** 2022-08-25 **Category:** modules-features It can be challenging to maintain personal connections among a hybrid or distributed workforce. One way to keep remote workers from feeling isolated is to incorporate asynchronous video communication, allowing people to make and send quick videos to each other. With MangoApps 16.0, we introduced a tool that we believe is essential for hybrid and […] ## Introducing Mango Recorder It can be challenging to maintain personal connections among a hybrid or distributed workforce. Over 80% of the global workforce is deskless, making async video a critical channel for reaching workers without a desk or corporate email. One way to keep remote workers from feeling isolated is to incorporate asynchronous video communication, allowing people to make and send quick videos to each other. With MangoApps 16.0, we introduced a tool that we believe is essential for hybrid and fully remote workspaces: Mango Recorder. It is available now for all MangoApps customers and can be enabled by an administrator from the domain settings panel — no separate installation or third-party subscription required. The Mango Recorder app allows users to more personally connect with people without endless calls. It also eliminates the need to schedule calendar time with a large group of people. These feats can both feel nearly impossible for distributed teams — especially when they're across different time zones. Async video tools reduce meeting load for distributed teams by eliminating the need to coordinate across time zones for routine updates and [training and employee engagement](/articles/learning-and-development-strategy-embedded-in-daily-work) delivery. With Mango Recorder, you can record quick videos of your screen and camera and utilize screen capture. You can even annotate these images and videos and add a call-to-action button to a video. Mango Recorder screen captures and videos integrate with posts, pages, campaigns and courses within MangoApps, making them easy to add as media throughout the platform. A single-hub approach to video, forms, and communications reduces the number of disconnected tools employees navigate daily — competitors cite 6–8 tools as the norm as part of broader [employee communications](/solutions/employee-communications) sprawl. ## Screen and Camera Bubble Recording - Allows you to simultaneously record your screen and add a camera bubble to appear in the recording alongside your screen. - Users have the option of just including a profile photo in the bubble, or nothing at all. This bubble can be moved to any part of the screen at any time during a recording. ## Capture and Record Screens - Allows users to capture or record a full window or region - Supports selecting a desktop when a user has a multi-desktop setup ## Annotation Tools - Annotation tools such as arrows, text boxes and more, can be added to captures and recordings. - Users can define amount of time the arrow, text box etc. stays on the screen during a video. ## Video Trimming - Videos can be trimmed any number of times - The user can revert back to the original before saving ## Closed Captions (CC) in Multiple Languages - Mango Recorder can automatically generate closed captions (CC)/subtitles for the audio in videos by using the MangoApps AI engine in up to six languages being used in the domain. - Closed caption files can also be uploaded in any language. - The system will detect a user's language preference and will make that language the default for the closed captions when the user plays the video. ## Call-to-Action Button for Videos - Ability to add a call-to-action button to any video to link to a form, survey or internal or external URL or download a resource - Action button text, text color, button color and button link can all be customized - The call-to-action button is shown while the video is played, as well as at the end of the video. ## Engagement Insights Engagement insights can be viewed within MangoApps or downloaded in an .xls format, including: - Video duration (for videos only) - Total views - Unique views - Downloads - Reactions - Pinned (saved) - Call-to-Action (CTA) Clicks (for videos with buttons only) Async video with built-in engagement analytics — views, CTA clicks, reactions — gives communicators measurable reach data that calendar-based meetings cannot provide. This positions Mango Recorder's Engagement Insights not as a reporting add-on but as a direct way to prove communication ROI. Per McKinsey research, 81% of leading companies effectively use data and analytics tools; Engagement Insights brings that same discipline to internal video communications. Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback — and tracked engagement data is one concrete way to demonstrate that listening is happening. ## Privacy, Sharing & Long-Term Storage - Users can set the permissions and sharing settings for all video recordings and screenshots taken with Mango Recorder, and even set default settings for these. - All of the recordings and screen captures taken with Mango Recorder are saved in a new MangoApps module called My Recordings, which has a clean, searchable and filterable interface. ## Integrated with Other MangoApps Modules - Recordings created with Mango Recorder are automatically available within MangoApps to embed in a post. - Recordings that other users have created with either full company or public access can also be added to posts and campaigns. - Recordings can also be embedded on pages or used as chapters inside of a course using the LMS module — making Mango Recorder a natural fit for [employee engagement courses](/articles/learning-and-development-strategy-embedded-in-daily-work) and onboarding programs. Mango Recorder works within the same no-email, mobile-first platform that already serves frontline workers through the [MangoApps employee app](/solutions/employee-app) — async video is not a separate tool but part of a unified frontline experience. This matters because improved frontline communication and single-hub access have been linked to a 26% reduction in employee turnover. Videos are a much more effective way to communicate information — viewers retain up to 95% more from videos than they do from text. Using Mango Recorder can better align teams, encourage quicker support, add a personalized touch to sales outreach, create [employee engagement training](/articles/learning-and-development-strategy-embedded-in-daily-work) content at scale, and produce smooth presentations without scheduling overhead. ## How to Get Started with Mango Recorder Mango Recorder is available to all MangoApps customers running version 16.0 or later. To enable it for your team: 1. **Admin activation:** A domain administrator enables Mango Recorder from the MangoApps admin panel under Modules. No third-party software or separate license is required. 2. **User access:** Once enabled, users access Mango Recorder directly from the MangoApps interface — desktop browser or the mobile app — without installing additional software. 3. **Permissions:** Admins can configure default sharing and privacy settings at the domain level; individual users can override these for each recording. 4. **Storage:** All recordings are stored within MangoApps in the My Recordings module, subject to your organization's existing storage plan. Not yet a MangoApps customer? Contact the MangoApps team to request a demo or learn about plans that include Mango Recorder. You can also explore the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) to see how async video fits into a broader employee communications strategy. ## Frequently Asked Questions About Mango Recorder ### When was Mango Recorder released and is it available now? Mango Recorder launched with MangoApps 16.0 and is available now for all customers on that version or later. Existing customers can confirm their version and enable the module through the admin panel immediately. ### What are the system requirements for Mango Recorder? Mango Recorder runs within the MangoApps platform and does not require a standalone desktop application. It is supported on modern browsers (Chrome, Edge, Firefox) on Windows and macOS, and is accessible via the MangoApps mobile app on iOS and Android for playback and sharing. Screen recording and camera bubble features require a device with a camera and microphone and browser-level permissions granted by the user. ### How does Mango Recorder compare to standalone screen-recording tools? Standalone screen-recording tools require employees to record, export, upload to a file-sharing service, and then link or attach the file in a separate communication — typically adding 3–5 steps and at least one additional tool to the workflow. Mango Recorder eliminates those steps: recordings are created, stored, shared, and measured inside the same platform employees already use for posts, campaigns, and [employee engagement](/solutions/employee-communications) surveys and questionnaires. Per the IDC MarketScape 2024 assessment, unified digital workspace platforms that consolidate cloud-based productivity applications reduce tool-switching friction and improve adoption — see the [IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment](/resources/idc-marketscape-2024) for context on how integrated platforms are evaluated. **Already a MangoApps customer?** Check out the MangoApps Customer Portal for full technical documentation and release notes. **Not a customer?** Contact us to learn more or request a demo. --- # ROI Series, Pt. 3: Helping people find information faster **Author:** Christos Schrader **Published:** 2022-08-17 **Category:** knowledge-management This is part 3 of our ROI blog series, where we discuss your employees’ ability to find things quickly In part one of this blog series, we summarized the challenges around quantifying digital work hub ROI. Then, part two zeroed in on replacing email for internal collaboration. In this article, we’ll cover the next section […] ### This is part 3 of our ROI blog series, where we discuss your employees' ability to find things quickly In part one of this blog series, we summarized the challenges around quantifying digital work hub ROI. Then, part two zeroed in on replacing email for internal collaboration. In this article, we'll cover the next section of our ROI Report: helping people find information faster by improving and unifying search. The short answer: a [modern intranet](/solutions/modern-intranet) with unified search reduces time spent looking for information by at least 25%—and up to 80% for organizations with fragmented systems. For a 2,500-person company, that translates to 3,250 hours saved every week. The sections below show how we get to that number, what it means for desk and frontline workers, and what metrics to track once you've deployed. ### Poor search experience causes frustration and wastes time How much of your week do you spend searching for information or files? According to IDC, employees spend roughly 2.5 hours per day searching for information—that's more than 14 hours per week for desk workers, and around three hours for frontline workers. These numbers can vary wildly from company to company and industry to industry. For example, a nurse or doctor is likely to need to reference policies more frequently than a retail store associate. Separate from search time, employees lose over 4 hours per week switching between disconnected systems—compounding the total productivity loss well beyond what search alone accounts for. Regardless of the specifics for your workplace, it's a safe bet that people waste time daily trying to find things. The issues that arise from this can vary by role. Many desk workers, for example, work across many different digital platforms every day. As a result, they struggle to keep track of which conversations are happening on which platform. When they need to reference a discussion from a few months ago, or find a specific version of a file, they embark on a journey through the annals of their wide digital footprint. For example, let's say you're a salesperson. A few months ago, someone from the design team sent you a mockup that you ultimately didn't wind up using. Now, you have a project that could benefit from a similar design. You're hoping to find a specific version of a file they sent so you can use it as a reference. What happened to that file? Is it in the downloads folder on your computer? Is it buried somewhere in the nested folders on your intranet? Maybe OneDrive or some other file sharing solution? Your searches in all of these places return nothing. Did you discuss it over email? Slack? Teams? You can't remember, so you have to go to each of these places one at a time. Since you don't remember exactly what the file was called or what was said about it, you'll wind up trying various search terms in each. This can spiral into an hours-long search that doesn't end in success. This is especially true when you're using platforms that offer a poor, outdated search experience. At a certain point, you give up. This means several things at the same time: 1. You just wasted two hours that you could have spent on something productive 2. The project stalls, and you may have to get a designer to do that same work over again 3. You become frustrated, and your mindset may negatively impact the rest of the work you do today When you compound these issues across a large desk-based workforce where they come up regularly, you are looking at a major problem for your enterprise. ### Frontline search issues are a drain on resources Frontline workers, on the other hand, tend to have less frequent issues where they need to find something and can't. However, theirs tend to be harder to resolve, due to the lack of tools that are set up to help them find information faster. Per Emergence Capital, 80% of the global workforce is deskless—yet most knowledge management tools are built for desk workers with corporate email addresses and VPN access. That gap is where information-access friction becomes a retention and cost risk: frontline employee replacement costs range from $4,400 to $15,000 per worker, meaning that friction around finding information isn't just a productivity issue—it's a direct financial exposure. For example, let's say you are a store employee at a large retail chain. You're getting ready to have your first child, so you need to understand the company's childcare leave policies. Unfortunately, you don't know where to find that information, or even who to ask. A good first step would be to ask some of your colleagues while on your shift. Unfortunately, they don't know. You spend some time perusing the random assortment of policy documents in your break room, but they are disorganized. You are unable to find anything pertinent to your situation. Even if you do find something, you have little confidence that it is up to date. It is unclear how recently the papers were printed. Traditional intranets compound this problem: they deliver static, ungoverned content that becomes stale over time, making search failure more likely the longer the system runs without active governance. You ask your manager, and they tell you that you need to reach out to HR. If you're lucky, maybe they give you someone's email address or phone number. At this point, you have reached the bounds of what you can do to solve this problem while on shift. Your only recourse is to continue chasing down your company's elusive childcare leave policies in your free time. From here, you'll probably have to speak to several different HR employees before you get an answer. Depending on how promptly they each reply, there could be a lengthy delay before you finally get access to the information you were looking for. Over the course of days or weeks, this has created a number of problems: 1. You've wasted a good deal of your free time outside of work 2. Something like 5–10 different people have had to take time out of their day to help you 3. You probably received several conflicting answers to your question. Thus, you may end with a poor understanding of the policy, or low confidence in the final answer you received Per Social Edge Consulting, 91% of organizations operate an intranet—yet nearly a third of employees never log in to it, and only 13% use one daily. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools. Those numbers suggest that most intranets are not solving the frontline access problem; they're simply existing alongside it. ### A modern intranet helps people find information faster When you implement a [modern intranet](/solutions/modern-intranet) like MangoApps, both desk and deskless workers experience a dramatic reduction in the time it takes to solve problems like the ones above. Desk workers will no longer have to waste hours sifting through files and conversations in multiple places. Instead, there's a single search bar that returns everything, including files and conversations from other employees that could be relevant. Universal search spans connected storage platforms—SharePoint, Google Drive, Box, and Dropbox—from a single query, eliminating platform-hopping entirely. The results are organized with filters that quickly get you to the right item. MangoApps also connects multiple AI engines—including OpenAI, Gemini, and Azure OpenAI—trained on company data, making search contextually aware of roles and permissions rather than relying on keyword matching alone. For frontline workers, the intranet and company communications are available in an intuitive mobile app. Critically, no corporate email address or VPN is required—workers can reach HR documents and SOP operations guides directly from their phone. The HR team maintains a [knowledge base](/key-features/knowledge-bases) within the intranet with all of their policy documents. This single source of truth, governed by a [content governance engine](/key-features/content-governance-engine), is always the place to find the most updated documents. Thus, our retail worker seeking childcare leave policies will get a clear answer in minutes by searching from their phone. For more on how this plays out in a retail context, see [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling). Furthermore, for less straightforward questions, they can find and message the relevant person from the people directory. This is practically guaranteed to help them find information faster. The end result is that everyone in the company is more connected to information, files, and each other. The scope of positive changes that can manifest as a result is difficult to capture and measure. ### Measuring the impact of improved search In our ROI Report, we examine a hypothetical company with 2,500 employees that is considering switching to MangoApps. We call them ACME. 2,000 of their employees are in frontline roles, and the other 500 are desk workers. For the purposes of ROI calculation, we set aside the downstream effects outlined above. The numbers focus exclusively on time saved on searching. Industry research states that a modern intranet reduces time spent searching for information by roughly 25%. We estimate that this is a conservative figure for the types of companies we work with. Occasionally, prospects come to us with extremely convoluted paths to information. For companies like these, we are able to reduce their time spent searching by up to 80%. Taking the more conservative figure, a 25% reduction in searching time for ACME works out to a time savings of 45 minutes a week per frontline employee and 3.5 hours a week per desk worker. That's a total of 3,250 hours per week across the organization. As stated above, these are pretty conservative numbers, and in a lot of cases, they can be far higher. Furthermore, there are many other downstream effects, some of which will be captured in other posts in this series. Helping people find information faster can contribute to reductions in duplicated work, as well as improving employee sentiments and engagement. When you remove barriers between your people and the work they are trying to do, the result is better performance. For an independent evaluation of how MangoApps compares to other intranet and employee experience platforms on these dimensions, see [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report). ### What metrics should you track after deployment? Decision-makers reading an ROI series naturally want to know what to measure once the platform is live. The metrics that matter most for search and information access fall into three categories: **Usage and adoption:** Track daily active users against the 13% industry baseline (per Social Edge Consulting) and set a target above it. MangoApps customers have reached 90% frontline adoption within the first six months in large enterprise deployments, driven by search and access improvements that sustain engagement beyond initial rollout. Per SWOOP Analytics, the six-minutes-per-day benchmark for traditional intranet tools is a low bar—aim for meaningful session depth, not just logins. **Time recovered:** Measure average time-to-answer for common HR and policy queries before and after deployment. The IDC baseline of 2.5 hours per day spent searching gives you a pre-deployment anchor. A 25% reduction is the conservative target; track whether your organization trends toward the 80% ceiling as governance matures. **Downstream cost avoidance:** Duplicated work, HR escalations, and manager interruptions all carry a cost. With frontline replacement costs ranging from $4,400 to $15,000 per worker, even modest improvements in information access that reduce frustration-driven attrition produce measurable savings. Tie search improvement data to your quarterly retention numbers to surface this connection. For a broader view of how these metrics fit into workforce operations planning, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the benchmarks HR and operations leaders are using this year. ### How long until you see ROI, and what does implementation involve? Implementation timeline is one of the first questions decision-makers ask after reviewing ROI projections. The honest answer depends on your current environment, but a few reference points are useful. MangoApps is designed so that experiences can be built in minutes rather than months, with no IT-led customization required for initial deployment. The platform's [company portal](/key-features/company-portal) and knowledge management [libraries](/key-features/libraries) can be configured by HR or communications teams without developer involvement. MangoApps customers have reached 95% full adoption within 90 days—a figure that reflects adoption outcomes, not just setup speed. For organizations with highly fragmented systems, the first measurable ROI signal typically appears within the first 30–60 days as search consolidation reduces the most acute platform-hopping behavior. The 3,250-hours-per-week figure for a 2,500-person organization assumes steady-state adoption, which most customers reach within a quarter. If you want to see how these numbers apply to your specific headcount and role mix, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) includes benchmarks that can help you calibrate the estimate before you run a formal ROI calculation. ### Next steps In the next post in this series, we will tackle the impact of consolidating your tech stack. To see how these numbers might look for your team, check out our ROI Calculator. Or, read our ROI Report to get a full breakdown of how we view ROI. For a real-world example of unified search and knowledge management in action, see [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study). --- # What Do Frontline Employees Actually Want? **Author:** Mason Hager **Published:** 2022-08-09 **Category:** news-and-updates It’s easy to justify equipping your desk employees with the proper tools to do their daily job as they generally work from one location. But what about your frontline and deskless employees?  Frontline workers face a whole other set of barriers to communication that can make it difficult for them to be properly engaged. As […] ## What Do Frontline Employees Actually Want? It's easy to justify equipping your desk employees with the proper tools to do their daily job as they generally work from one location. But what about your frontline and deskless employees? Frontline workers face a whole other set of barriers to communication that can make it difficult for them to be properly engaged. Per Emergence Capital, 80% of the global workforce is deskless — yet these workers are routinely excluded from the same communications desk workers receive by default, simply because they lack a corporate email address or VPN access. As they are primarily mobile and not always reachable, work can quickly become very isolating and disengaging. One concrete solution to these issues is implementing an Employee SuperApp that works on personal devices without requiring a corporate email or VPN. But at a more prescriptive level, there is a lot you can do to start to identify the gaps. **A few questions you should ask internally:** - Do your frontline workers have a mobile-first way to receive company communications without logging into a desktop or VPN? - Do they understand how their daily work connects to the company's broader goals? - Do they have easy, on-demand access to the tools, training, and resources they need to do their jobs? If the answer is no to any of these three questions, then it might be time to reassess what your frontline workers actually want. From our experience, we have found that what frontline workers want is: - To feel like they matter to the company and their voices are heard - To understand the company's big picture goals (and how they contribute to those goals) - Easy access to technology and resources - To stop receiving irrelevant company communications When you start to take those factors into account, you will naturally see employee engagement levels rise among your frontline workforce. This can lead to increased efficiency, improved employee satisfaction, and more. The cost of ignoring these signals is real: replacing a single frontline employee costs between $4,400 and $15,000, making disengagement a direct financial risk, not just a culture problem. --- ## How to Act on These Insights Understanding what frontline employees want is only half the equation. Here are three concrete first steps organizations can take without waiting for a full platform rollout. **1. Audit your current communication channels for frontline reach.** Per Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in, and only 13% use it daily. If your primary communication channel is a desktop intranet, a significant portion of your frontline workforce is structurally unreachable. Start by mapping which channels your frontline workers can actually access from a personal mobile device, without a VPN or corporate email. **2. Run a targeted employee engagement survey focused on tool accessibility and communication relevance.** Frontline workers who feel unheard rarely volunteer that feedback unprompted. A short employee engagement questionnaire — five to eight questions focused on whether workers receive relevant information, understand company goals, and can access resources on the go — surfaces the specific gaps faster than any top-down audit. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) outlines the communication gaps most commonly reported by frontline teams. **3. Prioritize role-targeted, AI-curated communications over broadcast messaging.** The "stop receiving irrelevant communications" want maps directly to a concrete capability: AI-powered feeds that filter and surface content by role, location, and shift. Per IDC, employees already spend 2.5 hours per day searching for information — irrelevant noise compounds that problem. An employee experience platform that delivers role-targeted content by default eliminates the noise without requiring workers to configure anything themselves. For retail teams specifically, the [Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) shows how targeted communications reduce operational friction at the store level. Organizations that have acted on these steps report measurable outcomes. PetSmart reported a 4x industry engagement multiple after deploying a mobile employee app. OU Health achieved 87% workforce engagement within a few months of launching a branded employee app. These results are not outliers — they reflect what happens when frontline workers get the same quality of communication infrastructure that desk workers have always had. For a deeper look at how [employee engagement solutions](/solutions/employee-engagement) translate into retention and performance outcomes, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) provides a useful benchmark framework. --- ## Webinar — What Do Your Frontline Employees Actually Want? Want to learn more about how you can actually engage your frontline workers? Check out this webinar where one of our team members does a deep dive into how you can better engage your frontline workers and equip them with the tools to succeed with an Employee SuperApp. **In this webinar, you'll learn:** - Why your frontline workers often feel disconnected from management - How you can properly equip frontline workers with modern technology - How you can keep your frontline workers engaged and in the loop Watch the webinar: What Do Your Frontline Workers Actually Want? --- ## What Is an Employee SuperApp and Why Does It Matter for Frontline Teams? An Employee SuperApp consolidates communications, task management, training, and resource access into a single mobile application that works on personal devices — no corporate email, no VPN, no IT provisioning required. This matters because the structural barrier for most frontline workers is not motivation; it is access. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools — a figure that reflects how poorly traditional platforms serve workers who are not at a desk. A unified employee experience platform changes that equation by meeting workers where they already are: on their phones, between shifts, on the floor. For industries like [retail](/industries/retail) and [hospitality](/industries/hospitality), where shift-based schedules make synchronous communication nearly impossible, a mobile-first app is not a convenience — it is the only realistic channel for consistent engagement. The [MangoApps recognition in a leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) reflects how this category of platform is being assessed against enterprise-grade communication and engagement standards. --- ## What Should You Measure to Know If Frontline Engagement Is Working? Engagement is not a feeling — it is a set of measurable behaviors. The right employee engagement software surfaces leading indicators before turnover or productivity loss becomes visible in operational data. Key metrics to track include: - **App adoption rate within the first 90 days** — a proxy for whether the tool is actually accessible and useful to frontline workers - **Content engagement by role and location** — identifies which teams are receiving relevant communications and which are being flooded with noise - **Survey response rates on employee engagement questionnaires** — low response rates signal distrust or disengagement, not just survey fatigue - **Training completion rates** — per Gallup's research on employee engagement and development, workers who have access to learning opportunities are significantly more likely to stay; the connection between training and employee engagement is one of the strongest levers available to frontline managers For organizations building out a measurement framework, [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) provides current benchmarks on engagement drivers that apply directly to frontline and deskless populations. --- # Campaigns Provide Targeted Communications with a Personalized Experience **Author:** Rebecca Stone **Published:** 2022-08-04 **Category:** modules-features Internal communications are a crucial piece of running a successful company. But it’s often neglected and under-funded. The most successful companies take a savvy, marketing-adjacent approach when it comes to pushing information out to employees. With that in mind, the new Campaigns function in MangoApps enables internal communications teams to operate more efficiently. They can […] # Campaigns Provide Targeted Communications with a Personalized Experience Internal communications programs almost universally fail on the same structural problem: most of what gets sent never reaches the employees it was meant for. Per Social Edge Consulting, 91% of organizations run an intranet, yet nearly a third of employees never log in to it, and only 13% use it daily. Per IDC, employees spend an average of 2.5 hours per day searching for information — not because the information doesn't exist, but because the delivery infrastructure can't reach most of the workforce. The failure is architectural. Broadcast communication — send-to-all email, intranet posts that require employees to seek them out — was designed for office-based workers at desks with corporate email addresses. Per Emergence Capital, 80% of the global workforce is deskless. The majority of employees in healthcare, retail, manufacturing, and logistics have historically been unreachable through the channels most communications teams use by default. What gets published on an intranet stays there, waiting for employees who never arrive. MangoApps Campaigns addresses this at the infrastructure level. Rather than publishing content and hoping employees find it, Campaigns pushes targeted messages through the channels employees actually use — email, SMS, and mobile — with real-time analytics that confirm who received and opened each send. The result is an [employee communications](/solutions/employee-communications) function that operates with the discipline of an external marketing program, not the assumptions of an internal broadcast. ## Why broadcast communication doesn't reach most employees The baseline assumption behind most internal communications tooling is that every employee has a corporate email address and checks company systems from a computer during business hours. For office-based knowledge workers, this is largely accurate. For the majority of the workforce, it isn't. Per SWOOP Analytics, the average employee spends six minutes per day using intranet tools. That figure isn't evidence of disengagement — it's evidence of how poorly intranet tools fit into the actual flow of frontline work. A distribution center associate clocking in for a shift, a healthcare aide moving between patient rooms, a retail worker on the floor: none of these employees can pause to log into a desktop portal. The six minutes isn't a failure to communicate; it's a measurement of the mismatch between the tool and the workforce. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), employee engagement correlates directly with whether workers feel the organization is paying attention to their experience. Communications infrastructure that reaches office workers but excludes frontline employees communicates something implicit — and it shows up in engagement data. Campaigns closes this gap by pushing messages to employees regardless of whether they would have sought the content out. Workers receive communications via SMS and mobile without a corporate email address or VPN access. Targeting rules determine who receives which message based on job title, location, hire date, team membership, or engagement level on the platform. Campaign messages bypass notification settings entirely, reaching employees even when they're not actively using the platform. ## What targeted delivery changes in practice The shift from pull to push communication compounds over time in ways that aren't obvious at first. A compliance update posted to an intranet reaches employees who happen to check it. A Campaign sends it directly to the employees who need to acknowledge it, confirms who opened it, and follows up with non-openers — automatically. A policy change that once required manual tracking to confirm acknowledgement becomes a documented, timestamped process with completion logged by individual. This distinction matters most for frontline-heavy industries, where the majority of employees have historically been excluded from targeted internal communications. Campaigns reaches workers without corporate email — a structural differentiator for organizations in healthcare, retail, manufacturing, and logistics, where legacy intranet tools reach the 20% and assume the 80% are covered. The outcomes are measurable. Organizations that have launched targeted, branded communications through MangoApps have achieved 87% workforce engagement within months of go-live, per MangoApps case study data. Personalized, role- and location-targeted communications drive four times industry-standard engagement rates for frontline workforces. Given that replacing a single frontline employee costs between $4,400 and $15,000, the retention value of communications that actually land is a calculable number, not a soft benefit. ## The targeting layer: who receives what, through which channel Campaigns gives internal communications teams precise control over audience definition. Segments can be built from any combination of job title, location, hire date, team membership, and platform engagement level. That last criterion is the operational differentiator: targeting by engagement level makes it possible to identify employees who have been disengaged from platform communications and reach them directly, before that disengagement compounds into an attrition signal. Delivery channel selection operates at the campaign level, not the platform level. A policy update for warehouse workers might go via SMS. An executive newsletter for a knowledge worker segment might go via email. A time-sensitive safety alert might go to both. The communications team makes the channel decision based on the message and the audience — not a default setting applied uniformly across the organization. Personalization operates at the message level. Campaign authors can customize the subject line and body to address recipients by name or include other dynamic fields. Messages that feel specific to the recipient open at higher rates — a consistent finding in external marketing research that applies with equal force to internal communications. Scheduling is flexible: campaigns send immediately or are queued in advance, with a centralized calendar view that keeps multiple team members coordinated without duplicating efforts. ## The measurement layer: converting activity into evidence What internal communications has historically lacked is the analytics infrastructure to demonstrate its own value. Campaigns provides real-time visibility into opens, unique clicks, device type breakdowns (web versus mobile), opens by location and department, and time-of-open data. These metrics do more than confirm delivery — they give communications leaders the data needed to report results to leadership, identify which segments are under-reached, and refine targeting over time. Boost functionality closes the follow-up loop. When open rates fall below expectations, teams can resend to non-openers with adjusted personalization applied at re-send. Admins can revise the message content before boosting — turning a missed first send into a second attempt with a more targeted message, rather than an identical repeat. For organizations building the business case for structured internal communications investment, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading teams are pairing campaign analytics with retention and productivity data to construct an ROI narrative for leadership. The framework is straightforward: time recovered from reduced information search (per IDC, 2.5 hours per day per employee), engagement lift measured through open and click rates, and retention cost avoided when communications programs keep frontline workers connected and informed. ## How AI extends campaign personalization Traditional campaign personalization is manual: a communications team member selects a segment, writes a message, and adds a name-merge field. The ceiling on that approach is the bandwidth of the communications team. MangoApps supports multiple AI engines — OpenAI, Gemini, and Azure OpenAI — which positions the platform to extend campaign personalization beyond manual segmentation as AI-assisted content surfacing and delivery optimization capabilities mature. Competitors in this space are moving toward AI-native content surfacing as a primary differentiator. The MangoApps multi-engine architecture is the counter-positioning: not a single vendor dependency, but a model-agnostic infrastructure that doesn't require swapping platforms when the AI landscape shifts. The practical near-term value: communications teams can use AI to draft message variations, optimize subject lines, and surface the right content for the right segment faster. The foundation is already in place. ## Templates and production logistics Campaigns includes customizable templates that require no HTML or design expertise. A communications team member can build, target, and schedule a campaign without involving IT or a design team. Custom campaigns built from scratch support images, videos, links, and buttons. The production barrier that historically made email campaigns a marketing-department task has been removed. A centralized lifecycle management interface gives a snapshot view of all campaigns: status, audience, scheduled date, and key metrics — with filtering and sorting options. This operational layer makes it possible for a small communications team to manage high-volume, multi-segment programs without losing track of what's been sent, to whom, and with what result. ## The case for replacing ad hoc communications with structured campaigns Three characteristics separate organizations where internal communications works from those where it doesn't. First, they push rather than publish. Content that sits on an intranet reaches the employees who seek it. Campaigns reach the employees who need the message — regardless of whether they would have looked for it, and regardless of whether they have a corporate email address. Second, they measure at the individual level. An open rate broken down by department, device type, and location tells a communications leader something actionable. A page view count tells them almost nothing. The analytics layer in Campaigns is designed for the former. Third, they reach every employee. Per Emergence Capital, 80% of the global workforce is deskless. Most internal communications programs are structurally built for the other 20%. Campaigns treats SMS and mobile as first-class delivery channels — not afterthoughts — which is the only architecture that covers an entire workforce. For organizations evaluating where they stand relative to the market on internal communications capability, the [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarking context for assessing communications features across competing platforms. The gap between organizations with structured, targeted communications programs and those without is widening — and the measurement infrastructure that Campaigns provides is the mechanism that makes it possible to see that gap closing in real time. --- # Thinking of adopting SharePoint? Consider these disadvantages. **Author:** Christos Schrader **Published:** 2022-07-19 **Category:** comparisons At MangoApps, we get a lot of questions about SharePoint during the sales process. It is very common for companies to come to us looking to replace an old SharePoint implementation where its disadvantages are causing problems. In other cases, companies consider us as an option alongside adopting SharePoint as they look to replace an […] # Thinking of Adopting SharePoint? Consider These Disadvantages. Most organizations evaluating SharePoint are already paying for it. It ships inside Microsoft 365 licenses, which makes it easy to treat as a sunk cost — not a new commitment. That framing is precisely where the evaluation tends to go wrong. Choosing to build an intranet on SharePoint is not a licensing decision. It is an infrastructure commitment that includes consultant fees, IT labor, ongoing governance, and the compounding cost of low adoption. Per a 2025 cost model from Awesome Technologies Inc., the first-year total for a 1,000-user SharePoint deployment runs $130,000–$426,000 when licensing, implementation, customization, and governance are included. That range excludes the cost of rebuilding when — not if — the initial implementation becomes obsolete. Before that investment is approved, the evaluation should ask several questions that SharePoint's surface appeal tends to suppress. ## The real cost is not in the license A basic SharePoint deployment for a 1,000-user organization starts at approximately $15,000. Enterprise deployments with custom integrations, multi-department governance, and migration from legacy systems reach $150,000 or more at the outset. Add two to four years of dedicated IT staffing — SharePoint requires specialists for routine content updates that business users cannot handle themselves — and the total cost of ownership diverges sharply from the licensing line item. The productivity cost is less visible but equally measurable. Per IDC, employees lose an average of 2.5 hours each day searching for information across disconnected systems. Per SWOOP Analytics, the average employee spends six minutes a day actively using intranet tools. Those two data points, taken together, describe a platform that consumes substantial IT resources while failing to deliver the adoption required to justify them. The cost isn't just in the deployment budget — it shows up every shift, in every department, as unrecovered time that compounds across quarters. Per Social Edge Consulting, 91% of organizations operate an intranet. Nearly a third of employees never log in. Only 13% use one daily. These adoption figures are not explained by employee indifference. They are the predictable result of platforms designed for one segment of the workforce and deployed to all of it — and SharePoint's architecture makes that structural mismatch more acute than most. ## Why SharePoint doesn't reach most of your workforce SharePoint's architecture assumes users have a corporate email address, a provisioned Microsoft account, and access to a desktop or laptop on a corporate network. Per Emergence Capital, 80% of the global workforce is deskless — nurses, retail associates, logistics coordinators, field technicians, manufacturing operators. For this majority, SharePoint's access model is a disqualifier before a single page loads. The nurse without a corporate email cannot receive the policy update sent through the SharePoint-connected communications platform. The warehouse supervisor without VPN provisioning cannot pull the compliance document from the document library. The hotel maintenance technician working evenings cannot access the HR self-service portal that requires a domain login and a desktop browser. In healthcare, hospitality, logistics, and manufacturing, these are not edge cases. They describe the majority of the workforce. An intranet that cannot reach 80% of employees is not a modern intranet — it is a document repository for the desk-based minority, deployed under the name of an organization-wide communications platform. Organizations that respond to low adoption by investing more in SharePoint customization typically find that adoption improves marginally, if at all. The constraint is structural: SharePoint was built for office workers, and no implementation budget resolves that. When OU Health deployed a purpose-built mobile employee app, the organization achieved 87% workforce engagement within the first few months of launch — not because their programs had changed, but because their delivery infrastructure finally reached the staff those programs were designed for. ## The integration complexity trap SharePoint's position inside the Microsoft 365 ecosystem is often presented as its primary strength. In practice, it frequently deepens the tool-sprawl problem. Organizations that deploy SharePoint often find themselves managing parallel systems — SharePoint for documents, Teams for chat, a separate platform for forms, another for recognition or training — without any of them consolidating into a coherent employee experience. Each system requires its own login, its own notification configuration, and its own onboarding cycle for every new hire. SharePoint integration complexity has become one of the most active competitive areas in the intranet market, with more than ten vendors now actively covering it as a primary differentiation theme. The activity reflects organizational reality: SharePoint integrations typically require custom development or third-party middleware, and each creates a maintenance dependency that IT must absorb as versions change. The consolidation argument is not about organizational tidiness. It is about the daily coordination overhead that tool sprawl generates across every shift. When TeamHealth consolidated more than 200 disparate systems into a single mobile dashboard for its frontline clinical staff, the primary outcome was not a higher satisfaction score. It was the elimination of the time lost to system-switching, login failures, and duplicate data entry — time that went back into patient-facing activity. That outcome is not achievable by adding integrations to SharePoint. It requires reducing the tool surface entirely, which a platform built around consolidation is designed to do from day one. ## What the evaluation should actually test A standard SharePoint evaluation focuses on feature lists and licensing. A more useful evaluation tests against the access and adoption conditions that determine whether the investment produces outcomes. **Does it reach every employee?** Can all staff access the platform without a corporate email address, VPN, or shared workstation? Can they use it from personal devices before or during their shift? In organizations with significant frontline populations, this is the single most important evaluation criterion — and the one SharePoint most consistently fails. A [modern intranet](/solutions/modern-intranet) is designed to reach staff on any device, regardless of provisioning status. **How much IT does it require on an ongoing basis?** Can the internal communications team update the company homepage without submitting a ticket? Can HR post a policy change to the right audience in minutes? SharePoint's day-to-day administration requires technical staff for functions that business users in most organizations are capable of handling directly. Platforms designed for self-service shift that work to the teams who own the content, compressing update cycles from days to minutes and removing the IT overhead that inflates SharePoint's true cost. **Does it surface relevant content?** SharePoint's native interface delivers the same undifferentiated feed to every employee regardless of role, location, department, or shift schedule. Employees accustomed to algorithmically filtered content in their personal lives encounter a static document repository at work. The result is the six-minute daily usage number from SWOOP — employees don't disengage from intranets because they lack motivation. They disengage because the platform gives them no compelling reason to return. **Is adoption measurable?** Does the platform provide policy-read confirmation rates by shift and department? Time-to-acknowledgment for compliance updates? Participation rates broken down by role and location? Without these metrics, intranet administrators operate on intuition rather than data. These leading indicators move faster than annual engagement surveys and reveal within weeks whether the platform is actually reaching the employees it was deployed for — or whether adoption is concentrated in the same desk-based 20% who would have used any platform. ## The questions SharePoint deployments typically can't answer Three years after a SharePoint implementation goes live, the organization typically faces a version decision. The current deployment is outdated. A new version is available. The consultant who built the original implementation may no longer be on contract. Custom integrations may be partially broken. The organization must decide whether to rebuild — with new consultants, new timelines, and new costs — or stay on a degrading platform until something fails. This is not a failure of execution. It is the expected outcome of deploying a platform where the maintenance obligation transfers entirely to the deploying organization. The vendor releases the update; the IT team absorbs the cost of adopting it. The business pays either way, and the cycle repeats on SharePoint's release schedule rather than the organization's own readiness. The [ClearBox 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an independent evaluation framework for assessing how platforms handle this long-term ownership question — including update cadences, vendor support models, frontline access depth, and governance structures that prevent implementations from degrading. These are the dimensions that determine total cost of ownership in years two through five, which licensing comparisons routinely leave out. ## The decision the IT team is actually making When IT teams advocate for SharePoint, they are typically optimizing for familiarity and a licensing argument that fits cleanly in a single spreadsheet row. Those are reasonable inputs. They become insufficient when they exclude the access gap, the adoption rate, and the five-year maintenance obligation. The [MangoApps employee app](/solutions/employee-app) addresses the access gap at the infrastructure level — no corporate email required, offline-capable, personal-device friendly — because the frontline access problem cannot be configured around in SharePoint. It requires a platform built around that constraint from the start, not adapted to it after the fact. The organizations that move from SharePoint to a purpose-built employee communications platform consistently report the same realization: the programs they had already invested in — recognition, training, policy communication — were already in place. The infrastructure to deliver them to the full workforce was not. Removing the access barrier is what allows existing investments to produce the outcomes they were designed for. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), the capability that most reliably predicts sustained employee engagement is whether employees receive the information they need, when they need it, without having to escalate. That is a delivery criterion before it is an engagement one. SharePoint can be deployed. The more useful question — the one that belongs in the evaluation before the contract is signed — is whether it can actually be delivered to every employee, on every shift, on every device. --- # Updates to our Search Capabilities and Algorithmic News Feed **Author:** Rebecca Stone **Published:** 2022-07-14 **Category:** modules-features As a product-led company with a heavy focus on ongoing improvement and innovation, MangoApps is always rolling out new updates and improvements. We thrive on bringing ideas from our customers to life in our product. With that in mind, here are three of the newest features that we are really excited about. We’re already seeing […] ## Updates to our Search Capabilities and Algorithmic News Feed MangoApps is rolling out three significant updates to its search engine, AI-based image features, and algorithmic news feed. If you want the short version: search is now approximately five times faster, images are fully searchable via AI text detection, and the news feed now uses an algorithm to surface the most important items first. All three features are available to existing customers through the MangoApps Customer Portal, and each requires only minimal configuration by a network admin to activate. Per IDC, employees spend an average of 2.5 hours per day searching for information — and per Social Edge Consulting, nearly a third of employees never log in to their intranet at all. These updates are designed to close that gap by making the [modern intranet](/solutions/modern-intranet) faster, smarter, and more relevant from the moment a user lands on the homepage. ## New Search Engine A product like ours lives and dies by its search engine. It's at the crux of our offering. If you can't find stuff easily, you might as well not have an intranet. We have always prided ourselves on our search function's ability to take everything your company has and narrow down search results to exactly what you need. With this update, we have made it faster and easier to do just that. The new and improved intelligent search engine can perform a best match search about five times faster than the older, data-based search engine. Universal search also extends across connected third-party storage platforms — including SharePoint, Google Drive, Box, and Dropbox — in addition to native MangoApps content, making it a genuine tool for knowledge management across your entire digital ecosystem. The new search and algorithmic feed also work on the MangoApps mobile app without requiring a corporate email address, which matters given that per Emergence Capital, 80% of the global workforce is deskless and relies on mobile access. - It finds more relevant search results. - Search more types of content such as people, teams, libraries, events, notes, trackers and forms and ideas and idea campaigns - New options to filter search results - Stores recent and saved searches - Predictive look-ahead finds matching items in different modules across the platform as you're typing out your search term(s) - The option to add a hero banner with a network-wide search integration on the homepage gives your site a wow factor and provides users with an easy way to search upon entering the platform. The hero banner search integration is configured through the [webpage builder](/key-features/webpage-builder) in your admin settings — no developer involvement required. ## AI-Based Image Features Until recently, images were difficult for computers to understand. As a result, your ability to return relevant images as search results was only as good as the tags you appended to your images. In most companies, there isn't a robust system of image tagging, so images are largely left out of search results. Now, though, we are able to use AI to detect text within images, and include that text in search results, making it as easy to find images in MangoApps as it is to find documents. Rather than treating AI as a bolt-on feature, MangoApps is built as an AI-native intranet where intelligence is foundational to search, feeds, and content surfacing — not an afterthought. The platform also supports 50+ languages with real-time translation, so search and news feed updates are accessible to global and multilingual workforces without additional configuration. - Image analysis makes images searchable. (If a user searches a word and the search engine detects that word in an image across the platform, it will come up in the search results.) - Images are automatically assigned the top hashtags (up to five) with the highest relevancy score to the image. - Images that include personally identifiable information (PII) will be detected (if data loss prevention policy rules have been activated by the network admin). The platform also supports SAML 2.0, OAuth 2.0, and SSO, so the speed and AI capabilities do not come at the cost of enterprise governance. ## Simplified, Intelligent News Feeds Since its inception, the goal of the MangoApps news feed has been to help people make sense of their jobs. All job-critical updates, conversations and action items are now put into a single feed. This helps users get their work done without losing time due to switching from one feed to another. Our simplified, intelligent news feed also makes it much less likely that things will slip through the cracks. The single feed provides an overhead view of your current workload down to the minutia. With our most recent update, we've added algorithmic capabilities to the news feed, enabling it to intelligently prioritize your updates. This ensures that the most important things are always first on the list, and therefore top of mind. Per Social Edge Consulting, only 13% of employees use an intranet daily — a statistic the algorithmic feed is directly designed to improve by surfacing content that is actually relevant to each individual user. - The intelligent news feed uses an algorithm to decipher the priority each item in the news feed should have. It takes into account feed types, whether a user has already read an item, the age of the item and more. - Users have the option to automatically mark an item as read once a user has scrolled past an item. Posts are the only exception. - Must read and announcement posts come with a visual bar and branded tag in the site's primary colors. This helps draw attention to these important items. Must read and announcement posts stay at the top of the feed until they are viewed and/or acknowledged. This makes sure important information does not get lost. - Filters are available to show only unread items, pinned items, items a user has posted, etc. For organizations managing communications across [department sites](/key-features/department-sites) or distributed [workspaces](/key-features/workspaces), the algorithmic feed consolidates updates from all of those sources into a single prioritized view. ## Getting Started: Availability, Configuration, and Rollout These three features are available now to all MangoApps customers. Here is what you need to know to activate them: **Is this available to my account right now?** Yes. All three features — the new search engine, AI image analysis, and the algorithmic news feed — are included in your existing MangoApps subscription and do not require a plan upgrade. **Do I need to enable these features, or are they on by default?** The new search engine is enabled by default. AI image analysis and PII detection for images must be activated by a network admin through the admin console under Data Loss Prevention settings. The algorithmic news feed is on by default, but individual users can adjust their feed filters from their profile settings. **How do I configure the new search hero banner on my homepage?** The hero banner is added through the webpage builder in your admin panel. Select the homepage layout, add the search widget block, and publish. The change takes effect immediately for all users. **Does this work for frontline and mobile users?** Yes. The new search and algorithmic feed are fully functional on the MangoApps mobile app and do not require a corporate email address to access, making them available to the deskless workforce without additional IT configuration. **What about multilingual teams?** The platform's 50+ language support with real-time translation applies to both the new search results and the news feed, so global teams receive updates in their preferred language without manual intervention. For a broader look at how these knowledge management tools fit into a complete intranet strategy, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent analysis of where MangoApps sits in the market. ## Frequently Asked Questions **How does the algorithmic news feed decide what to show me first?** The algorithm weighs several signals: the type of content (must-read announcements always surface first), whether you have already read or interacted with an item, how recently the item was posted, and your role and team membership. You can override the algorithm at any time using the filter options to show only unread items, pinned items, or items from specific groups. **Will the new search affect how content is organized in my existing libraries and portals?** No. The search engine update is a query-layer change — it does not reorganize or modify your existing content structure. Your [company portal](/key-features/company-portal) pages, libraries, and file hierarchies remain exactly as configured. The only visible change to end users is faster results and the expanded content types returned. **How do these updates affect intranet adoption metrics?** Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in. Faster, more relevant search and a personalized algorithmic feed directly address the two most common reasons for non-use: content is hard to find, and the feed is cluttered with irrelevant updates. Enterprise deployments using similar AI-native feed and search configurations have reported 90% frontline adoption within the first six months. For context on the business cost of low adoption, replacing a single frontline employee costs between $4,400 and $15,000 on average — making intranet engagement a measurable retention lever. Already a MangoApps customer? Check out the MangoApps Customer Portal for full configuration documentation. Not yet a customer? [Contact us to learn more about MangoApps as a knowledge management solution](/solutions/knowledge-management). --- # ROI Series, Pt. 2: Replacing Email For Internal Collaboration **Author:** Christos Schrader **Published:** 2022-06-17 **Category:** company-collaboration This is part two of our digital work hub ROI series, where we discuss replacing email In part one of this blog series, we summarized the challenges around quantifying digital work hub ROI. In this article, we’ll focus on one specific area of opportunity from our ROI Report: reducing reliance on email. Many companies are […] ### This is part two of our digital work hub ROI series, where we discuss replacing email In part one of this blog series, we summarized the challenges around quantifying digital work hub ROI. In this article, we'll focus on one specific area of opportunity from our ROI Report: reducing reliance on email. Many companies are missing out on a chance to replace email for internal communication and collaboration. Part three of the series covers search functionality, and helping people find information faster. For a broader view of where internal communications is heading, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) is a useful companion to this series. #### Your employees spend too much time on email Far too many companies rely on email for all of their internal collaboration. This usually results in a cascade of productivity issues, as it creates a firehose effect. Employees receive so many emails that it becomes very difficult to create a sense of priority. Furthermore, email clients have poor search functionality, and files and conversations can become difficult to find. The average person today is drowning in email. According to Harvard Business Review, the average full-time American worker spends 2.6 hours on email every day and receives 120 emails. On top of that, employees lose over 4 hours per week switching between disconnected systems, compounding the email overload problem beyond inbox time alone (per MangoApps product page on tool-sprawl). And per IDC, employees spend an additional 2.5 hours per day searching for information — meaning the combined drag of email overload and fragmented tools can consume the majority of a knowledge worker's day. We aren't going to try to tell you that you should get rid of email entirely. It's still one of the best ways to communicate with people outside of your organization. However, a big chunk of the emails workers receive every day are coming from their leadership and colleagues. For these use cases, there are a lot of issues that you could solve by replacing email with a tool more suited to the job. #### The problems with corporate email For one thing, most companies don't have an organized approach to deciding who should get what mass emails, and keeping the distribution lists up to date. This creates an unregulated system where irrelevant newsletters and updates fill employees' inboxes. The time spent by each employee sifting through these irrelevant emails can really add up. Beyond that, from a design perspective, email works best for short conversations about specific topics. When you try to have ongoing, non-linear conversations in this format, it becomes confusing and difficult to parse. Many teams find themselves using a single email thread for all of their ongoing collaboration, looping different people in and out and moving from topic to topic. Doing ad-hoc team collaboration via email creates frustration for everyone involved because it's hard to find files and past conversations. In our ROI Report, we examine a hypothetical company with 2,500 employees that is considering switching to MangoApps, which we've named ACME (they sell elaborate traps to help coyotes catch birds). 2,000 of their employees are in frontline roles, and the other 500 are desk workers. In the area of reducing reliance on email, they would see savings on two fronts. #### 1. Save 30 minutes per day per desk worker As stated above, the average desk worker spends 2.6 hours per day on email. There are a number of factors that contribute to this, and a few are within your company's control. First off, many companies do not give enough thought to the volume of company-wide emails they are sending. In many cases, you could deliver those messages more effectively by replacing email with another tool. With MangoApps, users have some control over the relative priority of various kinds of notifications. You can send communications through your intranet system, enabling self-service content. This removes the need for a lot of the messages that exist to make users aware of a policy change or an update to a document. Furthermore, precise AI-powered targeting lets you send things out to smaller segments, so only the people who actually need to receive a particular message will get it. This personalization mechanism — surfacing relevant content to each employee rather than broadcasting to everyone — is what makes mass email genuinely obsolete rather than just inconvenient. #### Open collaboration spaces Another key piece of MangoApps is the ability to collaborate in open, searchable group spaces instead of convoluted email threads. For companies where most collaboration and file sharing happens in lengthy email chains, this is a massive area of opportunity. In at least one documented MangoApps customer deployment, replacing siloed email threads with open group spaces helped consolidate more than 200 disparate systems into a single communication layer (per MangoApps case study — TeamHealth consolidation). By moving this collaboration into MangoApps, companies like ACME enable their employees to be nimble and inclusionary. Threads become shorter and more logical, and action items are less likely to slip through the cracks. For a real-world example of how this plays out at scale, see [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study). Between these two areas, industry research shows that adopting a tool like MangoApps reduces corporate email by about 20%, saving 30 minutes per day for each desk worker. For ACME, that's 1,250 hours per week. It's important to note that employee time is not a zero-sum game — especially for information workers. ACME won't see the equivalent of 1,250 paid person-hours in cash savings. However, by any measure, 1,250 hours per week is a lot. That's a major opportunity for their people to do something more productive than sift through their inboxes. These changes definitely save some time for frontline workers as well. However, since there isn't as much research around their email usage, we won't try to put a number on it. #### 2. Save $4/month per frontline worker Like many companies, ACME uses Microsoft for their workplace software, and they give every employee an Outlook account, which they use to reach them. For desk workers, this makes sense, but for many frontline teams, this is a bad solution. Email is not a good tool for reaching frontline employees. In most cases, corporate teams use it to push out mass email notifications, which frontline workers largely ignore. Then, when a particular worker needs a file or resource, they have to dig through their crowded inbox to find it. Furthermore, most frontline workers only send a handful of emails per month. This matters at scale: per Emergence Capital, 80% of the global workforce is deskless. Yet per Social Edge Consulting, 91% of organizations operate an intranet — and nearly a third of employees never log in to it. When the primary communication channel is email and the intranet goes unused, frontline workers are effectively cut off from the information they need. Frontline employees can access communications, shifts, and HR tools without a corporate email address or VPN — a capability gap that pure email-centric setups simply cannot close for deskless workers (per MangoApps frontline/mobile-first product positioning). In short, a tool like MangoApps, where intranet and messaging sit in an intuitive app, is a better fit for this demographic. Instead of bombarding them with impersonal emails, you create interactive pages and repositories where they can find all the resources they need. Better yet, it's cheaper than a Microsoft license. In most cases, we are able to save customers like this a minimum of $4 per user per month for anyone that no longer needs an Outlook account (and sometimes considerably more). In ACME's case, their 2,000 frontline workers no longer need email, saving $96,000 in licensing fees. The retention upside compounds this: the average cost to replace a single frontline employee runs between $4,400 and $15,000, meaning communication-driven disengagement carries a financial risk that dwarfs the licensing savings alone. #### How to Plan Your Email Replacement Knowing the ROI case is one thing; executing the migration is another. Here is a practical framework for moving internal communication off email without disrupting daily operations. **1. Audit your current email volume by category.** Before you can reduce email, you need to know what is driving it. Segment your inbound email into buckets: company-wide announcements, team collaboration threads, file sharing, and external correspondence. Most organizations find that 40–60% of internal email falls into the first two categories — exactly where a modern intranet or teamwork management platform can replace it. **2. Define your tool selection criteria.** Not every platform fits every workforce. Key criteria to evaluate include: mobile-first access for frontline workers (no VPN or corporate email required), AI-powered content targeting to replace broadcast emails, open group spaces for ongoing collaboration, and integration with existing HR and scheduling systems. MangoApps is recognized in [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) as a platform that addresses these criteria across both desk and deskless populations. **3. Run a contained pilot before full rollout.** Choose one department or location — ideally one with a mix of desk and frontline workers — and migrate their internal communication to the new platform for 30–60 days. Measure email volume before and after, track intranet login rates (per Social Edge Consulting, only 13% of employees use an intranet daily under typical conditions — a pilot lets you identify and fix adoption barriers early), and collect qualitative feedback on usability. **4. Address change management explicitly.** The biggest reason email replacement projects stall is not technology — it is habit. Designate channel champions in each team, publish clear guidelines on which tool to use for which type of communication, and make the new platform the path of least resistance by pre-loading it with the resources employees already search for in email. Organizations that launch a branded communication app have achieved 87% workforce engagement within months of go-live, illustrating how quickly adoption can accelerate when change management is deliberate. **5. Retire the old channel progressively.** Rather than a hard cutover, reduce the frequency of company-wide emails in stages — weekly to biweekly to monthly — while directing employees to the intranet for the same content. This gives laggards time to adjust while creating a measurable forcing function. For healthcare and other regulated industries where communication compliance matters, [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) offers a concrete example of this migration approach in practice. #### What Other Tools Exist for Internal Communication? MangoApps is not the only platform in this space, and a fair evaluation should acknowledge the landscape. The main categories of tools companies consider when replacing email for internal communication are: - **Team messaging apps** (e.g., Slack, Microsoft Teams): Strong for real-time desk-worker chat, but typically require a corporate login and do not serve frontline workers without additional licensing. They also tend to multiply notification volume rather than reduce it. - **Standalone intranets** (e.g., SharePoint, Confluence): Good for document management and self-service content, but per SWOOP Analytics, the average employee spends only six minutes per day using intranet tools — suggesting that a pure intranet without integrated messaging and mobile access does not fully replace email. - **Frontline communication platforms** (e.g., Beekeeper, Staffbase): Purpose-built for deskless workers, but often lack the desk-worker collaboration features needed to serve a mixed workforce from a single platform. - **Unified digital work hubs** (e.g., MangoApps): Combine intranet, messaging, teamwork management, and HR tools in one platform accessible to both desk and frontline workers without requiring a corporate email address. This is the category most relevant to the ACME scenario described above. The right choice depends on your workforce composition. If more than half your employees are frontline or deskless, a unified hub that eliminates the email dependency entirely — rather than layering another tool on top of email — will deliver the clearest ROI. The [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides third-party context on how these platforms compare. #### Next Steps The ROI case for replacing email in internal communication is clear and quantifiable. For a company like ACME, the combination of 30 minutes saved per desk worker per day and $96,000 in annual licensing savings from eliminating frontline Outlook accounts represents a concrete, defensible return — before accounting for the retention risk that communication-driven disengagement creates. But the numbers only materialize if the migration is planned deliberately: audit your email volume, select a platform that serves both desk and deskless workers, run a pilot, invest in change management, and retire the old channel in stages. Organizations that follow this sequence consistently see adoption accelerate faster than they expect. Email has changed the way we work in many ways, but that doesn't mean it's the right tool for every kind of digital communication. For internal collaboration, announcements, and frontline access to resources, purpose-built platforms deliver better outcomes at lower cost. In part three of this series, we tackle the impact of search on improving the speed with which people find information. To see how these numbers might look for your team, check out our ROI Calculator. Or, read our ROI Report to get a full breakdown of how we view ROI. You can also explore the [solutions/employee-communications](/solutions/employee-communications) page to see how MangoApps structures internal communication across desk and frontline populations. --- # Intranet Engagement Ideas To Improve Employee Reach **Author:** Mason Hager **Published:** 2022-06-07 **Category:** employee-engagement Want to improve intranet engagement? Getting your employees to consistently use your intranet can represent quite the challenge. Despite the clear value a modern intranet platform provides, employees are often hesitant to adopt it. This can lead to poor engagement levels. These intranet engagement ideas will help you fix that. A few of the factors […] Want to improve intranet engagement? Getting your employees to consistently use your intranet can represent quite the challenge. Despite the clear value a modern intranet platform provides, employees are often hesitant to adopt it. This can lead to poor engagement levels. These intranet engagement ideas will help you fix that. A few of the factors that can contribute to poor intranet engagement include: Lack of buy-in from leadership Poor intranet onboarding processes Insufficient training courses and videos explaining the intranet’s features Failure to communicate the value of the intranet platform Unclear navigation and outdated content If you are suffering from any of these challenges, don’t fret! We’ll go over how you can make sure your intranet is set up for success so employees learn to rely on it. Let’s dive into a few ideas to improve intranet engagement: #1: Build an intranet launch plan If you haven’t launched your intranet yet, you should consider building out an intranet launch plan. Think about how you can drive your employees to use the intranet on the day of the launch.  Below are a few factors to consider when launching a new intranet platform: Get buy-in from leadership Any internally facing initiative starts with strong advocacy from the top. As such, for intranet engagement ideas to succeed, they need leadership support. If the leaders of your company are not actively promoting the new intranet , you won’t see high engagement levels. Get leadership to become advocates for the new platform and have them emphasize the importance of its adoption.  Promote the launch There are several actionable steps you can take to effectively promote the launch of your new intranet. This includes sending out emails before the intranet is launched, hosting webinars detailing how to use the intranet, conducting contests, offering prizes, and more. A few examples: Host a competition to name the intranet Complete an intranet training course and you are entered into drawing to win a prize Offer incentives for employees to join virtual meetings/webinars to learn how to use the platform #2: Host important content and resources on your intranet Use the content management system (CMS) within your intranet to build a resource library for your organization. An effective CMS will allow your company to segment access to resources. This ensures that employees are only seeing important information that pertains to their job. Furthermore, if the intranet becomes the easiest way to find the content people actually want or need to see, they will naturally gravitate towards it. Sometimes the best intranet engagement idea is simply to make your employees’ lives easier by organizing content well. Also, when content and resources are properly hosted within the intranet, it removes any duplicate file versions. This can help declutter your employee experience. A quirky example to ensure employees are visiting the intranet daily is publishing your company lunch menu (if you provide lunches) daily on the platform. In doing this, you can be reasonably sure that employees will go to the platform daily.  view use case Think about what your company’s ‘lunch menu’ is. What piece of content will get employees visiting the intranet every day? Is it a daily newsletter? A weekly agenda? Once you identify what that ‘high-traffic’ item is, you’ll see a spike in recurring intranet engagement. #3: Replace existing systems A new intranet platform can replace a lot of old systems and applications that were in place. Your employees may have become accustomed to these old systems and do not want to replace them. When this problem occurs, stress the value impact of an organization-wide shift to the new intranet. A key step to driving high intranet engagement is ensuring that the majority of your employees are switching over from old systems and centralizing their work within the intranet platform. For this reason, it is crucial to work with a modern provider that has all of the essential intranet features you need to create a single source of truth for your employees. #4: Hyper-relevant, personalized content Another way to improve employee adoption of your intranet is by tailoring the content within it to your individual employees. Segment your employees into groups based on their department, office location, projects they are working on, and more. In doing this, you can provide them with highly relevant information and resources that directly pertain to their job. You can remove the clutter that can often come with seeing countless messages and information that is irrelevant. Employees are much more likely to adopt an intranet that is tailored to their specific needs. #5: Conduct an audit The last step in improving engagement is to conduct an intranet audit and make it easier to navigate. To do this, you’ll need to take a complete inventory of your intranet. Oftentimes, your intranet will have been contributing to a large amount of outdated content, unused pages, misplaced folders, and more. Conduct an audit of the content within your intranet, and use it as an opportunity to make sure you are following modern intranet best practices. Make a list of folders, paths, amount of content in each and log it. Once you have a grasp on which pieces of content are repetitive or unused, remove them. Repeat this process until your intranet is filled with only relevant and current content.  Your intranet should be a place where employees can confidently go and access a resource without worrying whether it is the correct version. Once you complete your audit, you’ll see employees naturally gravitate back to your intranet as content becomes more relevant, current, and easier to find. learn more #6: Mobile App With a mobile intranet, employees can manage tasks on the go, access content and information immediately, quickly respond to and collaborate with colleagues, and more. By offering a mobile app as a feature, your employees are much more likely to consistently engage with your intranet. In addition, a mobile intranet can empower employees to collaborate on the go. By offering a mobile app, your dispersed employees can stay engaged and access content anywhere, anytime.  This is particularly helpful in connecting your frontline employees to the remainder of the workforce.  As they previously had no means to communicate with desk workers or upper management, they are now 100% tapped into the workplace conversation. MangoApps MangoApps is a modern company intranet and employee communications platform. It provides all the tools leaders and employees need in one place so you can create a unified hub for 100% of your workforce. Unlike other solutions, MangoApps brings all the people, tools, and communications into one central hub, helping employees engage and work more efficiently than ever before. We also have a dedicated CSM team that helps our customers generate intranet engagement ideas to help make the intranet a habit for their employees. For more information, take a look at our intranet design examples, learn more about our intranet solution, or read customer stories from TeamHealth or Great Harvest Bread. --- # ROI Series, Pt. 1: How To Measure Digital Workplace ROI **Author:** Christos Schrader **Published:** 2022-06-03 **Category:** integrated-digital-workplace How do you measure the ROI of adopting a modern digital work hub?  This post is part one of our ongoing digital workplace ROI series, in which we will quantify the benefits of adopting a modern digital work hub (read part two and part three). We hope this will add some context to the research […] ## ROI Series, Pt. 1: How To Measure Digital Workplace ROI #### How do you measure the ROI of adopting a modern digital work hub? This post is part one of our ongoing digital workplace ROI series, in which we will quantify the benefits of adopting a modern digital work hub. We hope this will add some context to the research behind our ROI Report and ROI Calculator. **The short answer:** digital workplace ROI breaks into two categories — hard savings (direct cost reduction) and soft savings (time and efficiency gains). Hard savings come from auditing and consolidating your software spend. Soft savings come from benchmarking time waste against industry research and calculating what recaptured hours are worth at your average wage. The eight categories where companies consistently find the most return are: reducing email reliance, faster information retrieval, tech stack consolidation, knowledge transfer, onboarding and training, IT strain reduction, process automation, and culture-building. The sections below explain how to work through each. There is no simple way to measure the complexities of company culture and work productivity. So how do you decide whether a digital work hub platform is worth the investment? In this series, we'll take an in-depth look at the metrics we use to evaluate customer success, and help you evaluate digital workplace ROI. First, you should take a look at all the different ways information currently flows through your company. How much time and money does each of these avenues cost you every day? MangoApps solves a wide variety of problems for different kinds of customers. However, there are a few patterns that we run into with new customers, regardless of the industry or the size of the company. --- #### 1. Over-reliance on email If the bulk of your collaboration and file sharing happens over email, your desk employees are likely to be working in silos. They also waste a great deal of time searching for information and duplicating other people's work. Per IDC, employees spend an average of 2.5 hours per day searching for information — a direct drag on productivity that email-centric workflows make worse. Furthermore, over-reliance on email hurts frontline workers. If they don't have email addresses, your frontline workers are out of the loop. If they do have email addresses, you are overpaying for a tool that is ill-suited for their needs. Per Emergence Capital, 80% of the global workforce is deskless, meaning the majority of your people may never see a message that lives only in an inbox. #### 2. Using SharePoint or an outdated intranet Per Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in, and only 13% use one daily. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools. Those numbers reflect a usability problem, not a content problem. Both SharePoint and the kinds of homemade intranets that IT teams used to build for companies have problems. They are difficult to use, expensive to maintain, and often leave employees to find ad-hoc solutions for their teams. SharePoint Online licensing alone runs $5–$20 per user per month, but the first-year total cost of ownership for a 1,000-user enterprise can reach $130,000–$426,000 once implementation, customization, and governance are included (per Awesome Technologies Inc.'s 2025 cost model). Switching to a [modern intranet](/solutions/modern-intranet) winds up saving a lot of time and money in the long run. It requires far less from your IT team, stays up to date over time, and has superior navigation and search functionality. Furthermore, modern intranets are mobile-friendly. This creates a much better experience for frontline workers. It also reduces the amount of time HR and IT staff have to spend assisting them. For a broader view of how the category is evolving, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) offers independent benchmarks across leading platforms. #### 3. Lack of culture across locations This point is becoming more important as the world settles into a hybrid work model. If you have employees distributed across several locations and/or working from home, fostering company culture requires new systems and approaches. When you're not all in the same office together, it can be difficult to foster and maintain company culture. With a digital work hub, you set yourself up for success. Simple things can vastly improve company culture in the modern distributed work environment. For example, a [company portal](/key-features/company-portal) gives employees a shared digital home where they can ask questions, recognize a job well done, and stay connected to leadership — regardless of location. One documented outcome: organizations that launched a branded employee app achieved 87% workforce engagement within a few months of go-live. Disconnection also carries a hard cost. Frontline employee replacement runs $4,400–$15,000 per person, making poor communication a quantifiable retention risk, not just a culture concern. --- #### Measuring digital workplace ROI For companies struggling with these three issues, there is a massive return on the investment of a digital work hub. In our ROI Report, we estimate that an example 2,500-person company can save almost $700,000 on annual licensing fees. Furthermore, their employees can save over 13,000 hours per week. These numbers come from our experience working with hundreds of enterprise customers for over a decade, as well as industry research. There has been a lot of material written on the subject of digital workplace ROI. We think it's important to underscore that these results are highly situational. Our figures should serve as a baseline for a deeper, more specific discussion rather than be viewed as absolute. In terms of how you think about measuring ROI, we generally split it into two categories: hard and soft savings. In other words, direct monetary savings versus time savings or efficiency improvements. Hard savings are easier. You can audit your software spend to see which expensive point solutions you could replace with a digital work hub. In most cases, prospective customers are able to identify several. TeamHealth, for example, consolidated 200+ point systems into a single mobile dashboard after adopting MangoApps — a documented outcome, not a theoretical one. On the other hand, soft savings are more complex. It is not easy to measure how much time your employees will save from a modern digital work hub. Our advice is to read our ROI Report, which offers benchmarks for various sources of time waste. Once you've done that, dig around internally to see how your company matches up to them. Depending on your current tech stack and culture, you might be way above or below average. #### Areas of opportunity In our report, we reference digital workplace ROI across the following eight categories: 1. Reducing reliance on email 2. Helping people find information faster 3. Consolidating your tech stack 4. Improving knowledge transfer and reducing duplicated work 5. Reducing onboarding and training costs 6. Reducing strain on IT 7. Digitizing and automating business processes 8. Creating a culture of sharing and empowerment This blog series will feature an article about each, and we will link them here as they get published. To see how much we estimate we could be saving your company, try out our ROI Calculator. We just need a few basic pieces of information about your company. Then, we can apply all the research behind our ROI Report to give you a better estimate. For a more tailored exploration of the ROI your company could get from MangoApps, the best thing to do is reach out to our expert sales team for a discovery call. --- #### How do I actually calculate digital workplace ROI for my company? Start with three concrete steps: **Step 1 — Audit your software spend.** List every tool your employees use for communication, file sharing, project tracking, and HR self-service. Identify overlapping functionality. Most organizations find three to seven tools that a unified digital work hub can replace. Multiply the per-seat cost of each by your headcount to get an annual hard-savings baseline. **Step 2 — Benchmark your time waste.** Use the IDC figure of 2.5 hours per day lost to information search as a starting point. Survey a sample of employees to see how your company compares. Multiply recaptured hours by your average fully-loaded hourly wage to convert soft savings into a dollar figure. Even recovering 30 minutes per employee per day across a 500-person workforce produces significant annual value. **Step 3 — Model the retention impact.** If your frontline turnover rate is above industry average, apply the $4,400–$15,000 replacement cost per employee to the number of exits you could prevent by improving communication and connection. This is often the largest single line item in an ROI model for organizations with significant hourly or field workforces. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) includes additional benchmarks for this calculation. Once you have estimates for all three, add them together and divide by your projected annual platform cost. That ratio is your ROI multiple. #### What should I look for when evaluating intranet platforms? Beyond price, evaluate platforms on four dimensions: adoption rate (low daily usage, like the six-minute average per SWOOP Analytics, signals a usability problem that will undermine your ROI model), mobile accessibility for frontline workers, AI-native personalization that surfaces relevant content without manual curation, and time-to-value. Deployment speed matters because ROI accrues from day one of adoption, not day one of purchase. Features like [department sites](/key-features/department-sites) and a [webpage builder](/key-features/webpage-builder) that non-technical teams can manage without IT involvement directly reduce the hidden labor costs that inflate SharePoint's total cost of ownership. For independent analysis of how leading platforms compare, [MangoApps' inclusion in a leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides a useful third-party reference point. #### What comes next in this series? Each of the eight ROI categories listed above will get its own dedicated article. The next installment covers how to quantify time savings from faster information retrieval — including how a well-structured [employee app](/solutions/employee-app) with unified search changes the math on the 2.5-hours-per-day problem. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers related ground if you want to get ahead of that topic now. This is just part one of this blog series, so stay tuned. We will continually update the list above with links as the rest of the series goes live. --- # How To Leverage A Social Intranet **Author:** Mason Hager **Published:** 2022-05-26 **Category:** employee-experience What is a social intranet? A social intranet, also known as a modern intranet, has all the bells and whistles that come with a traditional intranet, with one caveat, it is specifically designed to promote communication and collaboration among your employees. In organizations where communication is siloed, a social intranet can facilitate work-place relationships and […] Per IDC, employees spend an average of 2.5 hours per day searching for information across fragmented tools. Per Social Edge Consulting, 91% of organizations already operate an intranet. Put those two figures together and the implication is uncomfortable: most organizations have invested in the solution and still have the problem. The adoption data makes the gap concrete. Per Social Edge Consulting, nearly a third of employees never log in to their organization's intranet, and only 13% use it on a daily basis. Per SWOOP Analytics, the average daily time spent on SharePoint-based intranet environments is six minutes. Six minutes does not describe a collaboration platform — it describes a file cabinet with a login screen. A social intranet — designed from the ground up to support communication, community, and collaboration rather than document storage alone — can close that gap. But deployment is not leverage. The organizations that translate their intranet investment into measurable outcomes have moved past feature evaluation into deliberate adoption work. This article covers what that work actually looks like. ## Build the business case before you launch A successful social intranet implementation starts with a financial argument, not just a cultural one. Without one, intranet projects get approved and then left to succeed on their own — which is precisely how organizations arrive at a platform that 13% of employees use daily. Per IDC, the 2.5 hours per day your employees spend searching for information across disconnected tools is a quantifiable productivity loss. For a 500-person organization, that figure runs to millions annually. A social intranet that consolidates your core communication, file sharing, and task coordination into a single platform eliminates the context-switching that drives that loss. For organizations running on dozens of separate enterprise tools, the consolidation also meaningfully reduces IT overhead and system maintenance costs. The frontline dimension strengthens the case further. Per Emergence Capital, 80% of the global workforce is deskless — field workers, retail associates, healthcare staff, hospitality teams who have historically been excluded from intranet deployments because traditional intranets required a corporate email address, a VPN, and a dedicated device. Replacing a frontline employee costs between $4,400 and $15,000 depending on role and industry. A social intranet that reaches your frontline workers on personal mobile devices — without a corporate email requirement — has a retention story your HR leadership can price and your budget approvers can evaluate. Make this case before you select a platform and before rollout planning begins. The organizations that do secure real change management resources. The ones that don't get a deployment that nobody uses. ## Get your employees to communicate in one place Your employees are not communicating poorly because they lack tools. They are communicating in fragmented, ephemeral ways because they have too many tools and no single canonical home for any given conversation. When a decision gets made in a group chat, it is invisible to a colleague added to the project the following week. When a policy update lands in an email thread the team archived two years ago, it is effectively lost the moment the team turns over. When a new hire onboards through their manager's ad hoc guidance, they don't know what they don't know — because the knowledge that would help them was never captured somewhere they can access. Low daily intranet usage is not a technology problem — it is a change management problem. Employees continue using familiar tools unless they experience a concrete benefit from switching. The organizations that build real adoption don't start with mandates. They start with demonstrations. They show employees how [modern intranet](/solutions/modern-intranet) search retrieves a conversation from eight months ago; they demonstrate how project workspaces keep a decision record that survives personnel changes; they let skeptics try mobile access on their own phones before the formal rollout begins. The adoption conversation that works is not "here is the new tool, please use it." It is: "here is the specific problem you have today, and here is why this solves it better than what you are currently using." ## Design for the employees who are hardest to reach The structure of most intranet failures follows a predictable pattern. Desk-based employees adopt the platform at reasonable rates because it fits the workflow they already have. Frontline employees — the ones generating the most operationally significant communication in your organization — adopt it at much lower rates, or not at all. Per Emergence Capital, 80% of the global workforce is deskless. For retail, healthcare, manufacturing, logistics, and hospitality organizations, frontline employees are not an edge case — they are the majority. An intranet that reaches only your back office has reached a fraction of the employees it was built to connect. Frontline adoption requires two things the traditional intranet was never designed to provide: mobile-first access that works on personal devices without IT setup, and login credentials that do not depend on a corporate email account. An [employee app](/solutions/employee-app) that delivers full messaging, document access, and group collaboration on a personal device removes the structural barrier that has historically kept frontline workers off the platform. This is not a trimmed-down version of the intranet — it is the intranet, designed for the employees who need it most. The impact compounds over time. Barut Hospitality Management, a Turkish resort chain that had been running entirely on mobile phones, email, and in-person relay chains, deployed a social intranet accessible on personal devices and gave department managers a shared space that no longer depended on physical presence to relay information. Per Ibrahim Yilmaz, their Group Director of Human Capital, employees could find the information they needed 24 hours a day, seven days a week — a shift from word-of-mouth relay chains to a persistent, searchable record. ## Structure collaboration around where work actually lives A social intranet generates engagement at the team level, not the company level. The closer your platform architecture mirrors the actual shape of your work — by project, by department, by cross-functional initiative — the more often employees have a genuine reason to return. [Workspaces](/key-features/workspaces) built around teams and active projects give employees a canonical home for the work they are already doing. When a workspace contains the live conversation for a project alongside its file history, task list, and decision record, it becomes the place where work happens rather than one of several places work might have happened. Employees who have a role-specific workspace with content relevant to their responsibilities return to it because returning is less costly than reconstructing context from other sources. The engagement mechanics in a social intranet — reactions, comments, acknowledgments — matter because they lower the barrier to participation without requiring a full response. A frontline worker who cannot write a considered reply during a shift can acknowledge a policy update with a single tap. Per McKinsey, 89% of frontline workers are more likely to stay with their organization when leaders actively listen to and act on their feedback. The engagement layer of a social intranet is one of the few infrastructure decisions that makes bidirectional feedback structurally possible at scale, across every employee regardless of where or when they work. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring their communication architecture to sustain this kind of ongoing engagement — not as a one-time launch event, but as an operational practice built into how work gets done. ## Address security and personalization as enterprise requirements Five distinct competitor platforms now lead with "secure intranet" as a primary positioning frame, which reflects where enterprise buyers have moved their evaluation criteria. Security is no longer a procurement checkbox — it is a filter applied before the feature comparison begins. The requirements that matter in practice: SAML 2.0 and SSO integration so your employees authenticate through existing identity providers without a separate credential; role-based permissions that restrict content and workspaces to the appropriate audiences; and HRIS synchronization that automatically updates access rights when employees change roles, transfer, or depart. Manual access management at scale is a compliance exposure. It also guarantees that your employee directory falls out of date — a directory that HR teams must update manually will never accurately reflect your current organization. One synced from your HRIS on a recurring schedule will, and a current employee directory is one of the highest-return features in a social intranet for exactly this reason: colleagues you might never otherwise locate are at your fingertips, searchable by role, skill, or location, without anyone maintaining the list by hand. Modern social intranets also address the personalization gap that has made traditional intranets feel irrelevant to most of their users. AI-driven content curation that surfaces information by role, team, location, and work context replaces the broadcast model that sends company-wide announcements to frontline workers who needed operational guidance specific to their site or shift. Personalization is not a premium feature — it is the mechanism that makes a platform feel relevant to each individual employee rather than only to the employees closest to whoever configured it. ## Measure whether you are actually getting leverage The instinct after a launch is to count registered users and declare adoption. That metric is incomplete and consistently misleading. Your social intranet is creating value when employees use it to resolve questions, make decisions, and coordinate work — not just when they log in. The metrics that indicate real leverage: daily active users rather than total registered accounts; search query volume, which tracks whether employees trust the platform to surface what they need; content engagement rates; and behavioral changes that matter operationally — how often questions get answered inside the platform rather than outside it, and how many manual status update requests disappear because project workspaces became self-serve. Organizations that set measurement baselines before launch and review them at 30, 60, and 90 days consistently move adoption faster than those that measure only when someone asks. The ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report treats measurability as a genuine differentiator in platform selection — not because analytics are optional, but because platforms that cannot show you where adoption is stalling cannot help you address it. The technology you deploy is a constant. Adoption is a variable. Every organization that has moved that variable has done it through deliberate, measurement-driven follow-through — not platform selection alone. --- # How To Improve Employee Satisfaction **Author:** Mason Hager **Published:** 2022-05-12 **Category:** employee-experience What is employee satisfaction? Employee satisfaction describes how content and happy employees are with all aspects of their job. There are several factors that can contribute to employee satisfaction within the workplace, including: employee experience, opportunity for career growth, job flexibility, relationship with colleagues, and work-life balance. Not only does employee satisfaction have a significant […] What is employee satisfaction? Employee satisfaction describes how content and happy employees are with all aspects of their job. There are several factors that can contribute to employee satisfaction within the workplace, including: employee experience, opportunity for career growth, job flexibility, relationship with colleagues, and work-life balance. Not only does employee satisfaction have a significant impact on the levels of employee engagement, but it also has a direct correlation to the overall productivity of your business. Simply put, satisfied employees generate a higher business output than unsatisfied employees.  How to monitor employee satisfaction levels Having a solid understanding of employee satisfaction levels can often be the difference between high productivity and a resignation. There are a slew of tools at your disposal that can help you track employee satisfaction levels within your organization.  One such tool is an Employee Net Promoter Score (eNPS) survey. An eNPS survey is an internal scoring system that helps business leaders assess the levels of employee loyalty and engagement. The result of the survey dictates whether an employee is placed into one of three different categories based on their feedback: promoters, passives, and detractors.  eNPS surveys allow managers to get a finger on the pulse of their teams and effectively engage employee morale. In addition, by conducting these surveys you are showing your employees that you value their input. 5 ways to improve employee satisfaction #1: Recognize the efforts of your employees Employees thrive on positive feedback. Unfortunately, it can be quite difficult for leaders to find a consistent way to highlight individual/team accomplishments without a process in place. When your employees are performing at a high-level, cast a spotlight on them and recognize their work. When leadership praises the efforts of a team or individual employee, it can go a long way in making the employees feel valued and appreciated by the company.   An effective employee recognition program can help improve your company culture, boost morale, and create a space for employees to recognize each other’s work and personal milestones. #2: Provide effective business tools Another way to improve employee satisfaction is to equip your employees with the tools and resources they need to do their job effectively. Nothing leads to dissatisfied employees like inefficient platforms and unclear processes.  It is crucial to provide your employees with the internal communication and work collaboration tools that can allow them to conveniently access what they need, when they need it. This will lead to higher productivity and remove any frustrations that can arise when dealing with slow and outdated systems.  #3: Encourage social connections Create opportunities for your employees to connect with colleagues in other office locations or departments. Not only does this naturally create ‘happier’ employees, it also can help make the company feel smaller.  One way to encourage this is by having an internal employee directory available to your workforce. With an employee directory, employees can easily search for colleagues that might have shared work responsibilities, shared interests, or skills that could provide value on a specific project. As a result, this will help build better office relationships and more efficient teams.  #4: Offer employee growth opportunities Keep employees satisfied by offering a wide slate of employee growth opportunities. Give your employees a chance to learn new skills, develop professionally, and participate in learning courses/programs. Employees that are stagnant with their responsibilities and have limited opportunity for career advancement are likely to become dissatisfied with their job. Investing in employee growth can grow the skill level of your workforce, ultimately benefitting the company’s bottom line. In addition, you will be able to fulfill more roles internally as more of your staff become qualified for certain positions. When employees feel that they have room to grow within the organization, they are much more likely to want to stay. #5: Embrace remote & hybrid work The pandemic has revealed that organizations can support remote work environments. More importantly though, it has shown employees that they can still effectively do their work while away from the office. While remote work was once thought of as a luxury, it is now considered a necessity for employees. A survey of the U.S. workforce revealed that over 68% of Americans would prefer to work remotely in some capacity. By offering flexible work environments and allowing employees to work remote, you can improve employee satisfaction levels throughout the organization. Data also suggests that offering remote work environments can improve the productivity of your workforce. Over 40% of remote employees believe that they are more productive while working at home during the pandemic, as opposed to the office. This indicates that hybrid/remote work environments don’t just improve employee satisfaction, but they also contribute to higher productivity levels and ultimately, a higher business output for the organization. How to get started Improving employee satisfaction can do wonders to employee morale as well as your company’s bottom line. So how do you get started? We recommend considering a modern intranet platform. An intranet platform (like MangoApps) offers you a place to centralize content, connect with colleagues, measure employee feedback, and much more. It truly is the holy grail of improving employee satisfaction and engagement! To help decide what platform is the best fit for you, schedule a call for your own personalized demo. For further reading, check out this blog that details 7 top intranet features your employees will love. --- # Why You Should Invest in Your Frontline Healthcare Workers **Author:** Mason Hager **Published:** 2022-04-05 **Category:** employee-experience April 5, 2022 – Nobody has been hit harder during the pandemic than the nurses and healthcare professionals working on the frontlines. Hospitals, health clinics, and everything in-between have encountered record-high numbers of sick patients. With limited resources at their disposal, employee burnout levels among healthcare professionals are seemingly at an all-time high. As a […] # Why You Should Invest in Your Frontline Healthcare Workers The business case for investing in frontline healthcare workers is not complicated, but it is frequently misunderstood. Most health system leaders frame it as a morale investment — spending money to make nurses and clinicians feel valued. The evidence points to something more concrete: turnover costs that range from $4,400 to $15,000 per frontline worker, productivity losses from information fragmentation that IDC measured at 2.5 hours per employee per day, and engagement infrastructure that currently reaches fewer than 13% of healthcare employees on a daily basis, according to Social Edge Consulting. Investing in frontline workers is a financial decision. The cost of not investing is already being paid — in replacement hiring, in hours lost to information search, in burnout-driven attrition that compounds across large clinical workforces. Health systems that have run the numbers aren't building the case for engagement tools because of culture ambitions; they're running the math and realizing the investment pays for itself. This post examines what the investment consists of, what the evidence shows when organizations make it, and how to structure the ROI conversation so the decision doesn't stall in budget review. ## The disengagement cost most health systems haven't calculated Turnover is expensive at every level of a healthcare organization, but frontline workers — nurses, clinical assistants, technicians, and support staff — are where the numbers become most significant at scale. At a conservative $10,000 average replacement cost, a 2,000-person frontline workforce with 20% annual turnover generates $4 million in annual turnover expense. A 10% improvement in retention saves $400,000 — enough to fund an engagement initiative many times over. The IDC research adds a second cost center: employees spend an average of 2.5 hours per day searching for information they need to do their jobs. For a 1,000-person clinical workforce earning $35 per hour on average, that is $31.9 million in annual productivity loss. Recovering 20% of that search time through centralized information access returns $6.4 million per year. These figures don't require a pilot program to estimate — they require only your headcount, average hourly wage, and annual turnover rate. The math almost always favors investment. ## Why the tools most health systems rely on don't reach clinical staff Healthcare organizations are not, by and large, ignoring the engagement problem. According to Social Edge Consulting, 91% of organizations operate an intranet. The problem is adoption: nearly a third of employees never log in, and only 13% use an intranet daily. SWOOP Analytics found that the average employee spends just six minutes per day in intranet tools. That adoption gap has a structural cause. According to Emergence Capital, 80% of the global workforce is deskless — and in healthcare, that figure is higher. Nurses, clinical assistants, and patient-facing technicians work in motion. They are rarely sitting at a workstation, and standard intranet tools were designed for desk workers who check a browser tab during downtime. This is not a willingness problem. Clinical staff who aren't using an intranet aren't disengaged — they're using tools in an environment those tools weren't designed for. The engagement investment only works when the infrastructure can reach employees where they actually are. ## Four investment categories with documented returns When healthcare leaders evaluate frontline engagement investments, the highest-return categories share a pattern: they address the barriers clinical staff face in their actual work environment, rather than replicating desk-worker tools at smaller scale. **Mobile-first communications infrastructure** Clinical staff who cannot receive notifications, read updates, or message peers without walking to a workstation cannot maintain team cohesion across a shift. A platform that works on personal devices — with no corporate email or VPN required, with offline document access for hospital dead zones, and with real-time translation across 50+ languages for diverse clinical workforces — removes the primary adoption barriers. The communications investment pays back through information-sharing speed and shift coordination, but the secondary payback is retention: clinical staff who feel connected and informed consistently report lower burnout scores. **Centralized knowledge management** The IDC figure — 2.5 hours per day searching for information — matters most in healthcare because the cost of finding the wrong protocol isn't just productivity loss; it's a clinical risk. A mobile-accessible repository for policies, procedures, and HR materials reduces search time while supporting regulatory compliance. Documented access to current protocols is an auditable event, and platforms that log that access give healthcare IT teams the compliance evidence they need without additional tooling. **Embedded training and compliance** Compliance training is a recurring operational cost in healthcare. The challenge is scheduling: clinical staff rarely have four-hour blocks for classroom instruction. An [employee experience platform](/solutions/employee-app) that delivers training modules in mobile micro-sessions — completable between patient interactions — changes the completion economics substantially. For context on how this differs from conventional L&D programs, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). **Real-time recognition and feedback** Recognition and feedback infrastructure matters in healthcare because the workforce conditions that drive burnout — high patient load, limited autonomy, poor communication with management — are the same conditions that turn early disengagement into full attrition. Recognition programs that operate in real time, are visible to peers, and don't require manager approval for each entry are measurably more effective than annual reviews at reducing early-tenure turnover. ## What the evidence shows in healthcare deployments The figures above give you an estimate. What tells you whether that estimate is plausible in a clinical environment is what health systems have actually achieved. OU Health achieved 87% workforce engagement within a few months of launching a branded mobile employee app for clinical staff — a figure that reflects what happens when the access barrier is removed and clinical workers can participate in the same communication environment as their desk-based colleagues. TeamHealth consolidated over 200 disconnected systems into a single mobile dashboard, directly reducing tool sprawl for frontline clinical workers across a large distributed workforce. Healthcare deployments of mobile-first engagement infrastructure consistently show adoption rates above 60% within 90 days when the platform requires no corporate device and no IT provisioning — compared to the 13% daily active rate that Social Edge Consulting measured in conventional intranet environments. For a detailed look at how one health system structured its rollout, see [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology). These examples don't establish a guarantee, but they do establish a baseline. The 90-day adoption benchmark is achievable, and it is short enough to generate measurable results within a single fiscal quarter. ## How to structure the ROI conversation with your CFO Healthcare IT and HR leaders who want to get frontline engagement investments approved need to translate operational outcomes into financial terms. Here is a practical framework for each component. **Turnover savings.** Calculate your current annual turnover rate for frontline workers. Multiply headcount by turnover rate by your average replacement cost (use $4,400 as a floor and $15,000 as a ceiling for non-physician frontline staff). Apply a conservative 10% reduction in turnover as the engagement benefit. That is your annual saving. **Productivity recovery.** Apply the IDC 2.5-hour daily search baseline to your frontline population. Use their average hourly rate. Target a 15–20% reduction in search time as the engagement outcome. That is your annual productivity return. **Training economics.** Compare the cost of scheduling classroom compliance training — facility time, overtime, staff coverage — against mobile self-paced completion. The cost differential is typically significant, and mobile completion rates tend to be higher, which also reduces compliance audit risk. **Implementation timeline.** Healthcare IT buyers are rightly cautious about deployment complexity. Platforms designed for frontline workers — with QR code enrollment, no VPN dependency, and no required integration with legacy EHR systems on day one — can reach full adoption within 90 days. That timeline supports a pilot-based approval process and generates measurable return within the same fiscal year. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) includes the metrics frameworks HR leaders at health systems are using to structure these ROI conversations, including the engagement survey infrastructure that supports ongoing measurement. ## What to measure once the investment is live The ROI conversation requires ongoing validation. These are the metrics that give you signal early enough to course-correct if adoption is lagging. **Daily active users.** Social Edge Consulting measured 13% daily usage as the baseline for conventional intranet tools. A mobile-first platform deployed to clinical staff should cross 60% within 90 days; if it doesn't, investigate whether the enrollment process is creating friction. **Time-to-information.** Measure how long it takes a nurse or clinical assistant to locate a current policy document before and after launch. The IDC 2.5-hour daily search figure is your pre-launch reference point. **Voluntary turnover rate, tracked monthly by unit.** Turnover reduction is the largest single financial return from engagement investment. Monthly tracking by unit gives you enough resolution to identify which departments are responding before the annual review cycle. **Training completion rates.** Mobile micro-session completion should outperform classroom completion within the first quarter. If it doesn't, the training content design is the likely constraint — not the platform. **Employee Net Promoter Score.** A monthly pulse survey gives you leading-indicator sentiment data before attrition numbers move. This is the fastest way to catch retention risk 60–90 days before it becomes a resignation. ## Making the investment decision Frontline healthcare workers represent a health system's highest-contact workforce and, in most organizations, its highest-turnover risk. The investment decision doesn't rest on values or culture ambitions — it rests on arithmetic. The replacement cost of a frontline clinical worker is measurable. The productivity loss from information fragmentation is measurable. The compliance cost from undertrained or unreachable staff is measurable. Health systems that have made organized investments in mobile-first communications, centralized knowledge, embedded training, and recognition infrastructure have documented the returns — in turnover reduction, in productivity recovery, in adoption rates that far exceed what conventional intranet tools achieve. The question is not whether to invest. The evidence on returns is consistent enough that the question is where to start: identify the unit with the highest turnover rate, calculate the replacement cost at $4,400–$15,000 per departure, and build the pilot case from there. That number is almost always large enough to justify the first phase on its own. --- # How To Align Remote & Distributed Teams **Author:** Mason Hager **Published:** 2022-03-31 **Category:** team-collaboration A shift in the modern workforce Over the past decade we have seen a gradual shift in the typical workplace landscape. As business leaders tested the waters and evaluated the productivity of their limited remote employees, it appeared as though remote work seemed a viable alternative for small teams of employees. The concept of an […] # How to Align Remote & Distributed Teams Aligning remote and distributed teams comes down to one practical question: do your employees have a single, reliable place to communicate, find information, and understand what is expected of them? When the answer is no, productivity erodes, engagement drops, and the cost compounds quickly. Replacing a single frontline employee runs between $4,400 and $15,000, which means poor alignment is not just a culture problem — it is a measurable financial risk. This guide covers the specific tactics and tools that close the alignment gap for both remote knowledge workers and frontline deskless employees. --- ## Why Distributed Teams Fall Out of Alignment The root cause is almost always fragmented tooling and information. Employees spend an average of 2.5 hours per day searching for information (per IDC), yet the typical corporate intranet does little to solve this. According to Social Edge Consulting, 91% of organizations operate an intranet, but nearly a third of employees never log in, and only 13% use one daily. SWOOP Analytics puts the average daily time spent in intranet tools at just six minutes. Those numbers reveal a structural problem: most intranets are built for passive storage, not active alignment. Remote and distributed employees need something that meets them where they are — on a mobile device, in the field, or across time zones — not a portal they have to remember to visit. Tool sprawl makes the problem worse. When information is scattered across email, chat, project management apps, and file-sharing platforms, employees lose over 4 hours per week switching between disconnected systems (per MangoApps product research on tool sprawl problem framing). That is half a workday every week spent on navigation rather than work. --- ## The Frontline Alignment Gap Is Different From Remote Work Most conversations about distributed teams focus on knowledge workers who have laptops, corporate email addresses, and VPN access. But 80% of the global workforce is deskless (per Emergence Capital) — frontline employees in healthcare, retail, logistics, and manufacturing who may never sit at a desk. Frontline alignment requires a different approach: - **No corporate email required.** Frontline employees need to access communications, schedules, and HR tools without a corporate email address or VPN. Requiring one creates an immediate barrier that leaves large portions of the workforce unreachable. - **Mobile-first access.** A platform that works on a personal smartphone — with offline capability — is not optional for field teams; it is the baseline. - **Multilingual support.** Real-time multilingual translation across 50+ languages is a prerequisite for truly aligning global distributed teams, not just a convenience feature. Without it, a significant share of your workforce receives communications they cannot fully understand. For [employee communications](/solutions/employee-communications) strategies that account for both deskless and remote workers, the platform architecture matters as much as the content strategy. --- ## Four Tactics to Align Remote & Distributed Teams ### 1. Create a Single Source of Truth for Company Information When there is no central place for employees to access information, the consequences are predictable: duplicate work, conflicting document versions, missed announcements, and time wasted searching. The IDC figure above — 2.5 hours per day lost to information search — is largely a symptom of this problem. A [unified employee app](/solutions/employee-app) gives every employee, regardless of location or device, access to the same verified resources. Files are versioned, searchable, and organized so that a frontline worker on a phone and a remote manager on a laptop are always working from the same information. This is the foundation of a functioning intranet for distributed teams: not a static document repository, but a living, searchable knowledge base that employees actually use. ### 2. Track Content Consumption — and Act on the Data One of the most common frustrations for leaders managing distributed teams is uncertainty: *Did my team see that policy update? Did the new safety procedure reach the warehouse floor?* Content consumption tracking answers those questions directly. A digital work hub surfaces data on who has viewed a post, completed a required read, or acknowledged a policy — giving managers the visibility they need to follow up with employees who have not engaged. This matters because unread communications are not a minor inconvenience. When alignment breaks down at scale, the downstream effects show up in engagement scores, compliance gaps, and turnover. OU Health achieved 87% workforce engagement within months of launching a branded digital work hub, demonstrating what consistent, measurable communication can produce. For a broader view of where internal communications is heading, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the metrics and benchmarks teams are using to measure reach and impact. ### 3. Reduce Tool Sprawl With a Unified Platform Tool sprawl is one of the most underestimated alignment problems. When employees have to move between separate apps for messaging, file storage, task management, HR requests, and company news, context is lost at every transition. The 4+ hours per week lost to app-switching (per MangoApps product research) translates directly into slower decisions, missed updates, and lower engagement. A digital work hub consolidates these functions so that employees have one place to start their day. This is not about eliminating every specialized tool — it is about removing the friction that comes from having no central hub that ties them together. For organizations evaluating platforms, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an independent assessment of how leading platforms compare on consolidation and usability. ### 4. Use AI-Powered Content Surfacing to Reach the Right Employees Static intranets push the same content to everyone and rely on employees to find what is relevant to them. For distributed teams — where employees span different roles, locations, languages, and schedules — this approach produces the low engagement numbers Social Edge Consulting documents: nearly a third of employees who never log in are often employees who logged in once, found nothing relevant, and never returned. AI-curated feeds and intelligent search change this dynamic. Instead of a single company feed, each employee sees content personalized to their role, location, and team. Instead of browsing folders, they type a question and get a direct answer. This is the difference between an intranet that employees are told to use and one they choose to use. Personalization also supports employee engagement more broadly — when communications feel relevant, employees are more likely to read, respond, and act on them. --- ## What About Security and Governance? Distributed communications introduce real security considerations that are easy to overlook when the focus is on adoption and engagement. When employees access company information from personal devices, home networks, and public locations, enterprise-grade access controls are not optional. A trustworthy digital work hub for distributed teams should include SAML 2.0 single sign-on, role-based permissions that limit access to information by team or location, and audit trails for sensitive communications. These controls protect the organization while still allowing the open, accessible experience that drives adoption among frontline and remote employees. For organizations in regulated industries, this is especially relevant. The [American College of Radiology case study](/resources/case-study-american-college-radiology) illustrates how a healthcare organization managed secure, organization-wide communication across a distributed workforce. --- ## Frequently Asked Questions ### What is the difference between a digital work hub and a traditional intranet? A traditional intranet is primarily a document repository with a news feed. A digital work hub integrates communication, task management, HR tools, training, and content in one place — and is designed to be used daily on any device, including mobile. The engagement gap between the two is significant: Social Edge Consulting finds only 13% of employees use a traditional intranet daily, while a well-implemented work hub is designed to be the starting point for every employee's workday. ### How do you align employees who don't have corporate email or a company device? The answer is a mobile-first platform that allows employees to authenticate with a phone number or employee ID rather than a corporate email address. This removes the most common barrier to frontline alignment. Employees can receive communications, access schedules, complete training, and submit HR requests from a personal smartphone — without VPN or IT provisioning. ### How does employee engagement training fit into a distributed team strategy? Employee engagement training and employee engagement courses are most effective when they are embedded in the daily workflow rather than delivered as separate events. A digital work hub can surface training content in the same feed where employees receive company news and team updates, making learning a continuous habit rather than a scheduled interruption. For more on this approach, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). --- ## The Bottom Line: Alignment Requires Infrastructure, Not Just Intent Remote and distributed teams do not fall out of alignment because employees are disengaged or managers are inattentive. They fall out of alignment because the infrastructure — the tools, the information architecture, the communication channels — was not designed for a workforce spread across locations, time zones, and device types. The practical steps are clear: 1. **Consolidate** communications, files, and HR tools into a single platform that works on mobile without a corporate email address. 2. **Measure** content consumption so leaders know which employees and teams are not receiving critical information. 3. **Personalize** content delivery using AI so that each employee sees what is relevant to their role and location. 4. **Secure** distributed access with role-based permissions and SSO so that openness does not come at the cost of governance. 5. **Include frontline workers** explicitly — not as an afterthought to a knowledge-worker remote work strategy. Organizations that treat alignment as an infrastructure problem — rather than a management problem — are the ones that close the engagement gap. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading organizations are building this infrastructure in practice. --- # How To Sync Information Between MangoApps & ADP Workforce Now® **Author:** Mason Hager **Published:** 2022-03-24 **Category:** news-and-updates With our connector to ADP Workforce Now®, customers will be able to automatically synchronize their ADP® worker information with MangoApps so that employee data is always current.  Are you an ADP Workforce Now user? Our MangoApps customers can now: Provide their employees with instant access to pay summary information, time-off details, and updated shift information […] ## How To Sync Information Between MangoApps & ADP Workforce Now® With our connector to ADP Workforce Now®, customers can automatically synchronize their ADP® worker information with MangoApps so that employee data is always current. The integration delivers two core capabilities: an ADP Virtual Assistant widget that surfaces pay, time-off, and shift data directly inside MangoApps, and a background sync that updates user accounts, permissions, and group memberships every 15 minutes — with zero IT intervention required. **Are you an ADP Workforce Now user? Our MangoApps customers can now:** - Provide their employees with instant access to pay summary information, time-off details, and updated shift information directly from their MangoApps dashboard. - Automatically sync employee information directly into MangoApps, allowing for immediate adjustments to permissions, departments, teams, and more. Let's dive into what this could mean for your business moving forward. ### Employees Have Instant Access to Their HR Information Joint users of MangoApps and ADP Workforce Now can access their latest pay, time-off, and shift information directly from the ADP Virtual Assistant widget on their MangoApps dashboard. This matters especially for the roughly 80% of the global workforce that is deskless (per Emergence Capital) — workers who rarely sit at a desktop and need HR self-service data available on a mobile productivity app, not buried in a separate HR portal. This widget allows employees to quickly access important information directly from their dashboard without having to leave their MangoApps environment. Per IDC, employees spend an average of 2.5 hours per day searching for information; consolidating HR data inside the same workforce management platform where employees already receive company news, updates, and resources directly reduces that overhead. Users no longer have to go through another sign-in process or switch applications to access their pay, time off, or shift information. With our connector to ADP Workforce Now, employees can receive this information in the same place as all other company news, updates, and resources — making MangoApps a genuine productivity app for the entire workforce, including frontline teams. ### Synchronized Employee Information Customers are now able to synchronize employee information from ADP Workforce Now directly into MangoApps. Our connector for ADP enables customers to import users from ADP, and automatically syncs changes to user accounts every 15 minutes to accommodate for new hires, terminations, or changes to a user's profile information. This ensures employee information always remains current and allows you to automatically enroll new users into the proper groups, teams, and departments within your MangoApps environment as soon as they're added to ADP. Administrators will no longer need to manually update employee information or permissions within the MangoApps environment. It can automatically be synced with any changes made in ADP. Employee data is automatically synced when an employee joins or leaves the team or is departing the company. Beyond convenience, automatic sync at termination keeps access permissions current in real time, reducing security and compliance exposure — a meaningful benefit for organizations in regulated industries. Acknowledgement tracking tied to HRIS sync can also confirm which employees have seen policy or procedure updates and trigger targeted follow-up notifications, supporting compliance use cases (per Staffbase case study). The employee data layer in MangoApps is designed to make these HRIS-driven events actionable without requiring custom development. HRIS integrations can automate onboarding workflows — including task assignments and routine approvals — through no-code configuration, removing IT dependency for new-hire provisioning (per Beekeeper product page). Group enrollment, permission changes, and onboarding task triggers fire automatically from ADP events, requiring zero admin intervention. For organizations tracking onboarding efficiency, pairing HRIS sync with mobile-accessible training and digitized onboarding workflows has been associated with 50% faster new-hire onboarding. **Hear From Our CEO** "We're excited to deepen our offering to our customers with this integration", says Anup Kejriwal, Founder and CEO of MangoApps. "Modern digital workspaces have become increasingly versatile, and it has never been more important to provide a unified employee experience for our customers. We know that our joint users will truly benefit from this integration." ### Learn More Easily set up your integration between MangoApps and ADP with no IT support or maintenance required. The connector is available through the ADP Marketplace. To understand how MangoApps approaches modern HCM and HRIS-connected workflows more broadly, explore our 2026 HR Trends eBook or review the IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment for independent context on integrated employee experience platforms. --- ### What Data Fields Does the ADP Workforce Now Connector Sync? The connector synchronizes core worker profile data from ADP Workforce Now into MangoApps, including employee name, department, job title, employment status, and group or team assignments. On the HR self-service side, the ADP Virtual Assistant widget surfaces pay summary information, time-off balances, and shift details. Fields that drive access control — such as employment status changes at hire or termination — are reflected within the 15-minute sync cycle, so permissions stay current without manual administrator action. For a full list of supported fields and mapping options, contact your MangoApps account team or visit the ADP Marketplace listing. ### What Are the Setup Prerequisites and Implementation Timeline? The ADP Workforce Now integration is designed for no-code configuration — no IT support or ongoing maintenance is required after initial setup. Prerequisites include an active MangoApps account and an ADP Workforce Now subscription with API access enabled through the ADP Marketplace. Most customers complete the initial configuration in a single session. Because group enrollment, department assignments, and permission rules are defined once and then triggered automatically by ADP events, there is no recurring administrative overhead. Organizations that have deployed integrated employee experience platforms report 90% frontline adoption within the first six months, which suggests that low-friction setup directly influences long-term engagement. For step-by-step guidance on connecting MangoApps with third-party cloud-based productivity applications, the MangoApps & Microsoft Integration Guide illustrates the general integration pattern, and your account team can walk through ADP-specific configuration. ### How Does HRIS Sync Support Frontline and Distributed Teams? The 80% of the global workforce that is deskless (per Emergence Capital) rarely interacts with HR systems through a desktop browser. The ADP Virtual Assistant widget inside MangoApps is accessible via the MangoApps employee app, putting pay summaries, time-off balances, and shift information on the same mobile screen where frontline employees already receive shift communications and company updates. HRIS-connected platforms can also support multilingual communication for distributed or factory-floor workforces, reducing translation overhead (per Staffbase case study) — a practical consideration for organizations with geographically dispersed teams. For organizations managing hourly or shift-based workforces, the Store Manager's Playbook for Smarter Retail Scheduling covers how integrated scheduling and HR data reduce administrative friction at the team level. --- # Writing company communications your employees will actually read **Author:** Christos Schrader **Published:** 2022-02-09 **Category:** employee-engagement At many companies, internal communicators face an uphill battle. These tips will help you win people’s trust over time by writing company communications that are engaging and relevant. Depending on your industry, a good chunk of your workforce likely takes anything from “corporate” with a grain of salt. Some ignore it entirely. This attitude is […] At many companies, internal communicators face an uphill battle. These tips will help you win people’s trust over time by writing company communications that are engaging and relevant. Depending on your industry, a good chunk of your workforce likely takes anything from “corporate” with a grain of salt. Some ignore it entirely. This attitude is especially common in industries with a lot of frontline workers, like healthcare and retail. Clinicians, retail workers, and other people out in the field have spent their entire careers being pestered with unnecessary emails, bulletins, and memos. Most of these communications were written by people who were totally out of touch with the workers’ needs. Furthermore, they provided those workers with very little of value. They were more likely to offer blockers or waste their time than to help them do their jobs. Through this lens, it is unsurprising that they don’t want to read your emails. Would you read your emails? To fix this, you have to do a better job of keeping things simple, direct, and relevant. Hopefully, you have access to a communication platform that allows you to create and distribute interactive, engaging content. If not, don’t worry—everything in this article applies to email or more traditional formats, too. 1. Keep it short and use visuals You already know this, but it bears repeating. If you write a novel, no one’s going to read it – this refers to your messages subject lines, as well. Write in chunks with titles that capture the key points, separated by images. This maps well to how the human brain digests information. Some situations, though, require writing company communications with a deeper level of detail about a topic. A good solution is to capture the main point in a short blurb, and link out to the long version. This not only keeps your message brief, but does a neat little psychology trick that many salespeople use. You get someone to say yes to a small, low-commitment question. The dopamine hit of giving another person a positive social cue primes them to say yes to more things, and they feel like they’re the one in control. Clicking a link to a longer document plays the same trick in your head. It’s more likely that you’ll actually read it, compared to a really long email. For example, you might have received an email with a synopsis of this blog post, then clicked on it. Now, here you are reading it. Would you have made it this far if the whole post had been in that email? Doubtful. 2. Provide value In any business relationship, there’s a mix of items for which each party relies on the other. Hopefully, your audience needs things from you about as often as you need things from them. If that’s the case, you can sandwich things you want them to know between things they want to know from you. If you do this well, people will read your messages without much prodding. However, there are many cases where you’re in a more difficult position. You need people to engage with your content, but they rarely or never need your help to do their jobs. In this case, providing value is tricky, and requires creativity. One approach is to find something they need that is difficult for them to get, and insert yourself into the process by delivering it to them in an easily digestible manner. Then, you can use those messages like a trojan horse. Another approach is to appeal to the employees’ interests on a human level. Find something they like, and start talking about it. Or, be funny. Make your communications so entertaining that people just plain want to read them. Humor is a slippery slope, though. Waste too many words on jokes that don’t land, and you’ve lost your audience. Tread carefully here. In any case, writing company communications that provide some kind of value is crucial. 3. Stay ahead of their questions Every internal communicator knows the pain of getting 500 replies to a mass email asking the same question. Over time, you get to know your audience and can make sure your content answers the kinds of questions they normally ask. To get to this knowledge faster, show the communications you’re going to send out to a couple people from your audience. Ask them if it makes sense and if they have any follow-up questions. With a good representative sample, this will fast-track you towards tailoring your messaging to your audience. Anything you can do to answer people’s questions before they have a chance to ask them is worth it. Even if they still ask because they didn’t read your message all the way through, you have somewhere to point them. 4. Segment and target as much as possible The key to successfully writing company communications is to make every message a person receives feel directly relevant to them. If you’re blasting company news to everyone with the same message, people will ignore you over time. See how MangoApps helps you draft and segment employee communications LEARN MORe With every single communication that you send, you need to consider your audience carefully. Answer these two questions ruthlessly: Does everyone in this group actually need to receive this message? Is there any way I can segment this group further? The more people you can eliminate from any given message, the better. The more you can break down your audience and make your message hyper-relevant, the more likely you are to build affinity and trust. Trust is the key. Make employees believe that everything you send them is important to them, and they’ll engage with your messages. It’s worth the extra effort to target and refine everything you send. 5. Choose your topics wisely, don’t over-communicate This ties into the above, but it’s worth reiterating. If you email me twice a day and my job doesn’t depend on reading your emails, you can bet that I won’t read them. Less is more, especially when there isn’t a two-way flow of requests between you and your audience. You need to be judicious with your communications. View every communication you write through the lens of a merciless editor: Do you really need to send an email about this? Do you really need to cover all these topics in this much detail? Does this really need to go to all these people? If you don’t have good answers to these questions, go back to the drawing board. Conclusion There’s a reason writing company communications is a full-time job. It’s a lot more nuanced than many people and organizations realize, and getting it right is the key to strong employee engagement and retention. Delivering the right message to the right people at the right time is everything. It’s possible to do this well with even the most outdated tools, but there’s no question that a modern communication platform makes it easier. For further reading, our customer symplr gives some great advice on getting buy-in from leadership and launching a new internal comms initiative, and our customer Benchmark shows how a simple mobile solution enables frontline teams. --- # How to declutter your content with an intranet audit **Author:** Christos Schrader **Published:** 2022-01-20 **Category:** intranet Most company intranets are the digital equivalent of a messy teenager’s bedroom, with piles of dirty clothes on every surface. An intranet content audit can help you fix this. Nested folders with no overriding logic, search that only returns exact matches in the title, inconsistent file names, partially updated versions of the same file in […] ## How to declutter your content with an intranet audit Most company intranets are the digital equivalent of a messy teenager's bedroom, with piles of dirty clothes on every surface. An intranet content audit can help you fix this. Nested folders with no overriding logic, search that only returns exact matches in the title, inconsistent file names, partially updated versions of the same file in different places—the hallmarks of a useless intranet are familiar to anyone who's worked on a team with outdated tools. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in to it—and those who do average just six minutes of daily use, per SWOOP Analytics. IDC research puts the cost of that dysfunction at 2.5 hours per day per employee spent searching for information that should be easy to find. The larger your company is, the more likely it is that you desperately need to declutter your intranet. At the same time, the larger your team, the less feasible and more challenging it is to change. **So how do you fix it?** Get a [modern intranet](/solutions/modern-intranet), obviously. But that takes time and costs money, so here are 5 things you can do right now to make the best of the current situation. Even if you only have control over part of your intranet, conducting an audit can improve your department's experience. Potentially, it can also act as a pilot program for the rest of the company. --- ### 1. Watch people use it Ask a couple colleagues to show you how they typically navigate the intranet. Put twenty minutes on their calendar, and ask them to show you how they get to the content they use most frequently. Ask them what they like and don't like about the way it's set up. Find patterns, and then find ways to remove unused items and consolidate common roundabout paths to content. Another way to get data on this is to run a survey. You'll get less detail, but it's easier to spot larger trends. Keep it short, and tie each question to something specific that it is in your power to change. A mix of surveys and 1:1 discussions will arm you with the best balance of information. Hopefully, it will also give you a to-do list you can refer to as you run your intranet audit. If your workforce includes deskless or frontline employees—who make up roughly 80% of the global workforce, per Emergence Capital—make sure your observation sessions include them, since their navigation patterns and access constraints often differ entirely from office-based colleagues. ### 2. Establish a data policy You probably have this in a document somewhere buried in your IT team's portion of the intranet. Ideally, it lists out your policies for how to name files, proper metadata, and some language around how to decide where things are put. Generally speaking, it establishes intranet best practices. Has anyone read it? No. Many companies try to address this by sending out memos or scheduling meetings to go over the policy. This is a losing battle. Instead, pick a few high traffic folders or pages, and fix the content. Remove duplicates, update or remove anything old, give everything consistent names—make it perfect. Lead by example. When someone screws it up, which you can bet will happen soon, politely ask them to fix it. If they ignore you, fix it yourself. This in combination with step one has the potential to get other people on board for the changes you're making. This is good. The more intranet audit champions you have, the better. For a structured model to guide this work, the [Intranet Governance Plan: A Practical Model for a Modern Intranet](/articles/sharepoint-server-2016-2019-replacement-intranet-governance-plan) is a useful reference. ### 3. Take an inventory Make a list of folders, paths, and amount of content in each. Put it in a spreadsheet. If possible, include volume and recency of activity. You can't fix a problem until you understand it. Once you have an inventory, start chipping away at it. Take note of bloated folders, outdated pages, and repetitive information. Then, find a way to consolidate and refresh. This can involve a lot of time-consuming manual effort. It is usually helpful to start small; pick the highest-traffic areas, and start there. Prioritize content that is important and keep it organized. Make sure it is findable without having to wade through a bunch of irrelevant, disorganized clutter. This will naturally deprioritize less important and less frequently needed items and folders, which is good. Decluttering your intranet from top to bottom is likely an impossible task for one person or team. If your organization relies on SharePoint, note that enterprise deployments can exceed $150,000 in implementation costs before ongoing governance and customization are added, making auditing a legacy platform a recurring expense rather than a one-time fix, per MangoApps' SharePoint alternatives analysis. The [SharePoint Server 2016/2019 Migration Checklist](/articles/sharepoint-server-2016-2019-migration-checklist) outlines what a structured inventory and transition plan looks like in practice. ### 4. Establish content governance If your intranet has governance features built into it, it's unlikely you've made it this far. That said, if they're there, set rules around how long a piece of content stays up before it either gets archived or flagged for a relevancy check. This ensures that old information disappears over time, which builds trust. A complete governance audit should also cover access controls: who can view, edit, and publish content in each section. Permission structures—including role-based access, SSO via SAML or LDAP, and whether frontline employees can log in without a corporate email or VPN—are as important to audit as the content itself. Frontline employees can be locked out of intranet content entirely when access requires a corporate email address or VPN; modern platforms support login without either, per MangoApps product documentation. If you don't have governance tooling, figure out a way to do it manually, at least with your high-traffic content. One way to do this is to pick the most important items, and create a spreadsheet with links to them. In this spreadsheet, list the last time each folder, wiki, or document was checked for relevancy and updated. Once a quarter or year, fire up that spreadsheet, do an intranet audit, and make sure everything is up to date and in the right place. Again, a little goes a long way. Even if you only do this with a small percentage of your content, it will have value. You just have to make sure you're applying yourself in the high traffic areas your colleagues are actually going. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) offers independent benchmarks for what mature governance looks like across platforms. ### 5. Pay attention to your own patterns Every time you struggle to find something, take note of where you looked for it first. Then, go back and put it in that place. Think about how you could organize things to match your own tendencies. This will likely serve others, too. This may be the smallest scale item on this list, but you can have high confidence in the outcome. --- ### The case for a modern intranet All of the above is time-consuming. It's a big, manual effort that is likely to be outgunned by apathetic colleagues. Without a modern intranet platform to automate this work away, you're fighting a losing battle. Furthermore, you're doing so in a way that is costing you money every day. Per Social Edge Consulting, only 13% of employees use their intranet daily—a number that reflects not just poor adoption habits but the direct consequence of ungoverned, hard-to-navigate content. Upgrading to a modern intranet offers not only a better interface and a functional search, but other key intranet features like automated content governance, freshness checks, AI-generated metadata, and the ability for departments to own their own content without IT involvement. AI-driven content surfacing and automated governance reduce the need for manual audits by flagging stale pages, suggesting metadata, and personalizing what each employee sees—so the intranet stays current without a quarterly spreadsheet review. All of these things can preclude the need for any future intranet audits. The stakes are real: replacing a single frontline employee costs between $4,400 and $15,000 on average, and a disconnected or unusable intranet is a measurable contributor to disengagement and turnover. A well-governed modern intranet, by contrast, can achieve 90% frontline adoption within the first six months, as demonstrated in large enterprise deployments. See how [Santee Cooper's 'The Coop' builds connection across every corner of its workforce](/resources/santee-cooper-case-study) as a concrete example of what that adoption looks like in practice. To learn more about how a modern intranet can affect your business, explore MangoApps' [knowledge management tools and solutions](/solutions/knowledge-management), or read about [frontline intranet requirements for replacing legacy platforms](/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements). --- ### What should an intranet audit include beyond content? Most audit guides focus on content hygiene—removing duplicates, updating stale pages, fixing folder structures. A complete audit should also cover permission structures and access controls (who can see what, and whether role-based access is enforced), mobile and frontline usability (can employees without a corporate email or VPN reach the intranet at all?), and search configuration (does search index metadata and body content, or only file titles?). Skipping these layers means the content you clean up may still be invisible or inaccessible to the people who need it most. ### How often should you run an intranet content audit? For most organizations, a full audit once per year is realistic, with lighter quarterly reviews of high-traffic sections. If your organization is migrating platforms, restructuring departments, or onboarding a large number of new employees, treat those as triggers for an unscheduled audit. The goal is not a perfect intranet at a single point in time but a governance rhythm that keeps content trustworthy on an ongoing basis. ### When does an intranet audit signal it's time to replace the platform? If your audit consistently surfaces the same problems—ungoverned content, poor search, no mobile access, IT bottlenecks for every publishing change—the issue is structural, not organizational. Traditional intranets can take months to deploy, strain IT teams, and deliver static, ungoverned content that becomes stale; modern platforms can be stood up in minutes with AI-curated content governance built in from day one, per Unily and MangoApps product documentation. At that point, the audit is no longer a fix—it's evidence that the platform itself needs to change. --- # IDC MarketScape Names MangoApps a Leader in Content Management Systems for Authenticated Digital Workspaces 2021 Vendor Assessment **Author:** Christos Schrader **Published:** 2021-11-03 **Category:** industry-insights IDC MarketScape highlights MangoApps’ customization, breadth and depth of features, security, accessibility, and the most extensive set of SAAS integrations of the providers in the report MangoApps has been named a Leader in the IDC MarketScape: Worldwide Content Management Systems for Authenticated Digital Workspaces 2021 Vendor Assessment.1  The IDC MarketScape called out the following as […] ## IDC MarketScape Names MangoApps a Leader in Content Management Systems for Authenticated Digital Workspaces 2021 Vendor Assessment #### IDC MarketScape highlights MangoApps' customization, breadth and depth of features, security, accessibility, and the most extensive set of SaaS integrations of the providers in the report MangoApps has been named a Leader in the IDC MarketScape: Worldwide Content Management Systems for Authenticated Digital Workspaces 2021 Vendor Assessment.1 For organizations evaluating intranet and knowledge management platforms, a Leader designation in the IDC MarketScape means the vendor demonstrates both strong current capabilities and a credible forward-looking strategy — placing MangoApps among a select group of providers that IDC judges capable of meeting enterprise requirements today and over the next three to five years. The IDC MarketScape called out the following as key differentiators: "MangoApps was founded in 2008 as an engineering-first company building out 80% of its capabilities organically. Resident on both the AWS and Google marketplaces, MangoApps offers platform modularity and feature breadth and depth, making it a good value for the price of the application. MangoApps also works closely with its customers to create custom integrations and modules, a majority of which wind up being incorporated into the base product." --- ### Read the report for more details DOWNLOAD REPORT --- Furthermore, MangoApps' scope of integrations has been highlighted. "MangoApps has the largest set of built-in SaaS integrations. The customers just need to enter their credentials to toggle on new modules from Google Workplace, Microsoft 365, Okta, Box, JoinMe, Slack, Zendesk GitHub, Vimeo, and so forth. Clients can create their own modules as well with webhooks." That integration breadth matters in practice. Per IDC, employees spend an average of 2.5 hours per day searching for information — a direct cost that a unified intranet with pre-built connectors to the tools employees already use can measurably reduce. Real-world deployments bear this out: TeamHealth consolidated more than 200 systems into a single mobile dashboard after deploying a unified employee app, and CVS achieved 90% frontline adoption within the first six months of launch. The report noted, "MangoApps supports user personalization of its home page by curating its content and apps from internal and external sources. Users can set up their intranet profile by connecting it to any SSO system and get shifts and schedule delivery personalized viewable on a mobile app." Personalization at this level addresses a documented gap in traditional intranet adoption. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use one daily — with average daily usage clocking just six minutes per user per SWOOP Analytics. A home page employees can actually configure around their role and schedule is one of the clearest levers for closing that gap. MangoApps' [modern intranet](/solutions/modern-intranet) approach is built around exactly this kind of role-based, personalized experience. ### Security and Governance: What the IDC Report Actually Validated The report stated, "MangoApps takes security and accessibility to a new level with support for video-closed captions (using Applied AI) and a Content Governance Engine for remote device management and data loss prevention of personally identifiable information data with administrative notifications." Unpacking what that means in practice: the Content Governance Engine gives IT administrators centralized control over content lifecycle, device-level access policies, and automated PII detection — capabilities that matter especially for regulated industries. AI-powered closed captions extend accessibility compliance without manual effort. MangoApps also supports OpenAI, Google Gemini, Anthropic, and Azure OpenAI engines, giving organizations flexibility in how AI is applied across the platform rather than locking them into a single model. For security-conscious buyers, the [company portal](/key-features/company-portal) and [workspaces](/key-features/workspaces) features layer role-based permissions on top of this governance foundation. For context on what enterprise alternatives cost: SharePoint deployments for 1,000 users can run between $130,000 and $426,000 in the first year alone, including licensing, implementation, and customization, per a 2025 cost model by Awesome Technologies Inc. MangoApps' IDC-validated "good value for the price" positioning is a direct contrast to that total cost of ownership. ### Frontline and Deskless Workforce Enablement MangoApps sees a unified work hub as being at the center of a strong employee experience, and content management is a crucial piece of their vision for the workplace of the future. They have designed their product to be user-friendly and functional for a wide range of employee types and use cases, allowing you to get all of your employees onto the same work hub without compromising on missing features. That range explicitly includes frontline and deskless workers — a segment that represents 80% of the global workforce, per Emergence Capital. MangoApps supports no-email-required mobile access and real-time translation across 50+ languages, removing two of the most common barriers to frontline adoption. OU Health achieved 87% workforce engagement within a few months of launching a branded employee app on the platform; PetSmart reached a 4x industry engagement multiple. Disconnected communication tools carry a direct retention cost: frontline employee replacement ranges from $4,400 to $15,000 per worker, per MangoApps' own product research — making platform adoption a measurable financial issue, not just an IT preference. The [employee app](/solutions/employee-app) is purpose-built for this audience. Having been in the business for over a decade, their team has worked closely with their customers to develop custom solutions to various common business problems. See how that plays out in practice in the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) and the [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms). "Our mission is to help companies create a friction-free, empowered workplace, so every employee has an opportunity to produce extraordinary results," says Anup Kejriwal, CEO of MangoApps. "For companies, efficiency creates new investment opportunities. For employees, success at work drives happiness and satisfaction. We hope to create a virtuous cycle of success that makes the world more efficient every day." --- ### What Does 'Leader' in the IDC MarketScape Actually Mean? The IDC MarketScape vendor assessment model is designed to provide an overview of the competitive fitness of ICT (information and communications technology) suppliers in a given market. The research methodology utilizes a rigorous scoring methodology based on both qualitative and quantitative criteria that results in a single graphical illustration of each vendor's position within a given market. IDC MarketScape provides a clear framework in which the product and service offerings, capabilities and strategies, and current and future market success factors of IT and telecommunications vendors can be meaningfully compared. The framework also provides technology buyers with a 360-degree assessment of the strengths and weaknesses of current and prospective vendors. A Leader designation specifically indicates that a vendor scores in the top tier on both the Capabilities axis (current product strength) and the Strategies axis (roadmap credibility and market approach). It does not mean the vendor is the only strong option — other providers also appear in the Leader segment — but it does mean IDC's analysts found MangoApps' current feature set and forward strategy credible enough to recommend it for enterprise evaluation without qualification. ### How Does MangoApps Compare to SharePoint and Other Intranet Platforms? The IDC report positions MangoApps on value, modularity, and integration breadth. For buyers comparing against SharePoint specifically: SharePoint's first-year total cost for a 1,000-user deployment can reach $426,000 (Awesome Technologies Inc. 2025 cost model), and traditional SharePoint intranets are frequently cited for slow deployment timelines and heavy IT dependency. MangoApps' organic engineering model — 80% of capabilities built in-house per the IDC report — means integrations and governance features are native rather than bolted on through third-party connectors. For a broader competitive view, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) evaluates MangoApps alongside other leading platforms across usability, governance, and employee experience criteria. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) also covers how platform selection decisions are shifting as organizations prioritize frontline access and AI-assisted content delivery. ### What Should You Do Next? If the IDC Leader designation is the starting point for your evaluation, the logical next steps are: reviewing MangoApps' specific feature set against your use cases (the [department sites](/key-features/department-sites) and [webpage builder](/key-features/webpage-builder) features are particularly relevant for content management teams), reading independent analyst coverage such as the [MangoApps Wins Gold in Reworked's 2026 IMPACT Awards for Excellence](/articles/mangoapps-gold-reworked-2026-impact-awards), and examining customer outcomes in deployments like [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study). The core takeaway: MangoApps earned the IDC Leader designation by building a platform that addresses the three failure modes most intranets share — low adoption, poor governance, and fragmented integrations. The independent research, customer adoption figures, and security architecture described above give you the evidence to evaluate that claim on its merits rather than taking the press release at face value. --- **About IDC MarketScape** The IDC MarketScape vendor assessment model is designed to provide an overview of the competitive fitness of ICT (information and communications technology) suppliers in a given market. The research methodology utilizes a rigorous scoring methodology based on both qualitative and quantitative criteria that results in a single graphical illustration of each vendor's position within a given market. IDC MarketScape provides a clear framework in which the product and service offerings, capabilities and strategies, and current and future market success factors of IT and telecommunications vendors can be meaningfully compared. The framework also provides technology buyers with a 360-degree assessment of the strengths and weaknesses of current and prospective vendors. 1 IDC MarketScape, Worldwide Content Management Systems for Authenticated Digital Workspaces 2021 Vendor Assessment, IDC #US47412921, September 2021 --- # IDC MarketScape Names MangoApps a Leader in Content Management Systems for Authenticated Digital Workspaces 2021 Vendor Assessment **Author:** MangoApps **Published:** 2021-11-03 **Category:** press-release MangoApps has been named a Leader in the IDC MarketScape: Worldwide Content Management Systems for Authenticated Digital Workspaces 2021 Vendor Assessment. IDC MarketScape highlights MangoApps’ customization, breadth and depth of features, security, accessibility, and the most extensive set of SaaS integrations of the providers in the report. # IDC MarketScape Names MangoApps a Leader in Content Management Systems for Authenticated Digital Workspaces Most intranet platforms have an engagement problem, and most buyers know it. Per SWOOP Analytics, the average employee spends six minutes per day using intranet tools. Per Social Edge Consulting, 91% of organizations operate an intranet — and nearly a third of employees never log in at all. Per IDC, the operational cost of that disengagement is 2.5 hours per employee per day spent searching for information that should be findable in one place but is not. An analyst designation in this environment is only meaningful if it addresses the actual reasons intranet investments underperform. IDC's MarketScape: Worldwide Content Management Systems for Authenticated Digital Workspaces 2021 Vendor Assessment named MangoApps a Leader on both axes the methodology uses — current product capabilities and forward strategic direction. This post explains what the assessment found, where MangoApps' positioning is specific and differentiated, and how to apply the IDC criteria to a practical vendor selection decision. ## What the IDC MarketScape methodology actually measures The IDC MarketScape does not rank platforms by market share, customer count, or revenue. It assesses two independent dimensions: capabilities (what the platform can do right now, across the evaluation criteria) and strategy (whether the vendor's direction sustains that capability as enterprise requirements evolve). A Leader designation reflects strong positioning on both — which means it survives as a reliable signal longer than a ranking that reflects last quarter's sales numbers. For technology buyers, the practical value is vendor risk reduction before due diligence begins. IDC uses data submitted by vendors alongside independent customer interviews — the results are not self-reported. That process makes a Leader designation a more reliable signal than comparison matrices produced by vendors themselves, which are designed to favor whoever produces them. The 2021 assessment focused specifically on authenticated digital workspaces, a scope that emphasizes governance, security, and integration requirements for enterprise deployments rather than general collaboration use cases. ## The two gaps any intranet designation has to clear Before applying any analyst designation to a vendor selection decision, it is worth naming the two failure modes that account for most poor intranet outcomes. The first is access model failure. Per Emergence Capital, 80% of the global workforce is not desk-based. Healthcare aides, warehouse workers, retail associates, and field technicians do not start their shifts at a browser with a company email address. A platform that does not extend to these populations — without requiring corporate email enrollment or managed-device authentication — will reproduce the 13% daily-use rate per Social Edge Consulting that is the industry baseline for platforms built around desk-worker assumptions. Evaluating a platform against IDC's criteria without testing the access model for your specific workforce composition produces a confident selection that fails at deployment. The second is governance depth. Healthcare organizations, financial services firms, and government contractors operate in environments where a platform decision is effectively a compliance decision. Data-loss prevention policy enforcement, PII detection, audit log coverage, and accessibility compliance determine whether a platform can be deployed at all — not whether it can be configured later. Platforms that treat governance as a configuration layer on top of an open-access architecture produce implementations that require exception handling at every regulatory review cycle. IDC's assessment documented that MangoApps meets the threshold on both dimensions. That is not the same as saying every organization's requirements are covered — but it eliminates the category of due diligence that most selections spend the most time on. ## What IDC specifically identified as MangoApps differentiators IDC's assessment pointed to three areas where MangoApps' positioning separates it from the rest of the evaluated field. **Organic engineering depth.** MangoApps was founded in 2008 and has built approximately 80% of its capabilities in-house rather than through acquisition. Capabilities built within a single codebase maintain a consistent security model, produce fewer integration seams between modules, and fail more predictably than platforms stitched together from acquisitions with separate authentication layers. For IT and security teams, this translates directly to administrative overhead and audit surface area over the deployment lifecycle. **The broadest built-in SaaS integration set.** IDC identified MangoApps as having the largest set of built-in SaaS integrations among all assessed providers — including Google Workspace, Microsoft 365, Okta, Box, Slack, Zendesk, GitHub, and Vimeo. These integrations activate through credential entry rather than custom development work, which eliminates the implementation overhead that typically separates a purchase decision from a productive deployment. Organizations can extend further through webhooks. **Security and governance infrastructure.** IDC's assessment noted that MangoApps "takes security and accessibility to a new level." The Content Governance Engine covers remote device management, data-loss prevention for personally identifiable information, and AI-assisted closed-caption generation for accessibility compliance. For regulated industries, this combination — enterprise-grade data governance paired with broad workforce reach — closes a gap that has historically forced organizations to maintain separate systems for different employee populations. ## Why security governance has competitive stakes in 2026 Five major intranet providers now lead their market positioning with zero-trust access controls and data-loss prevention governance as primary differentiators. MangoApps has held these capabilities for years — the IDC assessment documented them in 2021 — but the competitive stakes have shifted as enterprise buyers increasingly treat security governance as a go/no-go criterion rather than a feature comparison. The practical implication: organizations evaluating intranet platforms will encounter "secure intranet" positioning from nearly every vendor in the field. The question that separates substantive claims from marketing language is whether security governance is architectural (built into the data model and access layer from inception) or configurational (applied as a layer on top of a platform designed for open access). MangoApps' Content Governance Engine is architectural — it is not an add-on enabled after the fact, which is the more common pattern among platforms that have added governance features to meet enterprise demand over time. ## What named customer outcomes tell you that analyst designations do not OU Health achieved 87% workforce engagement within a few months of launching a branded MangoApps employee app for clinical staff. TeamHealth consolidated more than 200 disconnected systems into a single mobile dashboard through MangoApps. Both outcomes share the same structural driver: changing the access model produced the adoption change, not changing the content strategy. This distinction matters for organizations where an intranet has delivered low engagement for several years. The default diagnosis is usually content quality, distribution cadence, or editorial investment. The more common root cause — and the one that analyst assessments like IDC's help surface — is that the platform's access architecture excludes the employees whose engagement data would matter most to measure. A platform that reaches only the employees who were already going to log in produces engagement data that confirms it is working for that population and goes silent on everyone else. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), this exclusion compounds over time: the correlation between frontline disengagement and customer satisfaction outcomes is consistently underestimated when organizations rely on engagement data drawn from a desk-worker sample. ## The cost comparison most evaluations omit Per cost modeling by Awesome Technologies Inc. (2025), a 1,000-user SharePoint implementation ranges from $130,000 to $426,000 in the first year — including licensing, implementation, customization, and maintenance, but excluding the productivity cost of low adoption. Per IDC, the information search overhead alone adds 2.5 hours per employee per day to that calculation — a cost that does not appear on any licensing invoice but shows up in project timelines, decision latency, and the operational pace of teams who cannot find the information they need. Purpose-built intranet platforms that integrate with SharePoint rather than replacing it represent a materially different cost and maintenance structure. The federation approach — providing a unified search layer across SharePoint files, Teams activity, and Google Drive documents without requiring migration — addresses information fragmentation at the source rather than adding another destination employees need to check. For organizations where the per-IDC search cost is real, the integration model matters more than the licensing comparison. ## How to apply IDC's criteria to your own evaluation The IDC MarketScape provides a starting framework — translating it into a practical selection process requires specificity about your workforce composition and compliance environment. **Who actually uses the platform, and through what device?** If more than 30% of your workforce lacks a company-issued device or email address, evaluate mobile-first access specifically: no-email enrollment, offline document access, and push notification delivery to personal devices. This criterion rules out most SharePoint-based configurations before any other evaluation begins. **What does your compliance environment require at the data layer?** Healthcare, financial services, and government organizations should test data-loss prevention policy enforcement, audit log coverage, and PII detection against specific regulatory requirements — not vendor documentation alone. The enforcement architecture needs to handle your organization's edge cases. **What is already running in your technology stack?** The integration breadth IDC identified matters most for organizations with active Microsoft 365 or Google Workspace deployments. An intranet that federates these systems addresses information fragmentation where it starts; one that sits alongside them without connecting adds another destination employees must check. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) provides measurement frameworks for setting adoption benchmarks before a platform selection begins — including the employee sentiment signals that predict engagement before attrition numbers move. ## What the Leader designation establishes and what it does not The IDC MarketScape Leader designation reduces vendor risk without replacing hands-on evaluation. It documents that MangoApps met an independent analyst threshold for current capability and strategic direction across both dimensions — which removes a category of due diligence from the selection process and shifts the remaining work to testing fit against your specific workforce composition, compliance requirements, and integration environment. The capabilities that matter most in practice are the ones IDC specifically validated: organic platform depth that maintains a coherent security model, the broadest built-in SaaS integration set among all assessed providers, and governance infrastructure suited to regulated industries. These are the same factors that determine whether an intranet investment produces sustained engagement across the full workforce — or joins the majority of tools employees open for fewer than six minutes per day (per SWOOP Analytics). The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides a complementary benchmarking lens alongside the IDC assessment, comparing MangoApps against other major platforms on frontline accessibility, search quality, and administrative overhead. For organizations ready to move from evaluation to planning, the [modern intranet](/solutions/modern-intranet) solution page covers current product specifications and the access model configuration that determines frontline workforce reach from day one. --- # 5 retail staff survey questions you should be asking **Author:** Christos Schrader **Published:** 2021-10-04 **Category:** employee-engagement Get actionable results with these retail staff survey questions that quantify employee engagement. Employee surveys are one of the best ways to predict behavior and give your employees a chance to feel heard. Simple, consistent surveys are key So you’ve decided to start conducting surveys to measure sentiments and engagement among your retail associates. How […] Get actionable results with these retail staff survey questions that quantify employee engagement. Employee surveys are one of the best ways to predict behavior and give your employees a chance to feel heard. Simple, consistent surveys are key So you’ve decided to start conducting surveys to measure sentiments and engagement among your retail associates. How do you do so in a way that will actually create something tangible? One key aspect of a successful employee survey program is consistency. You should be asking the same questions annually or biannually, so you have a baseline and can see patterns and discrepancies. It’s also crucial to keep the survey simple, so people actually do it. Furthermore, ask questions that give you quantitative data, and if possible, use an employee app specifically designed for retail. Do something with the data The most important thing you can do, above all else, is make sure you actually do something with this data. Take it in, analyze it, and pick some areas where you can take action. Furthermore, ensure that your store associates see you taking that action. In the long run, this will build trust, and make people feel like they have a voice. They’re also more likely to take the survey seriously if they remember the actions you took last year. If you’re not going to do anything with the data, it’s pointless to collect it. You’re better off asking fewer questions and using the answers for something tangible. Following these guidelines is the key to mitigating the burnout issues that plague many retail organizations. With all that out of the way, here are 5 retail staff survey questions you should consider asking. All of them can be measured on a scale of 1 to 10. 1. How likely are you to recommend us as a place to work? This question can be used to create what’s known as an eNPS, or employee Net Promoter Score, which helps you put a number on employee engagement. If someone is likely to recommend you to their friends and family as a place to work, they’re happy with their job. Asking a question like this gives you a single number that tells you how happy your employees are. Compare different job functions or locations against each other. It will be apparent who needs more support and where your efforts are best focused. You can also have a follow-up question that asks why. This isn’t measurable, but if you take the time to read the responses, you’ll gain some valuable insights.  Learn more about how to use eNPS scores to measure engagement and loyalty. 2. Do you feel equipped with the tools and training you need to perform well in your role? This is a great retail staff survey question because it has a clear action item. When your employees say they feel unequipped, all you have to do is find out what tools or training they’re missing. Then, you do your best to provide what they ask for. Just asking this question can go a long way towards creating affinity with your store associates. And actually doing something about it? That’s a home run. People want to feel like their work matters, and investing in them demonstrates their value to you. Many retail communication problems can be avoided simply by asking this question. 3. How is your relationship with your supervisor? This is a tricky one, because associates are often hesitant to criticize their manager if they think there could be negative repercussions. However, if you ask it the right way, you can get important data about your employee experience. The old adage that “people quit their boss and not their job” generally holds true.  Getting data on this topic makes it easy to either remove poor managers, or find ways to help them improve. Retention among store associates is always a topic of conversation, and better management leads to better retention. MangoApps can help you create and deploy employee surveys Learn More 4. Do you feel that you have opportunities for career growth and development here? This is another telling question, because retail staff who don’t feel that there’s room for growth are unlikely to stick around. It’s likely that this question will get a comparatively lower score among certain subsets of your employee base, like students or seasonal workers. It may not be a priority, but it’s still useful to get a baseline and track it over time. The results are likely to give you some actionable insights. 5. How would you rate your working conditions? This example question is intentionally vague, but you should take the opportunity to ask about something specific.  You could measure worker perception towards compensation and benefits, or the structure of their team, or their physical location, or any number of other things. The more specific you get in the question, the more useful the answers. Your store associates are the best eyes you have for potential issues with working conditions. The best way to get that data is to simply ask. Seriously, do something with the data The best employee survey in the world is still a wasted effort if the data doesn’t get turned into action. Asking your retail staff survey questions like the above will give you insights that you can actually use. Ask the same questions regularly, establish a baseline, and take action when you spot areas for improvement. Do this right, and you can establish trust with your store associates, and improve retail employee engagement, sentiment, and retention. For more reading, take a look at our employee app for retail, or read customer stories from Superdrug and A.S. Watson. --- # Finding An Effective LMS For Manufacturing **Author:** Mason Hager **Published:** 2021-09-28 **Category:** learning-management Organizations in the manufacturing industry face a big problem. With factory machinery and processes constantly evolving, along with fluctuating safety and compliance standards, it can be impossible to keep your frontline employees prepared and educated.  Not only does this lead to an ill-equipped workforce, it also makes it extremely difficult to assess employee knowledge from […] ## Finding An Effective LMS For Manufacturing Organizations in the manufacturing industry face a persistent challenge. With factory machinery and processes constantly evolving, along with fluctuating safety and compliance standards, it can be impossible to keep your frontline employees prepared and educated. Per Emergence Capital, 80% of the global workforce is deskless — and manufacturing plants make up a significant share of that population, making a purpose-built lms learning system essential rather than optional. Not only does this lead to an ill-equipped workforce, it also makes it extremely difficult to assess employee knowledge from a management perspective. Without a clear overview of individual employee knowledge, it becomes very challenging to run an effective and efficient factory plant while maintaining organizational compliance. Fortunately, you can incorporate a modern LMS solution into your organization to help prevent this from happening. With advanced tracking and reporting capabilities paired with efficient distribution of training resources, an LMS can transform the way that your frontline workers learn and develop. In this article, we will highlight the five most important ways that an LMS solution can benefit your manufacturing organization — and then address the practical questions buyers ask next: what to look for in a vendor, what implementation looks like, and how to frame LMS adoption as a strategic learning and development investment rather than a compliance checkbox. ## 5 Benefits Of A Modern LMS In The Manufacturing Industry ### #1: Standardize Training With an LMS, you can remove the inefficient siloed learning resources that always seem to rake up a heavy expense. A modern lms learning system provides a centralized platform that ensures every employee receives a consistent level of training and certifications. In addition, there is no longer any confusion as to which workers have greater areas of expertise, and areas where there is room to grow. Standardizing training also means your standard operating procedures (SOP operations) live in one auditable place — not scattered across binders, shared drives, or individual supervisors' inboxes. This matters especially when auditors arrive or when a process changes overnight. **Side note** — Your LMS should also enable you to provide personalized training courses for each individual factory worker. With this, they can grow their skills in the areas that are relevant to them. Connecting training to a [skills management](/key-features/skills-management) framework lets managers see skill gaps at a glance and assign targeted courses before those gaps become safety incidents. ### #2: Ensure Compliance Crystal clear oversight, reports, and analytics make it easier than ever to gain insights into worker knowledge. Maintain organization-wide compliance by providing necessary training programs and courses that satisfy safety and regulatory requirements. Integrating your LMS with HRIS and payroll systems can automate user sync, digitize onboarding paperwork, and streamline compliance data collection in one workflow — eliminating manual admin steps between HR and training teams (per Beekeeper product positioning on HRIS + LMS integration). When employee roles change, training assignments update automatically, removing the compliance audit burden from managers. MangoApps' [solutions for modern HCM](/solutions/modern-hcm) are built with this kind of connected data layer in mind. Manufacturing LMS platforms that support no-code workflow automation can also handle shift-based task assignments, routine approvals, and policy acknowledgments without IT involvement (per Beekeeper product positioning on no-code workflow automation for frontline ops). ### #3: Provide 'Hands-Off' Onboarding Revamp your onboarding processes to instantly provide new hires with the information and resources needed to hit the ground running. With an LMS, they are equipped to immediately make a valuable contribution to your organization. With processes set in place, you should be able to onboard a new employee and have them instantly presented with all of the tools and resources they need to get started. Organizations that deliver onboarding via mobile-accessible LMS with digitized workflows report up to 50% faster new-hire onboarding — a meaningful gain in high-turnover manufacturing environments. For a deeper look at how learning fits into the broader employee lifecycle, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) is worth reading alongside this article. ### #4: Enable Mobile Learning Your factory workers need quick access to work instructions, new safety protocols, updated policies, and SOP operations documentation. With a modern LMS, you can quickly distribute training materials and relevant information via a user-friendly mobile app. In many cases, employees are given a training session in person or over video, and then expected to remember everything that they learned. This can be especially overwhelming for new employees who are hit with an onslaught of information and onboarding materials. One key benefit of using an LMS is that those materials are available as a reference, from mobile, whenever they need them. This ensures that they have everything they need while on the floor, reducing errors and confusion. Video-based and virtual learning formats are increasingly first-class features for frontline platforms — not add-ons. Mango Training supports video-based learning modules so workers can watch a machine operation walkthrough or a safety demonstration on their phone between shifts, rather than waiting for the next scheduled classroom session. Per IDC, employees spend an average of 2.5 hours per day searching for information; putting training content on mobile cuts that search time dramatically for floor workers who can't step away from their station. Multilingual inline translation covering 200+ languages is also increasingly table-stakes for frontline manufacturing platforms serving diverse workforces (per Beekeeper product positioning on multilingual translation). If your plant employs workers across multiple countries or language backgrounds, your LMS needs to meet them where they are. ### #5: Gain Insight Into Worker Knowledge Your LMS should provide you with both a high-level overview of employee knowledge as well as be able to zoom in on an individual employee. With a modern LMS, you can use analytics to measure the success of your training programs. Gain insights into the knowledge level of your frontline workforce. This data layer is what separates a compliance-checkbox LMS from a genuine learning and development platform. When managers can see which workers have completed recertification, which teams have skill gaps in a new piece of equipment, and which training modules have low completion rates, they can act before a safety incident or audit finding forces their hand. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading manufacturers are using workforce data to shift from reactive to proactive L&D investment. ## Mango Training — The LMS For Manufacturing Mango Training is MangoApps' cloud-based lms learning system that prioritizes employee elearning and learning & development so that you don't have to. Equip your factory workers with a learning platform that allows them to quickly adapt to new production changes, factory policies, and security requirements. With Mango Training, you can do just that. Large-scale rollouts have achieved 90% frontline adoption within the first six months — a benchmark that reflects both platform usability and the structured change management MangoApps supports. --- **Track progress** — With certificates and transcripts, we make it easy for you to see which workers are up to date on specific machine equipment training. **Personalize learning** — With workers based in different departments, factory plants, and countries, it is imperative that they are receiving training resources that are relevant to them. Mango Training's [training connect](/key-features/training-connect) feature ties learning paths to role, location, and skill gap data so assignments stay current as your workforce changes. **Auditable paths** — High-level and granular view of learning progress across your teams, ready for safety audits or regulatory reviews. **Recertification** — Assign refresher courses automatically after a certain period of time. Keep your factory workers sharp as they keep up with constantly evolving equipment and machinery. **Simple course creation** — Our course builder makes it easy for your organization to stay agile and quickly create and deploy new training courses to factory workers. **Flexible training** — Enable factory workers to study at their own pace. With our mobile app, employees have the flexibility to consume training material anytime, anywhere. This is especially important given that, per Emergence Capital, 80% of the global workforce is deskless and rarely sits at a desk to complete required learning. For organizations evaluating how Mango Training fits into a broader employee experience platform strategy, the [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study) case study shows how a distributed workforce used MangoApps to close communication and learning gaps at scale. ## How To Choose An LMS For Manufacturing: Key Criteria Buyers researching an LMS for manufacturing typically need answers to three practical questions before they can move forward. Here is a direct answer to each. **What should you look for in a manufacturing LMS vendor?** Prioritize these criteria when evaluating options: - **HRIS integration** — Does the platform sync employee roles, departments, and compliance records automatically, or does your HR team manage that manually? - **Mobile-first design** — Is the mobile experience built for workers without a desk, or is it a desktop interface squeezed onto a phone screen? - **Compliance and audit trails** — Can you produce a complete training history for any employee on demand, including recertification dates and acknowledgment records? - **No-code course creation** — Can a training coordinator build and deploy a new course without IT involvement? - **Multilingual support** — Does the platform support inline translation for diverse workforces, ideally covering 200+ languages? - **Video and virtual learning** — Are video modules and virtual instructor-led sessions supported natively, not just as file attachments? - **Scalability** — Can the platform handle shift-based assignments, multiple plant locations, and role-based learning paths without custom development? MangoApps' [learning management solution](/solutions/learning-management) is designed to meet all of these criteria for manufacturing environments specifically. **How long does LMS implementation take in manufacturing?** Implementation timelines vary by organization size and integration complexity, but a practical benchmark for a mid-size manufacturing company (500–2,000 employees) is 6–12 weeks from contract to go-live for a cloud-based LMS with standard HRIS integration. Factors that extend timelines include custom content migration, complex shift-based permission structures, and multi-site rollouts requiring localized content. Organizations that use no-code workflow automation and pre-built HRIS connectors consistently land at the shorter end of that range. Targeting 90% frontline adoption within the first six months is a realistic goal when the platform is mobile-first and onboarding is structured. **How does an LMS support learning and development beyond compliance?** Compliance training is the floor, not the ceiling. A manufacturing LMS that also supports continuous learning for development — skill-building, cross-training, leadership pipelines — delivers measurably more value than one that only tracks required certifications. Per the [Break The Annual Review Cycle](/resources/break-the-annual-review-cycle) executive guide, organizations that embed learning into daily work rather than treating it as a periodic event see stronger retention and faster skill development. Framing your LMS investment as an employee experience platform capability — not just a compliance tool — also makes the business case easier to defend to finance and operations leadership. ## Learn More With a modular approach and affordable pricing, Mango Training gives you a direct way to educate and engage factory workers. If you are evaluating LMS options for your manufacturing organization, the criteria above give you a vendor-neutral framework to compare platforms — and Mango Training is built to meet every item on that list. Interested in seeing it in action? Schedule a personalized demo or set up your own free trial today. --- # KCoe Isom explains why they chose MangoApps and how they use it **Author:** Christos Schrader **Published:** 2021-09-22 **Category:** intranet Debra Helwig, Senior Internal Communications Manager at KCoe Isom, spoke at Engage’s Internal Communications Conference this past week. The two-day virtual event featured round tables, interactive sessions, and speaking slots from a wide variety of internal communications experts. The speakers gave us all some great insights to take home and build upon. About three-quarters of […] # Why KCoe Isom Chose MangoApps — and How They Use It Every Day KCoe Isom, a national accounting and consulting firm, needed an intranet that employees would actually use. After evaluating their options, they selected MangoApps — and within months, roughly three-quarters of their firm was logging in daily. This post summarizes their selection criteria, implementation approach, and the specific use cases that drove adoption, based on a presentation by Debra Helwig, Senior Internal Communications Manager at KCoe Isom, at Engage's Internal Communications Conference. ## The Problem: Low Intranet Adoption Is the Industry Norm KCoe Isom's challenge is common. According to Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use one daily (per Social Edge Consulting). Meanwhile, IDC research finds that employees spend an average of 2.5 hours per day searching for information — time that a well-organized intranet is designed to recover. For a professional services firm where knowledge workers bill by the hour, that search overhead has a direct cost. Replacing a single knowledge worker costs between $4,400 and $15,000 on average, which means high turnover driven by frustration with fragmented tools compounds the problem quickly. KCoe Isom wanted to break that pattern. Their goal was an intranet that employees would open by habit, not obligation. ## Why KCoe Isom Selected MangoApps Debra Helwig outlined three criteria that drove the selection decision. **1. Consolidation of tools and content in one place** KCoe Isom's employees were navigating multiple systems to find documents, directories, and internal links. Intranet platforms that consolidate quicklinks, directories, and content in one place measurably reduce tool-switching friction for distributed teams. MangoApps' [company portal](/key-features/company-portal) gave the team a single destination where staff could check announcements, access HR resources, and reach the tools they use most — without opening a second browser tab. **2. Security and governance fit for a compliance-sensitive firm** Accounting firms handle sensitive client data and operate under strict compliance requirements. KCoe Isom needed an intranet with enterprise-grade access controls. MangoApps supports SAML 2.0 single sign-on, role-based permissions, and department-level visibility controls — features that let administrators grant the right access to the right people without IT-heavy customization for every change. **3. Implementation speed** One of the most common objections to intranet projects is the timeline: months of IT customization before anyone sees value. KCoe Isom's rollout did not follow that pattern. The team was able to stand up organized pages and a working directory quickly, using MangoApps' [webpage builder](/key-features/webpage-builder) to structure content without developer involvement. Professional services firms using a unified intranet report faster onboarding and reduced reliance on email for internal communications, and KCoe Isom's experience aligned with that pattern. ## How KCoe Isom Uses MangoApps Day-to-Day Once live, the platform became a daily habit rather than an occasional reference tool. Helwig reported that about 75% of the firm visits MangoApps every day — a figure that stands in sharp contrast to the industry average of 13% daily usage (per Social Edge Consulting) and the SWOOP Analytics benchmark of just six minutes per day spent in intranet tools. The primary use cases break down into three areas: - **Quicklinks and tool access.** Employees use the intranet as a launchpad to reach the external systems they need — payroll, project management, client portals — without hunting through bookmarks or asking colleagues for URLs. - **Content and announcements.** Internal communications are published centrally, so staff across offices and remote locations see the same information at the same time. This reduced the volume of firm-wide emails that previously carried routine updates. - **Organized pages and directories.** The team built structured [department sites](/key-features/department-sites) for practice groups and administrative functions. New hires can orient themselves by browsing the directory rather than relying on a colleague to walk them through where everything lives. This structure also supports employee engagement training and onboarding: new staff encounter a consistent, navigable environment from day one, which shortens the time before they can work independently. ## What Made Adoption Stick High launch-day traffic is easy to generate with a firm-wide announcement. Sustained daily usage — 75% of a professional services firm, consistently — requires the platform to deliver genuine utility. For KCoe Isom, three factors sustained engagement: 1. **The content was organized, not just published.** Pages were built with the employee's workflow in mind, not the communications team's org chart. Staff could find what they needed in two clicks. 2. **The quicklinks replaced a real pain point.** Before MangoApps, employees maintained their own browser bookmarks for internal tools. Centralizing those links removed a friction point that had previously sent people to email or Slack to ask for URLs. 3. **Leadership visibility.** Firm leadership used the platform to share updates, which signaled that the intranet was the authoritative source of internal information — not a secondary channel. For context on how intranet adoption patterns compare across industries, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides a detailed benchmark across platform types and deployment sizes. ## The ROI Case: Translating Usage into Time Saved IDC's finding that employees spend 2.5 hours per day searching for information provides a useful frame for estimating the value of KCoe Isom's adoption rate. If a firm of, say, 500 employees recovers even 30 minutes per person per day through better information access, that is 250 hours of productive time returned daily across the organization — time that, for billable professionals, has a direct revenue equivalent. The employee engagement software category often struggles to quantify its value in concrete terms. KCoe Isom's 75% daily usage rate is itself a meaningful metric: it means the intranet is functioning as infrastructure, not a project. ## What to Consider If You're Evaluating an Intranet KCoe Isom's experience points to a few questions worth asking during any intranet evaluation: - **Will employees use it without being told to?** The 13% daily usage average (per Social Edge Consulting) suggests most intranets fail this test. Ask vendors for verified adoption data from comparable organizations. - **Can non-technical staff maintain it?** If keeping content current requires IT tickets, content will go stale and usage will drop. KCoe Isom's team managed their own pages using MangoApps' built-in tools. - **Does it work for distributed and mobile users?** Per Emergence Capital, 80% of the global workforce is deskless. An intranet that only works well on a desktop browser will exclude a large share of any workforce that includes field, frontline, or remote staff. MangoApps' [employee app](/solutions/employee-app) addresses this for organizations with mixed workforces. - **What are the security and access controls?** For compliance-sensitive industries — accounting, healthcare, legal — role-based permissions and SSO support are not optional features. For a broader view of where internal communications is heading, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the patterns shaping intranet strategy this year. ## The Bottom Line KCoe Isom's intranet story is not primarily about the platform — it is about what happens when an intranet is built around how employees actually work. Their 75% daily usage rate is the result of deliberate decisions: consolidating tools, organizing content by workflow, and giving leadership a visible presence on the platform. For professional services firms evaluating a [modern intranet](/solutions/modern-intranet), the KCoe Isom case illustrates that adoption is not a launch-day event. It is the outcome of choosing a platform employees find genuinely useful, and then maintaining that utility over time. If your organization is working through a similar evaluation, reviewing how comparable firms structured their rollout — including selection criteria, governance decisions, and content architecture — is a practical starting point before committing to a platform. --- # Why Your Factory Workers Feel Disengaged **Author:** Andrew Wong **Published:** 2021-09-20 **Category:** company-culture Factory floor engagement represents a problem that many manufacturing organizations face. A study found that only 25% of factory employees are engaged, and that there is the same number of actively disengaged factory workers as engaged workers. This alarming battle doesn’t stem from a single source, but rather a few common culprits that are touched […] # Why Your Factory Workers Feel Disengaged Miguel runs the same line every Tuesday from 6 a.m. to 2 p.m. at an automotive parts facility in the Midwest. Last month, a new lockout/tagout procedure was released. He found out three days late — a coworker passed him a printed copy in the break room. The week before, he needed a material safety data sheet and spent 40 minutes digging through a shared drive that hadn't been organized since 2019. His onboarding supervisor retired two years ago and was never replaced. Miguel is not disengaged by nature. He has become disengaged by infrastructure. Per IDC, employees spend an average of 2.5 hours per day searching for information across disconnected systems. On a factory floor, that search time isn't overhead — it's accumulated friction that, compounded daily, quietly destroys whatever connection a worker has to their organization. The data on manufacturing engagement is stark. Only 25% of factory employees are engaged, and the share of actively disengaged workers is nearly equal to the share who are genuinely committed. This is not a hiring problem. It is not a compensation problem. It is a design problem: the tools most manufacturers use to communicate, train, and recognize their workforce were built for desk workers — not for the 80% of the global workforce that is deskless, per Emergence Capital. Fixing it starts with naming exactly what breaks down, and why legacy infrastructure makes it worse. ## Communication tools built for email users don't reach the floor Email is the default internal communication channel in most manufacturing organizations. For office employees with a dedicated inbox and a laptop, it works reasonably well. For floor workers without a corporate workstation, company email, or a quiet hour to sit and read, it doesn't reach them at all. Paper-based communication fares no better. Printed newsletters and policy updates arrive in batches, get misplaced, and leave managers no way to confirm whether a critical update — a safety procedure change, a regulatory notice, an emergency protocol — was actually read by the people it was meant to reach. The result is a structural information gap that widens with every policy cycle. Workers disengage not because they are indifferent, but because the communication channels assume an employee profile that doesn't match their daily reality. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools. That figure is not a sign of disinterest. It reflects friction. When information requires a VPN, a specific device, or a corporate login that floor workers don't have, the tools reach only the office-based fraction of the workforce — and the floor goes uninformed. ## Language barriers that safety procedures cannot afford to ignore Manufacturing workforces are often multilingual. Workers from dozens of language backgrounds operate the same equipment under the same safety requirements, yet most internal communication is delivered exclusively in the dominant language of the office. The gap is operational, not philosophical. Safety protocols that are partially understood create real exposure. A worker who can follow a visual cue but cannot read the written procedure is more likely to improvise under pressure. Compliance documentation that requires an informal translator introduces delay at exactly the moments when speed matters most. Real-time multilingual translation embedded in the communication layer — not a separate tool, not a workaround — is the difference between a safety system that reaches every worker and one that reaches the portion of the workforce comfortable with a single language. Most manufacturing organizations still handle multilingual communication with printed bilingual posters, leaving a significant gap that directly affects both safety outcomes and inclusion. ## Invisibility at scale is its own disengagement driver A facility running 300 workers across three shifts doesn't have a feedback problem — it has a visibility problem. Only 20% of factory workers report that someone at work encourages their development, recognizes good work, or discusses their progress with them. That number tracks. A floor supervisor managing 40 workers per shift has roughly 12 minutes per worker per week for anything other than production status. Recognition doesn't happen because the infrastructure doesn't enable it — not because supervisors don't care. When workers receive no signal that their contribution is noticed, they calibrate accordingly. Engagement is a response to environment, and invisibility is an environment. [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) documents this dynamic across industries: the single strongest predictor of engagement isn't compensation or job fit — it's whether an employee received recognition in the past seven days. Manufacturing organizations cannot fulfill that requirement through a supervisor's individual memory. They need infrastructure that makes recognition possible at the scale the floor actually operates. ## No centralized LMS is a disengagement problem wearing a compliance mask Inconsistent safety training is typically framed as a compliance risk. It is — but the engagement impact is equally significant and less discussed. Workers who can't track their own certifications, don't know when renewals are due, or have to chase down a safety manager to confirm their status feel administratively stranded. The absence of a centralized learning management system doesn't just create regulatory exposure; it signals to workers that career development isn't something the organization actively manages on their behalf. Per Social Edge Consulting, 91% of organizations operate an intranet, but only 13% of employees use it daily — and nearly a third never log in at all. A standalone LMS with a separate login and desktop-only access follows the same adoption curve. Workers who don't use the system don't complete optional training. Certifications lapse. Safety refreshers happen once and are forgotten. The fix is not a better standalone LMS. It is learning embedded in the same environment where workers already receive communications and find resources. When a factory worker can complete a required safety certification from the same mobile app they use to check shift updates, completion rates rise because the friction cost of doing it approaches zero. [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) examines the design choices that distinguish learning embedded in daily work from learning that lives in a separate system — the distinction is exactly the gap between a compliant workforce and an engaged one. ## Files and resources nobody can find stop being resources Per IDC, 2.5 hours per day disappear to information search across disconnected systems. On a factory floor, that manifests as workers hunting through old shared drives, asking supervisors for documents that should be self-serve, or operating from a procedures handout that may or may not reflect the current version. This is both a productivity loss and an engagement signal. Workers who cannot find what they need without escalating to a manager learn, over time, that self-sufficiency is not available to them. They stop trying. The organizational result is a workforce that is more dependent on supervisors for routine information retrieval than necessary — which increases supervisor load, slows resolution, and frustrates workers who wanted to solve problems independently. A consolidated, searchable resource environment available on a mobile device — without requiring a corporate email address or VPN — eliminates this category of friction. Per Social Edge Consulting, most organizations already have an intranet investment. The problem is not whether the investment exists; it is whether the platform was designed for the access patterns of a floor worker rather than a desk employee. ## What closing the gap costs and what it saves Disengaged factory workers don't simply underperform. They leave. Replacing a single frontline manufacturing employee costs between $4,400 and $15,000 when accounting for recruiting, onboarding, training time, and productivity lag during ramp. Multiply that by annual turnover rates in high-disengagement facilities — which can reach 30–40% — and the financial case for infrastructure investment becomes a straightforward calculation. The organizations that have closed this gap share a common pattern: mobile-first access that doesn't require corporate credentials, multilingual communication that reaches every worker regardless of device or language, recognition infrastructure that doesn't depend on a supervisor's individual bandwidth, and a learning system that lives inside the same daily workflow rather than in a separate application that workers visit once a quarter. The [Santee Cooper case study](/resources/santee-cooper-case-study) documents what happens when a large distributed workforce gets a communication platform built for how their employees actually work: workforce connection metrics shift within months of deployment, not years. For organizations evaluating what to look for when selecting a platform, the [Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026](/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) lays out the criteria that distinguish platforms built for the factory floor from platforms built for the office with a mobile app added later. ## The infrastructure argument Miguel's situation is not unusual. It is the norm in manufacturing organizations that have layered communication and training tools on top of a workforce that was never the primary design target. The tools work for employees who fit the assumptions built into them. They miss everyone else. Factory worker disengagement is a predictable output of systems that impose desk-worker workflows on people who will never sit at a desk. The fix is not engagement programs, culture initiatives, or incentive structures layered on top of broken infrastructure. It is infrastructure that actually reaches floor workers — mobile by default, multilingual by design, with learning and recognition built into the daily flow rather than siloed in separate systems they were never going to visit. The gap between having tools and having tools that work for the floor is measurable. So is the cost of leaving it open. --- # Top Tactics To Reduce The Turnover Rate In Hospitality **Author:** Alec Morrison **Published:** 2021-09-20 **Category:** industry-use-cases Employee turnover has been a continuous problem for businesses in the hospitality industry. Lack of recognition coupled with a high stress work environment are two of the primary contributor to a high turnover rate. An easy way to engage employees is to have an employee-driven mindset that uplifts the staff environment. Read ahead to find the […] # Top Tactics To Reduce The Turnover Rate In Hospitality Employee turnover has been a continuous problem for businesses in the hospitality industry. Replacing a single frontline hospitality employee costs between $4,400 and $15,000 per departure, making retention a direct P&L issue—not just an HR concern. Lack of recognition coupled with a high-stress work environment are two of the primary contributors to a high turnover rate. An easy way to improve employee engagement is to adopt an employee-driven mindset that uplifts the staff environment. Read ahead for the top tactics to accomplish this. **Top 5 Ways To Reduce Employee Turnover Rate In Hospitality:** ## 1. Employee Recognition With strenuous hours on the floor and little acknowledgement by customers, hospitality workers inevitably suffer from job fatigue. This feeling of unappreciation can often lead to a loss of productivity for not only the worker, but also for the rest of the floor team. Caring for your employees is crucial for maintaining a positive work environment. Housekeepers, front desk workers, and other frontline workers often feel forgotten due to the minimal amount of acknowledgement they receive in their jobs. Without the proper appreciation, a spiraling effect of unhappy employees is created that is detrimental to your entire company. The solution is finding a consistent, tangible way to recognize employees for their impactful work contributions. Taking the time to reward your staff and acknowledge their successes can go a long way toward employee longevity. Employee engagement software that automates peer-to-peer recognition, milestone badges, and manager shout-outs removes the friction that causes recognition programs to stall. To see how a structured program works in practice, review [From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program). ## 2. Greetings In the grand scheme of things, work takes up the majority of many people's lives. Despite this, it is important to remember and enjoy the personal milestones and celebrations of your employees. Implementing a method to recognize the little things, like a staff member's birthday or a workplace anniversary, can help make employees feel included and valued. Make your business setting embracive of all employees to demonstrate your company's value for their personal lives as well. ## 3. Onboarding & LMS Having a good onboarding program can make or break an employee's experience. Providing a personalized onboarding and learning process makes new hires feel more equipped during their new career beginnings. Instead of being thrown out on the floor, they are informed with the proper knowledge of how to do their jobs effectively. But effective employee engagement training doesn't stop at onboarding. Hospitality roles benefit from continuous learning paths—video-based microlearning for service standards, role-specific compliance modules, and career development tracks that show employees a future within the organization. When workers see a clear path forward, they are far less likely to leave. An [lms learning system](/solutions/employee-engagement) embedded in the same app employees already use for scheduling and communication removes the barrier of logging into a separate tool. Equipping employees with the tools to get started on day one and continue to build their knowledge is a win for everyone involved. For a deeper look at how to make learning stick, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ## 4. Real-Time Communication When there are countless customers with high demands, the systematic operations within a hospitality company can become increasingly hectic. These companies should acquire a centralized platform to communicate with targeted workers in real-time and simplify the operational process. Providing an easy way for individuals to engage in two-way conversations promotes efficient communication and keeps your company running smoothly. Communicating this way helps solve customer needs quickly without the mess of using several communication methods. Critically, per Emergence Capital, 80% of the global workforce is deskless—meaning most hospitality employees never sit at a computer. Your communications platform must be mobile-accessible on personal iOS and Android devices, with no corporate email or VPN required, to allow all employees to connect on-the-go. Frontline employees who lack access to a mobile-first communication tool are systematically excluded from company culture and recognition programs. Employees also lose over 4 hours per week switching between disconnected systems—a direct drag on hospitality floor productivity. ## 5. File and Policy Organization Keeping organized is a crucial part of maintaining growth and efficiency within a hospitality company. To ensure frontline workers are up to date with company policies, your business must have a centralized location for all internal information. This helps eliminate confusion and gets everyone on the same page. Policy organization gives employees a place to find answers to customer questions, such as hotel policy information or emergency procedures. Additionally, it helps your staff personally understand the blueprints and makeups of your organization. Per IDC, employees spend an average of 2.5 hours per day searching for information—time that a well-organized knowledge base directly recovers. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading hospitality and service organizations are structuring their internal knowledge hubs to cut that search time significantly. ## Measuring Success: Metrics That Show Whether Turnover Is Actually Improving Tactics only matter if you can measure their impact. The following metrics give hospitality HR and operations leaders a clear picture of progress: - **90-day and 1-year retention rates** — Track the share of new hires who remain after 90 days and after 12 months. These are the two windows where hospitality attrition is highest. Improvement here is the clearest signal that onboarding and early recognition programs are working. - **Employee engagement survey scores** — Run a short employee engagement questionnaire at 30, 60, and 90 days post-hire, then quarterly. Look for movement in questions about recognition, communication clarity, and access to training. A 5-point improvement in engagement scores typically precedes measurable retention gains by one to two quarters. - **Time-to-productivity for new hires** — If your LMS and onboarding program are working, new hires should reach full productivity faster. Track the number of days from start date to first solo shift or first unassisted customer interaction. - **Platform adoption rate** — Organizations that deploy a branded employee app with role- and location-targeted news feeds achieve 87–90% workforce engagement within the first few months of launch, per MangoApps case studies including OU Health and the Kansas City Chiefs. If adoption lags, recognition and communication programs cannot reach the employees who need them most. - **Cost-per-departure trend** — Because replacing a frontline hospitality employee costs between $4,400 and $15,000, even a 10% reduction in annual departures produces a measurable return. Track total annual separation costs quarterly and tie them to the engagement initiatives you've launched. As a general benchmark, organizations that address recognition, communication, and structured learning simultaneously typically see measurable retention improvement within two to three quarters. Quick wins—like birthday greetings and peer recognition—can lift engagement survey scores within the first 30 days. Structural improvements—like a functioning LMS and mobile-first communication—take one to two quarters to show up in retention data. For broader context on what HR leaders are prioritizing this year, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) provides benchmarks across industries including hospitality. ## What Does Turnover Actually Cost My Property or Brand? The $4,400–$15,000 per-departure figure is an average. Actual costs depend on role complexity, local labor market conditions, and how long a position stays open. A front desk manager vacancy in a high-demand market costs more than a seasonal housekeeping role—but both carry hard costs: recruiting fees, overtime for remaining staff, training hours, and the productivity gap while the new hire ramps up. The most useful exercise is to multiply your average annual separations by a conservative mid-range replacement cost (roughly $7,000–$8,000 for most frontline hospitality roles) and compare that figure to the annual cost of an employee engagement platform. For most mid-size hospitality operations, the math favors investment in retention tools by a wide margin. The [Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026 and beyond](/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) includes a cost-comparison framework that HR and operations leaders can use to build an internal business case. ## MangoApps for Hospitality Streamline your employee workflow using a centralized, all-in-one internal communications platform. With MangoApps, your [hospitality](/industries/hospitality) organization can transform the way employees work—connecting recognition, employee engagement training, mobile-first communication, and policy management in a single app that works on any personal device without corporate email or VPN. If you would like to learn more about how MangoApps can assist your organization, schedule a personalized demo with us today. --- # Why Banks Need Modern Internal Communication **Author:** Amaya Kejriwal **Published:** 2021-09-15 **Category:** company-collaboration An old internal communication system not only stalls productivity and output, but also affects your workplace culture and customer service. As found in this study, modern internal communications platforms can enable your bank to unlock seamless collaboration and communication. In this article we discuss a few of the ways that a modern internal communication system […] # Why Banks Need Modern Internal Communication Per IDC, employees spend 2.5 hours per day searching for information. For a bank branch with 30 staff members, that translates to 75 hours of productive capacity consumed by information retrieval before a single customer interaction happens. The overhead doesn't distribute evenly — it concentrates in the employees who most need to be present for customers: tellers looking up current fee schedules, branch managers tracking down the latest policy update, and compliance teams chasing the version of a document that supersedes the one in their inbox from six months ago. Legacy email systems created this overhead and cannot solve it. The email inbox was designed for messages between individuals, not for the structured information governance a regulated financial institution requires. Banks that recognize this gap but treat modernization as an IT refresh are underestimating what the decision actually changes. ## The 2.5-hour search tax — and what reduces it in modern deployments Per Social Edge Consulting research, 91% of organizations operate an intranet. Per the same source, only 13% of employees use it daily, and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends six minutes per day using intranet tools. The pattern holds across industries: the platform exists, employees default to email and workarounds, and the information search overhead persists. In banking, this inefficiency is operationally significant. A teller who needs the current overdraft policy during a customer conversation cannot wait for a supervisor to forward an email. A branch manager coordinating shift coverage during a staff shortage cannot afford a 20-minute search for a contact directory. The cost registers in response time, service quality, and the operational friction that accumulates into employee frustration and eventual disengagement. Modern communication platforms address this through AI-driven search and personalized information surfacing — not just better keyword search, but content prioritization that routes the right documents, announcements, and updates to the right employee before they even need to search. The distinction matters for banks: a better inbox reduces search time at the margins; an intelligence layer eliminates it as a daily drain. For a view of how high-performing organizations are closing this gap, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers current adoption patterns and the structural changes driving them. ## Why email's security posture disqualifies it in regulated banking Email was built for general-purpose correspondence, not for institutions handling sensitive financial data, audit-sensitive communications, and regulatory updates that require chain-of-custody tracking. Five competitors in the enterprise communication space now explicitly lead with "secure intranet" positioning in financial-services content — a market signal that banking buyers have identified this as a real concern and vendors are responding. The security baseline for internal communication in banking is specific. SAML 2.0 single sign-on eliminates credential sprawl and ensures access is governed by the bank's identity management system. Role-based permissions scope communication access by department and function — compliance updates reach compliance staff, sensitive HR communications stay within appropriate channels, and no employee has visibility into information outside their function. Enterprise-grade encryption at rest and in transit means sensitive institutional data doesn't represent open exposure. Audit trails document who received what, when, and whether they acknowledged it — a capability required for regulatory examination readiness. Email provides none of this natively. Banks operating on email-based internal communication are managing sensitive institutional information through a system designed for open correspondence. A [financial services communication platform](/industries/financial) built for regulated industries treats these capabilities as baseline requirements, not premium configuration options. The time-sensitivity gap compounds the security problem. All messages in an email inbox receive identical urgency — a promotional update and a critical fraud alert sit in the same queue. A modern platform supports push notifications, SMS alerts, and in-app urgency signals for time-sensitive communications, ensuring that employees receive and acknowledge critical updates immediately rather than encountering them hours later during an inbox scan. ## The 80% of your workforce that legacy systems can't reach Per Emergence Capital research, 80% of the global workforce is deskless. In banking, that category encompasses tellers, branch representatives, loan officers working primarily on the floor, and field service staff. This workforce tier interacts with more customers per day than any other employee segment — and they are consistently the last to receive updated information under legacy communication models. Legacy email systems require a corporate email address and, for external access, frequently a VPN. A branch employee without a company-issued device — common in banks with high frontline turnover — has no reliable access to internal communications outside of a configured terminal during business hours. Policy updates, compliance notifications, benefits changes, and schedule modifications go unseen until the employee happens to be at a desk, if they arrive at all. A modern [employee communications](/solutions/employee-communications) platform removes the access barrier by enabling mobile access through personal devices, with no corporate email address or VPN required. Frontline employees receive the same structured communications, acknowledgment requests, and HR notifications as office staff — through an app interface they can use on their own phone between customer interactions. The retention stakes are measurable. Replacing a single frontline bank employee costs between $4,400 and $15,000 in recruitment, onboarding, and lost productivity. Per [Gallup's 2026 State of the Global Workplace research](/articles/gallup-2026-state-of-the-global-workplace), information disconnection is among the primary drivers of employee disengagement — and disengaged employees exit. A communication system that structurally excludes frontline staff is not an equity concern in the abstract; it is a quantifiable retention and cost risk that shows up in annualized turnover figures. ## What a modern bank communication platform does operationally The operational shifts a modern platform produces are specific, not theoretical. **Centralized, version-controlled knowledge.** Policy documents, compliance updates, procedural guides, and internal handbooks live in a single searchable repository. When a regulatory change requires an immediate update to branch-level procedures, the new version replaces the old one in the same location employees have always accessed it — no email chains, no version conflicts, no teller working from an outdated procedure because they missed the mass email from three months ago. **Structured acknowledgment for compliance communications.** Compliance updates and policy changes require that employees receive and confirm receipt — not that an email was sent to a distribution list. Modern platforms support read-acknowledgment workflows that track confirmation by employee, flag non-responders for follow-up, and generate auditable records for regulatory review. "We sent an email" is not a defensible compliance posture in an examination. **Two-way communication that sustains engagement.** Broadcasting information at employees without a feedback mechanism builds disengagement over time. A platform that supports employee surveys, feedback submission, and direct response to announcements creates the conditions for sustained engagement. The structural test is whether employees can submit input and observe it influencing decisions within the same platform. Without that loop, even a well-configured communication system drifts back toward passive repository behavior. **Role-scoped access governed by function.** Sensitive communications reach only employees with the appropriate access level. Compliance staff receive regulatory updates; branch managers receive operational procedural changes; all employees receive general announcements. Permissions are managed through role definitions tied to the bank's HR data, not through manual distribution list maintenance that creates gaps every time someone changes departments. ## How to evaluate internal communication platforms for banking environments Platform features among mature vendors have largely converged. Most support announcements, document storage, search, mobile access, and basic survey capability. The differentiation for a banking environment lies in how platforms handle compliance, security, and deskless-worker requirements that generic enterprise tools treat as configuration afterthoughts. **Security certifications and compliance specifics.** Request documentation of SAML 2.0 SSO support, SOC 2 Type II certification, communication archiving compatibility with your relevant regulatory body, and data residency options. A vendor that responds with general "enterprise security" language without specifics is not positioned for regulated financial services — ask for the compliance documentation directly. **Deskless-worker access in practice, not in principle.** Ask vendors for documented examples of frontline adoption in comparable financial services environments: not aggregate platform statistics, but specific deployments where branch staff — not only corporate employees — reached meaningful daily engagement. Ask explicitly what happens when a frontline employee doesn't have a corporate email address. **Migration timeline and change management support.** Most mid-size banks complete phased migrations in 60 to 90 days. The variables are content volume, integration complexity, and employee group size. A vendor whose change management plan ends at administrator training is not accounting for the adoption drop-off that occurs at the branch level without role-specific onboarding and internal champions. **HR system integration depth.** The platform should connect to your HRIS for user provisioning, so that onboarding and offboarding automatically govern platform access. Single sign-on is the baseline; bidirectional data sync with your HRIS is the target. Platforms that require manual synchronization with HR data introduce access control gaps every time your HR team gets behind on updates. ## What adoption data says about closing the 13% gap Per Social Edge Consulting, only 13% of employees use an intranet daily despite 91% of organizations operating one. The gap is not primarily a feature problem — the banks sitting at six-minute-per-day average engagement are not there because the platform lacks functionality. They are there because the platform was deployed without the change management rigor that frontline-heavy workforces require. Organizations that reach 85–90% workforce engagement within six months of a platform launch consistently follow a pattern: role-specific training during the first 30 days, branch-level internal champions who model platform behavior, and communications about the rollout delivered through the platform itself. The last point is practically important — if the rollout is communicated through the old email system, employees have no immediate evidence that the new platform is the primary channel. The bank that addresses security, frontline access, and information search simultaneously — through a platform built for regulated industries rather than generic enterprise users — converts a communication upgrade into an operational and retention advantage. The alternative is continuing to measure communication success by email volume: a metric that reliably records activity without measuring whether anyone received, understood, or acted on what was sent. --- # Improve Your Nonprofit With Enhanced Tracking **Author:** Ella Foley **Published:** 2021-09-10 **Category:** industry-use-cases Lack of funding coupled with a high turnover rate can make operating extremely difficult without developing a proper nonprofit tracking system. Take the time to implement organizational tracking to improve your nonprofit in the long run. In this article we discuss how you can reduce employee turnover, improve decision-making, and promote collaboration by tracking effectively. […] # Improve Your Nonprofit With Enhanced Tracking Nonprofits operate at a structural disadvantage that for-profit organizations rarely face simultaneously: tight margins, high turnover, and a workforce that often includes dozens of volunteers who have never attended a training session. The conventional advice — track your KPIs, maintain your donor records, document your processes — is correct. But it stops short of the harder question: whether the information you've already captured is findable when someone needs it. Per McKinsey, employees spend an average of 2.5 hours daily searching for information that should be accessible but isn't. For a nonprofit running on a $2 million annual budget with a development director, two program coordinators, and a rotating volunteer roster, those hours are not a productivity loss. They're a mission loss. Time consumed hunting for last quarter's donor list, reconstructing a campaign report, or re-explaining an onboarding procedure to the third new volunteer this month is time not spent on the work the organization exists to do. The nonprofits that solve this problem aren't the ones with better spreadsheets. They're the ones that stopped treating tracking as a documentation exercise and started treating it as a knowledge infrastructure problem. ## Why spreadsheets stop working as your organization grows The case for spreadsheets is real: they're free, flexible, and everyone already knows how to use them. For organizations in their first two or three years, they're adequate. The structural failure arrives later — when the organization grows past five staff members, starts managing a volunteer roster of fifty, or runs multiple fundraising campaigns in parallel. The problem isn't that spreadsheets store data incorrectly. It's that they don't make data findable. When a donor record lives in a file called "donor-master-updated-FINAL-v3.xlsx" in a shared drive folder organized by someone who left in 2022, the data exists but the institutional knowledge is gone. Per APQC, Fortune 500 companies lose $31.5 billion annually to knowledge loss. For a nonprofit operating on thin margins, even a fraction of that friction can derail a campaign or cost a major gift. The upgrade path most nonprofits eventually discover runs from personal spreadsheets to shared, version-controlled documents to a knowledge management system with structured search and role-based permissions. The first transition is the most important one: moving from data that lives in someone's drive to knowledge that lives in a searchable system that survives turnover. ## What nonprofit tracking actually needs to capture Most tracking frameworks focus on outputs: KPI numbers, fundraising results, donation totals, budget actuals. These matter. But outputs are only useful if the team can act on them — and the team can only act on them if the data is structured, current, and accessible to the right people at the right time. **KPIs and organizational performance.** Per a Banner Health employee poll, 63% of employees say their intranet's content is not current and relevant. That figure hits KPI dashboards hardest: stale metrics don't inform decisions — they undermine them. KPIs tracked in a centralized, searchable knowledge management system remain visible and current across departments. Tracked in a personal spreadsheet, they become inaccessible the moment the person who built them leaves. For a practical framework on connecting performance data to organizational decisions, [Closing the Information Gap in Performance Reviews](/articles/closing-the-information-gap-in-performance-reviews) offers directly applicable guidance. **Donor records and relationship context.** Donation amounts and gift dates are easy to capture. The harder data is the relationship context: when a donor prefers to be contacted, which programs resonate with them, what the last conversation covered. This context tends to live in email threads and the personal notes of whichever development staff member manages the relationship. When that person leaves — and turnover in the sector is well above the private-sector average — the context leaves with them. A structured donor record in a shared knowledge base, with role-based permissions that update automatically when staff change positions or leave, is what prevents this cycle from repeating indefinitely. **Fundraising campaign performance.** Every campaign generates data that could sharpen the next one: cost per dollar raised, channel conversion rates, volunteer engagement, optimal timing. Gathered in a shared, searchable knowledge base, this data compounds over time — each new campaign benefits from the institutional memory of every prior one. Gathered in a post-campaign email thread that nobody can retrieve two years later, it effectively doesn't exist. **Budget transparency.** Budget documents that live in one person's folder and are emailed to stakeholders on request are not transparent — they're centralized and fragile. The same Banner Health poll found that 59% of employees report difficulty finding information they need. For budget data that changes frequently, the answer is a shared document in a governed system with automated notifications to relevant stakeholders, not a periodic email that some people miss and others don't read. ## The mobile access gap most nonprofits don't address Per the Banner Health employee poll, 61% of employees want access to organizational information outside the work VPN, and 55% want access from a mobile device. For a for-profit company with a desk-based workforce, that's a convenience issue. For a nonprofit that depends on volunteers who are never on a VPN, never on a company-issued device, and may only engage with the organization during specific event windows, it's a structural access failure. If volunteer coordinators can only view donor intake procedures by logging into a VPN or sitting at an office workstation, the information may as well not exist for anyone in the field. Modern knowledge platforms deliver wikis, onboarding materials, policy documents, and forms to personal mobile devices without requiring VPN access or corporate account enrollment. For organizations with distributed volunteer rosters — seasonal program staff, event-based contributors, part-time coordinators across multiple sites — mobile-accessible tracking is not a premium feature. It's a baseline requirement for the information to actually reach the people who need it when they need it. ## Onboarding and workflow: where tracking pays back fastest The highest hidden cost in most nonprofits isn't recruiting. It's the invisible expense of re-teaching institutional knowledge every time someone new joins. When the procedure for handling a major gift lives in the executive director's memory, or the volunteer onboarding sequence is a PDF from three years ago attached to an email nobody can find, every new staff member starts from scratch. The cycle repeats. No-code workflow automation addresses this directly. Routine approvals, volunteer onboarding sequences, donation acknowledgment tasks, and budget notifications can be formalized as automated processes that run consistently regardless of who is on duty and regardless of how recently they joined. Organizations that digitize their onboarding and operational workflows report significantly faster ramp time for new staff and volunteers — not because the people are more capable, but because the knowledge arrives in a structured, accessible sequence rather than through an improvised conversation with whoever happened to be available. For organizations managing shift-based volunteer programs or multi-site operations, pairing a knowledge base with a [workforce management solution](/solutions/workforce-management) keeps scheduling, shift assignments, and operational documentation in the same accessible system — rather than distributed across three spreadsheets, a group chat, and someone's personal calendar. ## Evaluating knowledge management tools for nonprofits The evaluation criteria for nonprofits differ from for-profit organizations in three specific ways. **Mobile access without corporate credentials.** If the platform requires a company-issued device or VPN enrollment, it excludes volunteers. Look specifically for browser-based or app-based access that works on personal devices without IT provisioning. **Role-based permissions that update automatically.** Staff and volunteer rosters in nonprofits change frequently. Permissions that require manual IT updates will be stale within weeks of any staff transition. HRIS-synced or role-based access that revokes and updates automatically when positions change is the operational requirement — not a security nicety. **No-code administration.** Nonprofits rarely have dedicated IT staff. A platform that requires developer configuration for every new workflow, form, or document structure won't be maintained after the initial setup. No-code automation and straightforward administrative interfaces are necessities, not premium features. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an independent benchmark of major platforms against frontline accessibility, search quality, and administrative overhead — a practical starting point for separating marketing claims from actual functionality. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines how organizations of all sizes are replacing fragmented spreadsheet systems with integrated platforms to reduce operational drag, with case studies applicable to lean nonprofit environments. ## What the right tracking system actually changes The goal of a nonprofit tracking system is not better spreadsheets. It's faster access to the institutional knowledge the organization has already generated. When donor records are findable in under two minutes, development staff spend their time building relationships rather than reconstructing histories. When campaign performance data is accessible to the coordinator running the next similar program, each effort benefits from the last rather than starting over. When onboarding procedures exist in a mobile-accessible, searchable format that doesn't depend on any single person's memory, volunteer turnover stops destroying institutional knowledge every six months. The nonprofits that achieve operational stability on thin margins aren't doing it with more sophisticated data strategies. They're doing it with knowledge infrastructure that makes what the organization already knows available to the people who need it — at the moment they need it. That's the operational shift that a well-implemented knowledge management system produces. For organizations where every staff hour is accountable to a mission, it's often the difference between a program that scales and one that stalls every time someone new walks through the door. --- # How To Reduce Burnout Among Healthcare Employees **Author:** Alec Morrison **Published:** 2021-09-09 **Category:** healthcare September 9, 2021 – Employee satisfaction/happiness has represented a massive issue among healthcare organizations in recent history. With 70% of nurses reporting that they feel burned out, it has never been more critical than ever to keep your healthcare professionals engaged. It is difficult for your healthcare workers to adequately care for patients when they […] ## How To Reduce Burnout Among Healthcare Employees Employee satisfaction has represented a critical issue among healthcare organizations for years. With 70% of nurses reporting that they feel burned out, it has never been more important to keep your healthcare professionals engaged. The five strategies below — connection spaces, structured recognition, positive news sharing, routine wellness checks, and active listening — give healthcare leaders a concrete starting point, along with guidance on how to measure progress and know when each approach is working. It is difficult for your healthcare workers to adequately care for patients when they are not in the right headspace. When unmotivated, they are less attentive, less engaged, and unhappy with their work environment. This type of thinking often results in high replacement costs and a negative work culture. Thankfully there are many proactive steps your healthcare organization can take to begin preventing burnout among your healthcare professionals. In this article, we go over a few of these steps, and reveal the path forward for your healthcare organization. ## #1 Provide spaces for connection In such an emotionally demanding industry, it's essential to give hardworking employees a break. When people are constantly on their feet and busy caring for others, it's difficult to take a few minutes and catch your breath. With long hours and stressful shifts, workers typically gravitate towards a feeling of self-isolation and become distanced from their work environment. This feeling of isolation can be prevented by encouraging staff to share their thoughts and advice with each other. Virtual support groups for different departments and locations work great for this, especially for medical centers where there is very little downtime to decompress after dealing with difficult situations. One often-overlooked barrier: per Emergence Capital, 80% of the global workforce is deskless, and many frontline healthcare workers — nurses, technicians, aides — lack a company email address or regular access to a desktop. Connection tools that require VPN access or a corporate login will simply go unused. Mobile-first platforms that work on personal devices remove this barrier entirely, making it realistic for a floor nurse to join a virtual support group between shifts. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) explores how healthcare and other frontline industries are solving this access gap in practice. ## #2 Show appreciation It's easy to get burned out when you feel that the work you do doesn't matter. Show your healthcare professionals that what they're doing is important and appreciated by implementing a recognition initiative. Rather than treating recognition as a single gesture, the most effective organizations build it as a structured, measurable employee engagement program — one where peer-to-peer awards, manager shout-outs, and milestone celebrations are tracked and reported over time. This can be as simple as giving workers the ability to send each other virtual awards. But the data suggests going further: peer recognition and employee engagement tools deployed as a branded mobile app can deliver 4x the engagement of industry-standard approaches, per a MangoApps case study. This will ensure that your employees don't feel as if their hard work helping patients is going unnoticed. For a detailed look at how one healthcare-adjacent organization built this kind of program from scratch, see [From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program). **Measuring progress:** Track recognition frequency (awards sent per employee per month), participation rate (share of staff who have sent or received at least one award), and correlate quarterly against your employee engagement survey scores. A 30-point engagement score increase is achievable at large employers after deploying a unified employee experience platform — but only if recognition activity is monitored and acted on. ## #3 Celebrate the good news Another great way of eliminating healthcare burnout is by reminding your workers of the good events that happen. Only hearing about negativity creates an uninviting culture and atmosphere. Prevent this by making space for positive news, such as in a section of your company newsletter. This can be work-related. For example, did somebody save a patient's life or did your staff come together to help someone out? It can even be for celebrations outside of work, such as of an employee completing a marathon or getting married. ## #4 Send routine wellness checks A monthly check-in shows employees that their thoughts and feelings matter. This is essential in making them feel welcomed in the place they work at. For clinics that are especially stressful, sending an employee engagement survey every week to hear feedback can be the difference between workers feeling isolated versus feeling valued. Keep employee engagement questionnaires short — five questions or fewer — so completion rates stay high even on busy units. Per Social Edge Consulting, only 13% of employees use an intranet daily, and nearly a third never log in at all; if your wellness check lives only on a desktop intranet, most frontline staff will never see it. Delivering surveys via a mobile app on personal devices closes that gap immediately. ## #5 Listen to your employees Once you know how your employees are doing, you can decide the best way to help them. Use the feedback gathered from your wellness check-ups to take action to prevent healthcare burnout in your clinic. For instance, after hearing that your employee is extremely tired after their 60-hour work week, you could give them the option to reduce their hours for the upcoming week. Alternatively, you could choose to assign them to less stressful tasks to build up their resilience again. Listening to your employees by taking turns this way makes them feel listened to and cared for. Combine your scheduling and feedback software together on one platform to make this simple to implement. Fragmentation is a real cost: per IDC, employees spend an average of 2.5 hours per day searching for information across disconnected tools — time that could be redirected to patient care. Consolidating scheduling, wellness surveys, recognition, and communication into a single employee experience platform eliminates that friction for both managers and frontline staff. The [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study shows how a healthcare organization put this consolidation into practice. For broader context on how employee engagement training and development practices are evolving across industries, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) is a useful companion read. ## MangoApps MangoApps is an all-in-one hub that makes it easy to implement all of these burnout-reducing strategies, plus much more. With a modular approach and affordable pricing, MangoApps gives you an easy way to meet your healthcare professionals where they are, with a unified employee experience. Healthcare-specific frontline deployments have achieved 87%+ workforce engagement within months of launch — without requiring company email or VPN access, per a MangoApps case study. We designed our infrastructure using public cloud partners including Amazon Web Services (AWS), incorporating principles of operational excellence, security, reliability, performance efficiency, and cost optimization. Interested in learning more about how MangoApps can help your healthcare organization? Schedule a personalized demo, or try a free trial today. You can also explore our [solutions/employee-engagement](/solutions/employee-engagement) page to see how the platform supports recognition, surveys, and communication in a single place. ## How do we measure whether burnout reduction is working? Measuring progress matters as much as the strategies themselves. Three metrics give healthcare leaders a clear signal: - **Employee engagement survey scores:** Run a baseline employee engagement questionnaire before launching any initiative, then re-survey at 60 and 90 days. Look for movement in questions about feeling valued, feeling heard, and intent to stay. - **Recognition participation rate:** Track the percentage of staff who have sent or received a peer award each month. Low participation signals that the program needs promotion or that access barriers (no mobile app, no personal-device login) are blocking adoption. - **Voluntary turnover rate by unit:** Burnout is a leading driver of turnover. If engagement scores improve but turnover doesn't move within two quarters, investigate whether workload or scheduling — not culture — is the primary driver. For a broader view of how HR teams are approaching these metrics heading into the next planning cycle, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers engagement measurement frameworks in detail. ## What if we can't afford dedicated employee engagement software? Not every healthcare organization can immediately invest in a full employee experience platform. In that case, prioritize the strategies with the lowest implementation cost and the fastest measurable return: 1. **Peer recognition first.** A structured shout-out channel in any existing messaging tool costs nothing to launch and can move engagement scores within weeks. The key is making it visible to the whole team, not just a manager. 2. **Short pulse surveys over long annual surveys.** A five-question mobile-friendly form sent monthly generates more actionable data than a 50-question annual survey that most staff skip. 3. **Dedicated connection time on the schedule.** Even a 10-minute post-shift debrief built into the schedule — no software required — reduces the isolation that drives burnout. When the organization is ready to consolidate tools, the [The Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026 and beyond](/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) provides a vendor-neutral framework for evaluating employee engagement software options against frontline-specific requirements. ## Which burnout-reduction strategy works fastest? Based on available evidence, structured recognition programs show the fastest measurable impact — typically within 30 to 60 days — because they are visible, social, and require no behavior change from employees beyond acknowledging a colleague. Wellness surveys and listening programs take longer (60–90 days) because they require a feedback-to-action cycle to build trust. Connection spaces and positive news channels tend to show gradual, compounding effects over three to six months as culture shifts. If speed is the priority, launch peer recognition first, layer in a short employee engagement survey at week four to establish a baseline, and use the survey data to sequence the remaining strategies by the issues your specific workforce surfaces. --- # Mango Training: An LMS For Healthcare **Author:** Mason Hager **Published:** 2021-08-31 **Category:** learning-management Between tending to multiple patients, recording detailed reports, checking medical equipment and more, healthcare professionals have a jam-packed schedule. With seemingly no extra time to spare, it can be difficult for them to freshen up on their skills or finally go through those recertification courses they’ve been meaning to take.   At MangoApps, we recognize that […] ## Mango Training: An LMS For Healthcare Between tending to multiple patients, recording detailed reports, checking medical equipment and more, healthcare professionals have a jam-packed schedule. With seemingly no extra time to spare, it can be difficult for them to freshen up on their skills or finally go through those recertification courses they've been meaning to take. At MangoApps, we recognize that your workers are never done with training. As new hospital procedures, regulations, and equipment are introduced, continuous learning and development remains a requirement. Mango Training is MangoApps' cloud-based LMS learning system for healthcare — a module inside the broader [MangoApps employee experience platform](/solutions/employee-app) — that centralizes course creation, compliance tracking, personalized learning paths, and HRIS integration in one place. Below, we walk through exactly how healthcare organizations use it and what to expect. ## Mango Training Mango Training is MangoApps' cloud-based LMS learning system for healthcare that prioritizes employee learning so that you don't have to. In this article, we dive into a few ways how our healthcare customers use MangoApps. ### 'Hands off' onboarding The healthcare industry as a whole experiences around a 30% yearly turnover. High churn carries a compounding cost: every departing employee triggers recruiting, credentialing, and retraining expenses that strain already-tight operating budgets. As employees depart your organization, new ones are brought in — and per Emergence Capital, 80% of the global workforce is deskless, meaning most healthcare new hires will never sit at a desktop to complete onboarding modules. We make it easier than ever to onboard new hires by creating a 'hands off' onboarding process. With Mango Training, your healthcare workers are instantly provided access to the information and training resources they need to hit the ground running. Mobile-accessible LMS training can accelerate new-hire onboarding by up to 50% for frontline healthcare workers who lack desk access. One large healthcare and pharmacy deployment reached 90% frontline adoption within the first six months of going live. For a deeper look at how learning and development strategy can be embedded into daily workflows rather than treated as a one-time event, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ### Quick and easy course creation Easily create and deploy training courses to your entire workforce, or specific departments and teams, in minutes. Courses can be flagged as mandatory and alerts can be set to remind employees to complete them. Mango Training supports video-based and virtual instructor-led delivery formats — critical for shift workers who cannot attend live sessions and need async video as a practical alternative. Persona-based content targeting by role, department, or care unit ensures nurses, technicians, and administrators each receive only the training relevant to their scope, reducing noise and improving completion rates. ### Satisfy compliance requirements With Mango Training, you can maintain organization-wide compliance by satisfying HIPAA and other regulatory requirements. In addition, our [LMS learning system](/solutions/learning-management) can be configured to reassign courses automatically after a certain period of time. This ensures that your workers remain up-to-date on required certifications and training. Compliance tracking is also where SOP operations management intersects with learning: when standard operating procedures change, updated courses can be pushed automatically to the affected roles, closing the gap between policy change and verified staff acknowledgment. ### Personalized learning paths Mango Training makes it easy for your employees to fill their CE credit requirements by enabling them to select courses they are interested in learning. Each individual's learning path can be tracked through [skills management](/key-features/skills-management) to give management greater insight into the growth of its employees. In addition to a high-level view of learning progress across your teams, transcripts can be exported for licensing boards when necessary. Reframing learning and development as a strategic capability — not just a compliance checkbox — is what separates organizations that retain clinical talent from those that cycle through it. For a broader view of how workforce learning trends are shifting in 2026, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the key signals HR leaders are acting on. ### Remove siloed learning resources Remove expensive siloed learning resources and ensure that all healthcare professionals receive the same level of training and certifications. With a centralized platform, tracking employee learning progress has never been easier. Nurses and healthcare workers are now equipped with the training courses and skill-refreshers they need to provide the best patient care possible. HCM integration is a key part of eliminating silos: healthcare LMS platforms that connect with HRIS automatically sync employee roles, permissions, and certifications, eliminating manual roster management. MangoApps supports this through its [modern HCM](/solutions/modern-hcm) layer, which keeps training records aligned with HR data without requiring manual exports or reconciliation. ## What Does Setup Actually Look Like? Setup time and integration depth are the two questions healthcare IT teams ask most often before committing to a new LMS learning system. Mango Training is cloud-based, which means there is no on-premise infrastructure to provision. Most organizations are creating and deploying their first courses within days of provisioning, not months. HRIS integration — connecting Mango Training to your existing employee data system — is handled through MangoApps' [employee data](/solutions/employee-data) layer, which syncs roles, departments, and certification records automatically. For organizations evaluating how a unified platform compares to point solutions, the [Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026 and beyond](/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) provides a structured framework for that decision. ## How Does Mango Training Fit Into the Broader MangoApps Suite? Mango Training is one module inside MangoApps' broader employee experience platform. That means learning does not live in a separate system disconnected from communications, scheduling, and workforce management. When a policy changes, the same platform that notifies staff can also trigger a mandatory course reassignment and track completion — all without switching tools. Per IDC, employees spend an average of 2.5 hours per day searching for information. Centralizing training alongside communications and operations data directly reduces that drag. The [Training Connect](/key-features/training-connect) feature surfaces relevant courses inside the same interface employees already use for daily work, rather than requiring a separate login to a standalone LMS. For organizations that want to see how a comparable workforce has approached this kind of platform consolidation, the [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study) case study is a useful reference. ## The Bottom Line: What Mango Training Delivers for Healthcare Mango Training is a cloud-based LMS learning system built specifically for the operational realities of healthcare: high turnover, deskless frontline workers, strict HIPAA and regulatory compliance requirements, and the need for continuous learning and development without pulling staff off the floor. Here is what it concretely provides: - **Automated onboarding** that gives new hires immediate access to role-specific training, with mobile delivery for the 80% of healthcare workers who are deskless (per Emergence Capital) - **Compliance automation** that reassigns HIPAA and SOP operations courses on a schedule and exports transcripts for licensing boards - **Persona-based course targeting** so nurses, technicians, and administrators each see only what is relevant to their role - **Video and async delivery** for shift workers who cannot attend live sessions - **HRIS-connected roster management** that eliminates manual certification tracking - **Unified platform** — training, communications, and workforce data in one place, not three separate logins Organizations that treat learning and development as a strategic capability — not just a compliance obligation — see measurable reductions in turnover cost and faster time-to-competency for new hires. If you want to see how Mango Training maps to your specific hospital or health system, [schedule a personalized demo](/solutions/learning-management) or explore the [Break The Annual Review Cycle: The Executive's Guide To Creating A Culture Of Continuous Employee Development](/resources/break-the-annual-review-cycle) resource to build the internal case. --- # A 5-step strategy for successful intranet implementation **Author:** Christos Schrader **Published:** 2021-07-27 **Category:** intranet This post is an excerpt from our intranet implementation whitepaper of the same name. Download the full report here. Watch Melissa discuss the topic in a recent webinar here. Melissa Hoyos was brought on by symplr, a healthcare governance, risk and compliancesoftware provider with 1,500 employees, in early 2021 to overhaul the way the companyand […] # A 5-step strategy for successful intranet implementation Melissa Hoyos joined symplr, a healthcare governance, risk, and compliance software provider with 1,500 employees, in early 2021 with a clear mandate: overhaul how the company communicates internally. As Director of Internal Communications, she had already deployed Microsoft SharePoint at three previous organizations. She knew what a failed launch looked like—and she was determined not to repeat it. Hoyos selected MangoApps and structured the implementation around five principles she credits with making the launch succeed. According to IDC, employees spend 2.5 hours per day searching for information they cannot easily find. That figure puts the cost of a poorly structured intranet in concrete operational terms: lost time is lost capacity, and for a 1,500-person company, it compounds daily. The framework below addresses the organizational, technical, and cultural factors that separate intranets employees actually use from ones that quietly fail. ## Why most intranet launches fail after go-live The failure pattern is consistent across industries. According to Social Edge Consulting, 91% of organizations operate some form of intranet—yet only 13% of employees use those tools daily, and nearly a third never log in at all. SWOOP Analytics found that employees spend an average of six minutes per day inside intranet platforms. The adoption gap rarely traces back to the technology. Platforms fail when organizations deploy without clarity on what they are building the intranet *for*, without leadership visible enough to signal that the tool matters, and without a structure that reflects how employees actually work. For organizations where approximately 80% of the workforce is deskless—according to Emergence Capital—an intranet that requires a desktop login adds a structural barrier on top of those organizational ones. The five principles below address each of these failure modes directly. ## Step 1: Start with a vision and leadership buy-in An intranet can mean different things to different organizations. A healthcare company might build it around policy distribution and compliance acknowledgment. A retail chain might prioritize scheduling and frontline communication. A technology company might center it on knowledge management and cross-team collaboration. At symplr, the mandate was clear: create a central destination for company news and culture that email alone could not support. "We chose MangoApps for its ease of use," says Hoyos. "Our purpose was sharing company news. We didn't have anything prior—just email and Microsoft Teams. We saw the functionality was spot on for sharing company news, almost like a website, in a CNN kind of way." That clarity of purpose made leadership alignment straightforward. "I think you really need to take leadership along on the journey and get really clear about what the intranet is for," says Hoyos. "As long as you and your leadership are aligned, you feel empowered to say, 'This is what it's for. This is the philosophy.' Then later on, leadership won't be confused about why you're doing something." The vision should also account for workforce composition. Organizations managing a large frontline population—field crews, healthcare staff, retail associates—need to identify what percentage of their workforce lacks a company email address before selecting a platform. A [modern intranet](/solutions/modern-intranet) that supports device-agnostic access from personal smartphones changes the reachability equation for those employees from day one. ## Step 2: Ask the right questions during vendor demos The purpose of a vendor demo is not to see what the platform can do in general. It is to test whether the platform can do the specific things your vision requires. Hoyos went into demos with a clear hierarchy of priorities. "I really wanted the power to customize the home page," she says. "I had a vision and I knew what would work. Make sure that you go in with a vision, but be flexible on the small things. We got 99% of everything we wanted with MangoApps." Beyond design flexibility, enterprise intranet evaluations should include questions about security architecture. Organizations managing sensitive employee data—particularly in healthcare or financial services—need to understand how a platform handles role-based permissions, SSO and SAML 2.0 integration, audit logging, and mobile device access controls before the evaluation closes, not after go-live. Support quality is also a differentiating factor that rarely surfaces in a feature checklist. "Accessibility to the MangoApps support team has been phenomenal," says Hoyos. "With SharePoint, you have to be an engineer to learn things. If I wanted to redesign a page out of the box, there's no way—I'm not a designer or engineer. With MangoApps, if you have a concept, you can immediately implement it. It's been a lot easier than my last three experiences." ## Step 3: Relinquish control and get everyone involved This is the step internal comms professionals most often resist—and the one Hoyos credits as most important for long-term engagement. "At previous companies, I had control of everything that went on the intranet, or at least proofed and edited it," she says. "I think that approach can hurt engagement. It doesn't feel like you're owning something if somebody's constantly behind you checking and fixing it." At symplr, contributors were given publishing rights and trusted to use them. The result was a more active platform and a more distributed ownership model that did not depend on the internal comms team as a bottleneck. This model works when the platform's permission system is granular enough to define what each contributor can and cannot do. Departmental editors can publish to their own sections without touching company-wide announcements. Regional managers can post operational updates without accessing compliance documentation. Giving people ownership of their corner of the intranet while maintaining administrative oversight of the broader architecture creates engagement without chaos. ## Step 4: Get executives to promote the launch at every opportunity Employee adoption is directly correlated with how visibly leadership uses the tool. When executives post company news on the intranet—rather than sending it through email or announcing it only in all-hands meetings—they signal that the platform is the authoritative source of organizational information. At symplr, the executive team was an active presence on the intranet from day one. That visibility served two purposes: it established that the platform was a real communication channel rather than an IT project, and it gave other employees a reason to check in regularly. The launch period is the highest-leverage moment for this signal. Executive promotions—mentions in all-hands, links from email footers, visible activity on the platform itself—establish early habits that compound over time. Frontline employee replacement costs range from $4,400 to $15,000 per worker depending on role; organizations that solve the adoption problem in the first 90 days avoid the longer-term retention cost of a communication infrastructure employees never learned to trust. For organizations with a large frontline workforce, executive promotion should extend to mobile access specifically. Frontline workers who see their managers using the same platform from a smartphone—without a corporate email—adopt faster than those who perceive the intranet as a desk-worker tool. ## Step 5: Start small, then grow and iterate The most common implementation mistake is building the full vision before launch. Hoyos recommends the inverse: deploy the core use case, measure adoption, and add capabilities based on what employees actually need. At symplr, the initial focus was company news. That single use case was enough to establish the habit of checking the intranet. Subsequent features—department pages, knowledge base sections, forms—were added incrementally as the team understood how the platform was being used. This approach also reduces implementation risk. A limited launch surfaces usability issues with a smaller audience, before the platform is company-wide. Feedback gathered in the first 30 to 60 days shapes the full deployment in ways that no pre-launch planning can replicate. Post-launch, AI-powered content personalization changes the growth trajectory. A static intranet delivers the same content to every employee; a platform with intelligent content surfacing routes relevant policy updates, training content, and operational announcements to the employees most likely to need them. That shift—from broadcasting to personalization—is what separates a platform employees check from one they ignore. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents the specific patterns that determine whether an intranet gains or loses adoption momentum after launch, including reachability benchmarks for frontline workers and communication frequency models that sustain engagement past the initial rollout. ## How to measure intranet success after go-live The metrics that matter depend on the original vision. For symplr, success looked like consistent engagement with company news—employees reading, reacting, and sharing content rather than relying on email for organizational updates. For a frontline-heavy organization, the relevant metric might be the percentage of shift workers accessing safety updates before their shift begins. Across deployments, a few measurements tend to be most diagnostic: **Daily active users as a percentage of total workforce.** The 13% benchmark from Social Edge Consulting represents the industry baseline for intranets that are not working. A healthy intranet achieves 40–60% daily active use within six months of launch. **Time to information retrieval.** If the 2.5-hour daily search figure documented by IDC applies to your organization before launch, it should be measurable—and meaningfully lower—afterward. **Compliance acknowledgment rates.** For organizations using the intranet for policy distribution and sign-off, tracking acknowledgment rates by department and role turns the platform into an audit tool as well as a communication channel. The [ClearBox 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides evaluation criteria aligned with how enterprise buyers assess platform effectiveness over time—useful both during vendor selection and in post-launch reviews. ## What year two looks like The first year of an intranet implementation is about establishing the habit. The second year is about expanding the value. For most organizations, that expansion involves three moves: adding modules that address operational pain points identified during year one (forms, scheduling, knowledge management), deepening integration with existing HR and identity systems, and formalizing the governance model that determines who owns what on the platform. The governance questions often surface unexpected complexity. Which team owns the department pages? Who reviews outdated content? How are role transitions handled when employees change departments? These questions are easier to answer after a year of live operation than before launch—which is another reason to start small and let actual usage patterns inform the architecture. Healthcare organizations that consolidate disparate communication systems—scheduling tools, policy portals, compliance trackers—into a single platform find that second-year expansion is where operational ROI compounds. The [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study documents this pattern: initial deployment focused on communication, followed by phased expansion into knowledge management and operational workflows. --- The five-step framework Hoyos developed at symplr reflects lessons learned across repeated deployments in different organizational contexts. Vision before technology, the right vendor questions, distributed ownership, executive visibility, and incremental growth—each step addresses a specific failure mode that has ended intranet projects before they reached their potential. An implementation that gets these five things right does not just launch. It gets used. --- # Unlock Your Business Potential With Automations **Author:** Andrew Wong **Published:** 2021-07-23 **Category:** workplace-productivity With technology evolving at a rapid pace, it can be difficult to maintain your company’s competitive edge. Streamlining your business processes is crucial in closing this technology gap. Employees can then refocus their energy on creating quality output.  In this article, we’ll explain automated business processes and how they can transform your business operations. What […] # How Business Process Automation Unlocks Operational Efficiency Automating repetitive business processes is one of the most direct ways to reduce manual operations, free up employee time, and scale output without adding headcount. This article explains what business process automation is, where it delivers the most value by department, and how to evaluate whether your organization is ready to move beyond manual workflows. ## What Is a Business Process — and Why Does Automation Matter? A business process is a defined sequence of tasks executed to achieve a specific business outcome. These sequences exist across every department: HR onboarding checklists, IT access provisioning, sales approval chains, and operations instructions for field teams. When those sequences rely on manual steps — emails, spreadsheets, verbal handoffs — they introduce delays, errors, and inconsistency. Automations replace those manual steps with rules-based logic that triggers actions automatically. Common examples include: - Creating and enforcing business rules within existing workflows - Routing information between teams without extra communication channels - Sending notifications when project status changes or deadlines shift - Consolidating incoming data into a single record without duplicate entry - Triggering corrective task assignments when a process checkpoint fails — for example, when an inspection fails or an approval is missed, the next responsible party is automatically notified and assigned a follow-up task, closing compliance loops without manual follow-up For organizations managing deskless or frontline workers, no-code workflow automation can handle shift swapping, PTO requests, and routine approvals without IT involvement, making adoption faster across non-technical departments. ## Use Cases by Department Automation applies differently depending on the department's workflow structure. Here are concrete examples across common business functions: ### HR and People Operations HR teams spend significant time on repetitive data entry and status tracking. Automation platforms that integrate with HRIS, LMS, and payroll systems can sync user data and digitize onboarding, reducing manual data entry across HR workflows. This matters especially in high-turnover environments: per the 2024 WorkProud Study Retail White Paper, 4 out of 5 retail workers do not plan to stay long term — meaning HR teams are constantly cycling through onboarding without automation support. Automated onboarding workflows can assign training modules, send welcome communications, and provision system access the moment a new hire record is created — without a coordinator manually triggering each step. For teams looking to improve how performance data flows into reviews, [Closing the Information Gap in Performance Reviews](/articles/closing-the-information-gap-in-performance-reviews) covers how structured data collection reduces the guesswork in evaluation cycles. ### Scheduling and Shift Management Frontline operations teams — retail, healthcare, logistics — deal with constant schedule changes. Manual operations in scheduling create bottlenecks: a shift swap requires a manager to manually approve, notify, and update the schedule. Automated scheduling workflows reduce that friction significantly. According to internal benchmarks from frontline operations deployments, automated workflow tools produce an average 40% reduction in scheduling time for frontline operations teams. For healthcare environments specifically, where more than half of healthcare workers report burnout and overwork (per a recent study), reducing administrative load through automation directly affects staff wellbeing and retention. MangoApps' [solutions/shifts-schedules](/solutions/shifts-schedules) capabilities address this by automating swap requests, availability updates, and manager approvals in a mobile-first interface. ### Compliance and Audit Trails One underappreciated benefit of automation is the compliance record it creates. Every automated action is timestamped and logged. For regulated industries — healthcare, financial services, unionized workforces — this means that approvals, task completions, and escalations are documented without anyone manually maintaining a log. This creates defensible audit trails that hold up during grievance reviews or regulatory inspections. For organizations managing unionized employees, where documentation requirements are especially strict, [Managing a Unionized Workforce Is Different. Your Software Should Be Too](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) outlines why generic workflow tools often fall short. ### IT and Operations IT teams use automation to handle access provisioning, ticket routing, and system alerts. Operations teams apply it to SOP operations — encoding standard operating procedures as automated checklists that trigger in sequence, ensuring every step is completed and recorded. This is the practical definition of lean operations: removing waste from process execution by eliminating the manual coordination layer. ## What the Data Says About Automation ROI An Economist Intelligence Unit report found that 91% of companies reported increased capacity to handle volume after adopting automation, and 85% gained new revenue sources. These figures are frequently cited but should be read alongside organization-specific context — sample size and year of the EIU report were not disclosed in the original publication, so treat them as directional rather than definitive. A more specific figure: according to a Forrester Report, a company with 20,000 employees can realize $7.5 million in added value over three years by deploying integrated workforce automation. That figure accounts for time savings, error reduction, and improved workforce utilization. For a practical look at how one large employer achieved this at scale, the [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study) case study details the operational changes and outcomes. ## How to Know If Your Workflows Are Ready for Automation Not every process is a good automation candidate on day one. The strongest candidates share these characteristics: 1. **High frequency** — the task happens daily or weekly across multiple people 2. **Rule-based logic** — the decision at each step follows a consistent if/then structure 3. **Documented steps** — there is an existing operations manual or SOP that defines the correct sequence 4. **Measurable outcome** — you can track whether the process completed correctly Processes that require significant human judgment at each step — creative work, complex negotiations, nuanced performance conversations — are poor automation candidates. Start with the high-frequency, rule-based workflows and build from there. For a broader view of where workforce operations are heading, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the operational shifts organizations are prioritizing over the next two years. ## What to Look for in an Automation Platform When evaluating automation tools, mid-market operations teams without dedicated developers should prioritize: - **No-code configuration** — the ability to build and modify workflows without writing code or filing IT tickets - **Mobile accessibility** — especially for frontline and deskless workers who complete tasks on mobile devices, not desktops - **HRIS and payroll integration** — so automated workflows sync with the systems of record HR already uses - **Audit logging** — timestamped records of every automated action for compliance purposes - **Cross-department applicability** — a single platform that handles HR, operations, and scheduling workflows rather than a separate tool for each MangoApps' [solutions/workforce-management](/solutions/workforce-management) capabilities are built around these requirements, with no-code workflow configuration designed for operations managers and HR teams rather than developers. ## The Bottom Line: Automation Is an Operational Baseline, Not a Luxury The organizations that have already automated their high-frequency, rule-based workflows are not gaining a competitive advantage — they are meeting the operational baseline that their workforce and customers now expect. Those still running manual operations in scheduling, onboarding, approvals, and compliance tracking are absorbing costs in coordinator time, error correction, and employee frustration that automation would eliminate. The practical starting point: identify your three highest-frequency manual processes, confirm they follow rule-based logic, and map the steps. If a documented SOP or operations manual already exists, you have everything needed to configure an automation. If it does not, writing that documentation is the first step — and it will be useful regardless of what platform you choose. For HR teams specifically, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how automation fits into broader people operations strategy heading into the next planning cycle. --- # Company Newsletter Ideas for Employee Engagement **Author:** Alec Morrison **Published:** 2021-07-19 **Category:** employee-engagement The secret to adding interest to internal communication tools As internal communication tools have become increasingly common in the workplace, quality company newsletter ideas are essential for reading engagement. With the recent movement of shifting from email to enterprise social networks, employees have been accessing their company newsletters in new ways. The same challenge of […] ## The secret to adding interest to internal communication tools As internal communication tools have become increasingly common in the workplace, quality company newsletter ideas are essential for reading engagement. With the recent movement of shifting from email to enterprise social networks, employees have been accessing their company newsletters in new ways. The same challenge of actually getting people to read these still proves difficult, however. Many workers only skim the first couple headers, or ignore it altogether. This is a lost opportunity for your company to share important news and promote [employee engagement](/solutions/employee-communications). The secret to capturing your employees' attention from the newsletters is deceptively simple: include more positive, accessible announcements and present it in a visually appealing way. News stations and click-bait articles often rely on negative headlines to draw people in. Yet, an overabundance of pessimistic information promotes a bleak work culture that no one wants to be a part of. The reason for this is because of a phenomenon known as negativity bias. This means that your company will need to pay close attention to the type of information that is being shared. Too much negativity can turn employees away from reading your newsletters. The other mistake companies make when writing newsletters is not including enough interesting content. Workers will not waste their time reading something that is boring. Know your audience and create for them. Notably, per Gartner, 2023, 47% of workers struggle to find necessary information at least half the time — a problem that well-structured newsletters can directly address. An easy way to create engaging newsletters is to focus on creating content that is uplifting and relevant to your employees. Read ahead to find 5 company newsletter ideas for how to accomplish this. ## 5 company newsletter ideas for employee engagement ### #1 Provide thrilling updates Have a huge company-wide success that you want to tell everyone about? Make a spot for this in your newsletter! Let your employees know how great the company is doing and keep them up-to-date with the latest news. Also share any important, targeted announcements with monthly newsletters. These can track progress and communicate department adjustments to promote work improvements. Being honest and up to date with your employees creates an authentic brand reputation that helps retain them. Additionally, company updates keep workers on the same page and leads to a more efficient, unified workplace. Newsletters and updates targeted by role, location, and team outperform generic all-staff broadcasts for driving readership and action — a key employee engagement strategy when your workforce spans multiple departments or shifts. ### #2 Newsletter themes Connect with your employees by designing themed newsletters relating to a seasonal event! Building newsletters inspired by events and holidays can help raise spirit throughout your company. Creative newsletters keep employees intrigued with the fresh designs each month and helps connect them with the company as well. More company newsletter ideas include showing support for local events, such as city sporting events. This fun way to engage employees cultivates an inclusive community that helps them unite with each other. For teams in distributed or frontline environments — such as [grocery](/industries/grocery) or [healthcare](/industries/healthcare) — themed content tied to local events is especially effective at building belonging across dispersed locations. ### #3 Interactive questionnaires A fun way to connect with your employees is by asking them several fun questions relating to an ongoing event in the world. Employees can then answer and compare their opinions. For example, one question may ask "what is your favorite holiday food?" during the time of a certain holiday. Another scenario could relate to a business decision, such as including a question on the marketing team newsletter like "what new platform should we advertise our product on?" Employee engagement questionnaires like these help create interactive discussions and bring employees closer together through sharing their opinions. Employees can additionally learn about the various cultures of their coworkers, better connecting them with one another. Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback — and interactive newsletter surveys are a low-friction way to demonstrate that listening. ### #4 Celebrate employees Let the whole company or certain teams know when someone made an impressive accomplishment or completed an important job contribution. Showcasing the talents of your employees makes those honored feel appreciated, while motivating workers to perform their best as well. Shoutouts can also be done for what people have been accomplishing outside of work. This gives the company a chance to connect with its employees and show them that you care personally. For a deeper look at how recognition data can inform performance conversations, see [Closing the Information Gap in Performance Reviews](/articles/closing-the-information-gap-in-performance-reviews). Additionally, save time creating the newsletter and make it more visually appealing by using templates. This helps you avoid the faux pas of an inconsistent and poorly designed newsletter that no one wants to read. ### #5 Easily accessible news Use notifications to make sure that workers never miss an update and can view your newsletter instantly. Also, internal communication tools capable of mobile accessibility satisfies the needs of remote workers and those that prefer mobile alerts. This matters especially for deskless and frontline workers. Replacing paper-based and scattered communications with a single digital hub reduces operational friction and measurably improves frontline staff engagement. Employees navigating 6–8 disconnected tools daily are less likely to read or act on internal communications delivered through yet another channel — which is why consolidating newsletters into a single [employee app](/solutions/employee-app) with push notifications and mobile-first formatting is a concrete employee engagement strategy worth prioritizing. Present your information using multiple media formats to further personalize your newsletters for each employee. For example, embed videos directly in your newsletters for easy access. You can also provide podcasts in addition to written publications for those who prefer to listen to their news. Only 22% of company intranets currently deliver personalized content, per the State of the Digital Workplace & Modern Intranet, 2024 — meaning there is significant room to differentiate by targeting content by role, location, or team. ## MangoApps MangoApps' Posts & Newsletters software provides the communication tools needed to share real-time news and announcements for your employees. Streamlining a visually engaging, multimedia news tool helps share up-to-date company news to both desk and deskless workers. For a practical look at how one organization put this into practice, see [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology). Ready to go deeper on employee engagement strategies and internal communications trends? The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the formats, channels, and measurement approaches that are moving the needle this year. And learn more about MangoApps' Posts & Newsletters software to recognize how your business can boost its newsletter engagement rate below. ## How do you measure whether your company newsletter is actually working? Engagement metrics — open rates, click-throughs, and survey response rates — are the most direct signals, but they only tell part of the story. The business outcomes that matter most are retention and adoption. Organizations that replaced scattered communications with a unified frontline engagement hub have reported a 26% reduction in employee turnover and 90% frontline adoption within the first six months of deployment. Tying your newsletter program to these metrics — rather than stopping at "employees feel appreciated" — is what separates an employee engagement strategy from a one-off communications effort. Practically, start by establishing a baseline: track open rates for the first three issues, then segment your audience by department or location and compare performance. Per McKinsey research, 81% of leading companies effectively use data and analytics tools — applying that same discipline to internal communications is how you move from guessing to improving. ## What makes a newsletter actually reach frontline and deskless workers? Most newsletter advice assumes employees have a corporate email address and a desktop. For the 80%+ of the global workforce that is deskless — including workers in [healthcare](/industries/healthcare), [financial services](/industries/financial), and field operations — that assumption breaks the entire distribution model. Effective frontline newsletter delivery requires push notifications to personal or shared mobile devices, SMS-based alerts as a fallback, and content formatted for small screens without requiring a VPN or corporate login. Segmenting content by shift, location, or role ensures that a warehouse associate in one region does not receive the same all-staff blast as a corporate finance team member — and that neither group ignores the message because it feels irrelevant. ## How do newsletter themes and questionnaires connect to broader employee engagement training? Themed newsletters and employee engagement questionnaires are entry points, not endpoints. When employees respond to an interactive poll or engage with a recognition shoutout, that behavioral data surfaces which topics, formats, and voices resonate — information that can directly inform employee engagement training design and employee engagement courses. For organizations building a more structured approach, embedding engagement signals from newsletters into a broader learning and development strategy creates a feedback loop: what employees respond to in communications tells you what they care about, which shapes what training you prioritize. For more on that connection, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). --- # Measure Employee Engagement And Loyalty With eNPS **Author:** Amaya Kejriwal **Published:** 2021-07-19 **Category:** employee-engagement Having a great understanding of employee engagement can be the difference between high productivity and a resignation. Thus, decision-makers must implement the right tools to combat low employee morale. This article will highlight how an eNPS survey can provide you with a single metric to assess employee engagement and identify the path forward for your […] ## Measure Employee Engagement And Loyalty With eNPS Having a clear understanding of employee engagement can be the difference between high productivity and a resignation. Decision-makers must implement the right tools to combat low employee morale. This article explains how an eNPS survey provides a single metric to assess employee engagement, identify where your workforce stands, and chart a path forward. ## eNPS — Your Next Employee Engagement Tool Employee Net Promoter Score (eNPS) is an internal scoring system that helps managers and leaders assess the levels of employee loyalty and engagement. It is an easy-to-use method that places employees into three different categories based on their feedback: promoters, passives, and detractors. For organizations looking to move beyond anecdotal feedback, eNPS functions as a foundational layer within a broader [employee engagement](/solutions/employee-engagement) measurement strategy — connecting pulse data to real decisions about communications, training, and HR workflows. ## How To Implement eNPS ### Create a Survey The first step when implementing an eNPS survey is to figure out how you are going to create and distribute it to all of the employees in the company. This can be especially challenging if your company has a mix of desk and deskless workers. Per Emergence Capital, 80% of the global workforce is deskless — meaning the majority of employees may lack company email or consistent desk access, making mobile-first survey delivery essential rather than optional. An online survey system addresses this directly, allowing you to create a secure, reliable, and easy-to-understand employee engagement survey that all employees can access regardless of location or device. ### Survey Content One of the best things about an eNPS survey is how easy it is to create and fill out. Generally, you only have to ask your employees two questions to be able to calculate your eNPS and get feedback: 1. On a scale from 1-10, how likely are you to recommend us as a place to work for your family and friends? 2. Why did you choose this rating? These questions, although seemingly simple, provide great insight into the thoughts and attitudes of employees. By providing both quantitative and qualitative data, there is plenty of information for the company to reflect on and use in decision-making. Plus, because the survey is so short, you are much more likely to have a large survey sample to analyze. Employee engagement questionnaires that are shorter consistently achieve higher completion rates, which improves the statistical reliability of your eNPS. ### Calculate The Score Once you have sent out the survey and received all of the data, it's time to calculate the eNPS. Employees are split into three different groups depending on the rating they give their employer: - **Promoters (9–10):** Highly engaged employees who would actively recommend the company as a place to work. - **Passives (7–8):** Satisfied but not enthusiastic; unlikely to advocate and potentially open to other opportunities. - **Detractors (0–6):** Disengaged employees whose experience is negatively affecting morale and, potentially, retention. #### The Formula **eNPS = % Promoters − % Detractors** Passives are excluded from the calculation. The resulting score ranges from −100 to +100. ### Interpreting Your eNPS eNPS scores can vary from -100 to 100. Generally you want your score to be positive, which would mean that you have more promoters than detractors. Based on the type of company, you may want to consider segmenting eNPS scores based on job type or location. For instance, you could have a scenario where you find that most of your promoters are corporate employees, and most of your detractors are frontline employees. Segmenting eNPS by role type is especially critical for organizations where frontline workers operate without a desk, VPN, or company email, as their experience diverges sharply from corporate employees. In this case, it would be crucial to understand what you are doing right in the office, and how you are failing your frontline workforce. Separating scores based on job type ensures that all voices are represented and the score is an accurate representation of employee sentiment. It may also be beneficial to look at how eNPS scores change over time. If your eNPS scores are trending upwards, it means the changes that were made are working. If they trend downwards, then you need to go back to the drawing board and try to come up with a different solution. Acting visibly on eNPS feedback — closing the loop with employees — is cited as the primary driver of score improvement over successive survey cycles, not the survey cadence itself. Employees who see their input translated into visible action are far more likely to participate in future rounds and to shift from passive to promoter over time. ## Reaching Remote, Hybrid, and Frontline Employees Traditional employee engagement surveys were designed for desk-based workers with company email accounts. That model excludes the majority of the global workforce. Per Emergence Capital, 80% of workers are deskless, and frontline employees in industries like retail, hospitality, and healthcare are systematically underrepresented when survey delivery relies on desktop intranets or email. For remote and hybrid teams, the challenge is different but equally real: without a shared physical space, engagement signals are harder to read, and survey fatigue can set in quickly if cadence is not calibrated. A short, mobile-accessible eNPS survey sent on a predictable schedule — quarterly is a common starting point — gives distributed teams a low-friction channel to register their sentiment without requiring them to log into a system they rarely use. Per Social Edge Consulting, only 13% of employees use an intranet daily, and nearly a third never log in at all, which underscores why survey delivery cannot depend on intranet access alone. For organizations in frontline-heavy sectors, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines how mobile-first engagement tools are closing the gap between corporate and field-based employee experience. ## Transform Your Workplace eNPS surveys benefit companies by providing key insights for managers to comfortably interpret the results and make quick decisions. Managers can conduct these surveys anytime, anywhere, and can grasp the team pulse regardless of employee location. They are the most cost-effective method to empower employees and value their input, ultimately inspiring beneficial change within the company. Though employee engagement will not come directly from the surveys themselves, simply using eNPS surveys boosts employee morale as their opinions are being acknowledged. Transparency with survey results also bolsters team relationships and generates insights from both the quantitative and qualitative data analysis. These insights inform the actions needed to improve the company workflow. If an employee can experience their impact on the company, it increases their emotional investment. This can reduce fatigue, prevent employee churn, and lead to an enrichment of the overall company culture. Organizations that have invested in a unified employee experience platform have seen measurable results: OU Health achieved 87% workforce engagement within months of launching a branded employee app, and British Airways attributed a 30-point engagement score increase to consolidating employee communications and feedback into a single platform. For a broader view of how engagement metrics connect to organizational performance, [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) provides current benchmarks across industries and regions. ## eNPS as One Layer of Your Employee Engagement Software Stack eNPS is a diagnostic tool, not a complete solution. The score tells you where sentiment stands; it does not automatically fix the underlying drivers. The organizations that see sustained improvement are those that connect eNPS insights to action workflows — using the data to trigger targeted communications, identify training and employee engagement gaps, or surface HR self-service needs. For example, a cluster of detractors in a specific department might indicate a need for manager development, pointing toward [performance management](/solutions/performance-management) workflows. A pattern of low scores among new hires might signal onboarding gaps that employee engagement training or structured learning paths could address. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading organizations are integrating pulse survey data into broader talent and engagement strategies. Employee engagement software that connects survey delivery, results analysis, and follow-up action in one place removes the friction that causes insights to stall between the data and the decision. When employees see that a survey led to a visible change, participation rates rise and scores improve — reinforcing the cycle. ## MangoApps Every company should have the right tools to ensure that each eNPS survey is reliable, secure, and easy to implement. With MangoApps, you can easily gauge employee satisfaction and gain insight into your teams through a single employee experience platform. In addition to being easy to set up, the platform has all the features necessary to ensure honest and useful feedback from employees: - Templates for easy survey creation, including eNPS surveys, 360° feedback, and more - Built-in employee directory, enabling segmentation and targeting within a single hub - Mobile-friendly platform for enterprise-wide use, including deskless and frontline workers - Real-time tracking and data exportation for in-depth analysis - Integrations that connect survey insights to communications, learning, and HR workflows ## Frequently Asked Questions About eNPS ### How often should we run an eNPS survey? Most organizations run eNPS surveys quarterly, though some prefer a bi-annual cadence for smaller teams. The key variable is not frequency but follow-through: per research cited across employee engagement product benchmarks, the primary driver of score improvement is acting visibly on results between cycles. Running surveys more frequently without closing the loop on prior feedback accelerates survey fatigue and depresses participation rates. For remote and distributed teams, a consistent, predictable schedule matters more than a high-frequency one. ### What is a good eNPS score? eNPS scores range from −100 to +100. A score above 0 means you have more promoters than detractors, which is the baseline threshold. Scores between 10 and 30 are generally considered good; scores above 50 are considered excellent. Benchmarks vary by industry — frontline-heavy sectors like retail and hospitality typically see lower baseline scores than knowledge-worker organizations, which makes segmentation by role type and comparison against industry peers more meaningful than chasing a universal target. The [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides context on how platform choice affects engagement outcomes across sectors. ### How do we act on eNPS results to actually improve the score? Closing the loop is the single most important step after calculating your eNPS. Share results transparently with employees, acknowledge what the data shows — including negative findings — and communicate the specific actions the organization is taking in response. Detractor feedback, in particular, should be treated as a prioritized input into workflow, training on employee engagement, or management practice changes. Organizations that treat eNPS as a listening mechanism rather than a reporting exercise consistently see score improvement over successive cycles. --- # 5 Company Pitfalls for Emergency Communication **Author:** Alec Morrison **Published:** 2021-07-19 **Category:** frontline-communication When unforeseen situations arise, it is critical to have an emergency communication system on hand to easily communicate the next steps to your workforce. Ram Tool experienced this firsthand when a massive ice storm struck parts of Texas in February 2021. Rather than the operations manager calling each employee individually at the crack of dawn, […] ## 5 Company Pitfalls for Emergency Communication When unforeseen situations arise, it is critical to have an emergency communication system on hand to easily communicate the next steps to your workforce. The five most common pitfalls — lack of preparation, communication delays, inconsistent information delivery, one-way outreach, and missing acknowledgement tracking — each have concrete solutions that can be built into your standard operating procedures (SOP operations) before a crisis ever hits. Ram Tool experienced this firsthand when a massive ice storm struck parts of Texas in February 2021. Rather than the operations manager calling each employee individually at the crack of dawn, Ram Tool was able to navigate the emergency efficiently and notify their workers of the multiple day shut down. Using a single alert, Ram Tool was able to save the operations manager hours, and informed the entire workforce simultaneously. Delivering and managing a strong communications system is essential when tackling the difficult process of a crisis. Below, we have explained the 5 pitfalls to avoid when building an emergency communication system, as well as what solutions to focus on to greatly enhance a company's crisis management. ## 1. Lack of Emergency Communication Preparation Many companies fail to properly prepare for an emergency. When a time-sensitive crisis does occur, employees are forced to scramble and are unsure of what actions to take. With minimum employee communications training, they are likely to make sloppy decisions that could potentially harm the business, or even worse, harm themselves. ### Solution: Prepare, prepare, prepare! The best way to remove any potential room for error for an emergency or crisis is to prepare. Your company should have a mass notification system in place so that employees are informed of what to do during a crisis. Employees should frequently undergo emergency communication drills, like fire drill procedures, to ensure that all understand in the event of a crisis. Take the time to prepare and educate your workers prior to an actual emergency. In doing so, you can diminish any confusion that could arise during the crisis, and ensure that your employees are equipped to handle any situation. Documenting these procedures in a living [operations manual](/resources/2026-workforce-operations-trends-ebook) — rather than relying on manual operations and tribal knowledge — means every team member can reference the same source of truth when seconds count. ## 2. Emergency Communication Delays Relaying emergency information as quickly as possible to employees can be challenging in a crisis. When creating a mass notification system, make sure to be clear and concise. Employees can often develop incorrect assumptions about the plan and fail to prepare accordingly. ### Solution: Communicate frequently and in a timely manner During a crisis, time is a key factor in determining whether your company successfully manages the situation. Sending out clear messages immediately during the emergency will allow your employees to all be quickly notified. Consistently formatting your messages will keep all your employees on the same page under one mass notification system. This eliminates any margin for error that could potentially harm your company or its employees. Communicating frequently to keep your workers up-to-date can make a huge difference and drastically improve your company's workflows. Note that per Gartner, 2023, 47% of workers struggle to find necessary information at least half the time — a gap that becomes dangerous during a crisis. Building clear, templated operations instructions into your emergency workflow directly addresses this risk. ## 3. Inconsistent Information Delivery Oftentimes, companies have no consistent delivery system for sending out emergency messages to their workforce. As information is sent out with conflicting formats, workers are prone to misinterpret the information. ### Solution: Consistent and purposeful messages Messages and updates should be concise and only display information that your employee needs. Using a template develops a sense of consistency for all employees that can lead to the easy digestion of information. You can also segment the delivery of information based on specific teams or departments. For example, factory workers should only receive information intended for them. By segmenting the distribution of information, your company can clear up any confusion and streamline your mass notification system. A dedicated [employee communications platform](/solutions/employee-communications) makes this segmentation straightforward to configure and audit after the fact. ## 4. One-way employee communication outreach Your company likely has a dispersed workforce. Employees are often working remote, across different office locations, or on-the-go. This can make it very challenging to reach all your employees through a single communication channel during a crisis. ### Solution: A multi-channel communication system Adopting a multi-channel emergency communications system will maximize the range of communication to all employees during a crisis. This arrangement will reach more levels of employees while maintaining the simple administration controls of the previous singular mass notification system. For frontline-heavy organizations, the access barrier is especially acute. Frontline employees can access emergency alerts, rosters, and critical documents via single-sign-on mobile without a corporate email or VPN, eliminating access friction during a crisis (Joinblink / Blink product page). In a 550+ frontline-employee organization, a single mobile hub achieved 95% employee reach — a benchmark that illustrates why channel design matters as much as message content. Replacing paper processes and siloed systems with a single mobile hub also reduced employee turnover by 26% for one frontline-heavy organization (Joinblink / Go North West case study), underscoring that the right [employee app](/solutions/employee-app) pays dividends well beyond the emergency itself. The Ram Tool ice-storm scenario is a useful reminder that connectivity itself can fail during a weather crisis. Ensuring your platform supports offline access to critical documents means workers can reference operations instructions even when cell service is degraded. ## 5. Lack of Employee Acknowledgement Understanding which workers have viewed and acknowledged each alert is crucial. Organizations often have minimal information on whether employees have viewed the information or not. Not understanding which employees have viewed the alert can prevent companies from re-notifying specific individuals. ### Solution: Monitor insights and feedback Companies should implement a system that tracks views and enables employees to respond via messages to each alert. This gives full insight to who has viewed the crisis update and allows the organization to plan accordingly. Insight-based data then enables the capability to re-send alerts, verifying that employees have seen the message. Additionally, two-way communication can provide the ability for workers to gain clarity about alerts or give feedback. With insights and feedback, your company can assure employees are fully prepared for a crisis. Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback — making two-way acknowledgement a retention tool as much as a safety tool. Given that replacing a single frontline employee costs between $4,400 and $15,000 on average, the financial stakes of poor crisis communication extend far beyond the incident itself. ## MangoApps With MangoApps, you can share real-time emergency messages to ensure the safety of 100% of your employees. Streamlining a multi-channel communications system on a singular employee communications platform allows your organization to send accurate information across all departments in your company. If you would like to learn more about MangoApps' Emergency Alerts feature and how it fits into a broader internal communications strategy, explore the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) for current benchmarks and planning frameworks. --- ## How Often Should Emergency Communication Drills Occur? Frequency depends on workforce size, industry risk profile, and regulatory requirements, but a practical baseline is quarterly tabletop exercises for leadership and at least two full-drill simulations per year for all staff. High-risk industries — healthcare, grocery, and financial services — often run monthly scenario reviews. The key is to treat drills as a living part of your SOP operations rather than a one-time compliance checkbox. After each drill, document gaps and update your operations manual before the next cycle. ## What Metrics Indicate a Successful Emergency Communication System? Three metrics are worth tracking consistently: - **Reach rate:** What percentage of employees received and acknowledged the alert within the first 15 minutes? The 95% benchmark achieved by one frontline organization using a single mobile hub is a useful target. - **Time-to-first-message:** How many minutes elapsed between the triggering event and the first outbound notification? Shorter is better; anything over 10 minutes in a life-safety scenario is a process failure. - **Drill-to-live gap:** Do employees behave during real events the way they behave during drills? A wide gap signals that your employee communications training is not translating to muscle memory. Per McKinsey research, 81% of leading companies effectively use data and analytics tools — applying that discipline to crisis communication metrics is how organizations move from reactive to prepared. ## How Do You Prevent Misinformation from Spreading During a Crisis? Misinformation fills the vacuum left by delayed or inconsistent official messaging. Three practices close that vacuum: 1. **Designate a single authoritative channel** — employees should know before a crisis which platform carries official updates, so they do not default to informal group chats or social media. 2. **Publish update cadences** — even a message that says "no new information, next update in 30 minutes" prevents speculation. 3. **Correct errors publicly and quickly** — if an earlier message contained wrong information, send a clearly labeled correction through the same channel. Transparency builds the trust that keeps workers from seeking outside sources. For organizations managing unionized or highly regulated workforces, consistent and documented messaging also protects against grievances and compliance exposure. See [Managing a Unionized Workforce Is Different. Your Software Should Be Too.](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) for additional context on communication governance in those environments. --- # How A Workplace Democracy Encourages Employee Engagement **Author:** Andrew Wong **Published:** 2021-07-19 **Category:** employee-engagement A common pain point for managers, HR, and leadership is retaining a high level of employee engagement. With many methods at hand, a study found that the best way to encourage employee engagement is through an open flow of information. One easy, low-cost solution for this is establishing a workplace democracy. What does a workplace democracy […] # How A Workplace Democracy Encourages Employee Engagement Workplace democracy is a compelling idea in theory: give employees a voice, earn their investment. In practice, most implementations reach only a fraction of the workforce. Per Emergence Capital, 80% of the global workforce is deskless — field workers, retail associates, healthcare staff, hospitality teams — and traditional democratic participation channels were built around corporate email addresses, intranet logins, and office-based access. That structural exclusion doesn't just limit the idea's reach. It actively undermines it. A democracy where the majority of participants cannot vote is a headquarters survey with a generous name. This is the problem most workplace democracy conversations skip. The bottleneck isn't leadership buy-in or cultural resistance. It's infrastructure — the specific set of access and tooling decisions that determine whether democratic participation is available to all employees or only to the ones already sitting inside the organization's digital perimeter. ## The problem with how most organizations define employee voice Most organizations frame employee engagement as a communication problem. Hold more town halls, send more surveys, install an open-door policy. The data suggests otherwise. Per Social Edge Consulting, 91% of organizations operate an intranet. Yet nearly a third of employees never log in, and only 13% use intranet tools on a daily basis. Per SWOOP Analytics, the average daily time spent on SharePoint-based intranet environments is six minutes — closer to a file cabinet check than a democratic forum. Per IDC, employees spend 2.5 hours per day searching for information across fragmented systems. These numbers don't describe a workforce that lacks willingness to engage. They describe a workforce that lacks the infrastructure to participate. Open-door policies don't help the nurse finishing a night shift at 6 a.m. Intranet surveys don't reach the retail associate who never received a corporate email address. Town halls don't substitute for a persistent, searchable record of decisions that workers can access on their own schedule. ## What workplace democracy actually requires A workplace democracy is the use of democratic principles — open discussion, shared decision-making, voting, and transparent communication of results — to give every employee genuine influence over their work. The operative word is every. When democratic tools exclude the majority of employees by design, engagement improvements cluster at headquarters while frontline turnover continues unchanged. True workplace democracy has three structural requirements that the standard playbook misses: **Access without corporate credentials.** Frontline employees are structurally excluded from traditional participation channels because they lack corporate email addresses or VPN credentials. Any platform that requires either cannot serve your deskless workforce. Mobile-first access on personal devices, with login options that don't depend on IT provisioning, is a prerequisite for inclusion — not a premium feature reserved for enterprise deployments. **Asynchronous participation.** Democratic participation that happens only in scheduled meetings or during business hours excludes shift workers, field teams, and employees across multiple time zones. Persistent discussion threads, scheduled voting windows, and notification-driven feedback tools allow participation to happen on the employee's schedule rather than the office's. **Visible closed-loop accountability.** The signal that kills participation faster than any access barrier is feedback that visibly disappears. When employees submit input and never see what happened to it, they stop submitting. Organizations that sustain democratic engagement publish results, document decisions, and connect employee input to action — not as a gesture, but as the mechanism that keeps participation rates up over time. ## Why the frontline dimension changes the business case For retail, hospitality, and similar industries, frontline employees aren't an edge case — they are the majority of the workforce. Per Emergence Capital, the deskless workforce represents 80% of global workers. Replacing a disengaged frontline employee costs between $4,400 and $15,000 depending on role and industry. At that cost, workplace democracy isn't a culture initiative — it's a cost-avoidance strategy with a measurable return. The adoption data strengthens the case. Organizations that reach 90% or higher employee adoption of engagement tools within the first six months see measurable engagement score increases. Access and adoption are the bottleneck — not willingness to participate. OU Health achieved 87% workforce engagement within months of deploying a branded, inclusive communications platform that reached staff who had previously been outside the system entirely. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how workforce engagement patterns vary by industry — useful for benchmarking your current frontline participation rate against sector averages. ## The three implementation decisions that determine whether it sticks Platform choice matters less than implementation quality. Organizations that build lasting democratic engagement tend to make three decisions correctly from the start. **Scope the decisions that are genuinely open to input.** Workplace democracy fails when employees discover their votes are advisory in practice, even when framed as binding. Before launching any participation program, define which decisions go to a vote, which solicit feedback only, and which remain with leadership. This distinction isn't a limitation on democracy — it's what makes participation feel credible. Employees who understand the scope of their input before participating treat disagreement as productive dialogue rather than evidence of a broken process. Common decision categories that benefit from genuine employee input include recognition nominations, process improvement priorities, team norms, and workplace policy changes that affect daily routines. Strategic decisions can still incorporate employee perspectives through structured feedback without requiring a vote on outcomes employees lack the full context to evaluate. **Design participation for the employees who are hardest to reach.** The easiest way to run a workplace democracy is to send a survey to the employee distribution list. The problem is that list excludes every employee without a corporate email address. A distribution strategy that reaches your full workforce — including frontline, part-time, and field employees — requires mobile-first notification, personal device access, and participation windows that accommodate shift schedules. Employees already lose over four hours per week switching between disconnected systems. Consolidating ballots, discussion, and results on a single platform eliminates the context-switching that turns a two-minute participation moment into a friction-heavy process. Per IDC, the information-retrieval overhead alone — 2.5 hours per day — signals how much friction employees are already absorbing. Adding a separate participation tool multiplies that cost rather than reducing it. **Close the loop visibly and consistently.** Organizations managing complex labor relationships often have the clearest models of what closed-loop communication requires. The piece [Managing a Unionized Workforce Is Different. Your Software Should Be Too.](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) addresses how inclusive communication tools navigate structured labor environments — the core principle applies broadly: employees stay engaged when they can trace their input to a visible outcome. Closing the loop isn't a single announcement after a vote. It's a persistent record — searchable, accessible on any device, available to an employee hired six months after the decision — of what was decided and why. Teams that archive discussion threads alongside decision records give future employees the context that would otherwise evaporate during personnel turnover. ## Measuring whether democratic engagement is actually working Measurement starts before implementation. Establish a baseline using an employee engagement survey or employee engagement questionnaires distributed before launching democratic participation tools. Track participation rates in votes and discussions as the leading indicator — adoption predicts engagement score movement before the score itself reflects the change. Follow up with pulse surveys at 30, 60, and 90 days. Qualitative signals matter alongside quantitative ones: voluntary turnover rates, the ratio of questions answered inside the platform versus escalated to managers, and the frequency of unsolicited employee feedback. Organizations that set these baselines before launch and review them on a regular cadence consistently move adoption faster than those that measure only when someone asks. Per research covered in [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), organizations where leaders consistently act on employee feedback see meaningfully higher retention and performance outcomes. The infrastructure that makes that feedback loop operational — persistent, searchable, accessible to every worker regardless of shift or location — separates a workplace democracy that compounds over time from programs that peak at launch and decay. Measurement is what reveals which side of that line your organization is on. ## The one change that determines the outcome Most workplace democracy implementations stall for the same reason: they reach the employees who were already well-connected and leave the others out. The frontline workers, shift-based teams, and field staff who would benefit most from democratic participation are exactly the ones the standard playbook fails to include. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring communication infrastructure to sustain org-wide engagement — not as a one-time launch event, but as an operational practice built into how work gets done. The question worth asking before investing in any engagement initiative is not "do we have a voting tool?" but "can every employee in our organization actually use it?" For industries with large deskless populations, the answer is usually no — and that gap is where engagement scores stall, turnover concentrates, and the business case for workplace democracy remains stuck at the level of aspiration rather than measurable outcome. Closing that access gap is the implementation task. Everything else follows from getting every employee into the room first. --- # How To Improve Employee Retention **Author:** Ella Foley **Published:** 2021-07-13 **Category:** people-operations Why do you need to improve employee retention? Taking the steps to improve employee retention is well worth the effort. Not only is low employee retention a pain to manage from an HR perspective, it also is extremely costly. In fact, replacing a single employee can cost an organization about 50-60% of that worker’s salary. […] ## Why do you need to improve employee retention? Taking the steps to improve employee retention is well worth the effort. Not only is low employee retention a pain to manage from an HR perspective, it also is extremely costly. In fact, replacing a single employee can cost an organization about 50-60% of that worker's salary. Working to improve your employee retention rate can provide countless benefits to your company, including increased productivity, higher [employee engagement](/solutions/employee-engagement), and a positive workplace culture. Below, we provide 7 cost-effective ways for you to improve employee retention within your organization. ## 7 ways to improve employee retention: #### #1: **Start strong** during onboarding Onboarding is one of the most important interactions a company has with each employee, as it sets the tone for the long-term professional relationship. New hires should come in feeling welcome, engaged, and unified, like they're joining a community where they will forge friendships, learn, and contribute a great deal. You can provide a solid foundation for employee retention by making new hires feel welcomed during the onboarding process. It doesn't hurt to provide a personal touch as well by introducing them to the rest of their colleagues. Try creating a personalized 'welcome' section for new employees and displaying it on your company's internal dashboard. In addition, a smooth onboarding process is critical to the long-term level of engagement of an employee. Supplying new hires with the resources, information, and training they need to get started immediately can make a huge difference in morale, satisfaction, and their long-term outlook. Digitizing onboarding through a mobile-accessible platform can cut new hire ramp time by 50%, directly reducing early-tenure attrition risk — a meaningful gain given that employees already navigate 6–8 disconnected tools daily, fragmenting communication and eroding engagement from day one. #### #2: **Consistently provide positive feedback** Another way to improve employee retention is by implementing strong feedback programs within the organization. Studies show that for optimal team performance, employees need approximately 5 positive comments for every negative one. By providing frequent positive feedback you can make major strides in boosting the morale and satisfaction levels of your employees. Pairing feedback programs with structured [performance management](/solutions/performance-management) practices ensures that recognition is consistent and tied to measurable outcomes. In addition to providing positive feedback, be sure to also celebrate the small accomplishments of individual employees. A little appreciation from top brass can go a long way in improving long-term employee satisfaction. #### #3: **Increase team recognition** & reward model employees Recognize teams and groups for a job well done. This can make every member feel appreciated and can be as effective as recognizing people individually. By celebrating a team's achievement, you can encourage other groups and teams to work more cohesively. A good way to reward teams for their hard work is with a recognition program. You can use a point system to automatically keep track of prize handouts. Workers can redeem their points for prizes like gift cards, retreats with coworkers, or even extra PTO! Nonmonetary prizes can be motivating too. Try providing options like having lunch with the CEO or winning a convenient parking space. By taking the steps towards improving employee recognition, you can ensure the longevity of your employees, while making your company a great place to work. Recognition programs tied to HRIS data can automatically sync employee roles and milestones, enabling timely, personalized recognition at scale — reframing recognition not as an occasional gesture but as an integrated retention system. See how this works in practice in [From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program). #### #4: Use gamification & awards Another way to improve employee retention is by leveraging digital awards and a gamification system within the workplace. This will help add excitement and get employees in a competitive mindset. Each time your top employees exceed expectations, you can reward them with gamification points. By creating a gamification system, you can encourage employees to truly go above and beyond, helping improve employee retention. A bonus is that game leaderboards also give employees an easy way to learn each other's names, which helps create a connection across colleagues you weren't previously familiar with. In addition to a gamification system, you can use digital awards to honor employees for their achievements. Digital awards are easy to bestow and can motivate others in your company if you display them on individual profiles, a public dashboard, and the company newsfeed. #### #5: **Create workplace connections** Creating an environment where workplace connections form naturally is the ideal environment that HR professionals strive for. Getting to that point means you have to enable employees with a tool that allows them to communicate and collaborate with each other regardless of where they are. There are many employee engagement software tools available that can get the job done. By providing an online space for workers to have conversations and collaborate on business projects, you can streamline productivity while creating a positive work environment that people will want to be a part of. Not to mention, getting to meet coworkers fosters friendships that can ultimately improve employee retention and keep your employees sticking around longer. #### #6: Celebrate personal and work milestones Celebrating your employees' personal and work milestones is another easy way to keep them happy and improve employee retention. Celebrating employee's birthdays is a simple way to make sure they feel appreciated. Greeting cards are a great way to do this and are easy to customize to each individual. While getting everyone in the office to sign a card can be tiresome, doing this virtually can streamline and automate the process, making it even easier to implement. You can also remind long-term employees that your company values them by celebrating their work anniversaries. This process can be automated so that employees can easily congratulate each other on another year with the company. #### #7: **Recognize frontline & remote employees** While each of these staff appreciation ideas is essential, it is equally important to reward workers who are not in the office as well. This includes frontline workers, factory employees, remote workers, or those that are on-the-go. Per Emergence Capital, 80% of the global workforce is deskless — meaning the majority of employees may never sit at a desk or have a company email address. Organizations with a mix of frontline and desk workers need to be able to meet each employee where it's most convenient for them. Frontline employees can be reached via push notifications, SMS, and in-app alerts without requiring a company email address or VPN — closing a retention gap that traditional intranet tools consistently miss. Per Social Edge Consulting, only 13% of employees use an intranet daily, and nearly a third never log in at all, which means desk-centric retention programs leave the majority of your workforce behind. We recommend equipping your entire workforce with an employee experience platform that is accessible both in-office and through a mobile device. This will help connect everyone within your workforce and can go a long way in bridging the gap between your desk and frontline employees. For a deeper look at what to evaluate, the [Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026 and beyond](/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) is a practical starting point. ## MangoApps MangoApps is an **all-in-one employee app**. It provides all the tools company leaders and employees need to connect and empower 100% of your workforce. With MangoApps, you can level-up your company communication, engagement and operations with a unified app for both desk and deskless employees. OU Health achieved 87% workforce engagement within a few months of launching a branded employee app on the platform — a result that reflects what a unified employee experience platform can deliver when recognition, communication, and onboarding tools work together. --- ## How do you measure whether your retention efforts are working? Improving employee retention requires more than implementing programs — it requires tracking whether those programs are moving the needle. The most reliable leading indicators include voluntary turnover rate (tracked monthly, not annually), 90-day and 1-year retention rates by department, employee engagement survey scores, and eNPS (employee net promoter score). Employee engagement questionnaires administered quarterly give HR teams a consistent signal before attrition becomes visible in headcount data. Pairing survey data with platform analytics — such as recognition frequency, onboarding completion rates, and intranet login rates — gives a fuller picture. Per SWOOP Analytics, the average employee spends only six minutes per day using intranet tools, so low engagement scores often reflect access and usability gaps as much as cultural ones. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines the metrics HR leaders are prioritizing this year. ## What role does training play in employee retention? Training and employee engagement are closely linked: employees who feel they are growing are significantly less likely to leave. Employee engagement training — whether delivered through manager coaching programs, structured learning paths, or embedded microlearning — signals to employees that the organization is invested in their development. A [learning and development strategy embedded in daily work](/articles/learning-and-development-strategy-embedded-in-daily-work) is more effective than periodic off-site courses because it reduces the friction between learning and doing. Employee engagement courses tied to role-specific skills also address a common driver of disengagement: the feeling of being stuck. Per IDC, employees spend 2.5 hours per day searching for information — time that structured training and a well-organized employee experience platform can reclaim and redirect toward productive work. ## How do you retain frontline and deskless employees specifically? Retaining frontline workers requires a different approach than retaining desk employees. Because 80% of the global workforce is deskless (per Emergence Capital), generic retention strategies built around email newsletters, desktop intranets, or manager one-on-ones will miss the majority of your workforce. Effective frontline retention programs share three characteristics: mobile-first access that works without a company email or VPN, recognition systems that reach workers on the floor or in the field in real time, and scheduling and communication tools that reduce the daily friction that drives frontline turnover. Industries like [retail](/industries/retail) and [hospitality](/industries/hospitality) face particularly acute frontline retention challenges, where shift-based schedules and high turnover rates make automated, mobile-accessible recognition and communication tools a practical necessity rather than a nice-to-have. --- # The Complete Guide To Deskless Worker Communication **Author:** Christos Schrader **Published:** 2021-05-20 **Category:** employee-engagement Deskless workers are an underserved majority By deskless workers, we mean anyone whose job doesn’t require sitting at a desk all day—often also called frontline workers. This includes retail employees, construction workers, nurses and doctors, and everyone else at the front lines of your industry. In this article, we will discuss the massive opportunity many […] ## Deskless Workers Are an Underserved Majority By deskless workers, we mean anyone whose job doesn't require sitting at a desk all day—often also called frontline workers. This includes retail employees, construction workers, nurses and doctors, and everyone else at the front lines of your industry. Deskless workers make up 80% of the global workforce, per Emergence Capital, yet only 22% feel their job is important to the company vision. That gap stems from lacking both communication from leadership and access to modern employee engagement tools. This guide explains why deskless worker communication breaks down, how to fix it in five actionable steps, and what to look for in an employee experience platform that actually reaches people who are never at a desk. In most industries, deskless workers are the vast majority of employees. They are also often the ones making the product and/or interacting with customers. Despite this, they are neglected or ignored—especially when it comes to decisions about workplace tools. Most companies give their corporate teams modern devices and software for communication and collaboration. However, decision makers don't have enough insight into the needs of their deskless employees. As a result, those workers don't get access to the tools they need, leaving them feeling undervalued. With poor access to communication, they also don't see the bigger picture to which their work contributes. ## Deskless Workers Are the Face of Your Company When a potential customer interacts with your company, they are most likely going to meet someone who falls into the deskless workers bucket. That could mean a retail worker, concierge, nurse, or any number of other positions. In that context, the numbers above should disturb you. If there is any group that should be the most tapped into the company mission and vision—and the least disillusioned with their jobs—surely it is the people responsible for executing on positive customer experiences. Our whitepaper on the subject offers a detailed breakdown of this situation. Its contents include: - The reasons deskless worker communication is often neglected - The harmful effects this has on business and company culture - Advice and data to help decision makers foster employee understanding and behavior change - Details on what frontline employees actually want to receive from management ## Deskless Worker Communication Is Challenging On the most fundamental level, the reason deskless workers get less company communication is that they're harder to reach. Furthermore, there isn't always a clear line between investing in deeper outreach to deskless teams and better performance. It can be hard to justify making the investment. People that sit at desks do most of their work from one location and one or two devices. It's not hard to justify providing your desk employees with a computer, and possibly a mobile device. These devices are crucial for their jobs as information workers. Deskless workers, on the other hand, face barriers to communication that vary by sector and job role. When your job requires mobility in an ever-changing environment—think construction sites with spotty connectivity, hospital floors with no time to check email, or logistics routes with no VPN access—it's not always possible for you to be reachable at any moment, especially by the old-fashioned channels that most companies rely on. The intranet problem illustrates this clearly. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use one daily. SWOOP Analytics found the average employee spends just six minutes per day in intranet tools. For deskless workers without a corporate email address or VPN, that number is effectively zero. Meanwhile, IDC estimates employees spend 2.5 hours per day searching for information—time that compounds into serious productivity loss when frontline workers can't find what they need quickly. For example, even something as simple as a store manager creating and distributing the store schedule each month can become a logistical nightmare, and a headache for everyone involved. When you rely too heavily on email and word of mouth, deskless worker communication is quite cumbersome. The [Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) covers practical approaches to this specific problem. ## Low Engagement Is Costing You If you want the best out of your deskless employees, it is crucial to enable them with better technology. Once that's done, consistent outreach and two-way communication are the key to your success. In short, create a path with tools that bring them into the fold. Then, make use of it, engage in dialogue, and act on the feedback you get. People who feel like they have a voice work harder at their jobs—this is the real key to frontline employee engagement. That has always been true, among any group of people. The cost of getting this wrong is concrete. Replacing a frontline employee costs between $4,400 and $15,000, making poor communication a direct retention and cost risk. Low employee engagement also drags on output: employees lose over 4 hours per week switching between disconnected systems, compounding the productivity cost of poor frontline tooling. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents how leading organizations are closing this gap. **This is where an Employee SuperApp comes into play.** Organizations are looking for a way to connect and enable their frontline employees the same way they do with desk-based workers. With the average person checking their phone over 300 times a day, it's clear that the best way to power deskless worker communication is by meeting your employees where they are and enabling them with a platform they can access while on the move. ## How to Improve Deskless Worker Communication: 5 Actionable Steps Decision-makers who want to act on this problem—not just diagnose it—need a practical framework. Here are five steps that move from audit to measurable improvement. **1. Audit your current communication channels.** Map every channel your frontline workers are supposed to use: email, SMS, bulletin boards, shift handoff notes, manager huddles. Then ask honestly: which ones require a corporate email address or VPN that most deskless workers don't have? Which ones assume workers are stationary? Identify the gaps before selecting a solution. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) includes a channel audit framework built for frontline-heavy organizations. **2. Define your communication priorities by role.** Not every frontline worker needs the same information at the same cadence. A nurse in [ambulatory care](/industries/ambulatory-care) needs real-time clinical updates and shift alerts. A grocery associate needs schedule changes and product knowledge. A construction worker needs safety bulletins and offline access to job-site documents. Segment your workforce and define what each group needs to receive, from whom, and how often. **3. Select a platform that works without email or VPN.** Frontline employees can be reached via push notifications, SMS, and in-app alerts for time-sensitive communications—without a corporate email address or VPN. This is a non-negotiable requirement for any employee experience platform serving a deskless workforce. Also confirm the platform supports offline access for workers in low-connectivity environments, such as construction sites, hospital basements, or logistics routes. Real-time multilingual communication (50+ languages) is increasingly important in retail, [healthcare](/industries/healthcare), and hospitality verticals where workforce diversity is high. **4. Pilot with one team and measure employee engagement.** Before a full rollout, run a 60–90 day pilot with one location or department. Use an employee engagement survey or employee engagement questionnaire at the start and end of the pilot to measure shifts in sentiment, information access, and belonging. OU Health achieved 87% workforce engagement within a few months of launching a branded frontline app. PetSmart reported a 4x industry engagement multiple after deploying a mobile employee app. These results came from deliberate pilots with clear measurement, not big-bang rollouts. **5. Act on feedback and close the loop.** Employee engagement software is only as valuable as the action it prompts. Build a cadence for reviewing feedback from frontline workers, communicating what you heard, and reporting back on what changed. Workers who see their input acted on are significantly more likely to stay engaged. Training on employee engagement—for managers, not just HR—is often the missing piece that determines whether a technology investment translates into sustained behavior change. See [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) for a framework on embedding this into daily work. ## What an Employee SuperApp Actually Includes **With an Employee SuperApp, you can:** - Bring frontline employees into the loop by giving them the tools to communicate and collaborate with their dispersed colleagues—on personal devices, without a corporate email address or VPN. - Connect frontline employees with the resources and information they need within one app, including scheduling, shift swaps, HR self-service, and training and employee engagement content. - Allow frontline employees to quickly reference necessary information while on the floor, including offline documents for low-connectivity environments, leading to additional upselling opportunities and improved customer service. - Provide a clear org chart and employee directory so that frontline workers know where to go and who to turn to for questions. - Provide frontline employees with self-serve tools that can lead to improved operational excellence and efficiency. - Integrate with complex systems to reduce the digital friction created by switching across apps while on the floor. - Create feedback mechanisms—including employee engagement surveys and questionnaires—to give frontline employees a voice and get deeper insights into how to motivate them. - Communicate in 50+ languages in real time, so multilingual frontline teams in retail, healthcare, and hospitality receive accurate information without delay. For a look at how this plays out in a regulated, communication-intensive environment, see [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology). ## MangoApps — The Employee SuperApp for Frontline Workforces MangoApps is the Employee SuperApp for organizations with a frontline workforce. With MangoApps, you're able to give 100% of your workforce all the tools they need in one employee app to increase productivity, improve retention, and boost employee engagement. MangoApps works on personal devices without requiring a corporate email address or VPN, making it accessible to the deskless workers who are hardest to reach through traditional channels. The platform supports offline access, real-time multilingual communication, push notifications, shift management, HR self-service, and training on employee engagement—all in a single branded app. MangoApps is customizable and offers a wide range of unique functionalities aimed at solving any business need. It has been recognized in [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) and [MangoApps Wins Gold in Reworked's 2026 IMPACT Awards for Excellence](/articles/mangoapps-gold-reworked-2026-impact-awards). To learn more about how MangoApps can help your organization, or how you can take advantage of all the benefits that Employee SuperApps have to offer, book a demo or schedule a call with our team today. ## Frequently Asked Questions About Deskless Worker Communication ### How do I measure the ROI of a frontline communication investment? Start with baseline metrics before any tool change: voluntary turnover rate, time-to-fill open shifts, manager hours spent on scheduling and information requests, and scores from an employee engagement survey or employee engagement questionnaire. After a 90-day pilot, compare those numbers. Replacing a frontline employee costs between $4,400 and $15,000, so even a modest improvement in retention pays back the technology investment quickly. Productivity gains from reducing the 2.5 hours per day employees spend searching for information (per IDC) add a second ROI layer. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) includes a measurement framework for frontline communication programs. ### How do I manage change when rolling out a new communication platform to frontline workers? Change management for deskless workers differs from desk-based rollouts because you cannot rely on email announcements or all-hands meetings. Effective approaches include: training managers first so they can champion the tool on the floor; using push notifications and SMS to drive initial adoption; running employee engagement training sessions in short, shift-friendly formats; and closing the feedback loop visibly so workers see that their input shaped the rollout. Per Gallup's 2026 State of the Global Workplace research—covered in [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace)—manager behavior is the single largest driver of team-level engagement, making manager enablement the highest-leverage change management investment. ### What should I look for when comparing employee communication tools for frontline workers? Evaluate any employee experience platform against these criteria: Does it work without a corporate email address or VPN? Does it support offline access for low-connectivity environments? Does it offer real-time multilingual communication for diverse workforces? Does it consolidate scheduling, HR self-service, training, and communications in one place to reduce app-switching? Does it include employee engagement software features—surveys, pulse checks, recognition—so you can measure what's working? And does it provide analytics so managers can see who is and isn't reached? The [solutions/employee-communications](/solutions/employee-communications) page outlines how these criteria map to specific platform capabilities. --- # Corporate learning from the bottom up **Author:** Christos Schrader **Published:** 2021-03-05 **Category:** learning-management Corporate learning is an area of huge potential for just about every company, but that potential often goes unrealized. Generally speaking, when companies begin to incorporate training into their employee experience, they have few options that are both effective and affordable. Most training programs wind up incorporating content produced externally by contractors, which is by […] # Corporate Learning from the Bottom Up Every organization has a knowledge distribution problem. According to IDC, employees spend 2.5 hours per day searching for information — time that compounds across every team, every shift, and every department. The knowledge they need to do their jobs often already exists inside the organization. A senior technician figured out the fix three months ago. A floor supervisor developed a workaround that cut inspection time in half. Nobody wrote it down where anyone else could find it. Bottom-up corporate learning is the operational strategy that closes this gap. Instead of purchasing external content that generalizes across industries and roles, organizations identify the internal experts who already carry the knowledge others need and give them a structured way to share it. The result is a workplace learning system built from the inside out — specific to the company's processes, current to this quarter, and credible to the people watching it because it comes from someone they recognize. This article covers what bottom-up workplace learning looks like in practice, how to implement it in five concrete steps, and how to measure whether it's producing results that matter. --- ## Why external training programs keep falling short The standard corporate training model runs like this: a learning and development team identifies a skill gap, contracts with a content provider, and deploys modules across the organization. Employees complete the modules. Boxes get checked. The problem is not the effort — it's the content. External training is designed for a generic audience. A compliance module written for "manufacturing employees" covers the regulations, but not the specific way a particular site handles line changeovers, or the nuance in a supplier agreement that affects how quality exceptions get logged. Employees sit through content produced by someone who has never seen their floor, their tools, or their customers. The miss is structural, not a vendor quality issue. No external provider can know what a company's team knows. The knowledge that drives performance lives with the people who built it — the floor manager who has processed every equipment failure for six years, the customer success representative who has handled thousands of variations of the same complaint. Peer-generated, role-specific micro-learning has become a core pillar of what researchers and practitioners now call a "learning organization" — one where institutional knowledge is continuously captured and redistributed rather than held siloed in tenured employees' heads or lost when people leave. --- ## What bottom-up workplace learning actually looks like Bottom-up learning is not asking employees to become instructional designers. It is asking them to do something they already do every day — explain how they do their job — and giving them a system to capture and share that explanation at scale. In practice, this starts with video. The smartphone in an employee's pocket is more capable than the studio equipment available to most eLearning contractors a decade ago. A team lead can record a five-minute walkthrough of a safety procedure on a phone. A customer service rep can narrate the steps through a complex returns scenario. Video learning content is now the primary format for workplace training, and the production quality required is far lower than most managers assume — employees respond to authenticity from a known colleague, not production value from a stranger. The second component is searchability. Recorded knowledge is only useful if employees can find it when they need it, on the device they have in hand. An LMS learning system integrated with the platforms employees already use — rather than deployed as a standalone tool — means employees searching for how to do something encounter the relevant training module alongside policies, team announcements, and department discussion threads. According to IDC, employees spend 2.5 hours per day searching for information; a unified search surface that returns training content alongside operational knowledge reduces that friction directly. The third component is structure: an organized tagging and categorization system so that content about, say, forklift certification, is discoverable under "safety," "warehouse operations," and "new hire onboarding" — not buried in an upload folder only the person who created it knows about. --- ## Getting started: five steps to launch peer-generated learning The most common failure mode for bottom-up learning programs is treating launch as a technology problem rather than a process problem. The platform is necessary, but it is not sufficient. These five steps move from platform to program. **Step 1: Identify the first five subject matter experts.** Start narrow. Identify one or two domains where knowledge concentration creates operational risk — where if two or three specific people left, the organization would struggle. These are the first recording sessions. Look for employees whose colleagues frequently ask them the same questions; that pattern signals captured expertise. **Step 2: Define a recording protocol.** Employees who have never produced training content need a structure to follow. A simple brief — five to eight minutes maximum, state the problem or task at the start, show the steps, close with the most common mistake to avoid — removes the creative burden and produces consistent, usable content. Pair new contributors with a colleague who can watch the first draft and offer one round of feedback. **Step 3: Set up the tagging and categorization system before the first upload.** Content taxonomy is painful to retrofit. Agree on a category structure that mirrors how employees search — by role, department, process type, and compliance requirement — before the library has any entries. The [knowledge management](/solutions/knowledge-management) architecture of the platform should match how work is actually organized, not how the LMS vendor organized their demo data. **Step 4: Pilot with a cohort, not a company-wide announcement.** Rather than launching to the full organization, assign a group of 20 to 30 employees across two or three teams to use the library for a defined period. Measure what they search for and don't find. These gaps become the second recording priority — and the pilot group becomes internal advocates who can describe the value from direct experience. **Step 5: Build a contribution habit, not a campaign.** Bottom-up learning degrades back into a static library if contribution becomes a one-time initiative. Build module creation into existing workflows — quarterly team retrospectives, post-incident reviews, onboarding ramp-up documentation. The [learning and development strategy](/articles/learning-and-development-strategy-embedded-in-daily-work) that sustains itself is the one that captures knowledge as a byproduct of normal work, not as a separate request employees need to schedule time for. --- ## Reaching the frontline workers that traditional training misses Bottom-up workplace learning has a structural advantage for organizations with deskless or distributed workforces — and a structural failure mode if the platform deploying it requires a desktop to access. According to Emergence Capital, 80% of the global workforce is deskless, working in manufacturing, healthcare, retail, logistics, and field services where a desktop computer is intermittent or absent. Traditional LMS platforms are designed for desk workers: they require a corporate email address, a company-managed device, or VPN access to a protected network. Employees who work a shift and clock out without ever opening a laptop are functionally excluded. A [learning management system](/solutions/learning-management) built for frontline access changes the deployment equation. Employees log in on a personal device, access the training content assigned to their role, complete the module on a break, and return to work. The certification is recorded. The manager can see completion status before the shift starts. No paper sign-in sheet, no classroom scheduling, no external training coordinator required. This access model also matters for onboarding speed. When new hires can complete role-specific training from a mobile device before their first full shift — not waiting for a classroom session to be scheduled — organizations reduce time-to-competency without increasing training headcount. Employees who start with access to organized, searchable peer-generated content ramp faster than those waiting for a structured classroom program. --- ## How to measure whether it's working The measurement failure in corporate learning programs is almost always a leading indicator problem: organizations measure completion rates rather than outcomes. Ninety percent completion on a training module is not evidence that the module produced any behavioral change or operational improvement. Bottom-up learning programs should be measured against operational outcomes identified before deployment. **Time-to-competency for new hires.** If subject matter experts in a warehouse recorded the ten most common first-month mistakes, measure whether new hire error rates change in the first 90 days after the library is deployed. A reduction in early errors is direct evidence that the content transferred knowledge effectively. **Knowledge search resolution rate.** If the platform surfaces training content in search, measure how often employees find what they were looking for without opening a support ticket, calling a supervisor, or asking a colleague to step away from their work. A rising resolution rate means the library is answering questions before they become interruptions. **Content contribution rate.** Track how many employees have contributed at least one module after the first six months. A library that five people built is not a bottom-up learning program — it is five people's opinions. Genuine peer learning requires broad contribution across roles, departments, and tenure levels. **Reduction in repeated questions.** The pattern that identifies a knowledge gap in the first place — multiple employees asking the same question of the same senior person — should decrease as the library matures. If the same questions keep surfacing, the relevant module either doesn't exist or isn't discoverable enough to reach the employees asking. This is an information architecture problem, not a content problem. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) notes that learning and development has shifted from a compliance-driven function to a strategic retention lever — organizations that give employees a visible path to skill development see measurably lower turnover in competitive labor markets. The measurement frame shifts accordingly: the question is not whether employees completed training, but whether they can do something after training that they couldn't before. --- ## The knowledge your organization already holds Every employee who has mastered a role-specific task, resolved a recurring operational problem, or built a skill that colleagues consistently ask about is a potential contributor to the organization's knowledge base. The infrastructure to capture and distribute that knowledge — an LMS learning system integrated with the platforms employees already use, searchable and mobile-accessible — is the mechanism that turns implicit expertise into organizational capability. The organizations that close the knowledge distribution gap are not the ones with the largest training budgets. They are the ones that systematically extract knowledge from the people who already carry it and make that knowledge available to everyone who needs it, regardless of where they work or what device they have. That is what a bottom-up workplace learning program produces — and why it outperforms externally sourced content in every deployment where employees actually use it. --- # Microsoft Viva Validates Our Vision Of A Unified Employee Experience **Author:** Christos Schrader **Published:** 2021-02-10 **Category:** comparisons Microsoft has recently announced the launch of Microsoft Viva, and declared it a pioneer of a new enterprise software category called EXP (Employee Experience Platform). This announcement was exciting and heartening to us here at MangoApps. It gave instant legitimacy to an idea that we have relentlessly pursued for almost a decade. Coming from an […] # Microsoft Viva Validates the Case for a Unified Employee Experience Platform When Microsoft launched Microsoft Viva and declared it the founding product of a new enterprise software category — the Employee Experience Platform (EXP) — it confirmed what a growing number of HR and IT leaders had already concluded: fragmented tools are failing workers. For organizations evaluating their options, the more useful question is not whether a unified employee experience matters, but how to build one that employees will actually use. This article explains what the EXP category means, why most intranets and engagement tools fall short of it, and what a practical path to implementation looks like. --- ## Why Unified Employee Experience Has Become Urgent The problem is measurable. Employees spend an average of 2.5 hours per day searching for information they need to do their jobs (per IDC). That is not a minor friction point — it is a structural drain on productivity that compounds across every team and every shift. The intranet was supposed to solve this. According to Social Edge Consulting, 91% of organizations operate an intranet. Yet nearly a third of employees never log in to it, and those who do spend an average of just six minutes per day inside it (per SWOOP Analytics). Only 13% of employees use their intranet daily (per Social Edge Consulting). The gap between deployment and adoption is not a training problem — it is a design problem. Microsoft's own research into knowledge sharing found that executives were significantly more satisfied with their knowledge management tools than the information workers who depend on those tools every day. Workers reported spending 11–14% of every workday either searching for or recreating information — up from 4.3% in 2016. That trajectory is moving in the wrong direction. The EXP category exists to reverse it. --- ## What Microsoft Viva's Launch Actually Signals Microsoft Viva entering the EXP space is meaningful for two reasons. First, it confirms that the category is real and that enterprise buyers are ready to invest in it. Second, it highlights how much ground still needs to be covered. Viva launched as a set of modules layered on top of Microsoft 365 and Teams. For organizations already standardized on that stack, it offers a logical starting point. But it also inherits the limitations of that stack: it is primarily designed for desk-based knowledge workers, it requires existing Microsoft licensing, and its adoption among frontline and deskless employees — who make up 80% of the global workforce (per Emergence Capital) — remains a significant open question. The EXP category is not just about knowledge workers. Any platform that leaves out the majority of the workforce is solving only part of the problem. --- ## Why Traditional Intranets Fall Short of the EXP Standard Traditional intranets take months to deploy, place heavy demands on IT teams, and tend to produce static, ungoverned content that becomes stale within weeks of launch. The result is the adoption gap described above: a platform that exists but is not used. Modern EXPs are designed to eliminate that IT dependency. Frontline employees can access the platform on personal devices without a corporate email address, a VPN, or a desk — no IT provisioning required. This matters because the employees most likely to be disengaged are often the ones least likely to have a company-issued device or a dedicated workstation. Cost is also a factor that rarely appears in initial vendor conversations. SharePoint's first-year total cost for a 1,000-user enterprise ranges from $130,000 to $426,000 when implementation, customization, and governance are included — not just licensing (per Awesome Technologies Inc.'s 2025 cost model). Organizations evaluating employee engagement software should account for the full cost of deployment, not just the per-seat price. For a broader view of where the market is heading, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an independent assessment of how leading platforms compare on adoption, governance, and frontline access. --- ## How to Build a Unified Employee Experience: Four Implementation Steps Microsoft Viva's launch is a useful prompt for any organization to audit its own approach. Here is a practical framework for moving from fragmented tools to a functioning EXP. ### 1. Audit Your Current Tool Stack List every platform employees are expected to use for communication, task management, learning, HR transactions, and information retrieval. For each tool, identify who actually uses it, how often, and what problem it was originally purchased to solve. Most organizations discover significant overlap, redundancy, and gaps — particularly for frontline workers who may have no access to desk-based tools at all. ### 2. Define Worker Personas by Role and Access A corporate communications manager and a warehouse associate have fundamentally different information needs, device access, and daily workflows. An EXP that treats all employees identically will serve neither well. Define at least two or three distinct personas — typically desk-based knowledge workers, frontline or deskless workers, and managers — and map the specific pain points each group experiences today. ### 3. Prioritize Pain Points by Business Impact Not every friction point carries the same cost. The average cost to replace a single frontline employee ranges from $4,400 to $15,000, which means that employee engagement and retention are directly connected to the bottom line. Prioritize the pain points most likely to drive disengagement or turnover: inability to find information, lack of recognition, disconnection from company news, and absence of a feedback channel. An [employee engagement survey](/solutions/employee-data) or structured employee engagement questionnaires can surface these priorities quickly. ### 4. Measure Adoption, Not Just Deployment A platform that is deployed but not used has not solved the problem. Set adoption targets before launch — for example, a CVS deployment using a unified platform achieved 90% frontline adoption within the first six months. Track login frequency, content interaction, and task completion rates. Use that data to iterate on the experience rather than waiting for annual engagement surveys to surface problems. For a deeper look at how learning fits into this framework, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers how to embed skill-building into daily workflows rather than treating it as a separate initiative. --- ## What a Modern EXP Should Include Based on the implementation framework above, a functioning EXP needs to address several capabilities that traditional intranets and point solutions do not cover: - **A uniting intranet layer** that serves as the single entry point for all employees, regardless of role or device - **AI-native personalization** that surfaces relevant content, tasks, and updates for each employee without requiring manual curation — MangoApps, for example, connects to OpenAI, Google Gemini, Anthropic, and Azure OpenAI to deliver AI-curated feeds from company data - **Mobile-first access** for frontline workers who do not have corporate email addresses or company-issued devices - **Enterprise security** including SAML 2.0, OAuth 2.0, SSO, and Active Directory integration — capabilities that matter to IT and compliance teams even when they are invisible to end users - **Integrated employee engagement tools** including surveys, recognition, and feedback channels that are embedded in the daily workflow rather than siloed in a separate HR system MangoApps has been building toward this architecture for nearly a decade, working directly with customers to refine what a practical, affordable EXP looks like at scale. The [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides third-party context on where the platform stands relative to the broader market. --- ## How Does MangoApps Compare to Microsoft Viva? This is the question most readers will have after reviewing both options. The honest answer is that the right choice depends on your existing infrastructure and your workforce composition. Microsoft Viva is a strong fit for organizations already standardized on Microsoft 365 that primarily need to improve the experience of desk-based knowledge workers. It benefits from deep integration with Teams, SharePoint, and the broader Microsoft ecosystem. MangoApps is designed for organizations with a mixed workforce — including frontline, deskless, and hourly workers — who need a single platform that works across device types without requiring Microsoft licensing or IT-heavy deployment. Its modular structure means organizations can start with the components they need now and expand as requirements grow. Savings of up to 80% compared to assembling equivalent functionality from multiple point solutions have been cited by customers, and the platform's [employee app](/solutions/employee-app) is built to serve workers who have never had a company-issued device. For organizations in regulated industries or with complex workforce structures, [Managing a Unionized Workforce Is Different. Your Software Should Be Too](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) covers how platform design affects compliance and worker relations in those environments. --- ## What ROI Should You Expect from an EXP Investment? ROI from an EXP investment comes from three sources: 1. **Time recovered from information search** — if employees currently spend 2.5 hours per day searching for information (per IDC) and an EXP reduces that by even 30 minutes, the productivity gain across a 500-person workforce is material 2. **Reduced turnover costs** — given that replacing a single frontline employee costs between $4,400 and $15,000, measurable improvements in employee engagement translate directly into avoided recruiting and onboarding costs 3. **Consolidation savings** — replacing three to five point solutions with a single platform reduces licensing, integration, and IT maintenance costs The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how HR leaders are quantifying these returns in their business cases for EXP investment. --- ## The Takeaway Microsoft Viva's entry into the EXP category is a signal, not a solution. It confirms that the market has recognized what the data has shown for years: fragmented tools, underused intranets, and disconnected employee engagement programs are costing organizations in productivity, retention, and operational efficiency. The organizations that will benefit most from this moment are not the ones that immediately adopt whichever platform has the largest marketing budget. They are the ones that audit their current state honestly, define what their specific workforce actually needs, and choose a platform — or build toward one — that employees will use every day, not just in the first week after launch. If your organization is ready to evaluate what a unified employee experience would look like in practice, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) is a useful starting point for benchmarking your current approach against where the market is heading. --- # MangoApps Ranked #1 Digital Workspace Platform **Author:** Christos Schrader **Published:** 2021-02-05 **Category:** integrated-digital-workplace MangoApps is thrilled to announce that we have landed the #1 spot overall in SoftwareReviews’ 2021 Digital Workspace Data Quadrant Awards, beating out 13 competitors including Microsoft Teams and Workplace by Facebook. Based on user input and reviews, the report analyzes over 40 parameters to give a detailed breakdown of the market. It shows how […] # MangoApps Ranked #1 Digital Workspace Platform by SoftwareReviews MangoApps is an all-in-one digital workplace that combines intranet, collaboration, training, and content management into a single environment — accessible to every employee, including frontline and deskless workers who may not have a corporate email address. In 2021, SoftwareReviews' Digital Workspace Data Quadrant Awards ranked MangoApps #1 overall among 14 platforms, including Microsoft Teams and Workplace by Facebook. This article explains what that ranking means, what the platform actually does, and whether it might fit your organization's needs. ## What Is MangoApps? MangoApps brings together the capabilities that most organizations currently manage across separate tools: an [intranet and company portal](/key-features/company-portal), team workspaces, document management, an employee directory, training delivery, and internal communications — all in one place. Employees access it through a browser, a desktop app, or a mobile device, with no corporate email required for frontline access. According to Emergence Capital, 80% of the global workforce is deskless, yet most digital workplace tools are designed around desk-based, email-centric workflows. MangoApps is built to reach both populations from a single platform, with offline access and mobile-first design for workers on the floor, in the field, or on the road. Organizations that have deployed the platform have seen measurable results. OU Health achieved 87% workforce engagement within a few months of launching a branded employee app on MangoApps. TeamHealth consolidated more than 200 separate systems into a single mobile dashboard using the platform. ## The SoftwareReviews #1 Ranking: What It Measured SoftwareReviews is a division of Info-Tech Research Group. Their Data Quadrant evaluates software across more than 40 parameters drawn from verified user reviews, covering product functionality, vendor performance, and what they call the "Emotional Footprint" — a measure of the relationship quality between a vendor and its customers. MangoApps earned the top composite score across all 14 vendors evaluated. The platform also ranked first in four specific categories: - **Business Value Created** - **Breadth of Features** - **Ease of IT Administration** - **Document Management** - **Employee Directory** "The composite score captures how a vendor has performed across key indicators such as product functionality, vendor performance, and the relationship with their customers," said David Piazza, President of SoftwareReviews. "A strong showing with this metric demonstrates a product that not only delivers value for their customers, but is also a partner that people want to work with." "Businesses all over the world are being confronted with a major shift in how and where they work," added Ken Weston, Senior Research Analyst at Info-Tech Research Group. "The challenge is that productivity means something different to everyone." ## Why the Intranet and Digital Workplace Market Needs a Better Answer The market context behind this ranking matters. According to Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in to it, and only 13% use it daily. SWOOP Analytics found that the average employee spends just six minutes per day using intranet tools. Meanwhile, IDC estimates that employees spend 2.5 hours per day searching for information they cannot easily find. These numbers point to a structural problem: most intranet deployments are not designed around how employees actually work. A platform that scores well on ease of IT administration and breadth of features matters only if employees actually use it. Cost is also a factor for organizations evaluating alternatives. Enterprise SharePoint deployments for 1,000 users can cost between $130,000 and $426,000 in the first year alone, according to a 2025 cost model by Awesome Technologies Inc. — making consolidated, all-in-one alternatives materially cheaper at scale. Retention is another dimension of the ROI calculation. Replacing a single frontline employee costs between $4,400 and $15,000 on average. Platforms that improve [employee engagement](/solutions/employee-engagement) reduce that turnover cost directly. ## Key Capabilities Worth Evaluating For readers who landed here from a product search rather than an award announcement, here is a functional summary of what MangoApps includes: - **Intranet and company portal**: Centralized news, announcements, policies, and resources accessible to all employees, including those without a desk or corporate email. The [modern intranet](/solutions/modern-intranet) layer supports branded experiences and targeted content by role, department, or location. - **Department sites and team workspaces**: Dedicated spaces for teams to collaborate, share files, and track projects without switching to a separate tool. [Department sites](/key-features/department-sites) and [workspaces](/key-features/workspaces) are configurable without IT involvement. - **Training and employee engagement**: Embedded learning tools allow organizations to deliver employee engagement training, onboarding courses, and compliance content inside the same environment employees use for daily communication — removing the friction of a separate LMS. - **Content and document management**: Structured document libraries with version control, permissions, and search, ranked #1 in the SoftwareReviews evaluation. - **Employee directory**: A searchable, profile-rich directory that ranked #1 in the SoftwareReviews evaluation and supports org-chart navigation and expertise discovery. - **Webpage builder**: A no-code [webpage builder](/key-features/webpage-builder) for creating internal pages, microsites, and resource hubs without developer support. ## Security and Administration For IT and security teams evaluating employee engagement software, MangoApps supports SAML 2.0, OAuth 2.0, and single sign-on (SSO) integration, which addresses the data governance and access control requirements common in regulated industries. The platform's top ranking in Ease of IT Administration in the SoftwareReviews report reflects this design priority: security controls should not require ongoing IT overhead to maintain. ## AI-Assisted Personalization The 2021 SoftwareReviews ranking predates the current generation of AI-assisted workplace tools. MangoApps has since added an AI assistant and content personalization capabilities that surface relevant information to each employee based on their role, location, and behavior — reducing the information-search burden that IDC quantifies at 2.5 hours per day. ## Frequently Asked Questions ### How does MangoApps compare to Microsoft Teams or SharePoint? Microsoft Teams is primarily a communication and meeting tool; SharePoint is a document management and intranet platform. MangoApps covers both functions plus training delivery, employee engagement surveys and questionnaires, and frontline mobile access in a single product. Enterprise SharePoint deployments for 1,000 users can cost between $130,000 and $426,000 in the first year alone (per a 2025 cost model by Awesome Technologies Inc.), while MangoApps consolidates those functions at a lower total cost. The SoftwareReviews evaluation placed MangoApps above Microsoft Teams on composite score, business value, and breadth of features. ### Is MangoApps suitable for frontline or deskless workers? Yes. The platform is designed for organizations where a significant share of the workforce does not sit at a desk or use a corporate email address — which, per Emergence Capital, describes 80% of the global workforce. Employees can access MangoApps via a mobile app without a corporate email, and the platform supports offline access for workers in low-connectivity environments. TeamHealth's consolidation of 200+ systems into a single mobile dashboard is one documented example of this use case. ### What does the research say about intranet adoption rates? According to Social Edge Consulting, 91% of organizations run an intranet, but only 13% of employees use it daily and nearly a third never log in at all. The gap between deployment and adoption is the central problem that a well-designed digital workplace platform addresses. The SoftwareReviews ranking specifically measures whether users find value in the product — not just whether IT has deployed it — which is why the Emotional Footprint and Business Value Created metrics are meaningful signals. ## What to Do Next If you are evaluating digital workplace or employee engagement software, the SoftwareReviews Data Quadrant report is a useful independent reference — it is based on verified user reviews rather than vendor-supplied data. For a broader view of where the intranet market is heading, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) covers the competitive landscape in detail, and the [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides additional third-party context on the platform's positioning. If you want to understand how internal communications strategy connects to engagement outcomes, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the current research and practical approaches. The clearest next step is to see the platform in a live environment with your own use cases. Contact MangoApps to schedule a demo and bring specific questions about your workforce — particularly if you have a significant frontline or deskless population, or if you are consolidating multiple tools into a single employee engagement platform. --- # Announcing MangoApps 15 **Author:** Christos Schrader **Published:** 2021-01-18 **Category:** modules-features We are thrilled to announce the release of MangoApps version 15! This update is the culmination of a boatload of work from our product team. It’s a huge leap forward in our feature offering. MangoApps now includes a full-featured LMS integrated directly into the platform, as well as workflow automation, and new features centered around […] We are thrilled to announce the release of MangoApps version 15! This update is the culmination of a boatload of work from our product team. It’s a huge leap forward in our feature offering. MangoApps now includes a full-featured LMS integrated directly into the platform, as well as workflow automation, and new features centered around moderation and data loss prevention. We made a lot of quality of life upgrades and changes, too. All of it stems from user feedback and our mindset of continuous improvement. See the full release notes for a detailed changelog, or read on for a high-level breakdown. New Learn Module Our new learn module is exactly what it sounds like—a dedicated space for all of your learning needs. This module will allow you to create media-rich, engaging courses for employees to take, from onboarding through continuous certification and upskilling. It also has capabilities for customer education. This is a feature that our customers have been requesting for a long time. Digital learning is a crucial piece of a modern organization’s success. Now that it sits within MangoApps, that’s one less expensive platform you have to teach your employees how to use. With the Learn module, your employees can see which courses have been assigned to them, and receive tailored recommendations. There are certificates, learning paths, and course templates, plus SCORM and xAPI importing. With MangoApps 15’s new learning capabilites, you have everything you need to build a powerful eLearning program. Workflows Let You Automate Form & Tracker Actions Forms and trackers are a key piece of MangoApps’ ability to help your team work more efficiently and communicate better. However, there can be a lot of rote work involved in keeping approvals and sales flows running smoothly. Our new workflow functionality enables you to outsource a lot of that work to rule-based automation. The feature ships with a few basic templates, and a whole lot of possibilities. Our new workflow functionality enables you to outsource a lot of that work to rule-based automation. The feature ships with a few basic templates, and a whole lot of possibilities. This feature will give you unprecedented control over tasks that used to be manual. Going forward, we can’t wait to see what our customers do with it. We think workflows have massive potential as we continue to refine and expand their capabilities in the next MangoApps 15 releases. New Widgets Add Complementary Functions We have launched a pack of widgets for G Suite, meaning that G Suite users can now add Gmail, Google Drive, and Google Calendar widgets to their MangoApps dashboard. This makes it much easier for your employees to access all of their tools from the unified MangoApps dashboard. We have also added new widgets to our Microsoft 365 widget pack for OneDrive and Calendar. New Moderation Capabilities In MangoApps 15 Content moderation can be an important consideration for workplace forums like our Employee Social Network. Our new moderation features give customers more flexibility and control. Users can now flag content they feel is inappropriate, which designated admins can review. At the domain level, admin approval can be required for all content, anything containing certain keywords, or only content that has been flagged. Also, bulk moderator actions are baked in, and high-level users can be made exempt from approvals. Exemptions can even be limited to relevant areas of the platform. The tool is flexible overall, and allows any organization to choose a moderation policy that balances their needs. New DLP Functionality Data loss prevention is an important consideration for any large company looking at service providers like MangoApps. To that end, we’ve introduced a set of features to identify and report common patterns of sensitive information. MangoApps 15 comes with pre-shipped patterns for finance and PII data (examples in the US include social security or credit card numbers), and you can add your own patterns in minutes with no coding or IT support. You can handle these instances in a number of ways. Admins can be notified case-by-case or in a daily digest email, and can then message users about removal. It’s also possible to set up notifications for the user, which will automatically inform them. This can help teach employees organically about any policies they have violated. It’s also easy to get a domain-wide view of these policy violations, and the system is audit-ready. Other Important Enterprise Features MangoApps is committed to making our product the best possible solution at the enterprise level. To that end, it’s now possible to automate team membership as new hires are made and teams change. This helps large organizations handle the sometimes unwieldy task of ensuring that everyone has access to the right content. Furthermore, we’ve added SCIM support, giving our users yet another way to bulk import SSO data. Other Additions To MangoApps We have added support for alternate email notifications. Many of our customers don’t give a company email address to all of their workers. This makes it hard to keep everyone in the loop. With alternate email notifications, users can sign up to receive notifications at their personal email. In the messaging tab, we have added the ability to turn off replies for mass messages. Furthermore, you can send automated private messages to users, such as when they receive certificates or transcript updates within the Learn module. We have also made a slew of updates to our browser client and mobile apps that improve load time and quality of life. In the mobile apps, you can now access modules for moderation features and LMS content. --- # Guide To Creating A Strong eLearning Program **Author:** Rahul Suresh **Published:** 2021-01-13 **Category:** learning-management The role of eLearning in the modern workplace has gone beyond dry compliance trainings from HR. According to Forbes, nearly 72% of organizations believe that their eLearning program provides them with a competitive edge. Today, businesses turn to digital learning mechanisms to upskill employees. This enables them to intuitively grasp information about new market trends […] ## Guide To Creating A Strong eLearning Program The role of eLearning in the modern workplace has gone beyond dry compliance trainings from HR. According to Forbes, nearly 72% of organizations believe that their eLearning program provides them with a competitive edge. Today, businesses turn to digital learning mechanisms to upskill employees. This enables them to intuitively grasp information about new market trends and deploy them to work with customers. Some even work with business schools and other outside subject matter experts to ensure the content is top quality. Your company may not have a clear strategy to implement eLearning programs that will bear fruit in the long term. Below are 5 concrete ways to build a strong eLearning strategy—covering needs assessment, LMS selection, simplicity, employee engagement training, and measurement—so you can stop re-searching and start executing. --- ### 5 Ways To Build A Strong eLearning Program #### **Identify Needs** Your eLearning Program Can Address Before launching an enterprise-wide eLearning initiative, you need to identify both business needs and employee desires. The best eLearning programs help employees build both the skills they want to improve and those that management values. You'll probably find some overlap between the two. Identifying market needs should be easy, as leadership is likely aware of the skill gaps between their team and their business goals. To identify employee needs, you can create an employee engagement survey and/or just ask around. Employee engagement questionnaires are particularly useful here because they surface learning preferences alongside motivation and satisfaction data in a single instrument. Once you have spoken to leadership and conducted an employee survey, you'll have everything you need to build a balanced curriculum. For a broader view of how learning fits into workforce strategy, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading organizations are aligning skill development with business outcomes this year. --- #### **Do Your Homework And Find The Right LMS** Finding a good lms learning system is crucial to implementing a successful eLearning program. Employees already navigate 6–8 disconnected tools daily, which fragments attention and erodes learning retention—a unified platform directly addresses that fragmentation. When looking for an LMS, there are several factors to consider: - **Is it mobile-friendly?** Per Emergence Capital, 80% of the global workforce is deskless. For these frontline employees, mobile access is not a checkbox—it is the primary channel. Frontline workers should be able to access training, shifts, and HR self-service from a single mobile app without requiring a company email address or VPN connection. - **How easy is it to upload course content?** If you already have content, you want to be sure you can import it easily. If you're going to be building a program, you'll want to make sure the course creator is easy to use. It should be able to handle all the media types you'll want to include, like text, images, video, and quizzes. - **Are there certificates and can you build a curriculum?** The easier it is to define who should take which courses, and track who has already done so, the better. Look for [skills management](/key-features/skills-management) features that map certifications directly to job roles. - **What's the user experience like?** The courses themselves should be visually appealing and easy to navigate. Also, the navigation should make it easy to find relevant courses, track your progress, and see some information about each course before you take it. - **How is their customer service?** You will need to work with them at some point. Making sure that the LMS has a strong customer service team up front will save you some headache. - **Does it integrate with your HRIS and payroll systems?** Integrating an LMS with HRIS and payroll systems can automate user provisioning, sync roles and permissions, and digitize onboarding workflows—reducing manual admin overhead significantly. With a good, modern platform, employees will be able to manage their growth trajectory within the organization. Your LMS should keep a virtual track record of their certifications, learning goals and objectives. Furthermore, AI-driven personalized learning recommendations—not just generic suggestions—should surface tailored course paths based on each employee's role, skill gaps, and career goals. This is what separates a modern learning experience platform from a basic course repository. --- #### **Promote Simplicity In Your eLearning Program** Your employees are (hopefully) busy, and it can be hard to make time for learning. Hence it is crucial that you make this as simple as possible. Your LMS should be accessible from mobile and easy to use, and your courses should be as short as possible. We recommend courses that are organized into bite-sized chunks and make use of multiple forms of media. Video-based and virtual learning formats deserve explicit attention here. Short-form video lessons—two to five minutes each—consistently outperform long-form text modules for knowledge retention, and they travel well across devices. When all modalities (video, quizzes, documents, live sessions) live in one unified platform rather than scattered across separate tools, employees spend less time hunting for content and more time learning. Per IDC, employees already spend 2.5 hours per day searching for information; a consolidated learning environment directly reclaims that time. Clear, engaging course material in combination with a user-friendly LMS and a curriculum that balances business needs with employee desires—that's all it takes. If you do everything we've listed so far, your employees will engage with your eLearning program and get value from it. For a practical example of how a large organization unified its workforce learning and communication, see [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study). --- #### **Enable Open Communication** With Employees Many companies fall into an unfortunate pattern. Leadership mandates training they feel is important, with no input from the rest of the organization. Then, they create dry materials that make no considerations for the end user's experience. As a result, employees roll their eyes and do the bare minimum to complete the courses. Nobody really learns anything. Successful employee engagement courses do not do this. Instead, they build courses with the employees in mind. Some of the content is based on employee engagement surveys, and everything is short, engaging and well-organized. Even better, it's clear what each course contains, and why it's important. Furthermore, content is segregated so that employees are only assigned courses that are actually relevant to them. The above can only happen if open communication is encouraged and acted upon. Employees need a mechanism to leave feedback on course material, and should be included in the planning. It's important that they feel their needs are being met. Connecting your learning program to a broader [employee engagement](/solutions/employee-engagement) strategy—rather than treating it as a standalone initiative—is what sustains participation over time. For a deeper look at why learning programs stall and how to fix the structural causes, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) is worth reading before you finalize your curriculum plan. --- #### **Use Quizzes** To Reinforce Learning Good eLearning courses are peppered with short quizzes. This keeps the user engaged by forcing periodic interaction. Also, it gives you an easy way to judge whether or not the material has been absorbed. It's much easier to go back and refine your courses when you have access to quiz data. If a particular quiz consistently garners lower scores than the others, that portion of the course likely could be improved. Furthermore, it's a lot harder for employees to mindlessly click through the courses if they know there's a quiz. --- ### MangoApps — Bringing It All Together Effective eLearning is the way forward for corporate training, and most companies have significant room for improvement. The five steps above—needs identification, LMS selection, simplicity, open communication, and quiz-based reinforcement—give you a complete implementation framework. Organizations that follow this sequence typically see measurable gains: new hire onboarding speed can improve by 50% when training is delivered through mobile-accessible, digitized workflows rather than in-person or desktop-only sessions, and large enterprise rollouts have achieved 90% frontline adoption within the first six months. The common thread across all five steps is integration. When your LMS, communication tools, and HR systems operate as a unified platform rather than separate point solutions, employees stop toggling between 6–8 disconnected tools and start spending that time actually learning. MangoApps [learning management solutions](/solutions/learning-management) bring course delivery, skills tracking, AI-driven recommendations, and frontline mobile access together in one place—so you're not stitching together a standalone LMS with separate communication and HR tools. The [training connect](/key-features/training-connect) feature specifically helps administrators assign, track, and report on employee engagement training at scale. If you would like to learn more about MangoApps LMS, contact us or schedule a personalized demo today. --- ### How Do You Measure eLearning ROI? Building a program is only half the work—knowing whether it's delivering value is what justifies continued investment. The most reliable eLearning ROI metrics fall into three categories: - **Completion and engagement rates:** What percentage of assigned employees finish each course? Low completion on a mandatory module signals a content or access problem, not a motivation problem. - **Knowledge retention scores:** Compare pre- and post-quiz scores over time. If scores plateau or decline after 30 days, your content cadence or reinforcement strategy needs adjustment. - **Business outcome correlation:** Track whether skill gaps identified in your initial needs assessment close after training. Tie this to performance review data where possible—[performance management](/solutions/performance-management) tools that share data with your LMS make this correlation straightforward. - **Time-to-productivity for new hires:** If onboarding is part of your eLearning program, measure how quickly new employees reach full productivity compared to a pre-program baseline. Without these measurements, eLearning budgets are difficult to defend and impossible to optimize. --- ### How Do You Handle Resistance to eLearning Rollouts? Change management is the most commonly underestimated part of any eLearning implementation. Employees who are skeptical of new training systems usually have one of three concerns: the content isn't relevant to their role, the platform is harder to use than their current tools, or they don't see how completing courses benefits them personally. Address each concern directly before launch: - **Relevance:** Use the needs-assessment step to ensure every employee cohort receives only courses mapped to their actual job responsibilities. Irrelevant mandatory training is the fastest way to destroy engagement. - **Usability:** Pilot the platform with a small cross-functional group before a full rollout. Their feedback will surface navigation issues that administrators miss because they're too close to the system. - **Personal benefit:** Make career pathing visible. When employees can see that completing a certification unlocks a new role or pay band—surfaced through skills management features—completion rates rise without additional mandates. For organizations managing complex workforce structures, [Managing a Unionized Workforce Is Different. Your Software Should Be Too](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) covers additional change management considerations that apply equally well to eLearning rollouts in regulated or contract-governed environments. --- ### What Should You Do After the First 90 Days? The first 90 days of an eLearning program are about adoption. Days 91 onward are about optimization. Once your baseline data is in, run a structured review: 1. **Audit completion rates by department and role.** Departments with low completion often have a manager buy-in problem, not an employee motivation problem. Address it at the manager level. 2. **Retire or update low-scoring content.** Quiz data will tell you which modules are failing to transfer knowledge. Rewrite or replace them before the next enrollment cycle. 3. **Expand the content library based on new survey data.** Re-run your employee engagement questionnaire every six months. Workforce skill needs shift faster than annual curriculum reviews can capture. 4. **Evaluate platform fit.** If your LMS required significant workarounds in the first 90 days, that friction compounds over time. Assess whether the platform's limitations are structural or configurable. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides additional benchmarks for how organizations are structuring continuous learning programs beyond the initial rollout phase. --- # 5 Ways Outdated Tools Hurt Large Companies **Author:** Rahul Suresh **Published:** 2020-12-21 **Category:** industry-insights According to market research, the digital transformation market is expected to grow to $3.3 trillion by 2025. Every enterprise will likely experience a push to adopt more digital business tools in that time, and replace the outdated tools that are in place today. When multiple departments deploy different tools without coordination, there is a high […] ## 5 Ways Outdated Tools Hurt Large Companies According to market research, the digital transformation market is expected to grow to $3.3 trillion by 2025. Every enterprise will likely experience a push to adopt more digital business tools in that time, and replace the outdated tools that are in place today. The five ways those outdated tools hurt large companies are: inefficient communication, poor collaboration, security threats, limited mobile access, and dissatisfied onboarding — and each carries a measurable cost that goes well beyond inconvenience. When multiple departments deploy different tools without coordination, there is a high chance of the organization facing tool sprawl. Tool sprawl is when company information is spread across too many tools, some of which have the same basic features. This results in confusion and lost productivity — employees lose over four hours per week switching between disconnected systems due to tool sprawl alone — and can be a huge expense for collaborative operations. The IT department can struggle to manage all of these tools. In fact, IT teams manage three to four times more systems than necessary due to tool sprawl. This means that departments will find themselves using outdated systems for their daily needs, so everyone loses out on the advanced capabilities that a more modern toolset would offer. Legacy systems and tool sprawl bring down the success quotient of the entire organization. Outdated systems are hurting big companies, and this article will explore some of their effects. ### 5 Ways Outdated Tools Hurt Large Companies #### #1: **Inefficient Communication** When multiple departments use legacy platforms for their own internal management, there is no unified communication strategy. For large companies with a distributed workforce, this means important announcements may have to be repeated across multiple communication channels. In many cases, it can mean that these updates simply don't make it to certain sectors of the workforce. The scale of this problem is significant. Per IDC, employees spend 2.5 hours per day searching for information — time that a unified intranet and employee communications platform could reclaim. Yet per Social Edge Consulting, while 91% of organizations operate an intranet, nearly a third of employees never log in to it, and only 13% use one daily. That gap between deployment and adoption is itself a symptom of fragmented, outdated tooling. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) explores how leading organizations are closing that gap. For these reasons and more, lacking a unified communication strategy can hamper growth and contribute to corporate bloat and inefficiency. #### #2: **Poor Collaboration** In a modern workforce environment, collaboration plays a key role in helping teams work together to solve problems. However, many organizations rely mostly on face-to-face discussions and manual information capture. Remote work is only growing more common, and will continue to do so. This was as true a few years ago as it is today, though the pandemic certainly acted as a catalyst. Therefore, enterprises need to be thinking about and implementing better mechanisms for digital collaboration and teamwork management. Workers with access to a unified platform can communicate with colleagues and track projects in the same workspace. This makes geographical constraints and lack of meaningful information — both clear signs that your outdated tools need to be replaced — problems of the past. For a deeper look at how this plays out in practice, [MangoApps' inclusion in a leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) offers useful third-party context. #### #3: **Security Threats** When legacy systems or department-specific products are accessing critical data, enterprise security can be threatened. These sorts of solutions often live outside the purview of modern security monitoring systems. For example, tool sprawl generally means that different systems are accessing and sharing data in multiple formats so that cross-functional teams can access this data at any time. This will inevitably result in problems unless there is a clear security roadmap in place for mitigating challenges like cyberattacks. Without a proper code or discipline for enterprise security as a whole, there are serious threats to customer data. There could be severe repercussions if that data falls into the wrong hands. The financial exposure is compounded by the total cost of maintaining legacy environments: SharePoint's first-year total cost for 1,000 users ranges from $130,000 to $426,000 when implementation and customization are included — a figure that makes the business case for consolidation concrete rather than abstract. #### #4: Limited Mobile Access At many enterprises, the tools they use internally either predate smartphones or come from the era when we were still figuring out how to use them. This is a major problem for any organization, but is especially relevant for distributed teams or those with deskless employees. Per Emergence Capital, 80% of the global workforce is deskless — yet frontline employees often cannot access legacy tools without a corporate email address or VPN, creating a structural access gap that no amount of policy can paper over. Traveling salespeople, frontline workers in [healthcare](/industries/healthcare) or [grocery](/industries/grocery) environments, and field technicians all benefit greatly from modern mobile-friendly tools that allow them to access all the information they need from wherever they are. With outdated tools still in use, companies often leave these people in the dark about important updates. Even worse, they may lose out on business or make a costly mistake due to the inability to access a particular tool or piece of data in a time-sensitive situation. That disconnection carries a retention cost as well: replacing a frontline employee costs between $4,400 and $15,000, making poor tooling a measurable retention risk, not just a productivity issue. #### #5: **Dissatisfied Onboarding** Disjointed operations will turn off newer employees who are anxious about learning how to navigate your tools and processes, which starts their relationship with the company off on the wrong foot. Onboarding is a make-or-break moment in the employee lifecycle — the way you present your inner workings at this critical juncture sets the tone for everything that follows. A new employee should immediately gain access to a clear set of policies and procedures, a logical repository of information, and all the tools they need to do their job. Fragmented sop operations — standard operating procedures scattered across legacy wikis, shared drives, and department-specific tools — make that first experience needlessly confusing. If you don't have these things housed in a modern workspace, new employees are likely to lose enthusiasm for their new job right out of the gate. This impacts their productivity and engagement through their whole tenure. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) examines how organizations are redesigning onboarding around unified digital environments to address exactly this problem. ### How to Evaluate Whether Your Tools Need Replacing Decision-makers who recognize these five pain points often ask the same follow-up question: how do we know when the cost of staying outweighs the cost of switching? A practical starting point is a tool audit that answers three questions: 1. **How many systems does IT actively manage, and how many overlap in function?** If the answer reflects the three-to-four times redundancy that tool sprawl typically produces, consolidation is overdue. 2. **What is the fully loaded annual cost of your current stack?** Include licensing, IT administration, security patching, and the productivity cost of employees spending 2.5 hours per day searching for information (per IDC). Compare that against the deployment cost of a unified intranet platform — legacy deployments typically require months of IT-led customization, whereas modern unified platforms can be deployed and adopted in weeks. 3. **Can every employee — including deskless and frontline workers — access the tools they need without a corporate email address or VPN?** If not, the access gap is already costing you in retention and compliance. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides a vendor-neutral framework for evaluating intranet and employee experience platforms against exactly these criteria. ### What a Modern Replacement Actually Looks Like A unified employee app addresses all five failure modes above in a single environment: a shared communication layer, collaborative project tracking, governed content with AI-curated search so employees stop spending 2.5 hours a day hunting for information, mobile-first access that requires no VPN or corporate email, and a structured onboarding experience tied to documented sop operations. The definition of intranets has evolved well beyond a static document repository — modern platforms function as the operational backbone connecting every worker, whether they sit at a desk or work a shift on a factory floor. For organizations in regulated or distributed industries, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines how peer organizations are structuring that transition and measuring ROI in the first 90 days. ### Replace Your Outdated Tools With MangoApps Digital transformation is an evident phenomenon. 89% of all organizations are adopting a digital-first strategy, and a unified employee experience will be key to their success. Engage your employees with modern productivity tools, and you empower them to do their best work as this trend continues into the future. MangoApps can prove to be the perfect solution for enterprises looking to replace or augment their legacy systems. The five problems outlined above — inefficient communication, poor collaboration, security exposure, limited mobile access, and broken onboarding — each have a direct, quantifiable cost. Addressing them through a single unified platform is not a technology decision; it is a business-case decision with a measurable return. To learn more about how MangoApps can help your organization, contact us or schedule a demo today. --- # 5 Tips To Improve Frontline Employee Engagement **Author:** Christos Schrader **Published:** 2020-12-08 **Category:** employee-engagement In many organizations that have a distributed workforce, there is often a disconnect between office and frontline workers. The office workers communicate with modern tools, leaving frontline teams out of important conversations. Luckily, there is a lot you can do to improve frontline employee engagement. Most leadership teams recognize the need for this to change. […] In many organizations with a distributed workforce, there is often a disconnect between office and frontline workers. Office workers communicate with modern tools, leaving frontline teams out of important conversations. Fortunately, there is a lot you can do to improve frontline employee engagement — and the five tips below give you a concrete starting point, whether or not you have a dedicated platform in place. Most leadership teams recognize the need for this to change. According to a Harvard Business Review survey, 78% of business leaders consider closing this gap critical to their future success. And the cost of inaction is real: replacing a single frontline employee costs between $4,400 and $15,000, making disengagement a direct financial risk — not just a culture issue. While every employee might not need a company email address, frontline workers still need to be in the loop. Otherwise, their voices are not heard. With a branded employee app, you can empower frontline employees and connect them to the company's main pulse. ## How An Employee SuperApp Boosts Frontline Employee Engagement Mobile devices are the most popular way for people to get their information. On average, approximately 70% of smartphone users check their phones within 10 minutes of receiving a notification. That matters because, per Emergence Capital, 80% of the global workforce is deskless — meaning the majority of employees worldwide do their jobs away from a desk and a desktop browser. Organizations must meet employees where they are — hence the need for an Employee SuperApp. An Employee SuperApp unifies the tools and resources an employee uses in their daily work life, particularly on the frontline. Think of it as a swiss army knife for your frontline employee's digital workplace needs: all of the services and tools required on a daily basis, rolled into one singular platform. The goal of an Employee SuperApp is to present your organization with a tool that can be molded and customized to accomplish exactly what your company needs. A fully branded, no-email-required mobile experience means frontline workers can access shift information, company news, and peer recognition without a corporate email address — and offline access to critical documents and shift schedules is a baseline expectation, not a premium feature. For context on how the broader intranet and employee experience platform landscape is evolving, the [MangoApps Included in Leading Research Firm's Intranet Platforms Ev...](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides useful independent benchmarking. These tips for boosting frontline employee engagement don't require you to have a platform like MangoApps. They're applicable to any organization. However, an Employee SuperApp definitely makes them easier to implement and track. ## Ask For Frontline Workers' Input This is an easy one, but many companies don't give their frontline employees a place to submit ideas and feedback. All you have to do is ask about their experience with the company, and encourage their response. With MangoApps, you can do this by creating a group intended for ideas and input, or leverage our ideas module. The most important thing is to make sure that leadership engages with the frontline team's posts. Seeing this response will encourage more people to make their voices heard. They'll feel good, and leadership will gain insights into frontline team needs that may have gone unvoiced before. Done well, this creates a virtuous cycle that will pay long-term dividends in boosting frontline employee engagement. Running a structured employee engagement survey or distributing employee engagement questionnaires through the same platform closes the loop — giving leadership quantified data alongside the qualitative ideas. ## Regular Town Hall Content Town hall meetings can be hard to execute. In many old-fashioned companies, executives travel and hold a big meeting in each location, one at a time. This format can be intimidating for would-be question askers, and also means diverting a lot of people away from important tasks. Also, no one gets the benefit of hearing the questions and answers from other locations. With MangoApps, it's easy to create virtual town hall content. Employees just need a group where they can ask questions they want to see addressed, anonymously or not. Then, leadership can set aside an hour every month to create video or text responses to those questions. This consistent dialogue creates a culture of openness and real communication, and lets frontline workers know they are valued. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) outlines how organizations are shifting from broadcast-style announcements to two-way dialogue as a core internal communications strategy. ## Encourage Communication Between Shifts & Locations Frontline workers often only ever see or talk to the people who are in the same location as them, and work the same hours. There might be an occasional retreat or meeting of some sort, but that doesn't usually result in any ongoing interactions. With MangoApps, it's easy to foster communication among groups of frontline workers who normally wouldn't interact. When they can give each other feedback, or share ideas that have been successful, everyone better understands each other's needs. People who have access to this sort of network feel like a part of something greater, and see the full context of what their work means. Context and feelings of contribution are major contributors to frontline employee engagement, and are lacking at far too many companies. For retail and hospitality organizations specifically, cross-location communication is especially valuable — see [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) for a practical look at how shift-based teams can stay aligned. One important caution: frontline employees who lack access to a branded mobile app are more likely to rely on personal messaging apps such as WhatsApp for work communication, creating compliance and data-security risks that a purpose-built employee experience platform eliminates. ## Recognize Great Work With Shout Outs and Rewards Everybody loves to be praised. Most leaders understand this, but lack a good place where they can dole it out. With a company app, leaders can type a quick post and give shout outs to employees who go above and beyond. It's easy, and will get in front of everyone relevant without being disruptive. You can also give out more formalized awards this way, and create space for employees to nominate each other. This takes very little effort, but goes a long way towards creating a culture of encouragement and motivating frontline workers. Pairing recognition with a structured [solutions/performance-management](/solutions/performance-management) approach ensures that informal praise connects to formal career development — a combination that drives sustained engagement. ## Actually Address Frontline Workers' Concerns All of the above are good starting points. However, if done poorly, they are empty gestures. In fact, doing all of the above without follow-through might even contribute negatively to company culture and employee engagement. If employee feedback is gathered and ignored, it can feel patronizing. The key is to actually listen. Frontline workers see things that management cannot, and their ideas can make a big difference. All you have to do is give them a space where they can contribute, and take those contributions seriously. Once you figure out what your frontline team members want, all you have to do is execute to meet their needs. People need to feel like they matter and their voices are heard. They'll feel fulfilled and do better work. As an added benefit, effective two-way communication will give you new insights and ideas that can improve your bottom line. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) identifies closing the feedback loop as one of the top priorities HR leaders are investing in this year. ## What Metrics Should You Track for Frontline Employee Engagement? Implementing the five tips above is only half the work — you also need to know whether they're moving the needle. The most actionable metrics for frontline engagement include: - **App adoption rate:** Enterprise deployments have benchmarked 90% frontline adoption within the first six months as an achievable target for a well-launched branded app. - **Active usage:** Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools — a baseline to beat, not to match. Per Social Edge Consulting, only 13% of employees use an intranet daily, and nearly a third never log in at all. - **Survey participation rate:** Tracking how many frontline workers complete employee engagement surveys over time shows whether psychological safety is improving. - **Recognition frequency:** Count the number of peer-to-peer shout outs and manager recognitions per month per team. Declining frequency is an early warning sign. - **Town hall question volume:** More questions submitted — especially anonymous ones — signals that workers believe leadership will actually respond. - **Retention rate by location:** Because replacing a frontline employee costs between $4,400 and $15,000, even a modest improvement in retention produces measurable ROI. For organizations that want a structured framework, [Gallup's 2026 State of the Global Workplace: What It Means for HR, ...](/articles/gallup-2026-state-of-the-global-workplace) provides benchmark data you can use to contextualize your own scores. ## How Long Before Engagement Efforts Show Results? Timelines vary by organization size and starting point, but the pattern from enterprise deployments is consistent: early indicators (app adoption, survey participation) move within the first 30–90 days; lagging indicators (retention, productivity) take three to six months to reflect the change. Organizations that have launched a branded frontline app have reported 87% workforce engagement achieved within a few months, and a 4x industry engagement multiple in some cases. Those results are not automatic — they depend on leadership visibly responding to feedback, consistent town hall cadence, and recognition programs that run without gaps. Training on employee engagement is often the missing link. Frontline managers need to know how to use the tools and how to respond to feedback in ways that build trust rather than erode it. Embedding that training into daily workflows — rather than running a one-off employee engagement course — is what separates organizations that sustain results from those that see an initial spike and then plateau. See [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) for a practical approach. ## What If We Can't Afford a Dedicated Platform? The five tips in this article are platform-agnostic. You can ask for input via a shared email inbox, run town halls over a free video conferencing tool, and recognize employees in a group chat. The process matters more than the technology at the start. That said, the data on generic tools is sobering: per IDC, employees spend 2.5 hours per day searching for information — a problem that a purpose-built employee experience platform is specifically designed to solve. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in. The gap between having a tool and having one that frontline workers actually use is where most engagement programs stall. For organizations in specific verticals — [industries/retail](/industries/retail), [industries/hospitality](/industries/hospitality), or [industries/nonprofit](/industries/nonprofit) — purpose-built configurations can reduce implementation time and cost significantly compared to building from scratch on a generic platform. ## MangoApps — The Employee SuperApp for Frontline Teams **MangoApps** is an employee experience platform built for organizations with a frontline workforce. With MangoApps, you're able to give 100% of your workforce all the tools they need in one employee app to increase productivity, improve retention, and boost employee engagement — with no email address required for frontline access. MangoApps is customizable and offers a wide range of unique functionalities aimed at solving any business need. Explore the [solutions/employee-engagement](/solutions/employee-engagement) page to see how the platform maps to the five tips above, or book a demo to see it in action. --- # Your Company Lunch Menu Can Boost Employee Engagement **Author:** Christos Schrader **Published:** 2020-11-10 **Category:** company-culture Everyone wants to know what’s for lunch It’s easy to forget that your company is made up of human beings, and we all get hungry. This may be the one thing we all have in common. Enter the company lunch menu. There’s probably a lot of dry information you need your team to see. For […] ## Everyone wants to know what's for lunch It's easy to forget that your company is made up of human beings, and we all get hungry. This may be the one thing we all have in common. Enter the company lunch menu — and with it, one of the most underused levers in your employee engagement strategy. There's probably a lot of dry information you need your team to see. For instance, HR policies, healthcare, changes to office rules, funding updates…the list goes on. Although important, it isn't always easy to get the team to read and engage with this type of content. However, if you are among the companies that boost employee engagement and morale by providing lunch, just about everyone wants to know what's on the menu. People will not only read this piece of content, they will actively seek it out. That voluntary, daily behavior is exactly the kind of platform habit that internal communications teams spend months trying to build — and the lunch menu hands it to you for free. ## Where is your company lunch menu now? How does your team find the lunch menu? Is it on a bulletin board somewhere? Maybe it gets emailed in bulk at the beginning of each month and buried in everybody's inboxes. Regardless, it's likely that you're missing an opportunity — and if your workforce includes frontline or deskless employees, the gap is even wider. Per Emergence Capital, 80% of the global workforce is deskless, meaning a bulletin board or a corporate email chain reaches only a fraction of the people who actually want to know what's for lunch. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in to it, and only 13% use intranet tools daily. The average employee spends just six minutes per day on intranet tools, per SWOOP Analytics — but IDC research finds they spend 2.5 hours per day searching for information across disconnected systems. A lunch menu that lives in a single, accessible platform doesn't just solve a food question; it creates a daily on-ramp to every other piece of content you need people to see. If you publish your company lunch menu daily on a digital [employee experience platform](/solutions/employee-engagement), you can be reasonably sure that everyone who eats the provided lunch will go to that platform at least once a day. There are many ways you might use this information. If you're trying to encourage everyone to use a new communication tool, putting the menu there helps build the habit. You could also bundle the menu into a daily newsletter of some sort, paired with other content that you want everyone to be aware of. Employees lose over four hours per week switching between disconnected systems, per MangoApps unified platform research; consolidating routine content like menus into a single platform directly reduces that friction. ## Use exciting content strategically Even just timing important announcements so they coincide with the posting of the lunch menu can go a long way to increase employee engagement. Although important, the company lunch menu is just one example. There are probably pieces of content specific to your company that naturally get people excited. Use them strategically, and you are sure to see an uptick in participation around other important content, too. Pair this kind of thinking with an effective employee engagement software platform, and you're well on your way to a thriving company culture. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring exactly this kind of content hierarchy. ## How to Get Started: Turning Your Lunch Menu into an Engagement System The concept is straightforward, but execution requires a few deliberate decisions. Here's a practical framework: **1. Choose a platform that reaches every employee — including frontline workers.** If your menu lives only in email or on a bulletin board, your deskless majority never sees it. Look for an employee experience platform that supports mobile access without requiring a corporate email address. Frontline and deskless employees are disproportionately disengaged precisely because routine communications never reach them. Replacing a disengaged frontline employee costs between $4,400 and $15,000, per an industry report cited on the MangoApps mobile employee app product page — making low-friction daily touchpoints like a digital lunch menu a measurable retention lever, not just a convenience. **2. Assign a clear owner for menu updates.** The menu only works as an engagement hook if it's accurate and timely. Designate one person — a facilities coordinator, office manager, or cafeteria vendor contact — to post updates on a fixed daily schedule. Inconsistency breaks the habit loop you're trying to build. **3. Use location- and role-targeted content to personalize the experience.** A branded employee app can surface location-specific menus alongside targeted HR updates, turning a single daily habit into a personalized communications channel. Retail and hospitality organizations with multiple sites, for example, can push site-specific menus to each location's employees automatically — see how this plays out in [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling). **4. Measure the engagement lift.** Track platform login frequency before and after introducing the daily menu post. Monitor open rates on content bundled alongside the menu versus content posted independently. Use an employee engagement survey or employee engagement questionnaires at the 60- and 90-day marks to capture qualitative feedback on whether employees feel better informed. OU Health achieved 87% workforce engagement within months of launching a branded employee app that centralized communications; PetSmart reported a 4x industry engagement multiple after deploying a similar app for frontline staff. These outcomes are replicable when the platform habit is anchored to content employees already want. **5. Pair menu engagement with broader training and employee engagement initiatives.** Once employees are logging in daily, that session is an opportunity. Surface microlearning content, policy acknowledgments, or employee engagement training modules alongside the menu. For a deeper look at embedding learning into daily workflows, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ## What If Your Company Doesn't Provide Lunch? The lunch menu is a proxy for any piece of content your employees actively want. If your organization doesn't offer a cafeteria or catered lunch, the same logic applies to: - **Daily shift schedules** — especially relevant for [retail](/industries/retail) and [hospitality](/industries/hospitality) workforces where shift visibility drives attendance and morale. - **Recognition and shoutouts** — peer recognition posts consistently generate high voluntary engagement on internal platforms. - **Local news and team wins** — brief, location-specific updates that feel personal rather than corporate. - **Benefits reminders tied to deadlines** — enrollment windows, wellness reimbursements, and PTO reminders perform well when surfaced at the right moment. The principle is the same: identify the content your employees seek out voluntarily, publish it consistently on your central platform, and use that daily visit to expose them to the content they need to see. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines how organizations are systematizing exactly this kind of pull-based internal communications strategy. ## The Definitive Takeaway A company lunch menu is not a communications strategy — but it is proof that one exists. If your employees will reliably seek out one piece of content every single day, you already have the foundation of a high-engagement internal communications channel. The question is whether you're building on it. Publish the menu on a platform every employee can access — including deskless and frontline workers who don't have a corporate email. Assign ownership, set a consistent schedule, bundle adjacent content strategically, and measure the lift. Organizations that treat routine, high-interest content as an engagement on-ramp consistently outperform those that rely on broadcast-only communications. The lunch menu is the simplest version of that idea. Start there, then scale it. --- # Why Mobile Apps Are Part Of Company Success **Author:** Anna Carriveau **Published:** 2020-10-16 **Category:** company-culture According to Statista, 81% of American phone owners have a smartphone. In many sectors of the workforce, that number is far higher. Companies have had customer mobile apps for years, but not one for their employees. This article will discuss a few ways that you can use your employees’ smartphones to improve company success. Reach […] # Why Mobile Apps Are Part Of Company Success Marcus manages 14 grocery stores across a metro region. He has 340 employees on the books. Three hundred of them don't have company email addresses. Every week, shift updates go out by group text. Policy changes get posted as printouts in break rooms. Training announcements depend on managers passing the word down. Per IDC, employees spend 2.5 hours per day searching for information — but Marcus's team doesn't have the infrastructure to search at all. They were never given access to begin with. This is the frontline access problem. Per Emergence Capital, 80% of the global workforce is deskless, yet most internal communication infrastructure is built for the 20% sitting at desks with managed devices and corporate email accounts. A branded mobile employee app closes that gap — and the business case for closing it is measured in dollars, not features. ## The cost of keeping frontline workers disconnected When frontline employees feel cut off from the organization, they leave. Frontline employee replacement costs range from $4,400 to $15,000 per worker. In grocery, healthcare, and logistics, annual turnover often runs at 40–60%, which means that disconnection isn't an abstract engagement problem — it's a recurring line item on the P&L. Per Social Edge Consulting, 91% of organizations operate an intranet. Nearly a third of employees never log in, and only 13% use one daily. Per SWOOP Analytics, the average employee spends just six minutes per day in intranet tools. These aren't engagement platforms serving most of the workforce — they're filing cabinets that most employees never open. The mobile app model inverts the equation. Instead of expecting employees to come to a system, the system reaches them through their personal phones — through push notifications timed to their shift, through content targeted to their role and location. Organizations that have deployed branded mobile employee apps report 87% workforce engagement within a few months of go-live, and a 4x engagement multiple compared to industry baseline after full deployment. Marcus's 300 employees without company email aren't an edge case. They're the workforce. ## No email required — and why that changes everything The most common friction point in frontline app adoption isn't app design. It's login. Requiring a corporate email address as the entry point locks out every warehouse associate, home health aide, and retail clerk who was never provisioned one. A mobile employee app built for frontline access uses personal phone numbers and SMS verification as the login mechanism. No VPN, no IT provisioning ticket, no help desk call to get started. An employee who works the 5 AM shift can download the app on their personal phone and be connected to their manager, their schedule, and their company's HR portal before the first truck arrives. This is the distinction that separates purpose-built frontline platforms from intranet software retrofitted for mobile. Intranet tools were designed for desk workers with managed devices and IT support. Mobile-first employee apps were designed for workers who bring their own phone and start a shift in 20 minutes. See how this plays out in a regulated, distributed environment: [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) demonstrates how no-email access was the difference between reaching frontline staff and not. ## From messaging tool to operational hub Marcus's original problem wasn't communication style. It was tool sprawl. Shift schedules lived in a spreadsheet. Time-off requests required a separate HR portal. Training modules were in a third system nobody remembered how to log into. Announcements happened on paper in the break room. A single branded mobile app can consolidate 200+ disparate systems into one mobile dashboard. For frontline teams, this isn't a convenience feature — it's the difference between workers who know their schedule and workers who call the store manager at 6 AM to ask. The operational consolidation matters most in three areas. **Shift scheduling and real-time updates.** Personalized push notifications, SMS, and in-app alerts targeted by role, location, and team outperform broadcast email for time-sensitive communications. When an open shift needs to be filled at short notice, the right employees see the alert in minutes — not the next time they check an inbox they rarely open. **HR self-service for workers without desk access.** Pay stubs, benefits enrollment, and PTO requests accessible from a personal phone fundamentally change the employee experience for workers who were never provisioned a desktop portal. Offline access for critical documents ensures workers in low-connectivity environments — construction sites, remote care facilities, warehouse back rooms — are never cut off from essential information. **Training embedded in daily workflows.** When training lives in the same app as the daily schedule, completion rates climb. Workers aren't context-switching to a separate LMS — they're seeing a training prompt appear between shifts, when the timing is natural and the device is already in their hand. For a deeper look at why this outperforms standalone programs, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) examines the embedded-learning difference across industries. ## The branding case: belonging as a retention strategy A company app branded with your logo and colors is not cosmetic. It signals to employees that the organization built something specifically for them — not something repurposed from the desk-worker stack and handed down. Internal branding and organizational belonging are directly linked to retention. Employees who interact with a branded digital home — rather than scattered across a dozen disconnected tools — feel more connected to the organization's identity. That connection shows up in turnover data. At $4,400 to $15,000 per frontline replacement, an app that reduces annual churn by even 2–3 percentage points pays back its cost in avoided replacement spend before most other retention investments do. For Marcus, the branded app does something group texts can't: it makes his 340 employees feel like they're part of one organization, not 14 independent stores. Company news, recognition posts, shift updates, and leadership announcements reach everyone simultaneously — including the worker who just transferred from a different location and hasn't met most of the team yet. ## Why the intranet failed and what replaces it The intranet model assumes workers will pull information when they need it. That assumption breaks down for frontline employees who don't have a desk, aren't assigned a managed device, and interact with the organization only during shift windows. One-third of employees never log into the company intranet at all, and only 13% use it daily. The gap isn't a design problem — it's an infrastructure problem. Push beats pull for workers whose default device is their personal phone, not a workstation. Mobile apps close that gap by delivering the right content to the right person at the right moment, based on role, location, shift membership, and communication preferences. Information finds the employee rather than waiting for them to go looking. That inversion is what makes adoption numbers different: when the app delivers genuine daily value — schedule access, pay stubs, shift alerts — employees open it without being told to. For how leading organizations have structured this infrastructure shift, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) benchmarks rollout timelines and engagement metrics by industry. ## What the ROI case actually looks like The business case for a frontline mobile employee app rests on three measurable levers, not a feature checklist. **Retention cost avoidance.** If Marcus's 340-person organization runs 60% annual turnover, that's roughly 204 departures per year. At the conservative $4,400 replacement cost, that's $897,600 in annual replacement spend — not counting productivity loss during transitions. An app that reduces turnover by 5 percentage points avoids roughly $74,800 in replacement costs at the low end. At the $15,000 figure, the same reduction produces $255,000 in annual cost avoidance from a single-digit improvement. **Productivity recovery.** Per IDC, employees lose 2.5 hours per day searching for information. A unified mobile dashboard with role-targeted content and offline access cuts that search time. For a 300-person frontline team working 250 days per year, a 15-minute daily recovery per employee recaptures 75,000 person-hours of productive time annually. **Engagement lift.** Organizations that have deployed branded employee apps report 87% workforce engagement within months and a 4x engagement multiple versus industry baseline after full deployment. Higher engagement correlates with lower absenteeism and higher output — the downstream effects compound the direct retention savings over time. Marcus's group texts were free. But the turnover they failed to prevent cost his organization nearly a million dollars last year. ## What successful deployment actually requires Three factors consistently predict whether a frontline mobile app achieves adoption or becomes another tool employees ignore. **No login barrier.** When employees don't need a corporate email or VPN, first-login friction drops sharply. SMS verification as the entry point is the single most effective adoption accelerator for deskless workforces. If a worker can't get in on their own in under two minutes, the app fails before it starts. **Immediate personal value.** Apps that surface shift schedules, pay stubs, and time-off requests alongside company news give employees a reason to open the app daily — not just when HR sends a broadcast. If the first session doesn't answer a question the employee actually has, the app sits unused regardless of what features it offers. **Manager-led activation.** Frontline managers who demonstrate app use in team huddles drive adoption faster than top-down mandates. When the shift manager pulls up the schedule on the app during a pre-shift briefing, the behavior becomes normalized before it becomes required. The [solutions/employee-app](/solutions/employee-app) outlines how platforms built for this model handle no-email login, offline access, role-based content targeting, and the branded experience that makes adoption stick across deskless and desk-based teams alike. The technology is the easier half of the equation. The harder half is reaching 87% of the workforce rather than the 13% who were already going to log in anyway. --- # An Internal Social Network: Mango Directory **Author:** Christos Schrader **Published:** 2020-09-29 **Category:** modules-features At many organizations, a digital employee directory with job functions and contact info can be difficult to find or nonexistent. Putting this simple, useful asset into place is one of the first steps along the digital transformation journey. With MangoApps, it is an easy, low-cost win.  Mango Directory is like an internal LinkedIn for your […] ## An Internal Social Network: Mango Directory At many organizations, a digital employee directory with job functions and contact info can be difficult to find or nonexistent. Putting this simple, useful asset into place is one of the first steps along the digital transformation journey — and with MangoApps, it is an easy, low-cost win. Mango Directory is like an internal LinkedIn for your employees: a fast, easy way to locate and learn about coworkers inside a unified [intranet](/articles/mangoapps-2026-forrester-wave-intranet-platforms) platform. Features include rich employee profiles, visual org charts, and a dashboard for company-wide resources. For employees, this means detailed, useful information is at their fingertips, whether or not they have a computer or a company email address — a critical consideration given that 80% of the global workforce is deskless, per Emergence Capital. Yet per Social Edge Consulting, while 91% of organizations operate an intranet, nearly a third of employees never log in, and only 13% use intranet tools daily. The average employee spends 2.5 hours per day searching for information, per IDC — time that a well-adopted directory directly recovers. Mango Directory is built to close that gap. "As part of my role at MangoApps, I see firsthand that many companies still rely on Excel spreadsheets to maintain employee information. We built Mango Directory to give employees one central place they could go to learn about, find, and connect with each other," said Anup Kejriwal, CEO of MangoApps. Mango Directory's rich profile pages give employees a chance to showcase their skills, personalities, and achievements alongside basic job roles and contact information. At the company level, custom attributes can be added for industry-specific needs. Better yet, these internal resumes are fully searchable, allowing employees to connect and engage in productive collaboration. Search for people by department, location, expertise, skills, and more, with multiple criteria and saveable filters. Of course, a resource like this is only as useful as the information contained within it. That's why we enable syncing with Active Directory and other enterprise systems — including HRIS platforms — so that roles, permissions, and reporting lines stay current automatically without manual admin work. We also give admins full control over which fields are required versus unnecessary, to reduce clutter. Mango Directory supports SAML 2.0 single sign-on and admin-controlled field permissions, addressing the enterprise security and compliance requirements that define a secure intranet. On both the computer and the mobile [employee app](/solutions/employee-app), Mango Directory gives employees a fully customizable and highly relevant homepage. The AI-assisted search function — with natural-language queries and saveable filters — ensures quick access to the exact information needed. Frontline employees can access the directory and company resources on personal iOS or Android devices with offline support, no VPN or corporate email required. This means time savings, improved communication and relationships among far-flung coworkers, and better morale across the board. For context, replacing a single frontline employee costs between $4,400 and $15,000 on average; connection tools that reduce turnover pay for themselves quickly. Better yet, having an employee directory is the first step of digital transformation. Once your workforce is on board with MangoApps, you have the ability to add deeper features like [internal communications](/solutions/employee-communications), collaboration tools, and training modules, all inside the platform they're already using every day. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) explores how organizations are building on this foundation to drive measurable engagement. The business edition of Mango Directory is available for free for unlimited users, and the paid version, which adds additional features including advanced analytics, HRIS sync, and expanded admin controls, comes for a small per-user license fee. Most organizations reach 95% platform adoption within 90 days of launch. --- ## How Does Mango Directory Compare to Other Employee Directory Tools? A people directory is now a foundational layer of any secure, unified intranet — and five major competitors explicitly frame directory plus secure intranet as a combined capability, per competitive movement data. What distinguishes Mango Directory is the combination of frontline-first mobile access (no corporate email required), HRIS and Active Directory sync, SAML 2.0 security, and a free unlimited-user tier that most enterprise intranet vendors do not offer at any price point. MangoApps was also included in a leading research firm's evaluation of intranet platforms — see the [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) for an independent assessment. For a broader market view, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) benchmarks MangoApps against the field. ## How Long Does It Take to Implement Mango Directory? Implementation timelines vary by organization size and existing HR system complexity, but MangoApps is designed for rapid deployment. Syncing with Active Directory or an HRIS can be configured in hours, not weeks. Profile data imports, field customization, and admin permission structures are handled through a guided setup. Most teams have a live, populated directory within days of kickoff, and the 95% adoption benchmark within 90 days reflects how quickly employees embrace a tool that is genuinely useful on day one. Healthcare organizations, for example, have used the platform to enable easy communication across distributed care teams — see the [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study for a concrete example. ## What Does 'Digital Transformation' Actually Mean for an Employee Directory? In this context, digital transformation means replacing fragmented, manual processes — spreadsheets, email chains, printed org charts — with a single, always-current source of truth that every employee can access from any device. The intranet definition most relevant here is a secure, internal network that connects people, information, and tools. Mango Directory serves as that connective layer: once employees are using it daily, the organization has the infrastructure to layer on training, communications, and workflow tools without asking people to adopt yet another platform. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines how HR leaders are sequencing these investments to maximize adoption and ROI. To learn more about how Mango Directory can benefit your organization, schedule a personalized demo today. --- # Breaking Down Work Silos Once and For All **Author:** Anna Carriveau **Published:** 2020-08-12 **Category:** industry-insights In the traditional work environment, silos are almost inevitable. With rigid top-down communication, it’s no wonder information gets lost and employees feel isolated. But breaking down work silos can actually be quite simple. With a strong centralized workspace, any organization can easily remove damaging work silos once and for all. A Shared Space One of […] # Breaking Down Work Silos Once and For All Work silos cost organizations more than morale. Employees spend an average of 2.5 hours per day searching for information (per IDC), and workers lose over 4 hours per week switching between disconnected systems (per MangoApps platform research). These are not soft productivity losses — they are measurable drains on output, engagement, and retention. This article explains what causes silos, how to measure their impact, and what structural changes actually eliminate them. ## What Causes Work Silos? Silos rarely form because employees want to hoard information. They form because the systems, structures, and norms of an organization make sharing harder than not sharing. The three most common root causes are: **Hierarchical communication structures.** When information flows only top-down, employees in different departments or levels never develop lateral communication habits. Updates get filtered, context gets lost, and teams begin operating as independent units. **Tool fragmentation.** When HR uses one platform, operations uses another, and field teams rely on text messages or printed schedules, there is no shared layer where information can flow freely. Per MangoApps platform research, employees lose over 4 hours per week just switching between these disconnected systems. **Exclusion of deskless workers.** According to Emergence Capital, 80% of the global workforce is deskless — working in warehouses, clinics, retail floors, or field sites without regular access to a corporate email address or desktop computer. Most internal communication tools are built for desk workers, which structurally excludes the majority of the workforce from day one. Understanding these causes matters because the fix has to match the diagnosis. A new chat tool does not solve a structural hierarchy problem. A searchable intranet does not help a frontline worker who cannot log in without a VPN. ## How to Measure the Impact of Silos Before investing in any solution, it helps to quantify what silos are actually costing your organization. A few concrete benchmarks: - **Information search time:** IDC research puts average search time at 2.5 hours per day per employee. Across a 500-person organization, that is roughly 1,250 hours of lost productivity every single workday. - **Intranet non-use:** According to Social Edge Consulting, 91% of organizations operate an intranet — but nearly a third of employees never log in, and only 13% use one daily. If your intranet is the primary communication channel, most of your workforce is not receiving those communications. - **Low engagement time:** SWOOP Analytics research found that employees spend an average of just six minutes per day using intranet tools. A tool that gets six minutes of daily use is not breaking silos — it is becoming one. - **Turnover cost:** Replacing a disconnected frontline employee costs between $4,400 and $15,000 (per MangoApps industry research). Silo-driven disengagement is not just a culture problem — it is a balance-sheet problem. These numbers give HR and operations leaders a starting point for building a business case. If your organization can identify even a 20% reduction in search time or a meaningful improvement in intranet adoption, the ROI calculation becomes straightforward. ## What Change Management Steps Are Actually Needed? Technology alone does not break silos. The organizations that see lasting results typically follow a structured change management approach: 1. **Diagnose before deploying.** Use an employee engagement survey or employee engagement questionnaires to identify where communication breaks down, which teams feel most isolated, and which tools employees actually use. This baseline data shapes the rollout. 2. **Secure visible leadership participation.** When senior leaders post updates, respond to comments, and use the same tools as frontline workers, it signals that the platform is not optional. Adoption follows behavior modeling. 3. **Train for habits, not just features.** Employee engagement training and training on employee engagement should focus on communication norms — when to use a group channel vs. a direct message, how to tag the right people, how to surface information for colleagues — not just how to click through a new interface. 4. **Measure adoption continuously.** Track daily active users, search query volume, and cross-department interactions. If only 13% of employees are logging in daily (the industry average per Social Edge Consulting), that is a signal to revisit onboarding, not just the tool. 5. **Include frontline workers from day one.** Any rollout that starts with desk workers and adds frontline workers later will recreate the same two-tier information structure that caused silos in the first place. ## A Unified Workspace as the Structural Fix Once the diagnosis is clear and change management is planned, the right platform can address silos at multiple layers simultaneously. Here is what that looks like in practice. ### A Single, Searchable Layer Across All Content The most direct fix for information silos is a workspace where [all of your content is in a single, searchable, and easily organized area](/solutions/employee-communications). This means not just internal posts and announcements, but files stored in SharePoint, Google Drive, Box, and Dropbox — all surfaced through universal search. Silos exist at the data layer, not just the communication layer, and a platform that integrates with 200+ enterprise systems addresses both. AI-powered personalization takes this further. Rather than requiring employees to know where to look, an AI assistant trained on company data can surface the right information to the right person automatically — reframing the searchable workspace as intelligent, not just organized. ### Communication Tools That Reach Every Employee Instant messaging, group chats, news feeds, and announcement channels are table-stakes features. What differentiates a genuinely anti-silo platform is whether those tools reach every employee — including the 80% who are deskless (per Emergence Capital). Frontline employees should be able to access [communications, schedules, and HR tools through a mobile employee app](/solutions/employee-app) without a corporate email address or VPN. For global or distributed workforces, real-time multilingual translation across 50+ languages removes language-based silos that no org chart redesign can fix. ### Departments and Groups That Organize Without Isolating Department spaces give HR, IT, operations, and other functions a home for their content — shared updates, files, calendars, and announcements — without requiring everyone to wade through irrelevant information. Groups serve a similar function at a smaller scale, organized around projects, locations, or shared interests rather than org-chart lines. The key design principle is that these spaces should be visible and joinable across the organization, not locked down. A department space that only department members can see is a digital silo, not a solution to one. ### Task Visibility Across Teams One of the quieter costs of silos is duplicated work — two teams solving the same problem because neither knew the other was working on it. Shared task spaces with assigned roles, status tracking, and cross-team visibility address this directly. When employees can see what their colleagues are working on, coordination happens naturally rather than through scheduled check-ins. ### People Discovery: Profiles, Org Charts, and Directory Search Employees cannot collaborate across silos if they do not know who to reach out to. Detailed employee profile pages — showing skills, roles, past projects, and contact information — combined with a navigable org chart make it possible for anyone in the organization to find the right person quickly. This is especially important in large or distributed organizations where employees may never meet in person. ### What If We Cannot Afford New Software? This is a fair question, and the honest answer is that the cost of inaction is also real. If replacing one disconnected frontline employee costs between $4,400 and $15,000 (per MangoApps industry research), and silo-driven disengagement is a documented driver of turnover, then the status quo carries a price tag too. For organizations with genuine budget constraints, a phased approach often works: start with the highest-impact silo (usually frontline communication exclusion or cross-department information search) and build the business case from measurable results before expanding. Employee engagement software does not have to be deployed organization-wide on day one to deliver value. It is also worth auditing what you already pay for. Many organizations are paying for multiple overlapping tools — a separate intranet, a separate messaging app, a separate task manager, a separate HR portal — that collectively cost more than a unified platform would, while still producing silos because the tools do not talk to each other. ## The Bottom Line Work silos are not a personality problem or a culture problem at their root — they are a structural problem created by hierarchical communication norms, tool fragmentation, and the systematic exclusion of deskless workers from information flows. Fixing them requires diagnosing the specific causes in your organization, building a change management plan that includes frontline workers from the start, and choosing a platform that addresses silos at both the communication layer and the data layer. The benchmarks are clear: employees spend 2.5 hours per day searching for information (IDC), nearly a third never log in to the intranet (Social Edge Consulting), and the average employee spends just six minutes per day on intranet tools (SWOOP Analytics). Any solution that does not move those numbers is not breaking silos — it is adding to them. For a deeper look at where internal communications are heading, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the shifts organizations are navigating right now. If you want to see how a large-scale deployment handled frontline inclusion specifically, the story of [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study) is a concrete example of what the rollout and adoption process looks like in practice. --- # Why you Need A Learning Management System **Author:** April Thomas **Published:** 2020-08-04 **Category:** integrated-digital-workplace More and more among successful companies learning management systems are beginning to emerge. And while you might have heard the name or maybe even taken a course or two, LMS are still a bit of an enigma among the working world. So to cut through the clutter and clear up any confusion, we have outlined […] ## Why You Need a Learning Management System A learning management system (LMS) is software that lets organizations create, deliver, and track employee training — all in one place. If your company still relies on in-person sessions, printed manuals, or scattered video calls to train workers, an LMS learning system replaces that patchwork with a consistent, measurable, and scalable alternative. This article explains what an LMS is, why it matters for learning and development, and how to evaluate whether your organization is ready for one. ## What is A Learning Management System? As the name suggests, an LMS or a learning management system is a program companies use to create and manage learning opportunities for their employees. This is done through a series of courses or lessons covering topics of every kind — from compliance and safety to product knowledge and leadership skills. Courses can include video-based modules, virtual learning sessions, quizzes, and structured reading, giving employees multiple formats that match how they actually learn. When companies implement an LMS into their organization it simplifies and improves both the overall internal teaching and learning experience. For organizations looking to build a genuine [learning and development strategy embedded in daily work](/articles/learning-and-development-strategy-embedded-in-daily-work), an LMS is the operational foundation that makes that strategy executable rather than aspirational. ## Universal Teaching One of the greatest benefits a learning management system has to offer is its ability to create a universal experience for all employees. With detailed learning courses built beforehand, all workers will be exposed to the same experience, making sure nothing is forgotten in training or misinterpreted by regional teachers. Every employee throughout the organization sees the same clear and straightforward content in the same way, whether you're an accountant in Portland or a Sales Rep in Connecticut. This consistency matters especially for standard operating procedures (SOP operations), where a single misunderstood step can create compliance risk or operational error across an entire region. ## Learn At Your Own Pace Once an LMS course has been created, completing it is a totally individual experience. Enrolled employees have the freedom to decide how, when, and where to take a course, letting them fit it in around their existing schedule. Self-appointed learning also gives workers the chance to cover topics at their own pace, spending more time on areas where they need extra practice on and quickly completing courses they already understand. This flexibility is especially important for frontline and deskless workers. Per Emergence Capital, 80% of the global workforce is deskless — meaning the majority of employees cannot access training through a desktop computer during a scheduled shift. Mobile-accessible LMS training enables these frontline workers to complete onboarding and compliance courses without requiring a desk or corporate email address, meeting them where they actually work. The [MangoApps employee app](/solutions/employee-app) is built specifically to support this kind of mobile-first learning access. ## Track Individual Understanding LMS courses even allow administrators to implement comprehensive quizzes into the learning course, giving employees the chance to test their knowledge before moving on. With knowledge checks built right into the course, employees are actually learning from their lessons and retaining important information. Quiz attempts can even be accessed by leaders and administrators, letting them see how different users performed and how many attempts it took to complete the course. Beyond quizzes, [skills management](/key-features/skills-management) tools can map course completions directly to employee skill profiles — connecting learning activity to talent development and performance reviews rather than treating training as a one-time administrative event. ## Analyze Employee Progress For administrators, learning management systems do much more than just simplify the employee learning experience. In addition to tracking individual workers, an LMS also gives leaders all kinds of detailed analytics like average length of time to complete a course, average quiz scores and answers, and the average rating of the overall course, helping them learn more about their workers, strengthen their organization, improve productivity, and create a healthier work environment. These analytics become significantly more useful when the LMS is part of a unified [employee experience platform](/solutions/employee-data) rather than a standalone tool. When course completion data sits alongside HR profiles, performance records, and workforce management data, leaders can connect learning investment to business outcomes — moving well beyond training administration into genuine learning for development. ## Streamline Onboarding While an LMS is useful in all kinds of corporate learning, it is most immediately impactful for onboarding employees. A positive onboarding experience is essential for successful workers and helps employees not only build a strong foundation but also feel connected and confident in their new organization. The efficiency gains here are measurable: onboarding speed can be cut by 50% when training is delivered through a mobile-accessible, digitized LMS versus in-person or paper-based methods. LMS platforms integrated with HRIS automatically sync employee roles, permissions, and onboarding workflows — eliminating manual enrollment and reducing administrative overhead. Organizations that have reached 90% frontline adoption within the first six months typically do so when LMS is part of a unified employee experience platform rather than a separate system employees must remember to log into separately. For a practical look at how this plays out in a distributed workforce, the [Santee Cooper case study](/resources/santee-cooper-case-study) shows how a large utility connected its workforce through a unified platform that includes structured learning pathways. ## MangoApps LMS At MangoApps, our [learning management system](/solutions/learning-management) makes creating, taking, and analyzing courses easy and enjoyable. We know that for both employers and employees access to the right information is essential to a successful work experience — and per IDC, employees already spend 2.5 hours per day searching for information, a cost no organization can afford to compound with fragmented training tools. That's why MangoApps connects LMS directly to the intranet, HR profiles, and workforce management in a single platform, avoiding the 6–8 disconnected tools problem that undermines most learning and development programs. The [training connect](/key-features/training-connect) feature ties course assignments to roles and teams automatically, so the right learning reaches the right people without manual intervention. To learn more, contact us or schedule a personalized demo today. --- ## How Do I Choose the Right LMS for My Organization? Selecting an LMS learning system comes down to three practical questions: Does it reach all your workers (including frontline and deskless employees who need mobile access)? Does it integrate with your existing HRIS so enrollment and permissions sync automatically? And does it give administrators analytics that connect to business outcomes, not just completion rates? Organizations evaluating platforms should also consider whether the LMS is a standalone product or one module inside a broader employee experience platform. Standalone tools require employees to remember a separate login, which drives down adoption — per Social Edge Consulting, nearly a third of employees never log in to intranet tools at all, and per SWOOP Analytics, the average daily time spent using intranet tools is just six minutes. An LMS embedded in a platform employees already use daily avoids this adoption gap entirely. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers vendor evaluation criteria in more detail for HR and L&D leaders building a business case. ## What Are the Risks of Implementing an LMS Without a Clear Strategy? The most common failure mode for LMS rollouts is treating the platform as a content library rather than a learning and development capability. When courses are created without clear learning objectives, without connection to performance data, and without a plan for reaching frontline workers, adoption stalls quickly. A second risk is underestimating the change management required. Per Social Edge Consulting, 91% of organizations operate an intranet, yet only 13% of employees use one daily — a gap that reflects what happens when tools are deployed without sustained engagement strategies. The same dynamic applies to LMS platforms. Building a rollout plan that includes manager accountability, mobile access for deskless workers, and regular course updates is as important as the platform selection itself. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines how leading organizations are structuring these rollouts to avoid the adoption cliff. ## How Does an LMS Connect to Broader Talent Development? An LMS that only tracks course completions is a training administration tool. An LMS that connects completions to skill profiles, performance reviews, and succession planning is a strategic talent development asset. The distinction matters because learning for development — building capabilities that the organization will need in 12 to 24 months — requires visibility into what employees know today and what gaps exist at the team and department level. MangoApps connects LMS data to [modern HCM](/solutions/modern-hcm) workflows so that course completions inform skill gap analysis, development plans, and internal mobility decisions. For HR leaders ready to move beyond the annual review cycle, the guide [Break The Annual Review Cycle](/resources/break-the-annual-review-cycle) offers a framework for building continuous development into everyday work rather than treating learning as a once-a-year event. --- # How To Build A High Performing Team **Author:** Anna Carriveau **Published:** 2020-07-15 **Category:** team-collaboration There’s nothing quite like working with a high performing team, but successful groups almost never happen accidentally. Teams, when done right, are a huge asset both to the company and individual employees. In our article today, we’ll take a look at how to build high performing teams at any organization. 5 Ways To Build A […] ## How To Build A High Performing Team There's nothing quite like working with a high performing team, but successful groups almost never happen accidentally. Teams, when done right, are a huge asset both to the company and individual employees. Below are five concrete employee engagement strategies any organization can apply to build and sustain a high performing team—whether your people sit in the same office or are spread across multiple locations. ## 5 Ways To Build A High Performing Team: #### #1: Set Clear Goals One of the biggest hurdles to building a high performing team is having to overcome unclear goals and objectives. When team members are working toward different objectives, or don't know definitively what the end goals are, poor communication and ineffective work are inevitable. Before your team starts dividing assignments, take the time to meet together and make sure everyone is on the same page. Clearly define your team's objectives and any goals or actions that go along with it. Allow people to ask questions, provide input, and start off together. Having clearly defined goals can improve your organization's [team collaboration and employee engagement](/solutions/employee-engagement)—and gives managers a baseline against which to track progress over time. #### #2: Assign Roles and Responsibilities Once everyone in the team is on the same page, it's time to assign roles and responsibilities. Clearly defined roles prevents duplicate work from happening and gives every team member a clear objective to work toward. Take the different strengths and weaknesses of team members into account when assigning roles and try to find a good fit for each member of your team. When a wide variety of skills complement each other and come together, the best outcomes always occur. Make sure every member of your team understands their importance to the team as well. In a high performing team, no one role or responsibility is more important than another. For distributed or frontline teams, role clarity matters even more. Teams that include frontline or deskless workers require mobile-first, non-email communication channels to keep all members equally informed and engaged—siloed communication is one of the fastest ways to erode the role clarity you've worked to establish. #### #3: Establish Strong Leadership Team leaders are essential for a high performing team. Leaders keep everyone focused, on track, and working well together. A good leader can build unity within a team and encourage an engaging and productive environment. When choosing a team leader, consider not only the person's capabilities, but also what kind of work needs to be done. Regardless of overall goals, a strong team leader should be able to: provide clear and helpful feedback, honestly address questions and concerns, genuinely listen to team members, manage any emerging conflicts, and wholeheartedly recognize and reward success. Listening is not a soft skill—it's a retention driver. Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback. Yet per Unily research, only 24% of frontline workers feel their feedback from customer interactions is actually heard by leadership. Closing that gap is one of the highest-leverage actions a team leader can take. For a deeper look at how information gaps affect team outcomes, see [Closing the Information Gap in Performance Reviews](/articles/closing-the-information-gap-in-performance-reviews). #### #4: Show Heartfelt Recognition Whether it's a leader encouraging teammates, or peers highlighting success, recognizing and supporting other team members will boost morale, productivity, and employee engagement. Employee recognition is key for a high performing team, and shows employees their hard work is appreciated and noticed by others—encouraging both continual effort and a healthy work environment. Recognition even benefits other team members as well, as they see the support and encouragement a peer receives and strive to accomplish the same outcome. Recognition also connects directly to measurable business outcomes, not just morale. Per Enterprise Apps Today 2022, 60% of high performing firms report increased performance when employees are recognized consistently. Peer-to-peer recognition embedded directly in team communication tools—not siloed in a separate HR system—drives faster adoption and more consistent recognition behavior. Linking recognition cadence to team KPIs gives managers a concrete way to demonstrate that appreciation programs are working, not just feel-good initiatives. #### #5: Regular Status Reports Conducting regular status reports helps everyone stay on track and keeps each other updated without having to hold long, drawn-out status meetings. With intranet tools like those available in MangoApps, team members can send out either a quick update or a detailed status report to their entire team, giving them the freedom to both create updates and read coworker reports whenever best fits their schedule. These reports keep everyone updated and informed no matter where they might be or what else is going on. High-performing teams also benefit from real-time sentiment and engagement analytics that surface morale issues before they escalate—without relying solely on periodic employee engagement surveys or questionnaires. Per Workday Peakon Employee Voice, engagement metrics can reveal warning signs up to nine months before an employee leaves, giving managers a meaningful window to intervene. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading organizations are building these feedback loops into everyday workflows. ## MangoApps High performing teams and all of their accomplishments are never out of your reach. With some careful planning and a little creativity, successful teams can happen anywhere. MangoApps supports the five steps above through specific modules—task assignments, shift management, no-code approval forms, and built-in recognition tools—so the framework doesn't live only in a planning document. To learn more about how MangoApps can support your [performance management](/solutions/performance-management) goals, schedule a personalized demo with us today. schedule demo ## How Do You Measure High Team Performance? Setting goals and assigning roles creates the conditions for high performance, but measuring it requires a different discipline. Useful team performance metrics include on-time task completion rates, sprint velocity, quality error rates, and employee engagement survey scores tracked over time. Per McKinsey research, 81% of leading companies effectively use data and analytics tools to monitor workforce performance—meaning measurement is not optional for teams that want to sustain results. Employee engagement software with built-in analytics dashboards makes it practical to track these signals without adding administrative overhead. For teams evaluating their current toolset, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines the measurement frameworks HR leaders are prioritizing this year. ## How Should Leaders Handle Underperformers on a Team? Underperformance rarely appears without warning. Engagement metrics, missed deadlines, and reduced participation in status updates are early signals that something is off. Leaders who address these signals early—through direct, honest conversation and genuine listening—are far more likely to turn performance around than those who wait for a formal review cycle. Employee engagement training and structured coaching conversations give managers a repeatable process for these discussions. The goal is not to remove the person but to understand whether the role fit, workload, or clarity of expectations is the root cause. See [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) for practical guidance on building the coaching capability that high performing teams require. ## Does Team Size Affect Performance? Research consistently points to smaller teams—typically five to nine members—as the sweet spot for accountability and communication speed. Larger teams introduce coordination overhead that slows decision-making and dilutes individual ownership. When teams must scale beyond that range, breaking into sub-teams with clear interfaces between them preserves the accountability dynamics that make small teams effective. For organizations managing large distributed workforces—such as retail, hospitality, or BPO environments—this sub-team structure, supported by mobile-first communication tools, is often the practical answer to the tension between scale and performance. The [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study) case study illustrates how one large organization maintained team cohesion at scale. --- # How To Create The Perfect Company Newsletter **Author:** Anna Carriveau **Published:** 2020-05-26 **Category:** industry-insights Company newsletters are a great tool for keeping employees up to date while boosting employee engagement and morale. At MangoApps, we’ve seen company newsletters of every kind and have figured out a few tips along the way. Whether you’re creating a weekly update, a monthly newsletter, or anything else in-between, these are a few of […] ## How To Create The Perfect Company Newsletter Company newsletters are a proven tool for keeping employees informed while boosting employee engagement and morale. At MangoApps, we've seen company newsletters of every kind and have figured out a few tips along the way. Whether you're creating a weekly update, a monthly newsletter, or anything in-between, here are our suggestions for constructing the perfect company newsletter—including what to include, how often to send it, how long it should be, and how to measure whether it's working. ### Include Company Mission and Goals Save space in every company newsletter to include your mission statement and any upcoming goals that employees need to know about. While it might seem a little repetitive at first, including this information ensures that everyone stays on the same track. This can also help keep company values and objectives fresh in employees' minds. ### Capture Employee Attention A company newsletter needs to be interesting as well as informative if employees are going to read it. A great way to make sure your content stays engaging is by including more than just standard text in your message. Take the opportunity to incorporate images, employee spotlights, photos, graphs, infographics, videos, and even gifs. Using a wide array of communication styles will help you clearly get your point across while remaining a reader-friendly piece of informative content. One often-overlooked factor: personalized newsletter content targeted by role, location, and team drives significantly higher open and engagement rates than one-size-fits-all broadcasts. A generic blast sent to every employee—from the warehouse floor to the executive suite—will inevitably feel irrelevant to large portions of your workforce. ### Upcoming Events Include relevant information about any upcoming events that employees may be interested in. Events can be anything from important deadlines to an upcoming birthday in the office. Either way, this time-sensitive information allows employees to plan ahead and gives them a reminder about what's next. ### Address Concerns Employees often voice concerns at work but tend to feel that their input is ignored or misunderstood by leaders. Help reassure workers while also answering questions by including a concerns section in your regular company newsletter. There are dozens of different ways to learn about how an employee is feeling—including employee engagement surveys and employee engagement questionnaires. Pick one and take some time to help everyone feel heard, understood, and appreciated. ### Praise Success Employees often work hardest when they feel that leadership is recognizing their efforts. Regularly highlighting teams and individuals will uplift and encourage spotlighted employees, show positive examples around the company, and encourage other workers to continue their efforts. Be genuine and generous with your praise, and employees will naturally be happier and work harder. ### A Leadership Message Consider including in every company newsletter a short message from the CEO or some other leaders in the organization. A leadership message acts as a navigation tool for employees, informing them of what is happening, what is expected of them, what changes are in store, and more. With consistent engagement from leadership, employees feel more confident and secure in the company. For a broader look at how leadership communication shapes the employee experience, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) offers current benchmarks and practical frameworks. ### Customer Success Story Customer success stories are a great way to build company camaraderie as employees learn about other areas of the organization, celebrate others' success, and see how their work impacts the overall goals and outcomes of the company. Success stories are just as uplifting as well, and help encourage and inspire everyone around. ### Reaching Frontline and Deskless Employees One of the most common newsletter failures is a distribution model that only works for desk-based employees. Per Emergence Capital, 80% of the global workforce is deskless—yet most company newsletters are delivered exclusively via corporate email or intranet, channels that frontline workers rarely access. Per Social Edge Consulting, nearly a third of employees never log in to the intranet at all, and only 13% use intranet tools daily. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools. Mobile-first delivery closes that gap. Frontline and deskless employees are often excluded from company newsletters because they lack corporate email or intranet access; delivering newsletters through a branded, mobile-native employee app removes that barrier entirely. Organizations that make this shift have seen 90% frontline adoption within the first six months when newsletters are delivered through a branded, mobile-native app rather than email alone (per Unily/CVS case study data). You can see how this plays out in practice in the [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study. For organizations in high-turnover, shift-based industries, the stakes are especially high. The average cost of replacing a single frontline employee ranges from $4,400 to $15,000—making consistent, accessible communication that reduces disengagement a measurable business priority, not just an HR nicety. ### How Often Should You Send a Company Newsletter? Frequency depends on your organization's size, pace of change, and communication culture—but a few benchmarks are useful. Most internal communications professionals recommend: - **Weekly:** Best for fast-moving organizations, project-heavy teams, or companies undergoing significant change. Keep these short (300–500 words) and scannable. - **Bi-weekly:** A practical middle ground for mid-size organizations. Allows enough time to gather meaningful content without letting information go stale. - **Monthly:** Appropriate for organizations with slower news cycles or where employees are already receiving frequent updates through other channels. Monthly newsletters can run longer (600–1,000 words) and include more narrative content like customer success stories and leadership messages. Regardless of cadence, consistency matters more than frequency. Employees who know a newsletter arrives every first Monday of the month will build a habit of reading it. Irregular sends erode that habit quickly. ### How Long Should a Company Newsletter Be? Length should match your cadence and your audience's reading context. A weekly newsletter read on a mobile device during a shift break should be tighter than a monthly digest read at a desk. General guidelines: - **Mobile-first audiences (frontline, field, retail):** 200–400 words, heavy use of bullet points, bold headers, and visuals. - **Office or hybrid audiences:** 400–800 words with a clear table of contents or section headers so readers can scan and jump. - **Executive or all-hands editions:** Up to 1,000 words when covering major strategic updates, but always lead with the most critical information above the fold. Per IDC, employees already spend 2.5 hours per day searching for information. A newsletter that is too long or poorly structured adds to that burden rather than reducing it. Respect your employees' time by being concise and well-organized. ### How to Measure Whether Your Newsletter Is Working A newsletter without measurement is a broadcast, not a communication strategy. The metrics that matter most for internal newsletters include: - **Open rate:** The percentage of employees who opened the newsletter. Benchmark varies by industry and delivery method, but rates above 50% are achievable with mobile-native delivery. - **Read rate / scroll depth:** Did employees actually read the content, or just open and close it? Employee engagement software and employee experience platforms can surface this data. - **Click-through rate:** If your newsletter includes links to resources, events, or policies, track how many employees follow through. - **Engagement score lift:** Track whether departments or locations that receive targeted, role-personalized newsletters show measurable improvement in employee engagement survey scores over time. - **Adoption rate:** For organizations rolling out a new communications platform, 87% workforce engagement within a few months of launching a branded employee communications app is an achievable benchmark—and a useful target to set before launch. For a deeper look at how internal communications outcomes connect to broader workforce trends, [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace) is worth reviewing alongside your newsletter metrics. ### Building A Company Newsletter With MangoApps At MangoApps, we help companies create the best possible newsletters with a centralized [employee communications](/solutions/employee-communications) system instantly accessible to every employee—including frontline workers who don't have corporate email. Our detailed newsletter template provides outstanding options for companies to choose from, or you're welcome to start from scratch on your own. Creators can include videos, images, files, and more, and content can be targeted by role, location, and team rather than sent as a generic blast. AI-assisted content surfacing helps communicators surface the right information to the right employees automatically. For more information on crafting a company newsletter, or to see what other features MangoApps offers through our [employee app](/solutions/employee-app), contact us or schedule a personalized demo today. --- # Are You Set Up To Support Remote Teams? **Author:** Anna Carriveau **Published:** 2020-05-19 **Category:** industry-insights With smartphones, tablets, and laptops now the new norm, the way people work is more remote than ever. Work is no longer confined to a specific space and people naturally want to embrace this newfound flexibility. For companies wanting to stay ahead, supporting remote teams is now more important than ever. How To Support Remote […] # Are You Set Up To Support Remote Teams? Supporting remote teams effectively comes down to three fundamentals: the right technology infrastructure, the right people, and a documented plan everyone can follow. With over 80% of the global workforce classified as deskless, mobile-first remote access is now a baseline requirement rather than a differentiator. Yet per Gartner, 2023, 47% of workers still struggle to find necessary information at least half the time — a direct symptom of fragmented remote infrastructure. If your organization hasn't audited its remote setup recently, the gaps are likely costing you more than you realize. ## How To Support Remote Teams ### Find the Right Technology Remote work is only possible if the right technology is easily accessible to all employees. If you're ready to embrace remote work, take the time to find the right [employee communications platform](/solutions/employee-communications) for all of your different needs. Remote technology should be intuitive for every kind of employee — including frontline and field-based workers who may not have a corporate email address or VPN access. It should be easily accessible and mobile-friendly on personal devices. A centralized system like MangoApps makes all the difference when it comes to organizing documents, saving data, and collaborating with coworkers. More importantly, it acts as a consolidation layer: employees navigating 6–8 disconnected tools daily lose over 4 hours per week switching between systems — a direct cost of fragmented remote infrastructure (MangoApps product pages — unified platform / tool sprawl framing). Replacing those siloed systems with a single communication hub reduced employee turnover by 26% for one frontline-heavy organization (Joinblink — Go North West case study). A single [employee app](/solutions/employee-app) can give frontline and remote employees access to shifts, HR tools, team communications, and company resources without requiring a corporate email address or VPN. When evaluating platforms, look for solutions with a track record of independent validation. MangoApps has been included in leading intranet platform evaluations — see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) for context on what analysts look for in enterprise-grade remote work tools. ### Video Conferencing Video conferencing is a staple of the remote work environment. It helps employees stay connected while working remotely or across various office locations. Since it is a primary form of communication, the video conferencing tools need to be high quality and dependable. As a remote workforce, you'll use video conferencing for everything from regular weekly meetings to discussing critical projects. ### Instant Messaging When not meeting via video chat, instant messaging is the perfect tool to quickly check in with employees, ask coworkers questions, or share a file or link. Instant messaging is a subtle method of communication, allowing remote workers to stay in touch while still answering at their own convenience. Instant messaging is also flexible, and can include one-on-one conversations, or group chats. For teams thinking through their broader employee communications training strategy, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring async and real-time communication layers. ### Hire a Project Manager Effective project managers are important in any company, but they're absolutely critical in remote work. Good project managers know how to find the line between overseeing employees and giving them the freedom to work undisturbed. A good project manager makes remote teamwork management more productive, efficient, and enjoyable for everyone involved. ### Find The Right Employees Hiring employees for your remote team will be one of the most important steps you'll make. While remote work has some amazing opportunities, it isn't the right fit for everyone. During your initial hiring process take time to carefully interview employees to assess their interests and abilities in a remote environment. A good candidate for remote work will have exceptional communication skills, strong organization abilities, strict time management, and regular accountability. It is critical to hire individuals who are able to efficiently communicate and collaborate while working remotely. Retention is equally important once you've hired well. Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback — making two-way communication tools a direct retention lever, not just a productivity feature. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines how organizations are building feedback loops into their remote workforce operations. ### Make a Plan As you prepare for remote capabilities, it's important to have a documented operations manual that workers can follow — covering SOP operations, escalation paths, and communication norms. Decide beforehand what exactly you want to get out of the experience and what your expectations are. Having operations instructions prepared beforehand will keep everyone on the same page and align expectations. Per McKinsey research, 81% of leading companies effectively use data and analytics tools to track whether those plans are working — so build measurement into your plan from day one, not as an afterthought. ## Building A Remote Team With MangoApps MangoApps is designed to consolidate the tools distributed teams rely on — messaging, video, document management, shift access, and HR resources — into a single employee communications platform accessible from any device, with no corporate email or VPN required. Organizations that have made this shift report measurable outcomes: 90% frontline adoption within the first six months was achieved by CVS after deploying an enterprise employee experience platform. For a detailed look at how a large distributed workforce made the transition, see [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study). To learn more about remote success or how MangoApps can help, schedule a personalized demo with us today. ## How Do You Manage Timezone and Asynchronous Communication Challenges? Timezone gaps are one of the most common friction points for distributed teams. The answer is an asynchronous-first communication culture backed by the right tooling: documented SOP operations that don't require real-time clarification, threaded messaging that preserves context, and recorded video updates that replace synchronous stand-ups when schedules don't overlap. The key is reducing the number of decisions that require immediate responses — which means investing in clear operations instructions and a well-maintained operations manual that employees can consult independently. Per Gartner, 2023, 47% of workers struggle to find necessary information at least half the time; async communication only works when information is actually findable. ## How Do You Measure Remote Team Productivity? Measuring remote team productivity starts with defining the right inputs and outputs before work begins — not retrofitting metrics after the fact. Useful signals include task completion rates against documented SOP operations, response-time benchmarks within your employee communications platform, and engagement data from your intranet or employee app. Per McKinsey research, 81% of leading companies effectively use data and analytics tools to track workforce performance. If your current toolset doesn't surface these signals, that's a consolidation problem: teams navigating manual operations across disconnected systems generate data that lives in silos and can't be aggregated. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how organizations are building measurement frameworks for distributed and frontline teams. ## What Does a Remote-Ready Technology Stack Actually Look Like? A remote-ready stack in 2025 is not a collection of best-of-breed point solutions — it's a unified layer that eliminates tool sprawl. At minimum it includes: a mobile-first employee app accessible on personal devices without VPN, integrated messaging and video, a searchable knowledge base for operations instructions and SOP operations, and HR self-service tools. The benchmark is simple: can a frontline employee on a personal smartphone complete their entire workday — check their schedule, message their manager, access their employee handbook, and submit a form — without switching apps? If the answer is no, the stack has gaps. For examples of lean operations in practice across distributed industries, the [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace) report provides useful benchmarks on engagement and productivity for remote and hybrid workforces. --- # 5 Ways to Create a Collaborative Work Environment **Author:** Anna Carriveau **Published:** 2020-05-12 **Category:** company-collaboration Creating a collaborative work environment is a natural part of any successful organization, but like most good things, it’s often much easier said than done. At MangoApps, we know the importance of team collaboration and we’re proud to be forward-thinking leaders in the field. Here are a few of our favorite ways companies can get […] # 5 Ways to Create a Collaborative Work Environment Creating a collaborative work environment is a natural part of any successful organization, but like most good things, it is often much easier said than done. The five approaches below give teams a concrete starting point — from choosing the right technology to rewarding the behaviors you want to see — and each section closes with a signal you can use to know whether it is working. **Here are five ways companies can get started creating a collaborative work environment:** ## Find the Right Technology Collaboration depends on easy communication, and that rings especially true for remote workers, on-the-go employees, and the frontline workforce. Per Emergence Capital, 80% of the global workforce is deskless — workers who often have no corporate email address, no VPN, and no reliable path into the tools their desk-based colleagues use every day. Traditional setups that rely on email and siloed tools deliver static, ungoverned content that becomes stale and drives disengagement over time. The more precise problem is tool sprawl. Employees lose over four hours per week switching between disconnected systems, making a unified collaboration platform a direct productivity intervention — not just a convenience. Per IDC, employees already spend 2.5 hours per day searching for information; fragmenting that search across a dozen apps compounds the cost. The best way to boost company collaboration is to consolidate: replace the patchwork of email threads, chat apps, and shared drives with a single [employee engagement](/solutions/employee-engagement) platform where every worker — including frontline employees without a corporate email — can communicate, collaborate, and access what they need from a branded mobile app. Per SWOOP Analytics, the average employee spends only six minutes per day using intranet tools, and per Social Edge Consulting, nearly a third of employees never log in to the intranet at all. A platform that works on the device employees already carry closes that gap. For a broader view of where intranet and employee experience platforms are heading, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) is a useful benchmark. ## Set Goals When it comes to effective collaboration, getting started is often the hardest part. Collaboration requires a unique mindset and skill base. To help employees practice this effectively and keep everyone on the same page, establish a few goals for teams and the company as a whole. Your goals can be about hosting brainstorming sessions, creating weekly updates, establishing idea management, or whatever else you think will help coworkers begin to participate in a collaborative work environment. Employee engagement surveys and employee engagement questionnaires are practical tools here: run a short pulse survey before you launch any new collaboration initiative so you have a baseline, then repeat it at 30 and 90 days to see whether participation and sentiment are moving in the right direction. ## Establish Roles Teams only work well when everyone has a place and knows their part, and collaborative efforts are not any different. Everyone should know what their job is and what is expected of them in the designated project, team, or assignment. Creating roles and responsibilities will help teams stay organized and comfortable reaching out and assisting each other. For organizations in high-turnover environments — retail, hospitality, BPO — clear role definition inside a shared digital workspace also reduces onboarding friction and helps new employees contribute faster. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading operations teams are structuring digital roles to reduce that ramp time. ## Reward Collaboration When it comes to establishing a new system, a little extra incentive never hurts. When you see successful collaboration taking place, take the time to stop and recognize the efforts of those employees. This will uplift and encourage employees to continue in their efforts and inspire other coworkers to do the same. The business case for getting this right is significant. The average cost to replace a single frontline employee runs between $4,400 and $15,000, which means a collaborative, connected work environment is also a retention investment. Recognition programs tied to visible collaboration activity — comments, shared documents, cross-team contributions — give managers a concrete way to reinforce the behaviors that reduce that turnover cost. ## Measure Collaboration Success Knowing *how* to collaborate is only half the equation. Knowing *whether* it is working is what turns a one-time initiative into a sustained cultural shift. Three KPIs give most teams a clear read: - **Participation rate:** What percentage of employees are actively contributing — posting updates, responding to questions, completing shared tasks — versus passively consuming or not logging in at all? Per Social Edge Consulting, only 13% of employees use an intranet daily, so even moving that needle by 10 percentage points is a meaningful signal. - **Project completion time:** Are cross-functional projects closing faster after you introduce shared workspaces and clearer role assignments? A reduction in cycle time is one of the clearest indicators that collaboration is reducing friction rather than adding it. - **Employee engagement scores:** Run regular employee engagement surveys and track the engagement score for teams that are actively using collaboration tools against those that are not. Per Social Edge Consulting, 91% of organizations operate an intranet, yet adoption remains low — the delta between availability and actual use is where engagement scores tend to diverge. One large enterprise case study cited 90% frontline adoption within the first six months after deploying a unified platform, demonstrating that the right employee engagement software drives measurable participation — not just availability. Tracking these three metrics gives leadership the evidence needed to expand what is working and course-correct what is not. For context on how engagement trends are shifting heading into 2026, [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace) is worth reviewing alongside your internal data. ## Create Online Updates Online updates are a practical way to encourage collaboration and enhance employee freedom at the same time. Digital updates are stored in a centralized area where coworkers can post or read updates whenever works best for them. This allows them to tailor these updates around their existing schedule. Having time to devote to an update also means that coworkers can take their time to ask questions, provide feedback, and create a truly helpful and collaborative work environment. AI-powered personalization takes this a step further: rather than surfacing every update to every employee, a modern intranet can use AI to route the right content to the right person automatically — reducing noise and making it more likely that employees actually engage with what they see. ## Use Teams in MangoApps MangoApps is designed to ensure your company has a collaborative work environment. One of the resources available to clients are designated team spaces. Team areas in MangoApps are set aside for the needs and resources of a specific team, giving them their own unique area to post updates, access files, ask questions, and much more. Frontline employees can participate fully through a single branded mobile app — no corporate email address or VPN required. MangoApps was recently recognized for this approach in [MangoApps Wins Gold in Reworked's 2026 IMPACT Awards for Excellence](/articles/mangoapps-gold-reworked-2026-impact-awards) and was evaluated among leading platforms in the [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms). Collaboration can feel frustrating at first, but with clear goals, defined roles, the right uniting intranet, and a consistent measurement habit, the payoffs become visible quickly. ## What If My Team Resists Change? Resistance to new collaboration tools is common and usually signals one of two things: the tool adds friction rather than removing it, or employees do not yet see what is in it for them. The most effective counter is to start with a small, visible win — pick one team, one project, and one workflow, and demonstrate a measurable improvement in completion time or communication clarity before rolling out more broadly. Connecting participation to recognition (see the Reward Collaboration section above) also shifts the dynamic from compliance to genuine adoption. For a deeper look at how learning and development practices can accelerate that shift, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers the connection between skill-building and sustained engagement. ## How Do I Sustain Collaboration Long-Term? Sustaining collaboration requires treating it as an operational discipline rather than a one-time initiative. That means revisiting your goals quarterly, refreshing role assignments as teams evolve, and keeping your measurement cadence consistent. It also means investing in employee engagement training so that managers — not just HR — know how to model and reinforce collaborative behaviors in their day-to-day work. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines how leading organizations are embedding collaboration and engagement practices into their standard operating rhythms rather than treating them as separate programs. --- # Why Should Companies Build A Culture Of Inclusivity? **Author:** Anna Carriveau **Published:** 2020-05-05 **Category:** company-culture Creating an inclusive environment for your employees is more than just a morale booster. A truly inclusive organization helps employees feel accepted, productive, and happier. Let’s take a look at a few of the different ways a culture of inclusivity benefits businesses of every kind. Engaged Employees To do well, employees have to feel accepted […] # Why Should Companies Build A Culture Of Inclusivity? Creating an inclusive environment for your employees is more than just a morale booster. A truly inclusive organization helps employees feel accepted, productive, and happier. The business case is clear: companies that invest in employee engagement through inclusion see measurable gains in retention, creativity, and performance. Let's take a look at a few of the different ways a culture of inclusivity benefits businesses of every kind. ## Engaged Employees To do well, employees have to feel accepted and appreciated. When companies and leaders go the extra mile to make sure everyone feels included, employees know their organization truly cares about them personally and individually. As a result, workers are more happy and engaged. In fact, recent studies from The Economist pointed out that improved inclusion in the workplace increases employee satisfaction. Organizations that have launched branded, inclusive employee apps have seen results like 87% workforce engagement achieved within months of going live (OU Health). Reviewing [Gallup's 2026 State of the Global Workplace: What It Means for HR, ...](/articles/gallup-2026-state-of-the-global-workplace) offers additional context on how engagement gaps persist across industries and what leaders can do about them. ## Increased Creativity Different backgrounds and opinions encourage us to think in new ways. Working together in an inclusive environment can prompt new and innovative ideas. According to Miguel Castro, a senior director and lead at SAP, "When people are comfortable and can authentically express themselves, they are more likely to perform better. This can improve engagement and contribute to the organization as a whole." Workplace inclusion gives employees the freedom to contribute openly and bring the best ideas to light. One often-overlooked dimension of inclusion is language access. Inclusive employee experience platforms now support inline translation in 200+ languages, directly removing language barriers for diverse and frontline workforces — a concrete mechanism that goes well beyond cultural training alone (per Beekeeper product research). This matters especially because 80% of the global workforce is deskless (per Emergence Capital), meaning frontline employees in retail, hospitality, and healthcare are structurally excluded if the tools their company uses require a desktop or a corporate email address. ## Reduced Turnover Recent studies in inclusive leadership show that higher inclusion rates have been linked to lower turnover among employees. When companies invest from the start in higher quality, more inclusive relationships, employees feel supported in their efforts. This can foster brand loyalty among employees and cultivate a long-term commitment. British Airways linked a 30-point engagement score increase to deploying a unified employee experience platform — a result that illustrates how inclusion, when supported by the right infrastructure, becomes a measurable business outcome rather than a values statement. For organizations managing complex or distributed workforces, resources like the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outline how retention strategies are evolving alongside employee experience expectations. ## Inclusivity Training The first step in creating a more inclusive culture is setting goals to make it happen. Take time as leaders to establish inclusion goals and develop training and employee engagement programs that encourage inclusive interactions. Don't be afraid to, where appropriate, ask employees about their different backgrounds, beliefs, and traditions. Allowing employees to share what makes them unique will help them feel welcome. Inclusive onboarding supported by mobile-accessible training can reduce new-hire ramp time by 50%, making employee engagement training a measurable business lever rather than a soft initiative (per Beekeeper product research). Organizations that connect inclusion goals to a unified digital workplace — combining communication, HR self-service, and training in one app — see measurably faster adoption among frontline workers who previously lacked access to company systems (per MangoApps case studies including OU Health and Kansas City Chiefs). For a deeper look at how to embed this kind of learning into daily workflows, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) is a practical starting point. ## MangoApps Building a culture of inclusivity is a major stepping stone in long-term business success, and MangoApps is here to help. With centralized and streamlined communication systems integrated right into our advanced work features, communicating and collaborating with everyone instantly becomes much easier. MangoApps functions as a mobile-first employee experience platform that reaches workers on personal devices — no corporate email required — so that frontline and deskless employees are included from day one, not treated as an afterthought. Explore our [solutions/employee-engagement](/solutions/employee-engagement) capabilities to see how the platform supports inclusion at scale, or review how MangoApps was evaluated in the [MangoApps Included in Leading Research Firm's Intranet Platforms Ev...](/articles/mangoapps-2026-forrester-wave-intranet-platforms). To learn more about how MangoApps improves organizations, schedule a personalized demo with us today. --- ## How Do You Measure the Success of an Inclusive Culture? Inclusion is only as strong as the evidence behind it. Leaders who want to move beyond good intentions should track concrete indicators: employee engagement survey scores, voluntary turnover rates, participation rates in employee engagement courses and training programs, and adoption metrics for internal communication tools. Employee engagement questionnaires administered quarterly — rather than annually — give HR teams a faster feedback loop to identify where specific groups feel excluded before problems compound. Platforms that surface these metrics in one dashboard make it easier to connect inclusion investments to business outcomes. ## What Are Common Mistakes Companies Make When Building Inclusive Cultures? The most common mistake is treating inclusion as a one-time initiative rather than an ongoing operational commitment. A single diversity training session rarely changes behavior; sustained employee engagement training embedded in daily workflows is far more effective. A second frequent error is building inclusion programs only for office-based employees. Because 80% of the global workforce is deskless (per Emergence Capital), any inclusion strategy that relies on desktop intranets or corporate email structurally excludes the majority of workers. Only 13% of employees use an intranet daily, and nearly a third never log in at all (per Social Edge Consulting) — which means information and belonging are already unevenly distributed before cultural initiatives even begin. A third mistake is failing to account for language diversity: multilingual workforces need more than translated PDFs; they need real-time, in-context translation built into the tools they use every day. ## How Can Technology Support a More Inclusive Workplace? Employee engagement software and employee experience platforms have shifted the inclusion conversation from aspiration to infrastructure. A platform that works on any device, supports multiple languages, and consolidates communication, training, and HR self-service into a single app removes the structural barriers that prevent frontline and distributed employees from feeling part of the organization. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) outlines how leading organizations are rethinking their communication stack specifically to close these access gaps. For industries where frontline inclusion is especially critical — such as [industries/retail](/industries/retail) or [industries/hospitality](/industries/hospitality) — the right platform is not a nice-to-have; it is the foundation on which any culture of inclusivity must be built. --- # How Can Technology Help Engage Field Employees? **Author:** Anna Carriveau **Published:** 2020-04-28 **Category:** employee-engagement Field employees are workers in frontline positions that interact directly with the customers, products, or services their company sells. Examples of field employees include retail staff, hospitality crews, health care clinicians, etc. Despite being on the frontlines, field employees are often the last ones to receive access to modern work technology.  Yet their job output […] ## How Can Technology Help Engage Field Employees? Field employees are workers in frontline positions that interact directly with the customers, products, or services their company sells. Examples of field employees include retail staff, hospitality crews, health care clinicians, and more. Despite being on the frontlines, field employees are often the last ones to receive access to modern work technology. Yet their job output could be greatly improved with a few simple upgrades. With better work communication tools, employees can naturally increase teamwork, have more positive customer interactions, and reduce the turnover costs that come with disengagement — replacing a frontline employee costs between $4,400 and $15,000, making disengagement a direct financial risk, not just a culture issue. According to Emergence Capital, 80% of the global workforce is deskless, yet most employee engagement software is built for desk workers. The six capabilities below show how a unified employee experience platform — one that requires no corporate email address or VPN — can close that gap. ### Six Ways Technology Can Help Engage Field Employees #### #1: Access In The Field Since frontline workers are usually on the go, computers are often inaccessible or out of reach. Granting your workers access to a mobile-friendly work app, even for short periods of the day, will allow your deskless workers to stay engaged and up to date on company news. A branded, mobile-first app lets field employees access shifts, HR self-service, training, and IT requests from a single interface — no VPN or corporate email required. This matters because, per IDC, employees spend an average of 2.5 hours per day searching for information; consolidating those resources in one place directly reclaims that time. For industries like [retail](/industries/retail) and [hospitality](/industries/hospitality), where staff turnover is high and connectivity can be limited, offline access for workers in low-connectivity environments is an equally important differentiator. #### #2: Easy Instant Messaging Field employees can use instant messaging to stay in touch with one another and quickly communicate. It's faster than email and is a simpler way of contacting someone. This is perfect for both desk employees and busy frontline workers. Instant messaging is a core component of any employee engagement strategy because it keeps communication flowing without pulling workers away from their primary tasks. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) explores how organizations are standardizing on in-app messaging to replace fragmented communication channels. #### #3: Fun Video Conferencing Using video conferencing for meetings and conversations is a great way to keep field employees in touch with workers they may not otherwise have a chance to engage with. It can be helpful for everyday meetings or even just checking in with specific employees. By building new connections and stronger relationships with employees, your organization will generate an increase in employee engagement and improved productivity. #### #4: Secure Communication When a communication method is not provided, field employees turn to Facebook, WhatsApp, or texting as an alternate communication outlet for work communication. This can create serious security issues within your organization. Beyond security risk, using personal apps like WhatsApp for work communication exposes companies to data governance and compliance failures — a liability that enterprise-grade employee engagement software is specifically designed to prevent. Long-term reliance on unsecured apps puts company data at risk and jeopardizes internal security. For organizations managing complex workforce structures, [Managing a Unionized Workforce Is Different. Your Software Should Be Too](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) outlines why purpose-built platforms matter. #### #5: Shared Speaking Space Improve employee engagement by providing a shared speaking space for all of your employees. Frontline workers can use it for brainstorming work ideas or just simple chit chat. With a place to post updates about work, employees can stay up to date on news while relating and engaging with other employees' posts. Since field employees will have access to other coworkers, they can create new connections. Failure to provide a shared communication space for your field workers leads to reduced engagement, which can be quite harmful to your company culture. The intranet adoption data underscores the urgency: per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use intranet tools daily. A shared social feed embedded in the same app employees use for scheduling and messaging drives far higher participation than a standalone intranet portal — SWOOP Analytics found the average daily time spent using intranet tools is just six minutes, a benchmark a unified platform is designed to beat. #### #6: Simple Scheduling By uploading weekly work schedules into a communication software solution, employees can easily see their approved hours. They can also quickly communicate through the program if they need to make changes or ask others to work for them, eliminating the need for texting, collecting phone numbers, or sending emails. [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) offers a practical framework for teams ready to move scheduling into a unified platform. ### MangoApps These ideas are just the tip of the iceberg when it comes to using technology to engage your deskless workers. With MangoApps' communication and collaboration platform, your field employees will have instant access to their peers and will be easily able to stay in the loop regarding company news. The platform consolidates messaging, video, scheduling, HR self-service, and training in one place — functioning as a true employee experience platform rather than a collection of disconnected tools. Real-world outcomes validate the approach: OU Health achieved 87% workforce engagement within months of launching a branded employee app, and PetSmart reported a 4x industry engagement multiple after deploying a similar frontline solution. MangoApps was also recognized in a leading research firm's evaluation of intranet platforms — see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) for details. For more information on how MangoApps can help, contact us or schedule a demo today. --- ### What Should Organizations Consider When Rolling Out Technology for Field Employees? Implementation is where many employee engagement initiatives stall. The most common obstacles include low initial adoption, resistance from frontline managers, and the challenge of reaching workers who lack corporate email addresses. A phased rollout — starting with scheduling and messaging before adding training and HR self-service — tends to produce faster adoption than deploying all features at once. Choosing an [employee engagement](/solutions/employee-engagement) platform that requires no VPN or corporate email removes the single largest barrier for deskless workers. For a broader view of how learning fits into this rollout, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) is a useful companion read. ### How Do You Measure Whether Field Employee Engagement Technology Is Working? Organizations should track both adoption metrics and downstream outcomes. Adoption metrics include daily active users, message volume, and schedule-view frequency. Downstream outcomes include employee retention rates, customer satisfaction scores, and incident or error rates. Running a structured employee engagement survey or employee engagement questionnaire at 30, 90, and 180 days post-launch gives HR teams a baseline and a trend line. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading organizations are building measurement frameworks specifically for frontline populations. If engagement scores plateau, that is typically a signal to revisit training and employee engagement programming — not the technology itself. ### What Is the Cost of Doing Nothing? The financial case for acting is straightforward. Replacing a frontline employee costs between $4,400 and $15,000. Per IDC, employees lose 2.5 hours per day to information search alone. And per Social Edge Consulting, nearly a third of employees never log in to the intranet their organization already pays for — meaning the status quo carries both a hard cost and a significant opportunity cost. Organizations in sectors like healthcare, logistics, and [hospitality](/industries/hospitality) that delay modernizing field communication tools are effectively subsidizing disengagement. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) quantifies these costs across industries and outlines the business case for a unified frontline platform. --- # Creating Connections With A Remote Workforce **Author:** Anna Carriveau **Published:** 2020-04-21 **Category:** online-community-software Shifting to a remote workforce takes practice for even the most prepared organization. Finding ways to communicate, build connections, and maintain a culture with your remote workforce can be a challenge. Fortunately, remote work doesn’t have to be difficult. With a little forethought and the right tools in place, employees can connect with coworkers, increase […] # Creating Connections With a Remote Workforce: Tactics, Tools, and Measurable Outcomes Building genuine connection across a remote workforce is one of the most concrete challenges HR and operations leaders face today. The good news: the right combination of structured communication practices, mobile-first access, and engagement measurement can close the gap between distributed employees and the organization they work for. This article walks through four proven tactics, explains how to implement each one in practical steps, and shows how to measure whether they are working. --- ## Why Remote Connection Is a Business Problem, Not Just a Culture Problem Disconnected remote workers cost organizations between $4,400 and $15,000 per replacement hire, making sustained connection a measurable retention lever (MangoApps mobile product page / industry report). At the same time, employees spend an average of 2.5 hours per day searching for information (per IDC), and traditional communication tools create tool sprawl that costs workers more than 4 hours weekly switching between disconnected systems (MangoApps unified platform product page). These are not soft costs. They show up in turnover rates, productivity metrics, and employee engagement survey scores — the same numbers that land on executive dashboards. --- ## Tactic 1: Video Conferencing — Structure It So It Actually Runs Video calls are the closest substitute for in-person interaction, but unstructured video meetings quickly become noise. Here is a three-step implementation approach that keeps them useful: 1. **Schedule a 15-minute weekly all-hands check-in.** Keep it to announcements, blockers, and one recognition moment. Rotate the facilitator so no single manager carries the burden. 2. **Run monthly virtual coffee pairings.** Use a random pairing tool or a simple spreadsheet rotation to connect two employees who do not normally collaborate. Thirty minutes, no agenda. 3. **Record and caption every meeting.** Employees in different time zones or with accessibility needs should not be excluded from the information shared. A short recorded summary also reduces the number of follow-up messages. **How to measure it:** Track attendance rates over 90 days. If weekly all-hands attendance drops below 70%, the meeting format needs adjustment — not more meetings. --- ## Tactic 2: Instant Messaging — Replace Email Threads, Not Conversations Instant messaging reduces the volume of email threads and speeds up decisions on low-stakes questions. To make it work in a remote context: 1. **Define channel conventions on day one.** Create dedicated channels for projects, departments, and social topics. Without structure, messaging platforms become as cluttered as an overloaded inbox. 2. **Set response-time norms, not always-on expectations.** Remote employees in different time zones need clear guidance: for example, a four-hour response window during business hours prevents both anxiety and burnout. 3. **Integrate with your task and document systems.** Messaging that lives in a silo forces employees to context-switch. A unified [employee experience platform](/solutions/employee-app) that combines messaging, documents, and task tracking eliminates that friction. **How to measure it:** Monitor average response time and the number of messages that escalate to email. A healthy messaging culture shows faster resolution and fewer email threads on the same topics. --- ## Tactic 3: Mobile-First Access for Frontline and Remote Workers Approximately 80% of the global workforce is deskless (per Emergence Capital), yet most remote-work communication strategies are designed for employees who sit at a computer. Frontline workers in healthcare, retail, and field operations rarely have a corporate email address or VPN access — which means standard intranet and video tools simply do not reach them. The practical fix is a branded mobile app that employees can download on a personal device without IT provisioning. This matters because, according to Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use intranet tools daily. The average daily time spent using intranet tools is just six minutes (per SWOOP Analytics). An app that lives on the device employees already carry — and that does not require a corporate email to authenticate — changes those numbers. One large enterprise deployment reported 90% frontline adoption within the first six months of launching a branded employee app. A separate deployment reached 87% workforce engagement within a few months. Those figures reflect what happens when access friction is removed rather than managed around. For organizations in industries where frontline workers are the majority — such as [healthcare](/industries/healthcare) or [grocery](/industries/grocery) — mobile-first access is not a nice-to-have. It is the baseline requirement for any remote connection strategy to function. --- ## Tactic 4: Leader Check-Ins — Consistency Over Frequency When leaders and employees work in different physical spaces, informal visibility disappears. Remote workers need to know that leadership is aware of their contributions. The risk is that check-ins become either too infrequent to matter or so frequent they feel like surveillance. A structured approach: 1. **Block one 20-minute 1:1 per employee every two weeks.** Use the first half for work updates and the second half for open conversation — career questions, concerns, or recognition. 2. **Send a brief written acknowledgment after any significant contribution.** A direct message or a public post in a team channel takes two minutes and has a measurable effect on retention. 3. **Use pulse surveys to surface what informal conversation misses.** Short employee engagement questionnaires — three to five questions, sent monthly — give leaders data on morale before it becomes a turnover problem. **How to measure it:** Track employee engagement survey scores quarter over quarter. Organizations that run regular pulse surveys and act on the results see higher retention than those that survey without follow-through. --- ## Tactic 5: Recognition and Engagement — Beyond Communication Mechanics Connection and engagement are related but not the same. An employee can receive every message and attend every meeting and still feel disengaged. Recognition, personalized content, and peer-to-peer interaction are the engagement drivers that communication tools alone do not provide. Practical steps: - **Build a recognition feed into the employee app.** Public peer recognition — visible to the whole organization — reinforces the behaviors and values that matter to the company. - **Personalize the news feed by role and location.** A frontline worker in a distribution center does not need the same updates as a corporate finance analyst. Relevant content increases the likelihood that employees open the app daily. - **Tie recognition to employee engagement training.** Managers who receive structured training on employee engagement — including how to give specific, timely recognition — produce measurably higher engagement scores on their teams. For a deeper look at how learning and development connects to daily engagement, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). --- ## How to Measure Whether Your Remote Connection Strategy Is Working Tactics without measurement are guesses. Here are the four metrics worth tracking: | Metric | What It Tells You | How to Collect It | |---|---|---| | Employee engagement survey score | Overall sentiment and trend direction | Quarterly pulse survey, 5–10 questions | | Voluntary turnover rate | Whether connection efforts are affecting retention | HR system, tracked monthly | | App or platform daily active users | Whether employees are actually using the tools | Platform analytics dashboard | | Average information search time | Whether tool consolidation is reducing friction | Periodic time-audit survey | If engagement scores are flat but daily active users are rising, the platform is being used but the content or recognition layer needs work. If turnover is falling but engagement scores lag, check whether recognition is reaching frontline workers specifically. --- ## What to Do Next A remote connection strategy does not require a complete technology overhaul. Start with the highest-friction point: if frontline workers cannot access your communication tools without a corporate email, fix that first. If leaders are checking in inconsistently, build the calendar blocks before adding new software. For organizations ready to consolidate point solutions into a single platform, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are reducing tool sprawl and improving [employee communications](/solutions/employee-communications) outcomes in distributed teams. The goal is not connection for its own sake. It is an engaged workforce that stays, performs, and contributes — and that outcome is measurable from the first 90 days. --- # Finding Benefits In Employee Dashboards **Author:** April Thomas **Published:** 2020-04-14 **Category:** modules-features One of the biggest hurdles employees face daily is attempting to track down resources and relevant information. In fact, hours are spent every week just trying to get the content you need to successfully accomplish tasks. This can lead to decreasing engagement as employees get frustrated. Fortunately, accessing information doesn’t have to be a burden. […] ## Finding Benefits In Employee Dashboards One of the biggest hurdles employees face daily is tracking down resources and relevant information. Per IDC, employees spend an average of 2.5 hours per day searching for information — time that compounds into lost productivity and declining employee engagement. Fortunately, accessing information doesn't have to be a burden. Employee dashboards solve this by consolidating the tools, content, and updates each person needs into a single, role-relevant view inside your company [intranet](/solutions/modern-intranet). This article covers the concrete benefits companies gain from employee dashboards and how to get the most out of them. ## A Centralized Space Employee dashboards are the first thing your employees see when logging into their company intranet. Dashboards encompass all of your most used and important content in one easy-to-navigate area, giving you access to all of your resources and information at a glance. Whether you're trying to check the progress of a project or navigate to another area, dashboards are the centralized space employees need to keep work effective, productive, and organized. Per Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in, and those who do average only six minutes per day of active use (per SWOOP Analytics). A well-configured dashboard directly addresses that adoption gap by surfacing what each person actually needs rather than presenting a generic homepage. A single dashboard can consolidate 200+ previously siloed systems into one unified experience, eliminating tool-switching overhead entirely. ## Layouts To Love Employee dashboards are designed to make work easier and more intuitive. It only makes sense, then, that they should be customizable to fit personal preferences. Employees can design their individual dashboard to include widgets catered to their specific needs, then organize those widgets in whatever size and arrangement makes the most sense for them. Beyond manual configuration, AI-curated personalization surfaces role- and location-relevant content for each employee automatically, reducing the burden on individuals to configure their own experience from scratch. This means a nurse in a hospital system and a warehouse associate in a distribution center each see a dashboard tuned to their context — without IT intervention. You can explore how [workspaces](/key-features/workspaces) and role-based layouts support this kind of targeted content delivery. ## Locked In Content Dashboards also give employers the ability to lock certain widgets onto their employees' dashboards. This ensures that everyone has access to the most important tools. Locked content means that while employees can rearrange where and how a specific widget appears, it cannot be removed from their dashboard. This is a practical way to make sure that no one is missing out on crucial content — whether that's a benefits enrollment link, a safety checklist, or a company-wide announcement. ## Every Kind Of Information Dashboards give you the freedom to add whatever kind of content will best help your teams. Dashboard widgets include both static content, like forms and shortcuts, and dynamic content, like notifications and company news. Having both types of information readily available enables employee dashboards to be the one-stop access area for updated and important information. This breadth matters for employee engagement. When employees can find policy documents, submit HR requests, complete training on employee engagement, and read the latest company news from a single screen, the friction that drives disengagement disappears. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) explores how unified content access directly correlates with measurable engagement improvements. ## Work From Anywhere — Including the Frontline With mobile-friendly digital dashboards, employees have the freedom to work from anywhere. Dashboards are updated instantly and accessible anywhere with internet access, allowing workers to see and utilize the most recent information from whatever device they have next to them. This matters especially for the deskless workforce. Per Emergence Capital, 80% of the global workforce is deskless — and most traditional intranet tools were never built for them. Frontline employees can access dashboards without a corporate email address or VPN, on personal iOS or Android devices with offline support for critical content. That removes the single biggest barrier to frontline intranet adoption. Per Social Edge Consulting, only 13% of employees use an intranet daily; mobile-first, no-email-required access is one of the most direct levers for closing that gap. The business case for closing it is concrete: replacing a disconnected frontline employee costs between $4,400 and $15,000 (per MangoApps mobile product page), making dashboard adoption a measurable retention investment, not just a convenience feature. Organizations that have acted on this see real results — OU Health achieved 87% workforce engagement within a few months of launching a branded dashboard app, and PetSmart delivered 4x industry-average engagement through a unified mobile dashboard. For a deeper look at how a [modern employee app](/solutions/employee-app) extends dashboard access to every worker regardless of role or device, the use cases map directly to the frontline scenarios described here. ## MangoApps With dedicated employee dashboards in your work environment, workers finally have the opportunity to use one quick, efficient, and centralized space. At MangoApps, we work with companies of every kind to create a holistic digital experience — from configuring a [company portal](/key-features/company-portal) that reflects your brand to deploying role-specific layouts that serve both desk-based and frontline teams. To learn more about employee dashboards or to see MangoApps at work in your own company, contact us or schedule a demo today. **Schedule Demo** --- ## How Do I Navigate to Benefits or HR Content in My Dashboard? If your organization has configured a benefits widget, it will appear on your dashboard home screen — either pinned by your administrator (locked content) or available in the widget library for you to add. Look for widgets labeled HR, Benefits, or your HRIS provider's name. If you don't see a benefits widget, contact your HR or IT administrator: they can lock the widget to your dashboard so it appears for your role. Administrators can also create a dedicated [department site](/key-features/department-sites) for HR that houses benefits enrollment links, plan documents, and open-enrollment deadlines in one place, then surface that site as a dashboard shortcut. ## What If My Benefits Widget Is Missing? A missing widget usually means one of three things: the widget hasn't been added to your organization's dashboard library, your role or location profile doesn't include it in the default layout, or it was removed during a dashboard reconfiguration. The fastest path to resolution is to check the widget library (typically accessible via an "Add Widget" or "+" button on your dashboard) and search for your benefits provider or HR system by name. If it isn't listed, ask your intranet administrator to add it. Administrators can use the [webpage builder](/key-features/webpage-builder) to create a custom HR landing page and pin it as a widget for specific employee groups — no development work required. ## How Do I Customize My Dashboard to Show the Content I Need? Most employee dashboards support two layers of customization: personal and administrative. As an individual employee, you can typically drag and resize widgets, add new ones from the library, and remove any widget that isn't locked. As an administrator, you can define default layouts by role, department, or location — and lock high-priority widgets (like benefits enrollment, safety alerts, or employee engagement survey links) so they're always visible. If your organization uses AI-driven personalization, the system will also surface role- and location-relevant content automatically over time, supplementing whatever manual configuration you've done. For a full walkthrough of layout and widget options, the [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) benchmarks how leading platforms handle dashboard personalization and can help you evaluate whether your current setup matches best practice. --- # What Is Enterprise Content Management? **Author:** April Thomas **Published:** 2020-04-07 **Category:** integrated-digital-workplace What Is Enterprise Content Management Enterprise content management is the way that your organization chooses to store and handle data at an enterprise level. This includes everything from document storage to document sharing and analysis. If it involves the lifecycle of information, it’s part of enterprise content management. Naturally, such a large scope encompasses a […] ## What Is Enterprise Content Management Enterprise content management (ECM) is the strategy and set of tools an organization uses to capture, store, organize, manage, and deliver information across its entire lifecycle — from creation and collaboration through archiving and disposal. This includes document storage, version control, workflow automation, records management, and secure access controls. If it involves how information moves through your organization, it is part of enterprise content management. For most organizations, the practical problem ECM solves is this: employees spend an average of 2.5 hours per day searching for information, per IDC. That is roughly 30 percent of the workday lost before any productive work begins. A well-implemented ECM strategy cuts that waste by making content findable, governed, and accessible to the right people at the right time — whether they sit at a corporate desk or work on a factory floor without a company email address. ## Why Does Enterprise Content Management Matter? Imagine walking into an office where company information is literally all over. Files are covering the floor, books on every imaginable topic are open on desks and chairs, and somewhere in the mess is a flash drive with even more information. In the office, a handful of employees are rummaging through the papers trying to find information, taking papers off to new areas, and even throwing new work into the air. Actually accomplishing anything in such an environment seems absurd, if not impossible. And yet, all too often we treat our digital workspaces in a similar way. Just because information is saved somewhere does not mean it is organized or easily accessible, especially when it is needed by a large number of employees. Successful enterprise content management brings order to the confusion and puts into place a logical and easy-to-follow processing system — simplifying, streamlining, and improving everything from digital archiving to data workflow. Effective ECM also connects directly to employee retention. Replacing a disconnected frontline employee costs between $4,400 and $15,000, according to an industry report cited on MangoApps' mobile employee app product page — making poor content accessibility a measurable retention risk, not just a productivity issue. Organizations that treat ECM as infrastructure rather than an IT project protect both productivity and headcount. For a broader look at how structured information access supports workforce performance, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) offers useful benchmarks across platform categories. ## What Are the Core Components of an ECM System? A complete ECM system typically spans five functional areas: 1. **Capture and ingestion** — scanning, uploading, and tagging documents and records from any source, including email, forms, and third-party applications. 2. **Storage and organization** — structured [libraries](/key-features/libraries) and [knowledge bases](/key-features/knowledge-bases) that give every piece of content a logical home with consistent metadata. 3. **Workflow and process automation** — routing documents for review, approval, or archiving without manual handoffs. 4. **Search and retrieval** — universal search across connected repositories (SharePoint, Google Drive, Box, and internal wikis) so employees find what they need in seconds rather than hours. 5. **Governance and compliance** — permissions, audit trails, retention policies, and access controls (including SSO and SAML 2.0 support) that ensure only authorized users see sensitive content and that records meet regulatory requirements. Governance deserves particular emphasis. Without it, ECM becomes a content dumping ground. A [content governance engine](/key-features/content-governance-engine) enforces ownership, expiration dates, and review cycles so content stays accurate and compliant rather than accumulating as stale noise. ## ECM and the Intranet: Understanding the Relationship The definition of intranets and ECM are often conflated, but they serve distinct purposes that overlap significantly in practice. An intranet is the internal network and employee-facing portal through which people access company information, communicate, and collaborate. ECM is the underlying discipline that governs how that information is structured, stored, and controlled. Per Social Edge Consulting, 91% of organizations operate an intranet — yet only 13% of employees use it daily, and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools. Those numbers reveal an adoption problem that ECM strategy directly addresses: when content is disorganized, outdated, or hard to find, employees stop returning to the platform. A [modern intranet](/solutions/modern-intranet) built on sound ECM principles — structured content, governed permissions, AI-assisted search — closes that engagement gap by making the intranet genuinely useful rather than a digital bulletin board. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) explores how leading organizations are redesigning their intranet experience around content accessibility and employee engagement. ## ECM for the Deskless Workforce Traditional ECM implementations were designed for office workers with corporate laptops, VPN access, and company email addresses. That model excludes approximately 80% of the global workforce, which is deskless, per Emergence Capital. Frontline employees in manufacturing, healthcare, retail, and logistics need access to schedules, HR documents, safety procedures, and operational content — but most legacy ECM platforms were never built to serve them. Enterprise-grade ECM must extend to mobile, no-email frontline employees. That means a [company portal](/key-features/company-portal) accessible from a personal smartphone, content permissions that do not require a VPN, and push notifications that surface relevant information without requiring employees to search for it. Organizations that close this gap see measurable differences in engagement and retention. OU Health, for example, achieved 87% workforce engagement within months of launching a branded unified app — an outcome that reflects what happens when ECM reaches every employee, not just desk workers. ## ECM Best Practices Organizations that get the most from enterprise content management tend to follow a consistent set of practices: - **Audit before you build.** Map where content currently lives, who owns it, and how often it is accessed before selecting tools or migrating data. - **Assign content ownership.** Every document or knowledge article should have a named owner responsible for keeping it current. Orphaned content is the primary driver of intranet abandonment. - **Standardize metadata and taxonomy.** Consistent tagging makes search reliable. Without it, universal search returns noise instead of answers. - **Integrate rather than duplicate.** ECM platforms that connect to existing tools — Microsoft 365, Google Workspace, Slack, HRIS systems — reduce friction and eliminate the need to maintain parallel repositories. - **Plan for frontline access from day one.** If your ECM strategy does not account for mobile, no-email employees, it is not enterprise-grade. - **Govern continuously.** Set content expiration dates, schedule periodic audits, and enforce retention policies. ECM is not a one-time migration; it is an ongoing operational discipline. For organizations evaluating [knowledge management](/solutions/knowledge-management) as part of a broader ECM strategy, these practices apply equally to wikis, FAQs, and structured knowledge bases. ## How MangoApps Supports Enterprise Content Management At MangoApps, we believe in keeping everything centralized, from employee communication to digital storage and data processing. When content is searchable, organized, and available within one area, employees are better able to stay focused, accomplish tasks, and feel engaged in their organization. All of our platforms are fully customizable and accessible anywhere with internet access — including on mobile devices for frontline employees who do not have corporate email addresses or VPN access. MangoApps incorporates a wide variety of tools designed to assist users during every stage of the content management process. Whether you need structured document libraries, survey tools to gather employee input, workflow automation to route approvals, or collaborative project spaces, MangoApps supports the full content lifecycle. Integrations with Microsoft 365, Google Drive, Box, Slack, and 200+ other applications mean teams can use existing tools while benefiting from a unified, searchable experience — without the $130,000–$426,000 first-year infrastructure cost that a 1,000-user SharePoint deployment typically carries. MangoApps also incorporates AI-powered content surfacing, including universal search, OpenAI and Gemini integrations, and AI-curated feeds that surface relevant content based on role, location, and activity — so employees spend less time searching and more time working. To see how other organizations have put these principles into practice, the [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study) case study illustrates what a well-governed, mobile-accessible ECM deployment looks like at scale. ## What Should I Look for in an ECM Platform? When evaluating ECM platforms, prioritize these criteria: - **Unified search** across all connected repositories, not just native content - **Governance controls** including permissions, audit logs, retention policies, and SSO/SAML 2.0 support - **Mobile-first access** for frontline and deskless employees without VPN or corporate email requirements - **Integration breadth** with the productivity tools your teams already use - **AI-assisted retrieval** that surfaces relevant content proactively, not just reactively - **Deployment speed** — platforms that require months of IT-led customization create governance debt and stale content before the first employee logs in - **Adoption metrics** — ask vendors for daily active usage data, not just seat counts The [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides independent analyst context for how unified platforms are being evaluated against these criteria in 2026. ## How Do I Get Started with ECM Implementation? Most successful ECM implementations follow a phased approach: 1. **Discovery** — audit existing content repositories, identify the highest-friction information workflows, and define governance requirements. 2. **Platform selection** — evaluate tools against the criteria above, with particular attention to frontline access and integration depth. 3. **Pilot deployment** — launch with one department or use case, measure search success rates and time-to-information, and refine taxonomy before scaling. 4. **Governance setup** — assign content owners, configure permissions, set retention policies, and establish a review cadence. 5. **Rollout and adoption** — train employees, communicate the value proposition clearly, and track daily active usage to identify adoption gaps early. For organizations connecting ECM to broader workforce operations, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading companies are integrating content strategy with operational workflows. Whatever your current enterprise content management process, MangoApps is here to help. To see MangoApps at work firsthand in your own organization, contact us or schedule a personalized demo today. --- # How To Collaborate While Working Remotely **Author:** Anna Carriveau **Published:** 2020-03-31 **Category:** company-collaboration Remote work is becoming increasingly essential each year. Running a business with remote employees offer both the employees and the organization many advantages. However, learning to navigate the remote environment can take a little getting used to. Flexible schedules, being away from the office, and all of the other changes in the remote environment means […] # How To Collaborate While Working Remotely Remote work is no longer an edge case — it is how a growing share of the global workforce operates. Whether your team is fully distributed, hybrid, or includes frontline employees who never sit at a desk, the core challenge is the same: how do you keep people collaborating effectively when they are not in the same room? The answer comes down to four practical strategies — digital communication, virtual collaboration spaces, transparent management, and leadership support — backed by the right unified platform. This article walks through each one so you can act on them immediately. ## Empower Remote Workers With Digital Communication It is impossible for remote workers to collaborate if they cannot communicate easily. Every employee needs a simple, straightforward method of communicating both one-on-one and as a group — through private messaging, news feeds, videos, audio calls, and direct messaging. An intranet platform that consolidates these channels removes the friction of jumping between disconnected tools. That friction is measurable. Remote and distributed teams lose over four hours weekly switching between disconnected communication and work-management systems, compounding collaboration friction beyond simple distance (MangoApps product pages). Meanwhile, employees already spend 2.5 hours per day searching for information (per IDC), a burden that a well-configured intranet with universal search and AI-assisted information surfacing can cut significantly. The definition of an intranet has also expanded. Today's platforms are not static document repositories — they are dynamic employee hubs. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use one daily. The gap between deployment and adoption is almost always a usability problem, not a technology problem. Choosing a platform built around the employee experience — not IT convenience — is the first step toward closing that gap. For a deeper look at how modern platforms are evaluated, see [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report). One often-overlooked dimension: per Emergence Capital, 80% of the global workforce is deskless. Frontline and remote employees can access communications, schedules, and HR tools without a corporate email address or VPN, removing a common barrier to participation for non-desk workers (MangoApps product pages). Any remote collaboration strategy that ignores mobile-first, no-email access is leaving a large share of the workforce behind. ## Establish Collaboration Spaces Collaboration is straightforward when employees are in the office — you walk down the hall. When physically gathering is not an option, the answer is virtual collaboration spaces. With digital platforms designed specifically for group and team collaboration, employees have a dedicated space to ask questions, post updates, share resources, and work together in real time. Effective teamwork management in a remote context means those spaces need to be persistent, searchable, and organized by project or team — not buried in an email thread. A unified platform replaces the patchwork of point solutions (separate chat apps, file-sharing tools, video platforms) that creates the tool-sprawl problem described above. For a real-world example of what this looks like at scale, the story of [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study) shows how a large distributed workforce achieved 90% frontline adoption within the first six months of deploying a modern employee app. ## Ensure Transparent Management When employees work remotely, it can be difficult to know what everyone is responsible for and who carries specific assignments. For teams to collaborate effectively, everyone needs to be on the same page. Efficient project management tools simplify this process significantly. Project managers can assign responsibilities to each team member digitally and track individual progress — all within the same communication and collaboration platform. This helps coworkers know who carries which responsibilities and keeps everyone accountable while working outside the office. Transparency also has a retention dimension. Replacing a single frontline or remote employee costs between $4,400 and $15,000 on average. Poor remote collaboration and disengagement are leading drivers of that turnover. Clear task ownership, visible progress, and consistent manager check-ins are not soft benefits — they are cost controls. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading organizations are structuring remote work management to reduce both friction and attrition. Traditional intranet deployments take months of IT-led customization and produce static, ungoverned content that becomes stale — a direct obstacle to remote collaboration (Unily product page). Modern platforms built for [employee communications](/solutions/employee-communications) invert that model: content is governed by the teams who own it, updated continuously, and surfaced to the right people through personalization rather than manual navigation. ## Emphasize Leadership Support Transitioning to working remotely takes time for even the best employees. And even though it offers real advantages, it will always be different than working in the office. Remote workers need to know that leadership not only understands their new needs but also supports and encourages them in their remote efforts. This is especially important when only some employees work outside the office. Without the consideration and care of leadership, remote employees can feel isolated and reluctant to participate fully in collaborative efforts. Leadership support is also a communications design problem. If the channels leaders use to share updates, recognize contributions, and gather feedback are not accessible to remote and frontline workers, those workers are structurally excluded from the culture — regardless of intent. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) outlines how organizations are redesigning leadership communication to reach every employee, not just those at a desk. ## Working Remotely With MangoApps Whether you are gradually transitioning toward remote possibilities or find yourself in an unexpected remote work situation, collaboration is not only still possible — it can be more consistent and measurable than before. MangoApps brings digital communication, collaboration spaces, project management, and leadership tools into a single [employee app](/solutions/employee-app), eliminating the tool-sprawl that costs distributed teams hours every week. Frontline workers get mobile-first access without a corporate email address; desk workers get a unified hub that replaces disconnected point solutions; and managers get visibility into progress and participation across the entire team. To learn more about working remotely, our product and services, or to see how MangoApps can work within your own organization, contact us or schedule a personalized demo today. ## What Tools Should Remote Teams Actually Use? The strategies above — digital communication, collaboration spaces, transparent management, leadership support — all depend on the underlying platform doing the heavy lifting. The most common mistake organizations make is assembling a stack of point solutions (one tool for chat, another for file sharing, a third for project tracking) and expecting employees to stitch them together. That approach produces the tool-sprawl problem: over four hours of lost productivity per employee per week (MangoApps product pages) and an intranet that only 13% of employees use daily (per Social Edge Consulting). A unified platform addresses this by making the intranet the single destination for communication, collaboration, and work management. MangoApps has been recognized for this approach — see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) for an independent assessment of where the platform stands relative to the market. For organizations in specific industries, the implementation details vary. Healthcare organizations managing distributed clinical and administrative staff, for example, face different compliance and access requirements than retail or financial services teams. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers platform selection criteria across industries. ## How Do You Measure Remote Collaboration Success? Most organizations deploy remote collaboration tools and then measure success by adoption rate alone. That is a starting point, not a finish line. Meaningful measurement looks at three layers: - **Participation breadth**: Are frontline and non-desk employees engaging, or only office-based staff? Per Emergence Capital, 80% of the global workforce is deskless — if your metrics only reflect desk workers, you are measuring a minority. - **Information findability**: Are employees spending less time searching for what they need? IDC's benchmark of 2.5 hours per day searching for information is the baseline to beat. AI-assisted search and personalized content surfacing are the primary levers. - **Task and project visibility**: Can managers see assignment status, blockers, and completion rates without scheduling a status meeting? Transparent project management tools make this visible by default. Organizations that track all three layers consistently report higher engagement and lower turnover among remote and frontline populations — outcomes that connect directly to the $4,400–$15,000 replacement cost avoided per retained employee. ## How Do You Onboard Remote Employees Into a Collaborative Culture? Onboarding is where remote collaboration either takes root or fails. New remote employees who cannot find information, do not know where to ask questions, or feel invisible in digital spaces disengage quickly — often before the 90-day mark. Effective remote onboarding uses the same platform employees will use every day: the intranet and employee app. Structured onboarding paths, accessible on mobile without a VPN or corporate email, give new hires a guided first experience rather than a blank screen. Managers who use the platform's project and task tools to assign early wins give new employees visible accountability and a sense of contribution from day one. For organizations building or rebuilding their onboarding approach, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers how embedding learning into daily workflows — rather than separating it into a standalone LMS — accelerates time-to-productivity for remote and frontline employees alike. --- # Transforming Customer Experience Through Employee Engagement **Author:** Anna Carriveau **Published:** 2020-03-24 **Category:** employee-engagement In the business world, it is crucial to monitor your customer experience. Without a positive customer environment, even the best products and services will struggle to survive. Most organizations overlook one of the most obvious ways to strengthen customer experience. Research has illustrated a direct link between employee engagement and customer experience. In fact, a […] # Transforming Customer Experience Through Employee Engagement Customer experience is determined before a customer interacts with your brand. It is shaped by whether your frontline employees know what they are doing, believe in where they work, and have the information they need to resolve issues quickly. Those conditions are an engagement problem before they are a training problem, a technology problem, or a process problem—and the evidence is difficult to dismiss. Organizations with high employee engagement see up to four times more profitability than comparable peers. But the engagement strategies most organizations deploy target the wrong employees: desk-based workers with corporate laptops, company email addresses, and a dedicated place to complete an annual survey. Per Emergence Capital, 80% of the global workforce is deskless. In retail, hospitality, healthcare, and BPO—sectors where customer interactions are the product—the majority of customer-facing employees never receive the recognition, communication, or training that engagement programs promise. That gap is where customer experience breaks. ## Why frontline employees are the customer experience variable most organizations underestimate The connection between employee engagement and customer outcomes runs through a mechanism that is operational, not motivational. The quality of a customer interaction is constrained by what the employee in that interaction knows, how quickly they can access it, and whether they have the confidence to act on it. Engaged employees carry better answers into those interactions—not because they care more, but because they have been given the infrastructure to be more effective. Frontline employees—store associates, contact center representatives, healthcare technicians, logistics workers—are the people having those interactions. They are also the employees most systematically excluded from the communication and recognition infrastructure that engagement programs depend on. Per IDC, employees spend an average of 2.5 hours per day searching for information. For desk workers with full intranet access, that number is already significant. For frontline employees who lack company email or cannot satisfy a VPN requirement on a personal device, it often means the information does not arrive at all. A frontline associate who cannot quickly confirm a return policy, locate the escalation contact, or retrieve a product specification mid-conversation delivers a customer experience that pricing strategies and loyalty programs cannot compensate for. Per Social Edge Consulting, 91% of organizations operate an intranet. Only 13% of employees use it daily, and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends six minutes per day on intranet tools. Those numbers are not indictments of employee motivation—they are measurements of tools built for desk workers and deployed to a workforce that is mostly not at a desk. ## Ownership, trust, and the behaviors customers notice When employees receive consistent recognition, stay informed about organizational direction, and have access to the same communication channels as corporate staff, they develop a sense of ownership over outcomes. That ownership changes how they handle customer interactions in ways that are visible to customers but difficult to script or manufacture. An engaged frontline employee defends the organization in difficult conversations, recommends it to their own networks, and absorbs service friction without passing it to the customer. These are documented behavioral differences between high-engagement and low-engagement frontline workforces. They represent a form of customer experience capital that competitors cannot easily replicate, because it is built through consistent treatment of employees over time, not through training scripts. Building that ownership requires closing the communication gap between corporate and frontline workers. Employee engagement surveys and employee engagement questionnaires are practical diagnostic tools for identifying where trust is breaking down before it surfaces in customer reviews and churn data. What the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) research shows is that manager relationships and access to development resources are the strongest predictors of engagement—both of which depend on communication infrastructure that reaches employees where they work, not infrastructure they have to travel to a desk to access. An organization running an intranet that frontline workers do not use is not running an engagement program. It is running a program for the 20% of the workforce that already has the most access to organizational resources. ## Information access as the operational link between engagement and customer service The most direct path from employee engagement to customer experience improvement runs through information access. An employee who can pull up a product specification, confirm a time-sensitive promotion, or find the right escalation contact without interrupting the customer interaction delivers a measurably different experience than one who cannot. This is not a problem that employee engagement training courses solve on their own. It requires communication infrastructure that delivers the right information to the right employee at the right moment—on a device they already carry, without prerequisites that most frontline employees cannot satisfy. Frontline employees navigating six to eight disconnected tools daily experience communication fragmentation that directly degrades response times and service consistency. The solution is not more tools—it is fewer tools, accessible without a managed device or corporate email account, that surface the right information at the right time. Organizations that digitize onboarding and provide mobile-accessible training on employee engagement and operational procedures report up to 50% faster time-to-productivity for new hires. That compression matters most in the first 90 days after hire, when customer service quality is most at risk. High-turnover sectors—retail, hospitality, BPO—cycle through this vulnerability constantly. Faster time-to-productivity reduces the window during which customers encounter employees who are not yet equipped to help them. Enterprise deployments of mobile-first employee experience platforms have demonstrated 30-point increases in employee engagement scores and 90% frontline adoption within six months when rollout includes visible leadership participation and manager-level employee engagement training. The [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study documents how structured communication tools translate into measurable operational improvements in a knowledge-intensive frontline environment—a pattern that applies wherever employee information access is the primary constraint on service quality. ## What unlocks the idea-sharing loop Some of the most consequential improvements to customer experience originate with frontline employees—the people who hear customer complaints directly and observe process failures in real time. Those improvements only reach decision-makers when employees have accessible communication channels and a reasonable expectation that sharing is professionally safe. Employee engagement training that builds psychological safety—combined with platforms that give frontline workers a voice in organizational channels rather than limiting them to receiving top-down communications—opens this loop structurally. Per Social Edge Consulting, the gap between organizations that run intranets (91%) and employees who use them daily (13%) reflects a design problem, not an awareness problem. The tools were not built for the employees most likely to have the feedback worth acting on. The practical implication is that idea-sharing cannot be created through culture initiatives alone if the communication infrastructure excludes the employees you need to hear from. Embedding communication channels and employee engagement courses into daily workflows—rather than treating them as separate events requiring desktop access—is how organizations sustain this culture at scale rather than cycling through launch-and-decay patterns. ## How to measure the employee engagement and customer experience connection The most direct measurement approach tracks customer satisfaction scores (CSAT, NPS) alongside employee engagement survey results on a consistent quarterly cadence. When both datasets are collected regularly and attributed to the same teams or locations, the correlation becomes operational rather than theoretical: teams with higher engagement scores reliably produce higher customer satisfaction ratings. Operational leading indicators worth tracking alongside satisfaction scores include first-contact resolution rates, average handle time, employee turnover in customer-facing roles, and time-to-productivity for new hires. These metrics typically move before CSAT does, giving operational teams time to address root causes before they surface as visible customer experience problems. At the investment level, reduced voluntary turnover is the largest single driver of engagement program ROI. Replacing a frontline employee costs an estimated 50 to 200 percent of annual salary when recruiting, onboarding, and lost productivity are fully accounted for. Improved engagement scores reduce voluntary turnover measurably, which compounds across the tenure of a workforce. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) provides a measurement framework for connecting engagement investment to outcomes that finance and operations stakeholders can act on—moving the conversation from directional benefit claims to trackable business metrics tied to retention and service quality. ## What to expect from an engagement transformation Timelines vary by organizational size and starting conditions, but the pattern from enterprise deployments is consistent. Early operational wins—faster information access, reduced search time, improved onboarding speed—typically arrive within the first quarter. Measurable engagement score improvements are visible by the end of the first year. The cultural layer—the shift in ownership, trust, and the brand ambassador behaviors that most directly affect customer experience—requires 12 to 18 months of consistent reinforcement through recognition programs, feedback loops, and employee engagement software that reaches every employee, not just those at a desk. Organizations that set these expectations clearly at the outset avoid the most common failure mode: abandoning an engagement initiative before the cultural change has time to compound into customer experience outcomes. For industries where customer-facing labor is both the primary cost and the primary competitive differentiator—retail, hospitality, healthcare, BPO, nonprofit services—that compounding creates durable separation from competitors still running engagement programs that do not reach their frontline workforce. The organizations that close the customer experience gap are, almost without exception, the ones that figured out how to close the frontline engagement gap first. [MangoApps employee engagement](/solutions/employee-engagement) is built for that challenge: mobile-first access, recognition systems that reach frontline workers without requiring company email, and communication infrastructure that functions across the full workforce rather than only the desk-based fraction of it. --- # Make Remote Work Easy With MangoApps **Author:** April Thomas **Published:** 2020-03-19 **Category:** integrated-digital-workplace COVID-19 has caused companies of every size to contemplate how social distancing can effectively happen within their organization. For many businesses, turning to remote work seemed like the obvious answer, but suddenly shifting to a remote setting is surprisingly easier said than done. In fact, in a recent poll, 91% of participating HR leaders cited […] # Make Remote Work Easy With MangoApps Remote and hybrid work is permanent — but for most organizations, the infrastructure supporting it still isn't. The evidence is in the usage data: per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and just 13% use one daily. The average time an employee spends using intranet tools like SharePoint is six minutes per day (per SWOOP Analytics). Meanwhile, employees lose an estimated **2.5 hours per day** searching for information they need to do their jobs (per IDC). These aren't engagement failures. They're design failures. When a platform requires a VPN or corporate email address, it works for headquarters employees and structurally excludes everyone else. When it broadcasts the same content to every employee regardless of role, location, or active projects, employees stop checking it. The six-minute daily usage figure isn't a mystery — it's the predictable result of tools built for a narrow slice of the workforce. The organizations making remote work actually function in 2026 aren't buying more tools. They're consolidating what they already have and extending genuine access to the workers they've historically left out. ## The missing 80% in most remote work strategies Per Emergence Capital, approximately **80% of the global workforce is deskless** — meaning the majority of employees worldwide don't sit at a computer during their workday. Frontline workers in healthcare, retail, logistics, and manufacturing are often the last to receive company communications and the first to disengage when the tools designed to reach them require desktop access or credentials they don't carry. The business consequences are measurable. Replacing a single frontline employee costs between **$4,400 and $15,000** on average. That range makes the retention value of keeping field workers connected a calculable operational cost, not a soft culture initiative. Organizations whose remote work tools create structural access barriers for frontline workers pay that cost repeatedly — in turnover, in onboarding, and in the institutional knowledge that leaves with every disengaged hire. MangoApps is designed to work on personal smartphones and tablets without requiring a corporate email address, VPN, or company-issued device. A warehouse associate, a retail floor employee, or a home health aide accesses the same company news, task assignments, and team conversations as any headquarters employee — from the device they already carry. That access architecture is what distinguishes platforms that claim frontline support from those that actually deliver it. ## What adoption looks like when the access barrier is removed Adoption numbers shift materially when a platform's access requirements match the actual conditions of the workforce rather than the ideal conditions of an office-centric deployment. The American College of Radiology needed communication to reach staff across roles, locations, and devices — including employees who didn't have traditional desk access or corporate devices. Rather than adding another tool to an already-fragmented communication stack, they deployed a unified employee app that gave every staff member a single place for company news, task assignments, and team coordination. The result was a measurable improvement in how quickly information reached employees, and how consistently staff engaged with it across the organization. The [full case study](/resources/case-study-american-college-radiology) covers implementation approach, rollout structure, and adoption outcomes. For a research-grade, independent view of how MangoApps compares against enterprise alternatives, [the 2026 intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides third-party analysis across the dimensions organizations typically evaluate when consolidating remote work infrastructure. ## Why adding tools makes remote work harder, not easier IT teams at mid-size and enterprise organizations typically manage 3–4x system redundancy across communication, file sharing, task management, and HR platforms. Every overlapping system adds a security review, a vendor relationship, an integration maintenance commitment, and a new place where employees might need to check for information. The fragmentation compounds over time. The 2.5-hour daily search burden (per IDC) is the downstream output of that fragmentation. Employees aren't slow at finding information — they're navigating four or five disconnected systems to locate something that should be in one place. That navigation cost is invisible on any single day and catastrophic in aggregate: at 2.5 hours per day, an employee loses the equivalent of three full months of working time per year to information search alone. Consolidating into a unified platform doesn't just reduce IT overhead — it changes the employee experience from one of constant tool-switching to one where the information needed is findable from the same place where messages arrive and tasks are assigned. That consolidation is the mechanism for moving intranet engagement from six minutes a day to habitual, meaningful use. ## The capabilities that move the needle for distributed teams Not every remote work feature produces equal returns. The capabilities with the highest leverage for distributed and frontline teams are those that directly address the three problems the research surfaces: too little relevant information, too many places to find it, and too much friction in the access path. **Targeted posts with read confirmation.** Company-wide broadcasts that don't require acknowledgment get scrolled past or missed entirely. Posts with a required-read setting create an audit trail at scale — managers and compliance teams see exactly who has and hasn't received a critical update, without sending a follow-up to the entire company. For healthcare, financial services, and other regulated environments, this is operational infrastructure, not an optional communication feature. **Group spaces organized by team, topic, or location.** Most communication defaults to org chart structure. But the questions employees need answered — and the conversations that move work forward — follow projects, regions, and specialties, not reporting lines. Group spaces give employees a coherent home for information relevant to them. Location-based groups extend this to geography: a regional manager pushes a policy update, a weather alert, or a shift coverage change to the right subset of employees automatically, without broadcasting it company-wide. **Integrated messaging, video, and screen sharing.** Remote employees lose the informal communication that resolves misunderstandings before they compound. When messaging, video chat, and screen sharing live in the same platform as file sharing and task management — rather than in a separate subscription — employees stop switching contexts for interactions that should take 30 seconds. For distributed teams onboarding new hires, screen sharing within the same environment as the task list reduces the back-and-forth that slows ramp time across time zones. **AI-driven content surfacing and notification prioritization.** The most common complaint about company intranets isn't that the content is wrong — it's that there's too much of it and none of it feels relevant. MangoApps uses AI to surface content based on role, location, group membership, and activity patterns, and to prioritize notifications so critical updates reach the right people without competing with noise. Personalized surfacing is the mechanism for moving engagement from the six-minute SWOOP Analytics benchmark toward habitual, daily use. **Searchable, version-controlled file access.** Files stored within a group, project, or company space are searchable and version-controlled — remote workers have the current version without chasing email attachments or second-guessing whether the document they found is still accurate. This directly addresses the information search time IDC quantified: when the document lives in the same environment as the task and the conversation, the search stops being a multi-system problem. **Multilingual communication.** MangoApps supports 50+ languages with real-time translation built in, enabling communication across globally distributed and multilingual workforces. For organizations with employees in multiple countries or regions, a company-wide announcement posted in English reaches a Spanish-speaking frontline worker in their preferred language without a manual translation step or a separate localized deployment. ## What IT and security teams need before approving a deployment For organizations in regulated industries, the security layer is audited before any platform reaches company-wide rollout. MangoApps supports SAML 2.0, OAuth 2.0, and single sign-on (SSO) — the authentication standards that healthcare, financial services, and government organizations require before approving a platform for enterprise deployment. These aren't differentiating features; they're the baseline that regulated industries treat as table stakes. Consolidating fragmented tools into a unified platform also reduces the security surface area: fewer vendor relationships, fewer integration points, fewer parallel systems to audit. Organizations managing 3–4x redundancy across their remote work stack can reduce that administrative overhead while simultaneously tightening the controls that matter in compliance-sensitive environments. The employee engagement software review process becomes simpler when there's one platform to evaluate rather than four overlapping ones. For organizations evaluating how a unified intranet platform fits their industry-specific security and communication requirements, the solution pages for [healthcare](/industries/healthcare) and [financial services](/industries/financial) cover the relevant compliance and workflow specifics. ## How to evaluate whether your current remote work stack is working The practical test isn't which features your current stack includes. It's whether the people who need those features can actually access them — and whether they do. If less than a third of your workforce logs into the company intranet regularly, the access design is the structural bottleneck. If frontline or field employees consistently report feeling out of the loop on company news, the delivery mechanism isn't reaching them. If your IT team manages more than two communication tools that partially overlap, the administrative burden is compounding with every integration and deployment decision. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how organizations across industries are restructuring distributed communication infrastructure — including what realistic consolidation timelines look like and where most rollouts stall before reaching full adoption. ## The bottom line Remote work doesn't fail because employees won't collaborate. It fails when the platforms organizations deploy require access conditions most of their workforce can't meet, serve generic content that employees have learned to ignore, and scatter information across enough separate systems that finding it costs more time than using it. The shift that produces measurable adoption — and measurable retention — is consolidation paired with genuine mobile access. When the same environment reaches a headquarters employee on a laptop and a frontline worker on a personal phone, when relevant content surfaces based on who that employee actually is, and when required-read audit trails are built in for compliance-sensitive communications — remote work stops being a coordination tax and starts functioning as designed. --- # A Modern Intranet: Engage Employees With Compelling Content **Author:** Anna Carriveau **Published:** 2020-03-17 **Category:** intranet Unlike their predecessors, modern intranets actually have the ability to centralize communication and collaboration across an organization. From document storing to instant messaging to project workspaces, intranets are truly the inclusive and intuitive tool every office needs. But even the best tools are only successful if used effectively. For a modern intranet to reach its […] ## A Modern Intranet: Engage Employees With Compelling Content Per Social Edge Consulting, 91% of organizations operate an intranet — and nearly a third of their employees have never logged in. Only 13% use one daily. Those numbers are not a content problem. They are a structural diagnosis: most intranets were designed for the fraction of the workforce that sits at a desk with a corporate laptop, and deployed with the expectation that everyone else would find their way in anyway. The gap between deploying an intranet and actually engaging employees through it has less to do with content quality than with three foundational decisions: who the platform was built to reach, whether the content delivery model creates relevance, and whether employees can respond rather than just receive. Get those three right, and intranet engagement becomes a measurable business outcome. Get them wrong, and no content calendar will close the gap. ## Why most intranets exclude the majority of the workforce before they launch Per Emergence Capital, 80% of the global workforce is deskless. Retail floor staff, hospital nurses, distribution center workers, field technicians — they do not have assigned laptops, corporate email addresses, or uninterrupted time at a desk to scroll through a feed. An intranet that requires any of those three things has structurally excluded most of the organization before a single piece of content goes live. The 13% daily utilization rate is not a ceiling. It is an artifact of who the platform was designed for. Organizations that have extended access to personal mobile devices — removing the requirement for a corporate email or a VPN connection — close that gap faster than any content refresh could. OU Health achieved 87% workforce engagement within a few months of launching a branded intranet app that frontline workers could access from their own phones. That result changes the economics of intranet investment. Replacing a single frontline employee costs between $4,400 and $15,000 when recruiting, onboarding, and lost productivity are fully accounted for. An intranet strategy that closes the utilization gap is a retention lever, not just a communications expense. A [modern intranet](/solutions/modern-intranet) architecture that reaches the full workforce — not just the desk-based 20% — is the precondition for everything else in this guide. ## The information cost of a broken content delivery model Per IDC, employees spend an average of 2.5 hours per day searching for information. Per SWOOP Analytics, the average employee spends just six minutes per day on intranet tools. The distance between those two figures is where intranet engagement strategies quietly collapse. Employees are efficient, not apathetic. If the intranet does not surface relevant information faster than a text message to a colleague or a quick search in a chat tool, employees default to those channels — and the intranet becomes a repository rather than a platform people choose. Low visit frequency is not a motivation problem; it is a signal that the content delivery model does not match the way employees actually work. Two structural fixes reduce that gap. Role- and location-targeted content delivery — posts scoped to specific teams rather than broadcast to the entire organization — ensures that employees who do log in see content relevant to their role rather than announcements aimed at someone else. AI-driven personalization surfaces the right content in each employee's feed without requiring them to remember which channels they subscribed to or navigate to each space manually. Governance matters here in a way that often goes unaddressed. Role-based content permissions ensure that sensitive information — HR policy updates, compliance documents, executive communications — reaches the right audiences without broadcasting to the full workforce. This is not a security checkbox; it is what makes employees trust the platform enough to return to it consistently. ## What content strategy looks like for the full workforce Solving access and delivery creates the foundation. What kind of content actually drives return visits is a different question — and the research here is consistent. The intranets employees return to daily share three properties: content is short and scannable, employees can respond rather than only read, and the platform surfaces contributions from peers, not only from administrators. Each of those properties requires a deliberate content strategy decision, not just a platform feature. Short content is a structural commitment to employees' time. The same IDC finding that employees lose 2.5 hours per day to information search means that intranet content must justify its place in an already-overloaded schedule. Clear headings, one idea per section, and no filler create a platform that signals it values attention — and that credibility compounds over time into habitual use. Two-way content is what separates an intranet from a broadcast channel. [Workspaces](/key-features/workspaces) that support comments, reactions, and threaded discussion — employee engagement surveys built directly into the platform rather than deployed as a separate email campaign — give employees a mechanism to contribute rather than only consume. When feedback is visible and generates a response, return frequency increases. When it disappears into a system employees suspect nobody reads, contribution stops. Peer-generated content is the engagement mechanism that administrator-only publishing cannot replicate. Interest-based communities, cross-team recognition channels, expertise-sharing threads for specific roles or locations — these are the content types that generate the behavioral signals (comments, reactions, return visits within 48 hours) that distinguish real engagement from nominal membership. ## How to govern intranet content without creating a bottleneck The risk in a well-designed content strategy is centralized ownership. When a single team controls all intranet publishing, content freshness depends entirely on that team's bandwidth — and the platform goes quiet the moment that team is stretched. Employees notice. Once they learn the intranet is not reliably current, the habit of checking it breaks — and it rarely reforms on its own. Effective governance distributes ownership without removing oversight. Department owners should be able to publish content to their own scoped spaces without requiring IT approval or a ticket queue. Templates and style guides keep content consistent without centralizing the work. A quarterly review process — identifying inactive spaces, consolidating duplicates, archiving content that has passed its useful life — keeps the platform navigable as it grows and prevents the sprawl that makes newer intranets feel just as cluttered as the legacy tools they replaced. Named owners per space, documented publishing cadences, and clear criteria for what gets archived are what distinguish a platform that maintains high utilization over time from one that launches well and then quietly deteriorates. ## How to measure whether intranet content strategy is working Enrollment counts and total page views are the metrics most intranet dashboards surface first. They are also the least useful signals available. An employee who logged in once during onboarding and never returned counts the same as one who visits daily — and the two situations require very different responses. Four metrics give a more honest picture: **Active visit rate**: What share of enrolled employees logged in at least once in the past 30 days? Below 40% for a platform with mixed access — desk-based and frontline employees — is a warning sign. Below 20% suggests the content model is not serving employees' needs regardless of platform quality. **Content contribution spread**: Is content being generated by employees across the organization, or by a handful of administrators? Platforms where 5% of users generate 95% of content have become read-only tools — and will follow the same adoption decline as the broadcast intranet they replaced. **Dwell time by content type**: Which formats — video, survey, discussion thread, structured article — generate more than 60 seconds of average time on page? These are the formats worth investing in. Which consistently generate less than 15 seconds? Cut them from the rotation rather than increasing publishing frequency to compensate. **Survey completion rate in-platform vs. email**: If surveys deployed through the intranet outperform identical surveys sent by email, the platform has crossed a meaningful threshold — employees trust it enough to act in it rather than treating it as a secondary channel to check when prompted externally. Setting baselines before launch and reviewing these metrics monthly creates the evidence base for sustained investment. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers measurement frameworks in more detail for communications teams building their first reporting cadence. ## The architecture question underneath every engagement problem Most intranet content guides answer "how do we publish more effectively?" The more productive question is "what would make an employee who currently ignores the intranet choose to come back tomorrow?" The answer is rarely better content. It is access (mobile, no corporate email required), relevance (role- and location-targeted rather than broadcast), and participation (feedback channels that generate a visible response). An intranet that delivers on those three things does not need to compete with email and chat for attention — it becomes the fastest path to information employees already need, and habits form around it naturally. For organizations evaluating platforms against these criteria, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarks across access model, personalization depth, and governance — the dimensions this guide argues matter most before any content strategy conversation begins. --- # Building A More Responsible Workforce With Technology **Author:** Anna Carriveau **Published:** 2020-03-10 **Category:** integrated-digital-workplace Technology in the last decade has redefined the working world. No matter your industry or profession, technology has undoubtedly influenced it in almost unimaginable ways. But with all of the improvements and progress made along the way, it isn’t often someone considers how technology can help companies build a more responsible workforce. In this article, […] # How Technology Builds a More Responsible Workforce Technology has changed how work gets done—but its most underappreciated effect is how it redistributes accountability. When employees can access information instantly, collaborate across locations, and stay connected to company culture through a unified platform, responsibility shifts from managers enforcing compliance to workers exercising genuine ownership. This article breaks down four specific mechanisms through which workplace technology builds a more responsible workforce, and addresses the practical questions organizations face when deploying it. --- ## Why Most Intranets Fail Before They Can Help Before exploring what technology *can* do, it's worth acknowledging a structural problem: most organizations already have an intranet and it isn't working. According to Social Edge Consulting, 91% of organizations operate an intranet—yet only 13% of employees use one daily, and nearly a third never log in at all. Six minutes per day is the average time employees spend using intranet tools, per SWOOP Analytics. Those numbers reveal a gap between deployment and adoption. A platform employees ignore cannot build accountability, surface knowledge, or foster culture. The sections below describe what changes when technology is designed around how employees actually work—including the 80% of the global workforce that is deskless and has no regular access to a desktop computer (per Emergence Capital). --- ## 1. Flexibility With Accountability: Remote and Frontline Workers Flexible work is often framed as a remote-office story, but that framing excludes the majority of workers. Retail associates, healthcare aides, logistics crews, and hospitality staff make up most of the global workforce and have historically been the *least* connected to company systems, policies, and culture. When organizations deploy mobile-first, no-email access tools, they extend the same accountability infrastructure to deskless workers that office employees take for granted: shift confirmations, policy acknowledgments, task completions, and direct communication with managers. This matters financially as well as operationally. Replacing a frontline employee costs between $4,400 and $15,000, making technology-driven retention a direct financial priority—not just a culture initiative (per industry benchmarks cited across MangoApps frontline workforce resources). Online collaboration tools give employers the assurance they need to enable effective remote work while also giving employees the autonomy to work within the flow of their lives. Reduced micromanagement correlates with higher engagement and loyalty—but that reduction only works when both sides trust the shared system. For a concrete example of what frontline adoption looks like in practice, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how organizations are closing the connectivity gap for non-desk workers. --- ## 2. Access to Information: The Hidden Productivity Problem Employees spend an average of 2.5 hours per day searching for information, according to IDC. Across a 250-person team, that is roughly 625 hours of lost productivity every single day—not from disengagement, but from friction. Document storage and retrieval technology addresses the most obvious layer of this problem: paper is gone, files are searchable, and sharing takes seconds. But the deeper issue is fragmentation. Employees lose over four hours per week switching between disconnected systems, meaning tool consolidation is as much a productivity lever as any single feature (per MangoApps tool-sprawl positioning research). When an employee has to check five platforms to find one policy document, the problem isn't any individual tool—it's the absence of a unified layer. A well-designed [intranet](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) functions as that unified layer: a single place where documents, announcements, training materials, and workflows coexist. When employees can find what they need without friction, they are more likely to use that information to solve problems independently—which is the behavioral definition of a responsible workforce. AI is beginning to accelerate this further. Rather than requiring employees to know where to look, AI-driven content surfacing delivers relevant information based on role, location, and recent activity. The result is that the right employee sees the right information at the right time—without a manager having to push it manually. --- ## 3. Transparency as an Organizational Obligation Responsibility flows in both directions. While much of this article addresses employee accountability, transparency is the dimension where *employers* are accountable. Employees cannot be expected to act in alignment with company values, priorities, or strategy if they don't have reliable access to that information. Technology removes the logistical excuses for opacity. Announcements, policy updates, leadership communications, and strategic context can reach every employee—desk-based or deskless—through a single channel. Organizations that use a unified intranet platform to share content consistently report stronger employee trust scores and lower voluntary turnover. For organizations managing complex or distributed workforces, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) outlines how communication strategy and platform design interact to drive transparency at scale. --- ## 4. Social Connection and Employee Engagement Employee engagement is not a soft metric. Disengaged employees cost organizations in absenteeism, turnover, and output quality. The challenge is that engagement cannot be mandated—it has to be cultivated through genuine connection to colleagues, purpose, and culture. Enterprise social networks embedded within a unified platform give employees a structured way to share ideas, recognize peers, ask questions, and participate in company culture without requiring a separate consumer app. This matters especially for multilingual workforces: modern platforms now support 50+ languages with real-time translation, making workforce inclusion a technical capability rather than a manual process (per MangoApps frontline workforce product documentation). The results when adoption succeeds are measurable. OU Health achieved 87% workforce engagement within a few months of launching a branded employee app. CVS reached 90% frontline adoption within the first six months of deployment. These outcomes are not accidental—they reflect platforms designed to meet employees where they are, rather than requiring employees to adapt to the platform. For organizations evaluating [employee engagement software](/solutions/employee-engagement), the distinction between a tool employees tolerate and one they actually use is the difference between those adoption numbers and the 13% daily-use figure cited at the top of this article. --- ## What Does a Responsible Workforce Actually Look Like? A responsible workforce is one where employees have the information, tools, and context to make good decisions without constant supervision. Technology enables that condition by: - Giving every employee—desk-based or deskless—access to the same information and communication channels - Reducing the friction of finding information so that using it becomes the default behavior - Creating transparency from leadership that makes alignment possible - Building social connection that makes employees want to stay and contribute None of these outcomes happen automatically. They require a platform designed for adoption, not just deployment—and an organizational commitment to using it consistently. --- ## Frequently Asked Questions ### How do you measure whether technology is actually building accountability? The most direct indicators are behavioral: intranet login rates, document acknowledgment completions, task closure rates, and participation in social or recognition features. Lagging indicators include voluntary turnover, absenteeism, and scores from an **employee engagement survey** or **employee engagement questionnaires** administered at regular intervals. If adoption metrics are low (recall: only 13% of employees use a typical intranet daily, per Social Edge Consulting), the platform design or change management process needs attention before accountability outcomes will improve. ### What's the difference between an intranet and an employee engagement platform? Traditionally, an intranet was a document repository with a news feed. An employee engagement platform adds social features, recognition tools, mobile access, task management, and analytics. The distinction is collapsing as vendors build unified platforms that handle both. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an independent evaluation of how current platforms compare across these dimensions. ### Does this apply to industries beyond office work? Yes—and arguably the need is greater in frontline industries. Retail, hospitality, healthcare, and logistics organizations face the highest turnover rates and the lowest historical investment in employee-facing technology. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how HR leaders in these sectors are prioritizing digital access for non-desk workers as a retention and compliance strategy. --- ## The Bottom Line Building a responsible workforce is not primarily a training or culture initiative—it is an infrastructure decision. When employees have reliable access to information, clear communication from leadership, tools that work on their device and in their language, and a social environment that makes work feel connected to something larger, responsible behavior follows naturally. The organizations that achieve this don't do it by deploying more tools. They do it by consolidating onto a platform that removes friction, reaches every worker, and gives both employees and managers the visibility they need to operate with confidence. To see how MangoApps approaches this as a unified platform—covering intranet, communications, engagement, and frontline access—[review the findings from MangoApps' inclusion in a leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) or explore how other organizations have put it into practice. --- # What is Team Collaboration? **Author:** Anna Carriveau **Published:** 2020-02-25 **Category:** team-collaboration What is team collaboration? Put simply, team collaboration is the combined efforts of multiple individuals to achieve a common set of goals and objectives. This means utilizing teammates talents and skills to accomplish a business objective. Nowadays, digital resources are enabling all kinds of unique teams across a company. This means that collaboration details can […] ## What is Team Collaboration? Team collaboration is the combined efforts of multiple individuals to achieve a common set of goals and objectives. This means utilizing teammates' talents and skills to accomplish a business objective. Digital resources are enabling all kinds of unique teams across a company, which means collaboration details can differ greatly from team to team. While the specific details might not be the same, successful team collaboration shares a few similar elements — and the organizations that get those elements right see measurable results. For example, 89% of frontline workers say they will stay with their companies if leaders listen to their feedback, per McKinsey research, making collaboration a direct driver of retention. One often-overlooked reality: frontline and deskless workers make up over 80% of the global workforce yet are systematically excluded from traditional collaboration tools that require corporate email or a desk. True team collaboration must reach every worker, not just those at a desk. ## Facilitate Open Communication The first step in encouraging a collaborative effort is to create a culture of open communication. No matter what kind of team you're working with, every member should feel comfortable enough to share ideas. The best collaboration is a combination of different ideas built on top of each other. So while one idea alone might not be the answer, it can help spark whatever will work. Trust, transparency, and active engagement are crucial in a collaborative team environment. Employee engagement strategies that prioritize open dialogue also reduce attrition. Replacing a single frontline employee costs between $4,400 and $15,000, making collaboration-driven retention a direct financial lever for operations-heavy organizations. Organizations in sectors like [healthcare](/industries/healthcare) and grocery retail have seen this play out directly — a unified communication hub contributed to a 26% reduction in employee turnover at Go North West after deployment. ## Enable Flexibility Every team is unique and needs something different in order to find its perfect balance. While it's important to take note of successful elements in previous team experiences, be flexible enough to embrace something different as well. For one group, working outside of the office might be beneficial, while another team finds inspiration in a traditional meeting room. Take the time to explore options, be open to suggestions, and find the perfect style to enhance and improve team collaboration. Flexibility also means meeting workers where they are — on a mobile device, in a different language, or on a non-traditional schedule. AI-assisted features like real-time translation across 50+ languages and smart scheduling tools make the flexibility principle executable rather than aspirational. Employees lose over 4 hours per week switching between disconnected collaboration systems, so consolidating communications, scheduling, and HR into one platform is what makes flexibility sustainable in practice. Consolidating fragmented tools into one collaboration hub can reduce the number of disconnected systems employees navigate daily from 6–8 apps down to one. For a practical look at how scheduling flexibility plays out on the ground, see [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling). ## Emphasize Transparency Collaboration is most effective when diverse teams combine their different skills to create something original and interesting. In order to make those differences meaningful, teams need to understand each other's unique skills. Team members need to respect each other's abilities and be willing to work together to accomplish a project or goal. Transparency also depends on information being findable. Per Gartner, 2023, 47% of workers struggle to find the information they need at least half the time — a gap that undermines even the most well-intentioned collaborative culture. Per McKinsey research, 81% of leading companies effectively use data and analytics tools to close exactly this kind of visibility gap. Employee engagement software that surfaces the right content to the right people — rather than burying it across 6–8 disconnected apps — is what turns transparency from a value into a practice. See how this works in action in the [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study). ## Encourage Positive Feedback Improving team collaboration depends on positive feedback from everyone involved. Employees need to be able to not only share their own thoughts, but also openly discuss potential questions, problems, or flaws they see in other ideas. When criticism and critiques do occur they should always be positive, uplifting, and informative. Feedback is designed to improve projects and should never be focused on any specific individuals. When people know that their idea will be scrutinized respectfully, teams can overcome potential setbacks and resolve issues before they even occur. Employee engagement surveys and employee engagement questionnaires are structured ways to capture this feedback at scale — giving leaders a consistent signal rather than relying on ad hoc conversations. For a broader view of how feedback loops connect to workforce outcomes, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers current benchmarks across industries. ## Improve Team Collaboration With MangoApps Team collaboration is a crucial element in today's highly competitive business environment. When teams are able to work together, harness differences, and create solutions, employees and organizations both naturally come out ahead. At MangoApps, we focus on making the principles above executable for every worker — including the frontline and deskless employees that legacy tools leave behind. Organizations like OU Health have reported 87% employee engagement rates, and the Kansas City Chiefs achieved 90% platform adoption after deploying a unified collaboration hub. To see our [employee communications solutions](/solutions/employee-communications) in action, contact us or schedule a personalized demo today. ## What Are the Biggest Barriers to Team Collaboration? Even teams that understand the principles above run into predictable obstacles. The most common barriers include: - **Tool fragmentation**: When employees navigate 6–8 disconnected apps daily, context is lost and collaboration slows. Per Gartner, 2023, nearly half of workers can't find the information they need at least half the time. - **Frontline exclusion**: Workers without corporate email or a dedicated desk are often locked out of the platforms their desk-based colleagues use. Frontline and deskless workers make up over 80% of the global workforce, yet most collaboration tools are not designed for them. - **Lack of psychological safety**: Open communication requires trust. Without it, employees self-censor, feedback loops break down, and the collaborative culture described above never takes hold. - **Unclear ownership**: When roles and responsibilities aren't visible to the whole team, duplication and gaps emerge. Teamwork management tools that assign and track tasks transparently reduce this friction. Addressing these barriers is often a prerequisite before the cultural elements — open communication, flexibility, transparency — can take hold. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading organizations are tackling these structural challenges. ## How Do You Measure Team Collaboration Success? Principle-based advice is only useful if you can tell whether it's working. Measurable indicators of healthy team collaboration include: - **Platform adoption rates**: High adoption (e.g., 90% at the Kansas City Chiefs) signals that employees are actually using the tools provided rather than reverting to email or informal workarounds. - **Employee engagement scores**: Regular employee engagement surveys and employee engagement questionnaires give HR and team leads a quantitative baseline. Per McKinsey research, 81% of leading companies use data and analytics tools to track these signals systematically. - **Turnover reduction**: A 26% reduction in employee turnover was reported after deploying a unified frontline communication hub at Go North West — a direct financial outcome tied to collaboration investment. - **Information findability**: Tracking how often employees report difficulty finding information (a benchmark: 47% struggle at least half the time, per Gartner, 2023) shows whether transparency improvements are landing. - **Time saved on tool-switching**: Employees who move from 6–8 apps to a single hub reclaim over 4 hours per week — a productivity metric that's straightforward to measure before and after a platform change. For teams building or refining their employee engagement training and development programs alongside collaboration initiatives, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) offers a practical framework for connecting the two. --- # What Are Employee Directories? **Author:** April Thomas **Published:** 2020-02-18 **Category:** modules-features An employee directory is exactly what it seems, a place to store, share, and access basic employee information. But how companies choose to organize and execute that information makes all the difference in the world. While employee directories themselves are certainly nothing new, the old fashioned method of paper packets and stacks of flashcards are […] # What Are Employee Directories? An employee directory is exactly what it seems — a place to store, share, and access basic employee information. But how companies choose to organize and execute that information makes all the difference in the world. While employee directories themselves are certainly nothing new, the old-fashioned method of paper packets and stacks of flashcards are thankfully no longer necessary. With modern, digital, and cloud-based capabilities available for organizations almost instantly, finding the right coworker or building a successful team is always easy. Per IDC, employees spend an average of 2.5 hours per day searching for information — a cost that a well-structured directory embedded in your [company intranet](/key-features/company-portal) can dramatically reduce. ## Available Everywhere Traditional paper or spreadsheet directories are difficult to navigate and only accessible at specific locations or if you happen to have a physical copy. If employees need to work from home, step out of the office, are frontline workers, or just can't find a physical copy, communicating across the company just isn't an option. Modern, cloud-based employee directories can be accessed anywhere you have internet access. Users can even download the latest version onto their device for offline viewing. Modern directories incorporate into your company intranet, making them centralized and available at any time. This matters especially for the deskless workforce. Per Emergence Capital, 80% of the global workforce is deskless — and modern employee directories eliminate the need for corporate email addresses, allowing frontline workers to log in and access profiles and communications on personal devices without a VPN. For organizations where replacing a single frontline employee costs between $4,400 and $15,000, directory-driven connection and retention are a measurable business priority. ## An Interactive Environment Modern employee directories aren't just lists of information. With digital interactive capabilities, workers can pull up company addresses, co-workers' phone numbers, emails, and all kinds of other interactive information right on their computer, phone, or another smart device. Contact information is simple to interact with as well, making it easy to stay in touch with other employees. The [MangoApps employee app](/solutions/employee-app) extends this interactivity to frontline and mobile workers who may never sit at a desk. ## Detailed Information In a nearly unlimited digital environment, directories no longer need to worry about saving space, enabling them to offer all kinds of detailed and engaging information. Employees can establish lasting friendships. With digital directories, every employee can have a descriptive profile page with personal biographies, work histories, hobbies, interests, and more. Detailed profile pages also act as an internal resume, helping supervisors create strong teams. Employee directory profiles embedded in a unified intranet can go further still — surfacing personalized content by role, location, and team, moving beyond static contact cards to dynamic, contextual employee pages that serve each worker the information most relevant to them. ## Synchronized Information One of the traditional employee directory's greatest weaknesses is its inability to stay updated. Even when information is readily available, it always seems to be incorrect or somehow outdated. The struggle to keep content correct is particularly challenging in companies with high turnover, seasonal workers, and quick promotions. Over time, information becomes increasingly outdated and trying to work around directory errors just isn't worth it. Modern employee directories overcome this issue by naturally integrating with company LDAP/AD, ensuring all information is automatically incorporated into the employee directory. Beyond LDAP/AD, HRIS integration can automatically sync employee roles, permissions, and profile data — keeping directories accurate even through org restructures and rapid onboarding. These integrations also automatically update changes, keeping information consistent across the company and up-to-date. Employees are able to manually change information as well, allowing details to stay current. Per Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in, and only 13% use intranet tools daily. Outdated, hard-to-navigate directories are a leading reason. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools, which means every second of friction in finding a colleague is friction the platform cannot afford. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) offers a detailed benchmark of how leading platforms address this engagement gap. ## Quick Employee Search Another problem of traditional directories is that it can be difficult to find information. Even if employee records are up-to-date, traditional employee directories are long, disorganized, or difficult to navigate. Trying to track down details takes time and is incredibly frustrating. Modern employee directories actively overcome this issue by developing an easy way to navigate search repositories. Quick employee search abilities use features like predictive text, advanced search, detailed filters, and saved favorites to get you the best results right away. Leading platforms now go further, using AI-powered people search to surface the right person in seconds — contrasting sharply with static keyword search in legacy tools. Rather than scrolling through alphabetical lists, employees can search by skill, project history, location, or department, and the directory returns ranked, contextual results. ## Security and Governance of Directory Data As employee directories become richer and more interconnected, security and governance matter more. Modern directory platforms support role-based permissions so that sensitive fields — compensation bands, personal contact details, HR notes — are visible only to authorized roles. Single sign-on via SAML 2.0 and OAuth 2.0 ensures that access is tied to verified identity, and data governance controls let administrators audit who has viewed or exported directory records. For organizations evaluating platforms, the [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides independent analysis of how enterprise intranet vendors handle security and compliance. ## MangoApps Employee directories don't have to be ineffective, outdated, or difficult to manage. With MangoApps, we help companies of every size establish effective resources tailored to their exact needs. The directory is not a standalone tool — it is one layer of a [unified modern intranet](/solutions/modern-intranet) that connects communications, HR self-service, and team collaboration in a single platform. To learn more about innovative new employee directories or to see MangoApps in action in your own organization, contact us or schedule a personalized demo today. **Schedule Demo** --- ## How Do I Choose the Right Employee Directory Software? When evaluating employee directory software, prioritize these criteria: - **Frontline and mobile access** — Does the platform support personal-device login without requiring a corporate email or VPN? Per Emergence Capital, 80% of the global workforce is deskless, so mobile-first access is not optional. - **HRIS and LDAP/AD integration** — Automatic sync with your HR system of record keeps profiles accurate through onboarding, promotions, and departures without manual intervention. - **AI-powered search** — Static alphabetical lists are insufficient for large organizations. Look for predictive search, skill-based filtering, and role-based result ranking. - **Security and governance** — Role-based permissions, SSO (SAML 2.0/OAuth 2.0), and audit logging protect sensitive employee data. - **Platform unification** — A directory embedded in a broader intranet and employee experience platform delivers more value than a point solution. Look for connections to communications, [department sites](/key-features/department-sites), and HR workflows. - **Adoption benchmarks** — Per Social Edge Consulting, only 13% of employees use intranet tools daily. Ask vendors for documented adoption rates; a 90% frontline adoption rate within six months is an achievable benchmark from large enterprise deployments. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading HR teams are rethinking directory and people-data strategy as part of broader workforce operations. ## How Do I Implement an Employee Directory? Implementation typically follows four stages: 1. **Audit existing data** — Export current employee records from your HRIS or spreadsheet and identify gaps: missing roles, outdated contact details, and employees without profile photos. 2. **Connect your identity provider** — Integrate with LDAP/AD or your HRIS so that new hires, role changes, and departures sync automatically from day one. 3. **Define profile fields and permissions** — Decide which fields are public (name, title, team, photo), which are role-restricted (personal phone, manager notes), and which employees can self-edit. 4. **Drive adoption** — Announce the directory through existing communication channels, embed it in your intranet home page, and train managers to reference it during onboarding. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) includes practical guidance on driving adoption of new intranet tools. For a real-world example of how a large organization rolled out a unified directory and communications platform, see [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology). ## What Is the Relationship Between an Employee Directory and an Intranet? An employee directory and an intranet are closely related but not the same thing. The intranet is the broader digital workplace — the platform that hosts news, policies, team workspaces, and tools. The employee directory is a core module within that platform, providing the people layer that makes everything else more useful. When a directory is embedded in a unified intranet rather than managed as a separate tool, employees can move from reading a company announcement directly to viewing the author's profile, messaging them, or joining their team workspace — all without leaving the platform. This integration is what separates modern employee experience platforms from legacy contact lists. Per Social Edge Consulting, nearly a third of employees never log in to the intranet at all; a rich, connected directory gives them a reason to. For a deeper look at how intranet strategy and employee experience intersect, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) is an independent benchmark worth reviewing before any platform decision. --- # Simplifying Local Government With Mobile Capabilities **Author:** April Thomas **Published:** 2020-02-11 **Category:** workplace-productivity Local government is incredibly important, and in many ways more influential on a day-to-day level than national policies and practices. However, working in the local arena can be time-consuming, frustrating, and even discouraging at times. Trying to tackle important regional issues without the tools or information you need can be extremely difficult. Fortunately, local government […] # Simplifying Local Government Operations With Mobile Capabilities Local government field teams — inspectors, public works crews, permit officers, and seasonal contractors — spend most of their workday away from a desk. That creates a specific operational problem: how do you keep distributed employees connected, informed, and productive when they rarely sit in front of a computer? The answer is a mobile-first approach to employee communications and operations management. This article explains the concrete benefits, the implementation steps, and what to look for when choosing a platform. Over 80% of the global workforce is deskless — the same population local government field teams belong to — making mobile-first access a baseline requirement, not a nice-to-have. Yet 47% of workers struggle to find necessary information at least half the time (Gartner, 2023). For a permit inspector in a rural township or a public works crew without reliable broadband, that gap has real consequences. --- ## Why Mobile Capabilities Matter for Local Government ### Keep Field Employees Connected Without Email or VPN Local governments rely heavily on part-time inspectors, seasonal staff, and contractors who often lack corporate email addresses or access to a VPN. A single mobile [employee communications platform](/solutions/employee-communications) can give these workers access to schedules, HR tools, forms, and team communications without requiring either. That is a decisive operational advantage over traditional intranet setups that assume every employee has a managed device and a network login. When employees spread across multiple sites can report findings, coordinate with peers, and escalate issues from a phone, important work is less likely to be duplicated and critical updates reach the right people faster. ### Access Operations Manuals and SOP Operations Documents On the Go Government work is document-heavy by design. Operations instructions, SOP operations checklists, permit forms, inspection templates, and compliance records all need to be accessible in the field. A mobile platform keeps these documents digital and searchable, eliminating the risk of lost paperwork or outdated printed copies circulating among crews. Critically, offline access for critical documents ensures field workers in areas with limited connectivity — common in rural local government — are never blocked from essential information. When a crew is working in a low-signal area, they can still pull up the operations manual they need without waiting for a connection to restore. 47% of workers struggle to find necessary information at least half the time (Gartner, 2023). For local government, where manual operations and paper-based filing are still common, that friction translates directly into slower service delivery and higher administrative costs. ### Cross-Department Teamwork Management Government projects rarely belong to a single department. A road resurfacing project might involve public works, traffic engineering, communications, and the mayor's office simultaneously. Effective teamwork management across these groups requires a shared space where members from any department can coordinate without relying on email chains or in-person meetings. A centralized [employee app](/solutions/employee-app) lets administrators create project groups with members drawn from any department, share updates in real time, and maintain a searchable record of decisions — all from a mobile device. ### Reduce Manual Operations and Save Budget Replacing paper-based processes and siloed systems with a single mobile hub reduced employee turnover by 26% in a frontline-heavy public-transit workforce (Joinblink / Go North West case study). That outcome matters for local government budget planners: replacing one frontline employee costs $4,400–$15,000 on average, giving municipalities a direct financial argument for investing in tools that improve retention. Digitizing the filing, storing, and retrieval process also reduces the staff hours spent on manual operations — time that can be redirected toward citizen-facing services. Improved productivity in back-office and field operations naturally reduces overtime costs and administrative overhead. --- ## What to Look for in a Mobile Employee Communications Platform Not every platform is built for the realities of local government work. When evaluating options, prioritize these capabilities: - **No-email, no-VPN onboarding** — Contractors and seasonal workers should be able to join and use the platform without a corporate email address or managed device. - **Offline document access** — Field teams in rural or low-connectivity areas need to retrieve operations instructions and SOP operations documents even without a live signal. - **Cross-department group workspaces** — The platform should support project groups that span departments, not just team-level channels. - **Digital forms and workflows** — Inspection reports, permit applications, and compliance checklists should be completable on a mobile device and automatically routed to the right reviewer. - **Employee communications training resources** — Adoption depends on training. Look for platforms that include onboarding guides and employee communications training materials built into the product. - **Analytics and reporting** — 81% of leading companies effectively use data and analytics tools (McKinsey research). Local government managers benefit from visibility into which communications are reaching field staff and which documents are being accessed. --- ## Getting Started: A 5-Step Implementation Checklist The following steps give local government IT and operations leaders a practical path from evaluation to full deployment. 1. **Audit current communication gaps.** Survey field employees and department heads to identify where information gets lost, delayed, or duplicated. Common pain points include outdated printed SOP operations documents, missed shift updates, and inaccessible HR forms. 2. **Map your workforce segments.** Identify which employee groups lack corporate email or VPN access — seasonal inspectors, contracted crews, part-time staff. These groups define the minimum access requirements your platform must meet. 3. **Select a mobile-first platform.** Prioritize platforms that offer offline access, no-email onboarding, and cross-department workspaces. Evaluate whether the vendor has experience with field-heavy or public-sector workforces. 4. **Digitize your highest-friction documents first.** Start with the operations manual sections and SOP operations checklists that field teams reference most often. Migrating these first delivers immediate, visible value and builds adoption momentum. 5. **Train staff and measure adoption.** Roll out employee communications training in phases, starting with department leads who can support their teams. Track login rates, document access frequency, and form completion rates to identify where additional support is needed. 89% of frontline workers will stay with their companies if leaders listen to their feedback (McKinsey research) — use early adoption data to surface and act on employee concerns before they become retention problems. --- ## Frequently Asked Questions ### Can a mobile platform work for employees without smartphones or reliable internet? Yes, with the right platform. Look for solutions that support offline access so documents and forms remain available without a live connection. Some platforms also support SMS-based notifications for employees who do not have smartphones, though feature access will be limited compared to a full app experience. ### How does a mobile employee app handle sensitive government data? Enterprise mobile platforms use role-based permissions, encrypted data storage, and audit logs to protect sensitive records. Administrators can control exactly which documents and communications each employee group can access, which is important for managing contractor access versus full-time staff access. ### What does implementation typically cost and how long does it take? Costs vary by organization size and feature requirements. Most mid-sized local governments (500–2,000 employees) can complete a phased rollout in 60–90 days. The budget case is straightforward: if replacing a single frontline employee costs $4,400–$15,000 on average, retaining even a small number of additional employees through better communication tools can offset platform costs in the first year. --- ## The Bottom Line Local government field operations have the same mobile access problem as any deskless workforce — but with the added complexity of contractors without corporate email, rural connectivity gaps, and strict document compliance requirements. A mobile employee communications platform that supports no-email onboarding, offline document access, and cross-department teamwork management directly addresses those constraints. The implementation path is straightforward: audit your communication gaps, map your workforce segments, digitize your highest-friction SOP operations documents, and train staff in phases. The financial case is equally clear — reduced turnover, lower administrative overhead, and faster service delivery justify the investment against any reasonable budget review. For a closer look at how MangoApps supports field-heavy workforces, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the operational patterns shaping deskless work this year. --- # 5 Must Have Communication Features For A Successful Start-Up **Author:** Anna Carriveau **Published:** 2020-01-28 **Category:** industry-insights Owning a business is never simple, especially during the start-up stage. From establishing a brand to staffing an office, a new business needs every advantage. Thankfully, increased business tools and technology have made accessing resources much easier for enterprising individuals. This article focuses on the different communication tools available to new organizations and which features […] # 5 Must-Have Communication Features for a Successful Start-Up Most start-up communication advice focuses on the wrong population. The five features that actually determine whether a team stays connected look nothing like the list that gets written for a 15-person office team with company-provisioned laptops. Per Emergence Capital, 80% of the global workforce is deskless — and most early-stage companies hire from that pool before they hire from any other. A retail operation, a field service team, a restaurant group, a healthcare provider — these organizations are building mixed workforces from the first hire. The tools commonly picked in year one tend not to account for that. Per Gartner's 2023 Digital Worker Survey, 47% of employees already struggle to find necessary information at least half the time — at established companies with IT departments and provisioned devices. Start-ups begin that number higher, not lower. The five features below are not ranked by sophistication. They are ranked by how directly each one determines whether a communication platform reaches the full workforce or only the 20% sitting at laptops. --- ## Mobile access that does not require a corporate email address The most consequential failure mode in early-stage communication platforms is access design. Most platforms assume every employee has a corporate email address, authenticates through SSO, and works on a company-provisioned device. For desk workers at established organizations, that is a reasonable assumption. For a start-up hiring hourly associates, field technicians, or shift-based workers, it creates an onboarding friction that effectively excludes those employees from day one. The practical form of this failure is invisible until it is costly: three weeks after a frontline hire, they are getting critical information by text from their manager — not through the official platform — because provisioning is still pending. That is not a compliance oversight. It is an access design problem that compounds every time a new hourly or field-based employee is onboarded. A platform designed for mobile-first, no-email access inverts this: employees authenticate by phone number or employee ID, access everything through a personal device, and are fully operational without IT setup. Organizations that deploy this way have documented 90% frontline adoption within the first six months — a benchmark that should appear in vendor evaluation criteria, not just sales decks. For start-ups where field access, shift coverage, and distributed coordination are daily realities, [a purpose-built employee app that supports deskless access](/solutions/employee-app) is a structural requirement before any other feature on this list matters. --- ## Security that earns client trust while protecting distributed operations Security concerns at start-ups run on two parallel tracks that are usually conflated but require separate answers. The first is operational: protecting file sharing and communication across a mix of personal and company-owned devices, without a dedicated IT team managing exceptions. Role-based access controls, end-to-end encryption, and audit logging address this track. These are baseline requirements, not differentiators — any platform under evaluation should clear them. The second is reputational. New clients in regulated industries — healthcare, financial services, grocery retail — are frequently asked to share sensitive information with vendors they do not yet know. A start-up's security posture is invisible to those clients unless it has been independently validated. Certifications like SOC 2 Type II, ISO 27001, HITRUST, and FedRAMP ATO provide that validation and directly shorten security questionnaire cycles with cautious enterprise buyers. For start-ups entering those markets, it is worth knowing which platforms have been evaluated against independent governance standards. [MangoApps' coverage of the Forrester Wave: Intranet Platforms, Q2 2024](/articles/mangoapps-2026-forrester-wave-intranet-platforms) documents how platforms are scored across security and governance dimensions — the kind of third-party reference that turns a security review conversation from a barrier into a brief. --- ## Collaboration tools that replace fragmentation rather than adding to it Most collaboration platforms claim to improve teamwork. The question that matters for a lean start-up team is more specific: does this platform reduce the number of systems employees navigate daily, or does it add one more? A single unified platform can replace six to eight disconnected tools employees would otherwise navigate — reducing context-switching and the communication delays that accumulate when project documentation lives in a shared drive, process manuals live in a separate wiki, and team messaging runs through a third tool. The Gartner finding that 47% of workers cannot find necessary information at least half the time is partly a search problem, but it is also a fragmentation problem. Consolidation addresses both. For early-stage teams writing operations documentation and SOP materials for the first time, having that content in one searchable place that everyone can access — including hourly staff who authenticated by phone number rather than corporate email — creates an operational advantage in the first weeks rather than eventually. Modern platforms also include AI-assisted features as standard: auto-scheduling, real-time translation across 50+ languages, and intelligent content curation that allow lean teams to operate with the coordination efficiency of much larger ones. These are present-day capabilities, not future roadmap items. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how start-ups and scaling organizations are structuring their collaboration stacks to avoid fragmentation from the outset — including benchmarks on tool consolidation timelines and adoption rates. --- ## Customization that survives the growth curve Start-ups face a specific pressure on platform flexibility that stable organizations do not. The company's structure, workflows, communication norms, and content are simultaneously being built and frequently changing. A platform that forces a start-up into a vendor's default template will become an obstacle within months of launch. Only 22% of company intranets currently deliver personalized content to employees, per the *State of the Digital Workplace & Modern Intranet, 2024*. That benchmark reflects how rarely platforms are actually configured to serve different roles and contexts — which means a genuinely customizable platform remains a differentiator, not a commodity. The practical test of customization for a start-up is straightforward: can the platform adapt its permission structures, content channels, and workflow configurations as departments and locations are added? Can it house operations documentation in a way that is equally accessible to an hourly associate on a personal device and a manager on a laptop? And can it scale from 15 employees to 150 without requiring reimplementation? That last question matters more than most first-time buyers anticipate. The migration cost of switching platforms mid-growth — in employee time, re-onboarding friction, and content migration — typically exceeds whatever savings came from starting with a cheaper, less flexible option. --- ## Employee engagement and the cost of not measuring it early Employee engagement takes on a different urgency at start-ups than at established organizations. Without the brand recognition, compensation scale, or benefits packages that retain people at large companies, early-stage teams depend on mission, culture, and the quality of daily experience. A communication platform that actively supports recognition, feedback, and leadership visibility directly shapes whether that experience is strong enough to retain people before they receive a better offer. Per McKinsey research, 89% of frontline workers will stay with their companies when leaders actively listen to their feedback. For a start-up where every departure disrupts operations and forces a costly replacement process, this is a direct financial calculation: replacing a single frontline employee costs between $4,400 and $15,000 on average. A team that loses 10 employees in year one to preventable disengagement absorbs $44,000 to $150,000 in overhead — on top of every other early-stage cost. The engagement features that prevent this are specific: peer-to-peer recognition tools (not just manager-to-employee), feedback mechanisms that surface dissatisfaction before it becomes a resignation, and analytics that give leadership visibility into whether communications are reaching employees. Per McKinsey, 81% of leading companies effectively use data and analytics to manage workforce performance — which means measurement is now a baseline operational expectation, not an advanced feature reserved for large HR teams. For practical guidance on building retention-focused engagement programs without a dedicated HR function, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers what early-stage and scaling organizations are actually implementing. --- ## How to sequence these five features by stage Not all five features carry equal weight at every point in a start-up's development. The constraint changes as the organization grows. **At founding (1–20 employees):** Mobile access and security are the non-negotiables. If the platform cannot reach every hire from day one — including hourly and field-based staff without corporate email — and cannot clear a security review from a regulated-industry client, the other features are irrelevant. Get access and security right first. **At early growth (20–100 employees):** Collaboration consolidation becomes the critical lever. At this stage, process documentation is being created for the first time, new hires are onboarding faster than individual training can cover, and multiple workstreams are running simultaneously. Fragmented tools compound all three problems. A unified platform that surfaces the right information to the right person — on any device — is the infrastructure that allows early growth to feel controlled rather than chaotic. **At scaling (100+ employees):** Customization and engagement carry the most weight. The people who joined for the mission are now receiving offers from larger companies with better-defined career paths. Your platform needs to give managers the visibility and tools to recognize and retain those employees before retention becomes an emergency. Two questions worth asking any vendor explicitly during evaluation: Can every employee on your team — including those without a corporate email address — onboard and use the platform from day one? And what is the documented deployment timeline for a team at your current size? Traditional enterprise deployments take three to six months before communication tools deliver reliable results. Platforms designed for frontline and deskless access typically reach meaningful adoption in weeks. The gap between those timelines matters for how quickly the platform starts earning back its cost. Getting communication infrastructure right early is not a premium consideration — it is how start-ups avoid rebuilding the same foundation twice. --- # What Is An Employee Social Network? **Author:** Anna Carriveau **Published:** 2020-01-21 **Category:** enterprise-social-networking From the Gutenberg Press to the cloud, technology, when used correctly, has always had a way of advancing and improving the working world. And with the advent of employee social networks, technology has made its mark once again. While personal social network platforms like Facebook, Twitter, and Instagram have been dominating the internet for over […] # What Is An Employee Social Network? From the Gutenberg Press to the cloud, technology has always had a way of advancing and improving the working world. And with the advent of employee social networks, technology has made its mark once again. While personal social network platforms like Facebook, Twitter, and Instagram have been dominating the internet for over a decade, the move for a private, employee-centered social network is still a relatively new experience. But just like how personal social networks have reshaped traditional forms of friendship, sharing, and overall communication, employee social networks are positively improving information sharing, employee relationships, and even work opportunities — and the business case for them is harder than ever to ignore. An employee social network is a private, enterprise-grade platform that gives employees a dedicated space to collaborate, share knowledge, and build relationships — without the noise or privacy risks of consumer social media. Per Social Edge Consulting, 91% of organizations already operate an intranet of some kind, yet nearly a third of employees never log in to it. The gap between having a tool and having one people actually use is exactly what a well-designed employee social network is built to close. ## Increased **Knowledge Management** Undocumented knowledge management has always been a bit of a struggle. Employees transfer to new positions and leave the company, leading to lost knowledge. As a result, future employees either struggle to access existing information or have to redo previous projects. The scale of this problem is significant: per IDC, employees spend an average of 2.5 hours per day searching for information — time that compounds into real productivity loss across an entire workforce. With employee social networks, knowledge management is no longer forgotten or lost in an unknown void of information. Social networks naturally document employee experiences from friendly collaboration conversations to straightforward document sharing. Modern platforms go further, using AI-driven content curation and universal search to surface the right knowledge instantly — directly addressing the 'lost knowledge' problem that static intranets have never fully solved. Everything is stored in one centralized area, available anywhere employees have [intranet](/articles/mangoapps-2026-forrester-wave-intranet-platforms) access. For a deeper look at how knowledge-sharing connects to workforce performance, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) offers useful benchmarks on what separates high-adoption platforms from shelf-ware. ## **More Connected Employees** Connecting with coworkers and creating positive work relationships is a fundamental factor in employee engagement. Flexible schedules, remote work, multiple offices, and telecommuting teams are all incredibly beneficial. However, they can make building authentic employee connections feel more difficult than ever — particularly for the 80% of the global workforce that is deskless and rarely sits behind a corporate computer, per Emergence Capital. Employee social networks can make interacting and engaging with coworkers incredibly easy regardless of location. Frontline employees can access an employee social network without a corporate email address, VPN, or a desk — on personal iOS or Android devices with offline support for critical content. When peers can form friendships, work is more engaging, enjoyable, and productive all around. Platforms that support real-time multilingual translation across 50+ languages remove a structural barrier to connection for global and distributed workforces — a capability that consumer social networks were never designed to provide. The retention stakes are real: replacing a disconnected frontline employee costs between $4,400 and $15,000, making the case for social connectivity a hard financial argument, not just a culture one. CVS demonstrated this concretely, achieving 90% frontline adoption within the first six months of deploying a modern [employee communications](/solutions/employee-communications) platform. ## An **Open and Inviting Culture** Workplace hierarchy can be a difficult balance in a traditional environment. Employees need to know their supervisors trust them, support their work, and appreciate their efforts. This needs to be done while still maintaining a respectful leadership style. Employee social networks help managers find this balance by creating an open and inviting communication environment. It becomes easy for leaders to follow ideas, see progress reports, facilitate discussions, and assign tasks without micromanaging employees. These social networks allow supervisors to participate with employees in an approachable environment, improving relationships across the entire team. One organization that put this into practice is Santee Cooper, whose branded internal network — explored in [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study) — demonstrates how a social intranet can bridge leadership and frontline employees across a geographically dispersed utility workforce. ## **Better Onboarding Experiences** Joining a new organization is always a bit of an intimidating experience. A new environment, company culture, work responsibilities, and so much more can make even the most prepared employee feel a little overwhelmed. While every job will always have its individual learning curve, employee social networks can greatly improve and shorten the overall onboarding experience. New employees can easily connect with coworkers to ask questions, make friends, and successfully integrate into the organization. These networks also store important files, documents, and data in easily accessible areas, helping new workers learn work processes and manage information quickly and completely. Employee engagement training and structured learning paths embedded in the social network accelerate this further — connecting new hires to the right people and the right content from day one rather than leaving them to navigate a fragmented set of tools. For context on how learning strategy fits into daily work, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) is worth reviewing alongside any onboarding redesign. ## **Enterprise Security: What Separates an Employee Social Network from Consumer Social Media** One of the most important distinctions between an employee social network and a consumer platform is governance. Enterprise-grade employee social networks are built on security frameworks that include SAML 2.0 single sign-on, role-based permissions, and data residency controls — keeping social collaboration compliant with internal IT policy and external regulatory requirements. Employees get the familiarity of a social feed; IT gets the auditability and access controls that consumer platforms cannot provide. This is not a minor feature distinction — it is the reason organizations in regulated industries such as [healthcare](/industries/healthcare) and [financial services](/industries/financial) can deploy social intranets at scale without creating compliance exposure. ## **Unified Platform vs. Standalone Social Tool** A common objection to employee social networks is that they risk becoming yet another application employees must check. That concern is valid when the social layer is a point solution bolted onto an existing stack. The answer is an employee social network embedded within a unified platform that combines communications, operations, and HR self-service in a single destination. When the social feed, task management, announcements, and employee engagement software all live in one place, adoption rises because employees have a reason to be there — not just for social interaction but for the work itself. One organization achieved 87% workforce engagement within a few months of launching a branded [employee app](/solutions/employee-app) built on this unified model. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools — a benchmark that reflects what happens when social and operational tools remain disconnected. A unified platform changes that equation by making the intranet the place where work actually happens. ## Case Study: Leveraging A Social Intranet Barut Hospitality Management, a Turkish organization with 6 resort hotel locations spread across Turkey, was looking for a social intranet that could connect their workforce and streamline communication and collaboration among their employees. In need of a solution to better equip their dispersed hotel employees, Barut Hospitality Management began their search for a social intranet that was user-friendly, could assist their compliance efforts, and could support their Turkish employees. Learn how Barut Hospitality Management was able to leverage a social intranet to transform the way that their employees collaborate and communicate. ## MangoApps Like other technology throughout the ages, employee social networks have come to improve and enhance the everyday work environment. At MangoApps, we take pride in helping companies craft innovative, inviting, and intuitive enterprise social networks designed around their unique strategies and styles. From collaborative workspaces to dedicated news feeds, you'll find everything employees need within MangoApps. To learn more, or to see how MangoApps can improve your own organization, contact us or schedule a personalized demo today. --- ## How Do You Implement an Employee Social Network? Implementation typically follows three phases: platform selection, configuration, and adoption. During platform selection, organizations should evaluate whether the social network is a standalone tool or embedded in a unified intranet and employee experience platform — because standalone tools tend to produce the low engagement benchmarks (six minutes per day, per SWOOP Analytics) that make leadership question the investment. Configuration involves setting up role-based permissions, integrating with existing identity providers via SSO, and building out the initial community structure — groups, channels, and knowledge bases — before launch. Adoption is where most implementations succeed or fail: organizations that pair launch with structured employee engagement training, executive participation, and clear use-case communication (not just 'here is a new tool') consistently outperform those that treat rollout as a technical event. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers adoption frameworks in detail and is a practical starting point for teams planning a rollout. ## What Should You Look for in an Employee Social Network Platform? Not all employee social networks are built for the same workforce. Key evaluation criteria include: mobile-first access without requiring a corporate email or VPN (critical for the 80% of the global workforce that is deskless, per Emergence Capital); multilingual support for distributed teams; enterprise security including SAML 2.0, SSO, and role-based permissions; AI-powered search and content surfacing to solve the knowledge-retrieval problem; and integration with HR, operations, and communications tools so the platform becomes a daily destination rather than an occasional check-in. Organizations in specific verticals — such as [grocery retail](/industries/grocery) or [ambulatory care](/industries/ambulatory-care) — should also evaluate whether the platform has demonstrated adoption in their industry, since frontline workforce dynamics vary significantly by sector. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides a useful framework for aligning platform capabilities to operational workforce needs. ## How Does an Employee Social Network Affect Employee Engagement Survey Results? Employee engagement survey scores and employee engagement questionnaire responses tend to improve when employees feel informed, connected, and heard — all outcomes that a well-adopted social network directly supports. The mechanism is straightforward: when employees can see leadership communicate transparently, participate in discussions, and access the information they need without spending 2.5 hours searching (per IDC), the drivers of disengagement — feeling out of the loop, disconnected from leadership, or unable to find help — are reduced. Per Social Edge Consulting, only 13% of employees use an intranet daily under current conditions; organizations that close that gap through a more engaging social layer see measurable shifts in the engagement indicators that show up in survey data. For the latest research on what is driving engagement and disengagement globally, [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace) is the most current benchmark available. --- # How Financial Firms Use Digital Project Spaces To Boost Client Relationships **Author:** Anna Carriveau **Published:** 2020-01-14 **Category:** integrated-digital-workplace For many businesses, managing finances can feel like an uncomfortable and unconquerable enigma. And while financial institutions have the experience and skill to support all kinds of organizations, turning your finances over to a stranger is almost as frightening as trying to manage them alone. Thankfully, modern communication and collaboration tools make working with financial […] # How Financial Firms Use Digital Project Spaces to Strengthen Client Relationships Financial advisory teams face a specific operational challenge: they must coordinate sensitive client work across distributed staff, manage compliance requirements, and respond quickly — all while using tools that were not designed to work together. According to Gartner's 2023 Digital Worker Survey, 47% of workers struggle to find necessary information at least half the time (per Gartner, 2023). For financial firms, that friction shows up directly in client response times and relationship quality. Digital project spaces address this by consolidating communication, file access, task tracking, and client collaboration into a single environment. This article covers five concrete ways financial firms use them — and answers the follow-up questions most teams have before committing to a platform. --- ## 1. Replacing Disconnected Tools With a Single Operational Hub Financial teams navigating six to eight disconnected tools daily experience compounding delays in client-facing work. Switching between a shared drive, an email thread, a compliance checklist, and a separate messaging app is a form of manual operations overhead that accumulates invisibly. Employees lose over four hours weekly switching between disconnected systems — a figure directly applicable to financial advisory teams managing multiple client workspaces. Replacing paper processes and siloed systems with a single digital hub reduces operational friction and accelerates client response times for service-oriented teams. A [shared digital workspace](/key-features/workspaces) gives every adviser, analyst, and client contact a single place to find current documents, active tasks, and recent decisions — without hunting across platforms. Only 22% of company intranets currently deliver personalized content to employees (per State of the Digital Workplace & Modern Intranet, 2024), which means most financial teams are still working around generic, one-size-fits-all tools. A purpose-configured project space changes that baseline. --- ## 2. Establishing Clear Accountability Across Advisory Teams Large clients often require a dedicated team of advisers with distinct responsibilities. Without structured teamwork management, tasks fall through the gaps between team members, and work gets duplicated when communication is unclear. Digital project spaces solve this through individual task assignments, shared to-do lists, and visible ownership. When every deliverable has a named owner and a due date, teams accomplish work faster and coordinators spend less time chasing status updates. [Task management tools](/solutions/task-management) let financial teams assign client deliverables, set deadlines, and track completion without a separate project management subscription. For firms that need to document repeatable processes — onboarding a new client, preparing a quarterly review, or running a compliance check — [trackers and workflows](/key-features/trackers-workflows) function as a living operations manual, replacing ad-hoc email chains with structured, auditable steps. --- ## 3. Giving Clients Meaningful Visibility Into Their Own Work Financial services are personal. No two clients have identical priorities, risk tolerances, or reporting preferences. Advisers who treat every engagement the same way produce generic outcomes. Digital project spaces allow financial organizations to invite clients directly into a dedicated workspace where they can review progress, ask questions, flag priorities, and see outcomes in real time. This level of detailed client involvement removes the information asymmetry that makes clients anxious — they no longer have to wait for a scheduled call to know where things stand. According to McKinsey research, 81% of leading companies effectively use data and analytics tools to inform decisions. Giving clients access to their own financial data and project status within a shared workspace is a practical application of that principle at the relationship level. --- ## 4. Supporting Distributed Teams With Mobile-First, Secure Access Financial advisers and their clients are increasingly mobile. A platform that requires VPN access or a corporate email address to retrieve a client file creates friction that slows down service delivery. Single-sign-on mobile access reduces friction for staff trying to access client files and compliance documents without requiring VPN or corporate email — a meaningful advantage for firms with remote advisers or field-based client service teams. Beyond convenience, security and compliance governance must be treated as a first-class requirement, not an afterthought. Financial firms operating under regulatory frameworks need role-based permissions, audit trails, and data residency controls built into the platform — not bolted on. Mentioning that a tool is "safe and secure" is not sufficient due diligence for a regulated industry. When evaluating any employee communications platform for financial services use, confirm that the vendor can document enterprise-grade access controls and compliance logging. 90% frontline adoption was achieved within the first six months of deploying a unified digital workspace in one large-scale deployment (CVS case study), which suggests that mobile-first, low-friction access is a primary driver of actual usage — not just a feature checkbox. --- ## 5. Organizing and Retrieving Financial Documents Without Manual Search Financial work is document-intensive. Contracts, statements, compliance filings, and client correspondence accumulate quickly, and the cost of not finding the right version of a file at the right moment is high. Even digitized, organizing and locating essential documents across shared drives and email attachments consumes significant time. Digital project spaces are designed to store, organize, and surface financial documents through structured search — including full-text search through PDFs and saved files. Combined with a [to-do list and task layer](/key-features/to-do-list), teams can link specific documents directly to the tasks that require them, so nothing is retrieved out of context. For firms looking to move away from manual operations and build repeatable, auditable document workflows, this capability is foundational. --- ## What Financial Firms Should Look for Before Choosing a Platform The five capabilities above are only useful if the platform is actually adopted. Two follow-up questions come up consistently when financial teams evaluate digital project spaces: **How quickly can a financial firm get a platform running?** Legacy intranet tools have historically required months of IT configuration before any adviser can use them. Modern platforms are designed for faster deployment, but financial firms should ask vendors for a concrete time-to-value benchmark — specifically, how long it takes to configure role-based permissions, onboard a client workspace, and train a team of advisers. Firms that have consolidated communications into a single hub have seen a 26% reduction in employee turnover (Go North West case study), which suggests that deployment speed affects not just IT timelines but retention outcomes. **How does this connect to broader employee communications and performance tracking?** Digital project spaces work best when they are part of a connected operations environment. For firms that want to tie client project outcomes to adviser performance, [goals management tools](/key-features/goals-management) provide a structured way to set, track, and review individual and team objectives alongside the work itself. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how organizations are connecting project-level work to company-wide communication strategies — relevant for financial firms managing both internal teams and external client relationships. **What about employee communications training for advisers new to digital workspaces?** Adoption depends on training. Financial firms introducing a digital project space should plan for structured employee communications training that covers not just the tool mechanics but the new norms around client visibility, document versioning, and task ownership. McKinsey research finds that 89% of frontline workers will stay with their companies if leaders listen to their feedback — which means the rollout process itself, including how advisers are trained and heard during onboarding, affects long-term retention. --- ## The Concrete Takeaway Digital project spaces give financial firms a structured way to manage client relationships, coordinate distributed advisory teams, and meet compliance requirements — without adding more tools to an already fragmented stack. The five capabilities covered here — unified operations, task accountability, client visibility, secure mobile access, and document organization — are not abstract benefits. Each one addresses a specific operational friction point that financial teams encounter in day-to-day client work. If your firm is evaluating platforms, start by auditing how many tools your advisers currently use to complete a single client deliverable. If the answer is more than three, consolidation will produce measurable time savings. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides a structured framework for that kind of operational audit across service-oriented teams. --- # How To Improve Team Potential **Author:** Anna Carriveau **Published:** 2019-12-30 **Category:** team-collaboration Feedback, especially in an office setting, has the potential to positively or negatively affect the entire environment. When feedback is delivered in a supportive way, it engages and empowers employees. However, harsh feedback can quickly cause resentment. This leaves employees feeling frustrated, discouraged, and searching for new employment. Maintaining positive feedback doesn’t mean that you […] # How to Improve Team Potential Through Feedback and Recognition Feedback shapes whether a team grows or stagnates. When it is delivered consistently, tied to specific behaviors, and reaches every employee — including those on the frontline — it becomes one of the most reliable levers for improving team potential. This article explains four concrete ways structured feedback and recognition programs raise team performance, along with the practical steps to make each one work. ## What Does "Improving Team Potential" Actually Require? Improving team potential is not simply a matter of encouraging managers to say "good job" more often. It requires a system: peer-to-peer recognition channels, mobile-accessible feedback for deskless workers, and recognition tied to specific behaviors rather than vague outcomes. Recognition programs that include peer-to-peer feedback reduce voluntary turnover more effectively than manager-driven praise alone (per rewards-and-recognition category research across competitor coverage). Structured recognition tied to specific behaviors — not just end results — produces measurably higher engagement scores than general praise, according to employee experience research including the British Airways case study cited by Unily. The four sections below address the most common gaps teams encounter when trying to build a feedback culture that actually sticks. --- ## 1. Unify Your Team Around Shared Recognition Teamwork breaks down when individual contributions go unseen. Positive team feedback helps coworkers recognize the value each member brings, including members they may be struggling to appreciate. When praise is visible to the whole group — not just delivered in a one-on-one conversation — it reinforces shared purpose and reduces the friction that slows collaboration. One structural change that accelerates this: moving recognition into a shared feed where peer kudos, manager praise, and milestone acknowledgments appear together. This makes recognition a repeatable system rather than an occasional gesture, and it gives quieter contributors the same visibility as high-profile performers. For teams that want to go deeper on building this kind of culture, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading organizations are structuring recognition programs at scale. --- ## 2. Recognize Hard Work in Ways That Reach Every Employee The benefit of team projects is that they draw on a wide range of skills — communication, coordination, prioritization, and domain expertise. Effective recognition should acknowledge the difficulty of that coordination, not just the final deliverable. However, recognition only works if it reaches the people it is meant for. According to Emergence Capital, 80% of the global workforce is deskless. Frontline and remote employees lack desk-based touchpoints, which means email-only or intranet-only recognition channels systematically exclude them. Mobile-accessible feedback and recognition — delivered via push notification and in-app alerts — is not a nice-to-have for distributed teams; it is the baseline for equitable engagement. Organizations that unify recognition and communication tools in a single app have reported 90% frontline adoption within the first six months. That adoption rate matters because recognition that employees never see produces no engagement benefit. See how one organization put this into practice: [From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program). --- ## 3. Use Feedback to Improve Performance — Not Just Morale Constructive feedback is the mechanism that aligns team behavior with expected outcomes. Unlike individual feedback, which can feel isolating or biased, team-level feedback addresses the group as a whole and invites collective problem-solving. Team members gain autonomy to decide together how to address gaps and find solutions, which increases ownership of the outcome. For feedback to improve performance consistently, it needs to be tied to specific, observable behaviors. "Great work this quarter" tells a team very little about what to repeat. "The way you coordinated handoffs between the design and engineering tracks cut the review cycle by two days" tells them exactly what worked and why it mattered. This behavioral specificity is also what separates [employee engagement](/solutions/employee-engagement) programs that move the needle from those that generate survey responses but no lasting change. Employee engagement surveys and employee engagement questionnaires are useful diagnostic tools, but the follow-through — structured feedback tied to what the data reveals — is where performance actually improves. Teams looking to connect feedback loops to formal development pathways will find practical frameworks in [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). Digitized feedback and training workflows replace manual processes and can reduce new-hire onboarding time by 50%, making the connection between recognition and development concrete from day one. --- ## 4. Build a Feedback Culture That Leaders Model First A positive feedback culture does not emerge on its own. It is modeled from the top. When leaders provide regular, specific, and encouraging feedback, they set the standard employees follow. Over time, supportive comments and constructive critique become part of how the team operates — not a special event triggered by performance reviews. This cultural shift has measurable downstream effects. Employee engagement, work satisfaction, and productivity all increase in environments where feedback is normalized and consistent. [Performance management](/solutions/performance-management) frameworks that embed feedback into daily workflows — rather than reserving it for annual reviews — make this normalization far easier to sustain. One structural barrier worth addressing: many organizations run intranets or communication platforms that employees rarely use. According to Social Edge Consulting, only 13% of employees use an intranet daily, and nearly a third never log in at all. SWOOP Analytics puts the average daily time spent using intranet tools at just six minutes. If your feedback and recognition channels live inside a platform employees avoid, the culture-building effort is undermined before it starts. Choosing an [employee experience platform](/solutions/employee-engagement) that employees actually open — because it surfaces personalized, role-relevant content — is a prerequisite for any of the cultural work above to land. --- ## Frequently Asked Questions ### How is team feedback different from individual performance reviews? Individual performance reviews assess a single employee's contributions and can feel high-stakes or isolating. Team feedback addresses the group as a whole, distributes accountability across members, and invites collective problem-solving. It is less likely to trigger defensiveness and more likely to produce shared commitment to improvement. ### What makes a recognition program reduce turnover rather than just boost morale temporarily? Recognition programs that reduce voluntary turnover typically share three characteristics: they include peer-to-peer channels (not just manager-to-employee praise), they tie recognition to specific behaviors employees can repeat, and they reach all employees — including frontline and remote workers — through mobile-accessible channels. Programs that rely solely on manager praise or annual awards tend to produce short-term morale bumps without changing retention patterns. ### How do you measure whether team feedback is actually improving engagement? Employee engagement surveys and employee engagement questionnaires provide a baseline. The more useful question is whether survey results are followed by visible, specific action — changed workflows, new recognition touchpoints, or adjusted team norms. Engagement scores improve when employees see that feedback leads to change, not just when they are asked to provide it. Tracking recognition frequency, peer kudos volume, and manager feedback cadence alongside survey scores gives a more complete picture than survey data alone. --- ## The Bottom Line Improving team potential through feedback requires four things working together: recognition that unifies the team around shared contributions, channels that reach every employee regardless of location or device, feedback tied to specific behaviors rather than vague outcomes, and leaders who model the culture they want to see. None of these elements works in isolation. For organizations ready to move from occasional praise to a structured, platform-enabled recognition program — one where peer kudos, manager feedback, and milestone tracking appear in a single personalized feed — MangoApps provides the infrastructure to make that system repeatable. To see how it works in practice, explore the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) or review [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace) for the broader workforce context behind these recommendations. --- # Turning A Negative Hotel Review Into A Positive Experience **Author:** Anna Carriveau **Published:** 2019-12-23 **Category:** industry-insights In today’s heavily customer-controlled market, hospitality industries are held to an incredible standard. With social media, online reviews, and hospitality recommendations all over the internet, unsatisfied customers have almost innumerable methods of sharing an unhappy experience. And customer reviews make a real difference. Studies have shown that over 85% of customers trust online reviews about […] # Turning a Negative Hotel Review Into a Positive Experience A two-star review is not a customer service problem. It is a training audit. When a guest posts about slow check-in, a room that smelled of smoke despite a non-smoking request, and no follow-up after flagging the issue in person, they are documenting three distinct points where your knowledge transfer broke down: a reservation flag that didn't reach housekeeping, an SOP that didn't cover room escalation under time pressure, and a shift handoff process with no written record. The guest didn't write a review. They wrote a failure report. Hotels that treat negative reviews this way — as evidence of internal process gaps rather than reputation emergencies — are the ones whose complaint volume actually declines over the following quarters. Per the Gartner 2023 Digital Worker Survey, 47% of workers struggle to find the information they need at least half the time. In hotel operations, that number shows up as a housekeeping team that never saw the non-smoking flag, or a front-desk agent who missed the departure note from the previous shift. This article covers how to close that gap systematically — not with a better public response template, but with the operational infrastructure that prevents the same review from appearing again six months later. ## The gap between "we responded" and "we fixed it" Most hospitality properties have a public response workflow. Someone monitors Google and TripAdvisor, there's a response template, and a manager gets notified when a review scores below three stars. What most don't have is a feedback loop connecting the public response to a documented internal change. The guest response — acknowledge the specific complaint by name, apologize without deflecting to staffing or seasonality, offer a concrete next step with a named contact — is visible work. It affects every future traveler who reads that thread. A specific, genuine response within 24 to 48 hours is significantly more likely to shift the reviewer's perception than one that arrives after a week of internal deliberation. But the public response is the beginning of the work, not the end. After it goes live, the question shifts from "what do we say to the guest" to "what broke internally that allowed this to happen." Those two questions require different owners, different timelines, and different processes. Properties that conflate them tend to produce good public responses and recurring operational failures. ## Why the same complaints keep reappearing The pattern behind most repeat complaints is information that didn't travel reliably across a multi-shift operation. A guest preference captured at booking but siloed in the reservation system. A service recovery flag documented by one manager that never entered a shared record visible to the next shift. In a hotel, information needs to reach housekeeping, front desk, food and beverage, and maintenance — across three shifts, with staff turnover among the highest of any industry. Verbal handoffs and printed shift sheets have a structurally high failure rate in that environment. The right information can only reach the right person if that person is in the right room at the right moment. In practice, they often aren't. Moving shift-critical information into a written, searchable, persistent record that every team member can access from a personal device removes that dependency. Over 80% of the global workforce is deskless, and hotel operations fall almost entirely into that category — housekeeping, food and beverage, overnight maintenance staff don't have corporate email addresses or company-issued computers. An [employee communications platform](/solutions/employee-communications) built for personal device access, without VPN or corporate email requirements, eliminates the access barrier that causes frontline teams to miss critical updates. Per a Unily benchmark from a large-scale frontline deployment, properties that moved from paper-and-email communication to structured mobile delivery achieved 90% staff adoption within six months. The question isn't whether your team can learn a new system. It's whether your current system is reliably reaching everyone who needs it before their shift starts. ## Negative reviews as employee engagement training audits This is where most training programs miss. Employee engagement training is typically calendar-driven: a quarterly classroom session, an annual compliance refresher, an onboarding module watched once and never revisited. None of those formats account for how hospitality SOP operations actually change — frequently, seasonally, in response to volume shifts, and often without a reliable mechanism to reach the 11pm maintenance crew or the weekend housekeeping team. When a guest posts about a service failure that a written SOP was designed to prevent, the most useful diagnostic question is not "did we train on this?" but "did the training reach the person who needed it, at the time they needed it, in a format they could actually use?" The answer is almost always no — not because the training doesn't exist, but because employee engagement courses built for classroom delivery don't transfer into high-turnover, multi-shift environments without a delivery mechanism designed for those environments. A short module on the updated complaint-handling procedure, delivered to a mobile device before a shift begins, converts training on employee engagement from an event that competes with operational work into a habit embedded in the shift itself. That is what an effective lms learning system delivers in a frontline hospitality context: not a classroom replacement, but knowledge at the moment of need. An [employee app](/solutions/employee-app) built for personal device access gives frontline staff the same access to policy updates, shift information, and learning content that desk-based employees get through an intranet. For hospitality specifically, this is how the policy-knowledge gap that generates service failures gets closed: not by holding more training sessions, but by making the right knowledge available to the right person before they walk onto the floor. For the structural patterns that separate employee engagement training programs that change behavior from those that look good on paper, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers where most programs break down at the operational level and what the effective design looks like. Replacing a single frontline hospitality employee costs between $4,400 and $15,000. The communication and coordination friction that erodes job satisfaction — "I never know what's going on," "I found out about the policy change at the start of my shift" — is one of the leading drivers of that turnover. Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback. The employee engagement survey that runs two weeks after a corrective training update — asking whether the team understood the new procedure and has what they need to follow it — is a retention mechanism, not an HR formality. ## Verifying that the fix is actually holding Four weeks after updating the housekeeping SOP for room-status flags and rolling out a written shift-handoff log, most properties face a practical problem: they assume the fix is working. Sometimes it is. Often it isn't — either because the updated procedure didn't reach everyone who needed it, or because the new behavior held for the first week and quietly reverted. Two mechanisms close this gap. **Employee engagement questionnaires** run two to four weeks after a corrective action, asking the relevant team whether they have the information, tools, and support they need to handle the specific situation. A housekeeping team that still reports uncertainty about room-flag escalation after a documented SOP update has a communication problem, not a compliance problem. The distinction matters because the interventions are different: a communication gap calls for a delivery fix; a compliance gap calls for a coaching conversation. **Review trend tracking** — monitoring whether the specific complaint category appears in new guest reviews over the following 60 to 90 days — is the accessible analytics layer available to every property regardless of size or technology stack. Per McKinsey research, 81% of leading companies effectively use data and analytics tools. At the property level, this doesn't require a data team: it requires someone checking whether non-smoking room complaints have decreased since the last SOP update, and documenting the finding in writing so the pattern is visible across multiple months. One organization that replaced scattered communications and paper processes with a single frontline communication hub documented a 26% reduction in employee turnover. That result compounded over months and was only measurable because someone tracked it. The same logic applies to review trends: the improvement is real, but it only becomes actionable data when someone connects the operational change to the outcome in writing. ## The 90-day proof loop Concrete timelines prevent the recovery process from becoming indefinite. Within 48 hours: the guest-facing response goes live and the internal team is briefed on the root cause in writing — a shared record, not a verbal summary at shift change. Within one week: the updated SOP or procedure is distributed through a channel where delivery can be confirmed, since email in a frontline environment has no reliable read receipts. At 30 days: a first check on review trend data — is the complaint category declining? At 30 to 45 days: a pulse survey with the relevant team — is the updated procedure understood and being followed? At 90 days: a second trend check and a written record of the outcome. If complaint rates in the category haven't declined after 90 days, the problem is either systemic — a process that needs to be redesigned, not just updated — or the information didn't reach the right employees, which is a communication infrastructure diagnosis. The two outcomes call for different interventions. The 90-day window makes it possible to tell them apart before another quarter of reviews makes the distinction for you. ## When the root cause is structural, not instructional Not every negative review points to a training gap. Some point to processes that are structurally broken: check-in queues too slow for the property's volume, room-status systems that weren't designed for high-occupancy compression, cancellation workflows that generate confusion regardless of how well staff understand the SOP. Individual errors, properly documented, cluster. When a specific complaint category appears across multiple reviews over multiple months, the root cause is almost certainly a process problem, not a knowledge problem. Non-smoking room misassignments that correlate specifically with high-occupancy nights are not a housekeeping training issue — they are a workflow escalation issue. An operations team that treats these as individual incidents rather than a pattern will keep updating the SOP without fixing the problem. The difference between a training fix and a process fix matters because training investment on a structurally broken process generates no improvement in outcomes. The review trend data and the pulse survey results are what tell you which problem you actually have. ## Building the compounding advantage Properties that close the feedback loop — diagnose the root cause, distribute the fix through a channel that actually reaches frontline staff, verify whether it's holding with employee engagement surveys and review trend data — build a compounding advantage in guest satisfaction that shows up in review trends within one quarter. The public response to the guest is visible. Every future reader of that thread sees it. But the fix to the internal process is what determines whether the same review appears again. Guests document failures. The operational infrastructure you build in response to that documentation is the thing that changes the outcome over time. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents how operations leaders are structuring these feedback and communication loops across frontline teams — including the benchmarks that predict service quality outcomes before they appear in guest reviews. --- # How Internal Communication Aids Employees In A Crisis **Author:** Anna Carriveau **Published:** 2019-12-17 **Category:** integrated-digital-workplace No matter how prepared your organization is, you’re bound to encounter a crisis at some point. From frantic deadlines to unexpected errors, businesses are sure to find themselves at an impasse at least occasionally. When last-minute changes, dangerous situations (such as a COVID-19), or any other kind of crisis occurs, it’s essential to have a […] # How Internal Communication Aids Employees In A Crisis No matter how prepared your organization is, you're bound to encounter a crisis at some point. From frantic deadlines to unexpected errors, businesses are sure to find themselves at an impasse at least occasionally. When last-minute changes, dangerous situations, or any other kind of crisis occurs, it's essential to have a reliable intranet or internal communication platform your workforce can count on. Per Social Edge Consulting, 91% of organizations already operate an intranet — yet nearly a third of employees never log in, which means the tool that should protect your people in an emergency may be going unused before one ever arrives. **Here are a few ways internal communication aids and enables employees in a crisis:** ## Prepare Employees Whether it's a company-wide alert or a small team update, employees can only react to a situation after being informed. With an internal communication system, you can easily broadcast news to staff members. Strong internal communication is an excellent resource for preparing employees ahead of time for a foreseeable rush like the end of a quarter or the start of an upcoming holiday season. With advanced warning and knowledge, employees will be much better prepared for any upcoming events. Preparation also means closing the information gap before a crisis hits. Per IDC, employees spend an average of 2.5 hours per day searching for information — time that compounds dangerously when speed matters most. A well-structured [employee communications](/solutions/employee-communications) platform reduces that search burden by centralizing policies, emergency procedures, and contact directories in one place. ## Alert Everyone While well-planned situations are ideal, sometimes hectic situations show up suddenly without warning. When unexpected situations occur, time is often of the essence. Being able to warn and strategize with coworkers can often make the difference between failure and success. A fragmented toolset — stitching together email, SMS, and separate chat apps — slows that response. A single unified platform enables the speed described here: one alert triggers push notifications, in-app messages, and SMS simultaneously, so no one waits for a forwarded email chain. Per Emergence Capital, 80% of the global workforce is deskless, meaning a large share of your employees have no corporate email address and no desk to return to. Organizations without a mobile-ready communication channel leave those frontline workers entirely unreachable during a crisis. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are closing this gap with mobile-first alert strategies. ## Diminish Danger Although you always hope to avoid dangerous situations, they can occasionally occur. In a potentially dangerous environment, all affected employees need to be notified as quickly as possible. With a safe and secure internal communication platform — one that enforces enterprise security standards such as SAML 2.0 single sign-on and role-based permissions — employees at risk can quickly be alerted without exposing sensitive operational data to the wrong audiences. This gives them time to assess any possible issues and make the necessary changes. Workers are also able to update each other about changes in unstable situations, check in with each other, or request additional assistance. For industries where physical safety is a daily concern, the stakes are especially high. Healthcare organizations, for example, rely on rapid, role-specific alerts to coordinate responses across departments — a use case explored in MangoApps' work with [healthcare](/industries/healthcare) and [ambulatory care](/industries/ambulatory-care) organizations. ## Establish A Plan No matter what created the initial crisis, every situation needs a plan in order to move forward and find a successful resolution. With an instant and accessible internal communication system, employees can easily share information, collaborate together, and begin to find answers and create action plans. Solutions can get started right away and everyone is already on the same page and easily able to contribute to the conversation. Fragmented tools make this harder than it needs to be. Employees lose over 4 hours weekly switching between disconnected systems — time that compounds during a crisis when speed matters most. A unified [employee app](/solutions/employee-app) keeps messaging, documents, and task coordination in a single interface, so teams spend their energy solving the problem rather than hunting for the right channel. ## MangoApps Reliable company communication is important for so much more than just team updates and regular news. At MangoApps, we know firsthand the difference a well-designed communication platform creates. Our mission is to empower organizations with the communication, collaboration, and information tools they need under any circumstance. MangoApps has been recognized in [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) and included in a [leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) — validations that matter when you're choosing a platform your workforce will depend on in a crisis. To learn more about internal communication or to see MangoApps at work in your own organization, contact us or schedule your own personalized demo today. --- ## What Types of Crises Require Internal Communication? Internal communication systems are tested across a wide range of scenarios — not just physical emergencies. The most common categories include: - **Operational crises:** System outages, supply chain disruptions, or sudden staffing shortfalls that require rapid redeployment of resources. - **Safety emergencies:** Workplace accidents, natural disasters, or public health events (such as a disease outbreak) where physical safety depends on immediate, accurate alerts. - **Reputational or regulatory events:** Data breaches, compliance failures, or media incidents where employees need consistent, approved messaging before they speak to customers or the public. - **Rapid business change:** Mergers, leadership transitions, or sudden policy shifts that create uncertainty and require clear, timely communication to prevent rumor and disengagement. Each type demands a different communication cadence — from a single broadcast alert to an ongoing thread of updates — which is why a flexible intranet platform matters more than a single-use notification tool. Poor communication during any of these events carries a real cost: replacing a frontline employee who leaves due to disconnection costs between $4,400 and $15,000, framing crisis communication as a retention issue, not just an operational one. ## How Fast Must Crisis Alerts Actually Be? Speed in crisis communication is not a vague aspiration — it has measurable thresholds. Push notifications and in-app alerts are specifically cited as the mechanism for reaching time-sensitive audiences during emergencies, not just email broadcasts. Email open rates drop sharply when recipients are away from a desk, and per SWOOP Analytics, employees spend an average of only six minutes per day using intranet tools — meaning passive content alone will not reach people in time. Effective crisis alert systems combine: - **Push notifications** to mobile devices for immediate visibility - **SMS fallback** for workers without smartphones or reliable data connections - **In-app acknowledgment** so managers can confirm who has received and read the alert - **Escalation rules** that automatically re-notify unacknowledged recipients For organizations in fast-moving sectors like grocery retail, where shift workers may be mid-floor with no desk access, this layered approach is the difference between a coordinated response and a chaotic one. The [Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) illustrates how frontline communication speed translates directly to operational outcomes. ## What Communication Channels Work Best During a Crisis? No single channel reaches every employee in every situation. The most effective crisis communication strategies layer channels based on urgency and audience: - **Mobile-first alerts** for deskless and frontline workers who represent, per Emergence Capital, 80% of the global workforce - **Intranet news feeds and pinned announcements** for employees who do have desk access and need context beyond a short alert - **Group messaging and threaded discussions** for teams that need to coordinate a response in real time - **Manager cascade communications** for organizations with unionized or distributed workforces where direct broadcast may not be appropriate — a dynamic explored in depth in [Managing a Unionized Workforce Is Different. Your Software Should Be Too.](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) The definition of an effective intranet in a crisis context is not simply a document repository — it is the connective layer that ties all of these channels together under a single login, with role-based permissions ensuring the right message reaches the right people without exposing sensitive information to the wrong ones. Per Social Edge Consulting, only 13% of employees use an intranet daily under normal conditions; a crisis is precisely the moment that number must approach 100%, which means the platform must be intuitive enough to use under pressure, on any device, without training. --- # 5 Ways Increased Communication Can Streamline Construction Projects **Author:** Anna Carriveau **Published:** 2019-12-10 **Category:** workplace-productivity To streamline construction, you need to have a truly collaborative experience. From the client or organization in need of the structure, the construction company in charge of operations, individual independent contractors, local government rules and regulations, and even pedestrian or local citizen support, it takes a lot of communication and coordination to get a project […] ## 5 Ways Increased Communication Can Streamline Construction Projects To streamline construction, you need a truly collaborative experience. From the client or organization commissioning the structure, to the construction company managing operations, independent contractors, local government regulations, and even community stakeholders — it takes disciplined communication and coordination to get a project completed on time and on spec. Per Gartner, 2023, 47% of workers struggle to find necessary information at least half the time, a problem that hits construction teams especially hard when workers are spread across a noisy, fast-moving job site. Below are five ways that increased communication can streamline construction — and what it takes to actually execute each one. ## 5 Ways To Streamline Construction Projects: ### Create A Centralized Space Construction work depends on a lot of factors, and no two projects are ever exactly the same. Inclement weather, local events, the time of year, and the location of the project all change how work needs to be handled. Depending on the time of day work is done or the worksite's physical location, getting important information out right away isn't always easy. Construction workers need a simplified way to coordinate quickly with supervisors, foremen, and coworkers about workplace changes, unexpected issues, and immediate concerns. In order to be effective, this method of communication also needs to work well within the construction environment of irregular hours, loud and potentially dangerous equipment, and workers spread out across the site. Over 80% of the global workforce is deskless, which means a mobile-first approach isn't optional — it's the baseline. A practical centralized hub lets workers access shifts, forms, training, HR self-service, and compliance tools in one app without requiring a corporate email address or VPN, matching how frontline workers actually operate. Push notifications and SMS alerts ensure time-sensitive communications — weather delays, safety warnings, last-minute schedule changes — reach every worker immediately, regardless of where they are on site. Offline access for critical documents and compliance checklists ensures workers in low-connectivity job sites are never blocked from safety information. With a mobile-friendly, always-available [employee communications platform](/solutions/employee-communications), collaborating and communicating effectively becomes straightforward even in the most demanding site conditions. ### Enable Complete Compliance In construction, cutting corners is absolutely unthinkable. The safety, structural integrity, and functionality of a project depend on dedicated compliance to every rule and regulation. When mistakes or missteps occur the results can be dangerous or even detrimental. By creating a detailed checklist all employees are able to easily see and interact with, supervisors can quickly update new requirements and coworkers can remain aware of important changes, processes, or compliance concerns. Digitizing standard operating procedures (SOP operations) into a shared, searchable platform means the most current version of every checklist is always the one workers see — eliminating the version-control failures that paper binders create. When compliance requirements change mid-project, push notifications can alert the entire crew instantly rather than relying on a supervisor to cascade the update manually. ### Simplify Training And Development Construction is a complicated industry and work tools, building materials, and even structure styles are always changing. Construction employees need to know how to operate and effectively work with each new component as soon as possible. But finding time to train every employee is incredibly time-consuming. With a centralized communication and collaboration platform that includes a built-in LMS learning system, effectively teaching and informing employees becomes far more manageable. Managers can upload specific employee engagement courses, product instructions, certification requirements, and even lessons and quizzes. This uniformity gives every employee a similar learning experience, without taking time away from important work. Employees can instead learn and certify themselves at the most convenient opportunity — on a lunch break, between shifts, or during transit to the next site. Positioning training and employee engagement together inside the same platform — rather than routing workers to a separate system — removes friction and drives completion rates. For a deeper look at how to embed learning into daily workflows rather than treating it as a separate event, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) also covers how leading organizations are integrating on-demand learning with frontline operations. ### Offer Feedback And Recognition Employees need consistent feedback in order to thrive in the workplace. This support shows workers that their managers are aware of them, acknowledge their efforts, and care about their long-term success. Offering support and employee engagement in construction can be difficult given the physical separation of crews and the pace of site work. The stakes are real: per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback. Replacing a single frontline employee costs between $4,400 and $15,000 when accounting for recruiting, onboarding, and lost productivity — making recognition not just a culture initiative but a direct cost-control lever. Find a way to communicate praise to employees, preferably in a public setting where coworkers can see and contribute as well. As you increase encouraging communication, workers will become more dedicated and devoted to their tasks. This helps employees work more efficiently and improve the overall work environment. Employee engagement software that surfaces recognition feeds, pulse surveys, and employee engagement questionnaires in the same app workers already use for scheduling and compliance removes the barrier of adoption. The [Break The Annual Review Cycle](/resources/break-the-annual-review-cycle) guide offers a practical framework for building continuous feedback loops that work for field-based teams. ### Encourage A Social Environment In addition to praise and acceptance, construction workers also need friendship and camaraderie for success. With varying work schedules and environments, finding that friendship can be difficult. Give employees a place to communicate together, connect, and establish a social sphere. When employees have a place to meet up, share stories, and build positive relationships, they become more engaged and interested in their organization. Work is no longer just a place to earn an income, but a productive environment where they want to be. Replacing paper processes and siloed systems with a single mobile hub has been shown to reduce employee turnover by 26% for frontline-heavy operators (per Joinblink frontline case study data). A social layer built into the same [employee app](/solutions/employee-app) workers use every day — rather than a separate consumer platform — keeps engagement within the organization's communication ecosystem and gives leadership visibility into team sentiment. ## Streamline Construction With MangoApps Construction is a complicated and intricate process, relying on effective team collaboration and communication. The five areas above — centralized mobile access, compliance management, integrated training on employee engagement, structured recognition, and social connection — are not abstract ideals. Each one maps to a concrete capability: push and SMS alerts for site communications, digital SOP operations checklists, a built-in LMS learning system for employee engagement courses, recognition feeds with employee engagement survey tools, and social channels that build crew cohesion. Organizations that execute across all five areas close the loop on the most common reasons construction projects stall: information gaps, compliance failures, undertrained crews, and high turnover. Per McKinsey research, 81% of leading companies effectively use data and analytics tools to measure and improve these outcomes — meaning the investment in communication infrastructure pays back in measurable project performance, not just employee satisfaction scores. At MangoApps, our tools are designed to make that happen for construction teams — without requiring workers to have a corporate email address, navigate a VPN, or switch between multiple apps. To learn more about how MangoApps works with construction companies, contact us or schedule a personalized demo today. ## What Tools Actually Enable This in Construction? The five strategies above require a platform built for frontline realities, not office workers. Key capabilities to look for include: mobile-first access with no email or VPN requirement, offline document availability for low-connectivity sites, push and SMS notification channels for safety-critical alerts, a built-in LMS learning system for employee engagement courses and certifications, digital compliance checklists with version control, and recognition and employee engagement survey tools accessible from the same interface. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) outlines how organizations are evaluating and deploying these capabilities in 2026. ## How Do You Measure the Impact of Better Construction Communication? Measurement starts with baselines. Before deploying a centralized platform, track: average time to distribute a compliance update site-wide, training completion rates per crew, voluntary turnover among frontline workers, and incident rates tied to information gaps. After rollout, 90% frontline adoption within the first six months is an achievable benchmark for mobile communication platforms in field-heavy industries. Employee engagement questionnaires and pulse surveys built into the platform give supervisors a continuous read on crew sentiment without requiring separate tooling. Per Gartner, 2023, reducing the 47% of workers who struggle to find information at least half the time is itself a measurable leading indicator of project efficiency. ## What About Managing Compliance Across Multiple Sites or Crews? Multi-site construction operations face a compounded version of every challenge described above: compliance requirements may vary by jurisdiction, crews rotate between projects, and supervisors cannot physically be everywhere at once. A platform that supports role-based content targeting — so a crew in one jurisdiction sees the applicable local SOP operations checklist, not a generic one — is essential at scale. For organizations managing unionized crews, communication protocols add another layer of complexity; [Managing a Unionized Workforce Is Different. Your Software Should Be Too](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) covers how to navigate those requirements without creating compliance exposure. --- # How To Enhance Your Intranet Security **Author:** Anna Carriveau **Published:** 2019-12-03 **Category:** intranet Intranets are an essential element in any modern business organization. They unify employees, connect resources, and simplify sharing of every kind. However, these benefits don’t come without additional concerns. While an intranet is a communication and collaboration advantage, organizations often worry about their security. We’ve found that with a little forethought, your company intranet should […] Most intranet security frameworks were written for one type of employee: the desk-based worker with a corporate laptop, a managed device, a company email address, and a VPN connection. These frameworks advise password policies, encryption requirements, and access control configurations that assume every employee arrives at a workstation, opens a browser, and logs into a corporate network before starting the day. Per Emergence Capital, 80% of the global workforce is deskless. The distribution center worker checking inventory on a personal phone, the retail associate reviewing the day's task list between customers, the healthcare technician pulling a procedure protocol from the break room — none of these employees match the model that most intranet security guidance was designed for. When your security architecture doesn't account for them, the choice your organization faces is binary: expose frontline workers to an inadequately governed experience, or exclude them from the intranet altogether. Neither is acceptable. Per IDC research, employees spend an average of 2.5 hours per day searching for information — a cost that compounds when security friction makes your intranet harder to use than a text message chain. When access errors, permission mismatches, or VPN requirements that personal devices can't satisfy become routine, adoption collapses. Per SWOOP Analytics, the average employee already spends only six minutes per day using intranet tools; a security design that adds friction to that six minutes drives it closer to zero. Intranet security designed for your full workforce closes the adoption gap rather than creating one. The five architectural decisions below are where that gap opens — or closes. ## Start with identity, not passwords The foundation of intranet security is not a password policy. It is identity infrastructure: the mechanism by which the system knows who a person is, what role they hold, and what they are authorized to access before they ever reach a login screen. Your intranet should support SAML 2.0, OAuth 2.0, Active Directory, and LDAP to enforce identity-based access control at the SSO layer. The practical consequence is significant: when an employee changes roles, leaves your organization, or transfers to a different department, access updates automatically across every connected system. There is no list of individual documents to manually re-permission. There is no gap between when an access change is requested and when it takes effect across all integrated tools. Password-only policies — even strong ones — cannot provide this. They require manual administration at every transition point, create audit gaps that grow with organizational complexity, and depend on individual employees to maintain hygiene across an expanding set of tools. At a 500-person organization managing a dozen integrated systems, the overhead of manual credential management is significant. At a 5,000-person organization with distributed teams and high frontline turnover, it becomes unmanageable. Identity infrastructure managed at the SSO layer is the control plane that makes every other security decision in this list enforceable at scale. ## Design permissions around roles, not documents Document-level access controls are better than no access controls — but they require continuous manual maintenance as content accumulates, roles evolve, and employees move through your organization. An access control strategy that works when your intranet has 500 documents and 200 employees typically breaks down when those numbers reach 10,000 and 2,000. Role-based permissions enforced at the intranet layer resolve this scaling problem. An employee who moves from a store associate role to a department manager role sees different content automatically — not because an administrator manually adjusted individual document permissions, but because their role changed and the permission model updated to reflect it. This architecture matters most for sensitive content: payroll information, compliance documentation, personnel records, and executive communications that have different intended audiences across your organization. When permissions are role-based and centrally administered, every access decision has a legible audit trail. MangoApps' [company portal](/key-features/company-portal) and department sites are built around this model, allowing administrators to scope content access precisely to roles and teams without maintaining document-level exceptions for each content update. Privilege creep — where employees accumulate access they no longer need as they move through roles — is one of the most common and underreported security vulnerabilities in large organizations. Role-based permissions address it structurally rather than requiring periodic manual audits to catch it. ## Extend your security model to frontline workers Per Social Edge Consulting, 13% of employees use their intranet daily — and nearly a third never log in at all. Low adoption and weak security often share the same root cause: the security model was designed for the 20% of the workforce at a desk, not the 80% working in the field. Frontline workers — in distribution centers, retail locations, hospital floors, and manufacturing facilities — typically access workplace tools on personal mobile devices. They may not have a company email address. They almost certainly lack a VPN connection. A security model that requires corporate email for account creation or a VPN for network access has already excluded a significant share of your workforce before the first login attempt. A mobile-first security model enforces the same role-based permissions and SSO controls on personal devices as on managed desktops. It supports device-level authentication — biometrics, PIN — without requiring a managed device as a prerequisite. It does not create a reduced experience for frontline workers; it applies the same permission architecture across device types, so a warehouse associate and a corporate manager operate under the same governance model, not parallel systems with different security standards. Standard operating procedures for digital safety — how to recognize a phishing attempt, how to handle sensitive content, what to do when something looks wrong — should be documented, version-controlled, and searchable inside your intranet, not distributed as email attachments that workers without company email may never receive. Embedding security expectations into daily workflows is more effective than one-time training, and it addresses the reality that most security incidents trace back to employees who didn't know the rule, not employees who chose to break it. ## Verify encryption — don't assume it Encryption is table stakes. TLS 1.2 or higher for data in transit, strong encryption for data at rest — these are baseline requirements, not differentiators. The question worth asking in any platform evaluation is not whether a vendor claims to encrypt data. It is whether the vendor publishes its encryption standards, undergoes independent third-party security audits, and can produce documentation to support an enterprise security review. Self-reported compliance and independently verified compliance are not the same thing. The distinction surfaces when your organization needs to document its security posture for a board, a regulator, or a procurement review. Vendors whose security posture can only be described in marketing language — without audited evidence — create documentation gaps that enterprise IT and legal teams typically discover at the worst possible moment. [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) evaluates leading platforms on security architecture using an independent framework that enterprise buyers can apply directly to platform selection decisions. It is a more useful benchmarking tool than vendor-produced comparison matrices when your security review requires third-party substantiation. ## Govern integrations through a single control plane Each integration point in your technology stack is a potential security surface. An HR system connected through a proprietary API, a document management platform with its own authentication model, a task tool adopted independently by two teams — each operates outside your intranet's SSO layer unless actively governed. And each one that operates outside the SSO layer creates a gap where access changes don't propagate automatically, audit trails break, and ungoverned data sits between systems. Your intranet security posture weakens when your organization manages 3–4x more systems than necessary, multiplying integration points that each represent a potential vulnerability. The counter to tool sprawl is not fewer integrations — it is governed integrations. When enterprise systems connect through a unified permission and SSO layer, each connected tool inherits the same access controls rather than introducing a new security surface. Administrators can review and revoke integration access from one place, reducing the operational overhead of maintaining a distributed technology stack. Tool consolidation through a governed intranet layer also reduces the attack surface that external threats can probe. An organization with 40 integrated systems — each with its own authentication handshake — presents a fundamentally different exposure profile than one where those 40 systems authenticate through a single identity layer with unified audit logging. ## A security architecture employees will actually trust Per Social Edge Consulting, 91% of organizations operate an intranet. The adoption data consistently shows that most employees route around the platforms their organizations have built — a pattern that reflects, in part, how often security architecture creates friction for the employees it was designed to protect. The organizations that close this gap share a consistent design approach: security is built into the foundation, not layered on afterward. Identity is managed centrally at the SSO layer. Permissions are role-based and automatically maintained. The security model accounts for frontline workers on personal devices, not just desk-based employees on managed hardware. Integrations are governed through a unified control plane, and every connected system inherits the same access controls rather than maintaining its own. The outcome is not just a more secure intranet — it is an intranet that employees trust enough to open. And every hour of search time recovered through a trusted, well-adopted platform represents measurable productivity returned to your organization without additional headcount or tooling. MangoApps is recognized for this architectural approach in the [Forrester Wave assessment of intranet platforms](/articles/mangoapps-2026-forrester-wave-intranet-platforms). For organizations actively evaluating platforms, the [modern intranet](/solutions/modern-intranet) security model — covering identity, frontline access, and integration governance — is documented in detail for enterprise security and procurement reviews. --- # Bridging The Gap In Customer Communication **Author:** Anna Carriveau **Published:** 2019-11-12 **Category:** industry-insights Professional services handle customers from all kinds of areas and industries, most of whom have little first-hand experience with the specific service. Without personal knowledge of the process, customers depend on the experience and skill of the professional to offer guidance, advice, and support along the way. Working together, a customer’s vision and a professional’s […] # Bridging the Gap in Customer Communication Per Gartner's 2023 Digital Worker Survey, 47% of workers struggle to find necessary information at least half the time. In most industries, a slow search means a delayed task. In professional services, it means a client who calls back in 30 minutes and receives a different answer than they heard this morning. The communication gap that quietly erodes client relationships isn't caused by poor communicators. It's caused by a knowledge retrieval problem — information that exists somewhere across email threads, shared folders, and meeting notes but can't be reached when it matters most. Four strategies separate firms that close this gap from those that manage it indefinitely. The differentiating factor isn't training. It's infrastructure. ## The retrieval problem hiding behind a communication problem Consider a client success manager at a mid-size consulting firm. She's in an active client call when the client asks about a recommendation made during a project review three months earlier. The information exists — in a meeting note, an email thread, a document uploaded to a shared folder — but locating it during a live call means switching between three systems while keeping the client engaged and the conversation on track. She makes a reasonable inference from memory. She's slightly off. The client notices. This scenario repeats itself dozens of times a week across professional services teams of every size. Per the *State of the Digital Workplace and Modern Intranet, 2024*, only 22% of company intranets deliver personalized content to employees — meaning most professionals navigate a generic information environment that doesn't surface client-specific context at the moment of need. What firms typically diagnose as a communication problem is, at its root, a systems architecture problem. Employees can lose over four hours per week switching between disconnected communication and project tools, directly degrading their ability to respond accurately under client pressure (per MangoApps research on tool-sprawl). Training employees to communicate more clearly doesn't change the underlying constraint. The information exists but can't be reached in real time. The four strategies below address the retrieval layer. Fix that, and the communication layer largely follows. ## Set communication standards that live where employees work Before any technology closes the retrieval gap, firms need shared agreement on what current information looks like and where it lives. Communication standards — how project updates are formatted, how status changes are escalated, how decisions are logged and attributed — only function when they're accessible in real time. A communication standard buried in an onboarding document is not, practically speaking, a standard. Neither is a guideline stored in a folder organized by quarter. For professional services teams managing five or ten concurrent client engagements, SOP operations documentation needs to live in a central, role-accessible knowledge management system — one that surfaces the most relevant guidelines based on the employee's active projects rather than requiring them to know where to look before they can find what they need. The operational gap this creates is visible in how inconsistently clients receive information across a team. One account manager formats updates one way; a colleague uses a different structure; a third improvises based on what the client last responded well to. The client experiences three different communication styles from one firm. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents how communication consistency has become a technology infrastructure problem as much as a training one — particularly for client-facing teams where inconsistency compounds with every interaction. ## Give each client engagement its own knowledge environment Every active client project accumulates context over time: decisions and their rationale, open questions, documents, historical communications, and the informal knowledge that builds between formal deliverables. When that context is distributed across email, messaging platforms, and shared drives, no single team member has a complete picture — and new members joining mid-engagement start from a partial one. Dedicated project workspaces consolidate this context in one environment. All project communication, documents, and status updates live in a single location. External guest access allows clients to participate directly — reviewing updates, uploading documents, asking questions — without requiring a separate communication channel outside the team's knowledge environment. The practical effect is immediate. The client success manager from the earlier scenario now has accurate context in front of her during the call. "What did we decide in March" takes 15 seconds rather than 15 minutes, and the answer is correct. New team members covering for a colleague can answer client questions with accurate context rather than a promise to follow up. Account managers transitioning between engagements don't lose the institutional knowledge accumulated over months of work. [MangoApps' employee app](/solutions/employee-app) delivers this kind of unified project environment, combining team channels, document management, and mobile access in a single place. The result is a reduction in the tool-switching that slows client-facing teams precisely at the moments that matter most — the live call, the unexpected client question, the sudden deadline. ## Deploy knowledge management tools built for retrieval at the moment of need Per a Banner Health employee poll, 63% of employees said their intranet content was not current or relevant. That's a retrieval design problem, not a volume problem. A knowledge base that requires employees to reconstruct the filing logic someone else used three years ago isn't functioning as a knowledge management system. It's functioning as an archive with a search bar attached. Modern knowledge management tools close this gap by using AI-powered search connected to existing repositories — SharePoint, Google Drive, Box — to surface accurate answers from company data without requiring employees to know where the information lives. For client-facing professionals, this shift is structural. When a consultant can pull up the correct precedent, benchmark, or historical client decision in under a minute from any device, client communication improves not because the consultant became a better communicator, but because the retrieval environment stopped working against them. This is the positioning gap that most communication improvement efforts miss. The problem isn't that employees need to communicate more carefully — it's that they're working from incomplete or stale information because their tools of knowledge management aren't designed for retrieval at the moment of need. Deploying a unified employee experience platform can also reduce the number of redundant systems IT teams manage by three to four times, simplifying the tech stack that client-service teams depend on every day (per MangoApps research on IT complexity and tool consolidation). The [MangoApps 2026 Forrester Wave Intranet Platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) covers how AI-assisted search has moved from roadmap item to active evaluation criterion for enterprise intranet platforms — a shift that reflects what client-facing knowledge teams now require from their internal tools. ## Enable access without a VPN or corporate email Per Banner Health, 61% of employees want intranet access outside the work VPN. In professional services, where client engagements frequently take place at client sites, in transit, and from home offices, restricting platform access to a corporate VPN connection isn't a security posture — it's a structural access barrier that reopens the retrieval gap whenever a team member is away from their desk. Mobile-first access without a corporate email requirement is the baseline for any team that works outside a fixed office. iOS and Android access to project documents, team channels, and client updates means the information environment follows the team member rather than waiting for them to return to a desk or a VPN session that won't connect from a client building's guest WiFi. The access gap has measurable consequences. OU Health achieved 87% workforce engagement within months of launching a unified communication app. The difference between platforms requiring VPN access and those designed for use anywhere isn't a feature distinction — it's an adoption distinction. For professional services firms where client responsiveness is the product, that adoption gap is the communication gap made visible and measurable. For frontline and field-based employees specifically, the replacement cost of a client-facing employee lost to poor communication infrastructure ranges from $4,400 to $15,000 per person. Firms that close the mobile access gap don't just improve communication quality — they reduce the structural friction that causes client-facing professionals to disengage from the tools that are supposed to support them. ## What to expect in the first 90 days Firms that deploy a unified knowledge and communication environment typically see the impact on client responsiveness before it shows up in dashboard metrics. The first visible shift is usually a reduction in how often team members say "let me get back to you on that" — because the answer is now accessible in real time rather than after a multi-system search across disconnected tools. The second shift appears in client perception. Clients don't always name improved communication consistency explicitly; they renew contracts, expand engagements, or refer colleagues. The connection between retrieval speed and client retention isn't theoretical. It's visible in the patterns of firms that have moved from fragmented tool stacks to unified environments. Implementation doesn't require a full organizational transformation. The highest-leverage starting point is almost always the client-facing team experiencing the most visible retrieval failures — the group where "let me get back to you" is costing the most. Configure their workspace first. Measure response times and client satisfaction signals over a 30-day baseline. The evidence for wider deployment typically surfaces before the end of that window. For a broader view of how [employee communications](/solutions/employee-communications) capabilities support client-facing teams at scale — including how firms structure communication across projects, roles, and geographies without adding administrative overhead — the solution page covers the full capability set across posts, campaigns, alerts, and personalized feeds. The gap in customer communication closes when the retrieval problem is solved. Not when employees are trained to communicate more carefully — when the systems they depend on stop requiring them to choose between responding quickly and responding accurately. --- # How A Centralized Workspace Helps You Stay Tech Savvy **Author:** Anna Carriveau **Published:** 2019-10-29 **Category:** integrated-digital-workplace From retail and manufacturing to banking and healthcare, modern businesses rely heavily on technology organizations to enable their everyday operations. In fact, the business-to-business (B2B) technology industry has never been stronger. In order to maintain a industry advantage, technology providers have to say current on the latest industry innovations. With technology updating almost every day, […] # How a Centralized Workspace Helps Your Organization Stay Tech-Savvy An **intranet** — a private, internal network that gives employees a single place to communicate, collaborate, and access company knowledge — is now standard infrastructure for most organizations. According to Social Edge Consulting, 91% of organizations operate an intranet. Yet the same research finds that nearly a third of employees never log in, and only 13% use it daily. The gap between having a centralized workspace and actually benefiting from one is where most companies lose ground. This article explains what makes a centralized workspace genuinely useful for staying current on technology trends, and what separates platforms that employees actually use from ones that collect digital dust. --- ## What Is an Intranet, and Why Does It Matter for Tech-Savvy Teams? The **definition of an intranet** is straightforward: a private network accessible only to an organization's staff, used to share information, tools, and resources. In practice, a modern intranet does far more than host a company directory or post HR announcements. It becomes the connective tissue between people, knowledge, and the systems they rely on every day. For B2B technology organizations — where staying current on industry developments is a competitive requirement, not a nice-to-have — a well-designed intranet is the difference between employees who can act on new information quickly and those who spend their day hunting for it. According to IDC, employees spend an average of 2.5 hours per day searching for information. That is roughly 12.5 hours per week per person that a centralized, searchable workspace can reclaim. According to SWOOP Analytics, the average employee spends only six minutes per day using intranet tools — a figure that reflects how poorly most deployments are designed, not how little employees need them. --- ## Turning New Knowledge Into Action Understanding the latest technology advancements is only half the challenge. The other half is translating that knowledge into something the organization can actually implement. A centralized workspace gives employees a shared environment to surface new ideas, discuss feasibility, and coordinate rollout — without the friction of switching between disconnected tools. Employees lose over four hours weekly switching between disconnected systems, according to MangoApps product analysis of tool sprawl in enterprise environments. A unified platform eliminates that switching cost by consolidating communication, project collaboration, and knowledge storage in one place. Enterprise deployments have demonstrated that a centralized platform can consolidate more than 200 disparate systems into a single mobile dashboard (per MangoApps case study data from TeamHealth). When a team discovers a relevant industry development, [dedicated project workspaces](/key-features/workspaces) let them move immediately from discussion to planning to execution — keeping the organization's response time short and its competitive position intact. --- ## Reaching Every Employee, Including Frontline Workers According to Emergence Capital, 80% of the global workforce is deskless — working in retail, manufacturing, healthcare, logistics, and other environments where a desktop computer is not part of the job. Yet most intranet deployments are designed around desk-based employees, leaving frontline workers without access to the same knowledge and communications their office-based colleagues receive. A centralized workspace built for the full workforce allows frontline and deskless employees to access company knowledge without a corporate email address or VPN — removing the most common adoption barrier for non-desk roles. When the cost of replacing a single frontline employee runs between $4,400 and $15,000, keeping those workers connected and informed is a retention strategy as much as a communication one. Organizations that have launched a branded, mobile-accessible centralized app have reported 87% workforce engagement within a few months of go-live. The [MangoApps employee app](/solutions/employee-app) is designed specifically to serve both desk and non-desk employees from a single platform. --- ## Company Communication That Employees Actually Read A centralized platform changes how technology trends and company news travel through an organization. Instead of relying on email threads that get buried or all-hands meetings that happen quarterly, a [modern intranet](/solutions/modern-intranet) makes sharing and consuming industry updates a routine part of the workday. Department-specific news feeds, targeted announcements, and scheduled newsletters can all live in one place — organized so that a software engineer sees relevant development updates while a sales team member sees client-facing product news. This kind of structured communication reduces noise and increases the likelihood that employees actually engage with what they receive. For teams responsible for internal communications strategy, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) offers a detailed look at how leading organizations are structuring their communication channels to improve reach and engagement. --- ## Learning Opportunities Embedded in Daily Work Technology adoption often requires more than reading a summary. Employees need structured courses, hands-on walkthroughs, and reference materials they can return to as they apply new skills. A centralized workspace lets organizations deliver all of that without requiring employees to leave their primary work environment. Courses can be targeted to specific teams, departments, or roles. Completion can be tracked. And because the learning content lives alongside the tools and projects employees use every day, the gap between learning something and applying it shrinks considerably. Standardized training modules also ensure that every employee — regardless of location or shift — receives the same foundational knowledge. For organizations looking to make learning a structural part of how work gets done rather than a separate initiative, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers the most common design mistakes and how to avoid them. --- ## AI-Assisted Information Surfacing One of the most significant shifts in modern centralized workspaces is the move from passive information storage to active knowledge delivery. Rather than requiring employees to know where to look, AI-assisted platforms surface relevant documents, updates, and expertise based on what a person is currently working on. This directly addresses the IDC finding that employees spend 2.5 hours per day searching for information. When the platform proactively connects employees to what they need — rather than waiting for them to search — that time is recovered and redirected toward productive work. For technology organizations where staying current is a daily requirement, this shift from search to surface is meaningful. --- ## Security as a Foundation for Confident Knowledge Sharing A centralized workspace is only as useful as it is trustworthy. Employees and IT teams need confidence that sensitive company knowledge, client data, and internal communications are protected before they will use a platform as their primary work hub. MangoApps supports SAML 2.0, OAuth 2.0, LDAP, and single sign-on (SSO) — the authentication standards that enterprise IT teams require before approving any platform for broad deployment. Security is not an add-on feature; it is the prerequisite that makes confident, organization-wide knowledge sharing possible. For organizations evaluating intranet platforms against enterprise requirements, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an independent assessment of how leading platforms compare on security, usability, and governance. --- ## What to Look for in a Centralized Workspace Not all centralized workspaces deliver the same outcomes. When evaluating options, technology organizations should look for platforms that address the following: - **Unified access**: Desk and deskless employees on the same platform, without VPN or corporate email requirements - **Searchable knowledge base**: A single, indexed repository that surfaces information rather than requiring employees to know where it lives - **Targeted communication**: The ability to segment news, updates, and learning content by role, department, or location - **Structured learning**: Course delivery and completion tracking built into the same environment where work happens - **Enterprise security**: SAML 2.0, OAuth 2.0, LDAP, and SSO support as baseline requirements - **AI-assisted discovery**: Proactive surfacing of relevant knowledge, not just passive storage - **Fast deployment**: Modern platforms can be configured and stood up in days, not months of IT-led customization For organizations currently running SharePoint 2016 or 2019 and evaluating what a replacement should include, [Frontline Intranet Requirements: A Practical Checklist for Replacing SharePoint](/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) provides a structured framework for the evaluation. --- ## The Direct Answer: Does a Centralized Workspace Actually Help Organizations Stay Tech-Savvy? Yes — but only when the platform is designed so that employees use it consistently. The research is clear: 91% of organizations have an intranet (per Social Edge Consulting), but daily usage sits at 13% and nearly a third of employees never log in at all. A centralized workspace that employees avoid does not help anyone stay current on anything. The organizations that close this gap share a few characteristics: they make the platform accessible to every employee regardless of role or device, they use it as the primary channel for company communication rather than a secondary one, they embed learning into the daily workflow rather than treating it as a separate system, and they choose platforms with AI-assisted knowledge surfacing so that staying informed does not require active effort. For technology organizations specifically, where industry developments move quickly and competitive advantage depends on acting on new information faster than competitors, a centralized workspace is not a productivity tool — it is an operational requirement. The question is not whether to have one, but whether the one you have is actually being used. MangoApps is built to address each of the gaps described above. To see how the platform handles your organization's specific structure and workforce mix, [explore the company portal features](/key-features/company-portal) or review how [department sites](/key-features/department-sites) can be configured for different teams and locations. --- # Become A Better Mentor With A Digital Collaborative Workspace **Author:** Anna Carriveau **Published:** 2019-10-22 **Category:** online-community-software Educators have the important responsibility of sharing and enriching the lives of their students. Educators have the opportunity to mentor, guide, and positively influence their pupils. However, with the ever-increasing focus of technology in the classroom, it’s only natural to worry about a teacher’s ability to mentor effectively. With remote meetings, online coursework, and so […] # How a Digital Collaborative Workspace Helps Educators Become Better Mentors Consider Maria, an adjunct instructor teaching across two campuses. Between 7 a.m. and 3 p.m. on Tuesdays, she teaches a morning section, holds two office-hour appointments, reviews a student's draft, and checks her department chair's latest policy update. She does all of this across six different applications — the LMS for course materials, email for department updates, a scheduling tool for office hours, a shared drive for student documents, a separate HR portal for her own professional development, and a team chat she barely opens. Per IDC, employees spend an average of 2.5 hours per day searching for information across disconnected systems. For Maria, that search time isn't overhead — it's the hours she can't give to the student who sent her a draft at 9 p.m. The fragmentation problem in education is a mentorship problem. And solving it requires more than another tool; it requires a digital workspace designed to replace the stack. ## Why fragmented tools degrade mentoring, not just productivity The efficiency case for unified digital workspaces is well-documented. Per Social Edge Consulting, 91% of organizations operate an intranet, yet only 13% of employees use it daily, and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools — a number that says less about the tools' utility and more about the friction cost of reaching them. The mentorship cost of fragmentation is less discussed. When a student's question, an assignment rubric, department guidance, and peer feedback each live in different systems, the instructor spends attention switching between contexts rather than building relationships. The cognitive overhead of navigating six applications isn't neutral — it accumulates as fatigue, and fatigue is the enemy of presence. Effective mentorship requires presence: sustained attention, remembered context, the capacity to follow up. A digital collaborative workspace collapses those contexts into one. That consolidation doesn't just save time — it frees the attentional bandwidth that mentoring actually requires. The question for any institution evaluating these tools isn't whether a unified platform is more efficient; it's whether the time and attention returned to instructors actually reaches students. ## The mobile gap that leaves distributed educators behind Maria is relatively well-resourced. Per Emergence Capital, 80% of the global workforce is deskless — a figure that includes adjunct instructors moving between campuses, field educators working with frontline staff, and teachers in rural districts who can't rely on campus infrastructure. For these educators, digital workspace tools that require a desktop and a corporate login don't reach them at all. Mobile-first design is not a convenience feature in this context — it's an access requirement. A workspace platform that allows educators to access schedules, course updates, student communications, and peer feedback from a personal device without a VPN or corporate credential closes the gap that desktop-first tools create. When this access model is deployed correctly, organizations have documented workforce engagement rates above 85% within months of launch — a figure that reflects actual reach into distributed staff, not adoption by the office-based fraction of the workforce. This matters for mentorship because the educators hardest to reach are often the ones serving students who need sustained mentoring most: adjuncts at community colleges where students face structural barriers, field educators working with at-risk youth, instructors splitting time across departments with no dedicated office. Building mentorship infrastructure that doesn't reach these educators leaves the students with the most to gain without the advocates who could help them. ## Peer knowledge sharing as a mentorship multiplier Maria is a capable instructor, but her ability to mentor is partly a function of what she knows — and experienced educators' institutional knowledge doesn't travel between departments easily. The faculty member who developed the most effective study support approach for students returning after a gap year may be across campus and entirely invisible to Maria's workflow. A digital collaborative workspace gives educators a structured channel to share lesson approaches, surface resources, and provide peer feedback that would otherwise stay siloed. Peer-to-peer knowledge sharing embedded in a digital platform accelerates informal learning faster than scheduled training alone — particularly for distributed or frontline educators who can't rely on hallway conversations. This kind of networked knowledge exchange doesn't replace formal professional development; it supplements it in the real-time, context-rich way that formal training rarely can. For institutions managing mentorship at scale across multiple departments and campuses, the mechanism that turns individual expertise into institutional capacity is not more training sessions — it is infrastructure that keeps expert knowledge accessible to the people who need it, when they need it. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how organizations are building communication architectures that allow this kind of distributed knowledge exchange without requiring synchronous coordination — a particularly relevant framework for institutions with part-time or distributed teaching staff. ## Connecting mentorship to structured learning Informal peer exchange is valuable, but it isn't sufficient. Effective mentorship in educational institutions also requires structured pathways: onboarding for new instructors, professional development tracks, compliance training that can be tracked and verified. The problem many institutions face is that structured learning lives in a separate LMS learning system that educators visit reluctantly, while peer collaboration happens in a different tool, and neither connects to daily work. A platform that functions as both a collaborative workspace and a learning management environment closes that gap. Rather than sending Maria to a separate system for required training and back to another tool for peer conversation, a unified platform keeps both in the same environment. Instructors who can complete professional development from within their daily workflow — alongside the communication and course material access they need anyway — actually complete it. Completion rates for mobile-accessible training rise when training is reachable where the work happens, not accessible only on a separate login. For a practical framework on what this integration looks like in operation, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers the specific design choices that distinguish learning embedded in daily work from learning treated as a separate event. ## The burnout dimension Teaching is emotionally demanding. Instructors need spaces to share frustrations, ask for help, and receive support from peers who understand the specific pressures of the role. Without those spaces — and without relief from a fragmented tool environment that multiplies daily friction — burnout accelerates and mentoring quality declines proportionally. When educators feel disconnected from colleagues and buried in administrative noise across too many channels, the first thing they protect is their own energy. Students receive less access, not more. A digital workspace that consolidates communication, surfaces role-relevant information rather than broadcasting to everyone, and gives educators a peer channel they actually use reduces both the cognitive overhead and the isolation that fuels burnout. The relationship between communication clarity and workforce engagement runs in one direction: when employees know where to find information and feel connected to colleagues doing similar work, engagement rises. For educators, that engagement directly shapes the quality of what students experience — the bandwidth for a difficult advising conversation, the follow-through on a student's long-term goals, the presence that makes the difference between a transaction and a mentoring relationship. ## What improvement looks like in practice Institutions that approach this systematically — starting with a mobile-first deployment, tracking adoption rates, and measuring whether educators are reaching the platform in their daily work — see outcomes that go beyond efficiency. Intranet adoption, which per Social Edge Consulting typically sits at 13% of daily users, rises when the platform is designed for the access patterns of educators rather than office workers. The [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study documents what a communication overhaul produces in a knowledge-intensive, multi-department environment with complex access constraints. The patterns transfer directly to educational institutions: when communication, peer learning, and structured training live in one place, instructors spend less time navigating and more time doing the work that mentorship requires. For institutions evaluating platforms against real educator and workforce needs, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) evaluates how leading platforms handle the intersection of communication, learning, and engagement — the three dimensions that determine whether a workspace actually reaches educators or gets ignored by them. ## The infrastructure behind effective mentoring Maria's six-app navigation problem is not unusual. It is the norm in institutions that have accumulated collaboration tools without designing for the educator experience. The gap between having digital tools and those tools supporting mentorship is closed by consolidation, not addition. A digital collaborative workspace designed for distributed educators — mobile-first, peer-connected, integrated with structured learning — doesn't make mentors out of instructors who weren't already mentors. It removes the infrastructure barriers that prevent the good ones from doing the work at scale. That removal is measurable: in time returned, in attention freed, in educators who stay engaged enough to show up for the students counting on them. --- # Why Manufacturing Needs To Go Mobile **Author:** Anna Carriveau **Published:** 2019-10-15 **Category:** online-community-software Corporate executives, freelance workers, and practically everyone in-between are now working remotely. With easier access technology tool and the freedom to operate on the go, mobile access seems like an obvious choice for knowledge workers, but it’s potential is far less limited. In fact, even hands-on industries like manufacturing could benefit from mobile quite a […] # Why Manufacturing Needs To Go Mobile Manufacturing has always been a physical business. The work happens on the floor, at the line, at the machine — not at a desk. That's unlikely to change. What has changed is the expectation that the people doing that work should have access to the same information, training, and communication tools that office workers have taken for granted for decades. The business case for mobile in manufacturing isn't about convenience. It's about retention, safety, and operational continuity. According to McKinsey research, 89% of frontline workers say they'll stay with their employer when leaders actively listen to and act on their feedback. A mobile tool is the mechanism that makes that listening practical at scale. Without it, feedback arrives late, safety information moves slowly, and the gap between management and the floor compounds every shift. This article covers four operational gaps that mobile addresses in manufacturing — and what separates tools that actually get adopted from the ones that don't. ## The manufacturing communication gap is structural, not cultural Most enterprise communication tools were built for desk workers. Email, intranets, and document repositories assume the user is sitting at a workstation with a corporate login and reliable internet access. That describes roughly 20% of the global workforce. For manufacturing teams, the other 80% — operators, technicians, quality inspectors, and maintenance staff on the floor — are effectively disconnected by design. This isn't cultural resistance to technology. It's an access problem. When a shift policy changes or a safety protocol updates, the plant supervisor can't blast an email to workers who don't have corporate email addresses. When a machine operator needs to reference a maintenance procedure mid-shift, they can't pull up the company intranet on a shared terminal two sections away. The information exists. The path from that information to the worker who needs it is broken. Mobile tools built for frontline workers solve for this directly. Enrollment happens via QR code, SMS link, or personal email — no corporate account required. Access works from a personal mobile device without a VPN. Gartner's 2023 Digital Worker Survey found that 47% of workers struggle to find necessary information at least half the time; on a manufacturing floor, that statistic translates to errors, rework, and safety incidents that are preventable. Mobile access that requires no special provisioning removes the prerequisite that was blocking adoption in the first place. ## Real-time alerts make safety and quality responsive Manufacturing requires speed of information as much as speed of production. When a quality defect surfaces at one station, workers two stations down need to know before they process the same batch. When safety conditions shift on the floor, the delay between discovery and notification can't be measured in hours. Real-time mobile communication closes that gap. Workers receive targeted alerts by team, shift, or physical location — not just company-wide broadcasts that generate noise for employees on different schedules or at different sites. Supervisors can push a notification and require a read acknowledgement, creating a digital audit trail for compliance purposes. That confirmation loop matters in regulated environments where documenting that workers received a safety update is as important as the update itself. For quality and safety purposes, the medium shapes the outcome. A push notification to a personal device, readable in seconds between tasks, does what a posted notice on the breakroom wall cannot: it arrives when the information is still actionable, not after the situation has already resolved. The more distributed the floor, and the faster the production cadence, the more that timing difference compounds. ## On-demand training eliminates the "wait until next quarter" problem Manufacturing processes change constantly — new equipment, updated regulatory requirements, revised procedures. The traditional response is a scheduled training session: pull workers who can be spared from the floor, deliver the update, document completion, and hope the information sticks. That model doesn't scale. When product lines change monthly and regulatory requirements shift quarterly, a training calendar built around quarterly classroom sessions creates a permanent information lag between what the organization knows and what the floor worker knows. In the meantime, workers operate on outdated procedures — sometimes safely, sometimes not. Mobile-delivered training removes the scheduling bottleneck. Workers complete a short procedure update between shifts, at their own pace, from their own device. Managers assign training to specific teams when an SOP changes and track completion in real time rather than waiting for a session roster. [Learning and development embedded in daily work](/articles/learning-and-development-strategy-embedded-in-daily-work) — accessible when the need arises rather than scheduled weeks in advance — produces faster adoption and higher retention of updated procedures. Offline access matters here as well. Plant floors, cold storage facilities, and remote sites often have inconsistent connectivity. Mobile tools that cache documents and training materials locally ensure workers in low-connectivity environments aren't cut off from essential procedures at the moment they need them. This isn't an edge case in manufacturing — it describes a significant portion of where the work actually happens. ## Recognition closes the visibility gap between the floor and leadership Physical distance has a predictable organizational effect: the harder something is to observe, the less likely it is to be acknowledged. Plant floor workers completing difficult, repetitive, or high-risk tasks often have limited visibility with senior leadership — not because their contribution isn't valued, but because the organizational mechanisms for recognition weren't built for distributed, shift-based work. McKinsey research establishes that 89% of frontline workers will stay with their companies when leaders demonstrate that they hear and respond to frontline input. Recognition is one of the most concrete signals of that responsiveness. When a plant manager acknowledges a floor worker's contribution within hours rather than waiting for a quarterly review cycle, the behavioral outcome — retention — is measurable. Mobile recognition tools let peers and managers acknowledge contributions in the moment, visible across teams that can span a facility or the entire company. The worker who caught a defect that would have triggered a recall, the team that hit a production target three days early — these moments surface in a mobile feed rather than passing unnoticed. The acknowledgement is immediate and public in a way that shift-end verbal feedback never is. For manufacturing organizations where replacing a mid-skill frontline employee costs between $4,400 and $15,000 per departure — accounting for recruitment, onboarding, and the productivity gap while the role is unfilled — tools that reduce voluntary turnover aren't operational nice-to-haves. They carry a direct and calculable return. ## Workforce operations from any device: scheduling, shift management, and time tracking The operational complexity of manufacturing scheduling is significant. Multiple shifts, variable staffing requirements, last-minute callouts, and compliance requirements around overtime all converge on whoever owns the schedule. For the worker, the information asymmetry is equally frustrating: shift assignments communicated via posted boards, supervisor phone calls, or paper printouts leave little room for advance planning or self-service adjustments. Mobile workforce management changes both sides of that equation. Managers publish schedules, push shift-change notifications, and fill open shifts through the same platform workers use to receive communications and complete training. Workers view availability, request swaps, and confirm assignments from their phones — without calling a supervisor or waiting for a posted update. The self-service layer reduces the administrative overhead that multiplies when a team is spread across multiple shifts and locations. Time tracking via mobile reduces the friction of manual clock-in processes and creates a digital record that integrates with payroll without a separate data entry step. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) identifies mobile-first workforce management as a consistent differentiator for manufacturing organizations that outperform on both retention and operational efficiency metrics. The ability to view, manage, and respond to scheduling information from a personal device reduces what can be called the "I didn't know" category of coverage gaps — the no-shows and last-minute scheduling scrambles that follow from information arriving too late to act on. ## What separates mobile tools that get adopted from those that don't The typical failure mode for manufacturing mobile deployments isn't feature parity. It's enrollment. A tool that requires a corporate email address, IT provisioning, and VPN setup will see adoption rates that reflect the difficulty of those prerequisites. Workers who aren't enrolled can't engage, and a partially adopted platform creates a two-tier information environment rather than closing one. Enrollment via QR code, SMS link, or personal email removes that barrier. A ten-second scan at shift start connects a worker to the platform without any IT involvement. That simplicity is not incidental — it determines whether the tool reaches the workers who need it most. Beyond enrollment, the questions that determine whether a mobile tool functions in a manufacturing environment: **Does it work without consistent connectivity?** Plant floors and remote sites have variable signals. Tools that require a live internet connection for document access fail precisely where workers need them most. **Can it reach workers without a corporate email address?** Most frontline manufacturing workers don't have corporate email. Enrollment must support personal identifiers — phone number, personal email, or QR code. **Does it send targeted communication rather than company-wide broadcasts?** Alerts by team, shift, or location are more useful than notifications that create noise for workers on different schedules. **Does it unify communication, training, scheduling, and recognition in one place?** An [employee app](/solutions/employee-app) that brings these functions together reduces the number of systems workers navigate and increases the probability that any given worker is actually enrolled and active. **Is there an analytics layer for administrators?** Managers need to know which teams have completed a compliance training update, which safety notifications have been acknowledged, and where adoption gaps remain. Visibility into use is what closes the loop between deployment and measurable outcomes. ## The manufacturing case for mobile is an equity argument first The organizations building the strongest case for mobile in manufacturing aren't doing it to be current with technology trends. They're doing it because the workers on their floor — the ones responsible for quality, safety, and output — deserve the same access to organizational information that their desk-based counterparts have had for years. The [employee communications](/solutions/employee-communications) infrastructure that functions in manufacturing is one designed for the conditions of a plant floor: inconsistent connectivity, no corporate email, shift-based schedules, and a workforce that needs information in seconds rather than hours. When that infrastructure is in place, the operational and retention outcomes follow. The safety alert that reaches a worker between tasks. The training module completed before the new product line goes live. The recognition that travels from the plant floor to the company-wide feed. The shift change that a worker can request from their phone without calling their supervisor. These aren't features. They're the operational baseline for a manufacturing workforce that has what it needs to do the work well — and to stay. --- # Encouraging Employee Engagement In Construction **Author:** Anna Carriveau **Published:** 2019-10-01 **Category:** employee-engagement In today’s working world, salary increases simply aren’t enough. Employees need to be acknowledged, encouraged, supported, and engaged. Unfortunately most of the recent efforts surrounding employee engagement is aimed at office employees. One industry in particular where frontline workers are being neglected is construction. Unlike working in the office, construction workers are constantly moving and […] # Encouraging Employee Engagement In Construction In today's working world, salary increases simply aren't enough. Employees need to be acknowledged, encouraged, supported, and engaged. Unfortunately, most recent efforts surrounding employee engagement are aimed at office employees. Construction is one industry where frontline workers are being consistently neglected — and the consequences are measurable. Per Emergence Capital, 80% of the global workforce is deskless, yet most digital communication tools are designed for desk-based workers, leaving frontline crews without real-time access to updates or company resources. Construction workers are constantly moving and adapting to problems on the frontline, facing challenges unlike those in any other environment. In this article, we'll take a deeper look at how leaders can boost employee engagement in the construction industry through practical employee engagement strategies that reach workers where they actually are. ## Enable Seamless Communication Construction conditions are constantly changing. Whether it's the weather, traffic stops, legal requirements, or another factor, something unexpected always seems to influence the work. Without regular updates and reliable communication, construction employees can feel left out of the loop. Having dependable employee communication not only equips workers with tools to make necessary changes but also demonstrates their importance to the organization. The challenge is structural: per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in to it, and only 13% use one daily. For construction crews who spend their day on a job site rather than at a desk, a desktop-first intranet is effectively no intranet at all. The fix is mobile-first delivery — a dedicated mobile app that pushes role-specific safety updates, schedule changes, and company news directly to a worker's phone. Per IDC, employees spend an average of 2.5 hours per day searching for information; closing that gap on a job site has direct safety and productivity implications. Persona-driven communications — delivering role-specific updates and resources based on job function — are emerging as a best practice for reaching distributed and frontline teams (Akumina / State of the Digital Workplace & Modern Intranet 2024). Regular, targeted communication helps cut through the confusion and enables a safe, productive, and engaging work environment. For a broader look at how internal communications are evolving for frontline-heavy organizations, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the key shifts shaping the field. ## Inspire and Support Employees Construction work is difficult in every sense of the word. From daily physical labor to negotiating contract agreements, construction workers are often mentally and physically exhausted. When encouraging employee engagement in construction, employees need honest and enthusiastic leadership to motivate and inspire long-term success. Proactive leadership means more than just giving orders or ensuring work is done. Authentic leaders are a part of the team. They know the workers personally, understand the conditions they work in, and offer consistent praise and support. Without a reliable leader, the difficult work can wear a team down. However, with the right support and encouragement, the hard work can become an engaging, uplifting, and uniting activity. Leadership development and employee engagement training are increasingly recognized as interdependent — managers who receive structured coaching on recognition and communication consistently outperform those who don't. For context on how learning initiatives connect to frontline engagement outcomes, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) is worth reviewing alongside any construction engagement initiative. ## Improve Workplace Safety Construction work regularly includes hazardous environments or dangerous activities. And while some risks will always be unavoidable, ensuring employees understand safety procedures is essential for engagement. When employees face unnecessary risks within the work environment, a pessimistic attitude is almost inevitable. Helping workers stay aware of work policies and procedures will not only create a safer work environment but also improve employee attitude and engagement onsite. Safety communication is also a direct engagement lever: when workers receive timely, role-relevant safety updates rather than generic all-staff blasts, they report feeling more valued and better prepared. Persona-driven platforms that segment content by job function and location make this kind of targeted safety communication operationally feasible for large, distributed construction crews. Organizations managing similarly complex, distributed workforces — such as those explored in [Managing a Unionized Workforce Is Different. Your Software Should Be Too](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) — face comparable communication challenges and have found structured digital channels essential. ## Make Resources Accessible Construction work is hands-on, fast-paced, and doesn't leave a lot of time for checking messages or reviewing files. But without a way to view information, workers often feel discouraged and unappreciated. Employees need to know their contributions are important, and that their work is just as valuable as corporate. The access gap is real and quantifiable. Per SWOOP Analytics, the average employee spends only six minutes per day using intranet tools — a figure that almost certainly skews lower for construction workers who lack desktop access entirely. Only 22% of company intranets currently deliver personalized content to employees, meaning most construction workers receive the same generic communications as corporate staff, a key driver of disengagement (Akumina / State of the Digital Workplace & Modern Intranet 2024). Mobile-first platforms deployed for large frontline workforces can reach 90%+ adoption within the first six months when the experience is purpose-built for non-desk workers (Unily CVS case study). By providing fast, simple, and reliable mobile access to resources — schedules, safety documents, HR forms, project updates — employees feel understood, supported, and engaged. The scale of lift is significant when the right infrastructure is in place. Eurostar reported a 253% increase in employee engagement after deploying a unified employee communications platform. British Airways, with an 80% frontline workforce, achieved a 30-point engagement score increase within the first year of launching a mobile-first intranet, with 85% of employees reporting they understood the company vision. These outcomes are not limited to aviation; they reflect what happens when any frontline-heavy organization closes the access gap. MangoApps' [solutions for employee engagement](/solutions/employee-engagement) are built around this same principle — meeting workers on the device they already carry rather than the desk they don't have. ## What Metrics Should You Track for Construction Employee Engagement? Implementing employee engagement strategies is only half the equation — measuring whether they're working is equally important. For construction teams, useful leading indicators include: mobile app adoption rate among field crews, frequency of safety-acknowledgment completions, participation rates in employee engagement surveys, and manager response times to worker-submitted issues or questions. An employee engagement survey deployed quarterly (rather than annually) gives site supervisors actionable data before disengagement compounds into turnover. Tracking these metrics by crew, site, and role — rather than as a single company-wide score — surfaces the pockets of disengagement that aggregate numbers hide. For a structured view of how HR and operations leaders are approaching engagement measurement heading into the next planning cycle, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines the benchmarks and frameworks gaining traction across industries with large frontline populations. ## How Do You Reach Distributed and Remote Construction Teams? Construction projects are rarely confined to a single location. Crews rotate across job sites, subcontractors move between projects, and supervisors may oversee multiple locations simultaneously. Reaching these distributed teams requires more than a company newsletter — it requires an employee experience infrastructure built for location variability. Practical approaches include: push notifications for time-sensitive safety or schedule updates, offline-capable mobile apps for crews working in areas with limited connectivity, and role-based content targeting so a concrete finisher in the field receives different information than a project manager in the trailer. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how organizations with distributed workforces are structuring their communication and operations technology stacks to address exactly these challenges. ## The Bottom Line on Construction Employee Engagement Construction work's unique environments create real challenges, but employee engagement doesn't have to be one of them. The four levers — communication, leadership, safety, and resource access — are well understood. What separates organizations that move the needle from those that don't is execution infrastructure: specifically, whether frontline workers can actually receive, act on, and respond to communications from the device in their pocket. The evidence from frontline-heavy industries is consistent: when mobile-first, persona-driven platforms replace desktop-only tools, engagement scores rise sharply, safety compliance improves, and workers report feeling like a genuine part of the organization rather than an afterthought. For construction companies ready to close that gap, MangoApps provides the employee engagement software and mobile-first communication tools purpose-built for shift-based, location-variable teams. Contact us or schedule a personalized demo to see how it works in practice. --- # Strengthening The Financial Sector With Centralized Workspaces **Author:** Anna Carriveau **Published:** 2019-09-24 **Category:** integrated-digital-workplace Financial services are anything but simple. With constantly changing market values, and shifting global economies, no two financial accounts are ever the same. Perhaps more than almost any other industry, financial clients are counting on their advisers to stay informed, manage their resources, and represent their individual interests. Keeping every detail organized is critical to […] # Strengthening the Financial Sector With Centralized Workspaces Financial services firms operate under conditions that few other industries face: constantly shifting market values, strict regulatory requirements, and clients who expect their advisers to have the right information at exactly the right moment. A centralized intranet — a private, internal network that connects employees, data, and workflows in one place — gives financial organizations the infrastructure to meet those demands without drowning in fragmented tools and scattered files. This article explains how a well-designed centralized workspace addresses the specific operational and compliance challenges financial teams face, and what to look for when evaluating one. ## What a Centralized Intranet Actually Does for Financial Teams An intranet, by definition, is a private network accessible only to an organization's staff. In the financial sector, that definition matters because it draws a clear boundary around sensitive client data, regulatory documents, and internal communications. According to Social Edge Consulting, 91% of organizations already operate an intranet — but the same research found that nearly a third of employees never log in, and only 13% use one daily. That gap between deployment and adoption is where most financial firms lose value. The core problem is relevance. Only 22% of company intranets currently deliver personalized content to employees (per Akumina's State of the Digital Workplace & Modern Intranet 2024), which means most advisers open their intranet and see a generic feed that has little to do with their specific client portfolios or market segments. A centralized workspace built around role-based dashboards changes that dynamic: advisers see the client data, regulatory updates, and market signals that apply to their work, not a one-size-fits-all homepage. Employees spend an average of 2.5 hours per day searching for information (per IDC), a cost that compounds quickly in a financial environment where timing affects outcomes. Centralizing knowledge management tools — document libraries, policy repositories, compliance checklists — into a single searchable location directly reduces that overhead. ## Consolidating Financial Information Without Creating New Silos Financial data does not stay still. Market conditions change overnight, regulatory guidance is updated mid-quarter, and client circumstances evolve continuously. When that information lives across email threads, shared drives, and disconnected applications, advisers spend more time locating context than acting on it. A centralized workspace brings financial news feeds, client account details, compliance documentation, and internal research into a single location. Advisers can filter by client segment, asset class, or regulatory category rather than switching between systems. This is what distinguishes a purpose-built [intranet for financial teams](/solutions/modern-intranet) from a generic file-sharing tool: the ability to surface the right information for the right role without manual searching. Knowledge management tools embedded in the workspace — structured wikis, tagged document libraries, version-controlled policy pages — also ensure that when guidance changes, the updated version is what advisers find, not a cached copy from six months ago. ## Improving Collaboration Across Branches and Compliance Boundaries Financial firms often operate across multiple branches, regions, and regulatory jurisdictions. Advisers in different offices may be working on similar client profiles but have no structured way to share approaches, flag risks, or escalate questions. A centralized communication layer inside the intranet closes that gap. Team [workspaces](/key-features/workspaces) allow advisers to collaborate on client cases, share research, and document decisions in a traceable way — which matters both for service quality and for compliance. When a regulator asks how a recommendation was reached, a workspace with a documented discussion thread and attached analysis is far more defensible than a reconstructed email chain. Collaboration also accelerates onboarding. New advisers can access institutional knowledge — past case approaches, product explainers, compliance FAQs — without waiting for a senior colleague to be available. That self-service access to knowledge and knowledge management resources shortens the time before a new hire is productive. ## Responding to Client Concerns With Complete, Current Information Client trust in financial services is built on responsiveness and accuracy. When a client calls with a question about their portfolio or a concern about a market event, the adviser's ability to answer confidently depends on having complete, current information in front of them. A centralized workspace gives advisers a single view of a client's account history, recent interactions, relevant market context, and applicable product options. Rather than putting a client on hold to search three different systems, the adviser can respond from one screen. [Department sites](/key-features/department-sites) within the platform can be configured for specific practice areas — wealth management, commercial lending, insurance — so each team's workspace reflects their actual workflow rather than a generic layout. This specificity is what separates a well-configured intranet from one that employees ignore. Per SWOOP Analytics, the average daily time spent using intranet tools is just six minutes — a figure that reflects how often intranets fail to deliver content worth returning to. Role-specific dashboards and client-facing knowledge bases give advisers a reason to open the platform first, not last. ## Providing a Secure Environment That Meets Financial Compliance Requirements Security in financial services means more than keeping data in one place. Regulators expect organizations to demonstrate who accessed what, when, and why. A centralized workspace addresses this through several specific controls: - **Role-based access controls** ensure that advisers see only the client data and documents relevant to their accounts, reducing both accidental exposure and insider risk. - **Audit trails** log document access, edits, and sharing events, creating the evidentiary record that compliance teams need for regulatory examinations. - **Centralized governance** means that when a policy is updated, the old version is archived and the new one is the only version in circulation — eliminating the compliance risk of advisers working from outdated guidance. - **Data residency and access boundaries** keep sensitive client information within the organization's controlled environment rather than dispersed across personal email or consumer file-sharing tools. Competitors in the secure intranet space have made compliance governance a primary differentiator. Financial organizations evaluating platforms should ask specifically about audit logging, access control granularity, and how the platform handles document versioning under regulatory retention requirements. The [company portal](/key-features/company-portal) layer of a well-structured intranet is where these governance controls are most visible to employees and administrators alike. ## How Quickly Can a Financial Firm Deploy a Centralized Workspace? One concern financial organizations raise is implementation time. Compliance-sensitive environments are cautious about technology changes, and IT teams are often stretched. Modern intranet platforms can be deployed and fully adopted within weeks rather than months, without requiring IT-led customization for every department. A unified platform that reaches 95% employee adoption after deployment (a benchmark cited in consolidated intranet case studies) demonstrates that consolidation drives engagement rather than just reorganizing the same underused tools. For financial firms specifically, the deployment sequence that works best typically starts with the highest-friction information problem — usually compliance documentation or client account access — and expands from there. Starting narrow and demonstrating measurable time savings builds internal support for broader adoption. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers adoption patterns across industries, including financial services, and is a practical reference for teams planning a rollout. ## What to Look for in a Financial-Sector Intranet Platform Not every intranet platform is built for the specific demands of financial services. When evaluating options, financial organizations should prioritize: 1. **Personalized, role-based dashboards** that surface adviser-specific client data and market signals rather than generic content feeds — given that only 22% of intranets currently deliver personalized content (per Akumina's State of the Digital Workplace & Modern Intranet 2024), this remains a meaningful differentiator. 2. **Compliance and governance controls** including audit trails, role-based access, and document version management. 3. **Knowledge management tools** that are searchable, tagged, and version-controlled — not just a shared drive with a search bar. 4. **Mobile access** for advisers who are not desk-based. Per Emergence Capital, 80% of the global workforce is deskless, and financial field teams are no exception. 5. **Measurable adoption metrics** so the platform team can identify which departments are not engaging and why, before low usage becomes an entrenched habit. MangoApps builds centralized workspaces around these requirements. The [webpage builder](/key-features/webpage-builder) allows financial teams to configure department-specific pages without IT involvement, and the platform's governance layer supports the audit and access control requirements that financial regulators expect. For organizations evaluating how MangoApps compares to other intranet platforms, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an independent assessment. ## The Bottom Line A centralized workspace is not a productivity perk for financial firms — it is an operational requirement. Advisers who spend 2.5 hours a day searching for information (per IDC) are not serving clients. Compliance teams that cannot produce audit trails are exposed to regulatory risk. Branches that cannot share knowledge are leaving institutional expertise siloed. The intranet platforms that financial organizations should consider are those that deliver role-specific content, enforce governance controls, and achieve adoption rates high enough to make the investment worthwhile. Generic deployments that 87% of employees ignore do not solve the problem — they add another tool to the pile. If your organization is evaluating centralized workspace options for financial services, the practical next step is to map your highest-friction information workflows first, then assess which platform controls address your specific compliance requirements. That scoping exercise will surface the questions worth asking in any vendor conversation. --- # 4 Ways Effective Document Management Improves Donor Retention **Author:** Anna Carriveau **Published:** 2019-09-17 **Category:** knowledge-management For charities and non-profit organizations, making a lasting difference is a way of life. Successful charities truly fulfill their mission and better the world one individual at a time. But non-profits can only achieve their goals and continue to influences others with regular and reliable donations. And while one-time donors are, of course, always appreciated, […] # 4 Ways Effective Document Management Improves Donor Retention Per the Fundraising Effectiveness Project, three out of four first-time donors do not give again. Non-profit leaders typically respond by refining stewardship programs, adding follow-up touchpoints, or improving thank-you sequences. Those interventions matter. But when donor retention audits trace the drop-off to specific moments — a volunteer who could not answer a question, a campaign brochure that contradicted last quarter's messaging, a donor who suspected their information was not handled carefully — the root cause is rarely the mission. It is the information infrastructure behind the people delivering it. Document management is not a glamorous investment. It is also one of the most direct levers non-profits have for ensuring that every volunteer interaction, every branded touchpoint, and every compliance filing either builds or erodes donor confidence. The four mechanisms below explain how — and what a governed document environment looks like in practice. ## Volunteers who cannot find information cannot retain donors Volunteers are the primary interface between most non-profits and their donors. They answer questions at events, follow up on campaign pledges, and represent the organization in every informal exchange. But volunteers are also high-turnover, often field-based, and operating without the access infrastructure that staff have: corporate email, VPN-accessible systems, and desktops designed for information retrieval at a desk. Per McKinsey research, employees spend an average of 2.5 hours daily searching for information. For a volunteer in the middle of a donor conversation, that search time does not compress — it either produces an answer or it does not, and the donor draws conclusions from that gap. Per a Banner Health employee survey, 55% of respondents wanted intranet access from a mobile device, and 61% wanted access outside the work VPN. Those figures describe the operational reality of field-based volunteers, not an edge case. Role-based document access, mobile-first availability, and governed [knowledge bases](/key-features/knowledge-bases) ensure that a volunteer on their first day has the same access to current campaign materials as a staff member of five years. Access is scoped automatically to the volunteer's campaign or region — reducing the risk that confidential donor data from one program surfaces in another's search results, and eliminating the manual provisioning steps that most non-profit technology teams do not have time to manage. ## Branding inconsistencies are document governance failures Non-profit branding is the mechanism through which donor trust is built or eroded over time. When a volunteer distributes a brochure contradicting the current campaign's language, or when a regional team emails an event recap using last year's visual identity, the inconsistency signals organizational fragility — even when the underlying mission is strong. Per Bloomerang and Fundraising Effectiveness Project research, non-profits that communicate impact clearly retain donors at rates up to 70% higher than those that do not. That consistency gap is almost always a document governance problem. Distributed teams working from shared drives, email attachments, and personal copies of older assets will produce divergent materials unless the system makes the current version the only accessible version. A [content governance engine](/key-features/content-governance-engine) enforces brand standards by controlling which templates and assets volunteers can modify. Real-time co-editing closes the version conflict problem that distributed teams otherwise manage through back-and-forth corrections and iteration loops. When governance is embedded in the platform, on-brand materials become the default output rather than the product of a manual review cycle that most non-profits do not have capacity to run consistently. ## Compliance documentation does not manage itself Non-profits operating across state, regional, or national boundaries face compliance obligations that multiply with their reach. Grant reporting, donor privacy regulations, and financial disclosure requirements all depend on document trails that are accurate, current, and auditable — and all three attributes require a structured governance environment rather than shared drives and inboxes. Per APQC research, Fortune 500 companies lose $31.5 billion annually due to knowledge loss, with the absence of structured document governance as a primary cause. For non-profits operating on thin margins, the proportional impact is steeper: grant disqualification, regulatory penalties, or reputational damage that takes years to recover from in donor relationships. The organizations most at risk are those maintaining compliance documentation manually, in personal drives or email threads rather than in governed systems with full audit trails. Version history and access logs address the compliance gap directly. When every document update is recorded, reversible, and attributable, compliance officers can demonstrate accountability to regulators and major donors without reconstructing the record from scattered sources. A document libraries solution that maintains full version history gives compliance teams the evidence they need without adding manual overhead to an already stretched operations function. ## Donor confidentiality depends on architecture, not policy For donors who give privately — major donors, institutional funders, or donors from sensitive populations — anonymity is a condition of continued giving, not a preference. When confidentiality is breached, most donors do not complain. They stop giving. Per the Banner Health employee survey, 59% of respondents reported difficulty finding needed information, and 63% said intranet content was not current or relevant. Those conditions create pressure to route around formal systems — sharing files informally, maintaining personal copies outside governed storage, or granting ad-hoc access to expedite a request. Each workaround is a potential confidentiality failure. Role-based permissions that sync automatically from HR records eliminate the workaround incentive. When a regional coordinator can access exactly the donor records needed for their campaign without requiring IT to intervene, the informal sharing pattern disappears — not through enforcement, but because the system makes the correct path the lowest-friction path. A [knowledge management](/solutions/knowledge-management) platform with HRIS-synced access controls updates automatically when volunteers join, change campaigns, or exit the organization, without the manual offboarding step that many non-profits miss. ## How to move from intent to implementation The most common barrier to improving document management in non-profit organizations is not budget. It is the absence of a governance plan before tools are deployed — producing a platform that replicates the same access and version problems at higher cost. A practical implementation sequence: **Audit before you architect.** Identify which documents volunteers request most often, which materials generate the most version confusion, and where compliance documentation currently lives. The goal is a folder and permissions structure that mirrors the campaign or regional org chart, not a migration of existing chaos into a new system. **Set baseline requirements early.** Mobile access and role-based permissions synced to HR records should be baseline requirements, not premium features. Per the Banner Health data, the majority of field-based workers expect access outside VPN and from mobile devices. A platform that requires VPN or a desktop browser is one that field volunteers will route around, reinstating the informal patterns that governance is meant to eliminate. **Treat version control as a compliance mechanism.** For non-profits operating across multiple jurisdictions, version history is the mechanism that demonstrates accountability when grant auditors or major donors request documentation of process. Evaluate platforms on the depth of the audit trail, not just the presence of a version history feature. **Measure adoption at the campaign level.** Page-level analytics on knowledge content identify which donor resources volunteers actually use. That data allows content owners to prioritize reviews, retire stale materials before they reach contributors, and verify that the governance structure is producing the findability it was designed for. For organizations evaluating the broader intranet and communication infrastructure that typically surfaces alongside a document management initiative, the [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent evaluation criteria that non-profit technology leads can apply directly to their platform selection process. ## The return is measurable across three dimensions Document management rarely appears in donor retention frameworks because its effect is indirect — it operates through volunteers, through brand consistency, through compliance confidence, and through the invisible architecture of donor privacy. But the return maps to three concrete numbers. Volunteer productivity: eliminating the 2.5-hour daily information search burden (per McKinsey) across a volunteer team of 20 recovers roughly 50 staff-hours per week that can be redirected to donor outreach. Donor retention lift: non-profits that communicate impact clearly retain donors at rates up to 70% higher than those that do not — and governed, on-brand materials are the mechanism that delivers that consistency. Compliance risk reduction: a single regulatory fine or audit failure costs far more than the annual licensing cost of a governed document platform. Three out of four first-time donors do not give again. The stewardship strategies that aim to change that ratio work better when every volunteer has access to current materials, every campaign document reflects a consistent identity, and every donor record is protected by architecture rather than by a policy document. Document management is what makes every other retention investment more effective — not instead of those investments, but underneath them. --- # Break Out Of A Creative Rut With Increased Company Collaboration **Author:** April Thomas **Published:** 2019-09-03 **Category:** company-collaboration In the entertainment and media industry, staying creative keeps the lights on. Without new, interesting, and entertaining material, it’s impossible to keep audiences captivated and engaged. And with ever-increasing competitive content, cutting through the clutter has never been more essential. But try as you might, creativity can not be forced. Thankfully, hitting a creative roadblock […] # Break Out of a Creative Rut With Company Collaboration Marcus runs creative for a regional entertainment company — 85 people, three studios, and a roster of remote contributors spread across two time zones. Last spring, his team spent four days circling the same three concepts for a broadcast pitch that needed to feel genuinely fresh. Two of his strongest writers were remote. A new hire who had spent the past decade producing content for the exact demographic the pitch was targeting didn't know the project existed. By the time the team realized they were stuck, the deadline had moved from comfortable to urgent. The problem wasn't a lack of ideas. It was the infrastructure those ideas had to travel through to become visible. Creative blocks in media and entertainment rarely start with imagination running dry. They start with friction: time employees spend hunting for context they can't locate, colleagues they can't reach easily, and examples buried in a project folder someone linked two years ago and no one has found since. Per Gartner (2023), 47% of workers struggle to find necessary information at least half the time. For creative teams working across shifts, studios, or time zones, that number isn't abstract — it's a direct drag on the quality of ideas they can generate under pressure. This is the version of the creative rut that company collaboration tools are built to solve. Not the personal kind — the structural kind. --- ## Why isolation, not imagination, causes most creative blocks The default diagnosis for a creative rut is personal: someone burned out, ran dry, or lost the thread. That framing is convenient but usually wrong for teams. When a creative team cycles through the same ground repeatedly, it's almost always because the pool of inputs they're drawing from has gotten too small. Writers talk to the same writers. The visual team has its own channel. New hires ask questions that senior colleagues answered thoroughly in a project file no one linked them to. The fix isn't a forced brainstorm session — it's expanding the surface area of who and what the team can actually access. Collaboration platforms that unify communications, search, and workflow automation reduce this friction directly. A team member looking for context on a past campaign shouldn't have to send three messages and wait for a response from whoever happens to be online. A remote contributor shouldn't miss an ideation thread because the discussion happened in a meeting they weren't on. When the infrastructure closes those gaps, the actual creative problem — what should the idea be — becomes the one the team spends energy on. The connection to [employee engagement](/solutions/employee-engagement) outcomes is direct. Employees who feel isolated from the knowledge and people they need to do their jobs well don't just produce worse work — they disengage. Per McKinsey research, 89% of frontline workers say they will stay with their companies if leaders listen to their feedback. Collaboration tools are one of the most direct channels for making that listening happen at scale, not just in quarterly engagement surveys. --- ## How broader access changes what creative teams can generate Creativity, stripped to its mechanics, is pattern-matching across a wider-than-expected set of inputs. Individual experience has a ceiling. Team knowledge doesn't — provided people can actually get to it. When Marcus's team finally had a unified workspace where remote contributors could search previous campaigns, leave threaded comments on active projects, and surface connections between current briefs and past work, the pitch that had stalled for four days came together in a single afternoon. The idea didn't originate from a senior writer or a new hire working alone — it came from a comment a remote video editor had left on a three-year-old campaign file, surfaced when someone searched for a keyword from the brief. That's not a story about better brainstorming technique. It's a story about search infrastructure. For creative teams, three collaboration capabilities tend to move the needle most: **Unified search across messages, files, and projects.** The most common version of a creative block is someone not being able to find something they know exists somewhere. Per the *State of the Digital Workplace & Modern Intranet, 2024*, only 22% of company intranets deliver personalized content — meaning most employees navigate generic feeds rather than surfaces tuned to their role and active work. Teams on platforms that surface relevant content by context report faster orientation on new briefs and less time spent re-explaining decisions that were already made. **Mobile access for distributed contributors.** Creative teams in entertainment aren't uniformly office-based. Set designers, location coordinators, remote writers, and production staff all need access to the same collaboration layer as people in the building. Mobile-first platforms that don't require VPN or corporate email close this access gap without adding IT complexity. When remote and frontline contributors can add to a shared ideation space from their phones in real time, the range of ideas that surface is genuinely wider. **Asynchronous ideation channels.** Real-time brainstorming has a selection bias problem: it favors whoever speaks first and loudest in a meeting room. Asynchronous group channels let team members contribute on their own schedule and at their own pace. For contributors across time zones, this isn't a preference — it's the only realistic path to full participation. --- ## The excluded contributor problem One consistent pattern in media and entertainment organizations is that the employees with the most direct audience exposure — production staff, event crews, client-facing coordinators — are the least likely to be part of early creative conversations. This is partly logistical: they're not in the building when a brief gets discussed, they don't have accounts on the same tools as the core creative team, and their feedback tends to enter the project after it's already been through several rounds of revision. The result is that creative teams regularly miss inputs that would have sharpened their ideas earliest. The employee engagement strategies that address this are mostly about removing access barriers rather than running special inclusion programs. A collaboration platform with mobile onboarding, searchable group channels, and role-based content feeds can connect a field coordinator's insight to a creative brief before the first draft exists — not after the final version is locked. Per McKinsey research, 81% of leading companies effectively use data and analytics tools to drive performance. A significant share of that data is the unstructured knowledge and direct feedback that employees outside the immediate creative circle are carrying. Making that knowledge searchable and accessible is both a technology decision and an employee engagement strategy. --- ## What the transition to connected collaboration looks like Organizations that break creative ruts consistently at the team level tend to share a few structural characteristics. They've reduced the number of systems their contributors navigate daily. They've built searchable archives of past work that new hires can access without asking anyone. They've given remote and mobile contributors the same access to ideation and communication channels as office-based staff. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents how leading organizations are building these rhythms into their communication cadence — including the shift from ad-hoc collaboration requests to always-on channels where ideas accumulate over time rather than disappearing after each meeting. For teams navigating high turnover and frequent audience changes, the principles from [Closing the Information Gap in Performance Reviews](/articles/closing-the-information-gap-in-performance-reviews) translate directly: centralized knowledge, searchable history, and connected contributors close information gaps in creative workflows for the same reasons they close them in performance-review processes. The infrastructure is the same; the application changes. --- ## Measuring whether collaboration investment is paying off The most common failure mode after deploying a collaboration platform isn't low adoption — it's the wrong metrics. A team watches usage climb and assumes creative output follows. But high message volume doesn't mean the friction that was blocking idea generation has actually been removed. The signals that matter for creative teams are more specific: time from brief to first viable concept, frequency of cross-team contributions to active projects, and the proportion of final ideas that incorporated input from outside the core creative group. Employee engagement surveys that include items on information access and collaboration quality — not just general job satisfaction — give managers a sharper read on whether the infrastructure is working or just being used. Organizations that tie engagement survey results to specific collaboration behaviors tend to surface friction points before they show up in turnover data or missed deadlines. For operations and HR teams building these measurement frameworks into annual planning, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) documents the approaches gaining traction among distributed workforce organizations. --- ## The infrastructure argument The traditional advice for creative ruts is individual: try something new, talk to someone outside your field, take a break and return with fresh eyes. That advice isn't wrong — it's just incomplete for teams under deadline pressure. When nearly half of workers already struggle to find information they need at least half the time (per Gartner, 2023), telling a creative team to "just collaborate more" without addressing the underlying infrastructure is like prescribing effort when the problem is tooling. The recommendation is directionally right but ignores what's actually slowing the team down. The practical shift is infrastructure-first: give the team unified search so they can find what already exists; give remote and mobile contributors the same access as desk-based staff; build asynchronous channels where ideas accumulate over time rather than disappearing after each meeting. When those elements are in place, the individual strategies — cross-pollinating with colleagues in adjacent roles, helping a peer through a different kind of problem, stepping away and returning to a brief with fresh eyes — become genuinely effective rather than individually heroic efforts against structural friction. The creative rut breaks not because someone had a breakthrough. It breaks because the team's combined knowledge finally became accessible enough to act on. --- # Why You Need Video Messaging for Corporate Communication **Author:** April Thomas **Published:** 2019-08-20 **Category:** modules-features Corporate communication is a crucial part of every organization. Leaders need a way to share news globally, motivate employees, and establish a strong company culture. But most of the time corporate contact just feels flat. Even if the content is important, messages tend to be impersonal, unrelatable, or just boring. Despite their best efforts, executives […] # Why You Need Video Messaging for Corporate Communication Corporate communication is a crucial part of every organization. Leaders need a way to share news globally, motivate employees, and establish a strong company culture. But most of the time corporate contact just feels flat. Even if the content is important, messages tend to be impersonal, unrelatable, or just boring. Despite their best efforts, executives will never be able to personally meet every employee, and yet, without some kind of personal connection corporate communication is doomed to stay uninspiring. Video messaging changes that equation directly: it delivers the tone, body language, and authenticity that written memos cannot, and it reaches employees wherever they work — at a desk, on a shop floor, or on a mobile device. **Here are four of our favorite reasons companies need video messaging for their corporate communication:** ## Actively Engage Your Audience Showing employees you understand, appreciate, and support their work without losing your sense of leadership can be a difficult balance. But video communication tools help corporate leaders bridge the gap between empathetic and authoritative. Video messages, while still professional, are naturally more down to earth than official company newsletters or written communication. Employees connect more strongly when they are able to see a face, hear a voice, and watch a real reaction. Employees instead are able to recognize management as individuals who care about their unique needs and provide transparent communication they can actually trust. The stakes are real: per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback — and video is one of the most direct signals that leadership is listening. While video messages obviously aren't appropriate for every situation, well-placed videos allow management to reach out personally to employees, increasing empathy, engagement, and dedication throughout the organization. Explore [employee engagement strategies](/solutions/employee-communications) and how video fits into a broader communications plan. ## Share Every Part Of A Message Video messages don't just make communication more relatable, they actually increase understanding as well. While words are of course the main focus of a message, a large part of comprehension also comes from recognizing non-verbal communication. Facial expressions and body language, voice tone and intonation, and even where or how a speaker stands all work together with words to create a complete picture. When communication is only shared in writing or verbally passed down a chain of command, important clarification details are often missed or misunderstood. This is especially true in verbal only communication, where individual interpretations can easily creep in. Video messages help management create clear and easy-to-understand information by presenting a single source of truth where employees can see every aspect of communication. Platforms that combine video messaging with AI-powered search and tagging allow employees to surface the right video content instantly, rather than hunting through archives — a capability that matters especially when 47% of workers struggle to find necessary information at least half the time, per Gartner, 2023. For a deeper look at how communication gaps affect performance, see [Closing the Information Gap in Performance Reviews](/articles/closing-the-information-gap-in-performance-reviews). ## Communicate In The Moment Unlike drawn-out written communication, videos are simple to make, easy to share, and ready to go almost instantly. With video tools leadership can respond to employee questions and concerns or share company news at any time. Video messages give leaders the freedom to address issues in the moment. This helps eliminate confusion, prevent rumors, and keeps everyone on track and informed. Short, regular, video updates are also a fantastic tool for creating authentic communication at the corporate level, demonstrating to employees first hand that their management is aware of relevant issues in the organization, stays in touch with day-to-day activities, and values openness and honesty at every level. Video communication tools that include built-in analytics — view rates, completion rates, and engagement depth by location or role — let communications teams prove message reach and optimize future broadcasts, a gap that email-only approaches cannot close (per Akumina and MangoApps product benchmarks). The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading teams are measuring communication effectiveness today. ## Show Technological Success In business, adaptation is essential. As the world advances and society changes, businesses need to evolve as well or risk becoming obsolete. Part of adapting also includes embracing new technology. From enterprise social networks to eco-friendly initiatives, companies who understand and utilize important innovations stay ahead of the competitive curve. And when it comes to communication, video messaging is right at the forefront. Business video messaging incorporates long-term recreational tools into a successful company environment, creating quick, clear, and concise communication. And video tools instill confidence in employees as well. Successfully incorporating video messaging reassures employees that their organization is aware of industry changes and ready to adapt as needed. Per McKinsey research, 81% of leading companies effectively use data and analytics tools — and video analytics is increasingly part of that picture. For context on how MangoApps fits into the broader intranet landscape, see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms). ## Video Messaging With MangoApps At MangoApps, we understand the difficulties executives face trying to create engaging and effective corporate communication. So we've made the process as simple, interesting, and intuitive as possible. With MangoApps' video capabilities, sending high-quality company communication only takes a couple of clicks. In minutes leaders can easily create a post, record a message, and broadcast their announcements to either the entire company or a selected team. And with TinyTake, our helpful screen capture and video recording software, management can even annotate screenshots, record their screens, or screen share across the company. For organizations with large frontline or deskless workforces, mobile-first video delivery is especially critical. Deploying a mobile-first video communication channel for a predominantly frontline workforce can achieve 90%+ adoption within the first six months when paired with a unified intranet platform (per Unily / CVS and British Airways case studies). One 40,000-employee airline workforce achieved a 91% platform usage rate after rolling out a mobile-first video and intranet solution in just eight weeks. See how a similar approach enabled [Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology). Corporate communication doesn't have to be dry, impersonal, or confusing. With the right tools, video messaging, company announcements, and employee engagement all come quickly and intuitively. --- ## How Do I Get Started with Video Messaging for Internal Communications? Getting started does not require a large production budget or a dedicated media team. Most organizations begin with three steps: 1. **Choose a platform with native video support.** Look for tools that allow recording, uploading, and broadcasting from a single interface — and that support mobile playback for frontline employees. MangoApps' [employee app](/solutions/employee-app) includes these capabilities out of the box. 2. **Define your use cases first.** Executive town halls, team updates, onboarding walkthroughs, and safety briefings each have different format requirements. Starting with one high-value use case (such as a weekly leadership update) builds the habit before scaling. 3. **Measure from day one.** Track view rates, completion rates, and employee responses. Only 22% of company intranets currently deliver personalized content, per the State of the Digital Workplace & Modern Intranet, 2024 — video analytics help close that gap by showing which messages actually land. For a broader framework on building communication into daily workflows, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) offers a useful parallel. ## What Are Common Pitfalls When Rolling Out Video Messaging? Even well-intentioned video programs stall. The most common failure points are: - **Treating video as one-way broadcast only.** Without AI-assisted tagging, transcription, and search, video content becomes a growing archive that employees cannot navigate. Discoverable video — where employees can search by topic, speaker, or date — dramatically increases long-term value. - **Ignoring frontline and mobile workers.** Articles and intranets that focus only on desk-based employees miss the majority of many workforces. Eurostar reported a 253% increase in employee engagement after adopting a unified communications platform with video capabilities that reached all worker types. - **Skipping the measurement layer.** Without view-rate and completion data segmented by role or location, communications teams cannot demonstrate ROI or identify which employee groups are being missed. Employee engagement software with built-in reporting closes this loop. - **Inconsistent cadence.** Sporadic video updates undermine the authenticity benefit. A predictable schedule — even a brief weekly update — builds trust faster than occasional high-production broadcasts. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how organizations are structuring communication cadences for hybrid and frontline teams. ## Is Video Messaging Enough on Its Own, or Does It Need a Broader Strategy? Video messaging is most effective as one layer within a broader employee engagement strategy, not a standalone fix. Organizations that see the strongest results pair video with: - **Structured feedback channels** — so employees can respond to what they watch, not just receive it - **Employee engagement surveys and questionnaires** — to measure whether video communication is actually shifting sentiment and comprehension - **A unified intranet or employee app** — so video, documents, announcements, and social recognition live in one place rather than scattered across email, chat, and shared drives A 30-point increase in employee engagement score has been attributed to social and AI-assisted video reporting tools within one year of deployment, demonstrating that video works best when embedded in a platform that connects communication to action. For industry-specific applications, see how these principles apply in [healthcare](/industries/healthcare) and [financial services](/industries/financial) environments. To learn more about MangoApps or how video messaging strengthens corporate communication, contact us or schedule a personalized demo today. **Schedule Demo** --- # Successful Client Communication in the Profession of Services **Author:** April Thomas **Published:** 2019-08-13 **Category:** industry-insights Professional service organizations work directly with clients every day completing projects and performing services. For these employees, successful client communication isn’t just a convenience, it’s essential for any kind of business success. Ineffective communication in the professional services industry leads to unhappy clients, unclear expectations, confusing results, and frustrated employees. Not exactly the ideal work […] Professional services organizations run on relationships. The quality of the work matters — the strategy, the deliverables, the domain expertise — but so does the experience of working together over the life of an engagement. And more client relationships erode from communication failures than from delivery failures. Per Gartner's 2023 research, 47% of workers struggle to find necessary information at least half the time. For client-facing professional services teams, that figure isn't abstract: it's the status update a client is still waiting for, the file that exists in three versions across four platforms, the decision that got made in a chat thread but never made it back to the shared project record. The friction is structural, not interpersonal. Most professional services teams have capable, well-intentioned people who genuinely want to serve their clients well. What erodes communication is the combination of fragmented tooling, undocumented expectations, and improvised processes that were never designed to hold together under the pressure of active delivery. The communication failures that most commonly cost professional services firms client trust follow predictable patterns — and each one is fixable. ## When your team uses too many tools The most common professional services communication failure isn't a conversation that went badly. It's a message that arrived in the wrong place, or a decision that lived in one platform while the client was checking another. Fragmented tool stacks — email for formal updates, chat for quick questions, a separate project management app for task tracking, and a client portal for document review — force teams to context-switch constantly. Every platform becomes a partial record. A client follows up on something discussed over chat, but the relevant decision was confirmed in an email thread that none of the current team members can locate. Version-control errors multiply. Updates arrive out of sequence. Client confidence erodes not because the work is poor, but because the process feels disorganized. The fix is channel consolidation: designating a single primary form of communication that both your team and your client agree to use for substantive updates, with other channels reserved for specific, documented exceptions. A unified [employee communications platform](/solutions/employee-communications) that supports role-based delivery, mobile access, and secure file sharing addresses most of these failure points in one place. Organizations that have moved to a unified communications hub have achieved 95% employee adoption rates across large distributed teams — and reliable client communication depends first on consistent internal coordination behind it. ## When expectations live in your head The second failure mode is the assumption gap. Engagements frequently begin with verbal alignment that feels solid in the kickoff meeting and quietly fragments within weeks as each party's mental model of scope, success criteria, and process diverges. Assumptions are most dangerous when they're invisible. Your team defines project completion as final deliverable handoff. Your client defines it as full implementation with training complete. Neither party flagged the difference because it seemed obvious to each of them — until the final milestone arrives and the conversation becomes difficult. The rework, the extended timeline, and the relationship friction that follow are all more expensive than the hour it would have taken to write down shared definitions at the start of the engagement. The fix is a written engagement foundation — what some teams call an operations manual for the engagement. Before work begins, document project scope, success criteria, escalation contacts, decision rights, and how status will be communicated. This document should live somewhere both parties can access at any time, not buried in an email thread that requires scrolling through 200 messages to find. Per Gartner's 2023 data, 47% of workers struggle to find necessary information at least half the time; clients experience the same friction when shared agreements aren't maintained in a consistently accessible location. ## When clients don't know what's happening Progress updates are the most visible form of communication in a professional services engagement — and among the most consistently mismanaged. Professional services teams tend to under-communicate during active delivery. The team is heads-down on the work and assumes the client understands that silence means progress is happening. Clients rarely interpret it that way. Silence reads as disorganization, missed milestones, or uncertainty — and clients compensate by requesting status updates more frequently, which interrupts delivery and compounds the problem. The fix is a predetermined update cadence: a structured, documented rhythm that both sides expect and can rely on. Shorter, more frequent updates consistently outperform longer monthly reports — not because they carry more information, but because they make clients feel continuously informed rather than periodically briefed after the fact. Role-based communication delivery ensures that updates reach only the stakeholders who need them, reducing noise for clients and internal teams alike. When the cadence is documented from the start of an engagement, neither party spends time negotiating communication frequency mid-project. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations structure update cadences that keep stakeholders consistently informed without creating the fatigue that causes important updates to be ignored. ## When expertise becomes a barrier instead of a bridge Every professional services firm brings specialized knowledge — that's what clients hired you for. The challenge is making that expertise legible rather than simply exercising it. When you deliver a recommendation without the reasoning behind it, clients face a choice between accepting it on trust or questioning it without enough context to do so constructively. Neither outcome serves the relationship. Unexplained recommendations generate follow-up questions, delayed approvals, and escalations that slow delivery and test patience on both sides. The alternative — explaining the why behind significant decisions in accessible language — takes more time in individual conversations and reduces total elapsed time by preempting the questions that would otherwise arise. The reciprocal matters equally. In business-to-business professional services, your client typically has deeper domain expertise in their own industry than you do. Treating every engagement as a mutual knowledge exchange — actively soliciting client input on industry-specific constraints, competitive context, and internal stakeholder dynamics — produces better deliverables and stronger relationships than one-directional expertise delivery. Per McKinsey research, 89% of frontline workers will stay with their companies when leaders actively listen to their feedback. The same principle applies in client relationships: clients who feel heard on concerns and suggestions are measurably more likely to deepen engagements and refer others. Structured employee communications training for client-facing teams formalizes this two-way exchange and makes it consistent across engagements rather than dependent on individual relationship style. ## When something breaks down Even with strong documented process, consistent updates, and clear expertise-sharing, communication breakdowns happen. How a firm responds is often more determinative of the long-term relationship than whether the breakdown occurred at all. The failure mode here isn't the breakdown itself — it's the absence of a predefined response path. Teams that establish conflict resolution protocols at engagement kickoff — who the single point of contact is on each side, what constitutes a formal escalation versus a routine correction, which medium moves from asynchronous to synchronous when tension is high — execute cleanly when problems arise. Teams that improvise conflict resolution under deadline pressure almost always make the situation more difficult than it needs to be. Tracking communication breakdowns systematically creates pattern recognition that compounds over time. Per McKinsey research, 81% of leading companies effectively use data and analytics tools. Applying that discipline to communication incidents — not just delivery metrics — lets you identify recurring failure modes and update your engagement documentation to address them proactively. One breakdown becomes a standing prevention across future engagements. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how operations teams build measurement infrastructure that converts incident data into durable process improvement. ## The structural pattern that separates strong communicators The firms that consistently deliver strong client communication share one characteristic: they've removed structural friction rather than relying on individual talent or relationship intuition. A unified [employee app](/solutions/employee-app) that brings together messaging, file sharing, and project updates in one interface removes the context-switching burden that fragments client communication at its source. Written engagement foundations replace verbal assumptions with shared, accessible operating reality. Structured update rhythms replace silence with predictable cadence. Documented escalation paths replace improvised conflict resolution with clean, consistent execution. Per the State of the Digital Workplace and Modern Intranet report, 2024, only 22% of organizations have personalized their internal communications infrastructure. The firms that have built consistent, documented, measurable communication systems operate with a structural advantage over competitors who still rely on tool sprawl and individual relationship skill to hold engagements together. The investment in communication infrastructure is front-loaded. The return compounds across every engagement that renews, every client who refers another, and every breakdown that doesn't happen because the escalation path was already in place. Client retention and referrals are measurable outcomes of process quality, not personality — and the firms that track those metrics consistently find that communication infrastructure is the variable that most reliably moves them. The firms that wait to address it structurally — hoping the next skilled hire will fix the problem — continue cycling through the same breakdowns at increasing cost. --- # How To Motivate Frontline Employees **Author:** April Thomas **Published:** 2019-08-07 **Category:** integrated-digital-workplace Frontline employees are the foundation of many successful organizations. Rather than working in an office, frontline employees are on the literal front lines of their industry. Frontline workers make up 70% of the world’s workforce. They are the retail staff, hospitality crews, and many other employees, that directly impact customer care and product success. In […] # How To Motivate Frontline Employees Frontline employees make up 80% of the global workforce (per Emergence Capital), yet they are consistently the hardest group to keep engaged. If you manage a frontline team in retail, hospitality, healthcare, or any other field-based industry, here are the five tactics that move the needle most: 1. **Give every worker mobile-first access** — no corporate email or VPN required. 2. **Consolidate tools into one app** — shifts, forms, training, and HR self-service in a single place. 3. **Replace broadcast messages with targeted alerts** — segmented by role, location, and team. 4. **Recognize contributions publicly** — peer shoutouts and manager recognition visible to the whole organization. 5. **Empower frontline decision-making** — give workers the information and authority to resolve issues without escalating every problem. The sections below explain why each tactic matters and how to put it into practice. --- ## Why Frontline Engagement Is a Balance-Sheet Problem, Not Just an HR Concern Disengaged frontline employees do not just underperform — they leave. Replacing a single frontline employee costs between $4,400 and $15,000 (per MangoApps mobile app product page, citing industry research). Multiply that across a workforce of hundreds or thousands, and disengagement becomes a direct financial risk. According to [Gallup's 2026 State of the Global Workplace: What It Means for HR, ...](/articles/gallup-2026-state-of-the-global-workplace), employee engagement levels remain stubbornly low across most industries, with frontline workers consistently scoring below their office-based counterparts. The causes are structural, not motivational — and fixing them requires structural solutions. --- ## The Four Structural Barriers That Undermine Frontline Motivation ### 1. Legacy Tools That Don't Fit the Job Frontline workers are physically separated from technology decision-makers. The result is that equipment decisions get made by people who never use the equipment. Outdated tools create data inaccuracy, slow workflows, and signal to frontline staff that their working conditions are an afterthought. When employers do invest in technology for frontline employees, it rarely meets their actual requirements. In a global survey, over a third of frontline respondents said that while their company invests significantly in technology, it does not make their work any easier. Constantly working around office-centered tools costs time and erodes trust in leadership. ### 2. Information That Never Reaches the Front Line Employees spend an average of 2.5 hours per day searching for information they need to do their jobs (per IDC). For frontline workers without a desktop or a reliable intranet connection, that number is likely higher — and the consequences are more immediate. A retail associate who cannot quickly find a product specification or a return policy creates a poor customer experience in real time. Limited information also prevents frontline employees from fully utilizing their benefits, understanding policy changes, or acting on company news. The problem compounds when workers lack a mobile-accessible source of truth they can consult mid-shift. AI-curated content feeds and real-time translation across 50+ languages can address both the information access gap and the language diversity common in frontline workforces — ensuring the right content reaches the right worker in the right language without requiring manual segmentation by managers. ### 3. Communication That Gets Distorted in Transit For most frontline workers, company information travels through top-down channels: corporate to regional management to store or site managers to individual teams. Each handoff introduces delay, interpretation, and inconsistency. Some managers communicate well; others do not. The result is that two employees doing the same job in different locations may be operating on different information. This structure also signals a lack of respect. When frontline employees receive filtered, secondhand information, they correctly infer that leadership does not consider them a primary audience. That perception drives disengagement faster than almost any other factor. Personalized push notifications, SMS, and in-app alerts — segmented by role, location, and team — measurably outperform top-down broadcast communication for frontline reach (per MangoApps frontline engagement product page). Direct communication is not just faster; it is a statement that frontline workers matter. ### 4. Unapproved Apps That Create Security and Compliance Risk When official communication channels fail, frontline employees find alternatives. Consumer messaging apps fill the gap — and create a significant security exposure. Long-term reliance on unsecured apps puts company data at risk and can violate HIPAA, NDAs, and other industry compliance requirements. Employees caught using unapproved apps can trigger audit failures or licensing consequences, even without an actual breach. The fix is not to prohibit workarounds — it is to provide a sanctioned alternative that is genuinely easier to use than the workaround. --- ## Mobile-First Access Is a Prerequisite, Not a Feature The single most common reason frontline engagement programs fail is that the tools require a corporate email address or VPN to access. Frontline employees rarely have either. A no-email, no-VPN login model is the architectural baseline that any frontline engagement solution must meet — everything else is secondary. According to Emergence Capital, 80% of the global workforce is deskless. Yet most intranet platforms are built for the 20% who sit at desks. Per Social Edge Consulting, 91% of organizations operate an intranet, but nearly a third of employees never log in to it, and only 13% use it daily. SWOOP Analytics found that the average employee spends just six minutes per day using intranet tools. These numbers reflect platforms designed for office workers, deployed to people who work on their feet. For [retail](/industries/retail), [hospitality](/industries/hospitality), and other frontline-heavy industries, a mobile app that workers can access from their personal device — without IT provisioning — is the difference between a communication platform that gets used and one that gets ignored. --- ## Consolidating Tools Removes the Friction That Kills Engagement Tool-switching is a hidden productivity and engagement tax. Consolidating shifts, forms, training, HR self-service, and IT requests into a single mobile app eliminates the switching cost that can consume more than four hours per week per employee (per MangoApps unified platform product pages). Beyond efficiency, consolidation matters for adoption. Frontline workers will not use five separate apps for five separate functions. They will use one app that handles everything — or they will use none of them and revert to informal channels. A branded employee app also functions as a trust and identity signal. When an organization invests in a purpose-built, branded experience for its frontline workforce, workers notice. That investment communicates that the organization takes their experience seriously. The results are measurable: OU Health achieved 87% workforce engagement within a few months of launching a branded mobile app (OU Health case study). PetSmart reported a 4x industry engagement multiple after deploying a branded employee app (PetSmart case study). CVS reached 90% frontline adoption within the first six months of platform deployment (CVS case study). For organizations exploring what a consolidated platform looks like in practice, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading organizations are restructuring their tool stacks around frontline needs. --- ## Recognition and Training Are Engagement Multipliers Motivation is not sustained by access alone. Frontline employees need to feel that their contributions are visible and valued — and that the organization is investing in their growth. Public recognition — peer-to-peer shoutouts, manager acknowledgments, and milestone celebrations visible across the organization — closes the visibility gap that top-down communication creates. When a frontline worker's achievement is visible to colleagues and leadership, it reinforces that their work matters. Employee engagement training and structured learning embedded in daily workflows compound this effect. Workers who see a path for development are more likely to stay. For a deeper look at how to make learning stick without pulling frontline workers off the floor, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). Employee engagement surveys and questionnaires — delivered through the same mobile app workers use for everything else — give leadership a continuous signal on what is working and what is not, without requiring frontline workers to sit at a computer to respond. --- ## What Good Frontline Employee Engagement Software Actually Does Not all [employee engagement](/solutions/employee-engagement) platforms are built for frontline realities. When evaluating employee engagement software, the criteria that matter most for frontline workforces are: - **No-email, no-VPN login** — workers access the platform from their personal device without IT provisioning. - **Role- and location-based content segmentation** — a warehouse associate in Phoenix sees different updates than a store manager in Boston. - **Offline functionality** — the app works in environments with intermittent connectivity. - **Integrated shift management and HR self-service** — workers can view schedules, request time off, and access pay information in the same place they read company news. - **Compliance-safe communication** — all messaging stays within a governed environment, eliminating the security risk of consumer apps. - **AI-powered personalization** — content feeds surface what is relevant to each worker's role, location, and language without requiring manual curation. For organizations that want an independent benchmark, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) evaluates platforms specifically on their frontline and deskless worker capabilities. --- ## Frequently Asked Questions ### How do you measure frontline employee engagement? The most reliable signals are a combination of quantitative and qualitative data: pulse survey scores (delivered via mobile), platform adoption rates, shift completion and absenteeism trends, and voluntary turnover rates segmented by location and role. Employee engagement questionnaires sent through the same app workers use daily achieve significantly higher response rates than email-based surveys, because frontline workers rarely have corporate email access. Tracking these metrics over time — rather than running a single annual survey — gives HR teams an early warning system for disengagement before it becomes attrition. ### What is the difference between employee engagement and employee enablement? Engagement measures how motivated and connected employees feel. Enablement measures whether they have the tools, information, and authority to do their jobs effectively. The two reinforce each other: a worker who is motivated but lacks the right tools will become frustrated; a worker who has every tool but feels invisible will disengage. Frontline motivation programs that address only one dimension tend to produce short-term improvements that fade. The most durable gains come from addressing both simultaneously — which is why consolidating tools and improving communication belong in the same initiative as recognition and development. ### How long does it take to see results after deploying a frontline engagement platform? Adoption timelines vary by organization size and change management investment, but the case study data points to meaningful results within the first six months. CVS reached 90% frontline adoption within six months (CVS case study). OU Health saw 87% workforce engagement within a few months of launch (OU Health case study). The organizations that move fastest share two characteristics: they involve frontline workers in the platform selection process, and they launch with a small set of high-value use cases (shift management, direct messaging, and company news) before expanding to additional features. --- ## The Concrete Next Step Frontline employee motivation is not a culture problem that resolves itself with better values statements. It is an infrastructure problem: the wrong tools, the wrong communication architecture, and the wrong information access model for the people doing the work. The path forward is specific: 1. Audit your current frontline communication stack. Identify every tool that requires a corporate email or VPN — those are your access barriers. 2. Calculate your current frontline turnover cost using the $4,400–$15,000 replacement cost range as a baseline. 3. Evaluate employee engagement software against the no-email, mobile-first criteria above — not against feature lists designed for office workers. 4. Run a pilot with one location or team before a full rollout, using adoption rate and pulse survey scores as your success metrics. 5. Expand based on what the data shows, not on assumptions about what frontline workers want. For organizations in specific verticals, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how frontline engagement strategy is evolving across industries — and what the highest-performing organizations are doing differently. --- # Strengthen Education with Collaboration Tools **Author:** April Thomas **Published:** 2019-07-23 **Category:** company-collaboration Universities are used to providing students with the best tools available, but what about the resources instructors need? For most educators, accessing reliable resources usually includes searching through mountains of emails, attending endless meetings, or paying for a service out-of-pocket. University employees spend countless hours just organizing their own classes, let alone trying to collaborate […] # Strengthen Education with Collaboration Tools Every university has a digital infrastructure problem hiding in plain sight. Student-facing systems — learning management platforms, enrollment portals, student email — are regularly evaluated, upgraded, and benchmarked against peer institutions. The tools faculty and staff use to do their jobs receive far less scrutiny. The result is an institution where a student can check their grades at midnight from a personal phone, while the adjunct professor who graded that exam cannot access department policy documents without a VPN or a campus-provisioned device. Per Gartner's 2023 Digital Worker Survey, 47% of workers struggle to find necessary information at least half the time. In a university setting, that number compounds across every semester: rotating research teams lose institutional knowledge when one cohort graduates and the next arrives; adjunct faculty on heavy course loads have no time to navigate three separate systems to find a curriculum update; campus operations staff working evening shifts cannot reach the collaboration platform until the next morning. The collaboration gap in higher education is not a communication problem. It is an infrastructure problem — and it carries a measurable cost. ## The university workforce looks more like frontline workers than desk workers The framing matters. When administrators think of "employees," they typically picture office staff with corporate email and regular access to enterprise systems. The actual university workforce is more distributed and access-constrained than that picture suggests. Adjunct faculty make up a significant share of teaching staff at most institutions — often without dedicated office space, company-managed devices, or reliable access to campus systems between classes. Field researchers may be off-campus for weeks collecting data. Campus operations staff — facilities, dining, security — work shift schedules that do not align with standard IT support hours. Per a Banner Health employee poll, 61% of employees want intranet access outside the work VPN. The same dynamic plays out in higher education: a faculty member driving between campuses or an operations supervisor working a night shift cannot pause to log into a desktop-only system. Infrastructure that requires a campus network or a corporate email address to function structurally excludes a significant portion of the workforce — not by design, but by default. This access gap shows up in engagement over time. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), employees who feel the organization is not investing in their experience disengage faster. University workers who cannot reach the tools they need default to workarounds — group chats, shared drives with no governance, email threads that bury institutional knowledge — and those workarounds create the fragmentation that makes the next information search harder still. ## The ROI case for consolidation The standard objection to platform consolidation in higher education is that universities are not businesses and the ROI framing does not apply. The objection misidentifies the relevant evidence: administrators need operational benchmarks, not financial projections. Organizations that have completed structured intranet rollouts report a 95% employee adoption rate for a 5,000-person workforce merged through acquisition — a useful parallel for multi-campus institutions managing complex communication across sites. Organizations deploying unified employee platforms report a 52% decrease in IT support requests, a number that maps directly to the help-desk overhead university IT departments consistently flag as a constraint on higher-value work. Per a Banner Health employee survey, 63% of employees said intranet content was not current and relevant. For a university department, that translates directly: if the platform that should surface policy updates, grant deadlines, and curriculum changes is perceived as stale, faculty stop checking it. The information exists in the system; institutional trust in the channel does not. Governance tooling — structured content ownership, role-based publishing, automatic expiration dates on time-sensitive posts — closes that perception gap more reliably than any communications campaign. Per the State of the Digital Workplace and Modern Intranet, 2024, only 22% of company intranets have personalized content. The majority of university platforms deliver the same undifferentiated feed to a lab researcher, a dining services supervisor, and a department chair. Persona-driven delivery — where each role sees the content relevant to their function and location — increases both adoption and trust in the channel, because the content arriving in the feed is consistently relevant to the person reading it. ## Where fragmentation actually costs hours The collaboration cost of fragmented tools is not abstract. It appears in specific workflows that repeat every semester. **Research knowledge continuity.** Research projects rotate teams of graduate students, undergraduate research assistants, and faculty leads. Without a centralized platform for project documentation, each rotation starts with a partial handoff: a folder of files emailed from the outgoing researcher, a shared drive with inconsistent naming conventions, and verbal briefings that document nothing durably. A knowledge management tool with contextual search surfaces prior proposals, field notes, and IRB submissions by context — not just by file name — so new team members spend less time reconstructing what was already known and more time advancing the work. **Cross-department coordination.** A business school offering a joint internship track with the engineering department needs a [structured communication channel](/solutions/employee-communications) that creates a searchable record. An ad hoc email thread does not. When the joint track runs again next year, neither department has institutional memory of how the first cohort was structured, which partner organizations participated, or what the onboarding logistics looked like. A shared collaboration space solves this — not as a convenience feature, but as the mechanism that allows a multi-department initiative to build on its own history year over year. **Adjunct onboarding at scale.** Universities with large adjunct populations onboard dozens of instructors every semester — each needing access to course materials, department policies, and IT systems. An onboarding workflow that depends on IT provisioning a new email account before day one creates a delay that is resolved either through workarounds (shared accounts, physical printouts) or results in faculty starting the semester without access to what they need. A platform that authenticates via mobile number or simple SSO shortens that cycle from days to hours and removes IT as a bottleneck in the critical first week. ## What a unified platform requires in a university context Not every employee engagement software product built for the enterprise translates cleanly to higher education. The requirements differ in three specific ways. **Role-based content delivery.** A faculty member, a research associate, a dining hall supervisor, and a department administrator have different daily information needs. A platform that delivers undifferentiated all-staff announcements to all four creates noise for each of them and diminishes trust in the channel over time. Persona-driven delivery — configured by role and, in multi-campus environments, by location — ensures that curriculum updates reach the instructors who need to act on them, not the full staff list. **Mobile access without VPN dependency.** The operational question is not "does it have an app?" — it is "can an adjunct faculty member authenticate and reach their schedule, policy documents, and department updates from a personal device in under 60 seconds, without submitting an IT ticket?" Platforms that require a campus VPN or a managed device answer that question with a no. For a workforce where a significant percentage are off-campus or between campuses at any given moment, that is a meaningful structural gap. **Contextual search across institutional knowledge.** A search function that surfaces documents by context — pulling up a prior grant application when a faculty member searches for a current deadline, or surfacing a past IRB submission when a new research assistant needs a template — recovers a meaningful share of the 47% of workdays that knowledge workers spend looking for information, per Gartner. Intelligent search is not a premium feature in this context; it is the mechanism that makes institutional memory durable across personnel rotations. The [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study shows how a large, distributed organization with a mix of on-site and remote staff solved the same communication and knowledge-access fragmentation that universities face — and the adoption trajectory that followed once the access barrier was removed. ## Measuring whether the platform is working Deploying a collaboration platform is not the end of the process. University administrators need to demonstrate outcomes to governing boards and accreditation bodies that increasingly ask about institutional effectiveness and digital infrastructure investment. The metrics that matter in a higher education context: - **Faculty adoption rate** — what percentage of instructors actively use the platform within 60 days of launch, not just the administrators who configured it - **IT support ticket volume** — whether the platform reduces help-desk requests or shifts the burden rather than eliminating it - **Content relevance ratings** — whether faculty rate communications as relevant to their role (the Banner Health 63% figure is a baseline benchmark for what poor governance looks like) - **Research knowledge reuse** — whether teams building on prior work report faster onboarding than teams starting from scratch The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an independent framework for evaluating platforms against criteria like these — distinguishing tools that genuinely close the access and engagement gap from those that replicate the same structural problems in a newer interface. ## The implementation path is shorter than most IT teams expect The standard concern from university IT departments is that a platform consolidation project will require months of configuration before it reaches faculty. That timeline applies to legacy enterprise deployments. Modern collaboration platforms designed for distributed organizations support no-code configuration — department administrators can stand up role-based collaboration spaces in weeks, without IT involvement. The initial path covers authentication (mobile number or SSO, no email provisioning required), role configuration, and a pilot with one department before a phased rollout to the broader institution. The resulting IT surface area is also smaller. A single unified platform with centralized authentication is easier to audit, secure, and maintain than a stack of overlapping point solutions with separate credential sets and separate update cycles — a compliance and security dividend for institutions subject to FERPA or research data governance requirements. What looks like a faculty experience investment at the start of the project often shows up as an IT simplification dividend by the end of the first year. ## What changes when the infrastructure works The coordination overhead that currently absorbs hours of faculty time each semester — searching for documents, forwarding information across email threads, attending synchronous meetings that exist only because no async channel carries the same authority — is recoverable. The hours exist in the system; they are absorbed by infrastructure friction, not by the work itself. Universities that remove the access barrier and give every employee — tenured faculty, adjunct instructors, research staff, and campus operations workers — a unified platform recover those hours measurably. The coordination overhead shifts to the substantive work it was always meant to support: stronger research cycles, more consistent curriculum delivery, and an adjunct workforce that feels connected to the institution rather than peripheral to it. That shift is quantifiable, attributable to the infrastructure change, and reportable to the bodies that fund and accredit the work. --- # Improving Your Guest Experience With Internal Communication **Author:** Anna Carriveau **Published:** 2019-07-16 **Category:** integrated-digital-workplace Set foot into any hotel and you’ll know right away what type of experience it’s going to be. From beautiful views to onsite amenities, hotels depend on providing guests with a relaxing, enjoyable, and entertaining stay. However, even the best dining facilities or concierge services will fail without one often-overlooked element, successful internal communication. While […] Set foot into any hotel and you'll know right away what type of experience it's going to be. From beautiful views to onsite amenities, hotels depend on providing guests with a relaxing, enjoyable, and entertaining stay. However, even the best dining facilities or concierge services will fail without one often-overlooked element: successful internal communication. Quick and dependable internal communication is the cornerstone of every happy hotel experience — and the right intranet platform is what makes it possible at scale. ## Create A Seamless Experience Hotel staff includes all kinds of different teams and departments. Each group tends to work independently and on-the-go. Each team needs to work together to create a comprehensive experience for the guests. Without reliable internal communication, it's impossible for teams to work on-the-go, while still responding quickly to individual guest needs. Hotel staff need a space to address immediate concerns, share updates with one another, connect with other departments, and effectively collaborate together to provide a pleasant stay. Per Emergence Capital, 80% of the global workforce is deskless — a profile that mirrors most hotel operations, where housekeeping, front desk, and food-and-beverage staff rarely sit at a desktop. A mobile-first [employee communications](/solutions/employee-communications) platform reaches these workers where they already are, without requiring them to find a shared terminal or log into a legacy intranet. ## Keep Everyone Up To Date Hotels are a constantly changing environment. With popular seasons, company promotions, and local events, something different is always going on. Even the number of guests staying at a hotel greatly varies from day to day. To ensure a more enjoyable experience for your guests, hotel staff needs to know about upcoming conditions as soon as possible. Without successful internal communication, employees are often unaware of important changes, and are unable to answer questions. Keeping staff informed is especially important when new or unexpected situations occur. Sudden maintenance problems, drastic weather changes, or any other unusual experiences can quickly blindside uninformed employees, creating a confusing experience for everyone involved. The cost of poor information access is measurable: per IDC, employees spend an average of 2.5 hours per day searching for information. In a hotel environment, that friction translates directly into slower guest response times. Per Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in, and only 13% use one daily. The gap between having a communication tool and actually using it is where most hotel communication strategies break down. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) explores how leading organizations are closing that gap. ## Ensure Brand Continuity Hotel brands promise guests a specific experience and provide them a baseline of what to expect during their stay. When guests attend a familiar hotel brand or return to a favorite establishment, they're counting on that same great stay. But new employees, unclear instructions, distinct management styles, and even different physical locations can make it difficult to ensure everyone receives the same experience. Hotels need dependable internal communication not only within their own branch, but also throughout the organization. Streamlined and straightforward corporate communication ensures that every branch can stay up-to-date on policies, ask questions about brand experiences, and provide guests with the positive visit they expect no matter where they are. Standardizing brand experience across locations also depends on consistent sop operations — documented, accessible standard operating procedures that every team member can reference regardless of shift or property. Only 22% of company intranets currently personalize content by role or location (per Akumina, citing the State of the Digital Workplace & Modern Intranet 2024), meaning most hotel intranets are still broadcasting one-size-fits-all messages to housekeeping, front desk, and management alike. Role-specific newsfeeds and location-based groups change that dynamic. MangoApps has been recognized for this capability in [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report). ## Simplify Employee Onboarding During their busy seasons, employees need all of the help they can get providing outstanding services and overcoming new obstacles. To help offset the sudden influx, management usually brings on new or temporary employees. These new employees need to be quickly onboarded and prepared for the fast-paced environment of the busy season. With dependable internal communication, new staff can easily access important information, answering questions and providing the freedom to work independently. New team members can also quickly communicate with employees, enabling them to connect with mentors and peers at any time. Speed of deployment matters here too. New intranet platforms can be deployed and adopted at scale in as little as 8 weeks, meaning a hotel group does not need a months-long IT project to modernize staff communications (per Unily, citing a British Airways rapid rollout with a 40,000-employee, 80%-frontline workforce). For teams evaluating how learning fits into onboarding, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) offers a practical framework. ## MangoApps Hotels need quick, clear, and effective internal communication to consistently give guests great experiences. And at MangoApps, we're here to make that happen. With location-based groups, instant newsfeeds, mobile-enabled information, IMs, private messaging, and much more, we empower hospitality organizations of every size to communicate and collaborate effectively. MangoApps is built for on-the-go hotel staff who never sit at a desk — a direct contrast to legacy intranets that create friction for distributed, frontline teams. The platform's [employee app](/solutions/employee-app) puts role-specific updates, SOPs, and team messaging in every staff member's pocket from day one. To learn more about how MangoApps helps the hospitality industry or improving internal communication, contact us or schedule a personalized demo today. schedule demo ## What Should Hotels Look for in an Internal Communication Platform? Not every communication tool is built for the realities of hotel operations. When evaluating options, hospitality teams should prioritize: - **Mobile-first access** — staff should be able to receive updates, respond to requests, and access sop operations documentation from any device, without a desktop login. - **Role- and location-based targeting** — housekeeping, front desk, and food-and-beverage teams have different information needs. A platform that delivers persona-driven communications reduces noise and increases relevance. - **Rapid deployment** — busy seasons don't wait for IT timelines. Look for platforms that can reach full adoption in weeks, not quarters. - **Measurable adoption metrics** — given that only 13% of employees use an intranet daily (per Social Edge Consulting), adoption tracking is not optional. Set a baseline and measure against it after rollout. - **Intranet and CMS capabilities** — a cms intranet that centralizes policies, brand standards, and training materials in one searchable location eliminates the 2.5-hour daily information search (per IDC) that drains staff productivity. For a broader view of how workforce operations tools are evolving, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the key shifts shaping frontline communication strategies. ## How Do You Measure Whether Internal Communication Is Actually Working? Improving hotel guest experience through internal communication is only meaningful if you can tell whether it's working. Three practical measurement approaches: 1. **Platform adoption rate** — track the percentage of staff logging in weekly. A mobile-first rollout in a predominantly frontline workforce can achieve a 91% usage rate (per Unily, British Airways case study). Use that as a benchmark when setting targets. 2. **Response time to guest requests** — measure the average time between a guest request being logged and the relevant department acknowledging it. Internal communication improvements should compress this window. 3. **Onboarding time-to-productivity** — track how quickly new seasonal hires reach independent task completion. Faster access to SOPs and peer messaging directly shortens this curve. MangoApps has been recognized for delivering measurable outcomes in this space — see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) for independent analyst context on what separates high-adoption platforms from low-engagement ones. --- # 6 Leadership Lessons From Factory Employees **Author:** April Thomas **Published:** 2019-07-02 **Category:** company-collaboration Manufacturing factories aren’t typically somewhere you find desk employees, but they might just be the best place to discover insightful leadership strategies. While the setting and circumstances are certainly different, factory employees and their unique environment illustrate management practices in a much more tangible way. Six leadership lessons you can learn from factory employees: Don’t […] Manufacturing factories aren’t typically somewhere you find desk employees, but they might just be the best place to discover insightful leadership strategies. While the setting and circumstances are certainly different, factory employees and their unique environment illustrate management practices in a much more tangible way. Six leadership lessons you can learn from factory employees: Don’t Cut Corners In manufacturing, cutting corners can have serious consequences. While shortcuts might appear to save time, they often create an unsafe workplace. Machinery malfunctions, product recalls, inferior workmanship, and damaged reputations are never worth the occasional inconvenience. In leadership, the physical results of cutting corners aren’t always as obvious. Besides the obvious mistakes that careless work can bring, avoiding work introduces a negative attitude into the work environment. As a leader, employees look to you to set the culture, tone, and ethics of the organization. Corner cutting, even when it seems innocent, shows employees they don’t need to take the time to do it right. As a shortcut-focused attitude spreads across the organization, what started out as a simple, probably even harmless work-hack, soon becomes an entire culture of disengaged, dissatisfied, and unmotivated employees. Make Work Meaningful Factories are loud, active, physically demanding, and overall just hard work. At the end of the day, employees go home sore, exhausted, and ultimately, with a real sense of personal satisfaction. When employees are able to measure their efforts, they develop a sense of pride, accomplishment, and dedication in the work they do. In manufacturing, seeing the end results are often easy. But in the corporate world, it can be a little more difficult. As a leader, it is your responsibility to help employees see the results of their efforts. Make sure employees understand the entire workflow process, and show them how their efforts directly lead to success. Celebrate their individual accomplishment and create an environment where everyone knows the difference they make.    Every Job Is Essential   In factory work, you can’t skip a single step. It doesn’t matter how simple or mundane a task might be, a single missing screw can ruin an otherwise perfect product. In leadership, it is the same. As a leader, it’s tempting to think your role or the roles of other senior employees are more meaningful, but one of the most important leadership lessons is knowing that every team member is essential for success. Make sure every member of your team participates and contributes to the group, both by doing their work and by offering their unique perspective. Respect each team member’s knowledge and experience in their particular field and avoid any kind of arrogance or elitism. Don’t pretend, or let other team members pretend, to know about a field they have little training or experience in. Help your team see the value of each position. It’s easy to discredit a role when you don’t understand how it works or what it contributes to the team. As you help your team members recognize not only their own value, but also the value of those around you, you will develop a hardworking, happy, and efficient team that works together with real unity. Acknowledge Limitations In manufacturing, it’s crucial to work within your own limitations. Not understanding safety practices, not having the required physical strength, or not being up to date on specific procedures can slow down factory progress and possibly even cause injuries. In the corporate environment, faking your way through a situation is often a little easier, but the results are just as damaging. As leaders, we want to instill confidence and respect. Our team needs to trust us to make the best decisions, support them, and get work done. But sometimes pride gets in the way. While leaders, of course, need to know their responsibilities and be able to do their job, you’ll never be up to date on every new idea or have in-depth knowledge on every topic your team covers. Similarly, time constraints, physical health, and other factors create real limitation that cannot just be ignored. Openly acknowledging your limitations can feel like a weakness at first, but it is actually incredibly freeing. Being honest with your team shows the trust and respect you have for them and encourages them to be honest with you as well, allowing everyone to overcome limitations and accomplish work.   Communication Is Preparation Timing in manufacturing is essential. After too much time has passed, many factory materials can no longer be manipulated or are no longer safe to work with. Without clear team communication, this window of workable opportunity is lost, and factories are forced to begin again. While it might not always happen in a tangible way, this critical leadership lesson applies to businesses as well. Company teams, especially client-facing teams, often find themselves facing a specific window of opportunity. Sometimes these moments are known in advance and sometimes they come as a surprise. Either way, without straightforward and effective communication, teams are unable to act and lose opportunities. As a leader, your team must be prepared to take on a challenge whenever it arises. When healthy team communication has been established well in advance, it’s easy for teams to take advantage of new opportunities and smoothly handle whatever comes their way.    Be Open To Adjustments It’s easy to think of a stereotypical factory employee, but in reality, factory workers include individuals from every background. Everyone working on the factory floor has a different opinion, life story, living situation, theological belief, and much more. They all have unique perspectives and individual experiences but regardless of any difference, come together to get the job done. As a leader, it’s easy to stereotype what our team needs to be. Work habits, personal preferences, and other characteristics can influence what we visualize as the perfect team. Recognizing leadership lessons means being open to new individuals, styles, and ideas. At the end of the day, objectives always need to be accomplished but try letting a different team member take on a task, putting together a different kind of team, or listening to suggestions from other employees. You might just be surprised to discover unknown talents or a new dream team. MangoApps Lasting leadership lessons come not just from reading books or brainstorming ideas, but from understanding and apply real-world experiences. That’s why at MangoApps, we design our products around meeting real customer needs. We help organizations successfully implement internal communication tools, interactive company intranets, engaging enterprise social networks, and everything in-between. To learn more about how MangoApps works with manufacturing, helps leader build outstanding teams, or to see our services at work in your own organization, schedule a personalize demo today.  schedule demo --- # How To Get Honest Feedback From Employees **Author:** Anna Carriveau **Published:** 2019-06-18 **Category:** employee-engagement Employees interact with customers, understand internal processes, and have a truly unique perspective on how everything occurs. Understanding employee feedback is a huge advantage, both in terms of company and product growth, as well as in individual employee happiness. Unfortunately, gaining genuine feedback can be difficult. Even if you ask for it, employees are hesitant, […] ## How To Get Honest Feedback From Employees Employees interact with customers, understand internal processes, and have a truly unique perspective on how everything occurs. Understanding employee feedback is a huge advantage, both in terms of company and product growth, as well as in individual employee happiness. Unfortunately, gaining genuine feedback can be difficult. Even if you ask for it, employees are hesitant, afraid that being too straightforward might have negative implications on their job. Besides decreasing employee productivity, the "not my problem" approach of a disengaged employee often makes them unwilling to share insights. So how can you encourage employees to actually share honest feedback on company issues? ## 5 Ways To Encourage Employee Feedback: ### **Encourage More Engagement** The first step in encouraging employees to share their opinion is to make sure that they actually want to share. When employees are engaged, invested, and involved in the organization, they want to see it do well. They naturally strive to fix problems and overcome obstacles. The most important thing to remember is that employees need to feel safe, understood, challenged, and invested. When they appreciate and enjoy their work environment, they naturally become more engaged. Reviewing [Gallup's 2026 State of the Global Workplace: What It Means for HR, ...](/articles/gallup-2026-state-of-the-global-workplace) can help you recognize the early signs of decreasing employee engagement and benchmark your own employee engagement strategies against global data. ### Make Sharing Opinions Easy Once you have confirmed that your employees want to share, the next step becomes providing them a platform to do so. It should be easy for employees to share thoughts and suggestions. One example of this are traditional employee suggestion boxes. These boxes are straightforward for employees, but lack the order and simplicity needed to sort through ideas. Similarly, detailed spreadsheets with color-coded KPIs might be great for leaders, but they just look like a confusing mess to the average employee. Thankfully, with today's technology and collaboration tools, sharing ideas and analyzing workplace insights is easier than ever. With a transparent and communicative workforce, you can boost employee productivity. For a broader view of how communication tools are evolving, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) outlines the platforms and practices gaining the most traction. ### Offer Anonymous Feedback No matter how confident and comfortable employees are, it's always a little scary to give company critiques. You never know exactly how your honest feedback is going to be received. Give employees the confidence they need by providing anonymous feedback options. Help employees understand that your greatest interest is in improving everyone's experience — whether that means employees, customers, investors, or whoever else it may be. Anonymous feedback works best when it is backed by an analytics layer, not just a suggestion box. An employee engagement survey tied to a platform with reporting capabilities lets leaders identify patterns across teams, locations, and roles — rather than reacting to one-off comments. Only 22% of company intranets currently deliver personalized content, meaning most feedback channels reach employees with generic, low-relevance prompts that suppress honest responses (per Akumina, citing the State of the Digital Workplace & Modern Intranet, 2024). Connecting your employee engagement questionnaires to role- and location-based targeting meaningfully increases the relevance of each prompt. And while it might seem obvious, respect and honor the trust of your employees and truly offer anonymous suggestions. If you have the ability to discover the identity of employees giving anonymous feedback, don't do it. Your workers are trusting you to honor your word and respect their right to privacy. You violate that trust at the expense of your entire company culture and corporate reputation. ### Create Open Communication Facilitate trust by showing employees that communication isn't just a one-way experience. If you expect workers to be open and honest with you, then they need to receive the same treatment. While obviously every business decision can't be shared and some information must be kept confidential, prepare and inform employees about issues whenever possible. This not only helps employees feel connected and engaged in the organization but also shows the confidence you have in your workforce. When people feel trusted they are much more likely to offer it in return. Being open with employees means including them in both the positive and negative experiences. While it can feel safer to hold onto bad news as long as possible, being blindsided by a layoff, a lost client, an organizational rearrangement, or any other kind of setback is always a worse experience. For organizations navigating complex workforce structures, [Managing a Unionized Workforce Is Different. Your Software Should B...](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) explores how communication norms and feedback channels need to adapt to different employee contexts. ### Actually Follow Through Collecting information and honest feedback is ultimately useless if you don't do anything with it. In fact, asking employees for their opinions and then disregarding their input is probably worse than not asking at all. While you can't fulfill every request of course, honestly acknowledging their input and thanking employees for their contributions goes a long way. Employees need to know that their concerns are being heard, that their insight matters, and that they make a lasting difference. Organizations that close the feedback loop — visibly acting on employee engagement survey results — see measurably higher participation rates in subsequent pulse surveys compared to those that collect but don't respond (per Simpplr). Following through is especially important when you do decide to make changes based on employee feedback. Let employees know about changes and then keep your word to the best of your abilities. AI-assisted analysis is increasingly the bridge between collection and action. Rather than manually reviewing hundreds of open-text responses, leaders can use sentiment analysis to surface the themes that matter most and prioritize accordingly — directly shortening the time between hearing feedback and acting on it. It can be easy to let plans fall through the cracks, but make an effort to stay organized, follow up often, and ensure changes actually happen. ### Reach Frontline and Deskless Employees Where They Are Any employee feedback strategy that relies solely on desktop tools will miss a significant portion of the workforce. Per Emergence Capital, 80% of the global workforce is deskless — shift workers, field technicians, retail associates, and others who rarely sit at a computer. These employees have some of the most direct customer and operational insight in any organization, yet they are the least likely to be reached by traditional employee engagement software. Persona-driven communication channels — segmented by role, location, and shift — increase the relevance of feedback prompts and lift response rates for frontline workers (per Akumina). A mobile-first employee engagement platform ensures that an associate on the floor or a technician in the field can complete an employee engagement survey in the same moment they notice a problem, rather than waiting until they're back at a desk — if they ever are. For retail-specific context on how this plays out operationally, [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) illustrates how frontline communication and feedback loops connect to day-to-day management. ## MangoApps At MangoApps, we know the importance of listening to employees. With surveys, quizzes, and detailed employee recognition tools, we make it easy for employees to share and leaders to analyze, assess, and act on input. Our [solutions/employee-engagement](/solutions/employee-engagement) capabilities connect anonymous feedback collection to enterprise-grade analytics, so the gap between hearing from employees and acting on what they say stays as short as possible. To learn more about MangoApps or see how it can work for your own company, contact us or schedule a personalized demo today. **Schedule demo** --- ## What Questions Should You Actually Ask Employees? The quality of feedback you receive depends heavily on the quality of questions you ask. Effective employee engagement questionnaires avoid yes/no formats in favor of scaled or open-ended prompts: "On a scale of 1–10, how confident are you that leadership acts on the feedback you provide?" or "What is one process change that would most improve your day-to-day work?" Pulse surveys — short, frequent check-ins of five questions or fewer — consistently outperform annual surveys in response rate and data freshness. Mixing quantitative scales with at least one open-text question per survey gives analytics tools enough structured data to trend over time while still capturing the nuance that numbers alone miss. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading HR teams are redesigning their survey cadences for 2026. ## How Do You Analyze and Act on Feedback Once You've Collected It? Collecting feedback is only the first step; the analysis and response cycle determines whether employees bother participating next time. Start by categorizing responses into themes — compensation, workload, communication, recognition — so you can prioritize by frequency and severity rather than reacting to the loudest individual voice. Sentiment analysis tools can automate much of this categorization at scale, flagging emerging concerns before they become retention problems. Once themes are identified, assign owners and timelines: vague commitments to "look into it" erode trust faster than a clear "we heard X, here is what we are doing by [date]." Organizations that close this loop visibly see measurably higher participation in subsequent pulse surveys (per Simpplr). For a practical look at how one organization built this kind of feedback infrastructure, see [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology). ## How Does Employee Engagement Training Help Leaders Collect Better Feedback? Managers are often the weakest link in a feedback system — not because they don't care, but because they haven't been trained to ask, listen, and respond without defensiveness. Employee engagement training equips managers with the conversational frameworks to hold one-on-ones that surface honest input, the skills to distinguish venting from actionable insight, and the habits to close the loop visibly with their teams. Training on employee engagement also helps managers understand how their own communication behaviors — transparency, follow-through, responsiveness — directly influence whether employees trust the feedback process enough to participate honestly. For a deeper look at how learning programs connect to day-to-day engagement, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) outlines the structural reasons most training investments underdeliver and what to do instead. --- # 5 Ways To Build Lasting Partner and Vendor Relationships **Author:** Anna Carriveau **Published:** 2019-06-11 **Category:** industry-insights Every successful business has a strong team of partners and vendors on its side. These outside sources can help with anything from supplying materials to logistics services to finances, and much more. While your individual organization might be outstanding, without effective external cooperation and support, its almost impossible to thrive. So, naturally, it makes senses […] ## 5 Ways To Build Lasting Partner and Vendor Relationships Every successful business has a strong team of partners and vendors on its side. These outside sources can help with anything from supplying materials to logistics services to finances, and much more. While your individual organization might be outstanding, without effective external cooperation and support, it's almost impossible to thrive. So, naturally, it makes sense to ensure your partner and vendor relationships are as happy and healthy as possible. **Here are 5 ways to build lasting relationships with partners and vendors:** ### #1: Choose Your Partners Wisely The first step to a great long-lasting relationship is making a good first choice. When originally evaluating partners and vendors, carefully consider a long-term relationship. Can the company perform your required roles and services for a long period of time? Do they embody characteristics and a culture you feel comfortable associating yourself with? Can you communicate well with them regularly? Ask potential partners for a list of references or about current clients similar to yourself. A successful vendor relationship depends on much more than just the cheapest price or even the best products and services. Ensure your relationship, work style, and ethics are compatible from the start. ### #2: Maintain Clear Communication You wouldn't expect employees to work effectively without regular and up-to-date communication, and vendor relationships are exactly the same. Make sure vendors have at least one regular point of contact with the company that can update and inform them about needs, schedule changes, order issues, or anything else. One way to communicate easily with vendors is by incorporating them into your employee communications platform. Many platforms even have a specific guest user setting, designed just for partner and vendor communication. These allow organizations to include vendors in only specific groups or areas within their network, ensuring communication is easy and content stays safe — a capability sometimes called persona-driven or role-based access control, which protects sensitive internal content while keeping collaboration fluid (per Akumina product page). Incorporating vendors into a unified communications platform — rather than siloed email threads — reduces missed updates and accelerates issue resolution during supply disruptions (per Simpplr/Unily change management and crisis communications use cases). However you decide to communicate, make sure it is clear, regular, and informative. For a broader look at where employee and partner communications are heading, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) is a useful reference. It's also worth noting that 47% of workers struggle to find necessary information at least half the time, per Gartner, 2023 — a friction point that applies equally to external partners navigating your processes. ### #3: Provide Comprehensive Training In addition to regular communication, it's important to arrange periodic training for outside organizations. Occasional training ensures everyone working with your company understands your goals, requirements, and unique concerns — including your standard operating procedures (SOPs), operations manuals, and any operations instructions specific to your workflows. It serves as a reminder to established contacts and helps new members receive detailed training right from the source. Regularly scheduled trainings also mean vendors and partners are always up to date on any changes to guidelines and regulations. Structured digital onboarding via a platform — rather than periodic in-person sessions alone — makes vendor training repeatable and auditable. Guest-user and group-access features let you deliver the right operations instructions to the right external contacts without exposing unrelated internal content. The results can be significant: organizations that pair a structured digital rollout plan with ongoing training have seen frontline adoption rates reach 90% within the first six months (CVS case study). Once you've established an initial vendor relationship, schedule a follow-up training a few months in advance. After your follow-up, continue to implement refresher sessions or updated trainings as often as needed. ### #4: Stay Understanding And Supportive Vendor relationships are, believe it or not, relationships! Which means they depend on trust, understanding, and mutual respect. Of course, there may come a time when you and your vendor need to part ways, and we are in no way advocating you don't correct problems or resolve concerns. But just like any successful personal relationship depends on mutual commitment and understanding, it's important to support your vendors and show them appreciation. Like your own employees, vendors are experts in their industry and often have unique ideas and perspectives organizations can benefit from. If you've carefully selected a reputable vendor and cultivated a strong relationship so far, you can trust them to make the right choice in sticky situations, ask for input and ideas, and support them through the occasional ups and downs. Analytics can reinforce this dynamic: real-time sentiment and engagement analytics on partner communications help operations teams identify relationship friction before it escalates to contract risk (per Unily case study on sentiment insight for crisis communications). Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback — a principle that translates directly to vendor retention when partners feel heard and valued. ### #5: Put Yourself In Their Shoes Partners might assist you in your own efforts, but don't forget they are a business too. Every vendor you work with has its own vendors, goals, guidelines, and aspirations. When working with a vendor, especially when overcoming an obstacle, consider the situation from their perspective. Try to offer solutions that are mutually beneficial or take into account your vendor's needs. When companies are considerate of and support each other, a truly successful partnership is able to emerge. Centralizing communications and self-service resources on a unified platform supports this mutual benefit: organizations have reported a 52% decrease in support requests after making this shift (Workday case study), freeing both sides to focus on strategic collaboration rather than administrative back-and-forth. ### MangoApps While they might seem insignificant at times, vendor relationships can make or break an otherwise healthy organization. Much like regular relationships, vendors and partners require a little time, effort, and consideration in order to thrive. At MangoApps, we help companies achieve successful internal and external communication — from structured vendor onboarding workflows to role-based access controls that keep collaboration fluid without compromising security. To learn more about how MangoApps supports [workforce management](/solutions/workforce-management) and external partner communications, contact us or schedule your own personalized demo today. **Schedule Demo** --- ### How Do You Measure Vendor and Partner Relationship Health? Choosing the right vendor and communicating clearly are necessary first steps, but measuring whether those relationships are actually healthy over time is what separates reactive vendor management from proactive partnership strategy. Key indicators include response time on issue resolution, training completion rates, and engagement levels within your shared communications channels. Per McKinsey research, 81% of leading companies effectively use data and analytics tools — applying that same discipline to external partner communications gives operations teams an early warning system for relationship friction before it becomes a contract or supply-chain risk. Sentiment and engagement analytics built into your employee communications platform can surface these signals automatically, rather than waiting for a missed deadline or escalated complaint to reveal a problem. ### What Should You Do When a Vendor Underperforms? Even well-chosen vendors will occasionally fall short of expectations. A structured response process — grounded in your documented SOPs and operations manual — protects both parties and keeps the relationship recoverable. Start by reviewing the original agreement and any operations instructions you provided during onboarding: underperformance is sometimes a training or communication gap rather than a capability failure. Schedule a direct conversation, share specific data on the gap, and agree on a remediation timeline with measurable checkpoints. If the vendor has been incorporated into your communications platform, the audit trail of shared updates, training completions, and prior issue resolutions gives both sides an objective basis for the conversation. Parting ways should be a last resort, not a first response — especially when the cost of re-qualifying a new vendor is factored in. ### How Do You Negotiate Better Terms Without Damaging the Relationship? Negotiation is a normal part of any long-term vendor relationship, and approaching it as a mutual benefit exercise rather than a zero-sum transaction preserves goodwill. Come prepared with data: utilization rates, order volumes, issue frequency, and any measurable outcomes your partnership has produced. Vendors who have been trained on your processes, integrated into your communications workflows, and treated as genuine partners are far more likely to offer flexible terms than those kept at arm's length. For a deeper look at how workforce operations and vendor strategy intersect, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers emerging frameworks that apply to both internal teams and external partner networks. Framing negotiations around shared goals — rather than purely on price — tends to produce agreements both sides will honor over the long term. --- # How To Assemble Fantastic Work Teams **Author:** April Thomas **Published:** 2019-06-04 **Category:** team-collaboration Ineffective teams have been the bane of our existence from almost the very beginning. Ask any student what the worst part of school is, and group projects are sure to top the list. And teamwork doesn’t go away once you graduate, whether you work in a traditional office or an on-the-go environment, teamwork is sure […] ## How To Assemble Fantastic Work Teams Ineffective teams have been the bane of our existence from almost the very beginning. Ask any student what the worst part of school is, and group projects are sure to top the list. And teamwork doesn't go away once you graduate — whether you work in a traditional office or an on-the-go environment, teamwork is sure to surface at least occasionally. Inept teams are disengaging, discouraging, and ultimately unproductive. It's honestly enough to make you consider giving up on teams entirely, at least, until you experience a team that gets it right. Unlike the discouraging mess of an unsuccessful team, when teams actually work well together they are productive, focused, and make work an enjoyable experience. But how do you bridge the gap between terrible and terrific? The answer is by assembling fantastic work teams — and then giving them the structure, measurement, and conflict-resolution tools to sustain that performance over time. ## Four Ways To Assemble Fantastic Work Teams ### #1: Take Advantage Of Interests Every employee at your organization is unique, with his or her own talents and interests. And while everyone has to do dull work occasionally, interest is often only a matter of perspective. Just like chores around the house, a task one person loves can be absolute misery to another, even if they share the same skill level. Whenever possible, talk to potential team members about their interests in a particular topic or task. Taking on a topic they genuinely enjoy also subconsciously encourages employees to work harder, become more invested, and enjoy the overall experience more, making them a strong asset to any team. And because making a choice invokes a sense of independence, selecting their own team increases an employee's sense of personal responsibility for the project. By analyzing each individual's skill set, you can truly begin to build a high-performing team — a foundational step in any set of [employee engagement strategies](/solutions/employee-engagement) worth implementing. For distributed and frontline teams, this principle requires extra intentionality. Per Emergence Capital, 80% of the global workforce is deskless, meaning the majority of employees may never sit in a planning meeting where interests are discussed. Proactively surfacing interest and skill data through surveys or digital profiles ensures those workers aren't assigned by default rather than by fit. ### #2: Look Outside Of The Expected We all want work teams with successful innovators, who can whip out ingenious ideas at a moment's notice. However, trying to fulfill these "creative" stereotypes actually dooms teams to future failure. While quirky, eccentric, idea-heavy employees certainly exist somewhere, they are by far the exception. In reality, the best solutions are often generated by every day, introspective, and seemingly average individuals. By limiting your innovative teams to stereotypically extroverted or artistic personalities, you risk seriously missing out on the best opportunities. In fact, recent research has actually shown that caring, considerate, and compassionate employees are generally more creative and good idea-driven than over-the-top, boisterous, or Type-A individuals. This is especially relevant for organizations with shift-based or hourly workforces. Frontline workers in retail, hospitality, and logistics often carry deep operational insight that never reaches leadership — not because they lack ideas, but because the team structures weren't designed to include them. The [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study) illustrates how a large distributed workforce can be brought into collaborative structures that surface ideas from every level. ### #3: Create Psychological Safety Successful teams need more than just flamboyant thinkers or even hard-working individuals. In order to thrive, teams have to include a strong sense of psychological safety. Psychological safety — each team member's ability to comfortably contribute to the group — is considered one of the most important components of long-lasting team success. When team members can comfortably present ideas and take risks together, solutions are not only shared but strengthened by the team experiences and insights. Similarly, a study done by MIT and Carnegie Mellon found that teams with equally contributing members were overall more successful than teams dominated by only a few individuals. Teams with equal contribution across members — not just a few dominant voices — consistently outperform hierarchical team structures on complex problem-solving tasks, per MIT and Carnegie Mellon research. Psychological safety is not just a cultural nicety. Teams that lack it suppress dissenting ideas, which measurably reduces the quality of decisions and innovation output, per employee experience research from Simpplr and Unily. New, shy, or otherwise hesitant employees often have important insights but need a little extra encouragement. Work teams need to establish an environment that can bring out the best in each other. Understanding how learning culture intersects with team safety is explored further in [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ### #4: Show Authentic Team Support Even the best teams will struggle under mediocre or inefficient management. As a leader, you are responsible for not only building dependable teams, but also providing regular assistance and support. Leaders need to create their own version of a psychological safe space, where teams are appreciated and encouraged. Supportive leaders show teams their true potential and help them reach it. With the encouragement of their leaders, teams can safely work harder, experiment more, and become emotionally invested in project outcomes. The data on what happens when this support is operationalized through a platform is striking: Agero reported a 22x increase in employee engagement after deploying a unified employee experience platform, and British Airways achieved a 30-point engagement score increase following platform-driven team communication improvements. These outcomes suggest that authentic support, when paired with the right infrastructure, compounds in measurable ways. ## How Do You Measure Whether Your Team Is Actually Working? Assembling a team is only the first step. Knowing whether it's performing requires deliberate measurement. Employee engagement surveys and employee engagement questionnaires are among the most direct tools available — they surface whether team members feel heard, valued, and aligned with shared goals. Pulse surveys run at regular intervals (bi-weekly or monthly) give leaders a leading indicator of team health before problems escalate. Tracking output metrics — task completion rates, cycle times, and cross-functional collaboration frequency — alongside engagement data gives a fuller picture than either measure alone. For a broader view of where workforce measurement is heading, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers emerging approaches to team performance analytics. ## How Should Teams Handle Conflict Before It Derails Progress? Even well-assembled teams encounter friction. The difference between teams that recover and teams that fracture is usually whether a conflict-resolution norm was established before the conflict occurred — not after. Effective norms include: a shared agreement that disagreement about ideas is expected and welcome (reinforcing psychological safety), a designated process for escalating unresolved disputes to a neutral party, and regular retrospectives where friction points are named without blame. Distributed and frontline teams face compounded collaboration friction when tools are fragmented, because workers must context-switch across multiple disconnected apps just to complete a single workflow, per MangoApps and Beekeeper product research. Consolidating communication and task management into a single environment reduces the ambient stress that makes conflict more likely. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) addresses how operational fragmentation affects team cohesion in detail. ## How Do You Onboard New Members Into an Existing High-Performing Team? Adding someone to a team that already has established norms, inside language, and shared history is one of the most underestimated challenges in teamwork management. Done poorly, it disrupts the existing team's rhythm and leaves the new member feeling like an outsider. Done well, it refreshes the team's perspective and accelerates the new member's contribution. Key practices include: assigning a peer buddy (not just a manager) for the first 30 days, explicitly walking new members through the team's psychological safety norms rather than assuming they'll absorb them, and giving new members a low-stakes early win to build confidence. Employee engagement training and structured onboarding programs that embed these practices into daily workflows — rather than treating them as one-time orientation events — produce measurably faster ramp times. For context on how training connects to sustained engagement, see the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook). ## MangoApps Improving team collaboration in the workplace is critical to any organization's success. Successful work teams are the cornerstone of any prosperous organization and MangoApps is here to help. With MangoApps' collaboration platform, employees have the tools and flexibility they need to share resources, collaborate together, and accomplish outcomes — whether they're at a desk, on a retail floor, or working a shift without regular access to a corporate intranet. To learn more about how MangoApps can transform your company, contact us or schedule a demo today. --- # Successfully Serving Big Clients With Small Teams **Author:** Anna Carriveau **Published:** 2019-05-21 **Category:** industry-insights Over the last decade, start-ups and small businesses have shown that you don’t need an enterprise-sized staff to pack a serious punch. When small teams work well together they can not only keep up with larger competitors but even offer unique advantages unavailable anywhere else. They don’t need to be limited or intimidated by a […] Over the last decade, start-ups and small businesses have shown that you don't need an enterprise-sized staff to pack a serious punch. When small teams work well together they can not only keep up with larger competitors but even offer unique advantages unavailable anywhere else. They don't need to be limited or intimidated by a client's size. With the right attitude, any-sized team can successfully serve a big client — and the five strategies below show exactly how. ## Cultivate A Culture Of Collaboration Small teams successfully meet big client needs when they create an authentic culture of collaboration. True collaboration combines good ideas together, helping the best solutions and outcomes emerge. Collaborative thinking is important for all companies, but especially for larger organizations, where industries are much more likely to settle into outdated habits or fall into a creative rut. Because of their distinct size, small teams can have a serious collaborative advantage. With fewer people involved in the process, it's easier for team members to build friendships and become comfortable together. This makes them more likely to think creatively, share ideas, and increase idea turnaround time than with a larger team. Peer-to-peer recognition embedded in a shared platform — rather than a standalone app — keeps small teams aligned on shared wins without adding tool overhead, a specific advantage when serving enterprise clients who expect cultural cohesion. Research supports the impact: peer recognition programs generate 36% more employee engagement than manager-only programs, and 60% of high-performing firms report increased performance when employees are recognized, per Enterprise Apps Today 2022. Exploring [solutions/employee-engagement](/solutions/employee-engagement) can help teams build this kind of recognition culture at scale. ## Establish Unquestionable Transparency To help large clients stay successful, small teams must establish crystal clear transparency. Every team member needs to understand who is taking on each task, what plans are in progress, and what their own individual responsibilities are. Transparency helps teams build trust, remove confusion, and ensure everyone is on the same page. When it comes to team transparency, smaller numbers can be a serious advantage. In large teams or enterprise organizations, workloads can often become unclear and confusing. It can be difficult to determine who is responsible for each assignment and tasks are divided disproportionately, with some employees taking on enormous efforts while other coworkers are unable to contribute effectively. Transparency also extends to measurement. Small teams have a structural edge here: with fewer layers of management, real-time sentiment and engagement analytics surface problems faster than they would in a large organization. Engagement metrics can reveal warning signs as far as nine months before an employee leaves, per Workday Peakon Employee Voice — meaning small teams that monitor team health proactively can course-correct before a client relationship is ever affected. For a deeper look at how performance visibility connects to retention, [Closing the Information Gap in Performance Reviews](/articles/closing-the-information-gap-in-performance-reviews) is a useful starting point. ## Keep The Final Outcome In Mind Enterprise clients need teams to keep the end results in mind. This means that employees understand how their individual efforts contribute to client success and what the long-term goals of a completed project are. When employees have the end goal in mind they stay motivated and create better content. In large teams, employees often work in silos, only receiving enough information to complete their specific assignment. This often causes workers to feel disjointed from their tasks and struggle to stay engaged. In small companies, coworkers with different roles and responsibilities talk, work, and regularly interact, making it easier for everyone to see the complete picture. Keeping the outcome visible also requires the right operational infrastructure. No-code workflow automation for task assignments, approvals, and shift changes lets small teams absorb enterprise-scale operational requests without proportionally growing headcount — a critical capability when a big client's scope expands mid-engagement. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines how teams are building this kind of scalable operational backbone today. ## Stay Accessible At All Times Big clients are always busy and unexpected circumstances can happen in an instant. For any team to achieve big client success, they need to be prepared for unusual opportunities and abrupt plan changes at any time. When action needs to happen now, teams have to be accessible and ready to react immediately. Smaller teams are naturally easier to assemble, and have fewer moving parts to manage. This helps them avoid communication confusion and conflict in other areas. With a small, centralized, and easy-to-access team, client changes or concerns can be addressed right away. Small teams can quickly work together to create effective solutions and implement new ideas at a moment's notice. Accessibility is not just a mindset — it requires the right infrastructure. A unified mobile platform that consolidates communication, task management, HR self-service, and training into one app removes the tool-switching friction that disproportionately slows small teams serving large clients. Enterprise clients also expect their vendors' tools to integrate with existing HRIS, LMS, and payroll systems; small teams that offer that integration depth avoid becoming a coordination bottleneck. For teams operating in high-volume, client-facing environments, the [industries/bpo](/industries/bpo) page illustrates how these operational requirements play out in practice. ## Embrace Constant Innovation Small teams are constantly focused on innovation. To make their mark on the industry, they are striving to incorporate new ideas and think outside of the box. Smaller-sized teams provide big businesses the creativity, energy, and passion they often need to break out of legacy habits and find the next new idea. Data backs this up: 72% of companies investing in tech-enabled frontline insights reported increased productivity, and per McKinsey research, 81% of leading companies effectively use data and analytics tools — a capability small teams can adopt without the bureaucratic overhead that slows larger organizations. Embedding a continuous learning culture alongside innovation efforts compounds this advantage; [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) explores how to make that connection practical. ## MangoApps At MangoApps, we equip teams with the work-centered tools they need for success. We're proud to offer companies an integrated employee platform where communication and collaboration are easy on every level. To learn more about successfully serving big clients or how MangoApps helps organizations of every size, contact us or schedule a free personalized demo today. --- ## What Tools Do Small Teams Need to Serve Enterprise Clients? The strategies above — collaboration, transparency, outcome focus, accessibility, and innovation — all depend on having the right operational foundation underneath them. In practice, that means three categories of tooling: - **A unified communication and task platform.** Consolidating messaging, task management, and HR self-service into a single app eliminates the tool-switching overhead that slows small teams disproportionately. Per the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook), fragmented communication is one of the leading causes of missed client expectations. - **Analytics and engagement measurement.** Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback — yet only 24% of frontline workers feel their feedback from customer interactions is heard by leadership, per Unily research. Employee engagement software that surfaces these signals in real time gives small teams a retention and performance edge. - **Integration with enterprise systems.** Enterprise clients expect vendors to plug into their existing HRIS, LMS, and payroll infrastructure. Small teams that offer this integration depth avoid becoming a coordination bottleneck as client scope grows. ## What Are the Common Failure Points When Small Teams Take On Big Clients? Not every small team is ready for enterprise-scale work, and recognizing the warning signs early prevents costly missteps: - **Scope creep without workflow automation.** When a big client's requests expand, teams without no-code workflow automation for approvals and task assignments absorb the load manually — and quality suffers. - **Transparency gaps at scale.** Small teams that rely on informal communication norms find those norms break down when client complexity increases. Structured teamwork management practices and documented SOPs (standard operating procedures) become essential, not optional. - **Engagement erosion under pressure.** Per Workday Peakon Employee Voice, engagement metrics reveal warning signs nine months before an employee leaves. Small teams serving demanding clients are especially vulnerable to burnout; monitoring employee engagement through regular employee engagement surveys or questionnaires is a proactive safeguard, not an administrative burden. - **Tool fragmentation.** When team members use separate apps for chat, tasks, scheduling, and training, response times slow and errors increase — exactly the opposite of the agility that makes small teams attractive to big clients. Recognizing these failure points before they materialize is what separates small teams that grow with their enterprise clients from those that lose them. ## How Should Small Teams Price and Resource for Big Clients? Taking on a large client without a resourcing plan is one of the most common ways small teams undermine their own advantages. A few principles apply broadly: - **Price for scope, not just hours.** Enterprise clients generate unpredictable request volumes. Pricing models that account for scope expansion — retainers with defined escalation tiers, for example — protect team capacity and client relationships simultaneously. - **Build headroom into the team before you need it.** The accessibility advantage of a small team disappears if every team member is already at 100% utilization. Maintaining a modest capacity buffer is what makes the "available at any time" promise credible. - **Use automation to scale output, not headcount.** No-code workflow automation for task assignments, approvals, and shift changes lets small teams absorb enterprise-scale operational requests without proportionally growing headcount — preserving the lean structure that made them attractive in the first place. - **Invest in employee engagement training.** Teams under enterprise-client pressure need structured support. Formal training on employee engagement and team health keeps morale stable and performance consistent even during high-demand periods. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading teams are building these programs today. --- # How To Improve Office Communication **Author:** Anna Carriveau **Published:** 2019-05-07 **Category:** company-collaboration While companies usually focus on improving customer communication, internal office communication is just as important. Poor internal office communication can create a confusing work environment where employee struggle to stay engaged, accomplish tasks, and improve productivity. Products and services will suffer and businesses can even fail entirely. Businesses depend on effective office communication and it […] ## How To Improve Office Communication While companies usually focus on improving customer communication, internal office communication is just as important. Poor internal office communication creates a confusing work environment where employees struggle to stay engaged, accomplish tasks, and improve productivity. Products and services suffer and businesses can even fail entirely. The good news: improving office communication comes down to five concrete tactics — updating your intranet, reducing email dependency, centralizing tools, investing in team building, and creating channels for honest feedback. Each section below covers what to do, common pitfalls to avoid, and how to measure progress. **Here are a few of our favorite internal communication improvements to start implementing change in your office:** ## Incorporate Your Intranet Just about every organization has a company intranet — per Social Edge Consulting, 91% of organizations operate one — but having one isn't the same as using it effectively. The same research finds that nearly a third of employees never log in, and only 13% use their intranet daily. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools, a figure that signals a design and relevance problem, not a technology one. When intranets are up-to-date, modern, and easy to use, they become a one-stop-shop for all of your wide-reaching office communication. Company intranets give employees the power to quickly find both long-standing and unchanging tools, like employee handbooks and vacation request forms. A key reason adoption stalls: only 22% of intranets currently deliver personalized content to employees, meaning most workers receive the same generic updates regardless of role or location (State of the Digital Workplace & Modern Intranet 2024). Persona-driven communications — routing announcements and resources based on employee role, location, or department — measurably reduce information overload compared to broadcast email. For organizations prioritizing mobile-first deployment, a modern intranet platform can achieve 90%+ frontline adoption within the first six months when change management is built into the rollout (Unily, CVS case study). The ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report offers a useful benchmark for evaluating whether your current platform meets modern adoption standards. **Common pitfall:** Launching an intranet without a content governance plan. Assign section owners, set review cadences, and audit stale pages quarterly. ## Depend On Email Less Companies have become too dependent on office email. From company-wide announcements to one-on-one correspondence, the go-to option is always to send an email. While email is certainly a quick and convenient method of office communication, its simplicity makes it easy to overuse. With countless emails received daily, it can take hours to keep all of your information straight, and often ends up as an overwhelming mess. Besides wasting valuable company time and energy, email has no way of prioritizing or categorizing information. The downstream cost is significant: per IDC, employees spend 2.5 hours per day searching for information — a figure that compounds when critical updates are buried in inboxes. Shifting announcements, project updates, and team discussions to a dedicated employee communications platform creates a searchable, categorized record that email simply cannot provide. For a deeper look at this topic, read our whitepaper "Why Activity Stream Is Replacing Email In The Workplace." ## Centralize Your Tools Technology allows us to work faster, more efficiently, and in ways that would have been impossible years ago. But if we aren't smart about it, well-meaning technology can become more of a hindrance than a benefit. Companies today have all kinds of tools to assist their work and improve their efforts, but too often companies rely on tech that can only complete one task. This results in employees having to manage countless different tools just to get their work done. Switching between tools and trying to remember the nuances of each program can take serious time and can inadvertently become a real communication barrier. When employees have a single and centralized program that incorporates all of their needs, office communication becomes much more efficient. The 2026 Internal Communications Trends eBook outlines how organizations are consolidating their communication stacks to reduce context-switching and improve employee engagement across departments. **Common pitfall:** Consolidating tools without involving frontline employees in the selection process. Per Emergence Capital, 80% of the global workforce is deskless, meaning any centralized platform must be mobile-ready from day one — not retrofitted later. ## Invest In Team Building Team building is about more than just having fun with other employees. Social activities strengthen relationships by getting coworkers to talk to each other. And while talking is great for building culture and improving teams, it also pays off during business hours. When employees have genuine friendships at work and know how to communicate together, collaboration naturally occurs. Employees are more willing to share opinions and think creatively in an environment where they know their contributions are appreciated. Team building activities also help employees learn more about their coworkers' communication styles, thought processes, and opinions, clearing the way for easier office communication. Tracking whether team-building investments actually move the needle on employee engagement requires measurement. An employee engagement survey administered before and after a team-building initiative gives managers concrete data rather than anecdotal impressions. The 2026 Workforce Operations Trends eBook covers how leading organizations are tying culture investments to measurable engagement outcomes. ## Encourage Honest Feedback While managers and employers often provide insight for employees, successful office communication requires two-way feedback. When employees feel confident and comfortable enough to share ideas openly, companies can benefit from real insight and inspiration. Employees often have a unique perspective that could greatly increase company success, but are often reluctant to share ideas without an inclusive environment. To foster real feedback from employees, managers need to do more than just put up a suggestion box. Employers need to encourage real, honest, and open feedback under any situation and show employees their ideas are always heard, valued, and taken into real consideration. Employee engagement software can formalize this loop: pulse surveys, anonymous feedback channels, and engagement dashboards give leadership visibility into whether communication improvements are landing — or whether employees are still disengaged. See how this plays out in practice in Closing the Information Gap in Performance Reviews. ## Office Communication With MangoApps An effective office communication strategy is crucial for companies to empower employees. Creating and maintaining successful strategies aren't one-time activities or quick-fix solutions but involve a continuous and well-planned approach. But it doesn't have to be difficult to get started. At MangoApps, our integrated employee app provides companies with the environment to communicate effectively and achieve long-term success — from a modern intranet and centralized messaging to employee engagement surveys and analytics that show what's working. To learn more about strengthening office communication or how MangoApps helps businesses improve their abilities, contact us or schedule a personalized demo today. ## Which Tools Should We Choose for Office Communication? The right tool stack depends on your workforce composition. Organizations with a high share of deskless or frontline workers — per Emergence Capital, that's 80% of the global workforce — need mobile-first platforms that don't require a desktop login. Key criteria to evaluate: Does the platform consolidate messaging, document management, and announcements in one place? Does it support persona-driven content so a warehouse employee and a finance analyst each see role-relevant updates? Does it offer analytics so you can track adoption and engagement rates over time? The Enabling Easy Communication at the American College of Radiology case study is a useful reference for how a large, distributed organization evaluated and deployed a unified communication platform. ## How Long Does It Take to See Results? Timelines vary by organization size and change management investment, but a phased approach consistently outperforms a big-bang rollout. For intranet deployments specifically, organizations that prioritize mobile access and assign internal champions can achieve 90%+ frontline adoption within six months (Unily, CVS case study). For email reduction, teams that migrate project communication to a centralized platform typically report measurable time savings within the first 30 days — largely because IDC's 2.5-hours-per-day information search burden drops when content is searchable and categorized. Set a 90-day baseline measurement using an employee engagement survey before launch so you have a comparison point. ## What If Employees Resist the Change? Resistance is normal and predictable. The most common causes are tool fatigue (employees have already adopted too many platforms), lack of visible leadership participation, and unclear communication about why the change is happening. Mitigation steps that consistently reduce resistance: involve frontline employees in platform selection before rollout, have senior leaders visibly use the new tools in the first 30 days, and tie the change to a specific pain point employees already recognize — like the daily inbox overload. Employee engagement training for managers on how to model new communication behaviors is often the highest-leverage investment in the first quarter. For a broader view of how learning and development intersects with communication culture, see Why Your Learning and Development Strategy Fails (and How to Fix It). --- # Make The Most Out Of Information With MangoApps Forms **Author:** Anjali **Published:** 2019-04-30 **Category:** modules-features Instant online accessibility means so much more than just getting quick directions or asking virtual assistants unusual questions. For businesses, unlimited online access means gathering feedback and sharing resources right away. With the right tools, any organization can effortlessly assemble information from almost anywhere in the world.  At MangoApps, we’ve built forms and trackers for […] # Make The Most Out Of Information With MangoApps Forms Per IDC, employees spend 2.5 hours per day searching for information they cannot easily find. For teams managing distributed workforces, shift-based schedules, and compliance requirements, that figure is not an abstraction — it is a direct cost, measured in delayed decisions, missed approvals, and operational drift that compounds over time. The root cause is usually not a lack of information. It is a lack of structure around how that information moves. Paper forms require transcription before the data becomes actionable. Email-based requests get buried in threads. Spreadsheets maintained outside the HR system create reconciliation gaps that take hours to close. Manual operations built on these patterns do not fail catastrophically — they slow everything down, steadily and invisibly. MangoApps Forms is designed to close that gap. The platform treats form submission not as an isolated event but as a trigger for what happens next: automated approvals, manager notifications, HRIS sync, and real-time tracking — all within the same environment where employees already do their daily work. ## Why the format of data collection determines whether it gets used Per Social Edge Consulting, 91% of organizations operate some form of intranet, but only 13% of employees use those tools daily — and nearly a third never log in at all. SWOOP Analytics found that employees spend an average of six minutes per day inside intranet platforms. Any form tool that requires employees to navigate to a separate system inherits that adoption problem from the start. When employees navigate 6–8 disconnected tools each day to complete their work, friction is cumulative. A paper-based expense report requires a transcription step before the manager can act on it. An email-based incident report creates a tracking gap. A form tool that lives outside the operational workflow creates one more context switch employees have to make — and often do not. Keeping forms inside the platform employees already open daily is a structural advantage over standalone tools. Completion rates rise not because the form itself is better, but because it appears in context — at the moment and in the place where the work is already happening. ## What MangoApps Forms does differently Most form tools are designed for data collection. MangoApps Forms is designed for operations. The distinction matters in practice: every form submission can trigger an automated workflow without IT involvement, routing PTO approvals, expense sign-offs, and shift swap confirmations to the right person in the right context automatically. Forms integrate with HRIS systems to auto-sync employee roles and permissions, eliminating the manual re-entry that creates data errors when employee records live in separate places. When a new hire's role and department are updated in the HR system, their form access updates automatically — no separate administrator task required. Persona-based targeting allows form distribution to be scoped by role, region, or department. A warehouse associate sees the forms relevant to their work. A store manager sees a different set. Neither sees forms that do not apply to them, and neither requires manual routing from an administrator. This kind of precision in operations instructions delivery is especially valuable for organizations managing compliance-heavy workflows across large, distributed teams. The no-code template library covers the most common use cases — expense reports, PTO requests, onboarding checklists, incident reports, and shift-swap forms — so teams can publish a working form the same day they configure it. Organizations that digitize forms and replace paper-based processes with mobile-accessible workflows report up to 50% faster new-hire onboarding. For teams building the ROI case for moving away from manual operations, that is a direct and measurable starting point. ## How mobile-first access enables frontline teams Per Emergence Capital, 80% of the global workforce is deskless. For frontline employees in retail, healthcare, logistics, and manufacturing, any form tool that requires a desktop login is not a form tool — it is a gap in the data collection process. MangoApps Forms is built with mobile-first access as a core design requirement. Frontline employees can submit forms from any personal device without a corporate email address or IT provisioning. Incident reports, equipment checks, and shift handoff notes can be filed in real time from the floor, before the context that makes them useful fades. For [workforce management](/solutions/workforce-management) teams running distributed operations, that immediacy is the difference between a complete record and a reconstructed one. Forms are scoped by shift, location, or role, so a technician in the field sees forms relevant to their work rather than a generic list. The file upload feature extends submissions further: employees attach photos, documents, or other files directly to a submission, turning a field report into a complete record without any follow-up email. ## Setup, integration, and what implementation actually looks like One of the most common questions when evaluating a forms tool is how long it actually takes to go live. For MangoApps Forms, most teams configure and publish their first form within a single working session. The no-code editor and template library eliminate the blank-page problem — select a template, configure permissions and targeting, and publish to mobile and desktop. HRIS sync is configured by an admin in the same interface, with no separate integration project required for standard connections. For organizations managing sop operations across multiple departments or locations, configuration can be scoped granularly: a healthcare team runs a different incident report form than a logistics team, each routing to the appropriate approver automatically. Once live, every form includes a built-in tracker — a searchable, filterable data table where submissions appear as they arrive. The tracker supports export, sharing, and embedding, so HR analysts and operations managers work with form data without switching to a separate reporting tool. Admins see who accessed form data, when, and what action was taken — and permissions can be adjusted by role or group as needs change. For teams building the case for digitizing paper-based workflows, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides a practical framework for evaluating form and workflow digitization against current manual operations processes. ## Security, access control, and compliance Company form data often includes sensitive employee information, compliance records, and documentation that must meet regulatory standards. MangoApps Forms operates within the same security architecture as the broader platform: SSL-based in-transit encryption, configurable mobile access controls, and admin-level permissions management covering who can view, edit, and export submissions. Administrators maintain a full audit view — who accessed form data, when, and what action followed. Permissions are customized by role or group, and stored content can be disabled or wiped when operational or compliance requirements change. For organizations in regulated industries — healthcare, financial services, government contracting — these controls are prerequisites, not optional features. Keeping forms in the same environment as other HR and operations data means no separate audit trail to maintain and no additional data agreement to negotiate with a third-party form provider. ## How MangoApps Forms compares to general-purpose alternatives Typeform and Google Forms are built for external audiences — customer feedback, event registration, one-off surveys. They work well for those use cases. They are not designed for the operational workflows that run inside an organization: HRIS sync, automated approvals, role-based targeting, or teamwork management within a shift-based workforce. When a form submission needs to trigger a manager notification, route to an approver, or update an employee record, a standalone form tool requires custom integration work — a third-party automation layer, a webhook, or a manual export process. In MangoApps, those connections are built in. A submitted shift swap request notifies the manager, routes to approval, and reflects in the schedule within the same workflow. SWOOP Analytics found that employees spend an average of six minutes per day inside intranet tools. Form tools that sit outside the daily workflow inherit that adoption gap by default. Keeping form submission inside the platform employees already open is a structural advantage that feature additions to an external tool cannot replicate. For a broader view of how organizations have built connected operations workflows across large, distributed workforces, see how Raley's centralized data collection and communication for over 20,000 employees in the [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study). ## Collecting external feedback and data MangoApps Forms extend beyond internal employee workflows. A custom form can be shared via public link, embedded on the company website, incorporated into a newsletter, or distributed through social media. All external submissions flow into the same tracker as internal forms, keeping everything centralized without maintaining a separate system for external contributors. For organizations running customer advisory programs, community feedback initiatives, or external partner workflows, this unified collection point removes the need to reconcile data from a separate form tool with internal operations data. Everything is searchable and exportable through the same interface as the rest of the platform. ## What changes when forms are part of the operating environment IDC's finding — 2.5 hours per day lost to information search — is not a habits problem. It is an architecture problem. When data collection happens in a different system from the approvals that follow, and both are separate from the HR records they should update, the cost of that fragmentation shows up in every workflow that depends on the data being current. When forms live inside the same platform as messaging, scheduling, and HR data, the structure of that problem changes. Submissions route automatically. Data syncs without re-entry. Operations managers have visibility into form completion alongside their other operational data, without building a separate report from two systems. For teams evaluating how to move away from paper-based and manual operations workflows, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) provides a framework for assessing digital form deployment across HR and operations processes at scale. Most organizations find the first workflow they digitize is faster to implement than expected — and the return becomes clearer once form data, approval routing, and operations reporting are visible in a single environment. --- # Using MangoApps Recognitions To Produce Better Business Outcomes **Author:** Anjali **Published:** 2019-04-25 **Category:** modules-features The modern workplace is adapting and expanding. Remote teams, increased field work, and flexible schedules all mean managers can’t rely on the methods of the past. Managers need to think creatively, exercise innovation, and develop new ideas in everything they do. While this applies to business goals, it also includes the practice of employee recognition […] # Using MangoApps Recognitions To Produce Better Business Outcomes The modern workplace is adapting and expanding. Remote teams, increased field work, and flexible schedules all mean managers can't rely on the methods of the past. Managers need to think creatively, exercise innovation, and develop new ideas in everything they do. While this applies to business goals, it also includes the practice of employee recognition and reward. Employee retention, engagement, and productivity all depend on a leader's ability to acknowledge fellow employees — and the data backs this up: employees who feel adequately recognized are 45% less likely to leave within two years, and organizations with highly effective recognition programs see 31% lower voluntary turnover compared to those with ineffective programs. When coworkers work in the same office, celebrations and acknowledgment are naturally much simpler. Office parties, award ceremonies, and company outings all help build unity and show employer support. Unfortunately, in the world of remote workforces, showing appreciation can be a little more difficult. At MangoApps, we know that your employees are your biggest asset. So we've designed an engaging and enriching way to celebrate employee, team, and company success as part of a unified [employee experience platform](/solutions/employee-engagement) — not a standalone feature bolted on after the fact. In this post, we'll outline a few of the ways employers can use MangoApps Recognitions to build company culture and showcase success. ## Supporting Team Accomplishments MangoApps Recognitions makes it easy to celebrate the hard work of any team, department, or group within the organization. With recognitions available through MangoApps, you can highlight teams working together at the local level or spread throughout the globe. Either way, support and encouragement from leaders will be visible for everyone to see, bringing their achievements to light and helping every team member feel appreciated, supported, and encouraged. Appreciating the work of an entire team has long-lasting effects throughout the organization, as each group strives to do their best and is bolstered by regular and sincere acknowledgment. Recognition programs that include peer-to-peer recognition are significantly more likely to produce positive business outcomes than manager-only programs, because coworkers observe day-to-day contributions that managers miss (per SHRM/Workhuman research on peer recognition effectiveness). With MangoApps, it's easy to select the team you want to recognize and create a personalized message about their accomplishment — and because recognition lives inside the same platform employees use for communication and task management, participation rates are higher than with standalone recognition apps that require a separate login (per Unily/unified employee experience platform category research). See how this plays out in practice in [From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program). ## Recognizing Individual Employee Success Employees work hard for your company every day, achieving goals and helping your business grow. Regular and supportive feedback is one of the best ways to show employees you are aware of their efforts and support their continual contributions. When employees feel valued, understood, and listened to, they naturally reciprocate, creating a happy, healthy, and successful work environment. Employee awards also help inspire each member toward new goals and increased accomplishment. MangoApps Rewards allow both coworkers and company leaders to send support and encouragement across the organization. Employee rewards can be displayed company-wide, within a specific group or team, or to the user's followers. Employee awards are also stored on an employee's personal profile page. This allows employees to proudly display their success and build a positive reputation. From major achievements to smaller day-to-day successes, users can celebrate anything and everything within the organization. For organizations tracking the impact of recognition on employee engagement, the [key-features/rewards-and-recognition](/key-features/rewards-and-recognition) page outlines how recognition data feeds directly into employee profiles and engagement analytics — giving HR teams a measurable signal rather than a gut feeling. For a broader look at how recognition connects to performance outcomes, the [solutions/performance-management](/solutions/performance-management) page shows how these tools work together across the platform. ## Sharing Personal Milestones and Achievements Even though we interact with coworkers on a regular basis, it is sometimes easy to forget that they have important personal achievements happening outside of the office. Personal milestones and achievements help employees connect together and celebrate success on every level. From a new move to a new baby, the moments that happen after work hours are also important to recognize and share. As employees learn more about each other, they create stronger work relationships and a dedicated and devoted company culture. Sharing personal events with coworkers and peers makes employees feel connected with the workplace and engaged in their environment. This is especially important for frontline and deskless employees, who are disproportionately excluded from traditional recognition programs because they lack corporate email or intranet access — creating an employee engagement gap that mobile-first recognition tools directly address (per Beekeeper/frontline workforce product category research). Per Emergence Capital, 80% of the global workforce is deskless, meaning the majority of employees have historically been invisible to recognition programs designed around a desk and a corporate inbox. MangoApps Recognitions reaches these workers where they are. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) explores how leading organizations are closing this gap as part of a broader employee experience strategy. ## MangoApps Recognitions All of the recognitions available in MangoApps are made to facilitate employee interaction. Coworkers and supervisors alike can easily comment, react, and add attachments to recognitions, making it easy to congratulate a team or wish someone a happy birthday. Recognitions help employees and teams understand their value and feel appreciated in their workplace, turning a typical job into a supportive and enriching work experience. With likes, reactions, and commenting in MangoApps Recognitions, your workforce is much more involved with all kinds of events, and can build a fun, inviting, and engaging company culture. To learn more about building an uplifting company culture or to see MangoApps Recognitions at work in your own business, contact us or schedule a free, personalized demo today. schedule demo ## What Business Outcomes Should We Expect From a Recognition Program? The title of this article promises better business outcomes, so here is the direct answer: structured recognition programs tied to a unified employee experience platform produce measurable improvements in three areas. **Retention.** Employees who feel adequately recognized are 45% less likely to leave within two years. Organizations with highly effective recognition programs see 31% lower voluntary turnover compared to those with ineffective programs. Given that replacing an employee typically costs 50–200% of their annual salary, even a modest reduction in voluntary turnover produces significant cost avoidance. **Engagement.** Per Gallup's research (see [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace)), low employee engagement costs the global economy roughly $8.9 trillion annually. Recognition is one of the highest-leverage, lowest-cost levers available to managers — particularly when it is delivered in the flow of work rather than through a separate system employees must remember to log into. **Participation and reach.** Recognition that lives inside the platform employees already use for daily communication sees higher participation rates than standalone tools. For frontline-heavy industries — hospitality, BPO, nonprofit — this distinction is especially significant, because workers without a corporate desk or email address are otherwise invisible to recognition programs. MangoApps is built to reach [industries/hospitality](/industries/hospitality), [industries/bpo](/industries/bpo), and [industries/nonprofit](/industries/nonprofit) workforces through a mobile-first experience that requires no corporate email. ## How Do We Measure the Impact of Recognition? Measuring recognition impact starts with connecting recognition activity to the engagement and retention data you already track. Within MangoApps, recognition events are stored on employee profiles and visible in engagement analytics, giving HR teams a record of who is being recognized, how often, and by whom. This data can surface gaps — teams or individuals who are rarely acknowledged — before those gaps become turnover events. For organizations building or refining a measurement framework, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading companies are tying recognition frequency to engagement survey scores and voluntary turnover rates. Employee engagement software that integrates recognition, communication, and performance data in one place makes this analysis far more tractable than stitching together data from three separate tools. If your organization is evaluating employee engagement software or an employee experience platform more broadly, [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides independent third-party context on how MangoApps compares across the category. --- # How Customers Use MangoApps Employee Profiles **Author:** April Thomas **Published:** 2019-04-18 **Category:** modules-features At MangoApps, we’re proud of our products and how they help every user create an individualized experience. We know that working in a completely customizable environment can sometimes be a daunting experience. To help our new users get started, we’ve asked current clients to share a few examples of how they use MangoApps Employee Profiles. […] ## How Customers Use MangoApps Employee Profiles At MangoApps, we know that working in a fully customizable intranet environment can feel daunting at first. To help new users get started, we've asked current clients to share how they use MangoApps Employee Profiles — and what outcomes they've seen. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in. Rich, searchable employee profiles are one of the most direct ways to change that equation by giving people a reason to show up. As our long-term clients share their own experiences, we hope you'll begin thinking about your own company and how MangoApps Employee Profiles can help you. ## Build Successful Teams One of our marketing clients uses MangoApps Employee Profiles to build project teams from internal talent before looking externally. This client works with businesses across a wide range of regions and industries. By searching an employee's unique skills and work experience, the team is better able to assemble groups with the specific industry insights and regional knowledge each engagement requires. Searching through employee skills and experiences has also given established teams access to more internal resources — colleagues can ask questions, share ideas, or gain insight from others with similar backgrounds. MangoApps profiles can be synced automatically from HRIS data, keeping roles, permissions, and org-chart positions current without manual admin work — eliminating the stale-directory problem that causes employees to distrust people-search tools in the first place. Explore the employee directory and employee data capabilities to see how skills-based search works in practice. ## Access Info On The Go One of our distribution customers relies on MangoApps Employee Profiles to access important contact information on the go. Distribution employees are often out of the office delivering products, meeting vendors, or visiting other branches. With MangoApps Employee Profiles, phone numbers and addresses are fully interactive, allowing users to save contact information directly into their phone or make a call right then and there. You can search through employee profiles by name, location, and more, making it a portable employee directory for a workforce that's rarely at a desk. This matters more than it might seem: per Emergence Capital, 80% of the global workforce is deskless. Frontline employees can access profiles and the employee directory without a corporate email address or VPN, making people-search viable for workers who have never had a company login. Our distribution client has significantly increased communication throughout their organization as traveling employees have been able to keep in touch with coworkers and find contact information for people in new areas. Per IDC, employees spend an average of 2.5 hours per day searching for information — interactive, mobile-accessible profiles cut directly into that lost time. ## Learn About Employees A retail client uses MangoApps Employee Profiles to help colleagues and future coworkers connect before their first shift together. Supervisors and coworkers can access a new employee's profile photo, personal bio, work history, and more. The new employee can also look up coworkers at their new location, learn names and faces right away, and get to know more about the area. Retail intranet deployments that include rich employee profiles have been linked to faster shift-team assembly and reduced manager time spent on introductions — a vertical-specific outcome that directly affects scheduling efficiency. For more on that angle, see [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling). This helps everyone connect on a more personal level, smoothing employee transitions and creating a more united work environment. Replacing a single frontline employee costs between $4,400 and $15,000 on average — connection tools that reduce early attrition pay for themselves quickly. ## Empower New Employees An education-focused client uses MangoApps Employee Profiles to simplify and streamline the onboarding process. In addition to detailed user information, MangoApps Employee Profiles include interactive and visual org charts. These org charts help new hires easily learn company hierarchy and understand unique team dynamics. Employees can also visit personal profiles to learn more about individual supervisors, coworkers, and direct reports. Descriptive employee profiles let you match faces to names, helping new hires interact confidently with peers from day one. As a result, new educators feel like they fit in right away and are able to contribute to learning outcomes more effectively. For organizations thinking about how profile-driven onboarding connects to broader learning strategy, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) is a useful companion read. ## What Features Make Employee Profiles Work? The use cases above share a few common enablers worth naming explicitly: - **HRIS sync:** Profiles pull live data from your HR system of record, so org charts and role information stay accurate without manual updates. See how this fits into a [modern HCM](/solutions/modern-hcm) approach. - **Mobile-first access:** Field and frontline employees reach profiles from any device, with no corporate email or VPN required — critical given that 80% of the global workforce is deskless, per Emergence Capital. - **Skills and experience search:** Managers can filter by skill, location, department, or work history to find the right person for a project or shift without posting an external job. - **Interactive org charts:** Visual hierarchy maps help new hires and cross-functional teams understand reporting lines and find the right point of contact fast. - **No-email directory access:** Per Social Edge Consulting, only 13% of employees use an intranet daily, and the average daily time spent in intranet tools is just six minutes, per SWOOP Analytics. Profiles that are genuinely easy to reach — from a mobile home screen, not buried behind a VPN — are what close that gap. For a broader look at how these capabilities fit together, the [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarking across platforms. ## How Do I Set Up and Maintain Employee Profiles? Setup typically involves three steps: connecting MangoApps to your HRIS (such as Workday, ADP, or BambooHR) to import baseline profile data, configuring which fields are visible to which audiences, and deciding which fields employees can self-edit. Once the HRIS connection is live, new hires appear in the directory automatically and role changes propagate without admin intervention. Organizations that want to go further can layer in custom fields — certifications, languages spoken, project history — that employees maintain themselves. The [workforce management](/solutions/workforce-management) and [employee app](/solutions/employee-app) pages walk through configuration options in more detail. For benchmarks on what successful adoption looks like, case studies have documented 90% frontline adoption within six months when profiles are accessible from a mobile home screen and tied to a daily workflow like shift check-in or task assignment. ## Is MangoApps the Right Fit for My Industry? The four use cases above span distribution, retail, marketing services, and education — but the underlying need (finding the right person, fast, with accurate information) is consistent across industries. Organizations in regulated sectors such as financial services face additional requirements around data access and permissions; the [financial services](/industries/financial) page covers how MangoApps handles those constraints. For a view of how MangoApps has been evaluated against other intranet platforms, [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides third-party context. ## The Bottom Line MangoApps Employee Profiles solve a specific, measurable problem: employees waste 2.5 hours per day searching for information (per IDC), and nearly a third never log into their intranet at all (per Social Edge Consulting). Profiles that are mobile-accessible, HRIS-synced, and searchable by skill or location give employees a reason to open the intranet — and give managers a way to build teams, onboard new hires, and connect a distributed workforce without relying on outdated spreadsheets or email chains. If you're ready to see how MangoApps Employee Profiles would work in your organization, [schedule a demo](/solutions/employee-app) or explore the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) to see how leading organizations are approaching employee experience this year. --- # 5 Ways To Transform Employee Smartphones Into A Business Advantage **Author:** Anna Carriveau **Published:** 2019-04-16 **Category:** integrated-digital-workplace Smartphones have transformed the modern world. With so much information so easily available, it’s not surprising that most people seem to always have their phone within arms reach.  So how can your business leverage this? Not to worry, we’ve got you covered. Here are a few of our favorite ways your company can transform employee […] ## 5 Ways To Transform Employee Smartphones Into A Business Advantage Smartphones have transformed the modern world. With so much information so easily available, it's not surprising that most people seem to always have their phone within arm's reach. Over 80% of the global workforce is deskless, making mobile access the primary — not supplementary — channel for the majority of employees worldwide. So how can your business leverage this? Here are five ways your company can transform employee smartphones into a successful business solution — along with what to consider when it comes to security, BYOD policies, and tool selection. ### Increase Employee Availability Smartphones make your employees reachable anywhere. By enabling employees to use smartphones, you greatly increase their range of availability. Smartphones help employees stay in constant communication wherever they might be. Coworkers will be able to collaborate and work effectively together while traveling, working across different time zones, or on-the-go. With rising customer demands expecting support at all hours of the day, increased employee availability is a significant advantage in the business world. Allowing your team to work with smartphones helps employees utilize their most productive hours. Integrating smartphones into the workday establishes long-term habits of responsive workplace communication. Employee engagement improves measurably when workers feel reachable and heard. Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback — and mobile availability is one of the most direct ways to create that feedback loop. ### Improve Collaboration Abilities Effective collaboration is how big ideas reach their full potential. In today's world of distractions and never-ending competitors, successful ideas are more important than ever. Easily connecting employees through [team collaboration tools](/solutions/employee-communications) can help organizations draw insights from across the company. Coworkers in different offices (or even in different countries) can now brainstorm, discuss, and collaborate together. Enabling employees to access collaboration tools on their smartphone takes this collaboration one step further. It may not always be possible for employees to work from their computers, especially when working remotely, traveling, or collaborating with coworkers in another time zone. One underappreciated friction point: employees navigating 6–8 disconnected tools daily lose meaningful productive time. Consolidating those tools into one mobile experience directly addresses the tool-sprawl problem that undermines collaboration at scale (per MangoApps unified platform research). The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) explores how leading organizations are rationalizing their communication stacks to close this gap. ### Extend Executive Outreach Executives and senior employees are incredibly busy and are often attending meetings and traveling away from the office. When executives are unavailable, it can create a serious disconnect between leadership and their teams. Employers need the flexibility to understand risks and pay attention to teams no matter where they might be. Enabling everyone to work with their employee smartphones bridges this gap by keeping leaders and employees in regular communication. Employers can immediately communicate new ideas, policy updates, and important information to their teams, helping them adapt and implement new changes and stay in the loop. Additionally, employees have a reliable outlet to reach out to supervisors and provide them with important news, updates, and developments. Smartphones keep everyone up-to-date and help companies make the most of regular travel or a busy schedule. Note that only 22% of company intranets currently deliver personalized content to employees, per the State of the Digital Workplace & Modern Intranet, 2024 — meaning most organizations are broadcasting the same message to everyone rather than surfacing what's relevant by role or location. Mobile platforms that support personalization close this gap at the leadership communication layer. ### Empower Field Employees Clinicians, retail employees, drivers, and all kinds of other occupations require employees to regularly operate away from a desk. And to make matters even more difficult, field employees often need updates even more than traditional office employees. Per Gartner, 2023, 47% of workers struggle to find necessary information at least half the time — a problem that is acute for deskless workers who can't simply walk to a shared drive. Creating a mobile-friendly environment makes it easy to communicate important information to field employees. But the most effective approach goes further: a single branded [mobile employee app](/solutions/employee-app) lets frontline workers access shifts, HR self-service, employee engagement training, and team communications without a corporate email address or VPN — removing the most common access barriers for deskless workers (per MangoApps mobile employee app product page). Field employees in areas with limited connectivity also require offline access for critical documents and app content, a capability gap that generic smartphone policies don't address (per MangoApps mobile employee app product page). The operational upside is measurable. Replacing a single frontline employee costs between $4,400 and $15,000. Replacing paper processes and siloed systems with a single mobile hub has been shown to reduce employee turnover by 26% in frontline-heavy industries such as transit and logistics (per Joinblink / Go North West case study). For healthcare organizations managing clinical staff in the field, see how mobile-first communication applies in [ambulatory care settings](/industries/ambulatory-care). Grocery and retail operators can explore a parallel model in the [Raley's Companies' success story](/resources/raleys-case-study), where MangoApps connected 20,000 employees across locations. Modern mobile deployments also extend beyond document access into operational workflows: AI-assisted scheduling, shift swaps, time tracking, and SOP operations checklists are now standard capabilities in leading mobile employee platforms — not just communication channels. ### Strengthen Company Culture Social media and instant messaging have transformed human communication immensely over the past decade. Everywhere you look, people seem to be glued to their mobile screens scrolling through news feeds, looking at multimedia content, and talking to friends. What if that same engagement was found in your internal company communication? Employee engagement software, like MangoApps, lets employees create social media-inspired intranet portals that can be accessed on a smartphone through a dedicated company app. These portals let coworkers communicate and socialize at any time, helping strengthen employee relationships and promote friendships outside of normal office hours. As employees are able to support, uplift, and have fun together, company and team culture naturally grows. For organizations looking to formalize this approach, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines how culture-building through mobile communication connects to broader employee engagement strategy and retention outcomes. ### MangoApps While smartphones might cause distractions and disruptions in an academic environment, they can also be the perfect tool for exceptional business success. When encouraged and implemented effectively, employee smartphones allow employees to increase productivity and communication across every layer of the organization — from the executive suite to the frontline. One large enterprise deployment achieved 90% frontline adoption within the first six months, demonstrating that mobile rollout speed is measurable and fast. To learn more about successfully incorporating employee smartphones, or how MangoApps helps organizations make the most of mobile communication, contact us or schedule a personalized demo with us today. --- ## What Security Risks Should You Address Before Rolling Out Employee Smartphones? Mobile enablement introduces real security considerations that belong in any implementation plan. The most common risks include unsecured Wi-Fi connections, lost or stolen devices with access to company data, and shadow IT when employees use personal apps to fill gaps left by inadequate official tools. A BYOD (bring your own device) policy should define minimum OS version requirements, mandate device encryption, establish remote-wipe authority for lost devices, and specify which apps are approved for business use. Containerization — separating personal and work data on the same device — is the standard technical control for BYOD environments. Platforms that require no VPN and no corporate email for frontline access (as MangoApps does) reduce the attack surface compared to solutions that route all traffic through a corporate network. ## How Do You Build a BYOD Policy That Employees Actually Follow? A BYOD policy fails when it reads like a legal document and gets buried in an onboarding packet. Effective policies are short, written in plain language, and communicated through the same mobile channel employees are being asked to use. Key elements include: a clear statement of what the company can and cannot access on a personal device, reimbursement terms if applicable, acceptable-use guidelines, and a simple process for reporting a lost device. Involving frontline managers in drafting the policy — rather than issuing it top-down — increases buy-in. For unionized workforces, BYOD terms may need to be negotiated; see [Managing a Unionized Workforce Is Different. Your Software Should Be Too.](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) for guidance on that specific context. ## How Do You Choose the Right Mobile Employee Engagement Software? The right employee engagement software for mobile deployment should meet four criteria: it works without a corporate email or VPN (critical for frontline access), it consolidates communication, scheduling, and document access in one place rather than adding another tool to the stack, it supports offline access for field workers in low-connectivity environments, and it provides administrators with analytics to measure adoption and engagement. Per McKinsey research, 81% of leading companies effectively use data and analytics tools — meaning measurement capability is a differentiator, not a nice-to-have. For a broader view of how workforce operations technology is evolving, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) is a practical starting point for evaluating platforms against current benchmarks. --- # How MangoApps Simplifies the Getting Started Experience **Author:** Anjali **Published:** 2019-04-11 **Category:** modules-features Over the years company intranets have become an indispensable part of any digital workplace. When deployed successfully, intranets can improve communication, enhance collaboration, and encourage productivity throughout the workplace. But transitioning to a new work platform can feel a little intimidating. MangoApps’ simple, step-by-step, getting started process always keeps new users in mind and makes […] # How MangoApps Simplifies the Getting Started Experience Per Social Edge Consulting, 91% of organizations operate an intranet — yet only 13% of employees use one daily, and nearly a third never log in at all. SWOOP Analytics puts average active-user time at just six minutes per day. That gap between deployment and daily use is not a product quality problem. It is an onboarding problem: employees who don't successfully navigate a new platform in the first week rarely return for a second look. MangoApps addresses this by treating the getting-started experience as a first-class feature rather than a post-launch afterthought. Configuration happens on the admin side before any employee invitation goes out. The employee-facing flow is guided, step-by-step, and completable in under 15 minutes. Most organizations reach full team adoption within 90 days — a meaningful contrast to traditional intranet deployments, which can take months of IT-led customization before a single employee logs in. ## Why traditional intranet onboarding fails The standard approach assigns IT a platform configuration job and HR a communication job, then hopes the two land at the same time for every employee. It rarely does. Corporate desk workers with company email addresses get access. Frontline staff — warehouse teams, retail associates, healthcare workers — get left out because they don't have a company email address, which most platforms require for the invitation flow. Emergence Capital estimates that 80% of the global workforce is deskless. An intranet that only reaches the other 20% is not an intranet — it is a document repository for managers. MangoApps supports login without a corporate email address, so frontline employees can participate in the getting-started experience on the same day as their desk-based colleagues, through the [employee app](/solutions/employee-app). The retention implications are real: replacing a frontline employee who never successfully onboards to the intranet costs organizations between $4,400 and $15,000 per departure, making a frictionless getting-started experience a retention issue, not just a UX concern. ## Before the first invitation goes out The MangoApps onboarding process begins before any employee touches the platform. MangoApps representatives work with admin teams to evaluate business objectives, configure the domain, and set up the [modern intranet](/solutions/modern-intranet) environment to reflect the organization's structure and culture. Branding, navigation, module selection, and dashboard layout are handled in this pre-launch phase so the platform employees see on day one looks like their actual organization — not a generic template. This front-loading is deliberate. The fewer decisions an employee has to make on first login, the more likely they are to complete the getting-started flow and return. IDC research finds that employees spend an average of 2.5 hours per day searching for information. Reducing that number starts at onboarding, not after — when employees know where to find things immediately, information-seeking time drops. Administrators control the entire invitation process from the domain portal. Users can be added individually by email, imported in bulk via CSV, or brought in as guest users — contractors, freelancers, or clients who benefit from regular access without full employee status. Each approach feeds into the same getting-started flow, giving every user the same guided first-login experience regardless of how they were provisioned. ## The getting-started flow employees actually complete When a new user logs in for the first time, they walk through a sequence of guided steps. Domain administrators control which steps appear and in what order, with the ability to enable, configure, or reorder from the admin portal at any time. The available steps include: **Introduction video** — An admin-supplied or out-of-the-box video that sets expectations and orients new users to what MangoApps is for, not just how to navigate it. **Privacy policy** — More than compliance language, this step is where enterprise governance begins. Administrators can enforce SSO, SAML authentication requirements, and password policies directly within the getting-started flow, establishing security posture before any employee accesses sensitive content. For organizations under regulatory scrutiny, this layer ensures governance is in place from the first login rather than as a retroactive control. **Change password** — Employees set a personal login credential with admin-configured strength requirements and character limits. **Profile overview and About Me** — New users fill in their profile photo, name, employee ID, skills, and areas of expertise. A complete profile from day one makes the colleague discovery and team recommendation features immediately useful rather than empty. **Locale settings** — Date format, time format, time zone, and language. Particularly important for distributed teams where a single default setting serves no one correctly. **Team recommendations** — New employees often don't know which groups, projects, or departments to join first. This step surfaces relevant communities so employees enter a social context from the start rather than landing on a blank, static dashboard. **Notification preferences** — Employees configure which updates they receive and through which channels. Setting this early keeps engagement high without overwhelming anyone in their first week. **Custom steps** — Administrators can insert their own steps using video content, rich text, or profile information — a mechanism for embedding compliance acknowledgments, culture content, or role-specific context directly into the flow. For organizations with specific regulatory requirements or complex departmental onboarding, this step does the work that otherwise lands in an employee's email inbox and gets ignored. For organizations that connect learning and development content to their onboarding workflow, the [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers how leading organizations integrate onboarding with daily work rather than treating them as separate programs. ## The first 30 days: dashboards and guided discovery After the initial getting-started sequence, the MangoApps dashboard becomes the primary tool for easing employees into regular use. Administrators configure new user dashboards with widgets designed to keep first-time users oriented without requiring them to self-navigate: **Getting Started Mission** — Surfaces key modules and features, revisitable after the initial flow is complete for employees who want to explore further. **Colleague Suggestions and Colleagues I Follow** — Builds the social graph that brings employees back to the platform as a communication channel, not just a document repository. **Group Suggestions** — Reinforces the team recommendations from the getting-started flow, continuing to reduce the "I don't know where to go" problem into the second and third weeks. **Announcements and Must Read Posts** — Connects employees to active company communication from day one, making the intranet feel live rather than static. **Invite Colleagues** — Turns engaged early adopters into a recruitment channel within the platform. Employees who successfully onboard become advocates for the platform among peers who haven't yet joined. The first weeks are the highest-churn period in any intranet adoption. Dashboard design during this window determines whether employees develop a habit or quietly stop logging in. ## When to consider a soft rollout For large organizations or workforces unfamiliar with collaboration technology, a staggered rollout reduces risk and improves feedback quality. A soft rollout selects a smaller group — a department, a region, a job function — to complete the getting-started experience before the platform opens to all employees. The feedback gathered during this phase typically surfaces configuration gaps that are far easier to address before thousands of employees encounter them simultaneously. Organizations that have followed a structured launch approach report significant results. OU Health achieved 87% workforce engagement within months of launching a branded intranet app. PetSmart reported a 4x industry engagement multiple after a mobile-first intranet launch. Both outcomes depended on deliberate onboarding sequences — not just platform availability. Making the technology accessible without a structured getting-started experience rarely produces numbers like those. ## What to expect after day 1: the questions teams actually ask The getting-started flow answers "what is this and how do I set it up." The questions that follow tend to be harder. **How do we know whether onboarding is working?** Three metrics matter in the first 90 days: daily active user rate (what percentage of invited employees return after their first login), getting-started completion rate (what percentage of users finish the full onboarding flow), and time-to-first-contribution (how long before a new user posts, comments, or joins a group). Tracking all three reveals where the funnel breaks. A high completion rate with low daily active users points to a dashboard problem. A low completion rate points to the getting-started flow itself. **What happens when employees don't have a corporate email address?** MangoApps supports login without a corporate email, so frontline workers in retail, healthcare, manufacturing, and logistics can participate from day one. Administrators configure alternate authentication flows for these users within the same admin portal used for desk-based employees — there is no separate system to maintain and no reason to treat deskless staff as a second rollout phase. Including them from the beginning improves overall adoption numbers and eliminates the communication equity gap that emerges when frontline teams are on a separate, delayed timeline. **How long does the admin-side configuration take?** Most organizations complete the domain setup, branding, getting-started step sequencing, and dashboard configuration in partnership with MangoApps representatives within a few weeks. The employee-facing getting-started flow itself takes a new user fewer than 15 minutes to complete. For large enterprises using a soft rollout, the full company-wide launch typically lands within 60–90 days of the initial kickoff. **How does MangoApps compare to other intranet platforms?** The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarking across the major intranet platforms on deployment speed, configurability, and employee experience. MangoApps' differentiated elements in the getting-started flow — the no-email frontline access option, admin-controlled step sequencing, enterprise security governance built into the privacy policy and password steps, and the dashboard widget system — are evaluated alongside competitors' onboarding approaches in that analysis. **What does IT have to manage on an ongoing basis?** After the initial domain configuration, the getting-started flow requires no IT involvement to maintain. Administrators add, reorder, or disable steps from the admin portal at any time. New user invitations, bulk provisioning, and guest user access are all self-service. ## The outcome a structured getting-started experience produces A frictionless onboarding sequence is not primarily an IT success metric. It is a business outcome with a measurable cost attached. Per Social Edge Consulting, nearly a third of employees never log in to their organization's intranet. Every one of those employees represents a platform investment that returned nothing — and often a communication gap that HR and operations teams filled through less efficient channels like email chains, group chats, and printed memos. MangoApps targets full team adoption within 90 days by front-loading configuration on the admin side and keeping the employee-facing flow to a guided sequence completable in under 15 minutes, with no IT intervention required after setup. The security governance layer — SSO, SAML, and password policy enforcement built directly into the getting-started steps — means security posture is established at first login rather than managed as a separate configuration exercise after the fact. The intranet an employee successfully onboards to in week one is the intranet they use in month six. Features, integrations, and analytics all depend on that first impression landing correctly — and on every employee, not just the desk-based majority, having a path to get there. --- # Improve Company Connectivity With MangoApps Groups **Author:** Anjali **Published:** 2019-04-09 **Category:** modules-features Company intranets have changed and evolved over the years. From its origins as a simple document management platform to the extensive business collaboration system it is today, intranets continue to adapt and grow to meet the needs of a modern business.  Intranets benefit organizations by increasing productivity, efficiency, and employee engagement. But if employees are […] # Improve Company Connectivity With MangoApps Groups Per IDC, employees spend an average of 2.5 hours per day searching for information. Per Social Edge Consulting, nearly a third of employees never log in to the company intranet at all, and only 13% use intranet tools daily. Those numbers are not indictments of employee motivation — they are measurements of a structural design problem: intranets built to push information down from the top give employees no reason to come back. The fix is not more content or a better homepage. It is a peer layer. Structured communities — purpose-built groups organized around how employees actually work, not around org-chart hierarchy — are what turn a passive intranet into a platform people use voluntarily. MangoApps Groups provides that layer. ## Why broadcast intranets lose most employees before they engage The adoption failure of most intranets follows a predictable arc: the platform launches, participation is strong for the first few weeks, and then utilization quietly collapses. Per SWOOP Analytics, the average employee spends just six minutes per day on intranet tools. That is not a communication failure — it is a consequence of building a one-directional channel and expecting two-directional behavior. Per Emergence Capital, 80% of the global workforce is deskless. Retail associates, hospital floor staff, distribution workers, and field technicians do not have managed laptops or corporate email addresses. An intranet that requires either to log in has structurally excluded the majority of the workforce before any design decision is made. The 13% daily utilization rate is not a ceiling — it is an artifact of who the intranet was built for. Groups solve both problems simultaneously. They give employees a specific community with content relevant to their work, rather than a generic feed they did not ask to subscribe to. And when designed with mobile-first access, they reach the employees a desktop-only intranet never will. ## How to structure groups around the work, not the org chart The most common mistake in group design is treating the org chart as the only valid organizing logic. Reporting structures produce groups, but they do not always produce active communities. Three more durable organizing principles tend to outperform hierarchy-based structures over time. **Purpose-based groups** unite employees who collaborate toward a shared goal — a project team, a department, or a cross-functional committee. These groups are the most intuitive to launch, but also the most likely to go quiet after the immediate purpose is resolved. Build in a recurring mechanism — a standing agenda, a shared reference library, a weekly question — to keep them active beyond the project that created them. **Expertise-based groups** connect employees who share a skill set or role regardless of where they sit in the organization. These are the communities where institutional knowledge lives: where a new nurse asks an experienced colleague how to handle an edge case, or where a field technician shares a fix that saves the next person three hours. Per IDC, structured groups with clear ownership and searchable content can meaningfully reduce the 2.5 hours per day employees spend searching for information — a faster path to an answer than any search bar. **Interest-based groups** — sports teams, wellness channels, book clubs — may seem peripheral, but they build the relational layer that makes employees more willing to participate honestly in work channels. The psychological safety that develops in informal communities transfers into professional ones. Event-based groups — organized around recurring meetings, seasonal initiatives, or milestone activities — are underused but effective. They give occasional collaborators a structured space to coordinate without cluttering the broader community feed, and they archive naturally once the event passes. For globally distributed or shift-based teams, language is a design constraint that rarely surfaces until utilization reports make it visible. Groups designed for a single language exclude non-English-speaking employees even when they are technically enrolled. MangoApps supports multilingual feeds and real-time translation, which removes the adoption barrier that causes non-participation among frontline employees who were never structurally reachable in the first place. ## Permission tiers and enterprise security governance Not all group content should be visible to all employees. MangoApps supports three permission tiers that map cleanly to most organizational security requirements. **Public groups** are open to any member of the organization. They work well for organization-wide communities — IT support queues, internal learning resources, all-hands discussion threads — where broad participation is the goal. **Private groups** appear in directory listings but require approval to join. Members can request access or be invited by an admin. These are appropriate for department-level workspaces, project-specific communities, and any group whose content is sensitive enough to warrant a controlled membership model. **Unlisted groups** are invisible to everyone except the creator and invited members. They do not appear in search results or group directories. These are designed for executive discussions, HR matters, and legal review processes where even listing the group is inappropriate. For enterprise deployments, manual permission management does not scale. MangoApps supports SAML 2.0, single sign-on (SSO), and HRIS-synced role permissions, which means group membership updates automatically as employees change roles. A nurse promoted to charge nurse is added to the right groups; a contractor who exits is removed. This positions groups as governed infrastructure rather than an access-controlled chat space. [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarks for evaluating how permission governance compares across leading platforms. ## Reaching the employees traditional intranets miss The deskless workforce exclusion problem is solvable, but it requires a specific design choice: group access cannot depend on a corporate email address or VPN connection. MangoApps addresses this through its [employee app](/solutions/employee-app), which allows frontline and no-email employees to participate in groups via mobile without a managed device. This is not an edge-case feature — it is the primary mechanism for closing the utilization gap that data on the 80% deskless workforce consistently reveals. Once mobile access is available, personalized content surfacing determines whether employees actually engage. MangoApps' AI-assisted search and content recommendations surface relevant group content automatically in employees' feeds, reducing the need to remember which groups they belong to and manually navigate to each one. Groups that deliver role- and location-targeted content rather than an undifferentiated broadcast show meaningfully higher daily active usage rates among frontline employees. Group sprawl is the failure mode that follows successful launch. Organizations that allow unrestricted group creation often end up with dozens of overlapping, abandoned groups within a year. Establish a naming convention, a clear ownership requirement, and a quarterly review to archive inactive groups and consolidate duplicates. A group with a single admin is fragile — designate at least two per group so that no single departure causes a community to go unmanaged. ## Measuring whether your groups are generating engagement or just membership Enrollment in a group is not the same as activity in a group. The distinction matters because most intranet analytics report membership counts, which look healthy even as utilization collapses. Per Social Edge Consulting, 91% of organizations operate an intranet — but the gap between that figure and the 13% daily utilization rate shows that deployment and adoption are not the same problem. Four metrics give a clearer picture of whether groups are working. **Active membership rate**: What share of enrolled members post, comment, or react at least once per week? A rate below 20% typically signals that the group's purpose is not compelling enough to drive return visits. **Content contribution spread**: Are a handful of admins generating all content, or is participation distributed across members? Groups with distributed contribution are healthier and more resilient — a single admin going on leave does not silence the community. **Membership retention at 90 days**: Groups that lose more than 30% of active members in their first 90 days usually lack a recurring purpose or consistent posting cadence. Intervene early rather than attempting a relaunch after the community has gone quiet. **Search-to-group traffic**: MangoApps analytics can show how often users arrive at group content via search versus direct navigation — a proxy for whether the content is genuinely discoverable or only accessible to employees who already know where to look. Distributing employee engagement surveys through group channels — rather than generic email blasts — also improves response rates, because the survey reaches employees in the context of their daily work community rather than as an interruption. OU Health achieved 87% workforce engagement within a few months of launching a group-enabled mobile employee app, a result that reflects what happens when groups reach the full workforce rather than only the portion that sits at a desk. ## How groups fit into a broader intranet strategy Groups handle the peer-to-peer and community layer of a modern intranet. The company portal and department sites handle structured, top-down content. Together they cover the full range of how employees seek and share information — broadcast, peer-generated, and search-discovered. For organizations building that architecture, the MangoApps [modern intranet solution](/solutions/modern-intranet) integrates groups with portal content, department sites, and unified search. Replacing a frontline employee costs between $4,400 and $15,000 when recruiting, onboarding, and lost productivity are fully accounted for. Groups that genuinely reach deskless workers — not just desk-based employees — are one of the most measurable ways to reduce that cost over time. For context on how organizations are structuring internal community governance at scale, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the group adoption patterns that consistently correlate with sustained employee engagement scores across modern intranet deployments. --- # How To Create The Best Onboarding Experience **Author:** Anna Carriveau **Published:** 2019-04-02 **Category:** company-culture How can your organization create the best onboarding experience possible to accommodate for new hires? In order for any business to grow, new employees have to be onboarded. Recent studies have shown that nearly one-third of new hires quit their job within the first 6 months. Retaining long-term and effective employees is essential for every […] ## How To Create The Best Onboarding Experience How can your organization create the best onboarding experience possible to accommodate new hires? In order for any business to grow, new employees have to be onboarded. Nearly one-third of new hires quit their job within the first 6 months — and replacing a frontline employee costs between $4,400 and $15,000, making early onboarding investment a direct retention ROI lever, not just a culture nicety. Retaining long-term and effective employees is essential for every business. But how do you help employees feel welcomed, engaged, and appreciated? It starts with empowering employees from day one. In a survey, 53% of HR professionals reported an increase in positive employee engagement when onboarding activity is improved. ## Here are 5 ways to improve your employee's onboarding experience: ### #1: Onboarding Into An Inviting Culture Starting a new job is always a bit of an intimidating experience. You're suddenly introduced to a new environment, a new culture, and a new set of guidelines. Establishing a welcoming and accepting culture beforehand will make this transition much smoother. Take a look at your team or work environment and consider what you can do to create a more inviting culture. Team welcome activities with new employees are a great place to start. When a new member joins the team, try organizing an informal gathering where everyone can get to know each other away from the typical work environment. When done correctly, team introduction activities can help establish work culture standards for employees. Personalization matters here too. Competitors now emphasize onboarding content feeds targeted by role and location from day one — a practice that moves new hires from generic orientation to relevant, contextualized information immediately. An employee directory that auto-populates new hire profiles on arrival gives teams an immediate, structured way to connect across departments and locations. ### #2: Keep An Open Door Policy A newly onboarded employee has a lot to learn in a relatively short period of time. From incorporating unique business practices to learning product information, retaining all of the information can prove challenging. It's completely natural for new employees to need reminders and make mistakes as they start out. This transitional period is the perfect opportunity to demonstrate an encouraging and supportive environment. By promoting a judgment-free open door policy, new employees can comfortably ask questions and refresh their knowledge on important information. Such policies should allow employees to confidently grow in their new position by openly seeking guidance and direction. Open door policies can also improve the overall level of transparency within a company. This leads to both new and established employees feeling motivated, trusted, and valued. Note that employees lose over 4 hours weekly switching between disconnected systems — a friction point that begins at onboarding when tool access is fragmented. Reducing that friction from day one reinforces the open, accessible culture you're trying to build. ### #3: Take Advantage Of Technology Many companies primarily use technology during onboarding as a tool for conducting presentations, but it has so much more to offer. Some of the best organizations successfully supply their workforce with employee-friendly technology. Tools like MangoApps help companies set up social media-inspired intranet platforms to foster learning experiences and nurture collaboration. New hires receive access to interactive communities from day one, making it easy to discover more about their roles and responsibilities, make friends with similar interests, and much more. In some organizations, technology allows the onboarding journey to begin well before the employee enters the office. Companies can use such platforms to introduce new employees to their teams, provide learning materials, and more. However, technology only works if employees can actually access it. Per Emergence Capital, 80% of the global workforce is deskless — and employees who lack access to a mobile onboarding app, especially frontline workers without corporate email, are effectively excluded from digital onboarding workflows from the start. A purpose-built employee app enables onboarding on personal devices without requiring corporate email or VPN, directly addressing the access gap that traditional onboarding portals create for hourly and field workers. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in — and per SWOOP Analytics, the average daily time spent using intranet tools is just six minutes. That low engagement often traces back to a poor onboarding experience with the platform itself. Onboarding platforms that integrate with HRIS systems can auto-sync new hire roles, permissions, and profiles on day one, eliminating manual IT provisioning delays and giving employees a reason to log in immediately. Structured learning workflows embedded in onboarding also close a critical gap. Connecting new hires to ongoing learning paths — through an integrated LMS learning system — means onboarding doesn't end after week one. Per IDC, employees spend 2.5 hours per day searching for information; embedding training and employee engagement resources directly into the onboarding flow reduces that search burden from the first day. OU Health achieved 87% workforce engagement within months of launching a branded employee app, demonstrating what a connected, mobile-first onboarding experience can deliver at scale. For a deeper look at how to connect onboarding to ongoing development, see Why Your Learning and Development Strategy Fails (and How to Fix It). ### #4: Appreciate Their Investment When a new customer is acquired, it is natural to assume that he or she will be interested in learning more about your organization. Onboarding a new employee is a similar process. While an employee may not directly invest money into your business as customers do, employees are willing to invest their time, talents, and energy each and every day. It's only natural to provide employees in turn with transparency in the workforce. Employees should never need to wonder about how their work is contributing to company success. Just like an organization's customers, employee investment should be appreciated right from the start. ### #5: Improve With Honest Feedback Successfully completed employee onboarding requires employers to evaluate and reflect on the process. Employers need to collect honest feedback — through structured employee engagement surveys and employee engagement questionnaires — as well as consider the onboarding process from their own experience. Continually adapting, assessing, and improving this process is the key to long-lasting employee success. What worked well for employees at one point in time isn't necessarily the best policy for every onboarding experience. Seek out genuine feedback from new hires and be willing to adapt as needed. Implementing changes based on employee experiences will not only improve future onboarding activities, but also demonstrate receptiveness to employee's thoughts and ideas. Onboarding new employees should be a collaborative team experience, not a process for HR to take on alone. Embracing employees to your work environment is a key to achieving long-lasting success. For a broader view of where workforce practices are heading, the 2026 HR Trends eBook covers how leading organizations are rethinking the full employee lifecycle. ## What Should Onboarding Technology Actually Include? If you're evaluating employee engagement software or an LMS learning system to support onboarding, look for platforms that offer: role- and location-based content personalization from day one; mobile access without corporate email or VPN for frontline and deskless workers; HRIS integration to auto-provision accounts and profiles; embedded learning paths that connect onboarding to ongoing employee engagement training; and feedback mechanisms such as employee engagement questionnaires built into the flow. Per Social Edge Consulting, only 13% of employees use their intranet daily — platforms that make onboarding the first compelling reason to log in are far more likely to sustain that habit. ## How Do You Measure Whether Onboarding Is Working? The clearest signals are early retention rates, time-to-productivity, and scores from employee engagement surveys administered at 30, 60, and 90 days. Qualitative feedback from new hire cohorts — gathered through structured employee engagement questionnaires — surfaces friction points that quantitative data misses. If your onboarding platform integrates with your HRIS, you can also track login frequency, module completion rates, and community participation as leading indicators before the 6-month retention cliff arrives. The ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report provides independent benchmarks for evaluating how well intranet and employee experience platforms support these outcomes. --- # How Customers Use The MangoApps Groups Module **Author:** April Thomas **Published:** 2019-03-28 **Category:** modules-features At MangoApps, we understand that incorporating new collaboration software is a unique experience for every business. For some of our clients, it can be difficult at first to visualize how to best incorporate our tools into their organization. We have collected a few examples from our clients about how they best utilize the MangoApps Groups […] # How Customers Use The MangoApps Groups Module At MangoApps, we understand that incorporating new collaboration software is a unique experience for every business. For some of our clients, it can be difficult at first to visualize how to best incorporate our tools into their organization. We have collected a few examples from our clients about how they best utilize the MangoApps Groups module — covering interest communities, client updates, file organization, and confidential executive collaboration. As you learn how our customers use this feature, think about how it could work for your organization. ## Create Interest Groups One of our retail clients uses the MangoApps Groups module to create public interest groups for their employees. These public interest groups are open to anyone in the organization. A few of their most popular groups include a company-wide book club and a location-based soccer team. While not work-related, these groups initiate friendships and trust throughout the organization. In addition they can help bridge the gap between coworkers, as they receive a chance to interact in a friendly and casual environment. These groups also introduce coworkers that might not otherwise meet due to differing work schedules and offices. The business case for social groups goes beyond morale. Employees with strong workplace friendships are significantly less likely to leave voluntarily, making interest groups a measurable retention tool — not just a perk. Replacing a single frontline employee costs between $4,400 and $15,000 on average, which means even modest improvements in social cohesion carry real financial weight. For retail environments in particular, where turnover is persistently high, this is a meaningful lever. See [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) for related strategies on keeping frontline teams connected. It is also worth noting that frontline and deskless employees — who make up over 80% of the global workforce — are routinely excluded from group-based collaboration tools that require corporate email or VPN access. MangoApps Groups are accessible on mobile without a corporate email address, so hourly and field workers can participate in the same interest communities as their office-based colleagues. ## Share Important Updates One of our marketing customers utilizes the module to share updates with clients without having to schedule extra meetings. When clients are able to quickly evaluate work progress and approve projects, the marketing teams can immediately respond. The MangoApps Groups module helps bridge the gap with clients between geographical distances and varying time zones. With access to group content readily available, clients can collaborate with the marketing team at their convenience. This use case addresses a broader challenge: per Gartner, 2023, 47% of workers struggle to find necessary information at least half the time. Group-based updates — organized by project or client — reduce that friction by giving everyone a single, searchable location for status posts, files, and approvals. Per the State of the Digital Workplace & Modern Intranet, 2024, only 22% of company intranets currently deliver personalized content, which means most employees are still sifting through noise to find what matters. Structured groups narrow that gap considerably. Explore how [employee communications](/solutions/employee-communications) can be organized around groups to keep every stakeholder current without additional meetings. ## Storage and Organization A local sales company uses MangoApps Groups to manage and organize important sales files and information. Each group is specifically tailored to unique sales situations, circumstances, and needs, providing users with quick and easy access to their most important resources. Having instant access to relevant resources helps the different sales teams provide their customers with the best available information as they need it. This leads to an increase in sales and improvement in customer service. Using the MangoApps Groups module also ensures that every user has access to the most current resources. Information is never lost and is immediately distributed throughout the organization with a single click. MangoApps Groups can also be paired with AI-powered search so members surface the right file or update without manual digging — a meaningful step beyond static folder-based storage. Per Banner Health, 63% of employees said their intranet content was not current and relevant, and 61% wanted intranet access outside the work VPN. Group-based file organization, combined with mobile access, directly addresses both complaints. For a deeper look at how knowledge management tools can be embedded in daily workflows, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ## Collaborate Together A healthcare company uses MangoApps Groups to internally discuss upcoming acquisitions and other sensitive business decisions. By organizing unlisted groups, executives and other business leaders are able to securely discuss critical business decisions. This makes it much easier for leaders to communicate together without having to worry about spreading rumors, breaking non-disclosure agreements, or disrupting daily work. Working confidentially is particularly important in the [healthcare](/industries/healthcare) industry where changing procedures, amended information, and new initiatives are particularly prevalent. Confidential or unlisted groups enforce role-based permissions so sensitive discussions — M&A activity, HR matters, regulatory changes — are visible only to explicitly added members, not merely hidden from search. This is a governance distinction that matters: access control at the group level means that even a platform administrator cannot accidentally surface restricted content to the wrong audience. For organizations in regulated industries, this architecture supports compliance requirements without requiring a separate secure-messaging tool. Read [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) for a real-world example of how a healthcare organization structured its internal groups for both security and usability. ## Getting Started: What to Expect When You Set Up Groups A common follow-up question after reviewing these use cases is: how difficult is it to actually configure and launch groups? The short answer is that MangoApps Groups are designed to be created and managed by department leads or HR teams without IT involvement. Administrators can designate groups as public (open to all), private (request to join), or unlisted (invite only), and each setting carries its own permission defaults. Most organizations launch their first set of groups — typically a mix of department groups and one or two interest groups — within a single onboarding session. For frontline-heavy organizations, the mobile-first setup is particularly relevant. Per Banner Health, 61% of employees wanted intranet access outside the work VPN, and MangoApps Groups are accessible via the [employee app](/solutions/employee-app) on any mobile device without requiring a corporate email address. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring their group taxonomies to balance openness with governance. ## How MangoApps Groups Compare to Slack and Microsoft Teams Organizations evaluating employee engagement software frequently ask how MangoApps Groups differ from channels in Slack or Teams. The core distinction is scope: Slack and Teams are built around real-time messaging, while MangoApps Groups are designed as persistent, structured spaces that combine discussion, file storage, task tracking, and member management in a single location. Groups do not require constant monitoring to remain useful — a file posted six months ago is as discoverable as one posted yesterday. A second distinction is workforce coverage. Slack and Teams assume every user has a corporate email and a laptop. MangoApps Groups extend to frontline and deskless workers via mobile, without requiring email provisioning. For organizations with a mixed workforce — office staff, field technicians, retail associates — this means a single group infrastructure can serve the entire employee population rather than creating a two-tier communication system. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an independent assessment of how intranet-based group tools compare across vendors on governance, usability, and frontline reach. MangoApps has also been recognized for its platform depth: see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) for context on how the platform is positioned relative to other enterprise intranet and employee experience tools. ## The Bottom Line on MangoApps Groups The four use cases above — interest communities, client update sharing, sales file organization, and confidential executive collaboration — represent a fraction of how organizations deploy the Groups module. What they share is a common outcome: employees spend less time searching for information and more time acting on it. Per Gartner, 2023, 47% of workers struggle to find necessary information at least half the time; structured groups with clear ownership and role-based access directly reduce that number. If your organization is evaluating employee engagement software or knowledge management tools and wants to see how Groups fits into a broader platform, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) is a practical starting point. For a live walkthrough tailored to your industry and workforce mix, schedule a personalized demo with the MangoApps team. --- # 5 Ways To Unleash The Power Of Small Independent Teams **Author:** Anna Carriveau **Published:** 2019-03-26 **Category:** company-culture Whether you’re a long-established global enterprise or an emerging start-up, small teams are the secret to long term success. Empowering small independent teams, helps workers handle tasks autonomously and encourages the best an employee has to offer. While small companies have long known the benefits of size-controlled teams, larger companies are starting to catch on. […] ## 5 Ways To Unleash The Power Of Small Independent Teams Whether you're a long-established global enterprise or an emerging start-up, small teams are the secret to long-term success. Empowering small independent teams helps workers handle tasks autonomously and encourages the best an employee has to offer. While small companies have long known the benefits of size-controlled teams, larger companies are starting to catch on. When used effectively, small teams are one of your most important resources for getting things done on time. But how exactly do you utilize teams effectively? **Here are our top 5 ways to unleash the power of small independent teams:** ## #1: Create Customer Awareness In order to be interested and engaged in their efforts, small independent teams need to understand how their work directly impacts the customer experience. Knowing that their role makes a real difference provides teams with a sense of purpose and pride. Understanding your role in a larger process also helps teams connect to the overall company mission. Companies can help their workers in this effort by educating employees about a project's long-term goals and development. By painting a clear picture of a project's outcome, beyond their own piece in the puzzle, teams are better able to see how their effort contributes to company success. For distributed and frontline teams — who make up roughly 80% of the global workforce, per Emergence Capital — this context is even more critical. Workers without desk access or a company email address are structurally at risk of missing the broader mission unless communication reaches them on the devices they actually use. You can use MangoApps to track the overall progress of a project, helping employees throughout the development process stay aligned — whether they're in an office, on a retail floor, or working remotely. For a real-world example of how this plays out at scale, see [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study). ## #2: Encourage Honest Transparency Employers are often hesitant to disclose complete and detailed company information to their teams. This stems from the fear that employees cannot be trusted with sensitive information. While this may seem pragmatic at a glance, it is not an effective way to empower small independent teams. Team members devote countless hours to the work they do and are expected to provide their leaders with all kinds of information. When that courtesy is not returned, leaders often appear suspicious, dishonest, or condescending. No one likes to hear about layoffs five minutes before they happen. Being transparent with your teams creates a mutual sense of honesty and dramatically improves employee trust, engagement, and dedication. This matters especially for [employee engagement](/solutions/employee-engagement) across geographically distributed teams, where information gaps widen quickly. Small teams operating without a unified communication platform routinely navigate 6–8 disconnected tools daily, fragmenting collaboration and slowing decision-making — a fragmentation challenge MangoApps is specifically designed to address. Employees already spend an average of 2.5 hours per day searching for information, per IDC; adding tool fragmentation on top of that compounds the problem significantly. For a deeper look at how transparency and communication strategy intersect, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers current benchmarks and practical approaches. ## #3: Promote Effective Independence While freedom can seem daunting, it's a natural next step. Small independent teams need their leader's trust to make important decisions and work independently. After all, how can you have small independent teams when you take away all of their independence? Successful leaders allow teams to make important decisions, trusting that they have the knowledge they need to make the right call. Providing freedom for your teams doesn't mean there aren't any guidelines, or that you never check on team activity. Rather, it means taking a step back, trusting that you've hired good employees, and putting together a team that works well together. Increasingly, AI-assisted coordination — automated scheduling, task assignments, and approvals through no-code workflows — is how organizations operationalize this trust at scale. Automating routine team coordination tasks through workflow automation measurably reduces manager overhead and accelerates team independence, according to operational benchmarks cited by Beekeeper. Frontline and distributed team members who lack mobile access to team tools, updates, and HR self-service are structurally excluded from the autonomy that makes small teams effective — a gap that mobile-first employee experience platforms address natively, per MangoApps product documentation. Increasing team freedom is a welcome change for everyone, providing managers with extra time and giving teams the chance to express their independence and exceed expectations. To understand how learning and development reinforces this kind of autonomy, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ## #4: Offer A Better Work-Life Balance Team members can only bring out their best performance when their own personal needs have been met. And while managing a successful home and private life ultimately comes down to the employee, this effort can be greatly enhanced by an effective work-life balance. Providing a flexible work-life balance is an organic part of enabling team independence. When teams have the freedom to determine how and when they work together, they feel more empowered and committed to their tasks, while still being able to take care of personal commitments. The needs of every team are different, but with a few basic company guidelines and a dependable team, they'll be able to work out the best balance themselves. For distributed and shift-based teams, this flexibility depends entirely on tools that work on personal devices without requiring VPN access or a company email — true mobile-first access rather than a desktop-first afterthought. For scheduling-specific guidance in distributed environments, [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) offers a practical framework that applies well beyond retail. ## #5: Foster Constant Collaboration No matter how small your team might be, they need access to effective collaboration tools. This is especially important if teams are geographically separated or work away from the office often. Collaboration technology, like MangoApps, allows team members to communicate and work together anywhere with an internet signal. Collaboration tools are also a significant help when teams need to work together to accomplish a specific goal. Effective tools allow for video calls, file sharing, discussion platforms, and more. Collaboration tools help employees with every aspect of becoming a successful team, including understanding the importance of a project, increasing team independence, and creating a better work/life balance. They're also a great way for teams to access company-wide or department-wide resources. The adoption gap between traditional intranets and mobile-first employee experience platforms is stark: only 13% of employees use a traditional intranet daily, and nearly a third never log in at all, per Social Edge Consulting. By contrast, organizations that deploy a branded, mobile-first app see 90%+ average adoption rates. Increasing team collaboration through the right platform can create a much more productive work environment — and the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines how leading organizations are making that shift today. ## Putting It All Together Organizations can't survive without dedicated, creative, and insightful employees. Small teams, when well constructed and given the power to work independently, are how to make that happen. These teams can innovate and explore new ideas while successfully completing projects on time. The five methods above — customer awareness, honest transparency, effective independence, work-life balance, and constant collaboration — are mutually reinforcing. None of them works in isolation, and all of them depend on employees having reliable, mobile-accessible tools that meet them where they work. Organizations that digitize training and task workflows see 50% faster new-hire onboarding, making the infrastructure investment directly measurable. Contact us to learn more about empowering small independent teams, or how MangoApps helps teams achieve their best every day. ## How Do You Measure Whether Small Teams Are Actually Working? Empowering small teams is only half the equation — knowing whether it's working is the other half. The most reliable indicators include task completion rates against deadlines, employee engagement survey scores (tracked consistently over time, not just annually), and qualitative signals from employee engagement questionnaires that surface how autonomous team members actually feel. Platforms that combine teamwork management dashboards with employee engagement software give managers a single view of both output and sentiment, rather than requiring separate tools for each. For a broader view of how HR leaders are approaching measurement in 2026, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the metrics frameworks gaining the most traction. ## How Do You Handle Resistance When Teams Push Back on Autonomy? Not every team embraces independence immediately. Some employees — particularly those accustomed to highly directive management — experience autonomy as ambiguity rather than freedom. The most effective approach is graduated: start with bounded independence (clear goals, flexible methods) before moving to full self-direction. Training and employee engagement programs that explicitly build decision-making confidence are more effective than simply removing oversight. Pairing autonomy with transparent performance feedback — so teams can self-correct rather than waiting for a manager to intervene — closes the loop. For organizations navigating this in complex workforce environments, [Managing a Unionized Workforce Is Different. Your Software Should Be Too](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) addresses how structured autonomy works within formal labor frameworks. ## What Does Remote and Distributed Team Engagement Look Like in Practice? The five tips above apply to co-located and distributed teams alike, but distributed teams face an additional layer of complexity: the informal trust-building that happens naturally in shared physical spaces has to be deliberately engineered. Remote employee engagement requires intentional communication cadences, asynchronous collaboration norms, and — critically — tools that don't assume everyone has a desk, a company laptop, or a corporate email address. Per Emergence Capital, 80% of the global workforce is deskless, meaning the majority of small teams worldwide are already operating in distributed or mobile contexts. Employee engagement training that accounts for this reality, rather than defaulting to office-centric models, is what separates organizations that scale small-team autonomy from those that don't. --- # MangoApps’ TinyTake for Teams **Author:** April Thomas **Published:** 2019-03-21 **Category:** news-and-updates TinyTake centers around seamlessly incorporating visual communication into the workplace, helping employees communicate faster and more effectively. It includes, of course, our most up-to-date version of TinyTake, as well as a few more highly engaging and visually based modules and features. Let’s take a quick look at everything you need to know about TinyTake for […] # TinyTake for Teams: How MangoApps Closes the Visual Communication Gap Text has a fundamental weakness as a workplace communication medium: it strips context. When a frontline supervisor writes out a step-by-step procedure, the person reading it has to reconstruct the mental model the supervisor already has. When a support analyst describes a software issue in a ticket, the recipient has to imagine what the screen actually looked like. When a trainer explains a process in an email, the trainee has to translate words into actions without seeing those actions performed. This is not a writing quality problem. It is a medium problem. Per Gartner's 2023 Digital Worker Survey, 47% of workers struggle to find the information they need at least half the time. Text-heavy communication doesn't cause that number — but it makes it significantly harder to fix. TinyTake for Teams is MangoApps' response: a suite of screen capture, video recording, screen sharing, and people-directory tools built to close the gap between what employees know and what they can communicate. This article covers how each capability works, who benefits, and what outcomes organizations can realistically expect when visual communication is built into the platform rather than bolted on. ## Why the medium matters more than the message Most enterprise platforms treat communication as a text problem. Documents, messages, forms — these are the primary vessels for workplace knowledge. Visual content gets treated as supplementary: a screenshot pasted into a chat, a screen recording uploaded to a separate platform, a training video hosted somewhere outside the intranet. The result is fragmentation. Visual content gets created, shared in its immediate context, and then lost. No tagging, no search, no way to find the recording from last quarter's onboarding session. A new hire asks the same question that an experienced employee already answered on video two months ago — and no one knows the video exists. TinyTake for Teams is built differently. The four tools it bundles — screen capture, video, screen sharing, and a people directory — feed into a single searchable media library. Visual content stops being ephemeral and becomes institutional knowledge. That architectural choice is what separates a visual communication tool from a visual communication system. ## Screen capture and annotation: making the implicit explicit The screen capture module allows employees to capture anything on their screen, then annotate it with text boxes, arrows, magnification callouts, and markup tools before sharing. For operations teams building SOP documentation, operations manuals, and step-by-step instructions, this is the entry point. Written procedure documentation has a chronic readability problem. Steps that are obvious to the author — because the author can see the interface in their head — are frequently ambiguous to the reader. Annotated screenshots solve this by showing the exact state of the system at each step, with arrows pointing to the specific button or field the reader needs to find. The result is documentation that requires less interpretation, generates fewer clarifying questions, and produces fewer procedural errors. For organizations with large frontline workforces or high turnover, this matters especially. The time a senior employee spends re-explaining a process to a new hire is time that well-tagged annotated documentation could have pre-empted. Every screenshot stored in the media library answers a question before it gets asked. ## Video recording: converting individual expertise into reusable knowledge The video recording module captures at up to 60 frames per second with audio, supports multi-monitor setups, and includes a countdown display and screen magnification. Employees can produce training videos, product demonstrations, and operations instructions without specialized software or production skills. The strategic value here is often underestimated. Institutional knowledge — the understanding of why things work a certain way, the workarounds for known system quirks, the judgment calls that experienced employees make automatically — is typically locked in people's heads. It surfaces when someone asks a question and the right person is available to answer. When that person is unavailable, or leaves the organization, the knowledge goes with them. Video recording changes this. When an experienced employee records a walkthrough of a complex process, that recording can be saved, tagged, and made searchable. The next person with the same question finds the answer in minutes rather than waiting for the original expert to be free. Per McKinsey research, 89% of frontline workers say they will stay with their companies if leaders listen to their feedback — staying means the institutional knowledge they've accumulated stays too. Video ensures that knowledge transfers even when they eventually don't. ## Screen sharing: zero-install collaboration for every device type The screen sharing module allows employees to share their entire desktop or a selected region with anyone inside or outside the organization. Participants join via a secure link — no software installation required. Sessions support audio, work across device types, and can be recorded, saved, and labeled for future reference. The zero-install access point is the capability that matters most for organizations with deskless or frontline employees. A store manager, field technician, or clinical worker who needs to walk a colleague through a system configuration doesn't need to ask them to install software. They send a link. The colleague clicks it and sees the screen. Common deployment patterns include: - **Customer support**: walking a client through a process in real time rather than writing a multi-step email - **Vendor collaboration**: reviewing system configurations together without sharing credentials - **Internal training**: running employee communications training sessions that participants who can't attend live can watch as recordings afterward Per the *State of the Digital Workplace & Modern Intranet, 2024*, only 22% of company intranets currently deliver personalized content. Screen sharing and recorded sessions can be targeted by department or role — a district manager's walkthrough of a new compliance requirement reaches the team leads who need it, not the entire organization. ## People directory: connecting names to the knowledge behind them TinyTake for Teams includes a searchable employee directory with profile images, reporting relationships, email, phone number, and both professional and personal details. Contact information is interactive — clicking a phone number or email initiates the action directly. This capability supports the visual communication tools in a practical way: knowing who recorded a video or ran a screen share session makes the content more credible and easier to follow up on. When an employee watches a training recording and has a follow-up question, they can look up the presenter immediately rather than asking their manager who to contact. Organizational clarity at scale is harder than it looks. In organizations with hundreds or thousands of employees, the friction of reaching out to someone you haven't met in person is real. The directory closes that friction, which matters most for the teams using TinyTake most: operations teams documenting processes, communications teams distributing training content, and support teams collaborating across locations. ## The media library: why visual content stays findable Every file created or shared within TinyTake — screenshots, recordings, session archives — is automatically stored in a searchable media library where items can be tagged, named, and retrieved. This is the architectural choice that distinguishes TinyTake from a collection of standalone visual tools. Without a media library, visual communication is ephemeral. A screen share session gets recorded and the file sits in someone's downloads folder. A training video gets uploaded to a drive folder that no one bookmarks. The Gartner statistic — 47% of workers struggling to find information they need — applies as much to internally created visual content as it does to documents. The tagging and search layer makes institutional knowledge discoverable. Recorded how-to videos can be auto-tagged, making them retrievable by topic rather than by remembering who created them. For organizations evaluating visual communication tools as part of a broader [employee communications platform](/solutions/employee-communications) strategy, the media library is the capability that determines whether content accumulates value over time or resets with every new hire. ## Frontline accessibility and what it changes For organizations with large frontline workforces, the relevant question isn't whether visual communication tools work — it's whether they work for employees who don't have managed desktops. TinyTake's screen sharing module handles this via secure link architecture: participants join without an account or software installation. The [MangoApps employee app](/solutions/employee-app) extends this further, providing mobile-first access to the broader platform — including the media library, directory, and video recordings — from a personal device without corporate credentials. The deployment pattern in the market is consistent. Visual and mobile-first communications platforms report rapid frontline adoption when the access barrier — mandatory software installation, corporate device requirements — is removed. Organizations that achieve high frontline engagement do so by meeting employees on the devices they already carry. For teams evaluating how visual communication tools fit into a broader internal communications investment, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers current benchmarks on frontline adoption and deployment patterns across industries. The [MangoApps Forrester Wave evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides independent analyst context on where the platform positions against alternatives in the employee experience space. ## What outcomes organizations can expect Outcomes from deploying visual communication tools follow a predictable pattern across deployment types. Support volume decreases. When employees can show rather than describe an issue — via screenshot, recording, or screen share — the back-and-forth required to diagnose the problem drops. Clarifying questions decrease because visual context eliminates the ambiguity that text descriptions leave open. Documentation quality improves without requiring more effort. Annotated screenshots and short how-to recordings produce clearer operations manuals than written procedures alone, and they take less time to create than comprehensive text documentation. Per McKinsey research, 81% of leading companies effectively use data and analytics tools — visual documentation works on the same principle: teams that capture what they know produce usable institutional assets with lower effort than text-only alternatives. Onboarding time shortens. New employees can find existing recordings for common processes rather than waiting for a colleague to be available. The media library converts experienced employees' expertise into self-service training assets that don't expire when the expert is out of office. For teams setting targets before rollout, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) includes current benchmarks on communication efficiency and operational documentation practices across comparable deployments. ## Closing the show-vs-describe gap The 47% of workers who struggle to find information they need aren't struggling because the information doesn't exist. They're struggling because it exists in a form that doesn't survive transfer — a verbal explanation, a text description of something visual, a mental model that never got documented. TinyTake for Teams addresses this at the medium level. Screen capture turns the implicit into the explicit. Video recording converts individual expertise into reusable institutional knowledge. Screen sharing removes the access barriers that keep visual collaboration platform-dependent. And the people directory ensures that the humans behind the content are findable when a follow-up question arises. For organizations evaluating whether to consolidate visual communication tools into their MangoApps deployment, the practical case comes down to one principle: content that lives in the same platform employees use for daily communications gets found. Content that lives elsewhere doesn't. --- # Building A Company Culture Of Continuous Learning **Author:** Anna Carriveau **Published:** 2019-03-19 **Category:** company-culture Building a company culture of continuous learning is paramount for industry growth and long-term success. Learning new skills can help employees engage with their work, and feel connected to their company. Continuous learning fosters advanced thinking, adapting, and innovation. By creating an atmosphere of learning and growth, employers are helping their workers stay on top […] ## Building A Company Culture Of Continuous Learning Building a company culture of continuous learning is essential for industry growth and long-term success. Learning new skills helps employees deepen their [employee engagement](/solutions/employee-engagement), feel connected to their company, and advance their careers within your organization. Continuous learning fosters advanced thinking, adaptability, and innovation. By creating an atmosphere of learning and growth, employers help their workers stay on top of important trends, compete on both a local and global scale, and develop the skills that matter most. **Below, we address a few ways to help foster learning and development throughout your organization:** ## Identify Your Work Culture The first step toward building a culture of continuous learning is understanding the culture your organization currently has. Business culture is composed of company goals, employee habits, and the general perceptions around the office. This can include both positive and negative elements. Successfully identifying your current work culture will make it easier to address negative features and see areas where you might be falling short. It will also help you establish the kind of learning environment best suited for your organization. Some businesses work in a formal or traditional style, while others implement a more casual and modern approach. Neither take is necessarily wrong, but both require different learning styles and curriculum. One often-overlooked dimension of culture identification is access equity. Per Emergence Capital, 80% of the global workforce is deskless—meaning frontline employees in retail, healthcare, manufacturing, and logistics are frequently excluded from learning programs designed for desk-based workers. Any honest culture audit must ask: are our learning initiatives actually reaching everyone, or only those with a company email and a laptop? ## Choose The Best Curriculum Once you've identified your current culture and outlined any necessary changes, it's time to put together a plan. This plan could include tackling misconceptions, reemphasizing company goals or missions, or whatever other negative attitude may be interfering with building a culture of continuous learning. It also includes creating a learning curriculum designed to match your company's style and needs. For some companies, that may mean implementing a library where employees can casually browse and discover for themselves. For others, it might mean implementing an outlined course guide, taking employees step by step through learning outcomes and objectives. When selecting employee engagement courses and training formats, consider how the curriculum will be delivered. Organizations that embed learning into a unified platform—combining an [LMS learning system](/solutions/learning-management), communications, and HR tools—see faster adoption than those running learning as a standalone initiative, because employees don't have to switch between six to eight disconnected tools daily to complete training. AI-curated learning paths take this further by surfacing the right content for each employee automatically, making personalized curriculum selection scalable rather than a manual, one-size-fits-all decision. You can explore how [skills management](/key-features/skills-management) capabilities support this kind of targeted curriculum design. ## Create The Right Environment Learning can only last in the right environment. How will you implement your plan? What will your learning environment look like? And most importantly, how will you transition your employees from their current experiences into a culture of continuous learning? A large part of an effective learning environment is providing a place for collaboration, discussion, and experimentation. For many companies, this might involve helping employees discuss their ideas on company communication platforms, or providing time for employees to practice their new skills. However you decide to proceed, be sure to establish an open, inviting, and trusting environment where employees can communicate and share their insights. The physical and digital environment must also account for where employees actually work. Frontline workers are disproportionately excluded from continuous learning programs because most LMS platforms require a company email, a desk, or VPN access to participate. Mobile-accessible onboarding and training programs can cut new-hire ramp time significantly—at least one frontline platform has reported 50% faster onboarding through digitized, mobile-first learning workflows (per Beekeeper product data). Designing your environment with mobile access as a baseline, not an afterthought, is what separates inclusive learning cultures from ones that inadvertently leave the majority of the workforce behind. ## Encourage Active Participation Most importantly, encourage everyone to participate. Make sure employees at every level—including frontline and deskless workers—can access and utilize your learning initiatives. A culture of learning means involving everyone in the process. Employees may need some incentive to get started, but over time, a natural interest and enjoyment will often emerge. A large part of encouragement also includes setting aside time or allowing employees time to complete learning objectives or take part in learning activities. Most employees who do not participate in company-provided employee engagement training simply lack the time. Ensuring employees can learn effectively—through [training and employee engagement tools](/key-features/training-connect) that fit into their existing workflow—is essential to a culture of continuous learning. When platform design prioritizes participation, the results are measurable: one large pharmacy and retail deployment achieved 90% frontline adoption within the first six months, and another organization reached 87% workforce engagement within a few months of launching a branded mobile learning and communications app. ## MangoApps When done the right way, continuous learning can help transform employees into a more productive, engaged, and successful workforce. MangoApps is here to help. We believe in providing companies with the tools they need to empower employees and create a lasting culture of learning and growth. To see how other organizations have approached this, review [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study) for a real-world example of a unified learning and communications platform in action. Contact us today or schedule a personalized demo to learn more about how MangoApps can help your organization foster an environment of employee progress and growth. --- ## How Do You Measure the Impact of a Continuous Learning Culture? Measuring the return on employee engagement training is one of the most common follow-up questions organizations face after launching a learning initiative. Useful metrics fall into three categories: - **Participation rates:** What percentage of employees complete assigned learning modules? Segment this by role, department, and location to surface access gaps—especially for frontline workers. - **Knowledge retention and application:** Pre- and post-assessments, manager observations, and performance data tied to [performance management](/solutions/performance-management) cycles can indicate whether learning is translating into on-the-job behavior change. - **Business outcomes:** Track indicators like error rates, customer satisfaction scores, time-to-productivity for new hires, and voluntary turnover. Per IDC, employees spend an average of 2.5 hours per day searching for information—a figure that drops when knowledge management tools and structured learning are integrated into daily workflows. Employee engagement surveys and employee engagement questionnaires administered before and after a learning initiative provide a baseline and a benchmark. Without measurement, culture change remains anecdotal. ## How Long Does Culture Change Take, and What Are the Common Pitfalls? Culture change timelines vary, but most organizational development research suggests meaningful shifts in behavior and norms take 12 to 24 months of consistent reinforcement. The most common pitfalls that slow or reverse progress include: - **Treating learning as an event, not a system.** One-time training sessions rarely produce lasting change. Embedding learning into daily workflows—through an integrated employee experience platform rather than a standalone LMS—dramatically improves retention and habit formation. For a deeper look at why standalone initiatives underperform, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). - **Ignoring the frontline access problem.** Per Emergence Capital, 80% of the global workforce is deskless. If your employee engagement software requires a desktop login or a corporate email, you are structurally excluding the majority of your workforce from day one. - **Failing to secure manager buy-in.** Managers who do not model learning behavior or who do not protect time for their teams to complete training are the single largest predictor of low participation rates. - **Measuring inputs instead of outcomes.** Tracking the number of courses published is not the same as tracking whether employees can apply what they learned. Tie learning metrics to business outcomes from the start. For a broader view of how workforce trends are shaping learning and development priorities in the year ahead, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the key shifts HR leaders are navigating right now. ## What Budget and Technology Do You Need to Get Started? Budget requirements depend heavily on the size of your organization, the complexity of your curriculum, and whether you are building on existing infrastructure or starting from scratch. A few practical considerations: - **Audit your current tool stack first.** Per SWOOP Analytics, the average employee spends only six minutes per day using intranet tools, and per Social Edge Consulting, nearly a third of employees never log in to the intranet at all. If your existing platforms are not being used, adding another standalone learning tool will compound the problem rather than solve it. - **Prioritize integration over addition.** Employee engagement software that combines LMS, communications, and knowledge management tools in a single interface reduces the switching cost that kills participation. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines how integrated platforms are reshaping how organizations approach operational learning at scale. - **Plan for mobile from the start.** Mobile-first access is not a premium feature—it is a baseline requirement for any organization with frontline or distributed workers. Budget for a platform that does not require a desk, a VPN, or a corporate email to access training content. Workplace learning is now one of the most actively researched categories in the employee experience market, with at least nine competitors publishing on the topic—signaling that buyers are evaluating solutions carefully before purchasing (per Mango IQ gap escalation signal). Starting with a clear measurement framework, an integrated platform, and a mobile-first access model gives your organization the strongest foundation for a continuous learning culture that actually sticks. --- # Boost Your Team’s Happiness With Transparency In The Workplace **Author:** Anna Carriveau **Published:** 2019-03-14 **Category:** employee-engagement Providing customers with clear communication and straightforward services is a priority of every organization. So when it comes to our employees, shouldn’t this be the same? Engaging and informing employees about business decisions, potential changes, and upcoming events can foster greater trust, commitment, and dedication. Even when it is bad news, employees will still appreciate […] ## Boost Your Team's Happiness With Transparency In The Workplace Engaging and informing employees about business decisions, potential changes, and upcoming events fosters greater trust, commitment, and dedication. Even when the news is difficult, employees appreciate and respect open transparency. In this article, we outline five ways organizations can improve employee engagement and internal communication through transparency in the workplace — and what to do when those efforts stall. ### 5 Ways To Improve Team Happiness With Transparency: #### #1: Establish Honest Communication Open communication is one of the most influential factors in determining employee happiness and motivation. Employees are expected to provide honest and reliable information. When employers hesitate to do the same, it can contribute to feelings of distrust, resentment, and hesitation. One way to provide quick and honest communication is through an effective internal communication system. Many collaboration programs mirror the successful elements of popular social media networks, incorporating them into the corporate setting. These networks make spreading reliable information fast and easy. The infrastructure behind honest communication matters more than most organizations acknowledge. Per IDC, employees spend an average of 2.5 hours per day searching for information — time that compounds into a measurable drag on productivity and trust. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use intranet tools daily. Per SWOOP Analytics, the average daily time spent using intranet tools is just six minutes. Traditional top-down intranet deployments that take months of IT-led customization tend to produce static, ungoverned content that becomes stale — directly undermining the honest communication culture this article advocates. With a unified internal communication system, your organization can decrease rumors, eliminate miscommunication, and increase transparency in the workplace. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) explores how leading organizations are closing this gap. #### #2: Evaluate Organizational Hierarchy Flat organizational hierarchies tend to facilitate much better communication than traditional top-down decision making. While organizations will always need structure and leadership, flat organizational hierarchies focus on engaging with employees at every level, giving them the chance to add input, ideas, and contributions to the organization. This structure empowers employees and helps them know that they are an important part of the overall organization. Flat hierarchies also improve transparency in the workplace by helping employees throughout the company stay up to date on changes, news, and important details from other departments. For organizations managing complex or distributed teams — including unionized workforces — hierarchy evaluation requires additional nuance. [Managing a Unionized Workforce Is Different. Your Software Should Be Too.](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) outlines how communication structures must adapt to workforce composition, not just org-chart preference. #### #3: Provide The Right Tools Whether you're an office worker or a firefighter, it's difficult to perform your job well without the right equipment. Providing employees with the tools they need to perform their job well shows that you value their work and are committed to their success. But that doesn't mean employees have to have the newest version of every tool. Part of transparency is being honest with employees about company resources, abilities, and limitations. When employees feel you have their best interest at heart, they are much more understanding of company finances and budget limitations. Tool selection carries a dimension that desk-centric organizations frequently overlook: per Emergence Capital, 80% of the global workforce is deskless. Employees who lack access to a unified, mobile-first communication channel are effectively excluded from transparency initiatives — they cannot receive push notifications, policy updates, or recognition without a corporate email or a desk. Replacing a disconnected or disengaged frontline employee costs between $4,400 and $15,000, making the right tooling a measurable retention investment, not just a culture initiative. [The Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026 and beyond](/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) provides a framework for evaluating whether your current stack actually reaches every employee. #### #4: Encourage Authentic Recognition Transparency in the workplace can only be achieved through authentic and genuine recognition. Real recognition helps employees feel valued and encourages them to improve their efforts. For recognition to be honest and transparent, it needs to be specific, thoughtful, unbiased, and inclusive. Employees should know why a person is being recognized, support and encourage their recognized peer, and know that they have an equal opportunity for receiving their own recognition. If employees receive some kind of reward, prize, or incentive for their work, it should be tailored to match the interests of the individual or team as much as possible. When employees know that you understand them on a personal level, transparency and trust is increased all around. Recognition also carries measurable business outcomes. Transparent recognition programs that are role- and location-targeted — not one-size-fits-all — drive measurably higher frontline adoption than generic all-hands announcements, as demonstrated in the PetSmart and OU Health case studies. OU Health achieved 87% workforce engagement within a few months of launching a branded employee app. Connecting recognition to employee engagement strategies rather than treating it as a standalone culture initiative is what separates programs that sustain over time from those that fade. See [From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program) for a concrete example of recognition tied to engagement outcomes. #### #5: Demonstrate Transparency Did you know that Facebook shares important company information with its staff every Friday afternoon via a Q&A session hosted by its CEO? From interns to Vice Presidents, everyone in the 15,000 plus global workforce has access to the sessions. These meetings help everyone within the organization feel trusted, respected and understood. While a broad-reaching Q&A might not be the right fit for your organization, happiness with transparency depends on organizations providing employees at every level with the chance to voice their concerns, ask their questions, and know that their input is valued. British Airways achieved a 30-point engagement score increase after deploying a unified employee experience platform — evidence that demonstrated transparency, when backed by the right infrastructure, produces outcomes that show up in employee engagement survey results, not just in culture surveys. Explore how [employee engagement strategies](/solutions/employee-engagement) translate demonstrated transparency into measurable outcomes. ### MangoApps Being transparent in the workplace is essential for long-lasting business growth, development, and success. When employees feel respected by their supervisors and organization as a whole, work becomes much more than just a job. It becomes an opportunity to contribute and make a difference. At MangoApps, we know that organizations are the most successful when every voice is heard. That's why we set out to provide organizations with a solution that encompasses everything they need to communicate with employees, discover opinions, and offer genuine praise — including the frontline and deskless workers who make up the majority of many workforces. To learn more about how MangoApps can assist your organization, contact us or schedule a personalized demo today. --- ### How Do You Measure Whether Transparency Is Actually Working? Transparency is not self-reporting. Organizations that want to know whether their five-tactic approach is landing should look at a combination of leading and lagging indicators: - **Employee engagement survey scores** — run a baseline employee engagement questionnaire before launching transparency initiatives, then re-measure at 90 days and six months. Engagement scores are the most direct proxy for whether employees feel informed and respected. - **Intranet and communication tool adoption rates** — per Social Edge Consulting, only 13% of employees use intranet tools daily. If your post-launch number is not materially higher, the channel is not reaching people, regardless of content quality. - **Recognition program participation** — track both the number of recognitions given and the distribution across teams, levels, and locations. Uneven distribution signals that the program is not yet inclusive or transparent. - **Voluntary turnover in frontline roles** — since replacing a disengaged frontline employee costs between $4,400 and $15,000, a reduction in voluntary turnover is a direct financial signal that transparency and recognition investments are working. - **Information search time** — per IDC, employees spend 2.5 hours per day searching for information. Reducing that figure through better communication infrastructure is a measurable productivity outcome tied directly to transparency. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines how HR teams are building measurement frameworks around employee experience and engagement in 2026. ### What Are the Most Common Pitfalls When Building a Transparent Culture? Organizations that commit to transparency in the workplace frequently encounter the same obstacles: 1. **Treating transparency as a one-time announcement, not an ongoing practice.** A single all-hands meeting or CEO video does not create a transparent culture. Consistency — weekly updates, open Q&A cadences, visible recognition — is what builds trust over time. 2. **Excluding deskless and frontline workers by default.** Per Emergence Capital, 80% of the global workforce is deskless. If your transparency tools require a corporate email address or a desktop login, the majority of your workforce is structurally excluded before the initiative begins. 3. **Conflating tool deployment with culture change.** Deploying an intranet does not automatically produce transparency. Per SWOOP Analytics, the average employee spends just six minutes per day on intranet tools. The platform must be designed around how employees actually work — mobile-first, push-notification-driven, and integrated into daily workflows — not how IT prefers to govern content. 4. **Recognition programs that are generic rather than targeted.** One-size-fits-all recognition announcements are perceived as performative rather than genuine. Role- and location-specific recognition, as demonstrated in the OU Health case study, drives meaningfully higher adoption and trust. 5. **No feedback loop from employees to leadership.** Transparency is bidirectional. Organizations that broadcast information without creating structured channels for employees to respond — through employee engagement surveys, pulse checks, or open forums — are practicing communication, not transparency. For industry-specific considerations, [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) illustrates how transparency around scheduling and operations plays out in a high-turnover, deskless-heavy environment like [retail](/industries/retail). --- # How Customers Use MangoApps Dashboards **Author:** April Thomas **Published:** 2019-03-05 **Category:** modules-features At MangoApps, we believe in providing users with personalized communication tools. We offer our customers exactly what they need, without requiring extra or unnecessary features. Sometimes this can come as a real surprise to companies, and personalizing your individual experience can actually be a bit of a transition. To help our customers bridge the gap […] ## How Customers Use MangoApps Dashboards MangoApps Dashboards give employees a single, personalized intranet portal where they can access updates, complete tasks, and communicate — without switching between disconnected apps. Per IDC, employees spend 2.5 hours per day searching for information across fragmented systems; a unified dashboard directly addresses that cost. The four use cases below show exactly how real customers — in healthcare, sales, marketing, and tech — put dashboards to work today. For context on how widespread the problem is: per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use intranet tools daily. Per SWOOP Analytics, the average daily time spent using intranet tools is just six minutes. Dashboards that surface role-specific, relevant content are one of the clearest ways to close that gap. ## Access Updated Info One of our [healthcare](/industries/healthcare) customers relies on MangoApps Dashboards to establish check-ins for health officials and employees. Dashboards help health professionals prepare for the day by providing up-to-date information about patient conditions, concerns, and care notes. Employees also use the check-out process to provide detailed descriptions of what happened during the day. This ensures that the next person on shift will have all of the data and information they need. As employees regularly report details, a descriptive patient log is created, where authorized individuals can see patient history and progress over time. Check-ins also help employees know when a health professional has arrived, keeping everyone well-informed. Healthcare intranets and dashboards that surface role-specific, real-time information are a recognized best practice for shift-based clinical teams, yet most legacy intranet tools require IT customization to achieve this. MangoApps makes that configuration available to administrators without engineering support. For a deeper look at how a peer organization approached this, see [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology). ## Prepare For The Day A sales client uses MangoApps Dashboards to consolidate their employees' morning routine into one easy-to-use area. Employees check messages, view accounts, file reports, and perform other routine duties generally at the start of every day. By keeping their content organized in a single area, employees can track their daily tasks and complete activities faster. Employees are able to customize their individual dashboards, helping them stay productive and on task. As employees begin their day with their MangoApps Dashboards, they can also see and comment on the recognitions, achievements, and greetings regularly shared by company supervisors, helping everyone celebrate and support internal success. Personalized dashboards can consolidate access to 200+ enterprise systems — including HRIS, LMS, and communication tools — into a single pane of glass, eliminating the need to switch between apps. Employees lose over four hours per week switching between disconnected systems; a unified dashboard directly addresses this tool-sprawl cost. For teams evaluating how [employee communications](/solutions/employee-communications) fit into this picture, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the shift toward consolidated, role-based communication channels. ## Stay On Top Of Trends A creative marketing boutique uses MangoApps Dashboards to stay up-to-date with the latest industry news. With clients spread across multiple countries and covering a variety of interests and industries, it can be difficult to stay on top of legal changes, competitor work, and trending topics. Dashboards allow employees to incorporate news sources, social media feeds, and more, into one location. Team members can tailor their dashboards to include information from as many or as few sources as they need, helping them create a reliable and up-to-date resource portal. Dashboards also make it easier for boutique employees to follow changes in their clients' industries. Employees are able to conduct research effectively and create more industry-specific and reliable content. ## Individual Organization One of our tech clients utilizes MangoApps Dashboards for individual organizational success. Functioning almost like a digital planner, employees use their digital dashboards to store notes, add reminders, view tasks, organize to-do items, track important events, and keep an eye on their personalized calendar. Employees have found that after implementing dashboards, work became much more streamlined and easier to manage. Keeping everything available in one location has helped employees stay focused and productive throughout the day. Employees are able to turn thoughts into actions, as daily reminders and to-do lists keep ideas from being forgotten. ## Frontline and Deskless Workers: A Use Case Often Overlooked The use cases above are desk-worker-centric, but dashboards matter just as much — arguably more — for frontline teams. Per Emergence Capital, 80% of the global workforce is deskless. Frontline and deskless employees can access MangoApps Dashboards on personal mobile devices without a corporate email address, removing a common barrier to adoption for distributed teams in retail, manufacturing, and [ambulatory care](/industries/ambulatory-care) settings. For retail shift workers, a dashboard can surface the day's schedule, safety updates, and team announcements the moment they clock in — no VPN, no IT ticket, no shared kiosk required. Replacing a single frontline employee costs between $4,400 and $15,000 on average; dashboard-driven engagement and communication are a measurable lever for reducing that turnover cost. The [Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) covers how operations leaders are applying this thinking today. MangoApps AI can also auto-surface relevant content by role, location, or team — so a nurse on a night shift and a warehouse associate on a morning shift each see what is relevant to them, without manual configuration by a manager. ## What Results Do Customers Actually See? Qualitative anecdotes are useful, but measurable outcomes matter more when building a business case. OU Health achieved 87% workforce engagement within months of launching a branded, role-personalized employee app built on MangoApps. For independent validation of where MangoApps sits in the intranet and employee experience platform landscape, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides a detailed, analyst-led comparison. MangoApps was also [recognized in a leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) for its approach to unified employee experience. ## What to Do Next MangoApps Dashboards are personalized intranet portals designed to incorporate all of your needs. They help employees stay on top of important details, quickly communicate with each other, and access critical information — whether they are at a desk, on a hospital floor, or on a retail floor without a corporate email address. If you are evaluating dashboards for your organization, three questions worth answering first: What systems do your employees currently switch between daily? Which employee segments have the lowest intranet adoption today? And what does a measurable engagement or productivity outcome look like for your team? To see how MangoApps Dashboards work in practice for your industry, schedule a personalized demo — or explore the [employee app](/solutions/employee-app) to understand how dashboards fit into a broader unified platform. ## How Do I Set Up a MangoApps Dashboard? Dashboard setup in MangoApps is handled at the administrator level, with no engineering support required. Admins can configure role-based default layouts, pin specific widgets (tasks, announcements, calendars, news feeds), and allow employees to personalize within defined parameters. Frontline employees without corporate email addresses can be onboarded via the mobile app using a phone number or employee ID. For teams with complex integration needs, MangoApps connects to 200+ enterprise systems including HRIS and LMS platforms, so existing tools surface inside the dashboard rather than requiring employees to leave it. ## How Does MangoApps Compare to Other Intranet Platforms? The intranet market is crowded, and the definition of intranet has expanded significantly — modern platforms are expected to handle communications, task management, knowledge management, and frontline access in one place. MangoApps is designed as a unified platform rather than a point solution, which means dashboards are connected to the same data layer as messaging, documents, and workflows. For an analyst perspective on how MangoApps compares, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) is the most current independent evaluation available. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) also covers how organizations are rethinking their intranet strategy as workforce demographics shift. --- # Uncover Inspirations With The MangoApps Ideas Module **Author:** Anjali **Published:** 2019-02-28 **Category:** modules-features Some of the best industry insights and ideas come from internal employees. Employees interact with company products and service in a wide variety of ways and often develop insightful perspectives. Finding and utilizing these inspirations though can be a little tricky. Typically, companies rely on a suggestion box system to gather ideas from their workforce, […] # Uncover Inspirations With The MangoApps Ideas Module Employee ideas are one of the least tapped sources of organizational advantage. Workers who interact directly with customers, products, and processes see inefficiencies, opportunities, and friction points that leadership often misses entirely. The challenge is not a lack of good ideas — per APQC, Fortune 500 companies lose an estimated $31.5 billion annually to knowledge loss, much of it from insights that were never captured or acted on. The challenge is infrastructure: most organizations rely on suggestion boxes, shared inboxes, or informal channels to surface employee input, and these methods are too broad and disorganized to produce consistent results. The MangoApps Ideas Module replaces that infrastructure with a structured, campaign-based system that takes employee ideas from submission through evaluation and into task workflows. This article explains how the module works, who benefits most, how it compares to standalone suggestion tools, and what getting started actually looks like for teams evaluating [employee engagement](/solutions/employee-engagement) software. ## Why suggestion boxes fail at scale Traditional suggestion boxes — physical or digital — share a fundamental structural problem: they collect everything and organize nothing. Without a defined scope, submissions range from operational requests to product ideas to personal complaints. Without an evaluation workflow, ideas pile up in a queue that grows faster than anyone can review. Without visibility into what happens after submission, employees stop contributing. Per a Banner Health employee poll on intranet performance, 59% of employees reported having trouble finding information they needed — a finding that applies equally to ideas buried in unstructured repositories. When contributors cannot see their input being acted on, the participation loop breaks, and the knowledge embedded in those observations is effectively lost. The MangoApps Ideas Module was built to fix these mechanics: structured campaigns replace open-ended submission boxes, voting surfaces the strongest ideas automatically, and direct integration with task management closes the gap between approval and action. ## How the Ideas Module works: campaigns, targeting, and evaluation The module is organized around campaigns rather than a single catch-all inbox. Admins create individual campaigns targeted to specific business objectives — a product feedback initiative for customer-facing teams, a process improvement campaign for operations, a cost-reduction challenge for finance. Each campaign has its own scope, timeline, and evaluation criteria. Campaign targeting goes beyond broadcast delivery. Admins can segment by persona, role, or location, ensuring idea campaigns reach the employee segments most likely to have relevant input rather than broadcasting to the entire workforce indiscriminately. Per MangoApps and Akumina communications product pages, this targeted delivery is a meaningful differentiator against general-purpose suggestion tools that treat all employees as a uniform audience. Once a campaign is live, employees submit ideas with text, images, attachments, or hashtags. Colleagues vote on submissions and comment to refine or expand them. The voting mechanism surfaces the strongest ideas organically — most-endorsed submissions rise to the top, giving evaluators a clear signal on where to focus review time. Admins designate evaluators — individuals or groups — who assess submissions, update idea statuses, and route approved ideas forward. ## Mobile-first idea capture: including frontline workers One of the structural failures of traditional suggestion systems is that they exclude the workers most likely to observe operational problems firsthand. Frontline and deskless employees — warehouse workers, retail associates, field technicians, clinical staff — typically lack desk access and company email accounts. Per Beekeeper and MangoApps frontline product pages, this exclusion is systemic: these workers often have the clearest view of process failures and customer friction, but they are effectively shut out of suggestion systems built for desk-based employees. The MangoApps Ideas Module is fully accessible on mobile, tablet, and smart devices. Employees can capture ideas in the moment — on the floor, in the field, between shifts — and expand or refine submissions later. Per a Banner Health employee poll, 55% of employees want intranet access from a mobile device and 61% want access outside the work VPN. For organizations with distributed or frontline workforces, mobile reach determines whether the full workforce participates in idea programs or only the desk-based subset. ## Closing the submission-to-implementation gap The distance between idea submission and actual implementation is where most suggestion programs lose momentum. An employee submits an idea, receives no feedback, and eventually stops contributing. The organizational learning in that observation is never captured. The Ideas Module addresses this with explicit workflow stages. Submitted ideas move through defined phases — socialization, evaluation, approval — with status updates visible to contributors. Evaluators have full visibility into submission history and can communicate decisions rather than leaving contributors without feedback. When an idea is approved, it converts directly into a task in MangoApps' work management layer. This direct routing from approval to execution reduces the gap between submission and implementation — a capability that employee engagement software competitors consistently position as a core differentiator against standalone suggestion tools that stop at collection and voting. ## Leaderboards, analytics, and measuring idea program performance Campaign analytics and leaderboards give admins the data to evaluate whether an idea program is working and which contributors are driving the most value. The Ideas Module tracks submissions, votes, and conversions from campaign launch through task completion. Leaderboards surface top contributors by submission volume and idea popularity, creating visible recognition for active participants. Per McKinsey research, 81% of leading companies effectively use data and analytics tools — connecting idea activity to measurable business outcomes is part of what separates organizations that benefit from employee input from those that simply collect it. Analytics at the campaign level show participation rates, evaluation throughput, and conversion rates from idea approval to task creation. Teams that want to connect idea management to broader engagement reporting can do so within MangoApps' unified analytics layer rather than exporting data to a separate tool. ## The Ideas Module as part of a unified employee engagement platform Idea management delivers its full value when connected to the broader engagement stack, not deployed as a standalone feature. When campaigns, voting, evaluation, and task conversion are integrated with communications, recognition, and performance tools on one platform, the impact compounds in ways that isolated suggestion systems cannot replicate. A retail organization that runs an idea campaign among store associates, surfaces winning submissions through internal communications channels, recognizes top contributors through the recognition module, and converts approved ideas into store-level tasks has built a visible, self-reinforcing loop. Per a British Airways case study via Unily, organizations using unified engagement platforms have reported a 91% usage rate post-rollout for a 40,000-employee workforce, with a 30-point increase in employee engagement tied to connected social and analytics features. The [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) report adds independent context: conditions that allow employees to feel heard — including whether their ideas are solicited and acted on — are a direct predictor of organizational outcomes including productivity and retention. For teams evaluating how unified platforms compare on integration depth and employee experience, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent third-party analysis. ## Getting started: what implementation looks like Setup time is a reasonable concern when evaluating any new module. Admins can launch a campaign by selecting a title, writing a description, assigning campaign managers, and setting start and end dates — a process that takes minutes rather than weeks. Campaign managers do not require administrative permissions beyond their assigned campaigns, so large organizations can delegate idea program management to department heads or business unit leads without elevating broader system access. For context on broader platform adoption: the average SharePoint intranet deployment takes approximately nine months, per the dormakaba case study. MangoApps is designed to move at a different pace. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how organizations are consolidating employee engagement tools and what implementation patterns look like when the goal is platform consolidation rather than point-solution replacement. ## Ideas Module vs. standalone suggestion tools Organizations evaluating idea management software typically encounter two categories: standalone suggestion platforms and idea management as a feature within a broader employee engagement suite. Standalone tools focus on collection and curation — structured submission forms, voting, and basic workflow. Their limitation appears at the edges: approved ideas have no native path into task execution, and idea activity lives in a silo separate from the engagement, recognition, and communications data the organization already tracks. Integrated platforms treat idea management as one node in a connected employee experience. Campaign results inform recognition decisions. Approved ideas convert into tasks without manual handoff. Participation data sits alongside other engagement metrics in a single view. For organizations already using MangoApps for communications, document management, or frontline operations, the Ideas Module extends that infrastructure rather than adding a separate system to manage. ## What to expect from a structured idea program Organizations that implement structured idea programs consistently report the same pattern: the first campaign generates more submissions than expected, a smaller number are actionable, and the evaluation workflow is the organizational capability that determines whether the program sustains beyond the first cycle. The MangoApps Ideas Module gives organizations the mechanics to run that workflow — campaigns, targeting, voting, evaluation stages, task conversion, and analytics — in one place. The business value is the practice it enables: a repeatable system for capturing, evaluating, and acting on employee input at the pace the business requires. For teams in industries with high employee turnover or distributed workforces — including retail, healthcare, and manufacturing — the speed and mobile accessibility of idea capture matter as much as the evaluation workflow. Ideas that cannot be captured in the moment, by the workers closest to the problem, are ideas that are effectively lost. --- # Is Higher Pay Winning Over Your Employees? **Author:** Anna Carriveau **Published:** 2019-02-21 **Category:** employee-engagement The priorities of employees are changing. While bosses in the past could rely on motivating employees with salary increases, the modern workforce has other ideas. Employees today, consider a wide range of engagement factors when accepting a position within a company. These considerations typically include having a sense of purpose, a strong work/life balance, an […] # Is Higher Pay Winning Over Your Employees? The priorities of employees are changing. While bosses in the past could rely on motivating employees with salary increases, the modern workforce has other ideas. Employees today consider a wide range of employee engagement factors when accepting a position within a company. These considerations typically include having a sense of purpose, a strong work/life balance, an inviting and inclusive work environment, and career advancement opportunities. While money will always be an important aspect of the work experience, here's what to expect when you only count on money to win over your employees — and what to do instead. ## Significant Revenue Losses Throwing money at a problem to win over your employees seems like an easy answer, and in the past it was. Getting employees to work longer and work harder was as simple as naming the right price. However, incentivizing employees to work around the clock tends to create more problems than actual solutions. Being constantly on call or working late hours day after day, month after month, and even year after year takes a mental, physical, and emotional toll, and employees are no longer satisfied. Employees expect their organizations to respect their work/life balance and recognize their needs away from the business. Overly investing in an organization today almost always contributes to disengagement, regardless of the monetary compensation. This disengagement tends to result in higher stress levels, decreased energy, and ultimately lower productivity. A recent Gallup study estimated that productivity losses cost the US economy between $450 to $550 billion every year. A single disengaged employee can cost a company $3,400 for every $10,000 the organization spends on salaries. As employees begin to experience stress, anxiety, and unhappiness, they often reach out to coworkers and colleagues for support. This can increase feelings of discontent and irritability. Instead, try investing in real employee happiness and values. This will help your workforce stay much more focused, boost employee engagement, and improve productivity. For a broader look at where workforce expectations are heading, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines the non-monetary factors reshaping retention strategies this year. ## Poor Customer Service When it comes to bad customer service experiences, there are almost never second chances. In fact, a recent study noted that a single negative customer service experience can drive away over 82% of customers. Even if you have world-class marketing to promote a positive image, it is your employees that actually interact with customers. Generously compensated employees still struggle to maintain genuine brand loyalty and customer care when their opinions, values, interests, and concerns are not being recognized. Disguising unhappiness in front of customers only works so far, and instead of helping win over your employees, attempting to soothe over problems with money tends to increase resentment in the long run. This dynamic is especially pronounced in customer-facing industries. Organizations in [retail](/industries/retail) and hospitality, for example, see direct revenue consequences when frontline employee engagement drops — no pay increase compensates for a workforce that feels unheard. You can use an employee experience platform like MangoApps to create surveys and polls — what practitioners call employee engagement questionnaires — to gauge employee opinions within the organization. These tools, combined with caring and considerate management, help companies create long-lasting, authentic, and passionate employees. ## Burnt Out Employees Organizations with highly engaged employees typically experience more growth than companies with lower engagement levels. This is largely due to increased employee productivity, consistency, and dedication. Overworked employees burn out quickly, which decreases morale, diminishes productivity, and escalates employee turnover. Between recruiting costs and onboarding expenses, replacing an employee can cost on average 20%–30% of the employee's annual salary. And when employees are burning out left and right, those costs can quickly add up. Increasing turnover rates can make it very difficult to attract talented and hard-working employees. Recognition is a concrete lever here that pay alone cannot replicate. Companies with strong recognition cultures see 31% lower voluntary turnover than those without formal programs. Employees who feel adequately recognized are 2.7x more likely to be highly engaged than those who do not. Recognition programs that include peer-to-peer acknowledgment — not just manager-to-employee — are linked to stronger retention outcomes, a dimension pure pay increases cannot replicate, per SHRM recognition research. To see how one organization built this infrastructure in practice, read [From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program). For a deeper look at the warning signs before burnout becomes turnover, [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace) offers current benchmarks on engagement and stress across industries. ## Remote and Frontline Employees Face a Distinct Challenge The pay-as-motivator problem is not uniform across your workforce. Per Emergence Capital, 80% of the global workforce is deskless — frontline workers in retail, healthcare, logistics, and similar sectors who rarely sit at a desk and are often the hardest to reach with traditional engagement programs. Remote and hybrid employees report lower engagement scores than on-site peers when recognition is infrequent or informal, suggesting that distributed teams require structured non-monetary engagement programs, per Gallup's State of the Global Workplace research. For these employees, a pay increase is even less likely to address the root cause of disengagement: they feel invisible. Mobile-first employee engagement software closes this gap by bringing recognition, communication, and feedback tools directly to the devices frontline workers already use. Employees who feel their non-monetary values — purpose, flexibility, inclusion — are met are significantly less likely to accept a counter-offer when recruited away, making pay-only retention strategies structurally fragile, per Deloitte Global Human Capital Trends. ## So Now What? Building a Non-Monetary Engagement Strategy While most employees today value work that provides freedom, flexibility, remote options, and a healthy work/life balance, the only way to truly know what your employees want is to ask. Anonymous employee engagement surveys are a practical resource for employees to communicate their challenges, opinions, interests, and needs — and the data they generate should drive action, not just reporting. A structured approach to non-monetary engagement typically includes three components: - **Recognition infrastructure:** Formal and peer-to-peer recognition programs that make employees feel seen on a regular cadence, not just at annual reviews. - **Feedback loops:** Regular employee engagement questionnaires and pulse surveys that surface issues before they become turnover events. - **Career development:** Training and employee engagement programs that connect daily work to long-term growth. Research consistently shows that employees who see a development path are more likely to stay. For practical guidance, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) is a useful starting point. As you commit to working with your employees across all three areas, you will be able to build a loyal team that is dedicated to achieving long-term success. ## MangoApps: An Employee Engagement Platform Built for This Problem At MangoApps, we believe open communication is the primary way to win over your employees. MangoApps is an [employee engagement platform](/solutions/employee-engagement) specifically designed to encourage, motivate, and communicate with everyone in your organization — including deskless and remote workers who are most vulnerable to pay-only motivation strategies. The platform combines employee engagement surveys, peer-to-peer recognition, social communication, and performance tools in one place, replacing the fragmented approach of using pay as a substitute for genuine engagement infrastructure. Organizations looking to move from philosophy to practice can explore [MangoApps' solutions for performance management](/solutions/performance-management) as a complement to recognition and feedback programs. If you would like to learn more about how MangoApps can help improve your employee engagement, contact us or schedule a demo today. --- ## Frequently Asked Questions ### What non-monetary incentives actually reduce employee turnover? The most effective non-monetary retention levers are structured recognition programs (including peer-to-peer acknowledgment), clear career development pathways, and consistent feedback mechanisms. Companies with strong recognition cultures see 31% lower voluntary turnover than those without formal programs. Pay increases, by contrast, address dissatisfaction temporarily but do not build the sense of purpose or belonging that keeps employees from accepting competing offers. Per Deloitte Global Human Capital Trends, employees whose non-monetary values are met are significantly less likely to accept a counter-offer when recruited away. ### How do I measure employee engagement beyond salary satisfaction? Employee engagement questionnaires and pulse surveys are the standard starting point. Effective surveys go beyond satisfaction scores to measure dimensions like sense of purpose, manager relationship quality, recognition frequency, and career growth confidence. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring their listening programs to capture these signals at scale. Anonymous survey tools are especially important for frontline and remote workers, who may be reluctant to share candid feedback through direct channels. ### How does employee engagement software replace pay-as-motivator strategies? Employee engagement software operationalizes the non-monetary engagement model by giving managers and HR teams the tools to recognize employees consistently, collect and act on feedback, and connect workers to company purpose — all in one platform. Rather than relying on periodic pay reviews to signal that employees are valued, a unified platform creates daily touchpoints that reinforce belonging and recognition. For organizations with distributed or frontline workforces, mobile-first employee experience platforms are particularly important because they reach workers where they are, not just where a desktop happens to be. --- # Decrease Distractions With MangoApps File Management **Author:** Anjali **Published:** 2019-02-19 **Category:** modules-features Nothing quite compares to working “in the zone.” You know the feeling, when difficulties feel like an exciting challenge, the task ahead holds your undivided attention, you have a true zeal for the work at hand, and productivity is at its peak. Unfortunately, “in the zone” moments are becoming less and less frequent during the […] # How MangoApps File Management Reduces Workplace Distractions Employees spend an average of 2.5 hours per day searching for information they need to do their jobs, per IDC. At a 40-hour workweek, that is roughly the equivalent of a full day each week consumed by navigation rather than work. The cause is almost never a motivation problem — it is an architecture problem. When documents live in disconnected systems, finding the right version of a file requires context-switching that destroys focus and accumulates into an invisible tax on every team's output. MangoApps file management consolidates document storage, search, collaboration, and access controls into a single intranet platform. The argument for doing so is not convenience — it is a measurable reduction in the coordination overhead that builds whenever employees have to navigate tool fragmentation to accomplish basic tasks. ## File sprawl is a unification problem, not a storage problem Organizations rarely lack storage. They have too much of it, in too many places, with too little coherence between them. The result shows up in how employees actually work: per MangoApps internal competitive intelligence, employees lose over four hours per week switching between disconnected systems. Per SWOOP Analytics, the average employee spends only six minutes per day on intranet tools. When file access requires navigating to a separate system, those six minutes are often the only window an employee has — and most files will never be found within them. Per Social Edge Consulting, 91% of organizations operate an intranet, but nearly a third of employees never log in, and only 13% use it daily. The gap between deployment and actual adoption is a search-and-access problem: tools that make files hard to find train employees to route around them entirely. The fix is not adding more storage capacity — it is building a single environment where documents, conversations, and tasks coexist, and where finding a file takes seconds rather than a context-switching chain through three separate platforms. That is what MangoApps functions as: a uniting intranet where file management, team collaboration, and operational workflows share a common environment. The sections below cover how each file management capability contributes to that consolidation — and where organizations typically see the clearest productivity gains. ## Why enterprise document security has to come first File management that employees will actually use has to be file management they can trust. MangoApps supports SAML 2.0 and OAuth 2.0 authentication, encrypted storage through Amazon S3 with automatic virus scanning and file encryption at rest, and tiered permission controls that let administrators assign one of four access levels to any document. Full version management, file check-in and check-out to prevent conflicting edits, and storage options that extend to Box or SAN storage round out the enterprise security foundation. These are not secondary features. The "secure intranet" theme is now prominent across competing platforms — organizations have made security the headline of their file management story rather than a footnote in a feature list. Leading with security in a file management conversation is also a response to a real operational risk: most companies cannot tell you, today, exactly which version of a compliance document a given employee last accessed, or whether a file shared with a contractor three months ago has been revoked. MangoApps makes those questions answerable. The security case also directly addresses the frontline workforce access gap. Per Emergence Capital, approximately 80% of the global workforce is deskless. Many frontline employees lack corporate email addresses, which means traditional file management systems that require email-based authentication create a structural access barrier for the majority of the workforce in most organizations. MangoApps supports no-email-required document access — a capability that matters not just for usability but for retention. Replacing a single frontline employee costs between $4,400 and $15,000 on average. Document access friction is a retention risk, not just a productivity metric. ## Editing and collaboration without leaving the platform With Office 365 integration, users can view, create, edit, and co-edit Word, PowerPoint, and Excel files directly inside MangoApps. The platform handles file locking and version management automatically, autosaves all files, and maintains a full access and edit history. Employees can attach documents from SharePoint, OneDrive, Google Drive, and Dropbox without leaving the platform, and publish edited files back to external systems to keep external repositories in sync without manual re-upload workflows. The productivity argument is concrete. Per a Journal of Experimental Psychology study, interruptions as short as 2.8 seconds more than doubled participants' inability to recall where they left off in a task sequence. Toggling between a communication platform and a separate document editor is exactly the kind of micro-interruption that accumulates into the four-hour-per-week context-switching loss cited above. Keeping editing inside the same environment where work is assigned and discussed eliminates that switching cost at the source. For teams connecting document activity to project timelines, [trackers and workflows](/key-features/trackers-workflows) in MangoApps link file updates to operational tasks without requiring separate status reporting — closing the loop between a document change and the work it belongs to. ## Search that finds what you need, not what you remember naming Standard intranet search indexes file titles. MangoApps deep search indexes content — inside PDFs, HTML and XML files, RTF documents, plain text files, and content inside ZIP archives. Users can attach custom metadata to documents, which makes it possible to filter and explore by attributes relevant to their workflows rather than navigating folder structures designed by someone else months ago. AI-assisted retrieval extends this further, surfacing relevant files based on context rather than requiring exact keyword matches. This is one of the core knowledge management tools that separates a functional intranet from a file dump. When search surfaces the right document in seconds, employees stay in context and avoid the disorientation that comes from extended information hunts. It also makes the system more equitable: it works for someone who joined three months ago and for someone who has been there ten years. The teamwork management case for better search is straightforward. When team members can find documents independently, they stop creating duplicate files, stop asking colleagues to resend attachments, and stop working from outdated versions. Search quality is one of the primary reasons that Social Edge's 13%-daily-engagement figure looks the way it does — employees who cannot find what they need stop coming back. For organizations comparing MangoApps to other enterprise intranet platforms on search and document management, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent analysis across leading vendors. ## File management as the connective tissue of a single-platform strategy Enterprise SharePoint deployments carry first-year costs between $130,000 and $426,000 for a 1,000-user organization, per Awesome Technologies Inc.'s 2025 cost model. That figure does not include the integration work required to connect SharePoint to a separate communication platform, a separate task management system, and a separate employee directory — each with its own maintenance overhead and access friction. MangoApps includes file management as part of a broader intranet and collaboration platform, which means the consolidation case extends well beyond storage licensing. Documents, conversations, team workspaces, and search share a single environment. Employees do not context-switch to access a file that was shared during a project discussion — the document is already in the same place where the discussion happened. For a large-scale example of what this looks like in practice, the [Raley's Companies case study](/resources/raleys-case-study) covers how a multi-site retailer extended intranet access to 20,000 employees — including frontline workers across dozens of locations — using MangoApps as the single platform for communication and file management. ## What to measure after consolidation The productivity recovery from consolidating file access is not theoretical — it is measurable, if organizations track the right indicators. Three metrics correspond directly to the underlying problem that file consolidation addresses. **Search time per task.** The IDC benchmark of 2.5 hours per day searching for information establishes a meaningful baseline. Organizations that track time-to-document before and after consolidation consistently find that unified search and deep content indexing recover time that was previously invisible in project budgets. **Intranet engagement rates.** The Social Edge benchmark of 13% daily active use reflects how most enterprise intranet deployments perform. A file management system that employees use — because it is fast, accessible, and returns accurate results — moves this number. Weekly active use rates and document retrieval frequency are practical proxies for whether the platform is doing its job. **Frontline adoption.** For organizations with a significant deskless workforce, mobile document retrieval rates and active use among frontline employees are the clearest signal that the no-email-required access model is working. If frontline engagement with documents is near zero, the access architecture still has a gap the platform configuration has not closed. The 2.5-hour daily loss from fragmented file access is a recoverable number. Organizations that consolidate on a unified platform with working internal links, permission-gated access, and deep search consistently report moving their effective search time well below the IDC baseline — not because employees suddenly become more efficient, but because the tool architecture stops working against them. --- # Increasing Employee Engagement With Technology **Author:** Anna Carriveau **Published:** 2019-02-14 **Category:** employee-engagement It’s well known throughout the working world that employee engagement and business profitability go hand in hand. But just understanding the importance of engagement isn’t enough. Despite increased awareness about this concern, the majority of employers still struggle to find a solution. An astounding 86% of the global workforce considers itself primarily unengaged while at […] It's well known throughout the working world that employee engagement and business profitability go hand in hand. But just understanding the importance of engagement isn't enough. Despite increased awareness about this concern, the majority of employers still struggle to find a solution. An astounding 86% of the global workforce considers itself primarily unengaged while at work. Among the companies who have succeeded in encouraging and improving employee engagement, one clear strategy points to their success: technology. When it comes to employee engagement efforts, the right employee engagement software can make all the difference. Below are five ways employers can increase employee engagement through the use of technology—plus what to measure, what to avoid, and which follow-up questions to answer before you re-search. ## 5 Ways To Improve Employee Engagement With Technology ### #1: Improve Learning Experiences Technology provides new opportunities for employees to effectively learn about your business. It allows employees to become better prepared for their position and find their fit within the organization. Yet workplace and workforce learning has become the fastest-escalating content gap in the employee engagement category—at least nine competitors now publish dedicated content on the topic, per Mango IQ competitive movement data—which means organizations that treat learning as an afterthought are falling behind on both culture and search visibility. Effective employee engagement training goes well beyond a static PDF library. Structured learning workflows, video-based and virtual learning formats, and integration with an LMS learning system give every employee a clear development path tied to their role. Technology solutions can help employers administer effective coaching techniques for every employee. Technology tools can also help simplify the onboarding and recruitment experience, creating a positive first impression for employees and setting them up for future happiness and success. For a deeper look at how to embed training on employee engagement into daily workflows rather than treating it as a one-time event, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ### #2: Facilitate Employee Recognition There are few things more disappointing than working hard without recognition. Showing employees appreciation and encouragement is essential to retaining their trust, support, and dedication. While it may be impossible to call for a physical celebration, there are plenty of technology-enabled channels for you to celebrate their success. Having a social intranet that connects everyone in your organization makes it easy to highlight accomplishments and show support to all employees. Showing encouragement and support is particularly important for junior employees, who often receive less recognition than their peers. Replacing a disengaged frontline employee costs between $4,400 and $15,000, making technology-driven recognition a direct cost-avoidance strategy, not just a culture initiative, per MangoApps mobile product page industry report attribution. Organizations that have deployed modern recognition tools have seen measurable results: one case study reports an 87% workforce engagement rate achieved within a few months of launching a branded employee app (OU Health case study). ### #3: Empower Coworker Collaboration Effective teams make or break employee engagement. If a team is going to succeed, it needs to have reliable information exchange, individual accountability and responsibility, and efficient team management. While that might be easy in some areas, when teams are separated by different locations, succeeding together can feel impossible—unless you have the right technology. Employees lose over four hours per week switching between disconnected systems, a direct drag on engagement that a unified platform eliminates. On top of that, IDC research shows employees spend 2.5 hours per day searching for information, per IDC—time that could be redirected toward meaningful work. Organizations all over the world use collaboration and communication tools to help teams perform together and achieve their different goals. Communication software should include file sharing, project management, instant communication channels, and more. When teams can successfully accomplish outcomes and achieve their goals, increased employee engagement will naturally follow. For organizations in complex or distributed industries, resources like [The Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026 and beyond](/resources/ultimate-intranet-buyers-guide-for-a-frontline-workforce-2026) offer practical criteria for evaluating collaboration platforms. ### #4: Encourage Honest Feedback Traditional employee surveys tend to be fairly limited, and typically do not allow employees to offer their genuine opinion. However, there are now several technology-enabled solutions that allow organizations to conduct quick, effective, and completely anonymous employee engagement surveys. These solutions allow employees to speak freely and be heard, while still maintaining appropriate privacy and security. As employees are able to voice their opinions through structured employee engagement questionnaires, managers and other corporate leaders will receive important insights, ideas, and feedback, while helping employees feel acknowledged and understood. For broader context on where employee listening is heading, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how survey cadence and anonymity design are evolving across industries. ### #5: Create Social Engagement One of the best ways to build company engagement with technology is to incorporate intuitive, social media-style tools into your work environment. Successful organizations today deploy branded company intranets that mirror popular social media tools and let both the organization and its employees make posts, send updates, share photos, organize activities, run polls, and communicate together. However, adoption is a persistent challenge. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use intranet tools daily. SWOOP Analytics benchmarks average daily intranet use at just six minutes per day, per SWOOP Analytics. The gap between deployment and genuine engagement is real—and it's why static, one-size-fits-all intranets are being replaced by branded, AI-personalized platforms that surface role- and location-specific updates rather than a single undifferentiated company feed, per Unily product page and MangoApps product pages. For frontline and deskless workers—who represent 80% of the global workforce, per Emergence Capital—this distinction is especially important. Frontline employees without corporate email or a desk can still access training, schedules, HR self-service, and team communications through a single branded mobile app, no VPN required, per MangoApps mobile and frontline product pages. As employees are able to create connections and collaborate in a familiar and engaging environment, they will naturally become more involved and engaged on every level. Organizations that have made this shift report a 30-point increase in engagement score after deploying a modern intranet platform (British Airways case study). See [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study) for a real-world example of a branded intranet driving measurable engagement across a distributed workforce. ## MangoApps As the world progresses toward a more digitally enabled environment, the role of technology in the workplace will only continue to rise. Companies that invest in technology that encourages and empowers their employees will always bring out their best potential. For over a decade, MangoApps has helped organizations of every size work better through innovative, adaptive, and personalized business technology. You can explore MangoApps' [solutions/employee-engagement](/solutions/employee-engagement) to see how the platform addresses each of the five pillars above in a single unified experience. To see how MangoApps can personally benefit your business and improve your employee engagement with technology, contact us today or schedule a demo. --- ## How Do I Measure Whether Technology Is Actually Improving Engagement? Deployment is not the same as impact. To know whether your employee engagement software is working, track a short set of leading indicators alongside lagging ones: - **Adoption rate**: What percentage of employees log in at least weekly? Per Social Edge Consulting, only 13% of employees use intranet tools daily—use that as a baseline to beat. - **Survey response rate**: Higher participation in employee engagement questionnaires signals psychological safety, not just tool availability. - **Time-to-information**: If employees are still spending 2.5 hours per day searching for information (per IDC), your platform's information architecture needs work. - **Recognition frequency**: Track peer-to-peer recognition posts month over month. Flat or declining volume is an early warning sign. - **Learning completion rates**: If you've integrated an LMS learning system, completion rates for employee engagement courses are a direct proxy for whether learning is embedded in daily work or treated as optional. For a structured framework on tracking these metrics across your workforce, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers measurement approaches tied to operational outcomes. ## Which Types of Organizations See the Fastest Results? The five strategies above apply broadly, but certain workforce profiles see faster returns: - **Retail and hospitality**: High frontline-to-desk ratios mean mobile-first access is non-negotiable. A unified app that delivers schedules, recognition, and team communications without requiring corporate credentials removes the single biggest adoption barrier. See how these dynamics play out in [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling). - **Healthcare and nonprofits**: Compliance-sensitive environments benefit most from structured employee engagement training workflows and anonymous feedback channels that meet documentation requirements. - **BPO and distributed services**: Teams spread across time zones need asynchronous collaboration tools and AI-personalized feeds so that relevant updates reach the right people without flooding everyone. For industry-specific guidance, MangoApps publishes resources for [retail](/industries/retail) and [nonprofit](/industries/nonprofit) workforces that map engagement technology to sector-specific workflows. ## What Are the Most Common Pitfalls When Using Technology for Engagement? Technology alone does not create engagement—implementation and governance determine whether tools become habits or shelfware. The most common failure modes: 1. **Launching without a content strategy**: An intranet with no editorial ownership quickly becomes a ghost town. Assign section owners and publish a minimum viable content calendar before go-live. 2. **Ignoring frontline access**: If your engagement platform requires a corporate email address or VPN, 80% of the global workforce (per Emergence Capital) is effectively excluded from day one. 3. **Treating the survey as the strategy**: Employee engagement questionnaires surface problems; they don't solve them. Close the loop publicly—share what you heard and what you're changing. 4. **Underinvesting in learning**: The 'Improve Learning Experiences' section is where most organizations cut corners. Structured employee engagement courses tied to career paths outperform ad hoc training libraries on every retention metric. 5. **Measuring adoption instead of outcomes**: Login counts are a vanity metric. Tie your employee engagement software metrics to business outcomes—turnover rate, time-to-productivity for new hires, and internal promotion rates—to make the ROI case to leadership. For additional context on how leading organizations are approaching these challenges, [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace) provides current benchmarks on engagement drivers and failure modes across regions and industries. --- # How MangoApps Forms Can Significantly Simplify Company Paperwork **Author:** Anjali **Published:** 2019-02-12 **Category:** modules-features In an office-setting, the word ‘paperwork’ often conjures up images of long hours, tedious tasks, and unproductive assignments. Even important and necessary paperwork can feel mundane, draining, and inspire all kinds of procrastination. MangoApps Online Forms aims to change that. We know that some forms are unavoidable, but that doesn’t mean they should be difficult, […] # How Digital Forms Reduce Manual Operations Overhead Across Your Organization The daily search for information costs employees 2.5 hours per day, per IDC. Most operations leaders assume that figure comes from sprawling documentation or unclear processes. The actual driver is simpler: the average organization runs six to eight disconnected tools, and submitting a form often means leaving one system, logging into another, and waiting for an approval that routes through a third. The problem isn't that organizations still use paper. Most have already digitized their forms. The problem is where those digital forms live — in standalone SaaS tools disconnected from the systems where decisions actually get made. Platform-embedded digital forms change the architecture of that problem. When forms, approvals, and submission data live in the same employee experience platform employees use for scheduling, communications, and task management, submissions stop creating system-crossing delays. The paperwork still exists. The operational penalty for completing it largely doesn't. ## Why "digitizing forms" is the wrong frame The business case for form digitization is usually presented as a paperwork story: fewer filing cabinets, fewer manual data entries, fewer lost submissions. That framing is accurate but misses the core operational problem. Ninety-one percent of organizations already operate an intranet, per Social Edge Consulting. Yet only 13% of employees use one daily, and nearly a third never log in at all. The average employee using intranet tools spends six minutes per day on them, per SWOOP Analytics. That's not a training gap — it's a navigation gap. Forms buried in separate systems get abandoned before they get completed. The operational consequences are predictable. Expense submissions pile up in email threads. PTO approvals wait for a manager to check a secondary tool. Incident reports get filed inconsistently because three people on the same team use three different processes. Each individual delay is small. Aggregated across a workforce of 500, the processing overhead adds up fast. The right frame isn't "we need to digitize our forms." It's "we need forms that live where decisions happen — and that route automatically to the people who need to act on them, without requiring anyone to open a new tab." ## What platform-embedded forms actually replace When forms are embedded in the employee experience platform rather than hosted in a standalone tool, three things change structurally. **Submissions trigger workflows, not just storage.** A PTO request submitted through a standalone form tool creates a record in a tracker. A PTO request submitted through a platform-embedded form triggers an approval routing to the manager directly in their workflow view, with submission data already attached. The distinction isn't between paper and digital. It's between a form that creates a data artifact and a form that creates an action. **Data stays governed in one place.** Centralizing form data within a unified platform — rather than routing submissions through multiple SaaS tools — reduces the attack surface for data exposure and supports governance requirements across HR, IT, and compliance teams. Every sensitive submission touches fewer systems, which means fewer security models to manage and fewer points of failure. [Teams navigating the complexity of unionized environments](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) gain an additional benefit here: a clear, auditable submission record for every transaction, rather than approvals scattered across email and chat. **Employees submit where they already are.** Form discovery falls apart when completing a form requires navigating to a different system. Embedded forms appear in the same interface where employees check their schedule, read announcements, and communicate with their team. The average employee spends six minutes per day on intranet tools, per SWOOP Analytics — that's not enough time to navigate away, log into something new, find the form, and submit it. Embedded forms remove the navigation step entirely. ## The frontline gap most form tools leave open The operational case for digital forms is well-understood for desk-based workers. The more significant gap is for the teams traditional tools leave out. Eighty percent of the global workforce is deskless, per Emergence Capital. Frontline and field-based employees in retail, healthcare, field service, and manufacturing have historically been underserved by form tools designed for office environments. Forms that require a desktop login, a corporate email address, or a stable internet connection don't function for a nurse completing an incident report between patient rooms or a warehouse associate submitting a safety observation at the end of a shift. This is where mobile-first access becomes a structural requirement, not a convenience feature. Deskless employees who can't submit forms on a device they already carry — without a corporate email address and without a desk login — aren't underserved by bad tooling. They're excluded from the process entirely. Their data doesn't get collected. Their approvals don't get routed. Their submissions exist as workarounds: verbal handoffs, paper slips, text messages to managers. Organizations that have digitized forms and training workflows on mobile report up to 50% faster new-hire onboarding, per Beekeeper case study data. The driver isn't the technology itself — it's closing the submission gap that existed when frontline employees had no accessible path to complete the form in the first place. For organizations managing globally distributed or multilingual workforces, inline language support enables consistent data collection without creating parallel form versions for different language groups. The form structure stays consistent; the language adapts to the employee. That's not a translation workaround — it's standardized operations at a global scale. ## The no-code automation layer that turns submissions into action Form creation is the straightforward part. The operational value comes from what happens after submission. No-code workflow automation handles recurring HR, IT, and facilities requests — PTO approvals, shift swap submissions, expense reports, help desk tickets — without developer involvement. HR administrators configure the routing logic themselves. If a PTO request from an employee in a specific location requires a supervisor approval and a payroll notification, that chain is configured in the platform without writing a line of code. This distinction matters most for time-sensitive approval chains. For [teams managing shifts and scheduling workflows](/solutions/shifts-schedules), a shift swap request that routes automatically to the covering employee and the schedule manager resolves in minutes rather than days. The same logic applies to expense submissions, safety incident reports, and onboarding checklists. The routing is configured once. Every subsequent submission follows it automatically. For [workforce management teams](/solutions/workforce-management) overseeing field-based or distributed operations, the no-code layer makes it possible to standardize submission processes across departments without requiring each department to build its own tooling. Templates exist for the most common request types. Routing logic is configurable by administrators. Governance is centralized by default. The aggregate effect — across a workforce where PTO requests, shift swaps, expense reports, and incident submissions happen daily — is a measurable reduction in the manual handoff work that currently generates delay and error across operations. ## What structured data management actually enables downstream Every form submission populates a searchable tracker with response data and identifying information. Admins can filter, sort, import, export, and share tracker data directly. In isolation, that sounds like standard SaaS tooling. The operational value comes from what the tracker enables downstream. For HR teams running onboarding programs, submission data from day-one forms, equipment requests, and policy acknowledgments flows into a single view rather than across three systems. Completion status is visible without chasing individuals. Follow-ups can be triggered automatically for submissions that go incomplete. For compliance teams managing documentation requirements across departments or locations, a unified tracker with consistent submission records is the difference between an audit that requires three weeks of data collection and one that requires three hours. The data was always being collected — the problem was that it lived in six places with six different access models. For operations teams managing field-based work, form data that feeds directly into the broader workforce management stack — connected to scheduling, time tracking, and task management — stops functioning as a reporting burden and starts functioning as operational input. ## What to settle before you deploy Most form digitization projects stall not at the technology level but at the process definition level. Four questions, answered before launch, prevent the most common implementation delays. **Which forms have the highest submission volume?** Start with the highest-frequency requests — PTO, expenses, incident reports — to capture the most immediate efficiency gain. Low-volume compliance forms can follow in a second phase. **Who are the approvers and what are the routing rules?** No-code automation is only as effective as the routing logic you configure. Define the approval chain for each form category before configuring automation, not after. Automated routing configured around an ambiguous approval chain just routes ambiguity faster. **Which employees need mobile access?** For organizations with frontline or field workers, identifying access requirements early ensures the mobile experience is configured correctly from the start. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how operations teams are structuring digital tool rollouts for mixed desk and deskless workforces — including which form categories to prioritize for frontline deployment. **What does 90-day success look like?** Define baselines before launch: current submission volume, average processing time, error rate per form type. The goal is not a technology deployment — it's a measurable reduction in manual operations overhead. Sixty days in, the question shouldn't be "are employees using it?" It should be "by how much has processing time dropped?" ## The structural shift behind the efficiency numbers Organizations will always need forms. The question is whether those forms impose unnecessary friction on the people completing them and unnecessary overhead on the teams acting on the data. The research is consistent. Employees are already spending 2.5 hours daily navigating information rather than acting on it, per IDC. Forms that are hard to find, slow to process, or disconnected from downstream workflows compound that burden. Ninety-one percent of organizations have an intranet, per Social Edge Consulting, and nearly a third of employees never use it — which means forms that live only in that system are already failing a large share of the workforce before a single submission happens. Platform-embedded digital forms change the equation at the structural level. The form is where the employee already is. The approval routes to who needs to act on it. The data populates the tracker without a manual entry step. The 80% of the global workforce that is deskless, per Emergence Capital, submits from the field without a desk or a corporate email address. The distinction that matters isn't between paper and digital. It's between forms that create data artifacts and forms that create decisions — and between a tool employees occasionally navigate to and one that's already part of their daily workflow. --- # The Benefits of Running Anonymous Employee Surveys **Author:** Anna Carriveau **Published:** 2019-02-07 **Category:** company-culture As a manager or business leader, it can be difficult to correctly assess your employee engagement levels. Concerns about putting their best face forward can make employees appear to be happy and enthusiastic, even if their genuine opinion are further from the truth. Employees who are genuinely invested and engaged naturally work harder, are more […] ## The Benefits of Running Anonymous Employee Surveys As a manager or business leader, it can be difficult to correctly assess your [employee engagement](/solutions/employee-engagement) levels. Concerns about putting their best face forward can make employees appear to be happy and enthusiastic, even if their genuine opinions are further from the truth. Employees who are genuinely invested and engaged naturally work harder, are more creative, and are happier. So how does a manager help employees feel safe and encourage them to offer real and regular feedback? By providing them with anonymous employee surveys. By accurately assessing employee feedback, you can truly begin to build a high-performing team. Below are just a few of the reasons why successful companies need to offer anonymous employee engagement surveys to their employees. ### Receive Honest Feedback Anonymous employee surveys give employees a chance to offer real feedback without having to worry about negative repercussions. These surveys give a voice to employees who may be hesitant to go against the perceived majority. Anonymous surveys help managers get a clear picture of how their teams operate, and can help them find patterns, fix problems, and communicate more openly. This results in a positive work environment where employees feel understood, engaged, and appreciated. Employees who feel their voice is heard at work are 4.6x more likely to feel empowered to perform their best work — making honest feedback channels one of the highest-leverage investments a manager can make. ### Inspire More Engagement Anonymous employee surveys are also a valuable tool to boost employee engagement. They can help employees feel appreciated and heard by their managers and their company. This also contributes to a deeper trust and creates stronger ties within the organization. Surveys can also indirectly promote engagement as well. Managers can correct concerns or resolve potential problems that frustrate or discourage employees. Helping employees analyze and learn from their recent outcomes can encourage them to apply the lessons they've learned and continue to work hard in the future. Survey frequency matters here: annual engagement surveys miss real-time sentiment shifts, while quarterly or monthly pulse surveys — sometimes called employee engagement questionnaires — allow managers to catch disengagement before it becomes attrition. Anonymous pulse surveys work best when paired with a closed-loop action plan; employees who see visible follow-through on survey results report significantly higher trust in leadership than those who don't. ### Improve Accountability With anonymous employee surveys, you can create accountability for both the managers and employees. These surveys give employees a safe place to share their concerns, ideas, thoughts, and opinions, while removing excuses that lead to resentment. When employees have a place to share, they become accountable for their communication and are responsible for making their needs known. Similarly, surveys foster accountability for employers. When employers are aware of problems and opinions, they are responsible to respond and reciprocate to those issues however they consider appropriate. This dual accountability creates a culture of transparency, honesty, and respect within an organization. For a broader look at how accountability connects to [performance management](/solutions/performance-management), the dynamics are closely related. ### Make Informed Decisions Anonymous employee surveys can also be used to make informed and unbiased decisions. For example, employees can vote on a new company policy without worrying about social pressure playing into their answers. Anonymous surveys in this way help both leaders and everyday employees work with confidence, overcome potential bias, and make more accurate and informed decisions. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) explores how data-driven feedback loops are reshaping how HR teams approach workforce decisions. ### Boost Employee Retention While this is a somewhat indirect result, it is also ultimately one of the long-term goals of all anonymous employee surveys. Surveys help employees feel safe and understood and give them a platform to honestly voice their opinions. As a direct result, their engagement will improve and company culture as a whole will become stronger and more supportive. And as companies improve their engagement and corporate environment, employees will naturally want to stay. Retention has a direct financial dimension: replacing a single frontline employee costs between $4,400 and $15,000 on average, making retention-driving survey programs a measurable ROI lever — not just a culture initiative. Improved retention also promotes higher referral rates and a stronger sense of brand loyalty from employees, helping organizations become more productive, profitable, creative, and innovative throughout their industry. ### Reaching Every Employee — Including Frontline and Deskless Workers One of the most overlooked gaps in traditional survey programs is frontline and deskless worker inclusion. Frontline and deskless workers are disproportionately underrepresented in traditional survey programs because they lack corporate email or regular desktop access, creating a systematic blind spot in engagement data. Per Emergence Capital, 80% of the global workforce is deskless — meaning the majority of employees in industries like retail, hospitality, and nonprofit services may never be reached by a standard email-based survey. An employee experience platform that delivers surveys through a mobile app closes this gap, ensuring engagement data reflects the full workforce rather than only office-based staff. For organizations in customer-facing industries, this distinction is especially significant — see how engagement challenges play out in [retail](/industries/retail) and [hospitality](/industries/hospitality) contexts. ### MangoApps Anonymous employee surveys provide coworkers a platform to fearlessly provide honest input. This can be about anything from proposed business policies to opinions about pineapple on pizza. Surveys provide straightforward and accurate information, promoting increased clarity, improved understanding, and transparency. At MangoApps, we're dedicated to helping businesses foster long-term success through innovative communication and collaboration technology. Our employee engagement software surfaces survey results in manager dashboards and enables follow-up communications within the same platform — closing the loop between data collection and visible action. To learn more about how MangoApps can improve your organization, contact us or schedule your own personalized demo today. --- ## Frequently Asked Questions About Anonymous Employee Surveys ### How Do You Design an Effective Employee Engagement Survey? Effective employee engagement questionnaires balance quantitative rating scales with open-ended questions that surface qualitative themes. A well-designed survey covers four core areas: role clarity, manager relationship quality, growth opportunities, and sense of belonging. Keep surveys short — 10 to 15 questions for a pulse survey, no more than 30 for a comprehensive annual review — to protect completion rates. Avoid leading questions and ensure the anonymity mechanism is clearly communicated before employees begin. For context on how learning and development intersects with engagement survey design, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ### What Questions Should You Include in an Anonymous Employee Survey? Strong employee engagement survey questions fall into several categories: satisfaction ("How satisfied are you with your current role?"), advocacy ("Would you recommend this company as a great place to work?"), enablement ("Do you have the tools and resources you need to do your job well?"), and manager effectiveness ("Does your manager recognize your contributions?"). Open-ended prompts like "What is one thing we could change to improve your experience?" consistently generate the most actionable responses. Reviewing findings from sources like [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) can help benchmark your results against global norms. ### How Should Leaders Act on Employee Survey Results? Collecting survey data without visible follow-through is one of the fastest ways to erode employee trust. After each survey cycle, leaders should share a summary of findings with the full team, identify two or three specific actions the organization will take in response, assign owners and timelines to each action, and communicate progress at the next survey cycle. This closed-loop approach — survey, action, visible outcome — is what transforms an employee engagement survey from a data-collection exercise into a genuine driver of culture change. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) outlines how leading organizations are structuring these feedback loops at scale. --- # How the MangoApps Departments Boosts Connectivity and Engagement **Author:** Anjali **Published:** 2019-02-05 **Category:** modules-features The success or failure of any organization today depends heavily on its digital abilities to adapt, connect, communicate and collaborate. Knowing that these factors are essential, companies often invest in email, social media, video conferencing and all kinds of other independent digital tools, without implementing a centralized digital workplace strategy. While each of these programs […] # How MangoApps Departments Boosts Connectivity and Engagement Per IDC, employees spend an average of 2.5 hours every day searching for information they need to do their jobs. That number has not improved as organizations have added more collaboration tools — in many cases, it has gotten worse. The problem is not a shortage of platforms. It is that most tools require a corporate email address, a VPN connection, or a desktop login that a significant share of any workforce simply does not have. MangoApps Departments addresses the root cause: disconnected tools create disconnected teams. The module gives every department a unified hub for files, announcements, wikis, and conversations — without requiring IT provisioning, corporate email, or VPN access. This article covers how it works, what distinguishes a department hub built for frontline conditions from one built only for desk workers, and what the first 90 days of deployment should actually produce. ## Why most department intranets fail the workers they're supposed to reach Per Emergence Capital, 80% of the global workforce is deskless — working in healthcare, retail, logistics, manufacturing, and other settings where a desktop workstation is not part of the job. Enterprise intranet tools were largely designed without them in mind. Per Social Edge Consulting, 91% of organizations operate an intranet, but nearly a third of employees never log in, and only 13% use it daily. Per SWOOP Analytics, the average employee spends six minutes per day on intranet tools. Those numbers do not describe resistance to technology. They describe tools built for conditions most employees are not in. A platform requiring a corporate email address to enroll excludes every frontline worker without one. A platform requiring VPN access does not function on a personal phone between shifts. The connectivity gap in most department communication is not cultural — it is architectural. Closing it requires a hub that works under the conditions employees are actually in, not the conditions of the office-based minority the platform was originally designed for. ## What a purpose-built department hub requires Closing the connectivity gap at the department level requires more than moving files to a shared drive. Several conditions determine whether a department hub actually reaches the people it is supposed to — and whether it stays useful after the first month. **No-email enrollment.** Workers without a corporate email address must be able to join via QR code or SMS link in under a minute. This is not a secondary feature — it is the condition under which the majority of most workforces can participate at all. Deployment that requires IT to provision accounts for each frontline worker will not scale, and in many organizations it will not happen at all. **Mobile-first design.** Content must be optimized for personal iOS and Android devices, not merely readable on them. That means layouts built for a phone screen, not pinch-and-zoom versions of a desktop interface. For workers checking a schedule or a policy update between tasks, the difference between a usable interface and a frustrating one determines whether the hub becomes a habit or a one-time visit. **Role-based permissions without IT involvement.** Department admins need to control who sees what — module by module — without opening a support ticket. For organizations in healthcare, financial services, or other regulated industries, this also means enterprise-grade security: SAML 2.0, single sign-on, and role synchronization from an existing HRIS so that permissions stay accurate as the organization changes. **Content architecture that can stay current.** The six-minute daily average from SWOOP Analytics reflects what happens when employees learn the intranet cannot be trusted — they stop visiting and do not come back. A department hub needs distributed admin ownership, version control for shared documents, and a low-friction editing process to prevent the information decay that undermines adoption over time. MangoApps Departments meets each of these conditions. Frontline workers connect via the [employee app](/solutions/employee-app) on personal devices with no corporate email required. Enrollment takes under a minute via QR code or SMS link. Role-based permissions sync automatically from an organization's HRIS. Department admins configure access at the module level without IT involvement. ## How a department hub functions across a team Each department in MangoApps gets a dedicated space configured for the team that uses it: specific modules, defined permissions, and content organized for daily work rather than companywide broadcasting. The consolidation effect is direct — employees find files, announcements, wikis, calendars, and colleague profiles in one place instead of switching between four or five disconnected systems. File management supports version control through check-in and check-out, preventing conflicts when multiple team members update the same document. Integration with Microsoft 365 allows teams to co-edit documents directly in the browser. Department-specific wikis let teams build and maintain shared knowledge without relying on email threads that become the accidental source of record. Recognition works better when it is specific and timely. MangoApps Departments lets team members and managers recognize colleagues in the moment — publicly, within the department or across the company — with configurable reward structures admins can tailor to the behaviors their team needs to reinforce. Embedded forms and polls give managers a lightweight mechanism for checking policy comprehension or gauging team sentiment before a change goes live, rather than waiting for a quarterly survey cycle. For organizations in regulated industries, the American College of Radiology's deployment — documented in the [case study on enabling easy communication at ACR](/resources/case-study-american-college-radiology) — illustrates how a security architecture built on SAML 2.0, HRIS-synced roles, and granular permissions can coexist with a user experience employees return to daily. ## What to measure in the first 90 days Deployment is only useful if it produces a measurable change. The metrics that matter in the first 90 days are different from the aggregate engagement statistics most analytics platforms surface by default — and treating the wrong metric as the primary signal is how organizations conclude a deployment failed when it was actually working for one part of the workforce and invisible to another. **Login frequency by user type.** Separate desk-based and frontline logins in reporting. A single aggregate rate hides the gap a department hub is supposed to close. **Enrollment completion for non-email workers.** Track what percentage of eligible frontline workers completed QR code or SMS enrollment within the first two weeks. A low rate is an early signal that deployment communications failed, not that the technology did. **Behavioral engagement over passive views.** Page views do not distinguish between an employee who read a policy update and one who scrolled past it. Comments, acknowledgments, and form completions are the signals that information was processed rather than merely loaded. **Pulse survey response rates.** Forms and surveys embedded directly in department communications — rather than sent as standalone emails — consistently produce higher response rates. Per [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), organizations that collect and act on feedback continuously outperform those that collect it in annual cycles. Contextual pulse surveys embedded in the relevant communication produce actionable signals; standalone survey emails produce aggregated noise that arrives too late to act on. ## Getting started: what deployment actually looks like The question most organizations ask after they understand the value case is: what does this actually require to deploy? The technical setup is lighter than most enterprise software implementations. Department pages are configurable by admins without IT involvement. SAML and SSO integration follows standard protocols. HRIS sync is configured once and maintained automatically as the organization changes. The more operationally significant work is enrollment and content priming. For desk-based workers with SSO configured, enrollment is automatic. For frontline workers, QR code or SMS enrollment campaigns are the most effective mechanism — a worker who scans a code and finds relevant content immediately is far more likely to return than one who completes a multi-step account creation process and arrives at an empty page. Content priming before launch is consistently underestimated. The highest-impact content to have in place on day one: the most frequently searched reference documents (SOPs, benefits summaries, org charts), a pinned welcome announcement explaining what the hub is for, and at least one piece of interactive content — a poll, a form, or a feedback channel — that signals the space is two-way rather than a read-only noticeboard. The retention case is direct. Replacing a single frontline employee costs between $4,400 and $15,000 in direct recruiting and onboarding costs, before accounting for lost institutional knowledge. A department hub that reaches frontline workers — not just desk-based employees — is a retention investment with a measurable denominator. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents how organizations across industries are structuring department-level communication frameworks and what the transition from legacy tools typically looks like over the first six months. ## What success looks like at six months At six months, a well-deployed department hub should demonstrate three things: frontline enrollment above 70% of eligible workers, weekly active user rates meaningfully above the six-minute daily average that defines most legacy intranet deployments, and at least one documented operational outcome — a policy acknowledgment rate, an incident report completion rate, a measurable reduction in information search time — that has been shared with leadership. Organizations that consistently hit these benchmarks share two practices: they assign department admins with real content ownership from week one, and they extend enrollment to frontline workers at launch rather than treating them as a second phase. The Departments module provides the architecture. Building the discipline of keeping it current and acting on what it surfaces belongs to the teams that use it. --- # Why Investing In Engagement Is Always A Good Idea **Author:** Anna Carriveau **Published:** 2019-01-29 **Category:** employee-engagement Engaging and investing in your employees is now more important than ever. Engaged employees often outperform their peers.  Regardless of your company’s size or industry, honest employee engagement always leads to increased productivity. When connected, employees are more enthusiastic about their work and perform their job responsibilities better. While genuine employee engagement can be hard […] ## Why Investing In Engagement Is Always A Good Idea Engaging and investing in your employees is now more important than ever. Engaged employees often outperform their peers. Regardless of your company's size or industry, honest employee engagement always leads to increased productivity. When connected, employees are more enthusiastic about their work and perform their job responsibilities better. The sections below explain the core business case for engagement investment — and close with concrete steps for measuring and implementing an engagement strategy so you don't have to search elsewhere for next steps. **While genuine employee engagement can be hard to achieve, here are a few reasons why investing in engagement is always a good idea:** ## Increased Productivity While monetary incentives can temporarily motivate employees, real productivity comes from an internal and emotional drive. Happiness naturally produces more productivity as employees become dedicated to their work and want to contribute to its success. Happiness at work can come from a variety of factors such as interest in the physical tasks, an adaptive or accommodating schedule, a healthy work-life balance, or a friendly and supportive team. At MangoApps, we regularly see engagement and productivity gains as our clients have the freedom to work successfully and collaborate with coworkers and peers across their organizations. One often-overlooked drag on productivity: employees spend an average of 2.5 hours per day searching for information, per IDC. Employees also lose over four hours per week switching between disconnected systems — eroding the productivity gains that employee engagement programs are designed to create. A unified [employee experience platform](/solutions/employee-engagement) reduces that friction directly. ## Enhanced Profitability Companies with a more engaged workforce are on average 21% more profitable than similar organizations with lower levels of engagement. Engaged employees are more productive both in their work tasks and in their interactions with customers and clients. As productivity increases among employees, profitability naturally follows. Investing in engagement also increases profitability by reducing recruiting and hiring expenses. Replacing a frontline employee costs between $4,400 and $15,000, making retention through engagement a direct cost-avoidance strategy, not just a culture initiative. Helping employees feel understood and heard through regular and intuitive feedback — including structured employee engagement surveys and employee engagement questionnaires — allows you to identify the warning signs of decreasing employee engagement early on. ## Lower Maintenance Costs A large part of employee engagement is helping employees enjoy a better work-life balance. When employees can take care of their personal needs freely they don't have distractions during the workday. This helps them stay productive, invested, and engaged. One way MangoApps helps companies improve this balance is by drastically increasing remote work possibilities. MangoApps removes the worry of communication, reporting, and commitment concerns through its collaboration and communication driven technology. Remote work is a great solution for employers too. A partially or entirely remote work environment can provide significant savings in maintenance costs. With remote work, employers don't have to invest heavily in office spaces or office supplies. These expenses can be redistributed throughout other areas of the company. ## Improved Product Quality Engaged employees are invested in their company and committed to performing well. Not only do they work harder, but they often go above and beyond typical job duties. Better products and innovative ideas almost always originate from engaged employees. Organizations today have all kinds of teams dedicated to performing and perfecting different aspects and services of a company. Investing in engagement creates teams dedicated to helping each other to stay motivated, handle pressure and deliver quality output together. For a deeper look at how learning investments compound these gains, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ## Increased Customer Satisfaction For any business to survive, customer satisfaction is essential. Employees are your first customer and engaging and satisfying them throughout their experience will create authentic brand ambassadors. Engaged employees are more resilient to dissatisfied customers and have a genuine interest in their happiness. They know the value of their company's products and services and show honest commitment and dedication to customers. Empowering and engaging your employees is the key to successful customer-facing service decisions and to effectively understanding and utilizing customer feedback, suggestions, and opinions. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) explores how leading organizations are structuring employee experience to drive customer outcomes. ## Reaching the Frontline: Engagement Beyond the Desk Most engagement investments are designed for desk-based employees — yet 80% of the global workforce is deskless, per Emergence Capital. Disengaged frontline workers, who make up the majority of the global workforce, are disproportionately affected by poor communication tools. Meanwhile, per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use intranet tools daily — averaging just six minutes per day, per SWOOP Analytics. Reaching shift workers, field teams, and non-desk employees requires a different approach: a branded mobile app that requires no corporate email address or VPN. A company-branded employee app is also a tangible signal of investment in employees, connecting the white-label mobile experience directly to the engagement outcomes described throughout this article. OU Health achieved 87% workforce engagement within months of launching a branded employee app. British Airways reported a 30-point increase in engagement score after deploying an employee experience platform. For retail and hospitality contexts specifically, the [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) outlines how frontline-first communication translates to measurable engagement gains. ## Investing In Engagement With MangoApps Investing in engagement is a continual process and takes honest effort from managers and leaders within the industry. But when it is done right, employee engagement is one of the most effective tools a company has for promoting future success. Engaged employees are dedicated, happier, more productive, and most importantly, promote a positive and enriching environment that will attract and retain other well-performing employees. At MangoApps, we know that engagement starts with healthy communication and effective collaboration across teams, departments, branches, and organizations. Our employee experience platform brings together employee engagement software, mobile access for frontline teams, and AI-personalized content feeds that reduce information overload and sustain engagement over time. Contact us today to learn more about how MangoApps drives employee productivity — or explore the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) to benchmark your current approach. ## How Do I Measure Employee Engagement? Measuring employee engagement starts with a combination of quantitative and qualitative signals. Employee engagement surveys and employee engagement questionnaires are the most common structured tools — typically deployed quarterly or annually — and should track dimensions like role clarity, manager relationship quality, recognition frequency, and access to information. Pulse surveys (shorter, more frequent check-ins) complement annual surveys by surfacing real-time shifts in sentiment. Platform analytics — login rates, content interaction, peer recognition activity — provide behavioral data that self-reported surveys can miss. For context on what benchmark scores look like across industries, [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace) is a useful reference point. ## What Are the Most Common Barriers to Employee Engagement? The most common barriers to employee engagement fall into three categories. First, communication gaps: when employees — especially frontline and deskless workers — lack reliable access to company information, they disengage quickly. Second, tool fragmentation: employees who spend 2.5 hours per day searching for information (per IDC) or lose four-plus hours per week switching between disconnected systems are structurally prevented from feeling engaged, regardless of culture initiatives. Third, one-size-fits-all programs: training and employee engagement initiatives designed exclusively for desk workers leave the 80% deskless majority (per Emergence Capital) without meaningful investment. Addressing these barriers requires both cultural commitment and the right employee engagement software infrastructure. The [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides independent context on how platform selection affects these outcomes. ## What Tools Support an Employee Engagement Strategy? An effective employee engagement strategy typically relies on a layered set of tools: an employee experience platform that serves as a single destination for communications, recognition, and task management; employee engagement software with built-in survey and feedback capabilities; a mobile-first app for frontline and deskless employees who lack desktop access; and learning and development integrations that connect employee engagement training and employee engagement courses directly to daily workflows rather than isolating them in a separate LMS. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines how organizations are consolidating these tools to reduce switching costs and improve adoption rates. --- # How To Run A Successful Business With Remote Employees **Author:** Anna Carriveau **Published:** 2019-01-24 **Category:** company-collaboration Remote employees are becoming part of the norm with many successful businesses. While the idea of creating a remote work strategy might sound scary, it’s almost essential in today’s market. In fact, recent studies have shown that post-pandemic, nearly 65% of employees will want to work remotely full-time. This change has been growing in every […] ## How To Run A Successful Business With Remote Employees Remote employees are becoming part of the norm with many successful businesses. While the idea of creating a remote work strategy might sound daunting, it is almost essential in today's market. Post-pandemic, nearly 65% of employees want to work remotely full-time — and that shift is accelerating across every sector. Remote work benefits both employers and employees when you know how to implement and manage it correctly. The five strategies below give you a concrete framework to do exactly that, from hiring and onboarding through daily operations and long-term employee engagement. ## 5 Ways To Run A Successful Business With Remote Employees ### #1: Encourage Employee Autonomy If you are going to promote a remote work environment, your employees need a trustworthy sense of employee autonomy. A culture of autonomy should be instilled in employees from orientation onward. This ensures that both new hires and existing workers develop characteristics of ownership, innovation, freedom, transparency, and respect. When businesses incorporate a sense of autonomy, transitioning into remote opportunities becomes natural. Without these attributes, employees will struggle to stay engaged and productive without supervision. When workers feel invested in their work, they eagerly accomplish tasks from anywhere. Building that culture starts before day one. Organizations that embed [employee engagement](/solutions/employee-engagement) practices into onboarding — rather than treating them as a separate initiative — report faster ramp times and lower early attrition among distributed hires. ### #2: Keep Remote Work In Mind When Hiring When integrating a successful business with remote employees, it is important to remember that their assignments and experiences will differ greatly from in-office workers. Employees who work in a traditional office are regularly available to participate in training programs and receive mentorship with their daily activities. Employers can guide these workers more easily in a traditional environment. When you hire remote workers, select employees with a self-starting attitude. Remote employees should handle their responsibilities with minimal guidance and a greater sense of personal ownership. When conducting interviews for remote roles, assess out-of-office potential through sample tests or small assignments that mimic the position's typical responsibilities. One often-overlooked segment: frontline and field workers who do not have a company email address or VPN access. Per 80% of the global workforce being deskless (per Emergence Capital), a meaningful share of your remote hires may need app-based, no-email access to shifts, forms, training, and HR self-service through a single mobile app — eliminating desk access as a prerequisite for engagement. Organizations that account for this during hiring and onboarding see up to 50% faster new-hire onboarding when training is mobile-accessible and digitized. For a deeper look at how learning fits into daily workflows rather than sitting in a separate LMS, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ### #3: Incorporate The Right Tools Many of today's successful businesses use technology solutions to establish an effective remote environment — collaboration tools, project management platforms, communication channels, and more. Technology can be the key differentiator for your business in empowering remote employees. Collaboration technology allows companies to keep everyone at the same pace despite differences in time zones, regions, and availability. However, the tool category matters less than consolidation. Fragmented tooling — employees navigating 6–8 disconnected systems daily — is a primary driver of remote worker disengagement, not lack of supervision. Employees already spend an average of 2.5 hours per day searching for information (per IDC); adding more siloed apps compounds that cost. A unified platform that handles communication, task management, and employee engagement training in one place reduces context-switching and is a measurable productivity lever for distributed teams. AI-curated content personalization — surfacing role- and location-specific updates — is now a baseline expectation for remote employee platforms, not a premium feature. Automating routine remote workflows such as shift swapping, PTO requests, and task assignments via no-code tools also reduces manager overhead and accelerates onboarding for distributed hires. For context on how leading platforms are evaluated on these criteria, the [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides an independent benchmark. ### #4: Utilize Metrics and Analysis Collaboration technology makes it easier for managers and supervisors to track work metrics and project developments and stay current on employees everywhere. Digital tools measure team and individual productivity for both in-office and remote employees. Metrics can be tracked at every level — from team performance to task assessment to regional results. Simple, straightforward metrics help managers stay on top of project activity and gain a better understanding of how remote team members are performing. Metrics also keep supervisors aware of deviations or unusual behavior, letting them resolve conflicts, address questions, or provide support as soon as a need arises. A useful benchmark: 91% of organizations operate an intranet (per Social Edge Consulting), yet only 13% of employees use one daily and nearly a third never log in at all (per Social Edge Consulting). Average daily intranet usage sits at just six minutes (per SWOOP Analytics). These numbers signal that having a tool is not enough — the metrics you track must include adoption and engagement rates, not just task completion. Connecting metrics to a structured [performance management](/solutions/performance-management) framework closes the loop between activity data and meaningful outcomes. ### #5: Create Bonding Opportunities Just because your team is remote does not mean you have to ignore team activities. If possible, arrange for teams to physically meet at least once a year, giving members the opportunity to get to know each other personally. Additionally, organize online events like multiplayer games and contests where employees around the globe can play and compete with each other. This makes the whole team feel more united and less separated from the common goal of business success. You can also keep teams connected through a social intranet that gives employees a space to share stories and experiences and interact regularly. Technology makes it straightforward to build a successful business with remote employees by helping remote teams work, collaborate, and communicate through intuitive social intranets. For a real-world example of how one organization connected a large distributed workforce, the [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study) case study illustrates what strong remote and frontline rollout looks like in practice. ## What Does a Successful Remote Work Rollout Actually Look Like? Implementation timelines and adoption benchmarks matter as much as strategy. A large enterprise deployment benchmark shows 90% frontline adoption within the first six months is achievable when rollout includes mobile-first access, structured onboarding, and clear SOPs for remote operations. Common failure modes include: launching tools without defined workflows, skipping employee engagement surveys to baseline sentiment before and after rollout, and treating remote work policy as a one-time document rather than a living operating standard. Budget considerations should account for platform consolidation savings — replacing 6–8 point tools with one platform typically offsets licensing costs — as well as manager time recovered from manual coordination. For a forward-looking view of what HR and operations leaders are prioritizing, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) and the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) both address remote and hybrid workforce planning in detail. ## What If My Team Is Only Partially Remote? Hybrid teams — where some employees are in-office and others are distributed — introduce a specific coordination challenge: in-office workers default to informal communication channels that remote colleagues cannot access, creating an information gap that erodes employee engagement over time. The fix is not more meetings; it is ensuring that every workflow, approval, and update is documented and accessible asynchronously. Establishing clear SOPs for operations — who owns what, how decisions are escalated, where information lives — is the structural foundation that makes hybrid work equitable rather than accidental. ## How Do I Measure the ROI of Remote Work? ROI measurement for remote work programs typically covers four areas: productivity (output per employee, task completion rates), retention (turnover cost avoided), real estate savings (reduced office footprint), and engagement (employee engagement survey scores over time). Employee engagement questionnaires administered at 30, 60, and 90 days post-rollout give you a baseline and a trend line. Pair those with platform adoption metrics — daily active users, content interaction rates, workflow completion rates — and you have a defensible business case. The [Break The Annual Review Cycle: The Executive's Guide To Creating A Culture Of Continuous Employee Development](/resources/break-the-annual-review-cycle) resource offers a practical framework for connecting engagement data to development outcomes in distributed teams. ## MangoApps With the right strategies and consistent execution, building and managing a remote workforce is achievable for organizations of any size. At MangoApps, we help some of the world's most promising enterprises, start-ups, and high-performance teams create world-class remote teams. If you are interested in learning more about creating a successful business with remote employees, contact us for a free demo today. --- # Write a Review of MangoApps **Author:** Luke Walton **Published:** 2019-01-23 **Category:** customer-success-stories At MangoApps, we’re dedicated to delivering the most comprehensive employee communications and engagement platform for the digital workplace. Your feedback helps us achieve that goal. We invite you to share your thoughts on MangoApps by writing a review. Your insights not only help us improve but also guide potential users in their decision-making process. Why […] # MangoApps Review: What Real Customers Experience (and How to Share Yours) Enterprise software buying is a peer-dependent process. Per G2 and TrustRadius buyer behavior research, 92% of B2B software buyers consult peer reviews before requesting a demo — and products with 50+ reviews receive 4.6x more buyer traffic than those with fewer than 10. Every review a MangoApps customer writes closes a specific information gap for a peer who's trying to make the same evaluation decision you already made. This page exists for two audiences: current customers who want to share their experience, and prospective buyers who want to understand what actual deployments look like. The last section covers exactly where to submit a review and what to write. The sections before it cover what MangoApps actually does, where it's been deployed, and what independent signals say about adoption patterns in practice. ## What the review data is actually measuring Most people think of peer reviews as reputation management — a way to accumulate stars. They're actually a search and evaluation mechanism. Review platforms increasingly weight recency in their category rankings. Per G2 and Capterra's ranking methodology, platforms with fewer than 12 months of fresh reviews lose category positioning — which means a review submitted today directly affects how easily a peer can find MangoApps during their evaluation in six months. The content of reviews matters as much as the count. Enterprise buyers don't read summary scores; they search by use case. A manufacturing operations director evaluating communications platforms for a 1,500-person factory wants to find a review from someone managing a similar workforce — not a five-star generic testimonial. A healthcare HR leader evaluating communications tools for nursing staff wants to see something that describes adoption in a clinical, shift-based environment. The reviews that produce real buyer influence answer specific questions: what specifically changed after deployment? Which team adopted first? How long did adoption actually take? What was harder than expected? Those details are only available from people who've been through it. That's the review worth writing. Peer review sites are cited as the primary research channel by enterprise software buyers before requesting a demo, making third-party reviews a direct pipeline influence — not just a reputation signal (per TrustRadius and Gartner Peer Insights buyer behavior research). That reframe matters: a review is not a favor to a vendor. It's information infrastructure for the next buyer. ## What MangoApps actually does — and where it's deployed MangoApps is a unified employee communications and operations platform. It consolidates intranet, messaging, task management, surveys, scheduling, and workforce management into one interface rather than requiring separate tools for each function. The deployment context matters here. Per Emergence Capital, 80% of the global workforce is deskless — working without a corporate email address or company laptop. Most enterprise communication platforms are designed for the 20% who have both. MangoApps' mobile-first architecture targets the full population: frontline workers in manufacturing, retail, healthcare, and logistics who need the same communications access as their office-based colleagues without requiring a desktop. The numbers that motivate that architecture: per IDC, employees spend 2.5 hours per day searching for information. Per Social Edge Consulting, 91% of organizations operate an intranet, but only 13% of employees use it daily, and nearly a third never log in at all. Per SWOOP Analytics, the average daily intranet session is six minutes. MangoApps is built to close that gap — to make the platform worth opening daily, not just accessible in principle. Several capabilities tend to stand out in customer deployments: **Mobile access without a corporate email address.** The [employee app](/solutions/employee-app) allows frontline workers to access communications, schedules, and documents from a personal device without corporate credentials. In retail and healthcare contexts specifically, this is the capability that drives frontline adoption in the first 60-90 days of deployment — because it removes the access barrier that keeps hourly and shift workers out of most enterprise platforms. **Platform consolidation.** Organizations that replaced five or more separate tools — intranet, chat, forms, LMS, scheduling — with MangoApps report measurable reductions in administrative overhead. The specific tools replaced vary by organization; the outcome (one place employees actually check) tends to be consistent across deployment types. **Workforce management in the same platform.** The [workforce management](/solutions/workforce-management) capability handles scheduling, shift management, and compliance documentation alongside communications. Pure-play intranet competitors don't offer this natively; for operations-heavy teams, it's the integration that makes MangoApps relevant to ops leaders, not just HR and IT. **Employee engagement surveys and questionnaires.** Built-in employee engagement survey and questionnaire tools can be deployed to specific teams, departments, or locations, with results feeding directly into dashboards — no export to a separate analytics tool required. HR teams managing engagement measurement alongside communications programs report fewer handoffs between systems and higher survey response rates when the survey surfaces in the same app employees use for scheduling and team updates. **Learning and development built in.** Native learning modules and employee engagement training resources reduce dependency on a separate LMS. When employees access learning content in the same platform they use for daily communications, completion rates tend to improve — the content is in context rather than behind a separate login. MangoApps carries a 98% customer retention rate and more than one million users. Both are vendor-reported figures, but a 98% retention rate is a harder metric to inflate than a user count — it reflects whether customers find enough ongoing value to keep renewing year over year. ## Why most review solicitations fail (and what makes a useful one) A review page that just says "share your experience" asks customers to write a blank check. Without structure, reviews tend to be generic. Without prompts, reviewers don't know what buyers are actually searching for. Without outcome examples, customers undersell what they experienced and underserve the next buyer. Competitors in the employee experience and intranet space — Unily, Simpplr, Staffbase — pair their review asks with named customer outcomes: specific engagement lift numbers, frontline adoption rates, measurable reductions in unplanned attrition. These numbers do two things simultaneously: they help current customers frame their own experience in comparable terms, and they give prospects a reason to trust the reviews they're reading. MangoApps' 98% retention rate and one million users are the right anchor numbers. But the review page's job is to help customers translate those aggregate signals into the specific, granular descriptions that drive buyer decisions. The goal isn't advocacy. It's specificity. ## What to write — specific prompts for MangoApps reviewers **Describe your workforce makeup.** How many employees do you have, and what percentage are frontline or deskless? MangoApps is purpose-built for mixed workforces. "We have 1,200 associates and 80 corporate staff, and both groups now use the same platform" gives the next buyer more actionable signal than "great for large teams." Workforce composition is the single most useful self-selection filter for a prospective buyer reading reviews. **Name the tools you replaced.** Which tools did MangoApps consolidate in your environment? Did you replace SharePoint, a standalone scheduling system, a paper-based forms process, or a combination? Specific consolidation stories are among the most useful review signals for buyers estimating total cost of ownership and implementation scope. **Describe a before-and-after outcome.** Daily active usage, employee engagement survey response rates, frontline communications compliance, unplanned attrition — any observable metric from before and after deployment gives your review something concrete. "We went from 13% daily intranet usage to over 60% within 90 days" is the kind of specificity that distinguishes a useful review from a star rating. Metric type doesn't matter as much as having one. **Address adoption and change management honestly.** Where did deployment go smoothly? Where was it slower than expected? First-time enterprise platform buyers trust reviews that include some friction — pure advocacy reads as marketing. An honest deployment timeline, including what required iteration, is more credible than an unqualified recommendation. It's also more useful. **Tie the experience to a specific use case.** Were you solving a frontline communication problem, a compliance documentation problem, or a platform fragmentation problem? Stating the original use case helps the next buyer locate the review most relevant to their situation. A healthcare HR leader and a retail district manager have different problems; knowing which one you were helps them decide whether your experience maps to theirs. MangoApps' preferred review platforms are **G2** and **Capterra**. Search for "MangoApps" on either platform and select "Write a Review." The process takes under 10 minutes. The hardest part is knowing where to start — these prompts are designed to solve that. ## What prospective buyers should know If you arrived at this page while researching MangoApps rather than reviewing it, the review-writing framing above gives you the most useful orientation. The capabilities that current customers write about — frontline mobile access, platform consolidation, workforce management integration, survey and learning tools — are the ones that differentiate in practice across the deployment types where MangoApps is most commonly chosen. For healthcare and regulated-industry evaluators, the [American College of Radiology case study](/resources/case-study-american-college-radiology) illustrates how MangoApps deploys in a credentialed, compliance-sensitive environment — a more specific reference than generic enterprise SaaS case study language. For buyers evaluating MangoApps as part of a broader internal communications investment, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents where leading organizations are investing in communications infrastructure and what benchmarks they're using to measure success — useful context for scoping what "good" looks like before entering a vendor evaluation. Three questions worth asking in a demo, based on what customers consistently highlight in independent reviews: 1. Show me the mobile onboarding flow for a frontline employee with a personal device and no corporate email — how long does it take from zero to first message sent? 2. Walk me through what happens when a manager publishes a shift change or policy update — how do you track which employees received it, and what's the audit trail for compliance documentation? 3. If we're replacing two or three point solutions, what does the integration path look like in the first 30 days — what does IT need to configure, and what can we start with before the full integration is complete? These questions surface the answers that distinguish platforms at the demo stage. MangoApps' responses to them, paired with peer reviews from customers in comparable deployment environments, give you the most complete picture available before a purchase decision. --- # Connect Your Workforce With MangoApps Employee Directory and Profiles **Author:** Anjali **Published:** 2019-01-07 **Category:** modules-features Most modern-day organizations have a highly trained and diverse workforce with a range of talents across the board. With such a wide array of skills and abilities, it can be almost impossible for an employee to know all of his colleagues, let alone all of their expertise and experience. Finding the right coworker to help […] # Connect Your Workforce With MangoApps Employee Directory and Profiles Most modern organizations have a highly trained and diverse workforce with a range of talents across the board. With such a wide array of skills and abilities, it can be almost impossible for an employee to know all of their colleagues, let alone all of their expertise and experience. Finding the right coworker to help with a task or recommending the right candidate for an internal opportunity can often feel like a guessing game — especially if your only tool is an ineffective or outdated employee directory. Employees spend an average of 2.5 hours per day searching for information, per IDC, and a stale directory only compounds that lost time. If your organization is trying to make do with an old and out-of-date directory, MangoApps' intelligent employee directory is an important first step toward helping employees collaborate with each other and access the internal talent they need. In this post, we'll look at the core directory features designed to connect your workforce — and answer the practical questions that follow: how setup works, how it integrates with your existing HR systems, and how it serves employees who don't sit at a desk. ## Advanced Employee Directory Research shows that knowing your teammates, being familiar with your coworkers, and feeling like you can share at work have an incredibly positive effect on employee engagement levels. With this in mind, the MangoApps advanced employee directory enables users to access coworker profiles from multiple views, helping employees better understand their company's organizational structure and their own relationship to each member of the organization. Providing several directory alternatives also helps employees stay organized and find who they're looking for faster, improving overall company understanding and communication. No matter which directory view you choose, every option allows employees to easily connect with the workforce. Employees can follow their colleagues and grow their network, reach out with private chat or a private message, or browse a team member's profile and portfolio information. Traditional static directories become stale quickly because updates depend on IT or HR admins rather than employees themselves, reducing trust and usage over time. MangoApps addresses this by putting profile ownership in employees' hands and supporting HRIS integration that automatically syncs employee roles, permissions, and profile data so directories stay accurate without manual admin updates. For organizations evaluating where MangoApps stands in the broader market, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent analysis of leading platforms including MangoApps. ## Interactive Organization Charts MangoApps interactive org charts are visual, intuitive, and well-defined, making it easy to understand hierarchy, improve communication, and orchestrate success. If configured, clicking on an org chart image leads employees directly to a person's profile page, instantly providing them with essential group, team, talent, and contact information. Org charts can also be easily exported to an Excel sheet, and any company's individual chart can be edited by specified network admins. Admins can assemble and update their charts by manually creating or inviting users, or by automatically syncing with an existing LDAP/Active Directory database. Role-based permissions and SAML 2.0/SSO controls govern who can view, edit, or export org chart data, ensuring that directory governance meets enterprise security requirements without creating friction for everyday users. ## Dynamic Employee Profiles MangoApps employee profiles include descriptive and relevant information including personal bios, company expertise, industry experience, personal interests and activities, and even multiple addresses and office locations. Employee profiles can also use look-ahead abilities to include office locations, job titles, or another field along with the user's name, making it easier to identify users with the same or similar names. Profiles are updated and managed by employees in real time, removing the chore from admin responsibilities and ensuring that information is always up-to-date. An individualized profile page acts like an internal resume, showcasing an employee's skills, experience, and accomplishments company-wide — helping connect your workforce and improving internal advancement opportunities. Real-time translation across 50+ languages in employee profiles and directory search enables global teams to find and connect with colleagues regardless of language, a critical capability for multinational organizations. For healthcare organizations managing credentialed staff across multiple sites, see how this plays out in practice at [industries/healthcare](/industries/healthcare). ## Detailed Search Filters The MangoApps Employee Directory includes a highly advanced search bar specifically designed to connect your workforce. Users can simply click on the bar and receive several advanced filter options, allowing them to narrow their search by location, department, organization, team, or another custom or predefined profile attribute. The search bar also comes with built-in conditional operators, letting employees further narrow down their search by matching results with multiple criteria. For frequently used searches, employees can save advanced search filters for easy future access. Beyond manual filtering, MangoApps surfaces relevant colleagues based on skills, projects, or role context — helping employees discover the right person even when they don't know exactly who they're looking for. This AI-assisted people discovery reduces the time spent navigating org structures and accelerates cross-functional collaboration. ## Frontline and Deskless Worker Access Per Emergence Capital, 80% of the global workforce is deskless. Yet employee directories that require a corporate email address exclude a significant share of frontline and deskless workers who lack one. MangoApps' [employee app](/solutions/employee-app) is designed to work on personal mobile devices without a corporate email, so frontline employees in healthcare, grocery, financial services, and other industries can access the full directory, find colleagues, and update their own profiles from anywhere. Per Social Edge Consulting, 91% of organizations operate an intranet — but nearly a third of employees never log in, and only 13% use intranet tools daily. A directory that frontline workers can actually reach on their phones, without IT-provisioned credentials, directly addresses the adoption gap that makes most intranet investments underperform. For context on how [industries/grocery](/industries/grocery) retailers have approached this challenge, the frontline access model is a consistent differentiator. ## Employee Activities and Achievements One of the most important aspects of employee engagement is positive reinforcement and recognition of successful employee performance. The MangoApps Rewards and Recognition module lets coworkers and supervisors alike publicly recognize employees for their hard work and accomplishments, helping them feel understood and appreciated. The profile page of any user can include a widget to showcase the most recent award received by the individual, enhancing their profile and telling a story of gratitude and personal achievement. Recognition visible on a profile page also contributes to retention. Replacing a single frontline employee costs between $4,400 and $15,000 on average — making the connection between recognition, engagement, and retention a measurable business case, not just a cultural aspiration. For a deeper look at how engagement data translates to workforce outcomes, the [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace) report provides current benchmarks. ## How Long Does Setup Take, and How Does Integration Work? Setup timelines vary by organization size and existing HR infrastructure, but MangoApps supports automated sync with LDAP/Active Directory and HRIS platforms, which means the directory can be pre-populated from existing systems rather than built from scratch. For most organizations, this eliminates the manual data-entry phase that delays directory launches. Admins configure role-based permissions, define custom profile fields, and set governance rules during onboarding — after which employees maintain their own profiles in real time. For organizations in regulated industries such as ambulatory care or financial services, [industries/ambulatory-care](/industries/ambulatory-care) and [industries/financial](/industries/financial) pages outline how MangoApps handles compliance-relevant access controls within the directory and broader platform. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading HR teams are structuring employee experience platform rollouts, including directory and profile modules, if you want a broader implementation framework. ## How Does MangoApps Compare to Alternatives? MangoApps competes in the intranet and employee experience platform category. Key differentiators for the directory and profiles module include: employee-owned profile updates (versus admin-dependent static directories), frontline mobile access without corporate email, HRIS auto-sync, multilingual profile support, and AI-assisted people discovery. MangoApps was [included in a leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) and [won Gold in Reworked's 2026 IMPACT Awards for Excellence](/articles/mangoapps-gold-reworked-2026-impact-awards), providing third-party validation of its position in the market. For organizations evaluating employee engagement software more broadly — including how directory and profile tools fit into a larger engagement strategy — the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) maps the landscape of tools and their measurable impact on workforce connection. ## The Bottom Line MangoApps Employee Directory and Profiles solve a specific, measurable problem: employees waste 2.5 hours per day searching for information (per IDC), and a directory that is stale, desktop-only, or admin-dependent makes that worse. The MangoApps approach — employee-owned profiles, HRIS auto-sync, mobile-first access for deskless workers, multilingual support, AI-assisted discovery, and org-chart-level governance — addresses each failure mode of traditional directories directly. If your organization is ready to move from a static list to a living, searchable, mobile-accessible people graph, the next step is a personalized demo where you can see the directory configured against your own org structure and integration environment. Contact us to schedule one, or explore the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) to see how workforce connection fits into broader operational priorities for the year ahead. --- # How To Build An Engaging Workplace **Author:** Anna Carriveau **Published:** 2019-01-03 **Category:** employee-engagement It’s a transformative time for businesses and organizations. Competition in the last decade has grown rapidly in almost every industry. This has increased a company’s need to provide new, interesting, and innovative products and services. So how are successful organizations supposed to keep up with increasing competition? The answer, is simply by bringing out the […] ## How To Build An Engaging Workplace Building an engaging workplace comes down to five concrete actions: hiring for cultural fit, setting clear expectations, communicating regularly, recognizing contributions, and empowering employees to grow. When organizations get these five things right, employees become personally invested in company success and consistently drive innovation. The sections below explain how to execute each strategy — including how to extend them to frontline, remote, and hybrid workers who are often left out of traditional employee engagement programs. **Here's everything you need to know about how to build an engaging workplace:** ## Find the Right Cultural Fit Tight schedules, strict budgets, and pressure from HR often results in hiring managers choosing the first candidate who matches the job description. But just because an employee can perform all of the essential duties doesn't mean they are a good fit for your company culture. Bringing on new employees that don't mesh with your company culture can cause serious damage towards long-lasting employee engagement. Hiring employees without considering their cultural fit will cause new hires to feel like they don't belong. As new employees change the culture over time, longstanding workers will feel out of place in an unfamiliar environment. As the dissatisfaction from either group grows, their desire to leave the company will increase. Being aware of the warning signs of decreasing employee engagement is critical. While every employee needs to fulfill the job requirements of a position, their cultural fit within the company and ability to contribute to an engaging workplace should be considered along with their technical skills. Replacing a disengaged employee who leaves costs between $4,400 and $15,000 per person, making cultural-fit hiring a directly quantifiable retention investment (industry report data cited on MangoApps mobile employee app product page). For industries with high frontline turnover — [retail](/industries/retail), hospitality, and BPO — this cost compounds quickly across large hourly workforces. ## Establish Clear Expectations There's nothing more frustrating than not knowing what is expected of you at work. When employees are left trying to guess what to do, it's almost impossible for them to be entirely engaged. Even if you want to participate and do well, you can't be committed if you don't know what to do. Once recruited, managers must make sure that employees have been properly trained and understand their responsibilities within the organization. Everyone processes information differently. Assuming your employees will think just like you is a huge recipe for misunderstanding and irritation. Check in with your employees on occasion to make sure you are on the same page. Employee engagement training and structured onboarding are especially important for frontline workers, who often lack access to the same information flows as desk-based colleagues. Per Emergence Capital, 80% of the global workforce is deskless — meaning the majority of employees may never see a policy update, role clarification, or training module unless it is delivered through a mobile-first channel. Organizations that invest in [employee engagement courses and training programs embedded in daily work](/articles/learning-and-development-strategy-embedded-in-daily-work) see measurably higher role clarity and participation rates. ## Keep in Regular Communication Neglected relationships will never lead to an engaging workplace. Communicate and collaborate with your employees often and encourage them to work with each other. However, it is important to remember that regularly communicating with your employees does not mean micromanaging. Take an interest in your employees' welfare and show that you care about their growth on a personal and a professional level. Today, businesses all over the world are using collaboration tools to encourage healthy and productive communication. Collaboration tools make communication easy, whether it's group and project-based conversations or personal instant messaging. They also offer coworkers the ability to keep in touch while working remotely or temporarily away from the office. This ensures that everyone is updated, interested, and engaged. However, not all communication strategies are equal. Engagement strategies that rely solely on top-down broadcasts fail to deliver; personalized content targeting by role, location, and team drives measurably higher adoption and participation rates (MangoApps frontline employee app product page). Tool sprawl compounds this problem: employees switching between three to four times more systems than necessary lose over four hours per week in productivity, directly undermining the communication consistency that engagement depends on (MangoApps unified platform product page). Per IDC, employees already spend 2.5 hours per day searching for information — fragmented platforms make that worse, not better. For remote and hybrid teams, communication strategy requires additional structure. Async communication norms, digital visibility for remote contributors, and role-based content targeting are not optional enhancements — they are the baseline for keeping distributed employees engaged. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers current benchmarks for reaching both desk and deskless workers effectively. ## Show Genuine Appreciation While they're usually fairly rational, people are also highly driven by their emotions. In fact, a recent study even suggested that 70% of the average person's decisions are based primarily on emotions. One of the most influential emotions in the workplace is appreciation and recognition. Managers are often all too eager to point out mistakes and generally tend to neglect complimenting an employee's success. When employees feel undervalued or unappreciated, they will quickly become disengaged and emotionally disconnected. Continual dissatisfaction can even be contagious, causing decreased effort and engagement across the team. Don't assume that employees inherently know you appreciate their efforts. An engaging workplace depends on managers regularly and honestly praising success. Companies today can use an [employee experience platform](/solutions/employee-engagement) to announce achievements on a social media-inspired intranet, promoting a culture of appreciation and creating an exceptional work experience for every employee. One deployment benchmark worth noting: 87% workforce engagement was achieved within a few months of launching a branded employee app at scale — recognition loops built into the platform were a key driver. ## Empower People With Potential Understanding an employee's strengths and weaknesses will help them excel at your company. Rather than being overly critical when employees struggle with a new role or responsibility, genuinely assess their abilities and determine if they might be better suited in another position. Make this transition a positive experience, allowing an employee to play into his or her strengths, and avoid implications of failure or inability. Similarly, try to recognize potential within your employees and help them cultivate their skills. When employees know you have their genuine interest at heart they will be open with you about their strengths, weaknesses, and interests. Reward ambition and fuel potential wherever you can and help employees find their most engaging path within the organization. Structured performance conversations and development pathways are a practical mechanism for this. Connecting [performance management](/solutions/performance-management) processes to employee growth goals — rather than treating them as purely evaluative — gives employees a visible stake in their own trajectory and reinforces engagement over time. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines how leading organizations are linking development investment to measurable engagement outcomes. ## Build An Engaging Workplace With MangoApps While every employee is ultimately responsible for their own interests and actions, managers can play a huge role in encouraging, supporting, and sustaining a successful and engaging environment. When the right people are hired, trained, and given the tools to succeed, organizations can discover value beyond what they have ever seen. If you're interested in learning more about increasing employee engagement or discovering how MangoApps creates an engaging digital workplace by empowering and inspiring employees, contact us for a free demo today. ## How Do I Measure Whether My Engagement Efforts Are Working? Building an engaging workplace is only half the equation — knowing whether it's working requires consistent measurement. Employee engagement surveys and employee engagement questionnaires are the most widely used tools for tracking sentiment over time. Effective surveys go beyond annual pulse checks: they capture role-specific data, track trends by team or location, and feed directly into manager action plans. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in and only 13% use intranet tools daily — a gap that signals disengagement even when leadership believes communication is working. Pairing qualitative survey data with platform usage metrics gives a more complete picture. The [Gallup 2026 State of the Global Workplace report](/articles/gallup-2026-state-of-the-global-workplace) provides current global benchmarks for comparing your organization's engagement levels against industry norms. ## What If My Workplace Culture Is Already Struggling? The five strategies above are most effective when applied proactively, but they also serve as a diagnostic framework for cultures already showing signs of disengagement. If appreciation is absent, start there — recognition programs have the fastest measurable impact on morale. If communication is fragmented, consolidating onto a single employee engagement software platform removes the friction that prevents consistent connection. If frontline workers are disengaged, the problem is almost always access: per Emergence Capital, 80% of the global workforce is deskless, and engagement strategies designed for desk workers will not reach them without a mobile-first, no-email-required approach. 90% frontline adoption within the first six months is achievable with the right platform, per a CVS deployment case study — demonstrating that even large, distributed workforces can be reached quickly when the tool matches the workforce. For organizations in complex labor environments, [managing a unionized workforce](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) adds additional communication and compliance considerations that standard engagement playbooks do not address. --- # How MangoApps Is Connecting TeamHealth Clinicians **Author:** Anjali **Published:** 2018-12-20 **Category:** customer-success-stories About TeamHealth TeamHealth is a clinician services organization based out of Knoxville, Tennessee. The company provides highly-qualified and exceptionally-skilled physicians, advanced practice clinicians, and other healthcare professionals to hospitals and other health-related organizations throughout the United States. Well-known in the healthcare industry for their exceptional clinical associates across the country, TeamHealth works with more than […] # How MangoApps Is Connecting TeamHealth Clinicians TeamHealth operates one of the largest clinician networks in the United States — more than 16,000 affiliated healthcare professionals across approximately 3,100 facilities. Most of them are emergency room clinicians who are never at a desk. When TeamHealth needed to consolidate 200+ fragmented communication systems into a single mobile-first platform, reach a geographically dispersed workforce without desktop access, and meet strict HIPAA requirements, MangoApps delivered on all three. This case study explains what changed, what the outcomes show, and what other healthcare organizations evaluating this category should ask before making a platform decision. ## About TeamHealth TeamHealth is a clinician services organization headquartered in Knoxville, Tennessee. The company provides physicians, advanced practice clinicians, and other healthcare professionals to hospitals and health-related organizations throughout the United States, supporting more than 16,000 affiliated clinicians across approximately 3,100 facilities. The scale creates an inherent communication problem: a workforce this large, this dispersed, and this mobile cannot be reached through a desktop intranet designed for office-based employees. Emergency room clinicians move between patient rooms, departments, and facilities throughout a shift. They need a platform that meets them where they work — not one that assumes they will come to it. ## The challenge: connecting a workforce that is almost never at a desk Three structural problems defined TeamHealth's communication environment before MangoApps. **Tool sprawl.** TeamHealth was managing more than 200 separate systems for communication, scheduling, collaboration, and updates. According to IDC, employees spend an average of 2.5 hours per day searching for information — a cost that compounds across a clinical workforce where time is already measured in minutes between patients. Every additional system added to that fragmentation rather than reducing it. **Deskless access gap.** According to Emergence Capital, 80% of the global workforce is deskless. For TeamHealth, whose clinical employees are emergency room practitioners rather than desk workers, the standard intranet model was structurally incompatible with how the workforce actually operates. According to Social Edge Consulting, 91% of organizations run an intranet — but nearly a third of employees never log in, and only 13% use one daily. The implication is direct: a platform that relies on desktop access or habitual login behavior will systematically exclude the employees it most needs to reach. **Compliance requirements.** HIPAA governs how patient-adjacent information is handled in any communication channel. A general-purpose collaboration tool configured to meet those requirements is a different operational proposition than a platform where HIPAA compliance is built into the architecture. For TeamHealth, that distinction was non-negotiable. ## What MangoApps built for TeamHealth MangoApps gave TeamHealth's clinicians one platform where they start their day. Consolidating 200+ systems into a single mobile dashboard removed the need to navigate between disconnected tools to find schedules, receive company updates, complete assigned tasks, or connect with colleagues. ### A centralized action center MangoApps dashboards give TeamHealth clinicians a single place to see what needs attention. Clinicians receive push notifications and smart reminders about action items, can launch tasks directly from the dashboard, and can share items with supervisors without switching applications. The action center creates the habitual daily touchpoint that drives ongoing engagement — not a one-time login, but a platform employees return to because it surfaces what is pending. ### True mobile single sign-on TeamHealth clinicians access a wide range of software and resources throughout a shift. MangoApps provided true single sign-on, allowing staff to move between programs without re-authenticating. SWOOP Analytics found that the average employee spends only six minutes per day using intranet tools — a figure that reflects, in part, platforms that require repeated logins before staff can reach what they need. An [employee app](/solutions/employee-app) that removes authentication friction gets used; one that does not gets abandoned after the initial rollout. ### HIPAA compliance built into the architecture MangoApps is purpose-built for [healthcare organizations](/industries/healthcare) that operate under HIPAA compliance requirements. The platform includes SAML 2.0 authentication, audit-ready record-keeping, and the ability to read and manage user attributes and groups directly from the SAML assertion. For TeamHealth, this meant the platform could handle updated user attributes and a wide variety of groups — including clinicians rotating between facilities and assignments — without manual administrative intervention. This is the architectural distinction that separates a healthcare-grade platform from a general-purpose tool configured to handle sensitive data. The former is auditable by design; the latter requires ongoing oversight to maintain compliance posture. Five competitors now position specifically around "secure intranet" as a category. For healthcare IT and security teams, the evaluation criteria come down to specifics: named protocol support (SAML 2.0), HIPAA-compliant record-keeping, and group management by assertion — architectural decisions, not configuration choices. ### Coordinated communications at scale The TeamHealth communication team regularly publishes articles on behalf of leaders to manage messaging across the organization. MangoApps supports this with built-in ghostwriting: a content specialist can draft and publish under another user's name, with multiple departments able to edit before publication. Coordinated communications across 3,100 facilities requires a workflow that keeps messaging consistent without requiring executives to manage their own publishing queue. ### Content tools and recognition for clinicians on the move Clinicians needed a way to save relevant content immediately when they encounter it during a shift. MangoApps allows users to pin or unpin posts and updates directly from the mobile app, creating a personal saved library accessible from the newsfeed without a separate search. Direct and group messaging let clinicians connect with colleagues by name, location, or credentials — replacing ad hoc phone calls and disconnected messaging with structured, searchable communication. Recognition capabilities let TeamHealth employees acknowledge colleagues, supervisors, and direct reports with fully customizable awards. In healthcare, replacing a frontline employee costs between $4,400 and $15,000. Recognition built into the same daily workflow — not a separate platform — is a retention investment that addresses the engagement factors that drive attrition before they become turnover events. ## Outcomes: what the deployment produced TeamHealth's deployment produced a clinical workforce with a single access point for communication, task management, and scheduling — replacing 200+ systems with one mobile-first platform. The consolidation removed the daily tool-switching that had previously consumed clinician time and created compliance exposure. Healthcare organizations using a unified employee app have reached 87% workforce engagement within the first few months of launch, per the MangoApps OU Health branded app case study. Comparable deployments in high-volume frontline healthcare environments have reached 90% frontline adoption within the first six months. For TeamHealth, that trajectory means a clinician workforce that is consistently reached and less likely to disengage from an organization whose communication infrastructure works for how they actually work. The retention economics are the other half of the outcome picture. Replacing a frontline employee costs between $4,400 and $15,000. Across a 16,000-person clinical workforce, small improvements in retention produce significant dollar value. A platform that reduces daily friction — fewer systems to navigate, faster access to information, recognition built in — directly addresses the engagement drivers that precede attrition. For a comparable deployment in a distributed healthcare membership organization, the [American College of Radiology case study](/resources/case-study-american-college-radiology) covers how MangoApps reached a specialized, geographically dispersed workforce and what the adoption trajectory looked like in practice. ## What healthcare organizations should ask before choosing a platform The TeamHealth case surfaces a consistent set of evaluation questions for healthcare operators facing similar challenges. **Does the platform work without desk access?** This is the first architectural question for any clinical, field, or distributed workforce. A platform requiring desktop credentials or a corporate email writes off most of the workforce before deployment begins. MangoApps supports email-free login, mobile-first access, and SSO that removes authentication friction for employees who move between facilities throughout a shift. **Is HIPAA compliance designed in or configured in?** General-purpose collaboration tools can be configured to handle sensitive data, but those configurations require ongoing maintenance and oversight. For healthcare operators in regulated environments, a platform where HIPAA compliance is architectural — audit-ready records, SAML 2.0, group management built in by default — is a more durable operational choice than one that relies on configuration layers to maintain compliance posture. **What does adoption look like for dispersed clinical teams?** The TeamHealth deployment reflects a pattern common to successful healthcare intranet rollouts: establish the mobile app as the primary access point early, integrate SSO to remove authentication friction before the broader rollout, use the action center and push notifications to build habitual daily engagement, and layer in advanced features — ghostwriting, rewards, external navigation links — once the core habit is established. **How does implementation timeline compare across platforms?** The consolidation from 200+ systems to a single platform is a meaningful change management exercise, not just a technology swap. The most reliable deployment timelines establish a pilot across a single region or facility type first — surfacing access friction before the broader rollout, calibrating notification cadence against a real user population, and producing adoption rate data that makes the case for full deployment concrete. **Where can independent platform evaluations be found?** For organizations conducting a formal evaluation, the [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independently produced comparison data across intranet platforms, with coverage of compliance, workforce type, and industry-specific requirements. ## What the TeamHealth case study means for healthcare operators The critical decisions in a healthcare intranet deployment are made before the first employee logs in: choose a platform built for frontline access, not adapted for it; choose one where HIPAA compliance is architectural, not configured; and choose one that consolidates the tool landscape rather than extending it. TeamHealth's deployment demonstrates that these requirements can be met simultaneously in a production environment at scale — 16,000 clinicians, 3,100 facilities, HIPAA compliance by design, and a single mobile-first access point replacing 200+ fragmented systems. For healthcare organizations with dispersed, shift-based workforces facing the same combination of deskless access gaps, compliance obligations, and tool sprawl, that outcome is available without custom development. The organizations that get this right do not just solve a communication problem. They make a retention investment that compounds at scale — and they build the communication infrastructure that makes every subsequent initiative, from compliance training to recognition to policy updates, consistently reachable by the employees who need it most. --- # 8 MangoApps Features To Enhance Your Office Holiday Spirit **Author:** Anjali **Published:** 2018-12-18 **Category:** modules-features The holiday season is finally here! Which means festive evenings, office parties, and preparations for another outstanding year. At MangoApps, we understand how important holidays are and how celebrations bring everyone in the office closer together. So we wanted to offer a few ideas about how we can help. MangoApps features can help organizations strengthen […] The holiday season is finally here! Which means festive evenings, office parties, and preparations for another outstanding year. At MangoApps, we understand how important holidays are and how celebrations bring everyone in the office closer together. So we wanted to offer a few ideas about how we can help. MangoApps features can help organizations strengthen company culture, boost employee engagement and coordinate activities throughout the season. Here are 8 of the most festive MangoApps features to bring your workforce together and enhance your office holiday spirit. Office Locations And Holidays MangoApps enables companies to establish rich, detailed and informative office locations for every structure in the organization. These details include location address, work time, emergency contact information, and even a brief summary of what happens at that building or branch. Office locations also allow domain admins to add custom fields to each location, making sure they can meet enterprise-specific requirements and compliances. Locations can even be imported into MangoApps from a CVS of all branch areas. Within office locations, admins can assign recognized holidays for each location, and how the office will be affected. This gives employees a clear understanding of how the upcoming holidays will influence both their specific office and any other branches. Keeping employees aware and informed about office closures, business hour alterations, and any other offices changes throughout the season will help them plan vacations and personal activities easily, promoting a healthy work-life balance. Informing employees about holidays and celebrations in other branches will also help them plan, communicate and collaborate better with their peers throughout the organization. Employees can discover holiday details through the Office Locations page or by adding an upcoming holiday widget to their dashboard. Posts As A Story MangoApps allows company posts to be published as a site-wide banner. The banner is then visible to all users for up to 24 hours. After 24 hours, the banner will be automatically removed but the company post will still remain. Company posts are a great way to spread holiday cheer, announce the start of an office celebration, or recognize coworker celebrations like birthdays or work anniversaries. As employees click on a site-wide banner they are redirected to the entire post, letting them read, comment and react to the news. Banners are also a great way for management to highlight important news, preview upcoming events, promote new content, and celebrate employee success. Company-Wide Posts Company-wide posts are a fun and easy way to promote holiday cheer. Posts can be inquisitive and invite coworkers to share experiences or learn more about each other. Inspire engagement from everyone by asking questions, encouraging dialogue and posting about relatable topics. Posts asking “What is your favorite Christmas song?” “What is a classic holiday tradition?” or “Is fruitcake actually edible?” are sure to spark conversations company-wide. With the help of the comments section, reactions, GIFs and @mentions you’ll be boosting the office holiday spirit in no time. Company Calendars And Events MangoApps Company Calendar lets admins set a full year of location-based holidays and other important company dates. This wide-reaching company calendar helps companies and employees alike improve the office holiday spirit as they stay organized and plan more effectively throughout the year. Calendars help put holidays and other important events in context, allowing employees to see, prepare and schedule around upcoming activities well in advance. Company events can be created as a single event or a regularly scheduled experience. MangoApps Company Calendar also integrates with other important MangoApps modules, making sure that user holidays, events and meetings are automatically incorporated into a user’s calendar based on his or her office location, department, or team. Online Polls And Surveys MangoApps polls and surveys are the perfect way to discover opinions, boost engagement, plan events and gauge interest. Offices, for example, can create polls and surveys to see where they would like to hold the annual company Christmas party or if a department or team would like to participate in a cookie competition or gift exchange. Polls, much like company-wide posts, can also be used to share fun and interesting holiday questions and opinions. Polling employees about their “Favorite Christmas Movie” or ” Favorite Flavor Of Candy Cane” is a great way to get people involved, invested, and boost the office holiday spirit, while still staying productive throughout the day. Holiday Greetings Module The MangoApps Greetings Module provides users with the tools they need to celebrate holidays, life events and community milestones. The greetings module includes more than 60 out-of-the-box greeting for categories like holidays, birthdays, thank you’s and other events commonly found throughout the office. Domain admins can also create their own custom greetings, to incorporate industry or business specific shout-outs and recognition. Greetings are fun, festive and help spread holiday cheer, no matter what you are celebrating, helping employees engage with each other, communicate together and build lasting friendships across the organization. Private Messages Private messages can be created between individual employees or an entire group. These messages let users communicate and collaborate together outside of the public eye, making it the perfect place to plan a surprise retirement party, baby shower, birthday party or celebration. Private messages are also ideal for holiday plans, events, and activities between teams or small groups of individuals, where their conversations will not be distracting to other employees. Private messages can be sent to network users and established company guests, making it easy to communicate with anyone you need. Chats and GIFs Online chats are the fastest and easiest way to connect with other employees. Real-time chats can be initiated with individual coworkers or within a team or department at any time and from any device. Instant messaging provides users with the ability to cut across complex team dynamics and reach out to friends across the office to celebrate important occasions and wish each other well. Emojis, reactions, comments, and gifs are sure to encourage the office holiday spirit by making chats and posts engaging, fun and full of festivity. The holiday season should be festive and fun, especially in the office. With MangoApps, employees are sure to enjoy the holidays even more as they find new ways to communicate and share the office holiday spirit together. At MangoApps, we believe in providing businesses with the tools and support they need to expand, improve, and implement success. And of course, celebrating along the way! To learn more about how MangoApps can assist your organization, contact us or schedule a personalized demo today. schedule demo --- # How Customers Use MangoApps’ Company Sites Module **Author:** April Thomas **Published:** 2018-12-11 **Category:** modules-features MangoApps is dedicated to providing our clients with high-quality, personalized and customized communication. We love helping our customers and prospective clients discover how all of our different features can benefit their specific needs. We wanted to continue that effort by adding context to one of our popular features, the MangoApps Company Sites Module. So we’ve […] # How Customers Use MangoApps' Company Sites Module MangoApps is dedicated to providing our clients with high-quality, personalized, and customized communication. We wanted to add context to one of our popular features — the MangoApps Company Sites Module — by sharing concrete examples of how clients across industries use it today. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in. The examples below show how a well-designed company sites module changes that equation. Because we believe in strict confidentiality, we've withheld company names. As you review these industry examples, consider how the MangoApps Company Sites Module — a core part of our [modern intranet](/solutions/modern-intranet) platform — can address your organization's specific communication and knowledge management challenges. ## Centralize Company Information An architecture client uses the MangoApps Company Sites Module as a redirecting resource for its employees. The architecture industry must reference all kinds of building regulations and guidelines. Our client uses the company sites module as an easily accessible resource page, linking out to detailed wikis outlining various building types, guidelines, codes, and procedures. They also use the module to provide contact information for external building companies, advisors, and resources. Having this easy-access resource area makes long-term knowledge management simple and straightforward, and improves autonomy within the company as architects can conveniently navigate detailed archives and quickly find specific resources. Employees spend an average of 2.5 hours per day searching for information, per IDC — a centralized intranet resource page directly cuts into that lost time. The [company portal](/key-features/company-portal) and [department sites](/key-features/department-sites) features work together here to keep content organized by team and topic. ## Share Announcements and News A distribution company uses the company sites module to provide important updates, news, memos, and announcements to employees spread all over the country. Their distribution strategies and services require frequent travel, and employees often find themselves away from traditional offices. The company sites module makes it easy for employees to stay up to date on company news and travel details while on the road, visiting a potential client, or away on any other kind of company business. Employees can check updates whenever they need to without being bombarded by emails or misplacing important information. Content in the company site is easy to interact with as well, letting employees like updates, send comments, and offer feedback throughout the company. Per Emergence Capital, 80% of the global workforce is deskless — a mobile-first company sites experience allows frontline and distributed employees to access news, resources, and HR tools without a corporate email address or VPN. Keeping those workers informed also has a direct retention impact: replacing a single frontline employee costs between $4,400 and $15,000 on average, making consistent communication a measurable business investment. For a real-world example of this approach, see [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study). ## Create Unique Resource Pages One of our healthcare clients uses the MangoApps Company Sites Module to create specific resource pages and share important information. These pages offer a helpful overview of every department and provide a place to ask questions as needed. These resource pages also compile and categorize useful tools and make department information easy and accessible. Healthcare organizations using a centralized intranet portal can reduce cross-department form retrieval time and improve patient care outcomes by giving staff instant access to resources outside their own department. With MangoApps, the clinic provides better patient care, as employees can quickly find forms outside of their department. Role-based permissions and content governance controls within Company Sites ensure that sensitive clinical information is visible only to authorized staff — an increasingly important requirement as healthcare organizations face stricter compliance mandates. The [webpage builder](/key-features/webpage-builder) makes it straightforward for department administrators to maintain and update these pages without IT involvement. For a comparable deployment in a regulated environment, the [American College of Radiology case study](/resources/case-study-american-college-radiology) illustrates how a healthcare-adjacent organization achieved easy, governed communication at scale. ## Translate to the Local Language A global sales and marketing customer operates offices out of several countries, each with its own individual language. With its wide geographic reach, the organization needed a way to accurately and easily communicate corporate policies, work regulations, marketing guidelines, and other important company information to employees in each area. The MangoApps Company Sites Module was the solution. Our translation feature — supporting 50+ languages with real-time translation — lets our client present needed content in almost any language. Admins in every region can keep communication clear by creating both corporate-wide and area-specific content in the office's native language. This helps employees find, access, and utilize information no matter their language or area of the world. Multilingual capability is not a convenience feature for global enterprises — it is a strategic differentiator. Per SWOOP Analytics, the average employee spends only six minutes per day using intranet tools, and per Social Edge Consulting, only 13% use an intranet daily. Presenting content in an employee's native language is one of the most direct levers for closing that engagement gap. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers additional strategies for improving intranet adoption across distributed, multilingual workforces. ## MangoApps Company Sites: What to Expect from a Modern Deployment Across these four use cases, a consistent pattern emerges: the organizations getting the most from Company Sites treat it as a living, governed intranet layer — not a static page. Traditional intranets can take months to deploy, strain IT teams, and deliver ungoverned content that becomes stale quickly. The MangoApps Company Sites Module is designed to eliminate that setup burden, with an admin experience that lets non-technical owners publish, translate, and govern content without opening a support ticket. A well-adopted company sites rollout can reach 90% frontline adoption within the first six months — a benchmark achieved by large enterprises using modern intranet platforms. Role-based permissions, AI-powered content surfacing that delivers role- and location-relevant information automatically, and mobile-first access combine to make that adoption rate achievable rather than aspirational. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarking context for evaluating where any intranet platform stands against this standard. At MangoApps, we know that every company has its own unique strengths and challenges. We love to see the innovative ways companies use Company Sites to communicate, collaborate, and increase productivity. In addition to our feature set, we're always happy to work with clients to create personalized solutions. Contact us or schedule a demo to see how the Company Sites Module fits your organization's specific needs. ## How Do I Set Up the MangoApps Company Sites Module? Setup begins with your MangoApps admin console, where you can activate the Company Sites Module, define site structure, assign content owners by department or region, and configure role-based permissions. The [webpage builder](/key-features/webpage-builder) provides a no-code editing interface so department administrators can publish and update pages without IT support. For organizations migrating from SharePoint 2016 or 2019, the [Frontline Intranet Requirements checklist](/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) outlines the governance and access-control decisions to make before go-live. ## How Does Company Sites Compare to a Traditional Intranet? A traditional intranet — by definition, a private internal network for sharing company information — typically requires significant IT infrastructure, long deployment timelines, and ongoing maintenance to keep content current. The MangoApps Company Sites Module functions as the content and navigation layer of a [modern intranet](/solutions/modern-intranet), adding structured resource pages, multilingual publishing, and role-based governance on top of the broader MangoApps employee experience platform. For a detailed independent comparison of how MangoApps stacks up against legacy and modern alternatives, see the [MangoApps entry in the 2026 Forrester Wave for Intranet Platforms](/articles/mangoapps-2026-forrester-wave-intranet-platforms). ## What Other MangoApps Features Work Alongside Company Sites? Company Sites works most effectively when paired with [workspaces](/key-features/workspaces) for project-level collaboration, department sites for team-specific content hubs, and the [employee app](/solutions/employee-app) for mobile access by frontline workers without a corporate email address. Together, these tools of knowledge management form a unified layer that connects every employee — desk-based or deskless — to the information they need, when they need it. --- # 5 Signs Your Company Needs A Digital Upgrade **Author:** Anna Carriveau **Published:** 2018-12-06 **Category:** company-culture With the rapid rise of new technology in the workforce, businesses across industries are struggling to properly accommodate their employee’s growing needs. Employees today expect flexibility, freedom, and access to effective technology. Businesses that ignore these needs are doomed to have a difficult time recruiting and retaining high-quality employees. But how do you know if […] # 5 Signs Your Company Needs a Digital Upgrade If your employees are disengaged, struggling to find information, or quietly updating their résumés, outdated digital tools are often the root cause. This article identifies five concrete warning signs that your organization needs a digital upgrade — and explains what a modern intranet and employee engagement platform can do about each one. --- ## 1. Employee Turnover Is Climbing — Especially Among Your Best People High-performing employees leave when they feel unsupported by the tools they're given. Replacing a single frontline employee costs between $4,400 and $15,000, making digital friction a direct line-item risk — not just an engagement problem (per MangoApps mobile app product page and industry report framing). When exit interviews consistently surface frustration with technology, that's a signal worth taking seriously. The cost compounds quickly. Employees lose over four hours per week switching between disconnected systems, according to MangoApps product and tool-sprawl positioning data. That's time that could go toward actual work — and it's a friction point that drives people toward employers who have already solved it. If your organization is seeing turnover tick upward, audit your digital environment before assuming the problem is compensation or culture. Ask departing employees directly whether the tools made their jobs harder. Their answers will tell you more than most engagement surveys. --- ## 2. Your Intranet Is Ignored — or Barely Used According to Social Edge Consulting, 91% of organizations operate an intranet. Yet nearly a third of employees never log in, and only 13% use one daily (Social Edge Consulting). The average employee spends just six minutes per day in intranet tools (per SWOOP Analytics) — while spending 2.5 hours per day searching for information they can't find (per IDC). That gap is the problem. An intranet that employees avoid isn't a communication channel — it's a cost center. A stale, hard-to-navigate portal signals that communication is fragmented, content is out of date, and employees have learned to work around the system rather than through it. Modern intranet platforms can achieve 87–90% workforce adoption within the first few months when deployed with a branded, mobile-first experience, according to MangoApps case studies including OU Health, Kansas City Chiefs, and PetSmart. The difference between an ignored intranet and an actively used one usually comes down to personalization, mobile access, and whether the platform surfaces relevant content without requiring employees to hunt for it. For a detailed look at what separates high-adoption intranets from low-adoption ones, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) is a useful independent benchmark. --- ## 3. Frontline and Deskless Workers Are Left Out of the Loop Approximately 80% of the global workforce is deskless (per Emergence Capital). These are the employees — in retail, healthcare, manufacturing, logistics, and field services — who don't sit at a computer, don't have a corporate email address, and are often excluded from the digital tools that office workers take for granted. If your current digital environment requires a VPN login or a company email to access internal communications, you are structurally excluding the majority of your workforce. That's not a remote-work problem — it's a platform design problem. A [modern workplace intranet](/solutions/modern-intranet) built for frontline access works on personal mobile devices, requires no corporate email, and delivers the same news, policies, schedules, and recognition tools to a warehouse associate that it delivers to a corporate manager. When CVS deployed a modern employee experience platform with this design, they achieved 90% frontline adoption within six months. --- ## 4. Email Is Still Your Primary Communication Channel Email was designed for external correspondence, not for running internal operations across a workforce of any size. When email becomes the default channel for announcements, policy updates, shift changes, and team coordination, information gets buried, threads multiply, and employees disengage from communications entirely. The symptom is easy to spot: important announcements go unread, employees claim they "never got the memo," and managers spend time re-communicating information that was already sent. The underlying cause is that email provides no way to confirm comprehension, no way to surface relevant content to the right audience, and no way to encourage the kind of two-way dialogue that keeps employees connected to the organization. A unified [employee engagement](/solutions/employee-engagement) platform replaces the email-as-intranet pattern with targeted feeds, read receipts, acknowledgment workflows, and social interaction — all from a single location. Employees stop missing critical updates, and communicators stop guessing whether their messages landed. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are restructuring their channel strategy away from email dependency. --- ## 5. You're Managing Too Many Disconnected Systems The five signs above don't exist in isolation. They're usually symptoms of the same underlying condition: an organization running three to four times more digital systems than necessary, with no single platform tying them together. When employees need one tool for messaging, another for documents, a third for HR forms, a fourth for scheduling, and a fifth for recognition — and none of these systems talk to each other — the result is tool sprawl. Employees spend their time navigating between platforms rather than doing their jobs. IT spends its time managing integrations that break. And leadership loses visibility into whether any of it is working. An inability to surface relevant information quickly is itself a warning sign. If employees can't find what they need in under a minute, your digital environment is working against productivity. Modern platforms address this with AI-assisted content surfacing that delivers the right information to the right person without requiring a manual search. Consolidating onto a unified platform — one that handles communications, knowledge management, recognition, and frontline access — eliminates the switching cost, reduces the information-search burden, and gives employees a single place to start their day. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines how organizations are approaching this consolidation in practice. --- ## What to Do If You Recognize These Signs If two or more of these signs describe your organization, the problem is unlikely to resolve on its own. Digital environments don't improve passively — they require deliberate investment in platforms that are built for how your workforce actually operates. Here's a practical starting point: 1. **Audit your current tool inventory.** List every platform employees are expected to use. If the list exceeds six to eight tools, consolidation is overdue. 2. **Run an employee engagement survey.** Ask directly whether employees can find the information they need, whether they feel informed about company news, and whether their tools help or hinder their work. Employee engagement questionnaires focused on digital experience will surface friction points that leadership often can't see. 3. **Evaluate intranet adoption data.** If your analytics show that fewer than 20% of employees log in weekly, your intranet is not functioning as a communication channel. 4. **Assess frontline access.** Determine what percentage of your workforce cannot access your current digital tools without a corporate device or email. If that number is significant, your platform is not built for your workforce. 5. **Prioritize mobile-first, unified platforms.** Employee engagement training and onboarding are far more effective when delivered through a platform employees already use daily — not through a separate system they have to remember to check. Organizations that address these warning signs proactively — rather than waiting for turnover to force the issue — are better positioned to retain experienced employees, reduce operational friction, and build the kind of digital culture that supports long-term growth. For a closer look at how other organizations have navigated this transition, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the workforce technology decisions HR leaders are prioritizing this year. --- # 7 Warning Signs Of Decreasing Employee Engagement **Author:** Anna Carriveau **Published:** 2018-12-03 **Category:** employee-engagement As a manager, few things are more discouraging than receiving a resignation from out of the blue. Realizing that a good employee is unhappy at work can come as a shock, especially when it seemed like everything was going well. Decreasing employee engagement, especially in previously motivated employees, is a serious problem for organizations. Disengaging […] ## 7 Warning Signs Of Decreasing Employee Engagement As a manager, few things are more discouraging than receiving a resignation out of the blue. Realizing that a good employee is unhappy at work can come as a shock, especially when it seemed like everything was going well. Decreasing employee engagement, especially in previously motivated employees, is a serious problem for organizations. Disengaging attitudes can do a lot more than just cost companies a valuable employee — replacing a frontline employee costs $4,400–$15,000 on average, making early engagement intervention a direct cost-avoidance lever. Negative work perceptions can become contagious and could lead to serious problems in the long run. It is critical to recognize decreasing employee engagement in its early stages. If caught early, companies can address issues and clarify misconceptions right away, helping them retain strong employees. To help managers and supervisors with this effort, we have identified the 7 warning signs of decreasing employee engagement. ## #1: Declining Quality Of Work While it might seem obvious, declining work quality is one of the first signs of decreasing employee engagement. When employees no longer feel connected to their company they often struggle to put forth their best effort. If an employee starts to exhibit lower levels of work quality, it is important to handle the situation appropriately. Rather than punishing or issuing a warning, try to have a discussion and figure out the real cause of the problem. Working with an employee to overcome problems is usually much more effective than angry lectures or punishments. Evaluate their past performance and try and find where work quality began to decline. Communicate honestly about your concerns and work together to find a solution. Managers who rely solely on performance reviews to gauge engagement miss disengagement in high performers — pulse surveys and platform-level [collaboration analytics](/solutions/employee-engagement) surface hidden withdrawal before it becomes a resignation. ## #2: Silence From A Spokesperson When an outgoing influencer suddenly stops speaking up, it is almost always a sign of decreasing employee engagement. Outspoken employees tend to be passionate and persuasive, and can cause negative feelings throughout the organization. It is essential for an employer to understand what action triggered this change of behavior. While employees will not always agree with company decisions, disengagement often stems from misconceptions. Try to talk with your employee and gain perspective for why certain decisions were made. After addressing concerns and clearing up misconceptions, he or she may even become a spokesperson for the policy change or action, helping other employees stay engaged and onboard. ## #3: Disinterest In Collaboration A collaboration tool can make it easier for coworkers to communicate and shows admins important metrics about how employees are interacting with each other. This data helps employers see when a disinterest in communication and collaboration occurs. Reluctance to work with their peers is another important warning sign of decreasing employee engagement. This reluctance can be from a single employee, a team, a branch, or even across the entire organization. Disengagement is not only an individual problem — it spreads across teams. Organizations that fail to act on early warning signs face compounding retention costs that make the problem exponentially more expensive over time. Understanding employee collaboration efforts helps employers understand important sentiments within the organization. This rings especially true when there is an unexpected drop in engagement levels. Prolonged phases of reduced social engagement should never be left unattended and companies should do their best to assess concerns as soon as possible. For remote and distributed employees, disengagement signals look different than they do in an office. Reduced response times in async channels and drop-off in digital collaboration tools are the remote equivalents of skipping office activities — a pattern four competitors now explicitly address in their employee engagement software guidance. Employees also lose over 4 hours per week switching between disconnected systems, meaning tool fragmentation is itself a structural driver of disengagement. ## #4: Skipping Office Activities Sometimes, you may not recognize an employee's disengagement by looking at their performance. Disengaged employees might work brilliantly, execute goals, and receive outstanding evaluations, but work performance should never be considered the only indicator of engagement levels. While avoiding company games or organized social events doesn't always mean decreasing employee engagement, it can be a sign of unhappiness or disinterest in the company culture. This is particularly true if the employee was previously active and involved in office activities. Even though their work performance may not be suffering, disinterest in company culture is still important and could play a major role in your employee's happiness and work satisfaction. For frontline and deskless workers — who represent 80% of the global workforce per Emergence Capital — the equivalent signal is withdrawal from shared digital spaces, team channels, or mobile app activity rather than in-person events. An [employee experience platform](/solutions/employee-engagement) built for both office and deskless workers can surface these patterns before they escalate. ## #5: Increased Irritation or Anger If an employee suddenly seems angry or lashes out at others over the smallest issue, it is a sign of decreasing employee engagement. When employees mentally disconnect from a company it becomes more difficult to see coworkers and managers as part of their team. As a result, employees become much less patient and understanding of others in the workplace. Small annoyances may start to feel like compounding problems, especially if the real reasons for disengagement have not been discussed. HR personnel or their respective managers need to step in and diffuse the situation by addressing the real problem. However, increased irritation may also be due to problems that are not work-related. HR members should do their best to observe and consult with the employee to understand and address any underlying work-related issues. Structured employee engagement training and clear escalation frameworks — rather than ad hoc conversations — give managers a repeatable path for these situations. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines how leading organizations are formalizing these manager-employee feedback loops. ## #6: Unusual Performance Scores A collaboration tool can help employers manage employee engagement by making it easier to track employee performance. This could involve attendance logs, completion timelines, to-do lists, key performance indicators, and much more. Insights about employee performance can alert admins to changes in employee performance right away, helping them address concerns as they occur. When approaching an employee about his or her performance, be sure not to micromanage. Approach the situation with the goal to work together with employees to identify problems and find solutions. Employee engagement software with built-in [performance management](/solutions/performance-management) analytics makes it possible to detect unusual score patterns across teams and departments — not just individual contributors — so HR can intervene at the right level. Employee engagement questionnaires and pulse surveys embedded in the platform provide a continuous signal between formal review cycles. ## #7: Pessimistic About Challenges Engaged employees are excited about work and the role they play in an organization. They take on new challenges with enthusiasm and see them as opportunities to be creative and showcase their abilities. When employees experience decreasing engagement, challenges become burdens rather than motivations. This is particularly true when employees have always been quick to act and take on new tasks in the past. When an employee does not show his or her characteristic enthusiasm it is a clear indication that something is going on. Talk to employees about their work satisfaction or ask them about which project they would be interested in based on their talents and skills. Employee engagement courses and on-the-job learning opportunities can reignite a sense of purpose for employees who feel stagnant. Research on [why learning and development strategy fails](/articles/learning-and-development-strategy-embedded-in-daily-work) consistently points to training that is disconnected from daily work as a root cause of this kind of disengagement. ## MangoApps: From Warning Signs to Structural Solutions Decreasing employee engagement doesn't have to take you by surprise. With a little extra attention and some helpful tracking tools, your organization can overcome these employee engagement obstacles and address concerns right away. But managerial coaching alone is not a scalable solution. Each of the seven warning signs described above has a platform-level equivalent: collaboration drop-off, performance anomalies, pulse survey non-response, and reduced activity in digital channels are all signals that an employee experience platform is designed to catch automatically. MangoApps includes all of the reward and recognition tools, employee engagement survey capabilities, and analytics employers need to build productive cultures and address disengagement before it becomes a resignation. The platform is built for both office and deskless workforces — critical given that 80% of the global workforce is deskless, per Emergence Capital — and surfaces the exact engagement signals described in each warning sign above. To learn more about how MangoApps can increase employee engagement, contact us or schedule a demo with us today. --- ## What Should Managers Do After Spotting These Warning Signs? Recognizing a warning sign is only the first step. Effective retention requires a structured response: a one-on-one conversation within 48 hours of noticing the signal, a documented action plan co-created with the employee, and a follow-up check-in within two to four weeks. Employee engagement training for managers — covering active listening, feedback delivery, and escalation paths — significantly improves outcomes compared to informal coaching alone. Organizations that formalize these processes through an employee experience platform reduce the time between signal detection and resolution, which directly lowers voluntary turnover costs. For industry-specific approaches to engagement, see how these principles apply in [retail](/industries/retail) and [hospitality](/industries/hospitality) environments, where frontline disengagement is especially costly. ## How Do Engagement Warning Signs Differ for Remote and Frontline Employees? For in-office employees, warning signs are often visible: body language, attendance at meetings, participation in team activities. For remote and deskless workers, the signals are digital. Reduced message response times, lower participation in async channels, and declining use of collaboration tools are the remote equivalents of the seven warning signs above. Per Emergence Capital, 80% of the global workforce is deskless, meaning the majority of disengagement goes undetected by managers who rely on in-person observation alone. An employee engagement software platform that tracks digital collaboration patterns — not just formal performance metrics — is the only scalable way to monitor engagement across a distributed workforce. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are adapting their communication strategies for exactly this challenge. ## What Tools Help Organizations Measure and Improve Employee Engagement? Employee engagement surveys and employee engagement questionnaires are the most common starting point, but point-in-time surveys miss the continuous signals that precede disengagement. The most effective organizations layer three tools: (1) pulse surveys embedded in daily workflows, (2) platform-level analytics that track collaboration and activity patterns, and (3) structured manager training on engagement conversations. Employee engagement software that combines all three — rather than requiring separate point solutions — reduces the administrative burden on HR and gives managers actionable data in real time. For a broader view of how workforce operations technology is evolving to address these gaps, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) is a useful reference. --- # 5 Ways To Build A Culture Of Employee Recognition **Author:** Anna Carriveau **Published:** 2018-11-29 **Category:** company-culture Today’s workforce approaches satisfaction very differently than employees in the past. No longer will a large paycheck guarantee an organization the best talent they need.  Numerous workplace surveys conducted on modern-day workforce trends have shown employees consider other factors. In order to attract top talent, companies now need to build a culture of employee recognition. […] # 5 Ways to Build a Culture of Employee Recognition The recognition problem most organizations face isn't that they don't value their employees. It's that they built recognition programs for employees who are visible. A manager notices a strong performance in a weekly team meeting. A peer mentions a colleague's effort in passing. Annual reviews convert scattered impressions into formal ratings. These mechanisms work reasonably well for desk-based workers with consistent manager exposure — and reach almost no one else. Per Gallup, only 1 in 3 U.S. workers strongly agree they received recognition or praise for doing good work in the past seven days. That figure has remained largely unchanged despite recognition programs appearing across nearly every organization's HR infrastructure. The programs exist; the recognition doesn't reach. For organizations with frontline workers, distributed teams, or shift-based operations, the gap is more acute. According to Emergence Capital, 80% of the global workforce is deskless. A nurse on a night shift, a warehouse team lead, a retail associate closing a difficult customer interaction — these workers are systematically underserved by programs built around office visibility. Recognition built for the 20% will miss the 80%. The following five strategies address what actually determines whether a recognition culture takes hold: frequency, peer reach, frontline design, personalization, and measurement. They're not additions to an existing program — they're rebuilds of the assumptions most programs rest on. ## 1. Replace milestone recognition with everyday frequency The most common recognition program failure isn't absence of intent. It's low frequency. When recognition is tied to annual reviews, quarterly all-hands meetings, or work anniversaries, employees receive the message that they matter four times a year. That cadence is too infrequent to reinforce behavior or build culture. Recognition tied to formal cycles tells employees what the organization valued — past tense — not what it values now. Recognition is most effective when it's specific, timely, and linked to the behavior or outcome you want repeated. A direct acknowledgment delivered within 24 hours of a strong customer interaction reinforces the behavior. The same acknowledgment delivered three months later in a review cycle is historical data, not motivation. Moving to high-frequency recognition requires two things working in parallel: cultural permission — managers and peers who feel authorized to recognize without initiating a formal process — and tooling that makes the act low-friction. A quick shoutout in a team feed, a notification that takes 30 seconds to send, a peer acknowledgment that surfaces in a mobile app rather than waiting for a quarterly meeting. Organizations that treat the two as substitutes — either culture OR tools — find that culture drifts without infrastructure and tools go unused without cultural reinforcement. ## 2. Open recognition to peers, not just managers Manager-to-employee recognition is the default design pattern. It creates two compounding problems. The first is coverage: managers can only recognize what they observe. In distributed and frontline environments, direct observation is structurally limited. A district manager overseeing twelve locations cannot personally witness the customer recovery that happened at location 7 on a Tuesday evening. If recognition depends on manager observation, most recognition-worthy moments never enter the program at all. The second is authenticity. Peer recognition consistently outperforms top-down recognition on sustained engagement impact. When a colleague posts "that shift handoff saved us two hours" in a public team channel, it carries different weight than the same sentiment delivered in a formal review. Peer recognition is higher-frequency, more contextually specific, and perceived as more genuine — because it usually is. Peers witness the details that managers miss. Building peer-to-peer recognition into a program requires structured channels, not just cultural invitation. A public acknowledgment feed, a "shoutout" feature embedded in team communication tools, or a recognition board that any employee can contribute to creates the infrastructure for peer praise without requiring manager initiation. The [MangoApps employee engagement platform](/solutions/employee-engagement) enables peer-to-peer recognition feeds with visibility across teams and locations, so recognition travels laterally through an organization rather than only flowing from the top down. This matters most in shift-based or distributed environments where lateral trust networks are stronger than vertical reporting relationships. ## 3. Design specifically for frontline and remote workers Recognition for employees who don't sit at a desk requires intentional design, not adaptation of programs built for office environments. Mobile-first reach, asynchronous delivery, and role-targeted notification are baseline requirements for frontline populations — not optional enhancements. A push notification to a clinical staff member's phone recognizing a patient outcome lands differently than a post on an intranet she logs into once a week. A shift-based recognition feed that surfaces shoutouts from the prior team creates continuity that email-based programs fail to replicate. Automatic milestone recognition — a work anniversary, a completed safety certification, a 90-day onboarding completion — doesn't require a manager to remember and initiate; it runs on schedule. Healthcare organizations face this design challenge acutely: clinical staff work across locations, rotate shifts, and often have minimal overlap with the managers nominally responsible for recognizing them. symplr, a healthcare operations company, used MangoApps to build a recognition program that reached clinical workers across multiple sites and time zones through mobile-accessible tools designed for shift-based use. [The symplr recognition case study](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program) documents the infrastructure choices that made scaled frontline recognition functional in an industry where retention and engagement are chronic problems. The design principle transfers across industries: retail, manufacturing, logistics, field services. If recognition requires a desktop login, scheduled meetings, or manager-initiated steps during business hours, it is architecturally incompatible with how frontline work actually happens. ## 4. Personalize recognition to the person, not the occasion Generic recognition — the same gift card, the same all-hands callout template, the same plaque sent to whoever happens to have a work anniversary this month — creates a category of program that is technically running and functionally inert. Employees notice when recognition is administered rather than given. Personalization doesn't require large budgets. It requires attention. When a manager knows that a team member is working toward a professional certification and mentions it in a recognition post — "Marcus closed eight accounts this week while also finishing his PMP coursework" — the recognition signals genuine awareness of that person's priorities. That specificity carries more weight than the monetary value of any accompanying reward. SHRM research indicates that employees who receive recognition aligned to their stated preferences — flexible time, development opportunities, experience-based rewards — report higher satisfaction than those receiving standardized gifts of greater monetary value. The personalization signal itself is part of the recognition; it demonstrates that the organization is paying attention to the individual, not just the category. Practical implementation: build preference collection into the onboarding process. Ask employees what recognition means to them. Maintain that information somewhere accessible to managers. Surface it when recognition moments arise. This requires infrastructure — a field in an HR system, a note in a manager check-in template — more than it requires inspiration. The organizations that execute this well have made it easy for managers to act on preferences, not just encouraged them to remember preferences on their own. ## 5. Build measurement into the program from day one This is the step most recognition programs skip, and it is the most common reason they fail quietly rather than loudly. Without measurement, organizations cannot answer two foundational questions: Is the program actually reaching employees? And is it producing the outcomes it was designed for? The absence of measurement also creates a specific organizational risk: recognition programs get cut during budget cycles not because they failed, but because no one can demonstrate that they worked. Programs that run on stated intent alone are vulnerable to exactly this outcome. Recognition measurement doesn't require expensive research or dedicated analytics infrastructure. Three metrics provide sufficient signal to start: **Recognition frequency rate.** What percentage of employees received at least one formal recognition in the past 30 days? A program reaching 60% or more of employees monthly is functioning. A program where recognition is concentrated among 15% of the workforce — despite broad cultural intent — has a distribution problem, not a culture problem. The fix is different in each case. **eNPS trend.** Employee Net Promoter Score, surveyed quarterly, is a reliable leading indicator for whether recognition programs are moving aggregate engagement. Without a tracking metric, there is no basis for iteration, and no way to connect program inputs to engagement outcomes when leadership asks. **Early-tenure retention by cohort.** SHRM research connects structured recognition programs to meaningfully lower voluntary turnover within the first two years of employment. Tracking 90-day and 12-month retention by hiring cohort — and correlating it with recognition frequency data for those cohorts — gives HR a defensible ROI case that survives budget reviews and leadership transitions. For context on how leading organizations are connecting recognition, communication, and engagement measurement into a coherent data strategy, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the metrics frameworks that HR teams are using to convert program activity into retention and performance evidence. The [Gallup 2026 State of the Global Workplace report](/articles/gallup-2026-state-of-the-global-workplace) provides the benchmark data that makes those frameworks interpretable — including the recognition engagement gap that a functioning program should visibly close over time. ## What makes recognition cultures actually take hold Recognition cultures don't emerge from policy or stated intent. They emerge from systems: systems that make recognition low-friction for the giver, extend reach to employees regardless of location or shift, enable the peer-to-peer volume that managers alone cannot produce, and track whether the program is closing the gap it was designed to close. The Gallup figure — 1 in 3 workers receiving recognition in any given week — represents the baseline most organizations are starting from. The organizations closing that gap aren't doing it by reminding managers to say thank you more often. They're doing it by rebuilding the infrastructure that determines who recognition reaches, how frequently, and through which channels. Frequency, peer reach, frontline design, personalization, and measurement are not additions to a recognition program. They are the program. --- # 9 Ways To Hold More Productive Office Meetings **Author:** Anna Carriveau **Published:** 2018-11-20 **Category:** company-culture Surveys show that the average organization spends about 15% of its time in unproductive meetings. This can be frightening when you consider the amount of lost revenue this contributes to. This issue raises the question, how can companies reduce these numbers? One step in the right direction is to make better use of available tools. […] # 9 Ways To Hold More Productive Office Meetings Surveys show that organizations spend about 15% of their time in unproductive meetings — a number that has not moved much despite years of meeting-reform initiatives. The reason most interventions do not work is that they treat all bad meetings as the same problem. They are not. There are two distinct failure modes: meetings that should never have been scheduled, and meetings that belong on the calendar but consistently fail to produce outcomes. Conflating them leads to advice that optimizes the wrong thing. Shortening a meeting that should not exist does not address the underlying cost. The nine practices below address both failure modes, starting with the one most organizations skip. ## The first question: does this meeting need to exist? The most productive meeting is often the one that does not happen. Collaboration platforms that support pre-meeting document sharing and async updates can reduce meeting frequency by replacing routine status updates, approvals, and announcements entirely — not just shortening them. This changes the decision point: instead of asking how to run a meeting better, ask whether an async channel could achieve the same outcome at a fraction of the coordination cost. When organizations move routine communication to an [employee engagement](/solutions/employee-engagement) platform, the meetings that remain on the calendar are the ones that genuinely require real-time coordination. That shift does not happen automatically — it requires a deliberate policy naming which communication types belong in async channels and which require synchronous attendance. ### 1. Identify a real need before scheduling Before sending an invite, test whether the information can be shared through an existing tool. Much of what required meetings in past eras of fragmented communication now requires no meeting at all in organizations with a unified platform. The common mistake is scheduling a meeting out of habit — particularly for updates that could be delivered as a written post. A status update shared asynchronously the night before is more useful than a status meeting the next morning. Meetings should be reserved for decisions, alignment, and work that genuinely requires real-time input from multiple people. ## Getting the right people in the room Even meetings that pass the necessity test fail when the wrong people attend or arrive unprepared. Two practices govern participant selection and preparation: ### 2. Limit meeting members Most meetings should have no more than ten people. Beyond that threshold, decision-making slows, accountability for action items diffuses, and meeting length increases predictably. The cost of a twenty-person meeting is not only the time in the room — it is twenty separate calendars that had to clear and the work each person stopped doing. The common implementation mistake is conflating participation with visibility. The better approach is to keep the meeting small and route outcomes to observers asynchronously after it ends. For teams that include frontline or deskless workers who cannot always attend synchronous meetings, distributing outcomes through mobile-accessible channels ensures those employees receive the context they need without requiring synchronous attendance. ### 3. Prepare beforehand Every participant needs to arrive ready to share and contribute. That means ideas, reports, and questions should be structured ahead of time — not assembled in real time during the meeting itself. Employee engagement software that organizes pre-meeting materials in a single accessible place makes preparation practical even for participants on different schedules or in different locations. The implementation challenge is enforcement. A norm that says "please prepare in advance" without a mechanism is largely decorative. Sharing a structured brief with clear questions 24 hours before the meeting — and tracking which participants have opened it — converts preparation from an aspiration into an observable expectation. Organizations that deliver prep materials via mobile-accessible platforms have seen 50% faster new-hire onboarding compared to in-person-only sessions, a signal that structured, tool-supported preparation habits compound well beyond any single meeting. ## The four practices that keep meetings on track Meetings that pass the necessity test and have the right people in the room still fail when they lack structural discipline. Four practices make the difference: ### 4. Organize an agenda Without a clear agenda, meetings default to whoever speaks loudest. Even brainstorming sessions benefit from an outline of the objective and the expected output. A well-constructed agenda shared in advance lets participants prepare and lets the facilitator make explicit trade-offs when time runs short. The common mistake is treating the agenda as a list of topics rather than a sequence of decisions. Each item should name the question to be answered, not just the subject area. "Q2 marketing" is a topic. "Should we shift the Q2 launch to May given current team capacity?" is a decision — and a meeting organized around decisions ends with outputs rather than impressions. ### 5. Stay on task Off-topic discussions erode meeting time faster than any other single factor. Once a meeting drifts, recovering the thread costs additional time and focus. Background data and supporting analysis belong in pre-meeting documents, not in the meeting itself — information shared inside a meeting without prior context slows everyone down and rarely produces useful discussion. When tangents arise, the facilitator's job is to acknowledge them explicitly, park them in a visible note or follow-up thread, and return to the agenda. The implementation challenge is doing this without making contributors feel dismissed. Naming the tangent as worth following up on — rather than cutting it off — preserves both the agenda and the working relationship. ### 6. Confirm logistics in advance Meeting time is frequently wasted at the start on logistics: finding a room, connecting the display, troubleshooting the video call. Each minute lost at the opening disproportionately affects participant focus and signals that the meeting was not carefully prepared. Booking a space and testing the technology before the meeting starts eliminates this drag. For distributed teams, this means confirming the conferencing setup the day before, not five minutes before the invite fires. The preparation investment is small; the return in meeting quality is consistent. Teams that skip this step reliably attribute poor meeting perception to reasons downstream of logistics — when the real failure was upstream. ### 7. Stick to the schedule Meetings need a designated start and end time, and both need to hold. When team members know a meeting will end on time, they can plan their day around it. When meetings routinely run over, the calendar becomes a source of anxiety rather than a coordination tool, and participants begin protecting themselves by booking buffer time after every slot. Post-meeting anonymous pulse surveys embedded in follow-up communications give leaders a faster feedback loop on whether meetings are perceived as well-run and worth attending. Per Workday Peakon Employee Voice data, engagement metrics reveal warning signs up to nine months before an employee leaves — and meeting fatigue is one of the early signals pulse tools are designed to surface before it becomes attrition. Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback; brief, consistently followed-up surveys on meeting quality are one concrete mechanism for making that listening visible. ## Making outcomes stick after the meeting ends The last two practices address the gap between what happens in a meeting and what actually changes because of it. ### 8. Keep everyone engaged When meetings run long, attention deteriorates predictably. Passive attendance — being present but not expected to contribute — is a meeting design failure, not an individual motivation failure. Structuring meetings so every participant has a clear role throughout produces different outcomes than structuring them so a few people present while others observe. Per McKinsey research, 81% of leading companies effectively use data and analytics tools. Applying that mindset to meetings — through read receipts on shared materials, acknowledgment tracking on action items, and open-rate data on follow-up posts — gives leaders concrete evidence of whether meetings are producing behavior change after participants leave the room. Per Unily research, only 24% of frontline workers feel their feedback from customer interactions is heard by leadership, which underscores why measurable follow-up on meeting outputs matters as much as engagement during them. ### 9. Review action items and close the loop Meetings without documented action items are conversations, not decisions. Briefly reviewing the outputs of the previous meeting at the start of the next provides continuity — and makes explicit that what was decided is being tracked. When action items disappear after a meeting, participants learn quickly that committing to deliverables in a meeting carries no consequence. Modern [performance management](/solutions/performance-management) software can capture meeting minutes, assign action items with owners and deadlines, and surface them to participants who could not attend. Per Enterprise Apps Today 2022, 60% of high-performing firms report increased performance when employees are recognized — and closing every meeting with clear, attributed action items is one of the simplest forms of recognition: it signals that what was said mattered and will be followed through. ## Reaching employees who were not in the room For distributed or frontline workers who cannot always attend synchronous meetings, the objective shifts from shortening meetings to ensuring those employees receive outcomes, action items, and context through channels they can actually access. Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback. Per Unily research, only 24% feel that feedback is actually heard. Closing that gap starts with making meeting outputs — not just meeting invites — reachable to everyone. A post-meeting summary distributed through a mobile-accessible channel is not an administrative add-on. For a frontline employee who was not in the room, it is the meeting. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines how organizations are building the operational habits that translate meeting decisions into frontline action across distributed teams. ## Measuring whether meetings are getting better Most organizations treat meeting quality as a matter of culture and impression. The ones that actually improve it treat it as a measurable system. Three signals worth tracking before and after any meeting reform effort: average meeting length, the ratio of meetings to async updates in the same period, and post-meeting pulse survey participation rates. If the same questions surface in meetings month after month, the authoritative answer is not findable between sessions — that is a communication infrastructure gap, not a meeting facilitation problem. Declining pulse survey participation signals that employees do not believe their input will be acted on, which per Workday Peakon Employee Voice data is an early attrition warning visible up to nine months before someone leaves. For a broader view of how meeting culture connects to engagement and retention, [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) offers relevant context on what separates high-engagement organizations from the rest. ## When teams resist change Resistance to meeting reform is predictable in organizations where meeting density has become a signal of inclusion or importance. The most effective approach is to start with one change: a hard stop time, a shared agenda template, or a standing rule that any update deliverable as a written post does not become a meeting. Framing fewer, shorter meetings as a respect-for-time policy rather than a cost-cutting exercise reduces pushback. Piloting the change with one team and sharing the results gives skeptics concrete evidence before a wider rollout. The goal is not fewer meetings for their own sake — it is meetings that produce decisions, distribute outcomes to everyone who needs them, and leave participants with enough time and focus to act on what was decided. --- # How Customers Use The MangoApps Projects Module **Author:** April Thomas **Published:** 2018-11-13 **Category:** modules-features   At MangoApps, we believe in clear, helpful, and informative communication that makes understanding our products easy. We want prospective clients to perfectly visualize how MangoApps can work with them. So, we’ve put together a few examples of our popular projects module. To protect our client’s confidentiality, all business names have been withheld, but every illustration comes […] # How Customers Use The MangoApps Projects Module At MangoApps, we believe in clear, helpful, and informative communication that makes understanding our products easy. We want prospective clients to perfectly visualize how MangoApps can work with them. So, we've put together a few examples of our popular projects module. To protect our client's confidentiality, all business names have been withheld, but every illustration comes from a real MangoApps customer. As you read through each example, try to think about your own organization and how the MangoApps Projects Module can help you. The five use cases below span SaaS, retail, marketing, HR, and athletics — and each one illustrates a distinct way teams use project workspaces to collaborate, track progress, manage knowledge, and protect sensitive work. ## Collaborate On Common Goals One of our Software as a Service (SaaS) clients uses the projects module to facilitate peer-to-peer collaboration throughout the organization. Our client regularly develops and updates new software and is always trying to improve employee engagement. The MangoApps Projects Module gives employees a designated space where they can communicate, brainstorm, and collaborate together — functioning as a structured [teamwork management](/key-features/workspaces) hub rather than a loose collection of chat threads or email chains. ## Manage And Track Progress A customer in the retail industry uses the project module during the set-up and development of brick and mortar stores. Developing retail stores is a complicated and detailed process, and many of the steps need to be completed in a specific order. Establishing a new store can also be delayed by permit setbacks, product delays, and other unpredictable external factors. These unexpected or uncontrollable issues usually mean quick adjustments or changed plans. The MangoApps Projects Module lets administrators outline schedules, update tasks, [track progress](/solutions/task-management), and communicate with employees. This allows everyone to complete tasks on time and better prepare for a successful store opening. For a closer look at how distributed retail teams coordinate across locations, see [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling). ## Simplify Knowledge Transfer A marketing company utilizes the project module whenever project members are transferred. This company works with several high-end clients whose marketing needs are fast-paced and incredibly flexible. As a result, projects are often adapted as their needs change and grow. For our marketing client, regularly changing and adapting project outcomes and goals also means regularly adding or changing project members. When new employees join, they can access previous project history through the MangoApps Project Module's searchable history. This helps new members get up to speed without taking time away from other project members. This knowledge-transfer challenge is more widespread than most teams realize. Per McKinsey, employees spend an average of 2.5 hours daily searching for information — time that compounds quickly when project context is scattered across inboxes and shared drives. Treating project workspaces as active knowledge management tools, rather than just task lists, directly addresses that drain. MangoApps also supports AI-powered semantic search within projects, which surfaces relevant historical decisions and documents even when employees don't know the exact file name or keyword — a meaningful step beyond basic keyword search in conventional knowledge management systems. One organization reported a 60% reduction in repeated questions after deploying a searchable knowledge base within project workspaces. Project workspaces with role-aware permissions also automatically update when employees change roles or are offboarded, preventing stale access to sensitive project content — a gap that manual knowledge and knowledge management processes frequently leave open. ## Protect Sensitive Assignments An HR client often has to handle coworker disagreements, disability accommodations, harassment reports, and other sensitive assignments that need to be discussed confidentially and resolved discreetly. The MangoApps Projects Module allows them to create hidden projects where invited members can view or contribute to its contents. This gives the HR team a confidential place to discuss relevant details and create any necessary tasks or action items. Hidden projects allow HR members to address important issues while maintaining confidentiality and encouraging a happy company culture. For HR teams navigating complex workforce situations, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) offers additional context on how leading organizations are structuring sensitive workflows. ## Manage Specific Modules An athletic club uses projects to share specific schedules, organize sports teams, and manage different training modules. Club members can participate in different sports teams and tournaments throughout the year. The MangoApps Projects Module gives coaches, trainers, and other admins a designated space for their team where they can communicate updates, include helpful information, and activate additional module features like home workouts, player stats, practice schedules, or tournament brackets that might not be needed in other areas of MangoApps. This helps athletes throughout the club get the most out of their membership and stay on top of their training with the unique and specific modules they need. No-code workflow automation can handle routine project approvals, task assignments, and status updates within these specialized workspaces without requiring IT involvement — making it practical for non-technical admins like coaches or club managers to run their own SOP operations independently (per Beekeeper and Akumina product documentation). ## How Does the MangoApps Projects Module Compare to Tools Like Asana or Monday.com? This is one of the most common questions prospective customers ask. The core difference is context: standalone project tools like Asana or Monday.com manage tasks in isolation, while the MangoApps Projects Module lives inside a unified employee experience platform. That means project conversations, files, announcements, and [goals management](/key-features/goals-management) all exist in the same environment where employees already communicate — reducing the context-switching that fragments work across multiple apps. Additionally, MangoApps project workspaces can be extended with HRIS and LMS integrations to sync team rosters, training completions, and compliance records directly into project workspaces (per MangoApps integrations page and Beekeeper product documentation) — a capability that pure-play project tools typically require third-party middleware to replicate. For organizations evaluating intranet and employee experience platforms more broadly, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarking across vendors. For frontline and remote workers specifically, mobile access matters. Per Banner Health's internal employee poll, 55% of employees want intranet access from a mobile device and 61% want access outside the work VPN — needs that a projects module embedded in a mobile-first platform addresses directly, unlike desktop-centric project tools. ## How Do I Get Started With the Projects Module? Setup does not require IT configuration for most use cases. Admins can create a new project workspace, define member roles and permissions, activate the specific module features relevant to their team (task lists, trackers, file libraries, etc.), and invite members — all from within the MangoApps interface. [Trackers and workflows](/key-features/trackers-workflows) can be configured without code to automate recurring approvals or status updates. One organization achieved a 91% platform usage rate after an 8-week rollout across a 40,000-employee workforce, which suggests that adoption friction is manageable when the tool fits naturally into existing workflows. For teams replacing a legacy intranet or SharePoint environment, [Frontline Intranet Requirements: A Practical Checklist for Replacing SharePoint](/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) outlines the key capability gaps to evaluate before migrating project content. ## What to Do Next The five use cases above — SaaS collaboration, retail store development, marketing knowledge transfer, HR confidentiality, and athletic club management — each represent a different answer to the same underlying question: how do teams organize work, protect context, and keep everyone aligned without losing information along the way? Per APQC, Fortune 500 companies lose an estimated $31.5 billion annually to knowledge loss, and per McKinsey, employees spend 2.5 hours daily searching for information. A structured project workspace with searchable history, role-aware permissions, and integrated workflows directly reduces both costs. MangoApps products are designed to be personalized, and we love to see how companies use them to fit their different needs. We are always excited to work with our clients and are dedicated to helping them communicate and collaborate more effectively and achieve greater success. To see how the Projects Module would work for your specific industry and team size, schedule a personalized demo with us today. --- # 5 Employee Engagement Ideas For a Stronger Company Culture **Author:** Anna Carriveau **Published:** 2018-11-08 **Category:** employee-engagement Employee engagement is a pillar in building a strong company culture. Unfortunately, companies are falling incredibly short. Engaging your employees is key to improving company productivity, profit, and overall success. So how can your company create a thriving workplace culture? Here are the 5 best employee engagement ideas to increase participation, promote emotional involvement, and […] ## 5 Employee Engagement Ideas For a Stronger Company Culture Employee engagement is a pillar in building a strong company culture. Unfortunately, companies are falling incredibly short. Engaging your employees is key to improving company productivity, profit, and overall success. So how can your company create a thriving workplace culture? **Here are the 5 best employee engagement ideas to increase participation, promote emotional involvement, and build a stronger company culture:** ### #1: Improve Internal Communication Almost half of all personnel problems within an organization can be traced back to poor communication. Unclear or inappropriate communication causes employees to become frustrated and to disengage from their environment. As a result, it creates a culture where coworkers and employees no longer try to communicate together. Internal Communication and HR need to step up their efforts in providing helpful and straightforward communication material. This can be done through emails, newsletters, or other forms of communication. Internal communication should focus on creating and maintaining an emotional connection, not just be full of office jargon or rules to be followed. One underused lever: personalized communications targeted by role, location, or team. When employees receive information relevant to their specific context rather than company-wide blasts, engagement with that content rises measurably. It doesn't happen overnight, but companies can change their communication practices to encourage employee engagement and participation, creating a stronger company culture. For a forward-looking view of what's shifting in this space, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) is a useful reference. It's also worth noting that not every employee has a corporate email address or a fixed desk. Per Emergence Capital, 80% of the global workforce is deskless—meaning frontline and remote employees are often excluded from communication strategies built around email and desktop intranets. Engagement tactics must be differentiated by work context, not applied uniformly. ### #2: Increase Company Collaboration Effective employee engagement depends on a culture of increased collaboration. Employee engagement software can help employees communicate together by giving them a wide-reaching technological medium. These tools provide internal social media-like portals, file sharing, project collaboration ecosystems, and a wide variety of internal employee collaboration tools. One caution worth raising: adding more tools without consolidating existing ones can backfire. Employees who switch between disconnected systems lose over 4 hours per week, meaning tool consolidation is itself an engagement lever—not just a productivity one. Per IDC, employees already spend 2.5 hours per day searching for information; fragmented platforms compound that cost. A unified employee experience platform reduces that friction and keeps employees in a single environment where collaboration happens naturally. Increasing collaboration gets employees engaging with each other in both their physical location and throughout the company. As employees work together, they discover new friendships and have positive experiences. This often directly correlates to a stronger company culture. To understand how [solutions/employee-engagement](/solutions/employee-engagement) platforms support this in practice, the MangoApps case study on [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) shows what structured collaboration looks like at scale. ### #3: Invest In Health And Wellness Keeping a couple of exercise bikes and treadmills in a makeshift office gym isn't a great employee health initiative. In order to become more invested, employees need to feel that the company cares about their wellbeing and needs. In addition to providing insurance, companies should actively invest in programs that support a healthy and well-adjusted lifestyle. This could be subsidized gym memberships, health programs, or even stress-busting engagement sessions like office yoga. Participating in healthy activities encourages happiness and creativity. As employees participate in office contests and programs, they will get the chance to engage with coworkers outside of the office. Their teams and departments will become more united through a positive culture of health and wellness. Pairing wellness investment with employee engagement training—structured programs that teach managers how to recognize stress signals and respond—amplifies the impact beyond physical perks alone. ### #4: Foster Inter-Office Networking An organization can often span multiple office locations and time zones. Despite geographical distance, there is always room for nurturing healthy friendships between inter-office employees. In addition to planning fun get-together activities within each office, using employee collaboration software allows companies to create intranets and messaging platforms for all their employees to connect and converse. However, intranet adoption is a real challenge. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use intranet tools daily—averaging just six minutes per day according to SWOOP Analytics. That means the platform itself must be worth returning to: mobile-accessible, easy to navigate, and relevant to each employee's role. Interacting with people from different regions creates a stronger company culture on a corporate scale, but only when the tools actually get used. The [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides useful context on what separates high-adoption platforms from low-adoption ones. ### #5: Offer Recognition And Rewards A decent salary is no longer a direct indicator of employee loyalty. Today's workforce has all kinds of high-paying jobs to pick from. Organizations need to stand out by showing their care and commitment to employees. In addition to a good salary, companies should provide recognition for employee performance and success. This recognition could be in the form of rewards, benefits, perks and more. The financial case for getting this right is concrete: replacing a disengaged frontline employee costs between $4,400 and $15,000, making engagement investment directly quantifiable as a retention ROI argument. Employees need the opportunity to recognize their coworkers through some form of praise and recognition. Recognizing employees for their success shows them that engagement and hard work will pay off, and encourages a stronger company culture. Connecting recognition programs to [solutions/performance-management](/solutions/performance-management) systems ensures that acknowledgment is tied to measurable outcomes, not just sentiment. ### Building A Stronger Company Culture With MangoApps Employee engagement is the untapped opportunity for building a stronger company culture and improving corporate success. Improved engagement leads to a happier workspace and ultimately a better experience for everyone. The results from organizations that commit to structured engagement programs are measurable: OU Health achieved 87% workforce engagement within months of launching a branded employee app, and British Airways recorded a 30-point engagement score increase after deploying a modern employee experience platform—providing a concrete benchmark for what structured engagement programs can achieve. At MangoApps we help companies boost employee engagement and develop company culture through collaboration tools, project management, HR resources, enterprise social networks, and a unified mobile experience that reaches every employee—whether they sit at a desk or work on the front line. To see how your company can benefit from an engaging modern intranet, contact us to schedule a demo today. --- ### How Do I Measure Whether These Engagement Ideas Are Working? Implementing engagement initiatives is only half the equation—knowing whether they're moving the needle is the other. The most direct method is a structured employee engagement survey or employee engagement questionnaire administered before and after a program launches, establishing a baseline and tracking change over time. Pulse surveys (short, frequent check-ins) complement annual surveys by catching sentiment shifts in real time. Quantitative signals like intranet login rates, collaboration tool activity, and recognition program participation rates serve as leading indicators between formal survey cycles. For a broader view of how HR teams are approaching measurement in 2026, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers emerging frameworks for tracking engagement ROI. ### What Is the ROI of Employee Engagement Investment? The return on employee engagement investment is most clearly visible in retention costs, productivity, and customer outcomes. As noted above, replacing a disengaged frontline employee costs between $4,400 and $15,000—so even modest improvements in retention among a frontline workforce of 500 employees can represent hundreds of thousands of dollars in avoided replacement costs. Beyond retention, per IDC, employees spend 2.5 hours per day searching for information; reducing that through better communication and collaboration tools translates directly into recovered productive hours. Organizations in high-turnover sectors like retail and hospitality often see the fastest payback periods—see [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) for a sector-specific look at how operational and engagement improvements compound. The [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace) report provides additional benchmarks linking engagement levels to business unit performance. ### How Do I Get Leadership Buy-In for Employee Engagement Programs? Leadership buy-in typically requires translating engagement from an HR concept into a business metric. The most effective approach is to anchor the conversation in costs leadership already cares about: turnover expense, productivity loss, and customer satisfaction scores. Presenting a pilot program with defined success metrics—engagement survey scores, tool adoption rates, retention rates in a target department—gives executives a low-risk way to evaluate impact before committing to company-wide investment. Framing employee engagement training and employee engagement courses as capability-building investments (similar to technical training) rather than culture initiatives also tends to resonate with finance-oriented stakeholders. For organizations navigating complex workforce structures, [Managing a Unionized Workforce Is Different. Your Software Should Be Too](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) addresses how to build the case in environments where engagement programs face additional structural constraints. --- # How Customers Use The MangoApps Posts Module **Author:** April Thomas **Published:** 2018-11-01 **Category:** modules-features At MangoApps, we love to help our customers discover how different features can benefit their specific needs. But we also know that for prospective clients, visualizing how MangoApps will help your business can be a bit difficult. So we wanted to simplify that for you! The examples in this article illustrate one of our most widely […] ## How Customers Use The MangoApps Posts Module At MangoApps, we love to help our customers discover how different features can benefit their specific needs. But we also know that for prospective clients, visualizing how MangoApps will help your business can be a bit difficult. So we wanted to simplify that for you! The examples in this article illustrate one of our most widely used and core product features, the MangoApps Posts Module — a structured publishing layer that functions as the content backbone of a modern [employee intranet](/articles/mangoapps-2026-forrester-wave-intranet-platforms). Out of respect for our customers' privacy, all business names have been withheld, but we promise that all of our examples are genuine, real-life applications. As you read through the examples below, try to think about your own company and visualize how incorporating a posts module will benefit you. For context on why this matters at scale: per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use intranet tools daily. Per SWOOP Analytics, the average employee spends just six minutes per day in intranet tools. The Posts Module is designed to close that gap by surfacing relevant, categorized content where employees already work — on any device, without a VPN. ## Create And Send Newsletters One of our distribution clients uses the MangoApps Posts Module to create and distribute newsletters to employees while they're in the field. With truck drivers spread out across the country, communication can be difficult. Newsletters and announcements are easy to access from a laptop, phone, or any other mobile device. This helps keep distribution on time and drivers informed about updates, policies, and changes in real time. This use case directly addresses the deskless workforce problem: per Emergence Capital, 80% of the global workforce is deskless. Frontline employees can access posts and communications without a corporate email address or VPN, on personal iOS or Android devices with offline support for critical content — meaning a driver in a remote area still receives the same policy update as a headquarters employee. Poor communication with frontline workers carries a measurable cost: replacement costs for frontline employees range from $4,400 to $15,000 per worker, making reliable, mobile-first communication a direct retention investment. ## Organize And Find Content An EDU client uses the Posts Module to store and organize classroom information. This helps teachers and staff find projects, activities, and resources for the classroom. Information is archived, categorized by subject and grade level, and is all easily searchable by keywords or titles. The MangoApps Posts Module gives educators a space to share and search for ideas and resources — functioning as one of the core [tools of knowledge management](/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) that keeps institutional knowledge accessible rather than siloed in individual inboxes. Posts also give teachers a chance to collaborate with their peers regardless of geographical location, helping them stay motivated and inspired by colleagues no matter where they are located. This matters because, per IDC, employees spend an average of 2.5 hours per day searching for information. Structured categorization and archiving directly address the failure mode where traditional intranet content becomes stale and ungoverned without structured publishing workflows. The Posts Module's tagging and archiving system ensures content remains findable long after it is first published. For a deeper look at how learning resources can be embedded into daily workflows, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). ## Share Relevant Company Info Another client, a manufacturing and transportation company, uses the Posts Module for internal enablement. The organization provides employees with training resources, company news, best practices, and important updates both internally and throughout the industry. The Posts Module makes it easy for employees to find resources quickly, allowing them to stay self-sufficient. This, in turn, increases job satisfaction, speeds up work, and simplifies the training process. Their posts also keep employees up-to-date about changes and innovations in the transportation technologies industry, helping them become more knowledgeable and invested in the field. Organizations that have replaced siloed communication tools with a unified posts and content layer report consolidating 200+ systems into a single employee dashboard, per a MangoApps case study (TeamHealth). The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) explores how unified content publishing is reshaping internal enablement across industries. ## Keep Everyone Up-To-Date A financial management client has found the Posts Module incredibly helpful for communicating travel and expense reports in real time. Posts keep team members aware and prepared for financial updates, processed charges, company spending, budget restrictions, and more. Posts also give employees a centralized place to find important and regularly changing financial information, allowing them to stay informed and better help others stay within and adapt their financial goals. MangoApps Posts also acts as a financial history and analysis tool, keeping an easy-to-access record of past financial actions and making financial patterns, policies, and adaptations easier to understand and change for the future. For organizations in regulated industries, structured publishing with version history and searchable archives is a core knowledge management tool — not just a convenience. Learn how MangoApps supports [financial industry](/industries/financial) communication and compliance workflows. ## Highlight Company Culture With MangoApps Posts, one of our non-profit clients received the ability to strengthen their organization's culture. Posts have given them a place to share success stories, discuss fundraising ideas, ask questions, and encourage others. As a non-profit organization, they depend heavily on the time, talents, and resources of volunteers across the country. The MangoApps Posts Module has helped bring widespread volunteers together and has allowed them to demonstrate their mission in action. Highlighting success across the organization has brought strangers together through a common cause. This ultimately results in a close-knit community with a united purpose. Engagement outcomes from similar deployments are measurable: an 87% workforce engagement rate was achieved within months of launching a branded communications app in the OU Health case study. The [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study) case study shows how a unified posts and communications layer can produce comparable culture and engagement results across a geographically distributed workforce. ## What to Expect When You Implement the Posts Module Decision-makers evaluating the Posts Module typically want to understand what configuration looks like before committing. Here is what the implementation path generally involves: - **Permissions and audience targeting:** Posts can be scoped to specific groups, departments, locations, or the entire organization. Administrators control who can publish, who can comment, and which audiences receive which content streams. - **Categorization and tagging:** Content is organized by custom categories and tags, making it searchable by keyword, topic, or date — directly addressing the 2.5-hours-per-day search problem cited by IDC. - **Mobile and frontline access:** The Posts Module is accessible via the MangoApps [employee app](/solutions/employee-app) on personal iOS and Android devices, with no corporate email or VPN required — critical for the 80% of the global workforce that is deskless, per Emergence Capital. - **Integrations:** Posts connects with the broader MangoApps platform, including notifications, analytics, and AI-powered search, so employees surface relevant content without manual browsing. - **Governance and archiving:** Published posts are automatically archived and remain searchable, preventing the content decay that affects ungoverned intranet environments. For a structured approach to intranet governance, the [Intranet Governance Plan: A Practical Model for a Modern Intranet](/articles/sharepoint-server-2016-2019-replacement-intranet-governance-plan) is a practical starting point. ## Frequently Asked Questions About the Posts Module ### How does the Posts Module differ from a standard intranet news feed? A standard intranet news feed typically pushes content to all employees without targeting or categorization. The MangoApps Posts Module functions as a structured knowledge management tool: content is tagged, categorized, and scoped to specific audiences, so a truck driver in the field sees relevant operational updates while a finance team member sees budget and expense content. Posts also integrates with MangoApps' AI-powered search, so employees surface the right content without manual browsing — a meaningful improvement over the six-minute average daily engagement that SWOOP Analytics reports for traditional intranet tools. ### Can the Posts Module support industries with compliance or governance requirements? Yes. The archiving and version history features make the Posts Module suitable for regulated industries including healthcare and financial services. Published content is retained and searchable, creating an auditable record of communications. For healthcare-specific workflows, see how MangoApps supports [healthcare](/industries/healthcare) organizations. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) also evaluates MangoApps against governance and compliance criteria across intranet platforms. ### What ROI metrics should I expect? The most commonly cited outcomes from Posts Module deployments include reduced time spent searching for information (addressing the IDC-cited 2.5-hour daily average), improved frontline retention (given replacement costs of $4,400–$15,000 per worker), and measurable engagement lift — with deployments like OU Health reporting 87% workforce engagement within months of launch. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides additional benchmarks for measuring the business impact of unified employee communications. ## Learn More At MangoApps, we love how personalized our products are and we love to see the new and unique ways that companies use them to accomplish goals and improve collaboration. Every individual client can customize our services to benefit their specific needs. In addition to our out-of-the-box features, we are always happy to work with clients to create unique and specific solutions. The five use cases above — newsletters for deskless workers, knowledge organization for educators, internal enablement for manufacturing, financial communications, and culture-building for non-profits — represent a fraction of how the Posts Module is deployed. What they share is a common outcome: employees spend less time searching for information and more time acting on it. If your organization is evaluating whether a structured posts and [employee communications](/solutions/employee-communications) layer belongs in your intranet stack, the configuration flexibility, mobile-first access, and governance features described above give you a concrete basis for that decision without requiring a demo to understand the fundamentals. To hear additional examples or discuss how MangoApps can address your specific use case, contact us or schedule a personalized demo today. schedule demo --- # How To Refresh Employee Rewards and Recognition **Author:** Anjali **Published:** 2018-10-30 **Category:** employee-engagement Successful companies understand that employees are the core of their business. Highly engaged and satisfied employees work with an excited and positive energy that often helps transform business and boost profits. A workforce that feels a personal rapport with management is also more likely to become productive and engaged. Positive employee engagement happens when employers […] # How To Refresh Employee Rewards and Recognition Employee rewards and recognition programs directly affect retention, engagement, and team performance — but most programs underdeliver because they rely on outdated formats, ignore frontline workers, and treat recognition as a morale activity rather than a business signal. This guide covers eight concrete ways to refresh your approach, with attribution to current research so you can build a case internally. The core problem: only 23% of employees strongly agree their recognition is meaningful, according to Workhuman and O.C. Tanner Institute research. Frequency alone is not enough. Personalization, peer involvement, and behavioral specificity are what separate programs that reduce turnover from programs that produce plaques nobody remembers. For a broader view of where workforce programs are heading, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers recognition alongside the other engagement levers HR teams are prioritizing this year. --- ## Why Most Recognition Programs Stop Working Recognition programs decay for predictable reasons: - **Generic formats.** "Employee of the Month" awards that rotate without clear criteria lose credibility quickly. Recognition tied to specific, measurable behaviors — safety compliance rates, customer satisfaction scores, on-time delivery — sustains engagement longer than generic nominations, per Workhuman and O.C. Tanner Institute annual recognition research. - **Manager-only initiation.** Programs that rely exclusively on managers miss the contributions peers see most clearly. Recognition programs that include peer-to-peer recognition are significantly more likely to drive meaningful engagement improvements, because peers often have the most direct visibility into day-to-day contributions, according to SHRM and Workhuman research on peer recognition effectiveness. - **Desktop-only delivery.** Approximately 80% of the global workforce is deskless (per Emergence Capital), meaning frontline employees in retail, hospitality, manufacturing, and logistics rarely have access to company email or desktop tools. A recognition program that lives only in an intranet or email inbox structurally excludes the majority of your workforce. - **No connection to retention data.** When recognition participation is not tracked by department or location, HR teams cannot identify which pockets of the organization are disengaging before those employees leave. Companies with highly effective recognition programs see 31% lower voluntary turnover than those with ineffective programs, according to Workhuman and O.C. Tanner Institute research. That is the business case for getting the structure right. --- ## 8 Ways To Improve Employee Rewards and Recognition ### 1. Replace Generic Awards With Behavior-Tied Recognition Employee of the Month formats are familiar, but they work best when the selection criteria are transparent and tied to specific behaviors the organization wants to reinforce. Define two or three measurable behaviors — response time, safety record, peer feedback scores — and make those the public basis for selection. Employees who understand *why* a colleague was recognized are more likely to replicate the behavior than those who see a name on a plaque without context. MangoApps supports custom award categories so organizations can build recognition around their own operational priorities rather than defaulting to a single monthly slot. ### 2. Add Peer-to-Peer Recognition as a Program Pillar Manager-initiated recognition captures a fraction of the contributions happening in any organization. Peer recognition closes that gap. When employees can recognize colleagues directly — through a public post, a badge, or a point award — the volume and specificity of recognition increases substantially. Peers have the most direct visibility into day-to-day contributions: who stayed late to help a teammate, who caught an error before it reached a customer, who onboarded a new hire without being asked. Building peer recognition into your program structure, rather than treating it as optional, is one of the highest-leverage changes most organizations can make. See how one organization operationalized this: [From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program). ### 3. Deliver Recognition to Frontline Workers via Mobile Frontline and deskless workers are systematically underserved by traditional recognition programs because they lack access to company email or desktop tools, making mobile-first recognition delivery a structural requirement rather than a nice-to-have, according to Beekeeper and frontline workforce research across the product category. With 80% of the global workforce deskless (per Emergence Capital), any recognition program that requires a desktop login or a company email address is excluding the majority of employees from the start. MangoApps delivers recognition through a mobile app that does not require a company email address or VPN access, which means a warehouse associate, a hotel housekeeper, or a retail floor employee can receive and give recognition in the same flow as a desk-based colleague. For organizations in customer-facing industries, this gap is especially consequential. The [industries/retail](/industries/retail) and [industries/hospitality](/industries/hospitality) pages cover how recognition and communication reach frontline teams specifically. ### 4. Build a Point-Based Recognition Program With Redeemable Rewards Point-based programs give employees a running record of their contributions and create a tangible connection between behavior and reward. Points can be awarded for specific actions — completing a safety training module, assisting a teammate, maintaining a streak of on-time submissions — and redeemed for incentives based on company policy. This format also generates participation data. Which employees are earning points? Which departments have low participation? That data is more actionable than an annual engagement survey score. ### 5. Use Recognition Data as an Attrition Early-Warning Signal Most organizations treat recognition as a motivational output. A more useful frame is to treat recognition participation data as a leading indicator of disengagement risk. When recognition activity drops in a specific department or location — fewer peer nominations, lower point redemption, declining badge activity — that pattern often precedes attrition by weeks or months. Integrating recognition data with HRIS platforms allows HR teams to surface participation gaps by department or location, turning recognition into a leading indicator of attrition risk rather than a lagging morale metric, according to MangoApps product positioning and competitor HRIS-integration analysis across multiple vendors. Employees who receive recognition are 45% less likely to leave within two years, per Workhuman and O.C. Tanner Institute research. Tracking *who is not receiving recognition* is therefore as important as tracking who is. ### 6. Recognize Team and Department Performance, Not Just Individuals Team-level recognition reinforces collaboration and creates shared accountability for outcomes. When a department hits a quality target or a project team delivers ahead of schedule, recognizing the group publicly — not just the manager or the loudest contributor — signals that the organization values collective effort. Team awards also reduce the social friction that individual awards can create. A colleague who did not win Employee of the Month can still be part of a recognized team. ### 7. Celebrate Personal Milestones and Life Events Recognition that extends to personal milestones — work anniversaries, certifications, volunteer activities, life events — signals that the organization sees employees as people rather than job functions. Birthdays and work anniversaries posted to a shared newsfeed, where colleagues can comment and react, create low-effort moments of connection that accumulate over time. This is especially relevant for distributed or hybrid teams where informal hallway recognition does not happen naturally. ### 8. Use Gamification to Sustain Ongoing Participation Gamification mechanics — points, levels, badges, leaderboards — keep recognition visible and ongoing rather than episodic. Employees earn points for platform contributions: answering a colleague's question, uploading a resource, completing a task. Badges mark specific achievements. Leaderboards create friendly visibility into who is contributing. The key is that gamification should reinforce the behaviors the organization actually values, not just platform activity for its own sake. Badges for safety compliance or knowledge-sharing contributions are more meaningful than badges for logging in. --- ## How Do You Measure Whether a Recognition Program Is Working? The most common mistake is measuring recognition by volume — how many awards were given, how many points were distributed — without connecting those numbers to outcomes. More useful metrics: - **Participation rate by department and location** — identifies coverage gaps before they become attrition gaps - **Voluntary turnover rate in recognized vs. unrecognized cohorts** — quantifies retention ROI - **Employee engagement survey scores** correlated with recognition frequency — surfaces whether recognition is landing as meaningful - **Time between recognition events** — long gaps in an employee's recognition history are a disengagement signal Only 23% of employees strongly agree their recognition is meaningful (Workhuman / O.C. Tanner Institute). Measuring *meaningfulness* — through pulse surveys or qualitative feedback — is as important as measuring frequency. --- ## What Makes Recognition Feel Meaningful Rather Than Performative? Three factors consistently separate recognition that employees remember from recognition that feels like a checkbox: 1. **Specificity.** "Great job this quarter" is forgettable. "You caught the billing error that would have cost us the client relationship" is not. Recognition tied to a specific action or outcome lands differently than generic praise. 2. **Timeliness.** Recognition delivered within days of the behavior is more effective than recognition delivered at an annual review. The closer the recognition is to the action, the clearer the signal. 3. **Audience.** Public recognition — visible to peers, not just the manager — amplifies the signal. It also models the behavior for the rest of the team. These principles apply whether recognition is manager-initiated, peer-initiated, or system-generated through a points program. --- ## Getting Started: A Practical Checklist If your current recognition program needs a refresh, start here: - [ ] Audit which employee populations are currently excluded from recognition (frontline, part-time, remote, non-email users) - [ ] Define two or three specific behaviors you want recognition to reinforce — not just "good work" - [ ] Add a peer-to-peer recognition channel if you only have manager-initiated awards - [ ] Confirm your recognition platform is accessible via mobile without a company email or VPN - [ ] Set up participation tracking by department and location so you can identify gaps - [ ] Review recognition data quarterly alongside voluntary turnover data to test the correlation For organizations evaluating employee experience platforms, the [solutions/employee-engagement](/solutions/employee-engagement) page covers how MangoApps structures recognition alongside communication and operational tools in a single environment. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) also covers how recognition fits into broader workforce operations strategy for organizations managing distributed or frontline teams. --- # How To Successfully Incorporate Remote Employees **Author:** Anna Carriveau **Published:** 2018-10-25 **Category:** workplace-productivity Offering employees remote and work-from-home opportunities is now a business necessity. For many potential new hires, the ability to work remotely is actually a more influential factor than the starting salary. Today’s employees feel that remote work provides a better environment.  A study conducted by Flexjobs found that over 76% of employees preferred to work […] # How To Successfully Incorporate Remote Employees Offering employees remote and work-from-home opportunities is now a business necessity. For many potential new hires, the ability to work remotely is actually a more influential factor than the starting salary. Today's employees feel that remote work provides a better environment. A study conducted by Flexjobs found that over 76% of employees preferred to work on important projects away from the office. Remote opportunities give employees an atmosphere with less coworker interference. This contributes to a more comfortable environment, and a chance for employees to increase their work-life balance. If your organization is reluctant to provide a flexible or work-from-home option, it's time to change. It is also worth noting that hiring remote employees can be profitable for companies too — and that poor remote integration carries a measurable cost: replacing a single frontline or remote employee costs between $4,400 and $15,000 per person, making a well-structured remote program a direct cost-avoidance lever, not just a perk. **Here are the top three ways that remote employees can benefit your business:** #### Access To Top Talent Employers always want the best workforce for their business, but in the past have been limited by geographic location. Offering remote work provides employers with access to candidates from all over the world. This greatly diversifies their options and allows them to find someone who is truly the perfect fit. Having remote employees in a business is mutually beneficial for both parties. It allows businesses to operate in office locations that work well for them while still having access to high-quality workers, and it gives employees access to jobs that they want without having to compromise their physical location. #### Diversity Of Workforce Remote work gives employers access to workers from anywhere in the world. The diversity provided by remote workers can be as broad as coworkers from another country or as narrow as a colleague from another city or state. More diversity in a work environment almost always leads to increased perspectives and original solutions. Internal diversity also allows organizations to test out international ideas in the controlled and localized area of your organization. #### Increased Cost-Benefit In order to accommodate a growing workforce, businesses need to provide a large physical office. However, real estate prices are often expensive and can be a huge deterrent for business expansion. Physical offices need to be outfitted with supplies like computers, office furniture, etc. They also accrue maintenance costs such as cleaning, utilities, office supplies and other additional expenses. Over time, even the amount of money spent on a single employee can add up to a significant expense. Incorporating remote employees into an office reduces physical expenses and saves money for businesses to add other useful programs that will benefit both traditional and remote employees. ## Establishing a Successful Work Environment With Remote Employees Researchers expect that by 2027 close to 58% of US employees will work as freelancers at least part-time. The Gig Economy, as freelancers are more widely known, will be a real game changer for employment opportunities. So, what exactly do you do to ensure that your business is successful in incorporating remote employees? Here are three tips to help you get started. #### Create Effective Guidelines Allowing employees to work away from the office should be beneficial for everyone and should not put employers in a position where commitments are vague or unclear. At the same time, employers need to establish trust with remote employees and avoid the temptation to micromanage their work or time. Finding the right balance where employees have the freedom to work and expectations are well understood is critical for remote work success. Employers need to establish remote guidelines and expectations for critical components like communication, work quality, availability and other factors. Employers should also ensure that processes are in place to deal with policy or company violations appropriately. For a deeper look at how employee engagement connects to clear expectations and accountability, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the structural shifts shaping distributed workforce management this year. #### Use The Right Technology While the idea of remote employees is not new, the rapid growth of technology has greatly escalated its possibilities. In order to be successful, organizations must use the right tools to communicate well and work effectively. A unified [employee experience platform](/solutions/employee-engagement) — one that consolidates communication, file sharing, task tracking, and training into a single interface — is the practical solution for remote success, replacing the stitched-together tool sprawl that erodes the productivity gains remote work is meant to deliver. Employees switching between disconnected remote-work tools lose over four hours per week to context-switching alone. One access barrier that generic technology advice consistently overlooks: approximately 80% of the global workforce is deskless, per Emergence Capital, meaning many remote and frontline employees have no corporate email address and unreliable VPN access. Traditional intranet-based strategies fail this population — per Social Edge Consulting, nearly a third of employees never log in to the intranet and only 13% use it daily. Mobile-push and in-app alerts delivered through a no-email-required app are essential for reaching a distributed workforce where they actually are. For context on how leading organizations are rethinking internal communications infrastructure, see the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook). The right technology also closes the information-search gap: per IDC, employees spend an average of 2.5 hours per day searching for information — time that a well-structured employee experience platform can recover at scale. #### Build A Thriving Culture Having an effective globally or regionally disbursed team requires a specific company culture. Employees and managers alike need to embrace a culture of responsibility, self-motivation, teamwork and collaboration. This kind of attitude could be cultivated through frequent communication, shared commitments and continuous employee engagement activities involving both remote and in-office team members. Departments like internal communications and human resources could also play an active role in these efforts. Growing a common culture where every employee values transparency, respects time and realizes responsibility is vital for achieving remote success. For practical examples of how distributed teams in service-intensive environments maintain culture at scale, the [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study illustrates what this looks like in practice. ## How Do I Onboard Remote Employees Effectively? Onboarding is where remote incorporation either takes hold or breaks down. A structured remote onboarding program should cover three areas: access (ensuring the employee has the tools, credentials, and mobile app access they need on day one without requiring IT desk visits), context (sharing company values, team norms, and communication expectations in written, asynchronous formats), and connection (scheduling deliberate introductions with key colleagues across time zones rather than leaving relationship-building to chance). Because replacing a remote employee costs between $4,400 and $15,000 per person, investing in a thorough onboarding process is straightforward cost avoidance. Organizations that treat onboarding as a one-day orientation rather than a 30-to-90-day ramp consistently see higher early attrition among remote hires. Pairing new remote employees with an in-team buddy and using structured employee engagement questionnaires at the 30- and 60-day marks gives managers early signal on whether integration is succeeding before disengagement becomes a retention problem. ## How Do I Maintain Employee Engagement Across Distributed Teams? Incorporating remote employees is a setup task; sustaining employee engagement is an ongoing operational discipline. Organizations that treat engagement as a one-time onboarding checkbox rather than a measured, recurring process consistently underperform on retention and productivity. Three practices close the gap: - **Pulse surveys and employee engagement surveys on a regular cadence** — monthly or quarterly — give distributed teams a structured channel to surface friction before it compounds. Employee engagement questionnaires with five to ten targeted questions outperform annual surveys because they generate actionable data while context is still fresh. - **Visible recognition across time zones** — remote employees who are not physically present in an office are at structural risk of being overlooked in recognition moments. A unified platform that surfaces peer recognition in a shared feed counteracts this bias. - **Learning tied to daily work** — employee engagement training and development opportunities embedded in the flow of work, rather than scheduled as separate events, sustain engagement more effectively than periodic courses. For a detailed framework on this, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). For a broader view of how engagement trends are shifting in 2026, [Gallup's 2026 State of the Global Workplace: What It Means for HR](/articles/gallup-2026-state-of-the-global-workplace) provides relevant benchmarks for distributed workforce planning. ## How Do I Measure Whether Remote Integration Is Working? Successful remote incorporation is measurable, not just felt. The metrics that matter most fall into three categories: - **Adoption metrics**: What percentage of remote employees are actively using the communication and collaboration platform? A benchmark from a large enterprise deployment shows 90% frontline adoption within six months is achievable with the right mobile-first tooling — use this as a target, not a ceiling. - **Engagement metrics**: Track employee engagement survey scores, participation rates in company-wide communications, and recognition activity for remote employees specifically, not just as part of an aggregate score that can mask distributed-team gaps. - **Retention metrics**: Monitor 90-day and 12-month voluntary turnover for remote hires separately from on-site hires. Given the $4,400–$15,000 replacement cost per employee, a 5-percentage-point improvement in remote retention has a direct, calculable dollar value that justifies investment in employee engagement software and structured onboarding. Organizations that track these three categories together — adoption, engagement, and retention — have the data they need to iterate on their remote incorporation strategy rather than guessing. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides additional benchmarks for distributed workforce performance measurement. ## MangoApps The future of work is exciting and is now unrestricted by geographical constraints. At MangoApps, we provide a digital workplace platform that can help businesses continue to grow and embrace new work attitudes, ideas, and innovations. Schedule a demo with us today to learn more about how MangoApps can help your business integrate and incorporate remote employees. --- # 10 Reasons Companies Need To Use MangoApps Online Wikis **Author:** Anjali **Published:** 2018-10-23 **Category:** modules-features For most people, the first thing the word wiki brings to mind is the famous online encyclopedia Wikipedia. Wikipedia has completely changed the way information is consumed by people with highly varying backgrounds, views, interests, locations, and native languages. Searching for almost any term today almost always results in a related  Wikipedia link right at […] # 10 Reasons Companies Need To Use MangoApps Online Wikis Per IDC, employees spend an average of 2.5 hours per day searching for information they need to do their jobs. In a 40-hour workweek, that is nearly one full day consumed by navigation rather than work. Per SWOOP Analytics, the average employee spends only six minutes per day on intranet tools — which means the platform technically housing the information is not the one being used to find it. The knowledge exists. The delivery is broken. Wiki software is the answer most organizations reach for, and it works — when the implementation addresses the right set of problems. The deployments that fail do so for three predictable reasons: search that indexes file names rather than content, authentication that excludes frontline workers without corporate email, and no governance mechanism to keep information accurate after the launch event. These are not edge cases. They are the three structural weaknesses that separate wikis employees use from wikis they route around. ## Why conventional intranet infrastructure fails at knowledge delivery Per Social Edge Consulting, 91% of organizations operate an intranet. Nearly a third of employees never log in, and only 13% use it daily. These organizations did not fail to deploy knowledge tools — they deployed systems that went stale, and employees learned that asking a colleague was more reliable than searching. The failure is architectural. Email is designed for individual-to-individual communication, not group-accessible knowledge storage. Shared drives develop naming-convention chaos as organizations scale: two departments create overlapping folders, files get versioned through renamed copies, and the most recent policy document becomes indistinguishable from last year's draft. Knowledge accumulates but loses accessibility faster than it is created. Wiki platforms built for organizational knowledge have three structural advantages: content that is updated in place rather than versioned through renamed files, search that is accessible to everyone rather than dependent on knowing a file's location, and accountability structures that assign ownership to information so someone is responsible when it goes stale. The question is not whether wikis outperform email and shared drives for organizational knowledge — they do. The question is which wikis deliver on all three advantages in real deployments rather than only on paper. ## The search layer is the product Traditional wiki search indexes titles. A query that does not match the document name returns nothing. An employee who joined three months ago and does not know the internal naming convention for a policy finds nothing on a first search, a second search, and often gives up by a third. The policy exists; the search layer does not surface it. AI-assisted retrieval changes this by indexing content and intent. A natural language query — "how much notice do I need for a vacation request" — returns the correct policy document even if it is titled "Time Away Guidelines" and never uses the word "notice." For organizations with large or long-standing content libraries, this is the difference between a [knowledge management](/solutions/knowledge-management) platform that employees discover over time and one they abandon after a week. Deep content indexing extends this further: PDF documents, policy archives, HTML pages, and structured templates become searchable by what they contain rather than what they are called. Research cited in compliance documentation, procedures embedded in multipage files, and historical context stored in archived content all become accessible without requiring employees to know which file to open first. The adoption consequence is direct. Wiki tools that return dead-end searches train employees to work around them. When asking a colleague is reliably faster than searching, institutional knowledge migrates back to informal channels — and the wiki becomes a formality that employees have access to but practically never use. ## The access gap is larger than most deployments account for Per Emergence Capital, approximately 80% of the global workforce is deskless. In healthcare, retail, and field services, the share of frontline workers without corporate email addresses or assigned workstations approaches universality. Traditional wiki platforms are designed around the assumption of a laptop, a company email address, and IT-provisioned credentials. New frontline employees either wait for credentials before accessing onboarding documentation or borrow a colleague's device — neither creates a reliable knowledge access path. For shift-based workers whose onboarding coincides with high-volume periods, the IT ticket may take days to close, meaning the first week passes without structured access to the documentation they need. The organizational cost of this gap has a measurable proxy. Industry benchmarks place the cost of replacing a single frontline employee between $4,400 and $15,000 depending on role and industry. Employees who cannot access job documentation in their first weeks report lower confidence and leave at higher rates than those with immediate access. A [knowledge base](/key-features/knowledge-bases) that supports QR code enrollment, SMS verification, and personal device authentication reaches frontline workers on day one — before IT provisioning is complete and without requiring a corporate email address. This is not a convenience feature; it is the difference between a knowledge base that covers the full workforce and one that serves only desk workers while reporting adoption numbers across everyone. Platforms that meet this threshold consistently report higher total adoption figures because they are measuring access among employees who were previously excluded. An adoption rate that includes frontline workers is diagnostic — it identifies where content gaps and access gaps actually live. An adoption rate that excludes them only shows how desk workers use the system, which is not the knowledge delivery problem most organizations are trying to solve. ## Governance is what keeps wikis accurate past launch The most common wiki failure mode is not poor search or limited access — it is post-launch content degradation. Organizations invest heavily in launch content and almost nothing in what happens to content quality over the following 18 months. By month six, pages that were accurate on launch day have started to drift. By month 12, the most actively maintained sections are the ones that someone kept current through manual effort — which is exactly the behavior the wiki was supposed to eliminate. [Content governance](/key-features/content-governance-engine) addresses this at the structural level. Assigning a named owner to every page creates accountability: someone is responsible for keeping that section current, and when they leave the organization, ownership transfers and a review is triggered. Expiry flags schedule automated review prompts when content reaches a defined age. Administrator dashboards surface the health of the knowledge base before users discover degradation — showing which pages have no owner, which have not been reviewed in over a year, and which searches are returning zero results. Version history with full audit trails matters for compliance-sensitive industries: healthcare organizations that need to confirm which policy version was active during a given period, financial services firms that need to demonstrate what employees were instructed to do, and manufacturers whose quality procedures require an auditable trail of who changed what and when. For organizations migrating from SharePoint-based knowledge infrastructure, the [frontline intranet requirements checklist for replacing SharePoint 2016/2019](/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) covers governance criteria explicitly — including version history, ownership models, and expiry workflows that organizations replacing end-of-life platforms should verify before committing to an alternative. ## What organizations that fix the delivery problem actually measure The IDC 2.5-hour baseline is recoverable, but only for organizations that address search, access, and governance simultaneously. Deployments that solve one or two of the three problems consistently see partial improvement followed by a plateau — the remaining structural gap prevents full recovery of the wasted time. Organizations that report consistent progress against the IDC baseline share three practices. They measure time-to-answer, not just search volume. The relevant metric is whether employees found what they needed in a single session, not how many queries the platform logged. Declining time-to-answer is the leading indicator that both the search layer and the content depth are working. They track full-workforce adoption. The Social Edge 13% daily engagement figure reflects deployments that exclude or underserve frontline workers. Accurate adoption measurement includes frontline employees, because they represent the majority of the workforce in most organizations. A 60% adoption rate that excludes 80% of employees is a misleading figure regardless of how it looks in a quarterly report. They use zero-result queries as a content queue. Every search that returns nothing is a knowledge gap. Platforms that surface these patterns let administrators maintain a continuous documentation queue rather than discovering gaps reactively — when the employee who needed that answer escalated the question, or did not return for a second shift. The organizational case for wiki software is not that it provides better document storage. It is that it recovers hours currently lost to a delivery problem — and that recovery is measurable, compounding, and proportional to how thoroughly the implementation addresses search, access, and governance rather than treating any of the three as a second-phase concern. --- # 5 Ways For Companies To Reduce Email Overload **Author:** Anna Carriveau **Published:** 2018-10-18 **Category:** workplace-productivity With close to 150,000 emails being sent globally every minute, it’s no surprise that the average office worker spends close to 13 hours a week processing emails. Many of those emails are redundant, unimportant, or irrelevant to the receiver, resulting in hours of unproductive time.  So how can companies help prevent inbox bloat? Here are […] With close to 150,000 emails being sent globally every minute, it's no surprise that the average office worker spends close to 13 hours a week processing emails. Many of those emails are redundant, unimportant, or irrelevant to the receiver, resulting in hours of unproductive time. According to Gartner (2023), 47% of workers struggle to find necessary information at least half the time—a problem email overload makes significantly worse. So how can companies help prevent inbox bloat? Before diving into individual tactics, it's worth naming the structural problem: employees navigating 6–8 disconnected tools daily generate redundant email threads that a unified employee communications platform eliminates at the source—not just manages after the fact. The five strategies below address both the behavioral habits and the platform-level decisions that determine whether email overload gets managed or actually solved. **Here are the top 5 ways companies can reduce email overload and encourage successful communication:** ## #1: Collaboration Tools Having an integrated collaboration tool is a great way to reduce email overload. This ensures that key emails are tracked and employees are notified about updates. This is especially important when employees use a single email for both personal and office use. Collaboration tools can even replace emails by creating a centralized location for communication and company information—functioning, in effect, as a living operations manual for day-to-day teamwork management. Additionally, collaboration tools can sync with an employee's calendar and send automatic reminders about upcoming events. This encourages organization and communication, while benefiting the company and its employees. It's also worth noting that frontline and deskless workers—who make up over 80% of the global workforce—often lack corporate email entirely, making email-reduction strategies irrelevant without a mobile-first, no-email-required communication channel. For distributed teams, an [employee app](/solutions/employee-app) that works without a corporate email address is the starting point, not an add-on. ### How K·Coe Isom Ditched Corporate Email Learn how K·Coe Isom, a top 100 accounting firm, replaced email and brought all internal collaboration into MangoApps. ## #2: Organization and Filters Email marketing has a median ROI of over 122%. While that might be good news for businesses in general, for an employee, it often means an inbox flooded with promotional messages. If an employee wants to sort important work emails from unnecessary junk, it is vital for them to set inbox labels and filters. How an employee organizes their own inbox often comes down to personal preference. An inbox, for example, could show company emails first or have enabled notifications for priority messages. Whatever you choose, some kind of system needs to be in place. Organizing your inbox can make the difference between keeping up with important announcements and having to declare email bankruptcy. For teams looking at examples of lean operations in practice, inbox filtering is one of the simplest manual operations to standardize across a department—and one of the easiest to document in a shared SOP operations guide so new hires adopt good habits from day one. ## #3: Light and Lean Inboxes Employees should avoid subscribing to promotional material, newsletters, and other non-work-related subscriptions from their office email. Enough extra promotional material will end up in your inbox without you asking for it. Spending some time now to unsubscribe from promotional emails will save you from hundreds of future unwanted emails and will make it much easier to keep a clutter-free inbox. Sometimes it is even necessary to block a sender so that they become more responsible in the future. Work-related emails that are no longer active need to be archived and moved out of the inbox. Lastly, any ongoing email threads should always be as succinct and clear as possible. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) explores how leading organizations are codifying these lean-inbox habits into formal operations instructions that apply across the entire workforce—not just individual contributors. ## #4: Fixed Response Times Setting aside a few minutes at a set time every day to tackle an inbox can make a huge difference in the effort to reduce email overload. Even when employees are on vacation, spending just 10 minutes to check the office inbox can ensure that they are caught up on important events. This way, any critical communication can be acknowledged or seen. When you decide to dedicate your time to managing your email is up to you. Choose a time that works best for your schedule, but try to be consistent and do it every day. Employees also lose over 4 hours weekly switching between disconnected systems—time that compounds on top of the 13 hours already spent on email. Fixed response windows only deliver their full benefit when the number of systems requiring attention is itself reduced. ## #5: Reusable Templates Many official emails could be answered with the same reply, especially when all that is needed is a simple acknowledgment. Designing a few templates that match your most common email circumstances will save you time and reduce email overload in the long run. Having a template will make answering emails simpler and more straightforward. Preplanned templates can also ensure that emails include all of the important information. This saves the employees from the hassle of having to go back over information or resend emails if information was forgotten. Templates are most effective when they live inside a shared employee communications platform rather than individual inboxes—that way the whole team benefits, and the templates stay current without manual upkeep. As you can see, most of the tips we shared here to reduce email overload depend on employees changing their email practices. Organizations need to conduct regular employee communications training programs to ensure employees practice good email habits. Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback—and consistent, low-noise communication is a prerequisite for that feedback loop to function. ## MangoApps At MangoApps, we provide an integrated collaboration tool that can help employees work together to reduce wasted time and communicate better. Replacing scattered email threads with a single hub for real-time updates, digital forms, and key apps has been shown to reduce employee turnover by 26%, per the Joinblink / Go North West case study—linking email overload directly to broader workforce stability. Explore our [employee communications](/solutions/employee-communications) solution to see how we work with companies to increase outcomes and improve collaboration. ## What Does Implementing an Email-Reduction Strategy Actually Look Like? The five tactics above are the starting point, but implementation requires a sequenced plan. Most organizations begin by auditing which internal communications currently travel by email and could move to a dedicated channel—announcements, project updates, shift changes, and policy acknowledgments are common candidates. From there, teams define operations instructions for which tool handles which message type, document those rules in a shared SOP operations guide, and run a short employee communications training session to establish new norms. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) outlines how organizations across industries are structuring these rollouts in 2026. ## How Do You Measure Whether Email Overload Has Actually Improved? Reduction in email volume is the obvious metric, but it's a lagging indicator. More useful early signals include: time-to-response on critical communications, the number of "reply-all" threads per week, and employee-reported confidence in finding information. Per Gartner (2023), 47% of workers struggle to find necessary information at least half the time—tracking that figure before and after a platform consolidation gives a concrete baseline. Per McKinsey research, 81% of leading companies effectively use data and analytics tools to monitor workforce communication patterns, which means the measurement infrastructure is increasingly accessible even for mid-market teams. The [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study) case study details the specific metrics Raley's tracked during their communications consolidation. ## Does Email Overload Affect Frontline Workers Differently? Yes—and the difference is significant. Desk workers experience email overload as a volume problem; frontline and deskless workers often experience it as an access problem, because they may not have a corporate email address at all. For industries like [healthcare](/industries/healthcare), [grocery](/industries/grocery), and [financial services](/industries/financial), the majority of the workforce may be entirely outside the email ecosystem, relying instead on shift supervisors or printed notices for critical updates. A mobile-first employee app that requires no corporate email closes that gap and ensures that email-reduction strategies benefit the whole organization—not just the employees who were already connected. --- # How To Encourage Lasting Employee Intranet Usage **Author:** April Thomas **Published:** 2018-10-09 **Category:** intranet Your company’s intranet can be an amazing resource, but it won’t do any good if it isn’t used in the right way. At MangoApps, we believe that there are few things more heartbreaking than untapped potential, especially in business and corporate success. So we are sharing a few of the best ways companies can encourage […] ## How To Encourage Lasting Employee Intranet Usage Your company's intranet can be an amazing resource, but it won't do any good if employees don't actually use it. Per Social Edge Consulting, 91% of organizations operate an intranet—yet nearly a third of employees never log in, and only 13% use one daily. That gap has a real cost: per IDC, employees spend an average of 2.5 hours per day searching for information they can't easily find. Before the six strategies below can work, it's worth naming the structural barrier most articles skip: many intranets exclude deskless and frontline workers by design, requiring a corporate email address and desktop access. Per Emergence Capital, 80% of the global workforce is deskless. If your platform doesn't offer mobile-first, no-email-required access, behavioral nudges alone won't close the adoption gap. With that foundation in place, here are six proven ways to encourage lasting employee intranet usage and turn your platform into a daily work habit. --- ## 6 Ways To Encourage Employee Intranet Usage ### #1: Redirect Employee Inquiries Designating office resources to be available only on the intranet is an easy way to encourage natural employee engagement. These resources could be anything from employee benefits information to a PTO request form. When employees ask about information that is already stored on the intranet, gently refer them to where they can find the information. This subtle practice helps employees get into the habit of using their intranet as a resource and increases their own informational self-sufficiency. Establishing familiarity with posting and receiving information through the intranet will instinctively increase user engagement in other intranet areas as well. A modern [company portal](/key-features/company-portal) can consolidate HR self-service, benefits, and policy documents in one searchable location, making the redirect habit easier to reinforce at scale. ### #2: Make It A Work Catalyst Intranets are designed to make work more efficient and more creative. However, this will only happen if your intranet is up-to-date and easy-to-use. Old or irrelevant intranet information can be frustrating and negatively impact business decisions. Working with this kind of content quickly burns out employees and creates a perception that can be difficult to change. Not only that, when your intranet is riddled with outdated content and confusing processes, it can become cluttered and hard to use. This will in turn lead to lower levels of employee engagement and adoption of your intranet. One way to circumvent this is to proactively take steps to keep your intranet decluttered. In doing this, you can empower employees to easily access the information and resources they might need. It's also worth addressing tool sprawl directly. Employees lose meaningful time each week switching between disconnected systems; consolidating intranet, chat, HR self-service, and task management into one platform directly reduces that drag and raises daily return visits. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) offers a detailed look at how leading platforms compare on this dimension. In order to encourage lasting employee intranet usage, the content needs to be a catalyst for employees. It should make work easier, more efficient, and more enjoyable. ### #3: Build A Supportive Space Intranets allow people to collaborate, communicate, and develop relationships in unique ways. However this can only happen in a space where ideas and creativity are encouraged to grow. Healthy debates and alternative viewpoints strengthen ideas but only when they are positive and focused on improvement. This is especially important in a digital setting where it can be easy to misinterpret information. When employees feel encouraged and supported they will actively engage in successful ideas and conversations. Dedicated [workspaces](/key-features/workspaces) for teams and projects give employees a structured place to collaborate without the noise of company-wide channels, which lowers the social risk of contributing and makes participation feel more natural. ### #4: Give Employees A Choice Nothing creates pushback quite like telling a person what to do, especially if the change is different or disruptive. Allowing employees to make choices increases their sense of control over a situation and encourages feelings of active participation. This is true even if their choices are not particularly significant or relevant in the long run. Letting employees decide how and when to engage with the intranet or similar kinds of choices will help create lasting employee intranet usage and increased performance, persistence, and creativity. Employee engagement software that supports personalized feeds and notification preferences gives employees meaningful control over their intranet experience—turning a mandated tool into one they choose to open. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring that choice architecture. ### #5: Expect The Adoption Curve The adoption curve is a pattern established by human nature that explains how people typically react to changes and the rate at which enhancements are embraced. Just like profits, stocks and other business elements tend to follow certain patterns, humans also accept and utilize new technology and experiences in a fairly consistent way. Understanding this pattern helps employers create realistic intranet integration goals and expectations for employees and recognize how their company's individual adoption and usage compares to what is expected. A concrete benchmark: per SWOOP Analytics, the average employee spends only six minutes per day using intranet tools. Organizations that achieve 90%+ adoption typically deploy a branded mobile app with push notifications, SMS alerts, and offline access rather than relying on desktop-only portals. That context helps teams set realistic milestones and avoid declaring failure too early. For a real-world example of what rapid adoption can look like, see [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology). ### #6: Invite Unspoken Opinions Employees can often be hesitant to share thoughts and opinions, but that doesn't mean they don't exist. Supervisors can encourage discussion and participation by seeking out specific employees who may have insights or contrary positions and specifically invite them to voice their opinion. Often employees just need a friendly invitation to encourage their ideas and let them know their thoughts are needed and valued. This rings especially true if they offer a perspective that has not yet been considered. Running a periodic employee engagement survey or short employee engagement questionnaire through the intranet itself reinforces the platform as the place where employee voice lives—and gives leadership actionable data on what's working. --- ## How To Measure Whether Your Intranet Adoption Is Working The six strategies above are only as useful as your ability to tell whether they're moving the needle. The most reliable adoption indicators are: - **Daily active users (DAU) vs. monthly active users (MAU):** A healthy ratio is 40–60%. Per Social Edge Consulting, only 13% of employees currently use an intranet daily, so even modest DAU growth is meaningful progress. - **Search-to-find rate:** Track how often a search returns a clicked result vs. a dead end. Improving this metric directly addresses the 2.5 hours per day employees lose searching for information (per IDC). - **Content contribution rate:** What share of employees have posted, commented, or updated a document in the last 30 days? Low contribution signals a read-only culture that won't sustain engagement. - **Mobile vs. desktop sessions:** If mobile sessions are low and your workforce includes frontline workers, the platform's access model—not employee behavior—is the bottleneck. - **Pulse survey scores:** Short employee engagement questionnaires sent through the intranet can track perceived usefulness over time and surface friction before it becomes abandonment. Set a 90-day baseline, review monthly, and tie at least one metric to a business outcome (e.g., reduction in HR inquiry volume as self-service adoption rises). The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines how HR teams are connecting intranet metrics to broader workforce KPIs. --- ## What Tools and Platform Features Support Lasting Adoption? Behavioral strategies work best when the platform itself removes structural barriers. The features most correlated with sustained intranet usage are: - **Mobile-first access with no corporate email required:** This is the prerequisite for reaching the 80% of the global workforce that is deskless (per Emergence Capital). Without it, the six tips above apply only to desk-based employees. - **AI-driven content personalization:** Rather than requiring employees to seek out relevant content, personalized feeds surface it automatically—reducing the cognitive load that drives abandonment. - **Integrated department sites:** Keeping team-specific content organized in dedicated [department sites](/key-features/department-sites) prevents the clutter that makes intranets feel unusable. - **Push notifications and SMS alerts:** Organizations that achieve high adoption rates use proactive outreach to bring employees back to the platform rather than waiting for them to remember to log in. - **Employee engagement training and onboarding flows:** Structured training on employee engagement with the intranet—not just a one-time launch email—is what separates organizations that sustain adoption from those that plateau. For a broader view of how a [modern intranet](/solutions/modern-intranet) brings these features together, MangoApps has been recognized in leading analyst evaluations including the [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms). --- ## How Long Does Intranet Adoption Typically Take? Most organizations see three distinct phases: 1. **Launch spike (weeks 1–4):** Novelty drives initial logins. This is the period to capture early adopters and surface quick wins. 2. **Trough (months 2–3):** Usage drops as novelty fades. This is where the adoption curve is most commonly misread as failure. Maintaining momentum here requires the supportive space and choice strategies described above. 3. **Sustained habit (months 4–6+):** If the platform is genuinely useful and accessible, daily usage stabilizes. Organizations that deploy branded mobile apps with push notifications tend to exit the trough faster. The business case for pushing through the trough is clear: disengaged employees who abandon the intranet are also more likely to disengage from the organization entirely. Replacing a single frontline employee costs between $4,400 and $15,000 on average—a figure that reframes intranet adoption investment as cost avoidance, not overhead. --- ## MangoApps Creating lasting employee intranet usage doesn't have to be difficult. With a little attention an intranet can be the right fit for any kind of company. At MangoApps we work with businesses to enhance their own creative abilities and help them unlock all of their potential. We love to help businesses create collaborative business communication and offer advice on intranet success. To learn more about how MangoApps Intranet can benefit your organization, contact us or schedule a personalized demo today. --- # Why Employees Don’t Need Email Addresses **Author:** April Thomas **Published:** 2018-10-02 **Category:** integrated-digital-workplace For large enterprises in today’s business world, internal communication is synonymous with migraine. As companies expand, branches tend to become less and less connected. Leaders struggle to communicate with the thousands of employees that are spread out over different geographic locations. So what is the obvious solution? Give everyone an email address, right? While providing […] # Why Employees Don't Need Email Addresses — And What to Use Instead For large enterprises, giving every employee a company email address feels like the obvious solution to internal communication. It isn't. Email was built for external correspondence, and forcing it to carry the weight of internal communication creates real costs — in budget, in productivity, and in employee engagement. This article explains the five core reasons email fails as an internal tool, then offers a neutral comparison of the alternatives so you can make an informed decision. --- ## The Core Problem: Email Was Not Built for Internal Communication Employees spend an average of 2.5 hours per day searching for information (per IDC), and a significant portion of that time is lost inside cluttered inboxes. Meanwhile, 91% of organizations already operate an intranet of some kind (per Social Edge Consulting), yet nearly a third of employees never log in to it (per Social Edge Consulting) — which suggests the problem isn't a lack of tools, it's a lack of the *right* tools configured the right way. The case for removing or limiting employee email addresses is not about cutting communication. It's about replacing a tool that was never designed for the job with one that was. --- ## 5 Reasons Employees Don't Need Email Addresses ### 1. It Strains the Budget Without Proportional Return When a workforce is small, individual email accounts are a manageable expense. As headcount grows, the math changes. Email licenses cost roughly $5 per user per month, and that figure compounds quickly across a large organization. For employees whose roles are entirely internal — frontline workers, warehouse staff, retail associates — that spend delivers almost no return, because those employees rarely need to contact vendors, clients, or external partners. SharePoint's first-year total costs for 1,000 users range from $130,000 to $426,000 when licensing, implementation, and customization are combined, making it a useful benchmark for evaluating whether an email-plus-intranet stack is actually cheaper than a unified alternative. Being selective about who genuinely needs an external email address reduces licensing costs and removes a layer of communication noise that slows teams down. ### 2. It Fragments Priorities and Increases Cognitive Load Every message that arrives in an inbox arrives as an implicit demand. When employees receive dozens of messages per day — each framed as urgent by the sender — the result is not better communication, it is decision fatigue. Employees end up spending time triaging rather than working. Structured task tools, activity streams, and project channels solve this by separating information types: announcements go to announcement channels, tasks go to task lists, and direct messages go to direct message threads. The format itself signals priority, which email cannot do. ### 3. It Creates Ambiguity About Whether Messages Were Received Sending an email does not confirm it was read. Messages get filtered to spam, buried under higher-volume threads, or simply ignored without consequence. This ambiguity is particularly costly for compliance-sensitive communications — policy updates, safety notices, regulatory changes — where organizations need documented confirmation that employees received and acknowledged a message. Modern [employee communications](/solutions/employee-communications) platforms address this directly by providing read receipts, acknowledgment tracking, and audience segmentation, so communicators know exactly who has seen a message and who hasn't. ### 4. It Doesn't Work for the Deskless Majority Approximately 80% of the global workforce is deskless (per Emergence Capital). Frontline workers in healthcare, retail, manufacturing, and logistics rarely sit at a desktop. Checking email on a mobile device is a poor experience: attachments are hard to open, group threads are difficult to follow, and searching for a document from six months ago is nearly impossible. This is the most compelling business case for replacing email with a purpose-built internal tool. A workforce where most employees are on the floor, in the field, or on the road needs communication that is mobile-first by design, not mobile-compatible as an afterthought. Industries like [healthcare](/industries/healthcare) and [grocery](/industries/grocery) retail have moved in this direction specifically because their frontline populations were effectively unreachable through email. ### 5. It Creates Ongoing IT Overhead Every new hire requires a new email account. Every departure requires deprovisioning. In organizations with high turnover — common in retail, hospitality, and healthcare — this creates a continuous administrative burden on IT teams that could be redirected to higher-value work. Provisioning and deprovisioning users in a unified employee app is typically faster and less error-prone than managing individual email accounts across multiple systems. --- ## What Should Replace Email for Internal Communication? The right answer depends on your workforce composition, existing technology stack, and communication complexity. Here is a neutral comparison of the four most common alternatives. ### Option 1: Team Messaging Apps (Slack, Microsoft Teams) **Best for:** Knowledge workers, project-based teams, organizations already in the Microsoft 365 or Google Workspace ecosystem. **Strengths:** Real-time messaging, strong integrations, familiar interface, good search within channels. **Limitations:** Channel sprawl becomes its own form of noise at scale. Neither Slack nor Teams was designed for frontline or deskless workers — mobile experiences are functional but not optimized for shift-based or task-based workflows. Governance and compliance tooling requires additional configuration. ### Option 2: Intranet Platforms (SharePoint, Unily, Simpplr) **Best for:** Organizations that need a central content hub, document library, and top-down communications channel. **Strengths:** Strong content management, policy libraries, org-wide announcements, integration with HR systems. **Limitations:** Only 13% of employees use an intranet daily (per Social Edge Consulting), and only six minutes per day on average for tools like SharePoint (per SWOOP Analytics). Only 22% of company intranets deliver personalized content to employees, meaning most push the same generic messages to everyone regardless of role or location (per Akumina / State of the Digital Workplace & Modern Intranet 2024 research). Adoption is the central challenge, not functionality. ### Option 3: Activity Streams and Social Intranets **Best for:** Organizations that want to replace broadcast email with a feed-based model where employees see relevant updates in a role-based stream. **Strengths:** Higher engagement than static intranets, supports two-way communication, easier to surface relevant content by department or location. **Limitations:** Requires governance to prevent the stream from becoming as noisy as an inbox. Content strategy matters — a poorly curated activity stream replicates the email problem in a different format. ### Option 4: Unified Employee Apps **Best for:** Organizations with a significant frontline or deskless population that need messaging, task management, document access, and announcements in a single mobile-first interface. **Strengths:** Designed for the 80% of the workforce that is deskless (per Emergence Capital). Replaces multiple point solutions — email, intranet, task tools — with one governed platform. A fully mobile intranet platform can be deployed for a 40,000-employee workforce in as little as 8 weeks, with adoption rates above 90% (per Unily / British Airways case study). Replacing an email point solution with a broadcast-capable channel can generate approximately £80,000 in annual cost savings for a large enterprise (per Unily / British Airways case study). **Limitations:** Requires change management investment. Employees accustomed to email need onboarding to adopt new communication habits. Integration with existing HR and operations systems needs to be evaluated before deployment. MangoApps falls into this fourth category. Its [employee app](/solutions/employee-app) is built specifically for organizations with large frontline populations, offering messaging, task management, document access, and acknowledgment tracking in a single platform. A 95% employee adoption rate has been achieved for deployments built to replace fragmented email communication across a 5,000-person post-acquisition workforce. --- ## Frequently Asked Questions ### Do frontline workers actually need a company email address? For most frontline roles — retail associates, clinical staff, warehouse workers, field technicians — a company email address is rarely used for its intended purpose. These employees need shift schedules, task assignments, policy updates, and the ability to message a supervisor. A purpose-built [employee app](/solutions/employee-app) or mobile intranet delivers all of that without the overhead of an email account. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how organizations are restructuring their communication stack specifically for this population. ### What about employees who do need external email? The argument here is not that email should be eliminated entirely. Customer-facing roles, sales teams, finance, legal, and leadership all have legitimate needs for external email. The case is for *selectivity*: audit which roles genuinely require external communication, provision email for those roles, and replace it with a structured internal tool for everyone else. This reduces licensing costs and removes a communication channel that adds noise without adding value for internal-only employees. ### How do you measure whether the replacement is working? The metrics that matter are adoption rate (what percentage of employees log in at least weekly), read and acknowledgment rates for critical communications, and time-to-information (how long it takes an employee to find a document or policy). Intranet platforms and unified employee apps typically surface these analytics natively. For context on what good looks like, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) benchmarks adoption and engagement across major platforms. --- ## The Bottom Line Email is not a bad tool — it is the wrong tool for most internal communication, especially for the deskless majority that makes up roughly 80% of the global workforce (per Emergence Capital). The five problems outlined above — cost, cognitive load, ambiguity, poor mobile experience, and IT overhead — are not quirks of email. They are structural features of a technology built for external correspondence being asked to do something it was never designed to do. The practical path forward is not to eliminate email across the board, but to audit who actually needs it, replace it with a purpose-built internal communication tool for everyone else, and measure adoption rigorously. Whether that tool is a team messaging app, an intranet platform, an activity stream, or a unified employee app depends on your workforce composition and existing stack — but the decision should be driven by where your employees actually work, not by what your IT team already has provisioned. For a deeper look at how organizations are restructuring internal communications in 2026, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the shift away from email-centric communication models in detail. --- # The Roles of Artificial Intelligence in the Workplace **Author:** Anna Carriveau **Published:** 2018-09-27 **Category:** industry-insights The fear of artificial intelligence replacing or infringing on humankind has persisted ever since the birth of science fiction. But today, AI is no longer a work of fiction and is an active and important part of our working world.  AI and its continued advancement and integration in the workforce will, of course, change how […] # The Roles of Artificial Intelligence in the Workplace The fear of artificial intelligence replacing or infringing on humankind has persisted ever since the birth of science fiction. But today, AI is no longer a work of fiction and is an active and important part of our working world. AI and its continued advancement and integration in the workforce will, of course, change how businesses work, but it will never be the threat that many people fear. When used effectively, AI enables and improves the modern workforce — helping employees work more efficiently, reach information faster, and find more meaning in their roles. The sections below address the three questions most employees and leaders ask: Will jobs disappear? What should workers do now? And how do humans and AI actually co-exist day to day? ## Will People Lose Their Jobs? There are a few jobs that include skills that may in time become automated. A few examples of these occupations are data entry operators, translators, and customer support centers. The day-to-day tasks performed in these roles take up a huge amount of manpower and payroll costs. Often times, businesses feel that the time, effort, and costs are not always justifiable for the investment. This is where automation aided by AI can step in and take things into its own hands. Most simple and repetitive tasks do not actually require an AI analysis. Simple robotic process automation tools can perform a majority of tasks with success and speed beyond human ability. Bringing AI and cognitive computing into these environments greatly increases the speed, accuracy, and savings available to businesses. And while AI, of course, has many possible business applications and limits still being discovered, simple, regular, and straightforward tasks like payroll management or vendor invoicing are all very possible with the AI tech available today. The displacement concern is real but narrower than headlines suggest. The larger story is consolidation: employees currently navigate 6–8 disconnected tools daily, creating fragmentation that AI-powered unified platforms are specifically designed to eliminate — making AI adoption a platform consolidation story, not just an automation story (MangoApps product benchmark). For teams exploring how this shift affects talent operations, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading organizations are repositioning roles rather than eliminating them. ## What Should Employees Do? With artificial intelligence in the workplace increasingly replacing human involvement in everyday tasks, what should employees do? Employees in these areas need to start taking time now to explore new avenues and increase their skills. AI offers employees all kinds of exciting opportunities as they discover how to make AI an enabler. With AI taking care of routine tasks, employees are allowed more time and energy for strategic thinking and creative execution. This is not only an effective way to counter the perceived threat of artificial intelligence in the workplace, but it also frees up employees to move up the corporate ladder faster and find more meaning in their occupations. Employee engagement training and upskilling programs are the most direct lever available to HR teams right now. AI-driven onboarding automation can reduce new hire ramp time by up to 50%, making AI a direct lever for talent operations efficiency (Beekeeper product benchmark). Organizations that embed [learning and development strategy into daily work](/articles/learning-and-development-strategy-embedded-in-daily-work) — rather than treating it as a periodic event — are better positioned to help employees grow alongside AI rather than be displaced by it. Employee engagement surveys and employee engagement questionnaires are also increasingly being analyzed by AI tools that surface patterns HR teams would otherwise miss across thousands of responses. This turns a once-annual exercise into a continuous feedback loop that improves employee experience platform design in real time. ## How Can We Co-Exist? The secret to successfully using artificial intelligence in the workplace is understanding how it can make our work easier. Finding a vacant parking spot, scheduling events, sending out invites, booking meeting rooms, ordering supplies, taking minutes and much more are all little activities that AI can take off of our schedule. And while none of these activities individually take much thought, effort, or time, they can collectively add up to hours of productive time taken away from employees. The information-retrieval problem alone is significant: employees spend an average of 2.5 hours per day searching for information, per IDC. AI-native platforms can surface the right information for a specific employee in seconds using curated, role-based personalization — contrasting with static intranet content that becomes stale without governance (Unily product benchmark). Only 13% of employees use an intranet daily, and nearly a third never log in at all, per Social Edge Consulting — a utilization gap that AI-powered personalization is specifically designed to close. AI assistance with everyday office tasks will always lead to increased productivity and creativity. However, an unspoken real value of artificial intelligence and human collaboration can be attained in fields like medical diagnostics. Medical leaders globally are using cognitive tools such as IBM Watson to precisely identify causes and remedies for deadly diseases. Going through extensive data records could take a person months or even years to complete but for a machine, it takes only seconds. This increased organization and speed can lead to medical advancements years ahead of schedule. The co-existence story also extends to sop operations — the standard operating procedures that govern how frontline teams do their jobs. AI can surface the right SOP to the right worker at the right moment, reducing errors and training time simultaneously. ## AI as a Frontline Workforce Enabler Most discussions of AI in the workplace focus on knowledge workers and office environments. But 80% of the global workforce is deskless, per Emergence Capital — meaning the majority of workers never sit at a computer. Frontline workers in retail, hospitality, healthcare, and logistics are a primary beneficiary of workplace AI because mobile-first AI tools reach them without requiring company email, VPN, or a desk (MangoApps frontline product benchmark). For retail teams specifically, AI-assisted scheduling and task management tools are already reducing the coordination burden on store managers. The [Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) outlines how AI-informed scheduling decisions translate directly into reduced overtime costs and higher employee engagement scores on the floor. The outcomes from enterprise deployments are measurable: one large organization reported 90% frontline adoption within the first six months of deploying an AI-enabled intranet, a $20M cost avoidance, and a 30-point increase in employee engagement score after replacing a legacy intranet with an AI-native platform. These are not projections — they are documented results from organizations that treated AI as an employee experience platform investment, not just a back-office automation project. ## The Bottom Line There is no question that AI is a disrupter and that its presence and evolution will permanently change the business world. But the negative perceptions of AI overtaking human abilities or causing insurmountable unemployment just aren't true. With a massive growth rate, artificial intelligence in the workplace is absolutely here to stay. The practical path forward has three components. First, identify the repetitive, high-volume tasks — data entry, scheduling, information retrieval, SOP lookups — where AI delivers immediate time savings. Second, invest in employee engagement training and reskilling so that the time AI frees up is redirected toward higher-value work rather than absorbed by anxiety about displacement. Third, choose platforms that consolidate rather than add to tool sprawl — the goal is fewer logins, not more. Organizations that approach AI as an [employee engagement software](/solutions/employee-engagement) and experience layer — not just an automation layer — are the ones capturing measurable ROI. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides a practical framework for leaders ready to move from AI curiosity to AI implementation. ## What Industries Should Approach AI Differently? AI's role is not uniform across sectors. In healthcare, the value is in diagnostic speed and data synthesis. In retail and hospitality, the value is in frontline communication, scheduling, and task management — areas where employee engagement questionnaires consistently show the highest dissatisfaction. In nonprofit and mission-driven organizations, AI can reduce the administrative burden that pulls staff away from program delivery. Each industry has a different highest-value use case, and implementation strategy should reflect that rather than defaulting to a generic automation roadmap. ## How Do You Measure Whether AI Is Working? The clearest indicators are utilization, time savings, and employee engagement survey scores. If employees are not using the AI tools deployed — recall that the average daily time spent using intranet tools is just six minutes, per SWOOP Analytics — the problem is usually relevance and personalization, not resistance to technology. Tracking engagement scores before and after AI-assisted workflow changes gives HR teams a direct line of sight into whether the investment is improving the employee experience or simply adding another underused system to the stack. The [MangoApps inclusion in a leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) offers an independent benchmark for what effective AI-native platform deployment looks like in practice. --- # 7 Ways Artificial Intelligence Helps Human Resources **Author:** Anna Carriveau **Published:** 2018-09-25 **Category:** industry-insights Positive work culture evolution is an easy question to answer. We only have to ask ourselves, “How can we apply our acquired knowledge to create a better work environment?” This question has structured the growth of businesses for years and has lead to the development of artificial intelligence. As incredible as it might seem, the […] Positive work culture evolution comes down to one question: "How can we apply our acquired knowledge to create a better work environment?" That question has structured business growth for years and has led to the development of artificial intelligence. As incredible as it might seem, the business world is finally developing systems that can think like we do. AI has the potential to be used successfully in almost every department within an organization. Below, we focus on how artificial intelligence helps Human Resources transform your workforce — and what measurable outcomes organizations can expect when they act on these capabilities. ## 7 Ways AI Helps Human Resources: ### #1: Unbiased Decision Making Artificial intelligence systems are immune to the general stereotyping and biased decision making that are a part of human nature. HR members, who should remain unbiased, are just as susceptible to human discrimination as the rest of us. Artificial intelligence helps human resources process initial recruitment screenings, performance appraisals, job evaluations and all other kinds of factual information and insights about a person based strictly on real data rather than human perspectives and potential prejudice. This unbiased analysis allows organizations to develop more effective employee relationships based on actual work performance, policies, and conduct. Persona-based AI targeting — routing content by role, region, and language — also ensures compliance communications and policy updates reach the right employees without manual segmentation by HR, closing a gap that manual processes routinely leave open. ### #2: Smarter Recruitment Recruiters often need hours of tireless effort to pick the right talent for a position. AI-powered systems can quickly inspect thousands of candidate profiles and organize their abilities with those in demand. This makes it easy to provide HR with a set of qualified candidates right away, simplifying the entire hiring process. Organizations that pair AI screening with a unified [workforce management](/solutions/workforce-management) platform report 50% faster new-hire onboarding when mobile-accessible training and digitized workflows replace paper-based processes. ### #3: Simpler Learning and Development It is critical for HR to ensure that the talent within an organization is ready to handle upcoming industry demands. This means that HR needs to understand and assess employees' skills and help them practice continuous learning and development. AI-powered learning platforms can identify skill gaps and automatically surface personalized learning paths — reducing reliance on HR-led manual assessments and enabling continuous workforce development at scale. A data-driven LMS learning system enabled by technologies like AR or VR and powered by AI helps take this burden off the HR team and helps employees discover their own training interests and schedules. Manual assessments are driven by an HR team that may not properly capture or assess an employee's talents and interests. Moving to an AI-native approach closes that gap. For a deeper look at why traditional approaches fall short, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). You can also explore the executive framework in [Break The Annual Review Cycle: The Executive's Guide To Creating A Culture Of Continuous Employee Development](/resources/break-the-annual-review-cycle). ### #4: External HR Communication External communication with artificial intelligence gives human resources almost endless possibilities. It could be anything from smart conversational bots on the company's corporate website that provide information to automatic updates informing potential candidates of their application status. AI-driven bots provide real-time updates, regardless of business hours, to customers, coworkers, potential employees and anyone looking for simple and straightforward information. This matters especially for the 80% of the global workforce that is deskless, per Emergence Capital — workers who rarely sit at a desktop and need mobile-first, always-on communication channels to stay informed. ### #5: Processes Compliance and SOP Operations When employees grow at an exponential rate it becomes difficult for HR to properly monitor the dynamics of an organization. Artificial intelligence helps human resources become much more automated, making complicated and overloaded business processes much easier. With machine learning, complex compliance concerns — including SOP operations documentation and policy acknowledgment — can be simplified, organized and easily managed, allowing issues to be resolved fast and much more efficiently. No-code AI workflow automation for HR self-service (PTO requests, onboarding forms, policy acknowledgment) can be deployed in weeks without IT involvement, lowering implementation burden significantly. Organizations that have deployed AI-powered self-service intranets report a 52% decrease in HR support requests as a direct result. ### #6: Automated HR Functions Repetitive HR tasks like salary, bill settlements, work reports, and more can all be easily automated with cognitive intelligence. Intelligent conversational bots can also help employees understand policies, find information and fill out reports. AI-driven HR platforms that unify scheduling, time-and-attendance tracking, task assignment, and workflow automation in one place reduce the number of disconnected tools employees must navigate daily — a meaningful gain given that employees spend an average of 2.5 hours per day searching for information, per IDC. For organizations managing complex workforce structures, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines how automation is reshaping the HR function across industries. ### #7: Detailed Analytics and Employee Experience Data While companies usually like to collect as much data about their customers as possible, they often don't think to analyze their employees. AI-enabled analytics offer an easy and fairly unobtrusive way to collect valuable information about employee characteristics, styles, and overall behavior through a unified [employee experience platform](/solutions/modern-hcm). This information also benefits larger HR functions like employee ratings, appraisals, performance evaluations, compliance, and rewards. AI systems can even help strengthen employee relationships and retain talent by detecting signs of employee discomfort or irritation that may not be vocalized or that employees may not feel comfortable bringing to HR. Context matters here: per Social Edge Consulting, only 13% of employees use an intranet daily, and nearly a third never log in at all — meaning analytics built on intranet activity alone miss the majority of the workforce. AI that reaches employees through mobile apps and frontline-accessible channels captures a far more complete picture. Organizations that deploy AI-native employee experience platforms report 90% frontline adoption within the first six months. ## MangoApps: One Platform, All Seven Capabilities This article has only scratched the surface of how artificial intelligence helps Human Resources. Incorporating AI is the right way to implement a future-oriented, disciplined and unbiased decision model. But the real competitive advantage comes not from deploying seven separate point solutions — one for recruitment, one for learning, one for compliance, one for analytics — but from consolidating all seven functions inside a single [employee experience platform](/solutions/employee-app) that serves both desk-based and frontline workers without requiring email or a desktop. When businesses incorporate AI as a tool to strengthen their own human ability and ingenuity, they gain a stronger understanding of their workforce and help employees reach their full potential. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides a practical framework for evaluating where AI delivers the fastest ROI across HR functions. To learn more about improving team collaboration, communication, and ingenuity in your business, schedule a demo with MangoApps today. ## Which AI Tools Actually Do This? Not every AI HR tool covers all seven functions. When evaluating platforms, look for solutions that offer a unified employee data layer — so that recruitment, learning, compliance, and analytics share the same underlying profile rather than creating duplicate records. Platforms recognized in independent analyst evaluations, such as the [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms), provide a useful starting point for vendor shortlisting. Key questions to ask any vendor: Does the platform reach frontline workers without requiring a corporate email address? Can no-code workflows be deployed without IT involvement? Does the LMS learning system integrate with existing HRIS data? ## What Does AI HR Implementation Actually Cost and How Long Does It Take? Implementation timelines and costs vary widely depending on workforce size, existing tech stack, and the scope of automation. However, no-code AI workflow automation for HR self-service — covering PTO requests, onboarding forms, and policy acknowledgment — can typically be deployed in weeks rather than months, without IT involvement. Organizations replacing paper-based or disconnected processes tend to see the fastest payback: the 50% faster onboarding and 52% reduction in HR support requests cited above are representative of what early adopters report. For a detailed look at what to expect across the deployment lifecycle, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers change management and adoption benchmarks in depth. ## What Are the Risks of AI in HR? AI in HR is not without risk. Algorithmic bias remains a concern: AI systems trained on historical hiring or performance data can encode existing inequities rather than eliminate them, which is why human review of AI-generated recommendations remains best practice. Data privacy is a second consideration — employee analytics must comply with applicable labor law and data protection regulations, and employees should understand what is being collected and why. Finally, adoption risk is real: per SWOOP Analytics, the average employee spends only six minutes per day using intranet tools, which means AI features embedded in low-adoption platforms will go unused regardless of their technical sophistication. Choosing a platform with demonstrated frontline adoption rates, such as those documented in the [How Santee Cooper's 'The Coop' Builds Connection Across Every Corner of its Workforce](/resources/santee-cooper-case-study) case study, materially reduces this risk. --- # 7 Strategies to Choose the Best Intranet Vendor For Your Business **Author:** April Thomas **Published:** 2018-09-20 **Category:** intranet Forming and maintaining successful business relationships takes time, understanding and introspection. Choosing a lasting and reliable intranet vendor should be about more than just modules and features. At MangoApps, we believe in fostering open communication between businesses, employees, and anyone else in the business world. So it only makes sense to pass on our intranet […] ## 7 Strategies to Choose the Best Intranet Vendor For Your Business Forming and maintaining successful business relationships takes time, understanding, and introspection. Choosing a lasting and reliable intranet vendor should be about more than just modules and features. Per Social Edge Consulting, 91% of organizations operate an intranet — yet only 13% of employees use one daily, and nearly a third never log in at all. That adoption gap is almost always a vendor selection problem, not a technology problem. At MangoApps, we believe in fostering open communication between businesses, employees, and anyone else in the business world, so it only makes sense to pass on our intranet vendor expertise. **Here are the top 7 strategies for choosing the best intranet vendor for your business:** --- ### 1. Know Your Company Needs It's almost impossible to find the right intranet vendor if you don't have at least an idea of what you're looking for. Before you start talking to vendors, do a little introspection and think about what your main intranet focuses and goals are. Concretely, that means answering questions like: How many employees need access, and are they desk-based or distributed? What communication and collaboration problems are you solving today? Which existing tools must the intranet replace or connect to? Do you need multilingual delivery or role-based permissions for a regulated environment? It's also a good idea to briefly familiarize yourself with basic intranet options such as on-premise versus SaaS to help you communicate with vendors and understand how intranets can assist with your current goals and strategies. A [modern intranet](/solutions/modern-intranet) built around your documented requirements is far easier to evaluate than one chosen by feature checklist alone. ### 2. Think About the End-User It's easy to get caught up in seemingly endless options and possibilities, but if your intranet is going to be successful you have to keep the end-user in mind. Are the features what your employees need, will they be easy to understand, and will they integrate well with your business style? Every business has its own unique work styles and preferences, and a profitable intranet needs to accommodate and reinforce those behaviors. For example, artistic professions generally work in a less rigid space. Ideas tend to come unexpectedly, so projects often start quickly and finish slowly over time. Intranets for this type of work need to be fluid, adaptable, and accessible at all times. In contrast, an accounting firm works very systematically and benefits more from rigid structure and organization. It might take some reflection to understand your company's style. Choosing an intranet vendor allows you to build on employee work habits. Frontline and mobile readiness deserves specific attention here. Per Emergence Capital, 80% of the global workforce is deskless. Platforms that lack a purpose-built mobile experience create friction for distributed workers who make up the majority of many enterprise workforces. Ask every vendor to demonstrate their mobile app — not just a mobile-responsive browser view — before advancing them in your evaluation. The [Frontline Intranet Requirements checklist](/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) is a practical starting point for building that part of your evaluation criteria. ### 3. Listen To Your Intuition A good intranet should be almost instinctual. While you will need a basic introduction to its features, your intranet should feel easy and natural. Just like you learned how to use email or countless kinds of social media without detailed training or instruction, the right intranet for your company should be clear and easy to understand right from the start. If your intranet doesn't feel natural, especially when you are learning how to use it, it's not very likely to last. In addition to a system that works with your style, you need to be aware of potentially shady or unusual fine print. Vendors at times try to disguise information, making a great-looking service turn into something completely different. We all know the frustration of a "free" app or a phone provider's "encouragement" to upgrade. That's not the kind of nonsense you should be dealing with in your intranet. Read your contract terms carefully and listen to your intuition about what seems right. One area where fine print matters most: AI capabilities. AI-driven personalization — surfacing role-relevant content automatically — is now a baseline evaluation criterion for modern intranet vendors, not a premium differentiator. If a vendor is charging extra for basic content targeting or semantic search, that is worth scrutinizing closely. ### 4. Analyze Existing Methods In order for an intranet to be effective, it has to integrate easily with the products you already use. Intranets are designed to be a one-stop-shop of sorts for all of your company's internal needs. Your intranet needs to incorporate or replace your existing methods of sharing, collaborating, and communicating information. When evaluating integration depth, ask for specifics: MangoApps, for example, connects with 200+ enterprise tools including Microsoft 365, Workday, and ADP — a concrete benchmark to pressure-test against any vendor's claims. A useful intranet should also be as customizable as your company needs. Do you have a habit of personally tailoring everything — is software customization important to your brand and your work process? Or is software something that you like as-is, where you want it to do the job right out of the box? While neither approach is wrong, it is important that your intranet works how you do and offers you the freedom, or lack thereof, that you need. The [company portal](/key-features/company-portal) and [department sites](/key-features/department-sites) capabilities of a platform will tell you quickly how much configuration is actually possible versus promised. ### 5. Consider Your Accountants Company budget is probably the most important factor in choosing an intranet vendor or even not choosing one at all. As disappointing as it may be, a budget is often the fact that brings our plans back to reality. Even the most beneficial tools, services, and innovations are sometimes just out of reach because of budget. However, total cost of ownership — not just licensing — should anchor vendor budget conversations. Implementation, customization, migration, and third-party tooling can dwarf the headline license fee. As a benchmark: SharePoint enterprise implementation costs range from $15,000 for basic setups to $150,000+ for enterprise-grade deployments — a figure buyers should pressure-test against any vendor's quoted price. Build a full TCO model before signing anything. If you find yourself having to settle for a package, service, or vendor that's not exactly what you wanted, don't worry. You may need to compromise now, but knowing what you really want is key to future business success. Once you are ready to work with that new intranet vendor, chances are pretty good that their products will be even better. ### 6. Evaluate Their Experience Part of your success with intranet vendors comes from their own experience with your business and industry-specific needs. Take some time to look into their similar experience. Have they worked with clients like you before? Are they familiar with your unique challenges? Do they have a specialty? While specialties and specific experience might not be a deciding factor alone, they can contribute to an overall decision. And sometimes an outstanding vendor with great products and services just isn't a good fit for your business. Critically, ask vendors for documented adoption benchmarks — not just feature lists. Adoption outcomes are the most honest signal of platform quality. A 95% employee adoption rate achieved after a post-acquisition intranet rollout unifying 5,000 employees across 30 offices, or 90% frontline adoption within the first six months of a large enterprise deployment, are the kinds of proof points that separate credible vendors from aspirational ones. If a vendor cannot produce adoption data from comparable deployments, treat that as a red flag. A good intranet vendor also needs a strong customer service culture as well as the knowledge and know-how to handle questions and concerns. Before you commit, try to have at least one experience with your potential vendor's customer service team. Ask them any questions you have as well as what to do in a few plausible problems and scenarios. Having at least a little experience with customer service gives you a window into what your future encounters with the company will be like, especially when trying to resolve a concern or fix an issue. Independent analyst coverage — such as [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) — can supplement your own due diligence with structured vendor comparisons. ### 7. Assess The Association The final factor to consider before settling on an intranet vendor is the potential impact of your actual relationship. Every business has its own specific set of values and personality, and who you choose to associate with will say a lot about your own business. Even if a vendor provides an outstanding intranet, it is important to consider how you will be perceived for associating with them. A business's brand and company culture will also typically give you a good idea of what working with them will be like. Ideally, a successful business with services you enjoy will have a helpful and positive company culture and reputation, but unfortunately that is not always the case. It is important for both the success of your business relations and the continuous improvement of your own business reputation to take a little time and evaluate the potential side effects of associating with a specific intranet provider. --- ### MangoApps Choosing an intranet vendor is an important step for your business but it doesn't have to be intimidating. With a little forethought and some simple evaluation, you'll be sure to find the right vendor. At MangoApps, we understand the importance of combining useful tools with outstanding service and are committed to offering our customers the best intranet products with the best possible experience. See how MangoApps has been recognized for that commitment in [MangoApps' inclusion in a leading research firm's Intranet Platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms). To learn more about how MangoApps can help your organization, schedule a personalized demo today. --- ## What Questions Should I Ask Intranet Vendors Before Buying? Once you have your internal requirements documented, the vendor conversation should be structured around five question categories: 1. **Adoption evidence** — Ask for adoption rate data from deployments comparable to yours in size, industry, and workforce type. Per SWOOP Analytics, the average employee spends only six minutes per day using intranet tools; a vendor who cannot explain how their platform beats that benchmark has a problem. 2. **Integration specifics** — Request a live demonstration of integrations with the tools your organization actually uses today, not a slide listing logos. 3. **Governance and security** — Ask how the platform handles role-based permissions, multilingual delivery, message acknowledgment tracking, and compliance requirements for your industry. These are table-stakes for global or regulated organizations, not premium add-ons. 4. **Total cost of ownership** — Request a full TCO breakdown: licensing, implementation, migration, customization, and ongoing support. Compare this against the benchmark range noted above. 5. **Mobile and frontline readiness** — Ask to see the native mobile app experience, not just a browser demo. Per IDC, employees spend 2.5 hours per day searching for information; a platform that is hard to use on mobile compounds that problem for deskless workers. A structured [intranet governance plan](/articles/sharepoint-server-2016-2019-replacement-intranet-governance-plan) can also help you frame governance-related questions before vendor conversations begin. ## How Do I Compare Intranet Pricing Models? Intranet vendors typically price on one of three models: per-user-per-month SaaS subscriptions, enterprise site licenses, or consumption-based pricing. Each has different TCO implications: - **Per-user SaaS** is predictable and scales with headcount, but costs can spike during rapid growth or acquisitions. Ask whether deskless or frontline workers are priced the same as knowledge workers — many vendors charge a reduced rate for limited-access users. - **Enterprise site licenses** offer cost certainty at scale but often require larger upfront commitments and longer contract terms. Negotiate renewal terms and price caps before signing. - **Consumption-based pricing** is rare for intranets but appears in some AI feature tiers. Understand what triggers a usage charge before enabling any AI personalization features. Regardless of model, always request a line-item breakdown of what is and is not included in the base price. Implementation services, custom integrations, training, and premium support are frequently sold separately. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) includes benchmarking data that can help contextualize vendor pricing against current market norms. ## What Does a Successful Intranet Rollout Actually Look Like? Vendor selection is only the beginning. The organizations that achieve high adoption — the 90–95% figures cited above — share several execution patterns: - **Executive sponsorship from day one.** Intranets that launch as IT projects without visible leadership participation consistently underperform on adoption. - **Phased rollout with feedback loops.** Launching to a pilot group, measuring engagement, and iterating before full deployment reduces the risk of a low-adoption launch. - **Role-specific onboarding.** Frontline workers, managers, and knowledge workers have different use cases. Generic training produces generic results. - **Ongoing governance.** Content that goes stale is the single most cited reason employees stop using an intranet. Assign content owners, set review cycles, and use the platform's analytics to identify dead zones. See the [SharePoint Server 2016/2019 Migration Checklist](/articles/sharepoint-server-2016-2019-migration-checklist) for a practical governance and content audit framework that applies to any intranet transition. The right vendor will be a partner in all four of these areas — not just a software provider. That is the standard worth holding them to. --- # The Top Six MangoApps Employee Dashboard Benefits **Author:** Anjali **Published:** 2018-09-13 **Category:** modules-features The MangoApps employee dashboard provides a central location for employees to access, interact with and analyze up-to-date company information. Making sure that your employees have relevant information on hand helps them complete their tasks and make smarter data-driven decisions. Our dashboard provide admins the ability to monitor and measure employee engagement in real-time and on […] ## The Top Six MangoApps Employee Dashboard Benefits The MangoApps employee dashboard gives employees a single, personalized location to access company information, complete tasks, and stay connected — whether they're at a desk or on the floor. Per IDC, employees spend an average of 2.5 hours per day searching for information; a well-adopted dashboard eliminates most of that waste. MangoApps customers achieve 90%+ average adoption rates within the first six months, and organizations like OU Health reached 87% workforce engagement within months of launching a branded dashboard app, while PetSmart reported 4x the industry engagement benchmark (source: MangoApps case studies — OU Health, PetSmart). Below are the six core benefits that drive those outcomes. ### The Top 6 Benefits Of MangoApps Employee Dashboard: #### #1: Increase Efficiency Having updated information and resources at your fingertips naturally makes work more efficient. Per IDC, employees spend 2.5 hours per day searching for information — time the dashboard reclaims by surfacing the right content in one place. When employees don't have to hunt across departments and projects, they experience less work fatigue. This results in happier, more productive, and more efficient workers. Having company news easily accessible on your dashboard also makes it easier to act on. MangoApps employee dashboard benefits employees with time management by including tools like tasks and calendars that help them stay organized and plan their day. The dashboard also consolidates 200+ enterprise systems — including Microsoft 365, Google Workspace, HRIS, and LMS — into a single pane of glass, eliminating the tool-switching that costs employees 4+ hours per week (source: MangoApps integrations product page). For teams looking to embed learning into that same workflow, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). #### #2: Improve Goal Outcomes MangoApps gives admins the ability to set dashboard layouts, customize their appearance, and maintain complete control over published content. Admins also have access to a unique [admin portal](/key-features/company-portal) where they can change domain-wide settings. These comprehensive controls help admins implement company-wide strategies with ease. Management can organize long-term and short-term goals with confidence, knowing that changes, updates, and information will be quickly and effectively distributed throughout the entire company. Personalized news feeds surface targeted updates by role, location, and team rather than broadcasting the same content to every employee — so a warehouse team lead sees operational updates while a marketing manager sees campaign metrics (source: MangoApps frontline/engagement product pages). #### #3: Easily Share Information Content-driven widgets on the MangoApps employee dashboard help marketing and HR teams capture useful insights. MangoApps allows you to format posts in a variety of styles, ensuring that users consume content exactly how it was intended. Creators also have the option of enabling or disabling comments on posts, allowing them to gain employee insight, opinions, and perspectives when appropriate. Advanced admin tools track activities like user engagement and analytics, helping admins learn who has seen specific content. For organizations building out structured communication hubs, [department sites](/key-features/department-sites) extend this capability by giving each team its own targeted content space within the broader dashboard. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring these content flows. #### #4: Boost Employee Engagement Another benefit of the employee dashboard is that you can improve [employee engagement](/solutions/employee-engagement) with a structured internal communication strategy. Unlike email, where responses quickly become messy and disorganized, internal dashboard communication is straightforward, easy to follow, and ensures that each employee is regularly notified and engaged in discussions. User engagement is much easier for admins to monitor as well. MangoApps provides admins with reports that group employees by their level of engagement, giving admins a clear picture of how active users are and helping them set goals for increased employee engagement. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in, and only 13% use intranet tools daily — averaging just six minutes per day (source: SWOOP Analytics). The MangoApps dashboard is designed to close that gap through personalization, mobile access, and AI-assisted content curation that surfaces what each employee actually needs. For a broader view of where employee engagement is heading, the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) report offers relevant context. #### #5: Encourage Team Progress With an employee dashboard, teams are better able to update, monitor, and achieve outcomes. This allows everyone on the team to know what is being done, what needs to be worked on, and who to talk to about their tasks. [Workspaces](/key-features/workspaces) within MangoApps extend this further by giving cross-functional teams a dedicated project environment — with shared files, task tracking, and discussion threads — all visible from the same dashboard view. #### #6: Become A Truly Digital Company — Including Your Frontline Employees work in new ways and need companies that promote and encourage these new structures. Per Emergence Capital, 80% of the global workforce is deskless — and the MangoApps dashboard is built for them, not just for HQ. The dashboard works on personal devices without a corporate email address, VPN, or desk, giving frontline and deskless workers the same real-time access as office employees (source: MangoApps mobile product pages). Low dashboard adoption is not a minor inconvenience: replacing a single frontline employee costs between $4,400 and $15,000 on average. Keeping frontline workers informed and connected through a mobile-first dashboard is a direct retention lever. MangoApps employee dashboard benefits employees not just in the office but anywhere they work, making it the right tool to bring your entire organization — including the floor, the field, and the store — into the digital age. For retail-specific context, [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) shows how frontline teams put these tools to work. ### Is MangoApps Recognized as a Leading Intranet Platform? Yes. MangoApps has been evaluated by independent analysts as a leading [modern intranet](/solutions/modern-intranet) solution. The platform was included in a major research firm's intranet platforms evaluation — see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) — and earned recognition in [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report). These evaluations assess integration depth, personalization, frontline access, and admin controls — the same dimensions the six benefits above address. ### What Integrations and Implementation Timeline Should I Expect? The MangoApps dashboard consolidates 200+ enterprise systems — including Microsoft 365, Google Workspace, HRIS, and LMS platforms — into a single interface, eliminating the tool-switching that costs employees 4+ hours per week (source: MangoApps integrations product page). Most customers reach 90%+ adoption within the first six months. Implementation timelines vary by organization size and integration complexity, but MangoApps provides dedicated onboarding support and a configurable [webpage builder](/key-features/webpage-builder) that lets admins stand up branded dashboard experiences without engineering resources. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers what HR leaders should plan for during a platform rollout. ### What Results Can I Expect After Launching a Dashboard? The MangoApps employee dashboard is not a feature list — it is a measurable business outcome. OU Health achieved 87% workforce engagement within months of launch. PetSmart reported 4x the industry engagement benchmark. Across the customer base, MangoApps achieves 90%+ average adoption within six months (source: MangoApps case studies — OU Health, PetSmart). For organizations evaluating employee engagement software, these benchmarks provide a concrete baseline against which to measure your own rollout. To see how one organization structured their communications deployment, read [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology). MangoApps employee dashboards help both employers and employees develop long-lasting results well beyond the capabilities of email or a traditional intranet. Schedule a personalized demo to discover how MangoApps can best benefit your organization. --- # MangoApps Employee Dashboards: Built For Better Productivity **Author:** Anjali **Published:** 2018-09-06 **Category:** modules-features As any athlete knows, proper technique makes life a lot easier. In both sports and business working hard will never be enough if you aren’t also working smarter, staying innovative, using good form and utilizing the right tools for success. One of today’s essential business techniques is to provide your workforce with accesses to everything […] # MangoApps Employee Dashboards: Built For Better Productivity According to IDC, employees spend 2.5 hours per day searching for information across fragmented systems. For organizations running separate tools for communications, scheduling, task management, and HR, that cost compounds at every handoff. MangoApps employee dashboards address the problem at its source: rather than requiring employees to navigate between disconnected systems, the dashboard surfaces role-relevant information automatically — communications, task assignments, company updates, shift schedules, and external integrations — in a single personalized workspace accessible on any device. An employee dashboard is an information management layer that aggregates data, communications, and tools from across an organization's systems into one interface. The goal is not to host content — it is to route the right content to the right employee without requiring them to actively search for it. A static intranet page requires intent: the employee must know what to look for, know where it lives, and navigate there. A personalized dashboard requires none of those steps. The dashboard is typically the first screen an employee opens at the start of their shift. Getting that screen right determines whether a platform becomes central to daily work or remains something employees check occasionally when they remember it exists. ## Why most intranets fail the daily-use test According to Social Edge Consulting, 91% of organizations operate an intranet — but only 13% of employees use it daily, and nearly a third never log in at all. SWOOP Analytics puts the average at six minutes per day. Those numbers don't indicate low interest in information. They reflect a structural problem: most intranet platforms ask employees to come find information rather than delivering it where employees are already working. A dashboard-centric approach inverts that model. The platform surfaces what is relevant for each employee — based on role, team, and location — rather than publishing to a shared feed and expecting everyone to filter it individually. According to Emergence Capital, 80% of the global workforce is deskless or frontline. A dashboard that works only for desk-based workers with corporate laptops excludes the majority of the workforce it is meant to serve. MangoApps employee dashboards are available on mobile devices without requiring a corporate email address, VPN, or IT provisioning — a meaningful distinction for healthcare systems, retail chains, and logistics organizations where most employees never sit at a desk. ## What the dashboard gives every employee MangoApps employee dashboards are configured at the admin level and personalized automatically for each employee. Three settings govern the balance between standardization and individual flexibility. **Locked dashboards** give every user the same layout with no customization. Administrators choose which widgets appear and in what order. This is the right setup for organizations that need every employee to see the same announcements, compliance notifications, or shift updates without variation. **Semi-customizable dashboards** provide a defined widget set but let employees rearrange and resize. The information stays consistent; the presentation adapts to individual preference. This works well for organizations that want consistent visibility into key data while giving employees some ownership over their workspace. **Fully customizable dashboards** give employees complete control — adding, removing, and repositioning widgets. For knowledge workers with complex, self-directed workflows, this level of personalization supports the kind of habitual daily use that sustains long-term adoption. All three options share a core feature: content is always auto-personalized by role, team, and location. A frontline nurse at a hospital campus sees updates specific to their department and facility; an employee in logistics sees notifications from logistics teams, not from marketing or finance. A manager sees team task lists alongside company announcements. Personalization happens at the data layer automatically — employees do not configure it themselves. ## The widget library: what powers the dashboard The utility of a dashboard depends entirely on what it can surface. MangoApps provides a widget library across six functional categories that administrators can enable, configure, and combine. **Company and team widgets** broadcast updates from departments, projects, and groups. For shift-based or distributed workers who don't attend weekly all-hands meetings, these widgets are often the primary channel for organizational communication. **Content widgets** surface posts, pages, forms, and files relevant to each user. An employee who needs the current version of a safety procedure doesn't search a document repository — the widget surfaces it based on their team assignment and recent access patterns. Connecting related content this way also closes the gap that [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) identifies as a primary driver of disengagement: employees who feel uninformed and disconnected from organizational priorities. **Employee engagement widgets** support recognition, surveys, polls, and peer interaction. Embedding recognition and feedback touchpoints directly into the daily dashboard — rather than routing them to a separate platform — increases the frequency with which those interactions happen. **Task, event, and calendar widgets** connect to-do lists, deadlines, and calendar data to the primary workspace view. Supervisors can see shared task lists and track action items; employees see their own work queue without switching to a separate project management tool. **External integration widgets** connect to more than 50 third-party applications — HR systems, ITSM platforms, and productivity tools. Employees access what they need from a single interface rather than maintaining separate credentials and context for each system. **Admin widgets** provide administrators with shortcuts to MangoApps network settings and management functions, visible only to users with admin permissions. ## What companies are getting from a unified dashboard MangoApps deployments in frontline-heavy industries have produced measurable outcomes: 87% workforce engagement within months of launching a branded employee app dashboard at OU Health, and a 4x industry engagement multiple reported by PetSmart following adoption of a unified mobile dashboard experience. Those results align with what the underlying access data predicts. When employees start their shift on a platform that contains their schedule, task assignments, team communications, and HR tools, adoption becomes a side effect of the workflow rather than a separate change management goal. A single [employee app](/solutions/employee-app) can consolidate what are often 200 or more previously separate systems — reducing the license footprint, training overhead, and coordination cost of maintaining tools that don't communicate with each other. For organizations already running a dedicated workforce management system, MangoApps [workforce management](/solutions/workforce-management) integrations surface scheduling data directly in the dashboard layer. Shift schedules, clock-in controls, and time-off requests appear alongside team communications, eliminating the context switch that currently requires frontline workers to maintain two separate applications. ## How long does implementation take? MangoApps dashboards are configured through the administrative interface without developer involvement. The widget gallery is accessible to admins who can activate, configure, and arrange widgets for different user groups. Organizations with existing HR, ITSM, or productivity tool investments can surface those systems through integration widgets rather than asking employees to change how they work. The implementation timeline depends on integration complexity, but the platform is designed to support phased rollout. A practical approach: start with locked dashboards for high-visibility groups — frontline managers, HR — then expand customization and widget options as employees become familiar with the workspace. Most organizations see initial deployment within weeks, with full adoption rollouts measured in months rather than quarters. ## How MangoApps compares to alternatives The employee dashboard and intranet category spans a wide range of platforms — from SharePoint-based deployments that require IT configuration for each new user to purpose-built employee experience platforms designed around frontline access. The primary differentiators for MangoApps are the mobile-first, no-email onboarding path and the native workforce management layer that puts scheduling alongside communications in one view. For organizations evaluating the full category, the [ClearBox 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an independent assessment including criteria specific to frontline and deskless deployments — useful context for organizations where the 80% deskless workforce figure is not an abstraction but an operational reality. The distinction that matters most in head-to-head evaluation is whether the platform was designed with frontline access as a core requirement or retrofitted as a mobile app after the fact. The answer usually shows up in the onboarding flow: does a new frontline employee need an IT ticket and a corporate email to get a dashboard, or can they scan a QR code on their first day and be fully provisioned in minutes? ## The case for acting on the dashboard consolidation The productivity argument is direct. Employees who spend 2.5 hours per day — an IDC-documented figure — searching for information across fragmented systems are spending those hours on overhead, not on the work they were hired to do. Each context switch between disconnected systems carries a coordination cost that is individually small and collectively significant. Multiply it across a workforce and the aggregate is substantial. MangoApps employee dashboards address that cost by making information come to the employee rather than requiring the employee to go find it. The widget model, role-based personalization, and multi-device access — consistent from desktop to mobile — create a platform that functions for both desk-based knowledge workers and deskless frontline employees without requiring two separate strategies. For organizations ready to evaluate what a unified dashboard would look like for their specific workforce profile, starting with a pilot group that spans both desk and frontline workers gives a clearer picture of consolidation opportunity than a desk-only proof of concept does. The usage delta between those two groups — and what drives it — is usually the most revealing signal a platform evaluation produces. --- # Why MangoApps Employee Directory Stands Out: Bypassing Common Pitfalls Faced by Businesses **Author:** Anjali **Published:** 2018-08-28 **Category:** modules-features Maintaining an updated employee directory has become a daunting task in today’s rapidly evolving corporate landscape. Traditional directories, often static in nature, no longer cater to the dynamic demands of modern workforces. Enter MangoApps: an innovative employee directory solution tailored for the contemporary office. MangoApps Employee Directory: Overcoming Challenges in Traditional Systems 1. Ditching Spreadsheets […] # Why MangoApps Employee Directory Stands Out: Bypassing Common Pitfalls Faced by Businesses Per Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in, and the average daily usage sits at six minutes per day, per SWOOP Analytics. That gap is not an adoption problem that better onboarding or a refreshed interface can fix. It is an infrastructure problem: most employee directories were built for the workers who were easiest to reach, not the ones who needed them most. Per Emergence Capital, 80% of the global workforce is deskless — working in warehouses, retail floors, clinics, and field sites without a managed device or corporate email address. The default assumption behind most directory infrastructure — that every employee has a corporate credential and a VPN connection — excludes this majority before they ever open the platform. The result is a communication tool that works for headquarters and fails everyone else. This is the structural problem MangoApps solves differently. The distinctions are architectural, not cosmetic: access without a corporate email address, data that stays current without manual intervention, search that spans the entire digital workplace, and security built from the start rather than retrofitted for compliance. What follows examines each dimension in order of the gap it closes. ## The access model is where most directories fail first Authentication architecture is the most consequential design decision in directory infrastructure, and it is the one most organizations overlook until adoption numbers disappoint. A directory that requires a corporate email address and a VPN login works for desk workers. For the 80% of the workforce that is deskless, that architecture is a wall. Disconnected workers do not stop seeking information; they route around the directory using slower, less accurate channels — group text threads, posted bulletins, shift-start briefings. The cost appears in turnover: replacing a single frontline employee costs between $4,400 and $15,000, per industry research cited in MangoApps' mobile product documentation, and disconnection from colleagues and company culture is a documented driver of churn in deskless industries. MangoApps removes the email requirement at the infrastructure level. Frontline employees access the full directory through the [employee app](/solutions/employee-app) on a personal iOS or Android device — no VPN, no corporate credential, no IT provisioning ticket. A single invitation link, a personal phone, and they are inside the same directory environment as headquarters. For healthcare, logistics, and manufacturing organizations, this is the architectural difference between a directory that reaches the full workforce and one that effectively operates as a desk-worker contact list. OU Health achieved 87% workforce engagement within months of launching a branded employee app with an integrated directory, per MangoApps case study data. That figure does not reflect a better interface. It reflects a different access model: one that did not exclude the clinical staff, technicians, and support workers who make up the majority of a health system's payroll. ## Why data quality determines whether employees trust what they see The second failure mode is data drift. Most directory deployments start accurate and degrade over time. A role change, a reporting-line update, a department transfer — the HRIS system gets updated; the directory does not. Employees stop trusting what they see and stop using it. The IT team schedules another manual sync, and the cycle repeats. This is an architecture problem, not a maintenance discipline problem. Any directory that requires manual intervention to stay current will drift from reality. The question is whether the system is designed to self-correct or to depend on someone noticing. MangoApps resolves this through HRIS integration that automatically syncs employee roles, permissions, and profile data whenever a record changes in the source system. No admin tickets, no scheduled imports, no spreadsheet maintenance. The directory reflects the source-of-truth HR system in near real time, so a manager looking up a direct report's current role gets accurate data — not the version from the last export. This is the single most reliable mechanism for eliminating the trust erosion that kills directory adoption after launch, particularly in organizations with high frontline turnover where roles change frequently. ## Per IDC: 2.5 hours a day lost to finding the right person Per IDC, employees spend 2.5 hours per day searching for information. A meaningful share of that time is people search, not document search — finding the subject-matter expert, the regional compliance lead, the project owner for an initiative that predates current documentation. Basic keyword search returns a list of names. For any organization with more than a few dozen employees, a list of names is not an answer. Competitors including Unily now lead with AI-curated people-search experiences that surface the right employee in seconds using natural-language queries — a capability that has shifted from differentiator to table-stakes in enterprise directory evaluations over the past 18 months. Any evaluation that does not test natural-language people search is measuring last year's feature set. MangoApps addresses this through AI-assisted universal search that spans the employee directory and connected storage platforms — SharePoint, Google Drive, Box, and Dropbox — in a single query. An employee searching for "the person who handles compliance approvals for the Northeast region" gets a relevant result rather than a disambiguation page. That friction reduction compounds across every search, every day, across the full workforce. Applied to the IDC baseline, a 10% improvement in information retrieval for a 500-person organization at a $30 average burdened labor cost recovers roughly $1 million per year in time previously lost to search. The directory is not a standalone tool; it is an accelerant for every other workflow it connects to. ## The integration layer that converts a directory into daily infrastructure Standalone directory applications solve one problem and create several others. Employees manage separate logins for the directory, the messaging tool, the document library, and the scheduling system. Context switching erodes productivity. Data falls out of sync across platforms. The IT team inherits a portfolio of point solutions, each with its own maintenance burden and renewal cycle. A [modern intranet](/solutions/modern-intranet) that integrates the employee directory with collaboration, messaging, and content tools in a single environment changes that calculus. Org charts synchronized with AD/LDAP sit alongside department pages, project workspaces, and company announcements — so finding a colleague, messaging them directly, reviewing their department's resources, and understanding their role in an active project all happen in the same session, not across four browser tabs. TeamHealth consolidated more than 200 enterprise systems into one mobile dashboard, per MangoApps case study data. That consolidation is not an edge case; it represents the reduction possible when a connected platform replaces a fragmented set of point solutions. For organizations still running a directory as a separate tool, the fragmentation cost is present and measurable. Consolidation is what converts it into a recoverable number. ## Security as a documented requirement, not a procurement conversation Five competitors have moved security compliance to a headline positioning argument in the past 12 months. That shift reflects where enterprise IT evaluation has settled: a directory that stores role data, reporting relationships, and contact information without documented access governance creates auditable risk, particularly in healthcare, finance, and government-adjacent industries where regulators expect evidence of access control. MangoApps supports SAML 2.0, OAuth 2.0, and single sign-on (SSO) to ensure that directory access is authenticated, auditable, and aligned with existing identity management infrastructure. Deployment options span public cloud, private cloud, and on-premise environments. SOC 2 certification is current. Data residency options are available for organizations with geographic data handling requirements. For IT teams working through procurement review, the compliance conversation with MangoApps tends to be shorter than with alternatives — the requirements are documented and provable rather than negotiated case by case. Independent analysis of MangoApps' security architecture and directory capabilities, benchmarked against leading competitors, is available in [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report). ## The structural questions that reveal whether a directory will actually work Enterprise directory evaluations typically arrive at the feature checklist before the structural questions. That sequence produces shortlists of products that look similar at the surface and diverge on dimensions that appear only after implementation. The structural questions are simpler: Does the directory work for the workers who are not at a desk? Does it stay current without manual intervention? Does it connect to the tools employees already use, or does it add another login to manage? Does the security architecture meet the requirements the IT team will be asked to document in a compliance review? Per Social Edge Consulting, only 13% of employees use an intranet daily under normal conditions. Organizations that consistently beat that figure share recognizable characteristics: mobile-first access that does not require a corporate credential, data that self-corrects when the HR system changes, and search that returns the right person rather than a filtered list. None of those characteristics is a feature-checklist item. They are architectural decisions made before the interface was built. The ROI case follows directly. With frontline replacement costs running $4,400–$15,000 per employee and turnover rates exceeding 60% in some deskless industries, any platform that improves daily connection and utility carries a retention dividend that compounds over time. The business case is not primarily about the directory feature; it is about what the directory enables when it reaches the full workforce and stays accurate without maintenance overhead. For teams quantifying the cost of the current state and framing the investment for leadership review, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how HR and IT organizations are rethinking directory infrastructure as part of a broader employee experience strategy — including how to structure the internal business case around the access, accuracy, and integration dimensions that determine whether a directory produces the engagement numbers or the six-minute sessions. --- # 8 Powerful Ways MangoApps Can Enhance Employee Engagement **Author:** April Thomas **Published:** 2018-08-06 **Category:** employee-engagement It’s no secret that successful organizations are constantly working to enhance employee engagement. When employees see themselves as an integral part of an organization, they naturally become brand ambassadors. Companies and corporations want consumers to see them through the eyes of these empowered employees. Creating enthusiastic employee engagement takes work, communication and a solid understanding […] # 8 Ways MangoApps Can Enhance Employee Engagement Maya runs HR for a regional grocery chain with 2,400 employees spread across 60 locations. Last quarter, she launched a company-wide engagement survey. The response rate came back at 34%. When she dug into the data by role, the pattern was unmistakable: the responses came almost entirely from store managers and corporate staff. The cashiers, stockers, and deli associates the survey was designed to reach — the people whose engagement actually predicts turnover — were barely represented. Maya's problem wasn't the survey instrument. It was delivery. This is the most common failure mode in employee engagement programs, and it happens before anyone reads a single response. Per Emergence Capital, 80% of the global workforce is deskless — working in stores, warehouses, clinics, and distribution centers without a corporate laptop or company email address. Most [employee engagement software](/solutions/employee-engagement) was built for the other 20%. The infrastructure mismatch is baked in before the first question is written. What follows is how MangoApps addresses eight of the most common gaps in engagement programs — starting with the one that breaks most of them before they start. --- ## 1. Reach the 80% before running the first survey The access problem shows up in intranet data long before it shows up in engagement scores. Per Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in at all, and only 13% use one daily. Per SWOOP Analytics, the average employee spends six minutes per day on intranet tools. Engagement surveys sent through these same channels inherit the same structural failure. MangoApps delivers a branded mobile employee app that works on personal phones without a corporate email address, VPN, or IT provisioning queue. A new associate can be onboarded via QR code or SMS invite within minutes of hire, before their first shift is over. The result is measurable: OU Health achieved 87% workforce engagement within months of launching a branded employee app on MangoApps. PetSmart reported a 4x industry-standard engagement rate after deploying a mobile-first app with frontline access. The pattern is consistent. High engagement rates follow when the platform reaches workers where they actually are — not where the system expected them to be. --- ## 2. Create surveys at the team level, not just the company level A single company-wide survey collapses the distinct needs of different departments, shifts, and locations into one averaged result. A warehouse team's concerns about safety and scheduling show up in the same number as a corporate team's feedback on career development — which means neither gets addressed specifically. The aggregated score becomes a ceiling on meaningful action. MangoApps allows survey creation at the department, team, shift, and project level alongside company-wide campaigns. A shift supervisor can run a quick pulse check on a new scheduling change without waiting for the next quarterly cycle. A customer service lead can gather feedback on a process change before it rolls out to the broader organization. This distributes the capability for listening throughout the organization rather than centralizing it exclusively in HR. Employee engagement surveys and employee engagement questionnaires designed at the team level surface problems that company-wide surveys average away. Because the questions can be targeted to specific operational contexts, the data is more actionable for the manager closest to the issue — and the insight arrives in time to be useful. --- ## 3. Build anonymity into the structure, not just the policy Most employees say they trust anonymous surveys and then don't answer candidly. The reason is structural: when the survey runs on a platform tied to a work identity — a corporate email, a role account, a manager-assigned login — the anonymity feels conditional regardless of what the policy says. Employees do the math on traceability and adjust their responses accordingly. MangoApps supports anonymous surveys where respondent identity is not collected by survey creators, team leads, or administrators at any level. That is a structural guarantee, not a policy assertion. For employee engagement questionnaires focused on management quality, workload, compensation, or organizational direction, structural anonymity is often the difference between data that reflects what employees actually think and data that reflects what they're willing to put their name on. Anonymous surveys also change the nature of follow-up conversations. When managers know they're seeing unfiltered sentiment rather than socially managed responses, they use the data differently. --- ## 4. Connect feedback directly to action before trust erodes Survey data that sits in a dashboard without producing visible change erodes trust in engagement programs faster than low scores do. Employees who complete surveys and see no visible response become less likely to participate in future rounds — not because they're apathetic, but because they've updated their belief that the organization is actually listening. This is the mechanism behind declining response rates at organizations that run frequent surveys without closing the loop. MangoApps connects survey insights to task assignment. After analyzing feedback, managers can create action items assigned to specific individuals by role and responsibility, with accountability visible to relevant parties. The platform tracks participation in real time, enabling targeted reminders to non-respondents without manual list-building. Points and recognition can be awarded for survey participation, which increases response rates without requiring individual outreach from managers. The retention math is direct: replacing a disengaged frontline employee carries a direct cost of $4,400–$15,000 per person. Closing the feedback loop is how engagement investment produces measurable retention outcomes rather than just better survey scores in a dashboard no one acts on. --- ## 5. Target what each employee sees by role, location, and team A company-wide news feed that surfaces the same content to a warehouse associate in Phoenix and a corporate analyst in Seattle is not engagement infrastructure. It is noise. When content isn't relevant to the person receiving it, they stop opening the app. When they stop opening the app, the surveys, task updates, and communications that depend on the same channel stop reaching them. MangoApps supports role-based, location-based, and team-based content targeting, with AI-curated feeds that surface the most relevant updates for each employee's context. Targeted push notifications reach frontline workers who may not check the app proactively, giving time-sensitive communications the same reach as the engagement programs that depend on them. For organizations managing distributed, shift-based workforces, this kind of content personalization is what separates an app employees open at the start of every shift from one that competes with every other notification on their phone — and loses. --- ## 6. Remove the tool-switching friction that disengages people The cognitive cost of navigating disconnected systems accumulates invisibly. In retail and distribution environments, the typical worker navigates six to eight separate tools for scheduling, communications, training, HR self-service, and company news — none of which shares data with the others. Per IDC, employees spend 2.5 hours per day searching for information across these disconnected systems. That overhead is a direct disengagement mechanism. Employees who spend a meaningful share of their workday managing tool-switching rather than doing their job don't lack engagement — the infrastructure has made engagement expensive. They're paying a friction tax every shift. MangoApps consolidates messaging, scheduling, task management, surveys, learning content, and HR self-service into a single interface. For frontline workers with five minutes between tasks, a unified platform is not a convenience. It is the difference between engaging and not engaging at all. Reducing tool sprawl is not a platform story; it is an engagement story. --- ## 7. Embed training and employee engagement in the same workflow Employee engagement training and learning and development are connected at the outcome level — employees who see a path to growth remain more consistently engaged over time — but most organizations run them on separate platforms that don't share data. A manager can observe that an associate is disengaged but cannot easily connect that signal to a stalled development path. Two systems, zero visibility into the relationship between them. MangoApps embeds training on employee engagement alongside communications and survey tools in the same interface associates already use daily. Course assignments, progress tracking, and learning content are accessible from the same app as shift schedules and team updates. This doesn't require L&D teams to rebuild curriculum — it requires the learning platform to be present where employees already are, rather than waiting in a separate tab nobody opens. [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) documents how embedding learning into daily workflows — rather than isolating it in a standalone LMS — improves both completion rates and engagement outcomes. The infrastructure integration is what makes the connection between learning and engagement visible. --- ## 8. Benchmark engagement against external data, not just internal trends Internal engagement scores are useful for tracking year-over-year change, but they don't establish whether an organization has improved relative to industry peers or has simply normalized a low baseline. An HR leader whose scores rose three points from last year doesn't know if that improvement is meaningful without an external frame of reference. The number needs context before it can support a decision. [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) provides current engagement benchmarks by region, industry, and workforce type — the external reference that converts internal survey trends into context leadership can act on. MangoApps integrates with HRIS systems to connect survey data to workforce demographics, enabling analysis of engagement by department, tenure, role, and location over time. That connection is what allows an HR leader to identify not just that engagement improved, but which population drove it, which intervention moved the needle, and where the gap remains. --- ## What Maya found six months later When Maya ran her follow-up survey six months after deploying MangoApps, the response rate came back at 79%. More importantly, the data showed her frontline for the first time. The gap between hourly associates and corporate staff was real — but narrower than the original 34% response rate had implied, because the original 34% hadn't actually measured it. The technology that makes employee engagement programs work is not a better survey design. It is making sure the survey reaches the people it was designed to hear from — and that the infrastructure around it closes the loop, personalizes the content, and removes the friction that disengages people before they take the survey. The [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology) case study documents how a distributed organization closed a similar access gap — and what changed in engagement data when their frontline could actually participate. --- # How To Improve Company Culture **Author:** April Thomas **Published:** 2018-08-03 **Category:** company-culture Improving company culture has always been an influential factor in the professional business world.  However, within the last decade or so, it has become an increasingly important point of real discussion. At MangoApps, we couldn’t be more excited. We’ve known for a long time that a strong company culture directly correlates to a more sustainable […] # How to Improve Company Culture Per IDC, employees spend an average of 2.5 hours every day searching for the information they need to do their jobs. That friction isn't just a productivity problem — it's a culture problem. When employees can't find what they need, can't easily reach colleagues, and navigate different tools for every function, the daily experience of work feels fragmented regardless of what values leadership has committed to in writing. Six strategies help organizations build cultures that hold over time. What makes them different from most culture advice is the starting point: structural gaps come first, not last. Behavioral changes — recognition, community, trust — don't compound when employees can't reliably receive or respond to them. ## Anchor culture in a clear identity Every effective culture program starts with a clear answer to a deceptively simple question: what kind of organization do we want to be, and what behaviors reflect that? The culture identity is the lens through which hiring decisions, recognition criteria, communication norms, and promotion signals should all be interpreted consistently. Organizations that skip this step apply culture tactics in isolation — recognition programs with no clear criteria for what earns recognition; community-building efforts with no shared purpose to build around; feedback channels with no established norm for what happens when feedback surfaces. Getting specific about culture identity doesn't mean writing a values document. It means translating values into observable behaviors: the things a new employee would notice within the first 90 days that signal the organization is living what it says it believes. Without that specificity, culture programs run as disconnected initiatives rather than a coherent system — and organizations end up measuring activity (events held, surveys sent) rather than the outcomes that actually reflect whether culture is improving. ## Reach every employee, not just the ones at a desk Per Emergence Capital, 80% of the global workforce is deskless — working in healthcare, retail, manufacturing, logistics, and other settings where a desktop workstation isn't part of the job. Culture initiatives launched on platforms requiring a corporate email address, VPN access, or a desktop login exclude this majority before they begin. The employees with the greatest cultural distance from leadership are usually those with the highest turnover risk. Job turnover in organizations with strong culture runs under 14%. In organizations with weak culture, it approaches 50%. That gap is widest exactly where cultural communication is hardest to reach: frontline teams, distributed staff, shift workers, and employees without corporate email accounts. Reaching this group requires changing the enrollment model. Most enterprise platforms provision accounts through IT, require a corporate email to register, and optimize their interfaces for desktop browsers — conditions that don't apply to the majority of the workforce in most industries. Mobile-first access — joinable via QR code or SMS link in under two minutes without IT provisioning — is the condition under which frontline workers can participate at all. The [employee engagement](/solutions/employee-engagement) infrastructure that supports culture programs has to be accessible on a personal phone between shifts, not just on a company-provisioned laptop in an office. Treating frontline enrollment as a second phase produces the two-class culture that most culture programs are trying to eliminate. ## Build trust through consistency, not communication events Trust is built through repeated small signals that align over time: leadership saying something and following through; difficult news communicated directly rather than softened or delayed; feedback acknowledged and acted on rather than collected and forgotten. None of these require a communication event. They require a cadence. For leaders of distributed workforces, building trust at scale means creating the conditions for regular, observable signals — not just high-production quarterly broadcasts. Platforms that make leadership communication visible over time, where employees can see what was said and compare it to what actually happened, create the ambient consistency that trust requires. One-way broadcast tools, however polished, rarely close the trust gap because they don't provide the bidirectional signal history that employees use to calibrate whether leadership is reliable. Per Gallup's [2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), organizations that collect and act on employee feedback continuously outperform those that collect it in annual cycles. The mechanism matters more than the frequency: feedback embedded in the daily digital environment — surfaced in the same channel where a manager posts an announcement — gets acted on faster than feedback collected through a standalone survey tool that employees access once a quarter. ## Recognize people in ways that are specific and visible Recognition has the highest return per dollar of any culture investment, with one narrow condition: it has to be specific, timely, and visible to the people who matter most to the recipient. A general acknowledgment in a private performance review has minimal culture value. A specific callout — naming what the person did, tying it to a cultural value or a measurable outcome, shared in a channel where peers can see it — has a documented effect on both engagement and retention. The specificity tells employees which behaviors are actually valued, not just which employees are currently in good standing. The same logic applies to development investment. Learning embedded in the daily flow of work — accessible on a mobile device, integrated into tools employees already use — reaches more of the workforce than scheduled training sessions. [Embedding learning and development into daily work](/articles/learning-and-development-strategy-embedded-in-daily-work) has been shown to increase both completion rates and knowledge retention compared to classroom-style formats, because the learning context is closer to the moment when the skill is actually needed. ## Create community across the entire organization Community in a distributed workforce doesn't emerge organically — it has to be intentionally architected. The specific mechanism varies: a shared channel for a team, a recognition feed visible across the organization, a wiki where institutional knowledge accumulates over time rather than disappearing when someone leaves. The conditions that make community work are consistent regardless of mechanism: the space must be genuinely inclusive (frontline workers can participate, not just desk employees), consistently active (something new to encounter most days), and bidirectional (employees can contribute, not just consume). Per Social Edge Consulting, 91% of organizations operate an intranet, but nearly a third of employees never log in and only 13% use it daily. Per SWOOP Analytics, the average employee spends six minutes per day on intranet tools. Those numbers don't describe cultural resistance to technology. They describe tools built for conditions most employees aren't in — and a community space that most of the workforce can't access, or won't return to, isn't a community. Building community also requires keeping the space current. The most common reason intranet adoption collapses after an initial launch is that content goes stale within 60 days — announcements stop being posted, wikis stop being updated, and employees stop checking. Distributed admin ownership — where individual teams own their own spaces rather than routing every update through a central communications team — is what prevents the information decay that kills adoption over time. ## Measure culture progress, don't assume it Most organizations treat culture as a feeling rather than a metric. This is why culture programs rarely survive budget scrutiny: they can't demonstrate ROI, so they get deprioritized when competing initiatives are easier to justify. The signals are measurable. Active user rates on employee platforms, participation in recognition moments, pulse survey response rates, onboarding completion rates, and eNPS trend over time — none of these are perfect proxies for culture health, but together they show whether initiatives are reaching the right people, whether engagement is trending in the right direction, and where gaps are forming before they become resignation events. Effective measurement requires separating desk-based and frontline reporting. A single aggregate engagement rate obscures the gap between the employees a culture program is working for and the employees it's missing entirely. Disaggregated data — by role, by location, by communication channel — is what shows which parts of the organization the culture is actually penetrating. ## What sustained improvement requires Culture doesn't change because leadership commits to it in a strategy document. It changes because the daily experience of work — the tools employees use, the recognition they receive, the feedback they can give, the community they have access to — gradually becomes different from what it was before. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents how organizations across industries are replacing fragmented, tool-per-function architectures with unified employee hubs as the foundation for culture programs. The structural change precedes the measurable culture shift — not the other way around. The six strategies covered here — clear identity, inclusive reach, consistent trust, meaningful recognition, genuine community, and measurable progress — are not a sequence. They reinforce each other and depend on the same underlying infrastructure: the ability to communicate across the whole workforce, collect feedback in context, recognize people visibly, and track what's changing over time. For organizations where 80% of the workforce doesn't sit at a desk, getting that infrastructure right isn't preparatory work for the real culture program. It is the culture program. --- # How to Increase Team Collaboration Within the Workplace **Author:** Luke Walton **Published:** 2018-05-14 **Category:** team-collaboration Organizations are finding it difficult to increase team collaboration across the workplace. The challenge is nudging team members to get to know each other better, have them thrive on each other for success, while increasing the communication within departments and employees. With remote employees and offices across many locations, adapting to a collaborative team environment […] # How to Increase Team Collaboration Within the Workplace Organizations are finding it difficult to increase team collaboration across the workplace. The challenge is nudging team members to get to know each other better, have them thrive on each other for success, while increasing the communication within departments and employees. With remote employees and offices across many locations — and with 80% of the global workforce being deskless, per Emergence Capital — adapting to a collaborative team environment can prove to be a nightmare. Continue reading to learn how your workplace can maintain and improve team collaboration. ## The 6 Best Ways To Increase Team Collaboration Within the Workplace: ### #1: Team Building Games First, we have team building games and activities. Team building games are one of the best and most fun ways to build new relationships or amend old ones. It could be as simple as playing a favorite team sport like basketball, football, disc golf or even a water sport. Team building activities are an effective way to teach employees how to trust one another's judgment. These activities can also contribute to more efficient communication, and most importantly can help break the ice. ### #2: Streamlining The Process Breaking down company silos allows employees to reach out with valuable suggestions that will help streamline a company's processes. This improves team collaboration and, if the proposal is implemented, can make an employee feel like they belong. Encourage brainstorming and ask your team to come up with ideas around streamlining and how to implement them. Employees lose over four hours per week switching between disconnected systems, making a unified approach a productivity necessity rather than a convenience. ### #3: Use a Team Collaboration Portal There isn't a better way to increase team collaboration than with a team collaboration software platform — specifically one that functions as a true intranet and employee experience hub rather than just a file repository. Per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in to it, and only 13% use one daily. The root cause is often a platform that delivers an undifferentiated feed rather than role- and location-specific content. AI-curated personalization — surfacing the right information to the right employee automatically — is now a baseline expectation for modern collaboration platforms, not a premium add-on. Beyond personalization, employees spend an average of 2.5 hours per day searching for information, per IDC. A well-implemented collaboration portal cuts that waste directly. **A team collaboration software solution can:** - Provide a platform to store and share files with coworkers - Allow real-time editing to documents, ensuring every employee has the current version - Grant simplified training to employees through videos and documents, supporting [employee engagement training](/articles/learning-and-development-strategy-embedded-in-daily-work) at scale - Bring together employees from different departments and locations — including frontline workers who lack a company email address and are routinely excluded from standard tools, creating a two-tier workforce communication problem Because of the collaboration platform, employees are able to converse on a day-to-day basis about various internal tasks, group activities, policy changes, project challenges, ideas, questions, and more. One large enterprise deployment achieved 90% frontline adoption within the first six months of rolling out a dedicated [employee app](/solutions/employee-app), demonstrating what a well-implemented platform can deliver. ### Increasing Team Collaboration at Kelly-Moore Paints Learn how Kelly-Moore Paints got its workforce of over 1,600+ employees all collaborating while on the retail floor. ### #4: Improve Employee Communication Improving internal [employee communications](/solutions/employee-communications) is not something organizations have an assigned budget for. Nevertheless, it is one of the most important aspects of any organization. You could have some of the most talented individuals in the world, but without a cohesive team, an active and harmonious culture cannot be sustained. In order to improve communication, employers must entrust people to share information, challenges, feedback, and anything that will help to make work easier. Frontline and distributed employees who lack a company email address are routinely excluded from standard collaboration tools — a gap that structured employee communications strategy must address directly. For a deeper look at how leading organizations are closing this gap, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) offers current benchmarks and practical frameworks. ### #5: Improving Employee Engagement Engage employees from day one. Instead of dull PowerPoints and paperwork, start with eagerness and curiosity. Help employees get to know their co-workers by pairing them with a mentor. Familiarize them with a positive culture by creating a perfect first impression. Employee engagement courses and structured onboarding programs tied to a collaboration platform make this first impression consistent across every location and shift. Another way to improve employee engagement is by providing the option of working from home. Give employees the freedom to work from a more comfortable environment, remove travel and traffic time, and improve accountability as well. One healthcare organization achieved 87% workforce engagement within a few months of launching a branded collaboration app — a concrete outcome worth benchmarking against. For context on what drives engagement at scale, [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) provides current data on what employees actually need from their employers. Poor engagement is also a measurable retention risk: replacing a frontline employee costs between $4,400 and $15,000, making disconnection a financial issue, not just a culture one. ### #6: Improving Team Collaboration With Interdependence Lastly, creating a sense of community and synergy in any team is a must for success and interdependence. Employees working as an effective team thrive on each other's success. An individual or a department cannot single-handedly achieve success within a workplace. Without cooperation, communication, and trust, the most profitable companies will not be able to succeed in the long-run. ### Encourage People to Socialize Outside of Work Getting to know coworkers outside of work can boost interdependence and increase team collaboration and communication. To learn more about how to increase team collaboration, schedule a personalized demo to see how MangoApps can help. --- ## How Do You Measure Team Collaboration Success? Implementing the six methods above is only half the work — knowing whether they are producing results is the other half. The most practical measurement approaches include: - **Employee engagement surveys and questionnaires:** Regular employee engagement surveys give teams a structured way to surface friction, disconnection, and communication gaps before they become retention problems. Pulse surveys tied to a collaboration platform can track sentiment over time rather than capturing a single annual snapshot. - **Platform adoption metrics:** Track daily active users, content contribution rates, and search query volume inside your collaboration portal. Per SWOOP Analytics, the average daily time spent using intranet tools is only six minutes — a baseline that well-configured platforms consistently exceed when content is personalized and relevant. - **Cross-departmental project outcomes:** Monitor whether projects involving multiple departments are completing on time and within scope. Improvement here is a direct signal that silos are breaking down. - **Retention and absenteeism data:** Because replacing a frontline employee costs between $4,400 and $15,000, tracking voluntary turnover alongside collaboration investments gives HR a clear return-on-investment signal. For a structured framework on closing information gaps that affect measurement, see [Closing the Information Gap in Performance Reviews](/articles/closing-the-information-gap-in-performance-reviews). ## What Collaboration Tools Work Best for Frontline and Distributed Teams? Not every collaboration tool is built for teams without dedicated desks or company email addresses. The 80% of the global workforce that is deskless, per Emergence Capital, needs mobile-first, no-email-required access as a baseline — not an afterthought. When evaluating employee engagement software and collaboration platforms for frontline or distributed teams, prioritize: - **Mobile-first design:** The platform must be fully functional on a personal smartphone, not a scaled-down version of a desktop tool. - **No corporate email required:** Frontline workers in [healthcare](/industries/healthcare), [grocery](/industries/grocery), and [financial services](/industries/financial) industries routinely lack company email addresses. A platform that requires one excludes the majority of your workforce from day one. - **AI-driven content surfacing:** Rather than a single undifferentiated feed, the platform should surface role- and location-specific updates automatically, which is what drives the daily usage rates that generic intranets fail to achieve. - **Unified notifications:** Employees switching between five or more disconnected systems lose over four hours per week to context-switching. A single unified platform eliminates that drag. For an independent evaluation of how current platforms compare, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides analyst-level detail on what separates high-adoption platforms from low-adoption ones. ## How Does Team Collaboration Connect to Employee Engagement and Retention? Collaboration and employee engagement are not separate initiatives — they are the same initiative measured from different angles. When employees have clear communication channels, access to the right information, and tools that include rather than exclude them, engagement follows naturally. The financial stakes are concrete: replacing a frontline employee costs between $4,400 and $15,000, and disengaged employees are significantly more likely to leave. An employee engagement survey run before and after a collaboration platform rollout will typically show the connection directly. Organizations in sectors with high frontline turnover — such as [ambulatory care](/industries/ambulatory-care) — have used structured collaboration programs to move engagement metrics measurably within the first quarter of deployment. For a broader view of where workforce operations are heading and how collaboration fits into the picture, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) is a practical starting point. --- # How To Successful Utilize Your Workplace Intranet **Author:** Luke Walton **Published:** 2018-04-18 **Category:** intranet Accelerate Your Work Employees often face roadblocks while trying to search for a document within a file, folder, wiki, or a post in our company Intranet. They spend hours trying to find that one piece of missing text that could bring the whole puzzle together. Every time you have a distraction, it can deter your […] # How to Successfully Utilize Your Workplace Intranet A workplace intranet is only as useful as the habits built around it. According to Social Edge Consulting, 91% of organizations operate an intranet — yet nearly a third of employees never log in, and only 13% use one daily. That gap between deployment and adoption is where productivity, engagement, and institutional knowledge quietly disappear. This guide covers the specific behaviors and features that turn a neglected intranet into a daily work hub — from search and project tracking to recognition, content quality, and frontline access. --- ## Why Most Intranets Go Unused (and What to Do About It) Employees spend an average of 2.5 hours per day searching for information, according to IDC. Despite that, SWOOP Analytics reports the average employee spends only six minutes per day actually using intranet tools. The mismatch points to a usability and habit problem, not a technology shortage. Traditional intranets often require months of IT-led customization and deliver static, ungoverned content that becomes stale quickly. Modern platforms can be deployed and branded in days without heavy IT involvement — which means the barrier to a useful intranet is lower than most organizations assume. Employees also lose over four hours per week switching between disconnected systems (per MangoApps vendor positioning). A unified intranet that consolidates tools — files, wikis, calendars, messaging, and project tracking — is a direct productivity intervention, not just a convenience. For a broader view of where intranet platforms are heading, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) benchmarks the current landscape across adoption, features, and employee experience. --- ## 1. Use Search Intentionally to Recover Lost Time The most immediate way to get value from an intranet is to stop hunting through email threads and shared drives. A well-configured intranet search indexes wikis, files, blogs, posts, and connected platforms — so a single query surfaces results across all of them. AI-powered universal search goes further by connecting to external repositories like SharePoint, Google Drive, and Box, returning results from all connected platforms in one place. This is the difference between a search bar and a genuine knowledge retrieval tool. If a first search doesn't return what you need, use filters by content type, author, date, or department before escalating to a colleague. Treating search as a multi-step process — rather than a single attempt — recovers a meaningful share of those 2.5 daily hours IDC attributes to information hunting. --- ## 2. Reduce Unnecessary Meetings with Shared Calendars and Async Updates Meetings are frequently cited as one of the most time-consuming activities in the workplace. A shared intranet calendar lets you check coworker availability before scheduling, reducing the back-and-forth email chains that precede most meetings. More importantly, many status updates, approvals, and announcements that currently require a meeting can be handled through intranet posts, threaded comments, or project trackers. Shifting these to async formats gives employees time to respond thoughtfully and keeps meeting time reserved for decisions that genuinely require real-time discussion. --- ## 3. Track Project Work in One Place Project management features built into an intranet — folders, trackers, blogs, and calendars — keep all project context in one location rather than scattered across email, chat, and separate tools. Practical habits that make this work: - **Organize files in project folders** so every team member finds the current version without asking. - **Use the project calendar** to log milestones, training dates, and meeting times so nothing lives only in someone's personal calendar. - **Set permission levels** for each project member. Admins can grant limited access to specific projects, which matters both for collaboration and for data governance — a point covered in more detail below. - **Invite external collaborators** to specific projects without giving them access to the broader intranet. [Workspaces](/key-features/workspaces) in MangoApps are designed specifically for this kind of structured, permission-controlled project collaboration. --- ## 4. Ask Questions and Share Knowledge Publicly Knowledge that lives only in one person's head is a liability. Asking questions on a shared intranet forum — rather than in a private message — means the answer becomes searchable for the next person with the same question. This is the foundation of a knowledge management habit: every question answered publicly reduces the number of times that question needs to be asked again. Over time, the intranet becomes a living knowledge base rather than a static document repository. For organizations investing in formal learning programs, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers how to embed learning into daily workflows rather than treating it as a separate initiative. --- ## 5. Share Insights Through the Newsfeed — With Discipline An intranet newsfeed is only useful if employees trust that what appears there is worth reading. That requires discipline from everyone who posts. Guidelines that keep a newsfeed valuable: - **Post consistently** so employees know when to expect updates rather than being surprised by irregular bursts. - **Keep posts specific** — vague announcements generate confusion; concrete updates generate action. - **Use polls and questions** to invite participation rather than broadcasting one-way. - **Avoid cluttering the feed** with low-priority content. Every unnecessary post raises the cost of finding important ones. Employee engagement improves when the intranet newsfeed is treated as a curated channel, not a dumping ground. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring internal content strategies to improve readership and response rates. --- ## 6. Recognize Contributions Visibly Recognition is one of the highest-leverage uses of an intranet. A culture that identifies and endorses top contributors publicly — through badges, official recognitions, or peer shoutouts — reinforces the behaviors organizations want to see more of. Visible recognition on a shared platform also signals to the broader team what good work looks like, which has a compounding effect on employee engagement over time. According to [Gallup's 2026 State of the Global Workplace: What It Means for HR, ...](/articles/gallup-2026-state-of-the-global-workplace), employee recognition remains one of the most underleveraged drivers of engagement globally. Recognition delivered through the intranet — rather than in a private email — gives it social weight and makes it part of the organization's visible culture. --- ## 7. Use Idea Management to Turn Suggestions Into Projects Idea management features let employees submit suggestions tied to market trends, internal opportunities, or operational improvements — and let others vote, comment, and build on them. What makes this more than a suggestion box is the ability to set campaign start and end dates, track votes and comments, and convert a winning idea directly into a project with all the associated tools available. The full lifecycle — from suggestion to execution — stays inside the intranet rather than getting lost in email. --- ## 8. Extend Access to Frontline and Deskless Employees Approximately 80% of the global workforce is deskless, according to Emergence Capital. Yet most intranet adoption strategies are designed entirely around desk-based employees with corporate email addresses and laptops. Frontline employees — in retail, healthcare, manufacturing, logistics, and field services — can access a modern intranet from personal mobile devices without a corporate email address, VPN, or desk. This matters both for inclusion and for business outcomes: replacing a single frontline employee costs an estimated $4,400–$15,000, making intranet adoption a retention tool as much as a productivity one. Organizations that have extended mobile-first intranet access to frontline teams report significant engagement gains. One healthcare organization achieved 87% workforce engagement within months of launching a branded intranet app. For organizations managing distributed or frontline workforces, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the operational patterns that separate high-adoption deployments from low ones. --- ## 9. Maintain Security and Governance Habits An intranet that employees trust is one where they know who can see what. Governance habits that protect that trust: - **Set permission levels deliberately** — not every employee needs access to every project, department site, or file. - **Use SSO (single sign-on)** where available to reduce password sprawl and unauthorized access. - **Audit content regularly** — stale, ungoverned content erodes trust in the intranet as a reliable source of truth. - **Assign content owners** to key pages so there is always someone responsible for keeping information current. Admins who treat permissions and governance as ongoing practices — rather than one-time setup tasks — maintain an intranet that employees return to because they trust what they find there. --- ## 10. Keep Face-to-Face Communication for What It Does Best An intranet handles asynchronous information sharing, documentation, and broadcast communication well. It does not replace the relationship-building, nuanced negotiation, and real-time problem-solving that happen in direct conversation. Negative feedback, sensitive personnel matters, and complex interpersonal issues belong in face-to-face or private settings — not in public intranet posts or comment threads. Using the intranet for these interactions tends to escalate rather than resolve them. The practical rule: if a message requires tone, context, or immediate back-and-forth to land correctly, use a direct conversation. If it can be documented, searched, and referenced later, the intranet is the right channel. --- ## What Good Intranet Utilization Actually Looks Like High intranet utilization is not about logging in every day for its own sake. It is about building habits that make the intranet the default place employees go to find information, coordinate work, share knowledge, and stay connected to the organization. The organizations that get the most from their intranets share a few common patterns: 1. **Search before asking** — employees use search as a first step, not a last resort. 2. **Post to inform, not to perform** — content is specific, consistent, and actionable. 3. **Recognize publicly** — contributions are acknowledged where the whole team can see them. 4. **Govern continuously** — permissions and content ownership are maintained, not set and forgotten. 5. **Include everyone** — frontline and deskless employees have mobile access and are treated as full participants. For organizations evaluating or expanding their intranet investment, [MangoApps Included in Leading Research Firm's Intranet Platforms Ev...](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides independent context on how modern platforms are evaluated against these criteria. The [solutions/modern-intranet](/solutions/modern-intranet) page covers how MangoApps structures these capabilities for organizations at different stages of intranet maturity. --- # Everything Your Business Needs to Know About RSS Feeds **Author:** Anjali **Published:** 2017-11-22 **Category:** modules-features What is RSS? RSS is commonly referred to as Really Simple Syndication. It is a format used to publish content that is regularly published in blogs, news headlines, and more. People use RSS feeds to keep up with their favorite blogs, news sites, and more. You can choose the website you want to subscribe to […] ## The intranet content gap most organizations haven't named Per IDC, employees spend 2.5 hours every day searching for information that should be easy to find. Per Social Edge Consulting, nearly a third of employees never log in to the intranet at all — and only 13% use it daily. Ninety-one percent of organizations operate an intranet, per Social Edge Consulting. Almost none have closed the gap between the information stored there and the employees who need it. This is not a volume problem. Most intranets hold more content than employees could reasonably find on a good day. The failure is in delivery: content exists, but it doesn't reach the right person automatically. Employees search manually, come up empty, or stop trying. RSS feeds — Really Simple Syndication — are one of the most underused tools for closing that delivery gap. Not as a standalone subscription reader, but as the content infrastructure layer inside a modern intranet: a mechanism that surfaces relevant updates, announcements, and intelligence to employees automatically, without requiring them to navigate to multiple sources individually. The question isn't whether your organization should use RSS. It's whether your intranet is configured to use it in a way that actually reaches the right people — not just everyone at once. ## What RSS feeds are and why they matter for modern intranets RSS is a standardized format for publishing regularly updated content — blog posts, news headlines, policy updates, announcements — in a machine-readable feed that subscribers can pull into a central location. Rather than navigating to individual sources, users get updates from multiple feeds aggregated in a single view. That sounds like a convenience feature. Inside an intranet, it functions as a content governance tool. Per SWOOP Analytics, employees spend an average of six minutes per day using intranet tools. That number, alongside IDC's 2.5-hour daily search overhead, tells a specific story: intranet failure isn't about content volume — it's about delivery friction. Employees aren't spending only six minutes because they've found what they need; they're spending six minutes because the tool requires too much effort to surface relevant content. RSS addresses that by making content delivery continuous and automatic. A feed widget shows relevant updates, refreshed without manual navigation, without requiring a content team to broadcast identical messages across the entire organization. The key word is "relevant" — and that's where most RSS implementations miss the mark. ## The personalization gap that most RSS deployments miss Only 22% of company intranets currently deliver personalized content to employees, per Akumina's State of the Digital Workplace & Modern Intranet 2024 research. The remaining 78% push the same feed to everyone regardless of role, region, or job function. Consider what that means in practice. A healthcare organization's intranet RSS widget shows the same compliance news, the same HR updates, and the same industry feeds to a bedside nurse, a billing specialist, and a regional operations director. Each person filters mentally for what matters to them — or stops checking the widget at all. The platform hasn't reduced their information burden; it's moved the filtering work from the search bar to each employee's attention. This is the one-size-fits-all failure mode, and it's the default behavior of any RSS setup that hasn't been scoped for specific employee segments. Persona-driven content delivery routes relevant updates, announcements, and resources to employees based on role or location — not because a content team manually curates every post, but because the intranet's feed configuration does it structurally. Per Akumina and Unily product documentation, this is now a baseline expectation for modern intranet content tools, not a premium feature. Organizations that see consistent intranet engagement have made this shift architecturally. For internal communications teams, that means configuring RSS widgets to deliver role-appropriate feed clusters to each employee segment: sales teams see competitive intelligence and industry developments; operations teams see process and compliance updates; HR sees policy and regulatory feeds. The configuration is done once, maintained as needed, and delivers continuously — without requiring broadcast messages or manual segmentation for every post. ## What RSS does inside an intranet — and where it fits in the broader content stack Understanding where RSS belongs in a content strategy requires clarity on what it does well and where other tools are better suited. **Centralizing external intelligence.** Teams tracking competitor moves, regulatory developments, industry news, or sector research share the same underlying need: multiple external sources consolidated in one view, updated automatically. RSS handles this without requiring anyone to visit individual sites. A compliance team tracking three regulatory bodies and two industry publications gets a single, continuously refreshed widget rather than five separate browser bookmarks to check manually. **Distributing internal content.** RSS is not limited to external sources. Internal blogs, department update pages, and announcement channels can publish RSS-compatible feeds. A policy update from the compliance team's internal blog can appear in the same widget as external regulatory news — because both are RSS sources. The distinction between internal and external content becomes invisible to the employee; what they see is a coherent stream of relevant updates. **Moving content management out of IT.** At most organizations, updating a content widget, adding a feed source, or reconfiguring subscriptions requires filing an IT ticket. That bottleneck delays time-sensitive communications by days or weeks. Modern intranet platforms expose no-code RSS configuration to communications teams directly, so adding or removing feed sources is a comms decision, not a development task. Per Akumina and Unily product documentation, leading organizations manage content publishing without IT involvement as standard practice — not as a workaround, but as an intended architectural feature. MangoApps' RSS reader app supports all three functions. Users subscribe to relevant sources, and the platform renders feeds in a full-page or widget view with persona-based routing — so the right content reaches the right employee segment without requiring a broadcast to everyone. ## Reaching the 80% that desktop-only content misses Per Emergence Capital, 80% of the global workforce is deskless — frontline workers in healthcare, retail, manufacturing, logistics, and field services who don't sit at a desktop, don't have a corporate email address by default, and rarely interact with intranet tools designed for knowledge workers. An RSS configuration that only performs well on a desktop is structurally excluding the majority of the workforce. For distributed and deskless employees, mobile access to RSS-delivered content isn't a design preference. It is the difference between staying connected to organizational information and being left out of it entirely. When a frontline retail associate needs to see updated compliance guidance, or a field technician needs the latest safety procedure, that content needs to reach them on the device they carry — not the workstation they don't have. The [MangoApps employee communications solution](/solutions/employee-communications) supports mobile-accessible content delivery, extending RSS feed access to employees who need current information without being tied to a fixed workstation. The practical implication: before deploying RSS widgets broadly, test how they render on mobile devices with frontline employees specifically — not only office-based users in a testing environment. A feed widget that works cleanly on a large monitor may be difficult to navigate on a phone. If it doesn't work for the 80%, it doesn't function as an organizational communication tool at scale. ## RSS best practices for business intranets Deploying RSS feeds effectively requires more than subscribing to a few external sources. The following practices produce consistent value for organizations that rely on their intranet as a primary communications channel: **Segment feeds by role or team.** Configure widgets so sales teams see competitive intelligence and industry news, operations teams see process and compliance feeds, and HR sees regulatory updates — not one undifferentiated broadcast to the entire organization. Only 22% of intranets currently do this, per Akumina's 2024 research. Segmentation is a genuine differentiator rather than a standard baseline at most organizations today. **Blend internal and external sources in a single widget.** The most effective RSS configurations merge external feeds with internal ones. Employees see a complete, coherent picture — regulatory news alongside internal policy updates, industry developments alongside department announcements — without switching contexts or navigating multiple tools. **Audit subscriptions on a quarterly cadence.** Stale feeds create noise that reduces engagement with the widget over time. A subscription to a source that has shifted focus or stopped publishing meaningful content degrades the quality of the feed overall. Review active subscriptions quarterly and remove anything that no longer serves a clear purpose for the segment receiving it. **Hand configuration to communications teams.** Adding a feed source or removing a stale subscription should take minutes, not days. IT ownership of routine RSS management creates delays that make the tool impractical for time-sensitive communications. No-code intranet RSS tools exist specifically to move this responsibility to the people accountable for internal communications. **Test mobile rendering before broad rollout.** With 80% of the global workforce deskless (per Emergence Capital), a content tool that performs poorly on mobile is excluding most employees from the start. Include frontline device testing in any RSS deployment plan before a broad rollout. ## Evaluating intranet RSS and content delivery capabilities For organizations assessing whether their current intranet platform delivers the personalized, mobile-accessible content experience that drives consistent engagement, [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent benchmarking of personalization and content delivery capabilities across leading vendors. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how content delivery strategies — including RSS aggregation and persona-based routing — are shifting to meet the expectations of distributed, mobile-first workforces. For organizations actively evaluating modern platforms to replace legacy intranet tools, [the Frontline Intranet Requirements checklist](/articles/replacing-sharepoint-2016-2019-frontline-intranet-requirements) provides structured evaluation criteria specifically for mobile-first delivery and personalization requirements. The 2.5 hours per day that IDC benchmarks as daily search overhead is not a search problem. It's a delivery problem. RSS feeds configured for who is asking — segmented by role, region, or job function, and accessible on the devices employees actually carry — are part of the architecture that closes that gap. Feeds configured for everyone deliver to no one in particular. And employees who can't find relevant information quickly stop using the intranet at all, which is how a platform that 91% of organizations operate ends up being used daily by only 13% of their workforce. --- # Team Collaboration Software Features Your Company Needs To Have **Author:** Luke Walton **Published:** 2016-07-21 **Category:** team-collaboration Recognizing The Need For Team Collaboration Software Most organizations have recognized the need for an a team collaboration software solution. Picking one that is the right fit for your organization, is a whole other challenge. You have to identify which solution best fits all your organizations’ unique requirements. However, once implemented, the benefit is clear. […] ## Team Collaboration Software Features Your Company Needs To Have ### Recognizing The Need For Team Collaboration Software Most organizations have recognized the need for a team collaboration software solution — but knowing which features to require is what separates a successful deployment from shelfware. The core features your company needs include: **integrations with existing tools, document management, task and project management, security controls, onboarding support, AI-assisted search, and frontline-accessible mobile access**. Per Social Edge Consulting, 91% of organizations already operate an intranet or collaboration platform, yet nearly a third of employees never log in — a gap that traces directly back to missing features and poor fit. This guide walks through each requirement so you can evaluate vendors against your organization's actual needs. --- ### Understanding Your Company's Requirements A team collaboration software tool can increase employee productivity, accelerate processes, and streamline workflow. You need to gauge who can benefit from collaborating on tasks. Is it specific to a department or does it encompass the entire company? Start with understanding the type of content that is shared on this online collaboration platform. How many resources will work on it? What will the content be that is shared on it (video, audio, text)? Meet with the various department heads and understand the current communication gaps and problems. One often-overlooked starting point: employees lose over 4 hours per week switching between disconnected collaboration systems, making platform consolidation a measurable productivity lever — not just a convenience. IDC research puts the downstream cost even higher, finding that employees spend 2.5 hours per day searching for information. These numbers should anchor your requirements conversation before you ever open a vendor demo. --- ### Integrations With Existing Tools One of the main issues in an organization's post-purchase of a team collaboration software tool is the integration and deployment of the software throughout the organization. It is imperative when introducing a new software to the organization for it to work well with the existing apps and software used by employees. This will help increase the adoption of the new team collaboration software. If your company uses Microsoft suite (Word, Excel, PowerPoint, etc.) or Google services like Analytics, Apps & Drive, you should be able to integrate all these apps into your online team collaboration software. You should also be able to integrate with social media platforms: Facebook, Twitter, LinkedIn, and more. For organizations with complex tech stacks, look for platforms that can consolidate a large number of enterprise systems into a single dashboard — TeamHealth, for example, consolidated 200+ enterprise systems into a single mobile dashboard as part of their deployment. --- ### Impactful Onboarding And Training After you select the team collaboration solution that is the best fit for your organization, you need to begin thoroughly training employees on the new software. To ensure that employee-adoption of the new software is achieved, the collaboration software should include documentation, video tutorials, quick start guides, help articles, and more. New hires should also be onboarded with the expectation of completing the trainings. Adoption benchmarks are achievable when onboarding is treated as a feature requirement rather than an afterthought. Large enterprise deployments have reached 90% frontline adoption within the first six months when structured onboarding is built into the rollout plan. For a deeper look at embedding learning into daily workflows, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). --- ### Security For Your Company The online collaboration portal should allow you to securely connect to your teams and projects wherever you are. It should have the ability to enable/disable mobile access per platform, disable access or wipe stored content, and store complete mobile access logs. **A few other security features to look out for:** - Disable and wipe-out data from lost mobile devices. - Two-Factor Authentication (2FA) - Special security protocol and formats for passwords. - The ability to allow or disallow the web, desktop, or mobile from connecting with the network. Security requirements are especially acute for frontline and deskless workers. Per Emergence Capital, 80% of the global workforce is deskless — meaning the majority of your employees may be accessing collaboration tools on personal devices, often without corporate email addresses. Modern platforms eliminate the corporate email requirement for employee login entirely, enabling frontline workers to access collaboration tools on personal devices without IT provisioning. Evaluate whether your shortlisted vendors support this explicitly. --- ### The Cost Of Team Collaboration Software Regardless of your organization's size, cost is always a decisive factor when determining a new software solution. Pricing for team collaboration software typically ranges anywhere from $5 to $25 per user per month. You might also come across some free options (which are not ideal as you do not have full access to all the features). Some vendors tend to do some smart packaging of features and have different plans. If you do your research well, you will notice that the best products have the same features and charge less than others. Some big brands charge a premium, which could be as much as an additional $15 per user. At the same time, you can find the same features and functions with a lesser brand name, sometimes finding a better product and service at a more affordable price. However, per-seat licensing is only part of the total cost of ownership (TCO). Buyers should ask vendors directly about implementation, customization, and data migration costs — basic implementations can start at $15,000 and enterprise deployments can exceed $150,000. These costs rarely appear in the per-user pricing card but are often the largest line item in year one. Replacing a frontline employee costs between $4,400 and $15,000 (per an industry report cited on MangoApps' mobile employee app product page), which means adoption-focused collaboration software is a retention investment, not just a productivity tool — and TCO calculations should reflect that. --- ### Features To Look Out For **Document Management** You should be able to store, organize, share, and collaborate on any document or media file. Securely drag and drop large files into a network drive or a team folder quickly and easily. You should also be able to share file attachments via email. A workflow should have an option to automatically notify you when someone approves, rejects, downloads, uploads, adds comments, or views a document. You should also have the ability to drop files into a folder and quickly share a link with external customers, suppliers, vendors, and partners. **Task Management** Your team collaboration software should have a complete task management system which allows you to check tasks, across multiple projects, on one screen. Due dates, conversations, files, checklists, and time-logs for each task all in one place so you can save time and stay in control. Tasks should also have good workflow — a logical flow that changes state as work progresses. You should be able to re-assign work, add resources, and re-prioritize. Look out for notifications as well for updates on the project tasks that you are responsible for or need to accept or reject. You should also get complete reporting in any file format. **Project Management** One of the most important features of any online collaboration platform is the ability to manage projects. It is also essential that you be able to invite guest users to give customers or partners transparency and visibility during project execution. Many teamwork management tools have added elements to make them even more user-friendly. **AI-Assisted Search and Personalization** AI is now a baseline expectation in enterprise collaboration platforms, not a premium add-on. Evaluate whether the platform offers AI-curated content feeds that surface relevant documents and updates without manual searching, natural-language search that lets employees ask questions in plain language rather than navigating folder structures, and connections to AI engines such as OpenAI or Gemini for in-platform assistance. Per IDC, employees already spend 2.5 hours per day searching for information — AI-assisted search directly attacks that number. SWOOP Analytics found that the average employee spends only six minutes per day using intranet tools, which means the platform must surface the right information immediately or it will be ignored. **Multilingual and Global Access** Enterprise-grade collaboration platforms now support 50+ languages with real-time translation built in — a capability buyers should explicitly evaluate when assessing global or distributed teams. If your workforce spans multiple regions or languages, this should be a required feature, not a nice-to-have. For a current view of how leading platforms stack up across these feature dimensions, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent analyst scoring across vendors. --- ### MangoApps' Team Collaboration Software An effective team collaboration software is an absolute requirement. However, it can prove to be tricky choosing from the large variety of options available. Before investing time, resources, and a budget towards a solution, you have to understand what you want from the portal. MangoApps is a team collaboration software solution that addresses the full feature checklist above — integrations, document and task management, security, AI-assisted search, frontline mobile access, and multilingual support. MangoApps was also [included in a leading research firm's intranet platforms evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) and [recognized with a Gold award in Reworked's 2026 IMPACT Awards](/articles/mangoapps-gold-reworked-2026-impact-awards), providing third-party validation of the platform's capabilities. If you would like to learn more about how MangoApps can assist your organization, contact us or schedule a personalized demo today. --- ### How Do I Evaluate Collaboration Software for Frontline Workers? Frontline and deskless workers — who represent 80% of the global workforce per Emergence Capital — have different access requirements than desk-based employees. When evaluating platforms for frontline use, prioritize: no-email login options, offline content access, mobile-first interface design, and shift management integration. Per Social Edge Consulting, only 13% of employees use an intranet daily, and low frontline adoption is a primary driver of that number. Platforms built around desk-worker assumptions will underserve the majority of your workforce. See how organizations in healthcare and retail have addressed this in the [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study) case study, or explore the [employee communications solution](/solutions/employee-communications) purpose-built for distributed teams. ### What Is an Intranet and How Does It Relate to Collaboration Software? An intranet, by definition, is a private internal network that gives employees access to company information, tools, and communication channels. Modern collaboration platforms have largely absorbed traditional intranet functions — document libraries, company news, org charts, and policy repositories — while adding real-time messaging, task management, and AI-assisted search on top. The result is that the line between "intranet" and "collaboration software" has blurred significantly. When vendors describe a "unified intranet" or a "uniting intranet" platform, they typically mean a single environment that replaces both the legacy intranet and the fragmented collection of point tools (chat, file storage, project management) that grew up alongside it. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how organizations are consolidating these functions in practice. ### How Do I Build a Business Case for Collaboration Software Investment? The strongest business cases combine productivity data with retention impact. IDC's finding that employees spend 2.5 hours per day searching for information translates to roughly 12.5 hours per week per employee in lost productive time. At the same time, replacing a frontline employee costs between $4,400 and $15,000 (per an industry report cited on MangoApps' mobile employee app product page), so platforms that demonstrably improve retention carry a measurable ROI beyond productivity gains. Frame the investment around three levers: time recovered from information search, reduction in tool-switching overhead (over 4 hours per week per employee, per MangoApps product data), and reduced turnover in frontline roles. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides additional benchmarks for building this case internally. --- # How MangoApps Helps Manufacturers and Distributors Collaborate **Author:** Luke Walton **Published:** 2014-09-18 **Category:** industry-insights There are a variety of ways manufacturers or suppliers partner with distributors. From joint customer sales calls to product literature and promotions, these efforts help both the vendors and the distributor increase relationships with existing customers and earn business from new ones. Distributors aren’t really employees or customers, but they are more like your business […] # How MangoApps Helps Manufacturers and Distributors Collaborate Marco manages distribution for a regional industrial equipment brand across fourteen accounts in three states. His job is to move product, represent the manufacturer's line accurately, and bring market intelligence back to the sales team. What he cannot do — and what his manufacturer has never fixed — is get the product information he needs when he needs it. The spec sheet for a new hydraulic unit launched last quarter. Marco found out from a customer who had already seen the press release. Updated pricing took effect on a Monday. He found out the following Thursday, after quoting three jobs at the old rate. When compliance documentation was revised for a regulated product category, he received the update as an email attachment six weeks after the effective date. Marco is not disengaged. He is poorly connected to a manufacturer who built its collaboration infrastructure for employees, not partners — and then wondered why its distributor network kept underperforming. That distinction matters more than most manufacturer-distributor collaboration guides acknowledge. The question worth asking isn't whether manufacturers should communicate better with their distributors. It's whether the tools they use to communicate were ever designed to reach them. ## Why standard collaboration tools fail distributor networks According to IDC, employees spend 2.5 hours per day searching for information. For distributor reps operating outside the manufacturer's IT domain, that number is a floor, not a ceiling — because the information they need often sits behind credentials they were never issued. According to Social Edge Consulting, 91% of organizations operate an intranet. Yet nearly a third of employees never log in, and only 13% use their intranet daily. According to SWOOP Analytics, the average daily time spent in intranet tools is six minutes. These aren't engagement failures. They're access failures: platforms built for desktops, behind corporate firewalls, requiring company email addresses that distributor reps were never given. According to Emergence Capital, 80% of the global workforce is deskless. In manufacturing and distribution, that figure includes the majority of the reps who carry your products to market. When the collaboration infrastructure requires a company-issued email and a VPN connection, it doesn't reach them — and the spec sheet misses, compliance gaps, and inventory mismatches that result are predictable consequences, not management failures. The intranet adoption gap — 91% deployment translating to 13% daily use — is not a training problem. It is an architecture problem, and it shows up in manufacturer-distributor relationships more clearly than almost anywhere else in the enterprise. ## The access barrier at the root of the downstream problems The most common pattern in manufacturer-distributor breakdowns goes like this: the manufacturer believes it has communicated something; the distributor has not received it. That is not a communication failure. It is a design failure. Distributor reps are not employees. They don't have manufacturer-issued email addresses. They don't sit behind a corporate firewall. Many work from personal devices in the field, between customer visits, with intermittent connectivity. The enterprise intranet built for headquarters will not reach them — and every IT provisioning ticket required to create an external account adds delay that causes partners to default to email threads and phone calls instead. The no-email-required access model is the most decisive differentiator in external partner collaboration. It removes the onboarding barrier that stalls most programs before they gain traction: instead of an IT provisioning cycle that takes days or weeks, a distributor rep receives an invitation, opens an app on a personal phone, and is inside the collaboration environment the day they join the network. For manufacturers evaluating whether to extend an existing enterprise platform to partners or deploy a purpose-built tool: enterprise SharePoint deployments run $130,000–$426,000 in year one for 1,000 users, a cost that excludes the ongoing overhead of managing external access configurations securely. For mid-size distribution networks that need partner access without enterprise IT complexity, the total cost of ownership differential is a practical consideration, not a theoretical one. ## What changes when the collaboration environment reaches everyone When manufacturers and distributors share a workspace that a rep can open from a personal iOS or Android device — without a corporate credential, without a VPN — the communication patterns that drive revenue become consistent instead of ad hoc. Product spec changes reach distributor reps the moment they're published, not after a weekly email digest. Promotional assets live in one place rather than scattered across email threads. Compliance updates appear with version history and audit trails that satisfy regulatory requirements without requiring the manufacturer to manually track who received what. MangoApps supports this model through dedicated [workspaces](/key-features/workspaces) for each distributor partner, separate from internal employee spaces, where documentation, pricing, and promotional materials are accessible in real time. The [modern intranet](/solutions/modern-intranet) infrastructure underneath handles version control and access management without requiring distributor reps to have manufacturer-issued credentials. The two-way flow matters as much as the one-way broadcast. When distributor reps can surface product feedback, local market trends, and customer requirements back to the manufacturer's sales team through the same interface, manufacturers gain market intelligence that shapes the next product cycle — instead of receiving it six months later in a quarterly review. ## Mobile and multilingual access in distributed networks For a manufacturer with regional or international distribution networks, the mobile constraint is not a UX preference — it is an access requirement. A rep visiting a job site cannot consult a desktop intranet between appointments. A partner in a non-English-speaking market cannot reliably use a platform that requires a separate localization process to deliver product updates in the right language. MangoApps handles both constraints. The [employee app](/solutions/employee-app) works on personal iOS and Android devices without a corporate email address or VPN connection. Real-time translation across 50+ languages delivers product updates to a distributor rep in their preferred language without requiring a separate workflow from the manufacturer. AI-curated feeds surface the content most relevant to each partner's product lines and territory, rather than presenting every rep with content intended for other regions. For global distribution networks, these capabilities determine whether a collaboration program reaches every partner or only the fraction with the right credentials and the right device access. ## What manufacturers typically see once the access problem is solved Manufacturers who deploy a structured distributor collaboration environment tend to report consistent downstream changes once partners can actually access the system. Faster product launches: distributor reps learn about new products before launch day and can prepare their sales approach, rather than finding out from a customer after the fact. Reduced inventory friction: partners share a real-time view of demand signals instead of relying on lagged updates, reducing the mismatches that inflate inventory levels and extend lead times. Fewer compliance gaps: audit trails confirm that updated SOPs and regulatory documents reached every partner in the network, satisfying requirements in regulated categories without manual tracking. Lower partner churn: partners who feel informed and supported stay engaged. The cost of replacing a distributor relationship follows the same logic as employee turnover, where a single replacement typically runs $4,400 to $15,000. The company portal and department sites features in MangoApps allow manufacturers to structure this information architecture by product line, region, or distributor tier — so each partner sees what is relevant to their business without information overload from content intended for other segments. ## How long does implementation take, and what does adoption look like? Implementation is the question manufacturers typically ask last. It is usually the one that should be asked first. For straightforward use cases — a partner portal, a shared document library, and mobile access without IT provisioning — manufacturers typically reach initial deployment within weeks rather than months. The no-email-required onboarding model is the primary accelerator: distributor reps can be added to the network without waiting for IT provisioning cycles, which is the most common source of delay in traditional rollouts. Adoption follows a different curve than most enterprise intranet deployments. Platforms that report low adoption share a common characteristic: they required credentials most users didn't have or a device access pattern they couldn't complete. Platforms that remove those barriers — that open directly on a personal phone without a corporate login — reach adoption rates that conventional intranets do not. OU Health documented 87% workforce engagement within the first months of launching a mobile-first frontline app, a rate roughly four times the standard intranet adoption benchmark. The adoption gap is a design problem. Tools built for desktop employees with corporate credentials will not be adopted by field reps who have neither. Removing those requirements is not a product feature — it is the prerequisite for the collaboration program to function at all. ## The right infrastructure for manufacturer-distributor collaboration The collaboration problems that show up in manufacturer-distributor relationships — missed launches, compliance gaps, inventory friction, partner churn — are information problems. The right product data, compliance update, or demand signal did not reach the right person at the right time. A collaboration environment designed for external partners, with mobile-first access, no-email-required onboarding, real-time content updates, and multi-language delivery, addresses those problems directly. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides an independent evaluation of intranet platforms across dimensions directly relevant to this decision, including external collaboration, mobile access, and content management. Marco's manufacturer has the product. What it is missing is the infrastructure that connects its partners to it. The spec sheet exists. The pricing update exists. The compliance document exists. The problem is not content — it is delivery, to a user the platform was never designed to reach. --- # 18 Ways To have a Positive Attitude At Work **Author:** Luke Walton **Published:** 2014-03-14 **Category:** company-culture “A pessimist sees the difficulty in every opportunity; an optimist sees the opportunity in every difficulty.” ~Winston Churchill. It is no surprise that a majority of those who enter the workforce, do it with reluctance and hesitation. They subconsciously develop a negative attitude of thinking that can affect their mental health as well as their […] # 18 Ways to Have a Positive Attitude at Work A positive attitude at work is not a personality trait reserved for naturally upbeat people — it is a set of practiced behaviors that anyone can build. This article gives you all 18 actionable ways in plain text, so you can read, save, and apply them without relying on an image or hunting for a more complete answer elsewhere. Before diving in, one structural reality is worth naming: positive workplace culture requires both individual mindset and the right infrastructure. Employees who navigate 6–8 disconnected tools daily experience compounded communication friction that erodes positive workplace culture over time, according to MangoApps' own analysis of fragmented communication challenges. And because 80% of the global workforce is deskless (per Emergence Capital), positivity tips that only reach office staff miss the majority of workers entirely. --- ## The Full List: 18 Ways to Have a Positive Attitude at Work ### 1. Arrive prepared, not just on time Showing up a few minutes early gives you space to settle in, review your priorities, and start the day with intention rather than scrambling. The mental shift from reactive to proactive sets a calmer tone for everything that follows. ### 2. Plan your day with specific, executable tasks Vague to-do lists breed anxiety. Break your work into concrete actions — "draft the project brief" rather than "work on project" — so you can experience the small wins that sustain motivation throughout the day. ### 3. Collaborate openly and share ideas Contributing to a shared goal reinforces your sense of purpose. When you [share thoughts on projects with peers](/solutions/employee-engagement), you also signal trust, which tends to be returned. ### 4. Avoid office politics Gossip and political maneuvering drain energy and erode trust. When you feel pulled into a negative conversation, redirect it toward the work itself or disengage politely. ### 5. Adapt to change rather than resist it Organizations evolve. Treating change as information rather than threat keeps you from spending energy on outcomes you cannot control. ### 6. Celebrate small wins — yours and others' Acknowledging incremental progress, not just final outcomes, sustains momentum. A brief public recognition in a team channel costs nothing and reinforces the behaviors you want to see more of. ### 7. Set clear boundaries between work and personal time Burnout is the enemy of positivity. Protecting recovery time is not laziness — it is the maintenance that makes sustained effort possible. ### 8. Practice active listening in every conversation When colleagues feel genuinely heard, they engage more openly. Active listening — eye contact, paraphrasing, withholding judgment — is one of the fastest ways to build the relational trust that makes a team enjoyable to work in. ### 9. Reframe setbacks as feedback A missed deadline or a rejected proposal is data, not a verdict on your worth. Asking "what can I learn from this?" rather than "what does this say about me?" keeps you solution-oriented. ### 10. Take ownership of your mistakes Blaming circumstances or colleagues when things go wrong poisons team dynamics. Acknowledging your role in a problem — and proposing a fix — builds credibility and models the accountability culture you want around you. ### 11. Invest in your own learning Employees who see a path for growth report higher engagement. Organizations that digitize onboarding and training workflows report up to 50% faster new-hire ramp time, which directly supports early positive attitude formation, according to Beekeeper's onboarding research. Seeking out [learning and development opportunities embedded in daily work](/articles/learning-and-development-strategy-embedded-in-daily-work) keeps you growing rather than stagnating. ### 12. Communicate clearly and directly Ambiguous messages create unnecessary friction. State what you need, what you are offering, and what you expect — then confirm understanding. Clear communication reduces the frustration that accumulates when people feel misread or ignored. ### 13. Reduce information overload deliberately Employees spend an average of 2.5 hours per day searching for information (per IDC). That is time lost to frustration rather than contribution. Organizing your digital workspace — pinning key documents, unsubscribing from irrelevant channels — is a practical act of positivity. ### 14. Extend good faith to colleagues Assume competence and good intent until evidence suggests otherwise. Most workplace friction comes from misread tone in written messages, not actual malice. Defaulting to charitable interpretation prevents unnecessary conflict. ### 15. Bring solutions, not just problems When you raise an issue, pair it with at least one possible path forward. This habit shifts your own thinking from complaint to agency, and it makes you someone others want to collaborate with. ### 16. Protect your physical energy Sleep, movement, and nutrition are not separate from your professional performance — they are inputs to it. Treating your physical state as a professional responsibility is one of the most underrated positivity practices. ### 17. Make sure positive culture reaches every worker, not just desk staff Frontline workers without desk access or company email are disproportionately excluded from culture-building communications, deepening disengagement, according to Beekeeper and MangoApps' frontline product research. If your team includes deskless employees, ensure that recognition, updates, and connection opportunities reach them through mobile-accessible channels — not just email or desktop intranets. Only 13% of employees use an intranet daily, and nearly a third never log in at all (per Social Edge Consulting). ### 18. Love what you do — and if you don't, say so Authentic engagement is not about performing enthusiasm. If your role has drifted away from work that energizes you, that is a conversation worth having with your manager. Honest dialogue about fit and growth is more sustainable than forced positivity. --- ## Why Individual Attitude Is Only Half the Equation The 18 practices above are genuinely useful, but they operate inside a system. When that system is fragmented — disconnected tools, unreachable frontline workers, no shared communication infrastructure — individual effort has a ceiling. The data reflects this. Only 91% of organizations operate an intranet (per Social Edge Consulting), yet the average employee spends just six minutes per day using intranet tools (per SWOOP Analytics). That gap between availability and actual use signals that the tools themselves are not meeting employees where they are. Organizations that close this gap see measurable results. OU Health achieved 87% workforce engagement within months of launching a branded employee app. British Airways recorded a 30-point engagement score increase following a structured employee experience initiative. These outcomes did not come from attitude alone — they came from pairing the right mindset with the right infrastructure. For a broader view of where [employee engagement](/articles/gallup-2026-state-of-the-global-workplace) is heading, the research on global workplace trends is worth reviewing. --- ## Frequently Asked Questions ### How do you measure whether a positive attitude initiative is actually working? The most reliable signals are behavioral, not self-reported. Track meeting participation rates, peer recognition frequency, voluntary contribution to shared projects, and retention in the 90-day post-hire window. Employee engagement surveys and questionnaires can supplement these behavioral signals, but they should not be the only measure. A single survey score can mask wide variation across teams or locations. ### What is the connection between employee engagement training and positive workplace culture? Employee engagement training — whether delivered as formal courses or embedded in daily workflows — gives employees the language and frameworks to recognize and act on the behaviors described in this list. Training on employee engagement is most effective when it is continuous rather than event-based, and when it is accessible to frontline workers, not just managers and office staff. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading organizations are structuring these programs. ### Does the right employee experience platform actually change attitudes, or just measure them? A well-designed employee experience platform does both, but the more important function is enabling the behaviors that produce positive attitudes — easy peer recognition, accessible information, mobile-first communication for deskless workers, and personalized content feeds that make employees feel seen rather than broadcast-to. Measurement without enablement produces data without change. --- ## The Takeaway A positive attitude at work is built through consistent, specific behaviors — the 18 listed above give you a complete, actionable starting point. But sustaining that positivity at scale requires that the organization's communication infrastructure actually reaches every employee, including the 80% of the global workforce that is deskless (per Emergence Capital). Start with one or two practices from this list that feel immediately applicable. Then audit whether your team's tools and communication channels are reinforcing or undermining those efforts. The combination of individual habit and organizational infrastructure is what turns a good intention into a durable culture. --- # 4 Tips To Drive Social Intranet Enterprise Software Adoption **Author:** Luke Walton **Published:** 2013-12-18 **Category:** intranet According to a study done by the Sand Hill Group and Neochange, the most critical factor for software success and return-on-investment is effective user adoption. These groups conducted a survey in 2009 that incorporated the views and opinions of 353 IT buyers and software executives. In that group, over 70% listed user implementation as the […] # 4 Tips To Drive Social Intranet Enterprise Software Adoption According to a study done by the Sand Hill Group and Neochange, the most critical factor for software success and return-on-investment is effective user adoption. Their 2009 survey of 353 IT buyers and software executives found that over 70% listed user implementation as the most important factor for software success. The stakes are real: per Social Edge Consulting, 91% of organizations operate an intranet, yet nearly a third of employees never log in — and only 13% use one daily. Per IDC, employees spend 2.5 hours per day searching for information, a cost that a well-adopted intranet directly reduces. Here are four concrete tips to improve [employee engagement](/solutions/employee-engagement) and drive social intranet adoption across your organization. ## Set Clear Success Expectations Although setting expectations for your new intranet software is always a good idea, many organizations fail to do it effectively. Setting expectations first requires planning. The more time you invest on the front end, the more efficient your roll-out will be. The second component is effective communication. For your employees, the expectations of a new collaboration tool must be clear and understandable. Clear communication lets people know what is expected of them and helps them achieve measurable objectives more successfully. One often-overlooked group: frontline and deskless workers, who represent 80% of the global workforce per Emergence Capital. Most legacy intranet deployments exclude employees without a corporate email address entirely, creating a two-tier communication gap between HQ and the field. Setting expectations must explicitly account for how these employees will access the intranet — typically through a mobile-first app that requires no corporate email — so adoption goals reflect your entire workforce, not just desk-based staff. ## Define and Measure Success Metrics Key metrics to measure an intranet's success should be determined and agreed upon in advance. Once identified, progress for each specific parameter must be measured at pre-specified intervals and corrective actions should be taken if progress goals are not met. A realistic adoption benchmark: large enterprise deployments have achieved 90% frontline adoption within the first six months when mobile access and role-targeted content are prioritized from day one. Separately, organizations that launch a branded mobile intranet app have recorded 87% workforce engagement within a few months of go-live — a concrete target to anchor your planning. Beyond login rates and active-user counts, measuring intranet success should include tool-consolidation metrics. Organizations managing 3–4x more systems than necessary pay a hidden productivity tax that adoption KPIs alone won't capture. Tracking how many legacy tools the intranet replaces — and the time saved — gives a fuller picture of ROI. Per SWOOP Analytics, the average employee spends only six minutes per day in intranet tools, which means even modest consolidation gains compound quickly. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) offers a useful external framework for benchmarking your metrics against industry peers. ## Create Adoption Incentives Simple contests can be a meaningful catalyst in helping end users overcome fear or apathy related to new social intranet software. But incentive programs work best when they are designed with three elements in mind: clear rules, measurable outcomes, and role- or location-targeted delivery so employees see updates relevant to their job rather than a generic feed. **Contest formats that work:** - **Profile completion challenges** — reward the first cohort of employees to complete their intranet profiles with a small prize or public recognition. This drives initial logins and builds the social graph that makes the platform useful. - **Content contribution contests** — ask teams to post a set number of updates, how-to guides, or department news items within a defined window. Measure participation by department and share a leaderboard. - **Search-and-find quizzes** — post a weekly question whose answer lives somewhere in the intranet. Employees who find and submit the correct answer are entered into a drawing. This trains information-seeking behavior directly. - **Peer recognition sprints** — run a two-week window where employees earn points for recognizing colleagues through the platform. Points can be redeemed for gift cards or extra time off. For each contest, define the metric before launch (logins, posts, recognitions sent), set a baseline, and report results publicly. Employees who see the scoreboard are more likely to participate. Pair incentive programs with employee engagement training so managers understand how to coach their teams through the transition rather than leaving adoption to chance. ## Determine Effective Usage Traditionally, the majority of operating investments focused on new features, implementation services, and ongoing technical support. While these areas are all important, they do not enable effective intranet usage. Instead of thinking about your intranet as a technology department project, focus on your platform as a means of fostering communication and forging relationships — and as a consolidation layer that reduces the number of tools employees must juggle. Employees resist intranets partly because they represent one more tool in an already fragmented stack. A [modern intranet](/solutions/modern-intranet) that replaces email threads, shared drives, and standalone messaging apps removes that friction. Fewer systems means higher natural adoption because employees have fewer places to check and fewer passwords to remember. AI-powered personalization accelerates this further: when the platform surfaces role-relevant content automatically — rather than presenting a generic feed — employees find value on their first visit and return without being prompted. For frontline workers specifically, replacing a patchwork of paper bulletins, group texts, and manager-relayed updates with a single mobile app is itself the adoption incentive. The cost of not doing this is measurable: replacing a single frontline employee costs between $4,400 and $15,000 on average, making poor intranet adoption a retention risk, not just a technology problem. --- ## Common Adoption Challenges — and How to Address Them The four tips above set the foundation, but most organizations encounter predictable obstacles after launch. Here are the most common, with direct answers. **What if employees resist using the new platform?** Resistance usually signals one of two things: the platform feels like extra work, or employees don't see content relevant to them. Address the first by consolidating tools so the intranet *replaces* something rather than adding to the stack. Address the second by configuring role- and location-based content targeting from day one. Managers play a critical role here — embedding intranet use into existing workflows (team meetings, shift handoffs, project updates) normalizes the behavior faster than any top-down mandate. Employee engagement training for managers is often the highest-leverage investment in the first 90 days. **What if adoption is slow after the initial launch push?** A common pattern: a strong launch week followed by a sharp drop-off. Per Social Edge Consulting, nearly a third of employees never log in even after an intranet is live — so slow adoption is the norm, not the exception. Counter it with a 90-day activation plan: week one focuses on awareness and first login, weeks two through four on habit formation through contests and manager modeling, and months two and three on measuring and publicly sharing adoption metrics. Celebrating milestones ("500 employees active this month") sustains momentum. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) outlines communication cadences that keep engagement from plateauing after launch. **How do I sustain engagement beyond the first six months?** Sustained engagement requires the intranet to become the authoritative source for information employees actually need — policy updates, shift schedules, benefits changes, leadership announcements. Stale content is the single biggest driver of abandonment. Assign content owners by department, set a quarterly content audit cadence, and use employee engagement surveys and questionnaires to ask employees directly what information they're missing. Platforms that support AI-curated feeds reduce the content-maintenance burden by surfacing relevant existing content rather than requiring constant new publishing. For a deeper look at how learning and development fits into sustained engagement, see [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work). --- ## Case Study: How To Leverage A Social Intranet Barut Hospitality Management, a Turkish organization with 6 resort hotel locations spread across Turkey, was looking for a social intranet that could connect their workforce and streamline communication and collaboration among their employees. In need of a solution to better equip their dispersed hotel employees, Barut Hospitality Management began their search for a social intranet that was user-friendly, could assist their compliance efforts, and could support their Turkish employees. For another example of how a structured intranet deployment drives measurable communication outcomes, see [Enabling Easy Communication at the American College of Radiology](/resources/case-study-american-college-radiology). While these tips are not exhaustive, the combination of clear expectations, defined metrics, well-designed incentives, and a consolidation-first usage strategy gives most organizations a repeatable path to meaningful intranet adoption. Let us know in the comments what has worked for you. --- # A Few Workplace Culture Blogs To Check Out **Author:** Anjali **Published:** 2013-10-21 **Category:** company-culture Workplace culture is hard to define, even though we work in one throughout the day. Any workplace with a good culture has a way of life that involves the right amount of employee enthusiasm combined with a solid work ethic. The first step to building a great culture starts with tackling employee enthusiasm and engagement. […] # Workplace Culture Blogs Worth Reading — and What to Do With What You Learn If you're looking for workplace culture blogs that go beyond motivational quotes and actually help you improve employee engagement, this list covers the most consistently useful ones. Each entry includes a brief description of the blog's focus, its intended audience, and why it's worth your time. You won't need to return to Google to decide which ones fit your situation. Before diving in: engagement is not just a culture problem — it's an operational one. Per Gallup, only about 23% of employees worldwide are engaged at work, and the gap is widest among frontline workers who lack access to the same communication tools as desk-based colleagues (per Beekeeper's frontline workforce research). Keeping up with the best thinking in this space is a start. Turning that thinking into practice requires the right infrastructure. --- ## The Blogs: 7 Workplace Culture Resources Worth Bookmarking ### 1. Chief Happiness Officer Blog (Alexander Kjerulf) Alexander Kjerulf is a speaker, consultant, and author of *Happy Hour is 9 to 5*. His blog focuses on the psychology of happiness at work — specifically, why intrinsic motivation outperforms incentive-based management. His core argument is straightforward: when you create a positive work environment, employees motivate themselves and each other. His client list includes Microsoft, LEGO, IKEA, and Hilton. The blog is best suited for HR leaders and managers who want a philosophical grounding in why culture matters before they tackle the tactical side. ### 2. Workhuman Blog (formerly Globoforce) Workhuman (previously Globoforce) publishes research-backed content on recognition, belonging, and psychological safety. Their posts frequently cite their own survey data and are particularly useful for HR professionals building or refining employee recognition programs. The blog addresses questions like how recognition frequency affects retention and how peer-to-peer acknowledgment differs from top-down praise. If you're designing an employee engagement survey or rethinking your recognition strategy, this is a reliable reference. ### 3. SHRM Blog and HR Today The Society for Human Resource Management publishes practitioner-focused content covering everything from employee engagement training to compliance and workforce planning. Their content is especially useful for HR generalists who need to connect culture initiatives to measurable business outcomes. SHRM's 2024 HR Trends Report is frequently cited across the industry, and their blog posts often link directly to that research. If your team is building employee engagement courses or formal training programs, SHRM's resources provide a credible framework. ### 4. Gallup Workplace Blog Gallup's workplace blog is the most data-dense resource on this list. It draws directly from their ongoing global workforce surveys — including the annual State of the Global Workplace report — and covers employee engagement, manager effectiveness, and organizational culture with statistical rigor. Their employee engagement questionnaires and survey methodology are widely used as industry benchmarks. This blog is essential reading for anyone who wants to understand what the numbers actually say about engagement trends. You can also explore [Gallup's 2026 State of the Global Workplace: What It Means for HR, ...](/articles/gallup-2026-state-of-the-global-workplace) for a current-year breakdown of the key findings. ### 5. Josh Bersin Blog Josh Bersin is an independent HR industry analyst whose blog covers the intersection of HR technology, talent management, and organizational design. His writing is particularly useful for understanding how employee experience platform choices affect engagement outcomes. He frequently covers the fragmentation problem — employees navigating 6–8 disconnected tools daily, which suppresses communication and engagement — and the case for consolidating those tools. His audience is primarily CHROs, HR technology buyers, and senior people leaders. ### 6. Culture Amp Blog Culture Amp's blog is written by their in-house people scientists and covers employee feedback, engagement measurement, and the practical use of engagement data. Posts are grounded in aggregate data from their platform and tend to be specific and actionable. Topics include how to design an effective employee engagement survey, how to interpret engagement scores by department, and how to close the loop with employees after a survey cycle. This is a strong resource for HR teams that are already running engagement programs and want to improve their methodology. ### 7. Beekeeper Blog (Frontline Focus) Beekeeper's blog is one of the few workplace culture resources that addresses frontline and deskless workers directly. This matters because 80% of the global workforce is deskless, per Emergence Capital, yet most culture content is written for office-based employees. Beekeeper covers mobile-first communication, shift worker engagement, and the specific challenges of reaching employees who don't sit at a desk. If your workforce includes retail, hospitality, manufacturing, or logistics employees, this blog addresses a gap that most others ignore. --- ## Why Most Culture Advice Doesn't Reach the People Who Need It Most The blogs above are valuable, but they share a common limitation: most of their content assumes employees have regular access to a desktop computer or a corporate intranet. That assumption excludes the majority of the global workforce. Per Emergence Capital, 80% of the global workforce is deskless. Per Social Edge Consulting, only 13% of employees use an intranet daily, nearly a third never log in at all, and the average daily time spent using intranet tools is just six minutes, according to SWOOP Analytics. Meanwhile, IDC research shows employees spend an average of 2.5 hours per day searching for information — time that compounds into significant productivity loss. Frontline employees — who make up the majority of the global workforce — are disproportionately disengaged because they lack access to the same communication tools as desk workers. This creates a two-tier engagement problem that most culture blogs rarely address directly. The practical implication: reading about engagement best practices is only useful if your organization has the infrastructure to act on them. A culture of recognition doesn't work if shift workers can't receive recognition notifications. Training on employee engagement doesn't translate if your frontline team can't access the training materials from a mobile device. --- ## What Turns Engagement Principles Into Measurable Outcomes Organizations that consolidate communication, recognition, and work management into a single platform see measurably higher adoption than those relying on fragmented point solutions. OU Health, for example, achieved 87% workforce engagement within a few months of launching a branded employee app — a result that reflects what happens when engagement infrastructure matches the workforce's actual access patterns. Engagement scores can increase by 30 percentage points within the first year of deploying a modern employee experience platform, according to enterprise case study data. If your organization is evaluating [employee engagement](/solutions/employee-engagement) tools alongside the culture content you're reading, the most important question to ask is whether the platform works equally well for a corporate employee at a desk and a frontline worker on a mobile device. Most platforms are built for one or the other. The gap between them is where engagement initiatives stall. For a broader look at where HR technology is heading, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the platform consolidation trend in detail, including how organizations are reducing tool fragmentation to improve both adoption and engagement scores. --- ## Frequently Asked Questions ### What's the difference between employee engagement and employee experience? Employee engagement measures how emotionally invested employees are in their work and organization — typically captured through an employee engagement survey or questionnaire. Employee experience is broader: it encompasses every interaction an employee has with the organization, from onboarding through offboarding, including the tools they use, the physical environment, and the culture they work within. Engagement is an outcome; experience is the sum of conditions that produce it. ### How do employee engagement training and courses actually improve engagement scores? Employee engagement training and employee engagement courses work best when they target managers rather than individual contributors. Per Gallup, managers account for 70% of the variance in team engagement scores. Training that helps managers give better feedback, recognize contributions more consistently, and communicate organizational goals clearly tends to produce measurable score improvements. Training that focuses only on employee attitudes without addressing management behavior typically has limited impact. ### How do I know if my organization needs employee engagement software? If your organization runs engagement surveys but struggles to act on the results, or if your communication tools are fragmented across email, chat, intranets, and paper-based processes, employee engagement software can help close the loop between measurement and action. The category is broad — it includes survey platforms, recognition tools, communication apps, and unified employee experience platforms. The right choice depends on whether your primary gap is measurement, communication, recognition, or all three. Per Social Edge Consulting, 91% of organizations already operate an intranet, but low daily usage (13%) suggests the problem is often adoption and accessibility rather than the absence of tools. --- # Five Reasons to Permanently Remove Organizational Silos **Author:** Luke Walton **Published:** 2013-09-24 **Category:** company-culture Organizational silos reside within any organization. These silos can exist within large global corporations or a start-up with 10 employees. No matter the size, they are unfavorable to an organization’s ability to succeed in a rapidly changing world. Organizational silos come in a variety of styles including: Geographical Silos – arises from the collaboration difficulties […] ## The morning Marcus couldn't answer a simple question Marcus manages operations across six distribution facilities. His 200-person workforce runs shifts around the clock — warehouse workers, dock leads, floor supervisors — and most of them have never been issued a company laptop or a corporate email address. Last Tuesday, the compliance team updated the hazardous materials handling procedure. The update needed to reach every facility before the first shift. Marcus had three options: call each facility manager directly, trust a printed memo to be read and initialed before the line started, or send an email that most of his workforce could not receive. He made twelve phone calls. That scenario is not an edge case. Per IDC research, the average employee spends 2.5 hours per day searching for information they need to do their jobs — and that figure reflects workers who have full system access. For frontline workers without corporate credentials, the problem is not inefficient search. It is structural exclusion from the communication that shapes their work. Organizational silos explain why Marcus was on the phone at 6 AM. They explain why, per Social Edge Consulting, 91% of organizations operate an intranet while only 13% of employees use one daily. They explain why, per Emergence Capital, the 80% of the global workforce that is deskless is also the most likely to be uninformed when something critical changes. This article makes the case for removing organizational silos — and explains where to start. ## The five types of organizational silos and how each breaks down Organizational silos are not a single problem. They take five distinct forms, each with its own failure mode: **Geographical silos** form when distance — between offices, remote employees, or field locations — creates communication delays. A procedure change at headquarters takes days to reach a satellite facility, if it arrives at all. **Project silos** develop when work happens in closed groups. Teams complete deliverables without surfacing blockers, dependencies, or lessons learned to adjacent teams. The next team starts from scratch on problems already solved. **Functional silos** emerge when role ownership is unclear across departments. The result is redundant work, inconsistent decisions, and employees who feel invisible to colleagues in other functions. **Technology silos** arise when systems are not shared across the organization. For desk-based employees, this means switching between disconnected tools — workers lose over four hours per week in this churn. For frontline workers, technology silos mean total exclusion: if the platform requires a corporate login or a company device, 80% of the workforce is simply not on the network. **Information silos** persist when knowledge is trapped in email inboxes, restricted shared drives, or the institutional memory of individual employees. Per SWOOP Analytics, the average employee spends only six minutes per day using intranet tools — not because they lack interest in shared knowledge, but because platforms consistently fail to surface what people actually need. Marcus's Tuesday morning was a technology silo and an information silo operating simultaneously. Most organizations address one or the other. That is why the problem keeps returning. ## Five reasons to remove organizational silos **1. Cross-functional collaboration requires a shared infrastructure layer** When departments operate in separate systems with separate communication channels, coordination depends on individual effort — phone calls, direct messages, manual forwarding — rather than a shared layer that distributes information consistently. The right hand does not know what the left hand is doing, not because people are unwilling to share, but because there is no common place to share to. An [employee communications](/solutions/employee-communications) platform built to reach every worker, including those without corporate credentials, is the structural fix. The compliance update that cost Marcus twelve phone calls would have reached 200 workers in minutes through a targeted push notification on a mobile-accessible platform. Multiplied across daily operational communication in a workforce that size, the time recovered is real and compounding. **2. Duplicate work is a direct, calculable cost** Silos produce redundant work, overlapping functions, and inconsistent decisions across teams and departments. Per Social Edge Consulting, nearly a third of employees never log in to their organization's intranet at all. Information shared inside that system is invisible to a significant portion of the workforce — who then solve problems their colleagues already solved, and make decisions that contradict decisions already made elsewhere. The fix is not cultural encouragement to "share more." It is a platform with intelligent content personalization that surfaces relevant knowledge to the people who need it, rather than waiting for them to search through systems most of them rarely open. When employees consistently encounter information relevant to their role, the redundant work disappears — not because people changed their habits, but because the platform changed the default. **3. Knowledge retention degrades faster than organizations recognize** Every departure — voluntary or involuntary — removes institutional knowledge that was never formally captured. When information lives in systems only 13% of employees use daily, per Social Edge Consulting, the effective knowledge base of the organization is far smaller than the official document library suggests. The gap widens every time a long-tenured employee leaves. AI-powered search and intelligent content surfacing change the mechanism: instead of depending on employees to find what exists, the platform pushes relevant information to them based on role, location, and behavior. Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), organizations that actively cultivate employee engagement demonstrate measurably better retention, productivity, and customer outcomes. Making knowledge accessible — the right information reaching the right people — is one of the structural conditions that produces those outcomes, not a secondary benefit. **4. Silo-driven disengagement carries a quantifiable price tag** Disconnection from organizational communication is a reliable early indicator of disengagement: no visibility into company updates, no access to recognition programs, no sense of organizational direction. For frontline workers, that disconnection is often total. They are not on the distribution lists. They have no portal. They find out what changed when a manager happens to mention it. Replacing a single frontline employee costs between $4,400 and $15,000, depending on role and industry. That makes silo-driven disengagement a direct balance-sheet risk, not a culture problem with soft ROI. OU Health achieved 87% workforce engagement within months of deploying a unified mobile application for clinical and administrative staff. That outcome followed an access change, not a cultural initiative. Before the access layer closes — before every employee can reach the platform without a corporate email or VPN — the engagement problem does not have a solution. **5. Fragmented systems multiply a productivity loss that is already quantified** Workers lose over four hours per week switching between disconnected systems. Add the 2.5 hours per day employees spend searching for information they cannot quickly locate, per IDC, and the total daily productivity loss approaches a full working day per employee per week. These are not abstract drag effects. They are time losses that appear in project timelines, decision cycles, and quarterly output. An [employee app](/solutions/employee-app) that consolidates communication, documents, tasks, and recognition into a single place removes that friction at the source. The time recovered is measurable against pre-deployment baselines — not a projection, but a before-and-after delta that can be tracked at the team level. ## How to diagnose which silos are costing you the most Most organizations addressing silos begin with a technology purchase. A more durable approach starts with a diagnostic that surfaces where the actual friction lives before anything is bought or deployed. **Map your current tool landscape.** List every system employees touch in a workday. Count how many require separate logins. Identify where information is created versus where it needs to go, and measure the gap in each direction. Most organizations find the number of systems is three to four times higher than leadership assumes. **Test frontline access directly.** Can every worker in your organization receive a time-sensitive update within one hour, without a corporate email address or VPN? If not, you have a technology silo affecting your largest employee population. This is the highest-priority fix — it is the prerequisite for every other change, because AI personalization and knowledge surfacing only work on a population that can actually reach the platform. **Find where decisions are being delayed by missing information.** Project silos and functional silos usually surface here. When a manager cannot answer a direct report's question without a chain of emails to three other departments, that is a silo costing time every day — and it is fixable with better information architecture, not more meetings. **Measure intranet engagement honestly.** If your platform shows six minutes of daily use — the SWOOP Analytics benchmark — that is not a training failure. It is a relevance and access failure. The platform is not surfacing information people need, in a form they can reach. Six-minute averages persist when the platform was designed for the 20% of workers who have a desk, not the 80% who do not. **Set a 90-day checkpoint.** After consolidating onto a unified platform, track engagement at 30, 60, and 90 days post-launch. The organizations that see measurable progress — including the documented gains in healthcare, retail, and logistics deployments — are the ones running structured checkpoints and adjusting based on them, not the ones that deploy and wait for results to appear. ## What the recovery looks like in practice Breaking organizational silos produces gains in three measurable places, and each one is calculable before the investment is made: Time recovered is a baseline you can set today. At 2.5 hours per day per employee, per IDC, multiplied by headcount and average hourly cost, you have a current productivity loss against which any platform investment can be evaluated. The math is not complicated, and doing it before a purchasing conversation makes the business case concrete rather than aspirational. Turnover reduced is a number with a floor. At $4,400–$15,000 per frontline replacement, each avoidable departure caused by silo-driven disengagement is a line item that can be projected and tracked. The intervention — closing the access gap so frontline workers are not excluded from organizational communication — is a knowable cost with a known return. Engagement gains are documented at scale. For a broader view of how these outcomes compound across industries after platform consolidation, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the patterns organizations report when they move from fragmented infrastructure to a single unified platform. The problem Marcus faces every Tuesday is not inevitable. It is the output of infrastructure designed for desk workers and never extended to the rest of the workforce. When the access layer closes — when every employee, with or without a corporate email address, can receive updates, find documents, and contribute to shared knowledge — the twelve phone calls stop. That is the structural outcome of breaking organizational silos: not a cultural shift that takes years, but a measurable operational change that begins on day one. --- # 5 Must Have Enterprise Social Software Integrations **Author:** Luke Walton **Published:** 2013-06-24 **Category:** integrated-digital-workplace No one wants a new way to work, they want ways to improve the processes they are currently using. One of the best ways to ensure widespread adoption of social software is to utilize that enterprise social software integrations available.  Your enterprise social platform should have the ability to integrate social into your existing business processes. […] # 5 Must-Have Enterprise Social Software Integrations (Plus One You're Probably Missing) Most employees don't want a new way to work — they want the tools they already use to work together. That's the core business case for enterprise social software integrations: connecting your intranet and collaboration platform to the systems your teams depend on daily, so work flows instead of stalls. The stakes are real. Employees spend an average of 2.5 hours per day searching for information (per IDC), and workers lose more than 4 hours per week switching between disconnected systems. Meanwhile, only 13% of employees use their intranet daily, and nearly a third never log in at all (per Social Edge Consulting) — a signal that most intranets fail to integrate deeply enough into actual work to be worth opening. This article covers the five foundational integration categories every enterprise social platform should support, adds a sixth category that most legacy lists ignore, and closes with a prioritization framework so you know where to start. --- ## 1. Document Repository Integration In most enterprises, documents live in multiple places — SharePoint, Google Drive, Box, Dropbox — and information workers waste significant time hunting across all of them. Document repository integration solves this by surfacing files from every connected storage platform through a single search interface. The most useful implementation isn't just linking to external storage; it's **universal search** across all connected repositories. When an employee searches for a policy document or a project brief, results should come back regardless of where the file lives. This directly addresses the 2.5-hours-per-day information retrieval problem cited by IDC. What to look for in a document integration: - Bidirectional sync (not just read-only access) - Version control surfaced within the collaboration layer - Permission inheritance from the source repository - Search indexing across SharePoint, Google Drive, Box, and Dropbox simultaneously A [modern intranet](/solutions/modern-intranet) should make document retrieval a background function, not a daily friction point. --- ## 2. CRM Integration CRM integration connects customer data to the people who need it — support teams, account managers, field reps — without requiring them to leave the collaboration environment. The practical benefit is faster, more informed customer interactions and better peer-to-peer coordination when handling escalations or shared accounts. For frontline and field teams, this matters even more. According to Emergence Capital, 80% of the global workforce is deskless, and those workers often need customer context on a mobile device, not a desktop CRM dashboard. An enterprise social platform that integrates CRM data into a mobile-first experience closes that gap. CRM integration also reduces duplicate data entry and keeps customer records current across teams — a direct reduction in IT overhead and a measurable improvement in data quality. --- ## 3. LDAP / Active Directory and HRIS Integration Directory integration (LDAP or Active Directory) is table stakes: it gives employees single sign-on access to the collaboration platform, eliminates duplicate login credentials, and reduces help desk tickets for password resets. Most enterprises already understand this requirement. What the original conversation around directory integration often misses is **HRIS integration** — and it's more consequential. When your enterprise social platform connects to your HRIS, employee roles, permissions, org chart data, and profiles sync automatically. A new hire's account is provisioned the moment HR creates their record. A departing employee's access is revoked when their status changes. Manual provisioning — and the security gaps it creates — disappears. This goes well beyond password management. HRIS integrations reduce IT overhead, improve compliance posture, and ensure that the right people always have access to the right content without anyone filing a ticket. Modern enterprise platforms integrate with 200+ systems including Microsoft 365, Google Workspace, HRIS platforms, and LMS tools (per MangoApps integrations product page), meaning the integration surface is far broader than most teams realize. For HR teams managing workforce operations, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how HRIS integration fits into a broader digital workplace strategy. --- ## 4. Embedded Application Access (iFrame and Beyond) The original concept here — embedding external web applications directly into the intranet via iFrame — remains valid, but the category has expanded. The goal is **in-flow access**: employees should be able to complete tasks in business-critical applications without navigating away from the collaboration environment. Modern implementations go beyond iFrame embeds to include: - Native app connectors that pass authentication tokens - Widget-based dashboards pulling live data from external systems - Workflow triggers that initiate actions in connected tools from within the intranet The business case is the 4+ hours per week lost to application switching. Every time an employee has to leave the intranet, find a separate tool, log in, complete a task, and return, that's friction that compounds across thousands of employees. Embedded access reduces that switching cost. A well-configured [company portal](/key-features/company-portal) can serve as the single entry point for most of these embedded experiences, reducing the number of bookmarks and browser tabs employees need to manage. --- ## 5. Analytics Integration Analytics integration — whether through Google Analytics, a native analytics layer, or a BI tool — answers a question that most intranet owners struggle with: *Is this actually working?* Six minutes per day is the average time employees spend using intranet tools (per SWOOP Analytics). That number alone should prompt every intranet owner to ask which pages employees visit, how long they stay, and which content drives return visits versus dead ends. Analytics integration surfaces those answers. Practical metrics to track: - Page-level engagement (visits, time on page, scroll depth) - Search queries with no results (a direct signal of content gaps) - Navigation paths (where employees go after landing on the homepage) - Department-level adoption rates With 91% of organizations operating an intranet (per Social Edge Consulting) but only 13% of employees using one daily, analytics data is the diagnostic tool that explains the gap and guides improvement. --- ## 6. AI Engine Integration (The Category Most Lists Skip) AI engine integration is now a first-class requirement for enterprise social platforms, and most legacy integration lists — including the original version of this article — predate it entirely. The practical capability: connecting your intranet and knowledge base to an AI engine (OpenAI, Google Gemini, Anthropic, Azure OpenAI) creates an enterprise AI assistant trained on your company's own content. Employees can ask natural-language questions and get answers drawn from internal documents, policies, and wikis — rather than generic responses from a public model. This directly addresses the information-retrieval problem. Instead of spending 2.5 hours per day searching for information (per IDC), employees ask a question and get a sourced answer in seconds. The integration layer is what makes that possible: the AI engine needs access to connected document repositories, HRIS data, and knowledge bases to return accurate, company-specific results. For organizations evaluating platforms, multi-LLM support — the ability to connect to more than one AI engine — is a meaningful differentiator over point solutions locked to a single provider. --- ## How to Prioritize These Integrations Not every organization needs all six integrations on day one. Here's a practical framework for sequencing based on your situation: ### Start with identity and directory (LDAP/HRIS) If employees can't get in easily, nothing else matters. Single sign-on and automated provisioning are prerequisites for adoption. This is the integration that reduces friction at the front door. ### Add document repository next if information retrieval is the primary complaint If your help desk hears "I can't find the document" more than any other complaint, universal search across connected storage platforms should be the second integration you configure. The IDC figure — 2.5 hours per day lost to search — gives you a concrete ROI calculation: even a 30% reduction in search time across 500 employees is measurable in hours recovered per week. ### Prioritize CRM integration for customer-facing teams If a significant portion of your workforce interacts with customers — support, sales, field service — CRM integration delivers faster ROI than analytics or embedded apps. The cost of replacing a single frontline employee ranges from $4,400 to $15,000; integrations that reduce frustration and improve job effectiveness directly reduce that turnover risk. ### Add embedded application access when tool sprawl is the complaint If employees are toggling between 8–10 applications daily, embedded access reduces switching cost. This is a quality-of-life integration that improves adoption of the intranet itself by making it the place where work happens, not just the place where announcements live. ### Layer in analytics once the platform is live Analytics integration is most useful after you have baseline usage data to compare against. Configure it early, but expect it to become more valuable at the 90-day and 180-day marks when you have enough data to identify patterns. ### Evaluate AI engine integration based on knowledge management maturity If your organization has well-structured internal documentation, AI engine integration can deliver immediate value. If your knowledge base is fragmented or outdated, the AI assistant will surface poor-quality answers — fix the content first, then add the AI layer. For teams building out their knowledge management tools and strategy, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how AI-assisted search fits into a broader communications architecture. --- ## What About Frontline and Deskless Workers? One gap in most integration discussions: the assumption that employees have a corporate email address and a desktop browser. According to Emergence Capital, 80% of the global workforce is deskless — frontline retail workers, healthcare staff, field technicians, warehouse teams. For these employees, integrations must extend to mobile-first environments, often without a corporate email login. This changes the integration requirements in two ways: 1. **Authentication**: LDAP/Active Directory integration needs to support mobile SSO, not just browser-based login. 2. **Document and CRM access**: Files and customer data need to be accessible on a phone, in a low-bandwidth environment, without requiring a VPN. Organizations that design integrations only for desk-based workers leave 80% of their workforce with a worse experience — and a higher likelihood of non-adoption. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how frontline-specific integration requirements differ from traditional office deployments. --- ## The Bottom Line Enterprise social software integrations are not a feature checklist — they are the mechanism by which an intranet becomes part of how work actually gets done rather than a separate destination employees visit occasionally. The six categories covered here — document repository, CRM, LDAP/HRIS, embedded application access, analytics, and AI engine integration — address the most common failure modes: employees can't find information, can't access the right tools, can't authenticate easily, and can't see whether the platform is working. Solving those problems in sequence, using the prioritization framework above, gives organizations the clearest path from a low-adoption intranet to one that employees open because it's genuinely useful. If you're evaluating platforms against these criteria, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent analysis of how major vendors perform across integration depth, mobile access, and AI capabilities. --- # On-Premise vs. SaaS: Understanding Total Cost of Ownership with MangoApps **Author:** Luke Walton **Published:** 2013-04-17 **Category:** comparisons At MangoApps, one of the frequently asked questions by our customers and potential clients revolves around the differences and cost implications of Saas vs. On-Premise intranet solutions. I recently had an opportunity to collaborate with Software Advice and was asked to review their calculator. Rather than interpreting it in my words, I thought it would […] # On-Premise vs. SaaS Intranet: A Total Cost of Ownership Breakdown Choosing between an on-premise and a SaaS intranet comes down to one question most buyers underestimate: what will this actually cost over five to ten years? The upfront license fee is only one line item. When you add implementation, customization, maintenance, governance, and the labor required to keep the system running, the total cost of ownership (TCO) picture looks very different from the vendor's initial quote. This article gives you a concrete, worked example of on-premise versus SaaS TCO for a mid-market organization of 1,000 employees — so you can answer the question without leaving this page. --- ## Why Intranet TCO Is Harder to Calculate Than It Looks According to Social Edge Consulting, 91% of organizations operate an intranet, yet only 13% of employees use one daily, and nearly a third never log in at all. That adoption gap has a direct cost implication: every dollar spent on a platform that employees ignore is a dollar that generates no return. At the same time, IDC research shows employees spend an average of 2.5 hours per day searching for information — a productivity drain that a well-adopted intranet is supposed to solve. If your deployment model makes the platform hard to reach or slow to update, you pay twice: once for the software and once for the lost productivity it was meant to recover. The definition of an intranet has also expanded. A modern intranet is no longer a static document repository; it functions as a [company portal](/key-features/company-portal) that connects communication, content, and workflows in one place. That expanded scope changes the cost model for both deployment options. --- ## On-Premise Intranet: What You Are Actually Paying For On-premise solutions require a perpetual license or a large upfront purchase, plus the infrastructure to run them. For a 1,000-user organization, the cost components typically include: **Year-one costs (on-premise, 1,000 users — illustrative ranges)** | Cost Category | Low Estimate | High Estimate | |---|---|---| | Software license | $50,000 | $120,000 | | Server hardware and infrastructure | $20,000 | $60,000 | | Implementation and customization | $15,000 | $150,000+ | | IT staff time (configuration, launch) | $20,000 | $50,000 | | Training | $5,000 | $20,000 | | **Year-one total** | **$110,000** | **$400,000+** | SharePoint enterprise implementations, for example, can cost between $130,000 and $426,000 in the first year alone for 1,000 users when licensing, customization, and governance costs are combined — making the SaaS TCO crossover point arrive sooner than most buyers expect (per MangoApps analysis citing Awesome Technologies Inc. 2025 cost model). **Ongoing annual costs (years 2–10)** - Software maintenance and support contracts: typically 18–22% of license cost per year - IT staff for patches, upgrades, and security: $30,000–$80,000 per year depending on team size - Periodic re-platforming or major version upgrades: $40,000–$100,000 every three to four years - Additional investment to support mobile or frontline access, which on-premise solutions often do not include natively That last point matters more than it used to. According to Emergence Capital, 80% of the global workforce is deskless. On-premise platforms built for desktop access frequently require a separate mobile layer or point solution to reach frontline workers — a cost that rarely appears in the initial TCO comparison but materially widens the gap over a 10-year horizon. --- ## SaaS Intranet: What You Are Actually Paying For SaaS platforms replace the infrastructure and maintenance burden with a per-user subscription. The cost structure looks simpler, but hidden factors can inflate the 10-year number if you do not account for them upfront. **Year-one costs (SaaS, 1,000 users — illustrative ranges)** | Cost Category | Low Estimate | High Estimate | |---|---|---| | Annual subscription (per-user fee) | $15,000 | $60,000 | | Implementation and onboarding | $5,000 | $30,000 | | Data migration | $3,000 | $20,000 | | Integration middleware (if needed) | $2,000 | $15,000 | | Training | $3,000 | $10,000 | | **Year-one total** | **$28,000** | **$135,000** | **Ongoing annual costs (years 2–10)** - Subscription renewal: same per-user rate, scaling with headcount growth - Integration maintenance: low if the platform has native connectors; higher if middleware is required - Internal admin time: significantly lower than on-premise because the vendor handles infrastructure, security patches, and upgrades Hidden SaaS TCO factors that are rarely surfaced in vendor subscription quotes include integration middleware, data migration, and per-user scaling costs (per MangoApps blog / SharePoint alternatives analysis). Buyers should request a fully loaded quote that includes these line items before comparing against on-premise figures. Traditional intranets typically take months to deploy and strain IT teams with ongoing customization demands, whereas modern SaaS platforms can launch for 1,000+ employees in weeks without IT-led configuration (per Unily product page analysis). That faster time-to-value compresses the payback period and reduces the labor cost embedded in year one. --- ## Five-Year and Ten-Year TCO Comparison: A Worked Example The following scenario uses mid-range estimates for a 1,000-employee organization with moderate customization needs and no major re-platforming event. **Assumptions** - On-premise: $200,000 year-one cost; $70,000 average annual cost years 2–5; one re-platform at year 6 ($60,000); $70,000 average annual cost years 7–10 - SaaS: $60,000 year-one cost; $45,000 average annual cost years 2–10 (includes subscription growth and integration maintenance) | Horizon | On-Premise Cumulative TCO | SaaS Cumulative TCO | |---|---|---| | Year 1 | $200,000 | $60,000 | | Year 3 | $340,000 | $150,000 | | Year 5 | $480,000 | $240,000 | | Year 7 | $670,000 | $330,000 | | Year 10 | $880,000 | $465,000 | Under these mid-range assumptions, SaaS costs less at every horizon. The gap widens after year 6 when the on-premise re-platforming cost hits. Organizations with very large existing infrastructure investments or strict data-residency requirements may see a narrower gap, but the crossover point — where on-premise becomes cheaper than SaaS — does not appear in this scenario within a 10-year window. Note that these are illustrative figures. Your actual numbers will depend on your existing infrastructure, negotiated license rates, IT staffing costs, and the complexity of your integrations. Use this table as a starting framework, then adjust each line item against your own vendor quotes. --- ## What Drives the Biggest Cost Differences in Practice ### IT Labor and Governance Overhead On-premise platforms require dedicated IT resources for every upgrade cycle, security patch, and configuration change. SWOOP Analytics research shows the average employee spends only six minutes per day using intranet tools — meaning the IT labor cost per unit of employee value is high when the platform demands constant maintenance. SaaS platforms shift that burden to the vendor, freeing internal IT for higher-value work. Built-in workflow automation and enterprise analytics — features available in [department sites](/key-features/department-sites) and workspace tools on modern SaaS platforms — reduce the hidden labor costs that inflate on-premise TCO by eliminating manual content governance tasks. ### Frontline and Mobile Access On-premise solutions often require additional investment to support mobile or frontline access. For organizations where a significant share of workers are deskless (80% of the global workforce, per Emergence Capital), this is not a minor line item. A unified SaaS platform that includes mobile access in the base subscription avoids the cost of a separate point solution entirely. ### Deployment Speed and Time-to-Value A SaaS intranet deployment that achieves 90% frontline adoption within the first six months compresses the payback period significantly compared to an on-premise rollout that takes six to twelve months before the platform is stable enough for broad adoption. Faster adoption means the productivity gains from reducing that 2.5-hour daily information search (per IDC) begin accruing sooner. --- ## Frequently Asked Questions About Intranet TCO ### Does SaaS always cost less than on-premise over 10 years? For most mid-market organizations, yes — particularly when IT labor, infrastructure, and re-platforming costs are fully loaded into the on-premise figure. The exception is organizations with very high user counts (10,000+) where per-user SaaS fees accumulate quickly, or organizations that already own the infrastructure and have dedicated IT staff with spare capacity. In those cases, the gap narrows but rarely reverses within a 10-year window under realistic assumptions. ### What hidden costs should I ask vendors to disclose? For on-premise vendors: ask for the annual maintenance contract rate, the expected upgrade cycle and associated professional services cost, and the cost to add mobile or frontline access. For SaaS vendors: ask for the per-user rate at your projected headcount in years three and five, the cost of any integration middleware not included in the base subscription, and the data migration fee if you ever need to switch platforms. ### How does intranet adoption affect TCO? Directly. A platform that only 13% of employees use daily (per Social Edge Consulting) generates a fraction of the productivity return of one with broad adoption. Low adoption means the cost-per-active-user is far higher than the headline per-seat price suggests. Deployment model, mobile access, and content quality all affect adoption — which is why the [modern intranet](/solutions/modern-intranet) design approach prioritizes usability alongside cost efficiency. --- ## The Bottom Line: Which Model Fits Your Organization? For most organizations evaluating a 1,000-user intranet today, SaaS delivers a lower 10-year TCO — often by a factor of two — when all costs are fully loaded. The primary reasons are lower year-one implementation costs, no infrastructure overhead, faster deployment, and included mobile access for frontline workers. On-premise remains a defensible choice for organizations with strict data-residency or regulatory requirements that cannot be met by a SaaS vendor's compliance posture, or for very large organizations that can amortize infrastructure costs across a massive user base. Before committing to either model, build a fully loaded cost model using the line items in the tables above, request itemized quotes from at least two vendors in each category, and factor in your IT team's realistic capacity to support ongoing maintenance. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent vendor comparisons that can help anchor your evaluation against third-party benchmarks. For a deeper look at how MangoApps structures its deployment options — including both cloud and on-premise configurations — the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers the operational considerations that affect long-term platform costs. --- # How To Improve Social Onboarding **Author:** Anjali **Published:** 2013-03-04 **Category:** people-operations Onboarding is not simply about your company gaining another employee. Instead, it is more focused on the person who is joining. While filling out HR forms and reading training manuals is important, it is not an accurate definition of onboarding. Onboarding is the process of helping new employees acquire the knowledge and skills to become […] # How to Improve Social Onboarding for New Employees Social onboarding is the practice of connecting new hires to colleagues, culture, and role-relevant knowledge through a structured digital network — before and after their first day. Done well, it shortens time-to-productivity, reduces early voluntary turnover, and gives new employees a clearer sense of where they fit. Done poorly — or skipped entirely — it leaves new hires isolated, anxious, and more likely to leave within 90 days. This article explains what social onboarding involves, why a standard intranet often falls short, and what a structured approach looks like in practice. --- ## What Social Onboarding Actually Means Onboarding is not simply the process of completing HR paperwork. It is the process of helping new employees acquire the knowledge, relationships, and context they need to become effective members of the organization. A significant part of that process is relational: new hires need to know who to go to, who knows what, and how informal networks inside the company actually work. Social onboarding addresses that relational layer directly. Rather than handing a new hire an org chart and a training manual, a social onboarding approach gives them access to detailed employee profiles, team spaces, and peer connections from day one — ideally before their first day. New hire time-to-productivity is measurably shorter when onboarding includes structured peer-network access and role-based social profiles from day one, not just HR paperwork completion. Newcomers who build early relationships with coworkers tend to be higher performers and report greater job satisfaction over time. --- ## Why Most Intranets Fail at Social Onboarding According to Social Edge Consulting, 91% of organizations operate an intranet — but only 13% of employees use it daily, and nearly a third never log in at all. SWOOP Analytics puts the average daily time spent using intranet tools at just six minutes per day. These numbers reflect a structural problem: most intranets are built around document storage and top-down communication, not relationship-building or personalized onboarding journeys. The result is that new hires are handed login credentials to a system that existing employees barely use. That is not a social onboarding experience — it is a filing cabinet with a search bar. IDC research finds that employees spend an average of 2.5 hours per day searching for information. For a new hire who does not yet know where anything lives or who to ask, that figure is almost certainly higher. A social onboarding platform that surfaces the right people, resources, and team spaces based on a new hire's role and location addresses this directly — rather than leaving discovery to chance. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers how leading HR teams are rethinking onboarding as part of a broader employee experience strategy. --- ## The Access Problem for Frontline and Deskless New Hires According to Emergence Capital, approximately 80% of the global workforce is deskless — working in retail, healthcare, manufacturing, logistics, and similar environments where a corporate laptop and email address are not standard issue. Yet most social onboarding tools are built around corporate email login, which creates an immediate access barrier for the workers who arguably need structured onboarding the most. Organizations that fail to provide a structured digital onboarding path see higher 90-day voluntary turnover, with replacement costs ranging from $4,400 to $15,000 per frontline employee. Social onboarding platforms that work without a corporate email address remove a common access barrier for frontline and deskless new hires who never receive a company login — making it possible to reach the full workforce from day one, not just desk-based employees. A [searchable employee directory](/key-features/employee-directory) that works on mobile, without requiring a corporate email, is one of the most direct ways to give frontline new hires a social starting point. --- ## What a Structured Social Onboarding Approach Looks Like Effective social onboarding has a few consistent components: **1. Role-based social profiles available before day one** New hires should be able to browse the profiles of their future teammates — their expertise, current projects, and communication preferences — before they walk in the door. This reduces first-day anxiety and gives new employees a basis for starting real conversations rather than generic introductions. **2. Peer connections built into the onboarding workflow** Rather than leaving relationship-building to chance, structured social onboarding assigns peer mentors, buddy pairings, or cohort groups through the platform. These connections are tracked, not just suggested. **3. Mobile-first access with no email requirement** For frontline new hires, the onboarding experience needs to work on a personal smartphone from the moment an offer is accepted. Waiting until a corporate device or email account is provisioned means losing the first week of relationship-building entirely. **4. Personalized content and connection surfacing** AI-assisted profile matching and role-based resource delivery mean new hires see the people and information most relevant to their specific job — not a generic company-wide feed. This is an area where modern [employee engagement software](/solutions/employee-app) has moved well ahead of traditional intranet tools. **5. Gamification and progress tracking** Employee gamification elements — completing a profile, connecting with five teammates, finishing a training module — give new hires clear milestones and make the onboarding process feel less like a checklist and more like a guided experience. Organizations that execute this well report meaningful results. Benchmarks from social onboarding rollouts at scale show 87% workforce engagement achieved within months of launching a branded employee app, and 90% frontline adoption within the first six months. --- ## Does Social Onboarding Replace In-Person Orientation? No. Social onboarding is not a substitute for face-to-face time — it is a complement to it. When new hires arrive on their first day already familiar with their teammates' names, roles, and areas of expertise, the time HR and team managers spend on orientation can be more focused and tailored to individual needs rather than covering basics that a social platform already handled. This is particularly valuable for organizations with dispersed office locations or hybrid teams, where not every new hire will be in the same room as their manager or closest collaborators on day one. For a broader look at how learning fits into the employee experience after onboarding, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers the structural reasons most L&D programs lose momentum after the first 90 days. --- ## What Happens When Organizations Skip Social Onboarding? When companies do not provide a structured social platform, employees often create informal workarounds — Facebook groups, WhatsApp threads, personal Slack workspaces. These fill the social gap but create information security risks, fragment institutional knowledge, and exclude employees who are not part of the informal network. More concretely, the absence of structured social onboarding correlates with higher early turnover. Replacement costs for frontline roles range from $4,400 to $15,000 per employee — a figure that makes the investment in a structured onboarding platform straightforward to justify. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) includes data on how communication gaps during onboarding contribute to disengagement in the first year. --- ## Getting Started with Social Onboarding If your organization is evaluating how to improve social onboarding, the practical starting point is an audit of what new hires can actually access in their first week: - Can they find and connect with teammates before their first day? - Does the platform work on mobile without a corporate email address? - Are onboarding resources personalized to their role and location, or generic? - Is there a structured peer-connection workflow, or is relationship-building left to chance? - Can HR track onboarding progress and engagement, not just form completion? Answering these questions honestly will surface the specific gaps a social onboarding platform needs to fill. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides additional context on how workforce operations leaders are approaching structured onboarding as part of a broader employee experience investment. For organizations ready to move from audit to action, MangoApps provides an [employee app](/solutions/employee-app) built for both desk-based and frontline workforces — with mobile-first access, no corporate email required, role-based profile surfacing, and the employee engagement tools new hires need to connect and contribute from day one. --- # Employee Social Networks And Performance Management Systems **Author:** Anjali **Published:** 2013-02-21 **Category:** enterprise-social-networking Companies today are moving from systems of transactions to systems of engagement. More and more companies are adopting employee social networks and adapting it to their needs. While this adaptation is paramount in leading to increased communication, collaboration and teamwork, they also have a significant impact on performance management. What Is Performance Management The goal […] # How Employee Social Networks Strengthen Performance Management Systems Performance management fails most organizations not because managers lack effort, but because the systems they rely on are disconnected from how work actually happens. Annual reviews capture a snapshot; social networks capture the full picture. When an employee social network is integrated with a performance management system, organizations gain continuous visibility into goals, feedback, and collaboration — replacing the once-a-year ritual with an ongoing conversation. This article explains how employee social networks address the structural weaknesses in traditional performance management, why frontline and deskless workers are most affected by those gaps, and what a unified approach looks like in practice. ## What Performance Management Is Supposed to Do A complete performance management system covers five interconnected components: - **Performance Planning** — setting individual and team goals that connect to organizational objectives - **Ongoing Performance Communication** — regular check-ins, feedback, and coaching between managers and employees - **Data Gathering, Observation, and Documentation** — capturing evidence of performance throughout the year, not just at review time - **Performance Appraisal Meetings** — structured conversations grounded in documented evidence - **Performance Diagnosis and Coaching** — identifying development needs and acting on them in real time When all five components work together, the system improves productivity, employee engagement, product quality, innovation, and financial outcomes. In practice, most organizations collapse the entire system into the appraisal meeting and ignore the other four. ## Three Structural Problems That Break Traditional Performance Management ### 1. The Appraisal Is Mistaken for the System Performance appraisal is one step in a five-step process, not a synonym for performance management. When organizations treat the annual review as the whole system, they skip planning, skip ongoing communication, and skip real-time coaching. Employees arrive at review meetings without clarity on how their goals connect to organizational priorities — and managers arrive without enough documented evidence to give meaningful feedback. Employees navigating 6–8 disconnected tools daily creates communication fragmentation that undermines continuous performance feedback loops (per MangoApps product research on fragmented communication). A social network that surfaces goals, recognitions, and project updates in a single feed directly addresses this fragmentation. ### 2. Performance Management Is Treated as an Annual Event Most employees do not think about their performance goals between review cycles. They are rarely clear on their objectives for the current year, let alone how those objectives connect to team or company strategy. This is partly a culture problem, but it is also a tool problem: traditional performance management software is designed for annual input, not daily use. For context, only 13% of employees use an intranet daily, and nearly a third never log in at all (per Social Edge Consulting). When the tools meant to support ongoing communication sit unused, continuous performance management becomes impossible regardless of policy intent. Social goal-tracking changes this dynamic. When managers and employees can create, publish, and track goals inside the same platform they use for daily communication, goal visibility becomes a natural byproduct of normal work — not an extra administrative step. ### 3. Individual Data Misses Team and Influence Dynamics Traditional performance reviews measure what an individual completed. They rarely capture how that individual influenced others, unblocked teammates, or contributed to cross-functional outcomes. Most organizational bottlenecks are inter-team problems, not individual failures — yet individual-only data makes them invisible. A social graph built into an employee experience platform gives managers a richer signal. Who is helping whom? Where are requests going unanswered? Which teams are collaborating effectively and which are siloed? This kind of relational data is what separates a performance conversation grounded in evidence from one grounded in recency bias. ## The Frontline Visibility Gap Approximately 80% of the global workforce is deskless (per Emergence Capital), yet traditional performance management systems are designed for employees with a company email address and a desktop computer. Frontline workers in retail, hospitality, healthcare, and logistics are systematically excluded from performance conversations, goal-setting tools, and recognition programs — not because they perform differently, but because the tools were never built for them. This creates a visibility gap that affects the majority of the workforce. Managers cannot coach employees they cannot reach. Employees cannot engage with goals they cannot see. Mobile-first social networks close this gap by giving frontline workers access to the same performance conversations, recognition feeds, and goal-tracking tools available to desk-based employees. For organizations in [retail](/industries/retail) or similar frontline-heavy industries, this is not a feature enhancement — it is the difference between having a performance management system and having one that works for the people who actually deliver the customer experience. ## How Social Networks Repair Each Broken Component **Continuous feedback replaces the annual snapshot.** Instant feedback and real-time recognition allow for continual coaching and mentoring opportunities within the organization, turning performance communication from a scheduled event into a daily habit. Managers can acknowledge contributions in the moment; peers can recognize collaboration publicly; employees receive signals about their performance throughout the year rather than once. **Social goals create shared accountability.** When goals are visible to the team — not locked inside an HR system only managers can access — employees understand how their work connects to broader objectives. Shared visibility also creates natural accountability: progress is observable, blockers surface earlier, and coaching conversations happen before problems compound. **HRIS integration eliminates stale data.** Continuous [performance management](/solutions/performance-management) platforms that integrate with HRIS automatically sync employee roles and goals, eliminating the manual data-entry burden that makes annual reviews stale (per MangoApps integrations product research). When role changes, promotions, and team reassignments flow automatically into the performance system, managers work from current information rather than outdated org charts. **A unified platform replaces fragmented point solutions.** Employees spending 2.5 hours per day searching for information (per IDC) are not failing to be productive — they are navigating a fragmented tool landscape that was never designed to support continuous performance conversations. Consolidating social networking, goal-tracking, recognition, and communication into a single employee experience platform removes that friction. ## What Results Look Like in Practice Organizations that have replaced legacy performance and communication platforms with unified social networks have reported a 30-point increase in employee engagement scores and 90% frontline adoption within the first six months of deployment. These outcomes are not guaranteed, but they reflect what becomes possible when performance management is embedded in the tools employees actually use every day rather than isolated in a system they visit once a year. For a detailed look at how a large organization achieved this kind of adoption, the [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study) case study walks through the implementation and outcomes in concrete terms. ## Frequently Asked Questions ### How does an employee social network differ from an employee engagement survey? Employee engagement surveys and employee engagement questionnaires measure sentiment at a point in time — typically once or twice a year. An employee social network generates continuous behavioral signals: who is participating, who is recognizing others, where communication is breaking down, and how goal progress is tracking. Surveys tell you how employees felt last quarter; social networks show you what is happening today. The two approaches are complementary, not competing. ### What role does training play in employee engagement on these platforms? Employee engagement training and training on employee engagement are most effective when they are embedded in the daily workflow rather than delivered as standalone courses. When learning content, goal-setting, and performance feedback live in the same platform, employees encounter development opportunities in context — while working on a project, after receiving feedback, or when a skill gap surfaces naturally. For more on this approach, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) covers the evidence for embedded learning in detail. ### How do organizations measure whether the social network is improving performance outcomes? Key indicators include: goal completion rates tracked within the platform, frequency of manager-to-employee and peer-to-peer recognition, reduction in time-to-feedback after a project milestone, and changes in employee engagement scores over successive survey cycles. Platforms that surface these metrics in a dashboard give HR and managers the data they need to coach continuously rather than correct annually. ## The Takeaway Employee social networks do not replace performance management — they make it work the way it was always supposed to. By embedding goal-setting, feedback, recognition, and communication into a single platform that reaches every employee including frontline and deskless workers, organizations can move from an annual appraisal ritual to a continuous performance conversation. The structural problems are well-documented: tools go unused (only 13% of employees use an intranet daily, per Social Edge Consulting), frontline workers are excluded from the systems that shape their careers, and fragmented tools prevent the ongoing communication that performance management requires. A unified employee social network addresses all three. If your organization is evaluating options, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the platform capabilities HR leaders are prioritizing this year, including continuous feedback, frontline access, and HRIS integration — the same capabilities this article describes. --- # How To Measure The Success Of Your Team Collaboration Tools **Author:** Luke Walton **Published:** 2013-02-04 **Category:** team-collaboration The most important part of a successful intranet deployment is, of course, having the tools in place to measure success. We can’t base success on subjective feelings like, “Is it working?” or “Do we feel better connected?”. To measure the success of your team collaboration tools, you need to put hard and fast numbers on […] # How to Measure the Success of Your Team Collaboration Tools Measuring whether your intranet and team collaboration tools are actually working requires concrete numbers, not gut feelings. This article walks through the specific metrics that tell you whether your platform is delivering value — and what to do when the numbers fall short. The short answer: track daily active users, contribution rates, inter-group connectivity, information-retrieval time, and system consolidation savings. Each metric maps to a real business outcome, and together they give you a defensible ROI story. --- ## Why Most Intranet Measurement Falls Short According to Social Edge Consulting, 91% of organizations operate an intranet — yet only 13% of employees use one daily, and nearly a third never log in at all. That gap between deployment and actual use is where most measurement programs break down: teams track *whether* the platform exists, not *whether* it is being used. Two structural problems make this worse: - **Frontline exclusion skews the numbers.** Employees without a corporate email address or a desk are often excluded from adoption metrics entirely unless the platform supports no-email login. If your active-user count only reflects desk workers, you are measuring a fraction of your workforce and your ROI figures will be artificially low. - **Tool sprawl fragments activity.** When employees switch between three or four redundant systems, engagement signals are scattered across platforms rather than concentrated in one measurable hub. The result is that no single tool looks well-adopted, even when total collaboration activity is healthy. According to Emergence Capital, 80% of the global workforce is deskless. Any measurement framework that ignores this population is measuring the wrong thing. --- ## Metric 1: Daily Active Users Daily active users (DAU) is the most direct signal of whether your intranet has become part of how people work — or whether it is an occasional destination. A useful benchmark: SWOOP Analytics found that the average employee spends just six minutes per day using intranet tools. If your platform is delivering real value, you should see that number climb as adoption matures. If it stays flat or declines after the initial launch, the platform is not integrated into daily workflows. To move this metric: - Ensure the platform supports login without a corporate email so frontline workers are counted. - Use role- and location-based push notifications to surface content employees actually need, rather than relying on them to seek it out. - Tie daily check-ins to operational tasks — shift schedules, project updates, policy changes — so logging in has a clear work purpose. Platforms that support [department sites](/key-features/department-sites) and personalized feeds tend to see higher sustained DAU because employees find relevant content without extra effort. --- ## Metric 2: Contributions Per Employee Passive consumption is not the same as engagement. Tracking how many employees post, comment, share files, or update wikis tells you whether the platform is building organizational knowledge or just broadcasting it. IDC research found that employees spend an average of 2.5 hours per day searching for information. A well-used intranet reduces that number by centralizing knowledge and making contributions easy to find. When employees contribute consistently, the platform becomes a self-reinforcing knowledge base — each addition makes the next search faster. Measure: - Posts and comments per active user per week - Wiki and document edits per month - Idea submissions and project updates - Group instant message participation Low contribution rates often signal that participation feels effortful or that employees do not see the value of adding to a shared resource. Simplifying the contribution interface and recognizing active contributors publicly are two levers that consistently move this metric. --- ## Metric 3: Most Active Users and Participation Distribution Every platform has champions, regular participants, and passive consumers. All three groups matter, but for different reasons. - **Champions** validate the platform's value and model behavior for others. Track them to identify potential internal advocates. - **Regular participants** are the core of your knowledge base. Their consistency is what makes the platform reliable. - **Passive consumers** still benefit from the platform — they read, search, and apply information even if they rarely post. Do not mistake low contribution rates for zero value. The distribution of participation also tells you whether adoption is concentrated in one department or genuinely cross-functional. A healthy intranet shows activity across teams, not just in the groups that were most enthusiastic at launch. --- ## Metric 4: Inter-Group Connectivity One of the clearest signs that a collaboration platform is working is when knowledge flows across departmental boundaries rather than staying siloed within them. Open groups, cross-functional project spaces, and shared wikis all create pathways for this kind of connectivity. Measure the percentage of employees who participate in at least one group outside their primary department. If that number is low, your intranet may be replicating the silos it was meant to break down. [Workspaces](/key-features/workspaces) that are open by default — rather than requiring an invitation — lower the barrier for cross-functional participation and tend to produce higher inter-group connectivity scores over time. --- ## Metric 5: Information Retrieval Time One of the most CFO-friendly metrics you can track is how long employees spend searching for information before and after intranet deployment. IDC's figure of 2.5 hours per day is a useful baseline. Even a 30-minute daily reduction per employee translates to significant recovered productivity at scale. To measure this, run a brief employee engagement survey before launch and again at 90 days and 12 months. Ask employees how long they typically spend searching for a specific type of information — a policy document, a project file, a colleague's contact. The delta is your productivity ROI. --- ## Metric 6: System Consolidation Savings This is the measurement dimension most organizations overlook, and it is one of the most concrete signals available to finance teams. If your intranet deployment retires redundant point-solution subscriptions — separate tools for messaging, file storage, wikis, task management, and announcements — the cost savings are directly measurable. Track: - Number of software subscriptions cancelled after deployment - Per-seat licensing costs eliminated - IT support hours reduced This consolidation ROI is a credible, auditable number that complements the engagement metrics above and makes the business case for continued investment. --- ## What Good Adoption Actually Looks Like To calibrate your targets, consider what large-scale deployments have achieved. One enterprise deployment cited 90% frontline adoption within the first six months. A branded mobile intranet rollout at OU Health achieved 87% workforce engagement within a few months of launch. These numbers are not universal guarantees, but they establish what is achievable when the platform is accessible to the full workforce — including frontline and no-email employees — and when content is personalized to be relevant. For context on the financial stakes: replacing a single frontline employee costs between $4,400 and $15,000 on average. Low intranet adoption that contributes to disengagement and turnover is not a soft problem — it has a hard dollar cost. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are setting adoption benchmarks and tying them to business outcomes. --- ## How to Build Your Measurement Dashboard A practical measurement dashboard for team collaboration tools should include: 1. **DAU and WAU** (daily and weekly active users) — segmented by department and role, including frontline workers 2. **Contribution rate** — posts, edits, and comments per active user per week 3. **Participation distribution** — percentage of employees active in cross-functional groups 4. **Information retrieval time** — tracked via periodic employee engagement questionnaires 5. **System consolidation savings** — subscriptions retired and licensing costs eliminated 6. **Retention correlation** — compare engagement scores with turnover data quarterly Review these metrics at 30, 90, and 180 days post-launch. The 30-day read tells you about initial adoption; the 90-day read tells you whether behavior is sticking; the 180-day read tells you whether the platform has become infrastructure. --- ## Frequently Asked Questions ### What is a realistic daily active user rate for an intranet? Social Edge Consulting data puts average daily intranet usage at 13% of employees. Platforms that integrate operational workflows — shift schedules, task assignments, policy acknowledgments — consistently outperform this baseline because employees have a functional reason to log in, not just a social one. Targeting 40–60% DAU within six months is achievable for organizations that tie the platform to daily work tasks and support frontline access. ### How do I measure intranet ROI for a CFO? The most credible ROI signals for finance audiences are: (1) system consolidation savings from retired software subscriptions, (2) productivity recovery from reduced information search time, and (3) turnover cost avoidance linked to improved employee engagement scores. Each of these is quantifiable with data you likely already have. The [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) includes benchmarking data that can help you contextualize your numbers against industry peers. ### What should I do if adoption metrics are low after 90 days? Low 90-day adoption usually points to one of three causes: the platform does not support the devices and login methods your workforce actually uses (especially frontline workers); content is not personalized enough to feel relevant; or the platform is competing with too many other tools for the same workflows. Audit which employee segments are *not* logging in, check whether no-email and mobile access are enabled, and identify which redundant tools are still active. Addressing tool sprawl and frontline access together typically produces the fastest lift in engagement scores. The [solutions for employee engagement](/solutions/employee-engagement) page outlines specific features designed to address each of these gaps. --- ## The Bottom Line Measuring the success of your team collaboration tools means tracking six concrete metrics: daily active users (segmented to include frontline workers), contributions per employee, participation distribution across groups, information retrieval time, system consolidation savings, and retention correlation. Each metric has a clear business interpretation and a clear lever you can pull when the number is low. The industry baseline — 13% daily usage, nearly a third of employees never logging in — is not a ceiling. It is a starting point that reflects platforms that were not built for the full workforce. Organizations that extend access to frontline and no-email employees, consolidate redundant tools, and personalize content to role and location consistently outperform that baseline. If you want to see how these metrics apply to your specific workforce, the [company portal features](/key-features/company-portal) page shows how reporting and analytics are structured to surface the numbers described in this article. --- # Why Culture Is the Key To Outstanding Talent Management **Author:** Anjali **Published:** 2013-01-24 **Category:** company-culture Talent Management True talent management is about more than finding the right people. It’s also about making smart decisions that benefit both the workforce and the organization. The goal of talent management is to create a high-performance, sustainable organization that meets its operational goals. You can utilize a modern intranet solution to create culture and channel […] # Why Culture Is the Key To Outstanding Talent Management Talent management frameworks tell you what to do: hire well, develop continuously, review fairly, retain intentionally. What they rarely explain is why organizations that follow this playbook still lose their best people. The gap is almost never in the process design. It is in the culture those processes land in — and specifically, whether that culture actually reaches the full workforce executing them. The central problem is structural. Per Emergence Capital research, approximately 80% of the global workforce is deskless — frontline workers in healthcare, manufacturing, retail, logistics, and hospitality who rarely or never sit at a company-issued computer. Most talent management infrastructure was designed for the other 20%. The performance review tools, the recognition programs, the knowledge-sharing platforms, the onboarding flows — they assume access to a corporate email address and a browser-based intranet. For the majority of employees, those assumptions are false. Culture that only reaches desk workers is not organizational culture. It is headquarters culture. And talent management strategies built on a headquarters culture consistently underperform their own projections — not because the strategy is wrong, but because it is reaching less than a fifth of the people it was meant to develop and retain. ## The infrastructure failure enabling cultural exclusion Consider the actual usage numbers behind the intranet systems most organizations rely on to carry their culture. Per Social Edge Consulting, 91% of organizations operate an intranet, yet only 13% of employees use it daily, and nearly a third never log in at all. Per SWOOP Analytics, the average employee spends just six minutes per day with intranet tools. These numbers describe a delivery failure with direct cultural consequences: the collaborative behaviors organizations invest in — recognition, knowledge-sharing, transparent leadership communication — cannot happen at scale when the platform meant to enable them sits unused. Per IDC research, employees already spend 2.5 hours per day searching for information they need to do their jobs. For deskless workers who cannot access the intranet at all, that search either fails entirely or defaults to informal channels — a manager's verbal instructions, a printed bulletin board, a message from a colleague who may or may not have the current version of the policy. This is not a peripheral inconvenience. It is a direct impediment to the collaborative culture that talent management depends on. The retention consequence is measurable. Frontline employee replacement costs range from $4,400 to $15,000 per worker depending on role and industry. Organizations that cannot reach these employees with consistent cultural signals — recognition, development opportunities, transparent communication — pay this cost repeatedly, often attributing attrition to compensation or scheduling rather than to the access failure driving disengagement. Traditional intranets compound the problem by delivering static, ungoverned content that becomes stale. When the platform is hard to access and the content it serves is outdated, employees learn to disregard it entirely. That learned disengagement is cumulative. Once it sets in, a better content strategy alone will not reverse it. ## What changes when the access model actually works OU Health deployed a mobile-first employee app for clinical staff and reached 87% workforce engagement within the first few months — not because the culture messages improved, but because the platform finally reached frontline workers the previous system structurally excluded. That outcome reflects a consistent pattern: when access changes, engagement follows, because the cultural infrastructure can now actually deliver what it was designed to deliver. The access requirements for deskless workers are specific. The platform must function on personal devices without a corporate email address. It must deliver notifications in real time across varied shifts and time zones. It must work without a VPN. Without these characteristics, culture-building investment reaches some employees and misses the majority — and the collaborative behaviors organizations want never materialize at scale. AI-assisted personalization changes the equation further. When platforms surface communications based on role, location, and department — rather than broadcasting the same message to every employee — relevance improves and learned irrelevance declines. Employees who consistently receive communications that do not apply to them stop opening them. Per SWOOP Analytics, that learned disengagement is a primary driver of the six-minute average intranet engagement day. Role-based personalization is not a feature. It is what makes cultural communication land rather than disappear. The [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) documents that organizations actively cultivating engagement — not just tracking it — demonstrate measurably better retention, productivity, and customer outcomes. The mechanism is access: when every employee can receive, respond to, and contribute to the organizational communication stream, engagement follows. When they cannot, no amount of cultural investment closes the gap. ## The cultural behaviors talent management actually depends on Collaboration is not a feature of organizational charts. It is a choice employees make based on whether the environment signals that sharing is valued, safe, and practically easy. That choice depends on culture — and culture is built through specific behaviors that organizations can either enable or fail to enable at scale. Psychological safety — the ability to raise concerns, flag problems, and suggest ideas without fear of retaliation — is among the most consistent predictors of team performance. It is built through daily experience: being heard, seeing feedback acted on, observing that uncertainty can be acknowledged without consequence. When communication infrastructure excludes 80% of the workforce from that daily experience, psychological safety develops only in the pockets of the organization already connected. Recognition that reaches the recipient matters differently depending on where the employee works. Peer recognition and manager acknowledgment, when visible to the broader team, reinforce the behaviors an organization wants repeated. Recognition delivered through email threads or desktop-only platforms rarely reaches the clinical staff, warehouse workers, or retail associates it was meant for. What does not reach them does not motivate them. Closed feedback loops are the mechanism through which employees develop ownership over outcomes. Organizations that solicit input and visibly act on it cultivate this ownership. Organizations that solicit input and let it disappear into silence erode it. When frontline employees submit feedback through a platform they rarely access, see no response, and have no visibility into whether their input reached anyone, the loop is open. The deterioration that follows is gradual and invisible until it shows up in attrition data. Cross-functional visibility and accessible knowledge are the structural conditions that enable talent to develop faster. Employees who understand what other teams are working on reduce duplication, identify collaboration opportunities, and develop the organizational empathy that makes them worth retaining. This visibility requires a knowledge environment they can actually access — not one that requires a desktop login to navigate at all. ## Measuring whether culture is actually reaching everyone Culture is difficult to quantify, but the dimensions that matter most are trackable with the right tools. [Employee engagement](/solutions/employee-engagement) measurement means going beyond annual survey scores to real-time data: which workforce segments are receiving communications, which employees are responding to critical announcements, which teams are contributing to shared knowledge, and which employee populations are effectively invisible to the system. Without segment-level data, averages obscure the distribution. A 40% overall engagement rate might mean near-complete reach among headquarters staff and near-zero reach among overnight shift workers. Averages make that problem invisible until turnover data makes it undeniable — typically six to twelve months after the cultural deterioration already set in. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) identifies real-time feedback loops as one of the most consequential emerging capabilities in HR practice. Organizations that detect cultural deterioration before it becomes a retention event consistently outperform those waiting for annual survey results to arrive months after the relevant decisions were already made. The practical starting point is asking which employee populations the current platform cannot reach. That is where the cultural gap lives, and that is where the retention problem is developing. ## The sequence that builds culture capable of reaching everyone Building culture that supports outstanding talent management is not a single initiative. It is a sequenced set of infrastructure decisions, and the sequence matters. Fix access before fixing content. An organization that cannot reach its frontline workers cannot build culture with them — it can only build culture for the desk workers it already reaches. Once access is solved, measurement becomes tractable, feedback loops become real, and recognition finally lands with the people it was intended for. OU Health did not rewrite its culture messaging. It changed who could receive it. Development investment is the upstream variable for culture sustainability. [Why L&D strategies fail — and how to fix them](/articles/learning-and-development-strategy-embedded-in-daily-work) makes the critical distinction: the most effective approaches embed learning into the flow of daily work rather than treating it as a periodic formal training event. Organizations that connect development to the same environment where recognition, communication, and feedback occur build genuine talent management infrastructure. Organizations that silo training into a separate system add another access barrier. Cross-functional visibility and accessible knowledge are the final structural conditions. When employees can find information without spending 2.5 hours searching for it — when policy updates are findable, shift schedules are accessible on personal devices, and team knowledge does not disappear when someone leaves — the conditions for collaboration exist. Culture cannot overcome infrastructure failure. It can only amplify infrastructure that works. ## The takeaway for HR and operations leaders The talent management problem most organizations are trying to solve with better processes is usually an infrastructure problem. The processes work when the cultural environment they depend on reaches everyone. When 80% of the workforce is structurally excluded from that environment, the processes underperform regardless of their design quality. The first question worth answering is not "how do we improve our culture content?" It is "which employees does our current infrastructure actually reach?" OU Health answered that question and changed the access model. The result — 87% workforce engagement among clinical staff within months — was not the product of better messaging. It was the product of frontline workers finally being able to receive it. Organizations that consistently develop and retain outstanding people treat communication infrastructure with the same rigor they apply to financial or operational systems: measuring it, investing in it, and holding it accountable for reaching the entire workforce. Culture cannot be an aspiration that headquarters staff experience and frontline workers hear about secondhand. When the infrastructure reaches everyone, the talent strategy can too. --- # 10 Tips to Encourage Successful Innovation **Author:** Luke Walton **Published:** 2013-01-15 **Category:** company-culture Inspiring innovation amongst your employees can be extremely difficult. Most great ideas for enhancing corporate growth aren’t discovered at your research center or by brainstorming in the conference room. They come from the employees who regularly serve your customers and regularly experience setbacks. Identifying ways to encourage these employees to become more outspoken remains a […] # 10 Tips to Encourage Successful Innovation Most organizations say they want more innovation. Few have the infrastructure to produce it reliably. The gap isn't a shortage of ideas — per IDC, employees spend an average of 2.5 hours per day searching for information, which means the people closest to operational problems rarely have a clear channel for surfacing what they've observed. The ideas exist. The systems for capturing, routing, and recognizing them often don't. Per Emergence Capital, 80% of the global workforce is deskless — working without a company laptop or corporate email address. When innovation programs run through desktop intranets that only 13% of employees use daily, per Social Edge Consulting, they structurally exclude the workers with the most direct exposure to customer friction and process inefficiency. Inclusive innovation isn't a values statement. It's a design requirement. Here are 10 tips for building an innovation program that reaches every employee, produces measurable outcomes, and earns the sustained participation it needs to succeed. ## Building the access layer and culture ### 1. Create a dedicated innovation channel Good ideas don't arrive on schedule. An always-on channel — whether a dedicated module in your employee experience platform or a structured idea campaign cadence — gives employees a place to submit observations when the insight is fresh. The platforms that sustain participation over time are embedded in existing workflows: the app employees already open for shift communications, schedule changes, or policy lookups. Adding a separate destination employees must remember to visit is the fastest way to build a channel no one uses after two campaign cycles. Employees who feel their ideas are heard are more likely to stay. Recognition of innovation contributions is a measurable driver of retention, not just morale — which means the channel design decision has a direct line to turnover. ### 2. Make mobile access a prerequisite, not an afterthought Per Emergence Capital, 80% of the global workforce is deskless. Innovation programs that rely on desktop-based submission tools exclude warehouse workers, nurses, retail associates, and distribution center staff — the employees with the most direct exposure to the operational problems worth solving. Mobile accessibility is the access layer that makes "involve everyone" achievable in practice rather than in policy. Programs that integrate with existing HRIS and workflow tools see higher participation rates because employees don't need to context-switch to an unfamiliar system. The lower the friction, the higher the quality of what gets submitted — because participation isn't reserved for employees who happen to have fifteen minutes at a desk. ### 3. Model transparency from the top down Transparency enables innovation by closing the information asymmetry that makes frontline ideas feel disconnected from organizational priorities. When employees understand what problems the organization is trying to solve and why certain ideas were implemented or passed on, they can direct their thinking toward submissions that matter. Per Social Edge Consulting, nearly a third of employees never log into an intranet at all. The tools that establish daily relevance are embedded in the same interfaces employees use for timekeeping, scheduling, and team updates — not a separate portal they visit once a quarter. Senior leaders who visibly engage with submitted ideas, commenting and acknowledging impact, signal that the channel is real. That signal compounds: employees who observe a peer's idea reach implementation are more likely to submit their own. ## Running campaigns and developing ideas ### 4. Run structured idea campaigns Idea campaigns work because they create focus and reduce ambiguity. Rather than asking employees to submit ideas whenever they want, a campaign gives a specific prompt, a deadline, and a clear review process. The result is a concentrated pool of focused submissions that's easier to evaluate than an open-ended suggestion box accumulating for months. Campaign design matters as much as campaign promotion. Employees should be able to submit, comment on, and build onto each other's ideas — collaborative development catches gaps that solo submissions miss. Milestone recognition tied to campaign stages gives employees visible proof that the program is active, not ceremonial. ### 5. Involve all layers of the organization Most innovation programs describe themselves as open to everyone. Most generate submissions disproportionately from desk workers in headquarters roles. Closing that gap requires active outreach — not just a company-wide notification, but campaign promotion through the specific channels frontline teams use: team messaging apps, shift briefings, supervisor announcements. Frontline workers see customer friction that corporate teams don't. Logistics staff observe process inefficiencies invisible to product managers. Diversity of participation is the mechanism that surfaces the ideas most likely to move business metrics — not a feel-good principle layered on top. ### 6. Develop ideas collaboratively Individual submissions are a starting point, not an endpoint. The most productive programs create a visible idea development layer: employees can comment, add context, or flag operational constraints the original submitter didn't account for. This refinement step improves idea quality and distributes ownership — a team that helped shape an idea is more invested in its outcome than one that was informed of a decision afterward. AI-assisted idea surfacing adds leverage here. Modern employee experience platforms can flag trending submissions, surface dormant ideas that match current priorities, and route suggestions to the relevant manager automatically — reducing the manual overhead that causes good ideas to stall in a review queue. ## Closing the loop with recognition and accountability ### 7. Build a structured recognition system Recognition tied to innovation works best as a closed-loop system, not a cultural add-on. The loop has four stages: submission acknowledged, idea under review, idea advancing to pilot, idea implemented. Each stage is an opportunity to recognize the contributor publicly — on a leaderboard, in a team update, or in a company-wide post. Recognizing at each stage tells employees that the program is functioning, not just collecting. Peer nominations add a lateral recognition layer that manager-only systems miss. When colleagues can nominate each other for a well-developed observation or a creative solution, the program's signal reaches employees who might have otherwise dismissed it as a management initiative. See how this plays out in practice in [From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program](/resources/how-symplr-leverages-mangoapps-for-an-effective-rewards-and-recognition-program). ### 8. Give managers a structured review process Managers are often the weakest link in innovation programs — not because of intent, but because of missing process. They receive idea submissions with no structured workflow, no response-time expectation, and no escalation path. The result is a backlog of unacknowledged submissions that signals to employees that nothing actually happens. The fix is structure: assign a review owner for each campaign, set a response-time SLA (five business days is a practical starting point), and give managers a dashboard showing open submissions by submission date. Consistent, timely responses — even "we reviewed this and here's why we're not moving forward" — sustain participation because the feedback loop stays visible. ### 9. Connect innovation outcomes to organizational metrics Innovation programs that stay internal — ideas submitted, ideas reviewed, ideas filed — produce limited return. Programs that connect implemented ideas to business outcomes produce compounding return: employees see evidence that the channel drives real change, which increases participation in the next campaign cycle. Per the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook), leading organizations are structuring recognition and engagement investments around measurable outcomes rather than activity metrics. Tracking cost savings, cycle time reductions, or customer satisfaction improvements tied to implemented ideas gives the program a business case that sustains budget support through leadership transitions. ### 10. Reward implementation, not just submission Most recognition programs reward submission volume. The more powerful recognition target is implementation: when an employee's idea moves from concept to operational change, that outcome deserves visible acknowledgment proportional to its impact. Peer nominations, leaderboard milestones, and public acknowledgments in team feeds are low-cost mechanisms with outsized signal value. Incentive budgets don't need to be large. A well-designed [employee engagement](/solutions/employee-engagement) platform that consolidates idea management, recognition, and communication in a single experience does more for participation rates than a generous gift card budget attached to a platform employees rarely open. --- ## Measuring whether your program is working Running idea campaigns is the visible part of innovation management. Measuring outcomes is how you know whether the program is producing value or just activity. Track these metrics each quarter: **Ideas submitted per quarter.** A baseline volume indicator. Healthy programs typically see participation grow 20–30% after the first full campaign cycle, once employees trust that submissions receive responses. **Idea implementation rate.** The percentage of submitted ideas that advance from review to pilot or full rollout. Even a 5–10% implementation rate signals that leadership takes submissions seriously. Rates below 3% usually indicate a review bottleneck or a disconnect between what employees are submitting and what the organization is prioritizing — worth diagnosing before the next campaign. **Business impact per implemented idea.** Ties the program to organizational outcomes: cost savings, process efficiency gains, customer satisfaction improvements. This metric justifies continued investment and gives the program a seat in budget conversations beyond "it's good for culture." **Participation rate by team and location.** Surfaces inclusion gaps. Low participation from frontline or deskless teams typically points to an access problem — the submission channel isn't mobile-friendly, or the campaign wasn't communicated through the channels those teams actually use. **Time-to-review.** The single most damaging metric if left unmanaged. Per SWOOP Analytics, employees spend an average of six minutes per day using intranet tools. When a submission generates no visible response for weeks, employees don't return. A five-business-day response SLA — even a brief acknowledgment — substantially improves participant retention across subsequent campaigns. Per [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), employees who feel their contributions are recognized and connected to organizational goals are substantially more engaged and less likely to leave. An innovation program that closes the feedback loop between submission and outcome is one of the most direct mechanisms for producing that connection at scale. --- ## Common pitfalls that undermine innovation programs The tips above describe what successful programs do. The failure modes are equally instructive. **Treating the platform as the program.** Deploying an idea campaign tool doesn't create an innovation culture. The platform creates the channel; the program requires review owners, response SLAs, recognition touchpoints, and a visible connection between submissions and decisions. Organizations that deploy a platform and wait for innovation to happen typically find themselves with a channel nobody uses after the second campaign. **Excluding frontline workers by default.** Per Social Edge Consulting, 91% of organizations operate an intranet, but only 13% of employees use it daily. Per SWOOP Analytics, the average daily session is six minutes. If the innovation channel lives inside the intranet, it's functionally inaccessible to most of the workforce. Mobile-first channels embedded in daily workflows are the only access model that reliably reaches distributed and frontline teams. **Recognizing too late in the process.** Programs that only acknowledge ideas when they're implemented create long gaps of silence during which most employees disengage. Closing the recognition loop at each stage — submission received, under review, advancing to pilot, implemented — sustains participation between campaign cycles. **Failing to explain non-selections.** When ideas aren't chosen for implementation, employees benefit from understanding why. A brief explanation — "this conflicts with a regulatory constraint we're navigating" or "we're revisiting this in Q3" — converts a non-selection into a signal that the system is functioning. Silence converts it into a signal that it isn't. --- The employees closest to your customers and operations already have observations worth acting on. What most organizations lack is not raw ideas but a structured path from submission to decision to visible outcome — and a recognition system that makes employees want to repeat the process. Build that infrastructure and the innovation culture follows. Build the culture without it and you're asking people to trust a loop that doesn't close. --- # Employee Social Profiles: The New Company Directory **Author:** Vishwa Malhotra **Published:** 2013-01-07 **Category:** modules-features Corporate employee directories traditionally provide only basic employee contact details. The reason you have probably looked up someone in the employee directory is to get the person’s contact number or in some cases know his experience and background info. Corporate employee directories in most cases are not integrated with your other work software like the […] # Employee Social Profiles: The New Company Directory According to IDC, employees spend an average of 2.5 hours each day searching for information — a cost that accumulates whether or not anyone measures it. A significant portion of that time isn't spent searching documents or databases. It's spent trying to find the right person: someone with the expertise, context, or history to answer a question that nobody has written down. Traditional employee directories were supposed to solve this problem. They mostly haven't. A directory entry with a name, a phone number, and a job title tells you how to reach someone. It doesn't tell you whether that person is the right one to call, whether they've navigated a similar project, or whether five colleagues have already endorsed their expertise in the exact domain you need. Employee social profiles replace the static directory with a living professional record — one that accumulates skills, contributions, recognitions, and network relationships alongside the contact basics. The result is a system that can answer the questions organizations actually need answered: who knows this domain, who has done this before, and who is the right person to involve in this decision. ## Why static directories fail to scale Social Edge Consulting research shows that 91% of organizations operate an intranet, but only 13% of employees use it daily — and nearly a third never log in at all. That usage gap reflects something real about how directories are typically designed: they were built to store data, not to surface it. A traditional directory entry is static by nature. It reflects what HR entered at onboarding, updated only when someone remembers to maintain it. Role changes, new skills, completed certifications, and project experience accumulate in employees' actual work — not in the directory. The result is a tool that becomes less accurate over time and less useful as organizations grow and change. The search experience compounds the problem. SWOOP Analytics benchmarks average daily intranet usage at just six minutes. When finding the right expert requires browsing an org hierarchy or guessing the exact title of a colleague's role, most people stop trying and ask someone nearby instead. The knowledge the organization needs to share stays siloed by default. ## What employee social profiles actually contain An employee social profile is a structured, continuously updated record that brings together professional identity, work history, and real-time contribution data in one place. The contact basics are still present — name, title, department, location, direct line. But the profile builds outward from that foundation in ways a static directory cannot: **Skills and expertise.** Employees can declare areas of knowledge, and colleagues can endorse specific skills. This creates a crowdsourced skills inventory that reflects what people actually know rather than what their job title implies. Over time, the endorsement layer becomes a lightweight credentialing system — when multiple colleagues have endorsed someone's expertise in a subject, that signal carries weight in a way a self-reported title does not. **Work activity and contributions.** Social profiles capture what an employee has created, collaborated on, and contributed to: posts, documents, wikis, projects, ideas, campaigns. This activity feed turns a static entry into a professional record that shows how someone operates, not just where they sit. It answers the question that directories cannot: what has this person actually done here? **Awards and recognition.** Recognition received from managers and peers appears on the profile. This gives anyone reviewing the profile a view of what contributions have been valued — not just what tasks have been completed. For peer recognition specifically, a visible record of endorsements from colleagues across departments carries different weight than manager-assigned performance ratings. **Organizational connections.** Social profiles show who follows whom, who has collaborated on shared projects, and where reporting lines run. This network data often proves more useful for routing questions than the formal org chart, because it reflects actual working relationships rather than administrative hierarchy. ## How AI-assisted search changes expert discovery The traditional approach to finding an internal expert is to ask around: query your manager, search a job title, or post in a general channel and hope the right person sees it. This works for small organizations with stable teams. It fails at scale. When social profiles aggregate skills, contributions, and endorsements across the workforce, they create a searchable knowledge graph. AI-assisted search across this data can surface the right expert in seconds — filtering by declared skills, contribution history, project context, and peer endorsements simultaneously. A manager looking for someone who has navigated a specific regulatory process, managed a particular type of client, or built expertise in a technical domain doesn't need to know where that person sits in the hierarchy. The search does the routing. This isn't a soft cultural benefit. IDC's research on the 2.5 hours per day employees spend searching for information includes the time spent locating the right person as much as the time spent finding the right document. Reducing that friction across a workforce of hundreds or thousands of employees is a measurable productivity return. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) identifies expert-finding as one of the highest-value use cases for organizations investing in connected employee platforms — partly because it directly reduces information search overhead, and partly because it surfaces expertise that would otherwise stay invisible to the people who need it most. ## Frontline and deskless workers need profiles too According to Emergence Capital, 80% of the global workforce is deskless. Retail associates, field service technicians, warehouse staff, and healthcare aides outnumber office employees in most industries — yet most employee directory tools were designed for the 20% at a desk. A traditional directory assumes a company email address, a corporate laptop, and scheduled time to sit down and update a profile. None of those conditions reliably apply to frontline workers. The result is a skills inventory and expert-finding system that documents only part of the workforce — the part that already has the most organizational visibility. Social profiles built for frontline access work differently. Enrollment can happen via QR code, SMS invitation, or personal email rather than a corporate provisioning process. Profile updates can happen from a personal phone between shifts. Recognition received during a shift appears on the profile immediately, not after a manager files a report at the end of the week. This matters for retention as much as visibility. Frontline employees who appear in the organization's knowledge network — who receive recognition that surfaces on a profile others can see — experience the workplace differently than those who are administratively invisible outside their immediate team. When replacing a frontline worker in a mid-skill role costs $4,400–$15,000 per departure, tools that increase connection and visibility have a direct impact on that number. ## HRIS integration keeps profiles current without manual maintenance The most common reason employee profiles become useless is staleness. A profile created at onboarding and never updated reflects where someone started, not where they are. Role changes, promotions, certifications, and department transfers don't appear unless someone actively maintains the record — and in most organizations, nobody does. HRIS-integrated social profiles solve this at the source. When an employee's role changes in the HR system, the profile updates automatically: the org chart relationship, the reporting line, and the access permissions all adjust without requiring a separate profile edit. Certifications logged in an LMS sync to the skills section. Promotions appear in the activity feed the day they're recorded in the HR system. This eliminates the administrative burden that causes most employee directory programs to degrade over time. Your HR team isn't maintaining a separate system alongside the HRIS — the HRIS is the source of record, and the social profile is the human-facing view of it. The [American College of Radiology case study](/resources/case-study-american-college-radiology) shows what this looks like in practice: a distributed professional organization connecting staff across multiple locations found that automating profile maintenance was the condition that made expert-finding actually work. Profiles people trust are profiles people use — and profiles nobody maintains are profiles nobody trusts. ## How social profiles connect to engagement outcomes Employee social profiles are not a standalone feature. They're infrastructure for the engagement behaviors that improve retention, knowledge sharing, and onboarding speed. [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) identifies connection to colleagues and clarity about one's contribution to the organization as two of the strongest predictors of sustained engagement. Social profiles address both directly: they make each employee's contribution visible to the rest of the organization, and they give colleagues the context to build working relationships across departments and locations. The engagement mechanism works in both directions. An employee who can find a colleague's profile and see their project history, skills, and recognitions has more basis for reaching out than one who knows only a name and a title. That context reduces the friction of cross-functional collaboration — which, in large and distributed organizations, is often what determines whether institutional knowledge gets shared or stays isolated. For new employees specifically, a populated social network from day one accelerates the onboarding process. Knowing who to contact for a specific question — and having a basis for trusting that contact — shortens the path from hire to full contribution. Recognition received in the first 30 days that appears on a social profile is a qualitatively different signal than a private message from a manager. ## What makes implementation succeed Three factors determine whether a social profile program delivers on its promise or stagnates as another underused tool: **Adoption investment at launch.** Profiles that nobody fills out are empty directories. The organizations that get lasting value from social profiles invest in onboarding campaigns that explain the purpose, give employees time to complete their profiles, and establish recognition norms that make profile activity visible and meaningful. The platform creates the opportunity; deliberate adoption work creates the habit. **Mobile-first access design.** Any organization with frontline or field-based employees needs to assume that the majority of profile activity — updates, recognition, expert searches — will happen on a personal mobile device. A platform that requires VPN access, a corporate login, or a workstation to complete enrollment has excluded the majority of the workforce before anyone has sent a single recognition. **Connection to existing HR systems.** Without HRIS integration, the administrative burden of keeping profiles current falls on individual employees and HR administrators. With it, the foundational data is maintained automatically, and employees add the context that systems can't generate: self-reported skills, professional interests, and the professional narrative that makes a profile useful rather than just technically complete. ## From directory to knowledge infrastructure A static employee directory answers: how do I reach this person? An employee social profile answers: who is this person, what do they know, what have they contributed, and who in the organization has recognized their expertise? That's not an incremental improvement on the old directory. It's a different category of tool — one that makes organizational knowledge visible, searchable, and accessible to everyone who needs it, including the 80% of the workforce that doesn't sit at a desk. When your [modern intranet](/solutions/modern-intranet) connects social profiles to your HRIS, your recognition program, and your mobile access layer, you're building a capability that compounds over time. In the first months, it replaces the directory. Within a year, it becomes the mechanism through which expertise, collaboration, and organizational memory flow — not just for headquarters employees, but for everyone who works for the organization, wherever they work. --- # How To Compare Social Collaboration Software Vendors **Author:** patricka **Published:** 2012-12-18 **Category:** comparisons Your company’s decision to harness the power of social collaboration is commendable. With numerous vendors available, the key question is: how do you pick the best social collaboration software for your needs? Drawing insights from Jacob Morgan, the acclaimed author of “The Collaborative Organization,” there are eight essential aspects to consider when evaluating intranet vendors. […] # How to Compare Social Collaboration Software Vendors Choosing the right social collaboration platform is one of the higher-stakes IT decisions an organization makes — not because platforms are expensive (though they can be), but because the wrong choice at this stage tends to compound. According to Social Edge Consulting, 91% of organizations already run an intranet or collaboration platform. Only 13% of employees use it daily. Nearly a third never log in at all. Those numbers are not an employee engagement problem. They are a vendor selection problem. The evaluation frameworks that most organizations apply when comparing vendors are too thin. Three criteria are not eight. A polished demo is not a pilot. And the headline question — "Does this platform have the features we need?" — misses the dimension that actually predicts outcomes: "Will our employees use it?" This guide covers eight criteria drawn from vendor evaluation research and from patterns in organizations that have navigated intranet replacements successfully. The framework applies whether evaluating MangoApps, Simpplr, Unily, LumApps, Staffbase, or any other platform in the market. --- ## Why vendor demos reveal less than they appear to A typical vendor demo optimizes for visual appeal: polished UI, smooth navigation, and a persona scenario designed to show the product at its best. The demo answers the question "What can this platform do?" It rarely answers the question "What will it cost to do that for us, and how long will it take?" Total cost of ownership is the most systematically underweighted variable in vendor comparisons. A first-year deployment on SharePoint, including implementation and customization, runs between $130,000 and $426,000 for a 1,000-user organization, according to Awesome Technologies Inc.'s 2025 cost model — before ongoing maintenance, third-party integrations, or developer time. Platforms with pre-built configurations and packaged deployment services operate on a fundamentally different cost and timeline model, but that difference only becomes visible when organizations ask the right questions. SWOOP Analytics puts the average daily time employees spend actively using intranet tools at six minutes. IDC estimates that employees spend 2.5 hours per day searching for information. The gap between those numbers is not a training deficit. It is the cost of deploying a platform that does not surface the right content to the right people at the right time. A thorough vendor comparison surfaces which platforms are structurally designed to close that gap, and which ones will replicate the six-minutes-per-day problem in a new interface. --- ## The eight criteria for comparing social collaboration vendors ### 1. Deployment model and infrastructure Cloud-hosted, private cloud, and on-premise deployments carry meaningfully different cost, compliance, and timeline profiles. A vendor offering only a shared multi-tenant cloud may not be viable for organizations with data residency requirements or regulated industries. Confirm which deployment models are available under standard licensing and which require a separate contractual arrangement. Ask: What are the SLA commitments for each deployment option? Who manages infrastructure updates, and how are customers notified when the platform changes? ### 2. Licensing and total cost of ownership All-inclusive and modular pricing models produce very different long-term costs. Some vendors include mobile access, integrations, and modules like idea management or analytics in the base license. Others charge separately for each. Get a multi-year cost projection that includes onboarding, implementation services, and anticipated integrations — not just the per-seat rate. Replacing a frontline employee costs between $4,400 and $15,000 on average according to MangoApps internal analysis. A platform that fails to drive adoption in frontline roles carries a hidden cost that does not appear in any vendor's pricing proposal. ### 3. Customization costs and timeline Customization is one of the most common sources of implementation surprise. Some vendors charge at consulting hourly rates for any branding, workflow, or integration work outside a narrow defaults envelope. Others allow organizations to configure the platform through administrative interfaces without involving professional services. Confirm which customizations are self-service, which require vendor involvement, and what the rate is for each. The timeline question matters as much as the cost question. Modern packaged platforms have reduced enterprise deployment timelines significantly — one 40,000-employee organization replaced its legacy intranet in eight weeks using a purpose-built platform. Custom-built SharePoint implementations rarely finish inside twelve months. ### 4. Mobile access and frontline worker support Emergence Capital estimates that 80% of the global workforce is deskless — working in manufacturing, healthcare, retail, logistics, and field services where desktop access is intermittent or absent. For most organizations, the mobile experience is not a secondary feature. It is the primary interface for the majority of their workforce. Evaluating mobile is not about checking a box. The right test is this: access the platform on a personal mobile device, without a corporate email address or VPN, on a first log-in. That experience tells more about frontline adoption likelihood than any vendor demo. Vendors whose mobile interface requires company credentials, an IT-managed device, or a VPN tunnel have a structural barrier that training cannot resolve. Purpose-built platforms achieve frontline adoption rates of 90% within the first six months, as documented in a CVS deployment case study. That benchmark is not reachable with mobile-as-afterthought architecture. The [MangoApps employee app](/solutions/employee-app) and comparable purpose-built platforms start from the opposite premise: mobile is the primary design surface, and desktop is the extension. ### 5. Security and compliance Security has moved from a procurement checkbox to an active vendor differentiator. Five vendors in the intranet market now publish dedicated content on secure intranet capabilities — this is not a niche concern. The evaluation dimensions that matter most are: role-based permissions (can content access be limited by department, location, or employment type?), SSO compatibility (which identity providers does the platform support natively?), data residency options (can data be localized to specific regions?), and audit logging (what actions are recorded and for how long?). For organizations in healthcare, finance, defense, or government contracting, compliance certifications — HIPAA, FedRAMP, SOC 2, HITRUST — are screening criteria, not differentiators. Confirm current certification status and ask which certifications are actively in progress. ### 6. AI readiness and personalization AI-driven content personalization has shifted from a premium add-on to a standard differentiator in vendor evaluation conversations. The question is no longer whether a platform uses AI, but what the AI actually does. Content that surfaces by role, location, hire date, and activity history — without requiring employees to configure preferences — is meaningfully different from a platform with a search bar that uses keyword matching and calls it AI. According to the State of the Digital Workplace and Modern Intranet 2024 research, only 22% of company intranets currently deliver personalized content to employees. That gap is one of the primary drivers of the six-minutes-per-day usage pattern. Vendors who treat AI personalization as a differentiator should demonstrate it during the evaluation, not just describe it. The [MangoApps modern intranet solution](/solutions/modern-intranet) surfaces AI-curated feeds that adjust by role and engagement history without employee configuration — a capability worth testing against any vendor's claimed AI functionality during the evaluation period. ### 7. Integration ecosystem No organization deploys a collaboration platform in isolation. The integrations that matter are the ones employees already use: Microsoft 365 (SharePoint, Teams), Google Workspace, HRIS systems, scheduling tools, ticketing platforms, and SSO providers. A platform's total integration count is less important than the depth of the specific integrations the organization will actually use. The distinction between a native integration and a middleware-bridged connection matters for reliability, data freshness, and support ownership. Ask vendors to demonstrate the integrations the organization plans to use, not the ones in their marketing materials. For organizations that cannot migrate existing SharePoint document libraries, look for federation capabilities that surface SharePoint, Teams, and Google Drive files in a unified search without requiring content migration. The [ClearBox 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) scores vendors on integration depth and is a useful third-party reference for narrowing the field before finalizing an evaluation shortlist. ### 8. Adoption support and long-term vendor relationship The implementation team and the long-term support model are often the most consequential variables in a vendor comparison, and the least visible during the sales process. Ask for references from organizations of similar size and complexity. Ask whether implementation is handled by the vendor directly or subcontracted to a partner. Ask what the escalation path is for post-launch support. Platform adoption is not an event — it is a sustained process. Vendors who treat go-live as the finish line tend to produce the same underperformance patterns organizations were trying to escape when they initiated the evaluation. Ask for the vendor's documented approach to adoption at six months and twelve months, not just at launch. --- ## Questions to ask vendors that demos do not surface Structured vendor conversations produce information that demos cannot. Bring these questions into every evaluation: - What is the typical implementation timeline for organizations of our size, and what is our role in the project? - What customizations are self-service versus professionally serviced, and what is the hourly rate for the latter? - How does your platform support employees who do not have company email addresses or work on personal devices? - What security certifications do you hold, and which are currently in progress? - What does AI personalization actually do in your platform, and can we test it with our own content during the evaluation? - What does adoption support look like at six months and twelve months post-launch? The answers to these questions, documented consistently across vendors, produce a comparison that extends well beyond feature checklists. --- ## How to run a pilot that predicts adoption A pilot that tests only what the vendor prepares is not informative. A pilot that reflects actual usage conditions is. Three design principles produce useful pilots: **Test with representative users, not champions.** The employees who volunteer for pilots tend to be early adopters with higher tolerance for friction. Test with employees who represent the median: mid-tenure, distributed across departments, including frontline roles if the workforce includes them. **Test the first-log-in experience without IT assistance.** If the authentication or onboarding flow requires IT support to complete, that friction will appear at scale. New employees and frontline workers are most likely to encounter it. Simulate what they will actually experience. **Measure engagement at thirty days, not at launch.** Launch-week engagement numbers are inflated by novelty and organizational pressure. Thirty-day active use rates — and daily active use rates specifically — are the leading indicator of what year-one usage will look like. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers adoption benchmarks by workforce type and deployment model, useful context for setting realistic thirty-day targets during pilot design. --- ## What the comparison framework reveals A thorough evaluation using all eight criteria tends to sort vendors into three categories: platforms built for organizations like yours, platforms that could work with significant customization, and platforms that fundamentally misfit your workforce composition. The most common misfit is mobile. Organizations with significant frontline workforces often discover during piloting — not before — that a platform's mobile experience requires corporate credentials, managed devices, or IT-supported enrollment. That discovery late in an evaluation is expensive. The criteria above surface it early. The second most common misfit is cost. A platform priced attractively at the per-seat level often carries customization, integration, and governance costs that appear after signature. Getting a total first-year cost model from every vendor — including professional services, integrations, and training — is the most reliable way to compare the actual cost of each option. The goal of the comparison framework is not to find the platform with the most features. It is to find the platform that employees will actually use, at a cost the organization can sustain, within a deployment timeline that fits IT capacity. Those three constraints, applied rigorously to each vendor, produce a defensible choice — and avoid replicating the same six-minutes-per-day problem in a new interface. --- # 5 Best Yammer Alternatives for Enterprise Collaboration Software **Author:** Vishwa Malhotra **Published:** 2012-12-15 **Category:** comparisons Searching for Yammer alternatives? Look no further! Choosing the ideal collaboration software for your enterprise can be challenging. Your choice should consider: Concerns with Yammer: Its shared cloud SaaS often doesn’t align with the stringent security needs of some enterprises, making it less viable for businesses wanting to maintain data on-premise, behind company firewalls. Reasons […] # 5 Best Yammer Alternatives for Enterprise Collaboration Software Searching for Yammer alternatives? Here is the short answer: the five most-evaluated replacements are **MangoApps**, **Salesforce Chatter**, **IGLOO**, **SocialText**, and **Microsoft Viva Engage**. Each serves a different profile—read the comparison below to find the right fit for your organization's size, deployment model, and workforce type before scheduling a single demo. Choosing the ideal [employee engagement software](/solutions/modern-intranet) for your enterprise can be challenging. Your choice should consider: - Your unique operational demands. - The size of your organization. - Expected platform user count. **Concerns with Yammer:** Its shared cloud SaaS often doesn't align with the stringent security needs of some enterprises, making it less viable for businesses wanting to maintain data on-premise, behind company firewalls. Per Social Edge Consulting, 91% of organizations operate an intranet—yet nearly a third of employees never log in, and only 13% use one daily. Poor platform fit is a leading driver of that disengagement. **Reasons you might switch from Yammer include:** - Need for single-tenant private cloud or on-premise Enterprise Social Networks (ESN). - Seeking specific ESN customizations. - Wanting non-binding monthly agreements. - Preference for Perpetual Licensing. - Requirement for unique business system integrations. - Needing a data center outside the US. - Having fewer than 250 employees. - Not being an MSFT EA client. Note also that switching costs for Microsoft-stack ESNs extend well beyond licensing—customization, migration, governance, and third-party tooling can push first-year costs for a 1,000-user deployment to $130,000–$426,000, per MangoApps blog analysis and the Awesome Technologies Inc. 2025 cost model. That figure alone makes a thorough alternatives evaluation worthwhile. ## Top Yammer Alternatives for Enterprise Users **#1. MangoApps** Beyond a Yammer alternative, MangoApps offers content management, collaboration, communication, and more through a unified [employee app](/solutions/employee-app). Catering to organizations from 50 to 1 million users, MangoApps provides versatile deployment options—shared SaaS, single-tenant private cloud, and on-premise—along with security compliances including HIPAA and SOC 2 Type II. Unlike Yammer, MangoApps is built with frontline and deskless workers as a primary use case. Per Emergence Capital, 80% of the global workforce is deskless. MangoApps supports access without a corporate email address or VPN, from any device, making it viable for manufacturing, retail, healthcare, and logistics environments where Yammer and most competitors fall short. The platform also supports 50+ languages with real-time translation built in—a critical differentiator for global enterprises. Real-world outcomes: OU Health achieved 87% workforce engagement within a few months of launching a branded employee app on MangoApps. Wipro captured $20M in cost avoidance after deploying a unified employee experience platform. For context on what poor ESN adoption costs, replacing a single frontline employee runs $4,400–$15,000 on average—making engagement platform ROI measurable and direct. **Deployment options:** Shared SaaS · Single-tenant private cloud · On-premise **Security:** HIPAA, SOC 2 Type II **Best for:** Organizations of 50–1,000,000 users needing flexible deployment, frontline access, and enterprise security **Pricing model:** Per-seat subscription; perpetual licensing available **#2. Chatter** Salesforce's enterprise social network is mostly a layer on their CRM system. It currently lacks integration with project management tools and doesn't offer on-premise deployment. It has no meaningful frontline workforce story and is best suited to sales-led organizations already deeply invested in the Salesforce ecosystem. **Deployment options:** Multi-tenant SaaS only **Best for:** Salesforce-centric sales teams **Frontline access:** Not supported **#3. IGLOO** A viable option for online communities and enterprise collaboration, but limits small to mid-market customers to multi-tenant SaaS deployment. Organizations with on-premise or private-cloud requirements will find IGLOO's deployment flexibility insufficient. **Deployment options:** Multi-tenant SaaS **Best for:** Mid-market online communities **Frontline access:** Limited **#4. SocialText** A collaboration application focused on wikis, SocialText offers engaging intranet experiences but lacks integrations with common business tools like Microsoft Office. It is a niche choice for knowledge-worker teams that prioritize wiki-style documentation over broader ESN functionality. **Deployment options:** SaaS and on-premise **Best for:** Knowledge-worker teams, wiki-centric workflows **Frontline access:** Not a primary use case **#5. Microsoft Viva Engage** Replacing Yammer, Viva Engage is Microsoft's newest enterprise collaboration tool, emphasizing community engagement. With the Yammer brand phasing out, Viva Engage promises features that foster leadership involvement and efficient knowledge sharing, making it a potential fit for modern organizations already in the Microsoft 365 ecosystem. However, it inherits Yammer's shared-cloud architecture and remains a poor fit for organizations needing on-premise deployment, non-Microsoft integrations, or frontline access without corporate credentials. **Deployment options:** Microsoft 365 shared cloud only **Best for:** Microsoft EA customers with primarily desk-based workforces **Frontline access:** Requires Microsoft 365 F-tier licensing ## How to Choose: Matching Alternatives to Your Situation The right Yammer alternative depends on three decision variables that the brief descriptions above cannot fully resolve on their own. **By company size:** - Fewer than 250 employees: MangoApps and IGLOO both serve this segment; Viva Engage requires Microsoft EA status that most sub-250 organizations don't hold. - 250–5,000 employees: All five alternatives are viable, but deployment model and frontline access requirements narrow the field quickly. - 5,000+ employees: MangoApps (up to 1M users), Viva Engage, and Chatter are the realistic options at enterprise scale; SocialText and IGLOO have limited enterprise references at this size. **By deployment requirement:** - On-premise or single-tenant private cloud: MangoApps and SocialText are the only alternatives on this list that support it. Chatter, IGLOO, and Viva Engage do not. - Multi-tenant SaaS only: All five support this model. **By workforce type:** - Desk-based knowledge workers: All five alternatives are adequate. - Frontline or deskless workers (manufacturing, retail, healthcare, logistics): MangoApps is the only alternative on this list with a native frontline access model—no email, no VPN, any device. Per IDC, employees spend 2.5 hours per day searching for information; per SWOOP Analytics, the average daily time spent using intranet tools is just six minutes. Closing that gap requires a platform frontline workers will actually open. The [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent scoring across these dimensions if you want a third-party benchmark. **By total cost of ownership:** - Viva Engage appears low-cost if you already pay for Microsoft 365, but first-year TCO for a 1,000-user Microsoft-stack ESN deployment—including customization, migration, governance, and third-party tooling—can reach $130,000–$426,000, per MangoApps blog analysis and the Awesome Technologies Inc. 2025 cost model. - MangoApps offers perpetual licensing as an alternative to per-seat SaaS, which can materially reduce multi-year TCO for large deployments. - Chatter pricing is bundled into Salesforce tiers, making standalone cost comparison difficult. ## Discover the Ideal Yammer Alternative for Your Needs Platforms like MangoApps are stepping up, providing secure social networks, collaborative intranet software, and diverse deployment options. Switching to MangoApps can elevate your organization's security, employee engagement, and team synergy—with measurable outcomes like the $20M in cost avoidance Wipro captured and the 87% workforce engagement OU Health achieved within months of launch. If you are evaluating the full landscape of employee engagement software, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are structuring their platform decisions this year. For a deeper look at how MangoApps has been independently evaluated, see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms). Ready to move forward? Schedule a personalized demo to see how MangoApps fits your specific deployment, security, and workforce requirements. ## Which Yammer Alternative Has the Best Integrations? Integration depth varies significantly across the five alternatives. MangoApps supports connections to HRIS platforms, project management tools, Microsoft 365, Google Workspace, and custom business systems via API—including integrations that Yammer and Viva Engage do not natively support. Chatter integrates deeply with Salesforce CRM but has limited reach outside that ecosystem. SocialText notably lacks Microsoft Office integration, which is a disqualifying gap for most enterprises. IGLOO and Viva Engage offer moderate integration libraries, with Viva Engage strongest for organizations already standardized on Microsoft tooling. If your switching reason is a specific business system integration that Yammer cannot support, MangoApps and IGLOO are the most flexible starting points. ## What Happens to My Data If I Switch from Yammer? Data migration is one of the most underestimated switching costs in ESN transitions. Yammer stores conversation history, files, and community membership in Microsoft's shared cloud; exporting that data requires Microsoft's native export tools, which produce raw JSON and are not directly importable into most alternatives without a migration partner. MangoApps provides migration support and can ingest structured exports. Organizations with compliance requirements (HIPAA, SOC 2, GDPR) should confirm that their chosen alternative can receive data into a compliant environment from day one—not after a transition period on shared infrastructure. If your organization needs a data center outside the US, MangoApps is the only alternative on this list that explicitly supports that requirement. ## Is There a Yammer Alternative Built for Training and Employee Engagement? Several enterprises evaluate Yammer alternatives specifically because they need to combine employee engagement with structured learning—what is sometimes called employee engagement training or training on employee engagement. MangoApps supports this use case through integrated workspaces, course delivery, and knowledge-base tools within a single platform, eliminating the need for a separate LMS alongside an ESN. For organizations building this capability, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) outlines how to embed learning into daily workflows rather than treating it as a separate system. Viva Engage can connect to Viva Learning within the Microsoft ecosystem, but that requires additional licensing. Chatter and SocialText have no native learning delivery capability. --- # Top 10 SharePoint Alternatives for File Sharing and Collaboration **Author:** patricka **Published:** 2012-12-13 **Category:** comparisons There are many different reasons an organization might be seeking a SharePoint alternative. At MangoApps, we’ve seen them all—a great deal of our customers are former SharePoint customers. The most common issues they cite are lack of support for frontline employees, poor functionality in areas like search, governance, and personalization, or overreliance on expensive consultants […] Per IDC, employees spend 2.5 hours per day searching for information — a problem a well-chosen intranet should solve, not compound. Per SWOOP Analytics, the average employee spends just six minutes per day in intranet tools, which suggests that most SharePoint deployments aren't succeeding at the adoption problem they were purchased to fix. The cost stakes make the choice consequential. SharePoint's first-year total cost of ownership for a 1,000-user enterprise — including licensing, implementation, and customization — can reach between $130,000 and $426,000 (per Awesome Technologies Inc.'s 2025 cost model). That's not an indictment of the product; for many organizations, SharePoint's document management and IT governance are genuinely valuable. But it does mean that choosing the wrong alternative is expensive to reverse. Per Social Edge Consulting, 91% of organizations operate an intranet, but nearly a third of employees never log in, and only 13% use one daily. The right SharePoint alternative closes that adoption gap. The wrong one replicates it under a different product name. ## What to evaluate before you build a shortlist Modern alternatives in this category are evaluated on four criteria: deployment flexibility, adoption potential, integration breadth, and AI-driven personalization. Feature parity with SharePoint is a baseline expectation, not a differentiator. **Deployment flexibility** separates platforms that require significant IT and partner overhead from those with pre-built templates and no-code configuration. **Adoption potential** is the hardest to verify in a demo — ask vendors for references who will share actual login-rate data, not satisfaction scores. **Integration breadth** matters most if your organization has established SharePoint document libraries: a platform that federates search across SharePoint, Google Drive, Box, and Dropbox lets you preserve those investments rather than forcing a full migration. **AI-driven personalization** is increasingly a baseline expectation — four of the ten platforms below connect to major LLM providers for content curation and natural-language workflows. Use these four criteria as your shortlist filter before scheduling vendor demos. ## The 10 best SharePoint alternatives in 2026 ### 1. MangoApps MangoApps is built for organizations with significant frontline populations — shift workers, field teams, and distributed employees who don't have company email addresses and access work information from personal devices. Its platform combines content management, employee communication, engagement, training, and scheduling in a single mobile-first application. The [solutions/modern-intranet](/solutions/modern-intranet) page covers how the platform is structured for organizations migrating away from SharePoint. The integration model is what separates MangoApps from most alternatives: universal search across SharePoint, Google Drive, Box, and Dropbox means organizations can keep SharePoint document libraries where they work and replace the employee experience layer without committing to a full migration. MangoApps also connects to OpenAI, Gemini, Anthropic, and Azure OpenAI for AI-native content curation and personalization. It was recently evaluated in the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report), one of the more rigorous independent assessments of this category. **Best for:** Organizations with frontline and desk worker populations that need one platform; teams that want to preserve SharePoint document investments while modernizing the employee experience layer. ### 2. Beekeeper Beekeeper is a mobile-first employee app built specifically for shift workers — channel-based messaging, digital schedules, and task assignment in an interface designed for employees who've never used a corporate intranet. Onboarding friction is low because it doesn't require a company email address or VPN. Its constraint is scope. There's no native learning management system, no recognition module, and content management is thin. Organizations that want one platform to cover communications, training, and engagement will need third-party integrations for those gaps. **Best for:** Organizations whose primary need is shift communication and task coordination for frontline teams, and that are comfortable running a separate LMS alongside it. ### 3. Staffbase Staffbase is an employee communications platform that grew through acquisition to include community features, intranet capabilities, and newsletter creation. Its strength is polished editorial communication — branded content, campaign management, and multi-channel publishing for internal communications teams with sophisticated content operations. The acquisition history introduces some integration complexity. Components from different acquired products don't always feel unified, and some organizations report higher-than-expected configuration overhead when deploying the full platform. **Best for:** Communications-led organizations — mid-market companies with active internal comms functions — that want branded content delivery and editorial workflow built in. ### 4. Workvivo Workvivo is a social-layer employee engagement platform that Zoom acquired in 2023. It offers community feeds, recognition and rewards, a document repository, an employee directory, and advanced search alongside its social engagement core. For organizations already in the Zoom stack, Workvivo provides a natural engagement layer without a separate vendor relationship. Workvivo's primary audience is desk workers. Its mobile capabilities are present but secondary to the desktop experience, which limits its adoption potential for frontline-heavy organizations. **Best for:** Zoom-invested organizations that want an employee engagement and communication layer tightly coupled to their existing collaboration infrastructure. ### 5. LumApps LumApps is an enterprise intranet platform with deep integrations into Google Workspace and Microsoft 365. For organizations running either ecosystem, it can serve as the content and communication layer that surfaces information where employees already work, without requiring a behavioral shift to a new tool. Per Emergence Capital, 80% of the global workforce is deskless, and LumApps's frontline and mobile capabilities are limited relative to platforms built mobile-first. Organizations with significant frontline populations will find adoption potential constrained for that segment. **Best for:** Desk-worker-heavy enterprises running Google Workspace or Microsoft 365 that need a tightly integrated intranet layer. ### 6. Unily Unily is a premium enterprise intranet platform with some of the most sophisticated AI content curation and natural-language configuration tooling in this category. Its personalization capabilities are technically mature, and its product roadmap has moved quickly toward AI-native features. The tradeoff is cost and complexity. Unily is more expensive than most alternatives on this list, and organizations with specific structural needs often require implementation partners to realize full value. That profile positions it clearly toward large enterprises with dedicated IT and communications budgets. **Best for:** Large enterprises with premium tooling budgets and dedicated implementation resources that need the most sophisticated AI-curated content experience available. ### 7. Interact Interact is an intranet platform built around social and collaborative capabilities — staff directories, targeted newsletters, knowledge bases, and employee forums. Its design philosophy is participatory rather than broadcast: built to make employees contributors, not just recipients. Native task management is absent, which limits Interact for organizations that need operational workflow features alongside communications. Content management is a more recent addition and not yet as deep as the social layer. **Best for:** Organizations where the primary need is breaking down communication silos and building community culture — not operational workflow or document management depth. ### 8. Igloo Igloo provides a customizable digital workplace built around communication, culture, and knowledge sharing, with flexible information architecture that lets organizations build tailored environments rather than adopting a fixed structure. Its flexibility is a genuine strength for teams with specific structural requirements. Onboarding and training capabilities are thin natively. Organizations that need a robust LMS built into the platform will need to integrate a third-party system, which adds vendor complexity and can fragment the new-hire experience. **Best for:** Organizations that need maximum structural flexibility and are comfortable managing training and onboarding through a separate platform. ### 9. Simpplr Simpplr is a modern intranet with an AI-powered personalized news feed and targeted employee communication tools. Its interface is designed to reduce information overload — the problem that makes many intranets feel like noise rather than signal — and its administrator onboarding experience is faster than most enterprise alternatives. Task management, scheduling, and advanced collaboration features are limited or absent natively. Simpplr is a strong communications layer; it's a thinner operational platform. **Best for:** Organizations prioritizing personalized content delivery and communications clarity, particularly for desk workers currently ignoring an overpopulated intranet. ### 10. Happeo Happeo is a Google Workspace-native digital workplace platform for small and mid-sized organizations. Its Pages product functions as a structured intranet layer; its Channels product provides team communication on top of Google's infrastructure. For organizations already running Google Workspace, integration friction is minimal and time-to-value is fast. For organizations outside the Google ecosystem, Happeo's value proposition narrows significantly. Feature depth in frontline access, task management, and recognition is lighter than most alternatives on this list. **Best for:** Small to mid-sized organizations already running Google Workspace that want a structured intranet without significant implementation overhead. ## Three questions that narrow your shortlist Most organizations that choose the wrong SharePoint alternative do so by evaluating on a feature checklist rather than on fit with how their workforce actually works. These three questions map directly to the criteria that predict adoption success. **Is your workforce primarily frontline, desk-based, or mixed?** Frontline-first organizations — retail, healthcare, manufacturing, logistics — should weight mobile-first access, offline capability, and shift communication features heavily. Beekeeper, MangoApps, and Workvivo are the most frequently cited options for this use case. Desk-worker-heavy organizations have more latitude and can weight content management depth, integration breadth, and AI personalization more heavily — where LumApps, Unily, and Simpplr compete most directly. Mixed organizations need a platform that genuinely serves both audiences from a single login; the [solutions/employee-app](/solutions/employee-app) page covers how MangoApps handles this specifically. **Do you need SharePoint to stay, or does it have to go?** If your organization has established SharePoint document libraries that can't be cleanly migrated, prioritize platforms that federate search across SharePoint rather than requiring a full rip-and-replace. If a clean transition is feasible, that constraint drops out of your evaluation entirely and you have more options on price and implementation timeline. **What is your tolerance for implementation complexity?** Platforms requiring partner-led implementation — Unily and LumApps at enterprise scale — deliver more sophisticated outcomes but need more runway, often six to twelve months before meaningful adoption. Platforms designed for faster deployment — MangoApps, Staffbase, Simpplr — can demonstrate value within weeks, which matters if you're replacing something that's already failing. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) includes benchmarks on rollout timelines and adoption metrics that can help frame an internal business case. ## What successful adoption actually requires Choosing the right platform is necessary but not sufficient. Per Social Edge Consulting, 91% of organizations already have an intranet — the adoption gap is the problem, not the technology gap. Before committing to any vendor, ask for customer references who will share actual login-rate data: monthly active users as a percentage of the workforce, and how that number changed in the first twelve months after launch. Platforms confident in their adoption story will have that data. Those that aren't will offer satisfaction scores instead. The decision criterion that ultimately matters isn't which platform has the most features. It's which one your employees will actually use — because a platform that 87% of your workforce ignores, regardless of how capable it is, delivers the same outcome as no platform at all. --- # Why On-Premise Enterprise Social Networks are the Top Choice for Companies **Author:** patricka **Published:** 2012-12-05 **Category:** enterprise-social-networking Recent AIIM surveys have shed light on enterprise preferences between cloud and on-premise social networks. Their findings might redefine your expectations. The AIIM’s “Social in the Flow” report, derived from a survey of its 65,000 members in October, reveals that enterprise social network adoption is soaring. An impressive 78% of surveyed companies are in the […] # Why On-Premise Enterprise Social Networks are the Top Choice for Companies The enterprise social network market has reached a strange consensus: every serious vendor now claims their platform is "secure by default," yet security remains the primary selection criterion for 73% of enterprise buyers, per AIIM research. Two IT directors can both cite security as their top priority, choose entirely different deployment architectures, and both reach defensible conclusions — depending on what their organization actually needs from the platform. Per Social Edge Consulting, 91% of organizations currently operate an intranet. Nearly a third of employees never log in at all. Only 13% use one daily. Per SWOOP Analytics, the average employee spends six minutes per day using intranet tools. These numbers appear across cloud and on-premise deployments alike. They don't describe a security failure — they describe an adoption failure that a security-first deployment decision alone cannot fix. This is what makes the on-premise vs. cloud decision harder than vendor comparisons suggest: the question isn't which architecture is more secure in principle. It's which architecture will be secure enough for your data and accessible enough for your entire workforce — including, per Emergence Capital, the 80% who are deskless — to actually use. Those are two different questions that most deployment evaluations never separate. ## What "secure intranet" means in regulated industries For healthcare systems, financial institutions, and government contractors, data isolation is not a preference — it is a compliance requirement. Enterprise social networks in these sectors carry HR records, financial communications, IP-sensitive project data, and personnel files that regulatory frameworks require to be physically or logically isolated from other organizations' data. Modern on-premise and single-tenant private cloud deployments support SAML 2.0, OAuth 2.0, Active Directory, LDAP, and custom SSO configurations. These are the access controls regulated industries use to satisfy audit requirements and minimize breach exposure. Multi-tenant SaaS platforms often cannot match the configuration granularity these controls require — particularly for organizations that need to verify exactly where their data lives and who has physical access to the infrastructure running it. The competitive landscape has shifted meaningfully. Five vendors now explicitly market "secure by default" architectures as a primary differentiator. In several cases, that phrase describes encrypted multi-tenant storage rather than physical or logical data isolation. Organizations evaluating vendor security claims should verify whether "secure by default" means single-tenant isolation or simply encryption at rest in a shared environment. For regulated industries, that distinction is the difference between a compliant deployment and a compliance risk. ## The deployment spectrum most evaluations treat as binary On-premise vs. cloud is better understood as a spectrum — on-premise → single-tenant private cloud → multi-tenant SaaS — rather than a binary choice. Each position on that spectrum trades security control for operational simplicity, at a different total cost. A conservative total cost of ownership for a 1,000-user enterprise intranet runs $130,000–$426,000 in year one, depending on deployment model, integration complexity, and governance requirements (Awesome Technologies Inc., 2025 cost model). The range reflects what vendor licensing fees don't cover: identity provider integration, content governance workflows, audience targeting, and HRIS connections that automate employee provisioning. Deployments that don't establish these integrations at launch routinely cost more to fix retroactively than they would have to implement correctly from the start. Single-tenant private cloud deserves particular attention as a practical middle path. It provides data isolation comparable to on-premise while transferring infrastructure management to the vendor. For organizations without a dedicated IT team to manage physical servers and upgrade cycles, private cloud achieves the same security outcome with substantially lower operational overhead. The [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) benchmarks where current vendors fall on this deployment spectrum — useful context for organizations that need to verify vendor claims against independent analysis before committing to an architecture. ## The frontline access problem on-premise architectures must explicitly solve On-premise intranet architectures assume employees have corporate email addresses, provisioned devices, and reliable VPN access. Per Emergence Capital, 80% of the global workforce is deskless — warehouse associates, clinical workers, field technicians, and retail staff who typically have none of these. This is not a disqualifying limitation of on-premise deployment, but it is a design decision that must be made explicitly rather than discovered after go-live. An on-premise deployment that cannot extend secure, authenticated access to mobile-first frontline workers concedes practical reach to cloud-native alternatives regardless of its security architecture advantage. A workforce that cannot access the intranet doesn't benefit from its security controls. Per IDC, employees spend 2.5 hours per day searching for information across fragmented systems — and that gap doesn't close for frontline workers when the intranet requires a VPN they've never been provisioned. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) documents how leading internal communications teams are redesigning access architecture — shifting to phone-number provisioning and QR-code authentication that doesn't require a corporate email address or VPN — and how successful on-premise deployments are incorporating these access patterns rather than treating them as cloud-only capabilities. The employee app layer that bridges on-premise infrastructure to frontline devices is increasingly the variable that separates high-adoption enterprise deployments from underutilized ones. ## AI-powered features and the on-premise misconception The most persistent misconception about on-premise enterprise social networks: that choosing on-premise means forgoing AI-powered intranet features. This perception has real market consequences. Competitors are actively using AI capability as a cloud-adoption argument, implying that organizations that want AI-assisted search, content surfacing, and employee self-service must accept multi-tenant data storage. Modern on-premise and private-cloud deployments can integrate AI assistants from OpenAI, Gemini, Anthropic, and Azure OpenAI. The critical distinction is data handling: these integrations can be architected so that company data used to train or contextualize AI responses remains within the organization's own environment, rather than passing through shared third-party infrastructure. For organizations in regulated industries, the architecture answer to "how do we get AI-native intranet capability while maintaining data isolation" is the same as the security architecture answer: isolate the data, connect the model at the boundary. The on-premise AI integration argument directly counters the cloud-native vendor positioning that is currently the most aggressive competitive message in the intranet market. Organizations evaluating this question should require vendors to demonstrate, not just claim, that AI capabilities function correctly within an isolated deployment. ## Integration as the primary driver of daily intranet use Per AIIM's research, 83% of enterprise social network buyers identify integration with existing business processes as a critical requirement — and integration is the primary variable determining whether employees use the intranet daily or ignore it entirely. A [modern intranet](/solutions/modern-intranet) that connects to HRIS systems provisions employees into correct audience segments automatically from day one. New hires reach the right distribution groups without a manual process; role changes update audience memberships in real time; departing employees are removed without a ticket to IT. Without that integration, communications go to stale audiences, new employees miss time-sensitive information in their first weeks, and the manual overhead of audience management consumes time that should be spent on content. Per IDC's 2.5-hours-per-day information-search finding, the integration gap is where on-premise deployments either prove or lose their ROI case. Organizations running phased rollouts — starting with departmental or project-specific pilots before company-wide deployment — consistently validate SSO, Active Directory, and document management integrations in the pilot phase. The AIIM data reflects this pattern: 19% of deploying organizations start departmentally, 29% start with project-specific deployments, and both groups report lower adoption risk than those that deploy company-wide without integration validation first. ## Acknowledging the genuine trade-offs Honest evaluation of on-premise deployment requires naming what it costs. Upfront infrastructure investment, longer initial setup timelines, and ongoing maintenance burdens fall on internal IT teams. Upgrades and capacity scaling that cloud deployments handle automatically become internal responsibilities. For smaller organizations or those without dedicated infrastructure capacity, multi-tenant SaaS may deliver faster time-to-value even where it involves some security trade-offs. The decision framework that resolves this starts with a data classification exercise: which data in your organization requires physical or logical isolation, and which doesn't? HR records, IP-sensitive files, financial communications, and personnel data typically warrant stricter controls than general project collaboration or company announcements. That distinction often reveals that a hybrid approach — on-premise or private cloud for sensitive workloads, SaaS for lower-sensitivity communication — is more practical than forcing every use case into a single architecture. On-premise or single-tenant private cloud is appropriate when: regulatory or contractual requirements mandate data isolation; internal IT capacity can manage infrastructure and upgrades; and sensitive data categories will regularly flow through the platform. Multi-tenant SaaS is appropriate when IT overhead is a binding constraint, time-to-deployment is critical, or the workforce is primarily cloud-native without sensitive data mandates. ## The deployment decision that workforce reach determines Per the [Gallup 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), employee engagement correlates directly with whether workers feel informed and connected to their organization. The enterprise social network is one of the primary mechanisms for that connection — but only for employees who actually use it. The on-premise argument is strongest when three conditions hold simultaneously: the security requirement is genuine and regulatory, the IT capacity exists to manage infrastructure, and the access architecture has been designed to reach every employee — including the 80% without corporate-provisioned devices. Organizations where all three conditions hold don't need to compromise on security or AI capability to deploy on-premise. Those where one or more conditions don't hold should evaluate single-tenant private cloud or hybrid architectures against the same criteria before defaulting to multi-tenant SaaS. The deployment model is a means, not an outcome. The outcome is an intranet that closes the 2.5-hour daily information search gap (per IDC), reaches frontline and knowledge workers through access patterns they'll actually use, and integrates with the systems that make content relevant to each employee's role and location. Security is a necessary condition for that outcome in regulated industries. It isn't a sufficient one on its own. --- # 4 Keys to Successful Project Management and Team Collaboration **Author:** anup **Published:** 2012-12-03 **Category:** team-collaboration How often do you find yourself sitting in meetings for the better part of the workday, only to find that you have made very little progress on pending projects?  Face to face meetings certainly have value but what if your team is spread between buildings, cities, states or even countries?  How can you effectively communicate […] # 4 Keys to Successful Project Management and Team Collaboration Project management works when everyone involved can answer three questions without attending a meeting: what needs to happen, who owns it, and what is blocking progress. When those answers live in someone's inbox or surface only at a weekly standup, projects slow down — not because the team lacks capability, but because coordination overhead consumes the time execution requires. Four disciplines separate teams that execute consistently from those that don't: transparent goal alignment, real-time communication built for distributed teams, task ownership without micromanagement, and automated workflows that remove manual handoffs. According to Gallup, approximately 60 million full-time working Americans — about half the US workforce — can work remotely at least part of the time, which means most organizations are already managing distributed project work whether they've designed for it or not. This article covers how each of the four keys works in practice, what makes it break down, and how to apply it in the kinds of distributed, cross-functional environments most teams operate in today. --- ## Why coordination fails — and how these four keys fix it Most project failures aren't caused by unclear strategy or insufficient effort. They're caused by information gaps: a deadline missed because the dependency wasn't visible, a decision that reached the wrong people two days late, a task that slipped because no one knew it was blocked. A Ladders analysis estimated that one-quarter of professional jobs in the US and Canada were expected to be remote by the end of 2023. Teams operating across locations, shifts, and time zones have less organic visibility into each other's progress — which means the coordination structures that work informally in a single-location office fail when applied to a distributed one. Project managers compensate by adding meetings, check-ins, and status emails — all of which increase coordination overhead without solving the underlying visibility gap. The four keys work because they replace informal, proximity-based coordination with structures that function regardless of where people are located or what hours they work. --- ## Key 1: Transparent goal alignment across the project Goal clarity at the project level is not the same as goal clarity for every individual contributor. A project manager may understand that the Q2 launch has a hard dependency on documentation finishing before the engineering freeze — but if the person writing the documentation doesn't know their section is blocking three downstream deliverables, that connection is invisible to them. The fix is about information architecture, not culture. Goals, milestones, and dependencies need to live somewhere every contributor can see how their work connects to the whole. When [goals management](/key-features/goals-management) infrastructure exists — a shared location for project objectives, current status, and dependency maps — team members can self-orient without a status meeting. Managers spend less time sourcing information and more time removing blockers. The immediate operational test: can a team member who just returned from two days out answer "what is the current project status and what is blocking us" in five minutes or less, without calling anyone? If the answer is no, the goal alignment infrastructure isn't working. --- ## Key 2: Real-time communication for distributed teams Instant messaging as a coordination tool solves a specific problem that email doesn't: keeping communication attached to the work it's about. A conversation threaded to a task or project is searchable, visible to the right people, and doesn't require anyone to be copied correctly on a forwarded chain. For distributed teams, the communication infrastructure also needs to account for access. Workers who don't sit at a desk — retail associates, field technicians, warehouse crews, clinical staff — need the same communication access as office employees. When the project coordination system only works at a desktop, a significant portion of the workforce effectively can't participate. This creates a two-tier project environment where frontline contributors learn about changes after the fact. According to [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace), employee engagement is directly linked to whether workers feel informed and heard — a condition that requires infrastructure, not just good intentions. Real-time communication tools close the loop between those giving direction and those doing the work, regardless of where work happens. --- ## Key 3: Task ownership that doesn't require micromanagement Micromanagement is usually a symptom of a visibility problem. When a manager can't see whether a task is in progress, blocked, or completed without asking, their only tool for maintaining awareness is asking. The ask interrupts the person being asked, creates friction, and degrades the working relationship — even when the underlying coordination need is legitimate. Structured [task management](/solutions/task-management) shifts this dynamic by making task status observable without manual reporting. When a task has a clear owner, a due date, a dependency map, and a status field the assignee updates in place, anyone watching the project can see progress in real time. The manager's role shifts from status collector to blocker remover. For shift-based environments, the compound benefit appears at handoff points. The incoming shift knows what was completed, what's in progress, and what is blocked — before sending a single message. This eliminates a significant category of coordination errors in manufacturing, healthcare, and logistics environments where shift continuity is a daily operational requirement. --- ## Key 4: Automated workflows that remove manual handoffs Manual coordination — tracking who has approved what, following up on outstanding requests, re-routing items that went to the wrong person — is the invisible overhead inside most project management processes. According to a Forrester Report, a unified platform can deliver $7.5 million in three-year added value for a company of 20,000 employees; a significant portion of that figure comes from eliminating time spent on manual coordination steps. No-code [workflow automation](/key-features/trackers-workflows) routes approvals, escalations, and task assignments based on configurable rules rather than manual oversight. An approval that previously required a manager to notice, remember, and forward can route automatically based on team, project type, or cost threshold. Recurring checklists for shift handoffs, safety inspections, or onboarding sequences run without someone creating them each time. The categories that benefit most are consistent across industries: approval routing, status notifications, recurring task creation, and exception escalation. Process audits routinely surface these same four categories as the highest-volume manual coordination activities. These are the right places to start — and they typically produce visible time savings within the first month of deployment. --- ## Mobile access for workers without a desk Traditional project management platforms are built for desktop access — corporate email, VPN access, a company-managed device. For office employees, these barriers are low. For teams in manufacturing, healthcare, retail, logistics, and field services, where a desktop computer is intermittent or absent, these requirements create a structural exclusion: the coordination system exists, but the workers most affected by coordination gaps can't reliably access it. Mobile-first project access removes that barrier. Workers can see their assigned tasks, update status, and communicate with their teams from a personal device on a break or before a shift. Onboarding speed improves directly: new hires who can review task assignments and project context from a mobile device before their first full shift reach competency faster than those waiting for a scheduled classroom orientation. The organizations that achieve high adoption of digital project tools are consistently the ones that removed the login barriers — not the ones with the most feature-complete platforms. --- ## What to look for when evaluating project management tools Most project management tools solve the visibility problem for office workers. The gaps appear when the environment doesn't match the platform's default assumptions. Teams with frontline or field workers should evaluate whether the platform works on a personal mobile device without a corporate email or VPN requirement. Shift-based operations need to confirm that task handoffs are visible across shift boundaries — not just within a single user's active session. Organizations with complex approval chains need to verify that workflow automation is genuinely no-code, not a developer-configuration project marketed as self-service. The right questions for any product evaluation: Can a warehouse supervisor update task status from the floor without opening a laptop? Can a new hire see their project assignments before their first full shift? Can an operations manager configure an approval routing rule without filing an IT ticket? The answers reveal whether a platform supports teamwork management across the full workforce or only the portion that sits at a desk. --- ## Measuring whether the four keys are working Track outcomes, not activity. Task creation counts and login rates confirm the system is being used — they don't confirm that coordination is improving. Three outcome metrics worth tracking from deployment: time from task assignment to completion (compared against a pre-deployment baseline), manager escalation and follow-up frequency (if managers are asking fewer status questions, the visibility infrastructure is working), and cross-location handoff error rates (for shift-based or distributed teams, errors originating at handoff points should decline within the first three months). The shift from meeting-heavy, email-dependent project coordination to structured, visible, partly automated workflows doesn't happen from a single tool purchase. It happens from applying these four disciplines consistently — and measuring the right outcomes to know whether they're taking hold. Organizations that get this right don't just complete projects faster; they build the operational discipline that prevents coordination failures from accumulating in the first place. --- # 5 Ways To Keep Tasks Moving Forward **Author:** Luke Walton **Published:** 2011-01-07 **Category:** integrated-digital-workplace Streamlining tasks is the best way to keep tasks moving forward and progressing on a day to day basis.  Instead of thinking of tasks like pages of disjointed items, web task management can help you achieve a strong and steady flow to task management.  Web task management software offers your business access to task management […] # 5 Ways to Keep Tasks Moving Forward (and What to Do When They Stall) Keeping work moving through a team is harder than it looks. Tasks get created, assigned, and then quietly stall — waiting on a decision, a file, or a follow-up that never comes. According to Gallup.com, approximately 60 million full-time working Americans, about half the US workforce, can work remotely at least part of the time, which means the coordination gaps that slow tasks down are no longer confined to a single office floor. They span time zones, devices, and communication channels. This article covers five concrete ways to keep tasks progressing day to day, with practical guidance on what to do when each approach breaks down — so you don't have to go looking for answers elsewhere. --- ## 1. Create Tasks Quickly and Completely A task that takes too long to create often doesn't get created at all. Effective [task management](/solutions/task-management) means being able to capture a task — for yourself, a colleague, or a group — in seconds, with enough detail that the assignee can act without a follow-up conversation. That includes a clear description, a due date, and an owner. ### What to do when tasks are too vague to act on Vague tasks are one of the most common reasons work stalls. If a task description reads "follow up on vendor contract," the assignee has to do investigative work before doing actual work. A better pattern: - **Break large tasks into subtasks** with individual owners and due dates. - **Attach relevant files or links** at creation time, not after the first question comes in. - **Set a priority level** (high / medium / low) so assignees know what to tackle first when their queue fills up. Task privacy settings also matter here. Some tasks involve sensitive decisions or personnel matters. Keeping those visible only to the assigner and assignee prevents confusion and keeps the broader feed clean. --- ## 2. Convert Conversations Into Assigned Work Good ideas surface in comments, messages, and discussion threads — and then disappear. One of the most practical ways to keep tasks moving is to close the gap between where ideas are discussed and where work gets assigned. When a conversation in a project feed produces a clear action item, that item should become a task immediately, not a mental note. Promoting a comment or thread segment into a formal task — with an owner and a due date — turns discussion into accountable work. ### How to prevent ideas from falling through the cracks This is especially relevant for distributed teams. According to Ladders, one-quarter of all professional jobs in the US and Canada were expected to be remote by end of 2023, which means the hallway conversation where someone says "let's do that" no longer exists for a large share of the workforce. The feed *is* the hallway. Practical steps: - **Review open discussion threads at the end of each week** and convert any unresolved action items into tasks. - **Tag the person responsible** in the task at creation time so there's no ambiguity about ownership. - **Use real-time activity feeds as an accountability mechanism**, not just a notification stream — a timestamped record of who said what and when is a lightweight audit trail. --- ## 3. Give Everyone a Single View of Active Work Tasks stall when people don't know what they're responsible for, or when managers can't see what's blocked. A centralized task view — one that shows not just your own tasks but every task and project you have involvement in — eliminates the "I didn't know that was on me" problem. Project [workspaces](/key-features/workspaces) that co-locate tasks, files, discussions, and milestones in one place reduce context switching. When an assignee has to open four different tools to find the file attached to a task, the task slows down. When everything lives in one place, the friction disappears. ### What metrics show tasks are actually moving A visible task board is only useful if you know what "healthy" looks like. Concrete benchmarks to track: - **Completion rate by due date**: What percentage of tasks are closed on or before their deadline? - **Average time-in-status**: How long does a task sit in "In Progress" before it moves? - **Blocker frequency**: How often do tasks get flagged as blocked, and what's the average resolution time? At scale, these numbers matter. A 75% platform adoption rate across 12,000 users at a single franchise organization shows what sustained task engagement looks like when the tool is embedded in daily work — not treated as an optional add-on. --- ## 4. Automate the Hand-offs That Stall Tasks One of the most common failure modes in task management is the manual follow-up. A task is completed, but the next step doesn't start because someone forgot to notify the next person, or because the approval request is sitting in an inbox. This is where manual operations create unnecessary delays — and where automation closes the gap. Failed or blocked tasks can automatically trigger corrective actions and reassignments without manual manager intervention. No-code forms and approval routing let non-technical team members automate recurring request workflows without IT involvement — a pattern that four competitors now surface prominently on operations-focused pages. This is the difference between an [operations manual](/key-features/trackers-workflows) that describes what *should* happen and a system that enforces it. ### How to identify which hand-offs to automate first Not every workflow needs automation. Start with: 1. **Recurring requests** that follow the same approval path every time (expense approvals, shift change requests, content sign-offs). 2. **Tasks with a consistent "done means start the next thing" pattern** — onboarding steps, compliance checklists, SOP operations that repeat across locations or teams. 3. **High-volume, low-complexity tasks** where manual routing creates a bottleneck but the logic is simple enough to encode in a form. Examples of lean operations in practice: a retail chain that automates store-opening checklists so that a missed step triggers an automatic reassignment rather than a missed task. A healthcare team that routes shift-change handoff notes through an approval workflow rather than relying on verbal confirmation. These aren't edge cases — they're the daily reality for distributed operations teams. --- ## 5. Keep Remote and Distributed Teams in Sync Geography used to be a footnote in task management discussions. It isn't anymore. When team members are spread across locations, shifts, or time zones, the coordination overhead for keeping tasks moving increases significantly. A task that would take one conversation to unblock in a shared office can sit for 24 hours waiting for an async reply. Chat and instant messaging features help, but they're not sufficient on their own. The task itself needs to carry enough context — status, history, attached files, comments — that any team member can pick it up and understand where it stands without a briefing. ### How to handle blockers on distributed teams Blockers are the leading cause of task stagnation on remote teams. A practical protocol: - **Flag blockers explicitly in the task**, not just in a side conversation. If the blocker lives in a chat thread, it's invisible to anyone who joins the task later. - **Set a blocker resolution deadline** — if a blocker isn't resolved within 48 hours, escalate automatically or reassign. - **Use the task's activity feed as an audit trail**: timestamped comments showing who flagged the blocker, who was notified, and when it was resolved create accountability without requiring a status meeting. Task tools that unite team members across physical and geographical boundaries — and that log the history of every change — give managers the visibility they need to intervene before a blocked task becomes a missed deadline. --- ## How to Prioritize When Everything Feels Urgent One of the most common follow-up questions after setting up a task system is: *how do I decide what to work on first?* A few frameworks that work in practice: - **Impact vs. effort matrix**: Plot tasks on a 2x2 grid. High-impact, low-effort tasks go first. High-effort, low-impact tasks get deprioritized or dropped. - **Deadline-driven sequencing**: Sort by due date, but flag tasks whose completion unblocks other tasks — those get elevated regardless of their own deadline. - **[Goals management](/key-features/goals-management) alignment**: Tasks that connect directly to a team or organizational goal should carry higher weight than tasks that don't map to any stated priority. A [to-do list](/key-features/to-do-list) that's organized by priority — not just by creation date — is the difference between a team that's busy and a team that's making progress. --- ## What Good Task Management Looks Like at Scale The five approaches above work at the individual and small-team level. At scale — across thousands of users, dozens of locations, or multiple business units — the requirements shift. Adoption becomes the constraint, not capability. A concrete benchmark: 10 daily app opens per user is a measurable signal that task tools are embedded in daily work habits rather than used occasionally. When users open a task tool that infrequently, tasks get missed, status updates lag, and the system loses credibility as a source of truth. For organizations evaluating whether their current approach is working, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how operations teams are structuring task accountability at scale — including what separates teams with high task completion rates from those that struggle with chronic backlog. --- ## The Bottom Line Tasks stall for predictable reasons: vague descriptions, missing owners, manual hand-offs, blocked steps with no escalation path, and distributed teams without a shared view of what's in progress. Each of the five approaches above addresses one of those failure modes directly. The practical starting point: audit your current task backlog for the most common stall pattern. If most tasks are stalling at the hand-off stage, automation is the highest-leverage fix. If tasks are stalling because of vague descriptions, the fix is at creation time. If distributed teams are the constraint, the fix is in how context is attached to the task itself — not in adding more meetings. For a closer look at how MangoApps structures task management, workflow automation, and team accountability in a single platform, the [solutions/task-management](/solutions/task-management) page covers the full feature set with specific use cases by team type. --- # Creating A Foundation For Efficient Business Workflow **Author:** Luke Walton **Published:** 2011-01-06 **Category:** workplace-productivity Creating an efficient business workflow is at the core of streamlining your the way your company operates.  Web task management is one way to help you create a foundation for an efficient workflow.  When used to its potential, task management software allows you to create and manage an efficient business workflow, while maintaining a workforce […] # Creating a Foundation for Efficient Business Workflow The workflow advice that fills most management guides starts from a false assumption: that every employee has a desk, a company laptop, and a corporate email address. For organizations where a significant share of the workforce operates in a warehouse, on a retail floor, or in the field, that assumption doesn't just miss the point — it actively builds the disconnection it claims to solve. Per McKinsey research, 89% of frontline workers say they will stay with their companies if leaders listen to their feedback. Workflow systems that exclude those workers from the start can't capture that feedback, let alone act on it. The foundation problem isn't that organizations lack task management software. It's that most task management software was built for a subset of the workforce — and the metrics that result reflect exactly that. This article covers what a workflow foundation actually requires: not as a feature checklist, but as a set of structural decisions that determine whether the system reaches the whole organization or just the employees who already have a desk. ## Why workflow systems fail before they start The most common failure mode in workflow implementation isn't poor adoption of a well-designed system. It's building a system with a structural access problem and then optimizing around the edges when the adoption numbers come in low. A workflow tool that requires corporate email enrollment, VPN access, or IT provisioning for each user will reach knowledge workers and leave frontline employees working through informal channels — group texts, shift handoff notes, verbal instructions passed face to face. The formal system shows clean data. The actual work is happening somewhere else. This is the access problem that makes frontline worker inclusion in workflow systems the most consequential operational gap in enterprise organizations today. Organizations that don't address it structurally will run the same adoption analysis in twelve months and find the same numbers, regardless of how well-designed the interface is or how much time was spent on the change management campaign at launch. ## Task clarity for every employee, not just desk-based ones The starting point for any efficient workflow is a single place where employees can see what they are responsible for, access the documents they need, and understand how their work connects to broader team goals. Without this, employees spend time reconstructing context instead of doing work. A [task management solution](/solutions/task-management) that reaches a warehouse associate on a personal mobile device without IT provisioning is architecturally different from one that requires a browser session on a company laptop. The former closes the access gap. The latter preserves it while appearing to solve it. The distinction only becomes visible when adoption rates come in — by then, the contract is signed. The structural question to ask before evaluating any platform: does this system reach every employee who needs task clarity, or does it require a device or a credential they don't have? If the answer is the latter, the coverage gap is a design choice, not a configuration problem. ## Real-time collaboration that reaches the floor Real-time team collaboration only delivers value if everyone who needs to collaborate can actually access it. Workflow platforms that reach frontline workers without requiring corporate email or VPN access eliminate a structural bottleneck that desk-first tools cannot solve. This is the mechanism behind OU Health's 87% workforce engagement within months of launching a unified employee app for clinical staff. Those employees could reach the platform from a device they already carried, without credentials they didn't have. The outcome wasn't a communications campaign result. It was a structural access change that showed up in the engagement data — because the system finally included the people who were previously outside it. The [Raley's Companies case study](/resources/raleys-case-study) documents the same pattern at scale. Connecting 20,000 employees — many of them in stores, on floors, and in distribution centers — required a platform that didn't treat desk access as the default starting condition. When the platform reached those employees on their own devices, the engagement metrics followed. ## Automation that removes managers from routine decisions One of the most overlooked efficiency levers in workflow design is removing the human bottleneck from decisions that policy has already made. No-code workflow automation handles shift swapping, PTO requests, and routine task approvals without IT involvement — which means managers stop being the queue for decisions they've already encoded into rules. The practical result is faster answers at the point of need and a workflow system that employees use voluntarily rather than work around. [Trackers and workflow automation](/key-features/trackers-workflows) that let operations teams build approval chains, escalation rules, and status tracking without writing code convert a policy document into a system that runs consistently without supervision. The follow-up question that most implementations miss: can frontline employees access the automation on a mobile device, mid-shift, without involving a manager? If not, the automation benefit is concentrated among knowledge workers — and the efficiency gain is smaller than the implementation cost suggests. ## Analytics that measure health, not just activity Knowing that a task was updated is different from knowing whether the right tasks are being completed at the right rate. Activity feeds answer what happened. Analytics answer whether this is working. Per McKinsey research, 81% of leading companies effectively use data and analytics tools. Workflow platforms that treat analytics as a first-class feature — tracking task completion rates, read receipts, and acknowledgment status — give managers objective health signals rather than a feed to scroll through after the fact. Per Unily research, only 24% of frontline workers feel their feedback from customer interactions is heard by leadership. Analytics that surface acknowledgment gaps — not just send confirmations — are how organizations close that gap in practice rather than in intention. Per Workday Peakon Employee Voice data, engagement metrics reveal warning signs on average nine months before employees leave. That lead time is only actionable if the workflow system is generating the signals that feed those metrics in real time, not after a quarterly survey cycle. ## Converting conversations into assigned work One of the most consistent workflow failures is the gap between a decision and an assigned task. Conversations happen, someone commits to following up, and nothing gets created with an owner or a deadline. Two weeks later, the same conversation happens again. Workflow systems that let teams promote a conversation or feed item directly into a task — with an owner, a deadline, and a notification that everyone involved can see — close this gap at the moment it opens. Everyone has the same context. There is no ambiguity about who owns what or when it is due. Per Enterprise Apps Today (2022), 60% of high-performing firms report increased performance when employees are recognized. Recognition features that live alongside task completion — rather than in a separate platform — let managers close the loop between work done and acknowledgment given without requiring employees to navigate a separate system. ## Integration that makes the existing stack work together A workflow platform that operates in isolation from payroll, HRIS, and learning management systems creates its own coordination overhead. Employees maintain parallel records, managers lose confidence in the data they see, and the workflow system becomes the source of truth for nothing — which erodes adoption faster than any UX problem. TeamHealth's consolidation of more than 200 enterprise systems into a single mobile workflow dashboard is the clearest case study on this point. That result is only possible when the workflow layer integrates with existing infrastructure rather than attempting to replace it. The goal is not to add another tool to the stack. It is to make the tools already in use work together through a single interface that employees can access from wherever they work. Per dormakaba's case study, the average SharePoint intranet deployment takes nine months. Organizations that need to move faster typically find the timeline compresses when the platform builds on existing integrations rather than requiring custom connector development for every system it needs to touch. ## What a working workflow foundation looks like in practice The clearest signal that a workflow foundation is working is whether managers spend their time on decisions or on coordination. If most of a manager's day involves chasing status updates, re-explaining priorities, or routing approvals that policy has already resolved, the system is not doing its job regardless of what the vendor's dashboard shows. Cosentino's 85% daily active user rate after deploying a unified internal communications and workflow platform is the practical benchmark. Daily return use is the honest measure of whether a system is useful — not the adoption rate at launch, which training and novelty effects consistently inflate. The platforms that generate 87% engagement at OU Health and 85% daily return use at Cosentino share one structural characteristic: they didn't assume the workforce was already at a desk. The audit questions that most organizations skip before platform selection are the same ones that explain post-deployment disappointment: who in the workforce is currently excluded from the formal workflow, which routine decisions still require a manager to resolve, and what health metrics will be tracked once the system is live. Defining those answers before evaluating platforms changes the evaluation entirely — because the access model becomes a filter, not an afterthought. ## Why frontline access is the workflow question most frameworks skip Efficient workflows and employee engagement are frequently managed as separate workstreams with separate owners. They are not separate problems. Workflow systems that exclude frontline workers from task clarity and real-time visibility don't just create operational gaps — they create the disengagement that shows up nine months before someone leaves, per Workday Peakon Employee Voice data. Closing the frontline access gap is not a technology project with a finite completion date. It is a structural decision about which employees the organization treats as participants in work rather than recipients of instructions. The platforms that make that structural change — reaching the warehouse associate, the retail floor team, the field technician on a personal device without IT provisioning — consistently produce the engagement and retention outcomes that desk-first tools cannot, regardless of how many features those tools have. For the performance management dimension of this question — how workflow data connects to the feedback conversations that actually move engagement scores — [Closing the Information Gap in Performance Reviews](/articles/closing-the-information-gap-in-performance-reviews) addresses the structural link between day-to-day workflow signals and the retention-predictive feedback loops that act on them before the nine-month window closes. --- # How To Move Business Projects Forward **Author:** Luke Walton **Published:** 2010-12-30 **Category:** workplace-productivity Projects and tasks are the core of what we as businesses produce, so it is absolutely crucial to have the right tools. Task management tools help businesses manage all of the details created within every task and project. At MangoApps, our goal is to find a way to help move your business projects forward. By […] # How To Move Business Projects Forward: Five Practical Methods That Work Moving business projects forward consistently requires more than good intentions — it requires the right structure, the right tools, and clear accountability at every step. Whether your team is distributed across time zones, working from a corporate office, or operating on a factory floor without a company email address, the same core challenge applies: keeping everyone aligned, informed, and unblocked. This article covers five concrete methods for advancing projects, explains why each one matters, and addresses the follow-up questions most managers have after implementing them. --- ## The Five Methods at a Glance 1. Use a structured online task manager with clear ownership 2. Enable mobile task access for every contributor, including frontline workers 3. Build real-time collaboration into the project workflow 4. Match tasks to expertise using searchable employee profiles 5. Replace recurring status meetings with asynchronous project updates Each method is covered in detail below. --- ## 1. Use a Structured Online Task Manager With Clear Ownership A [task management](/solutions/task-management) system does more than create a to-do list. It assigns ownership, sets deadlines, attaches supporting documents, and creates a visible record of progress that every stakeholder can check at any time. The practical benefit is accountability. When a task has a named owner, a due date, and a status field, the question "where does this stand?" has a factual answer rather than a conversational one. Teams that operate this way spend less time in coordination overhead and more time on execution. No-code workflow automation extends this further: shift swapping, PTO requests, and routine task approvals can be handled automatically without IT involvement, reducing the manual coordination burden on project leads (per Beekeeper product page research). Integrating task management with HRIS and payroll systems also eliminates manual data re-entry and keeps project staffing records in sync automatically (per Beekeeper product page research). For organizations managing [trackers and workflows](/key-features/trackers-workflows) across departments, a centralized task system also creates an auditable record — important for compliance-sensitive industries where proving that a communication was received matters as much as sending it. --- ## 2. Enable Mobile Task Access for Every Contributor, Including Frontline Workers Most task management articles assume every contributor has a desk and a company email address. That assumption excludes a significant portion of the workforce. Frontline and deskless employees — warehouse workers, retail associates, field technicians, healthcare aides — are often the people executing the tasks that move projects to completion. Assigning tasks to workers without company email or desktop access via a branded mobile app keeps frontline contributors inside the same project loop as desk-based teams (per MangoApps product page, frontline/mobile-first positioning). Without this, project managers receive incomplete status pictures and frontline workers feel disconnected from outcomes. Employee engagement is directly tied to this inclusion. According to McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback. A mobile-first task environment is one of the most direct ways to create that feedback loop — workers can flag blockers, request clarification, and confirm task completion from the same device they already carry. Read receipts and acknowledgment tracking on task updates create an auditable record of who has seen critical project communications, supporting compliance-sensitive workflows (per MangoApps product page, multi-channel communications). This matters in regulated industries where "I didn't see the update" is not an acceptable explanation for a missed step. --- ## 3. Build Real-Time Collaboration Into the Project Workflow Geographic distribution is no longer the exception — it is the norm. Real-time collaboration tools remove location as a constraint, but the more important shift is structural: collaboration should be embedded in the project workflow itself, not treated as a separate communication layer. Practical collaboration features that directly advance projects include: - **Instant messaging and chat** tied to specific tasks or workspaces, so context stays attached to the work - **Secure document sharing** with version control, so teams always work from the current file - **Activity feeds that convert to tasks**, so action items surfaced in discussion are captured immediately rather than lost in a chat thread - **Shared [workspaces](/key-features/workspaces)** that give cross-functional teams a single place to coordinate According to McKinsey research, 81% of leading companies effectively use data and analytics tools — and project collaboration platforms are increasingly part of that analytics infrastructure, providing visibility into where work is moving and where it is stalling. Only 24% of frontline workers feel their feedback from customer interactions is heard by leadership, per Unily research. Embedding collaboration tools into the task layer — rather than keeping them in a separate messaging app — is one way to close that gap, because feedback surfaces where decisions are actually being made. --- ## 4. Match Tasks to Expertise — and Surface Knowledge Mid-Task Assigning the right task to the right person is a prerequisite for project momentum. When tasks are mismatched to skills, rework accumulates and timelines slip. Searchable employee profiles solve part of this problem: project managers can review a colleague's documented experience before assigning work, rather than relying on institutional memory or org-chart proximity. All task assignments posted to an activity feed also notify the relevant team members in real time, reducing the lag between assignment and acknowledgment. The deeper opportunity is connecting task management to organizational knowledge. Workers who can surface relevant SOPs, policies, or prior project documentation without leaving the task tool move faster and make fewer errors. This is the practical value of AI-powered search within a project context: rather than switching to a separate intranet or document repository, employees get the information they need inside the workflow where they are already working. For organizations tracking [goals management](/key-features/goals-management) alongside task execution, linking individual task assignments to broader team or organizational goals also gives employees clearer line-of-sight into why their work matters — a factor consistently associated with higher employee engagement. --- ## 5. Replace Recurring Status Meetings With Asynchronous Project Updates Status meetings are expensive. A one-hour meeting with eight attendees costs eight hours of productive time, and the information exchanged is often available in the task management system already. Asynchronous project updates — status fields, comment threads, progress percentages, automated notifications — deliver the same information at a fraction of the cost. When a meeting does occur, it starts from a shared baseline of current information rather than spending the first twenty minutes establishing it. Recognition is a related lever. According to Enterprise Apps Today 2022, 60% of high-performing firms report increased performance when employees are recognized. Asynchronous project tools create natural moments for visible recognition: a completed milestone, a resolved blocker, a task delivered ahead of schedule — all of these are visible in the activity feed and can be acknowledged publicly without scheduling a meeting. According to Workday Peakon Employee Voice data, engagement metrics can reveal warning signs of employee departure up to nine months before someone leaves. Teams that use project tools with built-in engagement signals — participation rates, task completion trends, response times — can identify disengagement early and intervene before it becomes attrition. --- ## What Results Should You Expect? Organizations that deploy unified mobile project and communications platforms have reported 87% workforce engagement within a few months of launch. Separately, teams that consolidate project tools have reduced context-switching by bringing 200+ enterprise systems into a single mobile dashboard. One global workforce of 5,900 employees recorded 85% daily active users after deploying a unified internal communications and task platform. These outcomes are not guaranteed by any single tool, but they reflect what becomes possible when the five methods above are implemented together rather than in isolation. --- ## Frequently Asked Questions ### How do you keep frontline employees engaged in projects when they don't have desk access? The answer is mobile-first design combined with deliberate inclusion. Frontline workers need task assignments, status updates, and feedback channels that work on a personal or company-issued mobile device without requiring a corporate email login. Branded mobile apps with push notifications, read receipts, and simple acknowledgment flows are the most direct solution. The goal is to eliminate the two-tier project experience where desk workers have full visibility and frontline workers operate on delayed, incomplete information. ### How do you measure whether project communication is actually working? Open rates, read receipts, acknowledgment tracking, and task completion rates are the primary signals. If a critical update was sent but not acknowledged, the project manager knows to follow up before the gap becomes a missed deadline. This analytics layer is what separates a project communication tool from a simple messaging app — and it is increasingly important for compliance-driven industries where documentation of receipt matters. ### How does task management connect to broader employee engagement? Task clarity, recognition, and feedback loops are three of the most direct drivers of employee engagement at the work level. When employees know what they are responsible for, receive acknowledgment when they complete it, and can surface blockers without friction, engagement follows. [Closing the information gap in performance reviews](/articles/closing-the-information-gap-in-performance-reviews) is one downstream benefit: managers who have a task-level record of an employee's contributions can conduct more accurate, less biased reviews. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading organizations are connecting operational tools to engagement outcomes in more detail. --- ## The Bottom Line Moving business projects forward is a systems problem, not a motivation problem. The five methods above — structured task ownership, mobile access for all contributors, embedded real-time collaboration, expertise matching with knowledge access, and asynchronous status updates — address the structural causes of project stagnation. The organizations that execute these methods consistently share one characteristic: they treat project tools as infrastructure for the entire workforce, not just for desk-based employees. Frontline inclusion, analytics visibility, and workflow automation are not add-ons — they are the difference between a project management system that works on paper and one that works in practice. For a closer look at how these methods apply to [performance management](/solutions/performance-management) and continuous development, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) covers the intersection of operational tools and workforce outcomes in detail. --- # 3 Benefits From Increased Team Collaboration **Author:** Luke Walton **Published:** 2010-12-29 **Category:** company-collaboration When companies adopt a modern collaboration tool, it can lead to an increase in team collaboration. With these tools, your organization can take a more open and communication-driven approach to project management. The command and control culture that surrounds micro-managing task schedules only hinders your work environment. It is critical to use a collaboration tool […] ## 3 Benefits From Increased Team Collaboration When companies adopt a modern collaboration tool, it can lead to an increase in team collaboration. With these tools, your organization can take a more open and communication-driven approach to project management. The command and control culture that surrounds micro-managing task schedules only hinders your work environment. It is critical to use a collaboration tool to improve the way that your teams operate — and the payoff is measurable: per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback, a retention outcome that begins with giving every employee a visible voice in daily work. ### #1: Complete Visibility One of the biggest challenges project management software faces is that communication typically happens in a closed system. This means little to no interaction with the people that matter most. By taking a more collaborative approach, you can increase team collaboration across an entire project. When doing this, it is critical to keep everyone on the team informed. Work does not occur in a vacuum — all employees should be able to easily and efficiently collaborate. This visibility gap is especially acute for frontline and deskless workers who lack company email or dedicated desk access. Collaboration platforms that reach these employees close a structural blind spot that traditional project management tools cannot solve. AI-assisted search for policies and SOPs is also emerging as a practical accelerator here: when team members can instantly surface the right procedure without asking a manager, project momentum stays intact. Per Unily research, only 24% of frontline workers feel their feedback from customer interactions is heard by leadership — a number that drops further when visibility tools don't extend beyond the desk. Using [workspaces](/key-features/workspaces) to organize projects by team or function is one concrete way to make that visibility real for every contributor, regardless of where they work. ### #2: Team Member Accountability With greater visibility and increased team collaboration, team members are now fully aware of what their responsibilities are. They also gain more insight on how their work impacts others on the team. They have a newfound responsibility to ensure that what they deliver is just as important as meeting a deadline. Increased accountability has a contagious effect among team members as well and is easily spread to other project teams, within functional teams, and can even ripple throughout the entire organization. With a greater sense of awareness and responsibility, team members become more focused on the work they do and how it impacts and influences others. Read receipts and acknowledgment tracking on team communications create a measurable accountability layer beyond task assignment alone — a feature particularly valuable in compliance-sensitive environments. Automated no-code workflows for shift swaps, PTO requests, and routine approvals also reduce the coordination overhead that erodes team accountability over time. Structured [task management](/solutions/task-management) practices, combined with [trackers and workflows](/key-features/trackers-workflows) that automate routine handoffs, give teams a consistent accountability framework without adding administrative burden. ### #3: Culture Change With greater accountability and responsibility within a team, a cultural shift will naturally take place. The office and its teams will transition from the traditional command and control mentality to an open and inclusive culture built around increased team collaboration, sharing, and helping each other accomplish team goals. A collaborative approach to project and task management can help drive this culture change like very few other applications within a business. The culture shift is not just qualitative. Per Enterprise Apps Today 2022, 60% of high-performing firms report increased performance when employees are recognized — a signal that the cultural conditions collaboration creates translate directly into output. One organization achieved 87% workforce employee engagement within months of launching a branded employee app; another recorded 85% daily active users after platform launch across a 5,900-person global company. These outcomes suggest that culture change driven by collaboration tools is both real and trackable. For a deeper look at how engagement metrics surface early warning signs, the [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers how leading organizations are measuring this shift. ## MangoApps The workforce is changing. Project management software solutions need to evolve. Inviting increased team collaboration is a great first step in transforming the way your company operates. With MangoApps your employees can be equipped with the tools they need to easily communicate. This leads to greater productivity, higher efficiency, and a more positive work environment. To learn how MangoApps can help your organization increase team collaboration, please contact our sales team or schedule a demo. --- ## How Do You Measure Collaboration Improvement? Tracking collaboration improvement starts with the metrics that reflect actual behavior, not just tool adoption. Daily active users, message response times, task completion rates, and acknowledgment rates on critical communications all serve as leading indicators. Per Workday Peakon Employee Voice data, engagement metrics can reveal warning signs up to nine months before an employee leaves — meaning the measurement infrastructure you build around collaboration tools doubles as an early-retention signal. [Closing the Information Gap in Performance Reviews](/articles/closing-the-information-gap-in-performance-reviews) explores how to connect these behavioral signals to formal review cycles so that collaboration data informs development decisions, not just project dashboards. Per McKinsey research, 81% of leading companies effectively use data and analytics tools — applying that same discipline to teamwork management metrics is how collaboration gains become durable. ## What Practices Sustain a Collaborative Culture Long-Term? Sustaining a collaborative culture requires more than launching a platform. Employee engagement training, structured goal alignment, and regular feedback loops all reinforce the behavioral norms that collaboration tools enable. [Goals management](/key-features/goals-management) features that connect individual tasks to team objectives give employees a continuous line of sight between their daily work and broader outcomes — one of the most reliable drivers of sustained employee engagement. For organizations building or refreshing their approach, [Why Your Learning and Development Strategy Fails (and How to Fix It)](/articles/learning-and-development-strategy-embedded-in-daily-work) outlines how embedding learning into daily workflows — rather than separating it into standalone employee engagement courses — accelerates the cultural shift that collaboration initiatives aim to produce. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) also documents how leading organizations are structuring these practices for distributed and frontline teams. ## How Does Collaboration Scale Across Frontline and Remote Teams? Scaling collaboration beyond desk workers requires tools designed for employees who operate without company email, fixed workstations, or predictable schedules. Mobile-first platforms that average 10 daily app opens per user across 12,000 employees demonstrate that frontline engagement is achievable when the experience fits how those workers actually operate. [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study) is a concrete example of how a large, distributed workforce achieved consistent communication and accountability at scale. [Performance management](/solutions/performance-management) frameworks that account for shift-based and field-based roles ensure that the visibility and accountability benefits described above extend to every employee — not just those at a desk. --- # 5 Ways Task Management Tools Can Create A Detailed Project Schedule **Author:** Luke Walton **Published:** 2010-12-23 **Category:** integrated-digital-workplace Collaboration tools or social intranets are some of the most important elements of small business software. Online task management tools offer a solution to the common question of how to best manage tasks.  Poor task management leads to increased risk for poor communication, poor use of employee expertise and resources and failed project execution. Using […] # 5 Ways Task Management Tools Can Create A Detailed Project Schedule Poor task management leads to increased risk for poor communication, poor use of employee expertise and resources, and failed project execution. If you've searched for how to build a detailed project schedule using a [task management](/solutions/task-management) tool, here is a direct answer: the five methods below — establishing executors, detailing task outlines, setting priorities, reassigning as needed, and collecting fast feedback — give you a repeatable framework you can implement today, without returning to Google for the next step. Collaboration tools or social intranets are some of the most important elements of small business software. Online task management tools offer a solution to the common question of how to best manage tasks. Using a task management tool allows you to create detailed project schedules and helps keep track of tasks. **Here are 5 ways that project and task management tools can help you create a detailed project schedule:** ## Establish The Executors As you establish the goal of your project you'll decide who is responsible for executing the associated tasks. Essentially you are deciding who the project manager is and who is on the project team. Using a task management tool allows you to create a project group — a shared [workspace](/key-features/workspaces) where all surrounding communication is in one place. This allows everyone to stay on the same page and to develop tasks and insight in one central area. Project workspaces where tasks, files, discussions, and milestones live together in one place reduce context switching and keep schedule dependencies visible to all stakeholders. As each task is assigned and as the project changes and evolves, you can easily re-open, reassign, or delete tasks as needed. Team members will be notified in real-time of any updates or changes made. ## Detail Task Outlines Once you are ready to establish the specific tasks that it will take to meet your project goals, you can begin assigning tasks in your task management tool. Using an online task management tool as part of small business software it is easy to create tasks with detailed notes and documents. You can also outline who is responsible for what task and how each task should be performed — including attaching your SOP operations documentation or an operations manual directly to the relevant task, so team members have the exact operations instructions they need without hunting through a separate system. This makes it clear who is responsible for what and becomes a quick reference if questions arise. Detailed audit trails — logging every task change with who made it, when, and why — protect teams during compliance reviews and prevent schedule disputes from derailing projects. ## Establish Priorities Use your online task management tool to establish the priority of the task. Is it due today, tomorrow, or sometime soon? If your task is dependent on the completion of another team member's task, you can change the priority at any time and adapt the task's role in the project completion. Everyone in the project team is notified in real-time. For teams managing multiple concurrent projects, a shared [to-do list](/key-features/to-do-list) view that surfaces each person's highest-priority items prevents the common failure mode where urgent work gets buried under routine assignments. Teams using automated, rules-based work assignment report a 40% average reduction in scheduling time — meaning managers spend less time on coordination and more on execution. ## Assign As Needed Small business software for project and task management tools makes it easy to adapt a task status. When you get into a task you may soon realize that it really needs to be broken into multiple tasks. With online task management tools, you can easily create a new task within a project group and also re-open or re-assign an existing task. All changes are made in real-time so all stakeholders are kept up to date, preventing duplicate efforts or confusion surrounding current status. Task management platforms that embed no-code [workflow automation](/key-features/trackers-workflows) — routing approvals, triggering follow-on tasks, and flagging blockers — reduce manual coordination overhead without requiring IT involvement. This is especially important for deskless and field workers: real-time mobile notifications and offline sync mean that teams without consistent desktop access stay in the loop on reassignments and priority changes the moment they happen. One franchise organization achieved 75% platform adoption across 12,000 users by deploying a mobile-first task and communications tool. ## Receive Quick Feedback Perhaps the biggest part of using any online task management tool to create a detailed project schedule is that you can instantly solicit feedback from project members. With microblogging, chat and instant messaging, you can easily post comments and questions to help you stay on track. When you create an environment of open communication, you can incorporate change much faster, adapt timelines and goals and stay on track because your questions are more readily answered. With your task management tool, these threads are archived and become searchable. Effective teamwork management depends on this feedback loop closing quickly. Per Gallup.com, approximately 60 million full-time working Americans — about half the US workforce — are able to work remotely part of the time, which means your feedback channels must work equally well for remote contributors as for those on-site. ## MangoApps Creating a detailed project schedule doesn't have to be difficult. With the collaboration abilities of an online task management tool, it is easy to manage projects and tasks better. With MangoApps, you can easily break down tasks, attach SOP operations documentation, automate task routing, and stay on top of a project's progress — all from a single platform that works for both desk-based and deskless teams. To learn more about how MangoApps can solve your project management needs, schedule a demo today. ## What Features Should I Look for in a Task Management Tool? When evaluating tools for teamwork management, prioritize these capabilities: - **Task dependencies and milestone tracking** — so the schedule reflects real sequencing, not just a flat list of to-dos - **SOP and operations manual attachment** — the ability to link operations instructions directly to a task eliminates the need for separate reference systems - **No-code workflow automation** — routing approvals and triggering follow-on tasks without IT involvement keeps manual operations overhead low - **Mobile-first access** — critical for field and deskless workers who need real-time updates without a desktop - **Audit trails** — every change logged with who, when, and why, protecting the team during compliance reviews - **Integrated workspaces** — tasks, files, discussions, and milestones in one place, reducing context switching For a broader look at how scheduling tools are evolving, see [What Scheduling Managers Wish the Software Just Knew](/articles/what-scheduling-managers-wish-the-software-just-knew). ## How Do I Prioritize Tasks Across Multiple Projects? Prioritizing across multiple projects requires a system, not just a list. A practical approach: 1. **Map dependencies first** — identify which tasks block others before assigning due dates. Use your task management tool's dependency features to make this visible to the whole team. 2. **Use a unified to-do view** — a single view that aggregates each team member's tasks across all active projects surfaces conflicts before they become missed deadlines. 3. **Set priority tiers, not just due dates** — label tasks as critical, high, normal, or low so that when two tasks share a deadline, the team knows which one to protect. 4. **Automate escalation** — configure your tool to flag tasks that are overdue or blocked, so managers don't have to manually chase status updates. 5. **Review weekly at the project level** — use [goals management](/key-features/goals-management) features to connect individual task priorities back to project milestones, so priority decisions are grounded in outcomes, not urgency alone. For retail and frontline environments where scheduling complexity is especially high, [The Store Manager's Playbook for Smarter Retail Scheduling](/articles/store-managers-playbook-smarter-retail-scheduling) covers prioritization frameworks built for shift-based teams. ## Is Task Management Software Right for My Team Size? Task management tools scale from small teams to enterprise organizations. The decision factors are less about headcount and more about workflow complexity: - **Small teams (under 25 people):** The primary gain is visibility — everyone sees what everyone else is working on, which eliminates the coordination overhead of manual operations like status-update emails and stand-up meetings. - **Mid-size teams (25–500 people):** Automation becomes the differentiator. Routing approvals, triggering follow-on tasks, and enforcing SOP operations steps without manager intervention saves significant time. Teams in this range report a 40% average reduction in scheduling time when using rules-based assignment. - **Large and distributed organizations:** Audit trails, compliance documentation, and integration with an operations manual become critical. Per a Forrester Report, a company with 20,000 employees can realize $7.5M in three-year added value from a well-implemented employee platform — a figure that reflects reduced coordination costs and improved retention alongside productivity gains. For organizations evaluating a broader digital workplace platform, the [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) provides a current benchmark for what teams of different sizes are prioritizing. --- # 5 Reasons to Use Mobile Project Management **Author:** Luke Walton **Published:** 2010-12-22 **Category:** integrated-digital-workplace Let’s face it, project management software isn’t typically considered a favorite tool among your employees. This majorly stems from it’s inability to evolve along with other web-applications. While these web interfaces can be improved to create a better user experience for your employees, it is the emergence of mobile project management tools that will help […] ## 5 Reasons to Use Mobile Project Management Project management software has long struggled with adoption — and for good reason. Most platforms were built for desk-bound workers with reliable internet, corporate email addresses, and time to navigate complex interfaces. That reality no longer describes most of the workforce. Over 80% of the global workforce is deskless, making mobile-first project access a baseline requirement rather than a convenience for most organizations. Below are five concrete reasons to use a mobile project management solution, plus what to look for when evaluating your options. ## 5 Reasons To Use Mobile Project Management: ### #1: Real-Time Communication Mobile project management not only provides employees with instant access to company resources, it also enables real-time communication between team members, project managers, and stakeholders. Employees no longer need to wait for a meeting to get the latest information, or to collaborate on a project. Instead, just access the project from anywhere and get what you need. The move to real-time for business communication software is a huge change, but as it is embraced, it transforms our ability to work smarter and more efficiently. This matters especially for frontline and deskless workers who don't sit at a desk between shifts. An [employee communications platform](/key-features/workspaces) that surfaces project updates, task assignments, and team messages in a single mobile view eliminates the need to juggle multiple channels — a real problem given that employees navigate 6–8 disconnected tools daily, creating fragmentation that mobile project management consolidation directly addresses. ### #2: Instant Status Updates Make status updates a thing of the past. Instead, build an open culture of teamwork management. Mobile project management tools provide the instant capability to keep everyone informed and to reduce communication breakdowns that can hamper success. Per Gartner, 2023, 47% of workers struggle to find necessary information at least half the time. Centralizing project status in a mobile hub — one that doesn't require a VPN or corporate email to access — removes that friction at the source. Frontline employees who can access shifts, forms, and project updates in a single mobile app without a corporate email or VPN experience measurably lower onboarding friction, which accelerates adoption across the workforce. ### #3: Time Tracking Project managers and business owners need to understand how time is being spent on project activities. Unfortunately, no one likes to track their time in a task management system. Employees also often simply forget to enter their time, creating an inaccurate representation of your work efforts. Mobile project management can resolve this by making it easy for project members to enter time on tasks or projects. Mobile apps that support offline access allow workers in low-connectivity environments — warehouses, transit depots, field sites — to continue updating tasks and accessing critical documents without interruption. When time entry happens in the moment rather than reconstructed at end-of-week, the data becomes reliable enough to inform SOP operations reviews and resource planning. Per McKinsey research, 81% of leading companies effectively use data and analytics tools; accurate mobile time tracking is a prerequisite for that kind of operational visibility. You can explore how [task management](/solutions/task-management) features support this kind of real-time tracking. ### #4: Connecting with Colleagues When you see your colleagues in the office on a daily basis, it can be easy to form connections with them. Communicating with them on a specific project is as easy as stopping by their office. However, what do you do when you are away from the office? How do you contact your colleague? With a mobile project management system, you can quickly access information and collaborate with colleagues. You no longer have to ask around to find that key resource you need to move on with your project. For distributed and deskless teams, this connection has direct retention implications. Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback. Mobile tools that make it easy to surface concerns, comment on project progress, and stay visible to leadership create the feedback loop that drives that retention. Replacing paper-based and siloed project communication with a single mobile hub has been shown to reduce employee turnover, with one transit operator reporting a 26% reduction after deployment (Go North West case study). Frontline employee replacement costs range from $4,400 to $15,000 per worker, which frames the retention ROI of better mobile engagement in concrete financial terms. ### #5: Stakeholder Engagement Finally, beyond the project team, you have a series of stakeholders that often exist outside of the company. These people typically only stay connected with a project through face-to-face interaction or crafted emails. In some situations, they may receive access to the web interface, but it just becomes another complicated system to learn. With mobile access to project management solutions, the focus is on quick access to the information that matters most. Usually, within just a couple taps of the screen, you can see where a project stands and even provide comments of your own. This is also where consolidation pays off. Rather than maintaining separate systems for project updates, HR communications, and operations instructions, a unified mobile hub lets stakeholders — internal and external — stay current without learning a new tool for every workflow. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading organizations are consolidating these touchpoints to reduce tool-switching costs. Mobile project management has the opportunity to really shake up how projects interact and engage with the project management system. By making it easily accessible, you can improve the overall level of employee engagement in the project. ## MangoApps MangoApps provides a mobile project management software solution that can change the way your employees stay connected. With an easy-to-use interface, employees can access resources and communicate on a project from wherever they are — no corporate email or VPN required. The platform functions as a unified hub for shifts, forms, HR communications, and project updates, directly addressing the 6–8 daily app problem that fragments deskless workforces. To learn more about how MangoApps can benefit your organization, contact us or schedule a personalized demo today. --- ## How Do You Measure the ROI of Mobile Project Management? ROI from mobile project management typically shows up in three places: time recovered from manual operations (status meetings, email chains, paper-based reporting), reduction in employee turnover driven by better engagement and communication, and faster project cycle times from real-time visibility. The Go North West case study documented a 26% reduction in turnover after consolidating communications into a single mobile hub. On the cost side, frontline replacement costs of $4,400–$15,000 per worker mean even modest retention improvements generate measurable returns. For a structured framework on tracking these outcomes, the [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines how HR and operations leaders are building the business case for mobile-first workforce tools. ## How Do You Drive Adoption When Employees Resist New Tools? Adoption resistance is the most common reason mobile project management initiatives stall. The most effective mitigation strategies share a few traits: the tool must require no new login credentials (no corporate email, no VPN), it must consolidate rather than add to the existing app stack, and it must surface information relevant to each worker's role without requiring them to navigate a full operations manual. Structured [trackers and workflows](/key-features/trackers-workflows) that mirror existing SOP operations processes reduce the learning curve significantly. For teams managing unionized or shift-based workforces, [Managing a Unionized Workforce Is Different. Your Software Should Be Too](/articles/managing-a-unionized-workforce-is-different-your-software-should-be-too) covers the specific adoption considerations that standard change management playbooks miss. ## What Should You Look for When Choosing a Mobile Project Management Solution? When evaluating options, prioritize these criteria: offline access for low-connectivity environments, no-email login for frontline workers, consolidation of project, HR, and communications functions in a single app, and configurable [goals management](/key-features/goals-management) that connects individual task completion to team-level outcomes. Per the Forrester Wave: Intranet Platforms, Q2 2024, governance and integration depth vary significantly across vendors — evaluate whether the platform can serve as a true employee communications platform rather than a standalone project tool. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) provides a vendor-neutral framework for assessing these capabilities against your organization's specific workforce profile. --- # 5 Tips for Successfully Deploying Collaboration Tools **Author:** Luke Walton **Published:** 2010-10-29 **Category:** company-collaboration There is no doubt that collaboration tools will help your business work better and smarter than ever before. But in order use this software to your full advantage it has to be introduced and deployed effectively. As we have talked and worked with customers, we have learned five of the best tips for successfully deploying collaboration tools. […] ## 5 Tips for Successfully Deploying Collaboration Tools Deploying collaboration tools only delivers value when the rollout is deliberate. Per Gartner, 2023, 47% of workers struggle to find necessary information at least half the time — a problem that worsens when tools are introduced without a clear strategy. Employees already navigate 6–8 disconnected tools daily, creating communication fragmentation that a unified deployment strategy must address from day one (MangoApps platform data). As we have talked and worked with customers, we have learned five of the best tips for successfully deploying collaboration tools. ## Have a Purpose The most important thing you can do when deploying collaboration tools is to have a purpose. Some collaboration technologies are designed to just engage departments or project teams through sharing. This is really to be expected, given that Twitter and Facebook styles of communication are becoming the norm. Sharing is important, but it needs a purpose. We have seen the greatest success with our customers when they take our core communication tools and wrap them around project management, task management, idea management, or some other greater objective — essentially building a living operations manual that teams actually use. The key here is to have an objective in mind and to leverage the communication paradigms to help bring those activities to life. Organizations that replace paper processes and siloed systems with a single communication hub report measurable reductions in employee turnover, not just productivity gains — including a 26% reduction in employee turnover after consolidating frontline communications into a single hub (Joinblink / Blink, Go North West case study). That outcome starts with purpose-driven deployment, not feature-first adoption. ## Get Management Involved With any initiative or goal, it is critical to get the management behind you. When management is properly informed about the benefits and advantages of effective collaboration tools, they will be much more open to exploring and embracing the option. Going at it alone, forcing the issue, and not getting management support is almost always a recipe for disaster. Prepare and encourage management to be on your side. Per McKinsey research, 89% of frontline workers will stay with their companies if leaders listen to their feedback — which means management participation in a collaboration rollout is not just an adoption tactic, it is a retention strategy. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) offers a practical framework for building that executive case. ## Don't Go Around IT Many 'would be' innovators avoid IT, afraid that their idea will be shot down or won't be taken seriously. This might, unfortunately, be true within a lot of organizations, but it doesn't mean you shouldn't try. Like working with management, involving IT can help you avoid bigger challenges around information security, SOP operations compliance, and data governance down the road. IT by nature is typically tasked with information security, and like it or not, company information sharing is their business. As a side note to IT folks, be open to your users. Don't discount what they are trying to do and the solution they are bringing to the table. Create a mutual partnership to understand the current problems and available options. ## Try Before You Buy Whatever solution you decide to deploy, it is important to experience a fully functional free trial. Don't get roped into a trial that has features disabled, or limits either end user or administrative capabilities. A trial should offer everything you are considering with the initial rollout. At MangoApps, we place a high value on this and provide fully functional trials to everyone. We also realize that it might take a little more time than a set 30 days, so we are flexible with your trial period to ensure you have the right amount of time to make a decision before you get ready to start deploying collaboration tools. When evaluating an employee communications platform during a trial, test it against your actual workflows — not just feature checklists. The [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms) provides useful context on what independent analysts look for when scoring enterprise collaboration platforms. ## Walk Before You Run Finally, be aware that technology is outpacing the end user's ability to consume. Solutions are becoming loaded with features, apps, and operations instructions that are simply too much and often go unused. As you consider deploying collaboration tools, make sure you can consume capabilities in realistic chunks. Be aware of all of the important capabilities available to you and bring them into the mix as those needs warrant. Remember to find your purpose first and then slowly expand and explore from there. Vague phasing is not enough. Set concrete adoption milestones: per MangoApps deployment data, 95% of customers reach full adoption within 90 days when deployment follows a structured rollout plan. Treat that 90-day window as your baseline target, not an open-ended timeline. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) includes a phased rollout framework you can adapt for your organization. ## A Note on Frontline and Deskless Workers Most deployment guides treat all employees as desk workers with corporate email. That assumption breaks down fast. Frontline workers make up over 80% of the global workforce and are disproportionately harmed by poor collaboration tool rollouts because they often lack corporate email or desk access (MangoApps / industry report framing). A successful teamwork management strategy for these employees requires mobile-first access, offline capability, and no-email onboarding from day one. Replacing a frontline employee costs $4,400–$15,000, making failed tool adoption a direct financial risk, not just a productivity issue (industry estimate). Solutions built for [workforce management](/solutions/workforce-management) and [shifts and schedules](/solutions/shifts-schedules) address these requirements natively — plan for them before launch, not after. ## MangoApps Our MangoApps suite allows our customers to improve team collaboration in the workplace, adding capabilities as the need emerges. If you would like to learn more about how MangoApps can assist your organization, schedule a personalized demo today! --- ## How Do I Measure Collaboration Tool Adoption After Deployment? Adoption is not the same as activation. Measuring it requires tracking active usage rates, not just login counts. Useful milestones include: percentage of employees who have completed at least one task or post within 30 days, message volume trends week-over-week, and the share of workflows that have migrated off legacy channels (email threads, paper forms, manual operations logs). Per McKinsey research, 81% of leading companies effectively use data and analytics tools — apply that same discipline to your internal platform metrics. Set a 90-day full-adoption target and review progress at 30-day intervals. The [Connecting 20,000 Employees: The Raley's Companies' Success Story With MangoApps](/resources/raleys-case-study) case study illustrates what structured adoption measurement looks like at scale. ## How Long Does a Typical Collaboration Tool Rollout Take? Timelines vary by organization size, IT complexity, and how many legacy systems are being replaced. For most mid-market organizations, a structured rollout follows three phases: a 2–4 week configuration and IT alignment phase, a 4–6 week pilot with a defined employee group, and a 60-day full-organization rollout with adoption checkpoints. Per MangoApps deployment data, 95% of customers reach full adoption within 90 days when following a structured plan. Organizations replacing fragmented manual operations and siloed systems should budget additional time for change management and employee communications training, particularly for frontline populations without prior digital tool experience. ## Which Features Should We Prioritize in the First 90 Days? Start with the capabilities that solve the most acute pain point your purpose-setting exercise identified. If the core problem is information fragmentation, prioritize a single searchable knowledge base and a company-wide news feed before enabling project boards or integrations. If the problem is frontline scheduling and shift communication, deploy [shifts and schedules](/solutions/shifts-schedules) and mobile notifications first. Avoid enabling every feature at launch — per the 'walk before you run' principle, feature overload is one of the most common reasons adoption stalls. The [2026 HR Trends eBook](/resources/2026-hr-trends-ebook) outlines which communication and operations capabilities organizations are prioritizing in current deployments. --- # 3 Steps to Add Measurable Business Value to Your Organization **Author:** Vishwa Malhotra **Published:** 2010-08-07 **Category:** industry-insights Everyone wants to add measurable business value to their organization, this is what we measure our growth, success and even failures upon. Without measuring, we are just guessing. Step 1: Connect your knowledge workers An enterprise social networking platform enables connecting your knowledge workers across the organizational hierarchy, time zones, and offices. To add measurable […] # 3 Steps to Add Measurable Business Value to Your Organization The business case for workplace collaboration software usually starts with a calculation: per IDC, employees spend 2.5 hours per day searching for information they need to do their jobs. Reducing that by half across a 1,000-person organization saves millions in labor hours annually. The math holds. The problem is the denominator. Per Emergence Capital, approximately 80% of the global workforce is deskless — working in motion across shifts, without corporate email addresses or company-issued devices. The platforms most organizations use to calculate productivity savings were built for the other 20%. When a tool reaches 20% of the workforce and the ROI model assumes 100% participation, the gap between projected and actual business value is structural, not behavioral. Closing that gap is not a deployment question. It is a design question — and it is the precondition for the three steps below to produce outcomes that are actually measurable. ## Why access has to come before anything else Per Social Edge Consulting, 91% of organizations operate an intranet. Thirteen percent of employees use one daily. Nearly a third never log in at all. Per SWOOP Analytics, the average employee who does log in spends six minutes per day doing so. These are not user adoption failures. They describe what happens when infrastructure is built for a desk-based minority and deployed to an organization where most of the work happens elsewhere. The cost of this gap compounds in ways most finance teams do not track directly. Employees who cannot access company communications improvise, escalate to managers, or proceed without the information. All three outcomes are slower and harder to audit than a functioning access layer would be. The cost to replace a single frontline employee runs from $4,400 to $15,000 depending on the role — a figure that reframes what connection infrastructure is actually worth. At scale, turnover driven by disconnection is one of the most avoidable costs in the business value equation. [Gallup's 2026 State of the Global Workplace](/articles/gallup-2026-state-of-the-global-workplace) documents how persistent exclusion from organizational information systems is a reliable early indicator of disengagement — and how disengagement's cost extends well beyond productivity into turnover, quality errors, and the coordination overhead that accumulates when managers become the de facto information layer because the platform cannot reach their teams. Fixing access is the structural intervention. The engagement and retention outcomes follow from that. ## Step 1: Reach the entire workforce, starting with the 80% without a desk Connecting the desk-based 20% is a solved problem. Most enterprise collaboration platforms handle it adequately. The measurable business value opportunity is in the rest of the workforce — the distribution center, the clinic unit, the retail floor, the field vehicle — where communication infrastructure typically does not reach because it was never designed to. Frontline and deskless employees can be reached without a corporate email address or VPN when the platform supports mobile-first enrollment on personal devices. The access barrier is not a behavioral problem. It is an enrollment model problem. Organizations that change the enrollment model — rather than the culture program layered on top of broken infrastructure — consistently see adoption rates above 70% within a quarter of launch. Two case reference points are worth anchoring to. OU Health achieved 87% workforce engagement within months of launching a branded employee app for clinical staff — an outcome that followed from changing who the platform could reach, not from changing the content it delivered. PetSmart reached four times the industry-standard engagement rate under a similar model. The mechanism in both cases was structural: when employees can reach the platform from a device they already carry, without credentials they do not have, usage follows without a change management program. The baseline metric for Step 1 is workforce reach: what percentage of employees receive and open a company communication within 48 hours? In organizations with a desk-only access model, this typically runs below 40% for non-email channels. When the enrollment barrier is removed, that number crosses 70% within a quarter. The ROI model starts using the correct denominator only after this step is in place — because any calculation that counts only the employees the platform can reach will overstate what the platform actually delivers to the organization. [Employee engagement solutions](/solutions/employee-engagement) that are designed for the full workforce — not just the connected minority — close the reach gap at the access layer, not the content layer. ## Step 2: Build an idea channel where participation produces visible outcomes The second structural gap is signal loss. Most organizations have nominal channels for employee ideas — a quarterly survey, a town hall, a digital suggestion box — but these channels share a design flaw: information flows in one direction. Ideas enter. Feedback rarely returns. Employees learn quickly that participation does not change anything, and contribution rates fall to match expectations. Per Social Edge Consulting, 13% of employees use an intranet daily. That figure describes how organizational communication typically flows: top-down, from leadership to employees, with no visible mechanism for ideas to travel in the reverse direction and reach decision-makers. The engagement gap is not a motivation problem. It is an architecture problem. An idea management platform that allows employees to submit, view others' submissions, vote, comment, and track ideas through a visible decision cycle changes the participation dynamic. Employees do not need behavioral change to participate — they need a feedback loop they can see. When an idea progresses toward a decision, and employees receive acknowledgment when a submission is adopted or declined, participation rates run two to four times the rate of traditional intranet deployments. AI-assisted idea routing is changing what this step looks like in practice. Platforms that use AI to surface relevant ideas to the employees most likely to have useful input — based on role, department, or prior contributions — increase the quality of ideas reaching reviewers and reduce the time spent evaluating submissions outside a reviewer's scope. Organizations deploying AI-native routing report higher submission volumes and shorter time-to-decision cycles, without requiring a larger review team. For the measurement piece: idea participation rate is the baseline metric. Of the employees who could submit an idea, what percentage do? The 13% daily engagement figure from Social Edge Consulting is a reasonable proxy for traditional intranet deployments. Purpose-built platforms with visible feedback loops typically achieve two to four times that rate within six months of launch. The [2026 Internal Communications Trends eBook](/resources/2026-internal-communications-trends-ebook) covers the measurement frameworks HR and communications leaders use to set baselines and track engagement shifts before they surface in attrition numbers. ## Step 3: Reduce the coordination overhead that accumulates in tool sprawl The third structural gap is fragmentation. Employees lose more than four hours per week switching between disconnected applications — navigating between email, chat, project tracking, document storage, and reporting dashboards that do not share a data model. Project status is distributed across those systems in fragments no single person can see in full. This is the mechanism that makes projects expensive even when the underlying work is straightforward. Proposal cycles extend because feedback is scattered across email threads. Sales cycles lengthen because deal history lives in a system only part of the team can access. Product timelines slip because task dependencies are tracked in a spreadsheet that is always slightly out of date. The cost is not dramatic per incident — it accumulates in hours, across people, across months, and it does not show up in any single tool's usage report. TeamHealth consolidated more than 200 disconnected systems into a single mobile dashboard. That outcome became achievable when the access model changed — when every employee, across every facility and role, could reach the same project surface. Coordination overhead did not shrink because of a new project methodology. It shrunk because information stopped being fragmented across systems no single employee could view in full. The consolidation itself was the intervention. The measurement case for Step 3 is the most directly tied to financial outcomes. Cycle time reduction on proposals and deals is trackable in CRM data. On-time delivery rates are trackable in project logs. The delta — in hours per project, in cost per closed deal — is the "measurable" in measurable business value. Without a unified surface, those numbers do not exist because the underlying data is too fragmented to aggregate reliably. For organizations evaluating which platform to move toward, the [ClearBox Consulting 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides a benchmarking framework comparing platforms on frontline accessibility, search quality, and administrative overhead — the three criteria that map most directly to the outcomes each step above is designed to produce. ## The sequence matters more than the steps Each step is a precondition for the next, which is why the order is not interchangeable. The insight quality in Step 2 depends on the reach achieved in Step 1 — an idea management platform that only reaches the desk-based 20% collects ideas from the minority of the people executing the work. The project efficiency in Step 3 depends on both — unified collaboration that excludes frontline workers produces a unified view of an incomplete picture. Organizations that address these gaps in parallel typically report slower results than those that address them in sequence: fix access before fixing content, fix participation before fixing process, fix integration before fixing reporting. The compounding effect comes from each step building on the previous one's baseline. That sequencing also determines what is measurable and when. Step 1 outcomes — workforce reach metrics — are visible within weeks of launch. Step 2 outcomes — idea participation rates — are visible within a quarter. Step 3 outcomes — cycle time reductions — require a full project cycle to measure, typically 60 to 90 days. The baselines for all three steps can be established before any platform decision. Workforce reach: what percentage of employees open a company communication within 48 hours? Idea participation: of the employees who could submit an idea, what percentage do? Cycle time: how many tools does a typical project require to reach a final decision, and how long does that take? These numbers do not require new software to measure. They require a decision to measure them — and a commitment to revisit them at a defined interval after any infrastructure change. That commitment is the structural work that converts a three-step framework into something specific enough to act on and honest enough to evaluate. --- # The Warning Signs of Serious Software Bloat **Author:** The MangoApps Team **Published:** 2010-05-18 **Category:** best-practices What Is Software Bloat? Software bloat is a term used to describe the tendency of newer computer programs to leave a larger installation footprint,  have many unnecessary features, or just generally use more system resources than necessary. It also describes software that comes pre-installed on a computer when it is purchased,  consists of time-limited trials or feature-lacking basic or […] ## The Warning Signs of Serious Software Bloat ### What Is Software Bloat? **Software bloat** is a term used to describe the tendency of newer computer programs to leave a larger installation footprint, have many unnecessary features, or just generally use more system resources than necessary. It also describes software that comes pre-installed on a computer when it is purchased, consists of time-limited trials or feature-lacking basic or beginner versions. Personally, we don't consider unnecessary RAM/disk space to be part of software bloat, but badly written software and poorly designed products certainly are. In this new computing world, software bloat is more about creeping features and taking a simple system and over-engineering it. Nowhere is this more visible than in enterprise [intranet](/solutions/modern-intranet) platforms, where bloated legacy tools correlate directly with near-zero daily usage — per Social Edge Consulting, only 13% of employees use their intranet daily, and nearly a third never log in at all, even though 91% of organizations operate one. Here is our simple checklist of how to spot software bloat in most enterprise software: ### 8 Warning Signs Of Software Bloat 1. **New software releases are extremely infrequent.** If an update is more than six months apart, you need to reassess your solution. 2. **There are millions of settings and preferences.** Your software should not have a million configuration settings that can deter the user from effectively using it. Bloated intranet platforms with excessive configuration requirements correlate with near-zero daily usage — traditional intranets take months to deploy, strain IT teams, and deliver static, ungoverned content that becomes stale (per Unily product research). 3. **Too complicated to manage.** Your software is inefficient if it requires an IT administrator to install, setup and manage. Software complexity that requires IT-led customization is a primary reason enterprises pay $130,000–$426,000 in first-year costs for platforms like SharePoint before any productivity return is realized (per MangoApps blog / Awesome Technologies Inc. 2025 cost model). 4. **The software comes with a training manual, or training package.** This implies that the software is too complex for the average user to understand. 5. **There are countless different editions & versions of the software.** When this is the case, you need to figure out if the edition you have is the most current. 6. **The software comes with a hardware spec that rivals a mainframe.** This is counterproductive to organizational efficiency & productivity — and it signals poor mobile readiness for the 80% of the global workforce that is deskless, per Emergence Capital. 7. **Irrelevant features.** The features list contains irrelevant functionalities that aren't relevant to the primary purpose of the software. Persona-based targeting and role-aware search are now table-stakes features that distinguish modern intranet platforms from bloated legacy tools requiring manual configuration for each audience segment (per Akumina product research). 8. **Minimal difference between software versions.** The primary difference between the old version and the new version is additional features that don't seem to provide a benefit. Per SWOOP Analytics, the average employee spends just six minutes per day using intranet tools — a benchmark that reflects how little value bloated platforms actually deliver. ### What Does Software Bloat Actually Cost? The warning signs above are symptoms. The real damage is measured in time and money. Per IDC, employees spend 2.5 hours per day searching for information — a direct consequence of disorganized, over-engineered platforms that bury content under layers of configuration. When a platform requires months of IT-led deployment and hundreds of thousands of dollars in first-year costs before a single employee benefits, the bloat has already won. The contrast is stark: Uber Freight Connect achieved a 95% employee adoption rate after deploying a unified, low-friction intranet platform — sharply contrasting with the near-zero daily usage rates seen on bloated legacy intranets. Bloat-free, mobile-ready platforms can reach 90% frontline adoption within the first six months, a benchmark that legacy tools with complex onboarding rarely approach. For a deeper look at how these dynamics are reshaping workplace technology decisions, the [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](/resources/clearbox-2026-intranet-and-employee-experience-platforms-report) provides independent vendor benchmarking across exactly these criteria. ### How Do You Fix Software Bloat? Recognizing bloat is step one. Fixing it means auditing your current stack against the checklist above and asking whether each tool earns its complexity. The practical path forward involves three questions: - **Can a non-IT employee configure and maintain it?** If the answer is no, the platform is over-engineered for its purpose. - **Does it work for deskless and frontline workers?** With 80% of the global workforce deskless (per Emergence Capital), a platform that requires desktop access or heavy onboarding excludes the majority of your people. - **Does it consolidate or multiply tools?** Bloat compounds when organizations layer point solutions on top of each other. A unified [company portal](/key-features/company-portal) that handles communications, content, and workflows in one place eliminates the configuration overhead that bloated stacks create. The [2026 Workforce Operations Trends eBook](/resources/2026-workforce-operations-trends-ebook) covers how leading organizations are rationalizing their software stacks and the criteria they use to evaluate replacements. ### Which Tools Are Designed to Avoid Bloat? Modern intranet platforms differentiate themselves from bloated legacy tools through AI-driven personalization, no-code workflow automation, and role-aware content delivery — turning the "million configuration settings" anti-pattern into a solved problem. Rather than requiring IT administrators to manually configure audience segments, platforms built on these principles surface the right content to the right person automatically. MangoApps combines employee social networking, team collaboration, and social intranet into one platform. At MangoApps, we believe that the current set of collaboration tools restrict the distribution of information and prevent effective collaboration. By integrating a modern social intranet, we enable a highly productive work environment that empowers and inspires employee engagement at all levels. Features like [department sites](/key-features/department-sites) and a no-code [webpage builder](/key-features/webpage-builder) are specifically designed to eliminate the IT dependency that bloated platforms require. For independent validation of how MangoApps stacks up against the bloat criteria above, see [MangoApps Included in Leading Research Firm's Intranet Platforms Evaluation](/articles/mangoapps-2026-forrester-wave-intranet-platforms). To learn more about how MangoApps can help your organization, contact us or schedule your own personalized demo today. --- # Complete Guide to Field Service Management **Type:** Resource **Published:** 2026-09-30 Late invoices, lost billables, inconsistent quotes, and technicians sent to work they are no longer certified for all trace back to six information gaps. This 64-page book names them, shows how to cost them on your own numbers, and lays out what a field service platform has to do to close them, with a 12-question evaluation scorecard and seven industry breakdowns. What is inside The six information gaps. Where field service operations actually leak money, from the invoice that waits on paperwork to the dispatch board that cannot see who is certified. What the gaps cost. Six formulas to put a number on late invoicing, missed billables, pricing drift, slow estimates, status calls, and compliance risk, using your own figures. Why the problem has been accepted as normal. Field service software was built in two halves for twenty years. Neither was built for the whole job, and three things have now changed that. From request to paid on one record. Work orders, dispatch, estimates, invoicing, price book, service agreements, inspections, fleet, and a customer portal on one data model, so nothing gets typed twice. AI grounded in your data. Who to send, a draft estimate from your price book, diagnostic steps from your own manuals, all running inside the permissions of the person asking. How to evaluate vendors. Twelve questions, a scorecard to run against every vendor including us, and five demo requests to send before the meeting. Industry breakdowns. HVAC, plumbing, electrical, property management, utilities and telecom, landscaping and grounds, and fire and life safety. Written for operations, service, IT, and finance leaders at field service companies and multi-site operators with 1,000 or more employees. No product content until page 13. One platform, a different answer for each role Owner or general manager Cash arrives faster because the invoice no longer waits on paperwork, and recurring agreements schedule and bill themselves. Dispatcher One board with every open job, every technician's workload, and the maintenance that generated itself overnight. A lapsed credential cannot be assigned. Field technician Work order, estimate, price book, signature, timesheet, and company news in one app on the phone they already carry. No password. No corporate email. IT Fewer vendors, contracts, integrations, and security reviews. One identity model, with HITRUST, SOC 2 Type II, and ISO 27001 on one system. 18+ years built for the frontline · 2M+ users · 98% retention · 90%+ adoption in 90 days · HITRUST · SOC 2 Type II · ISO 27001 · FedRAMP ATO **Download:** [Complete Guide to Field Service Management](https://mango-cdn.b-cdn.net/marketing/uploads/field-services-WEB-small.pdf) --- # Guide to Frontline Worker Communication & Engagement **Type:** Resource **Published:** 2026-09-25 63% of frontline workers say messages from leadership do not reach them. This book covers why, what closing the gap requires, and how to make communication a measured function instead of an act of faith. What is inside The six reach gaps. Where frontline communication actually breaks, and a six-question diagnostic to score your own operation. Why a mobile intranet does not fix it. The desk model makes seven assumptions. Frontline work breaks all seven. Ten requirements, written before the demo. What a frontline platform has to do, in the order a frontline-built product can do it. The business case. A cost and return model for a 5,000-employee employer, every assumption stated. How to evaluate vendors. Twenty questions and a nineteen-row scorecard to run against every vendor, including us. Industry breakdowns. Retail, healthcare, manufacturing, distribution, hospitality, and field services. Written for communications, HR, operations, and IT leaders at multi-site companies with 1,000 or more employees. No product content until page 25. Nine customer stories, including PetSmart Roughly 80% of a 55,000-person workforce had little or no access to the previous desktop-centric platform. The branded app closed that gap. Santee Cooper Field crews now receive storm alerts and safety notices in the same conversation as office staff, on an app their own employees named. Andersen Corporation Two-thirds of a 14,000-person workforce is frontline. Four years ago most had no email access. More than 90% now actively engage. 18+ years built for the frontline · 2M+ users · 98% retention · 90%+ adoption in 90 days · HITRUST · SOC 2 Type II · ISO 27001 · FedRAMP ATO **Download:** [Guide to Frontline Worker Communication & Engagement](https://mango-cdn.b-cdn.net/marketing/uploads/Frontline-Worker-Comms-WEB-small.pdf) --- # The Employee Platform for the AI Era: Technology Leaders Book **Type:** Resource **Published:** 2026-08-27 An assistant on top of disconnected tools can answer a question. It cannot safely act. This book is written for the person who owns the architecture, and it includes an eight-test proof of concept plan for evaluating any vendor's AI governance claims, ours included. Fill every gap. Connect any model. Govern it all. When a board asks for an AI strategy, what it is actually asking for is a foundation that can carry one. The technology leader is the person who will be asked to show whether that foundation exists. That is a harder question than it should be, because the stack was never built to answer it. A comms tool, a scheduling tool, a learning system, a help desk. Each was a sound decision on the day it was made. Together they became the fragmentation your AI is now expected to act on, with a separate identity, permission model, and record in every corner of it. The model is not the constraint. The foundation under it is. Why this lands on your desk The business consequences belong to the C-suite. The architecture decision belongs to you. The CFO sees 8 to 15 contracts per employee's workday and transformation ROI that never landed. The COO sees workforce execution going dark exactly where the stack ends. The CHRO sees an employee record that does not connect. You see the reason underneath all three: a stack that was never built to share, now being asked to host agents that act. What the book covers The foundation. One identity across desk and frontline, one permission model, one employee record, and one audit log. Stack subtraction as an operating number: every app moved onto the platform is one fewer vendor, contract, SSO configuration, and integration to maintain. The AI layer. Intelligence, assistants, and agents native to one data model. The Agent Development Lifecycle, where governance is a stage rather than a checklist, with risk review at design time and retirement through the same lifecycle that launched the agent. Adaptable and open. Build what no vendor shipped with Plugin AI Builder, AI Forms, and the AI Workflow Generator. Connect the intelligence you choose through standards-based MCP, or bring your own model. Extend programmatically with a 345+ command CLI, TypeScript and Python SDKs, and an integration fabric spanning 200+ systems. Governance and deployment. The same governance model across SaaS, private cloud, customer VPC, and on-premise. PII detection, per-agent autonomy settings, and a multi-level pause that works per agent, per app, per business, or platform-wide. The edges, stated deliberately. What the platform will not do, designed in rather than discovered later. No agent operates above the permissions of the user invoking it. High-impact actions stop for human approval. External writes are rate-limited per application per tenant. Nothing is on by default. The section to read first: an eight-test proof of concept plan Every architectural claim in the book is testable. The book hands you the test plan and asks you to run it against us. The permission test. Ask AI, as a limited test user, for something that user is not cleared to see. The answer should be scoped or refused, and the attempt should appear in the audit log. The grounding test. Ask about content that exists on the open web but not in approved sources. The answer should decline rather than improvise. The audit test. Take any agent interaction from the pilot and reconstruct it: who, what, when, outcome, timing, errors. If you cannot, the governance is a slide, not a system. The build test. Describe a small workflow to the AI builder. Verify the output requires review before rollout, respects existing roles without configuration, and carries version history with rollback. The external-agent test. Connect an MCP-compatible agent through OAuth. Verify consent is requested per scope, the agent acts as the connecting user, and its calls land in the same audit log as internal activity. The policy test. Declare an org-wide agent access policy. Verify an external agent call obeys it the same way an internal agent does. The kill-switch test. Pause a single agent and verify it stops responding everywhere while every other AI surface continues. Then confirm the other three levels exist. The escalation test. Attempt a high-impact action through an agent, a compensation change or a bulk operation, and verify it stops for explicit human approval. A vendor whose claims are architectural will hand you this list. A vendor whose claims are marketing will change the subject. Four deployment options, one governance model Most platforms in this category offer one way to deploy. MangoApps offers four: SaaS, private cloud, customer VPC, and on-premise. The same platform, the same apps, and the same AI governance run in all four, and the compliance posture carries across them. HITRUST CSF, SOC 2 Type II, and ISO 27001 certified HIPAA with BAA, and GDPR SSO and SAML, field-level RBAC, DLP, eDiscovery, configurable retention, MFA, geo-fencing Employee data never trains public models. The exclusion is contractual and architectural. Model choice is a setting, with automatic failover, and private LLM support for isolated requirements 99.9% uptime SLA Built for the frontline for 18+ years 2M+ users worldwide, 18+ years in market 98% customer retention 90%+ adoption within 90 days of launch 200+ enterprise integrations 50%+ of the roadmap comes from customer requests The Adoption Guarantee: if employees do not adopt after launch, you do not pay Read the book The full architecture argument, the AI layer in depth, the extension model, the governance posture, and the vendor test plan. No form. Read the book Schedule a call **Download:** [The Employee Platform for the AI Era: Technology Leaders Book](https://mango-cdn.b-cdn.net/marketing/uploads/TechLeaders-Employee-Platform-WEB_small.pdf) --- # End-to-End Talent Acquisition: The Modern Recruiting Playbook **Type:** Resource **Published:** 2026-08-26 Recruiting breaks at the handoffs, not the process. This book traces the four transitions where hiring falls apart, then shows what closes them when eight capabilities run on a single data layer. Read it free, no form. Recruiting runs on handoffs. That is the problem. A req approved in one place. A candidate tracked in another. Interviews scheduled by email, an offer chased through four inboxes, and an onboarding program that starts the person over. Recruiters absorb the space between those systems until it feels like part of the job. Ask a VP of Talent Acquisition about their biggest challenge and the first answer is process: time-to-fill is too long, offer acceptance has slipped, the candidate experience is not where it needs to be. Push further and the answer shifts. The tools do not talk to each other, the data lives in three places, and every hire involves manual coordination nobody has time for. Those are the same problem from two vantage points. The core challenge is not sourcing, compensation, or the labor market. It is infrastructure. 68% of companies operate with disconnected HR systems, and the inefficiencies compound every time a process crosses a system boundary (Ignite HCM, [YEAR]). The four transitions where hiring breaks The book is organized around the four moments a candidate crosses a system boundary, because that is where time, context, and candidates get lost. Requisition to posting. Approval chains that live in email and a job description written from scratch every time. Screening to interview. Resume volume scored by job-title proximity instead of what the role actually requires. Interview to offer. Scorecards in one place, approvals in another, and no record that holds up if anyone asks. Offer to onboarding. A signed offer that starts a second, manual process instead of the first day of employment. What is inside The Talent Acquisition Suite is eight capabilities on one data layer. Each works on its own. Each one you turn on gives the Recruiting Agent more connected data to work from. Job Board & Career Site. A branded application experience on the phone candidates already carry. Recruiting Agent (AI). Scores every application against the requirements of the role, and flags candidates about to slip away. Interview Scheduler. Panel coordination without the calendar relay. Offer Manager. Configurable approvals, versioned offers, and a clean record of who approved what. Background Checks. Ordered, tracked, and attached to the candidate record. Onboarding Hub. Acceptance provisions access, queues training, and puts the new hire in the directory before day one. Headcount Planner. Requisitions built from the capability gap, not just the vacancy. Talent Hub. Stage conversion, time-to-fill against time-to-hire, and where individual interviewers pull against the panel. Three outcomes the book is built around Recruiters who spend their time on people. The platform absorbs the coordination work, so the hours go to candidates instead of copying data between systems. Hiring decisions that hold up under scrutiny. Structured scorecards, configurable approvals, and a complete audit trail on every candidate. Consistent and defensible if a regulator, a union, or an internal review ever asks. A first week that matches the company they chose. A signed offer provisions access, queues training, and sets 30-day goals before day one. Why this sits on a platform, not in another point tool Talent Acquisition is one workflow on the AI-Ready Employee Platform for the Frontline. Requisitions, offers, and onboarding write to the same employee record that HR, payroll, learning, and performance already read. A hire becomes an employee without re-entry. That connection is also what makes the AI useful. The Recruiting Agent works inside your data, your permissions, and your rules, not the open web. No user can surface through AI what they cannot access directly. Most hiring is frontline hiring. The store associate, the charge nurse, the field technician, the warehouse crew. They have no corporate email and no company device, and they are the fastest to lose to a competing offer. When recruiting connects to scheduling, safety, and IT provisioning, a completed hire becomes a scheduled, equipped, credentialed worker with no manual handoff. Built for this, for 18+ years 2M+ users worldwide, 18+ years in market 98% customer retention 90%+ adoption within 90 days of launch 200+ enterprise integrations, 99.9% uptime SLA HITRUST CSF, SOC 2 Type II, and ISO 27001 certified Typical implementation completed in 8 to 12 weeks The Adoption Guarantee: if employees do not adopt after launch, you do not pay Read the book 63 pages, no form. The full problem breakdown, all eight capabilities in depth, what the first 90 days actually look like, and the questions recruiting leaders ask before they buy. Read the book Schedule a call **Download:** [End-to-End Talent Acquisition: The Modern Recruiting Playbook](https://mango-cdn.b-cdn.net/marketing/uploads/talent-acquisition-WEB.pdf) --- # Shifts & Schedules Book **Type:** Resource **Published:** 2026-08-03 This ebook examines what shift-based scheduling actually costs: in turnover, in overtime that creeps in unnoticed, and in the hours managers lose to coordination. It shows how one platform built for the frontline closes the information gaps behind every operational problem, so managers can run the schedule and trust the hours. AI Scheduling for Shift-Based TeamsRun the Schedule. Trust the Hours.The frontline operations manager has one of the hardest jobs in any organization.They are accountable for coverage, attendance, labor cost, fairness, and retention, often across multiple locations, often with high turnover, always on incomplete information from systems that don't talk to each other. And unlike their counterparts at a desk, they have been given almost no real infrastructure to do it with.That is not a management problem. It is an infrastructure problem. This ebook shows what the gaps cost, and how one platform built for the frontline closes them: AI-assisted scheduling, time and attendance connected to payroll, leave that updates the schedule the moment it's approved, and analytics that read across all of it.Who It's ForThis ebook is written for:VPs of Operations balancing coverage, labor cost, and retention across sitesCOOs who need an operation that survives turnoverOperations managers running the schedule on a group text and a spreadsheetFrontline employees who want their shift, swaps, and hours in one placeMulti-site operators in retail, grocery, healthcare, manufacturing, and field serviceWhy Now79% of hourly workers say scheduling is the single biggest factor in whether they stay (Work Institute, 2024)A typical frontline manager touches 5 to 7 disconnected systems to get through one shift cycle50% turnover across 500 frontline workers can cost $1M+ a year to replace (Gallup)At the same time, engaged frontline teams are linked to 23% higher profitability (Gallup), and every gap between systems, the missed punch, the swap that died in a text chain, the overtime nobody saw until payroll ran, quietly leaks cost the operation can't see.What You'll Walk Away WithA clear read on the five information gaps behind most frontline scheduling problemsA cost model for turnover, overtime, and coordination you can run against your own numbersThe questions to ask any scheduling vendor before you signA practical path to closing your biggest gap first, on the systems you already run **Download:** [Shifts & Schedules Book](https://mango-cdn.b-cdn.net/marketing/uploads/mangoapps-shifts-scheduling-ebook.pdf) --- # Performance & Growth Book **Type:** Resource **Published:** 2026-08-03 This ebook makes the case that a review cycle that changes nothing is not a process failure. It is an infrastructure failure. It shows what fragmented performance tools cost in manager hours and lost retention, and how reviews, goals, succession, and skills work when they finally share one data layer instead of separate vendor portals. Performance & GrowthThe Review That Changes Nothing Is an Infrastructure Failure.This ebook is for the VP of Talent Management who knows a completed review form and a meaningful development conversation are not the same thing.When performance data, goal progress, and skills history live in different systems, the manager reconstructs the year rather than reviews it. The conversation that was supposed to drive growth becomes a ritual that drives compliance.That is not a process failure. It is an infrastructure failure. This ebook shows what it costs, and how reviews, goals, succession, and skills change when they share a single data layer.Who It's ForThis ebook is written for:VPs of Talent Management and CHROs connecting today's capabilities to next year's needsHR business partners who own the review, goal, and succession workflowsManagers rebuilding a year of context the night before a reviewPeople teams focused on retention, internal mobility, and readinessRegulated employers tracking skills and certifications that can lapse silentlyWhy NowOnly 14% of employees strongly agree their reviews inspire them to improve (Gallup)A 5,000-employee org can spend 3,000 to 4,000 hours a year just assembling review data, close to two full-time roles (MangoApps model)51% of U.S. employees are actively watching or seeking new jobs (Gallup)At the same time, replacing a manager can cost 200% of their salary, 40% for a frontline worker (Gallup), and the succession plan that looked solid on a slide is often fiction the day the role actually opens.What You'll Walk Away WithA clear read on the four information gaps behind most performance failuresA cost model for the hours and retention lost to reviews rebuilt from memoryWhat continuous, connected performance looks like across reviews, goals, succession, and skillsThe questions to ask any performance-platform vendor, and a path to starting with your biggest gap **Download:** [Performance & Growth Book](https://mango-cdn.b-cdn.net/marketing/uploads/Performance-management-web-small.pdf) --- # The Employee Platform for the AI Era Executive eBook **Type:** Resource **Published:** 2026-07-28 The Employee Platform for the AI Era Executive eBook, written for the C-suite. This edition makes the case that in the AI age, the platform decision comes first. Fragmented tools produce fragmented, ungoverned AI, and 60 to 80% of a frontline workforce stays invisible to the dashboards that drive decisions. See how one platform gives your AI a foundation it can act on safely and gives you one view of who is performing and where the gaps are. Includes the platform overview, executive proof points, and customer results from OU Health, AutoZone, and the Kansas City Chiefs. The Employee Platform for the AI Era Executive eBook Executives at frontline-heavy organizations face two problems at once. First, 60 to 80% of the workforce is invisible to the dashboards that drive decisions. Scheduling compliance, training completion, task close rates, and safety acknowledgments sit scattered across a dozen systems or go untracked. Second, AI is now a board-level conversation, and the enterprises that will use it well are the ones that make a platform decision first. A chatbot on top of disconnected tools cannot act safely across the business. AI needs shared identity, permissions, employee data, workflow context, and governance. That is what a platform provides, and it is why the platform decision matters more than ever. Executives don't buy an intranet or a piece of HR software. They buy an AI-ready platform where the whole workforce, desk and frontline, finally shows up in one place. This edition is written for the CEO, CHRO, COO, CIO, and CFO. It covers the platform story, the executive case for one AI foundation that can act across the business, and the proof behind it: 90%+ adoption in 90 days, 98% customer retention, and results from OU Health, AutoZone, Andersen, and the Kansas City Chiefs, who went from 40% to 90% adoption. **Download:** [The Employee Platform for the AI Era Executive eBook](https://mango-cdn.b-cdn.net/marketing/uploads/AI-Ready-Employee-Platform_WEB-small.pdf) --- # 2026 Workforce Operations Trends eBook **Type:** Whitepapers & Ebooks **Published:** 2026-02-18 This report examines the operational realities behind that pressure. It outlines eight key trends shaping workforce operations — from practical AI adoption and flexible scheduling to continuous performance and upskilling — and shows how connected systems reduce friction without adding overhead. Workforce Operations in 2026How Organizations Are Simplifying Systems, Increasing Flexibility, and Keeping Frontline Operations Running at ScaleWorkforce operations are under growing pressure.In 2026, organizations must control costs, manage talent shortages, and adapt to constant change — all while running complex, frontline-heavy operations. Too often, scheduling, performance, communication, and workforce systems were never designed to work together.This report examines the operational realities behind that pressure. It outlines eight key trends shaping workforce operations — from practical AI adoption and flexible scheduling to continuous performance and upskilling — and shows how connected systems reduce friction without adding overhead.Who It’s ForThis guide is designed for:Operations leaders responsible for frontline executionWorkforce and scheduling managers balancing coverage and costHR partners supporting performance and retentionFrontline managers coordinating day-to-day workOrganizations seeking to simplify fragmented operational systemsWhy Now89% of CEOs expect AI to redefine value creation72% anticipate greater reliance on gig and flexible workers83% of workers report burnout, with frontline turnover often exceeding 70%At the same time, lack of career development is now the #1 reason frontline employees leave, and managers struggle to address underperformance in real time.The old model — rigid schedules, annual reviews, siloed systems — can’t keep pace. Workforce operations now require flexibility, visibility, and connected execution.What You’ll Walk Away WithA clear understanding of the 8 trends reshaping workforce operations in 2026Insight into how fragmented systems increase manager workload and slow executionA practical path toward more flexible scheduling, continuous performance, and AI-powered coordination **Download:** [2026 Workforce Operations Trends eBook](https://mango-cdn.b-cdn.net/images/marketing/resources/2026-Workforce-Operations-Trends-eBook.pdf) --- # 2026 Internal Communications Trends eBook **Type:** Whitepapers & Ebooks **Published:** 2026-02-18 This report outlines 12 trends reshaping internal communications — from managing change fatigue and empowering managers to adopting AI responsibly and proving impact with data. It shows how unified systems help communicators reach every employee with clarity, relevance, and measurable results. Reaching Every Employee in 2026What Modern Internal Communications Requires in a Distributed, Frontline-Heavy WorkforceInternal communications has moved from a support function to a business-critical operating role.In 2026, communicators are expected to reach a more distributed and frontline-heavy workforce while cutting through digital noise, rebuilding trust, and keeping employees aligned during constant change. The old model of broadcasting messages and hoping they land no longer works.This report outlines 12 trends reshaping internal communications — from managing change fatigue and empowering managers to adopting AI responsibly and proving impact with data. It shows how unified systems help communicators reach every employee with clarity, relevance, and measurable results.Who It’s ForThis guide is designed for:Internal communications leaders responsible for enterprise-wide messagingCorporate communications teams supporting distributed and frontline employeesHR and people teams partnering on engagement and alignmentManagers tasked with cascading updates and reinforcing strategyOrganizations struggling with disengagement, misalignment, and information overloadWhy NowOnly 23% of employees report feeling engaged25% of leaders say breaking through noise is their biggest communication challengeJust 9% of employees feel fully aligned with company goalsAt the same time, nearly 6 in 10 employees are “quiet quitting,” trust in leadership remains low, and change fatigue continues to rise.Communicators are no longer measured by what was sent. They’re measured by what was understood, acted on, and reinforced. This report shows how to close that gap.What You’ll Walk Away WithA clear view of the 12 trends defining internal communications in 2026Practical strategies to reduce noise, strengthen manager enablement, and drive two-way dialogueA path toward measurable, aligned communication that reaches desk and frontline employees alike‍ **Download:** [2026 Internal Communications Trends eBook](https://mango-cdn.b-cdn.net/images/marketing/resources/2026-Internal-Comms-Trends-eBook_MangoApps.pdf) --- # 2026 HR Trends eBook **Type:** Whitepapers & Ebooks **Published:** 2026-02-18 This report examines the real forces reshaping HR in 2026. It outlines eleven practical trends across technology, talent, culture, and leadership — and shows how unified systems can reduce friction, strengthen retention, and help managers keep daily work moving. Supporting Frontline Employees in 2026How HR Is Adapting Systems, Skills, and Support for a Distributed WorkforceSupporting employees has become one of HR’s most complex responsibilities.As organizations grow more distributed and frontline-heavy, HR teams are expected to support shifting roles, changing expectations, and constant disruption — often across systems that were never designed to work together.This report examines the real forces reshaping HR in 2026. It outlines eleven practical trends across technology, talent, culture, and leadership — and shows how unified systems can reduce friction, strengthen retention, and help managers keep daily work moving.Who It’s ForThis report is designed for:HR leaders supporting desk and frontline teamsCHROs navigating AI adoption and system consolidationPeople operations teams focused on retention and internal mobilityIT leaders tasked with simplifying fragmented HR technologyOrganizations managing distributed, shift-based workforcesWhy NowOnly 5% of HR teams feel fully prepared to implement AI effectively68% of companies operate with disconnected HR systemsFrontline turnover remains nearly double the average across industriesAt the same time, 1 in 5 employees will need redeployment by 2030, and burnout-driven turnover continues to drain payroll and productivity.What You’ll Walk Away WithA clear understanding of the 11 trends shaping HR in 2026Insight into how fragmented systems impact retention, mobility, and performanceA practical path toward simplifying support, embedding AI responsibly, and strengthening the frontline manager experience **Download:** [2026 HR Trends eBook](https://mango-cdn.b-cdn.net/images/marketing/resources/2026-HR-Trends-eBook_MangoApps.pdf) --- # Enabling Easy Communication at the American College of Radiology **Type:** Customer Case Studies **Published:** 2026-02-16 How the American College of Radiology Simplified Communication and Collaboration Across a Nationwide WorkforceThe American College of Radiology (ACR) represents more than 38,000 radiologists, radiation oncologists, nuclear medicine physicians, and medical physicists nationwide. With over 450 employees supporting that mission, ACR needed a better way to keep staff aligned, informed, and connected across departments and locations  .As a national organization, ACR was managing internal communication across a wide-reaching workforce. Email overload made it difficult to cut through the noise. Teams needed a central place for news, department information, events, and collaboration—without adding more complexity.To address this, ACR partnered with MangoApps to create a centralized digital hub that brings company updates, department resources, calendars, and collaboration tools into one unified experience.Key OutcomesCentralized communication: ACR reduced reliance on email and created one digital destination for company-wide updates.‍Stronger cross-department awareness: Public department pages and org charts improved visibility and connection across teams.‍Simplified scheduling: A personalized master calendar brought events and reminders together in one place.‍Effective remote collaboration: Distributed teams gained a reliable, shared workspace to collaborate and communicate seamlessly.‍Ongoing adaptability: ACR continues to evolve how it shares knowledge and engages employees within a flexible, unified platform. **Download:** [Enabling Easy Communication at the American College of Radiology](https://mango-cdn.b-cdn.net/images/marketing/resources/CaseStudy_ACR.pdf) --- # ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report **Type:** Analyst Report **Published:** 2026-02-04 The most comprehensive, independent analysis of leading intranet and employee experience platforms used by large and distributed organizations.‍ClearBox Consulting’s latest report provides an in-depth, scenario-based evaluation of today’s leading intranet and employee experience platforms — including MangoApps.What’s inside the ClearBox reportClearBox Consulting evaluates platforms using a practical, scenario-based framework designed to reflect how organizations actually work.The report includes:Independent analysis of leading intranet and EX platformsEvaluation across 8 real-world scenariosScenario-level scores and detailed commentaryClearBox’s perspective on MangoApps‍ClearBox's Perspective on MangoApps at a GlanceIn the 2026 report, ClearBox positions MangoApps as one of the most comprehensive platforms reviewed, highlighting its ability to unify communication, knowledge, engagement, and frontline support in a single, configurable experience.‍Download the full report to see how MangoApps and other leading platforms compare across real-world use cases that matter to large, complex organizations. **Download:** [ClearBox Consulting's 2026 Intranet and Employee Experience Platforms Report](https://mango-cdn.b-cdn.net/resources/newpdfs/2026%20ClearBox%20Consulting%20Intranet%20and%20Employee%20Experience%20Platforms%20Report_v5.0_MangoApps.pdf) --- # Internal Comms: Why Employees Don't Need Email Accounts **Type:** Webinars **Published:** 2026-01-13 Watch this video where we discuss why organizations are shifting away from email and instead adopting a modern digital work hub for their employee communications. --- # HR Team Planning Calendar For 2026 **Type:** Whitepapers & Ebooks **Published:** 2025-12-03 This calendar is a comprehensive resource for HR professionals to plan, engage, and inspire throughout the year. Whether you're focused on employee experience, compliance, or cultural initiatives, it equips you with the tools and insights to stay ahead. This calendar is a comprehensive resource for HR professionals to plan, engage, and inspire throughout the year. Whether you're focused on employee experience, compliance, or cultural initiatives, it equips you with the tools and insights to stay ahead.Key Features:Monthly HR Tips – Get practical strategies for employee engagement, wellness, compliance, and talent management.‍Essential HR Dates – Stay on top of key milestones like National Mentoring Month, Employee Appreciation Day, and Open Enrollment.‍Goal & Task Tracking – Set clear objectives, track HR initiatives, and reflect on achievements.‍Engagement & Culture Focus – Align HR efforts with DEI initiatives, team-building activities, and workplace wellness programs.Whether you’re planning major HR initiatives or looking for fresh ideas to boost employee morale, the MangoApps 2026 HR Calendar keeps you organized, prepared, and ready to make an impact. **Download:** [HR Team Planning Calendar For 2026](https://mango-cdn.b-cdn.net/resources/newpdfs/2026-HR-calendar.pdf) --- # Internal Communications Planning Calendar For 2026 **Type:** Whitepapers & Ebooks **Published:** 2025-12-03 The MangoApps 2026 Internal Comms Planning Calendar is your go-to resource for a year of creative, impactful communications. Packed with holidays, engagement ideas, and planning tools, this calendar is designed to lighten your load and inspire action. The MangoApps 2026 Internal Comms Planning Calendar is your go-to resource for a year of creative, impactful communications. Packed with holidays, engagement ideas, and planning tools, this calendar is designed to lighten your load and inspire action.Key Takeaways:Month-by-Month Inspiration: Discover five creative content ideas each month to spark engagement and keep employees informed and motivated.Tips for Strategic Planning: Learn how to structure your communications for maximum impact, balancing informational, engaging, and action-oriented posts.To-Do Lists and Goal Setting: Stay organized with monthly task lists and goals to track your progress throughout the year.Focus on Employee Connection: Use inclusive themes, fun celebrations, and meaningful recognition to foster a sense of community and collaboration.Practical Holiday Ideas: From Lunar New Year to National Trivia Day, the calendar includes unique holiday post concepts to add creativity to your messaging.Why Use This Calendar? Whether you’re juggling multiple campaigns or seeking fresh ideas to boost morale, the 2026 Internal Comms Planning Calendar equips you with everything you need to create an effective, engaging, and enjoyable communications strategy for the year ahead.‍ **Download:** [Internal Communications Planning Calendar For 2026](https://mango-cdn.b-cdn.net/resources/newpdfs/2026-IC-calendar.pdf) --- # Solution Brief: MangoApps Shifts & Schedules **Type:** Whitepapers & Ebooks **Published:** 2025-11-10 How to Fix Turnover by Rethinking Scheduling, Timekeeping, and Daily OperationsEvery frontline leader we talk to says the same thing: “We can’t hire fast enough.”But hiring isn’t the real problem—retention is. Unpredictable schedules, missed shift changes, and other small frustrations chip away at trust until people leave.This guide lays out a practical approach to stabilizing your frontline, reducing turnover, and restoring consistency. It shows how smarter schedules and connected operations can transform your workforce from reactive to resilient.Who It’s ForThis guide is designed for:Operations and HR leaders struggling with frontline churnIT professionals looking to unify disconnected toolsWorkforce managers who need better visibility and controlAnyone supporting shift-driven teams in healthcare, retail, manufacturing, and moreWhy Now📊 79% of hourly employees say scheduling is the #1 factor in staying at a job⏱️ Even one disruption every two weeks increases an employee’s likelihood of leaving by 20%⚠️ Legacy scheduling tools and point solutions can’t keep up with modern expectationsWith AI and mobile tools, you can take back control. This guide shows you how.What You’ll Walk Away WithA clear strategy to reduce turnover by improving scheduling and daily workflowsA breakdown of the core technologies that enable smarter, more flexible operationsA path toward higher retention, smoother execution, and a more resilient frontline team **Download:** [Solution Brief: MangoApps Shifts & Schedules](https://mango-cdn.b-cdn.net/marketing/uploads/Mango-Shifts-Schedules.pdf) --- # How Santee Cooper’s ‘The Coop’ Builds Connection Across Every Corner of its Workforce **Type:** Customer Case Studies **Published:** 2025-10-09 With crews in the field, teams in plants, and staff in offices, Santee Cooper needed a way to reach everyone with the same clarity and care. Using MangoApps, they created The Coop—a mobile-friendly hub where employees can read updates, share recognition, and access tools in seconds. It’s helped transform internal communication from fragmented to truly connected. How South Carolina’s Public Utility Connected Every Employee—From the Office to the Field—with a Unified Digital HubSantee Cooper, South Carolina’s public, not-for-profit electric and water utility, serves more than two million residents with help from over 1,600 employees spread across offices, power plants, and field sites.For years, connecting those employees—especially those without regular computer access—was a challenge. Leadership updates, safety alerts, and recognition efforts often struggled to reach the entire workforce.To bridge the gap, Santee Cooper partnered with MangoApps to create “The Coop,” a unified employee hub that brings everyone into the same conversation. The Coop combines communications, recognition, forms, and feedback into one easy-to-access platform—available on desktop and mobile for every employee, from turbine floors to corporate offices.Key OutcomesOne connected workforce: Field and office employees now share one digital home for company news, storm alerts, and updates.Stronger culture of recognition: Peer-to-peer recognition posts doubled, turning private thanks into visible celebrations.Faster onboarding: New hires connect to culture, tools, and people from day one through mobile-friendly access.Data-driven communication: Surveys and analytics give leaders real-time insight into employee sentiment and engagement.Sustained partnership: With ongoing support from MangoApps, The Coop continues to evolve alongside Santee Cooper’s mission.‍"People in the field can sometimes be disconnected with what’s happening corporate-wide. That’s just a natural result when your jobsite is a turbine floor or a bucket truck. That means a lot of our folks have limited access to a computer. The Coop gives us a way to close that gap."‍- Jeffrey Straight, Public Relations Specialist at Santee Cooper ## Key Outcomes - One connected workforce: Field and office employees now share one digital home for company news, storm alerts, and updates. - Stronger culture of recognition: Peer-to-peer recognition posts doubled, turning private thanks into visible celebrations. - Faster onboarding: New hires connect to culture, tools, and people from day one through mobile-friendly access. **Download:** [How Santee Cooper’s ‘The Coop’ Builds Connection Across Every Corner of its Workforce](https://mango-cdn.b-cdn.net/images/marketing/resources/CaseStudy_SanteeCooper.pdf) --- # Break The Annual Review Cycle: The Executive’s Guide To Creating A Culture Of Continuous Employee Development **Type:** Whitepapers & Ebooks **Published:** 2025-09-04 Break the Annual Review Cycle: The Executive’s Guide to Continuous Employee DevelopmentTraditional performance management is broken. Annual reviews and siloed tools leave leaders reacting to problems instead of preventing them. Gut-based decisions and fragmented data make it nearly impossible to retain top talent or plan for the future.This guide shows how to flip the script. By uniting predictive analytics with an integrated operations platform, organizations gain real-time visibility into employee performance, engagement, and growth. Instead of looking backward, you’ll be equipped to forecast trends, spot risks early, and build stronger teams.Who It’s ForThis guide is designed for:HR leaders ready to modernize outdated review processesOperations executives seeking visibility across the workforceIT teams tasked with unifying scattered performance dataAny organization looking to grow, retain, and develop talent at scaleWhy Now📉 Annual reviews alone are failing to prevent turnover and skill gaps📱 Employees expect intuitive, mobile-friendly performance tools📊 Predictive analytics can now forecast performance, retention risks, and succession needsWith today’s technology, organizations can move from reactive to proactive talent management.What You’ll Walk Away WithA roadmap for integrating predictive analytics into your talent strategyBest practices for building a continuous performance cultureA clear path to higher engagement, better retention, and stronger leadership pipelines‍ **Download:** [Break The Annual Review Cycle: The Executive’s Guide To Creating A Culture Of Continuous Employee Development](https://mango-cdn.b-cdn.net/marketing/uploads/EPMS-whitepaper.pdf) --- # The Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026 and beyond **Type:** Whitepapers & Ebooks **Published:** 2025-07-29 The Ultimate Intranet Buyer’s Guide for a Frontline Workforce in 2026 and Beyond‍A must-read for internal comms, HR, and IT leaders supporting deskless teams. This practical guide explores how to evaluate intranet platforms, avoid common pitfalls, and drive ROI—tailored specifically for the unique needs of the frontline workforce. Includes platform comparison checklists, success metrics, and future-ready intranet strategies. Your 2026 Frontline Intranet Buyer’s Guide is HereHow to Choose a Platform That Actually Works for Deskless TeamsChoosing the right intranet platform for your frontline workforce has never been more critical—or more confusing. With vendor claims sounding the same and workplace needs evolving fast, this guide is your roadmap to making a confident, future-ready decision.What’s Inside:Key challenges unique to frontline workers—and how the right intranet can solve them.A framework for comparing platforms based on real business impact.Checklists, benchmarks, and questions to ask vendors.Tips to drive adoption, engagement, and measurable ROI.Insights from real-world deployments in retail, healthcare, logistics, and more.Why It Matters:Frontline workers make up 80% of the global workforce, yet most intranets were never designed for them. This guide shows what’s different in 2026—and what to look for in a platform built for their success. **Download:** [The Ultimate Intranet Buyer's Guide for a Frontline Workforce in 2026 and beyond](https://mango-cdn.b-cdn.net/marketing/uploads/Intranet-Buyers-Guide-Frontline-Workforce.pdf) --- # What is MangoApps? (Overview Video) **Type:** Product Demos **Published:** 2025-07-25 Discover MangoApps: Your All-in-One Employee HubTired of juggling disconnected tools, missed messages, and frustrated teams? Meet MangoApps—your unified digital workspace built to bring clarity, connection, and efficiency to every employee, whether they’re at a desk or on the frontlines. Discover MangoApps: Your All-in-One Employee HubTired of juggling disconnected tools, missed messages, and frustrated teams? Meet MangoApps—your unified digital workspace built to bring clarity, connection, and efficiency to every employee, whether they’re at a desk or on the frontlines.In this video tour, you’ll see how MangoApps transforms the employee experience by:Centralizing communication, collaboration, and knowledge in one platformEmpowering frontline and desk workers alike with mobile-first accessReplacing intranets, chat apps, and task tools with one intuitive hubWatch now to see how organizations like PetSmart, OU Health, and TeamHealth use MangoApps to engage thousands of employees—on day one and every day after. --- # Scaling Rapid Growth Through a Unified Platform for Communication, AI, and IT Efficiency **Type:** Customer Case Studies **Published:** 2025-06-13 How a high-growth pharmaceutical commercialization startup replaced silos with a scalable, AI-powered employee hubPetauri was built to move fast. In just over a year, the company launched, acquired, and combined multiple best-in-class commercialization firms across the U.S. and U.K.—growing to over 400 employees while building its core infrastructure from the ground up.To unify newly acquired teams and systems while maintaining speed and flexibility, Petauri turned to MangoApps.Now branded internally as Springboard, MangoApps serves as Petauri’s centralized intranet and employee platform—bringing together communications, knowledge, and AI Assistants in one seamless digital experience. From onboarding to AI-powered support, Springboard enables every employee to feel connected, informed, and empowered from day one.‍ How a high-growth pharmaceutical commercialization startup replaced silos with a scalable, AI-powered employee hubPetauri was built to move fast. In just over a year, the company launched, acquired, and combined multiple best-in-class commercialization firms across the U.S. and U.K.—growing to over 400 employees while building its core infrastructure from the ground up.To unify newly acquired teams and systems while maintaining speed and flexibility, Petauri turned to MangoApps.Now branded internally as Springboard, MangoApps serves as Petauri’s centralized intranet and employee platform—bringing together communications, knowledge, and AI Assistants in one seamless digital experience. From onboarding to AI-powered support, Springboard enables every employee to feel connected, informed, and empowered from day one.Key OutcomesRapid onboarding: New hires from across acquired companies get immediate access to tools, policies, and company cultureAI Assistants in action: Internal-facing Assistants trained on company content deflect repetitive support requests and enhance productivitySingle source of truth: Centralized communications, governance, and policy updates for a distributed workforceLeadership alignment: Executives use the platform daily to share updates, model behavior, and build trustEnterprise-ready governance: SSO, audit logging, and secure prompt tracking support compliance and scale‍“MangoApps became the glue that holds our fast-growing company together. It gives every new employee—from newly acquired teams to recent hires—an immediate sense of belonging and access to everything they need.” — Jeff Petet, Senior VP of IT, Petauri ## Key Outcomes - Rapid onboarding: New hires from across acquired companies get immediate access to tools, policies, and company culture - AI Assistants in action: Internal-facing Assistants trained on company content deflect repetitive support requests and enhance productivity - Single source of truth: Centralized communications, governance, and policy updates for a distributed workforce **Download:** [Scaling Rapid Growth Through a Unified Platform for Communication, AI, and IT Efficiency](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_Petauri.pdf) --- # From Concept to Success: How symplr Leverages MangoApps for an Effective Rewards and Recognition Program **Type:** Webinars **Published:** 2025-05-28 See how one global company transformed scattered acts of appreciation into a seamless, culture-driven experience — right inside their intranet.In this 45-minute recorded session, the team at symplr pulls back the curtain on how they built and launched a company-wide Rewards & Recognition program that actually stuck. No gimmicks. No add-on apps. Just smart strategy, strong partnerships, and the power of MangoApps.You’ll hear real stories from:Melissa Hoyos, VP of Internal CommunicationsJami Mims, Director of Talent ManagementKevin Williams, Director of HR OperationsEmily Biery, Senior Internal Communications SpecialistOlivia Aguilar, Intranet Engagement Specialist‍Watch to learn:Why recognition needed a new home — and why MangoApps made senseHow symplr approached the rollout, from leadership buy-in to design detailsWhat it took to maintain momentum after launchTips for building a program that aligns with culture (not just processes)Whether you’re starting from scratch or rethinking your current strategy, this session is packed with lessons you can adapt to your own workplace. --- # Intranet & Employee Experience Platform RFP Template **Type:** Templates **Published:** 2025-05-27 Choose the right platform with confidence.‍Evaluating intranet and employee experience solutions? Start with a proven framework. Our downloadable RFP toolkit gives you everything you need to structure a clear, comprehensive request for proposal—saving you time and helping vendors provide better, more tailored responses.What’s Inside:Editable Word RFP Template: A structured, professional RFP document you can easily tailor to your organization’s goals, technical requirements, and selection process.Detailed Excel Vendor Questionnaire: A companion spreadsheet aligned with the RFP’s functional requirements section—perfect for side-by-side vendor comparisons.Plain Text Instructions File: Quick-start guidance to help your team understand how to use the templates efficiently.‍Why Use This Toolkit?Built by intranet and employee experience experts based on years of experience responding to RFPs just like the ones you'll issue. Covers all key areas: AI capabilities, mobile access, integrations, security, support & more!Helps you identify the right partner—not just the right product.‍Fill out the form to get instant access to the files.These templates are free to use and fully customizable—ideal for IT, HR, internal comms, or procurement teams leading digital workplace initiatives. **Download:** [Intranet & Employee Experience Platform RFP Template](https://mango-cdn.b-cdn.net/marketing/uploads/MangoApps_Intranet___EX_RFP_Template_2.zip) --- # MangoApps For External Collaboration **Type:** Whitepapers & Ebooks **Published:** 2025-03-28 What You Will Learn:MangoApps enables seamless external collaboration with partners, clients, consultants, and vendors through a secure and flexible file management system. Offering tailored guest user experiences and robust file control, MangoApps ensures efficient document sharing and collaboration across organizations. - Create a central hub for seamless collaboration with external partners, enabling effective project management, communication, and file sharing- Implement aflexible, secure platform for working with clients, partners, vendors, and external collaborators to streamline file sharing processesDownload MangoApps for External Collaboration and discover how MangoApps can streamline collaboration with your outside clients, partners, vendors, and more! ‍‍ **Download:** [MangoApps For External Collaboration ](https://mango-cdn.b-cdn.net/marketing/uploads/MangoApps_External_File_Collaboration_Tools.pdf) --- # The AI-Powered Intranet Blueprint: A Strategic Guide to Planning, Selecting, and Implementing the Right Solution **Type:** Whitepapers & Ebooks **Published:** 2025-03-27 The way we work is changing fast. With hybrid models, digital transformation, and now AI redefining the employee experience, organizations are rethinking how they connect, inform, and empower their people. But for many companies, intranets haven’t kept pace—and it’s time they did.This guide walks you through the essential steps to planning, selecting, and implementing an intranet built for the future. Whether you're exploring AI-powered features for the first time or looking to level up your digital workplace, this guide provides the clarity and structure you need to move forward with confidence.What You’ll Learn:Why traditional intranets are falling short—and how AI changes the game.How to identify gaps in your current digital workplace solutions. What AI capabilities to look for in a modern intranet (think intelligent search, personalization, automation, and more).How to evaluate vendors and cut through the hype.Proven strategies for driving adoption and long-term success.From assessing business needs to managing change, The AI-Powered Intranet Blueprint offers a complete framework to help you take the next step toward a more intelligent digital workplace.Who Should Download the Blueprint?This guide is designed for internal communications, HR, IT, and digital workplace leaders tasked with creating a more connected, intelligent, and efficient employee experience. Whether you’re just starting your intranet project or re-evaluating an existing one, this guide gives you the blueprint for success. **Download:** [The AI-Powered Intranet Blueprint: A Strategic Guide to Planning, Selecting, and Implementing the Right Solution](https://mango-cdn.b-cdn.net/marketing/uploads/The-AI-Powered-Intranet.pdf) --- # MangoApps Employee Onboarding Tools **Type:** Whitepapers & Ebooks **Published:** 2025-03-25 What You Will Learn:Streamline the new-hire experience and ensure employees feel engaged and prepared from day one. By utilizing MangoApps’ many onboarding-friendly features, admins can create a seamless transition for all new members of your company—-whether they’re employed at the office or on the frontlinesGroups give new employees a space to connect with each other and ask questions, as well as find helpful resources relevant to the new-hire experience.Tasks allow admins to automatically assign essential onboarding to-dos, including LMS courses, to new hires effortlessly. Campaigns create memorable first impressions via personalized journeys that both inform and engage recent recruits.And more! Download the Employee Onboarding Tools overview and discover how MangoApps can streamline your onboarding process and empower your new hires! ‍‍ **Download:** [MangoApps Employee Onboarding Tools](https://mango-cdn.b-cdn.net/marketing/uploads/MangoApps_Employee_Onboarding_Tools_.pdf) --- # MangoApps x Google Integrations **Type:** Whitepapers & Ebooks **Published:** 2025-03-20 What You Will Learn:Effortless User Management: Simplify authentication and provisioning with seamless integration into Google Workplace (OAUTH 2.0), Google Cloud Identity (LDAP), and Google SSO (SAML) Streamlined File Sharing & Collaboration: Edit and share files in real-time with Google Drive integration—no additional licenses required.‍‍Productivity Boost: Stay connected with native integrations for GoogleDrive, Google Calendar, and all other GSuite Apps directly within MangoApps.‍‍Download the Google Integrations Guide and discover how MangoApps can simplify your workflow and empower your team.‍‍ **Download:** [MangoApps x Google Integrations](https://mango-cdn.b-cdn.net/marketing/uploads/MangoApps-Google_Integrations.pdf) --- # Employee App Best Practices **Type:** Whitepapers & Ebooks **Published:** 2025-03-14 What’s the best way to implement an employee app? How can you be sure staff will utilize it? In this guide, we’ll cover the ins and outs of launching a successful employee app—from content strategy to mobile adoption—so that you can enhance the employee experience at your organization. Key FeaturesCollaboration TechniquesContent Strategy GuidesAdoption TipsLaunch Day Activity IdeasEngagement Tips‍ **Download:** [Employee App Best Practices](https://mango-cdn.b-cdn.net/marketing/uploads/Employee_App_Best_Practices.pdf) --- # Operation Modern Intranet: A Guide to Planning a Successful Intranet Launch **Type:** Whitepapers & Ebooks **Published:** 2025-01-23 Traditional intranets no longer meet the needs of today’s dispersed, digital-first workplaces. Employees require a modern solution that unifies tools, fosters collaboration, and delivers an exceptional employee experience. However, launching a modern intranet can feel like a daunting mission.This guide provides a step-by-step roadmap for business leaders and project managers to plan, develop, and execute a successful intranet launch. Backed by MangoApps' expertise, this resource simplifies the process, ensuring your organization can deploy an intranet that meets the demands of a modern workforce.Key Takeaways:Create a Business Case: Effectively outline the risks of outdated systems and highlight the value of a modern intranet for securing leadership buy-in.Engage Key Stakeholders: Learn to involve CEOs, CHROs, and other executives to champion your intranet initiative.Focus on User Needs: Understand how to design and launch an intranet that serves both desk-based and frontline employees.Plan for Success: Use actionable tips to manage content, timelines, and resources for a smooth implementation.Drive Adoption: Explore techniques for personalized experiences, intuitive navigation, and robust post-launch engagement.Why Read This Guide?This guide is the ultimate resource for organizations looking to modernize their intranet while avoiding common pitfalls. Whether you’re seeking to streamline workflows, boost employee engagement, or simplify tech integration, this roadmap will help you achieve a seamless launch that maximizes ROI. **Download:** [Operation Modern Intranet: A Guide to Planning a Successful Intranet Launch](https://mango-cdn.b-cdn.net/marketing/uploads/Operation-Modern-Intranet-Launch-Guide.pdf) --- # Unified Intranet & Employee App Features **Type:** Resource **Published:** 2025-01-10 **Download:** [Unified Intranet & Employee App Features](https://mango-cdn.b-cdn.net/resources/newpdfs/Unified%20Intranet%20%26%20Employee%20App%20Features.pdf) --- # Strengthening Connections & Culture: Full House’s Success with MangoApps **Type:** Customer Case Studies **Published:** 2025-01-07 Full House Case StudyFull House, a chain of 19 furniture stores in South Africa, needed a way to maintain strong connections with employees and customers while addressing operational inefficiencies across their widespread locations. MangoApps, branded internally as "LekkaChat," became their solution to unify communications and streamline operations.With MangoApps, Full House strengthened its culture, streamlined operations, and improved employee engagement, all while preserving its deep community ties.‍ Full House Case StudyFull House, a chain of 19 furniture stores in South Africa, needed a way to maintain strong connections with employees and customers while addressing operational inefficiencies across their widespread locations. MangoApps, branded internally as "LekkaChat," became their solution to unify communications and streamline operations.Since adopting MangoApps, Full House has achieved the following:Real-time communication replaced inconsistent email chains, ensuring employees stay informed.Employee engagement increased through features like a newsfeed for celebrating store achievements.Integration with Power BI provided easy access to KPIs and sales data.Tools like the Learning module and AI Helper improved efficiency in training and resource management.With MangoApps, Full House strengthened its culture, streamlined operations, and improved employee engagement, all while preserving its deep community ties.Download this case study to learn how MangoApps helped Full House connect, engage, and succeed across all locations.‍ **Download:** [Strengthening Connections & Culture: Full House’s Success with MangoApps](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_Full-House.pdf) --- # Connecting 14 Locations With a Centralized Digital Platform **Type:** Customer Case Studies **Published:** 2024-10-28 Paul Miller Auto Group Case StudyPaul Miller Auto Group, a well-established company with 14 dealership locations around New Jersey, faced the challenge of unifying their operations and streamlining processes across all locations. Each dealership previously operated independently, leading to inefficiencies in communication, inventory tracking, and corporate functions.When Hayes Miller, the Director of Communications, took on the task of centralizing their operations, MangoApps emerged as the ideal solution. Branded internally as "Podium" due to their connection with BMW Racing, the platform has transformed Paul Miller’s business, making it easier for employees to access information, communicate across locations, and streamline operations. Paul Miller Auto Group Case StudyPaul Miller Auto Group, a well-established company with 14 dealership locations around New Jersey, faced the challenge of unifying their operations and streamlining processes across all locations. Each dealership previously operated independently, leading to inefficiencies in communication, inventory tracking, and corporate functions.When Hayes Miller, the Director of Communications, took on the task of centralizing their operations, MangoApps emerged as the ideal solution. Branded internally as "Podium" due to their connection with BMW Racing, the platform has transformed Paul Miller’s business, making it easier for employees to access information, communicate across locations, and streamline operations.Since adopting MangoApps, Paul Miller Auto Group has seen significant improvements:A unified platform allows for consistent communication across 14 dealership locations.Operational inefficiencies were reduced, particularly in inventory tracking and daily reporting.The centralized platform has simplified IT processes through single sign-on (SSO), making onboarding and offboarding faster and more secure.Employee engagement has increased, with easier access to company information, event updates, and policies.HR inquiries have decreased significantly with tools like the centralized payroll calendar.Download this case study to learn how MangoApps helped Paul Miller Auto Group improve operational efficiency and streamline communication across their multiple locations.‍ **Download:** [Connecting 14 Locations With a Centralized Digital Platform](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_PaulMiller.pdf) --- # Connecting 20,000 Employees: The Raley’s Companies’ Success Story With MangoApps **Type:** Customer Case Studies **Published:** 2024-10-22 The Raley's Companies Case StudyWhen The Raley’s Companies acquired Bashas’ Family of Stores, they faced the challenge of uniting over 20,000 employees across two popular grocery chains operating in four U.S. states. With each brand having its own cultural strengths and systems for communication, The Raley’s Companies needed a unified platform that could bring their workforce together without losing the individual strengths of each brand.After evaluating several options, they chose MangoApps for its powerful combination of intranet and communication functionality and the personal partnership offered by the MangoApps team. This collaboration enabled them to seamlessly merge their teams onto a single platform—The Hive, an employee experience system that reflected the unique culture of The Raley’s Companies. The Raley's Companies Case StudyWhen The Raley’s Companies acquired Bashas’ Family of Stores, they faced the challenge of uniting over 20,000 employees across two popular grocery chains operating in four U.S. states. With each brand having its own cultural strengths and systems for communication, The Raley’s Companies needed a unified platform that could bring their workforce together without losing the individual strengths of each brand.After evaluating several options, they chose MangoApps for its powerful combination of intranet and communication functionality and the personal partnership offered by the MangoApps team. This collaboration enabled them to seamlessly merge their teams onto a single platform—The Hive, an employee experience system that reflected the unique culture of The Raley’s Companies.Since the rollout of MangoApps, The Raley’s Companies have experienced significant benefits:They successfully unified their workforce under one platform while preserving the strengths of both brands.They democratized content management, empowering different teams to manage their own materials.Frontline employees are now fully included in the communication process, ensuring better customer experiences.The Hive has reduced reliance on email, improved governance, and boosted daily usage across all teams.Download this case study to discover how The Raley’s Companies transformed their communication, collaboration, and employee engagement with MangoApps.‍ **Download:** [Connecting 20,000 Employees: The Raley’s Companies’ Success Story With MangoApps](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_Raleys.pdf) --- # MangoApps & Microsoft Integration Guide **Type:** Whitepapers & Ebooks **Published:** 2024-09-16 What You Will Learn:Effortless User Management: Simplify authentication and provisioning with seamless integration into Microsoft Active Directory, ADFS, Azure, and more.‍Streamlined File Sharing & Collaboration: Edit and share files in real-time with SharePoint and OneDrive integration—no additional licenses required.‍‍Productivity Boost: Stay connected with native integrations for Microsoft Teams, Outlook, Power BI, and more, directly within MangoApps.‍‍Download the Microsoft Integrations Guide and discover how MangoApps can simplify your workflow and empower your team.‍‍ **Download:** [MangoApps & Microsoft Integration Guide](https://mango-cdn.b-cdn.net/marketing/uploads/MangoApps_Microsoft_Integrations.pdf) --- # A New Generative AI Solution For Your Company **Type:** Whitepapers & Ebooks **Published:** 2024-07-31 In the last year, the push to adopt AI has grown, driven by its potential to vastly improve work efficiency and innovation. However, businesses have faced challenges in deployment, cost, and security, finding it hard to fully utilize AI’s capabilities.This book lays out a clear, actionable framework for business leaders to understand the practical application of AI in the digital workplace, and how MangoApps is uniquely positioned to serve that need. With MangoApps, you can:Deploy Generative AI Easily: Simplify the integration of cutting-edge AI technologies, and make them readily available to every employee in a centralized portal.Train AI on Enterprise Data: Empower your AI solutions to learn directly from your own data, ensuring outputs are highly relevant and tailored to your specific business contextEnsure Secure and Compliant Use: Operate with the assurance that your AI deployments are safeguarded within an enterprise-grade security frameworkAchieve Economical Scalability: Scale AI solutions across your organization without the worry of prohibitive costs or complex management overheadPersonalize AI For All Employees: Deploy AI assistants that offer tailored support, from searching for information and finding experts to addressing general employee needs, ensuring every team member benefits from customized assistance.And More!Download for a crash course in Generative AI for the enterprise and a concrete list of action items that will help you realize the benefits of this cutting-edge technology in your organization. ‍ **Download:** [A New Generative AI Solution For Your Company](https://mango-cdn.b-cdn.net/marketing/uploads/MangoApps_AI_Book.pdf) --- # MangoApps vs. WorkVivo **Type:** Whitepapers & Ebooks **Published:** 2024-07-16 Comparing MangoApps Against WorkVivoWhen comparing MangoApps and WorkVivo, it’s clear that each has its ideal fit. WorkVivo, now part of Zoom, offers a solid option for companies already deeply integrated with the Zoom platform and looking for straightforward communication solutions that fit seamlessly in that experience. However, MangoApps provides a more comprehensive platform, combining communication, intranet, and more – ideal for businesses needing extensive customization and functionality. Discover why many enterprises prefer MangoApps for its powerful, flexible features designed to enhance communication, collaboration, and productivity across the organization. Make an informed choice by understanding how MangoApps can meet and exceed your team’s needs. Comparing MangoApps Against WorkVivoWhen comparing MangoApps and WorkVivo, it’s clear that each has its ideal fit. WorkVivo, now part of Zoom, offers a solid option for companies already deeply integrated with the Zoom platform and looking for straightforward communication solutions that fit seamlessly in that experience. However, MangoApps provides a more comprehensive platform, combining communication, intranet, and more – ideal for businesses needing extensive customization and functionality. Discover why many enterprises prefer MangoApps for its powerful, flexible features designed to enhance communication, collaboration, and productivity across the organization. Make an informed choice by understanding how MangoApps can meet and exceed your team’s needs.And More!Download this document to see a full breakdown of the comparison between the two products, including a detailed feature table, and see why most companies are choosing MangoApps to replace Workplace from Meta.‍ **Download:** [MangoApps vs. WorkVivo](https://mango-cdn.b-cdn.net/images/marketing/resources/Workvivo-vs-MangoApps.pdf) --- # MangoApps vs. HCM **Type:** Whitepapers & Ebooks **Published:** 2024-07-10 MangoApps is an Employee Experience Platform that unites your HCM with other toolsIn today's business landscape, modern organizations rely on a variety of enterprise systems to streamline operations and enhance efficiency across different departments. Human Capital Management (HCM) is just one of these, alongside ITSM, ERP, CRM, and others like payroll systems, project management tools, security protocols, and facilities management systems to ensure smooth and coordinated workflows. Integrating these diverse systems into a unified platform, such as the MangoApps Employee Experience Platform, helps create a cohesive and productive work environment. MangoApps is an Employee Experience Platform that unites your HCM with other toolsIn today's business landscape, modern organizations rely on a variety of enterprise systems to streamline operations and enhance efficiency across different departments. Human Capital Management (HCM) is just one of these, alongside ITSM, ERP, CRM, and others like payroll systems, project management tools, security protocols, and facilities management systems to ensure smooth and coordinated workflows. Integrating these diverse systems into a unified platform, such as the MangoApps Employee Experience Platform, helps create a cohesive and productive work environment. This document provides a comprehensive view of how the MangoApps Employee Experience Platform integrates into your company’s technology ecosystem. MangoApps acts as a centralized communication, collaboration, and engagement hub, seamlessly connecting various line-of-business systems used across different departments. This integration enhances overall efficiency and ensures that all employees have easy access to essential tools and informationAnd More!Download this document to get a better understanding of how MangoApps can fit into your tech stack and become the cohesive employee-facing platform where your team goes to get work done.‍ **Download:** [MangoApps vs. HCM](https://mango-cdn.b-cdn.net/images/marketing/resources/HCM-vs-MangoApps.pdf) --- # MangoApps Overview Video **Type:** Product Demos **Published:** 2024-07-02 Watch this short overview video to get a quick glimpse into what MangoApps is all about! --- # Communicating Employee Schedules **Type:** Feature Datasheets **Published:** 2024-07-02 A.S. Watson BeneluxA.S. Watson Benelux, a large European retail chain with over 1,700 stores and 27,000 employees, realized that they needed to update the way that they communicated shift schedules to its thousands of frontline retail workers.With MangoApps, schedules are now being communicated to a team of over 20,000 retail employees on a weekly basis. A.S. Watson Benelux is able to reach their youthful workforce in a mobile app format that is useful for them and doesn’t require a company email address.Download this feature showcase to learn how switching to MangoApps allowed A.S. Watson Benelux to equip its frontline retail workers with an easy to access, dynamic scheduling system. ‍ **Download:** [Communicating Employee Schedules](https://mango-cdn.b-cdn.net/marketing/uploads/Communicating_Employee_Schedules.pdf) --- # Empowerment Through Technology: How Merchants Bonding Company has used MangoApps to streamline HR operations **Type:** Customer Case Studies **Published:** 2024-05-28 Merchants Bonding Case StudyWhen Aleah Vaske joined Merchants Bonding Company in 2021 as an intern in the HR department, the majority of her time was spent coordinating training and onboarding tasks for the company’s large crop of new hires. Fast forward to today, and Vaske has been able to largely automate all of these tasks using MangoApps, without any coding or involvement from IT. This is just one example of many ways that Merchants Bonding Company has been able to make things easier for their employees by centralizing tasks, resources, and communication within MangoApps, and using the platform’s interconnected systems to provide personalized employee experiences.‍ Merchants Bonding Case StudyWhen Aleah Vaske joined Merchants Bonding Company in 2021 as an intern in the HR department, the majority of her time was spent coordinating training and onboarding tasks for the company’s large crop of new hires. Fast forward to today, and Vaske has been able to largely automate all of these tasks using MangoApps, without any coding or involvement from IT. This is just one example of many ways that Merchants Bonding Company has been able to make things easier for their employees by centralizing tasks, resources, and communication within MangoApps, and using the platform’s interconnected systems to provide personalized employee experiences.Since launching MangoApps, Merchants Bonding has seen tremendous results:They no longer have to rely on email for the majority of their internal communicationThey've centralized their resources, communications, and training into one portal that's easy for their employees to useThey've used the data on the platform to create personalized employee experiencesAnd More!Download this case study to get a better understanding of how MangoApps helped Merchants Bonding transform the way they communicate, collaborate, and share information.‍ **Download:** [Empowerment Through Technology: How Merchants Bonding Company has used MangoApps to streamline HR operations](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_Merchants_Bonding.pdf) --- # A Strategic & Tactical Tool: How Great HealthWorks Uses MangoApps To Balance Growth & Stability **Type:** Customer Case Studies **Published:** 2024-03-29 Great HealthWorks Case StudyGreat HealthWorks uses MangoApps as a central location where its employees can access dashboards of key metrics, collaborate with external partners, and see all of the pertinent information for their role, from company news and events to files and policies. It is the first page that opens in any browser on their network, and has come to be the engine behind workflows across the business.‍ Great HealthWorks Case StudyGreat HealthWorks uses MangoApps as a central location where its employees can access dashboards of key metrics, collaborate with external partners, and see all of the pertinent information for their role, from company news and events to files and policies. It is the first page that opens in any browser on their network, and has come to be the engine behind workflows across the business.This strategic placement has streamlined communication of company events and news, providing employees with a centralized resource hub.Since launching MangoApps, Great HealthWorks has seen tremendous results:Real-time data is now accessible to all relevant employees and outside partners, greatly improving their agility and decision makinMangoApps is the default home page, and makes it much easier for employees to stay connected and up to dateIntegrations have made MangoApps a one-stop shop for everything employees needAnd More!Download this case study to get a better understanding of how MangoApps helped Great HealthWorks transform the way they communicate, collaborate, and share information.‍ **Download:** [A Strategic & Tactical Tool: How Great HealthWorks Uses MangoApps To Balance Growth & Stability](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_GreatHealthWorks.pdf) --- # MangoApps Business Case Template **Type:** Whitepapers & Ebooks **Published:** 2024-02-26 Figuring out the ROI of a software investment and getting executive buy-in is crucial to any digital transformation initiative. We have helped 
many prospects successfully navigate this process, and this business case template gives you all the tools you need to successfully present a compelling case to your executive team.Included is a spreadsheet where you can fill in stats about your company and get a tailored set of Hard & Soft ROI Estimations, as well as a presentation that puts some context around those numbers. With these tools, you have a great shortcut to a compelling presentation that will help you get the wheels moving on your digital transformation initiative. **Download:** [MangoApps Business Case Template](https://mango-cdn.b-cdn.net/marketing/uploads/MangoApps_Business_Case.zip) --- # IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment **Type:** Analyst Report **Published:** 2024-01-22 MangoApps was recognized as a Leader in the IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment. The IDC MarketScape noted that companies should consider MangoApps “if you are a midsize to large enterprise with both desk and deskless workers who need access to multiple apps integrated into a single company-branded AI-enabled digital workspace.”Download the report excerpt to see why the IDC MarketScape named MangoApps a leader, and highlighted the below as our strengths:Content and Personalization: MangoApps offers content authors a block editor to manage branded microsites with templates for easier content generation and workstreams. Data and Architecture: MangoApps has a large set of native SaaS integrations to enterprise applications with bidirectional updates. Clients can create their own microapps and widgets with API webhooks.Workspaces: MangoApps supports employee engagement with recognition aligned to company core values, a rewards store, and in-context polls. IDC MarketScape vendor analysis model is designed to provide an overview of the competitive fitness of ICT suppliers in a given market. The research methodology utilizes a rigorous scoring methodology based on both qualitative and quantitative criteria that results in a single graphical illustration of each vendor’s position within a given market. The Capabilities score measures vendor product, go-to-market and business execution in the short-term. The Strategy score measures alignment of vendor strategies with customer requirements in a 3-5-year timeframe. Vendor market share is represented by the size of the icons. **Download:** [IDC MarketScape: Worldwide Experience-Centric Intelligent Digital Workspaces 2024 Vendor Assessment](https://mango-cdn.b-cdn.net/marketing/uploads/IDCMarketScape_IntelligentDigitalWorkspaces_MangoApps.pdf) --- # Redefining Healthcare Operations: How a Unified Digital Workplace Drives Efficiency **Type:** Webinars **Published:** 2023-12-07 More than half of all healthcare workers report feeling burned out and overworked with many considering resignation. And it’s not just surgeons, physicians and nurses— that stat includes non-clinical healthcare staff and critical desk support staff, according to a recent study.A contributing factor is that desk workers and frontline staff alike feel disconnected from the tools they need to provide exceptional patient care and cut off from collaboration with colleagues. Most healthcare systems rely on browser-based medical records bogged down by cumbersome log-in processes to access important policies, resources and health information.When these frustrations equate to turnover, it’s costly for healthcare systems. Hospitals lost between $6.7 and $10.53 million in 2022 due to staff nurse turnover alone. The need for an improved work experience is more crucial than ever.Finding a  modern solution to fix communication breakdowns and streamline cumbersome workflow processes has never been more urgent. In this webinar, you will learn:How unifying employee experience can contribute to a more efficient and resilient healthcare workforce.How to consolidate digital workplace tools to enhance engagement of administrative and clinical staff.How to solve the most pressing employee engagement and communication issues facing healthcare systems today with a single app. --- # Building Trust, Culture, & Engagement: How KM2 Solutions Centralizes Resources And Unifies Their Team **Type:** Customer Case Studies **Published:** 2023-12-05 KM2 Solutions Case StudyKM2 Solutions uses MangoApps to provide a unified homepage and communications center for their international, bilingual team. Their agents get easy access to timekeeping, training, document management, and company news in a unified, user-friendly space. Meanwhile, their corporate teams benefit from simplified document management and governance, and have mechanisms to reach both broad and narrow segments with communications. Additionally, deep analytics are available to help them understand employee engagement and the efficacy of their programs. KM2 Solutions Case StudyKM2 Solutions uses MangoApps to provide a unified homepage and communications center for their international, bilingual team. Their agents get easy access to timekeeping, training, document management, and company news in a unified, user-friendly space. Meanwhile, their corporate teams benefit from simplified document management and governance, targeted communications, and analytics.This has enabled them to improve employee engagement and experience, centralize and simplify systems, and ensure that every employee has quick access to the documents they need, so they can provide flawless service to their customers.Since launching MangoApps, KM2 Solutions have seen tremendous results:Consistently over 90% employee engagement, measured month to monthThe MangoApps launch team helped them get from contract signing to launch in just 4 weeks100% of their product enhancement requests have been fulfilledAutomated governance reduces compliance workload, as their compliant team no longer has to maintain content manuallyAnd More!Download this case study to get a better understanding of how MangoApps helped KM2 Solutions transform the way they communicate, collaborate, and share information.‍ **Download:** [Building Trust, Culture, & Engagement: How KM2 Solutions Centralizes Resources And Unifies Their Team](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_KM2.pdf) --- # The Kansas City Chiefs' Video Case Study **Type:** Video Case Studies **Published:** 2023-10-27 Kansas City Chiefs Case StudyEvery gameday, the Kansas City Chiefs have over 600 event staff that are in a fan facing role with a unified goal of providing the best fan experience possible. With multiple Super Bowl Championships on the record books, the expectations are very high. While the offensive and defensive lines battle it out on the field, hear how Caitlin Petit, Director of Event Services, takes care of her frontline in the stands.  Kansas City Chiefs Case StudyEvery gameday, the Kansas City Chiefs have over 600 event staff that are in a fan facing role with a unified goal of providing the best fan experience possible. With multiple Super Bowl Championships on the record books, the expectations are very high. While the offensive and defensive lines battle it out on the field, hear how Caitlin Petit, Director of Event Services, takes care of her frontline in the stands. The Kansas City Chiefs new event services employee app “Huddle” - built on MangoApp - provides a single experience for all event staff. Everything event staff need is in Huddle - schedules, clock-in/out, top-down communication, peer-to-peer communication, training, all in one experience.Since launching Huddle to the event staff, the Kansas City Chiefs have seen tremendous results:90% adoption rate of Huddle - up from their average 40% adoption rate organization-wide.Reach 600 event staff members in an instant - never before possible. Other departments have inquired about adopting Huddle for their operations as well, including the Security and Stadium Operations teams.And More!Download this case study to get a better understanding of how MangoApps helped the Chiefs transform the way they communicate, collaborate, and share information.‍ **Download:** [The Kansas City Chiefs' Video Case Study](https://mango-cdn.b-cdn.net/marketing/uploads/KC-Chiefs_CaseStudy.pdf) --- # Keeping 600 Event Staff Engaged 365 Days a Year: The Kansas City Chiefs' Huddle **Type:** Customer Case Studies **Published:** 2023-10-27 Kansas City Chiefs Case StudyEvery gameday, the Kansas City Chiefs have over 600 event staff that are in a fan facing role with a unified goal of providing the best fan experience possible. With multiple Super Bowl Championships on the record books, the expectations are very high. While the offensive and defensive lines battle it out on the field, hear how Caitlin Petit, Director of Event Services, takes care of her frontline in the stands.  Kansas City Chiefs Case StudyEvery gameday, the Kansas City Chiefs have over 600 event staff that are in a fan facing role with a unified goal of providing the best fan experience possible. With multiple Super Bowl Championships on the record books, the expectations are very high. While the offensive and defensive lines battle it out on the field, hear how Caitlin Petit, Director of Event Services, takes care of her frontline in the stands. The Kansas City Chiefs new event services employee app “Huddle” - built on MangoApp - provides a single experience for all event staff. Everything event staff need is in Huddle - schedules, clock-in/out, top-down communication, peer-to-peer communication, training, all in one experience.Since launching Huddle to the event staff, the Kansas City Chiefs have seen tremendous results:90% adoption rate of Huddle - up from their average 40% adoption rate organization-wide.Reach 600 event staff members in an instant - never before possible. Other departments have inquired about adopting Huddle for their operations as well, including the Security and Stadium Operations teams.And More!Download this case study to get a better understanding of how MangoApps helped the Chiefs transform the way they communicate, collaborate, and share information.‍ **Download:** [Keeping 600 Event Staff Engaged 365 Days a Year: The Kansas City Chiefs' Huddle](https://mango-cdn.b-cdn.net/marketing/uploads/KC-Chiefs_CaseStudy.pdf) --- # Beyond Email and SharePoint: Health System Strategies For Improved Communication & Engagement **Type:** Webinars **Published:** 2023-07-18 Most agree there is a direct relationship between a team’s ability to easily communicate and its effectiveness. As such, it’s no surprise that health systems are looking to move beyond traditional tools for sharing internal policies and facilitating employee communication — such as email and SharePoint — and into a world where they can have more seamless interaction and increased security (think HIPAA) with fewer apps. In this webinar, TeamHealth Director of UX Jonathan Hensley and MangoApps CTO Vishwa Malhotra discuss these issues on a panel hosted by HealthSystemCIO. --- # How PetSmart Achieves Engagement at 4x the Industry Average **Type:** Webinars **Published:** 2023-07-13 --- # Drive Engagement & Efficiency For Your Government Organization **Type:** Webinars **Published:** 2023-06-22 Today’s business software landscape is filled with point solutions that aim to solve one problem very effectively, many of which don’t have the security accreditations required for the public sector.As a result, many organizations are forced to make do with an outdated tech stack that doesn’t solve many of the problems of the modern workforce. With the long buying cycles inherent in government and the often turbulent startup landscape powering most software, it can be difficult to incorporate many of the tools employed by the private sector.In this webinar, you will learn how an Employee SuperApp that meets the government’s rigorous security needs has transformed operations for local police departments, government contractors, and other agencies, enabling them to reach and equip both frontline and administrative staff with all the digital tools and information they need.‍ --- # Employee SuperApps: The Answer To Your Most Pressing Engagement & Efficiency Challenges **Type:** Webinars **Published:** 2023-06-08 ‍Join the webinar to hear our panelists discuss:How you can streamline your operations by consolidating your tech stack.Strategies to enhance communication & engagement among frontline teams.The advantages of a centralized digital work hub for frontline employees.Generate positive business outcomes with an Employee SuperApp.TeamHealth cut costs drastically by replacing several unnecessary tools.A.S. Watson Benelux transformed the culture of their 27K+ employees.The YMCA improved operational efficiency across autonomous branches.‍ --- # Upgrading To A Modern Intranet **Type:** Customer Case Studies **Published:** 2023-06-01 Marion Health Case StudyMarion Health, a provider of high-quality medical services with over 1,300 employees, used to host important information on static website pages. Employees were not viewing the content and it became impossible to keep people engaged. With our platform, they've been able to leverage a customizable and dynamic modern intranet to create a single space where employees can go to view current information and resources. By switching to MangoApps, Marion Health was able to achieve over 90% monthly employee adoption. In this case study, you will learn how Marion Health used MangoApps to:Improve communication and collaboration among staff and clinicians.Replace the global use of email for internal communications with MangoApps' Messenger tool. Effortlessly remain HIPAA-compliant and provide a secure digital workplace for employees. And more!Download this case study to get a better understanding of how MangoApps helped Marion Health transform the way they communicate, collaborate, and share information.‍ ## Key Outcomes - Achieved 90% monthly employee adoption **Download:** [Upgrading To A Modern Intranet](https://mango-cdn.b-cdn.net/marketing/uploads/MarionHealth_CaseStudy.pdf) --- # Bring It All Together: How An Employee SuperApp Drives Efficiency & Improves Employee Engagement **Type:** Webinars **Published:** 2023-06-01 Today’s business software landscape is filled with point solutions that aim to solve one problem very effectively. As a result, many companies are forced to either invest in a wide variety of tools or risk letting their employee tech stack become outdated, so employees wind up having to navigate a confusing array of interfaces and solutions. This has a number of downsides, including wasted time, duplicated efforts, and the inability to find and refer back to previous files and conversations.In this webinar from TeamHealth and MangoApps, you will learn how an Employee SuperApp has transformed TeamHealth’s ability to reach and equip both frontline and administrative staff, and how leaders in companies like yours are thinking about this space.We will cover topics such as:How you can drive operational excellence by reducing the number of tools your employees need to accessHow you can improve employee reach and engagement for your frontline teamsHow a centralized digital work hub can improve employee productivity --- # How An Employee SuperApp Transforms The Workplace **Type:** Whitepapers & Ebooks **Published:** 2023-05-30 How an Employee SuperApp transforms the workplaceThis whitepaper focuses on the importance and benefits of integrating an Employee SuperApp within an organization to eliminate information chaos and enhance the employee experience. The paper discusses the growing demand for such SuperApps, as well as their ability to create equality between frontline and desk workers. Here’s everything you need to know:In this whitepaper, we discuss how you can eliminate information chaos and provide a unified employee experience with an Employee SuperApp. This comprehensive whitepaper includes:Why the demand for Employee SuperApps continues to rise. How an Employee SuperApp can level the playing field among frontline & desk workers. 10 top-line & bottom-line benefits of an Employee SuperApp.How you can eliminate a massive productivity-killer within your organization.How you can save 9 hours/week per employee by unifying your searches within a SuperApp. How an Employee SuperApp fosters employee enablement in each industry. A deeper look into 20+ impactful features of an Employee SuperApp.And More!Download this whitepaper to learn how you can take your organization to the next level with an Employee SuperApp. ‍‍‍ **Download:** [How An Employee SuperApp Transforms The Workplace](https://mango-cdn.b-cdn.net/marketing/uploads/How_An_Employee_SuperApp_Transforms_The_Workplace.pdf) --- # Leveraging An Employee SuperApp To Improve Operational Excellence & Engagement **Type:** Webinars **Published:** 2023-04-20 Forward-looking IT & HR leaders are thinking about Employee SuperApps as a way to solve the communication issues of today and tomorrow, especially for frontline workers.Watch the webinar to hear our panelists discuss:How you can drive operational excellence by reducing the number of tools your employees need to access.How you can improve employee reach and engagement for your frontline teams.How a centralized digital work hub can improve employee productivity.How to internally build the case for an Employee SuperApp.Generate positive business outcomes with an Employee SuperApp.TeamHealth greatly reduced software costs by replacing several unnecessary tools.A.S. Watson Benelux created a culture shift for its 27K+ employees.The YMCA improved operational efficiency across autonomous branches.‍‍‍‍ --- # Building & Scaling To 1M+ Users With MangoApps **Type:** Whitepapers & Ebooks **Published:** 2023-04-13 Understanding How MangoApps Builds a Scalable Application for 1 Million+ UsersScalability is as crucial to the MangoApps application as its features and user interface. This document highlights key aspects that enable MangoApps to serve millions of users. Understanding How MangoApps Builds a Scalable Application for Over 1 Million UsersScalability is as crucial to the MangoApps application as its features and user interface. This document highlights key aspects that enable MangoApps to serve millions of users.MangoApps helps companies modernize their employee-facing applications. It brings intranet, communications, training & work management together in one platform to provide the most adaptable, intuitive, and unified experience in the market today. **Download:** [Building & Scaling To 1M+ Users With MangoApps](https://mango-cdn.b-cdn.net/images/marketing/resources/ScalableApplication_web.pdf) --- # The CIO's Guide To Employee SuperApps **Type:** Webinars **Published:** 2023-03-14 Watch this webinar to learn how forward-looking IT leaders are thinking about Employee SuperApps as a way to solve the communication issues of today and tomorrow, especially for frontline workers. Watch the webinar to learn:How you can drive operational excellence by reducing the number of tools your employees need to access.How you can improve employee reach and engagement for your frontline teams.How a centralized digital work hub can improve employee productivity.How to internally build the case for an Employee SuperApp.Generate positive business outcomes with an Employee SuperApp.TeamHealth greatly reduced software costs by replacing several unnecessary tools.A.S. Watson Benelux created a culture shift for its 27K+ employees.The YMCA improved operational efficiency across autonomous branches.‍‍ --- # Creating Massive Time-Savings With MangoApps **Type:** Customer Case Studies **Published:** 2023-02-16 Shelter Insurance, a property casualty insurance company that offers auto and home insurance across 21 states, was looking for a tool that could replace its outdated resource repository system for the Claims Department.Shelter Insurance's Claims Department quickly found that the breadth of features and capabilities MangoApps had to offer expanded far beyond being a one-stop shop for employee information.In this case study, you will learn how Shelter Insurance's Claims Department used MangoApps to:Save time and improve efficiency with trackers and automated formsQuickly onboard new employees Transform top-down communication across the departmentAnd more!Download this case study to get a better understanding of how MangoApps helped Shelter Insurance transform the way they communicate, collaborate, and share information.‍ **Download:** [Creating Massive Time-Savings With MangoApps](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_ShelterInsurance.pdf) --- # How Building A Workplace Community Boosts Frontline Employee Engagement **Type:** Webinars **Published:** 2023-02-02 Watch this video to learn how building a workplace community can lead to improved employee engagement among your frontline workforce. --- # Engage Your Frontline Workforce With A Modern Digital Work Hub **Type:** Product Demos **Published:** 2023-01-31 Watch this video to learn how unifying employee comms, collaboration, training, and work management into one platform can benefit engagement across frontline workers. --- # Effective Communication & Engagement Solution For Your Frontline Workforce **Type:** Webinars **Published:** 2023-01-30 Watch this video to learn why MangoApps is the perfect communication and engagement solution for your frontline employees. --- # How An Intranet Can Encourage Content Creation, Collaboration & Usage **Type:** Customer Case Studies **Published:** 2023-01-27 Brandmuscle is an innovative marketing organization that helps big brand marketing departments execute at the local level. With associates in several cities across the United States, Brandmuscle needed a new intranet platform that enabled easy communication, collaboration, and information sharing.Brandmuscle searched for a new and complete intranet solution to solve these issues. Brandmuscle selected MangoApps over other enterprise platforms for its consolidated database, all-inclusive capabilities, and scalable success.In this case study, you will learn how Brandmuscle used MangoApps to:Increase information sharing and accessibilityPromote a culture of interdependence and collaborationStreamline the onboarding and integration process for new employeesAnd more!Download this case study to get a better understanding of how MangoApps helped Brandmuscle transform the way the‍ **Download:** [How An Intranet Can Encourage Content Creation, Collaboration & Usage](https://mango-cdn.b-cdn.net/images/marketing/resources/CaseStudy_BrandMuscle.pdf) --- # Implementation Of A Digital Workplace **Type:** Webinars **Published:** 2023-01-27 Watch this video where Liam Stewart, Head of ICT, shows how Office of Public Works leverages MangoApps to build community across their dispersed employees.‍ --- # Brandmuscle Video Case Study **Type:** Video Case Studies **Published:** 2023-01-27 Brandmuscle is an innovative marketing organization that helps big brand marketing departments execute at the local level. With associates in several cities across the United States, Brandmuscle needed a new intranet platform that enabled easy communication, collaboration, and information sharing.Brandmuscle searched for a new and complete intranet solution to solve these issues. Brandmuscle selected MangoApps over other enterprise platforms for its consolidated database, all-inclusive capabilities, and scalable success.In this video, you will learn how Brandmuscle used MangoApps to:Increase information sharing and accessibilityPromote a culture of interdependence and collaborationStreamline the onboarding and integration process for new employees --- # How An Effective Intranet Can Connect Teams Across The World **Type:** Customer Case Studies **Published:** 2023-01-26 Huber+Suhner, a fiber optic cable manufacturing company based in Switzerland, needed to find a solution to connect its 3,900 employees around the globe in a timely manner.Thus, Huber+Suhner sought out to find a way to tackle these issues through collaboration and communication via an intranet solution. After looking at 20 different solutions, Huber+Suhner chose MangoApps because of its singular, browser-based platform that included up-to-date social and mobile communication tools.In this case study, you will learn how Huber+Suhner used MangoApps to:Efficiently communicate and collaborate globally across multiple time zonesUnify employees with one tool that allows them to easily share knowledge with each otherAnalyze the daily activities and project progress of different company teams around the worldAnd more!Download this case study to get a better understanding of how MangoApps helped Huber+Suhner transform the way they communicate, collaborate, and share information.‍ **Download:** [How An Effective Intranet Can Connect Teams Across The World](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_HuberSuhner.pdf) --- # Improving Internal Communications **Type:** Customer Case Studies **Published:** 2023-01-26 Ekspert, a Switzerland-based organization that provides accounting and payroll services, was looking for a platform that could help them with their internal communications while meeting their rigorous security requirements.Wanting to find a solution, Guillaume Sourd, IT ERP Specialist, and the rest of the Ekspert technical team began their search for a communication platform. After evaluating a handful of solutions, they decided MangoApps was the best fit for their unique needs.In this case study, you will learn how Ekspert used MangoApps to:Enhance their internal communications across the organizationCreate secure project spaces for employees to collaborate and communicate with clientsEnsure GDPR-compliance with rigorous security measuresAnd More!Download this case study to get a better understanding of how MangoApps helped Ekspert transform the way they communicate, collaborate, and share information.‍ **Download:** [Improving Internal Communications](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_Ekspert.pdf) --- # How An Adaptable Intranet Can Transform A Unique Workplace **Type:** Customer Case Studies **Published:** 2023-01-26 Wildlife Trusts, a nonprofit organization that works to provide information about wildlife and bring people closer to nature, needed to replace their outdated Intranet system to fix communication and collaboration issues across their 46 UK branches.Thus, Wildlife Trusts sought out an adaptable, intuitive, and modern intranet solution to solve these issues. After extensive research of other intranet platforms, Wildlife Trusts adopted MangoApps for its balanced structure, platform adaptability, and accommodating customer service.In this case study, you will learn how Wildlife Trusts used MangoApps to:Facilitate communication and collaboration on collective projects across different trustsOrganize employees into groups and teamsImprove and enhance current operations through open discussion threadsAnd more!Download this case study to get a better understanding of how MangoApps helped Wildlife Trusts transform the way they communicate, collaborate, and share information.‍ **Download:** [How An Adaptable Intranet Can Transform A Unique Workplace](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_WildlifeTrusts.pdf) --- # How A Modern Intranet Provides Accessibility & Community **Type:** Customer Case Studies **Published:** 2023-01-26 A non-profit organization dedicated to helping inmates receive an education, known as the Education of Justice Program (EJP), wanted to find an effective way to keep all staff members interconnected and capable of sharing information with one another.‍Thus, the EJP began their search to find an effective communication and collaboration platform. After doing extensive research to find the right fit for their program, the team chose MangoApps for its usability and the inclusive community it provides for their team.In this case study, you will learn how the University of Illinois used MangoApps to:Encourage workers to log on and participate in their online communityShare time-sensitive information with others in a quick, reliable wayBuild a successful and supportive community of people despite not sharing the same physical spaceAnd more!Download this case study to get a better understanding of how MangoApps helped University of Illinois transform the way they communicate, collaborate, and share information.‍ **Download:** [How A Modern Intranet Provides Accessibility & Community](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_UniversityOfIllinois.pdf) --- # How To Connect Employees Outside Of The Office **Type:** Customer Case Studies **Published:** 2023-01-26 Tatts Group, an Australia-based non-casino gambling company with 3,500 employees, had an outdated intranet solution that limited their collaboration and information sharing capabilities.Thus, Tatts Group began to look for a universal solution that would provide them with a centralized source of communication for all of their employees. After evaluating multiple intranet solutions, Tatts Group chose MangoApps due to its customizable apps and mobile capabilities.In this case study, you will learn how Tatts Group used MangoApps to:Connect employees across the globeRun the platform without the help of their technology teamParticipate in real-time communication and collaborationAnd more!Download this case study to get a better understanding of how MangoApps helped Tatts Group transform the way they communicate, collaborate, and share information.‍ **Download:** [How To Connect Employees Outside Of The Office](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_TattsGroup.pdf) --- # A 5-step strategy for successful intranet launch **Type:** Customer Case Studies **Published:** 2023-01-26 Intranet Deployment For Internal CommunicationsAt symplr, Melissa Hoyos, Director of Internal Comms, worked with MangoApps to overhaul their company’s intranet and communication strategy. She drew on her experience building and deploying SharePoint at three previous companies to ensure the program’s success.We have used Melissa’s expertise on the subject to put together this comprehensive guide for internal comms professionals.Her advice boils down to the following:Start with a vision and leadership buy-inKnow what is most important to you, and ask the right questions in demosRelinquish control and get everyone involvedAnd More!Download this case study to learn more, or read about our modern intranet solution.‍ ## Key Outcomes - Realized over $1,500/month in cost savings by switching to MangoApps. - Symplr's 1,350 employees generated over 37K views, 1,128 comments, 907 likes, 1353 pieces of new content on their new intranet. **Download:** [A 5-step strategy for successful intranet launch](https://mango-cdn.b-cdn.net/marketing/uploads/Symplr_CaseStudy.pdf) --- # How An Intranet Transforms Communication & Culture **Type:** Customer Case Studies **Published:** 2023-01-26 Superdrug, a health and beauty retailer with over 800 locations across the UK and Ireland, wanted to replace their outdated Intranet with a modern, engaging, and easy-to-use system for their 12,000 employees.After researching over 20 vendors, Superdrug adopted MangoApps for its intuitive operability, balanced communication interface, and multi-platform functionality.In this case study, you will learn how Superdrug used MangoApps to:Foster an increased sense of an interconnected communityFacilitate collaboration across different departments and international bordersCreate a centralized knowledge hub for on-the-go employeesAnd more!Download this case study to get a better understanding of how MangoApps' employee app for retail helped Superdrug transform the way they communicate, collaborate, and share information.‍ ## Key Outcomes - Over 10,000 employees adopted MangoApps within the first 8 weeks after launch. **Download:** [How An Intranet Transforms Communication & Culture](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_Superdrug.pdf) --- # Building Culture & Efficiency With A Modern Toolset **Type:** Customer Case Studies **Published:** 2023-01-26 Ram Tool is a construction supply company with 1,500 employees spread across 45 locations. About 200 of those employees are in corporate roles at their headquarters in Alabama.Like many companies centered around field operations, Ram Tool found it difficult to reach field employees through print materials. By partnering with MangoApps, they’ve created a space for intranet, communication, and collaboration that reaches employees who were previously left in the dark.In this case study, you will learn how Ram Tool uses MangoApps to:Communicate more effectively with their large frontline teams, including critical alertsCollaborate and share knowledge across departments and locationsReinforce their culture with gamification and friendly competitionAnd More!Download this case study to get a better understanding of how MangoApps helped Ram Tool transform the way they communicate, collaborate, and share information ## Key Outcomes - Operations Manager saves 3-4 hours by sending out targeted alerts to affected workforce. **Download:** [Building Culture & Efficiency With A Modern Toolset](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_RamTool.pdf) --- # How A Modern Intranet Enables Accountability **Type:** Customer Case Studies **Published:** 2023-01-26 Pinellas Park PD (a police department based in Florida) and their 110 employees used to struggle to be on the same page. Officers out on patrol had no easy way to exchange information with each other and their main office.Captain Adam Geissenberger knew he could find a modern intranet solution. After evaluating a handful of vendors, he chose MangoApps for our flexibility, responsive support team, and ability to meet his department’s security needs.In this case study, you will learn how Pinellas Park Police Department used MangoApps to:Improve communication & collaboration among patrol officersEstablish a culture of accountabilitySave upper-level management 10-15 hours per weekAnd more!Download this case study to get a better understanding of how MangoApps helped Pinellas Park Police Department transform the way they communicate, collaborate, and share information.‍ ## Key Outcomes - Leadership saves 10-15 hours per week, as they no longer have to search for information. **Download:** [How A Modern Intranet Enables Accountability](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_PinellasPark.pdf) --- # Uniting A Dispersed Workforce **Type:** Customer Case Studies **Published:** 2023-01-26 IPC, a non-profit trade association located in Illinois, was looking to switch to a modern intranet solution that could accommodate all of their unique needs.Teresa Rowe, Senior Director of Assembly and Standards Technology, began her search for an intranet that could supplement IPC’s diverse workforce, while providing a formal, documented approval process for industry standards and procedures.In this case study, you will learn how IPC used MangoApps to:Unite a dispersed volunteer workforceEmpower groups and teamsCreate a formal, documented process for industry standardsAnd More!Download this case study to get a better understanding of how MangoApps helped IPC transform the way they communicate, collaborate, and share information. **Download:** [Uniting A Dispersed Workforce](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_IPC.pdf) --- # Fostering sustainability and inclusion **Type:** Customer Case Studies **Published:** 2023-01-26 Introba, formerly known as Integral Group, is an engineering firm and sustainability consultant, with a global network of design professionals collaborating under a single deep green engineering umbrella. They replaced their outdated SharePoint implementation with MangoApps to unite their widely dispersed team and enable them to collaborate on complex ideas.In this case study, you will learn how Introba uses MangoApps to:Turn their diversity and sustainability goals into action itemsSave 10-12 hours a week for their IT team by capturing knowledge in wikisUnite global colleagues and help people find subject matter experts from beyond their local officeAnd More!Download this case study to get a better understanding of how MangoApps helped Introba transform the way they communicate, collaborate, and share information. ## Key Outcomes - IT team saves 10-12 hours a week by capturing knowledge in Wikis. **Download:** [Fostering sustainability and inclusion](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_Integral.pdf) --- # How An Intranet Can Transform Communication & Connectivity **Type:** Customer Case Studies **Published:** 2023-01-26 CCS, a nonprofit consulting firm, needed a way to increase communication, education, collaboration, and connectivity among their 3,000+ employees across various domestic and international offices.CCS began their search for a modern intranet solution to solve these issues. CCS adopted MangoApps instead of other vendors for its user-friendly focus, wide selection of functions and tools, and consolidated database platform.In this case study, you will learn how CCS used MangoApps to:Encourage employee participation and engagementSimplify file sharing with real-time search capabilitiesCreate an educational environment with a centralized knowledge databaseAnd more!Download this case study to get a better understanding of how MangoApps helped CCS transform the way they communicate, collaborate, and share information.‍ **Download:** [How An Intranet Can Transform Communication & Connectivity](https://mango-cdn.b-cdn.net/images/marketing/resources/CaseStudy_CCS.pdf) --- # Wildlife Trusts Video Case Study **Type:** Video Case Studies **Published:** 2023-01-25 Wildlife Trusts, a nonprofit organization that works to provide information about wildlife and bring people closer to nature, needed to replace their outdated Intranet system to fix communication and collaboration issues across their 46 UK branches.Wildlife Trusts sought out an adaptable, intuitive, and modern intranet solution to solve these issues. After extensive research of other intranet platforms, Wildlife Trusts adopted MangoApps for its balanced structure, platform adaptability, and accommodating customer service.In this video, you will learn how Wildlife Trusts used MangoApps to:Facilitate communication and collaboration on collective projects across different trustsOrganize employees into groups and teamsImprove and enhance current operations through open discussion threads‍‍ --- # TeamHealth Video Case Study **Type:** Video Case Studies **Published:** 2023-01-25 TeamHealth, a leading physician practice with over 23,000 employees, used to communicate with their employees mostly over email. They hadn’t quite figured out how to make mobile collaboration work—especially for clinicians—until they partnered with MangoApps.With our platform, they’ve been able to sunset several costly tools and create a unified digital work hub where a single mobile app contains everything from training and policy information to SSO integrations with over 200 other applications.In this video, you will learn how TeamHealth used MangoApps to:Connect physicians with nonclinical employees from across the nationEngage employees by allowing them to effortlessly share resources and company news with each otherCustomize their intranet to meet the unique challenges presented within the healthcare industry --- # Superdrug Video Case Study **Type:** Video Case Studies **Published:** 2023-01-25 Superdrug, a health and beauty retailer with over 800 locations across the UK and Ireland, wanted to replace their outdated Intranet with a modern, engaging, and easy-to-use system for their 12,000 employees.After researching over 20 vendors, Superdrug adopted MangoApps for its intuitive operability, balanced communication interface, and multi-platform functionality.In this video, you will learn how Superdrug used MangoApps to:Foster an increased sense of an interconnected communityFacilitate collaboration across different departments and international bordersCreate a centralized knowledge hub for on-the-go employees‍ --- # Kelly-Moore Paints Video Case Study **Type:** Video Case Studies **Published:** 2023-01-25 Kelly-Moore Paints, a paint manufacturing and retail company headquartered in San Carlos, California needed to replace their legacy Intranet with a modern, centralized, easy-to-use hub for their 1,400 employees.Chief Information Officer, Jim Maul, searched for a solution to solve these issues. After an extensive, two-dozen vendor RFP process, Maul selected MangoApps for its consolidated platform, free-flowing communication, and multi-faceted functionality.In this video, you will learn how Kelly-Moore Paints used MangoApps to:Improve employee efficiency with a centralized information and knowledge hubIncrease the level of communication between field sales employees and the corporate officeEncourage a cohesive and inclusive company culture --- # Huber+Suhner Video Case Study **Type:** Video Case Studies **Published:** 2023-01-25 Huber+Suhner, a fiber optic cable manufacturing company based in Switzerland, needed to find a solution to connect its 3,900 employees around the globe in a timely manner.Thus, Huber+Suhner sought out to find a way to tackle these issues through collaboration and communication via an intranet solution. After looking at 20 different solutions, Huber+Suhner chose MangoApps because of its singular, browser-based platform that included up-to-date social and mobile communication tools.In this video, you will learn how Huber+Suhner used MangoApps to:Efficiently communicate and collaborate globally across multiple time zonesUnify employees with one tool that allows them to easily share knowledge with each otherAnalyze the daily activities and project progress of different company teams around the world --- # Establishing A Connected Workplace Culture **Type:** Customer Case Studies **Published:** 2023-01-25 Great Western Bank Case StudyGreat Western Bank, a financial services organization that serves customers over 170 locations, had a common communication problem — too many emails were being sent to large groups, which reduced ownership and caused inbox clutter. Topics would be discussed across several email chains, creating confusion and inconsistency.Looking for a solution, Cheryl Olson, Employee Program Manager, and the rest of the Great Western Bank technical team began their search for a communication platform that could create clarity and efficiency in their communications, and give each employee a personalized experience based on their role and responsibilities. After evaluating 4-5 options, Cheryl came across MangoApps and immediately recognized its potential.In this case study, you will learn how Great Western Bank used MangoApps to:Contribute to a connected workplace cultureEnhance their internal communications across the organizationEnable employees to quickly find resources and informationAnd More!Download this case study to get a better understanding of how MangoApps helped Great Western Bank transform the way they communicate, collaborate, and share information.‍ **Download:** [Establishing A Connected Workplace Culture](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_GWB.pdf) --- # Strengthening Internal Communication And Collaboration **Type:** Customer Case Studies **Published:** 2023-01-25 Great Harvest Case StudyGreat Harvest Bread Company, a bakery that sells freshly baked bread and other food items across its franchised locations, was looking to equip its store owners with a modern intranet platform to strengthen their internal communication and collaboration processes.Great Harvest sought out to find a solution that could provide a modern search functionality for employees, while having a much cleaner and more efficient intranet architecture. After coming across MangoApps, they quickly realized the value it could bring to their organization and started migrating their content over.In this case study, you will learn how Great Harvest used MangoApps to:Allow store members to share knowledge, ideas, and informationCentralize resources and information in an easily searchable hubBuild a strong employee recognition program by offering incentives and kudosAnd More!Download this case study to get a better understanding of how MangoApps helped Great Harvest transform the way they communicate, collaborate, and share information.‍ **Download:** [Strengthening Internal Communication And Collaboration](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_GreatHarvest.pdf) --- # Creating A More Sustainable & Equitable World **Type:** Customer Case Studies **Published:** 2023-01-25 CIVICUS, an Alliance of more than 12,500 individual and organizational members distributed across the globe, was in need of a solution that could bring together its dispersed members and provide a safe place for them to communicate and store private information.CIVICUS turned to MangoApps due to its customizability, wide breadth of functionalities, and the content security it could offer for its members.In this case study, you will learn how CIVICUS used MangoApps to:Allow members to collaborate and communicate within a secure network.Offer comprehensive support, training, and resources to dispersed members.Create an increased sense of autonomy within the organization.And More!Download this case study to get a better understanding of how MangoApps helped CIVICUS transform the way they communicate, collaborate, and share information.‍ **Download:** [Creating A More Sustainable & Equitable World](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_Civicus.pdf) --- # Road to 90% Employee Engagement **Type:** Customer Case Studies **Published:** 2023-01-25 Columbia Basin Health Association Case StudyColumbia Basin Health Associate (CBHA), one of Washington State’s premier federally qualified health centers, wanted to upgrade its intranet platform to a modern solution that could offer improved connectivity and alignment for its workforce. Their previous platform had limitations that made it difficult to properly engage employees.CBHA’s focus shifted toward finding and implementing a solution that was better suited for both its frontline clinical staff and non-clinical desk workers. Once the leadership team experienced MangoApps, they recognized the flexibility and customizability it had to offer and decided to make the switch.In this case study, you will learn how CBHA uses MangoApps to:Achieve over 90% employee adoptionTransform communication and engagementImprove alignment across teamsAnd more!Download this case study to get a better understanding of how MangoApps helped CBHA transform the way they communicate, collaborate, and share information.‍ ## Key Outcomes - Achieved 90% monthly employee engagement of its MangoApps platform. **Download:** [Road to 90% Employee Engagement](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_CBHA.pdf) --- # How A Digital Workplace Helps YMCA Employees Better Serve Their Communities **Type:** Customer Case Studies **Published:** 2023-01-25 YMCA Case StudyThe YMCA, a nonprofit organization that does important work in communities across the US, sought out to find a solution that could create a flexible, digital workspace for their employees and volunteers.After demos with many software providers, YMCA decided to move forward with MangoApps because of its wide berth of features, simplistic look and feel, and most importantly, it was the only platform able to meet the diverse needs of their decentralized organization.In this case study, you will learn how the YMCA used MangoApps to:Create a unified digital workspace for their dispersed volunteers and employeesBuild an effective communication strategy in response to COVID-19Maintain a positive organizational culture and strong communityAnd More!Download this case study to get a better understanding of how MangoApps helped the YMCA transform the way they communicate, collaborate, and share information. **Download:** [How A Digital Workplace Helps YMCA Employees Better Serve Their Communities](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_YMCA.pdf) --- # Centralizing Employee Resources **Type:** Customer Case Studies **Published:** 2023-01-25 TCG, a fully remote government contractor that helps federal agencies develop custom-built IT and management advisory solutions, was looking to find a modern intranet platform that could provide a centralized location for employee resources.After evaluating a handful of options, TCG quickly decided that MangoApps’ high customizability and easy-to-use intranet platform provided the best fit for their specific needs.In this case study, you will learn how TCG used MangoApps to:Create a central repository of information and resourcesTrack employee engagement and see which employees were viewing distributed contentBridge the gap between their remote workforce, making sure everyone is in the loopAnd More!Download this case study to get a better understanding of how MangoApps helped TCG transform the way they communicate, collaborate, and share information.‍ **Download:** [Centralizing Employee Resources](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_TCG.pdf) --- # Building A Connected Workforce **Type:** Customer Case Studies **Published:** 2023-01-25 PROBIOMED Case StudyPROBIOMED, a Mexican biopharmaceutical enterprise, was looking to replace their custom-built intranet with a modern platform that could help employees communicate and collaborate better.After an extensive search, PROBIOMED found that MangoApps was the only platform that had all the features and integrations they were looking for.In this case study, you will learn how PROBIOMED uses MangoApps to:Transform internal communications across distributed employeesConsolidate their tech stackImprove company culture and employee engagementAnd more!Download this case study to get a better understanding of how MangoApps helped PROBIOMED transform the way they communicate, collaborate, and share information.‍ ## Key Outcomes - Achieved significant cost savings by consolidating tech stack with MangoApps. **Download:** [Building A Connected Workforce](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_Probiomed.pdf) --- # Enabling A Faster, More Efficient Team **Type:** Customer Case Studies **Published:** 2023-01-25 Pinion, formerly known as K·Coe Isom, is a top 100 accounting firm specializing in the food and agriculture industry, with about 450 employees spread all over the US.In early 2019, the firm began an extensive search for a new solution that would allow them to take a more modern approach to internal communication and knowledge management. They demoed 14 different intranet platforms—every provider they could find—and in the end chose MangoApps as a result of the platform’s flexible design and the MangoApps team’s focus on customer service.In this case study, you will learn how Pinion uses MangoApps to:Keep a growing record of their activities and build a useful repository of company knowledge and informationReduce reliance on email for collaboration, boosting productivity and visibilityBring all of their employee resources into a single dashboard, making things more convenient and reducing confusionAnd More!Download this case study to get a better understanding of how MangoApps helped Pinion transform the way they communicate, collaborate, and share information.‍ ## Key Outcomes - Realized over $50,000 in cost savings by replacing old systems. **Download:** [Enabling A Faster, More Efficient Team](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_Pinion.pdf) --- # Leveraging A Digital Workplace **Type:** Customer Case Studies **Published:** 2023-01-25 Office of Public Works (OPW), a government department in Ireland that is primarily responsible for flood relief and managing heritage and state properties, was looking to replace their outdated intranet.In need of a solution, Liam Stewart, Head of ICT at OPW, sought out to find a modern digital workplace platform that could improve employee engagement within their department, while also improving communication and collaboration across their 140 site locations.In this case study, you will learn how OPW used MangoApps to:Centralize employee access to information and resourcesEstablish workplace communities among specific teams and projectsImprove efficiency by incorporating trackers into their workflowsAnd More!Download this case study to get a better understanding of how MangoApps helped OPW transform the way they communicate, collaborate, and share information.‍ **Download:** [Leveraging A Digital Workplace](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_OPW.pdf) --- # Enabling Two-Way Communication With MangoApps **Type:** Customer Case Studies **Published:** 2023-01-25 Morningstar Living Case StudyMorningstar Living, a not-for-profit continuing care retirement community for senior citizens, had an outdated SharePoint platform that was limiting communication and engagement across employees.They sought to replace their SharePoint intranet with a solution that could offer better accessibility and an improved employee experience for both their administrative team and their on-the-move employees.In this case study, you will learn how Morningstar Living uses MangoApps to:Improve the way it distributes important top-down communicationsHarness the mobile app to connect and engage employees from wherever they areCreate a seamless user experienceAnd more!Download this case study to get a better understanding of how MangoApps helped Morningstar Living transform the way they communicate, collaborate, and share information.‍ ## Key Outcomes - Improved top-down & mobile communication by replacing SharePoint **Download:** [Enabling Two-Way Communication With MangoApps](https://mango-cdn.b-cdn.net/marketing/uploads/morningstarliving-cover.png) --- # Leveraging A Social Intranet **Type:** Customer Case Studies **Published:** 2023-01-25 Barut Hospitality Management Case StudyIn need of a solution to better equip their dispersed hotel employees, Barut Hospitality Management began their search for a social intranet that was user-friendly, could assist their compliance efforts, and could support their Turkish employees. Barut Hospitality Management Case StudyBarut Hospitality Management, a Turkish organization with 6 resort hotel locations spread across Turkey, was looking for a social intranet that could connect their workforce and streamline communication and collaboration among their employees.In need of a solution to better equip their dispersed hotel employees, Barut Hospitality Management began their search for a social intranet that was user-friendly, could assist their compliance efforts, and could support their Turkish employees.In this case study, you will learn how Barut Hospitality Management used MangoApps to:Transform the way their employees collaborateEquip frontline employees with the resources they need to better connect with their colleaguesProvide a digital workspace where important information can be found 24/7And More!Download this case study to get a better understanding of how MangoApps helped Barut Hospitality Management transform the way they communicate, collaborate, and share information.‍ **Download:** [Leveraging A Social Intranet](https://mango-cdn.b-cdn.net/images/marketing/resources/CaseStudy_BarutHotels.pdf) --- # CCS Fundraising Video Case Study **Type:** Video Case Studies **Published:** 2023-01-25 CCS Fundraising, a nonprofit consulting firm, needed a way to increase communication, education, collaboration, and connectivity among their 3,000+ employees across various domestic and international offices.CCS Fundraising began their search for a modern intranet solution to solve these issues. CCS Fundraising ended up adopting MangoApps instead of other vendors because of its user-friendly focus, wide selection of functions and tools, and consolidated database platform.In this video, you will learn how CCS Fundraising used MangoApps to:Encourage employee participation and engagementSimplify file sharing with real-time search capabilitiesCreate an educational environment with a centralized knowledge database‍ --- # How A Mobile App Connected A Remote Workforce **Type:** Customer Case Studies **Published:** 2023-01-25 Benchmark Human Services, an organization that serves individuals with disabilities and behavioral health needs, wanted to improve employee engagement among their dispersed workforce.Director of Communications, Courtney Heiser, identified a communication barrier among Benchmark’s remote-based nurses and practitioners. As workers were often in patient care facilities and homes, staying connected to their peers and upper management proved to be a challenge.In this case study, you will learn how Benchmark used MangoApps’ mobile app to:Improve communication & collaboration among remote employeesEquip workers with the critical information necessary to do their jobsQuickly push out company updates and informationAnd More!Download this case study to get a better understanding of how MangoApps helped Benchmark Human Services transform the way they communicate, collaborate, and share information.‍ **Download:** [How A Mobile App Connected A Remote Workforce](https://mango-cdn.b-cdn.net/images/marketing/resources/Benchmark_CaseStudy.pdf) --- # Why SharePoint Was Insufficient **Type:** Customer Case Studies **Published:** 2023-01-24 National Church Residences Case StudyNational Church Residences (NCR), the largest nonprofit provider of affordable senior housing and the largest manager of service coordinators in the U.S., was looking for a solution to replace its outdated SharePoint intranet.With a dispersed workforce located in over 360 communities across the country, communicating with employees was an ongoing challenge. After evaluating a handful of solutions, NCR was impressed with MangoApps’ capabilities and decided to make the intranet platform its new hub.In this case study, you will learn how National Church Residences uses MangoApps to:Improve top-down communications by replacing MailChimp with a platform that can reach 100% of its workforce.Create a space for employee engagement where people can interact and collaborate.Simplify the daily work life of employees by centralizing important resources, information, and tools in a single place.And more!Download this case study to get a better understanding of how MangoApps helped National Church Residences transform the way they communicate, collaborate, and share information. ## Key Outcomes - Improved employee engagement by 70% with MangoApps. - Sr. Comms Manager saves over 4 hrs/week distributing newsletters. **Download:** [Why SharePoint Was Insufficient](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_NCR.pdf) --- # A.S. Watson Benelux Video Case Study **Type:** Video Case Studies **Published:** 2023-01-24 A.S. Watson Benelux, a large European retail chain with over 1,700 stores and 27,000 employees, realized that they needed to update their internal communication processes to better connect with their young and on-the-go retail employees.A.S. Watson Benelux implemented MangoApps instead of other enterprise softwares for its mobile-friendly platform, customizability, and comprehensive toolset that addressed all of its needs.In this video, you will learn how A.S. Watson Benelux used MangoApps to:Engage and empower a young, dynamic workforceIncrease the level of communication & recognition among store clerks, managers, and corporate employeesEstablish a culture of interconnectedness among all facets of the organization --- # Tatts Group Video Case Study **Type:** Video Case Studies **Published:** 2023-01-23 Tatts Group, an Australia-based non-casino gambling company with 3,500 employees, had an outdated intranet solution that limited their collaboration and information sharing capabilities.Thus, Tatts Group began to look for a universal solution that would provide them with a centralized source of communication for all of their employees. After evaluating multiple intranet solutions, Tatts Group chose MangoApps due to its customizable apps and mobile capabilities.In this video, you will learn how Tatts Group used MangoApps to:Connect employees across the globeRun the platform without the help of their technology teamParticipate in real-time communication and collaboration --- # University of Illinois Video Case Study **Type:** Video Case Studies **Published:** 2023-01-23 The University of Illinois had a non-profit organization dedicated to helping inmates receive an education, known as the Education of Justice Program (EJP). EJP wanted to find an effective way to keep all staff members interconnected and capable of sharing information with one another.After doing extensive research to find the right fit for their program, EJP chose MangoApps for its usability and the inclusive community it provides for their team.In this video, you will learn how the University of Illinois used MangoApps to:Encourage workers to log on and participate in their online communityShare time-sensitive information with others in a quick, reliable wayBuild a successful and supportive community of people despite not sharing the same physical space‍ --- # How A Modern Intranet Improves Efficiency & Coordination **Type:** Customer Case Studies **Published:** 2023-01-19 Kelly-Moore Paints, a paint manufacturing and retail company headquartered in San Carlos, California needed to replace their legacy Intranet with a modern, centralized, easy-to-use hub for their 1,400 employees.Chief Information Officer, Jim Maul, searched for a solution to solve these issues. After an extensive, two-dozen vendor RFP process, Maul selected MangoApps for its consolidated platform, free-flowing communication, and multi-faceted functionality.In this case study, you will learn how Kelly-Moore Paints uses MangoApps to:Improve employee efficiency with a centralized information and knowledge hubIncrease the level of communication between field sales employees and the corporate officeEncourage a cohesive and inclusive company cultureAnd more!Download this case study to get a better understanding of how MangoApps helped Kelly-Moore Paints transform the way they communicate, collaborate, and share information.‍ ## Key Outcomes - Achieved over 95% monthly employee adoption. **Download:** [How A Modern Intranet Improves Efficiency & Coordination](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_KellyMoore.pdf) --- # What Do Your Frontline Workers Actually Want? **Type:** Webinars **Published:** 2023-01-18 Watch this video to learn what your frontline workers actually want, and how to transform alienated deskless workers into engaged employees.‍ --- # Intranet Deployment For Internal Comms **Type:** Webinars **Published:** 2023-01-16 Watch this video where Internal Comms expert - Melissa Hoyos of symplr, discusses five things you need to know when getting started with a new intranet platform. --- # Internal Communications Conference **Type:** Webinars **Published:** 2023-01-13 Watch this video where Internal Comms expert, Debra Helwig at Pinion (formerly known as KCoe Isom) explains how they achieved great employee adoption rates with their new intranet platform.‍ --- # Harnessing An Employee SuperApp **Type:** Customer Case Studies **Published:** 2023-01-12 OU Health Case StudyOU Health, a health system of hospitals, clinics, and centers of excellence in Oklahoma, was in need of a tool that could connect and engage its 10,000+ employees. Having previously used SharePoint as their primary intranet (and dealing with static intranet pages, limited communication, and poor content moderation), OU Health sought to replace SharePoint with a more modern and dynamic platform. With MangoApps' Employee SuperApp, OU Health is able to connect and engage its entire workforce within a HITRUST-certified environment. In this case study, you will learn how OU Health used MangoApps to:Connect & engage nearly 87% of their workforce within just a few monthsTransform the way employees communicate and collaborate while on the floorImplement a strong content governance structure while adhering to the healthcare industry's rigorous compliance requirementsAnd more!Download this case study to get a better understanding of how MangoApps helped OU Health transform the way they communicate, collaborate, and share information. ## Key Outcomes - Engaged over 87% of their 10,000 clinical employees in just a few months **Download:** [Harnessing An Employee SuperApp](https://mango-cdn.b-cdn.net/marketing/uploads/OUHealth_CaseStudy.pdf) --- # MangoApps - A Perfect SharePoint Alternative **Type:** Whitepapers & Ebooks **Published:** 2023-01-11 MangoApps vs. SharePointAt MangoApps, we get a lot of questions about SharePoint during the sales process. It is very common for companies to come to us looking to replace an old SharePoint implementation.In other cases, companies consider us as an option alongside adopting SharePoint as they look to replace an outdated homemade intranet.Although SharePoint has some features of a modern intranet, it is limited in many aspects, including:Requiring custom developmentNot working well on mobile devicesRequiring constant IT administrationConsisting of poor internal communicationsAnd more.Download this whitepaper for a deep dive into SharePoint’s strengths and weaknesses when it comes to modern employee expectations and needs, and a comparison to modern providers like MangoApps.‍ **Download:** [MangoApps - A Perfect SharePoint Alternative](https://mango-cdn.b-cdn.net/images/marketing/resources/MangoApps-vs-SharePoint-Whitepaper.pdf) --- # How to Successfully Launch Your Social Intranet **Type:** Whitepapers & Ebooks **Published:** 2023-01-11 Perfectly crafting an intranet, enterprise social network, or any other kind of collaboration platform takes time, patience, effort, and understanding. From outlining goals and finding a vendor to company branding and document organization, the initial preparation phase is what enables long term employee progress. **Download:** [How to Successfully Launch Your Social Intranet](https://mango-cdn.b-cdn.net/images/marketing/resources/MangoAppsWhitepaper-SocialIntranet.pdf) --- # How A Modern Intranet Engages A Younger Workforce **Type:** Customer Case Studies **Published:** 2023-01-11 A.S. Watson Benelux, a large European retail chain with over 1,700 stores and 27,000 employees, realized that they needed to update their internal communication processes to better connect with their young and on-the-go retail employees.Social Intranet Project Manager, Jan Kees Fokkens, turned to MangoApps to solve these issues. A.S. Watson Benelux implemented MangoApps instead of other enterprise softwares for its mobile-friendly platform, customizability, and comprehensive toolset that addressed all of its needs.In this case study, you will learn how A.S. Watson Benelux used MangoApps to:Engage and empower a young, dynamic workforce with an employee app for retailIncrease the level of communication & recognition among store clerks, managers, and corporate employeesEstablish a culture of interconnectedness among all facets of the organizationAnd more!Download this case study to get a better understanding of how MangoApps helped A.S. Watson Benelux transform the way they communicate, collaborate, and share information.‍ **Download:** [How A Modern Intranet Engages A Younger Workforce](https://mango-cdn.b-cdn.net/images/marketing/resources/CaseStudy_ASWatson.pdf) --- # A Solution For Clinical Communication Across Thousands Of Health Systems **Type:** Customer Case Studies **Published:** 2023-01-11 TeamHealth Case StudyTeamHealth, a leading physician practice with over 23,000 employees, used to communicate with their employees mostly over email. They hadn’t quite figured out how to make mobile collaboration work—especially for clinicians—until they partnered with MangoApps.With our platform, they’ve been able to sunset several costly tools and create a unified digital work hub where a single mobile app contains everything from training and policy information to SSO integrations with over 200 other applications.In this case study, you will learn how TeamHealth used MangoApps to:Connect physicians with nonclinical employees from across the nationEngage employees by allowing them to effortlessly share resources and company news with each otherCustomize their intranet to meet the unique challenges presented within the healthcare industryAnd more!Download this case study to get a better understanding of how MangoApps helped TeamHealth transform the way they communicate, collaborate, and share information. ## Key Outcomes - Realized over $2M in annual savings by consolidating systems. - Replaced SharePoint, two expensive file sharing solutions, company chat solution, email licenses for bulk of employees, and a custom-built LMS. **Download:** [A Solution For Clinical Communication Across Thousands Of Health Systems](https://mango-cdn.b-cdn.net/marketing/uploads/TeamHealth_CaseStudy.pdf) --- # Why Banks Choose MangoApps **Type:** Customer Case Studies **Published:** 2023-01-11 Banks & financial institutions face the common organizational problems of any company—overreliance on email, cluttered inboxes, siloed information, and poorly organized intranet, to name a few. Our banking customers love MangoApps because it has the deep security and permissions features they need, without compromising on the end user experience for their employees. **Download:** [Why Banks Choose MangoApps](https://mango-cdn.b-cdn.net/images/marketing/resources/MangoAppsMiniCaseStudies-Banks.pdf) --- # Security & Compliance at MangoApps **Type:** Whitepapers & Ebooks **Published:** 2023-01-10 A Detailed Look Into Security & Compliance at MangoAppsAt MangoApps, our mission is to help companies create a friction-free, empowered workplace so every employee has an opportunity to produce extraordinary results.For companies, efficiency creates new investment opportunities. For employees, success at work drives happiness and satisfaction. This cycle makes organizations more efficient every day.We know that intranet & communications are the front doors to your company’s data, and we have a special responsibility to keep it safe and secure. We’re committed to being transparent about our security practices and helping you understand our approach.Download this whitepaper for an in-depth look at MangoApps’ security and compliance practices.‍ **Download:** [Security & Compliance at MangoApps](https://mango-cdn.b-cdn.net/marketing/uploads/Security_Whitepaper.pdf) --- # Easy & Fast Onboarding With MangoApps **Type:** Whitepapers & Ebooks **Published:** 2023-01-10 This eBook represents a high-level overview of what you can expect in the onboarding/implementation process when you become a MangoApps customer.Interested in becoming a MangoApps customer? When you sign with us, you’ll receive:A dedicated support portal where you’ll work with our support team throughout the onboarding process and afterAccess to a 24/7 worldwide support team that is available to answer any questions at any timeA smooth implementation process that customizes your portal to match your company’s unique identityAnd more!Download this eBook to learn more about what the onboarding and implementation process will look like, and what is available to you post-launch of your MangoApps portal.‍ **Download:** [Easy & Fast Onboarding With MangoApps](https://mango-cdn.b-cdn.net/marketing/uploads/onboarding_ebook.pdf) --- # How To Declutter Your Intranet **Type:** Whitepapers & Ebooks **Published:** 2023-01-09 Why you need to declutter your intranetWith no policing, your intranet will grow cluttered over time. This is inevitable for teams who have homemade or SharePoint intranets that lack robust governance features. It can take a dedicated effort to prevent your intranet from becoming a wasteland of outdated and unused resources.In addition to lessened productivity, decreased engagement, and an overall lack of employee adoption, a cluttered intranet can also represent a large financial cost to your organization due to the amount of time wasted trying to navigate it.‍In this whitepaper, we will discuss the challenges of a cluttered intranet and provide 5 actionable steps you can take to begin decluttering your intranet, including:Establishing a data policy and sticking to itTaking inventory of the content within your intranetPaying attention to your own patternsAnd More!Download this whitepaper to learn more about the challenges a cluttered intranet provides, and what proactive steps you can take to make sure that it stays decluttered. To learn how MangoApps can take this work off your plate, read about our modern intranet platform.‍ **Download:** [How To Declutter Your Intranet](https://mango-cdn.b-cdn.net/images/marketing/resources/DeclutterYourIntranet_Whitepaper.pdf) --- # Why Healthcare Organizations Choose MangoApps **Type:** Customer Case Studies **Published:** 2023-01-09 Healthcare is all about the patients. You need a reliable product that can handle complex data security and HIPAA compliance, but also can be used without friction by non-tech workers, so they can focus on delivering the best care. **Download:** [Why Healthcare Organizations Choose MangoApps](https://mango-cdn.b-cdn.net/images/marketing/resources/MangoAppsMiniCaseStudies-Healthcare.pdf) --- # A Solution For Digital Tool Access Across Thousands Of Health Systems **Type:** Feature Datasheets **Published:** 2023-01-09 TeamHealthTeamHealth, a leading physician practice with over 23,000 employees, used to communicate with their employees mostly over email. They hadn’t quite figured out how to make mobile collaboration work—especially for clinicians—until they partnered with MangoApps.With our platform, they’ve been able to sunset several costly tools and create a unified digital work hub where a single mobile app contains everything from training and policy information to SSO integrations with over 200 other applications.Download this feature showcase to learn how switching to MangoApps empowered TeamHealth physicians with a unified mobile dashboard that had every tool they needed, accessible via SSO. **Download:** [A Solution For Digital Tool Access Across Thousands Of Health Systems](https://mango-cdn.b-cdn.net/resources/newpdfs/A%20Solution%20For%20Digital%20Tool%20Access%20Across%20Thousands%20Of%20Health%20Systems.pdf) --- # 4 Keys to Successful Project Collaboration & Execution **Type:** Whitepapers & Ebooks **Published:** 2023-01-06 How can you successfully use business social collaboration software to make your project collaboration & execution successful?Download this whitepaper to learn the four keys to lead to successful project collaboration. **Download:** [4 Keys to Successful Project Collaboration & Execution](https://mango-cdn.b-cdn.net/images/marketing/resources/MangoAppsWhitepaper-ProjectCollaboration.pdf) --- # Why Credit Unions Choose MangoApps **Type:** Customer Case Studies **Published:** 2023-01-05 Credit unions and financial service institutions face the common organizational problems of any company—overreliance on email, cluttered inboxes, siloed information, and poorly organized intranet, to name a few. Our credit union customers love MangoApps because it has the deep security and permissions features they need, without compromising on the end user experience for their employees.‍ **Download:** [Why Credit Unions Choose MangoApps](https://mango-cdn.b-cdn.net/images/marketing/resources/WhyCreditUnionsChooseMangoApps.pdf) --- # How A Digital Work Hub Can Reduce Employee Burnout In Your Healthcare Organization **Type:** Whitepapers & Ebooks **Published:** 2023-01-05 How to Reduce Employee Burnout In Your Healthcare OrganizationBurnout is on the rise among clinicians and other healthcare workers. Prior to the pandemic, nearly 40% of nurses reported they felt burned out because of long work hours, greater workloads, poor environments, and caring for significantly ill patients. In 2021, that figure had jumped all the way to 70%.With countless contributing factors to burnout (one being the extended trauma of fighting the pandemic for the last few years), there has never been a more important time to prioritize the digital employee experience of your healthcare workforce.‍In this whitepaper, we will make the case for how a modern digital work hub can reduce burnout in your healthcare organization, including:Improved agility in the face of COVID-19Creating a tailored employee experienceFostering continuous education among medical professionalsAnd more!Download this whitepaper to get up to speed on why your healthcare organization needs to evolve in its employee experience offerings, and make the switch to a digital work hub.‍ **Download:** [How A Digital Work Hub Can Reduce Employee Burnout In Your Healthcare Organization](https://mango-cdn.b-cdn.net/images/marketing/resources/WhitepaperHowADigitalHubReducesBurnoutInHealthcare.pdf) --- # Improving Efficiency & Unifying Resources **Type:** Customer Case Studies **Published:** 2023-01-05 Huitt-Zollars, a full-service design firm, was looking for a modern intranet platform that could provide their mix of field and desk employees with the resources and tools needed to do their jobs efficiently.Given the task to find an alternative solution, Huitt-Zollars researched a handful of modern intranet platforms and ultimately decided to move forward with MangoApps after finding that it offered everything they were looking for within a cloud interface.In this case study, you will learn how Huitt-Zollars uses MangoApps to:Communicate project wins and announcements to employeesBuild a workplace community that encourages collaborationImprove efficiency, centralize resources, and make information easily accessibleAnd more!Download this case study to get a better understanding of how MangoApps helped Huitt-Zollars transform the way they communicate, collaborate, and share information. **Download:** [Improving Efficiency & Unifying Resources](https://mango-cdn.b-cdn.net/marketing/uploads/CaseStudy_Huitt-Zollars.pdf) --- # Engage With Your Deskless Workers **Type:** Whitepapers & Ebooks **Published:** 2023-01-05 Engage With Your Deskless WorkersThis essential, straightforward guide will tackle your questions about the relationship between deskless workers, technology, and leadership. Download this whitepaper to get up to speed about the conversations many companies are having today about how to better reach and engage with their deskless workers. Deskless workers make up 80% of the workforce, yet only 22% feel their job is important to the company vision. This is a pretty extreme divide, and research indicates that it stems from lacking both communication from leadership and technological enablement.This essential, straightforward guide will tackle your questions about the relationship between deskless workers, technology, and leadership, such as:Why are deskless workers hard to reach, and how is this affecting my bottom line?Is it worth the investment to enable them with better technology?What communication strategies can I use to promote better engagement among deskless workers?The answers to these questions will give you a fundamental understanding of how deskless workers want to be reached and why it’s important, as well as arm you with data and strategies that will inform your decision-making.Download this whitepaper to get up to speed about the conversations many companies are having today about how to better reach and engage with their deskless workers. **Download:** [Engage With Your Deskless Workers](https://mango-cdn.b-cdn.net/images/marketing/resources/MangoAppsWhitepaper-DesklessWorkers.pdf) --- # MangoApps ROI Report **Type:** Whitepapers & Ebooks **Published:** 2023-01-04 Deep dive into the ROI of MangoApps Digital Work HubThis report examines MangoApps’ wide breadth of functionality through the lens of evaluating the returns our customers see on the investment of working with us. Although it’s difficult to measure the effects of a wholesale change to the way information flows through your team, we have used a mix of rigorous analysis and references to industry research to lay out a compelling case.‍ Deep dive into the ROI of MangoApps Digital Work HubThis report examines MangoApps’ wide breadth of functionality through the lens of evaluating the returns our customers see on the investment of working with us.We have quantified these results across the following areas:Reducing reliance on emailImproving the speed with which people find informationConsolidating your tech stackImproving knowledge transfer and reducing duplicated workReducing onboarding and training costsReducing strain on ITDigitizing and automating business processesCreating a culture of sharing and empowermentAlthough it’s difficult to measure the effects of a wholesale change to the way information flows through your team, we have used a mix of rigorous analysis and references to industry research to lay out a compelling case.‍ **Download:** [MangoApps ROI Report](https://mango-cdn.b-cdn.net/marketing/uploads/ROI_Report.pdf) --- # MangoApps Datasheet **Type:** Whitepapers & Ebooks **Published:** 2022-12-06 A modern work platform means a single source of truth for your employees, where everything they need is easy to find. Wherever they are, top floor to shop floor, MangoApps is right there with them. MangoApps was designed to unify your employee experience by combining intranet, communication, collaboration and training into one intuitive, mobile-accessible workspace. **Download:** [MangoApps Datasheet](https://mango-cdn.b-cdn.net/images/marketing/resources/MangoApps_Datasheet.pdf) --- # Tool Sprawl - A Toxin to Productivity **Type:** Whitepapers & Ebooks **Published:** 2022-11-10 80% of employees attribute lack of collaboration or ineffective business communication tools as the primary cause of workplace failures.Download this whitepaper to learn the drawbacks of tool sprawl and what best practices your organization can implement to avoid it. **Download:** [Tool Sprawl - A Toxin to Productivity](https://mango-cdn.b-cdn.net/images/marketing/resources/MangoAppsWhitepaper-ToolSprawl.pdf) --- # MangoApps LMS Data Sheet **Type:** Whitepapers & Ebooks **Published:** 2022-10-27 Transform your business with a cloud-based training platform that is powerful, intuitive, affordable, and mobile friendly.Your employees are the lifeblood of your business, and a strong training program is the best way to invest in their long-term success and make them feel valued enough to stick around for the long haul.‍ **Download:** [MangoApps LMS Data Sheet](https://mango-cdn.b-cdn.net/images/marketing/resources/MangoAppsTrainingDataSheet.pdf) --- # Why do companies need a platform for company apps **Type:** Whitepapers & Ebooks **Published:** 2022-10-12 As organizations worldwide adapt to a fundamental shift in how and where we work, most businesses encounter a similar set of challenges. In this whitepaper, you'll receive a summary of the challenges we hear from prospective customers every day. **Download:** [Why do companies need a platform for company apps](https://mango-cdn.b-cdn.net/images/marketing/resources/MangoAppsWhitepaper-CompanyApp.pdf) --- # How MangoApps Perfectly Complements G Suite **Type:** Whitepapers & Ebooks **Published:** 2022-10-05 G Suite customers often ask us how MangoApps works with G Suite? What can MangoApps do that G Suite doesn’t? Here are some of the common gaps in G Suite that MangoApps fills and why you need both systems.‍ **Download:** [How MangoApps Perfectly Complements G Suite](https://mango-cdn.b-cdn.net/marketing/uploads/mango_gsuite_new.pdf) --- # How MangoApps perfectly complements Microsoft 365 **Type:** Whitepapers & Ebooks **Published:** 2022-10-04 Microsoft 365 customers often ask us how MangoApps works with Microsoft 365? What can MangoApps do that Microsoft 365 doesn’t? Here are some of the common gaps in Microsoft 365 that MangoApps fills and why you need both systems. **Download:** [How MangoApps perfectly complements Microsoft 365](https://mango-cdn.b-cdn.net/marketing/uploads/MangoAppsWhitepaper-Microsoft365.pdf) --- # Work Smarter: MangoApps Integrations **Type:** Whitepapers & Ebooks **Published:** 2022-09-28 Replacing the tools your company uses today is not always an option. Instead, compliment your existing productivity, collaboration, and communication tools with MangoApps, and increase your ROI.Download this whitepaper to learn about how MangoApps integrates with existing software solutions such as Microsoft 365, GoogleApps, and Slack.‍ **Download:** [Work Smarter: MangoApps Integrations](https://mango-cdn.b-cdn.net/images/marketing/resources/MangoAppsWhitepaper-Integrations.pdf) --- # Employee Engagement is No Longer Optional **Type:** Whitepapers & Ebooks **Published:** 2022-09-22 Only 32% of employees are classified as engaged, leaving 70% of the world’s workforce either indifferent or actively disinterested in their occupation. Actively disengaged employees are estimated to cost organizations throughout the United States between $483 billion and $605 billion every year.Download this whitepaper to learn more about how employee engagement is no longer optional.‍ **Download:** [Employee Engagement is No Longer Optional](https://mango-cdn.b-cdn.net/images/marketing/resources/MangoAppsWhitepaper-EmployeeEngagement.pdf) --- # Digital Workplace Platform For The Modern Workplace **Type:** Whitepapers & Ebooks **Published:** 2022-08-19 There is a trend across industries that is seeing more and more organizations switching to a modern digital workplace platform. Outdated intranet solutions are simply not cutting it anymore.With employee experience at the top of the priority list, the demand for a modern platform that can house employee communications, work management, collaboration, and training is growing exponentially.Download this whitepaper to learn more about why organizations are making the switch to a modern digital work hub.‍ **Download:** [Digital Workplace Platform For The Modern Workplace](https://mango-cdn.b-cdn.net/images/marketing/resources/MAngoAppsWhitepaper-DigitalHub2.pdf) --- # Why A Digital Hub is Critical For Employee Engagement **Type:** Whitepapers & Ebooks **Published:** 2022-08-11 A digital workplace includes all of the software systems within a company that are internally focused and are required for employees to use in order to do their job. A Digital Workplace Hub facilitates employee engagement, promotes positive employee experiences and helps to create and support a great organizational culture. **Download:** [Why A Digital Hub is Critical For Employee Engagement](https://mango-cdn.b-cdn.net/images/marketing/resources/MangoAppsWhitepaper-DigitalHub.pdf) --- # Why Activity Stream Is Replacing Email In The Workplace **Type:** Whitepapers & Ebooks **Published:** 2022-05-10 Enterprise social networking services are replacing e-mail as the primary vehicle for interpersonal communications for business users.Download this whitepaper to learn how you can replace outdated email platforms with a modern messaging solution aimed at sending relevant comms to your employees when they need it most.‍ **Download:** [Why Activity Stream Is Replacing Email In The Workplace](https://mango-cdn.b-cdn.net/images/marketing/resources/MangoAppsWhitepaper-ActivityStreams.pdf) --- # Report: Digital Workspace Data Quadrant **Type:** Analyst Report **Published:** 2021-06-09 This comprehensive look at the Digital Workspace market is a must-have for anyone looking to make an informed decision in this space. It compiles 204 user reviews of 14 platforms and rates MangoApps #1 overall. **Download:** [Report: Digital Workspace Data Quadrant](https://mango-cdn.b-cdn.net/images/marketing/resources/Digital_Workspace_Vendor_Rankings_2021.pdf) --- # Account Setup at First Sign-In **Category:** System-features **Section:** Advanced Features **Updated:** 2026-10-14 What a new person is asked the first time they sign in, how an admin chooses which steps appear in Onboarding Settings, and where to see who has not finished. # Account Setup at First Sign-In ## 1. What it is Account setup is the short run of steps a person walks the first time they sign in. It collects their profile, how they want to be notified, when they can work, and a password of their own. Until they finish, every page they open sends them back to the steps. It serves three readers. An employee walks it once. A manager is told when a new report has finished. An admin chooses which steps appear and can see who is still part-way through. - **Enablement:** always on. It is part of the platform, not an app, and needs no licence. An admin shapes it in **Admin → General Settings → Onboarding**. - **What it is not:** it is not HR onboarding. The forms, documents and Onboarding Status on an employee record are a separate thing that HR works. A person can finish account setup in five minutes while their HR onboarding is still open, and the two are counted separately everywhere. ## 2. Standing it up Account setup works with no configuration. These steps are for an admin who wants to check or change what new people see. 1. Go to **Admin → General Settings**, find the **Onboarding** card and click **Manage Onboarding**. The page is titled **Onboarding Settings**. 2. In the **Onboarding Steps** card, read the badge on each step. **Auto resolves to: Shown** or **Auto resolves to: Hidden** tells you what a new person gets today. 3. Leave a step on **Auto (recommended)**, or choose **Always Show** or **Always Hide** for it. Read the warning under a step before hiding it. 4. If your company signs in through single sign-on, an **SSO Settings** card appears. Decide whether **Lock fields provided by organization** stays on. 5. Click **Save Settings**. 6. Add and invite your people in **Admin → Users**. Each one meets the steps at their first sign-in, on a computer or a phone. **The pairing that catches people out:** the **Go-live date** at the top of the same page does not switch account setup on, off, or change who walks it. It belongs to HR's alerts. Section 3 explains the split. ## 3. How it fits together **The four steps, in order.** A person sees only the steps that apply to them, and the progress panel beside each step lists exactly those. | Step, as the person sees it | What it asks | When Auto shows it | |---|---|---| | **Your profile** | First and last name, profile photo, phone number, time zone, language | Always | | **Notifications** | Email and SMS on or off, and an optional phone number to verify. In-app notifications are always on | When Shift Marketplace, On-Call Management or Calendar is enabled | | **Availability & shifts** | Minimum and maximum hours per week, maximum consecutive days, extra shifts, weekend and holiday availability | When Shifts & Scheduling is enabled | | **Security setup** | A new password, entered twice | For people who sign in with a password | **One step, three names.** The same step is labelled differently depending on where you read it. Knowing this saves a support call. | The person's progress panel | Onboarding Settings | "Last reached" on an admin profile | |---|---|---| | Your profile | Profile Completion | Complete Your Profile | | Notifications | Notification Preferences | Notification Preferences | | Availability & shifts | Availability & Shift Preferences | Availability & Shift Preferences | | Security setup | Security Setup | Security Setup | **No step can be skipped by the person.** There is no skip button. A step that is shown must be saved before the next one opens, and steps open in order. What a person may leave empty is inside a step: the phone number on **Notifications** is optional, for example. Only an admin removes a step, by hiding it for everyone. **Auto, Always Show, Always Hide.** Auto decides from what your company has enabled, as the table above shows. **Always Show** shows the step whatever is enabled. **Always Hide** removes it, with two limits: - Hiding **Your profile** is ignored for anyone missing a first or last name. They still see the step. - Hiding **Security setup** leaves people on the temporary password they were given, unless your password policy expires it. When **Notifications** is hidden, no Email or SMS choice is recorded for the person. Each notification category keeps its normal default. **Who is not asked for a password.** Two groups pass over **Security setup** however the step is set: - People who sign in through single sign-on. They have no password here to set. - People who have already chosen their own password. That covers someone who joined from a team invite, used a set-password link or a password reset link, or replaced an expired temporary password when they signed in. They are not asked for one again, unless an administrator sets or resets their password before they finish; then the step asks them to choose their own. A Super Admin who is shown the step gets a **Keep my current password** box, ticked to begin with, and can leave it ticked instead of choosing a new one. **The go-live date is HR's, not account setup's.** The **Go-live date** in the **Onboarding Tracking** card decides which employees HR tracks. For people hired on or after it, the **Missing I-9** and **Onboarding task** HR alerts can fire, sent to the recipients chosen for each alert, and they are counted in the statistics panel. People hired earlier are treated as pre-existing records. Account setup ignores the date entirely: anyone who has not finished is held at the steps, whenever they were hired, and whether or not a date is set. **Finishing has four effects.** - The person is let into the rest of the product. The finished page offers **Continue where you left off** when the steps interrupted them on the way to a page, and **Go to Dashboard** otherwise. - Their manager gets one notification, titled with the person's name and "is set up and ready". It links to the person's profile. - If HR's Onboarding Status for the person was blank or Not Started, it moves to In Progress. - The person is emailed that their account is set up, the first time they finish. No email goes when your company has turned that email off or the person has no email address. **The manager is told once.** The notification goes to the person's manager in your company. If that manager has left, it goes to the next manager up the reporting line and says why. If the person has no manager, nobody is notified. A person who starts over and finishes again does not trigger a second notification. **Computer, phone and mobile app share the same steps.** A person on a phone gets the same steps in the phone layout. A step already answered in the mobile app is not asked again on the web. ## 4. Running it ### See who has signed in but not finished 1. Go to **Admin → Users**. 2. Open **More filters**. 3. In the activity filter, choose **Signed in, account setup not finished**. The list shows people who have signed in at least once and are still held at the steps. People who have never signed in are under **Never Logged In** in the same filter. ### Check one person Open the person from **Admin → Users**. Under their invitation status, a line beginning **Account setup:** reads one of: - **finished**, with the date - **hasn't signed in yet** - **not finished — last reached** and the name of a step - **not finished** Someone you have invited shows **Invited**, with the date the invitation was sent for invitations sent since the date began to be recorded. If the invitation email could not be delivered, the profile goes back to **Pending Invitation** and says the invitation could not be delivered, so you can check the address and send it again. "Last reached" can name a step you have since hidden, which is why it does not say "is on". The Onboarding section of the employee's profile shows the same fact as **Account setup finished** with the date, or **Account setup: not finished yet**. It is shown, not typed: the product sets it when the person finishes. ### Read it beside HR onboarding Open the **New Hires Report**. Each person listed carries HR's status and, underneath, **Account setup done** with the date or **Account setup not finished**. The CSV export has an **Account setup** column reading **Done** with the date, or **Not finished**. The statistics panel on **Onboarding Settings** counts **Finished account setup (the steps above)** and **Not yet finished account setup** apart from **HR onboarding incomplete**. Those counts appear once a go-live date is set. ### Let someone walk the steps again The person does this themself. On the finished page, they click **Start over?** and confirm. The steps reopen with their earlier answers already filled in, and they are held at the steps until they finish again. Their password is not asked for again. ### Look at the steps as someone else Viewing as a person does not walk their setup for them. The step forms are shown disabled, nothing can be saved, and **Start over?** is refused. An admin viewing as someone is not held at that person's steps. ## 5. Settings All of these are on **Admin → General Settings → Onboarding → Manage Onboarding**. | Setting | Where | Default | What it changes | |---|---|---|---| | Profile Completion | Onboarding Steps | Auto (recommended) — shown | Whether new people see **Your profile**. Always Hide is ignored for anyone missing a first or last name | | Notification Preferences | Onboarding Steps | Auto (recommended) — shown when Shift Marketplace, On-Call Management or Calendar is enabled | Whether new people choose Email and SMS at first sign-in | | Availability & Shift Preferences | Onboarding Steps | Auto (recommended) — shown when Shifts & Scheduling is enabled | Whether new people enter hours and weekend and holiday availability | | Security Setup | Onboarding Steps | Auto (recommended) — shown | Whether people who sign in with a password must choose a new one. Never shown to single sign-on users | | Lock fields provided by organization | SSO Settings (appears when single sign-on is configured) | On | Profile fields filled in by single sign-on are read-only on **Your profile**. Fields that were not pre-filled stay editable | | Go-live date | Onboarding Tracking | Empty (tracking off) | Which employees the HR alerts and the statistics panel track. Does not change account setup | ## 6. More help - **[Account Setup FAQ](/help/articles/platform_account_setup_faq)** — questions from employees, managers and admins: changing an answer later, why someone is stuck, the limits each answer takes. - **[Users, Roles & Permissions](/help/articles/admin_users_and_roles)** — adding people and sending invitations. - **Security & Sign-On** — password policy and single sign-on. - **[Mobile — What Employees Get](/help/articles/platform_mobile)** — signing in on a phone. - Ask AI — the assistant answers questions about account setup from these articles. **Keywords:** account setup, first sign-in, first login, first login steps, account setup steps, onboarding settings, onboarding steps, new employee setup, set up my account, your profile, security setup, set a password, availability and shifts, notification preferences, always hide, always show, go-live date, start over, account setup not finished, new hire signed in --- # Account Setup at First Sign-In FAQ **Category:** Faq **Section:** Advanced Features **Updated:** 2026-10-14 Answers about the first sign-in account setup steps and Onboarding Settings — for the employee walking them, the manager waiting on a new hire, and the admin running them. # Account Setup at First Sign-In FAQ Answers to common questions about the steps a person walks the first time they sign in, and about the Onboarding Settings page that shapes them. For what account setup is and how it fits together, see the [Account Setup Overview](/help/articles/platform_account_setup). --- ## Walking the steps ## What will I be asked the first time I sign in? Up to four steps, in this order: **Your profile**, **Notifications**, **Availability & shifts**, and **Security setup**. You see only the ones that apply to you, so your list may be shorter. The panel beside each step shows which are done and which are left. ## Can I skip a step and come back to it later? No. There is no skip button, and each step must be saved before the next one opens. Until you finish, every page you open sends you back to the steps. Some fields inside a step are optional — the phone number on **Notifications** is one — so you can leave those empty and continue. You can sign out part-way and pick up at the same step next time. ## Why wasn't I asked to set a password? One of these reasons: - You sign in through your company's single sign-on, so there is no password here to set. - You already chose your own password — from a team invite, a set-password link, a password reset link, or the page that asks you to replace an expired password — so you are not asked again. - Your administrator has hidden the **Security setup** step. ## Why don't I see the Notifications or Availability & shifts step? Those steps appear only when they apply. **Availability & shifts** is shown when your company uses Shifts & Scheduling. **Notifications** is shown when your company uses Shift Marketplace, On-Call Management or Calendar. An administrator can also show or hide either step for everyone. ## Why can't I turn on Email or SMS on the Notifications step? Email is off and cannot be switched on when your account has no email address, or when mail cannot be delivered to it. SMS can be switched on only once your phone number is verified: add the number and verify it on the step, or do it later in **Account Settings → Notifications**. SMS is also unavailable if your company has it turned off, or if you replied STOP to our texts. In-app notifications are always on. ## If I turn Email off, can I still reset my password? Yes. Password reset emails are still sent to you. Sign-in codes are too, where your company allows signing in with a code. ## Can I do this on my phone? Yes. The same steps appear in the phone layout, in the same order. A step you already answered in the mobile app is not asked again on the web. --- ## Changing answers afterwards ## Where do I change what I entered during account setup? Each answer has its own place, and the finished page links to the ones open to you: | Answer | Where to change it | |---|---| | Email, SMS and other notification choices | **Account Settings → Notifications** | | Photo and phone number | Your profile (when your company lets people edit their own profile) | | Hours, weekend and holiday availability | **Account Settings → Availability** (when your company uses Shifts & Scheduling) | | Password | **Account Settings → Security** (not shown to single sign-on users) | | Language | **Account Settings → Preferences** | On a phone, **Availability**, **Password & security** and **Language** open the full site. ## Why can't I change my name or time zone? Your company may reserve those fields for an administrator. When it does, the finished page names which and tells you to ask your administrator. If you signed in through single sign-on, fields your organization filled in can also be read-only on the **Your profile** step. ## What does Start over do? **Start over?** is on the finished page. After you confirm, the steps reopen from the first one with your earlier answers already filled in, so you can change them as you go. Nothing you answered is cleared. You are held at the steps again until you finish them. Your password is not asked for again. To get back to the finished page later, open `/onboarding/completed`. --- ## For managers ## How do I know my new hire has finished setting up? You get a notification titled with their name and "is set up and ready". It opens their profile, where their contact details are. When your company uses Shifts & Scheduling, the profile also has a **When they can work** card. It shows their availability answers once they have saved them, and says no answers are on file until then. ## Why didn't I get a notification when my new hire finished? The notification goes to the person's manager on record in your company. Check that you are set as their manager. If their manager has left the company, it goes to the next manager up the reporting line. If the person has no manager, nobody is notified. ## My report started over and finished again. Why wasn't I told a second time? The notification is sent once per person. Starting over and finishing again does not send another. --- ## For admins ## Where do I choose which steps new people see? Go to **Admin → General Settings**, find the **Onboarding** card and click **Manage Onboarding**. In the **Onboarding Steps** card, set each step to **Auto (recommended)**, **Always Show** or **Always Hide**, then click **Save Settings**. The badge on each step shows what Auto resolves to for your company today. ## What does Always Hide actually do, and when is it ignored? **Always Hide** removes the step for everyone, with these limits: - **Profile Completion:** ignored for anyone missing a first or last name. They still see the step. - **Security Setup:** people stay on the temporary password they were given, unless your password policy expires it. - **Notification Preferences:** no Email or SMS choice is recorded for the person. Each notification category keeps its normal default. If every step is hidden for a person, their setup completes on their first visit and they go straight in. ## Do single sign-on users go through account setup? Yes, but not **Security setup** — they skip it whatever that step is set to. Their **Your profile** step arrives pre-filled. While **Lock fields provided by organization** is on, the pre-filled fields are read-only and the rest stay editable. That switch is on by default and appears on **Onboarding Settings** only when single sign-on is configured. ## Does the go-live date decide who has to walk account setup? No. The **Go-live date** governs HR's side only: which employees the **Missing I-9** and **Onboarding task** HR alerts can fire for, and who is counted in the statistics panel. Account setup does not read it. Anyone who has not finished is held at the steps, whatever their hire date and whether or not a date is set. ## How do I see who has signed in but not finished account setup? Go to **Admin → Users**, open **More filters**, and in the activity filter choose **Signed in, account setup not finished**. People who have never signed in are listed under **Never Logged In** instead. To check one person, open them from the list and read the **Account setup:** line. It says finished with the date, hasn't signed in yet, or not finished with the step they last reached. Someone you have invited also shows **Invited**, with the date the invitation was sent for invitations sent since the date began to be recorded. ## Where does account setup show up in HR reporting? On the **New Hires Report**, each person listed has **Account setup done** with the date, or **Account setup not finished**, under their HR status. The CSV export carries the same fact in an **Account setup** column. On **Onboarding Settings**, the statistics panel counts **Finished account setup (the steps above)** and **Not yet finished account setup** once a go-live date is set. ## Can I finish or reset someone's account setup for them? No. Account setup is the person's own. When you view as someone, their step forms are disabled, nothing saves, and **Start over?** is refused. The finish date on their profile is shown, not typed, so it cannot be entered by hand either. --- ## When something looks wrong ## A new hire says every page sends them back to the setup steps. What is wrong? Nothing — they have not finished. Each step that is shown must be saved, in order, and the last one completes the setup. Check their **Account setup:** line in **Admin → Users** to see the step they last reached, and ask what message that step shows them. Common ones: maximum hours per week lower than the minimum, a phone number shorter than 7 characters, or a missing password confirmation. Hours per week take 0 to 80, and maximum consecutive days take 1 to 7 or No preference. ## HR's report still lists someone as incomplete, but they finished account setup. Which is right? Both. They are two different facts. Account setup is the first sign-in steps. HR's Onboarding Status is set on the employee record as forms and documents come in. Finishing account setup moves a blank or Not Started status to In Progress, and no further. The **New Hires Report** prints both on each row so they can be read together. --- ## More help - [Account Setup Overview](/help/articles/platform_account_setup) — what account setup is and how it fits together. - [Users, Roles & Permissions](/help/articles/admin_users_and_roles) — adding people and sending invitations. - [Mobile — What Employees Get](/help/articles/platform_mobile) — signing in on a phone. - Ask AI — the assistant answers account setup questions from these articles. **Keywords:** faq, account setup, first sign-in, first login, first login steps, onboarding settings, skip a step, set a password, temporary password, change my time zone, change my availability, start over, always hide, always show, go-live date, single sign-on, account setup not finished, new hire is set up and ready, stuck on setup --- # Agent Workflows — AI Playbooks **Category:** System-features **Section:** Advanced Features **Updated:** 2026-08-12 How to build, run, and automate AI playbooks — reusable multi-step action sequences that span apps and run on demand or on a schedule. # Agent Workflows — AI Playbooks ## 1. What it is AI Playbooks let you build reusable, multi-step action sequences that span multiple apps. A playbook chains tool calls across domains — scheduling, HR, forms, service desk, and others — into a single runnable procedure. Users trigger playbooks through Ask AI by matching a trigger phrase, admins run them manually from the admin surface, or automation triggers fire them on a schedule or in response to a platform event. - **Enablement:** This is a platform admin surface, not a separately licensed app. Any admin can access it at **Admin → AI Playbooks** (the direct URL is `/admin/agent_workflows`). When the Loop app is enabled for your business, these pages move into the Loop app tabs instead. - **What it is not:** Playbooks are not the same as the AI Operations kill switches. AI Operations (Admin → AI Operations) governs whether agents can act at all; playbooks define *what* a sequence of actions does and *when* it runs. ## 2. Standing it up 1. Go to **Admin → AI Playbooks**. 2. Click **New Playbook**. Give it a name (required, max 100 characters), pick a primary domain, and optionally add trigger phrases so users can invoke it from Ask AI. 3. Build the steps. You have two paths: - **Build with AI**: type a plain-English description of what the playbook should do. AI drafts the name, description, steps, and declared inputs for you. Review the result in the visual step builder and edit before saving. - **Manual**: click **Add step** and pick an app (domain) and action (tool) for each step. Pass values between steps using `$inputs.` or `$steps..`. 4. Mark any step that writes data as **Require confirmation** — it will pause for admin approval before executing. 5. Save. The playbook is active by default. Users whose Ask AI query matches a trigger phrase will see it offered; admins can also run it manually from the playbook detail page. To set up unattended execution, create an **Automation Trigger** from the Automation Triggers tab. A playbook that pauses part-way through to ask the user for a value cannot be automated — the trigger will not save, because nobody is at the keyboard to answer. ## 3. How it fits together **Playbook** — A named, versioned sequence of steps, laid out in the **Steps** designer. Each playbook belongs to one primary domain (for grouping and routing) but its steps can call tools from any domain. A playbook with steps is "executable" and can be run; one without steps is a "prompt-hint" that only guides the AI's response. **System playbooks vs tenant playbooks** — MangoApps provides global system playbooks (visible in the "System playbooks" section at the bottom of the index page). These are available to your users through Ask AI by default. You can: - **Disable** a system playbook for your business so it no longer appears in Ask AI. - **Clone** a system playbook into an editable tenant copy (the copy tracks its parent but is fully independent). Tenant-owned playbooks are managed with the normal activate/deactivate/delete controls. **Trigger** — Binds a playbook to a schedule or a platform event so it runs unattended. Scheduled triggers use cron expressions interpreted in your business's time zone. Event triggers fire when a matching platform event occurs (leave request created, shift cancelled, form submitted, etc.). A trigger runs as a specific user (set at creation) and has built-in duplicate-run protection: if a previous run from the same trigger hasn't settled within 24 hours, the next occurrence is skipped. **Run** — One execution of a playbook. Each run pins the execution plan at start so mid-run edits to the playbook do not change a run already in progress. The run tracks per-step results (ok, failed, skipped), an overall status, and wall-clock duration. Statuses: **Pending**, **Running**, **Waiting**, **Awaiting confirmation**, **Confirmed**, **Completed**, **Failed**, **Cancelled**. **Confirmation gate** — Steps marked **Require confirmation before running** (or flagged as risky by their agent) pause the run and send an approval request to the run owner's Inbox. The approval window is 7 days; after that the confirmation expires. Automation triggers can pre-approve specific tools via the auto-approve setting. ## 4. Running it ### Creating a playbook with AI 1. Go to **Admin → AI Playbooks → New Playbook**. 2. In the **Build with AI** panel at the top, describe what the playbook should do. 3. Click **Draft playbook**. AI generates the name, description, steps, inputs, and trigger phrases. 4. Review every step in the visual step builder. AI can only use tools and domains that actually exist in your platform — unknown domains or tools are stripped server-side — but parameter values and step ordering should be verified. 5. Save when satisfied. ### Running a playbook manually 1. Go to **Admin → AI Playbooks** and click a playbook name. 2. Click **Run** (the playbook must be active and have at least one step). 3. Fill in any declared inputs and confirm. 4. You are redirected to the run detail page. If a step requires confirmation, an approval request appears in your Inbox. ### Setting up an automation trigger 1. Go to the **Automation Triggers** tab. 2. Click **New Trigger**, pick a playbook, and choose scheduled or event. - **Scheduled:** enter a cron expression. The first run time is shown before you save. - **Event:** pick a platform event name from the suggestions. Optionally add conditions ("Only if" rules) to filter which events fire the trigger. 3. Fill in the playbook's required inputs. The trigger will not activate with missing required inputs. 4. Save. The trigger is active by default. ### Reviewing run history 1. Go to the **Run history** tab. 2. Filter by status, playbook, or date range. Each row shows the playbook name, who ran it, status, step counts, and duration. 3. Click a run to see per-step results, dispatched parameters, and any error messages. 4. Use **Export CSV** to download the filtered history. 5. A failed run can be retried; a stuck run (**Pending**, **Running**, **Waiting** or **Awaiting confirmation**) can be cancelled. ### Managing system playbooks 1. Scroll to the **System playbooks** section at the bottom of the AI Playbooks index. 2. To hide a system playbook from your users' Ask AI, click **Disable for this business**. 3. To re-enable it, click **Enable for this business**. 4. To customize a system playbook, click **Clone to customize** — this creates an editable tenant copy. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Active | Playbook detail page (toggle) | On | Inactive playbooks are not matched by Ask AI and cannot be run. Automation triggers bound to an inactive playbook will not fire. | | Require confirmation (per step) | Step builder, per-step checkbox | Off | When on, the run pauses at this step and sends an approval request to the runner's Inbox. | | Auto-approve (per trigger) | Automation trigger form | Off | When on, confirmation-gated steps are approved automatically for this trigger's unattended runs. Can be scoped to specific tools. | | Trigger active | Automation trigger list (toggle) | On | Paused triggers do not fire on their next cron tick or event. | ## 6. More help - **AI Operations** — pause agents, review pending approvals, and monitor agent health. - **AI Consoles** — per-solution control surface for autonomy and approval settings. - Ask AI — the assistant answers questions about playbooks from these articles. **Keywords:** ai playbooks, playbooks, agent workflows, playbook, automation trigger, run playbook, playbook run, step builder, scheduled playbook, event trigger, system playbook, clone playbook, suppress playbook, playbook automation, build with ai, execution plan, trigger phrases, confirm step, run history --- # AI Assistants — Claude, ChatGPT, Slackbot and Microsoft 365 Copilot **Category:** System-features **Section:** Advanced Features **Updated:** 2026-10-16 How people use OneMango from an AI assistant, the one switch an admin turns on in Admin, Security, Connectors, and how access, approvals and revoking work. # AI Assistants ## 1. What it is People can use OneMango from the AI assistant they already work in: Claude, ChatGPT, Codex, Slackbot or Microsoft 365 Copilot. They ask in their own words ("what needs me this shift?", "approve Maria's time off"), and the assistant looks things up or makes the change in OneMango as that person, with that person's permissions. - **Enablement:** off by default. An administrator turns it on for the whole organization in **Admin → Security → Connectors**. - **What it is not:** it is not the Slack or Microsoft Teams connection that sends OneMango notifications and runs `/mango` commands. That is set up separately in **Admin → Organization → Integrations → Manage Messaging & Sharing** (see *Slack* and *Microsoft Teams*). It is also not Ask AI inside OneMango, which has its own settings. ## 2. Standing it up 1. Go to **Admin → Security → Connectors** and turn on **Let people connect AI assistants**. 2. Make OneMango available in the assistant: - **Claude and ChatGPT:** each person adds MangoApps as a connector in their assistant. The steps are on the setup pages at mangoapps.com/claude and mangoapps.com/chatgpt. - **Slackbot:** your Slack workspace admin adds the MangoApps Workforce app to Slack. After that, anyone can ask Slackbot about their OneMango work. - **Microsoft 365 Copilot:** your Microsoft 365 admin makes the MangoApps Workforce agent available to your people. They then open it in Copilot, where suggested prompts such as *My day* and *Approvals* show what it can do. 3. The first time someone uses it, the assistant asks them to sign in to OneMango and approve the access. They can only connect to the OneMango organization they belong to. 4. To confirm it worked, reopen **Admin → Security → Connectors**. Each assistant someone has connected is listed with who authorized it and when it was last used. If connectors are off, the sign-in screen refuses and says why. An administrator who tries to connect gets a button that opens the Connectors page; everyone else is told to ask their administrator. ## 3. How it fits together **The person's own access.** An assistant can see and do only what the person who connected it can see and do in OneMango. A manager's assistant can approve their team's requests; an employee's cannot. Apps that are turned off for your organization, or hidden from that person, are off for the assistant too. **Changes need the person's approval.** Anything that changes data (approving a request, completing a task, sending a reminder) first shows a preview of exactly what will happen. It runs only after the person approves, and an approval that isn't used within 5 minutes expires. Where the assistant supports it, the preview appears as a card with Approve and Cancel buttons. Messages sent to other people can't be recalled, and the preview says so. **One switch for everyone.** Turning **Let people connect AI assistants** off stops every connected assistant straight away, including ones already connected, until it is turned back on. Nobody has to reconnect when it comes back on. **Every call is recorded.** Each action an assistant takes is logged against the person it acted for. The most recent calls appear under **Recent API activity** on the Connectors page. **Changes say which assistant made them.** A change an assistant makes shows the person it acted for and the assistant, for example "Ana Ruiz via Claude", on the record's history and in Admin → Audit logs. Changes made with OneMango's own Ask AI read "via Ask AI". **Slackbot and Copilot need two approvals.** Your Slack or Microsoft 365 admin decides whether the OneMango app or agent is available in their product at all, and this page decides whether OneMango accepts it. Both have to say yes. ## 4. Running it **See who is connected.** The Connectors page lists each assistant, the people who authorized it, the access they granted, and when it was last used. **Limit an assistant to some apps.** Under an assistant's row, open **Limit which apps … can access** and tick the apps it may use. Leave everything unticked to allow every app that is turned on. Platform help and search stay available either way, and search covers every app the person can open. Playbooks, Governance and Company Profile appear in the list marked **all apps**: an assistant limited to some apps has them only when they are ticked, and once ticked they act in every app the person can open. **Revoke an assistant.** **Revoke** signs everyone out of that assistant immediately. People can connect again later if connectors are still on. **Each person sees their own.** Anyone can open **My Profile → Connected assistants** (on the phone: **Me → Connected assistants**) to see the assistants they signed in to, what each may do, their recent activity, any personal API tokens and their Office add-in sign-ins, and **Disconnect** one. Disconnecting stops that assistant acting for them straight away; it does not affect anyone else. **Sign out** on an Office add-in sign-in ends it on that computer, as the add-in's own Sign out does. To connect an assistant, add MangoApps Workforce in the assistant and sign in with your OneMango account. **Automations and integrations.** An assistant always acts as a person. For a script, a scheduled job or another system acting on its own behalf, use a service account instead (**Admin → Security → Service Accounts**). ## 5. Settings **Let people connect AI assistants** (default: off). Controls whether any AI assistant can connect to your organization. **Limit which apps … can access** (default: every app that is turned on). Set per connected assistant. ## 6. More help - *Slack*: OneMango notifications and `/mango` commands in Slack. - *Microsoft Teams*: OneMango notifications, approvals and `/mango` commands in Teams. - *Service Accounts*: access for systems rather than people. **Keywords:** AI assistants, connectors, Claude, Claude connector, ChatGPT, ChatGPT app, Codex, Slackbot, Microsoft 365 Copilot, Copilot agent, MCP, Model Context Protocol, connect Claude to MangoApps, turn off AI access, revoke AI assistant, AI assistant permissions, let people connect AI assistants --- # AI Consoles **Category:** System-features **Section:** Advanced Features **Updated:** 2026-10-08 The per-solution control surface where admins monitor what the AI handled, approve pending actions, and set the autonomy dial for each AI-First Solution. # AI Consoles ## 1. What it is AI Consoles is the per-solution control surface where admins monitor autonomous AI activity, approve or reject pending actions, and set how independently each AI-First Solution can act. Every registered solution domain gets its own console showing a hero metric, what the AI handled, a success rate and, where the solution holds actions for approval, an approval queue. - **Enablement:** AI Consoles is a platform feature, not a licensed app. It is available to any admin whose tenant has at least one AI-First Solution registered. No separate licence or toggle is required. - **What it is not:** AI Consoles is not the same as **AI Operations** (Admin → AI Operations). AI Operations contains the global kill switches (pause/resume all), agent health monitoring, and trust-level configuration. AI Consoles is the per-solution operational surface where you see what a specific solution did and approve its queued work. ## 2. Standing it up There is no separate setup for AI Consoles — the consoles appear automatically as soon as a solution domain is registered. 1. Enable the app whose AI-First Solution you want to manage (e.g. Shifts Scheduling, Service Desk, Inspections) from **Admin → Apps → All Apps**. 2. Navigate to the console via either path: - **Admin → AI Operations → AI Consoles tab** — the portfolio index showing every solution whose app your tenant has. - **Inside any app → AI Console sidebar tab** — the in-app console for that specific solution, with the full app sidebar intact. 3. Set the **AI mode** using the autonomy dial (see §3 below). Most solutions start on **Off** and do nothing on their own until you move the dial. Two start elsewhere: **AI Front Office** starts on **Auto** and **Mango GTM** on **Approve**. The AI Console sidebar tab appears automatically in every app that owns a registered solution. It is visible only to users who pass the console's permission gate (platform admins, plus the app's own admin predicate where one is registered). Individual apps can hide the sidebar link via a **Show AI Console in the sidebar** toggle in their settings. ## 3. How it fits together **Autonomy dial** — The three-position control that governs how independently a solution's AI can act. Each solution has its own dial; the setting is stored with that app's own configuration, and it also sets the agent's trust level. | Mode | Label in the UI | What happens | |---|---|---| | Off | Off — manual only | The agent will not act unattended. No autonomous actions are created. | | Approval | Approve — AI acts, human confirms | The agent proposes actions but every one enters the "AI actions to approve" list for a human to approve or reject before it executes. | | Auto | Auto — AI acts when confident | The agent acts on its own when its confidence meets the threshold. Only critical actions still require human approval. | Changing the dial from Off to Approval sets the agent's trust level to **Probation**; changing it to Auto sets trust to **Trusted**. The underlying trust ladder (**Probation** → **Standard** → **Trusted**) can still self-graduate under Auto mode via earned trust. **Hero metric** — Each solution provides a single headline number specific to its domain (e.g. shifts auto-filled, tickets resolved, onboarding plans progressed). Each solution supplies and computes its own metric. A 30-day sparkline trend appears once at least two daily snapshots have accumulated. **Approval queue** — The "AI actions to approve" card, listing every AI action in this domain that is still waiting for a decision. Approving executes the action; rejecting requires a reason. The queue is visible only to users who hold the approver right — platform admins plus the domain's registered approver predicate (e.g. Service Desk front-line agents can approve actions on tickets they already own). Mango CS and Mango GTM have no approval card: Mango CS holds nothing for approval, and Mango GTM shows a **To review** card linking to its drafted outreach while any are waiting. **Activity feed** — A unified "What the AI handled" list combining autonomous actions with trigger-fired playbook runs for the domain, capped at the 15 most recent. Completed items show a "Done by AI" badge; failed items show "AI couldn't complete". **Two hosting modes** — Every console can render in two places. The **app-native** console at `/apps//ai-console` keeps the app's full sidebar; the **generic** console at `/ai-console/` renders outside any app context. Every registered domain has an app-native console. The generic URL redirects to the app-native one (302) so bookmarks and links land on the in-app surface. **Default landing redirect** — When an admin sets a solution to Auto mode, the app's primary list view (e.g. the shift list, ticket queue) automatically redirects that admin to the console instead. Non-admin users always see the classic list view. Appending `?view=list` to the URL bypasses the redirect. ## 4. Running it ### Reviewing AI activity 1. Open the console for the solution (sidebar tab or **AI Operations → AI Consoles**). 2. The header shows how many actions the AI handled today and the 7-day success rate. 3. Expand or collapse the "What the AI handled" feed to review recent completed and failed actions. ### Approving or rejecting pending actions 1. Open the solution's console. The "AI actions to approve" card lists pending actions. 2. Click **Approve** to execute the action, optionally adding notes. 3. Click **Reject** — a reason is required. The action is marked rejected and will not execute. 4. If the queue has more than 15 items, expand the "View all" disclosure to see the rest. Pending-approval digests are emailed to admins with a direct link to the console. ### Changing the AI mode 1. On the app-native console, locate the **AI mode** dropdown. For Scheduling (Automation page), Onboarding (Settings → Automation) and AI Front Office (Settings) the same dropdown is on the app's settings page; Service Desk sets it in Settings → AI with the **Let AI work tickets on its own** switch and its **Propose only** / **Act on its own** choice. 2. Select Off, Approve, or Auto. 3. Click **Save**. The change takes effect immediately. On consoles where the dial lives on a separate settings page, the console shows a read-only badge with a "Manage in Settings" link. ### Using the portfolio index Navigate to **Admin → AI Operations → AI Consoles** to see every registered solution in a card grid. Each card shows the solution name, hero metric, and a pending-approval count badge. Click any card to open that solution's console. ## 5. Settings AI Consoles itself has no dedicated settings page. The settings that affect console behaviour live on each solution's app configuration: | Setting | Where | Default | What it changes | |---|---|---|---| | AI mode (autonomy dial) | Each solution's console or settings page | Off (AI Front Office: Auto; Mango GTM: Approve) | Controls whether the AI acts autonomously and whether actions need approval | | Confidence threshold | Autonomy dial (submitted with mode change) | 95 | The minimum confidence score (0–100) an AI action must reach to execute without approval in Auto mode | | Show AI Console in the sidebar | Per-app settings (where the app declares it) | On | Hides or shows the AI Console tab in the app's sidebar for eligible admins | ## 6. More help - **AI Operations — Pausing, Approvals & Agent Health** — the global kill switches, trust levels, and agent health monitoring - **AI Operations FAQ** — specific questions about pausing, trust graduation, and error thresholds - **Background Tasks & Job Monitoring** — progress tracking for imports, exports, and bulk operations - Ask AI — the assistant answers questions about AI Consoles from these articles. **Keywords:** ai console, ai consoles, solution console, autonomy dial, ai mode, approve ai action, reject ai action, pending approval, hero metric, ai handled, ai off, ai auto, ai approval mode, ai actions to approve, autopilot, ai shift manager, ai recruiter, ai receptionist --- # AI Front Office App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run AI Front Office — the AI receptionist, online booking, dispatcher queue, and win-back campaigns for service businesses. # AI Front Office ## 1. What it is AI Front Office handles inbound customer communication for service businesses — a homeowner texting about a plumbing leak, a caller booking a salon appointment, a website visitor requesting an estimate. The AI receptionist qualifies the request, captures a booking, and hands it to your dispatcher or operations team. - **Enablement:** AI Front Office is a pay-as-you-go app, available to every tenant with no license decision. Usage is billed per front desk. An admin enables channels and safety modes from **Apps → AI Front Office → Settings**. - **What it is not:** AI Front Office is the B2C front desk for your customers. It is not Mango GTM, which handles B2B sales and marketing for your own pipeline. ## 2. Standing it up 1. Go to **Apps → AI Front Office → Settings**. 2. **Set your business hours.** The receptionist uses these to decide when to handle calls itself versus defer to humans. The default is Monday–Friday 8 AM–6 PM Pacific, Saturday–Sunday closed. Choose your timezone and adjust each day's open and close times. 3. **Review the safety toggles.** Three are on by default: - **After-Hours Only** — the AI only handles inbound during after-hours; humans handle business hours. - **Shadow Mode** — the AI runs end-to-end but its bookings are saved as Shadow: kept out of the pending-review queue and every dispatcher alert, and listed under **Shadow** in the queue's **Status** filter. The receptionist tells the visitor their request is recorded instead of promising a call, and gives your contact details (the **Customer contact** card in Settings) so they can confirm a time. - **Dispatcher Approves All Bookings** — once Shadow Mode is off, every booking enters the dispatcher queue for review regardless of the AI's confidence. 4. **Enable at least one channel.** Web Chat is the lowest-risk starting point. SMS requires a Twilio number entered as the SMS number in the **Phone numbers — voice & SMS** card of Settings. Voice requires a Vapi assistant and a Twilio phone number binding (enter the IDs in the same card). 5. **Turn on the AI Receptionist master switch** (Enable AI Receptionist). Without it, no channel processes inbound messages. 6. **Confirm it worked.** Open the **Playground** tab and send a test message. The Playground uses the same AI agent and tools as production but does not create real bookings or page dispatchers. If Field Service Suite is not enabled, the Settings page warns you. The receptionist's lookup tools depend on Field Service data (customers, service areas, availability), and approved bookings convert to Field Service work orders. ## 3. How it fits together **Conversations and booking requests** — An inbound message (chat, SMS, or voice) creates a conversation. As the AI qualifies the customer's need, it may create a booking request — a structured intent before a work order exists. A conversation can end without a booking (the caller just had a question, or the AI answered from the knowledge base). A booking request can also arrive without a conversation, through the online booking widget or the lead webhook. Example: a homeowner texts "my water heater is leaking." The AI opens a conversation on the SMS channel, asks for the address and urgency, and creates a booking request with urgency **Emergency** and service type **Water heater**. The booking enters the dispatcher queue as **Pending review**. **Booking lifecycle** — A booking request moves through: Pending review → Dispatcher approved (or Auto-approved) → Converted (a Field Service work order or ServiceTitan job is created). Dispatchers can also decline with a reason. Shadow-mode bookings are kept out of the pending-review queue and every dispatcher alert (they are listed under the queue's **Shadow** filter) and are excluded from analytics. **Channels** — Four inbound channels, each independently toggled: - **Web Chat** — public widget on your booking subdomain. - **Inbound SMS** — routes to the AI receptionist via Twilio. - **Voice (phone)** — inbound calls via Vapi and Twilio. - **Web Voice (browser mic)** — visitors tap "Talk now" on the chat widget for a browser-mic conversation. **Dispatcher routing rules** — Rules that auto-assign incoming booking requests to specific dispatchers based on service type, ZIP code, and urgency. Rules are evaluated highest priority first; the first match wins. Empty fields on a rule act as wildcards. **Safety modes** — Three graduated controls for rollout: - **After-Hours Only** keeps humans in the loop during business hours and lets the AI handle after-hours intake. - **Shadow Mode** lets the AI run fully while keeping its bookings out of the review queue and every dispatcher alert — useful for evaluating quality before going live. Read them under the queue's **Shadow** filter, and the conversations behind them under **Shadow captures** on the Conversations page. Escalations still reach a dispatcher. - **Dispatcher Approves All** requires a human to approve every booking before it converts to a work order. Turn these off one at a time as you build confidence in the AI's responses. **Autonomy dial** — AI Front Office also participates in the platform-wide AI autonomy setting (the same Off / Approve / Auto dial used across AI solutions; it is the **AI mode** card at the top of Settings). A tenant that has never touched the dial keeps full autonomy by default. Dialing it down to Approve or Off means it takes no bookings of its own: inbound chats and texts are handed to a dispatcher, and on a phone call it can only pass the caller to a person. On Approve, the outbound calls, follow-up texts and win-back it would send wait on the AI Console under "AI actions to approve" for a person to confirm; on Off it sends none. ## 4. Running it ### Reviewing the dispatcher queue 1. Go to **Apps → AI Front Office → Booking Requests**. 2. The default view shows **Pending review** bookings, sorted by urgency (emergency first). Switch the sort to **Newest** or **SLA at risk** using the dropdown. The **Status** filter lists the rest: Awaiting first contact, Auto approved, Dispatcher approved, Converted, Declined, Expired, Shadow, and All. 3. Open a booking to see the full conversation transcript, activity log, SLA status, similar prior bookings, and any outbound call attempts. 4. Click **Approve** to create a Field Service work order (or push to ServiceTitan if that integration is enabled). Click **Decline** and select a reason. If you have reached the customer but are not ready to decide, click **Mark contacted**: it records first contact and clears the booking's Speed-to-Lead alerts, and the booking stays in the queue until it is approved or declined. 5. Dispatchers can also create bookings manually via **New booking request** for walk-ins, phone calls, or leads that arrived outside the AI channels. Bulk decline is available from the list view — select bookings, choose a decline reason, and submit. Bulk actions are capped at 100 records per submit. ### Reviewing conversations Go to **Apps → AI Front Office → Conversations** to see every intake conversation. Each row shows the channel, state, visitor info, and whether a booking was created. Open a conversation to read the full transcript, see the escalation reason (if any), and view linked scorecards. Once you have dealt with a conversation the AI handed to a person, click **Mark handled**: it stops counting as waiting and every dispatcher's alert for it clears. It is marked booked if a real booking exists for it; otherwise it is closed, and a closed chat or text thread reopens when the customer writes again. ### Monitoring Speed-to-Lead When **Speed-to-Lead SLA** is enabled, the system tracks time from booking creation to first dispatcher contact. The default SLA window is 5 minutes. A warning fires at 25% remaining; a breach fires at 100%. Notifications go to the assigned dispatcher or, if none is assigned, to users in the configured dispatcher roles. By default, the SLA clock pauses outside business hours (an after-hours booking deadlines shortly after next open). Turn off **Speed-to-Lead follows business hours** for 24/7 wall-clock SLA. ### Using Call Coach When **Call Coach (AI scoring)** is enabled, the AI scores each phone call the receptionist answers on five fixed axes — greeting, diagnosis quality, booking attempt, objection handling, and escalation appropriateness — and flags a missed booking opportunity. Chats and texts are not scored automatically: a manager scores them (open a conversation and click **Add manager score**). A manager scorecard starts from the active rubric's criteria, or from greeting, diagnosis, booking attempt, and objection handling when no rubric is active. Admins author rubrics from **Call Coach → More actions (⋮) → Manage rubrics**; only one rubric per business can be active at a time. Rubrics set the criteria managers score against — they don't change how the AI scores, and rubric weights are not applied to any score yet. Scorecards are created by the AI or by a manager, with an overall score from 0 to 100. ### Managing Win-Back campaigns When **B2C Win-Back Campaigns** is enabled, the Win-Back tab appears. Campaigns target dormant customers, declined estimates, abandoned intakes, overdue maintenance, or unscheduled recurring service. Each campaign sends outreach via SMS, email, or voice. Enrollments follow strict TCPA consent handling — no message is sent until consent is captured, and every send checks the platform suppression list. Campaign statuses are draft, active, paused, completed, or archived. ### Using the Knowledge Base When **Knowledge Base** is enabled, admins can author FAQ articles, upload documents (PDF, DOCX, TXT — up to 50 MB), and upload videos (up to 500 MB, auto-transcribed). The AI receptionist searches these entries before escalating to a dispatcher, so it can answer questions like "do you service this brand?" or "what's the warranty?" without human help. ## 5. Settings All settings are at **Apps → AI Front Office → Settings** unless noted otherwise. | Setting | Default | What it changes | |---|---|---| | AI mode | Auto | The Off / Approve / Auto dial in the card at the top of Settings, saved with that card's own Save button. Below Auto the receptionist takes no bookings of its own: chats and texts go to a dispatcher, and on a call it can only pass the caller to a person. On Approve its outbound calls, follow-up texts and win-back wait on the AI Console under "AI actions to approve". | | Enable AI Receptionist | Off | Master switch for the AI receptionist across all channels. Nothing processes without it. | | Web Chat Channel | Off | Enables the public web chat widget on your booking subdomain. | | Inbound SMS Channel | Off | Routes inbound SMS to the AI receptionist. Requires a Twilio SMS number in the **Phone numbers — voice & SMS** card. | | Voice Channel (phone) | Off | Inbound phone calls via Vapi and Twilio. Requires the phone-number binding in the **Phone numbers — voice & SMS** card. | | Web Voice (browser mic) | Off | Visitors can start a browser-mic conversation from the chat widget. Requires a web channel binding. | | After-Hours Only | On | AI receptionist only handles inbound during after-hours; humans handle business hours. | | Shadow Mode | On | AI runs end-to-end, but its bookings are kept out of the review queue and every dispatcher alert (listed under the queue's Shadow filter), and the receptionist tells the visitor their request is recorded. | | Dispatcher Approves All Bookings | On | Once Shadow Mode is off, every booking enters the queue for review regardless of AI confidence. | | Speed-to-Lead SLA | Off | Tracks time-to-first-contact and alerts dispatchers when the SLA is at risk. | | Speed-to-Lead SLA (minutes) | 5 | The SLA window in minutes. Warning at 25% remaining, breach at 100%. | | Speed-to-Lead follows business hours | On | SLA clock pauses outside business hours. Turn off for 24/7 operations. | | Speed-to-Lead AI first touch | Off | When no human contacts the lead by the warning threshold, the AI sends the first-touch SMS or call itself. | | Online Booking Widget | Off | Public booking form on your tenant subdomain (no AI conversation required). | | B2C Win-Back Campaigns | Off | SMS, email, or voice outreach to dormant customers, declined estimates, and more. | | Call Coach (AI scoring) | Off | The AI scores each phone call on greeting, diagnosis quality, booking attempt, objection handling, and escalation appropriateness; managers score chats and texts against your rubric. | | Knowledge Base | Off | Gives the AI receptionist a tool to search your authored FAQ and document content before escalating. | | Bilingual (English + Spanish) | Off | The receptionist detects the caller's language and replies in kind. When off, it stays in English. | | Urgent booking mobile push | On | Push notification to dispatchers when an emergency or same-day booking lands. Skipped for shadow bookings. | | Escalation alerts | On | Alert dispatchers the moment the AI escalates a conversation to a human. | | Sentiment-based escalation | On | Escalates to a dispatcher when the visitor shows sustained frustration. | | Negative streak for escalation | 2 | Consecutive negative visitor turns before sentiment escalation fires. | | Owner daily digest | Off | Daily email to admins summarizing what the AI answered, booked, and escalated the previous day. Skips quiet days. | | Capacity-aware booking | Off | Availability windows and auto-booking respect the day's committed job load vs. the daily capacity ceiling. No effect for ServiceTitan-sync tenants. | | Daily job capacity | 12 | Ceiling for capacity-aware booking (jobs per day). | | Outbound voice | Off | Master switch for AI-placed outbound calls (win-back voice, decline follow-up, abandonment recovery). | | Outbound — decline follow-up | Off | Schedule a follow-up call when a booking is declined because the customer declined the estimate. | | Outbound — abandonment recovery | Off | Schedule a recovery call when a chat or SMS conversation is abandoned and a phone number is on file. | | Missed-call text-back | Off | SMS the caller when an inbound call ends unanswered, so the lead isn't lost (needs the Twilio number's call-status callback — ask MangoApps support). | | Booking confirmation SMS | Off | SMS the customer when their booking is approved, declined, or expires unreviewed. | | Post-job happy text | Off | Thank-you SMS to the customer when their work order completes. Adds a review ask when a review link is configured. | | ServiceTitan sync | Off | Push approved bookings to ServiceTitan as jobs instead of creating Field Service work orders. Requires an active ServiceTitan integration. | | Allowed Roles | Manager, Admin, Super Admin | Roles that can access AI Front Office (review queue, conversations, outcome events, Playground). Set in the **Role access** card. | | Administrative Roles | Admin, Super Admin | Roles that can configure AI Front Office (settings, routing rules, win-back, call coach). Set in the **Role access** card. | ## 6. More help - **AI Front Office FAQ** — specific setup, operating, and troubleshooting questions. - Ask AI — the assistant answers questions about AI Front Office from these articles. **Keywords:** ai front office, ai receptionist, online booking, dispatcher, booking request, speed to lead, win-back, call coach, after hours, shadow mode, customer intake, twilio, voice channel, sms channel, web chat, ai-front-office, ai_front_office --- # AI Front Office FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-20 Answers to common setup and operating questions about AI Front Office — for the admin running it. # AI Front Office FAQ Answers to common setup and operating questions about AI Front Office. For what the app is and how to set it up from scratch, see the [AI Front Office Overview](/help/articles/ai_front_office_app_overview). --- ## Setup ## What do I need to turn on before the AI receptionist will answer? Two things: the master **Enable AI Receptionist** switch and at least one channel — **Web Chat Channel**, **Inbound SMS Channel**, or **Voice Channel (phone)**. Both are off by default. Turn them on at **Apps → AI Front Office → Settings**. If you enable only the master switch but no channel, the receptionist has nowhere to listen and nothing happens. The **AI mode** card at the top of Settings must also be on **Auto**, which it is unless someone changed it; on Approve or Off, chats and texts go straight to a dispatcher. ## What is shadow mode, and should I leave it on at first? Shadow mode is on by default. The AI receptionist runs end-to-end and logs every conversation, but the booking requests it creates are saved as Shadow: kept out of the pending-review queue and every dispatcher alert, and listed under **Shadow** in the queue's **Status** filter. The receptionist tells the visitor their request is recorded rather than promising a call, and gives your contact details (the **Customer contact** card in Settings) so they can confirm a time. Escalations still reach a dispatcher. Leave it on during your first few days so you can read transcripts and evaluate answer quality before any real bookings reach your team. ## What is after-hours-only mode? After-hours-only mode is on by default. When it is on, the AI receptionist only handles inbound contacts outside your configured business hours. During business hours, it immediately routes the visitor to a dispatcher so your human staff stays in the loop. Default business hours are Monday–Friday 8 AM–6 PM Pacific, Saturday and Sunday closed. Set your own hours at **Settings → Business Hours**. ## What does "Dispatcher Approves All Bookings" mean? It is on by default. Once Shadow mode is off, every booking request the AI creates enters the queue in **Pending review** regardless of its confidence score. When you turn **Dispatcher Approves All Bookings** off, high-confidence bookings that also pass the geocode-confidence floor and service-area check can be auto-approved without dispatcher review — but only if the receptionist's autonomy dial (the **AI mode** card at the top of Settings) is set to **Auto**. --- ## Permissions and access ## Who can see the dispatcher queue, and who can change settings? Two role lists control access, both set in the **Role access** card in Settings: - **Allowed Roles** (default: Manager, Admin, Super Admin) — can view booking requests, conversations, outcome events, and the Playground. - **Administrative Roles** (default: Admin, Super Admin) — can open Settings, Win-Back, Call Coach, Knowledge Base, Routing Rules, and Analytics. Platform admins and app admins always have full access regardless of these lists. --- ## Day-to-day ## How does a booking request get routed to a specific dispatcher? Routing rules match on three dimensions — **service type**, **zip code**, and **urgency** — evaluated in priority order (highest priority first). The first rule that matches assigns the booking to that rule's dispatcher. An empty field on a rule acts as a wildcard. If no rule matches, the booking stays unassigned and the entire dispatcher team sees it. ## What are the Speed-to-Lead warning and breach thresholds? The default SLA window is **5 minutes** (set **Speed-to-Lead (minutes)** in the **Thresholds** card of Settings). A warning fires when **25 % of the window remains** (75 % elapsed). A breach fires when the window is fully expired. By default, the SLA clock pauses outside business hours. Turn **Speed-to-Lead follows business hours** off for a 24/7 wall-clock SLA. ## How does the AI first-touch backstop work? When **Speed-to-Lead AI first touch** is enabled and no human has made first contact by the SLA warning threshold, the AI sends the first touch itself. The default channel is **SMS**; you can switch it to **Voice** if outbound voice is also enabled. SMS marks the SLA as met. A voice call is scheduled but still subject to quiet-hours and rate-limit checks at dial time. ## How do I embed the chat widget on my own website? Go to **Settings → Embed Widget**, generate an embed key, and paste the provided ` **Keywords:** faq, ai front office, ai receptionist, shadow mode, after hours, speed to lead, dispatcher, booking request, win-back, call coach, embed widget, topic gate, TCPA, voice channel, not answering, booking disappeared, ai-front-office, ai_front_office --- # AI Notepad App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-20 How to set up and run AI Notepad — upload recordings or write notes and get AI-generated transcripts, summaries, and action items. # AI Notepad ## 1. What it is AI Notepad turns meeting recordings, typed notes, PDFs, and web pages into searchable transcripts, summaries, and action items. Users upload a file or write notes; the AI produces a summary, extracts action items with owners and due dates, and surfaces key decisions and themes. Everything is searchable across all of a user's meetings and notes. - **Enablement:** AI Notepad requires a license. An admin enables it from Admin → Apps → All Apps, then configures it from **Settings** inside the app. - **What it is not:** AI Notepad does not schedule or host meetings. Most content arrives after the meeting — an uploaded recording, a Zoom cloud recording, a PDF, a web page, or pasted text. People can also record on a phone. Recording a call live in the OneMango desktop app is off until an admin turns on **Desktop capture** in Settings; those captures are transcribed in the cloud unless the admin chooses to keep desktop transcription on the computer. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **AI Notepad**. 2. Open the app and go to **Settings** (visible to admins and app admins). 3. Confirm **AI processing & Ask AI agent** is on (it is by default). It is the master switch: while it is off, uploads are stored but never transcribed or summarized, and the AI Notepad agent is removed from Ask AI. 4. If your organization uses Zoom, connect a Zoom integration at **Admin → Organization → Integrations** first, then return to **AI Notepad → Settings** to add a Zoom account. The account cannot be added until the integration exists — the form is disabled and an admin hint appears. 5. Optionally set a **Default Note Template**. It is applied to a new typed note started on the web when the person picks no template and has not set a default of their own. Built-in templates ship with the app: 1:1 Meeting, Team Standup, Retrospective, All-Hands, Sales Call, General Notes, and five for customer calls (Customer Check-in, Quarterly Business Review, Customer Escalation, Renewal & Risk Review, Customer Onboarding Kickoff). Admins and users can also create custom templates. 6. Review the remaining settings. Most features are on by default. These are off by default: **Daily accountability digest**, **Calendar meeting stubs**, **Auto-file notes into notebooks**, **Editors can pass a note on**, and **Desktop capture**. Turn them on if your organization wants them. 7. To verify the setup works: start a note with **New note** (the pen button above the list), type a few sentences, then open the note's **⋯** menu and choose **Convert to meeting note**. A summary and action items should appear within a minute. **Silent-dependency warning:** The **Automations** feature (rules that run after processing to create tasks, email the summary to attendees, or assign a Practice Hub scenario) requires the **Automations** toggle to be on in Settings. It is on by default, but if it was turned off, automations will not fire even if individual automation rules are marked active. ## 3. How it fits together **Meetings vs Notes** — AI Notepad has two creation paths that produce the same record type. A *meeting* starts from something to process — a recording, a PDF, a web page, or a pasted transcript — and goes through AI processing automatically unless an admin turned off **Auto-Process Uploads**. A *note* starts as a blank or template-based writing surface. The user writes first; when they want AI on it, they choose **Convert to meeting note** from the note's **⋯** menu (on a phone, **Analyze with AI**) to get a summary, action items, and insights from what they wrote. Both appear in the same list and open on the same page. The list's chips show **All**, **Meetings**, **Notes**, **Shared**, or **Deleted** (Recently Deleted). **Sources** — A meeting can start from an uploaded audio or video file, a Zoom cloud recording import, a PDF, a web page (URL), or pasted text. Zoom is the only provider recordings can be imported from; for Microsoft Teams or Google Meet, upload the recording file. PDFs, web pages, and pasted text are read directly rather than transcribed. VTT and SRT subtitle files are also accepted and treated as already-transcribed text. **Processing** — While a recording or document is being worked on, it shows **Pending** and then **Processing**; a finished note shows no status. If processing fails, the note shows **Failed** with the reason. A note that is still processing after a size-aware window (5 minutes, longer for large files, at most 60 minutes) shows **Stuck**. A failed or stuck note offers **Retry processing**. When **Auto-Process Uploads** is off, a new recording or document shows **Not started** until someone presses **Start processing** on it. **Notebooks** — A notebook groups related meetings and notes into a collection. Users create notebooks, give them a title and optional description, then add completed meetings to them. A notebook unlocks cross-meeting features: - **Meeting Comparison** finds decision drift, theme evolution, and conflicts across two or more selected meetings in the notebook. - **Artifacts** are AI-generated documents drawn from all completed meetings in the notebook: Decision Log, Open Issues Tracker, Glossary, Key Questions, and Action Items Rollup. Example: a notebook called "Q3 Product Reviews" containing four weekly review meetings lets a manager generate a single Decision Log spanning all four and compare how priorities shifted week to week. **Action items and My Items** — When the AI processes a meeting or note, it extracts action items with owners, due dates, and a commitment type (hard, soft, decision, or FYI). These appear on the meeting's detail page and also roll up into **My Items**, a personal view filtered to items assigned to the current user. My Items sorts pending items by urgency: overdue first, then due today, then due this week, then items with no due date. Items can be marked complete from either place. When a user is assigned an action item, they receive a notification. Action items can also be converted into Tasks app tasks from the meeting page. **Decisions** — The AI extracts decisions from meeting content and stores them as part of the meeting's insights. The **Decisions** tab (within My Items) provides a cross-meeting log of all decisions the current user can see, searchable by keyword. **Sharing and permissions** — The person who creates a note owns it. From the **Share** dialog they can share a note or a notebook with named teammates as **Viewer** (can read it) or **Editor** (can change it). Sharing a notebook reaches every note in it — an Editor on a notebook can also edit the notes inside. The owner can always manage sharing; Editors can too only when an admin turns on **Editors can pass a note on** in Settings (off by default). The person who created a note can delete it; it goes to **Recently Deleted**, where it can be restored for 30 days. The whole sharing feature can be turned off from Settings — people already shared with keep their access. **Chat** — Each processed meeting has a per-meeting chat where users ask questions about its content. There is also a cross-meeting chat (the **Chat** tab) that searches across all of the user's meetings. Chat can be scoped to a single meeting, a notebook, a set of selected meetings, all meetings, or a date range. Answers include citations back to the source transcript or note. The chat feature is controlled by the **Meeting Chat** toggle in Settings. **Content versioning** — Edits to a meeting's summary, action items, or insights are versioned. Each edit saves the previous state as a numbered version. Users can view the version history and restore a prior version. **Content revision** — Users can ask the AI to rewrite, expand, refine, or simplify an AI-generated section (summary, action items, or insights) without reprocessing the entire meeting. This is controlled by the **Content Revision** toggle. **Output formats** — A completed meeting can generate six additional AI views: FAQ, Timeline, Briefing Document, Key Themes, Compare (against other meetings), and Follow-up Email. Each is generated on demand from the meeting's detail page. ## 4. Running it ### Uploading a recording 1. In **Meetings & Notes**, open the arrow beside **New note** and choose **Upload a recording**. 2. Select an audio or video file and, optionally, give it a title. 3. If **Auto-Process Uploads** is on (the default), processing starts right away and the meeting shows **Pending**, then **Processing**. If it is off, the upload waits until someone opens it and chooses **Start processing**. 4. When finished, the user receives a notification: "Your meeting notes are ready." Supported file formats: MP3, MP4, WAV, M4A, WebM, OGG, QuickTime video, PDF, plain text, Markdown, VTT, and SRT. ### Importing Zoom recordings 1. An admin connects a Zoom integration at **Admin → Organization → Integrations**. 2. In **AI Notepad → Settings**, add a Zoom account under the meeting provider section. 3. Go to **Manage → Import Recordings** (shown to people allowed to import recordings once a Zoom account is connected), select a date range, and import recordings. Each import creates a meeting and queues it for processing. Already-imported recordings are marked so they cannot be imported twice. ### Writing a note and analyzing it with AI 1. Click **New note** (the pen button above the list). It starts from your default template if one is set; the arrow beside it lists the templates and the import options. The built-in templates cover 1:1s, standups, retrospectives, all-hands, sales calls, customer calls, and general notes. 2. Write freely. Notes auto-save. 3. When you want AI on it, open the note's **⋯** menu and choose **Convert to meeting note** (on a phone, **Analyze with AI**). Your text is kept as written and becomes the material for a summary, action items, and insights. 4. Once a note has AI output, **Enhance with AI** re-runs parts of it (summary, action items, decisions, open questions, timeline), and **Reshape the AI notes** reorganizes the AI notes around a template. ### Managing automations App admins create post-processing automations at **Manage → Automations**; an admin can let others create them under **Settings → Who Can Do What**. An automation fires when a meeting finishes processing and can perform one or more actions: - **Create tasks** from the action items - **Email the summary** to the meeting's attendees who can already open the note - **Assign a Practice Hub scenario** to the meeting owner (when Practice Hub is available) Conditions can narrow the trigger to a specific source type, template, or notebook. ### Viewing analytics Managers and app admins see an **Analytics** page under **Manage → Analytics** (an admin can change who under **Who Can Do What**) with usage metrics: total meetings, new meetings in the period, notes created, active users, AI summaries generated, and chat queries. The period can be set to 7, 30, or 90 days. Every user also has a personal **Your Recap** page showing their own meeting and note volume, AI usage, and action-item summary. ## 5. Settings All settings are at **AI Notepad → Settings**, accessible to admins and app admins. | Setting | Default | What it changes | |---|---|---| | AI processing & Ask AI agent | On | Master switch for transcription, summarization, every AI feature below, and the AI Notepad agent in Ask AI. When off, uploads are stored but never processed. | | Audio Overview | On | Generates an AI-narrated audio summary of each meeting. | | Meeting Chat | On | Lets users ask AI questions about meeting content. Also controls the Chat tab and cross-meeting chat. | | Output Formats | On | Lets users generate FAQ, Timeline, Briefing, Themes, Compare, and Follow-up Email from a meeting. | | Content Revision | On | Lets users rewrite, expand, refine, or simplify AI-generated sections. | | Meeting Comparison | On | Lets users compare content across meetings within a notebook. | | Knowledge Artifacts | On | Lets users generate notebook artifacts (Decision Log, Open Issues Tracker, Glossary, Key Questions, Action Items Rollup) from every note in a notebook. | | Sharing | On | Lets users share notes and notebooks with teammates. Turning it off stops new shares; people already shared with keep their access. | | Editors can pass a note on | Off | Lets an Editor share a note with others or file it into a notebook. | | Automations | On | Lets the people chosen under Who Can Do What (app admins by default) create post-processing automations. | | Daily accountability digest | Off | Emails each user a daily digest of their pending action items, and tells them in the app when one is overdue or due today. | | Calendar meeting stubs | Off | Pre-creates draft notes for upcoming calendar events. Requires a connected calendar integration. | | Pre-Meeting Prompt | On | Shortly before a calendar meeting starts (5 minutes by default), asks people if they want to join it and start AI Notepad. Each person can change it for themselves. | | Practice Hub recommendations | On | Suggests Practice Hub roleplay scenarios on a meeting's page based on its themes. Requires the Practice Hub app to be enabled. | | Who Can Do What | Varies | Who can record meetings on a phone or in the desktop app (everyone; uploading a file on the web is not limited by it), create note templates (everyone), create automations (app admins), see analytics (managers and above), and import cloud recordings (app admins). | | Auto-Process Uploads | On | Automatically begins AI processing when a recording is uploaded. When off, an upload waits until someone opens it and chooses Start processing. | | Auto-file notes into notebooks | Off | After processing, lets AI file a note that isn't in a notebook into the best-matching one. | | Max Upload Size (MB) | 500 | Maximum file size for audio and video uploads (10–2,000). | | Default Meeting Source | Upload | The source pre-selected when users create a new meeting. | | Default Note Template | (none) | Template applied to a new typed note on the web when the person picks none and has no default of their own. | | Data Retention (days) | 365 | Notes older than this move to Recently Deleted, can be restored there for 30 days, and are then permanently deleted. 0 keeps notes forever. | | Desktop capture | Off | Lets people record meetings and dictate voice notes in the OneMango desktop app. Live captures are transcribed in the cloud unless **Keep desktop transcription on the computer** is ticked. | | Notice when a meeting starts | Off | Starting point for whether the desktop app offers to take notes when someone joins a Zoom, Teams, or Meet call. Two companion settings decide whether it asks first or may start recording on its own (both default to asking first). | | Transcription language | Auto-detect | The language people usually speak, used to transcribe recordings. | | Recording retention (days) | 30 | The recordings of finished notes are deleted after this many days; the transcript, summary, and notes are kept. A recording whose note never finished processing is kept, so it can still be retried. A deleted recording cannot be restored. Each person can choose a shorter or longer period up to the limit an admin sets (1–365). | | Recording consent notice | On | Before their first recording, in the desktop app or on a phone, people must confirm they will let participants know; confirming once counts for both. Only a company admin can change it or its wording. | ## 6. More help - **AI Notepad FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about AI Notepad from these articles. **Keywords:** ai notepad, meeting notes, meeting transcription, meeting summary, action items, audio overview, notebook, meeting recording, note template, meeting chat, decisions, commitments, ai-notepad, ai_notepad --- # AI Notepad FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-20 Answers to common setup and operating questions about AI Notepad — for the admin running it. # AI Notepad FAQ Answers to common setup and operating questions about AI Notepad. For what the app is and how to set it up from scratch, see the [AI Notepad Overview](/help/articles/ai_notepad_app_overview). --- ## Setup ## Do I need to configure anything before my team can use AI Notepad? Enable the app from Admin → Apps → All Apps and confirm the **AI processing & Ask AI agent** toggle is on in AI Notepad Settings. That toggle is on by default, so most tenants can start using the app as soon as it is licensed and enabled. If you plan to import Zoom recordings, you also need to connect a Zoom integration under **Admin > Organization > Integrations** first — AI Notepad Settings will prompt you if one is missing. ## Who can access the Settings page and import recordings? Business admins and AI Notepad app admins can reach Settings. By default, importing Zoom recordings and creating automations are also for admins and app admins, and analytics is for managers and above; an admin can change each of these under **Settings → Who Can Do What**. All other users can create meetings, notes, and templates but cannot change app settings. --- ## Permissions and access ## Who can see a meeting or notebook I created? By default, only you. Meetings and notebooks are visible to their creator and to anyone they have been shared with. Sharing a notebook also grants access to every meeting inside it. The Sharing feature must be enabled in Settings (on by default). ## What sharing permission levels are available? The person who created a note owns it. From the **Share** dialog they give each person **Viewer** (read-only) or **Editor** (can change the content). The owner can always manage sharing and move the note between notebooks; Editors can do so only when an admin turns on **Editors can pass a note on** in AI Notepad Settings (off by default). The person who created a note can delete it — it goes to **Recently Deleted**, where it can be restored for 30 days. Editors cannot delete it. ## My employee says they can't see the Chat tab — what happened? The Chat tab appears only when **Meeting Chat** and **AI processing & Ask AI agent** are both on in Settings. If either is off, no user will see the tab. Inside a note, the Chat tab also waits until the note has finished processing. The same pattern applies to other feature toggles — each one controls whether the corresponding surface is visible to all users. --- ## Day-to-day ## What file types can I upload, and how large can they be? Accepted formats are MP3, MP4, WAV, M4A, WebM, OGG, MOV (audio/video), plus PDF, VTT/SRT captions, and plain text or Markdown. The default maximum upload size is **500 MB**. You can set it anywhere from **10 MB to 2,000 MB** in Settings. ## What happens after someone uploads a recording? If **Auto-Process Uploads** is on (the default), AI processing starts automatically — the meeting shows **Pending**, then **Processing**, and the status disappears when the notes are ready. When processing completes, the owner receives a notification that their notes are ready. If Auto-Process is off, the recording is stored but no AI work begins until someone opens it and chooses **Start processing**. ## How do automations work, and who can create them? By default, admins and app admins create automations; an admin can let others create them under **Settings → Who Can Do What**. An automation fires when processing completes and can **create tasks** (pushes action items into the Tasks app), **email the summary** to the meeting's attendees who can already open the note, and — when Practice Hub is available — **assign a Practice Hub scenario** to the meeting owner. Each automation can be scoped to a specific source type, template, or notebook. ## Can users set a personal default template? Yes. On the Templates page, any user can mark a template as their personal default. That template is automatically applied when they create a new note. Admins can also set a business-wide default template in Settings, which applies when a user has not chosen their own. ## How does cross-meeting chat work? Users can ask AI a question scoped to a single meeting, a notebook, a hand-picked selection of meetings, a date range, or all their accessible meetings. The assistant retrieves relevant passages across the selected scope and answers with citations that link back to the source meeting. --- ## When something looks wrong ## "My recording has been processing for a long time — is it stuck?" Processing time scales with file size. A small recording is typically ready within a few minutes; a 500 MB file can take considerably longer. The system treats a meeting as stuck only after a grace period proportional to the upload size (capped at 60 minutes). Once that threshold passes, the note shows **Stuck** and a **Retry processing** button appears. If processing fails, the note shows **Failed** with the reason and the same **Retry processing** button. If it shows **Not started**, automatic processing is off in Settings: open the note and press **Start processing**. ## "I uploaded a file but nothing happened — no transcript, no summary." Check two things. First, confirm **AI processing & Ask AI agent** is on in Settings. When it is off, uploads are stored but never processed. Second, confirm **Auto-Process Uploads** is on. If it is off, an upload waits until someone opens it and chooses **Start processing**. ## "I assigned an action item to someone but they didn't get a notification." Notifications fire only on a deliberate assignment change — not during the initial AI extraction. When a meeting is first processed, the AI fuzzy-matches speaker names to attendees, but these bulk assignments do not trigger notifications. The assignee is notified only when someone explicitly changes the assignment afterward. Also, assigning an item to yourself does not send a notification. ## "The transcript says Speaker A instead of the person's name." Speakers are told apart only on calls captured by the desktop app with cloud transcription, and Zoom imports keep Zoom's own speaker names. An uploaded recording is transcribed without speaker labels. The desktop capture hears the other side of the call as one stream, so it labels the voices it can separate (Speaker A, Speaker B) without knowing who they are. When the conversation itself shows who someone is (they introduce themselves, or someone thanks them by name) and they are on the meeting's calendar invite, the Transcript tab suggests the name and quotes the words that show it. The user accepts or dismisses each suggestion, or clicks a speaker's label to type a name. After a speaker is named, **Update notes with these names** rewrites the summary and action items with the new names. The transcript itself is not re-run. ## "The daily accountability digest isn't arriving." The **Daily accountability digest** toggle is off by default. Turn it on in Settings. The digest is sent as part of the platform's daily digest job, so it follows the same delivery schedule. Users must have at least one pending action item to receive it. Someone with no email address still gets an in-app notice on any morning an item is overdue or due today. --- ## Licensing and limits ## Does AI Notepad require a licence? Yes. AI Notepad requires a licence and is enabled per-tenant by an administrator. It is not on by default. ## Are there limits I should know about? | Item | Default | Configurable range | |---|---|---| | Maximum upload file size | 500 MB | 10–2,000 MB | | Data retention period | 365 days | 30–3,650 days, or 0 to keep notes forever | | Uploaded recording retention | 30 days | 1–365 days | | Chat message length | 5,000 characters | Not configurable | | Meeting title length | 500 characters | Not configurable | | Notebook title length | 255 characters | Not configurable | | Notebook description length | 2,000 characters | Not configurable | ## How does the data retention policy work? Each night, notes older than the configured retention period move to **Recently Deleted** — transcript, summary, notes, and recording. They can be restored from there for 30 days, then they are permanently deleted. The default is **365 days**; you can set it from **30 to 3,650 days**, or enter **0** to keep notes forever. Adjusting the retention period affects all existing notes, not just future ones. Uploaded recordings have their own, shorter limit (30 days by default, under **Desktop Capture & Transcription** in Settings). When it passes on a note that has finished processing, the recording itself is deleted and cannot be restored; the transcript, summary, and notes are kept. A recording whose note never finished is kept, so it can still be retried. ## Can I connect Zoom, Microsoft Teams, or Google Meet? Zoom is the only connected provider today. You can import Zoom cloud recordings manually from the recording import page, or automatically via webhook when a recording completes. Microsoft Teams and Google Meet import are not yet available — for those providers, upload the recording file directly. --- ## More help - [AI Notepad Overview](/help/articles/ai_notepad_app_overview) - Ask AI — the assistant answers AI Notepad questions from these articles. **Keywords:** faq, ai notepad, meeting notes, transcription, action items, notebooks, retention, sharing, automations, zoom import, audio overview, templates, not processing, upload size, ai-notepad, ai_notepad --- # AI Operations FAQ **Category:** Faq **Section:** Advanced Features **Updated:** 2026-08-12 Answers to common setup and operating questions about AI Operations — pausing agents, approvals, trust levels, limits, and troubleshooting. # AI Operations FAQ Answers to common setup and operating questions about AI Operations. For what it is and how to set it up, see the [AI Operations Overview](/help/articles/ai_operations). --- ## Setup ## Do I need a licence to access AI Operations? No. AI Operations is not a licensed app — it is available to every tenant automatically. Any user with the admin role or above sees it in the admin sidebar. It becomes useful as soon as at least one app with an AI agent domain is enabled. ## I turned on an app's AI agent but nothing is happening — what did I miss? Two switches must be on. The app's own agent toggle enables the agent itself, and **Autonomous Operations** in AI Operations (Admin → AI Operations → Agent Settings) must also be on for that domain. If that switch is off, the agent is technically present but will not propose or execute any actions. --- ## Permissions and access ## Who can approve pending actions? Any user with the manager role or above can approve most pending actions. The exceptions are **Compensation** and **Employee Data** domains — those require admin or above to approve, because approving executes a sensitive write (pay change, employee record edit). ## Can a System Admin pause agents from the Console? Yes. A System Admin can issue a global pause from the Console's Automation Hub. Domains paused this way cannot be resumed by a tenant admin — only the System Admin who paused them can lift the hold. --- ## Day-to-day ## What are the trust levels and how does a domain advance? Every domain starts at **Probation** and can advance through three levels: 1. **Probation** — all actions require approval. Daily cap: 10. Advances after 50 successful actions with a 95% success rate. 2. **Standard** — routine actions auto-execute; high-impact, bulk, and critical actions still require approval. Daily cap: 50. Advances after 200 successful actions with a 98% success rate. 3. **Trusted** — only critical actions require approval. Daily cap: 200. This is the highest level. Advancement is evaluated daily by a background job. You can also set the trust level manually from Agent Settings — a reason is required and recorded in the audit log. ## What counts as a "high-impact" action? An action is classified as high-impact if any of the following are true: it affects more than 5 people, it involves compensation or salary, or it involves termination or offboarding. ## How do I force approval for high-impact actions even at the Trusted level? Turn on **Require approval for high-impact actions** in the domain's Agent Settings panel. When this is on, actions that affect more than 5 people or involve compensation or termination always require approval — regardless of trust level. ## What happens if agents accumulate too many rejections? If a domain gets 3 or more rejected actions within 30 days, every action for that domain is routed to the approval queue regardless of its trust level. This override is additive — it can only add an approval requirement, never remove one. ## How long do pending approvals last before they expire? Pending approvals expire automatically after **14 days**. Three days before expiry, the action's owner and their manager are notified. After expiry, the action is cancelled and tenant admins are notified with the count. If the automation is still needed, you can re-run it. ## Can I retry a failed action? Yes, from the action's detail page (Action History → click the row), use the **Retry** button. Retries are capped at **3 per action**. Sample-data actions cannot be retried. If the action's domain does not have a registered runner, the Retry button will not appear. --- ## When something looks wrong ## "The agent was working yesterday but now it's doing nothing" Check three things in order: 1. **Paused?** Go to Admin → AI Operations → Overview. If the domain card shows a paused status, resume it (or ask your System Admin if it was paused globally from the Console). 2. **Daily limit hit?** Check Action History for today's count. The default cap is 10 at Probation, 50 at Standard, and 200 at Trusted. You can raise it in Agent Settings (max 500). 3. **Auto-paused on error rate?** If the 24-hour error rate exceeds the configured threshold (default 5%), the domain pauses itself automatically. The hourly safety monitor also sends a warning when the error rate reaches 80% of the threshold, and when daily actions reach 90% of the limit. Resume the domain after investigating the errors. The error rate check requires at least 5 actions before it activates, so a single failure will not trigger an auto-pause. ## "I resumed a domain but it says only the System Admin can resume it" That domain was paused globally from the MangoApps Console (system-admin level). Tenant admins cannot lift a console-level pause — contact your System Admin to resume it. ## "An action I approved did not execute" When you approve an action, it executes immediately. If execution fails, the action moves to the **failed** state. Check the action's detail page in Action History for the error. You can retry it (up to 3 times) from there. ## "Trust level isn't advancing even though the agent is doing well" Trust advancement counts only **Completed** and **Failed** actions — not Detected (pending), Pending approval, Approved (awaiting run), Rejected, Preview, or Duplicate skip. A standing approval backlog does not count toward the success rate. Check the domain's stats in Agent Settings to see the current count and success rate against the advancement thresholds. --- ## Limits and ranges ## What are the configurable limits and their allowed ranges? | Setting | Allowed range | Default | |---|---|---| | Max actions per day | 1–500 (0 = unlimited) | Per trust level: 10 / 50 / 200 | | Confidence threshold | 0–100 | 95 | | Pause on error rate (%) | 0–100 (0 = disabled) | 5 | | Notification cooldown | 0–1,440 minutes | — | | Approval workflow levels | 1–10 | — | Per-trust-level overrides for max actions/day, confidence threshold, and error rate can be set in the advanced section of each domain panel. ## How many rows can I export from Action History? The CSV export covers up to **10,000 rows**, ordered newest-first. ## Which apps support trigger-specific approval workflows? Three apps currently support trigger processes: - **Inspections** — inspection submission, template creation, corrective action - **Frontline Execution** — campaign request, campaign publication - **Policy Hub** — policy publication Other apps can have approval workflows, but without trigger-process scoping — the workflow applies to the app generically. --- ## More help - [AI Operations Overview](/help/articles/ai_operations) - **Agent Settings** (Admin → AI Operations → Agent Settings) — per-domain configuration - **Trust & Safety** (Admin → AI Operations → Trust & Safety) — rejection feedback and guardrail configuration - Ask AI — the assistant answers AI Operations questions from these articles. **Keywords:** faq, ai operations, automation hub, pause agent, trust level, pending approvals, daily limit, confidence threshold, error rate, auto-pause, retry failed action, rejection escalation, approval workflow, agent health --- # AI Operations — Pausing, Approvals & Agent Health **Category:** System-features **Section:** Advanced Features **Updated:** 2026-10-16 The admin hub for governing autonomous AI agents — pause and resume domains, review pending actions, monitor agent health, configure trust levels, and manage approval workflows. # AI Operations ## 1. What it is AI Operations is the admin surface for governing every autonomous AI agent in the platform. From here you pause or resume agents by domain, review actions that require human approval, monitor agent health, and configure trust levels that control how much autonomy each agent earns over time. - **Enablement:** AI Operations is available to every tenant automatically — it is not a licensed app. It appears in the admin sidebar for any user with the admin role or above. - **What it is not:** AI Operations is not where you configure what an individual app does — it governs the *safety envelope* around the AI (limits, approvals, pauses). Individual app behaviour is configured in each app's own settings. ## 2. Standing it up AI Operations itself requires no setup — it is live as soon as any autonomous agent domain is enabled for your business. The typical sequence: 1. Enable an app that has an AI agent (e.g. Shifts Scheduling, Time & Attendance, Recruiting). This is done from the app's own settings or Admin → Apps → All Apps. 2. Go to **Admin → AI Operations → Agent Settings**. Each enabled domain appears as an accordion panel. Confirm that **Autonomous operations** is turned on for the domains you want. 3. Every new domain starts at the **Probation** trust level — all actions require your approval before they execute. Check **Admin → AI Operations → Approvals** regularly to process the queue. 4. To verify it is working, go to **Admin → AI Operations → Overview**. You should see domain cards with status indicators and recent activity. **Silent-until-paired:** enabling an app's AI agent in the app's own settings is not enough if **Autonomous Operations** is off for that domain in AI Operations. The agent will be technically enabled but will not execute any actions. Both switches must be on. ## 3. How it fits together ### Autonomous Actions An **autonomous action** is any operation an AI agent proposes or executes — a schedule change, a leave adjustment, an employee data update. Every action is logged with a domain, capability, confidence score, priority, and status. The lifecycle is: **Detected (pending) → Pending approval → Approved (awaiting run) → Completed** (or **Rejected** / **Failed** at any step). Actions that do not require approval move straight from Detected to Completed. The entire stream is visible in **Action History**. ### Domains Each agent operates within a **domain** — a named area tied to a marketplace app. The 15 canonical domains are: Scheduling, Attendance, Leave Management, Timekeeping, Skills & Credentials, Compensation, Employee Data, Service Desk, Training, Onboarding, Performance Management, Procurement, Recruiting, Contracts, and Mango IQ. Pause/resume controls, trust levels, and daily limits are all set per domain. ### Trust levels Every domain starts at **Probation** and can advance through three trust levels: - **Probation** — all actions require approval. Advances after 50 successful actions with a 95% success rate. - **Standard** — routine actions execute automatically; high-impact, bulk, and critical actions still require approval. Advances after 200 successful actions with a 98% success rate. - **Trusted** — only critical actions require approval. Trust advancement is evaluated daily by a background job. An admin can also set the trust level manually from Agent Settings (a reason is required for audit). ### Rejection escalation If a domain accumulates 3 or more rejected actions within 30 days, every action for that domain is routed to the approval queue regardless of trust level. This is additive — it cannot relax an existing approval requirement. ### Approval Workflows (multi-level) Separate from the autonomous-action approval queue, **Approval Workflows** let you define multi-level approval chains for specific app processes. These are configured at **Admin → General Settings → Approval Workflows** and are scoped to a marketplace app. Currently, three apps support trigger-specific workflows: Inspections (submission, template creation, corrective action), Frontline Execution (campaign request, campaign publication), and Policy Hub (policy publication). A workflow can have up to 10 approval levels with optional time-based escalation. ### Agent Health The **Agents** page shows the operational status of every registered agent — enabled or unavailable, with a link to each agent's management surface. Data is sourced from the shared agent registry and cached for 2 minutes. ## 4. Running it ### Reviewing pending approvals 1. Go to **Admin → AI Operations → Approvals**. The badge count in the sidebar shows outstanding items. 2. Filter by domain or priority if needed. Actions are listed oldest-first. 3. For each action, review the description, confidence score, and affected user. Approve (optionally with notes) or reject (a reason is required). 4. Use the checkboxes and **Bulk Approve** / **Bulk Reject** for high-volume queues. Approved actions execute immediately. If execution fails, the action moves to the failed state and can be retried from its detail page (up to 3 retries). ### Pausing and resuming agents - **Per domain:** from the Overview dashboard, use the pause/resume button on any domain card. A pause reason is recorded in the activity log. - **Pause All:** the emergency stop at the top of the Overview page pauses every enabled domain (including standalone agent apps like Platform Admin Agent) in one action. - **Resume All:** the counterpart. Domains paused globally by a System Admin (console-level) cannot be resumed from this page — only the System Admin can lift those. ### Reviewing action history Go to **Admin → AI Operations → Action History**. Filter by domain, status, priority, and date range (24h, 7d, 30d, or custom). A trend chart shows daily volumes by status. Export to CSV covers up to 10,000 rows. ### Retrying a failed action From an action's detail page (**Action History → click any row**), use the **Retry** button. Retries are capped at 3 per action. Sample-data actions cannot be retried. ### Managing approval workflows 1. Go to **Admin → General Settings → Approval Workflows**. 2. Click **New Workflow**, select the app it applies to, and name the workflow. If the app supports trigger processes (e.g. Inspections), select which process this workflow gates. 3. Add approval levels (up to 10). Optionally enable time-based escalation. 4. Toggle the workflow on or off with the enable/disable control. You can also duplicate an existing workflow as a starting point. ## 5. Settings All per-domain agent settings are managed at **Admin → AI Operations → Agent Settings**. Each domain has an accordion panel. | Setting | Default | What it changes | |---|---|---| | Autonomous operations (on/off) | Off | Whether the agent can propose and execute actions for this domain. Both this and the app's own agent toggle must be on. | | Trust level | Probation | Controls which actions need approval. Can be set manually; a reason is required and recorded in the audit log. | | Max actions per day | Per trust level (Probation: 10, Standard: 50, Trusted: 200) | Daily cap on agent-executed actions. 0 means unlimited. | | Confidence threshold | Per app config | Minimum confidence score (0–100) an action must reach to proceed. Actions below this are skipped. | | Pause on error rate | Per app config | Error rate percentage (over 24 hours) that triggers an automatic pause. 0 disables auto-pause. Requires at least 5 actions before it activates. | | Require approval for high-impact actions | Off | When on, actions affecting more than 5 people, or involving compensation or termination, always require approval — even at the Trusted trust level. | Per-trust-level overrides for max actions/day, confidence threshold, and error rate can be set in the advanced section of each domain panel. ## 6. More help - **AI Operations FAQ** — specific questions about limits, thresholds, and troubleshooting - **Agents** page (**Admin → AI Operations → Agents**) — each agent links to its own app's management surface - **Trust & Safety** page (**Admin → AI Operations → Trust & Safety**) — Company Brain stats, rejection feedback, and guardrail configuration - Ask AI — the assistant answers questions about AI Operations from these articles. **Keywords:** ai operations, automation hub, pause agent, resume agent, agent health, pending approvals, trust level, probation, autonomous actions, kill switch, pause all, agent safety, approval workflow, confidence threshold, error rate, daily limit, agent configuration, trust and safety --- # AI Sheets App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run AI Sheets — create spreadsheets, import data, ask AI questions, confirm AI edits (and undo row edits), build formula columns, enrich rows in bulk, and automate with rules. # AI Sheets ## 1. What it is AI Sheets is a spreadsheet app where users create, import, and collaborate on structured data — and an AI assistant answers questions about it, proposes edits for review, fills columns in bulk, and generates formulas from plain-language descriptions. Questions that involve counting, totals, or averages run as exact SQL over every row, not as model estimates. - **Enablement:** AI Sheets requires a license. An admin enables it from Admin → Apps → All Apps, then configures AI features and limits from **Settings** inside the app. - **What it is not:** AI Sheets is not a database or a BI tool. It stores flat rows of data per sheet. It does not replace external spreadsheet software — it is for structured data that lives inside your organization, with AI layered on top. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **AI Sheets**. 2. Open **AI Sheets → Settings** (visible only to app admins). Confirm that **Enable AI features** is on. Review the individual AI toggles — **AI edits**, **AI column fill (enrichment)** and **AI automation actions** are all on by default — and the **Enable AI Sheets Agent** switch, which controls the Ask AI chat agent. 3. Decide whether to turn on **Allow public sharing links** (off by default). When it is on, sheet owners can generate a link that anyone with the URL can view, optionally requiring authentication. **Who can do what** on the same page narrows who may publish one. 4. Set **Maximum rows per sheet** if the default of 5,000 is not appropriate. The value must be between 100 and 50,000. The row limit applies to each tab, so set **Maximum tabs per sheet** (default 20, between 2 and 50) in the same section if you want a tighter ceiling on how much data one document can hold. 5. Grant access to the users or groups who should see the app. Users who have access see AI Sheets in their app launcher and can create their own sheets immediately — no further configuration is required. There is no prerequisite setup beyond enabling the app. Users can create sheets, import data, or pick a template the moment access is granted. ## 3. How it fits together **Sheets and rows.** A sheet is a named grid with a defined column schema and a set of data rows. Each sheet belongs to the user who created it. Sheets support up to 100 columns and a configurable maximum number of rows (default 5,000). Each row's data is capped at 64 KB. **Tabs.** A sheet is a workbook: it can hold several tabs, the way an Excel workbook holds worksheets. A tab is a complete worksheet in its own right — its own columns, rows, formula columns, saved views, comments, automation rules, activity, version history and live sync — and the column and row limits above apply to each tab, not to the document as a whole. Everything that identifies the document belongs to the sheet and covers every tab at once: name, description, tags, star, collaborators and their roles, the public link, the Forms connection, and Trash. Sharing a sheet therefore shares all of its tabs; there are no per-tab permissions. A formula column sees its own tab by default and can read a sibling tab by naming it — `sumcolumn(amount, "Q1")`, `vlookup(id, id, rate, "Rates")` — rendering blank if that tab is later deleted. An administrator caps how many tabs one sheet may hold (default 20). **Column types.** Every column has a type: Text, Number, Currency, Date, Email, URL, Boolean, Select (dropdown with defined choices), or Formula. Formula columns are computed at read time from an expression and are never directly editable. The formula engine supports arithmetic, comparisons, logic, string functions, date functions, and aggregate functions like column totals and lookups across rows. **Collaborators and permissions.** The person who creates a sheet is the owner. Owners can share sheets with other users as **Viewer** (read-only) or **Editor** (can edit rows and data). Only the owner can delete the sheet, manage sharing, create automation rules, or save it as a template. Viewers can comment on cells. The collaborator's default permission is Viewer. Sharing is per sheet: everyone the sheet is shared with sees every row and every column — there are no row- or column-level permissions — so keep data only some people may see (pay, for example) in a sheet shared only with them. **Hide from AI.** In **Edit Sheet → Columns** (from the sheet's **⋮** menu), any editor can tick **Hide from AI** on a column. It keeps that column's values out of what is sent to the AI — Ask AI answers, AI edits and AI column fill — and the AI is told the column is withheld rather than left to guess. It does not stop the AI writing into the column, and it does not hide the column from people, exports or the public link. > *Example:* Alex creates a "Q3 Hiring Pipeline" sheet with columns for Candidate, Role, Stage (a Select column with choices "Applied", "Phone Screen", "Interview", "Offer", "Hired"), Salary, and Start Date. Alex shares the sheet with two recruiters as Editors so they can update rows, and with the hiring manager as a Viewer. The hiring manager asks the AI panel: "How many candidates are at the Offer stage?" — the system runs an exact count over all rows and returns the number. **Templates.** A sheet can be saved as a template by its owner. Templates appear in the Templates tab alongside built-in system templates (Project Tracker, Budget Tracker, Contact List, Inventory, Event Planning) and pre-populated example sheets (Sales Pipeline and others). Creating a sheet from a template copies the column schema and any existing rows into a new sheet. **Views.** Each user can save personal views on a sheet — a named set of filters. A saved view keeps filters only, not a sort order. Views are per-user: only you see the views you save, and they do not affect other collaborators. **Form bridge.** When the Forms app is enabled, a user can create a sheet from a form template. The sheet's columns are derived from the form's fields. Existing submissions are backfilled as rows, and new submissions are added automatically as they come in. **Real-time collaboration.** Multiple users editing the same sheet see each other's row changes, new rows, deletions, and comments in real time. A presence indicator shows who is currently viewing the sheet. **Tags.** Sheets can be tagged with free-text labels. Tags appear as filterable pills on the sheet list, scoped to sheets the user owns or that were shared with them — a tag on someone else's private sheet is never visible. **Starring.** Only the sheet owner can star a sheet. Starred sheets appear in the **Starred** tab for quick access. **Soft delete and trash.** Deleting a sheet moves it to the Trash tab. Sheets in trash can be restored within 30 days. After 30 days, they can no longer be restored. The owner can also permanently delete a sheet from trash at any time. ## 4. Running it ### Creating a sheet Users can create sheets in four ways from the main sheet list: 1. **Blank sheet** — enter a name and optionally describe it with AI to auto-generate columns. 2. **From a template** — pick a system template or a saved user template. 3. **Import from CSV or Excel** — upload a `.csv` or `.xlsx` file. The system infers columns and imports rows. 4. **Import from Google Sheets** — paste a public Google Sheets URL. When importing into an existing sheet, the AI can suggest how the file's headers map to the sheet's columns. ### Working with tabs The tab strip sits in the status bar along the bottom of the grid. Clicking a tab switches to it in place — the grid, toolbar and comments reload for that tab without a full page load, and the address bar still changes, so deep links, bookmarks and the browser Back button all behave normally. **Alt+↓** and **Alt+↑** (or **Ctrl+Shift+PageDown** / **Ctrl+Shift+PageUp**) move to the next and previous tab. When the strip is longer than the window, the **≡** button at its right lists every tab. Everything below needs edit access to the sheet. Viewers see the strip and can move between tabs, but not change it. - **Add a tab** — click **+**. The New Sheet dialog opens as **"Add tab to "** with the same doors as a new sheet: Blank, AI, CSV, Google and Form. On the Blank door, **Copy columns from** starts the new tab with an existing tab's column schema (no rows). The Template door is not offered for a tab. - **Rename a tab** — double-click its label, or open the tab's **⌄** menu and choose **Rename**. Tab names must be unique within the sheet. **Edit columns** in the same menu opens that tab's column editor. - **Reorder tabs** — drag a tab along the strip, or use **Move left** / **Move right** in the tab menu. - **Duplicate a tab** — **Duplicate** in the tab menu copies the tab's columns and rows into a new tab beside it. - **Delete and restore a tab** — **Delete** in the tab menu removes the tab and its rows. It is a soft delete: for 30 days the tab appears under **Deleted tabs** in the **≡** list with a **Restore** button. A sheet always keeps at least one tab, so Delete is disabled on the last one — to remove the whole document, use **Move to Trash** instead. Deleting the very first tab is allowed; the sheet's identity moves to the tab that follows it. - **When the cap is reached** — adding or restoring a tab past the tenant's limit is refused with "This sheet already has N tabs, the maximum allowed in this business." An administrator raises the limit in Settings. Tabs show up everywhere the document does: the sheet list has a **Tabs** column and totals rows across every tab; the public read-only link shows the whole strip; mobile shows a read-only row of tab pills; and the Ask AI agent can list a sheet's tabs and add one (with confirmation). ### Asking questions with AI From the AI panel on a sheet, users type a natural-language question. The AI classifies the question and responds with one of these actions: - **Aggregate** (count, sum, average, min, max) — runs exact SQL over all rows and returns the computed number, optionally grouped by a column. - **Filter** — shows only rows matching the criteria. - **Sort** — reorders rows by a column. - **Chart** — renders a bar, line, pie, or doughnut chart from the data. - **Summary** — a text analysis for qualitative questions. ### Proposing and applying AI edits When a user asks the AI to change data ("set all overdue tasks to Blocked", "add 10 rows of sample contacts"), the AI proposes the edit first — showing which rows are affected and a before/after preview. The user confirms before anything is written. Every applied AI edit is logged in the sheet's **Activity Log**. AI row edits (updates, additions, deletions and duplicate cleanups) and AI column fills can be undone from the Activity Log — and from the AI panel straight after the change, until you leave the page. A column the AI added or changed is undone from the sheet's **Version History** (Undo on that columns change); a sheet it created and an automation rule are reversed by editing or deleting the sheet or rule. Edit types include updating rows, deleting rows, adding rows, adding a column, and updating a column's label or options. ### Enriching a column with AI AI Column Fill lets users fill or classify a column's values using AI. The user describes what value to derive for each row (for example, "categorize the support ticket by urgency" or "extract the city from the address"). The system previews results on a sample of rows, and the user confirms. The fill then runs in the background in batches. It can target all rows or a filtered subset, and can skip rows that already have a value. Enrichment supports both existing columns and new columns created on the fly. ### Managing automation rules Sheet owners can create automation rules from the sheet's **Automation Rules** page — open the sheet's **⋮** (More actions) menu and choose **Automation Rules**. Each rule has a trigger, optional conditions, and one or more actions. Up to 25 rules per sheet are allowed. **Triggers:** Row created, Row updated, Row deleted, Field changed, Rows imported, or Schedule (runs at a recurring interval, minimum every 5 minutes). A row you type or paste into the grid runs its **Row created** rules about 45 seconds after its first cell is entered, so the rule sees the whole row; an **Update fields** action then fills only the cells you left empty. Rows added by Duplicate, by an AI edit or from a form response are checked and updated at once. Either way, a Row created rule's notifications, emails and webhooks go out about 45 seconds after the row is added. **Actions:** Notify collaborators, Notify a user, Send email, Update fields, Create a row, HTTP request, AI fill column (on row triggers only), AI summary digest (on schedule only), or AI anomaly alert (on schedule only). AI actions need the **AI automation actions** setting (and **Enable AI features**) on. While it is off, an AI action cannot be added to a rule or changed, and rules that already hold one keep running with their AI actions skipped — the Automation Rules page marks those actions as turned off by your administrator. Such a rule can still be renamed, turned off, or have the AI action removed. **Allow outbound automation actions** works the same way for **Send email** and **HTTP request**. ### Sharing a sheet publicly When **Allow public sharing links** is on in Settings, sheet owners can generate a read-only public link from the sheet's **Share** panel — if they are among the people allowed under **Who can publish a sheet on a public link?** (everyone, by default). The owner can optionally require viewers to authenticate (sign in to the organization) before viewing. The public link can be regenerated to invalidate previous links. ### Duplicating a sheet Any user with edit access can duplicate a sheet. Duplication copies the column schema and all data rows — every tab included — into a new sheet owned by the duplicating user. The original owner is notified. Duplication is also the mechanism behind "Use template" — using a template duplicates it and strips the template flag. ### Exporting data Sheets can be exported as CSV or Excel (.xlsx) from the sheet view. An Excel export writes one worksheet per tab; a CSV export covers the tab you are on. A template CSV (headers only, no data rows) can also be downloaded to use as an import template. Importing an .xlsx workbook works the other way round — each of its worksheets becomes a tab, up to the tab limit. ### Cell comments Any collaborator — including viewers — can comment on a specific cell (a row-and-column intersection). Comments support @mentions by email or name. Mentioned users, the sheet owner, and prior participants on the same cell thread are notified — but only people who can open the sheet: a mentioned colleague who is not on the sheet is not notified, so share the sheet with them first. Comments appear in real time for other users who have the sheet open. ### Viewing activity and version history Both pages open from the sheet's **⋮** (More actions) menu. **Activity Log** lists what happened to the sheet: creation, rows added and deleted, imports, exports, sharing, duplications, column changes, AI changes, automation problems, and more. Edits to existing cells are in Version History. AI row edits and finished AI column fills carry an **Undo** button here for editors — it keeps working even if AI features are later switched off. **Version History** lists edits to existing rows and changes to the sheet's name, description and columns, with who made each. A row edit shows the cells it changed, old value → new value; open a version to see every field it changed, previous value beside new value. A sheet-level change (name, description, columns or a tab's name) carries an **Undo** button for editors, which puts back only what that change touched, the way it was before it. Undoing a columns change also rolls back column changes made after it. Undo never touches row values — AI row edits are undone from the Activity Log, and other row edits are corrected in the grid. ### Mobile AI Sheets has a dedicated mobile view at `/m/apps/ai-sheets`. On phones, users see their sheet list, open a sheet in a simplified table view, star sheets, export to CSV, and read or post cell comments. Editors can change an existing row: tap the pencil on the row to open a form with its fields. Adding and deleting rows, the AI panel and the full spreadsheet grid are desktop-only; phones redirect automatically. ## 5. Settings All settings are in **AI Sheets → Settings** (app admin only). | Setting | Default | What it changes | |---|---|---| | **Enable AI Sheets Agent** | On | Whether people can ask about their sheets from the **Ask AI** panel on any page. It also needs **Enable AI features** on — the agent is off when either switch is off. Turning only this off keeps the AI built into the grid. | | **Enable AI features** | On | Master switch for all AI capabilities — questions, suggestions, edits, enrichment, AI automations and the Ask AI agent. Turning this off disables every AI feature while leaving the spreadsheet fully functional. | | **AI edits** | On | Whether the AI can propose row and column changes (update, delete, add rows/columns). Requires the master AI switch. | | **AI column fill (enrichment)** | On | Whether AI enrichment (bulk fill a column with AI-derived values) is available. Requires the master AI switch. | | **AI automation actions** | On | Whether automation rules can run AI action types (AI fill column, AI summary digest, AI anomaly alert). Requires the master AI switch. Turning it off also skips those actions in existing rules; the rest of each rule keeps running. | | **Allow outbound automation actions** | On | Whether automation rules can use **Send email** (to any address, including outside your company) and **HTTP request** (webhooks). Turning it off stops those actions in existing rules at once and stops new ones being added; notifications, row updates and new rows keep working. | | **Who can publish a sheet on a public link?** | Everyone with access to the app | Narrows who may turn on a sheet's public link — app admins only, or specific groups. Applies only while **Allow public sharing links** is on. Admins can always publish. | | **Who can set up an automation that emails or calls a webhook?** | Everyone with access to the app | Narrows who may add **Send email** or **HTTP request** actions to a rule — and an existing rule's emails and webhooks are skipped while its author is outside the list. Applies only while **Allow outbound automation actions** is on. Admins can always set one up. | | **Allow public sharing links** | Off | Whether sheet owners can generate a public read-only link to a sheet. Turning it off makes every published link stop working at once but does not revoke them — turn it back on and the same links work again. | | **Maximum rows per sheet** | 5,000 | The maximum number of data rows allowed in a single tab. Accepts values from 100 to 50,000. | | **Maximum tabs per sheet** | 20 | How many tabs one sheet may hold, the first tab included. Accepts values from 2 to 50. Applies to Add tab, Excel workbook import and the Ask AI `add_tab` tool. Sheets already above a lowered limit keep their tabs; nothing is deleted. | **Governance.** App admins also see a **Governance** page (in the app's side menu, or **Open Governance** on the Settings page). It lists every sheet published on a public link and every automation that emails or calls an outside address, with **Revoke link** and **Disable rule** buttons. Revoking a link kills that URL for good — the owner would have to publish a new one. ## 6. More help - **AI Sheets FAQ** — specific setup and operating questions. - Ask AI — the assistant answers questions about AI Sheets from these articles. **Keywords:** ai sheets, spreadsheet, tabs, workbook, csv import, excel import, google sheets import, formula column, automation rule, data enrichment, ai column fill, public share link, sheet template, cell comment, collaborator, export csv, export xlsx, ai-sheets, ai_sheets --- # AI Sheets FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about AI Sheets — for the admin running it. # AI Sheets FAQ Answers to common setup and operating questions about AI Sheets. For what the app is and how to set it up from scratch, see the [AI Sheets Overview](/help/articles/ai_sheets_app_overview). --- ## Setup ## Do I need to configure anything before people can use AI Sheets? No. AI Sheets has no required configuration. Once you enable the app from Admin → Apps → All Apps and grant a licence, every user in your business can create and share sheets immediately. AI features, AI edits, AI column fill, and AI automation actions are all on by default. Public sharing links are off by default and must be turned on in Settings if you want them. ## Who can access AI Sheets settings? Only app admins can see the Settings tab. App admins control the Ask AI agent switch, the master AI switch, separate toggles for AI edits, AI column fill, and AI automation actions, the outbound automation actions toggle (Send email and HTTP request), who may publish a public link and who may set up an outbound automation, the **Allow public sharing links** toggle, the maximum rows per sheet (enforced per tab), and the maximum tabs per sheet. App admins also see the **Governance** page, which lists every published public link and every automation that emails or calls an outside address, and can revoke or stop any of them. --- ## Permissions and access ## Who can see and edit a sheet? The person who creates a sheet is its owner. Owners can share the sheet with other users in the business as a **Viewer** (read-only) or **Editor** (can add, change, and delete rows). Only the owner can manage sharing settings, delete the sheet, or change collaborator roles. Sharing covers the whole sheet: everyone it is shared with sees every row and every column — there are no row- or column-level permissions. **Hide from AI** on a column (Edit Sheet → Columns) keeps its values out of AI answers, edits and fills; it does not hide the column from people. ## Can I give someone else ownership of a sheet? Not by hand — there is no transfer button, and the person who created a sheet stays its owner. They can add other users as editors, but only the owner can manage sharing and delete the sheet. The one exception is someone leaving: when an Offboarding plan runs for a person, their sheets (including any in Trash) and the automation rules they wrote are handed to their manager — or, if they have no active manager, to a business admin — and their public links are revoked. --- ## Day-to-day ## What column types are available? Text, Number, Date, Checkbox (yes/no), Dropdown, Email, URL, Currency, and Formula. Dropdown columns let you define a fixed list of choices. Formula columns compute a value per row using an expression and cannot be edited directly. ## How do formula columns work? A formula column stores one expression that computes a value for every row. You can write the expression yourself or describe what you want in plain English and let AI generate it. Supported functions include arithmetic operators plus: ``` if() round() abs() min() max() sum() concat() upper() lower() trim() coalesce() days_between() today() year() month() day() sumcolumn() vlookup() ``` `sumcolumn()` totals a column across every row; add a quoted tab name as the last argument to `sumcolumn()` or `vlookup()` to read another tab of the same sheet (`sumcolumn(amount, "Q1")`). Expressions are capped at 500 characters. There are no per-cell formulas like `=SUM(A1:A5)`, and no references to a different sheet — a formula column reads its own tab, plus any other tab of the same sheet that it names. ## How do I add, rename, reorder, or delete a tab? A sheet is a workbook, and its tabs live in the strip along the bottom of the grid. Clicking a tab switches to it in place; **Alt+↓** and **Alt+↑** (or **Ctrl+Shift+PageDown** / **Ctrl+Shift+PageUp**) move to the next and previous tab, and the **≡** button lists every tab when the strip runs off the edge. With edit access: - **Add** — click **+**. The New Sheet dialog opens as "Add tab to " with the Blank, AI, CSV, Google and Form doors. On Blank, **Copy columns from** starts the tab with an existing tab's columns. - **Rename** — double-click the tab label, or choose **Rename** from the tab's **⌄** menu. Names must be unique within the sheet. - **Reorder** — drag the tab, or use **Move left** / **Move right** in the tab menu. - **Duplicate** — **Duplicate** in the tab menu copies that tab's columns and rows into a new tab. - **Delete** — **Delete** in the tab menu. It is a soft delete, restorable for 30 days. ## What applies to the whole sheet, and what applies to one tab? Each tab is a full worksheet: its own columns, rows, formula columns, saved views, comments, automation rules, activity and version history. The row and column limits apply per tab. Two things reach across tabs on purpose: a formula can total or look up another tab by naming it — `sumcolumn(amount, "Q1")`, `vlookup(item, item, rate, "Rates")` — and an automation rule's **Create row** action can add its row to any tab of the same sheet — pick the tab under **Add the row to** in the rule builder. The sheet — the document — owns everything else, and it covers every tab at once: the name, description, tags, the star, collaborators and their roles, the public link, the Forms connection, and Trash. So sharing a sheet shares all of its tabs, and there is no way to share one tab and hold another back. Moving the sheet to Trash takes its tabs with it, and restoring the sheet brings them all back. ## How do tabs work with Excel export and import? An Excel (.xlsx) export writes one worksheet per tab, in strip order. Importing an .xlsx workbook does the reverse: each worksheet in the file becomes a tab, up to your business's tab limit. CSV export and Google Sheets import stay single-tab — a CSV export covers the tab you are on, and each Google Sheets URL imports as one tab. ## How do I import data? You can import from a CSV file (up to 10 MB), an Excel .xlsx file (up to 10 MB), or a public Google Sheets URL. Google Sheets imports have a 30-second fetch timeout and a 50 MB content cap. The Google Sheet must be shared as "Anyone with the link" with at least Viewer access — organisation-only sharing does not work because the platform fetches it without a Google login. When importing into an existing sheet, AI can suggest how to map CSV headers to your columns. ## What can the AI do with my data? When the master AI switch is on, AI can generate a column schema from a description, answer natural-language questions, compute exact aggregates (count, sum, average, min, max, group-by) over every row with provenance, generate charts, and suggest formula expressions. With **AI Edits** also enabled, AI can propose row updates, additions, deletions, column additions, and duplicate cleanup — always through a preview you confirm before anything is written. With **AI Column Fill** enabled, AI can fill an entire column in the background (classify, extract, translate, or normalize values row by row). With **AI Automation Actions** enabled, automation rules can include AI-powered actions like per-row fills on new rows, scheduled digests, and anomaly alerts. ## Can I undo an AI edit? Yes, for changes to rows. An applied AI row update, row addition, deletion or duplicate cleanup, and a finished AI column fill, is recorded in the sheet's **Activity Log** (the sheet's **⋮** menu → **Activity Log**) with an **Undo** button that editors can use at any time later — even after AI features are switched off. Straight after the change, the AI panel shows the same **Undo this change** button until you leave the page. A column the AI added or changed is put back from the sheet's **Version History** (Undo on that columns change). ## How does the Forms-to-Sheet bridge work? When you create a sheet from a form, the sheet's columns are built automatically from the form's fields. Existing completed submissions are backfilled as rows. New submissions that arrive after the sheet is created are appended automatically, and resubmissions update the existing row rather than creating a duplicate. --- ## When something looks wrong ## Why can't I import my Google Sheet? The most common cause is that the sheet is not shared publicly. In Google Sheets, choose **Share → General access → "Anyone with the link"** with at least Viewer access. Organisation-only sharing does not work. Also check that the URL starts with `https://docs.google.com/spreadsheets/d/` — other formats are not accepted. ## My CSV import skipped some rows — why? The import stops at your sheet's row limit. If the sheet already has rows, only the remaining capacity is filled and the rest are skipped. Rows that exceed the 64 KB per-row data limit are also skipped. The import notice tells you exactly how many rows were skipped and why. ## I turned on a setting but nothing changed — is it broken? The AI toggles (AI Edits, AI Column Fill, AI Automation Actions) are gated behind the master **Enable AI Features** switch. If the master switch is off, the individual toggles have no effect. Turn on the master switch first, then enable the features you want. ## Why can't I see the public link option on my sheet? The public link lives in the sheet's **Share** panel, and only the sheet's owner has the **Share** button. In that panel, the **Enable public link** switch appears when two more things are true: an app admin has turned on **Allow public sharing links** in AI Sheets Settings (it is off by default), and you are among the people allowed under **Who can publish a sheet on a public link?** in the same Settings page (everyone, by default). When either is missing, the panel's **Public Link** section says which one and whom to ask. ## I deleted a tab by mistake — can I get it back? And why can't I delete this one? Deleting a tab is a soft delete. For 30 days it sits under **Deleted tabs** in the **≡** list at the right of the tab strip, with a **Restore** button next to it; restoring brings the tab's rows, comments and views back with it. Restoring is refused only if the sheet has meanwhile filled up to the tab limit — delete a tab first, then restore. Delete is disabled on the last remaining tab, because a sheet always keeps at least one. To get rid of the whole document, use **Move to Trash** on the sheet instead. Deleting the *first* tab is allowed — the sheet's identity simply moves to the tab that follows it, and the sheet's name, sharing and public link are unaffected. ## My automation rule stopped running — what happened? Open the sheet's **Automation Rules** page (the sheet's **⋮** menu — only the sheet's owner can open it). Renaming a column never breaks a rule — rules remember columns by their internal key, not their label. These do: - **A column the rule uses was deleted.** The rule is badged **Stale**; hover the badge, or open the rule, to see which columns are missing, then edit the rule. - **The rule was turned off.** Its status reads **Disabled**. The sheet's **Activity Log** says why: "System disabled the automation …: its author … is no longer an active member of this business" means the person who set the rule up left, and a rule never runs on behalf of someone who has gone (recreate it to run it as you); "… disabled the automation … as an AI Sheets admin" means an app admin stopped it from the **Governance** page. - **The rule is on but its author can't open AI Sheets.** Its status still reads **Enabled**, but it is skipped while the person who set it up can't open the app — an admin made AI Sheets admin-only again, changed who can use it, or a seat changed. The **Activity Log** says "System skipped the automation …", and the rule runs again by itself once they can open the app. - **Some of its actions are switched off.** An action marked with a ⊘ icon is skipped while the rest of the rule runs: your administrator turned off **AI automation actions** or **Allow outbound automation actions** (Send email, HTTP request) in Settings, or limited **who can set up an automation that emails or calls a webhook** and the rule's author isn't included. ## I asked AI to fill a column, but some rows came back blank — why? AI column fill runs one LLM call per batch of 20 rows. If the AI cannot determine a value for a row (the source data is ambiguous or empty), it returns blank for that row. The enrichment status shows how many rows were filled, skipped, and failed. You can re-run enrichment with different instructions or on a narrower filter. --- ## Licensing and limits ## Does AI Sheets require a licence? Yes. AI Sheets requires a licence and is disabled by default. An administrator enables it from Admin → Apps → All Apps for your business. Individual users do not need separate licences — once the app is enabled, everyone in the business can use it. ## How many tabs can one sheet have? Twenty by default, and an app admin can set the limit anywhere from 2 to 50 under **Settings → Limits → Maximum tabs per sheet**. The first tab counts towards the limit. It is enforced everywhere a tab can be created — the **+** button, importing an Excel workbook, restoring a deleted tab, and the Ask AI `add_tab` tool — and the refusal names the number: "This sheet already has 20 tabs, the maximum allowed in this business." Lowering the limit never deletes anything; sheets already above it keep their tabs and simply cannot gain more. Because the row limit applies to each tab, the tab limit is what bounds how much data one document can hold: tabs × rows. ## What are the limits? | Limit | Value | |---|---| | Rows per tab | 5,000 default; configurable from 100 to 50,000 | | Tabs per sheet | 20 default; configurable from 2 to 50 | | Columns per tab | 100 | | CSV / Excel upload size | 10 MB | | Google Sheets fetch cap | 50 MB | | Per-row data size | 64 KB | | Automation rules per sheet | 25 | | Actions per automation rule | 10 | | Conditions per automation rule | 50 | | Minimum schedule interval | 5 minutes | | Rows per AI edit or deletion | 1,000 per operation | | Rows per AI add | 100 per operation | | Rows per AI column fill | 1,000 per run | | Formula expression length | 500 characters | | Google Sheets import timeout | 30 seconds | | Sheet name length | 255 characters | | Sheet description length | 5,000 characters | | Automation rule name length | 255 characters | --- ## More help - [AI Sheets Overview](/help/articles/ai_sheets_app_overview) - Ask AI — the assistant answers AI Sheets questions from these articles. **Keywords:** faq, ai sheets, spreadsheet, tabs, workbook, row limit, tab limit, formula, enrichment, automation, import, public link, sharing, csv, google sheets, column limit, ai edits, ai-sheets, ai_sheets --- # App Builder FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about App Builder — mini apps and custom apps — for the admin running it. # App Builder FAQ Answers to common setup and operating questions about App Builder. For what the app is and how to set it up from scratch, see the [App Builder Overview](/help/articles/app_builder_app_overview). --- ## Setup ## Does App Builder need to be enabled or licensed before anyone can use it? There is nothing to license, but it does have to be turned on. App Builder is included with every edition and off by default: an administrator enables it from Admin → Apps → All Apps. Building and trying apps is free, and there is no per-employee charge. On our shared cloud, once mini app packs are switched on for your company, each *published* mini app takes a slot in a pack of live apps; custom apps take no slot. It stays opt-in rather than always-on because it can deploy code into your tenant, which is a decision an admin should make deliberately. AI tokens the builder spends stay on the shared platform AI-credits meter and are not billed separately. ## Who can build apps, and who can only monitor? Three tiers. A **global administrator** can do everything: create and edit mini apps, build, edit and deploy custom apps, manage API keys, and change settings. The **composer tier** — governed by the **Who can create mini apps** setting on **App Builder → Settings** (the **Who can build** card) — can compose, edit, and start mini apps from templates, and sees the mini apps they created on **Your apps**: the default admits everyone with the **Manager role** (plus admins and app-admins). A team lead with the Member role is not in it until you choose **Managers and admins, plus anyone with direct reports**; you can also widen it to everyone or narrow it to app-admins only. A **delegated app-admin** — granted from Admin → Apps → All Apps — can monitor Your apps, publish, unpublish and retire apps there, browse Templates, view Analytics, and retry loading a failed app. Code builds and Settings stay global-admin everywhere. Anyone else who built an app asks for it with **Ask an admin to publish** on the app's own page (also on its row in Your apps, its Edit with AI page and on the phone), where they can also see that they asked and withdraw the request. ## Can my managers create mini apps without me granting each one access? Yes — that is the default for everyone with the **Manager role**. **Who can create mini apps** (App Builder → Settings) ships set to **Anyone with the Manager role or above**, so they can open App Builder's home, see the mini-app and template cards, and compose — with no per-person grant. People who run a team but have the Member role are not included: choose **Managers and admins, plus anyone with direct reports** to add them without leaving anyone out. Set it to **Everyone with access to the app** and any member can (the office manager who needs a visitor log builds it without asking); set it to **App admins only** to require an explicit grant again. Whoever composes also approves the app's capability grants on its card, so widen with that in mind. ## I granted someone app-admin access but they can't build a custom app — is that a bug? No. Building a custom app deploys code and Settings governs unattended AI spend — both require the global-admin tier. A delegated app-admin sees Home, Your apps, Templates, and Analytics; they can publish, unpublish and retire apps from Your apps, and compose mini apps (the composer tier admits app-admins). The surfaces match the actions each tier can take, so nothing they can click will bounce them. ## Where did the Build, Compose, and Builds tabs go? They were removed from the left rail on purpose. Tabs are now *places* — Home, Your apps, Templates, Analytics, Settings — and the *verbs* live in the **Create** fork on the Home page: Mini app, Custom app, and Start from a template. Build history moved onto Your apps and the Recent builds card on Home. Every old URL still works; only the tabs changed. --- ## Mini apps vs. custom apps ## Should I create a mini app or a custom app? Start from what the thing *is*, not from how it should be built. If you are tracking, counting, or logging records — supplies on a shelf, visitors at a desk, equipment on loan, vehicle inspections — that is a mini app: no code, reviewed on a plain-language approval card, and running the same day. If you need custom screens, unusual logic, or an integration with an outside system, that is a custom app and AI writes real code for it. You do not have to get this right up front. The create fork asks in those terms rather than by technology, and the two paths cross-recommend each other — start describing a tracker in the code builder and it will point you at the faster path. ## What is actually created when I approve a mini app? Real platform objects, not a private copy of anything: a Power Tables table with your fields, the saved views you approved, automation rules, and — if the plan included one — a Live Board. Together they are registered as a marketplace app with its own slug, icon, launcher entry, and permissions, running at `/apps/`. **No code is generated and nothing is deployed.** That is why a mini app is live in minutes and why it improves as Power Tables and Live Boards do. ## Do mini apps show up in the public app directory? No. Mini apps are private to the tenant that created them. They never appear in the public MangoApps directory or in another business's marketplace, and there is nothing to submit — listing an app for other businesses exists only for custom apps. Publishing a mini app (next question) makes it live inside your own company, nowhere else. ## Are my mini apps visible to employees straight away? No. Every app you build — mini or custom — starts **unpublished**: only its creator, App Builder admins and anyone granted a role on the app can open it, so you can try it with real records before anyone else sees it. To take it live, an administrator or App Builder app-admin presses **Publish** on its row in **App Builder → Your apps**, which shows it to everyone; to limit it to some groups, add a visibility rule from Admin → Apps → All Apps instead. If you built it but cannot publish, press **Ask an admin to publish** on the app's own page or its row in **Your apps** — it then says that you asked, offers **Withdraw request**, and tells you if an admin declines. **Unpublish** on its Your apps row takes a live app back to just its creator and the admins — except that groups it is shared with keep it until their visibility rule is removed in Admin → Apps → All Apps. ## Do I need Power Tables and Live Boards licensed separately? No, and you do not need to turn them on. A mini app's records belong to the mini app itself, so it works with neither app enabled, and approving one switches nothing else on for the business. --- ## What a mini app can and cannot do ## What can a mini app's automations actually do? The always-on palette is four actions: **update a field on the record**, **notify a person**, **open a task**, and **send a scheduled digest** of what a saved view matches. Recipients come from a fixed vocabulary — the record's filer, the app's creator, a person-field on the record (an assignee), that person's manager, a role, or a team — never a free list. Four more powers exist only as **capability grants** the approval card disclosed and you approved: **send email** to an email-address field stored on the record (one address, rate-capped), **request approval** from a named approver before something proceeds, **public capture** (a public form at a tokened link), and **kiosk capture** (a shared-tablet kiosk where a badge tap identifies the employee — see the kiosk question below). You can revoke any of them later from the edit loop, and the revocation card names everything that stops working. Still impossible at any tier: webhooks, deleting or archiving rows, invoking AI, and approvals nested inside approvals. ## Can I get an alert 30 days before something expires? Yes. A mini app's triggers are **a record was created**, **a field changed**, and **on a schedule** — a scheduled rule binds to a saved view and sends a **digest** of everything the view currently matches. So "every Monday, message me what expires in the next 30 days" is one automation: a view filtered to the expiry window plus a scheduled digest to you. The digest is one summary message, not one message per row, so a big backlog cannot flood anyone. ## Can one mini app cover two linked tables? Yes — up to **three**. Describe owners, pets, and stays and the drafter composes three linked tables, connecting them with reference fields (a stay points at its pet, a pet at its owner) and giving every table its own page. Describe *more* entities than fit and it **folds** the extras into fields on an existing table — and the approval card says exactly where the fourth list went, so you approve what actually happened. A mini app can also hold a **reference to another mini app's records**, which is the platform's answer for shapes bigger than one app. ## Can the edit loop rename or remove things, or only add? Both directions. Adding: fields, views, automations, screens, a linked table, a board, a quick-update form, a public form. Changing and removing: **rename a field, remove a field, remove a page, edit a workflow field's allowed status moves, and revoke a capability**. Removals refuse honestly instead of half-working — you cannot remove a table's only page, and an app always keeps at least one page. Bulk restructuring still lives in the app's settings page and the Power Tables / Live Boards surfaces, where the same referential protection applies. ## Can people without OneMango accounts submit records to a mini app? Yes, if the app holds the **public capture** grant. The approval card discloses it in plain words ("anyone with the link can submit — no sign-in"), and once approved the app serves a public form at a tokened link you'll find in the app's settings — post it at the gate, print it as a QR code, or email it to suppliers. Submissions are honeypot-protected and rate-capped per business per hour. Fields the app's own automations set (a governed Status, say) are never offered on the public form — outsiders state facts, the app runs the workflow. Public submissions land as ordinary records, so views, boards, automations, and approvals all see them. ## Can employees use a shared tablet instead of their phones — a cafeteria register, a tool crib? Yes, if the app holds the **kiosk capture** grant. Its settings page shows a **kiosk link**: open it once on the tablet and it becomes the kiosk — *tap your badge → pick what applies → Done*, and the screen resets for the next person. The tablet's USB or Bluetooth badge reader "types" the badge number (the same RF IDeas-style readers used for workstation tap-in); a QR-coded badge works with a 2D scanner or the tablet camera, and typing the badge number works too. The kiosk is **badge only** — an employee number is refused, because a number is printed on paperwork while a badge has to be in hand — and every record it writes names the badge's owner in the person field and the change history. A badge counts when it matches the **Badge ID** on the employee's profile; fill that by tapping the badge on the profile's Badge ID box, or through the user import. "New link" in the app's settings unpairs every tablet at once; "Turn the kiosk off" closes the door while the app keeps running. The **Cafeteria Meal Log** template ships with a kiosk. ## Can a badge tap fill in the person on an ordinary record, not just at a kiosk? Yes. Turn on **Identify by badge tap** for any person field (Manage fields → the column's settings; the composer's plan carries it as `badge: true`). The record form then shows a badge box above the people picker — a tap or a camera scan of the badge's code selects the person, exactly as searching would. Typing a colleague's badge number in that box works too, so this is a convenience, not a lock; the kiosk is the surface that insists on the badge. ## I revoked the public link — is my printed QR code garbage now? No, and this is deliberate. Revoking public capture kills the link immediately: the form 404s and nothing can be submitted. But the token survives the revocation, so **re-granting the capability revives the SAME link** — the QR code taped to the gate works again without reprinting. If you want a genuinely new link (say the old one leaked), rotate the token from the app's settings instead. ## Can a mini app require a manager's sign-off before something proceeds? Yes, with the **request approval** grant. The plan names who approves in the same vocabulary as notifications (a role, a person-field's manager, and so on), and the card spells out what happens on approve and on decline — those follow-up actions are part of what you review. The approval itself is the platform's real approval flow: the approver gets a proper request with a human-readable summary, and the decision is recorded on the record. ## What is the quick-update form, and why can someone with no table access use it? It is one narrow door: identify a single record by its code, and report a new number for one field. The confirmation names the record and shows the movement — `12 → 9`, not just "saved" — and an optional note lands in that row's change log alongside every other change. It is safe to expose that widely precisely because it is narrow. It cannot create records, browse or read the table, touch any other field, or be pointed at a different table — every one of those is fixed by the app's definition, never by the request. So a member with no Power Tables data access can still open the mini app, use the door, and see an honest notice about what they cannot see, rather than a silently empty grid. ## I deleted a view the app created — what happens now? It stays deleted. Updates to a mini app only ever *add* pieces, so a later version never brings back something you deliberately removed — and everything else in the app keeps receiving updates as normal. The app's settings page says so. **Renaming** anything is always safe (views, automations, and the board reference fields by ID), and **archiving** an object keeps it resolvable. If you want a removed view back, ask for it in the app's edit loop (**Edit with AI**) and approve the change — turning the app off and on again does not re-create it. ## If I start from a template, do I get updates to that template later? No. A template compiles a **copy**. From the moment you approve it the app is yours, fully editable, with no upgrade tie back to the source — the app's settings page names the template it came from and says exactly this. The template shelf lists the platform's templates (fields, views, automations and screens together) and your workspace's own mini apps that you can open, as a starting point for a copy. ## I drafted a mini app but navigated away — did I lose it? No. Drafts are saved automatically the moment a plan comes back, so drafting does not have to be done in one sitting. Resume or discard them from the **Your open drafts** card on the compose page. Drafts are per-admin working notes, not a shared surface, and approving a plan settles its draft. --- ## Permissions and access ## Why can't my employees see the custom app I just deployed? A newly deployed custom app starts unpublished — only you and App Builder admins can open it. To roll it out, press **Publish** on its row in **App Builder → Your apps**, or scope it to specific groups with a visibility rule from **Admin → Apps → All Apps**. Until you publish, employees cannot see it in the app launcher or navigate to it. Mini apps work the same way. ## Can employees change settings in a deployed app? No. Settings inside a deployed custom app are restricted to administrators. Employees can use the app — view records, create records, submit forms — but cannot change its configuration. ## Who can change a mini app's settings? Someone holding an app-admin grant on *that mini app*, or a Power Tables admin. Each mini app is a real marketplace app, so a global admin can delegate administration of one specific mini app without handing over App Builder itself. That person can rename the app's vocabulary, print QR labels, manage its fields, and switch the app off. Who can *use* the app is a separate question, governed by the mini app's own audience — not by Power Tables' audience. --- ## Day-to-day ## How do I edit an app that is already deployed? For a **custom app**: open the build session from Build history or click **Edit with AI** on the app in **Your apps**. Describe the change in the conversation. The builder drafts a plan and pauses for your approval before writing code, the same way it does for a new build. After you review the changes, click **Deploy** or **Update** to push them live. Version history keeps the previous state one restore away. For a **mini app**: open it from Compose or Your apps and describe what to **add**. The proposed change renders on its own approval card, and applying it bumps the app's version. There is no deploy step — the change is live when you approve it. ## What does the plan-approval step look like? For a custom app, the builder drafts a plan listing the record types, screens, files, and capabilities the app will include, then pauses. For a mini app, the approval card lists every table with its fields and who can write to it, each saved view and what it filters to, each automation and what it does, the pages, the board, the quick-update form — and, in their own block, any **capability grants** the app needs (a public form, outbound email, approvals), each explained in plain words, because approving the card is what grants them. In both cases you can revise, edit, or decline before anything is created, and in both cases the plan is re-validated on the server when you approve it — so what you approved is what you get. ## Can I attach screenshots or documents when describing an app? Yes, in the custom-app builder. You can attach up to **5 images per message**, each up to **10 MB**. Accepted formats are PNG, JPEG, GIF, and WebP. The mini-app composer is text-only — you describe what you want to track in a sentence or two. ## How do I save a build as a reusable template? After a successful custom-app build, click **Save as template** in the builder. The template captures the original description and the approved plan specification, and is scoped to your business. You can also create templates manually from the Templates shelf. System templates (the curated gallery) are read-only, but you can import one as an editable draft. Mini-app templates are platform-provided and appear at the top of the same Templates page. ## How do people use a mini app from the shop floor? Two ways, neither of which needs an app install or a scanner. **Print QR labels** from the app's Manage menu gives you a sheet of one code per record; scanning a label with a phone camera opens that record's mobile card with − / + steppers. Or send people straight to the app's **quick-update** door, where they type the code and the new number. Both land in the same audit trail as every other change. --- ## When something looks wrong ## My app stopped loading — what happened? This applies to deployed custom apps. When one fails to load, App Builder records the failure. After **3 consecutive failures**, the app is quarantined and stops being loaded for users entirely. You will see a health alert in your inbox if alerts are on. From **Your apps**, you can retry loading the app, or open its build session with **Edit with AI** and use **Fix with AI** to repair the code. Rolling back to an earlier deployed version is on the app's page under **Admin → Custom Apps**. ## The builder hit its iteration limit and paused — what do I do? Click **Continue**. Each click doubles the builder's iteration budget for that session. If **Auto-continue long builds** is on in Settings (the default), medium and rich builds extend automatically up to **2 extra rounds** before pausing. The absolute ceiling is **120 iterations**. If that is not enough, the per-session token budget (12 million tokens by default) is the real stop. ## I got a "still processing" error when I sent a message The builder processes one message at a time. If you see this error, a previous turn is still running. Wait for it to finish, or click **Cancel** to stop the current generation before sending a new message. Short confirmations like "yes" or "build it" sent while a build is already running are absorbed silently so they do not block you. ## My mini app says it is still being set up — is it broken? Almost certainly not. Creating a mini app stamps several objects (a table, its columns, views, rules, and possibly a board), and that work finishes in the background. If a step fails, the platform retries and heals forward rather than starting over — the process is designed so a retry completes the remainder instead of duplicating anything. Give it a minute and reload. If it is still stuck after that, check **Your apps**. ## I see a health alert about an event handler being suspended — what does that mean? A built custom app's event handler was suspended after repeated failures when processing events. Events for that handler are being dropped until an administrator unsuspends it. Open the app in the builder or from Admin → Custom Apps to investigate and redeploy a fix. ## I can't find the app on my phone — where did it go? The custom-app builder itself is desktop-only. On a phone you see a "Building happens on desktop" card and a list of your live built apps that have a mobile view. Not every built app has a mobile page — only apps with record types are servable on mobile. Mini apps work in a phone browser, and QR labels deep-link straight to a record's mobile card. ## I submitted a form through the public link but nobody received it — why? Public submissions land as records in the app. If nobody is being notified, the app's notification rules or SLA configuration may not cover the public-submission flow. Ask your administrator to check the app's notification and overdue settings in the builder. ## How many versions of my app are kept? The builder keeps up to **10 file snapshots** per build session. Versions increment as you build and edit. When the cap is reached, the oldest snapshot is dropped. Restoring a version takes a safety snapshot of your current files first, so you do not lose the state you are rolling back from. --- ## Licensing and limits ## What are the mini-app limits I should know about? | What | Limit | |---|---| | Tables per mini app | 1–3, linked with reference fields; each table gets its own page | | Fields per table | 1–20 | | Field types available | Text, number, counter, choice, date, person, attachment, reference (a link to one record of another table or mini app), lookup (show a field through a reference) | | First field | Must be text — it is the record's display name | | Field name length | 60 characters | | App name length | 1–60 characters | | Options on a choice field | 2–20 | | Saved views per table | 6 | | Automations per mini app | 10 | | Automation actions — always available | Update a field, notify a person, create a task, scheduled digest of a saved view | | Automation actions — capability grants (disclosed on the card) | Send email to an address stored on the record, request approval, public capture form | | Automation recipients allowed | The record's filer, the app's creator, a person-field on the record, that person's manager, a role, or a team | | Automation triggers allowed | Record created, field changed, schedule | | Pages (screens) per mini app | 5, each with up to 5 sections; metric cards per page: 4 | | Rows shown on a live board | 3–10 | | Description length when composing | 2,000 characters | | Description length when editing | 1,000 characters | | Automatic repair rounds on an invalid draft | Up to 2, and only while each round fixes more than the last | | Open drafts kept per composer | 10 | | Records per printable QR label sheet | 120 | | Public form submissions | Honeypot-protected and rate-capped per business per hour | | How many mini apps you can run | Bounded by your company's table limit (each table counts), at most 25 unpublished at once, and — where mini app packs apply — your pack size for live ones | ## How many mini apps can we have? Three limits apply. **Tables:** each mini app creates one to three tables, and every table counts toward your company's table limit, which it shares with tables built by hand. The default is **5 tables**; an administrator can raise it to **25** on Power Tables' settings page without asking anyone (Power Tables has to be turned on in Admin → Apps → All Apps to open that page). Beyond that requires a MangoApps Console grant, which tops out at 500. If approving a mini app is refused with "This app needs N new tables, and your company's table limit … has room for M", that is the number to raise — then approve it again (an AI draft stays in **Your open drafts**; a plan started from a template is started again from that template). An app composed earlier whose setup stopped on "Table limit (5) reached" recovers the same way, with **Retry setup now**. **Unpublished apps:** up to 25 apps can wait unpublished at once; publish or retire one to create another. **Live apps:** on our shared cloud, once mini app packs are on, how many mini apps can be published at once is the size of your pack. ## What are the custom-app build limits I should know about? | What | Limit | |---|---| | Platform APIs available to a built app | 81 | | Declared capabilities an app can request | 16 | | Image attachments per message | 5 | | Image size | 10 MB | | Builder chat messages | 60 per hour | | Agent iterations per build turn | 40 | | Absolute iteration ceiling per session | 120 | | Wall-clock limit per build turn | 600 seconds | | Per-session token budget | 12,000,000 tokens | | Auto-continue rounds (medium and rich builds) | 2 | | File snapshots retained | 10 | | Quarantine threshold | 3 consecutive failures | | Health alert deduplication window | 6 hours | | API key scopes | builder, query, manage | | AI-usage log retention | 30 days | ## How is App Builder priced? App Builder is included with every edition, with no per-employee charge and no per-app charge for custom apps. Building and trying apps is always free: an app counts only once it is **published** to users and working. The one exception is size: records beyond an app's first **25,000** bill as app records whether or not it is published. On our shared cloud, once mini app packs are switched on for your company, live mini apps are sold in packs — from 1 to 100 apps, priced per app per month. Each published mini app takes one slot, and its slot includes the app's first **25,000 records** and its boards. Three consequences worth knowing: - An unpublished mini app takes no slot, so build and test as many as you like (up to 25 unpublished at once). - A mini app that fails to load is **free while it is broken**. - **Custom apps take no slot.** A mini app's records belong to the app, not to Power Tables, so they never add to Power Tables' usage. Builder AI tokens are not billed separately either — they stay on the shared platform AI-credits meter, and the Analytics tab shows the spend. For current rates, talk to your MangoApps account team. ## Can I build apps from external tools instead of the browser? Yes, for custom apps. App Builder issues scoped, revocable API keys and exposes an MCP endpoint. External tools — Cursor, Claude Code, or a CLI — can list tools, call them, and run read-only platform queries against your tenant. Keys track last use and can be revoked from the builder at any time. The three available scopes are **builder**, **query**, and **manage**. ## What quality checks does a build go through before I can deploy? Every custom-app build passes three checks before deploy is offered. First, deterministic fit checks validate the schema, paths, and file structure. Second, an AST-level static security scan inspects the generated code for sandbox escapes, forbidden method calls, and tenant-isolation violations. Third, an AI QA reviewer reads the intent (your description plus the approved plan) against the generated files and judges whether each scenario is correctly implemented. Mini apps do not go through these, because there is no code to scan. Their equivalent safeguard is the palette itself: the plan is validated against a fixed set of allowed field types, operators, actions, and recipients before you see it, and validated again on the server when you approve it. ## What can the Ask AI agents do — and what can't they? Two agents split this territory, and Ask AI routes to the right one by what you ask. The **App Builder agent** covers built custom apps. Four read tools: list the custom apps this business has built, report one app's health, show a built app's deploy/enable/disable audit trail, and list recent build sessions. Two write tools — **enable an app** and **disable an app** — both confirm first, only work on apps this business actually built, and are global-admin only. It cannot deploy, roll back, or delete an app, and it does not cover mini apps. The **Mini Apps agent** covers composed mini apps, for anyone the mini is published to: list the mini apps in this workspace, describe one's tables, fields, views and screens, look up and search records, report per-table record counts, and submit a quick-update form (with confirmation). It enforces each mini's own audience and each table's access on every tool call — ask about a restricted table and it tells you it cannot access it, rather than guessing. --- ## Settings ## What do the App Builder settings control? **Settings** is for global administrators only. Besides **Enable AI agents** (the switch for both App Builder agents in Ask AI) and **Who can create mini apps**, it carries three toggles: - **Auto-continue long builds** (default: on) — when a medium or rich custom-app build hits its iteration limit, the builder extends automatically (up to 2 rounds) instead of pausing for a click. - **Alert on built-app health problems** (default: on) — sends a notification when a built app is quarantined, fails to load, has an event handler suspended, or has an auto-update rolled back. Alerts are deduped to at most one per app per event per 6 hours. - **Alert when a marketplace-installed app has an update** (default: on) — sends a notification when a newer published version of an app your business installed from the marketplace is available. Apps built here raise no update alert — a built app changes when you redeploy it. An optional **Additional notification recipients** field lets you widen alerts to an admin-configured recipient group. Without it, alerts go to the app's builder and deployer first, then fall back to App Builder's app-admins. The three toggles and the recipient group concern custom-app builds. None of them affects mini apps, which have no build job, no iteration limit, and no deploy step. ## Where are a mini app's own settings? On the mini app itself, under **Manage → App settings**. That page carries the app's fields and where they came from, the vocabulary controls (rename "records" to whatever your business calls them, and relabel the tabs), the full list of objects the app manages, and an on/off switch for the whole app. Turning the app off hides it for everyone; the data is untouched and the settings page stays reachable so you can turn it back on. --- ## More help - [App Builder Overview](/help/articles/app_builder_app_overview) - [Power Tables Overview](/help/articles/power_tables_app_overview) — where a mini app's data lives - [Live Boards Overview](/help/articles/live_boards_app_overview) — where a mini app's board lives - Ask AI — the assistant answers App Builder questions from these articles. **Keywords:** faq, app builder, mini app, composed app, custom app, plugin, build, compose, deploy, template, api key, quarantine, fix with ai, health alert, iteration limit, token budget, not loading, permissions, app admin, quick update, table quota, public form, public capture, qr code, kiosk, badge tap, badge reader, shared tablet, approval workflow, linked tables, multi-table, workflow transitions, reference field, scheduled digest, who can create mini apps, composer access, app-builder, app_builder --- # App Builder Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and use App Builder — describe what you need in plain language and get either a no-code mini app composed from platform primitives, or a full custom app with AI-written code. # App Builder ## 1. What it is App Builder is where an administrator describes something the business needs and gets a working app, instead of filing a ticket against a six-month internal-tools backlog. It asks one question first: **does this need code?** Most of the list does not, so App Builder produces two different kinds of thing: - **Mini apps — no code.** Describe something you need to track, count, or log. An AI drafts a plan, you review it on a plain-language approval card, and on approval it becomes a real app at `/apps/` with its own icon, launcher entry, tabs, and permissions. **Nothing is generated and nothing is deployed** — a mini app is configuration stamped onto shared platform primitives (a Power Tables table, saved views, automation rules, and optionally a Live Board), so it inherits their scale, permissions, and audit trail and improves as they do. - **Custom apps — AI-written code.** When the need is custom screens, unusual logic, or an integration with an outside system, the same conversation writes real, inspectable files that deploy as their own app at `/apps/ext/`. The code path can also produce narrower artifacts — a dashboard widget or an Ask AI agent — which appear as their own categories on the Templates shelf. Both paths pause for your approval before anything is created, and both produce apps that are enabled per business like any other marketplace app. - **Enablement:** App Builder is included with every edition, with no per-employee charge, and off by default. An administrator enables it from Admin → Apps → All Apps. Building and trying apps is free; an app counts only once it is published and working (records beyond an app's first 25,000 bill as app records, published or not). On our shared cloud, once mini app packs are switched on, each published mini app takes a slot in a pack of live apps (its slot includes its first 25,000 records and its boards); custom apps take no slot. A mini app's records never bill through Power Tables. - **What it is not:** App Builder is the tool that *creates* apps. It is not where they run. A mini app runs at `/apps/`; a custom app runs at `/apps/ext/`. To manage or troubleshoot a running app, use the **Your apps** tab inside App Builder, the app's own settings page, or the **Custom Apps** page under **Admin → Apps & Integrations**. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **App Builder**. There is no seat license, and enabling it costs nothing — building and trying apps is free. 2. Open **Apps → App Builder**. Building custom apps and Settings are admin surfaces, and the full register of built apps is too (someone in the mini-app tier sees only the mini apps they created on **Your apps**) — but **creating a mini app is its own tier**: by default everyone with the Manager role can compose one, and the tenant can add people who run a team, widen it to everyone or narrow it back to app-admins with the **Who can create mini apps** setting (see Settings below). 3. On the App Builder **Home** page, the **Create** fork offers cards stated as needs rather than technologies — **Mini app**, **Custom app**, and **Start from a template**. The cards match your tier: a manager with composer access sees the mini-app and template cards; only full administrators see **Build a custom app**, because only they can deploy code. 4. **For a mini app:** click **Create a mini app**, describe what you want to track, and click **Draft my app**. Review the approval card — fields, views, automations, board, and quick-update form are all shown before anything exists — then click **Approve & create app**. The app is ready at `/apps/` within moments — unpublished, so only you and App Builder admins can open it until it is published (below). 5. **For a custom app:** click **Build a custom app** and describe what you want. The builder drafts a plan showing the record types, screens, and capabilities it intends to generate, then pauses for your approval before writing any code. Approve it, wait for the build, then click **Deploy**. **What is visible to whom, by default:** both paths work the same way. - **Every app you build starts unpublished** — a mini app once you approve it, a custom app once you deploy it. Only its creator, App Builder admins and anyone granted a role on the app can open it, so you can try it with real records first. Enabling App Builder does not make built apps visible to anyone. - **Publishing** is one button: **Publish** on the app's row in **App Builder → Your apps** shows it to everyone. Administrators and App Builder app-admins can press it; anyone else who built the app presses **Ask an admin to publish** on the app's own page or on its row in Your apps, which then shows the request and offers **Withdraw request** (an admin can **Decline request** on Your apps, and the person who asked is told). To show an app to some groups only, add a visibility rule from Admin → Apps → All Apps instead. **Unpublish** on the same row takes it back; groups it is shared with keep it until their visibility rule is removed. **No other app is switched on:** a mini app's records belong to the mini app itself, so approving one enables nothing else for the business. Each mini app creates one to three tables, and those count toward your company's **table limit** — the FAQ has the numbers and where to raise it. **Delegating access:** a full administrator can grant another person App Builder app-admin access from Admin → Apps → All Apps. That person can then monitor deployed apps and analytics, publish, unpublish and retire apps from Your apps, and create mini apps — without being able to build or deploy custom apps or change settings. ## 3. Key Concepts (How It Works) These are the distinctions worth getting right before you start — most confusion about App Builder traces back to one of them. ### Mini app vs. custom app vs. widget | | Mini app | Custom app | Widget / agent | |---|---|---|---| | **What it is** | Configuration on shared primitives | Generated Ruby/ERB files | A dashboard card or Ask AI agent inside a built app | | **Is code written?** | No | Yes, and you can read and edit every file | Yes — it is part of a code build | | **Is anything deployed?** | No | Yes, to `/apps/ext/` | Yes, with its package | | **Where it lives** | `/apps/` | `/apps/ext/` | The dashboard / the Ask AI sidebar | | **Good for** | Tracking, counting, logging, registers | Custom screens, unusual logic, integrations | Surfacing a number, or answering questions | | **Billing** | Free until published; where mini app packs apply, a live one takes a pack slot | No per-app charge, no pack slot | Part of its app | The honest rule of thumb: if you are tracking, counting, or logging records — supplies on a shelf, visitors at a desk, equipment on loan — that is a mini app, and it will be running the same day. If you need screens or logic that a table cannot express, that is a custom app. You do not have to decide correctly up front: the create fork asks in those terms, and the two paths cross-recommend each other. ### Plan vs. manifest vs. install Three words that sound interchangeable and are not: - A **plan** is what the AI drafts and you approve. It is *data*, written in field names, and it is what the approval card renders. A plan is validated before it is shown to you and validated again when you approve it, so nothing can be smuggled past the rules between those two moments. A plan you draft but do not approve is saved as a **draft** you can resume later. - A **manifest** is what a plan compiles into: a versioned JSON definition of the app, stored against your business. The manifest is the app's source of truth, and its version number goes up each time you make an additive edit. - An **install** is the record of that manifest having been *stamped* into your tenant — the actual Power Table, columns, saved views, automation rules, and Live Board that were created, and which manifest version created them. Stamping is idempotent: re-running it heals a partial install instead of duplicating anything. For a custom app the equivalent sequence is plan → generated files → deployed package, and the artifact you inspect is the code rather than a manifest. ### What the edit loop may change When you go back to a mini app and describe a change, the drafter proposes it on its own approval card, and the palette covers both directions: - **Adding**: fields, saved views, automations, screens, a linked table (up to the three-table cap), a board, a quick-update form, or a public form. - **Changing and removing**: rename a field, remove a field, remove a page (screen), edit which status values a workflow field may move between, and revoke a capability the app holds (the card names everything the revocation takes with it — for example, revoking public capture kills the public link). Removals are referentially protected and refuse honestly rather than half-working: you cannot remove a table's only page (every table needs one), and an app always keeps at least one page. What the loop still will not do is restructure data underneath you — for that, the app's own settings page and the Power Tables / Live Boards surfaces remain the home of bulk operations, with the same referential warnings. ### Template vs. copy Starting from a template compiles a **copy**. There is no upgrade tie back to the source: a template is a starting shape, and from the moment you approve it the app is yours to change. The app's settings page says exactly this, naming the template it came from. Two sources feed the Templates shelf, and both render on the same approval card and pass the same validation, so where a plan came from never changes what it is allowed to contain: - **Platform mini-app templates** — the curated gallery (Inventory, Equipment Loans, Goods-In Log, Temperature Log, and the rest), each a full working shape: tables, views, automations, screens, and any capabilities, disclosed on the card like any draft. - **Your own mini apps** — the mini apps in your tenant that you can open (App Builder admins see all of them) appear under "Your mini apps" as a start-from shape. Using one compiles an independent copy (name suffixed "(copy)"); the original is never touched by anything you do to the copy. Bare column sets are no longer offered on this shelf: a table on its own belongs to Power Tables, whose new-table flow has its own templates. ### Who owns an object after you change it Every object a mini app stamps is a real platform object, and you can manage it in Power Tables or Live Boards directly. What you do there decides who owns it: - **Renaming is always free.** Views, automations, and the board reference fields by ID, never by name, so a rename never breaks anything and is never overwritten by an upgrade. - **Archiving is not divergence.** An archived object still resolves, so upgrades continue normally. - **Hard-deleting an object the app created keeps it deleted.** Updates only ever add pieces, so a future release never resurrects something you deliberately removed, and the rest of the app keeps upgrading normally. The app's settings page says so. To get a removed piece back, ask for it in the app's edit loop (**Edit with AI**) — turning the app off and on again does not re-create it. ### Build sessions (custom apps) Every time you describe a new custom app or reopen an existing one, you work inside a build session. The session holds the conversation with the AI agent, all generated files, and up to 10 version snapshots you can restore. A session progresses through phases: planning → plan review → building → verifying → ready to deploy → deployed. Each session belongs to one business, but co-admins can reopen a deployed app's session — the session is tied to the app, not the person who started it. ### Plan → approve → build (custom apps) The builder never writes code without approval. It drafts a plan showing record types, screens, workflows, and the capabilities the app will declare, then pauses. You can approve, request changes with feedback (the agent revises and re-presents), edit the plan inline, or cancel to describe something different. If the builder detects that a similar app already exists in the business, it pauses and asks whether to update the existing app or build a new one. ### Complexity tiers and the iteration cap The builder classifies each request as Simple, Medium, or Rich based on the number of record types, workflows, and widgets you describe. Every build turn runs under the same iteration cap regardless of tier; what the tier governs is **auto-continue**. When a build hits the cap mid-flight, Medium and Rich builds can extend themselves automatically (up to 2 extra rounds) if the **Auto-continue long builds** setting is on. Simple builds always pause and wait for you to click **Continue**. Exact numbers are in the FAQ. ### Templates Reusable starting points. The Templates tab carries mini-app templates at the top and coded-app templates below, in three kinds: - *System templates* — curated starters shipped with the platform, organised into categories like Getting Started, CRUD / Data Management, HR & People, Automation & Workflows, Dashboard Widgets, and Ask AI Agents. - *Business templates* — templates your team saved from successful builds or created manually via the drawer form on the Templates page. - *Central library imports* — templates imported from the MangoApps gallery. They arrive as unpublished drafts for review before use. Example: your HR team describes "a tracker for new-hire equipment requests with an approval step and a dashboard showing pending items." The approval step makes this a custom app rather than a mini app. The builder classifies it as Medium, drafts a plan with two record types (Equipment Request, Equipment Item), an approval workflow, and a dashboard widget, then pauses. The admin approves, the agent builds, and after deploy the app appears at `/apps/ext/new-hire-equipment`. The admin saves it as a business template so another location's admin can start from it. ### Deployed apps vs. the builder A deployed custom app runs independently at its own URL with its own records, settings, and audience. It also has mobile views at `/m/apps/ext/` and can expose public submission forms via a shareable link (no login required). Reopening it in the builder loads the deployed files into a session so you can edit or extend it, but changes do not go live until you deploy again. The builder plans, builds, and deploys; the running app serves users. ### Records and data Each built custom app stores its data as records, scoped to your business. Records support file attachments (up to 10 files per record, 10 MB each), platform comments, evidence capture (photo, video, voice with GPS and timestamp), and an audit timeline showing who changed what. Records can also host Live Assist video sessions if that capability is enabled for the app. A mini app's records are Power Tables rows, with that app's own change log, search, filters, and import. ### Platform capabilities Built custom apps run inside the OneMango SDK sandbox and can only use capabilities they declare. The platform validates those declarations at deploy time. Available capabilities include notifications, approvals, tasks, e-signatures, comments, automation, scheduled jobs, AI features, feed integration, incoming webhooks, document generation, geocoding, HTTP access, and cross-app interop. A built app can read your real people, locations, departments, and schedules through declared capabilities — but only what its declaration permits, and only its own business's data. ### What a mini app's automations may do — and may not A mini app's automations run on a deliberately bounded palette, in two tiers. The **base palette** — always available — is: **update a field on the record**, **notify a person**, **open a task**, and **send a digest** (one summary message for everything a saved view currently matches, on a schedule). Triggers are **a record was created**, **a field changed**, and **on a schedule** — so "remind the assignee every Monday about anything still open" and "alert me before these expire" are both expressible, the second as a scheduled digest bound to a saved view filtered to the expiry window. Recipients come from a fixed vocabulary, never a free list: the person who filed the record, the person who created the app, a person-field on the record (an assignee), that person's manager, a role (admins, managers, members), or a team. The **capability tier** adds four grants that only exist if the approval card disclosed them and you approved: - **Send email** — to an email-address field stored on the record (one address, rate-capped per hour). This is how a mini app confirms something to an outside contact; it can never email an arbitrary list. - **Request approval** — pauses on a named approver's real approval; what happens on approve and on decline is part of the plan you read. - **Public capture** — a public form at a tokened link, so people without accounts can submit records (see the public capture concept below). - **Kiosk capture** — a shared-tablet kiosk at a tokened link: an employee taps their badge on the tablet's reader (or scans the code on it), fills in the kiosk's own fields, and the record is written as them — no sign-in, no PIN (see badge tap and kiosks below). A revocation is a first-class edit: "remove the public link ability" drafts a card that names everything the revocation takes with it. What remains off the palette entirely: webhooks, deleting or archiving rows, invoking AI, and nesting an approval inside an approval. **Tables:** a plan may hold up to **three linked tables** — the drafter links them with reference fields (a stay points at its pet, a pet at its owner) and every table gets its own page. Describe more entities than fit and it **folds** the extras into fields on an existing table and says so on the card in plain words, rather than declining. Power Tables itself still carries the fuller admin palette (including webhooks), and a mini app's table is an ordinary Power Table, so that door stays open. ### Workflow transitions (governed status fields) A choice field can carry **transitions**: which status values may move to which. Once governed, the machine is enforced for *every* writer — the grid, the drawer, mobile, the quick-update door, form submissions, board drags, and the app's own automations all obey the same rules, so "Received can only move to Inspected or Rejected" is a fact about the data, not a hope about the UI. Values you add later but do not govern stay free, so adding an option can never brick the field. ### Public capture and the printed-QR contract An app with the **public capture** grant serves a public form at a tokened link — contractors requesting site visits, suppliers logging a delivery — no account needed. Three facts to plan around: - The link is **findable in the app's settings**, and submissions are honeypot-protected and rate-capped per business per hour. - Fields the app's own automations write (a governed Status, for instance) are **never offered on the public form** — outsiders state facts; the app decides workflow. - **Revoking the grant kills the link; re-granting revives the SAME link.** The token survives revocation on purpose, so a QR code you printed and taped to the gate is not garbage after a pause-and-resume. ### Badge tap and kiosks Any **person field** can be set to **identify by badge tap** (a column setting; the composer's plan carries it as `badge: true`). The record form then shows a badge box above the people picker: a tap on a USB or Bluetooth badge reader — or a camera scan of the barcode/QR printed on the badge — fills in the person from the **Badge ID** on their profile. A badge counts only when it matches that profile field, which admins fill by tap (the profile's Badge ID box accepts a tap) or through the user import (`badge_number`, `card_number`, `prox_id`…). QR-coded badges whose code is a URL or JSON are unwrapped to the badge number automatically. An app with the **kiosk capture** grant also serves a **kiosk** — a shared-tablet page at a tokened link you open once on the tablet: *tap your badge → pick what applies → Done*, then the screen resets for the next person. Four facts to plan around: - The kiosk is **badge only**: an employee number typed at the tablet is refused, because a number is printed on paperwork while a badge has to be in hand. The tap answers a two-minute step token, and the record is written as the badge's owner — the person field and the change history both name them. - The kiosk's fields are the same anonymous-safe types a public form allows (text, number, counter, choice, date); the person field is filled by the tap and is never a form field. - The link is **findable in the app's settings** (copy it, replace it, or turn the kiosk off) and, like the public link, the token survives a pause so re-enabling revives the same tablets. Lookups and writes are rate-capped per tablet and per business. - A kiosk is declared when the app is composed or comes from a template (**Cafeteria Meal Log** ships one); the edit loop cannot add a kiosk to an existing app yet. ### Adding an existing table to a mini app The promote flow has a second form: a Power Tables owner can **add their existing table to a mini app** they can see, instead of minting a new app around it. The table keeps its data and origin, the app grows a page for it, and the app's users find it in the app's own navigation. This is how a table that grew up in Power Tables joins the app your team actually opens. ### Health tracking Each deployed custom app has a health status: Healthy, Failed validation, Failed to load, Failed at runtime, or Quarantined. The **Your apps** tab badges unhealthy apps, and the Home page shows both the total deployed count and the number that are not loading. Mini apps have no deploy step and therefore no health status; if a stamping step fails, the app repairs itself in the background and shows a "still being set up" state until it is ready. ### Who can do what App Builder itself has three tiers: - **Authoring tier — full administrators only** (admin or above). Build and deploy custom apps, manage API keys, and change Settings. - **Composer tier — governed by the "Who can create mini apps" setting.** Compose a mini app, edit one, and start one from a template. The default admits everyone with the **Manager role** (plus admins and app-admins); a tenant can add people who run a team (**Managers and admins, plus anyone with direct reports**), widen it to everyone or narrow it to app-admins only. Composer-tier users see Home, Templates and **Your apps**, which lists the mini apps they created. Each row offers **Edit with AI** (where the app's **Turn off** lives); an unpublished app adds **Ask an admin to publish** and **Remove**; a live one adds **Tell the team**; one turned off from App Builder adds **Turn on** and **Remove**; one whose setup failed adds **Retry setup** and **Remove**. A live app's row offers no **Remove**. They see nothing of the code-build surfaces. - **Monitoring tier — a delegated app-admin** (granted per app from Admin → Apps → All Apps) or any global admin. Sees Home, Your apps, Templates, and Analytics, and publishes, unpublishes and retires apps from Your apps. No code builds, and no Settings. Each **mini app is its own marketplace app**, so it has its own two roles on top of the above: - **Mini app admin** — someone holding an app-admin grant on *that* mini app, or a Power Tables admin. Can open the app's settings, rename its vocabulary, print QR labels, and switch the app off. - **Mini app user** — anyone the mini app is published to. Note that this is the *mini app's* own audience, not Power Tables'. A member with no Power Tables data access can still open the mini app: they get the quick-update door and an honest notice explaining what they cannot see, never a silently empty grid. Members never see App Builder itself. They interact only with the apps it produces. ## 4. Running it ### Creating a mini app 1. Go to **Apps → App Builder** and click **Create a mini app** (or open **Compose** directly). 2. Describe what you need to track, in a sentence or two. Example: *"We lend out projectors and cameras — track who borrowed what, when it's due back, and flag overdue gear."* 3. Click **Draft my app**. One of three things comes back: - **A plan**, rendered as an approval card listing the fields with their types, the saved views and what they filter to, the automations and what they do, the board, and the quick-update form. - **A recommendation**, when what you described is already a real OneMango app. The AI will not compose a toy version of payroll, scheduling, ticketing, chat, forms, or learning — it points you at the real product instead. - **A decline**, with the reason, when the ask needs an external integration or is not a record-tracking need at all. An ask that is merely *big* is folded rather than declined: up to three linked tables, with anything beyond that folded into fields — and the card says where the extras went. 4. Read the card. If it is not right, edit your description and draft again — nothing exists yet. If it is right, click **Approve & create app**. 5. The app is live. You land on it, and it is in the launcher for your members. Drafts you do not approve are saved automatically, so navigating away does not lose the work. Resume or discard them from the **Your open drafts** card on the compose page. ### Starting a mini app from a template From **Templates**, the **Mini app templates** shelf lists the platform's full app templates — fields, views, automations and board — and, under **Your mini apps**, your organization's own mini apps that you can open (App Builder admins see all of them), each offered as a copy with its own records. Bare tables are not offered here; start one from Power Tables' own templates when you create a table. Click **Use** on one and it renders on the same approval card, prefilled. Approve it as-is or discard it and draft your own. Remember that this compiles a copy — from that point on it is yours and template updates do not apply. ### Editing a mini app Open the app and choose **Edit with AI**, or open it from **App Builder → Your apps** (its creator sees the apps they built there; App Builder admins see them all). Describe the change — add a field, a view, an automation, a page, or a board or quick-update form if the app has none; rename or remove a field; remove a page; or take back a capability. The proposed change renders on its own card for approval, and applying it bumps the app's version. A removal refuses when something still uses what you are removing. Bulk restructuring — splitting a table, moving data between tables — is not something the edit loop does; the app's own **App settings** (fields, views, imports) is the place for those. ### Using a mini app day to day - **Records tab** — the full grid, with search, filters, sorting, and the app's saved views as navigation pills. - **Board tab** — the live board, if the app has one. It respects any audience you later set on the board in Live Boards. - **The quick-update door** — a narrow "report a value" form. The person identifies one record by its code and enters the new number; the confirmation names the record and shows the movement (for example, `12 → 9`), and an optional note lands in that row's change log. It cannot create records, browse the table, or be pointed at a different table — which is exactly why it is safe to give to someone with no access to the underlying data. - **Print QR labels** — from the **Manage** menu, a printable sheet of one QR code per record. Scanning a label opens that record's mobile card with − / + steppers, so a phone camera is the only hardware anyone needs. - **App settings** — fields and where they came from, vocabulary (rename "records" to whatever your business calls them), the list of everything the app manages, the **public capture link** (when the app holds that grant — copy it, rotate the token, or print it as a QR), the **kiosk link** (when the app holds the kiosk capture grant — open it on the shared tablet, replace it, or turn the kiosk off), and the on/off switch. Turning the app off hides it for everyone; the data is untouched and the settings page stays reachable so you can turn it back on. ### Starting a custom app build 1. Go to **Apps → App Builder** and click **Build a custom app**. 2. Type what you want or pick a template. You can also attach images (screenshots, wireframes) to show the agent what you have in mind. 3. The agent drafts a plan and pauses. Review it, then **Approve**, **Request changes** (with feedback), or **Cancel plan** to start over with a different idea. 4. Once approved, the agent builds the code. You can watch progress in real time, cancel mid-build, or click **Continue** if it pauses at the iteration limit. 5. When the status reads **Ready to deploy**, click **Deploy**. The deployer runs a security scan and file validation before anything goes live. If the files match the already-deployed version byte for byte, the deploy is skipped and you see "already up to date." ### Editing a deployed custom app Open a deployed app in the builder from the **Your apps** tab (click the row, then use **Edit with AI**) or from the builder's welcome screen. Describe what to change in the chat — the agent modifies the existing code in the same session. Changes are not live until you redeploy. You can also hand-edit individual files in the built-in code editor. The editor accepts `.rb`, `.erb`, `.json`, `.yml`, `.yaml`, `.css`, `.js`, `.txt`, and `.md` files. Ruby files are syntax-checked and security-scanned before saving. The version history panel lets you restore any of the last 10 saved snapshots. ### Fixing a failing custom app The **Your apps** tab shows each app's health status (Healthy, Failed to load, Quarantined, etc.). If an app is deployed but not loading, click **Retry load** to clear the error and ask the platform to reload it. If the problem is in the generated code, open the builder and click **Fix with AI** — the agent receives the error context and attempts a code-level fix. ### Saving and managing templates After a successful build, click **Save as template** in the builder to save the app's specification as a reusable business template. From the **Templates** tab you can also create templates from scratch, edit, or delete your business's own templates using the drawer form. System templates are read-only. To import templates from the central MangoApps gallery, click **Template Library** at the top of the Templates page. ### Reviewing build history **Build history** lists every custom-app build session in the business, reachable from **Your apps** and from the **Recent builds** card on Home. Filter by status (Draft, Generating, Ready to deploy, Deployed, Failed) or search by name. Each row links back into the builder to resume or inspect the session. Both Your apps and Build history support CSV export of the full filtered set. ### Viewing analytics The **Analytics** tab shows business-scoped numbers: - Deployed app count and records per app (total and last 30 days). - Build sessions in the last 30 days by status, with a deploy success rate (deployed vs. failed, excluding drafts and in-progress builds). - AI token spend attributed to the builder (limited to retained telemetry — the retention window is stated on the page). - Top templates used by this business, ranked by builds started. Analytics can be exported as CSV. All numbers are scoped to your business. ### Using the Ask AI agent Two agents divide this territory, and Ask AI routes your question to the right one: - The **App Builder agent** answers about *built custom apps*: it lists the custom apps this business has built and their deployment state, reports one app's health, shows a built app's deploy/enable/disable audit trail, and lists recent build sessions. As a full administrator you can also ask it to enable or disable a built app, which it confirms with you first. It cannot deploy, roll back, or delete an app, and it does not cover mini apps. - The **Mini Apps agent** answers about *composed mini apps*, for anyone the mini is published to: "what mini apps do we have", "what fields does the goods-in log capture", "how many vehicles are in the fleet list", record lookups and searches, and submitting a mini app's quick-update form (with confirmation). It respects each mini's own audience and each table's access — ask about a table you cannot see and it says so plainly instead of inventing an answer. ### Downloading and sharing built apps From an open build session you can download all generated files as a ZIP. Built custom apps can also be submitted to the community marketplace for other businesses to install — use the listing editor under **Admin → Apps & Integrations → Custom Apps** to manage the listing and submit for review. Mini apps are private to your tenant by design. They never appear in the public app directory or in another tenant's marketplace, and there is nothing to submit — publishing a mini app makes it live inside your own company only. ### API keys The builder includes an API key surface for programmatic access. Keys are business-scoped and carry scopes (builder, query, manage). A generated key is shown once — copy it immediately. Keys can be revoked but not re-displayed. ## 5. Settings App Builder's own settings are at **Apps → App Builder → Settings** (full administrators only). | Setting | Default | What it changes | |---|---|---| | **Auto-continue long builds** | On | When a Medium or Rich custom-app build hits its iteration limit mid-build, the builder automatically extends it (up to 2 extra rounds) instead of pausing. Turn off to review progress before each extension. | | **Alert on health problems** | On | Sends a notification when a built app is quarantined, fails to load, has an event handler suspended, or has an auto-update rolled back. Alerts are deduplicated per app per event — at most one every 6 hours. | | **Alert when a marketplace-installed app has an update** | On | Sends a notification when a newer published version of an app your business installed from the marketplace can be applied. Apps built here raise no update alert — a built app changes when you redeploy it. Informational only — at most one per new version. | | **Additional notification recipients** | None (the app's builder + App Builder admins only) | Widens built-app alerts to an additional admin-configured recipient group. Without a builder or group, alerts fall to the business's App Builder admins — or, if none are designated, to every administrator. | All four settings concern custom-app builds. They do not affect mini apps, which have no build job, no iteration limit, and no deploy step. One more setting on this tab, in its **Who can build** card: **Who can create mini apps** — the composer tier. **App admins only** (global admins plus App Builder app-admins), **Anyone with the Manager role or above** (the default), **People managers — anyone with direct reports**, **Managers and admins, plus anyone with direct reports** (both, so a team lead with the Member role is let in without leaving a manager out), **Everyone with access to the app**, or **Specific people — choose groups below**. It is not on the generic configure page. Whichever value is set, every created app is visible in App Builder's register. Per-app settings live on each app's own settings page, not here — record visibility, notifications, and automations for a custom app; fields, vocabulary, and the on/off switch for a mini app. Enabling App Builder and publishing it to people happen in Admin → Apps → All Apps. Who can use it follows this page: full administrators and App Builder app-admins always can, and everyone else only if **Who can create mini apps** lets them in — and it appears in their app launcher only once App Builder is published to them. ## 6. More help - **App Builder FAQ** — specific setup and operating questions, exact limits, troubleshooting, and allowed ranges for settings. - **Admin → Apps & Integrations → Custom Apps** — the platform-level registry of all deployed custom apps, including community marketplace installs. - **Power Tables** and **Live Boards** — the engines a mini app's records and board are built on. A mini app needs neither turned on: its fields, views, rules, imports and board are managed from the app's own **App settings**. - Ask AI — the assistant answers questions about App Builder and your deployed custom apps from any page, without opening the app. **Keywords:** app builder, mini app, composed app, compose an app, custom app, build an app, plugin, no code, ai builder, custom tracker, custom form, build with ai, deploy app, plugin template, built app, app builder template, approval card, quick update, public form, public capture, kiosk, badge tap, badge reader, qr code, approval workflow, linked tables, multi-table, workflow transitions, reference field, who can create mini apps, composer access, app-builder, app_builder --- # App Launcher & Sign-in Tiles **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-16 Give each person one place to open the other apps they use — Workday, ADP, Salesforce, your EHR — with tiles that sign them in through Okta, Microsoft Entra ID or OneLogin. Where the tiles show, where they come from, and how to add your own. # App Launcher & Sign-in Tiles ## 1. What it is The app launcher is the one list of everything a person can open from OneMango: the OneMango apps they have, the shortcuts you add, and the other apps your company's identity provider gives them. A **sign-in tile** opens another app — Workday, ADP, Salesforce, your EHR — already signed in, in a new tab, through your identity provider. This is what MangoApps Classic called the SSO widget. The same list, filtered for each person, shows in: - the **App Launcher** card on the Home dashboard, which lists each person's other apps grouped by category (OneMango's own apps are on the **More apps** card); - the **Quick Actions** widget on the home dashboard (people choose their own tiles); - the **Apps** page; - the phone's **Apps** grid and **More** menu; - **search** and Ask AI's navigation answers; - a **Sites page**, through the Quick Links block set to each reader's apps. **Enablement:** built into the platform — no app to license. Admins and super admins manage it. ## 2. Where the tiles come from | Source | Who sees a tile | Set up at | |---|---|---| | OneMango apps | Everyone who can open that app | Automatic | | Shortcuts you add | Everyone, or only certain job titles, locations or groups | **Admin → Organization → Quick Action Shortcuts** | | Apps your identity provider assigns | Each person sees the apps assigned to them there | **Admin → Integrations → Identity Providers** | | Apps OneMango signs people in to itself | Everyone, or only certain job titles, locations or groups | **Admin → Integrations → Identity Providers → Manage apps** | When two tiles point at the same address or share a name, people see one: your shortcut wins over the identity provider's app. ## 3. Add a sign-in tile yourself Use this for an app your identity provider doesn't list, or when you want to choose exactly who sees it. 1. In your identity provider, copy the app's sign-in link: - **Okta:** the app's **App Embed Link** (Applications → the app → General). - **Microsoft Entra ID:** the app's **User access URL** (Enterprise applications → the app → Properties). - **OneLogin:** `https://.onelogin.com/launch/`. 2. Go to **Admin → Organization → Quick Action Shortcuts** and click **Add shortcut**. 3. Paste the link as the **Destination**, and set **Opens in** to **Sign in through your identity provider (new tab)**. 4. Leave **App logo** on **Automatic**: when the destination is a well-known app (Workday, ADP, UKG, Salesforce, ServiceNow and about 200 more), the tile shows its logo, and the choice names the app it matched. Pick another app, or **No logo**, to change it. For an app that isn't listed, add a picture under **Your own logo** — a square picture works best. Without any logo, the tile shows the **Icon**. 5. Choose where it shows (**Quick Actions widget**, **App launcher**, **Search and Ask AI**), a **Category** for the launcher, and, if it is not for everyone, the job titles, locations or groups that should see it. 6. Save. People who are already signed in to your identity provider go straight into the app. Anyone who isn't signs in there first. ## 4. Show the apps your identity provider assigns Connect the provider once and each person's assigned apps appear on their own, with the provider's logos. - **Okta or Microsoft Entra ID connected for user sync:** open the connection under **Admin → Integrations → Identity Providers** and turn on **App launcher** in its capabilities. - **Okta, Microsoft Entra ID or OneLogin connected by SCIM provisioning:** open the SCIM connection and fill in its **App launcher** card with the provider's API credentials — read access to users and apps is enough, and the card says which permission each provider needs. Click **Save and test**, then switch on **Show the apps … assigns each person**. Provisioning is not affected. Then choose the **Launcher category** the apps are filed under, and whether they show in the launcher, in search, or both. Each person's list refreshes when they sign in and at least every 12 hours. With Okta's event hook set up on the connection, a change to someone's apps in Okta reaches OneMango straight away. ## 5. Put the tiles in front of people - **Home dashboard:** the **App Launcher** card is on every Home dashboard. Each person sees all of their other apps there — your shortcuts set to show in the launcher, the apps OneMango signs them in to, and the apps your identity provider assigns them — with no limit and nothing for them to set up. Someone with no other app doesn't see the card. Move or remove it in **Admin → Dashboard Builder**. - **Quick Actions:** shows up to nine tiles for things people do often. Your shortcuts lead by default (up to four), and people can add any other tile from **Customize**, including the apps in the App Launcher. - **A Sites page:** add a **Quick Links** block and set its links to come from **each reader's apps**. Every reader sees their own tiles; people who aren't signed in see nothing. - **Phone:** the Apps grid and More menu show the same list, and the Quick Actions widget shows the same tiles as on desktop. ## 6. Troubleshooting - **A shortcut doesn't show for someone.** Check it is **Visible**, lists the surface you're looking at, and that the person matches every targeting rule (job title *and* location *and* group). A shortcut that names a required app hides for anyone who can't open that app. - **Identity-provider apps are missing.** Check the connection is active, **App launcher** is on, and its credentials are filled in. The person must exist in the provider with the same email address, or be linked through the connection's sync. A newly assigned app can take up to 12 hours to appear unless the person signs in again. - **The tile shows an icon instead of the logo.** The destination isn't a well-known app (pick one under **App logo**, or add **Your own logo**), the logo was archived or removed from the Asset Library, or the picture failed to load. - **The tile opens the provider's sign-in page.** The person isn't signed in to your identity provider in that browser. After they sign in, the app opens. ## 7. Let OneMango sign people in to an app itself With no Okta, Microsoft Entra ID or OneLogin, OneMango can be the identity provider for an app that accepts SAML sign-in — Salesforce, Zendesk, Workday, Box and most business apps. 1. Go to **Admin → Integrations → Identity Providers** and click **Manage apps** under **Apps people sign in to through OneMango**. 2. Copy OneMango's values from the top of that page into the app's single sign-on (SAML) setup: the **Metadata** address (most apps read everything from it), or the **entity ID**, **Sign-in URL** and **Signing certificate**. 3. Click **Add an app**. Paste the app's own SAML metadata, or type its **entity ID** and the address where it receives sign-ins (its ACS URL). 4. Choose how the app knows each person — **Email address**, **Employee number**, **OneMango employee ID**, or **An ID only this app sees** — and which facts it is told (name, job title and so on). 5. Choose who may sign in (everyone, or certain groups, job titles or sites), set **Status** to **On**, and save. **Try it** signs you in as yourself in a new tab. People in the app's audience see its tile wherever the launcher shows, and an app that sends people to OneMango to sign in gets them back signed in. Anyone else is refused with a message that says why. Someone without the fact the app identifies people by (many frontline people have no email address) is told what is missing instead of being signed in. Every sign-in, and every refusal, appears under **Admin → SSO Logs**. Each organization signs with its own certificate, valid for five years; its fingerprint and expiry date are on the same page. ## 8. Open a page inside an app A shortcut can sign people in to one of the apps OneMango signs them in to (section 7) and open a particular page there — a Salesforce report, a Zendesk view, a ServiceNow queue. 1. Go to **Admin → Organization → Quick Action Shortcuts** and click **Add shortcut**. 2. Under **Sign people in to**, choose the app. 3. Paste the page's full address as the **Destination**. It must be on the app's own site — for an app that receives sign-ins at `acme.my.salesforce.com`, any address on `salesforce.com`. 4. Choose where it shows and who sees it, and save. The tile signs the person in and tells the app to open that page. It shows only to people who can sign in to the app, and the page always comes from the saved shortcut. Some apps ignore the page they are given and open their home page instead, so open the tile once after saving. For an app you sign in to through Okta, Microsoft Entra ID or OneLogin, use the page's address as an ordinary shortcut: the app sends the person to your identity provider and back to that page. **Keywords:** app launcher, SSO widget, SSO apps, single sign-on apps, enterprise apps, my apps, sign-in tiles, quick links, quick action shortcuts, company links, more apps widget, app launcher widget, my enterprise apps, deep link, open a page in an app, Okta apps, Okta dashboard, Microsoft My Apps, Entra ID apps, OneLogin apps, app logos, third-party apps, OneMango as identity provider, SAML identity provider --- # Appointment Scheduler App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run Appointment Scheduler — booking pages, meeting types, availability rules, team scheduling, and the public /meet surface. # Appointment Scheduler ## 1. What it is Appointment Scheduler lets employees publish booking pages at `/meet/` on your workspace domain. Invitees — external customers, candidates, vendors, or colleagues — pick a genuinely free slot and the meeting lands on the host's calendar automatically, with no back-and-forth email. - **Enablement:** Appointment Scheduler requires a license. An admin enables it from Admin → Apps → All Apps; it is off by default. - **What it is not:** Appointment Scheduler is the external-facing booking surface. It is not Interview Scheduler (which coordinates multi-round interview panels tied to Job Board applicants) and it is not the Calendar app (which manages internal events and recurring meetings). ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Appointment Scheduler**. Grant access to the users or groups who will host booking pages. 2. Go to **Apps → Appointment Scheduler → Settings**. Review the defaults — every switch is on except SMS reminders, and anyone with access to the app may publish pages people outside the organization can book. These settings apply to the whole workspace. Hosts can't change them, with one exception: each meeting type can set its own reminder lead time in place of the workspace default. 3. Have each host go to **Apps → Appointment Scheduler → Booking Pages** and create a page. A new page starts with a default "30 minute meeting" type and Monday–Friday 9:00–17:00 availability in the host's timezone. 4. The host edits their page to add or rename meeting types, adjust weekly availability windows, and set any date overrides (days off, custom hours). 5. Share the page's public link — `https:///meet/` — or embed it on an external website. Invitees can now book. **What silently blocks bookings:** a booking page with no active meeting type, or one that has expired, shows as "unavailable" even when active. If the workspace's **Allow booking via public /meet pages (applies to everyone, including colleagues)** setting is off, every booking page in the business shows as unavailable — to signed-in colleagues as well as outside invitees. ## 3. How it fits together **Booking page** — the published surface an invitee visits. Each page has an owner, a URL slug (unique per business), a timezone, and a visibility setting. A page can be solo (one host) or team (multiple hosts sharing one link). The page form offers three visibility choices: - **Link only — not listed anywhere** (the default) — anyone with the link can book, and the page isn't listed in the Directory or on your profile. - **Listed in the org directory** — the page appears in the in-app Directory, and anyone with the link can still book it, signed in or not. A solo page can also be what the **Book time** button on your profile and people-search card opens; a team page is listed in the Directory only, marked as a team page, because any teammate may host the booking. - **Listed internally — invitees must sign in to book** — listed in the same places, but only a signed-in member of your organization can book it. An admin can limit who may publish pages that people outside the organization can book (Settings → **Who can publish booking pages people outside the organization can book?**); for anyone that setting leaves out, the first two choices are locked in the page form and a new page starts as **Listed internally**. A page that already takes outside bookings keeps its setting, and its owner can still take it out of the directory (Link only) or list it internally. **Meeting type** — a bookable kind of meeting on a page ("30-min intro call", "60-min consult"). Each type carries its own duration, location mode (virtual, physical, or phone), buffer times, minimum notice period, booking window, and optional daily cap. A page can have several types; the invitee picks one before choosing a time. The default duration is 30 minutes, the default booking window is 60 days, and the default minimum notice is 4 hours. **Availability** — two layers control when a host's slots are offered: - **Weekly rules** — recurring windows per weekday (e.g. "Monday 9:00–12:00 and 13:00–17:00"). A new page starts with Monday–Friday 9:00–17:00. - **Date overrides** — a specific date that is either closed entirely or open with custom hours, replacing the weekly rules for that day. Busy time from the host's calendar, synced Google events, Outlook free/busy (via Microsoft Graph), approved leave, and confirmed appointments is subtracted automatically. The invitee only sees times that are genuinely free. **Assignment mode** — governs how a meeting type distributes bookings across hosts on a team page: - **Solo** — one host; the page owner. - **Round robin** — the invitee sees the union of every member's free time. The booking is assigned to the member who was assigned longest ago (rotation). A member who has hit the daily cap drops out of the rotation for that day. - **Collective** — every member must be free at the same time. All members attend the meeting. - **Group** — one host offers a session with a seat capacity (2–500 seats). When a session is full, invitees can join a waitlist; they are emailed if a cancellation frees a seat. A worked example: a 3-person Sales team creates a team booking page with a "30-min demo" meeting type in round-robin mode. A prospect visits `/meet/sales-demo`, sees all times where at least one team member is free, and picks Tuesday at 2 PM. The platform assigns the booking to the team member whose last assignment was the oldest — say, Jamie — re-checks Jamie's availability for conflicts (live, for an Outlook calendar), creates the calendar event, sends the prospect a confirmation email with a calendar attachment, and notifies Jamie. If Jamie had hit the daily cap, the next member in rotation would have received it. **Calendar integration** — every confirmed booking creates a calendar event on the host's calendar. Virtual meetings use the host's saved meeting-link provider (Zoom, Teams, etc.); if no link is saved, the event falls back to a physical-mode event the host can update. Collective bookings add every team member as an attendee so the meeting lands on all their calendars. **Routing** — a booking page can display a routing question before any slots. Each answer option redirects the invitee to a different booking page (up to 10 options). This steers invitees to the right host or team without requiring them to know your internal structure. Options that point at a deactivated or deleted page are automatically hidden from invitees. **Branding and embedding** — each booking page can carry a custom logo URL, accent color, and welcome message. Hosts can list up to 10 external domains (bare hostnames like `example.com`) that are allowed to embed the page in an iframe. The CSP header is extended only for those domains. **Custom questions** — each meeting type can ask the invitee its own intake questions. Open the meeting type, expand **Questions for the invitee**, and choose **Add question**: give it a label, pick a short answer, a paragraph, a drop-down (one choice per line) or a checkbox (a required checkbox must be ticked to book), and tick **Required** if it must be answered. Required questions are enforced when the invitee books; the answers appear on the appointment detail page and in the description of the host's calendar event. Editing a question's wording keeps the answers already given attached to it. **Integrations that fire automatically on booking:** - **Bookings (room reserve)** — a physical meeting type can auto-reserve a linked Space from the Bookings app. The room is released on cancellation. - **Guest Pass (visitor pre-registration)** — a physical meeting type can pre-register the invitee as a Guest Pass visitor, so reception expects them on arrival. The visit follows your Guest Pass approval settings, and the host is notified when it needs approval. If your Guest Pass settings let hosts approve their own visitors and a reschedule gives the meeting to a different host, an approved visit goes back to pending for the new host unless they gave that approval themselves — an approval from the previous host, or from a host reception had assigned, doesn't carry over. The exceptions: an approval from a Guest Pass approver in their own right (someone Guest Pass's **Who can approve a visitor?** setting names — managers and above by default — or a Guest Pass app admin) carries over, and the new host's own auto-approve setting approves the visit for them. - **Mango CS (CRM link)** — when the invitee's email domain or contact record uniquely matches a CRM account, the booking is linked and a meeting activity appears on the account timeline. - **Internal invitee recognition** — when a colleague books while signed in with their own work email, the meeting also lands on their calendar and they receive an in-app notification with a manage link. Booking on someone else's behalf doesn't do this: that person gets the confirmation email like any other invitee. ## 4. Running it ### Creating and editing booking pages Go to **Apps → Appointment Scheduler → Booking Pages**. New pages open in a drawer; the full-page editor opens after creation. In the editor, configure meeting types, weekly availability, date overrides, team members (for team pages), and routing. Duplicate a page to copy all its settings, types, availability, and membership as an inactive draft. A page with upcoming appointments cannot be deleted — deactivate it instead. A page with any appointment history (including past or cancelled) cannot be hard-deleted at all; deactivation is the graceful retirement path. Only a page's owner, or an admin, can open its editor. The editor's **Team** card marks anyone who **Can't open Appointment Scheduler**: invitees can still book them, but they can't see or manage those appointments until they're given access to the app or removed from the team. ### Hosting on a colleague's team page When a colleague adds you to their team page, you get a notification, and your **Dashboard** (and the mobile app) lists the page under **Team pages you host on**, with the weekly hours set for you and a **Leave team** button. You can change your own hours there yourself: **Set my hours** next to the page opens your weekly hours and date overrides for that page (on the phone too). Everything else about the page stays with its owner or an Appointment Scheduler admin in the page editor. Leaving stops new bookings from that page; appointments already booked with you stay yours. If fewer than two people are left, the page goes back to solo scheduling and its round-robin and collective meeting types switch to a single host. The owner is notified. ### Reviewing and managing appointments Go to **Apps → Appointment Scheduler → Appointments**. Three tabs: **Upcoming** (confirmed, including in-progress), **Past** (completed and no-shows), and **Cancelled** (cancelled and rescheduled originals). Search by invitee name or email, or filter by booking page. Export the filtered list as CSV. The list shows the meetings you host, every booking on pages you own (including ones round-robin, collective or group assignment gave to a teammate), and collective meetings you attend as a co-host. Admins and app-admins see every appointment in the business. The CSV export, the Dashboard's upcoming list and Analytics cover the same appointments. The **My Appointments** widget on your home dashboard counts only the meetings you host or co-host and opens the list narrowed to them; **Show all** widens it again. From an appointment's detail page, its host, the owner of its booking page, or an admin can: - Cancel — the invitee receives a cancellation email and the calendar event is removed. - Reschedule — pick a new time from the same page's live availability. The invitee receives a dedicated "appointment moved" email naming the time it moved from, or a plain confirmation for the new time when an admin has turned that email off in Settings. Either email updates the entry already on their calendar, so the old time is never left behind. - Mark no-show / clear no-show — record whether the invitee attended (past confirmed appointments only). This is bookkeeping only; no email is sent. Clearing a no-show within 3 days of the meeting lets its follow-up note go out if it has not been sent yet. The other hosts of a collective meeting can open it but can't change it — they don't see these controls or the invitee's self-service link. Bulk cancel is available from the list view (up to 100 at a time) for the appointments you can change. In Ask AI, "my appointments" means the meetings you host or co-host, and "my booking pages" the pages you own or are on the team of — for admins too, who can still open any appointment by its ID. ### Invitee self-service Every confirmation email includes a secure manage link. The invitee can cancel or reschedule from that link without signing in. The link keeps working even if an admin turns off public booking: the invitee can still cancel, but can't move the booking themselves until public booking is back on. ### Email lifecycle The app sends these emails to invitees: - **Confirmation** — sent on booking, with a calendar attachment (ICS). Includes the host's meeting link (for virtual) or location, the invitee's answers, and the manage link. - **Reminder** — sent at the configured lead time (default 24 hours), with the same calendar attachment. The host gets the same reminder in their inbox, by email and as a push notification. - **Rescheduled** — sent when a booking is moved, while **Send a dedicated "appointment moved" email on reschedule** is on. It names the time the meeting moved from and carries one calendar update that moves the invitee's existing entry to the new time. With the setting off, the invitee gets a plain confirmation for the new time instead, which updates the same entry. - **Cancellation** — sent when a booking is cancelled, with a calendar cancellation that removes the entry. - **Follow-up** — sent after the meeting ends, but only when the meeting type carries a follow-up note. The note is the opt-in; there is no separate toggle. No calendar attachment. A 12-hour minimum age gives the host time to mark a no-show before the thank-you goes out. - **Waitlist emails** (group sessions only, no calendar attachment) — one confirming the invitee joined the waitlist, with a link to leave it; one telling everyone waiting that a seat opened, with a link to book it; and one sent after the session starts if no seat opened for them. ### Monitoring with Analytics Go to **Apps → Appointment Scheduler → Analytics**. The dashboard covers the last 90 days and shows: upcoming count, completed count, cancellation rate, no-show rate, average booking lead time, bookings-per-week trend (8 weeks), and breakdowns by booking page, meeting type, host, and booking source. It counts the same appointments as your Appointments list; admins see the whole business. ### Using the Directory Go to **Apps → Appointment Scheduler → Directory**. This lists every active booking page in the business that is set to **Listed in the org directory** or **Listed internally**, searchable by page title or host name. Any app user can browse the directory and book a colleague — it is not admin-restricted. ### Shift-aware availability On the booking page editor, the page's owner can set a **Shift mode** that ties offered slots to each host's published shifts from the Shifts app: - **Constrain to shifts** — slots are only offered during the host's published shift times. Use this for frontline staff who should only take appointments when they are scheduled to work. - **Block during shifts** — the host's shift times are treated as busy. Use this for staff who should only take appointments outside their floor shifts. When no shift mode is set (the default), shifts are ignored and availability is governed entirely by the weekly rules and date overrides. ## 5. Settings All settings are at **Apps → Appointment Scheduler → Settings**. Only admins and app-admins can access this page. Each setting below is named exactly as it appears on the Settings page. | Setting | Default | What it changes | |---|---|---| | **Appointment Scheduler Agent (Ask AI)** | On | Lets the Appointment Scheduler agent answer booking questions in the Ask AI sidebar and, with confirmation, create booking pages, switch a page's link on or off, and cancel or reschedule appointments. It also turns on the "Describe it and let AI fill the form" bar on this app's forms. | | **Allow booking via public /meet pages (applies to everyone, including colleagues)** | On | When off, every booking page in this workspace shows as unavailable — to signed-in colleagues as well as outside invitees — and the colleague **Book time** buttons disappear from profiles, people search and the org directory. Anyone who already has a booking can still cancel it, but can no longer move it themselves. | | **Who can publish booking pages people outside the organization can book?** | Everyone with access to the app | Pages set to **Link only** or **Listed in the org directory** can be booked without signing in. People this policy leaves out can still publish pages listed internally, which invitees must sign in to book, and pages already open to outside bookings keep working. Appointment Scheduler admins can always publish either. | | **Send email reminders before appointments** | On | The invitee gets a reminder email, and the host gets the same reminder in their inbox, by email and as a push notification. SMS reminders and post-meeting follow-up emails are not affected — SMS has its own setting below, and a follow-up goes out only when the meeting type has a follow-up note. | | **Default hours before the appointment** | 24 | Between 1 and 168 hours (7 days); other values are adjusted to the nearest limit, and leaving the box empty saves 24. Applies to email and SMS reminders alike, and individual meeting types can override it. | | **Send SMS reminders to invitees who opt in** | Off | Works independently of email reminders. Requires the invitee to have given a phone number and ticked the opt-in on the booking form. Uses your business SMS quota, and no texts go out until SMS is set up for the workspace (Admin → General Settings → SMS Settings). | | **Treat approved leave as busy time** | On | Hosts on approved leave are never offered as available. Turn this off only if leave is not kept up to date in this workspace. | | **Send a dedicated “appointment moved” email on reschedule** | On | Names the change and shows the invitee the time it moved from. When off, they get a plain confirmation for the new time instead. Either email updates the entry already on their calendar — the old time is never left behind. | | **Notify a booking's other hosts and participants, not just the primary host** | On | Covers a collective meeting's other hosts, and anyone else added to a booking's calendar event — they get the booked, moved and cancelled notices too. With this off they are told nothing on any channel. (The meeting lands on their calendar either way.) | | **Alert hosts when part of a booking fails — unreadable availability, calendar, room, or Guest Pass** | On | Covers a host calendar we could not read (the slot was treated as free and booked anyway), a calendar event that was never created, a collective booking's co-hosts left off it, a failed room auto-reserve, and a Guest Pass visit that failed or stayed at the old time after a reschedule. With this off the host only sees it in the appointment's history. | ## 6. More help - **Appointment Scheduler FAQ** — specific setup and operating questions. - Ask AI — the assistant answers questions about Appointment Scheduler from these articles. **Keywords:** appointment scheduler, booking page, booking link, meet link, meeting type, scheduling link, availability, round robin, collective meeting, group session, waitlist, reschedule, public booking, external booking, embed booking page, team page, co-host, appointment-scheduler, appointment_scheduler --- # Appointment Scheduler FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Appointment Scheduler — for the admin running it. # Appointment Scheduler FAQ Answers to common setup and operating questions about Appointment Scheduler. For what the app is and how to set it up from scratch, see the [Appointment Scheduler Overview](/help/articles/appointment_scheduler_app_overview). --- ## Setup ## Do I need to configure anything before hosts can publish booking pages? Yes — two things. First, enable Appointment Scheduler in Admin → Apps → All Apps and grant access to the users or groups who will host pages. Second, check that the workspace-wide **Allow booking via public /meet pages (applies to everyone, including colleagues)** setting is on in **Apps → Appointment Scheduler → Settings** (it is on by default). If it is off, every booking page in your business shows as unavailable — to signed-in colleagues as well as outside invitees — even though individual pages are active. ## What are the default settings a new booking page starts with? A new page starts with visibility set to **Link only** (or **Listed internally**, when an admin has limited who may publish pages that people outside the organization can book and the creator is not among them), the owner's timezone, and a single "30 minute meeting" type with virtual location, no buffers, 4 hours minimum notice, and a 60-day booking window. Availability defaults to Monday–Friday 9:00 AM–5:00 PM. The host can change all of these in the page editor. ## Who can create and manage booking pages? Any user who has access to the Appointment Scheduler app can create booking pages. Only a page's owner (or an admin) can edit it — someone added to a team page takes bookings on it but can't change it. An appointment can be opened, cancelled, rescheduled or marked a no-show by its host, the owner of its booking page, or an admin; the other hosts of a collective meeting can open it read-only. Admins and app-admins see and manage every page and every appointment across the business. --- ## Permissions and access ## Who can change the tenant-wide settings? Only admins and app-admins. The **Settings** tab in Appointment Scheduler is hidden from regular users. Settings include the public-booking master switch, who may publish pages people outside the organization can book, reminder defaults, SMS reminders, and integration alerts. ## Why can't external visitors book on our page? Three things to check in order: the **Allow booking via public /meet pages (applies to everyone, including colleagues)** setting must be on; the individual booking page must be active (not deactivated or expired); and the page must have at least one active meeting type. A page with no active meeting type, or one whose meeting types have all expired, shows as unavailable even when the page itself is active. And a page set to **Listed internally — invitees must sign in to book** takes bookings only from signed-in members of your organization: outside visitors can't book it. ## What can someone on a colleague's team page do? They take bookings on the page but, unless they're an admin, can't edit it. Their **Dashboard** (and the mobile app) lists it under **Team pages you host on**, with the weekly hours set for them and a **Leave team** button; **Set my hours** next to the page lets them change their own weekly hours and date overrides themselves, while everything else about the page stays with its owner or an Appointment Scheduler admin. Leaving stops new bookings from that page; appointments already booked with them stay theirs. If fewer than two people are left, the page goes back to solo scheduling, its round-robin and collective meeting types switch to a single host, and the owner is notified. --- ## Day-to-day ## What happens when someone books an appointment? The platform checks the host's availability again at confirmation to prevent double-booking — their calendar, synced Google events, approved leave (while **Treat approved leave as busy time** is on) and, for an Outlook calendar, a live free/busy read — then creates a calendar event on the host's calendar, sends the invitee a confirmation email with an ICS attachment and a secure manage link, and notifies the host via inbox and push. If the meeting type is physical and auto-reserve is on, a room is reserved in the Bookings app. If Guest Pass pre-registration is on, the invitee is pre-registered as a Guest Pass visitor; the visit follows your Guest Pass approval settings, so it may need approval first, and the host is told when it does. If a colleague books while signed in with their own work email, the meeting also lands on their calendar. ## Can a host set a daily cap on how many appointments they take? Yes. Each meeting type has an optional **Maximum per day** field. When set, the host drops out of availability for that day once the cap is reached. On a round-robin team page the capped host drops out of the rotation for that day; the remaining members keep accepting bookings. ## What happens when a group session fills up? The slot stays visible but shows a **Join waitlist** option instead of a booking form. If someone cancels or reschedules out, everyone on the waitlist for that session is emailed. The first person to rebook gets the seat — there is no auto-booking and no held seats. Group sessions accept 2 to 500 seats. ## How do I enable SMS reminders for invitees? SMS reminders require opt-in on both sides. In **Settings**, turn on **Send SMS reminders to invitees who opt in** — it is off by default, and it works independently of email reminders. Then the invitee must provide a phone number and tick the reminder checkbox when booking. SMS uses your business SMS quota, and no texts go out until SMS is set up for the workspace under Admin → General Settings → SMS Settings. The opt-in carries over if the appointment is rescheduled. ## Can a meeting type have its own reminder lead time? Yes. Each meeting type has an optional **Reminder lead time (hours)** field. When set, the reminder — email and SMS alike — fires that many hours before the appointment instead of the workspace default. Accepted values are 1 to 168 hours (7 days). When left blank, the meeting type uses the workspace's **Default hours before the appointment** setting (24 unless an admin changed it). ## When does the follow-up email go out? Only when the meeting type has a follow-up note saved in its email templates. The follow-up is sent at least 12 hours after the appointment ends, giving the host time to mark a no-show before the thank-you goes out. Appointments older than 3 days are not eligible for a follow-up. ## I can't delete a booking page — what do I do? A page with upcoming appointments cannot be deleted; cancel those appointments first, or deactivate the page instead. A page with any appointment history — including past or cancelled bookings — cannot be hard-deleted at all. Deactivation is the permanent retirement path: the public link shows "unavailable" and no new bookings are accepted, but the appointment history stays intact. ## I can't delete a meeting type either — why? A meeting type that has any appointments on record is deactivated instead of deleted. It no longer appears on the public booking page, but the appointment history tied to it is preserved. Only meeting types with zero appointment history can be hard-deleted. --- ## When something looks wrong ## "I sent someone our booking link but they see 'unavailable'" Check three things: (1) the **Allow booking via public /meet pages (applies to everyone, including colleagues)** setting is on; (2) the booking page itself is active; (3) the page has at least one active meeting type with availability windows that produce free slots. If the page's visibility is **Listed internally**, the invitee must be signed in as a member of your organization to see it. ## "My team's round-robin page only shows one person's times" A team page requires at least two members. If a member was removed or left the team and the page dropped below two members, every round-robin or collective meeting type on that page was automatically reverted to solo mode. Re-add team members and then set the meeting type's assignment mode back to round-robin or collective. ## "A teammate is marked 'Can't open Appointment Scheduler' on the Team card" That person is still on the team, so invitees can book them, but they no longer have access to the app and can't see or manage those appointments. Give them access in Admin → Apps → All Apps, or remove them from the team. ## "The invitee says they never got a confirmation email" Confirmation emails are only sent to appointments in confirmed status with a non-blank invitee email. Check the appointment detail page for the invitee's email address. If the email is correct but undelivered, it may have been caught by the invitee's spam filter — the email includes an ICS calendar attachment, which some filters flag. Note that follow-up emails require a follow-up note on the meeting type; if no note is saved, no follow-up is sent. --- ## Embedding and branding ## Can I embed our booking page on an external website? Yes. In the page editor, add each external domain to the **Allowed embed domains** list — bare hostnames like `example.com`, up to 10 per page. The editor provides a copy-paste iframe snippet. Only the listed domains can embed the page; all others are blocked by the Content Security Policy header. --- ## Licensing and limits ## Does Appointment Scheduler require a licence? Yes. It is a licensed app, off by default. An admin enables it from Admin → Apps → All Apps and grants access per user or group. There is no per-booking or per-invitee charge. ## What are the limits I should know about? | Limit | Value | |---|---| | Meeting duration | 1 minute to 8 hours | | Buffer before/after a meeting | 0 to 4 hours each | | Rolling booking window | 1 to 365 days (default 60) | | Minimum notice | 0 or more minutes (default 4 hours) | | Group session seats | 2 to 500 | | Reminder lead time | 1 to 168 hours (default 24) | | Embed domains per page | 10 | | Routing options per page | 10 | | Booking page title | 120 characters | | Booking page slug | 60 characters | | Welcome message | 300 characters | | Bulk cancel | 100 appointments at a time | | Custom question answer length | 1,000 characters | | Email template note | 2,000 characters per note | | Analytics window | Last 90 days, 8-week trend | --- ## More help - [Appointment Scheduler Overview](/help/articles/appointment_scheduler_app_overview) - Ask AI — the assistant answers Appointment Scheduler questions from these articles. **Keywords:** faq, appointment scheduler, booking page, meeting type, availability, round robin, collective, group session, waitlist, reschedule, not showing, permissions, embed, reminders, no-show, booking link, co-host, leave team, appointment-scheduler, appointment_scheduler --- # Apps & Licensing FAQ **Category:** Faq **Section:** Administration **Updated:** 2026-10-16 Answers to common setup and operating questions about enabling apps, licensing, publishing, visibility rules, pinning, plugins, and app administration — for the admin running it. # Apps & Licensing FAQ Answers to common setup and operating questions about enabling, licensing, and rolling out apps in OneMango. For what the Apps page is and how to set it up from scratch, see the [Enabling Apps, Licences & Plugins Overview](/help/articles/admin_apps_and_licensing). --- ## Setup ## I enabled an app but my users can't see it — what did I miss? A newly enabled app starts as **admin-only** — it is not yet published to users. Your users won't see it until you explicitly publish it. Go to Admin → All Apps → click the app → Access management, then either click **Publish to everyone** or add a visibility rule for a specific group. The app must also be enabled — publishing an app that isn't enabled is blocked with a message telling you to enable it first. ## What's the difference between licensing and enabling? They are two separate gates. A **licence** is an entitlement — it means your organisation has the right to use the app. Licences come from your account manager, your Platform edition, a suite you subscribe to, or an add-on app line on your plan. **Enabling** is the admin's decision to turn the app on for your organisation. An app that is licensed but not enabled does nothing. An app that is not licensed cannot be enabled — you'll see a message naming the suite the app belongs to and how to add it. ## Do I need to configure an app before publishing it? No — publishing with default settings is safe. But the **Setup Health** badge on the Apps list flags enabled apps whose configuration still matches every schema default. That badge is a signal that you may not have reviewed the app's settings. You can configure the app at any time from Admin → All Apps → click the app → Configure. --- ## Permissions and access ## Who can enable and disable apps? Only users with the **Administrator** or **Super Admin** role. The Apps page uses the same administrator gate as the rest of the admin area. ## What does "app admin" vs "contributor" mean? These are per-app, per-business role assignments managed from the app's detail page. An **app admin** can configure the app (settings, schema, destructive operations). A **contributor** can work with records (create, edit) but cannot change the app's structure or settings. Contributors also gain access to the app even if it hasn't been published — the access check grants visibility to anyone assigned as an app contributor. ## How do visibility rules work? A visibility rule ties an app to a group (Admin › Groups). Only members of that group see the app. Multiple rules are additive — a user in **any** listed group has access. When the last rule is removed, the app falls back to its published state: if it was published to everyone, everyone still sees it; if it was admin-only, only admins see it. Each group can only have one rule per app per business. --- ## Day-to-day ## What happens to an app's settings when I disable it? Disabling preserves the app's configuration and its published state. The only changes are that the app is switched off, unpinned from the sidebar, and stamped with who disabled it and when. If you re-enable the app later, the previous configuration and published-to-users state are still there. ## How many apps can I pin to the sidebar? The sidebar rail holds a maximum of **7** pinned apps. If all 7 slots are full, you must unpin one before pinning another — the controller blocks the request with a message stating the limit. Only enabled apps can be pinned. Disabling an app automatically unpins it. ## When I save an app's configuration, does it overwrite settings the app wrote itself? No. The configuration save iterates only over keys declared in the app's configuration schema. Keys that the app's own settings page or background processes wrote are preserved — unrecognised parameters are ignored. ## Does the "Setup Health" badge mean something is broken? No. It means the app is enabled and every configuration key still matches its schema default. It's a reminder that you enabled the app but haven't customised its settings — the app works fine on defaults, but the defaults may not match your organisation's needs. Once you change any setting, the badge updates to "Customised." --- ## When something looks wrong ## "I clicked Enable but got told the app requires a licence" The app is not available to your organisation. The error message names the suite the app belongs to and what to do next. On a self-serve plan, add it yourself: an app priced per specialist from its page (**Add to plan**, as an add-on to a suite you already have), a suite from **General Settings → Billing & Payments → Plan**, or an employee suite with **Ask for company pricing** on that tab. On a plan managed by a MangoApps account team, contact your account manager. Pay-as-you-use apps (such as E-Signature, Bookings, Live Assist, Power Tables and Live Boards) skip the licence gate entirely; if one of those is showing this error, contact support. ## "I pinned an app but it doesn't show in the sidebar" Three possible causes: (1) You already have 7 apps pinned — the 8th is accepted but appears only in the overflow, not the rail. The Apps list shows a banner when pinned apps exceed the rail capacity. (2) The app isn't enabled — only enabled apps can be pinned, and disabling an app automatically unpins it. (3) The user personalised their own sidebar rail, which overrides the admin-set pins. --- ## Plugins (custom apps) ## What are the size limits for uploading a plugin? The zip file must be at most **10 MB**. When extracted, the contents must not exceed **100 MB** and must contain no more than **500 files**. Uploads that exceed any of these limits are rejected. ## Can I roll back a plugin to a previous version? Yes. The Plugins page at Admin → Apps → Custom Apps keeps the last **20 versions** of each plugin. You can roll back to any previous version from the version history. ## Can I uninstall a system app? No. System apps cannot be removed — the uninstall action explicitly blocks them with *"System apps cannot be removed."* You can only disable a system app (which hides it from users and unpins it). Custom plugins can be fully uninstalled, which runs the plugin's cleanup hook, purges its per-business data, and removes the marketplace link. --- ## More help - [Enabling Apps, Licences & Plugins Overview](/help/articles/admin_apps_and_licensing) - [Settings Hub & Navigation](/help/articles/admin_settings_hub) - [Billing & Payments](/help/articles/admin_billing) - Ask AI — the assistant answers questions about app management from these articles. **Keywords:** faq, enable app, disable app, app marketplace, license, licence, publish app, admin-only, visibility rules, pin app, sidebar, app admin, contributor, plugins, custom apps, configure app, setup health, rag --- # Ask AI App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-18 How to set up and run Ask AI — the platform's conversational assistant that routes questions to specialist agents, executes actions, and answers from your organisation's own knowledge. # Ask AI ## 1. What it is Ask AI is the platform's conversational assistant. Employees type or speak a question, and Ask AI routes it to whichever specialist agent owns the answer — scheduling for shift questions, leave management for PTO balances, service desk for ticket status, and so on. Each agent works with that app's live data, so answers reflect the current state of a schedule or queue, not just what a policy document says. - **Enablement:** Ask AI requires a licence and the **Platform Standard** edition or above. An admin enables it from **Admin → Apps → All Apps → Ask AI**, and can restrict access to specific groups or roles. - **What it is not:** Ask AI is not the place to pause or resume the AI across the organisation — those kill switches live in **Admin → AI Operations**. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Ask AI**, and enable it. Confirm the organisation is on the **Platform Standard** edition or above — Ask AI will not load on Platform Lite. 2. Open **Apps → Ask AI → Admin → Settings** and review the defaults. The key decisions at this stage: - **Enable Action Execution** (on by default) — whether the assistant can carry out actions such as filing tickets or creating shifts. Changes like these pause for the employee's confirmation first; only small changes to their own things, such as a bookmark or a page watch, run straight away. - **Enable Voice Mode** (on by default) — whether employees can speak to Ask AI. The default daily limit is **30 minutes per user**. - **Conversation retention** (default **24 months**) — how long transcripts are kept before the nightly sweep permanently deletes them. 3. Open **Apps → Ask AI → Admin → Agent Guidelines → AI Features** and confirm the toggles suit your rollout. Key defaults: - **Multi-agent answers** is on — a question that spans several areas is sent to each relevant agent, and their answers are combined into one reply. - **Shared knowledge search** is on — agents also search the **Company knowledge sources** ticked beneath it. - Review that source list. **Library items** may be off if your organisation already had libraries when this source was added. Tick it to let answers use your libraries. 4. To restrict Ask AI to a pilot group before a wider rollout, go to the app's **Audience** settings in Admin → Apps → All Apps and assign the group. Only members of that group will see the Ask AI entry point; others are redirected. 5. Confirm it works: open **Apps → Ask AI → Chat** and type a question. The response should stream in. If the organisation has other apps enabled (Shifts, Leave Management, Service Desk), try a question in each domain to verify agent routing. ## 3. How it fits together **Agents and routing** — Ask AI is a dispatcher, not a single model. Each enabled app registers its own specialist agent. When a message arrives, Ask AI classifies the intent and routes it to the matching agent. With **Cross-app reasoning & conversation continuity** on, an agent can reach into another app to finish a request, so the employee never restates the question. Agents follow the same licence and audience rules as their parent app. If an employee cannot reach the Compensation app, the Compensation agent will not answer them either. **Company knowledge** — Beyond each agent's live data, Ask AI searches your organisation's written knowledge. Each source is a separate switch under **Company knowledge sources** on the AI Features tab: Knowledge Base articles, HR Policies, SOPs, Site pages, Wiki pages, shared Drive files, Library items, Contracts, Posts, Verified answers, Training courses, Forms, Help articles, Recorder recordings, AI Notepad notes, custom app records, and the person's own tasks. Every source applies the asking person's own access. Within the Knowledge Base source, you can also switch off individual areas. **Libraries as a source** — Answers use items from only the libraries a person can already open, and only when the Libraries app is open to them. A library restricted to people leaders reaches a leader's answers and never an employee's. An item that links to another record, such as a form or a wiki page, is cited only when the person can open that record too. **Knowledge scope for each surface** — An embedded assistant (Ask AI shown on your intranet or another site, set up under **Embedded assistants**) can be narrowed to fewer sources. Its **What it draws on** list only narrows. It can never add a source your organisation has switched off, and each person's access still applies. Leaving every box clear means "use everything the organisation allows". For example, a perks panel on the intranet home might tick only **Library items**. Asked "what discounts do we get?", it answers from the perks library. Asked about the leave policy, it will not cite HR Policies, although the leave agent can still show the person their own balance. **Verified Knowledge** — When Ask AI gives a wrong or incomplete answer in a News Feed thread, a user can submit a correction. These corrections land in the **Verified Knowledge** queue (pending review). An admin approves, edits, or rejects each one. Approved entries become part of the retrieval corpus and directly influence future answers. **Personal Memory** — The assistant can remember facts about each employee across conversations. Every user can review and erase these facts from the **Personal Memory** tab. Whether facts are remembered is set in the Muscle Memory app, not in Ask AI. **Journeys** — Multi-step goals the assistant tracks for an individual employee. An employee can have up to **3 active journeys** at a time, each with up to **12 steps**. The assistant updates progress during conversation, and the employee can override any step from the **My Journeys** tab. Journeys are switched on and off by **Journeys (multi-step goal tracking)** on the AI Features tab. ## 4. Running it ### Reviewing Agent Guidelines Agent Guidelines shape how every agent thinks, communicates, and acts. Go to **Apps → Ask AI → Admin → Agent Guidelines**. The tabs are: 1. **Assistant** — the assistant's **Name**, **Icon**, **Greeting** and **Description**. The name is how it introduces itself in every answer. 2. **Context & Rules** — business context, custom instructions, universal guardrails, and a glossary, added to every agent's instructions. 3. **Communication** — tone, response style, apology, and escalation messages. 4. **Autonomous Actions** — action-level guardrails, notification rules, and whether reasoning is shown in chat. 5. **Overrides** — per-agent customisations that override the global settings. 6. **AI Features** — organisation-wide switches, including the company knowledge sources. 7. **Embedded assistants** — Ask AI panels published on other sites, each with its own permissions and **What it draws on** list. 8. **Questions** — what people asked that Ask AI could not answer. Context, Communication, and Autonomous Actions use a **draft / publish** workflow: changes stay in draft until you click **Publish**, then apply to all agents. Assistant, Overrides and AI Features apply on save. ### Managing Verified Knowledge Go to **Apps → Ask AI → Admin → Verified Knowledge**. The queue shows three tabs: **Pending**, **Active**, and **Retired**. Pending entries are submitted corrections awaiting review. Active entries are live and influence answers. Retired entries are archived. For each pending entry, you can approve (optionally editing the answer), reject, or leave it. An approved entry immediately becomes part of the retrieval corpus. ### Using the Knowledge Map **Apps → Ask AI → Admin → Knowledge Map** shows the graph of content linked to skills and roles. This makes retrieval skill-aware: an answer about welding safety is prioritised for employees whose role requires welding skills. You can add manual links between content (Knowledge Base articles, HR Policies, SOPs) and skills, or filter the graph by skill or role type. ### Running the Test Suite **Apps → Ask AI → Admin → Test Suite** (accessible to admins and managers) lets you send example questions to the live agent pipeline and see which agent handled them, the response, and the routing match. Tests run against the published Agent Guidelines configuration. ### Placing the Ask the assistant card on dashboards The **Ask the assistant** dashboard card lets people ask a question from the home dashboard. It shows the assistant's name, icon and greeting, a question box, and up to 4 suggested questions for the person's role. A named assistant's card reads "Ask" plus its name. The card is never added to boards automatically. It leads the **People Leaders** and **Employees** starter boards, and an admin can place it on any other board. It shows only to people who can open Ask AI. Admins also see a **Top questions** tile for the last 7 days: how many questions were asked, how many were answered, and the most common questions. A question appears only when at least 5 different people asked it, so no one can be identified from it. ### Processing Data Requests Data requests (GDPR Articles 15/17/20) are handled for every app at once, Ask AI included, at **Admin → Retention & Legal Holds → Requests about a person**. Find the person, check what each app holds, then choose **Export a copy** or **Erase their data**. Erasure is irreversible. Only admins (not app admins) can access this surface. ### Reviewing Analytics **Apps → Ask AI → Admin → Analytics** shows this tenant's Ask AI usage: adoption trends, volume, per-user and per-day breakdowns, with CSV export. ### Managing the Prompt Library **Apps → Ask AI → Prompt Library** shows a gallery of reusable prompt templates. The gallery combines system-wide curated prompts with the tenant's own org-private prompts. Any employee can browse and click **Use** to deep-link into the chat with the prompt prefilled. Admins can create, edit, and delete tenant-private prompts. Prompts are organised into categories: Productivity, Communication, Workflow, Analytics, and Operations. ### Asking about an attached video Open **Attach files**, select an MP4, MOV, or WebM clip up to two minutes and 100 MB, and wait for **Video ready** before sending a question. The mobile web chat links to the same responsive composer. Processing uses timestamped speech plus up to six sampled frames, so answers can point to evidence while explaining unreadable details and gaps between samples. A silent video uses visual samples. Retry interrupted processing or remove the clip to cancel. Private clip evidence expires after 24 hours; existing conversation answers follow the organization's conversation retention. ## 5. Settings Settings are split across three places: the **Settings** page, the **AI Features** tab, and each embedded assistant's own form. ### Settings page | Setting | Default | What it changes | |---|---|---| | **Enable General Questions** | On | Whether Ask AI answers open-ended questions beyond schedule and app-specific queries | | **Enable Schedule Queries** | On | Whether Ask AI answers shift and schedule questions | | **Enable Action Execution** | On | Whether agents can use their tools — look up live data and carry out actions (changes ask for the employee's confirmation first). Off stops live lookups too; answers from your company's knowledge continue | | **Enable Voice Mode** | On | Whether employees can use voice conversations with Ask AI | | **Voice Daily Limit** | 30 minutes per user | Per-user daily cap on voice usage; 0 means unlimited | | **AI Voice** | Marin | The voice used for spoken responses | | **Voice Response Style** | Concise | How verbose voice answers are | | **Voice Speech Pace** | Normal | Speed of spoken responses | | **Include Platform Help Articles in Answers** | Off | Whether the assistant's answers draw on platform help-centre articles in addition to company knowledge | | **Keep conversation history for** | 24 months | How long transcripts are retained before permanent deletion by the nightly sweep | | **Allow users to clear their conversation** | On | Whether employees see the "Clear conversation" and "Reset AI completely" controls | ### AI Features tab (Agent Guidelines → AI Features) | Setting | Default | What it changes | |---|---|---| | **Multi-agent answers** | On | Whether a question spanning several areas is sent to each relevant agent and the answers combined | | **Shared knowledge search** | On | Whether agents search the company knowledge sources ticked below it | | **Company knowledge sources** | Each source on, except **Library items** | Which sources shared search may use. Library items may be off for organisations that already had libraries when it was added | | **Leave out sources overdue for review** | Off | Whether answers skip content that Content governance has flagged as overdue for review | | **App explanations from Help Center** | On | Whether each app's agent answers "how does this work?" from that app's help articles | | **Journeys (multi-step goal tracking)** | On | Whether the assistant tracks multi-step goals for employees | | **Auto-detect goals** | On | Whether the assistant starts tracking a journey on its own when a goal is clear | | **Weekly improvement proposals** | Off | Whether admins get a weekly Inbox list of suggestions drawn from failed or low-rated turns | | **Cross-app reasoning & conversation continuity** | On | Whether an agent can reach into other apps to finish a request | | **Smarter routing (tool-signal boost)** | On | Whether routing is more decisive when a question clearly matches an app | | **Multi-step planner** | Off | Whether a "do X then Y" request becomes a plan with read-only steps run automatically | | **Re-plan attempts (planner)** | 1 | How many times the planner may refine a low-quality plan | ### Each embedded assistant (Agent Guidelines → Embedded assistants) | Setting | Default | What it changes | |---|---|---| | **What it draws on** | All clear (everything the organisation allows) | Narrows this assistant's company-knowledge answers to the ticked sources only | ## 6. More help - **Ask AI FAQ** — specific setup and operating questions, including limits, thresholds, and troubleshooting - **Ask AI — What It Can Do and How to Govern It** — the platform-level governance article covering AI operations, moderation, and cross-app controls - Ask AI — the assistant answers questions about Ask AI from these articles **Keywords:** Ask AI, AI assistant, AI chat, agent guidelines, voice mode, prompt library, journeys, verified knowledge, knowledge map, conversation history, AI settings, action execution, multi-agent, shared knowledge, company knowledge sources, library items, libraries, embedded assistant, what it draws on, Ask the assistant widget, dashboard card, ask-ai, ask_ai --- # Ask AI FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-14 Answers to common setup and operating questions about Ask AI — for the admin running it. # Ask AI FAQ Answers to common setup and operating questions about Ask AI. For what the app is and how to set it up from scratch, see the [Ask AI Overview](/help/articles/ask_ai_app_overview). --- ## Setup ## Do I need to do anything beyond enabling Ask AI before employees can use it? No. Ask AI requires a licence, and an admin turns it on from **Admin → Apps → All Apps**. Once it is enabled and your organisation is on the **Platform Standard** edition or above, employees see the chat sidebar immediately. The default settings — action execution on, voice on, shared knowledge on — are ready to use. You can refine settings and Agent Guidelines at any time, but nothing else blocks employees from asking their first question. ## Who can manage Agent Guidelines, Verified Knowledge, the Prompt Library and the other admin tabs? The Settings tab is open to admins and Ask AI app admins, and an Ask AI app admin can also manage **Embedded assistants**. Managers can open the **Test Suite**. Every other admin tab — Agent Guidelines, Questions, Verified Knowledge, Knowledge Map and Analytics — requires the full admin role (admin or above). Any employee can browse the Prompt Library and use an existing prompt. Only admins (admin or above) can create, edit, delete, or save tenant-private prompts. --- ## Permissions and access ## Why can some employees not see Ask AI, or get redirected when they open it? Three things to check. First, the app must be enabled for the organisation (**Admin → Apps → All Apps → Ask AI**). Second, if you have restricted the app's audience to a specific group in Admin → Apps → All Apps audience settings, only members of that group will see the Ask AI entry point — everyone else is redirected. Third, Ask AI requires the **Platform Standard** edition; it will not load on Platform Lite. --- ## Day-to-day ## Where does Ask AI pull its answers from? Ask AI draws on four layers. First, shared company knowledge — Knowledge Base, HR Policies, SOPs, Sites, Wikis, Drive, contracts, posts, training courses, forms, AI Notepad notes, custom-app records and more — each of which you can toggle on or off individually from **Agent Guidelines → AI Features**. Second, Verified Knowledge entries that admins have approved. Third, live data pulled from connected apps through agent tools (schedules, leave balances, tickets, etc.). Fourth, the files an employee attaches to a message. Optionally, you can include platform help-centre articles by turning on **Include Platform Help Articles in Answers** in the Settings page. ## How does agent routing work, and can employees force it? Each question is classified and routed to whichever specialist agent owns that domain. There are over 100 built-in domain agents, and each one is gated by the same licence and audience rules as its parent app. If a question spans two areas, the first agent hands the remainder to another mid-conversation. Employees can also force routing by @mentioning an agent inline (e.g. @hr, @scheduling). ## What happens when I approve a Verified Knowledge entry? The entry moves from the **Pending review** tab to the **Active** tab and immediately becomes part of the retrieval corpus. Future answers can cite it. You can also edit the entry before approving. To remove it later, retire it — it moves to the **Retired** tab and stops influencing answers. If the entry answers an unanswered question group, approving it also closes that group. **Reject this correction** hands the question back to the person who wrote the answer (see "I've been assigned an unanswered question" below). ## How do Journeys work and who controls them? Journeys track multi-step goals (onboarding a hire, migrating a policy) across sessions. Each employee can have up to **3 active journeys** at a time, each with up to **12 steps**. The assistant updates progress during conversation, and the employee can override any step from their **My Journeys** page. Journeys are toggled from **Agent Guidelines → AI Features**: the **Journeys** toggle controls whether goals are tracked at all, and **Journey inference** controls whether the assistant infers progress from conversation context. Both are on by default. --- ## Unanswered questions ## How do I see what people asked that Ask AI couldn't answer, and why are some questions missing? Open **Ask AI → Agent Guidelines → Questions** (admin or above) and click **Group questions**, or **Regroup questions** after the first run. Ask AI takes the last **30 days** of questions it couldn't answer from company knowledge and groups them by meaning. Each run considers up to the **200** most recent questions and uses your organisation's AI usage. Groups keep their identity across regroups, so an owner and a history carry over while people keep asking. A group is shown only when at least **5 different people** asked it. Smaller groups are counted in a note under the list but never displayed, so nobody can be picked out from what they asked. The **Narrow to** filter works on one department or one country at a time, and each slice must also reach five people. ## Who owns an unanswered question group? Each shown group becomes a Content Governance finding with the issue type **Unanswered question**. Ask AI assigns it to a topic expert for the group's subject who can open Ask AI; if there is none, it stays unassigned and the admins get the reminder. The finding is rated high when **20 or more** people asked, otherwise medium. Use **Assign or snooze** on the group's row to change the owner or snooze it in **Admin → Content Governance**. ## I've been assigned an unanswered question — what do I do? Open it from the reminder, or from **Content I own** in your profile menu. The page shows the merged question and how many people asked, counted but never named. Click **Create an answer**, write it, and choose **Send for review**. Your admins then approve or reject it in **Verified Knowledge**. While it waits, the question stays with you and the reminders stop. If they reject it, you get a "Your answer wasn't approved" notification and the question is yours again. ## What happens when I click "Create an answer" as an admin? A drawer opens with the merged question already filled in. You can describe the facts and click **Draft** to have AI fill the question and answer — it never saves on its own. Choose who the answer can influence, then **Save answer**. An admin's answer goes live in Verified Knowledge at once, closes the group and resolves its finding. ## Can a question group close without anyone writing an answer? Yes, in two ways. Once a week Ask AI re-asks each open group's questions as up to **3** of the people who asked, with their own permissions and nothing saved. The group closes only if every one of them now gets an answer from company knowledge. An admin can also resolve or dismiss the group's finding in Content Governance. Dismissing is permanent: the same question keeps landing in that dismissed group. ## How do I stop the unanswered-question reminders? Owners, or the admins when a group has no owner, get a weekly reminder. Each person can mute it in their notification preferences under **Ask AI unanswered questions**, which is on for in-app and email by default. That setting also covers the "answer wasn't approved" notice. For the whole organisation, open **Admin → Content Governance → Settings**. On the Ask AI card, turn off **Notify on governance review** to stop reminders. Turn off **Enable automated governance scanning** to stop filing findings altogether; it is on by default. --- ## Voice ## What are the voice limits, and which voices can I choose? Each voice session is capped at **15 minutes**. The per-user daily limit defaults to **30 minutes** and is configurable from the Ask AI Settings page; setting it to **0** removes the daily cap entirely. When an employee hits the daily limit, the voice button is disabled until the next day. Ask AI supports 10 voices: **Marin** (default), Cedar, Alloy, Ash, Ballad, Coral, Echo, Sage, Shimmer, and Verse. Marin and Cedar are the newest and recommended for best quality. The admin chooses one voice for the whole organisation from the Settings page, where an in-settings preview lets you hear each voice before selecting it. --- ## Attachments ## What files can I attach to a question, and what are the limits? Employees can attach up to **3 files per message**. Images (PNG, JPG, WebP, GIF), PDFs, Word, Excel, CSV, and plain text have an **8 MB** limit each. One of the files can be an **MP4, MOV, or WebM video**, up to **two minutes and 100 MB**. Supported video codecs are H.264, HEVC, VP8, and VP9, at up to 4K resolution. Images use vision; documents use text extraction. PDFs are read up to **100 pages**. Scanned or unreadable content produces an explanation when text cannot be extracted. ## How do I ask about a video? Use **Attach files** in the composer. On mobile web, **Attach files or a video** opens the full composer for the current conversation. Wait until the chip says **Video ready**, then ask your question. Processing combines timestamped speech, when available, with up to six sampled frames. Answers should cite timestamps and explain unclear details; sampled frames do not show every action between them and do not certify compliance. Remove the attachment to cancel processing and clear its extracted evidence. If processing fails or is interrupted, use **Retry processing**. Each clip allows up to three processing attempts; each employee can start six attempts per hour. Organization AI usage limits also apply. Private video uploads and extracted evidence expire after **24 hours**; answers already in the conversation follow the conversation's retention policy. ## Why was my video refused or left waiting? Use a supported export within the size, duration, and resolution limits. Corrupt files, unsupported codecs, and over-limit clips are rejected before processing. No audio track is supported: the assistant uses visual samples. If a worker is interrupted, the status offers retry after ten minutes without progress. You can remove a failed attachment; the composer blocks sending while an attachment is still processing or failed. --- ## When something looks wrong ## "The AI said it can't help and offered to open a ticket — what does that mean?" When the assistant detects that it cannot confidently answer — a capability refusal, an apology answer, or an empty result — it offers a **Get human help** button. People can also just ask for a person in the conversation ("can I talk to someone about this?"), and the assistant sends it the same way. Where it goes: - **With Service Desk** enabled for the organisation *and* open to that employee, it files a Service Desk ticket carrying the question, the AI's answer and the turn reference, routed by your Service Desk rules on the request type the question is classified into. - **Without Service Desk** (or when the employee's audience rules exclude them from it), it goes to the admins of the app the question was about — for example the Leave Management admins for a time-off question — as a notification with the question, the answer and a link to the employee's profile. If that app has no admins of its own, your Ask AI admins (or, failing that, your workspace administrators) receive it. The person asking never receives their own request. The button is hidden only when nobody could receive it — for example when the only administrator is the person asking. ## "My employees say they can't clear their conversation" Check whether **Allow users to clear their conversation** is turned on in the Ask AI Settings page (it is on by default). When this is off, the **Clear conversation** and **Reset AI completely** controls are hidden on every surface — web, mobile, and API — and the server returns a "disabled by your administrator" message if the endpoint is called directly. Clearing is a view-level action (the governance record is retained for the retention period), so this toggle controls a UX affordance, not data retention. --- ## Shared AI conversations ## Can I invite coworkers into a private conversation, and remove them later? From **History**, choose **Share conversation**. Edit the summary, select up to seven coworkers, choose contributor or viewer access, and review the exact content before sending invitations. Each coworker must accept before seeing the shared conversation. The original private history, attachments, memories and tool traces stay private. The owner opens **Participants** to change contributor/viewer roles or revoke access. Revocation blocks subsequent reading, search and exports; it cannot remove copies someone already downloaded. Contributors send as themselves. Shared conversations do not become personal AI memory. ## What can Ask AI use in a shared conversation? It uses the reviewed summary and shared messages. You can include a Service Desk ticket when every active participant can open it. Answers and follow-up context are checked again when access changes. Other sources and actions remain available in your private Ask AI conversation. ## What happens if an answer is interrupted? Your message stays in the conversation. A failed reply offers **Retry reply** to its sender. Live updates preserve your unsent draft. Reusing a submitted form with edited text produces a clear error instead of silently ignoring the edits; refresh and submit it as a new message. --- ## Conversation retention and data ## How long are conversations kept? The default is **24 months**. An admin can change this from the Settings page; the allowed range is **1–36 months**. Conversations older than the configured period are permanently deleted by a nightly sweep. Shortening the retention period removes history immediately on the next sweep and cannot be undone. Diagnostic flow logs are kept separately for **180 days** or the tenant's retention period, whichever is shorter. ## How do I handle a GDPR data-subject request for Ask AI data? Data requests are handled for every app at once, Ask AI included. Go to **Admin → Retention & Legal Holds → Requests about a person** (admin-only). Find the person, check what each app holds about them, then choose **Export a copy** (Article 15/20) or **Erase their data** (Article 17). Erasure is irreversible. Each request covers the current organisation only — a person who belongs to several organisations needs a request in each. --- ## Licensing and limits ## What are the hard limits I should know about? | What | Limit | |---|---| | Files per message | 3 | | Image/document size | 8 MB | | Video size / duration | 100 MB / 2 minutes; one video per message | | Video processing | Up to 6 sampled frames; 3 attempts per clip; 6 attempts per employee/hour | | Video evidence retention | 24 hours | | PDF page extraction | 100 pages | | Voice session length | 15 minutes | | Voice daily limit (default) | 30 minutes per user (0 = unlimited) | | Active journeys per user | 3 | | Steps per journey | 12 | | Conversation retention | 1–36 months (default 24) | | Diagnostic flow-log retention | 180 days or tenant retention, whichever is shorter | --- ## More help - [Ask AI Overview](/help/articles/ask_ai_app_overview) - [Ask AI — What It Can Do and How to Govern It](/help/articles/platform_ask_ai_for_admins) - [Content Governance](/help/articles/compliance_content_governance) - Ask AI — the assistant answers Ask AI questions from these articles. **Keywords:** faq, Ask AI, voice mode, voice limit, attachments, journeys, verified knowledge, company brain, agent routing, shared knowledge, data requests, unanswered questions, question groups, create an answer, content governance, content I own, conversation retention, clear conversation, prompt library, escalation, permissions, not showing, ask-ai, ask_ai --- # Ask AI — What It Can Do and How to Govern It **Category:** System-features **Section:** Advanced Features **Updated:** 2026-10-16 What Ask AI does, how to configure its agents and knowledge sources, and the admin controls for guidelines, moderation, retention, and data requests. # Ask AI — What It Can Do and How to Govern It ## 1. What it is Ask AI is the platform's conversational assistant. Each question is routed to a specialist agent that is wired into the app it covers — scheduling for shift questions, leave management for PTO balances, service desk for ticket status — so answers come from live data, not just documents. When a question spans two areas, one agent hands the conversation to another mid-turn. - **Enablement:** Ask AI is a licensed app that requires the **Platform Standard** edition or above. An admin enables it per tenant at **Admin → Apps → All Apps**; it is not on by default. - **What it is not:** Ask AI is the assistant your employees talk to. It is not the place where you pause AI or manage approvals — those kill switches live in **Admin → AI Operations**. ## 2. Standing it up 1. Enable the app at **Admin → Apps → All Apps**, then go to **Apps → Ask AI → Settings** and confirm that **Enable Action Execution**, **Enable General Questions**, and **Enable Schedule Queries** are on — all three default to on; each one you turn off narrows what Ask AI answers, as the **Settings page** table below describes. 2. Open **Ask AI → Admin → Agent Guidelines → Context** and write your **Business Context** — the who-we-are paragraph every agent prepends to its answers. Without it, agents answer accurately but generically. Save as a draft first; publish when ready. 3. On the **AI Features** tab under Agent Guidelines, confirm that **Multi-Agent** and **Shared Knowledge** are on. Then review the knowledge sources listed below the toggle — the Knowledge Base, HR Policies, SOPs, Sites, Wikis and Drive, and also contracts, posts, training courses, forms, AI Notepad notes, custom-app records and more, each with a count. Every source defaults to on; turn off any that should not appear in AI answers. 4. Verify the rollout by opening the **Test Suite** (available to admins and managers). Pick an agent, type a representative question, and confirm the answer reflects your published guidelines and knowledge sources. **Silent pairing to watch for:** enabling Ask AI alone makes the chat surface available, but individual agents only answer when their underlying app is also enabled and licensed. An employee asking a scheduling question gets "I can't help with that" if the Shifts app is not turned on for the tenant. ## 3. How it fits together ### Agents and apps Every marketplace app that has an agent contributes one (or sometimes two — a read-only help agent and an admin-operations agent) to the pool. The platform ships about 100 built-in agents; apps built with App Builder or the plugin system add their own automatically. An agent is available to a user only when the app it belongs to is enabled for the tenant and published to that user's audience. ### Guidelines and overrides Agent Guidelines are the instructions every agent follows — your business context, tone, guardrails, and action rules. They follow a **draft/publish** workflow: saving a draft stages changes without affecting live agents; publishing promotes them immediately. Context, Communication and Autonomous Actions use the draft/publish workflow; the other tabs apply on save. The tabs are: - **Assistant** — the assistant's name, icon, greeting and description. - **Context & Rules** — business context, custom instructions, universal guardrails, and glossary terms. - **Communication** — tone, apology and escalation messages, and response format. - **Autonomous Actions** — action-specific guardrails, notification rules, and whether the agent shows its reasoning. - **Overrides** — per-agent tweaks that layer on top of the global guidelines (extra instructions, tone, guardrails). - **AI Features** — org-level toggles for multi-agent answers, shared knowledge, journeys, cross-app reasoning, and the planner. - **Embedded assistants** — Ask AI panels published on other sites. - **Questions** — what people asked that Ask AI could not answer. ### Knowledge layers Ask AI draws answers from three layers, each governed differently: - **App data** — the live records inside each app (shifts, tickets, leave balances). Governed by the app's own permissions; the agent sees only what the asking user can see. - **Shared knowledge** — your Knowledge Base articles, HR Policies, SOPs, Sites, Wikis, Drive files, contracts, posts, training courses, forms, AI Notepad notes, custom-app records and more — only what the asking person can already open. Admins choose which sources are searchable on the AI Features tab, which lists every one. - **Verified Knowledge** — corrections and curated Q&A pairs that an admin has approved. These override retrieval when a matching entry exists. Managed at **Ask AI → Admin → Verified Knowledge**. ### Tool confirmation When an agent is about to do something that changes data — delete a record, submit a form, send a notification — it pauses and asks the user to confirm before proceeding. A few small changes to the person's own things, such as a bookmark or a page watch, run straight away. The admin can disable all write actions globally by turning off **Enable Action Execution** in Settings. ## 4. Running it ### Publishing or updating guidelines 1. Open **Ask AI → Admin → Agent Guidelines** and select the tab to edit. 2. Make changes and click **Save Draft**. The draft is staged but agents continue running the published version. 3. When ready, click **Publish**. Changes apply to all agents immediately. 4. To undo a draft before publishing, click **Discard Draft** — the tab reverts to the published values. ### Reviewing verified knowledge 1. Open **Ask AI → Admin → Verified Knowledge**. New entries appear on the **Pending** tab. 2. Review each entry. **Approve** to make it live (Ask AI will use it in answers), or **Reject** to discard it. 3. Active entries can be edited in place or **Retired** when they go stale. ### Running tests against your guidelines 1. Open **Ask AI → Admin → Test Suite**. The page shows whether guidelines are published or still on defaults, and flags any unpublished draft. 2. Select an agent, type a question, and run the test. The result shows the agent's answer under the current published guidelines. Managers can also access the Test Suite; all other admin surfaces require admin or above. ### Handling a data request Data requests are handled for every app at once, Ask AI included. 1. Open **Admin → Retention & Legal Holds → Requests about a person**. 2. Find the person and check what each app holds about them. 3. Choose **Export a copy** for an Article 15/20 access request, or **Erase their data** for an Article 17 erasure request. Erasure is irreversible. Data requests are scoped to the current tenant. An employee with memberships in multiple tenants requires a separate request from each. ### Customizing the assistant's identity Go to **Ask AI → Admin → Agent Guidelines → Assistant**. Admins can change the assistant's name, icon, greeting and description. The name is how the assistant introduces itself everywhere — in Ask AI, voice, Chat, Slack and Teams. ## 5. Settings ### Settings page (Ask AI → Admin → Settings) | Setting | Default | What it changes | |---|---|---| | **Enable Action Execution** | On | When off, Ask AI chat runs no agent tools at all: it still answers from your company's knowledge and the conversation, but makes no live lookups of schedules, balances or records, and no changes. | | **Enable General Questions** | On | When off, general "how do I…" questions that go to the platform help assistant get a "switched off" reply. Questions an app's agent handles are unaffected. | | **Enable Schedule Queries** | On | When off, the scheduling agent does not answer shift questions. | | **Include Platform Help Articles in Answers** | Off | When on, OneMango's public help articles join the search behind answers about your company. How-to questions about OneMango itself are answered from its help articles on their own switches (Enable General Questions; App explanations from Help Center). | | **Enable Voice Mode** | On | Allows employees to speak to Ask AI instead of typing. | | **Voice Daily Limit** | 30 minutes per user | The maximum voice minutes per user per day. Set to 0 for unlimited. | | **Allow users to clear their conversation** | On | When on, users can clear their visible conversation history. Clearing is cosmetic — the record stays available for governance until retention removes it. | | **Keep conversation history for** | 24 months | Conversations older than this are permanently deleted on the next nightly sweep. Shortening this removes history immediately and cannot be undone. | ### AI Features tab (Ask AI → Admin → Agent Guidelines → AI Features) | Setting | Default | What it changes | |---|---|---| | **Multi-agent answers** | On | When a question spans several areas, the relevant agents are consulted and their answers combined into one reply. | | **Shared knowledge search** | On | Agents search your company's knowledge content (KB articles, HR policies, SOPs, Sites, Wikis, Drive, contracts, AI Notepad notes and more) — only what the asking person can already open. The per-source toggles below this control which sources are included. | | **App explanations from Help Center** | On | Each app's agent answers "how does this work?" questions from that app's Help Center articles. | | **Journeys** | On | Multi-step goal tracking for employees, private to each person on their **My Journeys** page. **Auto-detect goals** (on) starts tracking one when a person is clearly working through it. | | **Weekly improvement proposals** | Off | Once a week, up to five admins — always including whoever turned it on — get an Inbox list of improvement suggestions drawn from failed, misrouted and low-rated questions — which means from what employees typed. | | **Cross-app reasoning & conversation continuity** | On | An agent can reach into other apps to finish a request and keep a conversation with the agent that asked a question. Off returns Ask AI to one app per question. | | **Smarter routing** | On | Routes more decisively when a question clearly matches an app. | | **Multi-step planner** | Off | Turns a multi-step request into a plan, runs the read-only steps, and drafts the steps that change data for approval. | ### Moderation (platform-wide, not per-tenant) Ask AI enforces a rate limit of 120 messages per user per hour. Every message is checked for offensive content, prompt injection attempts, and spam. Admins are not exempt from these checks. ## 6. More help - **Ask AI FAQ** — specific setup and operating questions, limits, and troubleshooting. - **AI Operations** — pausing AI, approvals, and agent health (the kill switches). - Ask AI — the assistant answers questions about itself from these articles. **Keywords:** Ask AI, AI assistant, AI governance, agent guidelines, verified knowledge, knowledge map, AI moderation, AI retention, data request, AI test suite, voice mode, action execution, multi-agent, shared knowledge, conversation history, GDPR erase, AI analytics, prompt library, ask-ai, ask_ai --- # Asset Pro App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-20 How to set up and run Asset Pro — IT asset inventory, assignment tracking, software license management, maintenance scheduling, and depreciation. # Asset Pro ## 1. What it is Asset Pro tracks your organization's hardware and software assets through their full lifecycle — from purchase through assignment, maintenance, and retirement. It gives admins a single place to see what you own, who has it, what it costs, and when it needs attention. - **Enablement:** Asset Pro requires a license. An admin enables it from Admin → Apps → All Apps. A mobile-optimized view is available automatically for phone browsers. - **What it is not:** Asset Pro is not a purchasing tool. Purchase requisitions and purchase orders live in the Procurement app; an asset created from a received PO item links back to that order automatically. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps → Asset Pro → Enable**. 2. Open **Asset Pro → Settings** and review the defaults. The important ones out of the box: auto-depreciation is on at 20% per year, warranty alerts fire at 60 days, maintenance reminders fire at 180 days, and assignment approvals are off. Adjust these to match your policy before adding assets. 3. Open **Asset Pro → Categories**. The app creates 12 default categories the first time an admin loads the page (Laptops, Monitors, Mobile Phones, Tablets, Keyboards & Mice, Headsets, Printers, Network Equipment, SaaS Subscriptions, Desktop Applications, Development Tools, Security Software). Edit or add categories to match your inventory. Each category sets whether a serial number is required, the expected useful life in months, and whether periodic inspections are needed. 4. Grant access by role. By default, all roles (Member, Manager, Admin, Super Admin) can view assets; Managers and above can manage them; only Admins and Super Admins can administer settings, categories, vendors, and contracts. You can narrow or widen each tier in Settings. 5. Start adding assets — manually, by CSV import, or by scanning barcodes. Each asset gets an auto-generated asset number with a configurable prefix (default "AST" for hardware, "SWL" for software). Confirm the dashboard shows your inventory counts. **Silent pairing to watch for:** If you turn on **Require Assignment Approvals** but turn off **Assignment and approval notifications**, approvers get no bell and no email — requests wait in the Pending Approval queue until someone looks. (An employee with no manager on record is not a problem: their requests go to the Asset Pro admins, then the business admins.) Software and contract emails are off until you arm them: **Send software lifecycle emails** and **Send contract renewal emails** are both off by default, so new tenants are not mass-mailed. ## 3. How it fits together **Hardware vs. Software assets** — Every asset is one or the other, chosen at creation. Hardware assets track serial numbers, physical condition, location, and physical assignment (check out / check in). Software assets track license type, seat count, subscription dates, and seat allocation. The distinction matters because only hardware assets can be assigned to a person, and only software assets have license entitlements. Both share categories, vendors, contracts, maintenance records, and depreciation. *Example — a Laptops category with 36 months useful life:* You add a laptop purchased for $1,200 on January 1. The nightly depreciation job applies the configured annual rate (default 20%) monthly, so after 12 months the current value drops to $960. At 36 months the value floors at the salvage value you entered (or $0). The EOL date auto-calculates to 3 years from the purchase (or deployment) date. The Device Refresh report flags it as due for replacement once that threshold passes. **Categories** — A category groups assets by type and governs per-type rules: whether a serial number is required, the default useful life for depreciation and EOL, and whether periodic inspections are required (with frequency, inspection template, and preferred day). Categories apply to hardware, software, or both. **Assignments and chain of custody** — When a hardware asset is assigned to a person, an assignment record tracks who has it, the condition at checkout, and the expected return date. If approvals are on, the assignment starts as **Pending Approval** and the asset shows **Pending Approval** too until a manager approves or denies it. After assignment, the recipient gets an acknowledgement prompt — they can confirm receipt or dispute it (wrong item, damaged, never arrived), which notifies the assigner and managers. Assignment types are **Permanent**, **Temporary**, or **Loaner**. **Software license entitlements** — A software asset with a seat count tracks individual allocations. Each entitlement assigns a seat to a user or a device. When all seats are filled the compliance status moves to **At capacity**; if allocations exceed the licensed count it becomes **Over-licensed**. Site-wide licenses (no seat count) are always compliant. **Vendors** — Vendors are shared across Asset Pro, Procurement, Supplier Hub, and Contracts. Within Asset Pro, a vendor can be invited to a portal where they upload certifications for admin review (approve or reject). Vendor records link to contracts and assets. **Contracts** — Service agreements, warranties, leases, and support contracts tied to a vendor and one or more assets. Each contract has a start date, end date, and optional renewal notice window. Once **Send contract renewal emails** is switched on in Settings (it is off by default), the nightly contract-expiration job alerts the contract owner when the notice window opens; auto-renewing contracts flag honestly as "renews automatically" so you can cancel before renewal locks in. **Facility layouts** — Admins can register a location as a facility and define rack layouts within it (aisle count, bays per aisle, beam levels). These layouts feed into the Inspections app for coverage-sweep inspections of pallet racking. A layout with inspection history cannot be deleted — you must archive or remove those records first. **Integrations** — Asset Pro connects to several sibling apps: - **Service Desk** — tickets can be linked to an asset; the asset card shows the open ticket count. - **Inspections** — categories can require periodic inspections with a linked template and frequency. - **SOP Hub** — SOPs link to individual assets or categories, with per-user completion tracking. - **Procurement** — a received PO item can create an asset record automatically. - **Device discovery** (Lansweeper, Intune, Jamf) — external device inventories sync into Asset Pro with ongoing sync-status tracking. ## 4. Running it ### Assigning hardware 1. Open the asset, open its **⋮** menu and choose **Assign to User**. 2. Select the person, choose the assignment type, and add notes. 3. If approvals are on, the request goes to the employee's manager (or, when they have none, the Asset Pro admins). The manager sees it under **Assignments → Pending Approval**. 4. Once approved (or immediately if approvals are off), the asset status changes to **Assigned** and the employee is notified. ### Returning or unassigning 1. On the assignment record, click **Complete Return** and record the condition at return. 2. Admins can also unassign directly from the asset, which records the return as an admin action. ### Scheduling maintenance 1. Open the asset and go to its **Maintenance** tab, or use the top-level **Maintenance** tab. 2. Click **Schedule Maintenance**, choose the type (Repair, Upgrade, Inspection, Cleaning, Calibration, or Other), set the scheduled date and estimated cost. 3. Move the record through **Start → Complete** (or **Cancel**). Completing a record updates the asset's last-maintenance date, which resets the interval-based reminder clock. ### Running a physical audit (stocktake) 1. Go to **Admin → Physical Audits** and click **Start Audit**. Choose the scope: all active assets, or a single location. 2. Scan barcodes, asset numbers, or serial numbers. Each scan is classified as Found, Unexpected, or Duplicate. The progress bar shows how many expected assets have been accounted for. 3. When finished, click **Complete**. The reconciliation report lists every expected asset not scanned (missing) and every unexpected asset that was scanned but was not in scope. ### Allocating software seats 1. Open a software asset and go to its **Seat Allocation** card. 2. Click **Allocate Seat** and choose a user or device. 3. The compliance status on the asset card updates automatically. ### Reviewing reports Go to **Reports**. Six reports are available, each exportable as CSV, PDF, or Excel: - **Inventory** — full asset list with filters by status, category, location, and condition. - **Assignments** — assignment history with active/returned/overdue filters. - **Depreciation** — purchase price, current value, and accumulated depreciation per asset. - **Maintenance** — maintenance records by type and status, with cost summaries. - **Device Refresh** — hardware older than the configured threshold (default 36 months), scored by replacement priority. - **EOL Timeline** — assets grouped into time-to-EOL buckets (past, 30 days, 90 days, 6 months, 12 months, 12+ months, no date). ## 5. Settings All settings live in **Asset Pro → Settings**. Defaults are read from the configuration service; the admin form merges saved values on top. | Setting | Default | What it changes | |---|---|---| | Enable Asset Agent | On | The master switch for the Asset Pro agent in Ask AI. Off means Ask AI stops answering Asset Pro questions altogether — it does not leave a read-only agent behind. | | Automatic Depreciation Tracking | On | Nightly job recalculates current value for all active assets with a purchase price and date. Off means current value stays as entered. | | Warranty Expiration Alerts | On | Nightly job emails the asset's assignee when a warranty is within the alert window, and sends a weekly digest to configured recipients (or admins). | | Maintenance Reminders | On | Nightly job sends reminders for upcoming scheduled maintenance (14-day lookahead), overdue records, and interval-based maintenance due. Weekly digest goes to configured recipients (or admins). | | Barcode/QR Code Scanning | On | Shows or hides the **Scanner** tab. Does not prevent barcodes from being stored on assets. | | Require Assignment Approvals | Off | When on, an assignment waits in **Pending Approval** until the employee's manager or an Asset Pro admin approves it; nobody can approve their own request. A request made through Ask AI waits for approval whatever this setting says, unless the person asking can already assign assets themselves. | | Software Asset Tracking | On | Enables the software-asset workflow: seat allocation, compliance status, and subscription alerts. | | License Compliance Alerts | On | Includes over-allocated and at-capacity licences in the software emails. Nothing is sent until **Send software lifecycle emails** is also on. | | Send software lifecycle emails | Off | Starts the nightly sweep that emails the chosen recipients when a subscription is lapsing, or a license is full or over its seat count. | | Subscription Alert Days | 30 days | How far ahead of a software subscription's end date the alert fires. | | Currency | USD | The currency of every Asset Pro amount — purchase price, current value, salvage value, cost per seat, maintenance cost and the depreciation report — on screen and in alert emails. | | Default Depreciation Rate (%) | 20% per year | Annual straight-line rate applied monthly by the depreciation job. | | Warranty Alert Lead Time (Days) | 60 days | How far ahead of expiration the warranty alert fires. | | Default Maintenance Interval (Days) | 180 days | Days between maintenance events. Assets with no scheduled maintenance whose last completed date is older than this trigger an interval reminder. | | Maximum Assignment Duration (Days) | 0 (unlimited) | When set above zero, temporary and loaner assignments get an auto-calculated expected return date. | | Asset Number Prefix | (blank: AST and SWL) | Starts every asset number the app generates — hardware as `PREFIX-00001`, software licenses as `PREFIX-SW-00001`. Letters and digits only, up to 8. Numbers already issued keep the prefix they were created with. | | Require a category on imported devices | On | When on, a device-discovery provider that creates assets cannot be saved without a Default Category. Every asset needs a category either way: a synced device whose category cannot be worked out is skipped, not created. | | Allow Custom Categories | On | Admins can create new categories beyond the defaults. | | Asset Form › Extra fields | (none) | Up to 30 admin-defined fields (text, long text, number, date, dropdown, or yes/no), each shown on hardware, software, or both, and optionally required when someone adds or edits an asset. Renaming a field keeps its saved values; removing one hides it and keeps the values until it is restored. | | Assignment and approval notifications | On | Email and in-app notification when an asset is assigned, approval is requested, or approval is granted/denied. | | Custody confirmations and disputes | Same as **Assignment and approval notifications** until saved | Tells whoever issued an asset that the employee confirmed receipt — or reported that it never arrived, arrived damaged, or is the wrong item. | | Return and custody-end notifications | On | Tells the receiving admin when an employee returns an asset, and tells an employee when an asset is taken off their custody by someone else. | | Maintenance notifications | On | Email and in-app notification for upcoming and overdue maintenance. | | Send contract renewal emails | Off | Starts the nightly sweep that emails the chosen recipients when a contract enters its renewal-notice window. | | View Access | Member, Manager, Admin, Super Admin | Which roles can see the Dashboard and Assets tabs. | | Management Permissions | Manager, Admin, Super Admin | Which roles can manage assets (assign, return, edit, schedule maintenance). Reports have their own picker, **Who can open Reports?** | | Administrative Permissions | Admin, Super Admin | Which roles can maintain Categories, Vendors, Contracts, facilities and stocktakes. Settings is open to business admins and Asset Pro admins. | ## 6. More help - **Asset Pro FAQ** — specific setup, operating, and troubleshooting questions. - Ask AI — the assistant answers questions about Asset Pro from these articles. - **My Assets** — employees can see their own assigned assets from the Dashboard's "My Assigned Assets" widget. This is the self-service view; it does not require Manager or Admin access. **Keywords:** asset management, asset tracking, IT inventory, asset assignment, hardware tracking, software licenses, license compliance, depreciation, warranty tracking, maintenance scheduling, barcode scanning, QR code, asset audit, stocktake, device refresh, end of life, EOL, chain of custody, asset_pro, asset-pro --- # Asset Pro FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-20 Answers to common setup and operating questions about Asset Pro — for the admin running it. # Asset Pro FAQ Answers to common setup and operating questions about Asset Pro. For what the app is and how to set it up from scratch, see the [Asset Pro Overview](/help/articles/asset_pro_app_overview). --- ## Setup ## Do I need to create categories before I can add assets? Yes. Every asset you add by hand requires a category — that is not configurable. Devices synced from Lansweeper, Intune or Jamf need one too: a device whose category cannot be worked out is skipped, not created. (The **Require a category on imported devices** setting only decides whether a device-discovery provider that creates assets must name a Default Category before it can be saved.) If your organization has no categories yet, Asset Pro auto-creates twelve defaults the first time you open the Categories tab — eight hardware categories (Laptops, Monitors, Mobile Phones, Tablets, Keyboards & Mice, Headsets, Printers, Network Equipment) and four software categories (SaaS Subscriptions, Desktop Applications, Development Tools, Security Software). You can rename, add, or deactivate them at any time. ## Who can see what after I enable the app? By default, all four organizational roles — Member, Manager, Admin, and Super Admin — can view assets. Managers and above can access Reports. Only Admins and Super Admins see Vendors, Contracts, Categories, Facility Layouts, and Settings. You can customize which roles appear in each tier from Settings. App Admins (users granted the Asset Pro app-admin role) always have full access regardless of the role-tier settings. --- ## Permissions and access ## Why can't one of my managers see the Reports tab? Reports are governed by their own setting, **Settings → Who can open Reports?** By default it admits managers and above. If it was narrowed (to admins, or to a group), anyone outside it loses the tab. Pick **Managers** there, or add the person to the chosen group. ## Why is the Scanner tab missing? The Scanner tab only appears when the **Barcode Scanning** toggle is turned on in Settings. It is on by default, but if someone disabled it, the tab disappears for everyone. Turn it back on and the tab returns immediately. --- ## Day-to-day ## How does depreciation work, and can I change the rate? Asset Pro uses straight-line depreciation. When auto-depreciation is enabled (it is by default), each asset's current value is recalculated from its purchase price, the annual depreciation rate, and the category's useful life. The default annual rate is **20%**, and the salvage-value floor defaults to **$0.00**. You can change the rate in **Settings → Default Depreciation Rate**. Accelerated or double-declining methods are not supported. ## What happens when an employee checks out an asset? When an asset manager assigns a device and assignment approvals are off (the default), the asset moves to **Assigned** status immediately, the employee appears as the current assignee, and — if assignment notifications are enabled — they receive an email and an in-app notification. If approvals are on, the asset shows **Pending Approval** and the employee's direct manager is notified to approve or deny. An employee who asks the Asset Pro assistant in Ask AI for a device always files a request for their manager to approve, whatever the approvals setting. Once approved, the assignment date is set and the asset status changes to Assigned. ## What are the assignment types, and does the app enforce return dates? Three types exist: **Permanent**, **Temporary**, and **Loaner**. By default the maximum assignment duration is unlimited. You can set a cap in **Settings → Maximum Assignment Duration (Days)** — it applies to Temporary and Loaner assignments only; when a value greater than zero is saved, those assignments automatically receive an expected-return date calculated from that cap. Assignments past their expected-return date appear in the Overdue Returns count on the dashboard. ## How do software license seats get tracked? Each software asset can record a license type — Per-Seat, Per-Device, Site-Wide, Concurrent, Subscription, or Perpetual — along with a total seat count. Seats are allocated to individual users or hardware devices. When all seats are allocated, the asset's compliance status changes to **At Capacity**. If an allocation would exceed the total, Asset Pro blocks it. Site-wide and perpetual licenses with no seat count are always considered compliant. ## I assigned an asset — why does the employee say they never received it? Every new assignment starts with an acknowledgement status of **Pending**. The employee must confirm receipt in their My Assets view. If they report a problem — wrong item, damaged, or never arrived — they can dispute it, which notifies the person who assigned the asset and the employee's own manager (plus anyone in the custody group your admin picked who can manage assets). Check the assignment's acknowledgement status on the Assignments tab. --- ## Notifications and alerts ## Who gets warranty expiration alerts? Per-asset warranty alerts go only to the asset's current assignee, starting **60 days** before the warranty end date (configurable in Settings). A separate weekly warranty digest covering all expiring and expired warranties goes to the admin-configured warranty recipients, or to app admins if none are configured. Unassigned assets produce no individual alert — they surface only in the weekly digest. ## Who receives maintenance reminders? Per-asset maintenance reminders go to the asset's current assignee and the person who requested the maintenance, plus any admin-configured notification group. If a maintenance record has no stakeholders, it skips the individual email and appears only in the weekly maintenance digest, which goes to the configured notification group or to app admins. ## When do software subscription alerts fire? Subscription expiry alerts are emailed only once **Send software lifecycle emails** is switched on in Settings — it is off by default. When it is on, they go to the asset's current assignee and its creator (or the group picked under **Who gets software license alerts**). The default alert window is **30 days** before the subscription end date. You can change this in **Settings → Subscription Alert Days**. --- ## When something looks wrong ## My employee says they can't see Asset Pro at all Three things to check. First, the app must be enabled for your organization — if it is not, everyone is redirected away. Second, the app may be restricted to specific user groups; someone outside the allowed audience sees "Access denied. The Asset Pro app is open only to certain people in your organization." Verify both in the app's marketplace settings. Third, **Settings → View Access** decides which roles can open the asset register; someone outside it can still open My Assets for the equipment they hold. ## I created an asset but there is no asset number on it Asset numbers are auto-generated on creation. Hardware assets get the prefix **AST** (producing numbers like AST-00001), and software assets get **SWL** (SWL-00001). If you configured a custom prefix in your app settings, the prefix changes accordingly — software assets then get your prefix with a `-SW` suffix. If the number is missing, the asset was likely imported without one; editing and saving it will generate one. ## An asset is stuck in "Pending Approval" but nobody has a pending approval A device shows **Pending Approval** while a request for it waits for a decision. Requests wait when **Settings → Require Assignment Approvals** is on, and an employee's request made through Ask AI always waits, whatever that setting says. Three things usually keep one waiting: - **Nobody has decided it yet.** The request goes to the employee's manager, and any Asset Pro admin can decide it too. Open **Assignments → Pending Approval** to approve or deny it. - **Nobody is able to approve it.** No one can approve their own request, so when the person who asked is the only Asset Pro admin and has no manager here, nobody was asked. They can withdraw the request from its page, or an admin can turn off **Require Assignment Approvals**. - **Another request is waiting on the same device.** Deciding one request leaves the device in Pending Approval while another still waits, so decide each one. Approving moves the device to Assigned. Denying (or withdrawing) a request puts the device back to Available — or to Assigned when someone still holds it — unless another request is still waiting on it, in which case it stays Pending Approval for that one. ## Why didn't the end-of-life date auto-calculate for my software asset? End-of-life dates auto-calculate only for hardware assets, using the deployment date (or purchase date) plus the category's useful-life months. Software assets are skipped because their EOL dates are set by the vendor, not derived from a purchase date. Enter the EOL date manually on the software asset's detail page. --- ## Reports and exports ## What reports are available, and who can run them? Six reports: **Inventory**, **Assignments**, **Depreciation**, **Maintenance**, **Device Refresh**, and **EOL Timeline**. Each can be exported to CSV, PDF, or Excel. Who can open them is set by **Settings → Who can open Reports?** — by default managers and above. ## What does the Device Refresh report measure? It lists active hardware whose purchase date is older than a configurable threshold (default **36 months**); software licenses are not devices and are left out. Each device receives a replacement priority — Low, Medium, or High — scored from its age, warranty status, and condition grade. Use it to plan your next hardware-refresh budget cycle. --- ## Licensing and limits ## Does Asset Pro require a licence? Yes. Asset Pro requires a OneMango licence. An admin enables it from Admin → Apps → All Apps, and no employees see it until that is done. ## Are there limits I should know about? - **Extra fields on the asset form:** 30 maximum, with types Text, Long text, Number, Date, Dropdown, and Yes / No. A required field is asked when someone adds or edits an asset; imports, device sync and purchase orders still create the asset and mark it "Missing info". - **Depreciation method:** straight-line only; no accelerated or double-declining. - **Barcode symbology:** auto-detected from the value you enter — EAN-13 (13 digits), UPC-A (12 digits), QR (8+ alphanumeric characters), or Code 128 (everything else). - **Facility layouts:** pallet racking is the only shipped layout type. - **Contract renewal notice:** defaults to 30 days before the contract end date. - **Inspection frequencies:** Daily, Weekly, Monthly, Quarterly, or Annually per category. --- ## More help - [Asset Pro Overview](/help/articles/asset_pro_app_overview) - Ask AI — the assistant answers Asset Pro questions from these articles. **Keywords:** faq, asset management, asset tracking, IT inventory, depreciation, warranty alerts, maintenance scheduling, barcode scanning, software licenses, license compliance, checkout, assignment approvals, device refresh, custom fields, not showing, permissions, asset_pro, asset-pro --- # Audit Logs & Activity History **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-14 Four audit log surfaces — System, API, Compliance, and Employment Law — that record who changed what, when, and why across the platform. # Audit Logs & Activity History ## 1. What it is Audit Logs give admins a tamper-evident trail of changes across the platform — who did what, when, and from where. The trail is split into four surfaces, each focused on a different kind of activity: system-wide data changes, API calls, shift-assignment compliance decisions, and employment-law events. - **Enablement:** The System and Employment Law surfaces are available to any admin. The API and Compliance surfaces require the Platform Enterprise edition. API Audit Logs additionally require the "API → Manage" permission. - **What it is not:** Audit Logs record platform activity — they are not the labor-law rule engine itself (that lives in Labor & Employment Law Rules) or the content moderation queue (that lives in Content Governance). ## 2. Standing it up Audit logging is automatic — there is no setup step to "turn it on." Records begin accumulating as soon as the platform is in use. 1. Go to **Admin → System Audit Logs** (the Settings Hub card labelled "System Audit Logs"). 2. The family navigation bar at the top links the four surfaces: **System**, **API**, **Compliance**, and **Employment Law**. Each tab is shown only when the business has the required edition and the admin the required permission. 3. For the **API** tab to appear, the business must be on the Platform Enterprise edition, and the admin's role must include the "API → Manage" permission. 4. For the **Compliance** tab to appear, the business must be on the Platform Enterprise edition. 5. To confirm it is working, the System tab should already show recent change entries. No additional configuration is needed — there are no settings to enable or disable logging, and no per-surface opt-in. The Source dropdown in the System tab only lists sources that actually have data for this tenant, so an admin never sees an empty filter option. ## 3. How it fits together **System Audit Logs** are the broadest surface. They combine records from multiple sources into a single unified feed: - **System Changes** — PaperTrail version records tracking creates, updates, and deletes of core models (users, shifts, schedules, locations, departments, roles, and more). Every row shows who made the change, what fields moved from which value to which, and when. - **EPMS** — performance review lifecycle events (created, submitted, approved, archived), visible only when the Employee Performance Management app is entitled. - **HR File Manager** — file access events (viewed, downloaded, uploaded), visible only when the HR File Manager app is entitled. - **Email System** — email delivery audit events tied to EPMS notifications. The "Changed by" column shows one of three labels: the admin's name when the actor is a member of this business, "User #" when the actor exists but is not a member here (a platform-level edit), or "System" when the change was made by automation with no human actor. The "Changed by" filter dropdown is scoped to this business's members only — a platform-level actor appears in the log itself but not in the filter picker, so an admin cannot browse foreign-tenant profiles through the filter. **Privacy redaction.** Chat message bodies are withheld from the audit trail. The version row still preserves the old content — but it is not displayed, because chat's own permission model has no path for an admin to read a room they are not a member of. The audit entry still shows *that* a message was edited, deleted, or restored. **Bulk operation grouping** collapses related changes (CSV imports, auto-assignments, batch updates) into a single expandable row when the Grouped view is active. An admin can toggle between Grouped and Flat views at any time. The grouping covers ten operation types: CSV import, bulk create/update/delete, auto-assignment, auto-enrollment, scheduled job, API batch, system sync, and data migration. **API Audit Logs** record every write operation and sensitive read made through the REST API. Each entry captures the controller, action, HTTP method, request path, response status, the API token used, the acting user, and the client IP address. Entries are classified by call type: customer API, mobile app, internal service, invalid token, or unauthenticated — so an admin can distinguish legitimate integrations from probing attempts. Customer API calls are always logged regardless of HTTP method. Internal service calls are logged only for write operations (POST, PUT, PATCH, DELETE). Invalid-token and unauthenticated attempts are always logged for security monitoring. **Compliance Audit Logs** record shift-assignment compliance decisions made by the scheduling engine. Each entry is one of four event types — match calculation, compliance override, assignment blocked, or assignment allowed — and carries the decision outcome (allowed, blocked, or overridden), match and skill-match percentages, any compliance or labor-law violations detected, and the MangoScore multiplier applied. When an assignment is overridden, the log records who authorized the override, the stated reason, and whether it was flagged as an emergency override. The analytics dashboard adds two forward-looking panels beyond the audit trail itself: a weekly-hours risk view showing employees approaching the max-weekly-hours cap, and a work-context coverage view showing how much of the workforce is classified as frontline, desk, or hybrid (unclassified workers are invisible to frontline-scoped labor rules). **Employment Law Audit Logs** are the immutable compliance trail. Once written, a record cannot be updated or deleted — the model raises an error on any attempt. These logs capture events from nine source systems (handbook grader, JD optimizer, compliance grader, scheduling engine, time tracking, leave management, onboarding, policy hub, and manual entry) and mark each event as compliant or non-compliant against the applicable employment-law rule and jurisdiction. Seventeen event types are tracked, including overtime calculations, break enforcement and violations, leave approvals and denials, scheduling validations, handbook checks, pay transparency validations, training requirements, accommodation requests, and fair-chance hiring events. **Where boundaries sit:** Each of the four surfaces stores its records in a separate table with its own filters, CSV export, and analytics dashboard. The family navigation bar at the top of every surface lets an admin move between them without returning to the Settings Hub. The System tab's detail drill-down (full changeset view) is available only for System Changes entries — other sources show summary details inline on the index page. ## 4. Running it ### Reviewing system changes 1. Go to **Admin → System Audit Logs**. 2. Use the filter bar to narrow by item type, changed-by user, action (Created / Updated / Deleted), date range, or source (System Changes, EPMS, HR File Manager, Email System, Bulk Operation). 3. When no date range is specified, the view defaults to the last 7 days. 4. Click a **System Changes** entry to see the full changeset — which fields changed, from what value to what value, and who made the change. Other sources show summary details inline. 5. Toggle **Grouped / Flat** to collapse or expand bulk operations. In Grouped mode, a CSV import that created 50 users appears as one row; in Flat mode, all 50 individual entries show. ### Reviewing API activity 1. Go to the **API** tab (the Platform Enterprise edition + "API → Manage" permission required). 2. The dashboard cards show total calls, calls today, success rate, and error rate. 3. Filter by date range, controller, action, HTTP method, response status (successful / client errors / server errors), API token, or user. 4. Click an entry to see the full request details including parameters, user agent, and referrer. ### Exporting audit data 1. On any of the four surfaces, click **Export CSV**. The export applies the current filters but is not limited by the on-screen pagination — it exports the full filtered result set. 2. The CSV downloads immediately as `unified_audit_logs_YYYYMMDD.csv` (System), `api_audit_logs_YYYYMMDD.csv` (API), `compliance_audit_logs_YYYY-MM-DD.csv` (Compliance), or `employment_law_audit_YYYY-MM-DD.csv` (Employment Law). 3. Sample audit rows (loaded in development/demo environments) are excluded from the System export. ### Reviewing compliance overrides 1. Go to the **Compliance** tab (the Platform Enterprise edition required). 2. The summary cards show total calculations, total overrides, emergency overrides, and the override rate for the last 30 days. 3. Use the **Emergency only** filter to isolate emergency overrides, or the **Has violations** filter to show only entries where compliance or labor-law violations were detected. 4. Filter by event type, decision, user, or date range to narrow the list. 5. Click **Analytics** to open a dedicated dashboard with: - **Violation trends** — daily violation counts and the top-10 most common violations. - **Performance impact analysis** — how MangoScore multipliers distribute across performance tiers. - **Override patterns** — overrides grouped by authorizer and by target user, plus emergency vs. regular split. - **Weekly hours risk** — employees approaching the max-weekly-hours cap this week (requires a rest-period setting with a weekly cap configured). - **Work context coverage** — how much of the workforce is classified frontline, desk, hybrid, or unclassified (unclassified workers are invisible to frontline-scoped labor rules). ### Reviewing employment-law compliance 1. Go to the **Employment Law** tab. 2. The summary shows total events, compliant vs. non-compliant counts, and the compliance rate for the last 30 days. 3. Filter by event type (overtime calculated, break violation, leave approved, pay transparency validated, etc.), source system, jurisdiction, rule, or compliant/non-compliant status. 4. Click **Analytics** to see daily trends, event breakdown by source and document type, and recent violations. 5. Click any entry to see its full detail including the linked employment-law rule, jurisdiction, event data, and compliance status. ### Loading sample data (development / demo environments only) In a development or demo/QA tenant, the System tab shows **Load sample data** and **Show/Hide sample** buttons. Sample rows are badged "Sample", excluded from CSV exports, and never created in production tenants. This lets an admin preview what a populated audit trail looks like before real activity accumulates. ## 5. Settings Audit Logs have no admin-configurable settings — logging is always on and cannot be disabled. The key operational defaults are: | Behaviour | Default | What it means | |---|---|---| | System log default date range | 7 days | The System tab loads the last 7 days when no date range is specified | | Compliance emergency override | Off | New compliance audit entries are not flagged as an **Emergency Override** | | Employment-law compliant flag | On | New employment-law entries are recorded as compliant; the source system marks them non-compliant for violations | | Employment-law immutability | Always on | Records cannot be updated or deleted after creation — the system blocks both operations | | Chat body redaction | Always on | Chat message content is withheld from the audit trail to respect chat's permission model | ## 6. More help - **Compliance Administration** — overall compliance settings and policies - **Labor & Employment Law Rules** — the rule engine whose events appear in the Employment Law tab - Ask AI — the assistant answers questions about Audit Logs from this article. **Keywords:** audit logs, audit trail, activity history, system changes, PaperTrail, API audit, compliance audit, employment law audit, who changed what, change history, bulk operations, CSV export audit, override tracking, compliance violations --- # Background Checks App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run background checks on recruiting candidates using Checkr, Sterling, or HireRight — integration setup, ordering, adjudication, and FCRA adverse action workflow. # Background Checks ## 1. What it is Background Checks lets you order, track, and adjudicate candidate background screenings from inside the recruiting pipeline. It connects to your existing Checkr, Sterling, or HireRight account through a system integration and keeps results, adjudication decisions, and FCRA adverse-action notices in one place. - **Enablement:** Background Checks is available to every tenant with no license decision, and MangoApps adds no per-check charge — your provider bills each check. An admin must configure at least one provider integration before the app does anything. - **What it is not:** Background Checks does not replace your provider account. Provider fees are billed by Checkr, Sterling, or HireRight directly. The app orders checks, receives results (by webhook from Checkr, and by polling from all three), and handles the FCRA notices — it does not run the screenings itself. ## 2. Standing it up 1. Go to **Admin → Organization → Integrations** and add a background-check integration for your provider (Checkr, Sterling, or HireRight). Enter the API key from your provider account (for Checkr, also the webhook secret). Use the **Test Connection** button to confirm the credentials work. 2. If you connect more than one provider, go to **Job Board → Settings → Integrations** and choose which one new checks are ordered through. Checks ordered from Job Board, and from an Onboarding Hub plan for a candidate, use that one (an Onboarding Hub order for another provider is only recorded on the plan); with none chosen, the oldest connection is used. Without Job Board, open the connection you want in **Admin → Integrations** and tick **Order new background checks through this connection**. The provider's own settings page names the connection orders currently use. 3. Background Checks is visible at **Apps → Background Checks** and inside **Job Board → Background Checks**. Both surfaces show the same data. Recruiting staff (business admins, HR admins, and Background Checks or Job Board app admins) see every check. A job's recruiter and whoever added the candidate see that candidate's checks; a job's hiring manager sees their status only. 4. To confirm setup, navigate to **Job Board → Background Checks**, click **Request Background Check**, and look for the candidate picker and package selector. If no provider is connected and no checks are on file yet, an administrator is taken to **Background Checks → Settings** with "Connect a background check provider to start using Background Checks." and anyone else is told to ask an administrator to connect one. Once checks are on file, the list and every check stay open without a provider; a banner says new checks can't be ordered, with a **Connect a provider** link for business administrators. The app also surfaces inside **Onboarding Hub** plans. When a plan has a linked recruiting candidate, the Background Check tab shows existing results from the screening pipeline, and lets someone who can work that candidate (recruiting staff, the job's recruiter, or whoever added the candidate) order a check, within your **Who can order a background check?** setting. ## 3. How it fits together **Check lifecycle** — A background check moves through a fixed sequence of statuses. Understanding the sequence prevents the most common admin question ("where is this check stuck?"): > *Example: Jane Doe, Senior Accountant, Comprehensive Background Check via Checkr.* > Recruiter clicks **Request Background Check** → status is **Not Started** → Checkr invites Jane to authorize the check → **Invited** → Jane authorizes, Checkr creates the report and the screening runs → **In Progress** → Checkr returns a result → **Clear** (or **Consider** / **Suspended**) → if Clear and auto-adjudication is on, it is marked **Approved** and the process ends. The eight statuses are: - **Not Started** — check requested but not yet sent to the provider. - **Invited** — the provider invited the candidate to authorize the check. With Checkr no report exists until the candidate does. - **In Progress** — the candidate authorized and the screening is running. - **Clear** — no adverse items found. - **Consider** — adverse items found; requires adjudication. - **Suspended** — the provider paused the screening (e.g. unable to verify). - **Canceled** — a recruiting admin canceled the check before it completed. Cancel Check asks why (candidate withdrew, duplicate order, position closed, or other with a note), and the reason shows on the check's timeline to recruiting staff. - **Error** — the provider reported a failure. The recruiter is notified by email. **Adjudication** — When a check returns **Consider** or **Suspended**, it lands in the **Needs Review** queue. Recruiting staff (a business admin, HR admin, or Background Checks or Job Board app admin) review the adverse items and pick one of four decisions: - **Approve** (clear for hire) - **Reject** (do not hire — triggers the FCRA adverse action flow) - **Conditional Approval** - **Escalated** — not decided yet; the check stays in Needs Review to be decided later Only recruiting staff can adjudicate — the button does not appear for other roles. If the integration has **Auto-adjudicate clear results** turned on, checks that come back Clear skip the queue entirely and are marked Approved automatically. **FCRA adverse action** — When an adjudication decision is **Reject**, the platform starts the two-step FCRA adverse action process: 1. A **pre-adverse action notice** is emailed to the candidate automatically (if they have an email on file). The notice includes the consumer report, the provider's contact information, and the FCRA Summary of Rights. 2. A waiting period begins (5 business days by default, 1–30 business days, configurable per provider connection). If the candidate files a dispute, the final notice is held while the dispute is open. The dispute does not pause or restart the waiting period. 3. Once the waiting period has ended and no dispute is open, a daily job sends the **final adverse action notice** to the candidate. If the candidate has no email address on file, the automated notices cannot be sent. The recruiter receives an in-app notification explaining which steps must be completed manually. Every step — adjudication decisions, notice timestamps, dispute events, and provider status changes — is recorded in the recruiting audit log. **Provider sync** — Checkr results arrive through webhooks; Sterling and HireRight results arrive by polling. A scheduled sync polls the provider every 6 hours for any checks still in Invited or In Progress status. Checks older than 90 days are excluded from the sync. You can also sync a single check manually from its detail page. **Access control** — Recruiting staff see every check across the business and can adjudicate, cancel, and manage disputes. A job's recruiter and whoever added the candidate see that candidate's checks and the decision; a job's hiring manager sees the status only. On the phone, an employee who applied internally sees their own check's status — matched by the employee link on their candidate record, not by email — but the decision is hidden from them to preserve the FCRA process. **Relationship to Job Board and Onboarding Hub** — Background Checks is sold both standalone and bundled with Job Board. The check surfaces appear when either app is enabled. Each check is tied to a recruiting candidate and optionally to a recruiting job. The Onboarding Hub's Background Check tab shows the same pipeline data and can order checks through the same integration. ## 4. Running it ### Requesting a check 1. Go to **Job Board → Background Checks** and click **Request Background Check**. 2. Search for a candidate in the picker. Only candidates with an email address appear. 3. Select a screening package. Four default packages are available: - **Basic Criminal Check** — SSN verification, national criminal database, sex offender registry. - **Pro Criminal Check** — everything in Basic plus county and federal criminal searches. - **Comprehensive Background Check** — everything in Pro plus employment, education, and professional reference verification. - **Executive Background Check** — full comprehensive check plus credit report, civil court searches, media searches, and extended employment history. The integration can define custom packages that override these defaults. 4. Click **Request Background Check**. The candidate receives an FCRA disclosure and authorization email (when auto-send is on). The check starts once they authorize. A candidate can have only one active background check. If one already exists, the request page redirects back to the candidate profile. A canceled check, or an order that failed before it reached the provider, frees the candidate for a new one. ### Reviewing results 1. Open a completed check from the list or click the email notification link. 2. The detail page shows the check status, adjudication status, provider, and timeline. If adverse items were found, they appear under **Results** with a count. 3. Sensitive fields (SSN, date of birth, driver's license number) are stripped from the raw report data before display. ### Adjudicating a check 1. Go to the **Needs Review** queue (linked from the dashboard stat card) or open a check with a **Consider** or **Suspended** status. 2. Choose a decision from the dropdown: Approve, Escalated, Reject, or Conditional Approval. 3. Enter adjudication notes (required for Reject and Escalated) and submit. The decision is recorded in the audit log. Approve, Reject and Conditional Approval are final; an Escalated check can be decided later. 4. If you reject, the FCRA adverse action process starts automatically (see §3). ### Managing a dispute When a candidate disputes their report during the FCRA waiting period: 1. Open the check detail page, scroll to the **FCRA Adverse Action** section. 2. Click **Record Candidate Dispute** and enter the dispute details. The final adverse action notice is held while the dispute is open. 3. After investigating, click **Resolve Dispute & Resume**. The waiting period was not paused or restarted: if it has already ended, the final notice goes out on the next daily run; otherwise it goes out when the period ends. ### Syncing status manually Open the check detail page and click **Sync Status** to ask the provider for the latest status now. For Checkr this also works for a check still on **Invited**: it syncs once the candidate has completed Checkr's invitation. ## 5. Settings Background check settings live on the provider integration, not on the app itself. Configure them at **Admin → Organization → Integrations → (your background-check provider) → Edit**. | Setting | Where | Default | What it changes | |---|---|---|---| | Auto-adjudicate clear results | Integration configuration | Off | When on, checks that return Clear are automatically marked Approved without entering the adjudication queue | | Notify recruiter on completion | Integration configuration | On | Sends an email to the person who ordered the check, the job's recruiter, and whoever added the candidate when a check completes (hiring managers are not emailed) | | Notify on adverse items | Integration configuration | On | Sends an email when a check requires adjudication (Consider or Suspended result) | | Notify candidate on progress | Integration configuration | Off | Sends candidates an email when the check moves to In Progress. Off by default because providers usually email candidates directly | | Notify candidate on completion | Integration configuration | Off | Sends candidates an email when a check completes with a Clear result. Off by default for the same reason | | Auto-send FCRA disclosure | Integration configuration | On | Sends the candidate the FCRA disclosure and authorization request automatically when a check is ordered. Off: OneMango sends no disclosure email; your provider or your own process must | | FCRA waiting period | Integration configuration | 5 business days | The number of business days (1–30) between the pre-adverse action notice and the final adverse action notice | | Enable AI Agent | Apps → Background Checks → Settings | On | Controls whether users can query background-check data through the Ask AI sidebar | ## 6. More help - **Background Checks FAQ** — specific setup and operating questions - **Job Board App Overview** — the recruiting pipeline that feeds background checks - Ask AI — the assistant answers questions about Background Checks from these articles. **Keywords:** background check, background screening, Checkr, Sterling, HireRight, adjudication, FCRA, adverse action, criminal check, pre-adverse action, recruiting compliance, background-checks, background_checks --- # Background Checks FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Background Checks — for the admin running it. # Background Checks FAQ Answers to common setup and operating questions about Background Checks. For what the app is and how to set it up from scratch, see the [Background Checks Overview](/help/articles/background_checks_app_overview). --- ## Setup ## Do I need to configure anything before I can order background checks? Yes. An admin must first connect at least one background check provider (Checkr, Sterling, or HireRight) under **Admin > Organization > Integrations**. Until one is connected, no check can be ordered: opening Background Checks takes an administrator to its Settings page with "Connect a background check provider to start using Background Checks." and tells anyone else "Background Checks needs a screening provider connected before it can be used — ask your administrator to connect one." If a connection is later disabled, checks already ordered stay open and the page says new checks can't be ordered. ## Who can see background checks, and who can adjudicate them? Recruiting staff — business admins, HR admins, and Background Checks or Job Board app admins — see every check and can adjudicate, cancel, and record disputes. A job's recruiter and whoever added the candidate see that candidate's checks, including the decision. A job's hiring manager sees the status of their candidates' checks only. On the phone, an employee who applied internally sees the status of their own check — matched by the employee link on their candidate record, not by email — but never the decision. --- ## Permissions and access ## Why can't a manager adjudicate a background check? Adjudication, cancellation, and dispute handling are restricted to recruiting staff — business admins, HR admins, and Background Checks or Job Board app admins. A line manager does not have access to the Needs Review queue or the adjudicate/cancel actions, because FCRA-regulated results (criminal and credit records) are not a general management surface. ## Who can request a new background check for a candidate? Recruiting staff (business admins, HR admins, and Background Checks or Job Board app admins), the recruiter on the candidate's job, and whoever added the candidate — narrowed by the **Who can order a background check?** setting in **Background Checks > Settings**, which can limit ordering to admins or to chosen groups. The "Request Background Check" button only appears for users who may order for at least one candidate. --- ## Day-to-day ## Can I order more than one background check for the same candidate? Not while one is active. A candidate can have one active background check; requesting a second redirects you back to the candidate profile with a message that a check has already been requested. A canceled check, or an order that failed before it reached the provider, frees the candidate for a new one. ## Which screening packages can I choose from? Four standard packages are available by default: **Basic Criminal Check** (SSN trace, national criminal database, sex-offender registry), **Pro Criminal Check** (adds county and federal criminal searches), **Comprehensive Background Check** (adds employment, education, and reference verification), and **Executive Background Check** (adds credit report, civil court, media search, and extended history). If your provider defines custom packages, they appear automatically at order time. ## What happens when a check comes back with a "Consider" or "Suspended" result? The check moves into the **Needs Review** queue. If the **Notify when a result needs adjudication** setting is on (it is by default), the person who ordered the check, the job's recruiter and whoever added the candidate are emailed, along with the people who can decide (HR admins and Background Checks or Job Board app admins; business admins when no one is designated). Hiring managers are not emailed — they see the status on the check page. Recruiting staff then record a decision — Approve, Reject, Conditional Approval, or Escalated. Notes are required for Reject and Escalated. Approve, Reject and Conditional Approval are final; an Escalated check stays in Needs Review to be decided later. The decision, the adjudicator, and the timestamp are logged in the audit trail. ## How does auto-adjudication of clear results work? When **Auto-adjudicate Clear Results** is enabled on the provider integration, any check that comes back "Clear" is automatically adjudicated as Approved. The notes record it as auto-adjudicated, and no adjudication-completed email is sent (the report-completed email already announces the outcome). Checks with "Consider" or "Suspended" results always go to the manual queue regardless of this setting. ## How does FCRA adverse-action handling work? When a check is adjudicated as Rejected, the app sends the candidate a pre-adverse action notice automatically (if a candidate email is on file). It then waits the configured number of business days before sending the final adverse-action notice. A daily job checks for checks whose waiting period has elapsed and sends the final notice. If the candidate disputes the report, recording the dispute holds the final notice while the dispute is open. It does not pause or restart the waiting period: once the dispute is resolved, the final notice goes out on the next daily run if the period has ended. The full sequence — pre-notice, waiting period, dispute, final notice — is logged in the audit trail. ## What if the candidate has no email address on file when adverse action is triggered? The pre-adverse action notice cannot be sent automatically. The recruiter and adjudicator receive an in-app notification explaining that FCRA requires a pre-adverse action notice and a waiting period, and asking them to complete those steps manually. --- ## When something looks wrong ## "Background Checks app is not enabled for your business." or "Connect a background check provider…" These are different messages with different fixes: - **"Background Checks app is not enabled for your business."** — neither Background Checks nor Job Board is turned on for your organization. An admin turns one on in the Apps Marketplace. - **"Connect a background check provider to start using Background Checks."** (shown to admins) or **"…ask your administrator to connect one."** (shown to everyone else) — the app is on, but no provider is connected. An admin connects Checkr, Sterling, or HireRight under **Admin > Organization > Integrations** and checks the connection is enabled. - **"No screening provider is connected, so new background checks can't be ordered…"** — your organization already has checks, so the list and every existing check stay open (including the FCRA steps on them), but ordering a new check, syncing with the provider and resending a consent email wait until an admin reconnects a provider. ## My check has been stuck on "Invited" or "In Progress" for days — is it updating? Status updates arrive from the provider via webhooks (live for Checkr) or via the automatic polling backstop every 6 hours (all three providers). Pending checks are polled for up to 90 days after they are created. You can also force an immediate sync by opening the check detail page and clicking **Sync Status** — for Checkr this includes a check still on "Invited", which syncs once the candidate has completed Checkr's invitation. If the status still does not update, verify that the provider integration is active and the API credentials are correct under **Admin > Organization > Integrations**. ## I got a background check notification but I can't find the check Users outside recruiting staff see only checks for candidates they added or jobs where they are the recruiter (a job's hiring manager sees their candidates' status only). If you received a notification as part of the recruiting team but the candidate was created by someone else, ask an administrator or HR admin to share the check details. ## Why did my candidate's background check disappear from the list? It did not disappear — the list is filtered. Check whether a status or adjudication filter is active. Recruiting staff see all checks; other users see only checks for their own candidates or jobs. --- ## Notifications ## Which notifications does Background Checks send, and can I turn them off? Three recruiting-team notification settings are configured per provider connection under **Admin > Organization > Integrations** (the connection's **Notifications** card): 1. **Notify when a check completes** — on by default. 2. **Notify when a result needs adjudication (consider / suspended)** — on by default. 3. **Notify when a check is requested** — off by default. Each person can also mute these with their own **Recruiting Notifications** preference. Candidate-facing progress and completion emails are off by default (providers usually email candidates directly). An admin can enable them on the connection. The FCRA disclosure email follows the connection's **Auto-send FCRA disclosure & authorization** setting. The pre-adverse and final adverse-action notices are not toggleable — they are a legal requirement. --- ## Licensing and limits ## Does Background Checks require a licence? No. Background Checks is available to every tenant with no licence to purchase. Your screening provider (Checkr, Sterling or HireRight) bills each check you order under your agreement with them; MangoApps adds no per-check charge of its own. ## Are there limits I should know about? - **Results per page:** 25 on desktop, 20 on mobile. - **Ask AI agent:** returns up to 50 checks per request (default 20). - **FCRA waiting period:** configurable from 1 to 30 business days per provider connection; the default is 5 business days. - **Status polling window:** pending checks are polled for status updates for up to 90 days after creation. - **One active check per candidate** — a second check cannot be requested while one is active; a canceled check, or an order that failed before reaching the provider, frees the candidate. --- ## More help - [Background Checks Overview](/help/articles/background_checks_app_overview) - Ask AI — the assistant answers Background Checks questions from these articles. **Keywords:** faq, background check, adjudication, adverse action, FCRA, screening, Checkr, Sterling, HireRight, consider result, pre-adverse action, dispute, background-checks, background_checks --- # Background Tasks & Job Monitoring **Category:** System-features **Section:** Advanced Features **Updated:** 2026-08-12 How the platform-wide background task tracker works — progress monitoring, cancellation, export downloads, and email notifications for imports, exports, and bulk operations. # Background Tasks ## 1. What it is Background Tasks is the platform-wide tracker for long-running operations. When anyone triggers a large import, export, or bulk update, the work runs in the background and a task card tracks its progress, outcome, and errors. The page is at **Background Tasks** in the user dropdown menu (top-right navigation bar). - **Enablement:** Background Tasks is a built-in platform feature — not a licensed app. It is available to every authenticated user automatically. There is no admin toggle to enable or disable it. - **What it is not:** Background Tasks is not an admin dashboard across all users. Every user sees only their own tasks. There is no cross-user view. ## 2. Standing it up Nothing to configure. Background Tasks is live for every user from the moment they have an account. 1. Any user triggers a long-running operation from elsewhere in the platform — for example, importing users from a CSV, exporting a Power Table, or running a bulk leave-balance recalculation. 2. A task card appears at **User menu → Background Tasks** with a live progress bar. 3. A badge on the **Background Tasks** menu item shows the count of active (pending or processing) tasks. 4. When the task finishes, the platform sends an email notification with a summary and a link back to the task detail page. There are no prerequisites, no role assignments, and no settings to configure before Background Tasks works. ## 3. How it fits together ### Task lifecycle Every background task moves through a fixed set of statuses: - **Pending** — the task is queued and waiting for a worker to pick it up. - **Processing** — the worker is actively running the operation. A progress bar shows records processed out of total. - **Completed** — the operation finished. If some individual records failed (e.g. invalid rows in an import), the task still completes but shows an error count alongside the success count. - **Failed** — the entire operation could not finish (e.g. the source file was unreadable or an unrecoverable error occurred). - **Cancelled** — an admin or the user stopped the task from the UI, or the platform cancelled it automatically (see below). A cancelled status always wins: if a user cancels a task while it is processing, the task transitions to cancelled regardless of any in-flight work. ### What creates tasks Background tasks are created automatically by more than 50 operations across the platform. The most common categories: - **Imports** — user CSV imports, leave-balance imports, skill imports, policy imports, ticket imports, Power Table imports. - **Exports** — user exports, leave-balance exports, Power Table exports, conversation exports. - **Bulk operations** — bulk approve timesheets or schedules, bulk user actions (deactivate, restore, permanently delete), bulk skill verification, bulk leave-policy assignment. - **Sample data** — loading or clearing sample data from Admin settings. - **AI drafts** — content generation tasks triggered by AI features. Each task type is labelled automatically (e.g. "Import: Users", "Export: Leave Balance", "Sample data: Shifts"). ### Email notifications When a task completes or fails, the platform sends an email to the user who started it. The completion email includes a summary with total, successful, and failed record counts, plus up to 10 inline errors. The failure email includes the error details. These emails always send — they are not in a user-configurable notification category. One exception: scheduled CI pipeline tasks do not send these emails by default, unless that particular task type is explicitly opted in. ### Automatic cancellation When an admin disables a marketplace app, all active background tasks associated with that app are cancelled automatically. Additionally, when a job starts executing, it checks whether the associated app is still enabled — if it was disabled between enqueue and execution, the task is cancelled before any work begins. ## 4. Running it ### Viewing your tasks 1. Click your **user avatar** (top-right) and select **Background Tasks**. 2. The page shows all your tasks, newest first, 25 per page. 3. Use the **status tabs** (All Tasks, Pending, Processing, Completed, Failed, Cancelled) to filter by status. 4. Use the **Task type** dropdown to filter by operation type (e.g. show only imports). 5. Active tasks display a live progress bar that updates automatically. If progress stalls for more than two minutes, a notice appears: *"This is taking longer than expected."* ### Cancelling an active task From the task card, click **Cancel**. A confirmation dialog explains that the work stops but the task row is kept in your history. The task transitions to the cancelled status and the underlying job is discarded so it cannot retry. ### Downloading an export file When an export task completes, a **Download** button appears on the task card. Click it to download the generated file (CSV, Excel, etc.). The download is only available after the task reaches the completed status. ### Viewing task details Click the task title to open the detail page. This shows the full task card, a description (if the originating operation provided one), and a **Result Data** section with any structured output the job recorded. The detail page also shows all retained errors (the list view caps at 25). ### Dismissing a finished task Click **Dismiss** on any finished (completed, failed, or cancelled) task to remove it from your history. This deletes the task record permanently. ### Clearing history Click **Clear History** at the top of the page to remove all finished tasks matching your current filter. Active tasks are never cleared — the button only affects completed, failed, and cancelled tasks. ## 5. Settings Background Tasks has no dedicated settings surface. It is a built-in platform feature with no configurable options. The behaviour is fixed: | Behaviour | Value | Source | |---|---|---| | Default task status | Pending | Every task starts here the moment it is queued | | Progress poll interval | 3 seconds | How often an active task card refreshes itself | | Stall warning threshold | 2 minutes of no progress change | When the "taking longer than expected" notice appears | | Tasks per page | 25 | The Background Tasks list | | Completion/failure email | Always sent (not user-configurable) | Goes to whoever started the task | ## 6. More help - **AI Operations** — the admin surface for governing autonomous AI agents (pause, resume, approvals, trust levels) - Ask AI — the assistant answers questions about Background Tasks from these articles. **Keywords:** background tasks, background task, job monitoring, import progress, export progress, bulk operation, task failed, task cancelled, cancel task, download export, clear history, task stuck, processing --- # Ballots App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-18 How to set up and run structured, auditable votes on documents and people — Yes/No and Election styles — with frozen voter rosters, comment policies, auto-approval, and a full audit trail. # Ballots ## 1. What it is Ballots lets you run structured, auditable votes on documents or people. A ballot can be a simple Yes/No decision (approve a policy, confirm a candidate) or a multi-option Election (choose among up to 10 candidates or documents). Every vote is attributable, every change is logged, and the voter roster is frozen at publish so late membership changes cannot alter an in-progress vote. - **Enablement:** Ballots requires a license. An admin enables it from Admin → Apps → All Apps; it is not active by default. - **What it is not:** Ballots is not a survey or a poll. It produces a recorded outcome (Approved, Rejected, Winner declared, or Closed – no winner) with an audit trail. For lightweight opinion-gathering without an outcome, use the News Feed poll or a Survey. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, enable **Ballots** for your business, and publish it to users. Until it is published, only admins and Ballots contributors can open Ballots — the app shows a banner saying so — while a ballot published in the meantime still sends voting notices to the employees on it and closes on schedule with no employee votes. 2. Open **Ballots → Settings**. Review **Who can create ballots?** — the default is **Only Ballots admins and contributors can create** (businesses already using Ballots before September 2026 keep **Any member can create**). To let members create, choose **Any member can create**, or **Ballots admins, contributors and members of specific groups** and pick the groups in the group picker that appears under that choice. To let one person create without Ballots settings, make them a Ballots contributor under **Apps → Ballots → Admins & Contributors**. (Ballots admins are App Admins, Admins and Super Admins.) 3. Under **Analytics access**, choose who can see the Analytics tab: **Ballots admins only** (the default), or **Ballots admins and members of specific groups**. 4. Under **Vote labels**, confirm or customize the three vote-button labels (default: Affirmative / Negative / Abstain). These apply to every Yes/No ballot. 5. Under **Auto-approval**, decide whether Yes/No ballots should be approved automatically at close when the affirmative votes reach a threshold share of all eligible voters (default: Off, threshold: 60%). This applies organization-wide, to every Yes/No ballot when it closes — including ones already open; creators cannot override it per ballot. The threshold box is greyed out while auto-approval is off, and its saved value is kept. 6. Under **Defaults for new ballots**, set the two defaults that creators can still change on each ballot: **Allow voters to change their vote before close** (default: On) and **Show live results to members while a ballot is open** (default: Off). 7. Under **Ballot notifications**, turn the six notification switches on or off (see §5 below). 8. The Ballots widget on the home dashboard shows each member the open ballots they can still vote on. No separate widget configuration is needed. **One choice needs a second step:** **Ballots admins, contributors and members of specific groups** needs at least one group. If you save that choice with no group selected, only Ballots admins and contributors can create — the save warns you, and the page then shows **Only Ballots admins and contributors can create**. ## 3. How it fits together **Two choices on the form, four combinations.** Every ballot answers two questions on the form: **What's on the ballot?** — **Document** or **People** — and **Ballot type** — **Yes/No** (Affirmative, Negative, or Abstain) or **Election** (voters pick from multiple options). Combining them gives four shapes: | What's on the ballot? · Ballot type | What voters decide | Example | |---|---|---| | Document · Yes/No | One document, approve or reject | "Approve the updated travel policy" | | Document · Election | Up to 10 labeled options, pick a winner | "Choose among three vendor proposals" | | People · Yes/No | One person, affirm or reject | "Confirm the new safety officer" | | People · Election | Up to 10 candidates, elect a winner | "Vote for Employee of the Quarter" | What's on the ballot and the ballot type can be changed while a ballot is a draft or scheduled. Once voting opens they are locked; to change them after that, duplicate the ballot and publish the copy. On a People · Yes/No ballot, the person on the ballot can vote on it if they are in the audience. To stop that, after publishing open **Manage voters**, choose **Specific members** and set them to **Can't vote**. **Voter roster — frozen at publish.** When a ballot is published, the app resolves the audience you picked (everyone, groups, or individual people) into a concrete list of members and snapshots it. From that point, group membership changes do not change the roster. Someone who joins the group after publish is not on the voter list and cannot vote. Someone who leaves the group after publish stays on it: they can still vote and still count toward turnout until the ballot's creator or a Ballots admin sets them to **Can't vote** in **Manage voters** (on a ballot that isn't resolved yet). The creator and Ballots admins can switch any member's voting rights on or off there. **Statuses and lifecycle.** A ballot moves through a defined sequence: > Draft → Scheduled (if a future open date is set) → Voting open → Closing soon (last 24 hours, a display state) → Closed – pending decision → **Approved** or **Rejected** (Yes/No), or **Winner declared** or **Closed – no winner** (Election). The lifecycle job runs every 10 minutes to open scheduled ballots, close expired ballots, auto-approve eligible Yes/No ballots, ask the creator (or a Ballots admin, if the creator has left) to record an outcome for a ballot that closes without one, and send closing reminders — 24 hours before close, or halfway through a voting window shorter than two days. Ballots also self-heal when viewed — if a scheduled ballot's open time has passed, it transitions to Voting open the moment anyone opens the list or detail page, without waiting for the next job tick. **Auto-approval (Yes/No only).** When auto-approval is turned on in Settings, a Yes/No ballot that closes with an affirmative share at or above the threshold is automatically approved. The affirmative share is measured against *all eligible voters*, not just those who voted — so a ballot where 1 of 87 voters said Yes reads ~1%, not 100%. Elections are never auto-approved; someone has to declare the winner or close the election with no winner. **Comment policy.** Each Yes/No ballot has a per-choice comment policy: the creator can set the comment for each choice (Affirmative, Negative, Abstain) to **Optional**, **Required**, or **Not allowed**. The default is Optional for Affirmative and Abstain, Required for Negative. Elections have a single comment policy that applies to the whole vote. **Discussion thread.** Vote justifications are mirrored into a real, repliable discussion thread (the Comments tab on a ballot). When a voter re-votes, the same comment is updated in place so replies survive. On each ballot, the creator sets who can comment and who can read comments separately: all members, voters only, or admins only. **Result visibility and availability.** Two independent controls determine who sees results and when. *Who can view results* is **Everyone**, **Voters only**, or **Admins only**. *Result availability* determines timing: **Real-time** (results update as votes come in) or **After ballot closes** (the tally is hidden until voting ends). Both are set per ballot by the creator. **Election seats.** For Election-style ballots, the creator sets how many selections each voter may make: **Pick 1** (the default) or **Pick up to** 2–9 — always fewer than the number of options on the ballot. When the winner is declared, the system elects the top candidates by vote count; nobody picks them by hand. If candidates are tied for the last seat, the tie is broken by ballot order, and the confirmation and the ballot history say so. If nobody voted, there is no winner to declare: re-open the ballot for more voting, or close it with no winner. (An older election with no more candidates than seats is the exception. It can still be declared without votes, every candidate is elected, and the confirmation says the result doesn't come from votes.) **Audit trail.** Every consequential action on a ballot — created, opened, edited, vote recorded, voter list changed, vote value changed, closed, approved (manually or automatically), rejected, winner declared, closed with no winner, re-opened, re-circulated — is logged with a timestamp, the person who did it (or "System" for automated actions), and a description. The full trail is in the **Ballot history** window (the ballot's ⋮ Actions menu), which has an **Export to Excel** button. Deleting a ballot deletes its history too. **Roles.** Ballots admins (App Admin, Admin, and Super Admin) see every ballot in the business on the Dashboard and My Ballots list, can open Settings, and can act on any ballot (record the outcome, manage voters, change votes, re-open, re-circulate). Analytics is open to Ballots admins and to anyone the **Analytics access** setting adds. Regular members see only ballots they created or are on the voter roster of. A ballot's creator can take the same actions on it as a Ballots admin, with two exceptions: once votes have been cast, only a Ballots admin can delete the ballot, and re-circulating also needs permission to create ballots. **Navigation.** The app has four tabs in the sidebar: **Dashboard** (all members), **My Ballots** (all members), **Analytics** (Ballots admins, plus anyone **Analytics access** allows), and **Settings** (Ballots admins only). On a phone, the Dashboard opens its mobile view at `/m/apps/ballots`. ## 4. Running it ### Creating a ballot 1. Go to **Ballots → My Ballots** and click **New ballot**. (The button appears only for people the **Who can create ballots?** setting allows.) 2. Under **Who can vote**, add groups, people or everyone — the members they cover when you publish become the frozen voter roster. 3. Enter a title (required, up to 100 characters) and optional description. 4. Under **What's on the ballot?** choose **Document** or **People**, and under **Ballot type** choose **Yes/No** or **Election**. For a People election, pick up to 10 candidates; for a Document election, add up to 10 option documents. 5. Set the comment policy, voting instructions, open/close dates, result visibility, and whether revoting is allowed. 6. Click **Save as draft** to save without publishing, or **Save and publish** to freeze the roster and open (or schedule) the ballot. ### Reminding members who haven't voted While voting is open, the ballot's creator or a Ballots admin can press **Remind members who haven't voted** in the ballot's **Voting window** panel, under the turnout. It sends one email and Inbox reminder to every member who can vote and hasn't yet, and the panel says how many that is before you send. You can send one reminder every 24 hours; until then the panel says when the next one can go, and once it has gone, how many members it was sent to. A duplicate or a re-circulated round starts with no reminder sent. The reminder is also recorded in **Ballot history**. It is separate from the automatic reminder before voting closes, and each member's own Ballots notification settings still apply. Ask AI can send it too ("remind the people who haven't voted on the parking ballot"). ### Resolving a ballot After voting closes, the ballot's creator or a Ballots admin records the outcome from the **Record the outcome** panel on the ballot's Results tab: - **Yes/No:** Approve or Reject. If auto-approval is on and the affirmative votes reach the threshold share of all eligible voters, the ballot is approved automatically at close. (Yes/No ballots are no longer declined; one declined earlier keeps its **Declined** label.) - **Election:** **Approve (declare winner)** — the system elects the top candidates by vote count — or **Close with no winner**, which elects nobody and shows **Closed – no winner**. An election can't be rejected. If nobody voted, it can't be declared: re-open it for more voting, or close it with no winner. (An older election with no more candidates than seats can still be declared.) Until an outcome is recorded, an election stays **Closed – pending decision**. ### Re-opening and re-circulating Both are in the ballot's ⋮ Actions menu. - **Re-open ballot** sets a new close date and moves a closed or resolved ballot back to Voting open. Existing votes are kept, and any recorded outcome is cleared. - **Re-circulate ballot** starts a fresh round on a closed or resolved ballot: you pick who can vote and a new close date, all existing votes are permanently deleted, the roster is re-snapshotted from the audience's current members, and the new round opens straight away. ### Managing voters and changing votes - **Manage voters** (creator or Ballots admin): view the frozen roster and switch individual members' voting rights on or off. On a resolved ballot, the roster is read-only. - **Change votes** (creator or Ballots admin): on a Yes/No ballot that is open or closed but not yet decided, record a vote for a member who hasn't voted, or change a recorded vote if revoting is allowed. A comment is required for every change. On drafts, scheduled ballots, elections and decided ballots the window is read-only, and the menu calls it **View votes**. ### Reviewing analytics Ballots admins — and anyone **Analytics access** allows — can go to **Ballots → Analytics**. The analytics dashboard shows all-time metrics across the organization: - **Ballots run** — ballots that have opened for voting. Drafts and scheduled ballots are not counted. - **Avg. turnout** — average share of eligible voters who voted, across the same ballots. A ballot that drew no votes counts as 0%. - **Auto-approved** — percentage of closed Yes/No ballots that were approved automatically. - **Avg. time to decide** — average calendar days from opening to the outcome being recorded (Approved, Rejected, Declined, Winner declared, or Closed with no winner). - **Participation rate over time** — average turnout of the ballots whose voting closed each week, for the last 12 weeks. - **Vote choice mix** — how the votes on Yes/No ballots split between Affirmative, Negative and Abstain. - **Fastest and slowest time to outcome** — up to five ballots each; a ballot never appears in both. - **Approval outcomes** — how decided ballots were resolved: approved automatically, approved manually, winner declared or closed with no winner (elections), rejected, or declined. - **Highest turnout ballots** — the five ballots with the highest participation rate. - **Most active voters** — the five members who voted on the most ballots. ### Exporting data - **Export to Excel** in the **Change votes** window downloads the roster with each member's department, vote and comment. - **Export to Excel** in the **Ballot history** window downloads the full audit trail. - **Export** on the Analytics page downloads ballots with their type, status, outcome (Auto-approved, or Approved by the person who recorded it), turnout, days open and days to decide. Ballots admins get every ballot, including drafts and scheduled ones. Anyone else with Analytics access gets the ballots the page measures, which leaves out drafts and scheduled ballots. All exports are Excel workbooks (.xlsx). ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Enable Ballots AI agent | Settings → Ballots AI agent | On | Members can work with Ballots from Ask AI — find ballots waiting for their vote, look up results they are allowed to see, and cast or change their own vote. Ballot creators and Ballots admins can also record outcomes, re-open and re-circulate ballots, and review a ballot's history. | | Who can create ballots? | Settings → Who can create ballots? | Only Ballots admins and contributors can create | Any member, only Ballots admins and contributors, or those plus members of specific groups. | | Who can see Ballots analytics? | Settings → Analytics access | Ballots admins only | Ballots admins only, or Ballots admins plus members of specific groups. Anyone else who opens Analytics is sent back to the Dashboard with "You don't have access to that section of Ballots." | | 'Affirmative' / 'Negative' / 'Abstain' label | Settings → Vote labels | Affirmative / Negative / Abstain | Changes the Yes/No vote-button labels across all ballots (up to 40 characters each). | | Enable auto-approval | Settings → Auto-approval | Off | When on, Yes/No ballots are approved automatically at close if the affirmative votes reach the threshold share of all eligible voters (not just the votes cast). | | Auto-approval threshold | Settings → Auto-approval | 60% | The affirmative percentage (of all eligible voters, not just the votes cast) required for auto-approval. Applies to every Yes/No ballot at close, including ones already open — not per ballot. Greyed out while auto-approval is off. | | Allow voters to change their vote before close | Settings → Defaults for new ballots | On | Pre-sets revoting on new ballots. Creators can change it per ballot. | | Show live results to members while a ballot is open | Settings → Defaults for new ballots | Off | Pre-sets result availability on new ballots. Creators can change it per ballot. | | When a ballot opens | Settings → Ballot notifications | On | Sends an email, an Inbox voting request and a push to every member who can vote and hasn't voted yet. | | When a ballot is closing | Settings → Ballot notifications | On | Reminds members who haven't voted yet — 24 hours before close, or halfway through a voting window shorter than two days. | | When a ballot is edited | Settings → Ballot notifications | Off | Tells everyone on the ballot when its details are changed. | | When a ballot is re-circulated | Settings → Ballot notifications | On | Asks members who can vote in the new round to vote again (one request per member). When it is off, the usual "voting is open" request goes out instead, if **When a ballot opens** is on. | | When a ballot's outcome is recorded | Settings → Ballot notifications | On | Tells everyone on the ballot, and its creator, when it is approved or rejected, or when an election's winner is declared or it is closed with no winner — never who won or the tally. | | When a member is added as a voter | Settings → Ballot notifications | On | Tells a member when they are given a vote on a scheduled or open ballot. | ## 6. More help - **Ballots FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about Ballots from these articles. **Keywords:** ballots, voting, election, yes no vote, ballot approval, voter roster, audit trail, auto-approve, re-circulate --- # Ballots FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-18 Answers to common setup and operating questions about Ballots — for the admin running it. # Ballots FAQ Answers to common setup and operating questions about Ballots. For what the app is and how to set it up from scratch, see the [Ballots Overview](/help/ballots_app_overview). --- ## Setup ## Do I need to configure anything before Ballots works? Yes. An administrator must enable Ballots from Admin → Apps → All Apps, the tenant must hold a licence for it, and the app must be published to users — until it is, only admins and Ballots contributors can open Ballots, and the app shows a banner saying so. Once it is enabled, Ballots admins can create ballots straight away; members can vote on any ballot they are included in. Visit **Settings** inside the Ballots app to let members create ballots too, choose who can see Analytics, set vote-label wording, turn auto-approval on or off, and control which notifications are active. ## Who can create ballots, and how do I restrict it? By default, only Ballots admins and Ballots contributors can create ballots. In **Settings → Who can create ballots?**, choose **Any member can create** to open it to everyone, or **Ballots admins, contributors and members of specific groups** and pick one or more groups in the group picker that appears under that choice. If you save the group choice with no group selected, only Ballots admins and contributors can create — the save warns you, and the page then shows **Only Ballots admins and contributors can create**. Ballots admins (App Admins, Admins, and Super Admins) can always create regardless of this setting. To let **one person** create ballots without giving them Ballots settings, a company admin makes them a Ballots **contributor** under **Apps → Ballots → Admins & Contributors**. A contributor can create ballots and manage the ones they created; they cannot open Ballots Settings or Analytics, or manage other people's ballots. (Businesses that were already using Ballots before September 2026 keep the setting they had — any member — until an admin changes it.) --- ## Permissions and access ## Who can see which ballots? Members see only ballots they are included in — ballots they created or ballots where they are on the voter roster. Ballots admins (App Admins, Admins, and Super Admins) see every ballot in the business, plus the Settings tab. The Analytics tab is shown to Ballots admins and to anyone the **Analytics access** setting adds. ## Which roles can access Analytics and Settings? **Settings** is for Ballots admins only: App Admin, Admin, and Super Admin. **Analytics** is for Ballots admins by default; in **Settings → Analytics access** you can also let members of specific groups see it. Each tab is hidden from the sidebar for everyone it isn't open to, and the routes are guarded too, so a direct link sends them back to the Dashboard — for Analytics, with the message "You don't have access to that section of Ballots." --- ## Day-to-day ## What are the two ballot types and when should I use each? **Yes/No** presents Affirmative, Negative, and Abstain choices on a single document or person — use it for policy ratification, proposal approval, or a single-candidate appointment. **Election** lets voters select from up to 10 candidates or document options, with a configurable number of seats — use it for committee elections or multi-option selection. On the form these are **Ballot type** (Yes/No or Election) and **What's on the ballot?** (Document or People). Both can be changed while the ballot is a draft or scheduled; once voting opens they are locked, and to change them you duplicate the ballot and publish the copy. ## What happens when a ballot's close date passes? Voting ends and the ballot moves to **Closed – pending decision**. If auto-approval is enabled and the ballot is Yes/No, the system checks whether the affirmative share of all eligible voters (not just the votes cast) meets the threshold. If it does, the ballot is automatically approved. Otherwise it stays pending until the ballot's creator or a Ballots admin records the outcome in the **Record the outcome** panel on the Results tab — **Approve** or **Reject** for a Yes/No ballot, or **Approve (declare winner)** or **Close with no winner** for an election. Closing with no winner elects nobody, and the election then shows **Closed – no winner**. An election can't be rejected. If nobody voted in an election, there is no winner to declare: re-open it for more voting, or close it with no winner. (An older election with no more candidates than seats can still be declared.) A ballot that closes without an outcome also puts a **Record the outcome** item in its creator's Inbox (and sends an email); if the creator has left, the Ballots admins get it instead. The item clears as soon as anyone records an outcome. ## How does the auto-approval threshold work? The threshold is a percentage measured against **all eligible voters**, not just those who voted. A ballot with 1 affirmative vote out of 87 eligible voters reads roughly 1%, even if that one person is the only voter. The threshold is set in **Settings → Auto-approval** and applies to every Yes/No ballot at close — including ballots that are already open, so changing it changes how those ballots are decided. It accepts values from 1% to 100%; the default is 60%. The threshold box is greyed out while auto-approval is off, and its saved value is kept. Auto-approval does not apply to elections. ## Can I customize the vote button labels? Yes. Go to **Settings → Vote labels**. You can rename the Affirmative, Negative, and Abstain labels to whatever wording fits your use case — for example "Yes", "No", "Pass" — up to 40 characters each. The labels update on all existing Yes/No ballots. ## What notifications does Ballots send, and which are on by default? Ballots has six notification switches in **Settings → Ballot notifications**: 1. **When a ballot opens** — on by default. Asks members who can vote to cast their vote. 2. **When a ballot is closing** — on by default. Reminds members who haven't voted yet, 24 hours before voting closes (or halfway through a voting window shorter than two days). 3. **When a ballot is edited** — off by default. Tells everyone on the ballot. 4. **When a ballot is re-circulated** — on by default. Asks members who can vote in the new round to vote again. If it is off, a round that opens straight away sends the usual "voting is open" request instead, as long as **When a ballot opens** is on. 5. **When a ballot's outcome is recorded** — on by default. Tells everyone on the ballot, and its creator, when a ballot is approved (automatically, or by its creator or a Ballots admin) or rejected, or when an election's winner is declared or it is closed with no winner. It says what the outcome is, never who won or the tally — members open the ballot to see results they are allowed to see. 6. **When a member is added as a voter** — on by default. Tells a member when they are given a vote on a scheduled or open ballot. A few notices are always sent and have no switch: a member is told when someone else changes their recorded vote, or removes it along with their voting rights; when voting closes without an outcome, the ballot's creator — or a Ballots admin, if the creator has left — is asked to record one; and the ballot's creator or a Ballots admin can remind the members who haven't voted at any time voting is open (**Remind members who haven't voted** in the Voting window panel, once every 24 hours). Each notice sends one email and an item in the member's Inbox; voting requests also send a push notification to the mobile app. Members who have already voted are never asked to vote again, and a member's voting request moves out of their Inbox's Needs-you list (and off the badge) as soon as they vote — a member normally has just one open voting request per ballot. Dates in these notices include the time and time zone. Each person can turn Ballots email and push on or off under **Account Settings → Notifications → Ballots**. ## What happens when I re-circulate a ballot? **Re-circulate ballot** (in the ballot's ⋮ Actions menu) starts a fresh voting round on a closed or resolved ballot. It is available to the ballot's creator and to Ballots admins, and a creator also needs permission to create ballots. You pick who can vote and a new close date. All previous votes are permanently deleted, the voter roster is re-snapshotted from the current audience (so membership changes since the first publish are now reflected), and the new round opens straight away. The prior winner flags on election items are also cleared. When the re-circulate notice is on, everyone on the new roster who can vote gets one request to vote again, and any open voting requests from the previous round are cleared from members' Inboxes. --- ## When something looks wrong ## I can't find a ballot I'm supposed to vote on Three common causes: (1) you are not on the voter roster — the roster is frozen when the ballot is published, so joining the group afterward does not add you; (2) the ballot is still in **Scheduled** status and has not opened yet — check with the creator for the open date; (3) the ballot is in **Draft** and has not been published. Ask the ballot's creator or a Ballots admin to check the voter list with **Manage voters** in the ballot's ⋮ Actions menu. ## I voted but want to change my answer — can I? Only if revoting is enabled on that ballot. The creator sets **Allow revoting while open** when creating it; new ballots start from the **Allow voters to change their vote before close** default in Settings, which is on. If revoting is off, the vote is final once cast. When a revote is allowed, the previous vote is superseded but kept in the audit history — only the latest vote counts in the tally. ## I can't see the results — it just says they're hidden The ballot's **Who can view results** setting controls who can see tallies. Options are **Everyone**, **Voters only**, or **Admins only**. Additionally, **Result availability** can be set to **After ballot closes**, which hides the tally from everyone — admins and the ballot's creator included — until voting ends. (The ballot's creator and Ballots admins can still see each member's recorded vote in **Change votes** — or **View votes** — in the ballot's ⋮ Actions menu.) New ballots use **After ballot closes** unless an admin has turned on **Show live results to members while a ballot is open** in Settings or the creator picks **Real-time**. Ask your admin which setting is in place. ## A ballot is still showing "Scheduled" even though its open time has passed The lifecycle job that transitions scheduled ballots to open runs every 10 minutes, so there can be a short delay. Opening the ballot's list or detail page also triggers the transition immediately, so navigating to the ballot resolves it. If it persists, check that the open date and time zone are set correctly on the ballot. ## How do I correct someone's recorded vote? Open the ballot, choose **Change votes** from the ⋮ Actions menu, find the voter, select the new choice, and enter a required comment explaining the correction. The change is logged in the ballot's history with the comment, the modifier's name, and a timestamp. If revoting is disabled on the ballot, you can record a first-time vote for a voter who hasn't voted, but you cannot change an existing vote. Votes can be changed only on a Yes/No ballot that is open or closed but not yet decided; on an election, a draft, a scheduled ballot or a decided ballot the window is read-only and the menu calls it **View votes**. --- ## Licensing and limits ## Does Ballots require a licence? Yes. Ballots requires a per-tenant licence and is disabled by default. An administrator enables it from Admin → Apps → All Apps. ## What are the limits I should know about? - **Candidates or document options per ballot:** up to 10 - **Ballot title:** up to 100 characters - **Vote labels:** up to 40 characters each - **Auto-approval threshold:** 1% to 100% of eligible voters - **Election seats:** Pick 1 (the default) or up to 9 selections, always fewer than the number of options - **Comment policy per choice:** Optional, Required, or Not allowed — set per choice (Affirmative, Negative, Abstain) or for the election as a whole - **Result visibility:** Everyone, Voters only, or Admins only - **Export format:** Excel workbook (.xlsx) - **Analytics window:** all-time only; no period filter - **Votes are not anonymous** — every vote is attributable with the voter's name and timestamp in the audit trail --- ## More help - [Ballots Overview](/help/ballots_app_overview) - Ask AI — the assistant answers Ballots questions from these articles. **Keywords:** faq, ballot, voting, election, yes no, threshold, auto-approval, roster, revote, audit trail, voter list, comment policy, ballots --- # Benefits Management App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run employee benefit plans, open enrollment, qualifying life events, COBRA, ACA compliance, and carrier connections in the Benefits Management app. # Benefits Management ## 1. What it is Benefits Management lets you create benefit plans, run enrollment periods, process qualifying life events, administer COBRA continuation coverage, track ACA hours, and transmit enrollment data to carriers — all from one app. - **Enablement:** requires a license. An administrator enables it from Admin → Apps → All Apps; it is off by default. - **What it is not:** Benefits Management does not maintain its own employee roster. It reads the same employee record the rest of the platform uses. A deactivation or employment-status change ends enrollments automatically on each plan's coverage-end rule. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Benefits Management**. This creates the app tile and the admin tabs. 2. Go to **Benefits Management → Plans** and create at least one benefit plan. Choose a category (Medical, Dental, Vision, Retirement, FSA, HSA, Life, Disability, Supplemental, or Other), how it is priced (One price for everyone, A price per person covered, or A price per coverage level), and set the monthly costs. A plan with no cost fields is valid but will show $0 to employees. 3. Go to **Benefits Management → Enrollment Periods** and create an Open Enrollment period with a start date, end date, and the plans it covers. The period must be active and within its date window before employees can enroll. 4. *(Optional)* Go to **Benefits Management → Settings → Enrollment Settings** to require approval of elections or configure the plan year, and to **Benefits Management → Settings → Automation** to enable election rollover. 5. *(Optional)* Go to **Benefits Management → Plans → open a plan → Manage → Eligibility Rules** to restrict a plan to employees who match criteria such as employment type, tenure, department, location, or role. With no rules, every active employee is eligible. 6. Confirm it worked: employees with access to the app see **My Benefits**, the current enrollment period, and the plans they are eligible for. Admins see enrollment counts on the Plans page. **Silent-until-paired:** a plan with eligibility rules does nothing until you also create an enrollment period that includes that plan. The plan exists, the rules pass, but employees cannot act on it without an open window. ## 3. How it fits together **Plans** are the core record. Each plan belongs to a category, a plan year, and a pricing model. Plans can be active or inactive; only active plans appear during enrollment. A plan with enrollments cannot be deleted — deactivate it instead. **Enrollment periods** are the windows during which employees can make elections. Three types exist: - **Open Enrollment** — company-wide, with a start and end date. When activated inside its window, an announcement email goes out to all employees. - **New Hire** — opened for a specific employee. The default enrollment window is 30 days from the hire date. - **Qualifying Event** — opened for one employee after a life event is approved. An enrollment period can be restricted to a subset of plans. An empty eligible-plans list means every active plan is available. **Enrollments** connect an employee to a plan. Each enrollment carries a status: Eligible, Pending Approval, Enrolled, Not approved (an approver turned the election down; the employee can re-elect while the window is open), Waived, or Terminated. An employee cannot have two active enrollments on the same plan. Per-member elections let the employee cover themselves, one or more dependents, or both — but not nobody (waivers are the explicit "none" path). *Worked example:* an admin creates a plan "Comprehensive Health 2026" (Medical, priced as "A price per person covered", plan year 2026) with monthly costs of $150 employee / $450 employer / $80 spouse / $60 child. They create a "2026 Open Enrollment" period running November 1–30 that covers this plan. An employee opens My Benefits during that window, sees the plan and per-member cost breakdown, and enrolls with spouse coverage. The enrollment records $150 + $80 = $230 employee cost and $450 employer cost. A plan priced as "A price per coverage level" works differently: it charges the one rate set for the level chosen (Employee only, Employee + Spouse, Employee + Child(ren), or Employee + Family), with nothing added per person. **Dependents** are people an employee covers: Spouse, Domestic Partner, Child, Stepchild, or Other. A dependent starts as Pending when their relationship type requires verification (then Verified or Rejected), otherwise Verified, and can have documents attached. Required documents are configured per relationship type — for example, a spouse requires a marriage certificate, while a child requires a birth certificate. The default dependent age limit is 26, matching the ACA standard. **Beneficiaries** are named by the employee under My Benefits → My Beneficiaries. A beneficiary can be linked to one plan or to all eligible plans. The system sends a reminder to life, disability and supplemental enrollees who have not designated one. **Life events** let employees change coverage mid-year. Supported events: Marriage, Divorce, Birth, Adoption, Death, Loss of Coverage, and Other. Each event type has a policy that sets whether documentation is required and how many days the enrollment window stays open, counted from the event date (30 days for most events, 60 for loss of coverage — or the filing limit under **Settings → Enrollment Settings → How late a life event may be reported**, when that is longer). An approved life event opens a special enrollment period for that employee. **Approval routing** is optional. When enabled, enrollment elections go to an assigned approver before taking effect. Routing can be global (one approver for all), by org unit, or by plan type. If no approver is configured for the relevant route, the enrollment auto-approves and is listed under **Admin → AI Operations → Action History**. The default approval SLA is 48 hours, with auto-escalation at 72 hours. ## 4. Running it ### Reviewing and approving enrollments 1. Go to **Benefits Management → Approvals**. Pending enrollments show the employee, plan, coverage level, and cost. 2. Approve or reject the enrollment. On approval the status changes to Enrolled and the employee is notified. On rejection the employee receives the rejection reason. ### Processing a qualifying life event 1. An employee submits a life event from **My Benefits → Life Events**, attaching documentation if the event type requires it. 2. The admin reviews the event at **Benefits Management → Enrollments → Life Events**. Approve to open a special enrollment window, or reject with a reason. 3. No life event an employee reports auto-approves by default (the app itself records an approved "Other" event when HR changes an employee's employment status). To approve some types without review, pick them under **Settings → Enrollment Settings → Auto-approve these life event types**. ### Administering COBRA 1. Go to **Benefits Management → Enrollments → COBRA Administration**. Eligible participants can be auto-detected from offboarding or added manually. 2. Select the participant, choose one or more benefit plans, and optionally send the initial-rights notice on creation. 3. From the participant page: generate and send notices (initial rights, election form, payment due, payment overdue, termination), record payments, and review the audit log. 4. The administrative fee surcharge defaults to 2% and is clamped to the federal 0–2% range. 5. COBRA file downloads (audit CSV/PDF and notice PDFs) require identity re-verification because they contain PII. ### Running ACA compliance 1. Go to **Benefits Management → Reports → ACA Tracking**. Hours are tracked per employee per month. 2. The app detects full-time status based on a configurable threshold (default 130 hours per month). 3. Go to **Benefits Management → Reports → ACA Forms** to generate employee 1095-C forms for a tax year. Forms are produced as PDFs. Use **Bulk Download** to download all completed forms as a zip file. 4. 1095-C downloads also require identity re-verification (they contain SSNs). ### Transmitting to carriers 1. Go to **Benefits Management → Settings → Carrier Connections** and create a connection. Choose 834 EDI or CSV as the connection type, map your plans, and configure SFTP credentials through an integration provider. 2. From the connection page, use **Transmit Now** to send the current enrollment file. Each transmission is logged with a success rate. ### Generating reports Reports are available at **Benefits Management → Reports** for enrollment, cost, compliance, and census data. Each report can be exported as CSV or PDF. PII-bearing exports (census, enrollment, and payroll reports) require identity re-verification; the cost report does not, because its rows are per-plan aggregates. A carrier-ready census export with reorderable columns is available separately. Payroll deduction exports include pre-tax/post-tax treatment by category. Scheduled reports can be configured at **Benefits Management → Settings → Scheduled Reports** with daily, weekly, or monthly frequency. ### Setting up plans with AI document parsing When creating a plan, upload a carrier document (PDF, DOCX, or image up to 20 MB). The AI parser extracts text and returns suggested values for the plan name, category, provider, coverage type, and monthly cost tiers. Review and adjust the suggestions before saving — nothing is written until you confirm. ## 5. Settings Settings are organized across six pages under **Benefits Management → Settings**. | Setting | Page | Default | What it changes | |---|---|---|---| | Require approval of elections | Enrollment | Off | When on, elections employees make themselves wait for their assigned approver before taking effect | | Allow mid-year changes | Enrollment | Off | When on, employees can change coverage level outside an enrollment period or life event window | | Plan year start month | Enrollment | January | The month that defines the start of the plan year | | How late a life event may be reported | Enrollment | 30 days | An employee cannot report a life event whose date is older than this; the enrollment window itself runs from the event date | | New hire enrollment window | Enrollment | 30 days | How many days from hire date a new hire can enroll | | Eligibility waiting period | Employees | 60 days | How many days a new employee waits before becoming eligible | | Dependent age limit | Employees | 26 | Age limit for child and stepchild dependents. The employee is sent a notice about six months before a child or stepchild reaches it; coverage is not removed automatically | | Allowed relationship types | Employees | All on, verification required | For each relationship (Spouse, Child, Domestic Partner, Stepchild, Other): whether employees can add it, and whether it requires document verification | | Benefits notifications (email and in-app) | Notifications | On | Master switch: turning it off stops every benefits email and in-app notification except COBRA notices. COBRA notices are not stopped by this switch; each automated COBRA reminder has its own switch under **COBRA Notifications** on the same tab. The Inbox asks for life events and overdue approvals still arrive | | COBRA administrative fee | Compliance | 2% | Surcharge applied to COBRA premiums (clamped to federal 0–2% cap) | | ACA tracking enabled | Compliance | Off | Enables per-employee monthly hours tracking and full-time detection | | ACA affordability safe harbor | Compliance | **Rate of pay** | Method used for the ACA affordability calculation. Rate of pay is the only affordability safe harbor the app computes today. | | Auto-rollover elections | Automation | Off | Whether unchanged elections carry forward when a new open-enrollment period is activated | | Plan comparison tool | Automation | On | Whether employees see a side-by-side plan comparison during enrollment | | Approval routing mode | Advanced | **Global** | How enrollment approvals are routed (Global, By org unit, or By plan type) | | Approval SLA | Advanced | 48 hours | Hours before an unanswered approval triggers a warning | | Escalation Trigger (Hours) | Advanced | 72 hours | Hours before an unanswered approval auto-escalates | | Data export enabled | Advanced | On | Whether reports can be exported as CSV/PDF | | Enable Scheduled Reports | Automation | On | Whether automated report delivery is available | | Enable Benefits Agent | Advanced | On | Whether the Benefits Agent in Ask AI can answer benefits questions and elect or decline coverage for the asker (it asks them to confirm first) | ## 6. More help - **Benefits Management FAQ** — specific setup, operating, and troubleshooting questions - Ask AI — the assistant answers questions about Benefits Management from these articles. **Keywords:** benefits, enrollment, open enrollment, benefit plan, health insurance, dental, vision, retirement, COBRA, ACA, 1095-C, qualifying life event, dependent, beneficiary, carrier, 834 EDI, wellness, premium, deduction, benefits-management, benefits_management --- # Benefits Management FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Benefits Management — for the admin running it. # Benefits Management FAQ Answers to common setup and operating questions about Benefits Management. For what the app is and how to set it up from scratch, see the [Benefits Management Overview](/help/articles/benefits_management_app_overview). --- ## Setup ## Do I have to create an enrollment period before employees can enroll? Yes. Employees can only submit elections during an active enrollment period. Three types exist: **Open Enrollment**, **New Hire**, and **Qualifying Event**. Open Enrollment and Qualifying Event periods require a start and end date. Without at least one active period, the enrollment form does not appear for employees. ## What roles can manage plans, periods, and settings? Admin, Super Admin, and anyone assigned as a Benefits Management app admin can access the admin-side screens (plans, enrollment periods, COBRA, ACA, settings). Managers can view their direct reports' enrollment summaries under the Team tab. All other employees see only their own benefits in the My Benefits tab. ## What happens if I turn on approval routing but have no approvers assigned? The enrollment auto-approves and moves straight to **Enrolled**. Each election approved this way, without a reviewer, is listed under **Admin → AI Operations → Action History**. To avoid this, assign at least one approver under Benefits > Approvals > Assign Approvers before enabling approval routing. --- ## Permissions and access ## Why can't an employee see any plans to enroll in? Three things must all be true: the app must be enabled for your business, an active enrollment period must exist that covers today's date (or targets that employee for a new-hire or qualifying-event window), and the employee must pass every eligibility rule attached to the plan. Eligibility rules can filter by employment type, tenure, hours worked, location, role, department, age, job title, or pay grade. If any single rule fails, that plan is hidden from the employee. ## My manager says they can't see the Team tab — what do I check? The Team tab requires the **Manager or above** role. Verify the manager's role in admin user settings. App-admin status alone does not grant the Team tab; the role must be Manager, Admin, or Super Admin. --- ## Day-to-day ## How do employees compare plans during open enrollment? When an active enrollment period is open, employees see a side-by-side plan comparison with per-plan costs. For plans with a price per coverage level, the cost is the rate for the level chosen; for plans with a price per person covered, it is the employee's rate plus each covered dependent's. Employees submit their election from this screen. If approval routing is enabled, the election moves to **Pending Approval** until an approver acts. ## What is election rollover, and how do I enable it? Election rollover carries forward an employee's current elections into a new open-enrollment period so they do not start from scratch. Enable it under Settings by turning on **Auto-rollover elections**. When a new open-enrollment period is activated, the system copies enrolled elections from the most recent prior open-enrollment period into the new one. Dependents carry forward if **Pre-populate dependents** is also on. ## What happens when an employee submits a qualifying life event? The employee picks an event type (marriage, divorce, birth, adoption, death, or loss of coverage), enters the event date, and uploads any required documentation. The event waits for an admin to review it unless its type is one you picked under **Settings → Enrollment Settings → Auto-approve these life event types** (none by default). On approval, a special enrollment window opens. The window runs from the event date — 30 days for most events, 60 for loss of coverage — so time spent waiting for approval comes out of it. The employee can then change or add coverage within that window. ## How does coverage termination work when an employee leaves? Each plan has a coverage termination rule. The default is **End of month of last day**. Other options are **Last day worked**, **End of the following month**, **N days after last day**, and **Do not automatically terminate coverage**. When an offboarding event occurs, the system calculates the coverage end date using the plan's rule and the employee's last day. ## I changed the approval SLA — does it affect pending approvals? No. The SLA and escalation deadlines are stamped on each approval record when it is created. The default SLA is 48 hours and escalation fires at 72 hours. Changing the setting only affects approvals created after the change. --- ## Dependents and beneficiaries ## What is the dependent age limit, and can I change it? The default dependent age limit is **26** (the ACA standard). Change it under Settings → Employee & Dependent Settings. The employee is sent a notice about six months before a child or stepchild reaches that age. Coverage is not removed automatically, and there is no student or disability exemption setting. ## What verification statuses can a dependent have? A dependent starts as **Pending** when their relationship type requires verification, otherwise **Verified**. An admin can move a pending dependent to **Verified** or **Rejected**. Each dependent relationship type has its own required-document list — for example, a spouse requires a marriage certificate, a domestic partner requires an affidavit and proof of cohabitation, and a child requires a birth certificate. Verification documents are uploaded as attachments on the dependent record. --- ## COBRA ## How is the COBRA administrative fee calculated? The fee is a percentage of the monthly premium, configurable under Settings > Compliance. The default is **2%** and the maximum allowed is **2%** (the federal cap for standard COBRA). The fee is computed once at enrollment and locked — changing the company-wide rate later does not retroactively change fees on existing participants. An admin can override an individual participant's fee from the participant detail page (0% to 2%), and the change cascades to all unpaid future payments. ## What is the coverage duration for COBRA? It depends on the qualifying event type. Termination and reduction in hours receive **18 months**. Death, divorce, legal separation, loss of dependent status, and Medicare entitlement receive **36 months**. The duration is set automatically when the participant record is created and can only be 18 or 36 months. ## How does the COBRA payment schedule work? When a participant's status changes to Enrolled, the system generates one payment record per month from the coverage start date through the eligibility end date. The first payment is due 45 days after the enrollment date. Each payment carries the monthly premium plus the administrative fee. The default grace period is **30 days** per payment. Payments past the grace period are flagged as overdue. --- ## When something looks wrong ## "I enrolled but my coverage hasn't started" If approval routing is turned on, the enrollment sits in **Pending Approval** status until an approver acts. Check **Benefits Management → Approvals → Enrollment Approvals**. If no approvers are assigned, the enrollment should have auto-approved — look in **Admin → AI Operations → Action History**, where each election approved without a reviewer is listed. If approval is not required, verify the enrollment's effective date; it may be set to **First of next month** or the plan-year start date rather than today. ## "My cost looks wrong on my enrollment" For one-price plans the cost is the plan's price (an election made before the plan's price last changed keeps the price it was made at until the price is next saved). For plans with a price per coverage level, the cost is the rate for the level chosen; for plans with a price per person covered, it is the employee's rate plus each covered dependent's. Whenever you save a changed price — the plan's price on the plan form, a tier on the plan form, a rate in the Rate table, or converting a plan to per-person pricing — every election on the plan whose coverage has not ended is re-priced at once, you are told how many changed, and each employee whose own cost changed is sent their old and new amount, as their notification settings allow (nobody is told when cost-change notices are off in Settings, or about a sample plan). Removing or switching off the only rate someone is priced on, changing a rate's tier or age band so it no longer fits them, leaving a covered dependent with no matching rate, or saving a one-price plan with no price, is refused. Switching the pricing model on the plan form does not re-price anyone until a price is next edited. No screen edits one election's cost on its own. ## "I submitted a life event but nothing happened" Unless its type is one you auto-approve, the event waits in **Pending** status for an admin to review it under **Benefits Management → Enrollments → Life Events**. Once approved, the special enrollment window opens and the employee can change coverage. An event older than the filing limit (**Settings → Enrollment Settings → How late a life event may be reported**, 30 days by default) is refused when the employee submits it; raise that limit (up to 90 days) so they can submit it — raising it also lengthens every life event's enrollment window to at least that many days — or have an admin make the coverage change for them under **Enrollments → Manage Enrollments → Manage Coverage**. --- ## ACA and carrier connections ## How does ACA hours tracking determine full-time status? The system tracks hours worked plus PTO hours per employee per month, if both toggles are on in Settings. An employee is flagged as full-time when their total hours meet or exceed **130 hours per month** (the configurable ACA threshold). Rate of pay is the only affordability safe harbor the app computes today; W-2 and Federal Poverty Line are shown in Settings as not yet supported. ## Can carrier transmissions run on a schedule? You can configure a schedule (manual, daily, weekly, monthly, or real-time) on each carrier connection, but only the **manual** option — the "Transmit Now" button — actually sends a file today. Scheduled automatic transmission is not yet implemented. Connection types are 834 EDI, CSV, or API; API connections are selectable but connection testing and transmission are not implemented yet. --- ## Licensing and limits ## Does Benefits Management require a licence? Yes. It is disabled by default and an administrator must enable it from Admin → Apps → All Apps. Benefits Management is part of the HR Operations suite and can also be licensed on its own. ## Are there limits I should know about? | What | Limit | |---|---| | AI document parse file size | 20 MB | | Supported parse formats | PDF, DOCX, PNG, JPEG, WebP | | Plan categories | Medical, Dental, Vision, Retirement, FSA, HSA, Life, Disability, Supplemental, Other | | Pricing models | One price for everyone, A price per person covered (optionally by age), A price per coverage level | | COBRA coverage duration | 18 or 36 months (by event type) | | COBRA administrative fee | 0–2% of premium | | COBRA first payment deadline | 45 days after enrollment | | COBRA grace period (default) | 30 days | | Default dependent age limit | 26 | | Default eligibility waiting period | 60 days | | Default new-hire enrollment window | 30 days | | Life event enrollment window | 30 days from the event date (60 for loss of coverage) | | Default approval SLA | 48 hours | | Default escalation deadline | 72 hours | | ACA full-time threshold (default) | 130 hours/month | | Approval routing modes | Global, By org unit, By plan | --- ## More help - [Benefits Management Overview](/help/articles/benefits_management_app_overview) - Ask AI — the assistant answers Benefits Management questions from these articles. **Keywords:** faq, benefits, enrollment, open enrollment, qualifying life event, COBRA, ACA, dependent, eligibility, approval, carrier, 834 EDI, wellness, premium, not showing, permissions, approval chain, benefits-management, benefits_management --- # Billing & Payments **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-14 How a tenant admin runs billing — the plan, trial and suites, payment methods, invoices, platform credits, and the AI, SMS and Voice AI spending controls. # Billing & Payments ## 1. What it is Billing & Payments is where an admin sees what the organisation pays for, and how it pays. It covers the plan, the trial, the card or bank account on file, invoices, and one balance of platform credits. Texts, voice minutes, AI and other metered usage all draw on that balance. - **Where:** **General Settings → Billing & Payments** in the admin sidebar. Only Administrators and Super Admins can open it. Everyone else is sent back to the admin dashboard. - **Mango Billing:** the Mango Billing app was retired on 17 September 2026. Your organisation's MangoApps bill — invoices, payment reminders, payment methods and plan — is here, and old Mango Billing invoice links open this page. Its commissions, revenue-recognition, GL export and tax reports were removed, not moved. - **What it is not:** it is not where you turn apps on or off for people. Use Admin → Apps → All Apps for that (see **Apps & Licensing**). Billing decides what you are *entitled to* and what you are *charged for*. ## 2. Standing it up How you start depends on how your organisation signed up. **Self-serve signup (a card at signup).** A self-serve trial starts only when a card is saved during signup. The workspace, its billing account, the card and a 14-day trial are all created at that moment. Nothing exists before it, and a refused card leaves nothing behind. 1. Open **Billing & Payments → Plan**. The **Trial Active** card shows the days remaining and the date the trial ends. 2. Choose **Bill me: Monthly** or **Annually · save 15%** before the trial ends. The choice applies to every line on the trial. 3. Check the **Billing Contact** card on the **Overview** tab. Invoices and payment reminders are emailed to the address it names. 4. Do nothing else if you want to continue. At the end of the trial, the plan starts and the first period is charged to the card on file. **A trial opened by our sales team.** Some organisations start from a company-pricing request instead. That trial starts at signup with no card. Its next step is a proposal priced per employee, never a card charge. **A managed account.** If an account manager set your organisation up, your plan is a contract. The **Contract** tab shows it, with your account manager's name. Plan changes go through them, so the Plan tab lists suites and prices without an **Add** button. **The pairing to watch.** A trial with no card on file does not convert. When the clock runs out, its apps switch off and the workspace becomes read-only. Adding a card at any point, before or after, is what keeps the apps running or turns them back on. ## 3. How it fits together **Lines.** Your plan is made of lines. A line is one suite or one app add-on you pay for, with its own seat count and billing period. The Plan tab lists each line with its price and status. **Suites and editions.** A suite is a bundle of apps priced per seat. Your **edition** (Platform Lite and up) is not chosen: it is earned from the suites and apps you subscribe to. The **Your edition** card on the Plan tab shows what it includes and what would earn the next one. An edition does not come with a monthly credit allowance. **One trial clock.** Every line on a trial shares one end date. A suite or app you add during the trial joins that clock, and nothing is charged for it until the trial ends. **What happens when the trial ends.** This depends on the state of your account: | Your situation | At the end of the trial | |---|---| | Card on file | The plan starts and the first period is charged | | No card on file | Apps switch off and the workspace goes read-only | | You chose **Don't continue** | Apps switch off; nothing is charged | | Trial opened by sales | Extended once while the proposal is prepared, then apps switch off unless it is signed | | More than 200 seats | Extended once while a contract is set up, instead of charging a card | A lapsed workspace keeps its data for 90 days. Adding a card during that time turns everything back on. **Trial reminders.** Admins get reminder emails before the trial ends: - **Self-serve trials** (a card saved at signup) get two reminders, 7 days and 1 day before the charge. - **Trials that started without a card** get three reminders, at 7, 3 and 1 days. **Platform credits.** There is one credit balance for the whole organisation. One credit is worth $0.01. Usage draws on it at a fixed rate per resource. For example, a text message costs 3 credits and a voice minute costs 12. The **What a credit buys** card on the Credits tab lists every rate. - **The welcome credit** is $75 of platform credits (7,500 credits) that every workspace starts with. It is used first and does not expire. - **Purchased credits** come from packs you buy on the **Credits** tab. They never expire. **Worked example.** This month your team sends 200 texts and uses 50 voice minutes: ``` 200 texts × 3 credits = 600 credits 50 voice minutes × 12 credits = 600 credits total = 1,200 credits (≈ $12.00) ``` Whatever is left of the welcome credit is used first. The rest comes off your purchased balance. ## 4. Running it ### Decide what happens at the end of the trial On **Plan**, with a card on file, the Trial Active card offers two choices: 1. **Start now** converts the trial today. The first period is charged immediately and your price is locked. 2. **Don't continue** lets the trial run out with nothing charged. The apps stay on until the end date. Either choice can be undone before the trial ends. After **Don't continue**, the card shows **Continue after all**. Without a card, the card offers **Add payment method** and **Not continuing? Let it end**. ### Add a suite or an app 1. On **Plan → Add a suite**, set the seat count and click **Add**. The confirmation shows exactly what will be charged. 2. On **Add-ons**, add a single app to a suite you already have. An app is never sold on its own. 3. During a trial, the new line joins the trial. Outside one, the first period is charged to your card right away. Every suite bills at least its minimum number of seats. Above 200 seats, we set up a contract instead. If you add a suite that includes an app you were already paying for, that app line is cancelled. Any unused part of what you paid for it is refunded to your card. To remove an add-on, click **Cancel** on the Add-ons tab. If the add-on has already been charged, it stays on until the end of the period you paid for. You can click **Keep it** to undo the cancellation before then. A suite has no **Cancel** button. During a trial, **Don't continue** lets every line end with nothing charged. After the trial, contact MangoApps support to end a suite. Employee suites (Frontline Operations, HR Operations, Communications & Intranet, Performance & Learning, AI Productivity) are not added here: they are priced per employee and quoted. Use **Ask for company pricing** on the Plan tab, and we send a proposal for this workspace. An employee suite includes Platform Standard, which Ask AI, Report Agent and advanced planning need. ### Manage payment methods On **Payment**, click **Add Credit Card** or **Add Bank Account** (a US bank account). A bank account must be verified before you can make it the default. The default method is what renewals, credit packs and add-ons are charged to. If an invoice is still unpaid, adding a card or changing the default pays it on the spot. ### Invoices and payment reminders On **Invoices**, search by invoice number, filter by **Paid**, **Open**, **Overdue** or **Voided**, and choose a date range. **Export CSV** downloads the filtered list. Opening an invoice shows its amounts, due date and description, with **Pay this invoice** while it is open and **Download PDF** when a PDF exists. On a self-serve plan, an unpaid invoice triggers reminder emails at 7, 14, 30 and 45 days past due, and a subscription invoice still unpaid after the last reminder switches the plan's apps off. The Plan tab then reads **Switched off — unpaid**. Paying the invoice turns them back on. If your account is managed by a MangoApps account team, or the invoice is for a signed order form, no automatic reminders are sent: the account team follows it up. ### Buy credits 1. On **Credits**, click **Buy credits** and choose a pack. 2. Add a billing address if asked. Sales tax is quoted on the page before you pay. 3. Optionally, turn on **Automatically buy … when the balance drops below … credits**. Auto top-up is saved when you pay. A pack paid by bank account is added to your balance once the payment clears, usually in 3 to 5 business days. The **Ledger** on the Credits tab shows every addition and draw, and can be exported to CSV. ### Mini app packs Where mini app packs apply, publishing a mini app built in App Builder takes a slot in a pack. Building and trying apps is free. 1. On **Credits**, find **Mini app packs** and click **Buy a pack** (or **Change pack**). App Builder's **Your apps** links to the same page from an app waiting to be published. 2. Pick a pack. The dialog names the monthly price before anything is bought; the pack is billed monthly to the card on file. 3. Publish the app from **Your apps**. A pack is listed on **Add-ons** as a mini app pack. Cancelling it leaves App Builder on: when the pack ends, mini apps published to everyone that take a slot are unpublished, and nothing is deleted. ### Control AI, SMS and Voice AI spending - **AI** shows AI usage by provider, model tier, top users and feature. It also holds the AI spend limits (see §5). - **SMS** shows texts sent. It also sets the low-balance alert for the whole credit balance. - **Voice** is read-only. It shows voice sessions and cloud transcription minutes, which draw on the same credits. On **Credits → This month, by resource**, you can give a resource its own **Monthly budget (credits)**. A budget emails your billing contacts at 80%, 90% and 100%. For texts, voice and API calls, it also pauses that resource once the budget is spent. AI's budget is the **Monthly Spend Limit** on the AI tab. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Bill me | Plan (during a trial) | Monthly | Whether lines bill monthly or annually once the trial ends | | Invoice email | Overview → Billing Contact | Blank | Where invoices and reminders go. Blank uses your billing account email, then your company contact email | | Monthly Spend Limit (credits) | AI | No limit | AI pauses for everyone once it is reached. It cannot exceed a platform maximum if one is set | | Default Per-User Limit (credits) | AI | Unlimited | Each person's monthly AI budget, unless they have an override | | Override (credits) | AI → Spend by User | Use default | One person's monthly AI budget | | Pay-as-you-go Overage | AI | On | On: AI keeps running past your credits, and the extra is billed monthly at 1¢ per credit. Off: AI pauses when credits run out | | Read-only Connector Limit (credits) | AI | No limit | A monthly ceiling on credits spent by read-only actions from connected AI clients | | Warn me when platform credits drop to | SMS | 500 credits | When the low-balance alert is sent | | Auto top-up | Buy credits | Off | Buys the chosen pack automatically when the balance drops below the threshold | | Monthly budget (credits) | Credits → This month, by resource | None | A per-resource budget: alerts at 80/90/100%, and pauses texts, voice and API calls once spent | AI limit changes apply as soon as you save. Your MangoApps account team can also set your organisation to stop AI when credits run out. In that case AI pauses at zero credits even with **Pay-as-you-go Overage** on. ## 6. More help - **Apps & Licensing** — turning on the apps your plan includes - **Settings Hub** — finding billing and other admin settings - Ask AI — the assistant answers billing questions from these articles. **Keywords:** billing, billing and payments, subscription, plan, edition, suite, trial, trial reminder, start now, don't continue, invoice, invoice email, payment method, credit card, bank account, platform credits, auto top-up, low balance, AI spend limit, pay-as-you-go overage, SMS credits, voice minutes, app add-ons, dunning, apps switched off unpaid --- # Bookings App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-20 How to set up and run Bookings — reserve rooms, desks, parking, lockers, and equipment, track occupancy, and respond to emergencies. # Bookings ## 1. What it is Bookings lets employees reserve physical workplace resources — meeting rooms, hot desks, parking spots, lockers, phone booths, AV equipment, company vehicles, and gym equipment — from a single calendar that prevents double-bookings automatically. Admins track who is checked in where, monitor space utilization, and send targeted emergency alerts by building or floor. - **Enablement:** Bookings is pay-as-you-go and available to every tenant without a license decision. You are billed per bookable space, not per user. - **What it is not:** Bookings reserves physical resources and prevents conflicts on them. It is not a calendar app (events and schedules are handled by Calendar) and it does not manage external visitors (that is Guest Pass, which is a separate app today). ## 2. Standing it up 1. Open the Bookings app from your Apps menu. The app is enabled automatically for every tenant — no license activation is needed. 2. Go to **Bookings → Spaces** and create your first space. Each space needs a name, a type (e.g. Meeting Room, Desk, Parking Spot), and a capacity. New spaces are active and bookable by default. 3. Go to **Bookings → Settings** and review which resource types are turned on. All eight — Desks, Meeting Rooms, Parking, Lockers, Phone Booths, AV Equipment, Company Vehicles, and Gym Equipment — are on by default; turn off any you do not use. 4. Set your booking policies: how far ahead people can book (default 30 days), maximum bookings per person per day (default 3), maximum duration per booking (default 8 hours, and 12 hours for desks, parking spots and lockers), the cancellation cutoff — how close to the start a holder can still cancel (default 2 hours) — and the change cutoff — how close to the start the time or space can still be changed (default 2 hours). 5. Confirm it works: have a test user open Bookings, pick a resource, and create a booking. They should see a confirmation and receive a confirmation email with a calendar invite (.ics) attached. **What silently does nothing until you also configure it:** - **Auto-release** is off by default. Enabling it in Settings does nothing until you also have spaces of a matching type (Meeting Room by default). The job releases unchecked-in bookings after a configurable grace period (default 15 minutes). - **QR code check-in** is on by default. People check in by scanning a space's QR code, so print each space's code from its detail page and post it at the space; until a code is posted there, people check in from the booking instead. - **Floor plans** show the uploaded image. Rooms are linked to a plan by the Floor plan column of the spaces spreadsheet import; placing rooms on the map isn't available yet, so the wayfinding view shows the plan without room markers. - **Room display devices** (tablets mounted outside rooms) require a registered device paired to a space; without pairing the display has nothing to show. ## 3. How it fits together **Spaces and bookings** — A space is any reservable resource: a conference room, a hot desk, a parking spot. Each space has a type, a capacity, a location (building, floor, area), and optional amenity and equipment tags (e.g. "projector", "whiteboard", "video conferencing"). A booking ties one user to one space for a time window. Bookings auto-confirm on creation — there is no approval queue and no recurring-booking option today. The system blocks overlapping bookings for the same space automatically. Example: "Conference Room A" is a Meeting Room with capacity 8 on Floor 1, East Wing, tagged with "projector" and "video conferencing". An employee books it from 2:00 PM to 3:00 PM for "Project planning" with 4 attendees. The system assigns a unique booking reference, sends a confirmation email with a calendar invite (.ics) attached, and blocks that slot from other users. Fifteen minutes before the start time, a reminder email goes out. The employee scans the room's QR code to check in, and after the meeting checks out — which marks the booking completed and triggers a feedback request — an Inbox notice, plus an email when they have an address — asking them to rate the space. **Resource types and toggles** — Each of the eight space types (Desk, Meeting Room, Parking Spot, Locker, Phone Booth, AV Equipment, Company Vehicle, Gym Equipment) has an independent on/off toggle in Settings. The toggle controls whether that type appears in the booking form's quick-actions on the dashboard and whether spaces of that type are offered. Spaces of a disabled type still exist but are not bookable through the standard flow. **Check-in and check-out** — Users check in to confirm they actually showed up. Check-in is available starting 15 minutes before the booking's start time. When auto-release is enabled, unchecked-in bookings are marked as no-shows and released back to the pool after the grace period. Check-out marks the booking as completed and optionally triggers a feedback request (an Inbox notice, plus an email when the person has an address). **Waitlist** — When a space is fully booked for a desired time, users can join a waitlist. If that booking is cancelled or auto-released, the first person on the waitlist is notified by email and gets a 15-minute head start to book the freed slot. The space is not held for them — anyone can still book it in that time — and if they have not booked it when the 15 minutes are up, the next person in line is told. Waitlist is on by default and can be disabled in Settings. **Service requests** — Users can attach service requests (Catering, AV Setup, Room Configuration, Cleaning) to a booking. Requests are routed to the facilities team (admins) and tracked through a lifecycle: pending → confirmed → in progress → completed. **Emergency dashboard** — Admins and security staff see a live view of who is checked into which rooms, filtered by building and floor. From this dashboard they can send targeted emergency alerts and export an occupant roster for first responders. Each is its own setting under **Bookings → Settings → User Permissions** — *Who can see who is in the building?*, *Who can export the occupant roster?* and *Who can alert everyone checked in to a building?* — and all three default to admins and Bookings app admins. Safety Hub's emergency alerts are a separate capability with their own setting in Safety Hub. **Favorites** — Any user can star a space to add it to their personal favorites. Favorite spaces appear on the dashboard for one-tap re-booking. Favorites are per-user; they do not affect other users or the space itself. **Space feedback** — After check-out, users can rate a space and report issues (broken equipment, cleanliness, temperature). Feedback is visible to all users. Managers see a feedback analytics view with aggregate ratings and an issues list. Admins can moderate feedback (hide or flag entries). **Floor plans and wayfinding** — Admins upload floor plan images per building and floor, then position rooms on them with a drag-and-drop editor. The wayfinding view is available to all users and shows live availability overlaid on the floor plan. ## 4. Running it ### Managing spaces Go to **Bookings → Spaces** (people named under *Who can add and edit spaces?* — managers and above by default — and app admins). You can create, edit, activate, deactivate, and duplicate spaces. Each space can have: - A location (building, floor, area) for filtering - Amenity and equipment tags for search - An optional hourly rate for cost tracking - An optional bookable-hours schedule restricting when the space can be booked (empty schedule means always available) - A linked floor plan for wayfinding Spaces with active bookings cannot be deleted — deactivate them instead. ### Reviewing bookings Go to **Bookings → Bookings**. Managers see all bookings in the business; non-managers see only their own. Filter by status (Confirmed, Cancelled, Completed, No Show), resource type, or date range. Admins can bulk-cancel or bulk-delete selected bookings. Each user also has a **My Bookings** view showing their personal booking history, upcoming bookings, and stats (total bookings, upcoming count, hours booked this month). ### Running reports and analytics Go to **Bookings → Analytics** for utilization dashboards: booking trends by day, usage by resource type, top spaces, peak hours, a utilization heatmap, and user engagement stats including no-show rate. Go to **Bookings → Reports** to generate utilization, booking analysis, or space performance reports for a date range. ### Handling service requests Go to **Bookings → Service Requests**. The facilities dashboard shows pending, in-progress, and today's requests. Staff can assign a request to themselves or a colleague, then mark it completed with notes and actual cost. ### Managing room display devices Go to **Bookings → Room Displays** (Manager or above, or app admin). Register a tablet device, pair it to a space, and mount it outside the room. The display shows real-time booking status and allows quick-book from the device. You can activate, deactivate, or regenerate the pairing token from the device detail page. ### Using the campus and emergency dashboards **Bookings → Campus Dashboard** shows real-time room availability across all buildings, with drill-down to individual buildings and floors. Any authenticated user with app access can view it. **Bookings → Emergency Dashboard** opens for the people named under any of the three emergency settings. It shows live head counts by building, and — to people named by *Who can see who is in the building?* — a live map of who is checked in where. From here you can send a targeted emergency alert (critical, warning, or informational) to everyone checked in to a building or floor (people named by *Who can alert everyone checked in to a building?*); the room displays there show it too, even when nobody is checked in. People named by *Who can export the occupant roster?* can export the roster as CSV for first responders. The dashboard lists the latest alerts sent from it, with who sent them and who they reached. ## 5. Settings All settings are at **Bookings → Settings** (admin only). | Setting | Default | What it changes | |---|---|---| | Desks & Workspaces | On | Whether desks appear as a bookable resource type | | Meeting Rooms | On | Whether meeting rooms appear as a bookable resource type | | Parking Spots | On | Whether parking spots appear as a bookable resource type | | Lockers & Storage | On | Whether lockers appear as a bookable resource type | | Phone Booths | On | Whether phone booths appear as a bookable resource type | | AV Equipment | On | Whether AV equipment appears as a bookable resource type | | Company Vehicles | On | Whether company vehicles appear as a bookable resource type | | Gym Equipment | On | Whether gym equipment appears as a bookable resource type | | Advance booking window | 30 days | How far in advance users can book | | Maximum bookings per day | 3 | How many bookings one user can make in a single day | | Maximum booking duration | 8 hours (12 for desks, parking spots and lockers) | The longest a single booking can last | | Cancellation cutoff | 2 hours | How close to the start time the holder can still cancel | | Change cutoff | 2 hours | How close to the start time a booking's time or space can still be changed | | Live sensor feed | On | Whether the real-time sensor table is shown and occupancy sensor readings are accepted | | QR code access | On | Whether QR code check-in and space QR codes are available | | Waitlist | On | Whether users can join a waitlist for fully booked spaces | | Auto-release | Off | Whether unchecked-in bookings are released after the grace period | | Auto-release grace period | 15 minutes | How long after the start time before an unchecked-in booking is released | | Notifications | On | Whether booking confirmation emails and reminders are sent | ## 6. More help - **Bookings FAQ** — specific setup, limits, and operating questions - Ask AI — the assistant answers questions about Bookings from these articles **Keywords:** bookings, room booking, desk booking, conference room reservation, meeting room, parking reservation, hot desk, workspace reservation, space management, occupancy, check-in, QR code check-in, floor plan, wayfinding, emergency dashboard, campus dashboard, room display, waitlist, service request, auto-release, no-show --- # Bookings FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Bookings — for the admin running it. # Bookings FAQ Answers to common setup and operating questions about Bookings. For what the app is and how to set it up from scratch, see the [Bookings Overview](/help/articles/bookings_app_overview). --- ## Setup ## Do I need to configure anything before employees can book? Bookings works immediately once enabled — all eight resource types are available by default and every role can create bookings. Open **Settings** to adjust booking policies, disable resource types you do not need, and choose who can administer spaces. ## Which resource types can I turn on or off? Eight types are available, each with its own toggle under **Available Resource Types** in Settings: Desks & Workspaces, Meeting Rooms, Parking Spots, Lockers & Storage, Phone Booths, AV Equipment, Company Vehicles, and Gym Equipment. Disabling a type hides it from the booking flow; existing bookings for that type are not cancelled. --- ## Permissions and access ## Who decides which employees can open Bookings? App access (who can open Bookings at all) is governed by platform **Access Management** on the app's listing — not a role list inside Bookings. Inside Bookings, three pickers under **Bookings → Settings → User Permissions** decide the rest: *Who can book a space?* (default: everyone who can open Bookings), and *Who can add and edit spaces?* and *Who can see booking analytics and reports?* (default: managers and above). Business admins and Bookings app admins can always do all three. ## Who can access the emergency dashboard? By default, admins and Bookings app admins. Three pickers under **Bookings → Settings → User Permissions** decide who else, and anyone named in any of them can open the dashboard and its live head counts: *Who can see who is in the building?* adds the live roster of names, *Who can export the occupant roster?* allows the first-responder CSV, and *Who can alert everyone checked in to a building?* allows the broadcast to everyone checked in to the building or floor you pick. That alert is separate from Safety Hub's emergency alerts, which have their own setting in Safety Hub → Settings — restricting one does not restrict the other. ## Can employees modify or cancel each other's bookings? Everyone keeps full control of their own bookings. Editing or cancelling someone else's booking is limited to the managers above that person and to administrators (business admins and Bookings app admins). Bulk cancel and bulk delete are restricted to administrators. --- ## Day-to-day ## How does double-booking prevention work? When someone creates or updates a booking, the system locks the space for that moment to prevent a race condition. If another confirmed booking already occupies the same space during the requested time window, the new booking is rejected. The availability calendar and the AI agent only offer free slots. ## How do employees check in to a booking? Three ways: scanning the QR code on their booking confirmation email, scanning a QR code posted at the space, or checking in from the booking detail page. Check-in opens 15 minutes before the booking starts and stays available until the booking ends. QR-code check-in has a tighter window — 15 minutes before to 30 minutes after the start time. ## What happens if someone doesn't check in? If you enable **Automatic Room Release** in Settings (off by default), unchecked-in bookings are marked as no-shows and released after a grace period. The default grace period is 15 minutes (adjustable from 5 to 120 minutes). The booker receives an email and an in-app notification. If the waitlist is on, the first matching waitlist entry is notified. ## How does the waitlist work? When a space is occupied during a requested time, employees can join the waitlist (on by default; toggle **Waitlist** in Settings). If that booking is later cancelled or auto-released, the earliest waitlist entry for that space and time slot is notified by email and in-app notification. That person gets a 15-minute head start to book the freed slot. It is not a hold — anyone can still book the space in that time — and if they have not booked it when the 15 minutes are up, the next entry is notified. ## What emails does Bookings send? Booking confirmation (with a calendar invite attachment), a reminder before the meeting, auto-release notice for no-shows, waitlist-available and waitlist-expired notices, service-request status updates, and a space-feedback request after checkout. Confirmations and reminders include an .ics calendar invite as an attachment. ## Does Bookings sync with Google or Outlook calendars? Not as a live two-way sync — changes made in Google or Outlook do not reach Bookings. In the other direction, every confirmation email carries a calendar invite (.ics) that lands the booking on the holder's Google, Outlook or iCal calendar. A reschedule re-sends the invite so your calendar updates, and a cancellation removes it. Bookings also appear on your OneMango Calendar. The **Calendar Invites** setting turns the invites off. ## Can employees set up a recurring booking? Not yet. Each reservation is booked individually. There is no repeat-pattern or standing-booking feature. --- ## When something looks wrong ## "I can't book a room — it says I've hit my daily limit" Each employee is limited to a configurable number of bookings per day (default: 3, adjustable from 1 to 10 in **Settings > Booking Policies > Maximum Daily Bookings**). Only confirmed bookings on that calendar day count. Cancel an unneeded booking to free a slot, or ask an admin to raise the limit. ## "I can't cancel my booking" Cancellations are blocked when the booking starts within the **Cancellation cutoff** (default: 2 hours, adjustable from 0 to 48 in Settings). Changing the time or the space follows its own **Change cutoff** (also 2 hours by default). A business admin or Bookings app admin can still cancel inside the cutoff. Once a booking has started and someone is checked in, it can't be cancelled by anyone — check it out instead. ## "I tried to check in but it said 'Unable to check in at this time'" Check-in opens 15 minutes before the start time. If you are earlier than that, wait and try again. If the booking has already ended or has been cancelled, check-in is no longer available. QR-code check-in closes 30 minutes after the start time even if the booking is still running — use the booking detail page instead. ## "My booking disappeared — what happened?" Most likely, **Automatic Room Release** is enabled and you did not check in within the grace period. Your booking was marked as a no-show and released. You should have received a notification titled "Booking Released." If you do not see one, ask your admin whether auto-release is turned on and what the grace period is. --- ## Licensing and limits ## Does Bookings require a licence? No. Bookings is pay-as-you-go and available to every tenant without a licence decision. You are billed per bookable space under management — no per-user fee and no minimum. Archived (inactive) spaces are not billed. ## What are the configurable policy limits? All five are set in **Settings > Booking Policies**: | Policy | Default | Range | |---|---|---| | Advance Booking Limit | 30 days | 1–365 days | | Maximum Daily Bookings | 3 per user per day | 1–10 | | Maximum Booking Duration | 8 hours (12 for desks, parking spots and lockers) | 1–24 hours | | Cancellation cutoff | 2 hours before start | 0–48 hours | | Change cutoff | 2 hours before start | 0–48 hours | The minimum booking duration is fixed at 15 minutes and is not configurable. --- ## More help - [Bookings Overview](/help/articles/bookings_app_overview) - Ask AI — the assistant answers Bookings questions from these articles. **Keywords:** faq, bookings, room booking, desk booking, space reservation, check-in, no-show, waitlist, auto-release, QR code, emergency dashboard, floor plan --- # Bot Connect FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Bot Connect — for the admin running it. # Bot Connect FAQ Answers to common setup and operating questions about Bot Connect. For what the app is and how to set it up from scratch, see the [Bot Connect Overview](/help/articles/connect_your_own_bot_app_overview). --- ## Setup ## Do I need to turn on both a global setting and a per-assistant placement? Yes. The pop-up bubble and Ask AI routing each have two gates. The global toggles in **Bot Connect → Settings** — **Route assistants inside Ask AI** and **Allow the site-wide pop-up bubble** — must be on, and the individual assistant must also have that placement selected. If either gate is off, the assistant does not appear on that surface. Both global toggles default to **On**, but the per-assistant **Enabled** switch defaults to **Off**, so a newly connected assistant does not appear until you explicitly enable it. ## What does my API endpoint need to return? OneMango POSTs a JSON body containing the question, conversation context, assistant slug, and user identity. Your endpoint should return a JSON object with the answer in an `answer` field. The proxy also accepts `reply`, `message`, `text`, or the OpenAI `choices[0].message.content` shape. A reply with none of these counts as a failed request — **Test** says so — rather than showing an empty answer. To stream, reply with a `text/event-stream` content type and send `data:` lines carrying the text deltas; send `data: [DONE]` to signal the end. ## How do I verify my bot is reachable before rolling it out? On the **Assistants** page, click **Test** on any API-mode assistant card. OneMango sends a test ping to the endpoint and reports whether the bot answered, or why not. Test requests are excluded from usage analytics, so they do not affect your success-rate numbers. --- ## Permissions and access ## Who can manage assistants and settings? Business admins (Admin or above) and users granted the Bot Connect app-admin role. No other role can see the Assistants, Analytics, Agent connections, or Settings tabs. End users interact with assistants only through the surfaces they are placed on; opening Bot Connect from Apps takes them to the first assistant they can use. ## Can I limit which employees see a connected assistant? For the app as a whole, yes — not per assistant. Bot Connect respects the app's visibility rules: if you scope the app to specific groups in Admin → Apps → All Apps, only users in those groups see the assistants — in Ask AI, the pop-up bubble, the full-page tab, and the Home widget. Users outside the scoped groups are told they do not have access. --- ## Day-to-day ## How does Ask AI decide which assistant answers a question? For each API-mode assistant placed in Ask AI, the router scores the question against the assistant's configured **Keywords** and **Topics / domains**. A keyword match is the strongest signal (exact word-boundary match). Topic words contribute a weaker signal and only claim the question when the native agent's own confidence is low. An assistant whose keyword is in the question beats one matched only by topic words; after that the higher score wins, then the longer keyword ("brake pads" over "brake"), and an exact tie goes to the one added first. A question that @mentions an agent, is about the page or an attached file, or is one OneMango always answers itself (your pay stub or paycheck deductions, where the handbook is, returned equipment) is never routed to an assistant. If no assistant scores above zero, the question falls through to native OneMango agents. ## Can my bot answer follow-up questions? In its chat panel (the pop-up and the full-page tab), yes: the panel sends up to 10 prior conversation turns with each question so your bot can answer in context. Each prior turn's content is capped at 2,000 characters. The turns arrive in the request's `context.history` array. In Ask AI, each question is routed on its own — a follow-up with none of the assistant's keywords or topics goes to OneMango's own agents, so employees should repeat a keyword to keep asking your bot. ## Does each proxied question cost AI credits? Yes. Bot Connect is usage-based: each question OneMango successfully proxies to your bot draws 1 AI credit. Test-connection pings do not draw credits. ## What does HMAC signing do, and should I enable it? When you enter an **HMAC signing secret** on an assistant, OneMango attaches an `X-MangoApps-Signature` header to every request. The header carries an HMAC-SHA256 signature of the raw JSON body, signed with your secret. Your backend can verify the signature to confirm the request genuinely came from OneMango. It is optional but recommended for production bots. ## What happens to API credentials and logs when I remove an assistant? Removing an assistant deletes the assistant, its encrypted credential record, and all its usage logs in a single transaction. Nothing is orphaned. If you only switch an assistant from API mode to iframe mode (without removing it), the credential record is also deleted immediately. --- ## When something looks wrong ## "I typed my question in Ask AI but a different assistant answered" The router matched a different assistant's keywords or topics more strongly. Open **Assistants → Edit** on the assistant you expected and check its **Keywords** and **Topics / domains**. Keywords are exact word-boundary matches and score highest — add the specific terms employees use, plurals included. If two assistants share overlapping terms, a keyword in the question beats any number of topic words, then the higher score wins; an exact tie goes to the one added first. Each card on the **Assistants** page names the keywords it shares with another assistant and which one gets a question where that keyword is the only match. The answer in Ask AI names the assistant that gave it, and **Analytics** lists which assistant handled each request. ## "The bot says it couldn't be reached right now" OneMango could not get an answer from the bot's API endpoint within 25 seconds, or the bot answered with an error. Open the assistant's card and click **Test** to check reachability — it says what went wrong. Common causes: the endpoint URL is wrong, the API key has expired, or the bot's server is down. If the last 3 requests within an hour all failed, the health monitor (every 15 minutes) marks the assistant as **Failing**, shows the last error on its card, and notifies admins. ## "I can't see the chat bubble anywhere on the site" Three things must all be true for the pop-up bubble to appear: the global **Allow the site-wide pop-up bubble** toggle in **Settings** must be on, the assistant must have the **Pop-up chat bubble** placement selected and be **Enabled**, and the user must be within the app's visibility scope. If Bot Connect is scoped to certain groups, users outside those groups do not see the bubble. Only one assistant is the pop-up — the first enabled one by name, your own before sample ones — and it shows on desktop pages, not in the phone app. ## "The iframe shows blank — nothing loads" In iframe mode, your chat URL's domain must be allowed by OneMango before it can be framed, and your bot's own site must allow being framed (no `X-Frame-Options: DENY`, and a sign-in that works inside a frame). Until both are true, the iframe renders blank. Employees can still use **Open in a new tab** on the assistant's page. The **Your sites that may show this assistant's page** field does not allow-list your bot's URL — it is for your own sites that frame OneMango. Consider switching to **Connect by API** mode, which does not require domain allow-listing and also supports analytics, health monitoring, and Ask AI routing. --- ## Partner agents ## What are Agent connections and Agent handoffs? They connect Bot Connect to a partner company's AI agent over the A2A protocol. A partner's agent can read service tickets as an employee you choose (with that employee's access only), and employees in a group you approve can hand a ticket ID to the partner's read-only skill and follow the answer under **Agent handoffs**. See the overview's "Agent connections and handoffs" section. ## "Employees in the group don't see the partner" Open the connection under **Agent connections**: the **What employee requests need** list shows which condition is missing — most often the partner card is not verified for the current settings, or no partner bearer token is stored. --- ## Licensing and limits ## Does Bot Connect require a licence? Yes. Bot Connect is disabled by default and requires a licence. An admin enables it from Admin → Apps → All Apps. Usage is billed through AI credits (1 credit per proxied question). ## What are the limits I should know about? | Limit | Value | |---|---| | Assistants per organization | Unlimited | | Assistant name | Up to 120 characters | | Question length | Up to 4,000 characters | | Follow-up context | Up to 10 prior turns, each up to 2,000 characters | | Request timeout | 25 seconds | | Request signing | HMAC-SHA256 | | Health-check cadence | Every 15 minutes | | Consecutive failures before alert | 3 requests within 1 hour | | Analytics periods | 7, 30, 90 days, or all time | | AI credit cost per question | 1 credit | --- ## More help - [Bot Connect Overview](/help/articles/connect_your_own_bot_app_overview) - Ask AI — the assistant answers Bot Connect questions from these articles. **Keywords:** faq, bot connect, external assistant, connect your own bot, iframe, api bot, ask ai routing, keywords, timeout, health monitoring, HMAC signing, streaming, popup bubble, not showing, failing, blank iframe, connect-your-own-bot, connect_your_own_bot, bot-connect --- # Bot Connect Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to register an external chatbot and surface it inside OneMango — in Ask AI, a pop-up, a full-page tab, or a Home widget. # Bot Connect ## 1. What it is Bot Connect lets you register a chatbot you already run on your own infrastructure and surface it inside OneMango — without rebuilding it. You choose where it appears: inside the Ask AI box, as a floating pop-up bubble, as a full-page tab, or as a Home dashboard widget. - **Enablement:** Bot Connect is a licensed app, disabled by default. An admin enables it from Admin → Apps → All Apps. - **What it is not:** Bot Connect does not host or train bots. It connects to a chatbot you already operate. If you need a OneMango-hosted bot with its own knowledge base, that is the Workforce Bots app. ## 2. Standing it up 1. Enable Bot Connect from Admin → Apps → All Apps. 2. Grant access. Only admins (Admin or above) and designated app admins can manage assistants and settings. All other users see only the surfaces an enabled assistant is placed on — they cannot open the admin tabs (Assistants, Analytics, Agent connections, Settings). An employee who opens Bot Connect from Apps lands on the first assistant they can use. 3. Open **Apps → Bot Connect → Assistants** and click **Connect a bot**. 4. Give the assistant a name (up to 120 characters). A URL-friendly slug is auto-generated from the name if left blank. 5. Choose how it connects: - **Embed by URL (iframe)** — OneMango frames your existing chat URL. Provide the **Chat URL** (it must start with `https://`). - **Connect by API** — Provide the **API endpoint**, an **API key / bearer token**, and optionally an **HMAC signing secret**. OneMango proxies questions to your endpoint and returns the answer — word by word in Ask AI when your bot streams; the pop-up and the full-page tab show the whole answer once it is complete. Credentials are stored encrypted in Integrations, never on the assistant itself. This mode is recommended because it supports Ask AI routing, analytics, health monitoring, and conversation-history forwarding. 6. Under **Where should it appear?**, select one or more placements: - **Inside the Ask AI box** — requires API mode. - **Pop-up chat bubble** — a floating bubble on every desktop page (the phone app's pages do not show it). - **Full-page tab** — a dedicated page at a shareable link. - **Home dashboard widget** — a card on the Home dashboard. 7. Optionally, under **Your sites that may show this assistant's page**, list your own sites (one per line) that may put the full-page tab inside their pages. 8. Toggle **Enabled** on so users can see the assistant. 9. Verify it works: - For an API assistant, click **Test** on the assistant card. A successful test shows "Reachable — your bot responded." - For an iframe assistant, click **Open** and confirm the chat loads in the full-page tab. The admin sidebar has five tabs: **Assistants** (the registry), **Analytics** (usage data), **Agent handoffs** and **Agent connections** (partner AI agents — see §4), and **Settings** (global toggles and demo data). **Two things that silently do nothing until both are set:** The **Pop-up** and **Ask AI** placements on an individual assistant will not appear unless the matching global toggle is also on in **Bot Connect → Settings** (see §5). Each placement is gated twice — once on the assistant and once globally. ## 3. How it fits together **Assistant** — a single registered bot. Each assistant has its own slug, connection mode, placements, optional icon and accent color, and (for API mode) its own endpoint and credentials. You can register as many assistants as your organization needs. Each one appears as a card on the Assistants page showing its mode badge (API or Embed), active placements, usage stats, and health status. **Connection mode** — the choice that shapes everything else: | | Embed by URL (iframe) | Connect by API | |---|---|---| | How it works | Renders your chat URL in an iframe | Proxies questions to your endpoint, returns the answer | | OneMango sees the conversation | No | Yes | | Supports Ask AI routing | No | Yes | | Analytics and health monitoring | No | Yes | | Domain allow-listing required | Yes | No | | Streaming support | N/A (your UI handles it) | Yes, via Server-Sent Events — shown word by word in Ask AI; the pop-up and full-page tab show the finished answer | An iframe-only assistant cannot be placed inside the Ask AI box — that placement requires API mode so OneMango can actually query the bot. **Placements** — where an assistant shows up. Each placement is independent, and an assistant can have several at once: | Placement | What the user sees | |---|---| | Inside the Ask AI box | Questions holding one of its keywords — or matching its topics, when OneMango's own agents are unsure — are answered by it instead of native agents | | Pop-up chat bubble | A floating bubble on every desktop page. At most one assistant appears as the pop-up (the first enabled pop-up assistant alphabetically — your own before sample ones) | | Full-page tab | A dedicated page at `/apps/external/` with a shareable link | | Home dashboard widget | A card on the Home dashboard listing each home-widget assistant, linking to its full-page tab | **A worked example:** You register "Parts Lookup Bot" in API mode, placed in **Ask AI** and **Full-page tab**. You set its keywords to `parts, sku, skus, catalog` and its topic to `store inventory`. When an employee types "how many SKUs are in stock?" in Ask AI, the router sees the keyword match and sends the question to your bot. The answer streams back in the Ask AI box, marked with the assistant's name. Each question is routed on its own: a follow-up with none of the keywords or topics ("and in Dallas?") goes to OneMango's own agents, so repeat a keyword to keep asking the bot. The same employee can also open the full-page tab from the left rail and chat directly. **Ask AI routing** — for API assistants placed in Ask AI, the platform scores each question against every routable assistant's configured keywords and topics. A keyword match is the strongest signal. Topic-word matches score lower and only claim the question when the native agent's confidence is weak. If no assistant matches, the question falls through to native agents. Routing requires the **Route assistants inside Ask AI** global toggle to be on. For routing, you configure two fields per assistant (a third, **What does it answer?**, is display only): - **Keywords** — comma-separated exact words, matched as whole words (list the plurals people use too: `sku, skus`). A keyword in a question is the strongest routing signal. When two assistants list the same keyword, each of their cards on the **Assistants** page says which one gets a question where that keyword is the only match; an exact tie goes to the assistant added first. When one assistant lists a longer keyword that holds another's (`brake pads` and `brake`), a question with the longer one goes to the assistant that listed it. - **Topics / domains** — broader topic phrases. Individual words from these phrases contribute a weaker signal. - **What does it answer?** — a short description shown under the assistant's name on Home and, for an API assistant, as the greeting when users open its chat panel. Ask AI does not route by it. **Health monitoring** — every 15 minutes, a background check reviews the most recent log entries for each enabled API assistant. If the last 3 consecutive requests all failed, the assistant is marked **Failing** on its card and admins receive a notification with the last error message. The notification fires once per transition from healthy to failing — it does not repeat while the assistant stays down — and has its own switch in notification settings, **Bot Connect assistant alerts** (in-app and email by default). The card shows the last error in words. When the assistant recovers — or an admin's **Test** gets an answer — the **Failing** badge clears and the failing notification is marked read. **API contract** — when OneMango proxies a question, it POSTs JSON containing the message, conversation context, assistant slug, and user identity, with the bearer token in the `Authorization` header. If an HMAC signing secret is configured, an `X-MangoApps-Signature` header carries an HMAC-SHA256 signature of the request body so your backend can verify authenticity. The bot's response is read from the `answer` field (or `reply`, `message`, or `text`); a reply with none of these counts as a failed request. To stream, the bot replies with Server-Sent Events whose `data:` lines carry the text deltas. **Credential security** — API keys and signing secrets are stored on an encrypted integration record, never on the assistant itself. When you remove an assistant, its credential record is deleted in the same transaction. If you switch an assistant from API mode to iframe mode, the credential record is also removed immediately. **Your sites that may show this assistant's page** — controls which of your own sites may put the assistant's full-page tab inside their pages (for an API assistant as well as an embedded one). Each entry is a site origin (e.g. `https://portal.yourcompany.com`). OneMango adds these origins to the page's `frame-ancestors` Content Security Policy. It does not allow-list your bot's chat URL. **Relationship to Workforce Bots** — Workforce Bots is a separate app that hosts, trains, and manages bots inside OneMango with knowledge bases, approval queues, and grading tools. Bot Connect does none of that — it is purely a connector for bots you run externally. Both apps can coexist: an employee might ask a Workforce Bot about company policies and a Bot Connect assistant about parts inventory in the same session. ## 4. Running it ### What users see End users do not see the Assistants, Analytics, Agent connections, or Settings tabs — those are admin-only. Users interact with assistants through the placements: typing a question in Ask AI, chatting via the pop-up bubble, opening the full-page tab, or clicking the Home widget card. Opening Bot Connect from Apps takes them to the first assistant they can use, and the app's rail lists those assistants (plus **Agent handoffs** for employees a partner connection allows). On the phone, assistants answer in Ask AI and from the Home card; the pop-up bubble is a desktop surface. The app respects visibility rules: if Bot Connect is scoped to specific groups, only users in those groups see the assistants. ### Reviewing usage Open **Bot Connect → Analytics** to see total questions asked, success rate, average response time, and active assistant count. The page shows daily volume (by day in your time zone), a breakdown by surface (Ask AI, pop-up, full page — the Home card opens the full page), a per-assistant table, and the 20 most recent requests with the reason any of them failed. Use the period picker (7, 30, 90 days, or all time) to adjust the window. Click **Export CSV** to download every request in the period, failure reasons included (question text is not exported). ### Testing an API assistant On the Assistants page, click **Test** on any API-mode assistant card. OneMango sends a test ping to the endpoint and reports whether the bot answered — or why not, for example that it refused the API key. Test requests are excluded from usage analytics. ### Editing or removing an assistant Click **Edit** on its card to open the form in a drawer. You can change the name, slug, connection mode, placements, credentials, routing configuration, icon, color, and enabled state. Click **Remove** to delete the assistant and its stored API credentials in one step. Removing an assistant also deletes its usage logs. ### Tuning Ask AI routing Edit an assistant and adjust the **Keywords** and **Topics / domains** fields under the **Ask AI routing** section (**What does it answer?** is the greeting and Home subtitle — Ask AI does not route by it). Keywords cause exact-word matches and are the strongest signal; list the plurals people use yourself. Topics contribute softer word-level signals. When two assistants list the same keyword, each card says which one gets a question where that keyword is the only match — an exact tie goes to the one added first. Test by asking questions in Ask AI and checking which assistant answered in Analytics. ### Responding to a health alert When an API assistant's health monitor detects consecutive failures, admins and app admins receive a notification titled "Bot Connect: assistant failing" with the assistant's name and the last error message. Open **Assistants**, find the card with the red **Failing** badge, and click **Edit** to check the endpoint and credentials. Click **Test** after correcting them — a successful test confirms the fix and clears the badge. Without a Test it clears within 15 minutes of the bot answering employees again. ### Agent connections and handoffs **Agent connections** (admins) link Bot Connect to a partner company's AI agent over the A2A protocol. Each connection has two halves, each switched on separately: - **Partner requests to Workforce** — the partner's agent reads service tickets *as the employee you choose*, with only that employee's current access. Optionally it may also ask Ask AI as that employee, and — on a second switch — propose changes, which the partner approves itself (nobody here is asked). On the connection's page, click **Create inbound token** and give the partner the token; it is shown once, and **Replace inbound token** stops the old one at once. - **Employees ask the partner** — employees in the approved group send a ticket ID to the partner's approved read-only skill. Save the partner's card URL, endpoint, skill and bearer token, then click **Verify partner card**. Changing the endpoint, card URL, skill, partner tenant, employee or group needs verification again and stops requests already in flight from continuing. Each half lists **what it needs** on the connection's page (connection enabled, token issued or stored, card verified, group active…), so you can see which one is missing. There is no Remove: switch a connection off to stop it. **Agent handoffs** is where an employee in the approved group asks the partner (**Ask a partner**), follows each request by its ticket number, answers when the partner needs more information, and uses **Ask again** on one that failed. They are notified when the partner answers, needs more information or fails (notification settings: **Bot Connect agent handoffs**). A handoff opened after its connection was changed or switched off — or after the employee left the group — says so and to ask a Bot Connect administrator. ### Loading sample data Go to **Bot Connect → Settings → Demo data** and click **Load Sample Data** to create five demo assistants (in iframe mode) so you can preview the app populated. Click **Remove Sample Data** to remove them. Sample assistants carry a **Sample** badge and never interfere with real ones; if you point one at your own chat URL or connect it by API, it becomes yours and Remove Sample Data leaves it alone. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | **Route assistants inside Ask AI** | Bot Connect → Settings | On | When on, Ask AI sends a question to the assistant whose keywords match it best — or whose topics match it, when OneMango's own agents are unsure. A question that @mentions an agent, is asked about the page or a file someone attached, or is one OneMango always answers itself (your pay stub or paycheck deductions, where the handbook is, returned equipment) stays with OneMango's own agents, as does everything else. When off, all questions go to native agents regardless of per-assistant placement. | | **Allow the site-wide pop-up bubble** | Bot Connect → Settings | On | When on, one assistant with the Pop-up placement — the first enabled one by name, your own before sample ones — shows as a floating bubble on desktop pages. When off, no pop-up appears even if an assistant has that placement selected. | | **Enabled** (per assistant) | Assistants → Edit | Off | Controls whether this assistant is visible to users. A disabled assistant does not appear in any placement and is not health-monitored. | Both app-level settings default to **On** from the configuration schema. The per-assistant **Enabled** toggle defaults to **Off**, so a newly connected assistant does not appear until the admin explicitly enables it. ## 6. More help - **Bot Connect FAQ** — specific setup and operating questions, including message limits, timeout behavior, and streaming details. - Ask AI — the assistant answers questions about Bot Connect from these articles. **Keywords:** bot connect, external assistant, connect your own bot, bring your own bot, chatbot, iframe bot, api bot, external chatbot, bot popup, ask ai routing, HMAC signing, streaming bot, connect-your-own-bot, connect_your_own_bot, bot-connect --- # Business Profile & General Settings **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-16 How to set your organisation's legal and operating details, work days, branding, sign-in page, languages, operating countries and notification channels. # Business Profile & General Settings ## 1. What it is Business Profile and General Settings are where you define your organisation once for the whole platform. Business Profile holds your legal and operating details: name, timezone, address, compliance information and default work days. General Settings is a hub of cards, each opening its own settings page: branding, sign-in page, languages, operating countries, notification channels and pay rules. - **Access:** both need the Admin or Super Admin role. Business Profile is at **Admin → Organization → Business Profile**. General Settings is at **Admin → General Settings → General Settings**. - **What it is not:** industry, website, company size, description and founding year are no longer on Business Profile. They live in **Admin → Organization → Company Profile**, and the edit form links there. Per-app rules (scheduling, leave, forms) live in each app's own settings. ## 2. Standing it up 1. Go to **Admin → Organization → Business Profile** and click **Edit Profile**. 2. Set **Timezone** and **Business Location** (the address, with autocomplete). Locations without their own timezone use this one. 3. Under **Default Work Days**, tick the days your business works. With nothing ticked, Monday to Friday applies. 4. Fill in **Compliance & Legal Information** if you run payroll, benefits or regulatory reporting here. Every field in it is optional. Click **Update Business**. 5. Go to **Admin → General Settings → General Settings** and open **Brand & Theme**. Set your colors and logo, then click **Apply Theme**. Nothing on that page reaches your people until you apply it. 6. Open **Operating Countries** and **Supported Languages** and pick yours. To show menus and buttons in each person's own language, turn on **Show the web interface in each person's language** on the Supported Languages page. 7. Open **SMS Settings** and switch on **Enable SMS Notifications** if you want text messages. SMS is off for every new business. **Two pairings that catch admins out:** - **A language needs both switches.** Adding Spanish to Supported Languages does not translate the interface on its own. The web interface translation switch must also be on. - **An app's SMS needs the global switch.** The per-app SMS toggles under **SMS by Application** only appear once **Enable SMS Notifications** is on. SMS then goes only to people with a verified phone number. ## 3. How it fits together **Business Profile vs Company Profile** — Business Profile is the operational and legal record: name, timezone, business type, address, compliance fields and work days. Company Profile describes what your company is: industry, website, size, description and founding year. Apps read those facts from Company Profile, so edit them there. **Locked identity** — the email domain, Business ID and business URL are set when the business is created. They show on the edit form as read-only and cannot be changed there. **Work days inheritance** — a location's work days come from the first of these that is set: 1. The location's own setting 2. The default for its location level, for example "Manufacturing Plants" 3. The business default on this page Example: the business default is Monday–Friday. The "Retail Stores" level sets Monday–Saturday. A store with no setting of its own works Monday–Saturday; the head office works Monday–Friday. Leave calculations and business-day counts follow the result. The **Manage location-specific work days** button on the edit form opens the level settings. **Supported languages vs interface languages** — enabled languages are the ones your organisation uses for content and communications. English is always included and cannot be removed. When web interface translation is on, the same list becomes the interface languages people can pick. The interface only offers a language whose translation the platform has already published. Any other enabled language stays available for content, and the interface shows it in English. The Supported Languages page lists the languages available for the interface. **Which language a person sees** — the web interface uses the person's profile language first, then your default language, then English. People change it from the language menu in the header. Arabic and Hebrew display right to left. The sign-in pages also show a language menu when more than one language is available. **Brand & Theme is one draft, applied at once** — color, logo, sign-in page and CSS changes wait on the page until you click **Apply Theme**. The last five applied themes are kept under **Recent Changes** (fifteen older ones under **Older changes**), each with a **Restore** button that says what it would change. **Restore** puts back colors, fonts, component styles, mobile colors and Custom CSS; your logo, favicon, the logo's Header Background, sign-in page, company colors and rail color overrides stay as they are. **Reset to Default** returns colors, fonts, component styles, mobile colors and Custom CSS to the defaults and keeps your logo, favicon, the logo's Header Background, sign-in page and company colors — it also deletes every rail color override, which **Restore** cannot bring back, so use **Save as Preset** first if you want to keep them. **Export Theme** and **Import Theme** carry the same colors, fonts, styles and CSS, not the logo, favicon or rail color overrides. **Brand & Theme sections** on the settings page: | Section | What it holds | |---|---| | Colors | Your Brand and Accent colors, and the colors your company adds by name. Added colors save as you add them, without **Apply Theme**; **Restore** and **Reset to Default** leave them as they are | | Logo & Favicon | Logo and browser-tab icon | | Sign-in page | A panel image and a message beside the sign-in form | | Navigation | Left navigation colors, including Rail Colors by Group | | Surfaces & Shape | Page, card and dialog backgrounds, borders, corner roundness, and card style and density | | Typography & Text | Heading and body fonts, base size, text colors, and your brand fonts | | Status Colors | Colors for success, error, warning and information messages | | Mobile App | Phone header and bottom navigation colors | | Advanced | Custom CSS | **Get my brand from my website** reads the logo, favicon and colors from your website and builds a look around them. You adjust it before anything changes. **Save as Preset** keeps the current look to reuse later. **Export Theme** saves the theme as a file; **Import Theme** loads an exported file and replaces your current theme. ## 4. Running it ### Setting up the sign-in page 1. Open **Brand & Theme** and expand **Sign-in page**. 2. Add a **Panel image**: PNG, JPG or WebP, 1200×1600 or larger, up to 5 MB. It fills the panel beside the sign-in form, cropped to fit. It shows on screens 768px and wider. 3. Type a **Message** of up to 500 characters, such as who to call when someone can't sign in. It shows on every screen size, as plain text. 4. Click **Apply Theme**. The image and message appear on the sign-in, password-reset, one-time-code and two-step verification pages. On a phone the message appears too — on the page that offers the mobile app and on the phone's own sign-in pages — without the image. ### Uploading a brand font 1. In **Typography & Text**, under **Brand fonts**, click **Upload font**. 2. Choose a WOFF2, WOFF, TTF or OTF file of up to 2 MB. Give it a **Family name** and a **Type** (serif or sans serif). 3. Confirm **Our licence lets us use this font on our website and apps**. The platform records who confirmed it and when. 4. Leave **This font's licence allows embedding in email** off unless your licence allows it. While it is off, email uses Georgia for a serif font and a standard sans serif otherwise. 5. Use **Add a weight** to upload Bold or Italic as separate files, so bold text uses the real bold. 6. Pick the font as the **Heading** or **Body** font at the top of the section, then click **Apply Theme**. Uploads save immediately, but nobody sees the font until you pick it and apply. A workspace can hold up to 24 font files. If you remove a font that is in use, that text falls back to a standard font until you pick another. ### Styling phone pages with Custom CSS The **Custom CSS** box under **Advanced** applies to desktop pages and phone pages. It is applied after the theme, so it overrides the settings above it. To style phone pages only, start a rule with `[data-surface="phone"]`. It takes effect when you click **Apply Theme**. ### Changing or revealing the Federal EIN 1. On the Business Profile edit page, find **Federal EIN** under Compliance & Legal Information. The current value is masked. 2. Click the eye icon to reveal it. You are asked to verify your identity first, and every reveal is recorded in the audit trail. 3. To change it, enter the new value as XX-XXXXXXX and click **Update Business**. You must verify your identity before the save is accepted. Leaving the field blank keeps the current EIN. ### Managing operating countries 1. Go to **Admin → General Settings → Operating Countries**. 2. Pick your countries. The page shows how many locations and employees are in each one. 3. Mark one as the **Primary Country** and click **Save Countries**. If you remove the primary country, the first remaining country becomes primary. ### Turning Messages on or off **Admin → General Settings → Messages** controls whether employees can send 1:1 and small-group messages. The switch turns the Messages app on or off for your whole business, and it needs a Messages licence. Finer rules are on the Messages app's own settings page. ## 5. Settings ### Business Profile | Setting | Where | Default | What it changes | |---|---|---|---| | Timezone | Business Profile → Edit | Set when the business is created | Time used for schedules and reports, and by any location without its own timezone | | Business Type | Business Profile → Edit | Customer | Categorises the business account | | Default Work Days | Business Profile → Edit | Monday–Friday | Work days for leave and business-day counting when no location or level overrides them | | Country of Incorporation | Business Profile → Edit (Compliance) | United States | Country where the business is legally registered | | Number of Employees | Business Profile → Edit (Compliance) | Blank | Headcount for compliance. An **ACA Applicable** badge shows at 50 or more; with this blank, active users are counted instead | ### General Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Show the web interface in each person's language | Supported Languages | Off | Shows menus, buttons and messages in each person's language | | Enable SMS Notifications | SMS Settings | Off | Whether any text messages are sent | | SMS Reply Mode | SMS Settings | One-Way SMS (Link-Driven Only) | Whether people can reply to a text | | Daily SMS Limit | SMS Settings | 100 | Most texts sent per day | | Monthly SMS Limit | SMS Settings | 1,000 | Most texts sent per month | | Per-Recipient Daily Limit | SMS Settings | 5 | Once this many texts have gone to one job candidate's number in a day, automatic recruiting texts (interview and offer reminders, recruiting alerts) to it stop for the day. Every text to the number counts; only the automatic recruiting texts are held back. Shown when the Job Board is on | | Restrict to US/Canada numbers only | SMS Settings | On | Blocks texts to job candidates (automatic and sent by a recruiter) and cards shared by text to numbers outside the US and Canada (notification texts still go) | | Use Custom SMTP Server | Email Notifications | Off | Sends email through your own mail server | | Overtime Threshold (hours/week) | Financial & Overtime Settings | 40 | Weekly hours after which overtime applies | | Overtime Multiplier | Financial & Overtime Settings | 1.5 | Pay multiplier for overtime hours | | Double Time Threshold (hours/week) | Financial & Overtime Settings | 60 | Weekly hours after which double time applies | | Double Time Multiplier | Financial & Overtime Settings | 2.0 | Pay multiplier for double-time hours | | This font's licence allows embedding in email | Brand & Theme → Upload font | Off | Whether email links your brand font or uses the fallback | The Financial & Overtime, New Employee Defaults, Company Holidays and Business Time Settings cards appear only when a workforce app is enabled: scheduling, time and attendance, leave, timesheets, or skills and certifications. ## 6. More help - **Company Profile** — industry, website, size and description. - **Locations, Departments & Org Structure** — location levels and the location-specific work days and timezones that override these defaults. - **Settings Hub & Navigation** — finding and searching across all admin settings. - **Security & Sign-On** — password policies, SSO and session controls. - **Admin → General Settings → Translation** — your terminology and how content translation behaves. The interface language switch is on Supported Languages. - Ask AI — the assistant answers questions about business profile and general settings from these articles. **Keywords:** business profile, general settings, company name, timezone, work days, logo, theme, branding, brand font, custom font, sign-in page, login page image, custom css, federal ein, legal entity type, fiscal year, union status, operating countries, supported languages, web interface translation, interface language, sms settings, email settings, push notifications, overtime, financial settings, messages --- # Calendar App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run the Calendar app — the workforce calendar, native events, Company Events with optional approval before an event opens, external sync, RSVP, check-in, conflict detection, and analytics. # Calendar ## 1. What it is Calendar gives every employee one view of their working time: shifts, approved leave, holidays, the native events they host or are invited to, and optionally their connected Google or Outlook calendar. With Company Events turned on, hosts can open an event for self-registration. Employees then find it on the **Company Events** page and sign themselves up. Admins decide what shows up, how events sync, who may open events for registration, whether an event needs approval first, and how attendance is tracked. - **Enablement:** Calendar is a licensed app. An admin enables it from **Admin → Apps → All Apps**. - **What it is not:** Calendar is not the tool that creates shifts — that is the Shifts app. Calendar displays shifts and other workforce items on a personal calendar, and adds its own events, RSVP, check-in, and sync on top. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Calendar**, and enable it for your business. 2. Open **Calendar → Settings**. The app is now live for everyone in your business: **Dashboard** and **My Calendar** are visible to all users. 3. For Google or Outlook sync, open **Settings → Calendar Sync & Connect**. Turn on **Google Calendar enabled** or **Microsoft Calendar enabled** and pick a **Connection mode** (**Per-User OAuth** or **Org-Enforced**). Org-Enforced also needs a service account, added on the same tab. 4. Optionally review **Settings → Event Types**. You can rename, reorder, or disable the pre-built types, and add up to 10 custom ones. 5. For self-registration, open **Settings → Events** and check **Company Events**, then choose **Who can open events for registration**. The **Company Events** tab appears for every employee as soon as the switch is on, even before anything is published. 6. Optionally require approval before an event opens for registration. Go to **Admin → General Settings → Approval Workflows**, click **Create Workflow**, and choose **Calendar**. Set **Applies to process** to **Event publication**, configure at least one approval level, and leave **Enable this workflow** checked. 7. To confirm it works, open **Calendar → My Calendar**. Employees see their shifts, leave, holidays, and native events; connected external events appear too. Two pairings do nothing on their own: - **External sync needs a connection.** Turning on a provider is step one. Each employee (Per-User OAuth) or the service account (Org-Enforced) must then connect before events flow. Without a connection the calendar still shows all workforce data. - **Event approval needs a complete workflow.** A workflow only takes effect when it is enabled, applies to **Event publication**, and has at least one approval level. Until then, hosts publish exactly as before. ## 3. How it fits together **Native events vs. workforce events.** The grid shows two kinds of content. *Workforce events* — shifts, leave, holidays, training sessions, interviews, tasks, 1:1 meetings, onboarding checkpoints — are owned by other apps and shown read-only. *Native events* are created in Calendar itself and carry the full feature set: invitees, RSVP, recurrence, attachments, check-in, and visibility controls. **Event types.** Every native event belongs to an event type, which supplies defaults for visibility, duration, color, and check-in. Ten pre-built types ship: Meeting, 1:1, All Hands, Town Hall, Training, Safety Briefing, Shift Huddle, Interview, Social / Off-site, and Focus Group. The host can override any default per event. Example: **Safety Briefing** defaults to 30 minutes, Public visibility, and QR check-in. A supervisor creating one only adds a title, a time, and invitees. **Visibility.** A native event is **Public** (visible to everyone on the guest list), **Private** (same access, but synced to external calendars as "Busy" with no details), or **Confidential** (visible only to invitees, hidden from calendar-admin oversight). Admins can switch off the Private or Confidential options. **Calendar Connect and sync direction.** Calendar Connect pushes workforce and native events to employees' Google Calendar or Outlook. **Per-User OAuth** means each employee connects their own account. **Org-Enforced** means a Google Workspace or Microsoft Entra admin grants tenant-wide access through a service account. Sync is one-way by default. With **Sync Direction** set to **Bi-directional**, edits made in Google Calendar flow back; Outlook stays outbound. An iCal feed is also available as a read-only option. **RSVP.** Invitees accept, decline, or (if allowed) answer Maybe, and hosts see a live rollup. People invited by email only can answer from signed buttons in the invitation, without signing in. **Discussion.** Every event has a comment thread with one level of replies and @mentions. Anyone who can see the event can post; on an open event, registrants and waitlisted people can too. Comments can be deleted by their author, the host, or an admin. **Delegation.** A delegate (an assistant) can create and manage events for a principal (the leader). A calendar admin sets this up under **Settings → Calendar Sync & Connect → More ways to manage events → Manage delegation**. The delegate then sees an "on behalf of" option in the event composer. **Open events (Company Events).** An open event is an ordinary native event its host has published for self-registration. The host sets a capacity (blank means unlimited), a waitlist, an optional registration window, and who may register — everyone, or chosen groups. People who were not invited find it on the **Company Events** page and register. They then get the reminders, join link, and check-in, as if invited. A recurring series can be opened too: one registration covers every session, and one seat holds across the series. When someone gives up a seat, the first person on the waitlist takes it and gets an Inbox notice. If the Training app is on, the same page also lists the instructor-led training sessions each person can book. Two gates decide who can publish. The person must be the event's host, a delegate, or an admin. They must also pass the **Who can open events for registration** setting. Example: a team lead hosts "Summer Volunteer Day" with 40 seats and the waitlist on. The forty-first person joins the waitlist as #1. When a registrant cancels, #1 is promoted, told in their Inbox, and the event lands on their calendar. **Event approval.** When approval is configured (step 6 above), a host cannot publish an event for registration until it is approved. What gets approved is what people will read: the event's title and description, and the listing's summary and audience. Change any of those after approval and the event needs approving again. Capacity, the waitlist, and the registration window are logistics, so changing them never re-opens approval. Approval does not publish the event — it unlocks **Publish to Events**, and the host picks the moment. Admins are not exempt. **Attendance check-in.** Event types can require check-in by QR code, by geo-fence, or either. With QR, the host displays a code and attendees scan it. With geo check-in, attendees check in from a phone inside the event's geo-fence. Walk-ins (people not invited) can be recorded for review when allowed. **Conflict detection.** Calendar spots overlapping events. In **Suggest** mode (the default) it badges the conflict and offers alternate times. **Auto-resolve** proposes a move and makes it after a response window unless the person with the conflict dismisses it on the event page or the organizer turns on **Don't auto-move this event**; a move can be undone for 60 minutes. ## 4. Running it ### Reviewing the dashboard Open **Calendar → Dashboard**. Six cards give a snapshot: **Today's Events**, **Needs Response**, **Upcoming Conflicts**, **Attendance Alerts**, **Feedback Summary**, and **Your Hosted Events**. ### Creating an event 1. Go to **Calendar → My Calendar** and click **New Event**, or click or drag a time slot. 2. Fill in the title, date and time, event type, location (physical, virtual, or hybrid), and visibility. 3. Add invitees — people, groups, or email addresses. With recommendations on, the composer suggests attendees from past co-attendance. 4. Optionally attach up to 10 files and set up to 5 reminders. Save. Events can also come from a .ics file: **Settings → Calendar Sync & Connect → More ways to manage events → Import from file (.ics)**, up to 200 events per import. A recurring series can be edited one occurrence at a time, from an occurrence onward, or as a whole. ### Opening an event for registration 1. Open an event you host and expand **Open for registration**. 2. Set the capacity, waitlist, registration window, summary, and audience groups, then click **Set up registration**. 3. If approval is required, click **Submit for approval**. The panel says in plain words why it is waiting — under review, rejected with the reviewer's comment, or changed since it was approved. **Withdraw approval request** takes it back while it is under review. 4. Once the event may be published, click **Publish to Events**. It now appears on the Company Events page, the home dashboard's upcoming events card, search, and Digital Signage screens that show events. 5. The same panel shows the roster and offers **Close registration** (existing seats are kept) and **Announce…** (a ready-to-send post with the registration link). Open events can also be created in bulk with **Import events** on the Company Events page. ### Approving events Approvers find pending events on the **Manager Approvals Dashboard**, in the **Publishing** queue, alongside policies, surveys, and other content waiting for sign-off. Deleting an event removes its pending approval request from the queue. ### Following up after an event On an event you host, the **Follow-up survey** card sends a survey to **People who checked in**, **Everyone who said yes or maybe, plus anyone who checked in**, or **Everyone invited**. It needs the Surveys app. Sending the same survey again for the same session reaches only people not yet asked. ### Reviewing analytics Go to **Calendar → Analytics**. **Core Calendar** covers event volume, RSVP rates, recurrence, and event types. **Connect** covers sync health and subscription-expiry alerts. **Autonomous** flags events with low attendance or low feedback scores. ## 5. Settings All settings are under **Calendar → Settings**, on these tabs: General, Events, Event Types, Calendar Sync & Connect, Smart Calendar, Attendance, Analytics, User Integrations, and Sync Logs. Event approval is the one control outside the app, under **Admin → General Settings → Approval Workflows**. | Setting | Where (tab → section) | Default | What it changes | |---|---|---|---| | Enable Calendar Sync | Calendar Sync & Connect | On | Org-wide switch for external calendar sync | | Allow user calendar sync | Calendar Sync & Connect → General | On | When off, only admins configure integrations | | Event title prefix | Calendar Sync & Connect → General | [Work] | Text added to synced event titles | | Sync Direction | Calendar Sync & Connect | **One-way** | Bi-directional also pulls Google Calendar edits back | | Google Calendar enabled | Calendar Sync & Connect → Google | Off | Org switch for Google Calendar sync | | Connection mode (Google, Microsoft) | Calendar Sync & Connect | **Per-User OAuth** | Or Org-Enforced, through a service account | | Microsoft Calendar enabled | Calendar Sync & Connect → Microsoft | Off | Org switch for Outlook sync | | iCal feed enabled | Calendar Sync & Connect → iCal | On | Read-only iCal subscription feed | | Global pause sync | Calendar Sync & Connect → Operational | Off | Stops all sync without disconnecting anyone | | Company Events | Events → Company Events | On for businesses created since September 2026; Off for earlier ones | Adds the Company Events tab and self-registration | | Who can open events for registration | Events → Company Events | **Managers and admins** | Everyone, Managers and admins, or Admins — on top of being the host | | Waitlist on by default | Events → Company Events | On | Prefills the waitlist switch | | Default capacity | Events → Company Events | 0 (unlimited) | Prefills the capacity field | | Default desktop view | Events → My Calendar | **Week** | First view on desktop | | Default narrow-screen view | Events → My Calendar | **Today** | First view on tablets and narrow windows; the phone view is fixed | | Join button window (minutes) | Events → My Calendar | 15 | When the Join button appears before a virtual event | | Allow private events | Events → Composer | On | Offers the Private visibility option | | Allow confidential events | Events → Composer | On | Offers the Confidential visibility option | | Max attachment size (MB) | Events → Composer | 25 | Per-file upload ceiling | | Natural-language quick-add | Events → Composer | On | "All hands Friday 3pm" quick-add | | Max attendees per event | Events → Invites | 5,000 | Ceiling on invitees per event | | Allow delegation | Events → Invites | On | Delegates may create events for others | | Allow Maybe | Events → RSVP | On | Offers the Maybe answer | | Require decline reason | Events → RSVP | Off | Declining asks for a reason | | Let emailed attendees RSVP without signing in | Events → RSVP | On | Yes / Maybe / No buttons in invitation emails | | Max recurrence horizon (years) | Events → Recurrence | 2 | How far ahead open-ended series extend | | Allow series-wide edits | Events → Recurrence | On | Hosts can edit a whole series at once | | Conflict-detection mode | Smart Calendar → Conflicts | **Suggest** | Off, Suggest, or Auto-resolve | | Smart attendee recommendations | Smart Calendar → Recommendations | On | Composer suggests attendees | | Auto-send post-event surveys | Smart Calendar → Feedback | Off | Sends the event's feedback survey after it ends | | Who gets the survey | Smart Calendar → Feedback | **Yes/Maybe replies and check-ins** | Or **Check-ins only** | | Enable Calendar AI agent (Ask AI routing) | Smart Calendar | On | Sends calendar questions in Ask AI to the Calendar agent | | QR code check-in | Attendance | On | QR attendance capture | | Geo check-in | Attendance | On | Geo-fenced attendance capture | | Allow walk-ins | Attendance | Off | Uninvited check-ins recorded for review, not rejected | | Check-in validity window (minutes) | Attendance | 15 | How early or late a check-in is accepted | | Default geo-fence radius (meters) | Attendance | 100 | Geo-fence size unless the event type overrides it | | Allow exports | Analytics | On | Export from analytics boards | | Scheduled email reports | Analytics | On | Scheduled analytics digests | ## 6. More help - **Calendar FAQ** — specific setup and operating questions, limits, and troubleshooting - **Surveys overview** — the surveys behind post-event feedback and follow-ups - Ask AI — the assistant answers questions about Calendar from these articles, and the Calendar agent acts on your calendar: agenda, invitations and RSVPs, open events and registration, an event's discussion thread, and how to watch a streamed event. **Keywords:** calendar, calendar sync, google calendar, outlook calendar, event, RSVP, recurring event, check-in, attendance, conflict detection, calendar analytics, delegation, ics import, calendar connect, meeting, company events, open registration, waitlist, sync direction, event approval, approve event before publishing, training sessions, follow-up survey --- # Calendar FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-18 Answers to common setup and operating questions about Calendar — for the admin running it. # Calendar FAQ Answers to common setup and operating questions about Calendar. For what the app is and how to set it up from scratch, see the [Calendar Overview](/help/articles/calendar_app_overview). --- ## Setup ## Do I need to enable sync before anyone can use the calendar? No. The calendar grid, native events, RSVP, and check-in all work without external sync. Sync to Google Calendar or Outlook is a separate opt-in under **Settings → Calendar Sync & Connect**. Enable the provider-level switch there and choose a connection mode (Per-User OAuth or Org-Enforced) before users can connect. ## Who can access Calendar settings? Only users with the Calendar App Admin role or a business-level Admin or above role can open the Settings tab. All other users see the Dashboard, My Calendar, My Stats, Company Events (when it is turned on), Events I Host, and My Integrations tabs. --- ## Permissions and access ## Who can create events, and who can edit them? Any user with access to Calendar can create events. Only the event host (or a delegate acting on their behalf) can edit or delete the event. Calendar App Admins can view non-confidential events for oversight, but editing is still restricted to the host. ## What does delegation mean, and how do I set it up? Delegation lets an assistant create and manage events on behalf of another person. A Calendar App Admin opens **Settings → Calendar Sync & Connect**, finds the **More ways to manage events** card, and clicks **Manage delegation** to name a principal (the leader) and a delegate (the assistant). The delegate can then compose events that appear as hosted by the principal. Delegation must be enabled in settings; the toggle is **Allow delegation** on the Invites settings group. ## Why can't some users see the Analytics tab? The Analytics tab appears only when the user's role matches the analytics dashboard permissions configured in **Settings → Analytics**. By default, the Core and Autonomous dashboards are visible to Calendar App Admins and leadership roles, and the Connect dashboard is visible to Calendar App Admins only. --- ## Day-to-day ## How do RSVP responses work? Invitees can respond **Yes**, **No**, or **Maybe**. The Maybe option can be hidden by turning off **Allow Maybe** in the RSVP settings group. When **Require decline reason** is on, declining requires a reason from an editable list (defaults: Schedule conflict, On leave, Not relevant to role, Other). Invitees may also attach a free-text comment up to 500 characters if **Allow RSVP comment** is on. ## Can I ask the host a question before the event? Yes. Every event page has a **Discussion** thread at the bottom: post a comment, reply to one, and type **@** to mention a colleague. The host and their delegate are told about every comment, the person you replied to is told about the reply, and anyone you @mention is told — but only if they can see the event. Invitees, registrants, and people on the waitlist can post; anyone who can see an open event's listing can read the thread before registering. ## Who can delete a comment on an event? The comment's author, the event's host or delegate, and admins (business admins and Calendar app admins). Deleting a comment removes its replies with it. ## Can people outside my company RSVP to an event? Yes, if the **Let emailed attendees RSVP without signing in** setting is on (it is on by default). External guests receive an email with a secure signed link and can respond Yes, No, or Maybe without logging in. Turning this setting off disables the public RSVP page for the entire business. ## How do recurring events work? When creating an event the host sets a recurrence rule (daily, weekly, monthly, or a custom pattern). Editing a recurring event offers three choices: **This event only**, **This and following events**, or **All events in the series**. Admins can turn off series-wide edits via the **Allow series-wide edits** recurrence setting. Open-ended series generate occurrences up to 2 years ahead by default (configurable from 1 to 10 years), with a hard cap of 3,650 instances per series. ## What is natural-language quick-add? When **Natural-language quick-add** is on in the Composer settings, users can type a sentence like "Lunch with Sam Friday 1 pm" in the composer and the app parses it into a structured event. The host reviews and adjusts the result before saving. ## What does conflict detection do, and how do I configure it? Conflict detection warns hosts about double-booked attendees. Under **Settings → Smart Calendar → Conflicts**, you choose a mode: **Off**, **Suggest** (badge plus alternate times), or **Auto-Resolve** (Calendar moves the event to a free time after a response window; the person with the conflict can keep the current time by dismissing it on the event page, the organizer by turning on **Don't auto-move this event**, and the move can be undone for 60 minutes). Switching to Auto-Resolve requires confirmation because it moves events automatically. --- ## External sync ## Which external calendars can users connect to? Google Calendar and Microsoft Outlook, each via OAuth. Users can also subscribe from any app that supports iCal using a read-only feed URL. Each provider must be enabled in **Settings → Calendar Sync & Connect** before users can connect. ## How do I connect my own Google or Outlook calendar? Open **Calendar → My Integrations** and choose **Connect Calendar**, then Google Calendar or Outlook; for a read-only feed in any other calendar app, choose **iCal Feed**. Everyone with Calendar can open My Integrations — the Settings tab is for Calendar admins. If a provider is missing from the list, your organization has not turned it on, or does not let people connect their own calendars; a Calendar admin changes that under **Settings → Calendar Sync & Connect**. Ask AI can check whether your calendar is connected and syncing, but it cannot connect one for you. ## Is sync one-way or two-way? It depends on the provider and on an admin setting. Google Calendar sync is outbound by default, and becomes two-way when your administrator sets **Sync Direction** to bi-directional under Calendar Settings → Calendar Sync & Connect — edits made in Google Calendar then flow back into OneMango (a change made on both sides since the last sync is paused for review rather than overwritten). Outlook sync is outbound only: events created in OneMango flow to Outlook, and changes made in Outlook do not flow back. ## How do I make Google Calendar sync two-way? Open **Settings → Calendar Sync & Connect** and set **Sync Direction** to **Bi-directional** (the default is **One-way**). From then on, edits made in Google Calendar flow back into OneMango for every connected Google account. The setting has no effect on Outlook, which stays outbound only. If the same event changed on both sides since the last sync, that event is paused for review rather than overwritten. ## How often does sync run, and how far ahead does it look? The default sync interval is **30 minutes** (configurable from 5 to 1,440 minutes). The default look-ahead is **60 days** into the future (configurable from 1 to 730 days). A **Global pause sync** kill switch halts all sync without disconnecting users — useful during a provider outage. ## I connected my calendar but nothing is syncing — what's wrong? Check these in order: (1) the provider-level switch for Google or Microsoft is on under **Settings → Calendar Sync & Connect**, (2) the **Global pause sync** switch is off, (3) the user's integration shows as connected and sync-enabled on the **User Integrations** tab. If admin approval is required, the connection may be pending approval. --- ## Check-in and attendance ## How do QR code and GPS check-in work? The host opens the event and displays a QR code (a full-screen Display-QR mode is available for on-site projection). Attendees scan the code to check in; a typed-code fallback is available for accessibility. GPS geo-fenced check-in uses the device's location: the default geo-fence radius is **100 meters** (configurable from 10 to 10,000 meters per event type). When a GPS reading is low-accuracy or times out, the host can manually confirm the attendee. ## Can someone check in if they aren't on the invite list? Only if the admin turns on **Allow walk-ins** in the Attendance settings. When enabled, an unmatched check-in is recorded as a walk-in for admin review rather than being rejected. --- ## Company Events (open registration) ## How do I find events I can register for? Open Calendar and click the **Company Events** tab. It lists upcoming open events — and, when your workspace uses Training, the instructor-led training sessions you can book — with the date, place, and spots left. Hit **Register** on a card, or **Details** first. A training session's Register, Switch and Cancel are Training's own, so the seat also shows on the course page. Use **Show** to see only events or only training sessions. On your phone, the same list is under Calendar's Company Events section. Your own event sign-ups are under **My registrations**. If you don't see a Company Events tab, Company Events is turned off for your workspace — that's an admin setting. ## What happens when I register for an event? It lands on your calendar like any invitation you accepted: you get the event's reminders, the join link if it's online, and you can check in on the day. You can cancel any time from the event's page or from My registrations — cancelling frees your spot for the next person. ## The event is full — what does joining the waitlist do? You take a numbered place in line. The moment someone gives up a seat, the first person on the waitlist gets it automatically and is notified — no re-registering needed. When that happens, the event lands on your calendar just as if you'd registered directly. ## Why does an event say "This event isn't open to you"? The organizer limited registration to specific groups, and you're not in one of them. Events with no group restriction are open to everyone in the company. ## Do I get points for attending an event? Yes, when your workspace runs Levels & Badges: checking in at an event you registered for earns **15 points** (up to two events per day count). Signing up alone doesn't score — showing up does. ## How do I open my event for registration? On your event's page, expand **Open for registration**. Set the capacity (leave it blank for unlimited), whether to run a waitlist, an optional registration window, a short summary, and who can register. Save, then click **Publish to Events** — the event appears on the Company Events tab immediately. Recurring series work too: registering signs someone up for every session, the listing shows the next session, and reminders and check-in run per session. Everyone who registers or joins the waitlist gets a confirmation email with the event on an attachable calendar invite, a waitlisted person is emailed again the moment a seat becomes theirs, and cancelling sends a confirmation with a link to register again while registration is open. The panel also shows the event's own numbers (registered, waitlisted, attended, cancelled) and an **Export roster (CSV)** button — name, email, status, registration and check-in times. ## Who can open events for registration? That's the **"Who can open events for registration"** setting in Calendar Settings: **everyone**, **managers and admins** (the default), or **admins** only. You also need to be the event's host (or a delegate or admin) to manage its registration. ## How do capacity and the waitlist behave? A blank capacity means unlimited. When the event is full and the waitlist is on, new sign-ups join the waitlist in order. When someone cancels, the first waitlisted person is promoted automatically and notified — the seat is never left empty while people wait. ## When does registration close? By default, when the event starts. You can also set an explicit open and close time in the registration settings, or click **Close registration** at any point — that stops new sign-ups while everyone already registered keeps their seat, their reminders, and check-in. ## How do I run the event on the day? The **Open for registration** panel shows the roster — everyone registered and waitlisted. Check people in the way you would for any event (QR, GPS, or manually); a registrant who checks in shows as **Attended** on the roster. ## How do I tell the company about my event? Click **Announce…** on the registration panel. It opens the composer with a ready-to-send post — the event's name, time, place, and a registration link — and you choose how loudly it lands, from a feed post to a broadcast. ## Can I bring in events from a spreadsheet? Yes — **Import events** on the Company Events tab. One row per event, with columns for the event name, date, start and end time, place, seats, waitlist, and details. Each row lands already published on the Company Events tab, ready for registrations. This is the fastest way to move an old sign-up sheet over. ## Can a Town Halls session be opened for registration, and how do people watch it? Yes. When a host schedules a session in Town Halls and ticks **Open for registration under Events**, its calendar entry is published on the Company Events tab for everyone, so people outside the session's audience can register and get the reminder and watch link. The calendar event page shows the session's state: the start time before it airs, a **Watch live** button while it streams, and **Watch recording** once a recording is ready. Anyone who watches the stream while registered is marked **Attended** on the roster, the same as a QR check-in at an in-person event. The switch only appears when Company Events is on, the host may open events for registration, and Town Halls is set to mirror sessions onto the calendar. ## Can I use Ask AI for an event's discussion or its live stream? Yes. Ask the Calendar agent what people are saying about an event ("what are people saying about the volunteer day") and it reads the discussion thread — top-level comments with their replies — for any event you can see or hold a seat on. Ask it to post a comment or reply ("ask on the volunteer day thread whether parking is free") and it posts as you after confirming; the host and anyone you replied to are notified exactly as from the event page. Plain text only — @mentions need the event page. For a streamed event, "how do I watch the town hall" returns the stream's state — scheduled, live, or recording ready — with the watch link. The same answers are available to Claude through the OneMango connector. ## How do I turn Company Events on, and where else do open events show up? It's the **Company Events** switch on the **Events** tab of Calendar Settings — on by default, so turning it off is your call per workspace. Once on, open events also appear on the home dashboard's **Upcoming Events** card, in company search results, and on Digital Signage screens that show event content. --- ## When something looks wrong ## My event disappeared — what happened? If the event was part of a recurring series and someone edited "this and following events," the series splits and earlier occurrences may have moved to a different parent record. Check whether the event was cancelled by looking at the event's audit log. Confidential events are completely hidden (not just locked) from non-invitees — a user who was removed from the invite list will not see the event at all. ## Why didn't I get a post-event feedback survey? Automatic feedback surveys are **off** until an admin turns on **Auto-send post-event surveys** in the Feedback settings, and an event only sends one when its event type has a survey linked (**Post-event survey** on the event type form, or the per-type map in the Feedback settings). The Surveys app must be on too. The survey goes out 30 minutes after the event ends (the **Send delay** setting). **Who gets the survey** decides who counts as an attendee: everyone who answered Yes or Maybe plus anyone who checked in (the default), or only the people who checked in — an event that takes no attendance still surveys its Yes and Maybe replies. The event's host never gets its survey. For recurring events, the **Recurring event policy** setting controls whether surveys go out after every occurrence, only the first, or only the last; an event type can set its own policy, which wins. A change to the policy applies to every survey that hasn't gone out yet. A survey is only ever sent for a session that ends after the event was saved: an event added after it had already happened, or an old series you edit, doesn't survey past sessions. If the event page says no survey will be (or was) sent, it names the reason — for example, the linked survey has no questions yet or is waiting for approval. ## Can I send a follow-up survey after my event? Yes, if you host the event, the Surveys app is on, and you can create surveys there. After the event starts, the **Follow-up survey** card on the event page lets you pick a survey you own or co-own (an admin can pick any) and send it to the people who checked in, everyone who said Yes or Maybe, or everyone invited. Sending the same survey again adds only people who don't have it yet. You see the results once enough people respond to keep answers anonymous — unless the survey is confidential, whose results only its owner and the people it's shared with can see. The **Focus Group** event type is made for this: a private session that takes check-in, followed by your questionnaire. ## Can an event need approval before it opens for registration? Yes, if your organization wants it. An admin creates an approval workflow for the Calendar app with the process **Event publication** (**Admin → Approval Workflows**). From then on the event's **Open for registration** panel shows **Submit for approval** instead of **Publish to Events**; once an approver approves it, **Publish to Events** returns. Changing the event's title, description, summary or audience after approval needs a new approval. Without such a workflow, events publish directly. --- ## Licensing and limits ## Does Calendar require a licence? Yes. An administrator enables Calendar for the organization from **Admin → Apps → All Apps**; nothing works for employees until that is done. Company Events is a separate switch inside Calendar Settings (on by default; an admin can turn it off). ## What are the limits I should know about? | What | Default | Configurable range | |---|---|---| | Attendees per event | 5,000 | 10–50,000 | | File attachments per event | 10 | Fixed | | Attachment size per file | 25 MB | 1–1,024 MB | | Reminders per event | 5 | Fixed | | Custom event types per business | 10 (plus 9 pre-built) | Fixed | | Event duration | 1 minute–365 days | Fixed | | Sync frequency | 30 minutes | 5–1,440 minutes | | Sync look-ahead | 60 days | 1–730 days | | Recurrence horizon | 2 years | 1–10 years | | Max instances per recurring series | 3,650 | Fixed | | RSVP comment length | 500 characters | Fixed | | Event title length | 255 characters | Fixed | | Event-type name length | 1–20 characters | Fixed | | Default geo-fence radius | 100 meters | 10–10,000 meters | | Check-in validity window | 15 minutes before/after | 0–240 minutes | | ICS import | 200 events per file | Fixed; file size up to 1 MB | | Registration capacity (Company Events) | Unlimited (blank) | 1–100,000 seats per event | | Default capacity prefill (Company Events) | 0 (unlimited) | 0–100,000 | | Waitlist on by default (Company Events) | On | On / Off | | Who can open events for registration | Managers and admins | Everyone / Managers and admins / Admins | --- ## More help - [Calendar Overview](/help/articles/calendar_app_overview) - Ask AI — the assistant answers Calendar questions from these articles. **Keywords:** faq, calendar, events, RSVP, check-in, sync, company events, open registration, register for event, waitlist, event capacity, sign up, recurring events, event types, Google Calendar, Outlook, attendees, geo check-in, QR code, conflict detection, not syncing, can't see event, comment, discussion, mention, live stream, watch live --- # Chat App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-19 How to set up and run the Chat app — real-time direct messages, group chats, channels, and the in-chat Ask AI assistant. # Chat ## 1. What it is Chat gives your organization real-time messaging — one-on-one direct messages, named group conversations, and channels — with @mentions, presence indicators, file sharing, inline replies, reactions, and built-in search. An optional Ask AI assistant can be brought into any conversation with an @mention or a trigger phrase, answering questions grounded in the room's own history. - **Enablement:** Chat is a licensed app. An admin enables it from **Admin → Apps → All Apps**, and it is off by default for every tenant. - **What it is not:** Chat is the *synchronous*, real-time messenger. The separate **Messages** app is the asynchronous, inbox-resident counterpart (like internal email). "Direct messages" in Chat and "Messages" are different products governed independently. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps → Chat → Enable**. 2. Open the Chat app from the left-hand navigation and go to **Settings**. Review the defaults — one-to-one messages, new group chats, file uploads, typing indicators, and the Ask AI assistant are all on by default. Adjust anything your organization needs off before users start chatting. 3. **Optional — restrict access.** If only certain groups or departments should use Chat, configure an access policy. Chat supports contextual access policies (the gate is enforced on every request, not just the first visit). 4. **Optional — customize Ask AI.** On the Settings page, scroll to the Ask AI identity form. You can change the assistant's name, icon, and description so the assistant appears under your organization's own branding. The identity is shared with the Ask AI sidebar — updating it here updates it everywhere. 5. **Optional — load sample data.** The Settings page has a Demo data card that loads sample rooms and messages so you can explore the app without waiting for real activity. 6. **Confirm it worked.** Open **Chat → Dashboard** as an admin. You should see the activity widgets (even if they show zeros). Have a test user open Chat and start a conversation — they should see the rooms list, the "New message" button, and (if enabled) the @Ask AI mention in the composer. **Pairing that silently does nothing:** **Ask AI grounded answers** requires **Semantic search** to also be on. If you enable grounded answers but leave semantic search off, the assistant has no embeddings to retrieve from and its answers will not reference conversation history. Both are on by default. When you first enable semantic search (or turn it back on), a background job backfills embeddings for all existing messages. The Settings page shows embedding progress so you can tell when history is fully searchable. ## 3. How it fits together **Rooms** are the central object. Every conversation is a room. There are three types: - **Direct** — a private one-on-one conversation. When you start a chat with one person, the app finds or creates a single direct room between you. Direct rooms cannot be renamed, and neither party can leave. - **Group** — a named multi-person conversation. Any member can be in multiple groups. The creator becomes the room admin; everyone else joins as a member. Groups can be renamed and members can be added or removed. - **Channel** — structurally identical to a group (same create, rename, and member-management flows), intended for broader, topic-based conversations. **Members and roles.** Each room member has one of two roles: **admin** or **member**. The creator of a group or channel starts as admin. Room admins can rename the room, manage members, delete anyone's messages, and configure per-room settings (including the per-room permissions below and the Ask AI proactive opt-in). Room admins make another member an admin, or remove someone's admin role, from the member list (**Make admin** / **Remove admin**); the last admin can't be demoted, and someone no longer active in your organization can't be made an admin. **Pinning and muting.** Members can pin conversations so they appear at the top of their rooms list, and choose how each conversation notifies them from its **…** menu: **All messages**, **Mentions only** or **Nothing**. A mute set on the phone or in the native apps shows in that menu as **Muted until …** (or **Muted**) **— Unmute**, so it can be undone on the web too. Messages that ask you to confirm you've read them — Important messages and read receipt requests — still reach your bell and email in a muted conversation. **Per-room permissions.** Group and channel rooms list them under **Conversation settings** (the gear button in the room header, shown to the room's admins): - **Who can add new members?** - **Who can see the group (or channel) member list?** - **Who can send messages in this group (or channel)?** - **Who can send important messages and request read receipts?** — only where Important messages or read receipt requests are on and allowed in that room - **Who can reply in threads?** — channels only Each is answered with **Any member**, **Conversation admins and company admins**, or **Company admins only**, and all default to "any member" (fully open). **Important messages and read receipt requests.** A sender can mark a message as Important (recipients must explicitly acknowledge it) or request a Read Receipt (the message body stays hidden until the recipient confirms they have read it). Both are per-message choices in the composer. They are available in direct messages, groups and private channels of up to 50 people — not in public channels or in channels of more than 50 people. In a group or a channel, the sender sees "Read by X/Y" and who has and hasn't read it, and when the sender was a manager or a room admin at the time they sent it they can also send a reminder to the people who haven't; in a 1:1 chat the sender sees when it was read. When an Important message has a backup who is not in the conversation and someone still hasn't confirmed, the backup's notice names who hasn't and offers a "Message" button that starts a chat with those people (through your company's usual chat rules); the notice never shows the backup the message's words. **Approval cards.** An approval card in Chat that was decided somewhere else says who decided it and, when known, where — for example "Approved by you, from your Inbox" — rather than only "Already handled". **Seen by.** Senders see who has seen their messages: "Seen by Bob" in a 1:1 chat, and in a group of up to 50 people, under their latest message someone has read, the names of who has read it — up to three, then how many more ("Seen by Ana, Bob, Cy +2"). A conversation of more than 50 people shows "Read by N%" instead, which opens the list of who has read it. In a group, a person your works-council settings keep out of read reports is never named. Admins can turn all of this off with **Show who has seen a message**; senders then see only "Sent" or "Delivered". Important messages and read receipt requests keep their own "Read by X/Y" either way — they are an explicit ask. **Ask AI in Chat.** When enabled, an AI assistant can be mentioned in any room with **@Ask AI** (or the admin-customized name). The assistant replies in the thread, grounded in the room's own message history when semantic search and grounded answers are both on. Admins can also set custom trigger phrases (default: "/ai"; workspaces set up before September 2026 keep "hey ai, /ai" until an admin changes it) that invoke the assistant without an @mention. Each room admin can additionally opt a room in to **proactive suggestions**, where the assistant chimes in when it detects an unanswered question, a meeting intent, or a commitment. **Editing and deleting messages.** Users can edit their own text messages within 15 minutes of sending. Users can delete their own messages at any time (no time limit); room admins can delete anyone's messages. Both capabilities are governed by business-level settings that the admin can turn off. **File attachments.** Messages can include up to 10 file attachments. Files are uploaded directly to storage (no file bytes pass through the application server). Blocked file types include executables (.exe, .bat, .sh, .msi, .dll, etc.) and browser-renderable formats (.html, .svg) that could carry scripts. Allowed types cover documents, images, audio, video, archives, and fonts. **Inline translation.** Any room member can translate a message into their preferred language or any supported language. Translations are cached server-side — the same message in the same language is translated once, so repeat viewers and teammates with the same language preference reuse the cached result. **Relationship to other apps.** Ask AI in Chat can open Service Desk tickets from inside a conversation (when in-chat actions are enabled). Video huddles (**Start huddle (Live Assist)** in a conversation's **…** menu, or the full-width **Start huddle** button at the end of the conversation on a phone) require the **Live Assist** app, enabled and published to the people who will use them. Chat is independent of the **Messages** app — enabling or disabling one does not affect the other. ## 4. Running it ### Reviewing analytics Go to **Chat → Analytics** (visible to admins and chat app admins). The page shows four metrics: - **Adoption** — percentage of provisioned users who sent at least 5 messages across at least 3 conversations (1:1 chats count) in the last 14 days, with a 12-bucket trend chart - **DAU/MAU stickiness** — daily active users as a percentage of monthly active users, with a 30-day daily trend - **Messages across departments** — percentage of messages exchanged between people in different departments, with the top department pairs by volume - **@Mention response rate** — how quickly @mentioned messages receive a reply, broken into 1-hour, 4-hour, and 24-hour buckets with a median response time You can export the full dataset as a CSV for further analysis. ### Exporting chat history for a legal matter A company admin can export Chat history from **Admin → Compliance → Chat Export**: choose up to 50 people and a range of days (at most 3 years), and optionally some of their conversations. The export is built in the background as a ZIP with one file per conversation those people were in — every message in those days, deleted messages and earlier versions of edited ones included — and can be downloaded by the admin who started it for 7 days, after which the file is deleted. Every export is recorded with the admin's name. A company admin can also keep everything in a conversation past your retention settings with **Hold a conversation** on **Admin → Compliance → Retention & Legal Holds**: find it by its name or its people, without joining it, and nobody in it is told; lifting a conversation's hold, there or from the conversation's own menu, asks for a reason. ### Managing deleted conversations Go to **Chat → Recently deleted**. A Chat admin sees every deleted conversation there; anyone else sees the ones they deleted themselves. When someone uses "Delete for everyone" on a conversation, it enters a 30-day restore window. You can restore individual rooms or select multiple and restore in bulk. After 30 days the room and its messages are permanently purged, unless a legal hold keeps them. ### Searching chat history Go to **Chat → Search**. Search uses full-text keyword search by default. When **Semantic search** is enabled, a meaning-based mode is also available that finds messages even when the exact words differ. The search page supports filters by room, sender, and date range. Results link directly into the matching message in its conversation. A separate **Find a conversation** box in the rooms list lets users filter their conversations by room name, member name, or message content without leaving the list view. ### Moderating content When **Content moderation** is enabled (off by default), new and edited messages are checked against blocked words and content patterns *after* they are delivered — the real-time send path is never blocked. Violations are either **flagged** (message stays visible, queued for review) or **hidden** (message removed until a moderator approves it), depending on the moderation action setting. An optional **AI moderation** layer adds LLM classification on top of keyword checks, at a per-message cost. ### Customizing the Ask AI assistant Go to **Chat → Settings → Ask AI identity**. You can set a custom name, description, history tip text, and avatar. This identity applies to the assistant in chat rooms and the Ask AI sidebar. ### Monitoring the dashboard Go to **Chat → Dashboard** (visible to all users). The personal dashboard shows: - Active conversations this week with a 4-week sparkline - Median response time on @mentions compared to the team - Messaging hours heatmap with a working-hours percentage - Top conversations with 14-day trend arrows - AI answer feedback (reactions on AI messages, from a nightly rollup) - Ask AI activity (turn volume, latency, and token usage) ## 5. Settings All settings are at **Chat → Settings** (company admins and Chat admins; the rows marked "Company admins only" are changed by company admins alone). | Setting | Default | What it changes | |---|---|---| | **One-to-one messages** | On | Whether users can start one-on-one direct messages | | **New group chats** | On | Whether users can create new multi-person group rooms; turning it off leaves existing groups, channels and project rooms working | | **Important messages** | On | Whether the Important message composer option is available | | **Read receipt requests** | On | Whether the Read receipt request composer option is available | | **Edit messages** | On | Whether users can edit their own text messages after sending (within 15 minutes) | | **Delete messages** | On | Whether users can delete their own messages and room admins anyone's; when off, nobody can delete messages — room admins included | | **File uploads** | On | Whether file attachments are allowed in messages | | **Max file size — images and documents (MB)** | 25 | Per-file cap for non-video uploads | | **Max file size — video (MB)** | 500 | Per-file cap for video uploads | | **Typing indicators** | On | Whether the "user is typing" animation appears | | **Show who has seen a message** | On | Whether senders see "Seen by" — the reader in a 1:1 chat, and up to three names then how many more in a group of up to 50 — and "Read by N%" with its list in conversations of more than 50 people. When off, senders see only "Sent" or "Delivered", and nobody can see how far anyone else has read. Important messages and read receipt requests are not affected | | **Keep messages for** | Forever | Company admins only: how long messages are kept, set separately for one-to-one messages, groups and channels (at least 30 days). Each night, messages older than that are hidden from everyone, and they are permanently deleted 30 days later; anything on legal hold is kept for your records | | **Information barriers** | None | Company admins only: pairs of groups whose people can't message each other | | **Semantic search** | On | Enables pgvector-backed semantic search across messages | | **Live Assist huddles** | Off | Adds **Start huddle (Live Assist)** to each conversation's **…** menu, and a **Start huddle** button at the end of the conversation on a phone (requires the Live Assist app, enabled and published to the people using it) | | **AI huddle summaries (records huddles)** | Off | Records every huddle automatically and posts an AI summary to the room when it ends, unless the huddle was too short to summarise; participants see a recording notice. Requires Live Assist huddles | | **Enable Chat Agent in Ask AI (read-only)** | On | Lets users search chat history and find conversations from the Ask AI sidebar (read-only) | | **Enable Chat actions in Ask AI** | On | Lets users start chats and send messages from the Ask AI sidebar, with confirmation before each action | | **Ask AI in Chat (@mention)** | On | Lets anyone bring the assistant into a conversation with @Ask AI | | **Ask AI trigger phrases** | On | Also invoke Ask AI when a message starts with a trigger phrase (no @mention needed) | | **Ask AI trigger phrases (comma-separated)** | /ai | The phrases that invoke Ask AI, case-insensitive (workspaces set up before September 2026 keep "hey ai, /ai") | | **Ask AI proactive suggestions** | On | Lets Ask AI chime in proactively in rooms that have opted in | | **Ask AI streaming replies** | On | Streams Ask AI replies token-by-token rather than posting the full answer at once | | **Ask AI grounded answers** | On | Grounds Ask AI answers in the room's own history via embeddings retrieval (requires Semantic search) | | **Ask AI in-chat actions** | On | Lets Ask AI execute actions (e.g. open Service Desk tickets) from inside chat; every action requires confirmation (workspaces set up before September 2026 keep Off until an admin turns it on) | | **Ask AI thread summaries** | On | Allows on-demand AI summaries of a conversation | | **Ask AI unread digest** | On | Enables the catch-me-up digest of unread conversations | | **Ask AI reads attachments** | On | Lets Ask AI extract and answer over attachment contents in the thread | | **Ask AI monthly token budget** | 0 (unlimited) | Monthly cap on in-chat Ask AI token spend; 0 means unlimited | | **Ask AI composer assist** | On | Offers AI rewrite/expand assists in the message composer | | **Ask AI smart replies** | On | Suggests one-tap reply chips under incoming messages | | **Working hours start (24h)** | 9 | Hour the workday starts; used by the dashboard outside-working-hours statistic | | **Working hours end (24h)** | 18 | Hour the workday ends; must be after the start hour | ## 6. More help - **Chat FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about Chat from these articles. **Keywords:** chat, direct message, group chat, channel, instant message, real-time messaging, @mention, Ask AI in chat, huddle, typing indicator, read receipt, important message --- # Chat FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-19 Answers to common setup and operating questions about Chat — for the admin running it. # Chat FAQ Answers to common setup and operating questions about Chat. For what the app is and how to set it up from scratch, see the [Chat Overview](/help/articles/chat_app_overview). --- ## Setup ## Do I need to enable anything else before Ask AI's grounded answers work in chat? Yes. **Ask AI grounded answers** requires **Semantic search** to also be on. Grounded answers retrieve conversation history through embeddings, so if semantic search is off the assistant has nothing to search against and its replies will not reference the room's history. Both settings default to on, but if either was turned off you need both enabled. When you first turn semantic search on (or back on), a background job backfills embeddings for all existing messages — the Settings page shows progress so you can tell when history is fully searchable. ## Who can change Chat settings? Company admins (admin role or above) and Chat admins — except **Keep messages for** and **Information barriers**, which company admins alone can change. The Analytics dashboard can also be opened by the people an admin names in Settings, and Recently deleted also shows each person the conversations they deleted themselves. --- ## Permissions and access ## Who can delete a conversation for everyone? Only the person who created the group or channel, or a Chat admin. Direct messages cannot be deleted for everyone. "Delete for everyone" is a soft delete — the conversation enters a 30-day restore window at **Chat → Recently deleted**, where the person who deleted it or a Chat admin can restore it. After 30 days it is permanently purged, unless a legal hold keeps it. ## What are the per-room permission settings? Group and channel rooms list them under **Conversation settings** (the gear button in the room header, shown to the room's admins): - **Who can add new members?** - **Who can see the group (or channel) member list?** - **Who can send messages in this group (or channel)?** - **Who can send important messages and request read receipts?** — only where Important messages or read receipt requests are on and allowed in that room - **Who can reply in threads?** — channels only Each is answered with **Any member**, **Conversation admins and company admins**, or **Company admins only**, and all default to fully open (any member). Conversation admins are the room's own admins; company admins are your organization's admins, and anything open to conversation admins is open to them too. --- ## Day-to-day ## How long can someone edit a message after sending it? 15 minutes. After that the edit option disappears. Only the sender can edit their own messages, and only text — media-only messages are not editable. Company admins and Chat admins can turn editing off entirely with the **Edit messages** toggle in Settings. ## Who can delete individual messages? A user can delete their own messages at any time (no time limit). A room admin can delete anyone's messages in that room. Both capabilities are governed by the **Delete messages** toggle in Settings — when it is off, nobody can delete chat messages, room admins included. ## What happens when a sender marks a message as Important or requests a Read Receipt? **Important** messages require each recipient to acknowledge them explicitly. **Read Receipt** requests keep the message body hidden until each recipient confirms they have read it. Both are per-message choices available in the composer for direct messages, groups and private channels of up to 50 people — not in public channels or in channels of more than 50 people. Each feature has its own business-level toggle (**Important messages** and **Read receipt requests**) in Settings. In a group or a channel, the sender sees "Read by X/Y" and who has and hasn't read it; when the sender was a manager or a room admin at the time they sent it, they can also send a reminder to the people who haven't, and other messages have no Remind button — making someone an admin later does not add one to what they already sent. In a 1:1 chat the sender sees when it was read. If the sender set a backup who is not in the conversation, the backup's notice names who hasn't confirmed and offers a "Message" button to start a chat with them, without the message's words. ## What does an approval card in Chat say once someone decides it elsewhere? It says who decided it and, when known, where — for example "Approved by you, from your Inbox" or "Declined by Dana, on the approvals page" — instead of only "Already handled". ## Who sees "Seen by" on a message? The sender. In a 1:1 chat they see "Seen by" and the other person's name; in a group of up to 50 people, under their latest message someone has read, the names of who has read it — up to three, then how many more ("Seen by Ana, Bob, Cy +2"). In a conversation of more than 50 people they see "Read by N%" instead, which opens the list of who has read it. An admin can turn this off with **Show who has seen a message** in Settings; senders then see only "Sent" or "Delivered". Important messages and read receipt requests keep their own "Read by X/Y" either way. ## Can we export Chat history for a legal matter or an investigation? Yes — a company admin can, from **Admin → Compliance → Chat Export**. Choose up to 50 people and a range of days (at most 3 years), and optionally only some of their conversations. The ZIP holds every conversation those people were in during those days, with every message in them, deleted messages and earlier versions of edited ones included. Only the admin who started it can download it, for 7 days; then the file is deleted, and the record of the export stays. To keep a conversation past your retention settings without joining it, a company admin uses **Hold a conversation** on **Admin → Compliance → Retention & Legal Holds** (found by its name or its people; nobody in it is told), and lifting a conversation's hold asks for a reason. ## What are the limits on file and video attachments? Up to 10 files per message. Non-video files default to a 25 MB per-file cap (admins can set it anywhere from 1 to 500 MB). Video has a separate, larger cap that defaults to 500 MB (configurable from 1 to 2,000 MB). Executable file types (.exe, .bat, .sh, .msi, .dll, and others) are blocked, and browser-renderable formats (.html, .svg) are also refused. Allowed types cover documents, images, audio, video, archives, and fonts. ## How does search work, and when should we enable semantic search? Keyword search (full-text) is always on and covers most needs — you can filter by room, sender, and date range. **Semantic search** adds a meaning-based mode that finds messages even when the exact words differ. It is on by default. When you first enable it (or turn it back on after it was off), a background job backfills embeddings for your existing message history. After the backfill completes, new messages and edits keep their embeddings current automatically. If your organization does not need meaning-based search and wants to avoid the embedding cost, turn it off in Settings. ## Can I customize the Ask AI assistant's name and avatar? Yes. Go to **Chat → Settings → Ask AI identity**. You can set a custom name, description, history tip text, and avatar. This identity applies to the assistant in chat rooms and the Ask AI sidebar — updating it in one place updates it everywhere. ## How do Ask AI trigger phrases work? When enabled (on by default), a message that starts with a trigger phrase invokes Ask AI without an @mention. The default phrase is **/ai** (case-insensitive); workspaces set up before September 2026 keep **hey ai** and **/ai** until an admin changes the list. Phrases are matched at word boundaries, so "Hey Aisha" does not accidentally trigger the assistant. You can customize the phrase list in Settings under **Ask AI trigger phrases**. --- ## When something looks wrong ## "I can't see the Chat app in my navigation" Chat is a licensed app that is off by default. An admin must enable it from **Admin → Apps → All Apps → Chat → Enable**. If the app is enabled but only some users can see it, check whether a contextual access policy has been configured — the access gate is enforced on every request, so a user outside the policy's audience will not see the app. ## "My employees say they can't start a DM with someone" Check two things: (1) the **One-to-one messages** toggle in Settings must be on, and (2) if a contextual access policy is configured, both the sender and the recipient must be within the policy's audience. Starting a DM with yourself is also not allowed — the app refuses it with an error. ## "Someone deleted a group chat — can I get it back?" Yes, if it was deleted within the last 30 days. Go to **Chat → Recently deleted** — the person who deleted it sees it there, and a Chat admin sees every deleted conversation. You can search by room name or participant name, filter by type (direct, group, channel), and restore individual rooms or select multiple rooms to restore in bulk. After 30 days the conversation and its messages are permanently purged and cannot be recovered, unless a legal hold keeps them. ## "Start huddle isn't showing up in chat rooms" **Start huddle (Live Assist)** is an item in each conversation's **…** menu at the top right of the room, not a button in the room header. On a phone it is a full-width **Start huddle** button at the end of the conversation, below the last message. Either one appears when: (1) **Live Assist huddles** is on in Chat → Settings (off by default); (2) the **Live Assist** app is enabled and published to the person — while it is published to admins only, nobody else sees it; (3) Live Assist's **Who can start a Live Assist session?** setting admits them; and (4) they are a member of the room who can send messages in it. The Live Assist section of Chat → Settings names whichever Live Assist prerequisite is missing. --- ## Licensing and limits ## Does Chat require a licence? Yes. Chat is a licensed app — it requires a licence and is disabled until an admin enables it from Admin → Apps → All Apps. It comes with the Communications & Intranet suite. ## What are the configurable ranges for attachment sizes? | Setting | Default | Range | |---|---|---| | Max attachment size (non-video) | 25 MB per file | 1–500 MB | | Max video attachment size | 500 MB per file | 1–2,000 MB | | Max files per message | 10 | Not configurable | ## Are there limits I should know about? - **Max files per message:** 10 - **Message edit window:** 15 minutes after sending - **Reaction emoji set:** 10 platform-default emojis - **Deleted conversation restore window:** 30 days before permanent purge - **Room name length:** 255 characters maximum - **Room topic length:** 500 characters maximum - **Working hours (dashboard stat):** configurable, defaults to 9:00–18:00; start accepts 0–23, end accepts 1–24 - **Ask AI monthly token budget:** 0 means unlimited; configurable up to 2,000,000,000 --- ## More help - [Chat Overview](/help/articles/chat_app_overview) - Ask AI — the assistant answers Chat questions from these articles. **Keywords:** faq, chat, direct message, group chat, channel, read receipt, file upload, attachment limit, semantic search, Ask AI, huddle, typing indicator, message editing, deleted conversation, troubleshooting --- # Classifieds App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run the internal Classifieds marketplace — categories, moderation, expiration, and settings. # Classifieds ## 1. What it is Classifieds is an internal marketplace where employees post items for sale, give things away, request items, or offer services to colleagues. All exchanges are peer-to-peer within the company — the platform does not facilitate payment or guarantee transactions. - **Enablement:** Classifieds requires a license and is off by default. An admin enables it from Admin → Apps → All Apps. - **What it is not:** Classifieds is not an e-commerce storefront. There is no cart, checkout, or payment processing. Buyers and sellers arrange everything directly. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Classifieds**. 2. Open **Classifieds → Settings** (the gear icon in the sidebar). The app works with its defaults, but review the **Moderation** tab before launch — decide whether listings require admin approval before they go live (off by default) and add any auto-moderate keywords or prohibited category names your organization needs. 3. Categories are created from the Classifieds home page. Create at least a few (e.g. Furniture, Electronics, Books) so employees can browse by topic. Categories require a name, an icon, and a color. Category is required on every listing by default. 4. Grant **App Admin** access to anyone who should moderate listings and review reports but is not a full business admin. App Admins see Pending Approval, Admin Reports, Analytics, and Settings under **Admin** in the sidebar. 5. Confirm it worked: any logged-in employee should see **Classifieds** in the app launcher and be able to post a listing. Admins should see the full sidebar: Home, Browse Listings, My Listings, My Favorites, Post Listing, and an **Admin** group holding Pending Approval, Admin Reports, Analytics, and Settings. **Email is off until you turn it on:** if you turn on **Require Admin Approval** but leave **Notify About New Listings** off, moderators are still asked in their inbox when a listing needs approval, but nobody is emailed. Turn both on together if your moderators rely on email. **Who is told:** inbox asks about listings awaiting approval and about reported listings go to the moderator group you select in the notification setting — only to its members who can moderate. If no group is selected, or nobody in it can moderate, they go to the Classifieds App Admins, and to the business admins when the app has none. **Notify About New Listings** adds an email when a listing needs approval. ## 3. How it fits together **Listings** — the central object. Each listing has a title (up to 100 characters), a description (up to 2,000 characters), a type, optional photos and videos, a price (for items being sold), a category, and an optional location tied to a business location. Listings auto-expire after a configurable number of days (default 30). The poster — or an admin — can renew a listing that is expired or within 7 days of expiring. Deleting a listing is a soft delete; it is hidden from Browse but preserved for reporting. A listing can be edited by its owner, a business admin, or a Classifieds App Admin — but only while the listing is active or pending approval. Anyone in those same roles can delete a listing at any time, and mark an active listing fulfilled — which cannot be undone. There are four listing types, and the type determines price behavior: - **For Sale** — price is required and must be greater than zero. - **Free / Giveaway** — price is forced to zero. - **Wanted / Request** — price is forced to zero. The poster is looking for an item. - **Services Offered** — price is optional. The poster offers a service. Supported currencies are USD, EUR, GBP, and CAD. The default is USD. A listing moves through these statuses during its life: - **Pending Approval** — waiting for admin review (only when approval is required or the listing was auto-flagged). Not visible in Browse to other users. - **Active** — live and visible in Browse. - **Expired** — past its expiry date. Hidden from Browse. Can be renewed. - **Fulfilled** — the poster (or a moderator) marked the deal as done. Favoriters are notified, and so is the poster when a moderator closed it. - **Deleted** — soft-deleted, by the poster or by a moderator. Hidden from Browse and from colleagues; the poster still sees it under **Removed** in My Listings. Example: an employee posts a standing desk under **Furniture → For Sale** at $150, attaches 3 photos, and picks their office location. It appears in Browse for 30 days. A colleague favorites it, gets notified when the price drops to $100, and uses **Message Seller** to open a direct-message thread about pickup. **Categories** — every business manages its own set. A category has a name (unique within the business), an icon, a hex color, and a sort order. System categories (seeded at setup) cannot be deleted. Custom categories can be deleted only when they have zero listings. Each category tracks its own active listing count. Prohibited category names (default: weapons, alcohol, drugs, adult) block listing creation at the form level — the match is case-insensitive and substring-based, so "adult" also blocks "Adult Content." **Favorites** — employees can save a listing to their My Favorites list and access them from the **My Favorites** tab. When a favorited listing's price drops, the platform notifies every user who favorited it with the old and new price. When a listing is marked as fulfilled, favoriters are notified that it is no longer available. Favorites can be turned off entirely in Settings; when off, the My Favorites tab is hidden. **Reports and moderation** — employees can report a listing as Inappropriate Content, Spam or Duplicate, Fraudulent or Misleading, Prohibited Item, or Other (with a required description). Each user can report a given listing once. Reports land in the **Admin Reports** queue, and the moderators are told in their inbox; a report has four resolution states: Pending, Reviewed, Resolved, and Dismissed. Separately, the keyword auto-moderation system scans the title, description, and tags of every new or edited listing against the configured keyword list. A match automatically routes the listing to the approval queue and creates a report record so it appears in Admin Reports. **Saved searches** — an employee saves their current Browse filters (category, type, location, keyword, with photos, free-only) as an alert with notifications on by default. A daily scan (13:00 UTC) checks each notifying saved search for newly-matching listings and sends an in-app notification to the owner that opens the new listing (or the matching results, when there are several). **Send interest to seller** — sends the seller a one-on-one message through the Messages app naming the listing, then opens that conversation in the inbox so both people can carry on. On a Wanted post it reads **Reply to this request**. It appears only on a live listing, when Messages is on for the organization, the viewer may start a conversation with the seller and the seller still works here — and never on the viewer's own listing. ## 4. Running it ### Reviewing pending listings When **Require Admin Approval** is on, or when auto-moderation flags a listing, it lands on the **Pending Approval** page. Approve or reject listings individually or in bulk. The tab shows a badge with the current pending count. 1. Open **Classifieds → Admin → Pending Approval**. 2. Review each listing's content and photos. Filter by category or search by title. 3. Click **Approve** to publish it, or **Reject** with a reason to soft-delete it. Use the checkboxes and bulk action bar to process several at once. The poster is told in their inbox (and by email if they have an address on file) when their listing is approved or rejected. A rejection's reason is sent word for word. A rejected listing cannot be edited, so the poster's notice and **My Listings** offer **Fix and post again**: a new listing that starts from what they wrote, which a moderator checks again while approval is on. ### Handling reports 1. Open **Classifieds → Admin → Admin Reports**. 2. Filter by status (Pending, Reviewed, Resolved, Dismissed) or by category. 3. Open a report to see the listing, the reporter, and the reason. 4. Mark the report as Reviewed (confirmed problematic), Dismissed (no action needed), or Resolved (issue fixed). Bulk actions are available. Marking a report does not change the listing. To take a reported listing down, open it and delete it: the poster is told in their inbox, and every report still pending on that listing is marked Resolved under your name. Rejecting a listing from Pending Approval resolves its pending reports the same way. A poster deleting their own listing leaves its reports pending for a moderator to close. ### Exporting data Admins can export all listings or all reports as CSV. - **Listings CSV** — title, category, type, status, price, currency, location, posted by, views, favorites, created date, and expiry date. - **Reports CSV** — listing title, category, reason, description, reported by, status, reported date, reviewed by, reviewed date, admin notes, and resolution notes. ### Monitoring the marketplace The **Analytics** tab (admin-only) shows total, active, fulfilled, expired, and pending listing counts, plus a breakdown by type and category, top posters, most-viewed and most-favorited listings, and a daily new-listings chart. Switch between 7-day, 30-day, and 90-day windows. The default view is 30 days. ### Automatic expiration A nightly job (01:30 UTC) flips any listing past its expiry date to **Expired** status. When **Notify About Expiring Listings** is on, the poster is also told — in-app, and by email if they have an address — 7 days before expiry (once per listing) and again when it expires. Expired listings can be renewed by the owner or an admin. ## 5. Settings All settings live at **Classifieds → Settings**, organized into tabs. | Setting | Tab | Default | What it changes | |---|---|---|---| | **Enable Classifieds** | General | On | Master switch for the app within this business | | **Max Active Listings Per User** | Posting | 10 | How many listings one person can have live or waiting for approval at once | | **Auto-expire Listings (days)** | Posting | 30 | Days until a listing expires automatically | | **Require Category** | Posting | On | Whether a category must be chosen on every listing | | **Require Location** | Posting | Off | Whether the location field is mandatory | | **Max Photos Per Listing** | Media | 5 | Photo limit per listing | | **Max Videos Per Listing** | Media | 1 | Video limit per listing | | **Max Photo Size (MB)** | Media | 10 | Maximum file size per photo | | **Max Video Size (MB)** | Media | 100 | Maximum file size per video | | **Require Admin Approval** | Moderation | Off | Whether every new listing needs admin approval before going live | | **Enable User Reporting** | Moderation | On | Whether employees can flag listings for review | | **Auto-moderate Keywords** | Moderation | *(empty)* | Comma-separated keywords that auto-flag a listing for approval | | **Prohibited Categories** | Moderation | weapons, alcohol, drugs, adult | Category names that cannot be used for listings | | **Notify About New Listings** | Notifications | Off | Email moderators when a new listing needs approval | | **Notify About Expiring Listings** | Notifications | On | Tell the poster (in-app and by email) when their listing is about to expire or has expired | | **Show Poster Department** | Privacy | On | Display the poster's department or location on listings | | **Enable Favorites** | Features | On | Let employees favorite listings for later viewing | | **Enable View Counter** | Features | On | Track and display how many times a listing has been viewed | | **Enable AI Agent** | AI | On | Let users query listings through Ask AI | **Browse and search:** the Browse Listings page shows active listings with filters for category, listing type, location, keyword search, photos only, and free items only. Sort by newest, most popular (views), or most favorited. Results are paginated at 20 per page. **Mobile access:** Browse, My Listings, My Favorites, Post Listing, and listing detail all have dedicated mobile views at `/m/apps/classified`. Phone-class browsers are redirected automatically. Admin surfaces (Pending Approval, Admin Reports, Analytics, Settings) stay on the desktop view. ## 6. More help - **Classifieds FAQ** — specific setup and operating questions. - Ask AI — the assistant answers questions about Classifieds from these articles. **Keywords:** classifieds, marketplace, buy sell trade, listings, for sale, free giveaway, wanted, services offered, classified moderation, listing approval, classified --- # Classifieds FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Classifieds — for the admin running it. # Classifieds FAQ Answers to common setup and operating questions about Classifieds. For what the app is and how to set it up from scratch, see the [Classifieds Overview](/help/articles/classified_app_overview). --- ## Setup ## Do I need to configure anything before employees can start posting? The app works with its defaults as soon as you enable it, but review two things first. Create at least a few categories (e.g. Furniture, Electronics, Books) — category is required on every listing by default. And if you turn on **Require Admin Approval**, also turn on **Notify About New Listings** in the same settings pass. Otherwise listings queue up for approval with no email to anyone. ## Who can moderate listings and review reports? Business admins, super admins, and anyone granted **App Admin** for Classifieds. App Admins see Pending Approval, Admin Reports, Analytics, and Settings under **Admin** in the sidebar. They can approve or reject pending listings, act on reports, edit or delete any listing, and export data. --- ## Permissions and access ## Why can't some employees see the Classifieds app? Two gates must both be open. First, an admin must enable Classifieds from Admin → Apps → All Apps. Second, the per-business **Enable Classifieds** toggle in Classifieds Settings must be on (it defaults to on). If either is off, employees are redirected away. ## Who can edit or delete another person's listing? A business admin, super admin, or Classifieds App Admin can edit any listing that is still active or pending approval. The same roles can delete a listing in any status, and mark an active listing fulfilled. Regular employees can only act on their own listings. --- ## Day-to-day ## How many active listings can one person have? 10 by default. You can change it under **Settings → Posting → Max Active Listings Per User**. When someone hits the limit, the form tells them and blocks the post until they fulfill, delete, or let one expire. ## How long does a listing stay up before it expires? 30 days by default, configurable under **Settings → Posting → Auto-expire Listings (days)**. A nightly job expires overdue listings and sends the poster an email. Seven days before expiry, the poster also gets an expiring-soon email (sent once per expiry cycle). ## Can I renew a listing after it expires? Yes. The owner, a business admin, or an App Admin can press **Renew** on the listing page or on **My Listings** — on an expired listing, or one within 7 days of expiring. Renewing sets it to expire the **Auto-expire Listings** number of days from today (30 by default), puts an expired listing back on Browse, and resets the expiring-soon notification so the poster gets a fresh warning before the new date. A listing still waiting for a moderator can't be renewed; if its days run out while it waits, approving it starts a fresh listing period. ## What happens when someone marks a listing as fulfilled? The listing moves to **Fulfilled** status and drops out of Browse. Every employee who favorited it gets an in-app notification that it is no longer available. It cannot be reopened afterwards. On the phone, whoever closes it can add an optional note. A moderator can mark someone else's listing fulfilled; the poster is then told in their inbox. ## What notifications does the app send? | Event | Who receives it | Channel | |---|---|---| | Listing needs approval | Moderators (the configured group, else App Admins, else business admins — only people who can moderate) | In-app, plus email (to moderators who have an address) when **Notify About New Listings** is on | | Listing reported by an employee | The same moderators | In-app | | Listing approved | The poster | Email + in-app | | Listing not approved | The poster | Email + in-app | | Listing removed by a moderator | The poster | In-app | | Listing marked fulfilled by a moderator | The poster | In-app | | Listing edited by a moderator and sent back for approval | The poster | In-app | | Listing expiring in 7 days | The poster | Email + in-app | | Listing expired | The poster | Email + in-app | | Price dropped on a favorited listing | Everyone who favorited it | In-app | | Favorited listing marked fulfilled | Everyone who favorited it | In-app | | Saved search has new matches | The search owner | In-app | Expiring and expired reminders — both the email and the in-app notice — are controlled by the **Notify About Expiring Listings** setting (on by default). The moderators' needs-approval email is controlled by **Notify About New Listings** (off by default). ## How do saved searches work? An employee saves their current Browse filters (category, type, location, keyword, with photos, free-only) as an alert. A periodic job checks for new listings that match, and notifies the owner in-app. The search can be deleted from the Saved Searches page at any time. Notifications default to on for new saved searches but each search can be toggled individually. --- ## When something looks wrong ## Why was my listing sent back for approval after I edited it? Two things send a live listing back. If **Require Admin Approval** is on, changing the title, description, or tags of a live listing puts it back in the approval queue (a price, photo, location or contact change does not). And if an admin has configured auto-moderate keywords, editing the title, description, or tags triggers a re-check: when any keyword matches, the listing is pulled back to **Pending Approval** and flagged for review. Either way the person who saved the edit sees a message that the listing is pending approval, and when a moderator made the edit the poster is told in their inbox. ## I can't post a new listing — it says I've reached the limit Each user is allowed a maximum number of listings that are live or waiting for approval at a time (default 10). Fulfilled, expired, and deleted listings do not count. Free a slot by fulfilling or deleting an existing listing. Ask your admin if the limit has been lowered from the default. ## My listing disappeared from Browse — what happened? Three things remove a listing from the Browse page. It expired (check your expiry notices — you can renew it from **My Listings**). An admin deleted it or rejected it from the approval queue. Or auto-moderation re-flagged it after an edit. Check your **My Listings** page — it shows counts by status, including pending and expired. ## My listing was not approved — how do I fix it? You are told in your inbox (and by email if you have an address on file), with the moderator's reason if they gave one. A rejected listing cannot be edited — it stays on **My Listings** under **Removed**, marked **Rejected** with any reason. Tap **Fix and post again** there, or the notice itself: it opens a new listing already holding what you wrote, so you change what needs changing and post it. Photos and videos are not carried over; add them again. If approval is still on, a moderator checks the new listing before it goes live. ## I don't see a "Send interest to seller" button on a listing That button sends the seller a short message in Messages for you ("Hi, I'm interested in your classified listing …") and opens the conversation. On a Wanted post it reads **Reply to this request** and says you may have what they are looking for. It appears only on a listing that is live on Browse, when your organization has Messages turned on, you are allowed to start a conversation with that person and they still work here — and never on your own listings. If you don't see it, use the contact details on the listing, or ask your admin who may start conversations in Messages. --- ## Moderation ## How does keyword auto-moderation work? Under **Settings → Moderation → Auto-moderate Keywords**, enter a comma-separated list of keywords. When any keyword appears anywhere in a listing's title, description, or tags (case-insensitive), the listing is routed to the approval queue instead of going live. The check also runs on edits — if a live listing is edited and the new content matches, it is pulled back to pending approval. ## Can I delete a category once it has been created? Custom categories can be deleted only when they have zero listings. System categories (seeded when the app is set up) cannot be deleted at all. If a category still has listings, deactivate it instead — inactive categories stop appearing in the Browse filter and the new-listing form. --- ## Licensing and limits ## Does Classifieds require a license, and who turns it on? Yes. Classifieds requires a license and is off by default. An admin enables it from **Admin → Apps → All Apps**. Once enabled, every employee in the organization can browse and post. ## What are the photo and video limits? | Limit | Default | Configurable? | |---|---|---| | Photos per listing | 5 | Yes | | Max photo size | 10 MB | Yes | | Photo formats | JPG, JPEG, PNG, GIF | Yes | | Videos per listing | 1 | Yes | | Max video size | 100 MB | Yes | | Video formats | MP4, MOV, AVI | Yes | All of these are editable under **Settings → Media**. The poster sees a validation error at upload time if a file exceeds the size or format limit. ## What currencies and price limits are supported? Four currencies are supported: USD, EUR, GBP, and CAD. The default is USD. The maximum price is $99,999,999.99. For **Free / Giveaway** and **Wanted / Request** listing types, price is forced to zero automatically. --- ## More help - [Classifieds Overview](/help/articles/classified_app_overview) - Ask AI — the assistant answers Classifieds questions from these articles. **Keywords:** faq, classifieds, listings, marketplace, moderation, approval queue, favorites, expiration, auto-moderate keywords, prohibited categories, listing limit, reports, classified --- # Communications FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-17 Answers to common setup and operating questions about Communications — for the admin running it. # Communications FAQ Answers to common setup and operating questions about Communications. For what the app is and how to set it up from scratch, see the [Communications Overview](/help/articles/communications_app_overview). --- ## Setup ## Which features are on by default and which need to be turned on? The Calendar, Idea Bank, Content Plan, Campaigns, Audiences, Analytics, Newsletters, AI Writer, Brand Voices, Comms Grader, writing help in the composer, and the read-only AI help agent are all on by default. Comms Triggers are on for new organizations; organizations that already had Communications when triggers were introduced keep them off until an admin turns them on. Approval Workflows, LinkedIn cross-post, the admin AI agent (drafting), and most signal-extraction and AI features (automatic topic tagging, discussion summaries, poll summaries, finding experts automatically, reader translation) are off by default and must be turned on in settings. Newsletters come with the app. To hide them, turn off **Newsletters** under **Settings → Modules**; the Publications and Issues surfaces and the Newsletters tab then disappear. --- ## Permissions and access ## Who can post Announcements, Must-Reads, and posts to Everyone? The **Who can post Announcements & Must-Reads** setting controls both types in the composer. The options are **Off** (removes both types for everyone, including admins), **Admins only**, **Admins and leadership**, or **Admins, leadership, and managers**. The default is **Admins and leadership**. Leadership is a job-title property, not the manager role — a manager without a leadership designation is not included under **Admins and leadership**. A separate setting, **Who can post to Everyone**, has three options: **Admins only**, **Admins and leadership** (the default), or **Anyone**. On the Broadcast page, anyone who may send broadcasts is offered Everyone regardless of this setting. ## Who can manage Audiences, send Newsletter issues, and access Comms Analytics? Audience administration and newsletter sending require the **publish communications** capability — by default that means admins and Communications app-admins. Comms Analytics and Triggers are admin-only. The Calendar, Idea Bank, and Campaigns are visible to all users who have access to the app; creating or changing the Content Plan is limited to admins and Communications app-admins. ## Why can't I see the Communications app? Three things must be true for an employee to see it: the Communications licence is enabled for the tenant, the app is accessible to the employee through your Access Management rules (visibility rules, work-context gates), and the employee is not excluded by a location or shift scope. Check all three if someone reports the app is missing. --- ## Day-to-day ## Can I edit a post after it's published? Yes, at any time. The author and Communications admins can edit a published post, and it shows **[edited]** afterwards. One exception: once people have acknowledged a post, it is locked and nobody can edit it, because those acknowledgements apply to the exact words. Comments can be edited for 15 minutes after posting. An admin can turn editing off for everyone with **Allow editing posts, polls, questions & comments** in settings. ## How do I feature a notice for a limited time? On a published post, open **Post actions → Feature notice**. Choose the start and end, set its order among featured notices, and optionally narrow it to an existing audience. **Preview audience** shows the readers who match both that audience and the post's current visibility. Save to schedule it; return to the same editor and choose **Stop featuring** to end it early. Admins, Communications app-admins, and communicators with permission covering the post's audience can feature notices. Active notices lead **All Posts**, and lead within each section on the mobile landing page and in Home's News Feed card. Readers see a **Featured** label and expiry. Featuring does not send an alert, create an acknowledgment requirement, or change anyone's personal pins. Withdrawing or deleting the source post ends its feature. ## What happens when I publish a Must-Read? The post is published and its recipient list is frozen immediately. Each recipient sees an acknowledge button, and the post keeps asking until its due date plus any extra days you chose (see the next question). Automated reminders are sent at 24 hours and 48 hours after publish (gated on the **Automated acknowledgement reminders** setting, on by default). Reminders are held to an 8 AM–8 PM local delivery window so nobody gets a reminder notification at 3 AM. A Must-Read is its own type in Compose — a Post or Announcement that has gone out can't be turned into one. ## How do I give a Must-Read or Broadcast a due date, and what makes someone overdue? Set **Due by** in the composer's Acknowledgement card. It must be in the future and, for a scheduled post, after the send time. If you leave it blank, the **Must-Read default due date (days after sending)** setting sets the due date: 7, 14, 30, 60 or 90 days after sending (default 30). **After the due date** decides what happens next: - **Keep asking for 3, 7 or 14 more days, marked overdue** — 7 is preselected. Anyone who still hasn't acknowledged is **Overdue** for those days. - **Take it out of the must-read lane** — the ask ends at the due date, so nobody is ever marked overdue. You can move the due date later from the post's edit page; the extra days move with it. Once the post stops asking, someone who never acknowledged shows as not acknowledged rather than overdue. For a Broadcast, fill in **Acknowledge by (optional)** under **Require acknowledgment**. It must be after the send time and within 30 days of sending, because a Broadcast stops asking for acknowledgement 30 days after it goes out. Leave it blank and the ask stays open with no due date, so nobody is marked overdue. ## How do I see which of my team haven't acknowledged a must-read? On the desktop, open **Measure → Acknowledgements**, pick the item, and use the **Show** filter: **Everyone**, **Not acknowledged**, **Overdue**, or **Acknowledged**. A manager who didn't write the item sees only their own direct reports in its audience. Admins, Communications app-admins and the item's author see everyone. On a phone, tap **My team** on the Communications home. **My Team's Must-Reads** lists every must-read and Broadcast your team still owes, with overdue ones marked. The **My team** link appears only if people report to you. ## A must-read in my Inbox says Overdue — can I still acknowledge it? Yes. **Overdue** means its due date has passed while the post is still asking. You can acknowledge it from **Waiting on you** in your Inbox or from the post itself until it stops asking. After that, acknowledging is refused because the acknowledgement window has closed. ## How do I send only to people who are on shift? In the composer's audience card, choose **Specific people or groups**, then **People who match all of several attributes**, pick at least one attribute, then tick **Only people on shift**. Choose when they count as on shift: - **Now** — clocked in, or on a scheduled shift, at the moment it sends. - **Today** — clocked in when it sends, or on a scheduled shift any time that day (12:00 AM to 11:59 PM). - **Tonight** — on a scheduled shift between 6:00 PM and 6:00 AM, or clocked in if it sends within those hours. - **Next hours** — clocked in when it sends, or on a scheduled shift running in the next 1 to 24 hours (default 4). Today and Tonight use each site's own local time. The audience is worked out again at every send, so a repeating message reaches whoever is on shift that time. ## How do I send only to people who match several things at once, like New York and a sales title? In the composer's audience card, choose **Specific people or groups**, then **People who match all of several attributes**. Tick values under each attribute you want: for example **New York** under **Location**, and every sales title under **Job title** (type "Sales" in its search box to find them). A person is included only when they match every attribute you set, and any one of the values you ticked within an attribute — New York or Boston, and a sales title. Each custom field counts as an attribute of its own. Departments are one attribute: the departments you tick, at any level, are alternatives. On a phone, choose **People who match all of several attributes** under **Audience** in the composer. The other choices under **Add to audience** — a department, a job title, a location, a role, a group — each add their people. A location and a job title added separately reach everyone at the location plus everyone with the title. ## Why didn't I get the message my coworkers on shift got? The sender probably limited it to people on shift during a set window. You are included only if you were clocked in when it sent, or had a scheduled shift inside that window. With **Now**, someone clocked in at a different site counts at that site, not this one. ## How do Broadcast acknowledgement reminders work? Broadcast reminders use their own settings, under **Settings → Broadcast**: **Reminder frequency** (every 2, 4, 8, 24, or 48 hours — default 24) and **Maximum reminders** (0–10 — default 3). A broadcast with **Auto-widen channels** ticked also sends a text with every reminder from the 2nd and a voice call with every reminder from the 3rd, on channels it uses — texts to people who haven't turned texts off or replied STOP, calls to people who take calls (everyone, on a Critical broadcast). When manager escalation is enabled, unacknowledged Must-Reads escalate to each employee's manager after a configurable window (24, 48, 72, 96, or 168 hours — default 72). ## What happens if my audience resolves to nobody when I hit Publish? The publish is refused. The message stays editable and tells you which audience needs attention. This applies to feed posts, broadcasts, scheduled sends, recurring sends, newsletter issues, and the API. A message is never reported as delivered when nobody received it. ## What is "Where people see it", and where does the message actually show up? It is the composer's card for where a message appears. Every type goes to **News and Inbox**. You can also tick extra places your company has switched on: **Top of Home** (one message at a time, 7 days at most), a **Store home** pin (when everyone the message reaches works at one store you manage), the shift a person is about to work (below the shift summary), the Time & Attendance screen while they are clocked in, their Benefits page beside the enrollment window, and break-room screens. A place shows only to people in the audience whose screen qualifies — the shift's date and site fall inside the window and sites you set, the punch is open, or an enrollment window is open (unless you untick that). The reader can dismiss it; if the message asks for acknowledgement, acknowledging removes it and writes the same acknowledgement record a must-read does. To show a Post or Announcement only in its places, tick **Skip News and Inbox** — no one gets a notification, and each place takes it down on the Until date you set for it (break-room screens have no Until date and keep it for up to 14 days after it is published). A must-read can't skip News and Inbox. Who may add which place: Top of Home needs publishing rights that cover everyone the message reaches (admins and Communications app-admins always have them); a store's home, a manager of that store; the shift, clock-in and Benefits places, anyone who may send that type of message. Usual audience limits still apply, and a place's site choice only narrows further. A Broadcast can be placed too: its places add to its normal delivery. ## Why don't I see the "Shift card" slot in the composer? It is off by default. The shift list is the schedule, and a marker on every card would read as a banner, so an admin has to switch it on deliberately under **Settings → Modules → Placement slots**. Once on, it offers a title-only line on qualifying shift cards in the Shifts list and the My Shifts calendar; tapping the shift opens the full message. ## What does "Shown" count in Measure's Placements table? People, not page loads. A person counts once per day when the surface actually rendered the card for them — a worker who reloads their shift ten times is one. Opened, Dismissed and Acknowledged are counted the same way, and the median time to acknowledge runs from the first time the card was shown to the acknowledgement. Placement counts are separate from a broadcast's Views (Views = opened the message itself); the broadcast page shows both side by side. ## Can the AI send or publish on its own? No. Every AI capability in Communications produces a draft or a suggestion. The AI Writer, Comms Grader, writing help in the composer, channel-native copy, newsletter drafter, and the admin AI assistant all stop at a draft or a suggestion the author accepts. A person must explicitly confirm before anything is published or sent. There is no setting that enables autonomous publishing. --- ## When something looks wrong ## "I changed my audience after publishing, but the acknowledgement roster didn't update" That is expected. The recipient list is frozen as a snapshot at publish time. Changing the audience definition after publish does not add or remove anyone from the compliance roster. This is deliberate — it keeps the audit trail stable. If you need to reach additional people, publish a new Must-Read to the updated audience. ## "My poll closed earlier than I expected" or "My poll never closes" Poll duration is set at creation time and accepts 1–30 days (default 7). You can also choose **Never** to keep a poll open indefinitely. Once published, the close date cannot be changed. If a poll closed sooner than expected, check the duration that was set when it was created. ## "Employees say they aren't getting broadcast SMS or voice calls" Check four things in order: (1) SMS or Voice call must be ticked on the broadcast itself — they start from your company's **Default Channels** (email only, unless an admin changed it); (2) your company must have that channel switched on — while it is off, no text or call goes, Critical included; (3) a broadcast that is not **Critical** texts or calls only people who turned texts or calls on in their own notification settings — a Critical one reaches everyone, except texts to anyone who turned texts off, replied STOP, or whose number can't receive texts; and (4) for SMS specifically, the employee's phone number must be verified. Voice calls need a phone number on file but not a verified one. Critical broadcasts bypass quiet hours; non-critical ones respect them unless the author turned off **Respect quiet hours**. Adding SMS or voice to a broadcast, or marking it Critical, is limited by **Who can add SMS, voice or Critical to a broadcast?** in the **Access** card on **Settings → Who can send what** (default: admins and Communications app-admins); someone sending from a template marked Critical keeps it. ## "I placed a message but the person says it isn't on their shift" Check four things in order: (1) the person is in the audience — a placement follows the message's recipient snapshot, so someone added to a group after you sent it is not in it; (2) the shift falls inside the placement's **From / Until** window and, if you narrowed to sites, at one of those sites (a region includes every site under it); (3) the slot is switched on under **Settings → Modules → Placement slots**, and the slot's app is turned on for the organisation; (4) they have not already dismissed it — Dismiss is per person and permanent for that message. A broadcast's page shows **Placed on** with each place, its dates and how many people have seen it there; a post's page lists its current places under **Where people see it**, with **End now**, for anyone who may end them. ## "The approval workflow isn't blocking my post from publishing" Admins always bypass approval workflows — an admin can publish without workflow approval. If you want admins to go through the workflow, that is not currently supported. Also confirm the workflow is set to **Active** and that its **Applies to** checkboxes cover what you're testing (posts, questions, polls, announcements, must-reads, broadcasts, in-context messages, newsletter issues and emergency alerts are each separate). ## "A triggered communication didn't fire for some employees" Triggered communications are suppressed in four situations: the trigger is disabled, the per-trigger throttle has not elapsed since the last firing for that recipient, the current time falls inside the trigger's quiet hours, or the firing time falls inside a PTO blackout period and blackout respect is on. Each firing records a status — check the trigger's firing history to see the suppression reason. ## "The Experts tab is empty even though people are answering questions" The topic cards on the **Experts** page list only the people an admin adds to each topic there — answering questions never adds anyone to them. To staff a topic, open it on the Experts page and add people; admins also see **Topics that need experts** at the top of the page (topics people posted about in the last 30 days with no expert, or only one on a busy topic), each with an **Add expert** button. Turning on **Find experts automatically** in settings also scores contributors weekly: the people it finds appear under **Top experts** beside the Feed and, while **Send new questions to experts** is on, receive routed questions. Admins see them on the Experts page under **Experts added automatically**, where **Remove** takes someone off a topic for good (they are not added back the next week) and **Undo** reverses it. Allow one weekly cycle after turning it on. **Send new questions to experts** uses the experts you add even when automatic scoring is off. ## "A scheduled newsletter issue didn't send" If a scheduled issue's send time passes and it is not sent within 24 hours (due to a worker outage or transient failure), the issue is reverted to draft and the publication owner is notified. Check whether the issue landed back in draft status. Also confirm the issue's audience still resolves to at least one person with an email address — an email-only publication with no reachable recipients is refused. --- ## Licensing and limits ## Does Communications require a licence? Yes. Communications is a licensed marketplace app, disabled by default. An administrator enables it per tenant from Admin → Apps → All Apps. ## Are there limits I should know about? | What | Limit | |---|---| | Media attachments per post | 10 | | Image file size (JPEG, PNG, WebP, HEIC/HEIF) | 100 MB | | GIF file size | 100 MB | | Video file size (MP4, MOV, WebM) | 500 MB | | Document file size (PDF, Word, Excel, PowerPoint, CSV, plain text) | 50 MB | | Post edit window | Any time, until people acknowledge the post | | Comment edit window | 15 minutes (fixed) | | Poll duration | 1 hour to 30 days (or never auto-close) | | Reaction palette | 2–12 active emojis from a 14-emoji catalog | | Voice recording length | 1, 2, 3, or 5 minutes (default 3) | | Brand Voice training samples | 3–10 samples, 50–5,000 words each, minimum 300 words total | | Newsletter block types | 6 static (text, image, divider, hero, callout, button) + 8 dynamic | | Must-Read default due date (when **Due by** is blank) | 7, 14, 30, 60, or 90 days (default 30) | | Must-Read "keep asking" after the due date | 0, 3, 7, or 14 days (7 preselected) | | Broadcast **Acknowledge by** | Within 30 days of sending | | On-shift audience, **Next hours** window | 1–24 hours (default 4) | | Broadcast reminder frequency | Every 2, 4, 8, 24, or 48 hours (default 24) | | Broadcast max reminders | 0–10 (default 3) | | Close comments automatically | 7, 14, 30, 60, or 90 days after the post is published (default 30, off by default) | | Broadcast auto-archive | 1, 2, 4, 8, or 12 weeks (default 1) | | Weekly notification limit | 3, 4, 5, 7, or 10 notifications per person, Monday to Sunday (default 5; the limit is off by default) | --- ## More help - [Communications Overview](/help/articles/communications_app_overview) - Ask AI — the assistant answers Communications questions from these articles. **Keywords:** faq, communications, news feed, broadcast, must-read, due date, overdue, on shift, acknowledgement, newsletter, audience, approval workflow, break-through, poll, brand voice, comms grader, permissions, not showing, reminder, communications-hub --- # Communications Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-20 What the Communications app does, how to stand it up, and the settings an admin configures — the unified feed, the four message types (Post, Announcement, Must-read, Broadcast), where people see a message beyond News and Inbox, newsletters, campaigns, acknowledgement tracking, and the Planning/Compose/Measure faces. # Communications ## 1. What it is Communications is the company-wide feed and internal-communications platform. Employees browse a single feed of posts, announcements, and must-reads; communicators plan, draft, and measure everything from the same app — including newsletters and Broadcasts that also go out by email, push, and SMS or voice call where your company allows them. - **Enablement:** requires a licence. An admin enables it from Admin → Apps → All Apps; it is not turned on automatically. - **What it is not:** Communications does not manage emergency alerts — those are owned by Safety Hub, which shares the approval-workflow primitive but has its own severity model and escalation path. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Communications**, and enable it. 2. Decide **who can post Announcements and Must-Reads**. Go to **Settings → General** and set **Who can post Announcements & Must-Reads** (default: **Admins and Leadership**). This one setting governs both types — choosing **Off** removes both from the composer for everyone, including admins. 3. If you need **Broadcasts** (messages that also go out by email — and SMS or voice call where your company allows them), give the communicators who should send them the **Broadcasts → Create** permission, or make them Communications app admins or contributors. The Broadcast type appears in Compose only for people who may send one. 4. Make communicators who should manage newsletters, campaigns, audiences, approval workflows, and settings — without being full company admins — **Communications app admins**, under **Apps Marketplace › Communications › Admins & Contributors**. 5. **Newsletters** are on by default. To hide them, turn off **Newsletters** under **Settings → Modules**. 6. Confirm by opening the app as a non-admin employee. They should see the feed's All, Unread, Must-read and Pinned tabs and a working Compose button. **If someone can't find Broadcast:** it needs both the app entitlement *and* the Broadcasts create permission (or a Communications app admin or contributor role). Without it, a person who can post announcements and must-reads does not get the Broadcast type — Compose says why under its **Type** card ("Broadcast isn't available to you — it needs permission to create broadcasts"). ## 3. How it fits together **Four message types.** Compose is one page with a **Type** card — each type asks a little more of the people who get it. This is the central design concept: - **Post** — in the feed. People see it the next time they open the app; it interrupts no one. Ranked under announcements. - **Announcement** — notifies right away, in the app and on phones. Ranked above posts. - **Must-read** — people acknowledge by a due date. Creates an audit record per person. The due date defaults to 30 days after sending; automated reminders go to people who haven't acknowledged 24 and 48 hours after it is published, and after 72 hours (by default) their managers are told how many of their team still haven't. - **Broadcast** — reaches people who aren't in the app. It notifies in the app and by push, adds email (your company's default channel) — and SMS or voice call where your company allows them — and is also posted to News for the same people. It asks people to acknowledge unless you untick **Require acknowledgment**. Broadcast has its own page in Compose (channels, what each channel says, SMS cost); picking it carries over what you have written. This is what was formerly the standalone Broadcasts app. Announcement and Must-read share the same permission gate (the **Who can post Announcements & Must-Reads** setting). Broadcast is a separate permission (Broadcasts create, or a Communications app admin or contributor role). This lets you grant "may announce but may not broadcast" — a common configuration. **Where people see it.** Every type lands in **News and Inbox**. On the composer's **Where people see it** card an author can also book the message into extra *places* — **slots** on screens people already use. Each slot comes with its own rules: one message at a time on it for a person, tied to the object on that screen where there is one (this shift's date and site, this open punch, this person's enrollment window), dismissible by the reader, and always time-boxed (7 days at most on Home, 90 days for the others). The places shipped today: | Place | App | Where the reader sees it | |---|---|---| | Top of Home | Home | Across the top of Home for the people it reaches — one message at a time | | Store home | Home | Pinned on one store's home, when the message goes to a single store the author manages (needs the Home briefing turned on) | | Shift detail | Shifts & Scheduling | On the shift they are about to work, below the shift summary | | Shift card | Shifts & Scheduling | A one-line marker on the shift in their Shifts list (off by default — an admin switches it on) | | After clock-in | Time & Attendance | On the Time & Attendance screen while they are clocked in | | Benefits overview | Benefits | On their Benefits page, beside the enrollment window | A Post or Announcement can **Skip News and Inbox** and show only in its places. A must-read, a Critical broadcast, or any message that asks for acknowledgement always reaches News and Inbox as well — a place only adds to that. **Three communicator faces.** Beyond the employee feed, Communications provides three admin/communicator surfaces: - **Planning** — **Ideas** (topics you might send; nothing there is scheduled) and the **Plan** page (what is going out, and when), with three views: **Month** and **Week** show every scheduled comm across types, and **List** is the plan itself, one year per plan. A summary line says how much is planned, written and still needs content, and which weeks have nothing going out. Items with no date wait in **Not dated yet**, and an admin can drag one onto a day. **AI suggest** proposes topics on either page; keep each one as a plan item or an idea. - **Compose** — the unified composer, an AI Writer, a Comms Grader, and newsletter authoring with a block-based editor. - **Measure** — cross-channel analytics: reach, read-through, and acknowledgement tracking on a single ledger. Pick any must-read or broadcast and see an audit-grade roster (acknowledged vs. pending) with segment-level breakdowns and a compliance CSV export. A **Placements** table lists every placed message with **Shown** (people who saw the card on the surface — distinct people, never page loads), Opened, Dismissed, Acknowledged and the median time to acknowledge. **Acknowledgements.** Must-reads and broadcasts share a single acknowledgement ledger. Once a person acknowledges, nobody can edit or delete the record in the app — it is an audit row. It is removed only by a privacy erasure request for someone who has left, or, for a broadcast, seven years after the broadcast is archived. The Measure face reports on both types identically, so you track one outstanding list instead of reconciling two systems. **Audiences.** A shared audience primitive that targets all delivery — feed posts, broadcasts, and newsletters. Audiences compose existing recipient groups with set operations (union, intersection, or "everyone"). Once defined, the same audience is reusable across every comm type. **Content hierarchy.** The feed is organized into **All**, **Unread**, **Must-read** and **Pinned** tabs, so posts that need action are not lost among everyday ones. **Mark all as read** on the Feed clears every unread post at once, except must-reads still waiting for your acknowledgement. With **Organize the feed into tabs** off, the feed is one list, newest first, with featured posts on top. Personalisation (following a topic) only changes *when* a post surfaces, never *whether* it does. **Reactions.** Reactions are drawn as the same icons everywhere. In **Settings → Active reaction palette** an admin chooses which reactions people can give, from 21: Like, Love, Celebrate, Wow, Sad, Angry, Support, Insightful, Applause, Haha, Taking a look, Rocket, 100, Fire and Star, plus six action reactions (Acknowledged, Need clarification, Concern, Disagree, Needs discussion, Escalate) that also feed Signals on the feed. The choice applies to every app with reactions — the feed, Workspace, chat, Messages, Broadcast, Recognition, Wikis, Sites and the rest — and all 21 are offered until an admin narrows it. A reaction someone already gave stays, and stays theirs to remove. ## 4. Running it ### Featuring a time-sensitive notice Open a published post's **Post actions → Feature notice** to choose its start, end, and order among featured notices. An optional audience narrows the feature to people who already have access to the post. Use **Preview audience** before saving. Admins, Communications app-admins, and authorized communicators can manage features. During its window, the notice leads All Posts and carries a **Featured** label with its expiry on desktop and mobile. On the mobile landing page and in Home's News Feed card, features lead within their existing sections. **Stop featuring** ends the placement early; unpublishing the post also ends it. Personal pins and acknowledgment requirements stay independent, and featuring sends no extra notification. ### Sending a broadcast 1. Open **Compose** and pick **Broadcast** under **Type**. It opens the Broadcast page and keeps what you have written. 2. Write the title and message. **Goes to** shows the channels: in-app always goes, and push too unless your company has switched it off; the rest start from your company's **Default Channels** (email unless an admin changed it). Use **Change channels** to turn email, SMS or voice call on or off. Anyone can turn a channel off; adding SMS or voice is for the people your company allows (by default admins and Communications app admins), and only where the company has that channel on. 3. **Require acknowledgment** is ticked by default — it adds the compliance roster and automatic reminders. Optionally set **Acknowledge by** (within 30 days of sending) and, where it is offered, tick **Auto-widen channels**, which adds a text with every reminder from the 2nd and a voice call with every reminder from the 3rd, on channels the broadcast uses — texts to people who haven't turned texts off or replied STOP, calls to people who take calls (everyone, on a Critical broadcast). 4. Tick **Critical — bypass quiet hours** only for emergencies (offered to the same people who may add SMS or voice, or on a template marked Critical). It reaches everyone right away, even in their quiet hours and past their notification settings — except texts to anyone who turned texts off, replied STOP, or whose number can't receive texts. 5. Choose **Delivery**: **Send to everyone immediately**, **Only people currently on shift**, or **Defer off-shift people to their next shift** (when their next shift starts within 24 hours; anyone else gets it now). 6. Select the audience, choose **Now** or **Schedule for later**, and press **Send broadcast** (**Submit for approval** when an approval workflow covers broadcasts). **Send a test to me** sends you a copy first. 7. Track delivery and acknowledgement from **Measure** or from the broadcast's page. A broadcast scheduled for later can repeat (every day, every weekday, every week or every month). Like every type, it can also be booked into extra places on the **Where people see it** card — see below. ### Choosing where people see it Every type has a **Where people see it** card. **News and Inbox** are always there: everyone in your audience finds the message in them. Below that, tick any extra place your company has switched on: 1. **Top of Home** — across the top of Home for your audience, between the **From** and **Until** you set (7 days at most). Only one message can be there at a time; if your dates overlap another message's, the card says when yours can start. 2. **Store home** — offered when everyone the message reaches works at one store you manage. Pick the day it runs **Until**; a newer pin for the same store replaces it. 3. **Shift detail**, **Shift card**, **After clock-in** and **Benefits overview** — set the window with **From** / **Until** (90 days at most; it always ends). For a shift or clock-in place you can open **Only at specific sites** (a region includes every site under it). For Benefits, choose whether it shows only while an enrollment window is open for the person. 4. **Break-room screens** (Digital Signage, where your company has screens) — a post can go there only when it is for everyone in the business; a broadcast can pick specific sites. To show a Post or Announcement **only** in those places, tick **Skip News and Inbox**: no one gets a notification, and each place takes it down on the Until date you set for it. Break-room screens have no Until date — they keep it in rotation for up to 14 days after it is published. A must-read can't skip News and Inbox — people have to confirm it. Readers who are in the audience and whose screen qualifies see the card; anyone else sees nothing. Dismiss hides it for that person. When the message asks for acknowledgement the card offers **Got it — acknowledge** instead, which takes it down and writes the usual acknowledgement record. On a sent message's page, **Where people see it** lists its current places with **End now**, for anyone allowed to end them. ### Publishing a newsletter 1. Go to **Newsletters** and create a **Publication** (the recurring series). Assign an owner, an audience, and optionally a slug for a public archive page. 2. Create an **Issue** (a single edition). The block editor supports six static block types (Text, Image, Divider, Hero banner, Callout, Button) and eight dynamic block types that pull live data from other apps — such as recent recognitions, new hires, open shifts, or upcoming events. 3. Preview, then **Send** or **Schedule**. Dynamic blocks are frozen at send time so every recipient sees the same snapshot. 4. Newsletter issues can optionally generate an AI podcast (a spoken-audio version) and cross-post to LinkedIn. ### Managing campaigns A campaign is a multi-touch wrapper that groups comms items (feed posts, broadcasts, newsletter issues) under a shared goal. Set KPI targets (opens, clicks, acknowledgements) and track actuals from the campaign's detail page. ### Reviewing approvals When approval workflows are enabled, communicators submit content for review before publishing. Reviewers see a pending queue under **Operate → Approvals**. A workflow can cover any of nine kinds of content: posts, questions and polls that employees write; announcements and must-reads; broadcasts and in-context messages; newsletter issues; and emergency alerts. Each workflow defines one or more approval steps with a role requirement. Admins always bypass approval gates. Emergency alerts are never held: an alert a workflow covers sends at once, and the workflow's reviewers are told afterwards that it went out without approval. ### Using the Idea Bank Ideas capture communication topics before they are scheduled. An idea can be promoted to a campaign or a scheduled comm. The AI Planning Assistant can suggest ideas, tracked with an **AI suggested** badge so you can measure how many AI ideas actually ship. ## 5. Settings Settings are under the app's **Settings** pages, grouped into sections. Key settings with real effects: ### Content & Composer | Setting | Default | What it changes | |---|---|---| | Organize the feed into tabs | On | Shows All, Unread, Must-read and Pinned tabs. Off shows one list, newest first, with featured posts on top | | What people can post › Posts | On | Offers the everyday post when someone writes a feed post. Also needed to write from a phone browser | | What people can post › Questions | On | Offers the Question. A reply can be marked as the correct answer while **Mark as correct answer** is on | | What people can post › Polls | On | Offers the Poll. Announcements and must-reads are never affected by these three | | Who can post to Everyone | **Admins and Leadership** | Who can address the entire company | | Who can post Announcements & Must-Reads | **Admins and Leadership** | Governs both types. **Off** removes both from the composer for everyone | | Must-Read default due date (days after sending) | 30 days | The due date a Must-Read gets when it is sent without one. From Compose, the post then keeps asking, marked overdue, for the days chosen under **After the due date** (7 unless the author changes it); sent any other way, it stops asking at the due date | | Automated acknowledgement reminders | On | Sends reminders to people who haven't acknowledged a must-read | | Escalate unacknowledged Must-Reads to managers | On | After a configurable window, notifies each pending employee's manager | | Allow editing posts, polls, questions & comments | On | Whether authors and Communications admins can edit a published post (any time, until people acknowledge it), and authors their comments (for 15 minutes) | | Allow new comments | On | Off keeps existing comments visible but stops new ones | ### AI Features | Setting | Default | What it changes | |---|---|---| | Writing help in the composer | On | Suggests clearer wording for posts and comments, in a chosen tone, for the author to accept or reject; also writes alt text for pictures | | Tag posts with topics automatically | Off | Classifies published posts and assigns topics automatically | | Suggest past answers to new questions | Off | Surfaces previously verified answers on new Question posts | | Send new questions to experts | Off | Notifies up to 3 subject-matter experts on the topic 30 minutes after a Question is posted. Only questions with a topic are sent, and none once a suggested answer was accepted or an answer was marked correct | | Summarize long discussions | Off | Generates a summary card at the bottom of long threads | | Translate posts for readers | Off | Lets employees read a post in their own language | | Spot signals in posts and comments | Off | Classifies posts into Risk, Issue, Idea, Question, Decision, Action Item, and Sentiment signals | ### Modules (Planning/Compose/Measure toggles) | Setting | Default | What it changes | |---|---|---| | Calendar | On | Shows the Plan page's Month and Week views — everything going out | | Ideas | On | Shows Ideas, the topics you might send | | Content Plan | On | Shows the Plan page's List view — what you have committed to say, and when | | Compose | On | Shows the Compose button | | AI Writer | On | Shows the AI Writer drafting surface | | Grader | On | Shows the readability and tone grader | | Publications (Newsletters) | On | Gates the entire newsletter subsystem | | Campaigns | On | Shows the Campaigns section | | Approval Workflows | **Off** | Gates the approval workflow subsystem | | Audiences | On | Shows the Audiences section | | Triggers | On for new organizations (organizations that already had Communications when triggers were introduced keep it off until an admin turns it on) | Gates event-driven automated triggers | | Analytics | On | Shows the cross-channel analytics face | ### Placement slots | Setting | Default | What it changes | |---|---|---| | Top of Home | On | Offers Top of Home on the composer's Where people see it card; one message at a time, 7 days at most | | Store home | On | Offers a store's home pin — once an admin turns on the Home briefing in the Dashboard Builder, where its "Today at your store" shows it | | Shift detail | On | Offers the shift-detail slot in the composer and renders placed cards on shift pages | | Shift card | **Off** | Offers the list-marker slot; a title-only line on qualifying shift cards in the Shifts list and the My Shifts calendar | | After clock-in | On | Offers the clock-in slot; renders on the Time & Attendance screen while clocked in | | Benefits overview | On | Offers the Benefits slot; renders on the Benefits page | A slot whose app is not turned on for the organisation stays unavailable however it is set here. Switching a slot off removes its option from the composer and stops rendering its cards immediately; placed messages are kept and come back when it is switched on again. ### Broadcast | Setting | Default | What it changes | |---|---|---| | Reminder frequency | Every 24 hours | How often people who haven't acknowledged a broadcast are reminded (every 2, 4, 8, 24 or 48 hours) | | Maximum reminders | 3 | How many reminders a broadcast sends (0–10; 0 turns them off) | | Enable AI authoring assists | On | The AI helpers in the composer — rewrite, translate, start from a brief, channel-native copy, hero image — and the "Describe it and let AI fill the form" bar | | Weekly AI-drafted check-in for silent tenants | Off | When no broadcast is published in a week, creates an AI-written check-in as a draft for your review. It never sends on its own | | Default Channels | Email | Channels pre-ticked when someone starts a broadcast, and used for broadcasts created without a channel choice (the mobile app, Ask AI). In-app and push always go; SMS and voice cost money per recipient | How many notifications each person gets in a week is no longer set here: it is the weekly notification limit under **Settings → General → Notifications**. ### Notifications & Media | Setting | Default | What it changes | |---|---|---| | How often people hear about Announcements | Realtime | How Announcements reach people who have not chosen their own notification setting: as each is published, or in an hourly or daily digest. Other posts and must-reads are not affected | | Limit how many notifications each person gets in a week | Off | Past the limit, messages still arrive in News and the person's Inbox but send no push, text or email. Authors see who is past it before they send | | Notifications per person, each week | 5 | The limit, counted Monday to Sunday across every Communications message that notifies (3, 4, 5, 7 or 10) | | Track email opens and clicks | Off | Records opens and clicks on Communications emails so Measure shows reach beyond the app | | Let people upload photos, videos and files | On | In posts and comments, and as a featured image. Off: people can still pick a picture from the image library | | Allow GIFs | Off | Search for a GIF or upload one in posts and comments. Needs uploads on | | Show link previews | On | When a post or a direct message has a link, show the page's title and picture under it | ## 6. More help - **Communications FAQ** — specific setup and operating questions, including acknowledgement tracking, content moderation, expert routing, and troubleshooting. - Ask AI — the assistant answers questions about Communications from these articles. **Keywords:** communications, news feed, broadcast, announcement, must-read, break-through, in context, placement, where people see it, top of home, skip news and inbox, shift detail, after clock-in, benefits overview, placement slots, newsletter, acknowledgement, campaign, approval workflow, comms hub, internal communications, company feed, audience, compose, plan, measure, signal extraction, subject-matter expert, SME, discussion summary, communications-hub --- # Company Profile **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-13 One agent-researched store of company facts — industry, certifications, differentiators, voice, culture — that every app reads instead of asking you again. How to research, review, confirm, and keep it fresh. # Company Profile ## 1. What it is The Company Profile is the platform's one canonical store of facts about your company — what you do, where you operate, what you're certified in, what makes you different, how you sound, and what your culture offers. Every app that needs company information reads it from here: AI agents ground their answers in it, RFP and bid responses cite it, recruiting pages describe your culture from it, generated emails and PDFs carry your identity from it. You confirm a fact once and stop being asked for it again — facts don't change because a different app needs them. - **Access:** requires the Administrator or Super Admin role, at **Admin → Organization → Company Profile** (directly above Business Profile in the sidebar). - **What it is not:** it is not the Business Profile. Business Profile holds operational settings — work days, timezone, compliance and legal details like the Federal EIN. Company Profile holds the descriptive facts about your company that apps and AI reuse. The two link to each other. - **Where Research is:** **Research my company** is in the **⋮ (More actions)** menu at the top right of the page. If it isn't there, either AI research isn't switched on for your account or a run is already open — in progress, or waiting for you under **Review N facts**. Editing facts by hand is always available regardless. The profile is organised into seven cards, named as they appear on the page: | Card | What it holds | |---|---| | **Identity** | Legal name, website, headquarters, founded, legal entity type, NAICS code, logo and brand colors | | **Size & reach** | Industry, specialty (field service trades), company size, headcount, geographies served, locations (kept in Admin → Locations) | | **What we offer** | What we do, positioning, products & services, markets served, capabilities | | **Proof & credentials** | Certifications, differentiators, customers you can name, proof points | | **How we sound** | Tone, wording to prefer and to avoid, your About us text | | **Culture** | Culture, values (kept in Recognition → Values), benefits, perks | | **How we sell** | Who you serve, target segments, standard terms, constraints you can't move | ## 2. Standing it up 1. Go to **Admin → Organization → Company Profile**. The page shows every facet, what's filled, what's confirmed, and what's still missing. 2. Open the **⋮** menu and choose **Research my company**. An AI agent gathers facts from three directions: what the platform already knows (your business record, locations, company values, past RFP answers), your public web presence (researched from your website domain), and anything your own documents and contracts state. Research runs in the background — the button shows "Researching…" until the results are ready. 3. If we don't have your website yet, type it in the box on the page next to the research button (or under Identity on **Edit**). Research works from your domain; a free email domain (gmail.com and similar) is deliberately not used. 4. When research finishes, a **Review N facts** button appears. Click it to open the review queue — every proposed fact with its source, a confidence level, and a citation. Confident, low-stakes facts arrive pre-ticked; high-stakes facts (certifications, named customers, legal details) and anything the agent was unsure about arrive unticked so you decide explicitly. 5. Tick what's right, untick what isn't, and save. Everything you save becomes a **Confirmed** fact — the strongest status a fact can have. Facts you leave unticked are set aside, not kept for later; run research again and the ones research found are proposed again (a fact someone told Ask AI is not). 6. Fill any remaining gaps by hand with **Edit**. Nothing requires research; typing a fact yourself confirms it just the same. **Try it with sample data first:** **Admin → Sample Data** can load a demonstration profile — a partly-confirmed fabrication company with a certification about to expire and a ready research draft waiting in the review queue — so you can walk the whole flow before touching real facts. Clearing sample data removes only the demonstration facts; anything real is untouched. ## 3. How it fits together **Provenance — every fact knows where it came from.** Each value carries a badge: **Confirmed** (a person typed it or kept it on Review), **From your platform** (found in your own platform data, with a reference to where), **Researched** (found on a public page, with the URL) or **Derived** (computed from other records, such as your business address). Demonstration facts read **Sample data**. A confirmed fact also says who confirmed it, so "why does it say that?" always has an answer. **Confirmed facts are locked.** Research never overwrites something a person confirmed. A new research run can *propose* a change to a confirmed fact, but it lands in the review queue unticked, beside what you have now, and takes effect only if you tick it. **The review queue is the anti-hallucination gate.** The agent cannot write directly to your profile, and it cannot propose a web fact without a source URL or an internal fact without a reference. Anything it can't cite is discarded before you ever see it. **Apps read, they don't re-ask.** AI agents across the platform receive a compact, confirmed-facts-first company context automatically. RFP Desk and Bid Fit draft from your proof and voice facets. Recruiting and candidate pages describe your culture. Generated emails, PDFs and portal pages carry your identity. When you correct a fact here, every one of those surfaces picks it up — there is no second copy to chase. **Sensitive fields stay home.** A small set of fields (for example, competitive weaknesses you record for internal honesty) never leave admin surfaces — they are excluded from AI prompts, generated documents and the capability statement. **Write-through to Business Profile.** A handful of facts live on both surfaces — website, founded, industry, company size, and **What we do** (shown as *About* on Business Profile). Editing them here updates the business record too, so the two pages can't drift apart. Your headquarters is separate from the business address on Business Profile: while AI research is switched on for your account, outgoing emails print the confirmed headquarters when there is one. **Per-app AI instructions.** When one app needs different *wording* — public-sector bids that must sound formal — don't fork the facts. RFP Desk carries its own short AI instructions (RFP Desk → Bid Profile) that style its drafts while reading the same profile underneath. ## 4. Running it ### Reviewing research results 1. Click **Review N facts** on the profile page (it appears whenever a research run is waiting). 2. Proposals are grouped by facet. Each shows the proposed value, its source and citation, and the agent's confidence. 3. Tick or untick, then save. Saved facts become Confirmed; anything left unticked is set aside, and the save message says how many. A later research run can propose research findings again. 4. If research found little ("your public pages didn't give us much to work with"), click **See what we tried** — the usual causes are a missing or wrong website, or a site that says little about the company. ### Re-running research Research can be re-run from the same **⋮** menu once nothing is waiting for review. Confirmed facts are never overwritten — new findings queue for review. Nothing re-runs research on its own: the page shows when the profile was last researched, so run it again when your website or offering changes. ### Keeping it fresh The profile is graded on three axes — how complete it is, how much of it a person has confirmed, and how current it is. Certifications carry expiry dates; anything expiring within 45 days is flagged on the page and in a **weekly email** to every admin, which also says when facts are waiting for review, so an expiring cert gets renewed in the profile before a bid or an agent cites it as current. Any admin can turn the email off for everyone with the **Weekly email** switch at the bottom of the page. The email is paused while AI research is off for your account. ### Asking a teammate When you don't know a fact, open **Ask a teammate** on its card and pick another admin; add a **Needed by** date if you want the task reminded and marked overdue. They get a task that links straight to the field, and the card shows the ask until the fact is filled in. Withdraw it with **Cancel** beside the ask. The task reaches them through the Tasks app; if Tasks isn't open to them, the page tells you so and gives you the link to send them yourself. ### Generating a capability statement **Capability statement (PDF)** is in the **⋮** menu — a one-page company summary built strictly from confirmed facts, suitable for attaching to bids and vendor registrations. It is available while AI research is switched on for your account, and unlocks once you confirm your legal name and what you do, plus one more fact for the body (headquarters, NAICS or a certification). Unconfirmed and sensitive facts never appear in it. ### Fixing a wrong fact Click **Edit**, correct the field, save. The correction is confirmed immediately and every consuming surface reads the new value. To confirm a researched value that is already right, tick **Confirm as is** under it and save. ## 5. Settings The Company Profile has one setting of its own — the weekly email. Everything else is a button on the page. | Control | Where | What it does | |---|---|---| | Research my company | Profile page, ⋮ menu | Starts a background research run; results queue for review | | Review N facts | Profile page | Opens the review queue for the waiting run | | Edit | Profile page | Direct editing of every card; saves are confirmed | | Ask a teammate | A card with missing facts | Sends another admin a task for one fact | | Capability statement (PDF) | Profile page, ⋮ menu | One-page summary of confirmed facts; needs AI research switched on, and unlocks once the profile is ready | | Weekly email | Bottom of the profile page | Turns the expiring-certification and waiting-facts email on or off for every admin | | Per-app AI instructions | RFP Desk → Bid Profile | Styles RFP Desk's AI drafts without changing shared facts | | Load / clear sample data | Admin → Sample Data | Demonstration profile and review draft; clearing removes only sample data | ## 6. More help - **Business Profile & General Settings** — the operational twin: work days, timezone, compliance and legal fields. - **Sample Data** — loading and clearing demonstration data across apps. - **AI Operations** — platform-wide AI controls, including pausing agents. **Keywords:** company profile, company research, ai research, company facts, certifications, differentiators, company voice, brand voice, company culture, capability statement, review queue, provenance, confirmed facts, freshness digest, expiring certification, per-app ai instructions, why does every app ask for my company information --- # Company Store **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How the Company Store works — catalog setup, points redemption, payment modes, approval holds, spend budgets, regions, fulfillment, and notifications. # Company Store ## 1. What it is Company Store lets employees spend recognition points — or, optionally, cash — on company merchandise, gift cards, experiences, and charitable donations. Admins curate the catalog, set approval thresholds, cap spend, and connect reward providers; employees browse, redeem, and track orders from the same app. - **Enablement:** Licensed app, disabled by default. An admin enables it from **Admin → Apps → All Apps** and must grant a licence before it is available to employees. - **What it is not:** Company Store does not issue recognition awards. Points flow in from the Recognition app (when the integration is on), from Levels & Badges level-up rewards, or from manual admin adjustments. To set up who can give recognition and for how much, use Recognition Connect. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Company Store**, and enable it with a licence. 2. Open **Company Store → Settings** and confirm **Store Open** is on (it defaults to on). Choose which payment modes to allow — **Points Redemption** is on by default; **Cash Purchases** and **Mixed Payments** are off. 3. Under **Catalog Categories**, choose which categories to offer. **Company Swag** and **Gift Cards** are on by default. **Experiences** and **Charitable Donations** are off until you enable them. 4. If you plan to offer gift cards through Tremendous or Tango Card, go to **Admin → Reward Providers** and connect the provider. Gift cards will not fulfill automatically until credentials are configured. Internal gift cards (no external provider) require manual fulfillment by an admin. 5. Go to **Admin → Manage Items** and add your first catalog items, or load sample data from **Settings** to explore the app before stocking real items. 6. If your workforce spans multiple countries, go to **Admin → Regions** and create a region per country. Items can then be scoped to a region, and each employee is auto-matched to one based on their work location or profile country. 7. To control company-funded spend, go to **Admin → Spend Budgets** and create budgets per department or manager team. Without a budget, redemptions are uncapped at the company level (employees are still limited by their own points balance and any monthly cap you set). 8. Confirm it works: as a non-admin employee, open **Company Store**. They should see the Dashboard with featured items, be able to browse the Catalog, and check their Points balance. **Silent-until-configured pairing:** gift-card items with an external provider type will not auto-fulfill until the matching provider integration is connected. The order is placed, points are deducted, and the item sits in Pending until an admin manually fulfills or retries it — with no error visible to the employee until the admin acts. ## 3. How it fits together **Items and categories** — Every item in the catalog belongs to one of four categories: **Swag**, **Gift Card**, **Experience**, or **Charitable**. Each category can be turned on or off independently in Settings. An item that belongs to a disabled category is hidden from the catalog. Items can be priced in points, cash, or both; at least one price is required. Items carry a status — **Active**, **Out of Stock**, **Discontinued**, **Draft**, or **Coming Soon** — and an item whose tracked inventory reaches zero is automatically moved to Out of Stock. When stock is added back, it returns to Active and employees who signed up for a back-in-stock notification are alerted. **Points balance vs. spend budgets** — These are two independent controls that are easy to confuse. An employee's **points balance** is what they own and can spend (earned through recognition or admin adjustments). A **spend budget** is a company-funded cap on how many points a department or manager's team can redeem in a given year — it does not add points to anyone's balance; it limits how much the company will let that group redeem. Redemptions draw down the most specific budget that applies (the employee's manager's budget first, then the department's). When both exist, a manager-level sub-allocation is carved out of the department envelope. An employee can still hold more points than the budget allows; they just cannot redeem past the budget until an admin tops it up. The budget warns its owner at 80% committed and again when a redemption is blocked. **Approval holds** — Redemptions above a configured point threshold are held for approval instead of being fulfilled immediately. There are two tiers: a **Manager Approval Threshold** routes the hold to the employee's direct manager (or to a designated Approver Group, such as a Rewards Committee), and an **Admin Approval Threshold** routes it to business administrators — only a business administrator can decide an admin-tier hold, so a Company Store app admin who is not one can see it but not approve it. The admin tier always takes precedence when both match. A velocity/fraud hold — triggered when an employee redeems too many times or too many points in a short window — always routes to admin approval, and the approver is told why it was held. A manager-tier hold from someone with no manager, or from the Approver Group's only member, goes to the business administrators too. Nobody decides their own hold while someone else can. Points are deducted and inventory is reserved at the moment the hold is created; if declined, both are refunded. **Regions** — An optional layer for multi-country workforces. Each region maps to a country and a currency. Items can be assigned to a region (or left global). Employees are auto-matched to a region by their primary work location's country, then their profile country, then the default region. Only one region per country is allowed within a business. **Fulfillment** — How an order gets to the employee depends on the item's provider and category. Gift cards with an external provider (Tremendous, Tango Card) are fulfilled automatically — the provider issues the card and the code or redemption link appears on the order. Print-on-demand swag (Printful) is submitted to the provider automatically. Managed swag (warehoused inventory fulfilled through the Managed Swag Fulfillment program) is routed to the operations desk. Internal items with no external provider are fulfilled manually by a store admin. Employees can track their order status and, for physical items, see carrier tracking links (UPS, FedEx, USPS, DHL). If an employee's physical order shipped wrong, they can request a return or exchange from the order page. **Cart** — Employees can add several items to a cart and check out once, as one order with one shipment. The cart takes company swag — print-on-demand items, managed-program items and items shipped from HQ inventory — but a cart holds items from one fulfillment route at a time, so print-on-demand and HQ-shipped items are ordered separately (the store says so when you try to mix them). Gift cards, charitable donations, engraved items and cash-only items are always checked out on their own. A cart holds up to **5 different items** and up to **5 of each**. Checkout accepts points, card, or points plus card (subject to the payment settings), the address and payment are entered once for the whole order, and every budget, approval and cap check is evaluated against the cart total. On the phone the cart checks out with points only; a shortfall points the employee to the desktop checkout to pay the difference by card. **Redeem now** on an item page places just that item, leaving the cart as it was, and **Order Again** on a finished order refills the cart from that order. Cancelling a cart order refunds the points and restocks every line. **Order requests** — From an order page an employee can message the store admins: **Question about my order**, **Request cancellation** (once the order is already with the provider and can no longer be cancelled directly), **Change shipping address** (before dispatch) or **Item arrived damaged or wrong** (after delivery). Store admins are notified in their Inbox and by email; cancellation requests appear as a queue on **Admin → Manage Orders**, everything else on the order's admin page. Approving a cancellation recalls the order at the provider where possible, cancels it and refunds the points; declines and replies reach the employee in their Inbox and by email and show on the order page. **Wishlists and restock alerts** — Employees can add items to a personal wishlist (saved until they remove it) or sign up for a back-in-stock notification on an out-of-stock item. The restock notification is one-shot: once the item comes back in stock the employee is notified and the watch is removed automatically. **Managed Swag Fulfillment** — An optional program (enabled under **Admin → Swag Fulfillment**) for warehoused company merchandise. When enabled, items marked as managed carry real inventory counts with a full audit ledger of every stock movement — restocks, redemptions, cycle counts, and damage adjustments. A configurable low-stock threshold (default 10 units) triggers an admin alert when stock crosses below it. Admins register inbound stock shipments; the central operations desk handles outbound shipping. **Recognition integration** — When enabled (on by default), points from recognition awards are automatically credited to the employee's Company Store balance. Turning this off disconnects the two: employees can still receive recognition, but it will not add store points. ## 4. Running it ### Managing the catalog Go to **Admin → Manage Items**. From here you can add, edit, or discontinue items. Each item requires a name, a category, and at least one price (points or cash). You can set inventory (leave blank for unlimited), assign a region, mark an item as **Featured** to show it on the store dashboard, add variant options (size, color), upload an image, and schedule a future publish date. When creating or updating an item, check **Announce to employees** to send a one-time notification that the item is now available. On a Draft or Coming Soon item with a publish time, the box instead announces it when the scheduled publish makes it live (if it is in stock and its category is on then). Items can also be imported from a connected reward provider's catalog (e.g. Tango Card). ### Reviewing and fulfilling orders Go to **Admin → Manage Orders** to see all orders. Filter by status to find orders that need attention. From an order's detail page, you can: - **Fulfill** a pending order manually (enter a tracking number and carrier, or a gift card code/link for internal cards). - **Cancel** an order — points and inventory are refunded automatically. - **Refund** a fulfilled order — points are refunded; for physical items, inventory is restored. Charitable orders cannot be refunded. - **Retry** a failed digital fulfillment (the button appears when a provider error is recorded). - **Reply to, decline or approve** the employee's requests about the order (questions, address changes, damage reports, cancellation requests). **Cancel & refund** on a cancellation request tries to recall the order at the provider first, then cancels and refunds; if the provider refuses, the order is still cancelled here and the refusal is shown so you know it may still be produced. Cash orders need a business administrator. For orders that included a cash or mixed payment, cancellation or refund automatically triggers a Stripe refund for the card portion. ### Adjusting employee balances Go to **Admin → User Balances** to see every employee's points balance, lifetime earned, and lifetime spent. You can adjust an individual balance (credit or debit points with a reason) or run a bulk adjustment. Store app admins are capped at the **App-admin Points Cap** (default 5,000 points per adjustment); larger adjustments require a business administrator. The same cap applies to an order an app admin places on an employee's behalf. The employee is notified of every admin adjustment. ### Approving held redemptions - **Manager approvals**: Managers (or members of the configured Approver Group) go to **Team → Approvals** and approve or decline each held order. Add a short reason when you decline — the employee sees it. On approval the order proceeds to fulfillment; on a decline the points and inventory are refunded and the employee is told it was not approved, and why. - **Admin approvals**: Admins review held orders from **Admin → Manage Orders**, filtered to the pending-approval status. ### Processing returns and exchanges When an employee requests a return or exchange on a fulfilled physical order, the request appears in the order's detail page. Each order supports one open request at a time. Physical items can be returned for a refund (points restored) or exchanged. Employees choose a reason — **Wrong size**, **Defective**, **Not as described**, **Changed mind**, or **Other**. Gift-card orders have a separate set of reasons for reporting issues — **Code not received**, **Code invalid**, **Wrong amount**, or **Other**. Store admins are notified of each new request. An admin approves or declines it; on approval, the corresponding refund is processed. ### Viewing team budgets (managers) Managers with direct reports see a **Team → Team Budget** tab showing their team's budget allocation for the current year: total allocation, amount spent, amount carved out for sub-allocations, and remaining balance. This is read-only — budgets are created and adjusted by admins under **Admin → Spend Budgets**. ### Assisted redemptions Go to **Admin → User Balances** and click **Redeem for employee** to place an order on behalf of an employee — useful for new-hire welcome kits or frontline workers without app access. The admin chooses the employee, the item, and provides a reason; the employee's own points are spent, and all the same rules (budget, approval threshold, inventory) apply. ### Tax reporting Business administrators (not store app admins) can access **Admin → Tax Reports** to review employees approaching or exceeding the tax-reporting threshold (default $600, matching the US IRS figure). Downloadable reports include annual summaries, detailed transactions, gift card reports, W-2 supplements, 1099-NEC data, P11D data, and threshold status. Reports containing SSN or home-address data require step-up identity verification before download. ## 5. Settings All settings are at **Company Store → Settings**. | Setting | Default | What it changes | |---|---|---| | **Store Open** | On | Master switch. Turned off, employees can't browse, redeem or buy, but can still see My Orders (and any gift-card codes on them). Admin pages and Settings stay available, and points don't expire while it is off. | | **Points Redemption** | On | Whether employees can redeem items with points. | | **Cash Purchases** | Off | Whether employees can buy items with a credit card via Stripe. | | **Mixed Payments** | Off | Whether employees can combine points and cash in one purchase. | | **Company Swag** (category) | On | Shows or hides the Swag category in the catalog. | | **Gift Cards** (category) | On | Shows or hides the Gift Cards category. | | **Experiences** (category) | Off | Shows or hides the Experiences category. | | **Charitable Donations** (category) | Off | Shows or hides the Charitable Donations category. | | **Points per Dollar** | 100 | Conversion rate used when mixing points and cash (100 points = $1). | | **Points Expiry** | 0 (never) | Months after earning before points expire. 0 means points never expire. | | **Monthly Redemption Cap** | 0 (no limit) | Maximum points an employee can redeem per calendar month. | | **Manager Approval Threshold** | 0 (off) | Redemptions at or above this point value are held for the employee's manager. | | **Admin Approval Threshold** | 0 (off) | Redemptions at or above this point value are held for admin approval. | | **Manager-tier Approver Group** | Direct manager | When set, manager-tier holds go to a designated group instead of each redeemer's org-chart manager. | | **App-admin Points Cap (grants and redemptions for others)** | 5,000 | Maximum points a store app admin can move for one employee in a single action — a balance adjustment, or an order placed on their behalf; larger actions require a business administrator. | | **Tax Reporting Threshold** | $600 | Annual taxable reward value at which an employee appears on admin Tax Reports. | | **Featured Items on Dashboard** | 6 | Number of featured catalog items shown on the store dashboard. | | **Velocity Window** | 24 hours | Rolling window for velocity/fraud controls. | | **Velocity Max Orders** | 0 (off) | Orders in the window that trigger a hold for admin review. | | **Velocity Max Points** | 0 (off) | Points redeemed in the window that trigger a hold. | | **Order Confirmation** | On | Notify employees when their order is placed. | | **Processing Updates** | On | Notify employees when an order starts being prepared (a physical order, a gift card being issued, or an experience being arranged). | | **Fulfillment Updates** | On | Notify employees when their order is fulfilled — including the notice that delivers a gift-card code. | | **Low Stock Alerts** | On | Notify store admins in the app when an item with a counted inventory falls to its Low Stock Alert number, and remind them weekly while it stays low. | | **Send store admin alerts to this group instead of the app admins** | Not set | When set, store admin alerts (new orders, low stock, low gift-card balance) go to this group instead of the Company Store app admins. Redemptions held for an admin's approval, and overdue ones, go to its business administrators. | | **Admin Order Alerts** | On | Notify store admins when a new order is placed. | | **Unspent Points Reminder** | Off | Remind employees with idle points at most once a month — in the app, and by email when they have an address. | | **Recognition Integration** | On | Automatically credit points when an employee receives a recognition award. | | **Company Store assistant (Ask AI)** | On | Lets people use Ask AI to check balances, browse and track orders and — after a confirmation — redeem, check out a cart, cancel or return orders; managers can approve or decline redemptions. | ## 6. More help - **Company Store FAQ** — specific setup and operating questions. - Ask AI — the assistant answers questions about Company Store from these articles. **Keywords:** company store, swag, gift cards, points redemption, recognition points, rewards catalog, merchandise, redeem points, store budget, charitable donation, experiences, fulfillment, company-store, company_store --- # Company Store FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Company Store — for the admin running it. # Company Store FAQ Answers to common setup and operating questions about Company Store. For what the app is and how to set it up from scratch, see the [Company Store Overview](/help/articles/company_store_app_overview). --- ## Setup ## Do I have to connect a reward provider before I can list items? No. Internal items (swag you fulfill manually, experience vouchers, charitable donations) work with no provider. You only need to connect **Tremendous** or **Tango Card** for digital gift cards, or **Printful** for print-on-demand swag. Until a provider is connected, gift-card items with an external provider type sit in Pending after checkout and must be fulfilled manually by an admin — no error is shown to the employee. ## Who can administer the store? Business administrators and anyone granted the **Company Store app-admin** role. Both can manage items, orders, balances, regions, budgets, and settings. Three exceptions: **Tax Reports** are restricted to business administrators only (app admins cannot access them), **cancelling or refunding an order that included a cash payment** also requires a business administrator, and **deciding an admin-tier or velocity hold** needs a business administrator. --- ## Permissions and access ## Why can't an employee see the store? Three things must all be true: the app must be **enabled with a licence** in Admin → Apps → All Apps, the **Store Open** toggle in Settings must be on, and the employee must pass the app's user-level visibility rules (audience scoping). If any one is missing, the employee is redirected away. With Store Open off, employees can still see My Orders (and any gift-card codes on them), and admins keep every Admin page and Settings — turning the store off is not a one-way door. ## Who can approve held redemptions? It depends on the tier. **Manager-tier holds** go to the employee's direct manager by default, or to the members of the **Approver Group** if one is configured in Settings (the group replaces the org-chart manager entirely — it does not supplement them). **Admin-tier holds** and velocity holds go to business administrators, who are the only people who can decide them; a manager-tier hold whose employee has no manager (or who is the Approver Group's only member) goes to them too. An administrator's own hold goes to another administrator when there is one. When both thresholds are met, the admin tier takes precedence. --- ## Points and balances ## How do recognition points get into the store? When **Recognition Integration** is on (the default), every recognition award is automatically credited to the recipient's store balance. The conversion uses the **Points per Dollar** rate (default 100): a $5 award becomes 500 store points. Peer-to-peer recognition points (from each employee's monthly giving allowance) credit 1:1 — the points value given is the points value received, with no dollar conversion. If a recognition is later revoked or expires, the corresponding points are reversed from the balance. ## Do points expire? Not by default. Points expiry is off, so balances never lapse unless you turn it on. In Settings, set **Points Expiry** to 1–60 months. After the configured window, unredeemed points age out on a first-in, first-out basis. Expiry pauses while the store or Points Redemption is switched off — nobody can spend points then — and switching it back on gives everyone 14 days' notice before anything expires. Points of someone who cannot open the store (it is limited to groups they are not in, or not yet published) are not expired either. When expiry is on, employees whose points will expire within 14 days receive a warning notification — and an email, when they have an address — repeated weekly until the points expire or are redeemed. Turning expiry on, or shortening it, never takes points that night: anything the new window reaches — including points that are already older than it — gets the same 14 days' warning first. A separate **Unspent Points Reminder** setting (off by default) reminds employees — with a notification in the app, and an email when they have an address — who hold points but haven't redeemed any in the last 30 days, at most once a month — and stops once their points have seen no activity for six months. ## What is the difference between an employee's points balance and a spend budget? A **points balance** is what the employee owns — earned through recognition or admin adjustments. A **spend budget** is a company-funded cap on how many points a department or manager's team can redeem in a given period. Budgets do not add points to anyone's balance; they limit how much that group can redeem. An employee can hold more points than the budget allows — they just cannot redeem past the remaining budget until an admin tops it up. Budget owners are warned when the budget reaches 80% committed. --- ## Payments ## What payment methods does the store support? The store supports **points-only** redemption (on by default), **cash purchases** via Stripe, and **mixed payments** combining points and cash. Cash and mixed payments are off by default and must be turned on in Settings. When enabled, Stripe accepts cards, digital wallets (Apple Pay, Google Pay), and one-click Stripe Link. No card is stored in the app — each cash checkout runs as a Stripe guest session. ## What happens when a cash or mixed order is cancelled or refunded? Points are refunded immediately. For the cash portion, a Stripe refund is triggered automatically for the amount Stripe actually captured. Only business administrators (not app admins) can cancel or refund orders that included a cash payment. --- ## Orders and fulfillment ## How does auto-fulfillment work? It depends on the item's provider. **Tremendous / Tango Card** gift cards are fulfilled automatically at checkout — the provider issues the card and the redemption link appears on the order. **Printful** print-on-demand swag is submitted to Printful automatically; the order moves to Processing once accepted. **Managed** swag (warehoused inventory) is routed to the operations desk. **Internal** items with no external provider must be fulfilled manually by a store admin from the order detail page. If auto-fulfillment fails, the order stays in Pending with an error recorded, store admins are notified, and a **Retry** button appears on the order. ## Why can't I add a gift card or charitable item to the cart? The cart is for company swag that ships as one order. Gift cards, charitable donations, engraved items and cash-only items check out on their own from the item page. A cart also holds items from one fulfillment route at a time — print-on-demand (Printful) items and items shipped from HQ inventory can't share a cart, and the store says "check out your current cart first, or replace it" when you try. The cart holds up to **5 different items** and **5 of each**. ## Why does "Add to cart" say the item isn't available, or send me to the item page? On the catalog the **Add** pill only appears on items that need no choices; an item with sizes or colors (or a price that depends on them) is added from its own page, after you pick the options. If an item is out of stock, in a switched-off category, or not offered in your region, the store refuses the add with the reason. ## Can I pay for a cart by card? Yes, when card payments (and, for a split, mixed payments) are switched on in Settings: the checkout offers **Pay with points**, **Pay by card** and **Points + card**, and preselects the split when the points balance falls short. The whole cart is one Stripe charge. On the phone the cart checks out with points only — a shortfall links to the desktop checkout to pay the difference by card. ## How does "Redeem now" differ from checking out the cart? **Redeem now** on an item page places that one item straight away and leaves whatever is in the cart untouched. The checkout page says so ("Redeeming this item on its own — the N items stay in your cart") and offers **Add to cart and check out together** instead. ## How does an employee cancel an order? While the order hasn't been sent to the provider, the order page has **Cancel order** — the points go straight back and stock is restored. Once the order is with the provider (Printful, a gift card provider), the button becomes **Request cancellation**: the request goes to the store admins, who can try to recall it at the provider and refund the points. Fulfilled orders can't be cancelled; they can be returned or exchanged instead. ## Where do employees' questions about an order go? **Contact store admin** / **Ask a question** on the order page sends a message to the Company Store admins (Inbox and email). Replies land in the employee's Inbox and by email, and also show on their order page under **Your requests**. Cancellation requests appear as a queue at the top of **Admin → Manage Orders**; questions, address changes and damage reports appear on the order's admin page with a reply box. ## "Cancel & refund" says the provider refused — was the order cancelled? Yes, here. Approving a cancellation request first tries to recall the order at the provider; if the provider refuses (it is already printing or shipped), the order is still cancelled and refunded in the store and the refusal is shown so you know it may still be produced and billed to your provider account. Decide with that in mind — you can **Decline** the request instead and reply to the employee. ## What does "Order Again" do? On a fulfilled or cancelled order, **Order Again** puts every line of that order back into the cart (skipping anything that can no longer be ordered, and saying which) and opens the cart. A single gift card or donation reorders through its own checkout. ## Can a charitable order be refunded? No. Charitable orders (donations) are excluded from refunds. The Refund action is not available on them. They are also excluded from multi-item carts and from bulk fulfillment. ## How do returns and exchanges work? An employee can request a return (refund) or exchange from their fulfilled order page by choosing a reason — **Wrong size**, **Defective**, **Not as described**, **Changed mind**, or **Other**. Gift-card issues have their own reasons: **Code not received**, **Code invalid**, **Wrong amount**, or **Other**. Each order supports one open request at a time. Store admins are notified of each new request. An admin approves or declines it; on approval the corresponding points (or card payment) are refunded for returns, or the exchange is processed. --- ## When something looks wrong ## "My employee placed an order but the gift card never arrived" If the gift card's provider integration (Tremendous or Tango Card) was not connected or the provider returned an error, the order is parked in Pending and an admin notification is sent. Check **Admin → Manage Orders**, find the order, and look for a fulfillment error. If the provider is now connected, use the **Retry** button. If it is an internal gift card (no external provider), you must manually supply the card code or link from the order detail page. ## "An order has been sitting in Awaiting Approval for days" If a held order's approver has not acted within 2 days, the assigned approver is reminded. If the order is still pending after 5 days, the business administrators who can decide it are pulled in as an escalation (for a manager-tier hold — an admin-tier hold is already with them). Reminders repeat every 2 days. Points remain deducted and inventory reserved while the hold is open; declining the order refunds both. ## "The budget is exhausted but we still have allocation left" Check whether manager-level sub-allocations are carved out of the department budget. The sub-allocation reserves that portion for the manager's team, reducing the department's available balance even if the sub-allocation has not been fully spent. Also confirm that the budget has not crossed the 80% warning — the warning fires once on the crossing and does not repeat, so it may have been missed. --- ## Regions and tax ## How does the store match an employee to a region? In order: (1) the employee's **primary work location's country**, then (2) their **profile country**, then (3) the **default region** (the region marked as default in Admin → Regions). An employee can also manually switch to a different region from the storefront. Only one region per country is allowed. ## Who can access tax reports, and why do downloads require re-verification? Only **business administrators** — store app admins cannot access the Tax Reports tab. Because the reports contain personally identifiable information (SSN, home addresses), downloads require recent identity re-verification (a step-up prompt) before the file is released. The default tax-reporting threshold is **$600** (matching the US IRS figure) and is configurable in Settings. --- ## Limits and specs ## What are the configurable limits I should know about? | Setting | Default | Allowed range | |---|---|---| | Points per Dollar | 100 | 1–1,000 | | Points Expiry (months) | 0 (never) | 0–60 | | Monthly Redemption Cap | 0 (no limit) | 0 or any positive number | | Manager Approval Threshold | 0 (off) | 0 or any positive number | | Admin Approval Threshold | 0 (off) | 0 or any positive number | | App-admin Points Cap (grants and redemptions for others) | 5,000 points | 0 (no limit for app admins) or any positive number | | Tax Reporting Threshold | $600 | Any amount greater than $0 | | Featured Items on Dashboard | 6 | 1–24 | | Velocity Window | 24 hours | 1–720 hours | | Velocity Max Orders | 0 (off) | 0 or any positive number | | Velocity Max Points | 0 (off) | 0 or any positive number | | Cart | 5 different items, 5 units per line | Not configurable | | Order request message | 2,000 characters | Not configurable | | Bulk Balance Adjustment | 200 users per batch | Not configurable | Business administrators bypass the app-admin balance adjustment cap entirely. --- ## More help - [Company Store Overview](/help/articles/company_store_app_overview) - Ask AI — the assistant answers Company Store questions from these articles. **Keywords:** faq, company store, points balance, redemption, gift cards, swag, fulfillment, budget, approval threshold, points expiry, regions, tax reporting, Stripe, recognition points, not showing, permissions, cart, cancellation request, order again, company-store, company_store --- # Compensation Management App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-18 How to set up and run Compensation Management — pay records, approval workflows, pay grades, policies, and analytics. # Compensation Management ## 1. What it is Compensation Management is where you maintain every employee's pay record, route compensation changes through an approval workflow, and track the full history of who changed what. It covers salary, hourly, commission, and contract compensation types. - **Enablement:** requires a license and is disabled by default. An admin enables it from **Admin → Apps → All Apps**. - **What it is not:** this app does not run payroll. For payroll integration and paychecks, see **Payroll Connect**. For merit-cycle planning and performance-linked compensation recommendations, see **Employee Performance Management** — EPMS has its own approval chain that writes pay directly; its approvals do not appear in this app's Approvals queue. ## 2. Standing it up 1. **Enable the app.** Go to **Admin → Apps → All Apps**, find **Compensation Management**, and enable it. The app requires a license. 2. **Set up pay grades** (optional but recommended). Go to **Admin → Compensation Management → Pay Grades**. Create your compensation bands — each grade needs a code, name, minimum, midpoint, and maximum salary. If you don't have grades yet, click **Start from a standard ladder** to generate a standard 11-grade ladder you can edit. Pay grades power comp-ratio analytics; without them, those charts are disabled. 3. **Assign employees to pay grades.** Go to **Admin → Compensation Management → Grade Assignments** to assign employees to their bands in bulk. 4. **Configure policies.** Go to **Admin → Compensation Management → Policies** to set who can see what: - Whether employees can view their own compensation - Whether employees can submit compensation change requests (and how often) - What managers see: **Full salary amounts**, **Salary ranges only**, or **No compensation details** - Who can view team compensation (a capability picker: **App admins only**, **Managers**, or **Specific people/groups**) 5. **Configure advanced settings.** Go to **Admin → Compensation Management → Advanced Settings** to set approval thresholds, default currency, default pay frequency, and auto-approval rules. 6. **Verify it works.** Go to **Admin → Compensation Management** — you should see the employee compensation list. Employees see their own pay at **My Compensation** in the app sidebar. Pay grades and policies are independent — enabling one does not require the other. But an employee assigned to a pay grade without pay data will show no comp-ratio, and a manager with the team compensation toggle on but no reports will see an empty list. ## 3. How it fits together **Compensation types** — every employee has exactly one: **Annual Salary**, **Hourly Rate**, **Commission-Based**, or **Contract Rate**. The type determines which amount field applies. The default for new employees is **Hourly Rate** with a currency of **USD** and a pay frequency of **Weekly**. Salary employees store an annual amount; hourly employees store a per-hour rate (converted to annual at 2,080 hours/year for analytics and comp-ratio calculations). **Pay grades** — a band with a minimum, midpoint, and maximum salary. Grades are organized by level and optionally by job family. An employee assigned to a grade gets a comp-ratio (their current salary ÷ the grade midpoint), which the analytics page plots across five bands: **Below Range** (under 80%), **Below Market** (80–95%), **At Market** (95–105%), **Above Market** (105–120%), and **Above Range** (over 120%). A grade still in use cannot be deleted — move its employees (current or former), step schedules and job titles to another grade first. **Approval workflow** — any compensation change can be routed through approval before it takes effect. The flow works three ways depending on how the change was initiated: - **Manual edit** by an admin: applied immediately, no approval required. - **Bulk update**: the initiator chooses an approval mode — apply immediately (admin override), route each change through approval, or submit them all together (approvers are notified once, then decide each employee's change individually). - **CSV import**: the same choice, plus **Auto-Approve Small Changes** (available once auto-approval is on in Advanced Settings), which applies raises within the configured thresholds and routes the rest. Auto-approval applies only to CSV imports run in that mode — never to bulk updates or employee requests. - **Employee request** (when enabled in Policies): the employee submits a request, it goes to an auto-assigned approver (an admin who is neither the requester nor the beneficiary), and the approver approves or rejects it. When a change is approved, it is applied to the employee's record and a history entry is created — unless the employee's pay changed after the request was filed, they left, the request sets pay for a pay type they are not on, or their pay already matched it. Then the approval is recorded as **Approved — not applied**, their pay is unchanged, and an employee who asked about their own pay may file again. The requester and the employee are notified when your notification settings allow. *Example: you import a CSV with raises for 25 employees, choosing auto-approve. The system checks each change against the auto-approval thresholds (say, 5% and $2,000). A $1,500 raise on a $50,000 salary (3%) passes both — applied immediately. A $6,000 raise on the same salary (12%) exceeds both — routed to the approval queue for manual review.* **Sensitive data protection** — compensation pages are behind a step-up verification gate. Viewing any page that shows per-employee pay requires the admin to re-verify their identity (the session stays elevated for 15 minutes). Every page view is audited: who viewed whose compensation, when. **Manager visibility** — when the team compensation toggle is on, managers see their direct reports' pay, scoped by the visibility level set in Policies: - **Full salary amounts** — exact numbers - **Salary ranges only** — amounts shown in $10,000 bands (salary) or $5 bands (hourly) - **No compensation details** — hidden entirely Managers never see company-wide data. Pay grade administration, grade assignments, CSV import, and sample data are restricted to the function tier (admins, super admins, and app admins). HR staff get access through the Admin role, an app-admin grant, or the Policies page's **Specific people** option. ## 4. Running it ### Reviewing and approving compensation changes 1. Go to **Compensation Management → Approvals**. The dashboard shows pending, approved, and rejected counts. 2. Click a pending request to review the current vs. proposed values, the justification, and the effective date. 3. Click **Approve** (with optional notes) or **Reject** (a reason is required). 4. For multiple requests, use **Bulk Review** — select requests and approve or reject them in batch. A pending request waiting more than 7 days is counted under **Waiting over 7 days** on the Approvals page and shows how long it has waited. A request whose effective date is within the next 30 days carries a **Soon** badge; one whose date has already passed carries **Retroactive**. ### Updating compensation in bulk 1. Go to **Admin → Compensation Management**, select employees (or use **Select All Filtered**). 2. Click **Bulk Update**. Choose the update type — percentage increase, flat increase, or set a new value. 3. Choose the approval mode: apply immediately, route through individual approvals, or batch approval (sent together; each change is still decided on its own). ### Importing compensation data via CSV 1. Go to **Admin → Compensation Management → Import**. 2. Upload a CSV file (maximum 10 MB). The file must include an **Employee ID** column. Supported columns: Compensation Type, Annual Salary, Hourly Rate, Pay Frequency, Currency, Effective Date, Notes. 3. Choose how to handle duplicates (update existing or skip) and the approval mode. 4. The import matches employees by Employee ID, applies or routes each change, and reports the count. ### Exporting compensation data Go to **Admin → Compensation Management** and click **Export**. The CSV includes employee name, job title, compensation type, salary/rate, pay frequency, currency, effective date, and notes. Export can be disabled in **Policies** (**CSV export** toggle). ### Viewing analytics Go to **Admin → Compensation Management → Analytics**. Charts include salary distribution, 6-month compensation trends, department breakdowns, and comp-ratio distribution (requires pay grades). Managers see analytics only if the **Manager analytics access** policy is on, and their data is scoped to their own reports. ### Viewing the audit trail Go to **Admin → Compensation Management → Audit Trail**. Every compensation change is logged with who changed it, when, the previous and new values, and the reason. Managers see only their reports' history. Filter by employee, date range, or change type (salary increase, decrease, type change). ## 5. Settings ### Advanced Settings (Admin → Compensation Management → Advanced Settings) | Setting | Default | What it changes | |---|---|---| | Auto-approval enabled | Off | When on, a CSV import run in **Auto-Approve Small Changes** mode approves raises within the thresholds below automatically. Bulk updates and employee requests are never auto-approved (a bulk update in Admin Override mode applies at once, with no approver) | | Auto-approval percentage threshold | 5% | Maximum percentage change for auto-approval | | Auto-approval amount threshold | $2,000 | Maximum dollar change for auto-approval (both thresholds must be met) | | Maximum retroactive days | 30 | How far back an effective date can be set on a new approval request | | Approval reminder days | 3 | Days after which the approver receives a reminder notification for a pending request | | Step increases enabled | Off | Enables step-increase scheduling (automatic grade-based pay progression) | | Default currency | USD | Currency pre-filled for new compensation records (supported: USD, EUR, GBP, CAD, AUD) | | Default pay frequency | Monthly | Pay frequency pre-filled for new records (Weekly, Bi-weekly, Monthly, Quarterly, Annually) | | Pay transparency enabled | Off | When on, employees see where their pay sits in their pay-grade band on My Compensation and in Ask AI; when off, Ask AI gives only the grade name | ### Policies (Admin → Compensation Management → Policies) | Setting | Default | What it changes | |---|---|---| | Employee self-view | On | Whether employees can see their own compensation in **My Compensation** | | Employee compensation requests | Off | Whether employees can submit compensation change requests | | Employee request frequency | Once per year | How often an employee can submit a request (Once per year, Twice per year, No limit) | | Manager team compensation | On | Whether managers can view their direct reports' compensation | | Manager visibility level | Salary ranges only | What managers see: Full salary amounts, Salary ranges only, or No compensation details | | Manager analytics access | Off | Whether managers can access the analytics dashboard (scoped to their reports) | | CSV export enabled | On | Whether admins can export compensation data as CSV | | Session timeout | 30 minutes | Inactivity timeout for the compensation session (15, 30, or 60 minutes; or no timeout) | | Mobile compensation access | On | Whether employees can view compensation on mobile devices | ### Who can view team compensation (Admin → Compensation Management → Policies) A capability picker that controls which non-admin users can see their team's compensation. Options: **App admins only** (default when team compensation toggle is off), **Managers** (default when team compensation toggle is on), or **Specific people/groups**. ## 6. More help - **Compensation Management FAQ** — specific setup, approval, and operating questions - Ask AI — the assistant answers questions about Compensation Management from these articles. **Keywords:** compensation, salary, pay, hourly rate, pay grade, comp ratio, compensation approval, merit, pay equity, bulk update, compensation history, pay frequency, compensation policy, compensation-management, compensation_management --- # Compensation Management FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-18 Answers to common setup and operating questions about Compensation Management — for the admin running it. # Compensation Management FAQ Answers to common setup and operating questions about Compensation Management. For what the app is and how to set it up from scratch, see the [Compensation Management Overview](/help/articles/compensation_management_app_overview). --- ## Setup ## Do I need to configure anything before employees can see their compensation? Yes. Two things must be true: the app must be enabled in **Admin → Apps → All Apps**, and the **Employee self-view** toggle in **Admin → Compensation Management → Policies** must be on (it is on by default). If either is off, employees see nothing. Managers also need the **Manager team compensation** toggle turned on before they see their reports' pay. ## Who can access compensation data once the app is on? Three tiers of access exist. The **function tier** — admins, super admins, and anyone with the Compensation Management app-admin role — can see and edit all employees' compensation, manage pay grades, run imports, and view analytics company-wide. HR staff get access through the Admin role, an app-admin grant, or the Policies page's **Specific people** option. **Managers** can view their direct reports' compensation when the team compensation toggle is on, scoped by the visibility level you set in Policies. **Employees** can view their own pay on the **My Compensation** page when employee self-view is on. --- ## Permissions and access ## Why can't a manager see their team's compensation? The **Manager team compensation** toggle in **Policies** must be on. If it is on and the manager still sees nothing, check the **Manager visibility level** — if it is set to **No compensation details**, amounts are hidden entirely. Also confirm the manager actually has direct reports assigned in the org structure; the view is scoped to their own reports, not a department. ## Can I control how much pay detail managers see? Yes. Under **Admin → Compensation Management → Policies**, the **Manager visibility level** setting has three options: **Full salary amounts** shows exact numbers, **Salary ranges only** shows pay in $10,000 bands for salaried employees and $5 bands for hourly employees, and **No compensation details** hides amounts entirely. The default is **Salary ranges only**. --- ## Day-to-day ## How does auto-approval decide whether to approve a change? Auto-approval applies only to a CSV import run in **Auto-Approve Small Changes** mode — it never applies to bulk updates or employee requests (a bulk update in Admin Override mode applies at once, with no approver). It must be turned on in **Admin → Compensation Management → Advanced Settings**. When it is on, an imported change is auto-approved only if it is an **increase** and it falls within **both** the percentage threshold (default 5%) **and** the dollar threshold (default $2,000). If either threshold is exceeded, the change is routed to manual review. Changes on an employee with no current pay (a new position) always require manual approval regardless of thresholds. ## How far back can an effective date be set on a compensation change? The **Maximum retroactive days** setting in Advanced Settings controls this. The default is 30 days. Any request with an effective date further back than that limit is rejected at submission. The allowed range for this setting is 0–365 days. ## When does a pending approval show as waiting too long? A pending request waiting more than 7 days is counted under **Waiting over 7 days** on the Approvals page. A request whose effective date is within the next 30 days carries a **Soon** badge. Approvers also receive a reminder notification after the number of days set in **Approval reminder days** (default 3 days). ## Can I cancel or reverse an approved compensation change? You can cancel a request only while it is still **Pending**. The original requester or any admin can cancel it. Once a request is approved, the change is applied to the employee's record immediately and cannot be undone through the approval workflow — unless their pay changed after it was filed, they left, it sets pay for a pay type they are not on, or their pay already matched it. Then it is recorded as **Approved — not applied** and their pay is unchanged. To correct an approved change, submit a new change request with the correct values. ## What happens when I import a CSV of compensation changes? Upload the file at **Admin → Compensation Management → Import** (maximum 10 MB, CSV format). The file must include an **Employee ID** column to match rows to employees. You choose an approval mode: apply all changes immediately (admin override), route everything through approval, or use auto-approve for changes within your configured thresholds and route the rest. Each row creates a separate change request, and duplicates can be set to update or skip. --- ## When something looks wrong ## Why can't I see my pay information? Your administrator controls whether employees can view their own compensation. If the **My Compensation** page is not showing, the **Employee self-view** toggle may be off. If you are on a mobile device, the **Mobile compensation access** toggle may also be off. Ask your admin to check both settings under **Admin → Compensation Management → Policies**. ## I submitted a compensation change request but nothing happened — where is it? Your request is waiting for an approver to review it. Go to **My Requests** to check its status. If you do not see a way to submit a new request, your admin may have disabled employee requests, or you may have reached the submission limit — employees can submit once per year, twice per year, or with no limit, depending on the policy your admin set. The limit counts from the day of your last request, not a calendar period, and **My Requests** shows the date you can send the next one. A request you withdraw before it's reviewed doesn't count toward the limit. ## Why does the compensation page ask me to verify my identity again? Compensation data is classified as sensitive. Every time you open a page that shows per-employee pay, you must re-verify your identity through a step-up check. Once verified, the session stays elevated for 15 minutes before the next prompt. If you fail the verification 5 times, you are locked out for 15 minutes. ## Why did Ask AI say it needs my identity verified before it changes pay? Changing an employee's pay, or approving or rejecting a pay-change request, through Ask AI is for compensation administrators, and it uses the same identity check as the Compensation pages. Ask AI shows a card with the before and after, and the change is made only when you press **Confirm** on that card. If the check has not been done, verify your identity on any Compensation page (it stays valid for 15 minutes), then ask Ask AI again and press **Confirm**. Typing "yes", or approving from Slack, Teams, a phone app, another app or a connector, cannot carry the identity check, so those cannot change pay — use Ask AI in your browser. ## A pay grade won't delete — what's blocking it? A pay grade cannot be deleted while it is in use — by current or former employees, a step schedule, or a job title. The message says which, and the Pay Grades list shows "Can't delete: used by …" on that row. Move them to another grade first (job titles under **Admin → Job Titles & Families**), then delete it. ## Why is the comp-ratio chart on the analytics page empty? Comp-ratio requires pay grades. If no pay grades have been created, or no employees are assigned to a grade, the chart has no data to plot. Create grades at **Admin → Compensation Management → Pay Grades** (or click **Start from a standard ladder** for a default 11-grade ladder you can then edit), then assign employees at **Grade Assignments**. ## Why did some employees get skipped during a bulk update? The bulk update applies only to the employees you selected and only if they have existing compensation data. Employees with no compensation record are skipped. Check the results summary after the operation — it reports how many were updated and how many were skipped. --- ## Licensing and limits ## Does Compensation Management require a licence? Yes. It requires a licence and is disabled by default. An admin enables it from **Admin → Apps → All Apps**. It is not available until then. ## What are the limits I should know about? | Item | Limit | |---|---| | CSV import file size | 10 MB | | Accepted import format | CSV only | | Compensation roster page size | 25 per page | | Audit trail page size | 50 per page | | Grade assignments page size | 50 per page | | Maximum retroactive effective date | 0–365 days (default 30) | | Step-up verification attempts before lockout | 5 attempts, then 15-minute lockout | | Compensation session timeout options | 15, 30, or 60 minutes (or no timeout) | | Employee request frequency options | Once per year, Twice per year, or No limit | | Supported currencies (default currency setting) | USD, EUR, GBP, CAD, AUD | | Auto-approval percentage threshold range | 0–100% (default 5%) | | Auto-approval dollar threshold | Must be greater than $0 (default $2,000) | | Comp-ratio bands | Below Range (<80%), Below Market (80–95%), At Market (95–105%), Above Market (105–120%), Above Range (>120%) | --- ## More help - [Compensation Management Overview](/help/articles/compensation_management_app_overview) - Ask AI — the assistant answers Compensation Management questions from these articles. **Keywords:** faq, compensation, salary, pay grade, comp ratio, approval, step-up verification, bulk update, CSV import, pay frequency, manager visibility, auto-approve, compensation request, audit trail, compensation-management, compensation_management --- # Compliance Administration **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-14 The admin Compliance section — work-hour limits, rest periods, jurisdiction mapping, labor law enforcement, gap analysis, and audit trails. # Compliance Administration ## 1. What it is Compliance Administration is the admin sidebar section where you configure how the platform enforces labor and employment law during shift assignment. It contains the work-hour limits, rest-period rules, jurisdiction mappings, the employment-law rule library, a compliance explorer with gap analysis, and the audit trails that record every enforcement decision. - **Enablement:** The section appears automatically for every admin under **Admin → Compliance**. No app license is required. The Compliance Audit Logs surface within it requires the Platform Enterprise edition. - **What it is not:** This is not the Compliance Hub app (SOX/SOC 2 framework compliance) or Content Governance (moderation of user-generated content). It governs work-hour, rest-period, and labor-law enforcement in scheduling. ## 2. Standing it up 1. Go to **Admin → Compliance → Work Policy Settings**. A default RestPeriodSetting record is created automatically when a business is first created — you start with working defaults, not a blank form. 2. Review the hour limits and rest-period minimums. The defaults are 12 hours daily, 40 hours weekly, and 8 hours minimum rest. All three enforcement toggles are on by default. 3. Go to **Admin → Compliance → Jurisdictions** and create the jurisdictions your business operates in (country, state, or city). You can import from the global MangoApps jurisdiction catalog or create custom ones. 4. Go to **Admin → Compliance → Jurisdiction Mapping** and assign jurisdictions to your locations. Until a location has at least one jurisdiction, no labor-law rules are enforced for shifts at that location — this pairing is the most common silent setup gap. 5. Go to **Admin → Compliance → Labor Law Rules** and create the rules for each jurisdiction — wage, overtime, break, scheduling-notice, or minor-work rules. 6. To confirm it is working, assign an employee to a shift that would violate a configured limit. The assignment should either be blocked or produce a warning, depending on whether the violation is configured as a hard disqualifier or a warning penalty. ## 3. How it fits together **The sidebar groups eight surfaces** into one section, each handling a different part of the compliance lifecycle: - **Work Policy Settings** — tenant-wide hour limits, rest periods, break enforcement mode, and match-calculation dials. This is the enforcement configuration. - **Labor Law Rules** — per-business, per-jurisdiction scheduling rules (wage, overtime, break, schedule, minor). - **Employment Law Rules** — the global MangoApps-maintained rule library, plus business-specific overrides. - **Jurisdictions** — the business's jurisdiction registry (country/state/city hierarchy). - **Jurisdiction Mapping** — which jurisdictions apply to which locations. - **Compliance Explorer** — a read-only browser over the global rule catalog, with gap analysis, what-if simulation, and semantic search. - **Compliance Audit Logs** — shift-assignment compliance decisions (the Platform Enterprise edition only). - **Employment Law Audit History** — the immutable employment-law event trail. **Enforcement vs. observation.** Several controls operate on a spectrum rather than a simple on/off: - **Break enforcement mode** has three settings: **off** (no evaluation), **observe** (evaluate and record, but do not block anything), and **enforce** (evaluate, record, prompt at clock-out, and block non-compliant assignments). New tenants start in **observe** so admins can review their break-compliance backlog before it starts blocking. - **Hard disqualifiers vs. warning penalties.** Each compliance check — daily hours, weekly hours, rest period, overlapping shifts, approved leave, and availability conflicts — can be set as a hard disqualifier (blocks the assignment entirely, 0% match) or left as a soft check (reduces the match percentage by a configurable penalty but still allows the assignment). **Three-tier rule architecture.** The platform resolves which rules apply to a shift by combining three layers: 1. **System rules** (SystemEmploymentLawRule) — global, maintained by MangoApps, covering 18 document types and 18 rule categories across federal, state, and city jurisdictions. 2. **Business overrides** (BusinessEmploymentLawOverride) — per-business additions or stricter versions of system rules. Cannot relax a system rule. 3. **Labor law rules** (LaborLawRule) — per-business, per-jurisdiction scheduling rules that the shift-assignment engine reads directly. When rules at multiple jurisdiction levels apply, the more specific jurisdiction wins (city over state, state over country). ## 4. Running it ### Reviewing the compliance posture 1. Go to **Admin → Compliance → Compliance Explorer**. 2. The overview shows counts of total rules, federal rules, state rules, and city/local rules from the global catalog. 3. Click **Gap Analysis** to run a gap analysis against your business's locations. The service checks jurisdiction coverage, document completeness (employee handbook, anti-harassment policy, safety compliance), training requirements, and workplace posting requirements, and produces a compliance score with prioritized action items. ### Running a what-if simulation 1. In the Compliance Explorer, click **What-If**. 2. Choose a scenario type: add a new location, add employees to a state, or change industry. 3. For a location scenario, select a state and optionally a city. The simulator compares your current rules against the rules that would apply in the new location and reports additional requirements, impact level, and recommended actions. ### Searching the rule library 1. In the Compliance Explorer, click **Search**. 2. Enter a natural-language query. The search first tries semantic search (vector similarity against rule embeddings), then falls back to keyword search if no results match above the relevance threshold. ### Adjusting enforcement dials 1. Go to **Admin → Compliance → Work Policy Settings** and click **Edit Settings**. 2. Adjust the hour limits, enforcement toggles, hard disqualifiers, or warning penalties. 3. Save. Changes take effect immediately for all future shift assignments. ### Reviewing compliance decisions 1. Go to **Admin → Compliance → Compliance Audit Logs** (the Platform Enterprise edition required). 2. Filter by event type, decision, user, date range, or emergency overrides. 3. The analytics dashboard shows override usage, violation trends, weekly-hours risk, and work-context coverage. 4. Export the filtered log as CSV for external reporting. ## 5. Settings All settings below are on the Work Policy Settings page (**Admin → Compliance → Work Policy Settings**). | Setting | Default | What it changes | |---|---|---| | Maximum Daily Hours | 12.0 hours | Cap on hours an employee can be assigned in a single day | | Maximum Weekly Hours | 40.0 hours | Cap on hours an employee can be assigned in a week | | Minimum Rest Period | 8.0 hours | Minimum gap required between consecutive shifts | | Enforce Daily Hour Limits | On | Whether the daily-hours cap blocks or just warns | | Enforce Weekly Hour Limits | On | Whether the weekly-hours cap blocks or just warns | | Enforce Minimum Rest Periods | On | Whether the rest-period minimum blocks or just warns | | Daily Hours Warning Threshold | 80% | Percentage of the daily cap at which a warning fires | | Weekly Hours Warning Threshold | 80% | Percentage of the weekly cap at which a warning fires | | Allow Consecutive Shift Overlap | On | Whether shifts may overlap for handover time | | Max Consecutive Shift Overlap | 30 minutes | How much overlap is allowed when enabled | | Break Enforcement Mode | Observe | Off / observe / enforce — controls break-compliance evaluation | | Daily Hours Hard Disqualifier | On | Whether exceeding the daily cap blocks assignment (0% match) | | Weekly Hours Hard Disqualifier | On | Whether exceeding the weekly cap blocks assignment | | Rest Period Hard Disqualifier | On | Whether violating the rest minimum blocks assignment | | Overlapping Shifts Hard Disqualifier | On | Whether overlapping shifts block assignment | | Leave Requests Hard Disqualifier | On | Whether approved leave blocks assignment | | Availability Conflicts Hard Disqualifier | On | Whether availability conflicts block assignment | | Emergency Override Enabled | On | Whether managers/admins can override compliance blocks | | Contracted Days Off Block Mode | Soft prompt | Whether assignments on contracted days off prompt or hard-block | ## 6. More help - **Labor & Employment Law Rules** — detailed article on jurisdictions, rule types, overrides, and legal updates - **Audit Logs & Activity History** — detailed article covering all four audit log surfaces - Ask AI — the assistant answers compliance configuration questions from these articles. **Keywords:** compliance, work policy settings, rest period, daily hours limit, weekly hours limit, compliance explorer, gap analysis, what-if simulator, jurisdiction, labor law, employment law, compliance audit, break enforcement, shift assignment compliance, hard disqualifier, match calculation --- # Compliance Hub FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Compliance Hub — permissions, review campaigns, findings, the Risk Register, the Legal Register, evidence, auditor exports, and every limit — for the admin running it and the employees who attest. # Compliance Hub FAQ Answers to common setup and operating questions about Compliance Hub. For what the app is and how to set it up from scratch, see the [Compliance Hub Overview](/help/articles/compliance_hub_app_overview). --- ## Setup ## Do I need to configure anything before review campaigns work? Controls, general campaigns, findings and both registers work as soon as the app is enabled. Certification and change reviews need a source: Contracts / Supplier Hub or Service Desk when connected, otherwise vendors and changes you add to the **Review Register** — with neither, **Build items** creates nothing. Three features are off by default and need a switch in Settings: **Require evidence when attesting a review item**, **Auto-collect evidence from linked records** and **Require identity verification to download evidence**. ## Who can manage the compliance program, and how do I change that? By default only business admins and Compliance Hub app administrators can create controls, campaigns, subjects, findings, risks and obligations, decide other people's items, and generate exports. Change it under **Settings → Permissions** with the **Who can manage the compliance program?** picker: keep **Business admins and Compliance Hub app administrators only**, or choose **Specific people — admins, plus the groups I choose below** and name the groups. There is deliberately no "everyone" option. Regardless of the setting, every app member can still attest the items assigned to them. ## Who can see the Frameworks, Analytics and Guided Setup tabs? **Frameworks** appears for business admins and app admins, and only while **Enable Framework Library** is on. **Analytics** appears for managers and above, app admins, and anyone with the manage capability. **Guided Setup** appears for anyone with the manage capability. Everyone with app access sees the Program group: Dashboard, My Attestations, Controls, Review Register, Review Campaigns, Findings, Risk Register, Legal Register and Auditor Exports. ## Which frameworks are in the library, and can I add my own? Seven curated starter catalogs: SOC 2 (20 controls), SOX IT General Controls (15), ISO/IEC 27001 (20), HIPAA Security Rule (14), ISO 45001 (20), ISO 9001 (19) and ISO 14001 (14) — 122 controls with 113 crosswalks between them. They are starter subsets, not the full official standards. Tenant-defined frameworks cannot be created in the app; catalogs are authored in the MangoApps Console. You can still add your own controls to the register with the **Custom** framework tag. --- ## Permissions and access ## Why can't I see the findings my colleague mentioned? Findings are viewer-scoped. Managers and above, and anyone with the manage capability, see the whole register. Everyone else sees only the findings they own — on the Findings tab, on a control's page, on the Dashboard, in search and in Ask AI. If you should own that finding, ask its owner or an admin to reassign it to you. ## Who can generate the export or publish an anonymous auditor link, and what happens if I turn the toggle off? Generating, downloading, publishing and revoking exports needs the manage capability (business admins and app admins always have it). Publishing also needs **Allow anonymous auditor links** switched on in **Settings → Evidence & Scheduling**. Turning that toggle off disables every link already handed out, not just new ones; the export itself stays and can still be downloaded by a logged-in user with the manage capability. ## Who can unlock a completed campaign? Only business admins and Compliance Hub app administrators, regardless of the manage capability. Unlocking returns the campaign to **Active** so rows can be added, and the campaign completed and locked again. Rows that were already decided keep their decision; if one is removed, the removal and who had decided it are listed in the campaign's **History**. The unlock is listed there too, with who did it and when the campaign was first completed, and the auditor package shows the same history. Completing it again does not move its control's next review date. Archived campaigns cannot be unlocked at all. --- ## Day-to-day ## How does Build items decide who reviews what? Access reviews create one item per active person and assign it to that person's manager, never to the person themselves; with no manager, the campaign owner gets it. Certification reviews create one item per vendor certification from Contracts / Supplier Hub plus the Review Register. Change reviews create one item per Service Desk change request inside the campaign's date window plus the Review Register. General campaigns have no fan-out. Running **Build items** again is safe — existing subjects are skipped. ## I flagged an item — what happens now? A finding opens automatically, titled "Flagged: " plus the subject, with your reason as its description, **Medium** severity and a due date 30 days out. Its owner is the item's reviewer — the person the row is assigned to, so flagging someone else's row makes them the owner — or the campaign owner if that reviewer has left. The owner is told in-app and by push unless they flagged it themselves, and the review's owner is told an item in their review was flagged. The finding shows up on the control's page and the Dashboard. Flagging the same item again does not create a second finding. ## Where do I record that I reviewed my risk? Open the risk in **Risk Register**, expand **Record review**, set **Next review** and click **Mark reviewed**. That stamps you and today's date and moves the next review out by the risk's **Review cadence**. Only the risk's owner or someone with the manage capability can record a review; the nightly sweep reminds the owner when it is due or overdue. ## How do I evaluate a legal obligation? Open it in **Legal Register**, expand **Evaluate**, choose an **Outcome** (**Compliant**, **Partially compliant**, **Non-compliant** or **Not assessed**), set **Next evaluation** and click **Record evaluation**. The Dashboard's **Legal Register** card counts active obligations, gaps (partially or non-compliant), not assessed, and evaluation overdue. The owner or a manage-holder can evaluate. ## Where do the risk and legal suggestions come from, and why don't I see any? Both panels are shown only to people who can author the register. **Suggested from Safety Hub & Inspections** lists high or critical incidents and near misses from the last 12 months, failed inspections, and open regulator-visit findings — and only for apps you can open, up to 8 per source. **Suggested from your jurisdictions** lists active employment-law catalog rules for your mapped jurisdictions and their parents, up to 40, skipping rules already cited. If no location is mapped to a jurisdiction, the panel shows **Map your locations** instead. ## Can I attest all my pending items at once? Yes. On the campaign page, **Attest all my pending** attests every pending item assigned to you; someone with the manage capability can use **Attest all pending** for the whole campaign, recorded under their own name, except a row about their own access. Each click handles up to 200 items. When **Require evidence when attesting a review item** is on, items without evidence are skipped and the result says how many. ## Can I certify my own access? No. A row about your own access is decided by someone else, even if you run the program: the build step gives it to your manager (or, if you have none, to the review's owner or another program reviewer), the reviewer picker will not assign it to you, and Attest, Flag and N/A are not offered on it — on the campaign page, on your phone, or in **Attest all pending**. If no one else holds that row, someone who can manage the program reassigns it to another reviewer. ## What notifications does Compliance Hub send, and how often? Three switches in **Settings → Notifications**, all on by default. **Notify people about assignments and flagged items** covers every hand-over: a reviewer's assigned item (in-app, push and email) and campaign activation; a finding assigned to its owner, or reopened; a risk or legal obligation assigned to its owner; a recurring review opened automatically (to its owner — the control's owner when they can run the review, otherwise a program manager); an item flagged in a review (to the review's owner); and a finding closed (to whoever flagged it). **Send due-soon reminders** emails the campaign owner weekly inside the due-soon window, and its pending reviewers once the campaign is active (a draft's reviewers are not reminded; the owner is told it still needs activating); findings, risk reviews, legal evaluations and expiring evidence get in-app notices only. **Send overdue alerts** covers the same things, repeats every 3 days and stops 90 days after the due date. A campaign that was unlocked after it was completed gets no overdue alerts once its due date has passed, and it no longer holds back its control's next scheduled review. People can mute Compliance Hub email in their own notification preferences. --- ## When something looks wrong ## "I attested an item but it still shows pending" The campaign was archived while the item was still pending. Archiving locks a campaign for good, so the item keeps its pending status in the record and cannot be decided. (A completed campaign has no pending items: every row is decided before it can be completed.) To review that access now, ask whoever runs the program to add it to the current campaign. ## "Why can't I attest from my phone?" The mobile site can attest, flag and mark items not applicable, but it cannot attach evidence. When **Require evidence when attesting a review item** is on and the item has none, its card says "Needs evidence before you can attest" and offers **Attach evidence on the full site**, which opens that item on the full site with its evidence panel open. Attach the file there, then attest from either surface. ## "The export is missing the Risk Register and Legal Register sheets" Both registers are included in a full-program export, Excel or PDF. Choose **All — full program** as the **Scope**. A framework-scoped export limits evidence to that framework's controls and omits both registers. ## "I imported a framework but some controls say already present" The import is idempotent. A catalog entry is counted as skipped, not duplicated, when your register already holds it: the same entry imported before, or a control of the same framework (or one with no framework, such as a hand-made or CSV-imported control) that already uses its code. Re-importing after a catalog update adds only the new entries. When a control from a *different* framework already uses the code, the entry is still imported, under a code prefixed with its framework (for example `ISO45001-5.2`), so the two do not count toward each other. You can import by category, or tick the option to include crosswalked equivalents from other frameworks; imported controls are due in 30 days and owned by the importer. --- ## Licensing and limits ## Does Compliance Hub require a licence? Yes. Compliance Hub requires a licence and is enabled per tenant by an admin through Admin → Apps → All Apps. It is not auto-enabled. ## Are there limits I should know about? | What | Limit | |---|---| | Evidence file upload | under **25 MB** per file; label up to **255** characters | | Titles / reference code | **255** / **64** characters (reference code unique per business, case-insensitive) | | Decision note | **2,000** characters | | Fan-out subjects per campaign | **500** | | Bulk attest | **200** items per click | | Campaign items per page | **100**; other lists **25**; framework catalog **50** | | Control page | shows **20** campaigns, **50** evidence entries, **20** open findings | | CSV imports (controls, subjects) | **2,000** rows / **10 MB** per file | | Framework import | imported controls due in **30** days | | Due-soon window | default **14** days, accepts **1–120** | | Default review lead time | default **30** days, accepts **1–365** | | Reminder cadence | assignment once; due-soon weekly; overdue every **3** days, stopping **90** days past due | | Evidence expiring-soon badge | the due-soon window (default **14** days) before the valid-until date | | Auditor link expiry | **1–365** days or never (form default **90**) | | Auditor portal throttle | **1,000** page views and **30** downloads per hour per IP address | | Identity-verified download link | valid **15** minutes | | Export build | polls for about **5** minutes; export rows are never deleted | | Risk scale | **5 × 5**; Low **1–4**, Medium **5–9**, High **10–16**, Critical **17–25** | | Risk suggestions | **8** per source (**24** max), **12**-month lookback | | Legal suggestions | up to **40** | | Crosswalk confidence | **0–100** | | XLSX cell | **32,767** characters, truncated with a marker | | Agent list tools | default **25**, max **100**; coverage gaps default **50**, max **200** | --- ## More help - [Compliance Hub Overview](/help/articles/compliance_hub_app_overview) - Public framework library at **/compliance-library** — catalog controls, evidence hints and crosswalks, readable without a login - Ask AI — the Compliance Hub agent answers Compliance Hub questions from these articles. **Keywords:** faq, compliance hub, control register, review campaign, attestation, finding, evidence, auditor export, auditor link, framework library, risk register, legal register, compliance obligation, SOX, SOC 2, ISO 27001, HIPAA, ISO 9001, ISO 14001, ISO 45001, bulk attest, not showing, permissions, limits, compliance-hub, compliance_hub --- # Compliance Hub Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-17 How to set up and run a compliance program in Compliance Hub — controls, review campaigns, findings, the Risk Register, the Legal Register, evidence, and auditor exports across SOC 2, SOX, ISO 27001, HIPAA, ISO 9001, ISO 14001 and ISO 45001. # Compliance Hub ## 1. What it is Compliance Hub is where your team runs its own compliance program. You keep a register of controls, run recurring review campaigns that send attestation items to reviewers, track findings through remediation, and hand auditors an evidence package. Seven framework catalogs are available to start from: SOC 2, SOX, ISO 27001, HIPAA, ISO 9001, ISO 14001 and ISO 45001. Two registers sit alongside the controls. The **Risk Register** rates hazards on a 5 × 5 likelihood-by-impact scale and reminds owners to review them. The **Legal Register** lists laws, permits and contract requirements with a compliance status and an evaluation cadence. - **Enablement:** Compliance Hub is a licensed app. An admin enables it per tenant from **Admin → Apps → All Apps**; it is never on by default. - **What it is not:** Compliance Hub is not where policies are written or acknowledged — that is Policy Hub. Policies, SOPs, incidents and inspections stay in their own apps and link into Compliance Hub as evidence. ## 2. Standing it up 1. Enable the app from **Admin → Apps → All Apps**, then open **Apps → Compliance Hub**. The left rail shows a **Program** group (Dashboard, My Attestations, Controls, Review Register, Review Campaigns, Findings, Risk Register, Legal Register, Auditor Exports) and a **Manage** group (Frameworks, Analytics, Guided Setup, Settings) for privileged users. 2. Run **Manage → Guided Setup** (also linked from Settings as **Set up your program**). Pick a **Framework**, a **Program owner**, and tick **Import the framework's starter controls** and **Create the standard recurring reviews**. Setup imports the catalog's controls and creates three draft campaigns: **Annual Access Review**, **Annual Certification Review** and **Quarterly Change Review**. It is safe to run twice; nothing is duplicated. 3. Decide who manages the program. In **Settings → Permissions**, the **Who can manage the compliance program?** picker defaults to **Business admins and Compliance Hub app administrators only**. Choose **Specific people — admins, plus the groups I choose below** to name a compliance analyst who is not an admin. This is the platform's "Who Can Do What" capability picker. 4. Connect review sources. Certification reviews pull vendor certifications from Contracts / Supplier Hub. Change reviews pull change requests from Service Desk. Without those apps, add vendors and changes to the **Review Register** yourself. **Settings → Review Sources** shows a **Connected** or **Native register** badge per source. 5. Prepare the registers. Risk suggestions come from Safety Hub and Inspections, so the person authoring risks needs access to those apps. Legal suggestions come from the employment-law catalog through your mapped jurisdictions; the Legal Register shows **Map your locations** until at least one location is mapped. 6. Confirm it worked. The Dashboard shows control, campaign, finding, **Risk Register** and **Legal Register** cards. A reviewer sees their queue under **My Attestations** and on the mobile site at **/m/apps/compliance-hub**. Things that silently do nothing until a second thing is configured: - **Build items** on a certification or change campaign creates zero items when no source app is connected and the Review Register is empty. - The **Suggested from your jurisdictions** panel on the Legal Register is empty until locations are mapped to jurisdictions. - The **Suggested from Safety Hub & Inspections** panel is shown only to people who can author risks and can open those apps. - **Publish auditor link** is unavailable while **Allow anonymous auditor links** is off, and turning it off disables links already handed out. - Guided Setup only imports controls when **Enable Framework Library** is on and the runner is an admin or app admin. ## 3. How it fits together **Control vs framework control** — A control is a row in your register with an owner, a review cadence, a next review date and an effectiveness rating. A framework control is a catalog entry inside a framework in the library. Importing copies the catalog entry into your register and keeps a link back to it, which powers the **Also satisfies** crosswalk panel. **Campaign vs item vs subject** — A campaign is one review cycle, such as "Annual Access Review 2026". A subject is the thing being reviewed: a person's access, a vendor certification, a change request, or a row in the Review Register. An item is one attestation line, one campaign paired with one subject, assigned to a reviewer. Access reviews assign each person's item to their manager, never to the person themselves. **Finding vs risk vs obligation** — A finding is a tracked deficiency with an owner, a severity and a remediation lifecycle; flagging an item opens one automatically. A risk is a rated hazard with a likelihood, an impact and a review cadence. An obligation is a legal, permit or contract requirement with a compliance status and an evaluation cadence. They live in three different registers and are exported on three different sheets. **Inherent vs residual rating** — The inherent rating is the risk before treatment. The residual rating is optional and describes the risk after the treatment plan. Both use the same scale: score = likelihood × impact, banded **Low** (1–4), **Medium** (5–9), **High** (10–16) and **Critical** (17–25). > **Worked example.** A forklift-pedestrian conflict in Bay 3 is entered with Likelihood 4 and Impact 5. The inherent score is 20, so the badge reads **Critical**. After a barrier and a marked walkway, the owner records a residual Likelihood 2 and Impact 5. The residual score is 10, which reads **High**. The Dashboard's "high or critical" count uses the inherent rating. **Evidence vs linked source** — Evidence is the proof entry attached to a control, campaign, item, finding, risk or obligation. It is either an uploaded file or a link to a record another app owns: a vendor certification or contract obligation, a change request, an employee certification, an incident, CAPA action, toolbox talk or safety observation, an inspection, a policy, or an SOP. The picker only offers apps the viewer can open. Evidence can carry a valid-until date and shows **expired** or **expiring** badges. **Locked campaign** — Completing or archiving a campaign locks it. Decisions, evidence and subject deletion are frozen so the audit trail cannot change. Only a business admin or app admin can **Unlock** a completed campaign, to add rows before completing it again (decided rows keep their decision and reviewer); the unlock is listed in the campaign's **History** and in the auditor package. Archived campaigns are permanent. **Findings viewer scope** — Managers and above, and anyone with the manage capability, see the whole findings register. Everyone else sees only findings they own — on the register, the control page, the Dashboard, in Ask AI and in search. **Narrowed export** — An export scoped to one framework includes only that framework's controls and their evidence, and leaves out both registers. The **Risk Register** and **Legal Register** are included in a full-program export, Excel or PDF. Boundaries with other apps: management of change lives in Safety Hub permits and Service Desk change requests. Supplier pre-qualification lives in Safety Hub. Framework catalogs are authored in the MangoApps Console, not in the tenant. ## 4. Running it ### Running a review campaign 1. Go to **Review Campaigns** and create a campaign, or click **Launch Review Campaign** on a control's page. The due date defaults to today plus the **Default review lead time**. 2. Click **Build items** to fan out one item per subject. General campaigns have no fan-out; add items manually. 3. Click **Activate**. Reviewers are notified and the campaign can no longer return to draft. 4. Reviewers choose **Attest**, **Confirm flag** (a reason is required) or **Mark N/A** on each item. Anyone with the manage capability can use **Attest all pending** for the whole campaign, recorded under their own name. 5. When every item is decided, click **Complete & Lock**. The campaign locks and the control's next review date advances by its cadence. ### Managing findings 1. Go to **Findings**. Flagged items already appear here with the reviewer's note as the description and **Medium** severity. 2. To raise one by hand, add a finding with a title, severity, owner, due date, control and remediation plan. 3. The owner, or anyone who can manage the program, resolves it with **Resolve finding** and a resolution note, choosing **Remediated**, **Risk accepted (not remediated)** or **Closed**. Reopening clears the resolution stamp. ### Keeping the Risk Register current 1. Go to **Risk Register**. Use the **Suggested from Safety Hub & Inspections** panel and **Add to register** to pre-fill a risk from an incident, a failed inspection or a regulator finding. 2. Set the **Inherent rating** (Likelihood, Impact), a **Treatment / mitigation** plan, an optional **Residual rating**, an **Owner**, a **Review cadence** and optionally a **Treating control** and **Site / location**. 3. When the review date arrives, the owner opens **Record review**, sets **Next review** and clicks **Mark reviewed**. The nightly sweep reminds the owner when a review is due or overdue. ### Evaluating a legal obligation 1. Go to **Legal Register**. Use **Suggested from your jurisdictions** and **Add to register** to pre-fill from the employment-law catalog, or add an obligation with its **Citation**, **Regulator / authority**, **Jurisdiction** and **What it requires of us**. 2. Set an **Owner**, an **Evaluation cadence**, and optionally an **Implementing control**. 3. On the due date the owner opens **Evaluate**, picks an **Outcome** (Compliant, Partially compliant, Non-compliant or Not assessed), sets **Next evaluation** and clicks **Record evaluation**. The **gaps** filter lists everything partially or non-compliant. ### Handing an auditor the package 1. Go to **Auditor Exports**, choose a **Scope** (**All — full program** or one framework) and a **Format** (**Excel (XLSX)** or **PDF**), then click **Generate Export**. The page polls until the file is ready. 2. Click **Download package**, or **Publish auditor link** with an **Expires after (days)** value (default 90; blank never expires). The auditor opens the link without logging in. 3. Click **Revoke** to disable a link immediately. Export rows are kept permanently. 4. For a standing cadence, create an **Export Schedule** with a **Name**, **Scope**, **Cadence** (monthly, quarterly or annually) and **Next run**. Schedules can be paused and resumed. ## 5. Settings All settings are at **Apps → Compliance Hub → Settings** (business admin or app admin required). Allowed ranges are in the FAQ. | Setting | Where | Default | What it changes | |---|---|---|---| | Enable Compliance Hub AI Agent | Settings → Compliance Hub AI Agent | On | Makes the Compliance Hub agent available in Ask AI. It has 9 read tools and 4 confirmation-gated write tools (add, change or retire a control; launch a draft campaign) that only people who can manage the program hold. | | Who can manage the compliance program? | Settings → Permissions | Business admins and Compliance Hub app administrators only | Who can author controls, campaigns, subjects, findings, risks and obligations, build items, decide other people's items, run exports and schedules, and use Guided Setup. Admins always can. | | Enable Certification Review campaigns | Settings → Campaign Types | On | Offers the certification review type, its Guided Setup draft, and its fan-out from Contracts / Supplier Hub and the Review Register. | | Enable Change Review campaigns | Settings → Campaign Types | On | Offers the change review type, its Guided Setup draft, and its fan-out from Service Desk and the Review Register. | | Enable Framework Library | Settings → Campaign Types | On | Shows the Frameworks tab, allows Guided Setup to import starter controls, and enables the agent's framework coverage tool. | | Require evidence when attesting a review item | Settings → Evidence & Scheduling | Off | Blocks **Attest** until the item has evidence; bulk attest skips evidence-less items; on the phone, the item says it needs evidence and links to it on the full site. | | Require identity verification to download evidence | Settings → Evidence & Scheduling | Off | Adds a step-up identity check before an evidence file is served, via a short-lived signed link. | | Auto-collect evidence from linked records | Settings → Evidence & Scheduling | Off | The nightly sweep links vendor certifications and change requests as evidence onto pending items of active certification and change campaigns. | | Allow anonymous auditor links | Settings → Evidence & Scheduling | On | Allows **Publish auditor link**; turning it off also disables links already published. | | Due-soon window (days) | Settings → Evidence & Scheduling | 14 | How far ahead the Dashboard, list filters, nightly reminders and the agent treat something as due soon. | | Default review lead time (days) | Settings → Evidence & Scheduling | 30 | The default due date for new campaigns, launch-from-control, recurring campaigns and Guided Setup drafts. | | Notify people about assignments and flagged items | Settings → Notifications | On | Reviewers, when an item is assigned to them or a campaign activates (in-app and push; an assigned item also emails). A finding's owner when it is assigned to them or reopened, and the owner of a review, control, risk or legal obligation when it is handed to them (in-app and push). A review's owner when a recurring review opens automatically (the control's owner when they can run the review, otherwise a program manager) or an item in it is flagged, and whoever flagged an item when its finding closes (in-app). | | Send due-soon reminders — reviews, findings, risk reviews, legal evaluations and expiring evidence | Settings → Notifications | On | Weekly email to the campaign owner and, once the campaign is active, its pending reviewers (a draft's reviewers are not reminded; the owner is told it still needs activating); in-app only, to the owner, for findings, risk reviews, legal evaluations and expiring evidence (to whoever captured it; for proof the nightly sweep linked, to the reviewer holding that row, or the review's owner when the row has no active reviewer; not once its renewal is on the row as current proof). | | Send overdue alerts — reviews, findings, risk reviews, legal evaluations and expired evidence | Settings → Notifications | On | Same people, re-sent every 3 days and stopping 90 days after the due date. Not sent for a campaign unlocked after completion once its due date has passed. | Settings also hosts **Program Setup** (**Set up your program**) and **Demo Data** (**Load demo data** / **Delete demo data**), which only touch tagged demo records. ## 6. More help - **Compliance Hub FAQ** — specific setup and operating questions, employee complaints, and every limit - Public framework library at **/compliance-library** — the catalog controls, evidence hints and crosswalks, readable without a login - Ask AI — the Compliance Hub agent answers questions about Compliance Hub from these articles. **Keywords:** compliance hub, SOX, SOC 2, ISO 27001, HIPAA, ISO 45001, ISO 9001, ISO 14001, compliance controls, review campaign, attestation, audit export, evidence, finding, risk register, legal register, compliance obligation, vendor review, access review, change review, compliance framework, compliance-hub, compliance_hub --- # Content Governance FAQ **Category:** Faq **Section:** Administration **Updated:** 2026-09-29 Answers to common setup and operating questions about Content Governance, content ownership and Content Moderation — for the admin running it. # Content Governance & Moderation FAQ Answers to common setup and operating questions about Content Governance, content ownership and Content Moderation. For what these surfaces are and how to set them up from scratch, see the [Content Governance & Moderation Overview](/help/articles/compliance_content_governance). --- ## Setup ## Do I need to enable governance and moderation separately? Yes. Content Moderation follows the **moderation type** at Admin → General Settings → Content Moderation → Settings. The default is **Moderate only flagged content**: people report content, and nothing is screened automatically. Content Governance is switched on per app with **Enable automated governance scanning** on each app's card at Admin → General Settings → Content Governance → Settings. A few apps, such as Safety Hub, Contracts and Inspections, are switched in their own settings instead; their card says where. Neither needs a separate licence. ## Which apps does Content Governance cover? Twenty-three apps have governance checks: Libraries, Sites, Policy Hub (policies and handbooks), SOP Hub, Safety Hub, Wikis, Mango IQ, Mango GTM, Workforce Bots, Workspace, Drive, Inspections, Communications Hub, Contracts, Onboarding Hub, Service Desk, AI Front Office, RFP Desk, Recorder, Ask AI, Forms, HR Files and Training. Only these apps get a card on the governance settings page. ## Which content does moderation screen? Each app that accepts written content has its own screening policy — 31 today. They include Ask AI, Plugin Builder, the Forms builder and form submissions, Broadcast posts and comments, Recognition posts, Chat messages, and the public portals (Candidate Portal, Service Desk, Safety Hub, AI Front Office and others). Each policy decides which checks apply to its surface. Ask AI, for example, checks for prompt injection; a Broadcast post does not. --- ## Content ownership ## How do I set who owns a policy, page or SOP? Open the item's edit or settings screen and use its **Owner** panel. You can name a person, an **Owning team**, or both. The panel appears on policies, handbooks, SOPs, wikis (on the page's properties), knowledge-base articles, library items, forms, training courses and Sites pages (on Page settings). Anyone who can edit the item can change its owner, and the change saves with the rest of the form. ## Why won't it let me choose this person or team as the owner? Only someone who can open the item can own it. A person must be an active member who can open the item in its app. A team must be one of your organization's own groups, and every member must be able to open the item. The error names up to three members who can't. Give them access, or pick a team whose members all can. The team list shows the first 200 groups alphabetically. ## Why am I getting a review reminder for content I didn't write? You are its owner, or you are in the team that owns it. When an item falls due for review, the weekly scan reminds the named owner and up to 10 members of the owning team. Only people who can open the item are reminded. If nobody there can be reminded, the item's author is told. If the author can't be reminded either, the app's fallback reviewers are — usually up to five of your admins. ## Where can I see everything I'm responsible for keeping up to date? Open your avatar menu and choose **Content I own**. It lists, app by app, what you own by name, own through a team, or wrote while no owner is named. Each item shows when its review is due and any open issue. It also lists findings assigned to you, possible duplicates, and anything unpublished automatically after it expired, with **Publish again**. Each list shows up to 50 items. Anything you own but can't open is counted in a warning, not listed. ## What happens to someone's content when they leave? Offboarding hands it on. Items they own by name, and items they wrote with no owner named, go to their manager if that manager is still active. Otherwise they go to another active admin. Only what the new owner can open moves. The rest stays and is flagged **Owner has left** until someone chooses a new owner. The offboarding record shows this as **Content ownership**. Sites pages go to their own site's owners instead. ## How do I move all of one person's content to someone else? Use **Reassign content ownership** at Admin → General Settings → Content Governance → Settings. Choose **Reassign from** and **Reassign to**, then **Reassign all**. It covers policies, handbooks, SOPs, wikis, knowledge-base articles, library items, forms and courses, including items they wrote with no owner named. It works for people who have already left; the card lists anyone who left and still owns content. Only what the new owner can open moves, and you're told how much stayed. Sites pages are reassigned from each site's settings. ## Why can't I delete this group? The group owns content. A group that is the owning team of any policy, page, SOP or other governed item can't be deleted. The message says how many items it owns, and in which apps. Choose a new owner for those items first. Otherwise they would be left with no owner. --- ## Moderation access ## Who can review the moderation queue? Admins and super admins always can. Team admins can review items that belong to their own team, but not items from other teams or with no team. A reviewer assigned to the item can review it. For Chat messages, the moderators named in Chat's own settings can review them. ## Are admins screened by moderation? Usually not, but some surfaces screen everyone. Admins and super admins are exempt on most internal surfaces, such as Broadcast posts and Recognition posts. Ask AI, Plugin Builder, the Forms builder and Ideas' **Draft with AI** screen admins too. Public portals always screen their visitors. --- ## Day-to-day ## What happens when I approve or reject a moderation item? **Approve** publishes the held content and records who reviewed it and when. **Reject** removes the content. If **Notify content authors when their content is approved or rejected** is on (the default), the author gets an email with the outcome. ## What is the "Published without an automated check" panel? It lists content that published without being screened. When an automated screen doesn't answer in time, the system lets the content through rather than blocking it. These aren't decisions waiting for you, so they sit in their own panel below the queue. It covers the last 7 days and shows up to 10 rows. ## When do the governance scan and gap analysis run? The governance scan runs every Monday at 7:00 AM UTC. You can also start one with **Run Scan** on the findings page, once every 5 minutes. Gap analysis runs separately, every Wednesday at 7:00 AM UTC. It needs gap analysis turned on for the app and at least 50 searches in the last 30 days. --- ## When something looks wrong ## "A governance finding disappeared from the list" It was snoozed or it cleared. A snoozed finding stays open but leaves the worklist until its date passes; the date must be in the future. Each weekly scan also rechecks open findings. If the problem has gone — the content was updated, a missing source came back, or the item was deleted — the finding is resolved automatically. ## "I enabled AI moderation but nothing is getting blocked" AI moderation starts in **Observation** mode. It records what it would flag, but doesn't block or hold anything. Switch **AI Mode** to **Live** in Content Moderation settings when you're happy with what it catches. ## "The governance scan shows zero findings for most apps" Each app must be switched on for governance. At Admin → General Settings → Content Governance → Settings, check **Enable automated governance scanning** on each app you want scanned. For an app switched in its own settings, the card links there. The scan skips any app that is off. ## "A governance finding has been open for weeks — why hasn't it escalated?" Only **Low** and **Medium** findings escalate. A Low finding becomes Medium 30 days after it was found; a Medium finding becomes Critical 60 days after it was found. Both windows can be changed per app. A finding rated High stays High. Snoozed findings and possible duplicates never climb. Only **Open** and **Acknowledged** findings escalate, and each weekly scan moves a finding up at most one level. --- ## Licensing and limits ## Are there limits I should know about? | What | Limit | Where it applies | |---|---|---| | Review interval | 7–365 days per app | **Review Interval (days)** on each app's governance card | | Escalation windows | 1–365 days each | **Severity Auto-Escalation** on each app's governance card | | Default review interval (Libraries) | 90 days | Libraries, before you change it | | Default Low → Medium escalation | 30 days after a finding is found | The weekly scan, before you change it | | Default Medium → Critical escalation | 60 days after a finding is found | The weekly scan, before you change it | | Manual scan cooldown | 5 minutes | **Run Scan** on the findings page | | Broken links checked per scan | 50 | The broken-link check in each scan | | Broken-link timeout | 10 seconds | The broken-link check in each scan | | Failures before a broken link is critical | 3 in a row | The broken-link check in each scan | | Team members reminded per item | 10 | Review reminders to an owning team | | Admins reminded when nobody else can be | 5 | Review reminders, in most apps | | Items listed per app | 50 | **Content I own** | | Groups in the owning-team list | first 200, alphabetically | The **Owner** panel | | Content excerpt kept per moderation item | 500 characters | Each item in the moderation queue | | AI negativity tolerance | 0–100 (0–25 strict, 26–50 moderate, 51–75 relaxed, 76–100 lenient) | **Negativity Tolerance** in Content Moderation settings | | Gap analysis minimum | 50 searches in 30 days | The weekly gap analysis | | Unscreened-publish panel | last 7 days, 10 rows | **Published without an automated check** | --- ## More help - [Content Governance & Moderation Overview](/help/articles/compliance_content_governance) - [Audit Logs & Activity History](/help/articles/compliance_audit_logs) — tracks moderation decisions and governance changes - Ask AI — the assistant answers Content Governance & Moderation questions from these articles. **Keywords:** faq, content moderation, content governance, content owner, owning team, content I own, review reminder, reassign content ownership, offboarding, can't delete group, moderation queue, flagged content, stale content, broken links, AI moderation, observation mode, escalation, gap analysis, snooze finding --- # Content Governance & Moderation **Category:** Business-configuration **Section:** Administration **Updated:** 2026-09-29 Two admin surfaces under Admin → General Settings: Content Moderation screens what people post as they post it, and Content Governance checks published content for staleness, broken links, expiry and missing owners, and routes each finding to whoever owns the content. # Content Governance & Moderation ## 1. What it is Content Governance & Moderation are two admin surfaces that keep your tenant's content safe and current. **Content Moderation** screens what people post — comments, chat messages, AI prompts — as they post it, and blocks, holds or flags it. **Content Governance** checks content that is already published and files a **finding** (a flagged issue) for each problem: overdue for review, a broken link, expired but still live, no owner. Each finding goes to the person or team that owns the content. - **Enablement:** both live under **Admin → General Settings**, with no separate licence. Governance scanning is switched on per app on its **Settings** tab. - **What it is not:** moderation does not judge old content, and governance does not screen new posts. Moderation asks "should this be published?"; governance asks "is what we published still right, and who answers for it?" ## 2. Standing it up ### Content Moderation 1. Go to **Admin → General Settings → Content Moderation**, then open **Settings**. 2. Under **What to Moderate**, pick one option. The default is **Moderate only flagged content**: posts publish normally and users can report them. The others are **Moderate all content** (every new post and comment is held for approval) and **Keyword + AI moderation** (content is flagged when it matches a keyword or the AI detects an issue). 3. For keyword screening, add words to **Custom Keywords**, separated by commas. A built-in library of offensive words is checked as well. 4. To add AI screening, tick **Enable AI content moderation**. It starts in **Observation** mode, which records what the AI would flag without blocking anything. Switch to **Live** when you trust the results. 5. Under **Which Users / Teams?**, the default is **All users**. You can pick **Only specific users** or **Exempt specific users / teams** instead. Admins are exempt from screening on most surfaces. 6. Check the **Queue** tab. Held and reported items appear there for review. ### Content Governance 1. Go to **Admin → General Settings → Content Governance**, then open **Settings**. Each governed app has its own card. 2. Tick **Enable automated governance scanning** for each app you want checked. It starts on for Ask AI, Drive, Forms, Policy Hub, Training and Workspace, and off for the rest. Sites, Safety Hub, Inspections and Contracts are switched on from their own settings; their card links there. 3. Set **Review Interval (days)** where the card offers it. Some apps set their own interval, and the card shows it read-only. 4. Name owners. Open a policy, SOP, wiki page, library item, form, course, handbook, knowledge-base article or site page and fill in its **Owner** panel. **Owned content does nothing extra until governance is on for its app** — without the scan, nobody is reminded. 5. Wait for the weekly scan (every Monday at 07:00 UTC), or click **Run Scan Now** on the **Findings** tab. You can't start another within 5 minutes of the last run. 6. Check the **Findings** tab for results. ## 3. How it fits together **Owner, owning team and author.** Every governed item can name who answers for it. The **Owner** panel on the item's edit or settings screen has a person field and an **Owning team** field (one of your groups). You can fill in either or both. If both are empty, the item's author answers for it until an owner is named. Only someone who can open the item can own it; for a team, everyone in it must be able to open it. **The reviewer chain.** When a scan files a finding on owned content, the reminder goes to the first of these that applies: 1. the named owner, while they are an active member; 2. otherwise, the owning team's members (up to 10 of them); 3. otherwise, the author, while they are an active member; 4. otherwise, the app's own reviewers — by default your admins (up to 5). Only people who can open the item are told. A worked example: a Policy Hub policy names no owner but has **Owning team** set to "HR Operations". When its review falls due, the members of HR Operations who can open that policy are reminded. If everyone in the team has left, the reminder goes to the policy's author, and failing that to your admins. **Content I own.** Every person has a page at **avatar menu → Content I own**. It lists what they own in each app, whether they own it as **Owner**, as a **Member of** a team, or as **Author (no owner named)**. It shows each item's review date and any open findings. It also lists findings assigned to them, **Possible duplicates**, and anything **Unpublished automatically**. Items they own but cannot open are counted, never named, with a prompt to ask an admin. **Governed apps.** Each app decides what it checks. The apps with governance today are AI Front Office, Ask AI, Communications Hub, Contracts, Drive, Forms, HR Files, Inspections, Libraries, Mango GTM, Mango IQ, Onboarding Hub, Policy Hub (policies and handbooks), Recorder, RFP Desk, Safety Hub, Service Desk, Sites, SOP Hub, Training, Wikis, Workforce Bots and Workspace. **Findings come in types.** On Content I own, common ones read **No owner**, **Owner has left**, **Owner can't open it**, **Due for review**, **Review overdue**, **Expired, still live**, **Broken link** and **Possible duplicate**. The admin **Findings** list names a few differently — **Inactive owner**, **Stale content**, **Expired but live**. The duplicate check runs weekly across policies, SOPs, wikis, site pages and library items. **Unanswered questions (Ask AI).** Ask AI groups questions it could not answer from company knowledge. A group is shown only once at least 5 different people asked it. Each open group becomes an **Unanswered question** finding. The scan assigns it to a topic expert for the question's theme who can open it; with no expert, it stays unassigned and your admins are reminded. The owner writes the answer with **Create an answer**, if they are allowed to write Verified Knowledge. An owner who isn't an admin opens a read-only page for that one group from their reminder or from Content I own; admins work every group at **Ask AI → Agent Guidelines → Questions**. An answer from a non-admin waits for admin approval in Verified Knowledge, and no reminder goes out meanwhile. Approval closes the group and resolves its finding; a rejection hands the question back to its owner. Every Monday, before the scan, Ask AI re-asks each open group and closes any that company knowledge now answers. **Moderation modes.** **Moderate only flagged content** acts only on user reports. **Moderate all content** holds every post for review. **Keyword + AI moderation** holds or blocks only what triggers a rule. AI **Observation** mode logs without acting; **Live** mode blocks or holds. **Severity escalation.** Open **Low** findings become **Medium** 30 days after they were found; **Medium** findings become **Critical** 60 days after they were found. Both are adjustable per app. A finding climbs at most one level per weekly scan. **High** findings, snoozed findings and possible duplicates never escalate. **Boundary with offboarding and groups.** When an Offboarding plan removes someone, the policies, handbooks, SOPs, wikis, knowledge-base articles, library items, forms and courses they owned — or wrote with no owner named — are handed to their manager, else an admin. Only items the new owner can open move; the rest stay and are flagged **Owner has left**. Site pages are handed on by Sites itself. A group that owns content can't be deleted until that content has a new owner. ## 4. Running it ### Working the governance findings list 1. Go to **Admin → General Settings → Content Governance → Findings**. 2. Filter by app, issue type, severity or status. Snoozed findings are hidden until you tick **Show snoozed**. 3. For each finding, choose **Acknowledge**, **Resolve**, **Dismiss**, **Assign** (hand it to a person) or **Snooze** (hide it until a date; it stays open). 4. Select several findings for **Bulk Acknowledge**, **Bulk Resolve** or **Bulk Dismiss**. 5. Click **Export CSV** to download the filtered list. ### Handing someone's content to someone else Use this when a person changes role, or left without an Offboarding plan. 1. Go to **Content Governance → Settings** and scroll to **Reassign content ownership**. People who have left and still own content are listed there. 2. Pick **Reassign from** (anyone, including people who have left) and **Reassign to** (an active member). 3. Click **Reassign all**. Everything the new owner can open moves to them, and their open ownership findings are settled. You're told how many items stayed behind. The new owner gets a notification pointing to Content I own. Site pages are reassigned from each site's settings instead. ### Reviewing the moderation queue 1. Go to **Admin → General Settings → Content Moderation → Queue**. 2. Filter by source, issue type or severity. 3. **Approve** publishes the item; **Reject** removes it. The author is told either way, and you can add notes. 4. Below the queue, **unscreened publishes** from the last 7 days are listed. These went live because the automated screen did not answer in time. They are a record, not a to-do. ### Reading the analytics - **Content Governance → Analytics** shows findings over time, by issue type, app and severity, and time to resolve. Its **Gap Analysis** view shows the searches that found nothing, for apps where gap analysis is on. - **Content Moderation → Analytics** shows flagged content by source and severity, top flagged users, moderator activity, review time and AI security activity. ## 5. Settings ### Content Moderation — Admin → General Settings → Content Moderation → Settings | Setting | Default | What it changes | |---|---|---| | What to Moderate | Moderate only flagged content | Whether content is screened on report, always held, or screened by keywords and AI | | Custom Keywords | Empty | Extra words to catch, added to the built-in list | | Enable AI content moderation | Off | Whether the AI screens content | | AI Mode | Observation | Whether AI detections are only recorded, or block and hold content | | Harm Categories: Harassment & bullying | On | Whether the AI screens for harassment | | Harm Categories: Discrimination | On | Whether the AI screens for discrimination | | Enable negativity detection | Off | Whether the AI scores negativity | | Negativity Tolerance | 50 | How sensitive negativity scoring is | | Which Users / Teams? | All users | Who is screened | | Notify moderators when new items enter the queue | On | In-app and email alerts to moderators | | Notify content authors when their content is approved or rejected | On | Email to the author on a decision | | Hide personal information in AI answers | On | Hides Social Security, card and bank account numbers in AI answers. Emails and phone numbers are hidden when an answer holds three or more of them | ### Content Governance — Admin → General Settings → Content Governance → Settings (per app) | Setting | Default | What it changes | |---|---|---| | Enable automated governance scanning | On for Ask AI, Drive, Forms, Policy Hub, Training, Workspace; off for the others | Whether the weekly scan checks this app | | Review Interval (days) | 90 for Libraries; set by the app elsewhere | How long content may go unchanged before it is due for review | | Expire content after (days) | Blank (never) | Age at which content counts as expired, where the app supports it | | When content expires | Flag it for review | Flag only, or also unpublish it 14 days after it was flagged if still unresolved | | Check broken links | On, where the app offers it | Whether external links are tested | | Notify on governance review | On | Whether owners, teams and reviewers get reminders | | Enable gap analysis | Off | Whether search logs are analysed for missing topics | | Notify on gap summary | On | Whether admins get the gap-analysis digest | | Low → Medium (days) | 30 | When open low findings escalate | | Medium → Critical (days) | 60 | When open medium findings escalate | Each person can also mute the Ask AI reminder in their notification preferences, under **Ask AI unanswered questions**. It is on by default, in-app and by email. The same switch mutes the notice that an answer they wrote wasn't approved. ## 6. More help - **Content Governance FAQ** — specific questions about scans, owners, findings and moderation decisions - **Ask AI Overview** — how Ask AI answers from Verified Knowledge - **Audit Logs & Activity History** — who changed what, including moderation decisions - Ask AI — the assistant answers questions about Content Governance & Moderation from these articles. **Keywords:** content moderation, content governance, moderation queue, flagged content, stale content, broken links, governance findings, content owner, owning team, content I own, reassign content ownership, unanswered questions, expired content, possible duplicate, AI moderation, keyword blocking, gap analysis --- # Contests App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-20 How to set up and run time-boxed competitions — metric-driven, manually scored, photo/story submissions, or pick'em predictions — with team or individual standings and prizes. # Contests ## 1. What it is Contests lets you run time-boxed competitions with a real start date, end date, winner, and prize. Competitions can score automatically from platform activity, accept manually entered numbers, judge photo or story submissions, or run pick'em prediction pools. Contests supports both individual and team structures, with prizes paid as Company Store points, badges, or bragging rights. - **Enablement:** Contests requires a license. An admin enables it from Admin → Apps → All Apps, and it is off by default. - **What it is not:** Contests is the episodic, time-boxed layer of engagement. Ongoing XP and badge earning lives in Levels & Badges. Contests scores *from* that ledger (metric mode) but is a separate app with its own lifecycle. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Contests**. This requires a license. 2. Open **Contests → Admin → Settings**. Set **Who can create contests** — the default is **Admins only**. If you choose **Managers and above** or **Everyone**, those creators' contests wait for approval before going live. **Who can review contest approvals?** on the same page decides who clears them — app admins by default, or managers or a named group. 3. If you use metric-scored contests, confirm that **Levels & Badges** is enabled. Metric contests score from the Levels & Badges activity ledger. Without it, no platform actions are available to score on. 4. For points prizes, go to **Admin → Prize budgets** and create a budget for each manager who will fund prizes. Without a budget, non-admin creators cannot offer points prizes. 5. Confirm it worked: open the **Contests** tab in the app sidebar. You should see the contest dashboard with sections for live, upcoming, and finished contests, plus a template gallery if you can create contests. **Silent dependency:** Metric contests require Levels & Badges to be enabled. If it is off, the scoring-action picker in the contest form shows no actions, and any metric contest created would score zero permanently. ## 3. How it fits together **Scoring modes** — Every contest uses exactly one scoring mode, chosen at creation and locked when the contest goes live: - **Metric** scores automatically from the Levels & Badges activity ledger (XP points or event count). The creator picks which platform actions count — for example, "open shifts picked up" or "training courses completed." - **Manual** tracks numbers entered by hand or CSV — anything the platform doesn't measure automatically, like sales calls or pallets moved. - **Submission** collects photo or story entries (single image, or a before-and-after pair) judged by community votes or a designated judge panel. - **Prediction** runs pick'em pools: the organizer posts questions with options, participants pick, and correct picks earn points. Brackets advance automatically from round results. - **Business metric** (site-metric race) scores location teams on the improvement of a registered business metric compared to the same-length period before the contest window. **Structure** — A contest is either **individual** (each person competes alone) or **team** (grouped by department or location). Individual metric and submission contests are opt-in — nobody is publicly ranked without enrolling. Team contests and individual manual contests auto-enroll the entire audience when the contest goes live. Team contests support per-capita scoring, so a six-person store can compete fairly against a forty-person one. **Goal types** determine how a winner is decided: - **Highest score** — top of the leaderboard wins. - **First to target** — first to reach a number wins. - **Everyone reaches the target** — every team member must hit the target for the team to win. This is the cooperative, works-council-safe goal. - **Share of team reaches the target** — a configurable percentage of team members must hit the target, optionally with a secondary qualifying activity gate. - **Most improved** — scored on the difference between the contest window and a baseline of equal length immediately before it. - **Raffle** — individual only; participation earns tickets, and winners are drawn from the pool. The draw is seeded and audited. *Example: A "Safety Sprint" contest uses metric scoring on the "safety checklist completed" action, team structure grouped by location, with a "first to target" goal of 50 events. Per-capita scoring is on, so a small crew has the same shot as a large one. The prize is 500 Company Store points for the winning team, funded from the safety manager's delegated prize budget.* **Prizes** — Three types: **Company Store points** (deposited into the winner's rewards balance), **badge** (minted onto the winner's badge wall via Levels & Badges), or **bragging rights** (no tangible prize). Prediction contests, raffles and the two shared-goal formats (everyone reaches the target, share of team reaches the target) are restricted to badges or bragging rights — their payout can't be bounded in advance, so points prizes are not available on them. Because works-council mode allows only the shared-goal formats, a tenant using it offers badges or bragging rights only. Employee-created contests can only offer bragging rights. **Rule lock** — When a contest goes live, its scoring contract freezes: structure, scoring mode, goal type, target value, audience, prize type, and time window all become immutable. Corrections after that point go through admin override tools (score adjustments, disqualification, early end), never edits to the locked rules. **Programs and seasons** — A **program** (e.g. "Q4 Safety Cup") is a container that groups related child contests with roll-up standings across them, using either placement-points or summed-scores rollup. A **season** (e.g. "Monthly Pickup Challenge") is a recurring program — it automatically generates a new round on a weekly, biweekly, or monthly cadence from a chosen template. Ending a season stops new rounds; contests already running finish on their own schedule. **Challenges** — Any member can challenge a coworker to a 1v1 duel. Accepting spins up a real two-person contest that rides the full scoring engine. Duels always award bragging rights. Pending duel invitations expire automatically after 14 days if the opponent does not respond. If your organization restricts contests to team mode (works-council setting), duels are disabled. **Approval flow** — Non-admin creators always go through approval. When a manager or employee creates a contest, it enters **Pending approval** and appears in the approval queue of whoever **Who can review contest approvals?** names (app admins can always review). Approving moves it to **Scheduled** (and, for points prizes, locks the budget hold at that moment). Rejecting sends it back to the creator as a draft with the reviewer's reason, so they can revise and resubmit. Nobody can approve a contest they created. **Integrations** — Contests appear on the Comms Hub calendar alongside posts, surveys, and broadcasts, so an engagement campaign reads as one coordinated plan. Contest standings are shown on Digital Signage screens unless switched off. Winners earn participation XP through the Levels & Badges economy, and the Contests Agent in Ask AI lets users check standings, join contests, and make predictions conversationally. ## 4. Running it ### Creating a contest 1. Open **Contests** and click the **New contest** button, or pick a template from the gallery. Templates pre-fill structure, scoring mode, goal, and suggested duration. 2. Fill in the name, time window, audience (company-wide, specific locations, or specific departments), and prize. 3. If you are not an admin, the contest goes to the **Approvals** queue. Admin-created contests go straight to **Scheduled**. 4. Once scheduled, the contest activates automatically at its start time. For team contests, teams are snapshotted from the org structure at activation and membership is frozen for the duration. ### Reviewing approvals Go to **Admin → Approvals**. Each pending contest shows who created it, the prize, and — for points prizes — the creator's remaining budget. Approve to schedule it (the budget hold is taken at this moment) or reject with a reason, which sends it back to the creator as a draft. ### Admin overrides on a live contest Open the contest detail page. Admin tools are available while a contest is live: - **Adjust score** — adds or subtracts points as an audited overlay. The original score is never changed. - **Disqualify / Reinstate** — removes or restores an entrant. Disqualification is immediate; the standings refresh. - **End early** — freezes the contest at the current moment. Activity, manual and prediction contests go straight to the normal completion path (payout, winner announcement); a photo/story contest closes its entries and moves to judging, and finishes when judging does. - **Cancel** — terminates the contest. Any budget hold is released. Every override requires a reason, which is recorded on the audit trail. ### Managing prize budgets Go to **Admin → Prize budgets**. Create a budget by naming a grantee (the manager who will fund prizes), setting an allocated-points amount, and optionally an expiration date. When the grantee's contest is approved, the prize total is reserved from their budget. When the contest completes, the actual payout is confirmed and any remainder is released. ### Announcing a contest and featuring its winners From a contest's page, the creator or an admin can: - **Announce to audience** — while an opt-in contest is upcoming or live, sends one notification to every audience member who hasn't joined yet. It can be sent once. - **Feature winners** — after a contest completes, publishes the winners to the company News Feed as a post (idempotent — safe to click twice). Offered only when **Announce winners to company feed** is on in settings, which is off by default. - Winners automatically receive an in-app notification and an email with their shareable win card. ### Rerunning a finished contest When a completed contest declared a business goal and Loop measured its result, the creator or an admin can launch a rerun from the business-goal panel on its page (**Run it again**). The rerun pre-fills the same format, scoring mode, goal, and declared business goal, but with a fresh time window and no pre-approved budget — the creator reviews everything before saving, and the rerun goes through the normal approval and budget flow. ### Saving a custom template On any contest's detail page, the creator or an admin can click **Save as template**. This captures the contest's format (scoring mode, structure, goal, prize type) as a tenant-scoped custom template in the gallery. The time window, audience, and live state are not copied. ## 5. Settings All settings are under **Contests → Admin → Settings**. | Setting | Default | What it changes | |---|---|---| | Who can create contests | Admins only | Controls who sees the "New contest" button. **Managers and above** adds anyone with the Manager role or direct reports (with approval); **Everyone** adds all members (with approval and bragging-rights prizes only). | | Restrict to team contests with cooperative goals | Off | When on, individual contests and individual ranking are disabled organization-wide. Only team contests with cooperative goals (everyone or a share of the team reaches the target) are allowed. Designed for regions where publicly ranking employees requires works-council consultation. | | Locations restricted to team mode | None | Per-location restriction: contests whose audience includes any of these locations must be cooperative team contests, even when the organization-wide switch is off. | | Send weekly contests digest email | Off | A Monday-morning email with current standings and contests still open to join. It reaches everyone entered in a live contest and everyone in the audience of an open contest they haven't joined yet — not entrants only. A short summary also lands in each person's Inbox, so members with no work email get it too. | | Send rank nudges | On | Notifies entrants when they take the lead, move into or out of a prize place, and in the contest's final hour. Turning it off also stops the final-hour notice. | | Announce winners to company feed | Off | When a contest ends, automatically posts the winners to everyone's News Feed. | | Show contest leaderboards on digital signage | On | Break-room screens show live contest standings, naming the top three. Every screen shows them once Digital Signage is enabled, unless someone switches contest leaderboards off for that screen. | | Enable the Contests Agent in Ask AI | On | Lets users check standings, join contests, and launch templates conversationally through the Ask AI sidebar. | ### Viewing contest history The main dashboard shows the 12 most recent completed contests. For the full archive, click **View all** beside **Recently finished**. Completed and archived contests remain viewable there indefinitely. ## 6. More help - **Contests FAQ** — specific setup and operating questions, limits, and troubleshooting. - Ask AI — the assistant answers questions about Contests from these articles. **Keywords:** contests, competitions, challenges, leaderboard, gamification, prizes, team contest, duel, prediction, pick'em, bracket, submission contest, photo contest, raffle, prize budget, program, season --- # Contests FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-20 Answers to common setup and operating questions about Contests — for the admin running it. # Contests FAQ Answers to common setup and operating questions about Contests. For what the app is and how to set it up from scratch, see the [Contests Overview](/help/articles/contests_app_overview). --- ## Setup ## What do I need to configure before launching the first contest? Enable the app from Admin → Apps → All Apps, then open **Settings** in the Contests sidebar. The most important setting is **Who can create contests** — it defaults to **Admins only**, so managers and employees cannot create contests until you change it. Review the other defaults: real-time rank nudges are on, the weekly digest email is off, contest leaderboards on digital signage are on, and the Contests Agent in Ask AI is on. None of these block launching a contest, but they shape the experience employees get from the start. ## Who can create contests, and can I let managers or employees do it? The **Who can create contests** setting in Contests Settings has three options: **Admins only** (the default), **Managers and above**, and **Everyone**. Each tier adds constraints: 1. **Admins** can target any audience, award any prize type, and their contests go live without approval. 2. **Managers** can target only locations or departments they belong to, choose any prize type (points require a prize budget you granted them), and their contests require approval before going live. 3. **Employees** can target only locations or departments they belong to, can only offer bragging-rights prizes, and their contests also require approval. --- ## Permissions and access ## Why can't some managers see the Templates tab or the Create button? The Templates tab appears only for users who can create contests. If the **Who can create contests** setting is still at the default **Admins only**, managers and employees see the Contests, Programs, and My Wins tabs but not Templates. Change the setting to **Managers and above** or **Everyone** to open creation to those tiers. ## What does "Restrict to team contests with cooperative goals" do? This is the works-council mode. When enabled, every contest in the business must be a team contest with a cooperative goal — nobody is individually ranked. Individual contests, head-to-head duels, and competitive team goals are all blocked at creation time, including through the AI agent. You can also restrict specific locations instead of the whole business using the **Locations Restricted to Team Mode** setting: any contest whose audience overlaps a restricted location is forced to the same cooperative-team format. --- ## Day-to-day ## How are standings calculated — can people game the scores? Metric contests score automatically from the same verified activity ledger that powers Levels & Badges. The platform records the underlying action (a shift completed, an inspection done, a course finished), and the standings job recomputes every active contest's leaderboard every five minutes from that ledger. Nobody can type in a metric score; the only manual change is an admin's audited score adjustment (below), which shows on the audit trail with its reason. Manual contests score from figures an admin or the contest creator posts — one participant at a time or by CSV import. Submission contests are decided by community votes or a judge panel. ## Can I run a contest on numbers the platform doesn't track, like sales or steps? Yes. When you create a contest, choose the **Manual** scoring mode. While the contest is live, an admin or the contest's creator can post scores for enrolled participants — one at a time or by uploading a CSV of participant and value. Scores are additive: each entry adds to the participant's running total, so you can post daily or weekly numbers and let the total accumulate. You can also set a display unit (for example "$" or "steps") so the leaderboard labels the numbers correctly. ## What happens when a contest ends — how are winners determined and paid? When the contest window closes, the final standings snapshot freezes and the payout runs automatically. For points prizes, the prize table pays out by rank and the points land in each winner's Company Store balance. For badge prizes, the winner's badge is minted onto their Levels & Badges wall. Winners receive an in-app notification and an email with a shareable win card. Non-winners receive a "results are in" notification with their final rank. For cooperative goals (everyone reaches the target), every entrant who cleared the bar wins the same prize rather than being ranked. For raffles, winners are drawn from the ticket pool at the end, weighted by participation. ## How do I correct a score or disqualify someone from a live contest? Open the contest, then use the admin override controls. You can adjust a score (append-only — the original is never changed), disqualify an entrant, or reinstate a previously disqualified one. Every override requires a written reason and creates an audit entry. Score adjustments are folded into standings on the next five-minute refresh. Adjustments are only available while the contest is live — after completion, the payout has already ranked and paid the frozen board. ## How do prize budgets control what managers can spend? A prize budget is a points allowance an admin grants to a specific manager. That manager can then fund contest prizes only from what you granted. When the contest is approved, the full prize table is reserved against the budget; only what is actually paid at the end is deducted, and the remainder is released. You can revoke a budget with a reason or set an expiration date. Budgets that pass their expiration are automatically marked expired by the nightly sweep. Admins can create and award prizes without a budget. ## Can I end a contest early or cancel it? Yes. An admin can end a live contest early or cancel it at any stage before completion, and a contest's creator can withdraw (cancel) their own contest while it is a draft, waiting for approval, or scheduled but not started. Both require a written reason and create an audit entry. Ending early freezes the current standings, runs a final refresh, and pays out the prizes based on rankings at that moment — except a photo/story contest, where it closes entries and moves the contest to judging. Cancelling releases any reserved prize-budget hold and no prizes are awarded. ## What notifications do employees and admins receive? **In-app notifications** fire for: contest started, rank changes (took the lead, into/out of the prize ranks), the final hour before a contest ends, contest completed with results, and prediction-pick lock reminders. Judges get a notification when the judging window opens and a reminder 24 hours before it closes. Whoever reviews contest approvals — app admins by default, or the managers or group set under **Who can review contest approvals?** — gets an approval request when a non-admin submits a contest, and the creator is notified when it is approved or sent back. **Email** is limited to two messages: the winner award email (with an inline win card image) and an optional weekly digest summarizing active contests and open ones you can join. The weekly digest is off by default — enable it in Settings under **Send weekly contests digest email**. It reaches everyone entered in a live contest and everyone in the audience of an open contest they haven't joined, and leaves a short summary in their Inbox so members without a work email get it too. Rank nudges (took the lead, into/out of prizes, and the final-hour notice) are on by default. You can turn them off in Settings under **Send rank nudges** — that also stops the final-hour notice. --- ## When something looks wrong ## "I can't join this contest" — why would the Join button be blocked? Several things can block joining. The contest is not in your audience (it targets a specific location or department you don't belong to). The contest is a team contest, which enrolls everyone in the audience automatically — there is no Join button, except a **Rejoin** for someone who left while it is still running. The contest is a manual-scoring contest, which also auto-enrolls the audience when it starts. You are a manager and the contest has **Managers can't compete against their own reports** on (the default), which prevents managers from competing against their own direct reports. You created the contest — the person who sets a contest up runs it rather than competing in it (a 1:1 challenge you sent is the exception: you are one of its two players). Or you were previously disqualified by an admin, which is not cleared by trying to rejoin. ## "I didn't get any notification about this contest" — what happened? Contest-started notifications go only to people already enrolled at the moment the contest goes live. For individual contests (not manual), enrollment is opt-in — a new contest exists but you are not enrolled until you join. An admin or the contest creator can send a one-time "announce to audience" notification to everyone in the audience who hasn't joined yet, which surfaces the contest and a link to join. Team and manual contests auto-enroll the whole audience at activation, so those participants do get the started notification immediately. ## "My score hasn't changed even though I kept working" — why? Standings refresh every five minutes, so there is a short delay between doing the work and seeing it on the board. If it has been longer than that, check which scoring actions the contest tracks — only the specific activity types selected when the contest was created count toward the score. Also confirm you are still actively enrolled (not withdrawn or disqualified). For most-improved contests, your score is measured against your own pre-contest baseline, so improvement is relative to your starting point, not an absolute total. ## The prediction contest won't let me set points as the prize — why? Prediction contests (pick'em pools and brackets) are restricted to **badges** or **bragging rights** prizes. Points prizes are not available on pick-the-winner formats. This is a platform-wide rule, not a per-tenant setting — it applies to every prediction contest regardless of who creates it. ## The judging window closed and no one was declared a winner — what happened? If a judge-panel contest completes with zero judge scores submitted, no prizes are awarded. The system holds the contest in judging for 48 hours past the judging deadline as a grace period for the panel to score, sending escalation notifications to the judges and the app admins. After the grace period, it completes with no winners, releases any reserved prize-budget hold, and notifies the creator and admins that the payout was blocked. Entrants still receive participation credit. --- ## Licensing and limits ## Does Contests require a licence? Yes. Contests is a licensed marketplace app. It ships disabled by default — an admin enables it per tenant from Admin → Apps → All Apps. ## What are the limits I should know about? - **Templates:** 32 out-of-the-box system templates across six categories (engagement, safety, learning, culture, operations, seasonal), plus any custom templates your organization saves. - **Contest name:** up to 160 characters. - **Contest duration:** up to 365 days. - **Standings refresh:** every 5 minutes for active contests. - **Default judging window:** 3 days after the contest ends (for submission contests). Judges get a reminder 24 hours before it closes and a 48-hour grace hold if nobody scores. - **Duel duration:** up to 30 days. A pending duel invite expires after 14 days if the opponent doesn't respond. - **Raffle ticket cap:** 10 entries per person by default (configurable per contest). - **Score adjustments:** each adjustment must be under 10 billion. - **Prize types:** Company Store points, a badge, or bragging rights. Prediction contests, raffles and the shared-goal formats (everyone or a share of the team reaches the target) are limited to badges or bragging rights. - **Scoring modes:** metric (automatic from platform activity), manual (external numbers), submission (photo/story with votes or judges), prediction (pick'em and brackets), and site-metric (location teams racing on a business number). - **Goal types:** highest score, first to target, everyone reaches the target, most improved, raffle draw, and share-of-team threshold. --- ## More help - [Contests Overview](/help/articles/contests_app_overview) - Ask AI — the Contests Agent answers questions about running contests, standings, and your rank from these articles. **Keywords:** faq, contest, competition, leaderboard, prizes, scoring, templates, duels, predictions, brackets, prize budgets, works-council mode, team contests, standings, contests --- # Contracts App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How Contracts works — filing and importing contracts, AI review, negotiation, approvals, signing, renewals, obligations, vendors and service delivery — with the setup path and every setting's default. # Contracts ## 1. What it is Contracts keeps every agreement your organization signs — with vendors you buy from and customers you sell to — from the first draft to renewal or exit. It files the contract, reads it with AI, routes it for approval and signature, and then tracks what happens under it: obligations, renewals, spend, and the service actually delivered. - **Enablement:** Contracts is a licensed app. An admin turns it on from **Admin → Apps → All Apps**, then configures it at **Contracts → Settings**. - **What it is not:** Contracts is not a document editor. You write and redline contracts in Word, then upload them, start them from one of your standard contracts, or have a first draft made from a drafting form. ## 2. Standing it up Admins and Contracts app admins see a setup checklist on the Contracts dashboard. It covers standard contracts, approvers, bringing in contracts, the renewal calendar and a first approval, and ticks each step off as it happens. 1. Go to **Contracts → Settings → General**. Choose who you usually contract with under **Most of our contracts are with**: **Vendors we buy from** (the default), **Customers we sell to**, or **An even mix — ask every time**. Add every name you sign as under **Legal entity names we sign contracts as**, so the AI can tell which side of a contract you are on. 2. Still on **General**, decide **Who can create contracts?** The default is **Managers and admins**. Admins, Contracts app admins and contributors, and contract coordinators can always create contracts. 3. Add your standard contracts under **Standard Contracts** in the app's menu (Drafting & Signature) — the NDA, MSA and order form you send, as Word or PDF files. 4. Go to **Settings → Approvals** and decide who approves. With **Require approval for new contracts** on (the default), a submitted contract goes to the **Default approver roles** (Admin and Super Admin by default), or to a multi-level workflow you build under **Manage workflows**. 5. Bring in your existing contracts. **New Contract** files one at a time; **Bulk Upload**, in the actions menu on the contracts list, takes a whole binder at once. Bulk upload needs **AI contract analysis** switched on. 6. Open **Renewal calendar** from the same actions menu, or **Add renewals to your calendar** on any contract, and subscribe, so renewals and notice deadlines reach your own calendar. 7. Confirm it worked: file one contract, submit it, and approve it. Your managers should now see **New Contract** on the dashboard. **Things that do nothing until a second thing is set:** - **Built-in signing** needs the E-Signature app turned on. **DocuSign** or **HelloSign** needs an active integration at **Admin → Organization → Integrations**. Until one exists, the provider list on **Settings → Integrations** is empty. - **Obligations become tasks** only when the Tasks app is turned on. - **Signability verdicts** need at least one playbook rule with an ideal clause or a walk-away line. Until then, the playbook only checks whether each required clause is present. - **Delivered vs contracted** needs Safety Hub (hours and visits, read from work permits as an upper bound) or Service Desk (resolution times) for vendor contracts, and a linked Field Service agreement for customer contracts. - **Renewal reminders** count back from the contract's notice deadline, or from its end date when it has no notice date or period. ## 3. How it fits together **Vendor side and customer side.** Every contract is either with a vendor (you buy) or a customer (you sell). Vendors are the same records Procurement and Supplier Hub use; customers are the same accounts Mango GTM and Mango CS use. The **Customers** tab appears when your usual side is not vendors, or once any customer contract exists. **Status.** A contract is **Draft**, **Pending approval**, **Active**, **Expiring**, **Expired**, **Terminated** or **Renewed**. Active, Expiring and Expired follow the dates on their own: a nightly check moves a contract to Expiring when it enters the expiration-warning window, and to Expired after its end date. The other statuses change only when someone acts. **Owner, uploader and manager.** The uploader filed the contract and never changes. The owner is responsible for it from then on; admins and Contracts app admins can transfer ownership, and when someone is offboarded their contracts pass to their manager. A **contract manager** — the owner, the uploader, an admin, a Contracts app admin or a contract coordinator — can edit, submit, renew, amend and send the contract for signature. **Contract coordinator.** A coordinator (Settings → General → **Who can manage every contract?**) sees and edits every contract, files for any location, and decides value-tier approvals — without access to Settings. By default only app admins hold this. **AI analysis and the allowance.** With **AI contract analysis** on, a contract filed from **New Contract** gets an AI summary, a risk explanation and a risk score from 0 to 100 on its own. A bulk import does the same on commit unless **Summarize and risk-score each contract as it is filed** is switched off on the review grid. Each AI run counts against the contract's allowance — 3 runs per rolling 12 months by default. Admins and Contracts app admins are not limited. **Version, amendment and renewal.** These are easy to mix up: - A **version** is a new file on the same contract — a counterparty's redline, your next draft, a supporting document. - An **amendment** is a recorded change to value, dates, vendor or customer, payment terms or scope. Once approved, it updates the contract. - A **renewal** creates a new contract for the next term, with the same locations. The original becomes **Renewed**. Nothing renews automatically; someone clicks **Renew contract**. **Redlines and the playbook.** When a new draft replaces the contract file — uploaded by you, by the counterparty through their link, or emailed back to the contract's reply address — the AI compares it with the previous version. Each change becomes a redline, rated for impact and severity, with a suggested response of accept, counter or reject. Your **Negotiation Playbook** holds, per clause type, the ideal clause, fallback positions with the approver each needs, and the walk-away line. **Obligations.** An obligation is something owed under a signed contract — a quarterly report, an insurance renewal. It is **One-time**, **Recurring** or **Milestone**. Completing a recurring one creates the next. With the Tasks app on, each obligation on a live contract is also a task for its owner. Owners are reminded only while the contract is live (a draft, in approval, active or expiring); renewing a contract moves its open obligations to the new term unless the renewer unticks that box. **Services contracts and certificates.** On service, maintenance, support, SOW and consulting contracts, a **Service delivery** card compares confirmed targets with what was delivered over the last three complete months. Vendor certificates (SOC 2, COI, W-9, security audit, insurance) live in a shared register that Safety Hub also reads before a contractor's work permit is issued. _Example:_ A facilities team files a two-year cleaning **service agreement** with Brightway Services, worth $96,000 a year, as **CTR-00042**. The AI scores it 38 (Medium). The value is below the $100,000 legal-review threshold, so it goes to the default approvers and is approved. The owner confirms two targets on the Service delivery card: 173 hours on site and 20 visits a month (the contract says "40 hours per week"). In March, Brightway's COI lapses; the day before their next permitted visit, Safety Hub sends an Inbox ask, and the permit can only be issued with a recorded reason. Ninety days before the notice deadline, the owner is reminded and opens the renewal decision packet. ## 4. Running it ### Approving contracts 1. Open **My Work → Approvals** (the badge shows what is waiting on you). 2. Open a contract, read the AI summary and risk score, and choose **Approve** or **Reject**. A rejection needs a reason and returns the contract to Draft. 3. Approvers can also decide from the approval email. The link opens a confirmation page first; nothing is decided by opening the email. 4. Going on leave? Choose **Delegate my approvals** on the Approvals page, or ask Ask AI, to hand your approvals to a colleague for a date range. Under central review, agreements go to the next approver in line while you're away instead. ### Negotiating with a counterparty 1. On a draft, the negotiation card gives you **Download to send**, a copyable email, and the counterparty's no-login link. 2. When their redline comes back, open **Redlines** and accept, counter or reject each change — on desktop or on the phone. 3. Ask AI can check signability — whether the contract can be signed as-is, with named approvals, or not at all. ### Sending for signature 1. Open the contract and choose **Place Signature Fields**, then add signers in the order they sign. 2. Choose **Send for E-Signature**. Unsigned contracts are chased on the cadence you set in Notifications. 3. For a paper signature, use **Mark as signed**. On a contract out for e-signature, that cancels the open signing request and tells its signers. A signed draft that needs approval is submitted for approval straight away; a contract that still needs approval stays pending until its approvals complete, then goes live. ### Deciding renewals Owners are reminded ahead of the notice deadline. The **Renewal decision** page shows spend under the contract, open Service Desk tickets with the vendor, linked assets, the vendor scorecard and open obligations, with a suggestion to renew, renegotiate or exit. **Record decision** logs the choice, and the contract page shows it under Contract Details; renewing is a separate **Renew contract** action. On a contract that does not auto-renew, recording **Exit** stops the expiring-soon warnings for that term, and when it ends the expired notice becomes a plain note that it ended as planned. On one that auto-renews, recording Exit gives no notice to the other side: the owner is reminded to give notice by the notice deadline, and the expiring-soon warnings continue. ### Importing a batch Choose **Bulk Upload**, add files, a ZIP or a folder, and pick the side and signed state. On the review grid, filter by folder, fix vendor, type, dates, owner or location for many rows at once (every change is previewed and can be undone), then **Commit**. ### Telling other systems Contracts sends an event when something happens to a contract, so your ERP, finance system or an integration tool can act without anyone re-keying it: | Event | When | |---|---| | `contract.signed` | A signature is recorded — also while approval is still outstanding | | `contract.activated` | A contract goes into force: approved, auto-approved, signed with nothing outstanding, or an expired one given a later end date — the event says which | | `contract.renewed` | Someone renews a contract (the event names the new term) | | `contract.terminated` | A contract in force is terminated | | `contract.expired` | A contract in force passes its end date | | `contract.renewal_due` | A contract's notice deadline (or its end date, when it has none) comes inside the renewal-reminder window — once per term, and again when the contract is extended into a new term (a deadline whose reminder window starts after the previous deadline); corrections to dates inside the current term don't send it again | | `contract.obligation_due` | An open obligation reaches its due date, or is added or moved to today | | `contract.approval_reversed` | Someone reverses an automatic approval made by a learned approval pattern | An admin subscribes a webhook to them under **Admin → Webhooks**, or builds an **Automation Hub** rule on them — the **Contract Signed → Tell Finance** template sends a person you choose an Inbox note with the contract's summary. Each event carries the contract's number, title, type, counterparty, owner, location, status, value, currency and dates, never its description, notes, termination reason or AI summary. Events cover every contract in the organization, including contracts limited to certain locations; a rule can filter on `community_id`, the contract's primary location. Filing contracts by an import or a bulk upload sends nothing, but each contract's later events are sent like any other's; sample data never sends events. The app's own **Workflow Triggers** fire on the same events and take the same conditions. ## 5. Settings All settings are at **Contracts → Settings**, in nine tabs. | Setting | Where | Default | What it changes | |---|---|---|---| | Auto-generate contract numbers | General | On | Numbers new contracts in sequence. Off, **New Contract** and Edit ask for the number; contracts filed any other way are still numbered | | Contract number prefix | General | CTR | Gives numbers like CTR-00001 | | Most of our contracts are with | General | Vendors we buy from | Which side new contract forms open on | | Who can create contracts? | General | Managers and admins | Who sees New Contract and Bulk Upload | | Who can manage every contract? | General | App admins | Grants the contract coordinator role | | Who can view contract spend? | General | Everyone with access to the app | Who sees the Spend page and figures | | Who can export the register? | General | Managers and admins | Who can export the register and the due-diligence bundle | | Who can view portfolio analytics? | General | App admins | Who sees Analytics | | Who can see negotiation positions? | General | App admins | Who sees the playbook's fallbacks and walk-away lines | | Require approval for new contracts | Approvals | On | Contracts must be approved before they go active | | Default approver roles | Approvals | Admin, Super Admin | Who approves when no workflow matches | | Require legal review at or above (USD) | Approvals | 100,000 | Adds one legal-review approval at or above this value, with or without a workflow — after the last level when a workflow routes the contract | | Legal reviewers | Approvals | None (any admin) | Who can give the legal-review approval; one approval from this group is enough | | Auto-approve below (USD) | Approvals | 0 (off) | Approves smaller contracts without a person | | Allow approval delegation | Approvals | On | Lets approvers hand their approvals to a colleague | | Require all approvers | Approvals | Off | Every assigned approver must approve | | Escalate overdue approvals | Approvals | Off | Alerts admins about stalled approvals | | Escalate after | Approvals | 7 days | How long before an approval counts as overdue | | Remind before escalating | Approvals | 24 hours | When the approver gets a reminder | | Renewal reminder | Renewals & Lifecycle | 90 days | How far before the notice deadline (or the end date when there is none) the owner is reminded | | Expiration warning | Renewals & Lifecycle | 30 days | When a contract turns Expiring and warnings start | | Allow amendments | Renewals & Lifecycle | On | Lets contract managers record amendments | | Amendments need approval | Renewals & Lifecycle | On | Every amendment must be approved | | Allow early termination | Renewals & Lifecycle | On | Allows ending an active or expiring contract early | | Score contract risk with AI | Compliance & Risk | On | Whether the AI produces a risk score | | Flag high-risk contracts | Compliance & Risk | On | Marks contracts that reach the risk level below | | Flag contracts at or above | Compliance & Risk | High | The level that triggers the flag | | Prevent deletion of active contracts | Compliance & Risk | On | Blocks deleting in-force contracts | | Restrict contracts with no location to administrators | Compliance & Risk | Off | Hides unassigned contracts from non-admins | | Re-verify identity before contract file downloads | Compliance & Risk | Off | Asks for re-verification before a file downloads | | AI contract analysis | AI & Agent | On | Turns AI analysis, redline comparison and drafting on or off | | AI runs allowed per contract in any 12 months | AI & Agent | 3 | The per-contract AI allowance | | Enable Contracts Agent | AI & Agent | On | Contracts in Ask AI | | Enable Contracts Admin Agent | AI & Agent | On | Portfolio search and spend questions for admins | | Send a weekly digest | Notifications | Off | Monday email of what needs attention | | Chase unsigned contracts every | Notifications | 7 days | Signature follow-up cadence | | Send contracts out for signature | Integrations | On | Turns e-signature on | | Default provider | Integrations | Native (Built-in) | Which signing service is used | | Track contract spend | Integrations | On | Turns on the Spend page | | Require payment terms | Integrations | Off | Makes payment terms required on new contracts | The **Notifications** tab also has one switch per notification — approval requests, approval decisions, expiring soon, expired, renewal decision needed, obligation reminders, counterparty activity, signature follow-ups and vendor certificate expiry are on; contract created is off. **Rules & Libraries** holds Workflow Triggers, Custom Fields, Drafting Forms, Vendor Certifications, Contract Types and Form Templates, plus **Manage workflows** for multi-level approvals. **Standard Contracts** and the **Negotiation Playbook** are in the app's menu, under Drafting & Signature. A workflow trigger runs on a contract event (signed, terminated, renewed or renewal due) when every one of its conditions matches — the same conditions an Automation Hub rule takes, such as contract type, contract value at least an amount (on a renewal, the new term's value), counterparty side, primary location, status, auto-renews or currency. A **Disable vendor** trigger runs only when a contract is terminated. Sample data adds three example triggers, switched off: they never run and can't be switched on — create your own trigger to automate your contracts. ## 6. More help - **Contracts FAQ** — limits, ranges, permissions and what to do when something looks wrong - Ask AI — the assistant answers questions about Contracts from these articles. **Keywords:** contracts, contract management, contract lifecycle, approval workflow, approval delegation, e-signature, renewal decision, renewal calendar, negotiation playbook, redlines, obligations, vendor certificates, vendor scorecard, service delivery, purchase order coverage, contract coordinator, bulk import, webhooks, contract events, automation rules --- # Contracts FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common questions about Contracts — for the employees, managers and admins who use it: filing, AI analysis, approvals, negotiation, renewals, obligations, service delivery, limits and troubleshooting. # Contracts FAQ Answers to common questions about Contracts, for the people who file, approve and run contracts. For what the app is and how to set it up from scratch, see the [Contracts Overview](/help/articles/contracts_app_overview). --- ## Setup ## Do I need to configure anything before my team can start filing contracts? Turn the app on from Admin → Apps → All Apps, then check three things in **Contracts → Settings**. Decide **Who can create contracts?** on the General tab (the default is managers and admins). Confirm who approves on the Approvals tab. For signing, turn on the E-Signature app or connect DocuSign or HelloSign at **Admin → Organization → Integrations** — until one of those exists, there is no provider to send with. ## Who can see a contract once it is filed? Admins and Contracts app admins see every contract, and so do contract coordinators. Everyone else sees contracts at the locations they can access, plus contracts they own or uploaded, contracts waiting for their approval, and contracts they owe an open obligation under. A contract with no location is visible to anyone with access to a location, unless **Restrict contracts with no location to administrators** is on. ## Does each person need a Contracts licence? No, not by default. Contracts is licensed and turned on for the whole organization by an admin. Once it is on, people reach it the same way as other apps in your workspace, unless your admin limits it to certain groups. --- ## Permissions and access ## Why can't I see the New Contract button? You see **New Contract** if you are allowed to create contracts, or if your admin has published at least one drafting form. People who can only use a drafting form get **I need one drafted**: you answer the questions and a first draft is made for the contract's owner to finish. To upload a contract yourself, ask an admin to add you under **Who can create contracts?** ## What can a contract coordinator do that an ordinary manager can't? A coordinator can see and edit every contract, file contracts for any location, and approve or reject contracts routed by value tier. A coordinator cannot open Settings, terminate a contract, transfer ownership or build approval workflows. A contract on an approval workflow is still decided by that workflow's approvers. Admins grant the role under **Settings → General → Who can manage every contract?** ## How do I change who approves contracts? Open **Settings → Approvals**. **Default approver roles** (Admin and Super Admin by default) decide contracts that no workflow matches. To route by amount, choose **Manage workflows** and build up to 10 levels; a workflow is picked by the contract's value, and each level can take approvers from a role, named people, a department or a location. The person who submitted a contract is never routed to approve it. When an approver leaves or is deactivated, the approvals waiting on them pass to the next approver the routing finds, or else to one of the workspace's admins; if there is nobody, a Contracts admin can decide the approval in their place. The contract's owner is told. An amendment is approved or rejected by an approver other than the person who requested it, unless nobody else can decide it, and until it is decided its requester can withdraw it from the contract's **Amendments** tab; the approvers who were asked get an in-app notice while approval-request notifications are on. ## I'm going on leave — how do I hand off my contract approvals? Open **Approvals** and choose **Delegate my approvals**, or ask Ask AI to do it. Pick a colleague and a start and end date. Contracts submitted in that window go to your colleague, who can also decide anything already waiting on you, and the record shows they decided on your behalf. Under central review, agreements go to the next approver in line while you're away; your colleague doesn't take your seat. Delegation needs **Allow approval delegation** on (it is on by default). It is open to approvers who can decide the approval queue and to anyone with a contract waiting on their approval, and your colleague must be able to approve contracts too. --- ## Day-to-day ## Why doesn't my contract have an AI summary or risk score? Automatic analysis runs for contracts filed from **New Contract** and for bulk imports committed with **Summarize and risk-score each contract as it is filed** on. A new version, an emailed file, or a contract started from a standard is not analyzed automatically — a contract manager can choose **Analyze with AI**. The contract page says why there is no score: still analyzing, allowance reached, AI off, AI unavailable, or needs attention (the run did not finish within about 20 minutes; retry it). ## What do the risk levels mean, and when is a contract flagged? The AI scores risk from 0 to 100: **Low** is 0–30, **Medium** 31–60, **High** 61–80 and **Critical** 81–100. Flagging is on by default. With **Flag high-risk contracts** on, a contract that scores at or above **Flag contracts at or above** (default **High**) shows a review banner. A flag sends no notification. With **Score contract risk with AI** off, no score is produced or shown. ## How many AI runs does a contract get? Each contract gets 3 AI runs per rolling 12 months by default; admins can set 1 to 100 under **AI runs allowed per contract in any 12 months**. A full analysis, a playbook scan, a smart-field extraction, a text read (OCR), a version comparison (a new version uploaded on the web or saved from Word) and an AI answer about one contract each use one run. A playbook scan with no rules for that contract type uses none. Admins and Contracts app admins are not limited. ## Does anything renew automatically? No. Ticking auto-renew on a contract describes the paper: it sets the notice deadline and projects lifetime value. The renewal is always someone clicking **Renew contract**, which creates the next term as a new contract. **Renew contract** is available when the contract is Active, Expiring or Expired and ends within 6 months. The new term keeps the contract's locations; the file and links are not copied. The Renew dialog moves the contract's open obligations to the new term — keeping their owners, due dates and tasks — unless you untick **Move open obligations to the new term**. Obligations left on the renewed term leave their owners' task lists and get no more reminders. ## When are renewal and expiry reminders sent? The owner gets a **Renewal decision needed** reminder every 14 days from the renewal-reminder window (default 90 days) before the notice deadline, until a decision is recorded. A contract with no notice date or notice period counts the window back from its end date instead, until the expiring-soon warnings take over. **Expiring soon** warnings go every 7 days inside the expiration-warning window (default 30 days) before the end date, and **Expired** goes once. Once the owner records **Exit** for a term that does not auto-renew, the expiring-soon warnings stop, and the expired notice becomes a plain note that the contract ended as planned. On an auto-renewing contract, recording Exit gives no notice to the other side, so the owner is reminded to give notice by the notice deadline — when the reminder window opens, two weeks before, and three days before — and the expiring-soon warnings continue. The contracts team also gets a weekly in-app summary of contracts ending within 30 and 60 days. ## I got a task for a contract obligation — what do I do? Do the work, then complete the task in Tasks or on the contract's **Obligations** tab; completing either side completes both. If the obligation repeats, the next one appears with its new due date. You get reminders 7 days and 1 day before, on the due date, and once the day after if it is still open, while the contract is live — a draft, in approval, active or expiring. Once the contract has expired, been terminated or renewed, its open obligations leave your task list and the reminders stop. Only the obligation's owner or a contract manager can complete it. ## How do I send a draft to the other side for their redline? On the draft, use **Download to send** and **Write the email** on the negotiation card. The email carries the contract's reply address and asks them to reply with their redline. They can also use the no-login counterparty link to view, download, upload a revised draft and comment. When their draft arrives and AI is on, the AI compares it with your version, and you accept, counter or reject each change on the **Redlines** tab or on the phone. ## Why did the counterparty's link stop working? A counterparty link lasts 30 days by default (you can choose 1–90), and **Extend** keeps the same link working longer. The link also changes every time the counterparty uploads a file through it, so older copies stop working — send the new one. Uploads and comments stop once the contract has expired or been terminated, and a revoked link never works again. ## How does delivered versus contracted work on a services contract? The **Service delivery** card appears on service, maintenance, support, SOW and consulting contracts, on vendor and customer agreements, and on any contract with a confirmed target, a service term the AI read, or a linked Field Service agreement. A contract manager confirms each target — hours on site and visits per month, resolution time per ticket — typed in or accepted from the AI's reading of the contract. For a vendor, Safety Hub work permits give the most time the contractor could have been on site: a month is **Under target** only when even that falls short, and otherwise reads **Can't confirm from permits**. A vendor with no issued permits in the months shown reads **Not measured**, and a month with none, beside months that have some, reads **No permits issued this month** — not every visit needs a permit, so it shows no shortfall. Resolution time comes from Service Desk tickets about the vendor, opened to resolved. Response time can't be set as a target, because Service Desk records when your desk replies, not when the vendor does. For a customer, hours and visits come from the linked Field Service agreement's work orders. Counts cover only the contract's term and, when it names any, its sites. **Mark reviewed** records that a month was checked, with an optional note; it claims no credit, and a month with nothing measured cannot be marked. ## Why can't I issue a work permit for a contractor? A certificate the contractor needs for site work — such as their certificate of insurance — has lapsed, runs out before the work ends, was denied, or was never provided. Certificates of insurance count by default; tick **Required for site work** on any other certificate that should. To issue anyway, tick **Proceed anyway** and give a reason; the reason is kept on the permit. The day before the work starts, Safety Hub also sends an Inbox ask about the same gap. A current insurance expiry on the contractor's Safety Hub pre-qualification also counts as insurance on file. When a vendor renews a certificate, link the renewal with **Replaces** (on the certificate form, or **Renews** when you review a vendor upload) so the old one stops counting; a renewal with the same title is matched on its own, and cover that runs back to back counts as continuous. Update the certificate under **Contracts → Settings → Rules & Libraries → Vendor Certifications**, or ask the vendor to upload a new one. ## Does my purchase request show whether a contract covers it? Yes, once you choose a vendor. The requisition and the purchase order show which contract covers it and how much ceiling remains, **Not under a contract**, or **Exceeds contract ceiling by** the amount over. If you cannot open that contract or see contract spend, you see only **Covered by a contract** or **Not under a contract**, without amounts. It never blocks the purchase. ## Can our ERP or finance team hear when a contract is signed? Yes. Contracts sends events — `contract.signed`, `contract.activated`, `contract.renewed`, `contract.terminated`, `contract.expired`, `contract.renewal_due`, `contract.obligation_due` and `contract.approval_reversed` (an automatic approval by a learned pattern was reversed). An admin points a webhook at them under **Admin → Webhooks**, or builds an Automation Hub rule; the **Contract Signed → Tell Finance** template sends a person you choose an Inbox note with the contract's summary. Each event carries the contract's number, title, type, counterparty, owner, location, status, value, currency and dates, never its text or notes. `contract.activated` also says what put the contract into force — approval, the auto-approve limit, a learned pattern, a signature or a reactivation. `contract.renewal_due` is sent once per term, when the notice deadline (or the end date, when there is none) comes inside the renewal-reminder window. Extending the same contract into a new term — a later end date or an approved amendment whose deadline's reminder window starts after the previous deadline — sends it again for the new deadline, as a renewal does, and runs the renewal-due workflow triggers again; corrections to dates inside the current term, including a changed notice date or notice period, don't. Webhooks receive every contract in the organization, including ones limited to certain locations, so filter by `community_id` in a rule if a location's contracts should stay out. Filing contracts by an import or a bulk upload sends nothing, but each contract's later events are sent like any other's; sample data never sends events. --- ## When something looks wrong ## Why can't I see a contract I know exists? Contracts are shown by location. If the contract's locations are not ones you can access, you will not see it unless you own it, uploaded it, must approve it, or owe an obligation under it. Ask an admin to add the right location to the contract or transfer ownership to you. ## I submitted a contract and nothing happened — why? Check the approval setup. If **Require approval for new contracts** is off, or the value is below **Auto-approve below**, the contract goes active without an approval. Otherwise someone must hold one of the **Default approver roles**, or the matching workflow's levels must resolve to at least one person — a level with nobody in it stalls. Approvers get an email and an in-app notice. Sent the wrong version? Withdraw it from approval from the contract's Actions menu (or the phone) — it goes back to draft, and the approvers get an in-app notice while approval-request notifications are on. ## Why was this contract approved automatically? Either its value is below **Auto-approve below** (Settings → Approvals, in USD — a value in another currency is converted first, and one with no exchange rate always goes to an approver), or it matched a **learned approval** a Contracts admin accepted. Muscle Memory proposes one when people here have approved at least three contracts of the same type from the same vendor, in the same currency, with none rejected in three years — a contract counts once its approval was completed, at the value it was approved at; it appears under **Settings → Approvals → Learned approvals**, and nothing is automatic until an admin accepts it (the record is checked again when they do). A matching contract up to the highest value in that record is then approved without asking anyone, and the owner and the usual approvers are told in the app and by email. Any of them can choose **Reverse** on the contract within 30 days, unless it has been e-signed: it goes back to awaiting approval (through your approval workflow if one now covers it), the pattern pauses, and you are told anything that already ran when it was activated, since reversing does not undo it. A pattern is never used on a contract an approval workflow covers, at or above the legal-review threshold, on one rated high risk, flagged for attention, already e-signed or rejected by a person before, while its AI analysis is still running or after it failed, or while automation or Muscle Memory is paused. It pauses itself when a person rejects a contract it would have approved, and can only be resumed while the record still holds. It expires after 12 months; if Muscle Memory still proposes it then, an admin can accept it for another 12 months. ## Why is Bulk Upload missing or refused? Bulk upload reads every file with AI, so it needs **AI contract analysis** on under **Settings → AI & Agent**, and you must be allowed to create contracts. A batch holds at most 500 contracts; a larger one is refused whole, and nothing is filed. Files that are not PDF, DOC or DOCX, or are over 50 MB, are listed and skipped. ## Why does it ask me to verify my identity before I can download a contract file? Your admin has turned on **Re-verify identity before contract file downloads**. Re-enter your password or PIN when asked; the verification lasts 15 minutes. --- ## Licensing and limits ## What are the file, import and AI limits? | Limit | Value | |---|---| | Contract file types | PDF, DOC, DOCX | | Contract file size | 50 MB | | Bulk upload | 500 contracts per batch (a ZIP or folder counts by the contracts in it) | | Attachments on one email-in message | 10 | | AI runs per contract | 3 per rolling 12 months by default (1–100) | | Smart fields the AI reads | 55 | | Signature batch | 500 recipients | | Due-diligence bundle | 500 contracts | | Approval workflow | 10 levels | | Approval email link | 7 days | ## What ranges can the approval and reminder settings take? | Setting | Range | Default | |---|---|---| | Renewal reminder | 1–365 days | 90 | | Expiration warning | 1–365 days | 30 | | Escalate after | 1–90 days | 7 | | Remind before escalating | 0–720 hours (0 sends no reminder) | 24 | | Chase unsigned contracts every | 1–30 days | 7 | | Re-approve when value changes by | 0–100% | 10 | | Require legal review at or above (USD) | 0–10,000,000 | 100,000 | | Auto-approve below (USD) | 0–10,000,000 | 0 (off) | ## Which e-signature providers can I use? **Native (Built-in)** signing through the E-Signature app, which is billed per envelope, or a connected **DocuSign** or **HelloSign (Dropbox Sign)** account. Choose the default under **Settings → Integrations → Default provider**. For a paper signature, use **Mark as signed** on the contract; on a contract out for e-signature, that cancels the open signing request and tells its signers. Signing records the signature. A signed draft that needs approval is submitted for approval straight away, and a contract that still needs approval goes live only when its approvals complete. --- ## More help - [Contracts Overview](/help/articles/contracts_app_overview) - Ask AI — the assistant answers Contracts questions from these articles. **Keywords:** faq, contract, new contract, approval, delegate approvals, AI summary, risk score, renewal, notice deadline, obligation, task, counterparty link, redline, service delivery, work permit, certificate, purchase order coverage, webhooks, contract events, bulk upload, not showing, limits, contracts --- # Dashboards & Widgets **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-18 How to configure the employee home dashboard — group dashboards, personal layouts, Top of Home, card style and density, the Widget Gallery, and custom embed, board and quick-add widgets. # Dashboards & Widgets ## 1. What it is The dashboard is every employee's home page. When someone signs in or taps the home icon, the platform decides which dashboard they get and which widgets it shows, based on their group membership and role. Two admin pages control it: - **Admin → Dashboard Builder** — where you compose dashboards and assign each one to a group. - **Admin → Widget Gallery** — the catalog of every widget, where you switch widgets on or off for the whole business and create custom embed widgets. How every card looks — its outline, shadow and spacing — is set once for the business in **Brand & Theme Settings**, not per dashboard. **Enablement:** these are built-in admin pages, not a licensed app. Admins and super admins can use them. **What it is not:** the Dashboard Builder does not change the admin sidebar. It only decides each audience's home page and which apps are recommended on that audience's navigation rail. ## 2. Standing it up The dashboard works with no configuration. Every business gets starter dashboards filled with default widgets. The steps below tailor it. 1. Go to **Admin → Dashboard Builder**. Every business has three starter dashboards: **Default** (the catch-all for everyone), **All Admins** and **All Managers**. 2. For each dashboard, drag widgets from the palette onto the canvas. The palette groups widgets as **Platform**, **Core Apps** and one section per enabled app. Pick the dashboard's layout under **Columns** in the toolbar: 1 to 4 equal columns, **Main + side** (a wide main column beside a narrow one) or **Side + main + side** (a narrow column on each side of a wide main one). Each widget is one column wide, or **Full**, which puts it above the columns; widgets stack in their column with no gaps. On a narrow screen Side + main + side stacks both side columns beside the main one, and on a phone every widget is full width. The **News Feed** widget puts a feed on the dashboard, loading more as people scroll. It is one card with one list: company posts from Communications and the message boards of every workspace a person is in, together. The list leads with what **needs you** (a must-read waiting for your acknowledgement, a post that mentions you, a question sent to you as an expert), then what you have **not read** — company news first, then workspace posts — then a **You're caught up** line and everything older by latest activity. A notice Communications is featuring leads whichever of those sections it falls in. Weekly and closeout recaps you have not read are folded into one row you can open. A switch under the header narrows the list to **News**, **Workspaces** or **Unread**. The **⋮** menu opens the Feed or the Message Boards page and has **Mark all as read** while something is unread; a must-read still waiting for an acknowledgement stays unread until it is acknowledged. People who can post see **Compose**. With only one of the two apps the card takes that feed's name and the switch is **All** and **Unread**. The widget is offered only on **Main + side** and **Side + main + side**, where it fills the main column below any other widget there, and the side columns stay in view while people scroll. On a phone it is the last card, with the same single list and switch; recaps you have not read are one card that opens Message Boards. Every other layout keeps the three-row **Latest Posts** widget. 3. Click **Save draft** to store changes without affecting anyone. Click **Publish** to make the draft live. People only ever see the published layout. 4. To target a specific audience, click **Add dashboard** and choose a group. The new dashboard appears in the priority list above Default. 5. Drag dashboards to reorder them. Priority runs top to bottom (see §3). Default always stays last and cannot be deleted. 6. Anything everyone must see goes at the top of Home, not on a dashboard: book it as a **Top of Home** message from Communications (see §3). 7. Confirm with **⋮ → Preview as a person**, which shows the dashboard one person resolves to. **Pairings that matter:** - A widget only appears when the app it depends on is enabled in Admin → Apps → All Apps. Adding **Upcoming Shifts** does nothing until the Shifts & Scheduling app is on. ## 3. How it fits together ### Which dashboard a person gets Each dashboard is tied to a group and has a priority position. The platform gives each person the first published dashboard, from the top, whose group they belong to. Everyone else gets **Default**. A person sees only that one dashboard's published layout, filtered to the widgets their role and apps allow. ### Starter layouts vs. layouts you arranged The three starter dashboards are laid out automatically from the apps your business has. While nobody has saved a layout on one, it keeps itself current: enable a new app and its cards appear there for everyone. Once an admin saves a layout on a dashboard, that layout is yours. When a new app is enabled later, its cards are added only to the dashboard's draft, so nothing changes for people until you review and publish. Cards you removed are not added back. Dashboards you add yourself are never laid out automatically. ### Draft, published, and unpublished changes Every dashboard has two layouts. The **draft** is what you edit. The **published layout** is what people see. Editing a published dashboard parks the edit as "unpublished changes" until you publish again, so you can rearrange over several sessions without disturbing the live home page. ### Top of Home (the Hero card is retired) The old **Hero** card and the standing hero set in the Dashboard Builder are retired. A message everyone must see now shows at the top of Home itself — at the head of the Home briefing's News, or as a banner above the dashboard when the briefing is off — so it is never a card you place on a dashboard. A **Top of Home** message is booked from Communications. It reaches only the people in the message's audience, one message at a time for any one person, for at most 7 days, and it always ends. A board that still carries the old Hero card shows nothing in that slot; the Widget Gallery's sample says why. ### Card style and density **Card Style** and **Card Density** are business-wide theme settings. They apply to every card and dashboard widget on desktop, in dark mode and in the mobile app. You cannot set them per dashboard or per audience. ### Widget categories - **Platform** — always available, such as Quick Actions, App Launcher, More apps and Profile Summary. App Launcher shows each person's other apps, including sign-in tiles; More apps shows the OneMango apps they have; Quick Actions holds the tiles they choose — see [App Launcher & Sign-in Tiles](/help/articles/admin_app_launcher). - **Core Apps** — available when the matching core feature is on, such as Catch Me Up, Upcoming Shifts and Pending Approvals. - **Marketplace Apps** — one or more per enabled app. Each widget declares which roles can see it, which apps it depends on, and its default width. ### Widget Gallery curation The Widget Gallery is a business-wide on/off switch for individual widgets. Disabling a widget hides it everywhere — every dashboard, the mobile app, the builder palette and signage — without changing any layout. Re-enabling it restores every existing placement. ## 4. Running it ### Booking a Top of Home message 1. In Communications, write the feed post or broadcast. 2. In its **Where people see it** card, choose **Top of Home** and set when it starts and ends (7 days at most). ### Personal layouts A dashboard can let the people who get it arrange it for themselves. It is off for every dashboard until you turn it on, one dashboard at a time. With it on, a **Customize this page** link appears above the dashboard, at its right, on each person's desktop home page. There they can drag cards into a different order, move a card between columns, and hide the cards they don't need. Their arrangement is theirs alone. They cannot add cards, change a card's width or change the columns, so the dashboard keeps the shape you gave it. The phone follows what a person saved on desktop; there is no customizing on the phone. Your later changes still reach them: - A card you **add** appears for everyone, including people who rearranged. It lands after the card it follows in your layout. - A card you **remove** is removed for everyone. - **Reordering** cards does not move them for people who arranged the dashboard themselves. Their own order wins. - Changing the **Columns** puts everyone back on your layout. - Turning personal layouts **off** shows your layout to everyone at once. People's own arrangements are kept and return if you turn it back on. Because a move you make may not reach everyone, anything every person must see belongs above the dashboard, in the Home briefing or a Top of Home banner. Those cannot be moved or hidden. **Experience preview** shows a named person's own arrangement and lists the cards they hid. The composer offers **Top of Home** to every business — Home always has a top. The Communications app must be enabled, and the Top of Home slot must stay on in its **Placement slots** settings. ### Adding, copying or mirroring a dashboard - **Add dashboard** — pick a group from the dropdown. Groups already backing a dashboard, and groups that need runtime details (such as location-radius groups), are not offered. A new dashboard starts as a draft with an empty canvas. - **Copy from** — fills this dashboard's draft from another dashboard. **Replace** makes an exact copy; **Merge** adds only the widgets not already present. - **Mirror** — makes this dashboard show another's published layout. A mirror is read-only; edit the source instead, or unlink the mirror to make it independent. Circular mirrors are blocked. - **Preview** — a full-page rendering of the draft inside the real app layout. ### Disabling or enabling widgets business-wide 1. Go to **Admin → Widget Gallery**. The **Catalog** tab lists every widget; filter it by **Available**, **Disabled** or **Unavailable** (its app is off). 2. Click **Disable** or **Enable** on a card, or select several cards and use the bulk bar. Bulk changes are capped at 200 widgets per request. 3. A disabled widget disappears from all dashboards and pickers. Layouts are left untouched, so re-enabling brings it back everywhere it was placed. ### Creating custom widgets - **Embed widget** — in the Widget Gallery, click **New widget → Embed widget**. Enter a name (up to 120 characters) and an HTTPS address, then choose an aspect ratio (16:9, 4:3, 1:1 or 3:1) or a fixed height of 200–1,200 px (default 400 px). Optionally set a zoom level (100%, 90%, 75% or 50%). The address cannot point to a MangoApps domain. There is no per-widget role list: who sees an embed is decided by which dashboards you place it on. A weekly check re-tests whether each embed can still be framed. - **Board widget** — created in the **Live Boards** app from Power Tables data. - **Quick-add widget** — created in the **Power Tables** app on a table; it captures one row from the dashboard. ### Letting people rearrange a dashboard 1. In **Admin → Dashboard Builder**, open the dashboard's tab. 2. Open the **Dashboard actions** menu (⋮) and choose **Personal layouts…**. 3. Turn on **People can rearrange this dashboard** and click **Save**. It applies straight away; you do not need **Save draft** or **Publish**. The same drawer shows how many people have their own layout of the dashboard. To put them all back on your layout, tick the reset box and click **Save**. This cannot be undone. A person can also go back on their own, with **Reset to company layout** in Customize this page. After you publish a dashboard, the confirmation says how many people keep their own layout of it. Custom widgets are archived, not deleted. An archived widget leaves every dashboard but keeps its placements; restoring it brings them back. Archived widgets are listed on the **Custom Widgets** tab. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Widgets and order per dashboard | Admin → Dashboard Builder | Starter dashboards: laid out from your apps; added dashboards: empty | Which widgets people in that group see, and in what order | | Columns | Dashboard Builder → Columns in the toolbar | Two columns | 1 to 4 equal columns, Main + side, or Side + main + side | | Widget width | Dashboard Builder → width control on the card | One column | One column wide, or Full (above the columns) | | Recommended apps | Dashboard Builder → Recommended apps strip | None — the company's recommended apps apply | Apps suggested on that audience's navigation rail | | Personal layouts | Dashboard Builder → Dashboard actions (⋮) → Personal layouts… | Off | Whether the people who get this dashboard can reorder and hide its cards on their own home page | | Card Style | Admin → General Settings → Brand & Theme → **Surfaces & Shape** | **Standard** | Outline and shadow of every card: Standard (thin outline, soft shadow), Outlined, Elevated (lifted shadow, no outline) or Flat | | Card Density | Admin → General Settings → Brand & Theme → **Surfaces & Shape** | **Comfortable** | Room around card content; **Compact** fits more on a screen | | Widget on/off | Admin → Widget Gallery | All widgets on | Whether a widget appears anywhere in the business | **Out-of-the-box defaults:** - A dashboard you add starts as a draft and must be published before anyone sees it. - Only the Default dashboard is the catch-all. - Nobody can rearrange a dashboard until you turn on Personal layouts for it. - Cards look exactly as they always have until you change Card Style or Card Density. ## 6. More help - **Business profile and Brand & Theme** — the rest of the theme settings, including colors, fonts and the sign-in page. - **Communications** — composing messages, including Top of Home bookings. - **Live Boards** and **Power Tables** — building board and quick-add widgets. - Ask AI — the assistant answers questions about dashboards and widgets from these articles. **Keywords:** dashboard, widgets, home page, dashboard builder, dashboard configuration, widget gallery, group dashboard, top of home, hero, announcement banner, card style, card density, compact cards, embed widget, board widget, quick add widget, quick actions, more apps, app launcher, widget placement, default dashboard, disable widget, publish dashboard, mirror dashboard, recommended apps, personal layouts, customize this page, rearrange home, hide a card, reset to company layout --- # Digital Signage App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to register screens, manage media content, and configure what appears on your workplace displays. # Digital Signage ## 1. What it is Digital Signage turns any browser-capable screen into a workplace display that rotates alerts, Communications posts, recognitions, calendar events, and custom media slides. Each screen runs as a web page authenticated by its own token — no partner hardware or device agent is required. - **Enablement:** Digital Signage is a pay-as-you-go app billed per registered screen. A registered screen counts whether it is active or deactivated, online or offline, until you delete it; sample screens don't bill. An admin enables it from Admin → Apps → All Apps, then registers individual screens. - **What it is not:** Digital Signage does not replace a third-party signage platform. Its display URL can be embedded as a web zone inside an existing player (BrightSign, Scala, Yodeck, etc.) alongside that platform's own content. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Digital Signage**. 2. Open **Digital Signage → Settings** and review the module toggles. At minimum, confirm **Enable screen management** is on (it is by default). 3. Go to the **Screens** tab and register your first screen. Give it a name, optionally assign it to a location, and save. The system generates a unique display URL. 4. Copy the display URL and open it in the browser on your target device (a Chromium browser, Fire TV, smart TV, or any signage player that accepts a web URL). The screen begins polling for content immediately. 5. Return to the **Dashboard** tab. Within a few minutes the screen's status badge should change to **Online**, confirming it is connected. **What silently does nothing until configured:** a screen assigned to a location will only show media slides and broadcasts targeted to that location (or to all locations). If you upload media scoped to "Lobby" but the screen has no location set, that media will not appear. ## 3. How it fits together ### Screens A screen is a registered display device. Each screen carries its own 32-character token, and its public URL (`/signage/display/`) is the only credential the device needs. Screens have four statuses: - **Online** — heartbeat received within the last 5 minutes. - **Offline** — previously connected but no heartbeat in the last 5 minutes. - **Never connected** — registered but the display URL has never been opened. - **Inactive** — manually deactivated by an admin (the display shows "Screen is paused." instead of content). Example: you register three screens — *Lobby Wall* (location: HQ), *Break Room* (location: Warehouse), and *Cafeteria TV* (no location). Lobby Wall shows HQ-targeted media plus media published to all locations. Break Room shows Warehouse-targeted media plus all-location media. Cafeteria TV shows only media published to all locations. ### Content types and the feed Each screen rotates a playlist built from up to nine content types: custom media, Safety Hub alerts, Communications posts, recognitions, calendar events, open shifts, OKR progress, contest leaderboards, and Live Boards visualizations. Seven of them have an app-wide default in Settings and a rule on each screen. Contest leaderboards and Live Boards visualizations have no switch in Digital Signage Settings: each is switched in its own app's Settings, and on each screen. A broadcast sent to screens from the Communications composer follows the Communications posts rule rather than having a switch of its own. Every type except custom media and calendar events comes from another app, and produces no slide unless that app is enabled: Safety Hub for alerts, Communications Hub for posts and broadcasts, Recognitions, Shifts & Scheduling for open shifts, OKR Hub, Contests, and Live Boards. Calendar events need **Company Events** switched on in Calendar. Alerts reach a screen only when they are sent to everyone in the business — never when they are sent to particular people, groups, departments, locations, job titles or roles — and stay in the rotation for 24 hours after sending (longer only with an acknowledgement chase-up window that runs past that), or until the alert is stood down. The feed is assembled on each poll. Pinned items come first: urgent alerts (for those 24 hours), custom media slides in the order you set, must-read Communications posts, posts whose author ticked **Break-room screens**, and critical broadcasts. Everything else is ordered by how close it is to now — the newest posts and the soonest events and open shifts first — and the playlist is cut at the screen's **Max items in rotation**. ### Content rules (per-screen overrides) Each content type can be set to Show, Hide, or left to follow the app-level default — per screen. A screen's own Show or Hide always wins: the matching switch in Settings decides only for screens that follow it. A screen also supports scheduling windows: a one-shot date range and recurring dayparting (specific days of the week and a daily time window). This lets you show shifts content on the factory floor only during weekdays, 6 AM–6 PM, without touching the tenant default. ### Custom media and the approval workflow Custom media slides (images or short videos) are the content that originates inside Digital Signage rather than being mirrored from another app. A slide moves through these statuses: **Pending → Approved (live on matching screens)**, or **Pending → Rejected** Uploading a slide sends it for review — there is no separate draft or submit step (only sample data creates slides in **Draft**). When **Require media approval** is on (the default), new uploads start in **Pending** and must be approved by a reviewer before they appear. Reviewers are whoever **Who can approve media before it goes live?** admits — app admins and business admins by default — and a reviewer can approve their own upload. When approval is off, uploads go straight to **Approved** and appear on matching screens without review. While approval is required, a rejected slide can be edited and saved again by its author, which returns it to **Pending**. With approval off, an author's save puts their own waiting slide live, but not one a reviewer rejected, unpublished or sent back by editing it: that stays off screens until a reviewer approves it. An approved slide can be unpublished by a reviewer (returned to **Pending** without a rejection badge). While approval is required, only a reviewer can edit or delete an approved slide, and a reviewer's edit sends it back to **Pending** for re-review; its author can change it again once a reviewer has unpublished it. ### Zone tags Both screens and media slides carry optional zone tags — free-form labels like "lobby", "safety", or "cafeteria". A slide with zone tags appears only on screens whose tags overlap. A slide with no tags appears on all screens. A screen with no tags sees only untagged slides. ### Location scoping Screens can be assigned to a location. Media slides can also be scoped to a location or left as "all locations." The feed matches: a screen at Location A sees slides for Location A plus all-location slides. A screen with no location sees only all-location slides. ### Integration with Communications In the Communications composer, an author can tick **Break-room screens** on a message. A broadcast appears on screens only when it is ticked, and can be limited to specific sites (locations where a screen is registered). A post that goes to everyone appears on screens anyway while it is among the newest; ticking it puts it ahead of the other items, and a post sent to only some people never appears on a screen. Either way this is a request, not an override — each screen's own Communications posts rule still decides whether Communications content shows — and a message stays in the rotation for up to 14 days after it is published. The composer shows the option only when at least one active screen exists. ## 4. Running it ### Registering a screen 1. Go to **Digital Signage → Screens → Register screen**. 2. Enter a name, optional notes, and optionally assign a location. 3. Save. Copy the generated display URL and open it on the target device. ### Uploading custom media 1. Go to **Digital Signage → Media → Upload media**. 2. Upload an image (PNG, JPG, GIF, or WebP) or video (MP4 or WebM). Give it a title — the title, and the caption if you add one, are drawn along the bottom of the slide on the screen. 3. Optionally scope it to a location, add zone tags, set a schedule window, or configure recurring dayparting. 4. Save. If approval is required, it enters the review queue. If not, it goes live on matching screens without review. ### Reviewing pending media 1. Open the **Media** tab. The pending count appears at the top. 2. Open a pending slide and choose **Approve** or **Reject**. Rejections can include a reason the author sees in their notification. ### Forcing a screen refresh On an active screen's detail page, open the **More actions** menu and choose **Force refresh**. This sends a live signal to that screen, which reloads its page within a few seconds instead of waiting for its next poll — so it picks up new content and any change to the screen's own name, branding or settings. A screen that is offline cannot receive the signal; it loads the latest content on its own once it is back online. ### Rotating a screen's token If a screen's URL may have been exposed, go to the screen's detail page and click **Regenerate token**. The old URL stops working immediately. Update the device with the new URL. ### Reviewing the audit log Go to **Digital Signage → Audit log**. Every change an admin makes is recorded: screens created, edited, deleted, activated, deactivated, force-refreshed and token-rotated; media created, edited, deleted, submitted, approved, rejected and unpublished; and settings updates and resets. Each entry shows who acted, what they acted on, when, and the originating IP. Filter by action type or by a date range, and choose 50, 100 or 200 entries per page. The action dropdown is built from what has actually been recorded, so it only ever offers actions your business has performed. Approvals and rejections made through the AI assistant are recorded here too, marked as taken via the agent. The tab is visible to company admins and to users granted the Digital Signage app-admin role. ### Reviewing analytics Go to **Digital Signage → Analytics**. The page shows your screen total with status tiles — Online and Offline always, Never connected and Inactive when there are any — and **Slides delivered**: the total, by content type, by content item, by screen, and per day. A slide is counted when a screen fetches its feed, so the figure is delivery volume, not how many people saw it. Choose the last 7, 30, 90 or 180 days (30 by default). The figures can be exported to CSV. ## 5. Settings All settings are at **Digital Signage → Settings**. ### Modules The seven **Show…** switches are defaults, not commands: a screen uses one only while its own rule for that content type is left on **Follow app Settings**. A screen set to Show or Hide keeps its own answer. The other three switches are business-wide. | Setting | Default | What it changes | |---|---|---| | Enable screen management | On | Shows the Screens tab and the controls for registering and editing screens. Turning it off does not stop screens playing. | | Show media | On | Shows the Media tab, and is the default for whether screens play approved media slides. | | Require media approval | On | Uploaded media starts in Pending and must be approved by a reviewer before going live. When off, uploads go live without review. | | Show alerts on screens | On | Default for Safety Hub alerts: only those sent to everyone, for 24 hours after sending (or until a longer acknowledgement chase-up window ends). Requires Safety Hub. | | Show feed posts | On | Default for Communications posts from the last 14 days that go to everyone, plus broadcasts whose author ticked break-room screens. Requires Communications Hub. | | Show recognitions | Off | Default for employee recognitions from the last 30 days. Off by default because they name people. Requires Recognitions. | | Show calendar events | On | Default for company events open for registration that start in the next 14 days. Requires Company Events switched on in Calendar. | | Show shifts | Off | Default for published open shifts starting in the next 7 days at the screen's location (at every location, for a screen with none). Requires Shifts & Scheduling. | | Show OKR progress | Off | Default for current-quarter company-level objectives with traffic-light progress. Requires OKR Hub. | | Email admins about offline screens | On | One daily email per recipient about active screens that have not checked in for 24 hours or more, repeated for up to 14 days. It goes to the app's designated app admins, and to business admins only when none is designated or reachable by email. This switch is the only way to stop it: the email is not in a notification category, so a recipient cannot mute it from their notification preferences. | Contest leaderboards and Live Boards visualizations are not in this table: each is on by default once its app is enabled, and is switched in that app's own Settings or on a single screen. ### AI Agent **Enable the Digital Signage AI agent in Ask AI** (on by default) adds the Digital Signage assistant to Ask AI and the "Describe it and let AI fill the form" bar to this app's forms. See **Ask AI** below for what the assistant can do. ### Display Defaults | Setting | Default | What it changes | |---|---|---| | Default refresh interval | 60 seconds | How often a screen polls for updated content, for every screen that has not set its own. Per-screen overrides take precedence. | | Default theme | **Dark** | Light or Dark screen appearance, for every screen that has not set its own. Per-screen overrides take precedence. | ### Content Publishing Three capability settings, each defaulting to the behaviour it replaced, so nothing changes until you move a radio. App admins and business admins can always do all three. **Who can publish content to screens?** controls who can upload and manage media slides — and, because the library is shared, who can open it and see every slide in it. It defaults to managers and above. Change it to people managers (anyone with direct reports), to everyone with app access or to a content-authors group, or narrow it to app admins only. **How far does this grant reach?** scopes it: leave it company-wide, or choose *their own location only* so a site manager publishes to their own sites and cannot make an org-wide push. Anyone you have given the "Contributor — records only" grant for Digital Signage can also publish, whatever this setting says. **Who can approve media before it goes live?** controls approve, reject and unpublish. It defaults to app admins and business admins. Naming a group here is how you let a comms or brand team sign content off without making them Digital Signage app admins — that tier also shows every screen's display URL and opens Settings. **Who can see screen analytics?** controls the Analytics tab and its CSV export. It defaults to app admins and business admins. The audit log is deliberately not part of it and stays admin-only, because it records who did what and from which IP address. ## 6. Other ways to reach Digital Signage ### Ask AI With **Enable the Digital Signage AI agent in Ask AI** on, the Digital Signage assistant answers admin questions from the live data rather than from these articles. It can list screens with their online/offline status, summarise how many screens are up, list media by status, show what is pending review, and read the admin audit log. It can also approve or reject a media slide — both ask you to confirm first, both are limited to whoever **Who can approve media before it goes live?** admits, and both need the media library switched on. Try "Which screens are offline?", "Show me media pending approval", or "Who changed signage settings recently?" ### On a phone Opening Digital Signage on a phone shows a read-only status dashboard: how many screens are online and offline, each screen's state, and — if you can publish or review media — how many slides are waiting for review. Registering screens, managing media and changing settings are on the full pages: tap **Open the full page** at the foot of the phone page to get there. ### API Two read-only endpoints are available for reporting and integrations: `GET /api/v1/digital-signage/screens` and `GET /api/v1/digital-signage/media`, each with an index and a show action. They are scoped to your business, and each requires the same access as the matching tab in the app: `screens` needs the app-admin tier with **Enable screen management** on, and `media` needs publishing or review access with the media library on. An employee who is bounced from a tab in the browser is bounced from the endpoint too. There are no write endpoints — registering screens and approving media happen in the app. ## 7. More help - **Digital Signage FAQ** — specific setup and operating questions. - Ask AI — ask about your own screens and media; see **Ask AI** above for what the Digital Signage assistant can do. **Keywords:** digital signage, signage, screen, kiosk, lobby display, display, break room screen, media approval, signage content, offline screen, digital-signage, digital_signage --- # Digital Signage FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Digital Signage — for the admin running it. # Digital Signage FAQ Answers to common setup and operating questions about Digital Signage. For what the app is and how to set it up from scratch, see the [Digital Signage Overview](/help/articles/digital_signage_app_overview). --- ## Setup ## What do I need to configure before screens start showing content? Enable the app for your organisation, then register at least one screen. Out of the box, custom media, Safety Hub alerts, Communications posts, and calendar events are turned on — and each of the last three produces a slide only when its source is on too: the Safety Hub app, the Communications Hub app, and Company Events in Calendar. Recognitions, open shifts, and OKR progress are off by default — turn each one on in **Settings** when you are ready. If you plan to upload custom images or video, the approval workflow is also on by default, so your first upload will wait in **Pending** until a reviewer approves it. ## Who can manage screens, media, and settings once the app is enabled? Admins (admin or above) and anyone with a Digital Signage app-admin grant can manage screens, read the audit log, and change settings. Three of those capabilities are now yours to set in **Settings**, each defaulting to what it did before: - **Who can publish content to screens?** — who may upload and manage media slides. Defaults to managers and above; you can change it to people managers (anyone with direct reports), everyone with app access, specific groups only, or app admins only. You can also scope the grant to **their own location only**, so a site manager publishes to their own sites and cannot push org-wide. - **Who can approve media before it goes live?** — defaults to app admins and business admins. Naming a group here lets your comms or brand team sign content off without granting them the app-admin tier, which also shows every screen's display URL. - **Who can see screen analytics?** — defaults to app admins and business admins. Two notes on media. Authors keep control of what they uploaded, not of what colleagues uploaded: you can edit or delete **your own** slides, and — while **Require media approval** is on — an approved slide can be changed or deleted only by a reviewer, who has to unpublish it before you can edit it again. And anyone you grant publishing can also open the shared media library and see every slide in it, including who uploaded and approved each one — it is a shared library by design. A user with app access but none of these capabilities sees a short description of what Digital Signage is, not the screen list. --- ## Permissions and access ## Why can't a manager see the Screens or Analytics tabs? **Screens**, **Audit log** and **Settings** are for admins and app admins only. **Screens** additionally needs **Enable screen management** switched on, so an admin loses that tab too when it is off. **Analytics** is admin-only by default but is now configurable — see **Who can see screen analytics?** in Settings. Managers see **Dashboard** and **Media** (if the media library is enabled). If a manager needs full access, grant them the Digital Signage app-admin role from the app's page in **Admin → Apps → All Apps**. ## Who decides whether uploaded media needs approval before it goes live? An admin controls this with the **Require media approval** switch in Settings. When it is on (the default), new uploads start in **Pending** and only reach screens after a reviewer approves them. Reviewers are whoever **Who can approve media before it goes live?** admits — app admins and business admins by default — and a reviewer can approve their own upload. When it is off, uploads go live as soon as they are saved, with no review. --- ## Day-to-day ## How do I get a new screen running? Go to **Screens → Register screen**, give it a name, optionally pick a location, and save. The app generates a unique display URL. Open that URL fullscreen in any browser — a Fire TV, a smart-TV browser, a Raspberry Pi, a tablet, or a Chromecast — and the feed starts rotating. You can also paste the URL into a third-party signage platform (BrightSign, Scala, Signagelive, etc.) as a web-URL content slot. ## Can I schedule media to appear only during certain hours or days? Yes, two layers of scheduling stack together. **One-shot dates:** set a start and end date on a media slide so it appears only within that window. **Recurring daypart:** pick the days of the week (Sunday through Saturday) and a daily time window (e.g. 11:00 AM – 2:00 PM). Both must pass for the slide to show. Overnight time windows (e.g. 10 PM – 6 AM) are not supported — split them into two entries instead. Per-screen content rules also support dayparting: you can turn an entire content stream (e.g. shifts) on or off by day and time window for each screen independently. ## What content appears on screens, and can I control it per screen? Screens can rotate nine content types: custom media, Safety Hub alerts, Communications posts, recognitions, calendar events, open shifts, OKR progress, contest leaderboards, and Live Boards visualizations. A broadcast whose author ticked **Break-room screens** in the Communications composer follows the Communications posts rule — it has no switch of its own. Each screen has its own rule for every content type: **Show**, **Hide**, or follow the app-level default. A screen's own Show or Hide always wins; the matching switch in Settings decides only for screens left on **Follow app Settings**. Media, alerts, Communications posts and calendar events are on by default; recognitions, open shifts and OKR progress are off until you switch them on. Contest leaderboards and Live Boards visualizations are on by default and are switched in their own apps, not in Digital Signage Settings (see "Why can't I see OKR progress, contest leaderboards, or Live Boards visualizations on screens?" below). A content type also needs its source: Safety Hub for alerts, Communications Hub for posts and broadcasts, Recognitions for recognitions, Shifts & Scheduling for open shifts, OKR Hub for OKR progress, Contests and Live Boards for theirs, and Company Events switched on in Calendar for calendar events. Without it the type produces no slide, whatever the rule says. ## How does the media approval workflow work? An author uploads a slide and it goes straight to review — there is no separate submit step. The slide enters **Pending** status and the reviewers get an in-app notification. Reviewers are whoever **Who can approve media before it goes live?** admits: app admins and business admins by default. A reviewer can **Approve** it (it goes live on matching screens), **Reject** it (the author sees the reason), or later **Unpublish** it (returns it to Pending without a rejection badge). While approval is required, the author of an approved slide can no longer edit or delete it: only a reviewer can, and a reviewer has to unpublish it before the author can change it again. ## What happens when I edit an already-approved media slide? While **Require media approval** is on, only a reviewer can edit an approved slide, and saving the edit returns it to **Pending**: it comes off screens and must be approved again before it reappears. This prevents a swapped image or changed caption from bypassing sign-off. The slide's author is not offered the edit — they are told to ask a reviewer to unpublish it first. With approval off, authors can edit their own live slides and the change reaches screens without review. ## How do I push an alert to all screens immediately? Send the alert from Safety Hub to everyone in the business. Only an alert that goes to everyone reaches a screen — one sent to particular people, groups, departments, locations, job titles or roles never does, because anyone in the room can read a screen. Connected screens refresh within seconds of the send; a screen without a live connection picks the alert up on its next poll. The alert stays in the rotation for 24 hours after it is sent — longer only when it has an acknowledgement chase-up window that runs past that — or until you stand it down. An urgent alert is pinned to the front of the rotation for those 24 hours. A screen shows up to five alerts at a time, and only when its own **Critical alerts** rule allows them (or, for a screen that follows app Settings, **Show alerts on screens** is on). --- ## When something looks wrong ## Why does my screen show "Offline" on the dashboard? A screen is marked offline when it has not sent a heartbeat within the last 5 minutes. Common causes: the device lost power or network, the browser tab was closed, or the device went to sleep. Check the device physically, confirm it has network access, and reload the display URL. The dashboard sorts problem screens to the top so you can spot them quickly. ## My screen went dark overnight — will I be notified? By email, but not straight away: a screen is reported once it has not checked in for 24 hours or more. A daily sweep runs at 8:00 AM UTC and sends one email per recipient, covering every active screen in that state (sample screens are never reported). It goes to the app's designated app admins, and to business admins only when no app admin is designated or reachable by email — so you receive it only if you are one of them. The email repeats each day for up to 14 days, and stops sooner when the screen checks in again, when it is deactivated, or when **Email admins about offline screens** is switched off in Settings. A brand-new screen that has never connected gets a 24-hour grace period before it is first listed. In the meantime the dashboard shows the screen as **Offline** five minutes after its last check-in. ## A screen lost its network connection — what happens to the display? A service worker keeps the screen rotating its last-known feed and media content — not a frozen single frame. When connectivity returns, the screen catches up automatically. An "Offline — showing last received content" badge appears on the display so anyone walking by can tell it is stale. ## Why isn't a media slide showing on my screen? Check these in order: (1) The slide must be **Approved** — draft, pending, and rejected slides never reach a screen. (2) If the slide has a date schedule, today must fall within the start and end dates. (3) If the slide has a daypart schedule, the current day and time must match. (4) If the slide is pinned to a location, it plays only on screens assigned to that location — a screen with no location plays only slides set to all locations. (5) If the slide has zone tags, the screen must share at least one matching tag. (6) The screen's own **Custom media** rule must not be set to Hide — and if that rule follows app Settings, **Show media** must be on in Settings. (7) A sample-data slide plays only on sample screens. ## Why can't I see OKR progress, contest leaderboards, or Live Boards visualizations on screens? All three need their own app — OKR Hub, Contests, or Live Boards — enabled for your organisation. After that they differ. **OKR progress** is off by default: switch on **Show OKR progress** in Digital Signage Settings, or set a screen's own OKR Progress rule to Show. It shows current-quarter, company-level objectives only. **Contest leaderboards** and **Live Boards visualizations** are on by default as soon as their app is enabled, and have no switch in Digital Signage Settings. Each is switched for every screen in its own app's Settings — **Show contest leaderboards on digital signage** in Contests, **Show boards on Digital Signage** in Live Boards — and any single screen can hide them in its own content rules. A contest appears only while it is active and open to the whole company; a board appears only when **Publish to Digital Signage** is ticked on it. ## I rotated a screen's token — what happens to the old URL? The old URL stops working immediately. A device still showing it goes to "Screen not registered." within seconds when it has a live connection, and at its next feed refresh otherwise. A device that is offline keeps showing its last received content until it reconnects. Copy the new display URL onto the device to reconnect it. The rotation is recorded in the Audit log. --- ## Licensing and limits ## Does Digital Signage require a licence? No. Digital Signage is pay-as-you-go, billed per registered screen. A registered screen counts whether it is active or deactivated, online or offline, until you delete it; sample screens don't bill. There is no per-employee fee and no licence to purchase, and any tenant can turn the app on. ## What are the size and format limits for media uploads? Custom media accepts images (PNG, JPG, GIF, WebP) and videos (MP4, WebM) up to **500 MB** per file. Landscape (16:9) renders best in fullscreen. Header and footer branding images accept PNG or JPEG only, up to **10 MB**. Media titles can be up to 200 characters. ## Are there other limits I should know about? | Setting | Range | |---------|-------| | Refresh interval (how often a screen polls for new content) | 30 – 300 seconds, default 60 | | Rotation interval (how long each slide stays on screen) | 3 – 60 seconds, default 8 | | Maximum slides in a single rotation | 1 – 50 items, default 12 | | Image display duration (per slide) | 3 – 120 seconds | | Screen name | Up to 100 characters | | Communications posts and broadcasts recency window | 14 days | | Recognition recency window | 30 days | | Calendar events lookahead | 14 days | | Open shifts lookahead | 7 days | | Analytics date range | Last 7, 30, 90 or 180 days | Videos always play to their full length regardless of the rotation interval. --- ## More help - [Digital Signage Overview](/help/articles/digital_signage_app_overview) - Ask AI — the built-in agent answers Digital Signage questions, shows which screens are offline or what media is pending approval, and — if you are a reviewer — can approve or reject a slide for you, each with a confirmation step. **Keywords:** faq, digital signage, screens, kiosk, media library, approval workflow, offline, token, heartbeat, daypart scheduling, digital-signage, digital_signage --- # Drive App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run Drive — personal and shared drives, file sharing and versioning, external links, file requests, branding, and AI agents. # Drive ## 1. What it is Drive is centralized file and folder management for your organization. Employees get a personal drive for their own files, and teams get shared drives — one is created automatically for each workspace. Files stored in Drive carry versioning, permissions, commenting, and an activity trail. Drive also stores the files attached to broadcasts and workspace messages, each with a version record and an activity trail rather than as a disposable blob; those live in a hidden system drive and open from the post or message they came with. - **Enablement:** Requires a license. An admin enables it from **Admin → Apps → All Apps**. It is not turned on automatically. - **What it is not:** Drive stores and shares files. It does not replace document authoring — you create and edit content in the source application and upload or attach the result to Drive. ## 2. Standing it up 1. **Enable the app** — go to **Admin → Apps → All Apps**, find **Drive**, and enable it. 2. **Review settings** — go to **Drive → Admin → Settings**. The defaults are usable out of the box (versioning on, external links allowed, 500 MB upload limit). Adjust anything that needs to match your organization's policy before employees start using the app. 3. **Set up branding (optional)** — go to **Drive → Admin → Branding** to create a branding profile. Branding controls the look of external share link and file request landing pages — logo, accent color, header/footer messages, and optional PDF watermarking. One branding profile can be set as the default. 4. **Confirm it worked** — any employee who opens Drive sees **My Drive** in the sidebar (created automatically on first visit) and the **Shared Drives** of the workspaces they belong to. **Silent dependency:** Workspace-bound shared drives are created automatically when a workspace is created, but employees only see them if they are a member of that workspace. If an employee reports seeing no shared drives, check their workspace memberships first. **Permissions:** Business admins have Manager access on every drive — every Shared Drive and every person's My Drive. Drive App Admins have Manager access on every Shared Drive and on their own My Drive, but not on colleagues' personal drives. Everyone else — including people whose role in your organization is Manager, which gives no extra reach in Drive — sees their own My Drive, the Shared Drives of workspaces they belong to, and any files or folders shared with them. ## 3. How it fits together **Personal drives and shared drives** — Every user has exactly one personal drive ("My Drive"), provisioned automatically on first visit. Shared drives are team-level containers: one is created for each workspace, and there is no screen to create one any other way. Personal drives are private to their owner by default; a shared drive is reached through its workspace (owners and members get Editor, workspace viewers get Viewer), and any file or folder in it can also be shared with a person. **Items: files and folders** — Every node in a drive is either a file or a folder. Files carry their content through versions; folders are organizational containers. File names must be unique within the same folder (enforced at save time). Items support soft delete — trashing moves them to Trash, where they stay until permanently purged. Folders cascade: trashing a folder trashes all its contents. **Versions** — Each upload of a file with the same name in the same folder creates a new version rather than replacing the file. The most recent version is displayed by default. Any version can be restored as the current one. When versioning is enabled (the default), Drive retains up to 20 versions per file. When versioning is turned off, only the current version is kept and older versions are pruned on the next upload. **Sharing and roles** — Access is granted by sharing a file or folder with a person; a whole drive is reached through its workspace, not shared. Four roles, from least to most capability: **Viewer** (read and download), **Commenter** (read, download, and comment), **Editor** (read, download, comment, upload, edit, and trash), **Manager** (everything an Editor can do, plus sharing, external share links, and file requests). These are Drive roles, separate from anyone's role in your organization. A role on a folder is inherited by everything inside it. **External links** — A tokenized public URL that lets someone outside your organization view or download a file, or browse a folder and download the files in it, without signing in. External links can be password-protected, time-limited, and download-count-limited. The admin controls whether external links are allowed at all, whether a password is required, and the maximum lifetime. **File requests** — The reverse of an external link: a tokenized URL that lets someone outside your organization upload files into a designated folder. File requests have an expiry, an optional file-count cap, and can carry branding. The requester is notified when uploads arrive. **System drive** — A hidden per-organization drive ("App attachments") where other apps — broadcasts and their comments, alerts, workspace messages, direct messages, and Password Manager entries — store file attachments through Drive's infrastructure. It is not visible to users or admins in Drive; each attachment opens from the record it belongs to. **Workspace integration** — Every workspace automatically gets its own shared drive. Workspace owners and members receive Editor access to the workspace's drive, and workspace viewers receive Viewer access, without any additional configuration. ## 4. Running it ### Sharing a file or folder 1. Open the file and click **Share**, or choose **Share** from a file's or folder's menu in the list. You need Manager access on it (the Drive role). 2. Under **Add a person**, type a name or email and pick the person. 3. Choose a role: **Viewer**, **Commenter**, **Editor**, or **Manager**, and click **Add**. 4. The recipient is notified (if the **Notify users when files are shared with them or their access is removed** setting is on and they have not turned Drive notifications off). Someone who already has more access through a folder above it, the drive or their workspace is not told, and the Share panel says where their access comes from. 5. To revoke access, open the Share panel again and click the **×** beside the person under **People with access**. ### Creating an external share link 1. Open the file or folder's **Share** panel and go to its **External share links** section. 2. Set an expiry (left blank, it lasts the max lifetime configured in settings), an optional download limit, and a password (optional unless the admin requires one), then click **Create**. 3. Copy the link and send it to the recipient. The recipient can view or download the file — or browse the folder — without signing in. 4. To end the link before it expires, return to the same section and click the **×** (Revoke link) beside it. ### Sending a file request 1. Go to **Drive → File Requests** and click **Request files**. 2. Choose the target folder where uploaded files will land. 3. Enter the recipient's email and an optional message. Set an expiry and optionally a file-count cap. 4. The recipient receives an email with a link to the upload page. They can upload files without signing in. 5. When uploads arrive, the requester is notified. ### Managing branding profiles 1. Go to **Drive → Admin → Branding**. 2. Create a new profile: set a name, upload a logo, choose an accent color, and write header and footer messages. 3. Turn on **Apply a watermark to PDFs downloaded through public share links** if PDF downloads through external links should carry a visible watermark. 4. Set one profile as the default — it is used on external link and file request pages when no specific profile is selected. ### Viewing analytics 1. Go to **Drive → Admin → Analytics**. 2. The dashboard shows storage usage, file counts, and activity trends. 3. Analytics data can be exported to CSV. ## 5. Settings All settings live under **Drive → Admin → Settings**. Every setting below has a real runtime effect. | Setting | Section | Default | What it changes | |---|---|---|---| | **Enable Drive Help Agent** | Drive AI agents | On | Enables the read-only AI assistant that finds files by name and lists recent and shared files — and, when **Embed file contents for AI search** is on, summarizes files and finds them by description. Turning it off hides Drive from Ask AI entirely, the Drive Admin Agent included | | **Include Drive in Global Search** | General | On | Drive files appear in the platform's global search results | | **Enable Stale-Content Governance Reviews** | General | On | Files not updated in 120 days are surfaced to the content governance review pipeline, prompting the owner to upload a new version of anything out of date or move what nobody needs to the Trash | | **Max upload size (MB)** | General | 500 | Maximum size of a single file upload, in megabytes | | **Allow tokenized external share links** | External links | On | Users can create public share links. Turning this off stops new links and pauses every link already sent; the paused links work again if it is turned back on, so revoke a link to end it for good | | **Require password on external links** | External links | Off | Every external link must have a password set before it can be created; saving it on also turns off live links that were made without one | | **Max external link lifetime (days)** | External links | 30 | Upper limit on how long an external link can remain active | | **Max file request lifetime (days)** | Inbound file requests | 30 | Upper limit on how long a file request can remain open | | **Enable Drive Admin Agent** | Drive AI agents | Off | Enables the write-capable AI agent that can create folders, share files, make and turn off share links, revert versions, and trash items — restricted to managers and Drive App Admins, and requires user confirmation before each action. It also needs the Drive Help Agent on | | **Notify users when files are shared with them or their access is removed** | Notifications | On | In-app notification when someone is given access, their role changes, or their access is removed and they can no longer open the item | | **Notify users when a new version is uploaded or restored** | Notifications | On | In-app notification to members when a new version of a file is added, or an earlier version is restored as the current one | | **Notify an internal recipient in-app when invited to a file request** | Notifications | On | In-app notification to the invited user (if they are a member of your organization) when a file request is created | | **Notify requester when file-request uploads arrive** | Notifications | On | In-app notification to the requester when external uploads land | | **Keep prior versions of files** | Versioning & semantic search | On | Retains version history. When off, each upload replaces the previous version immediately | | **Embed file contents for AI search** | Versioning & semantic search | Off | Extracts text from uploaded files and sends it to an external embedding provider, so content search and the Drive Help Agent can search by meaning and summarize files, not just match filenames | | **Versions retained per file** | Versioning & semantic search | 20 | How many versions to keep per file. Older versions beyond this count are pruned after each new upload | ## 6. More help - **Drive FAQ** — specific setup and operating questions, limits, and troubleshooting. - Ask AI — the assistant answers questions about Drive from these articles. **Keywords:** drive, file management, file sharing, shared drive, personal drive, file versioning, external share link, file request, upload files, drive branding, drive permissions, drive AI agent, workspace drive, file storage --- # Drive FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Drive — for the admin running it. # Drive FAQ Answers to common setup and operating questions about Drive. For what the app is and how to set it up from scratch, see the [Drive Overview](/help/articles/drive_app_overview). --- ## Setup ## Does Drive need any configuration before people can use it? No. Once a business admin enables Drive from Admin → Apps → All Apps, every user gets a personal "My Drive" automatically the first time they open the app, and every workspace gets its own Shared Drive. Versioning and notifications are on by default. Two settings are worth reviewing early: - **Embed file contents for AI search** is **off** by default. Turn it on if you want people to search inside documents and the Drive Help assistant to summarize files or find one by description. While it is on, file contents are sent to an embedding provider. - **Allow tokenized external share links** is on by default. If your policy forbids sending files outside the organization, turn it off before people start making share links. ## Who can manage Drive settings, branding, and analytics? Business admins (admin or above) and anyone you have added as a Drive **App Admin**. Both roles see the Admin section in the left sidebar with Branding, Analytics, and Settings. --- ## Permissions and access ## What sharing roles exist, and what can each one do? Drive has four sharing roles, from least to most privilege: **Viewer** (browse and download), **Commenter** (add comments), **Editor** (upload, rename, move, trash, and upload new versions), and **Manager** (all of the above plus share with people, create external share links, and request files). You grant a role to a person on a file or folder, from its **Share** panel, and a role on a folder is inherited by everything inside it. These are Drive roles, separate from anyone's role in your organization: a person whose organization role is Manager still needs Drive's Manager role on a file to share it. A workspace's Shared Drive is not shared from a panel: its members reach it through the workspace. Workspace owners and members get Editor on the drive, and workspace viewers get Viewer. ## Why can't someone see a Shared Drive I set up? Shared Drives come from workspaces: Drive creates one for each workspace, and there is no screen to create one any other way. A user sees a Shared Drive in the sidebar when they are a member of its workspace, when the drive is open to everyone in your organization, or when they are a business admin or Drive app admin. To give someone the whole drive, add them to the workspace. To give them one file or folder without the rest of the drive, share that item with them from its **Share** panel; it then appears under **Shared with me**. ## How does the admin override work? Business admins automatically receive Manager access on every drive in their organization — every Shared Drive and every person's My Drive — without being shared in. Drive App Admins receive Manager access on every Shared Drive and on their own My Drive, but not on colleagues' personal drives; to recover a file from someone's My Drive, ask a business admin. Both can manage Drive's settings. --- ## Day-to-day ## How does version history work, and how many versions are kept? Re-uploading a file with the same name — or saving through the Office add-in — creates a new version. Each version stores its own author, size, content type, and an optional change summary. You can view, download, or restore any prior version with one click. By default Drive keeps the latest **20 versions** per file. The admin can change that number in Settings under **Versions to Retain Per File**, or turn **Keep Prior Versions of Files** off entirely — in that case each save simply replaces the current file and no history is kept. ## How do external share links work? A user with Manager access on a file or folder can create a tokenized public link from the **External share links** section of its **Share** panel. The link can optionally be password-protected, given an expiration date, and given a download-count limit. If the expiration date is left blank, the link lasts as long as the **Max external link lifetime (days)** setting allows, which is **30 days** by default. Any date further out than that cap is automatically clamped to it. Admins can require passwords on all external links with **Require password on external links**, limit who may create them under **Who can create external share links?**, and turn external links off entirely with **Allow tokenized external share links** — turning that off pauses every link already sent, and the links work again if it is turned back on; revoke a link to end it for good. ## How do file requests work? File Requests let you invite an outside recipient to upload files into a folder you choose. You can set an expiration date, a maximum file count, a recipient email, and a branding profile. If no expiration is specified, the request defaults to **14 days** (or the lifetime limit, if that is shorter). The admin-configured **Max file request lifetime (days)** (default **30 days**) caps any date further out, and lowering it also shortens requests already open. When a recipient uploads files, the requester is notified. You see the requests you created; business admins see every request, and Drive app admins see requests into Shared Drives and their own My Drive. ## What notifications does Drive send, and can I turn them off? Drive sends in-app notifications in these situations; the first four are each controlled by their own toggle in Settings (all on by default): 1. **Notify Users When Files Are Shared With Them or Their Access Is Removed** — fires when someone is given access to a file or folder (unless they already have more access through a folder above it, the drive or their workspace), when their role changes, and when their access is removed and they can no longer open it. 2. **Notify Users When a New Version Is Uploaded or Restored** — fires for all members who can see the file, both when someone uploads a new version and when an editor restores an earlier one. 3. **Notify an Internal Recipient In-App When Invited to a File Request** — fires when the recipient email matches a user in your organization. 4. **Notify Requester When File-Request Uploads Arrive** — fires when external files land. Drive also tells a file's creator and earlier commenters about a new comment, tells a link's creator when your link rules turned off or ended their share link, and sends automatic reminders when a share link or file request is approaching its expiration date. These have no toggle in Settings. Individual users can opt out of any Drive notification through their personal notification preferences (Drive notices appear in the app; Drive sends no email except the file-request emails). ## Can other apps store files in Drive? Yes. Drive doubles as the platform's file backend. Apps like Broadcasts and Workspace attach files into a per-business system drive, so each attachment gets Drive's version record and activity trail automatically. That system drive is not shown in Drive: people open an attachment from the post or message it came with, and who can see it follows that post or message. --- ## When something looks wrong ## "I uploaded a file but it replaced the old one instead of creating a new version" Check whether the admin has turned **Keep Prior Versions of Files** off in Settings. When versioning is disabled, each upload replaces the current file and no history is kept. Turn the setting back on to start retaining versions going forward — the previously overwritten content cannot be recovered. ## "I can't create an external share link" Five possible causes: (1) the admin has turned off **Allow tokenized external share links** in Settings, (2) the admin has limited **Who can create external share links?** to people you are not among, (3) **Drive Share Links** is switched off in the Portals catalog, (4) the admin requires a password and you did not enter one, or (5) you do not have Manager access on the file or folder (the Drive role). In the first three cases the **External share links** section of the Share panel says so in place of the form; in the fourth the form asks for a password; in the fifth the section is not shown at all. ## "I trashed a file and now I can't find it to restore it" Each drive has its own Trash. Open the drive the item was in and choose **Trash** at the top of its page; the **Trash** entry in the left sidebar opens your My Drive's Trash. Items can be restored for **30 days** after deletion. After that window the item is no longer restorable. If a name collision exists when you restore — because someone created a new item with the same name — the restored item is automatically renamed (e.g. "report (1).docx"). ## "I restored a folder but its contents are still in the Trash" When a folder is trashed, all its descendants are trashed with the same timestamp. Restoring the folder automatically restores descendants that were trashed at that same moment. Items that were trashed individually before the folder was trashed (they carry a different timestamp) stay in the Trash and must be restored separately. ## "Search only matches filenames, not what's inside the document" Two things to check. In-app content search requires the **Embed file contents for AI search** setting to be on — it is **off** by default, and a Drive admin turns it on in Drive Settings. When it is on, switch the search bar mode to **Contents** to search inside documents. Platform-wide Global Search only matches Drive item filenames, not document content — that is by design. ## "I can see a file in Recent but not in Shared Drives" A file can show up in Recent because you accessed it through a direct share (item-level membership) even though you are not a member of the drive it belongs to. That file will appear in your **Shared with me** list but not in the Shared Drives sidebar section, because the sidebar only lists drives where you have drive-level access. --- ## Licensing and limits ## Does Drive require a licence? Yes. Drive requires a licence and is turned on per business by an admin from Admin → Apps → All Apps. It is not enabled by default. There is no separate per-file charge. ## What are the limits I should know about? | Limit | Default | Configurable? | |---|---|---| | Max file upload size | 500 MB | Yes — **Max File Upload Size (MB)** in Settings | | Versions retained per file | 20 | Yes — **Versions to Retain Per File** in Settings | | External link max lifetime | 30 days | Yes — **Max External Link Lifetime (days)** in Settings | | File request max lifetime | 30 days | Yes — **Max file request lifetime (days)** in Settings | | File request default expiry (when left blank) | 14 days | No | | Trash restore window | 30 days | No | | File/folder name max length | 250 characters | No | | Drive name max length | 200 characters | No | | Stale-content governance review interval | 120 days | No | --- ## More help - [Drive Overview](/help/articles/drive_app_overview) - Ask AI — the assistant answers Drive questions from these articles. **Keywords:** faq, drive, files, folders, upload, versioning, external link, file request, sharing, permissions, trash, storage, search --- # Employee Data Administration **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-14 How to configure employee profiles, profile fields (built-in and custom), employee change requests, compliance tracking, leave types, and accrual policies — the admin guide to the People app and Leave Configurations. # Employee Data Administration ## 1. What it is Employee Data Administration covers two connected admin surfaces: the **People** app (its admin pages are under **People › Admin** in the left sidebar) and **Leave Configurations** (Admin → Leave Configurations). Together they are the system of record for employee profiles, field-level permissions, compliance deadlines, leave types, and accrual policies. - **Enablement:** People is a licensed marketplace app (`employee-data-management`) that an admin enables per tenant. Leave Configurations requires the Leave Management app to be enabled. - **What it is not:** this is not the employee-facing profile page. Employees see their own profile under their user record; this article covers the admin controls that govern what fields exist, who can see and edit them, what leave employees can request, and how accruals are calculated. ## 2. Standing it up ### People 1. Go to **Admin → Apps → All Apps** and enable the **People** app. 2. Go to **People › Admin › Settings**. Its sections are listed in the rail on the left. 3. In **General**, review **Enable Employee Self-Service** (on by default). When on, employees can change the fields set to **Employee Self-Edit** on their own profile. When off, employees cannot edit their own profile; admins still can. 4. In **Employee requests**, review **Let employees request changes, with approval** (on by default for new organizations). It turns on the **Request Update** links employees use to ask for changes to the profile fields they cannot edit themselves, and routes those requests for approval. While it is off, the profile offers no way to request a correction to such a field. While **Enable Employee Self-Service** is on and the People AI Agent's **Record Management** capability is on, Ask AI can still send a request for an employee's own phone, work phone, address, time zone or emergency contact when it is a field they cannot edit, and it comes to **Pending Requests**. 5. If your organization needs data beyond the built-in standard fields, confirm **Enable Custom Fields** in **General** is on (it is on by default). 6. Go to **People › Admin › Profile Fields**. This one page lists the built-in standard fields and your custom fields together, grouped by profile section. Set which fields are active and required, who can edit and see each one, and which appear as a column in the employee directory. Click **New Field** to add a custom field. ### Leave Configurations 1. Go to **Admin → Apps → All Apps** and enable the **Leave Management** app. 2. Go to **Admin → Leave Configurations**. 3. Click **Load Defaults** to create leave types from an industry template, or click **New Leave Type** to create them manually. 4. For each leave type that uses balance tracking, create an **Accrual Policy** and assign employees to it. A policy marked as default for its leave type applies automatically to any employee without an explicit assignment. 5. Go to **Admin → Leave Configurations → Notifications** to configure who gets notified on leave events and to set the approval authority (manager-based or specific groups). ## 3. How it fits together ### Standard fields vs custom fields Both kinds are managed on one page, **People › Admin › Profile Fields**, where the **All**, **Built-in** and **Custom** filters switch between them. **Standard fields** are the built-in profile attributes, organized into seven sections: Personal Information, Contact Information, Employment Details, Compensation, Compliance & Legal, Onboarding, and Offboarding. Each has a **Visible to** level (Admins Only, Employee + Admins, Managers & Above, or Everyone), an **Edit** permission (Employee Self-Edit, Manager Editable, or Admin Only), and a risk category (routine, standard, or critical) that determines how update requests are routed for approval. Editing implies seeing: a field's edit permission sets the lowest visibility it can have. **Custom fields** are fields your team creates, stored in the employee's metadata. They support 16 field types (text, textarea, number, email, phone, url, select, multiselect, radio, checkbox, date, datetime, time, file, currency, and rating). New custom fields can be added only while **Enable Custom Fields** is on. Each one is filed under a profile section — the same sections as the standard fields, plus Additional Information — and has the same visibility and edit controls. The two are independent: turning **Enable Custom Fields** off does not hide standard fields, and the custom fields you already have stay listed on Profile Fields. Standard fields cannot be deleted — only deactivated. ### Leave types and accrual policies A **leave type** defines a category of time off (e.g., Vacation, Sick Leave). Key properties include whether it requires approval, whether it deducts from a balance, whether negative balances are allowed, how many advance-notice days are required, and whether supporting documentation is required (and after how many days). An **accrual policy** controls how balances grow for one leave type. It sets the accrual frequency (monthly, bi-weekly, etc.), accrual amount per period, maximum balance cap, carryover rules, a waiting period before accruals begin, and whether new hires are prorated. Policies can have **accrual rules** that vary the rate based on tenure or employment type. One policy per leave type can be marked as the **default** — employees without an explicit policy assignment accrue under the default automatically, and those employees do not appear in the policy's assigned-users list. Leave types can be restricted by **jurisdiction** so that employees in a given country or state see only the types available to them. The availability matrix at Admin → Leave Configurations → Availability controls this. ### Profile update routing When **Let employees request changes, with approval** and **Enable Manager-Level Approvals** are both on, requests to change fields set to **Manager Editable** go to the employee's direct manager first. If the manager does not act within the reminder window, a reminder is sent. After the escalation window, the request escalates to an admin. A request still undecided after the expiry window expires, and the employee is asked to resubmit. Fields set to **Admin Only** go to HR or an admin, and skip the manager — unless an auto-approval rule approves them, or an approval workflow you configured for that field or section adds a manager step. Fields set to **Employee Self-Edit** need no request while **Enable Employee Self-Service** is on: the change applies when the employee saves it — except gender, date of birth, marital status and pay fields, which always go through a request. ### Compliance tracking The People dashboard surfaces five compliance categories: missing emergency contacts, expiring visas, I-9 reverification due, probation periods ending, and incomplete profiles. Each has a drill-down list and supports sending compliance reminders to the affected employees, in the app and by email to those with an email address. The visa and probation alert windows are set in **People › Admin › Settings › Dates and alerts**. ## 4. Running it ### Configuring field visibility and editability 1. Go to **People › Admin › Profile Fields**. Use the section filter, **Search fields**, or the **All** / **Built-in** / **Custom** filters to find a field. 2. For each field, set **Required** and **Active**, its **Edit** permission (Employee Self-Edit, Manager Editable, or Admin Only) and who it is **Visible to**, and whether it shows as a **Directory** column (this needs Everyone visibility). 3. Click **Save Changes** to apply changes in bulk. Some fields are permanently required — First Name, Last Name and Work Email show a checkmark in the **Required** column instead of a toggle, and cannot be made optional. Fields that are always visible show a fixed **Everyone** badge under **Visible to** and cannot be hidden. ### Managing leave types 1. Go to **Admin → Leave Configurations → Manage**. 2. Click **New Leave Type** to create one, or click a leave type's name to edit it. 3. To load a set of preconfigured types, click **Load Defaults** and select an industry template. 4. Leave types with existing leave requests cannot be deleted — the delete option is hidden for those types. 5. To export all leave types as CSV, click **Export**. To import from CSV, use the **Import** button on the Manage page. ### Assigning employees to an accrual policy 1. Go to the policy's detail page via **Admin → Leave Configurations → Manage → [Policy Name]**. 2. Open the **Assigned Users** tab and click **Assign Employees**. 3. Use the search and department/location filters to find employees. Select individuals or click **Assign All** for the filtered set. 4. Assignments of 25 or more employees are processed in a background job; smaller batches are saved immediately. 5. To remove an employee, click the unassign action next to their name. ### Sending compliance reminders 1. Go to **People › Overview** (the dashboard). 2. Click a compliance card (e.g., "Missing Emergency Contacts") to see the affected employees. 3. Select employees and click **Send Reminders**. Each receives an in-app notification, and an email if they have an email address, linking to their profile edit page (or their profile overview if **Enable Employee Self-Service** is off). ### Regenerating employee IDs 1. Go to **People › Admin › Settings › Employee IDs** and choose how the employee ID is generated: **Auto-generated**, **By employment type**, or **Custom pattern**. For a custom pattern, type any fixed text and use **Add field** to insert values such as a sequence number or the last 4 digits of the phone number. Click **Save Settings**. 2. The format applies to new employees. To apply a saved custom pattern to existing employees, click **Regenerate Mango IDs** in the same section. It opens a dry run of how existing IDs would change, covering up to 5,000 employees. 3. Click **Apply to all employees** to enqueue a background job that applies the pattern to all employees. ## 5. Settings ### People settings These settings are at **People › Admin › Settings**, one section at a time from the rail on the left; the **Where** column names the section. They are stored with the rest of your business configuration, and each one falls back to the default shown below until an admin changes it. | Setting | Where | Default | What it changes | |---|---|---|---| | Enable Custom Fields | Settings › General | On | When off, no new custom fields can be added on Profile Fields and the Custom Fields tab is hidden on employee profiles; built-in fields are unaffected | | Enable Employee Self-Service | Settings › General | On | Lets employees change the fields set to Employee Self-Edit on their own profile; when off, employees cannot edit their own profile, and admins still can | | Let employees request changes, with approval | Settings › Employee requests | On for new organizations | Shows the **Request Update** links employees use for fields they cannot edit themselves, and routes those requests for approval | | Enable Manager-Level Approvals | Settings › Employee requests | On | Routes requests for Manager Editable fields to the employee's direct manager instead of HR or an admin | | Send Reminder After (days) | Settings › Employee requests | 3 | Calendar days before the manager is reminded about an undecided request | | Escalate to Admin After (days) | Settings › Employee requests | 5 | Calendar days before an undecided request escalates to HR or an admin | | Expire Undecided Requests After (days) | Settings › Employee requests | 30 | Calendar days before an undecided request expires and the employee is asked to resubmit (0 = never) | | Who can see the org chart | Settings › Org chart | Everyone in the organization | Limits the chart to managers and administrators, administrators only, or one group; administrators always see it | | Default Probation Period (days) | Settings › Dates and alerts | 90 | Estimates a probation end date when an employee has none set | | Visa expiry dashboard window (days) | Settings › Dates and alerts | 60 | How far ahead expiring visas appear on the compliance dashboard | | Probation end dashboard window (days) | Settings › Dates and alerts | 14 | How far ahead ending probation periods appear on the compliance dashboard | | Seniority Calculation Method | Settings › Seniority and agreements | Calendar Years (based on hire date) | How seniority is computed: by calendar years or by approved timesheet hours worked | | Enable CBA Planner | Settings › Seniority and agreements | Off | Enables the Collective Bargaining Agreement planner | | Premiums | Timesheets → Settings | Off | Enables premium pay and the Premium Types surface. Configured in Timesheets, not here — the value is still stored with the People settings, but the checkbox moved | | Employee ID format | Settings › Employee IDs | Auto-generated | How employee IDs are generated: **Auto-generated** (random), **By employment type** (sequential codes per type), or **Custom pattern** (a template you build) | ### Former Employee Portal settings These are in **People › Admin › Settings › Former employees**. | Setting | Where | Default | What it changes | |---|---|---|---| | Enable Former Employee Portal | Settings › Former employees | Off | Activates the former employee self-service portal | | Portal Access Duration (years) | Settings › Former employees | 7 years | How long a former employee can access the portal after termination | | Access Token Validity (days) | Settings › Former employees | 3 days | How long a portal access link remains valid | | Allow On-Demand Experience Letters | Settings › Former employees | On | Former employees can request experience letters | | Allow Salary Information in Letters | Settings › Former employees | Off | Whether experience letters include compensation details | | Auto-Send Portal Access on Termination | Settings › Former employees | On | Automatically sends portal access when an employee is terminated | ### Leave Configurations settings Leave notification and approval settings are stored with the Leave Management app's own configuration rather than with the business-wide settings. | Setting | Where | Default | What it changes | |---|---|---|---| | AI Agent | Admin → Leave Configurations → Notifications | On | Enables the Ask AI leave management agent for employees | | Auto-Approve Max Days | Admin → Leave Configurations → Notifications | Per executor default | Maximum leave duration the AI agent can auto-approve | | Partial-Day Leave | Admin → Leave Configurations → Notifications | Off | Allows employees to request timed partial-day leave with start and end times | | Show Team Availability | Admin → Leave Configurations → Notifications | Off | Shows team members' leave schedules when an employee is requesting leave | | Approval Authority | Admin → Leave Configurations → Notifications | Managers | Who can approve leave: managers (reporting chain) or specific designated groups | ## 6. More help - **Employee Data Administration FAQ** — specific setup and operating questions (not yet published) - **Users, Roles & Permissions** — how to manage user accounts and role assignments - Ask AI — the assistant answers questions about employee data and leave configuration from these articles. **Keywords:** employee data, people app, employee profiles, profile fields, custom fields, standard fields, leave types, leave configurations, accrual policies, compliance tracking, visa expiration, I-9 reverification, probation, profile completion, employee ID, mango ID, former employee portal, self-service, employee requests, request update, approval routing, leave accrual, org chart, employee records --- # Enabling Apps, Licences & Plugins **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-16 How a tenant admin enables, configures, publishes, and controls access to apps in OneMango — licensing, visibility rules, pinning, app admins, and the App Builder plugin surface. # Enabling Apps, Licences & Plugins ## 1. What it is The Apps page is where a tenant admin turns platform capabilities on and off. Every feature in OneMango — scheduling, leave, recognition, forms, chat, and dozens more — is a marketplace app that an admin explicitly enables, configures, and rolls out to users. This page is the control surface for that lifecycle. - **Access:** Admin → Apps → All Apps. Requires the Administrator or Super Admin role. - **What it is not:** This page does not change your subscription. It is where you enable apps your organisation already has access to, and control who sees them. To get an app you do not have yet: on a self-serve plan, add it yourself — an app priced per specialist from its own page (**Add to plan**, an add-on to a suite you already have), a suite from **General Settings → Billing & Payments → Plan**, or an employee suite with **Ask for company pricing** on the same tab. On a plan managed by a MangoApps account team, your account manager adds it. ## 2. Standing it up There is no first-time setup — the Apps page is available to every admin immediately. The work is enabling the apps your organisation needs: 1. Go to **Admin → Apps → All Apps**. You see every app in the catalogue, grouped by category. A status filter lets you narrow to Enabled, Available, or Requires Licence. 2. Find the app you want. Click **Enable**. If the app requires a licence your organisation does not yet have, the message names the suite it belongs to and what to do next: on a self-serve plan, add it to your plan from its page, or ask for company pricing under **Billing & Payments → Plan**; on a managed plan, contact your account manager. 3. A newly enabled app starts as **admin-only** — your users cannot see it yet. The confirmation message tells you this and links to access management. 4. **Configure** the app before rolling it out. Click the app name to open its detail page, then click **Configure** to set its options. A "Setup Health" badge on the Apps list flags apps still running on default settings. 5. **Roll it out.** On the app's detail page, open **Access management** and either click **Publish to everyone** (all users see it) or add visibility rules to grant access to specific groups. 6. Confirm it worked: your users should now see the app in their sidebar or Apps panel (if pinned), and at its route. ## 3. How it fits together **Licence → Enable → Configure → Publish** — four gates, in order. An app that is licensed but not enabled does nothing. An app that is enabled but not published is visible only to admins. Skipping the configure step is safe but means the app runs on its schema defaults, which may not match your organisation's needs. Understanding these four stages is the key to a smooth rollout. **Licensing** — Most apps are licensed: they are marked as requiring a licence and stay unavailable until your business is entitled to them. Entitlement comes from one of four sources: a direct licence grant from your account manager, inclusion in your Platform edition, inclusion in a suite your organisation subscribes to, or an add-on app line on your plan. **Pay-as-you-use apps have no licence gate at all.** They are available to every tenant and draw platform credits as they are used rather than billing by seat. None is on automatically: each stays off until an admin enables it, and an app nobody turns on costs nothing. App Builder is not one of them — it comes with your Platform edition. **Published vs admin-only** — When you first enable an app, it is not yet published to users. Admins can see and use it immediately, but end users cannot. This gives you time to configure it, load sample data, and test before rolling it out. You promote it to users in one of two ways: "Publish to everyone" makes it visible organisation-wide, or adding a visibility rule makes it visible only to the members of a specific group. **Visibility rules** — A visibility rule ties an app to a group (Admin › Groups). Only members of that group see the app. Multiple rules are additive — a user who is in any of the listed groups has access. When the last visibility rule is removed, the app falls back to its published state (either visible to everyone, or admin-only). **App Admins and Contributors** — Beyond the organisation-wide Administrator role, individual users can be assigned as app-level administrators or contributors for a specific app. An app admin can configure the app (schema, settings, destructive operations). A contributor can work with records (create, edit) but never the structure. These assignments are per-app, per-business, and managed from the app's detail page. **Categories** — Apps are organised into eight categories: Scheduling, Recruiting, HR Operations, Learning & Growth, IT Services, Workplace Ops, Platform, and Productivity & Utility. The Apps list groups by category and the toolbar has a category filter chip. Custom apps (plugins) default to Productivity & Utility when no category is set. **Configuration** — Most apps declare a configuration schema that drives a generic settings form at Admin → All Apps → (app) → Configure. The schema defines the fields, types (boolean, select, multi-select, integer, slider, date range, time range, and others), and defaults. Saving the form merges only the schema-declared settings into the existing configuration — settings written by the app's own settings page are preserved. **Setup Health** — The Apps list shows a badge when an enabled app has a configuration schema and every key still matches its schema default. This is a signal that the admin enabled the app but never customised it, which may mean it is not behaving as intended. **System apps vs custom apps** — System apps ship with the platform and are managed by MangoApps. Custom apps (plugins) are built by your organisation or installed from the plugin marketplace. Custom apps auto-grant a licence when enabled and can be fully uninstalled (including their data). System apps cannot be deleted — only enabled or disabled. **Agent capability** — Some apps are AI-integrated (they have an AI agent that can take actions), some are agent-only (they exist purely as an AI agent with no traditional UI), and some have no agent capability. The Apps list shows a badge indicating each app's agent type, and a capability filter lets you narrow by type. ## 4. Running it ### Enabling an app 1. Go to **Admin → Apps → All Apps**. 2. Find the app. Click **Enable** on its row or from the app's detail page. 3. If a licence is required and not available, the error message names the suite the app belongs to and how to add it (see step 2 of *Standing it up*). 4. On success, the app is enabled and admin-only. The confirmation message tells you how to publish it. ### Disabling an app 1. Go to **Admin → Apps → All Apps**. 2. Find the enabled app. Click **Disable** from its row actions. 3. Disabling unpins the app from the sidebar and hides it from all users. The app's configuration is preserved — re-enabling it restores the previous settings. ### Publishing an app to users 1. Click the app's name to open its detail page. 2. Open the **Access management** panel. 3. Click **Publish to everyone** to make the app visible organisation-wide, or add one or more visibility rules to target specific groups. 4. To pull an app back to admin-only, click **Unpublish**. The app stays enabled and admins retain access, but end users can no longer see it. ### Configuring an app 1. Click the app's name, then click **Configure**. 2. The form shows every setting the app declares in its schema. Change values and click **Save**. 3. Some apps also have a dedicated settings page inside the app itself. The app's detail page links to it when one exists. ### Managing app admins 1. On the app's detail page, find the **Admins & Contributors** card (**App Admins** on an app that has only the admin role) and click **Manage Admins & Contributors** (**Manage App Admins**). 2. Click **Add Admin** (**Add App Admin**). In the panel that opens, search for the person by name or email and choose the role — **App admin** or **Contributor**, and on specialist apps **Collaborator** — then save. 3. To change or remove someone, use the actions on their row. ### Bulk operations The Apps list supports selecting multiple apps and then clicking **Bulk Enable** or **Bulk Disable**. Apps that require a licence your organisation does not have are silently skipped during bulk enable — the confirmation message reports how many were skipped and why. ### Pinning an app to the sidebar 1. On the Apps list, toggle the pin icon on the app's row. 2. The app icon appears in the sidebar rail for all users who have not personalised their own rail. The sidebar rail holds a maximum of 7 pinned apps. If all slots are full, unpin one first. 3. An app must be enabled before it can be pinned. Only enabled apps can be pinned. ### Plugins (App Builder) The Plugins surface at **Admin → Apps → Custom Apps** is a separate page for apps built with the App Builder SDK. From here you can: 1. **Upload** a plugin from a zip file or **install** one from the plugin marketplace. 2. **Enable or disable** a plugin for your business. 3. **Deploy** a new version (reloads the plugin's code without a container restart). 4. **Roll back** to a previous version if a deploy causes issues. 5. **Uninstall** a plugin entirely — this runs the plugin's cleanup hook, purges its per-business data, and removes the marketplace link. Customer-created plugins skip the licence requirement — the licence is auto-granted when you enable them. Plugins that have been shared to the plugin marketplace can be installed by other organisations from the **Marketplace** tab within Custom Apps. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | App enabled | Admin → All Apps → Enable/Disable | Not enabled | Whether the app is active for your organisation | | Published to users | Admin → All Apps → (app) → Access management → Publish | Not published | Whether end users can see the app, or only admins | | Pinned to sidebar | Admin → All Apps → pin toggle | Not pinned | Whether the app icon appears in the sidebar rail | | Per-app configuration | Admin → All Apps → (app) → Configure | Schema defaults (varies per app) | App-specific behaviour defined by its configuration schema | | RAG enabled | App detail page → Agent Settings | Off (shown as **RAG Disabled**) | Whether the app's knowledge base is available to the AI agent | ## 6. More help - **Apps & Licensing FAQ** — specific questions about licensing, access, and troubleshooting - **Settings Hub & Navigation** — finding settings and navigating the admin sidebar - **Billing & Payments** — managing your organisation's plan, invoices and payments - Ask AI — the assistant answers questions about app configuration from these articles. **Keywords:** enable app, disable app, app marketplace, apps, license, licence, licensing, publish app, app admin, visibility rules, app access, plugins, app builder, pin app, configure app, app settings, rollout, admin only --- # E-Signature App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run E-Signature — creating signature requests, placing fields, templates, kiosk mode, bulk sends, and compliance settings. # E-Signature ## 1. What it is E-Signature lets you send PDF documents for electronic signature with visual field placement, sequential signing order, and a full audit trail. Signers receive a tokenized link by email, sign in their browser, and the completed document is stored with a signing certificate. - **Enablement:** E-Signature is a pay-as-you-go app billed per envelope sent. It is available to every tenant with no license decision required — an admin enables it from Admin → Apps → All Apps. - **What it is not:** E-Signature is the standalone document-signing surface. Other apps (Offer Manager, Contracts, Onboarding Hub, HR File Manager, Policy Hub) each have their own "send for signature" leg that creates requests through E-Signature behind the scenes. Those integrations are configured in the consuming app, not here. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **E-Signature**. 2. Go to **Apps → E-Signature → Settings**. Review the defaults. The most important choice is **Who Can Send Documents** — the default is **All users**, meaning anyone in the organization can create and send signature requests. Change to **Managers only** or **Admins only** to restrict. 3. Decide whether external signers are allowed. **Allow External Signers** is on by default. Turning it off means every signer's email must belong to a member of your organization. 4. If you plan to use DocuSign or Dropbox Sign (HelloSign) instead of the built-in native signing, set up the provider integration at **Admin → Organization → Integrations** first, then select it as the **Default E-Signature Provider** in step 2. 5. Have a user go to **Apps → E-Signature → Requests → New Request**, upload a PDF, add signers, place fields on the document, and send. The signer receives an email with a link to sign. **What runs on its own from day one:** automatic reminders. **Send Automatic Reminders** is on by default, so a daily job emails each signer whose turn it is every 3 days until they act, for at most 60 days. Turn it off in Settings if you would rather chase signers yourself. ## 3. How it fits together ### Requests, signers, and fields A **request** is a document (or set of documents) sent for signature. It moves through these statuses: **Draft → Sent → Viewed → Partially Signed → Completed**. It can also be **Declined** (a signer refused), **Voided** (the sender cancelled it), or **Expired** (it passed its expiration date without completing). Each request has one or more **signers**, listed in a signing order. Signing is sequential — signer 2 cannot sign until signer 1 finishes. A signer can carry an optional role, such as "Employee" or "Manager": it is a label that templates use to place fields, and it does not change what the person must do — everyone listed must sign before the request completes. Signers can be internal (employees in your organization) or external (anyone with an email address), depending on the **Allow External Signers** setting. **Fields** are the form elements placed on the document's pages: **Signature**, **Initials**, **Date**, **Name**, **Text**, **Checkbox**, **Radio**, and **Dropdown**. Each field is assigned to a specific signer and can be marked required or optional. Fields are positioned visually on a PDF preview in the field editor. **Worked example:** You upload an NDA, add two signers — the employee (order 1) and the HR director (order 2). You drag a Signature field and a Date field onto the last page for each signer. You send the request. The employee receives an email with a signing link, completes their fields, and the HR director is notified it is their turn. Once both sign, the request moves to **Completed**, a signing certificate is generated, and a completion email goes to everyone. ### Templates A **template** saves field positions and signer roles so you can reuse the same layout across many documents. Templates have a category — **HR**, **Legal**, **Sales**, **General**, **Compliance**, **Onboarding**, or **Other** — and can be created from scratch, saved from a draft request's field editor with **Save as Template**, or cloned from another template. When you create a new request and select a template, its fields are pre-placed on the document. There are two kinds of templates: **custom templates** (created by your organization, scoped to your business) and **system templates** (global, available to all tenants). ### Native signing vs. external providers E-Signature has a built-in signing engine (the **Native** provider). Signers open a tokenized link in their browser, fill fields, and draw or type their signature. No third-party account is needed. If your organization uses DocuSign or Dropbox Sign (HelloSign), you can connect them at **Admin → Organization → Integrations** and select the provider as the default. Requests sent through an external provider use that provider's signing experience. You can also manually poll a provider for status updates with **Check Status** on a request. ### Integrations with other apps When a signature request completes, E-Signature notifies the consuming app automatically: - **Offer Manager** — marks the offer letter as signed. - **Contracts** — marks the contract document as signed and advances bulk-batch signature rollups. - **HR File Manager** — flips the file's badge from "Signature Required" to "Signed". - **Meal Compliance** — activates meal waivers waiting on a signature. - **Policy Hub** — acknowledges the policy document. These integrations fire on completion. No configuration in E-Signature is needed — the consuming app links the request when it creates it. ## 4. Running it ### Sending a request 1. Go to **Apps → E-Signature → Requests → New Request**. 2. Upload one or more PDF documents. Multiple documents are combined into a single PDF for field placement. 3. Add signers with name, email, and signing order. Optionally select a template. 4. In the field editor, drag fields onto the document pages. Assign each field to a signer. 5. Review the request on the **Confirm Send** page, then send immediately or schedule for later. Requests can also be **scheduled** for a future date and time. Scheduled requests remain in **Draft** until the scheduled time, when a background job sends them automatically. Scheduled sends that are more than 7 days past due are cleared rather than sent. ### Sending reminders When **Send Automatic Reminders** is on (the default), a daily job reminds the signer whose turn it is, at the configured **Reminder Frequency** (default: every 3 days). Reminders stop after 60 days. You can also send a reminder yourself from a request's detail page with **Send Reminder** — it goes to the signers whose turn it is, never to someone still waiting on an earlier signer. ### Voiding a request A sent request can be voided at any time before it completes. Voiding cancels the request for everyone: every signer it was still waiting on, and everyone who had already signed, is emailed that it was cancelled and that their link no longer works — outside signers included — and internal signers who were waiting also get an in-app notice. Voiding can't be undone; duplicate the request to send it again. ### Duplicating a request (revise and resend) Click **Duplicate** on any request to create a new draft that copies the documents, signers, and field placements. The copy belongs to the current user and starts fresh — no signed data carries over. ### Downloading results After a request completes, download the **signed document** (the original PDF with signatures overlaid) and the **signing certificate** (a separate PDF with the document hash, audit trail, signer IP addresses, and timestamps). ### Bulk sends Go to **Apps → E-Signature → Bulk Sends → New Bulk Send**. Upload a CSV with recipient names and emails, select a single-signer template, and preview before sending. Each row creates an individual request. Bulk sends are subject to the same **Who Can Send** restriction as individual requests. ### Kiosk mode Kiosk mode turns a shared device into a walk-up signing station. Go to **Apps → E-Signature → Kiosk → New Kiosk Session**, select a single-signer template, set a passcode (4–6 digits), and set the session timeout (default: 5 minutes). Open the kiosk link on the device. Each person enters their name and email, signs, and the station resets for the next person. The passcode is for staff: it is what you enter to take the device out of kiosk mode. ### Sharing requests A request creator or admin can share a request with individual users or groups. Shared users can open the request — its details, signers, status and the audit trail shown on the page — but cannot change it, and cannot download the signing certificate or export the audit trail, which carry signers' IP addresses. Go to a request's detail page and use the **Share** action. ### Exporting the audit trail From a request's detail page, click **Export Audit Trail** to download a CSV with every event: creation, sending, viewing, signing, declining, reminders, and voiding — each with a timestamp, user email, and IP address. ## 5. Settings All settings are at **Apps → E-Signature → Settings**. Only admins and app admins can access this page. | Setting | Default | What it changes | |---|---|---| | **Signers can open their signing links** | On | The incident switch: turn it off to pause every signing link E-Signature has emailed, all at once. While off, the links open a "not available" page and nothing is sent or reminded. Not covered: requests sent through DocuSign or Dropbox Sign, Policy Hub acknowledgments, and walk-up kiosks (close each kiosk under **Kiosk**). | | **Default Expiration (days)** | 30 | How long signers have before a request expires, counted from the day the request is created. An hourly job moves expired requests to the **Expired** status. | | **Default E-Signature Provider** | **Native (Built-in)** | Which provider handles single signature requests. Options: **Native (Built-in)**, **DocuSign**, **HelloSign (Dropbox Sign)**. External providers appear only after they are connected at Admin → Organization → Integrations. Bulk sends and walk-up kiosks always use the built-in signer. | | **Send Automatic Reminders** | On | A daily job emails the signer whose turn it is when they have not acted within the configured frequency, for at most 60 days. | | **Reminder Frequency (days)** | 3 | How often automatic reminders are sent to a pending signer. Only applies when automatic reminders are enabled. | | **Allow text messages (SMS)** | Off | Lets signers receive their identity-verification code by text message instead of email (when **Require Signer Identity Verification** is on), and lets Document Packages sent from Onboarding Hub, Offboarding and Contracts text their invitations and reminders. E-Signature's own signing invitations and reminders are sent by email. SMS usage is billed. | | **Who Can Send Documents** | **All users** | Who can create signature requests. Options: **All users**, **Managers only**, **Admins only**. This also gates bulk sends. | | **Allow External Signers** | On | Whether signers outside your organization can be added to requests and bulk sends. When off, every signer email must belong to a member of your business. Walk-up kiosks and Document Packages are not covered — anyone at a kiosk station can sign. | | **Generate Signing Certificate** | On | Whether a PDF signing certificate is generated when a request completes. The certificate includes the document hash (SHA-256), audit trail, and signer details. | | **Require Signer Identity Verification (OTP)** | Off | When on, signers must verify their identity with a one-time code — by email, or by text message when **Allow text messages (SMS)** is on — before they can sign. | | **Enable Trusted Timestamp (RFC 3161)** | Off | When on, a trusted third-party timestamp is embedded in the signing certificate for cryptographic proof of signing time. | | **Timestamp Authority** | FreeTSA | The authority that issues that timestamp: FreeTSA, DigiCert or Sectigo. | | **Signing Certificate Legal Notice** | United States | The law the certificate's Legal Notice cites: the US E-SIGN Act and UETA, or the UK's Electronic Communications Act 2000 and UK eIDAS (a simple electronic signature). | | **Show a custom message on the signing page** | Off | Shows the message you type in **Custom Signing Page Message** on the signing page. Your logo and colours on the signing page come from your portal branding, whether this is on or off. | | **Enable E-Signature Agent** | On | Whether people can use the E-Signature agent in Ask AI to check pending signatures, track request status, analyse documents and send reminders. | | **Enable AI Document Analysis** | On | Master switch for AI-powered document analysis. When on, uploaded documents are automatically analysed for summaries, key terms, risks, and field suggestions. Individual analysis features can be toggled independently below this switch. | ## 6. More help - **E-Signature FAQ** — specific setup and operating questions, limits, and troubleshooting. - Ask AI — the assistant answers questions about E-Signature from these articles. **Keywords:** e-signature, esignature, electronic signature, sign document, signing request, signature field, signing certificate, audit trail, docusign, hellosign, kiosk signing, bulk send, signer verification, OTP --- # E-Signature FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about E-Signature — for the admin running it. # E-Signature FAQ Answers to common setup and operating questions about E-Signature. For what the app is and how to set it up from scratch, see the [E-Signature Overview](/help/articles/esignature_app_overview). --- ## Setup ## What do I need to configure before my team can send documents? Nothing. E-Signature works with its built-in native signing provider out of the box, using default settings. The defaults are: expiration set to 30 days, automatic reminders on (every 3 days, to the signer whose turn it is), all users can send, external signers allowed, and signing certificates generated on completion. You can adjust any of these on the Settings tab. ## How do I connect an external signing provider like DocuSign or HelloSign? Go to Admin > Organization > Integrations, add a new integration in the "esignature" category for DocuSign or HelloSign, and enter your API credentials. Once the integration is active and enabled, the provider appears in the **Default E-Signature Provider** dropdown on the Settings tab. Requests sent through an external provider use that provider's signing flow and webhook-based status updates. --- ## Permissions and access ## Who can send signature requests? The **Who Can Send Documents** setting on the Settings tab controls this. It has three options: **All users** (the default), **Managers only**, or **Admins only**. App-level admins (granted through Admin → Apps → All Apps) can always send regardless of this setting. The same restriction applies to bulk sends. ## Who can see another person's signature requests? Admins and app-level admins see all requests in the organization. Managers see their own requests plus requests created by their direct reports. All other users see only requests they created or are named as a signer on. Anyone can also see a request that has been explicitly shared with them or with a group they belong to. ## How do I grant someone admin access to E-Signature without making them a full admin? Use Admin → Apps → All Apps to grant an app-level admin role for E-Signature. App-level admins can access E-Signature's Settings and Analytics tabs without any other admin privileges. **Document Packages** stays with full admins, because Onboarding Hub, Offboarding and Contracts build their packages from the same templates. --- ## Day-to-day ## What happens when I send a request with multiple signers? Every signer receives an invitation as soon as you send. The first signer's invitation asks them to sign; everyone after them is told it is not their turn yet, and gets a "your turn to sign" email (and an in-app notice, if they are a member) when the signers before them have finished. Reminders — automatic or the ones you send — go only to the signer whose turn it is. If any signer declines, the entire request moves to **Declined** status and remaining signers are not asked to sign. ## How do automatic reminders work? Automatic reminders are on by default. Turn them off with the **Send Automatic Reminders** toggle on the Settings tab. While on, the system sends a reminder to each pending signer at the interval set in **Reminder Frequency** (default every 3 days). Reminders respect the signing order — a signer whose turn has not arrived yet will not receive one. Reminders stop after 60 days regardless of the expiration window, so abandoned requests do not generate notifications indefinitely. ## Can I void a request after it has been sent? Yes. You can void any request whose status is **Sent**, **Viewed**, or **Partially signed**. Voiding cancels all outstanding signing links immediately — a signer who opens a voided request's link sees a message that the request is no longer active. Every signer it was still waiting on, and everyone who had already signed, is emailed that it was cancelled (outside signers included), and internal signers who were waiting also get an in-app notice. Voiding can't be undone; duplicate the request to send it again. ## How do I send the same document to many recipients at once? Use **Bulk Sends**. Choose a template that has a single signer role, upload a CSV file with one row per recipient (each row needs at least a name and email column), preview the list, and send. The system creates one individual signing request per recipient. A progress email is sent as the batch completes. If **Allow External Signers** is turned off, every email in the CSV must belong to a member of your organization. ## What is kiosk mode and how do I set it up? Kiosk mode turns a shared device into a walk-up signing station. Create a kiosk session from the Kiosk tab by choosing a single-signer template and setting a passcode (4–6 digits). Open the kiosk URL on the device. Each person enters their name and email, signs on screen, and the device resets for the next signer. The session timeout (default 5 minutes, maximum 60 minutes) controls how long a signer has before the session expires. The passcode is for staff only: enter it to exit kiosk mode. ## What AI document analysis features are available? When **Enable AI Document Analysis** is on (the default), signers and senders can use AI to summarize a document, ask questions about it, extract key terms, and detect potential risks — all before signing. Additional analysis toggles on the Settings tab cover PII detection, bias detection, sentiment analysis, compliance checking, content moderation, and readability scoring. Each can be turned off individually. A separate **AI Field Suggestions** toggle lets AI recommend where to place signature fields based on document content. ## What happens when all signers finish signing? The request moves to **Completed** status. The system generates a final signed PDF with all signatures overlaid, plus a signing certificate that records every audit event (created, sent, viewed, signed, completed) with timestamps and IP addresses. The creator and all internal signers receive a completion notification in their inbox and by email. If HR File Manager is enabled and configured to sync from E-Signature, the signed document is automatically filed there. --- ## When something looks wrong ## I received a signing link but it says "expired" — what happened? Signing links expire when the request reaches its expiration date (by default 30 days from the day the request was created — a draft kept for a while has less time left once it is sent, and one whose date has already passed cannot be sent until the sender sets a new one). An hourly background process checks for overdue requests and moves them to **Expired** status. Once a request expires, all its signing links stop working. Ask the sender to duplicate the request and resend it. ## It says I can't sign yet — why do I have to wait? The sender set a signing order. Each signer must complete before the next one can begin. You will receive a "your turn to sign" notification by email (and in your inbox if you are an internal user) as soon as all signers before you have finished. ## Why can't I create a new signature request? Your admin has restricted who can send documents. If the setting is **Managers only**, you need a manager role or above. If it is **Admins only**, only administrators and E-Signature app-level admins can create requests. Ask your admin to check the **Who Can Send Documents** setting on the E-Signature Settings tab. ## A signer says they never received the signing invitation — what should I check? First, confirm the email address on the request matches the signer's actual address (the system lowercases all signer emails). If the signer is external and **Allow External Signers** is turned off, external signers cannot be added in the first place. E-Signature's invitations are sent by email — **Allow text messages (SMS)** lets signers receive their identity-verification code by text (and lets Document Packages text theirs), but never sends a request's invitation by text. You can also click **Send Reminder** on the request to email a fresh link to the signer whose turn it is. ## A request shows "Declined" but only one signer refused — does that cancel it for everyone? Yes. When any signer declines, the entire request is marked **Declined** and no further signing is possible. The sender receives a notification with the signer's decline reason (if one was given). To continue, duplicate the request to create a fresh draft, remove or replace the declining signer, and resend. --- ## Licensing and limits ## Does E-Signature require a licence? No. E-Signature is a pay-as-you-go app, billed per envelope. It is available to every tenant without an upfront licence decision — an admin enables it from Admin → Apps → All Apps and usage is metered. ## What are the limits I should know about? - **Document format:** PDF only. - **Default expiration:** 30 days (admin-configurable on the Settings tab). - **Reminder frequency:** Every 3 days when enabled (admin-configurable); reminders stop automatically after 60 days. - **Kiosk session timeout:** Default 5 minutes, maximum 60 minutes per session. - **Kiosk passcode:** 4–6 digits. - **Template categories:** HR, Legal, Sales, General, Compliance, Onboarding, and Other. - **External providers:** DocuSign and HelloSign integrations are production-ready; other providers (Adobe Sign, PandaDoc, SignRequest, SignNow) have code in place but are not yet exposed in the UI. --- ## More help - [E-Signature Overview](/help/articles/esignature_app_overview) - Ask AI — the assistant answers E-Signature questions from these articles. **Keywords:** faq, e-signature, signing, document signing, audit trail, signing certificate, signer, kiosk, bulk send, template, OTP verification, external signer, reminders, expired, voided, esignature --- # Field Service Suite App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run Field Service Suite — work orders, dispatch, estimates, invoicing, service agreements, and optional modules for fleet, pricebook, GPS, accounting sync, and a customer portal. # Field Service Suite ## 1. What it is Field Service Suite manages the full lifecycle of field work: customer accounts, work orders, technician dispatch, estimates, invoicing, and recurring service agreements. It is built for organizations that send people to job sites — HVAC, plumbing, electrical, property maintenance, and similar trades. - **Enablement:** Licensed and opt-in. An admin enables it from Admin → Apps → All Apps; it is off by default. - **What it is not:** Field Service Suite is not the AI Front Office app. AI Front Office handles inbound customer calls, texts, and chat and can hand booked work into Field Service Suite, but they are separate apps with separate licenses. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Field Service Suite**. 2. Open **Field Service Suite → Settings** (visible only to app admins). Set the **Work Order Prefix** and **Invoice Prefix** if the defaults ("WO" and "INV") do not match your numbering scheme, and choose a **Default Priority** and **Default Tax Rate**. 3. Create at least one **Customer** under **Field Service Suite → Customers → New Customer**. Each customer needs a name; adding at least one **Site** (address) under the customer lets you tie work orders to a location. 4. Grant access using the standard app visibility rules. By default, all members of the business can see the app. Use **Access Management** to restrict it to specific departments or roles if needed. 5. Confirm it worked: any member should see the Field Service Suite tab in the apps list and can open the Dashboard. People who can write records — managers, and anyone given the app's **Contributor** role — also see **Dispatch**. **Invoices**, **Reports**, and **GPS & Routing** follow the choices in **Settings › Who Can Do What** (each starts at managers), and module tabs appear once their module is turned on. **Silent dependency:** The optional modules (Pricebook Pro, Fleet Pro, Customer Portal, GPS & Routing, Accounting Sync, Live Assist) are all off by default. Each must be turned on individually in **Settings → Premium Modules** before its tab appears in the sidebar. Turning on Accounting Sync also requires an enabled accounting integration (QuickBooks, Xero, or Sage) configured under **Admin → Organization → Integrations**. Turning on Live Assist requires the Live Assist app and a LiveKit meeting-provider integration. ## 3. How it fits together **Customers and Sites** — A customer is the company or person you do work for. Each customer can have multiple sites (service addresses). Work orders, estimates, invoices, and service agreements all link to a customer; work orders and estimates can also link to a specific site. Deleting a customer is blocked while any of these records exist. **Work orders** — The central record. A work order tracks a single job from creation to payment. It moves through a defined lifecycle: **Draft → Scheduled → Dispatched → In Progress → On Hold → Completed → Invoiced**. Terminal states (Invoiced and Cancelled) allow no further moves. Each work order has a type (Service, Repair, Install, Maintenance, or Inspection) and a priority (Low, Medium, High, or Urgent). Line items on the work order track parts, labor, and materials with quantity and price. There is no screen for adding line items to a work order: they are copied from the estimate when you convert it, or added through Ask AI ("add work order items"). To bill extra work, edit the invoice while it is still a draft, or create the invoice by hand. Example lifecycle: a work order WO-00042 is created as a Draft for customer Acme Property Management at their downtown site. An office manager schedules it for Thursday and dispatches it to a technician. The technician marks it In Progress on arrival, uploads job photos, captures the customer's signature, then marks it Completed. The office creates an invoice from the completed work order, which moves the work order to Invoiced. **Estimates and proposals** — An estimate is a priced proposal sent to a customer before work begins. Each estimate can contain multiple named options (for example, a basic repair option and a full replacement option). One option can be marked **Recommended**. When you send an estimate, the customer receives a link to a public proposal page where they can view the options and approve one by choosing it, or decline it with a reason. There is no signature step. Approving does not create a work order: the estimate's owner gets an action item, and someone with write access clicks **Convert to Work Order**. To re-quote a declined or expired estimate, use **Revise as a new quote**. Estimates that pass their expiration date are automatically marked expired by a daily sweep. **Invoices and payments** — An invoice can be created standalone or generated from a completed work order. Invoices follow their own lifecycle: **Draft → Sent → Viewed → Partially Paid → Paid** (or **Overdue** / **Void**). Invoices past their due date are automatically marked overdue by the same daily sweep. Payments are recorded with **Record Payment** on the invoice (cash, check, ACH, credit card, financing, or other). Field Service records payments; it does not take them — there is no Pay button on an invoice or in the customer portal. If you take card payments in your own Stripe account, turn on **Online Payments (Stripe)** in Settings and those payments are recorded on the matching invoice automatically, as long as the payment carries the invoice id. **Service agreements** — A recurring contract with a customer. Each agreement has a billing frequency (Monthly, Quarterly, Semi-annual, or Annual), a billing amount, and a contract window (start and end dates). Once an agreement is **Active**, a daily sweep automatically generates a draft invoice when the billing date arrives and, when **auto-schedule visits** is turned on, creates each visit's work order at the configured service frequency. Visit work orders are created unassigned, and the agreement's owner is told to dispatch them; draft invoices wait for someone to review and send them. Each agreement advances one period per sweep run, so a far-overdue agreement catches up one period per day rather than dumping a backlog. **Dispatch** — The dispatch board shows unassigned work orders, today's schedule, and active dispatches. Someone with write access (a manager, or anyone with the app's Contributor role) assigns a technician to a work order from the dispatch detail page; assigning automatically moves a Draft or Scheduled work order to Dispatched and notifies the technician. A dispatch shows as Assigned until the job is completed or cancelled; there is no accepted, en-route, or arrival-time tracking. ## 4. Running it ### Creating and managing work orders 1. Go to **Field Service Suite → Work Orders → New Work Order**. 2. Select a customer and optionally a site. Set the title, work type, priority, scheduled dates, and description. 3. Line items are not added on this page. They come from an estimate when you convert it, or from Ask AI ("add work order items"). A job with no line items can still be billed: click **Create Invoice Manually** on the work order and enter the lines on the invoice. 4. Assign a technician from the **Dispatch** tab (manager access or the app's Contributor role required). Technicians update the work order status from the field — the assigned technician can upload photos, capture the customer's signature, and advance the status. People with write access (managers and the app's Contributors) can do the same on any work order, and can also create, edit, and delete work orders. ### Sending an estimate 1. Go to **Field Service Suite → Estimates → New Estimate**. 2. Select a customer and add one or more options with line items. 3. Mark one option as **Recommended** if appropriate. 4. Click **Send to Customer** — the customer receives a link to the proposal page. 5. When the customer approves, the estimate's owner is notified; click **Convert to Work Order** to create the job. Approving does not create it on its own. ### Generating an invoice 1. From a completed work order, click **Generate Invoice** to pre-populate line items from the work order. 2. Or go to **Field Service Suite → Invoices → New Invoice** to create one from scratch. 3. Review the line items and tax calculation, then click **Send to Customer** to email it to the customer's contact on file. 4. Record each payment with **Record Payment**. If Online Payments is set up, card payments you take in your own Stripe account are recorded for you. ### Using the Dispatch Board 1. Go to **Field Service Suite → Dispatch** to see the list view (unassigned orders, active dispatches, today's schedule). 2. Switch to **Board** view to see work orders grouped by technician. 3. Click a work order to open the dispatch detail, then assign a technician. ### Reports Go to **Field Service Suite → Reports** (who can open it is set in **Settings › Who Can Do What**; managers by default). The reports page shows total work orders, completed count, revenue collected, average completion time, and breakdowns by status and priority. ## 5. Settings All settings are in **Field Service Suite → Settings** (app admin only). ### Premium Modules | Setting | Default | What it changes | |---|---|---| | **Pricebook Pro** | Off | Shows the Pricebook tab — a versioned service catalog with flat-rate pricing and margin analysis | | **Fleet Pro** | Off | Shows the Fleet tab — vehicle inventory, driver checkout/check-in, maintenance tracking, and inspections | | **Customer Portal** | Off | Shows the Customer Portal admin tab and activates the self-service portal where customers can view work orders, invoices, estimates, agreements, and submit service requests | | **GPS & Routing** | Off | Shows **Route Plans** (daily stop lists per technician; **Optimize** orders the stops by straight-line distance when the sites have coordinates) and the **GPS & Routing** live map. The map is in place, but no app shares technician or vehicle positions to it yet, so it stays empty. Who sees the map is set in **Settings › Who Can Do What** | | **Accounting Sync** | Off | Shows the Accounting tab — push invoices and payments to QuickBooks, Xero, or Sage via a connected integration | | **Live Assist** | Off | Adds a "Get help" button on work order detail pages for live remote video help (requires the Live Assist app and a LiveKit provider) | ### Core Settings | Setting | Default | What it changes | |---|---|---| | **Work Order Prefix** | WO | The prefix for auto-generated work order numbers (e.g. WO-00001) | | **Invoice Prefix** | INV | The prefix for auto-generated invoice numbers (e.g. INV-00001) | | **Default Tax Rate (%)** | 0 | Tax rate applied to new estimates and invoices | | **Default Priority** | **Medium** | Priority pre-selected when creating a new work order | ### AI Features | Setting | Default | What it changes | |---|---|---| | **Enable AI Features** | On | Master switch for the AI agent and all AI-powered features | | **AI Dispatch Recommendations** | On | Lets Ask AI rank technicians for a work order by open workload and experience with that type of work | | **AI Work Order Insights** | On | Lets Ask AI estimate a work order's duration and cost from similar past jobs and flag risks. Ask in Ask AI; nothing is added to the work order page | | **AI Pricing Suggestions** | On | Lets Ask AI suggest pricebook items and prices for a job you describe (needs Pricebook Pro). Ask in Ask AI; nothing is added to the estimate page | ### Online Payments (Stripe) This card is shown to business admins only; an app admin who is not a business admin does not see it. Payments are recorded only once both halves are in place: the **Stripe Webhook Signing Secret** saved here, and the webhook URL below configured in Stripe. Without the secret, every webhook is rejected. | Setting | Default | What it changes | |---|---|---| | **Enable Stripe Payments** | Off | Records payments you take in your own Stripe account against the matching invoice. It does not take payments — there is no Pay button. Whatever you collect with (a Stripe Payment Link, your own checkout, or the Stripe dashboard) must set `metadata[field_service_invoice_id]` to the invoice's id, or the payment can't be matched | | **Stripe Webhook Signing Secret** | (none) | Validates incoming Stripe webhook events — enter the secret from your Stripe Dashboard → Developers → Webhooks | When Stripe Payments is enabled, a webhook URL is generated automatically. Configure that URL in Stripe to receive these four events: ``` payment_intent.succeeded payment_intent.payment_failed checkout.session.completed charge.refunded ``` ### Notifications Sixteen toggles, one per event, under the names the settings page shows. All are **On** out of the box except the status-change one. The person who took the action is never notified about it. **Who hears about Field Service work with no owner** names one group. Customer service requests and failed vehicle inspections go to it; with no group named they go to the app's administrators (Admin › Apps), and if there are none, to every business administrator. The same group also stands in when a record's owner has left — a quote approved, declined or expired, a payment received, an invoice gone overdue, a contract visit due or a contract ending. For those, with no group named they go to the app's administrators, and if there are none **nobody is told** — the settings page warns you when that is the case. A stand-in for an invoice or payment notice must also be allowed to see invoices. | Setting | Default | What it does | |---|---|---| | **Tell a Technician a Job Is Theirs** | On | Tells the technician a work order is now theirs. When the board or Ask AI assigns and dispatches in one step, they get the Go Now notice instead | | **Tell a Technician Their Job Was Reassigned, Cancelled or Moved** | On | Tells the outgoing technician when a job is reassigned or unassigned, and the assigned technician when their job is cancelled or its start time changes | | **Tell a Technician to Go Now** | On | Tells the assigned technician when the job moves to Dispatched, with the date it is booked for — the one notice allowed through quiet hours | | **Tell the Assignee and Creator About Every Other Status Change** | Off | The creator, when a job is dispatched or cancelled; the assignee and creator, about the other changes (scheduled, started, on hold, resumed, invoiced by hand) | | **Tell the Creator a Job Is Finished** | On | Tells the creator and the assignee the job is completed | | **Tell the Estimate's Owner It Was Sent** | On | When a colleague, the Excel add-in or Ask AI emails it to the customer | | **Tell the Estimate's Owner the Customer Said Yes** | On | An action item to convert it into a work order | | **Tell the Quote's Owner the Customer Said No** | On | With the customer's reason; a decline that names a price waits under Needs you until the quote is revised | | **Tell the Estimate's Owner a Quote Died** | On | The quote passed its Valid Until date | | **Tell the Invoice's Owner It Was Sent** | On | When a colleague or Ask AI emails it to the customer | | **Tell the Invoice's Owner It Went Past Due** | On | The invoice passed its due date — including a part-paid one, told once | | **Tell the Invoice's Owner Money Arrived** | On | A payment was recorded, typed in or from Stripe | | **Tell the Dispatch Group a Customer Asked for a Visit** | On | An action item until someone assigns a technician | | **Tell a Contract's Owner a Recurring Visit Is Due** | On | The visit's work order was created, unassigned — an action item until someone assigns it | | **Warn a Contract's Owner Before It Ends** | On | In the last 30 days of the contract, at most once a fortnight | | **Tell the Dispatch Group a Vehicle Failed Inspection** | On | And the vehicle's assigned driver, when a pre-trip check is filed as Failed or Needs Attention | When a technician leaves the company with open jobs, the same group (or, with no group, the app's administrators and then every business administrator) is told which jobs to reassign. Each person also controls the **Field Service** category in their own notification settings, which delivers in-app, by email, and by push by default. Muting that category mutes all of the events above for that person. ## 6. More help - **Field Service Suite FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about Field Service Suite from these articles. **Keywords:** field service, work orders, dispatch, estimates, invoicing, fleet management, pricebook, customer portal, GPS tracking, service agreements, accounting sync, field-service-suite, field_service_suite --- # Field Service Suite FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Field Service Suite — for the admin running it. # Field Service Suite FAQ Answers to common setup and operating questions about Field Service Suite. For what the app is and how to set it up from scratch, see the [Field Service Suite Overview](/help/articles/field_service_suite_app_overview). --- ## Setup ## Do I need to configure anything before my team can start using Field Service Suite? An administrator enables the app from Admin → Apps → All Apps. It stays off until then. Once enabled, work orders, estimates, invoices, and dispatch are available immediately. Optional modules (Pricebook Pro, Fleet Pro, Customer Portal, GPS & Routing, Accounting Sync, and Live Assist) are separate toggles in the Settings tab. AI features default to on; disable them from Settings if you prefer to start without AI recommendations. ## What are the optional modules and how do I enable them? Six modules, each toggled independently in Settings: 1. **Pricebook Pro** — versioned service catalog with margin analysis 2. **Fleet Pro** — vehicles, maintenance scheduling, and inspection checklists 3. **Customer Portal** — magic-link self-service for your customers 4. **GPS & Routing** — live technician map and daily route plans 5. **Accounting Sync** — push invoices and payments to QuickBooks or Xero 6. **Live Assist** — remote video help on a work order (requires the Live Assist app and a meeting-provider integration) Only an app admin can change these toggles. That means a business admin, super admin, or a user with an explicit app-admin grant. --- ## Permissions and access ## Who can create and edit work orders, estimates, and invoices? Anyone with access to the app can view work orders, estimates, customers, and service agreements. Creating and editing records — and using the **Dispatch** board — takes **manager access** or the app's **Contributor** role. To let a dispatcher or billing clerk record work without making them an HR manager, go to **Admin › Apps**, open Field Service Suite, and use **Manage Admins & Contributors** to give them **Contributor**. The Settings tab is for **app admins** only. The rest is set per business in **Settings › Who Can Do What**, and each starts at managers: who can see invoices and payments, who can see reports and push invoices to accounting, who can see where technicians are, and who can change the active pricebook. Anyone who can write records can always see invoices. The **Accounting** page shows invoice totals, so it needs both "Who can see reports and push invoices to accounting?" and "Who can see invoices and payments?". ## Why can't I see the Reports, GPS & Routing, or Accounting Sync tab? Each needs its module turned on (for GPS & Routing and Accounting Sync) and the matching choice in **Settings › Who Can Do What**: **Reports** follows "Who can see reports and push invoices to accounting?"; **Accounting** needs that choice and "Who can see invoices and payments?" too, because it shows invoice totals; and **GPS & Routing** follows "Who can see where technicians are?". All three start at managers. **Dispatch**, **Route Plans**, and the **Customer Portal** admin tab need manager access or the app's Contributor role. The Pricebook and Fleet tabs appear for everyone with app access once their module is on; changing the active pricebook follows "Who can change the active pricebook?", and other changes need manager access or the Contributor role. ## Can I fill out a vehicle inspection without being a manager? Yes. Any team member with access to the app can create and complete vehicle inspections, as long as Fleet Pro is enabled. The standard checklist has 17 items across five categories (exterior, under-vehicle, safety, mechanical, interior). Adding, editing or removing vehicles, checking a vehicle out to someone, and scheduling maintenance need manager access or the Contributor role; the assigned driver can check their own vehicle back in. --- ## Day-to-day ## How does payment collection work? Field Service records payments; it does not take them. There is no Pay button on an invoice or in the customer portal — you collect the money and record it with **Record Payment** on the invoice, using one of seven methods: card, debit, ACH, cash, check, financing, or other. If you take card payments in your own Stripe account (a Stripe Payment Link, your own checkout, or the Stripe dashboard), have a business admin turn on **Online Payments (Stripe)** in Settings (the card is shown to business admins only), enter your Stripe webhook signing secret there, and add the webhook URL it shows to your Stripe Dashboard → Developers → Webhooks; those payments are then recorded on the matching invoice automatically, as long as the payment carries the invoice id. The invoice balance updates as soon as the payment webhook arrives. Refunds processed in Stripe also sync back and adjust the balance. ## Do service agreements create work orders and invoices automatically? Yes, once the agreement is **Active**. Each agreement has an auto-schedule setting. When it is on, a daily job checks whether a visit is due and creates an unassigned work order with status **Scheduled**, and tells the agreement's owner to dispatch it. Whether or not auto-schedule is on, the same job generates a **Draft** invoice for each billing period that comes due, with a 30-day payment term, for someone to review and send. One visit and one invoice are processed per agreement per day, so missed periods catch up over consecutive runs. ## How do customers approve an estimate I send them? The customer receives an email with a link to a shareable proposal page. They view the options and approve one by choosing it, or decline with a reason. There is no signature step. Viewing the proposal marks the estimate as **Viewed** automatically. Approval requires the estimate to be in **Sent** or **Viewed** status. Once the Valid Until date passes, the estimate changes to **Expired** and can no longer be approved. Approving does not create a work order: the estimate's owner gets an action item, and someone with write access clicks **Convert to Work Order**. ## What notifications does Field Service Suite send, and how do I control them? The app has sixteen notification toggles in Settings: assignment, assignment removed, dispatch, status change, completion, estimate sent, estimate approved, estimate declined, estimate expired, invoice sent, invoice overdue, payment received, customer service request, agreement visit, agreement expiring, and vehicle inspection failed. All are on out of the box except **status change**. Nobody is notified about an action they took themselves. Service requests and failed inspections go to the group you name under **Who hears about Field Service work with no owner**; that group also stands in when a record's owner has left (a quote approved, declined or expired, a payment, an overdue invoice, a contract visit or a contract ending). With no group named, these go to the app's administrators; with none of those, requests and inspections reach every business administrator, but an owner-left notice reaches nobody — the settings page warns you when that is the case. Each person can also mute the **Field Service** category in their own notification settings. It delivers in-app, by email, and by push by default, and muting it mutes all of the events above — jobs, quotes, invoices and payments, contracts, and fleet alerts — for that person. ## How do I sync invoices and payments to QuickBooks or Xero? Enable the Accounting Sync module and connect an accounting integration. Then open the Accounting Sync tab to push invoices and payments individually or in bulk. Draft and voided invoices are excluded automatically. A payment can only sync after its parent invoice has been synced. Each sync is logged with a status so you can see what went through and retry failures. ## Can I use Field Service Suite from my phone? Yes. Mobile-optimized views are available for work orders, estimates, invoices, fleet, service agreements, and the pricebook. Technicians can capture photos, videos, and customer signatures from the work-order page on a phone. Vehicle inspections work on mobile too. The mobile views are web-based and require an internet connection. --- ## When something looks wrong ## I was dispatched to a job but I can't mark it as invoiced or cancelled — why? A work order is marked **Invoiced** when its invoice is created (Generate Invoice). Only someone with write access — a manager, or someone with the app's **Contributor** role — can cancel a work order, or close one as Invoiced by hand when it was billed before it was finished. Technicians can move a work order through all other statuses — Scheduled, Dispatched, In Progress, On Hold, and Completed. Ask your office to handle invoicing or cancellation. ## My customer says they didn't receive the portal login email Check four things: the customer record must have a primary contact email, the customer must be **Active** (not Inactive), and the customer must not be sample data — no portal email is sent to sample-data customers. Fourth, no other customer record may share that email address (for example, one billing mailbox for two sites): when two customers share an address, the portal can't tell which one is asking and sends no link. For that customer, use **Email** or **Get Link** on the **Customer Portal** admin page instead. The sign-in link is limited to five requests per hour per email address. A request over the limit is refused, not queued — the customer sees "please wait N minutes" and can try again after that; a link that already arrived still works. Portal login emails are transactional and always deliver regardless of marketing preferences. ## Why did my estimate change to "Expired"? A daily job marks any estimate in **Sent** or **Viewed** status as **Expired** once its Valid Until date passes. Set a longer validity period before sending to prevent this. Approved and converted estimates are never expired. If the customer still wants to proceed after expiry, open the estimate and click **Revise as a new quote**: it copies the job and its options into a new draft for you to re-price and send, and links the two, so once you send the new quote, the customer's old link points them to it. ## A customer paid through Stripe but the invoice balance didn't update Field Service matches a Stripe payment to an invoice by the invoice id in the payment's metadata. Whatever the customer paid through — a Stripe Payment Link, your own checkout, or the Stripe dashboard — must set `metadata[field_service_invoice_id]` to the invoice's id on the PaymentIntent or Checkout Session. A payment without it can't be matched: record it on the invoice yourself with **Record Payment**, and add the metadata to your payment link or checkout so later payments match. Events stuck in processing for more than 15 minutes are retried automatically. If a completed payment with the same Stripe intent already exists, the duplicate is skipped to prevent double-recording. --- ## Licensing and limits ## Does Field Service Suite require a licence? Yes. An administrator enables it per tenant from Admin → Apps → All Apps. The app is not available to any user until an admin turns it on. ## How does the customer portal login work? Customers log in through a magic-link email — there is no username or password. The link is valid for **24 hours** and is **single-use**: once clicked, the token is consumed. A portal session lasts **4 hours**; after that the customer must request a new link. You can send links individually or in bulk from the Customer Portal admin tab, up to **100 customers** per batch. The login page never reveals whether an account exists. ## What are the limits I should know about? | Area | Limit | |---|---| | Pricebook CSV import | 5 MB file size, 5,000 rows max, aborts after 10 errors | | Pricebook category nesting | 10 levels deep | | Portal magic-link validity | 24 hours, single-use | | Portal session duration | 4 hours | | Portal bulk send | 100 customers per batch | | Portal login rate limit | 5 requests per hour per email address (refused, not queued, over the limit) | | Tax rate | 0–100% | | Work-order number format | Configurable prefix (default **WO**) + 5-digit sequence | | Invoice number format | Configurable prefix (default **INV**) + 5-digit sequence | | Estimate number format | **EST** + 5-digit sequence (not configurable) | | Vehicle inspection checklist | 17 standard items across 5 categories | --- ## More help - [Field Service Suite Overview](/help/articles/field_service_suite_app_overview) - Ask AI — the assistant answers Field Service Suite questions from these articles. **Keywords:** faq, work order, dispatch, estimate, invoice, pricebook, fleet, customer portal, service agreement, GPS tracking, accounting sync, Stripe, payment, field service, technician, field-service-suite, field_service_suite --- # Forms App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run Forms — building form templates, configuring approval workflows, managing submissions, and governing AI and mobile features. # Forms ## 1. What it is Forms lets you replace paper, PDFs, and email threads with digital forms your workforce can fill out on any device. You build a form — from scratch, from a plain-language description, or by uploading an existing PDF — publish it, and collect structured submissions that can route through approval workflows and trigger actions in other apps. - **Enablement:** Requires a license. An admin enables it from **Admin → Apps → All Apps**. It is not turned on automatically. - **What it is not:** Forms collects structured data and routes individual submissions through review. For anonymous employee-engagement surveys with trend analysis and action planning, use **Surveys** — it is a separate app. Use Forms when you need to review and act on each response individually. ## 2. Standing it up 1. **Enable the app** — go to **Admin → Apps → All Apps**, find **Forms**, and enable it. 2. **Decide who can create forms** — go to **Forms → Settings → Permissions**. The **Who can create & manage forms?** control defaults to **Managers** (admins, managers, and anyone designated as a Forms App Admin). You can tighten this to app-admins only, widen it to everyone, or restrict it to specific groups. 3. **Build your first form** — go to **Forms → Manage Forms** and create a new template. Add fields using the drag-and-drop builder, configure any validation or conditional logic, then **Publish** when ready. Forms start in **Draft** and are invisible to employees until published. 4. **Set the audience** — by default a published form is available to **All** employees. If the form is only for a specific department, location, or group, set it under **Form Settings → Audience & Access** in the builder before publishing. Employees outside the audience will not see it. 5. **(Optional) Configure approval** — if submissions need review, turn on **Requires approval** for the form (on the publish card, or in the builder's form settings). Its reviewers — the form's creator (while they can create and manage forms), owner and co-owners, and the recipients set under **Settings → Notifications** — are asked about each submission, and any one of them decides it; if none of them can, the Forms app admins, then the business admins, are asked. For sign-offs in a fixed order, add an approval workflow from the form's page (**Approval Workflow** in its menu). 6. **Confirm it worked** — employees see the published form on the **Published Forms** tab and can fill it out. Submitted responses appear in **Submissions** for reviewers. **Without a workflow:** a form that requires approval still has reviewers. Each submission is sent to the form's creator, owner and co-owners and the Settings → Notifications recipients (falling back to the Forms app admins, then the business admins) as "New submission to review", and any one of them can approve, reject or return fields. Only people who can open the submission are asked. **Permissions:** Admins and super admins have full access to all Forms surfaces. Managers see the Manage Forms, Submissions and Scheduled Forms tabs and the form builder by default (configurable under Settings → Permissions). The Analytics, Activity Log, and Settings tabs are restricted to admins and Forms App Admins. The Integrations and Activity Log tabs are admin and Forms App Admin only too. Regular employees see the Dashboard (their own forms and submissions), Published Forms and My Submissions; a person a form names as owner, owning team or co-owner also gets Manage Forms and Submissions, limited to those forms, and anyone with direct reports gets Submissions, limited to their reports' submissions. ## 3. How it fits together **Templates and submissions** — A form template is the definition: its name, fields, validation rules, and sharing settings. A form submission is one person's filled-out response to that template. Templates move through three statuses: **Draft** → **Published** → **Archived**. A submission moves through up to seven: **Draft** (auto-saved while filling) → **Submitted** → **Under review** → **Approved** or **Rejected**. Two additional statuses appear in specific workflows: **Pending completion** (a Workflows rule on the Integrations tab emailed someone else a link to fill in a missing field) and **Changes requested** (a reviewer returned specific fields to the submitter for correction rather than rejecting the entire form). **Audience targeting** — Every template has a target audience that controls who sees it on the Published Forms list and who can fill it out in-app. It is set under **Form Settings → Audience & Access**: the default is **All employees**; otherwise it is the union of the groups, departments, job titles, locations, roles and people you add. Admins and the people who manage the form can always open it. An **Anyone with the link** share link bypasses the audience (whoever holds the link can respond); an **Only logged-in users** link requires sign-in and applies it. **Field visibility** — Each field carries a visibility level that controls who can see the submitted answer (not who fills it in — the submitter always fills every field). The four levels, from widest to narrowest: **Everyone** (anyone who can view the submission, the default), **Reviewers** (the submitter, their manager, admins, and the people who review it — its workflow approvers, and onboarding HR for an onboarding form), **Managers** (the submitter, their manager, and admins), and **Submitter** (the submitter and admins only — managers and approvers cannot see it). The submitter always retains access to their own answers. **Approval workflows** — A form can have one or more approval workflows, each with ordered steps. When a submission enters review, the first matching active workflow governs it. A reviewer can approve (advancing to the next step), reject (bouncing the entire submission), or return individual fields for correction. A rejected submission that is corrected and resubmitted — from the submission page, the form, the phone, the API or a shared link — starts the workflow again at the first step, so every approver signs the corrected answers; a submission returned for correction continues at the step that returned it. Separately, a **Workflows** rule on the Integrations tab can use a **Request completion** action to email someone a link to fill in a missing field; the submission sits in **Pending completion** until they finish, then returns to Submitted. The workflow is pinned to the submission once review starts, so changing the workflow definition mid-flight does not affect in-progress submissions. **Categories and priorities** — Every form template carries a category (General, Safety, HR, IT, Facilities, Operations, Quality, Compliance, Maintenance, Training, Feedback, Onboarding or Other — admins can hide any of these or add their own under Settings → Form Categories) and a priority (Urgent, High, Normal, or Low — defaulting to **Normal**). Categories appear as a filter on both the Published Forms and Manage Forms lists. Priority is set in the builder's Form Settings and is used as a **Priority** filter on the Published Forms list. **Public and embedded forms** — A form can be shared outside your organization via a public link or QR code, or embedded on an external website in an iframe. Public forms accept anonymous or authenticated submissions. Each form can carry its own brand logo (uploaded under the form's Design settings) that replaces the default business logo on the public-facing page. **Integrations** — A submission can automatically create records in other apps when it lands: a task in Tasks, an incident report in Safety Hub, a ticket in Service Desk, or a note on the employee's record in Performance Management. Submitted files can also sync to the employee's HR file. Each integration is configured per form template under **Integrations** and is only available when the target app is enabled for your organization. ## 4. Running it ### Reviewing submissions 1. Go to **Forms → Submissions**. 2. Filter by status, date range, or search by form name. 3. Open a submission to view the answers. Fields restricted by visibility level are hidden from reviewers who do not meet the threshold. 4. **Approve**, **Reject**, or **Return for correction** (field-level). If field-level return is used, only the returned fields become editable for the submitter and the submission moves to **Changes requested**. 5. Reviewers can also bulk approve or reject selected rows (up to 200 at a time). Bulk approve skips submissions that follow an approval workflow (approve those one at a time on their own page) and submissions that still have returned fields open (those wait for the employee's corrections). ### Sharing a form publicly 1. Go to **Forms → Manage Forms**, open the form, and choose **Sharing Settings** from its ⋮ menu. 2. Turn on **Enable Form Sharing** and click **Save Sharing Settings**: that creates the form's link. For **Anyone with the link**, a QR code (opened as a PNG) and an Embed Code are offered too. 3. Choose the access type: **Anyone with the link** (people without an account can respond if **Allow anonymous responses** is ticked) or **Only logged-in users** (must be signed in to your organization and inside the form's audience). 4. Optionally set a start and end date for the link, a **Stop accepting responses at** time and a **Maximum responses** cap, whether people may respond more than once, saving progress, a confirmation message or redirect, GDPR consent, and **Log IP addresses**. Spam protection (a hidden honeypot field and a minimum-time check) is always on for public links. 5. Forms can also be embedded on external sites via iframe. ### Scheduling recurring assignments 1. Go to **Forms → Scheduled Forms** and create a new schedule. 2. Select a form template, set the frequency (e.g. daily, weekly, monthly), choose assignees, and optionally set an end date. 3. At each scheduled interval, assigned employees are notified that they have a form to fill out. 4. A schedule without an end date runs indefinitely until paused or deleted. ### Building a form with AI 1. Go to **Forms → Manage Forms → Create → Build with AI** (offered only when **AI Form Creation** is on in Settings). 2. Choose one of three methods: - **Describe it** — type a plain-language description and AI generates the fields, validation, and conditional logic. - **Upload a PDF or image** — upload an existing document and AI extracts the fields and layout into a digital form. - **Paste a web page URL** — point AI at a public page and it generates a form from the content. 3. Review and refine the generated form in the drag-and-drop builder before publishing. ### Viewing analytics 1. Go to **Forms → Analytics** (visible only when **Analytics Dashboard** is enabled in Settings and you have admin access). 2. The dashboard shows submission volume, completion rates, and status trends. 3. When **AI Analytics** is enabled, the Analytics page also shows what share of submissions had answers filled in by AI (for example by the Forms assistant from a document). 4. Reports can be exported to PDF, Excel, CSV, and JSON. ### Using PDF templates 1. Go to **Forms → Manage Forms → Create → Import from PDF** to upload a PDF you want to map to a digital form. 2. Map PDF fields to form fields. **Download PDF** on a submission then produces your original PDF filled in with the answers — generated when someone downloads it, not when the form is submitted. 3. PDF templates support version history so you can track changes. ## 5. Settings All settings live under **Forms → Settings**. Every setting below has a real runtime effect — toggling it changes what employees or the AI can do. | Setting | Section | Default | What it changes | |---|---|---|---| | **Forms Agent** | Agent | On | Enables the Forms AI assistant that can answer employee questions about forms | | **Who can create & manage forms?** | Permissions | Managers | Controls who sees the Manage Forms, Submissions and Scheduled Forms tabs and the form builder (a form's owner, owning team and co-owners still reach Manage Forms, Submissions and the builder for that form; Scheduled Forms stays with the Manage tier); Integrations, Analytics, Activity Log and Settings stay with admins and Forms App Admins. Options: Managers and above, App admins only, Everyone with access to the app, Specific people | | **AI Form Creation** | AI Features | On | Shows or hides **Build with AI** under Manage Forms → Create, and the ability to generate forms from text, PDF, or URL | | **AI Auto-Fill** | AI Features | On | Smart field-completion suggestions while filling a form | | **AI Validation** | AI Features | On | Flags likely mistakes in answers before the form is submitted | | **AI Analytics** | AI Features | On | Shows what share of submissions had answers filled in by AI, on the Analytics page | | **Voice Input** | Mobile Features | On | Microphone on text fields on the web form (tablets) and in the iOS app; phone web pages use the keyboard's dictation | | **Photo Capture** | Mobile Features | On | Photo to Text (reads the text in a photo into a field on the web form) and the camera on photo and file questions in the iOS app; attaching files in the browser follows File Attachments | | **GPS Location** | Mobile Features | On | Location fields offer **Get current location** on the web, the phone and the iOS app; when off, people type the address | | **Conditional Logic** | Form Features | On | Allow show/hide and require-when rules on fields | | **Multi-Page Forms** | Form Features | On | Allow splitting forms across pages with page breaks | | **File Attachments** | Form Features | On | Allow file, image, video, and audio upload fields | | **Max File Size** | Form Features | 10 MB | Per-file upload limit for attachments | | **Analytics Dashboard** | Form Features | On | Shows the Analytics tab for admins | | **Moderate Submission Content** | Form Features | On | Checks answers against your content-moderation guidelines before accepting. Only has an effect if the tenant has configured content moderation under **Admin → Content Moderation** | | **Send submission review alerts to this group** | Notifications | None | Adds a group to those told about each new submission on a form that requires approval (after the form's creator, owner and co-owners; only people who can open and decide it are asked). The awaiting-review reminder goes to the group *instead of* the Forms app admins. With no group, the reminder and any submission with nobody to tell go to the Forms app admins, then the business admins | | **Tasks App Integration** | Integrations | On | Auto-create tasks from form submissions (requires Tasks app enabled) | | **Safety Hub Integration** | Integrations | On | Auto-create incident reports (requires Safety Hub enabled) | | **Service Desk Integration** | Integrations | On | Auto-create support tickets (requires Service Desk enabled) | | **Performance Management Integration** | Integrations | On | Add a note to the employee's record on submission (requires Performance Management enabled) | Integration toggles only appear when the corresponding app is enabled for your organization. ## 6. More help - **Forms FAQ** — specific setup and operating questions, limits, and troubleshooting. - Ask AI — the assistant answers questions about Forms from these articles. **Keywords:** forms, form builder, form template, form submission, approval workflow, digital forms, pdf form, inspection form, incident report form, ai form builder, public form, qr code form, scheduled form, field visibility --- # Forms FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Forms — for the admin running it. # Forms FAQ Answers to common setup and operating questions about Forms. For what the app is and how to set it up from scratch, see the [Forms Overview](/help/articles/forms_app_overview). --- ## Setup ## Who can create and manage forms? By default, **Managers or above** plus anyone designated as a **Forms App Admin** can create, edit, and manage forms and submissions. An admin can change this in Forms **Settings** under "Who can create & manage forms?" — the options are Managers, App Admins only, Everyone, or Specific groups. Admin and Forms App Admin always have access regardless of this setting. ## Who can change Forms settings and view analytics? Only **Admins, Super Admins**, and the designated **Forms App Admin**. Managers cannot reach Settings, Analytics, or the Activity Log even when they can create and manage forms. ## Do I need to publish a form before people can fill it in? Yes. New forms start in **Draft** status. Only published forms appear in the Published Forms list and accept submissions. You can also archive a form to remove it from the list without deleting it — archiving stops new submissions but keeps existing ones. --- ## Permissions and access ## Why can't some employees see a form I published? Published forms default to **All employees**. If you set the audience to a specific department, location, or group, only employees matching that filter see the form in their Published Forms list. Check **Form Settings → Audience & Access** in the builder: the audience is the union of everything you add — everyone, groups, departments, job titles, locations, roles and named people. Admins and the people who manage the form (creator, owner, owning team, co-owners) can always open it. ## Who can view someone else's submission? A submission can be opened by the person who submitted it, the submitter's direct manager, any Admin or Forms App Admin, and the form's own people: its owner, owning-team members and co-owners, plus its creator while the creator is inside the "Who can create & manage forms?" group. If an approval workflow names specific users for the step the submission is waiting on, those people can also open and decide it. ## What are the field visibility tiers? Each field has a visibility setting that controls who can see the submitted answer: 1. **Everyone** (default) — anyone who can view the submission sees the value. 2. **Reviewers** — the submitter, their manager, Admins and Forms App Admins, and the people who review the submission: whoever approved a step of its approval workflow or is named for the step it is waiting on, and, for a form filled in as part of onboarding, the people who run onboarding. 3. **Managers** — only the submitter, their manager, and Admins and Forms App Admins can see the value. 4. **Submitter** — only the submitter plus Admins and Forms App Admins can see the value; managers and approvers are blocked. The submitter who entered a value always retains access to it, regardless of the tier. An HR role does not open a restricted answer by itself: the people who run onboarding see only the Reviewers tier, and only on a form filled in as part of onboarding. --- ## Day-to-day ## How do approval workflows decide who reviews a submission? Each approval step has a type that determines who must act: - **Specific users** — you name individual people; any one of them can approve the step. - **Users with role(s)** — anyone holding one of the chosen roles who can also open the submission: an admin, a Forms App Admin, one of the form's own people (owner, owning team, co-owners, and its creator while they can create and manage forms), or the submitter's manager. - **Any manager or admin (by role)** — anyone with the Manager or Admin role who can also open the submission. To ask a particular supervisor, name them under Specific users. Steps run in order. When nobody a step names can approve it (they left, or none of them can open the submission), admins and Forms App Admins sign it and are asked to. Workflows are set up from the form's page (**Approval Workflow** in its menu, shown once the form requires approval); to stop using one, untick **Active** on it — new submissions then skip it, and the ones already in its chain can still be approved. ## Can a reviewer return individual fields instead of rejecting the whole form? Yes. A reviewer can return specific fields for correction — the approved fields stay locked and only the returned fields become editable. The submission stays in a **Changes requested** status and cannot reach Approved while any field is still returned. Once the submitter corrects and resubmits, the workflow re-evaluates. ## What is request-completion and how does it work? A workflow rule can be set to **Request completion**, which pauses the submission and emails a magic-link URL to another person asking them to fill in a missing field. The submission enters **Pending completion** status. When the assignee finishes, the submission moves back to Submitted and the remaining workflow rules continue. Each rule fires only once — a rule that already ran is skipped on re-evaluation. ## What happens when someone submits a form that has integrations configured? Each integration fires independently after submission, if both the integration and its target app are enabled: - **Tasks** — auto-creates a task. - **Safety Hub** — auto-creates an incident report. - **Service Desk** — auto-opens a ticket. - **Performance Management** — adds a note to the employee's record. Each integration's rules are set per form on the Integrations tab (admins and Forms App Admins only). A Tasks, Safety Hub, Service Desk or Performance Management rule is switched off with its **Enable this rule immediately** switch, and those four also have tenant-wide switches under Settings → System Integrations. Workflow steps (emails and requests to complete) have no tenant-wide switch and no on/off switch of their own; they run for a form for as long as it has steps. ## Can I schedule a form to go out on a recurring basis? Yes. The **Scheduled Forms** tab lets you create recurring assignments on a daily, weekly, or monthly cadence. Each schedule targets specific employees, and you can set an end date to stop it automatically — without an end date, the schedule runs until you pause or delete it. --- ## Sharing and public access ## How do I share a form publicly by link or QR code? Open the form (Manage Forms → the form), choose **Sharing Settings** from its ⋮ menu, turn on **Enable Form Sharing**, pick **Anyone with the link** and save. A share link, a QR code you can save as a PNG, and an **Embed Code** for an iframe appear. **Regenerate Link** gives the form a new link — the old link, printed QR codes and embedded copies stop working. ## Can I limit how many responses a form accepts? Yes. On the Share Form page (**Sharing Settings** in the form's ⋮ menu), under **Response Collection**, you can set a **Maximum responses** cap and a **Stop accepting responses at** date/time. The response cap applies across all channels (web, mobile, API, and public link). The start/end date availability window applies to the public link only. Once either limit is reached the form stops accepting new submissions. ## Can I allow anonymous submissions? Yes. On the Share Form page you can tick **Allow anonymous responses**: people without an account can answer through the link, and their submissions have no linked user account. They are asked for their email address (required — unless the form asks for one itself), which reviewers see as the submitter and which receives a receipt when receipts are on, so these responses are not anonymous to your reviewers. ## Is respondent IP and browser data retained? Every submission keeps the browser's user-agent, and public-link submissions keep the referrer. The respondent's IP address is kept too unless you untick **Log IP addresses** (Share Form page → Privacy & Compliance, shown while Enable Form Sharing is on; on by default). All three, and the IPs in the Activity Log, are overwritten with [redacted] once they are **90 days** old. --- ## When something looks wrong ## "I can't submit this form — it says it's closed" The form may have hit one of these limits: (1) the **Stop accepting responses at** date/time has passed, (2) the **Maximum responses** cap has been reached (only non-draft submissions count against the cap), (3) the form was returned to Draft or Archived status, (4) today is outside the link's Start and End dates, or (5) **Enable Form Sharing** was turned off. Check the form's status and its Response Collection settings on the Share Form page (**Sharing Settings** in the form's ⋮ menu). ## "I filled out a form but my manager says they can't find it" A manager sees a submission in **Submissions** when the submitter reports directly to them (the manager set on the submitter's profile), when it is on a form the manager created, owns or co-owns, or when it is waiting on an approval step that names them. The form's audience does not matter. Anyone with direct reports can open Submissions, narrowed to their reports' submissions; Manage Forms needs the Manage tier under **Who can create & manage forms?** (or owning or co-owning a form); admins and Forms App Admins see every submission. Submissions waiting on their decision are also in **Inbox › Waiting on you**. ## "I can't find Build with AI" **Build with AI** lives under **Manage Forms → Create** (there is no separate sidebar tab). It is offered only when **AI Form Creation** is on in Forms Settings; only an Admin or Forms App Admin can change that setting. --- ## Limits and configuration ## What are the file upload limits? The default per-file upload limit is **10 MB**. An admin can change this in Forms Settings to anywhere from **1 MB to 50 MB**. File attachment fields can be disabled entirely via the **File Attachments** toggle in Settings. Build with AI's file extraction (PDF/image upload) has a separate **20 MB** limit and accepts PDF, JPEG, PNG, GIF, and WebP files. ## What are the limits for AI form creation from a text description? The description must be between **150 and 5,000 characters**. Descriptions shorter than 150 characters or longer than 5,000 are rejected with a validation message. AI Auto-Fill (the magic-wand button on text, email and phone fields of the web form) suggests the signed-in person's own name, email address or today's date for fields whose internal name is a name, email or date field (for example `full_name`, `email`, `date`). ## Are there limits on exports and bulk actions? Exports from the Submissions page are capped at the most recent **10,000 rows**, the Activity Log CSV at the most recent **5,000**, and Analytics data exports at **10,000** rows in the selected date range; the file says so when the cap bites. A PDF export of submissions or templates from Analytics is refused above **1,000 rows** — narrow the date range or export CSV instead — and a **Submissions Summary** report lists the **1,000** most recent submissions and says so. Bulk approve/reject acts on up to **200** selected submissions, and bulk approve skips submissions that follow an approval workflow or still have returned fields open. ## Does Forms require a licence? Yes. Forms requires a licence and must be enabled per tenant by an admin through Admin → Apps → All Apps. It is not auto-enabled — an admin opts in. ## What features can I turn on or off in Settings? Forms Settings exposes these per-tenant toggles, all **on** by default: - **Conditional Logic** — show/hide and require-when rules on fields. - **Multi-Page Forms** — page-break fields in the builder. - **File Attachments** — file, image, video, audio, and gallery field types. - **AI Form Creation** — **Build with AI** under Manage Forms → Create, and conversational form generation. - **AI Auto-Fill** — AI-assisted answer suggestions when filling a form. - **Analytics Dashboard** — the Analytics tab (visible to Admins and Forms App Admin only). --- ## More help - [Forms Overview](/help/articles/forms_app_overview) - Ask AI — the assistant answers Forms questions from these articles. **Keywords:** faq, forms, form builder, approval workflow, field visibility, file upload limit, public form, qr code, anonymous submission, scheduled form, conditional logic, pdf template, form permissions, not showing, can't submit --- # Frontline Execution App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-18 How to set up and run HQ-to-field campaigns that fan work out to locations, give every worker a ranked My Day list, and roll coverage up live. # Frontline Execution ## 1. What it is Frontline Execution lets HQ author an operational directive once — a promo changeover, a store reset, a safety walk, a daily opening checklist — target it to the right locations and roles, and fan it out automatically. Every frontline worker sees one ranked **My Day** list of what to do this shift, and managers watch completion roll up live across their span. - **Enablement:** Licensed and off by default. An admin enables it from Admin → Apps → All Apps. - **What it is not:** Frontline Execution is not a personal task manager. Work is anchored to a place and a role, not to a person, so the obligation and its coverage number survive absence, transfers and turnover: work the holder doesn't finish is moved by the campaign's rule once its deadline passes, and a manager can hand it off sooner. For person-assigned ad-hoc tasks, use the Tasks app. ## 2. Standing it up 1. Go to **Apps → Frontline Execution → Settings**. Review the defaults — the main surfaces are on. Under **Available features**, the three surface toggles (**My Day**, **Campaigns**, **Coverage rollup**) control which sidebar sections appear for your users. 2. **Import your location tree.** Go to **Import** in the Admin section of the sidebar. Upload a CSV of your locations (hierarchy import) and a CSV of employee-to-site assignments. The import page shows a dry-run preview before writing anything. Without a location tree and people attached to it, campaigns have nowhere to fan out. 3. **Set up campaign categories** (optional). Go to **Settings**, and in the **Categories** card click **Manage categories**. Categories are publication programme labels — "Planogram", "Safety", "Weekly Bulletin" — that color the publishing calendar and let you filter campaigns. They are separate from the owning department. 4. **Grant access.** Any employee with access to the app sees **Overview**, **My Day**, and **My requests**. Managers and above also see Day Sheet, Reviews, Request queue, Campaigns, Calendar, Coverage, People, Shared blockers, and Analytics. Admins and app admins see Settings and Import. 5. **Confirm it works.** Create a campaign in draft, target a test location, and launch it. The targeted worker should see it on their My Day list. Use **Starter campaigns** on the Campaigns page to seed three editable drafts if you want a template to start from. ## 3. How it fits together **Campaigns and items.** A campaign is the HQ directive — the aggregate. When you launch it, the platform fans it out into one **item** per targeted location. Each item is the durable obligation: it is bound to a place and a role, not to a person. The person holding it (`current assignee`) can change — through a claim, a reassignment, a handoff at shift end — without the obligation moving. That is what makes coverage survive turnover and absence. A campaign has one of three work types: - **Task** — the worker completes a piece of work, optionally with photo or signature proof. - **Inspection** — the worker fills out an inspection template bound to the campaign. - **Post** — the worker reads and acknowledges the directive (a read-receipt). *Example:* HQ creates a campaign called "Spring Endcap Reset" with work type **Task**, priority **Important**, targeted at the "All Retail Stores" audience and the "Merchandising Associate" role. On launch, the platform mints one item per store. At Store 247, the rostered associate sees it on My Day, claims it, photographs the finished endcap, and submits. The store manager reviews the photo and accepts it. Coverage for Store 247 moves to **Done**; HQ watches the chain-wide number climb on the Coverage page. **Who does it.** Each campaign chooses how the person behind each item is resolved: - **Each location's manager** (default) — the location's manager is assigned automatically. - **A single named owner** — one named person per location. - **Round-robin across the team** — spread across eligible people at each location. - **Anyone at the store can claim it** — work is posted unclaimed; anyone at the location who qualifies can pick it up. **When the owner is decided** is either **At launch — resolve the owner when it goes out** or **When it's picked up — whoever claims it becomes the owner**. **Unfinished work.** Work that is still open once its deadline has passed — including work held by someone who has since left — is handled by the rule the campaign chose under **If the work is still open when it's due**: **Hand it to whoever holds the role now** (the default), **Put it back in the pool**, **Hand off to the next shift**, or **Escalate to the accountable manager**. Until the deadline passes, the work stays with whoever holds it. **Separation of duties.** By default, the person who did the work cannot approve it. This is controlled by the **Someone Else Must Approve Submitted Work** setting. Even when turned off, campaigns that require photo or signature proof never allow self-approval. **Requests.** Any employee can submit a campaign request — "stores can ask too" is a real pattern, not just HQ departments. Requests land in the **Request queue**, visible to managers and above, where they are approved or declined. An approved request mints a draft campaign. If the tenant has configured an Approval Workflow for Frontline Execution, decisions route through that engine instead of the queue's direct buttons. **Blockers.** A worker who cannot complete an item reports a structured reason: **Stock hasn't arrived**, **Missing fixture or supplies**, **Equipment is down**, **Not enough staffed time**, **Instructions unclear for this location**, or **Something else**. When enough locations report the same problem on the same campaign (controlled by the **Locations Needed to Group a Blocker** setting, default 3), it appears on the **Shared blockers** page and can be escalated as a single Service Desk ticket. **Integrations with other apps:** - **Tasks / Inspections** — campaign items mint a Task or Inspection as the fulfillment record; notes and activities are shared. - **Training** — a campaign can require a Training course; work can be claimed without it, but can't be completed until the course is. - **Approval Workflows** — publication approval and request approval both route through the generic approval engine. - **Calendar** — campaigns and blackout periods project onto the shared calendar. - **Service Desk** — blocker escalations can open a ticket. - **Time Clock Kiosk** — workers who identify at a kiosk can see and act on their day's work (when **Show Work Lists on Shared Kiosks** is enabled). - **Asset Library** — campaigns can attach reference documents (planograms, spec sheets, SOPs) from the library. ## 4. Running it ### Creating and launching a campaign 1. Go to **Campaigns → New campaign**. 2. Fill in the name, work type, priority, target audience, expected role, assignment strategy, and dates. 3. Attach reference documents from the Asset Library if needed. 4. Use **Check writing** to score the draft against your content standards (if configured). 5. **Launch** the campaign. If publication approval is required, submit it for approval first. A launched campaign cannot be edited. A material change closes the original and mints a successor, so that work people already acted on is never rewritten under them. ### Reviewing submitted work Go to **Reviews**. The queue lists everything submitted within your span, oldest first, with proof shown inline. You can accept or reject items individually, or select multiple items and use **Bulk accept** to clear a batch at once. ### Monitoring coverage Go to **Coverage**. Each campaign shows the percentage of items completed across your locations, sorted worst-first. Drill into a campaign to see per-location status. Use **Remind** to send a nudge to assignees at locations that haven't completed yet. Export to CSV for reporting. ### Using the Day Sheet Go to **Day Sheet** and pick a location. This page shows everything landing on that store today across all campaigns, grouped by status, with who holds each piece. It prints for the morning huddle. A "What changed" brief shows new, completed, blocked, and reassigned work over a configurable lookback window (4, 8, 12, 24, 48, or 72 hours). ### Managing the publishing calendar Go to **Calendar**. Every campaign with a start date appears here, colored by department. Admins can create **blackout periods** — no-send windows. A campaign launched by hand during one only shows a warning and is never blocked; a **scheduled** release that falls inside one waits, and goes out when the window ends. ## 5. Settings All settings are at **Apps → Frontline Execution → Settings**, in the order and with the names the page uses. **Available features** | Setting | Default | What it changes | |---|---|---| | **My Day** | On | The worker's single ranked list. Turning it off also removes Day Sheet, Reviews, and every work action on the web, mobile, shared kiosks and the API, and pauses the daily digests and due-soon reminders. | | **Shift pass-downs** | Off | The outgoing shift shares open work, counts and notes with the next shift on My Day, Day Sheet, mobile and shared kiosks; the wrap-up after clocking out in a browser offers it as an optional step. The next shift acknowledges the handover. Shifts the system closed are marked, so a missing handover is not read as an all-clear. | | **Review handover follow-ups** | Off | Requires **Shift pass-downs**. Turn unfinished actions from a saved handover into Tasks items; a person reviews each one before it is created. AI suggests actions while **Enable AI features** is on. | | **Recheck stores after a shared ticket is resolved** | Off | When a linked Service Desk ticket is resolved, asks affected employees whether they can continue, and shows their answers on **Shared blockers**. Resolving the ticket never completes their work. | | **Screen pass-down text** | On | Checks handover notes against your organization's moderation rules before they save, including notes entered on a shared kiosk. Does nothing until your organization's moderation rules are set up. | | **Campaigns** | On | Lets HQ and managers author and launch campaigns. Also removes Requests, Calendar, Categories, the Translations desk, and campaign Q&A. | | **Coverage rollup** | On | Live per-campaign coverage up the location hierarchy. Also removes People, Shared blockers, Analytics, Remind on the coverage roster, Nudge on the Day Sheet, the coverage lines in the manager digest, and Ask AI's coverage answers. | | **Shared kiosks** | Off | Workers who identify at a kiosk with their employee ID and PIN can see, claim, complete and report problems with their work for that location. It is a shared device with no login — turn it on only where the tablet is physically controlled. | **Work rules** | Setting | Default | What it changes | |---|---|---| | **Most critical items one person sees per day** | 3 | Critical items beyond this keep their order on My Day but lose the critical badge, and someone already holding this many can't claim another critical item. 1 to 50. | | **Locations needed to group a blocker** | 3 | The same blocker reported at this many locations on one campaign becomes one shared blocker. 2 to 50. | | **Directive-work budget per person per day (minutes)** | 60 | The budget the workload gauges in the campaign form, the Request queue and Ask AI measure against. | | **Only allow completing work while on shift** | Off | Only workers who are clocked in, or on a scheduled shift (not a draft or on-call standby, with a 15-minute grace window either side), can complete work. | | **Allow saving work offline** | Off | On the mobile site, workers can save photos, signatures and submissions on their device; they upload when connected and must still pass the required checks. Claiming shared work, and submitting work that needs a location check, still need a connection. | | **Only allow completing work at the location itself** | Off | Uses the Time & Attendance geofence. Locations without one are unaffected. | | **Only assign work to people on shift** | Off | Refuses assignment to anyone not on shift — scheduled at the location (not a draft or on-call standby), or clocked in there right now. People on approved leave are never assigned. A location whose roster is still a draft may have work left unassigned. | | **Someone else must approve submitted work** | On | The person who did the work can't approve it. Even when off, campaigns requiring photo or signature proof never allow self-approval. | | **If a training check can't be completed** | **Block the work until training can be confirmed** | Only for campaigns that require a course. The other choice is **Let the work through**. | | **Let managers override a training block** | Off | A manager can release one piece of work past its training requirement, with a reason recorded permanently. | **Release schedule** | Setting | Default | What it changes | |---|---|---| | **Release frequency** | **No scheduled releases — launch anytime** | **Weekly release** or **Daily release** batch scheduled campaigns, which then publish automatically on the day and hour below. | | **Release day (weekly)** | Monday | Which day a weekly release goes out. Ignored for daily releases. | | **Release hour (0–23)** | 6 | The hour the release goes out, in your company's time zone (UTC when the company has none set). | | **Request lead time before a release (days)** | 3 | Late requests are still accepted, but flagged in the Request queue. 0 turns the cutoff off. | | **Require approval before a campaign can launch** | Off | Manual and scheduled launches need approval through a "Campaign publication" approval workflow. Set up that workflow first, or campaigns cannot launch. | **Authoring & language** | Setting | Default | What it changes | |---|---|---| | **Content standards for the writing check** | *(empty)* | The campaign's **Check writing** button scores drafts against this text. Up to 5,000 characters. | | **Worker-language pilot** | **None** | Up to two languages (**First language**, **Second language**). Matching workers get translated instructions, proof requirements, blocked reasons and review notes. Needs **Translate work into each worker's language**. | | **Warn when translations aren't ready at launch** | Off | Before launch, flags worker languages whose translation isn't finished yet, and queues the missing ones. Shown while **Campaigns** is on. | | **Keep the warning until translations are verified** | Off | The warning above stays until a person verifies each language on the Translations screen. It is advisory — it does not block anyone from launching. Applies only when the warning above is on. | **Notifications** | Setting | Default | What it changes | |---|---|---| | **Send managers a daily execution digest** | Off | Each morning, managers get one summary of their span: due, overdue, blocked, awaiting review, and completions. Paused while **My Day** is off. | | **Send workers a daily "your day" digest** | Off | One morning push to anyone with assigned or claimable work; anyone with no work is skipped. Paused while **My Day** is off. | | **Remind the assignee this many hours before work is due** | 4 | Sends once per assigned item; unclaimed work escalates instead. 0 turns reminders off. Paused while **My Day** is off. | **AI** | Setting | Default | What it changes | |---|---|---| | **Enable AI features** | On | One switch for every AI feature in this app: the Ask AI assistant, the photo proof-check on the review queue, the **Check writing** pass on campaign drafts, the microphones (dictation on work items and the assistant on shared kiosks), machine translation, handover follow-up suggestions, and the "Describe it and let AI fill the form" bar. With it off, none of them run. | | **Translate work into each worker's language** | On | Campaign titles and instructions show in each worker's profile language, including the worker-language pilot. Requires **Enable AI features**. | ## 6. More help - **Frontline Execution FAQ** — specific setup and operating questions, limits, and troubleshooting. - Ask AI — the assistant answers questions about Frontline Execution from these articles. **Keywords:** frontline execution, campaign, my day, coverage, day sheet, store execution, task execution, work list, campaign request, blocker, proof, kiosk execution, release cadence, frontline-execution, frontline_execution --- # Frontline Execution FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Frontline Execution — for the admin running it. # Frontline Execution FAQ Answers to common setup and operating questions about Frontline Execution. For what the app is and how to set it up from scratch, see the [Frontline Execution Overview](/help/articles/frontline_execution_app_overview). --- ## Setup ## Do I need to configure anything before campaigns work? Yes. Frontline Execution requires a licence and is disabled by default. Enable it from Admin → Apps → All Apps. Once enabled, three surface toggles under **Available features** in Settings — **My Day**, **Campaigns**, and **Coverage rollup** — are on by default. My Day also gates the Day Sheet, the Reviews queue and every work action, and the daily digests and due-soon reminders pause while it is off. Campaigns also gates Requests, the publishing Calendar, Categories, the Translations desk and campaign Q&A. Coverage rollup also gates People, Shared blockers, Analytics, Remind on the coverage roster, Nudge on the Day Sheet, the coverage lines in the manager digest, and Ask AI's coverage answers. ## Who can author and launch campaigns? Administrators, app administrators, and managers. Managers are scoped to their own subtree of the location hierarchy at query time, so they can only target locations they manage. ## Who can change Frontline Execution settings? Only administrators and app administrators. All other users, including managers, are redirected if they try to reach the Settings page. --- ## Permissions and access ## Why can't a manager see the Coverage, People, Shared blockers or Analytics tabs? All four are gated on two conditions: the **Coverage rollup** toggle must be on, and the user must be an administrator, app administrator, or manager. If the toggle is off, those tabs disappear for everyone, including admins. ## Why can't some employees claim work posted at their location? Two things can keep work from someone. First, if the campaign names an expected role, the work is reserved for people holding that role — anyone without the role doesn't see it among the work they can claim at all. Second, once someone is already holding the maximum number of critical items for the day (**Most critical items one person sees per day**, default 3, configurable from 1 to 50 in Settings), the platform refuses any further critical claims until they finish or release one. --- ## Day-to-day ## What happens when the assigned person quits, goes on leave, or transfers? Nothing breaks. Work is bound to a location and a role, not to a person. When someone leaves, their open work stays with them until its deadline passes; then the campaign's unfinished-work rule moves it — by default to whoever holds the role, or, if the campaign says so, back to the pool, to the next shift, or to the accountable manager. A manager can hand it off sooner. The due date, proof requirements, and coverage numbers are untouched. Every change is written to an append-only history showing who held the work and why it moved. ## How does the app decide who gets the work? Assignment checks five things in order: the person must be an active member, mapped to the location (or anywhere above it in the location tree), holding the required role if the campaign names one, not on approved leave, and holding any required certifications that are still current. People on shift at the location — scheduled there (a draft roster or on-call standby doesn't count), or clocked in there right now — are preferred over those who are not. A setting called **Only Assign Work to People on Shift** makes that preference a hard rule, but it is off by default because it can leave a location with no one on the hook. ## Why do I have to pick a reason when I hand work to someone else? A hand-off overrides the assignment the system made, so it asks why: **Not scheduled or off shift**, **On leave or out sick**, **Needs different skills or training**, **Already has too much on**, or **Something else** (which needs a short note). The reason goes on the work's history and is what the previous holder reads. It is also how the platform learns: if managers keep handing work off because the person was not on shift, Muscle Memory proposes turning on **Only assign work to people on shift**. Your note is never analysed — only the reason you picked is counted. ## What happens when a shift ends and work is unfinished? Nothing moves at the end of the shift itself. Once the work's deadline has passed, the rule the campaign chose under **If the work is still open when it's due** decides: **Hand it to whoever holds the role now** (the default), **Put it back in the pool**, **Hand off to the next shift**, or **Escalate to the accountable manager**. After 5 attempts with no completion, the work is marked missed. A campaign can optionally raise a corrective action automatically when work is missed. ## Can a campaign recur automatically? Yes. Campaigns can repeat daily, weekly, monthly, or on every published shift — per location, or per assigned shift employee. Weekly requires at least one day of the week. Every recurring schedule must have an end date — it will not run indefinitely by omission. Each occurrence creates a separate child campaign so that coverage is counted per occurrence rather than across the whole run. --- ## Proof and review ## Can I require proof before work counts as done? Yes. A campaign can require a photo, a signature, or both, and the server refuses to mark the work done until the proof is present. This rule is enforced identically on the web, mobile, kiosk, the API, and the AI assistant — no surface is a way around it. Acknowledgement-type and inspection-type campaigns cannot carry proof requirements because they have no attachment point for photos or signatures. ## Can the person who did the work approve their own submission? Not by default. **Someone Else Must Approve Submitted Work** is on out of the box and applies everywhere work is reviewed — the review queue, bulk accept, the mobile app, the API, and the AI assistant. Administrators are not exempt. You can turn the rule off in Settings for lower-risk work, but it still holds on any campaign that requires photo or signature proof. ## Why was my reviewer told "You can't review your own work"? The separation-of-duties rule prevents the person who completed the work from also approving it. This applies regardless of role, including administrators. The rule cannot be overridden on campaigns that require photo or signature proof, even if the setting is turned off. ## Why did a send-back come through without telling the worker what to fix? It shouldn't. The platform requires at least 4 characters in the reviewer's note when sending work back. The note is the only thing the worker sees, so a blank send-back would leave them guessing. This rule applies on every surface — web, mobile, API, and AI assistant. --- ## When something looks wrong ## "I can't see next week's work on My Day" My Day only shows items from active campaigns whose eligibility window includes the current time. If the campaign sets a "work available from" and "work available to" window, items outside that window do not appear. Also confirm the worker is mapped to a location the campaign targeted and holds the required role, if one is set. ## "I finished the work but it still shows as open" If the campaign requires review, completing the work submits it rather than finishing it. It moves to the Reviews queue and stays there until a reviewer accepts or sends it back. The Coverage page counts it as **Submitted**, not done, until the review is complete. ## "The training check won't let me complete this work" The training gate fails closed by default: if the platform cannot confirm the worker has completed the required course, the work is blocked. Two escape hatches exist. First, you can change **If a Training Check Can't Be Completed** from **block** to **allow** in Settings — this restores fail-open for tenants where an outage must never stop the floor. Second, you can turn on **Let Managers Override a Training Block**, which lets a manager record an override on one specific piece of work with a written reason kept permanently. The override requires at least 10 characters and names who granted it. ## "The shift fence is blocking someone who is actually on shift" The shift fence lets through anyone who is clocked in, or who is on a scheduled shift with a 15-minute grace period on each side. A shift on a draft roster, or on-call standby, does not count, and someone who clocked out early is off shift even before their shift's scheduled end. If the platform cannot look the answer up at all, the fence lets the worker through — it never locks someone out on missing data. If the problem persists, check whether the worker is clocked in, and whether their schedule has been published (or sent for approval) in the Scheduling app. ## "Forty stores all reported the same problem and I have to review each one" Open the **Shared blockers** tab under Manage. When at least 3 locations (configurable from 2 to 50 in Settings under **Locations Needed to Group a Blocker**) report the same structured problem on the same campaign, it appears as one grouped issue. From there you can raise a single Service Desk ticket that names all affected locations. The group is computed from live data, so as stores clear their blockers the group shrinks automatically. --- ## Licensing and limits ## Does Frontline Execution require a licence? Yes. It requires a licence and is disabled by default. An administrator enables it from Admin → Apps → All Apps. ## What are the limits I should know about? | What | Limit | |---|---| | Items shown in one worker's My Day list | 100 ranked, plus 25 claimable | | Critical items per person per day | 3 by default, configurable 1–50 | | Reference documents per campaign | 25 MB per file | | Allowed document types | PDF, Word, Excel, PNG, JPEG, WebP | | Estimated duration per campaign | Up to 480 minutes (8 hours) | | Worker-language pilot | Up to 2 languages per tenant | | Unfulfilled handoff attempts before work is marked missed | 5 | | Shared blocker grouping threshold | 3 locations by default, configurable 2–50 | | Campaign Q&A thread | 20 most recent questions displayed | | Directive-work budget per person per day (overload gauge) | 60 minutes by default, configurable 15–240 | | Due-soon reminder lead time | 4 hours by default, configurable 0–72 (0 turns it off) | | Release hour | 0–23 (tenant-local time; default 6) | | Request lead time before a release | 3 days by default, configurable 0–14 | | Content standards text | Up to 5,000 characters | --- ## More help - [Frontline Execution Overview](/help/articles/frontline_execution_app_overview) - Ask AI — the assistant answers Frontline Execution questions from these articles. **Keywords:** faq, frontline execution, campaign, my day, coverage, assignment, proof, review, blocker, handoff, overdue, not showing, permissions, kiosk, offline, frontline-execution, frontline_execution --- # Google Workspace Sync Overview **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-16 How a Google Workspace identity-provider connection brings your people and your Google groups into OneMango, what you set up first, and how synced groups behave as employee groups. # Google Workspace Sync ## 1. What it is A Google Workspace connection keeps OneMango in step with your Google domain. User sync brings in your people and keeps their details current. Group sync turns the Google groups you choose into employee groups, whose members follow Google. - **Enablement:** a tenant admin adds the connection under **Admin → Integrations → Manage Identity Providers**. Only admins can see or change it. - **What it is not:** it is not single sign-on. Signing in with Google is set up separately under the login methods. A Google Workspace connection syncs people and groups; it does not change how anyone signs in. ## 2. Standing it up 1. In the Google Cloud console, create a service account and download its JSON key. Turn on domain-wide delegation for it. 2. Go to **Admin → Integrations → Manage Identity Providers**, click **Add Connection** and choose **Google Workspace**. 3. Fill in **Google Workspace Domain** and **Admin Email (for Domain-Wide Delegation)**, then paste the key into **Service Account JSON**. 4. Expand **Scopes to grant in the Google Admin console** and grant those scopes. Do this in the Google Admin console, under Security › API controls › Domain-wide delegation, using the service account's client ID. There are three scopes, all read-only: - `https://www.googleapis.com/auth/admin.directory.user.readonly` — user sync - `https://www.googleapis.com/auth/admin.directory.group.readonly` — group sync - `https://www.googleapis.com/auth/admin.directory.group.member.readonly` — group sync 5. Save the connection, then click **Test** on its page. A passing test makes a new connection active (a connection an admin deactivated is switched back on with **Activate Connection**). The result also says whether group sync can work: **"Group sync is available."** or **"Group sync is not available yet: …"**. 6. Run **Sync → Full Sync** once so your people are linked before any group is synced. 7. In the **Groups** card, click **Choose groups** and decide which Google groups become employee groups (see §3). Group sync depends on two settings. Granting the group scopes in Google does nothing until you also choose groups here; choosing groups does nothing until the scopes are granted. User sync works without the group scopes, so you can roll out people first and groups later. To confirm it worked, open the connection page: - The **Groups** card lists the synced groups, each with how many members came from Google. - Under **What this connection can do**, the **Group sync** row reads **On**. ## 3. How it fits together **User sync and group sync.** User sync decides who exists in OneMango and keeps their name, email and other mapped fields current. Group sync runs after it and only arranges people into employee groups. It never creates anyone. A Google group member who has no OneMango account is left out of the employee group, not invented. **How a group member is matched.** Group sync first looks for the person user sync linked to that Google account. If there is none and the connection matches people by email (it does by default), it looks for an active member here with the same email address. This is how someone with an outside address in a Google group still lands in the right employee group. It will not match: - an address nobody has confirmed yet; - an address two members share; - a deactivated member; - someone suspended in Google. **Which groups sync.** The **Group sync** page offers four choices: | Choice | What syncs | |---|---| | **No groups** | Nothing. This is where every connection starts. | | **Every group in Google Workspace** | Every group in the domain. | | **Groups whose email or name starts with…** | Groups matching any prefix you type, e.g. `store-, leads-`. Letter case is ignored. | | **Groups I choose** | Only the groups you tick in the list. | Before you save, a line under the choices says what Save will do. For example: "Saving syncs 3 groups: store-north, store-south, store-west." It also says which synced groups a narrower choice will hand back. Nested groups count. A member of a group inside a synced group is a member of the synced group's employee group. **A synced group is an ordinary employee group, with one owner per member.** Google owns the members it added. Anyone an admin adds to that employee group by hand stays through every sync. The group's page says **"This team is synced from …"** and how many members came from Google. Changes there behave differently because Google is the source: - Rename the group in Google, not here; the next sync puts Google's name back. - Someone you remove by hand comes back on the next sync if they are still in the Google group. - A synced group cannot be deleted. Remove it in Google, or take it out of the connection's group sync. **Archived versus handed back.** These two are easy to confuse: - **Archived** — the group was deleted in Google. Its employee group is deactivated and loses the members Google added. Its name gains "(Google Workspace archived …)". - **Handed back** — you stopped syncing the group (chose **No groups**, or left it out of your choice). Its employee group stays active with all its members, as an ordinary group nobody syncs. If you choose that group again later, the same employee group (and workspace) is taken back rather than a new one created. Example: you sync every group, then change to **Groups whose email or name starts with…** `store-`. At the next group sync, `store-north` and `store-south` stay synced. `marketing` and `finance` are handed back as ordinary employee groups, members kept. **Workspaces per group.** Optionally, each synced group also gets a workspace with a named owner. Synced members get access without a notification and lose it when Google removes them. People the workspace owner adds stay. **Boundaries with other areas.** - **Employee groups:** synced groups appear in Employee groups like any other. Admins see a **Manage Google Workspace connection** link on them there. - **SCIM:** a SCIM connection pushes groups to OneMango instead, and has its own Groups card. A Google Workspace connection pulls them on a schedule. - **Okta, Entra ID and MangoApps Hub:** these connections sync people but not groups. The connections list shows "—" in their **Synced Groups** column. ## 4. Running it ### Let it run on its schedule Delta sync runs every 4 hours by default, and a full sync weekly. Group sync runs right after each successful full or delta sync, so groups follow Google within the same cycle. A deactivation sync does not trigger a group sync. ### Sync groups now On the connection page, click **Sync → Group Sync**. It appears once groups are chosen. The run happens in the background. Reload the page when it finishes; a large domain takes a minute or two. ### Change which groups sync 1. On the **Groups** card, click **Choose groups**. 2. Pick a choice. Read the line under the choices before saving: it says what will sync and what will be handed back. 3. Click **Save group sync**. A group sync starts straight away when the connection is active. ### See who was left out, and why The **Groups** card says how many members of the synced groups are not in their employee groups here. Click **See who and why** to open **Sync logs**. Each group sync row there shows what the run did, for example "Groups: 132 synced · members: 3 joined · 2 members left out". Open the row to see, per group, each person left out and the reason: - suspended in the provider; - switched off or no longer a member here; - no Workforce account this connection could match. ### Stop syncing groups Choose **No groups** and save. Every synced group is handed back at once, with its members kept, and nothing more is read from Google. Deleting the whole connection does the same for its groups. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Groups to sync | Groups card → **Choose groups** | **No groups** | Which Google groups become employee groups | | **Also create a workspace for each synced group** | Groups card | Off | Each synced group also gets a workspace; requires a **Workspace owner** | | **Unmatched User Policy** | Connection → **Edit** | **Skip (don't create users)** | Whether user sync creates people it cannot match. **Auto-create users** creates them. Group sync never creates anyone. | | **Delta Sync Frequency** | Connection → **Edit** → **Advanced Sync Settings** | **Every 4 hours** | How often changed people sync, and so how often groups sync | | **Full Sync Frequency** | Connection → **Edit** → **Advanced Sync Settings** | **Weekly** | How often everyone is re-read | | Field Mappings | Connection page | Google's default fields | Which Google fields fill which profile fields. Email, first name and last name always come from Google's default fields when a custom mapping leaves them out. | ## 6. More help - **Identity providers and SCIM** — the SCIM connection page explains how pushed groups and people work. - **Employee groups** — how employee groups are used across scheduling, audiences and access. - Ask AI — the assistant answers questions about Google Workspace sync from these articles. **Keywords:** google workspace, google groups, group sync, directory sync, identity provider, user sync, employee groups from google, domain-wide delegation, service account, synced groups, why is someone missing from a group, workspace per group --- # Guest Pass App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run Guest Pass — visitor pre-registration, check-in, digital badges, watchlist screening, and host notifications. # Guest Pass ## 1. What it is Guest Pass manages visitors from registration through check-out. Employees pre-register guests, or guests self-register through a public link. Each approved visitor receives a QR-code digital badge, and the host is told when their guest arrives and departs. - **Enablement:** Guest Pass is pay-as-you-go. It is available in Admin → Apps → All Apps with no license to purchase; you are billed per visitor check-in. - **What it is not:** Guest Pass tracks who is on-site. It does not reserve rooms, desks, or workspaces — that is Bookings. When a booking includes external guests, Bookings hands them off to Guest Pass for check-in, badges, and screening. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Guest Pass**, and enable it. 2. Configure access: in **Admin → Access Management**, set which audience (departments, locations, or roles) can open the app. Access is governed by platform Access Management, not by a setting inside Guest Pass. 3. Open **Guest Pass → Settings** and review the defaults. The settings that most affect behaviour are **Let hosts approve their own visitors** (on by default), **Auto-Approve Visitors** (off by default), **Enable Guest Self-Registration** (off by default), **Enable Visitor Watchlist** (on by default), and the three **User Permissions** pickers (who runs the front desk, who approves, who opens the security records). 4. For an unattended lobby tablet, open the **Check-In Scanner** from the Guest Pass **Dashboard** and leave it on the tablet: visitors scan their badge QR to check themselves in. The scanner works whether or not self-registration is on. If you also turn on **Enable Guest Self-Registration**, Settings shows two links — one to share with guests for their own phone or laptop, and a lobby-kiosk version for a tablet you leave out front. 5. To confirm it works, pre-register a test visitor from **Guest Pass → My Visitors → Pre-Register Visitor**. The visitor should appear as **Pending**, and whoever decides it should be asked. **Self-registered guests always wait for a decision.** A guest who registers through the public page is never approved automatically — not by **Auto-Approve Visitors** and not by a host's own auto-approve preference — because nobody has vouched for them yet. Their visit waits for its host's one-tap link (when hosts approve by email) or for an approver in **Pending Approval**. ## 3. How it fits together **Visitors and their lifecycle.** A visitor record captures who is coming (name, email, company, phone, purpose), who is hosting them, and the expected arrival and departure window. Every visitor moves through a status lifecycle: > **Pending** → **Approved** → **Checked In** → **Checked Out** A visitor can also be **Declined**, **Cancelled**, or **Expired** (a no-show whose expected departure has passed). Only approved visitors can be checked in. Checking in records the actual arrival time; checking out records the actual departure and deactivates the badge. **Example:** Jan Kolar from Acme Corp visits on Tuesday. The host pre-registers Jan with an expected arrival of 10:00 AM and departure of 2:00 PM. Jan starts as **Pending**. The host (or an approver) approves Jan → status moves to **Approved** and a QR badge is generated automatically. At 10:05 AM the front desk checks Jan in → **Checked In** and the host is told. At 1:50 PM Jan checks out → **Checked Out** and the badge is deactivated. **Party size.** A single registration can cover a party of up to 50 people. The party size defaults to 1. **Visitor types** determine the badge color and default access tier. There are four types: **Visitor** (standard, blue badge, basic access), **Contractor** (orange, standard access), **VIP** (purple, VIP access), and **Escort Required** (red, basic access — the visitor must be accompanied). The type is set at registration and governs the badge that is generated. **Digital badges.** When a visitor is approved, the system generates a QR-code digital badge automatically. The badge carries the visitor's name, host and company, and keeps working until the visit's expected departure plus the **Badge Expiry (Hours)** setting (24 hours by default). The visitor's approval email links to their badge, which they show on their phone or print. Staff can download a badge as PNG or SVG or print it as a PDF; where Apple Wallet is set up for your organization, people with security-records access can also issue an Apple Wallet pass from the visit page. Google Wallet is not supported. At a self-service kiosk, scanning the badge QR checks the visitor in. Badges can be revoked, reactivated, or regenerated individually or in bulk from **Digital Badges**. Each badge has an access level from 1 (basic) to 10 (emergency), set automatically from the visitor type. **Watchlist screening.** The watchlist is a register of flagged people. Each entry has a name, a risk level (**Low**, **Medium**, **High**, or **Critical**), a reason, and an optional expiry date. Visitors are matched by name, email, or phone against active watchlist entries at both approval and check-in. A match holds the visit for security review, and only people with security-records access are told which entry matched and its risk level — anyone else is told the visit is held. At a self-service kiosk, a flagged visitor sees only a general check-in refusal, never that they were flagged. **Automated housekeeping.** Three background jobs run on schedule: - An hourly reminder job sends overdue-checkout alerts to hosts (re-alerting every 4 hours, for up to a day after the visitor was due to leave) and one-time visit reminders to approved visitors arriving within 24 hours. - An hourly no-show sweep expires visitors still pending or approved past their expected departure, moving them to **Expired** and deactivating dangling badges. - A daily retention job purges visitor records (and their badges, photos, and access logs) older than the configured **Data Retention (Days)** setting. **Host notifications.** The host is told when a visitor is registered, arrives, departs, and when a check-out is overdue. Arrival and departure notices follow **Notify on Visitor Arrival** and **Notify on Visitor Departure** in Settings, and each host can turn any of these off, or switch off a channel, in their own **Host Preferences**. Approved visitors receive an email with a link to their badge and a calendar (.ics) invite. When **Let hosts approve their own visitors** is on, the host of a pending visit is asked to decide it: their email carries one-tap approve / decline links that work without signing in, the same ask appears in their Inbox, and they can decide from the visit's page. A visit that was declined or cancelled and then edited back to pending goes to the approvers instead — its host is not asked again. **Host preferences.** Each employee can set their own preferences: auto-approve known visitors (someone they have hosted before, with the same email, whose earlier visit was checked in — and only where they may approve their own visitors), set a default visit duration (8 hours by default), define their weekly availability schedule and quiet hours, choose notification channels (email, push, in-app, SMS), and set default access permissions for the areas their visitors can reach. **Integrations.** Bookings creates a Guest Pass visitor record when a room booking includes an external guest. Appointment Scheduler links appointments to Guest Pass visitors for check-in and badge tracking. ### Roles and who sees what Three of these tiers are set on **Guest Pass → Settings → User Permissions**; the other two are fixed. Business admins and Guest Pass app admins always hold every tier. | Tier | Who | What they can do | |---|---|---| | **Everyone in the app** | Any employee with app access | **My Visitors** (visits they host or registered) and **Host Preferences**. Pre-register visitors for themselves; edit their own visit while it is Pending, Declined or Cancelled; cancel their own visit while it is Pending or Approved. | | **Front desk** | **Who can run the front desk?** (default: managers and above), plus anyone holding the Guest Pass "Contributor — records only" grant | The **Dashboard**, the **Visitors** lists (All Visitors, Expected Today, Checked In), **Import Visitors**, the **Check-In Scanner** link, registering visitors for any host, and checking visitors in and out. | | **Approver** | **Who can approve a visitor?** (default: managers and above) | **Pending Approval** — approve or decline any pending visit. When **Let hosts approve their own visitors** is on, a visit's own host can also approve or decline that visit, from the email link, their Inbox, or the visit page. | | **Managers** | Managers and above, plus Guest Pass app admins (fixed) | The **Dashboard** (even outside the front desk), the **Security Dashboard**, **Reports** and **Analytics**, the **Check-In Scanner** link, and cancelling anyone's pending or approved visit. | | **Security records** | **Who can open the security records?** (default: admins and Guest Pass app admins) | **Real-Time Status**, **Access Logs**, **Digital Badges**, the **Watchlist**, the Security Audit report, and editing any visit at any status. | | **Settings** | Admins and Guest Pass app admins (fixed) | **Settings**, Reset to Defaults, and sample data. | An employee with only basic access sees **My Visitors** and **Host Preferences**. They can pre-register visitors they host themselves but cannot open the org-wide front-desk board. ## 4. Running it ### Approving visitors 1. Go to **Guest Pass → Visitors → Pending Approval** (an approver who does not run the front desk sees **Pending Approval** on its own in the menu). 2. Review the visitor's details, purpose, and host. 3. Click **Approve** or **Decline** (with an optional reason, which is emailed to the visitor). On approval, the system generates a digital badge and emails the visitor a link to it and a calendar invite. On decline, the visitor receives a declined notice. Where hosts approve by email, a host decides their own visitor from the one-tap link, their Inbox, or the visit's page. ### Checking visitors in and out The front desk checks visitors in and out from the **Visitors** lists or the visitor's detail page: **Check In** records the arrival time and tells the host (when arrival notices are on), and **Check Out** records the departure time and deactivates the badge. At an unattended kiosk running the **Check-In Scanner**, visitors scan their badge QR to self check in. ### Bulk pre-registration Go to **Guest Pass → Visitors → Import Visitors** to upload a CSV or paste rows. Each row creates a visit under the same rule as a visit an employee registers: it starts **Pending** and waits for a decision unless auto-approval applies. ### Managing the watchlist Go to **Guest Pass → Security → Watchlist** (security-records access; visible when the watchlist is enabled). Add entries with a name, risk level, reason, and optional email, phone, or expiry. Entries can be resolved, deactivated, or made permanent. Active entries are checked automatically at approval and check-in. ### Running reports Go to **Guest Pass → Reports → All Reports** (managers and above). Four reports are available, each downloadable as CSV or PDF; the Security Audit report needs security-records access: - **Visitor Summary** — visitor volume and trends - **Security Audit** — security events and compliance trail - **Host Activity** — host engagement and approval activity - **Badge Usage** — badge issuance and scan activity ### Reviewing the access log Go to **Guest Pass → Security → Access Logs** (security-records access). Every visitor action (registration, approval, check-in, check-out, badge scan, watchlist match) is logged with a timestamp, the acting user, and success/failure status. Failed access attempts and watchlist matches are flagged as security events and appear in the Security Dashboard. ### Using the Security Dashboard Go to **Guest Pass → Security → Security Dashboard** (managers and above). The dashboard shows recorded activity, failed activity (all time and today), the visitors currently flagged for security review, and recent security alerts. To see who is on site right now — during an evacuation or a security incident — go to **Guest Pass → Security → Real-Time Status** (security-records access). ### Analytics Go to **Guest Pass → Reports → Analytics** (managers and above). Visitor volume trends, popular visit times, host activity summaries, badge usage statistics, and a compliance score are available for 7-day, 30-day, or 90-day windows. ## 5. Settings Settings are at **Guest Pass → Settings** (admins and Guest Pass app admins). | Setting | Default | What it changes | |---|---|---| | **Enable Guest Pass Agent** | On | Whether people can use the Guest Pass Agent in Ask AI to register visitors, check them in and out, and look up visits. | | **Auto-Approve Visitors** | Off | When on, a visit an employee registers is approved at once and its badge issued — unless it matches the watchlist. While **Let hosts approve their own visitors** is on, it applies only to visits a host registers for themselves. Guests who self-register always wait for a decision. | | **Enable Guest Self-Registration** | Off | When on, opens a public registration page where guests enter their own details and pick their host, and shows its two links (for a guest's own device, and for a lobby kiosk). | | **QR Code Badges** | On | Whether visitor digital badges carry a QR code. | | **Badge Expiry (Hours)** | 24 | How many hours a digital badge keeps working after the visit's expected departure. A badge always covers its own visit, however far ahead it was approved. | | **Include Visitor Photo** | On | Whether the visitor's photo is shown on their digital badge, the printable badge and the lobby check-in screen. Photos are optional. | | **Notify on Visitor Arrival** | On | Whether the host is told when their visitor checks in. Each host can still turn this off for themselves in Host Preferences. | | **Notify on Visitor Departure** | On | Whether the host is told when their visitor checks out. | | **Send Visitor Welcome Email** | On | Whether the visitor gets a welcome email when they check in. | | **Send Visitor Thank-You Email** | On | Whether the visitor gets a thank-you email when they check out. | | **Who can run the front desk?** | Managers and above | Who sees every visit, registers visitors for any host, imports visitors, and checks visitors in and out. People holding the Guest Pass "Contributor — records only" grant are included automatically. | | **Who can approve a visitor?** | Managers and above | Who works **Pending Approval** and can approve or decline any pending visit. | | **Who can open the security records?** | Admins and Guest Pass app admins | Who opens the watchlist, access logs, digital badges, Real-Time Status and the Security Audit report, and can edit any visit. It does not include Settings. | | **Let hosts approve their own visitors** | On | Whether each pending visit's host is asked to decide it, with one-tap approve / decline links, an Inbox ask, and the buttons on the visit's page. Approvers can always decide in the app. While on, **Auto-Approve Visitors** applies only to visits a host registers for themselves. It does not decide whether visitors need approval — **Auto-Approve Visitors** does. | | **Data Retention (Days)** | 365 | How long visitor records (and their badges, photos, and access logs) are kept before the nightly retention job purges them. | | **Enable Visitor Watchlist** | On | Whether visitors are screened against the watchlist at approval and check-in. | | **Email Security Alerts** | On | Whether security alerts (denied access, watchlist hits, overdue check-outs) are emailed to the security team. | | **SMS for Critical Alerts** | Off | Whether critical security alerts are also sent by SMS. | | **In-App Security Alerts** | On | Whether the security team also gets security alerts in-app and by push. | | **Notify the Host's Manager** | On | Whether the visitor's host's manager is also alerted (not every manager in the business). | | **Alert Security on Overdue Check-Out** | On | Whether the security team is alerted when a visitor stays past their expected departure. Off, only the host is told. | | **Security team (who handles security alerts)** | None | The group that receives security alerts, alongside the visitor's host. With none selected they go to Guest Pass app admins — and if nobody holds that role, to every admin in the business. | ## 6. More help - **Guest Pass FAQ** — specific setup, operating, and troubleshooting questions. - Ask AI — the Guest Pass Agent can register a visitor, look up visits, approve or decline the ones you may decide, check visitors in or out if you run the front desk, and answer questions about Guest Pass from these articles. **Keywords:** guest pass, visitor management, visitor check in, visitor badge, visitor registration, watchlist, digital badge, QR code badge, pre-register visitor, self-registration, host notification, visitor approval, guest-pass, guest_pass --- # Guest Pass FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Guest Pass — for the admin running it. # Guest Pass FAQ Answers to common setup and operating questions about Guest Pass. For what the app is and how to set it up from scratch, see the [Guest Pass Overview](/help/articles/guest_pass_app_overview). --- ## Setup ## What do I need to configure before Guest Pass does anything useful? Four settings control how the app behaves out of the box. **Auto-Approve Visitors** is off by default, so every new visit waits as **Pending** until someone approves it. **Let hosts approve their own visitors** is on by default, so the visit's host is asked to decide it (by a one-tap email link, an Inbox ask, or the visit's page) — approvers can always decide it too. **Enable Guest Self-Registration** is off by default, so only employees can register visitors. **Enable Visitor Watchlist** is on by default, so visitors are screened at both approval and check-in. At minimum: enable the app in Admin → Apps → All Apps, set up who can access it in **Admin → Access Management**, review the three **User Permissions** pickers in Guest Pass settings, and have someone pre-register a test visitor to confirm the approval and notification flow works. ## I turned on self-registration but guests are stuck waiting — what happened? That is by design: a guest who registers through the public page always starts as **Pending**, and nothing approves them automatically — not **Auto-Approve Visitors**, and not a host's own auto-approve preference — because anyone can fill in that form and nobody has vouched for the visit yet. The visit waits for a person to decide it. When **Let hosts approve their own visitors** is on, the host they picked gets a one-tap approve / decline link and an Inbox ask; approvers can always decide it from **Pending Approval**. If guests are waiting too long, check that the hosts they pick are reading those asks, or that your approvers are working the queue. --- ## Permissions and access ## Who can approve or reject visitors? The people named by **Who can approve a visitor?** in **Guest Pass → Settings → User Permissions** (default: managers and above; you can pick a group or named people instead). Business admins and Guest Pass app admins can always approve. They decide any pending visit from **Pending Approval**. When **Let hosts approve their own visitors** is on, a visit's own host can also approve or decline that one visit — from the one-tap email link, their Inbox, or the visit's page. A visit that was declined or cancelled and then edited back to pending is decided by an approver, not its host. ## Why can't an employee see the Visitors tab or the dashboard? An employee with basic app access sees only **My Visitors** (visits they host or registered) and **Host Preferences**. The rest of the menu follows who they are: - **Dashboard** and the **Visitors** lists (All Visitors, Expected Today, Checked In, Import Visitors) — the front desk: **Who can run the front desk?** (default: managers and above), plus anyone holding the Guest Pass "Contributor — records only" grant. Managers and above also see the Dashboard, even outside the front desk. - **Pending Approval** — approvers: **Who can approve a visitor?** (default: managers and above). - **Security Dashboard**, **Reports** and **Analytics** — managers and above (fixed). - **Real-Time Status**, **Access Logs**, **Digital Badges** and **Watchlist** — **Who can open the security records?** (default: admins and Guest Pass app admins). - **Settings** — admins and Guest Pass app admins (fixed). The three pickers are in **Guest Pass → Settings → User Permissions**. Business admins and Guest Pass app admins always see everything. --- ## Day-to-day ## How do visitors check in? Two ways. A visitor can scan their badge QR code at an unattended kiosk or tablet to self check in. Alternatively, the front desk can check them in from the **Visitors** lists or the visitor's detail page, on desktop or phone. Either path records the actual arrival time and tells the host, when arrival notices are on. Watchlist screening runs again at check-in even if the visitor was already screened at approval. ## What happens when a visitor is approved? The system generates a QR-code digital badge automatically, sends the visitor an approval email with a link to their badge and a calendar invite (.ics file), and notifies the host. The badge works until the visit's expected departure plus 24 hours by default (configurable in settings under **Badge Expiry (Hours)**). The visitor's status moves from **Pending** to **Approved**, and they can now be checked in. ## Can a host auto-approve their own visitors without an admin turning it on for everyone? Partly. Each host can turn on **Auto-approve known visitors** in their **Host Preferences**, independently of the app-level **Auto-Approve Visitors** setting. It approves a visit for them only when all of these hold: - they have hosted this visitor before — an earlier visit with the same email that was checked in; - they may approve their own visitors — **Let hosts approve their own visitors** is on, or they are an approver; - the visitor does not match the watchlist and does not need an escort; - the guest did not register themselves on the Guest Pass public page (those always wait for a decision). A guest who books a meeting with the host through Appointment Scheduler counts as the host's own registration. ## How does watchlist screening block a visitor? The watchlist is checked at both approval and check-in. If an active, unexpired watchlist entry matches the visitor by name, email, or phone, the action is blocked and the visit is held for security review. Only people with security-records access are told the name and risk level of the matching entry; an approver or receptionist without it is told only that the visit is held for security review. At a self-service kiosk, the visitor sees only a general check-in refusal and is never told they were flagged. You can disable screening entirely by turning off **Enable Visitor Watchlist** in settings. ## Can I change a visitor's details after they are registered? It depends on who you are and where the visit stands: - **The visit's host, or the person who registered it,** can edit it while it is **Pending**, **Declined**, or **Cancelled**. Editing a declined or cancelled visit sends it back to **Pending** for an approver to decide. Once it is approved, checked in, checked out, or expired, they can no longer change it. - **People with security-records access** (**Who can open the security records?**) can edit any visit at any status. - Running the front desk does not by itself let you edit other people's visits. Only the front desk can move a visit to another host. Editing an approved visit does not email the visitor; use **Resend Notifications** on the visit page (or ask the front desk to) to email them their updated badge and calendar invite — where your organization sends email. --- ## When something looks wrong ## "My visitor was supposed to be auto-approved but they're stuck on Pending" Several things keep a visit pending. With the app-level **Auto-Approve Visitors** on: the visitor matches an active watchlist entry, the guest registered themselves through the public page, or **Let hosts approve their own visitors** is on and the person who registered the visit is not its host. With a host's own **Auto-approve known visitors** preference: the host has not hosted this visitor (same email) at a visit that was checked in, the visitor needs an escort or matches the watchlist, or the host may not approve their own visitors (**Let hosts approve their own visitors** is off and they are not an approver). Check the visitor's detail page for a watchlist hold, and the host's **Host Preferences** if they expected their personal auto-approval to apply. ## "I never got notified when my guest arrived" Check three things. First, confirm that **Notify on Visitor Arrival** is on in Guest Pass settings. Second, check your **Host Preferences** — if you turned off "Visitor arrives and checks in", or switched off a channel (email, SMS, push, in-app), you won't hear on that channel. Quiet hours never hold back an arrival; they only keep non-urgent notices off text and push, and there are none unless you set them. Third, verify that your business-level email notifications are enabled, since Guest Pass email alerts respect the platform email setting. ## "A visitor's badge says Expired but they haven't arrived yet" A badge covers its own visit however far ahead it was approved: it keeps working until the visit's expected departure plus the **Badge Expiry (Hours)** setting (24 hours by default). So a badge reads **Expired** before arrival only when its **Valid Until** was shortened by hand, or it reads inactive because it was revoked — someone with security-records access opens it under **Digital Badges** and sets a later Valid Until, or activates it again. A visit, not a badge, can also read **Expired**: the hourly no-show sweep marks a visit Expired when it is still pending or approved after its expected departure has passed, and deactivates its badge at the same time. An expired visit cannot be reopened — pre-register the visitor again for their new date. ## "A visitor I checked in hours ago still shows as on-site" A checked-in visitor stays in that status until someone explicitly checks them out — from the visitor's detail page, the Visitors list, or a mobile check-out action. If the visitor was expected to leave and has not been checked out, the host receives an overdue-checkout alert. These alerts repeat every 4 hours for up to a day after the visitor was due to leave. A check-in still open seven days after the visitor was due to leave is closed automatically. To resolve it, check the visitor out manually. ## "My visitor can't scan their badge at the kiosk" The badge must be active and within its validity window. If it has expired or was revoked, someone with security-records access opens it under **Digital Badges** and sets a later **Valid Until**, or activates it again (Regenerate refuses an expired or inactive badge). Also verify the visitor is in **Approved** status — only approved visitors can check in. Visitors in **Pending**, **Declined**, **Expired**, or **Cancelled** status cannot scan in. --- ## Licensing and limits ## Does Guest Pass require a licence? No. Guest Pass is pay-as-you-go. It is available to every tenant in Admin → Apps → All Apps with no license to purchase and no per-seat fee. You are billed per visitor check-in. Enabling it costs nothing until visitors actually start checking in. ## Are there limits I should know about? | What | Limit | |---|---| | Party size per registration | 1 to 50 | | Badge access levels | 1 (Basic Access) to 10 (Emergency Access) | | Badge expiry | The visit's expected departure plus 1 to 168 hours; default 24 hours | | Visitor photo size | 5 MB maximum (JPEG, PNG, GIF, or WebP) | | Purpose of visit | Up to 1,000 characters | | Watchlist reason | Up to 2,000 characters | | Host default visit duration | Up to 168 hours (1 week) | | Watchlist risk levels | Low, Medium, High, Critical | ## How long are visitor records kept before they are purged? The **Data Retention (Days)** setting controls this. The default is 365 days (30 to 2,555). A nightly retention job permanently deletes visitor records — along with their badges, photos, and access logs — older than the configured window. If you need records for compliance, increase the retention period before they are purged. Deleted records cannot be recovered. --- ## Badge and notification details ## What badge formats can I give visitors? Every approved visitor receives a QR-code digital badge; their approval email links to it, so they can show it on their phone or print it. Staff can download the QR image as PNG or SVG or print a badge PDF, and — where Apple Wallet is set up for your organization — people with security-records access can issue an Apple Wallet pass (.pkpass) from the visit page. Google Wallet is not supported. People with security-records access can revoke, reactivate, or regenerate badges individually or in bulk from **Digital Badges**. --- ## More help - [Guest Pass Overview](/help/articles/guest_pass_app_overview) - Ask AI — the Guest Pass Agent can register a visitor, look up visits, approve or decline the ones you may decide, check visitors in or out if you run the front desk, and answer Guest Pass questions from these articles. **Keywords:** faq, guest pass, visitor management, visitor check in, visitor badge, watchlist, self-registration, host notification, badge expiry, approval, overdue checkout, data retention, QR code, guest-pass, guest_pass --- # Headcount Planner App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run Headcount Planner — workforce plans, hiring budgets, positions, and the Job Board integration. # Headcount Planner ## 1. What it is Headcount Planner lets managers and HR leaders build workforce plans — how many people to hire, in which departments, at what budget — and track those plans through to filled positions. It connects directly to Job Board: **Create Job Posting** turns an approved position into a draft Job Board posting with one click, with its title, salary range, and skills carried over — and from there the position follows the hire on its own. - **Enablement:** Headcount Planner requires a license. An admin enables it from Admin → Apps → All Apps and configures it in the app's **Admin → General Settings** tab. - **What it is not:** Headcount Planner is for planning and budgeting headcount. It does not manage the recruiting pipeline itself — candidates, interviews, and offers live in Job Board, Interview Scheduler, and Offer Manager. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Headcount Planner**. 2. Open the app and go to the **Admin** tab. Turn on the features your organization needs: AI Forecasting, Market Intelligence and Executive Reporting under **General Settings**; the OKR Hub, Recruiting Apps and EPMS pages under **Integration Settings**; the Headcount Agent under **AI Configuration**. These all start off — see **5. Settings** for the two switches that start on. 3. Create your first plan: go to the **Planning** tab → **Plans** → **Create Plan**. Give it a name, choose the type (Annual, Quarterly, Project, Strategic, or Custom), and set the date range. 4. Add at least one scenario to the plan (e.g. Baseline). Inside the scenario, create department budgets — each budget defines the headcount, salary range, and priority for one department and role category. 5. Inside each budget, add positions — each with a title, justification, salary band, and target dates. 6. Grant access: the app is visible to managers and above, plus anyone designated as a Headcount Planner app admin. No separate role assignment is needed beyond the organization's existing manager hierarchy. 7. **Confirm it worked:** Managers should see the Headcount Planner Dashboard with active plans, key metrics, and upcoming milestones. The **Headcount Grid** shows a live view of employees and planned positions. **Silent-until-paired:** A plan does nothing visible until it has at least one scenario with a budget and a position inside it. The Dashboard metrics, Grid, and Analytics all derive from positions — an empty plan shows zeros everywhere. ## 3. How it fits together ### Plan → Scenario → Budget → Position This is the core nesting that governs the entire app. A **plan** covers a set period — typically a year or a quarter. It moves through four statuses: **Draft → Active → Completed → Archived**. Only a draft plan can be edited; only an active plan is visible on the dashboard and tracked by milestones. A completed or archived plan is read-only: positions on it can no longer be added, edited or decided. **Actions → Archive plan** closes a plan on purpose, and activating a plan archives any other active plan. **Validate** marks a plan as reviewed so it can be activated; it does not check the plan's figures. Each plan holds one or more **scenarios** — named what-if versions such as Baseline, Conservative Growth, Optimistic Growth, or Aggressive Expansion. Each scenario carries its own revenue growth assumption, budget constraint factor, and hiring velocity assumption. You can compare scenarios side by side, then mark one as the **selected scenario** — the one the plan's headline metrics reflect. Example: a 2026 Annual Workforce Plan might have three scenarios: | Scenario | Revenue growth | Hiring velocity | Total budget | |---|---|---|---| | Conservative Growth | 5% | 3 hires/month | $1.2M | | Baseline | 10% | 4 hires/month | $1.8M | | Aggressive Expansion | 40% | 10 hires/month | $4.5M | The team compares all three, then selects **Baseline** as the plan of record. Inside each scenario, **budgets** break the plan down by department. A budget defines the planned headcount, salary range, per-position budget, recruiting and onboarding cost estimates, and target dates for one department-and-role combination. The total budget is computed automatically: (positions × per-position budget) + (recruiting + onboarding costs × positions). Inside each budget, **positions** are the individual seats to hire for. Each position has a title, justification type (New Role, Backfill, Expansion, or Replacement), salary band, seniority level (Junior through Executive), priority (Low, Medium, High, or Critical), hiring manager, and target dates. Every position gets an auto-generated position ID in the format DEPT-ROLE-YEAR-###. ### Hiring status and the Job Board handoff Each position moves through a hiring pipeline: **Planned → Approved → Requisition Created → In Progress → Filled** The key transition is **Approved → Requisition Created**. When a manager clicks **Create Job Posting** on an approved position, the app creates a draft Job Board posting with the position's title, salary range, skills, employment type, and hiring manager already filled in; a Job Board admin or the posting's recruiter publishes it. **Create Job Posting** is hidden until Job Board is turned on for your business. From that point the position follows the posting on its own: it moves to **In Progress** when the first applicant arrives, and to **Filled** — recording who filled it and when — the moment the accepted candidate becomes an employee. Those automatic steps appear in the position's timeline as performed by *System*. **Start Hiring** and **Mark Filled** remain available for hires made outside Job Board. An approved position's title, seniority, employment type and compensation are what was approved. Changing any of them returns the position to **Planned** and notifies the approver and the position's stakeholders with what changed; dates, description, skills and managers can be edited freely. The edit form says so before you save. Once a position has a Job Board posting — or is filled, rejected or cancelled — those signed-off fields can no longer change at all; duplicate the position to ask for different terms. A position awaiting approval can be **Rejected**, and a reason is required. The position page then shows who declined it, when and why, with **Ask again (as a new request)** to send a copy for approval. While a position still awaits approval, the person who asked for it can **Withdraw request**, which cancels it. A position can be **Cancelled** at any stage before filling from the Headcount Grid. ### Milestones Each plan automatically tracks milestones — dated checkpoints such as budget approval, quarterly reviews, and completion targets. Milestones can depend on each other and flag themselves as critical-path items. A milestone that is blocked by an unfinished dependency cannot be started until the dependency completes. The system runs a daily sweep that notifies milestone owners about: - **Overdue milestones** — the owner is notified up to once per week while the milestone remains overdue, stopping after 90 days past due. - **Milestones due within 14 days** — the owner gets a heads-up notification. - **Over-budget budgets** — the plan creator is notified when a department budget in the selected scenario runs more than 5% over its plan. - **At-risk plans** — the plan creator is notified when an active plan is off track (milestone completion lags the timeline by more than 10 percentage points, past 25% of the timeline). Notifications go to the in-app bell (and push where opted in) plus a preference-gated email. Sample/demo data never triggers notifications. An admin can turn the whole daily sweep off with **Send deadline alerts and approval reminders** (Admin → General Settings; it starts on). ### Who can access what Headcount Planner is a management surface — it exposes compensation budgets and salary bands. Access requires **Manager or above**, or designation as a **Headcount Planner app admin**. Within the app: - By default, everyone who can open the app can create and edit plans, scenarios, budgets and positions, publish a budget, and approve or reject positions; rebalancing a whole scenario's budgets and editing salary benchmarks are for app admins. Admins change each of these under **Admin → General Settings → Permissions**; business admins and app admins always can. - **Admins and Super Admins** (plus app admins) can manage AI model configuration. - The **Admin** tab — General Settings, Integration Settings, Data Management, AI Configuration — is restricted to admins and app admins. - Department-level access: a manager can raise, edit, approve, reject or delete positions only in a department they are the named manager of, or their own department. Admins and app admins can work in any department. ## 4. Running it ### Starting from a sample plan Go to **Planning → Sample Plans**, open a sample plan and click **Convert to Plan**. Sample plans can be tagged by industry (Technology, Healthcare, Finance, Manufacturing, Retail, Government, Nonprofit or Education). Converting creates a draft plan of your own with a scenario and its department budgets, which you can then customize. ### Comparing scenarios Open a plan, go to **Scenarios**, and click **Compare**. The comparison view shows each scenario's total planned hires, total budget, ROI projection, and hiring velocity assumption side by side. ### Approving positions and starting hiring 1. Open a position and click **Approve** to move it from Planned to Approved (or **Reject**, with a reason). Positions awaiting approval also appear on the **Manager Approvals** dashboard (Home → Manager Approvals) beside leave and timesheets, each showing how many of the department's planned seats are already taken; approving there is the same as approving in the app. 2. Click **Create Job Posting** to create a draft Job Board posting from the position. The button is hidden until Job Board is turned on for your business. 3. From there the position follows the hire: **In Progress** when the first applicant arrives, **Filled** when the accepted candidate becomes an employee. For a hire made outside Job Board, click **Start Hiring** and then **Mark Filled** and select the employee. ### Using the Headcount Grid Go to **Planning → Headcount Grid**. The grid is a live spreadsheet-style view of employees and planned positions across departments, showing current headcount alongside planned positions, positions in hiring, and filled positions. ### Reviewing analytics Go to the **Analytics** tab → **Analytics Dashboard**. The dashboard shows planned vs. actual hires, budget utilization, hiring velocity, time-to-fill, and cost-per-hire trends over time. A daily snapshot job records monthly analytics so AI forecasting has real hiring history to draw from. **Standard Reports** provides pre-built reports. If **Executive Reporting** is turned on, managers can also access the **Executive Reports** section for C-level summary reports. ### Exporting data Plans, budgets, the headcount grid, and positions can be exported. When **Require identity verification before exporting salary & budget data** is on — the default for tenants set up after 8 September 2026 — users must re-verify their identity (step-up) before the export streams. ### Mobile access Managers can view the dashboard, active plans, upcoming deadlines, and approve or reject positions (with a reason) from mobile. Phone browsers are automatically redirected to the mobile view; tablets stay on the desktop view. Use `?desktop=1` to opt out of the redirect. ## 5. Settings All settings live in the app's **Admin** tab. Each switch is a tenant-wide gate — it applies to all users regardless of role. | Setting | Where | Default | What it changes | |---|---|---|---| | Enable Headcount Agent | Admin → AI Configuration | Off | Lets managers and HR ask the Headcount Agent about plans, budgets and positions in Ask AI, and request a new position (they confirm first) | | AI Forecasting | Admin → General Settings | Off | AI demand forecasts, scenario recommendations, budget optimization suggestions, skills-gap analysis, the AI Models library, and the AI Strategic Insights card on the dashboard | | Market Intelligence | Admin → General Settings | Off | Shows the Market Intelligence page: the salary benchmark library your team enters or imports, and AI market analysis for a role or region | | Executive Reporting | Admin → General Settings | Off | Shows the Executive Summary on the Analytics dashboard and the Executive Reports pages | | Send deadline alerts and approval reminders | Admin → General Settings | On | The daily check that tells a plan's owner about overdue or due-soon milestones, over-budget departments and off-track plans, and reminds approvers once a week about positions still waiting for their decision. The first request to decide a position, and decisions on positions and plans, are always sent | | Require identity verification before exporting salary & budget data | Admin → General Settings | On for tenants set up after 8 September 2026; Off for earlier tenants | Adds a step-up verification prompt before plan, budget, grid and position exports | | Permissions (five "Who can…?" controls) | Admin → General Settings | Everyone with access, except rebalancing and salary benchmarks (app admins) | Who may create and edit plans, publish a budget, approve or reject positions, rebalance a scenario's budgets, and edit salary benchmarks | | OKR Hub Integration | Admin → Integration Settings | Off | Shows the OKR Hub page and its nav item (OKR Hub must be turned on too). No goals are read from OKR Hub yet, so the page is empty | | Recruiting Apps Integration | Admin → Integration Settings | Off | Shows the Recruiting Apps page and its nav item, with your plans' open positions. No candidate pipeline is read yet. Create Job Posting, Start Hiring and Mark Filled work whether it is on or off | | EPMS Integration | Admin → Integration Settings | Off | Shows the Performance skills page and the Skills Analysis nav item (Performance Management must be turned on too). No skills data is read yet, so those screens show a dash or an empty list, not a measured figure | ## 6. More help - **Headcount Planner FAQ** — specific setup, operating, and troubleshooting questions - Ask AI — the Headcount Agent answers plain-language questions about plans, budgets, and positions awaiting a decision when enabled **Keywords:** headcount planner, workforce planning, hiring budget, headcount forecast, headcount plan, position allocation, requisition, scenario planning, hiring plan, headcount-planner, headcount_planner --- # Headcount Planner FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Headcount Planner — for the admin running it. # Headcount Planner FAQ Answers to common setup and operating questions about Headcount Planner. For what the app is and how to set it up from scratch, see the [Headcount Planner Overview](/help/articles/headcount_planner_app_overview). --- ## Setup ## Do I have to turn on features before they appear? Yes, for the optional ones, and each starts off. **AI Forecasting**, **Market Intelligence** and **Executive Reporting** are switches under **Admin › General Settings**; the **OKR Hub Integration**, **Recruiting Apps Integration** and **EPMS Integration** switches are under **Admin › Integration Settings** (the OKR Hub and EPMS pages also need that app turned on for your business); and **Enable Headcount Agent** is under **Admin › AI Configuration**. Each switch hides its own pages and navigation items while off — the AI & Intelligence tab does not appear until AI Forecasting or Market Intelligence is on. Two switches on General Settings start **on**: **Send deadline alerts and approval reminders**, and **Require identity verification before exporting salary & budget data** (on for tenants set up after 8 September 2026; earlier tenants keep it off until an admin turns it on). ## Who can access Headcount Planner and what can each role do? Because the app exposes salary bands and compensation budgets, it is restricted to **Manager, Admin, Super Admin, or a designated app admin**. Regular employees cannot access it. Within that group, managers can create and manage plans, scenarios, budgets, and positions, but only in departments they manage. Admins and app admins can manage records across all departments and can also access the Admin tab for app-wide settings and AI model configuration. Admins can narrow who may create and edit plans, publish a budget, approve or reject positions, rebalance a scenario and edit salary benchmarks under **Admin › General Settings › Permissions**. ## Do I need Job Board enabled for the recruiting handoff? Yes. **Create Job Posting** on an approved position creates a Job Board posting directly, so Job Board must be turned on for your business. Until then, the position can still be approved and tracked inside Headcount Planner, but **Create Job Posting** is hidden until Job Board is turned on; an admin sees a link to turn it on in its place. --- ## Permissions and access ## Can managers edit positions outside their own department? No. A manager can only create, edit, approve, reject, or delete positions in departments they manage — where they are the named department manager, or their own department. Admins and app admins can modify positions in any department. Plans are keyed to the department itself, so renaming a department in People keeps its plan and its manager's access. ## Why don't I see the AI & Intelligence tab? The tab appears only when at least one AI-related toggle is enabled and produces a visible action for your role. Go to **Admin › General Settings** and enable **AI Forecasting**, **Market Intelligence**, or both. If the toggles are on but the tab is still missing, confirm that you have Manager or above access. --- ## Day-to-day ## How does a plan go from draft to active? A plan must be **validated** before it can be activated. **Validate** marks the plan as reviewed — it records who validated it and when, and does not check the plan's figures — and then **Activate** makes it live. Activating a plan archives any other active plan. ## What happens to other active plans when I activate a new one? They are archived. Activating a plan archives any other active plan: each one becomes read-only, its undecided position requests leave approvers' queues, and its owner is told (unless they activated the new plan themselves). Archiving cannot be undone. ## How do I close or archive a plan? Open the plan and choose **Actions → Archive plan**. The plan becomes read-only: positions on it can no longer be added, edited or decided, and its undecided position requests leave approvers' queues. Job Board postings already created from it are not touched, and its owner is told if someone else archived it. Archiving cannot be undone. ## How do I create a Job Board posting from an approved position? Open the position and click **Create Job Posting**. The position must be **Approved**, must not already have a posting, and must be on a plan that is not completed or archived. A draft Job Board posting is created with the title, salary range, employment type, skills and hiring manager carried over; a Job Board admin or the posting's recruiter publishes it. After the posting is created the position advances on its own — see the next question. ## Does hiring status sync back from Job Board automatically? Yes. A position with a Job Board posting follows it: it moves to **In Progress** when the first applicant arrives, and to **Filled** — recording the employee and the date — the moment the accepted candidate becomes an employee in People. Those steps show in the position's timeline as performed by *System*. **Start Hiring** and **Mark Filled** remain for hires made outside Job Board, and for a posting that was closed without a hire the position stays open for you to cancel or reuse. ## I edited an approved position and it went back to "Planned" — why? Title, seniority, employment type, salary range, total compensation budget, signing bonus and equity are what an approver signs off on. Changing any of them on an approved position withdraws the approval: the position returns to **Planned**, the original approver is told what changed, and the hiring manager, reporting manager and requester are told it is awaiting approval again. Dates, description, skills, location and the manager pickers can be changed without this. The edit form warns you before you save, and the timeline records an *Approval withdrawn* entry naming the fields. ## Why can't I change a position's title or pay any more? Once a position has a Job Board posting — or is filled, rejected or cancelled — what the approver signed off is fixed: its title, seniority, employment type, salary range, total compensation budget, signing bonus and equity can no longer change. To hire for different terms, duplicate the position and send the copy for approval. ## How do I withdraw a position request? Open the position and click **Withdraw request**. It is offered while the position is still awaiting approval, to the person who asked for it and to anyone who manages positions in that department. The position is cancelled and leaves approvers' queues. ## My position was rejected — what now? The position page shows who declined it, when and why. If you can add positions in that department, click **Ask again (as a new request)** to send a copy of it for approval; you can change the copy until it is decided. The declined position itself stays as it is, as a record of the decision. ## Where else can I approve positions? On the **Manager Approvals** dashboard (Home → Manager Approvals), under **Headcount Requests**, beside leave, timesheets and job offers. Each row shows the role, salary range, justification and how many of the department's planned seats are already taken — including when a request is above the approved plan. Approving or rejecting there runs the same rules and notifications as approving inside the app. A reason is required to reject — there, on the position page and on the phone. ## How are department budgets calculated? The total budget for a department entry is: **(planned headcount × budget per position) + (recruiting cost per hire × planned headcount) + (onboarding cost per hire × planned headcount)**. Recruiting and onboarding costs are optional. Totals roll up from budgets to the scenario and from the selected scenario to the plan. ## How do I compare scenarios side by side? Open the plan and navigate to its scenarios. The plan detail page shows a radar chart comparing all scenarios on budget, timeline, risk level, confidence, and ROI. Each plan can hold up to six scenario types — Conservative, Optimistic, Aggressive, Baseline, Cost Optimization, and Market Expansion — and you can mark one as the selected scenario. ## How do I load sample data to explore the app? Open **Admin › Data Management** and use the **Load Sample Data** card. Sample records are tagged, and **Remove Sample Data** deletes them without touching records your people made. Ready-made plans by industry are separate: open **Planning › Sample Plans**, open one and click **Convert to Plan** to create a draft plan of your own from it. --- ## When something looks wrong ## Why can't I delete this plan? A plan can only be deleted when it is in **Draft** or **Archived** status. Archive an active or completed plan first (**Actions → Archive plan**), then delete it. A plan with a Job Board posting raised from one of its positions cannot be deleted while that posting exists: delete a draft posting in Job Board first; a published posting can only be closed, so that plan stays archived. ## I approved a position but it still shows "Planned" — what happened? Check whether you may decide on it. To approve, you must be allowed by **Who can approve or reject a planned position?** and **Who can create and edit workforce plans?** (**Admin › General Settings › Permissions**), and manage or work in the position's department unless you are an admin or app admin. Positions on a completed or archived plan cannot be decided at all. Also check the position's timeline: if someone changed its title, seniority, employment type or compensation after approval, the approval was withdrawn and the entry says who changed what. ## Why am I not getting notifications about overdue milestones? The daily notification sweep sends alerts for overdue and upcoming milestones (due within 14 days), over-budget departments, and at-risk plans. Check four things: (1) Headcount Planner must be enabled for your business; (2) you must be the milestone's owner or the plan's creator; (3) your notification preferences for the **Headcount Planner** category must allow in-app or email delivery; (4) **Send deadline alerts and approval reminders** must be on in **Admin › General Settings** (it starts on). Overdue-milestone alerts repeat at most once per week and stop after 90 days past due. ## I exported salary data and was asked to verify my identity — is that expected? Yes, if **Require identity verification before exporting salary & budget data** is on in **Admin › General Settings** — it is on by default for tenants set up after 8 September 2026. This step-up verification applies to plan, budget, grid and position exports. Every export is also logged in the sensitive-data audit trail. --- ## Licensing and limits ## Does Headcount Planner require a licence? Yes. The app requires a licence and is disabled by default. An administrator enables it per tenant from Admin → Apps → All Apps. ## What is the planning horizon for a single plan? Each plan covers one fiscal year. For multi-year planning, create separate annual or quarterly plans and compare them in the analytics dashboard. Quarterly plans require a quarter number (1–4). ## Are there limits I should know about? - **Plan name:** 255 characters. - **Estimated time to fill:** 1–364 days per department budget entry (default is 30 days). - **Revenue growth assumption:** between –100% and 500% per scenario. - **Budget constraint factor:** between 0 and 5 per scenario. - **AI difficulty score:** 0–100 per position. - **Over-budget threshold:** a department budget is flagged when allocated spend exceeds the plan by more than 5%. - **Position urgency:** a position is flagged urgent when its requisition target date is within 14 days. - **Market intelligence CSV import:** maximum 10 MB per file, .csv format only. - **Activating a plan** archives any other active plan. - **Grid export size:** up to 20,000 employees per export; a larger roster is refused with a prompt to filter by department or status first, rather than truncated. - **Approval-material fields:** title, seniority, employment type, salary range, total compensation budget, signing bonus and equity — changing any of them on an approved position withdraws the approval. --- ## More help - [Headcount Planner Overview](/help/articles/headcount_planner_app_overview) - Ask AI — the assistant answers Headcount Planner questions from these articles. **Keywords:** faq, headcount planner, workforce planning, forecast, plan, scenario, budget, position, requisition, job posting, approval, archive, withdraw, hiring status, market intelligence, headcount-planner, headcount_planner --- # HR Files App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run HR Files — storing employee documents, controlling who sees them, managing approvals, tracking retention, and keeping an audit trail. # HR Files ## 1. What it is HR Files is your secure document vault for employee records, contracts, compliance documents, and any other file that belongs in an HR file cabinet. You upload files, assign them to employees, choose who can see them, and the app tracks every view, download, and change in an audit log. - **Enablement:** Requires a license. An admin enables it from **Admin → Apps → All Apps**. It is not turned on automatically. - **What it is not:** HR Files stores and governs documents. It does not create them — offer letters come from Recruiting, signed forms from E-Signature, submitted forms from Forms, and so on. Those apps can sync their output into HR Files automatically (see *Document sync* in §3), but the authoring happens there. ## 2. Standing it up 1. **Enable the app** — go to **Admin → Apps → All Apps**, find **HR Files**, and enable it. 2. **Choose which file categories and types to offer** — go to **HR Files → Settings → File Organization**. By default four categories are enabled (Employee Records, Candidate Documents, Contracts, Policies) and all 13 file types are available. Disable any your organization does not use so they do not appear in upload forms. 3. **Decide on the approval workflow** — under **Settings → Workflow Settings**, the **Approval Workflow** toggle is on by default. When it is on, files that are sensitive — flagged **Sensitive**, matching a type on the **File Types Requiring Approval** list, or marked as a compliance document — enter a pending-approval queue. Until an approver signs off, only the uploader, admins, HR Files app admins, the approvers Settings names, the assigned employee, and anyone with an explicit access grant can see the file. Turn this off if your organization does not need a review gate. 4. **Grant access** — any user with the app enabled can upload and view files scoped to them. The **Admin** tab appears only for business admins and HR Files app admins. The **Approvals** and **Requests** tabs appear for them too, and for anyone Settings names under **Who can approve or reject a file?** and **Who can request a document from an employee?**. The **Compliance** and **Audit Log** tabs appear for managers and above, and for anyone with direct reports. 5. **Confirm it worked** — upload a test file from **HR Files → Files → Upload**. You should see it in the file list, and the dashboard tiles should update. **Silent dependency:** If you enable the approval workflow but leave the default sensitive file types unchanged, every Background Check, ID Document, Tax Document, and Performance Review will sit in the Approvals queue until an approver acts. Approvers are notified of each new file (and, while **Daily Approval Digest** is on, sent a daily digest of what is still waiting), but make sure someone is watching the queue. ## 3. How it fits together ### Audience — who can see a file Every file has a single **Who can see this?** setting (the audience). This is the most important concept in the app — it governs visibility everywhere: the file list, search, the mobile app, and the AI agent. | Audience | Who can see the file | |---|---| | **Just HR & admins** | Business admins, HR Files app admins, and the uploader — not the employee the file is about | | **HR + the employee** | Plus the assigned employee | | **HR + employee + reporting chain** | Plus everyone above the employee in their reporting chain | | **HR + specific roles** | Plus active members whose business role matches the roles you pick (and the employee, if one is assigned) | | **All active employees** | Every active member of the business | The uploader, business admins, and HR Files app admins always have access regardless of audience. Explicit access grants (added from the file's Access Control page) also override the audience. The upload form opens on **Just HR & admins** and switches to **HR + the employee** when you choose an employee, until you pick an audience yourself. **Restricted file types** override the audience. File types on **File types limited to HR & the employee** (Medical, Garnishment, and Disciplinary by default) are always treated as **HR + the employee** — narrower if the uploader picked a wider audience, and still open to the employee if they picked **Just HR & admins**; with no employee assigned, **Just HR & admins**. This prevents a manager from seeing a direct report's medical record through the reporting chain. Beyond HR, the uploader, the employee and — while the file awaits approval — its approvers, only an explicit access grant opens a restricted file, and the employee is told when one is given. ### Approval workflow When the approval workflow is enabled, sensitive files enter a **Pending** state. While pending — and if rejected — the file's audience beyond the assigned employee is suspended: reporting-chain managers, role matches, and all-employees access are blocked until an approver approves. The uploader, admins, HR Files app admins, the employee, and explicit grants keep access throughout; the approvers Settings names see it only while it waits for them. A file is considered sensitive when any of these are true: it is flagged **Sensitive**, the file's type is on the admin's **File Types Requiring Approval** list, or the file is marked as a compliance document. Two things send a file back to the approvers automatically: editing an approved sensitive file (any change, whether it already was sensitive or the edit made it so), and replacing the document of a rejected file. ### The Sensitive flag The uploader can tick **Sensitive** on any file; a type on **File Types Requiring Approval** sets it automatically, and so does the AI review when it finds personal data. The flag holds the file for approval while the workflow is on, keeps an **All active employees** file out of the Former Employee Portal, asks for identity re-verification before a download or preview when **Identity Verification for Sensitive Downloads** is on, and keeps the file's contents away from AI suggestions while **Never send sensitive or restricted file types to AI** is on. It does not narrow who can see the file once it is approved — the audience and the restricted file types do that. ### Document sync Other apps can push their completed documents into HR Files automatically. You configure which sources are active under **HR Files → Admin → Sync Settings**. Seven source apps are available: Recruiting, Onboarding Hub, Forms, E-Signature, Employee Data, Employee Profile, and Policy Hub. Each source has its own trigger rules (e.g., Recruiting syncs when a candidate is hired; E-Signature syncs when signing is completed; Policy Hub files the signature receipt when an employee signs a policy). Synced files are auto-approved and do not enter the approval queue, and only admins and HR Files app admins can edit or delete them. Sync can be paused globally or per source. ### Retention policies Each file can carry a named retention policy (1 Year, 3 Years, 5 Years, 7 Years, 10 Years, or Permanent). The retention clock starts from the file's document date (or upload date if none is set). When the retention period lapses, a daily check asks admins to review the file — archive it, extend its retention, or delete it. If **Automatically archive files past retention** is on, the check archives those files instead and tells admins, who can restore any of them. Nothing is ever deleted automatically. Files on hold — compliance documents, and files under a legal hold placed in **Admin → Compliance** on the file or its employee — are exempt from the retention review entirely. ### E-Signature integration Files marked **Requires signature** can be sent to their assigned employee for signing through the E-Signature app, with **Send for signature** on the file's page. Only PDF files are eligible, the employee needs an email address, and the E-Signature app must be enabled for the business; when one of these is missing, a note in place of the button says which. A dedicated signature page is appended to the document, and the employee receives the request. When signing completes, the file is automatically marked as signed. ## 4. Running it ### Uploading files 1. Go to **HR Files → Files** and click **Upload**. 2. Choose a file, assign an employee (optional — leave blank for company-wide documents), select a category and type, and set the audience. 3. A live **Visibility Preview** shows exactly who will be able to see the file with the settings you picked. 4. Click **Upload**. If the approval workflow is on and the file is sensitive, it enters the Approvals queue. After upload, AI reads the document and suggests a file type, category, and expiry date. These appear as pending suggestions on the file page — you review and apply or dismiss them. AI also auto-flags files that contain PII or sensitive content (it only ever promotes the flag, never removes it). **Bulk upload:** Admins can upload up to 50 files at once from **Admin → Bulk Upload**. All files in a batch share the same category, type, audience, and sensitivity setting. ### Approving files 1. Go to **HR Files → Approvals** to see the pending queue, oldest first. 2. Open a file to review it, or use the checkboxes for bulk approve/reject. 3. Approving makes the file's full audience take effect. Rejecting needs a reason, which the uploader is told. To correct a rejected file, replace its document from **Edit** — that sends it back to the approvers. Business admins and HR Files app admins can approve or reject, and so can anyone Settings names under **Who can approve or reject a file?**. A named approver cannot approve or reject a file they uploaded themselves, or replaced with a new version — another approver has to. Admins can decide their own uploads, so a company with a single admin is never left waiting. ### Requesting documents from employees 1. Go to **HR Files → Requests** and click **Request a document**. 2. Choose an employee, a file type, and optionally a due date and note. 3. The employee is notified. When they (or anyone) uploads a new file of that type for that employee — on the web, on the phone, or in a bulk upload — the request is automatically fulfilled and the requester is told. A document that arrives through sync (for example a signed form from E-Signature) does not fulfil a request; once it is there, cancel the request. One open request per employee per file type. You can send reminders (deduped to once per day) or cancel the request; while **Document Request Reminders** is on, overdue requests — and requests with no due date that are a week old — are also reminded automatically once a week. ### Reviewing compliance Go to **HR Files → Compliance** (managers and above, and anyone with direct reports). This page shows: - **Expiring documents** — files whose expiry date is within the next 30 days. - **Compliance documents** — files marked as compliance/legal-hold documents. - **Document Coverage** — a roster of every employee with their file count. When the minimum-documents rule is enabled, employees below the threshold or missing a required document type are flagged. From the coverage roster, anyone who can open this page can download an employee's files as a zip (**Download Employee Packet**) — managers for the people on their roster, admins for anyone. The packet holds only the files the person downloading it is allowed to download. ### Reviewing the audit log Go to **HR Files → Audit Log** (managers and above). Every file view, download, upload, edit, approval, access grant, and export is recorded with the user, timestamp, IP address, and file version at the time. Admins see the full business-wide log (defaulting to the last 30 days). Managers see only the audit trail for files they can view. The log can be exported as CSV, JSON, or PDF. Per-file logs are reached from the file detail page. ## 5. Settings All settings are under **HR Files → Settings**. | Setting | Default | What it changes | |---|---|---| | **Enable AI Agent** | On | Lets users ask about their documents through Ask AI. | | **AI metadata suggestions on upload** | On | After each upload, AI suggests file type, category, and expiry and flags PII. Suggestions must be reviewed — never applied silently. | | **Enabled File Categories** | Employee Records, Candidate Documents, Contracts, Policies | Which categories appear in upload/edit forms. | | **Enabled File Types** | All 13 types | Which file types appear in upload/edit forms. | | **File types limited to HR & the employee** | Medical, Garnishment, Disciplinary | File types always treated as **HR + the employee** (or **Just HR & admins** with no employee assigned), regardless of the uploader's choice. | | **Approval Workflow** | On | Holds sensitive files for an approver before the reporting chain, specific roles, or all active employees can see them. | | **Identity Verification for Sensitive Downloads** | Off | Requires users to re-verify their identity before downloading or previewing a file flagged Sensitive or of a restricted type. Verification lasts 15 minutes. | | **Expiry Reminders** | On | Reminds the uploader, and the employee when they can see the file, before it expires (HR Files admins when neither can be told; nobody for a file about someone who has left) — 30 and 7 days ahead by default; choose the days under **Remind this many days ahead** — and marks overdue files as expired. | | **Flag employees below a document minimum** | Off | Surfaces employees with fewer than the minimum number of HR files on the Compliance page. | | **Minimum documents** | 3 | The threshold for the rule above. | | **Required document types** | None | Each employee must have at least one file of every checked type — a count alone can pass three resumes while the ID document is missing. | | **Archive HR files when an employee is deactivated** | Off | Archives a deactivated employee's active files. Compliance documents stay active. Files are retained, not deleted. | | **Notify admins when files pass their retention period** | On | A daily check queues expired-retention files for admin review. Files on legal hold are exempt. | | **Automatically archive files past retention** | Off | Moves retention-expired files to Archived and notifies admins to confirm or restore. | | **Retention policy durations** | 1 Year, 3 Years, 5 Years, 7 Years, 10 Years | How long each named policy keeps a file. Adjust to match your jurisdiction. Permanent never expires. | Three platform security settings are always on and cannot be disabled: Secure Cloud Storage, File Encryption (at rest), and Comprehensive Audit Logging. ## 6. More help - **HR Files FAQ** — specific setup and operating questions. - Ask AI — the assistant answers questions about HR Files from these articles. **Keywords:** hr files, employee documents, document management, file manager, personnel files, document approval, compliance documents, audit log, retention policy, document request, file upload, sensitive documents, background check, tax document, id document, e-signature, document sync, hr-file-manager, hr_file_manager, hr-files --- # HR Files FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about HR Files — for the admin running it. # HR Files FAQ Answers to common setup and operating questions about HR Files. For what the app is and how to set it up from scratch, see the [HR Files Overview](/help/articles/hr_file_manager_app_overview). --- ## Setup ## What do I need to configure before HR Files is ready to use? Enable the app from Admin → Apps → All Apps (it requires a licence and is disabled by default). Once enabled, open **Settings** inside the app. The two things most admins configure first are the **approval workflow** (on by default — sensitive files wait in the Approvals queue until an approver decides) and **auto-sync** (which connected apps automatically file documents into HR Files). Both work with sensible defaults, so the app is usable immediately after enabling it. ## Who can see and manage files once the app is enabled? Everyone in the business sees the **Home** and **Files** tabs. What files they see depends on each file's audience setting. **Business admins and HR Files app admins** see every file, whatever its audience, and get the **Admin** tab: Settings, Bulk Upload, Sync Settings, and Document Consolidation. The **Approvals** and **Requests** tabs appear for them too, and for anyone in the groups Settings names under **Who can approve or reject a file?** and **Who can request a document from an employee?**. **Managers and above** — and anyone with direct reports — also see the Compliance view and the Audit Log, scoped to files they can access. Any user can upload a file for themselves; a manager can also upload for someone who reports to them. --- ## Permissions and access ## How does the audience setting control who sees a file? Every file has exactly one **Who can see this file?** setting (the audience): 1. **Just HR & admins** — business admins, HR Files app admins, and the person who uploaded it. Not the employee the file is about. 2. **HR + the employee** — plus the employee the file is assigned to. 3. **HR + employee + reporting chain** — plus everyone above that employee in their reporting chain. 4. **HR + specific roles** — plus active members whose role in the business is one you tick on the file (and the employee, if one is assigned). 5. **All active employees** — every active member of the business. The upload form opens on **Just HR & admins**; choosing an employee switches it to **HR + the employee** until you pick an audience yourself. Admins and HR Files app admins can choose any of the five; everyone else chooses from the first three. On top of the audience, you can add per-person access grants for finer control. ## What do restricted file types do? Some file types are too personal for the audience setting alone. Files of a type on **Settings → File types limited to HR & the employee** (default: **Medical**, **Garnishment**, and **Disciplinary**) are always treated as **HR + the employee**, whatever audience the uploader chose — narrower if they picked a wider audience, and still open to the employee if they picked **Just HR & admins**. A restricted file with no employee assigned is **Just HR & admins**. The uploader, admins, HR Files app admins, and anyone with an explicit access grant can still see the file; the employee is told when someone is granted access to it. ## What does marking a file Sensitive do? A file is flagged **Sensitive** when the uploader ticks it, when its type is on **File Types Requiring Approval** (the flag is set automatically), or when the AI review finds personal data in it. The flag: 1. **Holds the file for approval** while the approval workflow is on — see below. 2. **Keeps an All active employees file out of the Former Employee Portal.** 3. **Asks for identity re-verification** before a download or preview, when **Identity Verification for Sensitive Downloads** is on (restricted file types ask too). 4. **Keeps the file's contents away from AI suggestions**, while **Never send sensitive or restricted file types to AI** is on (the default). It does not narrow who can see the file once it is approved — use the audience, or a restricted file type, for that. ## How do per-person access grants work? From a file's **Access Control** page, admins and HR Files app admins — and anyone in the groups Settings names under **Who can grant a person access to a file?** — can give one person access with one of four permission levels: | Level | View | Download | Edit, replace, archive | Delete | |---|---|---|---|---| | **Read Only** | Yes | No | No | No | | **Read & Download** | Yes | Yes | No | No | | **Full Access** | Yes | Yes | Yes | No | | **Admin Access** | Yes | Yes | Yes | Yes | Editing and deleting rights from a grant do not apply to a file synced from another app — only admins and HR Files app admins manage those. Each grant is **Permanent** (until revoked), **Temporary**, or **Emergency**; Temporary and Emergency grants need an end date and stop working on their own when it passes. You can suspend, restore, or revoke any grant at any time; the person is notified of the grant and of each change (when they can open HR Files), and every change is audit-logged. --- ## Day-to-day ## How does the approval workflow decide which files need approval? When the approval workflow is enabled (it is by default), a file enters the pending-approval queue if it is **sensitive**. A file counts as sensitive when any of these is true: (1) it is flagged **Sensitive**, (2) its type is on **File Types Requiring Approval** (default: **Background Check**, **ID Document**, **Tax Document**, **Performance Review**), or (3) it is marked as a compliance document. Files that are not sensitive are approved on upload, and files synced from other apps are always approved on arrival. Business admins and HR Files app admins approve or reject files, as does anyone in the groups Settings names under **Who can approve or reject a file?**. A named approver cannot decide a file they uploaded themselves, replaced with a new version, or that is about them — another approver has to; admins can decide these too, so a company with one admin is never stuck. Rejecting always needs a reason, which the uploader is told. While a file is pending, only the uploader, admins, HR Files app admins, the approvers, the assigned employee, and anyone with an explicit access grant can see it; if it is rejected, the same people except the approvers named in Settings. The reporting chain, specific roles and all active employees see it only once it is approved. A file can come back to the queue later: - **Editing an approved sensitive file** — any change, whether the file already was sensitive or the edit made it so — sends it back for approval. - **Replacing the document of a rejected file** sends it back to the approvers, so the corrected version gets a fresh decision. ## Can I request a specific document from an employee? Yes. From the **Requests** tab, an admin, an HR Files app admin, or anyone in the groups Settings names under **Who can request a document from an employee?** can ask a specific employee for a specific document type (e.g. "please upload your tax document by Friday"). The employee is notified and sees the open request at the top of their HR Files page. When anyone uploads a new file of the matching type for that employee — on the web, on the phone, or in a bulk upload — the oldest open request is fulfilled and the requester is told. A document that arrives through sync (for example a signed form from E-Signature) does not fulfil a request; once it is there, cancel the request from the Requests tab. Only one open request per employee and document type is allowed at a time. ## Can I send a document out for signature from HR Files? Yes. On a file marked **Requires signature**, the people who can manage the file see **Send for signature**, which sends it to the employee through the E-Signature app. It needs the E-Signature app enabled, a PDF, and an assigned employee with an email address — when one is missing, a note in place of the button says which. When the employee completes signing, the file is automatically marked as signed with the date and signer recorded. If the initial send fails, you can send it again from the same button. ## Which apps auto-sync documents into HR Files? Seven sources can be enabled in **Sync Settings**: 1. **Recruiting** — resumes, cover letters, offer letters, background checks (on hire). 2. **Onboarding Hub** — all document types (on signed or verified). 3. **Forms** — HR, onboarding, compliance, and tax form submissions (on submission). 4. **E-Signature** — completed signed documents in employment, HR, compliance, and onboarding categories. 5. **Employee Data** — approved employee data documents. 6. **Employee Profile** — all profile documents (on creation). 7. **Policy Hub** — the signature receipt when an employee signs a policy. Each source has its own rules for which document types and events trigger a sync. When a previously-synced document is updated at the source, a new version is created on the existing HR file rather than a duplicate. You can pause all syncing globally or disable individual sources. ## What happens when an employee is offboarded? By default, nothing changes — the employee's files stay active and accessible to anyone who could already see them. If you turn on **Archive HR files when an employee is deactivated** in Settings (off by default), deactivating an employee automatically archives their active, non-compliance files. Compliance documents are never archived by this setting — they stay active. Archived files can always be restored. --- ## When something looks wrong ## "I uploaded a file but my employees can't see it" The most common causes, in order: 1. **The file is pending approval, or was rejected.** If the approval workflow is on and the file is sensitive, the reporting chain, specific roles and all active employees are blocked until an approver approves it. Check the file's approval status on its detail page. 2. **The audience is too narrow.** A file set to **Just HR & admins** is hidden even from the employee it is about, and **HR + the employee** is hidden from everyone else. Change the audience or add an explicit access grant. 3. **The file type is restricted.** File types on **File types limited to HR & the employee** (default: Medical, Garnishment, Disciplinary) are treated as **HR + the employee** regardless of the audience setting. 4. **The file is not assigned to an employee.** Company-wide files (no employee selected) are only visible through the audience setting — an employee-specific view won't show them. ## "I can't delete this file" Two kinds of hold block deletion: 1. **A compliance document.** A file marked as a compliance document cannot be deleted. Remove the compliance flag first if retention is no longer required. 2. **A legal hold.** A legal hold placed in **Admin → Compliance** on the file, or on the employee it is about, blocks deletion until the hold is lifted. A file that has already been deleted cannot be deleted again. If you are told you can't delete it at all, you are not one of the people who can: admins, HR Files app admins, someone with an Admin Access grant, and the uploader — but only until someone else approves the file. After that, archive it instead or ask an HR Files admin. ## What is the difference between archiving and deleting a file? **Archive** (open to anyone who can edit the file) takes an active file out of the working set: it stops expiry reminders and leaves the retention review, but stays visible to everyone it is shared with, and **Restore** brings it back. **Delete** removes the file from HR Files for everyone; there is no restore for a deleted file anywhere in HR Files, and the delete is recorded in the audit log, with the reason if one was given. Archive when you might need the file again; delete only when it should be gone. ## "The document coverage roster says an employee is missing documents" The Compliance view flags employees in two ways when the minimum-documents rule is enabled: (1) their total file count is below the configured minimum (default **3**, adjustable from 1 to 20 in Settings), or (2) they are missing one of the **required document types** you configured. An employee can have three files and still be flagged if one of the required types is absent. Only non-deleted files count. --- ## Licensing and limits ## Does HR Files require a licence? Yes. HR Files requires a licence and is disabled by default. An administrator enables it for the business from Admin → Apps → All Apps. ## What are the file size and upload limits? | Limit | Value | |---|---| | Maximum file size (non-video) | 100 MB | | Maximum file size (video) | 500 MB | | Bulk upload — files per batch | 50 | | Bulk upload — per-file size cap | 50 MB | | Employee file-packet zip | 200 files / 500 MB total | | File name length | 255 characters | Accepted formats: PDF, DOC, DOCX, XLS, XLSX, CSV, TXT, JPG, JPEG, PNG, GIF, MP4, MOV, AVI, WEBM, MPEG. ## How long are download and preview links valid? Download links are valid for **1 hour**. Preview links are valid for **5 minutes**. Both are signed links created each time you click Download or Preview, so a copied link stops working when it expires. ## What retention policies are available and how do they work? Each file can be assigned a retention policy: **1 year**, **3 years**, **5 years**, **7 years**, **10 years**, or **Permanent**. The retention clock starts from the file's document date (or the upload date if no document date is set). Admins can customise the duration for each named policy in Settings (from 1 to 100 years). When a file's retention period passes, a daily check asks admins to review it — archive it, extend its retention, or delete it. **Automatically archive files past retention** is off by default; turned on, the check archives those files and tells admins, who can restore any of them. Nothing is ever deleted automatically. Files on hold — compliance documents, and files under a legal hold placed in Admin → Compliance on the file or its employee — are exempt from the retention review. --- ## More help - [HR Files Overview](/help/articles/hr_file_manager_app_overview) - Ask AI — the assistant answers HR Files questions from these articles. **Keywords:** faq, hr files, document management, audience, sensitive flag, restricted file types, approval workflow, access grant, retention policy, compliance, auto-sync, document request, bulk upload, file size limit, download link, hr-file-manager, hr_file_manager, hr-files --- # Ideas App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run the Ideas app — lifecycle stages, campaigns, RICE scoring, review panels, and workspace settings. # Ideas ## 1. What it is Ideas is a structured suggestion box. Employees submit ideas, everyone upvotes, and a reviewer panel prioritizes them with RICE scoring and moves them through a configurable lifecycle pipeline. - **Enablement:** Ideas requires a license and is disabled by default. A Super Admin or Admin enables it from Admin → Apps → All Apps. - **What it is not:** Ideas does not manage project tasks or track work after an idea is approved. Once an idea reaches an Implemented or similar stage, hand it off to a project-management tool or workspace. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Ideas**. The app appears in the sidebar for all members once enabled. 2. Go to **Ideas → Settings → Idea Reviewers** and choose a reviewer group. Until you save a group, ideas route to the built-in **All Admins** group. The reviewer group controls who can score ideas and move them through lifecycle stages — membership is the only grant, with no admin bypass. 3. Confirm the default lifecycle stages work for your organization. Ideas ships with five stages: **New → Reviewing → Planned → Implemented → Deferred**. You can rename, recolor, reorder, add, or remove stages under **Settings → Lifecycle Stages**. Changes apply immediately. 4. Optionally restrict who can submit ideas. By default everyone can submit. Under **Settings → Idea Submitters**, pick a specific group to limit submissions. 5. Optionally, enable **Campaigns** (on by default) and configure who can create them under **Settings → Campaigns**. 6. To verify, have a test user open **Ideas** from the sidebar. They should see the Dashboard with an empty state and a prompt to post the first idea. **Silent-until-configured pairing:** if the reviewer group you select has no members, ideas can be submitted and voted on, but nobody can score them or move them through stages. The Settings page warns you when the group is empty. When an idea is submitted with an empty panel, the system sends admins a nudge notification saying the panel needs to be configured — rather than silently notifying no one. **Mobile:** the Ideas Dashboard and idea detail pages have mobile-optimized views at `/m/apps/ideas`. Phone-class browsers are redirected automatically; tablets stay on the desktop view. Opt out of the redirect for a session by adding `?desktop=1` to the URL. **Sample data:** under **Settings → Sample Data**, admins can load sample ideas and campaigns to explore the app before real submissions arrive. It's safe to run again — sample records already in the workspace are left alone, not duplicated. Use the **Remove Sample Data** button to take all of it back; it never touches your real records. ## 3. How it fits together **Lifecycle stages** — the pipeline every idea travels through. Each stage has a name, a color, and a category. The category determines what the stage means to the analytics engine: - **Entry** — where new ideas land (exactly one stage must be Entry; the default is "New"). - **Active** — work-in-progress stages (e.g. "Reviewing", "Planned"). - **Implemented** — the idea shipped. The author receives a celebration notification. - **Declined** — the idea was set aside. The system remembers which Active stage it came from. You can have between 2 and 10 stages. Renaming a stage does not break the funnel numbers — analytics key off the category, not the name. For example, renaming "Planned" to "In Progress" changes the label everywhere without losing history. A worked example: an employee submits "Weekend shift-swap board". It lands in **New** (Entry). A reviewer scores it (Reach 500, Impact 3, Confidence 80%, Effort 2 → RICE score 600, medium priority) and moves it to **Reviewing** (Active). After discussion, the reviewer moves it to **Planned** (Active) with a note ("approved for Q3"), which posts as a comment visible to everyone. When the feature ships, they move it to **Implemented**. The author receives a celebration notification, and the Dashboard shows the idea in the Implemented column. If the reviewer instead moves the idea to **Deferred** (Declined), the system records which Active stage it came from, so the lifecycle card shows where the idea fell out of the pipeline. **RICE scoring** — reviewers prioritize ideas with four inputs: **Reach** (how many people it affects), **Impact** (how much it matters), **Confidence** (how sure you are, expressed as a 0–1 factor where blank defaults to 100%), and **Effort** (how much work it takes). The formula is Reach × Impact × Confidence ÷ Effort. A score of 700 or above shows as high priority (green pill); 300–699 is medium (amber); below 300 is low. Scoring is optional and can be turned off workspace-wide in Settings. **Review panels** — a reviewer panel is an ordinary recipient group (managed in **Admin → Groups**). Panel membership is the only way to gain review authority; being an admin is not enough on its own. Each campaign can route its ideas to a different panel, or inherit the workspace default. Out of the box only Ideas admins choose a campaign's panel; **Settings → Permissions → Who can choose a campaign's review panel?** can widen that. **Campaigns** — optional, time-boxed drives that group ideas around a theme (e.g. "Summer cost-saving ideas"). Each campaign has a title, a brief, optional start and close dates, and can route ideas to its own reviewer panel. A campaign's phase is derived from its dates: future start date → **Scheduled**; past close date or manually closed → **Closed**; otherwise **Open**. A background sweep closes a campaign automatically once its close date has ended in the workspace's time zone. **Voting** — upvote-only. Each person can vote once per idea (enforced by a unique constraint). The author's own vote is cast automatically on submission, so every idea starts at 1. Admins can choose the upvote icon and whether removing an upvote is allowed. **Duplicate detection** — when an employee submits an idea, the system checks the title against existing ideas. If similar titles are found, the submitter sees a nudge with up to three matches and can vote on an existing idea instead of posting a duplicate. The detection also runs as the title is typed. **Threaded comments** — every idea has a discussion thread. Comments support @mentions (which trigger notifications) and threaded replies. Comments are visible to all members; the audit log (stage moves, score changes, edits) is visible only to reviewers. **Audit log** — every stage move, RICE score change, and idea edit is recorded with the actor, timestamp, and before/after values. Reviewers see the full trail on the idea's detail page. The Analytics dashboard uses the audit trail to compute average time an idea spends in each stage before moving on. **Engagement integrations** — submitting an idea earns XP in Levels & Badges (if that app is enabled) and creates a signal in Mango Signal. These fire automatically and do not require any configuration. Bulk-imported ideas skip both signals to avoid flooding. ## 4. Running it ### Reviewing and scoring ideas 1. Open **Ideas → My Review Queue** (visible only to members of a review panel). 2. The queue is a prioritized table ranked by RICE score (by votes when scoring is switched off). Use the **awaiting score** chip to filter to ideas still waiting for a review panel score — an idea a reviewer already moved to an Implemented or Declined stage is not waiting. An idea scored or decided only by its own author still is: its row says "Scored by its author" or "Moved by its author", and a colleague on the panel settles it by confirming the score (**Confirm score**) or the stage (**Confirm** on the current stage) on the idea's page. Switch to the **Matrix** tab for a visual Impact × Effort scatter view of scored ideas. 3. Click an idea to open its detail page. Fill in the RICE inputs in the scoring panel — Reach, Impact, and Effort are all required for a score to compute; Confidence is optional and defaults to 100%. Click **Save Score**. 4. Move the idea to the next stage using the stage picker. Add an optional note — it posts as a comment visible to everyone in the discussion and is recorded in the audit log. ### Managing campaigns 1. Go to **Ideas → Campaigns** and click **New Campaign** (available to the people **Settings → Campaigns → Who can create campaigns** allows — everyone by default). 2. Enter a title (required) and brief (required). Set optional start and close dates and pick an icon and color. An Ideas admin (or anyone **Who can choose a campaign's review panel?** allows) can also choose the campaign's reviewer panel; everyone else's campaigns use the **Default campaign reviewers** setting. 3. When submitting an idea, employees can attach it to any open campaign via the campaign picker on the submission form. 4. The campaign's creator or any Ideas admin can close, reopen, or delete the campaign. Deleting a campaign keeps its ideas — they are detached, not deleted, and remain in the Ideas feed. 5. Reopening a campaign that has a past close date clears that date so it does not immediately close again. ### Importing ideas from a spreadsheet 1. Go to **Ideas → Settings → Import & Export** and click **Import ideas**. 2. Upload a CSV, XLSX, or XLS file (max 10 MB, max 2,000 rows). Download the import template first to see the expected columns. 3. The import runs in the background. Duplicate titles are skipped automatically. Imported ideas start with zero votes — historical vote counts from the file are not carried over. ### Exporting and analytics - **Export all ideas (CSV)** is available from the Settings page and from the Ideas feed to the people **Settings → Permissions → Who can export the ideas CSV?** allows (Ideas admins by default). The export from the feed reflects the current feed filters and sort order. - **Analytics** (at **Ideas → Analytics**, for the people **Settings → Permissions → Who can see Ideas analytics?** allows — Ideas admins by default) shows total ideas, votes cast, participation rate, implementation rate, a stage funnel with average time in each stage, a 6-month submission trend, campaign performance, and the top 15 contributors. The entire dashboard can be exported to CSV. ### Editing lifecycle stages 1. Go to **Ideas → Settings → Lifecycle Stages**. 2. Click a stage (its name, color dot or pencil) to open its **Name**, **Color** and **Category** fields, change what you need, and click **Save**. The category sets the stage's role (Entry, Active, Implemented, Declined). 3. Drag the handle or use the arrow buttons to reorder stages. Add a new stage with the **+ Add stage** button. 4. Each stage shows how many ideas stand on it. To delete a stage, its ideas must first be moved to another stage — by a review-panel member, since stage moves are a reviewer action and admins get no bypass. The Entry stage cannot be deleted — to change which stage is Entry, promote a different one. Changes in this editor apply immediately without clicking Save. ## 5. Settings All settings are at **Ideas → Settings**. Changes under the Lifecycle Stages editor apply immediately; everything else applies when you click **Save settings**. | Setting | Section | Default | What it changes | |---|---|---|---| | Enable Ideas AI Agent | Ideas AI Agent | On | Lets people look up, submit, vote, comment, score, and move ideas from the Ask AI sidebar. | | Who can submit ideas | Idea Submitters | All Employees | Restricts idea submission to a specific group. | | Reviewer group | Idea Reviewers | All Admins (built-in fallback) | The group whose members can score ideas and move them through stages. | | Enable idea scoring (RICE) | Idea Reviewers | On | Turns RICE scoring on or off workspace-wide. When off, the score column, matrix, and score sort are hidden. | | Show reviewer names | Idea Reviewers | On | When off, reviewer avatars and names are hidden — only the panel's group name is shown. | | Upvote icon | Voting | Caret | The icon on the vote button. Choices: Caret, Chevron, Arrow, Circle, Thumbs up. | | Allow removing an upvote | Voting | On | When off, an upvote is final once given. | | Allow ideas to have a voting close date | Voting | Off | When on, submitters can set a date after which voting locks. | | Accent color | Display | Blue | Tints buttons, icons, and highlights across the app. Choices: Blue, Forest, Purple, Sunset. | | Default feed layout | Display | Grid | The layout people see first. Choices: Grid, List, Board. Anyone can switch, and their choice is remembered. | | Feed density | Display | Comfortable | Compact fits more ideas on screen. Choices: Comfortable, Compact. | | Allow file attachments | Submissions | On | Lets submitters attach files (images, PDFs, Office documents, plain text; max 25 MB per file). | | AI writing assistance | Submissions | On | Helps employees draft idea and campaign descriptions with AI. | | Enable idea campaigns | Campaigns | On | Adds the Campaigns section and the campaign picker when posting an idea. Turning campaigns off hides them; ideas already in a campaign stay with that campaign's review panel. | | Who can create campaigns | Campaigns | All Employees | Restricts campaign creation to a specific group. | | Default campaign reviewers | Campaigns | Same as the Idea Reviewers group | The panel a new campaign's ideas go to. Out of the box only Ideas admins can pick a different panel on a campaign — everyone else's campaigns use this one. | | Notify authors when their idea changes stage | Notifications | On | Email, in-app and push notification to the author on every stage move, including the reviewer's note. | | Notify reviewers when an idea is routed to their panel | Notifications | On | Email, in-app and push notification to panel members when a new idea arrives. Turning it off does not stop the review summary (at most every 3 days per reviewer) of ideas waiting more than 3 days for a review panel score. | | Notify authors of replies | Notifications | On | Email, in-app and push notification when someone comments on the author's idea. | | Notify people who are @mentioned | Notifications | On | Email, in-app and push notification when a person is tagged in an idea's discussion. | | Who can choose a campaign's review panel? | Permissions | App admins only | Who else can point a campaign at its own review panel. The chosen panel reviews and moves every idea in that campaign. | | Who can see Ideas analytics? | Permissions | App admins only | Who else can open Analytics and its CSV. Choices: App admins only, specific groups, everyone. | | Who can export the ideas CSV? | Permissions | App admins only | Who else can export ideas, with each author's name and email. Choices: App admins only, specific groups. | ## 6. More help - **Ideas FAQ** — specific setup and operating questions, limits, and troubleshooting. - Ask AI — the assistant answers questions about Ideas from these articles. **Keywords:** ideas, idea management, suggestion box, innovation, campaigns, RICE scoring, upvote, lifecycle stages, review panel, idea submission, voting --- # Ideas FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Ideas — for the admin running it. # Ideas FAQ Answers to common setup and operating questions about Ideas. For what the app is and how to set it up from scratch, see the [Ideas Overview](/help/articles/ideas_app_overview). --- ## Setup ## Do I need to configure anything before employees can start using Ideas? No. Once Ideas is enabled, the app seeds five default lifecycle stages (New, Reviewing, Planned, Implemented, Deferred) and sets the "All Admins" group as the default reviewer panel. Employees can submit, vote, and comment immediately. You can customize stages, reviewer panels, and other settings later from **Settings** without interrupting anything already in progress. ## Who can submit ideas and who can vote? By default every employee can submit ideas, vote, and comment. You can restrict submission to a specific group in **Settings > Who can submit ideas**. Campaign creation has its own audience gate in **Settings > Who can create campaigns**. Voting and commenting are always open to all employees. Admins and reviewers are not exempt from the audience gate — if you restrict submission to a group, an admin outside that group cannot submit either. ## How do I set up a reviewer panel? Go to **Settings > Idea Reviewers** and pick a group under **Reviewer group**. Every idea routes to this panel unless its campaign has a panel of its own (out of the box only Ideas admins choose a campaign's panel — see **Settings > Permissions > Who can choose a campaign's review panel?**). If no group is chosen, the "All Admins" group is used as a fallback. A reviewer is anyone who belongs to the assigned panel — there is no separate "reviewer" role, and admins do not get review access automatically. --- ## Permissions and access ## Why can't someone see the My Review Queue tab? The tab only appears for users who belong to at least one reviewer panel — either the workspace default panel or a campaign's dedicated panel. Being an admin is not enough; panel membership is the only grant. Add the user to the relevant group and the tab appears on their next page load. ## Who can access Analytics and Settings? **Settings** (including the lifecycle editor and Import) is for Ideas admins: App Admins of Ideas, Admins, and Super Admins. **Analytics** and the **ideas CSV export** go to Ideas admins by default, and you can open them to more people under **Settings > Permissions**: **Who can see Ideas analytics?** (specific groups, or everyone) and **Who can export the ideas CSV?** (specific groups). Ideas admins can always see both. Each section is hidden from the sidebar and route-guarded for everyone it doesn't include. --- ## Day-to-day ## How does RICE scoring work? Reviewers score ideas using the RICE model: **Reach x Impact x Confidence / Effort**. Reach is a whole number, Impact and Effort accept up to two decimal places, and Confidence is a 0–1 factor (0.5 means 50%, 0.8 means 80%). A blank Confidence counts as 1.0. The minimum Effort used in the calculation is 0.25, so the formula never divides by zero. All three of Reach, Impact, and Effort must be filled in for a RICE score to compute — leaving any of them blank saves the inputs but produces no score. The score pill on each idea shows green (700+), amber (300–699), or grey (below 300). RICE scoring can be turned off entirely in **Settings > Enable idea scoring (RICE)**. ## Can I customize the lifecycle stages an idea moves through? Yes. Go to **Settings** and scroll to the lifecycle editor. You can rename, reorder, and recolor stages, and assign each one a category: **Entry**, **Active**, **Implemented**, or **Declined**. There must always be exactly one Entry stage (it receives new submissions), and you must keep at least 2 stages. The maximum is 10. Renaming a stage does not break existing reporting — metrics key off the category, not the label. A stage that still has ideas assigned to it cannot be deleted: the editor shows how many ideas each stage holds, and those ideas have to be moved to another stage first — by a review-panel member, since moving ideas between stages is a reviewer action and admins get no bypass. ## How do idea campaigns work? A campaign is an optional, time-boxed drive that groups ideas around a theme. It has a title, a brief, optional start and close dates, and an optional dedicated reviewer panel. Its phase is derived from those dates: a future start date means **Scheduled**, a past close date means **Closed**, and everything else is **Open**. Employees can only submit ideas to an open campaign. Campaigns whose close date has passed are automatically closed by a background sweep. An admin or the campaign's creator can also close or reopen a campaign manually. Deleting a campaign keeps its ideas — they are detached, not removed. Campaigns as a feature can be turned off entirely in **Settings > Enable idea campaigns**. ## What notifications does Ideas send, and can I turn them off? Four events have their own switch in **Settings > Notifications**: **stage change** (to the author, including the reviewer's note), **panel routed** (to reviewers when a new idea arrives on their panel), **reply** (to the author), and **@mention** (to the person mentioned). Each arrives as an email (for people with an email address), an in-app notification (the bell) and a phone push; turning a switch off stops all of them for that event. When an idea lands on a stage with the Implemented category, the author gets a special "Your idea was implemented!" notification. A few notices have no switch in Settings: - a **review summary** to each review panel's members — campaign panels included — when ideas have waited more than 3 days for a review panel score, at most every 3 days per person (bell and push, while RICE scoring is on); - a notice to a campaign's creator when the **campaign closes** (bell only); - a notice to an author when an Ideas admin **removes their idea** (bell only); - an alert to admins when a new idea's **review panel has nobody in it**. Each person can mute Ideas notifications in their own notification preferences. ## How do I import ideas from a spreadsheet? Go to **Settings > Import ideas**. Upload a CSV, XLSX, or XLS file (10 MB maximum, 2,000 rows maximum). A downloadable template is available on the same page. Only **Title** and **Description** are required; optional columns include author email, stage, campaign, submission date, voting close date, and RICE scores. Rows whose title already exists in the workspace are skipped, so an accidental re-import does not duplicate. Only one import can run at a time per workspace. Imported ideas start with zero votes and send no notifications when they're imported — though, while RICE scoring is on, an imported idea with no score whose submitted date is between 3 and 30 days ago still appears in its review panel's summary. ## Can I export ideas or analytics to a CSV? Yes, both. On the **Ideas** feed, the people allowed to export (Ideas admins by default — **Settings > Permissions > Who can export the ideas CSV?**) see an **Export CSV** option that exports the current filtered and sorted list — whatever filters and sort you have applied carry into the file. On the **Analytics** page, **Export analytics (CSV)** downloads the full analytics dashboard: summary KPIs, stage funnel, time-in-stage, monthly trend, campaign performance (with each campaign's status), and top contributors. ## What happens when I reset settings to defaults? **Settings > Reset to defaults** restores every Ideas setting to its shipped default: anyone can submit ideas and create campaigns again, the review panel goes back to the built-in **All Admins** group, and the three permissions (choosing a campaign's review panel, seeing analytics, exporting the ideas CSV) go back to Ideas admins only. It also restores the five default lifecycle stages (New, Reviewing, Planned, Implemented, Deferred), matching stages by kind (category) rather than by name or position: a stage that is kept keeps its ideas and gets its default name and colour back, and ideas on a stage that is removed move to the default stage of the same kind — an implemented idea stays Implemented, a declined one stays Deferred. Each moved idea's Audit Log records the move. This is not reversible — custom stage names, colours and extra stages are gone after a reset. --- ## When something looks wrong ## I can't vote on this idea — why not? Two possible causes. First, the idea may have a voting close date that has already passed — voting stays open through the close date and locks when that day ends (midnight in your workspace's time zone), and from then on votes can be neither added nor removed. Close dates lock anything only while **Allow ideas to have a voting close date** is turned on in Settings. Second, you may have already voted: each person gets one vote per idea, enforced at the database level. If the **Allow removing an upvote** setting is turned off, your vote is final once cast. ## I submitted an idea but nobody has reviewed it The most common cause is an empty reviewer panel. When no one belongs to the assigned panel, Ideas sends a fallback notification to admins saying "No one can review this idea — its panel is empty." Check **Settings > Idea Reviewers > Reviewer group** and make sure the group has members. If the idea belongs to a campaign with its own panel, check that campaign's panel too. Remember that admins do not automatically get review access — they must be in the panel to score or move ideas. ## My attachment was rejected — what happened? Attachments must be under 25 MB each and must be a supported file type: images, PDF, Word documents (.doc/.docx), Excel files (.xls/.xlsx), PowerPoint (.ppt/.pptx), or plain text. The type is verified from the file's actual contents, not the file extension. If **Allow file attachments** is turned off in Settings, the attachment field does not appear at all. ## I posted an idea and it shows "similar ideas already exist" — what is that? Ideas checks your title against existing ideas when you submit. If it finds matches (based on shared keywords), it shows up to 3 similar ideas and offers a vote on any of them that can still take one from you, or you can post yours anyway. A match that is already Implemented or Declined, one whose voting has closed, or one you have already upvoted is shown for you to look at, without a vote button. This is a nudge, not a block — you can always post. --- ## Licensing and limits ## Does Ideas require a licence? Yes. Ideas is a licensed add-on, disabled by default. An admin enables it from Admin → Apps → All Apps. There is no automatic rollout to any workspace. ## What are the limits I should know about? | Item | Limit | |---|---| | Idea title | 200 characters | | Campaign title | 120 characters | | Stage label | 60 characters | | Lifecycle stages per workspace | 2 to 10 | | Attachment size | 25 MB per file | | Import file size | 10 MB | | Import rows per file | 2,000 | | Votes per person per idea | 1 | | Discussion depth | One level of replies | | Duplicate-detection matches shown | 3 | | Analytics reporting range | All-time | | Submission trend window | Last 6 months | | Top contributors shown | 15 | --- ## More help - [Ideas Overview](/help/articles/ideas_app_overview) - Ask AI — the assistant answers Ideas questions from these articles. **Keywords:** faq, ideas, RICE scoring, upvote, lifecycle stages, campaigns, review panel, import, voting, not showing, permissions, reviewer --- # Importing Data (Smart Import) **Category:** System-features **Section:** Advanced Features **Updated:** 2026-08-12 How to bring data into the platform from CSV files and spreadsheets using Smart Import — setup, column mapping, recurring imports, and historical migrations. # Importing Data (Smart Import) ## 1. What it is Smart Import is the platform's unified way to bring data in from CSV files or spreadsheet copy-paste. It covers users, departments, holidays, job families, job titles, and records in apps that register as import targets — over 20 data types through one consistent flow. AI suggests how your file's columns map to the platform's fields; you review, adjust, and commit. - **Enablement:** Smart Import is built into the platform — there is no app to license or enable. Business admins can import any platform target; delegated app administrators can import the targets their app registers (for example, a Company Store app administrator can import store items without being a business admin). - **What it is not:** Smart Import does not sync data continuously from an external system. For live synchronization with an HRIS, payroll provider, or identity provider, use the platform's Integrations. Smart Import also does not handle file attachments — it imports structured data (fields, values, references) from CSV or tab-separated text. ## 2. Standing it up Smart Import requires no separate configuration before first use — no app to enable, no API key to set up. Once you have data to bring in: 1. Go to **Admin → Bring Your Data** (`/admin/data-migration`). This page lists every data type you can import, grouped by app. Platform targets (Users, Departments, Holidays, Job Families, Job Titles) are always visible to business admins. 2. Click **Import** next to the data type you need. Each opens its own import page. 3. Upload a CSV file or paste rows copied from a spreadsheet. The platform reads both comma-separated and tab-separated formats automatically. Pasted data works directly from an Excel or Google Sheets copy — select a range including the header row, copy, and paste into the text area. 4. Review the AI-suggested column mapping on Step 2. Re-point, skip, or accept each column. For rows that already exist, choose **Skip them (add new only)** or **Update them**. 5. Click **Commit import** to write the records. **What to know before your first import:** - Files up to 25,000 rows are accepted. Files with 200 rows or fewer import inline; larger files run in the background and you are redirected to a progress page. You can leave and come back — the page polls automatically. - Downloading the **Template** CSV for a target gives you a file whose column headers auto-map perfectly on re-upload — no review edits needed. - An app-scoped target (for example, Store Items for Company Store) only appears in the catalog if that app is enabled for your tenant. - The maximum upload size is 10 MB for both files and pasted data. The accepted file types are CSV, TSV, and plain text. ## 3. How it fits together **Targets** — A target is a data type the platform knows how to import. Each target defines its fields, which columns are required, how duplicates are detected (by an identifier column such as name or email), and how references to other records are resolved. The catalog at **Admin → Bring Your Data** lists every target you have permission to import, grouped into **Platform** and per-app sections. Platform-level targets available to every business admin include Users, Departments, Job Families, Job Titles, Holidays, and Knowledge Base entries. The Users target is lightweight — it creates accounts without sending invitations, and it operates in headers-only mode, meaning the AI mapping sees column headers but never cell values, as an additional PII safeguard. App-level targets appear when their app is enabled — examples include Accounts and Contacts (Mango GTM / Mango CS), Tasks, Workspace Tasks, Store Items (Company Store), Contracts, OKR Objectives and Key Results, Vendors, Candidates (Job Board), Skills and Certifications, Assets, Deals, Purchase Orders, Training Courses, Billing Profiles, and RFP Answers and Engagements. Some targets depend on another — the catalog page notes these dependencies. For example, Key Results reference their parent Objective by title — import Objectives first. Job Titles reference Job Families, and Contacts reference their Account by name or domain. **Column mapping** — When you upload a file, the platform runs a two-stage suggestion: 1. **Heuristic matching** compares your column headers against known field names and aliases. An exact header-to-field match maps automatically with no AI involved. 2. **AI refinement** handles ambiguous or renamed columns. It reads the headers and a few sample values, then proposes destinations and value transforms (such as converting currency strings to numbers, or mapping status synonyms). Columns whose headers match sensitive patterns (SSN, salary, bank, password, and similar) never have their cell values sent to the AI — only the header is used. You always review and confirm the mapping before anything is written. The AI only proposes; deterministic code applies the confirmed plan. **Reference resolution** — When a column points to a related record (for example, a contact's account or a key result's parent objective), the platform resolves the reference through a pipeline: exact match first, then fuzzy matching (prefix, suffix, and name similarity), then embedding-based semantic matching, and finally AI adjudication for remaining ambiguous cases. Unresolved references are reported as problem rows, not silently dropped. **Saved mappings** — After a successful import, the platform remembers the confirmed mapping for that combination of target and column set. The next time a file with the same columns is uploaded, the saved mapping is reused instantly — no AI call, no review edits. The banner on Step 2 tells you when a saved mapping is being applied. **Import modes** — Two modes govern how the import handles rows that already exist (matched by the target's identifier field — typically name, email, or a similar unique value): - **Skip them (add new only)** — only new rows are created; existing records are untouched. - **Update them** — existing records are updated with the values from the file; new rows are still created. Some targets use a composite identifier (for example, RFP engagements are keyed on both title and due date) so that event-shaped data with repeated titles does not collapse into a single record. **Historical import** — Some targets support a historical-import mode for migrating past activity. When available, a **These are historical records** checkbox appears on the review step. Checking it imports the records as already completed, preserves their original dates, and suppresses notifications so a migration of 500 closed contracts does not generate 500 notifications. The import history page tags these runs with a **Historical** badge and names who enabled the mode. Use historical import when migrating closed contracts, completed OKR cycles, or resolved RFP engagements — not for current work. **Provenance** — Every record created by Smart Import carries a permanent provenance marker noting the source file, the import date, and whether it was a historical import. This appears as an **Imported** badge on the record's detail page. Provenance is never overwritten — it records the original import, even if the record is later updated by a subsequent import. **Permissions** — Who can import what depends on the target. Platform-level targets (Users, Departments, Holidays, Job Families, Job Titles, Knowledge Base) require a business admin. App-scoped targets also admit delegated app administrators — an admin of the Company Store app can import store items without being a business admin. Creating new custom fields during import always requires admin-level access. Import history is visible to business admins for all runs, or to app administrators for the targets they administer. ## 4. Running it ### Importing from a file or spreadsheet 1. Go to the import page for your target (either from **Admin → Bring Your Data** or from the in-app import button where available). 2. Choose **Upload a file** or **Paste data**. Pasted data works with rows copied directly from Excel or Google Sheets — include the header row. 3. Click **Map columns**. The platform parses the file, suggests mappings, and shows a data preview of the first few rows alongside each column's suggested destination. 4. On Step 2, review each column's **Import as** destination. The mapping table shows your CSV column name, a sample value, and the suggested target field. You can re-point any column to a different field, mark it **Skip**, or — if you are an admin and the target supports custom fields — create a new custom field on the fly. If a saved mapping from a previous import of the same columns is being reused, a banner at the top of Step 2 tells you. 5. Choose the import mode for existing rows and click **Commit import**. 6. After the import, the **Last import results** panel shows how many records were created, updated, and skipped. Problem rows are listed with the row number, identifier, and the reason each was skipped. Rows imported with warnings (imported but worth reviewing) appear in a separate expandable section. Click **Download problem rows** to get a CSV of only the failures for correction and re-import. ### Exporting current data Each import page has an **Export current data** button that downloads every record of that type as a CSV file. The export uses the same column names as the importer, so the exported file re-imports cleanly with zero changes — useful for round-trip edits or backup before a bulk update. User fields export as the user's email (which resolves unambiguously on re-import), reference fields export the matched value (for example, the account name), and dates export in ISO-8601 format. ### Setting up a recurring import For data that arrives on a regular cadence from an external system (for example, a nightly CSV export from an HRIS), you can schedule a recurring import: 1. On the import page, expand the **Recurring import** section. 2. Enter the **CSV URL** where the file is hosted. 3. Choose the **Cadence** — **Daily** or **Weekly**. 4. Choose **Existing rows** — **Skip them** or **Update them**. 5. Click **Schedule**. The URL must be an https (or http) address reachable from the internet — internal or private-network addresses are blocked for security. The platform fetches the file on the chosen cadence. Column mappings are resolved from the saved mapping for those columns — if no saved mapping exists and the columns do not match the target's field names exactly, the run fails with a message asking you to run one interactive import first to confirm the mapping. Unattended imports never guess. Every recurring run appears in **Import history**. You can **Pause**, **Resume**, or **Remove** a schedule from the same section. ### Reviewing import history Go to **Admin → Bring Your Data** and click **Import history**. This page shows every Smart Import run in your tenant — background and recurring — with the target name, filename, status (Pending, Running, Completed, or Failed), row counts (created, updated, skipped), who ran it, and when. Historical imports are tagged with a **Historical** badge. Business admins see all runs; delegated app administrators see only the runs for the targets they administer. ### Accessing import from within an app Several apps host the Smart Import flow inside their own interface — for example, Tasks, Company Store, Mango CS, and Mango GTM each have an import action in their admin views. These in-app importers use the same engine, the same mapping logic, and the same saved-mapping memory as the generic import page. They appear in the **Bring Your Data** catalog with a link that opens directly in the app's chrome. Workspace Tasks are imported from within a specific workspace — the catalog row links you to the workspace picker, and you start the import from there. ## 5. Settings Smart Import has no standalone settings page. Its behavior is governed by the choices made at import time and the recurring-import configuration: | Setting | Where | Default | What it changes | |---|---|---|---| | Import mode | Step 2 of every import | **Skip them (add new only)** | Whether existing records are updated or left untouched | | Historical records | Step 2 (targets that support it) | **Off** (unchecked) | Imports records as completed, keeps original dates, suppresses notifications | | Create custom fields | Step 2 (admin only, targets with custom-field support) | **On** for admins | Whether unmapped columns create new custom fields on the target; non-admins see a note that those columns will be skipped | | Recurring import — CSV URL | Recurring import section on the import page | *(none — must be configured)* | The hosted file the platform fetches on the cadence | | Recurring import — Cadence | Recurring import section | **Daily** | **Daily** or **Weekly** fetch from the URL | | Recurring import — Existing rows | Recurring import section | **Skip them** | Whether recurring runs update existing records or only add new ones | The recurring-import schedule is checked hourly. A schedule whose last run (successful or not) is older than its cadence is due for the next fetch. A failing URL is not retried on every hourly sweep — it waits for the next cadence interval. Value transforms — such as converting currency strings to numbers, normalizing date formats, or mapping status synonyms — are proposed by the AI during column mapping and confirmed during review. The platform supports common transforms including currency-to-number, percent-to-number, date normalization, boolean parsing, and case conversion (title case, uppercase, lowercase). ## 6. More help - **Importing Data FAQ** — specific questions about file size limits, supported formats, column-mapping troubleshooting, and common import errors. - **Employee Data Administration** — for bulk user management beyond the Smart Import user target. - **Integrations — SSO, HRIS, Payroll, SFTP, Webhooks** — for continuous synchronization with external systems, as opposed to Smart Import's file-based approach. - Ask AI — the assistant answers questions about Smart Import from these articles. **Keywords:** import, CSV import, data import, Smart Import, bulk import, spreadsheet import, data migration, bring your data, import users, import departments, import template, column mapping, recurring import, historical import, export data, paste data --- # Inspections App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run Inspections — building templates, scheduling recurring checks, running facility sweeps, tracking corrective actions, and managing external visit logs. # Inspections ## 1. What it is Inspections lets your team conduct workplace inspections, safety audits, and quality checks from the field or the floor. Inspectors work through scored checklists or sweep a facility layout aisle by aisle, with photo evidence, GPS capture, and electronic signatures. Failed items can automatically create corrective actions, and completed inspections can route through a multi-stage approval workflow before they close. - **Enablement:** Inspections requires a license. An admin enables it from Admin → Apps → All Apps and configures it under **Apps → Inspections → Manage → Settings**. - **What it is not:** Inspections tracks your own team's internal checks and recurring audits. For recording visits by external surveyors, auditors, or agencies (and tracking their findings and plans of correction), turn on the **Visit Log** module inside the same app — it is off by default. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Inspections**, and enable it for your organization. 2. Go to **Apps → Inspections → Manage → Settings**. Review the **Modules** card — the app ships with four core modules on by default (Checklist Inspections, Facility Coverage Sweeps, Corrective Actions/Approvals/Reporting, and Regulatory Knowledge Base) plus the Visit Logs module off by default. 3. Go to **Manage → Templates** and create at least one inspection template. Choose a category (Safety, Quality, Compliance, Equipment, Food Safety, Environmental, or General), add checklist items, and set a pass threshold (default 80%). 4. Assign the template to your team by either: - Creating an **Inspection Cycle** (a time-bounded period such as monthly or quarterly) under **Team → Inspection Cycles**, or - Creating a **Schedule** (a recurring rule that auto-generates inspections) under **Manage → Schedules**, or - Letting inspectors start ad-hoc inspections from the template. 5. To confirm it works, ask an inspector to open **My Inspections** — they should see any scheduled or cycle-started inspections waiting for them. **Silent-until-paired:** A template by itself does not create any inspections. You must also create a cycle, a schedule, or start one manually before an inspector has work to do. ## 3. How it fits together **Templates** — A template is the reusable checklist (or rack-question set) every inspection is built from. Templates belong to a category and carry a pass threshold, optional weighted scoring, photo-evidence and signature requirements, training prerequisites, and an optional approval workflow. Templates are authored by admins; inspectors consume them. **Inspections** — An individual inspection is one completion of a template by one inspector. It moves through statuses: **Draft → Scheduled → In Progress → In Review → Completed** (or **Cancelled**). When submitted, the score is calculated from the weighted items the inspector answered. If the score meets or exceeds the template's pass threshold the inspection passes; if any item flagged as auto-fail is marked failed, the inspection fails regardless of score. When the template has an approval workflow attached, the inspection enters **In Review** before it can complete. **Cycles** — A cycle is a time-bounded inspection period (monthly, quarterly, annual, or custom dates). A cycle uses one of three generation modes: - **Notify only** — announces the period; each inspector starts their own inspection. - **Per item** — auto-creates one inspection per registered item (imported via CSV or from assets), assigned via a strategy (location manager, single assignee, round-robin, or claim pool). - **Coverage sweep** — seeds one facility sweep per selected layout (see below). Once active, a cycle's generation mode is locked. Cycles can close manually, on the end date, or when all linked work is completed. **Schedules** — A recurring rule (daily, weekly, monthly, quarterly, or annually) that auto-generates inspections for a location and template. An hourly job creates the next inspection when the schedule is due — at its Preferred Time on the location's clock, or at the start of the location's day — and it is due by the end of that day. Unlike a cycle, a schedule has no bounded period — it keeps generating until it is deactivated, or pauses while its template is inactive. **Facility Coverage Sweeps** — An aisle-by-aisle walkthrough of a facility layout (managed in AssetPro). Inspectors record only exceptions (failures), not passes. Coverage rolls up per aisle and per sweep. Sweeps run inside a coverage-sweep cycle and can route through an approval workflow before sign-off. **Corrective Actions (CAPA)** — A follow-up action created when an inspection item fails or a visit-log finding needs remediation. Each action has a priority (Low, Medium, High, Critical), an assignee, a due date, and a status (Pending → In Progress → Completed or Cancelled). When the setting **Auto-Create Corrective Actions** is on (the default), a corrective action is created automatically for every failed item. While that setting is on, every corrective action in the register — from failed items, visit-log findings or missed frontline work — is also added to its assignee's Tasks list. **Visit Log** (independent module, off by default) — An internal record that an external party visited one of your locations. Tracks the agency, surveyor names, visit type (Routine, Complaint, Follow-up, Licensure, Audit, or Other), attached report documents, individual deficiency findings with citation codes, and the plan-of-correction lifecycle. Access defaults to managers and admins; it can be widened to everyone with app access or narrowed to admins only. **Training integration** — Templates can require that the inspector has completed specific training courses before they may start an inspection. If an inspection fails, the template can auto-enroll the inspector in a remediation training course. ## 4. Running it ### Conducting an inspection 1. The inspector opens **My Inspections** and selects a scheduled or in-progress inspection (or starts a new one from a template or cycle). 2. They answer each checklist item. Supported item types include yes/no, checkbox, rating, text, number, slider, date/time, photo, signature, single-select, multi-select, find-asset, and instruction-only. 3. Items can require a photo before the inspector can proceed. GPS location is captured automatically if available. 4. On submission, the score is calculated and the inspection either passes or fails. If the template requires a signature, the inspector must sign before submission. 5. If the template has an approval workflow, the inspection moves to **In Review** and appears in the reviewer's **Approvals** queue. ### Reviewing and approving inspections 1. Reviewers open **Team → Approvals** to see inspections and sweeps pending their decision. 2. They can approve (the inspection completes) or reject (the inspection returns to the inspector for rework). 3. Approval workflows support up to 10 levels, optional escalation, and named approvers. ### Managing corrective actions 1. Open **Team → Corrective Actions** to see all open actions, or **My Actions** for personal assignments. 2. Update the status, add resolution notes, attach completion evidence photos, and mark as completed. 3. Completed actions can be verified for effectiveness (a separate verification step with notes). ### Running a facility coverage sweep 1. Create a cycle with generation mode **Coverage sweep** and select the facility layouts to sweep. 2. When the cycle activates, one sweep is seeded per layout, expanded into per-aisle units. 3. Inspectors open **My Inspections** to see their assigned sweeps, walk each aisle, and log exceptions only. 4. The **Coverage** dashboard shows real-time aisle-by-aisle completion and exception counts. ### Viewing compliance and analytics Managers and admins open **Analytics → Analytics** and **Analytics → Reports** for inspection pass rates, trends by location and category, inspector performance, and corrective-action aging. The **Compliance Dashboard** is reached from the Reports page. **Sweep Insights** and **Visit Insights** sit in the same Analytics group when those modules are on. ## 5. Settings Settings are at **Apps → Inspections → Manage → Settings**. ### Module toggles These are the switches in the **Modules** card. | Setting | Default | What it changes | |---|---|---| | Checklist Inspections | On | Ad-hoc and per-item inspections, recurring schedules, and Quick Scan. | | Facility Coverage Sweeps | On | Aisle-by-aisle rack sweeps, coverage dashboard, and exceptions ledger. Requires facility layouts in AssetPro. | | Corrective Actions, Approvals & Reporting | On | CAPA register, approval queues and workflows, compliance dashboards, analytics and reports. Requires at least one of the two execution modules above. | | Regulatory Knowledge Base | On | Curated regulatory reference content the AI assistant can cite. | | Visit Logs | Off | External visit tracking, findings, plans of correction, and trend analytics. Runs independently of the core modules. | At least one execution module or Visit Logs must remain on — the app prevents disabling all of them. ### Feature settings | Setting | Default | What it changes | |---|---|---| | Auto-Create Corrective Actions | On | Raises a corrective action for each failed inspection item, and adds every corrective action in the Inspections register to its assignee's Tasks list. | | Default Pass Threshold | 80% | The pass threshold a NEW template starts with. Each template keeps its own threshold, so changing this does not change existing templates. | | Default Due Date | 7 days | Default due-date offset (in days) for new corrective actions. | | Enable Scheduled Inspections | On | Recurring location- and asset-based inspection schedules (the Schedules menu entry and the generation jobs). | | Scheduled inspections assigned (Settings › Notifications) | On | Tells an inspector, in the app and by email, when a recurring schedule assigns them new inspections. Off keeps generating them silently; they still appear in My Inspections. Settings › Inspections shows this switch read-only and links to it. | | Enable Quick Scan | On | Barcode/QR-code shortcut for starting an inspection on an asset. Requires the AssetPro app. | | Allow Inspection Pickup | On | Members at an inspection's location can pick up a scheduled inspection assigned to someone else. | | Allow Deleting Inspections | Off | Lets inspectors and managers delete inspection records. Off by default to protect signed-off audit data. | | Allow Managing Per-Inspection Visibility | Off | Lets admins and managers grant extra viewers to an individual inspection on top of default visibility. | | Show Facility Layouts link | Off | Adds a Facility Layouts shortcut to the Manage menu. Requires the AssetPro app. | | Show AI Console in the sidebar | On | Shows the AI Console entry in the left navigation (business admins and Inspections app admins only). | | Enable Live Assist | Off | Remote video inspection via Live Assist. Requires the Live Assist app and a configured meeting provider. | ### Team scoping These are under **Settings → Access & Visibility**. | Setting | Default | What it changes | |---|---|---| | Default visibility | **Location** | Who can see an inspection by default — people at its location, people who share any of the inspector's departments (primary or additional), or **No scoping**. No scoping is the WIDEST setting: every user in the business can open every inspection in full, including answers, photos, GPS and signatures. | | Manager visibility | **Own locations** | **Own locations** shows a manager their assigned locations and every location beneath them (members see only the locations they are assigned to); **All locations** gives managers the same business-wide view as admins. | | Member visibility | **Default** | **Default** follows the default visibility above; **Own only** restricts regular members to inspections they personally conduct. | ### Visit Log settings | Setting | Default | What it changes | |---|---|---| | Visit Log tracking mode | **Detailed** | **Detailed** runs the full plan-of-correction lifecycle (status stepper, due dates, reminders). **Simple** files the survey and deficiencies as a record with no status workflow. | | Visit Log access | **Managers & admins** | Who can open the Visit Log — everyone with app access, managers and admins, or admins only. Not narrowed by location: everyone admitted sees every visit. | ### AI feature toggles These are the switches in the **AI Features** card. | Setting | Default | What it changes | |---|---|---| | Inspections AI Agent (Ask AI) | On | Lets people ask the Inspections agent about inspections, templates, corrective actions and regulatory guidance. | | AI-Generated Reports | On | AI-generated summaries for completed inspection reports. | | AI Template Generation | On | AI-assisted creation of inspection templates from a plain-language description. | | Document to Template Conversion | On | Convert PDFs or photos of paper checklists into digital templates using AI. | | Regulatory Q&A (AI assistant) | On | AI-powered regulatory question answering from the Knowledge Base. Shown when the Regulatory Knowledge Base module is on. | | Inspection Analytics (AI assistant) | On | AI assistant can analyze inspection data for patterns, trends, and failure rates. Shown when the Corrective Actions, Approvals & Reporting module is on. | | AI Reading of Agency Reports (Visit Log) | On | AI reads an uploaded surveyor or auditor report to pre-fill a visit and its cited deficiencies. Shown when Visit Logs is on. | ## 6. More help - **Inspections FAQ** — specific setup and operating questions, limits, and troubleshooting. - Ask AI — the assistant answers questions about Inspections from these articles. **Keywords:** inspections, inspection template, safety audit, quality check, facility sweep, corrective action, compliance dashboard, inspection cycle, inspection schedule, visit log, regulatory knowledge base, quick scan, checklist inspection, CAPA, pass threshold, approval workflow --- # Inspections FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup, access and day-to-day questions about Inspections — for the admin running it, the managers overseeing it and the inspectors using it. # Inspections FAQ Answers to common setup, access and day-to-day questions about Inspections. For what the app is and how to set it up from scratch, see the [Inspections Overview](/help/articles/inspections_app_overview). --- ## Setup ## What do I need to configure before anyone can run an inspection? You need at least one active inspection template. A template holds the checklist questions, scoring, pass threshold and category. Create or activate one under **Templates** in the Inspections sidebar. By default only admins and Inspections app admins can author templates. To widen that, open **Settings → Access & Visibility** and change **Who can create and manage inspection templates?** to managers or to a named group. Admins keep authoring rights whatever you choose. ## What are the modules and how do I choose which ones to turn on? Inspections is split into six modules you switch on or off in **Settings → Modules**: 1. **Inspection Templates** — always on; included with either execution module. 2. **Checklist Inspections** — ad-hoc and per-item inspections, recurring schedules and barcode Quick Scan. 3. **Facility Coverage Sweeps** — aisle-by-aisle rack sweeps, the coverage dashboard and the exceptions ledger. 4. **Corrective Actions, Approvals & Reporting** — the corrective action register, approval queues, compliance dashboards, analytics and reports. Needs Checklist Inspections or Facility Coverage Sweeps on. 5. **Regulatory Knowledge Base** — regulatory reference content the AI assistant can cite. 6. **Visit Logs** — external surveyor and auditor visits. Off by default. Keep at least one of Checklist Inspections, Facility Coverage Sweeps or Visit Logs on. Settings refuses to save a configuration with all three off. --- ## Permissions and access ## Who can create, edit, sign off and delete inspections? Anyone who can open the app can start and conduct their own inspections. The assigned inspector, managers and admins can edit, start or cancel an inspection. Recording answers and signing off are narrower. Only the assigned inspector, a business admin or an Inspections app admin can do either. Deleting is off by default. An admin must first turn on **Allow Deleting Inspections** under **Settings → Access & Visibility → Permissions**. Even then, only the assigned inspector or a manager or above can delete. ## How do I control which inspections my team members see? Three settings under **Settings → Access & Visibility** decide it: - **Default visibility** — **Location** (the default) shows inspections at the viewer's assigned locations. **Department** shows inspections by inspectors who share any of the viewer's departments, primary or additional. **No scoping** is the widest setting: every user in the business can open every inspection in full, including answers, photos, GPS and signatures. - **Manager visibility** — **Own locations** (the default) or **All locations**. All locations gives managers the same business-wide view as admins. - **Member visibility** — **Default** follows the default visibility above. **Own only** limits regular members to inspections they personally conduct. Managers and admins are not affected. To add viewers to a single inspection, turn on **Allow Managing Per-Inspection Visibility**. Managers and admins can then grant specific people, groups, departments, locations, roles or job titles. A department grant matches a person's primary or additional department. A location grant covers people at that location or any location beneath it. Grants only add access; they never hide an inspection. ## I manage a region — why do I see inspections at stores I'm not assigned to? A manager of a region sees every location beneath it in Inspections. This applies when **Manager visibility** is **Own locations** and the default visibility is **Location**. Your reach covers the Team Inspections list and its location filter, coverage sweeps, cycle items, Quick Scan's due schedules, the Exceptions ledger and the AI assistant. Regular members still see only the locations they are assigned to. When per-inspection visibility is on, an inspection's **Manage visibility** panel names this group with a chip such as "Managers above Store 12". Only active locations count. ## Who can open the Visit Log? The **Visit Log access** setting offers **Everyone**, **Managers & admins** (the default) or **Admins only**. Managers & admins covers managers, business admins and Inspections app admins. Admins only covers business admins and Inspections app admins. Access is not narrowed by location. Everyone admitted sees every visit at every location, including uploaded agency reports. --- ## Day-to-day ## How does scoring work, and what does auto-fail mean? Each question carries a weight, **1.0** by default. The score is the share of earned weight out of total weight, from **0 to 100**. Questions answered N/A, skipped, or hidden by a conditional rule do not count. An inspection passes when its score meets the template's **pass threshold**. The threshold defaults to **80%** and can be set from 0 to 100 per template. **Auto-fail** overrides the score. If a question marked **Auto-fail on No** gets a failing answer, the whole inspection fails, whatever the score. ## How are corrective actions created, and when are they due? A corrective action is a follow-up task to fix a failed item. With **Auto-Create Corrective Actions** on (the default), completing an inspection creates one for each failed item that does not already have one. The same switch also adds every corrective action in the Inspections register to its assignee's Tasks list; turning it off stops both for corrective actions raised from then on. Priority comes from the failure severity the inspector chose: **Critical**, **Severe → High**, **Moderate → Medium**, **Minor → Low**. With no severity, a critical question gets **Critical**; otherwise weight decides, with 5 or more **High**, 2 or more **Medium**, and below that **Low**. The due date follows priority: | Priority | Due | |---|---| | Critical | 1 day | | High | 3 days | | Medium | the **Default Due Date** setting (default **7 days**, allowed 1–90) | | Low | twice the Default Due Date | The action goes to the location's manager first. If the location has none, it goes to the group set in **Route failed-inspection alerts to this group**, then an Inspections app admin, then a business admin. ## Can I require a photo or a signature before an inspection can be submitted? Yes. Both are enforced on every submission path: desktop, mobile, the API and the AI assistant. - **Photo evidence** — flag a question **Requires photo** on the template. The inspection cannot be submitted until every flagged, visible item has a photo. Items answered N/A or skipped are exempt. - **Signature** — turn on **Require signature** on the template. The inspection cannot be submitted without the inspector's typed signature. ## How do inspection cycles work, and what are the assignment strategies? A cycle is a recurring inspection period: **Quarterly**, **Annual**, **Monthly** or **Custom**. Its generation mode decides what happens at activation: 1. **Notify only** (the default) — notifies the audience; each person starts their own inspection. 2. **Per item** — creates one inspection per cycle item, such as one per location or asset. 3. **Coverage sweep** — seeds a facility coverage sweep per selected layout, split into aisles. Per-item cycles assign work by **Location manager**, **Single assignee**, **Distributed** (round-robin across a pool) or **Claim pool** (people claim items). The generation mode locks once the cycle leaves Draft. A cycle closes **Manually** (the default), **On end date**, or **On all complete**. Admins create and activate cycles; managers can view cycle progress. ## How does the approval workflow work for submitted inspections? When an approval workflow applies, submitting moves the inspection to **In Review** and sends it to reviewers. Approving completes it. Rejecting returns it to **In Progress** on the same record for rework. A workflow applies when the template has one attached. Otherwise, the most recent enabled business-wide workflow with the trigger **Inspection submission** applies. With neither, the inspection completes as soon as it is submitted. ## Can I pick up an inspection that was assigned to someone else? Yes, in two cases. An **In Progress** inspection can be taken over by a manager or above, or by anyone assigned to the inspection's location. A **Scheduled** inspection can be picked up by the same people, but only while **Allow Inspection Pickup** is on (the default). The original assignee is recorded in the inspection's history. Turning pickup off keeps scheduled inspections with their assignee. Takeover of in-progress inspections stays available either way. ## What happens to an asset's condition when an inspection fails? When a failed inspection is linked to an asset, the asset's condition is downgraded, never upgraded. A score below **50%** sets it to **Poor**. A score from **50% to 69%** sets it to **Fair**. A score of **70% or above** leaves the condition alone, even on a fail caused by an auto-fail question. --- ## When something looks wrong ## "I set up a recurring schedule but no inspections are being created" Check these things: 1. The schedule is **Active**, not paused. 2. Today, at the location, falls between the schedule's start and end dates. 3. **Enable Scheduled Inspections** is on in Settings. 4. The **Checklist Inspections** module is on. 5. The schedule's template is **active**. A deactivated template generates nothing until you reactivate it; the schedule's badge reads "Paused — template inactive". 6. The template is not run by inspection cycles. A cycle-managed template's timing belongs to its cycle, so schedules on it are skipped; the badge reads "Paused — template runs in inspection cycles". The scheduler checks every hour. A schedule creates its inspection at its **Preferred Time** on the location's clock (or at the start of the location's day when no time is set), and the inspection is due by the end of that day. A schedule that already has a pending inspection for the location's today is skipped until its next date. ## "It says I need training before I can start this inspection" The template lists required training courses. You must finish every listed course before you can start an inspection from it. The message names the courses still missing. The check runs when you press **Start**. It does not block the inspection being created, assigned or picked up. ## "My inspection scored above the pass mark but still shows as Failed" An auto-fail question caused it. When a question marked **Auto-fail on No** gets a failing answer, the whole inspection fails regardless of score. The inspection's score card names the question that triggered it. ## "I'm a manager and I can open the inspection, but I can't record answers or complete it" That is by design. Answers and sign-off belong to the assigned inspector, a business admin or an Inspections app admin. This keeps the signature honest. To finish the work yourself, take the inspection over first. You then become the inspector and can answer and sign off. ## "I turned off a module but I can still see its data in some places" Turning a module off hides its navigation and blocks its pages, but it deletes no data. Dashboards and analytics can still show records created while it was on. To remove data, use **Clear all inspections data** under **Settings → Data Reset**. It needs **Allow Deleting Inspections** on. It deletes every inspection, their corrective actions and evidence, and all sweep progress for your business. Templates, cycles, schedules, visit logs and settings are kept. It is not per-module. --- ## Licensing and limits ## Does Inspections require a licence? Yes. Inspections requires a licence and is disabled by default. An administrator turns it on from Admin → Apps → All Apps. ## What are the limits and allowed ranges I should know about? | Setting | Range or limit | |---|---| | Inspection score | 0–100 | | Pass threshold | 0–100% per template (default **80%**) | | Corrective action Default Due Date | 1–90 days (default **7**) | | Corrective action priorities | Low, Medium, High, Critical | | Corrective action statuses | Pending, In Progress, Completed, Cancelled | | Template name | Up to 255 characters | | Question text | Up to 500 characters | | Question weight | 0 or above (default **1.0**) | | Template categories | Safety, Quality, Compliance, Equipment, Food Safety, Environmental, General | | Inspection statuses | Draft, Scheduled, In Progress, In Review, Completed, Cancelled | | Schedule frequencies | Daily, Weekly, Monthly, Quarterly, Annually | | Cycle types | Quarterly, Annual, Monthly, Custom | | Question types | Yes/No, Checkbox, Rating, Text, Number, Slider, Date/Time, Photo, Signature, Single-select, Multi-select, Find Asset, Instruction | | Visit Log access | Everyone, Managers & admins, Admins only | | Visit Log tracking modes | Detailed (full plan-of-correction lifecycle), Simple (record only) | | Asset condition downgrade | Below 50% → Poor; 50–69% → Fair; 70%+ → no change | | Deficiency trend alert | A citation code appearing 3 or more times in 12 months | --- ## More help - [Inspections Overview](/help/articles/inspections_app_overview) - Ask AI — the assistant answers Inspections questions from these articles. **Keywords:** faq, inspections, corrective actions, templates, scoring, pass threshold, auto-fail, inspection cycles, schedules, coverage sweeps, visit log, permissions, regional manager, locations beneath, default visibility, photo evidence, signature, approval workflow, pick up, take over, not showing, can't start --- # Integrations FAQ **Category:** Faq **Section:** Advanced Features **Updated:** 2026-10-13 Answers to common setup and operating questions about SSO, HRIS, webhooks, SFTP, and service accounts — for the admin running them. # Integrations FAQ Answers to common setup and operating questions about integrations. For what each integration surface is and how to set it up from scratch, see the [Integrations Overview](/help/articles/platform_integrations). --- ## Setup ## Do I need to configure SSO if a system-wide default is already in place? No. If a system-wide default SSO configuration exists for a provider (Google Workspace, SAML, or Microsoft Entra ID), your tenant uses it automatically with no setup required. You can optionally add your own custom configuration alongside the system default — both will appear on the login page. To use only your custom configuration, change the provider setting on the SSO Settings page to **Custom Configurations Only**. ## What information do I need to set up SAML SSO? You need three things from your identity provider: the **SSO target URL** (or the IdP metadata URL — the platform can parse the XML and fill in the fields automatically), a **certificate** or certificate fingerprint, and the **name identifier format** (defaults to email address). You can paste raw metadata XML instead of entering fields individually. After saving, use **Test Configuration** to verify the handshake before enabling it for users. ## How do I connect an HRIS, payroll, or accounting provider? Go to **Admin → Organization → Integrations → Browse All Integrations**, pick a category, and select your provider. Six categories — HRIS, ATS, CRM, Accounting, Ticketing, and File Storage — connect through a guided OAuth handshake. All other categories use API credentials you enter directly. After connecting, choose which data types to synchronise, set a sync frequency, and click **Sync Now** to run the first pull. --- ## Permissions and access ## Who can manage integrations, SSO, and webhooks? All three surfaces require the **Admin** or **Super Admin** role. Webhooks have an additional requirement: the admin must also hold the **API → Manage** permission. SSO configuration is included in every edition, so no plan stops an admin from opening the SSO settings page. ## What roles can a service account have? A service account can be assigned the **Member**, **Manager**, or **Admin** role — never Super Admin. The default is Member with read-only access and token-only authentication (no web login). Admins can upgrade a service account to read-write access and widen its role on the service account's detail page. --- ## Day-to-day ## How often do third-party integrations sync automatically? The available sync intervals are **every 4 hours** (the default), **every 6 hours**, **every 12 hours**, and **daily**. Setting the frequency to manual disables the automatic schedule entirely — you sync only by clicking **Sync Now**. Each sync is a delta pull: only records changed since the previous sync are fetched. ## What is the difference between a regular sync and a force full resync? A regular sync is a **delta pull** — it asks the provider for records modified since the last sync (with a five-minute overlap to account for clock differences). A **Force Full Resync** clears all locally imported data for the selected entity type and re-imports everything from scratch. Use it when upstream deletions are not being reflected, or when you suspect the delta watermark has drifted. Force full resync is available for HRIS and Accounting integrations. ## How do I rotate a service account token without downtime? On the service account's token detail page, click **Rotate**. This generates a new token and immediately revokes the old one in a single step. The new token and secret are displayed once — copy them before navigating away. The platform also sends expiry reminders at **14 days** and **3 days** before a token expires, so you can rotate ahead of time. ## Can a webhook subscribe to all event types at once? Yes, for platform events. When creating or editing a webhook at **Admin → Webhooks**, tick **Select all platform events**. That ticks every platform event listed on the form today; an event added to the platform later is not added to the webhook unless you tick it. There is no wildcard option in the form. Through the API, subscribing to `*` receives every listed platform event, including ones added later. Plugin events are never included, by **Select all platform events** or by `*`. They appear in their own group under each plugin's name, and you pick each one you want. --- ## When something looks wrong ## My SAML SSO stopped working — what should I check first? Check your **identity provider certificate**. The platform runs a health check that warns **30 days** before the certificate expires, and flags it as an error once it has expired. Go to **Admin → SSO Configurations**, open your SAML config, and look for a certificate-expiry warning. Other common causes: the configuration was disabled, the IdP SSO URL changed, or the name identifier format no longer matches what your IdP sends. ## Why was my webhook automatically deactivated? A webhook is deactivated after **five consecutive delivery failures**. Each successful delivery resets the counter to zero. To re-enable it, open the webhook's detail page and click **Reactivate** — this resets the failure counter and turns the webhook back on. Before reactivating, check the delivery log to see the response codes — the most common cause is the receiving system being down or rejecting payloads. ## A webhook delivery failed — will it retry automatically? Yes. Failed deliveries are retried up to **five times** with exponential backoff: after **1 minute**, then **5 minutes**, **15 minutes**, **1 hour**, and **4 hours**. You can see the retry count and next retry time on each delivery in the webhook's detail page. If all five retries fail, the delivery is marked as permanently failed and counts toward the consecutive-failure deactivation threshold. ## SSO login failures are spiking — will I be alerted? Yes. When **five or more SSO failures** occur within a one-hour window for your business, the platform automatically sends an alert to all business admins — both as an in-app notification and by email. You can review every authentication attempt at **Admin → SSO Logs**, filtered by configuration, outcome, or date range. ## My HRIS sync ran successfully but some employee records look outdated — what happened? A regular sync only pulls records that the provider marks as modified since the last sync. If a record was changed in a way the provider did not flag, it will not be included. Try running a **Force Full Resync** from the integration's detail page — this bypasses the modification watermark and re-imports all records. If the data still looks stale after a full resync, check the provider's own sync status on their side. ## I set up JIT provisioning with the system default SSO, but new users are not being created on first login — why? When using JIT provisioning with a system-wide default SSO configuration, a **domain allowlist is required**. Enter the email domains permitted for auto-provisioning on the **SSO Settings** page (for example, `yourcompany.com`). Without an allowlist, JIT will not create accounts — this restriction exists because the system-level configuration is shared across tenants, so each tenant must declare which domains belong to it. --- ## Limits and retention ## Are there limits on the number of webhooks or integrations I can create? There is no hard cap on the number of webhooks or integrations per business. Each webhook URL must be unique within your business — you cannot point two webhooks at the same destination. For integrations, the platform supports over 220 providers across 31 categories. ## How long are webhook delivery logs and SSO logs kept? The webhook detail page shows the **last 50 deliveries** for that webhook, including status, response code, and response time. SSO authentication logs at **Admin → SSO Logs** are retained indefinitely and are paginated at 50 entries per page. Expired or revoked API tokens are cleaned up after **30 days**. ## Does SAML SSO work on mobile? SAML defaults to **web only**. If your identity provider supports mobile browser-based authentication, you can change the channel setting to **Both** (web and mobile) in the SAML configuration form. Google Workspace and Microsoft Entra ID default to **Both** and work on web and mobile out of the box. --- ## More help - [Integrations Overview](/help/articles/platform_integrations) - Ask AI — the assistant answers integration questions from these articles. **Keywords:** faq, integrations, SSO, SAML, single sign-on, HRIS, webhooks, webhook failures, webhook retry, SFTP, service accounts, API tokens, sync frequency, certificate expiry, JIT provisioning, force resync, token rotation, Merge, signing secret --- # Integrations — SSO, HRIS, Payroll, SFTP, Webhooks **Category:** System-features **Section:** Advanced Features **Updated:** 2026-10-13 How the platform connects to external systems — identity providers, HR systems, payroll, file transfers, and outbound event webhooks — and what an admin configures for each. # Integrations ## 1. What it is The platform connects to external systems — identity providers, HR and payroll systems, file servers, and downstream consumers — through a central integration hub and several purpose-built surfaces. Admins configure all connections; employees interact only with SSO (login) and personal calendar sync. - **Enablement:** The integration hub at **Admin → Organization → Integrations** is available to every admin. SSO and SCIM provisioning are included in every edition. - **What it is not:** Per-app connectors that an individual app manages (e.g. calendar sync inside the Calendar app, or social publishing inside Mango GTM) are configured within those apps, not here. This article covers the platform-level surfaces. ## 2. Standing it up Integrations span several admin pages. The path depends on what you are connecting. ### SSO / Single Sign-On 1. Go to **Admin → SSO Configurations**. 2. The **Login Methods** grid shows four providers: **Google Workspace**, **SAML**, **Microsoft Entra ID**, and **MangoApps**. Toggle each one on or off. 3. If a system-wide default configuration exists for a provider, your business uses it automatically. To supply your own credentials, click **New Custom SSO Configuration**, select the provider, and enter the required settings — client credentials for OAuth providers, or metadata and certificate for SAML. 4. On the **Settings** page, choose **Include System Default** or **Custom Configurations Only** per provider. If using the system default, you can opt into just-in-time (JIT) provisioning with a required domain allowlist. 5. Use **Test Configuration** to run a health check before enabling the configuration for users. 6. Confirm by checking the **Login page preview** banner — it shows exactly which SSO buttons employees will see. ### Third-party integrations (HRIS, accounting, ticketing, etc.) 1. Go to **Admin → Organization → Integrations** to see the health dashboard, then click **Browse All Integrations**. 2. Filter by category and select a provider. Six categories — HRIS, ATS, CRM, Accounting, Ticketing, and File Storage — connect through a shared OAuth handshake. All other categories use direct API credentials you enter yourself. 3. After connecting, choose which data types to synchronise (for HRIS: employees, time off, departments, employee payroll runs) and set a sync frequency. 4. Click **Test Connection**, then **Sync Now** to run the first pull. ### Webhooks 1. Go to **Admin → Webhooks**. You need the **API → Manage** permission. 2. Click **New Webhook**, enter the destination URL, an optional description, and select the event types you want to receive. 3. A signing secret is generated automatically. Share it with the receiving system so it can verify payloads. 4. Use **Test** to fire a test event and confirm delivery. ### SFTP 1. Go to **Admin → Organization → Integrations → Browse All Integrations** and select the **File Storage** category, then choose **SFTP**. 2. Enter the host, port, username, and either a password or private key. 3. Set the direction (import, export, or both), a schedule (manual, hourly, daily, or weekly), and the file pattern. 4. Individual apps — Timesheets, Attendance, Leave, Power Tables — reference this SFTP connection from their own import/export schedule pages. ## 3. How it fits together **System Integrations** — The central model for all third-party connections. It covers 31 categories and over 220 providers. Each integration belongs to one business, stores credentials encrypted at rest, and has its own sync frequency and health status. Six categories route through a shared OAuth partner; everything else uses direct API credentials the admin enters. **SSO Configurations** — A separate surface from the integration hub. SSO configurations can be *system-wide defaults* (shared across all tenants, managed from the console) or *business-level custom* configs. A per-business settings layer lets each tenant choose whether to use the system default, a custom config, or both — and whether to enable JIT provisioning. This two-tier design means most tenants need zero SSO setup if a system default is in place. **Integration Providers (SFTP)** — A legacy integration layer used primarily for SFTP connections. SFTP providers hold host, port, credentials, schedule, and direction. Apps that need file-based data exchange (Timesheets, Attendance, Power Tables, Benefits) reference an SFTP provider rather than managing their own connection. **Webhooks** — Outbound event notifications to external systems. Each webhook subscribes to one or more of 44 event types, receives HMAC-signed payloads, and is automatically deactivated after five consecutive delivery failures. Separate from webhooks, **Workflow Webhooks** (form/approval lifecycle events) and **Workforce Bot Webhooks** (conversation events) are configured within those respective apps. **API Tokens and Service Accounts** — Programmatic access for external systems that call into the platform. Admins issue scoped tokens (over 60 available scopes) and can create non-human service accounts with role-based access. Credentials are hashed after first display and support rotation without downtime. ## 4. Running it ### Monitoring integration health Go to **Admin → Organization → Integrations** to see the health dashboard: active count, healthy/warning/error breakdown, and an overall health score. Each integration's detail page shows the last sync time, sync metrics, and a delivery log. ### Triggering a manual sync On any integration's detail page, click **Sync Now** to run an immediate delta sync. For HRIS integrations, you can sync individual entity types (employees, time off, departments) or click **Force Full Resync** to bypass the watermark and re-import everything. ### Managing SSO logs Go to **Admin → SSO Logs** to view every authentication attempt. Filter by configuration, by outcome (successful or failed), or by date range. The platform automatically sends an alert to business admins when five or more SSO failures occur within an hour. ### Reviewing webhook deliveries On a webhook's detail page, view delivery statistics — total sent, success rate, average response time — and the last 50 individual deliveries with status, response code, and timing. If a webhook has been auto-deactivated after failures, click **Reactivate** to reset the failure counter and re-enable it. ### Rotating API credentials For API tokens, use **Rotate** to generate a new token and revoke the old one in a single step. The new token is shown once — copy it before navigating away. ## 5. Settings ### SSO settings | Setting | Where | Default | What it changes | |---|---|---|---| | Enabled | Admin → SSO Configurations | Off | Whether this SSO method appears on the login page | | Channel support | SSO config form | **Both** (web and mobile) | Restricts the SSO method to web only or mobile only | | JIT provisioning | SSO Settings page | Off | Auto-creates a user account on first SSO login | | JIT allowed domains | SSO Settings page | *(none — required when JIT is on with a system default)* | Comma-separated email domains permitted for auto-provisioning | | Debug mode | SSO config form | Off | Logs detailed authentication data for troubleshooting | | Attribute mapping | SSO config form (Advanced) | Platform defaults for common IdP formats | Maps identity-provider fields to platform user fields | ### Integration settings | Setting | Where | Default | What it changes | |---|---|---|---| | Active | Integration detail page | On (at creation) | Whether the integration syncs on schedule | | Sync frequency | Integration edit form | Per-integration | How often automatic delta syncs run | | Data types to synchronise (HRIS) | Integration edit form | All off — admin opts in per type | Which entity types are pulled: employees, time off, departments, employee payroll runs, include deleted data | ### Webhook settings | Setting | Where | Default | What it changes | |---|---|---|---| | Active | Webhook list or detail page | On | Whether the webhook receives events | | Event types | Webhook form | *(none — admin selects)* | Which platform events trigger a delivery | ## 6. More help - **Integrations FAQ** — specific setup and operating questions for SSO, HRIS, SFTP, and webhooks - Ask AI — the assistant answers questions about integrations from these articles. **Keywords:** integrations, SSO, SAML, single sign-on, HRIS, payroll, SFTP, webhooks, webhook events, API tokens, service accounts, identity provider, Google SSO, Entra ID, BambooHR, Workday, ADP, Gusto, Merge, file export, file import, sync --- # Interview Scheduler App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run Interview Scheduler — scheduling, availability, question banks, scorecards, and candidate self-scheduling. # Interview Scheduler ## 1. What it is Interview Scheduler coordinates multi-round interviews across your recruiting team. It manages interviewer availability, sends scheduling links to candidates, collects structured feedback through scorecards, and tracks each candidate's progress through a configurable interview workflow. - **Enablement:** Interview Scheduler requires a license. An admin enables it from Admin → Apps → All Apps, then configures it under the app's **Settings** tab. - **What it is not:** Interview Scheduler handles the interview process — scheduling, questions, and feedback. It does not manage job postings or the applicant pipeline (that is Job Board) or offer letters (that is Offer Manager). ## 2. Standing it up 1. Enable the app from Admin → Apps → All Apps. Only admins and app-admins can access the **Settings** tab once it is on. 2. Go to **Interview Scheduler → Settings**. Set your default interview format (Phone, Video, In Person, or Hybrid), default duration, default timezone, and business hours. These defaults pre-fill every new interview so recruiters do not have to set them each time. 3. Go to **Interview Scheduler → Availability**. Each interviewer publishes their own open time slots here. Without published availability, the candidate self-scheduling flow has nothing to show — candidates open the link and see "No Times Available Yet". 4. Go to **Interview Scheduler → Scorecards**. Create at least one feedback scorecard template. A default "General Interview Scorecard" is created automatically the first time the tab is opened, with five starter criteria (Technical Skills, Communication, Problem Solving, Cultural Fit, and Leadership Potential). 5. Optionally, go to **Interview Scheduler → Questions** and create a question bank. Questions can be grouped into question sets and auto-attached to new interviews via the **Auto-attach default question set** setting. 6. Grant access to the users who will schedule and conduct interviews. The app is visible to any user with access, but the **Settings** tab requires Admin or App Admin, and **Analytics** (Questions ▸ Analytics) is open to recruiting staff and to whoever Settings ▸ Permissions names for interview analytics (app admins by default). **Silent-until-paired:** Self-scheduling links will not work until at least one assigned interviewer has published availability slots. The app warns the scheduler at send time and notifies them again when a candidate opens the link and finds no times; the candidate sees "No Times Available Yet — please check back later." ## 3. How it fits together The app has seven tabs: **Interviews**, **View Pipeline** (deep-link to Talent Hub), **Self-Scheduling**, **Questions**, **Scorecards**, **Availability**, and **Settings** (Admin / App Admin only). Phone-sized screens are redirected to a mobile-optimized view automatically. **Interviews** are the core record. Each interview has a title, a candidate, a format (Phone / Video / In Person / Hybrid), a scheduled time, assigned interviewers, and optionally a question set and a scorecard template. An interview starts as a **Draft** and moves through a lifecycle: Draft → Active (Scheduled or Confirmed) → Completed, Cancelled, or No Show. Drafts have relaxed validation — no time or meeting details are required — so a recruiter can build an interview incrementally or hand it to the candidate to schedule. A special derived state, **Awaiting candidate**, appears when a draft has a live self-scheduling link out with the candidate. Video and hybrid interviews are auto-confirmed on activation because the meeting URL is already set. Phone and in-person interviews start as Scheduled and require manual confirmation. **Availability slots** are the time windows an interviewer publishes as open for interviews. Each slot has a start and end time, a preferred format, and optional buffer times before and after. Slots can recur daily, weekly, or monthly. Slot duration must be at least 15 minutes and no more than 8 hours. When a candidate books a slot through a self-scheduling link, the slot is marked booked and tied to the interview. **Workflows** define the stages a candidate goes through — for example, Phone Screening → Technical Interview → Behavioral Interview → Final Interview. Each stage specifies a default format and duration. The default workflow ships with four stages. Workflows are assigned at the job level, and Interview Scheduler suggests the next stage automatically when scheduling a new interview for a candidate. For example, a candidate applying for a Product Manager role might move through: Phone Screening (30 min, phone) → Technical Interview (60 min, video) → Behavioral Interview (45 min, video) → Final Interview (60 min, in person). Each stage generates a separate interview record tied to the same workflow. **Scheduling links** let the candidate pick their own time. The recruiter creates an interview (as a draft), assigns interviewers, and sends a scheduling link. The candidate opens the link, sees the interviewers' published availability, and books a slot. The interview is then activated automatically. Links expire after a configurable number of days (default 7). A recruiter can switch a draft between self-scheduling and manual scheduling at any time without starting over — the **Self-Scheduling** tab tracks all outstanding links. When multiple interviewers are assigned, the scheduler can request a panel view showing only the times when **all** requested interviewers are simultaneously free. **Question sets** are reusable collections of interview questions. Questions belong to categories (Behavioral, Technical, Cultural, Situational, Competency), have a difficulty level (Easy, Medium, Hard), and carry an estimated time. Question sets can be attached to an interview, and AI can generate a draft set from a plain-language description (at least 10 characters). When Practice Hub is available, interviewers can **Rehearse** a question set — the AI plays the candidate. Question sets can also be exported to PDF. **Interview guides** are structured playbooks for interviewers. Each guide has a type (General, Role Based, Stage Based, or Competency Based), a target role and department, and a curated sequence of questions. Guides are separate from question sets — a guide is a how-to-run-this-interview document, while a set is a reusable question pool. **Scorecards** (feedback templates) standardize how interviewers evaluate candidates. Each scorecard has named criteria with weights and a rating scale (up to 10 points). The default scale is 1–5 (Poor through Excellent). When an interview is completed, each participant submits feedback through the scorecard, and the system computes an aggregate recommendation. **Panels** support multi-interviewer sessions. A panel can be sequential (one interviewer at a time), parallel (all at once), or roundtable. The panel collects independent feedback from each member, then computes a consensus recommendation — aligned (more than 75% agree) or divided. ## 4. Running it ### Scheduling an interview 1. Go to **Interview Scheduler → Interviews** and click **Schedule Interview**. 2. Select a candidate and job. The workflow stage is suggested automatically based on the candidate's history. 3. Choose the scheduling mode: **Candidate picks a time** (self-scheduling) or **I'll pick a time** (manual). - For self-scheduling, assign interviewers who have published availability. The link is emailed to the candidate automatically unless the **Auto-email scheduling links** setting is off. - For manual scheduling, pick a date and time. The system checks for conflicts with existing interviews and calendar events. 4. Optionally attach a question set and a scorecard template. If a default question set is configured, it is auto-attached. 5. Submit. With **Send invitations now** ticked (the default) the interview goes live and invitations go out at once; untick it to keep a draft and activate it later — if anything is missing, the draft is saved and the app says what is needed. ### Managing availability 1. Go to **Interview Scheduler → Availability**. Three views are available: **My Availability** (your own slots), **Team** (interviewers you have worked with), and **All Interviewers** (everyone in the business). 2. Add a slot by choosing a date, start time, end time, and preferred interview format. An **All day** option spans the full business hours. 3. Make a slot recurring by choosing Daily, Weekly, or Monthly and setting an end date. Daily recurrence can optionally skip weekends. 4. Slots with a booked interview cannot be deleted until the interview is cancelled. ### Collecting feedback 1. After an interview is completed, each participant is prompted to submit feedback. The **Require Feedback Submission** setting (on by default) controls whether this is enforced. 2. Interviewers open the feedback form from the interview detail page. If a scorecard is attached, they rate each criterion on the configured scale and add comments. 3. Feedback can be saved as a draft before final submission. Submitted feedback can be retracted back to draft for editing. 4. The interview detail page shows each participant's recommendation and an aggregate consensus. ### Reviewing analytics Go to **Interview Scheduler → Questions → Analytics** (recruiting staff, plus whoever Settings ▸ Permissions names for interview analytics). The page shows question effectiveness ratings, question set performance, and an interviewer load table — how many upcoming interviews each interviewer has in the next 30 days, with an over-capacity warning based on the configured daily cap. Analytics can be exported as a PDF. ### Calendar integration When the Calendar app is enabled, scheduled interviews are automatically pushed to interviewers' connected Google or Outlook calendars. Cancellation removes the calendar event. The Settings page shows whether the Calendar app is connected. Interviewers can also download an `.ics` file from any scheduled interview to add it to a calendar manually. ### Candidate status automation Interview Scheduler updates candidate pipeline status automatically. Scheduling an interview moves the candidate from **Applied** to **Screening**. Completing an interview moves them to **Interviews in process** or **Interviewed** (if all workflow stages are done). Cancelling the only completed interview reverts them to **Screening**. ## 5. Settings All settings are at **Interview Scheduler → Settings**. Only Admin and App Admin roles can access this page. | Setting | Section | Default | What it changes | |---|---|---|---| | Default Interview Duration | Core Scheduling Configuration | 60 minutes | Pre-selected duration on the new interview form | | Default Interview Format | Core Scheduling Configuration | Video | Pre-selected format (Phone, Video, In Person, Hybrid) | | Default Timezone | Core Scheduling Configuration | Your organization's time zone | Timezone applied to new interviews | | Buffer Time Between Interviews | Core Scheduling Configuration | 15 minutes | Minimum gap between consecutive interviews | | Maximum Advance Booking | Core Scheduling Configuration | 90 days | How far ahead an interview can be scheduled | | Minimum Notice Hours | Core Scheduling Configuration | 24 hours | Earliest an interview can be set from now; 0 allows last-minute scheduling. Skipped for candidate self-scheduled bookings | | Max interviews per interviewer per day | Core Scheduling Configuration | 5 | Shows an over-capacity warning on the Analytics page when exceeded; 0 disables the warning | | Business Hours Start | Calendar & Availability Settings | 09:00 | Start of available scheduling window | | Business Hours End | Calendar & Availability Settings | 17:00 | End of available scheduling window | | Business Days | Calendar & Availability Settings | Monday–Friday | Days of the week when interviews can be scheduled | | Time Slot Interval | Calendar & Availability Settings | 30 minutes | Granularity of the time picker | | Enable Automated Reminders | Notification & Reminder Configuration | On | Sends automatic reminders before scheduled interviews. Checked every hour; each reminder goes at the lead times set in Reminder Schedule | | Reminder Schedule | Notification & Reminder Configuration | 24 hours before | When reminders are sent relative to the interview | | Notify When Interview Scheduled | Notification & Reminder Configuration | On | Emails candidate and participants when an interview is activated | | Notify When Interview Cancelled | Notification & Reminder Configuration | On | Emails all participants when an interview is cancelled | | Notify When Interview Rescheduled | Notification & Reminder Configuration | On | Emails all participants when the interview time changes | | Notify When Feedback Submitted | Notification & Reminder Configuration | On | Emails when an interviewer submits feedback | | Auto-attach default question set | Question Bank Defaults | Off | Automatically attaches the selected default question set to every new interview | | Require Questions | Question Bank Defaults | Off | Keeps an interview from being activated (it can still be saved as a draft) until at least one question is attached | | Randomize questions by default | Question Bank Defaults | Off | Randomizes question order when a set is attached | | Require Feedback Submission | Feedback & Evaluation Configuration | On | Marks feedback as required after an interview is completed | | Feedback Deadline | Feedback & Evaluation Configuration | 24 hours | Hours after completion within which feedback is expected | | Enable Scheduling Links | Candidate Experience | On | Turns on the candidate self-scheduling flow | | Scheduling Link Expiry | Candidate Experience | 7 days | How long a self-scheduling link stays active | | Auto-email scheduling links | Candidate Experience | On | Emails the scheduling link to the candidate automatically when one is created | | Default Scheduling Mode | Candidate Experience | Candidate picks a time | Which side of the scheduling fork is pre-selected on the form | ## 6. More help - **Interview Scheduler FAQ** — specific setup and operating questions, limits, and troubleshooting. - Interview Scheduler has a companion **Guides** tab for creating structured interview playbooks. - Ask AI — the assistant answers questions about Interview Scheduler from these articles. **Keywords:** interview scheduling, interview scheduler, candidate scheduling, self-scheduling link, availability slots, question bank, scorecard, interview feedback, interview workflow, panel interview, interview-scheduler, interview_scheduler --- # Interview Scheduler FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Interview Scheduler — for the admin running it. # Interview Scheduler FAQ Answers to common setup and operating questions about Interview Scheduler. For what the app is and how to set it up from scratch, see the [Interview Scheduler Overview](/help/articles/interview_scheduler_app_overview). --- ## Setup ## Do I need to configure anything before scheduling interviews? Enable the app from Admin → Apps → All Apps — it is disabled by default and requires a licence. Once enabled, interviewers should add their availability slots so the conflict-detection and candidate self-scheduling features have time data to work with. Without availability slots, the candidate's booking page says no times are available yet and the system cannot suggest conflict-free times. ## Who can access Interview Scheduler once it is turned on? Any user the app is made available to can see the Interviews list. Each person sees the interviews they scheduled or sit on, plus every interview for a requisition they recruit or hire for; admins, HR admins and recruiting app admins see all of them. The Settings tab appears only for admins, super admins, and Interview Scheduler app admins. Analytics (Questions ▸ Analytics, exported as PDF) is open to recruiting staff on a requisition and to whoever Settings ▸ Permissions names for interview analytics (app admins only by default). ## Who can manage scheduling links and candidate self-scheduling? Sending, retiring, or resending a candidate-facing scheduling link is open to recruiting admins, anyone who is a recruiter on a requisition, the person who scheduled that interview, and whoever Settings ▸ Permissions names for scheduling links (managers and above by default). A regular interviewer-participant on an interview cannot email the candidate or invalidate a link the recruiter sent. --- ## Permissions and access ## Why can't an interviewer see the Team or All Interviewers availability view? The My Availability view is open to everyone. The Team and All Interviewers views are open to recruiting staff on a requisition and to whoever Settings ▸ Permissions names for every interviewer's calendar (app admins only by default). To give an interviewer colleagues' open times, an admin adds them there or makes them an Interview Scheduler app admin. ## Who can edit or delete a question in the Question Bank? The question creator, any admin or HR admin, or an app admin of a recruiting app (Interview Scheduler, Job Board, Offer Manager) can edit or delete a question. Other users can view and use questions but cannot modify them. --- ## Day-to-day ## What is the draft-then-activate workflow? Submitting with **Send invitations now** ticked (the default) takes the interview live and sends invitations to all participants and the candidate. Untick it to keep a draft: fill in the candidate, interviewers, time, and optionally a question set and scorecard, then activate it when ready. If something is still missing — for example no interviewers assigned or no time set — the app tells you what is needed before it will activate. ## How do I switch between scheduling the time myself and letting the candidate pick? On a draft interview, you can hand scheduling over to the candidate at any time. The app creates a scheduling link tied to the assigned interviewers' availability, and optionally emails it. If the candidate doesn't respond, you can take scheduling back — the link is retired and you pick the time yourself. Both directions work without abandoning the interview. ## What happens when I complete an interview? Marking an interview as completed triggers a feedback request to every participant who attended and has not yet submitted feedback. If the candidate has more workflow stages remaining, the candidate status updates to reflect interviews still in progress. If all stages are done, the candidate status moves to "Interviewed." ## Can I download an interview to my calendar? Yes. Every scheduled interview has a Download .ics option that produces a file you can open in any calendar app. Drafts with no scheduled time cannot be downloaded. --- ## When something looks wrong ## "I sent a scheduling link but the candidate sees no times" The candidate booking page shows time slots drawn from the assigned interviewers' availability. If no interviewer has open times that fit this interview (its length, notice and booking window), the page tells the candidate "No Times Available Yet" and you get a notification. Ask each assigned interviewer to add availability slots in the Availability tab. The app warns you at send time when no interviewer has open times, but it does allow sending the link so the candidate can check back once slots are added. ## "My interview is stuck in draft — I can't activate it" The activation check requires a candidate, at least one interviewer, a scheduled time, a duration, a time zone, and meeting details that match the interview type. Video and hybrid interviews need a meeting URL; phone interviews need a phone number; in-person interviews need a location. If questions are required in settings, a question set must be attached. The interview detail page lists what is still missing. ## "The candidate says they can't reschedule" Candidate rescheduling is governed by two settings. First, rescheduling must be allowed in settings (enabled by default). Second, there is a per-interview reschedule limit — by default the candidate can reschedule up to 2 times, configurable from 0 to 5 in settings. Once the limit is reached, the candidate sees a message that no more reschedules are allowed. ## "I don't see the Confirm button on my interview" Video and hybrid interviews are auto-confirmed when activated — there is no separate confirmation step. The Confirm action is available only for phone and in-person interviews that are in the Scheduled status and have already been activated (not still in draft). ## "Why didn't the reminder go out?" Check three things. First, reminders must be enabled in settings (on by default). Second, reminders go out at the lead times chosen in Reminder Schedule (24 hours before by default); the reminder job runs every hour. Third, the reminder recipients setting controls who receives it — by default both the candidate and interviewers. --- ## Feedback and scorecards ## Can an interviewer edit feedback after submitting it? Yes, feedback in Draft or Submitted status can still be edited. An interviewer can also retract submitted feedback back to draft to make changes and resubmit. ## What rating scale do scorecards use? Scorecard templates accept a rating scale from 3 to 10 points. The default is a 5-point scale with labels Poor, Below Average, Average, Good, and Excellent. Each criterion can be weighted from above 0 up to 10 and marked as required or optional. The five built-in recommendation levels are Strong hire, Hire, Maybe, No hire, and Strong no hire. --- ## Licensing and limits ## Does Interview Scheduler require a licence? Yes. Interview Scheduler requires a licence and is opt-in per tenant. An administrator enables it from Admin → Apps → All Apps. It is disabled by default until then. ## What are the limits I should know about? | Setting | Default | Allowed range | |---|---|---| | Interview duration | 60 minutes | Up to 480 minutes (8 hours) | | Buffer time before/after slots | 15 minutes each | 0–120 minutes | | Advance booking window | 90 days | 1–365 days | | Minimum scheduling notice | 24 hours | 0–168 hours | | Scheduling link expiry | 7 days | 1–30 days | | Feedback deadline | 24 hours after completion | 1–168 hours | | Candidate reschedule limit | 2 | 0–5 | | Max interviews per day (warning) | 5 | 0–50 (0 disables warning) | | Analytics retention | Configurable | 30–1,095 days | | Scorecard rating scale | 5 points | 3–10 points | | Availability slot duration | — | 15–480 minutes | | Reminder lead times | 24 hours before | 1, 2, 6, 12, or 24 hours | --- ## More help - [Interview Scheduler Overview](/help/articles/interview_scheduler_app_overview) - Ask AI — the assistant answers Interview Scheduler questions from these articles. **Keywords:** faq, interview scheduling, candidate self-scheduling, availability slots, question bank, scorecard, feedback, scheduling link, conflict detection, interview workflow, reschedule, interview reminder, interview-scheduler, interview_scheduler --- # Job Board App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-01 How to set up and run Job Board — job postings, the public career portal, the candidate pipeline, and the recruiting tools an admin configures. # Job Board ## 1. What it is Job Board lets you create job postings, publish them to a branded career portal, and move candidates through a hiring pipeline — all inside the same platform your employees already use. Internal employees can browse and apply for open roles without a separate login, and external candidates apply through the public portal. - **Enablement:** Job Board requires a license. An admin enables it from **Admin → Apps → All Apps**, and it is off by default for every tenant. - **What it is not:** Job Board handles postings, the career portal, and the candidate pipeline. Offer letters and interview scheduling are handled by their companion apps — **Offer Manager** and **Interview Scheduler**. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Job Board**. This grants your tenant access to the app. 2. Open **Job Board → Settings → General Settings**. Turn on **Enable Public Career Portal** if you want external candidates to see and apply for jobs. Without this, the portal returns "not available" to outside visitors. 3. If you use custom application forms, turn on **Forms App Integration** (and confirm the **Forms** app is also enabled). Optionally turn on **Auto-Generate Forms** so a standard application form is created each time you publish a job. 4. Create your first job posting: go to **Job Board → Jobs → New Job**. Fill in the title, description, location, department, and hiring manager. Save as a draft, then click **Publish** when ready. 5. Grant access to the right people. Any employee can browse published jobs in the app. Job creation requires Admin, Super Admin, HR Admin, or Job Board App Admin. Settings access is restricted to the same admin roles. **Silent-dependency warning:** The public career portal does nothing until both conditions are true — the Job Board app is enabled for the tenant **and** the **Enable Public Career Portal** toggle is on in Settings. Turning on only one produces no portal and no error. ## 3. How it fits together ### Jobs and their lifecycle A job posting moves through five statuses: **Draft → Published → Paused → Closed → Filled**. Only published jobs appear on the career portal or in the internal job list. A closed or filled job can be reopened; if its application deadline had already passed, the deadline is cleared automatically on reopen. A job can only be deleted while it is a draft with no candidates, postings, interviews, or offers attached. Once any downstream record exists, close or fill the job instead. **Example:** You create a "Warehouse Supervisor — Night Shift" posting, assign it to the Dallas location and the Operations department, set the hiring manager to the regional director, and mark priority as **Urgent**. You save as a draft. After legal reviews the description, you click **Publish**. The job now appears on the career portal and in the internal job list. When a candidate accepts an offer, you mark the job **Filled**, which triggers auto-rejection emails to remaining candidates (if that notification setting is on). ### Internal vs. external postings Every job is **external only** by default (both internal and external flags are off). Turning on **Internal posting** makes the job visible to employees logged into the platform. Turning on **Internal only** additionally hides it from the public career portal — only employees see it. Employees who apply as internal candidates go through the same pipeline, but their profile auto-fills from the employee record. An internal posting can require a minimum tenure. When set, employees who do not meet that threshold cannot apply. ### The candidate pipeline Each candidate moves through a defined set of stages: **Applied → Screening → Qualified / Potentially Qualified → Interviews in Process → Interviewed → Ready for Offer → Offered → Hired**. A candidate can also be marked **Rejected**, **Withdrawn**, or **Unsuitable** at any point. Candidates are unique per job by email — the same person can apply to multiple jobs, and the candidate profile shows other applications by that email across the tenant. ### Roles and permissions Three roles govern who can do what on a per-job basis: - **Recruiter** (assigned on the job) — the operator. Can edit the posting, manage the pipeline, schedule interviews, send SMS, and create offers. - **Hiring Manager** (assigned on the job) — the decision-maker. Can view candidates, advance or reject them, and approve offers, but cannot edit the posting. - **Admin / Super Admin / HR Admin / App Admin** — full access to every job and all settings. The per-job applications inbox shows candidate details only to these stakeholders. An employee who opens the app can see published postings, but not who applied. ### Career portal and candidate self-service The public career portal is a standalone page at your tenant URL (e.g. `https://yourcompany.workforce.mangoapps.com/apps/job_board/public`). External visitors can browse published, externally-eligible jobs, filter by location, department, employment type, or remote, and apply without creating an employee account. Employees who visit the portal while logged in see all published jobs including internal-only postings. Candidates receive a reference number and portal-access token on application. They can track their application status, withdraw, and receive job alerts. An optional AI assistant on the portal helps candidates with application questions (controlled by the **Enable AI Assistant on Career Portal** toggle). ### CRM and talent pools Talent pools are named collections of candidates for future re-engagement. Each pool has a type: **General**, **Role-specific**, **Skills-based**, or **Diversity-focused**. Candidates are added manually, via bulk actions, or through sourcing campaigns. A pool can feed an active sourcing campaign that reaches out to candidates in stages. ### Companion apps Job Board hands off to **Offer Manager** for the signed offer letter and to **Interview Scheduler** for calendar-based interview coordination. Background checks integrate via the Integrations settings page with a configured provider. Jobs can be published to external job boards (Indeed, LinkedIn, Glassdoor, CareerBuilder, ZipRecruiter) through the same integrations page. ## 4. Running it ### Creating a job with AI If **AI Job Creation** is on in Settings, you can describe a role in plain language and the AI generates a draft posting — title, description, requirements, and benefits — for you to review and edit before publishing. ### Publishing to external boards When job-board integrations are configured under **Settings → Integrations**, publishing a job can automatically post it to enabled external boards. The auto-post setting controls whether this happens on publish or only on demand. ### Managing candidates Open a job and click into its applications inbox. By default the inbox shows **Applied** and **Screening** candidates — the triage view. Use the status filter to see all stages. From a candidate's profile you can: - Advance or reject with a reason (captured on the notes thread) - Add hiring-team notes with @mentions (notifies the mentioned users) - Upload or replace a resume - Move the candidate to a different job (blocked when an active offer exists) - Send a rejection email from a template - Request a reference check or assign a skills assessment - Request a background check (when the integration is configured) - Send or view SMS messages (when SMS is enabled for the tenant and the candidate has consented) Bulk actions let you advance, reject, email, add notes to, or add multiple candidates to a talent pool at once. ### Employee referrals A referral program defines a bonus amount, eligibility rules (minimum employee tenure, max referrals per employee or per month, salary threshold), and a payment timing (on hire, after a retention period, or split). Jobs can be assigned a specific referral program or inherit the best-matching one. Employees submit referrals and track them through a **My Referrals** view; a leaderboard shows top referrers. ### Exporting candidate data Candidate lists can be exported as CSV, PDF, or XLSX. Cross-job exports require admin-level access. When **Require Identity Verification for Candidate Exports** is on, the exporter must re-enter their password or PIN; the verification lasts 15 minutes. ## 5. Settings Settings live under **Job Board → Settings** and are accessible to Admin, Super Admin, HR Admin, or Job Board App Admin only. ### General Settings | Setting | Default | What it changes | |---|---|---| | **Enable Job Board Agent** | On | Lets users interact with the Job Board Agent via Ask AI | | **AI Job Creation** | Off | Enables AI-powered job posting drafting | | **Forms App Integration** | Off | Integrates with Forms app for custom application forms | | **Auto-Generate Forms** | Off | Creates a standard application form when a job is published (requires Forms App Integration) | | **Enable Public Career Portal** | Off | Opens the public-facing careers page to external candidates | | **Enable AI Assistant on Career Portal** | Off | Adds an AI assistant to the candidate-facing portal | | **Automated Job Posting Workflows** | Off | Enables multi-level approval workflows before jobs can be published | | **Approval Reminders** | Off | Sends reminder emails for pending job-posting approvals | | **Escalate Stalled Approvals** | Off | Alerts a responsible group when an approval stage stalls (default 7 days, configurable 3–30) | | **Advanced Analytics** | Off | Shows conversion rates, time-to-fill, and source effectiveness on the dashboard | | **Require Identity Verification for Candidate Exports** | Off | Step-up authentication before candidate data exports (15-minute window) | | **Enable Candidate Data Retention Policy** | Off | Anonymizes PII of rejected/withdrawn candidates after the retention period (default 24 months, minimum 6) | ### Notifications | Setting | Default | What it changes | |---|---|---| | **Stakeholder Notifications** | Off | Notifies recruiters and hiring managers of candidate activity | | **Interview Reminders** | Off | Sends reminders for upcoming interviews | | **Send Rejection Email on Reject** | Off | Automatically sends a rejection email when a candidate is rejected | | **Auto-Reject on Job Filled** | Off | Rejects remaining candidates when a job is marked Filled | | **Auto-Reject Delay** | 24 hours | How long after a job is filled before rejection emails go out | ### Integrations Configured under **Settings → Integrations**: - **Background check provider** — select a configured provider from Admin → Organization → Integrations - **External job boards** — enable connected boards (Indeed, LinkedIn, etc.) and toggle auto-posting - **Video interview platform** — select a platform and toggle auto-scheduling ### Workflow **Workflow → Workflow Approval** configures multi-level approval chains for job postings. **Workflow → Custom Fields** adds custom data fields to the workflow. **Workflow Settings** lets you define custom candidate status workflows or reset to system defaults. ## 6. More help - **Job Board FAQ** — specific setup, operating, and troubleshooting questions - Ask AI — the assistant answers questions about Job Board from these articles. **Keywords:** job board, job posting, career portal, recruiting, hiring, candidates, applicants, referral program, talent pool, internal posting, application form, job-board, job_board --- # Job Board FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-18 Answers to common setup and operating questions about Job Board — for the admin running it. # Job Board FAQ Answers to common setup and operating questions about Job Board. For what the app is and how to set it up from scratch, see the [Job Board Overview](/help/articles/job_board_app_overview). --- ## Setup ## Does Job Board need a licence before anything works? Yes. Job Board requires a licence and is disabled by default. An admin enables it per tenant from Admin → Apps → All Apps. No features are pushed on without that opt-in. ## Who can create and manage job postings? Super Admins, Admins, HR Admins, and designated Job Board App Admins can create new job postings. Once a job exists, the hiring manager and recruiter assigned to it can also edit, publish, close, and manage candidates for that job. Settings pages are restricted to Admins and App Admins only. ## Do I need to set up the public career portal separately? Yes. The portal is controlled by a separate toggle in Job Board Settings called **Public Career Portal**. Until you turn it on, all public portal pages return a "not available" response. Enabling the portal also lets you embed your listings on an external company website using the JavaScript embed widget. --- ## Permissions and access ## Why can't a recruiter see a particular job's candidates? Candidate access is restricted to the job's stakeholders — the recruiter, hiring manager, and creator of that job — plus anyone with an Admin or HR Admin role. If a recruiter is not assigned to the job, they cannot view its candidates. Assign them as the recruiter or hiring manager on the job's edit page to grant access. ## Why can't I delete a job posting? A job can only be deleted when it is still in **Draft** status and has no candidates, internal applicants, job-board postings, offers, or interviews attached. Once any of those exist, the delete option is removed. Close the job instead — closing preserves the full history while stopping new applications. --- ## Day-to-day ## What happens when the application deadline passes? The portal stops accepting new applications for that job automatically. The job stays in **Published** status, though — it does not close on its own. You still need to close or fill the job manually. If you reopen a job whose deadline has already passed, the deadline is cleared so the job can accept applications again. ## What are the stages in the candidate pipeline? There are nine stages: **Applied**, **Screening**, **Qualified**, **Potentially Qualified**, **Interviews in Process**, **Interviewed**, **Ready for Offer**, **Offered**, and **Hired**. A candidate can also be moved to **Rejected**, **Withdrawn**, or **Unsuitable** at any point. You can advance, reject, or move candidates individually or in bulk. ## How does the posting-approval workflow work? When approval is enabled in Settings, a new job posting starts as a workflow request rather than going straight to Draft. The workflow moves through up to three review stages — budget review, management review, and final approval — depending on your configuration. Each stage notifies the designated approver by email and in-app notification, and the requestor is notified on approval or rejection. Once approved, the posting can be published. ## Can I share a published job on LinkedIn? Yes. Any employee can share a published, externally-visible job to their personal LinkedIn feed using the **Share to LinkedIn** button on the job detail page. Internal-only postings are not shareable. ## How do internal-only postings work? Any job can be marked **Internal Only** so it is hidden from the public portal and shown only in the employee internal-mobility tab. Internal candidates apply with their employee profile auto-filled. If the job has a minimum internal-experience requirement, employees who have not been with the company long enough are told they do not meet the eligibility threshold. --- ## When something looks wrong ## I applied for a job but my application status hasn't changed — what's going on? Application status is updated by the recruiting team as they review candidates. The tracking link shows one of six public stages — Application Received, Under Review, Interviewing, Offer Extended, Hired, or Not Selected — so internal pipeline detail is not exposed. If your status has not changed, it means the review is still in progress. ## A candidate applied twice — why didn't the system catch the duplicate? Duplicate detection checks the candidate's email address within the same job. If a candidate applies to the same job twice with the same email, the second application is flagged. Applying to two different jobs with the same email is allowed and not treated as a duplicate. ## Why didn't the rejection emails go out when I marked a job as Filled? Automatic rejection emails are opt-in. Turn on **Auto-reject on job filled** in the Job Board notification settings. When enabled, rejection emails are sent after a configurable delay (default **24 hours**) so you have time to cancel if you marked the job as filled by mistake. ## My referral bonus wasn't paid — what happened? Referral bonuses follow the payment timing set on the referral program. The default is **Pay after retention period**, which requires the referred hire to stay for a waiting period (default **90 days**) before the bonus becomes eligible. Check the program's settings for the payment timing and retention days. Bonuses also require admin approval before they are marked as paid. ## I can't see the candidate tracking page anymore — what happened? The tracking link expires when the candidate is in a terminal status (rejected, withdrawn, or unsuitable) or, for hired candidates, when the start date is more than **180 days** in the past. If neither of those applies, ask the candidate to check the link — the token is unique and does not change. --- ## Referrals and programs ## Can I limit how many referrals an employee can submit? Yes. Each referral program has two optional caps: **Max referrals per employee** (total across the program's lifetime) and **Max referrals per month**. Once either cap is reached, the employee sees a message that they have reached their limit. Leave both fields blank for unlimited referrals. ## Can I set different bonus amounts for different roles? Yes. Referral programs support tiered bonuses by job level and department. Configure the tiers on the program's edit page. When a candidate is referred for a specific job, the system checks for a matching tier and falls back to the program's default bonus amount if none is found. --- ## Licensing and limits ## Are there limits I should know about? | Limit | Value | |---|---| | Candidate pipeline stages | 9 | | Job title length | 255 characters | | Candidate name (first / last) | 50 characters each | | Match score range (AI match score or keyword estimate) | 0–100 | | Candidate CSV export | Up to 10,000 records per export | | Job alert frequencies | Instantly, Daily, Weekly | | Journey "stalled" threshold | More than 14 days in the current stage | ## What is the candidate retention setting and what does it do? Candidate retention is an opt-in GDPR feature in Job Board Settings. When enabled, a daily sweep anonymises candidates in a terminal status (rejected, withdrawn, or unsuitable) who have not been updated for longer than the configured retention period. The default retention period is **24 months**. The minimum you can set is **6 months** — a lower value is clamped to 6 to prevent accidental mass redaction. Anonymisation is irreversible: PII is removed, but the analytics skeleton (status, job, source, scores, timestamps) is kept. --- ## More help - [Job Board Overview](/help/articles/job_board_app_overview) - Ask AI — the assistant answers Job Board questions from these articles. **Keywords:** faq, job posting, career portal, candidate pipeline, referral program, internal posting, application deadline, approval workflow, talent pool, job alerts, auto-reject, candidate retention, not showing, permissions, duplicate candidate, job-board, job_board --- # Job Descriptions App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run Job Descriptions — one structured, versioned document per job title, with approvals, acknowledgment, compliance checks, and PDF and Word export. # Job Descriptions ## 1. What it is Job Descriptions keeps one current, structured document for every job title in your organization. A description is a set of fields, not a page of prose: a position summary, essential functions kept separate from other duties, qualifications, licenses, physical and mental demands recorded with a frequency, work environment, FLSA status, EEO category, and a reasonable-accommodation statement. Publishing freezes a version, asks the people who hold the title to acknowledge it, and gives you a PDF or Word file to hand to anyone who asks. - **Enablement:** the app requires a license and is off until an admin turns it on from Admin → Apps → All Apps. Turning it on is not the last step: until you click **Publish to users** on the app's page (or publish it to specific groups), only admins and people given a role in the app can open it. - **Who does what inside the app:** admins — business admins, super admins, and anyone granted **App admin** for Job Descriptions — author, publish, archive, import, run the Acknowledgments report and campaigns, and change Settings. A **Contributor** writes and edits descriptions, runs the compliance check, and submits a description for approval when a publication workflow is set up (with no workflow, they mark a draft **Ready for an admin to publish**, which tells the app admins), but cannot publish, archive, import, see the Acknowledgments report or change Settings. - **What it is not:** it is not Job Board. Job Board runs postings and applicants; Job Descriptions holds the record for each title, and hands a copy to Job Board when you ask it to. It is also not where your job architecture lives — families, titles, levels, and pay grades are set in **Admin → Job Titles & Families**, and the description reads them. ## 2. Standing it up 1. Make sure your titles exist. Go to **Admin → Job Titles & Families** and confirm the active titles, their family, level, code, and pay grade. The Library lists one row per active title, so with no titles the app has nothing to show. 2. Publish the app to users. In **Admin → Apps → All Apps**, open Job Descriptions and click **Publish to users** (or publish it to specific groups). Until you do, only admins and people with a role in the app can open it, and the Library and Settings pages show admins a notice saying so. Do this before you publish descriptions: nobody who can't open the app is asked to acknowledge, and publishing the app later does not go back and ask them. 3. Go to **Apps → Job Descriptions → Settings** and set the acknowledgment rules: whether publishing asks holders to sign, how many days they get, and whether new hires and transfers are asked. Edit the default reasonable-accommodation statement here once — it pre-fills every new description. 4. Write your first description. On **Library**, find a title showing **No description** and click **Write description**. You can start from a starter for a common role type, describe the job and let AI fill the form, or import what you already have (see §4). 5. Publish it. Publishing creates version 1, makes it the version employees see, and — if the acknowledgment setting is on and you leave the ask ticked in the Publish window — asks everyone holding that title who can open the app to sign it. The confirmation says how many holders were asked when that is fewer than hold the title. 6. Confirm it worked. The Library row should read **Published** with a version and date. The people holding the title can now read the description on **My Job Description**, on desktop and on their phone. If they were asked to acknowledge it, a banner there asks them to. If the app was not yet published to users when you published the description, nobody was asked: publish the app to users, then start a re-acknowledgment campaign (§4) to ask them. **Things that silently do nothing until a second thing is also set:** - **Publication approval** needs an approval workflow created in **Admin → Approval Workflows** for Job Descriptions, using the **Job description publication** trigger. The workflow must be enabled *and* have at least one approval level. A workflow with no levels is ignored, and publishing stays direct. The Settings page shows **Active** or **Not configured**, so you can tell which state you are in. - **Acknowledgment** only reaches people who actually hold the title and can open the app. If nobody is assigned the title in their profile, or the app is not yet published to them, publishing asks nobody. Service and AI accounts are never asked. - **Create posting in Job Board** appears only for a published description that is not archived, only when Job Board is enabled for your workspace, and only for an admin who can also create postings in Job Board — a business admin, an HR admin, or a Job Board app admin. - **Competencies and pay range** are never typed into the description — they render from the job title. If a description shows no competencies, add them on the title. If no pay range shows, the title needs a pay grade with a minimum and a maximum, and the description needs its pay-range option turned on. - **Automatic re-acknowledgment** is off out of the box. It does nothing until you set a cadence in Settings. ## 3. How it fits together ### The working copy and the published version Each title has one description, and that description has two faces. The **working copy** is what admins and Contributors edit. The **published version** is what everyone else sees. Editing after a publish never changes what employees see — only publishing does. Worked example: *Registered Nurse* is published at version 2, and twelve people hold the title. HR adds an on-call duty and saves. The Library row now carries an **Unpublished edits** badge, the document page warns that employees still see version 2, and all twelve still see version 2. Publishing creates version 3, and each of the twelve is asked to acknowledge it. Every publish freezes a full snapshot — the content, the author, the date, the change summary you type, and the title's family, level, grade, code, and competencies as they stood that day. A later reclassification never rewrites an old version. You can open any prior version, compare two of them side by side section by section, and restore one into the working copy; restoring does not publish, so history is never rewritten. **Compare working copy with live** shows unpublished edits beside what employees read now, before you publish or submit them. When you submit for approval, an optional **What changed?** note and a **Don't ask job holders to acknowledge it again** choice travel with the request and apply when it publishes. ### What each row in the Library means - **No description** — the title has none yet. For admins this is the work queue. - **Draft** — written, not visible to employees. - **Awaiting approval** — submitted; the content is locked until it is approved or withdrawn. - **Published** — live. - **Published · review due** — last published (or last marked reviewed) longer ago than **Flag for review after** in Settings (12 months unless you change it; 0 turns the badge off). The State filter uses the same words. Nothing expires; it is a prompt to look at it. Two things clear it, and both are on the description's page for app admins: publish an updated version, or — if you reviewed it and nothing needs to change — **Mark as reviewed**. Marking it reviewed records who reviewed it and when, restarts the review clock from that day, publishes no new version and doesn't ask job holders to sign again. Either way the badge clears and the review reminder stops. While it stays due, the reminder (Settings → **Tell the owner when a published job description is due for review**) repeats every 30 days. - **Archived** — taken out of the employee-facing view. History and acknowledgments are kept. ### Who can see what Four tiers, and a person gets the widest one that applies: - **Everyone** sees the published description for their own title, and can acknowledge it. - **Supervisors** — anyone with people reporting to them, directly or further down — also see the published descriptions for the titles their reporting line holds. - **Authors** — business admins, super admins, and the app's App admins and Contributors — see every description, including drafts, unpublished edits and every version, and can run the compliance check. - **Admins** — business admins, super admins and the app's App admins — additionally see the acknowledgment report, Import, and Settings. Someone named as an approver on an open publication request can also read the description they are being asked to approve, until the request closes. Readers cannot edit. Their door is **Suggest a change** on a published description: they write what is missing, wrong, or out of date. The person who wrote the description and whoever last edited it are notified, as long as they can still author job descriptions, along with anyone in the group chosen under **Send Job Descriptions admin notices to this group** in Settings; when that leaves nobody, the app's admins are notified instead. The note stays on the document with their name and the version they were reading. ### Acknowledgment versus a re-acknowledgment campaign Both ask a person to sign, and they are not the same thing. An **acknowledgment** is pinned to a version. It is created when a version is published, or when someone takes the title. Publish a new version and the old ask is superseded by a fresh one, so a signature always refers to content the person actually saw. A **re-acknowledgment campaign** asks people to confirm the description they already have — no content change, no new version. Use it for an annual attestation. People who signed before are asked afresh and their earlier signature stays on record; people who already have an open request are left alone rather than given a second one. ### Where it touches other apps - **Admin → Job Titles & Families** owns families, titles, levels, and pay grades. The description reads them and freezes them into each version. - **Job Board** owns postings. "Create posting" copies the published description into a **draft** posting linked to the title; the recruiter tailors and publishes it there. It is a one-time copy, so later edits to the description do not reach the posting. While a draft posting for the title is still sitting in Job Board, **Create posting** opens that draft instead of making a second one. - **Performance Management** can score the title's competencies inside a review. That is switched on per review template, on the template's rating-categories step — not here. - **Ask AI** answers questions about descriptions using exactly the read tier above. ## 4. Running it ### Publish a revision without making everyone sign again 1. Edit the description and open **Publish revision**. 2. Untick **Ask current job holders to acknowledge this version** for a typo or formatting fix. Earlier acknowledgments stand, nobody is re-asked, and anyone who still owed a signature keeps the same request — it moves to the new version, so the obligation neither disappears nor doubles. 3. Type what changed. That summary shows in the version history and on the request. ### See who has signed, and chase the rest 1. Go to **Acknowledgments**. Each published description shows Holders (who holds the title today), Requested, Signed, Overdue, and a progress bar. 2. Click a title to list the people, with their status and the date they signed. 3. **Export CSV** for the whole report. You do not have to chase people by hand. Reminders start three days after a request is sent. Before the deadline they repeat on the cadence set in **Settings → Remind about an outstanding acknowledgment every** (7 days unless you change it); once the deadline has passed they come every 3 days. They stop when the person signs, and 8 weeks after the request was sent — after that the request still shows as outstanding on the report. If **Escalate overdue acknowledgments to the employee's manager** is on, the manager is also told once the deadline passes, and again every two weeks while it stays open. ### Run a re-acknowledgment campaign 1. On **Acknowledgments**, click **Re-acknowledgment campaign**. 2. Name it, choose every published description or pick specific titles, set the days to acknowledge, and add an optional note for the report. 3. Start it. The flash tells you how many people will actually be asked, and says so plainly when nobody is due. Asks are sent in the background and the campaign card fills in. To run this on a schedule instead, set **Re-acknowledge every** in Settings. Each month the app opens one campaign and asks every holder whose last signature is older than the cadence, and every holder who has never acknowledged the description. People who already have an open request are left alone, so nobody is asked twice. ### Check a description before publishing Open a description and choose **Check this job description** from the actions menu. The panel scores it out of 100 and lists findings by severity, covering biased or exclusionary language, overstated physical demands, missing ADA elements, FLSA and EEO completeness, pay-transparency readiness, and reading level. The header tells you what produced the findings: **Rules N · AI review N** when the optional AI pass ran, or **Rules only** when it did not. Rule findings are deterministic and repeat identically; AI findings are advisory and carry an **AI** tag, and may differ between runs. Nothing here blocks publishing — you decide. ### Bring in the descriptions you already have Go to **Import**. Upload up to 50 Word, PDF, or text files at once; each is parsed into the structured sections and matched to a title by code, then exact name, then partial name. Titles that already have a description are skipped. Everything lands as a **draft** — an import never publishes anything — and you get a notification when the batch finishes, naming each skipped file and why. An AI model reads each file into the sections, so this needs **Let bulk import use AI to read uploaded files** switched on in Settings; while it is off, the Import page says so and takes no files. If your descriptions are already in spreadsheet columns, use the **Smart Import** link on the same page instead. ## 5. Settings At **Apps → Job Descriptions → Settings**. The page is in four groups — Acknowledgment, Notifications, Document defaults, and AI features — followed by what the Ask AI assistant can do, the publication-approval status, and sample data. | Setting | Default | What it changes | |---|---|---| | Ask current job holders to acknowledge each published version | On | Publishing asks everyone holding the title who can open the app to sign that version. The request always reaches their inbox; the email that goes with it follows each person's Job Descriptions notification preference. The Publish window lets you skip it for a single revision. | | Ask new hires and transfers to acknowledge their job description | On | Setting or changing someone's job title asks them to acknowledge the published description for the new title. | | Days to acknowledge | 14 days (1–365) | Sets the due date on each request; after it, the request counts as overdue on the Acknowledgments report. | | Re-acknowledge every _N_ months | 0 (off), up to 60 | Above zero, one campaign opens each month asking every holder whose last signature is older than the cadence, and every holder who has never acknowledged the description. People with an open request are left alone. | | Remind about an outstanding acknowledgment every _N_ days | 7 days (0–90) | Reminders to the person who still has to sign start three days after the request and repeat every _N_ days until the deadline; after the deadline they come every 3 days. They stop 8 weeks after the request was sent. 0 turns reminders off, before and after the deadline — the request still shows as outstanding on the report. | | Escalate overdue acknowledgments to the employee's manager | On | Once a request passes its deadline, the employee's manager is told, and again every two weeks while it stays open — including after the employee's own reminders stop. If an admin has set the Overdue Escalation Ladder for job descriptions under **Admin › Notifications**, that ladder decides instead and this switch has no effect. | | Tell job holders when their description changes without asking them to sign again | On | When a version is published without asking for signatures, holders who signed an earlier version are told it changed, with a link. Nothing is added to what they owe. | | Tell the owner when a published job description is due for review | On | When a description passes **Flag for review after**, the person who wrote it is told while they can still author job descriptions, and the notice repeats every 30 days until a new version is published or an app admin marks it reviewed. Nothing is sent while **Flag for review after** is 0. | | Send Job Descriptions admin notices to this group | None | Review due, suggested changes and campaign receipts go first to the person they concern while they can still act on it — the description's author (for a suggestion, its last editor too), or whoever started the campaign — and the group you pick is added to them. When that leaves nobody, the group is told instead of the app's admins; a draft marked ready to publish goes to the group's members who can publish it instead of the app's admins (when none of them can, to the app's admins after all). With no group, an empty list goes to the app's admins (or, if it has none, your business admins). | | Default reasonable-accommodation statement | A standard ADA statement | Pre-fills every new description and every import. Editable per document. Up to 2,000 characters. | | Flag for review after _N_ months | 12 months (0–120) | A published description last published or marked reviewed longer ago than this is badged **Published · review due** in the Library, and the State filter of the same name finds it. 0 turns the badge and the review reminder off. | | Show the pay grade's range on new job descriptions by default | Off | New descriptions start with the title's pay range shown on the document, the exports, and any posting built from it. | | Job Descriptions AI assistant in Ask AI | On | Turns the read-only assistant on or off. It can find a description, summarize duties, run the compliance check, and list who has not acknowledged — always within what the person asking may already see. | | Let the compliance check use AI to review wording for bias and ADA risk | On | Off, **Check this job description** runs its rule checks only and says **Rules only**; no description text is sent to an AI model. | | Let bulk import use AI to read uploaded files into structured job descriptions | On | The AI model is the only reader for Word and PDF files, so off, **Word/PDF import stops working** and the Import page says so. Smart Import for spreadsheets is unaffected. | | Offer AI describe-to-fill on the job description form | On | Off, the "Describe it and let AI fill the form" bar is not shown on the job description editor. | | Publication approval | Not configured | Set in **Admin → Approval Workflows** using the **Job description publication** trigger. While a workflow is active, publishing goes through it and approved content publishes automatically. | The same page has **Load sample data**, which fills the app with example families, titles, published descriptions with version history, one draft, one due for review, and acknowledgment rows for you — useful for a walkthrough, and removable from the same card. ## 6. More help - **Job Descriptions FAQ** — specific setup and operating questions, limits, and what to do when something does not look right - **Job Board App Overview** — postings and applicants, and what "Create posting" hands over - Ask AI — the assistant answers questions about Job Descriptions from these articles **Keywords:** job description, essential functions, ADA, FLSA status, EEO category, physical demands, job description acknowledgment, re-acknowledgment campaign, job description approval, compliance check, job description versions, what does my job description say, who hasn't signed their job description, job-descriptions, job_descriptions --- # Job Descriptions FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Job Descriptions — publishing, versions, approvals, acknowledgment, re-acknowledgment campaigns, import, and the compliance check. # Job Descriptions FAQ Answers to common setup and operating questions about Job Descriptions. For what the app is and how to set it up from scratch, see the [Job Descriptions Overview](/help/articles/job_descriptions_app_overview). --- ## Setup ## Do I have to set anything up before I can write the first job description? Yes — your job titles. A job description is always written **for a title**, so the title has to exist first, under **Job Titles & Families**. The Library lists every active title and shows which ones have no description yet; that list is your work queue. Family, level, pay grade, code and competencies are read from the title and never re-typed into the document. ## Who can create, publish and read job descriptions? Four tiers, and everyone falls into at least the last one. 1. **Admins** — business and super admins, plus anyone granted **App admin** for Job Descriptions. They author, publish, archive, import, run the Acknowledgments report and campaigns, and change settings. 2. **Contributors** — anyone granted **Contributor** for Job Descriptions. They write and edit descriptions, run the compliance check, restore an earlier version into the working copy, and submit a description for approval when a publication workflow is set up — with no workflow, they mark a draft **Ready for an admin to publish**, which tells the app admins and shows on the description who marked it ready and when. They cannot publish, archive, import, see the Acknowledgments report or change settings. Admins and Contributors are the only people who see drafts and unpublished edits, apart from an approver reading the description they have been asked to approve; everyone else reads published versions only. 3. **Supervisors** — anyone with people reporting to them, directly or further down. They read the published description of any title held by someone in their reporting line. 4. **Employees** — everyone reads the published description for their own title, on desktop or on their phone, and acknowledges it when asked. Granting **App admin** is how you hand day-to-day ownership to an HR partner without making them a business admin; granting **Contributor** lets someone draft descriptions while an admin keeps control of what goes live. Both are granted on the app's Admins & Contributors page. --- ## Permissions and access ## Why can't a supervisor open the job description for someone outside their team? Because a supervisor's reach is their own reporting line. They see the published description of their own title, plus every title held by someone below them in the reporting tree — nothing else. If the person genuinely reports to them, check that the reporting relationship is set on the employee's profile and that their membership is active. ## I finished editing — why do employees still see the old version? Editing never changes what employees see. Your edits are held as an unpublished revision that only admins and Contributors can open; employees keep reading the last **published** version until you publish again. The document page tells you this directly, with a link to the version employees are currently reading. --- ## Day-to-day ## What happens when I publish a job description? Publishing does four things in one step. 1. It freezes a full, permanent version — every section, plus the title's family, level, pay grade, code and competencies exactly as they stood that day. 2. It records who published it, when, and the change summary you typed. 3. It makes that version the one employees see. 4. Unless you clear the checkbox (or **Ask current job holders to acknowledge each published version** is off in Settings), it asks every current job holder who can open the app to acknowledge it, with a due date and reminders. A description needs a position summary and at least one essential function before it can be published. ## I only fixed a typo — how do I publish without asking everyone to sign again? Clear the **Ask current job holders to acknowledge this version** checkbox in the Publish window. The new version still goes live, and nobody is asked afresh. Each holder who already has an open request keeps it — the request simply moves onto the new version, with the same due date. Nothing is lost and nothing doubles up. Leave the checkbox ticked for any change that alters what the job actually is. With an approval workflow, the same choice is made when you **Submit for approval**: add a short **What changed?** note for the approver and job holders, and tick **Don't ask job holders to acknowledge it again** for a correction that does not change the job. The choice is applied when the approval publishes. ## How do I ask every job holder to confirm their description again when nothing has changed? Start a re-acknowledgment campaign from the **Acknowledgments** tab. It asks every current holder in scope to confirm the version already published — no content change of any kind. Two rules matter: - People who already have an open request are **skipped**, so they never get two asks for the same thing. - People who signed earlier are **asked again**, and their earlier signature stays on record. Scope the campaign to every published description or to selected titles. You also set the days to acknowledge and can add a note that shows on the report. The confirmation message tells you how many people will actually be asked, not how many hold the titles. ## Can re-acknowledgment happen automatically on a cadence? Yes. In **Settings**, set **Re-acknowledge every N months**. The default is **0, which means off**; the range is **0 to 60 months**. With a cadence set, one campaign opens per calendar month. It asks every job holder whose last signature is older than the cadence to confirm their current description again, and every holder who has never acknowledged it. People with an open request are left alone, and someone whose earlier request was withdrawn is asked once the cadence has passed since that request. These campaigns appear on the Acknowledgments report alongside any you start by hand. ## We reviewed a job description and nothing needs to change — how do I clear "review due"? Open the description and use **Mark as reviewed** in the "Due for review" note at the top of the page. It is there for app admins — the same people who publish. It records that the description was reviewed, by whom and when, and restarts the review clock from that day: the **Published · review due** badge clears in the Library, the review reminder stops, and the next review falls due after your **Flag for review after** interval. No new version is published and job holders are not asked to sign again. If something does need to change, edit it and publish an updated version instead — that restarts the clock too. ## Does publishing need approval first? Only if your organization sets that up. Add an approval workflow for Job Descriptions with the **Job description publication** trigger, under Admin → Approval Workflows. With a workflow in place, you submit for approval instead of publishing, and approved content publishes automatically — no second click. With no workflow, publishing is direct. Settings shows which of the two states you are in. An approval covers the exact content the approver saw. Edit after approval and you need a fresh approval. ## Why can't I edit this job description right now? Almost always because an approval request is open, which locks the content. That is the promise the approval makes: the approver signs off on this text, not on whatever it becomes afterwards. Use **Withdraw approval request** on the document page to unlock it, edit, then submit again. The same block applies to restoring an old version while a request is open. If you see no **Edit** button at all, you are reading as an employee or supervisor rather than as an admin or Contributor. Use **Suggest a change** instead. ## Can I go back to an earlier version? Yes. Open **Version history**, pick a version, and restore it. Restoring copies that version's content into the working copy and records the move as a new entry — history itself is never rewritten or deleted. Restoring does **not** publish; review the restored content and publish it when you are ready. Every version is kept indefinitely, and any two can be compared side by side, section by section. Authors can also compare unpublished edits with what employees read now: **Compare working copy with live** on Version history (or on the description itself while it has unpublished edits) shows the working copy beside the live version before you publish or submit it. ## How do I bring in our existing Word and PDF job descriptions? Use the **Import** tab. Upload up to **50 files per run** in Word (.docx or .doc), PDF, or plain text. Each file is read, split into the structured sections by an AI model, matched to one of your job titles, and saved as a **draft** — imports never publish anything. The run happens in the background and finishes with a notification listing what was created and what was skipped. Because the AI model is the only reader, the Import tab takes no files while **Let bulk import use AI to read uploaded files into structured job descriptions** is off in Settings. If your descriptions already live in spreadsheet columns rather than documents, use the **Job descriptions** target on the shared Smart Import page instead. ## Why was one of my import files skipped? The notification lists every skipped file with its reason. The reasons are: - **No matching job title.** The notification names the title, and the code when the file had one. Add that title under Job Titles & Families, then import the file again. Matching tries the position code first, then an exact title name, then a partial name match. - **That title already has a description.** Existing work is never overwritten by an import. - **No readable text was found** in the file. - **The document could not be split into job-description sections.** - **The file was read, but the draft couldn't be saved** — the reason the save was refused follows. - **Word/PDF import is switched off.** **Let bulk import use AI to read uploaded files into structured job descriptions** was turned off in Settings after the upload. Turn it back on and upload the files again. - **The upload couldn't be read back from storage.** Upload that file again. - **Couldn't import this file**, followed by the error — for example, when your workspace's AI usage limit stopped the AI reading it. If the AI reading service itself is unavailable, the run is retried. If it stays unavailable, you get a notification saying the import stopped, naming any drafts that were created before it did; the uploaded files are not kept, so upload the rest again. A created draft can carry a note too: when the file was long and only its first 24,000 characters were read, when the title was matched only by a partial name, or when more than one job title matched. Open the draft and check it against the original, and that it sits on the right title. ## Does the compliance check stop me from publishing? No — it is advisory in every case, and the author decides. **Check this job description** scores the working copy out of 100 and lists findings by severity, and the panel separates two kinds: - **Rule findings** are deterministic and repeatable: ADA shape, overstated physical demands, FLSA and EEO completeness, biased or exclusionary language, reading level, and pay-transparency readiness. - **AI review findings** are advisory suggestions and may differ between runs. They are labelled with an **AI** badge. Clarity, vagueness and jargon notes from the AI review never rise above **Low** severity. Only protected-group language and absolute physical requirements written into prose can carry a higher one. The reading-level check flags anything above a 12th-grade reading level. Only the prose is graded — the demand grids are not sentences, so they are left out. ## Why don't I see "Create posting in Job Board"? Four conditions have to hold. The description must be **published**, because the posting is built from the published version rather than the working copy, and it must not be **archived**. **Job Board must be enabled** for your workspace. And you need admin access to Job Descriptions *and* the right to create postings in Job Board — a business admin, an HR admin, or a Job Board app admin. A delegated Job Descriptions admin without Job Board access does not see the option. When it runs, it creates a **draft** requisition linked to the same title, built from the published version, so the posting starts from the approved record. The recruiter tailors and publishes it in Job Board. It is a one-time copy: later edits to the description do not reach the posting. If the description shows the pay grade's range, the posting inherits it too. While a draft posting for the title is still sitting in Job Board, **Create posting** opens that draft instead of creating a second one. ## Someone spotted a mistake but can't edit the description — what can they do? They use **Suggest a change** on the document page, or the **Suggest a change** link on My Job Description. It is the only door for readers, who cannot edit. The note is limited to **2,000 characters** and is kept on the document. The person who wrote the description and whoever last edited it are notified, as long as they can still author job descriptions, along with anyone in the group chosen under **Who else receives Job Descriptions admin notices** in Settings. When that leaves nobody, the app's admins are notified instead. A document keeps **50** suggestions; past that, the oldest answered one makes room first. Authors see a panel on the page with open suggestions first, each with its author, the version they were reading and the date, and they mark each one **Done** or **Not changing**. The person who suggested it sees their own suggestions under **Your suggestions** on the same page, with that answer, and is told when it is answered. --- ## When something looks wrong ## "My Job Description page is empty — where is mine?" One of three things, and the page says which. - **No job title is set on your profile.** Ask your administrator to assign one; your description appears there once it is published. *For admins:* set the person's **Job Title** on their employment profile. If the title has a published description, it shows on their page straight away, and with **Ask new hires and transfers to acknowledge their job description** on, they are also asked to acknowledge it. - **The description for your title has not been published yet.** It appears here once HR publishes it, and you are asked to acknowledge it if HR asks holders to sign. - **It was archived.** Your acknowledgment history is kept, and a new description appears here if HR publishes one. ## "I already signed this — why am I being asked to acknowledge it again?" Two situations ask a second time, both on purpose. - **A new version was published.** Each signature is pinned to the exact version it was given for, so a new version means a new request. That pinning is what makes the record defensible. - **A re-acknowledgment campaign is running.** It asks you to confirm your current description because time has passed. The notice tells you whether anything in it has changed since you last signed — or that you haven't acknowledged a version of it before — and your earlier signature is untouched. Acknowledging closes the request immediately, along with any reminder sitting in your inbox. ## "I keep getting reminders about my job description — when do they stop?" Reminders begin **three days** after the request is sent. Until the deadline they repeat on your organization's reminder cadence — every **7 days** unless an admin changed it in Settings. Once the deadline has passed they come every **3 days**. They stop **eight weeks** after the request was sent. Acknowledging stops them at once. They also stop if the description is archived, or if a newer version supersedes the request. Past the eight weeks the request sends nothing further, but it still shows as outstanding on the admin report. If an admin set the reminder cadence to 0, no reminders are sent at all. ## Nobody was asked to acknowledge the version I just published — why? Work through these in order. 1. **The app isn't published to users yet.** Nobody who can't open the app is asked to acknowledge, and publishing the app later does not go back and ask them. The Library and Settings pages show admins a notice while this is the case. Publish the app to users (**Admin → Apps → All Apps**, the app's page, **Publish to users**), then start a re-acknowledgment campaign from **Acknowledgments** to ask the people who were skipped. 2. **The checkbox in the Publish window was cleared.** That is the "minor edit" path — the version goes live and nobody is asked afresh. 3. **The setting is off.** Check **Ask current job holders to acknowledge each published version** in Settings. 4. **Nobody currently holds the title.** Only active people holding that title are asked; service and AI-agent accounts are never asked to sign a job description. 5. **They were already asked for this same version** — requests are never duplicated for the same person and version. ## Why does the acknowledgment report show a different number of people than currently hold the title? Because the two columns count different things, deliberately. **Holders** (**Current Holders** in the CSV export) is who holds the title today. **Requested** is how many acknowledgment requests exist for the published version, and **Signed** (**Acknowledged** in the CSV) is how many of those are signed. These things make Holders and Requested diverge: - Someone took the title after the version was published, and **Ask new hires and transfers to acknowledge their job description** is switched off. - The publisher cleared the ask checkbox for that version. - Some holders couldn't open the app when the version was published — for example, before it was published to users — so they were not asked. Someone who was asked and has since moved to a different title counts in neither column. Their request and any signature stay on the record, and on the per-person CSV. ## What happens when I archive a job description? Employees stop seeing it, and any acknowledgment still waiting on them is closed out as no longer required. Everything else is kept: past versions, past signatures, and the employee's own acknowledgment history. Two follow-ons are worth knowing. An archived description cannot be published as-is — restore a version first, which returns it to draft. And you cannot archive one while an approval request is open, so withdraw the request first. --- ## Licensing and limits ## Does Job Descriptions need a licence, and who turns it on? Yes. Job Descriptions requires a licence and is **off by default** for every workspace — nobody gets it without opting in. A business admin enables it from Admin → Apps → All Apps, then clicks **Publish to users** on the app's page — until then only admins and people with a role in the app can open it. They can then delegate day-to-day ownership by granting someone **App admin** for the app, or let someone draft descriptions by granting **Contributor**. Pricing and packaging live on the app's directory listing. ## What are the limits and default values? | Setting or limit | Value | |---|---| | Job descriptions per job title | One | | Versions kept | Unlimited — nothing is pruned | | Ask job holders to acknowledge each published version | **On** by default | | Ask new hires and transfers to acknowledge | **On** by default | | Days to acknowledge | **14** by default; accepts **1–365** | | Re-acknowledge every N months | **0 (off)** by default; accepts **0–60** | | Campaign days to acknowledge | Starts from your Settings value; accepts **1–365** per campaign | | Campaign name and note | Name up to **120 characters**; note up to **1,000** | | Remind about an outstanding acknowledgment every N days | **7** by default; accepts **0–90** (0 = no reminders). Reminders start 3 days after the request, repeat every N days until the deadline, then every **3 days**; they stop **8 weeks** after the request | | Escalate overdue acknowledgments to the employee's manager | **On** by default; the manager is told once the deadline passes, then every two weeks while it stays open | | Tell job holders when their description changes without asking them to sign again | **On** by default | | Tell the owner when a published job description is due for review | **On** by default; repeats every **30 days** until a new version is published or an app admin marks it reviewed | | Send Job Descriptions admin notices to this group | **None** by default. The group is added to whoever a notice goes to first — the description's author (for a suggestion, its last editor too) or the campaign's starter. When that person has left or lost access, the group is told *instead of* the app's admins, and a draft marked ready to publish goes to the group's members who can publish it instead of the app's admins (when none of them can, to the app's admins after all) — so add anyone who should still hear of these to the group. With no group, an empty list falls to the app's admins | | Flag for review after N months | **12** by default; accepts **0–120** (0 = never flag) | | Show the pay grade's range on new job descriptions | **Off** by default | | Job Descriptions AI assistant in Ask AI | **On** by default | | Let the compliance check use AI to review wording for bias and ADA risk | **On** by default; off, the check runs its rules only | | Let bulk import use AI to read uploaded files into structured job descriptions | **On** by default; off, Word/PDF import stops working | | Offer AI describe-to-fill on the job description form | **On** by default | | Default reasonable-accommodation statement | Up to **2,000 characters** | | Suggestion from a reader | Up to **2,000 characters**; the 50 most recent are kept per document | | Bulk Word/PDF import | Up to **50 files** per run | | Accepted import file types | Word (.docx, .doc), PDF, plain text | | "Published · review due" state in the Library | Last published or last marked reviewed longer ago than **Flag for review after** (12 months by default); the Library's State filter uses the same words. It clears when a new version is published, or when an app admin uses **Mark as reviewed** on the description's page — that restarts the review clock with no new version and doesn't ask job holders to sign again | | Percent-of-time across essential functions | Cannot exceed **100%** | | Demand frequencies | Never, Occasionally, Frequently, Constantly — leaving an activity at Never omits it | | Export formats | PDF, Word (.docx); Library and Acknowledgments export to CSV | --- ## More help - [Job Descriptions Overview](/help/articles/job_descriptions_app_overview) — what the app is, how it fits together, and what to set up first - Job Titles & Families — where titles, levels, pay grades and competencies are maintained - [Job Board Overview](/help/articles/job_board_app_overview) — what happens to a posting created from a published description - Ask AI — the read-only Job Descriptions assistant finds a description, summarizes its duties, runs the compliance check, and lists who has not acknowledged, always scoped to what you can already see **Keywords:** faq, job descriptions, essential functions, acknowledgment, re-acknowledgment campaign, version history, publish, approval workflow, compliance check, ADA, FLSA, EEO category, physical demands, accommodation statement, pay range, import, reminders, review due, mark as reviewed, not showing, permissions, job-descriptions, job_descriptions --- # Labor & Employment Law Rules **Category:** Business-configuration **Section:** Administration **Updated:** 2026-08-12 How the platform tracks wage, overtime, break, scheduling, and minor-work rules per jurisdiction, keeps them current through legal updates, and enforces them in shift assignment. # Labor & Employment Law Rules ## 1. What it is Labor & Employment Law Rules is the platform's compliance engine for wage-and-hour, overtime, break, scheduling-notice, and minor-work regulations. It lets an admin map each location to a jurisdiction, attach the rules that apply there, and have the scheduling engine enforce those rules automatically during shift assignment. - **Enablement:** Available to any admin. The five admin surfaces — Labor Law Rules, Employment Law Rules, Work Policy Settings, Compliance Explorer, and Employment Law Audit History — appear in the admin sidebar under the Work Policies section. - **What it is not:** This is not Content Governance (moderation of user-generated content) or the Compliance Hub app (SOX/SOC 2 vendor compliance). It governs labor regulations that affect scheduling, pay, and breaks. ## 2. Standing it up 1. Go to **Admin → Employment Law Rules**. This surface shows the global rule library that MangoApps maintains — browse it to confirm the jurisdictions and document types that apply to your locations. 2. Go to **Admin → Labor Law Rules** and create the rules that govern your business. Each rule belongs to a **jurisdiction** and has exactly one **rule type**: wage, overtime, break, schedule, or minor. If your jurisdictions do not exist yet, create them first under **Admin → Jurisdictions** — each jurisdiction needs a code, name, and level (country, state, or city), and you can nest city inside state inside country. 3. Assign jurisdictions to locations. Until a location has at least one jurisdiction, the scheduling engine has no rules to enforce for shifts at that location — this pairing is the most common silent setup gap. 4. Go to **Admin → Work Policy Settings** to configure the tenant-wide enforcement dials: maximum daily hours, maximum weekly hours, minimum rest period, and break enforcement mode. The break enforcement mode starts in **observe** — it evaluates and records break-compliance events but does not block anything. Move it to **enforce** only after reviewing your break-compliance backlog. 5. To confirm it is working, create a shift at a location that has a jurisdiction with rules. The scheduling engine should apply compliance checks during assignment — blocked assignments appear in the Compliance Audit Logs. ## 3. How it fits together **Jurisdictions** are the organizing spine. A jurisdiction has a level (country, state, or city) and can be nested — a city jurisdiction has a state parent, a state has a country parent. When the scheduling engine resolves which rules apply to a shift, it walks the jurisdiction hierarchy from most specific (city) to least specific (country) and takes the highest-priority rule per type. Every jurisdiction belongs to the business and can optionally link to a global **system jurisdiction** maintained by MangoApps. When linked, the platform can keep the jurisdiction's name and code synchronized with the global catalog. **Labor Law Rules** are per-business, per-jurisdiction rules with five types: - **Wage** — minimum wage rate (decimal, e.g. $15.50) - **Overtime** — daily and/or weekly overtime thresholds (hours) - **Break** — meal break timing, rest break intervals, and a structured break-requirements document for complex multi-period statutes - **Schedule** — advance notice days for schedule publication - **Minor** — work-end time and maximum daily hours for minors Each rule has an effective date, an optional expiration date, and a priority. When two rules of the same type apply to a location (e.g. a state and a city wage rule), the more specific jurisdiction wins. A rule can optionally link to a MangoApps-maintained system rule and inherit its rate instead of using locally entered values — the admin chooses the rate source per rule. **Exceptions** let an admin exempt a specific role or employee from a labor law rule, or override a rule's value for them. Exception types are **override** (changes the value) and **exempt** (removes the rule). Target groups are **role** and **employee** — each must resolve to a real role type or user in the business. **Employment Law Rules** are a separate, broader knowledge base maintained globally by MangoApps (no business_id). They cover 18 document types — separation agreements, WARN notices, employee handbooks, non-compete agreements, leave policies, wage-hour rules, pay transparency, predictive scheduling, safety compliance, ADA accommodation, AI employment rules, and more. Admins cannot edit these directly but can add **business overrides** — either an "additional" rule (a requirement beyond the legal minimum) or a "stricter" rule (tightening an existing system rule). Overrides cannot relax system rules. **Legal Updates** track law changes over time. When MangoApps updates a system employment law rule, a legal update notification is created with a review period (default 30 days). Affected businesses receive a review record they can acknowledge, customize (by creating an override), or dismiss. If no action is taken before the review period ends, the update auto-applies. Reviews flagged as **urgent** are those with critical severity or whose auto-apply deadline is within 3 days. **Work Policy Settings** (the RestPeriodSetting record) are the tenant-wide dials that the scheduling engine reads during shift assignment. They govern maximum hours, rest periods, break enforcement, and which violations are hard disqualifiers (block the assignment entirely) versus soft warnings (penalize the match score). ## 4. Running it ### Creating a labor law rule 1. Go to **Admin → Labor Law Rules** and click **New**. 2. Select a jurisdiction and a rule type. 3. Fill in the fields for that type — the form shows only the fields relevant to the selected type (e.g. a wage rule shows only the minimum-wage field). 4. Set the effective date. Optionally set an expiration date and priority. 5. Save. The rule is active by default. ### Loading default rules 1. On the **Admin → Labor Law Rules** index, click **Load Defaults**. 2. This loads a seed file of standard rules for the business. Existing rules are not duplicated — the seed uses find-or-create logic. ### Adding a business override to an employment law rule 1. Go to **Admin → Employment Law Rules**. 2. Browse or search the system rules. Click a rule to see its details. 3. Click **New Override** on the rule detail page — or go to the **Overrides** tab. 4. Choose the override type: **additional** (new requirement) or **stricter** (tightening an existing system rule). A stricter override must reference a system rule. 5. Fill in the rule name, description, clause text, jurisdiction, document type, and category. Provide a business justification. 6. Save. The override is active and current immediately. ### Reviewing a legal update 1. Go to **Admin → Employment Law Rules** and click the **Legal Updates** tab. 2. The stats bar shows pending, reviewed, customized, and urgent counts. 3. Click a pending update to see the old and new clause text side by side. 4. Choose an action: **Acknowledge** (accept the system change), **Customize** (create a stricter business override), or **Dismiss** (mark as not applicable). Each action closes the review. ### Adding an exception to a rule 1. Go to **Admin → Labor Law Rules**, click a rule, then click **New Exception**. 2. Select the exception type (override or exempt) and target group (role or employee). 3. Provide the target value — a specific role type or employee. The value must resolve to a real record in the business. 4. Save. The exception is active by default and checked during scheduling enforcement. ### Using the Compliance Explorer 1. Go to **Admin → Compliance Explorer**. 2. The dashboard shows total active system rules, jurisdiction count, and a breakdown by level (federal, state, city). 3. Use the **Rules** tab to browse and filter by document type, rule category, jurisdiction level, or keyword. 4. Use the **Gap Analysis** tab to see where the business has compliance gaps — missing rules, documents, or training for its jurisdictions. 5. Use the **Search** tab for semantic search across the rule catalog using natural language. ## 5. Settings These settings live under **Admin → Work Policy Settings** and govern how the scheduling engine enforces compliance. | Setting | Default | What it changes | |---|---|---| | Max daily hours | 12.0 | Shifts that would push an employee past this cap are penalized or blocked | | Max weekly hours | 40.0 | Weekly hour accumulation cap | | Min rest period (hours) | 8.0 | Minimum hours required between the end of one shift and the start of the next | | Enforce daily hours | On | Whether the daily-hours cap is checked during assignment | | Enforce weekly hours | On | Whether the weekly-hours cap is checked during assignment | | Enforce rest period | On | Whether the rest-period minimum is checked during assignment | | Meal and rest break enforcement | **Observe — record findings only** | Off: no break evaluation. Observe: evaluate and record findings but do not block. Enforce: evaluate, record, prompt at clock-out, and block non-compliant assignments | | Daily hours hard disqualifier | On | When on, exceeding daily hours blocks the assignment entirely; when off, it only penalizes the match score | | Weekly hours hard disqualifier | On | Same as above for weekly hours | | Rest period hard disqualifier | On | Same as above for rest period | | Emergency override enabled | On | Whether managers and admins can override compliance blocks | | Compliance override roles | Manager, Admin, Super Admin | Which roles can authorize a compliance override | | Contracted days off | **Soft prompt** | Whether an assignment on a contracted day off raises a confirm dialog a manager can override, or fails outright | Labor law rule defaults (per rule, not per tenant): | Setting | Default | What it changes | |---|---|---| | Active | On | Whether the rule is enforced | | Priority | 0 | Higher-priority rules win when two rules of the same type apply | | Rate source | **Use my own values** | Switch it to **Use the MangoApps-maintained rate** and the rule inherits its rate from the linked MangoApps system rule | ## 6. More help - **Labor & Employment Law Rules FAQ** — specific setup questions, allowed ranges, and troubleshooting - **Audit Logs & Activity History** — the Employment Law tab records every compliance event this engine produces - **Compliance Administration** — overall compliance settings and policies - Ask AI — the assistant answers questions about labor law compliance from this article. **Keywords:** labor law rules, employment law rules, minimum wage, overtime threshold, break compliance, meal break, rest period, scheduling notice, minor work rules, jurisdiction, legal update, compliance override, break enforcement, work policy settings --- # Labor Law Rules FAQ **Category:** Faq **Section:** Administration **Updated:** 2026-08-12 Answers to common setup and operating questions about Labor & Employment Law Rules — for the admin running it. # Labor Law Rules FAQ Answers to common setup and operating questions about Labor & Employment Law Rules. For what the system is and how to set it up from scratch, see the [Labor & Employment Law Rules Overview](/help/articles/compliance_labor_law). --- ## Setup ## Do I have to assign jurisdictions to locations before anything works? Yes. The scheduling engine resolves rules by walking the jurisdiction hierarchy attached to a location. Until a location has at least one jurisdiction assigned to it under **Admin → Compliance → Jurisdiction Mapping**, the engine has no rules to enforce for shifts at that location — assignments proceed with no compliance checks and no audit trail. ## What rule types can I create, and which fields does each one use? Each labor law rule has exactly one type, and the form shows only the fields for that type: - **Wage** — minimum wage (decimal, e.g. $15.50) - **Overtime** — daily overtime threshold and/or weekly overtime threshold (hours) - **Break** — meal break timing, rest break intervals, and an optional structured break-requirements document for complex multi-period statutes - **Schedule** — advance notice days for schedule publication - **Minor** — work-end time and maximum daily hours for minors ## What are the three jurisdiction levels, and which one wins when they overlap? Jurisdictions sit at one of three levels — **Federal**, **State**, or **City** — and they nest (a city has a state parent, a state has a federal parent). When two rules of the same type apply to a location — for example a state wage rule and a city wage rule — the more specific jurisdiction wins: city beats state, state beats federal. --- ## Permissions and access ## Who can access the labor law and employment law admin surfaces? All five surfaces — Labor Law Rules, Employment Law Rules, Work Policy Settings, Compliance Explorer, and Employment Law Audit History — are in the admin sidebar. Access is limited to **Admin** and **Super Admin**. There is no app-specific licence gate; these are platform administration surfaces available to any tenant. --- ## Day-to-day ## Can a rule inherit its rate from the MangoApps-maintained system rule instead of using my own values? Yes. Each labor law rule can optionally link to a matching MangoApps-maintained system rule. The rule form shows a **Rate source** choice: pick **Use the MangoApps-maintained rate** instead of **Use my own values** and the rule takes its rate (minimum wage, overtime thresholds) from the linked system rule. The choice only appears when the rule's jurisdiction is linked to a system jurisdiction and the rule type has a matching category (wage, overtime, break, and schedule do; minor does not). ## What is a business override on an employment law rule, and can I relax a system rule? An override lets your business add a requirement beyond the legal minimum ("additional") or tighten an existing system rule ("stricter"). You cannot relax or remove a system rule — that is enforced by validation: a "stricter" override must reference an existing system rule, and there is no "relaxed" override type. ## What happens when MangoApps updates a system employment law rule? A legal update notification is created with a review period — 30 days by default, or 14 days for critical-severity updates. Your business receives a review record you can acknowledge, customize (by creating a stricter business override), or dismiss. If no action is taken before the review period ends, the update auto-applies. The auto-apply job runs daily at 02:05 UTC. ## What makes a legal update review "urgent"? A review is urgent when either the notification's severity is "critical" or the auto-apply deadline is within 3 days. ## How do exceptions work — can I exempt a specific role or employee from a rule? Yes. Each labor law rule can have exceptions with two types: **exempt** (removes the rule entirely for the target) and **override** (changes the rule's value for the target). Target groups are **role** (must be one of the business's configured role types) and **employee** (must be a valid user ID in the business). The target value is validated at save time — a typo or stale ID is rejected. During scheduling, the compliance engine checks role-based exceptions first, then employee-specific exceptions. --- ## Break compliance ## What are the three break enforcement modes? The **Meal and rest break enforcement** setting on Work Policy Settings offers three choices: 1. **Off — do not evaluate breaks** — no break evaluation at all 2. **Observe — record findings only** — evaluate and record break findings but do not block anything or reach anyone 3. **Enforce — prompt, block and adjust pay** — evaluate, record, prompt at clock-out, block non-compliant assignments, and produce payroll adjustments New tenants start on **Observe** so an admin can review their break-compliance backlog (under **Meal Compliance → Break Compliance**) before enforcement begins. ## Can an employee waive a meal break? It depends on how the break rule defines that meal period. A period can be always waivable; waivable only within an hours window — for example over 5 hours worked but not over 6; or not waivable at all. When a period is waivable for the shift's length, the waiver form offers it with the window spelled out ("Waivable only on days over 5 and up to 6 hours worked") and the employee chooses **Waived (voluntary)** or **Not waived — will take this meal period** for that specific period. --- ## When something looks wrong ## "I created rules but nothing gets enforced during shift assignment" Three things to check: (1) The location must have at least one jurisdiction assigned under **Jurisdiction Mapping** — without it the scheduling engine has no rules to apply. (2) The rules must be **Active** (on by default) and current — effective date in the past, expiration date either blank or in the future. (3) Work Policy Settings must have the relevant enforcement toggle turned on — **Enforce Daily Hour Limits**, **Enforce Weekly Hour Limits**, and **Enforce Minimum Rest Periods** are all on by default, but if someone turned one off, that check is skipped. ## "A legal update auto-applied before we reviewed it" The auto-apply job runs daily and applies any pending notification whose review period has already ended. The review period is 30 days for important/informational updates and 14 days for critical updates, counted from the notification's creation date. To prevent auto-apply, take action (acknowledge, customize, or dismiss) before the deadline. Urgent reviews — critical severity or fewer than 3 days until auto-apply — are flagged in the Legal Updates tab. ## "The Compliance Explorer search returned nothing for my query" The semantic search applies a relevance cutoff of 0.65 and discards weaker matches rather than showing them. Queries that are too vague or unrelated to any rule text will fall through to the keyword search and ultimately the empty state, rather than returning irrelevant results. Try using more specific legal or regulatory terms in your search. --- ## Limits and exact values ## What are the default Work Policy Settings values? | Setting | Default | Allowed range | |---|---|---| | Max daily hours | 12.0 | any value > 0 | | Max weekly hours | 40.0 | any value > 0 | | Min rest period (hours) | 8.0 | any value > 0 | | Daily hours warning threshold | 80% | 1–100 (integer) | | Weekly hours warning threshold | 80% | 1–100 (integer) | | Meal and rest break enforcement | Observe — record findings only | Off, Observe, Enforce | | Max consecutive shift overlap | 30 minutes | 0–60 (integer) | | Contracted Days Off | Soft prompt | Soft prompt, Hard block | | Emergency override enabled | On | — | | Compliance override roles | Manager, Admin, Super Admin | — | | All hard disqualifiers | On | — | ## Are audit log records editable? No. Employment law audit log records are immutable. Once a compliance event is logged, it cannot be edited or deleted by anyone — there is no path in the product, or behind it, that changes a record after it is written. --- ## More help - [Labor & Employment Law Rules Overview](/help/articles/compliance_labor_law) - [Audit Logs & Activity History](/help/articles/compliance_audit_logs) - [Compliance Administration](/help/articles/compliance_admin) - Ask AI — the assistant answers labor law compliance questions from these articles. **Keywords:** faq, labor law rules, employment law rules, jurisdiction, minimum wage, overtime threshold, break compliance, meal break, rest period, scheduling notice, minor work rules, legal update, compliance override, work policy settings, break enforcement mode, what-if simulator --- # Leader Rounds App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-18 How Leader Rounds works — structured leader-to-staff rounding conversations on a cadence, a stoplight issue ledger that closes the loop, and coverage rolled up the reporting line. # Leader Rounds App Overview Leader Rounds is structured leader rounding on staff: a leader has a short, recurring conversation with each direct report — what's working, who deserves recognition, what's broken, what do you need — and every issue raised becomes a tracked stoplight item the person who raised it can follow in the app when Leader Rounds is open to them. Coverage rolls up the reporting line so a director knows which leaders are rounding and what's stuck. Find it at **Apps → Leader Rounds** (or `/apps/leader-rounds`); on a phone it opens as a mobile capture surface at `/m/apps/leader-rounds`. ## Key Concepts (How It Works) **A round** is one recorded conversation: a leader, a subject (the person rounded on), a date, typed answers to a template's questions, and optional private notes. Rounds are records of conversations that already happened — you can't schedule a future round, and a round dated in the future is rejected. A round can also be **skipped** with a required reason (for example, the person is on leave), so an untaken round is a recorded decision rather than a gap. **The two visibility tiers** are the app's most important rule. The *shared tier* — the answers and the issues raised — is visible to the subject whenever they can open Leader Rounds (it is published to them, or they are in its audience): they see the rounds about them, the items they raised, current status, and the written reason whenever something is closed without a fix. The *private tier* — the leader's private notes — is visible to the leader and the leader's own management chain, and by default to every administrator of your company (a setting an admin can turn off, under **Settings → Who Can Do What**). It is never shown to the subject, and it is never available to the AI assistant. **The stoplight is derived, never hand-set.** An issue raised in a round lives on the platform's corrective-action register with an owner and a due date. Its color is computed: **green** when resolved, **red** when it's past due or was closed without a fix, **yellow** otherwise. Closing an issue as won't-fix requires a written reason, which the person who raised it can read when they can open Leader Rounds. Rounding covers everyone on a leader's reporting line, so when someone can't open the app the round, issue and skip forms name them and say to tell them another way. Every status change also lands an audit note on the issue's timeline, in the same transaction as the change. **Cadence is an obligation, not a calendar event.** The app never creates meetings on its own. Instead it answers one question per direct report: *have you rounded on this person in the last N days?* The due list computes itself from the org chart, so transfers and new hires are picked up automatically and deactivated people never appear. **Rounding Programs decide which conversation, and on what clock.** A program is an ordered rule: an audience (job title, department, location), optionally a leader filter (the leader's job title or department, or specific leaders chosen by name), a template, and a cadence. For each leader-and-person pair the first program that matches wins, and it supplies both the template the capture form opens with and the cadence the due list measures against. A program that sets only a cadence keeps the default template, and vice versa. When no program matches, the pair falls back to the tenant's **default rounding cadence** setting (30 days out of the box). Surfaces show the program's name, so a leader can see why they are being asked for a particular conversation on a particular clock. **Obligation covers direct reports; reach covers the subtree.** A leader is anyone with direct reports. Their due list and coverage number count *direct reports only* — but they may manually round on anyone deeper in their reporting subtree (skip-level rounding), and doing so never inflates anyone's overdue count. **Templates are copy-and-edit.** Three starters install automatically — Staff Rounding, New Hire 30-60-90, and Senior Leader Rounding. Starters stay pristine: to customize, duplicate one and edit the copy (question types: Rating 1–5, Yes / No, Pick from a list, Free text, Recognition — pick a person, and Issue — logged to the Issue Ledger). **Pacing turns a long cadence into a short monthly list.** A leader with 40 direct reports on a 120-day cadence should be rounding on about 10 a month, not 40. My Rounding shows a target for the current month — the sum, across the leader's people, of how much of each person's cadence falls inside the month — and an "up next" list of who to see, ordered by who has gone longest without a round. A leader can pin specific people to the front of the month's list. Pacing changes only the view: whether someone is overdue is still computed from completed rounds, and coverage uses the same formula, so the two can never disagree. **Pillars are the tenant's own strategy headings.** Pillars ("People & Culture", "Safety", "Customer Experience") are named by an admin, optionally from an industry preset. Template questions map to a pillar, so an issue raised from a question inherits it; a leader can override an individual issue's pillar. Pillars group the ledger's chips, the Themes tab's sections, and the rows of the Stoplight Board. **Substantive rounds are what count.** A completed round with every answer blank and no issue logged does not count toward coverage — that, plus subject visibility and same-day-cluster flagging, is how the app resists box-checking. **Themes roll up what leaders can already read.** The Themes tab aggregates scale and yes/no answers by team, location, or job title across the viewer's own reporting line. Every group with answers renders, whatever its size, because those rounds are attributed conversations the viewer can already open one by one. Below that numeric breakdown, an admin can run **AI themes**: one clustering pass over the written answers of the last 90 days, producing labelled themes with a reach count and a suggested pillar. An admin can refile any theme under a different pillar, and that human call sticks — later extraction runs never move it. Unlike the numbers above them, AI themes are a tenant-wide aggregate, so the anonymity floor applies: a theme is listed only once it was drawn from at least the configured minimum group size (5 by default). **Team conversations let a leader hear from the whole team before rounding.** When an admin switches them on, a leader can ask their direct reports three questions — what's going well, what gets in the way, and what the leader should ask about on their rounds — in a short, anonymous conversation with an AI interviewer. Each person is invited in their Inbox, even if Leader Rounds was never rolled out to them, and can take part once. While it is open (1–14 days, 7 by default) the leader sees only how many have taken part. Once it closes — on its last day, or earlier with Close Now — the answers are put together into a readout: each topic shows what several people said, a topic fewer people than the anonymity floor spoke to is held back, and if fewer than the floor took part at all the leader sees only the count. A team smaller than the floor can't be asked. Team conversations are off by default because every conversation uses AI credits. ## Who Can Do What | Role | What they can do | |---|---| | **Everyone who can open Leader Rounds** | See the rounds about them and the issues they raised ("Rounds About Me"), with status and won't-fix reasons; open any published Stoplight Board that covers them | | **Leaders** (anyone with direct reports, or managers) | Capture and skip rounds on their subtree, manage the issue ledger for rounds they lead, see Team Rollup, Themes and the Rounds Log for their reporting line, compose and publish Stoplight Boards over their own org, and delegate their rounding upward | | **Admins / Leader Rounds app admins** | Everything above across the whole tenant, plus Templates, Rounding Programs, Pillars, AI theme extraction, and Settings | Being the *subject* of a round grants read access only — a subject can never change the status of an issue they raised, even if they are themselves a leader. ## Main Surfaces - **My Rounding** — your due list (who's past cadence, who's never been rounded) and recent rounds, with Round Now and Skip actions. When team conversations are on, its "Hear from your team before your rounds" card starts one, shows the count while it is open, and shows the latest readout. - **Team conversations** — every team conversation you opened, newest first, each with its readout (also on a phone). - **New Round** — the capture form. Pick the person and template, answer as you talk, log issues with owners and due dates. You can also paraphrase the conversation into the AI assist bar and review the filled form. A "who deserves recognition" answer can be posted to Recognitions in one click afterward — the recognition goes through the normal moderation and approval gates. - **Issue Ledger** — every issue from rounds you can see, filterable by stoplight color, paginated, with inline status updates. - **Team Rollup** — coverage %, open reds, aging, and same-day-cluster flags per leader, with search, window filters (30/60/90 days), and CSV export. - **Themes** — aggregated answers by team, location, or job title across your reporting line, plus the AI theme list an admin can extract from written answers. - **Stoplight Board** — a red/yellow/green board with one row per pillar for a chosen leader and month, for huddle screens and slide decks. A leader composes it: the lights and issue counts are derived from that period's ledger and cannot be hand-set, while the summary and next steps for each row are written by the leader (AI can draft them from the period's issues, and the leader edits before saving). Publishing freezes the board — lights, counts and text are recorded as they stood — and adds a PDF export. Everyone the board covers can open a published board; drafts stay with their author and admins. A Leader Rounds admin can withdraw a published board, with a reason: it leaves everyone's view and stays listed for admins as withdrawn, and the admin can start a corrected board for the same month from it. Once a new board for that month is published, an old link to the withdrawn one takes the people it covered to the new board. - **Rounds Log** — every round you are allowed to see, not just the ones you led, filterable by leader and time window with the issue count and a substantive marker per round. This is how a director audits a coverage number: before it existed, a subordinate leader's round was visible to their manager only if it happened to raise an issue. - **Rounds About Me** — the subject tier: your rounds, your raised issues, and links back to the conversation each came from. - **Delegations** — hand your rounding obligation to someone above you in the reporting line for a set window (parental leave, a secondment). It is a transfer: your people move onto the delegate's due list and coverage number, and you stop being counted as due, for as long as the window is open. Only the obligation moves — your delegate could already see and round on these people — and a leader can hold one delegation at a time. Ending a delegation closes its window rather than deleting it, so past coverage still resolves correctly. Admins see who is covering for whom right now. - **Templates** — the template library: three pristine starters plus your own copies, industry packs, the shared central library, and AI-drafted question sets. - **Rounding Programs** — admin: which template and cadence applies to whom, as an ordered list of rules. Each rule shows how many people its audience actually matches, a rule that can never apply because one above it matches everyone says so, and a preview shows what a chosen leader's team would resolve to. - **Pillars** — admin: the strategic-pillar taxonomy, with industry presets offered on an empty list. Shows how many template questions map to each pillar. A pillar nothing references can be deleted; one with references archives instead, so history stays honest. - **Settings** — admin: the fallback cadence, weekly reminders, red-issue escalation and its backstop, the monthly team digest, the anonymity floor, team conversations, the AI switches, and Load/Remove Sample Data. ## Notifications & Automation - **Issue updates:** when an issue you raised changes status, you get an in-app notification (deduplicated — one per status change), including the written reason on a won't-fix. - **Weekly due reminders:** once a week (Monday, 08:00 UTC), each leader whose direct reports are past cadence gets one in-app digest naming who's due. Admins can turn this off in Settings; individuals can mute the Leader Rounds category in their notification preferences. A leader can also pause their own reminders from My Rounding. - **Red-issue escalation:** an open issue still red a set number of days past its due date notifies the leader's manager and re-nudges the owner, then repeats weekly while it stays red. Issues closed as won't-fix are decisions and never escalate. Admins control both the switch and the grace window in Settings. - **Monthly team digest:** on the 1st of each month, one aggregate "you said, we did" post per team on the News Feed — issues raised in rounds, issues resolved, what's still open. It never names who raised what and only posts for teams at or above the anonymity floor. Off by default; the News Feed admin can also switch Leader Rounds contributions off separately. - **Team conversation invitations:** when a leader opens a team conversation, each person on their team gets an invitation in their Inbox and as a push notification on the mobile app; it expires when the conversation closes. Everyone invited can switch these off under Leader Rounds · Team conversations in their notification preferences, including team members who don't use Leader Rounds themselves. The leader is told in-app when the readout is ready. - **Home dashboard widget:** leaders see rounds due and open reds on their dashboard (desktop and mobile), linking to exactly the lists counted. ## The AI Assistant The Leader Rounds assistant in Ask AI is **read-only**. It answers six kinds of questions: your due list, coverage rolled up your reporting line, ledger searches, the full history of one specific issue, your own rounds, and — when team conversations are on — what your team said in your own team conversations, never quoting anyone and never below the anonymity floor. It only ever reports what you can already see in the app, and private notes are not available to it at all. To capture a round, skip someone, or update an issue, it will point you into the app. Admins can disable the assistant in Settings. Inside the product, AI drafts in three places, each with a human in the loop: describe-to-fill on the capture form, a drafted question set on a new template, and the Stoplight Board's summary and next-steps text. In every one of them AI produces a draft that a person reviews and edits before anything is saved. Three more features send content to an AI model without drafting anything: voice dictation transcribes what a leader says on the capture form, theme extraction (run by an admin) clusters recurring themes from written answers, and — when team conversations are on — an AI interviewer talks with each team member and puts together the leader's readout from what several of them said. Each has its own switch in Settings. ## Settings | Setting | Default | What it does | |---|---|---| | Default rounding cadence | 30 days | The fallback interval between rounds per direct report, used for any pair no Rounding Program covers. Range 1–365. | | Weekly due reminders | On | The Monday in-app digest to leaders with due rounds | | Escalate aging red issues to the leader's manager | On | An open issue still red past the grace window below notifies the leader's manager and re-nudges the owner, weekly while it stays red. Won't-fix issues never escalate. | | Days an issue stays red before escalating | 7 days | The grace window, counted from the issue's due date, so a leader always gets this long before anyone above them hears about it. Range 1–90. | | Post a monthly "you said, we did" digest to each team's feed | Off | One aggregate News Feed post per team on the 1st of the month. Never names who raised what; only posts for teams at or above the anonymity floor. | | Minimum group size (anonymity floor) | 5 people | Applies in five places: the monthly team digest posts to a team only once this many distinct people had a substantive round; a newsletter block scoped to a single team shows numbers only at or above this size; on the Themes tab an **AI theme is listed only when it was drawn from at least this many people**; and on a Stoplight Board a pillar row built from fewer than this many distinct subjects keeps its light but hides its counts, in the published PDF too; and in a team conversation's readout a topic is shown only once this many people spoke to it. It does **not** apply to the numeric answer breakdown on the Themes tab — those rounds are attributed and the tab is visible only to leaders of the people in it. Raising this hides existing themes and board rows; lowering it never lowers the floor a team was promised when its conversation opened. The lowest value is your company's smallest group (set in Privacy), up to 25. | | Escalation backstop | None | A recipient group that hears about a stuck red issue when its leader has nobody above them. Left blank, those escalate to nobody. | | Leader Rounds AI assistant | On | The read-only Ask AI assistant | | Team conversations before rounds | Off | Lets leaders open anonymous AI conversations with their team. Every conversation uses AI credits. | | AI theme extraction | On | The Extract Themes run on the Themes tab | | AI drafting | On | Describe-to-fill on the capture form, the Stoplight Board's drafted text, and Generate with AI on Templates | | Voice dictation | On | The Speak button on the capture form, which sends the recording for AI transcription | Settings also carries Load/Remove Sample Data, which seeds a full demo state (rounds, every stoplight color, a same-day cluster) and removes it exactly. ## Scope Leader Rounds is **staff rounding only**: leaders rounding on their people. Patient rounding, EHR/census integration, and HCAHPS are deliberately out of scope. Historical import and offline capture are deferred by design. **Keywords:** leader rounds, rounding, leader rounding, staff rounding, stoplight, stoplight report, check-in, due list, coverage, issue ledger, themes, ai themes, pillars, stoplight board, rounding programs, delegation, pacing, evidence-based leadership, team conversations, hear from your team, leader-rounds, leader_rounds --- # Leader Rounds FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-18 Answers to common setup and operating questions about Leader Rounds — cadence, the due list, the stoplight ledger, themes, reminders, and what employees see. # Leader Rounds FAQ ## Setup ## Do I have to configure anything before leaders can start rounding? No. The three starter templates (Staff Rounding, New Hire 30-60-90, Senior Leader Rounding) install themselves the first time anyone opens the app, and the default cadence is 30 days. A leader with direct reports can capture their first round immediately. ## How do I customize the rounding questions? Starter templates stay pristine — you can't edit them directly. On the Templates tab, click **Duplicate** on a starter, then edit the copy: change a question's **Order** number to move it, remove questions, add new ones, and set the template's own cadence. Question types are Rating (1–5), Yes / No, Pick from a list, Free text, Recognition (pick a person), and Issue (logged to the Issue Ledger). A question that already has recorded answers keeps its type and can't be removed — duplicate the template to change it. ## How do I give different groups a different template or a different cadence? Use **Rounding Programs** (in the sidebar next to Templates). A program is a rule: an audience — job title, department, location — optionally narrowed to specific leaders, plus the template to use and the cadence to measure against. Programs are ordered, and the first one that matches a leader-and-person pair wins. Anyone no program covers falls back to the default rounding cadence in Settings. The list shows how many people each program's audience actually matches, so a filter that matches nobody is visible before anyone wonders why rounds aren't happening. ## A template has its own "Cadence (days)" field — when does that apply? Only when a Rounding Program assigns that template without setting a cadence of its own. Picking a template on the capture form never changes anyone's cadence — otherwise a leader could clear their own due list by choosing a different conversation. With no programs configured at all, every pair uses the tenant default. ## What are pillars, and do I have to set them up? Pillars are your organization's strategy headings — "People & Culture", "Safety", "Customer Experience". They are optional, but they are what groups the Themes sections, the ledger's chips, and the rows of the Stoplight Board. On the Pillars tab an empty list offers an industry preset (healthcare, retail, manufacturing, hospitality, call center) as a starting point you then rename. Map your template questions to pillars, and issues raised from those questions inherit the pillar automatically; anything unmapped shows as **Unaligned**. A pillar nothing references can be deleted; one that is referenced archives instead, so old boards and issues keep resolving. ## Permissions and access ## Who counts as a leader in this app? Anyone with direct reports in the org chart, plus anyone with a manager role or above. The rounding obligation covers direct reports only; a leader may also round on anyone deeper in their reporting line (skip-level), and doing so never adds to anyone's overdue count. ## Who can see a round's private notes? The leader who wrote them and that leader's own management chain. By default every administrator of your company can read them too — that is a setting (**Settings → Who Can Do What → "Business administrators can read private notes"**), and turning it off leaves the notes with the leader and the leaders above them. The person rounded on never sees them either way, and the AI assistant cannot read them for anyone. ## Can the person rounded on update the issues they raised? No. When Leader Rounds is open to them, they can see their issues, the owner, the status, and the written reason if something is closed without a fix — but only the leader who held the round, that leader's management chain, or an admin can change a status. This keeps the ledger the leader's record of follow-through. ## Who can see the Themes tab? Leaders see themes for their own reporting line; admins see the whole tenant. In the **numeric breakdown**, every group with answers renders whatever its size — those rounds are attributed, and the tab only aggregates conversations the viewer can already read one by one. The **AI theme list** below it is different: those themes are a tenant-wide aggregate, so the anonymity floor applies and a theme is listed only once it was drawn from at least the minimum group size. The floor also governs the monthly team digest, single-team newsletter blocks, and Stoplight Board rows. ## Who can see a Stoplight Board? A published board is visible to the leader it covers, everyone in that leader's org — the huddle audience it was made for — every leader above them, and app admins. Drafts are visible only to whoever is composing them, plus admins. Composing is limited to leaders, over their own org; a tenant-wide board is app-admin only. Who may **publish** is a setting (**Settings → Who Can Do What → "Who can publish a stoplight board"**) — any leader, for boards they composed, unless an admin narrows it. A published board can't be edited. If one was published by mistake, a Leader Rounds admin can **Withdraw** it from the board's page, with a reason. It then disappears for everyone it covered. Admins still see it under **Withdrawn**, with who withdrew it, when, and why. A corrected board can then be composed for the same month. Publishing and withdrawing send no notification. ## Day-to-day ## What makes a round count toward coverage? It must be completed and substantive — at least one question actually answered, or an issue logged. A round saved with every answer blank and no issue shows in history but does not count toward the leader's coverage number. That rule is deliberate: it keeps box-checking from reading as engagement. ## What should a leader do when someone is due but unavailable? Use **Skip** on the due list and give the reason (for example, "on approved leave until March"). The reason is required. A skipped round is a recorded decision, so the director sees a deliberate skip, with its reason, in the Rounds Log instead of an unexplained gap. Coverage on the Team Rollup still counts the person as not rounded, because it counts conversations only. ## Can an issue start out overdue? No. When an issue is captured during a round, its due date is set to today or later — a past date is moved up to today, and if no date is given it defaults to two weeks out. Red status is earned by real slippage, never by form input. ## Why does a recognition posted from a round say "awaiting approval"? The one-click recognition goes through the same gates as any other recognition: content moderation, anti-gaming checks, and your tenant's approval routing. If your Recognition program requires manager approval or the content is held for review, the post waits there. Each recognition answer can be posted once — the button then shows "Recognition posted." ## What does the "Same-day cluster" flag on Team Rollup mean? It means most of that leader's rounds in the window — five or more, with at least 80% stamped on a single calendar day in your organization's timezone — were logged in one sitting. It's a conversation prompt for the director, not an accusation: twelve rounds logged in four minutes usually weren't twelve conversations. ## When do leaders get reminded about due rounds? Once a week (Monday, 08:00 UTC — Sunday evening in Hawaii), each leader whose direct reports are past cadence gets one in-app digest naming who's due. It fires at most once per leader per week. Admins can turn reminders off in Settings; individuals can mute the Leader Rounds category in their own notification preferences. A leader who wants a break can pause their own reminders from My Rounding and resume them later. ## My cadence is long and my team is large — do I really have to round on everyone this month? No, and the app says so. My Rounding shows a monthly target: for each of your people it works out how much of their cadence falls inside this month, adds those up, and rounds up. On a 120-day cadence with 40 direct reports that is about 10, not 40 — and it shows an "up next" list of who to see, longest-unrounded first. If you want to see someone out of turn, pin them and they move to the front of the month's list. Pacing only changes what you are shown: whether a person is overdue is still worked out from the rounds and skips actually logged. One difference to know: a skip settles that person on your due list and this month's target, but Team Rollup coverage counts conversations only, so a skipped person still counts as not rounded there. ## I'm going on leave — can someone else cover my rounding? Yes. On **Delegations**, hand your rounding to someone above you in the reporting line for a set window. It is a transfer, not a copy: while the window is open your people move onto your delegate's due list and their coverage number, and you stop being shown as due or named in the Monday digest. Only the obligation moves — your delegate could already see and round on these people, so nobody gains access they didn't have. Recency carries across, so someone you rounded on ten days ago isn't immediately due for your delegate. You can hold one delegation at a time, so there is never a question of whose month it is. Ending one closes its window rather than erasing it, and past coverage still reads correctly; a delegation that hasn't started yet can be deleted outright. ## What is the Stoplight Board for? It is the board a leader takes into a huddle or a monthly review: one row per pillar for a chosen leader and month, each row red, yellow or green with a short summary and next steps. The lights and the issue counts are derived from that month's ledger — there is no status dropdown anywhere, so nobody can paint a row green. The words are the leader's; AI can draft them from the period's issues, and the leader edits before saving. Publishing freezes everything as it stood and gives you a PDF for the slide deck. A published board also shows what each row's light was on the previous board, so a row going red is visible rather than buried. ## How does a director see rounds their own managers did? Open **Rounds Log** (under My Rounding). It lists every round you are allowed to see, not just the ones you led, with filters for leader and time window, the issue count per round, and a marker for whether the round was substantive. My Rounding answers "who do I owe a round?"; the log answers "what actually happened across my line?", which is what makes a coverage number auditable. ## What are AI themes, and can I overrule one? On the Themes tab, an admin can run an extraction: one pass that clusters the written answers from the last 90 days into labelled themes, each with how many people it came from and a suggested pillar. Any admin can refile a theme under a different pillar, and that decision sticks — later extraction runs never move it. The numbers above the AI list are separate: those are the scale and yes/no answers, counted directly. ## What is a team conversation, and what does my leader see? When team conversations are switched on, a leader can ask their team three questions before their rounds in a short, anonymous conversation with an AI interviewer. You get an invitation in your Inbox and can take part once. Your leader never sees who said what: while it is open they see only how many people have taken part, and afterwards a readout of what several people said together. A topic fewer people than the anonymity floor spoke to is held back, and if too few people took part your leader sees only the count. You can take part even if you don't otherwise use Leader Rounds. ## When something looks wrong ## "Why can't I see my manager's notes from our round?" That's by design. A round has two layers: the shared one (the answers and any issues raised, which you can always see) and the leader's private notes, which are never shown to the person the round is about. If you can see the round but no notes, nothing is missing. ## "The issue I raised was closed without being fixed — why?" Sometimes the honest answer is no, and the app requires that honesty to be visible: closing an issue without a fix requires a written reason, which appears under your issue on Rounds About Me. The item shows red on the leader's ledger — it is not quietly hidden. ## "Why is my team missing from the Themes page?" Nobody on the team has answered a scale or yes/no question within the selected window — themes are built only from those answer types, so a team whose rounds carried free-text answers alone has nothing to aggregate yet. Widen the window filter or check that the team's rounds used templates with scale/yes-no questions. ## "Someone is missing from a leader's due list — where are they?" Four common causes: the person doesn't report to that leader in the org chart (the due list covers direct reports only), the person's account is deactivated (deactivated people never appear), they were rounded on within the cadence window and are simply listed as current rather than due, or a Rounding Program has put them on a longer cadence than you expected — the due list shows which program decided. ## "Why does a pillar row on the Stoplight Board show a light but no numbers?" Because fewer people than the anonymity floor are behind that row's issues. The light still shows — it is an aggregate — but the green/yellow/red counts are hidden, on the web page and in the published PDF, so a two-person pillar can't be read backwards to the individuals. Lowering the floor in Settings shows the counts; raising it hides more of them. ## "An AI theme I saw last week is gone — where did it go?" Two likely reasons. Raising the minimum group size in Settings hides every theme drawn from fewer people than the new floor, immediately and everywhere. Otherwise, a fresh extraction run has re-clustered the last 90 days of answers and the underlying answers have aged out of that window. A pillar you filed by hand is never moved by a later run. ## "Why did my manager get notified about an issue on my ledger?" Because it was still open and red past the escalation window — by default, seven days after its due date. That notifies your manager and re-nudges the issue's owner, and repeats weekly while the issue stays red. Closing an issue as won't-fix, with the written reason, is a decision rather than a delay, and never escalates. Admins control both the switch and the number of days in Settings. ## Licensing and limits ## What are the configurable ranges and limits? - Default rounding cadence: 1–365 days (default 30); Rounding Program and per-template cadences use the same range - Red-issue escalation: 1–90 days past due before the first escalation (default 7), then weekly while the issue stays red - Anonymity floor: your company's smallest group up to 25 people (default 5) — applies to the monthly team digest, single-team newsletter blocks, the AI theme list, Stoplight Board pillar rows, and team conversation readouts - Scale answers: 1–5 - Issue descriptions: up to 2,000 characters - Team Rollup window: 7–365 days (page filters at 30/60/90); Rounds Log uses the same windows and also allows all time - AI theme extraction: the last 90 days of written answers per run - Weekly reminder: at most one per leader per week, in-app - Upward delegation: one active delegation per leader at a time - Team conversations: open 1–14 days (default 7); one at a time per leader; each person takes part once - The AI assistant: 5 tools, all read-only — a sixth, for team conversations, while team conversations are switched on Licensing is per leader seat — the leaders who round — with admin opt-in per tenant; people being rounded on don't consume seats. **Keywords:** faq, leader rounds, rounding, due list, cadence, stoplight, issue ledger, themes, ai themes, pillars, stoplight board, rounding programs, pacing, delegation, escalation, anonymity floor, reminders, private notes, not showing, coverage, leader-rounds, leader_rounds --- # Leave Management App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 Set up and run time-off policies, accrual plans, blackout periods, and approval workflows for your organization. # Leave Management ## 1. What it is Leave Management runs the time-off lifecycle for your organization — from defining leave types and accrual policies through to employee requests, manager approvals, and balance tracking. Employees request full days, half days, or partial-day blocks; managers approve or deny in the app, on their phone, or in bulk; and balances update automatically as leave accrues and is used. - **Enablement:** Licensed and opt-in. An administrator enables it from **Admin → Apps → All Apps**, and it requires a licence. - **What it is not:** Leave Management does not handle shift scheduling or timesheets — those are the Shifts Scheduling and Timesheets apps. Company holidays are maintained per location and excluded from leave-hour math automatically; they are managed under **Administration → Holiday Management** in the Leave sidebar. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Leave Management**, and enable it. 2. Go to **Admin → Leave Configurations → Manage**. Create at least one leave type (e.g. Vacation, Sick Leave). Each type needs a name, a color, and an icon. You can load industry-standard defaults from the **Load Defaults** menu instead of building from scratch. 3. For each leave type that tracks balances, create an **accrual policy** and set the accrual frequency (daily, weekly, bi-weekly, monthly, quarterly, semi-annually, annually, per pay period, per hours worked, or custom), the per-period amount in hours, and optionally a maximum balance cap and carryover rules. 4. Assign employees to accrual policies — individually, by department or location filter, or with **Assign All**. A policy marked **Default for leave type** also covers every employee who has no explicit assignment. 5. If your organisation operates in multiple jurisdictions, open the **Availability** matrix under Leave Configurations and restrict specific leave types to the jurisdictions where they apply. Employees see only the types available in their work location. 6. Optionally configure **blackout periods** (Admin → Leave Configurations → Blackout Periods) and **coverage limits** (Admin → Leave Configurations → Coverage Limits) before the first requests come in. 7. Go to **Admin → Leave Configurations → Notifications** to review approval authority, notification channels, request options (partial-day leave, team availability), and AI Agent settings. Employees can now submit leave requests from the Leave Management app page, the mobile app, or Ask AI. Managers see pending requests in their manager dashboard and can decide from the app or follow the approval email straight to the request. **Silent-until-configured pairing:** an accrual policy with a blank accrual amount saves successfully but never accrues hours for anyone. Always set the per-period accrual amount when creating a policy. ## 3. How it fits together **Leave types** are the categories of time off your organisation offers — Vacation, Sick Leave, Personal Leave, Bereavement, and so on. Each type carries its own rules: whether it requires approval, whether it deducts from a balance, whether it allows a negative balance, the advance-notice window, the backdating window, and whether supporting documentation is required (and after how many days). New leave types default to active, approval required, balance-deducting, and accrual-enabled. **Accrual policies** govern how leave hours accumulate. A policy belongs to one leave type and accrues a fixed amount of hours on a schedule you choose. Policies support a waiting period for new hires, proration for mid-year starters, a maximum balance cap, and carryover rules (with an optional grace period and expiry). Accrual rules let you adjust the rate by tenure, role, location, or employment type — for example, adding hours for employees with more than five years of service. A leave type can have multiple policies; each employee is assigned to one (or falls back to the type's default policy). **Balances** track each employee's accrued, used, and available hours per leave type per year. All values are stored and displayed in hours (8 hours = 1 day). The balance is derived — it equals accrued minus used — and updates automatically when leave accrues, when requests are approved or cancelled, and when an admin adjusts hours manually. **Requests and approvals** — employees submit requests for full days, half days (morning or afternoon), or partial days (a specific time window in 30-minute increments, when enabled). Requests that fall within a blackout period, inside the advance-notice window, or at a coverage limit are routed to **special approval** rather than being rejected outright, so a manager can make the call. Statuses are: Pending approval, Special approval, Approved, Denied, and Cancelled. By default a manager approves leave for everyone at the locations they manage (or, if the company chooses, only their own reporting line), and admins can approve any request. Managers can delegate their approval authority while out of the office to a colleague who can approve leave — another manager, a leave administrator, a designated leave approver, or someone whose role approves leave. **Blackout periods vs coverage limits** — these are easy to confuse. A blackout period is a date range during which new requests of specified leave types are either blocked entirely or routed to special approval. A coverage limit sets the maximum number (or percentage) of people who may be off at the same time, optionally scoped to a location (each location is counted on its own), with an optional separate weekend threshold. Blackouts prevent leave during a specific window (e.g. year-end freeze). Coverage limits prevent too many people from being off at once. Both can coexist. ## 4. Running it ### Reviewing and approving requests 1. Go to **My Team → Team Requests** in the Leave sidebar and open **Needs Action** to see the requests waiting on you. 2. Select a request to see the employee's balance, pending hours, and any coverage or blackout flags. 3. Approve or deny individually, or select multiple requests and use **Bulk Approve** / **Bulk Deny**. The approval email links straight to the request; the decision itself is made in the app, where the balance and any shift conflicts are in view. ### Adjusting an employee's balance 1. Go to **Admin → Leave Balances**, find the employee, and open their balance for a leave type. 2. Use **Adjust Accrued Hours** or **Add Manual Usage** to correct the balance. Each adjustment is logged as a transaction in the accrual history. 3. To recalculate all balances from the ledger (approved requests + accrual transactions), use **Recalculate All** — this runs as a background task. ### Managing blackout periods 1. Go to **Admin → Leave Configurations → Blackout Periods** and create a period with a name, date range, and whether it should block requests or route them to special approval. 2. Optionally scope the blackout to specific leave types and/or locations. ### Importing and exporting - **Leave types** can be exported to CSV and imported from CSV under **Admin → Leave Configurations → Manage**. - **Leave balances** can be imported and exported (CSV or SFTP) under **Admin → Leave Balances → Import/Export**. - **Leave requests** can be imported under **Admin → Leave Requests → Import** for historical backfill — imported requests skip blackout, coverage, and backdating validations. ### Running accruals manually Go to **Admin → Leave Configurations → Manage → Accrual Policies** and click **Run Accruals**. This processes accruals for all active employees as a background task and notifies you when complete. ## 5. Settings Settings are configured at **Admin → Leave Configurations → Notifications** unless noted otherwise. | Setting | Default | What it changes | |---|---|---| | AI Agent Enabled | On | Whether the Ask AI agent can answer leave questions and take actions for employees and managers. | | Auto-approve leave requests up to this many days | 3 | When autonomous actions are enabled, the AI agent can auto-approve requests of this length or shorter. | | Allow partial-day leave requests | Off | Whether employees can request a specific time window (e.g. 9:00 AM – 1:00 PM) instead of a full or half day. | | Show "who's out" while picking dates | On | Whether the leave request form shows teammates who are already off on the selected dates. | | Managers approve leave for | Everyone at the locations they manage | Whether a manager approves leave for everyone at their locations or only for their own reporting line. | | Who can approve leave | Managers and admins | Optionally adds a designated approver group who can approve any request, on top of managers and admins. | Per-leave-type settings are configured on each leave type under **Admin → Leave Configurations → Manage**: | Setting | Default | What it changes | |---|---|---| | Requires Approval | On | Whether requests of this type need manager sign-off. | | Deduct From Balance | On | Whether approved leave reduces the employee's accrued balance. | | Allow Negative Balance | Off | Off: hours the balance can't cover are recorded as unpaid leave. On: the whole request is taken as paid time off and the balance goes below zero. | | Accrual Enabled | On | Whether a balance is tracked and accrued for this type. | | Advance Notice (days) | 7 | Requests submitted with less notice are routed to special approval instead of rejected. | | Backdating Window (days) | 14 | How far into the past an employee can file a request (e.g. logging a sick day after the fact). | | Documentation Required | Off | Whether supporting documents (e.g. a medical certificate) are required. | | Documentation Threshold (days) | 3 | Documentation is required only for requests of this many days or longer. | ## 6. More help - **Leave Management FAQ** — specific setup, operating, and troubleshooting questions. - Ask AI — the assistant answers leave balance, policy, and request questions from these articles. **Keywords:** leave management, time off, PTO, leave request, leave balance, accrual policy, blackout period, leave approval, coverage limit, half day, partial day, carryover, leave type, sick leave, vacation, leave-management, leave_management --- # Leave Management FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Leave Management — for the admin running it. # Leave Management FAQ Answers to common setup and operating questions about Leave Management. For what the app is and how to set it up from scratch, see the [Leave Management Overview](/help/articles/leave_management_app_overview). --- ## Setup ## Do I need to create accrual policies before employees can submit requests? Not necessarily. An employee can submit a request against any active leave type, but without an accrual policy the type carries no balance — so there is nothing to deduct from. If a leave type has **Deduct From Balance** turned on (the default) and no policy is assigned, the employee's available balance is zero and the shortfall is recorded as unpaid hours. Create at least one accrual policy per balance-tracking leave type and assign employees to it before opening requests. ## What happens if I save an accrual policy with a blank accrual amount? The policy saves successfully with an amount of zero, but it never accrues hours for anyone. Always set the per-period accrual amount when creating a policy. ## Which leave types do employees see? Employees see only the leave types that are active and available in their work location. If you have configured the **Availability** matrix under **Admin → Leave Configurations**, each type is restricted to the jurisdictions where it applies. Employees outside those jurisdictions do not see the type in their request form. Deactivating a type hides it from new requests but does not affect existing ones. --- ## Permissions and access ## Who can approve leave requests? By default, a manager approves leave for everyone at the locations they manage — or only for their own reporting line, if the company chooses that under **Managers approve leave for** — and administrators can approve any request. A Leave app administrator approves only if their own role approves leave. You can additionally configure a **designated approver group** at **Admin → Leave Configurations → Notifications** under **Who can approve leave**. Designated approvers are layered on top of the manager chain — they never replace it — and they can approve requests for any employee in the business. ## Can a manager delegate their approvals while they are out of the office? Yes. A manager can delegate leave approvals to a colleague for a date range of up to **180 days**. The colleague must be someone who can approve leave themselves — a manager, a leave administrator, a designated leave approver, or someone whose role approves leave — and the **Delegate to** list on My Team › Approval Delegation offers only those people. While the delegation is active, the delegate inherits the delegator's approval authority. The delegator keeps their own access, delegation does not chain (a delegate cannot re-delegate), and a delegate can never approve their own requests. --- ## Day-to-day ## Can employees request half-day or partial-day leave? Half-day leave (morning or afternoon) is always available. An employee can also book a morning half-day and an afternoon half-day on the same date — the system treats them as non-overlapping. Partial-day leave (a specific time window in 30-minute increments on a single day) is a separate setting. It is **off by default** and can be enabled at **Admin → Leave Configurations → Notifications → Allow partial-day leave requests**. When enabled, employees pick a start and end time; the minimum window is 30 minutes and times must land on a 30-minute boundary. Multiple partial-day requests on the same date are allowed as long as their time windows do not overlap. ## How far back can an employee file a leave request? Each leave type has a **Backdating Window** setting (default **14 days**). An employee can log a past absence — for example, a sick day — as long as the start date is within that window. Requests further in the past are rejected. Admins importing historical leave via the import path bypass the backdating limit. ## What happens when an employee submits a request and their balance is insufficient? The request is still created. The shortfall is recorded as unpaid hours — the funded portion comes from the accrued balance and the remainder is marked as unpaid leave. The employee is told about the split at submission and the approver sees it when reviewing the request. If the leave type has **Allow Negative Balance** turned on, the full amount is deducted regardless of the balance. ## Can an employee cancel or edit their own request? An employee can **cancel** a pending or special-approval request at any time, or an approved request whose start date has not yet arrived. Once the leave has started, only a manager or admin can cancel it. An employee can **edit** a pending, special-approval, or approved request only while the start date is still in the future and the overlapping schedule period is still open. If an employee changes the dates, leave type or hours of a request that is already approved, it goes back for approval: the balance is restored, the approvers are asked again, and approving it debits the balance for the new request and takes the employee off the shifts on its new dates. Shifts they were already taken off for the earlier dates are not put back automatically. Changing only the reason keeps it approved. When a manager or admin who can approve the request makes the change, it stays approved and the balance is reconciled — shortening a five-day approved request to three days returns the difference. ## What is the maximum date span for a single leave request? A single request can span up to **731 days** (two years). Requests beyond that limit are rejected with a field error. --- ## Blackouts, coverage, and special approval ## What is the difference between a blackout period and a coverage limit? A **blackout period** is a date range during which new requests for specified leave types are either blocked outright or routed to special approval — for example, a year-end freeze. A **coverage limit** caps how many employees may be off at the same time, optionally scoped to a location (each location is counted on its own), with an optional separate weekend threshold. Both can coexist on the same dates. ## What does "special approval" mean? A request is routed to **special approval** instead of normal pending status when it triggers one of three rules: 1. **Blackout period** — the dates overlap a blackout configured to route rather than block. 2. **Advance notice** — the request was submitted inside the leave type's advance-notice window (default **7 days**). 3. **Coverage limit** — the dates hit a soft coverage limit. The request appears in the manager's approval queue with the reason displayed. The manager can approve or deny it like any other request. ## Does a hard coverage limit block approvals too? Hard coverage limits block **new filings** — if a date is already at the cap, the employee cannot submit a request for it. Once a request is filed (including one that was filed before the limit existed), the approver can still approve it. This prevents deadlocks where two pending requests block each other permanently. --- ## When something looks wrong ## "My employee says they can't see a leave type that other employees can." The most common cause is the **Availability** matrix. If the leave type is restricted to certain jurisdictions under **Admin → Leave Configurations → Manage**, employees whose work location falls outside those jurisdictions will not see it. Check the employee's primary location and the type's jurisdiction settings. ## "An employee submitted a request and the manager never got notified." Check the notification settings at **Admin → Leave Configurations → Notifications**. Each action (request submitted, approved, denied, etc.) has its own toggle for who is notified and over which channels (in-app and/or email). If the manager is on leave, check whether skip-level routing or an active delegation is in place — the notification goes to whoever has approval authority at that moment. ## "An approved request shows a balance the employee no longer has." The balance snapshot on a request is captured at the time the request was created, not when it is viewed. To see the employee's current balance, go to **Admin → Leave Balances** and find the employee. If the balance looks wrong, use **Recalculate All** to rebuild it from the ledger (all accrual transactions and approved requests). --- ## Accruals, carryover, and expiry ## What accrual frequencies are available? Ten: **Pay Period**, **Daily**, **Weekly**, **Bi-weekly**, **Monthly**, **Quarterly**, **Semi-annually**, **Annually**, **Hours Worked**, and **Custom**. Each policy accrues a fixed number of hours at the chosen frequency. For **Hours Worked**, you also set how many hours worked earn one accrual unit. ## How do carryover, grace periods, and expiry work? Each accrual policy controls these independently: 1. **Carryover** — enabled by default. An optional **maximum carryover cap** limits how many hours roll into the new year. 2. **Grace period** — a number of months after year-end during which carried-over hours are still usable before expiry rules kick in. 3. **Expiry** — hours that exceed the carryover cap or pass the expiry date are either **forfeited** or **paid out**, according to the policy's expiry action. Consumption is FIFO, so only genuinely unused hours are affected. Balance alerts warn employees and managers before hours are at risk. The alert types are: **Approaching Maximum Balance** (triggered at 80% of the cap by default), **Balance Expiring Soon** (triggered 30 days before expiry by default), **Year-End Forfeiture Risk**, and **Balance Below Minimum**. --- ## Licensing and limits ## Does Leave Management require a licence? Yes. An administrator enables it from **Admin → Apps → All Apps** and it requires a licence. It is not auto-enabled — each tenant opts in. ## Are there limits I should know about? | What | Limit | |---|---| | Maximum request span | 731 days | | Notes and denial reasons | 2,000 characters | | Accrual policy waiting period | Up to 3,650 days (10 years) | | Approval delegation window | Up to 180 days per delegation | | Partial-day minimum window | 30 minutes, on 30-minute boundaries | | Balance unit | Hours (8 hours = 1 day) | | Custom hours minimum | 0.5 hours | --- ## More help - [Leave Management Overview](/help/articles/leave_management_app_overview) - Ask AI — the assistant answers leave balance, policy, and request questions from these articles. **Keywords:** faq, leave management, time off, PTO, leave balance, accrual policy, blackout period, coverage limit, half day, partial day, carryover, leave type, approval, negative balance, not showing, can't cancel, delegation, leave-management, leave_management --- # Levels & Badges App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How Levels & Badges awards XP for everyday work, organizes progress into tiers and badges, and surfaces leaderboards — with setup steps and settings. # Levels & Badges ## 1. What it is Levels & Badges is a gamification app that awards experience points (XP) when employees complete everyday work — finishing a shift on time, passing a quiz, submitting an idea, completing a task, and more. XP accumulates into levels and unlocks badges, and leaderboards let people and teams see where they stand. XP — shown in the app as points — is a progress score, not money; it is never spent. Company Store points are separate. - **Enablement:** Levels & Badges requires a license and is disabled by default. A company admin enables it from **Admin → Apps → All Apps**, then publishes it to users. Until it is published, only admins (and anyone given an app role for it) can open it. - **What it is not:** Levels & Badges does not create its own activity stream. It reads completion records that other apps already produce (Time & Attendance, Training, Tasks, Inspections, and others). There is nothing to connect or import. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Levels & Badges**, and enable it. 2. Open **Apps → Levels & Badges → Settings** (the Admin dropdown in the sidebar). Review the default settings — all ten badge categories are active and leaderboards are on. Adjust any you want to change before employees start seeing progress. 3. Confirm that the apps whose work you want to reward are also enabled. XP is only awarded for actions whose source app is enabled for your business. For example, if Training is not enabled, course completions and quiz passes earn no XP. The tracked apps are: Time & Attendance, Shift Marketplace, Tasks, Inspections, Safety Hub, Training, Surveys, Ideas, Ballots, Recognitions, Contests, and Calendar (checking in at a company event). The Engagement actions — logging in, reading, posting, commenting, reacting, and watching videos — count wherever they happen in the platform. 4. Publish it. A newly enabled app is admin-only: employees earn XP from the moment it is enabled, but they cannot open the app or see their progress until a company admin goes to **Admin → Apps → All Apps → Levels & Badges** and clicks **Publish to users**. To give it to some people only, publish it to specific groups from the same page. Only company admins can open that page — a Levels & Badges app admin cannot publish the app or change who has it. 5. Verify it works: perform a tracked action (complete a task, submit an idea) and open **Apps → Levels & Badges**. Within a few seconds the My Progress tab should show the XP award and your updated level. Badge definitions are seeded automatically the first time an admin opens the **Manage badges** tab. There is nothing to create before employees can start earning. ## 3. How it fits together ### XP and the action catalog Every XP-worthy action belongs to one of ten badge categories: **Reliability**, **Shift Hero**, **Execution**, **Safety**, **Learner**, **Quiz Whiz**, **Voice**, **Team Player**, **Contests**, and **Engagement**. Each action awards a fixed number of points. Some examples: | Action | Points | Category | |---|---|---| | Shift completed on time | 20 | Reliability | | Shift completed late, or one that can't be timed (ad-hoc or unscheduled, or no clock-in) | 8 | Reliability | | Open shift picked up | 25 | Shift Hero | | Task completed | 10 | Execution | | Safety inspection completed | 15 | Safety | | Training course completed | 30 | Learner | | Quiz passed | 20 | Quiz Whiz | | Recognition given | 5 | Team Player | | Recognition received | 15 | Team Player | | Idea submitted | 15 | Voice | | Daily log-in | 5 | Engagement | Some actions carry daily caps to prevent gaming. Task completions, for instance, award XP for the first 10 per day; recognitions received cap at 10; safety observations at 5; recognition given at 3; company event check-ins at 2. Uncapped actions (shift completions, course completions) award once per source record and can never double-count. Engagement actions — log-ins, reactions, comments, posts, reading content, watching videos — are deliberately low-value with tight daily caps. They are a tiebreaker on top of real work, not a reason to open the app. The Engagement category is on by default; a company that finds these actions inappropriate can turn the whole category off in settings. Point values are fixed: every action is worth the same in every company, and they cannot be changed. What admins control is which categories are active (**Settings → Active Badge Categories**) and each badge's threshold (**Manage badges**). ### Levels and tiers XP accumulates into 60 levels. The cost to advance increases in bands — leaving level 1 costs 50 XP, levels 22–25 cost 250 each, and the last level-ups (from level 55 up to 60) cost 425 each, so reaching Level 60 takes 16,075 XP in all. The curve is the same in every company and cannot be changed. Progress is presented as five named tiers; an employee's own level number appears only as a detail under their tier on My Progress (and on their manager's Team view), and the leaderboards and weekly digest show other people's tier and points, never their level number: | Tier | Levels | XP to reach | Icon | |---|---|---|---| | Rookie | 1–9 | 0 | Seedling | | Contributor | 10–21 | 750 | Person | | Pro | 22–37 | 2,850 | Star | | Veteran | 38–53 | 7,450 | Shield | | Master | 54–60 | 13,550 | Crown | A new employee starts at Level 1 (Rookie, 0 XP). As an example: after 10 on-time shifts (200 XP), 5 completed tasks (50 XP), and 1 training course (30 XP), they would have 280 XP — Level 5, still in the Rookie tier. At 750 cumulative XP they reach Level 10 and become a Contributor. Notifications fire on tier promotions, not on every level-up — employees are told "You reached Contributor!", not "You reached Level 10." The one exception is money: if your company pays Company Store points for level-ups, a level-up that pays sends a Company Store notice ("You earned 50 points!") to employees who can open the store. ### Badges Badges are earned when a running counter crosses a threshold. The built-in catalog has 45 badges across the ten categories, each line with escalating tiers. Six of them are earned only through the Contests app: the four Contests badges, plus **Show & Tell** and **Documentarian**, which count photos submitted to contests. For example, the Reliability badge line awards **Punctual** at 10 on-time shifts, **Dependable** at 50, **Always-On** at 100, and **Ironclad** at 250. The Learner line awards **Apprentice** at 1 course completed, **Trainee** at 5, **Star Student** at 10, and **Scholar** at 20. A badge is awarded once and never revoked. If an admin later raises the threshold, people who already earned it keep it. Admins can customize every built-in badge — rename it, change its icon, raise or lower the threshold, or disable it — from the **Manage badges** tab. When a threshold is lowered or a badge is re-enabled, everyone who already qualifies is awarded automatically via a background backfill. Admins can also create entirely custom badges within any category, choosing which tracked metric the badge evaluates against. Built-in badges can be disabled but not deleted. Custom badges can be deleted. Use **Reset** to restore a built-in badge to its original name, icon, threshold, and unlock message. ### Streaks Two categories track consecutive streaks alongside their cumulative counters. An on-time attendance streak increments with each on-time shift and resets to zero on a late arrival. A shift that can't be timed — an ad-hoc or unscheduled shift, or one with no clock-in — earns its 8 XP but counts toward neither the on-time badges nor the streak, and leaves the streak where it was. A login streak increments each day the employee opens the app and resets overnight if they miss a day. Streak badges — such as **Perfect Week** (5 on-time shifts in a row) and **Five in a Row** (5 consecutive active days) — reward consistency rather than volume. ### Leaderboards Leaderboards rank employees by XP across several scopes: - **Company-wide** — everyone in the business. - **Location** — the employee's assigned site(s). - **District / Region / Market** — a roll-up of every site beneath a parent node in the location tree. - **Job title** — employees with the same role (e.g. painters ranked against other painters). Each scope has a **monthly** board (current calendar month) and an **all-time** board. Boards refresh every night at 00:20 UTC; a newly enabled company shows live data until the first refresh runs. Departed employees are removed from boards automatically. Every employee sees a top-10 list, a "catch them" indicator showing the person directly ahead, and their own rank once they have earned XP in that period — someone with no XP in the period has no row on that board yet. Boards name everyone who has earned XP in the period; there is no per-person opt-out. ### Integrations with other apps **Company Store bridge (optional).** By default, XP is a status signal only — it has no monetary value. Admins can opt in to convert level-ups into Company Store points by setting both **Company Store Points per Level-Up** and **Monthly Store-Points Budget from Level-Ups** to values above zero in Settings. Both must be funded for the bridge to activate. A hard monthly cap prevents runaway spend. The Company Store app must also be enabled. **Contests.** The Contests app scores metric-based competitions directly from the Levels & Badges activity ledger. A contest whose prize is a badge puts that badge on the winner's badge wall, alongside their regular earned badges, while the Contests badge category is active. ## 4. Running it ### Reviewing analytics Go to **Apps → Levels & Badges → Admin → Analytics**. The page shows total participants, total XP awarded, badges earned, a tier distribution chart, and the top-10 leaderboard. All figures count only currently active employees. ### Managing badges Go to **Apps → Levels & Badges → Admin → Manage badges**. Badges are grouped by category. Select a badge to edit its name, icon, threshold, or unlock message. Use **Reset** to restore a built-in badge to its shipped default (reset does not re-enable a disabled badge). Use the **Add badge** button within a category to create a custom badge. ### Viewing the Team tab (managers) Any employee with direct reports sees a **Team** tab. It shows a roster of their reports with each person's level, total XP, this-month XP, and badge count, plus the same tier-distribution chart the admin analytics page shows — scoped to their team. ### Reviewing the weekly digest When the **Send Weekly Leaderboard Digest** setting is turned on, company administrators receive a weekly email, every Monday at 14:00 UTC, showing the month's top performers. The digest is off by default. ### Who sees what - **Everyone the app is published to** sees the My Progress tab (their own XP, level, tier, recent badges, recent activity) and the Badges catalog. - **Everyone the app is published to** sees the Leaderboard tab when leaderboards are enabled. - **Managers** (anyone with direct reports) additionally see a Team tab with their reports' progress. - **Admins and app admins** additionally see Analytics, Manage badges, and Settings under the Admin dropdown. ## 5. Settings All settings are at **Apps → Levels & Badges → Settings** (admin only). | Setting | Default | What it changes | |---|---|---| | Enable Leaderboards | On | Shows or hides the Leaderboard tab for all employees. | | Leaderboard Scope | **All** | Which board types appear: Company-wide, Location, Job title, or all of them. | | Send badge and tier-promotion notifications | On | Sends an in-app notification when an employee who can open the app reaches a new tier or earns a badge. It also goes to their phone only if they have turned on push for **Recognition** in their notification settings. These notices are never emailed. | | Send Weekly Leaderboard Digest | Off | Emails this month's top 10 to company administrators every Monday at 14:00 UTC. | | Active Badge Categories | All ten on | Controls which categories award XP and badges. Disabling a category stops all awards for its actions — the hooks still fire but XP is not recorded. At least one category must remain active. | | Site engagement target (%) | 80 | Threshold below which a manager is alerted that a site's trailing 30-day participation has dropped. Set to 0 to disable. | | Show individual activity in the Engagement report | Off | When on, the Engagement report includes per-person activity alongside the site and role totals. Off by default for privacy reasons. The Engagement report is open to admins and Engagement Champions only. | | Company Store Points per Level-Up | 0 (off) | Points granted to the employee's Company Store balance on each level-up. Both this and the monthly budget must be above zero. | | Monthly Store-Points Budget from Level-Ups | 0 (unfunded) | Hard monthly cap on the total store points the level-up bridge can issue across all employees. | ## 6. More help - **Levels & Badges FAQ** — specific setup and operating questions, limits, and troubleshooting. - Ask AI — the assistant answers questions about Levels & Badges from these articles. **Keywords:** levels and badges, gamification, XP, experience points, leaderboard, badges, tiers, engagement, levels, points, levels-badges, levels_badges, levels-&-badges --- # Levels & Badges FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Levels & Badges — for the admin running it. # Levels & Badges FAQ Answers to common setup and operating questions about Levels & Badges. For what the app is and how to set it up from scratch, see the [Levels & Badges Overview](/help/articles/levels_badges_app_overview). XP — shown in the app as points — is a progress score, not money; it is never spent. Company Store points are separate. --- ## Setup ## Do I need to configure anything before XP starts being earned? No. Once the app is enabled and licensed for your business, all ten badge categories are active by default and XP begins accumulating immediately. The one decision to make up front is whether to leave all categories on or turn some off under **Settings > Active badge categories**. One step remains before employees can see any of it: publishing. A newly enabled app is admin-only until a company admin goes to **Admin → Apps → All Apps → Levels & Badges** and clicks **Publish to users** (or publishes it to specific groups). XP earned before then is kept. ## Who sees what once the app is published? Everyone the app is published to sees **My Progress** (their own level, tier, XP, and badges) and the **Badges** catalog. The **Leaderboard** tab is visible to everyone when the **Enable leaderboards** toggle is on (on by default). Managers with at least one direct report also see a **Team** tab showing each report's level, XP, and badge count. The **Admin** menu (Analytics, Manage badges, Settings) is visible only to company admins and designated app admins. --- ## Permissions and access ## Can I delegate Levels & Badges administration without making someone a full admin? Yes. Anyone designated as an app admin for Levels & Badges gets the same Admin menu — Analytics, Manage badges, and Settings — without any other admin privileges. Publishing the app, and choosing which groups have it, stays with company admins: that is done on **Admin → Apps → All Apps**, which an app admin cannot open. --- ## Day-to-day ## What's the difference between Levels & Badges and Recognitions? Recognitions points carry real value and are redeemable in the Company Store. Levels & Badges XP is a status signal by default — not spendable. The two are separate systems; giving or receiving a recognition is simply one of many activities that can earn XP. You can optionally turn on the Company Store points bridge so that level-ups also mint store points, but even then the two pools stay distinct. ## What work earns XP, and can I choose which behaviors count? Activities that earn XP span ten categories: on-time attendance and shift completion (**Reliability**), picking up open shifts and completing swaps (**Shift Hero**), finishing tasks and checklists (**Execution**), safety inspections and observations (**Safety**), completing courses (**Learner**), passing quizzes (**Quiz Whiz**), completing surveys, submitting ideas, and casting ballot votes (**Voice**), giving or receiving recognition (**Team Player**), participating in or winning contests (**Contests**), and platform engagement such as logging in, reading content, commenting, and posting (**Engagement**). Each category can be toggled on or off under **Settings > Active badge categories**. Disabling a category stops all XP and badge awards for those activities immediately. ## How do levels and tiers work? XP accumulates across a 60-level curve. Each rewarded action adds XP, and the running total determines your level. Because "Level 47 of 60" means little to a frontline worker, levels roll up into five named career tiers: **Rookie** (levels 1–9), **Contributor** (10–21), **Pro** (22–37), **Veteran** (38–53), and **Master** (54–60). Tiers lead: employees see their tier name and a progress bar toward the next tier, with their own level and all-time points shown as a detail beneath it on My Progress — the same figures their manager sees on the Team view. The leaderboards and the weekly digest show other people's tier and points, never their level number. The XP required per level increases as you advance: leaving level 1 costs 50 XP, and the last level-ups (from level 55 up to 60) cost 425 each. 280 XP is Level 5; 750 XP reaches Level 10 and the Contributor tier; 16,075 XP reaches Level 60. The curve and the XP each action is worth are the same in every company and cannot be changed. ## How do the leaderboards work? There are monthly and all-time leaderboards. The monthly board resets at the start of each calendar month in your business's timezone. Each board shows top performers, the person directly ahead of the viewer as a "chase target," and the viewer's own rank once they have earned XP in that period — someone with no XP in the period has no row on that board yet. The bottom of the board is never exposed. Boards name everyone who has earned XP in the period; there is no per-person opt-out. Under **Settings > Leaderboard scope** you choose from four options: **Everything** (company, location, market, and job title — the default), **Company-wide only**, **By location and market only**, or **By job title only**. Rankings refresh from a nightly snapshot (00:20 UTC), with a live fallback so a newly enabled company sees data right away. ## Can I customize badges — rename them, change thresholds, or create new ones? Yes. From **Admin > Manage badges**, you can rename any badge (up to 80 characters), change its icon, adjust the threshold to earn it (minimum 1), and edit its unlock message (up to 280 characters). You can also enable or disable individual badges. Any built-in badge can be reset to its default at any time. You can create entirely new custom badges within any existing category. Built-in badges cannot be deleted, but custom badges can. ## How does the Company Store points bridge work? By default, XP is a status signal with no monetary value. To convert level-ups into spendable points, set both **Store points per level-up** and **Monthly store-points budget** to a value above zero under **Settings > Company Store points**. This is a double opt-in — nothing is minted unless both values are set above zero. The monthly budget is a hard ceiling: once what is left for the month cannot cover another level-up, further level-ups are held — not lost — and paid as the budget allows on a later award. Settings shows how much of this month's budget level-ups have minted. The Company Store app must also be enabled for your business. Each level is paid at most once. Employees who can open the Company Store are told when a level-up pays them points, and My Progress shows them any reward that is held. ## What notifications do employees receive? When **Send badge and tier-promotion notifications** is on (the default), employees who can open the app get an in-app notification on tier promotions and badge unlocks. It also goes to their phone only if they have turned on push for **Recognition** in their notification settings; these notices are never emailed. Notifications fire only when someone moves to a new tier, not on every individual level-up, so pings stay meaningful. Separately, when the Company Store points bridge is on, a level-up that pays points sends a Company Store notice ("You earned 50 points!") to employees who can open the Company Store, governed by their own Company Store notification preference. A separate **Send weekly leaderboard digest email** toggle (off by default) sends the current month's top 10 performers to active company administrators every Monday at 14:00 UTC. --- ## When something looks wrong ## "I completed a shift on time but didn't get any XP" The most common cause is that the **Reliability** category is turned off under **Settings > Active badge categories**. Also verify the app is enabled and licensed for your business. XP is awarded after the shift ends, not during — the award runs in the background and may take a moment to appear. If the employee clocked in after the shift's start time plus the configured grace period, the shift counts as late, which earns fewer XP (8 instead of 20) and resets any on-time streak. A shift that can't be timed — an ad-hoc or unscheduled shift, or one with no clock-in — also earns 8 XP; it is not counted as on time or late, so it does not move the on-time streak or the on-time badges. ## "I gave someone a recognition but didn't earn any XP for it" Three things to check. First, self-recognition is excluded — if someone recognized themselves, neither the "given" nor the "received" XP is awarded. Second, only the first 3 recognitions given per day earn XP (a daily cap to prevent gaming); on the receiving side, the first 10 recognitions received per day earn XP. Third, the **Team Player** category must be enabled under Settings. ## My leaderboard rank hasn't changed even though I earned XP today Leaderboard rankings refresh from a nightly snapshot at 00:20 UTC. XP earned today will appear on the leaderboard tomorrow. When a company first enables the app, a live fallback shows data immediately, but once snapshots exist the board reflects the previous night's standings. ## I lowered a badge threshold but nobody who already qualifies received the badge When you lower a badge's threshold or re-enable a disabled badge, a background job runs to award the badge to everyone who already qualifies. This job processes asynchronously and may take a few minutes. If qualifying users still haven't received the badge after several minutes, check that the badge's category is enabled under Settings. --- ## Licensing and limits ## Does Levels & Badges require a licence? Yes. It requires a licence and is enabled per company by a company admin through Admin → Apps → All Apps. It is not enabled by default, and once enabled it is admin-only until that admin clicks **Publish to users** on the app's page there. ## What happens to existing XP and badges if I disable the app? All existing data — XP events, levels, badges, and leaderboard standings — is preserved. No new XP is awarded while the app is disabled, and the Levels & Badges tabs are hidden from employees. When you re-enable the app, everything resumes from where it left off. XP is append-only and is never clawed back. ## What are the limits I should know about? | Item | Value | |---|---| | Maximum level | 60 | | Career tiers | 5 (Rookie, Contributor, Pro, Veteran, Master) | | Built-in badges | 45 across 10 categories (6 of them need Contests) | | Badge name length | 80 characters | | Unlock message length | 280 characters | | Badge threshold minimum | 1 | | Daily cap — tasks completed | 10 | | Daily cap — safety observations | 5 | | Daily cap — ideas submitted | 3 | | Daily cap — ballot votes | 5 | | Daily cap — recognitions given | 3 | | Daily cap — recognitions received | 10 | | Daily cap — daily login | 1 | | Daily cap — content reads | 5 | | Daily cap — posts created | 3 | | Daily cap — reactions | 5 | | Daily cap — comments | 3 | | Daily cap — videos watched | 3 | | Daily cap — media submitted | 2 | | Daily cap — company events attended | 2 | | Weekly digest recipients | Up to 25 admins per business | | Site engagement target default | 80% | --- ## More help - [Levels & Badges Overview](/help/articles/levels_badges_app_overview) - Ask AI — the assistant answers Levels & Badges questions from these articles. **Keywords:** faq, XP, badges, levels, leaderboard, tiers, gamification, not earning XP, badge threshold, store points, daily cap, levels-badges, levels_badges, levels-&-badges --- # Libraries App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run the Libraries app — curate company resources, forms, links, and internal records into targeted, permission-controlled collections. # Libraries ## 1. What it is Libraries lets you organize company resources into curated collections that different groups of people can browse and search. A collection can hold external links, uploaded files, images, and videos — and it can also point directly at an internal form or wiki page, so the resource opens where it already lives instead of being copied. Each library is targeted at an audience rather than published to everyone, and it is searchable across everything a person is allowed to see. - **Enablement:** Libraries is a licensed app and is off until an admin turns it on for the tenant from Admin → Apps → All Apps. - **What it is not:** it is not a file store like Drive. A library mostly curates *pointers* — a link, or a live internal record — though an item can also carry an uploaded document, image, or video. When an item points at a record that is later archived or deleted, the item shows as unavailable rather than linking into a dead end. ## 2. Standing it up 1. Turn the app on. In Admin → Apps → All Apps, enable **Libraries** for your tenant (it requires a license). 2. Go to **Libraries → All Libraries** and choose **New library**. Give it a name, then set two separate access decisions: - **Visibility** — *All Users*, or *Specific Audiences* (users, groups, departments). - **Who can add or remove items?** — *Everyone*, *Admins and specific users*, or *Admins only*. 3. If you chose **Specific Audiences**, add one or more audience rules. Each rule targets a department, location, group, job family, job title, organizational role, platform role, or a named individual. A rule grants *sight only* — it carries no curation role of its own. Who may add or remove items is a separate list of named people (see step 5). 4. Add **categories** to the library, then add **items** to each category. When you add a form or wiki item, a picker offers only records that are actually reachable — a draft wiki page or an archived form never appears. 5. If anyone besides an administrator should curate the library, name them individually and give each one **Contributor** (adds, edits, and removes items when **Who can add or remove items?** is *Admins and specific users*) or **Manager** (renames the library and organizes its categories at every level, plus items under *Admins and specific users*). Who the library reaches — Visibility, its audience rules and **Who can add or remove items?** — stays with Libraries administrators and the person who created the library; a Manager sees those settings read-only. 6. Confirm it worked: a member of the target audience should now see the library under All Libraries, be able to open its items, and find its contents in search. **The pairing that catches people out:** audience rules only take effect when a library's **Visibility** is *Specific Audiences*. Adding rules to an *All Users* library changes nothing. Likewise, choosing **Admins and specific users** for item management grants curation to no one until you also name the individual people who should have it — an audience rule never grants it, however the rule is targeted. ## 3. How it fits together **Library → Category → Item.** A library is a collection; categories group items inside it; an item is a single resource. For example, a **Company Policies** library might contain a **Time Off** category holding a *PTO Policy* item (linked to a wiki page) and a *Request Time Off* item (linked to a form). **Item types.** An item is one of: a simple link, a file (a link to a document or an uploaded document), a form, a wiki page, an image, or a video. (Survey and post items made before those choices were retired still open and edit.) The form and wiki types point at a live internal record, so the library reflects that record's real state — a page moved back to draft shows as inactive rather than as a working link. **Two access questions people conflate.** These are set separately on every library and answer different things: - **Visibility** — *who can see the library at all.* Governed by the library's audience rules when set to Specific Audiences. - **Who can add or remove items?** — *who can curate its contents.* This is the library's management level, and it is independent of who can see it. There is also a third, quieter level — **administering the library itself**. Renaming it and organizing its categories is for Libraries administrators, the person who created the library, and anyone named as a **Manager**; changing who it reaches (Visibility, the audience rules, and **Who can add or remove items?**) is for Libraries administrators and the creator only. Deleting or disabling a library is narrower still: a platform admin or a Libraries app admin only — including a Libraries admin limited to places and departments, for the libraries in their reach. **How each is granted.** Sight and curation come from two different lists, and this is the distinction most worth learning: - **Audience rules grant sight.** Anyone a rule matches can open the library. A rule carries no role beyond that, whatever it targets — so no group, department, or platform-role rule can make someone a curator. - **Named memberships grant curation.** You name individual people, each as a **Contributor** (add, edit, and remove items) or a **Manager** (that, plus renaming the library and organizing its categories). There is no *Viewer* membership — viewing is the audience's job. The management level decides who those curators are allowed to be: under *Admins and specific users* it is the named contributors and managers; under *Everyone* it is anybody who can see the library; under *Admins only* it is administrators alone. A **Manager** keeps library administration at every level — the management level governs items, not the library record. **Disabled is not deleted.** Disabling a library hides it from everyone except admins and the people who manage it, and excludes it from search, while keeping all of its content — useful while you reorganize it. Deleting a library removes it, everything in it, its audience, and every contributor and manager role held in it — and there is no trash to recover any of it from. **Boundaries with other apps.** When an item links a form or a wiki page (or, for items made earlier, a survey, post, or HR file), Libraries owns the pointer and the other app owns the record — the picker only offers records from apps that are enabled for the tenant. Content-governance reviews run on the shared platform governance pipeline, the same one Drive and Wikis use. ## 4. Running it ### Reorder libraries, categories, or items 1. On **All Libraries** (or inside a library), open **Reorder** while in Admin Order. 2. Move rows up or down and save. The order you set is what everyone sees. ### Take a library out of service temporarily 1. Open the library and use its **Enable/Disable** control (admin only). 2. While disabled, it is hidden from members and dropped from search but keeps all its content; re-enable it to bring it back. ### Review library health in Insights 1. Go to **Libraries → Insights** (admin only). 2. The **Governance** panel lists libraries with open findings — items that are stale or links that no longer resolve. The **Knowledge Gaps** panel lists searches employees ran that returned nothing, over a 7- or 30-day window. 3. Both panels only show data when their feature is switched on in Settings. ### Support employees browsing and bookmarking Employees browse libraries in a card view or a collapsible tree, search across every library they can see, and bookmark items they use often. Bookmarks are per person and item-only; the same content and bookmarks are available on mobile and through a browser extension that clips a page straight into a library. ## 5. Settings Found under **Libraries → Settings** (admin only). | Setting | Default | What it changes | |---|---|---| | Enable Libraries AI Agent | On | Whether the Libraries assistant answers in Ask AI | | Default Library View | Modern View | The starting layout of All Libraries — a card grid, or a collapsible tree | | Who can add or remove items in new libraries | Admins only | The item-management level a newly created library starts with | | Specific users for new libraries | None | People every new library starts out naming under *Admins and specific users*; the creator can remove them before saving | | Who can create a library? | App admins | Which people may create libraries; a Contributor grant also allows it | | Enable Governance Automation | On | Whether libraries are scanned on a schedule for stale items, broken links, missing or inactive linked records, items with no owner or an owner who left or can't open them, and items past the content-expiry period when one is set | | Review Interval for Every Library (days) | 90 | How long a library can go with nothing in it updated before it is flagged; it applies to every library | | Check for Broken Links | On | Whether the governance scan also checks external links | | Include Libraries in Global Search | On | Whether library content appears in the platform-wide search | | Auto-Generate Video Captions | On | Whether uploaded videos are captioned automatically (the audio is sent to our speech-to-text provider and uses AI credits) | | Notify Users When New Items Are Added | Off | Whether audience members get a notification when an item is added | | Notify People When Their Library Role Changes | On | Whether someone is told in-app when they are made a contributor or manager of a library, or their role on it changes | | Send Governance Review Reminders | On | Whether the people responsible for a library get its review reminders | | Enable Knowledge Gap Analysis | Off | Whether zero-result searches are collected and analyzed for gaps | | Send Gap Analysis Summaries | On | Whether gap summaries are sent when gap analysis is on | | AI: Search & Recommendations | On | Whether the assistant can search and recommend resources | | AI: Browse & Details | On | Whether the assistant can browse a library and open item details | | AI: Statistics & Reports | On | Whether the assistant can report counts and breakdowns | | AI: Content Management (Admin) | On | Whether Libraries administrators can add, edit, move, or remove items, create categories, and set or clear an item's owner via the assistant, with confirmation | The governance scan runs weekly and stays silent on day one — it has nothing to flag until content exists and ages past the review interval. The AI Content Management tools are admin-only and always ask for confirmation before they change anything. ## 6. More help - **Libraries FAQ** — specific setup and operating questions, and troubleshooting - Ask AI — the Libraries assistant answers questions about your resources, and about the app, from these articles. **Keywords:** library, libraries, resource collection, company resources, curated links, knowledge gap, broken link, who can see this library, library permissions, bookmark resource --- # Libraries FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Libraries — for the admin running it, and for the employees and library managers who use it. # Libraries FAQ Answers to common setup and operating questions about Libraries. For what the app is and how to set it up from scratch, see the [Libraries Overview](/help/articles/libraries_app_overview). --- ## Setup ## Do I need to configure anything before employees can browse libraries? Yes. Libraries requires a licence and is disabled by default, so an admin must first enable it in Admin → Apps → All Apps. Then create at least one library and give it a category. Every item lives in a category, so a library with no categories has nowhere to put its first item. ## Who can create a new library? The **Who can create a library?** setting under **Permissions** in Libraries Settings decides it. The default is **App admins only**. The other choices are **Managers and above — by role**, **People managers — anyone with direct reports, whatever their role**, **Everyone with access to the app**, and **Specific people — choose groups below**. Business admins, Libraries app admins, and anyone granted **Contributor** for Libraries under **Apps → Libraries → Admins & Contributors** can always create one, whatever this is set to. ## What permission does a new library start with? New libraries start with the **Who can add or remove items in new libraries** setting, which defaults to **Admins only**. The choices are **Everyone**, **Admins and specific users**, and **Admins only**. When you pick **Admins and specific users**, a **Specific users for new libraries** list appears. Everyone on that list starts as a contributor on each new library; existing libraries are not changed. --- ## Permissions and access ## What is the difference between Visibility and "Who can add or remove items?" They answer two separate questions. **Visibility** decides who can see the library: **All Users** or **Specific Audiences**. **Who can add or remove items?** decides who can add, edit, and delete its items. A library can be visible to everyone while only admins change its contents. ## Who can edit a library, and who can change its audience? Libraries app admins, business admins, the person who created the library, and anyone named as its **Manager** can rename it and organise its categories. Only a Libraries admin or the creator can change its **Visibility**, its audience rules, or **Who can add or remove items?**. A named Manager sees those controls read-only. Disabling or deleting a library is for Libraries admins only. ## How does "Admins and specific users" work? With **Admins and specific users**, only admins and the people you name in the library's **Specific users** panel can add, edit, and delete items. Each named person is a **Contributor** or a **Manager**; both can manage items, and a Manager can also rename the library and organise its categories. Anyone named there can open the library, even if the audience rules would not show it to them. The library's creator can always manage its items, at every setting. ## Which audience rules can I use to target a library? You can target by **Department**, **Location**, **Job Family**, **Job Title**, **Organizational Role**, **Group**, **Platform Role**, or **Individual User**. A person who matches any one rule can see the library. A department rule matches a person's primary department or any of their additional departments. A location rule includes every location beneath it, so a rule on a region reaches everyone at the sites in that region. ## "Why can't I see a library my coworker can see?" The library is probably set to **Specific Audiences**, and the coworker matches one of its rules while you do not. Ask an admin to check your department, location, and job title in your profile, since the rules read those. A department rule counts additional departments too, and a location rule covers every site beneath the chosen location. A library can also be disabled, which hides it from everyone except the people who manage it. ## "Why can't I add items to this library?" The library's **Who can add or remove items?** setting does not include you. Under **Admins only**, only admins and the library's creator can. Under **Admins and specific users**, you must be named on the library as a Contributor or Manager. Under **Everyone**, anyone who can see the library can add items. --- ## Day-to-day ## What types of items can I add to a library? In a **Mixed Content** library the Add Item form offers **Simple link**, **File**, **Form**, and **Wiki**. Form and Wiki appear only while the Forms and Wikis apps are turned on. File uploads a document, such as a PDF or an Office file. An **Images & Videos only** library offers a single **Media** option for images and videos. The library type is chosen at creation and cannot be changed afterwards. ## Can I disable a library without deleting it? Yes. A Libraries admin can disable a library from its actions menu and enable it again later. Items, categories, and audience rules are all kept. While it is disabled, only admins, the library's creator, and its Managers can open it. Items added to a disabled library send no new-item notifications. ## What view options are there? The main Libraries page has two views: **Modern View** (a card grid) and **Tree View** (a collapsible hierarchy). **Default Library View** in Settings picks the starting view, and it defaults to **Modern View**. Each category has its own layout: **Card view**, **Large view** (the default), or **Compact view**. Its sort order is **Admin defined**, **A to Z**, or **Z to A**. Categories in an Images & Videos library always show a card grid. ## Why are employees getting notifications about new items? The **Notify Users When New Items Are Added** setting is on; it defaults to off. When it is on, everyone who can see the library gets an in-app notification and an email, each subject to their own notification preferences. Items added together in one go are announced once, not one notification per item. Turn the setting off if the volume is too high. --- ## When something looks wrong ## "I searched for something and got no results — is search broken?" Search matches words in library names and descriptions, category names, and item titles and descriptions. It does not match an item by the name of its library or category. With several words, a result needs to match only one of them. If **Include Libraries in Global Search** is on, library items also appear in the platform-wide search bar. ## "The item says the source is unavailable" The item links to a form, wiki, or other record that was later deleted, archived, or deactivated. The item shows as unavailable instead of opening a dead page. Restore or republish the record, or replace the item with a current link. With governance automation on, a deleted record is flagged as critical and an archived or inactive one as medium. --- ## Governance and gap analysis ## What does governance automation check? When **Enable Governance Automation** is on, Libraries scans enabled libraries once a week. It flags libraries where nothing (the library, its categories or its items) has been updated within the review interval — a library manager can also save the library unchanged to confirm it is still accurate — stale items, broken external links, and items whose linked record is gone or inactive. The **Review Interval for Every Library (days)** accepts 7 to 365 and defaults to 90; an item is flagged at 80% of it. **Check for Broken Links** checks up to 50 external links per weekly run. **Send Governance Review Reminders** sends Inbox reminders only, with no email. ## What is knowledge gap analysis? **Enable Knowledge Gap Analysis** shows searches that returned no results on the Insights tab, so you know which content to add. It is off by default. Search terms are kept for about 90 days and are recorded anonymously unless this setting is on; turning it on also records who searched. **Send Gap Analysis Summaries** sends a weekly Inbox summary to organization admins and Libraries admins. Each weekly summary covers the last 30 days, and none is sent unless those 30 days hold at least 50 searches and at least one search that found nothing. --- ## Licensing and limits ## Does Libraries require a licence? Yes. Libraries requires a licence and is disabled by default. An admin enables it per organization in Admin → Apps → All Apps. ## Are there limits I should know about? | What | Limit | |---|---| | Library name | 100 characters, unique in your organization (not case-sensitive) | | Library description | 500 characters | | Library banner image | under 4 MB; PNG, JPEG, or WebP | | Item title | 255 characters | | Item description | 500 characters | | Link URL | 2,048 characters | | Uploaded file, image, or video | 100 MB per item | | Image formats | JPEG, PNG, GIF, WebP, SVG | | Video formats | MP4, WebM, QuickTime, AVI | | File formats | PDF, Word, Excel, PowerPoint, RTF, ZIP, plain text, CSV | | Uploaded caption file | 2 MB | | Governance review interval | 7 to 365 days (default 90) | | AI agent gap report | 7 to 45 days of search history | --- ## More help - [Libraries Overview](/help/articles/libraries_app_overview) - Ask AI — the assistant answers Libraries questions from these articles. **Keywords:** faq, libraries, library, resource library, knowledge base, library category, library item, permissions, audience rules, department audience, additional department, location audience, region, who can add or remove items, contributor, manager, governance, broken links, gap analysis, can't see library, can't add items, search --- # Live Assist App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-19 How to set up and run Live Assist — real-time remote video calls started from work orders, inspections, incidents, chat rooms, Lone Worker alerts and other records. # Live Assist ## 1. What it is Live Assist lets someone start a real-time video call — camera, microphone and screen share — from the record the work is about, such as a work order, an inspection, an incident or a chat room, and have a colleague see what they see and guide them live. Every call is listed in Live Assist against that record. When someone records a call, the recording, its transcript and an AI summary are kept with it. - **Enablement:** Live Assist is a pay-as-you-go app billed per participant minute with no licence required. An admin turns it on for the organization, publishes it to the people who should use it, and then checks the Live Assist switch inside each app — four start off, four start on. - **What it is not:** Live Assist is not a general-purpose meeting tool. Calls start from a record, not from a standalone "new meeting" button. The test call on the Settings page is a connectivity check only. ## 2. Standing it up 1. **Turn the app on.** Go to **Admin → Apps → All Apps**, find **Live Assist**, and enable it. 2. **Publish it to your people.** On the same page, publish Live Assist to everyone, or to the groups who should use it. Until you do, only admins see its buttons — the Live Assist **Overview** page says so for an admin. 3. **Video provider.** Live Assist runs on the shared MangoApps LiveKit account by default, so there is nothing to set up. For a dedicated LiveKit project (for example, for data residency), add a **LiveKit** meeting provider under **Admin → Integrations** (API key, API secret and server URL). 4. **Check the switch inside each app.** Every app Live Assist works inside has its own Live Assist switch. These four are off until an admin turns them on: - **Field Service Suite → Settings:** **Live Assist** — adds **Get help** to work orders. - **Inspections → Settings:** **Enable Live Assist** — adds **Live inspection** to in-progress inspections. - **Chat → Settings:** **Live Assist huddles** — adds **Start huddle (Live Assist)** to each conversation's **…** menu (top right of the room), and a full-width **Start huddle** button at the end of the conversation on a phone. - **Lone Worker → Settings:** **Open a live video channel to the responder when an alert is acknowledged** — opens a call automatically when a responder acknowledges any alert. These four are on until an admin turns them off: - **Safety Hub → Settings → Incident Settings:** **Live Assist** — adds **Live video** to incidents. - **Asset Pro → Settings → Core Features:** **Live Assist** — adds **Get help** to assets. - **Service Desk → Settings → General** (under **Features**): **Live Assist** — adds **Remote support** to a ticket's **Actions** menu. - **Onboarding Hub → Settings → Integrations:** **Live Assist** — adds **Welcome huddle** to onboarding plans. 5. **Confirm it works.** Go to **Apps → Live Assist → Settings** and run **Start test session**. Invite a teammate to check that they can join. The Live Assist **Overview** page shows an admin what still stands between their people and the buttons: whether the app is published past admins, whether **Who can start a Live Assist session?** is limited, and each app's switch. ## 3. How it fits together ### Calls and their names A call is a single video session attached to one record. What the call is called depends on how it started: - **Help call** — started with **Get help** (work orders, assets) or **Remote support** (Service Desk tickets). The person asking shares their camera or screen and a colleague guides them. **Remote support** started by a Service Desk agent is the agent calling the ticket's requester; a call the requester starts on their own ticket is an ordinary help call. - **Live video** — started with **Live inspection** (inspections) or **Live video** (Safety Hub incidents). The person on site points the camera while a remote colleague directs. - **Huddle** — started with **Start huddle (Live Assist)** in a chat room (**Start huddle** on a phone) or **Welcome huddle** on an onboarding plan. A call among the room's or plan's people. - **Site feed** — watching a registered site camera (see below). The watcher receives video only and cannot broadcast into the feed. Lone Worker calls open on their own when an alert is acknowledged; they appear as help calls about the alert. A call nobody joined shows as **Not connected**. Example: a technician on a work order taps **Get help**. A help call starts about that work order and the people Live Assist routes it to are notified (see below). A colleague joins, sees the technician's camera and guides them. If someone pressed **Record**, the recording and its AI summary are kept with the call. ### Participant roles - **Guided** — whoever started a help call or live video. - **Host** — whoever started a huddle (and anyone who joins a huddle without having been invited to it). - **Expert** — everyone else who joins, including everyone a call invited or rang by name. - **Observer** — someone watching a site feed. Subscribe-only: cannot publish audio or video. Every role except Observer has full camera, microphone and screen share. The role is how the person is listed on the call's details page. ### Who is notified when a call starts 1. **The record's own people, first, whatever the switch below says.** A work order rings its technician, whoever created it and Field Service's dispatch desk — the group chosen under Field Service's **Who hears about Field Service work with no owner**, else the Field Service app admins. An inspection rings its inspector; an onboarding plan its hiring manager, new hire and mentor; a chat room its members; a ticket its requester or assignee (see Remote support below). Assets, incidents and locations name nobody. 2. **Then, on Get help, Live inspection and Live video calls:** - If a group is chosen under **Route help requests to**, everyone in that group is notified — in the app and by phone push — on every such call, whatever the switch below says. - When no group can be rung — none is chosen, or the chosen group has nobody in it when the call starts (for example, an on-shift group with nobody on shift), or it has been deleted — the switch **When no group below can be rung, notify every manager and company admin** decides whether everyone with a manager or company-admin role gets an in-app notice. It is on by default. 3. **Huddles** ring only the chat room's members or the onboarding plan's people. **Remote support** started by a Service Desk agent rings only the ticket's requester; a call the requester starts on their own ticket rings its assignee and then the group or managers, like any help call. **Lone Worker** calls ring only the responder who acknowledged the alert — the alert's own escalation has already reached its responders. Each ring notifies up to 50 people at once; anyone past 50 is notified moments later by a background job. With the switch off, no group to ring and a record that names nobody (an asset or an incident), a call reaches no one — the person starting it is told so, and to use **Invite someone** (in the call's **⋮** menu) to bring a teammate in. The room's link opens only for people who already have access to the call, so sharing it is not enough. Once someone answers, everyone else who was rung is told who is on it, and their notice closes. ### Who can see, join and control a call - **Everyone** sees the calls they started, were invited to or joined, and — while it is live — a call that rang them. - **Joining a live call:** the host and anyone invited; on Get help, Live inspection and Live video calls, any manager and anyone the call rang, while it is running; on a chat huddle, the room's members; on a Lone Worker call, the alert's responders. A Service Desk agent's **Remote support** call is not open to managers: only the people on it (the agent, the requester and anyone invited) and the people allowed to open calls they were not part of can join it. - **Opening calls you were not part of:** decided by **Who can open sessions they were not part of?** (default: **App admins only**). Those people can open every call, including ended ones with their recording, transcript and AI summary. - **Ending a call for everyone, recording it, and inviting people into it:** the host, or anyone allowed to open calls they were not part of. Anyone else in the call can leave it. - **Retrying a failed recording or summary:** only the people allowed to open calls they were not part of — not the host. - **Site feeds:** watching one is decided by **Who can watch a site camera?** and reading its audit log by **Who can read and export a site feed's audit log?** (both default to app admins only). Registering, editing and taking a feed on air are for company admins and Live Assist app admins; deleting one is for company admins. - **Monitoring wall:** managers, company admins and Live Assist app admins. - **Analytics and Settings:** company admins and Live Assist app admins. Company admins and Live Assist app admins can always do everything above. ### Site feeds A site feed is a registered camera at a location — a tablet or kiosk running the capture page in a browser, or a fixed IP (RTSP) camera — that publishes video into a long-lived room that permitted people can watch. - **The device publishes; watchers only receive.** Someone watching a site feed cannot broadcast into it. - **On-air notice.** A browser capture point shows an **ON AIR** notice on its own screen while it is live. An IP camera has no screen, so it cannot show one — post signage at that location yourself. Live Assist marks every IP-camera feed as having no on-site notice. - **Audit log.** Every registration, pairing, on-air and off-air window, watch start and end, token rotation, recording start and stop, browser device going online or offline, and recording purge is written to an append-only log per feed. It answers "who watched which site, and when." An IP (RTSP) camera writes no online/offline rows. ### Recording, transcript and AI summary Recording is opt-in: a call is recorded only when someone presses **Record** in the room (the host, or someone allowed to open calls they were not part of). Two cases differ: - **Chat huddles** are recorded automatically when Chat's **AI huddle summaries (records huddles)** setting is on (with **Live Assist huddles**), and a recording notice is posted into the room. - **Site feeds** can be recorded only when recording is turned on for that feed. When a recording finishes it is saved with the call — as video evidence on the record itself for work orders, inspections, incidents, assets, Lone Worker alerts and App Builder records, and on the call's details page for the rest. The recording is then transcribed and an AI summary with key points and action items is written. The summary appears on the call's details page and on the record's **Live Assist** card. Only Chat writes it into the record itself: a huddle summary is posted into the room when Chat's **AI huddle summaries** setting is on and the huddle ran long enough to summarise. The host and everyone who joined are notified when the summary is ready; if the recording or summary cannot be produced, the host, everyone who joined and the people who can retry it are told. During a call, anyone in it can capture a snapshot. It is saved as photo evidence on the record when the record keeps photos, and otherwise on the call. ### Where the buttons appear | App | Button | Own switch | |---|---|---| | Field Service Suite | **Get help** on work orders | **Live Assist** (off by default) | | Inspections | **Live inspection** on in-progress inspections | **Enable Live Assist** (off by default) | | Chat | **Start huddle (Live Assist)** in each conversation's **…** menu; **Start huddle** at the end of the conversation on a phone | **Live Assist huddles** (off by default) | | Lone Worker | Opens automatically when an alert is acknowledged | **Open a live video channel to the responder when an alert is acknowledged** (off by default) | | Safety Hub | **Live video** on incidents | **Live Assist** (on by default) | | Asset Pro | **Get help** on assets | **Live Assist** (on by default) | | Service Desk | **Remote support** on tickets (for Service Desk staff, managers and the assignee) | **Live Assist** (on by default) | | Onboarding Hub | **Welcome huddle** on onboarding plans | **Live Assist** (on by default) | Every button also needs Live Assist published to the person, and **Who can start a Live Assist session?** to admit them. ## 4. Running it ### Reviewing calls Go to **Apps → Live Assist**. The Overview page lists the calls you can see with their record, kind, status, duration and AI summary. Filter by status (**Not connected**, **Live**, **Ended**) or by kind (**Help call**, **Live video**, **Huddle**, **Site feed**). Click **Details** on a call to see its AI summary, transcript, recording and participants. ### Using the monitoring wall Go to **Apps → Live Assist → Monitoring wall** (managers, company admins and Live Assist app admins). It shows the live calls you can join, recent ended calls you can open, and — for people who can see site feeds — the registered feeds and whether each is on air. It refreshes every 30 seconds. ### Managing site feeds Go to **Apps → Live Assist → Site feeds**. From here, depending on your access, you can: - **Register a feed** — give it a name and location, choose the source (Browser or RTSP), and optionally turn on audio capture and recording. - **Put it on air** — by hand, or on a schedule (days, start and end times, and time zone). - **Observe a feed** — opens a receive-only view of the feed. Available only while the feed is broadcasting. - **Read the audit log** — filter it and export it as CSV. - **Rotate the device token** — issues a new capture URL; update the device to it. ### Viewing analytics Go to **Apps → Live Assist → Analytics** (company admins and Live Assist app admins). It shows call volume over time, breakdowns by kind and by app, average duration and recording counts. The default window is 30 days, and the data can be exported as CSV. ## 5. Settings All on **Apps → Live Assist → Settings**: | Setting | Default | What it changes | |---|---|---| | **Who can start a Live Assist session?** | **Any employee** | **Managers & admins only** hides every button that starts a call (Get help, Live inspection, Live video, Remote support, Start huddle, Welcome huddle) from everyone else, and the server refuses their request. Lone Worker calls are not affected. | | **When no group below can be rung, notify every manager and company admin** | On | When **Route help requests to** has no group, or its group has nobody in it when a call starts or has been deleted, Get help, Live inspection and Live video calls send an in-app notice to everyone with a manager or company-admin role. Off, they reach only the record's own people. | | **Route help requests to** | No group | A group chosen here is notified — in the app and by phone push — on every Get help, Live inspection and Live video call, in place of every manager and company admin and whatever the switch above says. If the group has nobody in it when a call starts, or has been deleted, the switch above decides instead. | | **Who can open sessions they were not part of?** | App admins only | Who can open any call, including its recording, transcript and AI summary — and end, record and invite people into any call, and retry a failed recording or summary. **Any manager or above** or **Specific people** widen it. It does not affect who can answer a live call. | | **Who can watch a site camera?** | App admins only | **Specific people** lets chosen groups watch site feeds without registering or changing them. | | **Who can read and export a site feed's audit log?** | App admins only | **Specific people** lets chosen groups read and export the log without watching or changing a camera. | The same page has **Start test session** (a connectivity check) and **Sample data** (load demo calls and site feeds, then clear them). Per-feed settings, set when registering or editing a site feed: | Setting | Default | What it changes | |---|---|---| | **Capture audio as well as video** | Off | Whether the feed captures sound as well as video. | | **Allow recording this feed** | Off | Whether the feed can be recorded. Recordings are kept with the feed. | | **Delete recordings after (days)** | Blank (kept indefinitely) | When set, recordings older than this are deleted automatically by a sweep that runs every 5 minutes. | | **Automatically go on air on a schedule** | Off (put on air by hand) | When on, the feed goes on and off air on the days, times and time zone you set. | ## 6. More help - **Live Assist FAQ** — specific setup and operating questions. - Ask AI — the assistant answers questions about Live Assist from these articles. **Keywords:** live assist, remote video, video help, get help, live inspection, live video, screen share, remote expert, site feed, video inspection, huddle, help call, livekit, recording, snapshot, live-assist, live_assist --- # Live Assist FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-19 Answers to common setup and operating questions about Live Assist — for the admin running it. # Live Assist FAQ Answers to common setup and operating questions about Live Assist. For what the app is and how to set it up from scratch, see the [Live Assist Overview](/help/articles/live_assist_app_overview). --- ## Setup ## Do I need to configure anything besides enabling the app? Usually, yes. Before your people see a button that starts a call: 1. **The Live Assist app** must be enabled (Admin → Apps → All Apps). 2. **It must be published to them.** Until it is published past admins, only admins see its buttons. 3. **A video provider.** Live Assist runs on the shared MangoApps LiveKit account by default, so this is already done unless you want your own LiveKit project (Admin → Integrations). 4. **The app's own Live Assist switch.** Every app Live Assist works inside has one. In Field Service Suite, Inspections, Chat and Lone Worker it is off until an admin turns it on; in Safety Hub, Asset Pro, Service Desk and Onboarding Hub it is on until an admin turns it off. 5. **Who can start a Live Assist session?** must admit them. It allows any employee by default. The Live Assist **Overview** page shows an admin which of these is still in the way, and each app's switch. ## Which apps have their own Live Assist switch? All eight, named as they appear on that app's settings page. These four are off until an admin turns them on: - **Field Service Suite → Settings:** **Live Assist** — adds **Get help** to work orders. - **Inspections → Settings:** **Enable Live Assist** — adds **Live inspection** to in-progress inspections. - **Chat → Settings:** **Live Assist huddles** — adds **Start huddle (Live Assist)** to each conversation's **…** menu, at the top right of the room, and a full-width **Start huddle** button at the end of the conversation on a phone. - **Lone Worker → Settings:** **Open a live video channel to the responder when an alert is acknowledged**. These four are on until an admin turns them off: - **Safety Hub → Settings → Incident Settings:** **Live Assist** — adds **Live video** to incidents. - **Asset Pro → Settings → Core Features:** **Live Assist** — adds **Get help** to assets. - **Service Desk → Settings → General** (under **Features**): **Live Assist** — adds **Remote support** to a ticket's **Actions** menu, for Service Desk staff, managers and the ticket's assignee. - **Onboarding Hub → Settings → Integrations:** **Live Assist** — adds **Welcome huddle** to onboarding plans. ## How do I test that the video connection works? Go to **Apps → Live Assist → Settings** and run **Start test session**. You can invite a teammate to check that they can join. You cannot invite yourself — pick someone else. Test calls are marked as tests in the call list. --- ## Permissions and access ## Who can start a call, and how do I restrict it? **Who can start a Live Assist session?** on the Live Assist Settings page. The default is **Any employee**. **Managers & admins only** hides every button that starts a call — Get help, Live inspection, Live video, Remote support, Start huddle (Live Assist) and Welcome huddle — from everyone below manager, and the server refuses their request. Company admins and Live Assist app admins can always start one. Lone Worker calls open on their own when an alert is acknowledged and are not affected. Watching a site camera has its own setting, **Who can watch a site camera?** ## Who can see calls they were not part of? Everyone sees the calls they started, were invited to or joined, and — while it is live — a call that rang them. Beyond that: - **Managers** can see and join any Get help, Live inspection or Live video call while it is running, so they can answer it. Two exceptions: Lone Worker calls go to the alert's responders, and a Service Desk agent's **Remote support** call to the ticket's requester is not open to managers by role. - **Who can open sessions they were not part of?** decides who can open every call, including ended ones with their recording, transcript and AI summary. The default is **App admins only**; you can widen it to **Any manager or above** or to **Specific people**. - **Site feeds** are listed only for the people who can watch a site camera. Company admins and Live Assist app admins can always open every call. ## Who can join a call that is running? - The host and anyone they invited. - On a Get help, Live inspection or Live video call: any manager, and anyone the call rang, until it ends. - Not on a Service Desk agent's **Remote support** call, though: it rings only the ticket's requester, and managers cannot join it by role. - On a chat huddle: the room's members. - On a Lone Worker call: the alert's responders. - Anyone allowed to open calls they were not part of. ## Who can end, record or invite people into a call? The host, and anyone allowed by **Who can open sessions they were not part of?** (plus company admins and Live Assist app admins). Anyone else in the call can leave it but not end it for others. Retrying a failed recording or summary is only for the people allowed to open calls they were not part of — not the host. ## Who can use the Monitoring wall, Site feeds, Analytics and Settings? - **Monitoring wall:** managers, company admins and Live Assist app admins. - **Site feeds:** anyone who can register feeds (company admins and Live Assist app admins), watch a site camera, or read a feed's audit log. Deleting a feed is for company admins. - **Analytics and Settings:** company admins and Live Assist app admins. --- ## Routing and notifications ## Who is notified when someone asks for help? 1. **The record's own people, first, whatever the switches below say:** a work order's technician, whoever created it and Field Service's dispatch desk (the group chosen under Field Service's **Who hears about Field Service work with no owner**, else the Field Service app admins); an inspection's inspector; an onboarding plan's hiring manager, new hire and mentor; a chat room's members; a ticket's requester or assignee. Assets, incidents and locations name nobody. 2. **On Get help, Live inspection and Live video calls:** the group chosen under **Route help requests to**, in the app and by phone push — whatever the switch below says. 3. **When no group can be rung** — none is chosen, or the chosen group has nobody in it when the call starts (an on-shift group with nobody on shift, say), or it has been deleted — the switch **When no group below can be rung, notify every manager and company admin** (on by default) sends an in-app notice to everyone with a manager or company-admin role. With it off, nobody beyond the record's own people is notified. Huddles ring only the chat room's members or the onboarding plan's people. **Remote support** started by a Service Desk agent rings only the ticket's requester; a call the requester starts on their own ticket is an ordinary help call (its assignee, then steps 2 and 3). Lone Worker calls ring only the responder who acknowledged the alert — the alert's escalation has already reached its responders. ## Is there a limit on how many people a call rings? Each ring notifies up to 50 people straight away; anyone past 50 is notified moments later by a background job, so nobody is dropped. ## What happens when nobody is notified? If a call reaches nobody — for example, Get help on an asset with the switch off and no group to ring — the person starting it is told that nobody was notified and to use **Invite someone** (in the call's **⋮** menu) to bring a teammate in. Sharing the room's link is not enough: it opens only for people who already have access to the call. --- ## Day-to-day ## How does recording work, and is it on by default? Recording is opt-in. A call is recorded only when the host, or someone allowed to open calls they were not part of, presses **Record** in the room. When the recording finishes it is saved with the call, transcribed, and summarized by AI. The summary appears on the call's details page and on the record's **Live Assist** card. Two cases differ: - **Chat huddles** are recorded automatically when Chat's **AI huddle summaries (records huddles)** setting is on. A recording notice is posted into the room, and the summary is posted there when the huddle ends — unless the huddle was too short to summarise. With that setting off, a huddle someone records by hand gets its summary on the call's details page, not in the room. - **Site feeds** can be recorded only when recording is turned on for that feed. Only Chat writes the summary into the record itself. On a work order, inspection, incident, asset or ticket it is shown on the record's Live Assist card, not added as a note. ## Can I take a snapshot during a call? Yes. Anyone in a live call can capture a frame. Snapshots must be PNG or JPEG and no larger than 10 MB. A snapshot is saved as photo evidence on the record when the record keeps photos (work orders, inspections, incidents, assets, Lone Worker alerts, App Builder records), and otherwise on the call. ## How do site-feed schedules work? When you turn on a feed's schedule, it replaces the manual on-air control: you set the days of the week, a start and end time, and a time zone, and the feed goes on and off air on that schedule. Overnight windows (for example 22:00–06:00) are supported — the window belongs to the day it starts. A background sweep runs every 5 minutes to apply scheduled changes and check IP-camera state. If the feed has no time zone, it uses the location's, then the platform default. ## Does a site camera show that it is live? A browser capture point — a tablet or kiosk running the feed's capture page — shows an **ON AIR** notice on its own screen while it is live. A fixed IP (RTSP) camera has no screen and cannot show one, so post signage at that location yourself; Live Assist marks every IP-camera feed as having no on-site notice. ## What happens when a Lone Worker alert is acknowledged? When the Lone Worker setting **Open a live video channel to the responder when an alert is acknowledged** is on, acknowledging any alert — an SOS, a missed check-in or another trigger — opens a call between the worker and the responder who acknowledged it, and the responder is sent a link to join. The worker's last-known location shows in the room. If someone records the call, the recording is saved on the alert. The setting is off by default and needs the Live Assist app enabled. ## What is in a site feed's audit log? Every registration, on-air and off-air window, observation start and end, token rotation, recording start and stop, browser device going online or offline, and recording purge is written to an append-only log. An IP (RTSP) camera writes no online/offline rows. Rows cannot be edited or deleted. You can filter by event type and date range, and export to CSV (newest 10,000 rows per export). Who can read it is set by **Who can read and export a site feed's audit log?** --- ## When something looks wrong ## Why don't my workers see the Live Assist button? Check these in order — the Live Assist **Overview** page shows an admin most of them: 1. **Is Live Assist published to them?** If it is published to admins only, nobody else sees a button. Admin → Apps → All Apps. 2. **Is the app's own Live Assist switch on?** Every app has one. Field Service Suite, Inspections, Chat and Lone Worker start with it off; Safety Hub, Asset Pro, Service Desk and Onboarding Hub start with it on. 3. **Does "Who can start a Live Assist session?" admit them?** With **Managers & admins only**, frontline workers do not see the button. 4. **Is the record in the right state?** Live inspection appears on in-progress inspections; Remote support is shown to Service Desk staff, managers and the ticket's assignee, not its requester. ## Why is the Observe button unavailable on a site feed? A feed can be observed only while it is broadcasting: on air, and with its source live — a browser device that is connected, or an IP camera whose stream has been set up. If the feed is off air or its device is offline, **Observe** is unavailable. The feed's page shows its current state. ## A site feed's device went offline — why was nobody told? The 5-minute sweep notices when a browser capture device that was connected stops reporting and notifies company admins and Live Assist app admins. If the feed should have been on air at the time, the notice says so. A device that has never connected does not raise one, and neither does a fixed IP (RTSP) camera. ## My recording says "processing" and never finishes — where is it? After a recording stops (or the call ends), it shows as processing while the file is saved, transcribed and summarized — normally a few minutes. If it stays there, the video provider may not have delivered the file. If it fails, the host, everyone who joined and the people who can retry it are notified, and the call's details page offers **Retry** to the people who can retry it. --- ## Licensing and limits ## Does Live Assist require a licence? No. Live Assist is pay-as-you-go: there is no licence to buy and no monthly minimum. An admin enables the app, and usage is billed per participant minute. ## How is usage billed? Everyone's connected time in a call is added up and the total is rounded up to the next minute, once per call. Each person counts for at most 240 minutes of one call. The unit is a **participant minute** — a 10-minute call with 2 people is 20 participant minutes. The rate is a flat **$0.02 per participant minute**, with no tiers and no free allowance. Transcription and AI summaries draw on your shared AI credit pool, not the per-minute video meter. ## Are there limits I should know about? | What | Limit | |---|---| | Feed name length | 100 characters | | In-call snapshot size | 10 MB (PNG or JPEG) | | Analytics date range | 1–365 days (default 30) | | Call CSV export | Newest 10,000 rows per export | | Feed audit-log CSV export | Newest 10,000 rows per export | | People notified at once per ring | 50 — the rest are notified moments later by a background job | | External / guest participants | Not supported — invitees come from your organization only | --- ## More help - [Live Assist Overview](/help/articles/live_assist_app_overview) - Ask AI — the assistant answers Live Assist questions from these articles. **Keywords:** faq, live assist, remote video, get help button, live inspection, remote support, site feed, recording, snapshot, huddle, livekit, video provider, participant minute, audit log, monitoring wall, route help requests, live-assist, live_assist --- # Live Boards App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-14 How to set up and run Live Boards — leaderboards, KPI tiles, gauges, and status grids drawn from your data and placed on dashboards, TVs, and Digital Signage. # Live Boards ## 1. What it is Live Boards turns data you already have — Power Tables views, recognition activity, engagement by site, or coverage gaps by site — into visual displays that update automatically. Create ranked lists, stat tiles, gauges, scorecards, status grids, and more, then place them on dashboards, full-screen TVs, or Digital Signage slides. - **Enablement:** Live Boards is a pay-as-you-go app, billed from your credit wallet per active board per month (no per-employee fee). An admin enables it from Admin → Apps → All Apps; it is off until then, and members cannot open it until it is also published to users (step 2 below). Archived boards are not billed. - **What it is not:** Live Boards displays data from other sources — it does not store its own data. The data itself lives in Power Tables, the Recognitions app, the Levels & Badges app, or Shifts & Scheduling. If you need to collect or import data first, start with Power Tables. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Live Boards**. You also need at least one data source enabled: - **Power Tables** with at least one table that has a shared saved view, or - **Recognitions**, or - **Levels & Badges** (for engagement-by-site boards), or - **Shifts & Scheduling** (for coverage-gap boards by site). 2. Publish the app. A newly enabled app is open to admins only — a member who opens it is told "Live Boards hasn't been published to users yet. Ask a company admin to publish it." Go to **Admin → Apps → All Apps → Live Boards** and click **Publish to users** (or **Publish to specific groups**, then pick them under Access management). A board that reads Power Tables also needs Power Tables published to the same people. 3. Go to **Apps → Live Boards → Settings** and review the four settings: **Show boards on Digital Signage**, **Allow public board embed links**, **Default name masking for new boards**, and **Enable AI board suggestions**. 4. Go to the **Boards** tab and create your first board. The form asks for a name and a data source; you then add visualizations one at a time from the board editor. 5. To let others help build boards, a company admin goes to **Admin → Apps → All Apps → Live Boards**, opens the **Admins & Contributors** card, clicks **Manage Admins & Contributors**, and grants **Contributor** access to the users who should author boards. Contributors can create, edit, duplicate, and reorder boards and their visualizations and build playlists, but cannot change app settings, publish to Digital Signage, switch on public links, or archive/restore boards. 6. Confirm it worked: the board should appear on the Boards tab for every member who can see at least one of its visualizations. To put a visualization on the home page, a company admin places it on a dashboard from the board editor (see "Placing a visualization on a dashboard" below). 7. Optionally, load **sample data** from Settings to see a board for every chart type plus the states a demo otherwise can't reach — masking modes, goal bands, an archived board, and a screen rotation — useful for exploring the app before connecting real data. **Silent-until-paired:** a Power Tables source requires both the table and a shared saved view. If the table has only personal views, the board-creation form will refuse with an explanation. Create a shared view on the table first. **Native sources work without Power Tables.** If your workspace has Recognitions, Levels & Badges, or Shifts & Scheduling enabled but not Power Tables, you can still create boards — the source picker offers only the sources your workspace has enabled. ## 3. How it fits together **Board** — a named container that points at one data source and holds up to 12 visualizations. A board is either **Active** or **Archived**. Its **Data source** and **Source table** are locked while it has any visualization (archived ones count), because every visualization's column references point into that source; the **Saved view** is never locked and can be changed in **Board settings**. To point a working board at different data, remove its visualizations first — each one's snapshot history goes with it — and the source unlocks in Board settings, or build a new board on the other table. Duplicating a board does not help: the copy reads the same source and is locked on arrival. One exception is a repair: if the table a board reads was archived ("Source unavailable"), Board settings lets you pick a replacement table and every visualization moves with it, columns matched by name. **Visualization** — a single reading of the board's data, drawn as one of 13 chart types: ranked list, table, chart, movers, status grid, share (100% bar), calendar, stat, line, gauge, streak, pace, or scorecard (2–4 metrics side by side). Each visualization is its own widget — it can be placed individually on a dashboard, given its own **Audience**, and watched independently. **Data source** — boards can read from four sources. A **Power Tables view** is the default; the board binds to a saved view and draws its columns. **Recognition** boards rank people by recognition metrics (given, received, points). **Engagement (by site)** boards rank sites by engagement activity, and **Coverage gaps (by site)** boards count unfilled on-shift role slots per site (offered only when Shifts & Scheduling is enabled) — on both, entities are locations, not people, which makes them safe for a public screen. **Masking** — every visualization that ranks people carries a **Name masking** policy: **Full names**, **First name last initial**, or **Anonymized ranks**. The policy applies everywhere the visualization renders — dashboards, mobile, TV screens, public embeds, and signage. The workspace default is Full names; each visualization can override it in its drawer's **Advanced** section. Engagement and Coverage boards rank sites, not people, so the masking policy does not apply to them. **Playlist** — a named, ordered rotation of visualizations for screens that cycle through several automatically. Each playlist has its own **Seconds per visualization** setting and, once a Live Boards admin switches on **Share a link for screens that can't sign in**, its own public link. A playlist can hold up to 20 visualizations. **Snapshot** — the platform captures each active visualization's value once per night. These snapshots power the history page, sparklines, movers, streak, and pace visualizations. A Line with **Update through the day (intraday)** switched on is also captured hourly. Intraday snapshots are retained for 7 days; daily snapshots are kept for 13 months (396 days). ## 4. Running it ### Creating a board 1. On the **Boards** tab, click **New board**. 2. Name the board, choose a **Data source** and (for Power Tables) pick a **Source table**. The board starts on the table's oldest shared view; to read a different one, choose it under **Saved view** in **Board settings**. 3. The board editor opens. In the **Add a visualization** card, click a chart type — the drawer shows only the fields that chart type needs. 4. Add more visualizations as needed (up to 12 per board). Drag to reorder them. 5. On a board that reads a Power Tables view, and while **Enable AI board suggestions** is on, the visualization drawer has a box labelled **Describe this visualization (optional)** with a **Suggest with AI** button. It drafts a leaderboard — a ranked list, table or chart — for you to review. The table's name and description, its column names and types, and whatever you type in the box are sent to the AI — never any row data. ### Placing a visualization on a dashboard From the board editor, open the ⋮ menu on a visualization's row and pick a dashboard under **Place on dashboard**. The visualization goes live on that dashboard at once when the dashboard had no unpublished changes; otherwise it is added to the dashboard's draft and goes live the next time someone publishes it. Only company admins see this part of the menu (Live Boards admin or Contributor access is not enough), because it changes what that dashboard group sees on its home page. Boards also appear in the platform's global search when the app is enabled — searching by board name links directly to the board. ### Presenting on a TV or kiosk Open a board and click **Present** to show it full-screen with no app chrome. By default the board displays as a grid of all its visualizations. On a board with more than one visualization, click **Rotate one at a time** to cycle through them instead (30 seconds per visualization). The page refreshes itself automatically — no JavaScript is required on the display device. Present is a signed-in page: the TV's browser must be signed in as someone who can open the board, and it shows what that person may see. For a screen that should never need a sign-in, use a public link instead: a Live Boards admin opens the visualization's drawer (board editor → the pencil on its row → **Advanced**) and turns on **Allow external embed**, which creates an unguessable public link (saving closes the drawer — reopen the visualization to copy the link). Anyone with that link can view the visualization without signing in. Its masking policy still applies, and a visualization limited to an **Audience** cannot be embedded. ### Setting up a screen rotation (playlist) 1. Go to the **Playlists** tab (visible to contributors and admins). 2. Click **New playlist**, name it, tick the visualizations to include, set **Seconds per visualization**, and number them to set the order. 3. To share publicly, a Live Boards admin turns on **Share a link for screens that can't sign in** on the playlist, which creates a public link. Copy it to the TV's browser. The screen rotates through the visualizations automatically. Each visualization in the rotation must also have its own **Allow external embed** turned on — the playlist does not bypass the per-visualization opt-in. **Seconds per visualization** must be between 15 and 600 (default 60). ### Watching a visualization for alerts Members can **Watch** individual visualizations from the board page (**Stop watching** undoes it). Goal alerts are per visualization and off until its author ticks **Notify when this visualization crosses its goal** and sets a **Goal**; the switch is offered on **Stat**, **Line**, and **Gauge** only — Streak, Pace, and every ranked type never alert. Once it is on, the person who added the visualization, the group chosen under **Who to notify**, and everyone who watches it are notified when the value goes off target, and again when it recovers — each only if they can still open it. Rank-entry notifications are separate and opt-in: with **Notify members who enter the top 3** switched on for a visualization that ranks people, the nightly snapshot compares today's top 3 with yesterday's, and members who entered the top 3 are notified. ### Reviewing board health (Analytics) Admins see an **Analytics** tab that answers four operational questions no other surface does: - **Source health** — which boards are bound to a source that no longer resolves (archived table, deleted view, disabled source app). These boards show "source unavailable" on every dashboard, mobile list, and TV they appear on, with nothing else alerting the admin. - **Snapshot health** — whether the nightly snapshot job is running and which boards have gaps in their daily history. - **Public exposure** — which individual visualizations and which playlists are currently reachable by anyone holding a public link. The links themselves are never shown — only the count and the names. - **Reach** — where boards are placed (dashboards, playlists, signage), who watches them, and which active boards are not used anywhere. ### Weekly digest A weekly email digest goes to everyone who watches at least one visualization — the **Live Boards · Weekly Digest** notification is on by default. It is sent every Monday and lists up to 12 visualizations the recipient can open, watched ones first; if none has a value that week, no email is sent. To stop it, stop watching, or go to **Account Settings → Notifications → Add Notification Exception**, pick **Live Boards · Weekly Digest**, tick **Email**, and click **Add Exception**. ## 5. Settings All settings are at **Apps → Live Boards → Settings**. Admin access required. | Setting | Default | What it changes | |---|---|---| | **Show boards on Digital Signage** | On | Tenant-wide switch. When off, nothing from Live Boards plays on any Digital Signage screen, regardless of each visualization's own **Publish to Digital Signage** switch. | | **Allow public board embed links** | On | Tenant-wide switch. When off, every external embed link and every shared playlist link stops at once; the same links resume unchanged when it is switched back on. | | **Default name masking for new boards** | Full names | The masking policy pre-selected for the first visualization added to a board; later ones start from the masking of the first visualization on their board. Choices: **Full names**, **First name last initial**, **Anonymized ranks**. Each visualization keeps its own masking, set under **Advanced** in its drawer. | | **Enable AI board suggestions** | On | Shows or hides the "Suggest with AI" button in the "Add a visualization" drawer (boards that read a Power Tables view only). When used, the table's name and description, its column names and types, and whatever the author types in the box are sent to the AI — never any row data. | ### Wallboard branding Three additional settings control the appearance of full-screen and public-embed surfaces: | Setting | Default | What it changes | |---|---|---| | **Show your logo on full-screen boards** | Off | Displays a logo on wallboard surfaces (present mode and public embeds). | | **Logo** | None | An image from the Asset Library. System, business, and app-level library assets are available. | | **Accent color** | None (built-in dark palette) | A hex color value (e.g. `#1b6ef3`) used as the accent on full-screen surfaces. | ### Archiving and restoring boards Live Boards admins can archive a board from the ⋮ menu on its row in the boards list. Archiving removes the board and all its visualizations from every dashboard, mobile view, and screen at once. Archived boards appear under the **Archived** status filter on the Boards tab. Restoring a board, from the same menu, brings it back to all the surfaces it was placed on. Boards are never permanently deleted — archive is the only removal path. Duplicating an active board copies the visualizations it currently shows; a visualization archived on its own in the Widget Gallery is not copied. Duplicating an archived board copies the visualizations that restoring it would bring back. Every copy starts quiet — **Publish to Digital Signage**, **Allow external embed**, **Notify when this visualization crosses its goal**, **Also open a task while off target** and **Notify members who enter the top 3** are switched off — so a duplicate never appears on a signage screen or a public link, and sends no goal alert or rank notice, until someone switches those on. ## 6. More help - **Live Boards FAQ** — specific setup and operating questions, limits, and troubleshooting. - **Power Tables App Overview** — where the data behind most boards comes from. - Ask AI — the assistant answers questions about Live Boards from these articles. **Keywords:** live boards, leaderboard, kpi, scoreboard, signage, wallboard, dashboard widget, gauge, status grid, scorecard, board rotation, playlist, embed, live-boards, live_boards --- # Live Boards FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Live Boards — for the admin running it. # Live Boards FAQ Answers to common setup and operating questions about Live Boards. For what the app is and how to set it up from scratch, see the [Live Boards Overview](/help/articles/live_boards_app_overview). --- ## Setup ## Does Live Boards require Power Tables? Only for boards backed by a Power Tables saved view, which is the most common kind. Boards can also read Recognition activity, Engagement by site, or Coverage gaps by site (when Shifts & Scheduling is enabled) directly, so you can build a board without creating a table first. Each app meters independently — rows on the Power Tables side, active boards on the Live Boards side. ## What do I need to configure before boards appear on Digital Signage? Two things must be on. In Live Boards **Settings**, the **Show boards on Digital Signage** toggle must be enabled (it is on by default). Then each visualization needs **Publish to Digital Signage** turned on in its own drawer (board editor → the pencil on its row → **Advanced**) — a switch only Live Boards admins see. A visualization limited to an **Audience** cannot be published to signage. Signage screens also have their own per-screen content-type gate — if Live Board content is disabled on a particular screen, that screen skips boards even when the app-level switch is on. ## Can I change a board's data source after I create it? You can change which saved view a board reads at any time — **Board settings → Saved view** (visualizations already on the board keep their view unless you tick the box to switch them). But while a board has any visualization, archived ones included, its **Data source** and **Source table** are locked: each visualization reads columns from the current source, so switching would break them. To point a working board at different data, remove its visualizations first — each one's snapshot history goes with it — and the source unlocks in Board settings, or build a new board on the other table. Duplicating does not help: the copy reads the same source and is locked on arrival. --- ## Permissions and access ## Who can create boards, and who can manage settings? Two tiers. **Contributors** (anyone with app contributor access, or an admin) can create, edit, duplicate, and preview boards and their visualizations, and build playlists. **Admins** (app admins and company admins) additionally control app settings, archive and restore boards, publish visualizations to Digital Signage, and switch on the public links that put a visualization or a playlist on the open web. A company admin grants Contributor access at **Admin → Apps → All Apps → Live Boards** → the **Admins & Contributors** card → **Manage Admins & Contributors**. Placing a visualization onto a dashboard needs a company admin, which is separate from either Live Boards tier. ## Why can't some of my employees see a board? Work through the causes in this order: 1. **The app is not published to users.** A newly enabled app is open to admins only, and members are told "Live Boards hasn't been published to users yet. Ask a company admin to publish it." A company admin goes to **Admin → Apps → All Apps → Live Boards** and clicks **Publish to users** (or **Publish to specific groups**). 2. **The source app is not published to them.** A board that reads Power Tables also needs Power Tables published to the same people. 3. **A visualization's Audience excludes them.** **Audience (optional)** is set on each visualization (its drawer → **Advanced**), not on the board — only members of that group see it. 4. **It reads a Power Table restricted to specific people**, and they are not among them. 5. **It is switched off in the Widget Gallery.** 6. **The board is archived.** A visualization limited to an Audience cannot be published to Digital Signage or a public embed at all; on those surfaces, which have no viewer, the name masking policy is what protects people's identities. --- ## Day-to-day ## What are the 13 chart types? Ranked list, Table, Chart, Movers, Status grid, Share (100% bar), Calendar (agenda by date), Stat, Line, Gauge, Streak (days since), Pace (are we on track?), and Scorecard (2–4 metrics). A scorecard holds 2 to 4 unrelated metrics side by side, each against its own target. ## How does name masking work, and where is it applied? Each visualization carries one of three **Name masking** policies: **Full names**, **First name last initial**, or **Anonymized ranks**. A tenant-wide default for new ones is set in **Settings** under **Default name masking for new boards**. Masking is applied once in the rendering pipeline, so every surface — dashboards, signage, present mode, embeds, mobile — shows the same treatment. Masking governs people columns only; a visualization ranking stores, products, or sites always shows their real names. ## How do I put a board on a break-room TV without signing in? Use a public link, which a Live Boards admin sets up. For one visualization, turn on **Allow external embed** in its drawer and open its link on the TV. For several in turn, build a **Playlist** — a named rotation of up to 20 visualizations with a configurable **Seconds per visualization** (15–600 seconds, default 60 seconds) — turn on **Share a link for screens that can't sign in**, then paste that link into the TV's kiosk browser. The screen loops indefinitely with no account behind it. A shared playlist shows only visualizations that have **Allow external embed** on themselves, and both kinds of link stop while **Allow public board embed links** is off in Settings. **Present** is not a no-sign-in path: it is a full-screen page that refreshes itself every 2 minutes — no JavaScript and no signage player needed — but the TV's browser must be signed in as someone who can open the board, and it shows what that person may see. ## How do alerts and notifications work? Alerts are per visualization and off until its author ticks **Notify when this visualization crosses its goal** and sets a **Goal**. The switch is offered on **Stat**, **Line**, and **Gauge** only — Streak, Pace, and every ranked type never alert. You are told once when the value goes off target, once if it moves further off target (only when a warning threshold is set), and once when it recovers — only a band change triggers a notification, not every fluctuation. Recipients are the person who added that visualization, the group chosen under **Who to notify**, and everyone who watches it — all filtered to people who can still open it. Values are checked every night (hourly on a Line with intraday updates on), and sample boards never notify. You can optionally have a task created automatically while the value is off target by enabling **Also open a task while off target** in the visualization's drawer (board editor → the pencil on its row → **Advanced**). ## How do rank-entry notifications work? On a visualization that ranks people, you can turn on **Notify members who enter the top 3** in its drawer (board editor → the pencil on its row → **Advanced**). When the nightly snapshot detects a person who was not previously in the top 3, that person receives a notification. This is opt-in per visualization and only applies where the entities are people (not locations, stores, or products). ## Can I embed a board on an external page? Yes, per visualization and off by default. A Live Boards admin turns on **Allow external embed** in the visualization's drawer (board editor → the pencil on its row → **Advanced**) to create an unguessable link that renders it read-only with masking applied and no login required. The **Embed origins (optional)** field restricts which sites may frame it — one origin per line, up to 10. **Rotate link** cuts off every link already shared. A visualization limited to an **Audience** cannot be embedded. Playlists can be shared the same way, so a whole rotation can run on one public link. ## How current is a board, and where does its history come from? Boards read live data on every page load. Present mode refreshes every 2 minutes. History is separate: a nightly capture stores each visualization's values, which is what powers movement deltas (against 1, 7, 14, or 30 days back), movers trend lines, streak counts, and the history page. The history page offers 7, 30, 90, and 365-day windows (defaulting to 90 days) and can export to CSV. Daily history is kept for 13 months. A Line marked as intraday is also captured hourly; intraday detail is kept for 7 days. ## What does "Suggest with AI" do? When enabled in **Settings** (**Enable AI board suggestions**), a **Suggest with AI** button appears in the visualization drawer, in the box **Describe this visualization (optional)** — on boards that read a Power Tables view, for Contributors and admins. Describe what you want in plain language (up to 500 characters) and the AI drafts a leaderboard — a ranked list, table or chart — proposing the chart type, entity and score columns, aggregate, and ordering. The table's name and description, its column names and types, and whatever you type in the box are sent to the AI — never any row data. Goal values are accepted only when the number appears literally in your description. --- ## When something looks wrong ## "My board says its data source is unavailable" The board's underlying table or saved view has been archived, deleted, or made personal. The board renders a "source unavailable" message on every surface rather than going blank. Open the Analytics tab to see every board in this state alongside what it was bound to. If the table was archived, fix it by restoring the table in Power Tables, or open the board's **Board settings** and pick a replacement table — every visualization moves with it, columns matched to the new table by name; if any cannot be matched, the change is refused and nothing is altered. Duplicating the board does not repair it: the copy reads the same source. ## "The board I just created isn't showing on Digital Signage" Three gates must all be on: the app-level **Show boards on Digital Signage** toggle in Settings, the visualization's own **Publish to Digital Signage** switch (set by a Live Boards admin), and the per-screen content-type setting on the signage screen itself. Check all three. Also confirm the board's status is active — archived boards are not displayed anywhere. ## "My weekly digest email didn't arrive" The digest goes to people who watch at least one visualization, so check in this order. Do you watch one? Open a board and click **Watch**. Is a watched visualization still visible to you, with a value this week? Rows with no value are left out, and if nothing has a value no email is sent. Is there an exception for **Live Boards · Weekly Digest** under **Account Settings → Notifications → Current Exceptions**? Remove it. Is your **Email** channel on? The digest is on by default, sends every Monday, and includes up to 12 visualizations the recipient can actually open, with watched ones listed first. --- ## Licensing and limits ## How is Live Boards billed? Live Boards is pay-as-you-go from your credit wallet, billed per active board per month — 500 credits per active board a month, drawn on the 1st in advance. There is no per-seat charge and no minimum — you pay only for boards that exist and are active. Archived boards, sample boards, and boards with no active visualization are not billed; archiving a board stops the next month's draw, not the current one. An admin must enable the app before it can be used; it does not turn on automatically. ## Are there limits I should know about? | What | Limit | |---|---| | Visualizations per board | 12 | | Top-N ranking range | 1–100 | | Board name length | 120 characters | | Scorecard metrics | 2–4 per scorecard | | Playlist visualizations | Up to 20 | | Playlist seconds per board | 15–600 seconds (default 60) | | Present-mode refresh | Every 2 minutes | | Embed origin allowlist | Up to 10 origins per visualization or playlist | | History windows | 7, 30, 90, 365 days | | Daily snapshot retention | 13 months | | Intraday snapshot retention | 7 days | | Movement delta windows | 1, 7, 14, 30 days back | | Weekly digest visualizations | Up to 12 per email | | AI description length | 500 characters | --- ## More help - [Live Boards Overview](/help/articles/live_boards_app_overview) - Ask AI — the assistant answers Live Boards questions from these articles. **Keywords:** faq, live boards, leaderboard, kpi, signage, masking, wallboard, dashboard, playlist, embed, gauge, status grid, alerts, not showing, permissions, live-boards, live_boards --- # Live Translate App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-17 How Live Translate works, how to set it up, and how the company glossary shapes its translations. # Live Translate ## 1. What it is Live Translate is a real-time speech-to-speech interpreter for frontline conversations. Two people who do not share a language each speak in their own, and the app transcribes, translates, and speaks back in the other person's language — no bilingual colleague needed. - **Enablement:** Live Translate is pay-as-you-go. It requires no license; speech-to-text, translation on MangoApps' managed service, and text-to-speech draw your organization's AI credits, shown under Billing & Payments → AI (a translation provider your organization connects bills your own account instead). An admin enables it from Admin → Apps → All Apps. - **What it is not:** Live Translate is the real-time spoken interpreter. The company glossary it shares also governs written translation of voice notes, recognition posts, broadcast texts, alerts, policies, Frontline Execution campaigns, Sites, and News Feed posts and newsletters — but those surfaces are part of their own apps, not this one. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Live Translate**, and enable it. 2. Open **Live Translate** in **Admin → Apps → All Apps** and click **Publish to users** — or **Publish to specific groups**. Enabling alone doesn't give employees and managers access. 3. (Optional) Go to **Admin → Organization → Integrations** and connect a dedicated translation provider — AWS Translate or DeepL. Without one, translation falls back to the platform-managed engine automatically; no extra configuration is required. 4. (Optional) Go to **Admin → Translation** and adopt an industry starter pack or add your own glossary terms so company-specific vocabulary translates correctly from the start. 5. Confirm it works: open **Live Translate** from the app launcher, select two languages, hold the talk button, and speak. You should hear the translation spoken back. Admins can use the app as soon as it is enabled; employees and managers can once it is published to them (or their group is given access). The glossary and the dedicated provider are governance layers — they improve accuracy, but nothing blocks use without them. ## 3. How it fits together ### Two interpreter modes Live Translate offers two ways to use it, **One device** and **Two devices**, listed in the app's side menu. On a phone they also appear as buttons at the top of the page. **One device** — two people share a single phone or tablet. Each side of the screen has its own language selector and talk button. Person A holds their button and speaks; the translation plays aloud for Person B, and vice versa. Example: a warehouse supervisor (English) and a new hire (Spanish) stand together reviewing a safety checklist — one phone between them, each holding their button to talk. **Two devices** — each person uses their own phone. One person starts a session and receives a six-character code; the other enters it on their device to join. To save the typing, the host's screen also shows a QR code and a **Copy link** button (plus **Send link** on devices that have a share menu): the other person scans the QR code with their phone's camera or opens the link, and Two devices opens with the code already filled in — they still tap **Join**. The QR code and link are shown only to the host, and only until someone joins. Once paired, each person speaks on their own screen. The translation is broadcast to the other device and played automatically. Two devices also supports a **hands-free** mode where the app listens continuously and sends each utterance for translation when the speaker pauses, with no button press required. Live Translate isn't in the OneMango phone app (listed as Mango Ops in the App Store and on Google Play) — on a phone, open it in the phone's web browser: sign in at your company's OneMango address followed by `/m/login`, then open **Live Translate** from **More** (or go to `/apps/live-translate`). A paired session expires after 2 hours. Only the two participants can send or receive turns — a third person with the code is rejected. Using a screen reader, voice control or switch access? Press **Hold to speak** once to start and again to stop. ### The turn pipeline Each spoken turn runs three steps in sequence: the speech is transcribed (speech-to-text), the transcript is translated through the resolved provider, and the translation is spoken back (text-to-speech). Turns are ephemeral: Live Translate keeps no conversation record, there is no transcript history to open, and nothing you said is readable in the product afterwards — except a phrase someone flags as mistranslated (see **The quality loop** below). The transcript and translation appear on screen only while the conversation is open. On a shared phone in **one device** mode, tap **Clear** when you're done so the next person who picks it up doesn't see the conversation; in **two devices** mode, **Leave session** clears it. One qualification, stated plainly because "never stored" would be too strong. In **two devices** mode each turn travels to the other phone over OneMango's shared real-time message service, labelled with your organization's ID, and is deleted within roughly 90 minutes by a cleanup job that runs every 30 minutes. Until then the turn's text and its synthesized audio are held there. No screen in the product reads them; reaching them requires direct database access. **One device** mode does not use the message service at all. This is delivery, not retention: nothing accumulates, and there is still no conversation history anywhere in the product. ### The company glossary The glossary is a set of terminology rules managed at **Admin → Translation**. Besides Live Translate, it applies to written translation elsewhere on the platform: voice notes, recognition posts, broadcast texts, alerts, policies, Frontline Execution campaigns, Sites, and News Feed posts and newsletters. The list at the top of **Admin → Translation** is the current one. Chat message translation, Service Desk translation, broadcast voice calls, and SOP Hub's AI translate don't apply it yet. Two types of rule are available: - **Mapping** — a term in one language must translate to a specific term in another. For example, "forklift" (English → Spanish) must always become "montacargas", not a generic translation a provider might choose. - **Do not translate** — a term must pass through untranslated regardless of target language. Brand names, product codes, and acronyms like "OSHA" are common examples. A worked example: a retail chain adds three glossary rules — "stockroom" → "almacén" (mapping, English → Spanish), "backstock" → "existencias de reserva" (mapping, English → Spanish), and "SKU" (do not translate). When a supervisor says "check the backstock SKU in the stockroom", the Spanish translation uses "existencias de reserva" and "almacén" and keeps "SKU" as-is — for example "revisa el SKU de existencias de reserva en el almacén" — instead of whatever words the engine would have picked. The same three rules also apply when an English voice note is translated into Spanish. Terms match whole words — add plurals as their own terms. A mapping applies only when a translation runs in exactly its language pair. The glossary enforces rules at the platform layer, not inside any one provider. The mechanism is protect-then-restore: matched terms are replaced with placeholder tokens before the text reaches the translation engine, and the correct terms are substituted back after translation returns. This means rules work identically whether the tenant uses AWS Translate, DeepL, or the platform's LLM engine, and whether the surface is the spoken interpreter or a written translation. ### The quality loop Any user can flag a translation as wrong by tapping the **Wrong?** button on a translated turn (or on a translated voicenote). The flag lands in a pending queue visible at **Admin → Translation**, and the flagged phrase and its translation are kept there for review — a dismissed flag keeps them too. The person who flagged it isn't told what an admin did with it. An admin can then: - **Add term** — type just the word or short phrase that came out wrong into **Term (narrow to the word)** (the flagged sentence is on the card as **Original:**), enter its correct translation in **Should translate to**, and click **Add term**. Keep it short: a term matches only that exact wording, so a whole sentence rarely matches a later turn. - If the card says a term can't fix the flag — the speaker's language wasn't recognised, or both sides were set to the same language — there's nothing to add; **Dismiss** it once you've read it. - **Dismiss** it — close the flag if the translation was acceptable. Dismissing doesn't delete it: its phrase still counts in the most-flagged phrases on the Analytics page. Admins receive an in-app notification when flags arrive (throttled to one per 6 hours) and an email digest (throttled to one per 24 hours). ### Provider resolution Translation runs through the first configured engine in this order: 1. A **dedicated provider** the admin connected at **Admin → Organization → Integrations** — AWS Translate or DeepL (bring-your-own-key). 2. The **platform-managed engine** — AWS Translate with platform credentials, available to every tenant with no setup. 3. The **platform's language model** — used only where neither of the above is set up. The order is decided by what is set up. If the platform-managed engine fails during a spoken turn, that turn is retried once on the platform's language model, so the conversation carries on (just a little slower for that turn). If your organization's own provider fails, Live Translate never sends the words to another engine: that turn fails and the speaker tries again — or, if the provider rejected its key or ran out of quota, the speaker is told to let an admin know. Speech-to-text and text-to-speech always run on the platform's OpenAI key. If that key isn't set up, Live Translate shows a notice on load and disables the talk buttons, rather than letting users discover the failure mid-conversation. If text-to-speech fails on a single turn, the translation still appears on screen. ### Supported languages Live Translate supports 15 languages: English, Spanish, French, German, Portuguese, Italian, Chinese, Japanese, Korean, Arabic, Hindi, Russian, Vietnamese, Tagalog, and Polish. In one-device mode, either side can also be set to **Detect language**, which identifies the speaker's language automatically from their speech. Both sides cannot be set to Detect at the same time — the Detect side must speak first so the app knows what language to translate into. Your side — **Person A** on one device, **Your language** on two devices — starts on your profile language (English if your profile language isn't one of the 15). On one device, **Person B** starts on Spanish, or English if your profile language is Spanish. Each device remembers the last languages you picked. ## 4. Running it ### Managing the glossary 1. Go to **Admin → Translation**. 2. Add terms individually using the form at the top, or adopt an **industry starter pack**. Three packs ship with the platform: - **Warehouse & Manufacturing Safety** (English → Spanish) — 13 terms including lockout-tagout, PPE, and muster point - **Retail & Store Operations** (English → Spanish) — 9 terms including stockroom, planogram, and shrinkage - **Healthcare & Facilities** (English → Spanish) — 7 terms including shift handoff, charting, and isolation room 3. To bulk-add terms, import a CSV file with the header row shown below. Import only adds new terms: a row whose source text and languages match an existing term is skipped, even if you changed its translation in the file — edit existing terms in the list instead. 4. To export the full glossary, click **Export CSV** — useful for backup or for sharing terminology across tenants. The file uses the same columns **Export CSV** writes, under this header row: ``` source_language,target_language,source_text,target_text,term_type,case_sensitive,active ``` `term_type` is `mapping` or `do_not_translate`. The last two columns are optional — leave them out or blank and a term imports as case-insensitive and active; otherwise put `true` or `false`. Save the file as CSV UTF-8 with commas between columns. Each term can be marked active or inactive, and optionally set to case-sensitive matching. Language codes use ISO 639-1 format. For Live Translate, use two-letter codes such as "en", "es", and "pt" — its turns never use a regional code, so a term written for "pt-br" doesn't apply there, though regional codes like "pt-br" still apply on other translation surfaces. ### Reviewing flagged translations 1. Go to **Admin → Translation**. The **Flagged translations** section shows pending flags, oldest first. 2. For each flag, decide whether the translation was genuinely wrong. 3. To fix it, type the offending word into **Term (narrow to the word)** — it starts empty — enter its correct translation in **Should translate to**, and click **Add term** — this creates a glossary mapping and closes the flag in one step. 4. To close a flag without action, click **Dismiss**. The flagged-phrases list on the Analytics page shows which phrases are flagged most often — dismissed and resolved flags included — and whether the glossary already covers them. ### Viewing translation analytics 1. Go to **Admin → Translation**, then click **Analytics**. 2. The dashboard shows counts of machine translations (calls to AWS Translate or DeepL — translations written by the platform's language model aren't counted), voice transcriptions and spoken playbacks (both cover every feature, not only Live Translate), and active terms; a daily trend chart; the active engine with average latency, cached translations and a count per provider; the terminology quality loop (pending, resolved, dismissed flags); top target languages; and the most-flagged phrases. The window is selectable at 7, 30, or 90 days; AI usage logs are kept for 30 days, so a 90-day window shows no activity before that. Analytics show counts and languages, plus the most-flagged phrases table, which shows the text of phrases people flagged (all time, dismissed and resolved flags included). That table cross-references each phrase against the active glossary, so you can see at a glance which recurring complaints already have a term covering them and which still need one. ## 5. Settings Live Translate has no per-app configuration keys. Its behavior is governed by: | Setting | Where | Default | What it changes | |---|---|---|---| | App enablement | Admin → Apps → All Apps | Off | Adds Live Translate to your app list. Once enabled, it is admin-only until you publish it or give groups access (next row). **Disable** on the same page turns it off for everyone; to limit who can use it instead, unpublish it or narrow its groups under Access & Permissions | | Published to users | Admin → Apps → All Apps → **Live Translate** → **Access & Permissions** | Off | **Publish to everyone** lets every employee and manager open Live Translate; giving specific groups access limits it to those groups instead. With neither, only admins and people you add as the app's App admins or contributors can open it | | Translation provider | Admin → Organization → Integrations, category **Machine Translation (AWS Translate / DeepL)** | Platform managed | Which engine handles the translation step | | Glossary terms | Admin → Translation | None | Company terminology applied to Live Translate turns and the other surfaces that use the glossary (see **The company glossary**) | Glossary terms default to **Active** and **case-insensitive** matching when created. Flagged translations stay **Pending** until an admin adds a term from them or dismisses them. ### Sample data To explore the glossary and analytics without creating real terms, go to **Admin → Translation** and click **Load Sample Data**. This creates demonstration glossary terms and flagged suggestions you can experiment with, then remove when you are ready. ## 6. More help - **Live Translate FAQ** — specific setup and operating questions, limits, and troubleshooting - Ask AI — the assistant answers questions about Live Translate from these articles. **Keywords:** live translate, translation, interpreter, speech translation, glossary, terminology, do not translate, language barrier, paired session, two device, hands free, flag translation, starter pack, live-translate, live_translate --- # Live Translate FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-17 Answers to common setup and operating questions about Live Translate — for the admin running it. # Live Translate FAQ Answers to common setup and operating questions about Live Translate. For what the app is and how to set it up from scratch, see the [Live Translate Overview](/help/articles/live_translate_app_overview). --- ## Setup ## Do I need to configure a translation provider before my team can use it? No. If you connect your own provider (AWS Translate or DeepL) at **Admin → Organization → Integrations**, Live Translate uses it. Otherwise it falls back to a platform-managed engine automatically. Speech-to-text runs on the platform's OpenAI connection, so it must be available for a turn to run; if text-to-speech fails, the turn still arrives as on-screen text. ## How do I make Live Translate visible to employees after I enable it? Enabling the app at **Admin → Apps → All Apps** makes it visible to admins immediately. For employees and managers to see it, you also need to publish it to users — either globally or by setting up visibility rules for specific groups. Until you do, only admins and people you've added as the app's App admins or contributors can open it. An App admin or contributor can use Live Translate before it's published, but company terminology and flagged translations stay with company admins. --- ## Permissions and access ## Who can manage the glossary and view translation analytics? Only admins and super admins. The glossary and analytics live at **Admin → Translation**, which requires admin-level access. Employees and managers can use the interpreter and flag translations as wrong, but they cannot add, edit, or delete glossary terms or view the analytics dashboard. ## Why can't some of my employees see Live Translate? Three things must all be true: the app is enabled at **Admin → Apps → All Apps**, it is published to users (or the employee has an explicit visibility grant), and the employee's account is active in the organization. If all three are in place, check whether any visibility rules restrict access to specific groups. --- ## Day-to-day ## Does Live Translate store conversations? No conversation record is kept. Each turn is transcribed, translated, and spoken back in real time, the transcript appears on screen only while the conversation is open, and there is no transcript history to open afterwards. On a shared phone in **one device** mode, tap **Clear** when you're done so the next person who picks it up doesn't see the conversation; in **two devices** mode, **Leave session** clears it. Two qualifications, both worth knowing if you are answering a compliance question: - Tapping **Wrong?** on a turn deliberately saves that phrase and its shown translation to a review queue at **Admin → Translation**, so an admin can correct the glossary. This is the only durable copy. - In **two devices** mode, each turn travels to the other phone over OneMango's shared real-time message service, labelled with your organization's ID, and is deleted within roughly 90 minutes (a cleanup job runs every 30 minutes). Until then it holds the turn's text and audio. No screen in the product reads it — reaching it needs direct database access — and **one device** mode never uses it. ## How does the "Detect language" option work? In one-device mode, either side can be set to **Detect language** instead of a specific language. The app identifies the speaker's language automatically from their speech across all 15 supported languages. The side set to Detect must speak first, and both sides can't be set to Detect at once. In two-device (paired) mode, Detect is not available because each person's selection becomes the other person's translation target, so both must be set to a specific language. ## How do I add glossary terms in bulk? Go to **Admin → Translation**, choose the CSV file in the **Terminology** section, then click **Import CSV**. The file uses the same columns **Export CSV** writes, under this header row: ``` source_language,target_language,source_text,target_text,term_type,case_sensitive,active ``` `term_type` is `mapping` or `do_not_translate`. The last two columns are optional — leave them out or blank and a term imports as case-insensitive and active; otherwise put `true` or `false`. Save the file as CSV UTF-8 with commas between columns. The file must be under 1 MB and contain no more than 2,000 rows. Import only adds new terms: a row with the same source language, target language, and source text as an existing entry is skipped, even if you changed its translation in the file — edit existing terms in the list instead. To see the expected format, export your current glossary first. ## What are the industry starter packs? Three pre-built terminology sets you can adopt with one click at **Admin → Translation**: 1. **Warehouse & Manufacturing Safety** (English → Spanish) — 13 terms including lockout-tagout, PPE, and muster point 2. **Retail & Store Operations** (English → Spanish) — 9 terms including stockroom, planogram, and shrinkage 3. **Healthcare & Facilities** (English → Spanish) — 7 terms including shift handoff, charting, and isolation room Adopting a pack clones its terms into your glossary. You can edit or remove them freely afterward. A pack shows as already adopted once all of its terms exist in your glossary. ## How do I review flagged translations? Go to **Admin → Translation**. The **Flagged translations** section shows pending flags, oldest first (up to 50 displayed; the badge shows the true total). For each flag you can type the word that came out wrong into the empty **Term** box (the flagged sentence is shown above it as **Original:**), enter what it should translate to, and click **Add term** — which creates a glossary mapping and closes the flag in one step — or click **Dismiss** to close it without a term. If the card says a term can't fix it — the language wasn't recognised, or both sides were the same language — dismiss it instead. Dismissing doesn't delete the flag: its phrase still counts in the most-flagged phrases on the Analytics page. You receive an in-app notification when flags arrive (at most once per 6 hours) and an email digest (at most once per 24 hours). ## Can glossary terms be case-sensitive? Yes. Each term has a **Case-sensitive** option you can toggle when creating or editing it. When enabled, "PPE" matches only "PPE", not "ppe" or "Ppe". The default is case-insensitive matching. --- ## When something looks wrong ## "The app said it couldn't make out any speech" The app detected no speech in the recording. Common causes: a tap instead of a hold (the minimum hold is about 350 milliseconds), speaking too far from the microphone, or the microphone being muted at the OS level. In hands-free mode, an utterance shorter than 350 milliseconds is also discarded as a non-speech sound. ## "Microphone access is blocked" The browser refused Live Translate the microphone, usually because microphone permission is turned off for your OneMango site. Allow the microphone in the browser's site settings — on a phone, also check that the browser or app is allowed to use the microphone in the phone's settings — then try again. "No microphone was found on this device." and "The microphone is being used by another app — close it and try again." are the other two microphone messages; each says what to fix. "This browser can't use the microphone here. Open the page over https, or try another browser." is different: the page isn't on a secure (https) connection, or the browser or in-app view can't record audio. Open the site over https, or switch browsers. ## "Couldn't play automatically — tap Play again on the last message." The browser blocked the translation from playing on its own. The translation is still on screen; tap **Play again** on that turn to hear it. Play again stays available on the newest 10 turns. ## "Translation didn't go through — please try again." Speech recognition or the translation provider failed on that turn, most often a temporary provider problem. Try the turn again. If it keeps happening, check the **Translation engine** at the top of **Admin → Translation**: on MangoApps' managed engine (no provider of your own connected), contact MangoApps support. A provider your organization connected itself shows its own message instead — "Translation isn't set up correctly" or a usage-limit message — and the fix is in that provider's integration. ## "Taking too long — try again." On one device, a turn that hasn't come back within 60 seconds is abandoned. Try again, keeping the turn short. ## "You've reached the hourly limit for this feature" Each person can make 200 interpreter attempts an hour, shared between one-device and two-device mode. Every attempt that reaches the server counts — including one where no speech was heard — and the count resets at the top of each hour, UTC. Starting a two-device session has its own limit of 60 an hour. Both limits are per signed-in account, not per device or per session — so on one device, both speakers' turns count against the account that is signed in. ## "The translation used the wrong word for our equipment" The translation engine may not know your company's vocabulary. Add the correct term at **Admin → Translation**: create a **Mapping** with the source word and its correct translation, or a **Do not translate** rule for terms like brand names or product codes that should pass through untouched. The glossary applies on the very next turn with no restart or delay. ## "My partner can't join with the session code" A paired session code is 6 characters (letters and numbers) and expires after 2 hours. New codes leave out the letters O and I, so typing O for a zero or I for a one still finds the session. Only the first person to enter the code can claim the second seat — a third person is rejected even with the correct code. The joiner must also belong to the same organization, have access to Live Translate there, and join from that organization's own site. After 20 wrong codes in 10 minutes, that person can't join any session for up to 10 minutes. A link or QR code from the host only fills the code in: the same rules apply when they tap **Join**, and the person opening it has to be signed in to that organization first (the link brings them back to Two devices after they sign in). If joining still fails, have the host start a new session and share the fresh code. ## "The other person left." The full message reads "The other person left. If they don't come back, leave and start a new session." The other phone left the conversation — they pressed Leave, closed or navigated away from the page, lost their connection, or lost access to Live Translate. If hands-free was on, it switches off. The session stays open for the rest of its 2 hours, and only that same person can rejoin it with the same code — as long as they still have access. Otherwise, start a new session. If it was your own page that reloaded — a pull-to-refresh, or the phone reloading it after you switched apps — the start card offers **Rejoin session** with your code: tap it to take your seat back. The button stays only in that browser tab, only for you, and for up to 2 hours from when you were let in; **Leave session** removes it. If the session has ended by then, the page says so and the button goes away. ## "The session ended or expired. To keep talking, one of you starts a new session and the other joins with its code." Your turn was sent to a session that no longer accepts it: sessions last 2 hours from when they were started, and a session also refuses someone who can no longer take part in it. One of you starts a new session and reads or shows its code; the other joins with it. Both pressing Start makes two separate sessions, each waiting for the other. ## "Live Translate isn't available right now — the speech service isn't set up on this platform." This notice appears only when the platform's OpenAI connection — which runs speech-to-text and text-to-speech for every turn — isn't set up, and the app's buttons are disabled while it shows. Waiting won't clear it; contact MangoApps support. An outage looks different: there is no notice, and turns say "Translation didn't go through — please try again." ## "You no longer have access to Live Translate." / "Live Translate isn't available for your account." You see one of these when you try a turn or start a session on a page you opened earlier: the first when you aren't in Live Translate's audience any more — for example it was made admin-only, or your group lost access — and the second when your membership in this organization was deactivated. If Live Translate was turned off for the whole organization, the turn says "Live Translate was turned off for your organization." Hands-free switches off on any of the three. If you're outside the audience, reopening the page shows "You don't have access to Live Translate. Ask your administrator to make it available to you." An admin can publish Live Translate to you or your group, or reactivate your membership. ## "I can't see the Company terminology button" The **Company terminology** button appears only for admins and super admins. It opens **Admin → Translation** (the page titled "Translation"), where the glossary lives in the **Terminology** section. Employees and managers see the interpreter but not the button — this is by design, since only admins can manage terminology. --- ## Licensing and limits ## Does Live Translate require a license? No. Live Translate is pay-as-you-go with no license to purchase. An admin enables it at **Admin → Apps → All Apps**, and each turn's usage — speech-to-text, translation, and text-to-speech — draws your organization's AI credits (**Billing & Payments → AI**). The one exception is translation on a provider your organization connected itself (its own AWS Translate or DeepL account): that provider bills your account directly, so those characters draw no credits. By default turns keep running when the credits are used up, and what you use past your balance is invoiced. A turn is refused, with the limit's own message instead of a "try again", only when the credits are used up and **Keep AI running past your credit balance** is off (or your account is set to stop at zero), or when your organization's monthly AI budget or cap, or a person's own monthly AI limit, is reached. A new limit can take a few minutes to apply. ## What are the limits I should know about? | Limit | Value | |---|---| | Supported languages | 15, plus Detect in one-device mode | | Turns per user per hour | 200 | | Paired-session creates per user per hour | 60 | | Maximum audio upload per turn | 2 MB | | Maximum hands-free utterance | 15 seconds | | Paired session expiry | 2 hours | | Participants per paired session | 2 (host + one joiner) | | Glossary CSV import file size | 1 MB | | Glossary CSV import rows | 2,000 | --- ## More help - [Live Translate Overview](/help/articles/live_translate_app_overview) - Ask AI — the assistant answers Live Translate questions from these articles. **Keywords:** faq, live translate, translation, interpreter, glossary, terminology, paired session, hands free, language detection, speech translation, flag translation, wrong translation, rate limit, microphone, session expired, live-translate, live_translate --- # Locations, Departments & Org Structure **Category:** Business-configuration **Section:** Administration **Updated:** 2026-08-15 How to set up locations, define hierarchy levels, manage departments, and assign employees — the admin guide to organisational structure. # Locations, Departments & Org Structure ## 1. What it is Locations and Departments are the two organisational trees every admin configures before scheduling, leave, compliance, and most other apps work. Locations model where people work — from corporate headquarters down to individual stores, plants, or clinics. Departments model the functional groupings — Engineering, Nursing, Warehouse, etc. — independent of place. - **Access:** both surfaces live under the **Admin → Organization** section of the sidebar. Locations are at **Location Management**; departments are at **Departments**. Requires the Administrator or Super Admin role. - **What it is not:** Location Departments (floor, wing, unit sub-divisions within a single location) are a separate, opt-in feature gated by a business-level toggle — see §3. ## 2. Standing it up ### Locations 1. Go to **Admin → Location Management**. The page opens on the **Locations** tab showing physical locations. Five tabs are available: Locations, Map View, Hierarchy View, Levels, and Import/Export. 2. Go to the **Levels** tab first. Levels define the tiers of your location tree — for example Corporate → Region → District → Store. The platform creates four defaults (Corporate, Region, District, Location) when none exist. Mark at least one level as a **physical location** — this distinguishes real work sites from administrative groupings and controls which locations appear in scheduling, time clock, and geofencing. 3. If your organisation matches a common industry shape, click **Generate from Industry** on the Levels tab. Templates exist for retail, healthcare, manufacturing, hospitality, education, food & beverage, technology, finance, transportation, construction, and professional services — each creates six levels with appropriate names and physical-location flags. 4. Return to the **Locations** tab. Click **Add Location**. A location requires a name; physical locations also require an address. Assign it a hierarchy level and, if it is not a top-level location, a parent. 5. Assign employees to locations from the user's profile (Employment tab → Location) or in bulk via CSV import. Each user can belong to multiple locations; one is marked primary. **Silent-failure pairing:** a location assigned to a non-physical hierarchy level will not appear on the Locations tab (which filters to physical locations). It still exists and is visible on the Hierarchy View tab — but an admin who creates a store under a "Region" level and does not mark that level as physical will not see it where they expect. ### Departments 1. Go to **Admin → Departments**. The default view is a collapsible tree. 2. Click **Add Department**. Enter a name; optionally select a parent department to nest it, and assign a manager. 3. If starting from scratch, click **Load Industry Defaults** to seed a department tree for healthcare, retail, hospitality, or manufacturing. 4. Assign employees to departments from the user's profile or in bulk. Users can belong to multiple departments; one is marked primary. **Silent-failure pairing:** creating a department without assigning any employees to it means it exists in the tree but has no effect on scheduling groups, access scoping, or reporting — until someone is placed in it. ## 3. How it fits together **Location hierarchy (tree)** — locations form a single parent–child tree per business. A location's position in the tree is governed by its hierarchy level: a child's level number must be higher than its parent's (e.g. a Region at level 1 cannot sit under a Store at level 4). Circular references are blocked by validation. Each location inherits configuration from its parent or level when not set explicitly — timezone, work days, and jurisdiction all follow an inheritance chain. **Physical vs. administrative locations** — each hierarchy level carries a **Physical Location Level** switch. Locations assigned to a physical level represent real work sites and appear in the main Locations tab, on the map, and in scheduling. Locations at administrative levels (Region, District) are organisational groupings that exist only in the Hierarchy View. At least one level per business must be marked physical. When you assign or change a location's level, the location's own physical flag is derived from the level automatically. **Departments (organisational)** — departments also form a parent–child tree, independent of locations. Each department has a materialised path (e.g. `/1/5/12/`) that enables efficient subtree queries. Naming is unique among siblings: you can have "Admin" under both "Nursing" and "Finance", but not two "Admin" departments under the same parent. Departments carry a manager assignment; if none is set, the platform walks up the tree until it finds one. **Location Departments (opt-in)** — a separate concept from organisational departments. These are sub-divisions within a single physical location — floors, wings, units, zones, teams. They are disabled by default. An admin enables them at **Admin → General Settings → Location Departments** by turning on **Enable Location Departments**, which is off out of the box. Once enabled, you manage them inside each location's detail page. Location departments can only be created under physical locations. **Jurisdictions** — when a location is saved with a country, state, or city, the platform automatically resolves and links jurisdiction records. Jurisdictions connect locations to the compliance layer (labor law rules, employment law). The system matches against a built-in catalog of known jurisdictions and creates custom ones when a match is not found. **Scheduling teams** — the platform can automatically create scheduling groups (teams) from locations, departments, or the cross-product of both. This is controlled by three business-level settings: auto-create location teams, auto-create department teams, and auto-create location × department teams. When enabled, creating a new location or department also creates a corresponding scheduling group. ## 4. Running it ### Managing the location hierarchy 1. Go to **Admin → Location Management → Hierarchy View** tab to see the full tree. 2. Locations can be moved by editing them and changing their parent. The system validates that the new parent is at a higher hierarchy level and that the move does not create a cycle. 3. Bulk actions are available from the Locations tab: select locations and choose Update Level, Update Timezone, Update Work Days, Update Status, Mark Physical, Clear Physical, Change Parent, or Delete. ### Importing locations 1. Go to the **Import/Export** tab on Location Management. 2. Download the sample CSV for the expected column format (name, address, city, state, country, timezone, parent name, hierarchy level, geofence settings). 3. Upload a CSV file. The import runs as a background job and reports results. ### Configuring geofencing 1. Edit a location and enable **Enforce Geofence**. 2. Set latitude, longitude, and an allowed radius. The default radius is 100 metres (328 feet). 3. When geofencing is enforced, the platform uses Haversine-formula distance calculation to verify that clock-in/out events occur within the radius. ### Managing departments 1. The department index shows a tree view by default. Switch to a flat list view with the view toggle. 2. Drag-and-drop reordering is supported in tree view. 3. **Duplicate detection:** the platform automatically detects exact and near-duplicate department names (normalising for invisible characters, HTML entities, and spacing differences). A banner on the index page shows how many duplicate groups exist. Click through to review and merge. 4. **Merging:** select duplicate departments to merge. The merge reassigns all references — employees, goals, scheduling groups, recruiting jobs, succession plans — to the surviving department. The merge preview shows an impact count before you commit. Large merges run as a background job. 5. **Deleting:** deleting a department prompts you to handle its staff (reassign to another department or remove the assignment) and its children (move to parent, promote to root, or delete all). ### Importing departments Department imports now go through Smart Import: **Admin → Departments → Import** redirects to the platform importer with column mapping and a review step. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Location active | Location edit | On | Whether the location appears in pickers, scheduling, and reports | | Physical Location | Derived from hierarchy level | Off | Whether the location is a work site (shows on Locations tab, scheduling, geofencing) or an administrative grouping | | Enforce Geofence | Location edit | Off | Whether clock-in/out must occur within the allowed radius | | Allowed radius (metres) | Location edit | 100 | Geofence radius for clock-in/out verification | | Timezone | Location edit | Inherited from business | The timezone used for this location's schedules, shifts, and reports | | Inherit work days | Location edit | On | Whether work days follow the inheritance chain (location → level → business) or use a custom schedule | | Budget Usage Basis | Location edit | **Scheduled hours** | Whether labor budget tracking is based on scheduled hours, timecard hours, or both | | Enable Location Departments | Admin → General Settings → Location Departments | Off | Whether per-location sub-divisions (floor, wing, unit) can be created | | Department active | Department edit | On | Whether the department appears in assignment pickers and reports | ## 6. More help - **Users, Roles & Permissions** — how to assign users to locations and departments. - **Business Profile & General Settings** — business-level defaults that locations and departments inherit. - Ask AI — the assistant answers questions about locations and departments from these articles. **Keywords:** locations, departments, org structure, organizational departments, hierarchy levels, location levels, geofence, physical location, regions, districts, parent location, location departments, cost center, department manager, org chart, work days, timezone, jurisdiction, location import, department import, merge departments, duplicate departments --- # Lone Worker App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run Lone Worker — responder rosters, check-in schedules, SOS and floor-issue escalation, and the dead-man's switch that alerts your safety admins when the responder ladder runs out. # Lone Worker ## 1. What it is Lone Worker is a safety check-in and SOS escalation app for frontline workers. Workers confirm they are safe on a timed cadence; if they miss a check-in or tap the SOS button, an alert climbs an ordered responder ladder — push, SMS, and voice — until a human acknowledges it. - **Enablement:** Lone Worker is a licensed, admin-enabled app. An admin turns it on from **Admin → Apps → All Apps** and configures at least one responder roster before check-ins arm. An SOS raised with no roster still pages your safety admins as a break-glass fallback. - **What it is not:** Lone Worker does not track location continuously. It captures a single GPS reading at the moment an SOS is triggered, if the admin has left that setting on. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Lone Worker**, and enable it for your business. 2. Go to **Lone Worker → Responder Rosters** and create at least one roster. A roster is scoped to a **site** (location) or a **team** (scheduling group). Choose the scope from the grouped picker in the new-roster drawer. 3. On the roster detail page, add at least one **tier**. Each tier needs at least one responder and a set of notification channels (push, SMS, voice). A roster with no populated tier has nobody to notify. 4. **Check-in coverage starts from a roster, not the app toggle.** A worker's shift must resolve to an active roster before check-ins arm. Enabling the app without creating a roster does nothing — no workers will be prompted. 5. Optionally, go to **Check-in Schedules** and create a schedule for a site or team to override the default check-in interval and grace window. 6. Go to **Settings** to adjust defaults (check-in interval, grace window, escalation timeout) and to choose which optional features run. Location capture and the Safety Hub incident handoff are on by default; Live Assist video and wearable alerts are off until you turn them on. 7. To confirm it works: clock a worker in on a shift at a site that has a roster. Within one check-in interval the worker will see an **"I'm safe"** prompt on their **My Safety** page and receive an Inbox notification with push. The **Dashboard** will show the active roster count and any live alerts. **Silent-until-paired warning:** A roster scoped to a site only covers shifts at that site. A worker on a shift at a different site — or on a shift with no site at all — has no roster and will never receive a check-in. If you expected coverage and see none, verify the roster's scope matches the shifts you are running. **Who sees what:** The app sidebar has two groups. Every user with the app enabled sees **My Safety** and **Alerts** in the **Safety** group. **Dashboard** is there too for business admins, Lone Worker app administrators, anyone on a responder roster, and anyone either permission setting below covers; for everyone else, opening Lone Worker goes straight to **My Safety**. The **Manage** group shows only what the viewer is allowed to open: **Responder Rosters** and **Check-in Schedules** for people covered by the **Who can manage responder rosters & check-in schedules?** setting, **Analytics** for people covered by **Who can view safety analytics?**, and **Settings** for business admins and Lone Worker app administrators. Both permission settings default to admins and app administrators only. ## 3. How it fits together **Responder Roster** — the ordered list of people to contact when something goes wrong. Each roster is scoped to a site or a team. The most specific active roster wins: a team roster overrides a site roster. If no roster resolves, the alert routes to your safety admins as a break-glass fallback. A roster has one or more **tiers**, each with its own responders, notification channels (push, SMS, voice), and an acknowledgement timeout. The escalation engine walks the tiers in order: it notifies the first tier, waits for the timeout, and if nobody acknowledges, climbs to the next. A tier marked **Break-glass** also notifies your safety admins on top of its own responders. Safety admins are every business admin unless you pick a group under **Settings → Escalation → Safety admins** (only group members who are business admins or Lone Worker app admins are paged, since only they can open the alert and respond to it; a group with nobody like that in it falls back to every business admin, so the page is never lost). > **Worked example:** A warehouse has a roster named "Warehouse Night" scoped to the night-shift site. Tier 1 is the floor supervisor (push + SMS, 120-second timeout). Tier 2 is the safety manager and the site lead (push + SMS + voice, 120-second timeout). Tier 3 is break-glass. A worker triggers an SOS → the floor supervisor's phone buzzes. Two minutes pass with no acknowledgement → the safety manager and site lead receive push, SMS, and a voice call. Two more minutes → the break-glass tier fires: the safety admins are notified across all three channels. The climb stops the instant anyone acknowledges — for 60 minutes. If no outcome is recorded in that time, the alert goes back to the tier it was on and pages it again. **Check-in** — a timed "I'm safe?" prompt armed automatically when a worker clocks in on a covered shift (a shift whose site or team resolves to an active roster). The interval and grace window come from a **check-in schedule** for the site or team, or from the app-wide defaults if no schedule exists. When a worker answers, the next check-in is re-armed immediately. When the grace window lapses without an answer, a **missed check-in** alert fires through the same roster escalation as an SOS. Check-ins stop at the shift's scheduled end, even if the worker is still clocked in, and the worker is sent a notice saying so; their SOS keeps working. Check-ins are armed and cancelled by the clock-in/out hook and by a background sweep that runs every five minutes. The background sweep also sends the worker an Inbox/push notification when their check-in is coming due, so they do not have to keep the My Safety page open. **Check-in Schedule** — an optional per-site or per-team override of the default check-in interval and grace window. Only one schedule per site or team is allowed. When no schedule covers a shift, the app-wide defaults apply. Schedules are managed under **Lone Worker → Check-in Schedules**. **Alert** — the escalation record. Alerts are raised by three triggers: - **SOS** — one-tap emergency from the worker's My Safety page or the mobile app. Only one active SOS per worker at a time; a second tap while one is live does not restart the ladder. - **Missed check-in** — raised automatically when a check-in's grace window closes without an answer. - **Floor issue** — a worker-reported equipment or line problem ("Report a floor issue" on My Safety). Follows the same roster escalation but does not capture GPS. An alert ends in one of two terminal states: **resolved** (safe, false alarm, or incident) or **exhausted**. An alert is exhausted when the responder ladder runs out with no outcome recorded — nobody acknowledged in time, an acknowledgement lapsed and nobody took it again, or the responder who acknowledged it handed it back (or left the roster) with nobody on that tier or above left to alert — and that fires the dead-man's switch. One more case ends as exhausted without paging anyone: an acknowledgement still open after 24 hours is closed automatically. An exhausted alert can still be resolved: open it and record what happened. **Dead-man's switch** — if the entire ladder runs out with no outcome recorded, your safety admins are notified in the app and by push, email, SMS, and voice call. No Lone Worker setting turns it off. The in-app, push and email notices follow each admin's own notification settings for **Safety Hub & Lone Worker**; the text message (to a verified mobile number) and the phone call go out whatever those settings say, as long as texts and calls are on for your organization. **Safety Hub handoff** — when a responder resolves an alert as **Incident**, Lone Worker can open a Safety Hub incident automatically (on by default; controlled by a setting). The incident inherits the alert's location, shift, and worker. A floor-issue alert that resolves as an incident is categorised as an equipment failure; all other triggers are categorised as security. **My Safety** — the worker-facing surface at **Lone Worker → My Safety**. Workers see: - Their active check-in prompt with an **"I'm safe"** button (always visible while a check-in is armed, not only when due). - A one-tap **SOS** button. - A **Report a floor issue** button for equipment or line problems. A short note describing the problem is required. - Their recent alert history (last five alerts). - Their currently active alert, if any. On mobile devices this page redirects to the mobile-optimised view at **/m/apps/lone-worker**. **Audit trail** — every alert records an append-only event log: raised, each tier notified (with per-channel delivery outcome), acknowledged, resolved, and exhausted. These events are never modified or deleted. They are visible on the alert detail page and exportable as CSV for EHS or regulator review. ## 4. Running it ### Reviewing the dashboard Go to **Lone Worker → Dashboard**. The dashboard shows four counts: **Open alerts** (raised, notifying, or acknowledged), **Resolved today**, **Escalation exhausted** (exhausted alerts with no outcome recorded yet), and **Active rosters**. Below the counts is the **Open alerts** table — the 25 most recent, with **View all open** for the rest. When nothing is open, an admin sees **No open alerts — everyone's accounted for** (or, while no real roster exists yet, a prompt to create one). If exhausted alerts still have no outcome, it says **No alert is climbing the ladder — but exhausted alerts still need an outcome** instead, with a link to them. Admins and app admins see all alerts across the business. Other users see only their own alerts and alerts on rosters where they are listed as a responder. ### Responding to an alert When notified (push, SMS, or voice), open the deep link to the alert detail page. The alert shows the worker's name, the trigger type, any note the worker attached, the location (if captured), and the full event timeline. Select **I've got this — acknowledge** to acknowledge the alert and take ownership. Everyone else who was paged is told to stand down, and the climb holds for 60 minutes. Record the outcome within that time, or the alert goes back to its tier and pages it again. If the **Open a live video channel to the responder when an alert is acknowledged** setting is on, a Live Assist video session opens automatically so the responder can see the worker's camera. It applies to every alert that is acknowledged, not only an SOS. Then resolve the alert with an outcome: - **Safe** — the worker is confirmed safe; the alert closes. - **False alarm** — accidental trigger; the alert closes. - **Incident** — a real safety event occurred. A note is required. If the Safety Hub handoff setting is on, a Safety Hub incident is created automatically. A worker cannot acknowledge their own alert — that would stop the climb with nobody coming. A worker who is not a responder can close their own alert only as **False alarm**. A worker who is also a responder on the alert's roster, a business admin, or a Lone Worker app admin can record any outcome on their own alert, like any responder — they still cannot acknowledge it. ### Filtering and exporting alerts Go to **Lone Worker → Alerts**. The alert index supports filtering by state (Open, Active, Acknowledged, Resolved, Exhausted — Open is raised, notifying, or acknowledged), trigger type, date range, and individual worker. The same filters apply to the CSV export. Admins, app admins, and anyone on a responder roster can export a CSV of the filtered alert list. Each row records the alert id, trigger type, any trigger note, worker, state, resolution, raised/acknowledged/resolved timestamps, and linked Safety Hub incident id. The export is scoped to the viewer's own purview — a non-admin responder's CSV contains only alerts they could already see on the index page. ### Managing rosters and tiers Go to **Lone Worker → Responder Rosters**. From the roster detail page you can add and remove tiers, add and remove responders on each tier, set per-tier notification channels and acknowledgement timeouts, and mark a tier as break-glass. **Edit** renames a roster or changes the site or team it covers, and **Delete** removes it along with its tiers. There is no switch to pause a roster. When adding a responder to a tier, each person can appear on that tier only once. A responder who is also a business admin will not be double-notified on a break-glass tier. ### Viewing analytics Go to **Lone Worker → Analytics** (visible to the people the **Who can view safety analytics?** setting allows — admins and app administrators by default). Analytics shows business-wide totals only, with no worker names, locations or notes. The page shows total alerts, acknowledged rate, average acknowledgement latency, exhausted-but-open count, check-in completion rate, and a 14-day alert volume chart. An analytics CSV export is also available. ### Loading sample data Go to **Lone Worker → Settings** and select **Load Sample Data** to populate responder rosters, check-in schedules, check-ins, and alerts with realistic demo data — recent activity plus alert history going back several months. Loading runs in the background and can take a few minutes. Sample data never fires real notifications and can be taken out with **Remove Sample Data**, which also removes any Safety Hub incident created by resolving a sample alert as an incident. ## 5. Settings All settings are at **Lone Worker → Settings** (admin or app admin only). | Setting | Default | What it changes | |---|---|---| | **Enable the Lone Worker AI Agent in Ask AI** | On | Whether the Lone Worker agent answers questions in Ask AI and can acknowledge an alert for you, or hand back your acknowledgement (it always asks first). | | **Who can manage responder rosters & check-in schedules?** | Admins and app administrators only | Who can create, edit and delete responder rosters, tiers and responders, and check-in schedules. You can widen it to every manager, or add specific groups. Anyone allowed here can add themselves to a roster, and a roster's responders see its alerts. | | **Who can view safety analytics?** | Admins and app administrators only | Who can open Analytics and its CSV export. You can widen it to every manager, or add specific groups. Analytics never shows worker names, locations or notes. | | **Default check-in interval** | 60 minutes | How often a worker is prompted "I'm safe?" when no site/team schedule overrides. | | **Default grace window** | 10 minutes | How long after a check-in is due before a miss fires an alert, when no schedule overrides. | | **Default acknowledgement timeout per tier** | 120 seconds | How long a tier waits for an acknowledgement before climbing to the next tier, when the tier does not set its own. | | **Open a Safety Hub incident when an alert resolves as "Incident"** | On | Whether resolving an alert as Incident automatically creates a Safety Hub incident record. | | **Capture device location when an SOS is triggered** | On | Whether the worker's device GPS is captured once, at trigger time, and attached to the alert. | | **Open a live video channel to the responder when an alert is acknowledged** | Off | Whether acknowledging an alert opens a Live Assist video session between the worker and the responder. Requires the Live Assist app and a configured LiveKit provider. | | **Let wearable & IoT devices raise alerts** | Off | Whether events from a connected wearables integration (badge presses, panic buttons, line sensors) can raise alerts and page responders. An admin connects a device platform under Admin → Integrations → Wearables & IoT (signing secret, fallback worker, and the webhook URL to give the vendor); until it is connected and this is on, device events raise nothing. | ## 6. More help - **Lone Worker FAQ** — specific setup, operating, and troubleshooting questions. - Ask AI — the assistant answers questions about Lone Worker from these articles. **Keywords:** lone worker, lone worker safety, SOS, panic button, safety check-in, check-in schedule, responder roster, escalation, dead-man's switch, floor issue, missed check-in, worker safety, safety alert, lone-worker, lone_worker --- # Lone Worker FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Lone Worker — for the admin running it. # Lone Worker FAQ Answers to common setup and operating questions about Lone Worker. For what the app is and how to set it up from scratch, see the [Lone Worker Overview](/help/articles/lone_worker_app_overview). --- ## Setup ## What do I need to configure before check-ins start? Two things: a responder roster and, optionally, a check-in schedule. A shift is "covered" — meaning timed check-ins arm automatically when a worker clocks in — only when a responder roster resolves for that shift's site or team. Without a roster, check-ins will not arm, and a worker's SOS will route to the break-glass safety-admin broadcast instead of a named responder ladder. You can also create a check-in schedule for a site or team to override the tenant default cadence. If you skip the schedule, check-ins use your tenant's default interval and grace window (set in Settings). ## Who can manage rosters, schedules, and settings? Settings are restricted to business admins and Lone Worker app administrators. Rosters and check-in schedules follow the **Who can manage responder rosters & check-in schedules?** setting, and Analytics follows **Who can view safety analytics?**. Both default to admins and app administrators only; each can be widened to every manager, or to groups you choose. Anyone allowed to manage rosters can add themselves as a responder, so widen that one with care. --- ## Permissions and access ## Why can't some employees see the Lone Worker app? The app must be both enabled and licensed for your business, and accessible to the employee. If you use Access Management to restrict the app to specific groups, employees outside those groups are blocked on both the web and the API. Check the app's access settings in Admin → Apps → All Apps. ## Who can see which alerts on the dashboard? Admins and Lone Worker app admins see every alert across the business. Everyone else sees only their own alerts plus alerts on rosters they belong to as a responder. This scope also applies to the Alerts list and the CSV export. The dashboard's Open alerts table shows who has a live SOS or overdue check-in, so it is never served business-wide to a regular member. A worker who is on no responder roster and is not covered by either permission setting has no dashboard at all: opening Lone Worker takes them to **My Safety**, and their sidebar shows My Safety and Alerts. --- ## Day-to-day ## Which roster applies when a worker triggers an SOS or misses a check-in? The most specific active roster wins: a roster scoped to the worker's team is checked first, then one scoped to their site. If nothing resolves, the alert routes to a break-glass broadcast — your safety admins are notified over push, SMS, and voice. Safety admins are every business admin unless you pick a group under **Settings → Escalation → Safety admins**; only group members who are business admins or Lone Worker app admins are paged, since only they can open the alert and respond to it, and a group with nobody like that in it falls back to every business admin. That fallback is always on; a missing roster never swallows an alert. ## What happens when a worker misses a check-in? If a worker does not tap "I'm safe" before the due time plus the grace window elapses, the check-in is marked missed and an alert is raised automatically. That alert climbs the responder ladder exactly like an SOS. No one has to monitor a board — the system detects misses every minute. ## Can a worker cancel their own SOS? Yes, as a false alarm. A worker can close their own alert with the **False alarm** outcome. They cannot acknowledge it — acknowledgement must come from someone else, because acknowledging your own alert would stop the escalation ladder with nobody coming. Responders and admins can resolve an alert with any outcome: **Safe**, **False alarm**, or **Incident**. That includes their own alert: a worker who is also a responder on the alert's roster, a business admin, or a Lone Worker app admin can record any outcome on it. ## I acknowledged an alert but can't attend — can I hand it back? Yes. On the alert page, **Hand it back — I can't take this** puts the alert back on its responder ladder at the same tier: everyone else on that tier is alerted again (not you), or, when nobody else is on it, it climbs to the next tier at once. On the last tier that sends it to your safety admins through the dead-man's switch. The worker is told, and the alert's history records who handed it back. Only the responder who acknowledged it, or a safety admin (whose button reads **Release 's acknowledgement**, and the acknowledger is told), can do this; Ask AI can do it for you after you confirm. An acknowledgement held by someone taken off the roster, or who leaves the organization, goes back the same way on its own. ## What happens when I resolve an alert as "Incident"? A note is required. If the **Open a Safety Hub Incident** setting is on (on by default), resolving as "Incident" automatically creates a Safety Hub incident record. Floor-issue alerts produce an equipment-failure incident; all other trigger types produce a security incident. The Safety Hub handoff is best-effort — if it fails, the alert still resolves and the failure is logged. ## How do wearable and IoT device alerts work? Devices (RFID badge presses, push-to-talk panic buttons, line sensors) POST events to a signed webhook endpoint. Each event must be signed with the integration's HMAC-SHA256 secret. To protect deliveries from being replayed, the device platform can send an `X-Signature-Timestamp` header (Unix seconds) and sign `.` instead of the body alone: a delivery more than five minutes old is then refused, and once an integration has sent a timestamp, every later delivery must carry one (changing the integration's signing secret resets that). The device event is attributed to a worker by badge ID; if no badge matches, it falls back to the integration's fallback user. If that person has left, the event is still raised under their name — it pages your safety admins — and the integration's page says to pick a current person. An admin connects a device platform under **Admin → Integrations → Wearables & IoT**: enter a webhook signing secret (the same value goes on the device platform), optionally pick a fallback worker, save, and give the device platform the webhook URL the integration then shows. The integration's page also says how the last device delivery went — accepted, or refused and why. Device alerts also stay off until an admin turns on **Let wearable & IoT devices raise alerts** in **Lone Worker → Settings**. Events with neither a matching badge nor a fallback user are rejected. Accepted events raise an alert on the same responder ladder, acknowledgement flow, and audit trail as a phone-raised SOS or floor issue. A fall or man-down the device detects on its own raises an SOS that the worker sees as **Fall detected** or **Man-down detected**, not as an SOS they pressed; when the device sends no message with it, responders see the same words as the alert's note. --- ## When something looks wrong ## I tapped SOS and nothing happened — what's going on? If you already have an active SOS, a second tap is blocked to prevent restarting the escalation ladder from tier 1. You should see a message confirming your SOS is already active. If you see an error instead, the alert could not be saved — call your local emergency number if it is an emergency. Location capture is best-effort: a missing or denied location permission does not block the SOS. ## My check-in keeps saying "Are you safe?" even after I answered The "I'm safe" button is always visible while you have an armed check-in, even when it is not yet due. The prompt text ("Are you safe? Due by…") clears the moment your answer is recorded, but the button stays so you can confirm safety any time. If the prompt text reappears quickly, your site or team may have a short check-in interval — ask your admin to check the schedule. ## Check-ins are not arming for workers who are on shift Four things must all be true for a check-in to arm: the Lone Worker app is enabled for your business, the worker has clocked in (an active attendance record exists), the shift has not reached its scheduled end, and a responder roster resolves for the shift's site or team. If any is missing, no check-in is armed. Check-ins stop at the shift's scheduled end even when the worker is still clocked in, and the worker is sent a notice when they do — extend the shift to start them again. The most common cause is a missing roster — create one scoped to the site or team and check-ins will start arming on the next clock-in. ## The dead-man's switch fired — what does that mean? It means an alert ran out of responder tiers with no outcome recorded — nobody acknowledged it in time, an acknowledgement lapsed and nobody took it again, or the responder who acknowledged it handed it back (or left the roster) with nobody on that tier or above left to alert. The dead-man's switch broadcasts to your safety admins (every business admin, unless you picked a Safety admins group in Settings) in the app and over push, email, SMS, and voice. No Lone Worker setting turns it off. Its in-app, push and email notices follow each admin's own notification settings for **Safety Hub & Lone Worker**; the text message (to a verified mobile number) and the phone call go out whatever those settings say, as long as texts and calls are on for your organization. Intervene immediately: open the alert in Lone Worker and record what happened to close it — an exhausted alert can no longer be acknowledged, only resolved. If no roster was configured, the break-glass reached your admins directly. --- ## Licensing and limits ## Does Lone Worker require a licence? Yes. An admin enables and licenses the app from Admin → Apps → All Apps. Enabling the app does not start check-ins on its own — a responder roster must also be configured before any shift is covered. ## What are the configurable ranges and limits? | Setting | Default | Allowed range | |---|---|---| | Check-in interval | 60 minutes | 5–480 minutes | | Check-in grace window | 10 minutes | 1–120 minutes | | Acknowledgement timeout per tier | 120 seconds | 30–1,800 seconds | | Notification channels per tier | Push, SMS | Push, SMS, Voice (any combination) | | Floor-issue / SOS note | — | Up to 280 characters | | Alert audit-trail CSV export | — | Up to 10,000 rows per export | | Stale armed check-in cutoff | 24 hours | Fixed (armed check-ins more than 24 hours past due are cancelled without raising an alert) | | Escalation driver cadence | Every minute | Fixed | | Missed-check-in detector cadence | Every minute | Fixed | | Check-in scheduler cadence | Every 5 minutes | Fixed | --- ## More help - [Lone Worker Overview](/help/articles/lone_worker_app_overview) - Ask AI — the assistant answers Lone Worker questions from these articles. **Keywords:** faq, lone worker, SOS, safety check-in, responder roster, escalation, dead-man's switch, floor issue, wearable, check-in schedule, acknowledgement timeout, not showing, missed check-in, permissions, lone-worker, lone_worker --- # Loop App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-09 How Loop measures whether a change you made actually worked — plans, the measurement ledger, owner decisions, who gets in, and the settings an admin controls. # Loop ## 1. What it is Loop tells you whether a change you made actually worked. You name the change and the number it should move. Loop takes a baseline from the day the change took effect, scores the same number afterwards, and waits for a named owner to decide what happens next. It is built for the people who run improvement work: admins, and managers if you let them in. - **Enablement:** Loop is licensed. If your plan includes it (Platform Standard or Enterprise), it is already available to admins, and the weekly notice in section 5 (Settings) is already on, until an admin disables the app. On any other plan it is off until an admin enables it. Either way only admins see it until manager access is turned on. - **What it is not:** Loop is not where you pause the AI. Pause All AI, Resume All, the approvals queue and action history live under **AI Operations** in the admin sidebar (`/admin/automation-hub`). They are there whether or not Loop is enabled. ## 2. Standing it up 1. In the admin sidebar, open **All Apps**, choose **Loop**, and click **Enable App**. Skip this step if Loop already appears in your sidebar — your plan includes it. 2. Open Loop. As a business admin you see eight tabs: **Overview**, **Portfolio**, **Quarterly Review**, **Automations**, **Playbook Runs**, **AI Outcomes**, **AI Suggestions** and **Settings**. 3. Decide who else gets in, under **Settings**. Admins and Loop app admins always have access. Managers have none until a company admin turns on **Let managers use Loop for the locations they manage**. 4. Click **Make a plan** on the Overview and fill in the plan form (see the worked example in §3). Click **Save plan**. 5. Confirm it worked: the plan appears in the **Measurement ledger** with a status such as **Measuring (30d)**. A plan backdated past its window is scored at once and shows **Measured**, or **Inconclusive** when the window held too little data to score. If you saved it as a draft, it appears under **Not live yet** instead. Two pairings do nothing until the second half is in place: - **Manager access needs Access Management too.** The switch makes managers eligible. Access Management decides which of them see Loop. Saving the switch on publishes Loop to your users if it was not already published. The Settings page then tells you which state you are in: all managers can open Loop, only managers in the restricted groups can, or no manager can because Loop is not published. Change the audience in **Apps → Loop → Manage User Access**. - **Automatic reviews need an owner who can open Loop.** Some apps open a plan for you, such as a recurrence review when a safety corrective action is completed. A safety recurrence review or a succession coverage review is opened only when the person responsible can open Loop. While manager access is off, that means a Loop admin, and a manager's completed action is skipped quietly. Contest and RFP Desk plans go to a business admin instead when their author cannot open Loop. To see the Overview, Portfolio and Quarterly Review filled before real results exist, click **Load sample stories** on the empty Overview, or **Load Sample Data** at the bottom of Settings. ## 3. How it fits together ### A plan, a measurement and a decision These three are easy to run together. They are separate records with separate owners. - A **plan** is your promise: what changed, which number it should move, and which way. A person writes it. - A **measurement** is Loop's reading of that number: the level before the change, the level after, and the difference. Loop produces it; nobody types it in. - A **decision** is the owner's call on a measured result: **Keep**, **Adjust**, **Expand**, **Retire** or **Roll back**, with a reason. **Expand** is offered only when the plan's number can be measured at a single location and the plan is not already a pilot (a plan you already decided to Expand keeps the choice). A good number promotes nothing by itself. A worked example, using the plan form's own fields: | Field | Value | |---|---| | What changed? | Two-person closing shift at the flagship store | | Is it live? | Yes — it took effect on the date below | | Metric to watch | The number you expect the change to move | | What do you expect this number to do? | Go down | | By how much? (optional) | 20 | | Measurement window | 30 days | Loop compares the 30 days after the change with the 30 days before it. Suppose the number was 10.00 before and 7.50 after. The ledger row shows a delta of **-2.50**, the line "from 10.00 to 7.50", and the badge **Hit the plan**, because a 25% fall beats the 20% you promised. The owner then sees a **Decide** button on that row. ### How a plan is judged The plan badge compares what you predicted with what happened: - **Hit the plan** — the number moved the way you said, by at least the amount you named. With no amount named, the right direction is enough. - **Fell short of plan** — right direction, less than the amount you named. - **Didn't move** — no change at all. - **Moved the wrong way** — the opposite of your prediction. Color follows improvement, not arithmetic. A number that should fall and does fall shows green. ### Status is not the verdict Each ledger row also carries a status, which says how far the reading has got: **Measuring**, **Measured**, **Inconclusive** or **Failed**. Only a **Measured** row can carry a plan badge or be decided. **Inconclusive** means the window closed with too little signal to call, and the row says why. ### Drafts, rechecks and versions - A **draft** is a plan saved with **Not yet** under **Is it live?**. Nothing is measured until its owner enters the real date and clicks **It's live**. - A **recheck** is a second reading that Loop starts when the owner decides **Keep** or **Expand**. It uses the same window length and asks whether the change is still holding. Rows carry a **Recheck** badge. - A **version** is what **Adjust** produces. The next version opens prefilled, and the **Thread** link shows every attempt on one page. ### Plans you did not write A ledger row is not always a plan someone typed. The badge before the title says what was measured. Sample rows carry a **Sample** badge in front of it. - **Plan** — a change someone declared with a prediction. - **Change** — a plan opened with no stated prediction, such as a safety recurrence review. It is measured but gets no plan badge. A plan that an automation or a contest opened with a direction shows **Plan** and is judged like any other. - **Pilot** — a kept change being tried at another location. - **Lesson** — a Muscle Memory lesson being measured. - **Suggestion** — an AI suggestion that someone acted on. - **Action** — a completed Mango Signal action. The empty Overview lists the apps whose completed work starts a measurement by itself. Safety Hub, RFP Desk, Contests and Succession Hub open a plan. Mango Signal, Muscle Memory and Service Desk add a measurement of an action, a lesson or an acted-on suggestion, with no plan behind it. An automation that was given a number to move opens a plan too. ### Loop and Muscle Memory The two are siblings and are often confused. Muscle Memory is what the business remembers: lessons distilled from work that already closed. Loop is how the business tests a change: a baseline, a result and a decision. A lesson can be measured in Loop, and Loop's **The loop** card links to your active lessons. Neither app replaces the other, and each is enabled separately. ### What Loop hosts, and what stays in admin Loop hosts four admin pages as tabs: **Automations**, **Playbook Runs**, **AI Outcomes** and **AI Suggestions**. While Loop is enabled, their old admin addresses send admins into the Loop tabs, so each page has one home. These four tabs need a business admin. A Loop app admin without that role sees Overview, Portfolio, Quarterly Review and Settings only. The control side never moved. **AI Operations** keeps Overview, Approvals, Action History, Playbooks, Agents, Channels, Agent Settings and Trust & Safety in the admin sidebar. When Loop is not enabled, Automations and AI Outcomes appear there too. ## 4. Running it ### Decide a measured plan 1. Open **Overview** and find the row with a **Decide** button in the **Measurement ledger**. 2. Click the metric name under **Measures** to open its receipt, if you want the comparison windows behind the result. 3. Click **Decide**, choose a decision, and fill in **Why? (recorded with the decision)**. 4. Click **Record decision**. Only the plan's owner or a Loop admin sees **Decide**. Everyone else who can read the row sees "Awaiting" and the owner's name. ### Work the Portfolio **Portfolio** groups every improvement by what it needs from you: **Needs attention**, **Awaiting decision**, **Closed without a result**, **Trying again**, **Piloting in a new scope**, **Measuring**, **Not live yet**, **Adopted and holding**, and **Retired or rolled back**. Start at the top. A kept change in the holding group can be published for reuse with **Save as pattern**. ### Act on an opportunity card When your own data supports one, the Overview shows an **Opportunities** card for admins. Each card ends in an action such as **Make a plan**, **Record the fix** or **Invite a pilot**. Use **Dismiss…** to remove a card for good or to **Snooze 30 days**. ### Take a review to leadership Open **Quarterly Review** for the improvement program by its decision record: what was planned, what was proven, and what was decided. Click **Print / save as PDF** to hand it on. For one plan, the receipt and the thread link to an evidence pack that prints the change, its measurements and its decision. ### Author automations Business admins create and edit automations on the **Automations** tab and follow their executions on **Playbook Runs**. A kept plan with no automation offers **Create an automation** on its ledger row. A retired or rolled-back plan whose automation is still running offers **Pause its automation**. ### What managers and phones see A manager admitted to Loop gets the **Overview** tab alone, with a ledger limited to their own plans and their locations. On a phone, the Overview opens a mobile view with opportunities and the most recent measurements. Making and deciding plans, Portfolio, Quarterly Review, Settings and the four hosted tabs stay on desktop. ## 5. Settings All settings are at **Loop → Settings**. Loop admins can open the page; two switches are reserved for company admins and show as disabled for anyone else. | Setting | Who can change it | Default | What it changes | |---|---|---|---| | Let managers use Loop for the locations they manage | Company admin | Off | Makes managers eligible for Loop, and publishes Loop to your users when turned on | | Ask Loop advisor in Ask AI | Loop admin | On | Offers the Ask Loop advisor in the Ask AI sidebar to everyone who can open Loop | | Weekly improvement-openings notice | Loop admin | On | Sends one in-app notice a week, on Monday at 14:00 UTC, naming the openings that are new since the last notice | | Who receives it | Loop admin | Loop's admins (app-admin grants, else every business admin) | Sends the weekly notice to a group you pick instead; applies only while the notice is on | | Earned autonomy | Loop admin | Off | Lets Loop take the next step for practice types that earned it from your own decisions | | Share anonymized evidence | Company admin | Off | Counts your organization in cross-customer proof shown on pattern cards | Three things on the page are not switches: - **Earned tiers** lists each practice type with its tier — **Observe**, **Propose** or **Act** — and the evidence behind it. Tiers are computed from your decision record and cannot be set by hand. Loop has no AI-mode dial. - **Ask Loop** lists what the advisor can do. Every answer ends in a ready-made plan that a named person must commit. - The sample-data card holds **Load Sample Data** and **Remove Sample Data**. Sample rows are always labeled **Sample**. ## 6. More help - **Loop FAQ** — specific setup and operating questions, exact limits, and what to check when something is not showing. - **Muscle Memory App Overview** — the sibling app that holds the lessons Loop can measure. - **Ask AI** — the assistant answers questions about Loop from these articles, and Ask Loop answers "what should we do about…?" from your own numbers. **Keywords:** loop, make a plan, measurement ledger, did the change work, baseline, plan verdict, keep or roll back, recheck, portfolio, quarterly review, automations, playbook runs, ai outcomes, ai suggestions, ai operations --- # Loop FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-01 Answers to common setup and operating questions about Loop — for the admins and managers running it. # Loop FAQ Answers to common setup and operating questions about Loop — what it is, how to set it up from scratch, and what to do when something is not showing. --- ## Setup ## Do I have to turn Loop on before anything gets measured? Yes. Loop needs a licence, and an admin enables it from Admin → Apps → All Apps. It is off in every organization until someone opts in. Until then nothing is recorded and nothing is measured, including the measurements other apps would otherwise start for you. ## Who can open Loop once it is enabled? Business admins and anyone holding the App admin badge for Loop, always. Managers can use Loop too, but only once a company admin turns on **Let managers use Loop for the locations they manage** in Settings. That switch is off by default, and it makes managers eligible: Access Management decides which of them see Loop. Everyone else can't open Loop. ## Is the Ask Loop advisor switched on already? Yes — **Ask Loop advisor in Ask AI** is on by default. It answers "what should we do about X?" in the Ask AI sidebar, grounded in your own numbers. Every answer ends in a plan a named person still has to commit; the advisor never creates anything itself. It follows the same access rule as the app, so a manager reaches it only when they can open Loop. --- ## Permissions and access ## Why does a manager only see part of the ledger? By design — a manager sees only the measurements they are responsible for. That means plans they own or declared themselves, plans scoped to a location they manage, and suggestions they personally acted on. Admins see the whole organization. Managers also do not get the pipeline card, because it is an organization-wide shape. ## Why can't a Loop app admin open Automations, Playbook Runs, AI Outcomes or AI Suggestions? Those four tabs need a business admin role, and the App admin badge for Loop is not one. Someone holding only the badge sees Overview, Portfolio, Quarterly Review and Settings. The other four tabs are hidden from them rather than shown and then refused. Give them the business admin role if they need those pages. ## Who is allowed to record the decision on a plan? The plan's named owner, or a Loop admin acting on their behalf. Anyone else who can see the plan, such as the person who created it or the manager of its location, can read it and its receipt but cannot decide it. The same rule governs cancelling a plan, confirming its go-live date and inviting a pilot. Saving a kept plan as a reusable pattern is for Loop admins only, because it changes the pattern gallery for everyone. --- ## Making and measuring plans ## How far back can I date a change we already made? Up to 90 days. Loop takes its baseline from the day the change actually took effect, so a date further back would measure a different organization. Future dates are refused too — declare the change when it genuinely goes live. ## How long does Loop watch a number before it reports a result? 30 days by default; the plan form also offers 60 and 90 days. The result is computed on the overnight scoring run, shortly after 03:30 UTC, once the window has fully elapsed. So a 30-day plan reports on the morning after day 30, not on day 30 itself. ## Can I change a plan's metric or window after it has started? No — a plan cannot be edited once created. If you got it wrong, use **Cancel plan** on the ledger row, give a reason, and make a new one. Nothing is deleted: the cancelled plan stays on the record with your reason, and its open measurement closes as inconclusive. You can cancel only until the plan has a result; after that, record a decision instead. ## What are my choices when a result comes in? Up to five, each recorded with your reasoning: **Keep**, **Adjust**, **Expand**, **Retire** and **Roll back**. Expand is offered only when the plan's number can be measured at a single location and the plan is not already a pilot (a plan you already decided to Expand keeps the choice). Keep and Expand leave the change in force and start a recheck, so a change that quietly stops working reopens itself for review. Adjust immediately opens the next version of the plan, prefilled, with the expectation reset. --- ## When something looks wrong ## Why won't Loop let me record a decision on my plan? Decisions wait for evidence — a plan with no measured result yet offers only **Cancel plan**. This is enforced on the server, not just hidden in the page, so the button will not appear early for anyone. Wait for the window to close, or cancel the plan if it was a mistake. ## Why did our result come back inconclusive? The window closed with too little data to call honestly. Most metrics need at least 5 records in the measurement window; a few low-volume ones set a higher bar of their own. The receipt states the actual count and the bar it missed, so you can pick a longer window or a busier metric next time. ## A measurement failed — can I re-run it without waiting for tonight? Yes, if you are an admin: **Retry now** on the ledger row re-runs the scoring immediately. Failed measurements are also retried automatically on each overnight run, up to 10 attempts. After that the row stays visibly failed rather than being quietly abandoned. The reason for the failure is shown on the row itself. ## Why can't I pilot this change at another location? Two conditions have to hold. The change must have been decided **Keep** or **Expand**. Its metric must also be one Loop can compute for a single location — an organization-wide-only metric cannot honestly measure one site's pilot. Loop additionally skips any location with no manager to invite, and names the ones it skipped. ## I've been invited to pilot a practice — what am I agreeing to? You are agreeing to run the practice at your location and own its result. Nothing is measured until you accept and confirm the date it actually went live at your site. That date starts a measurement for your site alone; the original site's result is never assumed to carry over. You can decline instead, with a reason the inviter will see. ## Why are sample stories counting in our totals? Because you have no real measurements yet. While that is true, the loaded sample stories fill the tiles and pipeline under a banner saying so. The moment your first real measurement lands, every total reverts to real data only. Remove the samples any time from Settings. ## Why aren't we seeing any improvement opportunity cards? Quiet is a valid state — Loop shows cards only when your own data supports one, and never invents work to look busy. A trend card, for instance, needs at least 20 records in each 30-day window and a worsening of at least 15% before it appears. Dismissed cards also stay gone permanently unless you chose to snooze them instead. --- ## Autonomy, sharing and controls ## What can Loop do on its own if I turn on earned autonomy? Only two routine, reversible things, and only for practice types that earned the right. You cannot set that level by hand; unlike other apps Loop has no AI-mode dial, and Settings shows the evidence behind each earned level. After 3 decided plans with 2 kept, Loop proposes the next turn as a notification you act on. At 5 decided plans, a 60% hit rate and a recheck that held, it may act. Acting means drafting a stalled follow-up plan, or pausing an automation whose plan regressed. Both are reported to the owner and both can be reversed: cancel the drafted plan, with a reason, any time before it has a result, or resume the automation from its row's actions menu in Automations. **Earned autonomy** is off by default. ## What leaves our organization if I turn on "Share anonymized evidence"? Only a count of organizations. It lets you be counted in cross-customer proof such as "proven at 5 organizations" on a pattern card. That count appears only once 3 or more organizations have opted in. Your name, your numbers and your dates never leave your tenant, and the switch is off by default. ## Where do I pause Loop's automations in a hurry? In **AI Operations** in the admin sidebar, not inside Loop. That is where pause-all and resume-all, the approvals queue and action history live. It is available to every business admin whether or not Loop is enabled. Loop owns the learning half — the ledger, plans and decisions — so the emergency controls deliberately stay outside it. --- ## More help - Ask AI — the assistant answers Loop questions from this article. **Keywords:** faq, loop, make a plan, measurement ledger, baseline, measurement window, inconclusive, recheck, pilot invitation, earned autonomy, opportunity cards, improvement portfolio, quarterly review, manager access, not showing, permissions --- # Maintenance, Lockdowns & Suspended Accounts **Category:** System-features **Section:** Advanced Features **Updated:** 2026-10-18 Why the site shows a maintenance page, a read-only banner or a suspended notice, when it comes back, whether you sign in again, and how super admins run maintenance windows and security lockdowns. # Maintenance, Lockdowns & Suspended Accounts Sometimes the whole workspace is paused: a maintenance page instead of the app, a banner saying changes are blocked, or a notice that the account is suspended. Here is what each one means, when it ends, and who ends it. | What you see | What it is | Who ends it | |---|---|---| | "We'll be back soon", or your company's own maintenance message | A maintenance window | A super admin, or it lifts itself | | Banner: "Read-only freeze is active" | A maintenance window that blocks changes only | A super admin, or it lifts itself | | "We're performing platform maintenance" | Maintenance across MangoApps | MangoApps | | "Temporarily unavailable" | A security lockdown or a suspended account (the page doesn't say which) | Ask your administrator | | Banner: "Your workspace is read-only — the trial ended…" | A trial that ended without continuing | An admin, in Billing & Payments | | Banner: "Some apps are temporarily unavailable" | Apps switched off for an unpaid invoice | An admin, by paying | | "Your MangoApps account is suspended" or "You're signed in" | MangoApps suspended the account | MangoApps only | ## For everyone ### Why can't I save? The banner says the site is read-only A super admin has started a **read-only freeze**: "Read-only freeze is active — viewing works, changes are blocked for everyone." You can read everything, but nothing can be created, edited or deleted until it lifts. It is not about your role or permissions. When you press Save, a note appears above the form: "Changes are paused right now (read-only freeze). Nothing was saved." What you typed is still there, so save again once the freeze lifts. Some forms show a **Changes are paused** page instead; go back to keep working. If the banner says **"Your workspace is read-only — the trial ended…"**, the cause is billing, not maintenance (see below). ### When will the site be back? - The maintenance page shows **Expected back by** a time (the Changes are paused page and the read-only banner say "until" it), in your organization's time zone: the lift time the super admin set, or four hours after the window started if none was set, when it ends by itself. It can be lifted sooner. - With no time shown, it is a security lockdown or a window MangoApps set, which ends only when a person lifts it. - An open maintenance page checks again every five minutes and opens the app by itself when access returns. - Maintenance emails go to super admins only. Ask your administrator for more detail. ### Do I need to sign in again afterwards? Usually not. Maintenance windows and lockdowns block access; they don't sign anyone out. You are asked to sign in again only if your sign-in expired while the site was down (for example, you were away longer than your organization's sign-in timeout), or a super admin used **Sign everyone out** during a security lockdown, which also ends phone-app and Office add-in sign-ins. The same applies after a suspended account is reactivated. Nobody needs a new password. ### I see a "Scheduled maintenance" banner A window is booked. Until it starts, everyone sees a yellow banner with the start time, saying the site "will be unavailable" or, for a freeze, "will be read-only". **Read the message** shows what your admin wrote. Save your work before then. ### The page says "Temporarily unavailable" There is a security lockdown or the account is suspended. Contact your workplace administrator. If the sign-in page says **"[Company] is currently unavailable"**, the account is suspended: signing in won't open the app, but it shows what this means for you. Members see **You're signed in**: nothing in your schedule was changed or deleted, and you check your shifts with your manager directly until access returns. ## For super admins: Maintenance & Lockdown **Where:** **Admin → Security → Maintenance & Lockdown** (Super Admin only). The page stays open while a window or lockdown is on. ### Start or schedule a maintenance window 1. **Choose what to block:** a preset, or **Advanced** to pick surfaces. 2. **What people will see:** headline, message, optional contact email and status page link. **Starts at** (blank = now) and **Lifts at** (optional), in your time zone. **Preview page** shows the result. 3. **Who keeps access** (below). 4. **Confirm and start.** A full shutdown asks you to type your subdomain; blocking the API asks you to confirm integrations will be interrupted. One window at a time: lift the active one or cancel the scheduled one first. A scheduled window starts within about five minutes of its start time. | Preset | Blocks | Stays open | |---|---|---| | Full shutdown | Web, API, mobile apps, integrations | Only the people under "Who keeps access" | | API & mobile off | API, integrations, mobile apps | Web | | Staff access off | Web and mobile apps | API and integrations (payroll, HRIS) | | Read-only freeze | Every change, everywhere | Viewing on web, mobile, API and integrations | A maintenance window does not stop email or notifications. ### Who can still get in during maintenance? - **Super admins keep access** (on by default): super admins keep working, with a break-glass banner, and can still make changes during a read-only freeze. Other admins are blocked like everyone else. - **IP ranges that stay allowed:** anyone connecting from a range you tick, chosen from your organization's IP ranges. - **API tokens that stay live:** for example a payroll export or SIEM feed. With **Super admins keep access** off, everyone is blocked, you included, except allowed IP ranges. The Maintenance & Lockdown page still opens for super admins, so you can lift the window. MangoApps support can always reach the site. Signing in still works during a window, with a password, single sign-on or the phone app; what a person can do afterwards is still up to the window. **Forgot password?** is not offered while a window blocks the web (or the phone app, on the phone) or freezes changes, and **Sign in with code** is not offered while a window holds outgoing messages, which a security lockdown always does. Single sign-on creates no new account while a window blocks the web or freezes changes. During a security lockdown single sign-on is turned off altogether: sign in with your password. ### Does a maintenance window end on its own? Yes. It ends at its **Lifts at** time, or four hours after it started if none was set. Super admins are emailed when it ends. A running window can't be extended; start a new one if the work isn't finished. Two never end on their own: a **security lockdown** (super admins get a reminder email every day it lasts), and a **window MangoApps set**, which your admins can neither ride through nor lift. Contact MangoApps support (support@mangoapps.com) for that one. ### Lift, cancel and review **Lift maintenance now** restores access straight away, and existing sign-ins carry on. **Cancel scheduled window** calls off a booking. **History** lists the 20 most recent windows with outcome, what was blocked, who started it and how it ended. Every super admin with an email address is emailed when a window is scheduled, starts, is cancelled, ends or is lifted. Members are not emailed. ### How do I lock everyone out after a suspected breach? Use **Security Lockdown**, the red section at the bottom of the page. It is for a suspected breach, not planned work. Lift any maintenance window first. Enter the reason (internal only, never shown publicly), tick the confirmation, and click **Start security lockdown**. It starts at once and can't be scheduled. While it is on: - Web, mobile and API are blocked for everyone, admins included. Sessions and API tokens are blocked, not ended. - Incoming integrations (webhooks, provisioning) are refused. - Outgoing email and syncs are held and go out when it lifts, except reminders out of date by then. - Texts, calls and WhatsApp messages due meanwhile are cancelled and not resent. Emergency alerts still go out. - Single sign-on and **Sign in with code** are turned off; super admins sign in with their password. - A snapshot of sessions active in the last 30 days, API tokens and integration connections is saved for you to download as a CSV. - Members see a plain "Temporarily unavailable" page that never mentions a lockdown. - Every super admin with an email address is emailed. **If the incident is confirmed**, the super admin who started it has two steps. Neither can be undone, and neither is needed to lift. - **Sign everyone out** ends every session and every phone-app and Office add-in sign-in, yours included. Sign back in with your password and you land on the Maintenance & Lockdown page (your site address followed by /admin/maintenance); the rest of the site stays blocked. - **Revoke API tokens** stops every token. Integrations need new keys. **Lifting:** only the super admin who started it, or MangoApps support after verifying identity. Other super admins see a read-only summary. If you lift without signing everyone out, everyone who was signed in and hasn't timed out gets access back, including anyone who shouldn't. For one leaver, a lost device or a leaked key, use **Sessions & Tokens** instead; it doesn't take the site down. See [Security & Sign-On](/help/articles/admin_security_and_signon). ## Billing and suspended accounts ### Why are our apps switched off, or why is the workspace read-only? The banner tells you which of three causes applies: 1. **A read-only freeze** ("Read-only freeze is active"): a super admin set it. It ends when lifted or at its lift time. 2. **An unpaid invoice:** on a self-serve plan, reminders go out at 7, 14, 30 and 45 days past due. A subscription invoice still unpaid after the last one switches the plan's apps off, and the Plan tab reads **Switched off — unpaid**. Members see "Some apps are temporarily unavailable". Paying turns the apps back on, and data is kept. An unpaid invoice never suspends the account. 3. **A trial that ended:** a self-serve trial that ends without continuing switches its apps off and makes the whole workspace read-only ("Your workspace is read-only — the trial ended…"). Data is kept for 90 days. An admin adds a payment method, or clicks **Turn everything back on** if a card is on file. Details: [Billing & Payments](/help/articles/admin_billing). ### Our account is suspended — what do I do? MangoApps suspends a whole account by its own decision. While it is suspended: - The web app, mobile app and API are blocked for everyone. The sign-in page opens, but signing in doesn't restore access. - No data is deleted. The workspace's own emails, notifications and integrations stop. - Every administrator with an email address is emailed. - A maintenance window can't change it, and the billing pages can't be reached, so paying doesn't lift it. **Members:** contact your workplace administrator. **Administrators:** contact MangoApps support at support@mangoapps.com or your account manager. There is no self-service reactivation; only MangoApps can reactivate. **When it is reactivated**, access returns for everyone (allow up to a minute, then reload) and administrators are emailed. People may need to sign in again; nothing else about their accounts changes. Your own maintenance window or lockdown stays until lifted, and apps switched off for non-payment stay off until paid. If MangoApps is closing the account, the page administrators see says so; contact support straight away if that is unexpected. **Keywords:** maintenance, maintenance mode, maintenance window, scheduled maintenance, maintenance page, site down, outage, temporarily unavailable, read-only, read only, read-only freeze, can't save, changes blocked, changes are paused, lockdown, security lockdown, hacked, breach, sign everyone out, revoke tokens, suspended, account suspended, reactivate, switched off, unpaid, apps switched off, trial ended, who keeps access, break-glass, lifts at, when will it be back, sign in again --- # MangoApps Console **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-12 The platform-wide system administration portal — managing tenants, billing, apps, AI, operations, and compliance from a single console with role-based access and granular permissions. # MangoApps Console ## 1. What it is The MangoApps Console is the platform-wide administration portal for managing tenants (customer businesses), billing, app licensing, AI configuration, system operations, and compliance. It runs on its own subdomain — separate from any tenant — and is used by the team that operates the platform, not by tenant admins or end users. - **Access:** The Console lives at `console-{env}.workforce.mangoapps.com` (e.g. `console.workforce.mangoapps.com` in production). The legacy `sysadmin.*` hostname redirects here. - **What it is not:** The Console is not a tenant admin panel. Tenant admins manage their own business at **Admin →** within their subdomain. The Console manages the platform across all tenants. ## 2. Standing it up Console operator accounts are entirely separate from tenant user accounts. By default a SuperAdmin or an Admin creates operators and assigns their roles. 1. Sign in at the Console URL with email and password, or with **Sign in with Google**. Google sign-in works only for a staff account that already exists; it never creates one. 2. Go to **Platform Settings → System Users** to create an operator. Each needs a first name, last name, a unique email and a password of at least 12 characters. The email must be on an approved staff domain. 3. Assign one or more **roles**. Roles decide which sidebar sections and pages the operator can open. The ten roles are: SuperAdmin, Admin, Engineering, Product, Marketing, Sales, Finance, Legal, Support, Viewer. 4. Optionally tick **Require Two-Factor Authentication**. An operator who is required to use it and has not enrolled gets 24 hours to enrol before they are signed out, or the grace period the Console 2FA policy sets. 5. Confirm the operator can sign in and sees the sidebar sections their roles allow. A new operator defaults to the Viewer role and is active immediately. SuperAdmin is the only role that implicitly holds every permission. Every other role sees only the pages its permissions cover. An Admin cannot change the email, password, active status or 2FA requirement of a SuperAdmin; only another SuperAdmin can. If an operator opens a Console link while signed out — for example from an alert email — sign-in brings them back to that page instead of the dashboard. This works for password, two-factor, SSO-link and Google sign-in. ## 3. How it fits together ### Operators and roles Console operators are separate from tenant users. An operator can hold several roles at once. The highest-priority role becomes their primary role. From highest to lowest: SuperAdmin (1), Admin (2), then Engineering, Product, Marketing, Sales, Finance, Legal and Support (all 3), and Viewer (4). For example, an operator holding Sales and Viewer has Sales as their primary role, because level 3 outranks level 4. SuperAdmin holders pass every permission check. Every other role is resolved through role-permission mappings. Each role is granted a set of named permissions (for example **View customers** or **Manage pricing**), and every Console page requires one of them. ### Sales operators and their leads Demo Requests (the Console's list of sales leads) has its own four permissions: **View demo requests**, **Import demo requests**, **Work demo requests** (assign, change stage and follow-up, mark spam, re-sync to HubSpot) and **Delete demo requests**. By default the Sales role holds view, work and delete, but not import. Admin, Product and Marketing hold all four. A **Sales-only operator** is one who holds Sales and none of SuperAdmin, Admin or Marketing. Their access is limited to the leads assigned to them: - The lead list is titled **My Leads** and shows only their own leads. - Opening, assigning, marking spam or deleting another rep's lead is refused. The **Import** button appears only for roles with **Import demo requests**. Links to lead routing rules appear only for roles that can edit Marketing pages. Worked example: a rep holding only Sales opens the lead list and sees **My Leads**, containing just the leads assigned to them, with no Import button. Give the same person the Marketing role and the page becomes **Demo Requests**, listing every lead, with Import available. ### Permission categories Permissions are organized into categories that correspond to sidebar groups. The main categories: **Customers**, **Billing**, **Apps & Licensing**, **AI & Automation**, **Operations**, **System Settings**, **Users**, **API Tokens**, **Issue Reports**, **Legal & Compliance**, **Training**, **Knowledge Base**, **Company Store**, and several others. Each category has view, create, edit, delete, and specialized entries (for example **Manage pricing** under Billing, or **Manage OpenAI keys** under AI & Automation). Only a SuperAdmin can edit role-permission mappings (**Platform Settings → User Permissions**). ### Two-factor authentication Console 2FA uses TOTP (time-based one-time passwords). Once enrolled, the operator enters a code after their password. Ten backup codes are generated at setup and encrypted at rest. 2FA can be required in two ways. An operator's own **Require Two-Factor Authentication** box covers one person. The **Set Console 2FA policy** task on **System Operations → Operations** covers whole roles and sets their grace period. Either way, the grace period is 24 hours unless the policy sets a different one. After it, sign-in is refused until an administrator helps the operator enrol. ### Dashboard The Console dashboard is role-aware. It shows different widget groups depending on the operator's roles: - **Sales** (Sales, SuperAdmin, Admin, and only with **View demo requests**): overdue follow-ups, active leads, closed-won this month and the lead pipeline. A Sales-only operator's counts cover their own leads only. - **Marketing** (Marketing, SuperAdmin, Admin): AI conversations, demo requests, assessments - **Support** (Support, SuperAdmin, Admin): new/active/critical cases, personal case count - **Platform** (SuperAdmin, Admin, Engineering): total/active businesses, user counts, 2FA adoption, failed logins Operators with multiple roles see the union of all applicable widget groups. ### Console AI sidebar Every authenticated Console page includes an AI sidebar. It defaults to the **Console Operations** agent (read-only live data) on most pages, and switches to a specialized agent on context-specific pages (e.g. the **Case Center** agent on the issue reports page, the **Product Loop** agent on that page). Operators can also switch agents manually via the sidebar's assistant picker. ## 4. Running it ### Managing customer businesses Go to **Customer Management → Customer Businesses**. This lists all tenant businesses with user counts. From here an operator can: - **Create** a new customer business (requires a business name and an initial admin user email/password; domain and subdomain auto-derive from the name) - **Edit** business settings and toggle features like AI Builder - **Suspend / Unsuspend** a business (requires the **Suspend customers** permission) - **Grant or revoke bundles** to change the business's licensed app packages - **Destroy** a business (SuperAdmin only) ### Working sales leads Demo Requests has no Console sidebar entry. Operators reach it from the **Sales** section of the dashboard: **My Leads**, **All Leads** (not shown to Sales-only operators) and the **Lead Pipeline** button, which opens the **Lead Pipeline Dashboard**. From a lead, an operator with **Work demo requests** can assign it, update its stage and follow-up date, mark it as spam, or re-sync it to HubSpot. **Import Demo Requests** (from a CSV file) needs **Import demo requests**. ### Monitoring system health Go to **System Operations → System Health** (requires **View system health**). Additional operational pages: - **Background Jobs** — view and manage the job queue - **System Diagnostics** — platform-level checks - **System Logs**, **Admin Action Logs**, **Authentication Events**, **API Audit Logs**, **Notification Logs** — each gated by its own permission key - **Alert Settings** — configure system alert thresholds and recipients. Alerts are checked every 15 minutes. - **Operations** — run declared operational tasks, such as **Set Console 2FA policy**, which requires 2FA for whole roles and sets their grace period - **Platform Maintenance** — take tenants offline for maintenance windows (SuperAdmin only) ### Managing apps and licensing Go to **Apps & Licensing → Apps & AI Agents** (requires **View apps & licensing**). From here: - View all marketplace apps and their status - **Customer Access** — manage which tenants have access to which apps - **User Limits** — monitor and manage licensed user counts; shows businesses over their limit - **App Reviews** — moderate user-submitted app reviews - **App Analytics** — usage data across apps ### Configuring platform settings Go to **Platform Settings** (requires **View system settings**): - **System Settings** — global platform configuration including email delivery controls. The global email kill switch pauses all non-transactional outbound email for every tenant. - **Email Sender Config** — SMTP and sender address settings - **SSO Configurations** — manage single sign-on providers - **Stripe Configuration** — payment processing credentials - **System Users** — manage Console operators (requires **View users**) - **User Permissions** — edit role-permission mappings (SuperAdmin only) - **API Tokens** and **Public API Keys** — manage platform-level API credentials ### Working with support cases Go to **Support → Support Cases** or **All Cases** (requires **View issue reports**). Cases can be filtered by category group (support cases vs. feature requests). Operators with **Manage issue reports** can update status, assign cases, add notes, and reply to users. Case Workflow & SLA configuration is available to Admin-or-above operators. ### Viewing billing and revenue Go to **Finance → Revenue Dashboard** (requires **View billing**). Sub-pages for managing packages, app pricing, platform tiers, term/volume discounts, credit packages, and app licensing each require **Manage pricing** or **Manage licensing**. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Operator active status | Platform Settings → System Users | Active | Deactivated operators are rejected on their next request | | Operator role | Platform Settings → System Users | Viewer | Determines sidebar visibility and page access | | Require Two-Factor Authentication | Platform Settings → System Users | Off | Whether the operator must enrol in TOTP | | System alerts for operator | System Users → edit operator → Notifications | Role-dependent | On for SuperAdmin, Admin and Engineering; off for other roles | | Issue notifications for operator | System Users → edit operator → Notifications | Role-dependent | On for SuperAdmin, Admin and Support; off for other roles | | Enable System Alerts | System Operations → Alert Settings | On | Whether platform alerts are raised at all | | Enable Email Alerts | System Operations → Alert Settings | On | Whether system alerts send email | | Alert Cooldown (minutes) | System Operations → Alert Settings | 60 | Minimum time before the same alert repeats | | Case Center actions | System Users → edit operator → AI Action Access (SuperAdmin only) | Off | Lets the Case Center assistant make confirmed case changes | | Console operational actions | System Users → edit operator → AI Action Access (SuperAdmin only) | Off | Lets the Console assistant make confirmed app-access, retry, user-limit, suspend and restore changes | | Console role permissions | Platform Settings → User Permissions (SuperAdmin only) | Role defaults | Which permissions each role holds, including the four Demo Requests permissions | ## 6. More help - **MangoApps Console FAQ** — specific operating questions, permission troubleshooting, and exact values - Ask AI — the Console AI sidebar answers questions about live platform state on every Console page. **Keywords:** console, system admin, sysadmin, platform admin, super admin, tenant management, customer management, system settings, console login, console permissions, console roles, my leads, demo requests, sales role, platform operations, system administration --- # MangoApps Console FAQ **Category:** Faq **Section:** Administration **Updated:** 2026-10-13 Answers to common setup and operating questions about the MangoApps Console — for the operator running it. # MangoApps Console FAQ Answers to common setup and operating questions about the MangoApps Console. For what the Console is and how to set it up from scratch, see the [MangoApps Console Overview](/help/articles/console_overview). --- ## Setup ## Do I need to create a separate account for each Console operator? Yes. A Console operator account is separate from any tenant user account, with its own password, session and permissions. Create operators at **Platform Settings → System Users**. The email address must be on an approved staff domain, which by default means **@mangoapps.com** or **@mangospring.com**. ## What role does a new operator get by default? A new operator gets the **Viewer** role unless you pick another, and the account is active immediately. Viewer is the most restricted role and is mostly read-only. Only a SuperAdmin can give someone the **SuperAdmin** role. ## Can an operator hold more than one role? Yes. Tick several roles on the operator's form, and they get every permission that any of those roles grants. The highest-ranked role is shown as their primary role. The ranking is SuperAdmin, then Admin, then Engineering, Product, Marketing, Sales, Finance, Legal and Support as equals, then Viewer. ## What are the password rules for a Console operator? A Console password must be at least **12 characters**. That floor can be changed with the **Set a platform runtime setting** task on the Console's **Operations** page. A password reset link stays valid for **6 hours**, after which the operator must request a new one. --- ## Permissions and access ## Why can't my operator see a particular sidebar section? Each sidebar section needs a matching permission, such as **View customers** or **View notification logs**. If none of the operator's roles grants it, the section is hidden. A SuperAdmin changes which permissions each role holds at **Platform Settings → User Permissions**. SuperAdmins pass every permission check. ## Which actions are only available to a SuperAdmin? Some actions need the SuperAdmin role itself, and no permission grant substitutes for it. They include: - deleting a customer business - editing **User Permissions** - generating magic login links - anything on **Platform Maintenance**, including forcing one tenant into maintenance - deleting or impersonating another operator - requiring, resetting or disabling two-factor authentication (2FA) for another operator - turning on **Console operational actions** for an operator ## What does the Console dashboard show each role? Every signed-in operator can open the dashboard, but its sections depend on role: - **Sales** — shown to Sales, Admin and SuperAdmin operators who also hold **View demo requests**. - **Marketing** — shown to Marketing, Admin and SuperAdmin operators. - **Support** — shown to Support, Admin and SuperAdmin operators. - **Platform health** — shown to Engineering, Admin and SuperAdmin operators. An operator with several roles sees every section any of their roles qualifies for. ## What can the Sales role do with Demo Requests and My Leads? Sales operators can view their leads, work them and delete them, but cannot import leads. Demo Requests (the sales-leads list) has its own four permissions: **View demo requests**, **Import demo requests**, **Work demo requests** and **Delete demo requests**. By default, SuperAdmin, Admin, Product and Marketing hold all four, and Sales holds every one except import. An operator whose roles include Sales but not SuperAdmin, Admin or Marketing sees only the leads assigned to them. Their list is titled **My Leads**, and their Sales dashboard counts only those leads. --- ## Day-to-day ## How do I require two-factor authentication for Console operators? There are two ways, and both give the operator a setup window before they are signed out: 1. **One operator** — a SuperAdmin opens the operator's menu at **Platform Settings → System Users** and chooses **Require 2FA**. 2. **Whole roles** — run the **Set Console 2FA policy** task on the **Operations** page. You name the roles that must enrol and how many hours they get. The setup window is **24 hours** unless the policy sets a longer one. For operators covered by the policy, it starts at their next sign-in, unless you choose to start it when you run the task. ## How do I help an operator who lost their authenticator app and backup codes? A SuperAdmin chooses **Disable 2FA** from that operator's menu at **Platform Settings → System Users**. This clears their authenticator link and backup codes, and the operator is emailed that it happened. If 2FA is still required for them, a fresh setup window starts at the same moment, so they are not signed out for a deadline that passed before they first enrolled. Each operator gets **10 backup codes** when they set up 2FA, and each code works once. ## How long does a Console session last? A Console session ends after **8 hours** without activity. Whatever the activity, the operator is signed out **24 hours** after signing in. There is no "remember me" option. ## Where do I land after signing in from a link in an email? You land on the page the link pointed to, not the dashboard. The Console remembers the page when it asks you to sign in or when your session has expired. This works for password, 2FA, sign-in-link and Google sign-in. If you are still being asked to set up 2FA, you go to that step first. ## Can operators sign in with Google? Yes, from **@mangoapps.com** or **@mangospring.com** Google accounts only. Google sign-in never creates an account. The operator must already have a Console account with the same email address. ## How do I pause all outbound email across every tenant? Open `/system_settings/email_settings` on the Console and use **Pause Email Delivery** on the **Global Email Delivery** card. While delivery is paused, the **Email Configuration** card at **Platform Settings → System Settings** also links there with **Manage**. You must give a reason of up to 500 characters and choose how long: 15 minutes, 1 hour, 4 hours (the default), 24 hours or indefinitely. One-time passcodes, password resets and verification codes are still delivered. The switch needs the **Edit email settings** permission. ## What is the difference between suspending a business and putting it in maintenance? Suspension is a lasting account state: the tenant's users are refused until an operator reactivates it from the customer record. Suspending and reactivating need the **Suspend customers** permission. Maintenance is a temporary window that can block web, API, integrations and mobile access. A window forced from the Console cannot be bypassed or cleared by the tenant's own admins. Only a SuperAdmin can force maintenance or turn on platform-wide maintenance. ## Can the Console AI sidebar take actions, or only answer questions? It answers questions for every active operator, and takes actions only for operators who have been set up for it. The default **Console Operations** assistant is read-only. Confirmed actions, such as changing a tenant's app access or retrying a failed background job, need two things: - a SuperAdmin has switched on **Console operational actions** on the operator's record (off by default) - the operator holds **Manage customer access**, **Manage background jobs**, **View diagnostics**, **View notification logs** or **Suspend customers** --- ## When something looks wrong ## "I'm locked out of the Console after my 2FA setup period expired" A SuperAdmin must help, because you cannot fix this yourself. They can choose **Reset 2FA Deadline** for a new setup window, or **Make 2FA Optional** if your role is not covered by the platform policy. Until then the sign-in page shows "Your 2FA setup period has expired. Please contact a system administrator." ## "I deactivated an operator but they're still logged in" They are not, even if their page is still open. The Console checks that the operator is active on every request. Their next click or refresh signs them out and returns them to the sign-in page. ## "I'm in Sales and I can't see a colleague's lead or import leads" That is expected for Sales operators. If your roles include Sales but not SuperAdmin, Admin or Marketing, you see only the leads assigned to you. Opening another rep's lead returns "Access denied." Bulk actions change only your own leads. Importing leads needs **Import demo requests**, which the Sales role does not hold by default. --- ## Licensing and limits ## What limits and timeouts should I know about? | Limit | Value | |---|---| | Idle session timeout | 8 hours | | Maximum session length | 24 hours | | Minimum operator password | 12 characters (adjustable) | | Password reset link | 6 hours | | 2FA setup window | 24 hours by default | | Backup codes | 10, each single-use | | Console AI message length | 10,000 characters | | Console AI rate | 15 messages per minute per operator | | Email pause reason | 500 characters | | Authentication Events CSV export | 50,000 rows | The Authentication Events export covers every tenant, so narrow it with the page's filters before exporting. --- ## More help - [MangoApps Console Overview](/help/articles/console_overview) - Ask AI — the Console AI sidebar answers questions about live platform state on every Console page. **Keywords:** faq, console, system admin, sysadmin, operator, system users, user permissions, roles, sales role, demo requests, my leads, leads, two-factor, 2fa, backup codes, session timeout, sign in, password, email kill switch, maintenance mode, suspend business, magic login, console ai --- # Mango CS App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run Mango CS — the post-close customer success platform for account health, renewals, handoff, onboarding, success plans, cross-account tasks, and advocacy. # Mango CS ## 1. What it is Mango CS is the post-close customer success platform. It gives CSMs a single surface for account health, renewals, onboarding, success planning, and customer advocacy — from the moment a deal closes through every renewal cycle. - **Enablement:** Mango CS requires a license and is opt-in per tenant. An administrator enables it from **Admin → Apps → All Apps**. - **What it is not:** Mango CS owns everything after close. The pre-close motion — prospecting, demos, proposals, contracts — lives in Mango GTM. The two apps share the same account record, but each owns its own lifecycle stage. ## 2. Standing it up 1. Go to **Apps → Mango CS → Settings**. 2. **Review the capability toggles.** Most features are on by default (Account management, Contacts directory, Handoff checklist, Renewals, Success Plans, Implementation Projects, Growth, References, Reviews). Off by default, and turned on explicitly: **Auto-flag accounts at risk**, **Lifecycle Stage Automation** and **Team Workload**. 3. **Create or import your first accounts.** Go to **Accounts** and add accounts manually, or use **Import** to upload a CSV (up to 500 rows per import). Each account needs at least a name. Assign a CSM and an AE to each account so the dashboard and "My accounts" filters work. 4. **Define your contact roles.** The app ships four built-in roles — Champion, Economic Buyer, Technical Buyer, and Detractor. You can rename them or add custom roles under **Settings → Custom Fields → Contact roles**. 5. **Set up your onboarding templates** (optional). If you plan to use Implementation Projects, go to **Plan Templates** and create reusable milestone structures. When you create a new project, you can apply a template to pre-populate its milestones and checklist items. 6. **Configure the renewal cadence** (optional). In **Settings → Renewal Cadence**, set the uplift percentage and the reminder schedule. The defaults — 5% uplift, reminders at 60 and 14 days — work for most teams. Clear the reminder schedule to switch renewal reminders off. 7. **Confirm it worked.** Open the **Dashboard**. You should see your accounts in the "My Book" view and any at-risk or upcoming-renewal tiles populated. If Mango GTM is also enabled, the two apps share the same account record. When a deal closes in Mango GTM, the account opens in Mango CS with a handoff checklist already in pending state. The handoff cannot be marked complete until the AE fills in the three required fields. ## 3. How it fits together **Accounts and lifecycle stages** — Every customer is a single account record. Accounts move through six stages: Prospect → Onboarding → Active → Renewal → Expanding → Churned. A separate **At Risk** flag can be set at any stage — it is not a stage itself, so an account can be both Active and At Risk at the same time. Example: "Acme Corp" is in the **Active** stage with a health score of 38 and the **At Risk** flag set. It appears on the dashboard's at-risk worklist and on the renewals pipeline if its renewal date is within the selected window — the two signals are independent. **Health score** — A composite 0–100 score computed nightly from weighted signals: product usage (30%), CSM engagement (10%), customer sentiment (15%), and contract risk (30%). A support-ticket load signal (15%) is part of the model but is not available to most workspaces — support tickets aren't connected for them — so it is left out and the other signals share its weight; Settings → Health Score Model shows it greyed out when that is the case. An admin can change the weights under **Settings → Health Score Model**; a signal with no data is skipped and the others are re-weighted. When the Surveys app is enabled, sentiment comes from real NPS or CSAT responses; otherwise it falls back to the champion-to-detractor ratio among contacts. An account where no signal produced data shows **Not enough data** instead of a score — it is never given a made-up neutral number. An admin can turn on **Auto-flag accounts at risk** to set the At Risk flag automatically when the score is at or below a configurable threshold (default 50). It needs **Composite health score** on — with scoring off, nothing is flagged or cleared. **Handoff checklist** — A one-per-account checklist that captures what the AE promised, the customer's pain points, the implementation scope, and any special terms. When Mango GTM is enabled, the checklist opens automatically when a deal closes. It cannot be marked complete until the three required fields — Promised Outcomes, Pain Points, and Implementation Scope — are filled in. On completion, the account's CSM and AE are notified (who is told is set under **Settings → Notifications**). **Renewals and Mango GTM** — The renewal pipeline shows every account renewing within a selectable window (30, 60, or 90 days). Renewal dates come from two sources: subscription billing data and CSM-curated dates on the account. Each entry is classified into one of four stages: On Track, At Risk, Expanding, or Churning. Renewal reminders are emailed to the account's CSM and AE at a configurable cadence (default 60 and 14 days before renewal). If Mango GTM is enabled, a CSM can generate a renewal proposal with a configurable uplift (default 5%, clamped to 0–50%) that flows through the same proposal-to-contract pipeline the AE used at first sale. **Success Plans** — An account-level plan with nested goals and measurable outcomes. Each account can have one active plan at a time. Outcomes can be tracked manually, pushed via API, or auto-tracked nightly from health snapshots, linked-tenant engagement, or an MCP integration you configure in-app. A CSM can draft the plan structure with AI — the draft proposes up to 4 goals with up to 3 outcomes each for review before saving. Plans can be archived but not deleted. A customer-visible slice of the plan can be shared to the customer portal. **Growth** — The opportunities *you* want to introduce to a customer — modules, apps, use cases and services engagements — recorded against the account. It is the mirror image of a Success Plan: the plan carries the customer's goals, Growth carries yours. Each item has an opportunity, a category, a readiness (Immediate, Short term, Long term, or Not an opportunity) and a status (Active, Stalled, Implemented, Closed, plus any statuses your admin adds in **Growth fields**). A category naming SOW switches the item to statement-of-work next steps. Requirements and artifacts attach to the item (up to 100 MB per file). On an open item's follow-up date the account's CSM and AE get a reminder, and with **Growth alerts** on (Settings → Notifications) they are told when an item changes status. The **Growth** tab lists items across every account; the Opportunity and Category lists are set in **Settings → Growth**. **Tech Stack** — The systems a customer already runs — identity provider, HRIS, service desk and so on — each recorded on the account with a category and where it sits in the customer's own lifecycle (In use, Evaluating, Planned, Being replaced, or Retired). Supporting documents such as an architecture diagram attach to the entry (up to 100 MB per file). A system is added from its account; the **Tech Stack** tab lists every customer's entries in one place, with CSV export and a bulk import. The category list can be replaced with your own under **Settings → Custom Fields → Tech stack fields**. The tab appears whenever Account management is on. **Contacts and contact roles** — Each account has its own contacts. Every contact carries one or more role tags — the four built-in roles are Champion, Economic Buyer, Technical Buyer, and Detractor — plus any custom roles your admin defines. Role tags matter beyond labels: the health score's sentiment component reads the champion-to-detractor ratio, and the reference finder surfaces champions who have consented to references. A cross-account **Contacts** directory lists every contact in one place, with CSV export. **Team Activity** — A cross-account feed of all account activity in reverse chronological order. A CSM reading their own accounts sees each account's timeline; Team Activity shows what teammates are doing on other accounts. Teammates can react and comment on entries. The feed defaults to 30 days and filters to human-authored activities, excluding system events. **Catch me up** — The AI brief at the top of Team Activity. Pick a window (last 24 hours, 2 days, 5 days, or 30 days) and it reads every recap the team logged across all accounts in that period and returns a short summary, the topics that came up on more than one account, and anything that reads as time-sensitive — each linked to the accounts it came from. It reads the whole workspace rather than whatever filters the feed is showing, so a teammate's account is never hidden from the summary. Briefs are cached for 30 minutes and shared by everyone in the workspace, and logging a new recap clears the cache so the next brief includes it. Requires the Customer Success AI Agent to be on. The same brief is available on the phone, and to the Ask AI agent — ask it "catch me up" or "what did I miss?". **Tasks** — Every customer-success task in one filterable list. CS tasks are created where their context lives — the Tasks card on an account, "Create tasks" on a logged update, and the automatic off-track and renewal-risk sweeps — and the Tasks tab is where you read them all back across the whole book. A task counts as a CS task when it is linked to an account, one of its success plans, one of that plan's outcomes, or a logged update on it; the account it belongs to shows on every row whichever of those it came through. Filter by customer, owner (including Unassigned), status, deadline window, and priority, or use the one-click chips for Open work, Overdue, Due this week, Assigned to me, and Unassigned. The list defaults to open work; switch Status to Completed or All to see finished tasks — the account card and the dashboard only ever showed open ones. Search matches the task title, its description, and the customer name. The current filtered list exports to CSV. Tick rows to **reassign** them to someone else or **mark them complete** in one go — the one write this page carries, because acting on the set you just filtered is what a per-account page can't offer. Creating a task still happens where its context is, so there is one place each task is authored. Requires the Tasks app to be enabled, since that app owns the underlying records. **Implementation Projects** — Onboarding projects with milestones, checklist items, documents, and customer-facing forms. Projects move through stages: Pipeline → Kickoff → Setup → Training → Testing → Go-Live → Live → Blocked → Closed. Each project has a health status (On Track, At Risk, Blocked, Completed). The customer portal is one switch for all of your projects (**Onboarding** on the **Customer Hub** card in Settings, also in the Implementation menu), not one per project; a customer sees a project only once it is linked to their workspace and their administrators have accepted the link. Admins can also send welcome, go-live, and feedback-request emails (rate-limited to one per hour per type). Reusable plan templates can be created and applied to new projects. **References and Reviews (advocacy)** — Two related surfaces for customer advocacy. References tracks contacts who are willing and have consented to give reference calls. A reference is a logged call — not a separate record — and the contact's fatigue counter prevents over-asking within a configurable window (default 90 days). Reviews tracks review requests to G2, Gartner Peer Insights, TrustRadius, and any other review site you add in Settings. Both surfaces are delight-triggered: they surface candidates from accounts with strong health scores. ## 4. Running it ### Reviewing your book Open the **Dashboard**. The "My Book" view shows your assigned accounts with four tiles: total accounts, at-risk accounts, renewals within 90 days, and open tasks. Below the tiles, worklists show accounts needing attention — at-risk first (worst health score at the top), then upcoming renewals (soonest first). If the Tasks app is enabled, open tasks assigned to you also appear. If AI Notepad is enabled, recent meeting notes linked to your accounts are shown. Anyone can switch to **All Accounts** using the book selector; app admins can also open another team member's book. The selector groups team members by their owner role (CSM or AE). ### Managing renewals Go to **Renewals**. Choose a time window (30, 60, or 90 days). The pipeline groups accounts into stage tiles — On Track, At Risk, Expanding, Churning. Click **Generate Renewal Proposal** on an account to create a draft proposal with the configured uplift applied. The proposal opens in Mango GTM for editing and sending. Generating a proposal requires Mango GTM to be enabled — if it is not, the button is hidden and the action is blocked. The entire pipeline can be exported to CSV. The Accounts filter bar (search, health, owner, firmographics) narrows both the table and the export together. ### Working with Success Plans Go to **Success Plans**. Create a plan for an account — each account can have one active plan at a time. Within a plan, add goals, then add measurable outcomes under each goal. Each outcome has a target value, a metric type (Percentage, Number, Currency, or Custom), and a direction (Higher is better or Lower is better). To draft a plan with AI, click **AI draft** on the plan, optionally upload a source document (PDF, DOCX, TXT, or image), and review the proposed goals and outcomes before accepting. The AI proposes up to 4 goals with up to 3 outcomes each. Outcomes can be auto-tracked: set the source to a health signal (e.g. usage score), linked-tenant engagement (e.g. weekly active users), or an external MCP integration. Auto-tracked outcomes sync nightly. On-track or off-track status is computed automatically by comparing the latest measurement to the target. ### Running implementation projects Go to **Implementation**. Create a project and link it to an account. Apply a plan template to populate milestones and checklist items. As the onboarding progresses, move the project through its stages and update its health status. Within each milestone, mark items complete, upload documents, and assign customer-facing forms. An admin can switch the customer portal on for all projects at once and send welcome or go-live emails; the customer sees a project once its workspace is linked and their administrators accept the link. The **Board view** groups all active projects by stage for a Kanban-style overview. ### Logging reference calls and review requests Go to **References** to find reference-eligible contacts, filtered by industry, company size, account health, and topic. Contacts are sorted healthiest-first, least-recently-called-first to spread the load. Log a completed call from the drawer — this bumps the contact's fatigue counter and optionally creates a follow-up task with the configured donation incentive. Go to **Reviews** to see delight-triggered candidates — champions on accounts with a health score of 70 or above who haven't been asked recently. The page tracks review requests to G2, Gartner Peer Insights, TrustRadius, and any other site you list in **Settings → Advocacy → Other review sites** (one per line, `Name | link`), with a per-site velocity readout for the last 90 days. ### Managing team workload Enable **Team Workload** in Settings. Go to **Workload** to see the Load Index for each CSM — a composite of seven weighted signals (revenue under management, active accounts, at-risk accounts, renewals in 90 days, open tasks, accounts in the Onboarding stage, and active implementation projects), each measured against a configurable capacity baseline. From here, an admin can reassign accounts between CSMs or adjust per-CSM capacity (1–200%). Named workload profiles let you apply different baselines and weights to different roles. Workload snapshots are computed nightly; an admin can opt in to alerts (**Settings → Notifications → Workload alerts**) when a CSM newly crosses into the Overloaded band. ### Reviewing analytics Go to **Analytics** (admin only). The page shows health distribution across the book, churn count and rate, current-book ARR, and account/renewal stage distribution. Choose a time window (30, 60, 90, 180, or 365 days). If Success Plans are enabled, a portfolio roll-up shows on-track percentage across all active plans, with a CSV export for QBR preparation. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Customer Success AI Agent | Settings → Capabilities | On | Ask AI answers, the "Describe it and let AI fill the form" bar, Generate Briefing, the Success Plan AI draft, Catch me up (and its weekly digest), and task suggestions | | Account management | Settings → Capabilities | On | Shows the Accounts tab and all account features | | Contacts directory | Settings → Capabilities | On | Shows the cross-account Contacts tab | | Team Activity feed | Settings → Capabilities | On | Shows the Team Activity tab (requires Account management) | | Tasks | (no setting of its own) | On | The Tasks tab appears when Account management is on **and** the Tasks app is enabled in Admin → Apps → All Apps. A CS task belongs to an account, and the Tasks app owns the records, so there is no state where the tab is meaningful without both | | Weekly "Catch me up" digest | Settings → Notifications | Off | Emails the AI catch-up brief every Monday, covering the previous 7 days, to everyone named on an account as CSM or AE plus anyone who logged a recap that week. Only while the Customer Success AI Agent, Team Activity and Account management are on | | AE → CSM handoff checklist | Settings → Capabilities | On | Enables the handoff checklist on each account | | Renewal pipeline + reminders | Settings → Capabilities | On | Shows the Renewals tab and sends reminder emails | | Expansion signals | Settings → Capabilities | On | Enables expansion candidate detection | | Composite health score | Settings → Capabilities | On | Enables health scoring and the health column on accounts | | Implementation Projects | Settings → Capabilities | On | Shows the Implementation tab | | Success Plans | Settings → Capabilities | On | Shows the Success Plans tab. Off also cancels the automatically created tasks still open, the next morning | | Growth | Settings → Capabilities | On | Shows the Growth tab and sends growth follow-up reminders | | Customer References | Settings → Capabilities | On | Shows the References tab | | Online Reviews | Settings → Capabilities | On | Shows the Reviews tab | | Auto-flag accounts at risk | Settings → Health Score Automation | Off | Automatically sets At Risk when the score is at or below the threshold, and takes its own flag back once the score is 10 or more points above it. Needs Composite health score on | | Auto at-risk health threshold | Settings → Health Score Automation | 50 | Health score at or below which accounts are auto-flagged | | Move accounts to the Renewal stage | Settings → Lifecycle Stage Automation | Off | Moves Active accounts to Renewal when their renewal falls within the window (default 90 days) | | Default renewal uplift % | Settings → Renewal Cadence | 5% | Applied to generated renewal proposals | | Renewal reminder cadence | Settings → Renewal Cadence | 60, 14 days | Days before renewal when the account's CSM and AE are emailed (blank switches reminders off) | | AE field label | Settings → Account Field Labels | AE | Renames the Account Executive field across the app | | CSM field label | Settings → Account Field Labels | CSM | Renames the Customer Success Manager field across the app | | Reference fatigue window | Settings → Advocacy | 90 days | Days after a reference call during which the contact is flagged as recently called | | Reference incentive | Settings → Advocacy | Blank (off) | Charity donation amount per reference call (blank or 0 means no incentive) | | Review fatigue window | Settings → Advocacy | 90 days | Days between review asks to the same contact | | Team Workload | Settings → Team Workload | Off | Enables the Workload tab and Load Index view (admin only) | | Workload alerts | Settings → Notifications | Off | Notifies Mango CS admins when a CSM newly crosses into Overloaded (only while Team Workload is on) | | Customer Hub — Onboarding | Settings → Customer Hub | Off | Shows your implementation projects to each linked customer in their Customer Hub | | Customer Hub — Success Plans | Settings → Customer Hub | Off | Shows shared Success Plans to each linked customer in their Customer Hub | ## 6. More help - **Mango CS FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about Mango CS from these articles. The agent is read-only; it can look up at-risk accounts, the renewal pipeline, pending handoffs, and account health, and it links you to the account page, where Generate Briefing and the Success Plan AI draft live. State changes happen in the app, not from chat. **Keywords:** mango cs, customer success, health score, renewal pipeline, handoff checklist, success plan, implementation project, onboarding, at risk, expansion, customer references, online reviews, team workload, load index, account 360, tasks, cs tasks, mango-cs, mango_cs --- # Mango CS FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Mango CS — for the admin running it. # Mango CS FAQ Answers to common setup and operating questions about Mango CS. For what the app is and how to set it up from scratch, see the [Mango CS Overview](/help/articles/mango_cs_app_overview). --- ## Setup ## Do I need Mango GTM to use Mango CS? No. Mango CS can manage customer accounts from any source. The Mango GTM integration adds the AE-to-CSM handoff workflow and a shared account record, but it is not required. Some agent tools — contracts, meeting notes, and combined renewal-risk — only appear when the Contracts or AI Notepad apps are also enabled. ## What do I need to configure before Mango CS starts working? Enable the app from Admin → Apps → All Apps — that is the only hard prerequisite. Every feature (accounts, renewals, health score, success plans, implementation projects, growth, references, reviews) defaults to on except Team Workload, auto at-risk flagging and Lifecycle Stage Automation, which are off until you turn them on in Settings. Review tracking also needs at least one review link in Settings before any site appears — G2, Gartner Peer Insights or TrustRadius in their own fields, and any other site you use (Clearbox, a vertical review site) in the “Other review sites” box. ## What happens when an AE marks a deal as won in Mango GTM? The account opens on the Mango CS side in Onboarding stage and a handoff checklist is created in Pending state. The AE is prompted to fill in promised outcomes, champion, pain points, implementation scope, and special terms. Until the AE marks the checklist complete, the account stays in the pending-handoff queue visible to CSMs. --- ## Permissions and access ## Who is a Mango CS admin, and what extra capabilities do they get? A Mango CS admin is anyone with the app-specific admin role for Mango CS, or any super admin. Admins can access Settings, Analytics, and Team Workload. They can also manage custom fields and contact roles, delete implementation projects, toggle the customer portal, delete other users' Team Activity comments, import accounts with update capability, and view any CSM's book on the dashboard. ## Why can't I edit an account I can see? Any Mango CS user can view all accounts, but only the assigned AE or CSM on an account (or someone holding a co-owner role ticked under Settings → Team Workload) — or a Mango CS admin — can edit it. The same ownership rule applies to editing contacts, billing profiles, and tech stack items on that account. An admin can widen it under **Settings → Permissions → Who can edit an account they don't own?** — to the account owner's manager, or to groups you choose. If you need to edit an account you are not assigned to, ask an admin to reassign it or make the change for you. --- ## Day-to-day ## What drives the health score, and how often is it updated? The health score is a composite 0–100 value from weighted components: product usage (30%), CSM engagement (10%), contact sentiment (15%), and contract/renewal risk (30%) — read from the account's subscription, or from the renewal date set on the account when no subscription is linked (a date that passed more than 60 days ago is treated as out of date and skipped). A support-ticket load signal (15%) is part of the model but is not available to most workspaces — support tickets aren't connected for them — so it is left out and the other components share its weight (Settings → Health Score Model shows it greyed out when that is the case). A component with no data is skipped and the rest are re-weighted. Sentiment prefers real NPS or CSAT survey responses when the Surveys app is enabled; otherwise it uses the ratio of champion to detractor contacts. The score is recalculated and saved once per day for every non-churned account. ## How does the auto at-risk flag work? Auto at-risk flagging is off by default. When you turn it on in Settings → Health Score Automation and set a threshold (default 50), any account in Active, Renewal, or Expanding stage whose health score is at or below that threshold is automatically flagged At Risk during the nightly update — a score equal to the threshold is flagged. A flag the automation set is taken back once the score is 10 or more points above the threshold; a flag a person set, or one with reasons picked, is never cleared automatically. Turning the automation off leaves existing flags in place. The account's CSM and AE receive an in-app notification (marked urgent) when an account is newly flagged. It needs **Composite health score** on: with scoring off, no account is scored, so nothing is flagged or cleared. ## How does the renewal pipeline classify accounts? Every account with a subscription renewing in the next 90 days (configurable) or with a CSM-curated renewal date in that window appears in the pipeline. Accounts are classified into four stages in priority order: **Churning** (cancelled or pending cancellation), **At Risk** (past-due payment, flagged at risk, or health score below 50), **Expanding** (stage set to Expanding), or **On Track** (everything else). ## How are renewal reminders sent? A daily job checks for annual subscriptions — and accounts with a renewal date entered by hand — whose renewal falls on a configured reminder threshold (a run missed by up to two days catches up). The default thresholds are 60 and 14 days before renewal. Each matching threshold emails the account's CSM and AE, each according to their own Mango CS email preference; there is no in-app notification. Each reminder fires only once per threshold per renewal period. Clear the cadence in Settings → Renewal Cadence to switch reminders off. ## How does a renewal proposal get generated? Click **Generate Renewal Proposal** on a renewal entry. Mango CS creates a draft proposal with the configured uplift applied (default 5%). The quote basis is the current subscription rate if one exists, then the linked contract value, then the account's annual contract value as a fallback. The proposal is valid for 30 days and runs through the same proposal-to-contract-to-e-sign flow used at first sale. ## What are the outcome tracking modes in a Success Plan? A Success Plan captures an account's goals with measurable outcomes. Each outcome uses one of five tracking modes: **Manual** (you enter measurements by hand), **Built-in** (reads from the account's health score components — overall, usage, support, sentiment, or contract risk), **Engagement** (reads from the customer tenant's workspace — post view rate, message read rate, or weekly active users), **API** (external systems push values using the outcome's auto-generated key), or **Integration** (pulls from a configured MCP connector). Non-manual outcomes sync automatically once per day. ## What does "Catch me up" on Team Activity actually read? Every human-written recap logged across **all** accounts in the workspace within the window you pick (last 24 hours, 2 days, 5 days, or 30 days) — up to the 120 most recent. It deliberately ignores the filters the feed is showing, because the point is cross-team awareness: filtering the brief would quietly hide the teammate's account you were meant to learn about. System events (handoff initiated, renewal reminder sent) are excluded, as they are in the feed. When it caps at 120 recaps it says so. ## Why does Catch me up say the brief was "generated 20 minutes ago"? Briefs are cached for 30 minutes and shared by everyone in the workspace, so the whole team's clicks cost one AI call rather than one each. Logging, editing, or deleting a recap clears the cache immediately, so a brief can never predate a recap it should have read. To force a fresh one before then, pick a different window. ## Nobody logged anything, or the AI is down — what does the brief say? The two are reported differently on purpose. "No recaps were logged in the last N days" means the window really was empty. A warning saying the recaps "weren't analysed" means the AI service didn't answer — the recaps exist and nothing has read them. It will never report a quiet week it didn't actually verify. If your workspace's AI usage limit has been reached, the card says that instead. ## Who gets the weekly "Catch me up" email, and how do I turn it on? It is off by default. An admin turns it on at Settings → Notifications → *Email a weekly "Catch me up" digest*. It goes out Monday mornings over the previous 7 days to everyone named on an account as CSM or AE, plus anyone who logged a recap that week — so an EAM or TAM working accounts they don't formally own still receives it. It respects each person's email notification preferences, and it is not sent at all if there were no recaps or the AI didn't answer. It is sent only while the Customer Success AI Agent, Team Activity and Account management are on. ## Can the AI agent take actions on my accounts? Only one: it can share an account, or one logged recap, to a channel, group or chat you can post to — the same link card as the Share button — and it asks you to confirm first. Everything else it reads: at-risk accounts, the renewal pipeline, pending handoffs, expansion candidates, account health, the tech stack, use cases and growth items, account files, and the CS tasks you or the team owe. "My" questions ("which of my accounts are at risk?", "my renewals") cover the accounts you carry as CSM, AE or a co-owner role. All other changes — assigning a CSM, flagging an account at risk, logging a call, completing a handoff, sending a renewal proposal, creating or closing a task — happen in the app, and the agent tells you where. ## How do I log a call, meeting or note on an account? Open the account and choose **Log activity**. Pick the type (Call, Meeting, Email, Note, or a type your admin added), set when it happened — it defaults to now — and write what was discussed in the description. Pick the contact you spoke with if the account has contacts. There is no duration field, so put the length of a call in the description. The activity appears on the account's timeline and in the Team Activity feed. The Ask AI agent cannot log an activity for you. ## Can I delete an account? No — Mango CS keeps every account and its history. When a customer leaves, open the account, choose **Edit**, and set the Stage to **Churned**. A churned account drops out of the at-risk list, your book and expansion candidates (a renewal still in the window shows as Churning), and its activity, contracts and notes stay on file. ## Where do I see all my tasks across every account? The **Tasks** tab. It lists every customer-success task in the workspace with the customer on each row, and it opens on your team's open work, soonest deadline first. The chips along the top are one-click filters — Open work, Overdue, Due this week, Assigned to me, Unassigned — and the filter bar narrows by customer, owner, status, deadline window, and priority. Before this tab existed the only cross-account view was the dashboard's "My open tasks" card, which is capped at five and only ever showed open work. ## Can I act on tasks from the Tasks tab, or only look at them? Both. Tick the rows you want and the bulk bar appears: **Reassign** hands them to someone else, **Mark complete** closes them. That is what the cross-account list is for — a manager looking at nine overdue rows across six customers can clear them without opening nine tabs. Each row is still checked individually against your permissions, and the result tells you exactly what happened ("6 tasks completed, 2 already finished, 1 you don't have permission to change"). Creating a task is different — that still happens where the task's context is (the Tasks card on an account, or "Create tasks" on a logged update), so every task lands attached to the right customer and there is one place each one is authored. Click any task title to open it in the Tasks app for anything else. ## Why did a bulk action skip some of the tasks I selected? Because permissions are checked per task, using the same rules the Tasks app itself applies. To **mark a task complete** you must be its assignee, a Tasks or workspace admin, or the assignee's manager. To **reassign** it you must be the person who created it, a workspace admin, or the assignee's manager. Anything already finished is counted separately as "already finished". The confirmation message accounts for every row you ticked, so the numbers always add up. ## Why are some task titles on the Tasks tab not clickable? Because you don't have access to that particular task in the Tasks app, which admits the person it is assigned to, a Tasks or workspace admin, and the assignee's manager. Rather than give you a link that bounces you back with "You do not have access to this task", the row shows the title as plain text. You can still see the task, its customer, its owner and its deadline — just not open it. ## What counts as a "CS task"? Any task linked to an account, one of its success plans, one of that plan's outcomes, or a logged update on it. That covers everything created from the account page's Tasks card, from "Create tasks" on a recap, and by the automatic off-track and renewal-risk sweeps. Tasks from other apps — a shift checklist, a workspace to-do — are not CS tasks and don't appear here, or in the dashboard's "My open tasks" card. ## The Tasks tab isn't showing — where is it? It needs two things: **Account management** on at Settings → Capabilities, and the **Tasks app** enabled for the workspace in Admin → Apps → All Apps. The Tasks app owns the underlying records, so with it switched off there is nothing to list. It has no setting of its own. --- ## When something looks wrong ## Why hasn't my health score changed even though I just logged an activity? The health score updates once per day in a nightly batch, not on every activity. An activity you log today will be reflected in tomorrow's score. The CSM-engagement component (10% of the score) gives full credit for any logged activity in the last 7 days, so a single recent activity already maximises that signal — the delay is in the snapshot, not the calculation. Product usage is a separate component, read from the customer's own workspace. ## I turned on auto at-risk flagging — why aren't any accounts getting flagged? Four things to check. First, verify the threshold in Settings → Health Score Automation — it defaults to 50, and only accounts scoring at or below that value are flagged. Second, auto-flagging only applies to accounts in Active, Renewal, or Expanding stage; accounts in Prospect, Onboarding, or Churned stage are excluded. Third, an account that is already marked At Risk will not be flagged again. Fourth, **Composite health score** must be on in Settings → Capabilities — with it off, no account is scored. ## Why can't I generate a renewal proposal for this account? Proposal generation requires at least one of: an active subscription on the account, a linked contract with a value, or an annual contract value entered on the account record. If none of these exist, there is no quote basis to apply the uplift to. The account also needs a billing contact. If Mango GTM is not enabled, the proposal pipeline is unavailable entirely. --- ## References, reviews, and expansion ## How do reference tracking and the fatigue window work? The reference finder lists contacts who are marked willing to provide a reference and have given consent. Results are sorted healthiest account first, then least-recently-called first to spread the load. When you log a reference call, the contact's call count and last-called date are updated. A fatigue warning appears if the contact was called within the fatigue window (default 90 days, configurable in Settings). Logging a call can also create a follow-up task for the CSM with a charity donation reminder, if you have configured a reference incentive amount. ## Which review sites are supported? Any site you use. Three ship with their own Settings field — G2, Gartner Peer Insights, and TrustRadius — and each appears once you paste its submission link. Everything else goes in **Settings → Advocacy → Other review sites**, one per line as `Name | link` (for example `Clearbox | https://…`), so an analyst report or a vertical review site you engage with later needs no code change. Add `| no-incentives` after the link for a site that forbids vendor incentives; Gartner Peer Insights carries that rule built in, and the app never implies an incentive there. Review requests to the same contact respect the review fatigue window (default 90 days, configurable separately from reference fatigue). ## How does expansion candidate detection work? Two signals, either of which qualifies an account. First: a healthy account (health score 75 or above) renewing in 30–90 days, by its subscription or by the renewal date set on the account — near-renewal and doing well. Second: a customer account with at least one champion contact but no logged activity in the last 30 days — a dormant champion worth re-engaging. Churned accounts and prospects are never candidates. When you ask the Ask AI agent for expansion candidates, it names the signal behind each one. The Expansion feature toggle must be on in Settings. --- ## Team Workload ## What does the Load Index measure, and what counts as Overloaded? The Load Index is a weighted composite of seven signals: revenue under management, active accounts, at-risk accounts, renewals in the next 90 days, open tasks, accounts in the Onboarding stage, and active implementation projects. Each signal is measured against a capacity baseline — for example, the default active-accounts baseline is 40 per CSM. A Load Index of 1.0 means the CSM is at exactly 100% of capacity. The four bands are Headroom (below 0.70), Balanced (0.70–0.99), Stretched (1.00–1.29), and **Overloaded** (1.30 or above). With **Workload alerts** on (Settings → Notifications, off by default), Mango CS admins receive a notification when a CSM newly crosses into Overloaded. Team Workload is off by default and visible only to admins. --- ## Licensing and limits ## Does Mango CS require a license? Yes. Mango CS requires a license and is opt-in per tenant. The license is granted through your MangoApps account team, and an administrator then enables the app from Admin → Apps → All Apps. ## What are the limits and defaults I should know about? | Item | Default | Range or cap | |---|---|---| | Health score | 0–100 composite | Updated daily; shows Not enough data when no component has data | | Health score weights | Usage 30%, CSM engagement 10%, Support 15% (where connected), Sentiment 15%, Contract risk 30% | Configurable under Settings → Health Score Model | | Auto at-risk threshold | 50 | 0–100 (configurable); a score at or below it is flagged | | Renewal reminder cadence | 60, 14 days | Configurable (comma-separated, up to 6); blank switches reminders off | | Default renewal uplift | 5% | Configurable per tenant or per quote | | Reference fatigue window | 90 days | Configurable | | Review fatigue window | 90 days | Configurable (separate from reference) | | Reference incentive amount | Blank (off) | Configurable; blank or 0 means no incentive | | CSM capacity range | 100% default | 1–200% per CSM | | Workload — Overloaded threshold | Load Index 1.30 | Fixed | | Account name | — | Max 255 characters, unique per tenant | | Handoff checklist text fields | — | Max 5,000 characters each | | Success Plan outcomes target value | — | Decimal with 4 decimal places | | AI-drafted plan | — | Up to 4 goals, each with up to 3 outcomes | | Tech stack file attachment | — | Max 100 MB per file | | Analytics windows | 30, 60, 90 days | Also 180 and 365 for some metrics | | Catch me up windows | 2 days | 1, 2, 5, or 30 days | | Catch me up recaps read | Up to 120 most recent | Says so when it caps | | Catch me up cache | 30 minutes | Cleared when a recap changes | | Weekly digest | Off | Mondays, over the last 7 days | --- ## More help - [Mango CS Overview](/help/articles/mango_cs_app_overview) - Ask AI — the assistant answers Mango CS questions from these articles. **Keywords:** faq, mango cs, customer success, health score, renewal pipeline, handoff checklist, success plan, at risk, team workload, load index, references, reviews, renewal proposal, expansion, tasks, cs tasks, overdue tasks, team activity, catch me up, weekly digest, mango-cs, mango_cs --- # Mango Signal App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 What Mango Signal is, how to set it up, how its engagement score and risk alerts work, and what each role can see. # Mango Signal ## 1. What it is Mango Signal is a workforce-engagement intelligence layer. It reads signals from apps your organization already uses — Surveys, Shift Feedback, Leader Rounds, Recognitions, Performance, Communications, Ideas, Ballots and more — blends them into a single engagement health score, clusters the recurring themes behind that number, and flags the locations or segments that have dropped below a risk threshold. Managers then create actions against those risks, and the app measures whether the score actually improved after the action was completed. - **Enablement:** Mango Signal requires a license and is disabled by default. An administrator enables it from Admin → Apps → All Apps. - **What it is not:** Mango Signal is not a survey tool. It sits on top of Surveys (and several other apps) and interprets the cross-signal context. It does not replace any source app — it reads their data as inputs. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Mango Signal**. The app appears in the sidebar once enabled. 2. Open **Mango Signal → Settings** and confirm the defaults are acceptable. The engagement score, risk alerts, close-the-loop flow, action reminders and the AI features are all on by default. The weekly engagement digest is off by default. Under **Tuning**, check who receives risk alerts — with no group chosen they go to this app's designated admins, or to every company admin if none are designated. 3. Click **Backfill last 90 days** in Settings to populate the last 90 days of historical signals. Without this step the dashboard starts empty and only fills as new upstream events arrive. 4. Verify that at least one app whose signals feed the score (Surveys, Shift Feedback, Leader Rounds, Recognitions, Performance, Communications, Ideas, or Ballots) is also enabled. Mango Signal works with whatever subset you have, but with zero source apps there are no signals to score. 5. Confirm the result: open the Mango Signal dashboard and check that an engagement score and at least one theme appear. Managers should see risk segments and recommended actions if any segment is below the threshold. **Silent-until-paired:** The backfill step is the most common miss. Without it, a freshly enabled Mango Signal shows no data until enough new upstream events accumulate — which can take days if survey or feedback volume is low. The backfill sweeps Surveys, Recognitions, Performance, Communications, Shift Feedback, Attendance, Leave, Ideas, Ballots, Leader Rounds and Frontline Execution activity from the last 90 days and is safe to re-run (it deduplicates on the source record). ## 3. How it fits together ### Signals A signal is a single normalized event from an upstream app: a survey analysis, a recognition post, a performance review, a shift-feedback submission, a reaction or comment on a Communications post. Each signal carries a type, a numeric score, and exactly one subject — a user, a location, or a named segment. Sentiment, recognition, performance, engagement and theme signals count toward the score; attendance, burnout, churn-risk and risk signals are recorded but not scored. Mango Signal does not invent signals: they come from the source apps, or from a CSV an admin imports. Eight source apps feed the weighted engagement score today: Surveys, Shift Feedback, Leader Rounds, Recognitions, Performance, Communications, Ideas, and Ballots. Three more — Time & Attendance, Leave Management, and Frontline Execution — ingest signals that appear in the signal browse and export but do not factor into the score. Individual employee sentiment is never surfaced in dashboards, analytics, or the AI assistant. Every score and theme stays aggregated to the company, a location, or a segment. The only places individual signals are visible are the **Signals** tab, its CSV/XLSX export and the same feed over the token API — restricted to business admins and Mango Signal app admins, plus any specific groups an admin grants access to in Settings. ### Engagement health score A 0-to-1 number (higher is healthier) computed from the rolling window of signals. The score blends five signal types with fixed weights: - Sentiment — 40% - Recognition — 20% - Performance — 15% - Passive engagement — 15% - Themes — 10% The score is computed for the company as a whole and separately for every location and segment. Scores are recomputed nightly. If the nightly run has not yet produced a score (for example, on a freshly enabled tenant), the dashboard computes one on demand so it is never blank. When the newest nightly score is older than the score window (no run has written one since), the dashboard, phone, home card and digest say so and show it as the last score, with its date, rather than as today's. *Example:* A company with three locations — Warehouse A, Office B, and Field Crew C — gets four scores: one company-wide and one per location. If Warehouse A's 30-day sentiment average drops while its recognition volume stays flat, Warehouse A's score falls below the threshold and appears in the risk panel, while the other two stay healthy. ### Themes Recurring concepts extracted from signals by a nightly clustering pipeline. Each theme has a label, a polarity (positive, neutral, or negative), a signal count, and an average score. The dashboard surfaces the top five themes over the last 30 days so managers can see what is driving the number, not just the number itself. A theme is shown only when at least the minimum group size of distinct people are behind it. ### Risk segments Any location or named segment whose rolling engagement score falls below the configured threshold (default 0.40). The dashboard sorts them worst-first. Segments backed by fewer signals than the minimum group size (default 5) are excluded entirely — they are not shown anonymized, they are simply not reported. ### Actions A manager-owned work item created in response to a risk. Each action has an owner, an assignee, a due date, a status (Open, In Progress, Complete, or Dismissed), and optionally a scope (the whole company, a location, or a segment) and a set of linked source signals. Action titles are limited to 200 characters. When a manager sees a risk segment on the dashboard, the app recommends one to three concrete next actions. On the initial page load these are heuristic (instant); clicking **Refresh with AI** replaces them with AI-written recommendations when the **AI-written action recommendations** setting is on (with it off, the built-in recommender answers instead). ### Close-the-loop When an action is marked complete and the close-the-loop flow is on, three things happen: 1. A baseline engagement score for the action's scope is captured — the score over the 30 days before completion. 2. A "you said, we did" update is published to the people the action is about. A **company**-scoped action goes out as a company Broadcast to everyone in the business. An action with **no scope** is posted to the Communications feed for everyone. A **location** action is posted to the Communications feed for the people at that location and the locations under it. A **segment** action has no people of its own, so its update is posted only if whoever completes it ticks **Also post this update to everyone**. (Feed posts are skipped if Mango Signal's posts are switched off in the Communications settings.) 3. The people whose feedback the action was raised from receive an email. The baseline triggers a follow-up measurement after 30 days to compute the real delta. With the close-the-loop toggle off, completing an action sends no update or emails and starts no impact measurement — completed actions still appear in the **What Changed** archive. ### Impact measurement Each action completed while the close-the-loop flow is on gets a baseline score and a re-measurement 30 days after completion (a fixed window). The Impact tab shows per-action delta, delta percentage, and a status: pending, measured, inconclusive, or failed. It also rolls up measured, pending, positive and negative counts and the average delta across measured actions. A result needs at least 5 post-action signals, from enough people to clear the anonymity floor; otherwise it is inconclusive. ### Role-based access Mango Signal has three access tiers. What each role sees in the sidebar: | Role | Tabs visible | |---|---| | All users | Dashboard, What Changed, Actions (the actions they own or are assigned) | | Manager or above (and app admins) | Dashboard, What Changed, Actions (every action), Impact, Analytics | | Admin or above (and app admins) | All of the above plus Signals and Settings | App admin status can be granted per user, giving them the same access as a full administrator within Mango Signal without elevating their platform-wide role. The **Signals** tab also appears for anyone in a group an admin adds under **Who can read individual signal detail?** in Settings. ## 4. Running it ### Reviewing the dashboard The dashboard is the landing page. It shows the current company-wide engagement score, the top five themes, and (for managers) the worst three risk segments with recommended actions. Below the risk panel, the current user's open actions appear in due-date order (up to 5). A sample-data banner appears when demo signals are loaded. ### Creating and managing actions 1. On the dashboard, click a recommended action or go to **Actions → New**. 2. The form opens in a drawer. Fill in the title, description, assignee, due date, and optionally the scope (company, location, or segment) and linked signals. 3. Save the action. The assignee receives an email notification if they are not the owner. 4. When the work is done, the owner or the assignee clicks **Mark complete**. This fires the close-the-loop flow. Open actions with a due date trigger reminders: the assignee (or the owner, if the assignee is no longer active) is reminded when the action comes within 3 days of its due date (usually 3 days and again 1 day before), then the assignee and owner are reminded every 3 days while it is overdue, stopping 60 days past due. These are automatic; an admin can switch both off with **Action reminders (due soon and overdue)** in Settings. ### Viewing impact Go to **Impact**. Each row shows a completed action, its baseline and post-action scores, and the delta. The summary bar at the top shows counts of measured, pending, positive, and negative outcomes plus the average delta. Sample-data rows are labeled and excluded from the summary averages. ### Reviewing what changed (all employees) The **What Changed** tab is visible to all users, not just managers. It lists completed actions with their title, description, completion date, and impact direction — but omits the owner and assignee names. This is the employee-facing "you said, we did" archive. ### Browsing raw signals (admins and granted groups) **Signals** shows every individual ingested signal with its source app, type, score, and date. Because it exposes individual named sentiment, it is restricted to business admins and Mango Signal app admins by default; an admin can add specific groups (for example People Ops) under **Who can read individual signal detail?** in Settings. Filter by source app, signal type, segment, or time window. ### Using analytics Go to **Analytics**. The page shows the current engagement score, total signal volume, at-risk segment count, open action count, and a daily signal-volume trend chart. Use the window selector to switch between 7, 30, 90, or 180 days. Analytics is available to managers and above. ### Exporting and importing data People who can read individual signal detail (business admins and Mango Signal app admins, plus any group granted in Settings) can export raw signals to CSV or XLSX — from the Analytics page over its selected window (7, 30, 90, or 180 days), or from the Signals tab (the last 30 days). Other managers see the aggregate Analytics page without the export buttons. Admins can also import signals from a CSV file using a downloadable template — useful for backfilling from a retired feedback tool. ### Notifications Mango Signal sends seven types of notifications. Each is delivered by email and in-app bell. Users can mute them from their notification preferences under two categories: **Mango Signal** (risk alerts and the weekly digest) and **Mango Signal · Your Actions** (assigned, due-soon, overdue, completed and close-the-loop notices). | Notification | Who receives it | Frequency | |---|---|---| | Risk alert | The group chosen under **Settings → Tuning** (only its managers, admins and app admins); with no group chosen, this app's designated admins, or every company admin if none are designated | At most once every 7 days per recipient while the same segments stay at risk; a change in which segments are at risk can alert again the next day | | Action assigned | The assignee (when different from the owner) | One-time on creation | | Action due soon | The assignee — or the owner, if the assignee is no longer active | When the action comes within 3 days of its due date — usually 3 days and 1 day before | | Action overdue | The assignee and owner | Every 3 days while overdue, stops 60 days past due | | Action completed | The owner, when someone else completes it | One-time per completion | | Close-the-loop update | The people whose feedback the action was raised from | One-time on completion | | Weekly digest | Managers and admins, plus anyone who owns or is assigned an open action | Every Monday (opt-in; off by default) | ### Mobile Mango Signal has a mobile dashboard at **/m/apps/mango-signal**. It shows the engagement score, top themes, and open actions assigned to the current user, and the **What Changed** archive. From an action's phone page, its owner or assignee can mark it in progress or complete it. Opening Mango Signal on a phone redirects to the phone view automatically; the "open on desktop" link (`?desktop=1`) keeps that phone on Mango Signal's desktop pages until it opens a phone page again. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | **Engagement health score** | Settings | On | Turns the nightly score computation on or off. Switching it off also stops risk alerts; signals, themes, actions and the dashboard's risk-segments panel keep working. | | **Risk alerts** | Settings | On | Emails one alert naming every location or segment below the risk threshold. Who receives it is set under **Tuning**. Needs the engagement health score on. | | **Close-the-loop "you said, we did" flow** | Settings | On | Controls whether completing an action publishes the update, emails the people whose feedback fed it, and starts impact measurement. Completed actions still appear in What Changed even when this is off. | | **Weekly engagement digest email** | Settings | Off | Every Monday, emails managers and admins — plus anyone who owns or is assigned an open action — the company score and its week-on-week change, the top themes, and their own open and overdue action counts. | | **Action reminders (due soon and overdue)** | Settings | On | The due-soon and overdue reminders. The one-time "action assigned" email is not affected. | | **AI theme extraction (nightly)** | Settings | On | Once a night, AI clusters the phrases attached to the last 30 days of signals into themes. Off: no phrases are sent to the AI provider and existing themes stop refreshing. | | **AI-written action recommendations** | Settings | On | Lets AI write the recommendations behind **Refresh with AI** and the assistant's suggestions. Off: the built-in recommender is used. | | **Mango Signal AI assistant in Ask AI** | Settings | On | Enables or disables the Mango Signal assistant in Ask AI. | | **Engagement score window (days)** | Settings | 30 | The rolling window of signals used to compute the engagement score — and with it the risk-segments list, the risk-alert email and the weekly digest. Top Themes always covers 30 days. | | **Risk alert threshold (0–1, higher = more alerts)** | Settings | 0.40 | Locations and segments scoring below this value appear as at-risk, so a higher threshold flags more of them. At 0, nothing is ever at risk. | | **Minimum group size for reporting** | Settings | 5 | The anonymity floor. A location or segment is shown or alerted on only when at least this many signals were filed about it, and a theme only when at least this many distinct people are behind it. It can't go below the company-wide smallest group (5 unless raised under Retention & Legal Holds); maximum 50. | | **Route risk alerts to this group** | Settings | None | Sends risk alerts to this group instead of this app's admins; only its managers, admins and app admins receive them. | | **Who can read individual signal detail?** | Settings | Admins only | Who can open the Signals tab and export raw signals. Business admins and Mango Signal app admins always can; you can add specific groups. | ## 6. More help - **Mango Signal FAQ** — specific setup and operating questions, limits, and troubleshooting. - **REST API** — a scoped read/write API is available at `/api/v1/mango_signal` for native mobile and external integrators, tenant-scoped and role-gated to match the web surface. - **Ask AI** — the assistant answers questions about Mango Signal from these articles. **Keywords:** mango signal, engagement score, workforce engagement, risk alert, sentiment, close the loop, theme clustering, action planning, manager actions, impact measurement, mango-signal, mango_signal --- # Mango Signal FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Mango Signal — for the admin running it. # Mango Signal FAQ Answers to common setup and operating questions about Mango Signal. For what the app is and how to set it up from scratch, see the [Mango Signal Overview](/help/articles/mango_signal_app_overview). --- ## Setup ## Do I need other apps running before Mango Signal shows data? Yes. Mango Signal reads signals from the other apps your business already runs. Eight apps feed the engagement score today: Surveys, Shift Feedback, Leader Rounds, Recognitions, Performance, Communications, Ideas, and Ballots. Mango Signal works with whatever subset you have enabled — even one is enough to produce a score. Time & Attendance, Leave Management, and Frontline Execution also ingest signals (visible in the Signals tab, export and the API) but do not factor into the score. ## How do I backfill historical signals when we first turn on Mango Signal? Open **Settings** and click **Backfill last 90 days**. The system scans the last 90 days of Surveys, Recognitions, Performance, Communications, Shift Feedback, Attendance, Leave, Ideas, Ballots, Leader Rounds and Frontline Execution activity and creates signals from it. The backfill is idempotent — running it again does not create duplicates. Signals will start appearing within a few minutes, and the engagement score recomputes on the next nightly run or on-demand from the dashboard. --- ## Permissions and access ## Who can see what in Mango Signal? Mango Signal has three access tiers: 1. **All employees** see the Dashboard (engagement score, top themes, their own open actions), the What Changed tab (completed close-the-loop actions), and the Actions tab (the actions they own or are assigned). 2. **Managers** (Manager or above, or an app admin) see every action, and also the Impact and Analytics tabs. 3. **Administrators** (Admin or above, or an app admin) also see the Signals tab (raw per-employee signal data) and the Settings tab. An administrator can give specific groups the Signals tab too. On a phone, the dashboard shows the engagement score, top themes, and the user's open actions, and an action's owner or assignee can mark it in progress or complete it there. ## Who can browse the raw per-employee signal data? By default, only business administrators and Mango Signal app admins. An administrator can add specific groups (for example People Ops) under **Who can read individual signal detail?** in Settings; that one grant covers the Signals tab, the CSV/XLSX export, and the raw-signal API feed. Every other surface — the dashboard, themes, risk segments, and the AI assistant — aggregates data to the company, a location, or a segment. Individual employee sentiment is never surfaced outside those three. --- ## Day-to-day ## How is the engagement health score calculated? The score is a weighted average of normalized signals over the configured window (default 30 days). Five signal types contribute: - Sentiment — 40% - Recognition — 20% - Performance — 15% - Engagement — 15% - Themes — 10% The result is a number between 0 and 1, where higher means healthier. Scores are computed for the company as a whole and for every location and segment. ## How often does the score update? The system recomputes scores nightly at approximately 02:30 UTC. If no cached score exists yet (for example, right after enabling the app), the dashboard computes one on demand from the current signals so it never shows blank. ## What triggers a risk alert email, and who receives it? When a location's or segment's engagement score drops below the configured **Risk alert threshold** (default 0.4 on a 0–1 scale), the nightly computation sends one email and in-app notification naming every segment that slipped. It goes to the group chosen under **Settings > Route risk alerts to this group** (only the managers, admins and app admins in that group receive it) or, with no group chosen, to this app's designated app admins — falling back to every company admin when none are designated. To prevent repeated alerts about the same persistent risk, each recipient is re-alerted at most once every 7 days while the same segments stay at risk (a change in which segments are at risk can alert again the next day). Admins can adjust the threshold under **Settings > Risk alert threshold** — a higher threshold flags more segments. ## What happens when an action is marked complete? Three things happen in sequence: 1. A baseline engagement score is captured for the action's scope — the score over the 30 days before completion. 2. A "you said, we did" update goes to the people the action is about: a company-scoped action goes out as a company Broadcast; an action with no scope is posted to the Communications feed for everyone; a location action is posted to the Communications feed for the people at that location and the locations under it; a segment action is posted only if whoever completes it ticks **Also post this update to everyone**. The people whose feedback the action was raised from also receive an email. 3. A follow-up measurement runs after 30 days to compare the post-action score against the baseline and report the delta. This entire flow is gated by the **Close-the-loop** setting. Disabling it still lets people complete actions — it suppresses the update, the emails and the impact measurement; the action still appears in What Changed. ## How does the AI assistant work, and can it change data? The Mango Signal assistant appears in Ask AI when the **Mango Signal AI assistant** setting is turned on (it is on by default). It has seven read tools (engagement score, themes, risk segments, recommendations, action list, action detail, impact summary) and two write tools (create action, update action status). Every write requires the user to confirm before it takes effect. Manager-tier data stays gated to managers and admins even inside the assistant. ## How do I turn on the weekly engagement digest? Go to **Settings** and enable **Weekly engagement digest email**. The digest is off by default. When enabled, every Monday managers and admins — plus anyone who owns or is assigned an open action — receive an email summarizing the company engagement score, the trend versus the previous week, the top three themes over the last 30 days, and their own open and overdue action counts. Only manager-tier readers also see the number of at-risk segments. If nothing happened in the past week and the reader has no open actions, the digest is skipped. --- ## When something looks wrong ## The dashboard shows no data even though we use Surveys and Recognitions — why? Two common causes: 1. **No backfill.** Mango Signal only ingests signals going forward from the moment it is enabled. Historical data from before enablement does not appear automatically. Click **Backfill last 90 days** in Settings to scan the last 90 days. 2. **No scored signal types.** The upstream data may have been ingested but under a signal type that does not contribute to the score. Only sentiment, recognition, performance, engagement, and theme types factor into the engagement score. ## Someone says they stopped receiving risk alert emails — what should I check? Check these in order: 1. **Settings > Risk alerts** and **Engagement health score** — if either is off, no risk alerts are sent. 2. **Route risk alerts to this group** — a chosen group receives the alerts instead of this app's admins, and only its managers, admins and app admins get them; with no group, they go to designated app admins, or to every company admin if none are designated. 3. **Risk alert threshold** — if it was lowered, fewer segments qualify as at-risk. 4. **7-day dedup window** — while the same segments stay at risk, each recipient is re-alerted at most once every 7 days. 5. **Notification preferences** — the person may have opted out of the "Mango Signal" notification category in their personal notification settings. ## An action's impact shows "inconclusive" — what does that mean? The post-action measurement requires at least 5 signals in the action's scope during the 30-day measurement window, from enough people to clear the anonymity floor. If fewer arrived, there is not enough data to compute a reliable comparison and the result is marked inconclusive. This typically happens for narrowly scoped actions (a single small location or segment) where signal volume is low. ## Why can't I see the Impact or Analytics tab? The Impact and Analytics tabs are visible only to managers (Manager role or above) and Mango Signal app admins. Every employee sees the Dashboard, the What Changed tab, and the Actions tab, which lists the actions they own or are assigned. Ask your administrator if you need manager-level access to Mango Signal. ## Can my manager see my individual survey responses through Mango Signal? No. The dashboards, analytics, and AI assistant always aggregate data to the company, a location, or a segment. Individual employee feedback is never surfaced. The only exception is the Signals view and its export, which show raw signal records and are restricted to administrators (and any group an administrator grants access to). ## Why are some locations or segments not showing up in the risk segments panel? The **Minimum group size for reporting** setting (default 5) sets a floor on the number of signals a location or segment must have before it appears in the risk panel. Groups with fewer signals than this are excluded entirely to protect anonymity. The floor can't be set below your company-wide smallest group (5 unless raised under Retention & Legal Holds), so small groups stay hidden by design; raising the setting (up to 50) hides more of them. --- ## Licensing and limits ## Does Mango Signal require a licence? Yes. Mango Signal requires a licence and is disabled by default. An administrator enables it from Admin → Apps → All Apps. It is not bundled into any operational suite — it is a standalone premium add-on. ## What are the configurable settings and their allowed ranges? All settings are under the Settings tab (admin access required): | Setting | Default | Allowed range | |---|---|---| | Engagement health score | On | On / Off | | Risk alerts | On | On / Off | | Close-the-loop "you said, we did" flow | On | On / Off | | Weekly engagement digest email | Off | On / Off | | Action reminders (due soon and overdue) | On | On / Off | | AI theme extraction (nightly) | On | On / Off | | AI-written action recommendations | On | On / Off | | Mango Signal AI assistant in Ask AI | On | On / Off | | Engagement score window (days) | 30 | 1–365 | | Risk alert threshold (0–1, higher = more alerts) | 0.4 | 0.0–1.0 | | Minimum group size for reporting | 5 | Company-wide smallest group (5 or more)–50 | | Route risk alerts to this group | None (this app's admins) | One notification group | | Who can read individual signal detail? | Admins only | Admins only / Admins plus specific groups | --- ## More help - [Mango Signal Overview](/help/articles/mango_signal_app_overview) - Ask AI — the assistant answers Mango Signal questions from these articles. **Keywords:** faq, engagement score, risk alert, close the loop, action item, impact measurement, signal ingestion, weekly digest, anonymity floor, threshold, not showing, permissions, export, import, mango-signal, mango_signal --- # Mango Spend App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How Mango Spend handles employee expense reimbursements, company-card receipts, vendor invoices, and pre-approvals — setup, concepts, and admin operations. # Mango Spend ## 1. What it is Mango Spend handles expense reimbursements, company-card receipt tracking, vendor invoices, and pre-approvals inside OneMango. Employees photograph or email receipts; AI reads the vendor, total, tax, date, and category from each image. A policy engine checks every line against configurable caps, blocked categories, and duplicate detection before the report reaches an approver. - **Enablement:** Mango Spend requires a license and is off by default. An admin enables it in **Admin → Apps → All Apps**. - **What it is not:** Mango Spend is the employee-incurred and vendor-bill side of spend. It does not process payroll, calculate tax withholding, or move money — it produces payroll-ready CSVs and accounting exports that your payroll or ERP system consumes. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Mango Spend**, and toggle it on. 2. In the Mango Spend sidebar, open **Admin → Settings** and review the policy defaults. The receipt-required threshold, stale-expense age and default currency all take effect immediately. Mileage rates and blocked categories are set on their own pages (Mileage Rates, Categories). 3. If you use mileage tracking, turn on **Mileage tracking** in Settings (it is off by default), then go to **Admin → Mileage Rates** and add at least one rate with a start date. Without a rate, employees cannot submit mileage lines — a mileage line no rate could price is refused at submit, whether Policy enforcement is on or off. 4. Approval defaults to the employee's manager. To route approvals by amount, department, category, or cost center, enable **Conditional approval rules + delegations** in Settings, then create rules under **Admin → Approval Rules**. 5. Confirm the rollout by submitting a test report. The employee's **Reimbursements** list should show the draft, and the manager's **Approve → Employee Spend** should show it once submitted. **Silent-until-configured:** Vendor invoices and pre-approvals are off by default. An admin must turn on **Vendor invoices** or **Pre-approvals** in Settings before the tabs, inbox sections, and submission forms appear. The same applies to per-diem rates, multi-currency support, and corporate card features. Each of these is a separate toggle in Settings; enabling the app alone does not activate them. **Roles:** Every member with access to the app can submit reports and view their own data. Managers see the **Approve** section for their direct reports; anyone allowed to run payments sees **Pay → Employee Spend**. Mango Spend app admins see Settings, Categories, Mileage Rates, Budgets, Analytics, Saved Views, and the accounting sync surfaces. ## 3. How it fits together Mango Spend tracks four record types. They serve different sides of spending but share a common approval pattern and appear in the same inbox. **Expense report** — the core record. An employee creates a report, adds one or more expense lines, attaches receipts, and submits it for approval. Reports move through a single lifecycle: Draft → Submitted → Approved → Paid. An approver can also reject a report (final — the employee uses **Duplicate** to start a new draft from it; the copy keeps each line's original date and carries no receipts; a copy of any other report dates every line today) or send it back for changes (the employee edits and resubmits it). The employee can **Recall** a submitted report to draft; approval then starts over when it is resubmitted. A report cannot be submitted while it is empty or while any line has no amount. Each report gets a unique number (e.g. ER-2026-00001) and tracks its own total, reimbursable amount, and currency. **Expense line** — a single purchase within a report. Each line is one of three types: - **Expense** — a vendor, amount, category, and optional receipt. - **Mileage** — a distance in miles. The amount is computed automatically from the mileage rate in effect on the trip date. If no rate covers the trip date the line has no amount and cannot be submitted; it is priced automatically as soon as someone who manages spend rates saves a rate that covers it. - **Per diem** — a number of days and a location code. The amount is computed from the per-diem rate configured for that location. Lines can be split across GL tags (cost center, project code, category) using allocations that must sum to 100%. **Company-card receipt** — a separate record documenting a purchase on a corporate card. Nothing is owed back to the employee; the receipt exists so finance can prove what a card charge was for. Receipts follow their own lifecycle: Draft → Submitted → Approved. A reviewer can send a receipt back (it then reads **Sent back**), and until it is approved its owner can take a submitted receipt back with **Withdraw to edit**. If nobody else can review it — the submitter is the only Mango Spend admin and has no manager on file — the receipt says so instead of waiting silently. When corporate cards are enabled, the system can auto-match receipts to bank-imported card charges by comparing amount, date, and vendor. **Vendor invoice** — a bill the company owes a vendor, enabled separately in Settings. Invoices follow: Draft → Submitted → Approved → Paid, with an approver able to send back or decline. Payment records how the money left (ACH, Cheque, Wire, Card, or Other) and supports short-pays. A vendor roster tracks W9 status — missing W9s warn but never block. Invoice files must be PDF, PNG, or JPEG, up to 25 MB. **Pre-approval** — permission to spend before the money moves. An employee asks "may I spend $1,800 on the Denver conference?" and a manager approves or declines. Once approved, expense reports can be linked to the pre-approval, and the system tracks actual spend against the approved amount. Over-budget is a warning, not a block — the employee is never stopped mid-trip. Pre-approvals follow: Draft → Submitted → Approved → Closed. **Budget** — an admin-defined spending limit scoped to a dimension: the whole business, a single category, a cost center, a department, or a specific employee. Each budget covers a date range and is kept in your **Default currency** — spending is added up in that currency, so a budget in any other currency would compare unlike amounts (an older budget saved in another currency is flagged on the Budgets page). When a report's total would push a budget past its limit, the policy engine flags a warning — it does not block submission. **How reports, pre-approvals, and budgets relate:** A pre-approval reserves a ceiling ("you may spend up to $1,800"); the expense report records what was actually spent; a budget tracks all spend in its scope across all employees. These three levels of control operate independently but surface together in policy warnings at submit time. **Worked example:** An employee creates a report titled "Denver Conference — June 2026," adds an airfare expense line for $420 (category: Travel — Airfare, receipt attached), a mileage line for the 32-mile drive to the airport (priced at the rate in effect on the trip date), and a lodging line for $189/night. AI reads the airfare receipt and fills in the vendor, date, and tax. The policy engine flags a warning because the lodging line exceeds the Lodging category's per-expense cap of $300. The employee submits; the report routes to their manager, who sees the policy warning and approves. Finance later batches the report into a payroll-ready CSV for Gusto. **Email inbox for receipts:** Each user has a personal receipt email address (format: `receipts+@`). Forwarding a receipt to that address creates a draft expense report with the attachment, and AI reads the receipt automatically. The receipt must be an **attachment** (a PDF or a photo): the text of an email is not read, and an email with nothing attached files nothing — the sender gets an in-app notice saying so. Up to 10 attachments per email, each up to 15 MB. Accepted file types: PDF, JPEG, PNG, HEIC, HEIF, WebP, and GIF. ## 4. Running it ### Reviewing and approving reports 1. Go to **Approve → Employee Spend**. 2. Open a submitted report. Policy violations appear inline — warnings let the report proceed; blocks prevented submission and should not appear here. 3. Choose **Approve**, **Request changes** (under *Send back for changes…* — say what should change), or **Reject** (requires a reason). When conditional approval rules are enabled, a report may pass through a multi-step chain. Each step's approver decides in turn; approving advances the report to the next step. A Mango Spend admin can decide a report directly, which settles it for every remaining step — the decision card says whose it is first. Approval rules match on amount thresholds, categories, cost centers, submitter role, department, location, or role type. The first matching active rule (by priority order) owns the chain. When no rule matches, the report falls back to the employee's manager. ### Paying out approved reports 1. Go to **Pay → Employee Spend**. The reports waiting to be paid are listed at the top; choose **New batch**. 2. Select a payroll export format: Generic, ADP, Gusto, Paychex, or an accounting format (QuickBooks, Xero, NetSuite, Sage Intacct). 3. Add approved reports to the batch (while the batch is still open, **Remove** takes a single report back out), then choose **Export CSV & lock**. Exporting locks the batch and downloads the file — it does **not** pay anyone: every report in it stays **Approved**. 4. Run the file through payroll or your accounting system. When that run is confirmed, come back to the batch and choose **Mark as paid**. That is the step that moves each report to **Paid** (and, when *Notify employees on decisions / payouts* is on, tells each employee). A batch that has been voided keeps a list of the reports it released, with each amount, so a file already uploaded to payroll can be cancelled there. On the Pay lists, a report whose owner is no longer active in the company is marked, and the export warns about it — it is still paid. Payroll formats produce one row per report. Accounting formats produce one row per GL slice (line or allocation), tagged with cost center and project code. ### Managing categories Go to **Admin → Categories** to add, rename, block, or set caps on expense categories. Each category can have a per-expense cap and a daily cap. Blocked categories prevent employees from filing expenses against them. A category can also require a receipt regardless of the global receipt threshold. Nine default categories are seeded automatically the first time anyone opens Mango Spend: Meals & Entertainment, Travel — Airfare, Travel — Lodging, Ground Transportation, Office Supplies, Software / SaaS, Conferences, Telecom, and Other. ### Setting up approval coverage Under **Coverage**, an approver can hand their approvals to a colleague for a date range. Coverage needs **Conditional approval rules + delegations** or **Pre-approvals** switched on in Settings. While it is active: - With **Conditional approval rules + delegations** on, an expense report **submitted during the window** that would route to the original approver goes to the delegate instead, and stays with the delegate even after the coverage ends. With it off, expense reports are not rerouted: they keep going to the submitter's manager. - A report that was **already waiting** on the original approver when coverage started does not move — they still decide it (or a Mango Spend admin can). - **Pre-approval requests** follow the coverage as it stands today: they go to the delegate while it is active and return to the original approver when it ends. - **Company-card receipts** are never rerouted; they stay with the reviewer chosen in Settings. Both people must belong to the same organization. ### Managing vendor invoices When vendor invoices are enabled, **Approve → Vendor Invoices** shows every bill submitted to the group, and **Pay → Vendor Invoices** lists the approved bills waiting to be paid, alongside the **Vendors** roster. The approver group is configurable in Settings; if no group is set, Mango Spend admins serve as the fallback. Approvers can approve, send back (with a reason), or decline from the Approve page. Recording payment happens from the Pay page and requires choosing a payment method and optionally a reference number. ### Managing budgets Under **Admin → Budgets**, create period-bounded spending limits scoped to the whole business, a category, a cost center, a department, or a specific employee. Active budgets are checked at submit time; exceeding a budget produces a warning on the report. ### Accounting sync When **Live accounting sync (Merge.dev)** is enabled in Settings, approved reports and payment batches can be pushed to QuickBooks, Xero, NetSuite, or Sage Intacct. The **Admin → Accounting Sync** page shows push status and lets you retry failed pushes; a failed push of a report that a later push landed is shown as **Resolved** and no longer counted as failed. Imported accounting data (accounts, expenses, invoices, line items, payments, and webhooks) appears under **Admin → Accounting Data**. ## 5. Settings Open **Admin → Settings** in the Mango Spend sidebar (Mango Spend app admins only). The page is laid out in the cards below; each row is named as the page names it. ### What people can submit | Setting | Default | What it changes | |---|---|---| | **Pre-approvals** | Off | Enables the pre-approval workflow: employees ask permission to spend before the money moves, and the request appears under Approve → Pre-Approvals. | | **Reimbursements** | On | Master switch for expense reports. Turning it off hides the Reimbursements tab, the receipts-by-email inbox, My Preferences and Pay → Employee Spend — close out any exported batch first. | | **Company card receipts** | On | The receipt log for purchases already charged to a company card. Nothing is owed back to the employee. | | **Company card receipts → Reviewed by** | The submitter's manager | Who reviews a submitted company-card receipt: the submitter's manager, a Mango Spend admin, or no one (auto-approve). | | **Vendor invoices** | Off | Enables the vendor invoice workflow, the vendor roster, and the Vendor Invoices rows under Approve and Pay. | | **Vendor invoices → Approved by** | Blank (Mango Spend admins) | The group (Admin › Groups) whose members approve and pay vendor invoices. When blank, Mango Spend admins do both. | ### Who can do what Each defaults to Mango Spend admins and can name specific people instead, so finance staff do not need to be company admins. | Setting | Default | What it changes | |---|---|---| | **Who can see company-wide spend?** | Mango Spend admins | Analytics across every record type, the saved views built from it, and their emailed digests. | | **Who can run reimbursement payments?** | Mango Spend admins | Building payout batches, downloading the payroll CSV and marking a batch paid. | | **Who can keep the rate cards up to date?** | Mango Spend admins | The Mileage Rates, Per-Diem Rates and FX Rates pages. Categories and caps stay with admins. | ### Features | Setting | Default | What it changes | |---|---|---| | **Mileage tracking** | Off | Shows the Mileage Rates page and the mileage line type. Add a rate before announcing it — with no rate, mileage lines are blocked at submit. | | **Per-diem rates** | Off | Shows the Per-Diem Rates page and the per-diem line type. | | **Multi-currency + FX snapshot at submit** | Off | Enables the FX Rates page and locks exchange rates at submission time. | | **Conditional approval rules + delegations** | Off | Enables the Approval Rules page and Coverage. Without it, reports route to the employee's manager. | | **AI document reading (receipts & invoices)** | On | Uses AI to read vendor, total, tax, date, and category from uploaded receipts and vendor invoices. Off: the fields are typed by hand. | | **AI auto-categorization of receipt lines** | On | Lets the AI assign a category when reading a receipt. Only applies while AI document reading is also on. | | **Corporate cards (CSV import + auto-match)** | Off | The card statement feed: shows Card Accounts, Card Charges and Card Reconciliation, and matches receipts to imported card charges. | | **Corporate cards are individually billed (employee pays the card bill)** | Off | Off (the usual setup): the company pays the card issuer, so a charge matched to an expense line is not reimbursed. On: the employee pays their own card bill, so matched card lines stay reimbursable. | | **Mango Spend AI agent** | On | Lets your team ask about their own spend, approvals, cards and budgets from the assistant, and draft a report or a spend request in plain English. | | **Live accounting sync** | Off — no live sync | Pick a connected accounting system (a company admin connects it in Admin › Integrations) to push approved and paid reports to it as bills. Picking one turns sync on; choosing **Off — no live sync** turns it off. | ### Policy | Setting | Default | What it changes | |---|---|---| | **Receipt required at or above** | $25.00 | Expense lines at or above this amount must have a receipt (mileage and per-diem lines never need one). Set to 0 to require a receipt on every expense line. **This is not the whole rule:** a category with *Always require a receipt* ticked needs one at any amount, and seven of the nine default categories have it ticked. | | **Flag expenses older than (days)** | 90 | Lines with a spend date older than this trigger a warning. | | **Default currency** | USD | The currency for new reports and the home currency for FX conversions. Options: USD, EUR, GBP, CAD, AUD. Changing it converts nothing: every cap, rate and threshold keeps its number and is read in the new currency. A budget keeps the currency it was saved in while its spend is added up in the new one; the Budgets page flags it until it is saved again. | | **Default payroll export format** | Generic | The file layout used for new payment batches. Options: Generic, ADP, Gusto, Paychex, QuickBooks, Xero, NetSuite, Sage Intacct. A batch can override it. | | **ADP company code (Co Code)** | Blank | The first column of the ADP export. Left blank, the file carries the placeholder 0000, which ADP rejects. Only used with the ADP format. | | **Policy enforcement** | On | Master switch for the policy engine: caps, blocked categories, the receipt rule, duplicate, age, rate and budget checks. When off, none of these is computed — including duplicate detection, whatever its own switch says. | | **Duplicate expense detection** | On | Flags a warning when a line matches a line on another report with the same vendor, amount and date — or the same person's line with the same description, amount and date, which is how a line typed in by hand (it has no vendor) is matched — within the look-back window. A rejected or cancelled claim is never matched. Needs Policy enforcement on. | | **Duplicate expense detection → Look back (days)** | 30 | How far back the duplicate check searches. | ### Notifications | Setting | Default | What it changes | |---|---|---| | **Notify employees on decisions / payouts** | On | Sends email and in-app notifications when reports are approved, rejected, sent back, or paid. | | **Notify approvers of reports, vendor invoices, card receipts & pre-approvals awaiting review, plus invoice due/overdue reminders** | On | One switch for eight messages: reports, vendor invoices, company-card receipts and pre-approvals awaiting review, approver reminders, and the invoice due-soon and overdue digests. | | **Remind employees about expense lines still missing a receipt** | On | The recurring in-app nudge to an employee holding draft lines that still need a receipt. | | **Send budget alerts when a budget passes 80% or 100%** | On | The in-app budget alert. It goes to the budget's owner when the budget is for one employee; otherwise to the Mango Spend app admins, or to the company admins when no app admin is named. | ### Vendor invoice reminders | Setting | Default | What it changes | |---|---|---| | **Remind approvers after … days** | On, 3 days | Reminds the approver group about a vendor invoice that has waited this long. | | **Warn about invoices due within … days** | On, 5 days | Sends the approver group a digest of approved invoices coming due, and of overdue ones. | ## 6. More help - **Mango Spend FAQ** — specific setup, operating, and troubleshooting questions. - Ask AI — the assistant answers questions about Mango Spend from these articles. **Keywords:** expense reimbursement, receipt OCR, mango spend, expense report, corporate card, vendor invoice, pre-approval, mileage, per diem, payroll export, approval workflow, expense policy, mango-spend, mango_spend --- # Mango Spend FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Mango Spend — for the admin running it. # Mango Spend FAQ Answers to common setup and operating questions about Mango Spend. For what the app is and how to set it up from scratch, see the [Mango Spend Overview](/help/articles/mango_spend_app_overview). --- ## Setup ## Do I need to configure anything before employees can start submitting? Mango Spend seeds a default set of expense categories the first time anyone opens the app, so basic expense reports work immediately. Mileage and per-diem lines are off by default: turn on **Mileage tracking** or **Per-diem rates** in Settings, then add at least one mileage rate or per-diem rate before employees can submit those line types. The policy engine is on by default with a $25 receipt-required threshold, a 90-day stale-expense flag and 30-day duplicate detection. No category is blocked until you block one. ## What are the default policy settings, and where do I change them? All policy settings live under **Settings** in the Mango Spend app. The defaults are: - **Receipt required at or above:** $25 (set to $0 to always require a receipt) - **Flag expenses older than:** 90 days - **Duplicate lookback:** 30 days (accepts 1–365) - **Blocked categories:** none — tick **Block this category** on it under **Admin → Categories** - **Duplicate detection:** On - **Policy enforcement:** On (turns off all policy checks when disabled — caps, receipt rules, blocked categories, duplicate and age flags, rate and budget checks; a report still needs at least one line and an amount on every line, including a mileage or per-diem line no rate could price) Two default categories also carry per-line caps: **Meals & Entertainment** at $75 and **Travel — Lodging** at $300. You can change any cap, add new categories, or block additional ones under **Admin → Categories**. --- ## Permissions and access ## Who can submit, approve, and configure Mango Spend? All roles — member, manager, admin, and super admin — can access the app by default. Members submit and view their own reports. Managers see their own reports plus their direct reports' and can approve them. App admins see every report in the business, manage settings, run payment batches, and view analytics. ## Why can't a manager see another team's expense reports? Managers see only their own reports and their direct reports'. To see all reports across the business, the user needs app-admin access. Promote them to app admin or super admin, or give them the Mango Spend app-admin role in Admin → Apps → All Apps. --- ## Day-to-day ## How do I forward receipts by email instead of using the app? Each user has a personal receipt inbox address (visible in their Preferences). Forwarding a receipt to that address creates a draft expense report for the day and adds a line with the attachment. AI extraction runs automatically and fills in vendor, amount, date, tax, currency, and a category guess. One email can carry up to 10 attachments, each up to 15 MB. Accepted file types are PDF, JPEG, PNG, HEIC, HEIF, WebP, and GIF. ## How does the policy engine decide what to flag? The engine evaluates every report at submit time and stores the result — approvers see the same flags the submitter saw. Each violation is either **blocking** (prevents submission until fixed) or a **warning** (informational, does not block). Blocking violations: an expense line with no amount, missing receipt, blocked category, mileage line with no distance, mileage or per-diem rate not configured, per-diem line with no location or days. A report with no lines, or with any line that has no amount (an expense line, or a mileage or per-diem line no rate covers), cannot be submitted even when policy enforcement is off. Warnings: expense older than the configured age, per-line or daily cap exceeded, possible duplicate, budget exceeded, mileage or per-diem rate mismatch with the configured rate, card-receipt vendor mismatch. ## How do conditional approval rules work, and what happens if none match? Enable **Conditional approval rules** in Settings first — without it, every report routes to the submitter's manager. With it enabled, the system walks your rules in priority order and uses the first one that matches. A rule can match on amount range, categories, cost centers, departments, locations, or submitter role. Each rule defines an approver chain of one or more steps, where each step is either the submitter's manager or a named user. If no rule matches, the submitter's manager is still the fallback approver. ## How do I hand off approvals when someone is out of the office? Open **Coverage** in the Mango Spend sidebar (it appears once **Conditional approval rules + delegations** or **Pre-approvals** is on in Settings) and add coverage: the person going out, the delegate who will cover, and a date range. While it is active, and only while **Conditional approval rules + delegations** is on, an expense report **submitted during the window** that would route to the absent approver goes to the delegate instead, and the rerouting is recorded in the report's audit trail with both names. With that switch off, expense reports are not rerouted — they keep going to the submitter's manager — and only pre-approval requests follow the coverage. Three more things coverage does not do: a report that was already waiting on the absent approver before coverage started stays with them (a Mango Spend admin can decide it); a report routed to the delegate stays with the delegate after coverage ends; and company-card receipts are never rerouted. Pre-approval requests follow the coverage as it stands on the day — to the delegate while it is active, back to the original approver when it ends. ## How do I reimburse employees — what is the batch process? 1. Go to **Pay → Employee Spend** and choose **New batch** — the approved reports waiting to be paid are listed for you to add. Until you export, **Remove** on the batch page sends a report back to the waiting list. 2. Choose an export format: Generic, ADP, Gusto, Paychex, or an accounting format (QuickBooks, Xero, NetSuite, Sage Intacct). 3. Choose **Export CSV & lock** — this locks the batch's report set and downloads the CSV. Exporting does not pay anyone: the reports stay Approved. Before you export, the batch page names anyone the chosen format can't identify (no employee ID for ADP or Paychex; neither an employee ID nor an email address for Sage Intacct; no email for Gusto or the Generic file). 4. Import the CSV into your payroll system and run the payout. 5. Come back and choose **Mark as paid** once payroll confirms the run. Exporting alone does not mark anyone paid — this step does, and it sends each employee a payment notice when **Notify employees on decisions / payouts** is on (unless they have switched off Mango Spend notifications). The Sage Intacct file's **Vendor ID** is each person's External Employee ID, or their OneMango Employee ID when no external one is set, or their email address when they have neither. Files exported before October 13, 2026 carried an internal OneMango number there instead, so if your Sage vendors were set up from an older file, update their Vendor IDs to match. For accounting, you can also export bill CSVs for QuickBooks Online, Xero, NetSuite, or Sage Intacct, or push approved data directly if you have a Merge.dev accounting integration connected. ## How do I reconcile corporate card transactions? Enable **Corporate cards** in Settings, then add a card account — either by importing a CSV statement or connecting a live Plaid bank feed. When transactions come in, the auto-matcher pairs each charge to an expense line using amount, date (within one day), and vendor name. Exact matches pair automatically; fuzzy matches require the vendor name to be at least 90% similar. Unmatched charges stay in **Card Charges** until an employee matches them manually. At month-end, an admin opens the reconciliation view, picks the card and month, and marks it reconciled — this is permanent and cannot be undone. When a charge is matched to a line on a claim that was already filed, the line is no longer reimbursed (the company card paid it, unless your cards are set to individually billed), the claim's Activity records the amount before and after, and the employee — plus the approver while the claim is still waiting — is told in the app. ## How does multi-currency work? Multi-currency is off by default. Turn it on in Settings and set your **default currency** (USD, EUR, GBP, CAD, or AUD). Employees can then submit lines in any currency. The FX rate is resolved from your business's rate table in this order: direct rate, auto-inverted rate (the reverse pair), or USD triangulation (converting through USD). Rates can be entered manually, pulled from the European Central Bank daily feed, or overridden per pair. Each line's home-currency amount is snapshotted at submit time and does not change afterward. --- ## When something looks wrong ## Why can't I submit my expense report — it says a receipt is missing? A receipt is required on any line whose amount is at or above the receipt threshold (default $25). Some categories — Meals & Entertainment, Airfare, Lodging, Ground Transportation, Office Supplies, Software / SaaS, and Conferences — also have **Always require a receipt** turned on by default. Attach a receipt to each flagged line and try again. If you want to lower or raise the threshold, an admin can change it in Settings. ## Why didn't my mileage line get priced? Mileage lines are priced from the mileage rate in effect on the trip date. If no rate covers that date, the line cannot be priced and submission is blocked. Ask a Mango Spend admin (or whoever manages spend rates) to add a rate on the **Mileage Rates** page with an effective-from date on or before the trip date. There is no built-in default rate — the admin must configure at least one. Once a rate that covers the date is saved, the waiting line is priced automatically — there is nothing to re-enter. ## An employee's report has been stuck in "Submitted" for days — what do I check? Three things to look at: (1) Is the assigned approver still active? If they left or were deactivated, the report has no one to act on it. (2) Is there an approval delegation in place that may have rerouted the report to someone who doesn't know they have it? Check the report's audit trail for a delegation entry. (3) The system sends approval reminders after 3 days — if the approver still hasn't acted, you may need to follow up directly. App admins can also decide the report themselves from **Approve → Employee Spend**. ## A card transaction shows "Unmatched" after we imported the statement — why? The auto-matcher pairs a charge only with an expense line on a report that is still a draft, has changes requested, is waiting for approval, or is approved but not yet in a payment batch, and only when: the amount matches exactly, the dates are within one day of each other, the cardholder on the card account is the employee who filed the line, and the vendor agrees (the same name, the line's vendor at the start of the card descriptor, a name at least 90% similar, or — for a line with no vendor — its description naming the merchant). If any of these is off — the expense isn't filed yet, the amount was split, or the vendor name is too different — the charge stays unmatched. The cardholder can match it manually under **Card Charges**, or an admin can match it from the same page. --- ## Licensing and limits ## Does Mango Spend require a licence? Yes. Mango Spend is disabled by default and requires a licence. An administrator enables it from Admin → Apps → All Apps, and it is opt-in per tenant. ## What are the limits I should know about? - **CSV import:** 500 rows maximum per file. The import creates one draft report per currency in the file. - **Receipt email:** 10 attachments per email, 15 MB per attachment. - **Duplicate lookback window:** 1–365 days (default 30). - **Default per-line caps:** Meals & Entertainment $75, Travel — Lodging $300 (editable per category on the **Categories** page). - **Report numbering:** Auto-assigned as ER-YYYY-NNNNN (year and five-digit sequence, unique per business). - **Batch numbering:** Auto-assigned as PB-YYYYMM-NNN. - **FX rate sources:** Manual, European Central Bank daily feed, or Override. - **Budget alert thresholds:** An in-app alert goes out at 80% and at 100% of a budget's limit — to the budget's owner when the budget is for one employee, otherwise to the Mango Spend app admins (the company admins when no app admin is named). Each alert fires once per budget per recipient. ## Can reports under a certain amount be approved automatically? No. Every submitted report goes to a person for a decision — the employee's manager by default. To send reports to different approvers by amount, category, cost center or role, turn on **Conditional approval rules + delegations** in Settings and add rules on the Approval Rules page. A report with no matching rule and no manager goes to your company admins and Mango Spend admins. --- ## More help - [Mango Spend Overview](/help/articles/mango_spend_app_overview) - Ask AI — the assistant answers Mango Spend questions from these articles. **Keywords:** faq, expense report, receipt, reimbursement, approval, mileage, per diem, corporate card, payment batch, policy, budget, delegation, mango-spend, mango_spend --- # Meal Compliance App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-18 How to set up and run Meal Compliance — meal break waiver management, behavior detection, break-law findings, and autonomous enforcement. # Meal Compliance ## 1. What it is Meal Compliance connects meal break behavior — from timesheets and attendance — with the legal documentation that supports it. The app monitors whether employees are actually taking or skipping meal breaks, manages signed waivers for those who skip, detects when behavior changes, and flags employees who are waiving meals without a valid waiver on file. - **Enablement:** Meal Compliance requires a license and is off by default. An administrator enables it from Admin → Apps → All Apps. - **What it is not:** Meal Compliance does not schedule breaks. Break rules for each state live under Admin → Compliance → Labor Law Rules, and whether they are observed or enforced is set under Admin → Work Policy Settings. This app manages the waiver documentation and compliance monitoring that sit on top of those rules. ## 2. Standing it up 1. **Enable the app.** Go to **Admin → Apps → All Apps**, find **Meal Compliance**, and enable it for your organization. 2. **Set up jurisdictions.** Meal break waiver requirements are per-jurisdiction (state, county, or city). Go to **Admin → Jurisdictions** and confirm your locations have active jurisdictions assigned. Without jurisdictions, the break compliance engine has no rules to evaluate and remains silently inert. 3. **Configure break rules.** The break compliance engine reads labor law rules of type "break" that resolve through your locations' jurisdictions. Confirm at least one active break rule exists — the Break Compliance tab in Meal Compliance shows which rules are in force and which locations they cover. 4. **Review default settings.** Go to **Meal Compliance → Settings** and adjust the behavior detection window, waiver expiry period, and whether e-signature is required. 5. **Grant access.** Any employee can see the **My Breaks** tab (their own waiver status and break history). Managers can create and manage waivers for their direct reports. HR admins, app admins, and organization admins have full access to all employees' waivers, compliance gap reports, break compliance findings, and CSV exports. Designate app admins under **Admin → Apps → All Apps → Meal Compliance → App Admins** if you want non-admin users to have full access. 6. **Confirm it works.** The Dashboard shows four tiles: Active Waivers, Pending Signatures, Behavior Alerts, and Invalidated. A coverage percentage appears once the system detects employees waiving meals. The Break Compliance tab shows any break-law findings the engine has recorded. **Silent-failure pairing:** jurisdictions and break rules must both exist. A location with no jurisdiction resolves no break rule, so the engine writes no findings and the Break Compliance tab shows an empty report — which reads as "no violations" when it actually means "no rules". ## 3. How it fits together **Waivers** are the core records. A waiver is a signed document allowing one employee to voluntarily skip meal breaks. Each waiver belongs to one employee, optionally to a location and a jurisdiction, and moves through a lifecycle: **Draft → Pending Signature → Active → Expired** or **Invalidated**. A waiver that reaches its expiry date is swept to Expired automatically every four hours by a background job. Only managers, HR admins, and app admins can create waivers; employees cannot create their own, but an employee can withdraw their own waiver from **My Breaks** at any time. Waivers cannot be edited after creation — to correct a mistake, discard the draft (or invalidate a waiver that was already sent or activated) and create a new one. **Per-period elections** apply in jurisdictions that define more than one meal period (for example, a 1st and 2nd meal period). Each period is waived independently — an employee might waive the 2nd meal period while taking the 1st. When only one meal period is defined, the waiver form shows a single **Behavior State** selector (Waiving or Taking) instead of per-period radios. Elections record only what the employee chose; whether a waiver applies on a given day depends on the jurisdiction's rules for that period. Example: an employee at a California location works varying shifts. Their waiver elects to waive the 1st meal period. On a 5.5-hour day, that election applies and the system expects them to skip the meal break. On a 7-hour day, the law does not allow the 1st period to be waived, so the system expects them to take it — the waiver is still active but does not apply that day. **Behavior detection** runs in the background every four hours **while autonomous actions are turned on** (Settings → Autonomous actions). With autonomous actions off, no break pattern is analyzed and no new behavior is recorded, so the Compliance Gaps report, the dashboard coverage figure and compliance gap alerts dwindle as the last 30 days of recorded behavior age out; Ask AI can still analyze one employee's pattern on request. When it runs, the system reads each employee's completed and skipped break records of the **Meal Break** break type from Time & Attendance over a configurable detection window (default 14 days). A meal break recorded under another break type is not read, and one that was planned but never started counts neither as taken nor as skipped. Each day is scored independently: - All meal breaks completed, none skipped → that day counts as **taken**. - All meal breaks skipped, none completed → that day counts as **waived**. - Some completed, some skipped → that day counts as **mixed** (neither side). If an employee's waived days are 70% or more of their scored days, their pattern is **Waiving**. If their taken days are 70% or more, the pattern is **Taking**. Below 70% on both sides — including days scored mixed — the pattern is **Inconsistent**. A minimum number of days with break data must exist in the window before a pattern is determined (default 3 days); below that threshold the result is also Inconsistent, and too little data is never treated as a change in behavior. When the detected pattern differs from the behavior recorded on an employee's active waiver, the system logs a **behavior change alert**. When the detection's confidence meets **Minimum confidence** (default 95%), the day's action cap has not been reached and AI is not paused, it also proposes an action in the **AI Console**, where an admin approves or rejects it — behavior changes always wait for approval. Otherwise the change appears only under Behavior Alerts on the dashboard and no card is proposed. If **Auto-Invalidate on Behavior Change** is on (it is off by default), approving the action ends the waiver when the new pattern contradicts what the waiver records — for example, an employee on a waiving waiver who now takes their breaks — and the employee is told their waiver was ended. **Compliance gaps** are employees whose break records show them waiving meals in the last 30 days but who have no active waiver on file. The Compliance Gaps report (under **Waivers → Gaps**) lists these employees and can be filtered by location. The dashboard's coverage percentage measures the same thing: of employees detected as waiving, what share has an active waiver. **Break compliance findings** are recorded by a separate engine that evaluates each employee's actual breaks against the jurisdiction's legal requirements. Six finding types are tracked: - **Missing** — no meal break was recorded. - **Started too early** or **Started too late** — the break fell outside the allowed window. - **Too short** — the break was shorter than the legal minimum. - **2nd meal missing** — a required second meal break was not taken. - **Unbroken stretch** — the employee worked longer than the allowed unbroken interval. Each finding is classified by period kind (**Meal**, **Rest**, or **Unbroken work**) and carries a severity of **Violation** or **Warning**. The engine has three settings, chosen per organization under Admin → Work Policy Settings — **Off** (shifts are not checked), **Observe** (records a shift's findings when it is clocked out; prompts nobody and adjusts no pay) and **Enforce** (asks employees about rest breaks at clock-out — or at their next clock-in on the web or at the kiosk, for up to 14 days, when a manager, the shared kiosk or the automatic clock-out closed the shift — blocks non-compliant assignments, and writes missed-break pay to the timesheet as each state's break rule sets). The default is **Observe**. Review the findings that accumulate in Observe mode before switching to Enforce. **E-signature integration** is optional. When **Offer e-signature collection** is on in settings and the E-Signature app is separately enabled for your organization, a draft waiver can be sent to the employee for formal e-signature. A manager can also mark a draft waiver as active using the **Activate** action, whether or not e-signature is on — this records that a signature was collected outside the app. **Activate** is also offered for a waiver left in **Pending signature** whose signature request never went out, was voided, or expired unsigned. Without one of these two paths, a waiver has no way to become active. **Notifications.** The app sends four kinds of notifications (in-app bell and email): - **Waiver expiring** — sent to the employee, and to their manager (or an app admin when they have none), a configurable number of days before their waiver's expiry date (default 14 days). Not sent once a newer signed waiver already continues their coverage. - **Waiver invalidated** — sent to the employee when their waiver is ended, whether by a manager, an admin, or an approved behavior-change action. A draft discarded before it was ever sent is not announced. - **Compliance gap alert** — sent to the employee's manager (or to an app admin when there is no manager, and to the employee only when there is neither) when they are waiving meals without a valid waiver. Gap alerts depend on behavior detection, which runs only while autonomous actions are on; with it off they dwindle as the last 30 days of recorded behavior age out. - **Behavior change detected** — sent to the employee after an admin approves a behavior-change action in the **AI Console**. Not sent when that approval ends their waiver; they get the waiver-ended notice instead. Proactive reminders are checked every four hours for every organization with Meal Compliance enabled, unless **Send proactive reminders** is turned off in Settings or Automation Hub's **Pause All** is in effect. Expiry reminders go out whether or not autonomous actions are on. Compliance-gap alerts are checked on the same pass, but they work from detected break patterns, so they have something new to report only while autonomous actions are on. At most one reminder per person per waiver is sent each week. ## 4. Running it ### Creating a waiver 1. Go to **Meal Compliance → Waivers → New Waiver**. 2. Select the employee, optionally a location and jurisdiction, and choose the behavior state or per-period elections. 3. Set the validity period (Valid From / Valid Until). If Valid Until is left blank, the waiver does not expire by date. 4. Submit. The waiver is saved as a **Draft**. 5. Either click **Send for Signature** (if e-signature is enabled and the E-Signature app is active) or click **Activate** to put the waiver on file immediately. ### Invalidating a waiver 1. Go to **Meal Compliance → Waivers** and open the waiver. 2. Click **Invalidate**. Optionally provide a reason. 3. The employee is notified that their waiver is no longer valid. Active and Pending Signature waivers can be invalidated. A Draft is **discarded** instead — the employee never saw it, so they are not told. Already-expired waivers cannot be changed. ### Reviewing compliance gaps 1. Go to **Meal Compliance → Waivers → Gaps**. 2. The page lists employees whose break behavior shows them waiving meals without an active waiver. Filter by location if needed. 3. Create a waiver for any listed employee directly from the gap report. This report is available to HR admins, app admins, and organization admins only. ### Reading break compliance findings 1. Go to **Meal Compliance → Break Compliance**. 2. The report shows findings grouped by counts: total, open, by period kind, and affected employees. Filter by finding type, period kind, status, employee, or date range. 3. Resolve individual findings by marking them and adding an optional note. Before switching the engine from Observe to Enforce, review the findings backlog here — this is the only place accumulated observations are visible. ### Exporting waivers From the Dashboard or the Waivers list, click **Export** to download a CSV of all waivers (or filtered by status). The export caps at 10,000 records; if your data exceeds that, filter by status and export in batches. The file labels the truncation when it applies. ### Using the AI Console Open the **AI Console** tab. The console provides an AI mode dial with three positions: **Off — manual only**, **Approve — AI acts, human confirms**, and **Auto — AI acts when confident**. In Approve mode, the system proposes actions and waits for an admin to approve each one. Behavior-change actions always wait for approval, in every mode. The app always opens on the **Dashboard**. ## 5. Settings All settings are at **Meal Compliance → Settings**. | Setting | Card | Default | What it changes | |---|---|---|---| | Detection window (days) | Behavior detection | 14 | How many days of break records are analyzed to determine an employee's meal break pattern. | | Minimum days for reliable detection | Behavior detection | 3 | The number of days with break data required in the window before the system assigns a behavior pattern. Below this, the pattern is Inconsistent. | | Default waiver expiry (days) | Waivers and reminders | 365 | Pre-fills **Valid Until** on the New Waiver form: this many days after the waiver starts (today, or the day after the current waiver ends when you start the next one from a waiver about to expire). Existing waivers keep their dates. | | Expiry reminder (days before) | Waivers and reminders | 14 | How many days before a waiver's expiry date the system sends a reminder to the employee and their manager. | | Send proactive reminders | Waivers and reminders | On | Turns the four-hourly expiry reminders and compliance gap alerts on or off for your organization (gap alerts also need autonomous actions on, which detect the break patterns they report). | | Enable Meal Compliance AI Agent | AI agent | On | Lets people ask Ask AI about waivers, gaps and break patterns, and lets authorized users create, send, activate or end waivers from chat (each change asks for confirmation). | | Offer e-signature collection | Waivers and reminders | On | Shows the **Send for Signature** action on waivers, so employees sign in the E-Signature app. Requires the E-Signature app to be separately enabled. It does not stop a manager recording a signature collected on paper: **Activate** stays available either way. | | Enable autonomous actions | Autonomous actions | Off | Allows the system to take automated compliance actions (behavior analysis, waiver invalidation, gap notifications) without manual triggers. | | Auto-invalidate on behavior change | Autonomous actions | Off | When an admin approves a behavior-change action in the AI Console, the employee's waiver is ended if their new pattern contradicts it, and they are notified. Only takes effect while autonomous actions are enabled. | | Minimum confidence (%) | Autonomous actions | 95 | The confidence threshold for autonomous actions to execute. | | Max actions per day | Autonomous actions | 50 | Caps the number of autonomous actions the system can take per day. | | Trust level | Autonomous actions | **Probation** | Controls which types of autonomous actions are permitted. The three levels are **Probation**, **Standard**, and **Trusted**. | The AI Console's AI mode dial writes the same autonomous-actions fields. Its three positions — Off, Approve, and Auto — map to the Enable autonomous actions toggle and the Trust level. Moving the dial to Auto sets Trust level to Trusted. ## 6. More help - **Meal Compliance FAQ** — specific setup and operating questions. - **Ask AI** — the assistant answers questions about Meal Compliance from these articles and can check waiver status, list compliance gaps, analyze behavior patterns, and list break-law findings. **Keywords:** meal compliance, meal break waiver, meal waiver, break compliance, behavior detection, meal period election, waiver expiry, compliance gap, break law violation, e-signature waiver, meal-compliance, meal_compliance --- # Meal Compliance FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-14 Answers to common setup and operating questions about Meal Compliance — for the admin running it. # Meal Compliance FAQ Answers to common setup and operating questions about Meal Compliance. For what the app is and how to set it up from scratch, see the [Meal Compliance Overview](/help/articles/meal_compliance_app_overview). --- ## Setup ## Do I need Time & Attendance running before Meal Compliance works? Yes. Meal Compliance reads break records from Time & Attendance to detect behavior patterns, and it reads only breaks whose break type is named exactly **Meal Break** — a meal break recorded under any other break type is not counted. A break counts as taken once it is completed and as skipped only when its record is marked skipped; a meal break that is planned but never started is not counted either way. Detection also runs only while **autonomous actions** are on in Meal Compliance settings (they are off by default) — with them off, no break pattern is detected, whatever Time & Attendance records. ## Does the E-Signature app need to be enabled for waivers to work? No. When **Offer e-signature collection** is on in your Meal Compliance settings, sending a waiver for signature generates a PDF and routes it through the E-Signature app. If you have not enabled the E-Signature app, the "Send for Signature" action tells you which app to enable. You can still create waivers and use the **Activate** action to put them in force after collecting a signature outside the platform. --- ## Permissions and access ## Who can create and invalidate waivers? Administrators, HR admins, and Meal Compliance app admins have full access to all employees' waivers. A manager can create or invalidate a waiver only for their own direct reports. Employees cannot create waivers, but they can withdraw their own waiver — or decline one sent to them — from **My Breaks** on desktop or phone. ## Who can see the Compliance Gaps report and CSV export? Only administrators, HR admins, and Meal Compliance app admins. Managers do not have access to compliance reports. These reports name individual employees and their break behavior across the organization. ## What can employees see in the app? Every employee sees a **My Breaks** tab showing their own waiver status, recent break-behavior history, and a signing link for any pending waiver. They cannot see other employees' waivers, break behavior, or compliance data. The My Breaks page is also available on mobile. --- ## Day-to-day ## How does behavior detection decide whether someone is waiving or taking meal breaks? While autonomous actions are on in Meal Compliance settings, the system reads completed and skipped breaks of the **Meal Break** type from Time & Attendance over the detection window (default 14 days, configurable 7–90); a meal break that was planned but never started is not counted. Each day is scored: taken if all meal breaks were completed, waived if all were skipped, or mixed if some were completed and others skipped. When 70% or more of days are waived, the pattern is classified as **Waiving**. When 70% or more are taken, it is **Taking**. Below that threshold, or when there are fewer days of data than the **Minimum days for reliable detection** setting (default 3, configurable 1–14), the pattern is **Inconsistent**. ## What happens when a waiver is sent for e-signature? The system generates a PDF with voluntary-consent language, the employee's name, jurisdiction, location, validity dates, and any per-meal-period elections. It creates a signature request through the E-Signature app and emails a signing link to the employee. The waiver moves to **Pending signature** and activates automatically when the employee signs. An employee with no email address on file can't receive a signing link, so **Send for Signature** isn't offered for them — collect the signature on paper and use **Activate**. While a link is out, the waiver page shows when it was sent and when it expires, and **Resend signing link** sends the employee a fresh copy. ## Can I edit a waiver after creating it? No. Waivers cannot be edited. If the details are wrong, discard the draft (or invalidate a waiver that was already sent or put in force) and create a new one. This is by design — a signed legal document should not change after the fact. ## What happens when a waiver expires? A background sweep runs every 4 hours and marks date-expired waivers as **Expired**. Before that, a renewal reminder goes to the employee and to their manager (default 14 days before expiry, configurable 1–60 days), unless a newer signed waiver already continues their coverage. Once expired, the waiver stops counting as active. If the employee is still skipping meals, they reappear in the Compliance Gaps report — as long as behavior detection is running (it runs only while autonomous actions are on). ## What does "Auto-Invalidate on Behavior Change" do? It is off by default, and only takes effect while autonomous actions are on. A detected behavior change is proposed in the **AI Console** for an admin to approve when the detection's confidence meets **Minimum confidence** (default 95%), the day's action cap has not been reached and AI is not paused; otherwise the change is still recorded under Behavior Alerts on the dashboard, but no card appears. With this setting on, approving it ends the employee's waiver when their pattern has shifted to the opposite of what the waiver states — for example, a waiver saying they skip meals while detection shows they now consistently take them — and the employee is told their waiver was ended. Too little break data is never treated as a change. With this setting off, the behavior change is logged and can trigger an alert, but the waiver stays in force. --- ## When something looks wrong ## Why isn't behavior detection finding any patterns? First, check that **Enable autonomous actions** is on in Meal Compliance settings: behavior detection runs only while it is. Detection also needs meal-break clock punches in Time & Attendance. If employees are not recording meal breaks — or if the detection window is shorter than the **Minimum days for reliable detection** setting — no patterns are classified. Check that Time & Attendance is active and that employees record their meal breaks under the **Meal Break** break type — breaks of any other type are not read. ## I turned on "Offer e-signature collection" but Send for Signature says the E-Signature app isn't enabled The **Offer e-signature collection** setting in Meal Compliance is separate from having the E-Signature app enabled for your organization. Both must be true. Ask an administrator to enable the E-Signature app in Admin → Apps → All Apps. ## An employee says their waiver was invalidated but nobody did it manually A waiver can end without a manager clicking Invalidate in three ways: an admin approved a behavior-change action in the **AI Console** while **Auto-Invalidate on Behavior Change** was on, a form-version retirement (when an administrator re-collects waivers on a newer form), or the employee withdrew or declined it themselves. The waiver's detail page states which one it was. ## My dashboard shows 0 behavior alerts but the Behavior Alerts card lists employees The dashboard tile counts behavior changes from the last 7 days. The card also shows only changes from the last 7 days. If the numbers disagree, a sweep may have just run. Refresh the page — the count and the list are drawn from the same 7-day window. --- ## Autonomous mode ## How does autonomous mode work? Autonomous mode is off by default. When enabled, an AI loop runs every 4 hours to analyze each employee's break pattern; that analysis is what finds compliance gaps and behavior changes. Behavior-change actions (such as invalidating a waiver) are proposed in the AI Console and require admin approval before they execute. Expiry reminders and gap alerts are sent by the separate reminder pass described below, not queued for approval. You control how much it does with three settings: **Minimum confidence** (80–100%, default 95), **Max actions per day** (1–500, default 50), and **Trust level** (**Probation**, **Standard**, or **Trusted**; default **Probation**). ## Do I need autonomous mode turned on to get expiry and gap reminders? Not for expiry reminders: they are sent every 4 hours for every organization with Meal Compliance enabled, whether or not autonomous mode is on, unless **Send proactive reminders** is off or Automation Hub's **Pause All** is in effect. Compliance-gap alerts are different — they depend on behavior detection, which runs only while autonomous mode is on. With it off, no new behavior is recorded, so gaps and gap alerts dwindle as the last 30 days of recorded behavior age out. --- ## Licensing and limits ## Does Meal Compliance require a licence? Yes. It is disabled by default. An administrator enables it for your organization from Admin → Apps → All Apps. ## What are the configurable ranges and limits? | Setting | Range | Default | |---|---|---| | Detection window | 7–90 days | 14 | | Minimum days for reliable detection | 1–14 | 3 | | Default waiver expiry | 30–730 days | 365 | | Expiry reminder lead time | 1–60 days | 14 | | Minimum confidence (autonomous) | 80–100% | 95 | | Max autonomous actions per day | 1–500 | 50 | | Waiver notes | up to 2,000 characters | — | | CSV export | up to 10,000 waivers per download | — | | Autonomous run cadence | every 4 hours | — | | Break compliance enforcement mode | Off, Observe or Enforce | Observe | --- ## More help - [Meal Compliance Overview](/help/articles/meal_compliance_app_overview) - Ask AI — the assistant answers Meal Compliance questions from these articles. **Keywords:** faq, meal waiver, meal break, behavior detection, compliance gap, e-signature, autonomous mode, break compliance, invalidation, meal-compliance, meal_compliance --- # Messages App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-14 How to set up and govern Messages — private one-to-one and group mail, announced in each recipient's Notifications and read in Messages, managed independently of Chat. # Messages ## 1. What it is Messages lets employees send private one-to-one or small-group messages. Each new message is announced in the recipient's Notifications, alongside tasks and approvals, and read in Messages. It is asynchronous — more like email than Chat — and governed on its own track so an admin can control retention, who may start a conversation, and whether attachments are allowed without affecting Chat channels at all. - **Enablement:** Messages requires a license and is disabled by default. An admin turns it on from **Admin → General Settings → Messages** or from **Admin → Apps → All Apps**. - **What it is not:** Messages is not Chat. Chat provides real-time one-to-one chats, group rooms and channels with presence indicators and typing notifications. Messages provides private, asynchronous conversations, announced in Notifications. Turning Messages off does not stop Chat's one-to-one chats — they have their own switch in Chat's settings (Private chat). The two apps are licensed, configured, and retained independently. ## 2. Standing it up 1. Go to **Admin → General Settings → Messages** and turn Messages on. Alternatively, enable the app from **Admin → Apps → All Apps → Messages**. 2. Open **Apps → Messages → Settings** to configure its six settings: group messages, attachments, Ask AI in Messages, who can start a message, who can view messaging analytics, and the retention window. All six have sensible defaults (see §5), so the app works immediately without changing them. 3. No role assignment or per-user provisioning is needed. Every member in the organization can send and receive messages once the app is enabled. To restrict who may open new conversations, change **Who can start a message** to **Managers and above**, **App admins and business admins only**, or **Specific groups only**. 4. Confirm it works: open the **Messages** client from the profile menu at the top right (**Messages**). Start a one-to-one thread with another user, send a message, and verify it appears in that user's inbox. **What employees see:** the Messages client — a conversation list with a reading pane — opened from the profile menu at the top right (**Messages**), from the **Messages** tab in Communications when your organization has it, or by searching "messages". On a phone, it is the **Messages** row at the top of Notifications. The **New Message** composer is available there, and from the user directory, org chart, and profile pages. **What employees do not see:** the Messages app tile and its dashboard. They are visible only to business admins, designated Messages app admins, and anyone named under **Who can view messaging analytics** (who see the dashboard but not the settings). Employees who navigate directly to **Apps → Messages** are redirected to the Messages client. **Silent-until-configured pairing:** if you enable Messages but turn **Group messages** off, employees can only start one-to-one threads. They will see no error — the group option simply does not appear in the composer. This is by design, but can surprise admins who expect group messaging to work out of the box (it does: the default is On). Similarly, turning **Attachments in messages** off hides the attach and voice-note controls. Files sent through a direct API call while the toggle is off are rejected with an explicit error, not silently stripped. ## 3. How it fits together **Threads** — every conversation is a thread. A thread is either **one-to-one** (exactly two people) or a **group** (three to ten people). One-to-one threads are idempotent: starting a conversation with someone you have already messaged reopens the existing thread instead of creating a duplicate. Group threads are always new. Example: Priya messages Raj from the user directory. A one-to-one thread is created. Later she messages Raj again from a profile page — the same thread reopens with the full history intact. She then starts a group thread with Raj and two others; that is a separate conversation with its own history. **Messages vs. Notifications** — Messages has two related surfaces that are easy to confuse. The **Messages client** is where employees read and write conversations. It is the list-plus-reading-pane opened from the profile menu → **Messages**. **Notifications** (the bell, and the Inbox) lists the notices *about* messages (e.g. "New mail from Raj"), filed under the **Messages** category; opening one takes you to the conversation. They serve different purposes: one is the conversation, the other is the alert about it. **Composing** — employees start a new message from the **New Message** button in the Messages client, from the user directory, from the org chart, or from a profile. The composer opens as a drawer, lets the sender pick one or more recipients, add a subject line and write the first message. Files can be attached in the composer and go with the first message (up to 50 MB each); voice notes are recorded from the reply box once the conversation opens. Reply and Forward work the same way: they open the composer with the subject and a quoted body pre-filled. Forward quotes the text only — attachments and voice notes are not carried. **@Mentions** — inside a message body, employees can type **@** to mention a colleague who is part of the conversation. The mentioned person receives a separate notification so the mention stands out from the regular "new message" alert. **Reactions** — each message offers your company's reactions — the same set as the feed and every other app, chosen by your admin in Communications settings. Tapping a reaction toggles it; each reaction shows a count and who reacted. **Voice notes** — when attachments are enabled, the reply box in a conversation on a computer includes a voice recorder. The recorded audio is transcribed automatically while your organization has AI credits available, so the recipient can read it as text instead of playing it back. **Drafts** — the composer auto-saves a draft as the user types. Reopening the same thread restores the unsent draft. The draft is cleared as soon as the message is sent. **Governance vs. the client** — the Messages app page at **Apps → Messages** is the surface for governance settings and usage analytics. Only admins, Messages app admins and the people named under **Who can view messaging analytics** see it (the last group sees the dashboard only). The admin-facing dashboard shows total messages, active conversations, participants, and a 30-day trend chart. **Read state** — opening a conversation marks it read automatically. Employees can also mark a conversation unread from a specific message so it reappears as unread in their list. Messages has no read receipts: a sender is not shown whether the other person has read it. **Notifications and push** — when someone sends a message, every other participant receives an in-app notification (throttled to one unread notification per conversation to avoid inbox clutter). Each message also triggers a mobile push notification so closed apps are woken. Mentioned users get a separate mention notification instead of the ordinary one. Mobile push honors the registered **Messages** notification preference, so an employee who turns push off for that category stops receiving it. Muting a single conversation (from the conversation's own menu) stops both its notifications and its pushes for that employee only. **Relationship to Chat** — Chat and Messages share no configuration. An admin can disable Messages while Chat stays on, or vice versa. Retention windows, attachment policies, and access rules are set independently for each app. **Search** — Messages search is keyword-based, not semantic. When an employee searches in the Messages client, results match conversations by participant name, participant email, group-thread title, or message body text, and are capped at 50 conversations. ## 4. Running it ### Reviewing usage Go to **Apps → Messages**. The dashboard shows six analytics cards: - **Messages sent** — all time, excluding deleted. - **Last 30 days** — messages in the most recent 30-day window. - **Conversations** — total one-to-one and group threads. - **Active (30d)** — threads with at least one message in the last 30 days. - **Participants** — unique people who are part of any conversation. - **Reactions** — total emoji reactions on messages. Below the cards, a 30-day activity trend chart shows daily message volume. ### Changing who can start conversations Go to **Apps → Messages → Settings**. Under **Who can start a message**, choose **Everyone with access to Messages** (the default), **Managers and above**, **App admins and business admins only**, or **Specific groups only**. This restricts who may open a new thread; replying to an existing conversation is always allowed regardless of this setting. ### Setting a retention window Under **Message retention (days)**, enter the number of days after which messages are automatically purged. The default is **0**, which means messages are kept forever. Retention is governed separately from Chat's channel retention. Purging runs in two automatic stages, and the second one cannot be undone. Each night, the retention job soft-deletes every message older than the window: it disappears from the conversation, from unread counts, from search and from **My Trash** — a message past the window cannot be restored, because the next night's sweep would only remove it again. A conversation whose every message has been removed says so ("No messages in the last 30 days"). Thirty days later, the platform's nightly purge destroys that message row permanently, taking its voice notes and their transcripts with it. A message's effective lifetime is therefore the retention window **plus 30 days** — a 90-day window means a message is unrecoverable 120 days after it was sent. Files attached to a message go with it: they are moved to Drive's trash the same night and destroyed 30 days later. There is no on-demand purge and no legal hold yet, so this schedule is the only way messages leave the system. ### Archiving and muting conversations Employees can archive a conversation from its action menu. Archiving is per-person — it hides the thread from that employee's list only. The conversation reappears automatically for everyone if someone sends a new message. Muting a conversation stops its notifications and pushes for that employee. It does not change unread counts: new messages in a muted conversation still show as unread in the list. The conversation stays visible but stops alerting until the employee unmutes it. ### Managing group threads Participants can rename a group thread (up to 120 characters), add people (up to the 10-person cap), or leave the thread. One-to-one threads cannot be renamed or left — archive is the "hide" affordance there. ### Editing and deleting messages Employees can edit or delete their own messages. Edited messages show an "edited" indicator. Deleting is a soft delete: the message disappears from the conversation for everyone and the rest of the thread is untouched, but the author can restore it from **My Trash** for 30 days — or, when a retention window is set, until the message is older than the window, whichever comes first. The delete confirmation says how many days that is. After those 30 days the nightly platform purge destroys it permanently — the same second stage a retention-expired message goes through (see *Setting a retention window* above). ### Mobile access Messages has a dedicated mobile surface. Phone-class browsers are automatically redirected there. The mobile view provides the full conversation list, message reading, composing, replying, and forwarding — all with the same governance rules enforced server-side. Tablet-class browsers stay on the desktop surface. ### Loading sample data During setup or evaluation, go to **Apps → Messages → Settings** and scroll to the **Sample Data** card. Use **Load sample data** to generate realistic sample conversations. Sample records are tagged and can be removed with **Remove sample data** without affecting real conversations. ## 5. Settings All settings are at **Apps → Messages → Settings**. | Setting | Default | What it changes | |---|---|---| | **Group messages** | On | Allows group threads (up to 10 people). When off, only one-to-one threads can be created. | | **Attachments in messages** | On | Allows files and voice notes in messages. When off, the attach and voice-note controls are hidden and the server rejects uploads. | | **Ask AI in Messages** | On | Lets people ask Ask AI about their own conversations, mark them read, archive or mute them, and send a message as themselves after confirming. | | **Who can start a message** | **Everyone with access to Messages** | Controls who may open a new conversation. The other choices are **Managers and above**, **App admins and business admins only**, and **Specific groups only**. Replying to existing threads is always allowed. | | **Who can view messaging analytics** | **App admins and business admins only** | Who may open the Messages dashboard (aggregate counts and a 30-day chart, no message contents). The other choices are **Managers and above** and **Specific groups only**. It never grants the settings page. | | **Message retention (days)** | 0 (keep forever) | Auto-purges messages older than this many days, in two stages: a daily job soft-deletes them (they are not offered back in Trash), then the nightly platform purge destroys the message and its voice notes permanently. Effective lifetime is the window **plus 30 days**. Attached files go with them. | A **Reset to defaults** button restores all six settings to the values above. Each setting has a real runtime effect: the group-messages toggle is checked when creating a thread, the attachments toggle gates the upload controls and the server-side accept path, the initiation rule is enforced at thread creation, and the retention window drives a daily automated purge. ### Where else the enabled/disabled toggle lives The master on/off for Messages also appears at **Admin → General Settings → Messages**. Both surfaces write to the same underlying state, so toggling one is immediately reflected in the other. The governance settings (group messages, attachments, Ask AI, who can start, who can view analytics, retention) are only on the **Apps → Messages → Settings** page. ### Real-time delivery Messages are delivered in real time via WebSocket broadcast. When someone sends a message, every participant's open conversation updates immediately without a page refresh. If the recipient does not have the conversation open, the new-message notification and the unread badge in their inbox update in real time as well. ## 6. More help - **Messages FAQ** — specific setup and operating questions. - **Chat App Overview** — the companion real-time messaging app with channels and rooms. - Ask AI — the assistant answers questions about Messages from these articles, and from your own mail: it can list what is unread, open or search the conversations you are in (never anyone else's), mark a conversation read, archive it or mute it (for you only, as the buttons in your Messages list do), say what Messages allows in your organization, and send a message or a reply as you after you confirm it. An admin can switch this off under Messages → Settings → Ask AI. **Keywords:** messages, direct messages, private messages, group messages, DM, internal mail, message retention, who can start a message --- # Messages FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Messages — for the admin running it. # Messages FAQ Answers to common setup and operating questions about Messages. For what the app is and how to set it up from scratch, see the [Messages Overview](/help/articles/messages_app_overview). --- ## Setup ## Do I need to configure anything before employees can message each other? No. Once you enable Messages from Admin → Apps → All Apps, its settings start on defaults that let everyone use it: group messages on, attachments on, Ask AI on, everyone with access can start a message, analytics visible to admins only, and retention set to keep forever. Employees can send messages immediately. ## Who can access the Messages dashboard and settings? The Messages app tile opens an admin-only dashboard with usage analytics and governance controls. Only business admins and users with the Messages app-admin role can reach the settings page. The dashboard is also open to anyone named under **Who can view messaging analytics**. Everyone else is sent to their Messages client. --- ## Permissions and access ## I narrowed "Who can start a message" — can everyone else still reply? Yes. The restriction applies only to starting a new conversation. Replying to a thread you are already part of is always allowed, regardless of this setting. ## Why can't an employee see the "Message" button on someone's profile? The "Message" button on the user directory, org chart, and profile panel is hidden when either of two conditions is true: the Messages app is disabled for the business, or the "Who can start a message" setting does not include the viewer (for example it is **Managers and above** and the viewer is not a manager, or **Specific groups only** and the viewer is in none of those groups). --- ## Day-to-day ## Where do employees actually read and send messages? Employees use the Messages client, opened from the profile menu at the top right (**Messages**), or the **Messages** tab in Communications when your organization has it. They can also start a new message from the user directory, the org chart, a profile side panel, or a performance self-assessment. On a phone, Messages is the row at the top of Notifications. The Messages app tile in the sidebar is an admin dashboard, not a mailbox. ## Can employees message a group, and what's the size limit? Yes, if the **Group messages** setting is on (the default). A group thread supports up to 10 participants. The creator can name the group (up to 120 characters), add people later (up to the 10-person cap), and leave when done. One-to-one threads cannot be renamed or left — archive is the way to hide those. ## What can employees put in a message? Rich text with @mentions of other participants, file attachments, and voice notes (recorded on a computer) that are transcribed automatically while your organization has AI credits available. They can also react with your company's reaction set (the same one used in every app), and edit or delete their own messages after sending. ## What happens when someone sends a message? The message is delivered in real time to every participant. Each recipient gets an in-app notification (throttled to one unread notification per thread so a burst of messages doesn't stack rows). A mobile push notification fires for every message. Muted threads skip the notification and the push; their new messages still count as unread in the list. Message text is never included in push notifications or on the lock screen. ## Will a new message in an archived conversation bring it back? Yes. Archiving is per-participant — it hides the conversation from your list. When anyone in the thread sends a new message, the conversation resurfaces for all participants who had archived it. ## I can't find a conversation — can I search for it? Yes. The search in the Messages client matches by participant name, email, or message body text. Results are capped at 50 threads. Search is keyword-based (not semantic). --- ## When something looks wrong ## My employee says they're getting too many message notifications — what controls are available? Each employee can mute a conversation from the thread menu. Muting stops that conversation's in-app notifications and pushes until it is unmuted (new messages still show as unread in the list). Separately, employees can manage their notification preferences under the **Messages** category (Chat has its own, separate categories), which controls in-app, email, and push channels (all default to on). ## An employee says their draft disappeared after they sent a message Drafts are saved automatically per thread. When a message is sent successfully, its draft is cleared on the server immediately so the composer does not still show the text that was just posted. If the send fails, the draft is preserved. A draft is per-thread and per-user — switching between conversations does not lose unsent text. ## A group thread shows the wrong name — how do I fix it? Only group conversations can be renamed (up to 120 characters). One-to-one threads always display the other person's name and cannot be renamed. To clear a custom group name back to the default participant list, rename it with an empty value. ## Why does the thread only show the most recent messages? The Messages client loads the last 50 messages when you open a conversation. A "Load earlier messages" link appears at the top if there are older messages. Each page loads 50 more. --- ## Licensing and limits ## Does Messages require a separate licence? Messages requires a licence to enable, but it is included with OneMango at no additional cost as a platform-included capability. It is not sold as a standalone add-on and is not metered per use. An admin enables it from Admin → Apps → All Apps. ## Are there limits I should know about? - **Group size:** 10 participants per thread. - **Group name length:** 120 characters. - **Messages loaded per view:** 50 at a time, with pagination for older messages. - **Search results:** capped at 50 threads per query. - **Reaction emoji:** your company's reaction set — the same in every app, chosen by your admin in Communications settings. - **Retention:** configurable in whole days; 0 means keep forever. Deleting is permanent and happens in two automatic stages. The daily retention job soft-deletes messages past the window — they drop out of every conversation, unread count, and search result that night, and from Trash too: a message past the window cannot be restored, because the next night's sweep would only remove it again. Thirty days on, the nightly platform purge destroys the message and its voice notes for good. A message's effective lifetime is therefore the retention window **plus 30 days**, and nothing brings it back after that. Files a message carried go with it — to Drive's trash the same night, then destroyed 30 days later. There is no on-demand purge and no legal hold yet. --- ## More help - [Messages Overview](/help/articles/messages_app_overview) - Ask AI — the assistant answers Messages questions from these articles, and from your own mail: it can list what is unread, open or search the conversations you are in (never anyone else's), mark a conversation read, archive it or mute it (for you only, as the buttons in your Messages list do), say what Messages allows in your organization, and send a message or a reply as you after you confirm it. An admin can switch this off under Messages → Settings → Ask AI. **Keywords:** faq, messages, direct messages, private messaging, inbox, group messages, retention, voice notes, who can start a message, mute conversation, archive conversation --- # Microsoft Teams — Notifications, Approvals, Must-Reads and /mango Commands **Category:** System-features **Section:** Advanced Features **Updated:** 2026-10-16 How to connect OneMango to Microsoft Teams, make the MangoApps Workforce app available to your people, send must-reads to them as Teams messages, and what they can do with the app in Teams. # Microsoft Teams ## 1. What it is Connecting Microsoft Teams lets OneMango meet people where they already chat. Once someone adds the **MangoApps Workforce** app in Teams, their approvals arrive in that chat: Service Desk requests, change requests and recognition nominations, with Approve and Decline on the card. They can also use `/mango` commands to raise tickets or recognize a colleague. Admins can post a notice about a Communication (a sign-in link to read it) and shared items to Teams channels. If you turn it on, each person asked to acknowledge a must-read also gets it privately in Teams, with an **Acknowledge** button. - **Enablement:** it takes two admins. Your OneMango administrator connects Teams. Your Teams administrator makes the MangoApps Workforce app available in your organization. - **What it is not:** asking Microsoft 365 Copilot about OneMango work is a separate feature, controlled in **Admin → Security → Connectors**. See *AI Assistants*. ## 2. Standing it up 1. Go to **Admin → Organization → Integrations**, choose **Manage Messaging & Sharing**, then **Connect Teams** on the Microsoft Teams card. Sign in with a Microsoft 365 account that can approve apps for your organization, and approve. If **Connect Teams** is greyed out, MangoApps hasn't finished setting up Teams for your environment. Contact support. 2. Choose the Team (or Teams) OneMango may post into, then **Save Teams**. 3. On the Microsoft Teams page, under **Add App**, pick an app and tick what it may do: **Slash Commands**, **Notifications** and **Channel Posting**. Communications needs a channel chosen here. The **Commands** card on the right shows which commands are now on. 4. Ask your Teams administrator to make the **MangoApps Workforce** app available to your people in the Teams admin center. 5. Tell your people. The **Tell your employees** card has a message ready to copy and send. Each person adds the app in Teams (**Apps**, search for MangoApps Workforce, **Add**). 6. Optional: on the **Must-read messages** card, tick **Send must-reads as direct messages** and **Save**. It is off until you do. 7. To check it works, add the app yourself. It sends a welcome message listing the commands you can use. **Two pairings catch admins out.** Nothing reaches a person in Teams until that person has added the app, however the page is set up. And the **Must-read messages** card only offers its switch once Communications, Sites or SOP Hub is turned on for your organization. If people who add the app are told Teams isn't connected although it is, your connection predates OneMango recording your Microsoft 365 organization. Disconnect and connect Teams again once. ## 3. How it fits together **People are matched by work email.** When someone adds the app or writes to it, OneMango asks Teams for their work email. It must match their OneMango email. Only people who are active in your organization are matched. If someone can't be matched, the welcome message says so. **Messages need the app added.** OneMango can only send someone a message in Teams after they have added the app. Until then OneMango reaches them through its other notifications, as your notification settings allow. **A command runs only when two things are true.** Its app was added with **Slash Commands** ticked, and the person has access to that app in OneMango. `/mango help` lists what that person can use. The app's command menu shows every command, whether or not it is turned on. **Your own records stay private.** In a channel or group chat everyone sees the reply. So commands that show your own records (`/mango mytickets`, `/mango ticket_status`, `/mango myrecognition`) answer only in a 1:1 chat with the app. **Buttons act for the person who clicks.** Approve and Decline check that the clicker is allowed to decide. The result is posted in the chat. **If Teams isn't connected.** Someone who adds the app or writes to it before your organization has connected Teams is told to ask their OneMango admin. ### Must-read messages A must-read message is a private Teams message about something a person has been asked to acknowledge or complete. It is separate from the channel notice Communications posts: that notice goes to a channel, while a must-read message goes to one person. Channel posts are unchanged when you turn this on. It is sent for four kinds of item, at the moment the item is sent: | What was sent | What the person gets in Teams | |---|---| | A must-read post | Title, an "In short" summary, a link, and an **Acknowledge** button | | A broadcast that asks for acknowledgement | The same, with **Acknowledge** | | A Sites page published with **Ask readers to confirm they've read it** | Title, summary and a link only. They confirm on the page itself. | | An SOP that people are asked to complete | Title, summary and a link only. They complete it in SOP Hub. | The "In short" summary is written by AI, and the message says so. Each message also names who sent the item and, when there is one, the date it is due. For example, HR publishes a must-read post, "Updated uniform policy", to the Warehouse team. Each person on that team who has added the app gets a private card from MangoApps Communications. One tap on **Acknowledge** records it for them, exactly as if they had acknowledged it in OneMango, and the card then reads "✓ You acknowledged this." **It is set per connection.** The switch on the Microsoft Teams page governs Teams only. Slack has its own, on the Slack page, and both can be on at once. **Only the people still being asked get one.** The item's author is left out. So is anyone who is no longer active or has already acknowledged. The same item never reaches a person twice on the same connection. **It follows the item's own delivery rules.** A broadcast's delivery window applies. **Defer off-shift people to their next shift** holds an off-shift person's message until their shift starts. **Only people currently on shift** never sends it to someone off shift. Your off-shift protection (Right to Disconnect) holds back ordinary items, just as it holds back their push notification. Must-read posts and critical broadcasts are sent straight away. Anyone held back still finds the item in OneMango. **It uses each person's language.** The title and summary arrive in the language the person reads that item in. The card's own labels follow their display language. **The Acknowledge button acts only for the person it was sent to.** If someone else presses it, nothing is recorded. The button works for 30 days. After that it points the person to OneMango to acknowledge there. **Only new items are messaged.** Turning the switch on does not send messages about items that were already sent. **Ask AI in Teams.** Off by default. When an admin ticks **Let people ask Ask AI in Teams** on the Microsoft Teams page's **Ask AI** card, people can type `/mango ask` followed by a question, or simply chat with the MangoApps Workforce app. Anything that isn't a `/mango` command goes to Ask AI. They can also @mention the app in a channel or group chat. If the card says **Not available yet**, MangoApps hasn't finished setting up its Teams bot for your environment. Answers use the person's own OneMango access and need Ask AI to be available to them. In a channel or group chat, personal questions (pay, leave, reviews and the like) are not answered, and nothing is changed; the reply says to ask privately. A change that someone asks for privately shows a card with Approve and Decline. Only the person who asked can approve it, it expires after 10 minutes, and it works once. ## 4. Running it ### Change what an app may do in Teams 1. Open **Admin → Organization → Integrations → Manage Messaging & Sharing**, then the Microsoft Teams page. 2. Under **Registered Apps**, each app lists its features (Commands, Notifications, Channels). 3. To change them, add the app again under **Add App** with the new ticks. The ✕ removes it. ### Turn must-read messages on or off 1. On the Microsoft Teams page, find the **Must-read messages** card. 2. Tick or clear **Send must-reads as direct messages**, then **Save**. 3. If the card says **Not available yet**, MangoApps hasn't finished setting up its Teams bot for your environment. If it asks you to turn on Communications, Sites or SOP Hub, do that in **Admin → Apps → All Apps** first. ### The commands your people can use | Command | What it does | Needs | |---|---|---| | `/mango help` | Lists the commands you can use | Always available | | `/mango ask [question]` | Asks Ask AI | Ask AI turned on for Teams, and Ask AI available to you | | `/mango ticket [description]` | Raises a Service Desk ticket | Service Desk | | `/mango mytickets` | Shows your open tickets | Service Desk; 1:1 chat only | | `/mango ticket_status [ID]` | Shows one ticket's status | Service Desk; 1:1 chat only | | `/mango recognize [email] [message]` | Recognizes a colleague | Recognition | | `/mango myrecognition` | Your recognition summary | Recognition; 1:1 chat only | | `/mango leaderboard` | The recognition leaderboard | Recognition | ### Disconnect Teams **Disconnect** is on both the Messaging page and the Microsoft Teams page. It stops everything in this article, must-read messages included. Connecting again brings back the apps and settings you had. ## 5. Settings All on **Admin → Organization → Integrations → Manage Messaging & Sharing → Microsoft Teams**. | Setting | Where | Default | What it changes | |---|---|---|---| | Teams | Team picker, **Save Teams** | None chosen | Which Teams OneMango posts into | | Registered Apps | **Registered Apps** / **Add App** | None | Which apps offer commands, notifications and channel posts | | Default Channel | **Settings** card | None | The channel used when an app has none of its own | | Allow Share to Teams channels | **Settings** card | Off | Lets people share a record's title, note and link to a channel | | Only offer channels the sender belongs to | **Settings** card, under **Who can be sent a record** | Off | Channels the sender isn't in are shown but can't be picked | | Let people ask Ask AI in Teams | **Ask AI** card | Off | Lets people ask Ask AI with `/mango ask`, by chatting with the app, or by @mention | | Send must-reads as direct messages | **Must-read messages** card | Off | Sends each person asked to acknowledge a must-read or broadcast a private Teams message, and a link for a Sites page or SOP | ## 6. More help - *Slack*: the same features in Slack, including its own must-read messages switch. - *AI Assistants*: Microsoft 365 Copilot, Claude, ChatGPT and Slackbot. - *Notifications*: what OneMango sends and to whom, and off-shift protection. - Ask AI — the assistant answers questions about Microsoft Teams from these articles. **Keywords:** Microsoft Teams, Teams integration, connect Teams, MangoApps Workforce Teams app, Teams bot, /mango, slash commands, Teams notifications, Teams approvals, approve from Teams, Teams direct messages, must-read in Teams, acknowledge in Teams, acknowledgement broadcast Teams, Teams channel posts, Share to Teams, Ask AI in Teams, disconnect Teams --- # Mobile — What Employees Get **Category:** System-features **Section:** Advanced Features **Updated:** 2026-10-16 How mobile access works for employees — native apps, mobile web, auto-redirect, login, app grid, dashboard widgets, branding, and what admins control. # Mobile — What Employees Get ## 1. What it is The mobile experience gives employees access to the platform from their phones through two channels: a native iOS/Android app (available in the App Store and Google Play) and a mobile-optimized web surface at `/m/` that any phone browser can reach. Both show the same content — the same apps the admin has enabled, the same dashboard widgets, the same notifications — rendered in a lightweight layout designed for one-handed use. - **Enablement:** Mobile access is a platform capability, not a licensed app. Every tenant has it from day one. There is nothing to turn on — employees with a phone can sign in as soon as they have an account. - **What it is not:** This is not a separate product with its own data. Mobile shows the same business data as the desktop. An admin does not configure "the mobile app" — they configure apps, permissions, and branding once, and mobile reflects those choices. ## 2. Standing it up 1. Employees download the native app from the **App Store** (iOS) or **Google Play** (Android) and sign in with their organization's URL (the same `{business}.workforce.mangoapps.com` domain). 2. Employees who use a phone browser instead of the native app are automatically redirected to the mobile-optimized `/m/` surface when they visit a paired page. No configuration is needed — the platform detects the phone's User-Agent and redirects. 3. To customize the mobile look, go to **Admin → General Settings → Brand & Theme**. The **Mobile App** section lets you set header background, header text, footer background, active tab icon color, and inactive tab icon color. If left blank, the mobile header inherits the desktop sidebar rail color, then the Brand color. On a phone in dark mode the header is dark grey whatever color you choose. 4. Confirm it works: open your organization's URL on a phone. You should see the mobile login screen, then the mobile dashboard with widgets and a bottom tab bar. **Silent-until-paired:** Only apps that have a dedicated mobile view appear in the mobile app grid. Apps without a mobile view still work — tapping them from the tab drawer or a notification opens the desktop version inside the native app's WebView — but they are not listed in the grid to avoid confusion. Whether an app has a mobile view is determined by its route registration — no manual list to maintain. App Builder plugins with at least one record schema also get an automatic mobile renderer. ## 3. How it fits together **Two channels, one access model** — The native app and the mobile web surface (`/m/`) use identical access checks. An app that is enabled for the tenant and accessible to the employee on desktop is accessible on mobile. The mobile app grid, the bottom tab bar, and every in-app screen all run the same enablement and per-user visibility checks the desktop uses, so an admin never has to configure mobile access separately. **Auto-redirect** — When an employee visits a desktop URL on a phone, the platform automatically redirects them to the mobile equivalent. Tablets stay on desktop. The redirect fires only on GET requests so a form submission from a phone never loses its data. Employees can opt out for the rest of their session by appending `?desktop=1` to any URL (or `?mobile=1` to switch back). This preference is session-sticky — it persists until the session ends. **Native app vs. mobile browser** — The platform distinguishes between the native app WebView and a standalone phone browser. When running inside the native app, the mobile layout suppresses its own bottom tab bar (the native app provides its own navigation chrome). When running in a phone browser, the web tab bar shows: **Home** (dashboard), up to three pinned apps from the desktop sidebar, and a **More** button that opens the full app drawer. **App grid** — The full app directory is available at `/m/` (the "Browse all apps" screen). Apps are organized into categories — AI & Automation, AI Agents, Shifts & Scheduling, HR & People, Performance & Growth, Recruiting, Operations & Facilities, Procurement & Finance, Communication & Engagement, and Documents & Compliance. Each category is filtered to show only apps enabled for the tenant and accessible to the current user. If every app in a category is disabled, the category itself disappears from the grid. **Dashboard and widgets** — The mobile dashboard at `/m/dashboard` renders the same widget engine as the desktop dashboard, stacked in a single column. There are 95 mobile-native widget templates covering the full breadth of the platform — schedule, attendance, leave, timesheets, notifications, tasks, recognitions, service desk, forms, training, and more. Widget data comes from the same backend services, so an admin managing widget configuration on desktop simultaneously controls what employees see on mobile. **Multi-workspace support** — Employees who belong to more than one workspace can switch between them from the profile screen at `/m/me`. If an employee taps an app that is enabled on a different workspace but not the current one, the screen tells them to switch workspaces rather than showing the generic "App Not Enabled" message. ## 4. Running it ### Branding the mobile experience Go to **Admin → General Settings → Brand & Theme**. Under the **Mobile App** section, set: - **Header background** — the color of the top bar. Inherits from the desktop sidebar rail color if not set. - **Header text** — auto-detected from header background luminance (light text on dark backgrounds, dark text on light) if not set. - **Footer background, active icon, inactive icon** — control the bottom tab bar appearance. Brand colors, fonts, and border radius from the main theme also apply to the mobile layout. Custom Google Fonts set in the theme (Inter, Roboto, Open Sans, Lato, Montserrat) are loaded on mobile too. In dark mode, the header defaults to a neutral dark tone regardless of the brand color. The mobile layout also supports a maintenance banner — if a maintenance window or read-only mode is active, employees see a prominent bar at the top of every mobile screen explaining what is happening. ### Managing what appears on mobile No separate mobile configuration exists. To change what employees see on mobile: - **Enable or disable apps** at **Admin → Apps & Marketplace**. The mobile app grid and tab bar reflect this immediately. - **Pin apps** to the desktop sidebar rail. The first three pinned apps also appear as tabs on the mobile bottom bar. - **Set audience or visibility rules** on apps. Mobile enforces the same per-user access rules — audience groups, visibility rules, and license seat limits. ### Mobile login Employees sign in on mobile using the same credentials as desktop. Three authentication methods are available: - **Email/username and password** — standard credential login at `/m/login`. - **Sign in with code (OTP)** — a 6-digit code sent to the employee's email (preferred) or phone. Available when the **Sign in with code** setting is enabled (on by default). Employees can identify themselves by email, username, phone number, or employee ID. Codes are 6 digits and rate-limited to 3 requests per 5 minutes, with a maximum of 5 verification attempts per code. - **SSO** — any SSO provider configured with mobile support appears as a button on the mobile login screen. SSO providers must have their channel support set to **Mobile only** or **Both** to appear. Two-factor authentication, if enabled for the user, redirects to the standard 2FA verification flow before completing the login. The native app authenticates via a signed WebView token — it calls the API, receives a short-lived token, and opens `/m/login/native` to establish a session without the user re-entering credentials. Password reset is also available on mobile at `/m/forgot-password` — the employee enters their email or username and receives a reset link. The flow is identical to the desktop password reset. ### Mobile onboarding New employees who sign in on mobile are taken through the same onboarding wizard as desktop, rendered in the mobile layout. Steps, validations, and ordering are identical — only the look changes. Desktop users who accidentally land on `/m/onboarding` are bounced back to the desktop wizard, and vice versa. ### Mobile inbox Notifications appear at `/m/inbox` with folder chips (All, Action Required, Announcements, Archived, etc.) and infinite scroll (25 notifications per page). Each notification links to the mobile version of its target page. A **Messages** entry row at the top links to the direct-messages surface when the Messages app is enabled. Employees can mark individual notifications or all notifications in the current folder as read. When the Communications app is enabled and accessible to the user, a tab bar appears at the top of the inbox for switching between the notification feed and the communications surface. ### Mobile profile Employees can view and edit their profile at `/m/me`. Editable fields are governed by the same field-level permission system as desktop — by default, only preferred name and phone are employee-editable. The edit screen accepts JPG or PNG photos up to 5 MB. When Employee Data Management is enabled and self-service editing is off, non-admin employees cannot edit their profile on mobile. ### Mobile settings Employees manage their notification channel preferences at `/m/settings` — toggling email, push, SMS, and voice on or off. Channels that the admin has disabled at the business level, or that are blocked for the user (bounced email, unverified phone), appear as disabled and cannot be turned on. ### Desktop→mobile URL rewriting Notification action URLs and widget links are stored as desktop paths. On mobile, the platform automatically rewrites these to their `/m/` equivalents before rendering, so tapping a notification (for example, an approval request) opens the mobile screen rather than the desktop page inside the WebView. ### Expired session handling When an employee's session expires while using the mobile surface, they are redirected to `/m/session-expired` instead of the desktop login page. The native app detects this and can re-authenticate silently. In a phone browser, the employee sees a dedicated session-expired screen with a sign-in button. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Mobile header background | Admin → Brand & Theme → Mobile App | Inherits from the left navigation rail color, else Brand (dark grey in dark mode) | Top bar color on the mobile layout | | Mobile header text | Admin → Brand & Theme → Mobile App | Auto-detected from background luminance | Text color on the mobile top bar | | Mobile footer background | Admin → Brand & Theme → Mobile App | White (light) / dark zinc (dark) | Bottom tab bar background color; a color you choose is kept in dark mode too | | Active tab icon color | Admin → Brand & Theme → Mobile App | Brand, adjusted where needed to stay readable on the tab bar by day and at night | Color of the current tab's icon and label. The current tab is also shown with a bold label and a short bar above it, so it stands out whatever the colors | | Inactive tab icon color | Admin → Brand & Theme → Mobile App | Accent (muted gray when unset) by day, light gray at night, adjusted where needed to stay readable on the tab bar | Color of the other tabs' icons and labels | | Sign in with code (OTP) | Admin → Security Settings | On | Whether employees can log in on mobile using a 6-digit code | | Employee self-service editing | Admin → Employee Data Management | On (when app enabled) | Whether non-admin employees can edit their own profile on mobile | | SSO channel support | Per-SSO provider configuration | Both | Whether an SSO provider appears on the mobile login screen (set to **Mobile only** or **Both**) | ## 6. More help - **Notifications — Channels, Defaults & Opt-outs** — how the notification channels employees toggle on `/m/settings` work platform-wide - **Security & Sign-On** — SSO setup, two-factor authentication, and the OTP login setting - Ask AI — the assistant answers questions about mobile access from these articles. **Keywords:** mobile, mobile app, native app, mobile web, phone, smartphone, iOS, Android, mobile login, mobile dashboard, mobile widgets, mobile branding, tab bar, app grid, mobile redirect, OTP login, sign in with code, mobile SSO, mobile onboarding, mobile inbox, mobile profile, webview --- # Muscle Memory App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How Muscle Memory distills operational outcomes into evidence-backed lessons your organization recalls automatically — setup, concepts, and settings. # Muscle Memory ## 1. What it is Muscle Memory watches closed operational arcs — an incident resolved and its corrective action holding, an automation with a track record of clean runs, a Service Desk pattern that keeps bouncing — and distills each into a lesson backed by the records behind it. No evidence, no lesson. The app is licensed and opt-in. An admin enables it from Admin → Apps → All Apps; it requires a license. Once enabled, distillers run nightly and a retroactive backfill scans existing history on first enable. **What it is not:** Muscle Memory does not ask anyone to write things down. It learns from outcomes that already closed in other apps. Managers *can* add lessons manually, but the primary source is automated distillation. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps → Muscle Memory** and enable the app. 2. The first enable triggers a retroactive backfill of your operational history. When the backfill finishes, admins receive an in-app notification summarizing how many lessons were found. 3. Open **Muscle Memory → Settings** to review which distillers are active. Nine of the twelve sources are on by default; the experimental scheduling distiller and the two that read free text (Service Desk resolution notes, and the reasons people give when they reject the AI's drafts) are off until you turn them on. 4. Assign access. By default the app is available to all members. Lessons describe operations, never individuals, so every member with access can read them. Who may curate (confirm, correct, forget, reinstate, add, export) is yours to set under **Settings → Who can do what**; it defaults to managers and above, which is what the app enforced before that setting existed. 5. Confirm it worked: open the **Business Memory** tab. Lessons appear automatically as the nightly distiller sweep closes arcs. To see the app fully rendered before real lessons arrive, go to **Settings → Sample data → Load sample data**. If no lessons appear after the backfill: the distillers need closed arcs to work with. An incident whose corrective action has not yet completed, or one still inside its recurrence window, is not eligible. The default recurrence window is 60 days. ## 3. How it fits together ### Lessons, evidence, and confidence A **lesson** is one specific, operational statement — for example, *"Incidents of type Slip/Trip at the Downtown Warehouse stopped after the non-slip matting was installed (no recurrence in 60 days)."* Every lesson carries a confidence score between 0 and 1, a domain (such as Safety Hub, Scheduling, or Service Desk), and links to the records it was distilled from (its evidence). Confidence is not static. When the same pattern is observed again, the lesson is reinforced and its confidence rises. When a manager confirms a lesson, confidence increases. When later incidents contradict a "held" lesson, confidence decays — and if it falls below your confidence floor (default 0.60), the lesson is marked **Superseded**. Superseded lessons stay visible with a badge but stop appearing in Ask AI answers. ### Three statuses - **Active** — the lesson stands and can inform Ask AI answers (if above the confidence floor). - **Superseded** — later evidence contradicted it; visible with a badge, excluded from recall. A manager can reinstate it with the **Still holds** action. - **Forgotten** — a manager archived it. Hidden from all surfaces. The distillers will not re-learn a forgotten lesson. ### Business Memory vs Personal Memory These are separate stores serving different purposes: - **Business Memory** (the default tab) holds organization-wide lessons distilled from operational outcomes. Everyone with app access can read them; whoever your **Who can curate business lessons?** setting reaches curates them (managers and admins by default). - **Personal Memory** shows the durable facts the AI assistant remembers about the individual user across sessions — preferences, what they are working on. No colleague or manager can see another person's personal memory — an administrator reaches it only by including it in a data request about that person — and each user can erase any item or everything at once. ### Distillers — where lessons come from Each distiller watches a specific type of operational arc: | Distiller | What it watches | Default | |---|---|---| | Incident + corrective action outcomes | A corrective action completed and the recurrence window elapsed — verdict: **Held** or **Didn't hold** | On | | Automation (playbook) outcomes | Playbooks with enough run history — verdict: **Adopted** or **Rolled back** | On | | Service Desk resolution patterns | Request types with a consistent resolution track record — verdict: **Dependable** or **Bouncing** | On | | Leave/time-off decision patterns | Leave types with a decision record across approvals | On | | Onboarding + training readiness | Learning paths with a completion track record | On | | Won RFP bids | RFP bids that were won, along with library reuse data | On | | Staffing/scheduling correlations | Correlations between staffing and outcomes (experimental) | Off | Each distiller is individually togglable in **Settings → What Muscle Memory learns from**. ### Ask AI recall When a user asks a question in Ask AI, the recall service searches for relevant lessons (using semantic similarity and keyword matching) and injects them into the AI's context. The AI cites the lesson and links back to it. This is how the business's institutional knowledge reaches employees without anyone opening the help centre. Recall is on by default and controlled by the **Recall business lessons in Ask AI answers** setting. ## 4. Running it ### Reviewing lessons Open the **Business Memory** tab. Filter by status (**All lessons**, **Needs review**, **Verified**, **Superseded**), by domain, or search by keyword. Sort by **Most relevant** (last recalled, then confidence), **Highest confidence**, or **Recently learned**. Curators (whoever your **Who can curate business lessons?** setting reaches) see curation actions on each lesson: - **Confirm** — the lesson is true; raises confidence. - **Correct** — amends the lesson with a note (kept alongside the claim). - **Still holds** — reinstates a superseded lesson and lifts its confidence back to at least your confidence floor. - **Forget lesson** — archives the lesson permanently. It will not be re-learned. ### Adding a lesson manually A curator types one sentence into the text box at the top of the Business Memory tab — or the same box on the mobile view — and clicks **Add lesson**. The platform rewrites it into a structured claim with a domain and optional location — no form to fill. Near-duplicates reinforce the existing lesson instead of creating a second one. Sensitive text is rejected — passwords and door or alarm codes, ID and account numbers — and the same check applies to a curator's correction note. Lessons describe how the business works, never a person: don't write about anyone's health. Everyone else sees a **Suggest lesson** button instead, on both surfaces. Suggestions are born unverified and sit below the recall confidence floor until a curator confirms them. ### Exporting lessons Anyone who can curate lessons can download every one of them as a CSV from the **Export** button on the Business Memory tab. (Who that is follows your **Who can curate business lessons?** setting, which defaults to managers and admins.) The file includes each lesson's claim, domain, confidence, verification history, correction notes, evidence, and measured outcome lift. ### Weekly digest Every Monday, curators, managers and admins receive "What your business learned this week" in the app and by email — lessons minted in the past week, how often answers relied on them, and, for curators, what is waiting for review and any hand-added lessons that have not been re-confirmed in 6 months. An admin can turn the digest off under **Settings → Notifications**; each person can turn off the email or the in-app copy from their notification preferences (**Weekly Learning Digest**). ### Notifications Muscle Memory sends in-app notifications for: - **Backfill complete** — admins, when the first-enable retroactive scan finishes. - **A corrective action didn't hold** — curators, when an incident arc closes with a negative verdict (action request). - **A lesson may no longer hold** — curators, when a later event contradicts a lesson and it is superseded (action request). - **A teammate suggested a lesson** — curators, when someone who cannot curate suggests a lesson for review (action request). - **Your lesson was confirmed / amended / wasn't kept**, and **Your lesson matched one we already knew** — the person who suggested a lesson, when a curator decides on it. - **You now curate your business's lessons** — people who start curating through a change to **Who can curate business lessons?**, a role, group or team, with the number of lessons waiting. The first two action requests stop when an admin turns off **Alert curators when the nightly sweep supersedes or questions a lesson**. Users control these from their notification preferences under the **Business Memory Lessons** category; the weekly digest has its own category, **Weekly Learning Digest**. ## 5. Settings All settings are at **Muscle Memory → Settings**. Only users who can edit the app see this tab. | Setting | Card | Default | What it changes | |---|---|---|---| | Muscle Memory AI assistant in Ask AI | Muscle Memory Agent | On | Enables the Muscle Memory agent in Ask AI — browse, search, and (for curators) curate lessons conversationally | | Distill incident + corrective-action outcomes | What Muscle Memory learns from | On | Incident distiller runs on the nightly sweep | | Remember durable facts for each user (personal memory) | Personal memory | On | The assistant stores per-user facts across sessions | | Distill automation (playbook) outcomes | What Muscle Memory learns from | On | Playbook-outcome distiller runs | | Distill staffing/scheduling correlations (experimental) | What Muscle Memory learns from | Off | Scheduling distiller runs — experimental, opt-in | | Distill Service Desk resolution patterns | What Muscle Memory learns from | On | Service Desk distiller runs | | Distill won RFP bids into lessons | What Muscle Memory learns from | On | RFP win distiller runs | | Distill leave/time-off decision patterns | What Muscle Memory learns from | On | Leave decision distiller runs | | Distill onboarding + training readiness patterns | What Muscle Memory learns from | On | Onboarding readiness distiller runs | | Distill approval patterns across your apps (purchasing, expenses, scheduling, timesheets, access and asset requests, profile changes, form reviews) | What Muscle Memory learns from | On | Counts how dependably each kind of request is approved, in the apps you have switched on — purchase requisitions and orders, expense reports, shift claims, schedule approvals, timesheets, Service Desk access requests, asset requests, profile-change requests and form reviews. Numbers only, no record text | | Draft playbooks from Service Desk resolution notes (a curator confirms each one) | What Muscle Memory learns from | Off | Sends resolution notes to your AI provider to draft a de-identified "when X, the team does Y" lesson; it waits under Needs review until a curator confirms it | | Learn from the reasons people give when they reject the AI's drafts and proposed actions (a curator confirms each lesson) | What Muscle Memory learns from | Off | Same, for the reasons reviewers type when rejecting an AI-drafted reply or declining an action an agent proposed | | Recall business lessons in Ask AI answers | How Muscle Memory uses what it learns | On | Lessons are injected into Ask AI answers when relevant | | Show a lesson where the decision is made (for example, on the leave request form) | How Muscle Memory uses what it learns | On | A lesson about exactly what someone is doing is shown where they do it — beside the leave request form for the person asking, and above the leave, timesheet and shift-claim approval queues for the person deciding — to people who could also read it in the app | | Keep a history of where each lesson was used | Lesson usage history | On | Records a usage event each time a lesson enters an answer | | Also record who received the answer | Lesson usage history | Off | Adds the recipient's name to each usage record — off by default because lessons describe operations, not individuals | | Keep lesson-usage history for (days, 0 = forever) | Lesson usage history | 365 | Usage records older than this are deleted on the nightly sweep; 0 keeps them indefinitely | | Distill Frontline Execution overrides into setting proposals | What Muscle Memory learns from | On | Reads Frontline Execution's override ledger and proposes one setting change per lesson, for Loop to measure | | Propose repeat contracts you always approve, so a Contracts admin can accept them for automatic approval | What Muscle Memory learns from | On | Proposes only; nothing is approved automatically until a Contracts admin accepts a pattern | | Alert curators when the nightly sweep supersedes or questions a lesson | Notifications | On | The "corrective action didn't hold" and "may no longer hold" asks; suggestions still reach curators either way | | Send a weekly Muscle Memory digest to curators and managers (in-app and email) | Notifications | On | The Monday digest, both copies | | Minimum confidence to keep a lesson (0..0.85) | Thresholds | 0.60 | Written as a fraction: 0.6 is the 60% shown on lessons. Lessons below it stop informing answers and hints, and the approval, leave, Service Desk, onboarding, override and contract sources supersede a lesson whose fresh count falls below it on the nightly check (not one a curator marked Still holds in the last 30 days). Answers and hints never use a lesson below 0.6, whatever this is set to | | Recurrence window for incident lessons (days) | Thresholds | 60 | How far back the incident distiller looks for a recurring pattern | ## 6. More help - **Muscle Memory FAQ** — specific setup and operating questions. - **Ask AI** — the assistant answers questions about Muscle Memory from these articles, and the Muscle Memory agent can list, search, and help curate lessons conversationally. **Keywords:** muscle memory, business memory, institutional memory, lessons learned, corrective action, knowledge retention, business lessons, distiller, operational memory, muscle-memory, muscle_memory --- # Muscle Memory FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common setup and operating questions about Muscle Memory — for the admin running it. # Muscle Memory FAQ Answers to common setup and operating questions about Muscle Memory. For what the app is and how to set it up from scratch, see the [Muscle Memory Overview](/help/articles/muscle_memory_app_overview). --- **Setup** ## Will the app be empty when I first turn it on? No. Enabling the app triggers a retroactive backfill that scans your existing operational history — incidents, corrective actions, automation run records — and distills what it finds into lessons. Admins receive an in-app notification when the backfill completes, telling them how many lessons were minted. Tenants evaluating the app with no history can load sample data from the Settings tab. ## Which distillers are on by default, and which are off? Nine of the twelve learning sources are on by default: incidents and corrective actions, automations, Service Desk resolution patterns, won RFP bids, leave/time-off decisions, onboarding and training readiness, Frontline Execution overrides, approval patterns across your apps, and repeat contracts you always approve. Three ship off and must be turned on explicitly in **Settings → What Muscle Memory learns from**: the experimental staffing/scheduling correlations, and the two that read free text — playbooks drafted from Service Desk resolution notes, and lessons from the reasons people give when they reject the AI's drafts. A source only learns from an app your organization has enabled. ## Do I need to configure anything before lessons appear? No. With the defaults, the nightly distillation sweep and the retroactive backfill will start minting lessons from your existing data as soon as the app is enabled. The only prerequisite is that the source apps (Safety Hub, Service Desk, etc.) already have operational records. --- **Permissions and access** ## Who can see business lessons, and who can curate them? Every member the app is published to can browse and search business lessons — they describe operations, never individuals. That read is deliberate and is not configurable; if you need a narrower readership, restrict the app's audience under **Access Management** in Admin → Apps → All Apps. Everything else is yours to set, on **Settings → Who can do what**: - **Who can curate business lessons?** — confirm, correct, forget, reinstate, add a lesson directly, and export the corpus. Defaults to managers and admins, which is what the app enforced before this setting existed. You can also choose app admins only, anyone with direct reports, or specific groups. - **Who can see Muscle Memory analytics?** — the Analytics tab and the same figures over the API and the Ask AI assistant. Defaults to the same people who curate, but you can grant it more widely (for example, everyone) without granting anyone the ability to change a lesson. - **Who can suggest a lesson?** — defaults to everyone with app access. Business admins and anyone you designate as a Muscle Memory app administrator can always do all three, whatever these settings say. Whichever policy is in force applies identically on the desktop tab, the mobile view, the Ask AI agent, and the REST API — all four ask the same question. ## Who receives the weekly digest and alert notifications? The time-sensitive alerts (corrective action did not hold, lesson superseded, teammate suggested a lesson) go to whoever can curate lessons — your **Who can curate business lessons?** setting — under the **Business Memory Lessons** notification preference. The weekly Monday digest goes to curators and to every manager and admin, in the app and by email, under its own **Weekly Learning Digest** preference, so muting Business Memory Lessons does not stop it. Each person can mute either from their notification settings; an admin can turn the digest or the nightly alerts off for everyone under **Settings → Notifications**. --- **Day-to-day operations** ## How do I add a lesson that no system ever recorded? Type one sentence in the **Add a lesson** field on the Business Memory tab. AI restructures it into a claim with a domain and optional location scope. Lessons must be between 15 and 600 characters. If the sentence is too close to an existing lesson, it reinforces the existing one instead of creating a duplicate. Lessons added by a curator are born verified at 80% confidence. ## Can employees who are not managers suggest lessons? Yes, by default. Any member with app access can suggest a lesson from the Business Memory tab or from the mobile view — the same one-sentence box, which reads **Suggest lesson** for them and **Add lesson** for a curator. (An admin can narrow this under **Settings → Who can do what → Who can suggest a lesson?**.) Suggestions are born unverified at 55% confidence — below the 60% recall floor — so they cannot shape Ask AI answers until a manager confirms them. Suggestions are rate-limited to 5 per user per hour. Managers receive an in-app notification to review each suggestion. ## What happens when a manager confirms a lesson? Confirming boosts the lesson's confidence by 10 percentage points (capped at 100%) and records who verified it and when. If the lesson was below the recall floor before confirmation, the boost may bring it above the floor so it starts informing Ask AI answers. ## What does "correct" do, and how is it different from editing a lesson? Correcting a lesson attaches a note alongside the original claim — the note travels with the lesson everywhere it appears. The claim text itself is not rewritten. The correction counts as a human review (it records who corrected it and when) but does not boost confidence. ## What happens when I forget a lesson? Forgetting sets the lesson's status to **Forgotten**. It disappears from all list views, stops informing Ask AI answers, and — importantly — the distillers will never re-learn it, because the original dedup key is preserved. Nothing is hard-deleted; forgotten lessons are archived. ## How do I bring back a lesson that was marked superseded? A manager can reinstate a superseded lesson from the Business Memory tab (or via the Ask AI agent or REST API). Reinstating lifts the lesson's confidence back to the confidence floor and returns its status to **Active**, so it re-enters Ask AI recall. Reinstate works only on superseded lessons — it cannot undo a forget. --- **When something looks wrong** ## Why isn't a lesson showing up in Ask AI answers? A lesson must meet all of these conditions to be recalled into an Ask AI answer: its status must be **Active** (not superseded or forgotten), its confidence must be at or above the confidence floor (default **0.60**), and the **Recall business lessons in Ask AI answers** toggle must be on in Settings. Sample lessons (loaded from the Settings tab) are always excluded from recall. ## A lesson says "Superseded" — what does that mean? Later incidents of the same type at the same location contradicted the lesson's claim. Each contradicting incident reduces confidence by 10 percentage points. When confidence falls below your confidence floor (default 0.60), the lesson is marked **Superseded**: it stops informing Ask AI answers but stays visible on the Business Memory tab with all its evidence preserved. Managers see an in-app alert when a lesson is superseded by recent contradictions. ## My corrective action resolved the problem, but I don't see a lesson yet The incident distiller waits until the full recurrence window has elapsed after a corrective action completes — the default is **60 days**. Only then is the verdict final (held or did not hold). The distiller also runs on a nightly sweep, not in real time, so a newly eligible arc may take up to a day to appear. ## I can't find the lesson a notification linked me to Notification deep links carry the lesson's ID, and the list sorts that lesson to the top of the page. If the lesson has since been forgotten, it will not appear, and the page says so above the list: forgetting a lesson can't be undone, so a curator would need to add it again. If the lesson is simply outside the filter you have on, the same note offers a link that shows it. ## What is the Learning tab? It shows how your business is learning, in order, where the Business Memory tab shows what it knows. **Patterns forming** lists the records Muscle Memory is watching that do not have enough history for a lesson yet — counts only, for example "Service Desk · Access — 7 of 10 resolved requests needed". Below it, a timeline shows each lesson being learned, confirmed by a curator, relied on by the assistant, tested in Loop, or superseded. The patterns panel follows the same permission as Analytics; everyone who can open the app sees the timeline. ## Why does a lesson appear on the leave request form or an approval queue? When a lesson is about exactly what someone is doing, it is shown where they are doing it, with a link to the lesson in Muscle Memory. A person requesting leave sees the lesson for the leave type they pick, on the desktop and the phone (before they pick one, the two strongest). An approver sees it above the queue they are about to work: leave approvals (the lessons for the leave types waiting on that page), timesheet approvals and shift claims. Only active lessons at or above your confidence floor are shown, and only to people who could also read them in Muscle Memory. An admin can turn this off with **Show a lesson where the decision is made** in Settings. ## Which approvals does Muscle Memory learn from? Leave decisions, Service Desk resolutions and Frontline Execution hand-offs have their own lessons. Beyond those, it counts how dependably each kind of request is approved in the apps you have switched on: purchase requisitions and purchase orders, expense reports, shift claims, schedule approvals, timesheets, Service Desk access requests, asset requests, profile-change requests and form reviews. These lessons are made of counts only — never who asked, who decided, or anything that was written on the record. Only decisions a person made are counted: an approval made automatically by a rule, an instant grant or an AI agent is left out, and so is a record that was created already approved. Profile-change requests are counted per field, and never for a sensitive field (for example gender, date of birth, disability or veteran status, pay, or a custom field). Some records are never learned from by design, whatever is switched on: HR files, disciplinary actions, benefits, resignations, recruiting screenings, performance reviews, incident investigations, banked-time payouts and pay changes. ## What does "Apply this change" do? Some lessons propose one Frontline Execution setting change (for example, raising the daily directive budget). A Frontline Execution admin can apply it in one click from the lesson or from Loop: the setting is saved exactly as the settings page would save it, and Loop starts a 30-day measurement of whether it helped. If Loop is not available to you, the change is still made and the message says it is not being measured. ## Who gets the weekly email? Every Monday, people who curate lessons and managers receive "What your business learned this week" — new lessons, how often the assistant relied on them, and (for curators only) how many lessons are waiting for review. It is its own notification category, **Weekly Learning Digest**, so anyone can turn the email or the in-app copy off without affecting review requests. ## What is the difference between "used in an answer" and "offered to the assistant"? Every time someone asks Ask AI a question, Muscle Memory offers the assistant the few lessons that look relevant. Most of the time the assistant does not need them. When a lesson actually shapes the answer, the assistant records that, and only then does it count as **used** — that is the number beside each lesson, the one on the Analytics tab, and the only case in which the answer shows **Informed by N business lessons**. "Offered" is shown next to it so you can see both. Uses recorded before this distinction existed show as offered. ## Can I tell the assistant to remember something? Yes. Say "remember that I prefer CSV exports" and it is saved to your Personal Memory straight away, with a **Saved to your memory** note under the answer. If what you want remembered is about how the organization works ("month-end close is on the 5th working day"), the assistant tells you it will be sent to your lesson curators as a suggestion with your name on it; it appears under **Needs review** and informs answers only after a curator confirms it. If you curate lessons yourself, the assistant asks you to confirm it. Either way, the note under the answer links straight to the suggestion. Asking the assistant to remember something you previously erased puts it back. ## What are playbook lessons, and does Muscle Memory read what my team writes? Not unless an admin turns it on. Two settings — **Draft playbooks from Service Desk resolution notes** and **Learn from the reasons people give when they reject the AI's drafts and proposed actions** — are off by default. When on, those notes are sent to your AI provider to find the practice they have in common ("when an access request comes in, the team confirms manager approval, then…"). The draft never names a person, arrives under **Needs review**, and is never used in an answer until a curator confirms it. A curator's wording is never overwritten, and a forgotten playbook is not drafted again. ## Why does the "Used in N answers" count show zero for a lesson I know was used? If the **Keep a history of where each lesson was used** toggle is off in Settings, the app does not record individual usage events — the count reads zero because nothing was recorded, not because the lesson was never recalled. Turning the toggle on starts recording from that point forward; it does not backfill. --- **Personal memory** ## What is personal memory and who can see it? Personal memory stores durable facts the AI assistant remembers about each user across sessions. No manager or coworker can read it; an administrator can include it in a data request about that person (an export or erasure of everything the business holds about them). Each user can review every remembered fact on the **Personal Memory** tab and erase any single fact or everything at once. ## Can I turn personal memory off for the whole organization? Yes. The **Remember durable facts for each user (personal memory)** toggle in Settings controls personal memory tenant-wide. Turning it off stops new facts from being stored without affecting business memory. Existing personal facts remain until the user erases them. --- **Licensing and limits** ## Does Muscle Memory require a licence? Yes. Muscle Memory requires a licence and is opt-in per tenant — it ships disabled. An admin enables it from Admin → Apps → All Apps. That enablement is the single consent moment for both memory layers (business and personal), which matters because the app reads real operational data. ## Are there limits I should know about? | What | Limit | |---|---| | Hand-written lesson length | 15–600 characters | | Suggestion rate limit (non-curators) | 5 per user per hour | | Lessons recalled per Ask AI answer | 4 | | Confidence range | 0.00–1.00 | | Default confidence floor | 0.60 | | Default recurrence window | 60 days | | Reinforcement confidence boost | +0.05 (capped at 0.95) | | Confirmation confidence boost | +0.10 (capped at 1.00) | | Contradiction confidence decay | −0.10 per contradicting incident | | Manual lesson initial confidence | 0.80 (added by a curator) / 0.55 (suggestion) | | Usage history retention | 365 days by default (0 = keep indefinitely) | | Distillation schedule | Nightly sweep, plus a retroactive backfill at enablement | | Re-attestation nudge | Hand-added lessons not re-confirmed or recalled in 6 months | ## Who can export lessons? Anyone your **Who can curate business lessons?** setting reaches — managers, admins and super admins by default — can export the full set of visible business lessons (active and superseded) as a CSV from the Business Memory tab. The export includes evidence links, verification details, correction notes, and measured outcome data. --- **More help** - [Muscle Memory Overview](/help/articles/muscle_memory_app_overview) - Ask AI — the assistant answers Muscle Memory questions from these articles. **Keywords:** faq, muscle memory, business memory, personal memory, lessons, confidence, distiller, recall, corrective action, institutional memory, not showing, superseded, permissions, muscle-memory, muscle_memory --- # Notifications — Channels, Defaults & Opt-outs **Category:** System-features **Section:** Advanced Features **Updated:** 2026-10-16 How the platform delivers notifications across in-app, email, SMS, push (phone and browser), voice and Microsoft Teams, what admins control, and how employees manage their own preferences. # Notifications — Channels, Defaults & Opt-outs ## 1. What it is Every app on the platform sends its notifications through one shared delivery layer. One set of admin controls decides which notifications go out, on which channels, and when. Employees then tune their own preferences within what you allow. There are six channels: in-app, email, SMS, push, voice and Microsoft Teams. Push reaches people two ways: the OneMango phone app (listed as Mango Ops in the App Store and on Google Play) on a phone, and a web browser on a computer. - **Enablement:** notifications are part of the platform, not a licensed app, so every organization has them. Each outbound channel has its own master switch, and browser notifications are off until an admin turns them on. - **What it is not:** the notification bell and Inbox are where people *read* notifications. This article covers the delivery and settings layer underneath them. ## 2. Standing it up 1. Go to **Admin → General Settings → General Settings** and open the **Email Notifications**, **SMS Settings** and **App Push Notifications** cards. Each holds the master switch for its channel. When a master switch is off, nothing goes out on that channel, whatever anyone's preferences say. 2. To reach people on their computers, open **App Push Notifications** and turn on **Send notifications to browsers** in the **Browser notifications** card. It only appears while the master push switch above it is on, because browser notifications are a push channel. 3. Still on that page, press **Send a test to this browser**. Your browser may ask for permission first. A notification arriving confirms the setup works on your computer. 4. Go to **Admin → General Settings → Notifications**. The **Settings** tab holds the per-notification switches, grouped by area (Attendance & Time Tracking, Schedule Management, Leave & Time Off and so on). Review them, then press **Save All Settings**. 5. Optionally set up **Groups** at **Admin → General Settings → Groups**. If you have none yet, **Load Default Groups** creates a starter set. 6. Tell your people where their own settings live: **Account Settings → Notifications**. **Two things silently do nothing until a second thing is set:** - **Browser notifications need both halves.** The admin switch only makes the offer available. Each person must then press **Turn on** in their own browser before anything reaches it. - **Per-notification switches follow the app.** The Settings tab hides areas whose app is not turned on for your organization. A leave switch does nothing until Leave Management is enabled. ## 3. How it fits together **Channels and their defaults.** Each notification category (a type of message, such as shift reminders or approvals) has default channels for people who have not changed anything: - **In-app** is on almost everywhere, and **email** for most categories. - **Push** is on by default only for time-sensitive categories: shift reminders, approvals, direct messages, safety alerts and similar. - **SMS** is on by default only for emergency alerts, on-call, and job offers sent to candidates. A person can switch SMS on for more types in **Account Settings → Notifications** — among them **Shift Reminders** and **Open Shifts** (a new or urgent open shift, when Shift Marketplace's SMS Notifications setting is on). Ask AI can tell anyone which types can come by text and whether texts reach them. - **Voice** is never on by default. It is reserved for the last step of an escalation. - **Microsoft Teams** works only once your organization has connected Teams. It is then on by default for Service Desk help requests and change management. **Phone push vs browser push.** Both count as the **push** channel. A person's push preference, quiet hours and the protections below apply to both in the same way. The difference is how a device gets registered: - A **phone** registers when the person opens the OneMango phone app. - A **computer** registers when the person accepts the browser offer. While browser notifications are on, people see a banner reading *"Get notifications on this computer."* with **Turn on** and **Not now**. The browser's own permission prompt opens only after they press **Turn on**, never on page load. - The banner never appears on a phone, where the mobile app carries push. - Browser notifications follow the signed-in person. When someone signs out, that browser stops receiving their notifications, so a shared computer does not show one person's alerts to the next. **The order checks run in.** When a notification is about to go out on a channel, the platform checks in this order. The first check that says no wins: 1. The person's own blocks — an email address that bounced, or a channel they switched off entirely 2. The channel's master switch for your organization 3. The per-notification switch on the Notifications **Settings** tab 4. The person's preferences and opt-outs for that category and channel 5. Quiet hours — push, SMS and voice only A few messages that must arrive skip the person's own preferences (check 4): emergency alerts, critical broadcasts, Service Desk after-hours alerts, Lone Worker SOS escalations, and emails the platform treats as required, such as password resets and sign-in codes. Some of them also go through quiet hours and through a channel the person switched off entirely, on the channels they were sent with: - **Emergency alerts**: in-app, push, text and call. Their email still stops if the person turned email off. - **Service Desk after-hours alerts**: in-app, and push or text as the team set them. Their email copy follows the person's email settings. - **Critical broadcasts**: in-app, email, push and call. A critical text still stops if the person turned texts off, replied STOP, or their number can't receive texts. - **Lone Worker SOS escalations**: text and call. Reminders to acknowledge an emergency alert are not among them: they follow the person's channel preferences. They are urgent, though, so like other urgent notifications they come through quiet hours. Worked example: a shift reminder is going to an employee by push at 23:00. Push is on for the organization, the shift reminder switch is on, and the employee has push on for shift reminders. Business quiet hours run 22:00–08:00, so check 5 holds the push. The reminder still lands in their in-app notifications. Had the reminder been marked urgent, it would go through, because urgent notifications may break through quiet hours by default. **Groups.** A group is a reusable audience: a named set of people you can target from notifications, custom rules, app access and many apps' audience pickers. Groups are shared across the platform, not owned by one app. Types include a fixed list (**Static**), **Reports under a manager**, **Attribute match** (combine location, department, job level, tenure and more), job title or family, department, platform role, places (a location and beneath it, locations with an attribute, or a radius), and shift-based types whose membership changes through the day. **Being on shift.** Two places let you target only people who are working: - On the Groups page, an **Attribute match** group has **Only people on shift**, with the same windows: **Off**, **Now**, **Today**, **Tonight**, or **Next hours** after it sends. - In the audience picker used when composing (for example in Communications), **Only people on shift** offers a time window: **Now**, **Today**, **Tonight**, or **Next hours** for a chosen number of hours. The audience is worked out again at every send, so it always reflects the current rota. **Digests.** Email can arrive immediately, or batched into a daily or weekly digest. For purely informational categories (Libraries, Wellness Programs, Company Store and a few others), admins and managers default to a daily digest while employees stay on immediate. Anything urgent or asking for action still sends at once. ## 4. Running it ### Seeing why someone did or didn't get a notification Go to **Admin → General Settings → Notifications → Logs**. It lists every email, SMS, in-app and push notification sent to your people. It also lists deliveries that were blocked, with the reason in plain words — for example the recipient's own preferences, quiet hours, or a channel turned off for your organization. **Export CSV** downloads the filtered list. ### Watching delivery health The **Analytics** tab shows email, SMS and push delivery statistics: delivery rates, bounces, blocked recipients and escalations. From here you can retry soft-bounced emails, clear soft-bounce flags, or re-enable email or SMS for a person who was blocked. ### Checking who has push **Admin → General Settings → General Settings → App Push Notifications → Registered Devices** lists every registered phone and browser. You can filter it by **iOS**, **Android** or **Browser**, send a test to one device, or remove old ones. ### Routing attendance alerts with custom rules The **Custom Rules** tab is for attendance scenarios. **Create New Rule** pairs a notification type and condition with a threshold and one or more groups as **Notification Recipients**. You can also narrow a rule to one location or organizational role. Rules decide *who* is alerted; they do not block other notifications. ### Escalating what's urgent, and what's overdue Two escalation tools sit on the **Settings** tab: - **Escalation Defaults** covers urgent events. When on, a high or critical event goes out step by step. By default that is in-app and push, then SMS and email after 5 minutes without acknowledgement, then voice after a further 10 minutes. Some apps (Broadcast, On-Call, Safety and others) can override this in their own settings. - **Overdue Escalation Ladder** covers things people are late on: a policy, job description, course, Must-Read, onboarding task, credential or project to-do. The person who owes it keeps getting their app's own reminders. The ladder decides who else hears, and when — for example *their manager* on the day it becomes overdue, then *their manager's manager* a week later. The default ladder ships empty, so nothing escalates until you add steps. Each kind of item can use the default ladder, a custom one, or — where an app already escalated on its own — that app's setting. ### Protecting people's time off - **Right to Disconnect (off-shift protection)** holds non-urgent push, SMS and voice for frontline, hybrid, non-exempt and hourly workers while they are off shift. The messages wait in their in-app notifications. People with none of those classifications are not covered. - **Quiet non-urgent notifications while on the floor** is a per-location setting under **Admin → Organization → Locations**. While someone is clocked in at that location, non-urgent push, SMS and voice become in-app only. Urgent and emergency alerts pass through both. If the platform cannot tell whether someone is on shift, it delivers rather than mutes. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Master Push Notification Control | App Push Notifications | On | Whether any push goes out, to phones or browsers | | Send notifications to browsers | App Push Notifications → Browser notifications | Off | Whether people are offered browser notifications, and whether browsers receive push | | Per-notification switches | Notifications → Settings | Most on | Whether that notification type is sent at all | | Max emails per recipient per day | Notifications → Settings → Daily Email Volume Cap | 15 | Past this many a day, a person's further non-urgent emails go into a digest; 0 turns the cap off | | Enable Escalation System | Notifications → Settings → Escalation Defaults | On | Whether high and critical events escalate step by step | | Overdue Escalation Ladder | Notifications → Settings | Empty | Who hears about overdue items, and when | | Enable Business Quiet Hours | Notifications → Settings | Off | Whether push, SMS and voice are held during the quiet window | | Quiet Hours Start / End | Notifications → Settings | 22:00 / 08:00 | The quiet window, in your organization's time zone | | Right to Disconnect (off-shift protection) | Notifications → Settings | Off | Holds non-urgent disruptive channels for covered workers who are off shift | | Quiet non-urgent notifications while on the floor | Each location's settings | Off | Demotes disruptive channels to in-app for people clocked in there | The master switches for email and SMS live on their own cards under **General Settings**, beside App Push Notifications. Employees manage their own settings at **Account Settings → Notifications**. They can switch channels per category, choose each category's **Email Frequency** (**Immediate**, **Daily Digest**, **Weekly Digest** or **Disabled**), pick which email address notifications go to, and add exceptions for individual categories. Browser notifications are turned on from the banner in their browser, not from this page. ## 6. More help - **Notifications FAQ** — limits, retention, suppression reasons and troubleshooting - **Communications FAQ** — Must-Read due dates, overdue Must-Reads and on-shift audiences - Ask AI — the assistant answers questions about notifications from these articles. **Keywords:** notifications, notification settings, notification channels, email notifications, push notifications, browser notifications, desktop notifications, web push, get notifications on this computer, sms notifications, voice notifications, microsoft teams notifications, notification preferences, opt out, quiet hours, right to disconnect, on floor suppression, digest, daily digest, daily email volume cap, escalation, overdue escalation ladder, overdue must-read, groups, recipient groups, on shift audience, notification logs, notification analytics, custom notification rules, not getting notifications --- # Notifications FAQ **Category:** Faq **Section:** Advanced Features **Updated:** 2026-10-16 Answers to common setup and operating questions about the platform notification system — for the admin running it. # Notifications FAQ Answers to common setup and operating questions about platform notifications. For what the system is and how to set it up from scratch, see the [Notifications Overview](/help/articles/platform_notifications). --- ## Setup ## Do I need to enable each channel separately before notifications go out on it? Yes. Master toggles for email, SMS, and push live in **Admin → General Settings** under their own settings pages (Email Settings, SMS Settings, Push Settings) — not on the Notifications page. If a channel is off there, no notification of any kind goes out on that channel regardless of per-feature toggles. In-app notifications are always on and have no master toggle. ## What roles can configure notification settings? All notification admin pages — global settings, custom rules, analytics, and logs — require the **Admin** or **Super Admin** role in the current business. Managers and employees cannot access them. The one exception is the Advanced Notification Settings view (availability, skill, and conflict checks), which any authenticated user can read but only admins can edit. ## Can I edit another employee's notification preferences? No. Each employee manages their own preferences at **Account Settings → Notifications**. There is no admin override path — admins cannot change another user's per-category or per-channel preferences anywhere in the product. --- ## Permissions and access ## Which notifications can employees not opt out of? Employees can turn off any notification type or channel in their own preferences — there are no locked checkboxes, and admins cannot lock one. A few messages are delivered whatever those preferences say, because the message itself is marked as one that must arrive: - **Emergency alerts** reach every person on the channels the alert was sent with (in-app, push, text, call), even on a channel they switched off and during their quiet hours. Email still stops if the person turned email off entirely. Reminders to acknowledge an alert follow the person's channel preferences, but they are urgent, so they come through quiet hours. - **Critical broadcasts** reach people by in-app, email, push and call on the channels the broadcast uses, whatever their preferences and quiet hours. A critical text still needs a verified phone and stops if the person turned texts off, replied STOP, or their number can't receive texts. - **Service Desk after-hours alerts** reach the agent on duty for an unclaimed ticket, and their manager if it stays unclaimed, in-app and on the push or text channels the team set. The email copy follows their email settings. - **Lone Worker SOS escalations** reach the responders by text and call whatever their preferences. - **Required emails** — password resets, sign-in codes, and notices the platform must deliver such as legal and benefits notices, signature requests and receipts — send whatever the person's preferences, unless the address or its domain is blocked, or it bounced before. Texts, push and calls still stop at a channel your organization has turned off. Push reaches a phone signed in to the mobile app, or a browser where the person turned notifications on while your organization's browser notifications are on. Broadcast texts and Lone Worker SOS texts go only to a verified phone, and calls need a verified phone only if your organization requires it. ## Who can create and delete groups? Creating, editing, and deleting groups requires the **Admin** or **Super Admin** role. System-created default groups cannot be deleted. A group something still uses cannot be deleted either — a notification rule, a broadcast, a home dashboard, a wiki page, a Communications audience, a survey, form, SOP, Training automation or onboarding template's audience, a read audience, app access, a scheduling team, an app setting such as the Speak Up adviser panel, or content it owns. Its Delete is disabled and names what uses it; change or delete that first. --- ## Day-to-day ## When do digest emails go out? Daily digests are sent at **8:20 AM UTC**. Weekly digests are sent at **8:30 AM UTC on Mondays**. These are fixed schedules. By default, admin and manager roles receive daily digests for lower-priority categories (libraries, wellness programs, company store, timekeeping, leave, onboarding, goals), while employees stay on immediate delivery. Urgent and transactional emails always deliver immediately regardless of digest cadence. ## What is the daily email cap and what happens when it's hit? Every recipient has a per-day ceiling on throttleable emails. The default is **15 emails per day** per recipient per business. Once the count is reached, further non-urgent, non-transactional emails are deferred into the digest rail rather than sent individually — nothing is lost. The cap is configurable per business via the daily email cap setting on **Admin → Notifications → Settings**. Setting it to 0 disables the throttle. ## How does escalation work? Escalation fires only for events with **high** or **critical** severity. The default three-step sequence is: step 1 sends in-app and push (waits 5 minutes), step 2 adds SMS and email (waits 10 minutes), step 3 adds voice (no further wait). Both the steps and timing are configurable per business. ## What does "Right to Disconnect" actually suppress? When enabled at **Admin → General Settings**, it suppresses push, SMS, and voice for **covered workers** (frontline, hybrid, non-exempt, or hourly) who are **off shift** (no open attendance record, no current shift assignment). In-app and email still land. Urgent and mandatory dispatches (critical broadcasts, emergency alerts) bypass the suppression. Employees have no toggle — this is entirely business-controlled. Default: **off**. ## What does on-floor suppression do? When a location has **Quiet non-urgent notifications while on the floor** turned on, workers clocked in at that location have push, SMS, and voice notifications demoted to in-app only. Email still lands. This is for environments where phone use is restricted. The toggle is per-location, set by anyone who can edit the location (admins, or managers with location-edit permission). Default: **off**. --- ## When something looks wrong ## "I sent a notification but the employee says they never got it" Check **Admin → Notifications → Logs**. Each log entry shows whether the notification was delivered or blocked, and blocked entries include the specific reason. There are 13 suppression reasons, worded in the log as: the recipient's email address is blocked after a previous bounce; the recipient disabled that channel entirely; blocked by system-level settings; the channel is disabled at the business level; that notification type is disabled in business or app settings; blocked by a custom notification rule; disabled in the recipient's notification preferences; the recipient opted out of that category on that channel; blocked by notification settings; the recipient does not belong to this business; the source record is sample or demo data; suppressed during a historical data import; and quiet hours. Suppression records are retained for **90 days**. ## "An employee's email stopped working — they get nothing" The most likely cause is an auto-block from bounces. After a soft bounce retries **3 times** (with exponential backoff) and still fails, the system escalates to a hard bounce: the email address is added to the global blocked list and the user's email channel is disabled. Check **Admin → Notifications → Analytics** where you can clear soft-bounce flags and re-enable a user's email delivery. For SMS, a number the carrier reports as invalid, not mobile, unknown or a landline is blocked: no texts go to it, but the person's own SMS setting is left alone. An admin can lift the block with **Enable SMS** (or **Unblock Number**) on **Admin → Notifications → Analytics**. ## "Voice calls aren't going through at night" Voice calls have their own quiet-hours window: **9 PM to 8 AM** in the user's timezone. Non-urgent calls are rescheduled to 8 AM. After **5 reschedule attempts**, the call executes regardless. Urgent calls bypass voice quiet hours entirely. Additionally, the platform limits concurrent voice calls to **10 globally** — if all slots are busy, calls queue and run as slots free up. ## "Notifications are coming through even though quiet hours are on" Business-level quiet hours (default **10 PM to 8 AM**) only suppress **disruptive channels**: push, SMS, and voice. In-app notifications always land, and email cadence is handled by the digest system, not quiet hours. Urgent notifications — emergency alerts and the reminders to acknowledge them among them — go through quiet hours. Emergency alerts, critical broadcasts, Service Desk after-hours alerts and Lone Worker SOS escalations also skip quiet hours on the channels they were sent with. ## "We're running out of credits for texts" Texts draw on your organisation's one platform credit balance — **3 credits** per text message, the same balance AI, voice and metered apps use. See the balance, and buy a credit pack, on **Admin → General Settings → Billing & Payments → Credits**; admins are warned when the balance drops below **500 credits** by default. Check how many texts you are sending at **Admin → Notifications → Analytics**. SMS also has a per-business **daily limit** and **monthly limit**, which an admin sets on **Admin → General Settings → SMS Settings** up to the maximum set for your organization (contact MangoApps support to go higher). Once either is reached, texts stop for the rest of that day or month — except life-safety texts (Lone Worker SOS, missed check-ins, emergency alerts), which still go out and are billed as usual, and sign-in codes, which no limit stops. Two more settings apply only to some texts: the optional **per-recipient daily limit** holds back automatic recruiting texts (interview and offer reminders, recruiting alerts) once a candidate's number has had that many texts in a day — every text to the number counts toward it — and **domestic numbers only** covers texts to job candidates (automatic and sent by a recruiter) and cards shared by text. Shift reminders, broadcasts and other notification texts are not held to either. Alert SMS bodies are truncated to **320 characters** (~2 segments). Critical broadcasts can span up to **10 segments** (1,530 characters). --- ## Retention and limits ## How long are notifications kept? In-app notifications are **archived after 30 days** (read or unread) and **permanently deleted after 90 days** from archival. Notification suppression records (the log of why a notification was blocked) are retained for **90 days**. Broadcast ledger records (audience snapshots, delivery states, acknowledgements) are retained for **7 years** after a broadcast is archived. ## Are there limits on push notification size? Yes. FCM push payloads are limited to **4,096 bytes** (4 KB) — this is an FCM/APNs platform limit. Title and body are trimmed to fit. Push messages for offline Android devices are queued for up to **28 days**. In-app notifications are bulk-inserted in batches of 1,000. --- ## More help - [Notifications Overview](/help/articles/platform_notifications) - Ask AI — the assistant answers notification questions from these articles. **Keywords:** faq, notifications, quiet hours, emergency alerts, suppression, bounce, sms limits, escalation, digest, opt out, right to disconnect, on floor suppression, notification logs, recipient groups, voice notifications, notification retention --- # Offboarding App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-20 How to set up and run structured employee exits — plans, resignations, access revocation, exit interviews, knowledge transfer, and group terminations. # Offboarding ## 1. What it is Offboarding manages the full employee exit process — from the moment someone resigns or is terminated through access revocation, knowledge transfer, and post-separation document access. It replaces ad-hoc checklists with a tracked plan of tasks, documents, and compliance milestones. - **Enablement:** Offboarding requires a license. An administrator enables it from Admin → Apps → All Apps. - **What it is not:** Offboarding does not handle day-to-day HR records or org-chart changes. Those live in the People app. Offboarding only takes over once a departure is confirmed. ## 2. Standing it up 1. Go to **Apps → Offboarding → Settings**. 2. Set the **Default Notice Period for HR-Created Plans** (default: 14 days). This is the number of days added to today's date to pre-fill the termination date on **New Offboarding Plan**. The notice an employee must give when they resign is a different setting, **Default Minimum Notice Period**, which notice-period policies can override. 3. Decide whether to **Require exit interview** and **Require knowledge transfer** on plan completion. Both default to On — a plan cannot be marked complete until these are submitted. 4. Choose the **Resignation approval levels** (default: 2 — Manager then HR). This controls how many approvals a self-service resignation passes through before an offboarding plan is created. 5. Optionally choose a **Primary HR approver** (and backups). Anyone with an HR designation, Admin or Super Admin role can approve at the HR stage; the primary and backup approvers only decide who is notified first. 6. Go to **Apps → Offboarding → Templates** and create at least one offboarding template. A template defines the tasks and documents that are auto-generated when a plan is created from it. Without a template, the system generates a default task set based on the plan type. 7. Optionally create **Exit interview templates** and **Knowledge transfer templates** from the same Templates page. These define the questions and sections that appear when the departing employee completes those steps. 8. Grant access: admins, super admins and people whose organizational role is flagged as HR staff see every plan; managers see the plans of people in their reporting line. You can also make someone an **Offboarding app admin or contributor** from the app's **Admins & Contributors** panel in **Admin → Apps**, which lets them work every plan without changing their org-wide role. Group terminations, WARN notices and separation agreements stay with admins, super admins and HR. You don't need an exit interview template before you require exit interviews. With none set up, the departing employee answers the app's built-in questions — their reason for leaving, a few satisfaction ratings and whether they would recommend you as a place to work. Create a template when you want to ask your own. ## 3. How it fits together ### Plans, templates, and tasks An **offboarding plan** is the central record for one employee's departure. Every plan has a type, a termination date, a last working day, and a status that moves through Draft → Active → Completed (or Cancelled). A **template** pre-defines the tasks and documents that a plan should contain. When you create a plan from a template, the system copies the template's task and document definitions into the plan. Each task has a department (IT, HR, Manager, Payroll, Legal, Finance, Facilities, Operations), a day offset relative to the termination date, and a priority (Critical, High, Medium, Low). If no template is selected, the system generates default tasks based on the plan type. For example, a Voluntary plan gets seven tasks including "Schedule exit interview", "Knowledge transfer session", "Collect company equipment", and "Process final paycheck". An Involuntary plan begins with "Immediate access revocation" and also includes "Document termination reason" and "Review separation agreement". **Example:** You create a "Standard Voluntary Exit" template with 12 tasks across IT, HR, and Manager departments. An employee resigns, their manager approves, and the system auto-creates a plan from this template. Each task appears with a due date calculated from the termination date — "Revoke system access" on day 0, "Send COBRA notice" on day +1, "Knowledge transfer session" on day −7. ### Plan types Every plan is one of five types: **Voluntary**, **Involuntary**, **Retirement**, **End of Contract**, or **Layoff**. The type determines which default tasks are generated (when no template is used) and how the plan appears in analytics. One employee can have only one active or draft plan at a time. ### Resignations An employee can submit a resignation directly from the app. The request routes through a configurable approval chain of 1 to 3 levels: Manager only, Manager then HR, or Manager then Department Head then HR. Notice period policies can vary by country, region, and employee type — the system finds the most specific matching policy and calculates the last working day from it. When a resignation is fully approved, the system can **automatically create an offboarding plan** if that setting is enabled (default: On). The plan inherits the resignation's dates, manager, and type, is built from one of your active offboarding templates where you have one, and is created as a **Draft** — the employee does not see the plan until HR reviews it and clicks **Start**. ### Access revocation and SLA enforcement HR or IT can revoke access by hand from a plan's **Access Revocation** page. It lists IT systems, physical access, and equipment (the employee's assigned Asset Pro assets when Asset Pro is enabled), and three confirmation checkboxes — one per checklist — must all be ticked before the revocation is recorded. With **Auto-Revoke Access on Last Working Day** on (default: On), a daily job does the same for every active plan whose access is not yet revoked once its last working day has ended in your company's time zone — access goes at the first daily run (06:00 UTC) after the close of business that day — catching up plans from the previous 14 days if a run was missed. Revoking deactivates the employee's membership in your organization, ends their sessions, and hands what they own to a surviving owner where those apps are enabled — Password Manager vaults, Contracts, Workspaces, Sites and more. It cannot be undone from the product. When a plan is started, the system also sets a **secondary SLA**: end of business day one business day after the termination date. A plan whose required tasks are still incomplete at that point is marked as breached and escalated (see the Offboarding FAQ). Plans created from a termination in a connected HRIS (the Merge.dev webhook) also get a **primary SLA** — end of business day on the termination date, or 4 hours after the termination was logged if that was later. When it passes, the daily job disables the employee's account in each identity provider you switched on under **Automated Deprovisioning** in Settings (Okta, Azure AD, Google Workspace), and after that succeeds reclaims their Slack seat if **SaaS License Reclamation** is on. Plans created any other way do not get a primary SLA, so this outbound deprovisioning does not run for them — disable those accounts in your identity provider yourself; the Access Revocation checklist lists them. ### Exit interviews and knowledge transfer Both can be required organization-wide from Settings (both default to required). An exit interview uses a template of structured questions (rating scales, NPS, single and multiple choice, yes/no, open text), or the built-in questions when no template applies. Its answers are attributed, not anonymous: the employee, HR and administrators can read them; a manager who is not an administrator or in HR sees only that the step is done. For anonymous feedback, Settings can also send leavers an **Anonymous Exit Survey** from the Surveys app, read there only once enough people have answered. Knowledge transfer uses a template of sections where the departing employee documents their responsibilities, processes, and contacts. Plans cannot be marked complete until both are submitted — if required. An exit interview can also be scheduled for a specific date, and the employee receives an Inbox notification to complete it. When the departing employee submits knowledge transfer, the successor named on it is notified by email and in-app. With **Offer "Talk it through"** on in Settings, the departing employee can also hold their exit interview as a short conversation with an AI interviewer instead of filling in the form — see "What is Talk it through" in the Offboarding FAQ. ### Group terminations and WARN compliance Group terminations manage layoffs that affect multiple employees. They track WARN Act applicability, required notice periods, the decisional unit, and age demographics for OWBPA compliance. A new group termination's effective date defaults to 60 days out. From a group termination you create its WARN notices (plant closing, mass layoff, or relocation), each with employee, union, and state-agency versions; separation agreements are created on each employee's plan and linked to the group. Group terminations are restricted to admins, super admins, and HR — managers and Offboarding app admins cannot access them. ### Separation agreements A separation agreement is a legal document attached to an offboarding plan. It is created through a guided wizard that pre-populates employee information from the plan. For employees 40 or older they apply ADEA/OWBPA consideration periods (21 days for an individual, 45 days for a group termination) and a 7-day revocation period. There is no e-signature delivery yet: send the agreement to the employee yourself, then click **Mark as Sent** to record it. Separation agreements are restricted to the same HR-sensitive access level as group terminations. ### Former Employee Portal After the employee has left, the **Former Employee Portal** gives them a place to retrieve their pay stubs, tax forms, HR documents, and experience letters. It is switched on in **Admin → People → Settings** (Former employees), where you also set how many years access lasts after the termination date (default: 7). When a plan is completed and the employee has a personal email on file (different from their work email), they are granted portal access and emailed a link to it (unless **Auto-Send Portal Access on Termination** is off). They sign in with a one-time token sent to their personal email or phone. If **Require Personal Email During Offboarding** is on, the plan cannot be completed until HR verifies the personal email. HR can also send a token by email or SMS from the plan's **Former Employee Portal Access** card once the employee has been terminated. A token goes only to an email or phone number that was on file when the employee left, or that HR has verified on their offboarding plan since. If the address or number changed after they left — for example, another organization they still work for edited it — no token is sent to it until you verify it on the plan. The plan verifies the personal email and the personal phone; a work or home phone that changed after they left is never used. ## 4. Running it ### Creating an offboarding plan manually 1. Go to **Apps → Offboarding → Plans → New Plan**. 2. Select the employee, their manager, and a plan type. 3. Choose a template (or leave blank for default tasks). 4. Set the termination date and last working day. 5. The plan is created in **Draft** status. Review the generated tasks and documents. 6. Click **Start** to move it to **Active**. This sends notifications (to the manager, HR, and employee, based on Settings) and syncs the termination date to the employee record. ### Processing a resignation 1. Go to **Apps → Offboarding → Resignations** to see pending requests. 2. Review the request — check the intended last day, notice period, and reason. 3. Approve or reject. If the approval chain has more levels, the request advances to the next approver. 4. On final approval, an offboarding plan is auto-created (if enabled in Settings). ### Completing an offboarding plan 1. Work through each task — mark as completed, started, or skipped. 2. If required, have the employee complete their exit interview and knowledge transfer. 3. If **Require Personal Email During Offboarding** is on, verify the employee's personal email. 4. Once all required items are done, click **Complete**. The system deactivates the employee and revokes their remaining access, ends their benefit enrollments and opens COBRA eligibility (if Benefits Management is enabled), pays out banked time where your policy pays out on termination, and — if they have a personal email on file — grants Former Employee Portal access and emails them about it. ### Reviewing analytics Go to **Apps → Offboarding → Analytics**. The dashboard shows total exits, turnover rate, voluntary exits, and average tenure; exit trends and the voluntary vs involuntary split; rehire eligibility; knowledge transfer, final document and equipment return rates; exit reasons and exit interview insights — filterable to the last 7, 30 or 90 days or the last year. Exits by department are in the CSV export. ### Exporting a plan From any plan detail page, export as PDF or CSV for compliance records. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Default notice period for HR-created plans | Settings | 14 days | Days added to today to pre-fill the termination date on New Offboarding Plan | | Require exit interview | Settings | On | Plans cannot be completed until the exit interview is submitted | | Require knowledge transfer | Settings | On | Plans cannot be completed until knowledge transfer is submitted | | Request exit interview during resignation | Settings | Off | Pre-ticks "I would like to schedule an exit interview" on the employee's resignation form | | Auto-create offboarding plan | Settings | On | Whether an approved resignation automatically generates a plan | | Auto-revoke access on last working day | Settings | On | Whether the daily job revokes access once the last working day has ended in your company's time zone (cannot be undone from the product) | | Anonymous exit survey | Settings | None | An anonymous Surveys app survey sent to leavers when their plan starts (needs the Surveys app) | | Offer "Talk it through" | Settings | Off | Whether departing employees on voluntary, retirement and end-of-contract plans may hold their exit interview as a conversation with an AI interviewer (HR can offer it on other plans, or keep a plan to the form, from the plan page) | | Let leavers talk it through out loud | Settings | Off | Whether "Talk it through" also offers a live voice call, using your organization's voice minutes | | Notify manager | Settings | On | Send notifications to the plan's manager on plan events | | Notify HR | Settings | On | Send notifications to HR staff on plan events | | Notify employee | Settings | On | Send notifications to the departing employee on plan events | | Resignation approval levels | Settings | 2 | Number of approval levels: 1 (Manager), 2 (Manager → HR), or 3 (Manager → Dept Head → HR) | | Default minimum notice period | Settings | 14 days | Notice an employee must give when no notice-period policy matches them | | AI agent | Settings | On | Whether the Offboarding Ask AI agent is available | | Primary and backup HR approvers | Settings | None | Who is notified first at the HR approval stage (anyone with an HR designation, Admin or Super Admin role can still approve) | | Default template | Settings | None | Template pre-selected on New Offboarding Plan | | Notice period policies | Settings → Notice Period Policies | (none) | Per-country, per-region, and per-employee-type overrides for the notice period | ## 6. More help - **Offboarding FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about Offboarding from these articles. **Keywords:** offboarding, employee exit, termination, resignation, exit interview, knowledge transfer, access revocation, last working day, COBRA, separation agreement, group termination, WARN notice, notice period, former employee portal --- # Offboarding FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-14 Answers to common setup and operating questions about Offboarding — resignations, plans, access revocation, exit interviews, knowledge transfer, separation agreements, and compliance. # Offboarding FAQ Answers to common setup and operating questions about Offboarding. For what the app is and how to set it up from scratch, see the [Offboarding Overview](/help/articles/offboarding_app_overview). --- ## Setup ## Do I need to create templates before I can start an offboarding plan? No. When you create a plan without selecting a template, the system generates a default task checklist based on the plan type you choose — voluntary, involuntary, retirement, end of contract, or layoff. Each type produces different tasks with appropriate departments and priorities. Templates let you standardize and reuse a checklist across departures — you can keep separate templates per exit type, label them by role level (entry, mid, senior, executive), and assign each task to a department — but they are not required. HR picks the template when creating a plan. ## What are the default configuration settings? Until you change them in **Settings**, these defaults apply: - **Default notice period for HR-created plans:** 14 days - **Default minimum notice period (resignations):** 14 days - **Resignation approval levels:** 2 (Manager then HR) - **Require exit interview to complete a plan:** Yes - **Require knowledge transfer to complete a plan:** Yes - **Auto-create offboarding plan on resignation approval:** Yes - **Auto-revoke access on last working day:** Yes - **Request exit interview during resignation:** No - **Offer "Talk it through":** No - **Notifications to manager, HR, and employee:** All on - **Ask AI agent:** Enabled --- ## Permissions and access ## Who can see and manage offboarding plans? There are two levels of access: 1. **Full access** — admins, super admins, Offboarding app admins and contributors, and anyone with an HR designation (an organizational role flagged as HR staff). They see every plan in the business. 2. **Manager access** — managers see only plans for employees they manage (direct reports and anyone within their reporting-structure reach). They cannot see plans for employees outside their chain. Nobody sees their own plan while it is still a draft. Group Terminations, Separation Agreements, and WARN Notices are restricted further: only admins, super admins, and users with an HR designation can access those tabs — not managers, and not Offboarding app admins. ## I can't find the Offboarding app in my app directory — is it missing? It is hidden on purpose. The app only appears for people who manage offboarding (admins, managers, HR, app admins and contributors), for employees whose own offboarding plan has been started or whose resignation is pending or approved, for anyone asked to approve a resignation, and for anyone with an open task on a started plan. If none of these applies to you, the tile will not show in your directory. --- ## Resignations ## How does the resignation approval flow work? An employee submits a resignation through self-service. The request routes through 1, 2, or 3 approval levels depending on your configuration: 1. **1 level:** Manager only — manager approval finalizes. 2. **2 levels (default):** Manager then HR. 3. **3 levels:** Manager, then Department Head, then HR. At each level, admins and super admins can approve, and anyone with an HR designation can approve at the HR level — but nobody can approve their own resignation. If the direct manager is on approved leave, the skip-level manager (manager's manager) can approve in their place. Once the final level approves, the employee is notified by email and in-app, and the system auto-creates an offboarding plan (if that setting is on) as a **Draft** for HR to review and start. ## Can an employee withdraw a resignation? Yes, as long as the request is still pending — it has not yet been approved or rejected. Once approved, the employee cannot withdraw it. When it is withdrawn, the person it was waiting on, anyone who already approved it, and the employee's manager are notified, with the reason the employee gave. If an employee decides to stay after their resignation was approved, HR or an admin can **Rescind** it from the resignation's page: cancel the offboarding plan first, then give a reason. The request is marked withdrawn with "Rescinded by HR" and the reason on its timeline, the employee is told in the app, and they can resign again later if they need to. ## I submitted my resignation but it says I need more notice — what happened? The system calculates a minimum notice period based on your country, region, and employee type. Notice-period policies are matched from most to least specific: an exact country + region + employee-type match wins, then progressively broader matches, down to the **Default Minimum Notice Period** in Settings (14 days unless changed). If your intended last day is before the calculated date, tick **I would like to request a different last working day** on the resignation form. Your approvers then see the difference and decide whether to accept it. --- ## Plans and tasks ## Can an employee have more than one active offboarding plan? No. Each employee can have at most one plan in **Draft** or **Active** status. You must complete or cancel the existing plan before creating another. The same restriction applies to resignation requests — an employee cannot submit a new one while a pending or approved request exists, or once HR has started an offboarding plan for them. ## What happens when a plan is completed? Only an active plan can be completed. Completing it triggers several actions in sequence: 1. If Benefits Management is enabled, benefit enrollments are terminated and COBRA eligibility is opened. 2. The employee's termination date is recorded and their membership in your organization is deactivated, ending their access. (Their login stays active only if they still belong to another organization.) 3. Banked-time payout is triggered if the business has an auto-payout-on-termination policy. 4. If the employee has a personal email on file, Former Employee Portal access is granted and a portal-access email is sent (unless **Auto-Send Portal Access on Termination** is off in Admin → People → Settings). If **Require Personal Email During Offboarding** is on in those settings, the plan cannot be completed until HR verifies the employee's personal email. ## How is the completion percentage calculated? The percentage counts all required items: required tasks, required documents, plus the exit interview and knowledge transfer if those are marked as required on the plan. A required task counts once it is completed or skipped, a required document once it is verified (an uploaded but unverified document counts as three-quarters of an item), and the exit interview and knowledge transfer each count as one item. The plan reaches 100% only when every required item is done. --- ## Exit interviews and knowledge transfer ## What question types are available in exit-interview templates? Seven types: **text**, **textarea** (free-form), **rating** (1–5 scale by default), **NPS** (0–10 scale), **select** (single choice), **multiselect**, and **boolean** (yes/no). Rating and NPS questions auto-set a scale if you do not specify one. Select and multiselect require at least one option. ## My exit interview was submitted — why doesn't the successor see it? The successor is notified when *knowledge transfer* is submitted, not when the exit interview is submitted. The exit interview is an HR-facing instrument — its NPS score and summary are stored on the plan for HR to review. Knowledge transfer is the employee-to-successor handover: the successor receives an email and an in-app notification once the departing employee submits it. ## What is "Talk it through" for exit interviews? "Talk it through" lets the departing employee hold their exit interview as a short conversation with an AI interviewer instead of filling in the form. They type, or hold to talk (and, with **Let leavers talk it through out loud** on, can also talk live), and the interviewer asks the plan's exit interview questions one at a time. At the end they see what will be recorded, can change it or remove any answer that isn't required, and send it — what they send becomes their exit interview, exactly as if they had filled in the form. - **Off by default.** An admin turns it on with **Offer "Talk it through"** in Settings. It is then offered on voluntary, retirement and end-of-contract plans; from a plan's page, HR can offer it on another plan or keep one plan to the form. It is always optional — the form is one click away. - **When the employee gets the form instead.** While your organization's AI is unavailable, once the employee has used their monthly AI allowance, or when the plan's questions can't run as a conversation. The plan page says which. - **Who sees what.** The conversation itself is visible only to the employee. HR and administrators receive the answers the employee approves, attached to their offboarding record — not anonymous. Their manager sees that the step is done, not what was said, unless the manager is an administrator or in HR. - **Sending it.** Nothing is sent until the employee sends it. When **Auto-Revoke Access on Last Working Day** is on, their access ends once their last working day has ended in your company's time zone (at the next daily run, 06:00 UTC), so a conversation they haven't sent before then can't be sent; the conversation page names the day for them. An unsent conversation is deleted 30 days after they last answered. - **Reading it back.** After sending, the employee can read the conversation back from their exit interview page for 30 days, while they can still sign in. The answers they approved stay on the plan. - **Trying it.** HR can try the conversation from Settings or from an exit interview template — a rehearsal that is never counted and is deleted the next day. ## What are the default knowledge-transfer sections? Eight sections ship by default: **Key Responsibilities**, **Critical Processes**, **Systems & Tools**, **Key Contacts**, **Ongoing Projects**, **Tribal Knowledge**, **Documentation & Files**, and **Recommendations**. The first five plus Documentation & Files are required; Tribal Knowledge and Recommendations are optional. You can create custom templates with different sections. --- ## Access revocation and deprovisioning ## What does the termination SLA track? Two SLA targets, and which plans get them: - **Secondary SLA** — set on every plan you start with a termination date: end of business day one business day after the termination date. This is the deadline for all remaining required tasks. - **Primary SLA** — set only on plans created from a termination in a connected HRIS: end of business day on the termination date, or 4 hours after the termination was logged if that was later. When it passes, the daily job disables the employee's account in each identity provider you switched on under **Automated Deprovisioning** (Okta, Azure AD, Google Workspace). Plans started any other way get no primary SLA and no outbound identity-provider deprovisioning — disable the person's accounts in your identity provider yourself. Both deadlines use holiday-aware business-day math. Progress and breaches are recorded in an append-only audit log on the plan. ## What happens when the SLA is breached? A plan past its secondary SLA with required tasks still open is marked as breached. A daily escalation sweep runs at 09:00 UTC and notifies in tiers: - **At breach:** the plan's manager is notified. - **24 hours past the secondary SLA:** manager and HR are notified. - **48 hours onward:** manager, HR, super admins (executives), and the manager's own manager are notified. Each tier transition is recorded in the plan's audit log. After the top tier, reminders repeat at growing intervals and stop 30 days after the secondary SLA, so an abandoned plan does not email people forever. --- ## Compliance and legal ## How does COBRA tracking work? COBRA runs in Benefits Management. When you complete an offboarding plan with Benefits Management enabled, the person's benefit enrollments end and Benefits Management opens a COBRA eligibility record, for admin review, for each medical, dental, vision or FSA enrollment that ended, with the qualifying event date and type. Coverage duration is set automatically: **18 months** for the employee's own qualifying events (termination or reduction in hours), **36 months** for dependent events like divorce, death of the covered employee, or loss of dependent status. An admin generates the election notice in Benefits Management; the election deadline is **60 days** from when the notice is marked sent. An administrative fee of up to **2%** (the federal cap) can be applied. ## What ADEA/OWBPA rules apply to separation agreements? When the departing employee is 40 or older, the system automatically adjusts the separation agreement: - **Individual termination:** 21-day consideration period, 7-day revocation period. - **Group termination:** 45-day consideration period, 7-day revocation period. For employees under 40, the consideration period defaults to 21 days with no mandatory revocation period. California's rules are applied automatically: the non-compete is left out (an agreement that still carries one says it is not enforceable in California under SB 699), and the release carries a Civil Code § 1542 waiver. Every other US state gets a default 12-month non-compete, which you can change in the wizard — check that state's limits (Illinois, for example, sets an earnings threshold the system does not check) with counsel before you send it. ## What WARN notice types are supported? Three types: **plant closing**, **mass layoff**, and **relocation**. The federal threshold is 50 employees for a plant closing and 500 for a mass layoff (or 50–499 if that is 33% or more of the workforce). The federal minimum notice is 60 days. State-level WARN rules are also tracked. For example, California and Maryland require 60 days at 50 employees; New York and New Jersey require 90 days (at 50 and 100 employees respectively); Illinois requires 60 days at 75 employees. --- ## Licensing and limits ## Does Offboarding require a licence? Yes. Offboarding requires a licence and is disabled by default. An administrator enables it from Admin → Apps → All Apps. It is not auto-enabled for any tenant. ## Are there limits I should know about? - **Bulk CSV import:** maximum file size is **5 MB** and at most **5,000 rows**. Files over 100 rows are processed as a background job. Required columns: employee email, plan type, and last working day. - **Offboarding template duration:** 1–365 days. - **Notice-period policies:** each policy must target at least one criterion (country, region, or employee type). Notice period range: 1–365 days. - **Approval levels:** 1–3 (manager only, manager + HR, or manager + department head + HR). - **Plans per employee:** one active or draft plan at a time. --- ## More help - [Offboarding Overview](/help/articles/offboarding_app_overview) - Ask AI — the assistant answers Offboarding questions from these articles. **Keywords:** faq, offboarding, resignation, termination, exit interview, talk it through, knowledge transfer, separation agreement, WARN notice, COBRA, access revocation, deprovisioning, notice period, SLA, offboarding plan, group termination, severance --- # Offer Manager App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run Offer Manager — creating, approving, sending, and tracking offer letters with e-signature and negotiation support. # Offer Manager ## 1. What it is Offer Manager handles the full lifecycle of an employment offer: drafting the letter, routing it through internal approval, sending it to the candidate, tracking negotiation rounds, collecting an e-signature, and handing the accepted hire to Onboarding Hub. It connects Job Board candidates to offer letters and keeps compensation decisions auditable from draft to signature. - **Enablement:** Offer Manager requires a license. An admin enables it in Admin → Apps → All Apps; it is off by default. - **What it is not:** Offer Manager is not the recruiting analytics dashboard. Aggregate hiring metrics, pipeline charts, and cross-app reporting live in Talent Hub. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Offer Manager**. 2. Go to **Offer Manager → Settings** and review the default toggles. All features — Approval Workflows, Offer Templates, AI Offer Generation, Market Analysis, Offer Analytics, Compensation Benchmarks, and E-Signature Integration — default to **On**. 3. If you will use e-signature, enable either the **E-Signature** app (built-in signing) or configure an external provider (DocuSign or HelloSign — the two Offer Manager can send through) in **Admin → Organization → Integrations → E-Signature**. Then confirm the **E-Signature Integration** toggle is on in Offer Manager Settings. 4. To route offers to more approvers than the job's hiring manager, go to **Offer Manager → Approval Workflows** and create at least one workflow with conditions and approval levels — for example, a workflow with a salary condition that adds a finance approver for larger offers. Without a matching workflow, the job's hiring manager approves the offer. 5. Create at least one offer template under **Offer Manager → Templates**. Templates carry default compensation ranges, benefits and the offer letter. Without a template, recruiters author every letter from scratch. 6. Grant access to the recruiting team. Business admins and Offer Manager app admins manage settings, templates and workflows. Offers are created by the recruiting function (business admins, HR admins, Offer Manager app admins), Offer Manager contributors, the recruiter of a job, and whoever added the candidate. A job's hiring manager can see, withdraw and reopen its offers and approves them, but does not create or send them. **What silently does nothing until paired:** enabling e-signature integration in Settings has no effect unless either the E-Signature app is enabled or an external provider is configured in Admin → Organization → Integrations. The setting is a per-app gate on top of the provider. ## 3. How it fits together ### Offer lifecycle An offer moves through a fixed sequence of statuses: **Draft → Pending Approval → Approved → Sent → Accepted** (or **Rejected** / **Withdrawn** at several points). At any point from Sent onward, the candidate can counter-offer, which moves the status to **Negotiating**. Once a negotiated or sent offer is accepted and the candidate is marked as Hired, the status becomes **Ready for Onboarding**. Example: a recruiter drafts an offer for a Senior Engineer at $140,000 base plus $15,000 signing bonus. They submit it for approval. The approval workflow matches on salary range and routes it to the VP of Engineering (level 1) then the CFO (level 2), beside the job's hiring manager. All approve. The recruiter sends the offer. The candidate counters at $150,000 base. The recruiter records a company response at $145,000 and marks it as the final offer. The candidate accepts via the portal and signs the letter, whose signature request went out with the offer. The signed PDF syncs to HR Files. ### Who approves an offer **Approval workflows** are condition-based templates that an admin creates under Offer Manager → Approval Workflows. Each workflow defines conditions (salary range, department, location, job level, employment type) and one or more approval levels. When an offer is submitted, the most specific active workflow whose conditions match is used: workflows with conditions are checked before catch-all ones, the default wins among equals, then name order. If none match, the default workflow (if set) applies. Workflows support sequential approval (level 1 must approve before level 2), delegation, and a configurable timeout. **The job's hiring manager** is added as an approver on every submitted offer, beside any workflow's approvers — unless they created the offer. When no workflow matches, the hiring manager is the approver. If nobody can approve the offer (no matching workflow and no hiring manager on the job), submitting is refused with the reason, and the offer stays a draft. **Who approves** is who the offer's workflow and its job name — not a role. A super admin approves only an older offer that has no approval rows, and Offer Manager admins (business admins and Offer Manager app admins) can always use **Override Status** on the offer page. With **Require a separate approver** on (the default), nobody approves an offer they created. **With Approval Workflows turned off** in Settings, offers skip internal approval: submitting an offer approves it at once. ### Candidate portal When an offer is sent, the candidate receives a secure link to a branded portal page. There they can view the full offer, accept it, decline it, or submit a counter-offer (if negotiation is enabled). The portal is public — no account required. The link is tied to the candidate record and works for every offer sent to that candidate. ### Negotiation Negotiation is controlled by the **Maximum Counter-Offer Rounds** setting (default: **1 Round**). Each round is one candidate counter followed by one company response. The admin can set it to **No Negotiation Allowed** (candidate can only accept or decline), any number up to **5 Rounds**, or **10 Rounds (Maximum)**. The recruiter can also mark a company response as the **Final Offer**, which blocks further counter-offers from the candidate. ### Offer visibility By default, only the recruiting function (admins, HR admins, and Offer Manager app-admins) sees every offer. Everyone else sees only offers they created, offers for jobs they recruit or hiring-manage, or offers where they are a named approver. The **Who can see all offers?** setting in Offer Manager Settings can widen this to everyone with app access, or to specific people. ### E-signature flow When e-signature is enabled and a provider is configured, the recruiter can send an approved offer letter for signature. If **Request Signature When Sent** is on in Settings (the default), the signature request goes out with the offer; when it is off, the request goes out when the candidate accepts. The system tracks the signature status — Not Sent, Awaiting Signature, Viewed, Signed, Declined, or Expired. When the candidate signs, the signed PDF is cached and, if HR File Manager is enabled, synced to the employee's HR file. ### Offer templates Templates are reusable blueprints for offer letters. Each template carries a role level (Entry Level, Mid Level, Senior Level, or Executive), optional department and country/state targeting, a default compensation range, a default benefits package, and approval rules. When a recruiter selects a template while creating an offer, the compensation and letter content are pre-populated. Templates can be authored in two modes: **Simple** (a single rich-text offer letter body) or **Sections** (multiple named sections that are assembled into one letter, each optionally linked to an e-signature template for multi-document signing packets). In Sections mode the sections follow one another in the letter; add a **Page Break** section where the next one should start on a new page of the signed PDF. A section linked to an e-signature template always starts its own page. Templates can also be imported from the central template library or drafted by AI from a description (**Draft template with AI**, when AI Offer Generation is on). A candidate's offer letter is filled in from the template's placeholders, not written by AI. A template cannot be deleted if any offers reference it; it can only be deactivated. ### Compensation validation The offer form validates that the base salary and total compensation do not exceed the position's posted maximum salary. This check runs when the offer is submitted for approval (not while it is a draft). Negotiated offers that land above the original range are exempted — negotiation is the explicit mechanism for exceeding the band. ### HR Files sync When a signed offer document is received (e-signature status becomes Signed), the PDF is cached and — if HR File Manager is enabled with recruiting as a sync source — automatically filed in the employee's HR records. This happens in the background; no manual upload is required. ### Calendar integration Offer events (response deadlines, start dates, and negotiation deadlines) are projected to the Calendar Hub automatically. Events are created when an offer is saved and removed when it is withdrawn or deleted. ### Mobile Phone-sized browsers and the native app are automatically redirected to the mobile-optimized views for the dashboard, offer detail, and internal approvals pages. Tablets stay on the desktop view. A user can opt out with the `?desktop=1` query parameter. ## 4. Running it ### Creating an offer 1. Go to **Offer Manager → Offers** and click **Create Offer**. 2. Select a candidate (only candidates whose status is **Interviewed** with a completed interview, or **Ready for Offer**, appear in the dropdown). Candidates who already have an open offer — a draft, or one pending approval, approved, sent or in negotiation — are excluded. 3. Select a job and optionally choose a template to pre-fill compensation and letter content. 4. Enter the compensation package: base salary, bonus, signing bonus, and equity percentage. 5. Set the start date and offer expiration date. 6. Save as draft or submit for approval. ### Reviewing and approving 1. Go to **Offer Manager → Internal Approvals** to see offers awaiting your approval. 2. Approve or reject individually (a rejection needs a reason, which the recruiter sees), or select multiple offers and click **Approve Selected**. Each offer is re-checked server-side — offers you lack permission to approve are skipped. 3. If approval workflows are configured with sequential levels, earlier levels must approve before later levels can act. The tab badge shows the count of offers you can act on now — for the recruiting function it counts the whole pipeline's pending approvals. ### Sending and tracking 1. Once approved, open the offer and click **Send offer**. The candidate receives an email with a portal link. 2. From the offer detail page, you can send reminders, add internal notes, extend the expiration date, or withdraw the offer. 3. If the candidate counters, record the company response and optionally mark it as the **Final Offer**. ### Post-acceptance checklist After a candidate accepts, the offer detail page shows the next step: 1. **Mark as hired** — updates the candidate's status. 2. **Start date** — edit it with the pencil beside the start date to record the agreed day. 3. **Notify Hiring Manager** (in the offer's actions menu) — sends the job's hiring manager an in-app notification and, when they have an email address, an email. 4. **Set up onboarding** — when the Onboarding Hub app is enabled, opens a new onboarding plan for the hire. When it is not, the page asks you to enable Onboarding Hub; Offer Manager does not create a plan on its own. ### Delegating approvals Any approver can delegate their pending offer approvals to a colleague while out of office. Go to **Offer Manager → Internal Approvals**, click **Delegate approvals**, choose a delegate, and set a date range. The delegation is additive — the original approver keeps access, and the delegate can see and act on the delegator's assigned approvals. Only one delegation can be active at a time. ## 5. Settings All settings are under **Offer Manager → Settings**. Every toggle listed below has a runtime consumer that gates the corresponding feature. | Setting | Default | What it changes | |---|---|---| | AI Offer Generation | On | Lets template authors draft an offer template, and its letter text, with AI | | Market Analysis | On | Enables AI-powered salary and market analysis under Reports & Data → Market Trends | | Approval Workflows | On | Routes offers through internal approval before they can be sent; when off, submitting an offer approves it at once | | Offer Templates | On | Shows the Templates tab and allows template-based offer creation | | Compensation Benchmarks | On | Enables the compensation benchmarks view under Reports & Data → Market Trends | | Offer Analytics | On | Shows the Offer Analytics page under Reports & Data | | E-Signature Integration | On | Enables e-signature for offer letters; requires a configured provider to take effect | | Automated Reminders | On | Sends automatic follow-up reminders for outstanding offers | | Offer Event Notifications | On | In-app and push alerts for offer views, signatures, acceptances, declines, counter-offers and approval nudges; emails are not affected | | Maximum Counter-Offer Rounds | 1 Round | Controls how many times a candidate can counter-offer; 0 disables negotiation | | Require identity re-verification for document downloads | Off | When on, downloading signed or sent offer letters requires the viewer to re-verify their identity first | | Preferred E-Signature Provider | The E-Signature app's default | Which e-signature provider to use when more than one is available | | Who can see all offers? | Recruiting admins & app admins only | Widens who can see the full offer book beyond the recruiting function | ## 6. More help - **Offer Manager FAQ** — specific setup and operating questions, limits, and troubleshooting. - Ask AI — the assistant answers questions about Offer Manager from these articles. **Keywords:** offer letter, offer manager, compensation, salary offer, approval workflow, e-signature, candidate portal, negotiation, counter-offer, hiring, offer-manager, offer_manager --- # Offer Manager FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-14 Answers to common setup and operating questions about Offer Manager — for the admin running it. # Offer Manager FAQ Answers to common setup and operating questions about Offer Manager. For what the app is and how to set it up from scratch, see the [Offer Manager Overview](/help/articles/offer_manager_app_overview). --- ## Setup ## Do I need to configure approval workflows before I can send offers? No. When no approval workflow matches an offer, the job's hiring manager approves it — and the hiring manager is added as an approver beside any workflow's approvers too, unless they created the offer. If the job has no hiring manager and no workflow matches, submitting is refused with the reason and the offer stays a draft; add a hiring manager to the job or create a workflow. To add approvers for larger offers, create an approval workflow with a salary condition. Offers skip internal approval only when **Approval Workflows** is turned off in Settings — then submitting an offer approves it at once. ## How do I connect e-signatures to Offer Manager? Two paths are available. If your organisation uses the built-in E-Signature app, enable it and Offer Manager detects it automatically. If you use an external provider — DocuSign or HelloSign, the two Offer Manager can send through — set it up under **Admin > Organization > Integrations** as an e-signature integration, then open Offer Manager **Settings** and choose your **Preferred E-Signature Provider** from the dropdown. The **E-Signature Integration** toggle in Settings must also be on. Both paths can coexist — if multiple providers are configured, the dropdown controls which one is used when sending an offer for signature. --- ## Permissions and access ## Who can create and edit offers? Offers are created by the recruiting function (business admins, HR admins and Offer Manager app admins), Offer Manager contributors, the recruiter assigned to a job, and the person who added a candidate (for that candidate). Other people with access to the app — including a job's hiring manager — don't see **Create Offer**. Editing is open on a **Draft**, or on an offer the approval chain rejected, and is limited to the person who created the offer, the recruiting function, Offer Manager contributors, and the recruiter assigned to the job. You can't create or edit an offer made to yourself. ## Who can see all offers versus just their own? Users in the recruiting function — business admins, HR admins and Offer Manager app admins — see every offer in the business. Everyone else sees only offers they created, offers for jobs they recruit for or hiring-manage, or offers they were asked to approve. The **Who can see all offers?** setting can widen the full offer book to everyone with app access, or to specific people. This scoping applies to the Offers list, the Dashboard, and Reports. ## Who can approve an offer? The people the offer's approval names: the approvers of the workflow that matched it, at the level that is open now (with sequential levels, level 1 decides before level 2), and the job's hiring manager. Admin roles do not approve by themselves — a super admin approves only an older offer that has no approval rows — but Offer Manager admins (business admins and Offer Manager app admins) can always use **Override Status** on the offer page. With **Require a separate approver** on (the default), nobody approves an offer they created. Approval delegations also apply — see the delegation question below. --- ## Day-to-day ## How do approval workflows decide which workflow applies to an offer? Each workflow carries conditions: salary range, departments, regions, job levels, and employment types. When an offer is submitted for approval, the most specific active workflow whose conditions match it is used: workflows with conditions are checked before catch-all ones, the default wins among equals, then name order. If no workflow matches, the default workflow is used; if none is marked default, the job's hiring manager approves the offer. ## Can I delegate my approval authority when I'm out of office? Yes. Open Offer Manager, go to the **Internal Approvals** tab and click **Delegate approvals**. Choose a colleague and a date range. While the delegation is active, your delegate can see and act on your pending approvals in addition to their own. Delegations are additive — the original approver can still approve — and they expire automatically when the date range ends. ## How many rounds of counter-offers can a candidate make? The **Maximum Counter-Offer Rounds** setting in Offer Manager Settings controls this. The default is **1** round. You can set it to any value from 0 (counter-offers disabled) through 5, or to **10 Rounds (Maximum)**. Once a candidate exhausts the allowed rounds, the portal no longer shows the negotiate option. ## What happens after a candidate accepts an offer? The offer page shows the next steps: **Mark as hired**, the start date (edit it with the pencil beside it), **Notify Hiring Manager** in the actions menu, and **Set up onboarding**, which opens an onboarding plan when the Onboarding Hub app is enabled — when it is not, the page asks you to enable Onboarding Hub. If e-signature is configured, the signature request normally goes out with the offer (**Request Signature When Sent**, on by default); with that setting off, it goes out when the candidate accepts. When the candidate signs, the signed document is synced to HR Files and the candidate's status is promoted to hired. ## Can a candidate have more than one active offer at a time? No. The system enforces one open offer per candidate. An open offer is one in **Draft**, **Pending Approval**, **Approved**, **Sent** or **Negotiating** status — a draft counts. Delete or finish a draft, and withdraw a sent or negotiating offer (or let it expire), before creating a new one for the same candidate. Accepted, declined, rejected, withdrawn and expired offers don't block a new one. ## What does the candidate see in the portal? The candidate receives an email with a secure link (no login required). In the portal they can view any offer that has been sent, accept it, decline it, or — if counter-offers are still available — submit a counter-offer with an updated salary and a message. Counter-offers notify the hiring team by email and in-app notification. The candidate can also request that the signature email be resent if they lost it. --- ## When something looks wrong ## "I need to change the salary on an offer that is already approved." Only a **Draft**, or an offer the approval chain rejected, can be edited. An offer pending approval, approved or sent cannot be edited: withdraw a sent offer and duplicate it as a new draft, or ask an Offer Manager admin to return it to draft with **Override Status**. A rejected offer you rework is submitted for approval again, and its approvers decide afresh. ## "The offer says it expired, but I set no expiration date." Offers without an expiration date do not expire on their own. If the offer shows as expired, check whether someone set an expiration date when the offer was created or last edited. The expiration date field is optional at creation, but once set, the system marks the offer expired as soon as that date passes. ## "The salary I entered was rejected for being too high." When a job has a posted maximum salary, the system validates that the offer's base salary does not exceed it. This check applies when you send or submit the offer — drafts are not restricted. The validation is intentionally skipped when you accept a candidate's counter-offer, since the negotiated amount may legitimately exceed the original range. ## "I can't find the offer I'm looking for." If you are not in the recruiting function, you only see offers you created, offers for your jobs, or offers you were asked to approve. Ask a recruiting admin or an app admin to locate the offer. Also check the status filter — withdrawn and expired offers may be filtered out of the default view. ## "My approval delegation isn't working." Verify three things: the delegation's date range covers today, the delegate is an active user in the same business, and the delegation was not manually deactivated. Only one active delegation per approver is allowed at a time. If you created a new delegation, any previous one for the same approver was replaced. --- ## Licensing and limits ## Does Offer Manager require a licence? Yes. An admin enables it from Admin → Apps → All Apps, and it requires a licence before it becomes available. The app is disabled by default for every new business. ## Are there limits I should know about? - One active offer per candidate at a time. - Counter-offer rounds are capped by the **Maximum Counter-Offer Rounds** setting (default 1, maximum 10). - Automated reminders run every six hours and check five conditions: unviewed offers (24 hours after sending), unresponded offers (3 days after viewing), offers expiring within 24 hours, unsigned e-signatures (2 days after the signature request), and overdue internal approvals. All reminders respect the **Automated Reminders** toggle in Settings and stop after 90 days. - Approval-workflow conditions can filter by salary range, department, region, job level, and employment type. - Compensation fields (base salary, bonus, equity, and signing bonus) support values up to 10 digits with 2 decimal places. --- ## More help - [Offer Manager Overview](/help/articles/offer_manager_app_overview) - Ask AI — the assistant answers Offer Manager questions from these articles. **Keywords:** faq, offer, approval workflow, negotiation, e-signature, candidate portal, salary threshold, offer template, hiring, offer-manager, offer_manager --- # OKR Hub App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-14 How to set up and run OKR Hub — objectives, key results, check-ins, scoring, and the Performance Management integration. # OKR Hub ## 1. What it is OKR Hub lets your organization set objectives and measure them with key results, quarter by quarter. Objectives cascade from company level through department and team down to individual, and progress rolls up automatically so leadership can see alignment at a glance. - **Enablement:** OKR Hub requires a license. An admin enables it from Admin → Apps → All Apps; it is off by default. - **What it is not:** OKR Hub is not where individual performance reviews happen. Reviews, competency ratings, and appraisal cycles live in Performance Management. OKR Hub tracks strategic objectives and their measurable key results; the two apps connect through an optional integration. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps → OKR Hub** and enable the app. 2. Go to **OKR Hub → Setup → OKR Hub Settings** (open to admins and OKR Hub app admins) and configure: - **Fiscal Year Start Month** — objectives are planned by fiscal quarter. Set this if your fiscal year does not start in January (the default); every quarter boundary follows it. - **Traffic Light Thresholds** — **Yellow From** (default 70%) and **Green At or Above** (default 80%). Progress below the yellow threshold shows red. - **Key-Result Progress Format** — Percentage (default), Decimal, or Grade. It changes only how progress is shown on key-result lists and pages; objectives, reports, the dashboard and emails always show a percentage. 3. Decide whether objectives need approval before activation. Under **Approval Workflow**, toggle approval on for each level independently: Company, Department, Team, Individual. All four are off by default — objectives activate immediately. 4. Admins: open **Setup → Feature Toggles** and review the nine feature toggles: Quarterly Planning, Objective Templates, Objective Scoring, Progress Update Forms, Automated Check-ins & Reminders, Objective Confidence Rating, Advanced Analytics, Export Reports, and AI Insights. All are on by default. Turn off any you do not want your users to see. 5. If you use the Performance Management app, turn on **Enable OKR Integration** at the bottom of OKR Hub Settings to align objectives with Performance Management goals. 6. To confirm setup, ask someone to create and activate one objective with a key result. The objective should appear on their **My Work → My Dashboard**, and the key result should accept a progress update. **Silent-until-configured pairing:** the Performance Management integration is off by default. Without it, the **Strategy** tab (shown to managers when Performance Management is enabled) offers only its **Performance Management** overview page — Goal Alignments, Key Result Mappings and Integration Analytics appear once the integration is on. ## 3. How it fits together ### Objectives and key results An **objective** is a qualitative goal — "Improve customer retention." Each objective has one or more **key results**: measurable targets that prove whether the objective is being met — "Reduce monthly churn from 8% to 4%." By default, progress on the objective is calculated automatically from its key results. Objectives sit at one of four levels: **Company**, **Department**, **Team**, or **Individual**. Anyone can create a department, team, or individual objective. Only an admin, an OKR Hub app admin or HR can create a company-level objective. An active objective can cascade down: a manager or anyone with direct reports who can edit it uses **Cascade** to create a child objective one level down, for themselves or one of their direct reports (an admin can pick anyone). The child starts as a draft with the parent's quarter and dates, and its progress rolls up to the parent. Example: a company objective "Improve customer retention" (Q3 2026) might cascade to a department objective "Reduce support response time" owned by the Support lead, which in turn has a key result "Average first-response time under 2 hours" with a target value of 2 and the unit set to Hours. ### Scoring OKR Hub uses a 0.0–1.0 scoring scale. Objectives come in two types — **Committed** and **Stretch** — and each is graded on a different curve: - **Committed:** below 0.7 is **Did Not Deliver**; 0.7 up to 1.0 is **Delivered**; exactly 1.0 is **Delivered Fully**. - **Stretch:** below 0.3 is **Significant Miss**; 0.3 up to 0.7 is **On Target** (the typical outcome for a stretch goal); 0.7 up to 1.0 is **Exceeded**; exactly 1.0 is **Perfect**. An objective can only be scored after it is marked complete. Once scored, it can no longer be edited or reopened. ### Check-ins A check-in is a periodic status update on an objective. The owner records a progress summary, a confidence level (On track, At risk, or Off track), blockers, and next-period priorities. The person who reviews a check-in is the author's manager — the nearest active manager above them on the reporting line. An admin, an OKR Hub app admin or HR can also review any check-in. The reviewer can leave written feedback and later edit it. Until a check-in is reviewed, its author can edit it — and, once it is completed, delete it. While check-in generation is on, check-ins are created automatically for each owner of an active objective on the business's cadence: **Weekly** (default), **Biweekly**, or **Monthly**. Reminders go out on the **Reminder Day** (default: Thursday), in the morning UTC; there is no time-of-day setting. ### Initiatives An **initiative** is a supporting project or workstream linked to one or more key results. Initiatives track their own progress, priority, and status independently. They are under **Insights → Initiatives & Projects** (or **My Work → Initiatives & Projects** for people without the Insights tab). ### Performance Management integration When the integration is on, objectives can align to Performance Management goals through two mechanisms: - **Goal alignments** — link an objective to a goal with an alignment score, contribution percentage, and optional rationale. With **Require Alignment Rationale** on (the default), a Supports or Contributes To alignment at or above the **Ask for a rationale from (%)** contribution (default 10%) needs a written rationale. - **Key result mappings** — map a key result directly to a goal. When Performance Management's real-time updates are also on, the goal's progress updates the key result automatically. The **Insights → Strategic Cascade** page shows the chain from company objectives down: Objectives → Key Results → Goals. Managers, admins, OKR Hub app admins and HR can open it. ### OKR visibility By default, all objectives are visible company-wide (the OKR-industry standard for alignment). An admin or OKR Hub app admin can restrict visibility to **Managers (of their own team)** — each person sees their own objectives plus their direct reports' — or **Specific people**, the chosen groups, who see everything while everyone else sees their own plus their direct reports'. The setting is **Who can view employees' OKRs?** in OKR Hub Settings. Admins, OKR Hub app admins, and HR always see all objectives regardless of the setting. ### Following an objective Anyone who can see an objective can **Follow** it. Followers are notified when the objective or its key results are edited, completed or cancelled. Progress people log is not sent as a notice. ## 4. Running it ### Creating an objective 1. Go to **My Work → New Objective**. 2. Enter a title (up to 200 characters) and description (up to 2,000 characters). 3. Choose the level, quarter, and date range. The quarter defaults to the current fiscal quarter. 4. Optionally select a parent objective to cascade from, or start from a template. 5. Save. The objective starts in **Draft** status. 6. When ready, click **Activate**. If approval is required for this level, submit it for approval first. It shows **Awaiting approval**, and the owner's manager gets an "Objective awaiting your approval" notice and can **Approve** or **Reject** it from the objective's page or the **Team → Approve Objectives** page. An admin, an OKR Hub app admin or HR can also approve it (from **My Work → Approve Objectives** when they have no team), and they are who approves an objective whose owner has no manager. Once it shows **Approved**, the owner activates it; an objective **Sent back for changes** shows the reason and can be edited and submitted again. While an objective waits for approval, its owner can click **Withdraw from approval** on its page: it goes back to draft and nobody is asked to approve it until it is submitted again. If an admin turns approval off for a level, the objectives already waiting at that level go back to draft so their owners can activate them. Anyone can own their own objective. An admin can assign an objective to anyone in the organization; anyone with direct reports can assign one to a direct report. ### Tracking progress on key results 1. Open a key result and click **Update Progress**. 2. Enter the new value and a comment (at least 10 characters). The progress bar recalculates automatically. 3. For decrease goals (such as reducing churn), progress climbs as the value falls toward the target. Reaching the target does not auto-complete the key result. The owner must use **Mark Complete** explicitly. Managers and anyone with direct reports can use **Team → Bulk Update Progress** to update several key results at once. Update Progress and Bulk Update Progress need the **Progress Update Forms** toggle on. ### Completing, reopening and cancelling **Mark Complete** closes an objective, and a completed objective cannot be edited. Until it is scored, and while its end date has not passed, the people who can edit it can use **Reopen** to make it active again. A cancelled objective can be brought back with **Reactivate** only by an admin, and only until its end date. ### Quarter planning The **Quarter Planning Wizard** (under **Team**, for managers and anyone with direct reports, when the Quarterly Planning toggle is on) lists objectives from a selected quarter. Select the objectives to roll over, and OKR Hub clones them — with their key results — into the next quarter in draft status, resetting progress to zero. ### Approving objectives The **Approve Objectives** page has two tabs: **Waiting for approval**, with bulk approve and reject, and **Decided by me**, which lists the objectives you approved or rejected in the last 90 days. The page needs the Quarterly Planning toggle on; the Approve button on an objective's own page always works. ### Reviewing check-ins Managers and anyone with direct reports follow their team from the **Team** tab — **Team Objectives** and **Team Key Results** list the team's work — and review check-ins from **Team → Team Check-ins**. A badge shows how many check-ins are waiting for your review; a check-in that waits on someone else's review says whose. Click a check-in to read it and leave feedback. ### Scoring a completed objective 1. Open a completed objective and click **Score Objective**. Its owner, someone above the owner on the reporting line, or an admin can score it, when the Objective Scoring toggle is on. 2. Enter a final score (0.0–1.0) and scoring notes. Optionally score each key result individually. 3. Save. The objective and its key results are now locked from further edits. ## 5. Settings Settings are split across two pages: **Setup → OKR Hub Settings** (admins and OKR Hub app admins) and **Setup → Feature Toggles** (admins only). ### OKR Hub Settings (Setup → OKR Hub Settings) | Setting | Default | What it changes | |---|---|---| | Enable OKR Agent | On | Whether Ask AI answers OKR Hub questions and offers its confirmed changes (update key-result progress, activate or complete an objective) | | Who can view employees' OKRs? | Everyone with access to the app | Restricts OKR visibility to managers (of their own team) or specific people, or leaves it company-wide | | Who can view OKR reports? | Managers and above | Who can open the Executive Summary, Team Performance and Quarterly Review reports and their exports; admins, OKR Hub app admins and HR always can | | Default Cascade View | Tree View | Whether the Strategic Cascade page opens in tree or list layout | | Key-Result Progress Format | Percentage | How progress is shown on key-result lists and pages — Percentage, Decimal, or Grade. Objectives, reports, the dashboard and emails always show a percentage | | Progress Calculation | Average of key results | The default for new objectives: every key result except cancelled ones counts equally, or Manual Entry. Existing objectives keep their own setting | | Traffic light — Yellow From | 70% | Progress at or above this value (but below green) shows yellow (Needs attention); below it shows red | | Traffic light — Green At or Above | 80% | Progress at or above this value shows green | | Fiscal Year Start Month | January | Shifts all quarter boundaries to align with your fiscal calendar | | Require Alignment Rationale | On | Whether a Supports or Contributes To alignment to a Performance Management goal needs a written rationale | | Ask for a rationale from (%) | 10% | With rationale required, alignments at or above this contribution need one; smaller alignments are not refused | | Approval Workflow (per level) | Off (all four levels) | Whether objectives at Company / Department / Team / Individual level need approval before activation. Turning a level off sends the objectives waiting at that level back to draft | | Generate Check-ins & Check-in Reminders | On | Creates each owner's check-in on the cadence and reminds them to complete it. Off stops both check-in creation and check-in reminders; the digest and the other alerts are separate | | Check-in Frequency | Weekly | How often check-ins are due — Weekly, Bi-weekly, or Monthly | | Reminder Day | Thursday | The weekday check-in reminders go out (in the morning UTC) | | Notify on Objective Updates | On | Tells an objective's owner and followers when someone else edits it | | Notify on Key Result Updates | On | Tells a key result's owners, its objective's owner and followers when its details are edited or cancelled (completions are announced under Celebrate Milestones). Logged progress does not send a notice | | Notify People Directly | On | @mentions, a manager's review of your check-in, a score on your objective, and a check-in submitted for the reviewer to review. Stays on even if the update notices are off | | Alert At-Risk OKRs | On | A weekly alert (Wednesdays) to the owners of at-risk objectives and to the owners and co-owners of at-risk key results | | Celebrate Milestones | On | Celebration notifications when objectives or key results are completed | | Quarter End Reminders | On | Reminders 30, 14, 7, 3 and 1 days before the fiscal quarter ends, to objective owners and to anyone who owns or co-owns an open key result on that quarter's objectives | | Overdue Key Result Alerts | On | A daily alert for key results past their target date, to the key result's owner and co-owners and its objective's owner | | Weekly OKR Digest | On | A weekly summary, in-app and by email, to everyone who owns an active objective or owns or co-owns an open key result. People with no email address get it in-app | | Weekly Digest Day | Monday | The weekday the digest is sent (in the morning UTC) | | Enable OKR Integration | Off | Whether OKR Hub connects to Performance Management for goal alignments and key-result mappings | ### Feature Toggles (Setup → Feature Toggles, admins only) This entry opens the admin page also titled **OKR Hub Settings**. Its nine toggles show or hide entire feature areas. All are on by default. | Toggle | What it controls | |---|---| | Quarterly Planning | The Quarter Planning Wizard and the Approve Objectives page. With approvals required and this off, approvers act from each objective's own page | | Objective Templates | The template library for creating objectives from templates | | Objective Scoring | The ability to score completed objectives | | Progress Update Forms | The Update Progress dialog, its edit view, Bulk Update Progress and the phone quick-update. Key results can still be edited directly when it is off | | Automated Check-ins & Reminders | Check-in creation and every OKR reminder: check-in reminders, the weekly digest, and the at-risk, overdue and quarter-end alerts. Off stops all of them | | Objective Confidence Rating | The confidence rating on an objective. Check-ins collect their own confidence level regardless | | Advanced Analytics | The Analytics & Insights page | | Export Reports | Exports of objectives, the Strategic Cascade, check-ins, analytics, and the PDF, CSV and Excel report downloads | | AI Insights | The AI Assistant on the objective pages: suggest key results, score OKR quality, check SMART criteria, predict achievement, and suggest improvements. It does not switch off Ask AI's OKR agent, which has its own **Enable OKR Agent** switch in OKR Hub Settings | ## 6. More help - **OKR Hub FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about OKR Hub from these articles. **Keywords:** okr, objectives, key results, okr hub, goal setting, quarterly planning, check-in, scoring, cascade, alignment, okr-hub, okr_hub --- # OKR Hub FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-19 Answers to common setup and operating questions about OKR Hub — for the admin running it. # OKR Hub FAQ Answers to common setup and operating questions about OKR Hub. For what the app is and how to set it up from scratch, see the [OKR Hub Overview](/help/articles/okr_hub_app_overview). --- ## Setup ## Do I need to configure anything before my team can start using OKR Hub? Yes. An administrator must enable OKR Hub from Admin → Apps → All Apps and grant a licence. The app is disabled by default and requires a licence before anyone can access it. Once enabled, review **Setup → OKR Hub Settings** to set your fiscal year start month, check-in cadence and traffic-light thresholds. All nine feature toggles under **Setup → Feature Toggles** (Quarterly Planning, Objective Templates, Objective Scoring, Progress Update Forms, Automated Check-ins & Reminders, Objective Confidence Rating, Advanced Analytics, Export Reports, and AI Insights) default to on, so features are available immediately unless you turn them off. ## Who can see objectives once OKR Hub is turned on? By default, all employees see all objectives across the company. This follows the industry-standard OKR transparency model. An administrator or OKR Hub app admin can change this under the **Who can view employees' OKRs?** setting to one of three modes: **Everyone with access to the app** (the default), **Managers (of their own team)** — each person sees only their own objectives plus their direct reports', including direct reports who have since left — or **Specific people**: the chosen groups see everything, and everyone else sees their own plus their direct reports'. Admins, OKR Hub app admins, and HR admins always see everything regardless of the mode. --- ## Permissions and access ## Who can create objectives at each level? Anyone can create department, team and individual objectives. Only an admin, an OKR Hub app admin or HR can create a company-level objective, so the Level picker offers Company only to them. ## Who sees which tabs? - **My Work** — everyone. - **Team** — managers, and anyone with direct reports: Team Check-ins, Objectives, Team Objectives, Key Results, Team Key Results and Bulk Update Progress, plus Approve Objectives and the Quarter Planning Wizard when Quarterly Planning is on. - **Insights** (Analytics, Reports, Strategic Cascade, Initiatives) — managers, admins, OKR Hub app admins, HR, and anyone the **Who can view OKR reports?** setting admits. Everyone else finds Analytics and Initiatives under My Work. - **Strategy** — managers, when the Performance Management app is enabled. Its **Performance Management** page is the integration overview. - **Setup** — admins and OKR Hub app admins. Its **Feature Toggles** entry is shown to admins only. ## Why can't an employee see a colleague's objectives? Check the **Who can view employees' OKRs?** setting. If it is set to **Managers** or **Specific people**, employees outside the chosen groups see only their own objectives plus their direct reports'. Switch to **Everyone** if company-wide transparency is desired. Key-result visibility follows the parent objective's owner, so if an employee can see the objective they can see its key results. Co-owners of a shared key result can always see that key result. --- ## Day-to-day ## How is progress calculated on an objective? Progress rolls up from the objective's key results. Each key result tracks a start value, current value, and target value. For an increase goal the current value as a share of the target gives the percentage. For a decrease goal (e.g. reduce churn from 20% to 5%) progress rises as the value falls from start toward target. The business-wide default progress calculation is **Average of key results**: every key result except cancelled ones counts equally (key results cannot yet be weighted individually). Admins can change the default for new objectives to **Manual Entry** in OKR Hub Settings. Each objective can also set its own calculation mode (**Manual**, **Auto**, or **Hybrid**) on its Edit page. ## How does scoring work? Scoring uses a 0.0 to 1.0 scale. The automatic score suggested for an objective is the average of its key results' scores (or their progress if unscored), leaving out cancelled key results. The grade depends on the objective's type: - **Committed:** below 0.7 is **Did Not Deliver**, 0.7 up to 1.0 is **Delivered**, and exactly 1.0 is **Delivered Fully**. - **Stretch:** below 0.3 is **Significant Miss**, 0.3 up to 0.7 is **On Target** (the typical outcome for a stretch goal), 0.7 up to 1.0 is **Exceeded**, and exactly 1.0 is **Perfect**. Only a completed objective can be scored — by its owner, someone above the owner on the reporting line, or an admin. Once scored it can no longer be edited. Scoring is an admin toggle (Objective Scoring) and can be turned off. ## What happens when a key result reaches its target? The key result is not automatically marked complete. Reaching the target surfaces the **Mark Complete** action, and the owner must click it. This is intentional — it gives the owner a chance to verify the result before closing it. If a completed key result is later corrected back below its target, the status reverts to active and Mark Complete reappears. ## Can a completed objective be reopened? Yes, until it is scored and while its end date has not passed. Open it and choose **Reopen**; it becomes active and editable again. Its owner, someone above the owner on the reporting line, or an admin can reopen it. A **cancelled** objective is different: only an admin can bring it back with **Reactivate**, and only until its end date. ## How do check-ins work? Check-ins run on the cadence set in OKR Hub Settings: **Weekly**, **Biweekly**, or **Monthly** (default is Weekly). While check-in generation is on, OKR Hub creates one for each owner of an active objective every period. Each check-in captures a confidence rating (**On track**, **At risk**, or **Off track**), a progress summary, blockers, needs, and next-period priorities. The owner can attach files and add emoji reactions. The check-in's reviewer is the author's nearest active manager on the reporting line; an admin, an OKR Hub app admin or HR can also review any check-in. The reviewer can leave written feedback and edit it afterwards. Until a check-in is reviewed its author can edit it, and a completed, unreviewed check-in can be deleted by its author (or an admin). Reminder notifications go out on the **Reminder Day** set in OKR Hub Settings (default: Thursday), in the morning UTC — there is no time-of-day setting. A check-in is reminded once it is due within three days, and reminders stop 30 days after its date passes. ## Can I roll objectives into the next quarter? Yes, through the **Quarter Planning Wizard** under **Team** (available to managers and anyone with direct reports when the Quarterly Planning toggle is on). Select the objectives you want to carry forward and use **Rollover**. Each selected objective is cloned into the next quarter with progress reset to zero, status set to draft, and all key results copied with their values reset. ## How does the approval workflow work? Approval is off by default. An administrator can turn it on per level — separately for company, department, team, and individual objectives. When enabled, an objective owner submits the objective for approval and it shows **Awaiting approval**. The owner's manager gets an "Objective awaiting your approval" notice and clicks **Approve** or **Reject**; an admin, an OKR Hub app admin or HR can also approve anyone's objective but their own. When the owner's manager has left, the next active manager above them is asked instead. When the owner has no manager in the company, OKR Hub's app admins are asked; with no app admins, nobody is notified and the objective's page says so — an admin or HR approves it on the objective's page (or from **Approve Objectives** while Quarterly Planning is on). If the owner's manager changes, or the person asked leaves or loses the right to approve while it waits, the request moves to whoever decides it now. An approved objective shows **Approved** and its owner activates it; a rejected one shows **Sent back for changes** with the reason, and its owner can edit it and submit it again. While it waits, the owner can use **Withdraw from approval** on the objective's page to take it back to draft. If an administrator turns approval off for a level, the objectives already waiting at that level go back to draft, so their owners can activate them. Bulk approve and reject are on the **Approve Objectives** page (under **Team** for managers, under **My Work** for app admins and HR without a team), which needs the Quarterly Planning toggle on; the Approve button on the objective's own page always works. The page's **Decided by me** tab lists the objectives you approved or rejected in the last 90 days. ## What does following an objective do? Click **Follow** on an objective to be notified when it or its key results are edited, completed or cancelled. Progress people log is not sent to followers. --- ## When something looks wrong ## My progress bar is red even though we're making progress — what's wrong? The traffic-light colors follow the thresholds in OKR Hub Settings. By default, progress at or above **80%** (**Green At or Above**) is green (On track), **70–79%** (**Yellow From** 70%) is yellow (Needs attention), and below **70%** is red (Off track). An admin can change both thresholds; yellow must be lower than green. An active objective whose progress would be green but is behind pace for the time elapsed shows yellow. ## A key result says "Behind" but it isn't due for months — why? **Behind** is about pace, not the due date. OKR Hub measures each key result over the time from its objective's start date to the key result's own target date. It reads **On track** while its progress is no more than 10 points below the share of that time that has passed, and **Behind** once it falls further back, or once its target date arrives without the target met. For example, when 80% of the time has passed, a key result needs 70% progress to be on track. On **My Key Results**, the info icon beside the word shows that key result's numbers; on the phone they show under its progress bar. Logging progress with **Update Progress** updates the reading. ## I updated a key result but the objective progress didn't change If the objective's progress mode is set to **Manual**, key-result progress does not roll up automatically. Switch it to **Auto** or **Hybrid** on the objective's edit page. Also check that the key result's target value is not zero — progress cannot be calculated against a zero target. ## I can't edit my comment any more — it was only posted a few minutes ago Comment authors can edit their own comments for **15 minutes** after posting. After that window closes only an admin or an OKR Hub app admin can edit the comment. Authors, admins and OKR Hub app admins can always delete a comment; managers can delete comments on objectives owned by people they manage. ## Why didn't my team get check-in reminders? Check four things: - **Automated Check-ins & Reminders** is on under **Setup → Feature Toggles**. Off, it stops check-in creation and every OKR reminder. - **Generate Check-ins & Check-in Reminders** is on in OKR Hub Settings. Off, it stops check-in creation and check-in reminders only; the weekly digest and the at-risk, overdue and quarter-end alerts keep running. - The person has a pending check-in due within three days and not more than 30 days overdue. - It is the **Reminder Day** set in OKR Hub Settings (default: Thursday). Reminders go out that morning, UTC. People with no email address get the reminder in OKR Hub's notifications only. ## Why didn't someone get the at-risk, overdue or quarter-end alert? These alerts go to the objective's owner and also to the owner and co-owners of the key result concerned. Check that the alert's switch is on in OKR Hub Settings (**Alert At-Risk OKRs**, **Overdue Key Result Alerts**, **Quarter End Reminders**) and that **Automated Check-ins & Reminders** is on under Feature Toggles. At-risk alerts go out on Wednesdays, overdue alerts daily, and quarter-end reminders 30, 14, 7, 3 and 1 days before the fiscal quarter ends. Each of these alerts, and the weekly digest, also appears in OKR Hub's notifications, so people with no email address still get them. --- ## Licensing and limits ## Does OKR Hub require a licence? Yes. OKR Hub requires a licence and is opt-in per tenant. An administrator enables it from Admin → Apps → All Apps. It is disabled by default until then. ## Are there limits I should know about? | Item | Limit | |---|---| | Objective title | 200 characters | | Objective description | 2,000 characters | | Key result title | 200 characters | | Key result unit label | 50 characters | | Comment length | 3–1,000 characters | | Progress update comment | 10–1,000 characters | | Objective score range | 0.0–1.0 | | Key result current value (non-percentage) | Up to 150% of target (for a decrease goal, 150% of its largest value) | | Key result current value (percentage unit) | 0–150% | | Fiscal year start month | 1–12 (January–December) | | Traffic-light thresholds | 0–100 each; yellow must be less than green | | Ask for a rationale from (%) | 0–100 (default 10) | | Comment edit window | 15 minutes after posting (authors only; admins and OKR Hub app admins unlimited) | | Planning period | Fiscal quarters (Q1–Q4), following the fiscal year start month | --- ## AI features ## What can AI do in OKR Hub, and can I turn it off? There are two separate AI features, each with its own switch: - **AI Insights** (under **Setup → Feature Toggles**, on by default) controls the **AI Assistant** on the objective pages: suggest key results from an objective's title, score an OKR's quality against best practices, check it against SMART criteria, predict how likely it is to be achieved, and suggest improvements. The assistant only suggests — nothing it produces is saved unless a person adds it and saves. - **Enable OKR Agent** (in **Setup → OKR Hub Settings**, on by default) controls Ask AI's OKR agent, which answers questions about OKRs and can update key-result progress and activate or complete objectives, each only after the person asking confirms. Turning off AI Insights does not turn off the OKR agent, and turning off the agent does not remove the AI Assistant. --- ## More help - [OKR Hub Overview](/help/articles/okr_hub_app_overview) - Ask AI — the assistant answers OKR Hub questions from these articles. **Keywords:** faq, objective, key result, OKR, check-in, scoring, cascade, approval, traffic light, progress, alignment, confidence, not showing, permissions, okr-hub, okr_hub --- # Onboarding Hub App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-14 How to set up and run Onboarding Hub — building onboarding plans from templates, assigning tasks across roles, preboarding before day one, collecting documents, and tracking compliance. # Onboarding Hub ## 1. What it is Onboarding Hub manages the journey from "offer accepted" through a new hire's first months. You build templates that bundle tasks, documents, forms, checkpoints, trainings, and surveys, then assign them — manually or automatically — when someone is hired. New hires can start preboarding before day one through a secure portal, and the app tracks completion, sends reminders, and monitors I-9 and compliance status. - **Enablement:** Requires a license. An admin enables it from **Admin → Apps → All Apps**. It is not turned on automatically. - **What it is not:** Onboarding Hub covers the *inbound* journey. Offboarding (structured employee departures) is a separate app. Training courses are authored in the Training app — Onboarding Hub assigns them as plan items, it does not create them. The Forms app builds the form templates — Onboarding Hub pulls them into a plan as enrollment forms. ## 2. Standing it up 1. **Enable the app** — go to **Admin → Apps → All Apps**, find **Onboarding Hub**, and enable it. 2. **Create at least one template** — go to **Onboarding Hub → Templates → New Template**. A template defines everything a plan contains: tasks, milestone checkpoints, documents to collect, forms to fill, and their day-offset schedule. Set the template type (Standard, Executive, Technical, Custom, or Department-specific), role level (Entry, Mid, Senior, or Executive), and optionally a department and location scope so the auto-matcher can pick the right one later. 3. **Stock the libraries** — populate the Tasks, Documents, Forms, and Welcome Content libraries so template authors can pull from a shared catalog. Use **Load Default Data** under Settings to seed industry-standard items if you want a starting point. - For a ready-made set of pathways, use **Settings → Load Default Data → Starter Pathways**: Hourly and Salaried new hires, a New Leader pathway and an Internal Transfer and Promotion pathway, in a standard or a hospitality variant. Installing again restores any pathway you haven't changed and keeps one you've edited exactly as you left it; library items your libraries don't have are left out and listed. 4. **Set up relationship types** — Mentor and Buddy are seeded automatically. Add any custom types your program needs (e.g. Executive Sponsor, Skip-Level Manager) under **Settings → Relationship Types**. Mark a type as **Required** if every plan must have it assigned before it can start. 5. **Grant access** — admins and managers can create and manage plans. App Admins (granted through **Admin → Roles**) have manager-equivalent access. Employees see only their own onboarding plan; an employee who leads a team also sees their team's plans on the Plans list. Settings and compliance configuration are admin-only. 6. **Confirm it worked** — create a test plan for an employee, start it, and check that the employee sees their tasks under **Onboarding Hub → My Onboarding**. Verify that the new hire receives the welcome email and that the hiring manager is told the plan is live. **Silent dependency:** If you turn on **Create the onboarding plan on hire** under Settings → Automation, the auto-onboard needs either a pinned template or at least one active template that matches by role, department, or location. Without a matching template, the automation runs silently and creates nothing. ## 3. How it fits together **Templates and plans** — A template is a reusable blueprint. A plan is a live instance created for one person. Templates hold items (tasks, checkpoints, documents, forms) with day offsets relative to the start date; when a plan is generated from a template, those offsets produce concrete due dates. Plans move through five statuses: **Draft** → **Preboarding** → **Active** → **Completed** (or **Paused** at any point after activation). A plan can only be completed when all required items — required tasks, critical checkpoints, required documents, required enrollment forms, required surveys, and required trainings — are finished. Optional items do not block completion. **Template matching and pathways** — When you create a plan (or auto-onboarding fires), the system scores every active onboarding template; pre-start experience templates are never picked as the plan's template. A template can be set up as a **pathway**: the lifecycle events it is for (new hire, rehire, promotion, transfer, becoming a people manager) and the audience it is for (for example Hourly team members). What happened to the person counts most — a pathway for their event beats a template that names none, and a rehire also matches a new-hire pathway — then who they are (a pathway for an audience they belong to beats one for everyone), then location scope, role level and department. Location scoping has four modes: **Any** (business-wide), **Specific** (exact location match), **Regional** (location is an ancestor of the employee's), and **Headquarters** (employee is at the business's HQ). The most-specific match wins, with ties broken by most recently created. Admins can also pin a specific template for auto-onboarding, bypassing the matcher. Hourly and Salaried audiences read each person's FLSA status when it is recorded, otherwise their pay basis, which is set from the job when a candidate becomes an employee. **Standalone vs. recruiting mode** — Plans can be created in two ways. In recruiting mode, the plan is linked to a Job Board candidate — the candidate's job, hiring manager, and offer data carry over. In standalone mode, you pick any employee directly, fill in the job title yourself, and say what the onboarding is for — a new hire, a rehire, a promotion, a transfer, or someone becoming a people manager — so the suggested template is the pathway for that event. A promotion, transfer or new leader's plan is an **internal move**: the new-hire paperwork (I-9, W-4, employment agreement, direct deposit, benefits enrollment) is not added, and Analytics counts it as a move rather than a new hire. **Internal moves** — With **Create an onboarding plan for promotions, transfers and new people managers** on (Settings → Automation), a plan for the new role is created automatically when a promotion, a move to another department or location, or a move into management (a job title marked as a leadership position, or being marked a people leader) is recorded. It follows the same start and welcome-email choices as a plan created on hire. **Task assignment roles** — Every task in a template is assigned to a role: New Hire, Hiring Manager, Mentor, Buddy, HR Team, IT Team, or Admin. Tasks can also be assigned to a recipient group, which either fans out into one task per group member or assigns to a single lead. Role-based assignment resolves to the actual person when the plan is created. **Preboarding** — Plans in Preboarding status give new hires access to a secure, token-based portal before their start date. The portal shows only items scheduled as **Before start** — day-one and post-start items stay hidden until the start date. When the **Activate the plan on the start date** automation is on (it is off by default), an hourly job activates preboarding plans at 06:00 in the company's time zone on their start date, transitioning them to Active and sending the day-one welcome notification. **Relationship types** — Beyond the built-in Mentor and Buddy columns, admins can create custom relationship types (e.g. Department Lead, Executive Sponsor) and mark them required or optional. Each plan supports one assignment per type. System-default types (Mentor, Buddy) cannot be deleted; any type that is already in use on a plan cannot be deleted until removed. ## 4. Running it ### Creating a plan manually 1. Go to **Onboarding Hub** and click **New Plan**. 2. Choose **Recruiting mode** (select a hired candidate) or **Standalone mode** (select an employee, enter the job title, and choose what the onboarding is for). 3. The system suggests a template — the pathway for the event and the person, then by role, department, and location. Accept the suggestion or pick a different one. 4. Set the start date, hiring manager, and optionally a mentor and buddy. 5. Save. The plan is created in Draft status with items generated from the template. ### Starting preboarding 1. Open a draft plan and click **Begin Preboarding**. The plan moves to Preboarding status. 2. The new hire receives an email with a link to their preboarding portal — this reaches their personal email before they have a company account. 3. In the portal, the new hire can complete before-start tasks, fill enrollment forms, upload documents, and view welcome content. ### Managing documents and e-signatures 1. Each plan lists the documents it requires (ID, tax, benefits, background check, etc.). New hires upload files through the portal or the app. 2. Documents that need a signature can be sent through the native e-signature flow or a connected provider (DocuSign or HelloSign / Dropbox Sign). Onboarding packages are signed with the built-in signer. 3. After upload, an admin or manager verifies or rejects each document. Rejected documents send a notification so the new hire can re-upload. ### Reviewing I-9 compliance 1. Go to **Onboarding Hub → Compliance Report** (admin or HR admin only). 2. The report's tabs list employees without a complete I-9, work authorizations expiring within the next 30 days, authorizations that have already expired, and I-9s completed in the last 7 days. The **Incomplete I-9s** and **Expiring Work Authorizations** pages list everyone in those groups. 3. Once an authorization has ended, open its reverification from the report's **Expired** tab with **Trigger Section 3**. This opens the I-9 Section 3 form already on the employee's onboarding plan and makes it due in 3 days; nobody is notified automatically, so tell the employee. A row whose latest active or completed plan has no Section 3 form says so instead of offering the button, and a row whose Section 3 is already open shows its due date. ### Using the analytics dashboard 1. Go to **Onboarding Hub → Analytics**. The executive analytics view shows average time-to-completion and completion rates across plans, and new hires against exits. 2. The onboarding analytics view shows plan counts, overdue items, and status breakdowns, and breaks onboarding down by department, location, or pathway. **New hires** and **moves** (promotion, transfer and new-leader plans) are counted separately. **Time to productive** is the number of days from a plan's start date to the completion of its final milestone checkpoint, averaged over the plans signed off in the period you pick. 3. For a single plan, open it and choose **Audit Report** — a per-employee trail of every form, document, communication, and compliance item with timestamps. The audit report exports to CSV. ### Automated background operations Several daily jobs run without admin intervention: - **Preboarding auto-activation** — hourly, when the **Activate the plan on the start date** automation is on (off by default). Plans in Preboarding are activated at 06:00 company time on their start date, and each new hire receives a day-one welcome. - **Form and document reminders** — daily at 8 AM UTC. Each business's configured reminder triggers (3 days before, on due date, etc.) are evaluated and reminders sent. - **Checkpoint reminders** — daily at 8 AM UTC. Checkpoint owners are reminded about checkpoints scheduled for the next day. - **Overdue alerts** — daily at 8 AM UTC. Hiring managers are notified about plans with overdue items. Plans older than 90 days past their target completion stop generating alerts. - **Weekly digest** — every Monday at 9 AM UTC. Each hiring manager receives a summary of their active plans' status. - **Scheduled preboarding emails** — daily at 7 AM UTC. Sends admin-authored preboarding email campaigns to new hires based on a configured schedule. - **Department notifications** — every 30 minutes. Processes and sends pending department notification alerts (e.g. notifying IT about equipment setup). ## 5. Settings All settings are at **Onboarding Hub → Settings** (admin only). ### General | Setting | Default | What it changes | |---|---|---| | **Pre-start portal access** | On | Lets new hires access the preboarding portal before day one. When off, they see a "see you on day one" page instead. | | **Onboarding AI agent** | On | Enables the Onboarding agent in Ask AI. New hires check their own tasks, documents, equipment and first day and complete their own tasks; managers see and start, pause or resume the plans of the hires they run; admins and HR can also set up plans, assign tasks and training, and send reminders. Every change asks for confirmation first. | | **Onboarding admin agent** | On | Enables the admin agent in Ask AI that drafts a 30/60/90-day plan for a role. The draft is not saved — use **Templates → Draft with AI** to save one as a template. | | **Require identity re-verification for document downloads** | Off | When on, downloading onboarding documents requires the user to re-authenticate first. | ### Automation | Setting | Default | What it changes | |---|---|---| | **Create the employee account on hire** | Off | Automatically creates an employee record when a Job Board candidate is marked hired. | | **Create the onboarding plan on hire** | Off | Automatically generates an onboarding plan from a matched (or pinned) template when a candidate is hired. | | **Start the plan immediately** | Off | When on, auto-created plans start in Preboarding status instead of Draft. | | **Email the new hire their welcome on auto-onboard** | On | Sends the plan-created notification to the new hire when auto-onboarding fires. | | **Activate the plan on the start date** | Off | A daily job transitions preboarding plans to Active on their start date and sends the day-one welcome. | | **Create an onboarding plan for promotions, transfers and new people managers** | Off | Creates a plan for the new role when a promotion, a transfer, or a move into management is recorded — from the pathway set up for that event when there is one. The new-hire paperwork is not added. | ### Notifications A master **Automated reminders** switch (default On) gates all reminder delivery. Below it, individual toggles control each notification type — all default to On: Plan created · Plan completed · Form reminders · Document reminders · Checkpoint reminders · Overdue alerts · Weekly digest · Document verification · Mentor assignment · Buddy assignment · Task group assignment. **Reminder timing** for forms and documents uses four triggers per type: 7 days before (default Off), 3 days before (default On), on the due date (default On), daily once overdue (default Off). The default schedule is low-noise — a 3-day heads-up and a due-date nudge. ### Integrations | Setting | Default | What it changes | |---|---|---| | **Forms app integration** | On | Allows pulling Forms app templates into onboarding plans as enrollment forms. | | **Tasks app integration** | On | Keeps onboarding-task status in sync with the Tasks app. | | **Preferred e-signature provider** | None (tenant default) | Sets the default provider for sending a single document for signature — native, DocuSign, or HelloSign. | ## 6. More help - **Onboarding Hub FAQ** — specific setup and operating questions. - Ask AI — the assistant answers questions about Onboarding Hub from these articles. **Keywords:** onboarding, new hire, onboarding plan, preboarding, onboarding template, I-9, new hire tasks, onboarding checklist, mentor assignment, buddy assignment, onboarding documents, onboarding compliance, welcome content, orientation, hire onboarding, day one, onboarding-hub, onboarding_hub --- # Onboarding Hub FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-14 Answers to common setup and operating questions about Onboarding Hub — for the admin running it. # Onboarding Hub FAQ Answers to common setup and operating questions about Onboarding Hub. For what the app is and how to set it up from scratch, see the [Onboarding Hub Overview](/help/articles/onboarding_hub_app_overview). --- ## Setup ## Does Onboarding Hub require a licence? Yes. Onboarding Hub is disabled by default and requires a licence. An admin enables it per business from Admin → Apps → All Apps — nothing is pushed on automatically. ## What do I need to configure before onboarding my first new hire? At minimum, create one active onboarding template (Resources → Onboarding Templates). Without an active template the auto-matcher has nothing to suggest. Beyond that, review the Settings tabs — the defaults are production-ready (reminders on, pre-start portal on, AI features on), but the three automation steps that create employee accounts, create plans, and activate plans on the start date are all off until you turn them on deliberately. --- ## Permissions and access ## Who can manage onboarding plans and who can only see their own? Admins, super admins, app admins, and managers can see the Onboarding dashboard, create and manage plans, and access the Resources and Analytics tabs. Regular employees only see the **My Onboarding** tab, and only while they have an active plan. Settings are restricted further — only admins, super admins, and app admins can open the Settings tab. ## Why can't my managers see the I-9 Compliance Report or Incomplete I-9s? The I-9 and work-authorization compliance views expose company-wide federal PII (visa status, work-authorization expiry). Access is limited to admins, app admins, and HR admins. Regular managers are intentionally excluded — they will not see the I-9 links in the Analytics sidebar. --- ## Day-to-day ## Can I onboard someone who wasn't hired through Job Board? Yes. Create a standalone plan from the Onboarding dashboard by assigning a user directly instead of linking a recruiting candidate. Standalone plans work the same way — tasks, documents, checkpoints, reminders — they just don't require a Job Board candidate record. ## Can a person have more than one active onboarding plan at the same time? No. The platform prevents creating a second plan for someone who already has a plan in Draft, Preboarding, or Active status. Complete, pause or delete the existing plan before creating a new one. ## How does the auto-matcher choose a template for a new hire? The matcher looks at every active onboarding template (pre-start experience templates are never picked as the plan's template). First it asks **what happened**: a template set up as a pathway for the person's lifecycle event — a new hire, a rehire, a promotion, a transfer, or becoming a people manager — beats one that names no event, and a rehire also matches a new-hire pathway. Next it asks **who the person is**: a pathway for an audience (for example Hourly team members) is picked only for people in that group, and beats one for everyone. Then location scope (a specific site, then regional, then headquarters, then any location), a matching role level and a matching department refine the choice. If two templates tie, the most recently created one wins. If nothing matches, the matcher returns no suggestion and the admin picks manually. In the new-plan wizard's Direct Assignment mode, choose **What is this onboarding for?** so the suggestion is the pathway for that event. ## What are starter pathways, and what happens if I install them again? Settings › Load Default Data › **Starter Pathways** installs four templates, each picked automatically for the right person: Hourly and Salaried new hires (for the Hourly team members and Salaried & leaders audiences, created under Groups if you don't have them), a New Leader pathway and an Internal Transfer and Promotion pathway — in a standard or a hospitality variant. Installing one variant switches the other variant's matching pathways off. Installing again restores any pathway you haven't changed. A pathway you've edited since it was installed — renamed, re-pointed at another audience, a task added or changed — is kept exactly as you left it, and the result names it; delete it if you want a fresh copy. If your task or document library doesn't have an item a pathway names, that item is left out and the result lists it: load the library seed content and install again. Hourly and Salaried are read from each person's FLSA status when it is recorded, otherwise from their pay basis (hourly or salary), which is set from the job when a candidate becomes an employee. ## Does a promotion or transfer get an onboarding plan? Yes, when **Create an onboarding plan for promotions, transfers and new people managers** is on in Settings › Automation. When a promotion, a move to another department or location, or a move into management (a job title marked as a leadership position, or being marked a people leader) is recorded, a plan for the new role is created from the best-matching template — a pathway set up for that event comes first. The new-hire paperwork (I-9, W-4, employment agreement, direct deposit, benefits enrollment) is not added; it is already on file. The plan follows the same choices as a plan created on hire: it waits as a draft unless **Start plan in preboarding immediately** is on, and the person is emailed that it is ready unless **Email the new hire their welcome** is off. These plans are counted as **moves**, not new hires, in Analytics. ## Does someone posted to a location get an onboarding plan? Yes, when you ask for it. Settings › Automation › **Create a pre-arrival plan when someone is first assigned to a location** is off by default. With it on, a work assignment (People › Work assignments) that posts someone to a location for the first time creates a plan starting on their first day there, from the best-matching active template for that location that is set up for **Assigned to a location**. A later assignment to the same location creates nothing, and neither does a location with no such template, so a crew that rotates is not given the induction again on every trip. The plan follows the assignment: if the first day moves, the plan and the items nobody has started move with it, and if the assignment is cancelled the plan is paused. An administrator can also open the plan by hand from the assignment's row, which says why when none is opened, for example because the person is still in another onboarding plan. ## Can experienced people get a shorter plan than first-timers? Yes. Give each template an **Audience**: a group, added under Admin › Groups, such as "First trip" or "Experienced hands". When a plan is created automatically, a template whose audience the person belongs to is chosen ahead of one for everyone, so each tier gets its own plan for the same location or role. A group can match people by attributes such as job title or hire date, so nobody has to maintain the list by hand. ## How is "time to productive" measured? A plan's final milestone checkpoint — its highest-day checkpoint, such as the 30- or 90-day review — is the sign-off that the person is fully productive. Time to productive is the number of days from the plan's start date to the day that checkpoint was completed. Analytics averages it over the plans **signed off during the period you pick**, whenever they started, so a 30-day view shows the people who reached productivity in those 30 days. Plans whose final checkpoint is still open, skipped, or completed before the start date are left out rather than counted as zero. ## How do form and document reminders work? Each business sets its own reminder schedule independently for forms and documents. There are four triggers you can toggle on the Settings → Notifications tab: 1. **7 days before due** — off by default 2. **3 days before due** — on by default 3. **On the due date** — on by default 4. **Daily once overdue** — off by default A master **Automated reminders** switch gates all of them. When it is off, no automated reminders of any type are sent. Overdue reminders stop automatically after 90 days past the due date so a single neglected item cannot generate mail indefinitely. ## When do the surveys on an onboarding plan go out? On their due date, in your organization's time zone: the plan's start date plus the survey's day offset, or — for a survey scheduled **Before start** — that many days before the start date. The new hire gets the survey by email and in their Inbox (the Surveys app must be on, and the survey needs questions and, where your organization requires it, approval). Everyone who gets the same check-in in the same stretch of time answers it together, so results reach the anonymity threshold and anonymous answers stay anonymous. A check-in more than 30 days past its due date is not sent automatically — a plan started long ago does not get its early check-ins all at once. When the new hire submits a survey that is not anonymous, the plan item is marked complete on its own, and one they answered before its due date completes instead of being sent again. An **anonymous** check-in is never marked complete automatically — that would reveal who answered — so the new hire marks it done themselves. ## When does the weekly manager digest go out, and when does it stop? The digest emails every Monday at 9 AM UTC to each hiring manager who has at least one active plan. It automatically stops for plans whose target completion date (or start date, if no target is set) is more than 90 days in the past, so managers are not emailed indefinitely about hires who started long ago. The digest is gated by both the master **Automated reminders** switch and the **Weekly digest** toggle in Settings → Notifications. ## What happens when a plan is completed? The plan status moves to **Completed** and the completion timestamp is recorded. If the plan was created from a Job Board candidate, the candidate's status is updated to **Hired** and their onboarding status to **Completed**. The hiring manager receives a completion notification. Completion percentage is calculated from required items only — optional tasks and non-critical checkpoints do not block completion. ## How do buddy and mentor assignments work, and can I add custom relationship types? Every plan can name a mentor and a buddy, each with their own assignment notification. Mentor and Buddy ship as system defaults and cannot be deleted. Three additional types — Executive Sponsor, Skip-Level Manager, and Department Lead — are seeded on first use. You can add your own custom relationship types from Settings → Relationship Types with a name, code, and optional required flag. Custom types that are not in use can be deleted; system defaults can only be deactivated. ## What are the plan statuses and what transitions are allowed? A plan moves through five statuses: **Draft → Preboarding → Active → Completed**, with **Paused** as a side state. A draft plan can be started (moves to Active) if it has a start date, or moved to Preboarding. A preboarding plan auto-activates on the start date when the **Activate the plan on the start date** automation toggle is on. Active plans can be paused and resumed. Only active plans can be completed (resume a paused plan first), and completion requires 100% of required items to be done — a skipped item counts as done. --- ## When something looks wrong ## "My new hire says they can't see their tasks yet" If the plan is still in the preboarding phase (before the start date), the new hire only sees items explicitly scheduled as **Before start**. Tasks, documents, and forms scheduled for Day 1 or later stay hidden until the start date arrives. Check the plan's start date and the schedule type on each item. If the **Pre-start portal access** setting is off, candidates cannot access the portal at all before Day 1 — they would need to authenticate on or after their start date. ## "Reminder emails stopped going out after I enabled them" Three things can block reminders even when individual toggles are on: (1) the master **Automated reminders** switch is off — it gates every reminder type; (2) Onboarding Hub is not enabled for the business in Admin → Apps → All Apps — disabled tenants receive no automated notifications; (3) the template has its own **Send Reminders** toggle turned off — that overrides the business-level setting for plans created from that template. Check all three. ## "The weekly digest keeps going to a manager about a hire who started months ago" The digest automatically stops 90 days after the plan's target completion date. If the plan has no target completion date set, it falls back to the start date. Plans with neither date set are included to avoid dropping brand-new plans. The digest only covers active plans, so pausing, completing or deleting a plan stops it immediately. ## "A plan completed but the candidate still shows as in-process in Recruiting" If the candidate record could not be updated when the plan completed (for example, because it failed a validation on an unrelated field), the plan completes but the candidate's recruiting status stays unchanged. Check the candidate record in Job Board for validation errors. The platform logs these failures but does not block plan completion. --- ## Licensing and limits ## Does a promotion or transfer count toward our onboarded-hire usage? No. Only new-hire onboarding counts: each new-hire plan adds one onboarded hire when it is created. A plan for a promotion, a transfer or someone becoming a people manager is an internal move and is never counted. That person already holds a seat you pay for. - **Counted:** plans created from a Job Board candidate, and Direct Assignment plans where **What is this onboarding for?** is **New hire** or **Rehire**. - **Not counted:** plans the automation creates for promotions, transfers and new people managers. Direct Assignment plans set to **Promotion**, **Transfer (department or location)** or **Became a people manager** are not counted either. The count is taken when the plan is created. A plan deleted later, or never finished, still counts. The choice can't be changed afterwards, so pick the right event in the new-plan wizard. Sample data plans are never counted. ## What are the hard limits I should know about? | Limit | Value | |---|---| | Template duration | 1–365 days | | Plan name length | 255 characters | | Active plans per person | 1 (draft, preboarding, or active) | | Checkpoint satisfaction score | 1–5 | | Bulk document download | 100 MB per download | | AI stalled-task nudge window | 24–168 hours (default 48) | | Overdue reminder cutoff | 90 days past due date | | Relationship type name | 100 characters | ## What file types can new hires upload for documents? PDF, JPEG, PNG, GIF, HEIC (iPhone camera format), HEIF, DOC, and DOCX. Document types include identification, tax documents, benefits forms, emergency contacts, background check, education verification, employment verification, and custom. ## What e-signature providers does Onboarding Hub support? The built-in native e-signature (requires the E-Signature app to be enabled), plus external providers connected through Integrations: DocuSign and HelloSign (Dropbox Sign). Other connected providers are not used by Onboarding Hub. Select the preferred provider on the Settings → Integrations tab. E-signature packages can bundle multiple PDFs into a single signing request. --- ## More help - [Onboarding Hub Overview](/help/articles/onboarding_hub_app_overview) - Ask AI — the assistant answers Onboarding Hub questions from these articles. **Keywords:** faq, onboarding plan, preboarding, template matching, new hire, I-9, document verification, reminders, buddy, mentor, standalone, compliance, onboarding-hub, onboarding_hub --- # On-Call Management FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-14 Answers to common setup and operating questions about On-Call Management — for the admin running it. # On-Call Management FAQ Answers to common setup and operating questions about On-Call Management. For what the app is and how to set it up from scratch, see the [On-Call Management Overview](/help/articles/on_call_management_app_overview). --- ## Setup ## Do employees need to be enabled before they can be added to a rotation? Yes. Each employee has an on-call duty flag that defaults to **off**. Until a manager enables it, the employee does not appear in the rotation builder's staff list. Managers can enable employees directly from the rotation builder or the pool's Manage Staff modal without leaving the page. ## What role do I need to manage pools and rotations? You need the **manage on-call** capability. Admins have it by default. Managers who hold the capability but are restricted to specific locations can only manage pools tied to those locations. Pools with no location ("All Locations") are manageable by any on-call manager. ## Who can activate an incident? Activating a pool requires the **activate on-call** permission — typically granted to managers, admins, or monitoring systems. The activator must also have access to the pool's location. --- ## Permissions and access ## Why can't a manager see a specific pool? Pools can be tied to a location. Non-admin users only see pools at locations they have **view on-call** access for, plus any pool set to "All Locations" (no location assigned). Ask the admin to grant the manager view access for that location. ## Who can resolve an incident? Resolving requires a separate **resolve on-call** capability. Acknowledging, responding, commenting and linking are available to anyone who was notified for the incident or who holds the **manage on-call** capability. Snoozing, transferring and raising severity need **manage on-call** — a snooze silences the page for everyone, so being paged is not enough. --- ## Day-to-day ## How do rotations distribute shifts? Rotations use **round-robin** scheduling. Each shift slot gets one primary responder (and one backup, when backups are designated), cycling through the roster in form order. The default shift duration is **24 hours**. When you extend an existing rotation, the cycle continues where the original schedule left off rather than restarting at the first staff member. ## What happens when someone acknowledges an incident? The incident moves from **Active** to **Acknowledged**, and the escalation cascade stops for everyone — no further paging steps fire. The responder's record is updated to show they have taken ownership. Only active incidents can be acknowledged; acknowledging a resolved or cancelled incident has no effect. ## What does "Notify management on activation" do? When this toggle is on for a pool, every activation sends a notification to the active owners, admins and managers in the business — and anyone granted **manage on-call** — who can see that pool. This is in addition to the paging that goes to on-call staff. The toggle defaults to **on** for new pools and can be overridden per pool. ## Can I require resolution notes before closing an incident? Yes. Turn on **Require resolution notes** in the On-Call settings (Admin > On-Call Settings or the app's Settings tab). When enabled, the Resolve action blocks until the resolver enters notes — on both desktop and mobile. ## What is a handoff note? A handoff note is a free-text context message left on a pool by the outgoing on-call person — for example, "watch the 2 a.m. batch job." Only one active note exists per pool at a time; posting a new one supersedes the previous one. On-call managers and anyone currently on call for that pool can post or clear a handoff note. --- ## Escalation and paging ## How does the escalation cascade work? For **High** and **Critical** severity incidents, the primary responder is paged first. If they do not acknowledge within the configured wait time, the incident escalates step by step through additional channels — in-app, push, email, SMS, and voice. The moment anyone acknowledges, the entire cascade stops. Lower-severity incidents (Low, Medium) notify on-call staff directly without the cascade. ## What happens if no one is on call when an incident fires? The app falls back to staff from shifts that ended within the last 24 hours or start within the next 24 hours for that pool. This prevents a page from going completely silent when there is a gap between shift windows. ## I turned off escalation for On-Call, but incidents still escalate — why? On-Call follows your organization's escalation policy unless **Use an on-call-specific escalation policy** is on in On-Call → Settings. With the override off, turning escalation off anywhere else does not affect on-call incidents — they keep following the organization policy, which escalates high and critical incidents by default. To stop escalation for on-call incidents only, turn the override on, turn **Enable Escalation** off inside it, and save. Turning the override back off discards those on-call-specific settings and returns to the organization policy. --- ## When something looks wrong ## I'm on call but I'm not getting paged Check three things: (1) your on-call duty flag is enabled — if it was turned off, you are removed from the eligible staff list; (2) you are assigned to a shift that covers the current time — the dashboard shows your current status and upcoming shifts; (3) your notification preferences for **On-Call Alerts** have SMS and push enabled, and your phone number is on file (SMS requires it). If the incident was snoozed, notifications are suppressed until the snooze expires. ## My response shows as outside the SLA even though I responded quickly Response time is measured from the moment you were notified to the moment you recorded your response. The pool must have a **Response Time SLA** configured — new pools are pre-filled with the **Default Response Time SLA** setting (15 minutes unless an admin changed it), and an admin can clear it. If the SLA field is blank, no SLA measurement applies. If you are a manager who responded without having been paged, the clock starts from the incident's activation time, not from the moment you opened it. ## An incident disappeared from the Operations board The Operations board shows only active pools by default. If a pool was deactivated while an incident was still open, the incident stays visible on the Incidents tab and My On-Call, but drops off the Operations board. This is by design — the Incidents tab includes incidents from all pools regardless of pool status. --- ## Licensing and limits ## Does On-Call require a licence? Yes. On-Call Management requires a licence and is disabled by default. An administrator enables it from Admin → Apps → All Apps → On-Call. It is not turned on automatically for any tenant. ## Are there limits I should know about? | Item | Value | |---|---| | Severity levels | Low, Medium, High, Critical | | Incident statuses | Active, Acknowledged, Resolved (older incidents may show Cancelled) | | Default shift duration | 24 hours | | Minimum staff per pool | Defaults to **1** | | Escalation severity gate | High and Critical (by default) | | Fallback paging window | 24 hours before and after the current time | | Coverage gap alert | Runs every 6 hours, looks 7 days ahead; repeats about daily for a new gap, about weekly after a week, and stops after 30 days | | Snooze default (when no duration given) | 15 minutes | | Active incidents per page | 20 | | Resolved incidents per page | 10 | | Analytics window | Last 90 days | | Incident link types | Related, Duplicate | | Upcoming shifts on pool detail | Next 7 days | --- ## More help - [On-Call Management Overview](/help/articles/on_call_management_app_overview) - Ask AI — the assistant answers On-Call Management questions from these articles. **Keywords:** faq, on-call, on call, pager, incident, escalation, rotation, pool, coverage gap, SLA, handoff, acknowledge, snooze, who is on call, not getting paged, on-call-management, on_call_management --- # On-Call Management Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-14 How to set up and run on-call pools, rotations, incident response, and escalation in your organization. # On-Call Management ## 1. What it is On-Call Management lets you organize who is responsible for responding to urgent issues, when they are responsible, and how they get notified. You create pools of on-call staff, schedule rotations so coverage cycles automatically, and activate incidents that page the right people through in-app notifications, push, email and SMS — and, on high and critical incidents nobody acknowledges, a voice call. - **Enablement:** On-Call Management requires a license. An admin enables it from Admin → Apps → All Apps; it is off by default. - **What it is not:** On-Call Management handles incident paging and response tracking. It does not replace your regular shift scheduling — on-call shifts are separate from work shifts, even though both appear on the schedule. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps → On-Call** and enable the app. 2. Go to **On-Call → Settings** and set the **Default Response Time SLA**, **Notify Management By Default**, and **Require Resolution Notes** toggles to match your policy. 3. Go to **On-Call → Pools** and create at least one pool. Give it a name, choose a location (or leave it as **All Locations**), and set the **Response Time SLA** and **Minimum Staff Required** for that pool. 4. Enable staff for on-call duty. On the pool page, open the **Manage Staff** modal and enable the employees who should be eligible for on-call shifts. New employees are _not_ available for on-call by default — you must enable each person. 5. Create a rotation. From the pool, go to **Shifts → Create Rotation**. Choose a date range, a shift duration, and assign staff. The system creates round-robin shifts automatically: one primary per slot, cycling through your staff list in order. If you designate backup staff, one backup is also assigned per slot. 6. Confirm it worked. Return to **Operations** (the dashboard). You should see the pool listed with its currently on-call staff. On a phone, your on-call employees see the same status on the mobile On-Call screen. **What silently does nothing until a second thing is configured:** creating a pool alone does not put anyone on call. You must also enable at least one person for on-call duty _and_ create a rotation (or a manual shift) before the pool has live coverage. ## 3. How it fits together **Pool** — a named team responsible for a category of incidents (e.g. "IT Support On-Call" or "Emergency Response"). Each pool can be tied to a specific location or cover **All Locations**. A pool carries its own Response Time SLA, Minimum Staff Required, and management notification preference. You can have as many pools as you need. **Rotation** — a date range of automatically generated on-call shifts within a pool. When you create a rotation, you pick the start date, end date, shift duration (in hours), and the staff who participate. The system builds round-robin coverage: for a pool with three primary staff and 24-hour shifts, Staff A covers day 1, Staff B day 2, Staff C day 3, then back to Staff A. If you later extend the rotation, the cycle continues where it left off. **Shift** — a single on-call time block. Rotations generate shifts automatically, but you can also create one-off shifts manually. Each shift has a primary/backup designation and a priority number. Everyone on call at the moment of a page is paged at once; backup and priority only order the names on screen. > **Worked example:** You create a pool called "Night IT Support" at the Downtown location. You enable three employees — Alex, Jordan, and Sam — for on-call duty, then create a rotation from August 1–14 with 24-hour shifts. The system creates 14 shifts: Alex on Aug 1, Jordan on Aug 2, Sam on Aug 3, Alex on Aug 4, and so on. If you extend the rotation by 7 days, Sam picks up Aug 15 (continuing the cycle), then Alex on Aug 16, etc. **Incident (activation)** — what happens when someone triggers the pool. An activation pages the currently on-call staff, tracks their responses, records an activity timeline with comments, and stays open until someone resolves it. Each incident has a severity — **Low**, **Medium**, **High**, or **Critical** — and a status that moves from **Active** → **Acknowledged** → **Resolved** (or **Cancelled**). **Handoff note** — a message the outgoing on-call person leaves for the incoming one. Each pool shows one active handoff note at a time; posting a new one supersedes the previous. Anyone currently on call for the pool, or any on-call manager, can post or clear a note. **Incident links** — you can link related incidents together as **Related** or **Duplicate**. Links are bidirectional and visible from both incidents. **Escalation** — when escalation is enabled, high- and critical-severity incidents keep paging through a multi-step cascade: the first step goes to everyone on call at once, and later steps follow until someone acknowledges. Each step defines which channels fire (in-app, email, SMS, voice) and how long the system waits for an acknowledgement before advancing to the next step. On-Call Management can use the organization's default escalation policy or override it with an on-call-specific policy configured in **Settings → Escalation Policy**. Important: if you turn on the on-call-specific override and then turn **Enable Escalation** off within it, that disables escalation for on-call incidents entirely — it does not fall back to the organization default. **Roles and permissions** — who can do what is governed by scoped capabilities, not just the organization role: - **View** — any user who can see the pool's location can view pools, shifts, and incidents. Pools set to **All Locations** are visible to everyone. - **Manage** — create/edit pools, rotations, shifts, and enable or disable staff for on-call duty. Location-restricted managers can only manage pools at their assigned locations. - **Activate** — trigger an incident. Controlled separately from manage, so you can allow someone to page the team without giving them full pool management. - **Resolve** — close an incident. Also controlled separately. - **Analytics** — visible to managers and above, and to anyone granted the On-Call "Manage" capability (a delegated on-call manager does not need a manager role). - **Settings** — visible to admins and designated app admins. **Notifications** — an incident page goes out on every channel the responder can receive, following their notification preferences for **On-Call Alerts**: - **In-app** — always sent for activations (marked urgent, so it bypasses quiet hours). - **Push** — sent to the responder's phone when your organization has push notifications on and their On-Call Alerts preferences allow it. - **SMS** — sent if the user has SMS enabled and a verified phone number on file. Includes a deep link to the incident. - **Email** — sent as a separate email with the severity level in the subject line. - **Voice call** — the last step of the escalation cascade on high and critical incidents, when nobody has acknowledged and the responder has a verified phone number. The tenant-wide **On-Call Event Notifications** setting turns off routine on-call notices (rotation and shift assignments, coverage-gap alerts, acknowledgement and resolution updates); it never stops an incident page. **Coverage-gap alerts** — a background check runs every 6 hours across all tenants with On-Call enabled. For each active pool, it looks 7 days ahead. If any on-call shift in that window has fewer assigned staff than the pool's **Minimum Staff Required**, a rotation leaves an hour with nobody on call, or there are no on-call shifts at all, it sends an in-app notification to owners, admins, managers and anyone granted On-Call **Manage** who can see the pool. A new gap is announced about once a day; after a week it is repeated about once a week, and after 30 days it stops. Closing the gap (or the gap changing kind) resets that clock. ## 4. Running it ### Activating an incident 1. From the Dashboard, Operations, Pools, a pool's own page or Incidents, click **Activate**. 2. Select the pool, choose a severity (**Low**, **Medium**, **High**, or **Critical**), and describe the issue. 3. The system pages everyone currently on call for that pool — primaries and backups at the same time. The person who raised the incident is not paged about it. If no one else is on call at that moment, it falls back to staff from shifts that ended within the last 24 hours or start within the next 24 hours. 4. If **Notify Management on Activation** is on for the pool, owners, admins and managers — and anyone granted On-Call **Manage** — who can see the pool also receive a notification. ### Responding to an incident Paged staff see the incident in their notifications and on the **My On-Call** tab. They can: - **Acknowledge** — takes ownership and stops any running escalation cascade. - **Respond** — records availability ("Yes, I can respond" or "No, I'm not available" on desktop; **Available** or **Can't** on a phone), an optional estimated response time, and a note. - **Resolve** — closes the incident with resolution notes (required if the admin turned on **Require Resolution Notes**). ### Managing an open incident Managers (anyone with On-Call **Manage**) can also **transfer** an incident to a different pool (which pages that pool's on-call staff), **escalate severity** upward, and **snooze** notifications for a set number of minutes. Anyone who was paged for the incident can **add comments** to the activity log and **link** related incidents. ### Reviewing analytics Managers, admins, and anyone holding the On-Call "Manage" capability see the **Analytics** tab, which shows metrics over the last 90 days: total incidents, mean time to first response, mean time to resolve, SLA compliance percentage, per-pool breakdowns, and a weekly incident trend. ### Disabling a staff member from on-call You can remove someone from on-call eligibility from the pool's **Manage Staff** modal. If the person is still assigned to any current or upcoming on-call shift, the system blocks the change and asks you to reassign those shifts first — this prevents silently dropping coverage. ### Using industry templates The **Settings** tab includes a set of pre-built pool templates organized by industry: General Business, Healthcare, Retail, Hospitality, Manufacturing, Transportation, and Public Safety. Selecting a template creates new pools with names and descriptions appropriate to that industry. Existing pools are not changed. You can also load industry defaults from **Admin → On-Call Settings → Load Industry Defaults**. ### Using the mobile view Phone users are automatically redirected to the mobile On-Call screens for pools, incidents, and My On-Call. The mobile view supports acknowledge, respond and resolve, shows linked incidents, and lets you read and write the pool's handoff note. Transfer, severity escalation, snooze, and comments are available from the desktop view, which is always reachable via the **open desktop view** link at the bottom of the page. ## 5. Settings ### Organization-level settings These apply to all pools and are found in two places: **Admin → On-Call Settings** and the app's own **Settings** tab. Both write the same values. | Setting | Default | What it changes | |---|---|---| | **Default Response Time SLA** | 15 minutes | The SLA pre-filled when creating a new pool. Does not retroactively change existing pools. | | **Notify Management By Default** | On | Whether new pools default to notifying managers on activation. | | **Require Resolution Notes** | Off | When on, the resolve action requires notes before an incident can be closed. | | **Enable AI Agent** | On | Whether users can interact with on-call data through Ask AI. | | **Enable Industry Templates** | On | Whether the industry-template pool builder appears in the Settings tab. | ### Escalation policy (Settings tab) | Setting | Default | What it changes | |---|---|---| | **Use an on-call-specific escalation policy** | Off (inherits the organization default) | Enables a separate escalation configuration for on-call incidents. | | **Enable Escalation** | Copied from the organization policy (on unless an admin turned it off there) | When on, high/critical incidents keep paging step by step after the first page, which reaches everyone on call at once. Turning it off here, with the override on, stops escalation for on-call incidents only. | | **Severity Gate** | High and Critical | Which severity levels trigger the escalation cascade. | ### Per-pool settings Set when creating or editing a pool at **On-Call → Pools → [pool] → Edit**. | Setting | Default | What it changes | |---|---|---| | **Response Time SLA (minutes)** | The **Default Response Time SLA** setting (15 minutes unless changed) | Target response time for this pool. Drives the SLA compliance metric in Analytics and the per-response badge. | | **Minimum Staff Required** | 1 | The coverage-gap alert job runs every 6 hours and notifies managers when upcoming shifts in the next 7 days have fewer than this number of assigned staff. | | **Primary On-Call Pool** | Off | Shows a **Primary** badge on the pool. It does not change who is paged, the order pools are listed in, or which pool the Activate dialog picks. | | **Notify Management on Activation** | On | Whether owners, admins, managers and On-Call **Manage** holders who can see this pool are notified when it is activated. | | **Active** | On | An inactive pool stops appearing in the active-pools list and cannot be activated. Existing incidents remain visible. | ## 6. More help - **On-Call Management FAQ** — specific setup, operating, and troubleshooting questions. - Ask AI — the assistant answers questions about on-call pools, schedules, and incidents from these articles. **Keywords:** on-call, on call, pager, incident response, escalation, rotation, on-call pool, who is on call, coverage gap, SLA, handoff, on-call-management, on_call_management --- # Password Manager App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run Password Manager — personal vaults, team credentials, categories, security health, breach checks, sharing, and offboarding. # Password Manager ## 1. What it is Password Manager gives your organization a shared vault for team credentials and a private vault for each employee's own passwords. Entries are encrypted at rest, every access is audit-logged, and a built-in security engine flags weak, reused, or breached passwords. - **Enablement:** Password Manager requires a license. An admin enables it from Admin → Apps → All Apps and configures it from the in-app Settings page. - **What it is not:** Password Manager stores credentials your people use to sign in to other services. It does not replace your organization's own single sign-on or authentication settings — those live in **Admin → Security & Sign-On**. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Password Manager**, and enable it. 2. Open **Password Manager → Admin → Settings** and review the defaults. At a minimum, decide whether employees may store personal passwords (on by default) and whether team passwords are enabled (also on by default). 3. If you want to let non-admin employees create team passwords, choose one or more groups under **Who Can Create Team Passwords**. Without this, only admins and app admins can create team entries. 4. Optionally, set a **Default Password Expiry** so new login entries are automatically given a rotation deadline. 5. Default categories (Wi-Fi Networks, Software Licenses, Team Accounts, API Keys, Vendor Portals, Social Media, Banking & Finance, Personal) are seeded automatically the first time someone opens the app. You can add custom categories from **Admin → Categories**. 6. Confirm the app is working: open **Password Manager** from the sidebar, create a test entry, and verify it appears in the vault. ## 3. How it fits together ### Entry types Every record in Password Manager is an entry with a type that determines which fields it carries. - **Password** (the default) — a login credential with a username, password, optional URL, and optional one-time-password (TOTP) seed. - **Secure Note** — freeform encrypted text with no username or password fields. - **Credit Card, Identity, API Credential, Bank Account, Software License** — structured entries whose type-specific fields (card number, account number, license key, etc.) are stored as encrypted custom fields. An entry's type is fixed at creation and cannot be changed afterward. **Example:** a "Guest WiFi" entry of type Password holds the network name as the title, the SSID as the username, and the passphrase as the password. It is set to Team visibility with Public access so everyone in the organization can look it up. Its expiry is set to 30 days, so the nightly sweep marks it expired and the owner gets a reminder to rotate it. ### Personal vs Team Every entry is either **Personal** (Personal Passwords) or **Team** (Team Passwords). - **Personal** entries are private to the owner. No one else — including admins — can see, search, or access them. - **Team** entries are visible to other people based on their access level and any per-person sharing grants. A team entry's **access level** is either **Public** (anyone in the organization with the app enabled can view it) or **Restricted** (only people or groups explicitly granted access can view it). Group-based access uses the same groups as the rest of OneMango. ### Ownership and sharing Every entry has an **owner** — the person who created it. Owners can always view, edit, and delete their entries. For team entries, the owner or any admin can grant **View** or **Edit** access to individual people (to open an entry to a whole group, add the group to the entry's allowed groups on its edit form). Grants can carry an expiry date; a nightly sweep deactivates grants that have lapsed. Admins can also transfer ownership of a team entry to another person. ### TOTP (one-time passwords) Any Password entry can carry a TOTP seed — the same secret a 2FA authenticator app uses. Paste the setup key or the full `otpauth://` URI from the site's QR code, and the entry will generate rolling one-time codes directly on its detail page. Non-standard configurations (digit count, period, algorithm) are preserved from the URI. ### Password history When a login's password is changed, the previous value is saved automatically. Up to 20 past passwords are kept per entry. Editors can reveal or restore a prior password from the entry's detail page; every reveal is audit-logged. ### Password Agent When the **Enable Password Agent** setting is on, employees can look up, create, and rotate credentials through Ask AI in natural language. The agent uses semantic search, so a query like "wireless credentials" can find an entry titled "Guest WiFi". The agent cannot reveal secrets to anyone who wouldn't be able to see them through the app. ## 4. Running it ### Reviewing security health (admin) Go to **Password Manager → Admin → Analytics**. The Security Health panel analyzes all team login entries and flags: - **Weak passwords** — passwords that score below the strength threshold. - **Reused passwords** — the same password used on more than one entry. - **Stale passwords** — passwords that have not been rotated in 180 days. - **HTTP URLs** — entries whose URL uses unencrypted HTTP. The Analytics page also shows total counts, access statistics for the last 30 days, the most-accessed team entries, and how many entries are expiring within 30 days. ### Running a breach check (admin) From the Analytics page, click **Run Breach Check**. This sends a background job that checks each team login entry against the HaveIBeenPwned database using k-anonymity (no passwords leave your server in full). Results are kept for up to 30 days and the page says when the check last ran; a password changed since is no longer listed. The page shows which entries were found in known data breaches and how many times each appeared. ### Running a personal breach check Any user can check their own vault from **Password Manager → Security Checkup**. This page runs the same security-health analysis (weak, reused, stale, HTTP) on the entries that user owns. A **Run Breach Check** button triggers a personal breach check that covers both the user's personal and team-owned entries. ### Reviewing who has access (admin) Go to **Password Manager → Admin → Access Review** to see every team entry, its allowed groups, its access level, and every person who has been individually granted access. This answers "who can see X?" without opening entries one at a time. ### Managing categories Go to **Password Manager → Admin → Categories**. Categories organize entries and are visible in the vault's filter bar. Eight system categories are seeded by default. Admins can add custom categories. A system category cannot be deleted; a custom category can only be deleted when no entries use it. ### Importing passwords Go to **Password Manager → Passwords → Import** (also accessible from the import icon). Upload a CSV file or paste text. The importer previews parsed rows before committing. Each import can process up to 500 rows. You choose whether imported entries are personal or team, and you can assign a fallback category or let the importer create categories from a column in the source file. ### Exporting passwords From the Passwords list, click **Export**. This downloads a CSV of the entries in the list you are looking at — its tab, search and category filter. The export is audit-logged and is gated by the same identity-verification requirements as revealing a single password. The file holds every field of each entry, including card numbers, API keys, account numbers and other concealed fields, so you can use it as a backup. Importing it brings back each password, secure note, card, identity, API credential, bank account and software license with its kind and all of its fields. Expiry dates are not carried over (the organization's rotation policy applies to imported passwords), and categories named in the file are created only when an administrator imports it. Keep the file as safe as the vault itself, and delete it once you no longer need it. ### Sharing a credential externally (admin, off by default) When **Allow External Secure-Share Links** is turned on in Settings, admins can create an expiring, view-limited link for a team login or secure note that a non-OneMango recipient (a vendor, a contractor) can open. Links expire after 1, 7 or 30 days (never later than the entry's own expiry date) and allow 1, 3 or 5 views. The link landing page does not reveal the secret until the recipient explicitly clicks Reveal, so link-preview bots do not consume the view. Archived or expired entries can't be shared this way. Turning the setting off stops every outstanding link being served but does not revoke them — they work again if it is turned back on, so revoke a link to end it for good. The entry's External Share Links panel lists live links and the recent past ones, with how many views each used and when it was last opened. ### Offboarding When an employee leaves, the offboarding workflow automatically reassigns team entries they owned to their manager (or, if there is no manager or the manager can't open Password Manager, to a business admin) and deactivates their inbound access grants. It also revokes any external share links they created, and tells the owner of each affected entry. Personal entries follow the account's own lifecycle. ## 5. Settings All settings are at **Password Manager → Admin → Settings**. Only admins and app admins can reach this page. | Setting | Default | What it changes | |---|---|---| | Enable Password Agent | On | Whether employees can manage credentials through Ask AI. | | Allow Personal Passwords | On | Whether employees can create personal (private) vault entries. | | Allow Team Passwords | On | Whether team (shared) entries can be created at all. | | Show Password Strength Indicator | On | Whether the strength meter appears on entry forms and detail pages. | | Mask Usernames | Off | When on, usernames are masked with dots in lists, search and the phone's entry page; the desktop entry page still shows them. | | Require 2FA to View Passwords | Off | When on, a user must have two-factor authentication enabled on their account to view any entry. Users without 2FA see a banner on the vault list and can't reveal, copy or export passwords. | | Require Identity Verification to Reveal Passwords | Off | When on, the platform's step-up verification (the same 15-minute elevation used for sensitive HR data) is required before any password, TOTP code, or concealed custom field is revealed. | | Allow External Secure-Share Links | Off | Whether admins can create expiring, view-limited links for sharing a team credential with someone outside OneMango. | | Let People With Edit Access Share a Team Password | Off | Off: only a team password's owner and company administrators decide who can read it. On: anyone with edit access can grant and revoke access. | | Default Password Expiry (Days) | 0 (no expiry) | Number of days from creation until a new login entry expires. Entries past their expiry are marked expired by a nightly sweep and the owner receives rotation reminders at 7 days and 1 day before. | | Audit Log Retention (Days) | 365 | How long the record of who opened, copied, created or edited each password is kept before the nightly cleanup removes it. Minimum 30. | | Keep deletion and access-change records for (days) | 2555 (7 years) | How long the record that a password was deleted, that a person was given or lost their own access to it, or that its owner changed is kept. Never shorter than Audit Log Retention. A change to which groups can see a team password is an edit and follows Audit Log Retention. | | Max Personal Entries Per User | 0 (unlimited) | Cap on the number of personal entries a single user may have. Applies at creation and at import; team entries are not counted. | | Who Can Create Team Passwords | No groups selected (admins only) | Which employee groups are allowed to create team entries. Admins and app admins can always create team entries regardless of this setting. | ## 6. More help - **Password Manager FAQ** — specific questions about limits, troubleshooting, and day-to-day operations. - **Ask AI** — the Password Agent answers questions and manages credentials from the AI sidebar. **Keywords:** password manager, passwords, credentials, vault, team passwords, shared passwords, 2FA codes, TOTP, secure notes, breach check, password expiry, password health, security checkup, external sharing, password-manager, password_manager --- # Password Manager FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-14 Answers to common setup and operating questions about Password Manager — for the admin running it. # Password Manager FAQ Answers to common setup and operating questions about Password Manager. For what the app is and how to set it up from scratch, see the [Password Manager Overview](/help/articles/password_manager_app_overview). --- ## Setup ## Do I need to configure anything before my team can use it? Password Manager works out of the box once it is enabled and licensed. Both Personal and Team passwords are on by default. The Password Agent is also on by default, and entry encryption is automatic. The only features that require an admin to opt in are **Require 2FA to View Passwords**, **Require Identity Verification to Reveal Passwords**, and **Allow External Secure-Share Links** — all three are off by default. You will find all of these under **Settings** in the admin sidebar. ## Who can access admin settings, analytics, and access review? Any user who is an Admin or above for the organization, or who has been designated an App Admin for Password Manager. These roles see the **Admin** section in the sidebar, which contains Categories, Analytics, Access Review, and Settings. --- ## Permissions and access ## Who can create team passwords? Admins and App Admins can always create team passwords. For other users, the admin must specify which groups are allowed under **Settings → Who Can Create Team Passwords**. If no groups are selected, only admins can create them. Users who belong to at least one of the selected groups will see the Team option when creating an entry. ## Why can't some employees see certain team passwords? Team passwords have an access level. **Public** entries are visible to everyone who has access to the app. **Restricted** entries are visible only to group members listed in the entry's allowed groups, people with a direct per-person access grant, and admins. If an employee can't see a restricted entry, either their group isn't in the allowed list or they haven't been granted individual access. Check the entry's sharing panel or use the **Access Review** page to see exactly who can read it. --- ## Day-to-day ## How does the built-in 2FA authenticator work? Store a TOTP secret on any login entry — either paste a Base32 key or paste a full `otpauth://` setup URI from a QR code. The entry will then show a rolling one-time code with a countdown timer. Custom digit counts (6–8), periods (15–300 seconds), and algorithms (SHA1, SHA256, SHA512) from the setup URI are honored automatically. Every code view is audited. ## What happens when I rotate a password — is the old one kept? Yes. Each time a login's password is changed, the previous value is captured automatically into the password history. The app keeps the last 20 versions per entry. Users with edit access can view and restore any prior version — both actions are audited separately. ## How do I share a credential with someone outside the company? An admin must first enable **Allow External Secure-Share Links** in Settings. Once enabled, admins can create a tokenized, expiring link on a team login or secure note they manage (not on an archived or expired one). Each link lasts 1, 7 or 30 days — never past the entry's own expiry date — and allows 1, 3 or 5 views. The link lands on a page that does not reveal the secret until the recipient clicks an explicit Reveal button, so email and chat link-preview bots never consume the view. The link self-exhausts once all views are used or the expiry passes, and an admin or the entry's owner can revoke it at any time from the entry's External Share Links panel, which also shows past links and when each was last opened. ## What happens to someone's passwords when they leave the organization? When someone is offboarded, Password Manager automatically reassigns every team password they owned to their manager — or to an admin if their manager is not an active member or can't open Password Manager. It also deactivates all of their inbound per-person access grants and revokes the external share links they created, telling the owner of each affected password. Personal passwords are not touched and follow the account's own lifecycle. --- ## When something looks wrong ## "I can't see the password — it says I need to verify my identity" This means your admin has turned on **Require Identity Verification to Reveal Passwords**. You need to complete a step-up verification (a 15-minute elevated session) before any password, TOTP code, concealed field, or password-history entry is returned. Verify once and you can reveal secrets for the next 15 minutes without re-verifying. ## "The app says I need 2FA enabled to view passwords" Your admin has turned on **Require 2FA to View Passwords**. You need to enable two-factor authentication on your own account in your security settings before you can view, copy, export, or retrieve any password — including through the AI agent and the one-time code widget. The vault list shows a banner until you enable it, on desktop and on the phone. ## "I can't create a new password — it says I've reached the limit" Your admin has set a per-user cap on personal passwords under **Settings → Max Personal Entries Per User**. The default is unlimited (0 means no cap). If a cap is set and you have reached it, you can archive entries you no longer need to free up space — archived entries don't count against the cap. Contact your admin if you need the limit raised. ## "I imported my CSV but some rows say 'duplicate'" The import preview compares each row's title and username (case-insensitive) against your existing entries. If a match is found, the row is marked **Duplicate** and skipped to avoid creating a second copy. If you genuinely want to re-import, rename or delete the existing entry first. --- ## Security and auditing ## How are secrets encrypted? Passwords, notes, TOTP secrets, and concealed custom-field values are encrypted at rest using AES-256 non-deterministic encryption at the application layer, on top of per-business tenant isolation. This is not zero-knowledge — the server holds the keys so the AI agent, TOTP code generation, and breach checks can operate on the stored values. ## How does the breach check work? The breach check uses the HaveIBeenPwned Pwned Passwords API with k-anonymity: only the first five characters of a SHA-1 hash are sent to the service — the password itself, and even its full hash, never leave the server. The team breach check (admin-initiated from Analytics) scans up to 200 team logins, most recently updated first, and Analytics says when it stopped short. Each user can also run a personal breach check from the Security Checkup page, which covers every entry they own. Results are kept for up to 30 days and show when the check ran; a password changed after the check is no longer listed as breached. A lock prevents a second check from starting while one is already running. ## What gets logged in the audit trail? Every interaction with a secret is recorded: view, copy, reveal of concealed fields, TOTP code view, password-history view, password-history restore, create, update, delete, archive, restore, expiry, access grant, access revoke, AI retrieval, AI password view, attachment add, and attachment remove — 18 action types in total. Each audit row captures the user, timestamp, IP address, and device. On the web app, secret-returning endpoints are **fail-closed**: if the audit row cannot be written, the secret is not returned. Audit logs are retained for the number of days configured in Settings (default 365 days, minimum 30 days), and a nightly cleanup removes rows past the retention window. The records that a password was deleted, that a person was granted or lost their own access, or that ownership changed follow a second setting, **Keep deletion and access-change records for (days)** (default 2555 days — 7 years), which is never shorter than the first. --- ## Limits ## What are the limits I should know about? | What | Limit | |---|---| | Entry types | 7 (login, secure note, credit card, identity, API credential, bank account, software license) | | Custom fields per entry | 30 (text, concealed, URL, or date) | | Password history per entry | 20 versions | | Import size | 500 rows per import (CSV file max 1 MB) | | External share-link views | 1, 3 or 5 (1 by default) | | External share-link TTL | 7 days by default, 30-day maximum | | Bulk action (archive/categorize) | 100 entries at a time | | Security Checkup scan | 200 most-recently-updated entries | | Password generator default | 16 characters in the app, 12–64 via the AI agent | | Stale-password threshold | 180 days since the password was last rotated | | Weak-password threshold | Score below 60 out of 100 | | Audit log retention | Configurable, default 365 days (minimum 30) | | Deletion and access-change record retention | Configurable, default 2555 days (never shorter than audit log retention, maximum 3650) | | Max personal entries per user | Configurable, default unlimited | | TOTP digit count | 6–8 | | TOTP period | 15–300 seconds | ## Does Password Manager require a license? Yes. Password Manager requires a license and is disabled by default. An admin enables it from Admin → Apps → All Apps, and it becomes available to users with app access. --- ## More help - [Password Manager Overview](/help/articles/password_manager_app_overview) - Ask AI — the Password Agent answers Password Manager questions from these articles and can retrieve, create, rotate, and search credentials by natural language. **Keywords:** faq, password manager, vault, 2fa, totp, breach check, security health, team passwords, personal passwords, audit trail, import, export, sharing, encryption, offboarding, password-manager, password_manager --- # Payroll Connect App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to connect OneMango to your external payroll provider, sync employees, submit timesheets, and give employees access to their paychecks. # Payroll Connect ## 1. What it is Payroll Connect bridges OneMango to the external payroll system you already run. It syncs employee records, pushes approved timesheets to your payroll provider, imports paychecks so employees can view their pay stubs, and tracks compensation changes through an approval workflow. - **Enablement:** Payroll Connect requires a license. An admin enables it from Admin → Apps → All Apps and must configure at least one provider connection before anything works. - **What it is not:** Payroll Connect does not calculate payroll. If you want OneMango to prepare gross pay from approved timesheets for a processor that takes a file, use **Payroll Prep** instead. The two are separate apps; enabling one does not enable the other. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Payroll Connect**. 2. Open **Payroll Connect → Connections** and click the card for your provider (ADP Workforce Now, Workday HCM, Gusto, BambooHR, Paychex, Infor CloudSuite HCM, or Custom Integration; MangoPay is a demo provider for trying the app with sample data). 3. Enter your provider's API credentials (the fields vary by provider) and give the connection a name. 4. Click **Test & activate**. A passing test moves the connection from **Draft** to **Connected** and enables scheduled syncing. A failing test moves it to **Error** and stops all scheduled syncs. To recover, fix the credentials under **Edit**, use **Test Connection**, then click **Activate** — a passing test alone does not restart an Error or Inactive connection. 5. Go to **Connections → (your connection) → Employee Mappings**. Click **Sync Employees** to pull the employee roster from your provider. The sync matches employees by email; unmatched employees appear in the Unmapped list and can be mapped manually. 6. **Confirm it worked:** the Dashboard shows a card per connection with the employee count, health percentage, and last sync time. Your employees see their pay on **My Paychecks** (and the Payroll Connect tab on the phone) once paychecks are retrieved. **What silently does nothing until paired:** creating a connection without mapping employees means timesheet submissions and paycheck retrieval have nobody to operate on. Always sync or manually map employees before expecting data to flow. ## 3. How it fits together **Connections** — a connection is a set of credentials and settings that ties OneMango to one payroll provider. Each provider type can have one connection at a time. A connection has four statuses: **Draft** (just created, not yet tested), **Connected** (credentials validated, syncing enabled), **Inactive** (paused by an admin with **Pause**), and **Error** (the last test or sync failed). Only connected connections are picked up by the scheduled sync. Employees do not see paychecks from a Draft or Inactive connection. **Employee mappings** — each mapping links one OneMango user to their identifier in the payroll provider. Mappings are created automatically during an employee sync (matched by email) or manually by an admin. Without a mapping, that employee's timesheets cannot be submitted and their paychecks cannot be imported. > **Example:** you connect ADP Workforce Now and sync employees. The sync finds 150 employees in ADP. 140 match a OneMango user by email and receive an active mapping. The remaining 10 appear in the Unmapped list. You can map them manually by entering each one's ADP employee number, or you can review them as import requests (see below). **Timesheet submissions** — after a timesheet is approved inside the Timesheets app, Payroll Connect can push it outbound to the provider. This is always admin-initiated (from the **Timesheet Submissions** tab or queued in the background). It is never automatic — the scheduled sync does not submit timesheets, because pushing hours outbound becomes someone's pay and must not happen as a side effect of a cadence nobody set. **Paychecks** — the inbound counterpart: Payroll Connect pulls paycheck data from the provider and stores it. Employees see their pay stubs on **My Paychecks**, on the mobile app, and in the former-employee portal. Paycheck amounts are treated as sensitive data; viewing them in the admin interface requires a recently verified session (step-up authentication) and every view is logged to the audit trail. Employees can download a PDF pay stub from mobile or desktop. **Compensation changes** — these track proposed salary adjustments (raises, promotions, bonuses, adjustments, demotions). They move through an approval workflow: a requester creates the change, and a company admin approves or rejects it. Nobody can approve a change they requested or a change to their own pay. Once approved, a daily job applies a salary change to the employee's compensation record on its effective date automatically; a bonus is recorded but not applied to pay. Until that approval happens, the change sits in the queue and is not applied. The exception is a step increase raised automatically by a step schedule: its new pay is already in place when it reaches the queue, so approving acknowledges it and rejecting records an objection without undoing it. **HRIS sync** — a secondary data channel. When your organization has an HRIS integration configured under **Admin → Organization → Integrations** (such as BambooHR, Workday, or another Merge.dev-supported provider), Payroll Connect can browse the imported data in four tabs: Employees, Time Off, Departments, and Employee Payroll Runs. HRIS Settings in Payroll Connect controls which provider to pull from and whether live sync is on or off. **Import requests** — when an employee sync finds a person in the provider who has no OneMango account at all (not just unmapped), the sync can create an import request. Import requests sit in a review queue on the connection's **Import Requests** page. An admin approves (which creates the OneMango user and the mapping in one step) or rejects (a reason is required). Import settings on each connection control whether auto-creation is on or off, which fields are required, and an optional email domain allowlist. **Scheduled sync** — a background sweep runs every 15 minutes and checks every active connection. If a connection's sync frequency window has elapsed (2 hours for hourly, 26 hours for daily, 8 days for weekly), a full sync (employees + paychecks) is enqueued. The sync respects each connection's per-operation toggles: if paycheck retrieval is off, it syncs employees only and vice versa. Timesheet submission is never part of the scheduled sweep. **Health percentage** — the Dashboard and Connections pages show a health percentage per connection. This is the share of sync attempts in the last 7 days that succeeded. A connection that has never synced, is inactive, or has no sync logs in the window shows an em dash instead of a number. **Sensitive data protection** — paycheck amounts, salary details, and compensation changes are treated as sensitive pay data. Admin pages that reveal these values require a recently re-verified session (step-up authentication), and every view is written to the audit trail. The platform-wide **Hide Pay Amounts** setting (Admin › General Settings) is honored on the web and on the phone: when on, employees see no paycheck or salary figures, and the paycheck dashboard widgets are suppressed. **Who can do what** — three tiers. A **Contributor** for Payroll Connect can view connections, sync logs, mappings and paychecks, run a sync, and submit approved timesheets. An **App admin** can also create and change connections, credentials, mappings and import settings, and open Salary Management, Compensation Changes and the HRIS pages. Only a **company admin** can delete a connection, approve an import request, change a salary, export the salary report, or approve or reject a compensation change; company admins hold all three tiers automatically. Employees see their own paychecks on My Paychecks (web and phone) and in the former-employee portal after separation. Employees see only approved and processed compensation changes — pending and rejected proposals are not shown to them. **Payroll Connect vs. Payroll Prep:** Payroll Connect sends data to and receives data from your external payroll provider. Payroll Prep turns approved timesheets into a gross-pay report inside OneMango — it does not calculate taxes or net pay, and it does not pay anyone. They share no connections and no settings, and neither reads the other's records. They meet in Ask AI: when Payroll Connect holds an employee's paychecks, Payroll Prep's Payroll Agent answers "my last paycheck" from them, as the Personal Agent does, and lists year-end tax forms from Payroll Connect's providers. ## 4. Running it ### Syncing employees 1. Go to **Payroll Connect → Connections → (your connection)**. 2. Click **Sync Employees**. The sync pulls the roster from the provider, creates mappings for employees matched by email, and reports the count. 3. Review the **Unmapped** list. For each unmapped employee, you can enter their provider ID to create a manual mapping, or leave them unmapped. ### Submitting timesheets to the provider 1. Go to **Payroll Connect → Timesheet Submissions**. 2. The list shows approved timesheets that have not yet been pushed. Select the timesheets to submit. 3. Click **Submit**. Each timesheet is pushed to the provider individually. Successful submissions are marked **Submitted** (delivered to the provider); failures show a human-readable reason (credentials rejected, employee not mapped, provider unreachable) and can be retried. 4. For large batches, use **Queue in background** — the job sends up to 200 of the oldest waiting timesheets per run. 5. On a new connection, set **Send timesheets ending on or after** on its Edit page to the first pay period that provider pays, so timesheets already paid another way are not offered or sent. A timesheet already delivered through another connection is marked **Already delivered through …** and the background run skips it unless you select it. ### Retrieving paychecks 1. Go to **Payroll Connect → Connections → (your connection) → Paychecks** and click **Retrieve paychecks**, or use the Dashboard's **Retrieve Paychecks** quick action. 2. The retrieval pulls recent paychecks from the provider. BambooHR has no paycheck API and Infor syncs employees only, so neither offers this. 3. Retrieved paychecks appear under the **Paychecks** tab and become visible to employees on My Paychecks. ### Reviewing compensation changes 1. Go to **Payroll Connect → Compensation Changes**. 2. Filter by status (Pending, Approved, Rejected, Processed, Cancelled). 3. Open a pending change to see the employee, current salary, proposed salary, change amount, change percentage, and effective date. 4. **Approve** to allow the daily job to apply the change on its effective date. **Reject** (a reason is required) to stop it being applied. A step increase raised automatically is already in pay: approving acknowledges it, and rejecting records an objection without undoing it. 5. Changed your mind after approving? Open the change and use **Withdraw this approved change** (a reason is required). It works until the daily job applies the change; after that, correct the pay in Salary Management. ### Reviewing import requests 1. Go to **Payroll Connect → Connections → (your connection) → Import Requests**. 2. Filter by status (Pending, Approved, Rejected). Search by name, email, or provider employee ID. 3. Approve to create the OneMango user and the employee mapping in one step. Reject with a reason to skip the import; later syncs do not queue that person again unless you **Reopen** the request. 4. Configure the import policy under **Import Settings** on the same connection: auto-creation, required fields, and email domain allowlist. ### Managing salaries 1. Go to **Payroll Connect → Salary Management**. 2. The overview shows how many employees have validated salaries, discrepancies between OneMango and the provider, and employees with no payroll data. 3. Click an employee to see their salary analysis and recent paycheck history (the most recent 12 active paychecks are shown). 4. Export the salary report as CSV from the top of the page. ### Viewing sync logs 1. Go to **Payroll Connect → Connections → (your connection) → Logs**. 2. Each log shows the sync type, status, start time, duration, and record counts. 3. Filter to errors only to see recent failures. Error summaries never include raw provider data — they describe what to do (re-test credentials, check configuration, retry later). ## 5. Settings Payroll Connect has no app-level settings in the marketplace configuration. All settings live on each individual connection. ### Per-connection sync settings | Setting | Where | Default | What it changes | |---|---|---|---| | Sync frequency | Connection edit page | **Daily** | How often the scheduled sync runs. Choices: Hourly, Daily, Weekly, or Manual only. | | Timesheet sync enabled | Connection sync settings | **On** | Whether approved timesheets can be submitted through this connection. | | Paycheck retrieval enabled | Connection sync settings | **On** | Whether paychecks can be pulled from this connection. | | Notification email | Connection edit page | *Blank (falls back to business admins)* | Who receives sync-error email notifications. When blank, up to 5 business admins are notified. | | Notify on sync errors | Connection edit page | **On** | Whether an email is sent when a sync fails. | ### HRIS settings (app-admin only) | Setting | Where | Default | What it changes | |---|---|---|---| | HRIS sync provider | **Payroll Connect → Admin → HRIS Settings** | *None selected* | Which connected HRIS integration to pull data from. Selecting a provider turns live sync on; clearing it turns sync off. | | Employee creation policy | **Payroll Connect → Admin → HRIS Settings** | **Skip missing** | What happens when an imported employee has no matching OneMango user. Currently only "Skip missing" is implemented (unmatched employees are recorded as orphaned). | ## 6. More help - **Payroll Connect FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about Payroll Connect from these articles. **Keywords:** payroll connect, payroll integration, ADP, Gusto, Workday, BambooHR, Paychex, MangoPay, Infor, My Paychecks, paycheck, pay stub, timesheet submission, employee sync, compensation change, salary management, HRIS sync, payroll-connect, payroll_connect --- # Payroll Connect FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-18 Answers to common setup, pay-document and troubleshooting questions about Payroll Connect — for the admin running it and the employees who use it. # Payroll Connect FAQ Answers to common setup, pay-document and troubleshooting questions about Payroll Connect. For what the app is and how to set it up from scratch, see the [Payroll Connect Overview](/help/articles/payroll_connect_app_overview). --- ## Setup ## Do I need to set up a connection before anything in Payroll Connect works? Yes. Employee sync, paycheck import, tax documents and timesheet submission all need an active connection to a payroll provider. Payroll Connect requires a licence and is off by default, so an administrator first enables it from **Admin → Apps → All Apps**. Then create a connection on the **Connections** tab and enter your provider credentials. A new connection starts as a **Draft**; clicking **Test & activate** makes it **Connected** once the test passes. ## Which payroll providers can I connect to? Payroll Connect has built-in connectors for **ADP Workforce Now**, **Workday HCM**, **Gusto**, **BambooHR**, **Paychex** and **Infor CloudSuite HCM**. A **Custom Integration** connector works with your own API base URL, authentication and endpoints. **MangoPay** is a demonstration provider with pre-filled settings, for evaluating the app. ## Who can use the admin side of Payroll Connect? Access comes in three tiers: 1. A **Contributor** for Payroll Connect can view connections, sync logs, mappings and paychecks, run a sync, and submit approved timesheets. 2. An **App admin** can also create and change connections, credentials, mappings and import settings, and open Salary Management and Compensation Changes. 3. Only a **company admin** can delete a connection, approve an import request, change a salary, export the salary report, or approve or reject a compensation change. Company admins hold all three tiers automatically. Everyone else sees only their own paychecks and tax documents. --- ## Tax documents (W-2, 1099, 1095-C) ## Where do I find my W-2 or 1099? Open **My Paychecks** and select the **Tax documents** tab; on your phone, tap **Tax documents** in Payroll Connect. The tab lists your year-end forms by tax year. It appears only when your employer offers tax documents through OneMango. If it is missing, ask HR or payroll for a copy. ## Why do I have to verify it's me before I can download my W-2? Tax forms carry your full Social Security number, so every download asks you to confirm your identity first. You confirm with your password, or your personal PIN if you have set one. People who sign in through single sign-on confirm at their sign-in provider or with a one-time code. One confirmation covers tax-document downloads on the web and the phone for **15 minutes**. Every download is recorded in the audit trail. ## How do I let employees download their W-2 and 1099 forms? Turn on the **Tax documents** switch for the payroll connection at **Admin › Integrations**. It is off until you turn it on. W-2 and 1099 forms are available from **ADP**, **Gusto** and **Infor** connections. Forms are fetched from the provider each time someone downloads one and are never stored in OneMango. A Form 1095-C also appears on the same tab while Benefits Management is enabled. ## Can I still get my W-2 after I leave the company? Only if your former employer has turned it on in the Former Employee Portal. The portal is off by default. An admin enables it at **People › Settings › Former employees**, and it must also be switched on in the **Portals** app. Provider W-2 and 1099 forms need a separate switch in that section, **Let former employees download W-2 and 1099 forms from your payroll provider**, which is **off by default**. That switch also needs Payroll Connect enabled, pay amounts not hidden, and a connection with its Tax documents switch on. The portal signs people in with a code sent to their email or phone, and every download is recorded in the portal audit log. --- ## Permissions and access ## Can I hide pay amounts from employees entirely? Yes. Turn on **Hide Pay Amounts** in **Admin › General Settings** (payroll settings). Employees then lose paycheck figures on My Paychecks, the phone paycheck screen and the paycheck dashboard widgets. W-2 and 1099 forms are hidden with them, because they are pay documents. A Form 1095-C carries no pay figures, so employees still see it. Company admins are exempt and keep seeing everything. ## Why does viewing salary or paycheck data ask me to re-verify my identity? Salary and pay figures are sensitive data. **Salary Management**, **Compensation Changes** and each connection's **Paychecks** view ask for a recent identity confirmation (a "step-up") before showing figures. A confirmation lasts **15 minutes** and covers only the area you confirmed for. For example, confirming to read paychecks does not unlock tax-document downloads. Every reveal is recorded in the audit log. --- ## Day-to-day ## How are employees matched between OneMango and the provider? Each sync matches a provider record to a OneMango user by email address first, then by employee ID where the provider supplies one. Gusto connections match on email alone. A connection's **Field Mappings** decide which provider fields supply those values. You can also map someone by hand on the connection's **Employee Mappings** page by entering their provider employee ID. ## What happens when a sync finds an employee who isn't in OneMango? By default nothing is created: the record is logged and skipped. Change this on the connection's **Import Settings** page, under **When an employee exists in payroll but not in MangoApps**: - **Skip** (the default) — log it, import nothing. - **Review required** — queue it on the connection's **Import Requests** page, where a company admin approves or rejects it. - **Auto-create** — create the OneMango user automatically, but only when **Enable automatic user creation** is also ticked. ## How do I push approved timesheets to my payroll provider? Open the **Timesheet Submissions** tab, choose the connection, and submit approved timesheets individually or in bulk. A single submission from the page handles up to **25 timesheets**. For more, use **Queue in background**, which submits up to **200** per run. Timesheet submission is never automatic: scheduled syncs do not send timesheets. Sample-data timesheets are never offered. ## How does compensation change approval work? A compensation change (salary increase or decrease, bonus, promotion, demotion or adjustment) starts as **Pending**. A company admin approves or rejects it on the **Compensation Changes** tab. The person who requested a change cannot approve it themselves. Once approved, a daily job applies it on the effective date: it updates the employee's pay, records the change in their compensation history, and notifies them. Approved changes update OneMango only and are not sent to the provider, so record them in your payroll system as well. ## Can I turn off one operation without deactivating the whole connection? Yes. On the connection's edit page, under **What this connection may do**, turn off **Submit approved timesheets to the provider** or **Retrieve paychecks from the provider**. The connection then refuses that operation, for scheduled and manual runs alike, while everything else keeps running. --- ## When something looks wrong ## "My pay stub isn't showing up" Paychecks come from the connected provider, not from OneMango. Check three things: 1. The connection is active and has synced recently (the **Connections** tab shows the last sync). 2. The employee is mapped to their provider record on the connection's **Employee Mappings** page. 3. **Retrieve paychecks from the provider** is on for that connection. BambooHR has no paycheck API, so paychecks cannot be imported from a BambooHR connection. Gusto takes no timesheets from Payroll Connect: there is no verified Gusto endpoint for worked hours, so a Gusto connection is not offered as a timesheet target. Enter those hours in Gusto directly. ## A timesheet submission failed — what happened? The **Timesheet Submissions** tab shows the reason, such as "Employee not mapped to ADP". Failed submissions are not retried automatically. Fix the cause, such as mapping the employee or correcting credentials, then use **Retry** on the failed row. ## My compensation change was approved but the salary didn't update The change applies on the first daily run on or after its effective date. Check its **Scheduled application** card: - **Scheduled** — the effective date is still in the future. - **Ready to Apply** — it will apply on the next daily run. - **Failed** — the error is shown on the change. A change stops retrying after **3** failed attempts. - **No effective date** — the change has no effective date, so no daily run picks it up. - **Waiting** — the employee is no longer an active member. The change stays approved and applies if they are reactivated. A bonus never overwrites base pay, so the job refuses it; record bonuses in payroll directly. ## Why did my connection switch to "Error"? A failed connection test, employee sync or paycheck retrieval sets a connection to **Error**. Scheduled syncs run only for active connections, so syncing pauses. Open the connection, fix the credentials, test it again, and then activate it. ## The dashboard shows a connection's health as "—" instead of a percentage Health is the share of successful syncs over the last **7 days**. A dash means there is nothing to measure yet. The connection is inactive, has never synced successfully, or has no sync in that window. It does not mean the connection is broken. --- ## Sync schedule and limits ## How often does Payroll Connect sync automatically? Set **Automatic sync frequency** on the connection's edit page: **Hourly**, **Daily** (the default), **Weekly**, or **Manual only — never sync on a schedule**. A scheduler checks every **15 minutes**, so a sync starts within 15 minutes of becoming due. Scheduled syncs import employees and paychecks only. Sync-error emails are controlled by **Email on sync errors**, on by default. With no **Notification email** set, they go to up to **5** admins. ## Are there limits I should know about? | What | Limit | |---|---| | Timesheets submitted at once from the page | 25 | | Timesheets per background run | 200 | | Sync-error email recipients when no address is set | 5 admins | | Connection health window | 7 days | | Identity confirmation for pay data and tax documents | 15 minutes | | Automatic attempts to apply an approved compensation change | 3 | --- ## More help - [Payroll Connect Overview](/help/articles/payroll_connect_app_overview) - Ask AI — the assistant answers Payroll Connect questions from these articles. **Keywords:** faq, payroll connect, payroll integration, ADP, Workday, Gusto, Paychex, BambooHR, Infor, paycheck, pay stub, W-2, 1099, 1095-C, tax documents, tax forms, verify identity, former employee portal, timesheet submission, compensation change, sync, employee mapping, import request, payroll-connect, payroll_connect --- # Payroll Prep App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run Payroll Prep — generating gross-pay reports from approved timesheets, with overtime and shift-differential breakdowns. # Payroll Prep ## 1. What it is Payroll Prep turns approved timesheets into per-employee gross-pay reports — regular hours, overtime, and shift-differential premium pay — for any pay period you choose. Reports export to CSV, PDF, or JSON so you can feed them into your payroll system or keep them as an internal record. - **Enablement:** Payroll Prep is a licensed app. An admin enables it from Admin → Apps → All Apps; it is not turned on by default. - **What it is not:** This is a gross-pay engine, not a full payroll processor. It does not calculate tax withholding, net pay, direct deposit, or file tax forms. If you already run payroll through ADP, Gusto, Workday, or another provider, use Payroll Connect instead — that app bridges OneMango to your existing provider. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Payroll Prep**. The app requires a license and is not visible in the public app directory — it appears only for businesses that have it explicitly licensed. 2. **Configure pay periods.** Go to **Admin → General Settings → Payroll Settings**. Choose a pay period type (Weekly, Bi-weekly, Semi-monthly, or Monthly) and set the pay day offset — the number of days after a period ends when payment is processed. These settings are shared with Timesheets and Attendance and live outside any single app. 3. **Verify employee hourly rates.** Payroll Prep reads each employee's hourly rate from their employee record. If no rate is set, the line on the report page and in the PDF is marked **No rate on file** (its rate and pay show a dash); the CSV and JSON keep a 0.00 rate for processors that import them and flag the line — the CSV's **Rate Status** column, and `rate_on_file: false` in the JSON — making the gap visible rather than using an invented default. Set rates in the employee's compensation record before generating reports. 4. **Ensure timesheets are approved.** The report engine only picks up timesheets with an **Approved** status whose date range overlaps the report's pay period. Pending or rejected timesheets are excluded — approve them first. 5. **Grant access.** Admins see all reports by default. Managers and users with the **Payroll** permission (granted through the hierarchical permission system) see only the employees their own payroll access covers — usually the locations they have access to and their reporting line. Payroll Prep's App admins manage its settings without holding a global admin role and, like everyone else, see pay only for the people their own payroll access covers; Payroll Prep tells one who covers no one so, instead of generating an empty report. Payroll Prep appears in the app launcher only for the people it admits; publishing it (and any access groups) still decides which employees have the Payroll Agent in Ask AI for their own pay. 6. **(Optional) Enable the Payroll Agent.** Go to **Apps → Payroll Prep → Settings** and turn on **Enable Payroll Agent**. This lets employees ask the AI assistant about their own pay history, year-to-date earnings, and pay schedule via Ask AI. The agent is enabled by default when the app is set up. If the **Hide Pay Amounts** policy is on, it answers no pay questions for people pay is hidden from (administrators are exempt) and can only tell them their pay schedule and, where your organization issues one, list their Form 1095-C. **Silent-until-paired:** The app is enabled, but pay periods are not configured. The report form defaults to the current calendar month if no pay period settings exist — reports will still generate, but the pay-period alignment that the **Pay Periods** dropdown offers will be missing until you configure them in General Settings. **Timesheets must be enabled.** Payroll Prep reads from approved timesheets. If the Timesheets app is not enabled for the business, there is no data source and the Payroll Agent will also be unavailable. ## 3. How it fits together **Approved timesheets are the only input.** Payroll Prep does not read raw clock punches or shift assignments directly. It reads timesheets that have been submitted and approved in the Timesheets app. If an employee's hours are not on an approved timesheet for the period, they will not appear on the report. This is the most common reason for a "missing employee" on a report — the timesheet exists but has not been approved yet. **Overtime is a weekly threshold, not a period-wide total.** Hours are bucketed per 7-day week inside each timesheet, and only hours above the weekly overtime threshold count as overtime. The default threshold is 40 hours per week. The overtime multiplier defaults to 1.5×. Both values are set on the business and apply organization-wide to all reports. This distinction matters for bi-weekly and semi-monthly periods: two 38-hour weeks in a bi-weekly period produce zero overtime even though the period total is 76 hours. Overtime is always evaluated per week, not per period. **Premium pay is itemized by code.** If employees earn premiums — shift differentials (night, weekend, holiday, or custom codes defined in your scheduling setup), acting pay, or missed-break premiums (`MISSED_MEAL_BREAK`, `MISSED_REST_BREAK`) — the report itemizes premium hours and premium pay per code on each employee's line. Total pay on every line is Regular + Overtime + Premium. The premium breakdown exports in CSV as a pipe-delimited list in your organization's currency (e.g. `NIGHT_DIFF:4.5h/$67.50|WKND:8h/$56.00`). **Hourly rate comes from the employee record.** The report reads each employee's compensation rate from their employee record at the time the report runs. A salaried person's rate is their annual salary ÷ 2,080, kept to four decimals so rate × hours reproduces their pay to the cent. If no rate is set, the line is marked **No rate on file** — this makes missing data visible to the admin rather than substituting an invented default. Set rates before generating reports. **Pay amounts are sensitive data.** Viewing or downloading a report requires step-up identity verification (a 15-minute window after re-authenticating). Every view and download is audit-logged. If the business-wide **Hide Pay Amounts** setting is on, non-admin users see only hours — and export is blocked entirely for those users, since every export format includes pay figures. **Leave data is optional.** When generating a report, you can choose to include leave balances. When included, each employee's line shows their current leave balance, leave days used during the period, and unpaid leave hours (the portion of leave not covered by PTO, prorated to the pay period). This helps payroll teams identify shortfalls before processing payment. **Payroll Prep vs Payroll Connect:** These are two separate apps. Payroll Prep generates gross-pay reports internally. Payroll Connect syncs employees, approved timesheets and paychecks with an external payroll provider (ADP, Gusto, Workday, BambooHR, Paychex, or MangoPay). They keep separate data: Payroll Connect sends approved timesheets to the provider itself and never reads a Payroll Prep report. Use Payroll Prep when your processor takes a file, or Payroll Connect when it has a direct connection. They meet in Ask AI: the Payroll Agent lists year-end tax forms from Payroll Connect's providers, and when Payroll Connect holds the paychecks the provider issued, both the Payroll Agent and the Personal Agent answer an employee's "my last paycheck" from those, net pay included, and say so. ## 4. Running it ### Generating a report 1. Go to **Apps → Payroll Prep** and click **Generate Payroll Report**. 2. Choose a date range. The **Pay Periods** dropdown offers the last completed and the current period based on your pay period settings — select one, or enter custom dates. 3. Optionally filter by **Locations** to scope the report — leave it empty to include all locations — and choose whether to **Include Inactive Employees**. 4. Choose whether to include leave balances in the report. 5. Choose an **Export Format**: CSV, PDF, or JSON. 6. Give the report a name or leave it blank — a default name is generated from the date range (e.g. "Payroll Report 08/01/2026 - 08/15/2026"). 7. Click **Generate**. The report processes immediately and the result appears on screen. Non-admin users can only include locations they have permission to view. Attempting to include a location outside their access is blocked with an error. ### Reviewing a report The report detail page shows summary tiles — total regular hours, overtime hours, premium hours, and total pay — plus a cost breakdown chart. Below the summary is a per-employee table with hourly rate, regular/overtime/premium hours, and the corresponding pay columns. If leave balances were included at generation time, leave balance, leave used, and unpaid leave hours appear on each line as well. Non-admin users (managers, payroll-permission holders) see only employees at the locations they have access to and in their own reporting line. If the **Hide Pay Amounts** policy is active, pay columns are hidden and only hours are visible. Use the employee search field to filter the list by name or email. Results are paginated at 25 employees per page. ### Downloading and exporting Click **Download** on a completed report to get the file in the format you chose at creation time. The report's ⋮ menu also downloads it in the other two formats (CSV, PDF, or JSON), so a different format does not need a second report. The export includes all columns: employee name, email, hourly rate, regular/overtime/premium hours, pay amounts, shift-differential breakdown, shift count, and leave data (N/A when the report was generated without it); the CSV ends with a **Rate Status** column and, last, your organization's own **Employee Number**. The PDF ends on a total line, and the JSON carries totals for the people in the file. If the **Hide Pay Amounts** policy is active and you are not an admin, there is no Download — the report page says the file includes pay, so an administrator downloads it. Every export format includes pay figures, so there is no hours-only export. ### Regenerating a report Completed or failed reports can be regenerated from the report detail page. Regeneration reprocesses the same date range and filters against current timesheet data — useful if timesheets were approved or corrected after the original run. Non-admin users can only regenerate reports they created, or reports scoped to locations they have access to. A report scoped to a location that has since been deleted is not offered Regenerate — its people were found through that location — so generate a new report for the period instead. If a regenerate fails, the report stays as it was. ### Deleting a report The report creator or an admin can delete a report from the report list. Deletion removes the report and all its line items permanently. ### Email notifications A new report is generated while you wait, so no email is sent for it. When someone else regenerates a report you created, you receive a **Payroll Report Ready** email with a link to the report; regenerating your own report sends nothing. This notification is controlled by the **Payroll Report Ready Notifications** toggle in **Admin → Notification Settings**. ## 5. Settings Payroll Prep settings are split across two pages because pay periods and the pay-privacy flag are consumed by Timesheets, Attendance, and Scheduling as well. ### App settings — Apps → Payroll Prep → Settings | Setting | Default | What it changes | |---|---|---| | Enable Payroll Agent | On | When on, employees can ask the Payroll Agent about their own pay history, hours, overtime, year-to-date earnings, pay schedule, and benefit deductions via Ask AI. When off, the agent is hidden from Ask AI for all users. | ### Pay period settings — Admin → General Settings → Payroll Settings | Setting | Default | What it changes | |---|---|---| | Pay Period Type | Bi-weekly | The pay cycle: Weekly, Bi-weekly, Semi-monthly, or Monthly. Determines the default date ranges on the Generate Report form. | | Pay Period Start Day | Monday | The day of the week pay periods begin (Weekly and Bi-weekly only). | | Reference Start Date | *(none)* | A reference date to align weekly/bi-weekly cycles with your existing payroll calendar. Setting it auto-adjusts the start day. | | Pay Period Dates | 1, 15 | The two monthly dates where semi-monthly periods begin. | | Pay Day Offset | 3 days | Days after a period ends when payment is processed. Used to compute the pay date shown on reports and in the Payroll Agent. | | When pay day falls on a non-working day | Pay on the following business day | Shift the pay date to the next or previous business day when it lands on a weekend. | | Adjust pay day around holidays | Off | When on, a pay day landing on a business holiday is also moved using the direction above. | | Hide Pay Amounts | Off | Hides pay amounts from everyone except administrators across the platform — employees, managers and Payroll Prep app admins included; they see only hours and pay dates. Blocks non-admin payroll report downloads. The Payroll Agent answers no pay questions for people pay is hidden from — only their pay schedule and, where your organization issues one, their Form 1095-C. | ### Business-level overtime settings | Setting | Default | What it changes | |---|---|---| | Weekly overtime threshold | 40 hours | Hours worked above this in a single week count as overtime on the report. | | Overtime multiplier | 1.5× | The rate multiplier applied to overtime hours when calculating overtime pay. | ### Filtering the report list The **Apps → Payroll Prep** landing page lists all previously generated reports, newest first, paginated 10 per page. Use the filter bar to narrow by: - **Location** — show only reports that include a specific location. - **Pay Period Start** and **Pay Period End** — show only reports whose period falls within these dates. Click **Clear** to reset all filters. ## 6. More help - **Payroll Prep FAQ** — specific questions about report generation, overtime calculations, and export formats. - **Time & Attendance App Overview** — the attendance system that feeds timesheets into payroll. - **Shifts & Scheduling App Overview** — shift assignments and premium types that drive premium-pay calculations. - Ask AI — the Payroll Agent answers employees' questions about their own pay, hours, and pay schedule from completed payroll reports. It can show recent pay periods, a full breakdown of one period, year-to-date totals, pay-period comparisons, benefit deductions, and the upcoming pay schedule. When your company syncs paychecks through Payroll Connect, "my last paycheck" is answered from the paychecks your payroll provider issued. **Keywords:** payroll, payroll processing, gross pay, payroll report, overtime, premium pay, shift differential, pay period, pay schedule, labor cost, payroll export, payroll-prep --- # Payroll Prep FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Payroll Prep — for the admin running it. # Payroll Prep FAQ Answers to common setup and operating questions about Payroll Prep. For what the app is and how to set it up from scratch, see the [Payroll Prep Overview](/help/articles/payroll_app_overview). --- ## Setup ## Do I need the Timesheets app before Payroll Prep works? Yes. All hours come from approved timesheets. If there are no approved timesheets for a pay period, the report for that period will have no data. Timesheets must be enabled and employees must have submitted and approved timesheets before you generate a payroll report. ## Where do I configure pay periods, overtime, and pay dates? Pay-period settings (weekly, biweekly, semi-monthly, or monthly), the weekly overtime threshold, and the overtime multiplier are shared with Timesheets, Attendance, and Scheduling. Configure them once in **General Settings > Payroll Settings** — they apply across all four apps. The defaults are biweekly pay periods, a 40-hour weekly overtime threshold, and a 1.5× overtime multiplier. ## How do I turn the Payroll Agent on or off in Ask AI? Go to **Payroll Prep > Settings** and turn **Enable Payroll Agent** on or off. When enabled, employees can ask pay questions in the Ask AI sidebar. Only an admin or a Payroll Prep app admin can change this setting. When **Hide Pay Amounts** is turned on in General Settings, the agent stops answering pay questions for anyone pay is hidden from (administrators are exempt) — it can still tell them their pay dates and, where your organization issues one, list their Form 1095-C. --- ## Permissions and access ## Who can access payroll reports? Administrators, managers, and users who have been granted the **payroll** permission through your organization's role configuration. Managers and payroll-permission holders see only the people their own payroll access covers — usually the locations they oversee and their own reporting line — and no one else's pay. Administrators see all locations. A Payroll Prep **app admin** can manage settings but is still location-scoped for report data: they see pay only for people at locations where their role holds payroll access and in their own reporting line. An app admin whose role holds payroll access nowhere and who leads no one sees no one's pay, and Payroll Prep says so instead of generating an empty report. ## Why can't a manager see a report they didn't create? A non-admin user can only view a report if they created it or if all of the locations in that report's filter are within the locations they have access to. If the report includes any location outside their scope, they are blocked. Have an admin regenerate the report filtered to just that manager's locations, or grant the manager access to the additional locations. ## What is step-up verification, and why am I asked to verify my identity? Every time someone views or downloads pay amounts, the platform requires recent identity verification (a 15-minute window). This protects sensitive compensation data. Every view and download is also logged for compliance. If you are prompted, re-enter your credentials — the verification lasts 15 minutes before it is required again. --- ## Day-to-day ## What does a payroll report contain? Each report is a per-employee register for a pay period or custom date range. Per employee the report page shows hours (regular, overtime, total), hourly rate, regular pay, overtime pay, premium pay, total gross pay and shift count. Every export (CSV, PDF, JSON) carries the same figures plus premium hours, and the CSV adds an itemized breakdown by premium code such as night or weekend differentials. Optionally the export includes each employee's leave balance, leave days used in the period and unpaid leave hours (N/A — null in the JSON — when the report was generated without leave data). Report-level totals cover regular pay, overtime pay, premium pay and total gross: the PDF ends on a total line and the JSON carries totals for the people in the file, who generated the report and when (with `regenerated_at` when it was regenerated). ## Does Payroll Prep calculate taxes or net pay? No. All amounts are gross pay — regular pay plus overtime pay plus premium pay. Net (take-home) pay, tax withholding (federal, state, local, FICA), and deductions are not calculated or subtracted here. Export the gross-pay register and hand it to your bank, accountant, or payroll provider for the net-pay and tax steps. For full-cycle payroll with an external provider, use Payroll Connect instead. ## Can I regenerate a report with updated data? Yes. Open the report and choose **Regenerate**. The report is recalculated from the latest approved timesheets and current employee pay rates. The regenerated report appears right away. A report scoped to a location that has since been deleted cannot be regenerated; generate a new report for the period instead. If someone else regenerates a report you created, you receive a **Payroll Report Ready** email, provided **Payroll Report Ready Notifications** is on in Admin → Notification Settings; regenerating your own report sends no email. ## What export formats are available? Reports export to **CSV**, **PDF** (print-ready, landscape), or **JSON**. The CSV export includes an itemized premium-pay breakdown column in your organization's currency, a **Rate Status** column that flags a line with no pay rate on file, and ends with an **Employee Number** column holding your organization's own employee number (the first column, Employee ID, is OneMango's internal id). Choose a format when you create the report; a completed report's ⋮ menu also downloads it in the other two. ## How is overtime calculated? Overtime is calculated on a **weekly** basis within each timesheet — not across the entire pay period. Hours in excess of the weekly overtime threshold (default **40 hours**) in any 7-day week are overtime. Overtime pay equals the employee's hourly rate multiplied by the overtime multiplier (default **1.5×**). Both the threshold and the multiplier are configurable in General Settings. --- ## When something looks wrong ## "An employee's report line says No rate on file but they worked hours" The employee has no pay rate on their compensation record. On the report page Payroll Prep marks the line **No rate on file** (the rate and pay show a dash) rather than guessing a number — the PDF prints **No rate on file** and a dash for regular, overtime and total pay; the CSV and JSON keep a 0.00 rate for processors that import them and flag the line — the CSV's **Rate Status** column, and `rate_on_file: false` in the JSON — so finance can spot the gap. Set the employee's hourly rate in their compensation record and regenerate the report — the corrected rate will be picked up. ## "I enabled the Payroll Agent but employees say it's not available in Ask AI" Four things must all be true for the Payroll Agent to appear: (1) Payroll Prep is enabled for your organization, (2) the Timesheets app is enabled, (3) the **Enable Payroll Agent** switch in **Payroll Prep > Settings** is on, and (4) Payroll Prep is published to the employee (and they are in its access groups, if it has any) — publishing decides which employees have the Payroll Agent even though only managers, payroll-permission holders and its app admins see Payroll Prep itself in the app launcher. If **Hide Pay Amounts** is on in General Settings, the agent is still there but answers no pay questions for people pay is hidden from — it can only tell them their pay schedule and, where your organization issues one, list their Form 1095-C — so it cannot surface amounts the organization has chosen to suppress. ## "A manager can't see pay columns or download the report" If **Hide Pay Amounts** is turned on in General Settings, non-admin users see only hours on the report page, which tells them the report file includes pay so an administrator downloads it — every export format carries pay figures, so there is no Download for them. Admins still see and download full pay data. If this is not the intended behaviour, turn off **Hide Pay Amounts** in General Settings. ## "The report says 'failed' — what went wrong?" A report is marked failed only when an error stopped it from being built. Regenerate it; if it fails again, contact support. A period with no approved timesheets does not fail — the report completes with no employee rows, and the report page says why. ## "Why is someone missing from my report?" Only approved timesheets are counted. The report page lists how many people have hours in the period on a timesheet that is not approved, and how many had a timesheet approved after the report ran. Approve the timesheets, then regenerate the report. --- ## Licensing and limits ## Does Payroll Prep require a licence? Yes. It is a licensed marketplace app that is disabled by default. An administrator enables it per organization. It does not appear in the public app directory — it is visible only to organizations that have been explicitly licensed for it. ## Are there limits I should know about? - **Export formats:** CSV, PDF, JSON - **Pay-period frequencies:** weekly, biweekly, semi-monthly, monthly - **Weekly overtime threshold:** configurable, default 40 hours - **Overtime multiplier:** configurable, default 1.5× - **Report pagination:** 10 reports per page on the list view; 25 employees per page on a report - **Not included:** net pay, tax withholding, direct deposit, and tax-form generation (W-2, 1099) --- ## More help - [Payroll Prep Overview](/help/articles/payroll_app_overview) - Ask AI — the Payroll Agent answers employee pay questions from these articles and from their own payroll data. **Keywords:** faq, payroll report, gross pay, overtime threshold, premium pay, step-up verification, pay schedule, export, pay amounts, payroll agent, payroll, payroll-prep --- # People App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-14 What the People app does, how to set it up, and what an admin needs to know about profile fields, employee change requests, pay-details self-service, compliance tracking and the former-employee portal. # People ## 1. What it is People is the system of record for employee information. Admins decide which profile fields exist, who can see and edit each one, and how employee change requests are approved. Employees keep their own record current, including their direct deposit, W-4 and legal name. - **Enablement:** People requires a licence and is off until an admin enables it in Admin → Apps → All Apps. - **What it is not:** People is not payroll. It holds the record that Payroll Connect and other apps read. Year-end tax forms (W-2, 1099, 1095-C) are downloaded from **My Paychecks › Tax documents** in Payroll Connect, not from the People profile. ## 2. Standing it up 1. Enable **People** in Admin → Apps → All Apps. It appears in the left sidebar. 2. Go to **People › Admin › Profile Fields**. Decide which fields are active, which are required, who can see each one and who can edit it. First Name, Last Name and Work Email are always required. 3. Go to **People › Admin › Settings › Employee requests**. Confirm **Let employees request changes, with approval** is on. It adds the **Request Update** links employees use for fields they cannot edit themselves. With it off, the profile offers no way to ask for a correction. While **Enable Employee Self-Service** and the People AI Agent's **Record Management** capability are on, Ask AI can still send a request for an employee's own phone, work phone, address, time zone or emergency contact when it is a field they cannot edit, and it comes to **Pending Requests**. 4. Decide whether employees may change their own pay details. On the same section, turn on **Let employees change their own direct deposit and W-4**. It is off by default. 5. Grant access. Admins see the **Admin** group. Managers with direct reports see **Team › My Team**, and **Team › Pending Requests** when manager-level approvals are on. 6. Confirm it worked. Sign in as an employee and open **My Update Requests** from their profile. A **Pay and personal details** card lists the change forms your settings allow. **Silent-until-paired — check these before telling employees a form exists:** - The **Legal name** form appears only while **Let employees request changes, with approval** is on. - The **Direct deposit** and **Federal tax withholding (W-4)** forms appear only while **Let employees change their own direct deposit and W-4** is on. - The **Vehicle** form appears only while **Enable Custom Fields** is on *and* at least one vehicle field exists. Add them with **Load starter fields** in the ⋯ menu on Profile Fields: **Vehicle (Make & Model)**, **Vehicle Color** and **License Plate**. - The **Former Employee Portal** needs two switches: **Enable Former Employee Portal** in People settings, and the **Former Employee Portal** entry in the Portals app catalog. The Portals entry requires the Offboarding app. ## 3. How it fits together ### Visibility and edit permission Every field, built-in or custom, has two separate controls: - **Visibility** — who can see it: **Admins Only**, **Employee + Admins**, **Managers & Above**, or **Everyone**. - **Edit permission** — who can change it: **Employee Self-Edit**, **Manager Editable**, or **Admin Only**. Editing implies seeing. If you make a field Manager Editable, its visibility is raised to at least Managers & Above automatically. ### Direct edits vs change requests These are easy to confuse, and they behave differently: - A field set to **Employee Self-Edit** changes the moment the employee saves it. No approval is involved. - Any other field is changed by **request**. The request goes through your auto-approval rules, routing rules, workflows and delegations, then to an approver. Routing follows the field's edit permission. Manager Editable requests go to the employee's direct manager when **Enable Manager-Level Approvals** is on. Admin Only requests go to HR or admins, and managers are not told about them. An employee with no manager has their request sent straight to admin. ### Pay and personal details self-service Four change types have their own guided forms, on **My Update Requests** on desktop and the same card on the phone: | Form | Identity check | Approval | "Was this you?" notice | |---|---|---|---| | Direct deposit | Yes | Always | Yes | | Federal tax withholding (W-4) | Yes | Always | Yes | | Legal name | No — a supporting document is required instead | Always | Yes | | Vehicle | No | Only for fields employees cannot edit | No | - **Identity check.** Before the direct deposit or W-4 form opens, the employee verifies their identity again. The check is repeated when they submit. An admin using **View as** cannot file any of these four changes for someone else. - **Always approved by a person.** Direct deposit, W-4 and legal name changes can never be approved by an auto-approval rule. Bank and tax values are encrypted and shown masked to the last four digits. An approver verifies their own identity before opening one to review it. - **Direct deposit** takes a main account plus up to three more, each split by a fixed amount or a percentage. The main account receives what is left. - **Legal name** is blocked on the form if an identity provider manages the person's name. The employee is told to ask HR to change it there. ### The "this wasn't me" notice When someone changes their own direct deposit, W-4, legal name, email, user ID or phone number, People sends them a notice. It goes by email, including to the old address when the email itself changed. It goes by text message when they have no email and your organization sends texts. An in-app notification is also sent. The notice links to **Report a change you didn't make**, which needs no sign-in and works for 14 days. A report stops the change if it has not yet taken effect, and alerts your admins either way. **Worked example.** You set **Hold a new bank account before it takes effect (days)** to 3. On Monday, someone signed in as an employee submits a new bank account. The employee receives the notice, and an admin approves the request that afternoon. Because of the hold, the change is scheduled for Thursday. On Tuesday, the employee clicks **Report a change you didn't make**. The request is cancelled and their pay keeps going to the old account. Without a hold, the change takes effect the moment it is approved, and a later report can only tell HR to put it right. ### Compliance tiles vs the Profile Completion report The **Overview** shows five compliance tiles: **Emergency Contacts**, **Work Visas Expiring**, **I-9 Reverification Due**, **Probation Periods Ending** and **Missing Key Details**. Missing Key Details checks three fields only: phone, hire date and job title. The **Profile Completion** report under **Reports** checks eight: first name, last name, email, phone, hire date, job title, date of birth and emergency contact. The two numbers differ by design. Each tile depends on its field. If you deactivate **Visa Expiry Date** on Profile Fields, the visa tile and its reminders disappear too. ### Boundaries with other apps - **Shifts Scheduling** reads each person's **Schedulable** flag, which is on for new employees. - **Onboarding:** a W-4 filed through self-service is recorded against the employee's open onboarding W-4 step, if they have one. - **Connected HR systems:** approved changes are sent on to a connected HR system that holds that field. - **Payroll Connect** owns the **Tax documents** tab. Downloading a W-2, 1099 or 1095-C there asks for the same identity check. ## 4. Running it ### Reviewing change requests 1. Go to **People › Team › Pending Requests**. The Team group shows a count while requests wait. 2. Open a request to see the field, the old and new values, and its risk category (routine, standard or critical). 3. Approve or decline it. A bank or tax request asks you to verify your identity before its details open. A request no one decides is reminded, escalated to admin, and finally expired. The timings are under **Settings › Employee requests**. ### Handling a "this wasn't me" report Every admin gets a high-priority notification saying which of three things happened: the change was stopped, it had already taken effect, or it never took effect. In every case, check the person's account for other changes and make sure they can still sign in safely. When it had already taken effect, also put the change right in every system it reached. ### Acting on compliance alerts 1. Go to **People › Overview** and click a compliance tile. 2. Select employees and click **Send Reminders** to send each a notice, in the app and by email, to update their information. ### Changing the employee ID format 1. Go to **Settings › Employee IDs** and choose **Auto-generated**, **By employment type** or **Custom pattern**. 2. The format applies to new employees. To apply it to existing ones, use **Regenerate Mango IDs**, which shows a preview first. ### Running reports **People › Admin › Reports** holds Headcount, New Hires, Turnover, Diversity, Profile Completion, Compliance, Visa Expiry Tracker and EEO-4 reports. **Custom Fields Usage** appears while custom fields are on. ## 5. Settings All settings are at **People › Admin › Settings**, grouped by the section rail on the left. | Setting | Section | Default | What it changes | |---|---|---|---| | Enable Custom Fields | General | On | Shows custom fields and their management page | | Enable Employee Self-Service | General | On | When off, employees cannot edit their own profile; admins still can | | Let employees request changes, with approval | Employee requests | On for new organizations | Shows the **Request Update** links and the **Legal name** form | | Let employees change their own direct deposit and W-4 | Employee requests | Off | Offers the direct deposit and W-4 forms, behind an identity check | | Hold a new bank account before it takes effect (days) | Employee requests | 0 (no hold) | Delays an approved bank change so a "this wasn't me" report can still stop it | | Enable Manager-Level Approvals | Employee requests | On | Sends Manager Editable requests to the direct manager | | Send Reminder After (days) | Employee requests | 3 | When an undecided request reminds the manager | | Escalate to Admin After (days) | Employee requests | 5 | When an undecided request moves to the admin queue | | Expire Undecided Requests After (days) | Employee requests | 30 | When an undecided request expires; the employee must resubmit | | Who is notified about profile update requests | Employee requests | HR staff, or every admin when none is designated | Who hears about requests that need admin review | | Who can see the org chart | Org chart | Everyone in the organization | Limits the chart to managers, admins or one group | | Who can export it | Org chart | People with the People › Export permission | Who can download the chart | | Generation mode | Employee IDs | Auto-generated | How new employee IDs are created | | Default Probation Period (days) | Dates and alerts | 90 | Estimates probation end when no date is set | | Visa expiry dashboard window (days) | Dates and alerts | 60 | How far ahead the visa tile looks | | Probation end dashboard window (days) | Dates and alerts | 14 | How far ahead the probation tile looks | | Seniority Calculation Method | Seniority and agreements | Calendar Years (based on hire date) | Or Hours Worked, from approved timesheet hours | | Enable CBA Planner | Seniority and agreements | Off | Adds the CBA Planner under Admin | ### Former employees | Setting | Default | What it changes | |---|---|---| | Enable Former Employee Portal | Off | Gives terminated employees a sign-in link to their documents | | Answer staff questions about former employees in Ask AI | On | Lets your admins and HR staff ask Ask AI about former employees; former employees get no assistant | | Portal Access Duration (years) | 7 years | How long after termination the portal stays open to them | | Access Token Validity (days) | 3 | How long each sign-in link works | | Let former employees download W-2 and 1099 forms from your payroll provider | Off | Offers provider tax forms in the portal | | Allow On-Demand Experience Letters | On | Lets former employees request verification letters | | Allow Salary Information in Letters | Off | Includes pay in those letters | | Require Personal Email During Offboarding | On | Offboarding cannot finish without a verified personal email | | Auto-Send Portal Access on Termination | On | Emails portal access when someone is terminated | The W-2 and 1099 option carries a warning on the page. These forms show the person's full Social Security number, and the portal signs people in with an emailed or texted code, not a password. Forms come only from payroll connections whose **Tax documents** switch is on. ## 6. More help - **People FAQ** — specific setup and operating questions, limits and troubleshooting - **Employee Data Administration** — the platform admin guide for the related admin surfaces - **Ask AI** — the assistant answers questions about People from these articles **Keywords:** people app, employee data management, employee profiles, profile fields, custom fields, org chart, compliance tracking, profile update requests, self-service, direct deposit, w-4, legal name change, identity check, this wasn't me, former employee portal, mango id, employee code, employee-data-management, employee_data_management, people --- # People FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-20 Answers to common setup and operating questions about People — for the admin running it. # People (Employee Data Management) FAQ Answers to common setup and operating questions about People. For what the app is and how to set it up from scratch, see the [People Overview](/help/articles/employee_data_management_app_overview). --- ## Setup ## Does People require a licence? Yes. People requires a licence and is disabled by default. An administrator enables it from Admin → Apps → All Apps. It is opt-in per tenant — it will not appear for employees until an admin turns it on. ## How many standard fields does People ship with? People ships with more than 70 standard fields organized into seven sections: Personal Information, Contact Information, Employment Details, Compensation, Compliance & Legal, Onboarding, and Offboarding. Each field can be individually toggled active or inactive, set as required or optional, and given an edit permission level (employee, manager, or admin only). ## What custom field types can I create? There are 16 custom field types: text, textarea, number, email, phone, URL, select, multiselect, radio, checkbox, date, datetime, time, file, currency, and rating. Each custom field is filed under a profile section — the same sections the standard fields use, plus Additional Information — so it appears under that heading on Employee Profile Fields and on the profile. Each custom field supports ordering, min/max and regex validation rules, and a per-field usage report. --- ## Permissions and access ## Who can see and edit custom fields? Each custom field has independent visibility and edit permission settings. Visibility has four levels: **Everyone** (any colleague; it can also be a People directory column), **Managers & Above** (the employee's manager chain), **Employee + Admins** (the employee and admins), and **Admins Only**. Edit permission has three levels: **Employee Self-Edit** (the employee can update it), **Manager Editable** (the employee's manager can update it), and **Admin Only** (only admins can change it). Admins can always see and edit all fields regardless of these settings. ## Who can view the org chart? By default the org chart is visible to everyone. An admin can narrow it — to managers and administrators, administrators only, or one group — by changing **Who can see the org chart** in **People › Admin › Settings › Org chart**. Administrators always see it. --- ## Day-to-day ## How does the profile update approval workflow work? When an employee changes a field they cannot directly edit (an admin-only or manager-only field), the change is submitted as an update request. If **Enable Manager-Level Approvals** is on (on by default), manager-level requests route to the employee's direct manager. Admin-level requests go to the admin queue. The reviewer sees impact flags for payroll, benefits, and compliance, and can set a future effective date before approving. Approved future-dated changes apply automatically on the effective date. Only one pending request per employee per field is allowed at a time. The employee can cancel a pending request and resubmit. ## What are the SLA and escalation settings for update requests? Three settings control the lifecycle of pending requests: 1. **Reminder days** — a reminder is sent to the assigned manager after this many days (default **3**, range 1–10). 2. **Escalation days** — the request escalates from the manager queue to the admin queue after this many days (default **5**, range 3–14). 3. **Expiry days** — requests still pending after this many days auto-expire and the requester is notified to resubmit (default **30**, set to 0 to disable). A daily job enforces all three. If the employee's manager changes while a request is pending, the request is automatically escalated to an admin. ## What happens when an update request is approved for a field that affects payroll, benefits, or compliance? The request is flagged as **High Impact** and shows which systems are affected: Payroll, Benefits, and/or Compliance Reporting. Specifically: first name, last name, date of birth, address, marital status, and similar fields trigger payroll and benefits impact. Gender, date of birth, and marital status trigger compliance impact. The impact flags are informational for the reviewer — the field change is applied to the employee record on approval, and a connected HRIS, SFTP file drop or webhook receives the approved change; payroll sync depends on the Payroll Connect app being configured. --- ## Compliance monitoring ## What compliance checks are built in? Five checks, each with its own drill-down view and the ability to send bulk reminders to the selected employees, in the app and by email: 1. **Missing emergency contacts** — employees with no emergency contact on file. 2. **Visas expiring soon** — employees with a work visa expiring within a configurable window (default **60 days**, range 1–365). 3. **I-9 reverification due** — employees with I-9 reverification due within the next **30 days** (hard-coded). 4. **Probation periods ending** — employees whose probation ends within a configurable window (default **14 days**, range 1–90). 5. **Incomplete profiles** — employees missing a phone number, hire date, or job title. ## Can I change the probation period length for new hires? Yes. The default probation period is **90 days** and can be set between **1 and 730 days** in **People › Admin › Settings › Dates and alerts**. The notification window for probation endings (how far in advance probation-ending employees appear in the compliance dashboard) is a separate setting that defaults to **14 days** (range 1–90). --- ## When something looks wrong ## "I revealed a sensitive field but now it's asking me to verify again" The step-up verification (password or personal PIN) lasts **15 minutes**. After that, you must re-verify before viewing any masked field again. If you fail verification **5 times**, you are locked out for **15 minutes** before you can try again. This applies to SSN, date of birth, annual salary, hourly rate, bank account and routing numbers, and paycheck figures. ## "My employee can't request a profile update" The employee can only submit update requests for fields they are not allowed to directly edit. If a field's edit permission is set to **Employee Self-Edit**, the employee changes it directly — no request is needed. Also, only one pending request per employee per field is allowed; if there is already a pending request for that field, a new one cannot be submitted until the first is resolved. ## "The org chart isn't showing for some employees" If **Who can see the org chart** (People › Admin › Settings › Org chart) is narrowed, only the audience it names — plus administrators — can see it. Set it to **Everyone in the organization** if you want it visible company-wide. ## "A profile update request was auto-expired" Pending requests that sit unresolved past the configured expiry window (default **30 days**) are automatically expired by the system, and the employee is notified to resubmit. You can change this window or disable auto-expiry (set to 0) in People › Admin › Settings › Employee requests. --- ## Employee ID and former employee portal ## How does the Mango Employee ID work? There are three generation modes, configurable in the People settings: 1. **Auto-generated** (default) — generates an ID in the format E + 7 random digits (e.g., E1234567). 2. **By employment type** — uses a prefix per employment type + separator + sequential number (for example FT-000001 for Full-Time, PT for Part-Time, CT for Contractor); the page lists every employment type with its prefix, which you can change. The separator can be a hyphen, slash, or period, and the sequential number is zero-padded to 4–8 digits (default 6). 3. **Custom pattern** — a custom token template up to 24 characters. Bulk regeneration is available to reissue IDs across the workforce when switching modes. ## How does the former employee portal work? When an employee is terminated, they can receive a secure token link (via email or SMS) to access their historical employment records. The portal settings are: - **Access duration** — how long after the termination date a former employee can use the portal (default **7 years**). - **Token validity** — how long each token link remains active (default **3 days**; can be refreshed). - **Experience letters** — whether former employees can request experience or verification letters (on by default). - **Salary in letters** — whether experience letters include salary information (off by default). - **Auto-send on termination** — whether the portal access link is automatically sent when someone is terminated (on by default). The former employee signs in with a personal email or phone number on their employee record: one that was on file when they left, or one HR has verified on their offboarding plan since. A contact that changed after they left receives no token until it is verified. All portal access is audited. --- ## Profile completeness ## How is the profile completeness score calculated? The score is a percentage based on 8 fields: first name, last name, email, phone, hire date, job title, date of birth, and emergency contacts (at least one). Each filled field counts equally — a profile with 6 of 8 fields completed shows 75%. The incomplete-profiles compliance check uses a narrower set (phone, hire date, job title) because first name, last name, and email are always required at account creation. --- ## More help - [People Overview](/help/articles/employee_data_management_app_overview) - Ask AI — the assistant answers People questions from these articles. **Keywords:** faq, employee data, people directory, custom fields, profile update, approval workflow, compliance monitoring, sensitive PII, org chart, former employee portal, mango employee id, probation period, emergency contacts, employee-data-management, employee_data_management, people --- # Performance Management App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-01 How to set up and run Performance Management — modules, review templates, performance cycles and their elements, goals, 360 and continuous feedback, calibration, merit planning, automation and reminders. # Performance Management ## 1. What it is Performance Management runs employee appraisals: review templates, the reviews themselves, and the cycles that organize them. Around the review it adds optional modules for goals, 360-degree feedback, continuous feedback, competencies, development plans and merit planning. Employees complete self-assessments and track their goals. Managers assess their teams and approve what is waiting on them. Admins configure the modules, templates, cycles and automation. - **Enablement:** Performance Management is a licensed app. An admin enables it from **All Apps** in the admin sidebar. - **What it is not:** Turning the app on does not turn on every feature. Only **Performance Reviews** and **Goals Management** start switched on. 360 feedback, continuous feedback, competencies, development plans and merit planning stay hidden until you enable each module. ## 2. Standing it up 1. In the admin sidebar, open **All Apps**, choose **Performance Management**, and enable it. 2. Open the app and go to **Settings → Module Configuration**. Each feature is a card with an **Enable** or **Disable** button; the Performance Reviews card shows **Always On** instead. Turn on the modules you plan to use. Admins also see **Settings → Setup Wizard**, which walks through modules, review templates, goals, users and integrations in one pass. 3. Go to **Settings → Templates** and create at least one review template. Use **Create Template with Wizard** for a full template, or **Quick template** for a one-screen version. A review cannot be created without a template. 4. Decide your review rules. On the **Performance Reviews** module card choose **Settings**, then set the **Default Rating Scale** and the **Workflow & Approval** switches (see section 5). 5. Create the first reviews. Go to **Team → Team Reviews** and choose **Create New Review** for one person, or **More actions → Bulk Assign** for a department, location or role. 6. Confirm it worked. Each employee sees the review under **My Performance → My Reviews**. Each reviewer sees it under **Team → Team Reviews**. Who gets which tab: | Tab | Who sees it | |---|---| | **My Performance** | Everyone | | **My Rewards** | Everyone, when the Compensation Management app is enabled | | **Team** | Managers and above, Performance Management app admins, and anyone with direct reports | | **Compensation** | Admins, HR admins and app admins, when the Merit Matrix module is on | | **Analytics** | Admins, HR admins and app admins | | **Settings** | Admins, HR admins and app admins | **Silent-pairing notes — things that do nothing until a second thing is set:** - **Merit Matrix needs Compensation Management.** The module cannot be enabled until the Compensation Management app is on for your organization. - **Development Plans needs Goals Management.** Disabling Goals Management also disables Development Plans. - **Automation rules need the master switch.** Rules create nothing while **Enable Automation** is off, and it is off by default. - **Autonomous AI Capabilities need the AI mode.** The four switches do nothing until the AI mode is set to Approve or Auto on the AI Console. ## 3. How it fits together **Modules** — A module is one feature area you can switch on or off. **Performance Reviews** is the core module and is always on. The others are **Goals Management**, **Job Duties & Responsibilities**, **360-Degree Feedback**, **Merit Matrix**, **Development Plans**, **Continuous Feedback**, **Competency Assessment & Skills Tracking**, **Meeting Scheduling**, **Progress Tracking**, **Notes & Documents**, **Disciplinary Actions** and **ADP Integration**. **Predictive Analytics** also appears as a card marked **Coming Soon**; it cannot be switched on yet. A module that is off removes its entries from every tab, so "I can't find 360 feedback" usually means the module is off. **Template, review, cycle, element** — These four nest, and each answers a different question. - A **template** decides what a review asks and who fills it out. - A **review** is one employee's appraisal for one period, built from one template. - A **performance cycle** is a dated container that organizes reviews, such as a year. Its type is **Annual**, **Quarterly** or **Custom**. - An **element** is one round of reviews inside a cycle. It carries the review type, the period, the due date and the template. A worked example: `2026 Annual Cycle (Jan 1 – Dec 31)` › `Q1 Quarterly element (Jan 1 – Mar 31)` › `one Quarterly review per employee` The same cycle can hold four quarterly elements and one annual element. An element's timing is one of three choices: | Timing | What it means | |---|---| | **Fixed window — same dates for everyone** | Every employee is reviewed for the same period | | **Each employee's hire anniversary** | Each review falls on that person's own anniversary | | **A set number of days after hire** | Milestone reviews, 30, 60 and 90 days after hire by default | A cycle and each of its elements show **Upcoming**, **In progress** or **Past**, read from their dates — there is nothing to activate. A cycle can be edited until it is marked complete; an archived cycle is read-only. **The stages of a review** — A review moves through five stages, and the label tells you who is holding it. `Not started` › `In progress` › `Pending Approval` › `Approved` › `Archived` - While a review is not started or in progress, the employee and the reviewer complete their parts. Its badge names who it is waiting on — for example **Draft**, **Waiting on Employee**, **Waiting on Manager** or **Ready for Meeting**. - **Pending Approval** means the reviewer has submitted the final review and it is waiting for an approver. - **Approved** locks the overall score. Approval also sends the completion email and, when **Enable Automation** is on, runs your outcome rules. The person who submitted a review for approval cannot approve it themselves. On a review with a manager assessment that is the reviewer, so someone else must approve it. If you turn **Require Manager Approval** off, the reviewer's final submission approves the review immediately. **Four kinds of feedback, often confused** — They are separate records with separate rules. | What | Who writes it | Where it lives | |---|---|---| | **Self-assessment** | The employee, about themselves | Inside the review | | **Manager review** | The assigned reviewer | Inside the review | | **360 feedback** | Nominated colleagues, anonymous by default | Its own 360 feedback cycle | | **Continuous feedback** | Any colleague, at any time | **My Peer Feedback**, outside any cycle | A template decides whether a review has a self-assessment, a manager review or both. 360 feedback is never collected by a template. It runs as its own cycle with a nomination phase and then a feedback phase; a template can only choose to show the employee's 360 results as a card on the review. Continuous feedback is one of four types — **Praise**, **Constructive**, **Goal Progress** or **General** — and carries a visibility of **Private**, **Manager**, **HR** or **Public**. **Three different "cycles"** — A performance cycle organizes reviews. A 360 feedback cycle collects nominated feedback. A merit matrix has its own planning cycle for pay. Creating one does not create the others. **Goals, and how they differ from OKR Hub** — A goal here belongs to one employee, or to a department. It has a start date, a target date, a priority and a progress percentage. Optional **Milestones** set your own progress targets by date, for goals where most work happens late or in phases. New goals follow the **Approval Workflow Type** you choose. Under the default, **Two-Tier (Employee → Manager)**, the employee submits and the manager approves. **Three-Tier** adds a leadership approval. **No Approval Required** makes goals active at once. OKR Hub is a separate app that owns company objectives and key results. When OKR Hub is enabled and its sync with Performance Management is on, a goal's page shows a **Linked Key Results** card with **Attach Key Result**. The goal stays in Performance Management; the key result stays in OKR Hub. **Three switches that sound alike** — Each controls something different, and none of them affects the others. - **Enable Automation** controls automatic creation: reviews, 360 feedback cycles, and follow-up plans after a review is approved. - **Send performance review due & overdue reminders** controls reminder emails for reviews that already exist. - **Autonomous AI Capabilities** controls what the AI may do unprompted, such as launching review cycles or sending reminders. **Merit planning** — A merit matrix calculates a recommended increase for each employee in scope. It moves through **Draft**, **Calculating**, **Pending Approval**, **Approved** and **Finalized**. It belongs to the Merit Matrix module, which depends on the Compensation Management app. **Mobile** — On a phone, employees can complete a self-assessment, acknowledge a review, manage goals and give or request feedback. Managers can complete and approve reviews and approve goals. Setup, templates, cycles and merit planning are desktop-only. ## 4. Running it ### Organize reviews into a performance cycle 1. Go to **Analytics → Performance Cycles** and choose **Create Cycle**. Managers reach the same page, read-only, from **Team → Performance Cycles**. 2. Open the cycle and use **Add an element → Plan a new element**. Pick the review type, timing, period, due date and template. 3. Each element shows where it is in time, read from its dates, and offers what fits: - **Upcoming** (its period hasn't started): **Create reviews**, or **Set up automation** to make a rule that creates them on a schedule. - **In progress** (started, not yet past its due date): **Create reviews**, or **Add existing reviews** that were already sent. - **Past** (its due date has passed): **Add past reviews** that already happened. The cycle itself shows **Upcoming**, **In progress** or **Past** the same way. Its **⋮** menu holds **Mark Complete** (it stops collecting new reviews) and, after that, **Archive** (it becomes read-only). ### Create reviews for a group 1. Go to **Team → Team Reviews** and choose **More actions → Bulk Assign**. 2. Work through the three steps: **Configure**, **Select Employees**, **Review & Confirm**. Bulk Assign is available to admins, HR admins and app admins. ### Approve what is waiting **Team → Manager Approvals** gathers everything waiting on you in one place: performance reviews, development plans, 360 nominations, goals and competency assessments. Approving a review there has the same effect as approving it from the review page. ### Run a 360 feedback cycle 1. Enable the **360-Degree Feedback** module, then go to **Team → 360 Feedback Management** and create a cycle. 2. Choose **Activate Cycle**. Nominations open automatically if the start date has arrived; otherwise choose **Start Nominations** on or after that date. 3. Review nominations. When the cycle requires manager approval, pending nominations wait to be approved or declined. 4. Choose **Start Feedback Phase**, which appears once the nomination deadline has passed. Use **Send Reminders** for overdue participants, and finish with **Complete Cycle**. Employees see their nominations and results under **My Performance → My 360 Feedback**. ### Compare scores before finalizing **Analytics → Team Calibration** lists each employee's review status, overall score, goals, competencies and progress side by side, with a score distribution chart. Use it to align draft ratings before reviews are approved. ### Plan merit increases 1. Go to **Compensation → Merit Matrices** and choose **Create Merit Matrix**. 2. Open the matrix and choose **Start Calculations**. 3. When it reaches **Pending Approval**, choose **Approve**, then **Finalize**. Finalizing cannot be undone. 4. Use the **Reward Letters** panel on the matrix to generate and send letters. Employees read theirs under **My Rewards → My Reward Letters**. ### Automate review creation 1. Go to **Settings → Review Management** and choose **Manage Rules**. 2. Add a rule. A review rule fires on a cycle element, a hire anniversary, a tenure milestone, quarterly, twice a year or in a fixed month. 3. Turn **Enable Automation** on. Rules are checked once a day. ## 5. Settings Settings are under the **Settings** tab. Module-level settings open from the **Settings** button on a module card in **Module Configuration**. Seven cards show one while the module is on: Performance Reviews, Goals Management, 360-Degree Feedback, Continuous Feedback, Merit Matrix, Development Plans and Competency Assessment. | Setting | Where | Default | What it changes | |---|---|---|---| | Module cards | Module Configuration | **Performance Reviews** always on, **Goals Management** on, all others off | Shows or hides each feature area across the app | | **Default Rating Scale** | Performance Reviews settings | **5-Point Scale (Standard)** | The scale used by templates set to "Business Default" | | **Show Numeric Scores by Default** | Performance Reviews settings | On | Shows the number beside the rating label, for example "5 - Outstanding" | | **Require Manager Approval** | Performance Reviews settings | On | Submitted reviews wait in Pending Approval. When off, final submission approves the review | | **Allow Parallel Self-Assessment** | Performance Reviews settings | Off | Lets the employee start their self-assessment while the manager is still preparing the review | | **Require Final Acknowledgement of Performance Review** | Performance Reviews settings | Off | A two-sided review needs the employee's acknowledgement before it can be approved | | **Approval Workflow Type** | Goals Management settings | **Two-Tier (Employee → Manager)** | Who must approve a new goal before it becomes active | | **Minimum Goals Required** | Goals Management settings | 0 (no minimum) | A review cannot be submitted as complete until this many goals are linked to it. A template with its own goal-linking rule uses its own minimum | | **Enable Goal Weights** | Goals Management settings | Off | Adds a weight percentage to each goal | | **Require 100% Weight Total** | Goals Management settings | Off | Blocks review submission until goal weights total 100% | | **Anonymous Feedback** | 360-Degree Feedback settings | On | New 360 cycles hide who wrote each response | | **Require Manager Approval** | 360-Degree Feedback settings | On | New 360 cycles hold nominations for approval | | **Minimum / Maximum Peer Nominations** | 360-Degree Feedback settings | 4 / 6 | Apply to every 360 cycle. The feedback phase cannot start until each participant has the minimum, and nobody can receive more than the maximum | | **Allow managers to create 360° feedback cycles** | 360-Degree Feedback settings | Off | Lets managers, not only admins, create 360 cycles | | **Default Visibility Level** | Continuous Feedback settings | **Private** | The visibility preselected on new feedback, and given to feedback sent without choosing one | | **Enable Automation** | Review Management | Off | Lets automation rules create reviews, 360 cycles and follow-up plans | | **Autonomous AI Capabilities** | Review Management | All four off | Allows the AI to launch review cycles, reassign stuck reviews, send reminders and compile feedback summaries | | **Send performance review due & overdue reminders** | Notification Settings | Off unless set. Recently created organizations are set up with it On; older ones stay Off until an admin turns it on | Master switch for review reminder emails | | **First reminder** / **Overdue alerts** | Notification Settings | 7 days before due / 3 days past due | When the reminder emails go out | | **Performance Agent** | Module Configuration → General Settings | On | Makes the Performance Agent available in Ask AI | | **Enable AI Powered Features** | Module Configuration → General Settings | On for recently created organizations; older ones stay Off until an admin turns it on | Turns the in-app AI features on or off, including AI SMART goal analysis | ## 6. More help - [Performance Management FAQ](/help/articles/employee_performance_management_app_faq) — specific setup questions, limits and troubleshooting. - Ask AI — the assistant answers Performance Management questions from these articles. **Keywords:** performance management, performance review, review template, performance cycle, cycle element, self-assessment, manager review, pending approval, goals, goal approval, goal weights, milestones, 360 feedback, continuous feedback, competencies, team calibration, merit matrix, reward letters, review automation, review reminders, module configuration, can't see 360 feedback, linked key results, employee-performance-management, employee_performance_management, performance-management --- # Performance Management FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common questions about running performance reviews and cycles — for employees completing them, managers reviewing their team, and admins configuring the program. # Performance Management FAQ Answers to common setup and operating questions about Performance Management. For what the app is and how to set it up from scratch, see the [Performance Management Overview](/help/articles/employee_performance_management_app_overview). --- ## Setup ## Do I need to set up a template before anyone can be reviewed? Yes. A review cannot be created without a review template, and the form will not submit until you pick one. If no templates exist yet, create one first. The template decides what the review asks and who fills it out. ## Can the employee and the manager fill in different templates? No. A review uses one template. The template's **Who fills out this review?** setting decides who takes part: **Employee + Manager (both participate)**, **Self-Assessment Only (employee only)**, or **Manager Evaluation Only (no self-assessment)**. To give employees a different set of questions, build a separate template with the setting you need. ## Who can create a performance review for someone else? Super admins, business admins, HR admins and admins of the Performance Management app can create a review for **any** employee. An HR admin can open a review they created only if they are its assigned reviewer or a manager of that employee. Everyone else — including managers — can only create reviews for people they manage, directly or through their reports. Trying to create one for anybody else is refused. ## Is there a limit on how many reviews one employee can have? Only if you turn one on. In the Performance Reviews settings, **Enable Review Creation Limits** is **off** by default. When it is on, **Max Reviews per Employee** (default **2**, accepts **1 to 10**) applies within **Time Period (Months)** — 3, 6, 12, 18 or 24 months, with **12** as the default. **Allow Admin Override** lets admins and super admins go past the limit, and reviews an automation creates are never counted against it. --- ## Performance cycles ## How do I put reviews I've already sent into a performance cycle? Open the cycle and use **Add an element → From reviews already sent**. An element is one round of reviews inside a cycle, such as Q1 or the annual review. 1. The panel lists rounds of reviews that are not in any cycle yet. A round is two or more reviews with the same review type and the same review period. 2. Tick the rounds you want and click **Add selected as elements**. Each round becomes an element, and its dates, template and due date are read from the reviews themselves. 3. If one batch went out with slightly different dates, tick those rounds and click **Combine into one element**. Only rounds of the same review type can be combined. A round that runs past the cycle's dates is shown but cannot be picked. A review that shares its period with no other review is not a round. Add it from an element's **Add Existing Reviews** instead. ## Can an automation file its reviews into a cycle automatically? Yes. Open the cycle and use **Add an element → From an automation**, then click **Connect** next to a performance-review automation. The cycle's elements are built from that automation's schedule: - **Quarterly**, **Bi-annual** and **Company-wide annual** automations get one element per review period that falls inside the cycle. - **Hire anniversary** and **Tenure milestones** automations get one element that covers the whole cycle, because each employee's review falls on their own date. From then on, every review the automation creates is filed into the element whose dates cover it. Reviews it already created that are not in any cycle are filed at the same moment. An element already in the cycle with the same review type and matching dates is reused rather than duplicated. ## Why aren't my automation's new reviews landing in the cycle? A connected automation only files reviews into an element that is active, in a cycle that is still draft or active. Once a cycle is completed or archived, new reviews go to another connected cycle whose dates cover them. If there is none, they go to the cycle chosen on the automation itself while its dates cover them, or arrive unfiled. If the cycle page shows "automation rule without an element", connect that automation under **Add an element → From an automation** so each review lands in its element. ## Why can't I add an element to this cycle? Elements can only be added to a cycle that is draft or active. A completed or archived cycle shows "This cycle is completed, so elements can no longer be added to it." Adding elements is also limited to admins, HR admins and Performance Management app admins — managers can view cycles but not change them. --- ## Permissions and access ## Why can't I create a review for someone outside my team? Because you are a manager rather than an admin. Managers are limited to the people they manage — their direct and indirect reports. If you need to review someone outside that line, ask an admin to create the review, or to make you the assigned reviewer on it. ## Who can see a review once it has been created? Five groups can open it: - super admins and business admins - admins of the Performance Management app - the employee being reviewed - the assigned reviewer - any manager of that employee Nobody else can, and a review is never visible outside the organization it belongs to. ## Why can't I open someone else's review? Reviews are private to the people involved. You can open your own, plus anyone's if you are an admin, their assigned reviewer, or their manager. Anyone else sees "You do not have permission to access this performance review." --- ## Day-to-day ## How do I create a performance review for someone else? 1. Go to **Team → Team Reviews** and click **Create New Review**. The form is at `/apps/employee-performance-management/performance_reviews/new`. The Performance dashboard also has a **New Review** button for admins and managers. 2. Choose the **employee** and the **review template**. 3. Choose the **Assigned Reviewer**: **Employee's direct manager** (the default), **Me**, or **Custom reviewer**. A custom reviewer must be a manager or above. 4. Set the review period and the due date, and pick the **Review Type**: Annual, Bi-annual, Quarterly, Probationary or Ad-hoc. 5. Optionally add a title and a description. 6. Save it, or click **Save as Draft** to finish later. ## What happens right after I create a review? It starts as **Not Started** — set up but not yet underway. It moves to **In Progress** when the reviewer starts their part. The exception is a review whose template is **Self-Assessment Only**. That review starts **In Progress** straight away so the employee can begin. ## Do I have to give the review a title? No. Leave it blank and a title is generated from the review type, the review period and the employee's name. Anything you type is kept as-is. ## How do I fill in my own self-assessment? Open the review from your Performance dashboard and complete the self-assessment section. Your answers save as you go, so you can leave and come back before submitting. ## Why can't I edit my self-assessment any more? Because you have already submitted it. Your organization can allow changes after submission with **Allow Employee Edits After Submission**, which is **off** unless an admin turns it on. Even with it on, editing stops once the review has been approved or archived. ## Why doesn't my review have a self-assessment section? Because its template is **Manager Evaluation Only**, which has no employee part. You will see "This review does not include an employee self-assessment." Your manager completes it, and you can still read the result. --- ## When something looks wrong ## "The reviewer cannot be the employee being reviewed" — what do I do? You have picked the same person as both the employee and the reviewer. Choose a different reviewer: the employee's manager, yourself, or another manager-level colleague. Nobody can review themselves. ## "The selected employee has no direct manager" — what now? The person you are reviewing has no manager recorded, so the default reviewer has nobody to point at. Choose **Me** or **Custom reviewer** on this review, or add their manager to their profile and try again. ## Why was my due date rejected? The due date must fall after the end of the review period, and no more than a year after it. It also cannot be more than a year from today. The error names the review period end date so you can pick a date after it. --- ## More help - [Performance Management Overview](/help/articles/employee_performance_management_app_overview) - Ask AI — the assistant answers Performance Management questions from these articles. **Keywords:** faq, performance review, self-assessment, reviewer, review cycle, performance cycle, cycle element, review template, review automation, reviews already sent, direct reports, permissions, not showing, can't edit, employee-performance-management, employee_performance_management, performance-management --- # Personal Agent App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-14 How to enable, configure, and monitor Personal Agent — the AI assistant scoped to each user's own bookmarks, drafts, tasks, inbox, and cross-app personal data. # Personal Agent ## 1. What it is Personal Agent is an AI assistant that answers questions about a user's own data — their bookmarks, drafts, tasks, notification inbox, and private notes, plus their upcoming shifts, leave balance, recent paychecks, and expiring certifications when those apps are enabled. Every query is automatically filtered to the asking user, so the agent cannot see another user's personal data. Users interact with it through Ask AI; there is no separate chat interface. - **Enablement:** Requires a licence — the AI Productivity suite and All Employee Suites include it. An admin enables it per tenant and decides whether its write actions are allowed. - **What it is not:** Personal Agent does not manage other users' data, create workspace tasks, submit leave requests, or perform any domain-specific operation. Those belong to the owning app's own assistant (Shifts & Scheduling, Leave Management, etc.). Personal Agent can *read* data from those apps on the user's behalf — but only the user's own records, and only when the source app is also enabled. ## 2. Standing it up 1. Go to **Apps → Personal Agent → Settings** (or find **Personal Agent** in Admin → Apps → All Apps and choose **Configure**). 2. Check that **Enable Personal Agent** is on. It starts on as soon as the app is enabled, so the agent is already available to all users through Ask AI and read-only tools work immediately. 3. Decide whether to turn on **Allow write actions**. When on, the agent can bookmark records, remove bookmarks, edit bookmark notes, write private notes, mark notifications as read, acknowledge a must-read post or broadcast, and decide a request waiting on them, on users' behalf. This is off by default. Reads are never affected by this toggle. 4. Set the **Per-user daily write cap** (default 50 per user per day). The cap applies per user, not business-wide, and only counts writes — reads are unlimited. Set it to 0 for unlimited. 5. Confirm it works: open **Ask AI** from the top bar and type *"What's in my inbox?"* or *"Show me my bookmarks."* The agent should respond with data scoped to your account. Enabling the app turns the agent on — there is no separate go-live step. Only a business admin can switch **Enable Personal Agent** off, and doing so also turns the app off for the organization (see **Settings**). If you want to test the agent before rolling it out, use the **Load Sample Data** button on the Settings page. It runs in the background and creates a handful of drafts, notifications, and bookmarks on your own account, plus 90 days of sample agent activity for you and up to five sample people (when your organization has sample people) so **My Activity** and **Analytics** have something to show. Everything is tagged, so **Remove Sample Data** deletes it and leaves real data untouched. ## 3. How it fits together ### Read tools and write tools Personal Agent has two tiers of capability, controlled independently by the admin. **Read tools** are always available when the agent is enabled. They let the agent: - Search bookmarks by title and note text - List unfinished drafts - List tasks assigned to the user (filterable by status: open, overdue, completed, or all) - Summarize the notification inbox (unread count, action-required count, recent items) - List what is waiting on the user to acknowledge or confirm across apps — must-read posts, broadcasts, alerts, Sites pages, policies and SOPs — including asks that never sent a notification (for example in a category the user muted). This is the same list as the **Waiting on you** filter in Notifications - Search or list private notes (the personal scratchpad at /notes) No data is changed by any read tool. **Write tools** are off by default. When an admin turns on **Allow write actions**, the agent can: - Bookmark or un-bookmark a record - Update a bookmark's note - Write a new private note - Mark notifications as read (specific items, every visible item whose title mentions a topic, or all visible inbox items; snoozed items stay unread so they resurface as intended) - Acknowledge a must-read post or a broadcast from that list. Sites pages, policies, SOPs, alerts, job descriptions and posts confirmed in My Day are never confirmed in chat: the agent gives the user the link to confirm them where they live - Approve or decline a request waiting on them, as its own Approve / Decline buttons would Every write action except acknowledging and deciding runs without a confirmation prompt — each one changes only the user's own data, and the admin toggle and daily cap are the safety limits. Acknowledging a post or broadcast, and deciding a request, always show a confirmation card naming it first, because an acknowledgement is compliance evidence that cannot be taken back and a decision acts on someone else's request. Not every write can be undone: a removed bookmark that carried a note goes to Trash for 30-day recovery, one without a note is deleted outright, a bookmark note the agent replaces or clears keeps no copy (the agent shows the old text in its reply so you can ask it to put it back), and notifications the agent marks read can be marked unread again from the inbox. ### Cross-app lookups Personal Agent can also pull the user's own data from four other apps, when those apps are enabled for the tenant: | Source app | What the agent reads | Example question | |---|---|---| | **Shifts & Scheduling** | Upcoming assigned shifts | *"Am I working tomorrow?"* | | **Leave Management** | Leave balances by type | *"What's my PTO balance?"* | | **Payroll Connect**, else **Payroll Prep** | Recent paychecks from your payroll provider (gross and net); without them, Payroll Prep's gross pay per pay period — the answer names which | *"When was my last paycheck?"* | | **Skills & Credentials** | Certifications expiring soon | *"Which of my certs expire soon?"* | The example questions reach Personal Agent when asked from its page. From other pages, Ask AI usually sends single-app questions like these to that app's own assistant, which answers from the same records. These lookups are read-only and inherit the same privacy scope — every query is filtered to the asking user. If a lookup is unavailable — the source app isn't enabled or available to the user, its AI agent or that lookup is switched off in the app's settings, or (for shifts) Ask AI's schedule questions are off — the agent says which, so an admin knows what to turn on; if the app simply couldn't be reached, it says to try again. It never guesses or invents an answer. Asked from the **Personal Agent** page (or one of its **Try asking** prompts), *"What's on my plate this week?"* gets one answer combining the user's tasks, inbox items, and (when available) upcoming shifts. Asked anywhere else in Ask AI, plain task questions go to the Tasks app. For a cross-app answer from any page, ask for a personal snapshot — for example *"Build my personal snapshot: my shifts coming up and how much PTO I have left"* or *"Bring me up to speed on my unread notifications and unfinished drafts."* ### Privacy scope Every tool query is filtered to the asking user's ID and business. No tool accepts a target user parameter. If someone asks for "Bob's bookmarks", the agent explains it can only see the asking user's own data. Bookmarks can cover records from several apps: workspaces, workspace messages, comments, tasks, wiki pages, HR policies, SOPs, library items, site pages, recognition posts, job listings, recordings, and App Builder records. When the agent bookmarks a record on a user's behalf, it checks that the user can actually see that record before creating the bookmark. ### Worked example An employee opens Ask AI from the Personal Agent page and asks *"Are any of my tasks overdue?"* The agent queries tasks assigned to that user with a status of overdue. It returns a list with task titles and due dates. The employee then says *"Bookmark the first one with a note 'follow up Monday'."* If write actions are enabled and the daily cap has not been reached, the agent creates the bookmark with the note attached. If writes are off (the default), the agent tells the user write actions are off and that an administrator can turn them on with **Allow write actions** in Personal Agent → Settings. Later, the same employee asks *"What's my PTO balance?"* If Leave Management is enabled for the tenant, the agent reads the balance live from that app, scoped to the asking user. If it is not enabled, the agent says so and suggests the user contact an admin. ## 4. Running it ### Reviewing adoption (Analytics) 1. Go to **Apps → Personal Agent → Analytics** (business admin or Personal Agent app admin required). 2. Choose a time range: **7 days**, **30 days**, or **90 days**. 3. The dashboard shows: - **KPIs** — active users, total tool calls (read vs write), sessions, LLM token usage - **Daily tool calls** — trend chart over the selected range - **Routing quality** — how often Ask AI correctly routed questions to Personal Agent, with acceptance rate and average confidence - **Tool mix** — per-tool invocation count, success rate, average and p95 latency - **Write activity** — completed and failed write actions by tool - **Safety** — the current daily cap, how many users have hit it, and top tool-call failures - **User adoption** — per-user query distribution and the share of queries from the top 10% of users 4. Click **Export CSV** to download a per-tool-call export of the selected range (capped at 50,000 rows; the filename indicates when the export is truncated). Business admins get each call's user ID, user name and session ID. Personal Agent app admins get the same export with anonymous user keys instead (`user-1`, `user-2`, … numbered within that file) and no session IDs. ### Checking personal usage (My Activity) Any user can go to **Apps → Personal Agent → My Activity** to see their own tool-call history — total calls, success rate, the tools they have used (with read/write labels), and their 10 most recent calls. This view is scoped to the individual user. Admins see cross-user metrics under Analytics. Both My Activity and the Overview page are available on mobile at **/m/apps/personal-agent**. Settings and Analytics are admin-only and remain desktop-only. ### Managing settings changes Settings changes take effect immediately: - Turning off **Enable Personal Agent** stops the agent from answering personal-data questions across the tenant, and turns the app itself off for your organization (see **Settings** below). - Turning off **Allow write actions** blocks the agent's seven write actions while reads continue uninterrupted. - Changing the **Per-user daily write cap** applies from the next write action onward. Writes already performed today still count toward the new cap. The **Overview** tab (visible to all users) shows quick-start prompts that deep-link into Ask AI with the question prefilled. If write actions are off (the default), a notice appears below the prompts explaining that the agent can read but not change data until an administrator turns them on — and, for people who can manage Personal Agent, it links straight to Settings. Personal Agent only answers inside Ask AI, so a user whose account doesn't have Ask AI sees a note saying so instead of the prompts. ## 5. Settings All settings live on **Apps → Personal Agent → Settings** (visible to admins and Personal Agent app admins). | Setting | Default | What it changes | |---|---|---| | **Enable Personal Agent** | On once the app is enabled | When on, all users can query the agent through Ask AI. Turning it off stops the agent and also turns the app off for your whole organization (see below). | | **Allow write actions** | Off | When on, the agent can bookmark records, remove bookmarks, edit bookmark notes, write private notes, mark notifications as read, acknowledge must-read posts and broadcasts, and decide requests waiting on the user. Reads are unaffected. Acknowledging and deciding ask for confirmation first; the other writes run without a prompt. | | **Per-user daily write cap** | 50 per user per day | Maximum write actions one user's agent can perform in a calendar day. Reads do not count. Set to 0 for unlimited. The cap resets at midnight in each user's own time zone. | The app itself requires explicit enablement per tenant (it is not auto-enabled); once it is enabled, the agent is on by default. **Enable Personal Agent** is more than an agent switch: turning it off also turns the app off for your whole organization. Unless Personal Agent comes with your plan, employees then lose the **Overview** and **My Activity** pages, and admins lose **Settings** and **Analytics**. To bring it back, a business admin enables the app again in Admin → Apps → All Apps; the agent comes back on with it. (If Personal Agent comes with your plan, the Settings page stays available and switching **Enable Personal Agent** back on there does the same.) **Who can change settings:** Any user with admin or above role, or a user designated as a Personal Agent app admin — except **Enable Personal Agent**, which only a business admin can switch on or off. The **Overview** and **My Activity** tabs are visible to all users; **Settings** and **Analytics** are restricted to these roles. ## 6. More help - **Personal Agent FAQ** — specific setup, write-cap, and cross-app questions - Ask AI — the assistant answers questions about Personal Agent from these articles **Keywords:** personal agent, my bookmarks, my drafts, my tasks, my inbox, ask ai personal, personal assistant, write actions, daily write cap, personal agent analytics, my notes, my shifts, my leave balance, my pay, my certifications, personal-agent, personal_agent --- # Personal Agent FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Personal Agent — for the admin running it. # Personal Agent FAQ Answers to common setup and operating questions about Personal Agent. For what the app is and how to set it up from scratch, see the [Personal Agent Overview](/help/articles/personal_agent_app_overview). --- ## Setup ## Do I need to do anything before users can talk to the Personal Agent? Yes — two things. First, the app must be licensed and enabled for your tenant in Admin → Apps → All Apps — the AI Productivity suite and All Employee Suites include it. Second, the **Enable Personal Agent** toggle under **Apps → Personal Agent → Settings** must be on. Both must be true before the agent responds to personal-data questions through Ask AI. ## What's the difference between enabling the app and enabling the agent toggle? Enabling the app in Admin → Apps → All Apps turns the app on, and the agent with it — **Enable Personal Agent** starts switched on. The toggle is not a separate go-live step: turning it off stops the agent and also turns the app off for your whole organization, so unless Personal Agent comes with your plan, employees lose the **Overview** and **My Activity** pages too. Enabling the app again from Admin → Apps → All Apps brings the pages back and turns the agent back on with them. ## How do I test the agent before rolling it out? On the Settings page, use the **Load Sample Data** button. It runs in the background and creates a small set of drafts, notifications, and bookmarks on your own account, plus 90 days of sample agent activity for you and up to five sample people (when your organization has sample people) so **My Activity** and **Analytics** have something to show. Everything is tagged, so **Remove Sample Data** deletes it cleanly. Then open Ask AI and try a prompt like *"What's in my inbox?"* to confirm the agent responds. --- ## Permissions and access ## Who can change Personal Agent settings? Any user with an admin or above role, or a user designated as a Personal Agent app admin. Two things stay with business admins: only a business admin can switch **Enable Personal Agent** on or off, and only a business admin's **Export CSV** includes user IDs and names — a Personal Agent app admin's export replaces them with anonymous keys. The **Overview** and **My Activity** tabs are visible to all users; **Settings** and **Analytics** are restricted to those roles. ## Can the agent see other users' data? No. Every query is filtered to the asking user's ID. No tool accepts a target user parameter. If someone asks for another user's bookmarks, the agent explains it can only see the asking user's own data. --- ## Day-to-day ## What does "Allow write actions" control? When off (the default), the agent cannot bookmark or un-bookmark records, edit bookmark notes, write private notes, mark notifications read, acknowledge a must-read post or broadcast, or decide a request — it can still search and list them, and it tells the user an administrator can turn write actions on (and that they can mark notifications read in their Inbox, or confirm or decide an item on its own page, themselves). When on, the agent gains seven write tools: bookmark a record, remove a bookmark, update a bookmark's note, write a private note, mark notifications as read, acknowledge a must-read post or broadcast, and decide a request waiting on them. The first five run immediately without a confirmation prompt because each changes only the user's own data; acknowledging and deciding show a confirmation card naming the item first; the admin toggle and the **Per-user daily write cap** are the safety limits. Not every write can be undone: removing a bookmark that carries a note sends it to Trash for 30-day recovery, one without a note is deleted outright, a bookmark note the agent replaces or clears keeps no copy (the agent shows the old text in its reply so you can ask it to put it back), and notifications the agent marks read can be marked unread again from the inbox. This switch does not cover features Ask AI offers in every conversation — tracking a Journey, forgetting a remembered fact, or (for admins) starting an App Builder draft — which have their own settings. ## What types of records can users bookmark through the agent? The agent supports 13 record types: workspaces, workspace messages, workspace comments, tasks, wiki pages, HR policies, SOPs, library items, site pages, recognition posts, job listings, recordings, and app builder records. These are the same types available through the bookmark icon in the UI. Before creating a bookmark, the agent checks that the user can actually see the target record. ## How does the per-user daily write cap work? Every write that actually changes something counts against the user's daily limit — re-bookmarking a record that is already saved, or marking already-read notifications read, does not. The default is **50 writes per user per day**, configurable from 0 to 1,000 in Settings. Setting it to 0 means unlimited. The cap resets at midnight in each user's own time zone (the zone they chose on their profile, otherwise their location's, otherwise the organization's), not on a rolling 24 hours. When a user hits the limit, the agent tells them and stops accepting writes until the next day. Reads are never capped. ## What happens when someone asks the agent to mark their inbox as read? The agent marks all **visible** unread notifications as read. Snoozed items are deliberately excluded — they stay unread so they resurface at their scheduled time. Users can also ask the agent to mark specific notifications, or every visible notification whose title mentions a topic (*"mark my inspection notifications as read"*), rather than clearing everything. ## How do users check their own agent usage? Any user can go to **Apps → Personal Agent → My Activity** to see their tool-call history: total calls, success rate, which tools they have used (labelled read or write), and their 10 most recent calls. This view is also available on mobile. Admins see cross-user metrics under the **Analytics** tab. --- ## Cross-app lookups ## What personal data from other apps can the agent access? When the source apps are enabled for the tenant, the agent can pull the user's own data from **Shifts & Scheduling** (upcoming shifts), **Leave Management** (leave balances), **Payroll Connect** or **Payroll Prep** (recent pay), and **Skills & Credentials** (expiring certifications). These lookups are read-only and follow the same privacy scope — only the asking user's records. ## Which pay figures does the agent give — Payroll Connect or Payroll Prep? When **Payroll Connect** is available to the user and has paychecks synced for them from your payroll provider (ADP, Workday, Gusto and others), the agent answers from those paychecks — gross pay, net pay, taxes and deductions, the same list as the user's **My Paychecks** page. Otherwise it answers from **Payroll Prep**'s gross pay per completed pay period. It never mixes the two in one answer, and it always says which system the figures came from. If your organization has turned on **Hide Pay Amounts**, the agent shows no pay figures from either app. ## A user asked about their shifts, leave, pay or certifications, but the agent said it can't check — why? The agent says which of these applies: - **The source app isn't available to that user** — Shifts & Scheduling, Leave Management, Payroll Prep (and Payroll Connect, for pay) or Skills & Credentials is not enabled for your tenant, or that user isn't allowed to use it. An admin can enable the app in Admin → Apps → All Apps. - **The app's own AI agent is switched off** in that app's settings (**AI Agent Enabled**, or **Enable Payroll Agent** in Payroll Prep). The app itself is on; turn its agent back on there. - **That lookup is turned off inside the app** — **Team Calendar** in Shifts & Scheduling (upcoming shifts), **Balance Tracking** in Leave Management (leave balances), or **Certification Management** in Skills & Credentials (expiring certifications). - **Pay only:** your organization hides pay amounts (**Hide Pay Amounts** in Admin → General Settings → Payroll Settings). - **Upcoming shifts only:** **Enable Schedule Queries** is turned off in Ask AI's settings. - **The app couldn't be reached just now** — the agent says so and asks the user to try again in a moment; nothing needs to be switched on. --- ## When something looks wrong ## "I searched my bookmarks but some results are missing" Bookmark text search scans the most recent 2,000 bookmarks. If the user has more than 2,000 and the missing item is older, the agent adds a note suggesting a record-type filter to narrow the search. Filtering by type searches within that type's 2,000 window, which usually surfaces the result. Bookmarks whose record has since been deleted, or that the user can no longer open (for example after leaving a private workspace), are also left out of the agent's answers. The **Bookmarks** page still lists them — marked "This item was deleted or is in the trash" or "no longer available to you" — with a **Remove from bookmarks** link. ## "The agent said it couldn't find a record I asked it to bookmark" The agent checks that the user can see a record before bookmarking it. If the user does not have access — because of permissions, audience scoping, or the record being in a private workspace — the agent responds with "not found" without revealing whether the record exists. ## "Write actions are on but the agent says they're off" Both the **Enable Personal Agent** toggle and the **Allow write actions** toggle must be on, and the user must not have exceeded their daily write cap. If the agent toggle is off, writes are blocked even if the write-actions toggle is on. Check all three conditions in Settings. Inside an embedded Ask AI that has not been given permission to make these changes (for example a read-only one on a Hub page), the agent never makes them whatever these settings say — it tells the user to make the change in OneMango instead. ## "My employee says Personal Agent doesn't appear in Ask AI" Confirm the app is licensed and enabled for your tenant in Admin → Apps → All Apps (the AI Productivity suite and All Employee Suites include it), that it is published to that employee, that they have Ask AI, and that **Enable Personal Agent** is on in Settings. --- ## Employee-reported questions ## "How do I stop the AI from seeing my personal data?" There is no per-person opt-out today. Personal Agent reads only the asking person's own bookmarks, notes, drafts, tasks and inbox — never anyone else's — and only when that person asks it something, in Ask AI or an AI assistant they connected. An administrator decides whether Personal Agent is available for the organization and who it is published to. ## "I snoozed some notifications and then asked the agent to mark everything as read — did it clear them?" No. When the agent marks all notifications as read, it only touches items currently visible in the inbox. Snoozed items stay unread so they come back when their snooze period ends. --- ## Licensing and limits ## Are there limits I should know about? | Limit | Value | |---|---| | Bookmark note length | 500 characters | | Private note title length | 200 characters | | Bookmark text search window | 2,000 most recent bookmarks | | Per-user daily write cap | Default 50 (configurable 0–1,000) | | Analytics time ranges | 7, 30, or 90 days | | Analytics CSV export | 50,000 rows maximum; user IDs and names for business admins, anonymous keys for Personal Agent app admins | | Supported bookmarkable record types | 13 | | Included in | AI Productivity, All Employee Suites | --- ## More help - [Personal Agent Overview](/help/articles/personal_agent_app_overview) - Ask AI — the assistant answers Personal Agent questions from these articles. **Keywords:** faq, personal agent, bookmarks, drafts, inbox, write actions, daily cap, cross-app lookups, my bookmarks, my tasks, my inbox, ask ai personal, personal notes, not showing, permissions, personal-agent, personal_agent --- # Platform Admin Agent **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-19 AI assistant that helps administrators manage users, audit permissions, query org structure, and inspect system health through natural language in Ask AI. # Platform Admin Agent ## 1. What it is Platform Admin Agent is an AI assistant that lets administrators manage users, audit permissions, inspect org structure, and check system health through natural-language conversation in Ask AI. It works with live data — ask a question about your business, and it queries the actual records. - **Enablement:** Licensed app, disabled by default. Included in the Platform Enterprise edition. In other editions it is available only through a licence grant from your account team — it is not sold as a separate line item. An admin enables it from Admin → Apps → All Apps, then configures it from the app's Settings tab. - **What it is not:** Platform Admin Agent works with live data and takes actions. It is not a help or documentation assistant — for questions about how to use a feature or where to find a setting, ask @platform_help instead. ## 2. Standing it up 1. Go to **Apps → Manage Apps** and enable **Platform Admin Agent**. A license must already be granted for your business. 2. Open **Apps → Platform Admin Agent → Settings**. The agent is enabled for read-only queries by default. 3. Decide whether to turn on **Allow write tools** (off by default). With this on, admins can activate or deactivate users, change roles, give, change or remove app roles, resend invitations, send password-reset links, and stage records from pasted text for import through the agent. Each write action requires explicit confirmation before it runs. Writes also need **Enable Action Execution** on in **Apps → Ask AI → Settings**, where it is on by default. 4. Decide whether to turn on **Allow autonomous operations** (off by default). This lets autonomous playbooks run unattended — sentinel metric alerts, email, tasks, notifications, webhooks, and AI analysis; all but AI analysis also need **Enable Action Execution**. When this and write tools are both on, and **Enable Action Execution** is on in Ask AI settings, remediation scans you run from chat also queue a pending-approval action for each finding someone could act on, and notify only the admins who could make that change. 5. Open **Ask AI** from the top bar and try a prompt such as *"How many active users do we have?"* The Overview tab of the app shows nine suggested prompts you can click to open Ask AI with the question prefilled. Only Admin and Super Admin users can see or use this agent. Non-admins cannot invoke it, and the app tile is hidden from them in the Apps page and sidebar. ## 3. How it fits together **Read tools, write tools, and autonomous tools** are the three layers of capability, each controlled by its own setting. **Read tools** are available whenever the agent is enabled — in Ask AI, only while **Enable Action Execution** is on, because turning it off stops every agent tool, reads included. They let you: - Search and inspect user accounts (by name, email, role, status, department, or location). - List departments and locations with user counts. - Get a role summary — how many users hold each role. - Check a specific user's permissions. - List all Admin and Super Admin accounts. - List pending invitations that have not been accepted. - Search the platform audit log by user, action, or date range. - Get a system overview: active users, inactive users, enabled apps, and business info. - Audit org data quality — find active users missing a department, manager, job title, or location. - Compare access between two users — see which permissions they share and which differ. - Check app access health — inspect enablement, licensing, pinning, and configuration drift across all apps. - Check integration health — inspect external integrations, their health state, and last sync time without exposing credentials. - Check agent harness health — see Descriptor v2 coverage, effective tool counts, and contract integrity. Read tools never change anything. **Write tools** require both the **Allow write tools** toggle and Ask AI's **Enable Action Execution** to be on. There are eight: - **Activate or deactivate a user** — sets the user's membership status in this business. - **Change a user's role** — switches a user between member, manager, admin, and super admin; only a super admin can grant admin or super admin. - **Resend an invitation** — emails the invitation to an existing user who has not yet signed in to this business: with a one-time link to set their own password if they have never signed in, or with just their sign-in link if they have signed in before (to another business, for example), leaving their password unchanged. The agent refuses while **Welcome Emails** are turned off in Admin → General Settings → Notifications (User Accounts & Sign-in). - **Send a password-reset email** — emails the user a self-serve password-reset link. **Password Reset Emails** are always on — people need them to get back into their account — so they cannot be turned off. - **Stage an import** — stages records from text you paste for a Smart Import target. Nothing is written until you commit the import on its review page. - **Give, change or remove an app role** — makes someone App admin, Contributor or Collaborator of one app (company-wide, or for specific places and departments), changes what that role covers, or removes it. These three are separate tools, each confirmed on its own, and each change is recorded in the admin audit log as made through the agent. Every Ask AI write action waits for explicit confirmation; the four account changes also show a before-and-after diff preview. Deactivating someone also signs them out everywhere and unassigns their upcoming shifts, as it does from Admin → Users. Connected MCP clients use their authenticated scopes and the signed-in user's permissions to execute directly; each call is recorded in the connector activity log, and the MCP host may show its own confirmation prompt. **Autonomous tools** require the **Allow autonomous operations** toggle, and all but AI analysis also need Ask AI's **Enable Action Execution**. They run without a human in the loop — invoked by automation playbooks on a schedule, not by chat. Capabilities include sentinel metric alerts (fire when a watched metric crosses a threshold), webhooks, email, task creation, in-app notifications, and AI analysis. **Remediation scans** sit between read and write. You run them from Ask AI — nothing runs them on a schedule. Two scans exist: one surfaces stale invitations (not accepted within a configurable number of days), the other surfaces privileged accounts that may need an access review (admins who have not signed in within a configurable window). When autonomous operations are off or paused, or write tools are off, the scans return findings as evidence only. With **Enable Action Execution** off in Ask AI settings, they do not run at all. Otherwise, each finding that someone could act on also queues a pending-approval action and notifies only the admins who could carry out its recommended step — Super Admins alone for a change to a Super Admin account, and never the person the finding is about. A finding with no recommended step, a step nobody could run (such as an invitation to someone with no email address), or nobody else eligible to approve it comes back for manual review instead of being queued. **Worked example — stale invitation cleanup:** An admin asks *"Scan for failed invitations."* The agent finds 3 invitations older than 7 days that were never accepted. With autonomous operations off, it lists the 3 users and recommends re-sending or deactivating each one — no action is taken. With autonomous operations, write tools and **Enable Action Execution** all on, it also creates 3 pending-approval actions visible in **Admin → AI Operations → Approvals** and notifies the admins who could resend those invitations. One of them reviews each action, approves or rejects it, and the approved action executes as that admin, through the same write-tool path with the same safety guards. **Super Admin protection.** Unless the acting admin is themselves a Super Admin, the agent refuses to deactivate, change the role of, send an invitation to, or reset the password of any Super Admin account. The agent also refuses any action that would leave the business with no active Super Admin, or with no active administrator at all. These guards apply equally in chat, through MCP, and through the autonomous action runner. They also decide who can approve or reject a queued remediation action: an approved action runs as the admin who approved it, so AI Operations, the approvals email and AI Home offer Approve and Reject only to someone who could make that change themselves — and never to the person the finding is about. **Ask AI is the interface.** This is an agent-only app — it has no data-entry forms or grids of its own. Every conversation runs through Ask AI. The app surface has five tabs: Overview (suggested prompts), My Activity (your personal usage), Analytics (business-wide usage), Autonomous Operations (playbook execution ledger), and Settings. The @platform_admin mention is hidden from the autocomplete for non-admin users, so they do not encounter a control that would reject them. ## 4. Running it ### Asking a question Open Ask AI and type a natural-language question. The agent recognises admin-intent queries and routes them automatically. You can also click any of the nine suggested prompts on the Overview tab to open Ask AI with the question prefilled. Example prompts: - *"How many active users do we have?"* - *"Show me all admins in this business"* - *"List pending invitations"* - *"Show me users by department"* - *"Audit users missing department, manager, job title, or location"* - *"Compare permissions of user A and user B"* - *"Check app licensing and configuration health"* - *"Show unhealthy or stale integrations"* - *"Show recent permission changes"* ### Making a change (write tools) Ask the agent to perform a write action — for example, *"Deactivate jane@example.com."* The agent looks up the user, shows a diff preview of what will change, and asks you to confirm. Confirm to execute, or decline to cancel. You can identify users by email address or by user ID in any write request. The agent resolves emails case-insensitively. ### Reviewing autonomous operations Go to **Apps → Platform Admin Agent → Autonomous Operations**. This page shows the safety state (Running, Paused, or Disabled), a 7-day action breakdown by status, and the recent action ledger. Pending approvals link to the approval queue in Admin → AI Operations → Approvals, where an admin who could make the change can approve or reject them. ### Pausing autonomous operations On the Autonomous Operations page, click **Pause autonomous operations** to immediately stop all autonomous playbooks for this business. Click **Resume autonomous operations** to restart them. The pause is an emergency stop — no autonomous action runs while it is active. Remediation already waiting for approval can't be approved until you resume, but it can still be rejected. Pausing doesn't keep it waiting indefinitely: a review still waiting for approval is cancelled automatically 14 days after it was queued, paused or not. ### Reviewing your personal usage Go to **Apps → Platform Admin Agent → My Activity**. This page shows your tool calls, success rate, which tools you use most (classified as read or write), and your recent call history. The time range can be set to 7, 30, or 90 days (default 30). ### Reviewing business-wide analytics Go to **Apps → Platform Admin Agent → Analytics**. This shows all admins' activity aggregated: how many admins used the agent, total tool calls, read vs. write breakdown, tool mix with success rates and latency, routing quality, safety status, and approximate token cost. The same 7/30/90-day range selector applies. The Settings page also links to the platform-wide **Agent Health** page under Admin, which covers all AI agents in the business, not just this one. ## 5. Settings All settings are at **Apps → Platform Admin Agent → Settings**. | Setting | Default | What it changes | |---|---|---| | **Enable Platform Admin Agent** | On | Master switch. When off, the entire app disappears from the Apps page, sidebar, and navigation shortcut. History and analytics pages remain accessible so admins can review past activity. | | **Allow write tools** | Off | Unlocks eight actions: activate/deactivate user, change role, give, change or remove an app role, resend invitation, send password-reset email, and stage an import. Ask AI's **Enable Action Execution** must be on too. Each one still requires explicit confirmation before it executes. Approved remediation actions run through these same tools, so with this off the scans queue nothing and an action already queued can only be rejected, until it is cancelled automatically 14 days after it was queued. | | **Allow autonomous operations** | Off | Lets autonomous playbooks run unattended: sentinel alerts, webhooks, email, tasks, notifications, and AI analysis; all but AI analysis also need Ask AI's **Enable Action Execution**. Autonomous operations include AI analysis, which makes billable LLM calls without anyone watching. With write tools and Ask AI's **Enable Action Execution** also on, makes the remediation scans you run from chat queue an approval for each finding someone could act on. | Write tools and autonomous operations are independent. You can enable write tools without enabling autonomous operations, or vice versa — remediation approvals are the one place they meet, and they need both, plus **Enable Action Execution** in Ask AI settings. Both require the agent itself to be enabled. Turning the agent off disables the whole app, including its sidebar entry and navigation shortcut. To re-enable it, go to **Apps → Manage Apps**. ## 6. More help - **Platform Admin Agent FAQ** — specific setup and operating questions, limits, and troubleshooting - **Ask AI for Admins** — how Ask AI routes questions, including how it reaches this agent - **AI Operations** — the platform-wide pause controls, approval queues, and agent health dashboard - Ask AI — the assistant answers questions about Platform Admin Agent from these articles. **Keywords:** platform admin agent, admin agent, user management, audit permissions, org structure, system health, activate deactivate user, change user role, password reset, autonomous operations, remediation, sentinel alert, platform-admin-agent, platform_admin_agent --- # Platform Admin Agent FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-19 Answers to common setup and operating questions about the Platform Admin Agent — for the admin running it. # Platform Admin Agent FAQ Answers to common setup and operating questions about the Platform Admin Agent. For what the agent is and how to set it up from scratch, see the [Platform Admin Agent Overview](/help/articles/platform_admin_agent_app_overview). --- ## Setup ## What do I need to set up before the agent works? Four things must be in place. First, a Platform Admin Agent licence must be granted to your organisation — without it you cannot enable the app. Second, the app must be enabled in Admin → All Apps. Third, the **Enable Platform Admin Agent** toggle must be on in the app's Settings page. Fourth, **Enable Action Execution** must be on in **Apps → Ask AI → Settings**: with it off, Ask AI answers without running any of the agent's tools, so it can neither look anything up nor make changes. The licence and the app are off until someone grants and enables them, so a new licence does nothing until an admin deliberately turns the app on. The **Enable Platform Admin Agent** toggle defaults to on once the app is enabled, and **Enable Action Execution** is on unless someone has turned it off. ## Who can use the Platform Admin Agent? Only users with an **Admin** or **Super Admin** role in your organisation. The agent is hidden from the sidebar and Apps grid for everyone else, and any non-admin who reaches it through a direct link is redirected to the dashboard. Inside Ask AI, the Platform Admin Agent mention does not appear in the autocomplete for non-admins. ## What are write tools and should I turn them on? Write tools let the agent activate or deactivate users, change roles, give, change or remove app roles, resend invitations, send password-reset links, and stage records from pasted text for import. They are **off by default** — enabling the agent gives it read access to your user directory, org structure, audit log, and system health, plus the remediation scans described below. Turn them on only when you want conversational admin actions. They also need **Enable Action Execution**, which is on by default in Ask AI settings. Every write requires confirmation before anything changes, and the four account changes also show a diff preview. --- ## Permissions and access ## Can the agent modify Super Admin accounts? Not unless you are a Super Admin yourself. Through the agent, only a Super Admin can deactivate, change the role of, send an invitation to, or trigger a password reset for another Super Admin. If an Admin asks the agent to do any of those things to a Super Admin account, the agent refuses and tells you to ask a Super Admin. In Admin → Users, deactivating a Super Admin and changing their role follow the same rule; an Admin can still send a Super Admin an invitation or a password-reset email there, and that email goes only to the Super Admin's own address. ## Can I change my own role or deactivate my own account through the agent? No. The agent refuses both operations and explains why. Changing your own role could lock you out of administration, and deactivating your own account would end your session with no way to reverse it. ## Why does the agent refuse to demote or deactivate someone even though I'm a Super Admin? The agent prevents any change that would leave your organisation with no active Super Admin, or with no active administrator at all. If the person you are trying to demote or deactivate is the last one holding that role, promote another user first, then retry. --- ## Day-to-day ## What write operations does the agent support? Eight, and each requires confirmation before it executes: 1. **Activate or deactivate** a user account. 2. **Change a user's role** to Member, Manager, Admin, or Super Admin. Only a Super Admin can grant Admin or Super Admin. 3. **Resend an invitation** email to an existing user who has not yet signed in to this business. Someone who has never signed in gets a one-time link to set their own password; someone who has signed in before gets just their sign-in link, and their password is unchanged. Refused while **Welcome Emails** are turned off. 4. **Trigger a password reset** — the user receives a self-serve reset link by email. **Password Reset Emails** are always on, so this is never refused for that reason. The Welcome Emails switch is in Admin → General Settings → Notifications (User Accounts & Sign-in). 5. **Stage an import** — records from text you paste are staged for a Smart Import target; nothing is written until you commit the import on its review page. 6. **Give an app role** — make someone App admin, Contributor or Collaborator of one app, company-wide or for specific places and departments. 7. **Change an app role** — change the role or what it covers. 8. **Remove an app role**. The app-role changes are recorded in the admin audit log as made through the agent, and listed on My Activity. For the four account changes, identify the target user by email or user ID. The agent shows exactly what will change before you approve. ## How do remediation scans work? The agent can scan for two kinds of risk: **stale invitations** (users invited more than 7 days ago who never accepted) and **stale privileged accounts** (admins who have not signed in for more than 90 days). Both thresholds are configurable per scan. Each scan returns a list of findings with evidence and recommended next actions. If autonomous operations **and** write tools are both on for your organisation, and **Enable Action Execution** is on in Ask AI settings, each finding that someone could act on also queues a pending-approval action and notifies the admins who could approve it. With autonomous operations or write tools off, you get the same findings as evidence only — nothing is queued and no notifications are sent. With **Enable Action Execution** off, the scans do not run at all. ## Who is asked to approve a remediation finding? Only people who could make the recommended change themselves. Approving a finding runs its change as the person who approved it, so a finding about a Super Admin account goes to Super Admins only, and other findings go to every active Admin and Super Admin. The person a finding is about can never approve or reject it, and neither can a service account or a deactivated account. Who may decide is worked out from each account's current role, so a finding about someone who has become a Super Admin since the scan ran is a Super Admin's decision. The same rule applies wherever the decision is made — AI Operations, the daily approvals email, and AI Home — so you will not see an Approve button for a change you are not allowed to make; you see the reason instead. When approving could not make the change right now — the agent or its write tools are turned off, autonomous operations are turned off or paused, **Enable Action Execution** is off in Ask AI settings, the agent's licence has lapsed, the account is no longer part of your organisation, the finding no longer applies (for example, the admin has signed in since the scan, the account was reactivated, or the invitation was accepted), or the account's state blocks the change (it has no email address, **Welcome Emails** are turned off, or the change would leave no active Super Admin or administrator) — the people who may decide the finding can still reject it to close it. When the reason is something an admin can fix, such as adding the missing email address, turning Welcome Emails back on or promoting another user to Super Admin, fix it and then approve the finding; otherwise, reject it to close it. AI Operations and AI Home show the reason in place of Approve, and the daily approvals email lists the finding as **Reject only**, with a link that opens the Reject form. A finding nobody approves or rejects is cancelled automatically 14 days after it was queued, even while approving is on hold. A finding is returned for manual review instead of being queued when there is no recommended step to run (an active Super Admin who has not signed in recently is always a manual review), when nobody could run the step (for example, resending an invitation to someone with no email address), or when no one other than the person under review is allowed to approve it. The agent tells you which. ## What are autonomous operations? Autonomous operations let automation playbooks use the agent's unattended tools without a conversation — sentinel metric alerts, webhooks, email, tasks, notifications, and AI analysis; all but AI analysis also need **Enable Action Execution** on in Ask AI settings. The remediation scans are not among them: you run those from Ask AI, and with autonomous operations and write tools both on they also queue the findings someone could act on for approval. The feature has its own toggle in Settings (**Allow autonomous operations**, off by default) and a separate pause/unpause control on the Autonomous Operations page. Pausing stops autonomous actions immediately; unpausing resumes them. Remediation already waiting for approval can't be approved until you resume, and it can still be rejected. Pausing doesn't keep it waiting indefinitely: a review still waiting for approval is cancelled automatically 14 days after it was queued, including while autonomous operations are paused or turned off. ## What happens when I ask the agent a how-to question? The agent works with live data only. If you ask how to use a feature or where to find a setting, it tells you to ask the Platform Help assistant instead. It does not answer documentation questions. --- ## When something looks wrong ## "The agent says write tools are disabled — how do I turn them on?" Go to the Platform Admin Agent app → Settings and check the **Allow write tools** toggle. It is off by default. Only users with an Admin or Super Admin role can change this setting. Once enabled, every write still requires per-action confirmation. If the agent instead says action execution is turned off or disabled, or answers without looking anything up, turn on **Enable Action Execution** in **Apps → Ask AI → Settings**. ## "I get 'access denied' when I try to use the admin agent" Your current role does not have access. The Platform Admin Agent is restricted to Admin and Super Admin roles. Ask an existing admin to check your role under Admin → Users. If your role shows Member or Manager, the admin must promote you before you can use the agent. ## "The agent says it can't find a user I know exists" The agent searches within your organisation only. If the user belongs to a different organisation (business), they will not appear. Also check that you are using the correct email address — the agent matches on email case-insensitively, but a typo will return no results. --- ## Licensing and limits ## Does the Platform Admin Agent require a licence? Yes. The app requires a licence before it can be enabled. It is included in the Platform Enterprise edition. In other editions it is available only through a licence grant from your account team — it is not sold as a separate line item. ## What are the search and query limits? | What | Default | Maximum | |---|---|---| | Users per search | 20 | 50 | | Audit log entries per query | 25 | 100 | | Admin users listed | 20 | 50 | | Pending invitations listed | 20 | 50 | | Remediation bundle findings | 20 | 50 | ## What are the default thresholds for remediation scans? The stale-invitation scan surfaces invitations older than **7 days** by default. The privileged-access scan flags admins who have not signed in for **90 days**. Both thresholds can be overridden per scan by asking the agent to use a different number of days. --- ## More help - [Platform Admin Agent Overview](/help/articles/platform_admin_agent_app_overview) - Ask AI — the assistant answers Platform Admin Agent questions from these articles. **Keywords:** faq, platform admin agent, admin agent, user management, role change, deactivate user, remediation, privileged access review, stale invitations, autonomous operations, audit log, write tools, permissions audit, org data quality, platform-admin-agent, platform_admin_agent --- # Policy Hub App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run Policy Hub: versioned HR policies, handbooks, signatures and acknowledgment tracking, and the Compliance Report. # Policy Hub ## 1. What it is Policy Hub holds your HR policies and employee handbooks, versions every change, and tracks who has acknowledged what. When you publish a policy, everyone in its audience is asked to acknowledge it by a deadline. The Compliance Report then shows who is done, who is pending and who is overdue. - **Enablement:** Policy Hub requires a license. An admin enables it from Admin → Apps → All Apps. - **What it is not:** Policy Hub is not Compliance Hub. Compliance Hub handles SOX and SOC 2 vendor controls. Policy Hub handles internal HR policies and handbooks. ## 2. Standing it up 1. Go to **Policy Hub → Settings → Configuration** and review the defaults. The most important is **Default Acknowledgment Deadline (days)**, which is 14 unless you change it. 2. Create your first policy from **Policies → All Policies → New Policy**. You can start from a template, use **Import from Word**, or describe what you need and let AI draft it. Every new policy starts as a draft. 3. Set who it applies to. **All Employees** is on by default. Turn it off to pick departments or locations. Under **Jurisdiction & Applicability**, picking **Applicable States** narrows the audience further. 4. Decide how people confirm it. **Require Employee Acknowledgment** is on by default. Turn on **Require a Signature** if you want a signed record rather than a click. 5. Publish. Publishing creates a version and asks everyone in the audience to acknowledge it. 6. Confirm it worked. Open **Acknowledgments → Compliance Report**: the policy appears in **Policy Compliance Details** with its assigned and pending counts. **What silently does nothing until a second thing is configured:** - **State-scoped policies** reach only employees whose location has a state set. If no active location has a state, a state-scoped policy is assigned to nobody. The policy form warns you when coverage is short. - **Translations** need your organization's languages set up first, in **General Settings > Languages**. Until then the **Enable Multi-Language Support** switch cannot be turned on. - **Publication approval** applies only when an enabled approval workflow with at least one approval level exists for Policy Hub. Without one, anyone with HR access publishes directly. - **Comprehension checks** apply only when the policy has at least one active question. With none, there is no quiz before acknowledging. - **The Compliance Report** counts only published policies that require acknowledgment. A draft, or a policy with acknowledgment switched off, will not appear there. ## 3. How it fits together ### Who sees what - **HR access** means workspace admins, Policy Hub app admins and HR admins. They see the Policies menu, **All Acknowledgments**, **Compliance Report**, **Bulk Campaigns** and **Evidence Pack**. - **Settings** (Configuration and Activity Log) are for admins and Policy Hub app admins only. - **A people manager** (anyone with direct reports) gets **Acknowledgments → My Team**. It lists acknowledgments for their own reports, or for everyone below them in the organization. - **Everyone** sees the Dashboard, Policies, Handbooks, **My Pending** and **My History**. ### Policies, versions and statuses A policy is **Draft**, **Published**, **Archived** or **Retired**. Archived and retired policies can both be returned to draft. A published policy cannot be deleted; archive it first, which keeps its acknowledgment history. When you save a content change you choose its **Type of change**: **Minor**, **Major** or **Legal**. With **Re-acknowledge on Updates** on, a Major or Legal change asks everyone who acknowledged to acknowledge again. A Minor change keeps every acknowledgment and notifies no one. The same choice is on a policy you **Unpublish** to edit as a draft: it is what the next **Publish** counts as when the content differs from what was last published. Publishing again with unchanged content asks no one to sign again. Example: you publish "Remote Work Policy" as version 1. You rewrite the equipment section and save it as **Major**, creating version 2. Everyone who signed version 1 now shows as pending again, with a new deadline. ### Acknowledgment vs signature These are easy to confuse. An **acknowledgment** is a click confirming the employee has read the policy. A **signature** (**Require a Signature** on the policy) means the employee reviews the policy document and signs it in the app. The signed PDF is kept as evidence. No E-Signature app or provider is needed. Employees without an email address on file can still sign. They confirm it is them with a step-up: a text-message code to the mobile number on their profile, or else their password or PIN. A password is offered only to someone who has signed in before. Someone with none of these is told on the signing page to ask HR to add a mobile number. Each acknowledgment records the version, the time, how it was given, the device type and the IP address. ### Obligations: what the Compliance Report counts The report counts **obligations**: one targeted person × one policy. **Assigned** is the policy's current audience. **Acknowledged** is the people in that audience who have signed off on the current version. **Pending** is assigned minus acknowledged, so someone with no request yet still counts. **Overdue** is pending past its deadline. Example: "Code of Conduct" targets all 200 employees and "Forklift Safety" targets the 40 in the Warehouse department. That is 240 obligations. If 180 are acknowledged, **Compliance** reads 75%. Two numbers look alike and are not: - The report's **Pending** tile counts employee-policy pairs, including people with no request yet. - The Dashboard's **Outstanding Acknowledgments** tile counts acknowledgment requests that have been sent and not completed. Someone who has left a policy's audience no longer counts in the report, even if an old request still exists. ### Handbooks and templates A **handbook** assembles published policies into one document. The builder has four section types: a policy, custom content, a chapter header and a divider. When you publish a handbook that requires acknowledgment, its audience is asked to acknowledge each published policy in it. **Templates** are starting points. System templates come with the platform; you can also save your own. Using a template creates a new draft policy. ### Legal review cadence A policy can carry a **Review cadence**: Monthly, Quarterly, Semiannual, Annual, or **As needed (no schedule)**. A cadence sets the next review date. **Mark Reviewed** on the policy records the review and moves that date on by one interval. A policy with no cadence is never flagged. ## 4. Running it ### Checking compliance Go to **Acknowledgments → Compliance Report**. Four tiles show **Policies Tracked**, **Compliance**, **Pending** and **Overdue**. - **Compliance over the last 12 months** is a trend line built from a nightly snapshot, one point per night. Today's point is live. A new workspace starts with one point and fills in nightly. - **Break down by** splits the same numbers by an audience dimension. Location is the default; Department and Manager are among the others. Each person lands in exactly one row, so the rows add up to the total. - **Policy** narrows the breakdown and the trend to one policy. - **Export CSV** downloads the whole policy table. **Export breakdown** downloads the breakdown you are looking at. ### Chasing overdue acknowledgments 1. On the Compliance Report, select **View overdue acknowledgments**. 2. This opens **All Acknowledgments** filtered to **Overdue**. The chips are **All**, **Pending**, **Overdue** and **Acknowledged**. 3. **Pending** and **Overdue** count exactly what the report counts, so the list matches the tile. 4. Use the bell icon on a row to remind one person. With the list filtered to one policy, **Remind all** reminds everyone still pending on it. **Send All Reminders** on the Compliance Report reminds every pending employee across all published policies. Automatic reminders also go out on the schedule in Settings. ### Exporting evidence for an audit Go to **Acknowledgments → Evidence Pack** and choose **By employee** or **By policy**. - **By policy → Roster** lists every targeted employee with their record or outstanding status. **Export CSV** downloads the full roster, however large. - **Signature ledger** lists every signature on record. - IP address and user agent are hidden by default and left out of the standard export. Revealing them, or choosing **Export with IP address and user agent**, requires a step-up sign-in and is logged. ### Running a bulk campaign Go to **Acknowledgments → Bulk Campaigns** to bundle several policies into one acknowledgment request. This suits annual re-acknowledgment drives. A campaign tracks progress across its policies and can send reminders. ### Reviewing legal updates and coverage **Policies → Legal Updates** lists employment-law changes for your jurisdictions, rated Critical, Important or Informational. On each one you can **Mark as Reviewed**, **Dismiss Update** or **Apply Custom Override**. **Policies → Compliance Check** scans your policies against the requirements of the jurisdictions you operate in and shows gaps. ### Importing policies Use **Import from Word** on the policies list for a single Word document. Use **Policies → Bulk Import** for several PDF and Word files at once. Every imported document becomes a draft. ## 5. Settings All settings are at **Policy Hub → Settings → Configuration**. | Setting | Where | Default | What it changes | |---|---|---|---| | **Enable Policy Hub AI Agent** | AI Features | On | Lets employees ask Ask AI about policies. Also runs the nightly scan that flags stale and review-overdue policies. | | **Generate AI Summaries of Policies** | AI Features | On | Writes a plain-language summary of each policy when it is saved. | | **Allow AI to Generate Comprehension Questions** | AI Features | On | Lets authors draft quiz questions from a policy's text. | | **Auto-Publish Scheduled Policies** | Automation | On | Publishes a policy at its scheduled time and sends acknowledgment requests. Off means someone publishes it by hand. | | **Send Policy Review Due Notices** | Automation | On | Notifies policy owners daily when a review is near or past due. | | **Default Acknowledgment Deadline (days)** | Acknowledgment Settings | 14 | Days to acknowledge when a policy sets no deadline of its own. | | **Require Re-acknowledgment When Policies Update** | Acknowledgment Settings | On | The starting value of **Re-acknowledge on Updates** for new policies. Existing policies keep their own setting. | | **Notify Employees on Policy Updates** | Acknowledgment Settings | On | Tells employees when a policy they acknowledged changes. | | **Notify Employees About Acknowledgments They Owe** | Acknowledgment Settings | On | Sends the first request on publish and the automatic reminders after it. | | **Reminder Frequency (days)** | Acknowledgment Settings | 4 | Days between reminders. Each person gets up to four reminders, then a final overdue notice. Workspaces set up before this default changed keep 3. | | **Escalate Overdue Acknowledgments to Managers** | Acknowledgment Settings | On | Tells the employee's manager, in one morning notice, when acknowledgments are overdue. Someone with no manager is reported to HR and Policy Hub's admins instead (up to ten people, HR first). Disabled here when **Admin › Notifications › Overdue Escalation Ladder** overrides it. | | **Send Email Notifications** | Acknowledgment Settings | On | Turns off the email copy of Policy Hub notifications only. In-app notifications still arrive. | | **Low Compliance Alert Threshold (%)** | Acknowledgment Settings | 50 | Policies below this rate alert admins and appear in the weekly compliance summary, once someone has missed a deadline. | | **Enable Multi-Language Support** | Multi-Language Support | Off | Allows AI translation of policies. Needs your organization's languages set up first. | | **Enable Public Handbook & Policy URLs** | Public Handbook Settings | On | Lets shared handbook and policy links open. Turning it off breaks every link already shared. | | **Require Sign-In for Public Handbook & Policy Links** | Public Handbook Settings | On | Only signed-in members of your organization can open a shared link. Off lets anyone with the link open it. | ## 6. More help - **Policy Hub FAQ** — specific setup and operating questions, limits and troubleshooting - Ask AI — the assistant answers questions about Policy Hub from these articles. **Keywords:** policy hub, hr policy, employee handbook, policy acknowledgment, compliance report, overdue acknowledgments, policy roster export, re-acknowledgment, require a signature, employee without email, legal update, policy template, bulk acknowledgment, evidence pack, comprehension check, policy-hub, policy_hub --- # Policy Hub FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Policy Hub — for the admin running it. # Policy Hub FAQ Answers to common setup and operating questions about Policy Hub. For what the app is and how to set it up from scratch, see the [Policy Hub Overview](/help/articles/policy_hub_app_overview). --- ## Setup ## Do I need to configure anything before employees can use Policy Hub? Yes. An administrator must enable Policy Hub from Admin → Apps → All Apps and grant it a licence. Until then the app is invisible to everyone. Once enabled, the default settings work out of the box — acknowledgments are on, the deadline is 14 days, and reminders go out every 4 days — but you should review the Settings tab before publishing your first policy. If you plan to use multi-language translation, you also need to turn on **Enable Multi-Language Support** in Policy Hub settings. Translation is off by default and requires your business to have languages configured in General Settings first. ## Who can create and manage policies? Three roles have HR-level access: **Admin or above**, anyone designated as a **Policy Hub App Admin**, and anyone with the **HR Admin** role. These users can create, edit, publish, archive, and retire policies, manage templates, run acknowledgment campaigns, view compliance reports, and access the Evidence Pack. All other employees can browse published policies and handbooks, view their pending acknowledgments, and acknowledge policies assigned to them. --- ## Permissions and access ## Why can't a specific group of employees see a policy? A policy's audience is the intersection of two settings. First, the **audience targeting** — either all employees or specific departments and locations. Second, the **jurisdiction scoping** — if you select applicable states, only employees assigned to locations in those states are included. If an employee is not in both the audience and the jurisdiction, they will not see the policy and will not be asked to acknowledge it. Check the policy's edit page to see which departments, locations, and states are selected. If you are using state scoping, also check that your employees' locations have a state set — anyone at a location with no state falls outside every state-scoped policy. --- ## Day-to-day — Policies ## How does version control work when I publish a policy? Every time you publish a policy, the platform creates a numbered version snapshot that records the full content, the author, the date, and the change reason. You can compare any two versions side-by-side with highlighted additions and deletions plus change statistics. Version history is retained in full — there is no cap. Content edits to an already-published policy automatically create a new version snapshot. The version number advances only on content changes, not on metadata-only updates like renaming or changing the audience. ## Can I require employees to re-acknowledge after updating a policy? Yes. Each policy has its own **Re-acknowledge on Updates** switch; the setting **Require Re-acknowledgment When Policies Update** (on by default) is what new policies start with. When a policy's switch is on and you save a **Major** or **Legal** change to its published content, every employee who already acknowledged the previous version is flagged to re-acknowledge with a fresh deadline. A **Minor** change keeps every acknowledgment and asks no one. The same holds when you unpublish a policy, edit it as a draft and publish it again: the **Type of change** you pick on the draft decides, and publishing again with unchanged content asks no one. The re-acknowledgment deadline uses the policy's own deadline if set, or falls back to the tenant-wide default (14 days), or to a hard-coded 14 days if neither is configured. Employees see what changed since their last acknowledgment as a highlighted diff on the acknowledgment page. ## Can I schedule a policy to publish at a future date? Yes. Set the **Scheduled Publish Date** on a draft policy and it will publish automatically at that time. The scheduled date must be in the future. If publication approval is enabled for your tenant and the policy has not been approved by the scheduled time, it stays as a draft and loses its schedule — it will not publish without approval. ## How do I set up a comprehension check before acknowledgment? Open a policy, go to the comprehension-questions section, and add multiple-choice questions. Each question has answer options and one correct answer. Questions default to **inactive** — switch a question on when you are ready for it to gate acknowledgments. Once at least one question is active, employees must score at or above the passing threshold before their acknowledgment is accepted. The default passing score is **80%** and you can change it per policy. HR can see how many employees have attempted and passed. --- ## Day-to-day — Acknowledgments ## How are acknowledgments tracked? Each acknowledgment records the employee, the exact policy version, a timestamp, IP address, device type, and browser information as a full audit trail. Employees acknowledge with a confirmed click — they must check both "I have read" and "I agree to comply" boxes. The compliance report shows per-policy acknowledgment rates, and you can export the report to CSV. The Evidence Pack provides a per-person view of everything an individual employee owes and has signed, including the signed document when e-signature is used. IP address and browser details are masked by default in the Evidence Pack and require an elevated step-up authentication to reveal. ## Can I require a signature instead of a click? Yes. Turn on **Require a Signature** on the policy. Employees review the policy document and sign it in the app instead of click-acknowledging, and the signed PDF is kept as evidence. No E-Signature app, provider or integration is needed. Employees without an email address on file can still sign. They confirm it is them with a text-message code to the mobile number on their profile, or else their password or PIN. Someone with none of these is told on the signing page to ask HR to add a mobile number — they are never dropped back to a plain click. ## How do bulk acknowledgment campaigns work? Campaigns let you send acknowledgment requests for multiple policies to a targeted group of employees at once. Create a campaign, select the published policies that require acknowledgment, set filters for departments or locations, a due date, and whether to auto-remind. When you send the campaign, each recipient gets a document package containing the selected policies. Recipients with no email address on file are asked in their Inbox instead and sign in the app, confirming it is them with a text-message code, or their password or PIN. You can track completion rates, send reminders for outstanding packages, and cancel a campaign to void any pending signature requests. With auto-remind on, a campaign sends **one** automatic reminder to everyone who has not signed, when the due date is within the reminder window (7 days before it by default). **Resend Signature Requests** on the campaign reaches them again whenever you choose. --- ## How do I find who is overdue, and export the full list? Go to **Acknowledgments → Compliance Report**. The **Overdue** tile counts acknowledgments still pending past their deadline (someone who owes three overdue policies counts three times); select **View overdue acknowledgments** to open **All Acknowledgments** on its **Overdue** chip, which lists exactly the acknowledgments the tile counts. The **Compliance over the last 12 months** trend is built from a nightly snapshot, so a new workspace starts with one point and fills in night by night. For an audit, the Evidence Pack's **By policy → Roster** lists every targeted employee with their record or outstanding status, and **Export CSV** downloads the full roster however large it is. --- ## Day-to-day — Handbooks and sharing ## Can handbooks be shared externally? Yes. Published handbooks get a public URL with a clean custom slug. By default that link requires the viewer to **sign in** to your organization. An administrator can turn off **Require Sign-In for Public Handbook & Policy Links** in Policy Hub settings to allow anonymous viewing — useful for day-one onboarding reading before an employee has credentials. Individual policies can also be shared at a public URL when you turn on **Enable Public Link** on the policy (not available for a policy restricted to named readers). Both policies and full handbooks can be exported to PDF. --- ## Day-to-day — Translation and legal updates ## Can employees read policies in their own language? Yes, once you turn on **Enable Multi-Language Support** in Policy Hub settings. Your business must also have languages configured in General Settings. Policy Hub translates into **15 languages**: Spanish, French, German, Chinese (Simplified and Traditional), Portuguese, Vietnamese, Korean, Japanese, Tagalog, Arabic, Hindi, Russian, Italian and Polish. Other languages configured for your business are not offered for policy translation. Machine translations carry a disclaimer until a bilingual HR team member verifies them. You can download a bilingual PDF for side-by-side review. If the source policy is edited after translation, the translation is automatically flagged as stale so you know to refresh it. ## How does Policy Hub surface employment-law changes? Policy Hub shows employment-law change notifications with a severity level — Critical, Important, or Informational — sorted with the most urgent first. For each notification you can see which of your policies it affects, then mark it as reviewed, dismiss it, or apply a custom override. Every decision is logged in the activity trail. A separate **Compliance Check** tool (under the Policies tab) lets you pick a state and see the employment-law requirements your policies need to cover, drawn from the same rules catalog. --- ## When something looks wrong ## Why can't I acknowledge this policy? Three things can block an acknowledgment. First, if the policy has **required training courses** linked to it, you must complete those courses before the Acknowledge button becomes available. Second, if the policy has an active **comprehension check**, you must pass it with a score at or above the threshold (default 80%). Third, if the policy has **Require a Signature** on and you have no email address, mobile number, password or PIN to confirm it is you, the signing page asks you to have HR add a mobile number to your profile. If none of these apply and you still cannot acknowledge, the policy may no longer be published — only published policies accept acknowledgments. ## My acknowledgment shows as pending even though I already signed — what happened? Either the policy had a major or legal update after you acknowledged it, or your signature was due for renewal (some policies must be re-signed every so often, even when the text has not changed). In both cases everyone who signed earlier is flagged to acknowledge the current version. Your original acknowledgment is still on file, but you need to review and acknowledge the updated content before your status clears. On the acknowledgment page you will see a "What changed" section highlighting the differences since the version you last signed. ## I can't find a policy I know exists — where is it? If you are not an HR user, you can only see **published** policies that target your department, location, and state. A policy in draft, archived, or retired status is invisible to employees. If the policy is scoped to specific states and you are not assigned to a location in one of those states, you will not see it either. Ask your HR admin to check the policy's status and audience settings. If the policy was retired, an admin can reactivate it as a draft so it can be edited and republished. --- ## Licensing and limits ## Does Policy Hub require a licence? Yes. Policy Hub requires a licence and is disabled by default. An administrator enables it from Admin → Apps → All Apps. No policies, handbooks, or acknowledgment tracking is available until it is enabled. ## Are there limits I should know about? - **Acknowledgment deadline**: defaults to 14 days; configurable per policy and at the tenant level. - **Reminder frequency**: defaults to every 4 days for automated reminders (workspaces set up before this default changed keep 3). Each person gets at most five automated messages per policy, spaced by the reminder frequency: reminders while the policy is still within its deadline (never more than four), then overdue notices once the deadline has passed. - **Low-compliance alert threshold**: defaults to 50%. - **Word import size**: 10 MB per file. - **Bulk import**: up to 25 files per batch, 100 MB total. Accepts PDF and Word (.docx). - **Comprehension pass threshold**: defaults to 80%; configurable per policy. - **Review cadence options**: Monthly, Quarterly, Semiannual, Annual, or As needed (no schedule). - **Translation languages**: 15 supported languages. - **Version history**: unlimited — every publish is snapshotted with no cap. - **Campaign reminders**: one automatic reminder, 7 days before the due date by default. - **Training course picker**: shows up to 200 courses when linking training to a policy. --- ## More help - [Policy Hub Overview](/help/articles/policy_hub_app_overview) - Ask AI — the assistant answers Policy Hub questions from these articles. **Keywords:** faq, policy, handbook, acknowledgment, compliance, version control, re-acknowledgment, e-signature, require a signature, overdue, legal update, comprehension check, bulk campaign, translation, not showing, pending, approval, policy-hub, policy_hub --- # Portals App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-18 Central hub for managing every public-facing portal in your organization — catalog, branding, custom domains, identity recovery, security signals, and analytics. # Portals ## 1. What it is Portals is the single place to see and manage every public-facing portal your organization runs — the Candidate Portal, Customer Support Portal, Former Employee Portal, Guest Pass check-in, public forms, and more. Each of those portals is owned by its own app, but none of them can show you all the others. Portals fills that gap. From Portals an admin can browse a catalog of all portals, toggle each one on or off, configure the shared identity-recovery layer (the OTP and magic-link system that external visitors use to prove who they are), review a security feed of suspicious activity, apply unified branding, map custom domains, and view traffic analytics — all in one app instead of app by app. - **Enablement:** Portals requires a licence. An admin enables it in **Admin → Apps → All Apps**. Access is controlled through Portals app-admin assignment, not a configuration-driven role list. - **What it is not:** Portals does not replace each app's own portal settings. It is the umbrella view and the shared infrastructure (branding, recovery, domains). App-specific configuration — such as which jobs appear on the career site or which forms are public — stays in the owning app. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Portals**, and enable it. 2. Open **Portals → Catalog**. The catalog lists every portal whose owning app is licensed for your organization. Check that the portals you want are switched on — the row reads **Enabled**, or **Open** for a portal that also opens through its own app. **Off in its app** or **Open here · off in its app** means that app's own switch still keeps the portal shut — the line beneath names the setting; turn it on there. Toggle off any portal you do not need. 3. Open **Portals → Identity & Recovery**. Review the rate-limit window (default 60 minutes) and the maximum recovery requests per identifier per window (default 5). These settings govern every portal that uses the shared OTP / magic-link layer. 4. Open **Portals → Branding** if you want a consistent look across all branded portals. Upload your logo, set colors and fonts. Changes apply immediately to every portal that uses the shared branded layout. 5. Grant **App admin** for Portals to anyone else who should manage portals. Portals is open to Admins, Super Admins and people granted App admin for Portals — every tab. Anyone else is turned away at the door with "Portals is available to administrators only." **Silent-until-paired warning:** enabling Portals does not enable any individual portal. Every registered portal has a row in the Catalog, but a portal whose owning app is not licensed is marked **Unavailable** and cannot be switched on. If you enable Portals but have not licensed Job Board, for example, the Candidate Portal row stays **Unavailable** until Job Board is licensed. ## 3. How it fits together **Catalog vs. owning app.** The Catalog is the registry of all portals in your organization. It draws from a fixed list of 33 registered portal surfaces grouped into 13 categories (Recruiting, HR, Learning, Safety, Engagement, Forms, Documents, Facilities, Scheduling, Communications, Support, Field Service, and General). Only the portals whose owning app is currently licensed appear as toggleable. The Catalog controls whether a portal is reachable; the owning app controls what the portal contains. Toggling a portal off in the Catalog makes it unreachable even if the owning app is still enabled. That is the key distinction: the owning app decides *what* a portal shows; the Catalog decides *whether* it is accessible at all. For example: Job Board owns the Candidate Portal, Job Listings, and Job Alerts portals (all in the Recruiting category, grouped under the Career Portal heading). If all three are licensed and enabled in the Catalog, visitors can reach them. Disabling **Candidate Portal** in the Catalog leaves Job Listings and Job Alerts accessible while blocking candidate logins — without touching Job Board's own settings. When you save the Catalog with a filter active (by category, status, or search), only the portals visible on the current page are written. Portals hidden by the filter keep their previous state, so filtering does not accidentally disable everything out of view. **Identity & Recovery** is the shared authentication layer for external visitors. When a candidate, former employee, or customer requests a magic link or OTP to verify their identity, the request flows through this layer. It enforces a per-identifier sliding-window rate limit and logs every event into a hashed audit trail. Events are one of seven types: requested, sent, no match, consumed, failed, rate-limited, or invalid token. Identifiers (email addresses and phone numbers) are stored only as a one-way hash keyed to your organization — never as plaintext — so accessing the audit log does not expose contact information. A nightly rollup job aggregates audit events by portal and day into daily summaries. A separate nightly prune job deletes raw audit records and daily rollups older than the configured retention period. The rate limit and retention settings you configure in Identity & Recovery apply to every portal that uses the recovery layer. **Portal Hub** is the public landing page at `/portals` that lists every enabled portal for external visitors. It uses the shared branding you configure and lets visitors navigate to the portal they need without knowing a direct URL. Portal groups (such as the Career Portal group containing Job Listings, Candidate Portal, and Job Alerts) are displayed together under a shared heading. **Branding** is a single set of logo, colors, fonts, header/footer text, and optional custom HTML/CSS shared by every portal that uses the branded layout. One edit here updates every branded portal simultaneously. There is no on/off switch: until you customize something, every portal follows your workspace's **Brand & Theme**, and any setting you leave blank keeps following it. The branding record is versioned — the last 20 changes are visible on the Branding page, providing a history of who changed what. **Custom Domains** let you map your own hostnames (e.g. `careers.acme.com`) to a specific portal or to the full platform. Each domain is unique across all organizations. You add two DNS records its page shows — a proof record and a routing record — and its HTTPS certificate is issued and renewed for you; once the certificate is issued the domain counts as verified and switches on by itself. A hostname that is not verified within 30 days of being added is released, and its page shows the date. A **Careers** domain opens your public job board and a **Main** domain sends visitors to your OneMango sign-in page; a domain set aside for another single portal does what Main does — it does not open that portal's own page yet. A nightly background job re-checks DNS for every active domain and alerts admins if its routing record no longer points at us. The job does not automatically deactivate the domain — it warns so you can investigate whether the DNS change was intentional. **Two analytics surfaces.** Recovery Analytics (under the **Recovery Analytics** tab) charts the daily trend of recovery events — requested, sent, consumed, failed, rate-limited — over 7, 30, or 90 days, with a per-portal breakdown table. Traffic Analytics (under the **Traffic Analytics** tab) shows page views, unique visitors, sessions, bounce rate, device breakdown, and top pages across all portals, with date-range presets from today through the current year. Both are admin-only. ## 4. Running it ### Reviewing the portal catalog Go to **Portals → Catalog**. Each row shows the portal name, owning app, category, and enabled/disabled status, with a preview link when available. Filter by category (e.g. Recruiting, HR, Documents) or status (enabled, disabled, unavailable), or search by name. To change which portals are active, toggle the switches and save. Only portals whose owning app is licensed can be toggled — unlicensed portals appear as unavailable and cannot be turned on from here. Many portals open through their owning app as well (a survey's link, a paired kiosk, a Drive share link). Their rows show **Open** or **Closed**: switching one off closes its public page, and switching it on leaves it to the owning app as before. A separate **List on your public portals page** box decides whether that portal also appears as a tile on your public portals page. Turning a portal on never lists it by itself. Saving applies only to the portals currently visible after filtering, so you can safely save a filtered view without affecting portals hidden by the filter. ### Checking recovery health The **Dashboard** shows a 7-day snapshot of recovery activity: how many people asked for a sign-in link or code (recovery requests), how many were sent and how many were used, and a send success rate. The busiest portals by recovery events (named as the Catalog names them, each opening its rows in the Audit Log) and a count of anomalies (failures, rate-limited and invalid-token events) appear at a glance. A getting-started card appears for new installations until the first real recovery event is recorded. ### Monitoring security signals Go to **Portals → Security** (admin only). The Security tab surfaces derived signals from recovery audit data over an adjustable time window (default 24 hours): - **Repeat-failure IPs** — addresses generating the most failed, rate-limited, or invalid-token events. - **Identifiers near lockout** — hashed identifiers with the most flagged events, with a count of how many portals each has touched. - **Cross-portal patterns** — a single identifier requesting recovery across two or more different portals. - **Recent invalid-token events** — the latest attempts to use an expired or forged link. A background monitor runs every 15 minutes and notifies your Portals admins in-app and by email when the flagged events in one hour reach the alert threshold set on **Identity & Recovery** (default 25), unless **Recovery abuse alerts** is switched off in Settings. The alert fires once per spike, not repeatedly. ### Reviewing the audit log Go to **Portals → Audit Log** (admin only). Filter by portal, event type, IP address, identifier, or date range. The log shows 50 rows per page. Identifiers are stored as hashed values, not plaintext — to search, enter the original email or phone and the system hashes it for matching. Export the filtered set as CSV (capped at 10,000 rows per export). ### Updating branding Go to **Portals → Branding** (admin only). Upload a logo (PNG, JPEG, or WebP, up to 2 MB), favicon (PNG or ICO, up to 1 MB), or background image (up to 5 MB). Set the portal colors, header background and text colors, header and footer text, and fonts. Custom header/footer HTML (up to 50,000 characters each) is available when **Use custom header & footer HTML** is turned on; a custom stylesheet saved before can be removed but is no longer edited here. Click **Match workspace brand** to clear your portal-only settings so every portal follows Brand & Theme again. ### Managing custom domains Go to **Portals → Custom Domains** (admin only). Click **Add custom domain**, enter the hostname and select a purpose (the full platform, a specific portal, or careers). Its page shows the two DNS records to add — the proof record and the routing record — with copy buttons and whether each is found yet; add them at your DNS host within 30 days, or the hostname is released. Once its certificate is issued, the domain switches on by itself (**Check again** asks at once). To take a domain offline without deleting it, click **Deactivate**. Changing the hostname gives it a new certificate, and the new name's records to add. ### Viewing traffic analytics Go to **Portals → Traffic Analytics** (admin only). The dashboard shows total page views, unique visitors, sessions, bounce rate, pages per session and — on portals that measure it — average time on page, for the selected date range. Filter by portal to drill into a single surface. Use the date-range picker (today, yesterday, last 7 days, last 30 days, this month, last month, this year). Per-portal detail pages show the same metrics scoped to one portal. Export the current view as CSV. ### Mobile access The Portals dashboard, Audit Log, and Security views are available on mobile at `/m/apps/portals`. Branding, Custom Domains, Settings, and Traffic Analytics remain desktop-only. Phone-class devices are automatically redirected from the desktop dashboard to the mobile view. ## 5. Settings Portals has two settings surfaces. **Settings** controls which tabs are shown, the two security alerts and the Portals assistant. **Identity & Recovery** holds the four numbers that govern the recovery layer. ### Switches (Portals → Settings) | Setting | Default | What it changes | |---|---|---| | Enable Portals AI Agent | On | Whether the read-only Portals assistant answers in Ask AI. It answers only for Portals admins. | | Show portal catalog | On | The Catalog tab, and with it the on/off switches for public portals. Portals already open stay open while it is off. | | Analytics rollups and traffic analytics | On | The Recovery Analytics and Traffic Analytics tabs. Nightly rollups and visitor tracking keep running either way. | | Identity & Recovery effectiveness signals | On | The 30-day effectiveness figures on the Identity & Recovery page. The page itself and its limits are never hidden. | | Security signals tab | On | The Security tab. Alerting is the separate switch below. | | Recovery abuse alerts | On | The in-app and email alert when recovery failures spike. Independent of the Security tab. | | Recovery audit log | On | The Audit Log tab, its CSV export and the recovery figures on the dashboard. Events keep being recorded and pruned either way. | | Portal branding | On | The Branding tab. Your portals keep their branding while it is off. | | Custom domain mappings | On | The Custom Domains tab. Verified, active hostnames keep resolving while it is off. | | Custom domain drift alerts | On | The alert when a live custom domain stops passing DNS verification. Independent of the Custom Domains tab. | Turning a tab's switch off hides it from navigation; a bookmarked link to it returns to the Portals dashboard with a message naming the switch. Both alerts go to your Portals admins, and each person can mute them for themselves under **Portal Security Alerts** in their notification preferences — one switch there covers both alerts. Settings are stored per-organization. The **Sample Data** section at the bottom of the Settings page lets you generate a small set of synthetic recovery audit events so you can preview the Audit Log and Identity & Recovery dashboards before real traffic arrives. The sample data is safe to regenerate or remove at any time. ### Identity & Recovery thresholds (Portals → Identity & Recovery) | Setting | Default | What it changes | |---|---|---| | Window (minutes) | 60 | The sliding window over which recovery events are counted per identifier (5–1,440) | | Max recorded recovery events per identifier per window | 5 | The rate limit (1–20). Each recovery attempt records two events — the request and its outcome — so the default of 5 allows 3 attempts per window; the page shows the number of attempts your setting allows | | Alert threshold (flagged events per hour) | 25 | How many failed, rate-limited or invalid-token events in one hour, across your whole business, trigger the recovery abuse alert (5–500) | | Retention (days) | 180 | How long audit records and daily rollups are kept before the nightly prune job deletes them (7–3,650) | These four settings are shared across every portal that uses the recovery layer. Per-portal overrides are not exposed in the UI. ## 6. More help - **Portals FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about Portals from these articles. **Keywords:** portals, public portals, portal catalog, portal branding, custom domains, vanity domains, identity recovery, portal security, recovery audit log, portal analytics, portal hub, magic link rate limit, DNS verification --- # Portals FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-18 Answers to common setup and operating questions about Portals — for the admin running it. # Portals FAQ Answers to common setup and operating questions about Portals. For what the app is and how to set it up from scratch, see the [Portals Overview](/help/articles/portals_app_overview). --- ## Setup ## Do I need to configure anything before the catalog shows portals? No. Once Portals is enabled, the Catalog automatically lists every portal whose owning app is licensed for your organization. You do not need to register portals individually. If you license a new app that owns a portal, its portals appear in the Catalog the next time you open it. ## Who can access Portals, and which tabs are admin-only? Portals is open to **Admins**, **Super Admins** and people granted **App admin** for Portals — every tab. Anyone else is turned away at the door with "Portals is available to administrators only." Some tabs can be switched off for everyone in **Portals → Settings**. --- ## Day-to-day ## Does Portals own each portal's on/off toggle? Yes. The Catalog is where you enable or disable individual portals. The owning app controls the licence: a portal only appears in the Catalog when its owning app is licensed. Licensing lives with the app; the on/off switch lives in Portals. ## What does "Identity & Recovery" actually control? Three business-wide things. First, the rate limit for the shared OTP and magic-link layer: the sliding window (default 60 minutes, accepts 5–1,440) and the maximum recorded recovery events per identifier per window (default 5, accepts 1–20). Each attempt records two events, so the default allows 3 attempts per window. Second, the alert threshold — how many flagged events in one hour trigger the recovery abuse alert (default 25, accepts 5–500). Third, how long recovery audit records are retained before the nightly prune deletes them (default 180 days, accepts 7–3,650). Whether a portal uses a magic link or an OTP code is fixed by the owning app, not a Portals setting. ## What's the difference between Recovery Analytics and Traffic Analytics? Recovery Analytics charts the OTP and magic-link flow — nightly rollups of requested, sent, consumed, failed, and rate-limited counts over 7, 30, or 90 days, with a per-portal breakdown. Traffic Analytics measures visitors — page views, unique visitors, sessions, bounce rate, device mix, and top pages across portals. One tracks how portal login recovery is performing; the other tracks who is visiting. ## How do I set up portal branding? Go to **Portals → Branding**. Upload your logo, set brand and accent colors, choose fonts, and add header and footer text. Changes apply immediately to every portal that uses the shared branded layout. Turn on **Use custom header & footer HTML** to add your own header and footer markup. Any setting you leave blank follows your workspace's **Brand & Theme**; click **Match workspace brand** to clear your portal-only settings so every portal follows it again. ## How do I map a custom domain to a portal? Go to **Portals → Custom Domains** and click **Add custom domain**. Enter the hostname and choose its purpose (the full platform, a specific portal, or careers). The domain's page then shows two DNS records to add at your DNS host, each with a copy button: a **proof record**, which shows the domain is yours and lets its HTTPS certificate renew by itself (keep it), and a **routing record**, which points the hostname at us. We check them every few minutes; once the certificate is issued, the domain counts as verified and switches on by itself, and **Check again** asks at once. A hostname not verified within 30 days is released. A bare domain such as `acme.com` cannot take a CNAME: use a subdomain, or your DNS host's flattening. A **Careers** domain opens your public job board and a **Main** domain sends visitors to your OneMango sign-in page; a domain set aside for another single portal does what Main does for now, not open that portal's own page. ## Is the recovery audit log sufficient for compliance reviews? Every recovery event is logged with a timestamp, IP address, user-agent, and a one-way hash of the identifier, keyed to your organization — never plaintext email or phone. Retention is configurable (default 180 days, minimum 7) and enforced by an automatic nightly job. You can export filtered results as CSV, capped at 10,000 rows per export. For SOC 2 or HIPAA-style reviews this is generally sufficient; confirm specifics with your compliance team. ## Can I ask the AI agent about my portals? Yes. The Portals agent lives in Ask AI and answers questions like "How is portal recovery doing this week?" or "Which portals are enabled?". It is read-only and admin-gated — non-admin users never see its tools. Turn it off in **Portals → Settings** by disabling **Portals AI Agent**. --- ## When something looks wrong ## I never received my portal login link — what happened? The most common causes: the email address entered does not match the one on file, or the request was rate-limited. An admin can check by opening **Portals → Audit Log** and filtering by the identifier. If the event shows **Rate limited**, the visitor must wait for the current window to expire before trying again. A **Sent** event with no **Consumed** event means the link was delivered but never clicked — check spam folders. ## Why am I locked out of the portal even though I haven't requested that many codes? The recovery layer has two separate rate limits. The request side caps how many times you can ask for a code — at the default setting that is 3 requests per 60-minute window, because each request records two events and the limit (default 5) counts events. The verification side caps wrong code entries: 10 invalid attempts within 15 minutes from one device blocks verification for that identifier on that portal for 15 minutes, and that limit is fixed — raising the rate limit in Identity & Recovery does not change it. Both are visible in the Audit Log. ## I keep getting "Invalid code" when I try to verify — what's going on? OTP codes expire after a period set by the owning app. If the code has expired, request a new one. If you have entered 10 or more incorrect codes within 15 minutes, verification is temporarily blocked. Wait 15 minutes and request a fresh code. ## A portal I've licensed isn't appearing in the Catalog — why? Every registered portal has a row in the Catalog, but a portal whose owning app is not licensed *and* enabled for your organization is marked **Unavailable** and cannot be switched on. Confirm the owning app is enabled in **Admin → Apps → All Apps**. Some portals may not be obvious: Guest Pass Check-In requires the Guest Pass app, Customer Support Portal requires Service Desk, and Candidate Portal requires Job Board. --- ## Licensing and limits ## Does Portals require a licence? Yes. Portals needs a licence — ask your MangoApps account team. Once it is licensed, an admin turns it on under **Admin → Apps → All Apps**; it is off until then. ## What are the limits I should know about? | Limit | Value | |---|---| | Portals in the catalog | 33 across 13 categories | | Rate-limit window | 60 minutes default (accepts 5–1,440) | | Max recorded recovery events per window per identifier | 5 default (accepts 1–20) — 3 recovery attempts at the default | | Recovery abuse alert threshold | 25 flagged events per hour default (accepts 5–500) | | Wrong-code entries before verification pauses | 10 within 15 minutes from one device (fixed) | | Audit retention | 180 days default (accepts 7–3,650) | | Audit CSV export cap | 10,000 rows per export | | Logo upload | PNG, JPEG, or WebP; max 2 MB | | Background image upload | PNG, JPEG, or WebP; max 5 MB | | Favicon upload | PNG or ICO; max 1 MB | | Custom CSS | No longer edited on the Branding page; a stylesheet saved before can be removed | | Header text | Max 500 characters | | Footer text | Max 1,000 characters | | Custom header/footer HTML | Max 50,000 characters each | | Fonts | Any font in the font picker Brand & Theme uses | | Security window | Default 24 hours (accepts 1–168) | | Audit log page size | 50 rows per page | --- ## More help - [Portals Overview](/help/articles/portals_app_overview) - Ask AI — the assistant answers Portals questions from these articles. **Keywords:** faq, portals, portal catalog, identity recovery, rate limit, audit log, branding, custom domains, magic link, OTP, portal security, portal analytics, traffic analytics --- # Power Tables App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run Power Tables — typed data tables that scale to millions of rows, with CSV import, saved views, automations, and Live Boards integration. # Power Tables ## 1. What it is Power Tables lets you create typed data tables that scale to millions of rows. Each table you create is a real database table with defined column types, so sorting, filtering, and reporting run at database speed rather than in the browser. You can import data from CSV or Excel files (by hand or on a nightly schedule), set up automations that fire on row changes or on a schedule, let people count stock from a phone with counter columns, and connect tables to Live Boards for dashboards and signage. - **Enablement:** Power Tables is a pay-as-you-go app billed per 1,000 rows stored. An admin enables it from Admin → Apps → All Apps — no separate licence decision is required. - **Vocabulary:** one entry in a table is a **row**. (Some databases call it a "record"; Power Tables consistently says row, and so does this article.) - **What it is not:** Power Tables is the data layer. It does not chart or visualize data on its own — that is Live Boards' job. A saved view in Power Tables defines which rows and columns to show; a Live Board binds to that view to render tiles, gauges, and leaderboards. It is also not a spreadsheet — there are no formulas and no cell-by-cell editing in the grid; that is AI Sheets' job. - **Mini Apps are built elsewhere:** a Mini App (Inventory, a visitor log, a custom tracker with its own name, icon, and sidebar entry) is **authored in App Builder**, not here. Power Tables is the substrate underneath it. See "Mini Apps" in Key Concepts below. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Power Tables**, and enable it. 2. Open **Power Tables → Tables**. Create your first table — give it a name, then add typed columns (Text, Number, Date, Currency, Dropdown, and others). You can also use **Create with AI**: describe what you want to track and AI proposes columns for you to review before creating. 3. Grant access. By default every user who can reach the app can see every table. To restrict a table to specific people or groups, open the table's **Sharing** page and switch the access mode to **Restricted**, then add grants. Grant levels are **Viewer** (read rows), **Contributor** (also add and edit rows), and **Manager** (also rename or archive the table and manage its sharing — columns, imports, and automations stay with app admins). 4. Confirm it worked: your users should see Power Tables in the app launcher and be able to open the tables they have access to. On mobile, employees get a **read-and-count** surface at **/m/apps/power-tables** — table cards and searchable row cards, plus − / + steppers on any counter column. Adding rows, importing, and exporting stay on desktop. ## 3. Key Concepts (How It Works) A few of these words get used interchangeably in conversation and mean different things in the product. This section is the disambiguation. ### Table vs. view vs. board - A **table** is the data — a real database table with typed columns, holding every row. - A **view** is a named *slice* of one table: filters, sort order, and which columns are visible. It stores no rows of its own. Every table starts with an "All rows" view, and you author more from the grid. - A **board** is a *display* — a leaderboard, stat tile, gauge, or grid — and it lives in the **Live Boards** app, not here. A board binds to a **view**, never to a raw table, so the view is where you decide exactly which rows and ordering the board reflects. Refine the view and every board on it updates. ### Shared views vs. personal views - **Shared** views belong to the table and are visible to everyone who can see it. - **Personal** views belong to one user and are visible only to them. The difference matters twice: **only shared views can feed a Live Board**, and only shared views can be used as the row selector for a scheduled automation rule. If a board reports "source unavailable," a personal view is a common cause. The two also draw on separate pools — shared views are a configurable quota, personal views have a fixed per-user cap. ### Tables and columns A table has a name, a description, and a set of typed columns. Each column has a type that determines what values it accepts and which filter operators are available. The thirteen column types are: Text, Long text, Number, Currency, Checkbox (yes/no), Date, Date & time, Dropdown (admin-defined options), Email, URL, Person (a reference to an employee), File (an attachment on a row), and Link to a table (a pointer to a row in another table). Text, long text, dropdown, number, currency, date, email and URL columns can change type later (to text, dropdown, number or date) keeping their values; checkbox, date & time, person, file and link columns are fixed once created. One column is the table's **row label column** (**Edit table → Row label column**) — the value from that column names each row wherever it is referenced (assignment notifications, the phone cards, the Activity log). Left on **Automatic**, the first text column is used. A text, long text, dropdown, number, currency, date, email or URL column can **change type in place** (to text, dropdown, number or date) from its Edit drawer — every value is kept, or the change is refused naming what's in the way; other types are fixed once created. A column's **name** can always change: renaming is instant at any table size, because everything in the product references columns by ID rather than by name. ### Counter columns are a behaviour flag, not a column type A **counter column is not a fourteenth type.** It is an opt-in setting on an existing **Number** column ("Show − / + steppers for quick counting" on the column form). Ticking it changes only how the value is *entered*: - The desktop grid, the row drawer, and the mobile card render **− / + buttons** instead of a typed field, for anyone who can write rows on that table. (Viewers see the plain number.) The mobile steppers work without JavaScript. - A tap sends the **change, not the answer**. The server takes a lock on the row and applies `new = max(0, current + delta)`. So if a shelf holds 12 and two people each tap − at the same moment, the result is 10 — never 11. This is why counting from several phones at once is safe. - Counts **floor at zero**; you cannot drive a counter negative. - Because a tap is a delta, counter adjustments deliberately carry **no "someone else changed this" conflict check** — deltas compose, so there is nothing to conflict over. Typing an absolute value in the drawer still gets the normal check. - Each adjustment can carry a short **change note** ("used in OR 2"), up to 500 characters. Untick the flag and the same column goes back to being an ordinary number field. Nothing about the stored data changes. ### Relative date windows Date and Date/time filters can be written as a *window* rather than a fixed value. Eight operators are available: **today, yesterday, this week, this month, this quarter, this year, last N days,** and **next N days**. Both ends of the window are recomputed on the server every time the filter runs, so a view saved as "expiring in the next 30 days" keeps meaning that instead of freezing to the day it was saved. The same vocabulary drives Live Boards periods, saved-view alerts (**View options → Alert me**), and the AI agent (the agent covers all but *next N days*). ### Access mode vs. grant These are two different controls and both are needed to restrict a table. - The **access mode** is the table's posture: **Everyone** (the default — anyone with app access can open it) or **Restricted**. - A **grant** names one person or one recipient group and gives them **Viewer**, **Contributor**, or **Manager** rights on that table, with an optional expiry. Grants only take effect on a **Restricted** table. On an Everyone table they are inert — everyone can already see it. A grant can raise a plain member to Contributor or Manager on one table without changing their app-wide role, and admins always have full access regardless of grants. ### Archive vs. delete Nothing in Power Tables is deleted the moment you press the button. - **Archiving a table** moves it to the Tables list's **Archived** tab — **Restore** is in its ⋮ menu — and removes it from Live Boards, the API, and mobile. That starts a **7-day grace period**, after which it is permanently purged. A warning goes out 24 hours before the purge. Restoring counts against your table quota, so you need room under the limit. - **Deleting rows** (single, bulk, by an automation rule, or the clear step of a replace-mode import) sends them to the table's **Deleted rows** page, where an admin can restore a whole batch for 30 days. A restored row is re-inserted through the normal write path, so it is a new row that inherits current column rules. - **Archiving a column** is refused outright while something depends on it — see below. Exact retention windows are in the FAQ. ### Columns in use cannot be archived out from under what depends on them If you try to archive a column that an **enabled automation rule** references, that an **active Live Board** renders as its entity or score column, or that a **bound Form** maps to (including as its match column), Power Tables refuses and **names each consumer** in the message, so you know exactly what to edit first. Renaming that same column is always safe. ### Automations Rules that fire actions when something happens. Two trigger families exist: **row events** (a row is created, a row is updated, a *named field* changes, a row is deleted) and **schedules** (daily, weekly, or every N minutes). A scheduled rule binds to a shared view whose filters select the rows it acts on. Actions include updating fields, notifying a user, sending an external email, requesting approval, creating a task, calling a webhook, marking a row locked or archived (this writes a status value — the row stays editable), deleting a row, and three AI actions (fill a column, summary digest, anomaly alert). Rules that fail five consecutive times pause themselves automatically and notify their owner. ### Forms → table binding A Forms template can point at a Power Tables table, so a submission becomes a typed row. The binding lives on the **form template**, and it has two modes: - **Append** (the default) — every submission adds a new row. Ingest is idempotent, so a form that passes through several completed states still produces exactly one row, and editing a submission later does not rewrite the row it created. - **Update** (stock-take semantics) — the binding names a **match column**. The submission's answer for that column finds the existing row, and every other mapped answer is written onto it. "How many are left?" updates the master item instead of appending a log line. If nothing matches, the binding decides whether to create a row or record a visible skip; if two rows match, it stops rather than guess. This is the recommended capture path for frontline users: Forms already has a mobile surface, validation, and an audience model, so a form is a narrow door onto a table. ### Barcode scanning Any **Text** column can be marked "Scan a barcode or QR code into this field." The row editor then offers a **Scan** button that reads the code with the camera and drops the value into the field, with typed entry always available as a fallback. On a phone, **Scan a code** under a table's search box reads a label and finds its row. Supported symbologies: QR, Code 128, Code 39, EAN-13, EAN-8, and UPC-A. ### Quotas vs. the billing meter These are unrelated, and confusing them leads to the wrong fix. - **Quotas** are *capacity guardrails* on shared infrastructure — how many tables, rows, columns, indexes, shared views, and automation rules you may have. They cost nothing. Most can be raised by an admin in Settings up to a self-serve ceiling, and beyond that by MangoApps support. - The **billing meter** is what you pay for: rows stored, counted nightly across your **active** tables and charged per 1,000 rows per year. Archived tables, MangoApps sample data, and tables a turned-on mini app owns are not counted. There is no per-seat charge and no monthly floor. So raising a quota does not raise your bill, and lowering one does not lower it. Storing fewer rows is the only thing that changes what you pay. ### Mini Apps A **Mini App** — Inventory, a visitor log, a custom tracker with its own name, icon, and place in the sidebar — is **created in App Builder**, not in Power Tables. An admin describes what they need in plain language and gets a real app at its own address, with its own records, fields, views, rules and board. A mini app runs whether or not Power Tables is turned on, and while it is turned on its lists are managed inside the app — they do not appear in the Power Tables list. A mini app carries its own permissions — a frontline user can be given one narrow door ("report a count for this item") without being able to browse or edit the whole list behind it. **While a mini app is turned on, its records never bill through Power Tables:** they count under App Builder, where each mini app's first 25,000 records are included and records beyond that bill as app records. Turn the app off (from its Edit with AI page in App Builder, or the Apps Marketplace) and its tables are back in the Power Tables list and on the Power Tables meter until it is turned on again; the on/off switch on the app's own Settings page only hides the app and changes neither. See the [App Builder Overview](/help/articles/app_builder_app_overview). ### Live Boards Boards bind to a Power Tables **shared** saved view to render tiles, leaderboards, gauges, and grids on dashboards and Digital Signage. A board reads a view, never a raw table, so the view's filters control what the board shows. ## 4. Running it ### Creating and populating a table 1. Go to **Power Tables → Tables** and click **New Table**. 2. Name the table, add columns, and choose types. You can set validation rules per column (required, min/max for numbers and dates, a regex pattern for text). While adding a column you can also tick **Show − / + steppers for quick counting** on a Number column, or **Scan a barcode or QR code into this field** on a Text column. 3. Add rows manually from the table grid, or import from CSV or Excel. During import you map file columns to table columns; the app remembers the mapping for future imports. ### Counting stock 1. Edit the Number column that holds the quantity and tick **Show − / + steppers for quick counting**. 2. That column now shows − / + buttons in the desktop grid, in the row drawer, and on a phone at **/m/apps/power-tables**. Tapping either one applies the change on the server, so several people can count the same shelf at once without overwriting each other, and the value never goes below zero. 3. In the row drawer, type a short **note** beside the stepper before tapping ("used in OR 2") to record *why* the count moved. Notes are capped at 500 characters. 4. Review those notes in the **row's own History panel** — open the row and expand History — or, as an admin, on the table's **Activity log**. Both show the note beside the change it belongs to. ### Binding a Form to a table 1. Open the table's **Set up** page and choose **Feed from a Form**, then pick a form template. 2. Map each form field to a table column. 3. Pick the mode. **Add a new row per submission** is the default. **Update the matching row** turns the form into a stock-take: choose the **match column**, and each submission finds that row and updates the other mapped answers instead of appending. 4. The binding's health — including the reason for any submission that did not land — shows on the table's Set up page. ### Importing data on a schedule 1. Open the table's **Set up** page and, on the **Scheduled import** card, click **Set up a schedule**. 2. Provide the source. A **public HTTPS URL** needs no setup at all. A **protected HTTPS endpoint** or an **SFTP server** binds to a connection an admin configures once at Admin → Organization → Integrations. 3. Choose the mode: **Replace** (clears existing rows first — the source is the system of record) or **Append** (adds rows each run). 4. Enable the schedule. It runs nightly, and a **Run now** button triggers it on demand. The last run's status and any error appear on the table's **Set up** page, which is also where **Run now** is; the run history is on the Analytics page. ### Exporting data on a schedule 1. On the table's **Set up** page, on the **Scheduled export** card, click **Set up an export**. 2. Select an SFTP connection (configured under Admin → Organization → Integrations) and a remote path. Scheduled exports are **SFTP only** — an export has to push to a credentialed destination, so there is no HTTPS option here even though scheduled *imports* have one. 3. Choose the format: **CSV** or **XLSX**. 4. Enable the schedule. Each run writes the table's current rows to the destination. ### Archiving a column Archiving a column is refused while an enabled automation rule, an active Live Board, or a bound Form still depends on it. The refusal message names each one — edit or remove those first, then archive. Renaming the column instead is always safe and takes effect immediately. ### Setting up automations 1. Open a table and go to the **Automations** tab. 2. Create a rule: pick a trigger (row event or schedule), add conditions, then add actions. 3. For a scheduled rule, bind it to a shared view — the view's filters select which rows the rule acts on. The view must not use personal filters (the "@me" sentinel never matches for a scheduled run). ### Recovering deleted rows When rows are deleted, they are kept for 30 days. Open the table's **Deleted rows** page to see batches grouped by the action that deleted them (single delete, bulk delete, or import replace). Restore a batch to re-insert the rows as new rows. ### Reviewing activity Two different surfaces answer two different questions. - The **row's History panel** (open a row, expand History) is the field-by-field trail for that one row: which column changed, old value to new, who did it — or "Automation · rule name" when a rule did — and the **change note** on any counter adjustment. - The table's **Activity log** is the table-wide feed of who created, updated, or deleted rows. It shows a counter adjustment's note beside the change too. Imports and bulk inserts are deliberately not logged row by row; the import task record is the audit trail for those. The app-level **Analytics** page shows cross-table activity, schedule health, automation health, quota usage, and inventory flags (empty tables, tables with no writes in 30 days, archived tables awaiting purge). ## 5. Settings All settings are at **Power Tables → Settings** (admin only). There are ten in total: the six limits below, plus assignment notifications, the AI agent switch, Create-with-AI, and the default currency. ### Limits Each limit shows current usage and a utilization bar. A limit cannot be set below what is already in use. | Setting | Default | What it changes | |---|---|---| | Max tables | 5 | How many active tables the business can have | | Max rows per table | 1,000,000 | Row cap per table — import and manual entry both check this | | Max columns per table | 25 | Active columns per table | | Max indexed columns per table | 4 | Columns with a database index for faster filtering | | Max shared views per table | 25 | Shared saved views per table (personal views have a separate per-user cap) | | Max automation rules per table | 25 | Automation rules per table | Limits can be raised up to a self-serve ceiling. Past that ceiling, contact MangoApps support. If MangoApps staff have raised a limit for your account, the settings page shows a note. Personal saved views are bounded separately by a fixed per-user cap that is not listed here and cannot be raised. Exact defaults, ceilings, and the personal-view cap are in the FAQ. Raising a limit does not change your bill — see "Quotas vs. the billing meter" above. ### Notifications | Setting | Default | What it changes | |---|---|---| | Tell people when a row is assigned to them | On | Sends an Inbox item — "*Actor* set *column* to you on *row* in *table*" — when a Person column names someone on a single-row write. A bulk edit that sets a Person column sends that person one summary notice instead of one per row. Imports, sample data, form submissions, automation writes, and restored rows never send it, whatever this is set to. | ### AI | Setting | Default | What it changes | |---|---|---| | Enable the Power Tables AI agent in Ask AI | Off | Lets Ask AI answer questions about your tables; with confirmation it creates tables, views and indexes for admins and adds or updates rows for contributors. Off by default because the agent both reads every row of every table and carries write tools. | | Enable Create-with-AI for new tables | On | Adds a "Create with AI" panel to the New Table drawer — describe what to track and AI proposes typed columns. Only your typed description leaves the tenant; row data never does. | ### Currency | Setting | Default | What it changes | |---|---|---| | Default currency for money columns | USD | The currency unit shown on Currency columns that don't declare their own — appears in the grid, row form, and on Live Boards. Individual columns can override this; stored amounts are never converted. | ### Sample data The settings page also offers **Load Sample Data** and **Remove Sample Data**. Sample data creates several tables with rows, saved views, Live Boards, access grants, schedules, and view alerts so every surface has something to show. Sample import and export schedules are seeded paused — nothing runs on its own. ## 6. More help - [**Power Tables FAQ**](/help/articles/power_tables_app_faq) — specific setup and operating questions, and the exact numbers: file size limits, quota ceilings, retention windows, and pricing. - [**Live Boards Overview**](/help/articles/live_boards_app_overview) — building the leaderboards, tiles, and gauges that bind to your saved views. - [**Forms Overview**](/help/articles/forms_app_overview) — the capture surface to bind to a table. - [**App Builder Overview**](/help/articles/app_builder_app_overview) — where Mini Apps are actually created. - Ask AI — the assistant answers questions about Power Tables from these articles. **Keywords:** power tables, data tables, database, import csv, saved views, automations, rows, columns, live boards, export, counter columns, counting, stock take, barcode, relative dates, forms, mini apps, power-tables, power_tables --- # Power Tables FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Power Tables — for the admin running it. # Power Tables FAQ Answers to common setup and operating questions about Power Tables. For what the app is and how to set it up from scratch, see the [Power Tables Overview](/help/articles/power_tables_app_overview). --- ## Setup ## Do I need to configure anything before my team can use Power Tables? An admin must enable the app from Admin → Apps → All Apps — it is off by default. Once enabled, every member with app access can open and search tables. No other configuration is required before creating your first table, but you may want to review the quota settings (max tables, rows, columns, and indexes) and set a default currency for money columns in the app's Settings tab. ## What settings does Power Tables have? Ten, all at **Power Tables → Settings** (admin only): | Setting | Default | |---|---| | Max tables | 5 | | Max rows per table | 1,000,000 | | Max columns per table | 25 | | Max indexed columns per table | 4 | | Max shared views per table | 25 | | Max automation rules per table | 25 | | Tell people when a row is assigned to them | **On** | | Enable the Power Tables AI agent in Ask AI | **Off** | | Enable Create-with-AI for new tables | **On** | | Default currency for money columns | **USD** | The six limits are quotas (see "What are the quotas" below). The assignment-notification switch controls the Inbox item sent when a Person column names someone on a single-row write, and the one summary notice a bulk edit of a Person column sends that person instead of one per row. Imports, sample data, form submissions, automation writes, and restored rows never notify, whatever this is set to. The default currency applies to Currency columns that do not declare their own; individual columns can override it, and stored amounts are never converted. ## Who can create tables and who can only view them? Power Tables has three tiers of access. **Admins** (business admins, super admins, or anyone granted the Power Tables app-admin role) can create tables, define columns, import data, manage settings, and archive tables. **Contributors** (users granted the Power Tables contributor role) can add and edit rows but cannot change columns, run imports, or manage settings. **Everyone else** with app access can open tables, filter, sort, and search — viewing is not a privileged action. --- ## Permissions and access ## Can I restrict a table so only certain people see it? Yes. Each table has an access mode. The default — **Everyone** — means any member with app access can open the table. Switching to **Restricted** hides the table from everyone except admins and the people or groups you grant access to. Grants come in three levels: **Viewer** (can open the table and read rows), **Contributor** (can also add and edit rows), and **Manager** (can also rename or archive the table and manage its sharing — columns, imports, and automations stay with app admins). Admins always have full access regardless of grants. Grants can target individual users or notification recipient groups, and they support optional expiry dates. ## Why can't an employee see a table I shared with them? Three things to check: (1) the app itself must be enabled for the business and accessible to the user through Access Management visibility rules, (2) the table's access mode must be **Restricted** with a grant for that user or a group they belong to — on an **Everyone** table grants are inert, and (3) the grant must not have expired. If a restricted table has no active grant for the person, Power Tables returns a "not found" response rather than a "forbidden" one. --- ## Day-to-day ## Can I change a column's type after creating it? Yes, for text, long text, email, URL, dropdown, number, currency and date columns. Open the column's **Edit** drawer and pick the new type — it can become text, a dropdown, a number or a date. Every value is kept, or the change is refused with the reason: a value that wouldn't fit the new type (named, so you can fix it first), or a rule, board, form or view that still depends on the column. A column becoming a dropdown takes the values it already holds as its options unless you list them. In a table an app owns, ask **Edit with AI** in App Builder instead. Other types (Checkbox, Date & time, Person, File, and Link to a table) keep their type — add a new column for those. Renaming a column is instant at any table size. ## What column types are available? There are 13 types: **Text**, **Long text**, **Number**, **Currency**, **Checkbox** (yes/no), **Date**, **Date & time**, **Dropdown** (with admin-defined option lists), **Email**, **URL**, **Person** (picks a person with the people picker), **File** (an attachment on a row — photos, signed documents), and **Link to a table** (a pointer to a row in another table). File columns cannot be populated through CSV import; attach files from the row drawer after import. A **counter column is not a fourteenth type** — it is a tick-box on a **Number** column that swaps the typed field for − / + steppers. See the counting questions below. ## How do validation rules work? Each column can enforce rules on every write — including imports and the API. Available rules depend on the column type: **Required** is available on all types. **Min/max** bounds are available on number, currency, date, and date & time columns. **Regex pattern** is available on text, long text, email, and URL columns. Rules are enforced per row during imports, and rows that fail validation are skipped with an error reported against that row number. ## Why won't Power Tables let me archive a column? Because something is still using it. Archiving a column is refused while any of three consumers depends on it: 1. An **enabled automation rule** that references the column in its trigger, conditions, or actions. 2. An **active Live Board** that uses the column as its entity or its score column. 3. A **bound Form** that maps a field to the column — including using it as the match column in update mode. The refusal names each one by name ("*Stock Count* can't be archived: it's used by the automation rule "Reorder alert" and the board "Low stock"…"), so you can go and edit or remove those first. This is deliberate: archiving the column anyway would pause the rules and blank the boards behind a success message. **Renaming the column is always safe**, at any table size and with no dependency check, because everything in the product references columns by ID rather than by name. If you only want to relabel it, rename instead of archiving. ## What happens when I archive a table? The table moves to the Tables list's **Archived** tab — **Restore** is in its ⋮ menu — and disappears from Live Boards, the API, and mobile. Any Live Boards bound to a view on it show a "source unavailable" message. You have **7 days** to restore it; after that the data is permanently deleted. A warning notification is sent to the creator and admins 24 hours before the permanent deletion. Restoring an archived table counts toward your table quota, so you must have room under your limit to restore it. ## Can I undo a row deletion? Yes, for a limited time. Deleted rows (single deletes, bulk deletes, automation deletes, and rows cleared by a replace-mode import) are kept for **30 days**. An admin can restore a batch from the **Deleted rows** page on each table. A restored row is re-inserted as a new row through the normal write path, so it inherits current column rules and counts against the row quota. For replace-mode imports that cleared more than 50,000 rows, the kept set may be partial — the page discloses this. --- ## Counting, mobile, and scanning ## How do counter columns work? Tick **Show − / + steppers for quick counting** on any **Number** column. That column then renders − / + buttons instead of a typed field in three places: the desktop grid, the row drawer, and the mobile card at `/m/apps/power-tables`. The mobile steppers are plain form buttons and work with no JavaScript at all. The steppers appear only for people who can **write rows** on that table — contributors, managers, and admins. Viewers see the plain number, which is the usual reason someone reports "I don't have the buttons." The tick is a behaviour flag, not a new column type. Untick it and the column goes back to being an ordinary number field; the stored data is unchanged either way. It is also number-only: setting the flag on any other type does nothing. ## Can two people count the same shelf at the same time? Yes — that is the whole point of counter columns. A tap sends the **change, not the answer**. The server takes a lock on the row and applies `new = max(0, current + delta)`, so if a shelf holds 12 and two people each tap − at the same instant, the result is **10**, never 11. Counts **floor at zero**; a counter cannot be driven negative, and the resulting update can fire an automation so someone is told to reorder. Because a tap is a delta rather than an absolute value, counter adjustments deliberately carry **no "someone else changed this first" conflict check** — deltas compose, so there is nothing to conflict over. Typing an absolute value into the row drawer still gets the normal check. ## Can I record why a count changed? Yes. Beside the stepper in the row drawer there is a **note** field — type a short reason ("used in OR 2") before tapping − or +, and it is saved with that adjustment. Notes are capped at **500 characters**; anything longer is truncated. Read them back in the **row's own History panel**: open the row and expand **History**. The note appears in quotes on the change entry it belongs to, alongside the column name, the old and new values, and who made the change. The table-wide **Activity log** (admins) shows the same note beside the change it belongs to, so you can look for the reason behind a count across the whole table without opening each row. ## Can people use Power Tables from a phone? Yes, for **reading and counting**. The mobile surface at `/m/apps/power-tables` gives table cards and searchable row cards, plus working − / + steppers on any counter column, so a frontline user can find an item and adjust its count from the floor. Everything else stays on desktop: adding rows, editing other fields, importing, exporting, and all configuration. If you need frontline users to *capture* data on a phone, bind a Form to the table — see below. ## Can we scan barcodes into a table? Yes, into **Text** columns. Edit the column and tick **Scan a barcode or QR code into this field**. The row editor then shows a **Scan** button that reads the code with the camera and drops the value straight into the field; typed entry always remains available as a fallback. The row editor is part of the desktop grid — on a phone, open the table's full page ("Open on desktop") to scan into a field. To **find** a row by its label on a phone, tap **Scan a code** under the table's search box: the camera reads the code and searches for it. Six symbologies are supported: **QR**, **Code 128**, **Code 39**, **EAN-13**, **EAN-8**, and **UPC-A**. Scanning uses the browser's built-in barcode detector, so availability depends on the phone's browser — the typed fallback covers devices where it isn't available. --- ## Import and export ## What file types and sizes can I import? Power Tables accepts **CSV**, **XLSX**, and **XLS** files. CSV files can be up to **500 MB** via the direct-upload path. Excel files (XLSX/XLS) are capped at **100 MB** because the parser loads the workbook's shared-strings table into memory. For a multipart upload (the no-JavaScript fallback), the limit is **100 MB** regardless of type. If an Excel file is too large, save it as CSV instead. ## How does the scheduled import work? Each table can have one scheduled import that runs nightly, pulling a CSV or Excel file from a remote source. Two modes: **Replace** clears all existing rows and re-imports (the source is the system of record), and **Append** adds rows on each run (for accumulating logs). Sources can be a public HTTPS URL (no setup), a protected URL via a Data Feed connection configured at /admin/integrations (sends a bearer token, basic auth, or custom header), or a remote file on an SFTP server via an SFTP connection. A **Run now** button triggers it on demand, and the last run's status shows beside it. Both are on the table's **Set up** page, on the **Scheduled import** card. ## Can I export data, and what are the limits? Yes. Export captures the current view's filters, search, sort, and visible columns, and runs as a background task. **CSV export** has no row cap. **Excel export** is capped at **100,000 rows** — fewer on wide tables, since the cap is really 2.5 million cells (a 40-column table stops at 62,500 rows) — because the writer builds the workbook in memory; the Export menu shows the cap for the table you are on. Scheduled exports can push a CSV or XLSX file nightly to an SFTP server — the SFTP connection is required (exports always push to a credentialed destination). Note the asymmetry between the two schedules: a scheduled **import** can pull from a public HTTPS URL, a credentialed HTTPS endpoint, or SFTP. A scheduled **export** is **SFTP only**. ## Can a Form feed a table? Yes, and it is the recommended way to let frontline users capture data — Forms already has a mobile surface, validation, and an audience model. Bind it from the table's **Set up** page: pick a form template and map each form field to a table column. The binding is stored on the **form template**. There are two modes: - **Append** (the default): every submission adds a new row. Ingest is **idempotent** — a form that passes through several completed states (submitted, then approved) still produces exactly one row, and editing the submission afterwards does not rewrite the row it created. - **Update** (stock-take semantics): the binding names a **match column**. The submission's answer for that column finds the existing row, and every other mapped answer is written onto it — "how many are left?" updates the master item instead of appending a log line. Last write wins; the row's History records who and when. In update mode, if nothing matches the value, the binding's **unmatched** setting decides: create a new row (with the match value included, so it is findable next time), or record a visible skip on the submission. If **two or more** rows share the match value, Power Tables stops and records a skip rather than guessing which one to overwrite. A rejected answer never fails the submission itself — it is recorded against the binding, whose health card is on the table's Set up page. One caveat: a column mapped by a binding (or used as its match column) cannot be archived until the binding is edited or removed. ## Is there an API, and what can it do? Yes, under `/api/v1/power-tables`. Five endpoints: | Endpoint | What it does | |---|---| | `GET /power-tables` | List tables | | `GET /power-tables/:id` | One table's structure — columns (with currency units) and views | | `GET /power-tables/:id/rows` | Read rows, using the same filter grammar and keyset pagination as the grid | | `GET /power-tables/:id/aggregate` | Filtered aggregates — count, sum, avg, min, max | | `POST /power-tables/:id/rows` | Create one row, through the same casting, quota, validation, and audit path as the row drawer | **The API can create a row but cannot update or delete one.** There is no `PATCH` and no `DELETE` on rows, and no endpoint that changes configuration — that is deliberate, not an oversight. Row edits and deletes go through the app, the mobile steppers, bulk actions, automations, or a bound Form. Access is by API token with least-privilege scopes: `read:power_tables` for reads, `write:power_tables` for row creation. Row creation additionally requires the token's user to hold Power Tables **contributor** rights or above, exactly like the web row drawer. A **restricted** table is invisible — not forbidden — to a token whose user holds no grant on it. --- ## Saved views and automations ## How do relative date filters work? A filter on a **Date** or **Date & time** column can be a moving window instead of a fixed value. Eight operators are available: **today**, **yesterday**, **this week**, **this month**, **this quarter**, **this year**, **last N days**, and **next N days**. Both ends of the window are recomputed **on the server** every time the filter runs — never stored as dates. So a view saved as "expiring in the next 30 days" keeps meaning exactly that, instead of quietly freezing to the 30 days that followed the day you saved it. Windows are half-open ranges, which is what makes them correct on a Date & time column (a plain "on or before the end date" bound silently drops everything after midnight on the last day). For **last N days** and **next N days**, N is clamped to **1–3,650** (ten years). "Last 7 days" includes today. The same vocabulary is used in four places: grid and saved-view filters, Live Boards period selectors, saved-view alerts ("Alert me"), and the Power Tables AI agent. The agent exposes **seven** of the eight — it has no `next N days`. ## What are personal views versus shared views? **Shared views** belong to the table and are visible to everyone who can see the table. They are the only views that Live Boards can bind to and that automation schedule rules can use as row selectors. **Personal views** belong to one user and are visible only to them. Each user can have up to **25 personal views per table**. The shared-view cap is a configurable quota (default **25** per table, up to **100**). ## What can automations do, and what are the limits? Automation rules fire on row events (row created, updated, field changed, or deleted) or on a schedule bound to a saved view. Available actions include: update fields, notify a user, send an external email, request approval, create a task, send an HTTP request (webhook), mark a row locked or archived (this writes a status value — the row stays editable), delete a row, and three AI actions (fill a column, summary digest, anomaly alert). Limits: up to **25 automation rules per table** (configurable up to 50), up to **10 actions per rule**, up to **50 conditions per rule**, and scheduled rules process a maximum of **10,000 matching rows per run**. Hourly caps apply per business: **500 automation executions**, **100 webhooks**, and **50 external emails** per hour. A rule that fails **5 consecutive runs** pauses itself automatically and notifies the owner. --- ## When something looks wrong ## "I imported a CSV but some rows are missing" Check the import task's error report — it lists every skipped row by number with the reason. Common causes: the row violated a column validation rule (required value missing, number out of min/max range, value not in the dropdown's options), or the table hit its row quota and the remaining rows were skipped. Import stops cleanly at the quota boundary and reports how many rows were skipped. ## "My Live Board shows 'source unavailable'" The board is bound to a saved view on a Power Tables table. Check whether the table was archived (the board loses its source immediately on archive) or the view was deleted. If the table is still active, re-check the view in Power Tables — if it was a personal view, boards can only bind to shared views, and a personal view that was converted or deleted breaks the binding. To repair a board whose table was archived, restore the table here in Power Tables, or open the board's editor in Live Boards, click **Board settings**, and pick a replacement table — every visualization moves with it, columns matched to the new table by name; if any cannot be matched, the change is refused and nothing is altered. ## "The scheduled import failed" Open the table's **Set up** page and check the last run's status on the **Scheduled import** card. Common causes: the source URL returned an error or timed out, the SFTP connection credentials are invalid or the remote file path doesn't exist, the file exceeds the size limit, or the file isn't a supported format (CSV, XLSX, or XLS). For protected HTTPS sources, verify the Data Feed connection at /admin/integrations still has valid credentials. A failing schedule stays **On** and retries every night — it does not pause itself — so fix the source or pause the schedule yourself; failure notices are sent at most once a week while it keeps failing, and the full run history is on **Analytics → Schedule health**. --- ## Licensing and limits ## Does Power Tables require a licence? No. Power Tables is a **pay-as-you-go** app — available to every tenant with no licence decision. It stays off until an admin enables it. Billing is per 1,000 rows stored per year; there is no per-seat charge and no monthly floor. ## Exactly what does Power Tables cost? The meter is **rows stored**, in units of 1,000 rows per year, counted **nightly** across your **active** tables. The price is one flat rate at any volume: **$1.20 per 1,000 rows a year** (about $0.10 a month), drawn from your platform credit balance. Row counts are rounded up to the next 1,000. Three things are explicitly **not** billed here: - **Archived tables.** Archiving a table takes it off the meter immediately. (It also starts the 7-day purge clock — see the retention question.) - **OneMango sample data.** Sample tables are flagged at creation and are excluded regardless of what they are named or how their description is edited. - **Mini App records.** While a Mini App is turned on, a table it owns is off this meter entirely. Its records count under App Builder instead — each app's first 25,000 records are included, and records beyond that bill as app records. If the app is turned off (from its Edit with AI page in App Builder, or the Apps Marketplace), its tables are back in your Power Tables list and on this meter until it is turned on again. The on/off switch on the app's own Settings page does not change this — it only hides the app. There is **no per-seat charge and no monthly floor**, so a small table costs a small amount. ## Do quotas affect my bill? No. They are separate mechanisms, and confusing them leads to the wrong fix. - **Quotas** are capacity guardrails on shared infrastructure — how many tables, rows, columns, indexes, shared views, and automation rules you may have. Raising one costs nothing. - The **billing meter** is rows stored, counted nightly across active tables. Raising the max-rows quota from 1 million to 10 million does not change your bill by a cent; storing 10 million rows does. Likewise, lowering a quota does not reduce what you pay — archiving or deleting rows is what does that. ## How long is data kept? | What | Kept for | |---|---| | Per-field row change history (the row's History panel) | **180 days** by default — a company admin can change it under Admin → Security settings ("Keep record change history for"), between 30 days and 10 years | | Deleted rows (the table's Deleted rows page) | **30 days** | | Automation run log | **90 days** | | Scheduled import/export run log | **90 days** | | Archived table before permanent purge | **7 days**, with a warning notification **24 hours** before | The 7-day archive grace period is the only one of these that ends in permanent data loss, and it is the only one that warns you first: an Inbox notice goes to the table's creator and to admins 24 hours before the purge, and restoring the table at any point in the 7 days cancels it. Imports and bulk inserts are deliberately not written to the per-row change history — the import task record is the audit trail for those. Table rows themselves are kept indefinitely; only the *history of changes to them* ages out at 180 days. ## What can the Power Tables AI agent do, and is it on? It is **off by default** — turn it on with **Enable the Power Tables AI agent in Ask AI** in Settings. It is admin opt-in because the agent both reads every row of every table it can see and carries write tools. The agent has **12 tools**. Seven are read-only: list tables, get one table's structure, count rows, search rows, aggregate rows, list import activity, and compare entities to a target. **Five are writes**: create a table, create a saved view, request a column index, add a row, and update a row. Every write is **confirm-gated** — the agent shows the exact change and waits for you to approve it before anything is written. The three configuration writes are admin-only; the two row writes are available to contributors, matching the web row drawer. The agent honours the same access rules as the app: a restricted table a user holds no grant on is invisible to their questions. ## What are the quotas, and can I change them? Six quotas are admin-configurable in the Power Tables Settings tab: | Quota | Default | Self-serve ceiling | |---|---|---| | Tables per tenant | 5 | 25 | | Rows per table | 1,000,000 | 10,000,000 | | Columns per table | 25 | 100 | | Indexed columns per table | 4 | 7 | | Shared views per table | 25 | 100 | | Automation rules per table | 25 | 50 | Plus one that is **not** configurable: **25 personal views per user per table**. That is a separate pool from the shared-view quota and a per-user fairness limit rather than a tenant capacity choice, so raising "max shared views" does nothing for a user who has hit it — they delete a personal view they no longer use. When a quota is at its ceiling and you need more, contact MangoApps support — they can grant higher limits from the Console without a code change (up to 500 tables and 100,000,000 rows per table). When the limit is below the ceiling, any admin can raise it in Settings. A limit can never be set below what is already in use, and if MangoApps staff have raised a limit for your account the Settings page says so. Raising a quota does not change your bill — see "Do quotas affect my bill?" above. --- ## More help - [Power Tables Overview](/help/articles/power_tables_app_overview) - [Live Boards FAQ](/help/articles/live_boards_app_faq) — for boards bound to your saved views - [App Builder FAQ](/help/articles/app_builder_app_faq) — Mini Apps are created there, not in Power Tables - Ask AI — the assistant answers Power Tables questions from these articles. **Keywords:** faq, power tables, import, export, csv, columns, rows, saved views, quotas, permissions, automation, not showing, access, counter columns, counting, stock take, barcode, mobile, relative dates, retention, pricing, api, agent, power-tables, power_tables --- # Practice Hub App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run Practice Hub — AI roleplay scenarios where employees rehearse conversations and presentations, scored against a rubric you define. # Practice Hub ## 1. What it is Practice Hub lets employees rehearse real conversations and presentations against an AI that plays the other person — a frustrated customer, a job candidate, an audience — then scores the attempt against a rubric you define. Every practice ends in a scorecard: the learner's own words quoted and judged, with delivery signals like pace and filler words when voice is used. Scenarios are peer-authored by default. Employees draft them; L&D curates and promotes the best; and only a promoted **Official** scenario can mint a real Skills & Credentials credential. - **Enablement:** Practice Hub requires a licence and is off by default. An admin enables it per tenant from Admin → Apps → All Apps. - **What it is not:** Practice Hub is not a course builder — it is the rehearsal step between learning something in Training and doing it for real. Course creation and completion tracking live in Training. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps → Practice Hub** and enable the app. 2. Open **Practice Hub → Settings** and review the defaults. The app works immediately with its defaults — the items below are the ones worth deciding up front. 3. Decide whether employees may publish scenarios to the shared library. **Allow employees to publish scenarios to the Practice Library** is on by default. When on, peer submissions go through an AI content check and (by default) L&D approval before they reach the library. 4. If you want managers to review and adjust AI-generated scores, confirm **Let managers review and override scorecards** is on (it is by default). 5. Grant access. Practice Hub respects platform Access Management — target it to departments, locations, or specific people via groups. Any user with access can browse the library and practice; managers see the Assignments and Reviews tabs for their direct reports; admins see Curation, Analytics, and Settings. 6. Create your first scenario. Go to **Practice Library → New scenario** (or use **Describe it, AI drafts it** to generate one from a prompt). Add at least one persona and two scoring criteria, then publish. 7. Confirm it worked: employees should see Practice Hub in their app list, the scenario in the Practice Library, and a **Start practice** button on it. A scenario with no persona cannot be practiced — the **Start practice** button is disabled until at least one persona is added. To get started quickly, the Settings page offers **Load sample scenarios** (pre-built examples) and the **Working with AI** collection — five official scenarios covering delegation, evidence checking, exception handling, escalation, and responsible approval. Both are optional. ## 3. How it fits together **Scenarios and the trust ladder.** A scenario is the authored unit: a situation ("an angry customer calls about a late delivery"), one or more AI personas to roleplay against, and a rubric of scoring criteria. Every scenario has a visibility tier that determines how much trust the platform places in it: - **Community** — the starting tier for peer-authored scenarios. Visible in the library once published. - **Curated** — L&D has reviewed and promoted it. Admin-authored scenarios start here automatically. - **Official** — the highest tier. Only an Official scenario can be marked **Certifiable**, which means a passing attempt mints a real credential in Skills & Credentials. Example: an employee drafts a "Handling a product recall call" scenario → it lands as a Community draft → they publish it → the AI content check runs → L&D approves it into the library as Community → after it proves popular (good ratings, high pass rate), L&D promotes it to Curated → eventually to Official + Certifiable, linked to the "Crisis Communication" skill. **Attempts and scoring.** When a learner starts a scenario, the app creates an attempt — the record of one practice session. The learner converses with the AI persona (by typing or by voice), then ends the session — or discards an unfinished run, which is never scored. The AI scores the attempt against every rubric criterion and produces a scorecard with an overall score. The default passing threshold is 70 (configurable per scenario, 0–100). A scored attempt is private to the learner; managers see it only through the Reviews queue, and only for their own reporting line. **Interaction modes: conversation vs delivery.** Each scenario is set to one of two modes. In **Conversation** mode (the default), the learner has a back-and-forth with a counterpart — a customer, a colleague, a candidate. In **Delivery** mode, the learner holds the floor (a presentation, a pitch, a speech) and the AI persona acts as an audience — reacting, asking questions, but never taking a counterpart role. Separately, a scenario's **modality** controls whether the learner practices by typing, by voice, or by their own choice. Modality is a content decision made by the author. Typed replies, and spoken replies the AI answers aloud, always work; the tenant-level **Live voice roleplay** setting adds real-time speech-to-speech conversation. **Assignments and campaigns.** A manager can assign a specific scenario to one or more people with an optional due date. An assignment moves through four states: **Assigned → Started → Passed → Canceled**. A campaign wraps an assignment around an audience (a department or group) with optional recurrence — "everyone on the support team passes this scenario every 90 days." Recurring campaigns regenerate assignments automatically at the interval. **Score appeals.** A learner who disagrees with their score can raise a score appeal from their scorecard. The appeal goes to their manager's **Score appeals** queue (visible alongside the Reviews tab) — or, when nobody above them can review, to the Practice Hub admins. The learner can withdraw an open appeal from the scorecard. The manager can uphold the score, adjust it, or confirm the transcript was wrong (the transcript itself is not edited) — always with a note the learner reads. Score appeals require manager review to be turned on — if the setting is off, there is no reviewer to route to. **Drills.** After a scored practice, if the learner underperformed on a specific rubric criterion, the scorecard offers a focused drill — a short, private practice targeting just that weakness. Drills are auto-generated clones of the original scenario, tagged as private, and excluded from the Practice Library and all admin surfaces. **Recording analysis (opt-in).** When **Let employees upload call/meeting recordings for private AI analysis** is turned on, employees can upload a real call or meeting recording. The app transcribes it and scores it against a chosen scenario's rubric — the same scorecard as live practice. Recording analyses are private to the uploader and excluded from the manager review queue. **Skills & Credentials integration.** When an Official + Certifiable scenario is linked to a certification skill, a passing typed attempt automatically mints an employee skill record and a certification (live-voice attempts, course previews and recording analyses are scored but never certify). If the scenario has a recertification interval, the credential carries that expiry. A manager who overrides a score downward can withdraw the credential automatically. **The AI coach.** Each learner has a coach profile that the AI builds over time from scored practice. The coach tracks strengths, focus areas, and a narrative of the learner's development. It uses this profile to personalise scenario recommendations on the dashboard and in the Practice Library, and to offer a weekly practice plan (when the digest setting is on). Learners can see what the coach knows about them, set a personal practice goal, and remove any item from the coach's memory. If **Personalize AI coaching with workplace signals** is on, the coach also draws on performance review themes, recognitions, and skills data. **Mobile.** Employees on phones are automatically redirected to the mobile Practice Hub. The mobile experience covers the library, scenario details, and the full roleplay and scorecard flow. Manager and admin surfaces (Assignments, Reviews, Curation, Analytics, Settings) are desktop-only. ## 4. Running it ### Curating peer submissions 1. Go to **Curation**. The top section shows scenarios submitted by employees, oldest first. 2. For each submission, review the scenario content and the AI content check result (advisory — your decision overrides it). 3. Choose **Approve** (publishes it to the library) or **Return to author** with a note (sends it back as a private draft with your feedback delivered to their Inbox). ### Promoting scenarios 1. In **Curation**, the lower section lists published Community and Curated scenarios sorted by rating and usage. 2. Select one or more scenarios and choose a target tier: **Curated** or **Official**. 3. For Official scenarios, optionally check **Certifiable** and link at least one certification skill. A certifiable scenario with no linked certification skill cannot be saved. ### Reviewing scorecards 1. Go to **Reviews**. The **Pending** tab shows scored attempts by your direct reports (or, for admins, the whole company) that have not been reviewed. 2. Open an attempt to read the full transcript and scorecard. 3. Choose **Accept** (endorses the AI score) or adjust the score to a number 0–100. The learner is notified of adjustments. A review that changes a passing result to failing automatically withdraws any Training completion or certification that attempt had earned, scoped to what that specific attempt produced. ### Assigning practice 1. On any scenario, click **Assign**. Pick one or more people (or a department), set an optional due date, and add an optional note. 2. Assignees receive an Inbox notification. The assignment appears on their dashboard. 3. Track progress on the **Assignments** board. Managers see assignments for their direct reports; admins see all. By default, managers can only assign practice to their own reporting sub-tree. The setting **Let any manager assign practice across the whole company** widens this to all employees. ### Running a campaign 1. Go to **Campaigns → New campaign**. Pick a scenario, an audience, a due date, and optionally a recurrence interval. 2. The campaign fans out individual assignments to every member of the audience. 3. For recurring campaigns, the next round of assignments is generated automatically at the recurrence interval. ### Viewing analytics Go to **Analytics** (admin only). The dashboard shows headline counters (total scenarios, published, official, total attempts, scored, passed, active practitioners), the most-practiced scenarios, and category and difficulty breakdowns. Additional panels cover assignment adoption rates, competency gaps across the team, practice by department, shelf health (active vs stale scenarios), and AI usage. An **Export CSV** button downloads up to 10,000 attempt records. ### Handling score appeals When a learner raises a score appeal, it appears in the **Score appeals** tab (visible to managers alongside Reviews). Open each appeal, read the learner's statement and the disputed evidence, then resolve it — uphold the original score, adjust it, or confirm the transcript was wrong — and write the note the learner will read. ## 5. Settings All settings are at **Practice Hub → Settings**. Defaults are read from the app's configuration schema and apply until an admin changes them. | Setting | Default | What it changes | |---|---|---| | **Practice Hub AI Agent** | On | Whether the in-app AI assistant can answer questions about Practice Hub. | | **Allow employees to publish scenarios to the Practice Library** | On | Whether employees can submit scenarios to the shared library. Drafting for private practice is always allowed. | | **Peer scenarios need L&D approval before going live** | On | When on, a peer submission goes to the Curation queue for admin approval. When off, it goes live automatically after the AI content check passes. | | **Let managers review and override scorecards** | On | Whether the Reviews queue and Score appeals tabs appear for managers. | | **Let any manager assign practice across the whole company** | Off | When off, managers assign only to their direct reports and their sub-tree. When on, any manager can assign to anyone. | | **Award Recognition points when a peer scenario is promoted** | Off | Whether a promotion to Curated or Official grants Recognition points to the scenario author. | | **Suggest new scenarios weekly from real hard moments** | Off | When on, the AI drafts scenario suggestions weekly based on real support escalations and on Training quiz questions learners keep failing. L&D approves them before they enter the library. | | **Let employees upload call/meeting recordings for private AI analysis** | Off | Enables the upload flow (and sharing an analysis with a manager). Turning it off stops new analyses; people keep reading and deleting the ones they already made. Carries consent and privacy weight — two-party-consent laws may apply. | | **Days to keep uploaded recording files before auto-delete** | 30 | How long raw recording files are retained. Transcripts and scorecards stay until the employee deletes the analysis. | | **Personalize AI coaching with workplace signals** | On | Whether the AI coach uses performance review themes, recognitions, and skills data to personalize feedback and scenario recommendations. | | **Send active practitioners a weekly practice plan** | Off | Whether active practitioners receive a Monday Inbox digest with a personalised practice plan. | | **Live voice roleplay** | Off | Enables speech-to-speech practice using voice minutes from the tenant's balance. Each live session is capped at 10 minutes. | Below the toggles, the **Company context** section lets you describe your products, common objections, policies, and tone guidelines. The AI personas and scoring coach ground in this context when it is filled in. ## 6. More help - **Practice Hub FAQ** — specific setup and operating questions, limits, and troubleshooting. - Ask AI — the assistant answers questions about Practice Hub from these articles. **Keywords:** practice hub, roleplay, scenario, AI practice, score, rubric, rehearse, coaching, conversation practice, presentation practice, live voice, recording analysis, assignment, campaign, curation, certifiable, practice-hub, practice_hub --- # Practice Hub FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Practice Hub — for the admin running it. # Practice Hub FAQ Answers to common setup and operating questions about Practice Hub. For what the app is and how to set it up from scratch, see the [Practice Hub Overview](/help/articles/practice_hub_app_overview). --- ## Setup ## What do I need to configure before employees can start practicing? Enable the app and grant licences from Admin → Apps → All Apps. Employees can practice right away using any published scenario. To fill the library quickly, load the sample data from Settings — it installs several ready-to-use scenarios across categories. Optionally fill in the Company Context (products, objections, policies, tone) so that AI personas and scoring draw on your company's reality instead of generic placeholders. ## Who can create practice scenarios, and who can publish them? Any employee can draft a scenario — drafts are private to the author. Publishing to the shared Practice Library requires either an admin (or app admin), or the **Allow employees to publish scenarios to the Practice Library** setting to be on (it is on by default). When peer publishing is on, the **Peer scenarios need L&D approval before going live** setting controls whether a peer's submission goes live after the AI content check or waits in the Curation queue for admin approval. That approval gate is also on by default. --- ## Permissions and access ## What can each role do in Practice Hub? Three levels govern access: 1. **Any employee** — browse the library, take scenarios, view their own scorecards and coach profile, draft scenarios, upload recordings (when enabled), and challenge a score. 2. **Manager** (or app admin) — everything above, plus assign practice, run campaigns, review and override scorecards, and resolve score challenges. By default a manager can only assign and review their own direct and indirect reports. Turn on **Let any manager assign practice across the whole company** to extend that reach. 3. **Admin** (or app admin) — everything above, plus curate peer scenarios (approve, return, promote), view analytics, export data, and change settings. ## Why can't a particular group of employees see the Practice Library? Check three things: the app is enabled and licenced for your tenant, the employees have an active account in the business, and the scenario is in **Published** status. Draft and archived scenarios are visible only to their author and admins. If a peer scenario is stuck in **In review**, it is either awaiting the AI content check or sitting in your Curation queue. --- ## Day-to-day ## How does a scenario go from a peer's draft to an official, certifiable scenario? The lifecycle has two axes — status and visibility: 1. An author creates a **draft** (status). It is private. 2. The author publishes. If approval is required, it moves to **In review** and the AI content check runs. If the check passes, it lands in the Curation queue for admin approval. If approval is not required, a passing check publishes it automatically. 3. A published peer scenario starts at **Community** visibility. An admin can promote it to **Curated**, then to **Official**. Only an **Official** scenario can be marked certifiable. 4. A certifiable scenario must also be linked to at least one skill that requires certification in Skills & Credentials. ## How is a practice attempt scored? The AI runs three independent evaluations at temperature 0 and takes the median score per rubric criterion — this resists outliers. Each criterion is weighted, and the overall score is the weighted average. The scorecard quotes the learner's own lines as evidence under each criterion. Delivery metrics — filler-word count, pace (words per minute), and talk-to-listen ratio — are computed from voice turns when the learner speaks. The pass threshold is set per scenario (default **70** out of 100). Coaching feedback is generated separately, after the score is final, so it cannot bias the grade. ## Can a manager override an AI scorecard? Yes, when the **Let managers review and override scorecards** setting is on (the default). A manager can accept the score or set an adjusted overall score. If a manager overturns a pass to a fail, any credential and Training completion that the original pass minted are automatically revoked. ## What happens when someone passes an official, certifiable scenario? A pass on a scenario that is **Official**, **Certifiable**, and linked to a certification-required skill writes a real credential in Skills & Credentials at demonstration-level proficiency, plus a completion record in Training. If the scenario has a recertification interval, the credential carries a matching expiry date. Only live roleplay attempts qualify — recording uploads and browser-relayed live-voice transcripts do not count toward certification. ## How do assignments and campaigns work? An assignment ties one employee to one scenario with an optional due date and note. You can assign up to 500 employees at a time. A campaign wraps an assignment around an audience (a department, location, or custom group) with optional recurring cadence — up to 10 years. When the cadence fires, it re-assigns members whose previous pass is older than the interval. Audiences of 25 or fewer are assigned immediately; larger audiences are processed in the background. --- ## When something looks wrong ## I can't see my scorecard yet — how long does scoring take? Scoring runs in a background job: transcription, speaker labelling, then three scoring passes. Most attempts finish within a minute or two. If the scorecard still shows **Processing**, the job may have been delayed by a queue backlog. Check the Background Tasks page for stuck jobs. A status of **Failed** means the AI could not score the attempt — the learner can retry the scenario. ## My score seems wrong — can I challenge it? Yes. On any scored attempt, the learner can raise a score challenge, selecting whether the dispute is about the transcript, the score, a rubric criterion, or something else. The challenge goes to the learner's manager (or any reviewer with access). The reviewer can let the original result stand, adjust the score, or confirm the transcript was wrong — always with a note the learner reads. Manager review must be enabled for challenges to work. ## I uploaded a recording but it disappeared — where did it go? The raw recording file is automatically deleted after the retention window. The default is **30 days**; your admin can set it to anywhere from 1 to 365 days in Settings. The transcript, scorecard, and coaching note are kept until you delete the analysis yourself (Delete analysis on its page) — only the original audio or video file is purged automatically. ## Why didn't my practice session count toward certification? Four conditions must all be true: the scenario is **Official** visibility, the scenario is marked **Certifiable**, the scenario is linked to a skill that requires certification, and the attempt was a live AI roleplay (not a recording upload and not a browser-relayed live-voice transcript). If any of these is missing, the pass is recorded normally but no credential is minted. ## An employee says they stopped getting assignment reminders — what happened? Practice Hub suppresses reminder notifications for employees who are currently on approved leave or who are rostered but not on shift. The initial assignment notification always goes through regardless of duty status. Once the employee returns to active duty, the next daily reminder sweep picks them up again. The sweep itself reminds from two days before an assignment's due date until 30 days after it — an assignment with no due date, or one more than 30 days overdue, or on a scenario that has been archived, gets no automatic reminder (a manager can still nudge an open assignment from **Assignments** — one with no due date, or one past the 30 days). Assignments and their reminders also have their own **Practice assignments** row in each person's notification settings — if they turned its email or push off, that channel stays silent until they turn it back on. ## An employee's certification was revoked after a manager review — why? When a manager overrides a passing score to a fail, Practice Hub automatically revokes the credential and Training completion that the original pass created. It checks whether the employee has another passing attempt for the same scenario first — if they do, the credential stays. The revocation only affects records that the overturned attempt itself wrote. --- ## Recordings and voice ## Does live voice roleplay cost anything, and how do I turn it on? Live speech-to-speech roleplay is **off** by default. Enable it with the **Live voice roleplay** toggle in Settings. Each live session uses voice minutes from your tenant's balance. A single session is capped at **10 minutes**, and each employee is capped at **60 minutes per day**. Everyday practice — typing a reply, or speaking a reply and hearing the AI answer back — does not require live mode and does not spend voice minutes. ## Can employees practice in languages other than English? Yes. Practice Hub supports 15 languages: English, Spanish, French, German, Portuguese, Italian, Dutch, Polish, Hindi, Chinese, Japanese, Korean, Arabic, Tagalog, and Vietnamese. The AI persona and coaching feedback respond in the learner's chosen language. --- ## Licensing and limits ## Does Practice Hub require a licence? Yes. Practice Hub requires a licence and is disabled by default. An admin enables it from Admin → Apps → All Apps and grants licences to the tenant. ## What are the limits I should know about? | What | Limit | |---|---| | Recording upload size | 500 MB (audio or video) | | Recording retention | 1–365 days (default 30) | | Pass threshold range | 0–100 (default 70) | | Estimated scenario duration | 1–1,440 minutes | | Recertification interval | 1–3,650 days (or never) | | Live voice session cap | 10 minutes per session | | Live voice daily cap | 60 minutes per employee | | Single assignment batch | 500 employees | | Bulk assignment update | 200 at a time | | Campaign recurrence | Up to 3,650 days (~10 years) | | Analytics CSV export | 10,000 rows | | Company Context fields | 4,000 characters each | | Coach profile items | 6 focus areas + 6 strengths | | Rubric criterion weight | Per-criterion; overall score is weighted average | | Scoring samples | 3 independent evaluations (median) | --- ## More help - [Practice Hub Overview](/help/articles/practice_hub_app_overview) - Ask AI — the assistant answers Practice Hub questions from these articles. **Keywords:** faq, practice hub, roleplay, scenario, scoring, scorecard, rubric, certification, assignment, campaign, voice practice, recording upload, curation, coach memory, delivery mode, practice-hub, practice_hub --- # Procurement App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run Procurement — requisitions, purchase orders, budgets, supply ordering, invoicing, and vendor integrations. # Procurement ## 1. What it is Procurement manages the full purchasing cycle: employees submit purchase requisitions, approvers review them through configurable multi-level workflows, approved requisitions convert into purchase orders sent to vendors, and finance records invoices and payments against those orders. - **Enablement:** Procurement requires a license. An admin enables it from Admin → Apps → All Apps. - **What it is not:** Procurement does not manage vendor profiles or scorecards — that is Supplier Hub (the vendor management app). Procurement references the same vendor records but does not own them. ## 2. Standing it up 1. Turn Procurement on for your organisation in the Apps Marketplace, then open **Procurement → Setup → Settings** to review the defaults below. 2. Optionally create **approval workflows** at **Setup → Approval Workflows**. Without one, a submitted requisition at or above **Manager Approval Required At** (default 500 in your default currency) waits for the requester's manager or a Procurement admin, and one below it is approved on submission. Mark one workflow as the default so every requisition that doesn't match a conditional workflow still routes through it. 3. Under **Settings → Permissions**, check which roles can create requisitions (all four roles are allowed by default) and which roles can approve purchase orders (Admin and Super Admin by default). 4. If you plan to use budgets, create them at **Finance → Budgets** with a cost center and date range (**Show Budget Summary Cards** in Settings, on by default, puts their totals on the dashboard). A requisition is charged to the budget in its **Charge to** field, which starts on its cost center's own budget, and reserves and commits against it automatically. 5. For supply ordering (the employee self-service catalog), confirm **Enable Supply Ordering** is on in Settings. Add inventory items at **Warehouse → Inventory** so warehouse stock appears in the catalog, or configure vendor integrations at **Setup → Vendor Integrations** to include vendor catalog items. 6. Verify the setup by having a test user create a requisition. It should appear in the approver's **Pending My Approval** queue and, once approved, be convertible to a purchase order. ## 3. How it fits together ### Requisitions vs purchase orders A **requisition** is a request to buy something. A **purchase order** (PO) is the commitment to a vendor. Requisitions are internal; purchase orders are external. One requisition can produce multiple purchase orders when supply-order items come from different vendors. Requisitions move through these statuses: **Draft → Pending Approval → Approved → Converted to PO** (for standard requisitions) or **Approved → Partly fulfilled → Fulfilled** (for supply orders — Fulfilled once the warehouse items are issued and every vendor item has arrived). A requisition can also be **Rejected** or **Cancelled** at any point before a PO progresses past Draft. Purchase orders move through: **Draft → Pending Approval → Approved → Issued to Vendor → Received → Closed**. A PO can only be closed once it is both fully received and fully paid. **Worked example:** A manager submits a requisition (PR-00012) for 50 boxes of gloves at $8 each, totalling $400. The approval workflow routes it first to the department head, then to a budget owner. Both approve. The requisition status becomes Approved. An admin converts it to PO-00003, assigns the vendor, and issues the PO. When the shipment arrives, the admin marks it received, logs the vendor's invoice (INV-00005), records a payment, and closes the PO. ### Standard requisitions vs supply orders **Standard requisitions** are created by navigating to **Requisitions → New Requisition** and filling in line items manually. The requester picks a vendor, enters item details, and submits. An admin later converts the approved requisition into a PO. **Supply orders** are created through the **Order Supplies** catalog. Employees browse warehouse inventory and vendor catalog items, add them to a cart, and submit. The system creates a requisition automatically with the source type set to supply order. When a supply order is approved, purchase orders for vendor-sourced items are generated automatically — one PO per vendor. Warehouse-sourced items go to the **Fulfillment Queue** instead, where warehouse staff pick, pack, and ship them. An order with both kinds reads **Partly fulfilled** until its vendor purchase orders are received; a vendor item whose purchase order is rejected is named as not ordered when the order completes. ### Budgets and reservations A budget ties a dollar amount to a cost center and date range. When an employee submits a requisition charged to a budget (its **Charge to** field, which starts on the cost center's own budget), the system **reserves** that amount. When the requisition is approved, the reservation is **committed**. When it is rejected or cancelled, the reservation is **released**. This prevents over-commitment before money is actually spent. If a budget has **Enforce hard stop** turned on, a requisition that would exceed the available balance cannot be submitted at all — the employee sees a message naming the budget and its remaining amount. Budgets fire alerts at three configurable thresholds (default 75%, 90%, and 100% utilization). The budget owner receives a notification each time a threshold is crossed. Alerts are de-duplicated within a 24-hour window. ### Approval workflows An approval workflow defines who must approve a requisition and in what order. Each workflow has one or more **levels**, and each level specifies an approver type: a role (e.g. Manager), specific named users, the budget owner, the department head, the requester's direct manager, or members of a department or location. Workflows can be **conditional** — triggered only when the requisition amount falls within a range, belongs to certain departments, involves certain item categories, or is flagged as an asset purchase. When several conditional workflows match, the one with the highest minimum amount is used first (so an amount escalation is never skipped), then the one with the most department, category and asset-purchase rules, then the narrowest amount range. If no conditional workflow matches, the **default** workflow is used. Each business can have one default workflow. An approver who will be unavailable can set up an **approval delegation** — a date-bounded handoff to another user. Delegations can be scoped by amount, department, or category. ### Stations Stations are an opt-in feature for organisations that route supplies to fixed delivery points (e.g. ambulance stations, plant locations). Each station has a unique station number, a name, and exactly one cost center. When stations are enabled, the supply-order form shows a station picker instead of a freeform delivery location, and the cost center is derived automatically. Inventory items can carry per-station ordering limits (maximum per order, maximum per period) so a single station cannot over-order. ### Three-way matching When an invoice is linked to a purchase order and approved, the system performs **three-way matching**: it compares the invoice total against the PO total and computes a variance percentage. If the variance is within the tolerance (default 5%), the invoice is marked **Matched**. If not, it is flagged as a **Discrepancy** for review. ## 4. Running it ### Reviewing and approving requisitions 1. Go to **Requisitions → Pending My Approval**. 2. Open a requisition to review the line items, total, vendor, and budget status. 3. Click **Approve** to advance the requisition to the next approval level (or to Approved if this is the final level). Click **Reject** and provide a reason to return it to the requester. Admins can approve any in-progress requisition even if they are not a designated approver at the current level. ### Converting a requisition to a purchase order 1. Open an approved standard requisition. 2. Click **Convert to PO**. The system creates a draft purchase order with the same line items and vendor. 3. Review the PO, then submit it for approval. Once approved, issue it to the vendor. For supply orders, vendor POs are generated automatically on approval — no manual conversion step. ### Receiving goods and recording invoices 1. Open an issued PO and click **Mark Received**. For POs linked to inventory items, stock quantities are incremented and a transaction is recorded automatically. Partial receipts are supported — the PO stays in Issued status until every line is fully received. 2. Go to **Finance → Invoices** and create a new invoice. Link it to the PO. Submit for approval. 3. Once the invoice is approved, go to **Finance → Payments** to record the payment (Check, Wire transfer, ACH, Credit card, or Other). When the payment clears, the invoice and PO payment statuses update automatically. ### Running reports Go to **Insights** (admin only) for: - **Spend Intelligence** — AI-generated insights on spending patterns. - **Analytics** — spend by vendor, department, and month; budget utilization; approval funnel and average approval time. - **Chargeback Report** — spend broken down by cost center and delivery location, with CSV export. Supports quarterly and custom date ranges. - **Inventory Summary** — stock levels, values by category, and low-stock items, with CSV export. - **Order History** — supply order activity over a configurable period, with CSV export. - **Shipped Equipment** — serial number history showing which physical unit shipped where, with CSV export. ## 5. Settings All settings are at **Procurement → Setup → Settings**. | Setting | Default | What it changes | |---|---|---| | Enable Procurement Agent | On | Lets users work with Procurement through Ask AI | | Auto-approve purchase requests | Off | When on — and the Automation Hub master switch in AI Operations is on too — the Procurement agent's automatic actions approve submitted requests at or below its own ceiling that no approval workflow owns | | Agent Auto-approval Ceiling | 500 | The most the agent may auto-approve (default currency) | | Only auto-approve approved vendors | Off | When on, a request naming a vendor that is not active on your vendor book is never auto-approved; requests with no vendor are unaffected | | Remind approvers about stalled requests | Off | When on — and the Automation Hub master switch is on — the agent reminds approvers on a workflow-routed request after **Remind After (hours)** (default 24) | | Require Manager Approval for Requisitions | On | When off, submitting a requisition approves it unless an approval workflow owns it | | Manager Approval Required At | 500 | Requisitions at or above this amount need a manager's approval; below it they skip that step | | Require 3 Quotes Above | 5000 | Purchases above this amount require three vendor quotes | | Require a separate approver | Off | When on, nobody can approve a requisition, supply order, purchase order, invoice or invoice variance they raised themselves | | Auto-create PO from Approved Requisition | Off | When on, an approved requisition automatically generates a draft PO | | Three-Way Match Variance Tolerance Ceiling (%) | 5 | How far an invoice may differ from its PO and receipt before it needs a variance approval | | PR Number Prefix | PR | Prefix for requisition numbers (e.g. PR-00001) | | PO Number Prefix | PO | Prefix for purchase order numbers (e.g. PO-00001) | | Default Currency | USD | Currency used on new requisitions, POs, and budgets | | Roles Allowed to Create Requisitions | Member, Manager, Admin, Super Admin | Which roles see the New Requisition button | | Roles Allowed to Approve Purchase Orders | Admin, Super Admin | Which roles can create, edit, approve, and issue POs | | Roles Allowed to Approve Invoices and Release Payments | Manager, Admin, Super Admin | Who works accounts payable | | Roles That Can Work the Fulfillment Queue / View Inventory / Issue and Move Stock | None beyond admins | Warehouse access by role | | Show Budget Summary Cards | On | Shows budget totals on the Procurement dashboard | | Notify on budget thresholds | On | Notifies budget owners when a budget crosses an alert threshold | | Send weekly spend alerts | Off | Every Monday, tells Procurement admins about possible duplicate invoices, fast-rising spend and budgets that are nearly used up | | Enable Supply Ordering | On | Shows the Order Supplies catalog | | Enable Barcode Scanning | Off | Adds the warehouse Scan page and printable item and bin label sheets | | Eligibility User Attribute | Not set — falls back to the practice level user field | Which user field is matched against inventory item eligibility tags to control catalog visibility | | Delivery Locations | Not set | Pre-defined delivery locations shown in the supply order form | | Units of Measure | each, box, case, pair, roll, pack, set, kit | Available units when creating inventory items | | Inventory Costing Method | Manual | How an item's unit cost is maintained when a purchase order is received | | Enable Low Stock Alerts | On | Fires an alert when an inventory item's stock crosses below its reorder point | | Auto-create a draft PO when an item reaches its reorder point | Off | When on, a low-stock alert also drafts one purchase order per vendor; nothing is submitted or sent | | Enable Email Notifications (Master Toggle) | On | Master switch for all procurement email notifications (in-app notifications are not affected) | | Approval Pending (email) | On | Emails an approver when a requisition is waiting on them | | Approval Progress (email) | Off | Emails the requester as each approval level signs | | All Approvals Complete (email) | On | Emails the requester when every approval level is complete | | Purchase Order Emails | On | Sends email on PO approval and issuance events | | Invoice Emails | On | Sends email when an invoice is approved or not approved | ## 6. More help - **Procurement FAQ** — specific setup, operating, and troubleshooting questions. - Ask AI — the assistant answers questions about Procurement from these articles. **Keywords:** procurement, purchase requisition, purchase order, PO, budget, supply order, vendor, invoice, approval workflow, inventory, fulfillment, spend tracking --- # Procurement FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-14 Answers to common setup and operating questions about Procurement — for the admin running it. # Procurement FAQ Answers to common setup and operating questions about Procurement. For what the app is and how to set it up from scratch, see the [Procurement Overview](/help/articles/procurement_app_overview). --- ## Setup ## Do I need to create an approval workflow before anyone can submit a requisition? No. Requisitions can be submitted without any workflows configured. If no workflow matches a requisition and no default workflow exists, the requisition skips multi-level approval. Whether it still requires manager sign-off depends on the **Require Manager Approval for Requisitions** toggle and **Manager Approval Required At** in Settings. They are on and 500 (in your default currency) by default, so requisitions under 500 are approved on submission and those at or above 500 route to a manager. ## Which roles can create requisitions, and where do I change that? By default every role can create requisitions: Member, Manager, Admin, and Super Admin. To restrict it, go to **Settings → Permissions → Roles Allowed to Create Requisitions** and uncheck the roles you want to exclude. Anyone whose role is unchecked sees an error when they try to create a requisition. ## What needs to be set up before supply ordering works? Supply ordering is on by default. For employees to order from the catalog, you need at least one inventory item with quantity on hand. If your tenant uses Stations, create the stations first — they link each cost center to a delivery location so those fields are set automatically on every order. If you want to pull items from an external vendor catalog, set up a vendor integration (Staples, Grainger, or a manual CSV provider) under **Setup → Vendor Integrations**. --- ## Permissions and access ## Who can see a requisition besides the person who submitted it? Admins and Procurement app admins see all requisitions. A manager sees requisitions from their direct reports and their own. An approver assigned to a requisition can view it. A member sees only their own requisitions. The same scoping applies to the requisition list and CSV exports. ## Who can manage purchase orders? By default only Admin and Super Admin roles can create, edit, approve, and issue purchase orders. To change that, update **Settings → Permissions → Roles Allowed to Approve Purchase Orders**. Procurement app admins can always manage purchase orders regardless of the role list. ## Who can access the fulfillment queue? Admins, Procurement app admins, and any roles your admin adds under **Settings → Permissions → Roles Allowed to Work the Warehouse**. The same roles can also use Scan and the label printers and receive deliveries on purchase orders. The Inventory page under Warehouse has its own lists: **Roles Allowed to View Inventory** and **Roles Allowed to Issue & Move Stock**. --- ## Day-to-day ## How does the approval flow actually work once a requisition is submitted? When a requisition is submitted, the system uses the first matching active workflow in this order: the highest minimum amount first (so an amount escalation is never skipped), then the one with the most department, category and asset-purchase rules, then the narrowest amount range. If no specific workflow matches, the default workflow is used. Each workflow has ordered approval levels. A level can require approvers by role, by specific users, by budget owner, department head, or the requester's manager. Each level can require all approvers or a minimum number, and can escalate to a backup approver. The requisition advances level by level until all levels are satisfied, then it is marked approved. A rejection at any level rejects the entire requisition. ## Can an admin approve a requisition even if they are not a designated approver? Yes, if they hold the Admin or Super Admin role: they can approve a requisition that is pending approval even when they are not a designated approver on the current level. A Procurement app admin can approve a requisition that no approval workflow owns; once a workflow owns it, only the approvers that workflow names for the current level (or an Admin) can sign it. ## What happens when someone delegates their approval authority? The delegator picks a delegate, a date range, and optionally scopes the delegation to a maximum dollar amount, specific departments, or item categories. During that date range the delegate receives and can act on approvals that would go to the delegator. Delegations cannot overlap for the same delegator, and you cannot delegate to yourself. They auto-deactivate when the end date passes. ## What does "Auto-create PO from Approved Requisition" do? When this setting is on, approving a standard requisition (not a supply order) automatically creates a draft purchase order with the same line items and vendor. The requisition status changes to **Converted to PO** and you can find the new PO from the requisition detail page. --- ## When something looks wrong ## My requisition was submitted but nobody got an approval notification Approvers get an in-app notification whatever the email settings say; for the email, check three things. First, the **Enable Email Notifications** master toggle in Settings must be on. Second, **Approval Pending** must be ticked under that master toggle. Third, the requisition amount must be at or above **Manager Approval Required At** (default 500). Requisitions below it are approved on submission without routing to anyone, unless an approval workflow owns them. ## I submitted a requisition and it was immediately approved — why? Either its total was below **Manager Approval Required At** (default 500, in **Settings → Approval Workflow**) or **Require Manager Approval for Requisitions** is off, so submitting it approved it; or the Procurement agent's automatic actions approved it under **Auto-approve purchase requests** (which runs only while the Automation Hub master switch is on, and only at or below the **Agent Auto-approval Ceiling**), in which case the requester's notification says it was approved automatically and why. Lower the threshold (or turn the agent's auto-approval off) to route more requisitions to a manager. ## I'm trying to submit a requisition but it's blocked with a budget error The budget the request is charged to (its **Charge to** budget, or its cost center's budget when none is picked) has **hard stop** enabled, and the requisition amount exceeds what that budget has available. The error message names the budget and shows how much is available. Either reduce the order, increase the budget allocation, or turn off the hard-stop flag on that budget. ## Why does my invoice show "Discrepancy Found" after I approved it? When an invoice is linked to a purchase order, the system runs a three-way match comparing the invoice total against the PO total and receipt status. If the variance exceeds the tolerance (default 5%) or the PO has not been received, the match status is set to **Discrepancy Found**. You can approve the variance from the invoice match detail, or reject it. ## I can't find the fulfillment queue — where is it? The **Warehouse** tab (which contains the fulfillment queue) appears only for admins, Procurement app admins, and users whose role is in **Roles Allowed to Work the Warehouse** or one of the inventory role lists. If you don't see it, ask your admin to add your role. ## An employee says they can't order a supply item — it doesn't appear in their catalog Two things can hide an item. First, if the item has eligibility tags set, the employee's matching user attribute (configured in **Settings → Eligibility User Attribute**, which defaults to practice level) must include one of those tags. Second, if the employee is ordering from a Station and that station has per-item limits, they may have already hit the maximum quantity for the current period. --- ## Budgets ## How do budget reservations work? When a requisition with a budget is submitted, the requested amount is reserved against that budget. On approval the reservation moves from reserved to committed. On rejection or cancellation the reservation is released back to available funds. Reservations expire after 30 days if not committed. If the budget has hard stop enabled, submitting a requisition that would exceed the available amount is blocked outright. ## What are the default budget alert thresholds? Every budget starts with three alert thresholds: **75%**, **90%**, and **100%** utilization. When utilization crosses a threshold, the system creates an alert and notifies the budget owner. Alerts are suppressed for 24 hours after firing to avoid duplicates. --- ## Licensing and limits ## Does Procurement require a licence? Yes. Procurement requires a licence and must be enabled by an admin from Admin → Apps → All Apps before it is available to users. ## What currencies are supported? The default currency is USD. The supported currencies in the currency picker are **USD**, **EUR**, **GBP**, **CAD**, and **AUD**. The default can be changed in **Settings → Document Numbering → Default Currency**. ## What payment methods can I record? Check, Wire Transfer, ACH, Credit Card, and Other. The default payment terms on an invoice are 30 days. --- ## More help - [Procurement Overview](/help/articles/procurement_app_overview) - Ask AI — the assistant answers Procurement questions from these articles. **Keywords:** faq, procurement, requisition, purchase order, invoice, approval workflow, budget, three-way matching, vendor catalog, supply ordering, spend intelligence, not showing, approval threshold, permissions --- # Recognitions FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Recognition — allowances, budgets, award programs, anti-gaming controls, visibility, and kiosk mode. # Recognitions FAQ Answers to common setup and operating questions about Recognition. For what the app is and how to stand it up, see the [Recognition Overview](/help/articles/recognitions_app_overview). --- ## Allowances and points ## Why does someone have a 5,000-point giving allowance? Monthly giving allowances are set by role tier, not by seniority. The defaults are **1,000 for an individual contributor, 2,000 for a manager, and 5,000 for leadership**. A 5,000-point balance means that person resolves to the leadership tier — which is a *permission*, so an admin or owner lands there regardless of their place on the org chart. ## What's the difference between giving points and a Boost? Giving points happens when you **create** a recognition. A **Boost** adds points to a recognition that already exists — a one-tap "me too" — and it spends from the booster's own monthly giving allowance. Boosts are fixed at **5, 10, or 25 points**, and the feed only offers amounts the booster can still afford; if their remaining allowance is under 5, no Boost buttons appear. Each person can boost a given recognition **once**. ## Can someone boost a recognition they were involved in? They can't boost one where they are the **recipient**. Boosting a recognition you *gave* to someone else is allowed — the restriction is on receiving, not authoring. ## Why can't I attach a group budget to my Peer-to-Peer program? Peer-to-Peer recognition is funded entirely by each employee's monthly Peer Giving Allowance rather than a pooled pot, so the system rejects a group budget on that program type with an explicit error. Use group budgets on **Manager**, **Achievement**, or **Milestone** programs instead. --- ## Governance and anti-gaming ## How do I stop people from gaming recognition? Two admin-configured controls, both **off by default** (set to `0`): | Control | What it does | |---|---| | Monthly cap per giver | Limits how many recognitions one person can give in a calendar month | | Duplicate cooldown | Blocks recognizing the **same person** again within N days | Both count awards and recognition posts together, since to the recipient they're the same act. Because they default to off, a tenant that never opens these settings is unaffected. ## Do these limits also block awards the system generates? No. Award cycles, approved nominations, and lifecycle or certification milestones are not routed through the anti-gaming guard — it governs the open, user-initiated surface only. A cap you set for peer spam will not quietly suppress a service anniversary. --- ## Visibility and access ## Who can see a recognition once it's posted? Every recognition carries one of four visibility scopes — **public**, **department**, **team**, or **private**. Public posts are the ones that flow into the company News Feed (when the Communications app is enabled); the other three narrow the audience. Scope is set per recognition, so "is recognition visible to everyone?" depends on what the author chose, not on a single tenant-wide switch. ## Can I take back a recognition I gave? Yes, for a shout-out. Open the recognition's **⋮** (More actions) menu on the feed and choose **Delete** — on a phone, open the recognition and tap **Delete**. It leaves the feed, any points it carried are reversed, and your giving allowance is refunded. Recognitions moderators — business admins and Recognition app admins — can delete anyone's shout-out the same way. An **award** (from a program, an award cycle or an automatic milestone) is different: the person who gave it can't delete it. A Recognition admin **revokes** it while it is still active — on the web with **Revoke** on **Admin → Point Ledger**, on the person's page under **Team**, or on the award cycle's page; in the mobile app from the award's **⋯** menu (**Delete**). Revoking returns its cost to the budget, takes back the recipient's store points and tells them. Ask AI can find the recognition for you, but it does not delete or revoke one — use the steps above. ## Can frontline employees without a computer or company email participate? Yes, through **kiosk mode**. A shared device runs a kiosk session for a location, and employees identify with their employee ID and PIN — no corporate login — then recognize a colleague and the screen resets for the next person. A kiosk session can carry a timeout in minutes, after which it expires and has to be re-established. Leaving the timeout blank means the session runs until someone deactivates it, which is usually what you want for a permanently mounted device. --- ## What your users will report ## "I can't see the Boost button on anyone's recognition." Most often their remaining monthly allowance has dropped below 5 points, so no Boost amount is affordable and the buttons are hidden rather than shown-and- rejected. Check their allowance for the current month. Boosting also requires that giving allowances are enabled for the business and that the person is permitted to give recognition at all. ## "I'm not notified when a recognition needs my approval, or when my team is recognized." A recognition held for approval goes to the recipient's manager, or to the default reviewer, as an Inbox item, an email and a phone push. If one of those is missing, check the person's own notification preferences first — **Recognition · Approval Requests** — because a choice saved there wins over the defaults. The tenant-wide switch is **Pending approvals** under Recognition settings → Notifications. Managers hear about their team under **Team member recognized** in the same settings section: when a colleague recognizes one of their people, and by email too for work anniversaries and milestones. A manager isn't told about a recognition they gave, one they approved, or one they can't see. Each person controls these in their notification preferences, and both arrive in the app, by email and as a phone push unless they turn a channel off: - **Recognition · For You** — you were recognized, an award or milestone, a nomination, and the giver's side: the recipient tapping **Say thanks** (or replying), and a once-a-day "N people celebrated your recognition". - **Recognition · Your Team** — a manager's team recognitions and milestones, the monthly nudge about teammates who haven't been recognized, and the weekly leader digest. Mentions, comments, shares and the weekly digest stay under **Recognition**, which doesn't push unless the person turns push on for it. Points about to run out get their own reminders, in the app, by email and as a phone push: unspent giving points in the last five days of the month (**Recognition · Giving Points Expiring**), and earned Company Store points 14 days before your company's expiry policy removes them (**Company Store · Points Expiring**). ## "I recognized my teammate but they got no points." Check the recipient's worker classification. If their classification sits on the reward-points-excluded list, the recognition still posts and still appears in the feed, but the monetary points credit is skipped by design. --- ## More help - [Recognition Overview](/help/articles/recognitions_app_overview) - [Company Store Overview](/help/articles/company_store_app_overview) — where earned points are redeemed - Ask AI — the assistant answers Recognition questions from these articles. **Keywords:** faq, recognition, giving allowance, peer giving, boost, group budget, award program, award cycle, nomination, anti-gaming, cooldown, recognition kiosk, visibility, points, delete recognition, revoke award, recognitions --- # Recognitions Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 What the Recognitions app does, how to stand it up, and the settings an admin configures — peer recognition, award programs, giving allowances, budgets, kiosks, and award cycles. # Recognitions ## 1. What it is Recognitions lets employees recognize each other, managers award team members, and admins run structured nomination programs — all from one social feed. Each recognition can carry a company value, an illustrated award card, and (optionally) redeemable reward points that bank into the Company Store. - **Enablement:** requires a licence. An admin enables it from Admin → Apps → All Apps; it is not turned on automatically. - **What it is not:** Recognitions does not manage the point redemption catalogue — that is the Company Store app. Points earned here appear in the employee's store wallet, but the items they can redeem against live in a separate app. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Recognitions**, and enable it. 2. The first time anyone opens the app, a starter recognition program ("Employee Recognition", peer-to-peer) and six company values (Customer First, Teamwork, Integrity, Innovation, Excellence, Ownership) are seeded automatically. Admins can rename, delete, or add to either set — deleted defaults do not come back. 3. If you want employees to attach redeemable points to their recognitions, enable **Peer Reward Points** under **Settings → Reward Points**. This requires the Company Store app to also be enabled — without it, the toggle has no effect because there is nowhere to bank the points. 4. Grant the **App Admin** role to anyone who should manage programs, budgets, and settings without being a full business admin. Managers automatically see a **Team** tab for approvals once they have direct reports. 5. Confirm by opening the app as a non-admin employee. They should see the Dashboard, Feed, My Recognition, Programs, Leaderboard, and a working "Recognize" action. **Silent pairing to know about:** the Peer Reward Points toggle does nothing on its own — the Company Store must also be enabled and its recognition integration must not be turned off. If both conditions aren't met, points fields won't appear in the give form. ## 3. How it fits together **Programs and categories.** A recognition program defines the type of recognition (Peer-to-Peer, Manager, Achievement, or Milestone), whether nominations require approval, and the point range for each category within it. Categories under a program carry a name, color, icon, and default/min/max point values. The seeded "Employee Recognition" program ships with four categories: Teamwork, Helpfulness, Innovation, and Excellence. **Peer recognition posts vs. awards.** A recognition post is the everyday "shout-out" any employee gives from the feed. An award is the outcome of a nomination that was approved through a program's approval chain. Both appear in the same feed, but they follow different paths: posts are immediate (unless manager approval is required), while awards route through one or more approval levels defined on the program. **Giving allowances vs. group budgets.** These are two separate funding pools and the most common source of admin confusion: - A **giving allowance** is a per-employee monthly point budget for peer recognition posts. It resets each month and does not carry over. Three role tiers get different defaults: individual contributor, manager, and leadership. - A **group budget** is a company-, department-, or manager-level annual dollar pool that funds awards given through Manager, Achievement, or Milestone programs. Group budgets are hierarchical (company → department → manager) and enforce hard-stop spending limits. Peer-to-Peer programs draw from the giving allowance. The other three program types draw from group budgets. You cannot attach a group budget to a Peer-to-Peer program. **Award cycles (Model B).** A time-boxed nomination period where nominations pool during a window, then winners are selected either by **Spotlight** (everyone nominated by at least the cycle's threshold of different people) or **Committee** (the cycle's committee members each pick from the pool, and an admin decides the winners). A cycle nomination needs no manager approval — it waits in the pool until the cycle is decided. Award cycles are off by default and are independent of program award nominations, which have their own switch. **Company values.** A curated list of organisational values that employees tag onto a recognition. The six seeded defaults are a starting point — admins manage them at **Admin → Company Values**. **Award cards.** Illustrated card art from the Asset Library that the giver selects when composing a recognition. The app ships with system cards across 14 categories (Everyday Thanks, Teamwork, Customer Focus, Performance & Results, Above & Beyond, Innovation, Safety, Values & Integrity, Growth & Leadership, Wellbeing & Culture, Fun & Personality, Milestones & Service, Celebrations & Occasions, General). Admins add tenant-specific cards at **Admin → Award Cards**. ## 4. Running it ### Reviewing pending approvals When **Require manager approval** is on, or when a peer recognition carries points at or above the approval threshold, recognitions and nominations land in a pending queue. Reviewers (managers with direct reports, app admins, and business admins) see a banner on the Dashboard showing the count of items awaiting their decision. Reviewers do not have to open the app to decide. The approval email carries **Approve** and **Reject** links (a signed link, no login required; each opens a short confirmation page), and the item in your **Inbox** carries an **Approve** button — usually the fastest route on a phone. Whichever one you use, the decision is the same: deciding in the Inbox runs the identical approval path as the web queue, respects multi-level approval chains, and keeps the nomination's requested value. Turning something down needs a reason for the person who sent it, so rejecting is done from the app or the email's Reject form, never from a bare Inbox button. 1. Open **Team → Pending Approvals**. 2. Review the recognition content and point amount. 3. Approve or reject. Approved posts become visible; rejected posts are hidden and the giver's points are refunded. ### Managing programs 1. Go to **Admin → Manage Programs**. 2. Create a new program, choosing a type (Peer-to-Peer, Manager, Achievement, or Milestone) and the number of approval levels (1–5). 3. Add categories with point ranges under the program. 4. Activate the program when ready — employees see it in the Programs tab. ### Running an award cycle 1. Enable **Award Cycles** under **Settings → Cycles & Automation**. 2. Go to **Admin → Manage Award Cycles** (or the **Manage award cycles** button on that settings card) and create a cycle (cycles are filed under a built-in "Mango Champions" program). Give it a name, instructions, the criteria nominators read, an optional category, the nomination window (opens/closes dates), the points each winner receives (0 means recognition only), the selection mode (Spotlight with its distinct-nominator threshold, or Committee with its members), whether to favor first-timers, and whether it repeats weekly, monthly or quarterly. 3. When the window closes the cycle shows **Awaiting decision**. For Spotlight, review the nominees who met the threshold; for Committee, the members' picks are shown beside each nominee. 4. Decide winners — this creates their awards, credits the cycle's points and notifies the winners. The cycle then shows **Winners announced** and its results page lists them. ### Nominating in an award cycle When Award Cycles are on, everyone sees an **Award Cycles** tab in the app. It lists the cycles open now (each marked **Open**, with **Nominate**), an **Opening soon** list with each cycle's opening date, and **Recent winners** with **See results**. 1. On an **Open** cycle, choose **Nominate**. 2. Pick the colleague and say what they did — the cycle's criteria are shown above the form. 3. Submit. The nomination joins the cycle's pool; nobody approves it on its own, and the winners are chosen when the cycle closes. You can't nominate yourself, and you can nominate each colleague once per cycle. If your organization limits who may give recognition, the same limit applies to cycle nominations. Committee members find a cycle waiting for their decision under **Needs your review** on that tab and choose **Review nominees**; a member who is up for the award does not judge it (unless they are a business admin). ### Managing kiosk devices For frontline locations where employees don't have individual logins, a shared device can run a recognition kiosk. 1. Go to **Admin → Kiosk Devices** (requires Manager or above). 2. Create a session for a location, setting an alphanumeric passcode. 3. On the shared device, navigate to the kiosk URL and enter the passcode. 4. Employees identify themselves by employee ID and PIN, recognise a colleague, and the screen resets automatically. ### Using the Recognition Wall The Recognition Wall is a chrome-less, auto-refreshing display for a lobby TV or large screen. It is authenticated by a signed display token, not a user login. 1. Go to **Admin → Recognition Wall** (opens in a new tab). 2. Generate a display token under **Settings → Tools & Data** if one doesn't exist. ### Viewing analytics Admins and app admins find **Analytics** as the first item of the **Admin** menu: recognition activity, insights, and an at-risk view that flags employees or teams with low recognition activity. ## 5. Settings All settings are under the app sidebar's **Settings** dropdown. Settings are grouped into six sections. ### General | Setting | Default | What it changes | |---|---|---| | Peer-to-peer recognition | On | When off, only manager/admin award flows are available | | Anonymous recognition | Off | When on, employees can hide their name on a recognition | | Enable award nominations | On | Shows the Programs tab and lets people nominate peers for program awards | | Require manager approval | Off | When on, **every** peer recognition and **every** award nomination is routed to the recipient's manager before it posts — not just nominations | | Enable reactions | On | Toggles emoji reactions on the feed | | Enable comments | On | Toggles comment threads on recognitions | ### Reward Points | Setting | Default | What it changes | |---|---|---| | Enable peer reward points | Off | Turns on per-employee monthly giving allowances (requires Company Store) | | Monthly Giving Allowance — Individual Contributor | 1,000 points | Points each IC can give per month | | Monthly Giving Allowance — Manager | 2,000 points | Points each manager can give per month | | Monthly Giving Allowance — Leadership | 5,000 points | Points each leadership member can give per month | | Hold Peer Gifts for Approval At/Above | 500 points | Peer gifts at or above this threshold require reviewer approval before settling | | Min Days Between Points Gifts to Same Person | 7 days | Minimum gap before giving points to the same person again | | Leadership group | None | A group (Admin › Groups) whose members resolve to the leadership tier for allowance sizing — when not set, Admin/Owner role is used | ### Cycles & Automation | Setting | Default | What it changes | |---|---|---| | Enable award cycles | Off | Enables time-boxed nomination cycles with winner selection — adds the Award Cycles tab for everyone and Manage Award Cycles for admins | ### Notifications | Setting | Default | What it changes | |---|---|---| | Recognition digest & year in review | Off | One switch for two mailings: the weekly summary of recognition activity, and each employee's annual Recognition Wrapped recap every January | ### AI Agent | Setting | Default | What it changes | |---|---|---| | Enable AI Agent | On | Lets the Ask AI assistant give recognition, submit nominations, and approve on behalf of the user | ### Tools & Data This section provides admin actions rather than persistent settings: generating the Recognition Wall display token, loading or removing sample data, resetting all store-point balances, running a CSV bulk import, and importing a program configuration. ## 6. More help - **[Recognitions FAQ](/help/articles/recognitions_app_faq)** — specific setup and operating questions, including giving allowances, boosts, anti-gaming controls, kiosk mode, and troubleshooting. - **[Company Store Overview](/help/articles/company_store_app_overview)** — where earned reward points are redeemed. - Ask AI — the assistant answers questions about Recognitions from these articles. **Keywords:** recognition, peer recognition, awards, nominations, company values, giving allowance, reward points, leaderboard, kiosk, award cycle, recognition wall, boost, group budget, recognition program, recognitions --- # Recorder App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How free desktop capture and the Recorder cloud library fit together — enabling the app, what happens after an upload, visibility and sharing, public links, hand-offs into other apps, and every setting with its default. # Recorder ## 1. What it is Recorder is the cloud side of the desktop app's screen capture. Capturing a region, a window, the whole screen or your camera in the OneMango desktop app is free and works whether or not a company has the app: recordings and screenshots are saved on the computer that made them. Recorder adds a company library for those files. An uploaded recording gets a page on the web and on a phone, is transcribed and summarised, can be shared with named people, the whole company or an outside viewer, and can be handed to Training, SOP Hub, Libraries, Service Desk or Practice Hub. - **Enablement:** Recorder requires a licence. An admin enables it from Admin → Apps → All Apps, then configures it from **Settings** inside the app. - **What it is not:** Recorder is not AI Notepad. AI Notepad is for meetings — their notes, transcripts, action items and decisions. Recorder is for the screen and camera recordings people make on purpose: walkthroughs, how-tos, updates and bug reports. Recordings are their own library; they are not Drive files and do not appear in Drive. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Recorder**. 2. Open the app and go to **Settings** (visible to admins and to app admins for Recorder). 3. Under **New recordings**, set **Default visibility** to **Only the person who recorded it** or **Everyone in the company**. Tick **Enforce this default for everyone** if people must not choose their own default. 4. Under **Uploads**, set the **Maximum upload size (MB)**. Uploads larger than the cap are refused before any bytes are sent. 5. Under **Public links**, decide whether to tick **Allow public links**. Until it is on, nobody can mint a link for outsiders, and the **Anyone with the link** option in Send to chat does not appear. 6. Under **Transcripts and AI**, leave the three switches on unless the workspace should not spend AI credits on recordings. Transcription is what makes a recording searchable, captioned and usable by Ask AI. 7. To verify: in the desktop app, capture a screenshot, click **Upload** on its card, then open the link it copies. The recording's page shows the file with its poster. Record a short narrated video the same way; within a few minutes its page gains a transcript, a summary and chapters. Two pairings silently do nothing until both halves are set. **Draft an SOP** and the other hand-offs appear only where the target app (Training, SOP Hub, Libraries, Service Desk, Practice Hub) is enabled and the person may use it. **Translate captions into the workspace's languages** does nothing until the workspace has enabled languages under the platform's translation settings. A company that has not enabled Recorder sees the desktop panel exactly as before: capture, annotation, trimming, the tray and the shortcuts keep working, and no cloud actions appear. ## 3. How it fits together **Local first** — A capture is saved to the computer's capture folder the moment it ends. Uploading is a separate, optional step, and the local file stays where it is afterwards. A card that has been uploaded shows **Copy link**, **Open in browser**, **Share…**, **Send to chat** and **Use this recording** instead of **Upload**. The desktop's **Cloud** tab lists what is already on the server. **One row per capture** — The desktop identifies each capture by the file it was saved as, so retrying an interrupted upload, or uploading the same capture twice, lands on the same recording rather than a duplicate. Cancelling an upload moves its recording to the recycle bin; uploading that capture again brings the same recording back. **Videos and screenshots** — A recording is either a video or a screenshot. Both share the library, sharing, links, comments, pins and the recycle bin. Only videos get a transcript, a summary, chapters, captions, a call-to-action and watch-through insights; a screenshot's page shows the image and its details. **Processing** — After the bytes arrive, the server confirms the file type, reads the duration and dimensions the desktop did not send, and makes a poster frame when none was supplied. A video is then transcribed, summarised into a summary with chapters, and its captions are translated. The page shows **Processing** until the poster is ready and fills in the transcript and chapters as they finish. A silent screen recording finishes without a transcript; that is normal, not a failure. **Three ways to open a recording** — *Visibility* is the recording's own switch: **Only the person who recorded it** (and the people it is shared with), **Everyone in the company**, or **Anyone with the link** (when an admin allows public links). *Sharing* adds named people on top of that, as **Viewer** or **Editor**. A *public link* is a separate door for people without a OneMango account; it is minted per recording, can expire, carry a password or ask for an email, and stops working the moment an admin turns public links off. Admins configure the app but get no read-all door into private recordings; they can, however, restore any deleted recording. Worked example: Priya records a 4-minute walkthrough of the new expense form. It starts as **Only the person who recorded it**. She shares it with Dan as **Editor** so he can retitle it, and with the finance team lead as **Viewer**. Once the form ships she flips it to **Everyone in the company** so nobody needs to be named. When the outside auditor asks, she mints a public link that expires in 7 days, asks for an email before playing and hides the Download button. **Owner, editor, viewer** — The owner is the person who uploaded the recording; only the owner can change the **Show a Download button** switch, delete or restore it, and see who watched. An editor can rename it, change its visibility, share it further (unless an admin turned off **Editors can pass a recording on**), set the thumbnail, manage captions, add a call-to-action and mint public links (where the workspace's publish policy allows them). A viewer can play, comment, react, pin, and gets a Download button when the owner shows one. That switch controls the button, not the bytes: anyone who can watch a recording can save the file from their browser either way. **Pins** — The **Pin** button on a recording is a Bookmark; pinned recordings appear on **Bookmarks** alongside wikis, tasks and pages, and disappear from there if the recording is deleted or the app is turned off. **Hand-offs reference, never copy** — **Use this recording** creates a record in another app that points back at the recording: a Training lesson that plays it inside the course player with the transcript already attached, a draft SOP whose steps come from the chapters, a library link item, a comment on a Service Desk ticket, a new ticket whose title and steps AI drafts from the transcript for the person to edit before sending, or a Practice Hub attempt. Deleting the recording never deletes the lesson, SOP or ticket; the reference goes blank. **Classic My Recordings** — For customers coming from MangoApps Classic, Recorder is the successor to My Recordings. Private and company privacy, sharing roles, public links, pins, the recycle bin, thumbnails, captions, the call-to-action and view insights each have a counterpart here; hashtags and public-page color themes do not. Classic recordings do not appear in Recorder on their own; the migration is scheduled with MangoApps per workspace. ## 4. Running it ### Uploading from the desktop, the web or a phone In the desktop app, open the **Recorder** panel, find the card and click **Upload**. In the capture editor, **Quick Save to Recorder** saves the edited image or trimmed clip and uploads it in one step, copying the link when the upload is ready. On the web, drag a file onto the **Recordings** page. On a phone, open the mobile library and record straight from the camera or pick a file from the camera roll. All three land in the same library and go through the same processing. ### Working in the library **Recordings** lists everything you can see, with **Videos** and **Screenshots** tabs, a **Mine** / **Shared with me** filter, **Search by title** and a **Sort** control. Tick several cards to **Share with company**, **Make private**, **Download zip** or **Delete** them together. The **Insights** tab in the left navigation shows plays, completion and call-to-action clicks for your own recordings, exportable as CSV; the **Preferences** tab sets what your new recordings start as, and whether to transcribe them. ### Sharing and links **Share** opens a drawer with **People with access**, where you add people as **Viewer** or **Editor**, and — when the admin allows it — a **Public link** section with **New public link**, an expiry, a password, **Ask for an email before playing** and **Show a Download button on this link**. The same drawer holds **Get embed code**. **Send to chat** posts a card with the title, an optional note and the link into a chat room. ### Transcripts, captions and thumbnails On a video's page, **Captions & translations** lets an editor translate the captions now, upload a caption file, edit a track or delete one. **Set thumbnail** picks a frame from the video or uploads an image. The chapter list and the transcript panel seek the player when clicked. ### The recycle bin **Delete** moves a recording to the **Recycle bin**, where it can be restored for **30 days**; after that a nightly sweep removes the recording and its file for good. Members see their own deleted recordings; admins see every deleted recording in the company, by title and owner, and can restore any of them. With **Keep recordings for (days)** set, older recordings move to the recycle bin on their own each night. ## 5. Settings All at **Recorder → Settings**, in the order the page shows them. | Setting | Where | Default | What it changes | |---|---|---|---| | Default visibility | New recordings | Only the person who recorded it | What a new upload starts as when the person has not chosen their own default. | | Enforce this default for everyone | New recordings | Off | When on, **Your preferences** no longer offers a personal default and every new recording starts at the tenant default. | | Show a Download button on new recordings | New recordings | On | Seeds each new recording's **Show a Download button** switch; owners can still change it per recording. It shows or hides the button — it does not prevent saving. | | Maximum upload size (MB) | Uploads | 1000 | The largest file the desktop, the web or a phone will accept. | | Allow public links | Public links | Off | Whether editors can mint links for people without an account. Turning it off makes every existing public link stop working. | | Links expire after at most (days) | Public links | 0 (never expire) | The longest life a new public link can have; a longer request is shortened to this. Lowering it does not shorten links that already exist. | | Who can publish a recording on a public link? | Public links | Everyone with access to the app | Whether anyone who can use Recorder, or only Recorder admins, can open a recording to people outside the company. | | Editors can pass a recording on | Sharing with people | On | Whether an editor can add and remove the people a recording is shared with. Off leaves that to the person who made it. | | Transcribe new recordings (captions, search and Ask AI) | Transcripts and AI | On | Whether videos are transcribed after upload. Off means no captions, no summary and no search by what was said. | | Write a summary and chapters from the transcript | Transcripts and AI | On | Whether a transcribed video also gets a summary and chapters. | | Translate captions into the workspace's languages | Transcripts and AI | On | Whether captions are translated into the languages the workspace has enabled, and whether **Translate now** appears on a recording. | | Recorder Agent in Ask AI | Recorder Agent | On | Whether people can find and act on recordings from the Ask AI sidebar. | | Keep recordings for (days) | Retention | 0 (keep for ever) | Recordings older than this move to the recycle bin each night. | | Flag company-visible recordings that have not been updated | Retention | Off | On the weekly content-governance scan, flags company-visible recordings that have passed the review interval without being updated and nudges the owner to confirm they are still accurate. Recordings nobody has played are marked higher priority. | Transcription, summaries and caption translation draw on the workspace's shared AI wallet. ## 6. More help - **Recorder FAQ** — why Upload is missing, who can see what, public-link behaviour, transcripts that never arrived, the recycle bin, and every limit. - Capture itself — regions, windows, the camera, annotation, trimming and shortcuts — is part of the desktop app and does not depend on Recorder. - Ask AI — the assistant answers questions about Recorder from these articles. **Keywords:** recorder, screen recording, screenshot, screen capture, desktop app, upload recording, share recording, public link, transcript, captions, recycle bin, add to training, my recordings, clips --- # Recorder FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-09 Answers to common setup and operating questions about Recorder — for the admin running it and for the people recording: why Upload is missing, who can see a recording, public links, transcripts, the recycle bin, and every limit. # Recorder FAQ Answers to common setup and operating questions about Recorder. For what the app is and how to set it up from scratch, see the [Recorder Overview](/help/articles/recorder_app_overview). --- ## Setup ## Do I have to configure anything before people can upload? No. Once an admin enables Recorder from Admin → Apps → All Apps, every card in the desktop app's Recorder panel gains **Upload**, the **Recordings** page accepts drag-and-drop, and the mobile library can record from the phone. The defaults are private recordings, a 1000 MB upload cap, the Download button shown, and public links off. Two things need a second switch: public links stay unavailable until an admin ticks **Allow public links**, and translated captions need the workspace to have enabled languages. ## Who can change Recorder's settings? Business admins, and anyone made an app admin for Recorder. Settings is the last item in the app's left navigation, under **Admin**, and is hidden from everyone else. Admins also see every deleted recording in the recycle bin, by title and owner, and can restore any of them — but they get no read of a private recording's page or file. ## Does turning Recorder off take screen capture away from the desktop app? No. Capture, annotation, trimming, the tray section and the keyboard shortcuts are part of the desktop app and never depend on a licence. Turning the app off removes the cloud actions only: **Upload**, the **Cloud** tab, **Share…**, **Send to chat** and **Use this recording** disappear, and pinned recordings drop off the Bookmarks page. --- ## Permissions and access ## Why can't my colleague open the link I sent them? The recording is still private. A new recording starts as **Only the person who recorded it** unless the tenant default is **Everyone in the company**. Open the recording, click **Share** and add the colleague as a **Viewer** or **Editor**, or click **Share with company** so every active member can open it. ## Can people outside the company watch a recording? Only through a public link, and only when an admin has ticked **Allow public links**. An owner or editor opens **Share**, clicks **New public link** and chooses an expiry, an optional password, **Ask for an email before playing** and **Show a Download button on this link**. Admins can narrow who may publish with **Who can publish a recording on a public link?** — **Everyone with access to the app** (the default) or **App admins only**. A public link stops working the moment an admin turns public links off, and it can be revoked individually at any time. ## Why doesn't "Use this recording" offer Add to Training or Draft an SOP? Each hand-off appears only when its target app is enabled for the workspace and you may use it there. Add to Training needs the Training app and a video. Draft an SOP needs SOP Hub and an admin role. Use in Practice Hub needs Practice Hub with recording uploads allowed, a scenario with rubric criteria, and a transcript. Attach to a ticket and File a bug need Service Desk. ## Why is "Send to chat" missing, or my room not in the list? The button shows only when the workspace has the Chat app and you may send messages. The room list holds named rooms you are a member of — up to 100 — so a direct message thread is not offered. The **Anyone with the link** choice appears only when public links are allowed; otherwise the card carries a company link that requires sign-in. --- ## Day-to-day ## What happens to a video after I upload it? The server checks the file, reads its duration and size, and makes a poster frame if the desktop did not send one. If **Transcribe new recordings** is on and your own **Transcribe my recordings** preference is on, the video is transcribed and captioned. A transcript of at least 40 words then gets a summary and chapters, and the captions are translated into the workspace's languages, five languages per pass. You are notified when the transcript is ready. ## Can I stop people downloading a recording? You can change whether a **Download button** is offered, in two places — but that is a convenience, not a lock. The owner flips the recording's **Show a Download button** switch; its starting position comes from the admin's **Show a Download button on new recordings**. Each public link has its own **Show a Download button on this link** box, and the button appears on a link only when both switches are on. What it does not do is stop anyone saving the file: a recording that plays for you is served to your browser, and every browser's own video menu can save what it is playing. Treat the switch as tidying the page, and use visibility, public-link expiry, a password or **Ask for an email** to decide who can watch at all. ## How do I get a recording back after deleting it? Open **Recycle bin** in the app's left navigation and click restore. A deleted recording stays there for 30 days and the bin shows how many days each one has left; after that a nightly sweep removes it and its file for good. Owners see their own deleted recordings; admins see and can restore everyone's. ## Can I record from my phone? Yes. Open Recorder in the mobile web app and choose to record from the camera or pick a file from the camera roll. The upload goes through the same processing as a desktop upload, so it gets a poster, a transcript, chapters and captions, and it plays back on the phone with captions and chapters. Sharing, public links, editing and deleting are done on the web. ## How are plays and completion counted? A play is counted once per viewer every 30 minutes; the same person replaying within that window does not add a play. Completion means the viewer covered at least 90 percent of the video. The insights panel on a video's page shows plays, unique viewers, downloads, completion rate, the second most people stop at, a per-second heatmap and — for the owner — who watched. A public link counts one open per browser session. --- ## When something looks wrong ## "There is no Upload button on my card" Either the workspace has not enabled Recorder, or the desktop app was signed in before the app was enabled. If the card says **Sign out and back in to enable uploads.**, sign out of the desktop app and back in; the session then gains the upload permission without reinstalling. ## "This file is larger than your company's upload limit." The file exceeds **Maximum upload size (MB)** in Recorder's settings, 1000 MB by default. An admin can raise it to 4000 MB. The check runs before any bytes are sent, so trimming the clip in the editor and uploading the shorter file is the fastest fix. ## "My recording has said Processing for a long time" Poster and transcript arrive in stages, and a long video's transcript can take several minutes. If the server gives up it marks the recording failed with a message: **We couldn't process this recording. Try uploading it again.** or **This file isn't a video or image we can read. Record it again and upload the new file.** Uploading the same capture again from the desktop replaces the file on the same recording rather than creating a second one. Until then, a failed recording is visible only to its owner and its editors. Colleagues who could see it through **Everyone in the company**, or as a **Viewer**, will not find it in their library. It also cannot be switched to **Anyone with the link**, and no new public link can be created for it, because the link would never play. As soon as it is uploaded again, everyone it was shared with sees it again and public sharing is back; a public link plays once processing finishes. ## "My video never got a transcript" Check four things in order. **Transcribe new recordings** in Settings is off for the workspace. Your own **Transcribe my recordings** preference is off. The recording has no audio — a silent screen recording finishes as ready with no transcript, which is normal. AI is paused for the workspace — a monthly AI limit was reached, or its credits ran out and its AI billing stops at zero (**Billing & Payments → AI**) — in which case processing waits until AI is available again. A transcript shorter than 40 words gets no summary or chapters. ## "The public link says it is turned off" or shows nothing An admin has unticked **Allow public links**; every existing link goes inert until it is ticked again. A link can also have expired, been revoked, or reached its maximum number of opens. A link also shows nothing while its recording is failed or in the recycle bin. When **Links expire after at most (days)** is above 0, a link asked to live longer is shortened to that limit when it is created. ## "A recording vanished from my library without me deleting it" Look in the **Recycle bin** first. When **Keep recordings for (days)** is set above zero, recordings older than that move to the recycle bin each night, and the owner can restore them for 30 days. A cancelled desktop upload also moves its recording to the bin; uploading that capture again brings it back. --- ## Licensing and limits ## Does Recorder require a licence, and who turns it on? Yes. A business admin enables it from Admin → Apps → All Apps; it is off until then. Transcription, summaries and caption translation draw on the workspace's shared AI wallet rather than the licence. ## We used My Recordings in MangoApps Classic — what carries over? Recorder is the successor to My Recordings. Private and company privacy, sharing roles, the viewer-without-download case (now the **Show a Download button** switch), public links, pins (now Bookmarks), the recycle bin, thumbnails, captions, the call-to-action and view insights each have a counterpart. Hashtags, custom public-page colors and the old desktop links do not carry over. Classic recordings do not appear in Recorder on their own; the migration is scheduled with MangoApps for each workspace and keeps each recording's owner and privacy. ## Are there limits I should know about? | Limit | Value | |---|---| | Upload size | 1000 MB by default; admins set 10 to 4000 MB | | Accepted files | WebM, MP4, MOV video; PNG, JPEG images | | Video length | Up to 24 hours | | Title / description | 150 / 5,000 characters | | Custom thumbnail | PNG, JPEG or WebP up to 2 MB | | Caption file | WebVTT up to 2 MB; translation runs five languages per pass | | Public link | Never expires by default; admins can cap expiry at 1 to 365 days; password up to 72 characters; up to 100,000 opens | | Call-to-action | Label up to 60 characters; an http or https link | | Comment / chat note | 4,000 / 1,000 characters | | Bulk actions | Up to 100 recordings at a time; a zip holds up to 100 files or 1 GB | | Insights table | Up to 500 of your recordings; the who-watched list shows 50 | | Recycle bin | 30 days, then removed for good | | Retention | Keep for ever by default; admins set 1 to 3,650 days | --- ## More help - [Recorder Overview](/help/articles/recorder_app_overview) - Ask AI — the assistant answers Recorder questions from these articles. **Keywords:** faq, recorder, screen recording, screenshot, upload, public link, transcript, captions, recycle bin, send to chat, add to training, my recordings, not showing, permissions --- # Recruiting Agent App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-13 How to set up and run the Recruiting Agent — AI screening of Job Board applicants, an approval queue for the actions it wants to take, and Ask AI answers about your hiring pipeline. # Recruiting Agent ## 1. What it is The Recruiting Agent reads each applicant's resume against the job they applied for. It returns a score out of 100, a recommendation, and the strengths and gaps it found. Recruiters and hiring managers review those results. The agent can also draft candidate emails and book interviews for them, and it answers pipeline questions through Ask AI. - **Enablement:** the app requires a license. An administrator enables it from Admin → Apps → All Apps, then clicks **Publish to users** on the app's page. Until then only admins can open it. - **What it is not:** it is not a candidate database. Jobs and applicants live in Job Board; the Recruiting Agent works on them and keeps no list of its own. Stage changes happen in Job Board, through Ask AI with a confirmation, or when you approve or reject a screening (see Reviewing a screening). ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, enable **Recruiting Agent**, and click **Publish to users**. Until it is published, only admins can open the app. Ask AI must be enabled too; the Dashboard's Ask AI card only appears when it is. 2. Make sure Job Board is in use, with at least one published job and its **Recruiter** and **Hiring Manager** set on the job form. Those two people receive the agent's review notifications and its approval requests. A job with neither set is screened, but nobody is told about the result. 3. Open **Recruiting Agent → Settings** (admins and app admins). Fill in **Company Culture & Values** and **Custom Screening Instructions**. Both are blank by default; culture is pre-filled from your Company Profile if one exists. The agent screens without them, but every screening reads them when present. 4. Go to **Admin → AI Operations → Agent Settings** and find the Recruiting section. This is the second settings home, and it holds the switches that matter most. Here you set the **Ask AI Agent** switch, **Autonomous Operations**, and the two **Approval Requirements**. It also holds **Min Qualification Score**, **Auto-Advance Threshold**, and the four **Scoring Weights**. The weights must total 100 or the save is refused. 5. Leave **Autonomous Operations** off to begin with. Screening still runs; the agent just takes no action on its own. Turn it on later, once you have reviewed a batch of screenings and trust the scores. 6. To confirm it works: submit a test application in Job Board, or load demo data from **Settings → Demo data → Load Sample Data**. Within a few minutes the candidate appears under **Screenings** with a score and a recommendation. If the score is 80 or more, the hiring manager also gets an in-app **High-Scoring Candidate Alert**. **Silent dependency:** the auto-action switches on the app's Settings page do nothing until **Autonomous Operations** is on in AI Operations. That covers acknowledgments, rejections, phone-screen invites, and review-queue triage. You can set them before turning it on; the page says whether it is on. The one exception is **Auto-Screen New Applicants**, which runs whether or not Autonomous Operations is on. ## 3. How it fits together **Screening** — one AI pass over one candidate for one job. The agent extracts the resume text, scores technical skills, experience, education, and cultural fit, then blends them with your scoring weights into a single score. The score is stored on the candidate, so Job Board shows it too. Re-screening replaces it. **Recommendation** — derived from the score and two thresholds. Below **Min Qualification Score** (default 30) is **Decline**; at or above **Auto-Advance Threshold** (default 70) is **Advance**; anything between is **Review**. Example: three applicants for the Senior Software Engineer posting score 82, 55, and 22. The first is recommended Advance, the second Review, the third Decline. A Review recommendation sends the job's recruiter and hiring manager a **Candidate Ready for Review** notification. **Screening review vs pipeline stage** — the two things people conflate most. **Approve Screening** and **Reject Screening** record a reviewer's decision on the screening and write it to the audit trail. They also move a candidate who is still early in the pipeline: Approve moves an Applied, Screening, or Potentially Qualified candidate to Qualified, and Reject marks a candidate who is still in the pipeline Rejected (see Reviewing a screening). Reject sends a rejection email only when Job Board's own rejection-email setting is on. Every other stage change, such as Interviewed or Offered, is a Job Board action. Ask AI can do it too, and shows you the change before you confirm. **Autonomous Operations** — the master switch, in AI Operations. With it on, a background scan runs every 15 minutes and looks for work the enabled auto-actions allow. It acknowledges applications under 24 hours old. It proposes a phone-screen invite for a candidate in Screening whose current screening recommends Advance. It proposes a rejection for a candidate in Screening whose current screening, from the last 7 days, recommends Decline. Neither uses a keyword estimate or a screening a person has already approved or rejected, and both follow the two thresholds you set. Phone-screen invites and rejections always go to the approval queue first. Acknowledgments and review-queue triage can run without approval once the agent's trust level allows. Every agent starts at **Probation**, where everything is queued for a person. It earns **Standard** and then **Trusted** through successful actions. The current level and pause controls are in AI Operations, not in the app. **Approvals** — the queue of proposals the agent wants to carry out. Each proposal names the candidate, the action, and a priority. Approving carries it out immediately. A rejection sends the email and marks the candidate Rejected; a phone-screen invite sends the email and moves an Applied candidate to Screening. Declining requires a reason and nothing is sent. A proposal nobody decides is cancelled after 14 days and moves to **Cancelled or expired**. A new proposal notifies, in-app only, the job's recruiter and hiring manager when they are allowed to decide it, and this app's administrators. When none of them can decide, tenant admins are told instead, at most once a day. **Agent interviews vs Interview Scheduler** — interviews booked from this app's **Interviews** tab are the agent's own records. They do not appear in the Interview Scheduler app, and Interview Scheduler bookings do not appear here. Ask AI checks both before it books, so it will refuse to double-book a candidate who already has an upcoming interview in either place. **Ask AI** — the same agent, in conversation. Everyone can ask general questions. Candidate lookups, screening, ranking, outreach drafts, offer drafts, and interview booking are limited to recruiting staff. That means admins, HR admins, app admins, and the recruiter, hiring manager, or creator on a job. Anything that changes data shows a preview and asks you to confirm. **Two settings homes** — the app's own **Settings** page holds Auto-Screen, the auto-action switches, the two notification switches, the two screening text boxes, the outreach email tone, and who can approve the agent's proposals. **AI Operations → Agent Settings** holds the agent on/off switch, Autonomous Operations, approval requirements, thresholds, and weights. The app's Settings page links to the other one; it does not duplicate it. **Audit trail** — every screening, review decision, approval, outreach send or cancellation, and interview change is recorded with who did it and when. The most recent entries appear as **Recent Activity** on the Dashboard for people who can view candidate data. Admins can see every proposal the agent made and who decided it, and export it, under **Admin → AI Operations → Activity** (linked from Settings and Analytics). Records the agent created on its own are marked as autonomous, so you can tell agent actions from human ones. ## 4. Running it ### Reviewing a screening 1. Go to **Screenings**. The list shows the latest screening per candidate with its score, recommendation, and decision. Filter by candidate name, decision, recommendation, or job; **More Filters** adds a score range and screening dates. A candidate who is no longer moving through the pipeline (for example hired, rejected, or withdrawn) shows their pipeline status under their name. 2. **Screen a Candidate** starts a screening for any Job Board candidate, scored against the job they applied for. The result appears in the list when it finishes. 3. Open a screening to see the reasoning, strengths, gaps, deal-breakers, the parsed resume, the top other candidates for the same job, and this candidate's earlier screenings, with the current one marked. 4. Choose **Approve Screening** or **Reject Screening** (a reason is required). Approve moves a candidate who is Applied, Screening, or Potentially Qualified to Qualified. Reject marks a candidate who is still in the pipeline Rejected. A candidate who is further along, or already out of the pipeline, keeps their status and only the decision is recorded. Each screening takes one decision, on the candidate's current screening only: an older or cancelled screening, or one a new screening is about to replace, links to the current one instead. 5. **Re-screen** re-extracts the resume and runs a fresh analysis; the new result becomes the candidate's current screening. A score marked **Keyword estimate** came from keyword matching while the AI was unavailable. It is not an AI screening and has no confidence rating. On an AI screening, **Confidence** is worked out from the score — higher when the score is clearly high or clearly low, lower in the middle. It is not a rating the AI reports. To compare candidates, switch from **List** to **Rankings by Job** on the Screenings page. It ranks each candidate's latest screening by score within each job, ten jobs per page, with the job that has the highest-scoring candidate first. Search by job title, or narrow to open jobs and to candidates still in the pipeline. ### Working the approval queue 1. Go to **Approvals**. The **Pending** tab lists open proposals; **Approved**, **Declined**, and **Cancelled or expired** keep the history. 2. Open a proposal, read the candidate and action summary, then **Approve Proposal** (optional notes) or **Decline Proposal** (reason required). 3. Who can decide is set under **Settings → Who can approve or decline the agent's proposals?** (managers and above by default). Admins, HR admins, and recruiting app admins always can, and only people who can view candidate data can approve. Nobody can approve a proposal they raised themselves. ### Sending a candidate email 1. Go to **Outreach → New** and pick the candidate and an **Outreach Type**. The types are Application Acknowledgment, Initial Response, Rejection Email, Phone Screen Invitation, Interview Invitation, Offer, and Passive Candidate Outreach. 2. The agent writes a draft. Edit the subject and body, use the AI review to check it, then send it. Drafts can be cancelled; failed sends can be edited and retried. 3. A sent message shows **Sent** with the time. The app does not track opens or replies. ### Booking an interview 1. Go to **Interviews → New**, pick the candidate and an **Interview Type** (Phone Screen, Video, On-Site, Technical, Panel, In Person, Final). 2. Enter a **Date & Time**, or leave it blank. Left blank, the agent books the next business day at 10:00. It does not read anyone's calendar. The interviewer is the job's hiring manager, or the recruiter if no hiring manager is set. 3. The candidate receives a confirmation email and the interviewer a notification, unless **Interview Notifications** is off. 4. From the interview page you can reschedule or cancel (both need a reason) and mark it complete with a decision of Advance to Next Stage, Do Not Advance, or On Hold. Whichever you choose, completing an interview moves a candidate who has not been interviewed yet to Interviewed, or to Interviews in process when the job's interview workflow has more stages. None of the three rejects the candidate; rejecting is a separate stage change. The **Calendar** view shows the month's agent-booked interviews. ### Checking analytics and testing tools **Analytics** is open to every user and shows aggregates only. It charts screenings per day, score distribution, and the recommendation breakdown. It also counts outreach sent by type and interviews scheduled, completed, and cancelled, plus average time to screen and average score. Switch the range between **Last 30 Days**, **Today**, **Week**, **Month**, and **Quarter**. **Playground** (admins and app admins) runs each tool against a real candidate or test data: screening, outreach, interview scheduling, offer generation, and ranking. Screening and ranking make live AI calls; ranking screens at most 25 unscored candidates per run. Outreach tests produce drafts only and email nobody. ### What your people see Anyone the app is published to sees the **Dashboard** counters (screenings today, average score, pending approvals, outreach sent today) and **Analytics**. People with access to candidate data (admins, HR admins, recruiting app admins, this app's admins, and whoever your Talent Hub candidate-data setting allows, which is managers and above by default) also see Screenings (including Rankings by Job), Approvals, Outreach, and Interviews. On a phone, the app opens as a mobile view with the dashboard, screenings, approvals, and a read-only list of interviews; people who can approve the agent's proposals can approve or decline there. ## 5. Settings **Recruiting Agent → Settings** (admins and app admins): | Setting | Default | What it changes | |---|---|---| | Auto-Screen New Applicants | On | Screens every new application when it arrives, and a candidate moved to Screening who has no screening yet. An internal applicant (an employee applying to an internal posting) is screened only when someone clicks Screen, because their application has no resume. Runs whether or not Autonomous Operations is on. Off stops both. | | Auto-Send Acknowledgments | On | With Autonomous Operations on, the 15-minute scan proposes an application-received email for applicants under 24 hours old who have not had one (Job Board's own confirmation counts). It waits in Approvals until the agent's trust level lets it send on its own. | | Auto-Triage Recruiter Review Queue | Off | With Autonomous Operations on, notifies the job's recruiter (or hiring manager) about candidates recommended Advance or Review who have waited 12 hours or more without a decision. A job with neither person set gets no notice. | | Auto-Send Rejections | Off | With Autonomous Operations on, queues a rejection email for candidates in Screening whose current screening, from the last 7 days, recommends Decline. Always goes through Approvals. | | Auto-Send Phone Screen Invites | Off | With Autonomous Operations on, queues a phone-screen invitation for candidates in Screening whose current screening recommends Advance. Always goes through Approvals. | | Notify Approvers When the Agent Needs a Decision | On | Sends an in-app notification, and one reminder after 48 hours, to the people who can decide a new proposal. Off sends neither; proposals still wait in Approvals. | | Interview Notifications | On | Emails the candidate when a Recruiting Agent interview is booked, moved, or cancelled, and notifies the interviewers. Off still books, moves, and cancels interviews; it just sends nothing. | | Company Culture & Values | Blank | Text the AI reads on every screening to judge cultural fit. Pre-filled from your Company Profile when one exists. | | Custom Screening Instructions | Blank | Deal-breakers, priorities, and preferences applied to every screening. | | Brand Voice | Professional | The tone of the outreach emails the agent drafts: Professional, Casual, Technical, or Friendly. | | Personalization | High | How specific those drafts are: Low names the candidate and position only; High writes to this candidate and this position. | | Who can approve or decline the agent's proposals? | Managers and above | Who may approve or decline what the agent queues in Approvals: this app's administrators only, managers and above, or specific groups. Admins, HR admins, and recruiting app admins always can. Only people who can view candidate data can approve. | **Admin → AI Operations → Agent Settings**, Recruiting section: | Setting | Default | What it changes | |---|---|---| | Ask AI Agent | On | Whether the Recruiting Agent answers in Ask AI at all. | | Autonomous Operations | Off | Master switch for the 15-minute scan and every auto-action above. | | Approval Requirements: Outreach Emails from Ask AI | On | Ask AI saves every outreach email as a draft for a person to send. | | Approval Requirements: Interview Scheduling | Off | When on, Ask AI refuses to book and tells the user to schedule from the Interviews page. | | Min Qualification Score | 30 | Scores below this are recommended Decline. Nothing is declined automatically. | | Auto-Advance Threshold | 70 | Scores at or above this are recommended Advance. Nothing is advanced automatically. | | Scoring Weights (Technical / Experience / Education / Cultural Fit) | 40 / 30 / 20 / 10 | How the four part-scores blend into the overall score. Cultural Fit scores the candidate against your Company Culture & Values text. Must total 100. | ## 6. More help - **Recruiting Agent FAQ** — specific setup, permission, and operating questions - **Job Board App Overview** — where jobs and applicants are created and managed - Ask AI — the assistant answers questions about the Recruiting Agent from these articles. **Keywords:** recruiting agent, ai recruiter, candidate screening, screening score, candidate ranking, approval queue, autonomous operations, phone screen invite, rejection email, outreach email, interview scheduling, hiring pipeline, scoring weights, screening instructions, ai-agent-recruiting, ai_agent_recruiting, recruiting-agent --- # Recruiting Agent FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-13 Answers to common questions about asking, configuring and troubleshooting the Recruiting Agent. # Recruiting Agent FAQ Answers to the questions that come up while using and running the Recruiting Agent. --- ## Getting started ## How do I ask the Recruiting Agent something? Open Ask AI from the top navigation and type your question in plain English. To send the question straight to this agent, start it with `@recruiting`. For example: "show me the candidates in screening for the warehouse role". ## What can I actually ask it about? Open job postings, the candidates on them, AI screening scores, pipeline counts by stage, upcoming interviews, and market pay for a role. It works on the jobs and applicants already in Job Board. It keeps no candidate list of its own. ## Can it change things, or does it only look things up? Both, but every change is previewed first. Lookups run straight away. Writing is different — stage changes, contact-detail fixes, offer and outreach drafts, and interview bookings all show you exactly what will change. Nothing is written until you confirm. --- ## Permissions and access ## Why did it say I don't have permission to do that? The candidate tools are limited to recruiting staff. You qualify if any of these is true: 1. You are an administrator or an HR admin. 2. You are an app admin for Recruiting Agent, Job Board, Offer Manager or Interview Scheduler. 3. You are the recruiter, hiring manager or creator on at least one job posting. 4. Your Talent Hub setting for who can view candidate data includes you (managers and above by default). Everyone else is asked to go to a manager or admin. ## Why can I only see candidates for some of our jobs? You see candidates on the jobs where you are the recruiter, hiring manager or creator, plus any candidate you added yourself. Administrators, HR admins, Recruiting Agent app admins and anyone your Talent Hub candidate-data setting includes (managers and above by default) see every candidate in the business. ## "I'm interviewing someone next week — why can't I see it here?" Upcoming interviews sit behind the same recruiting-staff check as candidate data. Being named as an interviewer is not enough on its own. Open Interview Scheduler for your own calendar, or ask the recruiter on that job. --- ## Screening and ranking ## How does the AI score a candidate? It reads the resume against the job and returns one overall score out of 100, a recommendation, the candidate's strengths, and the gaps it found. The result is stored on the candidate, so asking for the score again does not re-run the analysis. ## Does re-screening someone overwrite their earlier score? Yes. Screening always recalculates and replaces the stored scores for that candidate. If you only want to read what is already there, ask to view the candidate's score instead of asking to screen them. ## Where do the screening weights and culture notes come from? An administrator sets them. Company Culture & Values and Custom Screening Instructions live on the Recruiting Agent's own Settings page. The four scoring weights — technical, experience, education and other — live in AI Operations, Agent Settings. They must total 100, or the save is refused. ## Can it rank everyone who applied for a job? Yes. Ask it to rank the candidates for a specific job and it returns them in fit order, each with a score, strengths and weaknesses. Name the job in your question — ranking runs against one posting at a time. --- ## Interviews, offers and emails ## "It keeps telling me to schedule the interview myself — why won't it do it?" Your workspace has interview scheduling set to require approval, and the agent will not book around that. Schedule it from the Recruiting Agent's Interviews page instead. An administrator can lift the requirement under Require Approval: Interview Scheduling in AI Operations, Agent Settings. ## Why did it say the candidate already has an interview? It refuses to double-book. Any upcoming interview counts, whether it was booked in Interview Scheduler or by the agent itself. It shows you those instead of creating another. ## Does it email candidates on its own? Not out of the box. Autonomous Operations is off by default, so the agent sends nothing on its own. In Ask AI, outreach is saved as a draft for a person to send while Require Approval: Passive Outreach is on, which it is by default. An offer letter is only ever drafted as text in the conversation; the offer itself is created, approved and sent in Offer Manager, under Offer Manager's own approval settings. ## Can I trust the salary numbers it gives me? Treat them as a starting point. Market pay analysis returns an AI-estimated band with its reasoning and a disclaimer about where the figures come from. The agent tells you to check the range against current market data before you use it. --- ## When something looks wrong ## "I pasted the candidate's email address — why couldn't it find them?" Candidates are looked up by name, and by the job they applied to when two people share a name. An email address or phone number is not a search term. Ask by the candidate's name, or by the ID number shown on their candidate page. ## I switched on an automatic action — why is nothing happening? Autonomous Operations is switched off. You can choose the auto-action switches at any time, but they only take effect once it is on. It is turned on in AI Operations, Agent Settings — not on the app's own settings page, which says whether it is on. --- ## Setup and limits ## How do I turn the Recruiting Agent on, and why can't my team see it? It requires a licence, and an administrator enables it for the business from Admin → Apps → All Apps. Enabling is only half the job. A newly enabled app stays admin-only until you publish it. Use Publish to users on the app's page, or publish it to specific groups instead. ## What does Autonomous Operations actually let it do? With it on, a background scan runs every 15 minutes. It can acknowledge new applications, invite high scorers to a phone screen, and decline low scorers. It can also push a stalled candidate to a recruiter. Each of those has its own switch, so you can enable them one at a time. ## How is autonomous activity capped? A new agent starts at the Probation trust level, where every action it wants to take is queued for a human first. The workspace also caps it at 50 autonomous actions a day. ## What happens if it starts getting things wrong? It pauses itself. Once more than 5% of its recent autonomous actions have failed, it stops acting until someone resumes it. It needs at least five actions before making that judgement. Three declined proposals within 30 days also push everything back to needing approval. --- ## More help - [Job Board](/help/articles/job_board_app_overview) — where jobs and applicants are created and managed - Ask AI — type `@recruiting` to send a question straight to this agent **Keywords:** faq, recruiting agent, candidate screening, candidate score, hiring pipeline, interview scheduling, offer letter, outreach email, autonomous operations, approval required, permissions, not showing, ai-agent-recruiting, ai_agent_recruiting, recruiting-agent --- # Report Agent App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 What Report Agent does, how to enable it, and the concepts an admin needs to configure data domains, saved reports, sharing, exports and scheduled delivery. # Report Agent ## 1. What it is Report Agent turns a plain-English question into a custom report over your own OneMango data. Someone asks "headcount by department" or "open tickets by status this quarter" in Ask AI, the agent picks the right area of data, runs the query, and answers with a table and a chart. The report can then be saved, refined, shared, exported, and put on a recurring schedule. The same data is reachable without the assistant: the app ships a visual report builder at **Apps → Report Agent → Reports**, where you pick a data domain, choose columns, filters, grouping and a chart type, and preview the result before saving. - **Enablement:** Report Agent requires a licence and the **Platform Standard** edition. It is disabled by default; an admin opts in per tenant from Admin → Apps → All Apps. There is no free tier and no automatic enablement on deploy. - **Who it is for:** managers, administrators, app admins for Report Agent, and app admins of an app whose data it reports on (who report on that app's data). An employee with no direct reports, no admin role and no app-admin grant cannot open the app or reach the agent in Ask AI — there is no self-service reporting view. - **What it is not:** Report Agent generates **reports and charts**, not dashboards. It has no dashboard-building tool. It is also not a replacement for an app's own analytics page — it is the cross-domain reporting surface used when no specialised analytics screen already owns the metric. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Report Agent**. The tenant must be on the Platform Standard edition or above; below that, every surface of the app — desktop, mobile and the Ask AI agent — refuses access. 2. Enabling is not the last step. A newly enabled app stays admin-only until you publish it to users from the app's page in the marketplace. 3. Go to **Apps → Report Agent → Settings**. Confirm the **Report Agent** switch at the top is on — it turns on both the Ask AI agent and the **AI Suggest** describe-to-fill bar inside the report builder. Both also need the Ask AI app enabled and visible to the user; where it is not, those AI features stay off whatever this switch says. 4. Scroll to **Data Sources** and review the data domains. Most are on as soon as the app is enabled; seven are off until you turn them on (see §3). Turning a domain off hides it from the builder, from the agent's routing, and from every saved report that uses it. 5. Decide the sharing and export posture: whether people may save reports at all, whether they may share them with each other, how many saved reports one person may keep, which export formats are allowed, whether an export needs identity re-verification, which team-scoped domains managers may report on, and who may schedule delivery to email addresses outside your organization. 6. Confirm it worked: open **Apps → Report Agent** as a manager. They should see the Dashboard, Reports and Scheduled Reports tabs; an admin or an app admin for this app additionally sees **Usage Analytics** and **Settings** under an Administration heading in the sidebar. **Silent-until-paired:** the Automation Hub's emergency stop is stored on the same configuration record this settings page writes, but it is pulled from **Admin → AI Operations → Automation Hub**. While it is engaged, scheduled reports are not generated or delivered even though every switch on the Settings page still reads "on" and every schedule still reads Enabled. Settings shows a read-only banner when the stop is engaged; it is released in the Hub, not here. Saved reports and Ask AI are unaffected. ## 3. How it fits together ### Data domains A **data domain** is one area of OneMango data the agent can report on — employees, attendance, shifts, leave balances, performance reviews, service-desk tickets, assets, OKR key results, and so on. Each has its own switch on the Settings page, its own keywords that a question is matched against, and its own canonical date field so "this quarter" means something honest for that domain (hire date for employees, ticket submission date for the service desk, effective date for compensation). Most are on the moment the app is enabled. **Seven are admin opt-in** and stay off until someone turns them on: Purchase Order Reports, Requisition Reports, Benefit Enrollment Reports, Benefit Plan Reports, Expense Reports, Expense Line Reports and Headcount Plan Reports. Two gates sit above the switch, and both can hide a domain the Settings page shows as on. A domain reads another app's data, so it is only available when **that app is enabled** for the tenant — compensation and merit are unreachable on a tenant that has not licensed Compensation Management. And each domain is reachable only by the people described under *Who can see what* below: outside the short list of team-scoped domains, that means a business administrator or an app admin for the app that owns the data. ### Who can see what Running the app and reading its data are separate questions: - **Business administrator** — reaches every enabled domain across the whole organization, can build **cross-entity (composite) reports** that join more than one domain, and manages the app (below). While **External delivery** is set to *Administrators only* (the default), only an administrator may own a schedule that emails an address outside the organization. - **App admin for Report Agent** — manages the app: Settings, Usage Analytics, every schedule, and every saved report on a domain they can reach, whatever its owner or visibility. The grant adds no data: what they can report on is what their own role reaches, plus the data of any app they are an app admin for. - **App admin of another app** — can open Report Agent and report organization-wide on the domains that read that app's data, and on nothing else beyond what their own role reaches. - **Manager** — someone holding the manager role, or with direct reports by the reporting line. They reach only the **team-scoped** domains — Employee, Timesheet, Timesheet Entry, Safety Incident, Safety Observation, Credential & License, Event Attendance and Training Session Attendance Reports — each bounded to their own team or locations. Someone with direct reports who does not hold the manager role reaches the three bounded by the reporting line: Employee, Event Attendance and Training Session Attendance. Each team-scoped domain has a **Managers can report on** switch on the Settings page, on by default. Every other domain is organization-wide data and is held back from managers. Everyone else has no access to the app at all. ### Saved reports, visibility and sharing A saved report stores the query definition, not a snapshot — running it re-reads live data. Each has a **visibility** of one of three values: - **Private (Only me)** — the default for a newly saved report. - **Shared (Selected users)** — visible to the specific people it was shared with. - **Public (everyone who can open its data source)** — visible to everyone who can use the app and report on that report's data domain. Each person who runs it reads only the rows their own access reaches — a manager's run of a public employee report covers their own team — and the report's page says whose rows your run reads. Administrators and app admins for Report Agent see every saved report on a domain they can reach, whatever its visibility. The **Enable Report Sharing** setting governs user-to-user sharing only; with it off, ordinary users see only the reports they own. A report cannot be shared with someone who could not open the app. Reports can be marked as favourites, duplicated, and used as starter **templates** — a starter library is seeded for the business the first time someone opens the builder. A report renders as a **bar, line, pie, doughnut or area** chart or stays a plain table; the chart type is stored on the definition, so the visual travels with the report into the builder, the Ask AI answer and a PDF export. ### Row budgets The number of rows a report reads depends on where it runs, and these caps cannot be raised ad hoc: | Where it runs | Rows read | |---|---| | Ask AI / builder live preview | 200 | | Running a saved report | 1,000 | | A scheduled delivery | 5,000 | | A full export | 10,000 | Separately, the **Preview Rows** setting caps how many rows are *displayed* in the Ask AI answer and in the builder's live preview — it does not cap a saved report's own results page. ### Scheduled reports A saved report can be put on a schedule that runs **daily, weekly, monthly or quarterly** at a chosen time in a chosen timezone. Delivery is one of three methods: - **Email** — the file is attached and sent to the recipient list. - **Webhook** — the run is POSTed to an HTTPS URL you supply. - **Download only** — the run is generated and stored in the app for later download. The output format is CSV, Excel, PDF or JSON, and a format an admin has switched off cannot be chosen for a schedule either. Recipients are governed, not freeform. An internal recipient must themselves be able to use Report Agent — a schedule cannot mail report data to someone who could not open the app. An address matching nobody in the tenant sends data off the platform entirely, so the **External delivery** setting decides who may schedule it: *Administrators only* (the default — a business administrator must own the schedule), *Off* (nobody), or *Anyone who can schedule a report*, optionally limited to a list of allowed email domains. A schedule the setting refuses is refused at save with the offending addresses quoted back. Sub-addressed aliases resolve to the mailbox owner, so `dana+weekly@acme.test` is treated as `dana@acme.test` and faces the same rule. A sweep runs every 15 minutes and fires any schedule that has come due. If a schedule fails five times in a row it is switched off automatically and its owner is notified. **SFTP delivery is not supported.** The option survives only as a carry-forward on legacy rows that already store it, so that editing an unrelated field on such a schedule does not silently flip it to Email; an SFTP run raises rather than delivering. Move those schedules to Email, Webhook or Download. ### The Ask AI agent In Ask AI the agent exposes six tools, all of them read-only: generate a report, refine the report currently on screen, export it, list report templates, get one template's details, and list your recent reports. The agent cannot delete a saved report, and it has no save command — saving is the button under the preview. Refining works on the report in the current conversation, and that context expires after 30 minutes. Exports the agent hands back are held for one hour and then discarded, so a link that has gone quiet just needs asking for again. ### Mobile `/m/apps/reporting-agent` is a **read-and-run surface only**. On a phone you can browse your reports, open one, run it and favourite it, and browse scheduled reports, open one, enable or disable it and run it now. There is no create, edit, delete or share on mobile — authoring is a deliberate handoff to the desktop app, and desktop and tablet visitors to the `/m/` path are sent back to the full app automatically. Saved reports and scheduled reports have **no `api/v1` surface**. Everything happens through the app, through Ask AI, or through scheduled delivery. ## 4. Running it ### Asking for a report in Ask AI 1. Open Ask AI and describe what you want — "headcount by department", "overtime hours by location last month". Starting the message with `@reporting` sends it straight to this agent. 2. The agent matches the question to a data domain, runs it, and answers with a preview table and a chart. 3. Say what to change — "filter to active only", "group by location instead" — and it rebuilds from the report on screen. 4. Click **Save** under the preview to keep it. The same row offers **Open Full Report** and **Refine**. ### Building a report by hand 1. Go to **Apps → Report Agent → Reports → New Report**, or start from a template in the picker. 2. Pick a data domain, then choose columns, filters, grouping and a chart type. The preview updates as you go. 3. Optionally use **AI Suggest** — describe the report in a sentence and the builder fills the fields in. It never submits the form for you, and it is only available while the Report Agent switch is on. 4. Save. The report lands in **Reports**, private to you until you share it. ### Exporting Open a report and choose a format. CSV, Excel, PDF and JSON can each be switched off for the whole organization. If **Require identity re-verification for exports** is on, you re-enter your account password (or your personal PIN, if set) before the download starts — and the same step applies to picking up a scheduled report's latest file. ### Scheduling a report 1. Save the report first — a schedule always runs a saved report. 2. Go to **Scheduled Reports → New**, pick the report, the cadence, the time and timezone, the delivery method and the format. 3. For email delivery, add recipients using the typeahead; it offers only addresses the save will accept. 4. Use **Run now** to prove the delivery path rather than waiting for the first occurrence, and the **next run** preview to confirm the cadence. ### Watching adoption and loading demo data **Apps → Report Agent → Usage Analytics** (admins and app admins only) shows total and conversational turns, distinct users, saved-report count, success rate against the sample size behind it, the most-used tools and when each was last used, the questions people actually ask, daily usage, and report-run outcomes by status — the one place a failed, timed-out or rejected run is countable. The Settings page also carries **Load Sample Data** and **Remove Sample Data**, which run the same generator the platform's own sample-data admin page uses, so the two surfaces cannot seed different data. ## 5. Settings All settings are at **Apps → Report Agent → Settings**, open to business administrators and to app admins for Report Agent and nobody else. ### Report Agent | Setting | Default | What it changes | |---|---|---| | Report Agent | On | Turns on the Ask AI agent **and** the AI Suggest bar in the report builder. Both also require the Ask AI app to be enabled and visible to the user. | ### Report Sharing & Collaboration | Setting | Default | What it changes | |---|---|---| | Enable Saved Reports | On | Lets users save reports. With it off, the builder's New Report door and the new-schedule form are both closed. | | Enable Report Sharing | On | Lets users share reports with each other. With it off, users see only reports they own; admins and app admins still see every report on a domain they can reach. | | Max Saved Reports per User | 50 | Blank or 0 means unlimited. Any other value must be between 5 and 500 — one outside that range is adjusted on save and the adjustment is reported back to you. | ### Export Options | Setting | Default | What it changes | |---|---|---| | CSV / Excel / PDF / JSON | On | Four switches, one per format. Each allows that format for both manual export and scheduled delivery. The JSON switch covers file downloads only — a webhook schedule's JSON payload is not affected by it. | | Require identity re-verification for exports | Off | Users must re-enter their account password (or personal PIN, if set) before downloading a report export or a scheduled report's latest file. Recommended when compensation, merit or succession domains are enabled — the page names which of those are currently on. | ### Performance & Limits | Setting | Default | What it changes | |---|---|---| | Preview Rows | 50 | How many rows appear in the Ask AI answer preview **and** in the report builder's live preview. Choices are 5, 10, 15, 20 and 50. It does not cap the results table on a saved report's own page. | ### External delivery | Setting | Default | What it changes | |---|---|---| | Scheduled reports to external email addresses | Administrators only | Who may schedule a report to an address that matches nobody in your organization: *Administrators only* (a business administrator must own the schedule), *Off* (nobody — a schedule that sends only outside the organization is paused, and one that also sends to members keeps running without its outside addresses), or *Anyone who can schedule a report*. Only a business administrator can change it; an app admin sees the current value. | | Allowed external email domains | Blank | Optional, comma-separated. When set, external recipients must be at one of these domains. Blank allows any domain. | ### Managers can report on One switch per team-scoped domain, each on by default. Turning one off stops managers who are not administrators from running that domain at all, even over their own team; administrators are unaffected. Each row says what "my team" means for that domain, and the domain must also be on under Data Sources. ### Data Sources (Data Domains) One switch per data domain, with a filter box and an "N of M enabled" readout. Disabling a domain hides it from the builder, from the agent's routing and from suggestions. All but seven default to on; the seven that default to off are Purchase Order, Requisition, Benefit Enrollment, Benefit Plan, Expense, Expense Line and Headcount Plan Reports. ### Set elsewhere The **emergency stop** for reporting automation is not on this page — it lives in **Admin → AI Operations → Automation Hub**, and while it is engaged no scheduled report is generated or delivered. This page shows it as a read-only banner and points at the Hub; it is deliberately not a second place the stop can be released from. ## 6. More help - **Report Agent FAQ** — specific setup and operating questions, limits, and troubleshooting. - **Ask AI** — how the assistant works across apps. Type `@reporting` to send a question straight to this agent. **Keywords:** report agent, reporting agent, custom report, saved report, scheduled report, report builder, data domain, report sharing, report export, csv export, excel export, pdf export, natural language report, ask ai reporting, usage analytics, report template, composite report, ai-agent-reporting, ai_agent_reporting, report-agent --- # Report Agent FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common questions about running, sharing, exporting and configuring reports with the Report Agent. # Report Agent FAQ Answers to the questions that come up while running and administering the Report Agent. --- ## Getting started ## How do I ask for a report? Open Ask AI and describe what you want in plain English — "headcount by department", "open tickets by status this quarter". Start the message with `@reporting` to send it straight to this agent. No query language or column names are needed. ## What can I build a report on? Around fifty areas of OneMango data. They cover: 1. People — employees, departments, separations, promotions, onboarding. 2. Time — attendance, timesheets, shifts, leave and leave balances. 3. Talent — performance, OKRs, competencies, succession, feedback, recruiting. 4. Pay — compensation changes, merit cycles and merit calculations. 5. Operations — Service Desk tickets, forms, tasks, inspections, safety, surveys, recognition, assets, training and credentials. ## Can I change a report after it's generated without starting over? Yes. Say what to change — "filter to active only", "group by location instead" — and it rebuilds from the report on screen. There has to be a report in the current conversation first, otherwise it asks you to generate one. ## How do I keep a report the agent just made? Click Save underneath the preview. The same row also offers Open Full Report and Refine. There is no save command in chat, so asking the agent to save it does nothing — use the button. ## How do I delete a saved report? From the Reports page inside the Report Agent app. The agent cannot delete reports and will direct you there. --- ## Exports and scheduling ## Which formats can I export to? CSV, Excel, PDF and JSON. An administrator can switch each of the four off for the whole organization under Export Options. When a format is switched off, the agent tells you that format is not enabled for your organization. The JSON switch covers file downloads only; a webhook schedule's JSON payload keeps flowing. ## "The download link the agent gave me stopped working" — why? Export links are deliberately short-lived. The generated file is held for one hour and then discarded. Ask for the export again to get a fresh link. ## Why am I being asked to verify my identity before an export? Your administrator has switched on Require identity re-verification for exports. It applies both to downloading a report and to picking up a scheduled report's latest file. It is off unless someone turns it on. ## Can a report run and be delivered on a schedule? Yes. Save the report first, then add a schedule: daily, weekly, monthly or quarterly. Each run can be emailed, sent to a webhook, or just stored in the app for download, in CSV, Excel, PDF or JSON. Schedules are set up in the app, not through chat. --- ## Limits ## How many rows do I actually get? It depends on where the report runs. In Ask AI it reads up to 200 rows. Running a saved report reads up to 1,000, a scheduled delivery up to 5,000, and a full export up to 10,000. ## Why does the chat show only a handful of rows when the count is much higher? The chat shows a preview, not the whole table. An administrator sets how many rows appear, under Preview Rows on the Report Agent Settings page. The choices are 5, 10, 15, 20 and 50, and it is 50 out of the box. Use Open Full Report or export to see the rest. ## Is there a cap on how many reports I can save? Yes, 50 per person out of the box. An administrator can set anything from 5 to 500 under Max Saved Reports per User, or leave it blank for unlimited. Once you hit the cap you are asked to delete an existing report first. --- ## Permissions and access ## "Why doesn't the Report Agent show up for me at all?" It is limited to managers, administrators and app admins. Someone with no direct reports, no admin role and no app-admin grant cannot open the app or reach the agent in Ask AI. There is no employee self-service view, so ask a manager or an administrator to run the report you need. ## I'm a manager — why can I only run a few kinds of report? Most areas of data are organization-wide, so they are held back to administrators and to the app admins of the app that owns the data. Managers get the team-scoped areas — Employee, Timesheet, Timesheet Entry, Safety Incident, Safety Observation, Credential & License, Event Attendance and Training Session Attendance Reports — each covering only their own team or locations. If you have direct reports but not the manager role, you get Employee, Event Attendance and Training Session Attendance. An administrator can also switch any of these off for managers under Managers can report on. ## Why is compensation missing from the reports I can run? Compensation and merit reports read organization-wide pay data, so they are not team-scoped. You need to be a business administrator or an app admin for Compensation Management, and Compensation Management has to be enabled for your organization. ## Who else can see a report I save? Only you, unless you share it. Saved reports start as Private (Only me); you can switch one to Shared (Selected users) or Public (everyone who can open its data source) — public means everyone who can use the app and report on that report's data area, and each of them sees only the rows their own access reaches. Administrators and app admins for this agent can see every saved report on a data area they can reach, either way. --- ## When something looks wrong ## "It says it couldn't find a report type for what I asked" — what now? Name what you want counted and how to break it down — "tickets by status this quarter" rather than "how are we doing". The agent matches your wording to a data area. Nothing matches if that area is switched off for your organization, or is out of reach for your role. --- ## Setup ## How do I turn the Report Agent on for my organization? It requires a licence and the Platform Standard edition, and an administrator enables it per business from Admin → Apps → All Apps. Enabling is not the last step. A newly enabled app stays admin-only until you publish it, with Publish to users on the app's page. ## Which data areas are off unless I turn them on? Purchase Order Reports, Requisition Reports, Benefit Enrollment Reports, Benefit Plan Reports, Expense Reports, Expense Line Reports and Headcount Plan Reports. Everything else is on once the app is enabled. Each area has its own switch under Data Sources on the app's Settings page. ## How do I stop people sharing reports with each other? Switch off Enable Report Sharing under Report Sharing & Collaboration on the Settings page. With it off, people see only the reports they own themselves; administrators and app admins for this agent still see every report on a data area they can reach. --- ## More help - [Ask AI](/help/articles/ask_ai_app_overview) — how the assistant works across apps - Ask AI — type `@reporting` to send a question straight to this agent **Keywords:** faq, report agent, custom report, saved report, scheduled report, export, data domains, row limit, preview rows, report sharing, permissions, not showing, ai-agent-reporting, ai_agent_reporting, report-agent --- # RFP Desk App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-14 What RFP Desk is, how the bid/no-bid assessor and the response drafter fit together, and what an admin sets up before the team answers its first RFP. # RFP Desk ## 1. What it is RFP Desk handles inbound solicitations — RFPs, RFIs, and security questionnaires your company receives. It answers two questions in order: should we bid on this, and if so, how do we write the response without re-deriving answers we already have. Drafting reuses your approved answers first, cites your own reference documents second, and marks anything it cannot support as needing a human — it never invents a claim. - **Enablement:** licensed and opt-in. An admin enables it in Admin → Apps → All Apps and publishes it to the people who work on bids. Subject-matter experts who only answer routed questions receive those as ordinary Tasks and do not need the app published to them. - **What it is not:** the buy side. Issuing RFQs *to your vendors* and scoring their responses is Supplier Hub. RFP Desk is for solicitations where you are the one responding. It also never sends anything to a buyer — export and submission are always human actions. ## 2. Standing it up 1. Go to **Apps → RFP Desk**. Everyone sees **Dashboard**, **Answer a Question**, and **Responses**, and **Bid / No-Bid** while the assessor is on and they may run assessments (an admin can narrow that under **Settings → Permissions**); contributors also see **Answer Library**, **Reference Library** and **Mine a Document**; app admins also see **Analytics** and **Settings**. 2. Go to **Settings** and open **Set up bid profile**. Fill in **What we can do** — the plain-prose description of what you deliver, certifications you hold, and constraints you can't move. The scoring rubric and the **How we write** style guide come prefilled with working defaults; add walk-away rules for terms that force a no-bid. **Without a bid profile, an assessed RFP is shredded into requirements but reports no score** — the Settings page shows a "Not set up" badge until one exists. 3. Seed the two libraries. In **Answer Library**, bulk-import an existing answer spreadsheet, or use **Mine a Document** to extract question/answer pairs from a past submission (you pick which candidates are saved; the document itself is not kept). In **Reference Library**, upload the documents drafting may quote — the security whitepaper, product datasheets — or index pages of your public website by URL. 4. Confirm it works: **Load Sample Data** on the Settings page seeds a sample bid profile and starter answers so you can try the assessor and the drafter before entering your own. Remove it from the same place when done. An empty setup still behaves honestly: with no libraries, every drafted section comes back marked **Needs input** rather than filled with invented text. The setup steps above are what turn those gaps into answers. ## 3. How it fits together **Two libraries, two levels of trust.** The **Answer Library** holds approved question-and-answer pairs — wording a human signed off, reused as-is. The **Reference Library** holds source documents; drafting synthesizes from them and attaches a citation to the document and section it used. They are not interchangeable: a library answer is your standing claim, a reference document is material a claim can be built from. Both are curated by RFP Desk contributors and app admins because both end up in front of buyers. **The grounding ladder.** Every drafted answer is produced the same way, on every surface: first an approved library answer, then your capability profile and reference documents (with citations), and if neither supports the question, the section is marked **Needs input** with a note about what a human must supply. Each section shows its grounding — for example **Reused from library** or **From your documents** — so a reviewer knows how much to trust the text. Worked example: "Describe your SOC 2 posture" finds the approved SOC 2 answer and reuses it. "Describe your approach to data residency" finds no approved answer, so it drafts from the uploaded security whitepaper and cites it. "Provide three healthcare references" matches nothing and comes back **Needs input**. **A response's life.** A response moves **Draft → In review → Approved → Submitted**, with **On hold** and **Declined** as side exits. Approval is refused while any section still needs input, any section is unreviewed, a Legal, Security, Commercial or HR section lacks that specialist's sign-off, or any required deliverable is unticked. Content locks at Approved; reopening for edits moves it back to Draft and revokes the approval. Review is per section — any team member can mark a section reviewed, and editing its text withdraws that review automatically. **Who does what.** Anyone the app is published to can assess RFPs, import questionnaires, answer questions, and review sections. Curation — the Answer Library, the Reference Library and document mining — is for RFP Desk contributors and app admins; the bid profile, Analytics and Settings are for app admins only. Approving, submitting or declining a whole response, and reopening one that is approved or submitted, is limited to the response's responsible person or an app admin. **Boundaries.** A routed question becomes a Task in the Tasks app, with the question and an answer box on the task itself; answering it fills the section and closes the task. Recording a bid decision can open a pursuit in Mango GTM when that app is enabled — the deal then lives in GTM, the response stays here. Widening drafting to all company knowledge (wikis, SOPs, policies, Drive) is a Settings decision, not the default — see §5. ## 4. Running it ### Assess an inbound RFP 1. Open **Bid / No-Bid** and paste the RFP text or upload the document. 2. The report lists every extracted requirement with a mandatory flag, judges each against your capability profile, and computes the fit score from your rubric. Two things override the score outright: an unmet mandatory requirement, or a term your walk-away rules refuse. 3. From the report you can draft a response or record the decision. ### Answer a questionnaire 1. Open **Responses** and import the buyer's Excel or Word questionnaire. Questions the Answer Library already covers are filled in automatically; the rest are marked. 2. Work the marked sections: edit directly, re-draft with guidance, or apply a suggested library answer. 3. Export writes your answers back into the buyer's original file, cell for cell. ### Route a question to the person who knows 1. On any section marked **Needs input**, pick the expert under **Send to** and choose **Ask them**. 2. They get a Task in their inbox with the question and an answer box — no RFP Desk seat needed. People who can open the response also get a link to it in RFP Desk. It works on a phone too. 3. When the answer is saved, the section's flag clears and the task completes itself. ### Finish and send 1. Have the team mark each section **Reviewed**. 2. Tick off the deliverables checklist — the forms and certificates the buyer requires you to attach, read out of the solicitation at import. 3. Move the response to **In review**, then **Approved**, then download: the buyer's filled workbook, or a Word document in your branding with AI-drafted opening sections (cover letter, executive summary) you can add and review like any other section. ### Keep the library true 1. Answers show their owner and last-reviewed date; past the review window (twelve months unless an admin changes it) they are flagged as stale wherever they are reused, and owners get a Monday reminder to re-confirm. A bid still being written that reuses an answer which has since been archived says so on the section, so you rewrite it before sending. 2. **Mark reviewed** confirms an answer is still true without editing it. 3. Winning a bid offers its approved answers back as library candidates for an admin to accept — nothing enters the library without a human choosing it. ## 5. Settings All under **RFP Desk → Settings** (app admins only). | Setting | Default | What it changes | |---|---|---| | Bid / No-Bid Assessor | On | The Bid / No-Bid tab: requirement extraction, fit scoring, and the terms screen. | | Bid Fit agent in Ask AI | On | Lets Ask AI assess an RFP, explain a score, and maintain the profile and walk-away rules conversationally. | | Responses & Answer Library | On | The Responses tab, Answer a Question, both libraries, and the RFP Response agent. Independent of the assessor. | | Also ground on all company knowledge | Off | Widens drafting beyond the Reference Library to wikis, SOPs, policies, Sites, Drive, Contracts, and AI Notes. Leave off unless you have reviewed what that content says — drafts go to buyers. | | Warn this many days ahead | 3 | How far before the buyer's deadline the daily reminder starts for the responsible person, the collaborators and anyone who still owes an answer to one of its questions. Set to 0 to turn deadline reminders off. | | Months until an answer goes stale | 12 | How long an approved answer stays current after it was last reviewed or edited. Drives the stale badge, the Needs review filter, the drafter's warning and the weekly ask. | | Ask owners to re-confirm stale answers each Monday | On | The weekly ask to each answer's owner (at most five per owner per week). Turning it off keeps the stale flags and only stops the chase. | | Mine won bids for reusable answers | On | When a bid is marked won, reads it with AI and offers its answers for the library. Nothing is banked automatically. Spends AI credit each time. | | Who hears about answers harvested from a win | The bid's own people | Adds a standing group; only its members who can curate the Answer Library are told. | | Permissions | — | Who may run Bid / No-Bid assessments and who can see every response, not only the ones they work on. | Turning **Responses & Answer Library** off also pauses the deadline reminders, the weekly stale-answer ask and win harvesting until it is turned back on. The bid profile's rubric weights, walk-away rules, and **How we write** style guide are edited on the **Bid Profile** page rather than Settings. The style guide starts with a built-in house style; leaving it blank falls back to that same default. ## 6. More help - **RFP Desk FAQ** — specific setup and operating questions, limits, and troubleshooting - Ask AI — the Bid Fit and RFP Response agents answer questions about RFP Desk from these articles, assess RFPs, and draft responses directly in chat. **Keywords:** RFP response, bid no-bid, security questionnaire, answer library, reference library, walk-away rules, capability profile, needs input, questionnaire import, RFP deadline reminders, rfp-desk, rfp_desk --- # RFP Desk FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-14 Answers to common setup and operating questions about RFP Desk — scoring, questionnaire imports, the answer library, approvals, and deadline reminders. # RFP Desk FAQ Answers to common setup and operating questions about RFP Desk. For what the app is and how to set it up from scratch, see the [RFP Desk Overview](/help/articles/rfp_desk_app_overview). --- ## Setup ## Why doesn't my RFP assessment show a score? There is no bid profile yet. Without one, an assessed RFP is still shredded into requirements, but nothing exists to judge them against, so no score is reported. Go to **Settings → Set up bid profile** and fill in **What we can do**; the rubric comes prefilled. ## Do I have to fill the libraries before importing a questionnaire? No — the import works immediately, but with empty libraries every question comes back marked **Needs input** because there is nothing approved to answer from. Seed the Answer Library first (bulk import or **Mine a Document**) if you want the first import to auto-fill. ## Who can curate the libraries, and who can just answer questions? Anyone the app is published to can assess RFPs, import questionnaires, answer and review sections, and use **Answer a Question** (an admin can narrow who may run assessments under **Settings → Permissions**). The Answer Library, Reference Library and **Mine a Document** are for RFP Desk **contributors** and app admins. The bid profile, Analytics and Settings are for RFP Desk app admins only. --- ## Permissions and access ## Why can't my teammate see the Answer Library tab? The library is curated content that future responses reuse as already-approved, so only RFP Desk contributors and app admins see it — everyone else still benefits from it through drafting. If your teammate should curate, give them the **Contributor** role for RFP Desk (the **Admins & Contributors** card on RFP Desk's page in the admin app marketplace). Contributor covers the Answer Library, Reference Library and Mine a Document without handing over Settings, the bid profile or deleting documents, which stay with app admins. --- ## Day-to-day ## Why did every section say "Needs input" right after my import finished? Large questionnaires (more than 25 questions) create their sections instantly and fill in library matches in the background a few moments later. Reload the page — auto-filled sections appear with their library grounding. If they still show as gaps after a minute, the library genuinely had no match for them. ## Why does a section say "Needs Sales (pricing)" instead of "Needs input"? Because it is a pricing question — per-seat rates, discounts, payment terms, fees, usage caps — and no answer library or reference document can answer it: Sales has to build and approve the figures. RFP Desk classifies these at import and again when it drafts, marks them **Needs Sales (pricing)** with a placeholder naming what Sales must supply, and never invents a number. They are counted separately from knowledge gaps everywhere (the response header, the filter pills, the import summary, the response list) so a subject-matter expert is not chased for a price. Sales fills in the **Pricing** card on the response page — line items, term, discounts, a not-to-exceed for usage items, plus assumptions and approvals — then uses **Insert pricing table into section** on each pricing question. Every figure is an estimate pending your quoting tool, and each pricing section needs a Commercial sign-off before the response can be approved. If the classifier missed one, tick "Pricing question" on the section. Ask AI will tell you a worksheet exists and how many pricing sections there are, but never reads out the figures. ## Why was my questionnaire rejected with "No questions found"? The import needs a table with a header row naming a **Question**, **Requirement**, or similar column — in an Excel sheet or a Word table. An RFP written as prose has no cells to fill: assess it on the **Bid / No-Bid** tab instead, then draft a response from the assessment and export it as a Word document. ## Why did saving a new library answer warn me about a similar existing one? The library spotted an existing answer that appears to cover the same question in different words. Two entries for one question means drafting picks between them arbitrarily, so the warning shows the existing answer side by side. Update that one if it is the same question; if yours is genuinely different, submit again and it saves. ## How do I make the current security whitepaper win over older documents? Edit its entry in the **Reference Library** and tick **Authoritative source for its subject**. When sources disagree on a fact, the authoritative document wins, and the draft flags the discrepancy for review instead of blending the claims. ## What does "Also ground on all company knowledge" actually expose? It widens drafting beyond the curated Reference Library to wikis, SOPs, HR policies, Sites, Drive files, Contracts, and AI Notes. Each source respects the drafter's own permissions, but none of that content was written to be quoted to a buyer — which is why the switch is off by default. Review what that content says before turning it on. ## Why can't I approve this response? Approval is refused until the response is complete, and the message names what is in the way: it has no questions yet, a section still needs input, a section is still unreviewed, a section classed Legal, Security, Commercial or HR still needs a sign-off from that specialist, or a required deliverable hasn't been ticked off. Clear the named blocker and approve again. ## Who is allowed to approve or submit a response? The response's responsible person, or an RFP Desk app admin — and the same goes for declining it and for reopening an approved or submitted response for edits. If no responsible person is set, anyone can move it. Reviewing individual sections is deliberately open to any team member — sign-off on the whole document is what stays gated. ## When do deadline reminders go out, and who gets them? Once a day, at 07:00 your organization's time, to the responsible person, the collaborators on the response and anyone who still owes an answer to one of its questions (or to its creator when none of them is set). They start a configurable number of days before the buyer's deadline — 3 by default, settable from 0 to 60 — and continue for overdue and approved-but-not-sent responses. Nobody receives more than 5 in one sweep. Set the number to 0 in **Settings** to turn them off. Each reminder ends with the next thing that stands in the way, in the order the **Approve** button checks them: questions that still need an answer, sections waiting for review, a specialist's sign-off, then a required item on the **What to submit** checklist that nobody has ticked. Someone who owes an answer is told about their own question. When nothing stands in the way it names the next step instead — send it for review, resume it if it is on hold, approve it, or, once it is approved, send it and mark it submitted — and says whose step it is when it isn't yours. ## How do we record that we won a bid? Open the submitted response and choose **We won** or **We lost** in the outcome card above the response details. The responsible person or an RFP Desk app admin can record it (anyone working on the response can when no responsible person is named), and can change or clear it later. A win offers the response's reviewed answers up for the answer library: whoever your **Settings** name is told when candidates are ready, and someone still picks what is banked. If your organization uses Mango GTM, a bid with a proposal takes its outcome from that proposal instead. --- ## When something looks wrong ## "I got a task saying 'RFP answer needed' — what am I supposed to do?" Someone routed you an RFP question only you can answer. Open the task: it shows the buyer's question with an answer box. Type your answer there and send it — you don't need to know anything else about the response, and the task completes itself once the answer is saved. If you can open RFP Desk, **Open in RFP Desk** on the task takes you to the section too. ## "I answered the question but the task is still in my list" The answer has to be sent from the task's answer box (or saved on the response section). If you replied in the task's comments or an email instead, the section is still empty — open the task and send the answer there. The task closes on its own when the section's gap clears. ## "Why can't I edit a section any more?" The response has been approved or submitted, which locks its content — otherwise an approval could be changed out from under itself. Move the response back to **Draft** (this revokes the approval) and edit; then it goes through review again. ## "The export didn't include one of our answers" Two possibilities. Opening sections — cover letter, executive summary — are never written into the buyer's questionnaire file by design; they appear in the Word document export. And if the buyer's file was revised after import, a section whose original cell no longer exists can't be placed — re-import the revised file to realign. --- ## Licensing and limits ## Does RFP Desk need a licence, and who can turn it on? Yes — it is licensed and off by default; a business admin enables it from the Apps Marketplace and publishes it to the bid team. Subject-matter experts who only answer routed questions do not need it published to them: their questions arrive as ordinary Tasks. ## What are the limits I should know about? - Questionnaire import: Excel or Word, up to **10 MB** and **500 questions** — a truncated import says so on screen. - Drafting from an assessment: up to **30 requirements** per pass. - Document upload on the Bid / No-Bid tab: up to **10 MB**. - Mining a past submission: PDF, Word, or text up to **20 MB**; very long documents are read up to a cap and the results say when they were cut short. ## How long until a library answer counts as stale, and what resets it? Twelve months by default (an admin can set anywhere from 3 to 36 under **Settings → Answer freshness**) after it was last reviewed — or, for an answer nobody has marked reviewed yet, last edited. **Mark reviewed** resets the clock without changing the text. Editing an answer that has been reviewed before does not: correct it, then mark it reviewed. Winning a bid deliberately does not either — a buyer accepting your bid is not a person confirming the claim is still true. Owners of stale answers are asked about them in their inbox each Monday (08:00 UTC), at most monthly per answer and stopping after six months if nobody acts; the ask leaves their **Needs you** as soon as they mark the answer reviewed or archive it. --- ## More help - [RFP Desk Overview](/help/articles/rfp_desk_app_overview) - Ask AI — the Bid Fit and RFP Response agents answer RFP Desk questions from these articles. **Keywords:** faq, RFP score missing, questionnaire import, needs input, answer library, stale answer, walk-away rules, approval blocked, deadline reminders, reference library, rfp-desk, rfp_desk --- # Safety Hub App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-14 How to set up and run Safety Hub — incident reporting and investigation, the shared corrective-action register, safety observations, toolbox talks, certification tracking, permits to work, contractor pre-qualification, emergency alerts with muster, the public safety portal, and OSHA/WCB determinations. # Safety Hub ## 1. What it is Safety Hub is the workplace safety app. It records incidents and runs their investigations, tracks corrective actions in a register shared with Inspections, collects safety observations, schedules toolbox talks, tracks required certifications, issues permits to work, pre-qualifies contractors, dispatches emergency alerts with a muster roll-call, and produces OSHA (US) and WCB (Canada) determinations. A public portal at `/safety` lets anyone report a hazard without logging in. - **Enablement:** Safety Hub requires a licence. An admin enables it per business from **Admin → Apps → All Apps**; it is never turned on automatically. - **What it is not:** Safety Hub is not Lone Worker (timed check-ins and SOS for people working alone — Lone Worker can open a Safety Hub incident, but the alert engines are separate). It is not Inspections (checklists and field audits — the two apps share one corrective-action register). It is not Compliance Hub — the risk register and legal register live there, and Compliance Hub reads Safety Hub records as evidence. It is not the Broadcasts app — emergency alerts are composed and sent inside Safety Hub. ## 2. Standing it up 1. **Enable the app** at **Admin → Apps → All Apps**. Grant access to the people who should see it through Access Management; anyone the app is published to can report incidents and observations. 2. **Create locations** at **Admin → Locations**. Incidents, observations, permits and talks are tied to a location. A manager sees safety records only at the locations they manage, so a record with no location is invisible to plain managers. 3. **Choose modules** at **Safety Hub → Admin → Settings → Modules**. Eight toggles: Incidents, Observations, Toolbox Talks, Certifications, Emergency Alerts, Contractor Pre-qualification, Permits to Work, and OSHA Compliance (US) under **Compliance**. All are on by default. **WCB Compliance (Canada)** is off by default. Each module's sidebar entries appear only while its toggle is on. 4. **Decide who sees every site and who may send alerts** under **Settings → Who Can Do What**. *Who can see safety records at every site?* defaults to Safety Hub app admins. *Who can send a Safety Hub emergency alert?* defaults to managers and admins. Pick a group for either to hand the capability to an EHS team without making them business admins. The alert Bookings sends from its evacuation dashboard to everyone checked in to a building is a separate setting, in Bookings → Settings. 5. **Define certification requirements** at **Safety Hub → Admin → Certification Requirements**. A requirement alone shows nothing: compliance is computed against certifications employees actually hold, which come from certified skills in Skills & Credentials or training records from Training Connect. Set up both sides or every roster stays empty. 6. **Assess contractors before their first permit.** With *Require a current pre-qualification before issuing a contractor permit* on (the default), a permit naming a contractor cannot be issued until that contractor has an approved or conditional assessment under **Team → Contractors**. Permits for your own employees are unaffected. 7. **Open the public portal, if you want one.** The `/safety` portal needs two things: Safety Hub enabled, and the Safety Hub portal switched on in the **Portals** app. Safety Hub's own Settings page shows a **Public Hazard Portal** card with *Open portal settings* and a *Close the public portal* button — it can close the portal but never open it. Fill in **Public Emergency Contacts** and the **Emergency number** (shown as 911 when blank), and mark the knowledge-base articles that should be public. 8. **Leave autonomous operations off until you are ready.** *Enable Autonomous Safety Operations* is off by default. Turning it on does nothing by itself: the **AI Console** (linked from the Settings page) also needs a trust level, and on probation every proposed action waits for your approval. 9. **Confirm it worked.** A manager landing on Safety Hub sees the dashboard tiles (days without injury, incidents this month, open investigations, permit tiles, expiring certifications). An employee is taken straight to **Submitted by Me**. On mobile, employees see their own submissions, permits and alerts. ## 3. How it fits together **Incident vs observation vs near miss** — An *incident* is a formal event record with one of eight types: Injury, Near miss, Property damage, Environmental, Security, Vehicle accident, Equipment failure, or Other. It carries a severity (Low, Medium, High, Critical), an investigation, OSHA/WCB determinations and corrective actions. An *observation* is a lightweight sighting — Positive, At-risk or Near miss — with an optional follow-up and no investigation. "Near miss" therefore exists on both sides, and the public portal files a Near Miss as an observation, not an incident. Other is the neutral landing type for reports that fit nothing else; reclassify it once reviewed. **Investigation vs corrective action** — High or Critical incidents, and every Injury, require an investigation. The investigator records findings and completes it; completion is one-way. Corrective actions are separate rows in the **Corrective Actions** register, shared with Inspections and Leader Rounds, each with a type, priority, due date and assignee. An incident cannot close while its investigation is open. When *Require Effectiveness Verification Before Closing Over Completed Actions (ISO 45001)* is on, it also cannot close while a completed action is awaiting the **Verify** step — which must be done by a manager who is neither the assignee nor the person who marked the action completed. **Requirement vs held certification** — A *certification requirement* says who must hold what, scoped by role, location, department or job title, with a validity period and reminder lead. A *held certification* is the employee's certified skill or training record. Compliance is the match between the two; the **Training Gaps** view separates "expired" from "never certified". **Alert vs muster check-in** — An *emergency alert* is the message you dispatch over In-app, Email, Push, SMS and Voice. Its recipient response is either *Require acknowledgement* (recipients confirm they saw it) or *Require safety check-in* — the muster, where each recipient answers "I'm safe" or "I need help" and the roster shows who has not answered. "I need help" pages responders: the alert's author plus the configured notification group; if none of them can be reached, the Safety Hub app admins, else the business administrators — never the person asking. When nobody can be paged, the person is told to call their manager or emergency services. **Permit stored status vs what the board shows** — A permit's status is Draft, Requested, Approved (shown as *Issued*), Suspended, Closed, Cancelled or Expired. *Active* and *Past end time* are not statuses: an issued permit is Active inside its work window and Past end time once the window closes. Nothing flips a permit to Expired until an hourly check finds it 24 hours past its end without a close-out — and an expired permit still counts under *Past end time* until it is closed out, for 30 days after its end (older ones stay under *All*, where they can still be closed). The same check cancels a request whose work window ended before anyone issued it, and tells the requester. **Pre-qualification current vs lapsed** — An assessment decided Approved or Conditional is *current* until its *Valid until* date. Past that date it shows a **Lapsed** badge and no longer satisfies the permit gate; a daily check then moves it to Expired. Conditional counts as current, with the conditions recorded on the assessment. **"Safety officer" is not a role** — Where Safety Hub adds "safety administrators" to a notice, it picks them in one of three ways. High/Critical incident alerts, at-risk and near-miss observation alerts and overdue corrective-action escalations add the site's safety lead (the Safety Lead contact named on the location, if they are a manager or a Safety Hub app admin); when the site names none, or the record has no site, they add up to 5 business admin accounts instead. Expired-certification notices (beside the person's manager), permit approval requests (beside the site's managers) and contractor pre-qualification reminders with no reviewer add up to 5 business admin accounts. When the AI agent escalates a High/Critical incident on its own, it notifies every active business admin. To name a real EHS team, set *Route incident and hazard alerts to this group* under **Settings → Notifications**. **My, Team and Admin zones** — Everyone gets the My zone: Report Incident, Submit Observation, Submitted by Me, My Certifications, My Alerts, My Toolbox Talks, My Corrective Actions, My Permits and Knowledge Base. Managers add the Team zone: Emergency Alerts, Incidents, Corrective Actions, Observations, Campaigns, Toolbox Talks, Topic Library, Certifications, Permits to Work, Contractors, OSHA (US), WCB (Canada) and Analytics. Admins and Safety Hub app admins add Alert Templates, Certification Requirements and Settings. Within the Team zone a plain manager is site-scoped; admins, app admins and anyone granted *Who can see safety records at every site?* see everything. **Worked example: a hot-work permit for a contractor.** A supervisor opens **My Permits**, clicks *Create Draft Permit*, picks *Hot work*, describes the work, sets the site, the *Work starts* / *Work ends* window (14 days at most) and the *Contractor (if external)*, and ticks the hazards. They click *Request approval*; the permit becomes Requested and authorisers get an in-app notification. Another manager for that site opens it and confirms all six precautions — from *Combustibles removed or shielded within 11 m (35 ft)* to *Fire watch during work and 60 minutes after* — then clicks *Confirm precautions and issue permit*. If the contractor has no current pre-qualification and the gate is on, that click is refused with the contractor's name. Once issued, the board shows it as Active during the window. At the end of the shift either party clicks *Close out*, ticks *Work complete or stopped; area inspected and left safe*, adds close-out notes and clicks *Close permit*. The record then reads "Area left safe". **Worked example: a contractor assessment.** A reviewer answers the 15-question questionnaire for a roofing contractor, answering Yes to everything except *Workers' compensation / employer's liability cover in force*. The score is 91% — normally a Low suggestion — but the suggested tier is capped at High, because a No on any 3-point Performance or Insurance question always caps it. The reviewer records the decision as Conditional, keeps High risk, sets the conditions and a *Valid until* date defaulting to 12 months out. ## 4. Running it ### Investigating an incident 1. Go to **Safety Hub → Team → Incidents**. Filter by status, severity, type or location. 2. Open the incident. If *Auto-assign Investigators* is on, an investigator was assigned at report time — the location's manager, else a business admin, else any manager — with a deadline of *Investigation Deadline (days)* after the event. Assign or change the investigator here if needed. 3. The investigator records findings and completes the investigation. Add corrective actions; they appear in the shared register with due dates and assignees. 4. Determine OSHA recordability (or WCB reportability) from the incident. A fatality is always recordable; otherwise an injury with days away, restricted work, medical treatment beyond first aid, loss of consciousness or a significant injury is. A case number is issued and the entry appears on the 300 Log. 5. Close the incident. Closure is blocked while the investigation is open or, with the ISO 45001 policy on, while an action awaits verification. Use *Print report* or the *Evidence pack* when an auditor asks. ### Running a toolbox talk 1. Go to **Team → Toolbox Talks** and schedule a talk: title, a topic from the **Topic Library**, location, facilitator, time, duration (prefilled from *Default Talk Duration*) and expected attendees. Attendees are invited, and reminded on the morning of the talk, when *Send Toolbox Talk Invitations, Reminders and Missed-Attendance Notices* is on. 2. The facilitator starts the talk and records attendance. With *Require Attendance Signatures* on, an unsigned roster is refused. Employees can self-record their own attendance on mobile. 3. Complete the talk with post-meeting notes, and print the attendance sheet if you keep paper records. The next morning, absentees' managers and the facilitator are told who was missing — the same switch covers this notice, so turning it off also stops it. ### Issuing a permit to work 1. Go to **Team → Permits to Work**. The board counts permits awaiting approval, active now and past end time; the default filter shows open permits — draft, requested, issued and suspended. 2. Open a Requested permit, confirm every precaution for its type, add *Authoriser's notes* and click *Confirm precautions and issue permit*. Precautions can only be ticked by managers. 3. Use *Suspend* (with a reason — work must stop; the requester is told) and *Resume* while the work is paused — Resume is refused once the permit's end time has passed, or while a contractor's pre-qualification is not current (when Settings requires one). The requester, the authoriser or a Safety Hub manager at the permit's site can close it, while it is Issued, Suspended or Expired (an expired permit still owes its close-out); a permit left open past its end time is nudged, then expired 24 hours later. Cancelling a permit notifies the requester, the authoriser and the crew. ### Assessing a contractor 1. Go to **Team → Contractors** and click to open an assessment for the vendor: scope of work, trades on site, EMR, TRIR, fatalities and citations in the last 3 years, insurance expiry. 2. Answer the questionnaire — Yes, No or N/A with evidence notes per question — and attach documents (insurance certificates already on the vendor are listed alongside). Click *Submit for decision*. 3. Record the decision: Approved, Conditional (with conditions) or Rejected, the risk tier, and *Valid until*. The register counts current, open, expiring-within-30-days and lapsed assessments, and the reviewer is warned 30 days before expiry. ### Dispatching an alert and reading the muster 1. Go to **Team → Emergency Alerts** and compose: title, body, an SMS version (a voice call reads the title and message), audience, channels, the recipient response and a chase-up deadline. Saving always creates a draft; start from an **Alert Template** for recurring scenarios. 2. Send it. Only the people named by *Who can send a Safety Hub emergency alert?* can press Send; an approval workflow never holds an emergency alert — it sends at once, and if a workflow covers alerts its reviewers are told afterwards. You can still submit a draft for review before you send it. With *Translate emergency alerts into recipients' languages (AI)* on, each non-English recipient gets a translated copy. 3. Watch the roster: safe, needs help and unresponded, with per-channel delivery diagnostics. A "needs help" pages responders with an Inbox action item. Unacknowledged recipients are chased every 6 hours over in-app, email and push until the chase-up deadline. 4. Cancelling a sent alert sends everyone it reached a stand-down notice in the app (and a push to the mobile app); no text, call or email is sent. *Open incident* from the alert pre-fills an incident with the alert's details. ### Monitoring certifications 1. Go to **Team → Certifications** for the roster, then **Expiring**, **Expired**, **By Employee**, **By Requirement** and **Training Gaps**. 2. Holders and their managers are reminded at the requirement's lead time (default 30 days), then 7 and 1 days before expiry; expired notices go to the manager and safety administrators weekly for 30 days. 3. Employees see their own under **My Certifications**, with a Practice Hub link for re-certification practice. ## 5. Settings All settings live at **Safety Hub → Admin → Settings**, grouped by card. Changes apply immediately. *Reset* clears only Safety Hub's own keys back to these defaults. | Setting | Card | Default | What it changes | |---|---|---|---| | Enable Safety Hub AI Agent | top of page | On | Whether Ask AI answers Safety Hub questions and runs its tools | | Enable Autonomous Safety Operations | top of page | Off | Lets the hourly detector nudge owners of stalled investigations and escalate unassigned High/Critical incidents; also needs a trust level in the AI Console | | Enable AI authoring assists (alert copilot and describe-to-fill) | top of page | On | The alert composer copilot and describe-to-fill on the observation, requirement and topic forms | | Enable Incidents Module | Modules | On | Incident reporting, investigations, the corrective-action register, OSHA and WCB | | Enable Observations Module | Modules | On | Observations and campaigns | | Enable Toolbox Talks Module | Modules | On | Talks and the Topic Library | | Enable Certifications Module | Modules | On | Requirements, rosters and expiry reminders | | Enable Emergency Alerts Module | Modules | On | Alerts, templates, muster and the alert API | | Enable Contractor Pre-qualification Module | Modules | On | The Contractors register and expiry warnings | | Enable Permits to Work Module | Modules | On | The permit board, My Permits, mobile permits and the hourly permit check | | Require a current pre-qualification before issuing a contractor permit | Modules | On | Refuses to issue a contractor permit without a current assessment | | Default pre-qualification validity (months) | Modules | 12 | Prefills *Valid until* on a decision | | Emergency number | Public Emergency Contacts | blank (shows 911) | The number on the portal's emergency page | | Emergency contacts | Public Emergency Contacts | none | Name, role and phone shown on the portal | | Who can see safety records at every site? | Who Can Do What | Safety Hub app admins | Cross-site visibility of incidents, corrective actions, certification rosters and observations | | Who can send a Safety Hub emergency alert? | Who Can Do What | Managers and admins | Who may press Send (web, API and Ask AI) | | Default channels | Emergency Alert Defaults | In-app, Email, Push | Pre-selected channels in the composer | | Default recipient response | Emergency Alert Defaults | Require acknowledgement | Pre-selected response mode in the composer | | Translate emergency alerts into recipients' languages (AI) | Emergency Alert Defaults | On | Per-recipient translation at send time | | Enable OSHA Compliance (US) | Compliance | On | OSHA dashboard, 300 Log, Form 301, Form 300A | | Enable WCB Compliance (Canada) | Compliance | Off | WCB dashboard, incident log, employer's report, annual summary | | Default WCB Province | Compliance | blank | Province used when an incident's location has none | | Auto-determine WCB Reportability | Compliance | On | Runs the WCB determination when an injury is created or updated (only with WCB on) | | Require Photos for Injury Incidents | Incident Settings | On | Refuses an Injury report without a photo on desktop and mobile — never on the public portal | | Auto-assign Investigators | Incident Settings | On | Assigns an investigator when a qualifying incident is reported | | Investigation Deadline (days) | Incident Settings | 7 | Days after the event before an investigation is overdue | | Require Re-authentication Before Printing or Exporting Incident Reports | Incident Settings | Off | Step-up identity check before exports, prints and OSHA/WCB filings | | Require Effectiveness Verification Before Closing Over Completed Actions (ISO 45001) | Corrective & Preventive Actions (CAPA) | Off | Blocks closing an incident while a completed action awaits verification | | Escalate Overdue Actions To | Corrective & Preventive Actions (CAPA) | No escalation | Daily overdue email to Safety officers or the Assignee's manager | | Allow Anonymous Observations | Observation Settings | Off | Shows the anonymous option on observation forms | | Observation Categories | Observation Settings | PPE, Housekeeping, Behavior, Equipment, Ergonomics, Chemical, Other | Category choices on observation forms | | Default Talk Duration (minutes) | Toolbox Talk Settings | 15 | Prefilled duration on a new talk | | Require Attendance Signatures | Toolbox Talk Settings | On | Refuses an unsigned attendance roster | | Expiry Reminder (days before) | Certification Settings | 30 | Lead time for expiry reminders and the "expiring" window | | Route incident and hazard alerts to this group | Notifications | none (site managers, then business administrators) | Extra recipient group for incident and observation alerts and help-request paging | | Enable Email Notifications | Notifications | On | The email leg of every Safety Hub notification | | Alert Site Managers and Administrators on New Incidents | Notifications | On | Master switch for new-incident alerts, including the High/Critical escalation | | Add the Site Safety Lead (or Business Administrators) to High-Severity Incident Alerts | Notifications | On | Adds the site's safety lead on High/Critical, else up to 5 admin accounts | | Alert on At-Risk, Near-Miss and Portal Suggestions | Notifications | On | Alerts for at-risk and near-miss observations and portal suggestions | | Send Toolbox Talk Invitations, Reminders and Missed-Attendance Notices | Notifications | On | Invitations, reschedule notices, day-of reminders, and the next-day notice to the facilitator and absentees' managers naming who missed a talk | | Send Certification Expiry Reminders | Notifications | On | Milestone and expired notices | | Send Weekly Safety Summary | Notifications | On (off for businesses that had Safety Hub before 28 Sep 2026) | Monday 08:00 local email digest of the previous week | | Weekly Summary Recipients | Notifications | Safety team | The recipient group, else Safety Hub app admins, else business admins (at most 25); or every active manager and admin | ## 6. More help - **Safety Hub FAQ** — specific setup and operating questions, employee complaints, and every limit - Ask AI — the assistant answers questions about Safety Hub from these articles. **Keywords:** safety, incident, incident report, safety observation, near miss, investigation, corrective action, CAPA, ISO 45001, toolbox talk, safety meeting, certification, permit to work, hot work permit, confined space, contractor pre-qualification, contractor, OSHA, WCB, emergency alert, muster, safety portal, safety compliance, safety-hub, safety_hub --- # Safety Hub FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-14 Answers to common setup and operating questions about Safety Hub — incidents, corrective actions, permits to work, contractor pre-qualification, emergency alerts, the public portal, OSHA and WCB — for the admin running it and the employees using it. # Safety Hub FAQ Answers to common setup and operating questions about Safety Hub. For what the app is and how to set it up from scratch, see the [Safety Hub Overview](/help/articles/safety_hub_app_overview). --- ## Setup ## Do I have to configure anything before Safety Hub starts working? Mostly no. Once an admin enables the app, the Incidents, Observations, Toolbox Talks, Certifications, Emergency Alerts, Contractor Pre-qualification, Permits to Work and OSHA Compliance (US) modules are all on; only WCB Compliance (Canada) is off. Three things do stay silent until a second piece exists: certification rosters need both a requirement and a source of held certifications (certified skills or Training Connect records); contractor permits cannot be issued until the contractor has a current pre-qualification (the gate is on by default); and autonomous safety operations need both the *Enable Autonomous Safety Operations* toggle (off by default) and a trust level in the AI Console. ## Why does the public safety portal say it is not available? The `/safety` portal needs Safety Hub enabled for your business and the Safety Hub portal switched on in the **Portals** app; if either is missing, visitors see a branded "not available" page. Safety Hub's own **Settings → Public Hazard Portal** card can only close the portal — re-opening it is done in Portals. Only knowledge-base articles marked visible in the public portal are published there. --- ## Permissions and access ## Who can see and do what in Safety Hub? Three tiers. **Members** (anyone the app is published to) report incidents and observations, see their own submissions, certifications, talks, assigned corrective actions and permits, read the knowledge base, and respond to alerts. **Managers** (platform Manager or above, or a Safety Hub app admin) get the Team zone: incidents and investigations at their sites, the corrective-action register with Complete and Verify, campaigns, talks, certification rosters, permit issue and suspend, contractor assessments and decisions, OSHA/WCB, analytics and the alert composer. **Admins** (platform Admin or above, or a Safety Hub app admin) add Settings, Certification Requirements, Alert Templates, sample data, closing the portal, deleting incidents and observations, and the AI Console. Two capability pickers under **Settings → Who Can Do What** widen this: *Who can see safety records at every site?* (default: app admins) and *Who can send a Safety Hub emergency alert?* (default: managers and admins). The alert Bookings sends from its evacuation dashboard to everyone checked in to a building is a separate setting, in Bookings → Settings. Alert recipients are the exception to the Members audience. Anyone who was sent an emergency alert can see it and respond to it, even if Safety Hub is not published to them. They see only **My Alerts** on desktop, the alerts inbox on their phone, and the same list through the API. Every other Safety Hub page stays closed to them. If an admin turns Emergency Alerts off, that list disappears, but a recipient can still check in or acknowledge from the alert itself. ## Why can't a manager see incidents at another site? A plain manager sees safety records only at the locations they manage; an incident at another site, or with no location at all, is invisible to them. Admins and Safety Hub app admins see every site. To give a safety committee cross-site visibility without making them admins, set *Who can see safety records at every site?* to a specific group. ## Who can authorise a permit to work? A manager for the permit's site — never the person who requested it. Managers granted *Who can see safety records at every site?* can authorise anywhere; a site-scoped manager only sees and issues permits at their own sites (a permit with no site is open to any manager). The authoriser opens the Requested permit, confirms every precaution for its type and clicks *Confirm precautions and issue permit*; precaution ticks are writable by managers only, and a manager who requested a permit must hand it to another manager to issue. The permit records who issued it and when. The requester, the authoriser or a Safety Hub manager at the permit's site can close it, while it is Issued, Suspended or Expired (an expired permit still owes its close-out); suspending and resuming are manager actions. --- ## Day-to-day ## How do I get a permit for hot work? Open **My Permits**, click *Create Draft Permit*, choose *Hot work*, describe the work, set the site, the *Work starts* and *Work ends* window (no more than 14 days) and the contractor if external, and tick the hazards you have identified. Save, then click *Request approval*. A manager confirms the six hot-work precautions and issues it; you will see it as Issued or Active on My Permits and on your phone. ## Why was my permit refused? A permit is only issued from Requested, and the refusal names the reason: you requested it yourself, the work window has already ended, one or more precautions are not yet confirmed, or the contractor has no current pre-qualification. Fix the cause — adjust the window, have the authoriser tick the remaining precautions, or have the contractor assessed under **Team → Contractors** — and request approval again. ## What happens when a permit runs past its end time? Nothing is flipped automatically at first. The board shows it as *Past end time* and the requester and authoriser are nudged; an hourly check had already warned them when the permit was within 1 hour of ending. If nobody closes it, the same check marks it Expired 24 hours after the end time (a suspended permit nobody resumed expires the same way), tells the requester and authoriser, and the record reads "Passed its end time without close-out." An expired permit still owes its close-out, so it stays under *Past end time* until someone closes it, for 30 days after its end; after that it is listed under *All*, where it can still be closed. A request nobody issued before its work window ended is cancelled by the same check, with the reason "The work window ended before the permit was issued.", and the requester is told. Once issued, a permit's type, window, site and contractor are frozen — cancel it and request a new one rather than editing. Close permits on time: tick *Work complete or stopped; area inspected and left safe* and click *Close permit*. ## Why can't I close this permit from my phone? You can close a permit from mobile. The requester, the authoriser or a Safety Hub manager at the permit's site can close it, while it is Issued, Suspended or Expired (an expired permit still owes its close-out). The close-out also requires the *area inspected and left safe* box to be ticked. Creating, editing, issuing and suspending a permit are desktop-only; mobile shows the permit list, a read-only checklist and the close-out. ## What does a "conditional" pre-qualification mean? Conditional is an approval with strings attached: the reviewer records the conditions (for example, a rescue plan on file before any work at height) and a *Valid until* date, which defaults to 12 months out. For the permit gate, Conditional counts as current exactly like Approved until *Valid until* passes. After that date the assessment shows **Lapsed**, permits for that contractor are refused, and a daily check moves it to Expired. ## How is a contractor's score and risk tier worked out? The 15 questions carry weights of 1 to 3 points; the score is the points earned by "Yes" answers as a percentage of the points available, with "N/A" removed from the denominator. The suggested tier is Low at 85% or more, Medium at 60% or more, otherwise High — except that a "No" on any 3-point Performance or Insurance question (EMR at or below 1.0, no fatalities, general liability, workers' compensation) caps the suggestion at High regardless of score. The reviewer chooses the final tier on the decision form. ## Who is notified when a high or critical incident is reported, and how? Site managers, up to 10 administrators, the site's safety lead, else up to 5 business administrators (with *Add the Site Safety Lead (or Business Administrators) to High-Severity Incident Alerts* on) and any group named in *Route incident and hazard alerts to this group* are notified in-app, by push and by email. High and Critical incidents also run the escalation cascade: in-app and push first, then SMS and email, then voice. An investigator is assigned at once when *Auto-assign Investigators* is on. All of this is gated by *Alert Site Managers and Administrators on New Incidents*, and the email leg by *Enable Email Notifications*. ## Why do the OSHA TRIR and DART rates show as an estimate or blank? Safety Hub does not track hours worked. The OSHA dashboard and the 300A summary therefore leave TRIR, DART and total hours blank, while the Analytics page shows an estimated rate using active users × weekdays × 8 hours. Recordable counts, DART cases and days away or restricted are exact; only the rates are estimated. ## Why does my tenant see no Canadian WCB screens? *Enable WCB Compliance (Canada)* is off by default; turn it on under **Settings → Compliance** and the WCB (Canada) entry appears in the Team zone. Reportability is auto-determined for injuries when *Auto-determine WCB Reportability* is on. Province rules exist for Ontario, British Columbia, Alberta, Manitoba and Saskatchewan only, and the province is read from the incident location's state (or *Default WCB Province*); an incident with no province is flagged but gets no WCB log entry. ## Why hasn't the weekly safety summary arrived? *Send Weekly Safety Summary* is on by default for businesses that added Safety Hub from 28 September 2026; businesses that had it before keep the setting they had. It is under **Settings → Notifications**, and *Enable Email Notifications* must also be on, because the summary is email-only. It arrives on Monday at 08:00 in your business's time zone and covers the previous Monday to Sunday. *Weekly Summary Recipients* decides who gets it: *Safety team* (the group chosen under *Route incident and hazard alerts to this group*, else the Safety Hub app admins, else the business administrators — at most 25 people) or *All managers and administrators*. ## Someone reported a hazard anonymously on the portal — where does it go? It depends on the report type. *Injury or Illness* and *Property or Equipment Damage* become an anonymous incident (the title is the first 100 characters of the description). *Hazard or Unsafe Condition*, *Near Miss* and *Safety Suggestion* become a safety observation marked as coming from the public portal, and suggestions alert managers when *Alert on At-Risk, Near-Miss and Portal Suggestions* is on. Portal reports carry no photos and no reporter account, and each address may file 5 reports per 10 minutes. --- ## When something looks wrong ## Why can't I see the incident I reported? Look under **Submitted by Me** — members do not get the Team zone's Incidents list, and on mobile the same feed is "Submitted by me". If you filed the report through the public portal, it is anonymous and not tied to your account, so it never appears there. Managers who cannot see a colleague's report are usually outside the incident's site. ## I reported an injury but it was rejected because no photo was attached — why? *Require Photos for Injury Incidents* is on by default, so an Injury report without at least one photo is refused on both desktop and mobile. Attach a photo (mobile can capture one with the camera) and submit again. The public portal never asks for photos, so a portal report is accepted without one. ## Why can't I close this incident — it says actions still need verification? *Require Effectiveness Verification Before Closing Over Completed Actions (ISO 45001)* is on. Every completed corrective action on the incident must be verified by a manager other than its assignee, with notes, before the incident can close; check the register's awaiting-verification filter. The investigation must also be complete. If the policy does not apply to you, turn the setting off under **Settings → Corrective & Preventive Actions (CAPA)**. ## Why isn't autonomous monitoring flagging stalled investigations? Check three things. *Enable Autonomous Safety Operations* is off by default and *Enable Safety Hub AI Agent* must be on too. In the AI Console, the agent needs a trust level — on Probation (10 actions a day) every action waits for your approval, and three rejections in 30 days force approval again; a paused agent does nothing. It only watches two patterns — investigations untouched for 7 days and Reported High/Critical incidents with no investigator — and it only sends nudges; it never changes records. --- ## Licensing and limits ## Does Safety Hub require a licence? Yes. Safety Hub requires a licence and is disabled until an administrator enables it for the business from Admin → Apps → All Apps. It is never auto-enabled. ## Are there limits I should know about? | Item | Value | |---|---| | Permit work window | up to 14 days | | Permit ending-soon nudge | within 1 hour of end time | | Permit auto-expire | 24 hours after end time, if not closed | | Pre-qualification expiry warning | 30 days before *Valid until*; expired the day after | | Pre-qualification documents | under 25 MB each | | Pre-qualification EMR / TRIR | EMR 0 to under 100; TRIR 0 to under 1,000 | | Suggested tier thresholds | Low at 85% or more, Medium at 60% or more | | Incident title / description | 3–255 / 10–5,000 characters | | Days away / days restricted | 0–9,999 | | Investigation deadline | 1–90 days (default 7) | | Investigation overdue reminders | daily for 7 days, then weekly, stopping at 90 days | | Observation description / specific location | up to 5,000 / 255 characters | | Campaign target / reward points | 1–1,000,000 / 0–1,000,000 | | Talk duration | 1–1,440 minutes | | Requirement validity / reminder lead | 1–1,200 months / 1–3,650 days | | Certification reminder milestones | lead (7–90 days, default 30), then 7 and 1 days; expired notices weekly for 30 days | | Corrective action due-soon reminders | 7, 3 and 1 days before; overdue escalation stops at 90 days | | Corrective action description / verification notes | up to 2,000 / 4,000 characters | | Alert title / body / SMS / voice | 200 / 10,000 / 320 / 700 characters | | Alert media | up to 4 files; images 10 MB, videos 50 MB | | Chase-up deadline options | 1, 2, 4, 8, 24 or 72 hours; re-notified every 6 hours until the deadline | | Check-in note | up to 2,000 characters | | Muster roster / permit board / contractor register pages | 25 per page | | Public portal | 5 reports per 10 minutes per address; 120 reads per minute; description 10–5,000, location 255 | | Similar incidents | 5 results | | Incident access log | 500 rows per export; kept 7 years | | Submitted by Me | 500 per source, 20 per page | | Analytics windows | 7, 30, 90 or 365 days | | API page size | 25 by default, 100 maximum | | Autonomous actions per day | 10 (Probation), 50 (Standard), 200 (Trusted) | --- ## More help - [Safety Hub Overview](/help/articles/safety_hub_app_overview) - Ask AI — the assistant answers Safety Hub questions from these articles. **Keywords:** faq, incident reporting, investigation, corrective actions, ISO 45001, permit to work, hot work permit, confined space, contractor pre-qualification, conditional approval, emergency alerts, muster roll-call, safety observations, toolbox talks, certifications, OSHA, TRIR, WCB, anonymous reporting, public safety portal, weekly safety summary, safety-hub, safety_hub --- # Sample Data — Loading and Clearing **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-18 How a Super Administrator loads realistic demo data from Admin → Sample Data (all modules, one module, one app, or with the Sample Data Assistant), loads or removes one app's data from its Demo data card, builds a themed sample organization, and clears sample data or starts over without touching real records. # Sample Data — Loading and Clearing Sample data lives at **Admin → Sample Data** and is open to Super Administrators. Load it with **Create All Sample Data**, a module's **Load standard set**, the **Sample Data Assistant**, or an app's own **Demo data** card. Remove it with **Clear**, a module's **Clear … data**, or **Start over**. Only sample records are removed; real people and real data stay. ## 1. What it is Sample Data fills a business with realistic demo records — people, departments, locations, holidays, and the records of each app — so you can show or test the product, and then removes them cleanly. Every sample record is marked as sample when it is created, which is how it is counted, kept out of inboxes, and removed later. - **Who can open it:** a Super Administrator, on any business. On an internal QA business (one MangoApps has marked for internal testing), Administrators can open it too. An Administrator on any other business who opens it sees: "Sample data tools are only available to a Super Administrator. Ask a Super Administrator in your organization to load or remove sample data." - **Employees and managers** cannot open this page. Someone who manages an app's settings (an administrator, or a person delegated to administer that app) can still load or remove that one app's sample data from its **Demo data** card — see below. Otherwise, ask an administrator. - **Where it is:** in the admin sidebar under **Super Admin → Sample Data** (on an internal QA business, an Administrator sees the section as **Demo Data**). A flask icon in the top bar (a magic-wand icon when the business looks empty) also opens it; hover it to see what it will do. Outside production it is always there for the people who can open the page; in production it shows only while the business holds sample data or looks empty. - **Demo Scenarios** is a separate page in the same sidebar section, for preparing a scripted demo story. This article covers the Sample Data page. ## 2. Standing it up 1. Go to **Admin → Sample Data**. 2. In **Every run uses these settings**, choose **How much** (Small, Medium, Large or XL) and, if you like, a **Theme** such as "regional hospital network". Pin people or locations under **Who it's for** if the data should be about them. 3. Click **Create All Sample Data**. The Sample Data Assistant opens with a plan: the standard set for every module. 4. Review the plan card and click **Create it** (or **Change something**). 5. The run works through the modules in the background. You can leave the page; you get a notification when it finishes, and an email if your account has an email address. The first load on a business also builds the shared **Foundation** — sample people, departments, locations and holidays — if the business has none yet. ## 3. How it fits together ### Foundation and modules **Foundation** is what every module shares: the business profile, the sample organization (departments, locations, job titles), the sample users, and holidays. It appears as a band of four cards — **Business**, **Organization**, **Sample users** and **Holidays** — with a **Ready** or **Not seeded yet** badge. The Organization card shows each count as the total and how many of them are sample. **Modules** group the apps. Each module card shows how many sample records it holds right now, or "No sample data yet", and the apps it covers. The modules are Performance Management, Shifts & Schedules, Recruiting, Service Desk, HR Operations, Knowledge & Compliance, Employee Experience, Communications Hub, Workplace Operations, Advanced Operations, and Platform & AI. Use **Find an app…** to jump to the module that holds a given app. Opening a module shows: - **What's in … right now** — every app in the module with its live count, a **Load standard set** button, and **Open** to go to the app. Apps whose data comes with the foundation show **Foundation** instead of a load button. - **Create … data with the Assistant** — describe what you want, or pick one of the ideas. - **Other inputs** — choices specific to the module, such as which review template to use. - **What … supports** — which shared settings (pinned people, pinned locations, volume, theme, clearing) the module honours. Settings it does not support are ignored there. ### The settings every run uses - **Who it's for** — pin people (**+ User**) or locations (**+ Location**). With nothing pinned, runs use the default sample group of people. - **How much** — Small (a handful of records per app), Medium (enough to fill every list and chart, the default), Large (hundreds per app) or XL (thousands per app; runs take longer). - **Theme (optional)** — used by apps that support theming, and by the sample organization. These settings save as soon as you change them and last until you sign out: a new sign-in starts again from the organization's theme, Medium, and no pinned people or locations. ### The Sample Data Assistant Click **Open Assistant** (or the **Assistant** button at the edge of the page). Describe what you want in plain words — one app, one module, or several apps that tell one story, such as "Shifts, Time Off and Performance for the same team". The Assistant never creates or removes anything itself. It proposes a **plan** on a card that lists, app by app, what will be made or removed. Nothing happens until you click **Create it**, **Remove it** or **Align it**. **Change something** lets you adjust the plan first. When several modules are planned together, they share the same people, one time window, and records that refer to each other. You can also ask the Assistant to make existing sample data consistent ("align it") — nothing is deleted. While a plan runs, its card shows each step; **Stop after this step** stops it, and the steps already finished stay. ### A themed sample organization Yes, AI can build a demo organization for a theme. Which button you use depends on whether the business already has a sample organization: - **No sample organization yet:** set a **Theme** and click **Build the organization** in the Foundation band. The Assistant writes departments, locations, job titles and people for that theme and shows them on a plan card for you to confirm. - **A sample organization already exists** (the band shows sample users): set the new **Theme** and click **Rewrite for the theme**. It renames the organization in place: the same departments, locations and people get new names, so every app's sample data on those people stays. **Rewrite, with new names for people** also gives people new names (pinned people keep theirs). To build a different organization from scratch instead, **Start over** first, then **Build the organization**. ### What loading turns on Loading an app's data from this page licenses and turns on that app and, for apps employees use, publishes it to every employee if it was not open to them yet. The module page tells you which apps that applies to before you click. ### Reports and billing - **Reports:** sample records are ordinary records in each app, so lists, dashboards, reports and exports count them alongside your real records until you remove them. A few compliance reports, such as EEO-4, leave sample people out. Clear the sample data before you rely on the numbers. - **Billing:** sample people are not billed. Per-employee plans and per-seat apps count only real, active people, and the billing pages say how many sample people were left out. Sample rows also do not count toward usage meters such as Power Tables storage. Loading licenses and turns on apps (above), but it does not add anything to your plan. ### Sample data stays out of inboxes An email about a sample record is not sent, and no bell notification is created about one, even when a sample record names a real person. ### One run at a time Sample-data runs happen one at a time per business; new requests wait their turn ("Waiting its turn…"). A load or removal for an app that already has one running is refused until it finishes. ## 4. Running it ### Load data for every module Click **Create All Sample Data**, check the plan card, and click **Create it**. ### Load one module or one app Open the module card. For one app, click **Load standard set** on its row. It starts with no plan to confirm, and the count updates as the data is written. If the business has no sample organization yet, the first load also builds the shared sample people, departments and locations. For something specific — dates, people, amounts — describe it in **Create … data with the Assistant** and confirm the plan. ### Load or remove one app from its own settings page Many apps have a **Demo data** card on their settings page with **Load Sample Data** and **Remove Sample Data**. It loads the same standard set (with the theme your sample organization was built for), shows whether sample data is loaded and how many records, and shows progress while a load or removal runs. Anyone who can open that app's settings can use it. Points to know: - The first load also adds the shared sample employees and organization if the business has none. Removing the app's data leaves those in place. - When an Administrator loads, the app is licensed and turned on. It never publishes an app you have kept admin-only — the card says so when that applies. - When an app shares its sample data with other apps, the confirmation names them; loading or removing affects all of them. - If an app's sample records are part of the shared company data, Remove explains that only a Super Administrator can clear them. Loading again usually adds little or nothing for people who already have data in that app; the result tells you. To start an app fresh, remove its data first. ### Remove sample data - **Some or all modules:** click **Clear** beside the record count at the top of the page. Tick the modules (**Select all** or **None**) and click **Clear selected**. This removes the modules' sample records; the sample people and organization stay. Shift Feedback, which comes with the shift data, has its own **Clear** link in the same dialog when it holds data. - **One module:** open it and click **Clear … data**. The Assistant shows what will be removed; click **Remove it**. If people are pinned, the clear removes only their sample data in the apps that support it; when it would remove everyone's, the button reads **Clear … data for everyone**. - **Everything — start over:** click **Start over** in the Foundation band (it sits in the band's **⋮** menu as **Start over instead** when your theme has changed), or ask the Assistant to start over — the only way when the band shows no **Start over** (there is no sample organization yet, for example after a run for pinned people only). It removes every module's sample data first, then the sample users, departments (with their job titles), locations and holidays. Pinned people and sites stay. Rebuild afterwards with a theme and **Build the organization**. - **Parts of the foundation:** the Organization card offers **Remove sample departments** and **Remove sample locations**; the Sample users card offers **Remove old users** (sample users who are not pinned, and their records). - **Remove seeded foundation** (in the Foundation band's **⋮** menu, when available) removes the sample employees, organization and shift records that sample-data loads recorded creating. Anything that existed before the first recorded load is not touched. ### Will clearing delete real records? No. Only records created as sample data are removed — real users, real data and your templates stay. If a real record still uses a sample item — for example, a real time entry logged against a sample project — that sample item is kept, and the result says what was kept and why. Records that belong to a sample person are removed with that person. When a clear finishes with leftovers, the page lists each app and what remains; where an app gives a reason, those records were kept on purpose, usually because another app's records still point at them — clear that app first rather than retrying. ### Keep the demo current Sample dates are fixed when the data is loaded, so "today" and "this week" views thin out over time. The page shows how old the sample dates are. **Refresh dates** moves every sample date forward in whole weeks, so weekdays stay put; real records are never touched. **Keep current automatically** (**Turn on** / **Turn off**) does this for you. ### Check what a demo will show **Demo readiness** → **Check now** opens every app's main screens as a sample manager and a sample employee and reports which ones show nothing, as a score, a list of screens to look at, and any apps that repeat the same text across many records. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Access | Role | Super Administrator on every business; also Administrator on an internal QA business | Who can open Admin → Sample Data and see its sidebar item and top-bar button | | Who it's for | Every run uses these settings | Nothing pinned (default sample group) | Which people and locations new sample data is about | | How much | Every run uses these settings | Medium | How many records each app gets (Small, Medium, Large, XL) | | Theme | Every run uses these settings | The theme the sample organization was built for, if any | How apps that support theming, and the sample organization, are named and written | | Other inputs | A module's page | Auto | Module-specific choices, such as which template to use | | Keep current automatically | Sample dates strip | Off | Whether sample dates are moved forward for you | The Demo data card on an app's settings page loads the standard set at Medium; a few apps (such as Contracts) let you set some counts on the card first. ## 6. More help - **Admin → Demo Scenarios** — prepare a scripted demo story with its own data. - **Background tasks** (the **⋮** menu at the top of the Sample Data page) — every run's progress and result. - Ask AI — answers questions about sample data from this article. **Keywords:** sample data, demo data, seed data, create sample data, create all sample data, load sample data, load standard set, clear sample data, remove sample data, delete sample data, start over, sample data assistant, demo data card, re-theme, rewrite for the theme, build the organization, setup wizard, sample records, demo tenant, volume preset, foundation data, sample users, sample employees, pinned people, refresh sample dates, demo readiness, reports, billing --- # SCIM Provisioning Overview **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-14 How a SCIM connection lets Microsoft Entra ID, Okta or an HR system create people, keep their profiles current, switch their access off and on, and push groups — what you set up, what the provider owns, and what stays yours. # SCIM Provisioning ## 1. What it is A SCIM connection lets your identity provider — Microsoft Entra ID, Okta, OneLogin, JumpCloud, or an HR system that speaks SCIM 2.0 such as Workday or UKG — manage your people here. The provider **pushes** changes: it creates people, fills their profile from the field mapping, switches their access off and on, and manages groups. - **Where:** **Admin → Integrations → Identity Providers**, then **Set up SCIM provisioning**. Only administrators can see or change it. - **What it never does:** it never sets a password, and it never makes anyone an administrator. Your own **Provisioning Rules** can make someone a Member or Manager from the groups the provider sends. - **What it is not:** it is not single sign-on. How people sign in is set up separately; the connection can be linked to a sign-in so the two work together. ## 2. Standing it up 1. Go to **Admin → Integrations → Identity Providers** and choose **Set up SCIM provisioning**. 2. Name the connection, choose your identity provider, and choose the **Linked sign-in** your people use (choose **None** for an HR system: new people then get an invitation). 3. On the connection's page, copy the **Tenant URL** and the **bearer token**. The token is shown once; if you lose it, **Replace** it and paste the new one into your provider. 4. In your provider, paste them into its provisioning settings. In Microsoft Entra, open your enterprise application → **Provisioning**, set **Provisioning Mode** to **Automatic**, and paste the Tenant URL and the token as the **Secret Token**. Select **Test Connection**, then save. 5. Assign a few people first, and switch provisioning on. Entra sends the first people within minutes, then checks for changes about every 40 minutes. **Provision on demand** sends one person straight away. 6. Back on the connection's page, the **Activity** list shows every request your provider sent. Microsoft Entra's own app provisioning signs in with the Secret Token. Leave the connection's authentication on the bearer token for Entra. ## 3. What the provider owns, and what stays yours | Field | Who decides | |---|---| | First name, last name, email, and whether they can sign in | The provider. These are locked on the profile and say **Managed by** your provider. | | Job title, department, phone, time zone, hire date (when the field mapping fills them) | The provider fills them. **An edit made here stays**: the provider stops updating that field for that person, and their profile says **Edited here**, with a button to use the provider's values again. | | Everything the field mapping does not fill | You. | A person who also belongs to another organization keeps their own profile: the provider manages their access here but does not write their profile fields. ## 4. Leavers, and switching people off here When the provider switches someone off (or removes them), they are switched off here: their sessions end, they get a separation date, and they can use the Former Employee Portal. The provider decides access for the people it holds. If you deactivate one of them in **People**, switch them off in the provider too: the next time the provider sends them as active, their access comes back and the separation details entered here are cleared. The People list marks them **From** your provider, their profile says **Provisioned by** it, and the Deactivate and Delete confirmations remind you. ## 5. Groups Groups the provider pushes become **employee groups** whose members follow the provider. People you add to such a group by hand stay, and are listed as added by hand. Turn on **Also create a workspace for each pushed group** to give each group a workspace whose members follow the provider. A group gets its workspace the next time the provider sends it; Microsoft Entra resends only groups that change, so restart provisioning in Entra to send them all. People added to the employee group by hand are not added to its workspace: add them in the workspace. ## 6. Pausing and removing - **Pause** stops the provider: its requests are refused until you **Enable** the connection again. The connection reads **Inactive**, and the provider keeps its lock on the people it holds, so nothing edited over the pause is put back silently. - **Remove this connection** stops the provider for good. Nobody is removed: the people stay members, pushed groups stay as ordinary employee groups, and workspaces stay with their owner, who can then manage their members. The request log goes with the connection. ## 7. When something looks wrong - **Check setup** says whether this side is ready to accept your provider. It cannot test the provider itself; use **Test Connection** in your provider. - **Activity** lists every request, with any refusal and its reason. A refused request can be **Replayed** once the cause is fixed. - **Needs review** holds people who could not be linked automatically: someone who also belongs to another organization, or who is managed by another source. ## More help - Single sign-on: **Admin → Integrations → Single sign-on** (SSO Configurations). - Role rules for pushed groups: **Admin → People → Provisioning Rules**. - Google Workspace, which this app pulls from rather than receiving pushes: see **Google Workspace Sync Overview**. **Keywords:** scim, scim provisioning, microsoft entra id, azure ad provisioning, okta provisioning, tenant url, secret token, bearer token, identity provider, automatic provisioning, deprovisioning, pushed groups, why did my edit change back, who switched this person back on --- # Search Across the Platform **Category:** System-features **Section:** Advanced Features **Updated:** 2026-10-16 How the search box at the top of every page works, what it finds and for whom, how synonyms and search areas shape it, and how admins check what one person would find or be told with Search as and Answer as. # Search Across the Platform ## 1. What it is The search box at the top of every page finds people, pages, settings and records from every app a person can open, from one field. As someone types, a short list of matches drops down under the box. **See all results** at the bottom of that list opens the full results page, grouped by where each match lives. Search only ever shows a row the person could already open. It never widens what anyone can see. - **Enablement:** nothing to turn on. Everyone who is signed in gets the search box, the full results page and their own Saved searches (and, on the Enterprise plan, My connections). The Search app's admin pages — Analytics, Synonyms, Promoted results, Sources, Search as, Answer as and Settings — are for admins, and need the Search app enabled for your organization. - **What it is not:** the search box is not Ask AI. It returns rows to open, not a written answer. Asking a question lives on the Ask AI button in the header and on the results page (**Open Ask AI**). ## 2. Standing it up Search works as soon as your organization exists. What an admin does is tune it: 1. **Check what feeds search.** Go to **Search → Settings** and read **Areas that feed search**. An area is one app or platform surface, and every area starts on. Turn one off only when you want it out of results for everyone. It stays findable inside its own app. 2. **Add your organization's shorthand.** Go to **Search → Synonyms**. If the page offers starter synonyms, add them in one click. They cover shorthand most workplaces use, such as PTO, FY, OOO, WFH and SOP. 3. **Decide who can look through other people's eyes.** Business admins can always use **Search as** and **Answer as**. If you have appointed Search app admins, decide whether they should too (see §5). 4. **Confirm it works.** Type a synonym into the search box — "PTO", say — and check that pages titled "Paid time off" appear. A saved synonym is used by the next search. **Two switches live in two places.** The Libraries, Wikis and Drive rows under **Areas that feed search** are the same switch as **Include Libraries in Global Search**, **Include Wikis in Global Search** and **Include Drive in Global Search** in those apps' own settings. Turning one off in either place turns it off in both. ## 3. How it fits together ### The search box and the results page The **search box** is a quick lookahead. It starts after 2 characters and checks a fast subset of areas on each pause in typing. Its answer is a short list: a **Best match** row when one result clearly wins, then page links and matching records. The **results page** runs the full search across every area that is on. It also looks for meaning matches — rows found because they mean the same thing, not because the words matched — for longer questions or when few rows match. On a phone, the magnifier in the header opens the phone results page, with the same lookahead under the field. On a computer, the box sits in the top bar and is hidden on narrow windows. ### What each person sees Every area applies its own app's permission rules to the person searching: - **Their own records only** — personal notes, saved items, HR files, leave balances and direct messages. - **Their own plus their team's** — for managers, records such as leave requests and timesheets of the people who report to them. - **Audience rules** — libraries, wikis, surveys and similar content respect who each item is published to. - **App enablement** — an app's results appear only when that app is enabled for your organization and visible to that person. **Page links** come from a curated shortcut list and the platform's page map, up to 5 at a time. A link to a page someone's role cannot open, or to an app that is not enabled, is not shown to them. Admins also see matching **admin settings** pages, with the path to each. **People search** tolerates typos ("Annup" finds Anup), names that sound alike ("Anoop" finds Anup) and preferred names. It matches email and employee ID only where your directory shows those fields. Other directory fields, such as city, are tried only when no one matched by name. ### Expired and not-yet-effective content Search and Ask AI read the same trust facts about a page, policy or document: - **Expired** — past its expiry date. It is left out of search results, as Ask AI leaves it out of answers. - **Not yet in effect** — still found, but labelled **Takes effect** with its date, listed after what applies today, and never the Best match. - **Overdue for review** — still found, and labelled **Review overdue**. ### Synonyms A **synonym** teaches search that two words mean the same thing. Worked example, using a starter synonym: | Term | Synonyms | Two-way | A search for… | also matches… | |---|---|---|---|---| | paid time off | pto, vacation, annual leave, time off | On | "pto" | paid time off, vacation, annual leave, time off | | paid time off | pto, vacation, annual leave, time off | Off | "pto" | nothing extra | | paid time off | pto, vacation, annual leave, time off | Off | "paid time off" | pto, vacation, annual leave, time off | With **Two-way** off, only the term finds its synonyms. Synonyms are a search tool only. They are separate from the Translation glossary, which changes how the interface is translated. ### Search as and Answer as These two admin pages answer "why does this person see something different from me?" Both need a named, active member of your organization. Neither saves anything under that person or lets the admin act on what is shown. **Search as** shows what one person would find in search for a query. It lists row titles by area. Private areas — their files, pay, leave, messages and similar — are counted but never listed. **Answer as** shows what Ask AI would answer that person from company knowledge. It shows the answer they would read and the sources listed with it. Under **Why each source**, every source the question reached is marked: - **Used** — the answer read it. - **Not needed** — found, but the answer did not need it. - **Left out** — with the reason, such as *Not visible to this person*, *Hidden from this person by a section rule*, *Expired*, *Not in effect yet* or *Overdue for review*. - **Ranked lower** — found, but ranked below what the answer read. These fold under one line. The person's own AI Notepad notes and tasks are counted, never shown and never used in the answer. When Ask AI would not answer them at all — they cannot open Ask AI, or answers from company knowledge are switched off in Ask AI's settings — the page says so instead of showing an answer. Answer as covers the company-knowledge answer only. In the Ask AI sidebar, a question that company knowledge cannot answer goes on to the app assistants, which this page does not run. **Every run of either page is recorded**: who ran it, for whom, the question or query, what was found, and when. After your **Keep search activity for** window, the record keeps who looked at whom and when, and drops the question and the sources. ## 4. Running it ### What your employees do 1. Click the search box, or press **Cmd+K** (Mac) or **Ctrl+K** (Windows) from any page. 2. Type at least 2 characters. Matches appear under the box. 3. Use the arrow keys and **Enter** to open a row, or **Esc** to close. 4. **Enter** with no row selected opens the full results page. So does **See all results for "…"** at the bottom of the list. Focusing the empty box shows **Recent** — the last few searches on that device. Recents are kept in the browser, per person and per organization, so a shared device does not show one employee's searches to the next. ### Close the gaps people hit 1. Open **Search → Synonyms**. **Searches that found nothing (last 30 days)** lists the most frequent searches that returned nothing. 2. Click one. The **Add synonym** drawer opens with it filled in — and, where a similar search did work, that search already set as the term. 3. Save. The next search uses it. For the full picture, and for pinning a page to the top of results, see the Search app article. ### Manage synonyms in bulk On **Search → Synonyms**, **Export CSV** downloads your list and **Import CSV** uploads changes. The file needs a `term` column; start from an export to get the rest of the shape. To pause a synonym without deleting it, turn **Active** off. ### Check what one person finds or is told 1. Open **Search → Search as** to check a search, or **Search → Answer as** to check an Ask AI answer. 2. Pick the **Person**. On Answer as, type what **They ask** and choose **Ask as them**. 3. Read the result. A missing row usually means an area is switched off, or a permission or audience rule in the owning app. On Answer as, the reason for each left-out source is on its row. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Areas that feed search | Search → Settings | All on | Takes one app or surface out of results for everyone. It stays findable inside its own app. | | Include Libraries / Wikis / Drive in Global Search | Each app's Settings | On | The same switch as that app's row in **Areas that feed search**. | | Let Search app admins use "Search as" and "Answer as" | Search → Settings | Off | Off means only business admins can use Search as or Answer as. Only a business admin can change it. | | Keep search activity for | Search → Settings | 90 days | How long search terms and clicks are kept for Analytics, and how long Search as and Answer as records keep the question and sources. Choices: 30, 90 or 180 days, or 1 year. | | Two-way (each side finds the other) | Search → Synonyms → Add synonym | On | Off makes the synonym one-way: the term finds its synonyms, not the reverse. | | Active | Search → Synonyms → Add synonym | On | Off pauses the synonym without deleting it. | The other Search settings — archived content, deactivated people, file types, the AI overview and admin notices — are covered in the Search app article. ## 6. More help - **[Search App Overview](/help/articles/search_app_overview)** — the results page, promoted results, analytics, external sources and every Search setting - **[Search FAQ](/help/articles/search_app_faq)** — specific questions and what to do when a search does not find what someone expected - **[Ask AI for admins](/help/articles/platform_ask_ai_for_admins)** — what the assistant can do and how to govern it - Ask AI — the assistant answers questions about search from these articles. **Keywords:** search, global search, search box, find, search bar, search results, see all results, best match, search synonyms, search relevance, command k, find people, can't find it, search as, answer as, why does ask ai answer differently, expired policy in search, takes effect --- # Search App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How Search works and how to run it — what feeds the results page, the live answers and AI overview above it, synonyms and promoted results, external sources, Search as and Answer as, and the settings an admin owns. # Search ## 1. What it is Search is the results page behind the search box at the top of every page. It looks across the OneMango apps a person can already open — policies, SOPs, wikis, files, people, shifts, tasks, forms and the rest — and groups what it finds by where it lives. On the Platform Enterprise edition it also reaches the systems your company keeps outside OneMango. The page answers in three ways at once. A **live answer** comes straight from records when the words name one fact ("pto balance", "who's on call"). An **AI overview** summarises what your documents say, with citations. The ranked results sit underneath. - **Enablement:** every paid plan includes Search, and nobody has to turn it on for a search to run. Anyone signed in gets the search box, the results page, Saved searches, and the My connections list with its **Disconnect** button. What the licence governs is the admin pages, connecting a new external source, and whether Search appears in the side navigation. - **What it is not:** Search is not Ask AI. Search hands back rows a person can open; Ask AI is a conversation. The results page has an "Ask AI about…" button, but they are separate apps with separate switches. - **Not an index:** every external search runs live, as the person searching. Nothing from your external systems is copied, indexed or cached. ## 2. Standing it up 1. Go to **Search → Settings** and read **Areas that feed search**: ninety areas under five headings, every one on. Turn one off only to keep it out of results company-wide; it stays findable inside its own app. 2. Teach Search your shorthand at **Search → Synonyms**. One click adds a starter set (PTO, OOO, WFH, SOP and similar), or import a list as a file. 3. Pin the answers you already know people miss at **Search → Promoted results**. A promoted result becomes the first row for the words you choose and is labelled **Promoted**. 4. On the Platform Enterprise edition, register external systems at **Search → Sources**, one entry per system instance. Use **Test** before you tell anyone. 5. Tell your people to connect. Each person connects their own account once at **Search → My connections**, and from then on their searches also ask that system, as them. 6. Confirm it worked: run a search yourself, then check **Search → Analytics** a few days later. **Load Sample Data** at the bottom of **Search → Settings** fills Analytics with a few weeks of activity meanwhile. **Things that silently do nothing until a second thing is also set:** - **A registered source with nobody connected returns nothing.** Registering a source is the admin half; each person still has to connect their own account. The Sources page shows how many people have connected to each one. - **The AI overview needs three switches on**, not one: Search's own **Show an AI overview above results**, the Ask AI app published to that person, and Ask AI's own company-knowledge switch. Turning any of them off removes the card. - **The Wikis, Libraries and Drive rows on the settings page are the same switch those apps show in their own settings.** There is one switch, shown in two places; turning it off in either place turns it off in both. - **The My connections tab only appears once an admin has registered at least one source** — and only on the Platform Enterprise edition. ## 3. How it fits together ### Areas and sections An **area** is what you switch on and off: one app or platform surface, listed on the settings page. A **section** is what a person sees: one group of results on the page, headed by where the rows live. Worked example. Leave is a single area on the settings page. Someone searching `holiday` sees separate groups on the results page for the holiday calendar, the leave policy and the holiday list — three sections, one area. Switching the Leave area off removes all of them at once. ### A live answer and an AI overview are different things A **live answer** is a fact read from live records — a leave balance, the next shift, who is on call, the next holiday, whether the person is clocked in, the manager's name, open tasks — shown as a card with the button to act on it. No AI is involved, and it is only as right as the records behind it. An **AI overview** is a short summary of what company documents say, with numbered citations. It loads a moment after the rest of the page, so results never wait for it. When a live answer already answers, no overview is shown. ### Best match, Top results, and the sections **Best match** is the single strongest row across every section, shown as a card, and only when the match is confident enough to earn it. **Top results** is the short ranked list under it, drawn from across the sections so one noisy area cannot fill it. Every section still renders in full below. Ranking only reorders rows a person could already open. It never widens what someone sees. Each ranked row can carry a small chip saying why it ranks — Yours, You acknowledged this, Your team, Your location, Promoted, People here open this, Meaning match, Review overdue, Takes effect (a date). Search and Ask AI read the same trust facts about a source. A page past its expiry date is left out of Search, as Ask AI leaves it out of answers. An entry that takes effect on a later date is still found, labelled **Takes effect** with its date, ranked below what applies today, and never the Best match. External results are ranked alongside everything else, but a bare external title is never the Best match — there is no text behind it to judge. ### Meaning matches A **meaning match** is a row found because it means the same thing, not because the words matched — a Spanish query finding an English SOP, or "time off rules" finding the leave policy. Meaning matches are ranked with everything else and labelled; they are never a section of their own. ### Synonyms and promoted results do different jobs A **synonym** widens what a query matches, everywhere: teach Search that FY means Fiscal Year and every area matches both. A **promoted result** changes nothing about matching — it pins one page or link to the top for the words you choose. Use a synonym for a different word; use a promotion for a page that exists but keeps losing. ### Sources and connections A **source** is the company's registration of one external system, created by an admin with the credentials to reach it. A **connection** is one person's own sign-in to that source. Disconnecting removes one person's sign-in; deleting a source removes everyone's. ### Saved searches and recent searches A **saved search** is kept on the server: the query, its filters, a name, and optionally a daily or weekly alert. A **recent search** is the last few things typed on that device — never shared and never aggregated. ### Search as and Answer as **Search as** shows an admin what one named person would find in the search box. It shows titles by area and nothing more. Private areas such as notes, HR files and pay are counted but never listed, and you cannot act on anything from it. **Answer as** is its twin for Ask AI: what Ask AI would answer that person from company knowledge, and why each source was used or left out. Nothing is saved to their Ask AI history. Worked example. Priya asks "How much paid time off do I get?" and gets a different answer from you. Answer as shows her answer, then gives each source a reason — **Used in the answer**, **Not visible to this person**, **Expired**, **Not in effect yet**. Her own AI Notepad notes and tasks are only counted. It covers company-knowledge answers only; the app assistants Ask AI falls back to are not run. If the person cannot open Ask AI, or company-knowledge answers are switched off, it says so instead of showing an answer. Business admins can use both. Every use is recorded in the audit log with your name, the person, the question, the sources and the time. ## 4. Running it ### Fix the searches that find nothing 1. Open **Search → Analytics** and pick a period. 2. Read the zero-result list — the searches people ran that returned nothing. 3. From any row, choose **Add synonym** — it reads **Add synonym → "…"**, prefilled with the nearest search that did work, when there is one — or **Promote…**, prefilled with the words that failed; you add the page to promote. 4. Watch the trend chart; the same search should stop appearing. Once a week, admins also get an Inbox notice listing the searches people keep running and opening nothing for. ### Check what one person can find, or would be told 1. Open **Search → Search as** for the search box, or **Search → Answer as** for Ask AI. 2. Pick the person and type what they searched or asked. On Answer as, choose **Ask as them**. 3. On Search as, read the areas that returned something. A missing row usually means an area is switched off, or a permission in the owning app. On Answer as, read **Why each source**. ### Keep an external source working Each source shows its last test result and how many people have connected. Admins get a notice in the Inbox and by email when a source keeps failing — every search for 15 minutes, or at least five searches, and half of them, in the last hour. Failing for everyone usually means a rotated secret or a changed host; failing some searches usually means the provider is slow or limiting us. Disabling a source hides it everywhere but keeps everyone's sign-ins, so re-enabling is instant. ### Curate promoted results over time A promoted result can have a start and end date, so a seasonal page can be pinned for open enrolment and stand down by itself. Any promotion can also be paused and resumed without deleting it. ## 5. Settings All of these live at **Search → Settings**, which admins and Search app admins can open. | Setting | Where | Default | What it changes | |---|---|---|---| | Areas that feed search | Search → Settings | All on | Switches one app or surface out of results for everyone. It stays findable inside its own app. **Reset to defaults** turns them all back on. | | Include archived content | Search → Settings | Off | Archived wikis, workspaces and direct message threads appear, marked **Archived**, and only to people who could still open them. | | Include deactivated people | Search → Settings | Off | Former employees appear in People results, marked **Deactivated**. "People who can help" stays current staff only. | | Exclude file types from results | Search → Settings | Nothing excluded | Keeps Images, Video, Audio, Archives or Design files out of file results. Each stays findable inside its own app. | | Show an AI overview above results | Search → Settings | On | Removes the AI summary card without touching Ask AI itself. | | Skip content with an open governance finding | Search → Settings | Off | The overview will not cite a page, policy, file or wiki that Content Governance has flagged — stale, ownerless, broken links, review overdue — until the finding is resolved. | | Keep search activity for | Search → Settings | 90 days | How long search terms and result clicks are kept to power Analytics and ranking. Results themselves are never stored. The questions asked through Search as and Answer as leave the audit log after the same period; the record of who looked at whom stays. | | Let Search app admins use "Search as" and "Answer as" | Search → Settings | Off | Hands **Search as** and **Answer as** to delegated Search app admins. Business admins always have both. Only a business admin can change it. | | Enable the Search Admin Agent | Search → Settings | Off | Lets admins ask Ask AI to report on search, run Search as or Answer as for a named person, and make three confirmed changes: add a synonym, promote a result, switch an area in or out. | | Route Search admin notices to this group | Search → Settings | Every business administrator | Sends the failing-source alert and the weekly nudge to a named group instead of the whole administrator roster. Search app admins are always kept. | | Send the weekly “people searched and opened nothing” nudge | Search → Settings | On | Monday morning Inbox notice listing searches at least two people ran five or more times in the last 30 days and opened nothing for. This switch stops it for everyone; each recipient can also mute their own copy under **Search · Administration** in their notification preferences, which mutes the failing-source alert too. | ## 6. More help - **[Search FAQ](/help/articles/search_app_faq)** — filters, limits, external sources, and what to do when a search does not find what someone expected - Ask AI — the assistant answers Search questions from these articles **Keywords:** search, global search, search results, can't find it, synonyms, promoted result, saved search, search alert, AI overview, live answer, meaning match, external sources, SharePoint search, Slack search, my connections, search analytics, search as, answer as, why does Ask AI answer differently --- # Search FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common questions about Search — filters, exact phrases, external sources, saved-search alerts, limits, and what to do when a search does not find what someone expected. # Search FAQ Answers to common questions about Search, for the people using it and the admins running it. For what Search is and how the pieces fit together, see the [Search Overview](/help/articles/search_app_overview). --- ## Setup ## Do I have to turn Search on before people can use it? No. The search box, the results page, Saved searches, and the My connections list with its **Disconnect** button work for everyone signed in, on every paid plan, with no admin action at all. What a licence governs is the admin pages, connecting a new external source, and whether Search appears in the side navigation. Every result is still permission-checked individually, so an ungated results page never shows anyone anything new. ## What do we need to set up before people can search an external system? Register the system at **Search → Sources**, then each person connects their own account at **Search → My connections**. What the source needs depends on the system: 1. **Microsoft 365** (SharePoint, OneDrive and Teams files) reuses the Entra ID app registration you already use for Microsoft sign-in or calendar sync, with the Search callback URL added as a redirect URI. 2. **Google Drive** can reuse your Google sign-in client, or carry its own. 3. **Confluence**, **Jira** and **ServiceNow** each need their own OAuth client ID and secret on the source, plus the site host (for example `yourcompany.atlassian.net`). 4. **Slack** needs its own Slack app's client ID and secret. There is no host to enter — the workspace is whichever one the person signs in to. 5. **Microsoft Teams messages**, **Box**, **Dropbox**, **Salesforce** and **Notion** each need their own OAuth client ID and secret on the source. Salesforce also needs your My Domain host and the one object the source searches; Dropbox asks whether to search file names or content. **Notion** searches only the page IDs you list, for one employee group you choose, and you confirm those pages may be shared with that group — its connection does not check each person's own Notion permissions. Registering the source is only half the job: until someone connects, that source returns nothing for them. ## Why is there no AI overview above my results? The overview needs three switches on, and any one of them removes the card: Search's own **Show an AI overview above results** (on by default), the Ask AI app being published to that person, and Ask AI's own company-knowledge switch. The overview is also deliberately skipped when a live answer is already the answer — a leave balance or a next shift needs no summary — and it never appears when the person is holding an **In** or **Only mine** filter. --- ## Permissions and access ## How does Search decide what a person can see? By what that person can already open. Search keeps no list of its own about who may see what: every area is searched with the person's own permissions, and ranking only reorders the rows those searches return. An area an admin keeps out of results in **Search → Settings** is left out for everyone. To check one person, an admin uses **Search → Search as** for what they would find, or **Search → Answer as** for what Ask AI would tell them. ## Can search show someone a document they are not allowed to open? No. Every area is queried with the person's own permissions, and ranking only reorders rows those queries already returned — it can never widen what someone sees. External systems make their own decision: the search runs as that person through their own sign-in, so they see exactly what they could see in SharePoint, Drive, Confluence, Jira, ServiceNow or Slack themselves. Notion is the exception: it shows only the shared pages an admin approved for the person's employee group. ## Who can open the Analytics, Synonyms, Promoted results, Sources, Search as and Settings pages? Business admins, and anyone made a Search app admin. Everyone else sees only the results page, Saved searches, and My connections. A Search app admin is granted at Admin → Apps → All Apps → Search → **Admins & Contributors**. **Search as and Answer as are the one exception.** A Search app admin gets Analytics, Synonyms, Promoted results, Sources and Settings, but not **Search as** or **Answer as** — reading what one named colleague can find, or what Ask AI would tell them, is held back from the delegated role by default. A business admin can hand both over with *Let Search app admins use "Search as" and "Answer as"* in Search → Settings; business admins themselves always have them. ## Can I see what my team searches for? Not by team. Analytics is admin-only and reports on the whole company — top searches, searches that found nothing, click-through by area, phone versus desktop — with no per-person or per-team breakdown. Individual search history is deliberately private: a person's recent searches are theirs, and are never turned into a company-wide "trending searches" list. ## Can I check what one of my people would find? Only an admin can. **Search → Search as** shows what one named person would get for a query, listed as titles by area, and private areas such as notes, HR files, pay and messages are counted but never listed. It shows up to five titles per area and nothing can be acted on from it. Every use is recorded. ## Why does the Sources page tell me to upgrade? External sources are a Platform Enterprise edition capability. The Sources page stays in the sidebar for admins on every plan and shows the upgrade state rather than disappearing, so you can see what it would do before you buy it. Everything else in Search works the same on every paid plan. --- ## Day-to-day ## How do I search for an exact phrase? Put the words in double quotes. `"radiation safety officer"` matches those three words together, in that order, and skips pages that merely mention all three somewhere. Without quotes, Search matches the words individually as it always has — including through your company's synonyms — which is usually what you want. ## What do the In, When and Only mine filters actually change? Each of the three narrows the page differently: - **In** runs one area only. External sources, the live answer, "People who can help" and the AI overview all stand down; meaning matches stay, but only from the area you picked. - **When** puts a date floor under everything. External sources keep running and are date-filtered too — an external result the system gives no date for is hidden rather than let through. The live answer, meaning matches, experts and the overview all stay. - **Only mine** shows your own rows and your own live answer. External sources, meaning matches, experts and the overview stand down. Under any filter, "Go to" shortcuts and "Did you mean" are switched off. A chip appears for each filter you set, and each chip removes only its own filter. The filters live in the page address, so a filtered page can be sent to someone else or reloaded unchanged. ## "How do I get told when something new turns up for a search I care about?" Run the search, choose **Save this search**, give it a name, and set alerts to Daily or Weekly. Alerts are **No alerts** unless you choose otherwise. The alert tells you about results the search has not shown you before — something new, or something that has started to match since (say, after an administrator adds a synonym) — and about later edits to results it has shown you. What the search found when you saved it is news only once it is edited. Alerts arrive in your Inbox and by email, listing up to 8 new rows with "…and N more" if there are others. ## "How do I connect Slack or SharePoint so my searches include them?" Go to **Search → My connections** and choose **Connect** beside the system. You sign in to that system once, in its own window, and from then on every search also asks it as you. You only see the systems an admin has registered, and the tab only appears once at least one exists. **Disconnect** deletes your sign-in for that source and nothing else. ## "Why does one result have an Acknowledge or Pick up button and another one doesn't?" Because the button appears only when the action is genuinely open to you right now. **Acknowledge** shows while your own acknowledgment is still pending; **Complete** shows on your own open task, and not when that task requires a completion photo; **Pick up** shows on an open shift with no claim already pending. The buttons are the same ones inside the owning app, with the same rules — Search does not grant anything. ## Should I add a synonym or promote a result? Add a **synonym** when people use a different word for the same thing — teaching Search that FY means Fiscal Year makes every area match both, for every search. Promote a result when the right page exists but keeps losing: a **promoted result** pins one specific page or link to the top for the words you choose and labels it **Promoted**. Promotions match whole phrases, so promoting "holiday schedule" does not fire on a search for "holiday". --- ## When something looks wrong ## "I searched for a document I know exists and it didn't come up" Work through these in order: 1. **Check the search itself.** Search needs at least two characters, and a quoted phrase must appear exactly as typed. 2. **Check for a filter.** A **When** filter hides anything Search cannot date; an **In** filter searches one area only. 3. **Check the area.** An admin may have switched that area off at **Search → Settings**, or excluded that file type. Content stays findable inside its own app either way. 4. **Check permissions.** Archived wikis and workspaces are out unless **Include archived content** is on, and deactivated people are out unless **Include deactivated people** is on. Otherwise the answer is usually a permission in the owning app — an admin can confirm with **Search as**. ## "Search asked 'Did you mean…' — where does that come from?" It appears when a search returns almost nothing, and it offers the nearest spelling that works. Two things feed it: searches other people here have already run successfully in the last 90 days, and the words in the few results and meaning matches your own search did find. That second source is why a first-ever misspelling still gets corrected — "radiaton safety" is offered "radiation safety" even if nobody has ever typed it here before. ## "My external source says Reconnect, or that it didn't answer in time" These are two different problems. **Reconnect** means your own sign-in to that system has expired or been withdrawn — choose it and sign in again; nobody else is affected. **Didn't answer in time** means the system itself was slow or unavailable on that search: every external source has a shared 4-second window to answer, and one that misses it becomes a labelled section rather than a failed page. Try the search again. If a source fails every search for 15 minutes, or at least five searches, and half of them, in the last hour, admins are told within the hour, in the Inbox and by email — failing for everyone usually means a rotated secret or a changed host. ## "People who can help didn't list the person who wrote the document" "People who can help" lists up to six people and puts content owners first when the search sounds like a question about ownership — words like "who wrote" or "who owns". Otherwise people matched on skills, job title, department or office lead. Three things keep someone off the list: you are never shown as your own expert, people already listed in the People section are not repeated, and only current, unexpired skill records count. ## "Why did the AI overview cite something from SharePoint?" Because the overview reads whatever the page reached. When external sources returned results for that search, the overview searches them again as you and may cite an external document alongside your OneMango documents; its label then reads "from company knowledge and" the source's name, and an external citation opens in a new tab. An overview that used only company knowledge is remembered for 10 minutes per person, so reloading the page does not rerun it; an overview that used external sources is never remembered, because those results are never stored. --- ## Licensing and limits ## Does Search need a licence, and who turns it on? Search is included with every paid plan and needs no admin opt-in — the results page runs for every signed-in person regardless. External sources are the one part gated separately: they need the Platform Enterprise edition. Sample data can be loaded and removed from **Search → Settings** without touching real activity. ## Are there limits I should know about? | What | Limit | |---|---| | Search length | 2 to 200 characters | | Rows shown per group | 5, then a **More … results (N)** link named for the group — **More Policies results (3)**; on the phone, every group is folded under **More by area** | | Top results | 4 across the whole page, at most 2 from any one group | | People who can help | 6 people, showing up to 3 current skills each | | "For you" on the page before you type | 3 rows per kind; tasks and shifts within the next 7 days | | External sources | all answer within one shared 4-second window; 10 results per source per search | | Saved searches | 30 per person; alerts are No alerts, Daily or Weekly; each alert lists 8 rows then "…and N more" | | Promoted results | up to 20 terms per promotion; title up to 200 characters; link up to 500 | | Synonyms | each term up to 120 characters | | Analytics | 7, 30 or 90 days; top 15 searches and top 15 zero-result searches | | Search as | 5 titles per area; business admins always, Search app admins only if switched on in Settings | | Search activity retention | 30, 90, 180 days or 1 year — 90 days by default | | Search API (`GET /api/v1/search`) | 20 results by default, 50 at most; read-only | Two more worth knowing. The "people here open this" ranking signal reads the last 90 days of clicks in your company only. The weekly admin nudge lists the top 5 searches that **at least two different people** ran five or more times in the last 30 days and nobody opened anything for — and an admin can switch it off in Search → Settings → Notifications. --- ## More help - [Search Overview](/help/articles/search_app_overview) — what Search is, how the pieces fit together, and the settings an admin owns - Press Cmd K on a Mac or Ctrl K elsewhere to jump to the search box from any page - Ask AI — the assistant answers Search questions from these articles **Keywords:** faq, search, can't find it, exact phrase, search filters, only mine, did you mean, saved search alert, my connections, reconnect, external sources, SharePoint, Slack, synonyms, promoted result, search as, search limits, retention --- # Security & Sign-On **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-13 Password policies, two-factor authentication, single sign-on (SAML, Google, Microsoft, OpenID Connect), session timeouts, account lockout and the authentication log: the admin guide to sign-in security. # Security & Sign-On ## 1. What it is Security & Sign-On is where you set the rules for getting into your organization. You set password rules, require two-factor authentication, add single sign-on (SSO) providers, control how long sessions last, and review who signed in and how. Every way in follows the policies you set here: password, SSO, a one-time code or a magic link. - **Where:** the **Security** section of the admin sidebar. **Sign-in Policies** and **SSO Configuration** need the Administrator role. **Sessions & Tokens** and **Authentication Log** appear only for a Super Admin. - **What it is not:** clock-in security (kiosk PINs, IP checks on punches, offsite clock-in) is a separate set of attendance settings, not part of this page. ## 2. Standing it up 1. Go to **Admin → Security → Sign-in Policies**. Every new organization starts with sensible defaults already on. Password complexity is enforced. Super Admins and Administrators must use two-factor authentication. People are signed out after 60 minutes of inactivity. 2. Review **Password Policies**. By default a password needs at least 8 characters, with uppercase letters, lowercase letters and numbers. Special characters are not required. Tighten this if your compliance framework asks for more. 3. Review **Two-Factor Authentication**. Turn on **Require Two-Factor Authentication for all users**, or tick roles under **Require only for specific roles**. People in a required role who have not enrolled are sent to the setup screen at their next sign-in. They are not locked out. 4. If you use SSO, go to **Admin → Security → SSO Configuration**. SSO is included in every edition. Add a provider: Google Workspace, SAML, Microsoft Entra ID, MangoApps or OpenID Connect. Test it, then enable it. A new configuration is off until you tick **Enable this configuration for login**. 5. Check the session limits. **Sign out after inactivity** defaults to 60 minutes. **Always sign out after** defaults to 24 hours. If you run shifts, consider a daily sign-out time between shifts (see §5). ## 3. How it fits together **Sign-in Policies vs SSO Configuration.** These are two separate pages that work together. Sign-in Policies set the rules for every way in: passwords, lockout, session length, two-factor and one-time codes. SSO Configuration manages the identity providers whose buttons appear on the login page. Someone who signs in through SSO is still signed out by your session limits. **Single sign-on providers.** There are five provider types: | Provider | What it is | |---|---| | Google Workspace | Sign in with a Google account | | SAML | Any SAML 2.0 identity provider, such as Okta, PingOne or ADFS | | Microsoft Entra ID | Sign in with a Microsoft work account | | MangoApps | Sign in with your MangoApps Hub account | | OpenID Connect | Any OpenID Connect identity provider your organization runs | You can add several configurations of one type, for example two SAML providers for two divisions. Every enabled configuration appears as its own button on the login page. Client secrets are stored encrypted and never shown again. **System default vs custom configuration.** For Google, SAML, Microsoft and MangoApps, MangoApps can supply a shared, ready-made configuration (the system default). You can use it, add your own custom configurations, or both. OpenID Connect is always your own: it is never offered as a system default, and it is only used for signing people in. **OpenID Connect presets.** When you pick OpenID Connect, you choose an **Identity provider**: Okta, Ping Identity, Auth0, OneLogin or **Other OpenID Connect provider**. The preset only pre-fills the form and names the login button — for example, an Okta configuration shows as "Okta". Every preset signs people in the same way. **Sign-in accounts (connecting your own Microsoft account).** A person can connect their own Microsoft account to their profile. Your organization must have Microsoft Entra ID sign-in set up. They go to **Account settings › Security**, open **Sign-in accounts**, and click **Connect Microsoft account**. An administrator can't link one person by hand. Two rules protect the person: - An account your organization created shows **Managed by your organization** and can't be disconnected there. - Nobody can disconnect their only way in. They must set a password or get another way in first. **Confirm it's you (step-up).** Some actions ask a person to prove it is still them, even though they are signed in. Changing your own password or PIN is one. So is connecting or disconnecting a sign-in account. The person enters their current password or PIN, or clicks **Confirm it's you**. That confirmation lasts 15 minutes. Someone who signs in with SSO can sign in to their provider again instead. If the provider can't confirm a fresh sign-in, they get a one-time code. Without a confirmation, the new password or PIN is not saved and the page says why. Worked example: an employee who signs in with Microsoft wants to set a PIN. They open the **Security & Password** card on their profile and click **Confirm it's you**. They sign in to Microsoft again, enter the new PIN and save. **Two-factor authentication.** Two-factor uses an authenticator app. People scan a QR code to enrol, get 10 one-time backup codes, and enter a 6-digit code at each sign-in. Service accounts are always exempt, because they cannot answer a challenge. Signing in with a one-time code skips two-factor, because the code is itself the second factor. **Session lifetime.** Three limits apply, and whichever comes first ends the session: - **Inactivity:** signs someone out after a period with no activity (default 60 minutes). - **Hours limit:** signs them out after a fixed number of hours, however busy they are (default 24). - **Daily sign-out time:** optional. Signs everyone out at one local time each day. **Account lockout.** After too many failed sign-ins (default 5), the account is locked for 60 minutes. A completed password reset ends the lock early. Trying again while locked does not restart the clock. A locked account cannot use a one-time code either. **One-time code sign-in.** People can sign in with a 6-digit code sent to their email or phone, instead of a password. It is on by default. **Authentication log.** This is a record of every sign-in, sign-out, failed attempt and expired session. Each entry shows how the person signed in, their IP address, browser and portal. Entries cannot be edited or deleted. They are kept for 395 days by default. ## 4. Running it ### Adding an SSO provider 1. Go to **Admin → Security → SSO Configuration** and click **New Custom SSO Configuration**. 2. Give it a **Name** and choose a **Provider Type**. 3. Enter the provider's details: - **SAML:** choose **Paste XML Metadata** and paste your provider's metadata. The sign-in URL and certificate are read from it automatically. Copy the service-provider values shown on the form into your identity provider. - **Google Workspace:** enter your OAuth `client_id` and `client_secret` in **Provider Settings (Google OAuth JSON)**. - **Microsoft Entra ID:** enter the app registration's client ID, client secret and directory (tenant) ID, as JSON, in the provider settings box. - **OpenID Connect:** pick the **Identity provider**, then fill in **Issuer URL**, **Client ID** and **Client secret**. Leave **Scopes** at `openid profile email` unless you map groups. Copy the **Redirect URI** into your provider. Also copy the **Mobile app redirect URI** if people use the mobile or desktop app. 4. Tick **Enable this configuration for login** and save. 5. Open the configuration and click **Test Configuration**. For OpenID Connect, the test checks your provider's discovery document, sign-in endpoints and signing keys. 6. The **SSO Configurations** page previews the login page, showing exactly which SSO buttons people see right now. For OpenID Connect, the **Initiate login URI** appears after you save. Paste it into your provider to let people start from its app tile, such as the Okta dashboard. ### Choosing system or custom configurations Click **Settings** on the SSO Configurations page. For each provider, switch it on or off and choose whether to **Include System Default**. You can also turn on automatic account creation. When it is on, anyone whose email is on your **Allowed email domains** list gets an account at their first SSO sign-in. For Microsoft sign-in, that domain list also decides who is matched to an existing account by email. People who connected their own Microsoft account keep signing in either way. ### Reviewing SSO logs 1. On the SSO Configurations page, open a configuration's menu and click **View Logs**. Or open a configuration and click **View all SSO logs**. 2. Filter by **Configuration**, **Status**, **From** and **To**. 3. Each entry shows whether the attempt worked and which configuration it used. Use it to debug a misconfigured provider. ### Checking NIST compliance Sign-in Policies shows a **NIST 800-63B (AAL2)** badge. It is green when two things are true: inactivity is 60 minutes or less, and the hours limit is 24 or less. Otherwise it reads "Outside AAL2" and lists the settings responsible. You are shown the tradeoff, not blocked. ### Signing people out or revoking API tokens 1. Go to **Admin → Security → Sessions & Tokens** (Super Admin only). 2. Find a person and click **Sign out** to end their sessions everywhere. 3. To sign out everyone, type your subdomain to confirm, then click **Sign everyone out**. Your own sessions are kept unless you tick **Include my own sessions**. 4. Click **Revoke** beside an API token to stop it at once. Any integration using it stops working. ### Reviewing the authentication log 1. Go to **Admin → Security → Authentication Log** (Super Admin only). 2. Filter by event, outcome and date, or search by name, email or IP address. 3. Export to CSV for compliance evidence. ## 5. Settings All of these are on **Admin → Security → Sign-in Policies**. | Setting | Default | What it changes | |---|---|---| | Require Two-Factor Authentication for all users | Off | Everyone must enrol in two-factor at their next sign-in | | Require only for specific roles | Super Admin and Administrator ticked | Roles that must enrol even when the switch above is off | | Enforce password complexity requirements | On | Whether the password rules below apply | | Minimum password length | 8 | Fewest characters a password can have | | Require uppercase / lowercase letters / numbers | All on | Character types a password must include | | Require special characters | Off | Whether a password must include a symbol | | Password expiration (days) | 0 (never) | Days before a password must be changed | | Maximum failed login attempts | 5 | Failed sign-ins before the account locks for 60 minutes | | Sign out after inactivity (minutes) | Blank: 60 minutes | Minutes with no activity before sign-out | | Always sign out after (hours) | Blank: 24 hours | Longest a session lasts, however active | | Also sign everyone out every day at | Blank (off) | A local time each day when every session ends | | Keep the authentication log for (days) | Blank: 395 days | How long sign-in records are kept | | Allow Self-Registration | Off | Anyone with your registration link can create an account. There is no approval step: it is active at once | | Enable OTP Login (Login with Code) | On | Whether people can sign in with a one-time code | | Enforce IP address restrictions | Off | People can sign in with a password or a one-time code in a browser (computer or phone) only from IP addresses you allow, and the Office add-in and the MangoApps CLI can finish signing in only from them. Single sign-on and the native mobile app are not filtered. A refused sign-in appears in the authentication log | ## 6. More help - **[Security & Sign-On FAQ](/help/articles/admin_security_and_signon_faq)**: exact limits and ranges, two-factor setup, SSO troubleshooting, and "why can't I sign in" questions. - **Users, Roles & Permissions**: who can access the platform and what they can do. - Ask AI: the assistant answers questions about sign-in security from these articles. **Keywords:** security settings, sign-in policies, password policy, two-factor authentication, 2FA, MFA, SSO, SAML, single sign-on, OpenID Connect, OIDC, Okta, Ping Identity, Auth0, OneLogin, session timeout, daily sign-out, account lockout, password expiration, OTP login, authentication log, IP restrictions, Google Workspace SSO, Microsoft Entra ID, connect Microsoft account, confirm it's you, change my password, change my PIN, self-registration --- # Security & Sign-On FAQ **Category:** Faq **Section:** Administration **Updated:** 2026-10-16 Answers to common setup and operating questions about password policies, two-factor authentication, SSO (SAML, Microsoft, Google, OpenID Connect), session timeouts, account lockout and authentication logging — for the admin running it, and the people signing in. # Security & Sign-On FAQ Answers to common setup and operating questions about Security & Sign-On. For what it is and how to set it up from scratch, see the [Security & Sign-On Overview](/help/articles/admin_security_and_signon). --- ## Setup ## Do I need to configure password rules before they take effect? No. Password complexity is enforced from the start. A password needs at least 8 characters, with uppercase letters, lowercase letters and numbers. Special characters are not required by default. Passwords never expire by default (**Password expiration (days)** is 0). Change any of these at **Admin → Sign-in Policies**. ## Which roles must use two-factor authentication by default? Super Admin and Administrator. People in these roles must enrol at their next sign-in, even when **Require Two-Factor Authentication for all users** is off. Change the list under **Require only for specific roles** on the Sign-in Policies page. Service accounts are always exempt, because they cannot answer an interactive challenge. ## How do I add Okta, Ping, Auth0, OneLogin or another OpenID Connect provider? Add it as an **OpenID Connect** configuration at **Admin → SSO Configuration**. 1. Click **New Configuration** and choose **OpenID Connect** as the Provider Type. 2. Under **Identity provider**, pick Okta, Ping Identity, Auth0, OneLogin or **Other OpenID Connect provider**. The choice pre-fills the form and names the button on the login page. 3. Enter the **Issuer URL**, **Client ID** and **Client secret**. The issuer must be a plain `https://` address with no query or fragment. 4. Copy the **Redirect URI** shown on the form into your identity provider. Also copy the **Mobile app redirect URI** if people sign in from the mobile or desktop app. 5. Save, click **Test**, then enable the configuration. The **Initiate login URI** appears after you save; it lets people start from the provider's own app tile, such as the Okta dashboard. The client secret is stored encrypted and never shown again. An OpenID Connect configuration always belongs to your organization — it cannot be a shared system configuration or an API-only integration. --- ## Permissions and access ## Who can sign people out, revoke API tokens or read the authentication log? Only Super Admins. **Sessions & Tokens** and **Authentication Log** appear in the Admin menu's Security section only for Super Admins, and both pages refuse anyone else. Administrators can view and change the Sign-in Policies and SSO Configuration pages. ## Does configuring SSO require a specific Platform edition? No. SSO and SCIM provisioning are included in every edition — Platform Lite, Standard and Enterprise. Administrators can open the SSO Configuration and SSO Logs pages in any edition. --- ## Day-to-day ## Can I run more than one SSO provider at the same time? Yes. You can mix provider types — for example SAML for one division and OpenID Connect for another — and add several of the same type. Every enabled configuration appears as its own button on the login page. The SSO Configuration page includes a login page preview showing exactly which buttons people see right now. ## Is there an SSO widget for our other apps (Workday, ADP, Salesforce…)? Yes — it is the app launcher. Each person sees tiles for the other apps they use, and a sign-in tile opens the app already signed in through your identity provider, in a new tab. The tiles come from two places: - **Apps your identity provider assigns.** Connect Okta, Microsoft Entra ID or OneLogin at **Admin → Integrations → Identity Providers** and turn on its **App launcher**. Each person then sees the apps assigned to them there. - **Tiles you add.** At **Admin → Quick Action Shortcuts**, add a shortcut whose destination is the app's sign-in link from your identity provider, and set **Opens in** to **Sign in through your identity provider**. Add a logo, and choose who sees it. The tiles show on the App Launcher card on the Home dashboard, in Quick Actions, on the Apps page, in the phone's Apps grid, in search, and on a Sites page through the Quick Links block. A shortcut can also open a particular page inside an app that OneMango signs people in to. See [App Launcher & Sign-in Tiles](/help/articles/admin_app_launcher). ## Can OneMango be the sign-in for our other apps, without Okta or Microsoft? Yes. OneMango can be the SAML identity provider itself for any app that accepts SAML sign-in. Go to **Admin → Integrations → Identity Providers → Manage apps**, give the app OneMango's metadata address, add the app, and choose who may sign in. People then open it signed in from its tile, or by going to the app directly. See section 7 of [App Launcher & Sign-in Tiles](/help/articles/admin_app_launcher). ## What happens when I require two-factor authentication for everyone? People who have not enrolled are sent to the two-factor setup screen at their next sign-in — they are not locked out. They scan a QR code with an authenticator app and receive 10 one-time backup codes. Each backup code is 8 characters and works once. Until they confirm a 6-digit code from the app, they cannot get past the setup screen. Someone who signs in with a one-time code sent to their email or phone is not asked for an authenticator code — that code counts as the second factor. ## How do I reset someone's two-factor authentication after they lose their phone? Go to **Admin → Users**, open the person's row menu, and choose **Disable 2FA**. This clears their authenticator and backup codes. If their role still requires two-factor, they set it up again at their next sign-in. Only a Super Admin can disable a Super Admin's two-factor authentication, and you cannot disable your own here. If the person still has a backup code, they can sign in with it instead. ## What does the NIST AAL2 badge on the Sign-in Policies page mean? It shows whether your session settings meet NIST 800-63B AAL2. That means an inactivity timeout of 60 minutes or less and an absolute timeout of 24 hours or less. If any setting goes past those limits, the badge reads "Outside AAL2" and lists each reason. Nothing is blocked — the badge only reports. ## Can people register themselves without an admin creating their account? Only if you turn on **Allow Self-Registration** on the Sign-in Policies page; it is off by default. There is no approval step. Anyone with your registration link gets an active account straight away, joins as a Member, and has the password emailed to them. Share the link only where you would be comfortable granting access. ## Why is it asking me to confirm it's me before I change my password or PIN? To change your own password or PIN, you first confirm your identity. On the Security & Password card, type your current password or PIN in **Current password or PIN**, then enter the new one. If you sign in with your organization's single sign-on and don't know a password, click **Confirm it's you** first. That check accepts your password, your PIN, a fresh single sign-on or a one-time code. A successful check lasts 15 minutes. After 5 wrong tries, the check is locked for 15 minutes. If you save without confirming, your old password or PIN stays in place and the page tells you why. ## How do I connect my Microsoft account so I can sign in with Microsoft? Go to **Account settings → Security** and find the **Sign-in accounts** card. Click **Connect Microsoft account**, confirm it's you, then sign in to Microsoft. The card appears only when your organization has Microsoft Entra ID sign-in set up and enabled. You can disconnect an account you connected yourself, but not your only way in. An account marked **Managed by your organization** can only be changed by an admin. --- ## When something looks wrong ## "I can't log in — it says my account is locked" The person went past the maximum number of failed sign-in attempts (5 by default). A lock lasts 60 minutes and clears on its own; this duration is fixed and not a setting. Trying again while locked does not restart the clock. Completing a password reset ends the lock early. A locked account cannot sign in with a one-time code either. ## "I'm being asked for a verification code and I don't know what that is" Two-factor authentication is required for the person's role. They set up an authenticator app, such as Google Authenticator or Microsoft Authenticator, by scanning the QR code on the setup screen. If they set it up before and lost their phone, they can enter one of their backup codes instead. An admin can also reset it with **Disable 2FA** on Admin → Users. ## "The SSO button isn't showing on the login page" Check three things: 1. At least one configuration for that provider is enabled at **Admin → SSO Configuration**, and its **Test** passes. 2. The provider is not switched off on the **SSO Settings** page. 3. It is a sign-in configuration, not one marked **API only** — those never appear on the login page. The login page preview on the SSO Configuration page shows the buttons people see right now. ## "Microsoft sign-in says it couldn't confirm my email address belongs to my organization" This happens with a Microsoft sign-in that serves more than one Microsoft tenant, when Microsoft can't vouch for the email address. The person signs in another way first, such as their email address. Then they connect Microsoft under **Account settings → Security → Sign-in accounts**, and Microsoft works from then on. An admin can instead add the person's email domain to the allowed email domains on that Microsoft Entra ID configuration. ## "I keep getting signed out" Check the session settings on the Sign-in Policies page: - **Sign out after inactivity (minutes)** — 60 minutes unless you set another value. - **Always sign out after (hours)** — 24 hours by default; it signs people out even while they are active. - **Also sign everyone out every day at** — optional; a set time ends every session at that time in your business's time zone. There is no "Remember me" option. When a session ends, people sign in again. ## "The one-time sign-in code I received isn't working" Codes expire after 15 minutes by email or 10 minutes by text message. After 5 wrong entries, the code stops working and the person must request a new one. People can request 3 codes per 5 minutes, with a 60-second wait between resends. If **Enable OTP Login (Login with Code)** is off, the sign-in-with-code option does not appear at all. ## "Our SSO was working and now it's failing" Open the configuration at **Admin → SSO Configuration** and click **Test**. For SAML, the test warns when the identity provider's certificate expires within 30 days. It reports "Certificate EXPIRED on [date]" once it has, and the fix is to paste the new certificate from your identity provider. For OpenID Connect, the test reads the provider's discovery document, sign-in endpoints and signing keys live, so a changed issuer or rotated setup shows up there. **Admin → SSO Logs** lists each attempt with the configuration it used, which isolates the broken one when several are active. --- ## Licensing and limits ## What are the allowed ranges for password, session and log settings? | Setting | Allowed range | |---|---| | Minimum password length | 8–64 characters | | Password expiration | 0 (never) to 365 days | | Maximum failed login attempts | 1–10 | | Account lockout | 60 minutes (fixed) | | Sign out after inactivity | 5–10,080 minutes (up to 7 days) | | Always sign out after | 1–720 hours (up to 30 days) | | Remember for | 1–90 days | | Keep the authentication log for | 30–2,555 days (about 7 years) | The authentication log keeps 395 days (13 months) unless you set another value. Entries older than your setting are pruned once a day. An authentication log export is capped at 50,000 rows. --- ## More help - [Security & Sign-On Overview](/help/articles/admin_security_and_signon) - [Users, Roles & Permissions](/help/articles/admin_users_and_roles) - Ask AI — the assistant answers security and sign-on questions from these articles. **Keywords:** faq, security settings, sign-in policies, password policy, two-factor authentication, 2FA, MFA, SSO, SAML, single sign-on, OpenID Connect, OIDC, Okta, Ping Identity, Auth0, OneLogin, Microsoft Entra ID, connect Microsoft account, confirm it's you, change password, change PIN, session timeout, account lockout, account locked, OTP login, SSO widget, app launcher, enterprise apps, one-time code, authentication log, self-registration, NIST --- # Service Accounts & API Credentials **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-13 How to create and manage non-human service accounts, issue and rotate API tokens, and enforce IP and device restrictions. # Service Accounts & API Credentials ## 1. What it is Service accounts are non-human user principals used for API integrations, automation bots, and AI agent attribution. Each service account has its own identity, role, and API tokens — separate from any human user's credentials. This keeps integration access auditable and revocable without touching a person's account. - **Enablement:** Service accounts are a built-in admin feature — no marketplace app licence is required. - **What it is not:** A service account is not a shared login for a team. It cannot be assigned the Super Admin role, and it does not count toward your human user seats. ## 2. Standing it up 1. Go to **Admin → Security → Service Accounts** (the admin sidebar, under the Security section). 2. Click **New Service Account** and fill in: - **Name** — a descriptive label (must be unique among service accounts in your business). - **Purpose** — Automation (API/integration principal) or AI agent (in-product attribution). - **Access level** — Read-only (default) limits all tokens on this account to `read:` scopes only. Read-write allows any scope. - **Login** — Token only (default, recommended) blocks all interactive web/SSO login. Web + token also allows browser login, subject to IP and device restrictions. - **Role** — Member (default), Manager, or Admin. This is the platform role for permission checks; API power comes from token scopes, not the role. - **Description** — free-text note visible on the account detail page. 3. After creation, go to the account's detail page and **issue an API token** (see §4 below). The account exists but cannot authenticate until it has at least one active token. 4. Confirm the integration works by checking the token's **Last used** timestamp on the detail page. **Silent-until-configured:** a service account with no active tokens cannot call any API endpoint. Creating the account alone does not grant API access. **No edit or delete in the admin UI.** Once created, a service account's Access level, Login, Purpose and Role cannot be changed. There is no delete action — to decommission an account, revoke all its tokens. If different settings are needed, create a new account and migrate the integration. ## 3. How it fits together **A service account is a user, flagged as a system account.** Under the hood it is an ordinary user record marked as a system account, with a companion profile holding its service-account settings. It has a synthetic email address on the `.invalid` top-level domain (guaranteed undeliverable), a random password it never uses, and is excluded from: - The normal user directory and user-count reports. - All notification delivery — notifications stop before they reach a service account. - All email delivery — the `.invalid` address is caught by the outbound mail guard. - Two-factor authentication requirements — service accounts are always exempt. This means service accounts do not consume user seats and will never generate stray notifications or emails. **Access level is a ceiling, not a grant.** The Access level (Read-only or Read-write) chosen for the account is an upper bound over every token on it. A read-only account's tokens can only hold `read:` scopes — the system refuses to save a token with any non-`read:` scope. A read-write account's tokens can hold any scope, but each token still declares its own explicit scope list. **Tokens require explicit scopes.** Unlike personal API tokens (where blank scopes means full access), service account tokens must declare at least one scope. This prevents accidental full-access grants. Two broad scopes are available: `admin` grants access to all endpoints, and `read:all` grants every `read:` scope. **Token authentication is two-part.** Each token has both a token ID and a secret. Both are shown once at issuance and stored as SHA-256 digests — neither can be retrieved afterward. API requests must present both values. A request with only the token and no secret will not authenticate. **Purposes.** Each account has a purpose that describes how it is used: - **Automation** — the default; used for API integrations and bots. - **AI agent** — carries attribution for in-product agent actions. Created automatically by the platform when an agent first runs (one per business, named "AI Agent"). - **Chat assistant** — the "@Ask AI" reply principal in the Chat app. Created automatically; identified by purpose, so renaming the assistant's display name does not break resolution. Admins create Automation accounts manually. AI agent and Chat assistant accounts are provisioned automatically on first use and do not need manual setup. **Name uniqueness.** Service account names must be unique within a business — the platform enforces this at the storage layer, so duplicates cannot be created. The rule applies only among service accounts; a service account can share a display name with a human user. ## 4. Running it ### Issuing a token 1. Open the service account's detail page (**Admin → Security → Service Accounts → click the account**). 2. In the **Issue a token** section, enter a token name, choose an expiry (30 days, 90 days, 1 year, or never), and select the scopes this token should have. 3. Click **Issue**. The plaintext token and secret are shown once in an alert banner at the top of the page. Copy both immediately — they are stored as SHA-256 digests and cannot be retrieved again. The integration authenticates by presenting both the token and the secret. Either value alone is not sufficient. The form offers permissions two ways. **Permission sets** tick what one job needs in a click: **Read only** (view everything, change nothing), **Publish training courses**, and **Full access**, which only a Super Admin can grant. Below them is one row per app or area with **Read**, **Write** and **Delete** boxes — the apps your business has switched on first, then people, settings and shared areas, then broad permissions such as `read:all` and the MCP scopes for agent tools. Where a permission also comes in a form limited to the account's own records, an **own only** box sits under the main one. Search narrows the rows by app name or scope code, **Select all shown** and **Clear all** act on what is listed, and a line above the table says what the token will be able to do. The permissions offered depend on the account's Access level — a Read-only account is offered only `read:` scopes, and only the Read only set. ### Rotating a token On the account's detail page, click **Rotate** next to the active token. This issues a replacement token with the same name, scopes, and expiry, then immediately revokes the old one. The new plaintext credentials are shown once. ### Revoking a token Click **Revoke** next to any active token. Revocation is immediate — the token's expiry is moved to the current moment. Revoked tokens remain visible in the list with a "Revoked" status badge. ### Configuring IP restrictions On the account's detail page, under **Access restrictions**: 1. Enable **IP restricted** to require that all API requests (and web logins, if allowed) come from specific IP addresses or CIDR ranges. 2. Enter allowed IP ranges, one per line. 3. Optionally enable **Include business IP ranges** to also accept the IP ranges configured at the business level (under Admin → Security). IP enforcement is fail-closed: if IP restriction is enabled and no ranges match, the request is rejected. This applies at both the API layer and the web login layer. The API returns: ``` 403 Forbidden — error code: ip_not_allowed ``` ### Configuring device restrictions Device restriction is available only for accounts with **Web + token** login. When enabled, a web login attempt from an unrecognized device is blocked. The device appears as "recognized" on the account's detail page, and an admin must click **Trust** to promote it to verified status before the account can log in from that device. ### Monitoring token expiry A daily background job (runs at 7:30 AM UTC) checks for service account tokens expiring within 14 days. Admins and super admins receive an in-app notification at two windows: 14 days and 3 days before expiry. Each reminder fires once per token per admin per window — it does not repeat daily within a window. The notification links directly to the account's detail page where the token can be rotated. ### How web login works for service accounts When a service account's **Login** is set to **Web + token**, the account can log in through the normal password form. However, several restrictions apply: - **Token-only accounts** are always blocked from web login — on both the password form and any SSO/magic-link path. - **IP-restricted accounts** are blocked if the request IP is not in the effective allowlist. - **Device-restricted accounts** are blocked if the browser's device is not yet trusted. The login attempt registers the device as "recognized", and an admin must explicitly trust it from the account's detail page before the next login attempt will succeed. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Access level | Set at creation | Read-only | Ceiling on token scopes — Read-only accounts can only hold `read:` scopes | | Login | Set at creation | Token only | Whether the account can also log in interactively via web/SSO | | Role | Set at creation | Member | Platform role for permission checks (Member, Manager or Admin — never Super Admin) | | IP restricted | Account detail → Access restrictions | Off | When on, API requests and web logins must come from an allowed IP | | Include business IP ranges | Account detail → Access restrictions | On | When IP restricted, also accept the business-wide IP allowlist | | Device restricted | Account detail → Access restrictions | Off | When on (web+token accounts only), web login requires admin-approved device | Access level, Login and Role are set at creation and cannot be changed through the admin UI afterward. To change these, create a new service account with the desired settings, migrate your integration to the new account's tokens, then leave the old account's tokens revoked. **Defaults are applied by the platform, not the form:** every new account starts at Read-only access, Token only login, IP restricted off, Include business IP ranges on, and Device restricted off. These defaults are applied at the storage layer — they hold regardless of what the form shows. ## 6. More help - **Service Accounts FAQ** — specific setup and operating questions (not yet published) - **Admin → Security → API Keys & Access** — personal API tokens for human users (separate from service account tokens) - Service account API tokens are subject to the same rate limits as all API tokens (per-token and per-IP throttles). - Ask AI — the assistant answers questions about service accounts from this article. **Keywords:** service account, api token, api key, api credentials, service account token, api access, bot account, integration account, non-human principal, token rotation, ip restriction, device restriction, api scopes, read only api, service account login --- # Service Desk App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run Service Desk — ticketing, knowledge base, SLA tracking, and the ITSM modules (Changes, Problems, CMDB, Access Requests, Grievances). # Service Desk ## 1. What it is Service Desk is a ticketing and IT service management app where employees submit requests and agents resolve them. It includes a knowledge base, SLA tracking, team-based routing, and optional ITSM modules — Change Management, Problem Management, a Configuration Management Database (CMDB), Access Requests, and Grievances. - **Enablement:** Licensed and opt-in. An admin enables it from **Admin → Apps → All Apps** and grants the licence. - **What it is not:** Service Desk is not the Ask AI assistant. Ask AI can search Service Desk's knowledge base to answer employees before a ticket is opened, but the two are separate apps with separate licences. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Service Desk**, and enable it. 2. Go to **Service Desk → Settings → Routing → Teams & Agents**. Create at least one support team and add agents to it. Without a team, tickets stay unassigned in the Available queue. 3. Still in Settings, open **Intake → Email Channel**. The email channel is on by default — confirm the inbound address. AI processing lives under **Advanced → AI**; decide whether to turn it on (it is off by default). 4. Under **Settings → Advanced → Knowledge Base**, confirm the Knowledge Base is on (it is by default). Optionally turn on additional modules under **Settings → Advanced → Modules** — Problem Management, Change Management, CMDB, and Access Requests are all on by default; Grievances is off by default. 5. To grant agent rights, add a user to a support team. Users who are members of at least one active support team — or who carry the legacy help-desk-agent flag — are recognised as agents. 6. Confirm it worked: agents should land on the **Dashboard** when they open Service Desk; members should see the **Help** hub with a **Submit a Request** card. ## 3. How it fits together **Tickets** — the core work item. An employee submits a ticket (from the web, mobile, email, API, Microsoft Teams, or a recurring schedule), it enters the queue, gets routed to a team or agent, and moves through statuses: Submitted → Queued → Assigned → In Progress → Resolved → Closed. Tickets can also be Pending Approval, Cancelled, or Rejected, and any open ticket can be flagged Escalated without changing its status. Priorities are Low, Medium, High, and Critical. **Teams and routing** — a support team is a pool of agents with a shared queue. When team-based routing is enabled (the default), incoming tickets are matched to teams by routing rules — conditions based on request type, priority, location, keywords, or AI-detected intent. Within a team, tickets are distributed by round-robin. When routing is disabled, tickets are assigned directly to individual agents. **Knowledge Base** — articles, documents, uploaded files, and crawled web pages that agents and AI draw on to resolve tickets. Content can require approval before publishing. The knowledge base supports role-based access tiers: content can be restricted so that only agents, managers, or admins see certain articles, while members see the rest. **ITSM modules** — each is individually toggleable: - **Change Management** — tracks changes through a lifecycle from Draft → Pending Review → In CAB Review → Approved → Scheduled → Implementing → Implemented → Closed. A change the CAB sends back shows as **Returned**. Changes have types (Standard, Normal, Emergency), a risk level, and can be routed through a Change Advisory Board (CAB) for review. Emergency changes can go straight to the CAB chair. - **Problem Management** — tracks recurring issues from Identified → Investigating → Root Cause Found → Fix in Progress → Resolved → Closed. Problems link to the tickets (incidents) they caused and to CMDB configuration items. Any problem that is not closed can be published as a Known Error once it has a workaround, so agents can apply the workaround while the fix is pending. - **CMDB** — a registry of configuration items (services, servers, applications, databases, networks, storage) and their relationships. CI records link to related problems and change requests so agents can see the downstream impact of an outage. - **Access Requests** — a self-service flow where employees request access to a location, workspace, site, support team, app, or equipment category. Requests go through an approval queue — or resolve instantly when the tenant's zero-touch policy matches (for example, a location request from someone already assigned to a location in the same city is auto-approved by default). - **Grievances** — a multi-stage escalation workflow that progresses through Filed → Acknowledged → Immediate Supervisor → Department Head → HR Director → Arbitration → Resolved → Closed, each stage with its own SLA window. This module is off by default. **Roles** — four levels determine what a user sees: | Role | Who qualifies | What they see | |---|---|---| | **Member** | Everyone else | Help hub, My Requests, and — when those modules are on — Changes, Grievances, and Access Requests | | **Manager** | Manages a support team but is not an agent | Member surfaces plus Tickets, Changes, Grievances, Analytics | | **Agent** | Members of an active support team (or legacy agent flag) | Dashboard, Knowledge Base, all enabled ITSM modules, Access Requests | | **Admin** | Business admin or Service Desk app admin | Everything: Dashboard, Tickets, all ITSM modules, Analytics, Settings | ## 4. Running it ### Reviewing and working the queue Agents open the **Dashboard** to see their assigned tickets, workload summary (open count, overdue count, capacity utilisation), and the Available queue of unassigned tickets. Agents can **Claim** an unassigned ticket to take ownership or **Assign** it to another agent. ### Managing SLAs SLA targets are set per priority in **Settings → Routing → Priorities & SLA**. Each one is the time a ticket has to be resolved. The defaults are 4 hours for Critical, 8 for High, 24 for Medium (Normal), and 72 for Low, and a service department can set its own hours, which take precedence. The clock starts when a ticket is assigned (or when it is submitted, if nobody has it yet); a ticket not resolved by then is flagged as breached. A changed target applies to new tickets and to existing tickets when they are next assigned. ### Escalating a ticket Escalation flags a ticket without changing its status. By default, the escalation is routed to the requester's manager; an admin can change this to route to Service Desk app admins instead. A ticket nobody has replied to goes to a higher-tier agent first, when there is one. A ticket escalates on its own when its agent has not replied within the escalation timeout, or when it is still open that long after missing its SLA target. The timeout defaults to 24 hours. Grievances are never escalated on their own. ### Auto-closing resolved tickets By default, resolved tickets auto-close after 5 days of inactivity. A reminder is sent 2 days before the close date. Admins can adjust or disable this in **Settings → Features**. ### Merging duplicate tickets Agents and admins can merge a duplicate ticket into a canonical one. The source ticket's requester becomes a follower of the target, and the source is cancelled with a merge note. ### Running a satisfaction survey When enabled (on by default), a satisfaction survey email is sent to the requester after a ticket is resolved. The default delay is 2 hours after resolution. ### Recurring tickets Service Desk app admins and business admins can create recurring ticket rules that generate new tickets on a schedule — daily, weekly, biweekly, monthly, quarterly, or yearly; agents can view them from **Recurring Tickets** in the sidebar. Useful for periodic maintenance or scheduled check-ins. ## 5. Settings Settings are organised into four sections, accessed from the Settings tab (admin only). ### Intake | Setting | Default | What it changes | |---|---|---| | Email channel | On | Whether inbound emails create tickets | | Allow unknown senders | On | Whether emails from addresses not matching any employee create a ticket (as an unidentified requester) or are dropped | | Require request category | On | Whether a category is required when submitting a ticket | | Anonymous requests | Off | Whether employees can submit tickets without their name attached | ### Routing | Setting | Default | What it changes | |---|---|---| | Team-based routing | On | Whether tickets are routed to teams via rules, or directly to individual agents | | Routing rules | On | Whether the routing rule engine evaluates conditions on incoming tickets | | Auto-assign | On | Whether tickets are automatically assigned to an agent (vs. sitting in the queue) | | Assignment method | Round-robin | How tickets are distributed among agents in a team | | Max concurrent tickets per agent | 5 | The cap on open tickets an agent can hold before new tickets go to the next agent | | Escalation | On | Whether unanswered assigned tickets, and tickets past their SLA target, escalate after the timeout (never grievances) | | Escalation timeout | 24 hours | How long a ticket can go unanswered, or past its SLA target, before it escalates | | Escalation target | Requester's manager | Who is notified on escalation — the requester's manager or Service Desk app admins (an unanswered ticket goes to a higher-tier agent first, when there is one) | | SLA per priority (Priorities & SLA) | Critical 4h, High 8h, Medium 24h, Low 72h | Time-to-resolve targets by priority level, counted from assignment | ### Features | Setting | Default | What it changes | |---|---|---| | Auto-close resolved tickets | On, after 5 days | Whether resolved tickets automatically close after a period of inactivity | | Satisfaction survey | On, 2-hour delay | Whether a satisfaction survey is sent after resolution, and when | | Ticket tasks | Off | Whether agents can attach a task checklist to a ticket | | Ticket retention purge | Off | Whether closed and cancelled tickets older than the configured window are permanently deleted | ### Advanced — Modules | Setting | Default | What it changes | |---|---|---| | Problem Management | On | Enables the Problems tab for tracking root-cause investigations | | Change Management | On | Enables the Changes tab for tracking infrastructure and process changes | | CMDB | On | Enables the CMDB tab for managing configuration items and their relationships | | Access Requests | On | Enables the Access Requests tab for self-service access requests and approvals | | Location auto-approve policy | Same city | Zero-touch policy for location access requests — Off, Same city, Same state, or Any existing assignment | | Grievances | Off | Enables the Grievances tab for multi-stage grievance workflows | ### Advanced — Knowledge Base | Setting | Default | What it changes | |---|---|---| | Knowledge Base | On | Whether the Knowledge Base tab and content are available | | KB content approval | Required | Whether new knowledge base content needs approval before publishing. Approvers (admins and app admins) always publish directly | | KB content creation permission | Admins only | Who can create KB content — admins only, or all users | | Suggest KB content on submit | On | Whether relevant KB articles are suggested when an employee starts a ticket | ### Advanced — AI | Setting | Default | What it changes | |---|---|---| | AI processing | Off | Master toggle for AI classification, priority detection, routing, and sensitive-content detection on incoming tickets | | AI response mode | Manual only | How AI reply drafts get created (needs AI draft generation on): **Manual only** (agents press Generate AI Draft when they want one), **Draft for review** (AI drafts every arriving request; an agent approves before it sends), or **Auto-send** (AI sends the reply itself when it is confident) | ## 6. More help - **Service Desk FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about Service Desk from these articles. **Keywords:** service desk, help desk, ticketing, ITSM, support tickets, knowledge base, SLA, change management, problem management, CMDB, access requests, grievance, IT support, ticket routing, service-desk, service_desk --- # Service Desk FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Service Desk — for the admin running it, the managers who approve, and the employees who file requests. # Service Desk FAQ Answers to common setup and operating questions about Service Desk. For what the app is and how to set it up from scratch, see the [Service Desk Overview](/help/articles/service_desk_app_overview). --- ## Setup ## Do I need to create support teams before tickets can be routed? Yes, while team-based routing is on, and it is on by default. A new ticket that no team matches stays unassigned in the Available queue, and Service Desk admins are notified that it could not be routed. Either create at least one support team with active members before tickets arrive, or turn team-based routing off so tickets are assigned straight to agents by the Assignment Strategy. ## What roles exist in Service Desk and what does each one see? There are four roles, and each gets its own sidebar: - **Admin** — a business admin, or anyone granted the Service Desk app-admin role. Sees the Dashboard, Tickets, My Requests, Knowledge Base, every enabled module, Analytics and Settings. - **Agent** — an active member of a support team. Sees the Dashboard, their own Tickets workbench, My Requests, Knowledge Base and every enabled module. - **Manager** — manages a support team but is not an agent. Sees Help, Knowledge Base, My Requests, their teams' Tickets, Analytics, and the Changes, Grievances and Access Requests modules when those are on. - **Member** — everyone else. Sees Help and My Requests, plus Changes, Grievances and Access Requests when each module is on. Members open the Knowledge Base from the Help page. ## Which ITSM modules are on by default? Problem Management, Change Management, CMDB and Automated Access Requests are **on** by default. Grievance Tracking is **off** and must be turned on in Settings → Advanced → Modules. Each module can be switched on or off independently, and its sidebar link appears or disappears with it. --- ## Permissions and access ## Why can't an employee see a ticket they were told about? Only people connected to the ticket can open it. That means the requester, the person who filed it on their behalf, the assignee, anyone it was escalated to, the requester's own manager, the person approving it, and its followers. Agents and admins can open any ticket. Anyone else needs to be added as a follower from the ticket page. ## Who can see every ticket in the organization? Agents, Service Desk app admins and business admins can always see every ticket. Everyone else sees only the tickets they are involved in. To widen that, change **Who can see every ticket in the organization?** in Settings → Features → General. It can be set to all managers or to specific people. ## Can I hide the assignee or priority from the person who submitted a ticket? Yes. Turn on **Hide Assignee from Requester** or **Hide Priority from Requester** in Settings → Features → General. Both are off by default. Once on, agents, admins, people allowed to see every ticket, and the assignee still see the field; the requester does not. With priority hidden, tickets filed by requesters get your Global Default Priority, and any priority they choose is ignored. ## Who can create a ticket on behalf of another employee? The **"Requesting For" Field Visibility** setting in Settings → Features → General decides this. The default is **Agents & Admins**. You can change it to **Admins Only** or **All Users**. --- ## Day-to-day ## How does auto-assignment decide who gets a ticket? With team-based routing on (the default), your routing rules pick the team first, and then an agent within that team. Without teams, the **Assignment Strategy** in Settings → Routing → Assignment picks the agent. The options are **Round Robin** (the default), **Workload Based**, **Expertise Based** and **Location Based**. Auto-assignment respects **Max Concurrent Tickets per Agent**, which defaults to 5 and accepts 1–20. ## What happens when a ticket breaches its SLA? The ticket is flagged as breached, and the assignee and the relevant managers are notified. The default SLA targets are **Critical** 4 hours, **High** 8 hours, **Medium** 24 hours and **Low** 72 hours, set in Settings → Routing → Priorities & SLA. A breach does not change the assignee. If the ticket is still open when the **Escalation Timeout** (24 hours by default) has passed since the breach, it is escalated once, to the person **Escalate To** names, unless someone escalated or de-escalated it since the breach. Both are in Settings → Routing → Assignment, and Escalate To chooses between the submitter's manager (the default) and Service Desk admins. Turn **Enable Escalation** off to stop automatic escalation. An agent or admin can also escalate an open ticket by hand with Escalate. Grievances are never escalated this way. While **Auto-flag overdue grievance stages for escalation** is on (the default), an overdue grievance stage is flagged to the person who owns that stage. ## How does auto-close work for resolved tickets? A ticket left in Resolved is closed automatically after **5 days** by default. **Enable Auto-Close** is on by default and is found in Settings → Features → Workflow. **Close After (days)** accepts 1–60. The requester gets a reminder **2 days** before the ticket closes, adjustable from 0 to 30 days. Once a ticket has closed, the requester, the assignee or an admin can reopen it. ## Can I require approval before a ticket is worked? Yes. In Settings → Features → Workflow, choose which request types need approval. You can also set a **Budget Approval Threshold ($)**, which defaults to $500. Any ticket with an estimated cost above that amount needs approval too. By default the requester's own reporting-line manager approves; you can change this to Service Desk admins or specific people. Service Desk app admins and business admins can always approve. ## How do recurring tickets work? A recurring ticket creates a new ticket on a **daily, weekly, biweekly, monthly, quarterly or yearly** schedule, at a set time of day and timezone. You can stop it after a number of tickets (**Max Tickets**) or on an end date. **Skip if previous ticket is still open** holds back the next ticket while the last one is unresolved. Only Service Desk app admins and business admins can create, edit or pause recurring tickets; agents can view them. ## Why can't I submit my change request for review? A change request needs its plans filled in before **Submit for Review** will go through. Every change needs an **Implementation Plan**. **Normal** and **Emergency** changes also need a **Rollback Plan**, while a **Standard** change does not. If a plan is missing, the change page names it and links to Edit so you can add it before you click Submit. ## Why did my emergency change go to review instead of being approved straight away? Only agents, admins and the chair of the change's review board can fast-track an Emergency change on submit. When anyone else submits one, it goes through normal review with its priority and emergency justification intact. An Emergency change always needs an **Emergency Justification**. ## I filed a grievance — where can I see how it's going? Open **Grievances** in the Service Desk sidebar. The link appears for everyone while Grievance Tracking is on. It lists your own grievances with each one's stage and deadline. Only you, the assigned handler and your grievance handlers can see it. Your own manager cannot see it just by being your manager. ## Who handles grievances? By default, Service Desk app admins and business admins read and work every grievance. Most organisations change **Who can read and work grievances?** to specific people and name their HR or employee-relations group. Set it in the grievance settings, which appear under Settings → Advanced → Modules once Grievance Tracking is on. The person who filed a grievance and its assigned handler always keep access to it. --- ## When something looks wrong ## "I resolved a ticket but the requester says they can't close it" **Feedback Required for Closure** (Settings → Features → Workflow) is probably on. It is off by default. While it is on, requesters must give a satisfaction rating from 1 to 5 before they can close their own ticket. Agents and admins closing the ticket are not affected, so ask the requester to rate it first, or close it yourself. ## "An agent filed a ticket for themselves and now they can't work it" **Prevent Self-Service on Own Tickets** (Settings → Features → General) is on. It stops admins and agents from starting, resolving or closing a ticket they submitted themselves, so another agent has to handle it. Ordinary employees are never blocked from their own tickets. Turn the setting off, or reassign the ticket. ## "Tickets are arriving by email but they're all categorised as General" AI triage is off. Inbound email is only categorised automatically when **Let AI triage requests as they arrive** is on (it is off by default) and **Auto-classify request type** is checked. Both are in Settings → Advanced → AI. Without them, email tickets land as General for your team to triage. A category picked on the request form still applies either way. ## "A manager says they can't see the Problems or CMDB tab" Problem Management and CMDB are open only to agents and admins. A manager who is not an agent does not get either one. Add the manager to a support team, or give them the Service Desk app-admin role. ## "Internal notes are visible to the requester" They should not be. Internal notes are visible only to agents, admins and the ticket's assignee. If a requester can see a note, it was most likely posted as a normal reply rather than marked internal. A public reply cannot be turned into an internal note afterwards. --- ## Licensing and limits ## Does Service Desk require a licence? Yes. Service Desk requires a licence, and an admin turns it on for your organisation from Admin → Apps → All Apps. It is off until an admin enables it. ## Are there limits I should know about? | Item | Limit | |---|---| | Ticket title | 3–255 characters | | Ticket description | at least 10 characters, when the description is required | | Comment | up to 20,000 characters | | Attachments per ticket | 5 by default (adjustable 1–20) | | Attachment size, email channel | 25 MB by default | | Satisfaction rating | 1–5 | | Max concurrent tickets per agent | 5 by default (adjustable 1–20) | | Support team tier levels | 1–5 | | Support team capacity | 50 by default | | Time logged per entry | up to 1,440 minutes (24 hours) | | Knowledge Base bulk-import file | 10 MB | | Ticket CSV import file | 10 MB | | Saved reply | up to 10,000 characters | | Auto-close window | 5 days by default (adjustable 1–60) | | Closed-ticket retention | off by default; when on, 12 months by default and never less than 3 months | | Custom field types | Text, Text Area, Number, Email, URL, Dropdown, Multi-Select, Radio Buttons, Checkbox, Date, Info Block | | Access request targets | Location, Workspace, Site, Support Team, App, Equipment | | Access request roles | Member, Manager, Co Manager | --- ## More help - [Service Desk Overview](/help/articles/service_desk_app_overview) - Ask AI — the assistant answers Service Desk questions from these articles. **Keywords:** faq, service desk, help desk, ticketing, SLA, knowledge base, ITSM, support teams, ticket routing, escalation, auto-close, approval, access requests, change management, change request, submit for review, rollback plan, implementation plan, grievance, CMDB, not showing, permissions, service-desk, service_desk --- # Settings Hub & Navigation **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-16 How the Settings Hub, admin sidebar, and sidebar app rail work — searching settings, browsing by category, pinning apps, and finding any admin surface. # Settings Hub & Navigation ## 1. What it is The Settings Hub is the searchable directory of every admin setting in the platform. Instead of remembering which menu holds a particular configuration page, you search or browse from one place. It also serves as the AI's grounding for "where do I find…" questions — the same registry that powers the Settings Hub page powers the Platform Help agent's answers. This article also covers the admin sidebar and the sidebar app rail — the left-hand navigation that organises the platform into zones (Home, Apps, Admin) and lets you pin frequently used apps for one-click access. - **Access:** Admin → Organization → Settings Hub. Requires the Administrator or Super Admin role. - **What it is not:** The Settings Hub does not change settings itself — it is a directory that links to the page where each setting lives. To actually change a setting, click through to the destination. ## 2. Standing it up The Settings Hub and sidebar navigation work immediately — there is no setup. Any user with the Administrator or Super Admin role sees the Admin zone in the sidebar and can open the Settings Hub from Admin → Organization → Settings Hub. 1. Go to **Admin → Organization → Settings Hub**. You see a search bar, a Quick Access row of common settings, and collapsible categories. 2. Type a keyword (e.g. "leave", "sso", "email") into the search bar. Results appear after two characters, ranked by relevance. Each result links directly to the configuration page. 3. If Ask AI is enabled for your business, click the **Ask AI** button or one of the suggested questions. The AI is hard-bound to the Platform Help agent on this page, so every question routes to the settings and navigation tools rather than falling through to a general-purpose answer. 4. To browse, expand a category card. Each item shows its title, a one-line description, and links directly to the configuration page. ## 3. How it fits together **Settings Registry** — Every tile in the Settings Hub comes from a single central registry. The registry defines the title, description, search keywords, destination page, required permission, and optional feature gate for each item. When an item is gated on a feature (e.g. the Attendance Settings tile is gated on the Time & Attendance app being enabled), the tile is hidden while that feature is off — so admins never see a link to a page they cannot use. The same registry backs Settings Hub search, the Platform Help agent's answers about where a setting lives, and the Quick Access row. All three surfaces always agree because they read one source. **Four categories** — The registry groups settings into four categories: - **Organization Settings** — Business Profile, Departments, Locations, Users, Roles, SSO, Security, Brand & Theme, Integrations, and other structural configuration. - **Operational Settings** — Billing & Payments, General Settings, Attendance, Shifts, Notifications, Content Moderation, Compliance, Audit Logs, Workforce Intelligence, AI Operations, and day-to-day configuration. - **App Settings** — One tile per enabled marketplace app that has a settings page. This category is populated dynamically from the apps your business has enabled. - **Data Import Center** — Every importer in one place: employee import, attendance import, shift import, leave balance import, compensation import, Smart Import targets, and scheduled import jobs. **Sidebar zones** — The left sidebar has three zones: Home, Apps, and Admin. Each zone has an icon in the rail (house, rocket, gear). The Admin zone only appears for users with the Administrator or Super Admin role. Within the Admin zone, settings are grouped into sections: General Settings, Organization, Security, Apps, AI Operations, Compliance, and Super Admin. **Pinned apps** — Admins can pin up to 7 apps to the sidebar rail so they appear as icons below the zone icons. Pinning is business-wide by default (set from Admin → All Apps via the pin toggle), but each user can personalise their own rail — their selection replaces the business default entirely. When the user's personal list is empty, the business default takes over — so unpinning every app restores the business rail rather than leaving it blank. **Admin sidebar sections** — Inside the Admin zone, the sidebar is divided into collapsible sections. Each section is gated by role — most require Administrator or Super Admin, while the Super Admin section and certain items within Security (Sessions & Tokens, Authentication Log, Maintenance & Lockdown) require Super Admin specifically. | Section | What it holds | |---|---| | General Settings | Billing & Payments, General Settings, Roles, Groups, Notifications, Content Moderation, Governance, Translation, Approval Workflows, Audit Logs, Workforce Intelligence | | Organization | Settings Hub, Business Profile, Departments, Locations, Users, Job Titles & Families, Dashboard Builder, Engagement, Quick Actions, QR Posters, Integrations, Bring Your Data | | Security | Sign-in Policies, SSO, Service Accounts, API Keys, plus Sessions & Tokens / Authentication Log / Maintenance & Lockdown (Super Admin only) | | Apps | All Apps, Widget Gallery, Custom Apps, App Pipeline, App Health | | AI Operations | Overview, Approvals, Action History, Agents, Channels, Agent Settings, Trust & Safety | | Compliance | Work Policy Settings, Labor Law Rules, Employment Law Rules, Jurisdictions, Jurisdiction Mapping, Compliance Explorer, Compliance Audit Logs (Platform Enterprise edition), Employment Law Audit History | | Super Admin | App Data Management, Sample Data (Super Admin only) | **Global search** — The platform's top-nav search bar also queries the settings registry. When an admin types a setting name into the global search, up to five matching settings appear alongside other results, linking directly to the configuration page. **Brand & Theme** — Admin → General Settings → Brand & Theme. Colors, logo and favicon, the sign-in page, navigation, surfaces, fonts, mobile app colors and Custom CSS, applied together with **Apply Theme**. Changes apply business-wide; **Rail Colors by Group** gives one group its own left navigation colors. ## 4. Running it ### Searching for a setting 1. Go to **Admin → Organization → Settings Hub**. 2. Type at least two characters into the search bar. Results appear within 300ms, grouped by category. 3. Click any result to go directly to that configuration page. Search matches against the item's title (highest weight), description, keywords, and sub-page names. If no results match, the page suggests asking AI instead. ### Asking AI where a setting lives 1. On the Settings Hub page, click **Ask AI** or type a question into a suggested chip (e.g. "Where do I change the leave policy?"). 2. The AI sidebar opens with your question pre-filled. Press send. The Platform Help agent searches the settings registry and navigation shortcuts to answer. The AI is hard-bound to the Platform Help agent on this page, so questions about settings always route to the right tools rather than falling through to a generic fallback. ### Browsing by category 1. On the Settings Hub page, scroll past the search bar to the category cards. 2. Click a category header to expand it. Each item shows its name and description. 3. Click an item to navigate to its configuration page. You can deep-link to a specific category by appending a category parameter to the URL — the linked category is expanded and scrolled to when the page opens. For example, to land on the Data Import Center: ``` /admin/settings_hub?category=data_imports ``` ### Navigating the admin sidebar 1. Click the **gear icon** at the bottom of the sidebar rail to open the Admin zone. 2. The admin panel shows collapsible sections (General Settings, Organization, Security, Apps, AI Operations, Compliance, Super Admin). Click a section header to expand or collapse it. 3. Click any item to navigate to that admin page. The Admin zone only appears for users with the Administrator or Super Admin role. If a user does not have either role, the gear icon is not shown. ### Pinning an app to the sidebar rail 1. Go to **Admin → Apps → All Apps**. 2. Find the app you want to pin. Use the pin toggle on the app's row. 3. The app icon appears in the sidebar rail for all users who have not personalised their rail. The rail holds a maximum of 7 pinned apps — if all 7 slots are full, unpin one first. An app must be enabled before it can be pinned. Pinning a disabled app is rejected. When an admin first enables an app, the app arrives pinned or unpinned according to its own platform-wide default. Most apps default to not pinned. ### Personalising your own app rail 1. In the sidebar, click the **Apps** zone icon (rocket). 2. In the Apps panel, click the pin icon next to any app to add or remove it from your personal rail. 3. Your personal rail replaces the business-wide default entirely. Unpinning your last app restores the business default. Your personal rail is stored on your membership and persists across sessions. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Business-wide pinned apps | Admin → All Apps → pin toggle per app | Not pinned | Which apps appear in the sidebar rail for all users who have not personalised | | Per-user pinned apps | Sidebar → Apps panel → pin icon | Empty — the business default is used | Replaces the business rail with this user's own selection | | Max pinned apps | Fixed platform limit | 7 | The sidebar rail holds at most 7 pinned app icons | | Quick Access items | Settings Hub page | 6 common settings | The chips shown below the search bar for one-click access | | Admin zone visibility | Automatic | Visible for Admin and Super Admin roles | Whether the gear icon appears in the sidebar rail | ## 6. More help - **Business Profile & General Settings** — configuring your company details - **Enabling Apps, Licences & Plugins** — turning apps on and off, managing licences - **Security & Sign-On** — SSO, password policies, session timeouts - Ask AI — the assistant answers "where do I find…" questions using the same registry as the Settings Hub. **Keywords:** settings hub, settings search, find a setting, admin sidebar, navigation, left sidebar, sidenav, pinned apps, pin app, admin navigation, where is, admin zones, sidebar, settings categories, app settings --- # Share FAQ **Category:** Faq **Section:** Advanced Features **Updated:** 2026-10-16 How Share sends a ticket, account, recap or post to a colleague, a chat, a text, or a Teams, Slack, MangoApps Hub or MCP place — and how to take it back. # Share FAQ **Share** sends a link to a record — a Service Desk ticket or comment, a Mango CS account or recap, or a Workspace post — to a place where people will see it. It is on the record's page, on the desktop and on the phone. ## Sending ## What does the other person see? The record's title, the line you write in "Say something" (optional, up to 500 characters), a link back to the record, and who shared it. The record's body, description and comments never leave. An internal note, a Workspace post kept from members or clients, and a grievance go out with no title at all — only your line and the link. ## Where can I share to? The places your company has turned on: **Email a colleague**, **OneMango chat** (a room you are in, or a new direct message), **Text a colleague**, and any Teams or Slack channel, MangoApps Hub group or MCP server an admin connected. The panel lists only what you can post to. ## Who can I send it to? Only colleagues who can open the record themselves. Share checks this before sending and tells you if they cannot, with your line kept. A text also needs a verified mobile number, and each one uses the company's platform credits. Nobody is emailed or texted who turned that off in their own settings. ## Why does it say "Already sent"? The same record went to the same place, with the same title, in the last ten minutes — a second press is treated as a double click. If you deleted the first post there, press **Remove** on its "Shared to" line, then share again. ## It says "It may have arrived". What do I do? The other system took the post but did not answer in time. Check that place before you share again, so it does not arrive twice. ## Afterwards ## Where can I see where something went? Under the record, a "Shared to" line lists each place, who sent it and when. A shared comment carries its own line under the comment. ## How do I take a share back? Press **Remove** on its "Shared to" line. The person who shared it and admins can remove it. A OneMango chat message is deleted from the room, and a Teams or Slack post or a MangoApps Hub post is deleted there when that system allows it. An email or a text cannot be recalled: Remove takes the line off the page, and says so before you confirm. ## What happens if the record is deleted? A deleted ticket, comment or recap takes its "Shared to" lines with it — a ticket takes its comments' too. What was sent stays where it went, and its link stops working; the delete confirmation says so when something was shared. A Workspace post moved to Trash keeps its lines, and its link works again if the post is restored. ## For admins ## How do I turn sharing on? Under **Admin › Integrations**. Email, OneMango chat, Teams, Slack and MangoApps Hub are switched on the **Messaging** page; email is on until you turn it off, and so is chat once the Chat app is on. An MCP server is switched on its own page, on its **Sharing** card: pick the tool that posts, fill in which of its inputs takes the link back (and the place id, when a tool lists places), then turn Sharing on. Texts follow the company's SMS setting. ## Can people only see the channels they belong to? Yes, for Teams and Slack: on the connection's page, turn on **Only offer channels the sender belongs to**. Channels a sender is not in are left out of their list. ## More help - [Integrations FAQ](platform_integrations_faq) **Keywords:** faq, share, sharing, share a ticket, share to Teams, share to Slack, email a colleague, text a colleague, OneMango chat, MangoApps Hub, MCP, remove a share, already sent --- # Shift Feedback App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How Shift Feedback collects post-shift ratings, tags, and comments tied to each attendance record, and how to configure collection, notifications, and analytics. # Shift Feedback ## 1. What it is Shift Feedback collects a quick rating from employees right after they check out of a shift. Each submission is tied to a specific attendance record and includes a 1–5 star rating, an optional descriptive tag (such as "Understaffed" or "Good team"), and an optional written comment. Managers are notified immediately (with **Who Can Read Feedback** set to administrators only, just those who can open it) — when a rating falls at or below a threshold you set, a low-rating alert goes out in place of the routine notice. Notices about an anonymous submission go out on a quarter hour of the clock, at least 15 minutes after the shift's last check-out (or, if someone stays clocked in, within 12 hours of the shift's end or of the rating, whichever comes first) — or, for a rating sent after that, on the hour at least an hour later — so their timing doesn't point to one person. **Enablement:** Shift Feedback is a licensed app. An admin enables it from Admin → Apps → All Apps, then configures collection rules under the app's **Settings** tab. **What it is not:** Shift Feedback is not a general-purpose survey tool. It captures one response per employee per completed shift, prompted at check-out time. For broader employee surveys, use the Surveys app. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps → Shift Feedback** and enable the app for your business. 2. Open the **Settings** tab inside the Shift Feedback app. Confirm that **Enable Feedback Collection** is on (it defaults to on). Without this toggle, the app is installed but employees are never prompted. 3. Review the **Feedback Window** setting. This controls how long after a shift checkout an employee can still submit feedback. The default is **1 week (168 hours)**. The reminder delay set under **Send the Reminder After** must be shorter than this window. If you pick a combination where it is not (for example a 24-hour window with a 48-hour delay), the reminder job clamps the delay to just inside the window and logs that it did, so reminders keep going out rather than stopping silently — but the Settings page still shows the value you picked, so set the two deliberately. 4. Under **Notification Settings**, confirm **Notify Managers of New Feedback** and **Alert on Low Ratings** are on (both default to on). Set the **Low Rating Alert Threshold** to the star level that should trigger a low-rating alert to managers (default is **2 stars or below**). 5. Verify it works: have a test employee complete a shift and check out. On their Attendance page and on the Shift Feedback **Home** tab, a "How were your recent shifts?" card should appear listing that shift with a **Give Feedback** button. After they submit, the shift's manager should receive a notification. **Silent-dependency warning:** Shift Feedback relies on completed attendance records. If your employees are not checking in and out (through the web, the mobile app, or a time-clock kiosk), there are no attendance records to attach feedback to, and the app has nothing to collect. ## 3. How it fits together **Feedback and attendance records.** Every feedback submission is linked to exactly one attendance record, which in turn belongs to one shift. An employee can submit feedback only once per attendance record. This one-to-one link means each rating maps to a specific shift on a specific date at a specific location, so managers can trace a low rating back to exactly what was happening that day. **Eligibility rules.** Not every completed shift is eligible for feedback. The system considers three factors: the employee must have checked out, the checkout must fall within the **Feedback Window** (default 1 week), and the shift must be among the employee's most recent completed shifts up to the **Maximum Feedback Eligible Shifts** limit (default 3). Ad-hoc shifts and early checkouts are excluded by default; you can include them under **Shift Type Exclusions** in Settings. For example, if an employee completes shifts on Monday, Tuesday, and Wednesday, and the limit is 3, all three are eligible. If they complete a fourth on Thursday without having submitted feedback for Monday, Monday drops off the eligible list and only Tuesday, Wednesday, and Thursday appear. **Tags.** Each submission can carry one primary tag from a predefined set: Busy, Calm, Stressful, Understaffed, Well managed, Equipment issues, Technical problems, Good team, and Difficult customers. If **Allow Custom Tags** is on, the feedback form also shows a free-text field where the submitter can type a tag of up to 50 characters. Tags appear in the All Shift Feedback list and in trend analysis. **Anonymous submissions.** When **Allow Anonymous Feedback** is on (the default), the feedback form includes a "Submit anonymously" toggle. Anonymous submissions never show the sender's name — not in the All Shift Feedback list, the detail view, CSV exports or Ask AI responses. Managers see "Anonymous" in place of the employee name, and see an anonymous submission at all only for a shift at least five people worked (more if your company raised its smallest group size). Admins and Shift Feedback app admins see every anonymous submission, with its shift, location and when it was sent — on a small shift, that is enough to tell who sent it. The form tells the worker this beside the **Submit anonymously** switch. **Mango Signal integration.** Every feedback submission is sent to Mango Signal as a sentiment signal. The 1–5 rating is mapped onto Mango Signal's −1 to 1 sentiment scale, with 3 stars as neutral. Anonymous submissions are segmented separately and recorded with their day only, not the time they were sent. This means shift-level sentiment appears in the cross-app workforce analytics layer without any extra configuration. ## 4. Running it ### Reviewing feedback Managers and admins see an **All Shift Feedback** tab with a filterable list of every submission they are allowed to see. Filters include rating (including **Low ratings**, everything at or below your Low Rating Alert Threshold), location, and the date it was submitted. Summary stats at the top show total feedback count, unique employees, and average rating — all scoped to the active filters. Each row shows the date it was submitted, employee name (or "Anonymous"), shift and location, star rating, tags, and a preview of any written comment. Click a row to open the full detail view with the complete written feedback. **Who can see what:** admins and Shift Feedback app admins see all feedback across the business. Managers see feedback from the locations their organizational role covers together with feedback from their own direct reports, wherever those people worked. Regular employees see only their own submissions on the Home tab. ### Exporting feedback data From the **All Shift Feedback** tab, click **Export CSV** to download all submissions matching the current filters. The export button only appears when **Enable Data Export** is on in Settings. ### Understanding trends When **Enable Trend Analysis** is on, the All Shift Feedback page shows company administrators and Shift Feedback app admins a **Feedback Trends** panel with AI-generated insights — alerts for declining ratings, rising negative tags, and weekly rating charts. This uses the same analytics infrastructure as other OneMango insight panels. ### Using Ask AI The Shift Feedback agent lets users interact with feedback data through Ask AI. Employees can ask about their own feedback history. Managers can ask for a period's feedback summary (to compare periods, ask for each) and specific submission details scoped to their team. The agent can also submit feedback on the employee's behalf for an eligible shift if asked. The agent is on by default. Disable it from the **Shift Feedback Agent** card at the top of Settings. ### Mobile and kiosk Employees can submit feedback from the mobile app at **/m/apps/shift-feedback**, which shows their feedback history, eligible shifts, and a submission form. On time-clock kiosks, the feedback prompt appears automatically after clock-out. The employee sees the rating tiles, optional tag selector, optional anonymous toggle, and a notes field right on the kiosk screen — no separate navigation required. The kiosk respects all the same configuration toggles as the web form (feedback collection, tags, anonymity, ad-hoc exclusion). ## 5. Settings All settings are under **Shift Feedback → Settings**. ### Feedback Collection Settings | Setting | Default | What it changes | |---|---|---| | **Enable Feedback Collection** | On | Master switch. When off, no employee is prompted and no submission is accepted — on any surface. | | **Require Rating** | On | When on, the star rating is mandatory. When off, employees can submit tags and comments without a rating. | | **Maximum Feedback Eligible Shifts** | 3 shifts | How many of the employee's most recent completed shifts are eligible for feedback at any given time. | | **Feedback Window** | 168 hours (1 week) | How long after checkout the employee can still submit feedback for that shift. | | **Allow Anonymous Feedback** | On | Shows the "Submit anonymously" toggle on the feedback form. | | **Screen Feedback for Offensive Content** | On | Checks submitted comments and custom tags against your company's content rules before they are saved. Turning this off stores what employees write without screening it. | ### Shift Type Exclusions | Setting | Default | What it changes | |---|---|---| | **Collect Feedback on Ad-Hoc Shifts** | Off | When off, ad-hoc (unscheduled) shifts are excluded from feedback eligibility. | | **Collect Feedback on Early Checkouts** | Off | When off, shifts where the employee checked out more than 1 hour before the scheduled end are excluded. | ### Feedback Tags Settings | Setting | Default | What it changes | |---|---|---| | **Enable Feedback Tags** | On | Shows the tag selector on the feedback form. When off, only rating and free-text comment are collected. | | **Allow Custom Tags** | Off | Adds a free-text "Add a custom tag" field to the form so employees can name something the default tags don't cover. Custom tags are limited to 50 characters. | ### Notification Settings | Setting | Default | What it changes | |---|---|---| | **Notify Managers of New Feedback** | On | Sends an in-app notification to the shift's managers (or, for a shift with none, its location's admins) and, for named feedback, the employee's direct manager when feedback is submitted. | | **Alert on Low Ratings** | On | In place of the new-feedback notice, sends a notification and a mobile push to the same managers when a rating is at or below the threshold. | | **Low Rating Alert Threshold** | 2 stars or below | The rating at or below which the low-rating alert fires. | | **Send Feedback Reminders** | On | Sends a notification and a mobile push to employees who have eligible shifts without feedback. The job runs hourly and honours the delay set below. | | **Send the Reminder After** | 48 hours after check-out | How long after check-out the single reminder is sent. Each shift is reminded at most once. A longer delay means more employees submit on their own first and are never reminded at all. | ### Analytics and Reporting | Setting | Default | What it changes | |---|---|---| | **Show Feedback Statistics** | On | Shows the rating and response-rate figures on Home and All Shift Feedback, and lets Ask AI answer questions about them. When off, those numbers are hidden from everyone, including managers, and the agent's summary tool refuses. | | **Show Response Rates** | On | Adds a Response Rate card (last 30 days) to the stat strips. | | **Enable Trend Analysis** | On | Shows the AI-generated Feedback Trends panel on the All Shift Feedback page to company administrators and Shift Feedback app admins. | | **Enable Data Export** | On | Shows the Export CSV button on the All Shift Feedback page. When off, CSV export is blocked on both the app and legacy admin endpoints. | ### AI Agent | Setting | Default | What it changes | |---|---|---| | **Enable AI Agent** | On | When off, the Shift Feedback agent is unavailable in Ask AI. | ### API access Shift Feedback has a REST API at `/api/v1/shift_feedbacks`. Employees can list their own feedback, submit new feedback, update or delete submissions within 24 hours, and query which shifts are eligible. API tokens require the `read:shift_feedback` or `write:shift_feedback` scope. ## 6. More help - **Shift Feedback FAQ** — specific setup and operating questions. - Ask AI — the assistant answers questions about Shift Feedback from these articles. **Keywords:** shift feedback, shift rating, post-shift survey, employee sentiment, feedback collection, shift experience, anonymous feedback, low rating alert, feedback tags, feedback trends, shift-feedback, shift_feedback --- # Shift Feedback FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-14 Answers to common setup and operating questions about Shift Feedback — for the admin running it. # Shift Feedback FAQ Answers to common setup and operating questions about Shift Feedback. For what the app is and how to set it up from scratch, see the [Shift Feedback Overview](/help/articles/shift_feedback_app_overview). --- ## Setup ## Do I need to configure anything before employees can submit feedback? No. Once the app is enabled, feedback collection is on by default with sensible defaults: rating required, anonymous submissions allowed, tags enabled, and reminders on. The three most recent completed shifts are eligible, and the submission window is one week after checkout. You can change any of these under **Settings**, but nothing blocks employees from submitting on day one. ## Who can access the Settings page? Admins, and anyone an admin makes a Shift Feedback **app admin**. The Settings tab appears in the Shift Feedback sidebar only for them; managers and regular employees don't see it. An app admin can change every setting except feedback collection, anonymous feedback, content screening, the AI agent and who can read feedback, which stay with admins. --- ## Permissions and access ## Who can see All Shift Feedback and export data? Managers and above, unless an admin has narrowed it to administrators under **Settings**. Admins see feedback across the entire business, and so does anyone an admin makes a Shift Feedback **app admin** — whichever option is chosen. The **Who Can Read Feedback** card in **Settings** links to **Apps → Shift Feedback → Admins & Contributors**, where an admin grants that role; an app admin can also change the app's settings, except feedback collection, anonymous feedback, content screening, the AI agent and who can read feedback. Each manager sees two sets of feedback together: - **Their locations:** feedback from everyone who worked a shift at a location they oversee through their organizational role. - **Their team:** feedback from their own direct reports, wherever those people worked. Anonymous feedback is shown to a manager only for a shift at one of their locations that at least five people worked (more if your company raised its smallest group size) — never because the writer reports to them. CSV export follows the same visibility rules. The export itself is controlled by the **Enable Data Export** toggle under **Settings > Analytics and Reporting**. ## Why can a manager only see feedback from some employees? A manager sees feedback from the locations their organizational role covers and from their own direct reports — nothing else. If a manager should see more, assign them to additional locations, grant a broader organizational role, or update who reports to them. --- ## Day-to-day ## When does the feedback prompt appear? The feedback form is offered right after an employee checks out from a completed shift. The employee can also return to it from the Shift Feedback Home page for any shift still within the submission window. By default, ad-hoc shifts and early checkouts are excluded. An early checkout is one that happens more than one hour before the scheduled shift end. You can include either or both under **Settings > Shift Type Exclusions** with the **Collect Feedback on Ad-Hoc Shifts** and **Collect Feedback on Early Checkouts** toggles. ## What are feedback tags, and can employees create their own? Tags are short shift-experience labels employees choose when submitting. There are nine built-in tags: Busy, Calm, Stressful, Understaffed, Well Managed, Equipment Issues, Technical Problems, Good Team, and Difficult Customers. You can turn tags off entirely with **Enable Feedback Tags** in Settings. You can also allow employees to type a custom tag (up to 50 characters) by enabling **Allow Custom Tags**. Custom tags are off by default. ## How does anonymous feedback work? When **Allow Anonymous Feedback** is on (the default), employees see a checkbox to submit anonymously. Anonymous submissions are never attributed to the person anywhere — the dashboard, the detail view, notifications, and the AI agent all show "Anonymous." A manager sees an anonymous submission only for a shift at one of their locations that at least five people worked (more if your company raised its smallest group size). Admins and Shift Feedback app admins see every anonymous submission, without a name but with its shift, location and when it was sent — so on a small shift, they can tell who sent it. The form says so beside the **Submit anonymously** switch. If you turn the toggle off, every submission is attributed to the employee. ## What is "Talk it through"? An employee can answer about a shift in a short conversation with an AI interviewer instead of the form — about two minutes, typed or held to talk. It is off by default: turn on **Offer "Talk it through"** in **Settings**, and **Talk it through instead** appears beside the form's Submit button on the web and on the phone. It is not offered at the time clock kiosk. Each conversation uses AI credits, and none is offered while your organization's AI credits are used up. The interviewer asks how the shift was (it must be answered while **Require Rating** is on), what made it that way, and — while **Allow Anonymous Feedback** is on — whether to share it without their name, which must always be answered. At the end the employee sees what will be recorded, can change it, and sends it. What they send becomes their feedback on that shift exactly as if they had filled in the form, with the same notifications your notify settings send. Only the employee can see the conversation itself: they can read it back from their own feedback until its transcript is deleted, a week after they send it. ## Can an employee edit or delete feedback after submitting? Through the API, an employee can update or delete their submission within 24 hours of submitting. After 24 hours, the submission is locked. There is no edit or delete from the web or mobile interface — only one submission per shift is allowed, and attempting to submit again shows a message that feedback has already been provided. ## What notifications do managers get about feedback? Two types, both on by default: 1. **New feedback** — a notification whenever someone submits feedback (unless the low-rating alert replaces it), controlled by **Notify Managers of New Feedback**. 2. **Low-rating alert** — an alert as soon as a rating at or below the threshold comes in (for an anonymous one, once the hold described below ends), controlled by **Alert on Low Ratings**. The threshold defaults to **2 stars or below** and can be set to 1, 2, or 3 under **Low Rating Alert Threshold**. Notifications go to the shift's assigned managers — or, for a shift with no managers, the admins of its location — and, for named feedback, the employee's direct manager. Anonymous submissions show "An anonymous team member" as the submitter, and their notices — low-rating alerts included — go out on a quarter hour of the clock, at least 15 minutes after the shift's last check-out (or, if someone stays clocked in, within 12 hours of the shift's end or of the rating, whichever comes first) — or, for a rating sent after that, on the hour at least an hour later — rather than the minute they were sent, so their timing can't be matched to one person's clock-out. If none of those managers can open a low rating (for example, a shift lead without a manager role), the app's admins get the low-rating alert in the app instead — or, if the app has no admins of its own, the business's admins. They get no mobile push, and a routine new-feedback notice is never sent to them this way. When **Who Can Read Feedback** is set to administrators only, managers who can't open a submission are not notified about it at all; a low rating then goes to the admins. ## How do feedback reminders work? When **Send Feedback Reminders** is on (the default), employees who completed a shift but haven't submitted feedback get a reminder. **Send the Reminder After** controls how long the job waits before sending it: 24, 48, or 72 hours after check-out (default 48). It is not a repeat interval — each shift is reminded at most once, ever. A longer delay lowers reminder volume, because more employees submit on their own first and are never reminded at all. The job looks back only as far as the **Feedback Window**, so a shift that has dropped out of the window is never reminded. If the delay you pick is not shorter than the window, the job clamps it to just inside the window and logs that it did, rather than sending nothing. ## What can the Shift Feedback AI agent do? Through Ask AI, the agent has six tools. Five read: list feedback (filtered by period, rating range, or tag), show details for a specific submission, return aggregated statistics for one period (count, average rating, the 1–5 distribution, top tags — a snapshot, not a trend line), pull up the asking user's own feedback history, and list the shifts still open for them to rate. The sixth submits the asker's own feedback for one of those shifts, and only after they confirm it — there is no way to submit on someone else's behalf, or to edit or delete a submission through the agent. Browsing other employees' feedback is restricted to managers, admins and Shift Feedback app admins — regular users can only see their own. You can disable the agent entirely under **Settings > Shift Feedback Agent** with the **Enable AI Agent** toggle. ## Does shift feedback feed into Mango Signal? Yes. Every submission automatically sends a sentiment signal to Mango Signal. The 1–5 rating is mapped onto Mango Signal's −1 to 1 sentiment scale, with 3 stars as neutral. Anonymous submissions feed in without identifying the submitter, and with their day only, not the time they were sent. --- ## When something looks wrong ## "I wasn't prompted for feedback after my shift" Three common causes: 1. **Ad-hoc or early-checkout shift** — both are excluded by default. Check **Settings > Shift Type Exclusions**. 2. **Already submitted** — only one submission per shift is allowed. If the employee already submitted, the prompt does not appear again. 3. **Feedback collection disabled** — an admin may have turned off **Enable Feedback Collection** in Settings. ## "I can't find the feedback form for a shift I worked last week" The shift may have fallen outside the eligibility window or the eligible-shift cap. By default, only the three most recent completed shifts are eligible, and the window closes one week after checkout. Check the **Maximum Feedback Eligible Shifts** (1, 2, 3, 5, or 10) and **Feedback Window** (24 hours to 2 weeks) settings. If the shift is older than the window or more recent shifts pushed it off the list, the form is no longer available. ## "My feedback shows my name even though I chose anonymous" The admin has turned off **Allow Anonymous Feedback** since the employee last submitted. When the toggle is off, the anonymous checkbox is hidden and all submissions are attributed. Previously submitted anonymous feedback remains anonymous — the toggle only affects new submissions. --- ## Licensing and limits ## Does Shift Feedback require a license? Yes. Shift Feedback requires a license and is disabled by default. An administrator enables it from Admin → Apps → All Apps. ## What are the limits I should know about? | Limit | Value | |---|---| | Rating scale | 1–5 stars | | Submissions per shift | 1 per employee | | Eligible shifts | 1, 2, **3** (default), 5, or 10 most recent | | Feedback window | 24 hours, 48 hours, 72 hours, **1 week** (default), or 2 weeks after checkout | | Custom tag length | 50 characters | | Comment length (kiosk) | 2,000 characters | | Low-rating alert threshold | 1, **2** (default), or 3 stars | | Send the reminder after | 24, **48** (default), or 72 hours after check-out — one reminder per shift, never repeated | | Reminder lookback | The Feedback Window (24 hours to 2 weeks) | | Edit/delete window (API) | 24 hours after submission | | Trend analysis period | 8 weeks | | API pagination | 20 per page (max 100) | --- ## More help - [Shift Feedback Overview](/help/articles/shift_feedback_app_overview) - Ask AI — the assistant answers Shift Feedback questions from these articles. **Keywords:** faq, shift feedback, post-shift rating, feedback tags, anonymous feedback, low rating alert, feedback window, trend analysis, feedback reminders, shift sentiment, talk it through, ai interviewer, shift-feedback, shift_feedback --- # Shift Marketplace App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-14 How to set up and run the Shift Marketplace — listing, claiming, trading, and offering shifts between employees with configurable approval workflows. # Shift Marketplace ## 1. What it is Shift Marketplace lets employees list shifts they can no longer work, pick up open shifts, trade shifts with coworkers, and send direct shift offers to specific people. Managers get an approval queue and a Coverage Autopilot view that flags at-risk shifts and can send offers automatically. - **Enablement:** requires a license. An admin enables it per tenant from Admin → Apps → All Apps; it is off by default. - **What it is not:** Shift Marketplace does not create or publish schedules. Schedules are built in the Shifts & Scheduling app; the marketplace surfaces only shifts from published schedules that are either marked as open by management or listed by an employee. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Shift Marketplace**, and enable it. 2. Publish at least one schedule in **Shifts & Scheduling**. The marketplace shows only shifts from published schedules. 3. Go to **Shift Marketplace → Admin → Settings** and choose an approval workflow (see §5). The default is **Require Manager Approval for All Claims**, which means every claim waits under **Shift Claims** until an approver decides it. Choose **Auto-Approve All Claims** to assign claims immediately, or **Smart Approval** to approve low-risk claims automatically. 4. If your business uses scheduling teams, set the **Swap Scope** on each team. This controls who can pick up shifts listed by team members. The default is **Same Group** — only members of the same team see and can claim the listing. 5. To allow cross-location pickup, go to **Shifts › Settings › Location Staffing Defaults** and unlock the locations where employees from other stores should be able to claim shifts. 6. Grant access to users. Any authenticated user whose business has the app enabled can open the marketplace. The Coverage Autopilot tab and the Admin menu (Shift Claims, Audit Log, Settings) are restricted by role — see §3. **Silent-until-paired:** if no schedules are published, the marketplace is empty — only shifts from published schedules appear. If the approval workflow is set to **Require Manager Approval** but no manager has shift-management permissions, claims sit pending with nobody to approve them. And if cross-location pickup is needed, unlock the relevant locations in Shift Requirements *before* employees try to claim — the default is locked, and an employee at another store simply will not see the listing. ## 3. How it fits together **Listings and open shifts.** Two kinds of availability appear side by side on the marketplace: - **Open shifts** are created by management in Shifts & Scheduling. They have no current assignee and need someone to fill them. - **Listings** are posted by employees from their own assigned shifts. An employee who cannot work a shift lists it so someone else can pick it up or propose a trade. Example: a barista at the Downtown location is assigned the Saturday 7 AM–3 PM shift but needs the day off. They open the marketplace, choose that shift, and list it as **Pickup or Trade**. A coworker at the same location sees it, claims it, and — depending on the approval workflow — is either assigned immediately or placed in the approval queue. **Listing types.** When an employee lists a shift they choose one of three types: - **Pickup Only** — anyone eligible can claim it outright. - **Trade Only** — applicants must offer one of their own shifts in return. The lister reviews and accepts or rejects. - **Pickup or Trade** — both paths are open. **Eligibility.** Not every employee sees every listing. The marketplace filters on several dimensions: - **Swap scope** — set per scheduling team. **Same Group** (the default) means only team members can pick up the listing. **Same Location** broadens it to anyone assigned to the shift's location. **Any** removes the group and location gate entirely. - **Location lock** — a per-location setting in Shift Requirements. When unlocked, cross-store pickup is allowed and overrides the team's swap scope. - **Job function** — a listing that requires a specific job function (e.g. "Staff") is visible only to employees whose job function matches, or — when skill-based role matching is enabled for the business — to employees who hold the required skills. - **Shift conflicts** — employees who already have an overlapping shift cannot claim the listing. Admins and managers see all listings regardless of eligibility, for oversight. **Approval workflows.** When a claim is not auto-approved, it creates a pending claim request. The configured approval authority determines which managers see it under **Admin → Shift Claims**. Smart Approval auto-approves when any of these conditions is true: the shift is 48+ hours away, the employee has been with you 3+ months and either holds a Manager or higher role or has a **Top Tier** or **Reliable** MangoScore (or a reliability score of 75% or higher), the employee is already working that day at the same location or in the same team, or the shift covers a critical role and starts within 24 hours. All other claims go to a manager. **Direct Offers.** An employee can offer a specific shift to a specific coworker without listing it publicly. The recipient accepts or declines; the sender can cancel a pending offer. Offers can carry an optional expiration date; after that date the offer expires automatically. Direct offers do not go through the claim approval workflow — accepting transfers the assignment immediately. **Coverage Autopilot.** A manager-only view that shows shifts starting within the next 7 days that still need coverage. From this view a manager can send offers to eligible employees or escalate an unfilled shift to the location manager. Admins can also trigger a detection cycle that queues an automated sweep. **Gamification tie-in.** When Levels & Badges is enabled, picking up an open shift and completing a shift trade each award XP automatically. **Audit trail.** Every marketplace action — listing, claiming, application, trade transfer, admin action — is recorded in the audit log with the actor, timestamp, and details. The log is exportable to CSV. **Roles and visibility:** | Surface | Who can see it | |---|---| | Dashboard, Listings, Applications, Direct Offers | All users with the app enabled | | Coverage Autopilot | Manager or above | | Shift Claims | Admin or above, or app admin with shift-management permission | | Audit Log, Settings | Admin or above, or Shift Marketplace app admin | ## 4. Running it ### Reviewing shift claims 1. Go to **Admin → Shift Claims** (linked from the marketplace's Admin tab). 2. Each pending claim shows the shift, the requesting employee, and when the request was submitted. Approve or reject with an optional reason. 3. Approving a claim assigns the shift to the employee immediately and notifies them. Rejecting sends a notification with the reason you entered. 4. Which claims a manager sees depends on the **Approval Authority** setting. Under **Any Manager with Shift Permissions** (the default), every qualifying manager sees all pending claims. Under **Employee's Direct Manager Only**, each manager sees only claims from their direct reports. ### Reviewing trade applications 1. When someone applies to trade for your listed shift, you see it in the listing's detail page under **Applications**. 2. Review the offered shift (date, time, location). Accept to swap both assignments in one step, or reject with a reason. 3. Accepting a trade rejects all other pending applications on that listing automatically. ### Using Coverage Autopilot 1. Go to **Shift Marketplace → Coverage Autopilot**. 2. The view lists at-risk shifts — those flagged as needing coverage and starting within 7 days. 3. For any shift, click **Send Offers** to notify eligible employees, or **Escalate** to alert the location's manager. 4. Admins can click **Run Detection Now** to queue a detection cycle that scans for new coverage gaps. ### Sending a Direct Offer 1. Go to **Shift Marketplace → Direct Offers → New Offer**. 2. Choose one of your upcoming shifts, then select the coworker you want to offer it to. Eligible employees are highlighted at the top of the list. 3. Optionally set an expiration date and add a note. 4. The recipient is notified and can accept or decline from their **Direct Offers** tab. ### Exporting the Audit Log 1. Go to **Shift Marketplace → Admin → Audit Log**. 2. Filter by action type, user, or date range. 3. Click **Export CSV** to download the filtered log. Exports are capped at 10,000 rows, newest first. ## 5. Settings All settings are at **Shift Marketplace → Admin → Settings**. | Setting | Default | What it changes | |---|---|---| | **Enable Marketplace** | On | Turns the marketplace on or off for the business. When off, marketplace matching and API access are disabled. | | **Enable AI Agent** | On | Lets users ask the AI assistant questions about marketplace data. | | **Shift Claim Approval Process** | **Require Manager Approval for All Claims** | How claims are handled: **Auto-Approve All Claims** (instant assignment), **Smart Approval** (auto-approves trusted employees and advance bookings, sends the rest to a manager), or **Require Manager Approval** (every claim waits for a manager). | | **Allow trades between overlapping shifts** | Off | Lets two coworkers whose shifts overlap or fall on the same day swap them. The shift each person gives up is not counted as a conflict, against the daily-hours limit or against rest time; location, team, role and any other overlapping shift still apply. | | **Shift Claim Approval Authority** | **Any Manager with Shift Permissions** | Who can approve pending claims: any shift manager, the employee's direct manager, the shift's location manager, the scheduling team manager, or any relevant manager. | | **New Marketplace Listings** | On | Notify eligible employees when a new shift is listed. | | **Shift Claims** | On | Notify the lister when their shift is claimed. | | **Claim Approvals** | On | Notify the employee when their claim is approved. | | **Claim Rejections** | On | Notify the employee when their claim is rejected. | | **Email Notifications** | On | Send notifications via email. | | **In-App Notifications** | On | Show notifications inside the application. | | **SMS Notifications** | Off | Send urgent notifications via SMS. | Per-event email and SMS toggles are also available for four events: **New Listing**, **Listing Claimed**, **Application Received**, and **Application Status**. All default to On; they layer on top of the channel switches above. Cross-location pickup is not configured here. It is set per location at **Shifts › Settings › Location Staffing Defaults**. ## 6. More help - **Shift Marketplace FAQ** — specific setup and operating questions. - Ask AI — the assistant answers questions about Shift Marketplace from these articles. **Keywords:** shift marketplace, pick up shift, claim shift, trade shift, shift swap, open shift, shift listing, shift offer, coverage autopilot, shift claim approval, shift-marketplace, shift_marketplace --- # Shift Marketplace FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-14 Answers to common setup and operating questions about Shift Marketplace — for the admin running it. # Shift Marketplace FAQ Answers to common setup and operating questions about Shift Marketplace. For what the app is and how to set it up from scratch, see the [Shift Marketplace Overview](/help/articles/shift_marketplace_app_overview). --- ## Setup ## Do I need to configure anything before employees can use the marketplace? Yes. Three things must be in place before the marketplace works: 1. **Enable the app** — Shift Marketplace requires a licence and is disabled by default. Enable it from Admin → Apps → All Apps. 2. **Publish a schedule** — employees can only list or claim shifts that belong to a published schedule. Unpublished shifts do not appear. 3. **Choose an approval mode** — the default is **Require Manager Approval for All Claims**, which means every claim waits for an approver under **Shift Claims**. To assign claims without review, switch to **Auto-Approve All Claims**; to approve low-risk claims automatically, switch to **Smart Approval** — both in Settings → Workflow Settings. ## Who can access the marketplace once it is enabled? Every employee in the business can browse listings and claim or apply for shifts they are eligible for. Managers and admins see all listings for oversight. The **Coverage Autopilot** tab is visible only to managers and above. The **Admin** tab (Shift Claims, Audit Log, Settings) requires admin or app-admin access. --- ## Permissions and access ## Who can change Shift Marketplace settings? Only users with **Admin** or higher role, or users granted **App Admin** for Shift Marketplace. The settings page covers notification toggles, the approval workflow, the approval authority, and the general Enable Marketplace / Enable AI Agent switches. ## What controls whether an employee can claim a particular shift? The marketplace checks five things in order: 1. **Ownership** — you cannot claim your own listing. 2. **Listing type** — a **Trade only** listing cannot be claimed directly; you must apply with a shift of your own. 3. **Group or location membership** — the scheduling team's swap scope determines whether you must be in the same team, the same location, or either. If the admin has unlocked the shift's location (Shifts › Settings › Location Staffing Defaults → Location-Locked off), any eligible employee can claim regardless of scope. 4. **Role / job function** — your job function must match one the shift requires, or be one your admin set to cover it (for example, an Assistant Store Manager covering a Store Manager shift, set in Shifts > Settings > Role-Based Eligibility). If your business has skill-based role matching enabled, matching skills also qualify you. 5. **Schedule conflicts** — you cannot claim a shift that overlaps with one you are already assigned. For trades, an admin can turn on **Allow trades between overlapping shifts** (see below). Additional checks apply to manager-posted open shifts: contracted day-off rules, location-mode restrictions, and tier requirements are enforced before the claim. --- ## Day-to-day ## What is the difference between Pickup Only, Trade Only, and Pickup or Trade? These are the three listing types an employee chooses when posting a shift: - **Pickup Only** — any eligible coworker can claim the shift in one click. - **Trade Only** — a coworker must apply by offering one of their own future shifts. No direct pickup is possible. - **Pickup or Trade** — the listing accepts either a direct pickup or a trade application. The default for a new listing is **Pickup Only**. ## How does a shift trade work? An employee posts a listing as **Trade only** or **Both**. A coworker applies by selecting one of their own upcoming shifts to offer. The listing owner reviews the application and accepts or rejects it. On acceptance, both shift assignments swap in a single transfer and all other pending applicants are automatically rejected. ## Can I trade for a shift that overlaps one of mine? Only if your admin has turned on **Allow trades between overlapping shifts** (Shift Marketplace → Settings → Workflow Settings). It is off by default. When it is on, you can see and apply for a **Trade only** or **Both** listing that overlaps a shift you already work — for example, swapping your 1–9 pm shift for a coworker's 9 am–5 pm shift on the same day. You must offer the shift that overlaps; the apply form selects it for you. The shift each person gives up is not counted as a conflict, against the daily-hours limit or against rest time. Every other rule still applies: location, team, role, and overlap with any other shift you work. ## How do direct shift offers work? An employee sends a private offer of their assigned shift to a specific coworker. The offer includes an optional note and expires after **7 days** by default. The recipient can accept, decline, or let it expire. The sender can cancel the offer at any time while it is still pending. ## What happens when someone claims a shift? The marketplace runs conflict and eligibility checks, then transfers the assignment from the original holder to the claimer. The original holder's assignment is removed and a new assignment is created. The lister, the claimer, and (depending on notification settings) eligible coworkers are notified. The claim is logged in the audit trail. If manager approval is required, the claim is held as a pending request under Shift Claims instead. ## Can two employees list the same shift? Yes. Multi-slot shifts allow each assigned employee to list their own slot independently. The same employee cannot create a duplicate open listing for the same shift, but different employees can. --- ## Approval workflows ## What are the three approval modes and how do I choose? Open **Settings → Workflow Settings → How should shift claims be handled?** and choose one: | Mode | UI label | Behaviour | |---|---|---| | Auto-approve | **Auto-Approve All Claims** | Every eligible claim is approved instantly. No manager review. | | Smart approval | **Smart Approval (Recommended)** | Low-risk claims are approved automatically; the rest go to a manager. | | Manager approval | **Require Manager Approval for All Claims** | Every claim waits for a manager to approve or reject it. | ## What does smart approval auto-approve? A claim is auto-approved under smart approval when any of these conditions is true: - The shift starts **48 or more hours** from now. - The employee is **trusted**: they have at least 3 months tenure AND their MangoScore tier is **Top Tier** or **Reliable** (or their reliability score is 75% or above), OR they hold a Manager or higher role. - The employee is already working that day at the **same location or scheduling team** as the shift. - The shift covers an **urgent critical role** — it needs coverage, starts within 24 hours, and has an unfilled critical role (Supervisor, Manager, Security, or Medical). Everything else is routed to a manager for review. ## Who can approve a shift claim? The **Approval Authority** setting in Settings controls this. Five options are available: | UI label | Who approves | |---|---| | **Any Manager with Shift Permissions** (default) | Any manager with the "manage shifts" permission | | **Employee's Direct Manager Only** | The claiming employee's direct manager from the org chart (checked up to 3 levels) | | **Shift Location Manager Only** | A manager assigned to the shift's location or its parent locations | | **Scheduling Team Manager Only** | A manager of the shift's scheduling team | | **Employee's Manager, Location Manager, or Team Manager** | Any of the above three | Admins and super-admins can always approve regardless of this setting. --- ## Coverage Autopilot ## What is Coverage Autopilot and who can use it? Coverage Autopilot is a manager tool that surfaces shifts at risk of going uncovered in the next **7 days**. From the board, managers can: - **Send coverage offers** to up to 10 of the best-matched eligible employees in one click. - **Escalate** an uncovered shift to the location manager. - **Run a detection cycle** on demand (admin or app-admin only) to refresh the at-risk list. Autopilot never rosters anyone on its own: an offer waits for the employee to respond, and auto-fill waits for an approver. --- ## When something looks wrong ## Why can't I see any shifts in the marketplace? Three common causes: 1. **No published schedule** — listings and open shifts only appear when their parent schedule is published. 2. **Eligibility filtering** — employees see only shifts they qualify for (team membership, location, role, no conflicts). Ask a manager or admin to check the same page; they see all listings. 3. **Marketplace disabled** — verify that **Enable Marketplace** is switched on in Settings → General. ## I claimed a shift but it still says "pending" — what happened? Your business is using **Smart Approval** or **Require Manager Approval** mode. Your claim did not meet the auto-approve criteria, so it was sent to a manager for review. You will be notified when the claim is approved or rejected. Changed your mind? Open the shift and choose **Withdraw my request**. If the shift goes to someone else first, or its listing is closed or cancelled, your request is declined automatically and you are told why. ## My trade application was rejected, but I didn't do anything wrong — why? When the listing owner accepts a different applicant, all other pending applications are automatically rejected. This is not a judgment on your application — the shift was filled by someone else. The same happens when someone picks the shift up instead, or the listing is closed or cancelled; the notice says which. ## A shift listing shows "Not Eligible" — what does that mean? The marketplace found at least one reason you cannot claim or apply for that listing. Common reasons include: - You are not a member of the shift's scheduling team or location. - Your job function does not match what the shift requires. - You have a conflicting shift at the same time (for a trade, one that you are not offering in exchange). - The listing is trade-only and you have no eligible shifts to offer. Hover over the indicator for the specific reason. ## Why are fully covered shifts showing as "at risk" on Coverage Autopilot? The coverage flag can become stale after bulk imports or setup-wizard runs. Loading the Coverage Autopilot page automatically heals stale flags for shifts in the 7-day window (up to 200 shifts per page load). If the at-risk list still looks wrong, click **Run Detection Now** to trigger a full detection cycle. --- ## Notifications ## Which notification channels does the marketplace support? Three channels, each independently toggled in Settings → Notification Settings: - **In-app notifications** (on by default) - **Email** (on by default) - **SMS** (off by default) Below the channel switches, the **Per-event Email & SMS** card lets you enable or disable email and SMS individually for each event: **New Listing**, **Listing Claimed**, **Application Received**, **Application Status**, **Open Shift Filled**, **Open Shift Posted**, **Open Shift Claimed**, **Shift Matched To You**, **Claim Approved** and **Claim Rejected**. A box ticked there sends nothing while its notification type or delivery channel above is off. --- ## Licensing and limits ## Does Shift Marketplace require a licence? Yes. Shift Marketplace requires a licence and is disabled by default. An admin enables it for your business from Admin → Apps → All Apps. ## What are the listing and offer statuses? | Record | Possible statuses | |---|---| | Listing | Open, Filled, Closed, Cancelled | | Application | Pending, Accepted, Rejected, Withdrawn | | Direct Offer | Pending, Accepted, Declined, Expired, Cancelled | A listing can be closed by its owner at any time before it is claimed; it is cancelled automatically if the owner stops holding the shift. Once claimed (status changes to Filled), it is locked as a completed transfer. --- ## More help - [Shift Marketplace Overview](/help/articles/shift_marketplace_app_overview) - Ask AI — the assistant answers Shift Marketplace questions from these articles. **Keywords:** faq, shift marketplace, shift claim, shift trade, shift swap, shift offer, approval workflow, coverage autopilot, listing, eligibility, cross-location, MangoScore, not showing, permissions, shift-marketplace, shift_marketplace --- # Shifts & Scheduling App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-18 How to set up and run Shifts & Scheduling — creating schedules, assigning shifts, managing teams, and configuring compliance rules. # Shifts & Scheduling ## 1. What it is Shifts & Scheduling is where you build, publish, and manage your workforce schedules. You create schedules for a date range, add shifts with times and locations, assign employees, and publish — employees see their upcoming shifts and can submit availability and time-off requests. - **Enablement:** Requires a license. An admin enables it from **Admin → Apps → All Apps**. It is not turned on automatically. - **What it is not:** Shifts & Scheduling handles the *plan* — who works where and when. Time tracking (clock-in/out, punch records) lives in **Time & Attendance**; leave accruals and balances live in **Leave Management**; open-shift bidding lives in **Shift Marketplace**. Those are separate apps that integrate with this one. ## 2. Standing it up 1. **Enable the app** — go to **Admin → Apps → All Apps**, find **Shifts & Scheduling**, and enable it. 2. **Set up locations** — go to **Admin → Locations**. Every shift belongs to a location (or is marked non-location-specific). At least one location must exist before you can create shifts. 3. **Create scheduling teams** — go to **Shifts & Scheduling › Settings › Scheduling Teams** (or have teams created for you: the **Scheduling Teams** card on **Settings › Schedule Settings** can make one team for each location, each department, or each department at each location). A scheduling team defines which employees appear in the scheduler for a given location, department, or custom group. 4. **Mark employees as schedulable** — new employees are schedulable by default. To exclude someone, clear the **Schedulable** flag on their profile. Only schedulable employees appear as candidates for shift assignment. 5. **Create your first schedule** — go to **Team → Shift Scheduler**, click **Create**, pick a team, set the date range, and add shifts. Publish when ready — employees are notified automatically. 6. **Confirm it worked** — after publishing, employees see their upcoming shifts on their dashboard and in the mobile app. The schedule appears under **Schedules** in Published status. **Silent dependency:** If you turn on **Require approval before a schedule is published** (see Settings below), every schedule must be approved before it is published. While it waits in **Pending Approval**, employees can already see their own shifts on it, but nobody is sent the "schedule published" notice until an approver approves it. **Permissions:** Admins have full access. Managers and custom roles can be granted Create, Edit, Delete, and Approve permissions for shifts and schedules through **Admin → Roles**. Employees without management permissions can view their own shifts, submit schedule requests, and claim open shifts — but cannot create or modify shifts. ## 3. How it fits together **Schedules and shifts** — A schedule is a named container for a date range (e.g. "Week of Aug 11"). It holds shifts — individual time blocks with a start time, end time, and location. Shifts are assigned to one or more employees. A schedule moves through three statuses: **Draft** → **Pending Approval** (if approval is required) → **Published**. Employees never see shifts on a draft. Once a schedule is submitted for approval or published, employees can see their shifts on it; the "schedule published" notice goes out only when it is published. **Scheduling teams** — A scheduling team controls who is eligible for shifts on a schedule. There are three types: - **Location** teams — automatically include employees assigned to that location. - **Department** teams — include employees in a specific organizational department, optionally scoped to certain locations. - **Custom** teams — you pick the members manually, or define criteria (department, location, skills, roles) that resolve membership dynamically. Each team can have a designated manager and co-managers. Teams also govern swap scope (whether shift swaps are limited to the same team, same location, or unrestricted) and contracted-hours tracking periods. **Coverage and requirements** — Each shift tracks whether its staffing requirements are met. You can set a minimum staff count per shift, define role-based requirements per location (e.g. "at least 1 Lead and 2 Crew"), and attach skill requirements. The scheduler shows coverage status in real time — green when met, flagged when short. When a shift needs coverage, it can be posted as an open shift for employees to claim. **Schedule requests** — Employees submit three kinds of request: **Day off**, **Extra shift** (to be given additional shifts), and **Schedule change**. Requests go to their manager for approval. Approved day-off requests automatically remove the employee from conflicting shifts. Requests can be one-time, half-day, partial-day, or recurring (weekly, bi-weekly, or every four weeks). **Schedule templates** — Reusable shift patterns that you apply to new schedules. A template defines shift names, times, days of the week, staffing, and optional breaks. Add, edit or clone a template's shifts in the side panel that opens from **Add Shift** or a shift's **⋮** menu. Each shift's staffing is either its own (a minimum number of people, plus job functions such as one Store Manager) or comes from a shift rule template, whose current numbers are used each time a schedule is built. A shift left without staffing needs its location's minimum from Location Staffing Defaults, or 1 person if the location sets none. You can load industry-specific templates or create your own. When applied, the template generates shifts for every week in the schedule period, and each shift follows its store's Location-Locked setting. **Assignment compliance** — When you assign an employee to a shift, the system checks a layered set of rules before allowing the assignment: - **Hard blocks** (prevent the assignment): daily and weekly hour limits, minimum rest-period violations, overlapping shifts, approved leave conflicts, missing critical skills, and role-based prohibited pairings. These are enforced automatically — the assignment is rejected with a specific reason. - **Warnings** (shown but do not block): approaching hour limits, tight rest periods, pending leave requests, contracted day-off conflicts, and contracted-hours budget overages in soft-enforcement mode. The scheduler sees the warning and can proceed. Admins can override hard blocks when necessary (e.g. emergency coverage). An admin override is recorded in the shift's change history. **Hour targets** — Each employee on a schedule gets an hour target derived in priority order: their contracted hours, the role-based default, or 40 hours per week. The scheduler shows how each employee is tracking against their target across the schedule period, so you can balance workload before publishing. **Cross-schedule visibility** — When you open a schedule, you can see read-only "ghost" shifts from other published schedules at the same locations. This prevents double-booking an employee across schedules that overlap in time. The setting **Show external shifts** (on by default) controls whether these ghost blocks appear. ## 4. Running it ### Creating and publishing a schedule 1. Go to **Team → Shift Scheduler** and click **Create**. 2. Select a scheduling team (or locations), set the period start and end dates, and give the schedule a name. 3. Add shifts — set the time, location, and required staff. Use the **Calendar** view for a day-by-day layout or the **Board** view for a person-by-day grid with drag-and-drop. 4. Assign employees to shifts — the system recommends candidates ranked by availability, skills, role fit, and fairness (fewest upcoming shifts first). Compliance violations (daily/weekly hour limits, rest-period rules, leave conflicts) block the assignment; warnings appear for softer issues. 5. When ready, click **Publish** (or **Submit for Approval** if approval is required). Employees receive a notification with their new schedule. ### Applying a template 1. Open a draft schedule and choose **Apply Template**. 2. Select the template and, for multi-location teams, map each shift row to a location. 3. The template generates shifts for each week in the schedule. You can then adjust individual shifts before publishing. ### Reviewing schedule requests 1. Go to **Schedule Requests**. Pending requests appear with the employee name, request type, dates, and priority. 2. Approve or deny each request. Approving a day-off request automatically unassigns the employee from any shifts that conflict with the requested dates. ### Sharing a schedule publicly 1. Open a published schedule and choose **Share**. 2. A token-based public link is generated. This needs **Allow public schedule share links** turned on in **Schedule Settings** (it is off by default). You can control whether the public view shows employee names, employee counts, or only shift times. The link can be set to expire on a specific date. ### Copying a schedule 1. Open an existing schedule and choose **Copy Schedule**. 2. Set the new date range. Shifts are duplicated with dates adjusted by the offset between the source and target periods. 3. Shift assignments are not copied unless you tick **Also copy staff assignments**. When you do, each person is checked against the new dates the same way a manual assignment is (approved leave, overlapping shifts, rest periods, hour limits); anyone who fails a check is left off, and the confirmation names them so you can fill those spots by hand. ### Importing and exporting shifts Go to **Admin → Shift Import/Export** to bulk-import shifts from CSV or export published schedules for payroll or reporting. Scheduled SFTP imports and exports can run automatically on a configured timetable. ### Reviewing the audit trail Every shift and schedule is versioned. Open a shift and view its change history to see who changed what and when, including the optional reason-for-change note. Schedule-level changes (publishing, approval, rejection) are also tracked. ## 5. Settings The app-wide switches are on **Shifts & Scheduling › Settings › Schedule Settings**. The page has these cards: | Card | Setting | Default | What it changes | |---|---|---|---| | **Schedule Publishing** | **Require approval before a schedule is published** | Off | When on, a schedule is submitted for approval and is published only when an approver approves it. Employees can see their shifts on it while it waits; the "schedule published" notice is sent on approval. | | **Schedule Publishing** | **Who is asked to approve** | Location-Based Hierarchy (Recommended) | **Location-Based Hierarchy** notifies managers with authority over the schedule's locations, then escalates up the organizational hierarchy; **All Eligible Managers** notifies every manager and administrator who can approve schedules. Shown only while approval is required. | | **Scheduling Authority** | **Who can manage shifts and schedules beyond their own?** | Managers and admins, company-wide | Narrowing it limits a manager to the locations they manage, the scheduling teams they run and the people who report to them. Only a company administrator can change it. | | **Shift Claim Approvals** | **How should shift claims be handled?** | Require Manager Approval for All Claims | Whether a claimed shift is approved at once (**Auto-Approve All Claims**), decided claim by claim (**Smart Approval**), or always waits for a manager. When the value comes from Shift Marketplace's settings, the page says so under the field. | | **Shift Claim Approvals** | **Who can approve shift claims?** | Any Manager with Shift Permissions | Who may approve a claim and see it in the approvals queue. When Shift Marketplace has its own value saved, that one is in force and the page says so. | | **Public Schedule Share Links** | **Allow public schedule share links** | Off | Lets people share read-only schedule links that open without signing in. Turning it off stops every existing link working; turning it back on restores them. | | **Scheduling Teams** | **One team for each location** / **One team for each department** / **One team for each department at each location** | Off | Creates a scheduling team automatically when a location or department is added. Existing locations, departments and teams are not touched — use **Quick Setup** on the Scheduling Teams page for those. | | **Past Shift Editing** | **Allow managers to edit past shifts** | Off | When on, managers and admins can edit or delete a published shift after it ends. Changes are captured in the shift's change history. Employees stay blocked regardless of this setting. | | **Default Scheduler View** | **Calendar view** / **Board view** | Calendar view | The view a schedule page opens in for people who have not chosen one themselves. A user's own choice overrides this default. | | **Notification Recipients** | **Send scheduling alerts to this group** | The managers on the shift, schedule or location, then this app's admins | A group told as well about a declined shift or a schedule still unpublished near its start (and about a coverage gap at a location with no active manager). | | **Notification Recipients** | **Who hears when a schedule is published** | Everyone on the team or location | Whether the published and updated notices go to the schedule's whole team (or everyone at its locations) plus anyone rostered on it, or **Only people rostered on that schedule**. | The same page also holds the **Suggestion rules** card for scheduling and, for business administrators, the sample-data card. **Role scheduling requirements** — at **Admin → Role Scheduling Requirements**, you can define per-role rules: expected weekly hours, maximum consecutive days, shifts-per-period targets, and rolling hour caps. These produce warnings or hard blocks when assignments would violate the rule. **Location staffing defaults** — at **Shifts & Scheduling › Settings › Location Staffing Defaults**, you set each location's minimum people for shifts that don't set their own staffing, and whether its shifts are open to other stores (Location-Locked). The lock decides who may claim or pick up a shift from another store; it does not change who a manager can assign directly. Shifts already built from a schedule template keep the values they were built with. **Break types** — at **Shifts & Scheduling → Settings → Break Types** (also under Time & Attendance), you set the kinds of breaks shifts can plan and employees take: name, length, paid or unpaid, required or optional. A Shifts admin can also create one, or add the standard set, straight from a shift's Breaks section without leaving the form. A break type that a schedule template uses can't be deleted. **Shift rule templates** — at **Shifts & Scheduling → Settings → Shift Rule Templates**, you create reusable staffing sets that a schedule template's shifts can use. They define minimum staff and role counts; a rule has no days or times of its own and applies only where a shift chooses it. Editing one changes schedules built after you save; schedules already built keep their numbers. **Notifications** — Employees are notified when a schedule is published or updated, and receive shift reminders before their shifts start. A **Schedule Summary** email listing the week's shifts is sent every Monday. In each person's notification preferences, **Schedule Management** and **Shift Reminders** start on in-app, email and push; **Open Shifts** starts on in-app and email; **Schedule Summary** is email only. Text messages (SMS) are opt-in: once an administrator turns SMS on, an employee with a verified mobile number can switch texts on for **Shift Reminders**, **Schedule Management** and **Open Shifts**. Notification preferences are per-user and per-channel. **Automated background operations** — Coverage status is refreshed daily, and each shift reminder is sent at the configured lead time before the shift starts (4 hours by default). Scheduling team membership is re-materialized every four hours so that employee changes (new hires, transfers, deactivations) are reflected automatically. ## 6. More help - **Shifts & Scheduling FAQ** — specific setup and operating questions. - Ask AI — the assistant answers questions about Shifts & Scheduling from these articles. **Keywords:** shifts, scheduling, roster, rota, shift planning, schedule publishing, shift assignment, open shifts, coverage, scheduling teams, schedule template, shift swap, shift rules, shift requirements --- # Shifts & Scheduling FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Shifts & Scheduling — for the admin running it, and the swap, give-away, pickup and call-out questions employees ask. # Shifts & Scheduling FAQ Answers to common setup and operating questions about Shifts & Scheduling. For what the app is and how to set it up from scratch, see the [Shifts & Scheduling Overview](/help/articles/shifts_scheduling_app_overview). --- ## Setup ## Do I need to set up locations before I can create schedules? Yes. Every shift belongs to a location. If no locations exist, you cannot create shifts. Go to **Admin → Locations** and add at least one location first. ## Are new employees schedulable automatically? Yes. The **Schedulable** flag defaults to **on** for every new employee. They appear as shift-assignment candidates immediately. To exclude someone, clear the **Schedulable** checkbox on their employee profile. ## What are the schedule period types? Period type is detected automatically from your start and end dates: - **Weekly** — a 7-day span starting on the business's configured week start day. - **Monthly** — starts on the first and ends on the last day of a single calendar month. - **Quarterly** — starts on the first day of a quarter-start month (January, April, July, or October) and ends on the last day of that quarter. - **Custom** — any date range that doesn't match the above patterns. A schedule's start date must be from the current week or later (based on the business's week start day). ## What happens if I turn on approval but nobody has approve permission? Admins and super admins are always included as fallback approvers. Even if no location manager has the **Approve** permission for schedules, your admins will receive the approval notification and can act on it. --- ## Permissions and access ## Who can create, edit, and publish schedules? Admins have full access. Managers and custom roles can be granted **Create**, **Edit**, **Delete**, and **Approve** permissions for shifts and schedules through **Admin → Roles**. Employees without management permissions can view their own shifts, submit schedule requests, and claim open shifts — but cannot create or modify schedules. ## Who gets routed an approval request? That depends on the **Who is asked to approve** setting at **Shifts & Scheduling › Settings › Schedule Settings**: - **Location-Based Hierarchy** (the default) — managers assigned to the schedule's locations who have the **Approve** permission, or (if none are found) the schedule creator's organizational superiors with **Approve** permission. - **All Eligible Managers** — every admin and super admin, plus any user who holds the **Approve** permission for schedules. In both strategies, admins and super admins are included as a fallback. The creator is never sent their own approval notification. --- ## Day-to-day ## What are the schedule statuses, and what can I do in each one? A schedule moves through three statuses: 1. **Draft** — you can add, edit, and remove shifts. Not visible to employees. 2. **Pending Approval** — waiting for an approver to approve or reject it. Employees can already see their own shifts on it, but the "schedule published" notice is not sent until it is approved. 3. **Published** — visible to employees. Employees are notified, and shifts sync to connected calendars. If an approver rejects a schedule, it returns to **Draft** with the rejection comments. ## What happens when I copy a schedule? Copying creates a new **Draft** schedule for the target date range. Shifts are duplicated with dates adjusted by the offset between the source and target periods. You can choose which weeks to include and whether to copy staff assignments. Break configurations and staffing requirements are also copied. If the schedule name already exists, a suffix is added automatically. ## What request types can employees submit? Employees can submit three types of schedule requests: - **Day off** — blocks them from shifts on the requested dates. Supports half-day (morning or afternoon), partial-day (a specific time window in 30-minute increments), and recurring patterns (weekly, every 2 weeks, or every 4 weeks). Recurring requests can repeat indefinitely until cancelled. - **Extra shift** — asks to be given additional shifts on the dates they pick; their manager arranges it. - **Schedule change** — asks to change their existing schedule; their manager arranges it. Every request has a priority (**High**, **Medium**, or **Low**; default is **Medium**) and follows the statuses **Pending → Approved / Denied / Cancelled**. When a day-off request is approved, the employee is automatically unassigned from any conflicting shifts. ## What weights does the Auto-Assign Wizard use to rank candidates? The wizard scores candidates across four factors, each with a configurable weight that must sum to 100: | Factor | Default weight | What it measures | |---|---|---| | **Availability** | 30 | Whether the employee's availability covers the shift | | **Preference** | 25 | How well the shift matches the employee's stated preferences | | **Fairness** | 25 | Employees with fewer upcoming shifts score higher | | **Role** | 20 | Whether the employee's role matches what the shift requires | You can adjust these weights per run. When a shift has specific role requirements, a separate role-priority ranking runs first to fill critical roles before general positions. ## How does the cross-schedule visibility ("ghost shifts") feature work? When you open a schedule, shifts from other published or pending-approval schedules at the same locations appear as read-only "ghost" blocks. This prevents double-booking employees across overlapping schedules. The **Show external shifts** setting (on by default) controls whether these blocks appear. Draft schedules are excluded so unpublished plans don't leak across schedules. --- ## For employees: swapping, giving away, picking up and calling out ## How do I swap a shift with a coworker? Post your shift in **Shift Marketplace** as **Trade only** (or ask the assistant: "swap my Thursday shift with a coworker" — it posts the trade for you after you confirm, and tells the coworker if you name one). A coworker applies by offering one of their own upcoming shifts. You review the applications and accept or reject them; when you accept one, both assignments swap in a single transfer and any other pending applicants are turned down. Until a trade is accepted, you are still on your shift. Trading for a shift that overlaps one of your own is possible only if your admin has turned on **Allow trades between overlapping shifts**. ## How do I give a shift away (drop it)? Post it in **Shift Marketplace** for pickup (or ask the assistant: "I need to drop my shift on Wednesday"). The listing is live at once — no manager approval is needed to post it. Posting it does **not** take you off the schedule: you stay assigned and responsible for working it until a coworker claims it and that claim is approved (instantly or by a manager, depending on your company's approval mode). ## How do I pick up an open shift? Open shifts posted by management, and shifts coworkers have posted for pickup, appear in **Shift Marketplace** — the **Find Shifts** tab in Shifts & Scheduling. You can claim one you are eligible for — your location, team and role must match (an admin can open a location's shifts to other stores by turning off its Location-Locked setting in **Settings › Location Staffing Defaults**), and it must not overlap a shift you already work. Depending on the approval mode, the shift is yours at once or your claim waits for a manager; pending claims show under **My Pending Claims**. If you see open shifts you can't claim, ask your manager about the location, team or role they require. If your company doesn't use Shift Marketplace, there is no **Find Shifts** tab or list of open shifts to browse; ask your manager about extra work, or, if your company uses schedule requests, submit an **Extra shift** request. ## I'm sick or running late — how do I tell my manager? Report an absence or a delay on the shift (or ask the assistant: "I'm sick and can't make my shift"). You can report on one of your own shifts on a published schedule that starts within the next 48 hours and hasn't ended. Your manager is notified. The report does **not** take you off the schedule — your manager decides whether to release the shift. For a shift further ahead that you can't work, open it from **My Shifts** and choose **Can't make it** — your manager is told, so they can find cover. For time off, submit a **Day off** schedule request (or a leave request, if your company uses Leave Management). If you expected a shift and can't find it, tell your manager directly. --- ## When something looks wrong ## "My employees can't see their schedule" The most common causes: 1. **The schedule is still in Draft** — employees never see shifts on a draft. Check the status on the Schedules page. If **Require approval before a schedule is published** is on (**Shifts & Scheduling › Settings › Schedule Settings**), a draft must be submitted for approval; once it is in **Pending Approval**, employees can see their shifts on it, though the "schedule published" notice waits for the approver. 2. **The employee is not assigned to any shift** — a published schedule is visible, but employees only see shifts they are assigned to (plus open shifts they can claim). ## "The system won't let me assign this employee to a shift" The assignment checks a layered set of compliance rules. Hard blocks that prevent the assignment: - **Daily hour limit exceeded** — the employee would exceed the maximum daily hours (default **12 hours**). - **Weekly hour limit exceeded** — the employee would exceed the maximum weekly hours (default **40 hours**). - **Minimum rest period violated** — less than the minimum rest gap between shifts (default **8 hours**). - **Overlapping shifts** — the employee already has a shift at the same time. - **Approved leave conflict** — the employee has approved leave covering that date. - **Missing critical skill or certification** — the shift requires a skill the employee does not have, or their certification has expired. These defaults are configurable at **Admin → Compliance → Work Policy Settings**. Admins can override hard blocks for emergency coverage; the override is recorded in the shift's change history. ## "An employee claimed an open shift but it says Not Eligible" The marketplace eligibility check applies several gates beyond basic staffing: - The employee is not in the shift's scheduling team or location. - The employee already has a conflicting shift at that time. - The employee is missing a critical skill or their certification expired. - The shift falls on a contracted day off (when the business uses **Hard block** mode for contracted days off; the default is **Soft prompt**). - The employee is set to a fixed primary location and the shift is at a different location. - The shift has role requirements and the employee's role does not match any role that still needs filling. A role can also be filled by the job functions set to cover it in **Shifts > Settings > Role-Based Eligibility** (for example, Assistant Store Manager covering Store Manager). Covers work one way, and the shift's own job function always fills first. The "Not Eligible" tooltip on the marketplace listing shows the specific reasons. ## "I edited a shift but the employee's calendar didn't update" Calendar sync triggers when a shift's start time, end time, name, location, or status changes. If the edit only changed other fields (notes, staffing requirements), no sync fires. Bulk operations that publish or unpublish an entire schedule trigger a batch resync for all assigned employees. If the calendar still shows stale data, check that the employee's calendar integration is active and sync-enabled under their profile. --- ## Compliance and rules ## What are the default compliance limits, and where do I change them? | Rule | Default | Where to change | |---|---|---| | Maximum daily hours | **12 hours** | Admin → Compliance → Work Policy Settings → Work Hour Limits | | Maximum weekly hours | **40 hours** | Admin → Compliance → Work Policy Settings → Work Hour Limits | | Minimum rest period between shifts | **8 hours** | Admin → Compliance → Work Policy Settings → Work Hour Limits | | Daily hours warning threshold | **80%** of limit | Admin → Compliance → Work Policy Settings → Warning Thresholds | | Weekly hours warning threshold | **80%** of limit | Admin → Compliance → Work Policy Settings → Warning Thresholds | | Maximum consecutive shift overlap | **30 minutes** (allowed by default) | Admin → Compliance → Work Policy Settings → Consecutive Shift Overlap Settings | At 80% of the daily or weekly limit, the scheduler shows a warning but does not block the assignment. At 100% it becomes a hard block. ## What does "contracted hours enforcement" mean in auto-assign? When the Auto-Assign Wizard fills a schedule, it respects each employee's contracted hours target (derived in priority order: their contracted hours, the role-based default, or 40 hours per week). The enforcement mode, which you set per run, controls how strictly: - **Strict** (the default) — the employee will not be assigned beyond their contracted hours. - **Soft only** — the employee can be assigned beyond their hours, but their candidate score is reduced. - **Off** — contracted hours are ignored during assignment. --- ## Notifications and calendar ## When do employees get notified about their shifts? - **Schedule published** — every assigned employee is notified when a schedule is published for the first time. A re-publish after edits sends an "updated" notification. - **Shift reminders** — sent before each shift starts. The default is **4 hours** before; an administrator sets the lead time for the whole business (**Reminder time (hours before shift)** in the admin notification settings). Employees cannot set their own reminder window. - **Schedule Summary** — an email listing the week's shifts, sent every Monday. In each person's notification preferences, **Schedule Management** and **Shift Reminders** start on in-app, email and push; **Open Shifts** starts on in-app and email; **Schedule Summary** is email only. SMS (text messages) is an opt-in channel. Once an administrator turns SMS on (**Admin → General Settings → SMS Settings**), each employee who adds and verifies a mobile number and switches SMS on in **Account Settings → Notifications** can be texted for: - **Shift Reminders** — before each shift starts. - **Schedule Management** — only notices marked urgent, such as the notice a manager gets about a new **High**-priority schedule request. - **Open Shifts** — when a new open shift is posted, and when a manager marks one urgent. This also needs **SMS Notifications** switched on in **Shift Marketplace → Settings**, and each employee switches SMS on for Open Shifts in their own notification preferences (it is off until they do). ## Which calendars can shifts sync to? Google Calendar, Microsoft Outlook, and iCal/CalDAV. Sync is triggered in real time when a shift is created, updated, or cancelled — and as a batch when a schedule is published or unpublished. Calendar sync must be enabled for the business and the employee must have an active calendar integration on their profile. --- ## Licensing and limits ## Does Shifts & Scheduling require a licence? Yes. An admin enables it from **Admin → Apps → All Apps**. It is not active for a business until they opt in. ## Are there limits on CSV imports? Yes. Shift and schedule CSV imports accept files up to **5 MB** and **2,000 rows**. Imports of 200 rows or fewer run immediately; larger files are processed in the background. Only `.csv` files are accepted — save a spreadsheet as CSV before importing it. --- ## More help - [Shifts & Scheduling Overview](/help/articles/shifts_scheduling_app_overview) - Ask AI — the assistant answers Shifts & Scheduling questions from these articles. **Keywords:** faq, shifts, scheduling, schedule approval, shift assignment, open shifts, coverage, rest period, hour limits, scheduling teams, shift reminder, calendar sync, schedule request, not showing, can't see schedule, shift swap, trade shift, drop shift, give away shift, pick up open shift, call out sick, running late, overtime, compliance, auto-assign, csv import --- # Sites App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run internal sites — pages built from sections that can pull live company data, support audience rules, and flag themselves when linked content changes. # Sites ## 1. What it is Sites lets your organisation build internal web pages — department homepages, onboarding guides, knowledge centres, executive portals — without leaving the platform. Each page is assembled from section types (page banners, questions and answers, team members, policy links, and dozens more). Several of those sections pull live data from other apps, so the page stays current. - **Enablement:** Sites requires a licence. An admin enables the app from **Admin → Apps → All Apps**, and it appears in the sidebar once enabled. - **What it is not:** Sites is not a public website builder. Pages are for signed-in people in your organisation, scoped by the audience rules you set. Public share links exist, but they are off until an admin turns on **Public share links**. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Sites**, and enable it. 2. Open **Sites → Admin → Settings** and review the defaults. Most features are on by default, including **Ask AI for readers** and **"In short" summaries**. Turn off anything you are not ready for. 3. Decide who may create sites. **Who can create a site?** (under **Permissions**) defaults to **Managers and above**. Admins and Sites app admins can always create sites, whatever it is set to. 4. Create the first site: click **New site**, give it a name, and pick a **Category**. Then add at least one page from the site's **Manage › Pages**. 5. Add members. The creator is automatically the owner. Add editors (create, edit and publish pages, and change the site's settings) or viewers (read the site while it's a draft or limited to an audience) from the site's **Manage › Members**. 6. Publish the site. Until you publish, only members can see it. After publishing, everyone in the organisation can read it — unless you narrow the site's **Audience** under **Manage › Members**, or restrict individual pages. Publishing the site does not publish its pages. Each page is published on its own, or in bulk from the page list. A site with no published pages shows nothing to people who are not members. ## 3. How it fits together **Sites and pages.** A site is the container. It has a name, a category, a navigation bar and members. Pages live inside a site, and each page is an ordered list of sections. A site holds up to 100 pages by default, and your organisation can have up to 50 sites. **The Pages panel.** In the page editor, **Pages** on the left lists every page of the site: its menu as a tree, then the pages that are not in the menu. Open a page by clicking it. Drag a page, or use its **⋮** menu, to move it up or down, put it under another menu item, or add it to or take it out of the menu. The menu's order is the site's page order. A new page stays out of the menu until you place it, except the first page of a site, which starts the menu. Labels, links and the menu's look are set in **Navigation**. Example: a "Facilities" site (category: Department) might contain three pages — "Welcome" (Page Banner + Quick Links + Team Members), "Office Policies" (Policy Links + Questions and Answers), and "Floor Map" (Text + Image Gallery). **Section types.** There are over 50 section types. Most are static: the author fills in the content (Text, Numbered Steps, Data Table, Image Gallery, Questions and Answers, Timeline, File Downloads). Others are live and read platform data each time the page is opened. **Policy Links** pulls published policies from Policy Hub. **Team Members** shows people from the org chart. **Form** shows a platform form. **My Upcoming Events** lists each reader's own upcoming calendar events. **Job Listings** pulls from Job Board. **Org Chart** draws a department hierarchy. **Wiki Page** shows one published Wikis page in place. **Categories.** A category (Team, Department, Location or site, Company-wide, Project or initiative, Knowledge base) groups sites on **All sites**. It does not affect who can read anything. Admins can rename, add or remove categories in **Sites → Admin → Settings → Categories**. **All sites.** Every site you can open, grouped, each as a tile with its icon, its description and how many pages it has, how many sites are inside it and when it was last updated. A site's icon takes the site's own color, or its category's color when it has none. **Member** and **Following** chips mark your sites. The search above the tiles matches every word you type in a site's name or description, so "store handbook" finds "Store Operations Handbook". **Page types and presentation.** Each page has a **Type** — Content, News, Wiki, Announcement or Landing — that classifies it in search and filtering. Its **Presentation** sets width and spacing: **Utility** (full width, compact), **Balanced** (standard width and spacing), **Editorial** (generous spacing), **Executive** (narrow, generous spacing) or **Campaign** (full-bleed hero). A page uses the site default unless its author picks one in Page settings. **Member roles.** Each site member has one of three roles: - **Owner** — everything an editor can, plus members, the site's audience, public sharing, and moving the site to Trash. A site must keep at least one owner. - **Editor** — create, edit and publish pages, manage page settings, and change the site's settings and navigation. - **Viewer** — can read the site while it's a draft or limited to an audience. Viewers see published pages only — not drafts — and cannot edit. Admins and Sites app admins can do everything an owner can, across all sites. **Audience rules.** By default a published site and its pages are visible to everyone. When **Audience restrictions** is on, an owner can narrow the whole site, and an editor can restrict a page to specific departments, locations, roles, job titles, job families, groups or people. A restricted page with no rules is visible to admins only. With **Per-segment sections** on, rules can also be set per section, so different readers see different parts of one page. Site members and admins always pass the site's audience. **Page approvals — available versus required.** These are two different switches, and admins often confuse them. - **Page approvals** makes approval *available*. An editor can send a page to a named approver, who approves it, asks for changes or rejects it. A page still waiting for approval cannot be published. A page never sent for approval can still be published. - **Require approval before publishing** makes approval *mandatory*. No page goes live — by hand, in bulk, on a schedule or through the AI assistant — until it is approved. Admins and Sites app admins can still publish without approval. Nobody approves a request they sent, admins included. Whoever asked — or the page's author — can **Withdraw request** while it is waiting. **Who can approve a page?** (under **Permissions**) sets who may act as an approver. It defaults to **Anyone with access to Sites**. The **Approvals** tab in the sidebar shows the pending queue, badged with how many pages are **waiting on you**: requests you can decide (for admins and Sites app admins every request someone else sent, otherwise the pages sent to you, under **Assigned to me**), your own requests an approver sent back to you, and your approved pages that are ready for you to publish. The **Waiting on you** filter on the Approvals page lists exactly those pages. Site owners and editors also see their sites' other pending pages under **All pending**, marked with who they are waiting for, but those are not counted. Your own requests that are still waiting for a decision are not counted either; they are under **Sent by me**. **Self-maintaining content.** Policy Links, Team Members, Contact Cards, Org Chart, Form, My Upcoming Events, News Feed and Wiki Page sections are bound to live platform data. While **Self-maintaining content** is on, a nightly scan compares each bound section with what it held at publish time. If a linked policy was unpublished, a person left, or a form was deleted, the page is flagged and an update is staged. The owner applies it to the page's draft and then publishes it, or dismisses it. Nothing changes on a published page until a person publishes it. **"In short" summaries.** While **"In short" summaries** is on, AI writes a one- or two-sentence summary and topic tags for each page when it is published. Readers see the summary above the page, marked "Written by AI". It appears only on the published page, and only while it describes the current published version. A page where any section has its own audience never shows one, because one summary cannot match what each reader sees. Authors control it per page from the **"In short"** card in Page settings (see §4). **Content expiry.** When **Content expiry** is on, a published page is archived automatically once its expiry date passes. The page's author is told seven days before; if the author has left, the site's owners are told instead. **Saved pages and follows.** People save pages for quick access from the **Saved & following** tab. When **Site follows and page watches** is on, people can follow a site to hear about newly published pages, or choose **Get page updates** on a page to hear when it is updated. **Translations.** When **Multi-language translations** is on, editors can have AI translate a page into other languages, and readers get a language switcher. A translation can be verified by a person, and is marked **Needs Update** when the source page changes. A translation carries its own "In short" summary, which an editor can type or correct in the translation editor. Readers of a translated page see that language's summary or none — never the original's. A summary a person typed is not marked "Written by AI". ## 4. Running it ### Choosing a starter Open **Site resources → Starter sites** to browse ready-made layouts. Each card identifies a **Single page** or a **Multi-page** site with its page count. Preview a site to try its navigation in desktop or phone view. **All pages** also includes pages outside its menu. ### Creating a page 1. Open a site and click **New page** on its home (or choose **Manage › Pages** and click **New page** there). 2. Optionally pick a page starter, then give the page a title and a **Type** (Content, News, Wiki, Announcement or Landing). Click **Create draft page**. 3. Add sections. The Sites AI agent can draft a page from a plain-language description, or you can add sections yourself from the section gallery. 4. Preview the page in the split-screen editor, then publish. ### Importing content From the page list's **⋮** menu (**Manage › Pages**, then **⋮**), choose **Import a document or web page**. Then pick what to build it from: upload a file (.md, .txt, .html, .pdf or .docx, up to 2 MB), give the address of a public web page (or of a PDF or Word document online), or paste text or markdown. The source is a guide to content and style, not a layout to copy. AI rebuilds it from the site's own sections in your company theme, keeps its facts exact, and brings its key images into the Asset Library. The result is saved as a draft for you to review. Leave the title blank to name the page from its content. Choose **A page per topic** for a long source such as a handbook: each topic becomes its own draft. On a site that has no menu yet, the first starts it and the rest go beneath it; otherwise they wait under **Not in the menu** in the editor's **Pages** panel until you place them. A page that needs a sign-in, or one on your company's own network, can't be read from its address. Paste its text instead, or use the Chrome extension from the open page. You can also ask the Sites AI to "make a page from" a link, a document in the Asset Library, or text you paste into the chat. A page imported from a web address remembers its source. **Refresh from source** in the page's **⋮** menu re-reads it. If something needs to change, it prepares an update: a banner on the page says an update is waiting, its review screen lists what changed, and you apply it to the page draft or dismiss it. While **Self-maintaining content** and **Import a document or web page (AI)** are both on, the sources of published pages are also checked weekly. An update is never applied on its own. A page captured with the Chrome extension is a snapshot of what your browser showed, so it is not refreshed. ### Controlling a page's "In short" summary Open the page, choose **Page settings** from its **⋮** menu, and find the **"In short"** card. It shows the summary readers currently see. - **Show "In short" on this page** hides or shows the summary on this page only. The summary is still written while it is hidden, because it also fills a missing link preview and search snippet. - **Write it again** asks AI for a fresh summary (the button reads **Write it now** when the page has none). The current summary stays until the new one arrives, usually in a minute or two. The button is disabled, with the reason shown, while the page is unpublished or "In short" is turned off for your organisation. Site owners, editors, admins and Sites app admins can use this card. To edit a translation's summary, open that translation and change its **In short** field. ### Approving pages Open **Approvals** from the sidebar. **All pending** and **Assigned to me** show pages waiting for a decision — choose **Approve**, **Request changes** or **Reject** on the row, or open the page to read it first. **Sent by me** lists the pages you sent that are still waiting, came back, or were approved and are not published yet, with the approver's note. Approving doesn't publish a page: an approved page stays there until someone publishes it — **Approved — ready to publish** with a **Publish** button when you can publish it, otherwise when it's scheduled to publish or who will publish it. Pages that came back also show on your Dashboard under **Sent back to you**, and approved pages you can publish under **Ready to publish**. ### Asking readers to confirm they've read a page When you publish, turn on **Ask readers to confirm they've read it** in the publish sheet, and optionally set a **Confirm by** date. The same switch is on the **Read confirmation** card in Page settings, and it applies when you next publish. Everyone the page is for is asked about the version you publish: readers see "Please confirm you've read this version." with an **I've read and understood this** button, and pages still waiting on them are under **Saved & following → To confirm**. Reminders arrive in the app as "Please confirm you've read: …". With a Confirm by date they start two days before it; without one, the morning after publishing. They repeat every three days and stop 21 days after the date (or after publishing when there is none). Editors open **Read confirmations** from the page's **⋮** menu to see who has **Confirmed** and who has **Not yet**. **Remind the rest** sends a reminder now to the people who haven't confirmed and can still open the page, skipping anyone reminded in the last 12 hours. While the switch is on, each publish asks readers about the version it publishes. ### Page owners and keeping pages current In Page settings, the owner card names a **Page owner** — one of the site's owners or editors — or an owning team, which must be a group whose members can all open the page. Readers see **Owned by …** at the foot of the published page, with the date it was last checked, or published if nobody has checked it since. A published page that goes longer than **Review pages every (days)** without being published again or checked is going stale. Its owner sees a notice on the page, and it is listed under **Pages that need care** on the Dashboard. **Mark as still accurate** in the page's **⋮** menu — or **Still accurate** on the notice — records the check without changing the page. The page's owner and anyone who can edit the page can mark it. ### Page purpose **Page settings → Page guidance → Purpose** says what the page is for: introduce a topic, find a service, follow a procedure, find an answer, read a story, or take part. It guides the Sites AI assistant's suggestions for the page and the update proposed when an imported page's source changes. **Infer from content** works the purpose out from the page's sections. Choosing a purpose does not rewrite the page. ### Download PDF, Print and QR posters On a published page, the **⋮** menu offers **Download PDF**, a PDF of the page as you read it — in your language, with the sections your audience shows you — and **Print**, which opens the reading layout in a new tab and your browser's print dialog. Editors also get **Print QR poster** on a published page of a published site: a printable sheet with a code that opens the page after sign-in, and keeps working if the page moves to another site. A published site's **Manage** menu has **Print QR poster** for the whole site. ### Duplicating a site **Manage → Duplicate site** makes a new draft site from an existing one, for editors who may also create sites. Choose the copy's name, category and audience, and optionally **Also copy members** (they keep their roles and aren't notified). Every page that isn't archived is copied with its status, sections, audiences, menu and links between its pages. Followers, bookmarks, comments, views, version history, translations and scheduled publish dates are not copied, and read confirmations start again when a copied page is next published. The copy runs in the background: it appears in **All sites** when it finishes, and **Background Tasks** in your account menu shows its progress. The item is disabled, with the reason, at the site limit or when the site has more pages than one site may hold. ### Bulk publishing or archiving From the page list, select pages with the checkboxes, then choose **Publish** or **Archive** from the bulk action bar. Pages that still need approval are skipped during a bulk publish (unless you are an admin or Sites app admin), and the confirmation message says how many. ### Viewing analytics and exporting Go to **Sites → Admin → Analytics**. It shows views over time, the most-read pages, pages nobody is reading, and **Content health** (pages going stale or flagged for review). The **AI reach** card shows how often Ask AI retrieved a Sites page, how many people that reached, and which pages were retrieved most. From the sites list, admins can choose **Export CSV** to download all sites, or the current filtered set. ## 5. Settings All settings are at **Sites → Admin → Settings**, grouped into cards. | Setting | Where | Default | What it changes | |---|---|---|---| | Enable Sites AI agent | AI agent card | On | The AI agent that drafts and manages pages from conversation | | Allow the AI assistant to make changes | AI agent card | On | When off, the assistant can still answer and search but cannot create, edit, publish, move or delete | | Analytics | Features | On | View tracking and the Analytics page | | Name individual viewers in analytics | Features | Off | Adds a Top viewers list naming who read each page | | Page comments | Features | On | Threaded comments on pages | | Multi-language translations | Features | On | AI page translations and the reader's language switcher | | Version history | Features | On | Version snapshots of each page | | Scheduled publishing | Features | On | Set a future publish time on a draft page | | Saved sections | Features | On | Save and reuse section designs across pages | | SEO & sitemap | Features | On | Link-preview tags and a per-site sitemap for signed-in users | | Public share links | Features | Off | Lets site owners create a link that opens a site's everyone-visible pages without a login | | Page approvals | Features | On | Makes approval available; does not make it mandatory | | Require approval before publishing | Features | Off | No page goes live until it is approved; admins and Sites app admins can still publish | | Audience restrictions | Features | On | Restrict sites and pages to specific people or groups | | Per-segment sections | Features | On | Show or hide individual sections by audience | | Ask AI for readers | Features | On | Readers ask a page or site a question, answered only from content they may see | | "In short" summaries | Features | On | AI writes a summary and tags on each publish; readers see it as "In short" above the page. Authors can hide it or write it again for each page from the "In short" card in Page settings | | Related pages | Features | On | A "Related pages" section at the foot of each page | | Site follows and page watches | Features | On | Following sites and watching pages | | Stock image search / AI image generation | AI & images | On | Image sources when editing sections | | Import a document or web page (AI) | AI & images | On | The import screen and the weekly source check | | Default page presentation | Site defaults | Balanced | Presentation for sites and pages that use the default | | Content governance | Content management | On | Flags pages due for review and shows Content health on Analytics | | Knowledge gap report | Content management | Off | Records, without names, searches and questions that found nothing | | Self-maintaining content | Content management | On for new organisations | Flags pages when linked data or an imported source changes, and stages a refresh. Organisations set up before 4 September 2026 start with it off until an admin turns it on | | Content expiry | Content management | Off | Archives published pages once their expiry date passes | | Default expiry period (days) | Content management | 365 | Expiry for a page published without its own date, while Content expiry is on | | Review pages every (days) | Content management | 180 | When an unrepublished page counts as going stale | | Max sites / Max pages per site | Limits | 50 / 100 | Caps on sites and on pages per site | | Max upload size (MB) | Limits | 25 | Largest file an editor can upload | | Who can create a site? | Permissions | Managers and above | Which people may create sites | | Who can approve a page? | Permissions | Anyone with access to Sites | Which people may act as approvers | | Page published, New comment and @mention, Page updated, Content expiry, Site member added, Approvals and refresh requests | Notifications | On | Each notification type Sites sends | ### Export and import between domains Company admins and Sites app admins can use **Sites → Admin → Settings → Export & Import** to copy one, selected, or all sites as a ZIP. Browse, search, filter and sort the export table to choose sites, or explicitly choose **All sites**. Selections are retained across pages and filters, and the form shows how many sites and pages will be included. The destination review shows the package totals and updates the selected totals as you choose sites, then creates new drafts with copied files and remapped page links. The completed import reports the sites and pages actually created. Existing destination content and app settings stay unchanged. Source-specific connections and restricted audiences are reviewed in **Finish setup**; saved templates and translations remain private until explicitly released. Public sites receive a new share link after publication. See the [Sites FAQ](/help/articles/sites_app_faq) for limits, privacy and recovery. ## 6. More help - **Sites FAQ** — specific setup and operating questions, limits and troubleshooting - Ask AI — the assistant answers questions about Sites from these articles. **Keywords:** sites, internal site, intranet page, company portal, department site, knowledge base, page builder, content review, page approvals, audience restriction, self-maintaining content, in short summary, page summary --- # Sites FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Sites — for the admins, site owners and readers who use it. # Sites FAQ Answers to common setup and operating questions about Sites. For what the app is and how to set it up from scratch, see the [Sites Overview](/help/articles/sites_app_overview). --- ## Setup ## Do I need to configure anything before people can start building sites? Yes: an admin has to turn Sites on first. Sites needs a licence and ships switched off, so an admin enables it from Admin → Apps → All Apps. Until then nobody sees it. After that, open Sites settings to review the limits, the **Features** switches and **Who can create a site?**. ## Who can create a site, and how do I change that? By default, **Managers and above** can create sites. Change this under **Who can create a site?** in Sites settings. The options are **Managers and above (default)**, **People managers (anyone with reports)**, **App admins only**, **Everyone with access to the app**, and **Specific people — choose groups below**. Admins and Sites app admins can always create sites, whatever this is set to. ## What can site owners, editors and viewers each do? Every site has three member roles: - **Owner** — everything an editor can do, plus manage members, set the site's audience, create public share links and move the site to Trash. - **Editor** — create, edit and publish pages, edit the site's details and navigation, and publish or archive the site. - **Viewer** — read the site. Whoever creates a site becomes its owner. A site must always keep at least one owner, so you can't remove the last one. --- ## Permissions and access ## Why can't I see a site my colleague can see? Most likely the site isn't shared with you. A published site is readable by everyone only when its audience is **Everyone**. A site set to **Only specific people** is open only to its audience rules and its members. A site that is still a draft, or has been archived, is open only to its members. Admins and Sites app admins see every site. To get in, ask a site owner to add you or widen the audience. ## Why can't I see a page on a site I can open? The page probably has its own audience. When a page's **Visible to everyone** switch is off, only people who match one of its audience rules can see it. Rules can name a department, location, job family, job title, organizational role, group, platform role or individual user. A restricted page with no rules at all is visible only to admins and Sites app admins. Unpublished and expired pages are also hidden from readers. ## Does a department audience include people whose department is only one of several? Yes. A department rule matches anyone who belongs to that department, whether it is their main department or one of the other departments on their profile. A location rule works the same way downwards: it admits everyone at that location or at any location beneath it. ## How do I show different sections of one page to different people? Leave **Per-segment sections** on in Sites settings (it is on by default). Then open the page's settings and use the **Per-section visibility** card to restrict a section to specific platform roles or departments. A section with no restriction shows to everyone who can see the page. Admins always see every section. --- ## Day-to-day ## What happens when I publish a page? Publishing makes the page live and saves a version you can restore later. If **Page published** notifications are on, the site's followers are told, except anyone the page's audience leaves out. Sites search and Ask AI pick the page up in the background, usually within a few minutes. Ask AI only ever answers a person from pages they are allowed to see. ## Do pages have to be approved before they go live? Only if you turn on **Require approval before publishing** in Sites settings. It is off by default. **Page approvals**, which is on by default, lets an author send a page to a named approver, but publishing without approval is still allowed. Either way, a page that is waiting for approval, or has been rejected, can't be published until it is approved. Admins and Sites app admins can always publish without approval — they can still ask someone to approve a page first if they want a second pair of eyes. ## Why can't I approve this page? You can approve a page only if it was sent to you for approval, and never a page you wrote yourself. Nobody can approve a request they sent — not even an admin — so the page shows **Waiting for approval from** the person you asked instead. Admins and Sites app admins can approve, reject or ask for changes on anyone else's request, even one sent to someone else. Admins can also limit who can be named as an approver under **Who can approve a page?** The default is anyone with access to Sites. ## I sent a page for approval — where do I see what happened, and can I take it back? Open **Approvals** in Sites and choose **Sent by me**. It lists the pages you sent that are still waiting, the ones that came back, and the ones that were approved but aren't published yet, with the approver's note. Approving doesn't publish a page — an approved page stays in the list until it's published: **Approved — ready to publish**, with a **Publish** button, when you can publish it; **Approved — scheduled for** a time when it will publish itself; or **Approved — waiting for** whoever can publish it. Pages that came back — changes requested or rejected — also show on your Dashboard under **Sent back to you**, and approved pages you can publish under **Ready to publish**, which opens just those pages. You get an email and a notification when the decision is made. While a page is still waiting you can choose **Withdraw request** there or on the page: it stays a draft, the approver is no longer asked, and you can request approval again later. If an admin publishes the page before it is approved, the request closes and you are told ("Published: "). ## How do I get told when a site posts something new? Open the site and select **Follow**. Followers hear when a page on that site is published, by email and in-app. To hear about edits to one particular page, open the page's three-dot menu (⋮) and choose **Get page updates** (on the phone it is a button on the page). You follow a site automatically when you are added as a member. Both need **Site follows and page watches** to be on in Sites settings. All the sites you follow are on **Saved & following**, and on **All sites** a followed site carries a **Following** chip. The sidebar's **Your sites** lists the sites you own or edit, and so does the Dashboard's **Your sites** table. ## Which notifications does Sites send, and can I turn them off? Each notification has its own switch under **Notifications** in Sites settings, and all six are on by default: 1. **Page published** — email and in-app, to the site's followers. 2. **New comment and @mention** — in-app only, to the page's author and everyone who has commented. 3. **Page updated** — email and in-app, to people watching the page, at most once per page per editor per hour. 4. **Content expiry** — email and in-app, to the page's author seven days before a page expires, or to the site's owners if the author has left. 5. **Site member added** — email and in-app, to the person added. 6. **Approvals and refresh requests** — email and in-app, to the approver when a page is waiting, and to whoever asked (and the page's author) with the decision. The same switch tells a page's author and site owners when a refreshed page is ready to review. People can still change their own cadence, or turn off Sites email, in their account notification settings. ## What happens when I archive an asset? In **Site resources › Assets**, choose **Archive** from an asset's ⋮ menu or its own page. Admins can also select several and archive them together. The asset leaves the Assets list and every image, file and video picker, so nobody picks it for a new page. Every page already using it keeps showing it — pictures, documents, files and videos alike. To take it off a page, edit that page's section. Other apps that use it, such as Store, Recognition and Contests, stop showing it; the asset's page names them before you confirm. To use it again, choose **Archived** under **More filters** and select **Restore**. Only **Permanently delete**, which admins can use on an archived asset, removes the file; the asset's page says how many pages still use it before you confirm. --- ## Content expiry ## What does content expiry do? Any page with an expiry date stops being shown to readers when that date passes. It disappears from the site, Sites search and Ask AI, whether or not **Content expiry** is on. If the **Content expiry** notification is on, the author is warned seven days before the date. Editors who open an expired page see why it is hidden, with **Change expiry date** and **Archive page** buttons. Turning **Content expiry** on in Sites settings adds two things: - **A default date.** A page published without its own date expires after the **Default expiry period (days)**, which is 365 unless you change it. - **Automatic archiving.** Expired pages are archived overnight. The page's author is told, or the site's owners if the author has left. To send the seven-day warning to more people, pick a group under **Who else should hear about expiring content**. ## "A page I used to read now says it expired — where did it go?" The page passed its expiry date, so readers no longer see it. It says "This page expired on…" with the date. Nothing is deleted. Ask the site's owner or an editor to give the page a new expiry date if it is still accurate. --- ## When something looks wrong ## "I can't find the New site button" If the button is missing entirely, your role doesn't meet **Who can create a site?** Ask an admin to widen it. If the button is there but greyed out, your company has reached its site limit. Hovering shows "Site limit reached". An admin can archive a site or raise **Max sites** in Sites settings. Archived sites and sites in Trash don't count towards the limit. ## "I don't see the Sites Dashboard" The Dashboard is the desk of whoever looks after pages. From the top: a search of the pages in every site you can read; **Decisions waiting on you** — pages waiting for your approval, pages sent back to you, approved pages ready for you to publish, and pages scheduled to publish; **Pages that need care** — pages that need an owner, show a policy, form or person that changed, have broken links, are going stale, expire in the next 30 days, or have required reading people are behind on, each with a link to exactly those pages; **Your sites** — the sites you own or edit, with how many pages need care, reads over the last 30 days and when a page was last published; and **How your pages are doing** — reads, readers, Ask AI questions that used your pages, the most-read pages and the pages nobody read, over 7, 30 or 90 days. It shows for admins and Sites app admins, for anyone who may create a site or owns or edits one, for anyone asked to approve a page, and for page owners. Everyone else opens Sites on **All sites**, and finds their bookmarks and follows under **Saved & following**. On a phone, the same sections sit above the sites list when there is something in them. ## "I deleted a page by mistake — can I get it back?" Yes, for 90 days. Open the site's pages list, select **Trash**, and restore the page. Site owners and editors can do this. The page comes back as a draft, with its audience rules and menu position where those were recorded. Comments, translations, view history, watchers, bookmarks and past versions are deleted for good, apart from any version that asked readers to confirm they had read the page. ## "A linked policy or person on my page is out of date" Turn on **Self-maintaining content** in Sites settings. It flags a published page when a policy, form, person or event it links to changes or is removed. It also flags a page whose source web page has changed. The page's owner gets a refresh to review, apply or dismiss, and nothing on the live page changes until they apply it. ## "I translated a page but the translation looks out of date" Editing the original page marks its existing translations **Needs Update**. That way nobody mistakes an old translation for a current one. Translate the page again with AI, by hand, or with AI followed by a human edit. Sites supports 38 languages. ## "Part of my translated page is still in the original language" The page's **Translations** list counts the passages that read the same as the original: **"N passages may still be in English"** (or your company's language). This happens when a translation was made before some kind of text could be translated, or when part of an AI translation failed. Some of them may be right as they are, such as names that read the same in both languages. Choose **Translate missing**: only those passages are checked and translated, names that read the same are kept, and everything else, including corrections someone typed, stays as it is. When you edit the translation, each of these passages is marked **May not be translated yet**. A passage you change back to the original's wording, or one the AI leaves as it is, stops being counted. ## What happens to sites owned by someone who leaves the company? When the person is offboarded, sites they owned alone pass to their manager. If their manager isn't available, the sites go to another admin. Their other site memberships are removed, and approval requests waiting on them move to one of the site's remaining owners. No site or page is deleted. --- ## Licensing and limits ## Are there limits I should know about? | Limit | Default | Can I change it? | |---|---|---| | Sites per company | 50 | Yes — **Max sites**; 0 means no limit | | Pages per site | 100 | Yes — **Max pages per site**; 0 means no limit | | Upload size per file | 25 MB | Lower only — 25 MB is the ceiling | | Default expiry period | 365 days | Yes — used only while **Content expiry** is on | | Review pages every | 180 days | Yes — when a page counts as going stale | | Trash recovery window | 90 days | No | | Top-level navigation items | 10 | No | | Sub-items under one navigation item | 15 | No | | Navigation label length | 60 characters | No | | Translation languages | 38 | No | Emptying a limit box in Sites settings restores its default. --- ## More help - [Sites Overview](/help/articles/sites_app_overview) - Ask AI — the assistant answers Sites questions from these articles. ## Can I export Sites to another domain? Yes. A company admin or Sites app admin can open **Sites → Admin → Settings → Export & Import**. Export one site from its **Manage** menu, choose several sites, or select **All sites** for the whole Sites collection. Include Page starters and saved sections (**Include saved templates**) or archived content when needed. The package includes the latest saved pages and their referenced files; it does not copy activity, memberships, historical versions or other apps' records. Browse the export table or search by site name, filter by category and status, and sort by name, last updated or page count. Select individual sites, the current page, or all matching sites. Selections stay selected when you change filters or pages; **Show selected** lets you review them. Choose **All sites** explicitly to export everything eligible; an empty selection exports nothing. The form shows the site and page totals for your selection, including the archived-content option. During import review, each site shows its page count; package totals and the selected totals are shown separately. The completion page confirms how many sites and pages were created. Download the ZIP, then use **Import sites** in the destination domain. Review names, existing destination categories and appearance, then create the new drafts. Existing content and company settings stay unchanged. The destination must have Sites enabled. Packages support up to 200 MB, 500 sites and 5,000 pages; large collections can be split into smaller exports. Export downloads expire after seven days. ## What happens to public content and connected sections during import? Everything arrives as a draft. Company-wide visibility is preserved, and a formerly public site is identified in the result. Publish and enable sharing to create its new public link; source share links are never reused. Restricted content stays private. A section tied to a source user, department, form or other record keeps its content and layout but stays hidden until setup. **Finish setup** can connect supported records once for their repeated uses. You can keep content hidden or explicitly allow destination defaults and finish in the page editor. Changed records are skipped unless reviewed; reordered nested items and changed rich-text links are kept safe from automatic positional replacements. Page starters and saved sections stay private until you review and make them available to company editors. Translations stay retained until their language is enabled and their connections are resolved, then import as needing review. Names and personal details typed in authored content are preserved. ## Can I undo an import or retry one that failed? **Retry transfer** resumes a failed operation using its saved progress. Cancelling stops further work; incomplete drafts remain private. **Remove untouched imported drafts** removes only the new drafts belonging to that import. If they were edited, published, moved, or received additional content or setup, use the normal Sites controls to remove them individually. Imported files are retained privately instead of being deleted or silently shared. Expiring a ZIP never deletes a completed imported site. ## How can I tell whether a starter creates one page or a whole site? Cards in **Site resources → Starter sites** show **Single page** or **Multi-page** with the page count. Open **Preview** to use the site’s menu and switch between desktop and phone views. **All pages** includes pages outside the menu too. Saved **Page starters** each create one page. **Keywords:** faq, sites, pages, internal site, intranet, page builder, content review, page approvals, withdraw approval request, audience targeting, departments, translations, content expiry, expired page, trash, archive asset, follow a site, not showing, permissions --- # Skills & Credentials App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run the Skills & Credentials app — the catalog of skills, certifications, and licenses your workforce holds, with expiry tracking, verification, and role-based gap analysis. # Skills & Credentials ## 1. What it is Skills & Credentials tracks what your employees know, what they are certified to do, and when those credentials expire. It gives admins a single catalog of skills, certifications, and licenses; connects them to role requirements so you can see coverage gaps; and alerts you before a credential lapses. - **Enablement:** licensed, opt-in. An admin enables the app from Admin → Apps → All Apps. - **What it is not:** this app does not deliver training. Course enrollment and completion live in the Training app; when a course awards a skill, the holding appears here automatically. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps → Skills & Credentials → Enable**. The app appears in the sidebar. 2. Open **Catalog** and add your first entries. Each entry is one of three kinds — **Skill**, **Certification**, or **License**. You can type them one at a time, import a CSV, or load an industry template. 3. For certifications and licenses, set a **standard validity period** (in months) so expiration dates are prefilled when someone earns the credential. 4. Go to **Settings → Role Requirements** and map which skills and certifications each role type needs, with a minimum proficiency level and whether the requirement is critical. 5. To let employees add their own skills, leave the **Require Verification Before Profile Visibility** setting on (the default). Employees can submit skills and upload documents; each submission enters the **Action Center → Pending Verifications** queue for admin review before it is visible on their profile. 6. Confirm it worked: open **Dashboard**. You should see your catalog count, the staff coverage percentage, and any pending verifications. **What silently does nothing until both sides are wired:** role requirements only produce gap analysis when employees also have holdings recorded against those same catalog entries. If you define requirements but nobody has the skills assigned, every role shows 0% coverage. Populate holdings — via batch assign, CSV import, or employee self-service — before drawing conclusions from the dashboard. ## 3. How it fits together ### The catalog and its three kinds Every entry in your catalog is exactly one of three kinds: - **Skill** — a proficiency-rated capability with no expiry (e.g., "Forklift Operation", "Spanish Fluency"). - **Certification** — a credential issued by an authority, with an issue date and an expiration date (e.g., "CPR Certification"). - **License** — same as a certification but distinguished in reporting and compliance (e.g., "Registered Nurse License", "CDL Class A"). Both certifications and licenses require a validity period and go through the same expiry-tracking pipeline. Skills do not expire. **Worked example:** your catalog has three entries: "Forklift Operation" (skill), "OSHA 30-Hour" (certification, 60-month validity), and "CDL Class A" (license, 24-month validity). When an admin assigns OSHA 30-Hour to an employee and enters an issue date of 2026-01-15, the system prefills the expiration at 2031-01-15. Thirty days before that date, the employee and their manager are notified. ### Holdings and proficiency A holding is one employee's record of one catalog entry. Each holding carries a **proficiency level** from 1 (Basic) to 5 (Expert). The default proficiency labels are Basic, Beginner, Intermediate, Advanced, and Expert, but an admin can rename and redefine each level under **Settings → Proficiency Levels**. For certifications and licenses, the holding also carries a certification date, expiration date, and optional certification number. Each renewal creates a new period in the credential's history, so you can answer "was this person certified on date X?" without losing the original record. ### Verification When **Require Verification Before Profile Visibility** is on, a self-reported skill is created inactive and enters the admin verification queue. An admin can approve (the holding becomes active and visible) or reject it (it stays inactive). When the setting is off, self-reported holdings are active immediately. Employees can also propose skills that are not yet in the catalog. These proposals appear in the same queue, where an admin can map the proposal to an existing catalog entry or accept it as a new entry. ### Role requirements and gap analysis Each role type in your organization can have required skills mapped against it, each with a minimum proficiency level and a critical flag. The **People Graph** and **Team Readiness** surfaces use these requirements to compute per-person and per-role coverage, surface under-covered skills, and identify who could fill a gap. Requirements can be scoped to specific locations. A requirement marked for all sites applies everywhere; one scoped to a site applies only to employees whose home location matches. ### Issuing authorities Certifications and licenses can be linked to an issuing authority — the credentialing body that granted the credential (e.g., American Heart Association, a state nursing board). Admins manage these under **Settings → Issuing Authorities**. System-defined authorities are shared across all tenants and are read-only; tenant-created authorities can be edited or deleted. An authority can carry a **verification URL template** so the system generates a one-click verification link from the credential number. Four authority types are available: **Government**, **Professional body**, **Vendor**, and **Internal**. ### Credential documents and the audit trail Employees can upload supporting documents (PDF, JPG, PNG, DOC, or DOCX, up to 10 MB each) when they add or renew a credential. Catalog entries can be marked **Requires document upload**, which blocks submission without an attached file. Every download is audit-logged. When the **Require identity verification for credential documents** setting is turned on, the viewer must re-verify their identity before the download proceeds. ### Integration with other apps - **Training:** when a course or learning path awards a skill, completing it creates the holding automatically (source: training). - **Scheduling:** scheduling groups can filter by skill, so only qualified employees appear in a shift pool. Changing a holding triggers a background refresh of the affected groups. - **Practice Hub:** a certifiable practice scenario can mint a holding on a passing attempt (source: practice). - **Skill Swap:** employees can offer to teach a skill they hold, and the "Close Your Gaps" panel on My Readiness links to peer teachers. ## 4. Running it ### Reviewing pending verifications 1. Go to **Action Center → Pending Verifications**. 2. Filter by skill or location if needed. 3. For a standard claim, click **Verify** to approve or **Reject** with a note. 4. For a proposed new skill (no matching catalog entry), click **Review** to map it to an existing entry or accept it as new. The employee is notified of the decision. ### Reviewing inferred skills When Skills Inference is enabled under **Competency Assessment**, the system proposes skills for employees based on their activity. Proposals below the confidence floor appear in **Action Center → Skill Reviews** for manager review. A manager can accept (mints a verified holding) or dismiss. ### Tracking expiring credentials Go to **Action Center → Expiring Soon** (app administrators) to see certifications and licenses expiring within 30, 60 or 90 days, or already expired. Filter by location. Export to CSV for offline follow-up. ### Processing bonus incentives If a catalog entry is marked **Bonus eligible**, newly earned certifications appear in **Action Center → Bonus Incentives**. Mark each as processed once the payout is handled outside the system. Back-dated imports (certification date more than 30 days before the record was created) are excluded from this queue. ### Batch assigning skills Go to **Assignments → Batch Assign** to assign one skill or certification to multiple employees at once. Select the catalog entry, choose a proficiency level, and pick the employees. For skills that require a document upload, batch-assigned employees can upload their document later from their personal My Skills page. ### Running reports Go to **Reports** for top-line metrics: catalog size, staff coverage, expiring credentials, role coverage, and the top 10 most-held entries. Use the **As-of date** field to check how many credentials were valid on a past date — useful for incident investigations. ### Exporting credentials From **Reports → Credentials Export**, download a CSV of every verified credential in the organization, including employee name, job title, skill, proficiency, verification date, expiry, and status. ### What employees see Employees open **My Skills** to view their holdings, see what is expiring, and add or renew a credential. **My Readiness** shows their current proficiency, gaps against their role's requirements, and learning content that can close each gap. **Explore** is the catalog browser — employees can search by kind and see learning resources attached to each entry. **Credential Wallet** is a printable summary of their certifications and licenses. On a phone, My Skills — viewing, adding, editing and renewing credentials — has its own view, and managers get a Team Skills summary; My Readiness, Explore and the Credential Wallet are desktop pages. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Skills Tracking | Settings → Features | On | Enables the Skills tab in the catalog and skill-type holdings | | Certification Management | Settings → Features | On | Turns on the credential management pages: Expiring Soon, Pending Verifications, Bonus Incentives, Exclusion Reviews, Issuing Authorities, the credentials export and the certifications API. Employees keep their own certifications either way | | Competency Assessment | Settings → Features | On | Enables the People Graph, Team Readiness, and Skills Inference surfaces | | Training Records | Settings → Features | On | Shows training-source badges on holdings and links to the originating course | | Require Verification Before Profile Visibility | Settings → Features | On | Self-reported holdings start inactive and must be approved before they appear on the employee's profile | | Require identity verification for credential documents | Settings → Features | Off | Adds a step-up identity check before downloading uploaded credential evidence | | Skills & Credentials AI Agent | Settings → AI Agent card | On | Enables the in-app AI agent for skills-related questions | | Daily admin digest for expiring credentials | Settings → Features | Off | Replaces the per-credential admin expiry alerts with one daily summary; employee and manager alerts are unchanged | | Email and in-app alerts for expiring credentials | Settings → Features | On | Sends the expiring-soon and expired notices to holders and their managers; paused while the AI agent's Expiry Alerts capability is running | ### Notification settings Under **Settings → Notifications**, each event can be toggled on or off, with separate checkboxes for the employee, their manager, and all app admins, plus optional extra email addresses. Events include: credential expiring soon (default lead time: 30 days), credential expired, daily admin digest, credential assigned, credential removed, credential submitted for review, credential approved or rejected, employee missing a required credential, the weekly team skills-gap report, license-check problems (never sent to the employee automatically) and exclusion-list matches (admins only). ## 6. More help - **Skills & Credentials FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about Skills & Credentials from these articles. **Keywords:** skills, certifications, credentials, licenses, proficiency, expiring certifications, skill gap, role requirements, verification, competency, credential wallet, skills-certifications, skills_certifications, skills-&-credentials --- # Skills & Credentials FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-18 Answers to common setup and operating questions about Skills & Credentials — for admins, managers and the employees who ask them. # Skills & Credentials FAQ Answers to common setup and operating questions about Skills & Credentials. For what the app is and how to set it up from scratch, see the [Skills & Credentials Overview](/help/articles/skills_certifications_app_overview). --- ## Setup ## Do I need to configure anything before employees can use the app? Yes — an administrator must first enable Skills & Credentials from Admin → Apps → All Apps. The app is disabled by default and requires a license. Once it is on, the four core modules — Skills Tracking, Certification Management, Competency Assessment and Training Records — are already switched on. Employees can start adding skills from My Skills straight away. ## Which features can I turn on or off in Settings? Each toggle on the Settings page is independent. These are **on** by default: - **Skills Tracking**, **Certification Management**, **Competency Assessment** and **Training Records** — the four core modules. - **Require Verification Before Profile Visibility** — a submitted skill stays off the employee's profile until someone verifies it. - **Email and in-app alerts for expiring credentials**. - **Automated license verification and exclusion screening** — only does anything once a screening integration is set up. These are **off** by default: - **Require identity verification for credential documents**. - **Daily admin digest for expiring credentials**. - Five shift rules: **Credentials must be valid on the shift date**, **Block revoked credentials**, **Only verified credentials satisfy requirements**, **Licenses must match the work location's jurisdiction** and **Block clock-in when a required credential is missing**. Turning Certification Management off hides the management pages, not anyone's records. Employees still see their own certifications on My Skills. ## How do I set which course earns a credential? You can link it from the credential itself, without opening Training. 1. In the catalog, open the skill, certification or license and choose Edit. 2. Find the **How this … is earned** section and pick one or more published courses under **Courses that award it**. 3. Save. Completing any linked course then grants the credential. When it expires, a renewal automation re-assigns that same course. This is the same link as the awarded-certification setting on the course form, so a change on either side shows on the other. The picker only appears when Training is turned on for your business. **Reference links** in the same section are preparation material and grant nothing. ## Why is a course greyed out in the "Courses that award it" picker? A course can award at most one certification. If a course already awards a different certification, it appears disabled with "already awards …" next to its name. If a save would break that rule, the course is left unlinked and the confirmation message names it. Plain skills are not limited this way. --- ## Permissions and access ## Who can manage the catalog, assign skills and run imports? Business administrators and anyone made an app admin for Skills & Credentials. The catalog, Assignments (including Batch assign and CSV import), Expiring Soon, and the Settings page are all reserved for them. Other users who open those pages are sent back to the home page with a message saying the page is for administrators. ## Who can see the team's skills and readiness, and can I change that? By default, managers — anyone at manager level or above. You can change it in Settings under **Who can do what** → **Who can see the team's skills and readiness?** The choices are everyone with access to the app, managers, people managers (anyone with direct reports), app admins only, or specific people. It covers Team Readiness, People Graph, Team Builder and Skill Reviews. Whoever holds it still sees only people inside their own reach. ## I manage a region — whose skills can I see? Everyone assigned to your region and to every location beneath it, plus your direct reports. A manager assigned to a region reaches all the stores under that region in Team Readiness, People Graph, Team Builder, Skill Reviews and Team Skills. Someone below manager level who has been given team access sees only their direct reports and the locations they are personally assigned to. ## Who can verify a credential someone has claimed? By default, only administrators and Skills & Credentials app admins. To widen it, go to Settings → **Who can do what** → **Who can verify a credential someone has claimed?** You can choose managers or specific people. Nobody can verify their own credential, including administrators. Pending Verifications lists every pending claim in the business except your own. ## Why isn't my new skill showing on my profile? It is waiting to be verified. With **Require Verification Before Profile Visibility** on (the default), a skill or credential you submit stays off your profile until a verifier approves it. You still see it in My Skills marked as pending. Once it is approved, it shows up for everyone straight away. --- ## Day-to-day ## How do I add a skill that isn't in the list? Type the skill's name on My Skills and submit it. It goes in as a proposal for review. The reviewer sees up to five similar catalog entries. They can map your proposal to one of those or create a new catalog entry from it. ## How do I add a certification or upload a certificate I just earned? Open **My Skills**. In the **Certifications** section choose **Add Certification** (licences have their own **Add License**), pick the entry from the catalog, and fill in the issue date, the expiration date and the number. A licence also needs its jurisdiction. Attach the file and save. PDF, JPG, PNG, DOC and DOCX files under 10 MB are accepted. Anyone can do this; no admin role is needed. If the certification is not in the catalog, type its name and submit it as a proposal for review. A self-reported certification goes to a verifier for review; with **Require Verification Before Profile Visibility** on (the default) it stays off your profile until it is approved. To attach a file to an entry you already have, use **Upload document** on its row where it is offered. To renew one that is expiring or has expired, use **Renew** on its row and attach the new document there. ## Why did my verified skill go back to pending after I edited it? Editing a verified skill or credential resets its verification — for example, changing the proficiency level or the dates. If **Require Verification Before Profile Visibility** is on, it is also hidden from your profile until it is approved again. Uploading a document to an already-verified entry does **not** reset it; the confirmation says "Verification status preserved." ## How does certification renewal work? A renewal closes the current validity period and opens a new one, so the history is kept rather than overwritten. The old period is marked as superseded, and the new one links back to it. The renewed credential goes back through verification, whatever its earlier status. Reviewers are notified the same way as for a new submission. ## How do I assign a skill to many employees at once? Use **Batch assign** on the Assignments page. Pick the skill and the employees; the proficiency level is pre-set to 3 (Intermediate), and you can change it before you assign. Batch assign does not mark the credential as verified. For someone who already holds the skill, it updates the dates you enter and leaves their proficiency level alone. ## What does the employee-skill CSV import need, and how does it match people? The file needs a skill name column plus at least one of the email or userid columns. The certification date, expiration date, certification number and proficiency level columns are optional. The full header row is: ``` skill_name,email,userid,certification_date,expiration_date,certification_number,proficiency_level ``` The skill must already be in the catalog — the import does not create catalog entries. People are matched by email first, then by userid as a user ID, an external employee ID or a username. Skill names match regardless of case and extra spaces. Imported credentials are recorded as verified by the admin who ran the import. ## What notifications can I configure? Settings → Notifications has eleven events in five groups. Each event has its own recipient choices (employee, manager, admins), and you can add email addresses outside your user list: - **Expiry** — Credential expiring soon (lead time defaults to 30 days, accepts 1–365); Credential expired; Daily admin digest of expiring credentials. - **Assignment** — Credential assigned to employee; Credential removed from an employee's record (also sent, once for each person who held it, when an admin deletes the catalog entry itself — the notice then says it was "removed from the catalog"). - **Verification** — Credential submitted for review; Credential approved or rejected. - **Role gaps** — Employee missing a required credential for their role (off by default); Weekly team skills-gap report for managers. - **Screening** — License check with the issuing board failed or reported a problem; Exclusion-list match needs someone to confirm identity. ## I turned on the daily admin digest — will admins still get individual expiry emails? No. With **Daily admin digest for expiring credentials** on, admins stop getting a separate alert for each credential that is expiring soon or has expired. Employee and manager alerts continue as before. The digest goes out daily at 08:30 UTC. It covers credentials expiring in the next 30 days and those that expired in the last 14 days. ## How do Training and Practice Hub add credentials? Completing a course or learning path that awards a skill writes the credential into Skills & Credentials automatically. The credential's page then shows **Earned from** with a link to that course or path. Passing a certifiable scenario in Practice Hub records the credential at proficiency level 3. Its expiry is set from the scenario's recertification interval. Practice Hub skips any credential that requires a document upload, because it cannot supply the document. --- ## When something looks wrong ## "My certification disappeared after I renewed it" It is still there — renewing closed the old validity period and opened a new one. The new period is the current one, and it waits for verification like any fresh claim. The superseded period is kept for history and compliance reporting. ## "I uploaded my licence but it still says unverified" Uploading a document does not change verification status on its own. A verifier still has to approve the credential from Pending Verifications. If **Require Verification Before Profile Visibility** is on, it stays off your profile until then. Ask your manager or admin who reviews credentials in your business. --- ## Licensing and limits ## Are there limits I should know about? | Item | Limit | |---|---| | Proficiency levels | 5 (names and descriptions can be changed in Settings) | | Standard validity period for a catalog entry | 1–120 months, or none | | Credential document size | Under 10 MB per file | | Accepted document formats | PDF, JPG, PNG, DOC, DOCX | | CSV import file size | Up to 10 MB | | CSV proficiency level | Whole number 1–5; blank means 1 (Basic) for a new assignment | | Import processed in the background | 100 rows or more | | Expiring-soon lead time | 1–365 days (default 30) | | Expiring Soon windows | 30, 60 or 90 days, plus Expired | | Expiring Soon list | 50 per page, exportable to CSV | | Certifications a course can award | 1 | --- ## More help - [Skills & Credentials Overview](/help/articles/skills_certifications_app_overview) - [Training FAQ](/help/articles/training_app_faq) — setting awarded skills from the course side. - Ask AI — the assistant answers Skills & Credentials questions from these articles. **Keywords:** faq, skills, certifications, licenses, licences, proficiency, verification, pending verifications, expiring certifications, renewal, earned from, course awards credential, regional manager, team readiness, csv import, batch assign, not showing, permissions, skills-certifications, skills_certifications, skills-&-credentials --- # Skill Swap App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How Skill Swap works, how to set it up, and how to manage the peer-learning marketplace where employees share expertise. # Skill Swap ## 1. What it is Skill Swap is an internal marketplace where employees post what they can teach and what they want to learn, then get matched into time-boxed learning partnerships. It turns informal knowledge-sharing into a structured programme with profiles, a searchable opportunity board, skills-based matching, session tracking, and ratings. - **Enablement:** Skill Swap requires a license. An admin enables it per tenant from **Admin → Apps → Skill Swap**. - **What it is not:** Skill Swap is not a formal training or certification system. It is peer-to-peer. For instructor-led courses and certifications, use Training or Practice Hub. ## 2. Standing it up 1. Go to **Admin → Apps → Skill Swap → Settings** (the Settings tab inside the app, which routes to the admin configuration page). 2. Click **Enable App** in the App Status card on the right. Until the app is enabled, employees cannot see it. 3. Review the **Workflow settings**. Two decisions matter most: - **Cross-Department Matching** (on by default) — when off, each person's board shows only their own department's opportunities, they can join only those, invitations stay within a department, and recommendations only suggest colleagues from it. - **Max Concurrent Learning Partnerships** (default **5**) — how many active partnerships each employee can hold before joining another, as mentor or learner. The choices are 3, 5, 10, or Unlimited. Posting opportunities is never limited. 4. Set a **Default Partnership Duration** (default **8 weeks**). This sets the expected end date for partnerships whose opportunity posting did not specify a duration. Progress bars and overdue indicators depend on it. 5. Decide whether to turn on **Auto-Complete Partnerships** (off by default). When on, a nightly sweep completes any active partnership past its expected end date and notifies both participants. When off, partnerships stay active until someone completes them manually. 6. Save the settings. Employees can now open Skill Swap from the app launcher, create a profile, and start posting opportunities. The app has six tabs visible to all users — **Dashboard**, **My Profile**, **Opportunities**, **Skills & Interests**, **Matches**, and **Partnerships** — plus a **Settings** tab visible only to admins and app admins. On mobile devices, Skill Swap automatically redirects to its mobile-optimized views. ## 3. How it fits together Skill Swap has four concepts that build on each other: profiles, opportunities, matches, and partnerships. **Skill Profile** — every employee who opens Skill Swap creates one. A profile holds a bio (minimum 50 characters), availability hours (0–40 per week), a preferred meeting style, and two skill lists: skills they can teach and skills they want to learn. The profile must exist before the employee can browse or post anything — opening Skill Swap without one redirects to the setup page. The preferred meeting style choices are: **Virtual**, **In-person**, **Both virtual and in-person**, **Lunch & learn sessions**, and **Flexible**. Each teachable skill carries a proficiency level (Beginner, Intermediate, Advanced, or Expert) and an availability toggle. Turning the toggle off hides the skill from matching without deleting it. The skill name has a 2–100 character limit and must be unique per profile. Each learning interest carries a current level (Beginner, Intermediate, or Advanced) and a priority: **Actively looking**, **Interested**, or **Someday**. The same name limits and uniqueness rule apply. When a teachable skill or learning interest name matches a skill in the organisation's skill catalog, the system links them automatically. This connection feeds the broader skills graph — for example, completing a partnership proposes the taught skills into the learner's certified skill profile for review. **Opportunity** — a posting on the board. It has four types: - **Teaching** — the poster is the mentor and teaches skills to participants. - **Learning** — the poster is the learner and seeks mentors. - **Project** — the poster leads a collaborative project; participants learn by contributing. - **Group** — similar to a project but focused on group learning. An opportunity has a title (5–200 characters), a description (10–2,000 characters), a list of skills needed, a list of skills offered, a maximum number of participants (1–50, default 1), and an optional expiry date and duration in weeks. Example: an employee posts a Teaching opportunity titled "Excel Pivot Tables & Power Query", lists "Excel" and "Data Analysis" as skills offered, sets max participants to 3 and a duration of 8 weeks. Three colleagues express interest; the owner reviews each match's compatibility score and accepts the best ones. An opportunity moves through these states: **Open** (accepting participants), **Full** (at capacity), **Paused** (temporarily hidden), **Completed**, **Cancelled**, or **Expired**. A daily automated sweep expires active opportunities past their expiry date and notifies the owner. **Match** — when an employee expresses interest in an opportunity, a pending match is created. The opportunity owner reviews it and accepts or rejects it. There are two flows: - **Self-initiated interest:** an employee finds an opportunity on the board, adds an optional message (up to 500 characters), and submits. The opportunity owner decides. - **Invitation:** the opportunity owner invites someone from the Recommendations page. The invited employee decides. Interest can be withdrawn while still pending, and an owner can withdraw an invitation the invited person has not answered yet. Owners can tick several pending requests and choose **Accept selected** or **Reject selected** to process them at once. A request or invitation nobody answers within 45 days is closed as **Expired**; an expired request does not stop the same person asking again while the opportunity is open. **Learning Partnership** — created automatically when a match is accepted. It pairs a mentor and a learner. For a Teaching opportunity, the poster is the mentor. For a Learning opportunity, the interested employee is the mentor. For Project and Group opportunities, the poster leads. The partnership sets an expected end date (from the opportunity's duration, or the admin-configured default if none was specified). Both participants can: - Schedule sessions (types: Virtual, In-person, Lunch & learn, or Phone call; max 480 minutes each). - Mark sessions complete, cancel them, or record a no-show. - Pause or resume the partnership. - Complete it when done — a paused partnership too. If either partner leaves the organization, their partnerships are paused and the other partner is told. They can complete the partnership from its page; it can resume if the person comes back. On completion, both parties rate each other on a 1–5 scale and leave written feedback. The learner's rating flows back to the mentor's average teaching rating on the relevant teachable skill — including a skill the mentor lists only afterwards, which starts with the rated partnerships they already finished teaching it. Completing a partnership also proposes the taught skills as new entries in the learner's skills profile for review. ## 4. Running it ### Reviewing matches Go to **Skill Swap → Matches**. The page shows two lists: interest received on your opportunities and interest you expressed in other opportunities. Filter by status — Pending, Accepted, Rejected, or Expired. Tick several pending requests and choose **Accept selected** or **Reject selected** to process them at once. Each match detail page shows a compatibility score (based on overlapping teachable skills and learning interests) and the specific skills that matched. ### Featuring an opportunity Admins and app admins can mark an opportunity as **Featured**. The three newest featured opportunities are pinned above the board while no search or filter is applied; on phones, featured opportunities are marked Featured and listed first until a search or type filter is applied. To feature an opportunity, edit it and check the Featured checkbox — this checkbox only appears for admin-level users. ### Inviting employees From **Skill Swap → Matches → Recommendations**, the system shows potential matches for each of your active opportunities, scored by skill overlap. Click **Invite** next to an employee to send them an invitation. The invitee receives a notification and decides whether to accept or decline. ### Managing the opportunity board The opportunity board at **Skill Swap → Opportunities** shows all active postings. Employees can search by keyword, filter by opportunity type (Teaching, Learning, Project, Group) and status, or filter by specific skills (comma-separated). Sorting options are newest first (default) or most popular (by interest count). Non-active opportunities (paused, completed, cancelled) are visible only to their owner and to admins. ### Monitoring partnerships Go to **Skill Swap → Partnerships**. The page shows partnerships where you are either mentor or learner, with summary statistics: total active, total completed, total hours, and counts as mentor versus learner. Each partnership card shows a progress bar based on elapsed time versus the expected end date. An overdue badge appears when a partnership passes its expected end date without being completed. Inside a partnership, the session timeline shows upcoming and past sessions separately. You can schedule new sessions, log past ones, and track total hours. ### Viewing analytics Admins and app admins can open **Skill Swap → Settings → View Analytics** to see: - Skills growth over time (last 6 months of teachable skills and learning interests added). - Opportunities by type (doughnut chart). - Partnership success rate trend (last 6 months). - Most taught skills and most wanted skills tables. - Most active mentors and most popular opportunities. - Profile adoption (current members who have a Skill Swap profile versus those who do not). Analytics can be filtered by time period (current month, last month, current quarter, last quarter, current year) and by department. Export to CSV or JSON from the **Export** dropdown. ### Notifications Skill Swap sends notifications for these events (when the admin's notification settings allow): - Someone expresses interest in your opportunity (action request to the owner). - Your interest is accepted or rejected (to the interested employee). - You are invited to an opportunity (action request to the invitee). - An invitation you sent is accepted or declined (to the owner). - Your opportunity expires (to the owner). - A request or invitation went unanswered for 45 days and was closed (to the person who was waiting). - A partnership is auto-completed (to both mentor and learner). Notifications go to the in-app Inbox by default. Email delivery can be turned off separately from the Settings page. ## 5. Settings All settings live at **Skill Swap → Settings** (the Settings tab, which routes to the admin configuration page). Admins and app admins can access it. | Setting | Default | What it changes | |---|---|---| | **Enable AI Agent** | On | When off, users cannot query Skill Swap data through Ask AI. | | **Cross-Department Matching** | On | When off, each person's board shows only their own department's opportunities and they can join only those; invitations and recommendations stay within a department. | | **Max Concurrent Learning Partnerships** | 5 | How many active partnerships an employee can hold before joining another, as mentor or learner. Posting is never limited. Choices: 3, 5, 10, or Unlimited. | | **Enable Notifications** | On | Master switch — when off, Skill Swap sends no notifications at all. | | **Notification Level** | All events | Set to **Important only** to keep requests, invitations and reminders, accepted matches, session changes, completed or paused partnerships, and deleted or paused postings, and skip updates like declined or withdrawn requests, expirations and ratings. | | **Email & Push Notifications** | On | When off, notifications land in the in-app Inbox only — no email or phone push is sent. | | **Default Partnership Duration** | 8 weeks | Sets the expected end date for partnerships whose opportunity did not specify a duration. Choices: 4, 8, or 12 weeks. | | **Auto-Complete Partnerships** | Off | When on, a nightly sweep completes active partnerships past their expected end date and notifies both participants. | The Settings page also shows usage statistics (skill profiles, opportunities, active partnerships, skills offered and skills wanted) and an **Enable App** / **Disable App** button for the app itself. A **Reset to Defaults** button restores all settings to the values listed above. A **Load Sample Data** card lets you load realistic demo data to explore the app before rolling it out. ## 6. More help - **Skill Swap FAQ** — specific setup and operating questions. - **Employee Performance Management → Integrations → Skill Swap** — optional integration that maps skill profiles to competency frameworks and development plans. - Ask AI — the assistant answers questions about Skill Swap from these articles. **Keywords:** skill swap, peer learning, mentoring, knowledge exchange, teach skills, learn skills, skill profile, learning partnership, opportunity board, mentor matching, skill-swap, skill_swap --- # Skill Swap FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Skill Swap — for the admin running it. # Skill Swap FAQ Answers to common setup and operating questions about Skill Swap. For what the app is and how to set it up from scratch, see the [Skill Swap Overview](/help/articles/skill_swap_app_overview). --- ## Setup ## Do I need to configure anything before employees can start using Skill Swap? Enable the app from Admin → Apps → All Apps — it is disabled by default and requires a licence. Once enabled, every employee can create a skill profile and browse the opportunity board. No other prerequisite is required, though you may want to review the default settings under the Settings tab before announcing the app. ## Who can access Skill Swap once it's enabled? Every active employee in the organization can create a profile, post opportunities, express interest, and manage their own partnerships. The Settings and Analytics tabs are visible only to administrators and Skill Swap app admins. App admins can also edit or delete any opportunity, not just their own. --- ## Permissions and access ## Who can change Skill Swap settings and view analytics? Administrators and Skill Swap app admins. Both roles see a Settings tab in the app's sidebar that opens the configuration page and an Analytics link to the dashboard. App admins have the same record-level access as full administrators within Skill Swap — they can edit any opportunity and manage all matches. ## Why can't an employee see the Settings tab? The Settings tab appears only for administrators and Skill Swap app admins. A regular employee sees the six other tabs — Dashboard, My Profile, Opportunities, Skills & Interests, Matches, and Partnerships — but not Settings. To grant someone access, assign them the Skill Swap app admin role. --- ## Day-to-day ## How does matching work? Matching is skill-overlap based. When an employee views an opportunity's recommendations, the system scores each candidate on how well their teachable skills overlap with the skills the opportunity needs (each match adds 10 points) and how well their learning interests overlap with what the opportunity offers (each match adds 8 points). A cross-department match adds a 5-point bonus. Candidates with zero shared skills are never surfaced. Each match card shows a compatibility score and the specific shared skills. You can restrict matching to the same department under **Workflow settings > Cross-Department Matching**. ## What are the four opportunity types? Teaching (someone offers to teach a skill), Learning (someone requests to learn one), Project (a project needing specific skills), and Group (a group session such as a lunch-and-learn). For Teaching, Project, and Group postings the creator becomes the mentor; for a Learning posting the interested person becomes the mentor. ## What happens when someone expresses interest in an opportunity? A pending match record is created and the opportunity owner receives a notification. The owner reviews the match, sees the compatibility score and shared skills, and accepts or rejects. Accepting creates a learning partnership with a start date and an expected completion date. The interested person is notified of the outcome. ## Can I pin an opportunity to the top of the board? Yes. Administrators and Skill Swap app admins can mark an opportunity as **Featured**. The three newest featured opportunities are pinned above the board while no search or filter is applied; on phones, featured opportunities are marked Featured and listed first until a search or type filter is applied. Regular employees cannot feature their own postings. ## What happens when a partnership is completed? Both partners can rate each other on a 1–5 star scale and leave written feedback. The learner's rating updates the mentor's average teaching rating for that skill. A skill the mentor adds to Skills I Can Teach after they already taught it — or renames an untaught skill to — starts with the rated partnerships they finished teaching it, so nothing taught before the skill was listed is lost. If the skills taught match entries in the organization's skills catalog, the platform proposes a skill signal for the learner — a record that enters the skills-inference review flow as a suggestion, not a confirmed skill. ## Can the opportunity owner invite someone directly? Yes. The owner can invite a specific employee to their opportunity. An invitation sends the invitee a notification; the invitee accepts or declines. This is separate from the normal express-interest flow — for an invitation, the invited employee is the one who decides, not the owner. --- ## When something looks wrong ## Why can't I join another opportunity? Each employee can be in a limited number of active learning partnerships at once, as mentor or learner. The default is 5; your admin may have set it to 3, 10, or Unlimited under **Max Concurrent Learning Partnerships**. At the limit you can't express interest, be invited, be accepted or resume a paused partnership on someone else's opportunity until one is completed or paused. Posting your own opportunities is never limited, and people accepted into your own opportunity are limited by its **Maximum Participants** instead. ## I expressed interest but nothing happened — what's going on? Your interest is pending until the opportunity owner accepts or rejects it. The owner receives a notification, and a reminder if they have not answered after a week. You can check the status on the Matches page under **My Interest & Invitations**. You can withdraw a pending interest at any time; once it has been accepted or rejected, it cannot be withdrawn. A request nobody answers within 45 days is closed and shown as **Expired**, and you are told in your Inbox unless Skill Swap notifications have been limited or turned off. That is not a decline: while the opportunity is still open you can express interest again from its page. The same applies to an invitation the invited person never answered — it closes after 45 days and the person who sent it is told the same way. The person who sent an invitation can also withdraw it while it is unanswered, from its match page. ## My opportunity disappeared from the board — what happened? If you set an expiry date, a nightly maintenance sweep marks expired opportunities as Expired and removes them from the active board. The sweep runs daily. You are notified when this happens, unless Skill Swap notifications are limited to Important only or turned off. The opportunity still appears in your My Opportunities list with an Expired status. To reopen it, edit it, set a new closing date and switch its status back to Active. ## Why are my employees not getting Skill Swap notifications? Check three settings under the Settings tab. **Enable Notifications** is the master switch — when off, nothing is sent. **Notification Level** controls which events fire: **All events** sends everything; **Important only** sends requests, invitations and reminders, accepted matches, session changes, completed or paused partnerships, and deleted or paused postings, and drops updates like declined or withdrawn requests, expirations and ratings. **Email & Push Notifications** controls whether notifications also go out as email and phone push — turning it off limits delivery to the in-app Inbox. ## A partnership has been sitting active for months — can it close automatically? Yes, but you need to opt in. Turn on **Auto-Complete Partnerships** under **Learning settings**. A nightly sweep then marks any active partnership past its expected completion date as completed and notifies both participants. The expected completion date comes from the opportunity's duration or from the **Default Partnership Duration** setting (4, 8, or 12 weeks; default is 8 weeks). ## The board says "Full" but the opportunity is still active — what does that mean? An opportunity can be Active and Full at the same time. "Full" means the number of active partnerships has reached the participant cap, so no new interest can be accepted. A place opens again when one of its partnerships is completed or paused, or the owner can increase **Maximum Participants** (up to 50) by editing the opportunity. --- ## AI agent ## What can the Skill Swap AI agent do? When the **Enable AI Agent** toggle is on (it is on by default), employees can interact with Skill Swap through Ask AI. The agent can browse open opportunities, search for mentors who teach a specific skill, show the employee's own profile and stats, and list their partnerships. It can also take actions — completing or pausing a partnership, or pausing an opportunity — but it always shows a preview of the change and asks the employee to confirm before writing anything. --- ## Licensing and limits ## Does Skill Swap require a licence? Yes. Skill Swap requires a licence and is disabled by default. An administrator enables it from Admin → Apps → All Apps. An administrator can also switch it off again from Skill Swap's Settings page. ## What are the limits I should know about? | Limit | Value | |---|---| | Active learning partnerships per employee | 5 by default (admin can set 3, 5, 10, or Unlimited); posting opportunities is not limited | | Participants per opportunity | 1–50 | | Opportunity title | 5–200 characters | | Opportunity description | 10–2,000 characters | | Skill name | 2–100 characters | | Interest / response message | Up to 500 characters | | Session duration | Up to 480 minutes (8 hours) | | Rating scale | 1–5 stars (both mentor and learner) | | Profile bio | Minimum 50 characters | | Weekly availability | 0–40 hours | | Proficiency levels (teachable skills) | Beginner, Intermediate, Advanced, Expert | | Learning interest priority | Actively Looking, Interested, Someday | | Default partnership duration | 8 weeks (admin can set 4, 8, or 12) | | Analytics export formats | CSV and JSON | | Analytics time periods | Current month, Last month, Current quarter, Last quarter, Current year | --- ## More help - [Skill Swap Overview](/help/articles/skill_swap_app_overview) - Ask AI — the assistant answers Skill Swap questions from these articles. **Keywords:** faq, skill swap, opportunities, partnerships, mentoring, matching, skill profile, teaching, learning, notifications, auto-complete, cross-department, skill-swap, skill_swap --- # Slack — Notifications, /mango Commands, Must-read Messages and Channel Posts **Category:** System-features **Section:** Advanced Features **Updated:** 2026-10-16 How to connect OneMango to your Slack workspace, choose which apps send notifications and run /mango commands, send must-reads as direct messages, and roll it out to your people. # Slack ## 1. What it is Connecting Slack lets OneMango meet people where they already chat. They get OneMango notifications in Slack, use `/mango` commands to raise tickets or recognize a colleague, and approve recognition nominations from the message itself. Admins can also post a notice about a Communication (a sign-in link to read it) and shared items to Slack channels. Once you turn it on, the MangoApps app also sends each person a private Slack message when a must-read is waiting on them. They can acknowledge it there. - **Enablement:** an administrator connects your Slack workspace once, then chooses app by app what Slack may do. Must-read messages, Share and Ask AI each have their own switch. - **What it is not:** asking Slackbot about OneMango work ("what needs me this shift?") is a separate feature, controlled in **Admin → Security → Connectors**. See *AI Assistants*. ## 2. Standing it up 1. Go to **Admin → Organization → Integrations**, choose **Manage Messaging & Sharing**, then **Connect Slack** on the Slack card. Sign in to Slack as someone allowed to add apps to your workspace, and approve. If **Connect Slack** is greyed out, MangoApps hasn't finished setting up Slack for your environment. Contact support. 2. Open the Slack page (**Configure**). Under **Add App**, pick an app and tick what it may do: - **Slash Commands:** its `/mango` commands work in Slack. - **Notifications:** its notifications are sent to Slack. - **Channel Posting:** it can post to a channel. Communications needs a channel chosen here. Click **Register App**, and repeat for each app. The **Commands** card on the right shows which commands are now on. 3. Optionally choose a **Default Channel**, and whether **Share** may post to Slack channels. 4. Optionally turn on **Send must-reads as direct messages** on the **Must-read messages** card (see §3). You don't need to add an app under **Add App** for this. 5. Tell your people. The **Tell your employees** card has a message ready to copy and send. Nothing in Slack announces the connection on its own. 6. To check it works, type `/mango help` in any Slack channel. You should see the commands you turned on. **Test Connection** at the top of the page checks that OneMango can still reach your workspace. ## 3. How it fits together **People are matched by work email.** OneMango finds a person by the email on their Slack profile, which must match their OneMango email. Only people who are active in your organization are matched. Someone who can't be matched can still type `/mango help` but can't raise tickets or give recognition. They also get no must-read messages in Slack; they still see the item in OneMango. **A command runs only when two things are true.** Its app was added with **Slash Commands** ticked, and the person has access to that app in OneMango. `/mango help` lists exactly the commands that person can use. **Replies are private.** Every `/mango` reply is visible only to the person who typed it, even in a busy channel. **Buttons act for the person who clicks.** Approve and Decline on a nomination card check that the clicker is allowed to decide. When it works, the card changes in place to show the outcome and the buttons disappear. When it doesn't, only the clicker sees why. **The app's Home tab.** Opening the MangoApps app in Slack shows each person the commands they can use. **Must-read messages are direct messages.** A must-read is anything that asks a person to acknowledge, confirm or complete it. When **Send must-reads as direct messages** is on, the MangoApps app messages each person privately in Slack when one of these is sent: | What is sent | Who gets a message | What the message carries | |---|---|---| | A must-read post | Each person asked to acknowledge it | Summary, link and an **Acknowledge** button | | A broadcast that asks for acknowledgement | Each person it was sent to | Summary, link and an **Acknowledge** button | | A Sites page published with **Ask readers to confirm they've read it** | Each reader asked to confirm | Summary and a link only | | A SOP published for people to complete | Each person assigned to complete it | Summary, due date and a link only | A Sites page is confirmed, and a SOP completed, on its own page in OneMango. That is why they arrive as a link and never with an **Acknowledge** button. For example: HR publishes a must-read post, "Updated uniform policy", to the Warehouse team. Each person on that team who hasn't acknowledged it gets a Slack message from the MangoApps app. It shows the title, who it's from, a short summary, **Acknowledge** and **Open in MangoApps**. Clicking **Acknowledge** records the acknowledgement in OneMango. The message then changes to "✓ You acknowledged this." A few rules decide who is messaged, and when: - **Only people still owed it.** Anyone who has already acknowledged, confirmed or completed it is skipped. So is its author. The same person is never messaged twice about the same ask on one connection. A Sites page republished with a new ask counts as a new one. - **The item's own delivery rules apply.** A broadcast set to **Only people currently on shift** never messages someone who is off shift. One set to **Defer off-shift people to their next shift** holds their message until that shift starts. Unless a broadcast is critical, **Right to Disconnect (off-shift protection)** holds its message back too, as it does for Sites pages and SOPs. A must-read post is sent straight away, like its push notification. Anyone held back still finds the item in OneMango. - **A SOP follows SOP Hub's own switch.** It is messaged only while **Tell Employees When a New Procedure Needs Completing** is on in SOP Hub settings. - **Each person reads it in their own language.** The labels and buttons use the display language on the person's profile. The title and summary use the language they would read the item in within OneMango, where a translation exists. Otherwise the original is shown. - **The summary is written by AI.** The message footer says so. - **The button belongs to one person.** If someone else clicks it, they are told it was sent to someone else, and nothing is recorded. The button works for 30 days; after that it points the person to OneMango. **The switch is per connection.** It is set separately on the Slack page and the Microsoft Teams page. A person reachable in both, with both switched on, gets a message in each. **Ask AI in Slack.** Off by default. When an admin ticks **Let people ask Ask AI in Slack** on the Slack page's **Ask AI** card, people can type `/mango ask` followed by a question for a private answer. They can also message the MangoApps app directly, or @mention it in a channel to get an answer in the thread. Direct messages and @mentions need permissions Slack connections made before this feature don't have: the card says so, and an admin reconnects Slack to approve them. If the card says **Not available yet**, MangoApps hasn't finished setting up its Slack app for your environment. Answers use the person's own OneMango access and need Ask AI to be available to them. In a channel, personal questions (pay, leave, reviews and the like) are not answered, and nothing is changed; the reply says to ask privately. A change that someone asks for privately shows a card with Approve and Decline. Only the person who asked can approve it, it expires after 10 minutes, and it works once. ## 4. Running it ### Supporting your people's /mango commands | Command | What it does | Needs | |---|---|---| | `/mango help` | Lists the commands you can use | Always available | | `/mango ask [question]` | Asks Ask AI; only you see the answer | Ask AI turned on for Slack, and Ask AI available to you | | `/mango ticket [description]` | Raises a Service Desk ticket | Service Desk | | `/mango mytickets` | Shows your open tickets | Service Desk | | `/mango ticket_status [ID]` | Shows one ticket's status | Service Desk | | `/mango recognize [email] [message]` | Recognizes a colleague | Recognition | | `/mango myrecognition` | Your recognition summary | Recognition | | `/mango leaderboard` | The recognition leaderboard | Recognition | ### Changing what an app may do in Slack 1. Open **Admin → Organization → Integrations → Manage Messaging & Sharing → Slack** (**Configure**). 2. Under **Add App**, pick the same app and tick the features it should have now. 3. Click **Register App**. **Registered Apps** shows the new set of features. The ✕ beside an app under **Registered Apps** removes it from Slack. ### Turning must-read messages on or off 1. Open the Slack page (**Configure**). 2. On the **Must-read messages** card, switch **Send must-reads as direct messages**. Turning it off stops new messages. People still acknowledge from OneMango as before. If the card shows **Turn on Communications, Sites or SOP Hub first**, none of those apps is on for your organization yet. ### Disconnecting **Disconnect** (on the Slack page, or the Messaging page) stops everything above. Connecting again brings back the apps and settings you had. ## 5. Settings All on **Admin → Organization → Integrations → Manage Messaging & Sharing → Slack** (its **Configure** button). | Setting | Where | Default | What it changes | |---|---|---|---| | **Slash Commands** | **Add App** | On | The app's `/mango` commands run in Slack | | **Notifications** | **Add App** | On | The app's notifications are sent to Slack | | **Channel Posting** | **Add App** | Off | The app may post to a channel | | **Default Channel** | **Settings** card | None | Where an app's notifications go when it has no channel of its own | | **Allow Share to Slack channels** | **Settings** card | Off | People can send a ticket, account or post to a Slack channel with **Share** | | **Only offer channels the sender belongs to** | **Settings** card, under **Who can be sent a record** | Off | Channels the sender isn't in are shown but can't be picked | | **Let people ask Ask AI in Slack** | **Ask AI** card | Off | People can ask Ask AI with `/mango ask`, a direct message or an @mention | | **Send must-reads as direct messages** | **Must-read messages** card | Off | Each person owed a must-read gets it as a private Slack message | The **Add App** defaults are how the checkboxes start each time you register an app. ## 6. More help - *Microsoft Teams*: the same features in Teams, including must-read messages. - *AI Assistants*: Slackbot, Claude, ChatGPT and Microsoft 365 Copilot. - *Notifications*: what OneMango sends and to whom. - Ask AI — the assistant answers questions about Slack from these articles. **Keywords:** Slack, Slack integration, connect Slack, /mango, slash commands, Slack notifications, Slack channel posts, Slack approvals, raise a ticket from Slack, recognize from Slack, Slack app home, Share to Slack, Ask AI in Slack, must-read in Slack, Slack direct message, acknowledge in Slack, Acknowledge button, disconnect Slack --- # SOP Hub App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to create, assign, and track Standard Operating Procedures — step-by-step procedures employees complete and SOP Hub admins sign off. # SOP Hub ## 1. What it is SOP Hub lets you author step-by-step procedures, assign them to the right employees, and track who has completed each one. When steps change, everyone who already finished the procedure is automatically flagged to re-complete it. Completions can be set to need sign-off by a SOP Hub admin, and QR codes let frontline workers scan a label at a workstation to open the right procedure on their phone. - **Enablement:** SOP Hub requires a license. An admin enables it from Admin → Apps → All Apps; it is off by default. - **What it is not:** SOP Hub is not a training course builder. If you need quizzes, modules, or certification tracks, use Training Connect. The two apps integrate — you can require a training course before an employee is allowed to start a procedure. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps → SOP Hub** and enable the app for your business. 2. Go to **SOP Hub → Settings** to review the defaults. The most important one is **Default Re-completion Period** (365 days) — this becomes the re-completion interval for every new SOP unless you override it per SOP. Set **Require Supervisor Verification by Default** if your procedures need sign-off. 3. Go to **SOP Hub → Manage → New SOP**. Give it a title, choose a type (Safety, Operations, Maintenance, etc.), and add at least one step. Each step has its own title, instructions, and optional time estimate. You can also describe the procedure in plain language and let Ask AI draft the steps, or upload a PDF/Word document to import an existing procedure. 4. Set the audience. By default **Applies to all employees** is off. Toggle it on, or choose specific departments, locations, or groups under **Target Audience**. 5. Leave **Requires completion** on (the default) so the app tracks who has finished the procedure. 6. **Publish** the SOP. Publishing triggers two things: the app creates a completion record for every employee in the target audience, and each person receives an email and in-app notification that the SOP requires their completion. 7. Confirm it worked: go to **SOP Hub → Reports → Compliance Report**. You should see the SOP listed with a compliance percentage and the count of employees who still need to complete it. **What silently does nothing until you also do it:** a SOP in Draft status is invisible to employees. You can create and edit it freely, but no completions are scheduled and no notifications go out until you publish. Similarly, **Multi-Language Support** (on by default) must stay on in Settings for anyone to add translations to a SOP or for employees to read them. **Who can author and manage SOPs:** HR admins, business admins and above, and SOP Hub app-admins. These same roles see the Manage, Templates, Manuals, Reports, and Settings tabs. All other employees see only the Dashboard and **My SOPs** tabs (their pending and completed procedures). ## 3. How it fits together **SOP** — a single procedure with a title, a type, steps, and an audience. Each SOP has a **type** that categorizes it. The available types are Safety, Quality, Operations, Maintenance, Cleaning, Equipment, Customer Service, Emergency, Onboarding, Compliance, Food Safety, Health & Safety, Environmental, and Custom. You can also assign a **category** (Safety & Compliance, Quality Control, Daily Operations, Equipment Maintenance, Customer Service, Emergency Procedures, Training & Onboarding, Administrative, or Custom) and a **difficulty level** (Beginner, Intermediate, or Advanced). A SOP moves through a lifecycle: **Draft → Published → Archived** or **Retired**. Only published SOPs are visible to employees and can be completed. Archiving takes a published SOP out of circulation; it can be unarchived back to Draft. Retiring is a permanent withdrawal — the SOP leaves the published set but its completion records stay for audit history. A retired SOP can be reactivated as a Draft. A published or retired SOP cannot be deleted; archive it first. A SOP contains an ordered list of **steps**. Each step has a title, written instructions, an optional time estimate, and an optional flag that marks it as requiring verification — any flagged step means the whole completion needs sign-off after the employee submits it. Employees complete steps one by one; the SOP is marked complete when every step is done. If the SOP also requires an acknowledgement, the employee must tick a "read and understood" confirmation before final submission. **Audience** — determines which employees are assigned the SOP. You can toggle **Applies to all employees** or scope by department, location, or group. When a SOP is published with "Requires completion" on, the system creates a completion record for every employee in the audience and notifies them. **Example:** a "Daily Equipment Startup" SOP (type: Equipment, difficulty: Beginner, estimated duration: 10 minutes) has four steps — *1. Inspect safety guards*, *2. Check fluid levels*, *3. Power on and run self-test*, *4. Log startup in the shift report*. The admin scopes it to the Warehouse department and publishes. Every warehouse employee sees it on their dashboard under **My SOPs → Pending Completions** and ticks off each step in order. If the admin later edits step 3 to add a calibration check, every employee who already completed the SOP is flagged to re-complete it against the revised steps — their previous progress is cleared. **Completion** — tracks one employee's progress through one SOP. A completion moves through these states: **Pending** → **In Progress** (at least one step done) → **Completed** → optionally **Pending Verification** → **Completed** (verified). Two automatic re-completion triggers exist: - **Content change:** editing the steps of a published SOP that requires completion immediately flags every existing completion as **Re-completion Required** and clears step progress. Only employees whose completion is newly flagged by that edit receive a notification — a second typo fix does not re-notify people who were already flagged. - **Scheduled re-completion:** if the SOP has a re-completion period set (defaulting to the tenant-wide setting), completions expire after that many days. The daily reminder job picks these up. Automated reminders respect both a frequency throttle (the **Reminder Frequency** setting) and a cap of 5 reminders per completion. After 5 reminders, or roughly 90 days with no action, reminders stop. **Template** — a reusable starting point. Templates can be system-provided (available to every business) or business-specific. Cloning a template into a SOP copies its steps, type, category, and audience defaults; the new SOP starts in Draft. A central template library is available at **SOP Hub → Templates → Template Library**. Ask AI can also draft an SOP from a plain-language description or an uploaded PDF/Word document, producing a draft SOP for review. **Procedure Manual** — a collection of SOPs, custom text sections and chapter headers assembled into a branded, downloadable PDF. Manuals have their own publish lifecycle (Draft → Published → Archived) and can be shared via a public URL when sharing is enabled. You can assign a document theme, set a custom slug for the URL, and brand the manual with a logo, colors, and header/footer text. A manual's audience can be scoped to departments, locations, or roles, and employees see only the published manuals that apply to them. The table of contents is generated automatically from the section structure. **Translation** — an AI-generated or human-edited rendering of a SOP's title, description, summary, and steps in one of 15 supported languages. Translations are marked stale automatically when the source SOP's content changes, and a human reviewer can verify or unverify each translation. The translation includes a disclaimer noting whether it was produced by AI or a human, and that the English version prevails in case of discrepancy. The supported languages are: Spanish, French, German, Chinese (Simplified), Chinese (Traditional), Portuguese, Vietnamese, Korean, Japanese, Tagalog, Arabic, Hindi, Russian, Italian, and Polish. **How it connects to other apps:** - **Training Connect** — a SOP can require one or more training courses as prerequisites. The link types are **Required Before SOP** (the employee is blocked from starting the procedure until they pass the course), **Recommended Training** (shown but not enforced), and **Certification Credit** (completing the SOP grants credit toward a training enrollment). The prerequisite gate is enforced on the desktop, mobile, and QR code completion paths. - **Asset Pro** — a SOP can be linked to a specific asset, letting you find the procedures that apply to that piece of equipment. **Verification** — sign-off can be required at two levels. The SOP-level toggle (**Require Supervisor Verification**) requires verification of the entire completion. Individual steps can also be flagged as requiring verification. If either is set, the completion enters **Pending Verification** after the employee finishes, and the sign-off request goes to one person: a SOP Hub admin — the employee's manager or the procedure's author when they manage SOP Hub, otherwise an administrator. A manager who does not manage SOP Hub is not asked and cannot sign off. **Mobile** — SOP Hub has a dedicated mobile view. Phone-class browsers are automatically redirected from the desktop dashboard to the mobile dashboard. QR-code scans render in a mobile-optimized layout. The mobile view supports step-by-step completion. When offline mode is enabled, a procedure opened by scanning its QR code keeps working if the connection drops, and step completions are queued and sent once it returns; the separate mobile dashboard pages are not covered. **Completion method** — each completion records whether it was worked through from a scanned QR code or opened in SOP Hub directly. It is kept on the completion record for audit and appears in the completions list's export, in the "Recorded through" column. **Content governance** — SOP Hub participates in the platform's content-governance system. The nightly governance scan checks published SOPs for stale content based on the re-completion period and flags findings for review. This is automatic and does not require separate configuration. ## 4. Running it ### Reviewing compliance Go to **SOP Hub → Reports → Compliance Report**. Each published SOP that requires completion is listed with the target audience size, the number completed, and a compliance percentage. You can send reminders per SOP or use **Send All Reminders** to nudge every pending completion across all SOPs. The report is downloadable as a CSV. Reminders that have already been sent within the configured Reminder Frequency are skipped, and each completion stops receiving reminders after 5. The flash message after a send tells you how many were sent and how many were throttled. ### Verifying a completion When a SOP or any of its steps requires supervisor verification, the completion moves to **Pending Verification** after the employee finishes. The sign-off request goes to a SOP Hub admin — the employee's manager or the procedure's author when they manage SOP Hub, otherwise an administrator — by email and in-app notification, while **Ask Supervisors to Sign Off on Completions** is on. Go to **SOP Hub → Reports → All Completions**, filter to **Awaiting Verification**, and click **Verify**. A sign-off can't be undone. The employee is notified when it is signed off, while **Confirm Sign-Off Back to the Employee** is on. If the work was done wrong, click **Send back…** instead and say what to redo — a reason is required. The employee's steps are cleared, they are asked to complete the procedure again and told your reason (in-app, and by email when they have an address), and their SOP page shows who sent it back and why. The completion comes back for sign-off when they submit it again, while the procedure still asks for one. You can't send back your own completion, one already signed off, or one on an archived or draft procedure, which nobody could open to redo, or the completion of someone who is no longer a member. On a phone, the **Sign-offs waiting** page has the same two choices. ### Managing versions Every edit to a published SOP increments its version number. Go to the SOP detail page and click **History** to see every version with its change summary. **Compare** shows a side-by-side diff of the steps between any two versions, with counts of steps added, modified, and removed. ### Using QR codes Each SOP is assigned a unique 8-character QR code at creation. Go to the SOP detail page and click **QR Code** to view, download as SVG or PNG, or print it. **Print QR Labels** on the SOPs list generates a printable sheet of labels for all published SOPs (filtered by type or search). Employees scan the code with their phone camera and are taken directly to the procedure's mobile completion view. QR codes only resolve to published SOPs. A label printed for a draft or archived SOP will not work. ### Duplicating a SOP On the SOP detail page, click **Duplicate**. This creates a new Draft copy with "(Copy)" appended to the title. The duplicate gets its own QR code and public token. It does not inherit sample-data status. ### Building a procedure manual Go to **SOP Hub → Manuals** and click **Create Manual**. Give it a title, pick a document theme for branding, and save. The manual opens on its page, where the **Manual Builder** card puts it together: **Add SOP** adds a published SOP, and **Add Section** adds a custom text section or a chapter header. Drag a section's handle, or use its arrow buttons, to reorder, and expand a section to remove it. Each card on the Manuals list has a **Manual Builder** button that opens the card directly. Publish the manual; it becomes viewable by its target audience and downloadable as a branded PDF. If **Enable Public SOP & Manual URLs** is on in Settings, the published manual is also accessible at a public URL — either by its auto-generated token or by a custom slug you set on the manual. ### Importing an existing procedure On the **New SOP** page, upload a PDF or Word document containing an existing procedure. The app extracts the text and uses Ask AI to structure it into steps, landing you in the SOP editor with a draft ready for review. The document must contain at least 50 characters of extractable text. ### Viewing the activity log Go to **SOP Hub → Reports → Activity Log** for a chronological record of SOP creation, editing, publishing, completion, verification, and reminder events. The log is filterable by event type and date. ## 5. Settings All settings are at **SOP Hub → Settings**. The Settings page also shows quick stats (total SOPs, published SOPs, templates, manuals, and total completions) and a sample-data card for loading or removing demo content. | Setting | Default | What it changes | |---|---|---| | Enable SOP Hub AI Agent | On | Lets employees ask questions about SOPs through Ask AI. When off, the SOP Hub agent does not respond. | | Generate AI Summaries of Procedures | On | Writes a short summary of a procedure whenever its steps change (in production only). Summaries already written stay when it is turned off. | | Allow AI to Draft Procedures | On | Shows the AI drafting panel — describe a procedure, or upload a PDF or Word document — on the new procedure and new template pages. | | Default Re-completion Period (days) | 365 | The re-completion period a new SOP starts with; each SOP can change it, and existing SOPs keep their own. Also used as the content-governance review interval. | | Reminder Frequency (days) | 7 | Minimum interval between automated completion reminders for the same employee. The daily reminder job skips anyone reminded more recently than this. | | Require Supervisor Verification by Default | Off | When on, new SOPs start with verification turned on; existing SOPs keep their own setting, and each SOP can change it. | | Enable Multi-Language Support | On | Allows SOPs to be translated into other languages. When off, the Translations page and language picker are hidden, and employees stop seeing existing translations until it is turned back on. | | Enable Public SOP & Manual URLs | On | Allows SOP share links and published manuals to be opened at a public URL. When off, every public link is paused; the same links work again when it is turned back on. | | Enable QR Code Access | On | Allows employees to scan QR codes to open SOPs on mobile. When off, QR scan routes, the QR Code page on each SOP, and the bulk-print labels page are all disabled. | | Enable Offline Mode | Off | A procedure opened by scanning its QR code keeps working if the connection drops, and step completions are queued and sent once it returns. Completions started in a desktop browser on that same device queue as well. Opening a procedure needs a connection. | | Notify Employees on SOP Updates | On | Sends email and in-app notifications to the SOP's audience when the title, description, or steps of a published SOP are edited. | | Tell Employees When a New Procedure Needs Completing | On | Tells employees when a newly published SOP is assigned to them. With it off the SOP is still assigned and tracked. | | Send Reminders for Outstanding Completions | On | Turns the automated completion reminders (paced by Reminder Frequency) on or off. | | Tell Employees When a Completion Has Expired | On | Tells employees when their completion has passed its re-completion period and must be done again. | | Tell Employees When a Procedure They Completed Has Changed | On | Tells employees flagged for re-completion because the steps changed. With it off they are still flagged. | | Ask Supervisors to Sign Off on Completions | On | Sends the sign-off request for completions that need verification. With it off nobody is asked. | | Confirm Sign-Off Back to the Employee | On | Tells the employee once their completion is signed off. | ## 6. More help - **SOP Hub FAQ** — specific setup and operating questions, including limits, thresholds, and troubleshooting. - Ask AI — the assistant answers questions about SOP Hub from these articles. **Keywords:** sop, standard operating procedure, procedure, completion tracking, supervisor verification, qr code, procedure manual, re-completion, sop template, safety procedure, compliance, sop-hub, sop_hub --- # SOP Hub FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about SOP Hub — for the admin running it. # SOP Hub FAQ Answers to common setup and operating questions about SOP Hub. For what the app is and how to set it up from scratch, see the [SOP Hub Overview](/help/articles/sop_hub_app_overview). --- ## Setup ## What do I need to configure before employees can start completing SOPs? Enable SOP Hub from Admin → Apps → All Apps, then create and publish at least one SOP. A newly created SOP starts in **Draft** status and is invisible to employees until you publish it. When you publish an SOP that has **Requires Completion** turned on, the system automatically assigns it to its target audience and notifies them. No additional configuration is required for the basic workflow, but review the Settings tab to adjust defaults like the re-completion period, reminder frequency, and whether supervisor verification is required by default. ## Who can create and manage SOPs? Three roles can author SOPs, manage templates, view reports, and change settings: **HR Admin**, **Admin or above**, and anyone designated as an **SOP Hub App Admin** for your business. All other employees see only the Dashboard and their personal **My SOPs** worklist. --- ## Permissions and access ## An employee says they can't see an SOP I assigned — what's wrong? Check three things in order. First, the SOP must be **Published** — draft, archived, and retired SOPs are not visible to employees. Second, look at the audience setting: if **Applies to All Employees** is off, the SOP is scoped to the departments, locations, or groups you picked, and the employee must match every kind you used — in one of the picked departments AND at one of the picked locations AND in one of the picked groups. A picked department or location also includes the ones beneath it. Third, confirm SOP Hub itself is enabled for your business and the employee has access to the app in Admin → Apps → All Apps. --- ## Day-to-day ## What happens when I edit a published SOP? Two things happen automatically. First, the system saves a version snapshot — each edit to a published SOP increments the version number, and the full version history is available on the SOP's History tab. Second, if the SOP requires completion and you changed its steps, every employee who already completed it is flagged for **re-completion**, their step-by-step progress is reset, and they receive a notification. Employees who were partway through also have their progress reset so they work through the revised steps from the beginning. Only employees newly flagged by this edit are notified — earlier edits do not re-send. ## How do I assign an SOP to a specific group of employees? On the SOP's create or edit form, turn off **Applies to All Employees** and then choose one or more **departments**, **locations**, or **groups** under the target audience section. When the SOP is published with **Requires Completion** enabled, only employees in those audiences receive a completion assignment and notification. ## Can I delete an SOP I no longer need? You can only delete a **Draft** SOP. Published SOPs must be archived first — try to archive, then delete. Retired SOPs cannot be deleted at all because they preserve audit history; reactivate a retired SOP to draft first if you need to remove it. To take a published SOP out of circulation without deleting it, use **Archive** (reversible) or **Retire** (permanent withdrawal that preserves completion records). ## How does supervisor verification work? When **Require supervisor verification** is on — either at the SOP level or on individual steps — an employee's completion stays in **Pending Verification** status until a SOP Hub admin signs it off. The request goes to one person: the employee's manager or the procedure's author when they manage SOP Hub (HR Admin, Admin, or a SOP Hub App Admin whose reach includes the SOP), otherwise an administrator. A manager who does not manage SOP Hub is not asked and cannot sign off. Anyone who manages the SOP can verify completions from the Completions list — or, when the work was done wrong, **Send back** the completion with a reason: the employee is told why and completes it again, and it comes back for sign-off when they resubmit, while the procedure still asks for one. A sign-off itself can't be undone. The switch applies to completions made after you change it. Turning it on does not re-label completions already done as Pending Verification, and asks nobody about them. Turning it off — on the SOP and on every step — clears the sign-offs still waiting: they count as completed, and the supervisors' requests are withdrawn. ## What is the difference between an SOP and a procedure manual? An SOP is a single procedure with step-by-step instructions, completion tracking, and its own version history. A procedure manual bundles multiple SOPs together with chapter headers and custom sections into one browsable guide. Manuals have their own table of contents, can be published at a public URL or a custom slug, and can be exported to a branded PDF using a Document Theme. --- ## When something looks wrong ## "I completed this SOP — why does it show up again as pending?" Two things can trigger re-completion. First, if the SOP has a **re-completion period** set (the default is 365 days), a daily check reopens it automatically once that period elapses since your last completion. Second, if someone edits the steps of a published SOP, every prior completion is flagged for re-completion so everyone works through the updated procedure. In both cases you receive a notification and your earlier step progress is cleared. ## "I scanned the QR code but it says the procedure is no longer in use" The QR scan only opens **published** SOPs. If the SOP was unpublished, archived, or retired after the label was printed, the scan says "That procedure is no longer in use, so there is nothing to complete." Ask your admin whether the SOP should be published again. A code that matches no SOP — or a SOP you are not allowed to read — says "Invalid QR code. SOP not found." instead. If **Enable QR Code Access** is turned off in SOP Hub settings, every scan says "This procedure can't be opened by scanning right now." ## "I'm blocked from starting an SOP — it says I need training first" Your admin linked a training course as a prerequisite for this SOP. You must complete that course before you can record any steps or submit the SOP. Open the SOP to see which courses are outstanding. If Training Connect is not enabled for your business, prerequisite links are ignored and will not block you. ## "My progress got reset — I was halfway through" When the steps of a published SOP are edited, in-progress work is reset so you complete the revised procedure from the beginning. You will see a notice that your progress was reset. This is intentional — on safety or compliance SOPs, carrying over step ticks from a previous version would mean the system recorded you as having done steps you never saw. --- ## Licensing and limits ## What settings can I configure in SOP Hub? Open the **Settings** tab (visible to HR Admin, Admin, or SOP Hub App Admin). The available settings and their defaults are: - **Enable SOP Hub AI Agent** — on by default. Lets people ask Ask AI about your SOPs. - **Generate AI Summaries of Procedures** — on. Writes a short summary of a procedure whenever its steps change (in production only). Summaries already written stay when you turn it off. - **Allow AI to Draft Procedures** — on. Shows the AI drafting panel — describe a procedure, or upload a PDF or Word document — on the new procedure and new template pages. - **Default Re-completion Period (days)** — 365 days. Pre-sets the validity window on new SOPs; existing SOPs keep their own, and you can change it per SOP. Also used as the content-governance review interval (30–365 days). - **Require Supervisor Verification by Default** — off. When on, new SOPs start with verification turned on; existing SOPs keep their own setting. - **Enable Multi-Language Support** — on. Turning it off closes the Translations page and stops showing existing translations to employees. - **Enable Public SOP & Manual URLs** — on. Covers both SOP share links and public manual URLs. Turning it off pauses every public link; the same links work again when you turn it back on. - **Enable QR Code Access** — on. Turn it off to stop every QR scan from opening a SOP. - **Enable Offline Mode** — off. When on, a procedure opened by scanning its QR code keeps working if the connection drops, and step completions are queued and sent once it returns. - **Notify Employees on SOP Updates** — on. Tells the SOP's audience when the title, description, or steps of a published SOP are edited. - **Tell Employees When a New Procedure Needs Completing** — on. Tells employees when a newly published SOP is assigned to them. - **Send Reminders for Outstanding Completions** — on, with **Reminder Frequency (days)** — 7 days. How often the system re-sends reminders for pending completions. - **Tell Employees When a Completion Has Expired** — on. Tells employees when their completion has passed its re-completion period. - **Tell Employees When a Procedure They Completed Has Changed** — on. Tells employees who are flagged for re-completion because the steps changed. - **Ask Supervisors to Sign Off on Completions** — on. Sends the sign-off request for completions that need verification; with it off nobody is asked. - **Confirm Sign-Off Back to the Employee** — on. Tells the employee once their completion is signed off. ## How many reminders does the system send for overdue completions? The system sends up to **5 automated reminders** per completion, spaced by the **Completion Reminder Frequency** you set (default: every 7 days). After 5 reminders the system stops. Reminders also stop 90 days after the completion was assigned, whichever comes first. You can send reminders manually from the Compliance Report at any time. ## What languages can I translate SOPs into? When **Enable Multi-Language Support** is turned on, you can translate an SOP into any of **15 languages**: Spanish, French, German, Chinese (Simplified), Chinese (Traditional), Portuguese, Vietnamese, Korean, Japanese, Tagalog, Arabic, Hindi, Russian, Italian, and Polish. You can translate into several languages at once. Translations carry a structural completeness score, and a human can review and verify them. If you later edit the source SOP, its translations are flagged as stale. ## Does SOP Hub require a license? Yes. SOP Hub requires a license and is disabled by default. Turn it on from **Admin → Apps → All Apps** and click **Enable**. If your organization is not licensed for it yet, the message there says how to add it to your plan. --- ## More help - [SOP Hub Overview](/help/articles/sop_hub_app_overview) - Ask AI — the assistant answers SOP Hub questions from these articles. **Keywords:** faq, sop, standard operating procedure, completion tracking, re-certification, qr code, procedure manual, supervisor verification, offline mode, translation, sop-hub, sop_hub --- # Speak Up App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to stand up Speak Up — designating the adviser panel, the acknowledgement and feedback clocks, the public portal, the Article 18 register, and why there is no administrator screen that opens cases. # Speak Up ## 1. What it is Speak Up is a protected-disclosure channel: a way for someone to report serious wrongdoing — fraud, harassment, discrimination, safety or data-protection failures — and be sure the report reaches a named, impartial person rather than their own manager. It is built around the EU Whistleblowing Directive (2019/1937) and its national transpositions, so it runs two statutory clocks, keeps a register an auditor can read, and accepts reports from people who no longer work for you. Reports go to a **designated adviser panel** that you choose. Reporters can file anonymously, confidentially, or openly, and an anonymous reporter keeps a one-time reference code that opens a two-way thread — the panel asks follow-up questions, the reporter answers, and no identity is ever stored. - **Enablement:** Speak Up requires a licence and is off by default. A business administrator enables it from Admin → Apps → All Apps, then designates the adviser panel. It does nothing until both are done. - **What it is not:** **it is not an app administrators read by default.** There is no administrator screen that opens a case — business admins configure the channel (the panel, the clocks, retention) and that is all the role gives them. This is deliberate and it is the point of the app: the plausible subject of a protected disclosure is an administrator, so the usual admin-sees-everything rule is inverted here (Directive Art. 9(1)(c)). The honest caveat, set out in §3: designating the panel is itself an administrator setting, and the panel can grant a named person into a single case — so the control is accountability (every grant and every case-body read is recorded), not impossibility. It is also not the anonymous-feedback channel in Surveys, which is a pulse tool with no legal clock, no register and no retention rule. ## 2. Standing it up All of these must be done before a single report can be filed. Doing only some of them looks identical to doing all of them from inside the app. 1. **Enable the app.** Go to **Admin → Apps → All Apps → Speak Up** and enable it for your business. A licence is required. 2. **Create the group that will be your adviser panel.** Go to **Admin › Groups** and create a group containing the people who will read disclosures — typically two to five: a compliance lead, an HR director, sometimes an external counsel account. Add the people to it. 3. **Designate that group as the panel.** Go to **Apps → Speak Up → Settings** and choose it under **Adviser Panel**. Only a business administrator can set or change this — a delegated app administrator can open Settings but the panel control is read-only for them, because designating the panel is the same act as granting access to every disclosure. 4. **Publish the app to your employees.** Enabling an app and publishing it to non-administrators are separate switches. Until it is published, every non-admin employee is refused — the app will look completely configured to you and be invisible to them. 5. **Confirm it worked.** Open **Apps → Speak Up**. You should see the intake form. If you see a "not accepting reports" page instead, the panel has not resolved — see the pairing note below. **The pairing that silently blocks everything:** the app being enabled is not enough. With no panel designated, every intake surface — in-app, mobile and the public portal — returns a "not ready" page and refuses reports. You will also receive an email telling you which of these states you are in and what to do about it. Two of those states are easy to hit by accident: - **The group you chose has no members.** Add people to it; do not pick a different group. - **The group you chose is too large.** A group covering most of the company is refused, because reports are readable only by the panel and a panel that is most of the workforce is not a confidential channel. Groups that cannot be used are marked *too large to be a panel* in the Settings dropdown. Note that the broad system groups — All Employees, All Staff, Full-Time Employees — sort to the top of that list and are all too large. Choose a narrower group. **To accept reports from outside the company** — ex-employees, contractors, suppliers and applicants, which the Directive requires — there is a public reporting page on your own tenant domain. It is **on as soon as Speak Up is enabled and the panel resolves**, needs no account, and is always anonymous-only, whatever reporting modes you allow internally. Its address is on **Apps → Speak Up → Settings** under *Public reporting address* — give it to leavers, contractors and suppliers. To close it, switch the Speak Up portal off in the tenant's portal catalogue; people who already hold a reference code can still check on their reports. ## 3. How it fits together **The adviser panel** is the whole access model. Panel membership is what grants the ability to see the case list, open a disclosure, message a reporter, acknowledge, investigate and close. It is a group (Admin › Groups), so it is not tied to any platform role — a panel member is very often an ordinary employee, and an administrator is not a panel member unless you put them in the group. Changing the group changes who can read every disclosure in the tenant, which is why only business administrators can do it. **Per-case grants** are the exception that keeps the panel small. When one case needs a specialist — a fraud disclosure needing someone from Finance — a panel member grants that person access to *that one case*. A grant can carry an expiry date (it is optional), is revocable at any time, and every grant and revocation is recorded. A grantee sees the single case they were granted, never the case list. **Recusal** is how the panel handles a disclosure about one of its own members. An adviser recuses themselves from a case; they immediately lose access to it and stop being alerted about it. The last remaining adviser cannot recuse — a case must always have somewhere to go. A disclosure naming the entire panel has no destination today; if that is a real risk for your organisation, keep an alternative channel documented outside the product. **The two statutory clocks** run automatically from the moment a report is filed. Acknowledgement is due within 7 days (Art. 9(1)(b)); feedback to the reporter is due within 3 months (Art. 9(1)(f)) and starts when the case is acknowledged. Both are configurable *downwards* only — the defaults are the Directive's ceilings and the app will not accept a longer window. Breaches raise a panel alert and mark the case red on the panel's list and on the register. **The register and retention** are one mechanism. Closing a case starts its retention clock. When that expires, an overnight job purges the disclosure — the report body, the message thread and any evidence are destroyed — while keeping the minimal register row an auditor needs: reference, category, dates, status and closure reason. Deleting the row would destroy the Article 18 register; keeping the content would breach retention. The purge is irreversible and it records itself on the case's audit trail. While the content is still needed — for a tribunal or a regulator — a panel member can place a **legal hold** on the case from its case page: a held case is never purged, and lifting the hold lets the retention clock finish. **The Safety Hub boundary.** A psychosocial case can be referred into Safety Hub as an incident, so psychosocial and physical safety share one corrective-action register. Nothing identifying crosses that boundary — the incident carries no reporter, no reference code and no case body. Referral is a one-way, terminal step: a referred case is read-only afterwards. ## 4. Running it Everything below is done by a panel member, not by an administrator. ### Working a new disclosure 1. Open **Apps → Speak Up → Cases**. New and overdue cases are marked. 2. Open the case and read it. Every read of a case body is itself recorded on the audit trail — including yours. 3. **Acknowledge** it. This is the Art. 9(1)(b) obligation and it starts the feedback clock. 4. **Start investigation** when you begin work, then use the message thread to ask the reporter follow-up questions. An anonymous reporter can answer without ever identifying themselves. 5. **Close** the case with a closure reason and the feedback the reporter receives. Closing starts the retention clock. ### Bringing in a specialist 1. On the case, add a grant naming the person, with an expiry date if the access should end on its own. 2. They reach that case from their own Speak Up view — they never gain the case list. 3. Revoke the grant when their work is done. Both actions are on the record. ### Handling a retaliation claim A reporter whose treatment changes after speaking up tells the panel in the case thread; a panel member, or an investigator granted into the case, then flags retaliation on the open case. The panel is re-alerted on a recurring cadence until the case closes. Flagged cases are filterable on the register. ### Producing the register for an auditor 1. Open **Apps → Speak Up → Register**. By default it asks you to verify your identity again before it opens. 2. Filter by date window, status, category, retention state or retaliation flag. 3. Export to CSV. By default the export asks you to verify your identity again at that moment rather than trusting an old session, because the register is the one artefact that outlives the case content. Sample rows loaded for demo purposes are labelled as such, on screen and in the export. ## 5. Settings All at **Apps → Speak Up → Settings**. Every setting here has a real runtime consumer. | Setting | Default | What it changes | |---|---|---| | Adviser Panel | *(none)* | The group whose members can read and work every disclosure. Until it is set and resolvable, no surface accepts reports. Business administrators only. | | Allowed Reporting Modes | Anonymous, Confidential, Open | Which modes the in-app and mobile intake forms offer. The public portal is always anonymous-only regardless of this. Business administrators only. | | Acknowledgement Window (days) | 7 | When acknowledgement falls due, Art. 9(1)(b). 7 is the Directive ceiling; lower values are accepted, higher ones are not. | | Feedback Window (days) | 90 | When feedback to the reporter falls due, Art. 9(1)(f), counted from acknowledgement. 90 is the Directive ceiling. | | Retention After Closure (months) | 60 | How long a closed case keeps its content before the overnight purge destroys it. Sixty months is common practice, **not** a legal determination — confirm the right value for your jurisdictions with counsel. Business administrators only. | | Require Identity Verification to Open or Export the Register | On | Whether opening or exporting the register requires re-verifying identity at that moment. On by default; a whistleblowing register is sensitive by construction, so tenants opt out rather than in. Business administrators only. | | Open a Safety Hub Incident When a Case Is Referred | On | Whether referring a case also opens an anonymous Safety Hub incident. Off means referral only marks the case referred. | | Who is told when the Speak Up channel stops working | *(every administrator)* | The group told when the channel is turning reports away (no panel, an empty or unusable panel). It carries no case details. Business administrators only. | Two controls that are deliberately *not* here: the public portal switch, which lives in the tenant's portal catalogue so that one control governs every public portal; and any AI setting, because Speak Up registers no AI assistant. Case content is excluded from the assistant, from search indexing and from embeddings — an assistant would need a standing read path across every case, which is exactly the access this app exists to deny. Public intake is rate-limited per IP address, and reference-code lookups separately so. Sample data can be loaded and removed from this same Settings page. ## 6. More help - **Safety Hub Overview** — the incident and corrective-action register that referred cases feed into - **Surveys Overview** — anonymous pulse feedback, and where the boundary with Speak Up sits - Ask AI — the assistant answers configuration questions about Speak Up from these articles. It cannot read disclosures. **Keywords:** speak up, whistleblowing, whistleblower, protected disclosure, anonymous reporting, confidential reporting, adviser panel, reference code, EU Whistleblowing Directive, 2019/1937, acknowledgement window, feedback window, retention purge, disclosure register, article 18 register, retaliation, public reporting portal, why can't I see Speak Up cases, admin cannot read reports, speak-up, speak_up --- # Speak Up FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers about raising a concern through Speak Up, handling one as an adviser, and configuring the channel as an administrator. # Speak Up FAQ Answers to the questions people ask when raising a concern through Speak Up, handling one as an adviser, or setting the channel up. For what the app is and how the pieces fit together, see the [Speak Up Overview](/help/articles/speak_up_app_overview). --- ## Reporting a concern ## Is my report really anonymous? Yes, if you choose **Anonymous — no identity is stored, you keep a reference code**. No account, name or user reference is saved against the report, and the app refuses to store one. Every reply you send is stored with no author, so nobody can work out who wrote it later. ## I lost my reference code — can I get another one? No. The code is shown once, on the screen immediately after you submit, and it cannot be re-issued or looked up. Copy it somewhere safe at that moment. If you lose it on an anonymous report, submit a new report and say in it that an earlier one exists. ## Who actually reads what I write? Only the designated adviser panel your organisation has named, plus anyone a panel member explicitly grants access to that single report. No administrator screen opens a report. Every time someone opens a report body it is recorded, including who and when. ## If I choose Confidential, who sees my name? Only the adviser panel. A panel member can bring someone else into your report — an investigator or a specialist. That person sees the report but not your name; they are shown "Confidential reporter". Choosing **Open — you report under your own name** is the only option that shares your name more widely. ## How long before someone responds to my report? Your organisation must acknowledge it within its acknowledgement window, at most **7 days**. It must then give you feedback on the outcome within at most **3 months**. Both clocks start automatically and the panel is alerted when either is missed. Check progress any time with your reference code. ## I reported anonymously but nothing shows under My Reports — is it lost? It isn't lost. **My Reports** lists only reports you filed while signed in under Confidential or Named, because those are the only ones that carry your identity. An anonymous report deliberately has no link to your account, so use **Check a Report** and your reference code instead. ## Can I report if I've left the company or I'm a contractor? Yes, if your organisation has switched on its public reporting page. That page needs no account and takes anonymous reports only. You get a reference code the same way, and return to the same page to read replies. Ask the organisation for the address, or look for it on a notice at your site. --- ## Handling a case ## This report seems to be about me — what should I do? Step away from it using **Recuse** on the case page. Recusing is immediate and permanent: you lose the case, its thread and its evidence, and it disappears from your Cases list. If you are the last adviser who could still handle that case, the app refuses the recusal rather than leave the report with nobody. ## Can I bring a colleague into one case without adding them to the panel? Yes — use **Case Access** on the case page to grant that one person access. **Viewer** can read the case and its thread and take no action; **Investigator** can also post to the reporter's thread as the panel. You can set an expiry date, and you can revoke a grant at any time. ## Why can't I close this case? Because it has already been referred, or already closed. A case referred for handling elsewhere reaches its final state at the moment of referral, so closing it afterwards would record the outcome twice. The refusal message on the case page names which of the two applies. ## Why can't I attach evidence to this case? Because the case is no longer open, or its content has already been removed under the retention policy. Evidence can only be added while a case is open, and only by panel members and Investigator grantees. Photos you do attach have their location and camera details stripped automatically, so an anonymous reporter is never exposed by a file. ## Why did a case disappear from my Cases list? Three things remove it: you recused yourself, your per-case grant was revoked or expired, or you left the adviser panel group. Recusal is the only one that cannot be undone. If a case you expect is missing and none of those apply, ask an administrator whether the panel group has changed. --- ## Setting up the channel ## I turned Speak Up on, but reporters are told it isn't accepting reports — why? Because no usable adviser panel is designated, and the app deliberately refuses reports it has nobody to give them to. The usual causes: no **Panel group** chosen, the chosen group has no members in it, the group reaches too much of the company, or the group picks its members per location. Open Speak Up settings — the panel card names which one applies. ## Why can't I choose "All Employees" as the adviser panel? Because a panel that is most of the company is not a panel. It would give nearly every employee read access to every disclosure, including its subject. A group of 10 people or fewer is always accepted; above that, it must reach fewer than half the active people in your business. ## Can administrators read reports? Not through any administrator screen — case access comes only from panel membership or a per-case grant. The honest caveat: choosing the panel group is an administrator setting, so an administrator who designates a group containing themselves becomes an adviser. Choosing the group, and editing its member list, are recorded in the audit log. **Someone who joins a role- or attribute-based group because their own role changed is not**, so review its membership just as carefully. ## How do I open the public reporting page for contractors and ex-employees? It is on as soon as Speak Up is enabled and the adviser panel resolves: anyone with the address can file an anonymous report with no account. The address is on Speak Up settings under *Public reporting address*; to close it, switch the Speak Up portal off in your tenant's portal catalogue. Switching it back off closes new submissions but keeps the status page working for people who already hold a reference code. ## What are the limits on the clocks and the retention period? | Setting | Accepts | Default | |---|---|---| | Acknowledgement window (days) | 1–7 | 7 | | Feedback window (days) | 1–90 | 90 | | Retention after closure (months) | 1–240 | 60 | A value outside a range is pulled back into it rather than honoured. The feedback deadline is additionally capped at three calendar months from the acknowledgement, which can be a day earlier than 90 days. ## What happens to a report when the retention period ends? An automatic purge clears the report text, the whole message thread and any attached evidence, and switches off any remaining per-case access. What survives is the minimal register row an auditor needs: reference code, category, dates, status and outcome. The record of what happened and when also stays, with its details blanked. Nothing that was removed is recoverable afterwards. To keep a case's content past its retention date — for a tribunal or a regulator — a panel member places a **legal hold** on it from the case page; a held case is never purged until the hold is lifted. --- ## More help - [Speak Up Overview](/help/articles/speak_up_app_overview) - **Check a Report** in Speak Up — follow any report with its reference code - Speak Up settings — panel, reporting modes, clocks, retention and the register **Keywords:** faq, speak up, whistleblowing, anonymous report, reference code, adviser panel, protected disclosure, retaliation, retention, register, speak-up, speak_up --- # Succession Hub App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run Succession Hub — critical roles, succession plans, talent identification, leadership assessments, and development programs. # Succession Hub ## 1. What it is Succession Hub identifies the roles your organization cannot afford to leave vacant and tracks who is ready to fill them. It combines critical-role identification, candidate readiness levels, leadership assessments, and development programs into one view so HR and leadership teams can close pipeline gaps before they become vacancies. - **Enablement:** Succession Hub requires a license. An admin enables it from Admin → Apps → All Apps; it is off by default. - **What it is not:** Succession Hub does not replace Performance Management. Reviews, goals, and competency evaluations are authored in Performance Management; Succession Hub reads the latest completed review to place people on the 9-Box Matrix, and does not own that data. Readiness levels and readiness scores are not calculated from it — HR sets them on each candidacy. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Succession Hub**. The app is licensed and opt-in per tenant. 2. Go to **Succession Hub → Settings** and confirm the core modules are on. Five modules are enabled by default: **Leadership Pipeline**, **Succession Planning**, **Leadership Assessment**, **Executive Dashboard**, and **Development Tracking**. Two additional modules — **Advanced Analytics** and **Transition Planning** — are off and can be turned on here. Board reports need no module. Each module card on that page says what its switch turns on. 3. Create at least one **Critical Role** under the **Succession** tab. A critical role defines a position the organization must have succession coverage for. Set its urgency level and, optionally, assign the current incumbent and required competencies. 4. Add **Succession Candidates** to that role. Each candidate receives a readiness level — Ready Now, Ready in 1 Year, Ready in 2 Years, Ready in 3 Years, or Development Needed — set by HR, and a rank. A plan's minimum is 2 successors by default; change it on each plan. 5. Optionally, set up **Competency Frameworks** and **Assessment Templates** under **Settings → Templates** to standardize how candidates are evaluated. 6. Decide who maintains succession data. By default that is admins and Succession Hub's app administrators. To admit an HR coordinator without making them an app administrator, name them a **Contributor** on Succession Hub's **Admins & Contributors** page (Admin → Apps); to admit whole groups, use **Settings → Who can access the succession pipeline?** 7. Confirm it worked: managers and HR users should see the **Overview** dashboard with critical-role counts, candidate totals, and a readiness score. Employees see only their own **My Profile** page. 8. Optionally, configure **Notification Settings** under **Settings → Notifications**. Assessment-due reminders, coverage-gap alerts, and review notifications are on by default. Assign recipient groups to control who receives each notification type. **Silent-until-paired:** a critical role with no succession candidates produces a coverage-gap alert but contributes nothing to bench-strength metrics. The role and at least one candidate must exist together before the dashboard reflects meaningful data. **Mobile view:** employees on mobile devices are automatically redirected to the mobile Succession Hub. The mobile view shows their candidacies, assessments, development programs and activities, and high-potential status. Managers and admins stay on the desktop view. ## 3. How it fits together **Critical Roles vs. Succession Plans.** These are the two structures users most often confuse. A critical role identifies a position — its title, department, urgency, and current incumbent. A succession plan defines the planning wrapper — review cadence, timeline, minimum successors, and the list of candidates. When you click **View Succession Plan** on a critical role, the app links them automatically (creating the plan if one does not exist). You can also create a standalone succession plan for a role that is not yet flagged as critical. Example: VP of Engineering (Critical Role, urgency **High**, incumbent: Jane Doe) → linked Succession Plan (review cadence **Quarterly**, minimum successors **2**, timeline **1 Year**) → 3 candidates ranked 1–3 with readiness levels ranging from **Ready Now** to **Ready in 2 Years**. **Readiness levels** describe how soon a candidate could step into the target role. The five levels are **Ready Now**, **Ready in 1 Year**, **Ready in 2 Years**, **Ready in 3 Years**, and **Development Needed**. Readiness feeds the bench-strength dashboard and the succession-coverage analytics. A plan's bench strength is **Insufficient** until it has at least as many active candidates as its minimum-successors requirement (default 2, set on each plan); past that, it is graded by how many of them are Ready Now or Ready in 1 Year — **Adequate** for 1, **Strong** for 2, **Excellent** for 3 or more. A critical role's risk level uses its plan's minimum too. **High-Potential Employees** are tracked separately from succession candidates. A high-potential record captures an employee's potential level — **Top Talent**, **High Potential**, or **Emerging Talent** — along with a retention-risk score and flight-risk flag. The same employee can appear as both a high-potential and a succession candidate. These are complementary: high-potential identification is about the person's growth trajectory; candidacy is about their fit for a specific role. **Leadership Assessments** score an employee on competencies relevant to a role or leadership track. There are 11 assessment types, including 360° Feedback, Leadership Competency, Potential Assessment, and Succession Readiness. Each type has its own competency set. Competency scores are on a 0–100 scale; the overall score is the average across all competencies rated. Assessments are considered current for 6 months. **Development Programs** track leadership-development activities such as internal programs, external programs, executive coaching, mentorship, and job rotations. Participants are enrolled and tracked through completion; once they finish, they can rate the program from their own **My Profile** page. Programs appear on high-potential profiles so reviewers — including the person's manager — can see what development has already been invested. **Competency Frameworks** define the leadership competencies used across assessments and role requirements. The app ships with a default Standard Leadership Competencies framework (Strategic Thinking, Communication, Team Leadership, Decision Making, Change Management, Emotional Intelligence, Problem Solving, Coaching & Development). Admins can create additional frameworks — for example, a Technical Leadership framework — under **Settings → Templates**. **Three access tiers.** Succession Hub enforces three levels of access: - **Function tier** (admins, Succession Hub's app administrators, Contributors, and any groups named under **Settings → Who can access the succession pipeline?**): sees all succession data across the organization. Can create, edit, and delete plans, roles, candidates, assessments, and programs. - **Manager tier** (any manager who is not in the function tier): read-only access to the high-potential, assessment, and candidacy records of their own direct reports. Cannot see the Succession, Development, or Analytics tabs. No org-wide counts are shown. - **Employee tier** (everyone else): sees only **My Profile** — their own candidacies on active plans, completed assessments, high-potential status, development programs and activities, and any role transition they are taking over. **Integrations with other apps.** Succession Hub reads Performance Management live, with no sync to configure: on the **9-Box Matrix**, a person's performance placement comes from their latest completed review (or, where there is none, the most recent performance rating on their leadership assessments), and the matrix shows that review's competency gaps against the person's job-title requirements. **Settings → Integrations** shows whether Performance Management, OKR Hub, SkillSwap, and Recognition are enabled for your organization; it has no on/off switches. Only Performance Management feeds Succession Hub today — the page says the other three are not used yet. ## 4. Running it ### Reviewing the dashboard The **Overview** tab shows a summary dashboard: total critical roles, succession candidates, high-potential employees, active development programs, recent assessments, and a succession readiness score. It also lists recent activity (assessments completed, program enrollments) and upcoming succession reviews. Critical roles needing attention — those without a **Ready Now** candidate — are highlighted. ### Reviewing bench strength Go to **Analytics → Bench Strength**. The page shows an aggregate readiness summary across all candidates, uncovered roles (fewer than 2 ready candidates), readiness by department, and a bench-strength score. Use this before leadership reviews to identify where the pipeline is thin. ### Running a talent review Go to **Talent → Talent Reviews**. Search for employees and add up to 4 to a side-by-side comparison. Optionally select a target critical role to score candidates against its required competencies. The comparison view shows flight-risk status and retention-risk scores, which requires a step-up re-authentication because it is sensitive data. ### Conducting a leadership assessment Go to **Development → Leadership Assessments → New Assessment**. Select the employee, assessment type, and source (Internal, External, Self, Manager, or Peer). Rate each competency on a 0–100 scale. The overall score is calculated automatically as the average. Completed assessments link to the employee's high-potential record if one exists. ### Managing succession reviews Go to **Succession → Succession Reviews**. Create a review with a type — Quarterly, Annual, Board Review, Ad Hoc, or Emergency — a date, and a conductor. Reviews track findings, recommendations, and action items. Use them to document the outcome of leadership-team discussions about the pipeline. ### Managing transitions Enable the **Transition Planning** module in Settings. Go to **Succession → Transitions** to create a transition record for a critical role. A transition tracks the outgoing and incoming employees, type (Planned, Emergency, Promotion, or Lateral Move), milestones, knowledge-transfer plan, and communication plan. ### Using the 9-Box Matrix Go to **Analytics → 9-Box Matrix**. The matrix plots candidates on a performance-vs-potential grid; performance comes from each person's latest completed Performance Management review, or their leadership-assessment rating where there is none. Use it during talent calibration sessions to align on who is ready now, who needs development, and who is misplaced. You can filter by department or target role. ### Viewing succession coverage Go to **Analytics → Coverage**. The coverage view shows which critical roles have enough ready candidates and which do not. The succession readiness score is the percentage of active critical roles that have at least one **Ready Now** candidate. ### Enrolling employees in development programs Go to **Development → Programs** and open a program. Use **Enroll** to add participants. Track their status (Enrolled, Active, Completed) and record completion dates and ratings. The program's completion rate and effectiveness rating update automatically as participants finish. ### Exporting reports The analytics and talent-pipeline pages offer CSV and PDF exports. Reports include succession-planning metrics, risk analysis, high-potential distribution by department, and development-program effectiveness. ## 5. Settings Settings are at **Succession Hub → Settings**. Only an admin or one of Succession Hub's app administrators can open them. | Setting | Where | Default | What it changes | |---|---|---|---| | Enable Succession Agent | Settings | On | Turns the AI agent on or off for this app | | Leadership Pipeline | Settings (Modules) | On, required | The High Potentials list and the dashboard's Leadership Pipeline card | | Succession Planning | Settings (Modules) | On, required | Succession plans and their successor benches | | Leadership Assessment | Settings (Modules) | On | Leadership Assessments in the Development menu | | Executive Dashboard | Settings (Modules) | On | Enables the executive-level succession dashboard | | Development Tracking | Settings (Modules) | On | Development Programs and Activities, and the Development Activities card on employees' profiles | | Advanced Analytics | Settings (Modules) | Off | Enables pipeline-health analytics and the Pipeline Health page for the people **Who can see the Pipeline Health page?** allows | | Transition Planning | Settings (Modules) | Off | Succession Transitions, and the incoming employee's transition card on their profile | | Who can access the succession pipeline? | Settings | App Admins only | Admits specific groups to the function tier, beyond admins, app administrators, and Contributors | | Who can see the Pipeline Health page? | Settings | App Admins only | Who besides the function tier can open Pipeline Health (Everyone, or specific groups). Needs Advanced Analytics on | | Show succession rank on the employee's own profile | Settings | Off | Whether a successor sees their rank on a plan on their own profile | **Settings → Integrations** has no switches: it shows which related apps are enabled for your organization, and that only Performance Management feeds Succession Hub today. Admins can also export and import the full module configuration as JSON, or reset all modules to defaults, from the main Settings page. A reset turns Advanced Analytics and Transition Planning off and every other module on; access policies and notification groups are kept. ## 6. More help - **Succession Hub FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about Succession Hub from these articles. It can look up pipeline coverage, candidate readiness, and plan status. **Keywords:** succession planning, succession hub, critical roles, high potential employees, leadership pipeline, talent review, bench strength, readiness level, succession candidates, 9-box matrix, leadership assessment, development programs, talent pool, flight risk, succession transition, succession-hub, succession_hub --- # Succession Hub FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Succession Hub — for the admin running it. # Succession Hub FAQ Answers to common setup and operating questions about Succession Hub. For what the app is and how to set it up from scratch, see the [Succession Hub Overview](/help/articles/succession_hub_app_overview). --- ## Setup ## Do I need to enable anything before Succession Hub works? Yes. Succession Hub requires a license and is disabled by default. An admin enables it from Admin → Apps → All Apps. Once enabled, five core modules turn on automatically: **Leadership Pipeline**, **Succession Planning**, **Leadership Assessment**, **Executive Dashboard**, and **Development Tracking**. Two additional modules — **Advanced Analytics** and **Transition Planning** — stay off until you enable them individually in Settings. Board reports need no module: they are always available under **Analytics → Reports**. ## What is the minimum setup to get useful data on the dashboard? Create at least one critical role and add at least one succession candidate to it. A critical role with no candidates produces a coverage-gap alert but contributes nothing to the bench-strength or readiness metrics. The role and a candidate must both exist before the dashboard reflects meaningful data. --- ## Permissions and access ## Who can see and manage succession data? Succession Hub enforces three access tiers: 1. **Function tier** — admins, Succession Hub's app administrators, and anyone named a **Contributor** on Succession Hub's **Admins & Contributors** page (Admin → Apps). Sees all succession data across the organization and can create, edit, and delete plans, roles, candidates, assessments, and programs. 2. **Manager tier** — any manager who is not in the function tier. Read-only access to high-potential, assessment, and candidacy records of their own direct reports only. No Succession, Development, or Analytics tabs are shown. 3. **Employee tier** — everyone else. Sees only their own **My Profile** page. An admin can also admit specific groups to the function tier under **Settings → Who can access the succession pipeline?** The default admits no one beyond admins, app administrators, and Contributors. ## Who can change Settings? Only an admin or one of Succession Hub's app administrators can open the Settings page. Contributors, and people admitted through **Who can access the succession pipeline?**, maintain succession data but cannot change Settings. --- ## Day-to-day ## What is bench strength and how is it scored? Bench strength measures how well a critical role is covered by succession candidates. The app classifies each plan as: - **Weak** — no active candidates at all - **Insufficient** — fewer active candidates than the plan's minimum, or enough candidates but none of them Ready Now or Ready in 1 Year - **Adequate** — 1 candidate who is Ready Now or Ready in 1 Year - **Strong** — 2 candidates who are Ready Now or Ready in 1 Year - **Excellent** — 3 or more candidates who are Ready Now or Ready in 1 Year The minimum number of successors defaults to **2** and is set on each plan (**Minimum Successors Required** on the plan's form). A critical role's risk level uses its plan's minimum too. ## What readiness levels can a candidate have? There are five: **Ready Now**, **Ready in 1 Year**, **Ready in 2 Years**, **Ready in 3 Years**, and **Development Needed**. Readiness feeds the bench-strength dashboard, coverage analytics, and the talent pipeline flow (Ready Now / Ready Soon / Developing, where Ready Soon is the Ready in 1 Year band). HR sets each candidate's readiness level, and optionally a readiness score, on the candidacy — they are not calculated from performance data. Employees see their candidacies on active plans only — a candidacy on a draft plan stays hidden from them until the plan is made active. ## How many leadership assessment types are there? There are 11 types: 360° Feedback, Leadership Competency Assessment, Potential Assessment, Performance Review, Succession Readiness, Leadership Potential, Role Readiness, Competency Assessment, Self Assessment, Manager Assessment, and External Assessment. Each type has its own competency set. Competency scores are on a 0–100 scale, and the overall score is the average across all competencies rated. An assessment's **Potential Score** and **Readiness Score** are recorded separately by the assessor. ## How does Succession Hub use Performance Management data? On the **9-Box Matrix**, each person's place on the performance axis comes from their latest completed Performance Management review; where they have none, it comes from the most recent performance rating recorded on their leadership assessments, and with neither they are placed in the middle performance band. The matrix also shows that review's competency gaps against the person's job-title requirements, when the job title has any. Succession Hub reads this live — it does not copy or sync it. Performance data does not set readiness levels or readiness scores; HR sets those on each candidacy. **Settings → Integrations** shows which related apps are enabled for your organization; it has no on/off switches. ## What types of talent pools can I create? There are three types: **Diversity**, **Skills-based**, and **Saved Group**. Skills-based pools can auto-populate from employee skill proficiency, so the pool stays current as skills data changes. Members can be added manually, via auto-population, through import, or from a talent review session. ## What succession review types exist? Five: **Quarterly**, **Annual**, **Board Review**, **Ad Hoc**, and **Emergency**. Each review tracks findings, recommendations, and action items. The next review date is calculated automatically — 3 months for quarterly, 1 year for annual, 3 months for board reviews, and none for emergency reviews. ## What transition types does Succession Hub support? If the **Transition Planning** module is enabled, you can create transitions of four types: **Planned**, **Emergency**, **Promotion**, and **Lateral Move**. Each transition tracks the outgoing and incoming employees, milestone timeline, knowledge-transfer plan, communication plan, and risk mitigations. A transition's health status is computed from milestone completion versus elapsed time: **On Track**, **Minor Issues**, **At Risk**, or **Critical Issues**. --- ## When something looks wrong ## Why can't I see the Succession, Development, or Analytics tabs? Those tabs are visible only to the function tier — admins, Succession Hub's app administrators, Contributors, and any groups named under **Settings → Who can access the succession pipeline?** Managers see only the **Talent** tab (scoped to their own reports). Regular employees see **My Profile**, and the **Pipeline Health** page only when the **Advanced Analytics** module is on *and* they are allowed by **Settings → Who can see the Pipeline Health page?** (default: app administrators only). Ask your admin to check those two access settings. ## I set up a critical role but the dashboard still shows no bench-strength data — why? A critical role alone does not contribute to bench-strength metrics. You must also add at least one succession candidate to the role's plan. Until both exist, the dashboard treats the pipeline as empty for that role. ## My employees say they cannot see their succession profile — what is wrong? Employees see their own profile at **Succession Hub → My Profile**. If it is not showing, check that the app is enabled for your organization and that the employee has access. The app's audience settings may exclude certain groups. ## Why did a notification not go out for a coverage gap? Coverage-gap alerts require two conditions: the **Coverage Gap Alerts** toggle must be on in **Settings → Notifications**, and a recipient group must be assigned to the coverage-gap alert category. If no recipient group is configured, the alert is skipped silently. Check both the toggle and the recipient assignment. ## Readiness change emails are not being sent — what should I check? Readiness-change notifications are off by default (unlike most other notification types). Go to **Settings → Notifications** and confirm the **Readiness Alerts** toggle is on, and that the direction you expect is ticked under **Alert On** (moves toward Ready Now are on by default; moves toward Development Needed are off). They go to the candidate's assessor and nominator, plus the recipient group if you set one — never to the candidate. --- ## Licensing and limits ## Does Succession Hub require a license? Yes. It is licensed and opt-in per tenant. An admin enables it from Admin → Apps → All Apps; it is disabled by default until then. ## Are there limits I should know about? | Item | Limit | |---|---| | Minimum successors per plan | Default **2**, editable on each plan | | Assessment template competencies | Up to **20** per template | | Assessment template questions | Up to **100** per template | | Assessment template duration | Up to **180 minutes** | | Succession plan templates — minimum candidates | **1–10** | | Readiness score range | **0–100** | | Retention-risk score range | **0–100** | | Candidate fit score range | **0–100** | | Candidate rank | Must be greater than **0** | | Development plan target date | Cannot be more than **5 years** in the future | | Performance Improvement Plan extensions | Maximum **2** extensions | | Assessment currency | Considered current for **6 months** | | Analytics data retention | No automatic purge — data is retained indefinitely | | Report export formats | PDF and CSV | --- ## More help - [Succession Hub Overview](/help/articles/succession_hub_app_overview) - Ask AI — the assistant answers Succession Hub questions from these articles. **Keywords:** faq, succession planning, critical roles, bench strength, readiness level, high potential, leadership assessment, 9-box matrix, talent pool, flight risk, transition planning, succession candidate, development program, succession-hub, succession_hub --- # Supplier Hub FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Supplier Hub — for the admin running it. # Supplier Hub FAQ Answers to common setup and operating questions about Supplier Hub. For what the app is and how to set it up from scratch, see the [Supplier Hub Overview](/help/articles/source_app_overview). --- ## Setup ## Do I need the Procurement or Contracts apps for Supplier Hub to work? No. Supplier Hub runs independently. The Procurement and Contracts integrations are optional add-ons: if either app is enabled, an awarded RFQ can be converted into a Procurement requisition or a draft Contract. With neither app enabled, the sourcing workflow still completes end to end — you issue, evaluate, and award as normal. ## Who can create and issue RFQs once I turn the app on? Managers and above, plus anyone you have made a Supplier Hub app admin. The same gate applies to issuing, editing after issuance, awarding, cancelling, and managing vendor questions. All authenticated users in your business can view the dashboard, the RFQ list, and the vendor directory, but write actions require the Manager role or higher (or the app-admin grant). ## What does the Settings page control, and who can reach it? Settings is visible only to admins and app admins. It contains workflow toggles (amendment controls, the finance-threshold block, evaluation rules), numbering prefixes, notification switches, and threshold values. Every toggle on that page has a runtime consumer — the app reads the setting before the action runs. If a toggle is off, the gate it controls is simply not enforced. --- ## Permissions and access ## Why can't a team member create an RFQ? RFQ creation, issuance, and awarding require the Manager role or above. If a team member needs to participate, assign them as an evaluator on an evaluation stage — evaluators can be any manager-or-above user in the business. Members below Manager can still view RFQs and vendor records. ## Who can see competing vendors' bid pricing? Confidential bid pricing is restricted to managers and app admins. When **Blind Evaluation (Scoring Screens)** is on in Settings, the scoring and comparison screens show "Vendor #42"-style labels instead of vendor names until the RFQ is awarded, so scores are given against the bid rather than the bidder. --- ## Day-to-day ## How do I edit an RFQ after it has been issued? Turn on **Allow Editing Issued RFQs** in Settings. With that enabled, a manager can edit an issued RFQ. If **Notify Vendors on Amendment** is also on, invited vendors are notified of the change. Awarded and cancelled RFQs cannot be edited regardless of this setting. ## What happens when I award an RFQ? The winning quote is marked accepted, the other bids are marked not selected, the RFQ moves to Awarded, and the winning vendor is recorded. If **Email All Bidders the Award Outcome** is on, the winner gets a congratulations email and every other bidder gets a regret notice; with it off, no vendor is emailed the outcome. Two optional downstream actions can also fire: if **Auto-Create Requisition on Award** is on, the Procurement app is enabled, and your role can create requisitions in Procurement, a requisition is created automatically; if **Create Draft Contract on Award** is on and the Contracts app is enabled, a draft contract is created and linked to the RFQ. RFIs are information-only — awarding an RFI selects a response but never creates a requisition or contract. ## Can I delete an RFQ? Only if the RFQ has not been awarded and no vendor has submitted a quote (excluding drafts and withdrawn quotes). Once real vendor quotes exist, deletion is blocked and the RFQ can only be cancelled. ## What is the difference between an RFQ, an RFP, and an RFI? All three are created in the same form by choosing a type. RFQs and RFPs support line items with pricing, side-by-side quote comparison, and conversion to a Procurement requisition or Contract on award. An RFI is information-only: the line-items section is hidden, no pricing is collected, and awarding selects a response without creating any downstream record. ## How does the evaluation pipeline work? Each RFQ can have multiple evaluation stages — for example Technical Review, Commercial Review, and Final Selection. The first stage opens automatically; the next opens when the current one is complete (all assignments finished, or a manager marks it complete early). Evaluators are assigned per stage and score each submitted quote against weighted criteria. The default criteria are Price (30%), Quality (25%), Delivery Time (20%), Vendor Experience (15%), and Support & Service (10%), but the RFQ author can set custom criteria and weights. ## Can I save draft scores and come back later? Yes. The evaluation form offers a **Save Draft** option that persists scores without completing the assignment. The evaluator can return and finish later. Only a final submission advances the stage. --- ## When something looks wrong ## Why can evaluators still see vendor names after I turned on blind evaluation? Check where they are looking. **Blind Evaluation (Scoring Screens)** replaces vendor names with labels such as "Vendor #42" on the scoring and comparison screens, the RFQ's quote list and activity trail, the dashboard's recent quotes, and quote notifications. Names stay visible on a single quote's detail page and in the vendor directory, and every screen shows names again once the RFQ is awarded. The setting is read each time a page loads, so turning it on takes effect immediately, including for evaluations already in progress. ## Why does the vendor scorecard page say "Vendor scorecards are disabled"? The **Vendor Scorecards** setting is off. Turn it on in Settings. This setting gates all scorecard surfaces across the app — the Vendors tab still lists vendors and their qualification status, but no scorecard data appears until the toggle is on. ## Why can't my RFQ be issued over the finance threshold? **Block Issue Above the Finance Threshold** is on in Settings, and the RFQ's estimated value (the sum of its line items) exceeds the **Finance Approval Block Threshold (USD)**. The default threshold is $10,000. Nothing is sent to a finance team for approval, and no role can issue past the block: the RFQ becomes issuable once its estimated value drops to the threshold or below, or once an admin raises the threshold (or turns the block off) in Settings. ## Why can't I find the "Create contract" button on my awarded RFQ? Three conditions must all be true: the RFQ must be awarded, **Create Draft Contract on Award** must be on in Settings, and the Contracts app must be enabled for your business. If all three are met and a contract was already created (either automatically on award or manually), the button changes to a link showing the linked contract. RFIs never show this button — they are information-only and cannot be converted into a contract. --- ## Vendor management ## What do the vendor qualification statuses mean? Qualification has five statuses: Pending, Approved, Rejected, Probation, and Blocked. Only Approved vendors are counted in the "qualified vendors" metric on the dashboard. Risk is scored on three dimensions — Financial, Operational, and Compliance — each rated Low, Medium, or High. The overall risk score is 0–100, where below 30 is Low risk, 30–69 is Medium, and 70 or above is High. ## How do vendor performance scorecards work? Each vendor is scored across five dimensions: Quality, Delivery, Price, Service, and Responsiveness, each on a 0–100 scale. Scores come from your team: after an RFQ is awarded, a manager rates the winning vendor from the RFQ page on the criteria chosen under **Vendor Rating Criteria** in Settings (1–5 stars each, stored as 20–100). The overall score is the average of the rated dimensions, plus any rated criterion with no dimension of its own, such as compliance. Performance status is derived automatically: 90–100 is Excellent, 75–89 is Good, 60–74 is Fair, 40–59 is Poor, and below 40 is Unacceptable. Scorecards require the **Vendor Scorecards** setting to be on, and rating requires **Vendor Rating**. --- ## Licensing and limits ## Does Supplier Hub require a licence? Yes. An admin must enable and license Supplier Hub from Admin → Apps → All Apps before it is available. The app is disabled by default. ## Are there limits I should know about? - **RFQ number prefix:** configurable, up to 10 characters. Default is "RFQ-". - **Quote number prefix:** configurable, up to 10 characters. Default is "QTE-". - **Minimum evaluators per stage:** configurable from 1 to 20. Default is 2. - **Minimum Quotes for Comparison:** configurable from 1 to 20. Default is 3. It only sets when the "Quotes Ready for Comparison" alert fires; an RFQ can be compared and awarded with fewer quotes. - **Default Quote Window:** 1 to 90 days. Default is 14 days, counted from the day you create the RFQ — it prefills the submission deadline, which you can change on each RFQ. - **Finance Approval Block Threshold:** default $10,000. - **Insurance expiring-soon window:** 30 days. - **Scorecard dimension range:** 0–100 per dimension. - **Overall risk score range:** 0–100. - **Analytics export formats:** PDF, CSV, and Excel (XLSX), from the export menu on the analytics page. - **Analytics default period:** last 6 months. Other options: 30 days, 90 days, and 1 year. --- ## More help - [Supplier Hub Overview](/help/articles/source_app_overview) - Ask AI — the assistant answers Supplier Hub questions from these articles. **Keywords:** faq, rfq, rfp, rfi, vendor, quote, evaluation, scorecard, procurement, contract handoff, blind evaluation, finance threshold, supplier hub, source, supplier-hub --- # Supplier Hub Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run Supplier Hub — issue RFQs, RFPs, and RFIs to vendors, score quotes, qualify suppliers, and hand awards off to Procurement or Contracts. # Supplier Hub ## 1. What it is Supplier Hub is a buyer-side sourcing workspace. You issue solicitations (RFQs, RFPs, and RFIs) to vendors, capture and score their quotes, and award a winner — then hand the result off to Procurement or Contracts without re-keying vendor or line-item data. - **Enablement:** Supplier Hub requires a license. An admin enables it per tenant from Admin → Apps → All Apps. - **Two ways a quote arrives:** an invited vendor can sign in to the **Vendor Portal** with an emailed one-time code and submit their own pricing, questionnaire answers, and documents — or an internal user can enter the quote on the vendor's behalf. Either way it becomes the same quote record you evaluate, so the two paths can be mixed within one RFQ. - **What it is not:** vendors cannot raise questions from the portal. They can view a solicitation and respond to it, but questions are still captured internally on their behalf from the RFQ's Q&A tab. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Supplier Hub**. The app appears in the sidebar for all users. 2. Go to **Supplier Hub → Vendors** and add at least one vendor. Each vendor needs a name and, for email notifications, a contact email. Vendors are shared with Procurement, Contracts, and Asset Pro — if any of those apps already have vendors, they appear here automatically. 3. Go to **Supplier Hub → Settings** and review the workflow toggles. The key decisions: - Whether to require single-vendor justification or award justification, and whether to block issuing RFQs above a finance threshold. - Whether awarding an RFQ automatically creates a Procurement requisition or a draft contract (each requires the corresponding app to be enabled). - Whether to keep vendor scorecards and vendor rating on (both ship on). 4. Optionally, go to **Supplier Hub → RFQ Templates** and create one or more reusable templates so future solicitations start with pre-filled line items and questions. 5. To confirm it worked: go to **Supplier Hub → RFQs → New RFQ**, verify you can select vendors, add line items, and save a draft. Access rules: - All users can view the dashboard, browse RFQs and vendors, and see their own RFQs. - **Manager or above** (or a Supplier Hub app admin) can create, issue, and award RFQs; enter and submit quotes; manage evaluation stages; and manage vendor records. - **Admin or above** (or app admin) can access Settings and load/remove sample data. ## 3. How it fits together ### Solicitation types Every solicitation is one of three types, chosen when you create it: - **RFQ** (Request for Quotation) — you need priced line items. Vendors quote quantities, unit prices, and totals. - **RFP** (Request for Proposal) — similar to an RFQ but typically used for services or complex purchases where the evaluation weighs more than price alone. - **RFI** (Request for Information) — information only. RFIs carry no line items and no pricing. "Awarding" an RFI selects the best response but never creates a requisition or contract. Example: you issue RFQ-00001 to three office-furniture vendors with five line items (desks, chairs, monitors, etc.), a submission deadline of two weeks out, and a question deadline of one week. Each vendor's quote prices those five items. After the deadline you compare quotes side by side, run an evaluation, and award the winner. ### Lifecycle A solicitation moves through these states: **Draft → Issued → Accepting Questions → Quotes Due → Under Evaluation → Awarded** (or **Cancelled** at any point before award). The transitions are mostly manual — you issue a draft, then move to evaluation — except that auto-close can reject new quotes once the submission deadline passes. ### Vendors, qualifications, and scorecards Vendor records are shared across Supplier Hub, Procurement, Contracts, and Asset Pro. Within Supplier Hub, each vendor can have: - A **qualification** record tracking approval status (Pending, Approved, Rejected, Probation, or Blocked), risk scores across three dimensions (financial, operational, compliance) rolled into a 0–100 overall score, insurance and license expiry dates, and diverse-supplier certifications (MBE, WBE, DVBE). - A **scorecard** tracking performance across quality, delivery, price, service, and responsiveness (each 0–100). The system calculates an overall score and derives a performance status: Excellent (90–100), Good (75–89), Fair (60–74), Poor (40–59), or Unacceptable (below 40). Scorecards appear only when the **Vendor Scorecards** setting is on. ### Evaluation pipeline Each solicitation can define multiple evaluation stages — for example, Technical Review, Commercial Review, and Final Selection. Within each stage you assign evaluators (managers or above), and each evaluator scores every submitted quote against weighted criteria. The default criteria are Price (30%), Quality (25%), Delivery Time (20%), Vendor Experience (15%), and Support & Service (10%), but you can change the weights or the criteria per solicitation. Blind evaluation shows "Vendor #42"-style labels instead of vendor names on the scoring and comparison screens until the RFQ is awarded. You can also require a minimum number of evaluators per stage and require written comments before a score is submitted. ### Cross-app handoffs When you award an RFQ or RFP: - If **Auto-Create Requisition on Award** is on, the Procurement app is enabled, and the person awarding can create requisitions in Procurement, the winning quote converts into a Procurement requisition. - If **Create Draft Contract on Award** is on and the Contracts app is enabled, a draft contract is created and linked to both the RFQ and the vendor. - RFIs are never converted. ## 4. Running it ### Creating and issuing a solicitation 1. Go to **Supplier Hub → RFQs → New RFQ**. 2. Choose the type (RFQ, RFP, or RFI), give it a title, select invited vendors, add line items (for RFQ/RFP), and optionally add vendor questions. 3. Set a submission deadline and, if applicable, a question deadline. 4. Save as draft. Review it, then click **Issue** to send it to the invited vendors. If **Email Vendors on RFQ Issue** is on, each invited vendor receives an email notification with a link. ### Entering and comparing quotes 1. On the issued RFQ, go to the Quotes tab and click **New Quote**. 2. Select the vendor, enter their per-item pricing (unit price, quantity, lead time), answer any RFQ questions, and save. 3. Repeat for each vendor's response. Once quotes are in, use **Compare** to view them side by side. ### Running an evaluation 1. On the RFQ, go to the Evaluation tab and add stages (or click **Add Default Stages** to start with Technical Review, Commercial Review, and Final Selection). 2. Assign evaluators to each stage. Each evaluator receives an assignment for every submitted quote. 3. Evaluators open their assignment, score each criterion, add comments (required if **Require Evaluation Comments** is on), and submit. 4. When a stage's evaluations are complete, a manager can mark it complete to move to the next stage. ### Awarding 1. On a solicitation that has received and evaluated quotes, click **Award** on the winning quote. 2. If **Require Award Justification** is on, provide a written reason. 3. If **Email All Bidders the Award Outcome** is on, the winner is emailed and every other bidder gets a regret notice. Downstream handoffs to Procurement and Contracts fire automatically based on your settings. ### Managing vendor Q&A Vendor questions appear under the Q&A tab on each RFQ. You can answer a question privately (visible only to the asking vendor) or broadcast the answer to all invited vendors. Internal-only comments let your team discuss a question without the answer being visible externally. ## 5. Settings All settings are at **Supplier Hub → Settings**. The workflow settings are stored in the app's configuration; defaults apply until you change them. Supplier Hub ships opinionated: most governance controls are **on** out of the box, so a new tenant gets justification prompts, evaluation comments, scorecards and score-ranked comparison without configuring anything. Turn off what your process doesn't need. Labels below are the ones on the Settings page. | Setting | Section | Default | What it changes | |---|---|---|---| | Enable AI Agent | Supplier Hub Agent | On | Lets users query vendor and RFQ data through Ask AI | | Require Single-Vendor Justification | RFQ Workflow & Approvals | **On** | Issuing to only one vendor requires a written reason | | Block Issue Above the Finance Threshold | RFQ Workflow & Approvals | Off | An RFQ estimated above the threshold cannot be issued. Nothing is routed to finance for approval; the block clears only when the value drops or an admin raises the threshold | | Finance Approval Block Threshold (USD) | Defaults, Thresholds & Numbering | 10,000 | The estimated value above which the block applies | | Only Invite Approved Vendors | RFQ Workflow & Approvals | Off | Restricts the RFQ vendor picker to suppliers with an approved qualification | | Allow Editing Issued RFQs | RFQ Workflow & Approvals | Off | Permits amendments after a solicitation is issued | | Notify Vendors on Amendment | RFQ Workflow & Approvals | **On** | Records and notifies vendors when an issued solicitation is amended | | Notify Vendors on Cancellation | RFQ Workflow & Approvals | **On** | Emails invited suppliers when an RFQ they were invited to is cancelled | | Require Award Justification | RFQ Workflow & Approvals | **On** | Awarding requires a written reason | | Auto-Create Requisition on Award | RFQ Workflow & Approvals | Off | Creates a Procurement requisition from the winning quote (requires Procurement app) | | Create Draft Contract on Award | RFQ Workflow & Approvals | **On** | Creates a draft contract in Contracts from the winning quote (requires Contracts app; RFIs never convert) | | Allow Late Quotes | Quotes | Off | Accepts quotes after the submission deadline | | Auto-Close After Deadline | Quotes | **On** | Rejects new quotes after the deadline (overridden by Allow Late Quotes) | | Rank Quotes by Evaluation Score | Quotes | **On** | Orders the comparison table by the evaluation scores already recorded, best first. It calculates nothing — scores come from evaluators | | Require Evaluation Comments | Evaluation & Vendors | **On** | Evaluators must provide overall comments when submitting scores | | Blind Evaluation (Scoring Screens) | Evaluation & Vendors | Off | Shows "Vendor #id" instead of names on the scoring and comparison screens, the dashboard's recent quotes, the RFQ activity trail and quote notifications, until the RFQ is awarded | | Collaborative Evaluation | Evaluation & Vendors | **On** | Lets several team members score the same quotes and shows the evaluation team panel | | Vendor Rating | Evaluation & Vendors | **On** | Allows rating vendors after award | | Vendor Scorecards | Evaluation & Vendors | **On** | Shows vendor performance scorecards across the app | | Minimum Evaluators per Stage | Defaults, Thresholds & Numbering | **2** | Evaluation stages must have at least this many evaluators | | Minimum Quotes for Comparison | Defaults, Thresholds & Numbering | 3 | Submitted quotes needed before the "Quotes Ready for Comparison" alert fires; it does not stop you comparing or awarding with fewer | | Default Quote Window (Days) | Defaults, Thresholds & Numbering | 14 | Prefills a new RFQ's submission deadline, counted from today | | Default Question Window (Days) | Defaults, Thresholds & Numbering | 7 | Prefills a new RFQ's question deadline, counted from today | | Email Vendors on RFQ Issue | Quotes | On | Emails each invited vendor a link the moment the solicitation is issued | | Email All Bidders the Award Outcome | Quotes | On | One switch for both emails: the winner is congratulated and every losing bidder gets a regret notice. Off, no vendor is told the outcome | | Notify on Quote Submission | Quotes | On | Emails the RFQ creator the moment a quote arrives | | RFQ Number Prefix | Defaults, Thresholds & Numbering | RFQ- | Prefix for auto-generated solicitation numbers | | Quote Number Prefix | Defaults, Thresholds & Numbering | QTE- | Prefix for auto-generated quote numbers | Notification settings (RFQ lifecycle, vendor interactions, evaluation events, and channel preferences) are configured in the lower half of the same page. ## 6. More help - **Supplier Hub FAQ** — specific setup and operating questions, limits, and troubleshooting. - Ask AI — the assistant answers read-only questions about vendors, RFQs, quotes, and vendor performance. **Keywords:** supplier hub, source, rfq, rfp, rfi, vendor management, vendor scorecard, vendor qualification, quote comparison, sourcing, procurement handoff, supplier-hub --- # Surveys App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-18 How to set up and run employee surveys — audience, anonymity, recurring pulses, program surveys sent by events, courses, onboarding and exits, results, the weekly digest and the anonymous feedback channel. # Surveys ## 1. What it is Surveys lets you author, distribute, and analyse employee surveys — engagement checks, recurring pulses, manager-effectiveness reviews, exit interviews, and custom questionnaires. It includes a separate anonymous feedback channel employees can use any time, outside a formal survey. Other apps can also send a survey you wrote for them: a post-event survey from Calendar, a session evaluation from Training, an onboarding check-in, or an anonymous exit survey. These are **program surveys**, and their results collect on the **Programs** page. - **Enablement:** Surveys is a licensed app. An admin enables it in **Admin → Apps → All Apps**, and it requires a licence. - **What it is not:** Surveys shares its question engine with the Forms app (same field types and builder), but a survey adds audience targeting, anonymity enforcement, scheduling, AI-powered analysis, and a response-rate dashboard that a plain form does not have. ## 2. Standing it up 1. Enable the app in **Admin → Apps → All Apps → Surveys**. 2. Go to **Surveys → Settings** and review the defaults. The two decisions that matter most on day one are whether to keep the **Anonymous Feedback Channel** turned on (it is on by default) and who is allowed to create surveys. By default only app admins can create surveys — widen it under **Who can create and manage surveys?** if managers or specific groups should also author their own. 3. Grant survey-administrator access to the HR team members who will manage results and the feedback inbox. They need the **Surveys app admin** role, assigned through **Admin → Users → Roles**. 4. Create your first survey: go to **Surveys → Manage Surveys → Create Survey**. You have five starting points: - **Describe it — AI drafts the whole survey** (sections, questions, and response types from a short prompt). - **Browse Library** — curated cross-customer templates filterable by industry or use case. - **Start from Template** — built-in templates: Employee Engagement Survey, Quick Pulse Check, Manager Effectiveness, New Hire Feedback, and Exit Interview. - **Use Existing Form** — pick any published form from the Forms app; questions are copied automatically. - **Duplicate Previous Survey** — re-run a past survey with the same questions. 5. Set the audience, schedule, and privacy options, then choose **Activate**. The survey must have at least one question before it can be activated. If your organization approves surveys before they go live, submit it for approval first (see **Getting a survey approved** below). 6. Confirm it is live: employees in the audience see it under **Surveys → Take Survey**, on their dashboard widget, and in their Inbox once invitations go out — when you choose **Send Invitations**, or on their own when the survey opens if **Send invitations when the survey opens** is on. **Silent-pairing note:** A survey targeted at specific departments, locations, or groups does nothing until at least one active employee belongs to the selection. If the audience resolves to zero people, activation succeeds but nobody receives the survey. ## 3. How it fits together **Survey types** — Four types organise surveys by purpose: **Engagement**, **Pulse**, **Custom**, and **Manager Feedback**. The type is a label for filtering and reporting; it does not restrict what questions you can ask. It is not the same as a program's **Kind** (below). ### Anonymity **Anonymity vs. confidentiality** — These are separate switches on every survey and the most common source of confusion. - **Anonymous Responses** (on by default for new surveys) strips respondent identity from results, exports, and the heatmap. Participation is still tracked so the system knows who to remind, but responses cannot be linked back to individuals. Anonymous exports give each answer only the week or month it was submitted in, never a time or a day, so they cannot be cross-referenced against login or badge logs. Once a survey has collected at least one response, anonymity can no longer be turned off — this is enforced at the data layer, not just the form. - **Confidential results** limits who can see results at all — only the survey owner, anyone they explicitly share results with, and survey administrators. When confidential is on, managers get no automatic team view and employees never see results, regardless of the other visibility switches. Confidentiality is independent of anonymity: a survey can be both anonymous and confidential, or neither. **Response floor** — Results stay hidden until a survey has enough responses to protect anonymity. Your organization sets the floor in **Settings** (**Minimum Response Threshold**, default 5). A single survey can raise it for itself — useful for a sensitive topic such as an exit or harassment pulse — with **Minimum responses before results show** on the edit page. A survey can never go below your organization's floor, and once responses have been collected its floor can be raised but not lowered, because people answered on the promise of that number. The same floor holds everywhere results appear: the results page, the heatmap, comments, exports, AI analysis and the results summary. ### Audiences, programs and pulses **Audience targeting** — Every survey targets one of four audience scopes: **All Employees**, **Specific Departments**, **Specific Locations**, or **Specific Groups** (from Admin › Groups). Two additional access modes support link-based distribution: **Anyone with the Link** (no login required — suitable for external respondents or customer feedback) and **Anyone with Link (Login Required)**, which tracks who responded but lets anyone with the URL take the survey after signing in. For link-based surveys you can generate a QR code from the Manage Surveys page. A program survey run has a fifth audience, **Invited people** — exactly the people the program sent it to. You can't choose it by hand. **Program surveys** — A program is something that sends the same survey over and over: an event, a training course, or a moment in someone's employment. You write the survey once in Surveys; this is the *template*. Each time the program fires, it sends a *run* (a copy of the template) to the people involved. | Kind | Where you connect the survey | Who is asked, and when | |---|---|---| | Event feedback | Calendar → event type → **Post-event survey** | Attendees after each event of that type ends — only while Calendar's **Auto-send post-event surveys** is on (Off by default) | | Event feedback | Calendar → an event's feedback summary → **Send a follow-up survey** | A host who may send that survey in Surveys chooses: people who checked in, everyone who said yes or maybe, or everyone invited. Use it for a focus group or workshop follow-up | | Training evaluation | Training → course → **Session evaluation survey** | Learners marked attended when a session is finalized; never no-shows | | Lifecycle survey | A survey step on an Onboarding Hub plan | The new hire, on the step's due date | | Lifecycle survey | Offboarding → Settings → **Send leavers an anonymous survey** | The leaver, once, when their departure is communicated. Only anonymous surveys can be picked | | Lifecycle survey | Ask AI, in Surveys | People you name, with a reason such as a transfer, a promotion or becoming a manager | A worked example: you link a "Course evaluation" survey to a course, and the course runs ten sessions. Each finalized session sends its own run, so the **Programs** page shows the course once, with **Runs** of 10. Four rules catch admins out: - **A template must be ready.** It needs questions, approval if your organization requires it, and must not be archived. The linking form warns "This survey won't be sent until it's ready" and says why. - **A recurring pulse can't be a template.** Its runs would mix into the pulse's results. Duplicate it and link the copy. - **Lifecycle runs are shared.** Everyone sent the same survey in the same window joins one run, so results can reach the response floor and one person's anonymous answer is never a run of its own. The window is the template's own open-to-close span, or 14 days if it has none. - **Runs stay out of Manage Surveys.** You manage the template there and read the runs under **Results → Programs**. An event's host and delegate, and a course's instructor, also get their run's results unless the survey is **Confidential**. **Recurring pulses** — A survey can be set to repeat on a **Weekly**, **Bi-weekly**, **Monthly**, or **Quarterly** cadence. When the current occurrence closes, the system automatically creates the next one with the same questions and audience. Each new occurrence keeps the survey's own response floor and its **Send invitations when the survey opens** setting, so a quarterly pulse set to send on open invites its audience every quarter without anyone pressing a button. All occurrences are linked into a pulse series, and the **Trend** view shows how responses change across runs. ### Sharing, tabs and other apps **Collaboration and access grants** — Survey owners can share a survey with other users or groups at four access levels: **Viewer** (read the definition), **Editor** (edit questions and settings), **Results** (view full results and export), and **Co-owner** (everything the owner can do except delete the survey). Admins and survey app admins always have full access regardless of grants. A user who has been shared a survey sees it on their **Manage Surveys** tab even if the tenant-wide "who can create" policy would not let them create new surveys. **Relationship with Forms** — Every survey is backed by a Forms template. You edit questions by opening the Forms builder (the survey editor links directly to it with **Open in Forms app to edit questions**). An existing published form can become a survey in one step without rebuilding any questions; the original form stays unchanged. **Draft autosave** — While an employee is taking a survey, their in-progress answers are saved as a draft automatically. If they navigate away and come back, the draft is restored. If a survey closes while someone is mid-submission, their answers are salvaged as a draft rather than lost. **Navigation tabs** — The app shows different tabs depending on the user's role: - Everyone sees **Dashboard** and **Take Survey**. - Users who can create surveys (per the tenant policy) or who have been shared at least one survey see **Manage Surveys**. - **Results** appears for the people named under **Who can view survey results across the company?**, and for anyone given Results or Co-owner access to a survey. - **Feedback Inbox** appears for the people named under **Who can read and action the anonymous feedback inbox?**, while the channel is on or it holds submissions. - **Team Results** appears for anyone with at least one direct report, admins included. - Admins and Surveys app admins also see **Access Review** (everyone granted access to a survey they don't own) and **Settings**. **Mobile** — Employees can browse available surveys, take surveys, save drafts, and submit anonymous feedback from the mobile app. The mobile views are optimised for touch and do not require desktop access. **Integrations with other apps** — Surveys connects to other parts of the platform in several ways: - The **Performance** app can automatically send a survey after a performance review is approved (post-review survey). - The **Service Desk** app can trigger a satisfaction survey when a help request is resolved or closed. - The **Onboarding Hub** can include surveys as steps in an onboarding plan, with configurable day offsets and due dates. Each step is sent as a program survey on its due date. - Surveys feeds sentiment and theme data into **Mango Signal** for organisation-wide analytics, and a survey's results page can raise a Mango Signal action (see **Acting on results in Mango Signal**). ## 4. Running it ### Getting a survey approved (optional) Some organizations review every survey before it reaches employees. An admin turns this on by creating an approval workflow for the Surveys app with the process **Survey publication** (**Admin → Approval Workflows**). With no such workflow, surveys activate directly, as described above. 1. On the survey's edit page, the **Publication approval** panel replaces **Activate**. When the questions are ready, choose **Submit for approval**. Approvers get an Inbox item they can approve or reject from, and the request is listed under **Approvals**. 2. While it waits its questions are locked, so approvers decide on exactly what was submitted. To change them, choose **Withdraw request**, edit the survey, and submit again. 3. Once approved, **Activate** comes back. Approval does not activate the survey for you — activating can email the whole audience, so that stays your choice. 4. An approval covers the questions it was given for. If a question changes afterwards, the survey needs approving again before it can be activated. Later rounds of an approved recurring pulse are covered while their questions stay the same. If approval is turned on while a recurring pulse is already running, its next round is skipped until the round that is running now is approved: the owner is told, and the notice links to that round's edit page, where it can be submitted. Once it is approved, the next round goes out on schedule. ### Sending invitations and reminders 1. Open **Manage Surveys**, select a survey, and choose **Send Invitations**. Each targeted employee receives an email and an Inbox notification with the survey name, estimated completion time, and deadline. 2. To have invitations go out on their own, turn on **Send invitations when the survey opens** on the edit page. Everyone in the audience gets the email and an Inbox item once, within 15 minutes of the open time — so a survey scheduled for next Monday doesn't open unannounced. On a survey that is already open, turning it on emails nobody now; use **Send Invitations** instead. Only people allowed to send to the whole company can turn it on for an **All Employees** survey. 3. To nudge non-respondents, choose **Send Reminders** — only employees who have not yet responded receive the reminder. 4. Before the close date — 3 days by default — the system automatically sends a pre-close reminder to non-respondents. Both the reminder and its timing are in **Settings**. The survey owner receives a notification when the response count meets the survey's response floor. ### Reviewing results 1. Go to **Results**, select a survey. The dashboard shows per-question summaries and response rates. You can filter results by department, location, manager, tenure, employee type, performance tier, or date range. When **AI Analysis** is enabled, the system generates sentiment scores (overall and by distribution), themes (3–7 per survey), and focus areas (top 3). 2. Use the **Heatmap** to compare scores across five dimensions: department, location, manager, tenure, and employee type. The tenure dimension groups employees into brackets: New Hire (under 1 year), 1–3 Years, 3–5 Years, 5–10 Years, and 10+ Years. Segments with fewer responses than the minimum response threshold display "N/A" to protect anonymity. 3. Open **Comments** to browse free-text responses. You can highlight individual comments to flag them for follow-up. For anonymous surveys, if applying demographic filters would narrow the responses below the threshold, the comments are blocked entirely. 4. **Export** downloads responses as CSV. For anonymous surveys the export gives each answer only the week or month it was submitted in. 5. Managers see a separate **Team Results** tab showing their direct reports' responses, or everyone below them when they choose **Everyone below me** — but only on surveys where the owner turned on **Let managers see their team's results** and the survey is not confidential. ### Reading program results 1. Go to **Results** and choose **Programs**. The button appears once you can see results for at least one program run. 2. Each row is one program: **Program**, **Kind**, **Runs** and **Latest run**. It lists only runs you hold full results on. 3. Choose **View results** to open the trend of that program's runs, with totals across them. A run below its response floor is left out of the totals and counted only as left out. Rating questions show group averages across runs; nothing pairs one person's answers. ### Acting on results in Mango Signal On a survey's results page, a **Create action** button sits beside each question and each AI theme. It opens Mango Signal's new-action drawer, prefilled, and the action keeps a link back to the survey. The button shows only when Mango Signal is on for your organization and you can read the survey's results as a manager or above or a Mango Signal app admin. The link carries the survey's name and the question or theme — never answers, counts or respondents. On a **Confidential** survey, the prefilled text names neither the survey nor the question. ### The weekly executive digest Every Monday, the roles ticked under **Who receives the weekly executive digest?** get an email and an Inbox notification. It summarises the surveys that closed the week before — responses, ratings and themes — leaving out anything below a survey's response floor. It covers up to 10 surveys and leaves program runs to the Programs page. Nothing is sent in a week when no survey closed. Each reader sees only surveys they hold full results on, and can mute it in their notification preferences under **Survey executive digest**. ### Sharing results back with employees After reviewing, you can publish a "You said, we did" summary. Open the survey's results page, choose **Share Results**, preview the aggregate and write the message, then **Publish to the whole audience**. Everyone in the survey's audience who can use Surveys, including those who didn't respond, receives the summary in their Inbox, and by email if they have an email address. ### Managing anonymous feedback When the Anonymous Feedback Channel is enabled, employees can submit feedback at any time — it is not tied to any specific survey. Each submission picks a topic (Workload, Safety, Leadership, Culture, Compensation, Communication, or Other) and receives a claim code. The employee can check their feedback's status later at `/feedback-status` using that code, without revealing their identity. 1. HR reviews submissions in **Surveys → Feedback Inbox**, filtered by status (**New**, **In Progress**, **Closed**) and topic. 2. Mark a submission **In Progress** to acknowledge it, add internal notes, and **Close** it when resolved. 3. Bulk actions let you close or mark multiple submissions at once. ### Non-responders and QR codes From **Manage Surveys** you can view the list of employees who have not yet responded (up to 200 shown). You can also generate a **QR code** for any survey with a shareable link — useful for posting in break rooms or on digital signage. ### Closing and archiving - A survey closes automatically when its close date passes. A daily background job handles this, emails the owner that results are ready (unless **Notify the survey owner when a survey closes** is off), and triggers AI analysis if the response threshold is met. Program runs close the same way, without the owner notice. - You can also close a survey manually from **Manage Surveys → Close**. - Closed surveys can be archived to move them off the active list. A draft survey with zero responses can be deleted outright; once responses exist, archive instead. - You can regenerate a survey's shareable link at any time; doing so invalidates the previous link and QR code. ## 5. Settings All settings are at **Surveys → Settings**. Only admins and survey app admins can access this page. | Setting | Default | What it changes | |---|---|---| | **Enable Surveys Agent** | On | Lets users interact with the Surveys agent through Ask AI to create surveys, check responses, and run analysis. | | **Enable Anonymous Feedback Channel** | On | Shows the anonymous feedback form to employees and the Feedback Inbox tab to admins. | | **Enable AI Analysis** | On | Enables AI-powered sentiment analysis, theme extraction, and focus-area generation on survey responses. | | **Minimum Response Threshold** | 5 | Number of responses required before results, AI insights, and heatmap cells are shown. Protects anonymity in small segments. A survey can raise it for itself, never lower it. | | **Include survey data in Report Agent** | On | Lets Report Agent build reports from survey data. It does not turn the Surveys app on or off. | | **Send pre-close survey reminders** | On | Emails non-respondents before a survey closes. Invitations and results summaries are unaffected. | | **Send that reminder this many days before close** | 3 | How far ahead of the close date the reminder goes out. | | **Notify the survey owner when a survey closes** | On | Sends the owner a notice when their survey closes, automatically or by hand. | | **Who receives the weekly executive digest?** | **Business admins** | Roles that get the Monday digest. Untick both to stop it. | | **Route new anonymous-feedback alerts to** | **Everyone who can triage the inbox** | Narrows the new-feedback alert to one group's members who can also triage. | | **Who can create and manage surveys?** | **App admins only** | Controls which users can author, edit, send, and close surveys. Can be widened to managers, everyone, or specific groups. Admins and survey app admins always pass regardless. | | **Who can view survey results across the company?** | **App admins only** | Name a group to give it the results of every survey, without authoring, settings or the feedback inbox. | | **Who can send a survey to the entire company?** | **App admins only** | Who may send invitations, reminders and results summaries on an **All Employees** survey. | | **Who can read and action the anonymous feedback inbox?** | **App admins only** | Name your People or HR group to work the Feedback Inbox. Company admins keep access. | ### Per-survey settings (on the survey edit page) | Setting | Default | What it changes | |---|---|---| | **Anonymous Responses** | On | Strips respondent identity from results and exports. Locked once responses are collected. | | **List in the Surveys app** | On | Shows the survey in the Take Survey browse list. Turn off for surveys distributed only through another channel (e.g. an onboarding step or performance-review follow-up) so it is reachable only via its direct link. | | **Confidential results** | Off | Restricts results to the owner, explicit grantees, and survey administrators. Blocks manager team view and employee results summary. | | **Let managers see their team's results** | Off | Lets managers view their team's responses — direct reports, or everyone below them. Ignored when the survey is confidential. | | **Show a results summary to employees** | Off | Lets employees in the audience view an anonymized aggregate summary after responding. Ignored when the survey is confidential. | | **Minimum responses before results show** | Blank (your organization's floor) | Raises this survey's response floor above the organization's. Can't be set below it, and can't be lowered once responses exist. | | **Send invitations when the survey opens** | Off | Emails the invitation and posts an Inbox item to the whole audience once, when the survey opens. Recurring pulses do this for every round. | | **Repeat / Recurrence** | None | Weekly, Bi-weekly, Monthly or Quarterly. The next occurrence is created with the same questions, audience and settings. | ## 6. More help - [Surveys FAQ](/help/articles/surveys_app_faq) — specific setup questions, limits, and troubleshooting. - Ask AI — the assistant answers questions about Surveys from these articles. **Keywords:** survey, pulse survey, engagement survey, anonymous survey, employee feedback, survey results, anonymous feedback, heatmap, survey analysis, pulse check, survey template, QR code survey, quarterly pulse, response floor, send invitations when the survey opens, survey approval, program survey, post-event survey, event feedback survey, training evaluation, session evaluation survey, onboarding check-in survey, anonymous exit survey, follow-up survey, focus group survey, executive digest, Mango Signal action, surveys --- # Surveys FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Surveys — for the admin running it. # Surveys FAQ Answers to common setup and operating questions about Surveys. For what the app is and how to set it up from scratch, see the [Surveys Overview](/help/articles/surveys_app_overview). --- ## Setup ## What do I need to configure before my first survey? Enable the Surveys app from Admin → Apps → All Apps and open its **Settings** tab. The settings that matter most before your first survey: **Enable AI Analysis** (on by default — controls whether the AI sentiment, themes, and focus-areas panel is available on results), **Minimum Response Threshold** (defaults to **5** — results, heatmap cells, open-text comments, and CSV exports for anonymous surveys stay hidden until this many responses arrive), and **Enable Anonymous Feedback Channel** (on by default — adds a separate always-on feedback inbox for employees). You can also configure **Who can create and manage surveys** — by default only admins and app admins can, but you can widen it to managers, specific groups, or everyone. ## Who can create and manage surveys? The **Who can create and manage surveys** setting on the Settings tab controls this. The default is **App admins** — meaning business admins, super admins, and anyone you have designated as a Surveys app admin. You can widen it to managers, specific groups, or all employees. Regardless of this setting, admins and app admins always retain full access. A user who was shared on a specific survey (via a collaborator grant) can manage that survey even without the tenant-wide create capability. --- ## Permissions and access ## Why can't a specific group of employees see a survey? Each survey has a **Target Audience** set during creation: **All Employees**, or a specific set of **Departments**, **Locations**, or **Groups**. Employees outside the selected audience are not assigned the survey and will not see it on their Take Survey page. Check the survey's audience setting in the editor and confirm the employee belongs to at least one selected department, location, or group. Also confirm the survey status is **Active** and within its open/close dates — a draft, closed, or scheduled survey is invisible to employees. ## What are the collaborator access levels, and how do I share a survey with another manager? Open a survey in the editor and use the **Collaborators & Access** card to share it with individual users or groups. There are four access levels: 1. **Viewer** — can see the survey definition (read-only). 2. **Editor** — can see and edit the survey (co-author questions and settings). 3. **Results** — can see the definition (read-only) and view the survey's responses and results. 4. **Co-owner** — can edit, view results, manage the lifecycle (activate, close, send reminders), and manage sharing. Only the survey owner or an admin can delete a survey; a co-owner can close or archive it but not delete it. Capabilities from multiple grants are additive — if someone has an Editor grant directly and a Results grant through a group, they hold both. --- ## Day-to-day ## Can surveys be anonymous, and what happens if I turn anonymity on? New surveys default to **anonymous**. When a survey is anonymous, respondent names are hidden in results, the comment browser, heatmap cells, and CSV exports. Exported CSVs give an anonymous answer only the week or month it was submitted in ("Week of Sep 14", "September 2026") — never a time or a day — to prevent cross-referencing against badge or VPN logs. Anonymity is a promise: once a survey collects its first response, anonymity can no longer be turned off — the toggle is locked at the model level so no path (UI, API, or agent) can retroactively expose identities. ## How does the anonymity threshold protect small groups? Results, per-question summaries, heatmap cells, open-text comments, and CSV exports for an anonymous survey only unlock once the survey reaches the **Minimum Response Threshold** (defaults to **5**, configurable in Settings). This prevents demographic filters — department, location, tenure — from slicing an anonymous survey down to a single identifiable person. The same threshold gates the AI analysis: it will not run until enough responses arrive. ## Can one survey need more responses than the rest before results show? Yes. On the survey's edit page, **Minimum responses before results show** raises the floor for that survey alone — for example 10 for an exit or harassment pulse while the rest of your surveys use 5. Leave it blank to use your organization's floor. It can't be set below your organization's floor, and once responses have been collected it can be raised but not lowered, because respondents answered on the promise of that number. Recurring pulses carry it to every new round. ## How are surveys distributed, and can reminders be automated? You can distribute a survey four ways: **email invitation** (Send Invitations button on the Manage Surveys list), an **authenticated link** (requires login), a **public link** (no login or account required), or a **QR code** (generated from the sharing modal for active public surveys). You can also set **open and close dates** to schedule availability. Invitations can go out on their own: turn on **Send invitations when the survey opens** on the edit page, and everyone in the audience gets the email and an Inbox item once, within 15 minutes of the open time. That is how a survey scheduled for later avoids opening unannounced, and a recurring pulse with it on invites its audience every round. On a survey that is already open, turning it on emails nobody now — use **Send Invitations**. For an **All Employees** survey, only people allowed to send to the whole company can turn it on. Reminders are partially automated. A daily background sweep sends reminders to non-respondents for surveys closing within the next **3 days** — once per close window, so extending the deadline re-arms a fresh reminder. You can also manually send reminders at any time from the Manage Surveys list; reminders go only to employees in the target audience who have not yet responded. ## How do I set up a recurring pulse survey? In the survey editor, choose a **Recurrence** cadence: **Weekly**, **Biweekly**, **Monthly**, or **Quarterly** (a common rhythm for engagement pulses). When the current occurrence closes, the platform automatically clones it into a new active survey with fresh open and close dates. Each occurrence keeps its own responses and results — the **Trend** tab on the results page shows response count and completion rate across all runs in the series. To stop recurrence, set the cadence back to **None**; the series history is preserved. ## Can surveys be approved before they go live? Yes, if your organization wants it. An admin creates an approval workflow for the Surveys app with the process **Survey publication** (**Admin → Approval Workflows**) and picks the approvers. From then on a survey's edit page shows a **Publication approval** panel instead of **Activate**: submit the survey, approvers approve or reject it, and **Activate** returns once it is approved. A survey's questions are locked while it waits, so approvers decide on exactly what was submitted; withdraw the request to make changes. An approval is for the questions it was given for — change a question and the survey needs approving again. While a survey is live its questions can't be changed at all: close it, edit them, then submit it for approval again before reactivating it. Later rounds of an approved recurring pulse are covered while their questions stay the same. If a recurring pulse was already running when approval was turned on, approve the round that is running now and its next round goes out on schedule. With no such workflow, surveys activate directly. ## Can other apps send one of my surveys? Yes — as a **program survey**. An event's post-event survey, a training course's session evaluation, a host's follow-up survey and an onboarding plan's check-in all use a survey you made as a template: each run (one event session, one training session, one group of new hires) is a copy of it sent to exactly the people it concerns. Runs are listed under **Results**, not among the surveys you manage, and you aren't emailed as each one closes; open a run's results and choose **View Trend** to compare it with the template's other runs. The people it's sent to can answer it even if they don't otherwise use Surveys. If the survey shows a results summary to employees, they also get the summary when you share it, and can open that survey's results. Recurring pulse surveys can't be used this way — duplicate one and use the copy. ## Can I create a survey from AI, a template, or an existing form? All three. On the new-survey page you can: - **Describe it to AI** — type a sentence describing what you want, and AI drafts a complete survey with sections, questions, and response types for you to refine. - **Start from a template** — choose from five built-in templates (Employee Engagement, Quick Pulse Check, Manager Effectiveness, New Hire Feedback, Exit Interview), browse a curated cross-customer template library, or duplicate a past survey. - **Use an existing form** — select any published form from the Forms app and convert it into a survey in one step, without rebuilding questions. ## What happens when a survey closes — does it close automatically? Yes. A survey with a **Close Date** is automatically closed by a daily background job once that date passes. When a survey closes (manually or automatically), the survey owner receives a **Survey Closed** email with the response count and completion rate. If AI Analysis is enabled and the survey meets the minimum response threshold, an AI analysis is also kicked off automatically so results are ready when the owner opens them. ## Who can see survey results, and can I export them? Results access depends on the survey's settings and your role: - **Full results** — the survey owner, anyone with a Results or Co-owner collaborator grant, and admins see all responses, the heatmap, comments, AI analysis, and can export to CSV. - **Team results** — managers see their team's responses — their direct reports, or everyone below them when they choose **Everyone below me** — and only when the survey has **Let managers see their team's results** turned on and is not marked **Confidential**. - **Employee aggregate** — employees in the audience can see a threshold-gated summary only, and only when the survey has **Show a results summary to employees** turned on and is not marked **Confidential**. CSV export is available only to full-results holders — never to the team or employee aggregate views. --- ## When something looks wrong ## "I completed the survey but it still shows in my pending list" The Take Survey page shows surveys you are assigned to and have not completed. If you submitted and still see it, your answers may have been saved as a **draft** rather than submitted. A survey you started shows **Continue Survey** (a **Started** badge on the phone) — it opens with "Resuming your saved draft" and your answers filled in. A draft is not a completed response; press **Submit** to send it. ## "My employees say they can't find the survey" Check three things: (1) the survey status is **Active** (not Draft, Closed, or Archived), (2) the current date is within the survey's open and close dates, and (3) the employee is in the **Target Audience** — if the survey targets specific departments, locations, or groups, employees outside those selections will not see it. Also check the **List in the Surveys app** toggle — if it is off, the survey will not appear in browse lists (it can only be reached through its direct link, email invitation, or an integration like onboarding). ## "I ran the AI analysis but nothing appeared" Three possible causes: (1) the survey has not reached the **Minimum Response Threshold** — AI analysis will not run until enough responses arrive (default **5**); (2) the analysis is still processing — allow a few minutes; if the analysis has been processing for more than 10 minutes it is likely stalled, and you can retry; (3) the analysis ran within the last hour — the platform deduplicates analysis runs, so if a recent analysis already completed, clicking Run Analysis shows "Analysis is already up to date." Check the results page for a status badge showing Ready, Processing, or Failed. ## "I can't delete a survey" A survey that has collected responses cannot be deleted — **archive** it instead. Only **draft** surveys or surveys with **zero responses** can be deleted. A conversation survey can't be deleted once people have started conversations on it, even before anyone has sent their answers, because deleting it would delete those conversations — close or archive it instead. This protects response data from accidental loss. Additionally, only the survey owner or an admin can delete; a co-owner can close or archive but not delete. --- ## Conversation surveys ## Can people answer a survey as a conversation instead of a form? Yes, once an admin turns on **Collect answers by conversation** in Surveys settings (it is off by default). A survey owner can then collect a survey's answers by conversation: each person has a short conversation with an AI interviewer, which asks each topic's opening question and follows up on what they say. At the end the person sees what will be recorded and can change it, or remove any answer that isn't required, before it's sent. **Offer the microphone in conversations** (also off by default) lets people answer by holding to talk or in a live voice call. While conversation mode is off, a conversation survey stays listed for the people it was sent to, but nobody can start it, and a conversation already under way is paused until the setting is turned back on. ## Who sees what someone says in a conversation? On an **anonymous** survey the conversation names nobody: the person's name isn't stored with their answers, and results show only for groups at or above the survey's response floor. On a **named** survey, the people running it, including admins, see the answers each person approves at the end, with their name; the conversation itself is visible only to that person, who can read it again from their completed surveys while it is kept. Someone who answers a named survey's public link without signing in is stored without a name. ## What is the conversation code? An anonymous conversation is tied to no account, so it shows a **conversation code** — 12 letters and numbers, like K7QF-29XM-PT4C — once, to keep. On the **Carry on a conversation** page (/ai-interviews/resume, linked from the survey's card and from Take Survey) the code carries on a conversation that hasn't been sent, on another phone or computer, or takes back answers that were sent while the survey is still open. Taken-back answers are deleted and left out of the results; the completion rate still counts the person as having taken part, and the results page says how many did. A conversation that isn't sent is deleted 2 days after it started. This code is not the Anonymous Feedback claim code (8 characters), which is checked on the Feedback Status page. ## What are Findings? A conversation survey's results page has a **Findings** tab for the people who see its full results. AI analysis of the sent conversations answers each of the survey's research questions, counting how many people said each thing, with quotes as evidence. Nothing is shown until at least the survey's response floor of people have taken part (5 by default), so nothing can be traced back to a person. Findings are made when the survey reaches its close date, and on demand from the Findings tab; they need **AI analysis** to be on in Surveys settings. ## How do I share a "You said, we did" summary, and can I take it back? Once a survey has closed with enough responses to show results, **Share Results** on its results page opens a message prefilled from the results for you to edit. Publishing sends it to everyone in the survey's audience, including people who didn't respond, as an Inbox item and an email, and it shows on their Surveys home. The next round of a conversation survey can open by asking whether what changed made a difference. To take a summary back, choose **Stop sharing** on the Share Results page: it leaves Surveys and people's Inbox, and new conversations in the next round no longer follow up on it — or on an earlier round's summary in its place. Emails already sent can't be recalled. If you share a summary again later, the people who had the earlier one see the new one in Surveys but aren't notified again. --- ## Anonymous Feedback ## What is the Anonymous Feedback channel, and how does it work? The Anonymous Feedback channel is a separate, always-on surface where any employee can submit feedback at any time — independent of any specific survey. It is enabled by the **Enable Anonymous Feedback Channel** setting (on by default). Employees choose a topic — **Workload**, **Safety**, **Leadership**, **Culture**, **Compensation**, **Communication**, or **Other** — and write a message (minimum 10 characters). No identity is recorded. After submitting, the employee receives a one-time **claim code** (8 characters) they can use to check the status of their feedback later. The people named under **Who can read and action the anonymous feedback inbox?** in Settings (app admins by default) see incoming feedback in the **Feedback Inbox** tab, where they can triage items by topic and status (**New**, **In Progress**, **Closed**), add action notes, and close items. When new feedback arrives, a bell notification (topic only, never the message body) goes to those same people 30 minutes to 2 hours later, at a random moment — so its time can't point to who sent it. An item someone has already picked up from the inbox sends no bell. ## How can a submitter check the status of their anonymous feedback? The submitter enters their claim code at the **Feedback Status** page (a public, unauthenticated page). The page shows the review status and any action notes the admin added — never the topic, message, reviewer, or any identity. If the code does not match, the page looks the same as a not-found result, so nothing leaks about which codes exist. --- ## Licensing and limits ## Does Surveys require a licence? Yes. Surveys requires a licence and is disabled by default. An administrator enables it for your business from Admin → Apps → All Apps. Once enabled, people in your organization can take surveys and use the feedback channel. Who can create surveys, read results across the company and work the feedback inbox is set on the app's **Settings** page. ## Are there limits I should know about? | What | Limit | |---|---| | Survey name length | 255 characters | | Survey types | Engagement, Pulse, Custom, Manager Feedback | | Audience targeting | All Employees, Department, Location, Group | | Recurrence cadences | Weekly, Biweekly, Monthly, Quarterly | | Minimum response threshold (default) | 5 responses (configurable in Settings; a survey can raise its own) | | Per-survey response floor ceiling | 1,000 responses | | Heatmap dimensions | Department, Location, Manager, Tenure, Employee Type | | Built-in templates | 5 (Engagement, Pulse, Manager, New Hire, Exit) | | Anonymous feedback topics | 7 (Workload, Safety, Leadership, Culture, Compensation, Communication, Other) | | Anonymous feedback message minimum | 10 characters | | Anonymous Feedback claim code length | 8 characters | | Conversation code length | 12 characters | | Unsent anonymous conversation kept for | 2 days after it started | | Non-responder list display cap | 200 employees per view | | Pre-close automated reminder window | 3 days before close date | | AI analysis deduplication window | 1 hour | | Collaborator access levels | Viewer, Editor, Results, Co-owner | --- ## More help - [Surveys Overview](/help/articles/surveys_app_overview) - Ask AI — the assistant answers Surveys questions from these articles. **Keywords:** faq, survey, anonymous, pulse, engagement, feedback, heatmap, threshold, anonymity, reminders, results, AI analysis, quarterly, response floor, invitations, approval, conversation, AI interviewer, findings, you said we did, conversation code, surveys --- # Talent Hub App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-18 How to set up Talent Hub, navigate its recruiting analytics pipeline board, manage sources, run compliance reports, and configure AI insights. # Talent Hub ## 1. What it is Talent Hub is the recruiting analytics and pipeline-management layer that sits on top of the data created by Job Board, Interview Scheduler, and Offer Manager. It has no candidates, jobs, or offers of its own — every record it displays is the live record from those apps, so there is no export or import step to see the full pipeline in one place. - **Enablement:** Talent Hub requires a licence and is off by default. An admin enables it from Admin → Apps → All Apps. - **What it is not:** Talent Hub does not replace Job Board for posting jobs or managing individual candidates. It is the reporting, analytics, and cross-job pipeline view — not the per-job operational surface. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps → Talent Hub → Enable**. The app requires a licence. 2. **No additional configuration is mandatory.** Because Talent Hub reads from Job Board, Interview Scheduler, and Offer Manager, it starts working the moment at least one of those apps has data (published jobs, candidates, interviews, or offers). 3. Access is open to recruiting staff — admins, HR admins, and app admins of Talent Hub, Job Board, Interview Scheduler, or Offer Manager — and to anyone holding the manager role or higher. A plain employee below manager who is not recruiting staff cannot open it. Who sees candidate names, contact details and AI scores is set separately on **Settings → Candidate data access** (default: managers and above, plus recruiting staff). 4. Confirm it worked: open **Apps → Talent Hub**. The Home tab shows quick metrics (Total Open Jobs, Applications, Interviews, Hires, Avg Time to Fill) and an Action Center of prioritised to-do items drawn from live pipeline data. The **Sources** tab is empty until you seed it. Go to **Sources → Seed Standard Sources** to load the built-in set (Indeed, LinkedIn, ZipRecruiter, employee referrals, and others), or create your own. **Silent dependency:** the Compliance tab only appears for people with EEO report access — recruiting staff always, plus whoever **Settings → EEO report access** names (default: managers and above) — and only while **EEO compliance reporting** is on. The AI Insights tab only appears when the AI insights setting is on (it defaults to on). If either is missing from the sidebar, check those two settings. Talent Hub also provides sample data that can be loaded from **Settings → Load/Remove Sample Data**. This loads a shared recruiting dataset (jobs, candidates, interviews, and offers) used across Talent Hub, Job Board, Interview Scheduler, and Offer Manager. Sample records are tagged and can be removed without touching real data. ## 3. How it fits together **Pipeline stages** — Every candidate moves through a fixed progression of nine stages: Applied → Screening → Qualified → Potentially Qualified → Interviews in Process → Interviewed → Ready for Offer → Offered → Hired Three terminal stages sit outside this sequence: Rejected, Withdrawn, and Unsuitable. The pipeline board enforces meaningful transitions rather than just flipping a status. Dragging a candidate to **Offered** redirects to Offer Manager to create a real offer. Dragging to **Interviews in Process** (when no interview exists) redirects to Interview Scheduler. **Hired** cannot be set from the board — it happens automatically when an offer is signed, or when someone working the accepted offer clicks **Mark as hired** on the offer in Offer Manager. Terminal moves and moving a candidate backwards (including reversing a rejection) require a reason. *Example:* A candidate applies to "Senior Engineer" through Job Board. They appear on Talent Hub's pipeline board in the **Applied** column. A recruiter drags them to **Screening**, then to **Interviews in Process** — the board opens Interview Scheduler to create the interview. After the interview, the recruiter drags them to **Interviewed**, then to **Offered** — the board opens Offer Manager. When the offer is signed, the candidate moves to **Hired** automatically. **Sources and attribution** — A source tracks where a candidate came from. Sources belong to one of eight categories: Job Board, Social Media, Referral, Direct, Agency, Event, Passive Sourcing, or Other. Each source can carry a price (CPC, CPA, Flat Fee, or Monthly). A per-application (CPA) price is counted for each application the source is credited with; for a flat, monthly or per-click fee, record what you paid for a period under **Recorded spend** on the source's edit page. Source Analytics and cost per hire add both, spreading a period's spend evenly over its days. UTM parameters on application links feed the campaign-performance view. **Relationship to sibling apps** — Talent Hub reads but does not write the core recruiting records. Candidates belong to Job Board, interviews to Interview Scheduler, offers to Offer Manager, and onboarding plans to Onboarding Hub. The Action Center links directly into those apps for the actual work (converting a hire to an employee, submitting interview feedback, following up on an expiring offer). The Quick Access panel on the Home tab shows links to all enabled recruiting apps. **AI Insights** — The AI Insights tab provides five groups of narrative analysis: general, pipeline, sourcing, interview, and bias insights. These are generated by a real LLM grounded in the tenant's actual recruiting metrics. The page loads instantly with a heuristic baseline; a background job warms the AI-generated narrative so the next page load shows it. The Hiring Forecast card is always a numeric projection and is never run through the LLM. **Stalled candidates** — A candidate in a non-terminal stage with no activity (a stage move, edit, note, call or email) for 14 or more days is flagged as stalled. The Candidates tab badges the count, the Action Center lists them, and a daily background job nudges whoever sourced the candidate — or, if nobody sourced them or that person has left, the job's recruiter and hiring manager, else the job's creator (at most once every 7 days, and 3 nudges per stall). Candidates idle for more than 60 days, on a closed or filled job, or with an offer awaiting the candidate's answer or an approval while Offer Manager's automated reminders are on are not nudged. **Talent Metrics** — The Talent Metrics tab surfaces key conversion rates (application-to-interview, interview-to-offer, overall hire rate), time-to-fill statistics (average, fastest, slowest), and pipeline distribution charts. All metrics are scoped to a configurable date range that defaults to the last 30 days. ## 4. Running it ### Reviewing the pipeline 1. Open **Apps → Talent Hub → Pipeline**. 2. The board defaults to all jobs. Use the job picker to filter to a single requisition, or filter by department, recruiter, or source. 3. Drag a candidate card between columns to advance or reverse their stage. Terminal moves (Rejected, Withdrawn, Unsuitable) and moves backwards prompt for a reason. 4. Click a candidate card to open the detail drawer with their timeline, interviews, and offers. Each column shows a badge with the true total count; the board renders up to 50 cards per column to keep load times fast. Use the **Show rejected, withdrawn & unsuitable** toggle to show those columns alongside the active pipeline. ### Running reports 1. Open **Apps → Talent Hub → Reports**. 2. Choose one of the five report types: Executive Summary, Hiring Manager Report, Sourcing Effectiveness, Diversity Analytics, or Compliance Report. 3. Pick a date range (Last 7 Days, Last 30 Days, Last 90 Days, Last 6 Months, or Last Year, or your own dates). The report updates as you choose; export it as PDF or CSV. 4. To schedule recurring delivery, click **Schedule delivery** on the Reports page and create a schedule with a cadence (Weekly, Monthly, or Quarterly), format (PDF or CSV), reporting window, and recipients. Eight report types can be scheduled — the five above plus Pipeline Analytics, Performance Analytics, and Trends Analysis. The reporting window is Last 7 days, 30 days, 90 days, 6 months, or 12 months (default 30 days). Recipients must be members of your workspace, and the Diversity Analytics and Compliance Report types only go to people with EEO report access. Report schedules are managed by recruiting staff (admins, HR admins, and recruiting app admins). ### Using AI Insights 1. Open **Apps → Talent Hub → AI Insights** (only visible when the AI Insights setting is on). 2. The page shows five insight groups: general performance, pipeline optimisation, sourcing effectiveness, interview process, and bias/fairness analysis. Each card includes actionable recommendations. 3. Use the **Predictions** sub-tab for hiring forecasts and predicted pipeline outcomes. 4. Use the **Recommendations** sub-tab for AI-generated sourcing, candidate, and process recommendations. The AI narrative refreshes in the background. When no cached AI result exists, the page shows a heuristic baseline derived from the same metrics. The next page load displays the AI version once the background refresh completes. ### Reviewing compliance 1. Open **Apps → Talent Hub → Compliance** (visible to people with EEO report access — see **Settings → EEO report access**). 2. The EEO Compliance dashboard shows diversity metrics and demographic breakdowns. 3. Four dedicated reports are available: EEO-1 Report, Applicant Flow Analysis, Adverse Impact Analysis, and Diversity Trends. 4. Adverse Impact Analysis uses the four-fifths (80%) rule per EEOC Uniform Guidelines: if any demographic group's selection rate falls below 80% of the highest group's rate, adverse impact is flagged. A group with too few candidates to compare is left out of the comparison and shown as **Too few to judge**. All compliance reports can be exported as CSV. EEO-1 reports also export as PDF. ### Searching and filtering candidates 1. Open **Apps → Talent Hub → Candidates**. 2. Filter by status, job, department, date range, or use the search bar to find candidates by name or email. 3. Quick filters at the top: **Active** (non-terminal stages only), **Stalled** (no activity for 14+ days), **Recent Hires** (hired in the last 30 days), and **My Candidates** (candidates you sourced, or on a job where you are the recruiter or hiring manager). 4. Sort by Match Score to surface the highest-scored candidates first; a keyword estimate is marked as one under its score. 5. Candidates can be exported as CSV by recruiting staff (admins, HR admins, and recruiting app admins). Bulk actions include adding candidates to a talent pool. ### Managing sources 1. Open **Apps → Talent Hub → Sources** (recruiting staff only). 2. Create, edit, activate, or deactivate sources. A source with candidate attributions or recorded spend cannot be deleted — deactivate it instead. 3. Set a price per source (CPC, CPA, Flat Fee, or Monthly), and record flat or monthly fees as spend for their period on the source's edit page, so Source Analytics can compute cost per hire and ROI. 4. Use **Seed Standard Sources** to load the built-in set of common sources across all categories. ## 5. Settings Settings default to **On** unless noted. Go to **Apps → Talent Hub → Settings** (recruiting staff only: admins, HR admins, and recruiting app admins). | Setting | Section | Default | What it changes | |---|---|---|---| | Executive summary report | Reports | On | Offers the Executive Summary report type on the Reports tab | | Hiring manager report | Reports | On | Offers the Hiring Manager report type on the Reports tab | | Talent Hub Agent | AI and analytics | On | Answers Talent Hub questions in the Ask AI sidebar | | AI insights | AI and analytics | On | Shows the AI Insights and AI Recommendations pages and their nav entries | | Predictive analytics | AI and analytics | On | Shows the Predictions page and the forecast cards on Analytics, Trends and Talent Metrics | | Pipeline analytics | AI and analytics | On | Shows the Pipeline Analytics page | | Performance analytics | AI and analytics | On | Shows the Performance Analytics page | | Stalled-candidate nudge emails | Notifications | On | Sends the daily stalled-candidate nudge described above | | EEO compliance reporting | Compliance | On | Shows the Compliance tab and its reports, and allows scheduled Compliance Report and Diversity Analytics emails | | EEO report access | Compliance | Managers and above | Who besides recruiting staff can see the Compliance tab and the EEO report types | | Candidate data access | Compliance | Managers and above | Who besides recruiting staff can see candidate names, contact details and AI scores | | Require identity verification for exports | Data security | On for new companies | When on, downloading candidate PII or EEO data as CSV, PDF or XLSX asks the person to verify their identity again. Companies that had Talent Hub before this setting existed were kept Off; only a company admin can change it. | ### Mobile Talent Hub has a mobile-optimised view at **/m/apps/talent-hub** with the dashboard summary, active jobs, candidates (search, plus status, Stalled and Active filters), upcoming interviews, and open offers. Tapping a candidate you can manage opens their Job Board page; tapping an interview or offer opens it in Interview Scheduler or Offer Manager when that app lets you see it. Phone browsers are automatically redirected from the desktop view. The same access rules apply: recruiting staff and anyone holding the manager role or higher can open it. ## 6. More help - **Talent Hub FAQ** — specific setup, operating, and troubleshooting questions - **Job Board**, **Interview Scheduler**, **Offer Manager** — the apps whose data Talent Hub reports on - Ask AI — the assistant answers questions about Talent Hub from these articles. **Keywords:** talent hub, recruiting dashboard, recruiting analytics, hiring pipeline, candidate pipeline, time to fill, cost per hire, EEO compliance, adverse impact, sourcing, recruiting reports, AI insights, pipeline board, talent-hub, talent_hub --- # Talent Hub FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Talent Hub — for the admin running it. # Talent Hub FAQ Answers to common setup and operating questions about Talent Hub. For what the app is and how to set it up from scratch, see the [Talent Hub Overview](/help/articles/talent_hub_app_overview). --- ## Setup ## What do I need before Talent Hub shows any data? At least one sibling recruiting app — Job Board, Interview Scheduler, or Offer Manager — must have data. Talent Hub reads their live records; it has no candidates, jobs, or offers of its own. Enable it from **Admin → Apps → All Apps → Talent Hub → Enable** (licence required), and the dashboard populates immediately from whatever recruiting data already exists. The **Sources** tab starts empty. Go to **Sources → Seed Standard Sources** to load the 28 built-in sources (Indeed, LinkedIn Jobs, employee referrals, and others across all eight categories), or create your own. ## Who can access Talent Hub? Access is open to recruiting staff — admins, HR admins, and app admins of Talent Hub, Job Board, Interview Scheduler, or Offer Manager — and to anyone holding the manager role or higher. A plain employee below manager who is not recruiting staff cannot open it. Who sees candidate names, contact details and AI scores is set separately on **Settings → Candidate data access** (default: managers and above, plus recruiting staff). Who sees the Compliance tab is set on **Settings → EEO report access** the same way. --- ## Permissions and access ## Why is the Compliance tab missing for some of my users? The Compliance tab (EEO dashboards and reports) appears for people with EEO report access: recruiting staff (admins, HR admins, and recruiting app admins) always, plus whoever **Settings → EEO report access** names — by default, anyone holding the manager role or higher. If an admin narrowed it to app admins or specific people, everyone else loses the tab. Separately, if **EEO compliance reporting** has been turned off in **Settings**, the Compliance tab disappears for everyone. ## Why can't a user export candidate data as CSV? CSV export of the candidate list requires recruiting staff: an admin, HR admin, or app admin of Talent Hub, Job Board, Interview Scheduler, or Offer Manager. Managers who can open Talent Hub can see candidates on screen (when candidate data access allows) but cannot download them. If the **Require identity verification for exports** setting is turned on, even admins must re-verify before the download begins. --- ## Day-to-day ## How does the drag-and-drop pipeline board work? The Pipeline tab shows a kanban board with one column per stage. Drag a candidate card between columns to change their status. The board enforces guardrails: 1. Dragging to **Offered** redirects to Offer Manager to create a real offer — the status does not flip on its own. 2. Dragging to **Interviews in Process** redirects to Interview Scheduler to schedule an interview, unless an interview already exists. 3. **Hired** cannot be set manually. Candidates are promoted to Hired automatically when their offer is signed. 4. Moving to **Rejected**, **Withdrawn**, or **Unsuitable** prompts for a reason. 5. Moving a candidate backwards in the pipeline (including reversing a rejection) also prompts for a reason. Each column renders up to 50 cards. The column badge shows the true total, so you still see the count even when the board is capped. ## What does the Action Center track? The Action Center on the Home tab is a prioritised to-do list drawn from live pipeline data. It surfaces: - **Day-one conversions** — new hires starting today who need an employee account (links to Onboarding Hub). - **Expiring offers** — offers expiring within 48 hours (links to Offer Manager). - **Overdue feedback** — completed interviews with no feedback submitted yet. - **Stalled candidates** — candidates with no activity for 14 or more days (see below). - **Ready for preboarding** — accepted offers ready to begin preboarding. Items are sorted by urgency (day-one conversions and expiring offers first). ## What counts as a stalled candidate? A candidate in any non-terminal stage (not Hired, Rejected, Withdrawn, or Unsuitable) with no activity — a stage move, edit, note, call or email — for **14 or more days**. Stalled candidates are badged on the Candidates tab, listed in the Action Center, and trigger automatic nudge notifications — except while their offer awaits their answer or an approval and Offer Manager's automated reminders are on, or once their job is closed or filled. The daily nudge goes to whoever sourced the candidate — or, if nobody sourced them or that person has left, the job's recruiter and hiring manager, else the job's creator. Each recipient gets at most **1 nudge every 7 days** and at most **3 nudges per stall** (activity on the candidate starts a new count). After **60 days** of inactivity the candidate ages out of the sweep entirely — at that point they should be rejected or archived, not nudged again. ## How do I schedule a recurring report? Open **Reports** and click **Schedule delivery**, then create a schedule. You choose: - **Report type** — any of eight types (Executive Summary, Hiring Manager, Sourcing Effectiveness, Diversity Analytics, Compliance, Pipeline Analytics, Performance Analytics, Trends Analysis). - **Cadence** — Weekly, Monthly, or Quarterly. - **Format** — PDF or CSV. - **Reporting window** — Last 7 days, 30 days, 90 days, 6 months, or 12 months (how far back each run covers). - **Recipients** — people who are members of your workspace. The Diversity Analytics and Compliance types only go to people with EEO report access. Only recruiting staff (admins, HR admins, and recruiting app admins) can create or edit report schedules. ## What date ranges can I use for analytics and reports? On-demand analytics support these preset ranges: **7 days, 30 days, 90 days, 6 months, and 1 year**. You can also enter custom start and end dates. Comparison windows are available for previous period and previous year. The Home tab defaults to 30 days; Source Analytics defaults to 90 days. ## Who can see candidate data and reports? Recruiting staff — admins, HR admins, and app admins of Talent Hub, Job Board, Offer Manager, or Interview Scheduler — always see candidate data and reports. Anyone else who can open Talent Hub (the manager role or higher) sees candidate names, contact details and AI scores only when **Settings → Candidate data access** includes them (default: managers and above); without it they still see jobs and analytics. Settings are for recruiting staff only. The **Diversity Analytics** and **Compliance** report types require EEO report access (**Settings → EEO report access**, default managers and above, plus recruiting staff). CSV export of the candidate list, managing sources, and changing settings require recruiting staff. ## Can I filter analytics by department, source, or date range? Yes. The pipeline and analytics views support filtering by department, recruiter, source, job, and date range. Reports accept the same department, job-type, and source filters alongside the date range. The pipeline board also supports search by candidate name or email and a toggle to include terminal stages. --- ## When something looks wrong ## Why can't I see the pipeline or any candidate data? Either you cannot open Talent Hub at all — you need the manager role or higher, or to be recruiting staff (an admin, HR admin, or app admin of Talent Hub, Job Board, Interview Scheduler, or Offer Manager) — or your admin has narrowed **Settings → Candidate data access** so it no longer includes you. Ask an admin to check both. ## Why did the AI Insights tab disappear? The AI Insights tab is hidden when the **AI Insights** setting is turned off. Go to **Settings** (recruiting staff) and confirm that **AI insights** is toggled on. The setting defaults to on for newly enabled tenants, but an admin may have turned it off. ## I dragged a candidate to "Hired" but nothing happened — why? The **Hired** status cannot be set from the pipeline board. Candidates move to Hired automatically when their offer is signed in Offer Manager, or when someone working the offer opens it in Offer Manager and clicks **Mark as hired** — which is offered once the offer is accepted. If the candidate's offer is not accepted yet, record the candidate's answer on the offer first. ## My scheduled report didn't arrive — what should I check? Check these in order: 1. The schedule must be **active** (not paused) and its next-run date must have come. Reports go out at 6 AM in your company's time zone on that date — or within the hour, if you set or edit a schedule for today after 6 AM. A run that sent nothing is tried again at the next 6 AM. 2. The recipient must still be an active member of the workspace and still allowed that report — a person who was deactivated, left, or lost EEO report access is skipped. 3. The report type must still be enabled in Settings (the Executive Summary and Hiring Manager report types each have their own toggle, and Diversity Analytics and Compliance Report stop while **EEO compliance reporting** is off). Report schedules are managed from **Reports → Schedule delivery** (recruiting staff only). ## A candidate has been sitting untouched for weeks — does anyone get notified? Yes, while **Stalled-candidate nudge emails** is on in Settings. A daily background process detects candidates in a non-terminal stage who have had no activity (a stage move, edit, note, call or email) for 14 or more days. It sends whoever sourced the candidate — or, if nobody sourced them or that person has left, the job's recruiter and hiring manager, else the job's creator — an in-app notification and an email. Each recipient gets at most one nudge every 7 days and at most 3 per stall. After 60 days of inactivity the candidate stops being swept — they should be closed out. Candidates on a closed or filled job, or with an offer awaiting the candidate's answer or an approval while Offer Manager's automated reminders are on, are not nudged. --- ## Licensing and limits ## Does Talent Hub require a licence? Yes. Talent Hub requires a licence and is off by default. An admin enables it for the whole business from Admin → Apps → All Apps. There is no free tier and no per-seat licensing — the licence covers the business. ## What are the limits I should know about? | Item | Limit | |---|---| | Pipeline board cards per column | 50 (column badge shows true total) | | Stalled-candidate threshold | 14 days without activity | | Stalled-candidate nudge interval | At most 1 every 7 days | | Stalled-candidate nudge cap | 3 per recipient per stall | | Stalled-candidate scan window | 60 days (longer = aged out) | | Expiring-offer action-center window | 48 hours | | Scheduled report window | Last 7, 30 or 90 days, 6 months, or 12 months | | Scheduled report cadences | Weekly, Monthly, Quarterly | | Report export formats | PDF, CSV | | Source name length | 100 characters | | Source slug length | 50 characters | | Source categories | 8 (Job Board, Social Media, Referral, Direct, Agency, Event, Passive Sourcing, Other) | | Standard built-in sources | 28 | | Source cost models | CPC, CPA, Flat Fee, Monthly | | AI Insights cache duration | 30 minutes | | Adverse-impact rule | Four-fifths (80%) per EEOC guidelines | --- ## More help - [Talent Hub Overview](/help/articles/talent_hub_app_overview) - Job Board, Interview Scheduler, Offer Manager — the apps whose data Talent Hub reports on - Ask AI — the assistant answers Talent Hub questions from these articles. **Keywords:** faq, talent hub, recruiting dashboard, pipeline board, candidate pipeline, stalled candidate, time to fill, cost per hire, EEO compliance, adverse impact, sourcing, recruiting reports, AI insights, not showing, permissions, export, talent-hub, talent_hub --- # Tasks App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run the Tasks app — assigning, tracking, and verifying work across your organization. # Tasks ## 1. What it is Tasks lets you create, assign, and track work across your organization — from one-off follow-ups to recurring checklists with photo proof and manager verification. Managers assign tasks to employees; employees see their own list and mark items complete. - **Enablement:** Tasks requires a licence. An admin enables it in Admin → Apps → All Apps, then configures it at **Apps → Tasks → Settings**. - **What it is not:** Tasks is not the same as workspace todos. Workspaces have their own lightweight task lists scoped to that workspace. The Tasks app is the org-wide surface for assigned, tracked, and reported-on work. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Tasks**, and enable it. 2. Go to **Apps → Tasks → Settings** to configure permissions and notifications. At minimum, decide whether employees can create their own tasks (**Allow employees to self-assign tasks** — on by default) and whether managers can assign tasks to others (**Allow all managers to assign tasks** — on by default). 3. Optionally create task templates at **Apps → Tasks → Templates**. Templates are reusable blueprints — a checklist task with specific items, a priority, an estimated duration, and an assignment rule. You can also load industry-specific default templates from the template library. 4. To restrict which employees see the app, use **Access Management** on the app's marketplace entry. Users outside the audience cannot reach any Tasks surface, even by direct URL. 5. Confirm it worked: navigate to **Apps → Tasks**. Managers should see the **Manage** and **Analytics** tabs. Employees should see **My Tasks**. Note: if you enable task verification or compliance reporting, those are off by default and must be turned on explicitly in Settings — they do nothing until activated. ## 3. How it fits together **Tasks vs workspace todos.** Both are task records, but they live in different places and serve different purposes. An org-level task belongs to the Tasks app: it appears in **My Tasks**, shows up in analytics, and can be escalated, verified, and reported on. A workspace todo belongs to a workspace task list, appears on the workspace canvas, and is managed by workspace contributors. Workspace todos do not appear in the Tasks app's analytics or digest emails. **Simple tasks vs checklist tasks.** A simple task has a title, a description, and a due date. A checklist task adds a list of items that must each be completed — optionally with photo proof or notes required per item. When the last checklist item is ticked, the task completes automatically. **Priorities.** When the priority system is enabled (it is by default), every task carries one of three levels: **Normal**, **Important**, or **Critical**. Automatic overdue escalation can be limited to Critical tasks, and Critical tasks can be texted to the assignee. If you turn the priority system off, the priority column and filters disappear from all views. **Subtasks.** Any task can have child tasks. Subtasks inherit the parent's assignee by default. The **Group subtasks and parent tasks on list and Kanban view** setting controls whether subtasks appear directly below their parent on the board and list views or sort independently. **Recurring tasks.** A task can repeat on a **Daily** (every few days, or weekdays only), **Weekly** (on chosen days), or **Monthly** (every few months, such as quarterly) cadence. The system creates the next occurrence automatically. Recurring tasks can also be created from templates with a recurrence pattern. The **Per Shift (no automatic repeat)** option creates a single task — nothing re-creates it per shift. **Templates.** Templates are reusable task blueprints an admin or manager creates once. A template defines the title, type, priority, checklist items, assignment type (**Manual**, **Role-based**, or **Auto**), estimated duration, and recurrence. Templates can be activated, deactivated, duplicated, and loaded from an industry-specific gallery. **Escalation.** A task can be escalated manually by a manager or automatically when overdue. A manual escalation goes to the assignee's manager (or the person who assigned the task, as a fallback). Employees can also flag a task as blocked using the **I'm blocked** button, which escalates it to their manager. The automatic overdue escalation (off by default) notifies the assignee's manager and the managers at the task's location, plus the recipient group if you picked one; a task with no manager to tell goes to that group, or else to the Tasks app administrators. **Verification.** When manager verification is enabled, completing a task does not close the loop — a manager must separately verify the work. With verification on you can also require a photo and completion notes when a task is completed, and require that someone other than the person who completed it does the verifying. ## 4. Running it ### Assigning tasks 1. Go to **Apps → Tasks → Manage** and click **New Task** (or use the quick-create drawer). 2. Fill in the title, assign to a user, set a due date, and choose a priority. 3. For checklist tasks, add items — each item can require a photo or notes. 4. To assign from a template, use **Create from Template**, pick a template, and select the users. When smart assignment is enabled, leaving the assignee blank lets the system pick the least-loaded eligible user, with a preference for users at the task's location. ### Reviewing completed work Completed tasks appear in the **Manage** view filtered to **Completed** status. If verification is enabled, managers see a **Verify Task** action on completed tasks that have not yet been verified. The **Analytics** tab shows completion rates, on-time percentages, and top performers. ### Managing templates Go to **Apps → Tasks → Templates**. Admins can create, edit, activate, deactivate, duplicate, and delete templates. The **Who can create & edit task templates** setting controls whether managers also have access (default: **Administrators only**). You can load industry defaults for Healthcare, Retail, Manufacturing, Hospitality, and seven other industries. ### Viewing analytics Go to **Apps → Tasks → Analytics** (managers, admins, and Tasks app administrators). The dashboard shows completion rate, average completion time, overdue rate, status and priority distribution, a completion trend chart, weekly performance, top performers, and efficiency metrics. Data can be filtered to the last 7, 30, or 90 days, or the last 12 months, and exported as CSV. Cancelled tasks are left out of Total Tasks and the rates, and the overdue count is every task past due right now, whatever the period. When compliance reporting is enabled, a separate compliance export includes verification status and completion evidence — including whether verification was required when each task was completed ("Not recorded" for tasks completed before October 2026). Employees see their own analytics at **Apps → Tasks → My Analytics** with a personal scorecard. ### Delegating tasks When delegation is enabled in Settings, an employee can delegate their assigned task to another team member from the task detail view. The task is reassigned and a delegation activity is logged. ### Mobile The Tasks app has a dedicated mobile view. Employees can see their pending, in-progress, and overdue tasks, start and complete tasks, tick checklist items (including photo capture for photo-required items), and add notes. Task creation on mobile is limited to simple tasks. ## 5. Settings All settings are at **Apps → Tasks → Settings**. Business administrators and Tasks app administrators can reach this page. ### Tasks Agent | Setting | Default | What it changes | |---|---|---| | Tasks Agent | On | Lets users create, assign, and track tasks in Ask AI and the in-app AI Task Assistant. Off also removes the AI describe-to-fill box from task forms and AI suggestions from the template picker | ### Permission Settings | Setting | Default | What it changes | |---|---|---| | Allow all managers to assign tasks | On | When off, only admins can assign or reassign tasks (unless **Who can create tasks for other people** is **Everyone**), and a manager can no longer cancel, reopen, or escalate a task they neither assigned nor are assigned to | | Allow employees to self-assign tasks | On | When off, employees can't create tasks for themselves | | Allow task delegation to other team members | Off | Lets employees delegate their tasks to a colleague | | Who can create tasks for other people | **Managers and administrators** | Also accepts **Everyone with access to Tasks** — any employee can then assign a task to any colleague who can use Tasks | | Who can create & edit task templates | **Administrators only** | Also accepts **Managers and administrators** | ### Notification Settings | Setting | Default | What it changes | |---|---|---| | Send notifications when tasks are assigned | On | Notifies the assignee immediately | | Send due date reminders | On | Reminder before the due date | | Tell the assigner when their task is completed | On | Completion notice to the person who assigned the task (verification requests follow the verification setting) | | Tell people when a task they're on changes | On | Notices when a task is cancelled, reopened, or its due date moves | | Notify participants about new comments | On | In-app only — comments never send email | | Notify the escalation target when someone escalates a task | On | Covers a manager clicking **Escalate** and an assignee raising a blocker | | Send task notifications by email | On | Email for assignments, reminders, overdue notices, escalations, completions, verification requests, cancelled and reopened tasks, moved due dates, and the daily digests. When off, notifications stay in-app | | Send SMS for critical tasks | Off | Texts the assignee when a Critical task is assigned to them or goes overdue; needs SMS set up for your organization. Escalations are not texted | | Send reminders this many hours before due date | **2 hours before** | Choices: 1, 2, 4, 8, 24, or 48 hours | | Escalate overdue tasks to managers | Off | An hourly sweep notifies the managers once a task has been overdue for the delay below; each task is escalated once | | Only escalate Critical-priority tasks | Off | Shown under overdue escalation. Off, every overdue task is escalated; on, only Critical tasks (needs the priority system) | | Escalate after a task has been overdue for | **1 hour** | Shown under overdue escalation; applies to every automatic escalation. Choices: 15 min, 30 min, 1 hour, 2 hours, 4 hours | | Send escalations & verification requests to this group | None | Shown while overdue escalation or manager verification is on. Notifies the group's members as well as the task's managers, and in place of the Tasks app administrators when a task has no manager | ### Priority System | Setting | Default | What it changes | |---|---|---| | Enable task priority system | On | Shows Normal, Important, and Critical levels throughout the app | ### Team Tasks | Setting | Default | What it changes | |---|---|---| | Show a Team Tasks page | Off | People see the open tasks of everyone who reports to the same manager as they do | | What teammates can do on each other's tasks | **View only** | Also **View and comment** or **View, comment and edit**; the assignee and their manager keep full control | ### Task Completion | Setting | Default | What it changes | |---|---|---| | Enable manager verification | Off | Adds a verification step after task completion | | Require photo verification for task completion | Off | Sub-setting of verification — requires a photo | | Require completion notes | Off | Sub-setting of verification — requires notes | | Require a different person to verify | Off | Sub-setting of verification — whoever completed a task can't also verify it | | Auto-archive completed tasks | Off | Hides old completed and cancelled tasks from active views | | Archive completed tasks after | **30 days** | Choices: 7, 14, 30, 60, or 90 days | ### Assignment Rules | Setting | Default | What it changes | |---|---|---| | Enable smart task assignment | Off | Auto-picks the least-loaded eligible user when no assignee is specified | | Maximum concurrent tasks per user | **No limit** | Caps active (pending + in-progress + overdue) tasks per person; choices: 3, 5, 10, 15, or 20 | ### Analytics & Reporting | Setting | Default | What it changes | |---|---|---| | Enable performance tracking | On | Shows the named Top Performers ranking on the Tasks dashboard, Task Analytics, and the managers' daily digest | | Send daily task digest to managers | Off | Daily email with team completion rates and overdue tasks | | Send employees their own daily digest | Off | Daily email with the employee's tasks due today and overdue | | Daily digest send time | **8:00 AM** | Choices: 6 AM, 8 AM, 9 AM, 12 PM, 5 PM, or 6 PM in your organization's time zone (UTC if none is set) | | Enable compliance reporting | Off | Adds a **Compliance Report (CSV)** export to the Task Analytics menu | ### Board & List Display | Setting | Default | What it changes | |---|---|---| | Group subtasks and parent tasks on list and Kanban view | Off | Sorts subtasks directly below their parent instead of newest-first | ## 6. More help - **Tasks App FAQ** — specific setup, limits, and operating questions. - Ask AI — the assistant answers questions about Tasks from these articles. **Keywords:** tasks, task management, assign tasks, task templates, checklist, recurring tasks, task delegation, task analytics, overdue tasks, task verification, subtasks --- # Tasks FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Tasks — for the admin running it. # Tasks FAQ Answers to common setup and operating questions about Tasks. For what the app is and how to set it up from scratch, see the [Tasks Overview](/help/articles/tasks_app_overview). --- ## Setup ## Do I need to configure anything before tasks start working? Enable the Tasks app from Admin → Apps → All Apps — it is disabled by default and requires a licence. Once enabled, the defaults let managers and admins create, assign, and complete tasks immediately. Optional features — smart assignment, SMS alerts, daily digests, overdue escalation, and completion verification — are all off by default and must be turned on in the Tasks settings page. Recurring tasks need no setting: any task or template can be set to repeat. ## Who can access which parts of Tasks? There are four levels of access: 1. **Admins and super admins** can do everything, including deleting tasks, managing templates, accessing analytics, importing tasks, and changing settings. 2. **Tasks app administrators** (designated per user in Admin → Apps → All Apps) have the same capabilities as admins, including changing settings. An HR admin role on its own adds nothing in Tasks — HR admins get the access of their admin, manager, or employee role. 3. **Managers** can create and assign tasks (when the **Allow all managers to assign tasks** setting is on, which it is by default), and can view team analytics for their locations and reporting line. Whether managers can author templates depends on the **Who can create & edit task templates** setting — the default is **Administrators only**. 4. **Employees** can view and work on their own assigned tasks in the My Tasks view, create personal tasks (when **Allow employees to self-assign tasks** is on, which it is by default), and see their personal analytics. When **Who can create tasks for other people** is set to **Everyone with access to Tasks**, employees can also assign tasks to colleagues. --- ## Permissions and access ## Why can't a manager assign tasks to other people? The **Allow all managers to assign tasks** setting is on by default, but an admin may have turned it off. When off, only admins and Tasks app administrators can assign (unless **Who can create tasks for other people** is set to **Everyone with access to Tasks**), and a manager can't cancel, reopen, or escalate a task they neither assigned nor are assigned to. Check the Tasks settings page under **Permission Settings** and re-enable it if needed. The error message the manager sees is: "Only administrators can assign tasks. An admin can enable manager assignment in Tasks settings." ## Why can't a manager create or edit templates? Template management is controlled by the **Who can create & edit task templates** setting, which defaults to **Administrators only**. Change it to **Managers and administrators** in the Tasks settings page under **Permission Settings** to let managers author and edit templates. ## Can employees create their own tasks? Yes, when the **Allow employees to self-assign tasks** setting is on (the default). When off, employees can't create tasks for themselves; they can still create tasks for colleagues if **Who can create tasks for other people** is set to **Everyone with access to Tasks**. Employees always see and work on tasks assigned to them, regardless of this setting. --- ## Day-to-day ## How do recurring tasks work? Set a task's or template's recurrence to **Daily** (every few days, or weekdays only), **Weekly** (on chosen days, every few weeks), or **Monthly** (every few months, such as quarterly). A background job runs every 15 minutes, checks for recurring tasks whose next occurrence is due, and creates a new task instance from the parent — copying its fields and checklist items, for the same assignee while they are still active. The **Per Shift (no automatic repeat)** option creates a single task; nothing re-creates it per shift. The original task stays open as the recurring parent; each generated instance is independent and tracks its own status. ## How does smart assignment decide who gets the task? When **Enable smart task assignment** is turned on in settings (off by default), a new task with no explicit assignee is routed to the person with the fewest active tasks (pending, in-progress, or overdue). If the task has a location, users who have been assigned tasks at that location are preferred. If you set a **Maximum concurrent tasks per user** cap (options: 3, 5, 10, 15, or 20), anyone at or above the cap is skipped. If no one has capacity, the task stays unassigned. ## What can the AI Tasks agent do? From Ask AI, in plain language, the agent can list your tasks (or, for a manager, the whole business's or one named person's), find a task from a description of it, count tasks by status, priority, location, assignee or category, show a task's full detail, list the task templates (managers), and create, assign, update, complete, cancel, reopen and escalate tasks. Every answer links the task's page. A task you create for **yourself** is created at once. Every other change — a task created for someone else, an assignment, an edit, a status change, a completion, and cancelling, reopening or escalating — shows what will change and waits for you to confirm. Reading needs no confirmation. The agent follows the same permission rules as the Tasks pages: employees act only on their own tasks, assigning to others needs the manager/admin permission, and cancelling, reopening and escalating are for managers and Tasks administrators (an employee can still cancel their own task). Ask AI cannot delete tasks — see below. An admin can turn the agent off entirely from the **Tasks Agent** card in Tasks settings. ## Can I delete a task? Yes, if it is a to-do you created for yourself, or you are an administrator or Tasks app administrator. A task someone assigned — even one you assigned to someone else — can only be deleted by an administrator. Open the task and delete it, or delete several at once from **My Tasks** in the **List** view: tick the tasks and choose **Delete** (tasks someone else assigned to you are skipped). Administrators and Tasks app administrators can also switch the **Manage** board to **Table**, tick tasks, choose **Delete Selected** and click **Apply**. Deleting cannot be undone. If you only want a task off your list, ask Ask AI to cancel it, or ask your manager to. Ask AI does not delete tasks. ## Can I delegate a task to someone else? Yes, if the admin has enabled the **Allow task delegation** setting (off by default) in the **Permission Settings** card. When enabled, an assignee can delegate their task to another team member from the task detail view. Completed and cancelled tasks cannot be delegated. ## What happens when a task is escalated? When a task is escalated it is flagged and the escalation reason is recorded. A manual escalation (or an assignee's **I'm blocked**) notifies the assignee's manager, or the person who assigned the task if no manager is set, by in-app notification and email — governed by **Notify the escalation target when someone escalates a task**. Automatic escalation is a separate setting: turn on **Escalate overdue tasks to managers** and choose how long a task must be overdue first (15 minutes, 30 minutes, 1 hour, 2 hours, or 4 hours; default is 1 hour). It notifies the assignee's manager and the managers at the task's location, plus the group in **Send escalations & verification requests to this group** if one is picked. Every overdue task is escalated unless you also turn on **Only escalate Critical-priority tasks**. --- ## When something looks wrong ## "I completed the task but my manager says it still shows as pending" If **Enable manager verification** is turned on in settings, completing a task triggers a verification request to the manager — the task shows as completed but is separately flagged for review. The manager must verify it. This is distinct from the task status itself; check whether verification is enabled and whether the manager has a pending verification notification. ## "I can't complete this checklist task — the button is greyed out" A checklist task auto-completes only when every checklist item is checked off. If individual items require a photo or notes (set per item when the task or template was created), those must be provided before the item can be checked. Look at which items are still incomplete and whether they have a photo or notes requirement icon. ## "My employee says they can't see their tasks" Three things to check: (1) the Tasks app must be enabled for your business; (2) if you use Access Management audience rules on the Tasks app, the employee must be in the included audience; (3) for personal task creation specifically, the **Allow employees to self-assign tasks** setting must be on. ## "An overdue task didn't trigger an SMS" SMS alerts go only to the assignee of a **Critical**-priority task — when it is assigned to them and when it goes overdue (escalations are never texted) — and only when all of these are true: your business has SMS set up, **Send SMS for critical tasks** is turned on in Tasks settings (off by default), the assignee has a phone number on their profile, and they have not opted out of SMS for tasks in their notification preferences. --- ## Templates and imports ## How do industry starter templates work? Go to Templates and choose **Load Industry Defaults**. Pick from 11 industries: Healthcare, Retail, Manufacturing, Hospitality, Food & Beverage, Education, Technology, Finance, Transportation, Construction, and Professional Services. Each pack creates a set of ready-to-use templates with checklist items, priority levels, and recurrence patterns pre-filled. Existing templates with the same title and category are skipped — your customisations are never overwritten. ## Can I import tasks in bulk? Yes. The Import tab (visible to managers, admins, and Tasks app administrators) uses the Smart Import engine — upload a spreadsheet (Excel or CSV) or paste rows to create tasks in bulk. Each assignee gets one in-app notice listing the tasks imported for them (not one per task), while **Send notifications when tasks are assigned** is on in Tasks settings; due-date reminders and overdue notices follow your Tasks settings as usual. --- ## Integrations ## Can tasks be created automatically from a Forms submission? Yes. A form template can include task rules that fire when a submission reaches a specified status (submitted, approved, or rejected). Rules can evaluate field values, submitter role, department, and location. The generated task's title and description support field placeholders (e.g. `{{field_name}}`), and assignment can route to the submitter, their manager, the form owner, a department head, a location manager, a specific user, or a role-based pool. Both the Tasks app and the form's **Tasks integration** toggle must be enabled. ## How do AI Notepad meeting action items become tasks? When a meeting is processed by AI Notepad, it extracts action items. If the **Create tasks** automation is enabled, each action item becomes a task — with the attendee matched to a business user as the assignee, the action text as the title, and any mentioned deadline as the due date. Duplicate tasks for the same meeting are prevented automatically. --- ## Licensing and limits ## Does Tasks require a licence? Yes. Tasks requires a licence and is opt-in per tenant. An administrator enables it from Admin → Apps → All Apps; it is disabled by default until then. ## Are there limits I should know about? | What | Limit | |---|---| | Task title | 255 characters | | Category name | 100 characters | | Document attachment size | 10 MB per file | | Allowed document formats | PDF, Word, Excel, PowerPoint, plain text, CSV, and images (PNG, JPEG, GIF, WebP) | | Comment length | 5,000 characters | | Escalation reason | 1,000 characters | | Concurrent task cap per user | No limit, 3, 5, 10, 15, or 20 (admin-configurable) | | Auto-archive window | 7, 14, 30, 60, or 90 days after completion (default 30) | | Due-date reminder lead time | 1, 2, 4, 8, 24, or 48 hours before due (default 2) | | Digest delivery time | 6:00 AM, 8:00 AM, 9:00 AM, 12:00 PM, 5:00 PM, or 6:00 PM in your organization's time zone, or UTC if none is set (default 8:00 AM) | --- ## More help - [Tasks Overview](/help/articles/tasks_app_overview) - Ask AI — the assistant answers Tasks questions from these articles. **Keywords:** faq, task assignment, checklist, recurring task, template, smart assignment, task delegation, overdue, escalation, task permissions, completion proof, tasks --- # Time & Attendance App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-20 How to set up and run Time & Attendance — clock-in/out, verification policies, kiosks, break types, auto clock-out, and the review queue. # Time & Attendance ## 1. What it is Time & Attendance is the system of record for actual hours worked. Employees clock in and out from the web, the mobile app, or a shared time-clock kiosk. Each punch captures the time, location, and — when you require it — a photo, GPS coordinates, IP address, or device identity. Managers see a live dashboard of who is on the clock, late, or absent, and review any flagged records before hours flow into timesheets. - **Enablement:** Requires a license. An admin enables it from **Admin → Apps → All Apps**. It is not turned on automatically. - **What it is not:** Time & Attendance records *actual* hours. The *plan* — who works where and when — lives in **Shifts & Scheduling**. Leave accruals and balances live in **Leave Management**. Approved timesheets live in **Timesheets**; **Payroll Prep** turns them into gross-pay reports, and **Payroll Connect** sends them to an external payroll provider. Those are separate apps that integrate with this one. ## 2. Standing it up 1. **Enable the app** — go to **Admin → Apps → All Apps**, find **Time & Attendance**, and enable it. 2. **Set up locations** — go to **Admin → Locations**. Each punch is associated with a location. At least one location must exist before employees can clock in. If you plan to use geofencing, configure the geofence radius on each location's settings page. 3. **Create break types** — go to **Configuration → Break Types** in the app sidebar. Define the breaks your employees take — name, duration, paid or unpaid, and whether the break is required. A new break type starts at 30 minutes, unpaid and optional; tick Paid or Required when it should be. 4. **Configure attendance settings** — go to **Configuration → Attendance Settings**. Decide which verification methods to require (photo, location, device, IP), set the time-window buffers, and choose whether to require a scheduled shift for clock-in. All verification settings default to off, so the app works immediately — tighten them as you roll out. 5. **Publish the app to employees** — in the app's marketplace entry, set visibility rules to control which groups of employees can access it, then publish. Until published, only admins can reach it. 6. **Confirm it worked** — after an employee clocks in, their record appears on the manager dashboard at **Time & Attendance → Team → Team Attendance**. The employee sees their status on their own dashboard and attendance history page. **Silent dependency:** If you turn on **Require Shift Assignment for Clock-in** (off by default) without the **Shifts & Scheduling** app licensed, no employee will be able to clock in — from the web, the kiosk, or the mobile app. Leave this off unless Shifts & Scheduling is active. ## 3. How it fits together **Attendance records** — Every clock-in creates an attendance record. It tracks the clock-in time, clock-out time, break records, work mode (on-site, remote, or off-site), and any verification data (photo, GPS, IP, device fingerprint). Records start in **Pending** status and move to **On time**, **Late**, or **Completed** as the shift progresses. A scheduled shift with no clock-in becomes a **No-Show** (a missed shift), and a shift the employee reported they would miss reads **Absence Reported** — a call-out, not a no-show. Each record also notes its punch source — web, kiosk, API, hardware time clock, CSV import, or missing-punch request — so you can tell how the punch arrived. **Flagged records and the review queue** — When a punch trips a policy (suspicious IP, outside the time window, unrecognized device, location mismatch, or missing clock-out), the record is flagged for review. Managers resolve flagged records from the review queue with an outcome — approved, adjusted, excused, or rejected. The edit trail on every record shows who changed what and when. **Breaks** — Break types are defined once by the admin (paid or unpaid, duration, required or optional). When an employee is clocked in, break records are created from the applicable break types. Employees start and end breaks manually; a break that is still running at clock-out is auto-completed. **Kiosks** — A time-clock kiosk is a shared device (typically a tablet at a work site) where employees identify with an ID and PIN instead of logging in. Each kiosk is paired to a location. One active kiosk is allowed per location. Employees punch in or out at the kiosk; the kiosk records the punch against their attendance record. Kiosk passcodes are encrypted at rest, and the device enrollment uses signed cookies with a five-year expiry. **Missing-punch requests** — When an employee forgot to punch, they submit a missing-punch request with the time they actually worked. The request creates a provisional attendance record that is held for manager review. Once approved, the hours count. **Absence reports** — An employee (or manager) can report an absence against a shift. Absence reason codes — defined by the admin under **Configuration → Absence Reason Codes** — classify the absence (paid/unpaid, requires documentation, counts as an occurrence, requires manager approval). A reported absence links to the attendance record for that shift. **Work modes** — Each punch carries a work mode: **On-site** (the default), **Remote**, or **Off-site**. Remote and off-site options only appear if the admin enables them (see Settings). Remote and off-site punches still record GPS and IP for the audit trail, but they skip geofence checks and are excluded from "who is in the building" counts. The work mode appears on the attendance record and in reports. **Timesheet sync** — Every clock-in, clock-out, and time adjustment automatically syncs into the corresponding timesheet entry in the **Timesheets** app. Attendance is the single writer; the timesheet is the downstream consumer. Managers approve timesheets, not individual punch records — but a flagged punch blocks clean timesheet approval until it is resolved. **Hardware time clocks** — External clock devices (badge readers, biometric terminals) push punch data to Time & Attendance via an HMAC-verified webhook. The system resolves each punch to an employee, matches it to a shift, and creates the attendance record. These punches appear with a "time clock" source so you can distinguish them from web or kiosk punches. ## 4. Running it ### Reviewing flagged records 1. Go to **Time & Attendance → Team → Team Attendance**. Records needing review appear under **Attendance Records Requiring Review**; **View All Records** opens the full **Requires Review** list. 2. Open a flagged record. The flags show what triggered review — suspicious IP, outside time window, unknown device, or missing clock-out. 3. Choose an outcome: approve, adjust the times, excuse the absence, or reject. Add notes if needed. 4. The employee is notified of the decision, and the timesheet entry updates to match. ### Managing who is on the clock Go to **Time & Attendance → Team → Currently Clocked In** to see a live roster of everyone on the clock, with their shift, location, and elapsed hours. **Time & Attendance → Team → No-Shows** lists employees with a scheduled shift who have not clocked in. ### Correcting someone's punch while they are on the clock Go to **Time & Attendance → Team → Currently Clocked In** and choose **Adjust Times** on the employee's row. Change the check-in time, or set a check-out time to clock them out, and add a note. A manager cannot adjust their own punch — they file a missing-punch request instead. ### Setting up a kiosk 1. Enable **Kiosk mode (whole organization)** in **Configuration → Attendance Settings** (under **Time Clock Kiosk**). It applies to every location, and it refuses punches from personal devices — the web and the mobile app included — so employees clock in and out only at a kiosk. 2. Go to **Time Clock Kiosks** (linked from the same settings page) and create a kiosk session for a location. The system generates a pairing code. 3. On the shared tablet, navigate to the kiosk URL and enter the pairing code. The device is enrolled and the kiosk is live. Only one active kiosk is allowed per location. 4. To regenerate all pairing codes at once, use **Bulk Update Pairing Codes**. ### Configuring notification rules Go to **Configuration → Notification Rules**. Create rules for events like missed clock-in, missed clock-out, late clock-in, consecutive late arrivals, suspicious activity, or location mismatch. Each rule sets a severity, delivery method (in-app with mobile push, email, or SMS), and recipients (the employee, their manager, both, all admins, or specific users). ### Importing and exporting attendance data Go to **Admin → Import / Export** in the app sidebar. On the **Import** tab, import attendance records from CSV or Excel (up to 5,000 rows, 10 MB). On the **Export** tab, download attendance records as CSV on demand. On the **Scheduled transfers** tab, schedule recurring SFTP imports or exports to move hours to your payroll vendor. An export with IP address, location and device columns, for investigations, is under **Admin → Analytics**. ### Viewing analytics Go to **Admin → Analytics** for aggregated charts and reports — hours by department, tardiness trends, and absence patterns. Data can be exported to CSV. ## 5. Settings All settings below are at **Configuration → Attendance Settings** unless noted otherwise. | Setting | Default | What it changes | |---|---|---| | **Enforce Time Window Restrictions** | On | When on, a clock-in is accepted from the Early Clock-in Buffer before the shift starts until the shift ends, and punches outside the buffers are flagged for review. When off, a clock-in is accepted from 2 hours before the shift starts. | | **Early Clock-in Buffer** | 15 minutes | How far before a shift's start an employee can clock in. | | **Late Clock-in Buffer** | 30 minutes | Grace period: a clock-in up to this many minutes after the shift starts counts as on time; later clock-ins are still accepted until the shift ends, but are marked late. | | **Late Clock-out Buffer** | 30 minutes | How far after a shift's end clock-out is accepted before being flagged. | | **Require Shift Assignment for Clock-in** | Off | When on, only employees with a scheduled shift can clock in. When off, the system creates an ad-hoc shift automatically. | | **Allow Remote (Work From Home) Clock-in** | Off | Adds a "Working remotely" option that skips geofence checks but still records GPS/IP. | | **Allow Off-Site / Traveling Clock-in** | Off | Adds an "Off-site / traveling" option with an optional note. Remote and off-site punches are excluded from "who is in the building" counts. | | **Require Clock-in Before Using the Intranet** | Off | Gates intranet access until the employee clocks in. Two modes: **Block** (redirect) or **Banner** (persistent reminder). Admins and employees on approved leave are always exempt. | | **Enable Automatic Clock-Out** | On | Automatically clocks out employees who exceed the configured thresholds. All auto clock-outs are flagged for manager review. | | **Maximum Hours Before Auto Clock-Out** | 12 hours | Absolute cap — clock out after this many hours regardless of shift schedule. | | **Minutes After Shift End** | 30 minutes | For scheduled shifts, auto clock-out this many minutes past the shift end time. | | **Send Clock-Out Reminders** | On | Sends a notification before shift end so employees remember to clock out. Works independently of automatic clock-out. | | **Clock-Out Reminder Lead Time** | 5 minutes | How far before shift end the reminder is sent. | | **Enforce IP Validation** | Off | Validates punch IP addresses against approved ranges. Three modes: **Passive** (monitor only), **Warning** (flag for review), or **Strict** (block unapproved IPs). Approved IP ranges are managed per location. | | **Require Photo Verification** | Off | Asks employees to take a photo at clock-in/out. Employees who cannot use the camera can continue without one — those punches are flagged for manager review rather than blocked. | | **Require Location Verification** | Off | Master switch for GPS verification. Each location must also have geofencing enabled in its own settings for enforcement to take effect. | | **Require Device Verification** | Off | A punch from a device the employee has not used before is accepted and flagged once for review; that device is trusted after it. | **Kiosk settings** (same page, under **Time Clock Kiosk**): | Setting | Default | What it changes | |---|---|---| | **Kiosk mode (whole organization)** | Off | When on, for every location, employees see their kiosk ID and PIN card instead of the personal clock-in widget, and punches from personal devices (web and mobile app) are refused. This does not create the kiosk itself — kiosks are created under **Time Clock Kiosks**. | | **Employee Identifier** | Mango ID | What employees enter at the kiosk to identify themselves: **Mango ID** or **External Employee ID**. | | **Default PIN** | None (employee must set a personal PIN) | The fallback PIN for employees who have not set their own. Choices: last 4 of the employee identifier, last 4 of external employee ID, date of birth (MMDD), a shared PIN for everyone, or none. | **Who Can See What** (same page): | Setting | Default | What it changes | |---|---|---| | **Who can see attendance records across the whole organization?** | App admins only | Controls organization-wide visibility. Managers always see their direct reports and anyone at their held locations. This setting decides who *also* sees everyone else. Options: **App admins only**, **All managers**, or **Specific people**. | ## 6. More help - **Time & Attendance FAQ** — specific setup and operating questions, limits, and troubleshooting. - **Shifts & Scheduling App Overview** — building the schedule that Time & Attendance tracks against. - **Timesheets App Overview** — where approved hours go after attendance is recorded. - Ask AI — the assistant answers questions about Time & Attendance from these articles. **Keywords:** time and attendance, clock in, clock out, punch, time clock, kiosk, attendance, break tracking, auto clock-out, missing punch, photo verification, geofencing, attendance review, absence report, buddy punching, time window, time-attendance, time_attendance, time-&-attendance --- # Time & Attendance FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-20 Answers to common setup and operating questions about Time & Attendance — for the admin running it. # Time & Attendance FAQ Answers to common setup and operating questions about Time & Attendance. For what the app is and how to set it up from scratch, see the [Time & Attendance Overview](/help/articles/time_attendance_app_overview). --- ## Setup ## Do I need Shifts & Scheduling before Time & Attendance works? Not necessarily. By default, employees can clock in without a scheduled shift — the system creates an ad-hoc shift at the moment they punch. If you want to require a scheduled shift before anyone can clock in, turn on **Require Shift for Clock-In** in Admin → Attendance Settings. That setting is off by default because Shifts & Scheduling is a separate licence. ## Who can see attendance records once I turn the app on? Every employee sees their own clock history. Managers see records for their direct reports and for employees at locations they are assigned to. The **View All Attendance** capability (configurable in the app's authorization settings) controls who sees records beyond their own authority — the default is **App Admins** (business admins plus anyone you delegate as a Time & Attendance app administrator). You can widen it to **Managers** or restrict it to **Specific** users. --- ## Permissions and access ## Why can't our Time & Attendance app administrator see all records? Check two things. First, the person must be granted the Time & Attendance app-admin role under **Apps → Time & Attendance → Admins & Contributors** — a business admin or super admin has it automatically, but a delegated app-admin needs the explicit grant. Second, the **View All Attendance** capability must be set to **App Admins** (the default) or **Managers**. If it is set to **Specific** users, only the named individuals see records outside their own reporting chain. ## Who can clock in on behalf of an employee? Managers and admins can add a manual record or clock someone in from the manager dashboard. Managers can do this for their direct and indirect reports and for employees assigned to their locations, but never for themselves. Admins can add a record for any employee in the business. --- ## Day-to-day ## How does the system decide whether someone is late? It compares the clock-in timestamp against the scheduled shift start plus the late grace period. The default grace period is **30 minutes** (admin-configurable in Attendance Settings). A punch within the grace period is on-time; a punch after it is late. Ad-hoc shifts — created when no scheduled shift exists — are always treated as on-time. A tardiness that rounds to less than one full minute is also treated as on-time, so employees are never flagged "late by 0 minutes." ## What happens when an employee forgets to clock in or out? They can submit a missing-punch request from the Time & Attendance app with the correct clock-in and clock-out times, any breaks taken, and a reason (5–1,000 characters). The request must fall within the retroactive window, which follows the **Timesheet Lockout Days** setting (default **7 days**). It routes to the employee's manager for review and is never auto-approved. A single missing-punch request cannot span more than **24 hours**. ## What does auto clock-out do, and when does it fire? Auto clock-out closes forgotten punches automatically so they do not stay open indefinitely. It has two rules, both on by default for new tenants: 1. **After shift end** — closes a scheduled punch after the configured number of minutes past the shift's end time. Default: **30 minutes** (admin-configurable, max 480). 2. **Maximum hours** — closes any open punch that has been running longer than the configured limit. Default: **12 hours** (admin-configurable, max 24). A stale punch left open beyond **24 hours** is closed by the system regardless of these settings. Every auto-closed punch is flagged for manager review. ## How are meal and rest breaks tracked? When an employee clocks in, the system automatically creates a break record for each break type your business has marked as **Required**. A new break type defaults to **30 minutes**, **unpaid** and **optional**. Paid break time stays in payable hours; unpaid break time is subtracted. If an employee ends a required break short of its configured duration, the record is flagged for manager review. Any break still in progress when the employee clocks out is auto-completed at the clock-out time. ## What is the difference between Time & Attendance and Timesheets? Time & Attendance records discrete clock events — each clock-in and clock-out is a record with a status (on-time, late, or missed), a punch source, and verification data. Timesheets aggregate those events into pay-period hours for review and approval. Every clock event, including breaks, syncs into the matching timesheet in real time, where hours roll up into overtime, double-time, and premium-pay totals. In short: attendance answers "when did they punch and was it valid?"; timesheets answer "how many payable hours this period, ready to approve?" --- ## When something looks wrong ## "I clocked in but it says I'm a no-show" This happens when the no-show detector ran before the employee punched. If the employee then clocks in (for example through the kiosk's grace window), the no-show flag is automatically cleared and the record is reclassified as on-time or late based on the actual punch time. If the flag persists, a manager can review and approve the record from the Requires Review queue. ## "I can't clock in — it says the clock-in window is closed" The employee is outside the allowed window. With **Enforce Time Window Restrictions** on, clock-in is allowed from the **Early Clock-In Buffer** (default **15 minutes**) before shift start until the shift ends; after the shift ends, the window closes. With it off, clock-in is allowed from **2 hours** before shift start, with no end. Ad-hoc shifts (no scheduled shift) are not subject to either rule. If this is a legitimate late arrival, a manager can add a manual record. ## "My punch was flagged for review — what triggered it?" A punch is flagged when any verification check fails. The review reason appears on the record and can include: - **Suspicious IP address** — the punch came from an IP not on the allowed list (when IP validation is enabled) - **Outside allowed time window** — punched outside the early/late buffer - **Unknown device** — device fingerprint not previously seen for this employee (when device verification is enabled) - **Location verification failed** — GPS coordinates outside the location's geofence radius (when location verification is enabled) - **Photo verification failed** — no photo provided or camera unavailable (when photo verification is required) ## Why did a manager correction not show up in the timesheet? Check whether the correction was saved successfully — the manager should see a confirmation. Clock-in and clock-out time changes sync to the timesheet automatically. If the adjustment involved a missing-punch request, it must be approved with a positive outcome (Approved, Adjusted, Time Corrected, Location Accepted, Tardiness Accepted, or Security Verified) before hours appear on the timesheet. Rejected, Unexcused Absence, and Excused Absence outcomes do not promote hours. --- ## Clock-in methods and security ## What are the three IP validation modes? IP validation must first be turned on with the **Enforce IP Validation for Clock Actions** toggle in Attendance Settings. Once on, you choose a mode: - **Passive** — IP addresses are recorded but no restriction is enforced. - **Warning** (default) — punches from unauthorized IPs are flagged for manager review but still accepted. - **Strict** — punches from unauthorized IPs are blocked entirely. When GPS coordinates are not available, the system falls back to IP-based geolocation for location verification. ## How does the kiosk PIN lockout work? The kiosk locks out after **5 failed PIN attempts** per device for **5 minutes**. A broader lockout triggers after **20 failed attempts** across all devices on that kiosk for **10 minutes**. Pairing-code guessing is also limited: **10 failed attempts** per code lock out for **10 minutes**, and **50 failed attempts** across a whole business lock out for **10 minutes**. Lockouts decay automatically — no admin action is needed to clear them. ## Can employees clock in from their phone, or from home? From their phone at the work site, yes — by default employees clock in and out from the mobile app or a browser on their own device. Clocking in from home or another off-site place is off until an admin turns on **Allow Remote (Work From Home) Clock-in** or **Allow Off-Site / Traveling Clock-in** in Attendance Settings. When you enable them, employees can choose a work mode (On-Site, Remote, or Off-Site) at clock-in. Remote and off-site punches skip geofence verification but still record GPS coordinates for the audit trail. Only on-site punches appear in "who is in the building" counts. If you turn on **Kiosk mode (whole organization)**, personal-device punching is off for everyone: employees clock in and out only at a Time Clock Kiosk. They can still file missing-punch requests and report absences from their own device. --- ## Notifications ## What attendance notification rules can I create? Eight rule types are available: **Missed Check-In**, **Missed Check-Out**, **Late Check-In**, **Early Check-Out**, **Suspicious Activity**, **Location Mismatch**, **Consecutive Late Check-Ins**, and **Consecutive Missed Check-Ins**. Each rule has a severity (Low, Medium, High, or Critical) and a delivery channel — **In-App** is the recommended default because it also delivers push notifications. Email and SMS are available but reach fewer employees in a typical frontline workforce. --- ## Licensing and limits ## Does Time & Attendance require a licence? Yes. An admin enables it from Admin → Apps → All Apps; it is not turned on automatically. Once enabled, admins must also publish it to employees (it starts in admin-only mode until published). ## Are there limits I should know about? | What | Limit | |---|---| | Auto clock-out maximum hours | 1–24 hours (default 12) | | Auto clock-out after shift end | 0–480 minutes (default 30) | | Early clock-in buffer | 0+ minutes (default 15) | | Late clock-in grace period | 0+ minutes (default 30) | | Missing-punch retroactive window | Follows Timesheet Lockout Days (default 7 days) | | Missing-punch maximum span | 24 hours | | Missing-punch reason length | 5–1,000 characters | | Stale open punch cutoff | 24 hours (system-enforced, not configurable) | | Attendance CSV export | 10,000 records per export | | Kiosk PIN lockout | 5 attempts → 5-minute lockout | | Kiosk session lockout | 20 attempts → 10-minute lockout | | Kiosk pairing-code lockout | 10 attempts → 10-minute lockout | | Clock-out reminder lead time | 5–60 minutes (default 5) | | Overtime warning threshold | 20–80 weekly hours (default 40) | | Max autonomous actions per day | 1–500 (default 50) | --- ## More help - [Time & Attendance Overview](/help/articles/time_attendance_app_overview) - Ask AI — the assistant answers Time & Attendance questions from these articles. **Keywords:** faq, clock in, clock out, kiosk, punch, break, missing punch, late arrival, no-show, auto clock-out, IP validation, geofence, photo verification, manager review, attendance permissions, time-attendance, time_attendance, time-&-attendance --- # Timesheets App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run the Timesheets app — approval workflows, auto-approval scoring, deadlines, overtime calculations, and exports. # Timesheets ## 1. What it is Timesheets collects worked hours into pay-period sheets that employees submit and managers approve before the data reaches payroll. It pulls clock-in/clock-out records from Time & Attendance and scheduled shifts from Shifts & Scheduling automatically, calculates regular, overtime and double-time hours, and supports single-level or two-tier approval workflows. - **Enablement:** Timesheets is a licensed app. An admin enables it from **Admin → Apps → All Apps → Timesheets**. - **What it is not:** Timesheets does not run the time clock — clock-ins and clock-outs happen in Time & Attendance. It does not process payroll — approved timesheets are exported to Payroll Connect or downloaded as CSV for an external payroll system. ## 2. Standing it up 1. **Enable the app.** Go to **Admin → Apps → All Apps**, find **Timesheets** and enable it. 2. **Configure pay periods.** Timesheets generates one sheet per employee per pay period, so a pay-period schedule must exist before any sheet appears. Go to **Admin → General Settings → Payroll Settings** and set the period type (weekly, biweekly, semi-monthly or monthly) and start date. (The page's own card is headed "About Pay Period Settings" — it is filed under Payroll Settings, not under a top-level "Pay Period Settings" nav item.) 3. **Set the approval workflow.** Go to **Timesheets → Settings** (in the app sidebar). Choose the **Primary Timesheet Approver** — their direct manager, the managers at their location, or everyone who can approve them — and decide whether to require a second-level regional approval. 4. **Set deadlines.** On the same settings page, set the **Submission Deadline** (days after the pay period ends) and the **Approval Deadline** (days after submission). These drive due-date badges and automated reminders. 5. **Grant approval permissions.** Ensure the managers who will approve timesheets hold the **Approve** capability for the Timesheets feature in their role definition. Admins always have this capability; managers hold it by default. 6. **Verify.** Ask an employee to open **Timesheets** in the sidebar. They should see a sheet for the current pay period, pre-populated with any shifts or attendance already recorded. > **What silently does nothing until paired:** enabling Timesheets without a pay-period schedule means no sheets are generated — employees see an empty page and no reminders fire. Configure pay periods first. ## 3. How it fits together **Timesheets, entries and pay periods.** A timesheet is a single employee's record for one pay period. It contains one entry per day the employee was scheduled or clocked in. Entries are created automatically from attendance records and scheduled shifts; employees can also add or edit entries manually (on the web, with a required reason for the change). The pay period is defined centrally — Timesheets reads it; it does not own it. **Statuses and what moves them.** A timesheet follows this path: | Status | Who acts | What happens next | |---|---|---| | **Pending** | Employee edits entries | Employee submits → **Submitted** | | **Submitted** | Approver reviews | Approver approves → **Approved** (or → **Awaiting Regional Approval** if two-tier is on); approver rejects → **Rejected**, with a reason | | **Awaiting Regional Approval** | Regional approver reviews | Regional approver approves → **Approved** | | **Rejected** | Employee corrects | Employee resubmits → **Submitted** | | **Approved** | — | Locked; exported to payroll | An employee can **recall** a submitted (not yet approved) timesheet to make corrections without waiting for a rejection round-trip. After approval, the employee can **request a correction** — the person who approved the sheet (and the regional approver, if any) is notified with the employee's reason. The approved timesheet itself stays locked: nobody can edit it in Timesheets, so the correction is handled outside the timesheet workflow. **Overtime calculation.** Hours are split into regular, overtime and double-time per workweek (not per period). The split honours the business-wide overtime threshold, the double-time threshold, and any location-specific daily overtime or daily double-time rule set under labor law configuration. A biweekly period of 45 hours one week and 30 hours the next correctly shows 5 hours of overtime, not zero. **Approved leave and holidays.** Days spent on approved leave or holidays appear alongside worked entries on the timesheet as read-only lines. Leave hours are shown separately and are not included in the payable total — that total is purely worked time. **Relationship to Time & Attendance.** When an employee clocks in and out, the attendance record syncs to the matching timesheet entry automatically. Unsynced clock-ins (such as ad-hoc or unscheduled shifts) are reported to the approver, who can add them to the timesheet with one click. Time & Attendance owns the clock; Timesheets owns the payable record. **Auto-approval scoring (optional).** When enabled, each submitted timesheet is scored out of 100. Points are deducted for anomalies — missing punches, edited entries, schedule deviations, overtime and unreviewed attendance. A sheet at or above the threshold (default 95) is approved automatically; anything below is flagged for the manager triage queue. Only timesheets submitted while scoring is on are scored — sheets already waiting for approval when it is turned on are not. Certain anomalies (suspicious IP, punch outside the allowed window, unreviewed attendance) always go to a human regardless of score. Admins can tune the per-factor weights from the settings page. **Edit trail.** Every change to a timesheet entry — whether by the employee or a manager — is recorded in the edit trail, and a change made on the web requires a reason. The trail shows who changed what, the original and new value, and when. Both the employee and the approver see the same trail. ## 4. Running it ### Reviewing and approving timesheets 1. Go to **Team** in the app sidebar. Its count is the number of timesheets waiting for your decision. It opens **Team Timesheets** on **Waiting for me**. 2. Use the status filter to switch lists: **Waiting for me**, **Waiting for regional** (shown when regional approval is on or regional sign-offs are outstanding), **Not submitted**, **Approved**, **Rejected** or **All**. Each shows its count. Narrow any list by location, employee name or pay period (**All periods**, **Current** or **Previous**). 3. Open a timesheet to see the day-by-day breakdown, overtime split, edit history and any manager instructions. 4. Approve, reject (with a required reason) or edit entries before approving. Every manager edit is recorded with a reason in the audit trail. If two-tier approval is on, the first-level approval sends the sheet to **Waiting for regional**. You can approve those sheets one at a time, or tick several and choose **Approve selected**. A different manager must give the regional approval unless **Allow Manager Override** is turned on in settings. ### Monitoring submission progress On **Team Timesheets**, choose **Not submitted**. It lists everyone in your team with no submitted timesheet for the previous pay period, with what is recorded for them so far. Choose **All** with the **Current** pay period to see who already has a timesheet this period. ### Exporting timesheets Managers export from the **Export** button on **Team Timesheets**. Admins can also use the **Export** tab of **Admin → Import / Export** in the app sidebar. Download a CSV filtered by status, date range, location and department. A manager's export covers their own people, and an admin's covers the whole company. The export includes employee ID, period dates, total hours, approval status, approver name and submission date. Employees can also export their own timesheet as CSV from the timesheet detail page. ### Importing timesheets Admins can bulk-import timesheet data from the **Import** tab of **Admin → Import / Export** (app sidebar) using a CSV file. Already-approved timesheets are protected — the importer does not overwrite their hours. ### Scheduled SFTP transfers Admins can set up scheduled imports and exports via SFTP from the **Scheduled transfers** tab of **Admin → Import / Export** (app sidebar). Schedules can run daily, weekly or monthly at a chosen time, and connect through an integration provider configured in the Integrations settings. ### Sending reminders for missing timesheets On **Team Timesheets → Not submitted**, a manager can send a reminder to one employee (**Remind** on their row) or to everyone listed (**Remind all**). Each reminder is an in-app notification and an email. Bulk reminders run in the background to avoid delays and include a cooldown to prevent duplicate sends. ## 5. Settings All settings are at **Timesheets → Settings** (app sidebar). ### Approval Workflow | Setting | Default | What it changes | |---|---|---| | **Primary Timesheet Approver** | Their direct manager | Controls who is told when a timesheet is submitted and reminded until it is approved. *Their direct manager* tells the manager the employee reports to (the managers at their location if none is set, then admins); *Managers at their location* tells every manager assigned to the employee's location; *Everyone who can approve them* tells every manager above the employee and at their location. Companies set up before the direct manager became the default keep *Everyone who can approve them* until an admin changes it. Approval authorization always follows role-based permissions regardless of this choice. | | **Require Regional Manager Approval** | Off | Adds a second approval step. First-level approval moves the sheet to **Awaiting Regional Approval** instead of **Approved**. | | **Allow Manager Override** | Off | When regional approval is on, allows the same manager who gave first-level approval to also complete regional approval. When off, a different manager must complete it. | | **Retroactive Correction Window (Days)** | 7 | How far back employees may file a missing-punch request. Set to 0 to allow any date. This does not control whether a timesheet can be edited — that is decided by its approval status. | | **Require Employee Certification at Submit** | Off | Employees must tick an accuracy statement before submitting. The statement text, timestamp, IP address and device are recorded for wage-hour records. | | **Instructions for Approvers** | "Please review all time entries carefully before approving. Check for accuracy and completeness." | Free-text instructions shown to approvers on the review page while a timesheet is awaiting approval. Clear it to show nothing. | ### Deadline & Notification Settings | Setting | Default | What it changes | |---|---|---| | **Submission Deadline (Days)** | 1 | Days after the pay period ends when employees must submit. Drives due-date badges and reminders. | | **Approval Deadline (Days)** | 2 | Days after submission when managers must approve. | | **Escalation Threshold (Hours)** | 48 | Hours a submitted timesheet may wait for its first approver before everyone else who can approve it is reminded too (admins when there is nobody else), by notification and email. | | **Enable Escalation Notifications** | On | Reminds everyone else who can approve the employee (admins when there is nobody else) once an approval is overdue past the escalation threshold. | ### Auto-Approval Scoring System | Setting | Default | What it changes | |---|---|---| | **Enable Auto-Approval Scoring** | Off | When on, timesheets submitted from then on are scored out of 100 and sheets at or above the threshold are approved automatically without manager review. Sheets below the threshold are flagged for the manager triage queue. | | **Auto-Approval Threshold (%)** | 95 | Minimum accuracy score for automatic approval. | | **Ignore Missing Punches** | Off | Missing punches do not count against the accuracy score. Only effective when auto-approval scoring is on. | | **Ignore Missing Punches on Approved Leave Days** | On | A missing punch on a day the employee is on approved leave does not count against the score. Only effective when auto-approval scoring is on. | > Auto-approval scoring is disabled while **Require Regional Manager Approval** is on. Two-tier approval keeps every timesheet on the manual path. **Accuracy Score Weighting** — below the auto-approval card, admins can customize the points deducted per anomaly type for three tunable factors: missing punches, edited entries and schedule deviation. Each can be adjusted or restored to the platform default. The remaining factors (suspicious IP, punch outside the allowed window, overtime hours, unreviewed attendance) are fixed. Suspicious IP, out-of-window punches and unreviewed attendance always route to a human regardless of the numeric score. ## 6. More help - **Timesheets FAQ** — specific setup and operating questions. - **Time & Attendance Overview** — how clock-ins reach the timesheet. - **Shifts & Scheduling Overview** — how scheduled shifts populate entries. - Ask AI — the assistant answers questions about Timesheets from these articles. **Keywords:** timesheets, timesheet approval, timesheet settings, pay period, overtime calculation, auto-approval, timesheet submission, regional approval, accuracy score, payroll export, timesheet certification, missing punches --- # Timesheets FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Timesheets — for the admin running it. # Timesheets FAQ Answers to common setup and operating questions about Timesheets. For what the app is and how to set it up from scratch, see the [Timesheets Overview](/help/timesheets_app_overview). --- ## Setup ## Do I need to configure pay periods before timesheets start working? Yes. Timesheets generates one sheet per employee per pay period, so a pay-period schedule must exist first. Go to **Admin → General Settings → Payroll Settings** and set the period type and start date. Without a pay period, employees see an empty page and no reminders fire. ## What are the three approval routing modes? The **Primary Timesheet Approver** setting in **Timesheets → Settings** controls who is told when an employee submits a timesheet, and reminded until it is approved: 1. **Their direct manager** (the default for a new company) — the manager the employee reports to. If they have none, or that manager cannot approve timesheets, the managers at the employee's location are told instead, and your admins if there are none. 2. **Managers at their location** — every manager assigned to a location the employee works at. Your admins are told if a location has no manager. 3. **Everyone who can approve them** — every manager above the employee in the reporting line and every manager at their location. A regional manager hears about each timesheet below them. Companies that used Timesheets before the direct manager became the default keep the option they had (**Everyone who can approve them**) until an admin changes it. If a timesheet is still waiting past the escalation threshold, everyone else who can approve the employee is reminded too, or your admins when there is nobody else (with **Everyone who can approve them**, that is always your admins). This setting controls who is _notified_, not who is _authorized_. Any user whose role includes the Timesheets Approve capability can approve a timesheet they navigate to, regardless of which routing mode is active. --- ## Permissions and access ## Who can approve timesheets, and can someone approve their own? Admins and super-admins can always approve. Managers can approve by default — the Timesheets Approve capability is included in the manager role. Custom org roles can also be granted the capability. Members (regular employees) cannot approve. No one can approve their own timesheet. Self-approval is blocked at both the permission layer and the controller — the system checks that the approver is a different person from the timesheet owner. ## Who can change Timesheet settings? Admins and super-admins, plus anyone given the **App admin** role for Timesheets (granted from **Admin → Apps → All Apps → Timesheets**). The entire **Timesheets → Settings** page requires one of those. Managers can approve timesheets but cannot change deadlines, approval routing, auto-approval thresholds, or any other setting. --- ## Day-to-day ## How are timesheets created — do employees have to start them? Timesheets are created automatically. The first time an employee opens the Timesheets page for a pay period, a sheet is generated if one does not already exist. Clock-in, clock-out, and break data from Time & Attendance sync into the entries automatically, including ad-hoc (unscheduled) shifts. A nightly job also pre-creates timesheets for new pay periods so they are ready before anyone opens the page. ## Can an employee take back a submitted timesheet before it's approved? Yes. An employee can **recall** a submitted timesheet as long as it has not yet been approved (or moved to regional approval). Recalling sets the sheet back to Pending so the employee can edit entries and resubmit. No manager action is needed. ## What can an employee do after a timesheet is already approved? The employee can submit a **correction request**. This sends a notification with the employee's reason to the manager who approved the sheet (and the regional approver, if applicable). If the original approvers have left the business, the notification goes to all users with Timesheets Approve authority instead. The approved timesheet itself remains locked — the correction is handled outside the timesheet workflow. ## How is overtime calculated when a pay period spans more than one week? Overtime is calculated per 7-day workweek, not per pay period. Within each week, hours past the overtime threshold (default **40 hours**) are counted as overtime at 1.5× and hours past the double-time threshold (default **60 hours**) are counted as double time at 2.0×. Both thresholds are configurable per business. If a location has a labor-law rule with a lower threshold — including a daily overtime threshold — the lower of the business and the labor-law value is used. A biweekly period where an employee works 45 hours one week and 30 hours the next correctly shows 5 hours of overtime, not zero. ## What reminders does the system send, and when does it stop? The system sends these automated reminders: - **Submission reminders** — due tomorrow, due today, and overdue notifications to employees who have not submitted. - **End-of-period reminders** — sent in the days before a pay period ends. - **Missing-punch reminders** — sent to employees whose timesheet has entries without a clock-in or clock-out. - **Approval reminders** — sent to managers when a submitted timesheet is waiting for review. - **Escalation** — sent when an approval is overdue past the escalation threshold (default **48 hours**) to everyone else who can approve the employee, or to admins when there is nobody else. Escalation is on by default and can be turned off. - **Manager nudge** — a manager can manually send a reminder from **Team Timesheets → Not submitted** to employees who have not submitted. Overdue reminders are sent daily for the first 3 sends, then weekly, with a hard cap of **8 total reminders** per timesheet. Reminders stop once the period's pay date has passed. ## How do pay premiums stack when more than one rule applies? Premium rules resolve in priority order (lower priority number = higher priority). Once a rule marked **Exclusive** applies, no further rules stack on top of it except those explicitly marked **Stackable**. Each premium is calculated as a percentage, a flat rate, or a rate override, depending on the premium type's configuration. Rules can have start and end dates, so a premium can be active for a specific window. Five categories are available: **Shift Differential**, **Acting Pay**, **Hazard**, **Call-Back**, and **Custom**. Premiums are applied automatically when **Enable premium pay** is checked in **Timesheets → Settings**; missed meal and rest break pay follows your break rules. ## Can managers approve or reject timesheets from the AI assistant? Yes. The Timekeeping Agent in Ask AI lets employees ask about their hours, overtime, status, and due dates in plain language. An authorized approver can also approve or reject a submitted timesheet from chat. The assistant shows a confirmation preview before making any change, and the approval is gated by the same Timesheets Approve permission — a manager without that capability only sees read-only answers. --- ## Auto-approval scoring ## How does auto-approval scoring decide what to clear and what to flag? When enabled, every submitted timesheet is scored on a 100-point scale. A flawless sheet scores 100; points are deducted per anomaly: | Anomaly | Default deduction | |---|---| | Missing punch | 8 points each | | Edited entry | 2 points each | | Schedule deviation (more than 15 minutes from scheduled start) | 3 points each | | Overtime hours | 1 point per hour | | Suspicious IP address | 15 points each | | Punch outside the allowed window | 15 points each | | Unreviewed attendance record | 10 points each | Sheets scoring at or above the threshold (default **95**, configurable from 50 to 100) with no blocking anomaly are approved automatically. Everything below is flagged for the manager triage queue. Only timesheets submitted while scoring is on are scored — sheets already waiting for approval when it is turned on are not. **Team Timesheets** shows separate **Flagged for review** and **Auto-approved** filters. Admins can tune the per-anomaly weights for three factors — missing punches, edited entries, and schedule deviation — from **Timesheets → Settings → Accuracy Score Weighting**. The other four factors use the platform defaults and cannot be adjusted per business. Auto-approval scoring is off by default and is disabled while two-level regional approval is on. ## Which anomalies always block auto-approval regardless of score? Three anomaly types always route the timesheet to a human, even if the numeric score is above the threshold: 1. **Suspicious IP address** — a punch from an IP flagged as suspicious. 2. **Punch outside the allowed window** — a clock-in earlier or later than the shift's allowed clock-in window, or a clock-out later than its allowed clock-out window. 3. **Unreviewed attendance record** — an attendance record that still requires manual review. If any of these has a count above zero, the timesheet is flagged for manager review. --- ## When something looks wrong ## "My employee's timesheet shows zero hours even though they clocked in" The most common cause is that the attendance records have not synced to the timesheet yet. Entries are created from Time & Attendance data — if the employee clocked in but their attendance record is incomplete (for example, they forgot to clock out), the entry may show as a missing punch with zero payable hours. Have the employee check their attendance record in Time & Attendance first, then re-open the timesheet. If attendance records exist but the timesheet is empty, the employee may be looking at the wrong pay period. Timesheets are generated per period — use the date range at the top to confirm the period matches the days worked. ## "An employee forgot to clock in — can they file a missing punch after the fact?" Yes. The employee can file a **missing-punch request** from the Attendance page or from the timesheet view. The request asks for the clock-in time, clock-out time, an optional break, and a reason (5 to 1,000 characters). It is routed to the employee's manager for review. The request must fall within the **Retroactive Correction Window**, which is set in Timesheet settings (default **7 days**). If the period is older than the window, the request cannot be submitted. Setting the window to 0 allows requests for any past date. ## "A manager can't complete regional approval on a timesheet they already approved at the first level" This is by design. When two-level approval is on, the system enforces a segregation-of-duties rule: the manager who gave first-level approval cannot also give regional approval. A different manager must complete the second step. If your business needs the same manager to handle both levels (for example, a small team with one manager), enable **Allow Manager Override** in **Timesheets → Settings**. When this is on, the first-level approver can also give regional approval. --- ## Licensing and limits ## What are the hard limits I should know about? | Limit | Value | |---|---| | Maximum hours per timesheet entry | 24 hours | | Maximum break duration per entry | 480 minutes (8 hours) | | Clock-out time cannot be more than | 5 minutes in the future | | Timesheet import file size | 2 MB | | Accepted import formats | CSV, XLSX, XLS | | Auto-approval threshold range | 50–100 (default 95) | | Missing-punch reason length | 5–1,000 characters | | Overdue reminders before the system stops | 8 (3 daily, then weekly) | | SFTP schedule frequencies | Daily, Weekly, Monthly | | Retroactive correction window | Configurable (default 7 days; 0 = unlimited) | --- ## More help - [Timesheets Overview](/help/timesheets_app_overview) - [Time & Attendance Overview](/help/time_attendance_app_overview) — how clock-ins reach the timesheet. - [Shifts & Scheduling Overview](/help/shifts_scheduling_app_overview) — how scheduled shifts populate entries. - Ask AI — the assistant answers Timesheets questions from these articles. **Keywords:** faq, timesheet approval, pay period, overtime calculation, auto-approval scoring, accuracy score, missing punch, regional approval, timesheet export, timesheet reminders, pay premiums, timesheet limits, timesheet certification, timesheets --- # Town Halls App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-18 How to set up and run company-wide sessions in Town Halls — town halls, all-hands, training briefings — with live video, chat, Q&A, polls, a stage wall, break-room screens, reach by location and on-demand playback. # Town Halls Town Halls was called Livestreaming before October 2026. ## 1. What it is Town Halls lets your company broadcast live video to the entire organization — or a targeted audience — directly inside OneMango. Typical sessions are town halls, all-hands meetings, leadership Q&A, training briefings, and safety announcements. Viewers participate through live chat, upvote-Q&A, and polls while watching. Streams are recorded for on-demand playback. - **Video:** a session's video is streamed here from your encoder, shown on another platform you link (Teams, Meet, your streaming vendor), or left out entirely for a session people are in the room for. The Q&A, polls and chat are the same in all three. - **In the room:** every session has a stage wall — a full-screen page for the screen behind the speaker that shows the question a moderator put on stage — and a join QR that brings people's phones into the Q&A. With Digital Signage, a session can also take over break-room screens while it is live. - **Enablement:** Town Halls is a pay-as-you-go app billed in platform credits — broadcast minutes and viewer minutes for a stream broadcast here, a flat charge per session without our video. It is available to every tenant without a separate license purchase; an admin enables it from **Admin → Apps → All Apps**. - **What it is not:** Town Halls runs one-to-many sessions. It is not a two-way video call or a remote-expert session — those are handled by Live Assist. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Town Halls**. 2. Open **Apps → Town Halls → Settings**. Review the defaults (see §5). The most important decision is **Who can schedule and host sessions** — the default is **Admins and app admins only**. Under **Questions**, decide whether hosts may make a session's questions anonymous (**Allow anonymous questions**, on by default). 3. Confirm a streaming provider is connected. The Settings page shows a **Provider** card. Most tenants use the managed Mux account (no setup needed). Enterprise tenants that need their own provider can configure one under **Admin → Organization → Integrations**. 4. Check the **Secure playback** badge on the provider card. If it reads **Public playback**, any person who obtains the stream URL can watch — even outside your organization. Contact MangoApps support to enable signed playback. 5. To try the workflow without notifying anyone, load the sample sessions from **Settings**. There is no test or rehearsal mode: **Go live** on a real session starts it for real and notifies its audience — everyone, when no audience is set — at once. For a real rehearsal, schedule a session whose audience is just the people taking part and set **Who can watch** to **Only this session's audience**. Your users will see a **Town Halls** widget on their home dashboard showing any live or upcoming sessions. **What silently does nothing until you also configure it:** the "Auto-post recordings to the Communications feed" setting requires the Communications app's own **Town Halls — allow posting to the feed** contributor switch to be on. If the contributor switch is off, the auto-post is skipped silently regardless of the Town Halls setting. ## 3. How it fits together ### Sessions and their lifecycle A session (the central object) moves through a fixed sequence: **Scheduled → Live → Ended → Recorded**. A session can also land in **Failed** if the provider refuses the go-live request. Ending a session is final — it can't be restarted. A session is scheduled by choosing a title, an optional description, a scheduled start time, and whether to record. Anyone allowed by the **Who can schedule and host sessions** setting can schedule one — by default admins, app admins and Town Halls contributors. Whoever schedules a session can name someone else as its host; after that, only they or an admin can change the host. Example: your HR director creates a session titled "Q3 All-Hands" scheduled for Friday at 2 PM, with recording on. That session appears on the company Calendar (if the Calendar integration is enabled), in the Town Halls dashboard widget, and in the Sessions list. On Friday the host opens the **Host console** with OBS, vMix, or another RTMPS-capable encoder ready, and clicks **Go live**. That starts the stream and notifies its audience straight away; the console then shows the RTMPS server URL and stream key, which the host pastes into the encoder before starting it. Viewers watch at the session's watch page. After the broadcast, the host clicks **End stream**. Once the provider finishes processing, the status changes to **Recorded** and the recording is available for on-demand playback on the same page. ### Roles These levels of access govern who can do what: - **Viewer** — any user the app is published to can watch, chat, ask questions, and vote in polls. A session whose **Who can watch** is **Only this session's audience** is open only to its audience, its host, whoever scheduled it and admins. - **Scheduling** — controlled by the **Who can schedule and host sessions** setting. Business admins, Town Halls app admins and Town Halls contributors can always schedule, whatever the setting says. - **Running a session** — opening the host console (server URL and stream key), going live, ending, editing and canceling, and switching break-room screens on or off while it runs. Allowed for the session's host, whoever scheduled it, any business admin, and any Town Halls app admin. - **Moderating** — removing chat messages, marking questions answered or dismissed, launching and closing polls, running the stage wall, the AI features (cluster questions, generate recap), and seeing the session's **Reach by location**. Allowed for everyone who can run the session, plus every Town Halls contributor. - **Town Halls contributor** — a role an admin grants per person under **Admin → Apps → Town Halls → Admins & Contributors**, for a comms partner who works on sessions without changing settings. A contributor schedules and runs their own sessions and moderates every session, but gets no host console, stream key, **Go live** or **End stream** on a session they neither host nor scheduled. ### Audience participation Three real-time features run alongside the video player: - **Live chat** — text messages that appear for every viewer in real time. Moderators can remove individual messages (the message is hidden from all viewers immediately; the audit trail is preserved). Chat closes automatically when the session ends. Messages are capped at 500 characters. A rate limit prevents flood spam. - **Upvote-Q&A** — viewers submit questions (up to 1,000 characters) and upvote others'. Questions are sorted by votes so the most popular rise to the top. Each session chooses how questions reach the room: **Open** (straight in), **Filtered** (a question with language the company's filter catches waits for a moderator), or **Reviewed** (every question waits for a moderator before anyone else sees it — the default for a session open to everyone). Moderators approve, edit then approve, or dismiss waiting questions from the watch page or the host console, and can switch the mode while the session runs. The host marks questions **Answered** or **Dismissed**; dismissed questions are hidden from all viewers, and the person who asked is told. New questions close when the session ends, but upvoting existing questions remains open afterward so a late viewer can still push a question up the host's follow-up list. - **Names on questions** — each session decides who sees who asked, separately from how questions are moderated: - **Shown to everyone** (the default) — the room sees each asker's name. - **Moderators only** — the room sees "Anonymous" in place of the name; the session's moderators see who asked in the waiting queue, on the stage card and in the questions export. - **Anonymous** — the question is saved with no asker at all, so nobody sees who asked: not the room, not the moderators, not the export. The asker sees their own questions under **Your questions** on the device they asked from, can withdraw one until it is answered, and is told if a moderator takes it out of the queue. The Ask box tells each person which of these applies before they ask. The setting is fixed once the first question arrives — people asked under it — and **Anonymous** is offered only while **Allow anonymous questions** is on in Settings (a session already anonymous keeps it). - **Polls** — moderators create a poll with a question and at least two options, then launch it live. Each viewer gets one vote per poll. Per-option results are hidden from a viewer until they have voted or the poll is closed, so results cannot bias the vote. The host can close a poll at any time to lock in results. ### The stage wall and join QR The stage wall is for the people in the room. It is a full-screen, dark page with the company's logo and the session's title and status (Starting soon, Live with how many have joined, or ended), meant for the screen behind the speaker or a vMix or OBS browser source: - **On stage now** — the question a moderator put on stage, in large type, with the next approved questions by votes beneath it under **Up next**. With nothing on stage, the wall shows the **Top questions** by votes. - **Only approved questions** — the wall never shows a question waiting for a moderator. It names the asker and their site only in a session whose names are shown to everyone; otherwise, and wherever a works council hides names, it says "A participant". - **The run of show** — moderators drive the wall from the **Stage wall** card on the host console, or on the watch page for a moderator who doesn't run the console: **Put on stage** (any approved, unanswered question from **Up next**), **Pin** (keeps the question up after it is marked answered; unpinned, it leaves the wall when answered), **Clear**, and **Pause wall** / **Resume wall** (paused, the wall keeps what it showed — except a question that is dismissed, which still leaves it). Each change reaches the wall within a few seconds without a reload. - **The display link** — the wall's own link opens it with no sign-in, for a stage machine that never logs in. It works until a moderator clicks **New link**: the old link stops at once, and a stage machine still showing it says "This display link isn't working" until it is given the new one. Digital Signage screens showing the wall switch to the new link on their own. - **The join QR** — in the wall's corner, on the Stage wall card, and on a printable sheet (**Print the QR**) with the session's title and start time for an agenda or the door. A scan signs the person in the usual way and opens the session's watch page on their phone, where they can ask a question. The sheet also prints the link for anyone who can't scan. ### Reach by location Once a session is live, its page shows **Reach by location** to its host, moderators and admins: of the people it was for (its audience when it has one, otherwise every active member), how many joined — by region (the districts and regions above the sites) and by site, each person counted at their own site in this company. Admins can pick any recent session in **Analytics**. Groups smaller than the company's smallest report group (5 by default, set under **Admin → Compliance → Retention & Legal Holds**) are counted together in **Other**, and a region is left out when a smaller group could be worked out from it. Break-room screens that played the session are listed separately, never as people. ### Connected apps Town Halls automatically wires into other apps when enabled in Settings: - **Calendar** — a calendar event is created when a session is scheduled, kept in sync on edits, and removed if the session is canceled. It goes on the calendar of the session's audience, or of everyone when no audience is set. - **Broadcasts** — a draft "We're live" Broadcast is created when a session goes live, when your company runs the Broadcast or Communications app. Nothing is sent until someone publishes it from **Communications → Broadcasts**: a business admin, a Communications or Broadcast app admin, anyone allowed to publish broadcasts or whose assigned audiences cover it, or the person who went live if they may create broadcasts. Admins, managers and anyone who manages or edits broadcasts see every draft there. While the session is live, the session page and host console link to the draft for the people who can open it, and a draft nobody sent is removed when the session ends. - **Communications feed** — a "Recording available" post is published to the Communications feed when the recording finishes (subject to the Communications contributor switch). - **Digital Signage** — when your company has Digital Signage with an active screen, a session everyone can watch can be sent to break-room screens (**Show on screens** on the schedule form, optionally **Only some sites**). While it is live, those screens switch to it: a stream broadcast here plays muted with its title, a LIVE NOW tag and the join QR; a session whose video is elsewhere, or has none, shows its stage wall. When it ends, the screens go back to their playlist. An alert in a screen's feed always comes first, and a screen whose own **Live sessions** rule is set to hide them never switches. A screen playing the stream counts as one viewer for viewer minutes, but is not counted as a person in the viewer count or reach. ### AI features Three AI-powered features help hosts and viewers: - **Cluster questions** (the Q&A on the watch page, for moderators) — groups and de-duplicates the Q&A list into themes so a host fielding many questions can see the topics that matter most. - **Generate recap** (session page) — produces a summary after the session from the audience interaction (chat, Q&A, polls) and, for a stream broadcast here, its captions, for employees who missed the session. - **Catch me up** (watch page, live sessions only) — gives a late-joining viewer a summary of what has happened so far, from the audience activity and, for a stream broadcast here, its live captions. One summary is shared by everyone who asks; it is refreshed at most once a minute. ## 4. Running it ### Scheduling a session 1. Go to **Apps → Town Halls → Sessions** and click **Schedule a session**. 2. Enter a title, optional description, scheduled start time, and host. Choose how **Questions** reach the room (Open, Filtered or Reviewed) and where the **Video** comes from — **Stream it here** (pick the **Spoken language** for its live captions, keep **Live captions while on air** checked or uncheck it for a low-latency stream, and check or uncheck **Record this stream**), **Another platform** (paste the https:// viewing link), or **No video**. Pick **Names on questions** (Shown to everyone, Moderators only or Anonymous). For a session everyone can watch, when your company has Digital Signage screens, tick **Show on screens** — and, under **Only some sites**, the sites whose screens should show it (none ticked means every site). The form shows the session's likely cost before you save. 3. Click **Schedule a session**. The session appears in the **Upcoming** section of the dashboard and, if the Calendar integration is on, on the company Calendar. ### Going live There is no test or rehearsal mode. **Go live** is the real start: it notifies people at once, and the stream key only exists after you press it. For a session on another platform or with no video, the console's **Open the room** is the start instead — it tells the same people and opens the Q&A, polls and chat, and **Close the room** ends it. 1. Open your encoder (OBS, vMix, or any RTMPS-capable software) so it is ready to paste into. 2. Open the session and click **Host console**. Before you go live it shows who will be told and who can watch. 3. Click **Go live**. The status changes to **Live** straight away, everyone in the session's audience (or everyone, when no audience is set) gets a "Live now" notification with a link to the watch page, and the console shows the **Server URL** and **Stream key**. 4. Paste the Server URL and Stream key into your encoder and start it. Viewers can open the session as soon as it is live, even before your encoder connects, so do this right away. 5. The console shows a real-time viewer count, a status badge, and the **End stream** button. Ending is final — a session can't be restarted. If the provider refuses the go-live, the session moves to **Failed** and the error reason is displayed on the console. The host can click **Try going live again** on the console (or **Try again** on the session's page). A failed session is left off the Town Halls home's On air, Upcoming and Past lists and the home-page widget. It still appears in the **Sessions** list, marked Failed, for everyone who can watch it, and its page tells them nothing was broadcast; only the people who can run the session see the reason and the retry button. A 15-minute reminder notification is sent to the host before a scheduled session starts. If the session targets a specific audience, those audience members also receive the reminder. For a session with no audience set, everyone else gets it only when **Remind everyone 15 minutes before a session that has no audience set** is on in Settings (off by default). People who registered for the session under Calendar's Events tab also get the calendar's own reminder an hour before. ### During the session - The host monitors the live viewer count and status from the **Host console**. - Moderators can remove chat messages, mark Q&A questions answered or dismissed, approve or dismiss questions waiting for a moderator, and launch or close polls — all from the watch page (the waiting questions are on the host console too). The console's **Open viewer page** button takes the host there. - **Cluster questions**, in the watch page's Q&A, groups the questions into themes for the host. - Moderators run the stage wall from the **Stage wall** card (host console or watch page): **Open the wall** opens it in a new tab, **Copy** copies its display link for the stage machine, and **Put on stage**, **Pin**, **Clear** and **Pause wall** change what the room sees. - The console's **Break-room screens** switch turns the session on or off for the screens while it runs. - Viewers who join late can use **Catch me up** on the watch page. ### Ending and reviewing 1. Click **End stream** on the host console. The session moves to **Ended** and can't be restarted. A live session cannot be edited or canceled — end it first. 2. Once the provider finishes processing (automatic), the status becomes **Recorded** and the recording is available for on-demand playback on the session's page. If recording was turned off for this session, no recording is kept. 3. A moderator can use **Generate recap** to create a summary of the audience interaction, and **Download all questions (CSV)** on the watch page or host console for the follow-up. The session's page shows its **Reach by location** to its host, moderators and admins. 4. To call off a session that hasn't aired, open it and choose **Cancel session** from its **⋮** menu; for a session that has ended, the same menu offers **Delete**. Either one also removes the mirrored Calendar event if one was created. ### Analytics Go to **Apps → Town Halls → Analytics** (admin and app admin only). The page shows sessions held, broadcast minutes and recordings, all time; sample sessions are left out. Broadcast minutes are part of what Town Halls bills for streams on the managed account (20 credits per broadcast minute; viewer minutes are billed on top — see the FAQ); streams on your own Mux connection are counted here but draw no credits. Each stream's minutes are rounded up individually. A **Recent sessions** table lists individual sessions with their broadcast minutes, unique viewers and status. Above it, **Reach by location** shows one aired session from the latest 20 at a time — pick it from the list and click **Show**. ## 5. Settings All settings are at **Apps → Town Halls → Settings** (admin and app admin only). ### Hosting & recording | Setting | Default | What it changes | |---|---|---| | **Who can schedule and host sessions?** | **Admins and app admins only** | Controls who can create and host new sessions. **Any user** lets every employee schedule a session. Admins, app admins and Town Halls contributors can always schedule regardless. Switching back to admins only doesn't take back sessions already scheduled: their host and whoever scheduled them can still edit them and go live — cancel those from **Sessions** if needed. | | **Record streams by default** | On | Pre-fills the "Record this stream" checkbox when scheduling. The host can override it per session. Recorded streams are available for on-demand playback; unrecorded streams are not. | | **Auto-caption recordings (AI transcription)** | On | Requests AI-generated captions on recorded streams. | ### Connected apps | Setting | Default | What it changes | |---|---|---| | **Add scheduled sessions to the company Calendar** | On | Creates and syncs a Calendar event for each scheduled session. Switching it off removes upcoming sessions from everyone's calendar; switching it back on adds sessions scheduled from then on, and ones already booked come back when they are edited. | | **Draft a 'We're live' Broadcast when a session goes live** | On | Creates a draft Broadcast when the host goes live (when the Broadcast or Communications app is on). Nothing is sent until someone who may publish broadcasts publishes it from **Communications → Broadcasts**, and a draft nobody sent is removed when the session ends. | | **Auto-post recordings to the Communications feed** | Off | Posts a "Recording available" entry to the Communications feed when the recording finishes. Also requires the Communications app's contributor switch for Town Halls to be on. | ### Questions | Setting | Default | What it changes | |---|---|---| | **Allow anonymous questions** | On | Lets a host set a session's **Names on questions** to **Anonymous** — saved with nobody's name behind them, not even for moderators or in the export. Off takes **Anonymous** off the schedule form for everyone; sessions already anonymous keep it, since people asked under it. **Moderators only** stays available either way. | ### Notifications | Setting | Default | What it changes | |---|---|---| | **Remind everyone 15 minutes before a session that has no audience set** | Off | A session with an audience always reminds that audience. On, every employee who can open the app also gets the 15-minute reminder for sessions with no audience; off, they hear about those sessions only when they go live. | ## 6. More help - **Town Halls FAQ** — specific setup and operating questions, limits, and troubleshooting. - Ask AI — the assistant answers questions about Town Halls from these articles. **Keywords:** livestreaming, live stream, town hall, all hands, broadcast, webcast, Q&A, polls, recording, playback, go live, stage wall, display link, QR code, anonymous questions, names on questions, digital signage, break-room screens, reach by location, town-halls --- # Town Halls FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-18 Answers to common setup and operating questions about Town Halls — for the admin running it: hosting, Q&A and names on questions, the stage wall and join QR, break-room screens, reach by location, billing and limits. # Town Halls FAQ Answers to common setup and operating questions about Town Halls. For what the app is and how to set it up from scratch, see the [Town Halls Overview](/help/livestreaming_app_overview). --- ## Setup ## Do I need to configure a streaming provider before anyone can go live? Most tenants use the managed provider and need no provider setup — streams work out of the box once the app is enabled. Enterprise tenants that need their own account can configure one under **Admin → Organization → Integrations** (category: Livestreaming Infrastructure (Town Halls)). The Settings page shows a **Provider** card so you can confirm what is connected. ## Who can schedule and host sessions? The **Who can schedule and host sessions** setting in **Apps → Town Halls → Settings** controls this. The default is **Admins and app admins only**. Changing it to **Any user** lets every employee schedule and host sessions. Business admins, Town Halls app admins and Town Halls contributors can always schedule regardless of this setting — make one person a contributor under **Admin → Apps → Town Halls → Admins & Contributors** to let them run sessions without giving them the settings. Switching back to admins only doesn't take back sessions already scheduled: their host and whoever scheduled them can still edit them and go live, so cancel those from **Sessions** if needed. ## What are the default settings when I first enable the app? | Setting | Default | |---|---| | Who can schedule and host sessions | **Admins and app admins only** | | Record streams by default | **On** | | Auto-caption recordings (AI transcription) | **On** | | Add scheduled sessions to the company Calendar | **On** | | Draft a "We're live" Broadcast on go-live | **On** | | Auto-post recordings to the Communications feed | **Off** | | Allow anonymous questions | **On** | | Remind everyone 15 minutes before a session that has no audience set | **Off** | --- ## Permissions and access ## Who can manage or moderate a specific session? Running a session — the host console and stream key, going live, ending, editing and canceling — is tied to the session: its host, whoever scheduled it, any business admin, and any Town Halls app admin. Moderating — removing chat messages, marking questions answered or dismissed, launching polls, running the stage wall, the AI features, and seeing the session's **Reach by location** — is open to all of those plus every **Town Halls contributor**, on every session. A contributor moderates from the watch page, which has its own **Stage wall** card; they don't get the console of a session they neither host nor scheduled. Someone who can schedule only because **Who can schedule and host sessions** is set to **Any user** cannot moderate someone else's session. ## Why can't I open the host console for a session I didn't create? Only the session's host, whoever scheduled it, or an admin can open the console. If you need it, ask whoever scheduled the session, or an admin, to make you its host — the host can't hand the session to someone else. To moderate chat and Q&A without the console, ask an admin to make you a Town Halls contributor. ## Can I limit who can watch a session? Yes. In the session's form, **Who can watch** has two choices. **Everyone with Town Halls** (the default) lets anyone who can open the app find the session and watch it; the **Audience** field then only decides who is notified. **Only this session's audience** limits the session to the people in its audience: nobody else sees it in the Sessions list, the Town Halls home, search or the home-page widget, and a link to it tells them it isn't available. Its host, whoever scheduled it, Town Halls admins and business admins can always watch it. Choosing it needs an audience, and a session limited this way can't be opened for registration under Events or shown on break-room screens. --- ## Day-to-day ## What RTMPS ingest URL do I point my encoder at? The host console shows the server URL and stream key once you click **Go live** — the key is created then, not when the session is scheduled. The ingest endpoint is `rtmps://global-live.mux.com:443/app`. Use any RTMPS-capable encoder — OBS, Wirecast, vMix, Zoom, or Teams. ## Can I edit or cancel a session while it is live? No. A live session must be ended before it can be edited or canceled. End it first from the host console (**End stream**), then make changes. ## What happens when I click "Go live"? The stream starts for real — there is no test or rehearsal mode. The platform creates the stream with the provider, shows the server URL and stream key on the console, and flips the status to **Live**. Straight away, everyone who can open the app (or the session's audience, when one is set) gets an in-app and push "Live now" notification, and — when that setting is on — a draft "We're live" Broadcast is created for someone who may publish broadcasts to send (it is removed if the session ends before anyone sends it). Viewers can join before your encoder connects, so have it ready and paste the key in as soon as it appears. Ending the session is final; it can't be restarted. ## What notifications do viewers and hosts receive? These notifications are sent automatically: 1. **Pre-session reminder** — sent 15 minutes before the scheduled start to the host (with a link to the console) and, when the session targets a specific audience, to those audience members (with a link to the watch page). For a session with no audience set, everyone who can open the app gets it only when **Remind everyone 15 minutes before a session that has no audience set** is on (off by default). The session's Calendar entry reminds only its host and the people who registered for it under Events, an hour before. 2. **Go-live notification** — sent to everyone who can open the app (or the targeted audience) when the host clicks **Go live**, with a link to join the session. The host is excluded. 3. **New time** and **Canceled** — when a scheduled session is moved or canceled, everyone already told about it (by a reminder or the go-live notification) hears about the change. 4. **Session ended automatically** — sent to the host when the platform ends a session whose encoder stopped sending video. 5. **You're hosting** / **No longer hosting** — sent when someone else makes you a session's host, or hands a session you hosted to someone else. Reminders and go-live notifications are one-shot per session per user, so overlapping schedules or retries never double-send; a session moved to a new time reminds its audience again. Employees can mute Town Halls notifications in their own notification settings (the **Town Halls** category). --- ## When something looks wrong ## I clicked "Go live" and the session shows "Failed" — what happened? The provider refused to create the stream. The host console displays the error reason. Common causes are missing or expired provider credentials, a provider rate limit, or a network issue. Click **Try going live again** on the console (or **Try again** on the session's page). The session stays editable — it is not locked into a failed state. If retries keep failing, a company admin checks **Admin → Organization → Integrations** (for your own Mux account) or contacts support (for the managed account) — if you aren't an admin, ask one. On the managed account, a go-live can also be held back before it reaches the provider when the company is short of platform credits (a stream on your own Mux account draws none, so it is never held back for credits); the message says so, and only a billing admin can top up. ## The live viewer count on the host console seems frozen or too high The viewer count is driven by a heartbeat from each watch page. If a viewer's tab crashes or their laptop sleeps without sending a leave signal, they drop out of the active count within 2 minutes. A background sweep runs every minute to clear viewers who have gone quiet. If the count still looks wrong after a couple of minutes, the sweep may have been delayed — ask the viewer to reload the watch page. The count is people only: break-room screens showing the session aren't in it, however many people stand in front of them. ## "Catch me up" says there's nothing to summarize, but the session has been going for a while "Catch me up" summarizes the room's audience activity — chat messages, questions, and poll results — and, for a stream broadcast here, its live captions of what was said. A session on another platform, or with no video, has only the room: if no one has chatted, asked questions, or launched a poll yet, it has nothing to work with and says there are no chat messages, questions or polls yet. Encourage audience participation. ## My recording is missing — the session ended but there is no playback Check whether **Record this stream** was checked when the session was scheduled. If recording was turned off for that session, the provider still auto-records but the recording is discarded at the provider level, so nothing is stored and playback is not available. The session's status stays **Ended** rather than moving to **Recorded**. ## The "Auto-post recordings to the Communications feed" setting is on, but no post appeared Two switches must be on. In Town Halls Settings the **Auto-post recordings to the Communications feed** toggle must be enabled, AND in the Communications app's contributor settings the **Town Halls — allow posting to the feed** switch must also be on. If the contributor switch is off, the auto-post is skipped silently. ## A viewer says they can watch the stream without logging in — is playback public? Playback is signed (access-controlled) only when a signing key is configured. The Settings page shows a badge: **Secure playback** means new streams use signed tokens (valid for 6 hours), and a leaked URL cannot be watched from outside. **Secure playback pending** means a signing key will be created the first time a stream goes live. **Playback security unconfirmed** means the platform couldn't tell how playback is set up, so assume it is public. **Public playback** means no signing key is present and anyone with the URL can watch. On the managed account, contact MangoApps support to enable signed playback. On your company's own Mux account (**Admin → Organization → Integrations**), a signing key is created automatically the first time a stream goes live, as long as the access token is allowed to create signing keys. --- ## Q&A, names on questions and polls ## Can moderators check questions before the whole company sees them? Yes. Each session has a **Questions** setting on its schedule form: **Open** shows a question as soon as it is asked; **Filtered** holds a question that contains language your company's content filter catches; **Reviewed** holds every question until a moderator approves it. A session for everyone starts as **Reviewed**, and one aimed at a set audience as **Open** — the host can change either, and switch it from the host console while the session runs. Waiting questions are listed under **Waiting for a moderator** on the watch page and the host console: approve one, correct it first (a typo, a name to take out), or dismiss it. The person who asked sees theirs marked "Waiting for a moderator — only you can see it", and is told if it is dismissed. When your company has AI moderation turned on, a question the AI flags is moved to the front of the queue (Reviewed) or held after it was shown (Filtered). ## Can we use Town Halls for a meeting we stream somewhere else, or one with no video? Yes. On the schedule form, **Video** offers **Stream it here** (your encoder streams to Town Halls), **Another platform** (paste the https:// link viewers open — Teams, Meet, or your vendor's player; viewers get a button to it beside the Q&A, polls and chat), or **No video** (a session people are in the room for). For the last two the host console offers **Open the room** and **Close the room** instead of Go live and End stream. A room left open is closed automatically 12 hours after its start. ## Are there live captions? Yes, for every stream broadcast here unless its host turns them off: captions are generated live on the stream in the language the host speaks — English, French, German, Italian, Portuguese or Spanish, chosen under **Spoken language** on the schedule form. Captions are not translated. Live captions put the video about 20–30 seconds behind the host, because the video service makes none on a low-latency stream; a host who wants the room closer to real time (about 5 seconds) unchecks **Live captions while on air** before going live. The choice is fixed once the stream is on air. Recordings also get captions when **Auto-caption recordings** is on. A session on another platform carries whatever captions that platform provides. ## Can I export the questions after a session? Yes. Moderators can choose **Download all questions (CSV)** on the watch page or the host console, during or after the session. The file lists every question — waiting, in the room, answered or dismissed — with who asked it and their department and location, the votes, its status, when it was asked and answered, and who answered or edited it. Who asked follows the session's **Names on questions**: a session shown to everyone or to moderators only names the asker; an anonymous session says "Anonymous", leaves out the department and location, and gives only the day an anonymous question was asked, not the time. Where a works council hides people's names, the row says "A participant" and leaves out the department and location, whatever the setting. ## Who can see who asked a question? It depends on the session's **Names on questions**, chosen on its schedule form: | Setting | The room (watch page, phone, stage wall) | The session's moderators (waiting queue, stage card, export) | |---|---|---| | **Shown to everyone** (default) | The asker's name | The asker's name | | **Moderators only** | "Anonymous" ("A participant" on the stage wall) | The asker's name | | **Anonymous** | "Anonymous" ("A participant" on the stage wall) | Nobody — the question is saved with no asker | The Ask box tells each person which applies before they ask, on the web and on the phone. In an anonymous session not even an admin can find out who asked: the question carries no name anywhere. Wherever a works council hides names, the stage wall and the export say "A participant" whatever the setting. ## Why can't I change Names on questions? It is fixed once the first question arrives — the form says "Questions have arrived, so this can't change — people asked under it." Until then the host can change it. If someone had the Ask box open when the host changed it, their question is not posted: they are told who now sees the names and asked to send it again if they're happy with that. ## "Anonymous" isn't offered on the schedule form An admin has turned off **Allow anonymous questions** in **Apps → Town Halls → Settings** (under **Questions**). Turning it on brings the choice back. A session that was already anonymous stays anonymous either way, and **Moderators only** is always available. ## How does someone see or withdraw their own anonymous question? The server keeps no record of who asked, so the asker's own browser remembers it: their anonymous questions are listed under **Your questions** on the watch page, on the device and browser they asked from, for whoever is signed in there — a second person on a shared device doesn't see the first one's questions as theirs. From there they can withdraw one until it is answered, and they see "A moderator took your question out of the queue. It isn't shown to anyone." if a moderator dismisses it. On another device, or after clearing the browser's data, the question is still in the room, just no longer listed as theirs — nothing on the server links it back to them. ## Can a viewer vote more than once in a poll or upvote a question twice? No. Each viewer gets exactly one vote per poll and one upvote per question. A poll vote is final — the first answer stands and can't be changed, so a second click is refused with a message saying so. A second upvote on the same question simply leaves the first in place. ## Can viewers still ask questions after the session ends? New questions are blocked once the session ends. Upvoting existing questions remains open, so a viewer who watches the recording can still push a question up the host's follow-up list. --- ## Stage wall and join QR ## How do I put the stage wall on the screen behind the speaker? Open the session's **Host console** (or, for a moderator who doesn't run the console, its watch page) and find the **Stage wall** card. **Open the wall** opens it in a new tab for you, signed in. For a stage machine or a vMix or OBS browser source that never signs in, click **Copy** under **Display link** and open that link there — it needs no sign-in. The wall has a **Full screen** button. It shows "Starting soon" before the session starts, "Live" with how many have joined while it runs, and "This session has ended" afterwards. ## Who can run the stage wall? Everyone who can moderate the session: its host, whoever scheduled it, business admins, Town Halls app admins and Town Halls contributors. Anyone else who opens the wall's address in the app is sent back to the session with "Only this session's host, a moderator, or an admin can run its wall." The display link is different: anyone with it sees the wall, but can't change it. ## What does the wall show when nothing is on stage? The top approved questions by votes. With no approved questions yet, it shows "Questions will appear here". It never shows a question still waiting for a moderator. ## Why did a question leave the wall? A question on stage leaves the wall when a moderator clears it, when it is dismissed or held for review, when its asker withdraws it, and when it is marked answered — unless it is **pinned**. A pinned question stays up after it's answered until someone clicks **Clear**, or **Unpin** (which then takes it down). ## Why can't I put a question on stage? Only an approved, unanswered question can go on stage. A question still waiting for a moderator is refused with "That question isn't in the room — approve it first." An answered one is refused with "That question has been answered — reopen it to put it on stage." ## What does "Pause wall" do? The wall keeps showing exactly what it showed when you paused it, so you can work the queue without the room watching. A question you dismiss during the pause still leaves the wall. Anything you put on stage while paused goes up when you click **Resume wall**, which brings the wall back to live. ## The display link says "This display link isn't working" Someone made a new link (**New link** on the Stage wall card), the session was deleted, or Town Halls was turned off for your company. Making a new link stops the old one at once — that's what it's for if a link was shared too widely. Copy the current link from the Stage wall card and open it on the stage machine. Digital Signage screens showing the wall switch to the new link on their own. ## Where does the join QR take people? A scan opens a sign-in page — the person signs in the usual way — and then the session's watch page on their phone, where they can ask a question, vote and — when chat is on — chat. Someone already signed in goes straight there. The QR is in the wall's corner (until the session is over), on the Stage wall card, and on a printable sheet: **Print the QR** opens a page with the session's title, start time and the QR, plus a link to type in for anyone who can't scan. ## Does the wall show who asked? Only in a session whose **Names on questions** is **Shown to everyone**: then it shows the asker's name and their site in your company. In a **Moderators only** or **Anonymous** session — and wherever a works council hides names — it says "A participant". --- ## Break-room screens ## Why isn't "Show on screens" on the schedule form? It appears only when your company has Digital Signage with at least one active screen, only while **Who can watch** is **Everyone with Town Halls** (a break-room screen is seen by anyone in the room), and not once the session has ended. ## Which screens switch to a session, and when? When the session goes live (or its room opens, for a session whose video is elsewhere or has none), the screens at the sites ticked under **Only some sites** switch to it — or every site's screens when none are ticked. A screen with no site set shows only sessions sent to every site. The screen goes back to its playlist when the session ends. If two sessions are live on screens at once, a screen shows the one that went live most recently. The host can switch screens off and on during the session with the console's **Break-room screens** switch. ## A screen didn't switch to the live session Check three things. The screen's own rule: on the screen's page in Digital Signage, **Live sessions** set to hide means it never switches. An alert: while an alert is in a screen's feed it plays its rotation with the alert first, and the session takes the screen only once no alert is up. The screen's site: it must be one the session was sent to, or the session must be sent to every site. While a session has a screen, the screen's page in Digital Signage says "Live now". ## A screen shows the stage wall instead of the video That is expected for a session whose video is on another platform or that has no video. For a stream broadcast here, a screen shows the wall while the stream can't play yet, and falls back to the wall within about 20 seconds if its player can't load at all (some smart-TV browsers, or a blocked video service). ## Do break-room screens cost viewer minutes? A screen playing a stream broadcast here counts as one viewer for viewer minutes, like a person watching, for as long as it plays. A screen that can't play the stream (an older smart-TV browser, a blocked video service) shows the stage wall instead and adds nothing. A session whose video is on another platform, or that has none, has no viewer minutes, so screens showing its stage wall add nothing to its flat charge. Screens are never counted as people: they are left out of the live viewer count and unique viewers, and listed separately in **Reach by location** with the minutes each one played. --- ## Reach by location ## Who can see Reach by location? A session's host, its moderators (including Town Halls contributors) and admins see it on the session's page once it has gone live. Admins also see it in **Apps → Town Halls → Analytics**, for one session at a time from the latest 20. Other employees don't see it. ## How is reach counted? Of the people the session was for — its audience when it has one, otherwise every active member — it counts how many joined, by site and by region (the districts and regions above the sites). Each person counts at their own site in your company (their primary location, else their first); people with no location are counted under **No site set**. Someone who joined from outside the audience is counted separately ("Plus N people from outside the session's audience"), so no row reads over 100%. Department isn't shown: it isn't held per company, so it can't be counted reliably for yours. ## Why are some sites counted in "Other", or a region left out? To keep anyone from being identified. Sites with fewer people than your company's smallest report group (5 by default, set under **Admin → Compliance → Retention & Legal Holds**) are counted together in **Other**. A region is left out when a smaller group's figures could be worked out from it, and an **Other** row that is itself below that size shows no figures. When the whole audience is smaller than that, the card says there were too few people to show reach without identifying anyone. ## Reach says the session's audience no longer exists The audience the session was limited to has been deleted, so there is nothing to measure against. The card still says how many joined. --- ## Licensing and limits ## Does Town Halls require a licence? No. Town Halls is a pay-as-you-go app billed in platform credits (see **How is billing calculated?**). It is available to every tenant without a separate license purchase. An admin enables it from **Admin → Apps → All Apps**. ## How is billing calculated? Town Halls is pay-as-you-go, drawn in platform credits from your company's credit balance. What a session costs depends on where its video comes from: | Session | What is charged | Rate | |---|---|---| | Streamed here (your encoder to Town Halls) | Broadcast minutes — the stream's wall-clock length, rounded up to the next whole minute when it ends | 20 credits per broadcast minute | | Streamed here | Viewer minutes — the minutes each person actually watched, added up across everyone | 5 credits per 10 viewer minutes | | Video on another platform, or no video | One flat charge per session, when its room closes | 500 credits per session | Viewer minutes come from the session's own attendance: each viewer's time runs from when they opened the watch page to when they left, or to their last sign of watching plus 30 seconds if their tab closed without saying goodbye — and a page left open while a laptop slept stops counting two minutes after its last sign of watching. Only the time while the stream was actually broadcasting counts: waiting on the page before your encoder connects, or after it stops, is never billed. A Digital Signage break-room screen playing the stream counts as one viewer too. A 90-minute all-hands watched throughout by 1,700 people is 90 broadcast minutes (1,800 credits) and 153,000 viewer minutes (76,500 credits). Before you go live, the host console shows the likely cost for the session's audience, and the schedule form shows it before you save. There is no monthly minimum. Sample sessions are never charged. When you stream through your own Mux account, Town Halls draws no platform credits for those streams — Mux bills your Mux account directly. ## Are there limits I should know about? | Limit | Value | |---|---| | Chat message length | 500 characters | | Question length | 1,000 characters | | Question rate limit | 3 questions a minute per person per session | | Chat rate limit | 5 messages per 10 seconds per viewer per session | | Stage wall | The question on stage plus the next 4 by votes; 6 top questions when nothing is on stage | | Stage wall display link | No expiry — works until a moderator makes a new link | | Your anonymous questions on a device | The newest 20 per session, for the 3 people most recently signed in there, in their 3 latest anonymous sessions | | Reach by location — smallest group shown | Your company's smallest report group: 5 by default, never lower | | Catch me up refresh | One summary shared by everyone who asks, refreshed at most once a minute | | Signed playback token lifetime | 6 hours | | Live-viewer heartbeat window | 2 minutes (a viewer without a heartbeat within this window drops out of the active count) | | Sync log retention | 90 days | | Poll minimum options | 2 (one per line) | --- ## More help - [Town Halls Overview](/help/livestreaming_app_overview) - Ask AI — the assistant answers Town Halls questions from these articles. **Keywords:** faq, livestreaming, broadcast, town hall, go live, stream key, recording, playback, signed playback, polls, Q&A, catch me up, encoder, RTMPS, Mux, chat, not working, stage wall, display link, QR code, anonymous questions, names on questions, digital signage, break-room screens, reach by location, town-halls --- # Training App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run Training: courses, learning paths, quizzes, certificates, enrollment automations, retakes and attempt history, compliance reporting, learner ratings and Q&A, and partner content. # Training ## 1. What it is Training is a native learning management system. Admins author courses from text, video, documents, SCORM packages, licensed partner content or AI roleplay practice. They sequence courses into learning paths, gate progress with quizzes, and issue branded certificates on completion for courses set to **Issue Certificate of Completion**. Courses can also award skills and certifications to the employee's Skills & Credentials profile. - **Enablement:** Training requires a licence and is off by default. An admin enables it from Admin → Apps → All Apps. - **Who administers it:** a Training admin is anyone who is an HR Admin, an Admin or above, or an app admin for Training. - **Where learners use it:** on the web, on a phone browser, and in the native mobile app. The mobile app shows Training as a bottom bar of tabs: **My Learning**, **Catalog**, **My Records**, and **My Team** for people managers. Authoring, enrolling and settings are admin work and stay on the web. - **What it is not:** Training is not Training Connect. Training Connect syncs employees and training records with an external LMS (Cornerstone, Workday, etc.). It comes with the Training app and has its own settings page: in the Settings Hub it is the **Training Connect — External LMS Sync** card, beside the **Training** card. Training is the native, built-in LMS. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps → Training** and enable the app for your business. 2. Go to **Training → Settings** and review the defaults. The three that matter most up front: - **Allow Self-Enrollment** (on by default) — lets employees browse the catalog and enroll themselves. Turn it off if every enrollment must be admin-assigned. - **Require Passing Quiz** (on by default) — learners must pass every required quiz lesson before the course marks as complete. - **Manager Notifications** (on by default) — emails a learner's manager when they complete a course. 3. Create at least one course (**Training → Content → Courses → New Course**). Choose a **Delivery Mode**: **Self-paced** (learners work through lessons on their own) or **Instructor-led** (learners register for scheduled sessions). 4. Publish the course. A self-paced course needs at least one lesson before it can be published. An instructor-led course is delivered in sessions, so it can be published without lessons. Until published, a course is a draft visible only to admins. 5. Enroll learners — manually from **Enrollments → Manage Enrollments**, through an automation (**Enrollments → Automations**), or by letting employees self-enroll from the Course Catalog. 6. Confirm it worked: enrolled employees see the course on their **My Learning** page. Admins see enrollment counts on the **Dashboard**. **Silent-until-paired:** An instructor-led course is assignable the moment it is published, but learners cannot actually attend until an admin schedules at least one session on the course's **Sessions** tab. An automation that assigns a required instructor-led course with no upcoming session warns you about it. Optionally, set up **Categories** and **Custom Fields** (both under **Content**) to organize courses and add structured metadata such as regulation type or audience. Optionally, require approval before a course goes live: under **Admin → Approval Workflows**, create an enabled workflow for Training with the **Course publication** process and at least one approval level. From then on, Training admins and the course's Instructors see **Submit for approval** where **Publish** was, and **Withdraw request** while it is pending. Approval does not publish the course: **Publish** is offered once the request is approved. For a self-paced course, an approval covers the one draft version it was submitted for, so each new version needs its own. Publishing again a course that was live before (after **Unpublish**) needs no new approval. ## 3. How it fits together **Courses and lessons** — A course is the unit of learning. Each course contains lessons, and each lesson is one of seven types: text, video, document, quiz, SCORM, partner course (licensed content from Go1 or another partner), or practice (an AI roleplay scenario from Practice Hub that the learner must pass). The practice type is offered only when Practice Hub is enabled. Each lesson can be marked required or optional; only required lessons count toward completion progress. **Video lessons** — YouTube, Vimeo, Bunny and uploaded videos play inside the lesson. Loom and Wistia videos can't be played inside the course: the lesson says so and offers a link that opens the video in a new tab. **Course versions** — Courses are versioned. Admins edit a draft version while the published version stays live. When the draft is published it becomes the new live version. A learner is pinned to the version they started on, so mid-course edits do not disrupt them. **Learning paths** — A learning path groups courses into an ordered sequence of steps. Each step holds one or more courses and can be required or optional. Completing every required step completes the path, which can issue its own certificate and skill awards. **Enrollments** — An enrollment ties one learner to one course. It tracks status (Enrolled, In Progress, Completed, Cancelled), progress, due date, and start and completion dates. Learning paths have their own enrollment, separate from the course enrollments inside the path. **Attempts** — A learner can hold **several** enrollments on the same course over time. Each one is an attempt. Only one is the *current* attempt, and only one can be *active* (Enrolled or In Progress) at a time. Nobody owes the same course twice at once, and their whole history is kept. Re-assigning a course does not overwrite the old record. It adds a new attempt and marks the previous one superseded. The earlier attempt keeps its status, progress, quiz results and certificate. A three-attempt history reads like this: ``` Attempt 1 Completed 100% Jan 2025 certificate issued (superseded) Attempt 2 Cancelled 45% Jun 2025 cancelled on re-assign (superseded) Attempt 3 Enrolled 0% Aug 2025 ← current ``` Open it from any learner's row on the Enrollments page: the row menu's **View History** item opens the **Attempt history** dialog. The list itself shows one row per learner — the current attempt. **Two things admins conflate here.** **Reset Progress** wipes the current attempt back to zero and leaves no record that the learner got further. **Re-assigning** starts a clean attempt and keeps the old one as evidence. For a re-certification, an audit, or anything you may need to prove later, re-assign — do not reset. A third action, **Remove**, takes the assignment off the learner's list entirely. **Cancelled is not the same as failed.** A cancelled attempt was closed out on purpose, with its progress frozen where it stood. A completed attempt is never cancelled: an earned certificate always stands. **Self-paced vs. instructor-led** — Instructor-led courses run in scheduled sessions: classroom, webinar or hybrid. Sessions have a capacity, a waitlist and an instructor. The admin schedules sessions; the learner picks one. **Training admins vs. per-course roles** — Training admins run everything. Beyond them, each course can have **Instructors** (can edit that course's content) and **Coordinators** (can manage that course's enrollments). Neither role reaches other courses or the Training settings. Separately, the **Permissions** settings let you extend three abilities past Training admins: creating courses, assigning training, and viewing reports. **Certificates** — When a course or learning path requires a certificate, completing it issues a branded PDF with a unique certificate number that anyone can verify. Design templates under **Content → Certificate Templates**. Each course uses a chosen template or falls back to the business default. **Quizzes** — Quizzes are standalone items attached to courses as quiz lessons. Each has a passing score, and can add a time limit, an attempt limit and shuffled questions. When **Require Passing Quiz** is on, every required quiz lesson must be passed before the course completes. **Skills & certifications** — A course or learning path can award skills or certifications from the Skills & Credentials catalog on completion. The award happens automatically in the background. How long a course-awarded skill stays valid comes from the course's own **Skill validity (days)**, or from **Default skill validity** when the course sets none. **Prerequisites** — A course can require other courses to be completed first. A prerequisite can be one of your own courses or a system course. **Selling courses** — Commerce is off by default. Turning on **Sell Courses** adds a **Commerce** section (Purchases, Promo Codes, Bundles) and the learner's cart, wishlist, purchase history and gifts. Licensing partner content does not need it. **Cross-app integrations:** - **Skills & Credentials** — course completions grant skills. Inspections and Frontline Execution can require a training course before work begins. - **SOP Hub** — completing a course linked to an SOP automatically verifies the SOP's training requirement. - **Recognitions** — a course completion can create an automatic recognition. - **Levels & Badges** — completing a course awards points. - **Policy Hub** — policies can link to required training courses. - **Onboarding Hub** — onboarding plans can include training courses. ## 4. Running it ### Enrolling learners 1. Go to **Training → Enrollments** and click **Enroll Users**. 2. Pick the course or learning path, choose the people, and optionally set a due date. 3. When **Notify learners** is ticked (it is by default), enrolled learners are notified in the app, and by email when they have an address. Either way, they see the course on their **My Learning** page. ### Re-assigning training someone already has Re-assignment is part of the enrolling flow, not a per-row action. Only people in your selection who already hold a record are affected. 1. In **Enroll Users**, pick the course or learning path and the audience as normal. 2. Under **If someone already has this**, choose one of: - **Skip them** (the default) — nobody who already has it is touched, finished or not. - **New attempt if completed** — only people who finished it get a new attempt. - **New attempt even if not completed** — everyone who has it gets a new attempt. Unfinished attempts are cancelled and kept as a dated record. 3. For a **learning path** only, choose under **For a learning path, the new attempt counts**: - **Honor prior completions** (the default) — courses already finished still count, so the new attempt starts part-way through. - **Force retake** — the new attempt starts at 0% and every course is taken again. Use this after a policy change invalidates old completions. 4. Enroll. The result reports how many were re-assigned and how many were skipped. A course retake always starts at zero, which is why the second choice appears only for learning paths. **Letting learners retake a course themselves.** Turn on **Allow Self Retake** on the course. A learner who completed it then sees a **Retake course** button; their earlier completion and certificate stay on their transcript, marked superseded. ### Setting up enrollment automations 1. Go to **Training → Enrollments → Automations** and create a new one. 2. Choose what it does: **Assign training to people** or **Send reminders & messages**. 3. Choose a trigger: Calendar Date, User Profile Date (such as hire date) or On Course Completion. Where job-change tracking is switched on for your environment, Attribute Change is offered too. To re-enroll people as a certification runs out, use **Reassign when** in step 5 and pick days **Before** or **After** **Certificate Expiry**. 4. Define the audience: **All Network Users**, **Specific Users**, or **Select User Criteria** (department, location, role and so on). 5. Add the courses or learning paths, with optional due-date offsets, and choose **Assign**, **Reassign** or **Assign & Reassign** for each. A reassigning course also sets **Reassign when**: a number of days before or after **Certificate Expiry** or **Course Completion**, or a fixed date. 6. Activate the rule. It runs on its trigger, and **Run Now** on its detail page runs it on demand. For a User Profile Date, On Course Completion or Certificate Expiry automation, Run Now enrolls only the people that day's run would, not everyone the criteria cover. **Due-date and overdue reminders go out without an automation.** Each morning, learners are reminded 7, 3 and 1 day before a course or learning path is due, then weekly while it is overdue, for up to 90 days. A **Send reminders & messages** automation that covers a course replaces those reminders for that course with its own schedule and recipients. ### Licensing partner content Partner content lives under **Content → Partner content**. Browse licensed courses in **Partner Catalog** and manage seat-based licences in **Course Licenses**. A partner course plays as an ordinary lesson inside a native course, so the learner never leaves the platform. ### Reviewing analytics and reports 1. **Training → Insights → Analytics** shows enrollment counts, completion rates and top courses over a date range you choose. 2. **Training → Insights → Reports** offers six reports, each exportable to CSV: Enrollment, Completion, Learner Progress, Quiz Performance, Compliance Status, and Learning Path Progress. 3. To have a report emailed on a cadence, click **Schedule** on its page. The schedule keeps the filters on screen. Choose daily, weekly or monthly and up to 50 recipients. Each send goes out at 7:00 AM in your organization's time zone, with the CSV attached. Recipients must be people allowed by **Who can view training reports?**. Open **Scheduled reports** on the Reports page to **Edit**, **Pause**, **Send now** or **Delete** a schedule. Training admins see every schedule; other report viewers see their own. The **Compliance Status** report covers training that has a due date. It opens on training that is overdue or due in the next 7 days. Narrow it by **Course** and **Department** (the learner's department). The **Compliance Status** filter switches between **Overdue or due soon**, **Overdue**, **Due soon**, **Completed** and **All**. For the two "due soon" views, **Due within** sets how far ahead to look: 24 hours, 7 days, 14 days or 30 days. Cancelled enrollments never appear. Export CSV uses the same filters. ### Using AI to create content Three AI tools help authors, and each has its own switches in Settings: - **The Training Agent in Ask AI.** A Training admin can ask it to generate a course from a topic, convert a PDF or an image into a course (save Word and PowerPoint files as PDF first), generate quiz questions, or translate a course. Course Instructors can also ask it to rewrite lesson text on their own courses. Courses it creates are saved unpublished for review. - **Create from Document.** A Training admin can also upload the file directly at **Training → Content → Courses → Create from Document**: a PDF or an image, up to 15MB (save Word and PowerPoint files as PDF first). Optionally set a course title and draft a ten-question quiz from the content. The course is saved as a draft; nobody is enrolled and nothing is published. - **Describe-to-Fill.** A bar at the top of the course, lesson, quiz, learning path and certificate template forms. The author describes what they want and AI drafts the form fields. It never saves anything on its own. ## 5. Settings All settings are at **Training → Settings**. Defaults below apply until an admin saves a different value. | Setting | Section | Default | What it changes | |---|---|---|---| | Allow Self-Enrollment | General Settings | On | Off, only admins and automations can enroll learners. | | Require Passing Quiz | General Settings | On | Learners must pass every required quiz lesson before a course completes. Admins can still mark an enrollment complete. | | Manager Notifications | General Settings | On | Emails a manager when one of their reports completes a course. Also controls the manager copy on reminder automations set to "Learner & Manager". | | Send Training admin alerts to this group | General Settings | Blank | Names a group (your L&D team, whoever owns a partner contract) to be told about partner-content and quiz alerts as well. A lesson a learner cannot play goes to the course's Instructors and Coordinators, a partner licence notice to whoever bought the licence, and a learner who has used up their quiz attempts to their manager and the course's Instructors and Coordinators. When one of those has nobody to tell, the group is told instead of the Training app admins and the other people the alert would fall back to, so add anyone who should still hear of it to the group. Blank, a blocked lesson on such a course goes to the Training app admins, then to anyone who holds those roles on another course or is designated HR staff, and only then to every business administrator. | | Sell Courses | General Settings | Off | Shows the Commerce section and the learner's cart, wishlist, purchase history and gifts. | | Default skill validity | General Settings | No Expiry | How long a skill a course awards stays current when the course sets no Skill validity of its own. It does not change the Certificate of Completion, which never expires, or a certification, which keeps the validity set for it in Skills & Credentials. | | Enable Training Agent | Training Agent | On | Lets people ask the Training Agent questions in Ask AI. | | Auto-assign required training to new hires | Training Agent → Autonomous Operations | Off | Enrolls people hired in the last 30 days in the training your rules say they need. | | Remind employees about expiring certifications | Training Agent → Autonomous Operations | Off | Warns employees whose course-awarded certification is close to expiring. Training sends nothing for a certification that Skills & Credentials announces itself (its expiry alerts or its agent) or that an active Safety Hub requirement covers. While Skills & Credentials sends them, this switch and the lead time are disabled, with a note saying why. | | Certification reminder lead time | Training Agent → Autonomous Operations | 7 days | How many days before expiry that warning goes out. | | Enable AI Course Generation · Document to Course Conversion · AI Quiz Generation · AI Lesson Text Editing · AI Course Translation | AI Content Creation | On | Each switch turns the matching Training Agent ability on or off. Document to Course Conversion also shows or hides the **Create from Document** button on the Courses page. | | Enable AI Describe-to-Fill on authoring forms | AI Content Creation | On | Off, the Describe-to-Fill bar is not shown. | | Who can create a course? · Who can assign training to other people? · Who can view training reports? | Permissions | Training admins only | Extends each ability to groups you choose. Assigning training can also go to managers, for their own direct reports only. | | Portal Title | Learner Portal Branding | My Learning | The learner home heading and its sidebar label, on the web and the mobile app. | | Welcome Message | Learner Portal Branding | "Track your learning progress and complete assigned training" | The message under the learner home heading. | | Hide 'Powered by MangoApps' Footer | Learner Portal Branding | Off | Removes MangoApps branding from the learner portal footer. | | Accent Color | Learner Portal Branding | Blank (your company brand color) | Recolors highlights, buttons and progress bars in the learner portal only. | The two Autonomous Operations switches do nothing until autonomous operations are switched on in the **AI Console**. New businesses start in approval mode, so each action waits for a person to approve it. ## 6. More help - **Training FAQ** — specific setup and operating questions, limits, and troubleshooting. - Ask AI — the assistant answers questions about Training from these articles. **Keywords:** training, lms, courses, learning management, learning paths, quizzes, certificates, enrollment, scorm, instructor led training, ilt, compliance training, compliance status report, overdue training, course catalog, ai course generation, retake, reassign training, attempt history, re-certification, course ratings, course reviews, course q and a, my learning mobile, create from document, course publication approval, scheduled reports --- # Training FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Training — for admins, the managers who follow their team's training, and the employees who take it. # Training FAQ Answers to common setup and operating questions about Training. For what the app is and how to set it up from scratch, see the [Training Overview](/help/articles/training_app_overview). --- ## Setup ## Do I need to configure anything before employees can take courses? No. Once Training is enabled, you can create a course, publish it and enroll learners straight away. Two settings under **Settings › General Settings** are on by default, and they are worth checking first: - **Allow Self-Enrollment** lets employees enroll themselves in courses from the catalog. - **Require Passing Quiz** means a learner must pass every required quiz in a course before it counts as complete. ## Who can create and manage courses? HR Admins, business admins and Training app admins can do everything in Training. Under **Settings › Permissions** you can hand out three tasks without making someone a full Training admin: - **Who can create a course?** Anyone you add can start a course and becomes its Instructor. They still can't publish it or edit other people's courses. - **Who can assign training to other people?** You can choose **Managers — their own direct reports only** or specific groups. - **Who can view training reports?** This covers everyone's progress and scores, so there is no "everyone" option. Each course also has a **Roles** tab for per-course help. **Instructors** manage that course's content and lead its sessions. **Coordinators** manage its enrollments and session rosters but can't change content. ## Can a course need approval before it goes live? Yes, if you turn it on. It's optional: under **Admin › Approval Workflows**, create a **Course publication** workflow. After that, a Training admin or the course's Instructor sees **Submit for approval** where **Publish** used to be. Approvers are notified. While the request is open, the person who can submit it can also click **Withdraw request**, revise the course and submit it again. Coordinators can't submit a course. Approval doesn't publish the course. It makes **Publish** available, and someone still has to click it. For a self-paced course, an approval covers one version: approving v2 doesn't let v3 go live, so each new version needs its own approval. A course that was live before and was then unpublished can be published again without approval. --- ## Permissions and access ## Why can't I enroll myself in a course? You can only enroll yourself when two switches are both on. The first is your company's **Allow Self-Enrollment** setting. The second is the course's own **Allow self-enrollment from catalog** option. When either is off, the course still appears in the catalog but shows **View details** instead of **Enroll**. Ask your Training admin to assign it to you. ## Why can't a manager see a team member's training progress? The **Team Dashboard** shows a manager only their direct reports. If the employee doesn't report to that manager, they won't appear. HR Admins, business admins and Training app admins see every employee. A person with no direct reports and no admin role can't open the team pages at all. --- ## Day-to-day ## How does a course count as complete? A course is complete when the learner has finished every required lesson in the course version they were enrolled in. If **Require Passing Quiz** is on (the default), each required quiz also needs a passing attempt. For an instructor-led course, session attendance counts instead of lesson progress. A Training admin, or the course's Instructor or Coordinator, can also use **Mark Complete** on an enrollment. When a course completes, the platform: - issues the Certificate of Completion, if **Issue Certificate of Completion** is on for the course; - grants any skills or certification the course awards; - emails the learner's manager, if **Manager Notifications** is on (the default); - updates the learner's progress on any learning path that contains the course. ## What lesson types can I add to a course? Seven types are available: - **Text**: a reading with rich text and images. - **Video**: an uploaded file up to 500 MB, or a link. YouTube, Vimeo and Bunny links play inside the lesson. Loom and Wistia videos can't be played inside the course; the lesson offers a link that opens them in a new tab. - **Document**: a PDF, Word, PowerPoint, Excel, text or RTF file under 50 MB. - **Quiz**: a quiz from your quiz library. - **SCORM**: a SCORM 1.2, SCORM 2004, xAPI, cmi5 or AICC package in a .zip under 100 MB. - **Partner course**: a course you license from a content partner such as Go1 or OpenSesame. - **Practice**: a scenario from Practice Hub (only when Practice Hub is enabled). ## How do automations enroll people automatically? Automations live under **Enrollments › Automations**. Each one either **assigns training to people** or **sends reminders and messages**. An assign automation starts from one of three triggers: - **Calendar Date**: runs once on a date, or repeats on a schedule. - **User Profile Date**: runs on, before or after a profile date such as hire date. - **On Course Completion**: runs when someone completes any of, or all of, the courses you pick. A fourth trigger, **Attribute Change**, is offered only where job-change tracking is switched on for your environment. You narrow who is included with criteria such as **Role**, **Department**, **Location**, **Job title**, **Hire date**, **Employment type**, **Cost center**, **Division**, **Custom field** or **Group**. **Preview** shows who would be matched before you commit. ## How do I give experienced people a different programme from new starters? Put each experience tier in a **group** and point training at the group. Training has no tier setting of its own, and it doesn't need one: a tier is a set of people, and groups are how the platform names a set of people. 1. Under **Admin › Groups**, add a group for each tier you use, for example "First trip" and "Experienced hands". A group can list people by hand, or match them by attributes such as job title, job level or hire date, so it keeps itself up to date. 2. In **Enrollments › Automations**, add one assign automation per tier and narrow it with the **Group** criterion: the full induction courses for the first group, the refresher for the second. **Preview** shows who each one would enroll. A course's **Difficulty Level** (Beginner, Intermediate, Advanced) is a label on the course for the catalog. It does not decide who is enrolled. Onboarding works the same way: an onboarding template's **Audience** is a group, so each tier can get its own plan. ## How do I make a course award a skill or certification? Open the course and go to **Completion & Certificate**. The **Skills & Credentials integration** section there lists what the course awards. Pick any number of skills under **Awards skills**. Pick at most one under **Awards certification**. A learning path has the same section. You can also set this up from the credential's side. In the Skills & Credentials app, a credential's form has a **How this is earned** section with a **Courses that award it** picker. Both places edit the same link, so a change made in one shows up in the other. Because a course awards at most one certification, a course that already awards a different one is greyed out in that picker, marked **"— already awards …"**. Remove the other certification from the course first. The picker lists only published courses. ## Does a certificate expire? The **Certificate of Completion** never expires. It is permanent proof that the learner finished the course. Expiry applies to what the course awards: - **A certification** expires after the course's **Certification Expiry (days)**. If that is blank, the certification's own **Standard validity** from Skills & Credentials applies. If neither is set, it never expires. - **A skill** expires after the course's **Skill validity (days)**. If that is blank, the **Default skill validity** setting in Training Settings applies: **No Expiry**, **90 Days**, **180 Days**, **1 Year** or **2 Years**. ## How do I re-enroll people automatically when their certification expires? Create an assign automation for the course and set **Perform** to **Reassign** or **Assign & Reassign**. Then set **Reassign when** to a number of days **Before** or **After** **Certificate Expiry**. The automation re-enrolls each person whose certification from that course expires on that day. Separately, the **Remind employees about expiring certifications** option on the Settings page sends reminders ahead of expiry, once autonomous operations are switched on in the **AI Console**. Its **Certification reminder lead time** accepts 1–30 days and defaults to 7. Training stays quiet when another app already announces the expiry: it sends nothing while Skills & Credentials announces your expiries itself (its expiry alerts or its agent), and nothing for a certification an active Safety Hub requirement covers. Those apps send the reminder instead. While Skills & Credentials sends them, both settings are disabled on the Settings page, with a note saying why. ## How do learning paths work? A learning path groups courses into ordered **steps**. Each course in a step is either **Required** or **Optional**. A step can also ask for a set number of its optional courses, such as "any 2 of these 4". The path is complete when every step's requirements are met. **Show steps in order** marks the steps after the learner's current one as Locked. This is guidance, not a hard lock: learners can still open any course in the path. Paths have their own enrollments and completion tracking. They also have their own self-enrollment option, which is off by default. ## Can I duplicate an existing course? Yes. The copy includes the course's lessons and is created unpublished, so you can edit it before anyone sees it. A copy of one of your own courses is titled "(Copy)", then "(Copy 2)" and so on. A copy of a catalog course keeps its title and becomes your own editable course. ## Can I delete a course? A Training admin can delete a course from its **Edit course** page, in the **Danger Zone** panel (choose **Edit** from the course's row menu on **Courses**, or open the course and click **Edit course**). Deletion is refused in two cases: - anyone is enrolled in the course, including people who completed it; - an SOP or a policy links to the course as its training. Remove the link first. The Danger Zone also offers **Archive Course** for a course that people are enrolled in, and for a course that has been published and still has a lesson or session to publish. An archived course is unpublished and leaves the catalog, and every learner's record and certificate stays. Publishing it again restores it, which needs at least one lesson in a self-paced course. A course with nobody enrolled that has never been published, or has no lesson left, can only be deleted. Ask AI can't delete or archive a course. ## Can I pass a whole team at once? No. There is no action that passes everyone at once. When a learner has genuinely finished, a Training admin, or the course's Instructor or Coordinator, can use **Mark Complete** on that person's enrollment. Ask AI can do this too, one enrollment at a time, after you confirm it. **Require Passing Quiz** (Training → Settings) applies to every course in the company, not to one team or one course. ## Can I add my certificate to LinkedIn? Yes. Open the certificate from **My Records → Certificates** and choose **Add to LinkedIn**. LinkedIn opens its "Add license or certification" form with these filled in: - the course or learning path name; - your company as the issuing organization; - the issue month and year; - the certificate number and its verification link; - the expiry month and year, when the course granted a certification or licence that expires (the completion certificate itself never expires). You review it and save it in LinkedIn yourself. Nothing is posted for you, so add each certificate on its own. ## Can a training report be emailed on a schedule? Yes. Click **Schedule** on any report page. The schedule keeps the filters you had on screen. Or click **Scheduled reports** on the **Reports** page to see every schedule and create new ones. Each schedule emails the report as a CSV file daily, weekly or monthly (on a day from 1 to 28). Emails go out at 7:00 AM in your organization's time zone. From the list you can **Pause**, **Resume** or **Send now**. You can add up to 50 recipients. Each one needs an email address and must be allowed to view Training reports under **Who can view training reports?** Training admins manage every schedule. Anyone else who can view reports manages only their own. --- ## When something looks wrong ## "I finished all the lessons but the course still says In Progress" This is usually a quiz the learner hasn't passed yet. When **Require Passing Quiz** is on, a required quiz needs a passing score, not just a submission. The default pass mark is 70%. If the course has no quizzes, check that the learner finished every required lesson in their own course version. Lessons added in a newer version don't count toward an existing enrollment. An admin, Instructor or Coordinator can use **Mark Complete** if the learner genuinely finished. ## "My employees didn't get enrolled automatically" Date-based automations are checked once a day, in the early hours (UTC). An "On the hire date" automation picks up the people whose hire date is that day. Check three things: 1. The automation is active. An inactive automation never runs, and **Run Now** refuses to run it. 2. The criteria match the employee's profile. **Preview** lists everyone the automation's criteria cover. For a User Profile Date, On Course Completion or Certificate Expiry automation it also says who **Run Now** would cover today, by your own calendar. 3. The employee's profile has the date the trigger uses, such as a hire date. To avoid waiting for the next daily run, open the automation and click **Run Now**. For a User Profile Date, On Course Completion or Certificate Expiry automation it enrolls only the people that day's run would, never everyone the criteria cover; its confirmation says how many. A run can be reversed from its history. Enrollments where the learner has already made progress are kept. If a person's hire date is often entered after that date has passed, set **Also catch up anyone whose day for this automation was in the last … days** on the automation's User Profile Date trigger. The daily run and **Run Now** then also enroll anyone whose date fell in that many days before the trigger day and who has never had the training; someone who already had it, finished it, left it or was removed from it is not enrolled again. A date entered later than that window is not picked up: enroll that person by hand from **Enrollments → Manage Enrollments**. ## "The SCORM lesson says it's processing" Training imports the package itself after you upload it, and the lesson shows **Processing…** until the import finishes. If an import is still unfinished after 15 minutes, it is retried once. If it still doesn't finish, the lesson shows **Failed** with a message saying what went wrong. Re-export the package if the message asks you to, then upload it again. ## "Where did this certification on my profile come from?" Completing a course that awards a skill or certification adds it to your Skills & Credentials profile automatically. On **My Skills**, a credential earned this way carries a **Training:** badge naming the course. Admins and managers who open the credential's details see the same course under **Earned from**. --- ## Quizzes ## What question types can a quiz have? There are eight types: **Multiple choice**, **Multiple select**, **True / False**, **Text**, **Ranking**, **Matching (Text)**, **Matching (Image)** and **Hotspot**. Every type except **Text** is graded automatically. Text answers are graded by hand and don't count toward the automatic score. ## What quiz settings can I configure? - **Passing Score (%)**: 0 to 100. The default is 70. - **Max Attempts**: leave blank for unlimited attempts. - **Time Limit (minutes)**: leave blank for no time limit. - **Allow retakes**: **Always** (the default) or **Only after fail**. - **Cooldown between attempts**: a wait in minutes. Leave it blank for no wait. - **Score policy (which attempt counts)**: **Highest** (the default), **Latest**, **Average** or **First**. - **Question display**: **One question at a time** (the default) or **All questions on one page**. - **Shuffle question order** is off by default. **Show correct answers after submission** is on by default. --- ## Instructor-led training ## How do instructor-led sessions work? Set a course's delivery mode to **Instructor-led** to schedule live sessions. Each session is a **Classroom**, **Webinar** or **Hybrid** session and has 12 seats by default. When a session is full, new registrants join a waitlist. They are promoted in order as seats open. Open sessions also appear on Calendar's **Events** page. When your workspace uses Surveys, you can choose a **Session evaluation survey** under **Instructor-Led settings**. It is sent when a session is finalized, to attendees only; no-shows don't get it. --- ## Licensing and limits ## Are there limits I should know about? | Item | Limit | |---|---| | Certifications a course or path can award | 1 (skills: any number) | | Quiz passing score | 0–100 (default 70) | | Quiz max attempts | Unlimited unless set | | Uploaded video | 500 MB | | Document lesson | Under 50 MB | | SCORM / xAPI / cmi5 / AICC package | Under 100 MB, .zip | | Session capacity | Any positive number (default 12) | | Certification reminder lead time | 1–30 days (default 7) | | Automation due date | 1–365 days after the assigned, hire or role start date | | Default skill validity | No Expiry, 90 Days, 180 Days, 1 Year or 2 Years | | Promo code | Up to 50 characters; percentage discount up to 100% | --- ## More help - [Training Overview](/help/articles/training_app_overview) - [Skills & Credentials FAQ](/help/articles/skills_certifications_app_faq) - Ask AI — the assistant answers Training questions from these articles. **Keywords:** faq, course, enrollment, quiz, certificate, certification, skills, learning path, SCORM, self-enrollment, automations, recertification, Completion & Certificate, Courses that award it, instructor-led training, not complete, can't enroll, approval, scheduled reports, training --- # Users, Roles & Permissions **Category:** Business-configuration **Section:** Administration **Updated:** 2026-10-19 How to add users, assign roles, configure permissions, and manage job families — the admin guide to who can do what. # Users, Roles & Permissions ## 1. What it is User Management is the platform administration surface where you add people to your business, control what they can access, and organise them by role, location, and job function. Every other admin surface — scheduling, leave, recognition, compliance — depends on users existing here with the right role and location assignments. - **Access:** Admin → User Management. Requires the Administrator or Super Admin role. - **What it is not:** This is not where you configure SSO, password policies, or session timeouts — those live under Admin → Security Settings. ## 2. Standing it up 1. Go to **Admin → Roles** and confirm the four default roles exist (Super Admin, Administrator, Manager, Member). If the page is empty, click **Create Default Roles** — this creates the four system roles with their default permissions. 2. Go to **Admin → User Management** and add your first users. Each user needs at minimum a first name and either an email address or a user ID. A user ID is 6 to 16 letters or digits with no spaces or symbols; digits alone are fine, so a badge or employee number works. If you leave the password blank, someone with an email address is emailed an invitation to sign in as you save; without an email address, or while **Welcome Emails** are turned off, you are shown a temporary password to pass on instead. 3. When creating a user, assign an **organizational role** from the dropdown. The role determines their platform-wide access level. If no role is selected, the user defaults to Member. 4. Assign a **primary location**. If you skip this, the user is assigned to the business's default location. 5. Someone you gave a password yourself, or imported, is not sent an invitation: **send an invitation** from the user's profile page (or in bulk from the user list), or pass on the password you chose. An uninvited user exists in the system but cannot log in until they receive credentials. **Silent-failure pairing:** a user who was never sent an invite — imported, given a password you chose, or added while Welcome Emails were off — stays in "Pending Invitation" status. They appear in reports and scheduling but cannot sign in — the most common first-week support question. ## 3. How it fits together **Roles and permissions** — OneMango has four built-in system roles, ordered by hierarchy level: | System role | Hierarchy level | Immutable | What it can do by default | |---|---|---|---| | Super Admin | 1 | Yes | Everything, including **System Health** and **Sample Data** | | Administrator | 2 | Yes | Everything except the two Super Admin–exclusive features, **System Health** and **Sample Data** | | Manager | 3 | No | View and manage direct reports, approve leave/timesheets, limited scheduling | | Member | 7 | No | View own schedule, request leave, view broadcasts | The Super Admin and Administrator roles are **immutable** — their core attributes and permissions cannot be edited or deleted. Manager and Member permissions can be customised. Beyond these four, you can create **custom organizational roles** (e.g. Director, Regional Manager, Supervisor) with their own hierarchy level and permission set. When you create a custom role, you pick a source role to copy permissions from, then customise. **Organizational role vs. legacy role:** every user has both. The organizational role is the modern, permission-granular assignment. The legacy role (Super Admin, Admin, Manager, Member) is derived automatically from the organizational role and controls platform-level access checks — the ones phrased as "Admin or above" or "Manager or above". You manage organizational roles; the legacy role follows. **Job families and job titles** — a separate organisational structure from roles. A job family (e.g. "Sales", "Engineering") groups job titles (e.g. "Sales Representative", "Sales Manager"). Job titles are assigned to users on their employment profile. They are informational and for reporting — they do not grant permissions. **Job functions** — a free-text classification on the user's employment profile, entered in the **Job Function** field. Job functions can be organised into categories and loaded from industry templates. Like job titles, they are informational — they do not control access. **Invitation lifecycle:** a user moves through three statuses — Pending Invitation → Invited → Accepted. A user pending invitation has a record but has never been sent an invite. What the invite email holds depends on whether they have signed in before. Someone who has never signed in gets a one-time link to set their own password; it works for 7 days, and after that **Forgot password?** on the sign-in page sends a new one. Someone who has signed in before — to another business, for example — already has a password, so their invite has only their sign-in link and their password is left unchanged. Once the user signs in, they move to Accepted, and there is no invitation left to send: Send Invite no longer appears for them, and bulk Send Invites skips them and says who was skipped and why. An invite is a welcome email, so while **Welcome Emails** are turned off in **Admin → General Settings → Notifications (User Accounts & Sign-in)**, Send Invite and bulk Send Invites show disabled with that reason. ## 4. Running it ### Adding a single user 1. Go to **Admin → User Management → Add User**. 2. Fill in at least first name and email (or user ID). Set their organizational role, location, department, and manager. 3. Save. With the password left blank, we email them an invitation with a one-time link to set their own password, and the confirmation names the address it went to — there is no password for you to pass on. Without an email address, or while **Welcome Emails** are turned off, no invitation is sent: copy the temporary password from the dialog that opens, which shows it only once. ### Importing users in bulk 1. Go to **Admin → User Management → Import**. 2. Download the CSV template for the correct column headers. 3. Upload a CSV file (max 10 MB). Choose the import mode: - **Add only** — creates new users, skips any that match existing email/user ID. - **Add and update** — creates new users and updates fields on existing matches. 4. The import runs as a background job. Progress and errors appear on the import page. ### Bulk actions Select multiple users from the list (or use "Select all filtered" with at least one filter active), then choose an action: - Activate / Deactivate - Change role or assign organizational role - Change department, location, or manager - Send invitations - Delete (soft-delete with 30-day recovery) When a bulk action targets more than 100 users, it runs as a background job with a progress card instead of synchronously. ### Deactivating and deleting users - **Deactivate** keeps the user record but removes platform access. Upcoming shifts are automatically unassigned. - **Delete** is a soft-delete: the record is hidden for 30 days and can be restored from **More Actions → Deleted Users**. After 30 days, records become eligible for permanent deletion. - **Permanent delete** requires typing "PERMANENT DELETE" as confirmation and cannot be undone. - You cannot delete yourself, and only a Super Admin can delete another Super Admin. The system prevents deleting the last Super Admin. ### Managing roles and permissions 1. Go to **Admin → Roles** to see all organizational roles. 2. Click a role, then **Permissions** to open the permissions matrix. 3. The matrix shows feature keys (scheduling, employees, leave, analytics, etc.) against actions (view, create, edit, delete, manage, approve, export, and others). Toggle each cell on or off. 4. Permissions for Super Admin and Administrator roles cannot be modified — they are immutable. 5. To create a custom role, click **New Role**, set a name and hierarchy level, and pick a source role to copy permissions from. You are taken to the permissions page immediately after creation. Permissions can also be exported/imported as JSON or CSV, and pre-built templates can be applied to custom roles. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Organizational role | User profile → Employment tab | Member | Determines all platform permissions for this user | | Schedulable | User profile → Employment tab | On | Whether the user appears in shift scheduling — new users ARE schedulable by default | | On-Call Enabled | User profile → Employment tab | Off | Whether the user can be assigned on-call duty | | Overtime Eligible | User profile → Employment tab | Business default | Whether overtime calculations apply | | Employment Status | User profile → Employment tab | (blank) | Full-time, part-time, contractor — informational | | Required Fields | People › Admin › Profile Fields | First Name, Last Name, Work Email (always) | Which profile fields must be filled before a user can be saved | ## 6. More help - **[Users, Roles & Permissions FAQ](/help/articles/admin_users_and_roles_faq)** — specific questions, exact limits, and troubleshooting: why a user cannot sign in, why a permission is not taking effect, restoring a deleted user. - **Security & Sign-On** — password policies, SSO, session timeouts, and two-factor authentication. - Ask AI — the assistant answers questions about user management from these articles. **Keywords:** users, roles, permissions, admin users, organizational roles, super admin, user management, job families, job titles, job functions, invite users, deactivate user, import users, bulk actions, user roles, member, manager, administrator --- # Users, Roles & Permissions FAQ **Category:** Faq **Section:** Administration **Updated:** 2026-10-19 Answers to common setup and operating questions about users, roles, permissions, and job families — for the admin running it. # Users, Roles & Permissions FAQ Answers to common setup and operating questions about user management, roles, and permissions. For what the system is and how to set it up from scratch, see the [Users, Roles & Permissions Overview](/help/articles/admin_users_and_roles). --- ## Setup ## What are the four system roles, and can I change them? The four system roles are **Super Admin** (hierarchy level 1), **Administrator** (level 2), **Manager** (level 3), and **Member** (level 7). Super Admin and Administrator are **immutable** — their permissions cannot be edited and the roles cannot be deleted or deactivated. Manager and Member permissions can be customised through the permission matrix at Admin → Roles. ## What happens if I create a user without selecting a role? The user defaults to **Member**. Their legacy role is set to Member, and the system automatically assigns the matching organizational role immediately after the user is created. ## Do I need to send an invitation separately after creating a user? Not when you add one person with an email address and leave the password blank: the invitation is emailed as you save, and the confirmation names the address it went to. Everyone else — someone you gave a password yourself, someone imported, or someone added while **Welcome Emails** were turned off — is in **Pending Invitation** status: they exist in the system but cannot sign in until they have credentials. Click **Send Invite** on their profile (or use the bulk invite action) to email them an invite. Someone who has never signed in gets a one-time link in the invite to set their own password; someone who has signed in before (to another business, for example) already has a password, so their invite has only their sign-in link and their password is unchanged. A user is invitable only when they are active, have an email address on file, and are not already **Accepted** (signed in to this business). While **Welcome Emails** are turned off in Admin → General Settings → Notifications (User Accounts & Sign-in), Send Invite shows disabled with that reason. --- ## Permissions and access ## How do I create a custom role with specific permissions? Go to **Admin → Roles → New Role**. Set a name, hierarchy level, and pick a source role to copy permissions from. If you select Super Admin as the source, Admin-level permissions are copied instead — Super Admin permissions are not copyable. If no source is selected or the source is not found, Member permissions are applied. After creation you are taken directly to the permission matrix to customise. ## Which features are reserved for Super Admins only? Two features are excluded from the permission matrix for every other role: **System Health** and **Sample Data**. Only Super Admins can access system checks and load or clear sample data. The matrix offers only permissions the product actually checks. Pages such as Integrations, Settings, Reports and Roles are opened by the platform role (Admin, or Manager and above) rather than by a matrix box, so they have no box there. A role's existing grants on those features are kept but change nothing. ## What is the difference between an organizational role and the legacy role? Every user has both. The **organizational role** is the modern, permission-granular assignment you manage at Admin → Roles. The **legacy role** (Super Admin, Admin, Manager, Member) is derived automatically from it and controls the platform-level access checks phrased as "Admin or above" and "Manager or above". You never need to set the legacy role directly — it follows the organizational role assignment. ## What is the hierarchy level and why is there a gap between Manager (3) and Member (7)? The hierarchy level determines who is "above" or "below" whom for subordinate/superior checks. The gap between level 3 (Manager) and level 7 (Member) exists to accommodate custom roles. When default roles are created, the system also provisions Director (2), Regional Manager (3), People Operations Manager (4), District Manager (5), Location Manager (6), and Supervisor (7) to fill those levels. --- ## Day-to-day ## How do I import users in bulk? Go to **Admin → User Management → Import**, download the CSV template, fill it in, and upload the file. Maximum file size is **10 MB**. Two import modes are available: **Add only** (creates new users, skips matches on email or user ID) and **Add and update** (creates new and updates existing matches). The import runs as a background job. ## What can I do with bulk actions, and when do they run in the background? Select multiple users from the list, then choose an action: activate, deactivate, change role, change password, assign organizational role, change department, change location, change manager, assign skill, assign leave policy, update schedulable status, update on-call status, send invitations, or delete. When the action targets more than **100 users**, it runs as a background job with a progress card. The "Select All Filtered" option requires at least one active filter — it is blocked without one. ## How does deactivating a user differ from deleting one? **Deactivate** keeps the user record but removes platform access and automatically unassigns their upcoming shifts. You can also record termination details (date, type, reason, last working day). **Delete** is a soft-delete: the record is hidden for **30 days** and can be restored from Admin → User Management → More Actions → Deleted Users. After 30 days, records become eligible for permanent deletion. ## What stops me from accidentally permanently deleting users? Several guards. You must type the exact confirmation string **"PERMANENT DELETE"** (for selected users) or **"DELETE ALL USERS"** (for all soft-deleted users). You cannot delete yourself — the system removes the current user from any bulk deletion list. Only a Super Admin can delete another Super Admin. And the system prevents deleting the last Super Admin in the business. --- ## When something looks wrong ## "I created users but they say they can't log in" The most common cause: their invitation status is still **Pending Invitation**. Importing users, or adding someone with a password you chose or while Welcome Emails were off, does not send credentials. Go to their profile and click **Send Invite**, or select them in the user list and use the bulk **Send Invites** action. If Send Invite shows disabled, **Welcome Emails** are turned off — turn them back on in Admin → General Settings → Notifications (User Accounts & Sign-in). Someone who has signed in before keeps their password when invited, so if they have forgotten it, click **Email Reset Link** on their profile to email them a reset link, or **Reset Password** to replace their password with a temporary one shown on screen for you to share. **Password Reset Emails** are always on, so Email Reset Link is always available. Also verify the user is **Active** — an inactive user cannot sign in even if invited. ## "A user has the Manager job title but can't approve timesheets" Job titles and job functions are **informational labels** — they do not grant platform permissions. Access is controlled entirely by the **organizational role**. The user needs a role that has the `approve` action enabled for the relevant feature (e.g. timesheets) in the permission matrix at Admin → Roles. ## "We deleted someone last month — can we get them back?" Deleted users can be restored for **30 days** from Admin → User Management → More Actions → Deleted Users. After 30 days they are eligible for permanent deletion and cannot be recovered. If fewer than 30 days have passed, click **Restore** on the user's entry. --- ## Job families and job titles ## What is the difference between a job family, a job title, and a job function? A **job family** (e.g. "Sales", "Engineering") is a grouping container. A **job title** (e.g. "Sales Representative") belongs to a job family and is assigned to users on their employment profile. A **job function** is a free-text classification on the user's employment profile, entered in the **Job Function** field. All three are informational and for reporting — none of them grant platform permissions or control access. ## Can I delete a job family or job title that has employees assigned? No — the system **deactivates** them instead of deleting. For both job families and job titles, the system checks for assigned employees first. If employees are assigned, the record is marked inactive and preserved. If no employees are assigned, it is deleted outright. --- ## Defaults and limits ## Are new users schedulable by default? Yes. **Include in Shift Scheduling** is **on** by default. A newly created user will appear in shift scheduling unless you explicitly turn that setting off on their employment profile. On-call is the opposite — **Enable for On-Call Duty** is **off** by default. ## Is there a limit on how many users I can export at once? Exports of more than **1,000 users** run as a background job rather than as a synchronous download. There is no hard cap on the number of users you can export. --- ## More help - [Users, Roles & Permissions Overview](/help/articles/admin_users_and_roles) — what the system is and how to set it up. - [Security & Sign-On](/help/articles/admin_security_and_signon) — password policies, SSO, session timeouts, and two-factor authentication. - Ask AI — the assistant answers user management questions from these articles. **Keywords:** faq, users, roles, permissions, organizational roles, super admin, administrator, manager, member, custom role, hierarchy level, bulk actions, deactivate user, delete user, invite user, job family, job title, permission matrix --- # What Your Employees See **Category:** System-features **Section:** Advanced Features **Updated:** 2026-10-16 The personal surfaces every employee lands on — dashboard, Notifications and its Waiting on you list, My Stuff hub, profile, bookmarks, drafts, notes, trash, AI Home, and account settings — and how an admin controls what appears on each. # What Your Employees See ## 1. What it is Every employee in the platform has a set of personal surfaces that are not tied to any single app: their **home dashboard**, the **Notifications** page (the Inbox) with its **Waiting on you** list, a **My Stuff** hub that collects mentions, assignments, bookmarks, drafts, and notes, a **user profile**, an **AI Home** feed for items that need decisions, and **Account Settings** for notification, security, and availability preferences. These surfaces are always available — they do not require a separate app licence. - **What it is not:** these are not admin surfaces. The admin Dashboard Configuration, the Widget Gallery, and the Suggestion Center are admin tools that *control* what appears here — they are covered in the Dashboards & Widgets article. This article describes what the employee sees as a result of those settings. ## 2. Standing it up Most personal surfaces work out of the box with no configuration. The steps below cover the things that do require admin action. 1. **Dashboard layout** — go to **Admin → Dashboard Configuration**. Three starter dashboards are created automatically: **Default** (all employees), **All Managers**, and **All Admins**. Each is a published layout of widgets. To change what a group sees, drag widgets in or out of the layout, resize them, then click **Publish**. Unpublished edits stay in draft and do not affect live users. 2. **Group dashboards** — to give a specific audience a different home page, create a new dashboard and attach it to a **Group** (from Admin › Groups). A user sees the first published dashboard whose group they belong to; everyone else gets the Default. 3. **Widget Gallery** — go to **Admin → Widget Gallery**. Any widget an admin disables here disappears from every dashboard, the mobile home, and digital signage at once. Widgets whose required app is not enabled for the tenant are filtered out automatically. 4. **Profile field visibility** — go to **People › Admin › Profile Fields**. Each standard field can be set to visible to **Admins Only**, **Employee + Admins**, **Managers & Above**, or **Everyone**, and its edit permission can be **Employee Self-Edit**, **Manager Editable**, or **Admin Only**. Fields set to **Everyone** under **Visible to** are what a colleague sees on someone else's profile; the **Directory** checkbox adds the field as a column in the People directory (it needs Everyone visibility). 5. **Profile tab visibility** — admins can toggle entire profile tabs (Personal Info, Employment, Compensation, Compliance, and Benefits when the Benefits Management app is on) on or off from the Profile tabs switches at the top of the same Profile Fields page. 6. **Suggestion Center** — go to **Admin → Suggestion Center** (or the Loop app's Suggestions tab if Loop is enabled). Each suggestion service has rules that can be enabled, disabled, or tuned per tenant. Rules with a low action rate are auto-muted by a nightly job. ## 3. How it fits together **Dashboard groups and priority** — a dashboard group is a published layout of widgets tied to a group audience. Groups are ordered by priority (lowest position number wins). When an employee loads the home page, the platform walks the list top-to-bottom and serves the first published dashboard whose group includes that user. The non-deletable **Default** dashboard sits at position 1,000 and catches everyone who did not match an earlier group. An admin can also **mirror** one dashboard to another — the mirrored dashboard inherits its target's published layout and stays in sync automatically. **Personal layouts** — where an admin has turned it on for their dashboard, an employee sees a **Customize this page** link above the dashboard, at its right, on the desktop home page. It lets them drag cards into their own order, move a card between columns and hide cards they don't need, then **Save**. Hidden cards are listed under **Hidden cards** with **Show** to bring one back, and **Reset to company layout** undoes everything. They cannot add cards or change a card's size. The arrangement is theirs alone and follows them to the phone. It is off by default; see **Dashboards & Widgets** for how an admin turns it on and what happens when the dashboard changes later. **Widgets and roles** — each widget declares which roles it is appropriate for (member, manager, admin, super admin) and which apps it depends on. A widget only appears on a user's dashboard if all three gates pass: the widget is placed on the user's matching dashboard, the widget's required app is enabled for the tenant, and the widget is not disabled in the Widget Gallery. The platform ships with approximately 70 registered widgets across three tiers: platform widgets (always available), core-app widgets (conditional on business settings), and marketplace-app widgets (conditional on enabled apps). Admins can also create custom widgets (embeds, boards, quick-action sets) from the Widget Gallery. **Catch Me Up** — the start-of-day brief that appears on the default dashboard. It is the single summary an employee reads to learn what happened since they last checked in: what they missed, what needs their decision, and what changed. When the employee clicks **Mark all caught up**, the last-seen marker advances and the brief resets. This is the only place the marker advances — refreshing the page or navigating away does not clear it. **AI Home** — at **/ai-home**, this surface collects everything the AI-backed apps have flagged for the viewer, ranked by urgency. Items appear in scope sections: **My items** (personal), **Team ops** (direct reports, for managers), **Hiring** (recruiting pipeline), and **Admin** (business-wide actions only administrators see). Each item shows its priority, the recommended action, and a confidence indicator when the AI reasoned the recommendation. Managers can approve, reject, dismiss, or snooze items. Employees can create follow-ups to track items the AI should re-check. Snooze durations range from 1 hour to 7 days. Items that have been resolved move to the **History** page. **Notifications and "Waiting on you"** — at **/inbox**, the page titled **Notifications** lists what has been sent to the employee. Employees reach it from the bell's **View all** link or **Notifications** in the sidebar. Its left rail has a **Waiting on you** filter; on the phone it is a **Waiting on you** chip above the list. **Waiting on you** is the one place an employee finds everything they have been asked to read and confirm and have not yet confirmed: - must-read posts, broadcasts and alerts - Sites pages, policies and SOPs - job descriptions, and Frontline Execution posts to confirm Kinds whose app is off for your organisation are left out. The list is built from each app's own records, not from notifications. So an item stays listed even when the employee has muted that notification category. Overdue items come first, then the soonest due date, then the newest ask. Each row links to the page where the item is confirmed — **Acknowledge**, **Check in**, **Confirm on the page**, **Complete it** or **Confirm in My Day**. Past 25 items of one kind, a "more" link opens that kind on its own, paged. Two rules decide who is asked. Only someone a broadcast was actually sent to can acknowledge it; its author is not asked unless they were a recipient too. Authors are never asked to acknowledge their own must-read post. Employees can also ask Ask AI what they still need to confirm. It can confirm must-read posts and broadcasts in the chat after the employee approves a confirmation card. For every other kind it gives the link. Example: an employee has muted policy notifications. They still see an overdue policy at the top of **Waiting on you**, followed by two broadcasts they have not acknowledged. **Three counts that look alike** — employees mix these up, so it helps to know which is which: - The bell's red badge and the **Home** row on the Notifications page count notifications that ask something of the employee. The bell menu's header, "N waiting on you", is this number too — not the **Waiting on you** list. - **Waiting on you** counts confirmations still owed, whether or not a notification was ever sent. - **Catch Me Up** shows only must-read posts published since the employee last caught up. **Waiting on you** is the whole backlog. **My Stuff** — at **/my-stuff**, a unified hub showing a snapshot from each personal surface: the 8 newest bookmarks, the 5 most recent unfinished drafts, the 5 newest private notes, open task assignments (up to 20), @-mentions (up to 15), unread notifications, unread direct messages, and AI-drafted check-ins awaiting approval (up to 10). Each section links out to the full dedicated surface. **Bookmarks** — at **/bookmarks**, the employee's saved items. The bookmark button appears next to workspace messages, comments, tasks, wikis, policies, SOPs, library items, site pages, recognition posts, and recruiting jobs. Each bookmark can carry a personal note (up to 500 characters). Bookmarks can be sorted, filtered by type, and searched. **Drafts** — at **/drafts**, the employee's unfinished text. As employees type in workspace message composers, comment boxes, direct-message threads, broadcast or task composers, and communications, the platform auto-saves their work. The drafts page lists everything in progress so the employee can resume or discard it. **Personal Notes** — at **/notes**, a private scratchpad. Notes support voice recording — a voicenote is transcribed automatically, and the transcript becomes the note body. Notes can be converted into self-assigned tasks (when the Tasks app is enabled and self-assignment is allowed). Notes auto-save as the employee types. **Soft delete and Trash** — at **/my-trash**, a personal recovery surface. When an employee deletes a personal note, bookmark (that has a note attached), workspace message, comment, direct message, Drive item, task list, event, or workspace, the item is soft-deleted and recoverable for **30 days** — a direct message only until it is older than the organization's Messages retention window, when one is set; each item in Trash shows how long it has left. The trash page shows only items the viewer themselves deleted, groups them by type, and supports sorting by most recently deleted or soonest to expire. After 30 days, a daily background job permanently purges the item. Drafts are the exception: discarding a draft hard-deletes it and does not send it to trash. **User profile** — each employee has a profile page with tabs that vary depending on which apps are enabled and what the admin has configured. The possible tabs include Overview, Personal Info, Employment, Attendance, Time Off, Compensation, Benefits, Performance, Skills & Credentials, Compliance, Custom Fields, Audit History, and Login Activity. When a colleague views someone else's profile, they see a simplified peer card showing only the fields set to **Everyone** under **Visible to**. **Account Settings** — at **/account_settings**, five tabs let the employee manage their own preferences: - **Notifications** — per-category delivery preferences (in-app, email, push) - **Security** — password change and two-factor authentication enrolment - **Availability** — preferred days off, weekly hour range, weekend and holiday availability, maximum consecutive days (only visible when scheduling is enabled) - **Preferences** — language preference and meeting URL defaults - **AI Profile** — how the AI personalises its responses (communication style, detail level, technical level) ## 4. Running it ### Reviewing what a group's dashboard looks like 1. Go to **Admin → Dashboard Configuration**. 2. Find the dashboard group and click **Preview**. The preview renders the published layout with real data for your own account. ### Disabling a widget across the entire tenant 1. Go to **Admin → Widget Gallery**. 2. Find the widget and toggle it off. It is removed from every dashboard, the mobile app, and digital signage immediately — no republish needed. ### Tuning the Suggestion Center 1. Go to **Admin → Suggestion Center**. 2. Each service (Scheduling, Leave Management, Compensation, Training, and others) lists its rules with 30-day telemetry: how often each suggestion was shown and how often employees acted on it. 3. Toggle a rule off to suppress it, or click into a rule to adjust its thresholds. Changes take effect immediately. 4. Rules whose action rate drops below 5% over the last 30 days (with at least 5 impressions) are flagged **At risk** and will be auto-muted by the nightly sweep unless an admin re-enables them first. ### Configuring which profile fields employees can see and edit 1. Go to **People › Admin › Profile Fields**. 2. For each field, set the **Visibility** level (who can see it) and **Edit permission** (who can change it). 3. Set **Visible to** to **Everyone** for fields a colleague should see on someone else's profile, and tick **Directory** for those that should also be a column in the People directory. 4. To hide an entire tab, use the Profile tabs switches at the top of Profile Fields. ### Managing self-service profile editing 1. Go to **People › Admin › Settings**. 2. Turn **Enable Employee Self-Service** on or off (People › Admin › Settings › General). When off, employees cannot edit their own profile fields — only admins and managers can. 3. Under **Employee requests**, review **Let employees request changes, with approval** (on for new organizations). When on, employees can ask for changes to fields they cannot edit themselves, and the request goes through a manager or admin approval workflow before taking effect. ## 5. Settings ### Dashboard | Setting | Where | Default | What it changes | |---|---|---|---| | Dashboard group layout | Admin → Dashboard Configuration | Three starter groups (Default, All Managers, All Admins) with pre-set widgets | Which widgets appear on an employee's home page | | Personal layouts | Admin → Dashboard Builder → Dashboard actions (⋮) → Personal layouts… | Off | Whether the employees who get a dashboard can reorder and hide its cards for themselves | | Dashboard status | Admin → Dashboard Configuration | Published (for starter dashboards) | A dashboard in **Draft** status is never served to users; **Published** is live; **Unpublished changes** means edits are pending | | Widget Gallery disable | Admin → Widget Gallery | All widgets enabled | A disabled widget is hidden from every surface at once | ### Profile | Setting | Where | Default | What it changes | |---|---|---|---| | Field visibility | People › Admin › Profile Fields | Varies per field | Who can see each profile field (Admins Only / Employee + Admins / Managers & Above / Everyone) | | Field edit permission | People › Admin › Profile Fields | Varies per field | Who can edit each profile field (Employee Self-Edit / Manager Editable / Admin Only) | | Directory column | People › Admin › Profile Fields | Varies per field | Whether the field is a column in the People directory list (only for a field visible to Everyone) | | Profile tab visibility | People › Admin › Profile Fields (Profile tabs) | All tabs on (where the parent app is enabled) | Toggles entire profile tabs on or off for all employees | | Enable Employee Self-Service | People › Admin › Settings › General | On | When off, employees cannot edit their own profile fields (admins and managers still can) | | Let employees request changes, with approval | People › Admin › Settings › Employee requests | On for new organizations | When on, employees can ask for changes to fields they cannot edit themselves; each request goes through a manager/admin approval workflow before taking effect | ### Account Settings (employee-facing) | Setting | Where | Default | What it changes | |---|---|---|---| | Notification preferences | Account Settings → Notifications | Per-category defaults | Employees choose which notification categories to receive and their delivery channel (in-app, email, push) | | Security (password, 2FA) | Account Settings → Security | Password only | Employees can change their password and enrol in two-factor authentication | | Availability & shift preferences | Account Settings → Availability | No preferences set | Employees set preferred days off, weekly hour range, weekend/holiday availability, and maximum consecutive days (only visible when scheduling is enabled) | | Language preference | Account Settings → Preferences | Business default | The language translations render in for this employee | | AI profile | Account Settings → AI Profile | No profile | Employees can view how the AI personalises its responses (communication style, detail level, technical level) | ## 6. More help - **Dashboards & Widgets** — admin-side configuration of dashboard groups, the Widget Gallery, and widget authoring - **Notifications — Channels, Defaults & Opt-outs** — how notification delivery works and what employees can control - **Ask AI — What It Can Do and How to Govern It** — the AI assistant employees can use from any surface - Ask AI — the assistant answers questions about the employee experience from these articles. **Keywords:** dashboard, my stuff, employee home, customize this page, personal layout, user profile, bookmarks, drafts, personal notes, trash, AI Home, account settings, widgets, what employees see, employee experience, employee homepage, Catch Me Up, suggestion center, voicenote, soft delete, notifications inbox, waiting on you, what do I still need to acknowledge, must-read confirmation, pending acknowledgements --- # Wikis App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run the Wikis app — create, organize, and maintain collaborative knowledge documentation with templates, version history, and content governance. # Wikis ## 1. What it is Wikis gives your organization a structured, collaborative space for creating and maintaining living documentation. Authors write pages using a rich-text editor, organize them into a hierarchy of sub-pages, and tag them for cross-cutting discovery. Built-in version history, edit locking, and content freshness tracking keep the knowledge base accurate as it grows. - **Enablement:** Wikis requires a license and is disabled by default. An admin enables it from Admin → Apps → All Apps. - **What it is not:** Wikis is not a file repository. For storing and sharing files, folders, and external links, use Drive. For curated library collections of company resources, use Libraries. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Wikis**. The app appears in the side navigation once enabled. 2. Open **Wikis → Settings** and review the default configuration. The most important decisions are the **Edit Lock Timeout** (default 30 minutes) and the **Stale Wiki Threshold** (default 120 days). 3. Optionally create one or more **templates** under **Wikis → Templates**. Mark one as the default so a page started from **New Wiki** with no template picked starts from it. Templates are browsable by all users; only admins and Wikis app admins can create or edit them. 4. Grant access. Everyone who can use the app can view published wikis; who can create new pages is the **Who can create a wiki page?** setting (everyone, by default). To delegate administrative tasks — settings, reordering, trash recovery, template management — without granting a full admin role, assign users as **Wikis app admins** under **Admin → Apps → App Admins**. 5. Confirm it works: create a test page, publish it, and verify it appears in the browse tree and in Global Search (if the **Include Wikis in Global Search** setting is on, which it is by default). **Silent-until-paired:** the **Notify on Wiki Publish** setting is off by default. Until you turn it on — and optionally pick a recipient group under Settings — publishing a page does not notify anyone. ## 3. How it fits together ### Pages, sub-pages, and the browse tree Every wiki page can have sub-pages nested under it, up to 5 levels deep. The browse screen shows a tree on the left and the selected page's content on the right. Admins can drag pages into a custom order; users can sort by most recent, title, most viewed, or that custom order. A page starts as a **Draft** (visible only to its creator and admins), moves to **Published** (visible to everyone or to specific groups, depending on its visibility setting), and can be **Archived** by its manager or an admin. Deleting a page moves it to Trash along with all of its sub-pages, and the other people who created those pages are told (in a very wide delete, only the deleted page's creator is). The page's creator — or an admin — can restore it from **All Wikis ▾ → Trash**, which brings its sub-pages back with it. Everyone sees only what they may restore there: a member their own pages, a Wikis app admin the pages they can read, a business admin everything. ### Visibility and permissions Each page carries three independent permission controls, set by its manager (its creator, unless management was transferred) or an admin through the **Properties** drawer: - **Visibility** — who can read the page: **Everyone** (default), **Specific Groups** (selected groups from Admin › Groups), or **Only me** (private to the creator). - **Edit permission** — who can edit the content: **Admin and Creator** (default) or **Any User**. Admins can always edit a page. - **Comment permission** — who can comment: **Any User** (default), **Admin and Creator**, or **Nobody** — choose **Nobody** to turn commenting off entirely for a page. Additional per-page toggles: **Allow Duplication** (default on), **Allow PDF Export** (default on, gated by the app-level PDF export setting), **Show Author** (default on), **Show Table of Contents** (default on), and **Lock Editing** (default off — prevents all member edits regardless of edit permission). ### Edit locking When someone opens a page for editing, the app acquires an edit lock. It keeps renewing while the editor is open, and leaving the editor frees the page at once; if the editor's browser stops answering, the lock times out after the **Edit Lock Timeout** (default 30 minutes). Another user trying to edit sees a conflict dialog with the lock holder's name, role, and avatar. From that dialog they can: - **Ask edit** — send the holder a request by mail (**Send Mail**) or, when both of you can use Chat, **Send in Chat**, asking them to release the page. - **Notify when free** — subscribe to a notification that fires when the lock is released or times out. - **Break Lock** (admins and Wikis app admins) — take the lock over at once; the editor is told. Leaving the editor, or the lock timing out, notifies anyone who subscribed. ### Version history Every publish or edit of a published page creates a numbered version. Drafts do not create versions — they appear only once published. From **Wiki Tools › Version History**, any viewer can browse the version timeline, view the full content of any version, and compare any two versions side by side with a line-level diff. Users with edit permission can restore an earlier version, which creates a new version recording the restore. Management transfers also appear in version history. ### Tags Tags are free-text labels (up to 50 characters each) that cut across the page hierarchy. Filtering by a tag in the browse view shows a flat list of matching pages regardless of where they sit in the tree. ### Templates Templates are admin-managed starting points for new pages. Each template has a name, an optional category, a body, and optional icon, color, and cover image. One template per organization can be marked as the default — a page started from **New Wiki** starts from it unless the author picks a different template or chooses to start blank. Pages added with **Add sub-wiki**, Ask AI or the browser extension start blank. Every user can browse and preview templates; only admins and Wikis app admins can create, edit, or delete them. ## 4. Running it ### Reviewing the dashboard The Wikis dashboard shows KPIs and widgets tailored to the viewer's role: - **All users** see their own wiki count, draft count, bookmarked count, mentions count, total views on their pages, and views on their pages this month — plus widgets for their drafts, bookmarked pages, recently viewed, and recently updated pages across the organization. - **Admins** additionally see the organization-wide total, published, draft, archived, and stale counts, plus org-wide engagement (views this month), a most-viewed list, top contributors, recent activity feed, and a needs-attention widget listing business-wide drafts pending publish. ### Managing stale content Published pages not updated or confirmed still accurate within the configured **Stale Wiki Threshold** (default 120 days) show a **May be outdated** badge to everyone who can open them. Business admins also get the dashboard's Stale KPI, which links to a filtered list of all stale pages. Editing and saving a stale page, or its owner answering **Still accurate** when its review is due, clears the flag. The weekly review reminder (to the page's owner, else its owning team, else the person who manages it) is part of Content Governance in the admin area, not this setting. ### Transferring management The page's manager or an admin can transfer management via the page's **Wiki Tools** menu (**Transfer management**). The new manager must be an active member of the organization. The transfer is recorded in version history. If the transferring user can no longer view the page after the transfer (for example, a private or group-restricted page), they are redirected to the browse view rather than seeing an access-denied error. ### The page's owner **Properties › Owner** names who answers for keeping a page's content right — a person, a team, or both — separately from who manages it. Until one is named, the page's manager answers for it. Owners find their pages, with the date each is due for review, under **Content I own** in the account menu. ### Exporting to PDF When the app-level **Allow PDF Export** setting is on (default) and the page's own **Allow PDF Export** toggle is on (default), any viewer can download the page as a PDF from the page's **Wiki Tools** menu (**Export PDF**). ### Duplicating a page When a page's **Allow Duplication** toggle is on (default), its manager or an admin can duplicate it. The copy is created as a draft beside the original (same parent). The copy is a snapshot — subsequent edits to either page are independent. ## 5. Settings | Setting | Where | Default | What it changes | |---|---|---|---| | Enable Wikis AI Agent | Wikis → Settings | On | Lets Ask AI answer questions from wiki content and act on wikis | | Enable AI Writing Assist | Wikis → Settings | On | The "Improve with AI" menu inside the wiki editor | | Enable AI Cover Image Generation | Wikis → Settings | On | Generating a page's cover image from a text prompt | | Who can create a wiki page? | Wikis → Settings | Everyone | Who sees New Wiki and may create pages, on the web and through Ask AI | | Include Wikis in Global Search | Wikis → Settings | On | Whether published wiki pages appear in platform-wide search results | | Edit Lock Timeout (minutes) | Wikis → Settings | 30 | How long a page stays locked after its editor's browser stops answering. While the editor is open the lock keeps renewing | | Allow PDF Export | Wikis → Settings | On | Master toggle for PDF export across all wiki pages | | Stale Wiki Threshold | Wikis → Settings | 120 days | How long a published page can go without an update or a "Still accurate" before it shows a May be outdated badge. Choices: 90, 120, 365, or 730 days | | Notify on New Comments | Wikis → Settings | On | Whether the page's manager (and the author of a comment being replied to) receives a notification when someone comments | | Notify Users on @Mention | Wikis → Settings | On | Whether a user receives a notification when @mentioned in a wiki comment | | Notify on Wiki Publish | Wikis → Settings | Off | Whether users are notified when a wiki is published. Recipients are determined by the configured recipient group, falling back to app admins then business admins | ## 6. More help - **Wikis FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about Wikis from these articles. **Keywords:** wiki, wikis, knowledge base, documentation, knowledge management, wiki template, revision history, version history, edit lock, sub-wiki, wiki tag, stale content, pdf export, wiki comments, content governance --- # Wikis FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-18 Answers to common setup and operating questions about Wikis — for the admin running it. # Wikis FAQ Answers to common setup and operating questions about Wikis. For what the app is and how to set it up from scratch, see the [Wikis Overview](/help/articles/wikis_app_overview). --- ## Setup ## Do I need to configure anything before people can start using Wikis? No. Once you enable Wikis from Admin → Apps → All Apps, the defaults are ready to use: new pages start as drafts with edit permission set to **Admin and Creator**, comments open to **Any User**, and visibility set to **Everyone**. Global search inclusion, PDF export and the Wikis AI Agent (so people can ask Ask AI about wiki content) are all on by default. The only setting that is off by default is **Notify on Wiki Publish** — turn it on in Wikis Settings if you want a page's publication announced. ## Who can create wiki pages? Whoever the **Who can create a wiki page?** setting in Wikis Settings allows — everyone who can use the app, by default. The creator manages the page — its edit and comment permissions, through the Properties panel — until they transfer management to someone else. Only admins and designated Wikis app admins can access Wikis Settings, manage templates, and reorder pages. A deleted page's creator can restore it from **All Wikis ▾ → Trash** — including a page that went to Trash with the page above it; a Wikis app admin can restore any deleted page they can read, and a business admin any page. ## What is a Wikis app admin, and how do I designate one? A Wikis app admin is a non-admin user who has been granted app-level administrative access. You assign app admins from **Admin > Apps > App Admins**. An app admin can open Wikis Settings, manage templates, reorder pages, break edit locks, restore deleted pages they can read, and delete any comment. Editing, archiving, deleting or transferring other people's pages, and the Stale view, stay with business admins and each page's creator. --- ## Permissions and access ## Who can edit a page, and how do I change that? Each wiki page has its own edit permission, set by the page's manager or an admin in the Properties panel. The two choices are: 1. **Admin and Creator** (default) — only the page's manager (its creator, unless management was transferred) and admins can edit. 2. **Any User** — anyone who can read the page can also edit it. A page can also be closed to edits with the **Lock Editing** switch in Properties. Regardless of the setting, an archived page can be content-edited only by its manager and admins. ## How does page visibility work? Each page has a visibility setting in Properties: - **Everyone** (default) — all users in the organization can view it once it is published. - **Specific Groups** — only members of the selected groups (plus the page's manager and admins) can view it. - **Only me** — only the creator can view it. Admins can also access it. Unpublished drafts are visible only to their creator and admins. ## Why can't some of my employees see a wiki page? The most common causes are: the page is still in **Draft** status (only the creator and admins see drafts), the page is **Archived**, or its visibility is set to **Specific Groups** or **Only me**. Check the page's status badge and its Properties panel. Published pages with visibility set to **Everyone** are available to all users. --- ## Day-to-day ## How does edit locking work, and what if someone's lock gets stuck? When someone starts editing a page, an edit lock is automatically acquired. The lock prevents other users from making simultaneous edits. It keeps renewing for as long as the editor is open, and leaving the editor frees the page at once. If the editor's browser stops answering (a lost connection, a crash or a sleeping laptop), the lock times out after the **Edit Lock Timeout** set in Settings (default **30 minutes**, adjustable from **1 to 1,440 minutes**). When the page frees up, everyone who chose **Notify when free** is told. If a lock gets stuck, any admin or app admin can break it with **Break Lock** (in the page's **Wiki Tools** menu or the edit-lock dialog). The **Ask edit** button in that dialog lets a waiting user send the lock holder a notification (throttled to one every **10 minutes**). ## How does version history work? Every save of a published wiki creates a numbered version. Open **Wiki Tools › Version History** to open any previous version, compare any two versions side by side with highlighted additions and removals, and see who made each change and when. Restoring an earlier version creates a new version with a **Restored** label, so nothing is lost. Version history is only generated for published pages — edits to drafts are not versioned. ## Can I use templates, and who manages them? Yes. Admins and Wikis app admins create templates from the **Templates** tab — each template has a name (up to **100 characters**), a body, an optional category and icon, and an optional cover image. One template per organization can be marked as the default. When any user creates a new wiki, they can choose a template to pre-populate the page's structure and content. ## How do I transfer management of a wiki? Open the page's **Wiki Tools** menu and select **Transfer management**. Both admins and the page's current manager can transfer it. The new manager must be an active member of the organization. The transfer is recorded in version history. If the previous manager no longer has access to the page after the transfer (for example, a draft or a visibility-restricted page), they land on **All Wikis** instead. Transferring management does not change the page's **Owner** (below). ## What is a wiki's Owner? **Properties › Owner** names who answers for keeping a page's content right — a person, a team, or both. It is separate from who manages the page: naming an owner does not change who can edit, manage or transfer it. Until an owner is named, the page's manager answers for it. Owners find their pages, with the date each is due for review, under **Content I own** in the account menu. ## How deep can sub-wikis be nested? Pages can be nested up to **5 levels** deep (for example, Company > Product > Version > Section > Page). The Add sub-wiki action and the parent picker automatically prevent you from exceeding this limit. Existing hierarchies that were deeper than 5 levels before the limit was introduced still work — they just cannot be pushed deeper. ## What can Ask AI do with wikis, and what is left to admins? With the Wikis AI Agent on (**Wikis → Settings**), people can ask Ask AI to find, read and summarise wikis they can open, see a page's details, revisions and comments, and get counts such as how many wikis there are, which are most or least viewed and which are outdated. It only ever shows pages the person could open themselves. It can also write, and every write asks for a **Confirm** first, one wiki at a time (a request such as "delete every wiki" is declined): - **Create** a new page — always as a draft, and only for people the **Who can create a wiki page?** setting allows. - **Edit** a page's title or body — only where the person could press Edit on the web. A page with **Lock Editing** on can be changed by admins only, and Ask AI says so. - **Set a page's Owner** — for admins and the page's creator. - **Publish, archive, send back to draft or delete** — **administrators only** through Ask AI. A page's creator uses the **Wiki Tools** menu on the page itself. Ask AI cannot list who has read a page. Administrators and the page's creator can open the page's view count to see its **Viewed by** list. --- ## Notifications ## What notifications does Wikis send, and can I control them? Three switches in Wikis Settings turn whole notification types on or off for everyone: - **Notify on New Comments** (on by default) — the page's manager is told when someone comments on the page, and a comment's author is told when someone replies to it. - **Notify Users on @Mention** (on by default) — a user is told when mentioned in a comment. Mentions to users who cannot read the page are not sent. - **Notify on Wiki Publish** (off by default) — this app's admins, or the recipient group you choose, are told when a page is published. Users who cannot read the page are excluded. Wikis also sends notices that no Wikis Settings switch turns off: edits others make to pages you manage, management handed to or from you, pages moved to Trash, **Ask edit** requests, a lock taken over by an admin, and a page you asked about becoming free (**Notify when free**). Page review reminders are switched on under Content Governance in the admin area. Every Wikis notification, including the three above, also follows each person's own **Wikis** notification preference, where they choose in-app, email, or neither. --- ## When something looks wrong ## "I can't export this page to PDF" PDF export requires two things to be true: the app-wide **Allow PDF Export** setting in Wikis Settings must be on (it is on by default), and the page's own **Allow PDF Export** switch in Properties must also be on (also on by default). If either is off, **Export PDF** does not appear in the page's Wiki Tools menu. ## "My edits disappeared after someone else saved" Edit locking prevents simultaneous edits, and the lock keeps renewing while the editor is open. Someone else can save first only if the editor's browser stopped answering long enough for the lock to time out (the **Edit Lock Timeout**, default 30 minutes) or an admin broke the lock. Either way, the next Save opens a conflict dialog where **Duplicate as New Draft** keeps the unsaved text, and anything saved over can be recovered from **Wiki Tools › Version History**. ## "A wiki page looks outdated but nobody has touched it" Published pages that have not been updated or confirmed still accurate within the stale threshold show a **May be outdated** badge to everyone who can open them; business admins also see them under the Stale count and filter. The threshold is configured in Settings under **Stale Wiki Threshold** with choices of **90**, **120** (default), **365**, or **730 days**. This is informational — it does not change the page's status. Editing and saving the page, or its owner answering **Still accurate** when its review is due, resets the clock. Wikis Settings sends no reminder itself: the weekly review reminder (to the page's owner, else its owning team, else the person who manages it) is part of Content Governance in the admin area. --- ## Licensing and limits ## Does Wikis require a licence? Yes. Wikis requires a licence and is disabled by default. An administrator enables it from Admin → Apps → All Apps for your organization. ## Are there limits I should know about? | What | Limit | |---|---| | Title length | 255 characters | | Description length | 500 characters | | Comment length | 2,000 characters | | Tag name length | 50 characters | | Template name length | 100 characters | | Cover image size | 10 MB (JPEG, PNG, WebP, or GIF) | | Inline image upload size | 10 MB (JPEG, PNG, WebP, or GIF) | | Page attachments | Up to 5 files, each up to 10 MB | | Comment attachments | Up to 5 files, each up to 10 MB | | Sub-wiki nesting depth | 5 levels | | Edit lock timeout | 1–1,440 minutes (default 30) | | Comment edit window | 15 minutes after posting (admins: unlimited) | | Comment delete window | 5 minutes after posting for its author (the page's manager, business admins and Wikis app admins: any time) | | View deduplication | One view counted per user per page per 30 minutes | --- ## More help - [Wikis Overview](/help/articles/wikis_app_overview) - Ask AI — the assistant answers Wikis questions from these articles. **Keywords:** faq, wiki, knowledge base, version history, edit lock, templates, sub-wiki, permissions, not showing, PDF export, stale, wikis --- # Workforce Bots App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to create, configure, and manage AI bots that answer employee questions from your uploaded documents. # Workforce Bots ## 1. What it is Workforce Bots lets you create AI assistants that answer employee questions from the documents you upload. You feed a bot your handbooks, SOPs, policies, or job descriptions, and it answers questions around the clock using only that material. - **Enablement:** Workforce Bots requires a license. An admin enables it from Admin → Apps → All Apps; it is off by default. - **What it is not:** Workforce Bots does not replace Ask AI. Ask AI is the platform-wide assistant; a Workforce Bot answers only from its own uploaded documents and configured knowledge base. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable **Workforce Bots**. A license is required. 2. Open **Workforce Bots → Bots** and click **New Bot**. 3. Choose a template — **HR Policy Bot**, **Recruiting Bot**, **Process Bot**, **Compliance Bot**, or **Custom Bot**. Each pre-fills a welcome message, a fallback message, and conversation starters you can edit. 4. Upload at least one document (PDF, DOCX, or text). The bot processes it into searchable chunks; wait for the status to show **Ready** before testing. 5. Set the **Access mode** to control where the bot is reachable: - **Portal Only (Public)** — anyone with the portal link can chat, no login needed. - **Portal with Login** — the portal link works but requires a OneMango login. - **Internal Only (Intranet)** — reachable only inside the app, through the Ask tab and the Bots list; no portal page. - **Both Portal and Internal** — available everywhere. 6. Confirm the bot appears on the **Dashboard** tab and that employees in the target group can see it in the **Ask** tab. Only admins and app admins can create, edit, or delete bots. All other employees can view and chat with bots that are active, not in draft, and whose access mode includes internal access. ## 3. How it fits together **Bots and documents.** A bot is a named assistant with its own document corpus, system prompt, and settings. Each document you upload is split into chunks and embedded for retrieval. When someone asks a question, the bot retrieves the most relevant chunks and passes them to the LLM with the question. A bot can have documents uploaded directly, ingested from a URL or pasted text, or synced from a Knowledge Base source such as Service Desk, Safety Hub, Recruiting, HR, Help, Learning, Inspections, or Custom. **Example:** You create a bot called "Benefits Guide", set it to **HR Policy Bot**, and upload your 2026 benefits handbook. An employee asks "Am I eligible for dental?" The bot retrieves the chunk from the handbook covering dental eligibility and answers with a citation. If the bot cannot find a relevant chunk, it shows the fallback message you configured. **Templates.** The five template types set the bot's starting personality and defaults. A **Compliance Bot** adds a legal-disclaimer prompt and connects to the compliance rules database. A **Recruiting Bot** allows candidates to attach resumes. A **Custom Bot** is a blank slate. You can change the system prompt, welcome message, and fallback message after creation regardless of template. **Access modes and portals.** Access mode determines where the bot is available. Bots with portal access get a shareable URL at `/apps/workforce_bots/portal/`. Portal-only bots are invisible to employees inside the app; internal-only bots have no portal page. A bot that is in draft or whose status is not active never appears to employees, regardless of access mode. **Ask — the router.** The **Ask** tab is a single input that routes each question to the best bot automatically. When there is only one active internal bot, it goes straight there. With multiple bots, a lightweight LLM classifier picks the most relevant one per turn and shows which bot answered. Employees do not need to know which bot to ask. **Low-confidence answers vs. Answer reviews.** These are two separate queues, and both are reached from the bot's Actions menu under the names used here. **Low-confidence answers** lists answers the bot itself flagged as below its configured confidence threshold. **Answer reviews** lists answers employees rated poorly (thumbs-down). Both are post-delivery — the answer has already been shown. In **Low-confidence answers**, approving or rejecting stamps a compliance record and notifies the person who asked. In **Answer reviews**, **Mark addressed** records that the rating was dealt with and tells the person who left it that an admin read their feedback. **Cross-agent discovery.** When the setting **Let other AI agents discover and consult these bots** is on, other AI agents in the platform (Ask AI, app agents) can find this tenant's bots by subject matter and route questions to them. It changes which questions reach the bot, not what the bot can do — no bot, document or setting is modified. The consult itself is metered, so it counts toward the bot's question count and monthly quota like any other question. **Portal embedding.** A bot with portal access can be embedded on an external website. The portal page supports three modes: the full-page portal at `/apps/workforce_bots/portal/`, a chrome-stripped iframe at `/apps/workforce_bots/portal/?embed=1`, and a JavaScript widget snippet that renders a floating chat bubble. Embedding is **refused until you name an origin**: set **Allowed embed origins** on the bot's edit page to the sites you want to allow (or `*` for any site, which puts the bot on pages you do not control). Leaving the field blank allows nothing, and the browser simply renders an empty box with no server-side error to find. **Escalation.** When an employee clicks "Route to a human" on a low-confidence answer, the bot tries to reach a person in order: first it creates a Service Desk ticket (if Service Desk is enabled for the tenant), then it sends an in-app notification to the bot's admin. The configured deflection webhook fires alongside either path. The reply to the employee says whether a human was actually reached. **Mobile.** Employees can browse and chat with bots from the mobile app at `/m/apps/workforce-bots`. The mobile view shows the bot directory and a full-screen chat interface. Admins stay on the desktop dashboard. **AI Writer and Comms Planner.** Workforce Bots includes an AI Writer (for generating content using a writing profile) and a Comms Planner (for planning a communications calendar). Both have been consolidated into the Communications app as canonical surfaces. If your tenant has Communications enabled, the Workforce Bots entry points redirect there. If not, the local surfaces remain available. ## 4. Running it ### Reviewing knowledge gaps Go to a bot's detail page and click **Knowledge Gaps**. This lists questions the bot could not answer, grouped by the employee's original question. You can click **Dismiss** to clear a gap without teaching the bot (it will keep giving the same answer), or click **Teach the bot** to write an answer — the answer is saved as an FAQ document in the bot's corpus so it can answer the same question next time. ### Reviewing flagged answers Open **Low-confidence answers** from the bot's Actions menu. Each row shows the employee's question and the bot's low-confidence answer. You can approve or reject individually, or select multiple and apply a bulk decision. The employee is notified of the verdict. ### Reviewing poorly rated answers Open **Answer reviews** from the bot's Actions menu. This shows answers employees rated with a thumbs-down. A low rating means the person was not satisfied — it does not mean the answer was wrong. Mark each as addressed once you have taken action (uploaded a better document, edited the system prompt, or decided the answer was actually correct). ### Syncing from a Knowledge Base On the bot's edit page, choose a **Knowledge Base source** (the dropdown shows sources that have entries for your organization); its published entries are pulled in when you save. Enable **Knowledge Base Sync** to keep the bot's documents updated automatically every hour. You can also click **Sync Now** on the bot's detail page to run an immediate one-time sync without enabling recurring sync. ### Setting up webhooks Open **Webhooks** from the bot's Actions menu. Each webhook fires a signed JSON payload to your URL when one of four events occurs: **Conversation completed**, **Low rating** (a thumbs-down), **Question unanswered**, or **Routed to a human**. The payload includes an HMAC-SHA256 signature using the webhook's secret. If an endpoint fails 15 times in a row, the webhook is auto-disabled until an admin re-enables it. ### Viewing analytics Open a bot's detail page and click **Analytics**. The page shows questions asked, conversations started, unanswered questions, the share of rated answers marked helpful (a thumbs-up), and top topics — all filterable by time range (24 hours, 7 days, 30 days, or 90 days). If a monthly question quota is configured, a usage meter shows progress. You can download the analytics as a PDF report. ### Exporting conversations From the admin side-panel chat or the portal, you can export a conversation as Markdown or PDF. Bulk Q&A (available on Compliance and Custom template bots) lets you paste or upload a list of questions, run them all through the bot, and export the results as XLSX, CSV, or Markdown. ### Managing documents Open a bot's **Documents** page to see every source in its corpus. You can upload files, add a web page by URL, or paste text directly. Each document shows its processing status: **Pending**, **Processing**, **Ready**, or **Failed**. Failed documents can be retried. The **Freshness** column shows when each document was last reviewed; the **Needs review** filter lists the ones never reviewed or past their review interval, and **Mark reviewed** clears them for governance tracking. ### Slack and Microsoft Teams Slack and Microsoft Teams aren't available for Workforce Bots yet: there is no way to connect a Slack workspace or a Teams team to a bot, so bots answer on their portal, embed, widget, in OneMango and in Ask AI. Answers delivered that way count against the bot's monthly question quota, but they are **not** stored as conversations: they do not appear in transcripts, analytics, ratings, the review queues, or the conversation export, and the per-bot low-confidence review setting does not apply to them. ## 5. Settings Settings are at **Workforce Bots → Settings** (admin or app admin only). | Setting | Default | What it changes | |---|---|---| | Default welcome message | *(blank — each template supplies its own)* | Pre-fills the welcome message when creating new bots | | Default fallback message | *(blank — each template supplies its own)* | Pre-fills the fallback message when creating new bots | | Apply Business Branding to Portals | Off | Applies your organization's theme colors and removes "Powered by MangoApps" from bot portals | | Include Bots in Content Governance | Off | Surfaces stale bot documents in the content governance dashboard and notifies reviewers. Review interval is 90 days. | | Monthly question quota | Unlimited | Maximum questions per bot each month. Once a bot passes it, that bot stops answering everywhere — the portal, the in-app Ask page, the mobile app, Ask AI and the chat panel on the bot's own page — until the next reset. Checked nightly against rolled-up usage, so a bot can run past the limit for up to a day. A bot with its own quota (Edit bot › Usage) keeps that number. | | Erase conversation text after | Keep forever | Erases the message text of conversations older than the configured number of days. The conversation row, timestamps, and audit trail are kept. Minimum 7 days. | | Require identity verification to read conversations | Off | Admins must re-enter their password or PIN before reading an employee's conversation. Each read is written to the audit log. Verification lasts 15 minutes. | | Notification email | *(blank — falls back to each bot's admin email)* | Receives monthly quota warnings | | Send a weekly summary | **On** | Sends a Monday in-app digest: questions asked, unanswered questions, poorly rated answers, and pending review decisions. Quiet weeks send nothing. | ### Per-bot settings (on each bot's edit page) | Setting | Default | What it changes | |---|---|---| | Access mode | **Internal Only (Intranet)** | Where the bot is reachable — portal, internal, or both. A new bot is **not** reachable from the public internet until you change this. | | Draft | Off | A draft bot is hidden from all employees | | Status | **Active** | **Active**, **Deactivated**, or **Retired**. Only active bots answer questions. | | Knowledge Base Sync | Off | When on, documents from the chosen Knowledge Base source sync every hour | | Web search | Off | Lets the bot supplement its documents with web search results | | PII redaction | **On** | Redacts personally identifiable information — SSNs, card numbers, phone numbers, email addresses and dates of birth — from the **employee's question**, before it is stored. The original text is not kept, so what an admin sees in the transcript, Knowledge Gaps and the CSV export is the redacted copy. This setting does not alter the bot's own answers — answers are scrubbed separately, by the platform's output PII scanning, which is a company-wide moderation setting rather than a per-bot one. | | Low-confidence review | Off | Flags low-confidence answers for admin review in the **Low-confidence answers** queue | | Low-confidence threshold | 0.40 | Answers with confidence below this score are flagged for review | | Deflection | **On** | Shows a "Route to a human" button on low-confidence answers. Escalation tries Service Desk (if enabled), then notifies the bot's admin. | | Auto-detect language | **On** | Responds in the language the employee used | | Monthly question quota | *(inherits app setting, or unlimited)* | Overrides the app-level quota for this bot | | Quota reset day | 1 | Day of the month the usage counter resets | | Follow-up nudges | Off | On the portal only: after a number of answers the employee has not rated, shows a one-time "Was I helpful?" prompt asking them to rate the answers | | Nudge after N turns without a rating | 3 | How many unrated answers before the prompt appears | ## 6. More help - **Workforce Bots FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about Workforce Bots from these articles. **Keywords:** workforce bots, AI bot, document bot, HR bot, policy bot, knowledge base bot, chatbot, FAQ bot, ask anything, bot portal, workforce-bots, workforce_bots --- # Workforce Bots FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Workforce Bots — for the admin running it. # Workforce Bots FAQ Answers to common setup and operating questions about Workforce Bots. For what the app is and how to set it up from scratch, see the [Workforce Bots Overview](/help/articles/workforce_bots_app_overview). --- ## Setup ## Do I need to upload documents before my bot can answer anything? Yes. A bot answers only from the material in its knowledge base. Until at least one document shows a processing status of **Ready**, the bot returns the fallback message you configured (or the template default) for every question. ## Which file types and sizes does the knowledge base accept? PDF, Word (.doc and .docx), and plain text. Each file can be up to **10 MB**. Spreadsheets, CSV, and image files are not accepted as knowledge documents. ## What happens after I upload a document? The system extracts the text, generates a summary and key topics, and splits the content into chunks of roughly 1,500 characters each. The document status moves from **Pending** to **Processing** to **Ready**. If extraction fails, the status shows **Failed** and you can retry from the Documents page. --- ## Permissions and access ## Who can create and manage bots? Admins and app admins can create, edit, delete, and sync bots, manage documents, review approvals, read conversations, and change settings. All other employees can view active bots and chat with them through the Ask tab or the portal, but cannot change anything. ## What do the access modes mean? Each bot has one of four modes: - **Portal Only (Public)** — anyone with the portal link can chat; no OneMango login required. - **Portal with Login** — the portal link works but the visitor must log in first. - **Internal Only (Intranet)** — available only inside the app through the Ask tab and the Bots list; no portal page at all. - **Both Portal and Internal** — available everywhere. The default is **Internal Only (Intranet)** — a bot you create by accepting the defaults has no portal page at all, and is reachable only by signed-in employees. Choose a portal mode deliberately when you want the bot on a public page. ## I set a bot to Internal Only but employees still can't see it — what's wrong? Check three things: the bot's status must be **Active**, the **Draft** toggle must be off, and the Workforce Bots app must be enabled for your organization. A draft bot, or a bot whose status is **Deactivated** or **Retired**, is hidden from everyone except admins. --- ## Day-to-day ## How does the Ask tab decide which bot to use? When your organization has more than one active internal bot, a lightweight classifier picks the most relevant one for each question. The answer shows which bot responded. With a single active internal bot, questions go to it directly. ## Can employees ask questions in their own language? Yes. On the bot's edit page, pick a **Primary language** from the dropdown (16 languages are available: English, Spanish, French, German, Portuguese, Italian, Japanese, Chinese, Korean, Hindi, Arabic, Dutch, Polish, Russian, Turkish, and Vietnamese). Enable **Auto-detect user language and reply in kind** to have the bot detect the language and respond in it automatically. Auto-detect is on by default. ## How do I embed a bot on our company website? The bot must have a portal access mode (**Portal Only**, **Portal with Login**, or **Both**). The portal page supports three embedding paths: a full-page link at `/apps/workforce_bots/portal/`, a chrome-stripped iframe at `/apps/workforce_bots/portal/?embed=1`, and a JavaScript widget snippet that renders a floating chat bubble. Embedding is refused until you name an origin: enter the allowed sites on the bot's edit page under **Allowed embed origins** (or `*` for any site). If you leave that field blank the iframe will not render anywhere — that is the shipped default for a new bot, and there is no server-side error to look for, so check it first if your embed shows an empty box. ## Can I pass our own SSO identity into an embedded bot? Yes. Set a **SSO shared secret** on the bot's edit page. Your site signs a JWT with that secret using HS256 (the token must include an expiry claim). The portal uses the asserted name and email for attribution without creating a platform account. ## How does the "Route to a human" escalation work? When deflection is enabled and an answer falls below the configured confidence threshold, the employee sees a **Route to a human** button. Clicking it tries to reach a person in this order: first it creates a Service Desk ticket (if Service Desk is enabled for your organization), then it sends an in-app notification to the bot's admin. The configured deflection webhook fires alongside either path. The reply the employee sees says whether a human was actually reached — it does not promise hand-off unconditionally. The button is on the bot portal, the bot's in-app chat panel, the **Ask** page and the mobile app; on the portal (when signed in), the chat panel and the mobile app it also stays on earlier answers when the conversation is reopened. Admins notified about an escalation open the conversation from the notice. Once someone has followed up, **Mark handled** on that conversation takes the notice out of every admin's Inbox. ## What triggers each webhook event? Webhooks fire on four events: **Conversation completed** (the session ends), **Thumbs-down (poor rating)** (the employee gives an answer a thumbs-down), **Question unanswered** (the bot could not find a relevant answer), and **Routed to a human** (the employee clicked the deflection button). Each payload is signed with HMAC-SHA256 using the webhook's secret. --- ## When something looks wrong ## "The bot just gave the wrong answer — can I fix it?" The answer has already been shown. Approving or rejecting it in **Low-confidence answers**, or marking it addressed in **Answer reviews**, records the review but does not change what the employee saw. To improve future answers, go to the bot's **Knowledge Gaps** page, find the question, and click **Teach the bot** — the answer you write is saved as an FAQ document in the bot's corpus. An answer someone rated poorly can be taught the same way from **Answer reviews** (**Teach the bot the right answer**). You can also upload a better document or edit the system prompt. When you approve or reject a low-confidence answer, you can add a **Note to the person who asked**. They see it with the decision and under that answer in **My questions**, where each conversation opens in full. The separate internal note is seen only by bot admins. ## "My document has been stuck on Processing for a long time" Open the bot's **Documents** page, find the document, and click **Retry**. If it fails again, the status shows **Failed** with an error message. Common causes are password-protected PDFs, scanned images without text layers, and corrupted files. Re-upload with a clean copy. ## "Employees say the portal page won't load" Verify the bot's access mode includes portal access (**Portal Only**, **Portal with Login**, or **Both**). A bot set to **Internal Only** has no portal page — the URL returns a not-found error. Also confirm the bot is **Active**, not in draft, and that its portal slug is set. ## "I got a notification that a webhook was auto-disabled" A webhook is automatically disabled after **15** consecutive delivery failures. Fix the receiving endpoint, then re-enable the webhook from **Webhooks** in the bot's Actions menu. The failure count resets on the next successful delivery. ## "The bot isn't answering questions from our Knowledge Base" Make sure a **Knowledge Base source** is selected on the bot's edit page and that you have clicked **Sync Now** or enabled **Knowledge Base Sync** for nightly updates. The available sources (Service Desk, Safety Hub, Recruiting, HR, Help, Learning, Inspections, Custom) appear in the dropdown only when your organization has entries in that domain. --- ## Governance and compliance ## What does PII redaction cover? When **PII redaction** is enabled on a bot, user messages are scanned before storage for five patterns: Social Security numbers, credit-card numbers, email addresses, phone numbers, and dates of birth. Each match is replaced with **[REDACTED]**. Redaction runs on user messages only, not on the bot's answers. ## How does the conversation retention policy work? In **Settings → Erase conversation text after**, set a number of days (minimum **7**). A nightly job erases the message text of conversations older than that window. The conversation row, its timestamps, ratings, and audit trail are preserved — only the free-text content is removed. Leaving the field blank keeps conversations forever, which is the default. ## What does "Require identity verification to read conversations" do? When enabled, admins must re-enter their password or PIN before opening the conversation transcript viewer. The verification lasts **15 minutes**. Each read is logged to the audit trail. This protects sensitive employee questions (HR, medical, benefits) from casual browsing by admins who stay logged in. --- ## Licensing and limits ## Does Workforce Bots require a license? Yes. An admin enables it from Admin → Apps → All Apps and a license is required. Workforce Bots is off by default for every organization. ## Are there limits I should know about? | What | Limit | |---|---| | Upload size | 10 MB per file | | Accepted formats | PDF, Word (.doc/.docx), plain text | | Knowledge-base chunk size | ~1,500 characters with 200-character overlap | | Bot name | 100 characters | | Bot description | 240 characters | | Welcome message | 120 characters | | Conversation starters | Up to 6 per bot, each up to 120 characters | | Avatar | PNG, JPG, or WebP; max 2 MB | | Portal message length | 5,000 characters | | Image attachments per turn | 2 images; max 800 KB decoded per image | | Raw photo upload (mobile) | 15 MB; downscaled to 1,024 px longest edge | | Portal rate limit | 60 questions/minute (paid) · 20 questions/minute (free-tier) | | Webhook secret | Minimum 16 characters | | Webhook circuit breaker | Auto-disables after 15 consecutive failures | | Conversation retention minimum | 7 days | | Monthly question quota | Optional, admin-configured per bot or across the organization. No hard cap by default. | --- ## More help - [Workforce Bots Overview](/help/articles/workforce_bots_app_overview) - Ask AI — the assistant answers Workforce Bots questions from these articles. **Keywords:** faq, workforce bots, AI bot, knowledge base, portal, document upload, PII redaction, webhook, approval queue, low confidence, deflection, quota, language, embed, workforce-bots, workforce_bots --- # Workforce Intelligence **Category:** System-features **Section:** Advanced Features **Updated:** 2026-08-12 The admin hub for MangoScore performance scoring and Recommendation AI shift-allocation weights — configure how employees are evaluated and how the scheduling engine ranks candidates. # Workforce Intelligence ## 1. What it is Workforce Intelligence is the admin surface where you configure two systems that work together: **MangoScore**, which evaluates employee reliability from attendance, cancellations, manager ratings, and consistency signals, and **Recommendation AI**, which uses configurable weights to rank candidates when the scheduling engine assigns shifts. - **Enablement:** requires the **Workforce Intelligence** permission, which is admin-only — it is not inherited by Manager roles. - **What it is not:** this is not a marketplace app you enable per-tenant. It is a built-in admin surface that appears under **Admin → Workforce Intelligence** in the sidebar for any user with the permission. ## 2. Standing it up 1. **Grant the permission.** Go to **Admin → Roles & Permissions** and grant **Workforce Intelligence → View** (or **Manage**) to the roles that should access this surface. Only admin-level roles receive it — Manager roles do not inherit it. 2. **Open the dashboard.** Navigate to **Admin → Workforce Intelligence**. The dashboard shows four stat tiles: Average MangoScore, Total Employees, Scored Employees, and whether Recommendation AI is Active or Setup Needed. Until the first weekly calculation runs, the Average tile shows a dash. 3. **Configure MangoScore weights.** Click **Scoring & Logic → MangoScore Settings**. Set the component weights (attendance, cancellation, manager rating, consistency) — they must sum to 1.0. Review the tier thresholds and adjust if your defaults need to change. 4. **Configure Recommendation Weights.** Click the **Recommendation Weights** tab. Set the four allocation weights (availability, preference, fairness, role) — they must sum to 100%. Optionally configure contracted-hours enforcement. 5. **Wait for the first calculation.** MangoScore recalculates automatically every Sunday at 02:00 UTC. Employees need at least 5 assigned shifts in the last 30 days to receive a score — anyone below that threshold is placed in the Unranked (Low Activity) tier. You can also trigger an immediate recalculation from the MangoScore settings (saving changed weights or thresholds automatically enqueues one). ## 3. How it fits together **MangoScore** is a per-employee reliability number (0.0–1.0) computed from four components, each with a configurable weight: - **Attendance** — proportion of assigned shifts the employee showed up for (default weight: 50%) - **Cancellation** — proportion of unexcused late cancellations or no-shows, inverted so lower is better (default: 30%) - **Manager rating** — average of 1–5 ratings entered by managers, normalized to 0–1 (default: 20%) - **Consistency** — punctuality streak length and shift-swap reliability, equally weighted; a successfully covered swap is neutral, only uncovered drops penalize (default: 0%, opt-in) The score places each employee into one of four **tiers** based on configurable thresholds: | Tier | Default threshold | Meaning | |---|---|---| | Top Tier | ≥ 0.90 | Highest reliability; eligible for early shift access | | Reliable | ≥ 0.75 | Solid performer | | Watchlist | ≥ 0.00 | Needs attention; managers are notified on entry | | Unranked (Low Activity) | — | Fewer than 5 shifts in the last 30 days | All four tier names are customizable per-tenant. **Recommendation AI** is a separate weighting system that the scheduling engine's auto-assign uses to rank candidates for a shift. Its four weights (availability, preference, fairness, role) must sum to 100%. A separate **contracted-hours** control sits outside the sum — it scales the penalty applied as an employee approaches their contracted-hours target, and the enforcement mode decides whether the cap is a hard limit, a soft penalty, or off. **How they connect:** MangoScore feeds into the scheduling engine's candidate ranking alongside the Recommendation AI weights. Top Tier employees can also claim shifts during the early-access window before the shift becomes generally available. ## 4. Running it ### Viewing employee scores Go to **Admin → MangoScore** (linked from the Workforce Intelligence dashboard). The index lists all employees with their current score, tier, attendance rate, cancellation rate, and manager rating. Filter by tier, location, role, or name. Export the current view as CSV. ### Rating an employee On the MangoScore detail page for an employee, enter a 1–5 manager rating. The score recalculates immediately. You cannot rate yourself — the system blocks self-ratings. ### Triggering a recalculation From the MangoScore index, use **Recalculate All** to enqueue a background recalculation for every employee in the business. The weekly job does this automatically each Sunday. Saving changed MangoScore weights or thresholds also triggers a recalculation. ### Adjusting recommendation weights Open the **Recommendation Weights** tab under Scoring & Logic. Drag the sliders for availability, preference, fairness, and role — the stacked bar updates live to show the balance. The total must reach exactly 100% before the form can be saved. ### Configuring contracted-hours enforcement On the same Recommendation Weights page, set the contracted-hours weight multiplier and choose an enforcement mode: - **Strict** (default) — employees who would exceed their contracted-hours target are filtered out of auto-assign entirely - **Soft only** — they stay in the pool but receive a score penalty - **Off** — contracted hours are ignored in auto-assign ## 5. Settings ### MangoScore settings Navigate to **Admin → Workforce Intelligence → Scoring & Logic → MangoScore Settings**. | Setting | Default | What it changes | |---|---|---| | System Name | MangoScore™ | Display name used throughout the application for the scoring system | | Attendance Weight | 0.50 | How much attendance contributes to the score | | Cancellation Weight | 0.30 | How much cancellation behavior contributes | | Manager Rating Weight | 0.20 | How much manager ratings contribute | | Consistency Weight | 0.00 | How much punctuality streak and swap reliability contribute; 0 disables this component | | Top Tier Threshold | 0.90 | Minimum score to reach Top Tier | | Reliable Threshold | 0.75 | Minimum score to reach Reliable | | Watchlist Threshold | 0.00 | Minimum score for Watchlist (below Reliable) | | Tier Names (×4) | Top Tier / Reliable / Watchlist / Unranked (Low Activity) | Custom display names for each tier | | Early Access Window | 24 hours | How many hours before general release Top Tier employees can claim shifts | | Weekly Digest | Off | When on, managers receive a weekly notification summarizing their team's scores | ### Recommendation weights Navigate to **Admin → Workforce Intelligence → Scoring & Logic → Recommendation Weights**. | Setting | Default | What it changes | |---|---|---| | Availability Weight | 30% | Weight given to employee availability for a shift | | Preference Weight | 25% | Weight given to employee shift preferences | | Fairness Weight | 25% | Weight given to even distribution of shifts | | Role Weight | 20% | Weight given to role-match for the shift | | Contracted Hours Weight | 1.0× | Multiplier on the soft penalty as utilization approaches 100% | | Contracted Hours Enforcement | Strict | Whether the contracted-hours cap is a hard limit, soft penalty, or off | ## 6. More help - **Workforce Intelligence FAQ** — specific setup and operating questions (coming soon) - Ask AI — the assistant answers questions about MangoScore and Recommendation AI from these articles. **Keywords:** workforce intelligence, mango score, mangoscore, performance score, scoring and logic, recommendation weights, recommendation ai, shift recommendation, attendance weight, tier threshold, top tier, reliable, watchlist, early access, contracted hours, employee reliability, manager digest --- # Worklog App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 How to set up and run Worklog — the app for tracking billable hours by client and project, generating invoices, and exporting time data. # Worklog ## 1. What it is Worklog lets employees track billable time against clients and projects, then turn that time into PDF invoices they can email directly. It is separate from shift scheduling and pay-period attendance — it is built for professional-services and agency work where hours are billed to an external client. - **Enablement:** Worklog requires a license. An admin enables it from Admin → Apps → All Apps; it is off by default. - **What it is not:** Worklog is not a shift scheduler or a payroll clock. It does not feed into Time & Attendance or Payroll Connect. Use it when the audience is a client you invoice, not a pay period you close. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps**, find **Worklog**, and enable it. This grants access to all employees in your organization. 2. Open **Worklog → Settings** (the Settings tab appears for business admins and designated Worklog app admins). Review the **Time Tracking** tab — decide whether to require a project, a client, or a description on every entry. By default, only a description is required; project and client are optional. 3. On the **Invoicing** tab, set your **Company Name for Invoices** and **Contact Information** — these appear on every generated PDF invoice. Choose your **Invoice Currency** (default USD; also available: EUR, GBP, CAD, AUD). 4. If your organization bills at a standard rate, set the **Default Hourly Rate** on the Invoicing tab. This rate is the fallback when neither a client nor a project specifies one. It defaults to 0.00, so billable entries without a rate produce a $0 amount until you set it. 5. Optionally, on the **Privacy** tab, turn on **Allow Admin Access to Time Logs** if admins need a read-only view of all users' entries for reporting. 6. Confirm it works: have a user open **Worklog → Time Entries** and log a test entry. They should see the entry on the dashboard with today's hours updated. **What silently does nothing until paired:** the **Weekly Summary Emails** and **Remind About Incomplete Days** toggles on the Notifications tab are both off by default. Turning them on does nothing visible to users until those users have at least one time entry — the weekly summary only emails users who logged time the previous week, and the incomplete-day reminder only targets users who logged time in the last 14 days. If you enable them at launch, no one receives anything until real usage begins. **App navigation:** once enabled, Worklog shows five tabs — **Dashboard**, **Time Entries**, **Projects**, **Clients**, and **Invoices**. Admins and app admins also see a **Settings** tab. Worklog has both desktop and mobile views; phone-size browsers redirect automatically to the mobile layout. ## 3. How it fits together Worklog has four core concepts: entries, projects, clients, and invoices. Understanding how they relate prevents the most common setup mistakes. **Entries** — the core unit. Each entry records a date, hours (entered directly or calculated from a start and end time), an optional project and client, a billable/non-billable flag, and an hourly rate. When an entry is billable, Worklog computes the amount as hours × rate. A single entry can hold up to 24 hours (one work date). New entries default to billable with the description field required. The hourly rate is resolved in a specific order: the client's default rate first, then the project's default rate, then the business-wide **Default Hourly Rate** from Settings (which defaults to 0.00). Setting a rate on the client or project saves the user from typing it on every entry. **Projects** — a way to group entries. Each project has a name, a color label, and an optional default rate. Projects are **Private** by default (visible only to the creator) or **Shared** (visible to everyone in the organization). Only the owner or an admin (a business admin or a Worklog app admin) can edit or deactivate a shared project; other users can log time against it but cannot change it. A project with existing time entries cannot be deleted — deactivate it instead. Example: a consulting firm creates shared projects for each engagement — "Acme – Phase 2 Audit", "Beacon – Monthly Retainer" — so every consultant logs against the same project while only the project lead manages it. **Clients** — the billing counterpart. A client has a name, email, phone, contact information, and an optional default rate. Like projects, clients are private or shared, and a client with existing entries cannot be deleted. Clients track uninvoiced billable entries and their total amount, which drives the quick-invoice flow on the dashboard. The relationship between these three: an entry optionally belongs to one project and one client. A project and a client are independent of each other — you can have a client with no project, a project with no client, or both on the same entry. **Invoices** — generated from a client's uninvoiced billable entries. Each invoice is auto-numbered (INV-YYYY-0001, one sequence per business per year), carries a 30-day payment term by default, and moves through four statuses: **Draft → Sent → Paid** (or **Cancelled** from Draft or Sent). An invoice's lines cannot be edited. Cancelling an invoice releases its entries back to uninvoiced so they can be re-invoiced. Invoices can be downloaded as PDF or emailed directly to the client (the client's email address must be set first). An entry that appears on an invoice cannot be deleted until the invoice is cancelled. This protects the invoice's persisted totals from drifting silently. **Sharing model — visibility vs. management:** a shared project or client is visible to every user, but only the creator or an admin (a business admin or a Worklog app admin) can edit, deactivate, or delete it. This means a team can log against the same client without risking accidental changes. Private records are visible only to their owner. **Dashboard** — the landing page at **Worklog → Dashboard** shows four stat cards for the current user: hours logged today, hours this week, billable amount this month, and total uninvoiced amount. Below those are recent time entries, recent projects (with color badges), and clients with uninvoiced amounts flagged as "Ready" for quick invoicing. A dashboard widget also appears on the main home page (when enabled by the dashboard builder), showing today's hours, this week's hours, and the uninvoiced amount at a glance. ## 4. Running it ### Logging time 1. Open **Worklog → Time Entries** and click **Log Time**. 2. Choose a date, enter hours directly or toggle to start/end time (Worklog calculates the duration automatically). Pick a project and client, mark billable or non-billable, and add a description. 3. To repeat a similar entry the next day, use **Log again** in an entry's action menu on **Time Entries** — it prefills the project, client, rate, hours, and description, but resets the date to today so the user reviews it consciously. Users can also create a new project or client inline from the entry form without leaving the page. ### Generating an invoice 1. From the **Dashboard**, click the action menu (⋮) and choose **Generate Invoice**. A modal shows each client with uninvoiced entries, their entry count, hours, and total amount. 2. Click **Generate Invoice** next to a client. Worklog bundles all of that client's uninvoiced billable entries into a single draft invoice, auto-assigns the next invoice number (INV-YYYY-0001 format), sets a 30-day due date, and opens the new draft invoice. **Download PDF** and **Email to Client** are on that page. 3. Open **Worklog → Invoices** to review it. From the invoice detail page you can: - **Mark as Sent (no email)** — moves the invoice from Draft to Sent. - **Email to Client** — emails the PDF to the client's email address and marks the invoice as Sent. The client must have an email address on file. - **Mark as Paid** — records payment (available from Draft or Sent). - **Cancel Invoice** — voids the invoice and releases its entries back to uninvoiced. Cancelling sends the client nothing; if the invoice was already emailed and the client still has an email address, its page then offers **Send Void Notice**. 4. You can also re-download the PDF at any time from the invoice detail page, unless the invoice was cancelled. ### Exporting time data From **Time Entries**, click **Export CSV** in the action menu. The export respects your current filters (date range, project, client, billable status) and the admin's export settings (date format, whether to include non-billable entries and rates). When an admin exports in all-users mode, the CSV includes a User column. ### Importing time entries Go to **Time Entries → Import CSV**. Upload a CSV file using the same column headers the export produces (Date, Project, Client, Description, Hours, Billable, Start Time, End Time, Hourly Rate). The import accepts the date format configured in Settings, so an exported file round-trips cleanly. Unknown columns are ignored. Valid rows are saved; failing rows are reported with their line numbers. Projects and clients named in the CSV that do not exist yet are created automatically as private records; a name that only matches an inactive project or client is reported as a row error. ### Reviewing all users' time (admin) When **Allow Admin Access to Time Logs** is on in Settings, admins and Worklog app admins — plus, if you choose **Specific people** under **Who can see other people's time logs?**, the groups you name, such as a billing team — can switch to an all-users view on the Time Entries page by selecting the scope toggle. Employees are told on their own Time Entries page that this is on. This is read-only oversight — the viewer can filter, sort, and export across all users but cannot edit or delete another user's entries. The filter dropdowns in this mode include all projects and clients in the organization, including other users' private records. ### Managing projects and clients From the **Projects** or **Clients** tab, admins and record owners can create, edit, deactivate, or delete records. Deactivating a project or client hides it from the entry form's dropdown but preserves existing entries. A project or client with existing time entries cannot be deleted — deactivate it instead. ## 5. Settings All settings are at **Worklog → Settings**, organized in tabs. Business admins and designated Worklog app admins can access them. | Setting | Tab | Default | What it changes | |---|---|---|---| | Enable Worklog | General | On | Master switch — turning it off disables the app for all users | | Require Project Field | Time Tracking | Off | Makes the project field mandatory on every entry | | Require Client Field | Time Tracking | Off | Makes the client field mandatory on every entry | | Require Description | Time Tracking | On | Makes the description field mandatory on every entry | | Default to Billable | Time Tracking | On | New entries start with the billable flag checked | | Maximum Hours Per Entry | Time Tracking | 24 | Upper limit on hours per single entry (capped at 24) | | Allow Future Dates | Time Tracking | Off | Whether entries can be logged for dates after today | | Default Hourly Rate | Invoicing | 0.00 | Fallback rate when neither the client nor the project sets one | | Company Name for Invoices | Invoicing | Organization name | The name printed on generated PDF invoices | | Contact Information | Invoicing | (blank) | Address, phone, email printed on PDF invoices | | Enable Logo on Invoices | Invoicing | Off | Whether to include the company logo on PDF invoices | | Invoice Currency | Invoicing | USD | Currency for invoice amounts (USD, EUR, GBP, CAD, AUD) | | Include Non-Billable in CSV | Export | On | Whether CSV exports include non-billable entries | | CSV Date Format | Export | MM/DD/YYYY | Date format in CSV exports (MM/DD/YYYY, DD/MM/YYYY, YYYY-MM-DD) | | Include Rates in Exports | Export | Off | Whether CSV exports include hourly rate and amount columns | | Allow Admin Access to Time Logs | Privacy | Off | Lets the people chosen below read everyone's time entries (read-only) | | Who can see other people's time logs? | Privacy | Admins and Worklog app admins only | Who the switch above grants besides admins and Worklog app admins (who always have it): nobody else, or the groups you choose | | Weekly Summary Emails | Notifications | Off | Emails each user a recap of their previous week's hours every Monday | | Remind About Incomplete Days | Notifications | Off | Emails and notifies users who logged time recently but missed a weekday | | AI Agent Enabled | General | On | Whether the Worklog agent is in Ask AI at all — off, it neither answers Worklog questions nor logs, edits or deletes entries or drafts invoices (each write asks to confirm) | ### Notifications When enabled in Settings, Worklog sends two types of automated notifications: - **Weekly Summary** — emailed every Monday to each user who logged time the previous week. Includes total hours, billable hours, earnings, and top projects. - **Incomplete Day Reminder** — sent daily (email and in-app) to users who have been actively logging time (within the last 14 days) but missed logging on the previous weekday. Weekend days are skipped automatically. Both are off by default. An overdue invoice reminder also runs weekly for any sent invoice past its due date, emailing and notifying the invoice owner, and the owner is told in-app when an invoice email to a client could not be delivered. Neither of those has an admin switch. Each person can mute Worklog notifications under their own notification settings. The **Worklog** category covers all four notices above, so muting it also mutes overdue-invoice reminders and undelivered-email alerts. ## 6. More help - **Worklog FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about Worklog from these articles. **Keywords:** worklog, time tracking, billable hours, invoices, time entries, projects, clients, hourly rate, CSV export, time log --- # Worklog FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Worklog — for the admin running it. # Worklog FAQ Answers to common setup and operating questions about Worklog. For what the app is and how to set it up from scratch, see the [Worklog Overview](/help/articles/worklog_app_overview). --- ## Setup ## Do I have to configure anything before users can log time? No. Once the app is enabled, every user can log time immediately. By default, entries require a description but not a project or client. You can change those rules in **Settings > Time Tracking** — the toggles are **Require Project Field**, **Require Client Field**, and **Require Description**. ## Who can access the Settings page? Business admins and users granted app-admin status for Worklog. The Settings page has six tabs: General, Time Tracking, Invoicing, Export, Privacy, and Notifications. Regular users never see it. --- ## Permissions and access ## Can admins see other users' time entries? Only if you turn it on. In **Settings > Privacy**, enable **Allow Admin Access to Time Logs**. That toggle is off by default. Once it is on, admins and Worklog app admins — plus, if you choose **Specific people** under **Who can see other people's time logs?**, the groups you pick — can switch to an "all users" view on the time-entries page, and employees are told on their own page that it is on. The view is read-only — viewers can filter and export, but only the owner can edit or delete an entry. ## Who can edit or delete a shared project or client? The owner who created it, or an admin (a business admin or a Worklog app admin). Shared projects and clients are visible to everyone in the business, but only the owner or an admin can edit, deactivate, or delete them. --- ## Day-to-day ## How is the hourly rate on an entry decided? When you leave the rate blank, Worklog fills it in automatically: it checks the client's default rate first, then the project's default rate, then the business-wide **Default Hourly Rate** from **Settings > Invoicing**. You can always override the filled-in rate on any individual entry. ## Can I log time without a project or client? Yes. Both fields are optional by default. An admin can make either one required in **Settings > Time Tracking** using the **Require Project Field** and **Require Client Field** toggles. ## What happens when I generate an invoice? Worklog creates a draft invoice containing all of the selected client's uninvoiced billable entries. The invoice gets an auto-generated number in the format INV-YYYY-0001 (one sequence for the whole business, starting again each year) and a due date 30 days from the invoice date. An invoice's lines cannot be edited: to change what is on a draft, cancel it and generate a new one. ## Can I email an invoice directly to the client? Yes. Use the **Email to Client** action on the invoice page. Worklog attaches the PDF and sends it to the email address on the client record. If the invoice is still in draft, emailing it automatically marks it as sent. The client record must have an email address — if it is blank, the action tells you to add one first. ## What happens when I cancel an invoice? All entries on that invoice are released back to uninvoiced status, so they can be included on a future invoice. The invoice itself moves to **Cancelled** and can no longer be emailed. If you had already emailed the invoice to the client, the cancelled invoice's page offers **Send Void Notice** as long as the client still has an email address (on a phone, the page links to the full page, which sends it). It emails the client that the invoice was cancelled and that no payment is due on it; nothing is sent unless you choose it, and once sent the button reads **Send Notice Again**. When you later email the same client a new invoice for those entries, that email tells them which cancelled invoice it replaces; if it bills only some of them, it says it includes work first billed on the cancelled invoice. ## Can I delete a project or client that has time entries? A project with existing entries cannot be deleted — deactivate it instead, which hides it from the project picker but keeps the entries. Clients follow the same rule. --- ## When something looks wrong ## Why can't I log time for a future date? Future dates are blocked by default. An admin can allow them in **Settings > Time Tracking** by enabling **Allow Future Dates**. ## My CSV import skipped some rows — what went wrong? The import processes each row independently. Valid rows are saved and failing rows are reported by line number (up to the first 10 errors). Common causes: a missing or unparseable date, hours outside the allowed range (must be greater than zero and at most the configured **Maximum Hours Per Entry**), or a missing description when the **Require Description** setting is on. The file must be a .csv, under 1 MB, and under 2,000 rows. ## Why does the overdue-invoice reminder keep coming for the same invoice? The reminder runs weekly for any sent invoice past its due date. It continues for up to 120 days after the due date. To stop it, mark the invoice as **Paid** or **Cancelled**. --- ## Notifications ## What notification emails does Worklog send? Admins control the first two in **Settings > Notifications**; the overdue reminder has no switch: 1. **Weekly Summary Emails** (off by default) — sent on Mondays to every user who logged time the previous week, with total hours, billable hours, earnings, and top projects. 2. **Remind About Incomplete Days** (off by default) — sent daily to users who have been active in the last 14 days but logged nothing the previous weekday. Weekends are skipped. 3. **Overdue invoice reminders** (always on for sent invoices past their due date) — sent weekly to the invoice owner, stopping after 120 days overdue. All three also deliver an in-app notification alongside the email, and the invoice owner is told in-app when an invoice email to a client could not be delivered. Each person can mute the **Worklog** category in their own notification settings. That category covers every Worklog notice, so muting it also stops overdue-invoice reminders and undelivered-email alerts. --- ## Export and import ## What columns are in the CSV export? Always included: Date, Project, Client, Description, Start Time, End Time, Hours, Billable. Three more appear when **Include Rates in Exports** is enabled in **Settings > Export**: Hourly Rate, Total Amount and Currency. When an admin exports in the all-users view, a User column is added after Date. The date format follows the **CSV Date Format** setting (MM/DD/YYYY, DD/MM/YYYY, or YYYY-MM-DD). ## Can I re-import an exported CSV? Yes. The import reads the same column headers the export writes (case-insensitive). It tries the configured date format first, then falls back to ISO and natural date parsing. Projects and clients named in the file are matched to existing active records or created automatically as private; a name that only matches an inactive project or client is reported as a row error instead of booking time to it. --- ## Licensing and limits ## Does Worklog require a licence? Yes. A business admin enables it per tenant from Admin → Apps → All Apps. Once enabled, every user in the business can use it — there is no per-user licence. ## Are there limits I should know about? | Limit | Value | |---|---| | Maximum hours per entry | 24 (hard ceiling; admin can set a lower value in Settings) | | CSV import | 2,000 rows and 1 MB per file | | Invoice number format | INV-YYYY-0001, one sequence per business per year | | Supported currencies | USD, EUR, GBP, CAD, AUD (set in Settings > Invoicing) | | Overdue-reminder window | 120 days past the due date | | Incomplete-day reminder scope | Users who logged at least one entry in the last 14 days | --- ## More help - [Worklog Overview](/help/articles/worklog_app_overview) - Ask AI — the assistant answers Worklog questions from these articles. **Keywords:** faq, worklog, time tracking, billable hours, invoicing, time entry, CSV import, hourly rate, project, client, permissions, not showing, overdue --- # Workspace App Overview **Category:** Apps **Section:** Apps & Extensions **Updated:** 2026-10-16 Set up and run the Workspace app — project message boards, to-do lists, timelines, milestones and risks, check-ins, Hill Charts, external access for people outside the company, and the Portfolio and Workload views across projects. # Workspace ## 1. What it is Workspace bundles a message board, grouped to-do lists, a schedule, recurring check-ins, and Hill Charts onto one scrollable canvas per project. Each workspace also gets its own Shared Drive automatically the moment it is created. - **Enablement:** Workspace requires a licence. An admin enables it for the business in Admin → Apps → All Apps; it is off by default. - **Edition requirement:** **Portfolio** and **Workload** plan across projects and people ("advanced planning"). They need the **Platform Standard** edition or above. Everything inside one project — the Table, Timeline and Plan tabs, milestones and dependencies — works in every edition. - **What it is not:** Workspace is not a standalone task manager. To-dos inside a workspace are the same task records the org-wide Tasks app uses, scoped to one project instead of living in a separate system. ## 2. Standing it up 1. Go to **Admin → Apps → All Apps** and enable the **Workspace** app. It requires a licence. 2. Open **Apps → Workspace → Settings**. Review who can create workspaces — the default is **managers and admins, plus anyone with direct reports**. You can widen this to everyone or specific groups, narrow it to the manager role or to people managers, or restrict it to app admins only. Some older businesses show **Managers & admins — by role only** selected instead. 3. Toggle canvas sections on or off. Every section (message board, tasks, schedule, check-ins, Hill Charts, linked tools, the Board view, and more) ships enabled. Disable any section your organisation does not need — workspaces will no longer show it. 4. Create the first workspace. Go to **Apps → Workspace → Workspaces** and click **New Workspace**. Give it a name, an optional description, and an icon/color. You become the owner. 5. Add members. Open the workspace and use the Members card on the canvas, or the **Members** tab (**Add a member**), to add people by name. Members receive a notification that they have been added. 6. Confirm it worked. Members see the workspace under **My Workspaces** on their **Dashboard**, which also lists what needs their attention (to-dos due or overdue, check-ins due, AI drafts to review) and a **Catch up** recap. On the home dashboard, the **My Workspaces** widget shows up to three of their workspaces with what each one needs from them: workspaces they bookmarked come first, then the ones they opened most recently. To bookmark a workspace, click the bookmark icon next to its name. Bookmarked workspaces are also listed first on the **Workspaces** page. 7. On Platform Standard or above, the app's left rail also shows **Portfolio** and **Workload**. Below that plan the two rows are hidden, and a saved link opens an upgrade panel instead. **Silent-dependency note:** The Shared Drive that each workspace provisions relies on the Drive app. If Drive is not enabled, the files section of the canvas will be empty. ## 3. How it fits together ### Roles Every workspace membership carries one of three roles. - **Owner** — created the workspace, or was made an owner. Can edit the workspace, manage members, archive, duplicate, export, rearrange the canvas, and toggle per-workspace features. A workspace can have several owners: **Make owner** on a member's row adds one without demoting anyone. The last owner cannot leave until someone else is an owner. - **Member** — can post messages, create and complete to-dos, add events, answer check-ins, and add links. - **Viewer** — read-only. Can browse messages, tasks, and events, but cannot create or edit content, with one exception: a viewer who is assigned a to-do can mark that to-do complete, reopen it, and comment on it (and edit or delete their own comments there). Personal state (marking a message as read, muting, saving a filter) is not gated by this restriction. Owners, members and viewers can leave an active workspace from its ⋮ menu (**Leave workspace**); their open tasks there become unassigned. People who are in through the workspace's access rule cannot be taken out one by one, so they are offered **Mute instead of leaving**. App admins (business admins and users granted the Workspace app-admin role) can perform any owner action on any workspace, regardless of membership. ### Canvas sections A workspace canvas is a single scrollable page divided into sections. The owner lays out the sections in two columns with **Rearrange canvas** in the workspace's ⋮ menu, and toggles sections on or off from **Features** in the same menu. Business-level settings control which sections are available at all; the owner can only disable within that set, never re-enable something the admin turned off. **Worked example.** Suppose an admin disables Hill Charts business-wide. Every workspace loses that section. An owner who previously disabled and then re-enabled Hill Charts in their workspace will not see it return — the admin gate takes precedence. ### Message Boards: every workspace's posts in one place **Message Boards** in the Workspace navigation lists the message-board posts of every workspace you are in as one stream, the most recently active first, so you do not have to open each workspace to see what is new. Filter it to unread posts and new replies, to posts and replies that mention you, to announcements, or to one workspace. **Mark all as read** clears every unread post and new reply at once (on one workspace's Messages page, that workspace's only). You can react and reply from a post's card where you can post in that workspace — posts, replies and to-dos offer your company's reactions, the same set as the feed and every other app (your admin chooses it in Communications settings), and a reaction you gave before the set changed stays yours to remove; open the post for the whole thread, polls and attachments. It shows only what you could already read in each workspace: a workspace whose message board is switched off, and posts held for review or restricted to owners, stay out. Each workspace's own Messages page shows its board the same way. People outside the company keep their access link to one workspace and do not see this page. ### To-do lists and tasks To-dos live inside named lists (e.g. "Launch checklist", "Adoption milestones"). Each list holds tasks that are the same records as in the org-wide Tasks app. Tasks can be assigned to members, given a due date, and marked complete. When a member is removed from (or leaves) a workspace, their open tasks are automatically unassigned so they surface as unowned. The same tasks appear in columns on the workspace's **Board** tab. ### Planning one project: Table, Timeline and Plan Three tabs inside a workspace turn its to-dos into a project plan. They work in every edition. - **Table** — every to-do as rows you filter, sort, edit in place and save as a view. Owners add project-specific columns from **Manage fields** (for example "Budget code" or "Go-live wave"), up to 30 per project. - **Timeline** — the dated to-dos over time. A to-do can **wait on** another (a finish-to-start link). When a to-do starts before what it waits on finishes, the tab warns you. An owner or member can click **Shift _n_ to-dos** to move the late ones forward, whole. Nothing is ever pulled earlier, and nothing moves without that click. **See what Shift will move**, under the warning, lists each to-do with its dates before and after, so you can check (or copy) the plan before pressing it — a shift is not undone in one step. - **Plan** — the project's **Health** rating, the signals the data shows, its milestones, status updates and risks. A milestone is a to-do with the **Milestone** box ticked; its subtasks are its deliverables. **Health vs signals.** The owner sets **Health** (On track, At risk, Off track, Not set) in **Edit details** or when posting a status update. The signals are computed and never overwrite it: overdue to-dos, missed milestones, open risks, and an owner's check-in that is due. A project marked On track with two missed milestones shows both. Risks raised on the Plan tab are the same records as the Compliance Hub risk register. The Plan tab works whether or not Compliance Hub is enabled; where it is, the register lists these risks too. ### Planning across projects: Portfolio and Workload - **Portfolio** lists every project the viewer may see, with its health and signals. Filter by health, signal, kind, department, location or status, save the filters as a view, or export to CSV. - **Workload** shows people against weeks. Each cell compares the hours of a person's open to-dos with the hours they have that week. Their hours come from a manager's hour target on a schedule, else their contracted hours, else their role's expected hours, else a standard 40 — less approved leave. What each person sees depends on who they are: | Viewer | Sees | |---|---| | Workspace app admin | Every workspace in the business | | Someone allowed to open Workspace Analytics and Reports | Every workspace except private ones they are not in | | Everyone else | The workspaces they can open | On **Workload**, anyone also sees the people who report to them. A person's load counts every open to-do they hold. A to-do's title is shown only when the viewer can open its workspace. A to-do's **Estimate (hours)** spreads evenly over the weekdays from its start (or today, if later) to its due date. A to-do with a due date but no start date lands all its hours on the due day. **Worked example.** A team member has 40 hours next week. Their estimates for that week total 46 hours, which is 115% — the cell reads **Stretched**. At 50 hours (125%) it reads **Over capacity**. At 30 hours (75%) it reads **Well loaded**, and below 50% **Room to spare**. Clicking a cell that holds to-dos opens a drawer where you tick some of them and hand them to someone else. ### Hill Charts A Hill Chart tracks progress on a named scope as a single dot on a 0–100 uphill-then-downhill curve. The left half represents figuring out the problem; the right half represents executing the solution; reaching 100 means done. Every position change is recorded as a history point, so you can review how a scope progressed over time. When the AI agent is enabled and **Auto-Propose Hill Chart Positions** is on, the system periodically proposes a new position based on completed to-dos and recent activity. The proposal appears as a pending badge; the owner accepts (which commits the move) or dismisses it. The AI never moves a dot without approval. ### Recurring check-ins A check-in is a question asked on a schedule — daily, weekly, or monthly. A check-in can also have a set opening time (**Opens at**) in a chosen **Time zone**. A weekly check-in can be limited to the weekdays you tick. If you leave **Opens at** blank, the first check-in opens right away. When a check-in fires, each member gets a response form. If **Auto-Draft Check-In Responses** is on, the AI drafts an answer from the member's recent workspace activity and notifies them that a draft is waiting. The member reviews, edits if needed, and approves. No AI draft ever posts without explicit approval. Check-ins can be paused and resumed. A paused check-in stays visible on the canvas with a "Paused" badge and does not fire until resumed. A check-in's **Answer** can be a written answer (the default) or a typed one: **Pick one from a list**, **Yes / no**, **Number** (with an optional lowest and highest value, such as a 1–5 rating) or **Date**. Typed answers are tallied on the check-in's page under **Results** for each cycle and are never AI-drafted. The answer type is fixed once someone has answered. ### Templates A workspace template captures the structure of an existing workspace — its to-do lists, Hill Charts, and check-in questions — without copying messages, files, or members. Creating a workspace from a template pre-populates that structure so projects of the same shape do not start from scratch. Templates come in two kinds: **system templates** (shared across all businesses, managed centrally) and **business templates** (saved by your team, editable and archivable). An archived template drops out of the picker but is never permanently deleted. A **dated template** also places each to-do and milestone relative to one date — for example **Go-live date** or **Opening day**. When you create a workspace from it, you pick that date and the plan counts back from it. You also choose who holds each role the template names. A role left empty keeps its to-dos unassigned, marked with the role's name. Five dated system templates ship: Store or Site Opening, Technology Implementation, Operational Improvement Project, Compliance Initiative and People Team Program. ### External access External access lets you invite someone outside the company — a client, vendor, partner or contractor, without a OneMango account — to follow a workspace. You issue an access link by email; it expires in 30 days and can be extended or revoked at any time, and an expired link can be renewed for 30 days after it lapses. The external guest sees messages, tasks, events, and Hill Charts, but never anything marked as internal-only. External guests can reply to messages from their link unless the owner switches off **External guests can reply** on the workspace's External access card, which makes their view read-only for that workspace. Turning off **Enable External Access** in settings disables both new invites and existing access links. ## 4. Running it ### Creating a workspace from a template 1. Go to **Apps → Workspace → Templates**. Your team's saved templates are listed first, then the system templates. To add one from the central template library, click **Browse Library** and choose **Use**. 2. On the template's card, click **Create from template**. The workspace takes the template's name (rename it from **Edit details** afterwards), and its to-do lists, Hill Charts and check-in questions are pre-populated. A dated template opens a form first that asks for its date and who holds each role, with a preview of the dated plan. 3. The new workspace starts as a **draft**. Only its owners (and Workspace app admins) can see it, and nobody is notified yet. It is listed under **Drafts** at the top of your **Workspaces** page. Set it up, then click **Launch workspace** on the canvas. The launch form shows what will go out, and lets you confirm or change who holds each role before anyone is told. Click **Launch workspace** again to make it live. Members are then told they were added, each role's to-dos go to its holder, and check-ins start on their schedule. A blank workspace can start as a draft too: tick **Save as a draft** on the **New Workspace** form. ### Duplicating or exporting a workspace - **Duplicate workspace** (⋮ menu) copies to-do lists (open tasks only), Hill Charts (reset to position 0), check-in configs and linked tools, and keeps the workspace's visibility, posting rules and auto-membership rule (people the rule matches can open the copy; a rule broad enough to need an admin's approval waits for that approval again before it applies to the copy). Files are copied only when you tick **Also copy files**. It does not copy messages, events, completed tasks or members — you become the copy's only owner. - **Export to CSV** (⋮ menu) asks you to re-verify your identity first. The file holds the workspace details, member emails, all messages and all tasks. ### Inviting someone outside the company 1. Open the workspace and go to the **External access** card on the canvas, or choose **External access** from the **⋮** menu. 2. Click **Invite someone**, enter the person's email address, and send. They receive an access link valid for 30 days. 3. To extend a link, click **Extend** on the invite row — it adds another 30 days from the current expiry. To revoke, click **Revoke**. A link that expired in the last 30 days is listed under the active ones with **Renew**, which reopens the same link. 4. To get a link again — to send it yourself, or because the email went astray — click **Copy link** on the invite row. It is the same link the person was sent. ### Reviewing projects across the business 1. Open **Apps → Workspace → Portfolio**. Choose **Sort: health, worst first** to put the projects in trouble at the top. 2. Filter by a signal (for example missed milestones) and click **Save this view…** to keep the filter for next time. 3. Open **Workload** to see who is overloaded in the coming weeks. Pick 4, 6, 8 or 12 weeks; 6 is the default. 4. Click a busy cell to open the **Reassign** drawer and hand to-dos to another person. The new assignee must be an active member of that workspace. The **Workspaces** list also has a **Timeline** view of your own workspaces. The first 100 (most recently edited) show in every edition; the pages after that need the Platform Standard edition. ### Importing a project from Monday.com or a spreadsheet 1. Open the workspace. Choose **Import from Monday.com / CSV** from the Tasks card's **⋮** menu (owners also have it in the workspace's **⋮** menu). Viewers cannot import. 2. Upload a Monday.com board exported to Excel, or any spreadsheet, and map its columns. 3. Review the preview. It shows what each row will do before anything is saved. 4. Confirm. Each person assigned work gets one notice for the whole import, not one per to-do. ### Adding items with the Create menu The **Create** button at the top right of the canvas adds a **Message**, **Task**, **Event** or **Linked tool**. Each opens its form in a side panel. When the workspace has no to-do list yet, **Task** reads **Task list** instead. An item appears only while its section is on. Viewers do not get the button, and neither does anyone on an archived workspace. A message that starts with a slash shortcut creates an item instead of a post: `/task`, `/msg`, `/link` or `/event`. Dates and assignees in a shortcut are read by the Workspace AI agent. With **Enable Workspace AI Agent** off, a `/task` keeps its text but gets no date, and `/event` adds nothing. A shortcut is refused when the post has **Internal only**, **Leads only**, **Post as announcement** or attachments set, because the plain item it creates would drop them. ## 5. Settings All settings are at **Apps → Workspace → Settings**. Only business admins and Workspace app admins can reach this page. ### AI features | Setting | Default | What it changes | |---|---|---| | Enable Workspace AI Agent | On | Master switch for all AI features in the app | | Auto-Propose Hill Chart Positions | On | Whether the agent periodically proposes Hill Chart dot moves based on completed work | | Auto-Draft Check-In Responses | On | Whether the agent drafts a response from recent activity when a check-in fires | ### Canvas sections Each of these can be toggled off to hide the section across all workspaces in the business. All default to **On**. | Setting | What it hides | |---|---| | Enable Message Board | The message-board section on the canvas | | Enable Tasks | The to-do lists section, and with it the Table and Timeline tabs | | Enable Schedule | The schedule / events section | | Enable Recurring Check-Ins | The check-ins section | | Enable Hill Charts | The Hill Charts section | | Enable Linked Tools Section | The "Linked tools" section for pinned external URLs | | Show Wikis Section on Canvas | The Wikis section (requires the Wikis app) | | Show Library Section on Canvas | The Library section (requires the Libraries app) | | Show Forms Section on Canvas | The Forms section (requires the Forms app) | | Enable External Access | External access invites and existing access links (turning it off disables outstanding links) | | Enable External Digest Generation | The owner's **External digest** — a summary of recent activity for external guests, with internal-only items left out. It is built from the workspace's own records, not written by AI | | Enable Board View | The **Board** tab, which shows a workspace's tasks in columns | | Enable Reports Tab | The Reports tab in the sidebar (visible to managers and above) | | Enable Comments on To-Dos | Threaded comments on individual tasks | | Enable Recurring To-Dos | Recurring to-do creation | | Enable Emoji Reactions | Emoji reactions on messages and tasks | | Enable iCal Feed for Schedule | iCal feed export for workspace events | ### Capacity limits | Setting | Default | What it changes | |---|---|---| | Max workspaces per business | Blank (unlimited) | Maximum active workspaces in the business. Drafts count toward it | | Max members per workspace | Blank (unlimited) | Maximum members per individual workspace | ### Access control | Setting | Default | What it changes | |---|---|---| | Who can create a workspace? | **Managers & admins, plus anyone with direct reports** | Controls who may create a new workspace. Options: everyone, managers and admins plus people managers, managers by role only, people managers only, app admins only, or specific groups | ### Notifications Each of these toggles one notification channel. All default to **On**, except the weekly external digest email, which defaults to **Off**. | Setting | What it controls | |---|---| | Notify on New Message | Email and in-app notification for new message-board posts | | Notify on New Comment | Notifications for new comments on messages | | Notify on @Mention in Message | Notifications for @mentions in messages | | Notify on @Mention in Comment | Notifications for @mentions in comments | | Notify on To-Do Assigned | Notification when a to-do is assigned | | Remind Assignees About To-Do Due Dates (due soon, overdue, milestones) | Reminds the assignee before a to-do is due and once when it goes overdue, and a milestone's owner a week and a day before it is due | | Notify on Check-In Due | Reminder when a check-in is due and no AI draft was created | | Notify When AI Draft Ready for Approval | Notification when the AI has drafted a check-in response | | Notify on Member Added | Notification when a user is added to a workspace, and to the new owner when a workspace is handed to them | | Notify on To-Do Comments (assignee, creator and earlier commenters) | Notification to the person assigned, the to-do's creator, and earlier commenters when someone comments | | Notify on @Mention in To-Do Comment | Notification for @mentions in to-do comments | | Email the Access Link to the Person Invited | Whether the access link is emailed to the person you invite (the URL is still issued and shown in the UI regardless) | | Email a weekly digest to external guests automatically | Off by default. Emails each workspace's external guests the external digest every Monday; it needs External Access and External Digest Generation on, and sends mail outside your company | | Notify when an event is added | Notification for new schedule events | | Remind before an event starts | Reminder before a schedule event starts | ### Content governance | Setting | Default | What it changes | |---|---|---| | Enable Content Governance | On | Whether message-board posts are subject to the platform's content-governance pipeline | ## 6. More help - **Workspace FAQ** — specific setup and operating questions - Ask AI — the assistant answers questions about Workspace from these articles. **Keywords:** workspace, project management, message board, to-do list, hill chart, check-in, external access, client portal, kanban, board, schedule, quick add, create menu, slash shortcut, template, draft workspace, launch workspace, bookmark, portfolio, workload, timeline, milestone, project risk, custom field, dependency, import from monday.com, who is overloaded --- # Workspace FAQ **Category:** Faq **Section:** Apps & Extensions **Updated:** 2026-10-16 Answers to common setup and operating questions about Workspace — roles, projects, planning, import and templates — for the admin running it. # Workspace FAQ Answers to common setup and operating questions about Workspace. For what the app is and how to set it up from scratch, see the [Workspace Overview](/help/articles/workspace_app_overview). --- ## Setup ## Do I need to configure anything before people can start using Workspace? Enable the app and grant the licence — that is the only prerequisite. Every canvas section (message board, to-dos, schedule, check-ins, Hill Charts, linked tools) is on by default. The AI agent, auto-drafted check-ins, and Hill Chart auto-proposals are also on by default. If you want to restrict who can create workspaces, change the **Who can create a workspace?** setting; the default is managers and admins, plus anyone with direct reports. ## Who can create a workspace, and how do I change that? By default, managers and admins can create workspaces, and so can anyone who has direct reports, whatever their role. Workspace app admins can always create one regardless of this setting. To change it, go to Workspace **Settings**, open **Workspace Creation**, and update **Who can create a workspace?**. The options are: **Managers & admins, plus anyone with direct reports** (the default), **Managers & admins — by role only**, **People managers — anyone with direct reports, whatever their role**, **App admins only**, **Everyone with access to the app**, or **Specific people** (choose groups). Organizations that were already using Workspace when this default changed in late September 2026 keep **Managers & admins — by role only** until an admin changes it. If someone cannot see the app at all, the licence has not been granted — check the app marketplace. If they see it but cannot create a workspace, this setting is why: widen it, or choose **Specific people** and add a group they belong to. ## What are the three workspace roles? Every workspace has three roles: **Owner**, **Member**, and **Viewer**. Owners can edit the workspace's details, archive, delete, duplicate, and export it, and manage members — including **Make owner** on a member's row, which adds another owner alongside the existing ones. Members can post messages, create to-dos, respond to check-ins, and move Hill Chart dots. Viewers have read-only access — they cannot post, create, or edit anything, with one exception: a viewer who is assigned a to-do can mark that to-do complete, reopen it, and comment on it (and edit or delete their own comments there) — on the canvas, in the Table and on the phone. Owners, members and viewers can leave an active workspace with **Leave workspace** in its ⋮ menu; their open tasks there are unassigned. The last owner has to make someone else an owner first, and people who are in through the workspace's access rule cannot leave one by one — they are offered **Mute instead of leaving**. --- ## Permissions and access ## Why can't I see Portfolio or Workload? Portfolio and Workload are advanced planning, which needs the **Platform Standard** plan or above. Below that plan their rows are not in the Workspace sidebar. Opening either page shows an upgrade panel instead, for example "Portfolio requires Platform Standard." Admins are told to contact sales; everyone else is told to contact their administrator. Everything inside one project works on every plan: the Timeline, Plan, Board and Table tabs, milestones, risks and dependencies. The timeline of all your workspaces shows your 100 most recently edited ones on any plan; its later pages need Platform Standard. ## Why doesn't the Portfolio show every project? The Portfolio shows each person the projects they are allowed to see. Company admins and Workspace app admins see every workspace. People who may open Workspace Analytics and Reports see every workspace except private ones they are not in. That group is managers and admins by default, set by **Who can open Workspace Analytics and Reports?** in Settings. Everyone else sees only the workspaces they can open, and archived workspaces stay hidden until you change the status filter. ## Can people outside the company access a workspace? Yes — clients, vendors, partners or contractors — if the **Enable External Access** setting is on (it is by default). A workspace owner issues an access-link invite from the **External access** card — the external guest views externally-visible updates and can add comments without a OneMango account. Posts and to-dos marked internal-only are automatically hidden. External guests cannot edit to-dos, post to the board, or create anything. To make a workspace read-only for external guests, switch off **External guests can reply** on the workspace's **External access** card. It is on by default. With it off, they still read the shared updates but the reply box is gone, and the invite and weekly update emails stop mentioning replies. ## How long do access links last? Each link expires in 30 days. A workspace owner can extend it by another 30 days using the **Extend** button, which keeps the same URL. A link that has already expired stays on the External access list for 30 more days with **Renew**, which brings the same URL back to life; after that, send a new invite. Links can also be revoked at any time. Turning off **Enable External Access** disables all existing links immediately, not just new ones. They start working again if external access is switched back on, so revoke any you no longer want. ## How do I get an access link again after it has been sent? Open the workspace's **External access** card or page and click **Copy link** on the person's row. It copies the same link they were sent, so you can pass it on yourself if the email went astray. Once the person has opened their link, the row also shows when they last did. **Copy link** is offered to the people who can invite — the workspace owner or a Workspace admin, within your company's rule on who may invite people outside the company. --- ## Day-to-day ## How do I add a message, task, event or link to a workspace? Use the **Create** button at the top right of the workspace canvas. It lists **Message**, **Task** (or **Task list**, when the workspace has no list yet), **Event**, and **Linked tool**, and each opens that item's form in a side panel. An item is left out when its section is switched off, and **Linked tool** is also left out when the owner has hidden the Linked tools card. Viewers, and anyone on an archived workspace, do not see the button. There is no quick-add bar on the canvas any more. If you like typing, start a message's body with `/task`, `/msg`, `/link`, or `/event` (**Create → Message**) and it creates that item instead of a post: - `/task Send the draft @Priya by Friday` — a to-do in the workspace's first list (an "Inbox" list is created if there is none). A teammate you @mention becomes the assignee if they are a member; the date becomes the due date. - `/msg Title -- body` — a post, exactly as typed. - `/link https://… Title` — a linked tool. - `/event Sprint review Friday 3pm` — a schedule event; members are notified. Dates and assignees are read by the Workspace AI agent. With **Enable Workspace AI Agent** off, `/msg` and `/link` still work, `/task` is kept as typed with no date, and `/event` adds nothing. A shortcut creates a plain item that everyone in the workspace can see — and external guests with an access link, except for links. So it is refused, with a note under the body saying why, when the post has **Internal only**, **Leads only**, **Post as announcement**, the location copies, or attachments set. Remove the command to post with those settings, or clear them to use the shortcut. ## How do I import to-dos from Monday.com or a spreadsheet, and what are the limits? Open the **⋮** menu on the workspace's Tasks card (**More task actions**) and choose **Import from Monday.com / CSV**. Owners also have it in the workspace's own **⋮** menu. Owners and members can import; viewers cannot. - **Size:** up to 5,000 to-dos and subtasks per import, and files up to 10 MB. - **Dry run first:** **Preview import** shows what every row will do — create, update, leave unchanged, skip, or refuse with a reason — and saves nothing. **Commit import** then writes it. - **Large files:** an import of more than 200 rows runs in the background. You see its progress, you get an email when it finishes, and each assignee gets one notice for all their new to-dos. - **Re-importing:** choose **Update them** to change what differs instead of creating duplicates. Only one import runs in a workspace at a time. From Monday.com, export the board to Excel with subitems and upload it as it is: groups become lists, items become to-dos and subitems become subtasks. People are matched to the workspace's members by email or name; anyone unmatched is named in the preview and their to-dos import unassigned. Extra columns become the project's custom fields only when an owner or Workspace app admin imports; otherwise they are skipped. ## Can I undo a task I linked in, change the order of lists, or reopen a cancelled to-do? Yes. A task linked in from the Tasks app has **Return to the Tasks app** in its drawer (owners and Workspace admins): it leaves the workspace with its notes, comments, history and subtasks, and gets back the assignee that linking cleared. If linking unassigned a task because its assignee isn't a member, the notice names the tasks and each one's activity keeps who it was assigned to. To reorder task lists, open a list's drawer and use **Move up** or **Move down**. A cancelled to-do has a **Reopen** control on its row, in the Table and in its drawer, and any to-do can be completed or reopened from its drawer. ## Can I add my own fields to to-dos, like a budget code or a vendor? Yes. A workspace owner or Workspace app admin opens the **Table** tab and chooses **Manage fields**. A field can be **Short text**, **Long text**, **Number**, **Money**, **Date**, **Pick one from a list**, **Yes / no**, **Email**, **Web link**, or **Person**. A project holds up to 30 custom fields, and a pick list holds up to 50 choices. On the Table tab you can also select up to 100 to-dos at once to complete, reopen, reassign, move, reprioritise or delete them. ## Why can't I make this to-do wait on another one? A to-do's **Waits on** section links it to work that must finish first, and a few rules apply: - Both to-dos must be in the same workspace. - Only top-level to-dos can be linked — a subtask follows its parent, so link the parent instead. - A link cannot close a loop, directly or through another to-do. - A to-do can wait on at most 20 others. - The gap is a whole number of days from -365 to 365; a negative gap lets the two overlap. Viewers cannot add links, and nothing can be linked in an archived workspace. ## How do dated templates work out the dates — do they count back from go-live? Yes. A dated template places each to-do and milestone a set number of days from one anchor date, such as go-live or opening day. When you pick it in **New workspace**, a date field appears under the template's own label (for example **Opening day**). Work planned before that day counts back from it ("60 days before opening"), and later work counts forward. The drawer previews every date before you create the workspace, and warns you when items would already be due before today. Leave the date blank to create the workspace with no dates and set them later. If the template names roles, you also pick who holds each one, and can still change them when you launch the draft; a role left empty keeps its to-dos unassigned and marked with the role's name. When you use **Save as template**, to-do dates are saved as days from the workspace's **Starts on** date — with no start date, no dates are saved. ## Why did my new workspace start as a draft, and who can see it? A workspace created from a template always starts as a draft; for a blank workspace, tick **Save as a draft** on the **New workspace** form. Only the workspace's owners and Workspace app admins can see a draft. Members, role holders and people matched by its access rule cannot open it yet, and nobody is notified. Your drafts are listed at the top of your Workspaces list under **Drafts — only their owners can see these**. When it is ready, open the workspace and choose **Launch workspace**. The panel shows what will go out and lets you confirm or change who holds each template role. Launching makes the workspace live: members are told they were added, each role holder gets one notice listing their to-dos, check-ins start on their schedule, and any welcome post is announced. Choose **Not yet** to keep it as a draft. Drafts count toward **Max workspaces per business**, so each one takes a place under the cap just as a live workspace does. ## What does "Catch me up" do? It generates a 3–5 bullet recap of what changed in the workspace since your last visit. The first time you use it, it covers the last 7 days. Each use updates your last-visited timestamp, so the next recap starts from where this one left off. Your last recap stays in the card for the rest of your browser session, so you can open something it mentions and come back to it; if you press **Summarize** again and nothing is new, it is still shown underneath. ## Can I fix a poll, a reply or where a post went after posting? Yes. A poll's author, a workspace owner or a Workspace admin can **Delete** a poll (its votes go with it) as well as close it. When you edit a reply you can tick or clear **Internal only**, wherever that box is offered for a new reply. And if you posted from a workspace that has location workspaces under it without ticking **Also post to every location workspace**, open the post: its **Location workspaces** panel shows which locations have a copy, which are waiting on their owner's review and which have none. The post's author sees a button there to post to the ones without a copy; each copy goes out under the name of the person who posts it. ## Can I mute notifications for a single workspace? Yes. Use the bell button on the workspace's tab bar, which offers four modes: **All notifications**, **Mentions only**, **Weekly recap only**, or **Mute everything**. Announcements and requests waiting on your decision still reach you in every mode except **Mute everything**. Changes to your own access reach you in every mode. ## How do recurring check-ins work? A workspace owner or member creates a check-in with a question (up to 500 characters) and a cadence — **Daily**, **Weekly**, or **Monthly**. The default cadence for new check-ins is set at the app level under **Default Check-In Cadence** (default: **Weekly**). When the AI agent is enabled and **Auto-Draft Check-In Responses** is on, each member gets a draft response based on their recent activity. They review and approve (or edit) it before it posts. Owners can pause and resume individual check-ins at any time. A check-in can also ask for a typed answer instead of a written one: set **Answer** to **Pick one from a list** (a poll — enter the choices one per line), **Yes / no**, **Number** (optionally with a lowest and highest value — 1 and 5 make a rating) or **Date**. Members answer with that input and can add a short comment, and the check-in's page shows the **Results** for each cycle: a count for every choice, or the average, lowest and highest number, or the dates given. Typed answers are never AI-drafted; members get the usual reminder. Once someone has answered, the answer type is fixed — the choices and the number range stay editable. To ask a question a different way, create a new check-in. ## Can I change a check-in answer after I submit it? Yes, until the next round opens. Open the check-in (or use **Change** beside "You responded" on the canvas card) and choose **Change my answer**: the form opens with what you gave, and saving replaces it. It works on the phone too. The status-update reminder is the exception — its answer is posted to the board as an update, so post a new update instead. ## How do Hill Charts work? Each Hill Chart tracks a scope on a 0–100 scale: 0 is just starting, 50 is the top of the hill (problem solved, now executing), and 100 is done. When **Auto-Propose Hill Chart Positions** is on, the agent computes a proposed position from completed to-dos. The owner or a member accepts or dismisses the proposal — the live position never moves without a person approving it. Every position change is recorded in the chart's history, tagged with whether a user or the agent made it. ## What can the Workspace AI Agent do, and does it act on its own? The agent can draft check-in responses, propose Hill Chart positions, summarize long threads, and suggest follow-up to-dos. It never commits a write on its own — every draft or proposal waits for a person to approve, edit, or dismiss it. Approved AI writes are logged for audit. Turn off **Enable Workspace AI Agent** to disable the agent entirely. Each feature also has its own switch — **Auto-Draft Check-In Responses**, **Auto-Propose Hill Chart Positions**, **Enable AI Thread Summaries and Catch me up**, and **Enable AI Follow-Up To-Do Suggestions** — so you can stop one while keeping the rest. The external digest is not an AI feature: it is built from the workspace's own records, and **Enable External Digest Generation** sits with **Enable External Access** in Canvas sections. ## What is the difference between duplicating and using a template? Duplicating a workspace copies its structure and open to-dos, Hill Charts (reset to position 0), check-in configurations, linked tools, cover image, and layout — but not messages, completed tasks, events, or members (the duplicate starts with the creator as its only owner). It keeps the workspace's auto-membership rule, so people the rule matches can open the copy (a rule broad enough to need an admin's approval waits for that approval again), and it copies the workspace's files only when you tick **Also copy files**. A template captures the reusable skeleton: to-do lists and their to-dos with milestones, dependencies and dates, Hill Chart scopes, check-in questions, the project's custom fields and its open risks (each risk's title, category and rating — not its description or how the team is handling it, since everyone in the company who uses Workspace can see a saved template). It carries no messages or history, and templates from the shared library can also post a welcome message. ## I asked to join a workspace — can I see where that stands, or take it back? Your pending asks are listed on **My Work** under **Waiting on owners**, each with **Withdraw**. The ask's own page shows the same waiting state and **Withdraw my request**, on desktop and phone. Withdrawing closes the request for the owners; you can ask again after a few minutes. ## Are members told when an event moves or is cancelled? Yes. When a future event's time or place changes, or the event is removed, the members who were told about it get a notification with the new time (or that it was cancelled). Changing only the title or notes tells nobody. On the phone, each event on the schedule has **Change or cancel**, which opens the event's form on the full page. ## What happens when I archive or delete a workspace? Archiving makes the workspace read-only and, when the message board is on, posts an internal-only "Project recap" message to the board summarizing the workspace's entire history. The workspace stays archived and can be restored at any time. Deleting is a soft delete — the workspace moves to My Trash and can be restored within 30 days; after that it cannot be recovered. Both actions are restricted to the workspace owner or a Workspace app admin. Anyone who follows an old link to a workspace in Trash is told so: an owner lands on the Trash list with Restore, and a member is told when it was deleted and that its owners can bring it back. --- ## When something looks wrong ## "I can't see next week's schedule in my workspace" The schedule section may be turned off. An admin can disable it at the app level (**Enable Schedule**), and a workspace owner can also hide it per workspace via the workspace's feature toggles. Check both. If the section is on but the user is a viewer, they can see the schedule but cannot add events. ## "My to-do disappeared from the Board" When a member is removed from a workspace (or leaves it), their open tasks are unassigned — but the tasks stay on the Board. If a to-do is missing, check whether it was moved to a different column or completed. The **Board** tab shows up to 50 tasks per column. If a column has more, the count shows the true total and the column ends with "+N more not shown · **Show all**", which lists every task in that column. ## "My post was not approved" — how do I get it on the board? Open the post, fix what the reviewer asked for and save it. Saving sends it back for review, whatever you changed; if the workspace has stopped reviewing posts since, saving posts it. A workspace owner or Workspace admin can also open the post and choose **Approve after all**. ## "My post, reply or attachment disappeared" A workspace owner or Workspace admin can move a post or reply to Trash. You get a notification naming who did, and they can restore it for 30 days — ask them if it was removed by mistake. A post, reply or attached file that you removed yourself is in your own **Trash** (profile menu) for 30 days; restoring a file puts it back on its post. ## "I didn't get notified about a new post" Check the member's per-workspace notification setting (the bell on the workspace's tab bar). If they chose **Mentions only**, **Weekly recap only** or **Mute everything**, regular posts will not notify them. Also confirm the admin-level toggle **Notify on New Message** is still on — it defaults to on, but turning it off suppresses message notifications for the entire business. ## Why is my project flagged red on the Portfolio? A project is flagged red when a milestone is past due or a high or critical risk is open. It is flagged amber for overdue to-dos, a check-in that is due, or any other open risk. The project's **Plan** tab lists its milestones and risks, so clear the flag there: complete or re-date the milestone, or close the risk. The **Health** rating (**On track**, **At risk**, **Off track**, **Not set**) is separate — an owner or Workspace app admin sets it when editing the workspace. ## Why does Workload say someone is over capacity? Workload spreads each open to-do's estimate evenly over its weekdays, from today to its due date. It compares that with the hours the person has that week. Those hours come from their contract or their role's expected hours, else a standard 40-hour week; a manager's hour target on a schedule covering the week wins, and approved leave is taken off. Each week then shows **Room to spare** (under half), **Well loaded** (half to full), **Stretched** (up to 20% over) or **Over capacity** (more than 20% over). A to-do with no estimate is counted but adds no hours. ## How do I move work off someone who is overloaded? Select a person's week on the **Workload** page to open **Reassign**, tick the to-dos, and choose who should take them. You can move up to 100 to-dos at once. You can only move to-dos in active projects where you are an owner or member; Workspace app admins can move them in any project. The new assignee must be a member of that project, and each person is told once about the whole move. --- ## Licensing and limits ## Does Workspace require a licence? Yes. Workspace requires a licence and must be enabled by an admin in the app marketplace before anyone can use it. Portfolio and Workload additionally need the **Platform Standard** plan or above. ## Are there limits I should know about? By default, the number of workspaces per business and members per workspace are both unlimited. An admin can set caps via **Max workspaces per business** and **Max members per workspace** in settings — leaving them blank means no limit. Drafts count toward the workspace cap. | What | Limit | |---|---| | Workspace name | 200 characters | | Cover image | under 5 MB; PNG, JPEG, WebP or GIF | | Check-in question | 500 characters | | Hill Chart scope label | 200 characters, unique within its workspace | | Custom fields | 30 per project; 50 choices per pick list | | Dependencies | 20 per to-do; gap of -365 to 365 days | | Import | 5,000 to-dos and subtasks, 10 MB; more than 200 rows runs in the background | | Table bulk actions and Workload reassign | 100 to-dos at a time | Content governance flags workspace content for review every 90 days by default. An admin can change this with **Review Interval (days)** in the governance settings, from 7 to 365 days. --- ## More help - [Workspace Overview](/help/articles/workspace_app_overview) - Ask AI — the assistant answers Workspace questions from these articles. **Keywords:** faq, workspace, project, to-do, kanban, board, create menu, slash shortcut, leave workspace, hill chart, check-in, external access, client portal, message board, template, dated template, go-live, draft, launch workspace, portfolio, workload, capacity, milestone, risk, dependency, custom fields, import, monday.com, csv, platform standard, permissions, not showing, muted, approval, AI agent --- # Your First Week as an Admin **Category:** System-features **Section:** Advanced Features **Updated:** 2026-10-16 The orientation path for a new admin — where the admin panel lives, what to set up first, how roles work, and the six sections of the admin sidebar. # Your First Week as an Admin ## 1. What it is This article orients a new admin — someone who has just been given the admin or super-admin role — to the platform's administration surfaces. It covers where the admin panel lives, what the first setup steps are, how the role system works, and where every category of settings can be found. - **Enablement:** there is nothing to enable. Every user with the admin or super-admin role sees the admin panel automatically. - **What this is not:** this is not the setup guide for any individual app. Each app has its own overview article covering its configuration. ## 2. Standing it up A new admin account is created by an existing admin or super-admin. There is no self-registration path for the admin role. 1. An existing admin goes to **Admin → Organization → Users** and either creates a new user or opens an existing one. 2. On the user's profile, set the **Role** to Admin or Super Admin. The four system roles are: Super Admin, Admin, Manager, and Member (the default for new users). 3. The user now sees a **gear icon** pinned to the bottom of the left sidebar rail. Clicking it opens the admin panel. 4. To confirm it worked: log in as the new admin and verify the gear icon appears. If it does not, the user's role on their UserBusiness record is still Member or Manager. **What silently does nothing:** assigning the admin role grants access to the admin panel, but it does not automatically grant app-level admin permissions. Per-app admin access (e.g. "Forms Admin" or "Training Admin") is governed by each app's own permission settings and may need to be granted separately. ## 3. How it fits together ### Roles The platform has four system roles, defined on the user's membership in each business: - **Super Admin** — full access to every admin surface, including security controls (Sessions & Tokens, Authentication Log, Maintenance & Lockdown) and super-admin-only areas like App Data Management. - **Admin** — access to all admin sections except the super-admin-only items listed above. In practice, Admins and Super Admins have the same access on most surfaces. - **Manager** — no access to the admin panel. A few admin pages are open to managers as well, but the admin sidebar does not render for them. - **Member** — the default role for every new user. No admin access. A business must always have at least one super-admin. The platform prevents demoting or deactivating the last one. ### The admin sidebar When an admin clicks the gear icon, a sidebar panel opens with six collapsible sections. Every section is available to Admins and Super Admins (super-admin-only items are restricted further). The sections are: 1. **General Settings** — Billing & Payments, General Settings, Roles & Permissions, Groups, Notifications, Content Moderation, Content Governance, Translation, Approval Workflows, Audit Logs, Workforce Intelligence. 2. **Organization** — Settings Hub, Business Profile, Departments, Locations, Users, Job Titles & Families, Dashboard Builder, Engagement, Quick Action Shortcuts, QR Posters, Integrations, Bring Your Data. 3. **Security** — Sign-in Policies, SSO Configuration, Service Accounts, API Keys & Access. Super-admin-only: Sessions & Tokens, Authentication Log, Maintenance & Lockdown. 4. **Apps** — All Apps (the marketplace), Widget Gallery, Custom Apps, App Pipeline (conditional on plugin promotions), App Health. 5. **AI Operations** — Overview, Approvals, Action History, Automations (only when the Loop app is not enabled), Agents, Channels, Agent Settings, Trust & Safety. 6. **Compliance** — Work Policy Settings, Labor Law Rules, Employment Law Rules, Jurisdictions, Jurisdiction Mapping, Compliance Explorer, Compliance Audit Logs (the Platform Enterprise edition only), Employment Law Audit History. A seventh section, **Super Admin** (or "Demo Data" for non-super-admins with sample-data access), appears for super-admins and includes App Data Management, Sample Data, and internal-QA-only tools. ### Settings Hub The Settings Hub (**Admin → Organization → Settings Hub**) is a searchable index of every admin setting, organized by category. Each setting is listed with a description, search keywords, and a direct link to the page it lives on. Use it when you know *what* you want to change but not *where* it lives. ## 4. Running it ### Setting up your business profile 1. Go to **Admin → Organization → Business Profile**. 2. Fill in your company name, timezone, address, industry, and company size. 3. Upload your logo at **Admin → General Settings → Brand & Theme**, then click **Apply Theme**. The logo and brand colors appear in the sidebar and throughout the platform. ### Adding locations and departments 1. Go to **Admin → Organization → Locations** to create the physical sites where your team works. Locations are used by scheduling, attendance, and compliance. 2. Go to **Admin → Organization → Departments** to create your team structure. Departments group employees by function. ### Inviting users 1. Go to **Admin → Organization → Users** to add users one at a time, or use the CSV import to add many at once. 2. New users are created with the Member role and an `uninvited` invitation status. Use **Send Invite** on each user (or in bulk) to email them a sign-in link. 3. For quick team invites, go to **Admin → Team Invites** to send email-based invite links. ### Enabling apps 1. Go to **Admin → Apps → All Apps** to browse the app marketplace. 2. Click an app to see its detail page, then click **Enable**. 3. Licensed apps require a license before they can be enabled. If the Enable button shows a license error, the message names the suite that includes the app and how to get it. On a self-serve plan you add it yourself: an app priced per specialist from its page (**Add to plan**), a suite from **General Settings → Billing & Payments → Plan**. On a plan managed by a MangoApps account team, contact your account manager. 4. After enabling an app, open its settings page to configure it for your organization. Enabling an app makes it available; configuring it makes it useful. ### Configuring notifications Go to **Admin → General Settings → Notifications** to review and adjust how the platform sends push, email, and SMS notifications. Each app's notification categories can be enabled or disabled here. ## 5. Settings These are the first settings a new admin should review. Each links to a deeper configuration surface. | Setting | Where | Default | What it changes | |---|---|---|---| | Business timezone | Admin → Organization → Business Profile | None (must be set) | Governs schedule display, time calculations, and report dates across the platform | | Logo and brand colors | Admin → General Settings → Brand & Theme | Platform defaults | Sidebar branding, login page, and email headers | | New-user default role | Admin → Organization → Users (on create) | Member | The system role assigned when a user is added | | Sign-in policies | Admin → Security → Sign-in Policies | Platform defaults | Password requirements, session timeout, and lockout rules | | SSO configuration | Admin → Security → SSO Configuration | Disabled | SAML/OAuth single sign-on for the business | | Global notifications | Admin → General Settings → Notifications | Per-category defaults | Which notification channels (push, email, SMS) are active for each app | ## 6. More help - **Settings Hub** — search all admin settings from one page at Admin → Organization → Settings Hub - Each app has its own Overview and FAQ article covering setup and operations - Ask AI — the assistant answers platform questions from these articles **Keywords:** getting started, new admin, first time admin, admin setup, admin panel, admin sidebar, how to become admin, admin role, super admin, where is admin, admin settings, setup checklist, admin overview, onboarding, first week, admin gear icon ---